Bug#807645: ifupdown package fails to configure itself (by dpkg)

On Fri, Dec 11, 2015 at 10:16:18AM +0100, Vincent Danjean wrote: > Executing /lib/systemd/systemd-sysv-install enable networking > done 0 > Failed to execute operation: File exists > dpkg: error processing package ifupdown (--configure): > subprocess installed post-installation script returned

Bug#807655: tripwire: segfaults during installation in i386 (chroot on amd64 host)

Package: tripwire Version: 2.4.2.2-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. This bug

Bug#807659: libgettext-commons-java: FTBFS: Error resolving version for plugin 'org.apache.maven.plugins:maven-eclipse-plugin'

Source: libgettext-commons-java Version: 0.9.6-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, libgettext-commons-java fails to build from

Bug#807660: jenkins-winstone: FTBFS: jenkins-winstone-2.8/target/test-classes does not exist

Source: jenkins-winstone Version: 2.8-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, jenkins-winstone fails to build from source in

Bug#807662: mrpt-common: fails to upgrade from 'jessie' - trying to overwrite /usr/share/mrpt/config_files/simul-beacons/example_simul-beacons.ini

Package: mrpt-common Version: 1:1.3.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + mrpt-apps Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to 'stretch' fails

Bug#807617: FTBFS due to test-suite failures

On Thu, Dec 10, 2015 at 11:41:06PM +0100, Michael Biebl wrote: > Since version 0.8, the test-suite basically fails on all architectures > as can be seen at > https://buildd.debian.org/status/package.php?p=ifupdown=unstable > > I can reproduce the problem on amd64 with a pbuilder build. > >From a

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

Hi Adrian, > If you like, you can send me a debdiff with your changes and I can > quickly review it and test-build it on one of the buildds. here is a new version of the debdiff. I have included the differences of armhf and armel architechture into the libechonest2.3.symbol file. I hope I have

Bug#807507: removal of libechonest2.1

Hello, > which, besides a date from the future, lacks a vital line: > * Drop bogus libechonest2.1 (Closes: #807507) > > Thus, I'm hereby closing this manually. > > 2.3.1-0.1 does break its users, but fortunately there's only one such user, > clementine. I've just requested a rebuild of it

Processed: mrpt-common: fails to upgrade from 'jessie' - trying to overwrite /usr/share/mrpt/config_files/simul-beacons/example_simul-beacons.ini

Processing control commands: > affects -1 + mrpt-apps Bug #807662 [mrpt-common] mrpt-common: fails to upgrade from 'jessie' - trying to overwrite /usr/share/mrpt/config_files/simul-beacons/example_simul-beacons.ini Added indication that 807662 affects mrpt-apps -- 807662:

Bug#807657: dvdauthor: FTBFS: compat.h:141:8: error: expected identifier or '(' before '__extension__'

Source: dvdauthor Version: 0.7.0-1.3 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, dvdauthor fails to build from source in unstable/amd64:

Bug#807650: mercurial-crecord: incompatible with mercurial 3.6

Package: mercurial-crecord Version: 0.20140626-1 Severity: serious Tags: sid stretch User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid because mercurial 3.6.1-1 added a Breaks against it: mercurial

Bug#807647: perl/experimental: trigger cycle on upgrades

Package: perl Version: 5.22.1~rc4-1 Severity: serious Tags: patch When spamassassin is installed, upgrading perl et al. from sid/5.20 to experimental/5.22.1~rc4-1 breaks due to a trigger cycle, see below. I believe perl.postinst should trigger 'perl-major-upgrade' with 'noawait'. Quoting

Processed (with 6 errors): Fixed in sid too

Processing commands for cont...@bugs.debian.org: > unarchive 673038 Bug #673038 {Done: Michael Gilbert } [slapd] slapd: slapcat output truncated every now and then Unarchived Bug 673038 > fixed -1 2.4.39-1 Failed to add fixed on -1: The 'bug' parameter ("-1") to

Bug#807502: gcc-avr: Missing support for atxmega

Hej, this may be a broader issue. I must confirm this bug for the x32e5 as well. Stepping gcc-avr back to testing helps for the meanwhile. The complained files do not exist in earlier versions. So either this may be a problem of a new feature or some odd configuration. GOOD LUCK, I have no

Bug#807675: dcmtkpp: FTBFS: SCU Failed: 0006:0213 Data dictionary missing

Source: dcmtkpp Version: 0.3.1-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, dcmtkpp fails to build from source in unstable/amd64: [..]

Bug#807664: python3-cap-ng: Python3 import error: undefined symbol: capng_print_caps_numeric

Package: python3-cap-ng Version: 0.7.7-1 Severity: grave Justification: renders package unusable Hi, The Python3 library doesn't work at all. A simple import causes an import error: $ cat test.py #!/usr/bin/python3 import capng $ python3 test.py Traceback (most recent call last): File

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

Hi, first of all, thank you for your help, both of you! I also learned a lot from this experience. > e.g. a symbol was leftover in symbols file: > + _ZN8Echonest12AudioSummary12setTimestampEf@Base 2.1.0 > and was preventing amd64 and i386 builds to succeed. You are right, it seems that I have

Bug#807672: natlog: FTBFS: [/usr/bin/icmbuild, line 166] Error: idx undefined

Source: natlog Version: 1.02.00-4 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, natlog fails to build from source in unstable/amd64: [..]

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

(Sorry for the slightly asynchronous reply, I got interrupted) On 12/11/2015 03:01 PM, Gianfranco Costamagna wrote: > this is *exactly* the reason for trying all yesterday evening to get it > working :) > (pbuilder now fails under qemu and arm*, probably because of the new > aptitude, so I had

Bug#807673: perspectives-extension: FTBFS: ValueError: empty namespace prefix is not supported in ElementPath

Source: perspectives-extension Version: 4.6.2-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, perspectives-extension fails to build from

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

Hi, > anyway, I still get issues with armhf and armel, but this time they seem to > be related > to one symbols wrong copy-pasted on line 249 > _ZN8Echonest4Term9setWeightEf@Base instead of > _ZN8Echonest4Term12setFrequencyEf@Base Hmm, it looks like I'm too unconsecrated. Fixed. > and

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

Hi again, >Btw, Stefan noticed that armel and armhf seem to have completely >different symbol tables as the types for many of the function >symbols are changed from double to float. > >Did you verify that? this is *exactly* the reason for trying all yesterday evening to get it working :)

