Bug#1042129: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol
On Thu, Dec 7, 2023 at 3:46 PM Jérôme Charaoui wrote: > > For the record, the upload is ready to go. I'm now only waiting for a > new build-dependency to pass through NEW, jruby-mavengem. > Sounds great, I'll take a look at the new package. Thanks for working on the 9.4 release. On my side in the meantime, I recently have been refreshing and updating several jruby build-dependencies like jnr-* package and a few other related packages.
Bug#1054747: ruby-octokit: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: require 'pry-byebug'
On Fri, Oct 27, 2023 at 09:20:42PM +0200, Lucas Nussbaum wrote: > Source: ruby-octokit > Version: 4.20.0-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20231027 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > Failure/Error: require 'pry-byebug' > > > > Gem::MissingSpecError: > > Could not find 'pry' (~> 0.13.0) among 122 total gem(s) A possible fix for this issue could be to just update pry-byebug package to a more recent release. https://github.com/deivid-rodriguez/pry-byebug/commit/a915f21fc63aa94473bbe7cb752c0fabacc3e567 pry-byebug 3.10.1 depends on a pry version that's in the archive. https://packages.debian.org/source/unstable/pry
Bug#1056902: RM: libbytelist-java -- ROM; unused, obsolete
retitle 1056902 RM: libbytelist-java -- ROM; unused, obsolete severity 1056902 normal reassign 1056902 ftp.debian.org thanks As title says. This package was used by JRuby but is obsolete nowadays. All packages in the archive depending on this were migrated or removed, so there is no more reason to keep it around. Thanks, Miguel.
Bug#1056902: libbytelist-java: Package is obsolete and should be removed before trixie release
Package: libbytelist-java Version: 1.0.15-1 Severity: serious Filing this to get the package removed from testing. No packages should add dependencies on libbytelist-java since this package is obsolete. Its functionality is now included in JRuby (jruby.jar). See note at https://github.com/jruby/bytelist Once jvyamlb is removed (#1056899) from archive and ruby-psych its the dependency on this package, it should be removed from unstable. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-4-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libbytelist-java depends on: ii libjcodings-java 1.0.58-1 libbytelist-java recommends no packages. libbytelist-java suggests no packages. -- no debconf information
Bug#1042129: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol
On Sat, Nov 25, 2023 at 12:29 AM Jérôme Charaoui wrote: > > [...] > > I've been working on a 9.4 release, you can see the progress here: > https://salsa.debian.org/lavamind/jruby > > I plan to upload this version to experimental within a few days, I still > have some minor issues with the testsuite to iron out before. Excellent, that's good to hear. There is no point then just backporting the fix if you are close to finishing preparing an upload. Let me know if there is something else I can help with. I think I'll take a look at some jnr-* dependencies packages that could use a new upstream release and/or bugfixes. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://keyserver.pgp.com/ "Faith means not wanting to know what is true." -- Nietzsche
Bug#1042129: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol
Thomas and Jérôme, Do you have any concerns with me uploading a fix for this issue? I'm working with some folks here in Cambridge MiniDebConf and I also have some cycles to spare to work on JRuby and maybe prepare a new upstream release for 9.3 and/or 9.4 series (experimental).
Bug#1042129: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol
tags 1042129 + patch
thanks
Upstream handled this when they upgraded Joni dependency to 2.2 on
JRuby 9.4 series.
https://github.com/jruby/jruby/commit/3c94d31f1e198f294e9bfcb96b4188c315252b6b
https://github.com/jruby/jruby/commit/783d14bcb140477bb2577310a90742d594a48896
See attached a fix for this issue.
diff -Nru jruby-9.3.9.0+ds/debian/changelog jruby-9.3.9.0+ds/debian/changelog
--- jruby-9.3.9.0+ds/debian/changelog 2023-01-16 21:08:51.0 +
+++ jruby-9.3.9.0+ds/debian/changelog 2023-11-24 11:48:05.0 +
@@ -1,3 +1,11 @@
+jruby (9.3.9.0+ds-9~miguel1) UNRELEASED; urgency=medium
+
+ * Fix FTBFS: adapt and backport changes from 9.4 releases
+to accomodate for changes in regexp library Joni 2.2.
+(Closes: #1042129)
+
+ -- Miguel Landaeta Fri, 24 Nov 2023 11:48:05 +
+
jruby (9.3.9.0+ds-8) unstable; urgency=medium
* d/tests: flag jirb test as flaky
diff -Nru
jruby-9.3.9.0+ds/debian/patches/0012-Use-Region-accessors-in-prep-for-privatizing-fields.patch
jruby-9.3.9.0+ds/debian/patches/0012-Use-Region-accessors-in-prep-for-privatizing-fields.patch
---
jruby-9.3.9.0+ds/debian/patches/0012-Use-Region-accessors-in-prep-for-privatizing-fields.patch
1970-01-01 01:00:00.0 +0100
+++
jruby-9.3.9.0+ds/debian/patches/0012-Use-Region-accessors-in-prep-for-privatizing-fields.patch
2023-11-24 11:48:05.0 +
@@ -0,0 +1,390 @@
+Subject: Use Region accessors in prep for privatizing fields
+Forwarded:
https://github.com/jruby/jruby/commit/3c94d31f1e198f294e9bfcb96b4188c315252b6b
+--
+diff --git a/core/src/main/java/org/jruby/RubyMatchData.java
b/core/src/main/java/org/jruby/RubyMatchData.java
+index 48fa92b..87e7c9d 100644
+--- a/core/src/main/java/org/jruby/RubyMatchData.java
b/core/src/main/java/org/jruby/RubyMatchData.java
+@@ -175,11 +175,11 @@ public class RubyMatchData extends RubyObject {
+ private void updateCharOffsetOnlyOneReg(ByteList value, Encoding
encoding) {
+ if (charOffsetUpdated) return;
+
+-if (charOffsets == null || charOffsets.numRegs < 1) charOffsets = new
Region(1);
++if (charOffsets == null || charOffsets.getNumRegs() < 1) charOffsets
= new Region(1);
+
+ if (encoding.maxLength() == 1) {
+-charOffsets.beg[0] = begin;
+-charOffsets.end[0] = end;
++charOffsets.setBeg(0, begin);
++charOffsets.setEnd(0, end);
+ charOffsetUpdated = true;
+ return;
+ }
+@@ -195,14 +195,14 @@ public class RubyMatchData extends RubyObject {
+ updatePairs(value, encoding, pairs);
+
+ if (begin < 0) {
+-charOffsets.beg[0] = charOffsets.end[0] = -1;
++charOffsets.setBeg(0, charOffsets.setEnd(0, -1));
+ return;
+ }
+ Pair key = new Pair();
+ key.bytePos = begin;
+-charOffsets.beg[0] = pairs[Arrays.binarySearch(pairs, key)].charPos;
++charOffsets.setBeg(0, pairs[Arrays.binarySearch(pairs, key)].charPos);
+ key.bytePos = end;
+-charOffsets.end[0] = pairs[Arrays.binarySearch(pairs, key)].charPos;
++charOffsets.setEnd(0, pairs[Arrays.binarySearch(pairs, key)].charPos);
+
+ charOffsetUpdated = true;
+ }
+@@ -211,14 +211,14 @@ public class RubyMatchData extends RubyObject {
+ if (charOffsetUpdated) return;
+
+ final Region regs = this.regs;
+-int numRegs = regs.numRegs;
++int numRegs = regs.getNumRegs();
+
+-if (charOffsets == null || charOffsets.numRegs < numRegs) charOffsets
= new Region(numRegs);
++if (charOffsets == null || charOffsets.getNumRegs() < numRegs)
charOffsets = new Region(numRegs);
+
+ if (encoding.maxLength() == 1) {
+ for (int i = 0; i < numRegs; i++) {
+-charOffsets.beg[i] = regs.beg[i];
+-charOffsets.end[i] = regs.end[i];
++charOffsets.setBeg(i, regs.getBeg(i));
++charOffsets.setEnd(i, regs.getEnd(i));
+ }
+ charOffsetUpdated = true;
+ return;
+@@ -229,23 +229,23 @@ public class RubyMatchData extends RubyObject {
+
+ int numPos = 0;
+ for (int i = 0; i < numRegs; i++) {
+-if (regs.beg[i] < 0) continue;
+-pairs[numPos++].bytePos = regs.beg[i];
+-pairs[numPos++].bytePos = regs.end[i];
++if (regs.getBeg(i) < 0) continue;
++pairs[numPos++].bytePos = regs.getBeg(i);
++pairs[numPos++].bytePos = regs.getEnd(i);
+ }
+
+ updatePairs(value, encoding, pairs);
+
+ Pair key = new Pair();
+-for (int i = 0; i < regs.numRegs; i++) {
+-if (regs.beg[i] < 0) {
+-charOffsets.beg[i] = charOffsets.end[i] = -1;
++for (int i = 0; i < regs.getNumRegs(); i++) {
++if (regs.getBeg(i) < 0) {
++charOff
Bug#893244: jruby FTBFS with openjdk-9
On Tue, Feb 26, 2019 at 03:05:48PM +0100, Markus Koschany wrote: > > [...] > > The FTBFS bug got fixed yesterday. I should complain more often. Andrej > uploaded version 9.1.17 to unstable. This is not the latest one but I > guess better than nothing? The original bug has not been closed yet. > Andrej, can we close it now and Debian bug #917702 too? Thanks a lot to Andrej for putting together a new upstream version upload at such short notice!! Now I think with that should be enough to fulfill the reverse build-depends to avoid having to drop packages from the upcoming release but I reiterate that jruby in its current state in Debian is only usable for very simple use cases. The output from many tests during build time is evidence of this. Any user expecting to run production workloads with Debian's jruby will be disappointed and they will require to use upstream artifacts, unfortunately. Thanks again for fixing the outstanding RC bugs on this package!! -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: PGP signature
Bug#893244: jruby FTBFS with openjdk-9
Hi Markus, On Sun, Feb 24, 2019 at 08:39:48PM +0100, Markus Koschany wrote: > JRuby is a mess. I guess we "just" need to package the latest upstream > release to fix the FTBFS bugs. Nobody felt like doing that in the past > twelve months, so I think it is unrealistic to believe we can make it > happen within one week. Of course if the release team can be convinced > to accept a new upstream release there might be additional time left. I agree, jruby is a mess, mostly because of me since I didn't have almost any time during this release cycle to work on it. I think jruby should be dropped from buster and a new libspring-java upload should be prepared shortly, to disable jruby support in it. It's not realistic to think that a new upstream release for jruby can be prepared in a week and that will work to be well supported during the next stable release life cycle. Cheers, Miguel. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: PGP signature
Bug#891449: jruby: system() does not work on arm64
tags 891449 + help
thanks
On Sun, Feb 25, 2018 at 02:13:41PM -0300, Antonio Terceiro wrote:
> Package: jruby
> Version: 9.1.13.0-1
> Severity: grave
> Justification: renders package unusable
>
> When debugging #890046 on ruby-json, I realized that I cannot execute
> any program with system() under jruby on arm64:
>
> 8<8<8<-
> (sid_arm64-dchroot)terceiro@amdahl:~/ruby-json-2.1.0+dfsg$ jruby -e
> 'system("date")'
> Errno::EACCES: Permission denied - /bin/date
> system at org/jruby/RubyKernel.java:1544
>at -e:1
> (sid_arm64-dchroot)terceiro@amdahl:~/ruby-json-2.1.0+dfsg$ /bin/date
> Sun Feb 25 16:59:17 UTC 2018
> 8<8<8<-
>
> - Passing the full path does not help
> - I only see this on arm64
Help on this bug is more than welcome.
--
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche
signature.asc
Description: PGP signature
Bug#895778: jruby: Several security vulnerabilities
On Sun, Apr 15, 2018 at 10:48:10PM +0200, Markus Koschany wrote: > I intend to work on the patches for Jessie and Stretch. Unstable could > be a bit more complicated due to the FTBFS with OpenJDK 9. Hi Markus, Thanks for taking care of jessie and stretch. I expect to be able to update jruby in unstable soon, although there is some pending work to do, as I mentioned in #895837. These days I'm more involved with that project as upstream, so I haven't find enough time to work on this package yet. Cheers, Miguel. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: PGP signature
Bug#870308: ruby-ridley FTBFS: test failures
tags 870308 + confirmed pending thanks I prepared an upload with a new upstream that fix this bug. However, since I'm no longer involved in the maintenance of this package (#890767), I'd prefer that another team member take a look at the git repo and complete the upload to fix this bug. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: PGP signature
Bug#888173: ruby-sawyer: FTBFS on ruby2.5: can't dump anonymous class
tags 888173 + confirmed upstream buster sid owner 888173 ! thanks The most immediate mitigation for this issue seems to be to disable the affected tests and report this to upstream. psych library included in ruby stdlib was updated between ruby2.4 to ruby2.5, from 2.2.4 to 3.0.0 and it has introduced some breaking changes. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: PGP signature
Bug#888129: ruby-json-spec: FTBFS on ruby2.5: Fixnum/Integer
owner 888129 ! thanks I'll work on this issue this weekend. Since it's already fixed at upstream, it should be a quick fix. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: PGP signature
Bug#890592: jruby FTBFS: Could not resolve dependencies for project org.jruby:jruby-core:jar:9.1.13.0
tags 890592 + confirmed owner 890592 ! thanks On Fri, Feb 16, 2018 at 02:36:19PM +0200, Adrian Bunk wrote: > Source: jruby > Version: 9.1.13.0-1 > Severity: serious > Control: affects -1 src:jruby-openssl src:mustache-java src:yecht > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jruby.html > > [...] > > [INFO] > [INFO] > > [INFO] Building JRuby Core 9.1.13.0 > [INFO] > > [WARNING] The POM for net.java.dev.jna:jna:jar:debian is missing, no > dependency information available > [WARNING] The POM for net.java.dev.jna:jna-platform:jar:debian is missing, no > dependency information available > [INFO] > > > [...] I could confirm the FTBFS issue however I'm still not sure that jruby is at fault here. libjna-java is not a direct or indirect jruby B-D so I'm not sure from where is coming this missing dependency message. I could just fix this issue by adding the missing B-D but I'm not convinced that's the right solution yet. The last time jruby was built by buildd, it didn't require JNA. https://buildd.debian.org/status/fetch.php?pkg=jruby=all=9.1.13.0-1=1507248630=0 -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: PGP signature
Bug#888174: ruby-whitequark-parser: FTBFS on ruby2.5: Update test_current for 2.5.0
owner 888174 ! tags 888174 + confirmed pending thanks I'll upload 2.4.0.2 very soon with a fix for this. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: PGP signature
Bug#877274: ruby-psych: broken symlink: /usr/lib/ruby/vendor_ruby/psych.jar -> ../../../share/java/psych.jar
severity 877274 normal thanks On Sat, Sep 30, 2017 at 03:20:36AM +0200, Andreas Beckmann wrote: > Package: ruby-psych > Version: 2.2.4-6 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package ships (or creates) > a broken symlink. Hi, This broken symlink is not a bug. The symlink will only be relevant to users that use ruby-psych library in combination with jruby. jruby explicitly depends on ruby-psych and libpsych-java. Most ruby users in Debian currently rely on MRI (ruby2.3 and/or ruby2.5), so the Java extension psych.jar is of no use to them. > > From the attached log (scroll to the bottom...): > > 0m27.6s ERROR: FAIL: Broken symlinks: > /usr/lib/ruby/vendor_ruby/psych.jar -> ../../../share/java/psych.jar > > Is ruby-psych missing a dependency on libpsych-java? It's not a dependency, it's only a suggestion. That's why there is a Suggests on libpsych-java instead of a hard dependency. I'll close this bug later unless there is another concern I'm not noticing right now, but as I said the broken symlink should not be a problem. Thanks, Miguel. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: PGP signature
Bug#881477: maven-debian-helper: missing dependency on libplexus-classworlds2-java
On Sun, Nov 12, 2017 at 10:59:46AM +0200, Adrian Bunk wrote: > Package: maven-debian-helper > Version: 2.2.6 > Severity: serious > > Many packages FTBFS: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/geronimo-validation-1.0-spec.html I'll take care of that later today. The fix is not to add a dependency on libplexus-classworlds2-java but to remove the maven rule on this package that force to use '2.x' and make it use the default 'debian' one that is provided by libplexus-classworlds-java. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: PGP signature
Bug#873118: commons-io: FTBFS: Several failed unit tests
Package: src:commons-io Version: 2.5-1 Severity: serious Justification: fails to build from source (but built successfully in the past) [...] Results : Tests in error: FileUtilsTestCase.testCopyDirectoryToDirectory_NonExistingDest:1323 ?? IO Unab... FileUtilsTestCase.testCopyDirectoryToExistingDest:1409 ?? IO Unable to delete ... FileUtilsTestCase.testCopyDirectoryToNonExistingDest:1367 ?? IO Unable to dele... Tests run: 1157, Failures: 0, Errors: 3, Skipped: 4 [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [1;31mBUILD FAILURE[m [[1;34mINFO[m] [1m[m [[1;34mINFO[m] Total time: 02:01 min [[1;34mINFO[m] Finished at: 2017-08-24T09:16:19Z [[1;34mINFO[m] Final Memory: 14M/276M [[1;34mINFO[m] [1m[m [[1;31mERROR[m] Failed to execute goal [32morg.apache.maven.plugins:maven-surefire-plugin:2.19.1:test[m [1m(default-test)[m on project [36mcommons-io[m: [1;31mThere are test failures.[m [[1;31mERROR[m] [1;31m[m [[1;31mERROR[m] [1;31mPlease refer to /<>/target/surefire-reports for the individual test results.[m [[1;31mERROR[m] -> [1m[Help 1][m [[1;31mERROR[m] [[1;31mERROR[m] To see the full stack trace of the errors, re-run Maven with the [1m-e[m switch. [[1;31mERROR[m] Re-run Maven using the [1m-X[m switch to enable full debug logging. [[1;31mERROR[m] [[1;31mERROR[m] For more information about the errors and possible solutions, please read the following articles: [[1;31mERROR[m] [1m[Help 1][m http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1 debian/rules:4: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- System Information: Debian Release: 8.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche commons-io_2.5-1_amd64-2017-08-24T09:13:55Z.build.gz Description: application/gzip signature.asc Description: Digital signature
Bug#857375: marked as pending
tag 857375 pending thanks Hello, Bug #857375 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-jar-dependencies.git/commit/?id=cb87d9b --- commit cb87d9bc7c2dacd9e81a24ee1a40aa0891ff1e9c Author: Miguel Landaeta <nomad...@debian.org> Date: Sat Aug 5 15:17:46 2017 +0100 Remove conflicting rubygems plugin diff --git a/debian/changelog b/debian/changelog index e4a74e2..c65593e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +ruby-jar-dependencies (0.3.10-2) UNRELEASED; urgency=medium + + * Remove /usr/lib/ruby/vendor_ruby/rubygems_plugin.rb since is causing +upgrade problems. (Closes: #857375) + + -- Miguel Landaeta <nomad...@debian.org> Sat, 05 Aug 2017 14:02:11 + + ruby-jar-dependencies (0.3.10-1) unstable; urgency=medium * Initial release. (Closes: #855086)
Bug#869417: marked as pending
tag 869417 pending thanks Hello, Bug #869417 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-octokit.git/commit/?id=dfff0c5 --- commit dfff0c563e0d4299efe70059089b73ad6b976d7f Author: Miguel Landaeta <nomad...@debian.org> Date: Mon Jul 24 18:26:32 2017 +0100 Fix dependency on ruby-sawyer diff --git a/debian/changelog b/debian/changelog index a800d5b..79c49ce 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +ruby-octokit (4.7.0-3) UNRELEASED; urgency=medium + + * Drop erroneus dependency constraint on ruby-sawyer that rendered the +package as uninstallable. (Closes: #869417). + + -- Miguel Landaeta <nomad...@debian.org> Mon, 24 Jul 2017 18:23:46 +0100 + ruby-octokit (4.7.0-2) unstable; urgency=medium * Upload to unstable.
Bug#868913: jruby: FTBFS: ERROR Manifest org.jruby:jruby-complete:bundle:1.7.26 : Classes found in the wrong directory: {module-info.class=org.jruby.org.objectweb.asm.module-info}
notfound 868913 1.7.26-1 reassign 868913 libmaven-bundle-plugin-java 2.5.4-3 severity 868913 normal tags 868913 + confirmed upstream forwarded 868913 https://issues.apache.org/jira/browse/FELIX-5430 retitle 868913 libmaven-bundle-plugin-java: Unexpected error about classes found in the wrong directory thanks On Wed, Jul 19, 2017 at 05:57:43PM +0200, Lucas Nussbaum wrote: > Source: jruby > Version: 1.7.26-1 > Severity: serious > Tags: buster sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20170719 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. This is really a bug in maven-bundle-plugin that is affecting jruby and probably is going to affect other packages that create bundles with that plugin during build time. maven-bundle-plugin seems to be unable to process jars including a module definition file (module-info.class) to be used with Java 9. In this case since libasm-java/6.0~alpha-1 jar files are shipping these files already, this is breaking jruby build. The next jruby upload will include a workaround for this. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#867652: jruby: FTBFS: Error creating shaded jar: Error in ASM processing class module-info.class: RemappingClassAdapter is deprecated, use ClassRemapper instead
Hi, Quick FYI note for anybody interested in fixing bugs in jruby 1.7.x: Right now I'm working to upload all the jruby 9.x B-D to sid, so it's unlikely I'll spend any effort on fixing bugs on this version unless they are also present in stable. I'll close/fix this bug when I get jruby 9.x building in sid. Cheers, Miguel. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#855673: rubocop: FTBFS: RuboCop::Cop::Lint::UselessAssignment when a variable is reassigned in loop body but won't be referenced either next iteration or loop condition registers an offense
On Tue, Feb 21, 2017 at 05:01:03PM +1300, Chris Lamb wrote: > Source: rubocop > Version: 0.47.1+dfsg-1 > Severity: serious > Justification: fails to build from source > User: reproducible-bui...@lists.alioth.debian.org > Usertags: ftbfs > X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org > > Dear Maintainer, > > rubocop fails to build from source in unstable/amd64: Hi Chris, This is not a FTBFS, in the build log can be seen how the package is successfully built: > dpkg-deb: building package 'rubocop' in '../rubocop_0.47.1+dfsg-1_all.deb'. The listed failures are just unit tests that upstream decided to mark as pending since they are not passing at the present time. I'll close this bug later unless I'm missing something else. Thanks, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#849217: jruby: FTBFS (sbuild hangs)
owner 849217 ! tags 849217 + moreinfo help thanks On Fri, Dec 23, 2016 at 06:49:41PM +0100, Santiago Vila wrote: > Package: src:jruby > Version: 1.7.26-1 > Severity: serious > > Dear maintainer: > > I tried to build this package in stretch with "dpkg-buildpackage -A" > (which is what the "Arch: all" autobuilder would do to build it) > but it failed: > > [...] > > E: Build killed with signal TERM after 60 minutes of inactivity > > > In this case, sbuild aborted the build because it detected too much > time without log activity, which is what happens when the build hangs. > > If you need a full build log, just say so and I will include it, > but the build also hangs in the reproducible builds autobuilders: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jruby.html > > If this is really a bug in one of the build-depends, please use reassign and > affects, > so that this is still visible in the page for this package. > Hello Santiago, Can you provide the full log of the failed build attempt? I can't reproduce this issue, although I don't use sbuild to build my packages but cowbuilder. Since I couldn't reproduce the issue with my builder tool of choice, I'll setup sbuild later to try again. In the meantine, the full build log could be handy. Any help to diagnose/reproduce the issue is more than welcome. Thanks, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#844841: jruby-maven-plugins: FTBFS: [ERROR] /<>/ruby-tools/src/main/java/de/saumya/mojo/gems/spec/yaml/YamlGemSpecificationIO.java:[8,26] cannot find symbol
tags 844841 confirmed thanks It looks like this package is broken since several months ago because the FTBFS is due to missing classes in snakeyaml 1.17 that was uploaded in April 2016. This package has never been in a stable release and is only needed to package jruby 9k. I could upload a new upstream release to fix this before the freeze but I'm not making promises. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#839567: rake does not work with jruby
Hi, Resuming the discussion about this bug, I believe the best solution we can come up right now is to drop the Provides for ruby-interpreter in jruby, given how late we are on the release cycle already. However, I'd like to revisit this issue during "buster" development cycle. jruby provides high compatibility with MRI, so users should be able to use rake and/or another standard ruby tools with jruby if they want. We should have in place a simple way to switch interpreters. I'd like to have jruby 9k packaged for "buster", so this package can be more relevant and more useful for real world users, so it's likely this need will surface again in the future. I plan to upload the most recent upstream release for jruby 1.7.x this weekend and fix all remaining RC bugs, unless there is an objection or some unexpected blocker. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#821181: jruby: FTBFS due to PsychParser class error
tags 821181 + pending thanks On Sat, Apr 16, 2016 at 03:08:19PM +0100, Miguel Landaeta wrote: > > [...] > > I already fixed the issue in the git repo. > > I don't upload the fixed package yet because it keeps FTBFS due to > another issue. It turns out I was responsible for the second bug. When I updated yecht 1.1-1, the updated .jar file is now dropping a class in the default package (YechtService.class). That doesn't work with maven-bundle-plugin. I got jruby 1.7.25 building in Debian although is not ready for upload since some tests are failing and I need to workaround the yecht issue in similar way to what is described here: https://techotom.wordpress.com/2014/10/21/fixing-the-default-package-is-not-permitted-by-the-import-package-syntax-with-maven-bundle-plugin/ Help is welcome as usual. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#821181: jruby: FTBFS due to PsychParser class error
On Sat, Apr 16, 2016 at 10:04 PM, Emmanuel Bourg <ebo...@apache.org> wrote: > Le 16/04/2016 16:08, Miguel Landaeta a écrit : > >> The bug was caused by a breaking change introduced in snakeyaml 1.17. > > Hi Miguel, Hello Emmanuel, > > Was this caused by the removal of getVersion() from > DumperOptions.Version? I may try to patch snakeyaml and bring back the > method to preserve the compatibility. > Yes, that was the cause of the bug. > What is the other issue you encountered? > After patching the getVersion() change I found the following error with maven-bundler-plugin: [...] [WARNING] Manifest org.jruby:jruby-complete:bundle:1.7.25 : Export org.jruby.util.io, has 4, private references [jnr.posix, jnr.unixsocket, org.jcodings, jnr.constants.platform], [ERROR] Manifest org.jruby:jruby-complete:bundle:1.7.25 : The default package '.' is not permitted by the Import-Package syntax. This can be caused by compile errors in Eclipse because Eclipse creates valid class files regardless of compile errors. The following package(s) import from the default package null [ERROR] Error(s) found in manifest configuration [INFO] [INFO] Reactor Summary: [INFO] [INFO] JRuby .. SUCCESS [ 0.119 s][INFO] JRuby Core . SUCCESS [01:00 min] [INFO] JRuby Ext .. SUCCESS [ 0.004 s][INFO] JRuby Readline . SUCCESS [ 3.436 s] [INFO] JRuby Ripper ... SUCCESS [ 4.680 s] [INFO] JRuby Lib Setup SUCCESS [ 0.003 s] [INFO] JRuby Artifacts SUCCESS [ 0.003 s] [INFO] JRuby Stdlib ... SUCCESS [ 1.777 s] [INFO] JRuby Complete . FAILURE [ 5.236 s] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 01:17 min [INFO] Finished at: 2016-04-16T13:12:11+00:00 [INFO] Final Memory: 110M/751M [INFO] [ERROR] Failed to execute goal org.apache.felix:maven-bundle-plugin:2.5.4:manifest (default) on project jruby-complete: Error(s) found in manifest configuration -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [...] I have not found yet the root cause of that. When I have some time available I will keep debugging if nobody beats me to it. Cheers,
Bug#821181: jruby: FTBFS due to PsychParser class error
tags 821181 + pending thanks On Sat, Apr 16, 2016 at 12:19:01PM +0100, Miguel Landaeta wrote: > Package: src:jruby > Version: 1.7.22-2 > Severity: serious > Justification: fails to build from source (but built successfully in the past) > Owner: Miguel Landaeta <nomad...@debian.org> > The bug was caused by a breaking change introduced in snakeyaml 1.17. I already fixed the issue in the git repo. I don't upload the fixed package yet because it keeps FTBFS due to another issue. Help is welcome. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#821181: jruby: FTBFS due to PsychParser class error
Package: src:jruby Version: 1.7.22-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Owner: Miguel Landaeta <nomad...@debian.org> Relevant error message: [...] [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /build/jruby-1.7.22/core/src/main/java/org/jruby/ext/psych/PsychParser.java:[232,66] error: cannot find symbol [INFO] 1 error [INFO] - [...] -- System Information: Debian Release: 8.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche jruby_1.7.22-2_amd64.build.gz Description: application/gzip signature.asc Description: Digital signature
Bug#804558: tweepy: FTBFS: ImportError: No module named {unittest2,vcr}
On Mon, Jan 4, 2016 at 6:43 AM, Carl Chenet <cha...@debian.org> wrote: > Hi Miguel, > > First of all, happy new year 2016! Hi Carl, happy new year to you as well! :) > [...] > > Tell me if I'm wrong but unittests executions are not mandatory by > Debian policy while building a Debian package. That's right, this is not mandatory. > > While waiting that somebody packages unittest2 and/or vcr for Debian, > could you disable the unit tests while creating the Debian package of > Tweepy? I've 2 more Debian package coming up and depending on > python3-tweepy so that would help me *a lot*. > > Tell me if you need that I push the modifications in the debian/rules (I > guess it's a simple override). Let's do this: * Can you file a wishlist bug on tweepy asking to enable the unit tests during build time and maybe explain why that can't be enabled right now and/or mark the bug as blocked by the unittest2 and/or vcr ITPs? * Push and upload the changes to workaround the FTBFS. I can't fix this bug right now because I'm about to begin my move to another country and my workstation with my PGP key has some connection problems during this week. Thanks, Miguel. -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x6E608B637D8967E9 available at http://keyserver.pgp.com/ "Faith means not wanting to know what is true." -- Nietzsche
Bug#809281: (no subject)
owner 809281 ! tags 809281 + confirmed thanks I'll take care of this. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#793911: groovy should not release with stretch
Hi Markus, On Fri, Dec 11, 2015 at 09:23:42PM +0100, Markus Koschany wrote: > > we can always consider to fix red5 with a NMU. We just should raise the > severity accordingly before we do that. Sure, that's a valid option. An NMU to DELAYED/7 or something is OK with me. > I hope I can lend you a hand with an update of libspring-java after I > have packaged the latest netbeans release. Perhaps you can write a short > TODO list and push it to the libspring-java repo, which upstream should > be packaged, if we have to package new dependencies and where you need > help. OK, unfortunately I don't have too much time lately but I think I can review latest Spring upstream releases to document if/which new dependencies are needed and push that to the repo. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#793911: groovy should not release with stretch
Hi Markus, On Sat, Nov 28, 2015 at 01:53:03PM +0100, Markus Koschany wrote: > > [...] > > These are the current reverse dependencies in unstable: > > libspring-java -> must be updated to a newer version I already pushed some trivial changes to the repo to migrate libspring-java to groovy2. > jenkins -> unmaintainable, can be ignored > > It bothers me jenkins package status but I'm not in a position to > help at this moment. > > red5 -> must be updated to a newer version Emmanuel sent a patch for this. Please see #805627. > If you want to update either libspring-java or red5, that would be a big > help. To package libspring-java new upstream releases is a task that would be very appreciated although is not easy but with the recent progress in Maven and Gradle helpers (thanks to Emmanuel again!) maybe this is something more feasible nowadays. Regarding red5, I'm not quite sure how much is used in Debian nowadays. Maybe we should contact Damien to check if he agrees to transfer its maintenance to pkg-java. I'm ccing him just in case. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#785876: turpial: Please update to GStreamer 1.x
On Sat, Nov 07, 2015 at 02:34:47PM +0100, Moritz Mühlenhoff wrote: > > This is marked as forwarded, was there a reply? I can find anything > anything the github issue tracker, should turpial be removed? Hi Moritz, There was not a reply from upstream. I follow closely the development of this project and I noticed there is almost no visible activity in this project for more than a year so I agree turpial should be removed if it's blocking important migrations. I'll file a RM bug for it. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#800807: jasperreports: FTBFS: cannot find symbol org.apache.batik.dom.svg.SAXSVGDocumentFactory
Package: src:jasperreports Version: 4.1.3+dfsg-3 Severity: serious Justification: fails to build from source (but built successfully in the past) Relevant error messages: [...] compile: [mkdir] Created dir: /tmp/buildd/jasperreports-4.1.3+dfsg/build/classes [javac] /tmp/buildd/jasperreports-4.1.3+dfsg/build.xml:9: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 1579 source files to /tmp/buildd/jasperreports-4.1.3+dfsg/build/classes [javac] warning: [options] bootstrap class path not set in conjunction with -source 1.5 [javac] /tmp/buildd/jasperreports-4.1.3+dfsg/src/net/sf/jasperreports/renderers/BatikRenderer.java:55: error: cannot find symbol [javac] import org.apache.batik.dom.svg.SAXSVGDocumentFactory; [javac]^ [javac] symbol: class SAXSVGDocumentFactory [javac] location: package org.apache.batik.dom.svg [javac] /tmp/buildd/jasperreports-4.1.3+dfsg/src/net/sf/jasperreports/renderers/BatikRenderer.java:175: error: cannot find symbol [javac] new SAXSVGDocumentFactory(userAgent.getXMLParserClassName(), true); [javac] ^ [javac] symbol: class SAXSVGDocumentFactory [javac] location: class BatikRenderer [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 2 errors [javac] 1 warning [...] -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#793630: groovy 1.8.6 and libcommons-cli-java 1.3.1 FTBFS
On Tue, Aug 25, 2015 at 11:52:47PM +0200, Markus Koschany wrote: > > I suggest to ask the release team for an exception and to provide the > security fix via testing-proposed-updates. The CVE-fix appears to be > straightforward and could be uploaded afterwards to stable-proposed-updates. Thanks for the suggestion. I'll ask for authorization to release team to go this with this approach. > > We shouldn't invest too much time in groovy 1.x anymore. I think the > time is better spent on trying to switch all r-deps from groovy 1.x to > 2.x as soon as possible and getting rid of this package. I absolutely agree with you on this. All the time that I want to spend working on groovy 1.x is to migrate r-deps to 2.x. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#795851: openjfx: FTBFS with Gradle 2.5
Hi Markus, On Thu, Sep 10, 2015 at 08:24:52PM +0200, Markus Koschany wrote: > *ping* (ahem, reappearing after my vacations) > Shall I proceed with this temporary solution? The only r-dep of openjfx > is netbeans which does not use openjfx at runtime so far. Someone > interested in sponsoring this? If nobody else has any objection, I can sponsor this. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#795207: samizdat: FTBFS: NameError: uninitialized constant Psych::ENGINE
owner 795207 ! reassign 795207 ruby-whitewash retitle 795207 ruby-whitewash: Broken when used with ruby2.2 due to YAML/Psych changes severity 795207 important affects 795207 src:samizdat thanks On Tue, Aug 11, 2015 at 07:56:17PM +0100, Chris West (Faux) wrote: Source: samizdat Version: 0.7.0-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche
Bug#791782: More test failures in ruby-patron
On Wed, Aug 12, 2015 at 01:48:59AM +, Potter, Tim (Cloud Services) wrote: I’m trying to rebuild this package from source and it’s also failing, but I get a different set of errors. Perhaps this will shed some light on what’s happening to someone: I'm not familiar at all with ruby-patron internals or upstream plans but I was looking at this package some weeks ago and it looks totally broken with ruby2.2 and I don't see any activity at upstream to fix that anytime soon now. Maybe I'm wrong but I didn't find any action plan regarding ruby2.2. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche
Bug#793630: groovy 1.8.6 and libcommons-cli-java 1.3.1 FTBFS
On Wed, Jul 29, 2015 at 10:00:16AM +0100, Russel Winder wrote: Emmanuel, Miguel, Hi Russel, Apache Groovy 1.x series is no longer maintained. All effort is now on the Apache Groovy 2.4.x and 2.5-SNAPSHOT versions. If Debian is to remove Commons CLI 1.2 then I suggest removing the groovy package since the groovy2 package is in place already, and is the right version for Debian to go with. That's right. We are no longer maintaining Groovy 1.x although we have several packages depending on it and our latest Debian stable release still includes groovy 1.x. I stumbled upon this bug due to my attempt to fix CVE-2015-3253 in unstable for groovy 1.8.6 (the published fix is relevant for all groovy versions since 1.7.0). I expect to remove groovy eventually but in the meantime we are applying only security bug fixes. We are working on groovy2 now. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#793630: groovy 1.8.6 and libcommons-cli-java 1.3.1 FTBFS
On Wed, Jul 29, 2015 at 09:57:35AM +0200, Emmanuel Bourg wrote: Le 29/07/2015 03:35, Miguel Landaeta a écrit : Since you have worked upstream with libcommons-cli-java, I hope to don't bother you with this help request. commons-cli provides several parsers with different behaviors. Up to 1.2 there was a gnu and a posix parsers, and starting with 1.3 I introduced a new unified parser (DefaultParser). You may try using it, it's just a matter of changing the instantiation and it's likely to work better. Yes, I already tried that with no luck. The thing is, commons-cli 1.3 is supposed to be backward compatible with 1.2 and I believe so. It still provides PosixParser class although is marked as deprecated. Current groovy version in the archive is 1.8.6-4 and it was compiled with commons-cli 1.2. When you try to build it today, ant tasks defs fail when they are run against 1.3. So, I can't even do a test build to check if DefaultParser works OK or not. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#793630: groovy 1.8.6 and libcommons-cli-java 1.3.1 FTBFS
tags 793630 + help thanks Hi Emmanuel, how are you? I'm writing you due to #793630. It's an FTBFS that I strongly suspect is caused by libcommons-cli-java 1.3. When I try to build groovy with libcommons-cli 1.2-3 it builds OK but it fails with 1.3.1-2 due to groovyc not recognizing a flag. I tried hard to debug this issue but I'm unable to understand how/why groovyc ends being called with --null flag. I stumbled upon this issue because I need to upload a security fix for groovy but I'm unable to build groovy in sid due to this issue. Since you have worked upstream with libcommons-cli-java, I hope to don't bother you with this help request. Thanks, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#793397: groovy: Remote execution of untrusted code, DoS (CVE-2015-3253)
owner 793397 ! tags 793397 + confirmed owner 793398 ! tags 793398 + confirmed thanks Thanks for the report, I'll take care of this bug. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#793635: groovy2: FTBFS: Could not find commons-cli:commons-cli:1.2
: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche groovy2_2.2.2+dfsg-4_amd64.build.gz Description: application/gzip signature.asc Description: Digital signature
Bug#793630: groovy: FTBFS: ant is passing an invalid flag to groovyc
') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche groovy_1.8.6-4_amd64.build.gz Description: application/gzip signature.asc Description: Digital signature
Bug#793640: groovy2: FTBFS: java.lang.ClassNotFoundException: org.apache.maven.building.Source
/buildd/groovy2-2.4.3+dfsg' debian/rules:13: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 E: Failed autobuilding of package I: unmounting dev/pts filesystem I: unmounting run/shm filesystem I: unmounting proc filesystem - Cleaning COW directory forking: rm -rf /var/cache/pbuilder/build//cow.15918 -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche groovy2_2.4.3+dfsg-1_amd64.build.gz Description: application/gzip signature.asc Description: Digital signature
Bug#789946: FTBFS: Failed to resolve artifact. Missing: org.jruby.extras:jffi:jar:debian
reassign 789946 libjenkins-java 1.565.3-3 retitle 789946 libjenkins-java: has outdated maven dependency information affects 789946 + jenkins-instance-identity thanks This bug is actually in jenkins and is probably impacting several packages as well. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#789946: FTBFS: Failed to resolve artifact. Missing: org.jruby.extras:jffi:jar:debian
owner 789946 ! thanks I'll take care of this. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#789509: libjnr-posix-java: Please remove this package from the archive
Package: src:libjnr-posix-java Version: 1.1.8-3 Severity: serious This is mostly a reminder, remove this package since it has been superseded by jnr-posix. -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#789514: jaffl: Please remove this package from the archive
Package: src:jaffl Version: 0.5.9-8 Severity: serious This is mostly a reminder, remove this package since it has been superseded by jnr-ffi. -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#787562: jython FTBFS and jython is uninstallable because of unsatisfied (build-)dependency on libjnr-posix-java (= 3.0.10~)
tags 787562 + pending confirmed thanks On Tue, Jun 02, 2015 at 09:28:17PM +0200, Johannes Schauer wrote: Source: jython Version: 2.5.3-6 Severity: grave Justification: fails to build from source Hi, jython Build-Depends on libjnr-posix-java (= 3.0.10~) but the version of libjnr-posix-java in unstable is only 1.1.8-3. Here is the relevant dose3 output for the build failure: Hi Johannes, Thanks for the report, we are aware of the issue and we are waiting for FTPmaster jnr-posix approval to solve this bug and others. https://ftp-master.debian.org/new/jnr-posix_3.0.10-2.html Thanks, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784664: jenkins: FTBFS: error: package org.mindrot does not exist
prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche - Copying COW directory forking: rm -rf /var/cache/pbuilder/build//cow.22134 forking: cp -al /var/cache/pbuilder/base.cow /var/cache/pbuilder/build//cow.22134 I: removed stale ilistfile /var/cache/pbuilder/build//cow.22134/.ilist forking: chroot /var/cache/pbuilder/build//cow.22134 cowdancer-ilistcreate /.ilist find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i ' - Invoking pbuilder forking: pbuilder build --buildplace /var/cache/pbuilder/build//cow.22134 --buildresult /var/cache/pbuilder/result/ --debbuildopts --no-targz --internal-chrootexec chroot /var/cache/pbuilder/build//cow.22134 cow-shell /home/miguel/packages/jenkins/test/jenkins_1.565.3-3.dsc W: /root/.pbuilderrc does not exist I: Running in no-targz mode I: using fakeroot in build. I: pbuilder: network access will be disabled during build I: Current time: Thu May 7 12:37:46 ART 2015 I: pbuilder-time-stamp: 1431013066 I: copying local configuration I: mounting /proc filesystem I: mounting /run/shm filesystem I: mounting /dev/pts filesystem I: policy-rc.d already exists I: Obtaining the cached apt archive contents I: Installing the build-deps - Attempting to satisfy build-dependencies - Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: cdbs, debhelper (= 9), default-jdk (= 1:1.6), javahelper, maven-debian-helper, unzip, ant, ant-optional, groovy (= 1.8.6-4~), jenkins-ant-plugin, jenkins-antisamy-markup-formatter-plugin, jenkins-crypto-util, jenkins-executable-war (= 1.28), jenkins-instance-identity (= 1.3), jenkins-mailer-plugin, jenkins-matrix-auth-plugin, jenkins-matrix-project-plugin, jenkins-memory-monitor, jenkins-ssh-cli-auth, jenkins-task-reactor, jenkins-test-annotations (= 1.1), junit (= 3.8.2), junit4, libaccess-modifier-checker-java, libacegi-security-java, libakuma-java (= 1.8), libanimal-sniffer-java, libannotation-indexer-java (= 1.7), libantlr-java, libantlr-maven-plugin-java, libaopalliance-java, libargs4j-java, libasm4-java, libbridge-method-injector-java (= 1.9), libbytecode-compatibility-transformer-java, libcglib3-java, libclassworlds-java, libcommons-beanutils-java, libcommons-codec-java, libcommons-collections3-java, libcommons-digester-java, libcommons-fileupload-java (= 1.3), libcommons-httpclient-java, libcommons-io-java (= 2.4), libcommons-lang-java, libcommons-logging-java, libguice-java (= 4.0~beta5~), libjaxen-java, libjbcrypt-java (= 0.3-4~), libjellydoc-java, libjenkins-commons-jelly-java, libjenkins-commons-jexl-java (= 1.1-jenkins-20111212), libjenkins-htmlunit-java, libjenkins-json-java (= 2.4-jenkins-1), libjenkins-plugin-parent-java, libjenkins-remoting-java (= 2.43), libjenkins-trilead-ssh2-java (= 214-jenkins-1), libjenkins-winstone-java (= 0.9.10-jenkins-44), libjenkins-xstream-java (= 1.4.4-jenkins-3), libjffi-java, libjfreechart-java, libjmdns-java, libjna-java, libjnr-posix-java, libjson-java, libjsr305-java, libjstl1.1-java, libjtidy-java, liblocalizer-java, libmail-java, libmaven-antrun-extended-plugin-java, libmaven-assembly-plugin-java, libmaven-dependency-plugin-java, libmaven-embedder-java, libmaven-enforcer-plugin-java, libmaven-hpi-plugin-java (= 1.93), libmaven-install-plugin-java, libmaven-javadoc-plugin-java, libmaven-stapler-plugin-java (= 1.17), libmaven-war-plugin-java, libmaven2-core-java, libmetainf-services-java, libmockito-java, libpam4j-java, librobust-http-client-java, libservlet3.1-java, libsezpoz-java, libsisu-guice-java, libspring-aop-java, libspring-core-java, libspring-ldap-java, libspring-web-java, libstapler-adjunct-codemirror-java (= 1.3), libstapler-adjunct-timeline-java (= 1.4), libstapler-java (= 1.224), libtrilead-putty-extension-java (= 1.2), libtxw2-java, libxpp3-java, ttf-dejavu-core dpkg-deb: building package `pbuilder-satisfydepends-dummy' in `/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 12027 files and directories currently installed.) Preparing to unpack .../pbuilder-satisfydepends-dummy.deb
Bug#780703: closed by Markus Koschany a...@gambaru.de (eclipse-pydev fails to build from source)
On Sun, May 03, 2015 at 11:44:27AM +0200, Markus Koschany wrote: I just tried to rebuild eclipse-pydev but I get a different error now. libjnr-constants-java : Conflicts: libconstantine-java but 0.7-6 is to be installed. Unable to resolve dependencies! Giving up... The package build fine during the freeze and tony could successfully upload eclipse-pydev. My guess is that we probably need a build-dependency on python to make sure that all dependency resolvers pull in the right packages. But the current error is different from this. I'm pretty sure this new error about conflicting dependencies was caused by my yesterday uploads. Yesterday, I began to replace all dependencies on libconstantine-java with libjnr-constants-java in unstable. I couldn't finish this task because I need to upload jython release in experimental to unstable but that release is coupled with a new libjnr-posix-java upstream release (stuck in NEW right now). When I fix jython I'll go back to fix this package as well. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#784162: jenkins: FTBFS due to error with jsr305 missing maven artifact
the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.jsr-305 -DartifactId=jsr305 -Dversion=0.x -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.jsr-305 -DartifactId=jsr305 -Dversion=0.x -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.kohsuke.stapler:maven-stapler-plugin:maven-plugin:1.17 2) org.kohsuke.stapler:stapler:jar:debian 3) org.jsr-305:jsr305:jar:0.x -- 1 required artifact is missing. for artifact: org.kohsuke.stapler:maven-stapler-plugin:maven-plugin:1.17 from the specified remote repositories: repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/), central (https://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304) at org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComplete(DefaultPluginManager.java:835) at org.apache.maven.plugin.DefaultPluginManager.loadPluginFully(DefaultPluginManager.java:1629) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.loadPluginFully(DefaultLifecycleExecutor.java:1582) ... 16 more [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Sun May 03 17:10:32 UTC 2015 [INFO] Final Memory: 5M/90M [INFO] /usr/share/cdbs/1/class/maven.mk:87: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- System Information: Debian Release: 7.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche - Copying COW directory forking: rm -rf /var/cache/pbuilder/build//cow.2042 forking: cp -al /var/cache/pbuilder/base.cow /var/cache/pbuilder/build//cow.2042 I: removed stale ilistfile /var/cache/pbuilder/build//cow.2042/.ilist forking: chroot /var/cache/pbuilder/build//cow.2042 cowdancer-ilistcreate /.ilist find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i ' - Invoking pbuilder forking: pbuilder build --buildplace /var/cache/pbuilder/build//cow.2042 --buildresult /var/cache/pbuilder/result/ --debbuildopts --no-targz --internal-chrootexec chroot /var/cache/pbuilder/build//cow.2042 cow-shell /home/miguel/packages/jffi/test.clean/jenkins_1.565.3-3.dsc W: /root/.pbuilderrc does not exist I: Running in no-targz mode I: using fakeroot in build. I: pbuilder: network access will be disabled during build I: Current time: Sun May 3 13:55:28 ART 2015 I: pbuilder-time-stamp: 1430672128 I: copying local configuration I: mounting /proc filesystem I: mounting /run/shm filesystem I: mounting /dev/pts filesystem I: policy-rc.d already exists I: Obtaining the cached apt archive contents I: Installing the build-deps - Attempting to satisfy build-dependencies - Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: cdbs, debhelper (= 9), default-jdk (= 1:1.6), javahelper, maven-debian-helper, unzip, ant, ant-optional, groovy (= 1.8.6-4~), jenkins-ant-plugin, jenkins-antisamy-markup-formatter-plugin, jenkins-crypto-util, jenkins-executable-war (= 1.28), jenkins-instance-identity (= 1.3), jenkins-mailer-plugin, jenkins-matrix-auth-plugin, jenkins-matrix-project-plugin, jenkins-memory-monitor, jenkins-ssh-cli-auth, jenkins-task-reactor, jenkins-test-annotations (= 1.1), junit (= 3.8.2), junit4, libaccess-modifier-checker-java, libacegi-security-java, libakuma-java (= 1.8), libanimal-sniffer-java, libannotation-indexer-java (= 1.7), libantlr-java, libantlr-maven-plugin-java, libaopalliance-java, libargs4j-java, libasm4-java, libbridge-method-injector-java (= 1.9), libbytecode-compatibility-transformer-java
Bug#780703: closed by Markus Koschany a...@gambaru.de (eclipse-pydev fails to build from source)
On Wed, Mar 18, 2015 at 12:46:24PM +0100, Markus Koschany wrote: Hello, I have just rebuilt eclipse-pydev with git-buildpackage in a clean sid cowbuilder chroot and I cannot reproduce this build failure. The binary-indep target works as expected. GIT_PBUILDER_OPTIONS=--debbuildopts=-A DIST=sid ARCH=amd64 git-buildpackage I can reproduce this bug by simply grabbing the source package and trying to rebuild it with cowbuilder. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#780519: tomcat7 build failure
tags 780519 + confimed owner 780519 ! thanks On Fri, Mar 20, 2015 at 11:10:28AM +0100, Markus Koschany wrote: [...] and recompiled openjdk-7 from scratch. But tomcat7 still fails to build from source even with this older openjdk-7 version. I checked the failing unit tests and all of them seem to be related with SSL features. I'll try to upload a fix during this weekend. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#780519: tomcat7 build failure
On Thu, Mar 19, 2015 at 02:48:32PM +, Serge Hallyn wrote: Hi, when I try to build tomcat7 from source on a jessie host, I get several test failures. One of the test output files is attached - I'm afraid I have no idea how to read this. Can anyone explain what's actually broken? Hi Serge, I think nobody has researched yet what's this bug about but we are already aware of it and we are tracking it on #780519. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#780519: tomcat7: FTBFS due to failing tests
/output/build/logs for details, search for FAILED. Total time: 36 minutes 3 seconds debian/rules:62: recipe for target 'build-stamp' failed make: *** [build-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#780519: tomcat7: FTBFS due to failing tests
tags 780519 + jessie thanks It is also failing in jessie. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#780519: tomcat7: FTBFS due to failing tests
found 780519 7.0.28-4+deb7u1 thanks I also found I can't rebuild tomcat7 in stable due to failing unit tests. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#779621: jakarta-taglibs-standard: CVE-2015-0254
On Sat, Mar 14, 2015 at 02:03:52PM -0300, Miguel Landaeta wrote: the release cycle. I mean, the full diff between 2.1.1 and 2.1.3 has almost Sorry, I got it wrong. The new upstream releases are 1.2.1 and 1.2.3. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#779621: jakarta-taglibs-standard: CVE-2015-0254
On Sat, Mar 14, 2015 at 06:21:37PM +0100, Emmanuel Bourg wrote: Thank you for taking care of this Miguel. Upstream told me that the commits r1642442 [1] and r1642613 [2] contained the relevant fixes for this issue. I haven't checked if they can be easily backported though. Emmanuel Bourg [1] http://svn.apache.org/r1642442 [2] http://svn.apache.org/r1642613 Excellent Emmanuel, thanks for contacting upstream about this. That should ease the backporting significantly. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#779621: jakarta-taglibs-standard: CVE-2015-0254
owner 779621 ! thanks On Tue, Mar 03, 2015 at 07:57:36AM +0100, Moritz Muehlenhoff wrote: Package: jakarta-taglibs-standard Severity: important Tags: security Please see http://www.securityfocus.com/archive/1/534772 Cheers, Moritz Hi, I can try to backport the fix introduced in jakarta taglibs 2.1.3. However, I can't make promises that the result is even applicable to the outdated version we have in the archive (1.1.2). It looks like the diff is going to be really big for this late stage in the release cycle. I mean, the full diff between 2.1.1 and 2.1.3 has almost 7000 lines. Even if I carefully manage to successfully backport only the fix, the diff is going to be big. Upstream implemented the fix in a new class org.apache.taglibs.standard.util.XmlUtil with 389 LoC... I'll try to come up with something or report if I failed at that. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#779107: libgpars-groovy-java: FTBFS due to missing build dependency libjsr166y-java
owner 779107 ! thanks On Tue, Feb 24, 2015 at 05:17:30PM +0100, Markus Koschany wrote: Source: libgpars-groovy-java Version: 1.2.1-1 Severity: serious Hi, I have just discovered that libgpars-groovy-java 1.2.1-1 in unstable fails to build from source because one of its build-dependencies libjsr166y-java (1.7.0-1) is missing in unstable. It seems it ought to be uploaded to unstable at some time, but perhaps it is better to do this after the freeze ends. Thanks for reporting it. I wonder why a new upstream release of gpars was uploaded to unstable during the freeze and how it was built in the first place. Anyway, you are correct Markus, the dependency on that libjsr166y-java version is needed and I believe it's better to fix this in unstable after the freeze ends. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#768621: nanoc: FTBFS in jessie: ERROR: Test ruby2.1 failed: Running tests for ruby2.1 using debian/ruby-tests.rb...
tags 768621 + unreproducible moreinfo thanks On Sat, Nov 08, 2014 at 06:44:10PM +0100, Lucas Nussbaum wrote: Source: nanoc Version: 3.7.3-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Hi, It looks like I'm going to need to setup sbuild in the same way how is used by debian-qa team to check all the packages. Lucas, is there a simple document or a howto to get up to speed with sbuild? I always used cowbuilder and I'm unable to reproduce some of the latest FTBFS bug related to failed unit tests. I'm tagging it unreproducible but please let me know if somebody else can reproduce this. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#768959: FTBS: Errors out in tests with ruby 2.1
tags 768959 + unreproducible moreinfo thanks On Mon, Nov 10, 2014 at 12:44:42PM +0100, Sjoerd Simons wrote: Package: ruby-simplecov Version: 0.7.1 Severity: serious When rebuilding ruby-simplecov: Running tests for ruby2.1 using debian/ruby-tests.rake ... /usr/bin/ruby2.1 -Ilib:test -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb test/test_1_8_fallbacks.rb test/test_command_guesser.rb test/test_deleted_source.rb test/test_file_list.rb test/test_filters.rb test/test_merge_helpers.rb test/test_result.rb test/test_return_codes.rb test/test_source_file.rb test/test_source_file_line.rb Hi Sjoerd, I can't reproduce this with cowbuilder (jessie chroot). Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#768723: pry: FTBFS in jessie: ERROR: Test ruby2.1 failed: Bacon::Error: /\* $/.===([1] pry(main)* ) failed
tags 768723 + unreproducible moreinfo thanks On Sun, Nov 09, 2014 at 08:24:43AM +0100, Lucas Nussbaum wrote: Source: pry Version: 0.10.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. I can't reproduce this failure in a jessie chroot. Could somebody confirm this? Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#766068: RFS: robocode 1.6.2+dfsg2-1 [ITA] [RC]
On Mon, Oct 20, 2014 at 11:58:06PM +0200, Markus Koschany wrote: Hi all, I have recently adopted Robocode, a Java programming game, and I think [...] Hi Markus, I'll take care of it. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#758972: Mojarra update 2.2.8
On Wed, Sep 17, 2014 at 11:37:35AM +0200, Markus Koschany wrote: Could you push your changes to Git please? I pushed a branch named 2.2.8 to the git repo. This branch is nowhere near to be uploaded. To build it, you will need to add javaee-api-7.0.jar to the classpath. However, this is FTBFS for me. It would be great if you can try to build it. However, as I said previously 2.2.8 introduces a new dependency on Java EE 6/7 APIs but I found out some issues with the APIs source licensing. According to http://central.maven.org/maven2/javax/javaee-api/7.0/javaee-api-7.0.pom that code is dual licensed under GPLv2 and CDDL. However there are some .java files in the source with confidential clauses and some weird non-free disclaimers. Maybe those disclaimers are outdated, I have to confirm this and if everything is OK, then get that package in the archive. I have written a new debian/copyright file and pushed it to experimental. Maybe you can use it as a starting point for the final release. I can confirm what you wrote. There is at least jsf-ri/systest-per-webapp/process-as-jspx/src/java/Blink.java which is non-free according to its license terms. I believe the other clauses are O.K. They are licensed under the GPL-2 with classpath exception or the CDDL and some files contain code fragments once licensed under Apache 2.0 Oh, I was talking about JavaEE API 7.0 source code. That Blink.java file can be removed from sources if needed. If you need some help, please feel free to ping me. Yep, I need help with this because I have not much free time in the last weeks and freeze deadline is approaching. Let me know if we can meet on irc, or we can continue via email as usual. I'll be working on this package (and the JavaEE one) this weekend. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#758972: Mojarra update 2.2.8
On Sat, Sep 27, 2014 at 06:44:47PM -0300, Miguel Landaeta wrote: Yep, I need help with this because I have not much free time in the last weeks and freeze deadline is approaching. Looking more closely at this I noticed the only package in Debian depending on mojarra packages is libspring-java. libspring-java build-depends only on libjsf-api-java. mojarra also provides libjsf-impl-java but there are not packages in Debian depending on this package. I already checked javax.faces 2.2 API and is compatible with 2.0 and libspring-java build doesn't break with the new mojarra version, so I'm going to upload a new mojarra package very soon but only providing the API. Given the deadlines and since this solution doesn't break anything available in Debian I think is a good approach. I'm going to combine our two branches and prepare the new upload. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#740586: (no subject)
unblock 759163 by 759131 tags 759163 + pending tags 758972 + pending tags 740586 + pending tags 677194 + pending tags 749206 + pending tags 759634 + pending tags 738110 + pending thanks A fix for all these bugs is already committed to the git repo and it will be uploaded soon. I need to check some pending issues with the maintainer that prepared this upload. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#762262: turpial: fails to load
severity 762262 normal tags 762262 + moreinfo unreproducible thanks On Sat, Sep 20, 2014 at 11:04:16AM +0100, Sharon Kimble wrote: Package: turpial Version: 3.0+dfsg-1 Severity: grave Justification: renders package unusable [...] And it fails to load, and is therefore unusable and broken! Hi Sharon, I can't reproduce this bug in sid or jessie installations. As Jakub indicated, this looks like some local issue due to Python libraries installation outside the distribution. Nothing wrong with that, but please make sure this is not interfering with Turpial dependencies. I'm downgrading the severity of this bug and I'd like if you can retry and confirm if there is really an issue with Turpial. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#750348: libturpial: FTBFS: Trying to write outside builddir
retitle 750348 libturpial: unit tests are trying to write outside builddir severity 750348 important thanks On Thu, Jul 31, 2014 at 06:16:58PM -0300, Miguel Landaeta wrote: [...] I'm looking for help to get a fix or workaround for this issue. I decided to disable the unit tests during build time and prepared a new upload (1.7.0-3) with this change. I'm downgrading the severity of this bug since libturpial is not going to FTBFS but I keep the bug open because this is not a proper fix. This is a workaround, so libturpial can migrate to testing and can be included in jessie. The units tests must not write outside the builddir and they must pass to be able to close this bug report. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#758972: Mojarra update 2.2.8
I keep working on this. So far, I was able to build 2.2.8 in Debian and this should fix all the serious bugs with this packages. I did this simplifying the build and replacing ant with javahelper. Another option is to keep using ant since Markus did some work in a branch. However, as I said previously 2.2.8 introduces a new dependency on Java EE 6/7 APIs but I found out some issues with the APIs source licensing. According to http://central.maven.org/maven2/javax/javaee-api/7.0/javaee-api-7.0.pom that code is dual licensed under GPLv2 and CDDL. However there are some .java files in the source with confidential clauses and some weird non-free disclaimers. Maybe those disclaimers are outdated, I have to confirm this and if everything is OK, then get that package in the archive. Another option is to check if some mojarra features depending on those APIs can be disabled. I'll post again when I have more info. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#758972: Mojarra update 2.2.8
Hi Markus, I can take a look at your changes but not right now since I'm in vacation right now. I'll check this during the next week since I know this is a very pressing issue and the clock is ticking for the next release. Thanks for taking a look at this. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#758972: Mojarra update 2.2.8
On Mon, Aug 25, 2014 at 01:41:15PM +0200, Markus Koschany wrote: I see that we are now working with three people on this issue. :) I've pushed some small changes. Please let me know if you agree with the updated get-orig-source target and if we should use upstream's SVN repository from now on. I couldn't find a source tarball for 2.2.8. I'm OK with that. I noticed mojarra source jars in Maven central repository are incomplete because don't contain some needed files (e.g. .dtd, .properties, .xsd, etc). So, maybe the best option is to switch to upstream's SVN as you said. I'm now going to rebase your debian-build patch. Perhaps some of those dependencies can be avoided. I'll take care of the missing B-D on JavaEE 6.0/7.0 API. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#758972: Mojarra update 2.2.8
On Sat, Aug 23, 2014 at 07:22:37PM +0200, Markus Koschany wrote: I will investigate whether an update to 2.2.8 can resolve the issues with mojarra. I'll report back as soon as it's done. I'm pretty sure 2.2.8 would resolve almost all the outstaing issues. However, after inspecting 2.2.8 I found it B-D on Java EE 6 APIs (e.g. javax.enterprise.context) and AFAICT they are not available in Debian yet. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#758972: Mojarra update 2.2.8
On Sat, Aug 23, 2014 at 07:22:37PM +0200, Markus Koschany wrote: Control: owner -1 ! Hi, I will investigate whether an update to 2.2.8 can resolve the issues with mojarra. I'll report back as soon as it's done. Markus Hi Markus, I just had a very quick chat with Tony today (here @DebConf) about this bug. I reviewed 2.2.8 release and its packaging looks simpler than 2.0.x releases. If you have a fix and need sponsoring just let me know. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#750348: libturpial: FTBFS: Trying to write outside builddir
tags 750348 + confirmed help upstream forwarded 750348 turpial-...@googlegroups.com thanks On Mon, Jun 02, 2014 at 08:59:10PM +0200, David Suárez wrote: Source: libturpial Version: 1.7.0-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140601 qa-ftbfs Justification: FTBFS on amd64 Hi folks, I'm looking for help with this bug. For full context, please take a look at: * https://bugs.debian.org/750348 * http://aws-logs.debian.net/ftbfs-logs/2014/06/01/libturpial_1.7.0-2_unstable.log What is happening here is: a Debian autobuilder is unable to build libturpial from source. This is a serious bug and has caused to get turpial dropped from testing. The autobuilder is failing because libturpial unit tests are trying to write in the homedir of the user who is running the build and this violates Debian guidelines (a package should not try to write outside its builddir). I was hacking the unit tests but I'm unable to get a reasonable fix for this issue. The files with problematic unit tests are: * tests/test_column_manager.py * tests/test_account_manager.py * tests/test_core.py I stumbled upon these two situations: * I tried to pass an explicit basedir to libturpial.config.AppConfig constructor to override the default basedir pointing to the homedir of the user running libturpial. I did this on tests/test_column_manager.py and tests/test_account_manager.py. * On tests/test_core.py I noticed that I can't specify an explicit basedir when you create an instance of libturpial.api.core.Core, so this is going to try to create ~user/.config/turpial. I'm looking for help to get a fix or workaround for this issue. Thanks, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#755333: [pkg-eucalyptus-maintainers] Bug#755333: wsdl2c: FTBFS: [javac] /«PKGBUILDDIR»/src/org/apache/axis2/builder/MultipartFormDataBuilder.java:28: error: package javax.servlet.http does not exi
tags 755333 + patch thanks On Mon, Jul 21, 2014 at 07:15:08PM +0900, Charles Plessy wrote: Hello everybody, I received a bug report that the wsdl2c package started to fail to build from source (see below). Hi Charles, This is just about a missing jar file in the classpath of the compilation. You'll find a fix for this bug attached to this email. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche diff -Nru wsdl2c-0.1/debian/changelog wsdl2c-0.1/debian/changelog --- wsdl2c-0.1/debian/changelog 2012-10-04 17:16:26.0 -0300 +++ wsdl2c-0.1/debian/changelog 2014-07-22 13:24:01.0 -0300 @@ -1,3 +1,9 @@ +wsdl2c (0.1-3) unstable; urgency=low + + * Add servlet-api-3.0 jar to compilation classpath. (Closes: #755333). + + -- Miguel Landaeta nomad...@debian.org Tue, 22 Jul 2014 13:21:45 -0300 + wsdl2c (0.1-2) unstable; urgency=low * Added patch from Colin Watson to force utf-8 encoding which is required diff -Nru wsdl2c-0.1/debian/rules wsdl2c-0.1/debian/rules --- wsdl2c-0.1/debian/rules 2012-06-23 04:07:09.0 -0300 +++ wsdl2c-0.1/debian/rules 2014-07-22 13:25:42.0 -0300 @@ -6,4 +6,4 @@ REQUIRED_JVM_VERSION := 1.5 JAVA_HOME:= /usr/lib/jvm/default-java DEB_ANT_BUILDFILE:= build.xml -DEB_JARS := commons-logging wsdl4j backport-util-concurrent gnumail httpcore jaxen commons-fileupload commons-cli geronimo-jms_1.1_spec commons-httpclient httpcore-nio +DEB_JARS := commons-logging wsdl4j backport-util-concurrent gnumail httpcore jaxen commons-fileupload commons-cli geronimo-jms_1.1_spec commons-httpclient httpcore-nio servlet-api-3.0 signature.asc Description: Digital signature
Bug#754643: gradle: FTBFS: Caused by: java.lang.RuntimeException: Could not determine the local IP addresses for this machine.
On Tue, Jul 15, 2014 at 08:20:50AM +0200, gregor herrmann wrote: On 07/12/2014 08:21 PM, Miguel Landaeta wrote: Is it possible that it's trying to make a connection to your X server? (Without having looked at the package:) Maybe this is yet another instance of #753944 (pbuilder: USENETWORK=no breaks package builds). Uhm, this is weird because I tried to build gradle during the last weekend and I already had installed pbuilder 0.215+nmu3 with the fix for #753944. Today I updated my development box again and this bug is not present anymore or so it seems. I'll do a couple of extra check and I'll close this if I can't reproduce it anymore. Thanks for the pointers. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#751058: pychef: FTBFS - URLError: urlopen error [Errno -2] Name or service not known
tags 751058 + pending forwarded 751058 https://github.com/coderanger/pychef/issues/31 thanks On Mon, Jun 09, 2014 at 09:21:09PM +0100, Michael Tautschnig wrote: I'm not sure whether this test expects any network connectivity!? The full build log is attached, but please do let me know if the problem happens to be unreproducible. Hi, Many unit tests for this library depend on network connectivity with https://api.opscode.com/organizations/pycheftest. I decided to disable those tests but this is not the correct solution for this issue. Maybe upstream can set up a chef-zero server and perform the tests against that. I'll forward this issue to them. I'm uploading a new package now. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#754643: gradle: FTBFS: Caused by: java.lang.RuntimeException: Could not determine the local IP addresses for this machine.
) at org.gradle.api.internal.tasks.compile.NormalizingGroovyCompiler.delegateAndHandleErrors(NormalizingGroovyCompiler.java:99) at org.gradle.api.internal.tasks.compile.NormalizingGroovyCompiler.execute(NormalizingGroovyCompiler.java:48) at org.gradle.api.internal.tasks.compile.NormalizingGroovyCompiler.execute(NormalizingGroovyCompiler.java:34) at org.gradle.api.internal.tasks.compile.DelegatingGroovyCompiler.execute(DelegatingGroovyCompiler.java:29) at org.gradle.api.internal.tasks.compile.DelegatingGroovyCompiler.execute(DelegatingGroovyCompiler.java:20) at org.gradle.api.internal.tasks.compile.IncrementalJavaCompilerSupport.execute(IncrementalJavaCompilerSupport.java:33) at org.gradle.api.internal.tasks.compile.IncrementalJavaCompilerSupport.execute(IncrementalJavaCompilerSupport.java:23) at org.gradle.api.tasks.compile.GroovyCompile.compile(GroovyCompile.java:77) at org.gradle.api.internal.BeanDynamicObject$MetaClassAdapter.invokeMethod(BeanDynamicObject.java:216) at org.gradle.api.internal.BeanDynamicObject.invokeMethod(BeanDynamicObject.java:122) at org.gradle.api.internal.CompositeDynamicObject.invokeMethod(CompositeDynamicObject.java:147) at org.gradle.api.tasks.compile.GroovyCompile_Decorated.invokeMethod(Unknown Source) at org.gradle.util.ReflectionUtil.invoke(ReflectionUtil.groovy:23) at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$4.execute(AnnotationProcessingTaskFactory.java:161) at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$4.execute(AnnotationProcessingTaskFactory.java:156) at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:510) at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:499) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:64) ... 71 more Caused by: java.lang.NullPointerException at org.gradle.messaging.remote.internal.inet.InetAddressFactory.init(InetAddressFactory.java:119) at org.gradle.messaging.remote.internal.inet.InetAddressFactory.findLocalAddresses(InetAddressFactory.java:70) ... 96 more BUILD FAILED [snip] -- System Information: Debian Release: 7.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche gradle_1.5-1_amd64.build.gz Description: Binary data signature.asc Description: Digital signature
Bug#750303: (no subject)
reassign 750303 src:stapler 1.218-1 forcemerge 750303 750273 thanks This bug was caused by stapler. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#750267: Bug introduced with groovy 1.8.6-4
owner 750267 ! owner 750273 ! owner 750279 ! owner 750303 ! owner 750309 ! thanks Hi, I was aware of these bugs but I didn't manage to upload the fixes on time. I'll take care of this. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#749206: mojarra: FTBFS: Build-deps are uninstallable due to libtomcat{6,7}-java conflict
Package: src:mojarra Version: 2.0.3-3 Severity: serious Justification: fails to build from source (but built successfully in the past) This package FTBFS in a clean sid chroot with this error: The following packages have unmet dependencies: libtomcat7-java : Conflicts: libtomcat6-java but 6.0.41-1 is to be installed. Unable to resolve dependencies! Giving up... The full build log is attached. -- System Information: Debian Release: 7.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche mojarra_2.0.3-3_amd64.build.gz Description: Binary data signature.asc Description: Digital signature
Bug#744330: groovy: makes xbmc FTBFS
clone 744330 -1 retitle -1 groovy: groovy-all.jar is broken due changes introduced with jarjar 1.4 reassign -1 groovy severity -1 serious thanks On Mon, Apr 28, 2014 at 01:48:26PM +0200, Balint Reczey wrote: Hi Miguel, Hi Bálint, Thank you for triaging this bug. Building XBMC using groovy.jar succeeded. I will update xbmc in unstable and experimental closing this bug. If you would like to prevent groovy from migrating to testing please clone this bug or open a new RC bug against it. No problem. I already cloned this bug report to keep blocking groovy 1.8.6-2 from reaching testing. I will wait two days for you giving green light before the uploads. Go ahead. It's good to know groovy is not totally broken. In the meantime, your packages are going to work if you don't depend on groovy-all.jar. I expected to fix this in 1.8.6-3. Cheers, PS. I'll contact you later to get more info about #733234. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#744337: gradle: FTBFS: java.lang.OutOfMemoryError: Java heap space
I identified the root cause of this bug in libjarjar-java. For more details, please look at #745815. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#744330: groovy: makes xbmc FTBFS
Hi Bálint, Can you retry your xbmc build on unstable changing the classpath used with groovy command? I'm able to reproduce errors like yours when I include groovy-all.jar in the classpath but not when I use groovy.jar. Examples: miguel@nina:~/packages/gradle/gradle-1.4$ groovy -cp /usr/share/java/groovy-1.8.6.jar -e 'println 1' 1 miguel@nina:~/packages/gradle/gradle-1.4$ groovy -cp /usr/share/java/groovy-all-1.8.6.jar -e 'println 1' java.lang.OutOfMemoryError: Java heap space at java.util.ArrayList.init(ArrayList.java:144) at org.codehaus.groovy.reflection.GeneratedMetaMethod$DgmMethodRecord.loadDgmInfo(GeneratedMetaMethod.java:193) at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.registerMethods(MetaClassRegistryImpl.java:155) at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.init(MetaClassRegistryImpl.java:83) at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.init(MetaClassRegistryImpl.java:61) at groovy.lang.GroovySystem.clinit(GroovySystem.java:29) at org.codehaus.groovy.runtime.InvokerHelper.clinit(InvokerHelper.java:49) at groovy.lang.GroovyObjectSupport.init(GroovyObjectSupport.java:32) at groovy.lang.Binding.init(Binding.java:34) at groovy.lang.GroovyShell.init(GroovyShell.java:70) at groovy.ui.GroovyMain.processOnce(GroovyMain.java:544) at groovy.ui.GroovyMain.run(GroovyMain.java:337) at groovy.ui.GroovyMain.process(GroovyMain.java:323) at groovy.ui.GroovyMain.processArgs(GroovyMain.java:120) at groovy.ui.GroovyMain.main(GroovyMain.java:100) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java:108) at org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:130) 1 Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#744330: groovy: makes xbmc FTBFS
I suspect the recent breakage in groovy could be caused by changes in libjarjar-java since that tool is used to manipulate groovy-all jar and had a new upstream release in the archive after wheezy release. I'll continue debugging this later. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#744992: python-falcon and python-libturpial: error when trying to install together
tags 744992 + confirmed thanks On Thu, Apr 17, 2014 at 09:56:09AM +0200, Jakub Wilk wrote: Source: python-falcon,python-libturpial Version: python-falcon/0.1.8-1 Version: python-libturpial/1.7.0-1 Severity: serious python-falcon and python-libturpial cannot be co-installed: It's my bad for polluting the filesystem this way. I should have noticed it earlier. I'll fix this ASAP. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#744330: groovy: makes xbmc FTBFS
tags 744330 + confirmed thanks On Sun, Apr 13, 2014 at 02:25:44AM +0200, Bálint Réczey wrote: Package: groovy Version: 1.8.6-2 Severity: serious Hi, Xbmc stopped building with latest groovy upload even with the workaround for another groovy bug. :-( Hi, I'm investigating this since I did the last groovy upload to unstable with the goal of enabing support for Java 8. Gradle is also broken (#744337) probably due to the same reason. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#744337: gradle: FTBFS: java.lang.OutOfMemoryError: Java heap space
: unmounting dev/pts filesystem I: unmounting run/shm filesystem I: unmounting proc filesystem - Cleaning COW directory forking: rm -rf /var/cache/pbuilder/build//cow.21460 -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#744337: gradle: FTBFS: java.lang.OutOfMemoryError: Java heap space
I forgot to include the complete failed log. This bug could be related to groovy 1.8.6-2 upload that I did recently. On #744330 is also reported some breakage on xbmc related to groovy. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche gradle_1.4-2_amd64.build.gz Description: Binary data signature.asc Description: Digital signature
Bug#735763: svnkit is marked for autoremoval from testing
Hi Markus, On Sat, Apr 05, 2014 at 12:47:52PM +0200, Markus Koschany wrote: On 03.04.2014 15:34, Miguel Landaeta wrote: I'll review it and upload it to DELAYED/5 if everything is OK. I just uploaded trilead-ssh2 to DELAYED/5. that would be great. Please go ahead and let me know if there is something that should be changed. I modified your NMU to also install Maven artifacts for this library. I'm going to eventually need that. If Matthew gives his consent, we can move trilead-ssh2 to debian-java as you said. I'm in favour of it but of course it's up to Matthew to decide. Let's wait for him. In the meantime I'm going to review your changes to svnkit. Thanks for taking the time to fixing these packages. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#735763: svnkit is marked for autoremoval from testing
On Sat, Apr 05, 2014 at 10:43:02AM -0300, Miguel Landaeta wrote: In the meantime I'm going to review your changes to svnkit. Hi again, I just uploaded svnkit 1.8.5+dfsg-1 to DELAYED/5 so it can enter to the archive in combination with updated trilead-ssh2 package. As comment, I had quite long time without working on this package so I noticed how Ant build file has evolved during these years. We can keep using that to build this package because it works but upstream switched to Gradle so I think eventually we are going to remove this divergence from upstream and just use Gradle as well. This looks like a task post-jessie anyway. Thanks for taking care of this packages Markus. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#735763: svnkit is marked for autoremoval from testing
On Wed, Apr 02, 2014 at 07:00:35PM +0200, Markus Koschany wrote: I have tested all reverse dependencies of svnkit and they seem to work. Only netbeans could not be tested because it's affected by another RC bug. Hi Markus, Since Matthew tagged his packages with LowThresholdNmu and trilead-ssh2 doesn't get an update since 4 years ago or so I think we can upload it. I'll review it and upload it to DELAYED/5 if everything is OK. If Matthew gives his consent, we can move trilead-ssh2 to debian-java as you said. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#741604: libspring-java: Multiple security issues
owner 741604 ! tags 741604 + confirmed thanks On Fri, Mar 14, 2014 at 01:24:47PM +0100, Moritz Muehlenhoff wrote: Package: libspring-java Severity: grave Tags: security Justification: user security hole http://www.gopivotal.com/security/cve-2014-0054 http://www.gopivotal.com/security/cve-2014-1904 I'm not sure whether these are worth a DSA? Hi Moritz, I believe a DSA is not necessary for those CVEs. I'm preparing fixes for sid and stable. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
