libisnativec-java - NMU or team upload?

Hi All, I just did a NMU for libisnativec-java and uploaded to DELAYED queue. But I am confused with that one. Old changelog shows it has always been "Team upload" but the "Maintainer:" does not say it is team maintained. Is NMU correct or shall I cancel that and do a normal "Team upload" instead

Re: Building r-cran-rcdk with cdk [Was: Re: Upgrading freehep to latest upstream (needed by cdk and probably others)]

Hi Andrius, On Mon, Jul 27, 2020 at 08:51:49AM +0300, mer...@debian.org wrote: > Hello, > > On 2020-07-27 08:38, tony mancill wrote: > >> It actually seems that org/openscience/cdk/smsd/Isomorphism is not > >> part of the currently packaged CDK. Any idea how to solve this? > > I am just starting

java-policy_0.57_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 27 Jul 2020 14:04:58 +0200 Source: java-policy Architecture: source Version: 0.57 Distribution: unstable Urgency: medium Maintainer: Debian Java Mailing List Changed-By: Emmanuel Bourg Closes: 966303 Changes: j

Processing of java-policy_0.57_source.changes

java-policy_0.57_source.changes uploaded successfully to localhost along with the files: java-policy_0.57.dsc java-policy_0.57.tar.xz java-policy_0.57_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#966303: marked as done (java-policy: Please specify the reference more precisely)

Your message dated Mon, 27 Jul 2020 12:19:37 + with message-id and subject line Bug#966303: fixed in java-policy 0.57 has caused the Debian Bug report #966303, regarding java-policy: Please specify the reference more precisely to be marked as done. This means that you claim that the problem h

Processed: Bug#966303 marked as pending in java-policy

Processing control commands: > tag -1 pending Bug #966303 [java-policy] java-policy: Please specify the reference more precisely Added tag(s) pending. -- 966303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Re: [kotlin] Call for Help!

Heyy, > > > >1. Error Log: (https://paste.debian.net/1157933/) On finding out the >reason for the same, some modules need an updated Gradle (which isn't >feasible). >2. What I decided was to patch the specific kotlin-Gradle-plugin with >it's an older version. Therefore, I tried

Re: [kotlin] Call for Help!

Heyy, While executing kotlin sub-modules for the kotlin-Gradle-plugin task. I was facing a couple of issues, which I tried to debug it in the following ways: 1. Error Log: (https://paste.debian.net/1157933/) On finding out the reason for the same, some modules need an updated Gradle (whi

Re: Processed: your mail

Hello, then this part should also updated: Chapter 1 Backgound https://www.debian.org/doc/packaging-manuals/java-policy/ch01.html Especially this part: Feel free to report comments, suggestions and/or disagreements to the java-common package () or the Debian Java mailing list . Change requests

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 966303 java-policy Bug #966303 [java-common] Java-common: Please specify the reference more precisely Bug reassigned from package 'java-common' to 'java-policy'. No longer marked as found in versions java-common/0.56. Ignoring request to

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 946688 java-policy Bug #946688 [java-common] hyperlink to bugs.debian.org/java-common is incorrect in https://www.debian.org/doc/manuals/debian-java-faq/ch1.en.html#s-bugs Bug reassigned from package 'java-common' to 'java-policy'. No lo