Bug#807647: marked as done (perl/experimental: trigger cycle on upgrades)

Your message dated Fri, 11 Dec 2015 12:49:41 + with message-id and subject line Bug#807647: fixed in perl 5.22.1~rc4-2 has caused the Debian Bug report #807647, regarding perl/experimental: trigger cycle on upgrades to be marked as done. This means that

Bug#768651:

$850,000 was donated to you reply to ( hawil6...@mediacombb.net ) for details.

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

I'm looking at it soon. I already have a look yesterday, but I had issues with some arm platforms. Now I should have time to finish it. cheers, G. Il Venerdì 11 Dicembre 2015 10:27, Stefan Ahlers ha scritto: Hi Adrian, > If you like, you can send me a debdiff

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

On 12/11/2015 02:36 PM, Gianfranco Costamagna wrote: > I'm looking at it soon. You don't have to. Stefan has already made a proposed change which I will testbuild later today or tomorrow. I'm just still at work :). Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer -

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

On 12/11/2015 02:56 PM, Gianfranco Costamagna wrote: > I have a build ongoing right now in amd64 i386 arm64 armel armhf powerpc. Sounds good. > the builds seems fine, at least I had to tweak a little bit the symbols and > change something in changelog Ok, good. > e.g. a symbol was leftover in

Bug#802665: augeas-lenses: httpd lens is broken in 1.2

On Tue, 27 Oct 2015 13:37:46 + Dominic Cleal wrote: > On 22/10/15 11:52, Erebus wrote: > > Package: augeas-lenses > > Version: 1.2.0-0.2 > > Severity: serious > > Justification: httpd lens is broken in 1.2 > > > > Dear Maintainer, > > > > I have learned that

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

Hi, >You are right, it seems that I have forgotten this line to exclude for >the other architecture, sorry. But now it looks good for me, too! nope, the lines was already splitted, just just forgot to delete it. now you have twice that symbol. anyway, I still get issues with armhf and armel,

Bug#807675: More failures apparently unrelated to "SCU Failed: 0006:0213 Data dictionary missing"

After fixing dcmtk (uploading right now) there are still failures: On one hand, during the build I get: cd build && ../tests/run.sh F: cannot initialize network: 0006:031c TCP Initialization Error: Address already in use E: Store Failed, file: dcmtkpp.iZA/data.dcm: E: 0006:0317 Peer aborted

Bug#807502: gcc-avr: Missing support for atxmega

Please do. It might be that we need to update avr-libc too? That work is in progress, but was delayed. Should be ready any day now... On Fri, Dec 11, 2015 at 3:57 PM, Lisandro Damián Nicanor Pérez Meyer < perezme...@gmail.com> wrote: > Then I would prefer to raise the severity to serious, are

