From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: briss-0.9
Date: Sat, 23 Dec 2023 02:45:08 +0100 [thread overview]
Message-ID: <20231223014508.hGNdaA5ZaVs4znCHIfI4qIspwkk1y7iQ1UWTJPPnVTY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44075@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
There's a closed pull request on the void-packages repository
New package: briss-0.9
https://github.com/void-linux/void-packages/pull/44075
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**. For now it uses the precompiled distribution (the LanguageTool package does this too). It should be possible to compile it if someone knows how to handle the dependencies.
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
closes #37737
I attempted to compile from source:
`distfiles="https://sourceforge.net/code-snapshots/svn/b/br/briss/code/briss-code-r75-briss.zip"`
But some dependencies are missing and I don't know how to package it:
```
[ERROR] Failed to execute goal on project briss: Could not resolve dependencies for project at.laborg:briss:jar:0.9: The following artifacts could not be resolved: jpedal:jpedal:jar:4.74b27, jai:jai-imageio:jar:1.0, jai:jai-core:jar:1.0, jai:jai-codec:jar:1.0: Failure to find jpedal:jpedal:jar:4.74b27 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
```
prev parent reply other threads:[~2023-12-23 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 10:55 [PR PATCH] " Eloitor
2023-09-08 1:45 ` github-actions
2023-09-08 16:20 ` [PR PATCH] [Updated] " Eloitor
2023-09-08 16:21 ` Eloitor
2023-12-08 1:46 ` github-actions
2023-12-23 1:45 ` github-actions [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231223014508.hGNdaA5ZaVs4znCHIfI4qIspwkk1y7iQ1UWTJPPnVTY@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).