Bug#807589: marked as done (libechonest: FTBFS on all architectures due to mismatched symbols file(s))

Your message dated Fri, 11 Dec 2015 15:53:09 + with message-id and subject line Bug#807589: fixed in libechonest 2.3.1-0.3 has caused the Debian Bug report #807589, regarding libechonest: FTBFS on all architectures due to mismatched symbols file(s) to be

Processed: DCMDICTPATH is not set properly in dcmtk

Processing commands for cont...@bugs.debian.org: > block 807675 by 807691 Bug #807675 [src:dcmtkpp] dcmtkpp: FTBFS: SCU Failed: 0006:0213 Data dictionary missing 807675 was not blocked by any bugs. 807675 was not blocking any bugs. Added blocking bug(s) of 807675: 807691 > thanks Stopping

Processed: Re: Bug#807666: nmu: mpich_3.1-6

Processing control commands: > reassign -1 src:mpich Bug #807666 [release.debian.org] nmu: mpich_3.1-6 Bug reassigned from package 'release.debian.org' to 'src:mpich'. Ignoring request to alter found versions of bug #807666 to the same values previously set Ignoring request to alter fixed

Bug#807502: gcc-avr: Missing support for atxmega

On Friday 11 December 2015 16:15:52 Hakan Ardo wrote: > Please do. Done, thanks! > It might be that we need to update avr-libc too? That work is in > progress, but was delayed. Should be ready any day now... It might be, if so just ping me as soon as it's available in incoming.d.o and I'll

Processed: severity of 791964 is important

Processing commands for cont...@bugs.debian.org: > severity 791964 important Bug #791964 [gdm3] gdm3: upgrade causes X session to be terminated Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 791964:

Bug#807507: marked as done (libechonest2.1: Missing libechonest.so.2.1)

Your message dated Fri, 11 Dec 2015 15:53:09 + with message-id and subject line Bug#807507: fixed in libechonest 2.3.1-0.3 has caused the Debian Bug report #807507, regarding libechonest2.1: Missing libechonest.so.2.1 to be marked as done. This means that

Processed: Re: Bug#807502: gcc-avr: Missing support for atxmega

Processing commands for cont...@bugs.debian.org: > severity 807502 serious Bug #807502 [gcc-avr] gcc-avr: Missing support for atxmega384d3 since last upload Ignoring request to change severity of Bug 807502 to the same value. > thanks Stopping processing here. Please contact me if you need

Bug#732723: cegui-mk2: Please upgrade OGRE dependency to 1.9 when upstream ready

Am Montag, den 05.10.2015, 11:28 +0200 schrieb Muammar El Khatib: > On Sun, Sep 27, 2015 at 8:42 PM, Tobias Frost > wrote: > > > Yes. Go ahead. Today I contacted FTP masters because I think the > > > debian/copyright file is ok. I will keep you posted about it. > > > > > > >

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

Bug#807713: telepathy-idle: Cannot create any connection

Package: telepathy-idle Severity: grave It appears that telepathy-idle is unusable right now, adding a connection in Polari or Empathy fails. Polari console output shows: (org.gnome.Polari:3203): Gjs-WARNING **: JS ERROR: TelepathyGLib.Error: Protocol 'irc' not found on CM 'idle'

Bug#807487: pbuilder update in sid breaks pbuilder on (old)stable

* Mattia Rizzolo , 2015-12-09, 19:07: I *believe* aptitude was using /build/.aptitude/cache/ for this so the wildcard was not picking it, instead now it started using /build/aptitude/cache, so interferring with the wildcard. This is bug #807545, which is now fixed... For

Bug#800172: marked as done (forg: Please migrate a supported debhelper compat level)

Your message dated Fri, 11 Dec 2015 22:50:22 + with message-id and subject line Bug#800172: fixed in forg 0.5.1-7.2 has caused the Debian Bug report #800172, regarding forg: Please migrate a supported debhelper compat level to be marked as done. This

Bug#807707: ddclient exit hook for dhclient breaks network configuration

Hi Doug, On 12/11/2015 09:42 PM, Doug Kingston wrote: > The Problem: When I looked at the ddclient hook, I noticed it was > calling exit(0), > which exited the entire dhclient-script prematurely. This is very > bad, since none > of the other exits was given an opportuntity to run. Exits must

Bug#804386: marked as done (condor: FTBFS on arm64 ppc64el and s390x: conflicting declaration 'typedef long unsigned int uint64_t')

Your message dated Fri, 11 Dec 2015 22:35:00 + with message-id and subject line Bug#804386: fixed in condor 8.4.2~dfsg.1-1 has caused the Debian Bug report #804386, regarding condor: FTBFS on arm64 ppc64el and s390x: conflicting declaration 'typedef long

Processed: Re: Bug#807713: telepathy-idle: Cannot create any connection

Processing control commands: > severity -1 normal Bug #807713 [telepathy-idle] telepathy-idle: Cannot create any connection Severity set to 'normal' from 'grave' -- 807713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807713 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#807713: telepathy-idle: Cannot create any connection

Control: severity -1 normal On Fri, Dec 11, 2015 at 11:12:59PM +0100, Julian Andres Klode wrote: > Package: telepathy-idle > Severity: grave > > It appears that telepathy-idle is unusable right now, > adding a connection in Polari or Empathy fails. Polari > console output shows: > >

Processed: tagging 807673, bug 807673 is forwarded to https://github.com/danwent/Perspectives/issues/166

Processing commands for cont...@bugs.debian.org: > tags 807673 + upstream Bug #807673 [src:perspectives-extension] perspectives-extension: FTBFS: ValueError: empty namespace prefix is not supported in ElementPath Added tag(s) upstream. > forwarded 807673

Processed: retitle 807698 to srtp: CVE-2015-6360: Prevent potential DoS attack due to lack of bounds checking on RTP header CSRC count and extension header length ...

Processing commands for cont...@bugs.debian.org: > retitle 807698 srtp: CVE-2015-6360: Prevent potential DoS attack due to lack > of bounds checking on RTP header CSRC count and extension header length Bug #807698 [src:srtp] CVE-2015-6360: Prevent potential DoS attack due to lack of bounds

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 673038 2.4.39-1 Bug #673038 {Done: Michael Gilbert } [slapd] slapd: slapcat output truncated every now and then Ignoring request to alter fixed versions of bug #673038 to the same values previously set > End of

Bug#793911: groovy should not release with stretch

Le 11/12/2015 21:16, Miguel Landaeta a écrit : > 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.

Processed: fixed 673038 in 2.4.39-1

Processing commands for cont...@bugs.debian.org: > fixed 673038 2.4.39-1 Bug #673038 {Done: Michael Gilbert } [slapd] slapd: slapcat output truncated every now and then Marked as fixed in versions openldap/2.4.39-1. > thanks Stopping processing here. Please contact me if

Bug#793911: groovy should not release with stretch

Le 11/12/2015 22:49, Miguel Landaeta a écrit : > 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. I've packaged most the new dependencies required by Spring

Bug#793911: groovy should not release with stretch

Am 11.12.2015 um 22:49 schrieb Miguel Landaeta: > 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

Bug#807730: incorrect bsd/unistd.h header

Package: libbsd-dev Version: 0.8.0-2 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi! After a recent update of libbsd, programs using it now fail at compile time with: /usr/include/bsd/unistd.h: In function 'setproctitle': /usr/include/bsd/unistd.h:64:2: error: expected

Bug#807629: marked as done (Incomplete dependencies: clementine fails to start)

Your message dated Sat, 12 Dec 2015 03:29:41 +0100 with message-id <20151212022940.ga3...@angband.pl> and subject line fixed in binNMU has caused the Debian Bug report #807629, regarding Incomplete dependencies: clementine fails to start to be marked as done. This means that you claim that the

Bug#805746: aghermann: Fails to build with GSL 2

Hey Yaroslav & Bas, Sorry for getting a bit late with an apparently simple fix. Here's version 1.0.7, which builds with gsl-2.0: http://johnhommer.com/academic/code/aghermann/source/deb/aghermann_1.0.7-1.dsc. Cheers, Andrei On Sat, 21 Nov 2015 23:52:21 +0100 Bas Couwenberg

Bug#807728: Could not create directory: /home/jff/.cache

Package: pbuilder Version: 0.221.1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, since the last update I get allways: [...] Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ... Reading package lists... Building dependency tree... Reading state information...

Bug#807502: gcc-avr: Missing support for atxmega

Then I would prefer to raise the severity to serious, are you OK with that? -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ El dic 11, 2015 11:48 AM, "Thorsten Schulz" escribió: > Hej, > > this may be a broader

Bug#807672: natlog: FTBFS: [/usr/bin/icmbuild, line 166] Error: idx undefined

Dear Chris Lamb, you wrote: > natlog fails to build from source in unstable/amd64: Yes, it's a hard life But no kidding: thanks for the update. The build-problems are caused by natlog's build script not yet being updated to the latest icmake version. I'm working on that right now, and I'll

Bug#807645: ifupdown package fails to configure itself (by dpkg)

Package: ifupdown Version: 0.8.2 Severity: serious Justification: fail to configure itself Hi, I just upgraded ifupdown and it fails to configure itself. I've added "set -x" to /var/lib/dpkg/info/ifupdown.postinst and a final "echo done $?" at the end of /lib/systemd/systemd-sysv-install.

Processed: tagging 804386

Processing commands for cont...@bugs.debian.org: > tags 804386 + pending fixed-upstream Bug #804386 [condor] condor: FTBFS on arm64 ppc64el and s390x: conflicting declaration 'typedef long unsigned int uint64_t' Added tag(s) fixed-upstream and pending. > thanks Stopping processing here. Please

Bug#807698: CVE-2015-6360: Prevent potential DoS attack due to lack of bounds checking on RTP header CSRC count and extension header length

Source: srtp Version: 1.4.5~20130609~dfsg-1.1 Severity: grave Tags: security Hi, from what I figured out it seems the 1.4 series is also affected by CVE-2015-6360. While there is no aead mode srtp_unprotect needs the patch nevertheless. See:

Bug#789118: Cannot unlock screen after upgrading GNOME if locked before upgrade

Package: gnome-shell Version: 3.18.3-2 Followup-For: Bug #789118 Dear Maintainer, Pretty close to this bug, although it's not dependant on upgrading Gnome. The last few upgrades of SID have surfaced a similiar bug. On setting my power settings via Gnome-Settings for 15 minutes, upon attempting

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

I have a build ongoing right now in amd64 i386 arm64 armel armhf powerpc. the builds seems fine, at least I had to tweak a little bit the symbols and change something in changelog e.g. a symbol was leftover in symbols file: + _ZN8Echonest12AudioSummary12setTimestampEf@Base 2.1.0 and was

Bug#807705: xserver-xorg-video-openchrome: FTBFS: /usr/include/xorg/os.h:558:1: error: expected identifier or '(' before '__extension__'

Source: xserver-xorg-video-openchrome Version: 1:0.3.3-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, xserver-xorg-video-openchrome fails to

Bug#807707: ddclient exit hook for dhclient breaks network configuration

Package: ddclient Version: 3.8.2-2 Severity: critical Tags: patch Justification: breaks the whole system Dear Maintainer, As far as I can tell, this also impacts the unstable version (3.8.2-3) What led up to the situation? After installing ddclient on my Google Compute Engine hosted

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. >

Bug#793911: groovy should not release with stretch

Am 11.12.2015 um 21:16 schrieb Miguel Landaeta: [...] >> 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

Bug#807706: uima-addons: FTBFS: Unresolveable build extension: Plugin org.apache.uima:PearPackagingMavenPlugin:2.3.1

Source: uima-addons Version: 2.3.1-3 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, uima-addons fails to build from source in unstable/amd64:

Processed: reassign

Processing commands for cont...@bugs.debian.org: > reassign 807502 binutils-avr Bug #807502 [gcc-avr] gcc-avr: Missing support for atxmega384d3 since last upload Bug reassigned from package 'gcc-avr' to 'binutils-avr'. No longer marked as found in versions gcc-avr/1:4.9.2+Atmel3.5.0-1. Ignoring

Bug#807502: gcc-avr: Missing support for atxmega

Hi, the file you want is crtx384d3.o and not crtatxmega384d3.o (even i the new avr-libc). Dont know why he's suddenly trying to use crtatxmega384d3.o instead, but the issue seems to be in binutils. I'm reassigning the bug there and will keep looking... On Fri, Dec 11, 2015 at 4:23 PM, Lisandro

Processed: RM: haskell-concrete-typerep -- ROM; Unmaintained by upstream

Processing control commands: > block 807606 by -1 Bug #807606 [src:haskell-concrete-typerep] haskell-concrete-typerep: FTBFS: Constructor `TypeRep' should have 4 arguments, but has been given 3 807606 was not blocked by any bugs. 807606 was not blocking any bugs. Added blocking bug(s) of 807606:

Bug#807607: marked as done (pkg-haskell-tools: FTBFS: At least the following dependencies are missing: base >=4.6 && <4.8)

Your message dated Fri, 11 Dec 2015 09:47:01 +0100 with message-id <1449823621.3363.0.ca...@debian.org> and subject line Re: Bug#807607: pkg-haskell-tools: FTBFS: has caused the Debian Bug report #807607, regarding pkg-haskell-tools: FTBFS: At least the following dependencies are missing: base