Bug#797866: libtorrent: ABI transition needed for libstdc++ v5

On 09/09/15 07:00, Jose-Luis Rivas wrote: > On 08/09/15, 10:24pm, Jose-Luis Rivas wrote: >> Just to be clear, if I rebuild this with the source packages from >> unstable with a new upstream version the rename is not necessary? > > Nevermind, upstream bumped soname anyway. A new upstream SONAME mak

Bug#797866: libtorrent: ABI transition needed for libstdc++ v5

Nevermind, upstream bumped soname anyway. On 08/09/15, 10:24pm, Jose-Luis Rivas wrote: > Just to be clear, if I rebuild this with the source packages from > unstable with a new upstream version the rename is not necessary? > > On 03/09/15, 08:21am, Simon McVittie wrote: > > Source: libtorrent > >

Bug#797866: libtorrent: ABI transition needed for libstdc++ v5

Just to be clear, if I rebuild this with the source packages from unstable with a new upstream version the rename is not necessary? On 03/09/15, 08:21am, Simon McVittie wrote: > Source: libtorrent > Version: 0.13.2-1 > Severity: serious > Justification: breaks ABI without a package rename > Tags:

Bug#778144: marked as done (telepathy-qt: ftbfs with GCC-5)

Your message dated Tue, 08 Sep 2015 22:18:33 -0700 with message-id <1789613.4tzhsEBzHy@myrada> and subject line telepathy-qt: ftbfs with GCC-5 has caused the Debian Bug report #778144, regarding telepathy-qt: ftbfs with GCC-5 to be marked as done. This means that you claim that the problem has bee

Bug#797090: marked as done (konversation: FTBFS: *** No rule to make target '/usr/lib/libsoprano.so')

Your message dated Tue, 08 Sep 2015 22:16:45 -0700 with message-id <1914234.JVbGLdY4i6@myrada> and subject line FTBFS: *** No rule to make target '/usr/lib/libsoprano.so' has caused the Debian Bug report #797090, regarding konversation: FTBFS: *** No rule to make target '/usr/lib/libsoprano.so' to

Bug#777952: marked as done (libkolab: ftbfs with GCC-5)

Your message dated Tue, 08 Sep 2015 22:20:39 -0700 with message-id <1616974.EZlhAVZ77k@myrada> and subject line libkolab: ftbfs with GCC-5 has caused the Debian Bug report #777952, regarding libkolab: ftbfs with GCC-5 to be marked as done. This means that you claim that the problem has been dealt

Bug#778036: closing 778036

close 778036 4:4.14.2-3 thanks

Processed: closing 778036

Processing commands for cont...@bugs.debian.org: > close 778036 4:4.14.2-3 Bug #778036 [src:okteta] okteta: ftbfs with GCC-5 Marked as fixed in versions okteta/4:4.14.2-3. Bug #778036 [src:okteta] okteta: ftbfs with GCC-5 Marked Bug as done > thanks Stopping processing here. Please contact me if

Bug#795818: closing 795818

close 795818 1.0.0-3 thanks

Processed: closing 795818

Processing commands for cont...@bugs.debian.org: > close 795818 1.0.0-3 Bug #795818 [src:libindi] libindi: FTBFS on arm64: symbols mismatch Marked as fixed in versions libindi/1.0.0-3. Bug #795818 [src:libindi] libindi: FTBFS on arm64: symbols mismatch Marked Bug as done > thanks Stopping processi

Bug#794977: please, fix this soon

I used the ln -s workaround, thanks Aleksi. But I think this package is important enough to deserve a quick official update. By the way, if the update checked for the presence of the simlink fix and warned to undo it, that would be very appreciated :) -- Francesco Potortì (ricercatore)V

Bug#798113: marked as done (wmdate ftbfs with the new libdockapp)

Your message dated Tue, 08 Sep 2015 22:53:17 + with message-id and subject line Bug#798113: fixed in wmdate 0.7-4.1 has caused the Debian Bug report #798113, regarding wmdate ftbfs with the new libdockapp to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#798115: marked as done (wmail: FTBFS with libdockapp v0.7.0)

Your message dated Tue, 08 Sep 2015 22:53:12 + with message-id and subject line Bug#798112: fixed in wmail 2.0-3.1 has caused the Debian Bug report #798112, regarding wmail: FTBFS with libdockapp v0.7.0 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#798413: ftp.debian.org: Source-only uploads which FTBFS on Arch: all buildd require NEW processing in next upload

Package: ftp.debian.org Severity: serious Justification: Kafka is alive Kind ftpmasters: When a source-only upload fails to build from source in the "Arch: all" autobuilder [1], the system seems to think that the source does no longer provide such Arch: all packages. As a result, it seems, new u

Bug#798113: marked as done (wmdate ftbfs with the new libdockapp)

Your message dated Tue, 08 Sep 2015 22:53:17 + with message-id and subject line Bug#798118: fixed in wmdate 0.7-4.1 has caused the Debian Bug report #798118, regarding wmdate ftbfs with the new libdockapp to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#798118: marked as done (wmdate: FTBFS with libdockapp v0.7.0)

Your message dated Tue, 08 Sep 2015 22:53:17 + with message-id and subject line Bug#798118: fixed in wmdate 0.7-4.1 has caused the Debian Bug report #798118, regarding wmdate: FTBFS with libdockapp v0.7.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#798115: marked as done (wmail: FTBFS with libdockapp v0.7.0)

Your message dated Tue, 08 Sep 2015 22:53:12 + with message-id and subject line Bug#798115: fixed in wmail 2.0-3.1 has caused the Debian Bug report #798115, regarding wmail: FTBFS with libdockapp v0.7.0 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#798118: marked as done (wmdate: FTBFS with libdockapp v0.7.0)

Your message dated Tue, 08 Sep 2015 22:53:17 + with message-id and subject line Bug#798113: fixed in wmdate 0.7-4.1 has caused the Debian Bug report #798113, regarding wmdate: FTBFS with libdockapp v0.7.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#798112: marked as done (wmail ftbfs with the new libdockapp)

Your message dated Tue, 08 Sep 2015 22:53:12 + with message-id and subject line Bug#798115: fixed in wmail 2.0-3.1 has caused the Debian Bug report #798115, regarding wmail ftbfs with the new libdockapp to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#798112: marked as done (wmail ftbfs with the new libdockapp)

Your message dated Tue, 08 Sep 2015 22:53:12 + with message-id and subject line Bug#798112: fixed in wmail 2.0-3.1 has caused the Debian Bug report #798112, regarding wmail ftbfs with the new libdockapp to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#798383: marked as done (request-tracker4: Depends on non-free libapache2-mod-fastcgi)

Your message dated Tue, 08 Sep 2015 22:36:47 + with message-id and subject line Bug#798383: fixed in request-tracker4 4.2.12-2 has caused the Debian Bug report #798383, regarding request-tracker4: Depends on non-free libapache2-mod-fastcgi to be marked as done. This means that you claim that

Bug#793137: tulip: FTBFS on armel and armhf - blocks testing migration

Submitted https://bugs.debian.org/798408 on libgles2-mesa-dev and libglew-dev, affecting those 2 FTBFS bugs.

Processed: severity of 794935 is normal, tagging 794935

Processing commands for cont...@bugs.debian.org: > severity 794935 normal Bug #794935 [release.debian.org] llvm-toolchain-3.5: library transition is needed when GCC 5 is the default Severity set to 'normal' from 'serious' > tags 794935 = pending Bug #794935 [release.debian.org] llvm-toolchain-3.5

Processed: found 798197 in 3.1.1-1, tagging 797966, tagging 797292, tagging 796542, tagging 796531 ...

Processing commands for cont...@bugs.debian.org: > found 798197 3.1.1-1 Bug #798197 [sdformat] sdformat build-depends on libignition-math2-dev which is not available on armel and mips. There is no source info for the package 'sdformat' at version '3.1.1-1' with architecture '' Unable to make a s

Bug#777863: gcc-msp430: ftbfs with GCC-5

Dear Maintainer, please find attached patch that fixes the compilation problem. Functionality of the resulting gcc I can't assert as I don't know how to test if binary produced by this gcc is functional or not - I'd need real or emulated MSP430 board I guess. The patch is in unified diff format

Processed: tagging 777863

Processing commands for cont...@bugs.debian.org: > tags 777863 + patch Bug #777863 [src:gcc-msp430] gcc-msp430: ftbfs with GCC-5 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 777863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777863 Deb

Bug#794332: marked as done (sssd-common: deletes conffile owned by sssd: /etc/logrotate.d/sssd)

Your message dated Tue, 08 Sep 2015 21:24:59 + with message-id and subject line Bug#794332: fixed in sssd 1.12.5-3 has caused the Debian Bug report #794332, regarding sssd-common: deletes conffile owned by sssd: /etc/logrotate.d/sssd to be marked as done. This means that you claim that the pr

Bug#798357: marked as done (libnetcdf-cxx-legacy-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/share/info/netcdf-cxx.info.gz)

Your message dated Tue, 08 Sep 2015 21:22:30 + with message-id and subject line Bug#798357: fixed in netcdf-cxx-legacy 4.2-2 has caused the Debian Bug report #798357, regarding libnetcdf-cxx-legacy-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/share/info/netcdf-cxx.info.gz to

Bug#798353: marked as done (libsndio-dev and libroar-dev: error when trying to install together)

Your message dated Tue, 08 Sep 2015 21:24:07 + with message-id and subject line Bug#798353: fixed in sndio 1.0.1-1 has caused the Debian Bug report #798353, regarding libsndio-dev and libroar-dev: error when trying to install together to be marked as done. This means that you claim that the p

Bug#794935: llvm-toolchain-3.5 - upload != transition done

Control: reopen -1 User: release.debian@packages.debian.org Usertags: transition Control: block -1 by 790756 Control: reassign -1 release.debian.org Control: forwarded -1 https://release.debian.org/transitions/html/auto-llvm-toolchain-3.5.html Control: retitle -1 llvm-toolchain-3.5: library t

Processed: Re: Bug#794935: llvm-toolchain-3.5 - upload != transition done

Processing control commands: > reopen -1 Bug #794935 {Done: Sylvestre Ledru } [src:llvm-toolchain-3.5] llvm-toolchain-3.6: library transition is needed when GCC 5 is the default 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you m

Bug#797966: syncevolution-common: uninstallable due to libsynthesis0 dependency

On Sat, Sep 05, 2015 at 09:10:14PM +0200, Tino Mettler wrote: > thanks for the offer. I'll do it this way, then. I also intend to package the > latest upstream release but this would take longer. Having just the bug fix and letting it migrate to Stretch before the new upstream is uploaded would b

Bug#796118: Should djbdns be removed?

On Tue, Sep 08, 2015 at 03:01:29PM -0400, Robert Edmonds wrote: > Moritz Mühlenhoff wrote: > > reassign 796118 ftp.debian.org > > retitle 796118 RM: djbdns > > thanks > > > > On Wed, Aug 19, 2015 at 05:45:30PM +0200, Moritz Muehlenhoff wrote: > > > Source: djbdns > > > Severity: serious > > > > >

Processed: tagging 797721

Processing commands for cont...@bugs.debian.org: > tags 797721 + pending Bug #797721 [zsh] zsh frozen with zombie child due to the use of TRAPCHLD Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 797721: http://bugs.debian.org/cgi-bin/bugrepor

Processed: Re: Bug#796731: freecontact: FTBFS on mips (test suite failure)

Processing control commands: > reopen -1 Bug #796731 {Done: Debian FTP Masters } [src:freecontact] freecontact: FTBFS on mips (test suite failure) Bug reopened Ignoring request to alter fixed versions of bug #796731 to the same values previously set -- 796731: http://bugs.debian.org/cgi-bin/bu

Bug#796731: freecontact: FTBFS on mips (test suite failure)

Control: reopen -1 On Fri, Aug 28, 2015 at 17:42:10 +0200, Andreas Tille wrote: > Hi Julien, > > On Fri, Aug 28, 2015 at 05:20:55PM +0200, Julien Cristau wrote: > > On Wed, Aug 26, 2015 at 17:05:39 +0200, Andreas Tille wrote: > > > > > Any chance to do a manual build on a more powerfull MIPS bo

Bug#748737: [request-tracker-maintainers] Bug#748737: Bug#748737: Bug#748737: Bug#748737: rt4-extension-assettracker: fails to upgrade from wheezy

On Tue, Sep 08, 2015 at 11:07:50AM -0400, Shawn Moore wrote: > Hi Jerome et al, > > (Hi! I’m Shawn, one of the upstream engineers on Request Tracker) > > > 2015/09/04 17:09、Jerome Charaoui のメール： > > > >>> Is this a good place to suggest Best Practical's own > >>> RT::Extension::Assets (http://

Processed: Re: Bug#798357: libnetcdf-cxx-legacy-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/share/info/netcdf-cxx.info.gz

Processing control commands: > tags -1 pending Bug #798357 [libnetcdf-cxx-legacy-dev] libnetcdf-cxx-legacy-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/share/info/netcdf-cxx.info.gz Added tag(s) pending. -- 798357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798357 Debian

Processed: jessie-pu: package conkeror/1.0~~pre-1+git141025-1+deb8u1

Processing control commands: > block 795597 by -1 Bug #795597 [conkeror] Conkeror crashes on start up with SyntaxError, ReferenceError and TypeError 795597 was not blocked by any bugs. 795597 was not blocking any bugs. Added blocking bug(s) of 795597: 798404 -- 795597: http://bugs.debian.org/cg

Bug#798357: libnetcdf-cxx-legacy-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/share/info/netcdf-cxx.info.gz

Control: tags -1 pending Hi Andreas, Thanks for your continued work on piuparts. I've updated Breaks/Replaces to include netcdf-doc too in -2, the upload should hit the archive soon. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10

Bug#798402: FTBFS: missing build-dep on doxygen

Source: libpqxx Version: 4.0.1+dfsg-4 Severity: serious Justification: fails to build from source (but built successfully in the past) Your package no longer builds on any of the buildds: https://buildd.debian.org/status/logs.php?pkg=libpqxx&ver=4.0.1%2Bdfsg-4&suite=sid It seems the build-arch ta

Bug#798401: gdb-python2 does not actually link to python2, but python3

Package: gdb-python2 Version: 7.10-1 Severity: grave Justification: renders package unusable Dear Maintainer, The gdb-python2 package does not actually contain a version of gdb linked to python2. Rather, it is a byte-for-byte identical copy of the /usr/bin/gdb shipped in the gdb package, which li

Bug#754704: Suggested fix is not correct

The suggested fix of adding a line to the dnssec-tools.conf file zonefile-parser Net::DNS::ZoneFile cannot be right. After re-starting rollerd, and waiting an hour, this message is printed out: zonefile parser Net::DNS::ZoneFile not usable; using default parser Net::DNS::ZoneFile::Fast at /us

Bug#797976: marked as done (spice: CVE-2015-3247: memory corruption in worker_update_monitors_config())

Your message dated Tue, 08 Sep 2015 19:49:48 + with message-id and subject line Bug#797976: fixed in spice 0.12.5-1.2 has caused the Debian Bug report #797976, regarding spice: CVE-2015-3247: memory corruption in worker_update_monitors_config() to be marked as done. This means that you claim

Bug#796118: Should djbdns be removed?

Moritz Mühlenhoff wrote: > reassign 796118 ftp.debian.org > retitle 796118 RM: djbdns > thanks > > On Wed, Aug 19, 2015 at 05:45:30PM +0200, Moritz Muehlenhoff wrote: > > Source: djbdns > > Severity: serious > > > > djbdns is RC-buggy for many years now and was out of testing since 2009. > > Shou

Bug#798336:

i think the problem is that after this upgrade python-service-identity:amd64 1.0.0-3 -> 14.0.0-1 python-characteristic should also be upgraded from 0.1.0 to 14.0.x Davor

Bug#771169: marked as done (openssl: Removes symbol without SONAME bump)

Your message dated Tue, 08 Sep 2015 19:00:16 + with message-id and subject line Bug#768476: fixed in openssl 1.0.2d-2 has caused the Debian Bug report #768476, regarding openssl: Removes symbol without SONAME bump to be marked as done. This means that you claim that the problem has been dealt

Bug#769023: marked as done (openssl: Removes symbol without SONAME bump)

Your message dated Tue, 08 Sep 2015 19:00:16 + with message-id and subject line Bug#768476: fixed in openssl 1.0.2d-2 has caused the Debian Bug report #768476, regarding openssl: Removes symbol without SONAME bump to be marked as done. This means that you claim that the problem has been dealt

Bug#781094: marked as done (curl: relocation error on starting)

Your message dated Tue, 08 Sep 2015 19:00:16 + with message-id and subject line Bug#768476: fixed in openssl 1.0.2d-2 has caused the Debian Bug report #768476, regarding curl: relocation error on starting to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#770278: marked as done (openssl: Removes symbol without SONAME bump)

Your message dated Tue, 08 Sep 2015 19:00:16 + with message-id and subject line Bug#768476: fixed in openssl 1.0.2d-2 has caused the Debian Bug report #768476, regarding openssl: Removes symbol without SONAME bump to be marked as done. This means that you claim that the problem has been dealt

Bug#781929: marked as done (deluge-gtk: version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference)

Your message dated Tue, 08 Sep 2015 19:00:16 + with message-id and subject line Bug#768476: fixed in openssl 1.0.2d-2 has caused the Debian Bug report #768476, regarding deluge-gtk: version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference to be marked as done. This

Bug#770605: marked as done (openssl: Removes symbol without SONAME bump)

Your message dated Tue, 08 Sep 2015 19:00:16 + with message-id and subject line Bug#768476: fixed in openssl 1.0.2d-2 has caused the Debian Bug report #768476, regarding openssl: Removes symbol without SONAME bump to be marked as done. This means that you claim that the problem has been dealt

Bug#768522: marked as done (openssl: Removes symbol without SONAME bump)

Your message dated Tue, 08 Sep 2015 19:00:16 + with message-id and subject line Bug#768476: fixed in openssl 1.0.2d-2 has caused the Debian Bug report #768476, regarding openssl: Removes symbol without SONAME bump to be marked as done. This means that you claim that the problem has been dealt

Bug#787712: marked as done (libcurl: relocation error libcurl.so.4: symbol SSLv3_client_method)

Your message dated Tue, 08 Sep 2015 19:00:16 + with message-id and subject line Bug#768476: fixed in openssl 1.0.2d-2 has caused the Debian Bug report #768476, regarding libcurl: relocation error libcurl.so.4: symbol SSLv3_client_method to be marked as done. This means that you claim that the

Bug#771993: marked as done (feh: relocation error: /usr/lib/i386-linux-gnu/libcurl.so.4: symbol SSLv3_client_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference)

Your message dated Tue, 08 Sep 2015 19:00:16 + with message-id and subject line Bug#768476: fixed in openssl 1.0.2d-2 has caused the Debian Bug report #768476, regarding feh: relocation error: /usr/lib/i386-linux-gnu/libcurl.so.4: symbol SSLv3_client_method, version OPENSSL_1.0.0 not defined

Bug#768476: marked as done (openssl: Removes symbol without SONAME bump)

Your message dated Tue, 08 Sep 2015 19:00:16 + with message-id and subject line Bug#768476: fixed in openssl 1.0.2d-2 has caused the Debian Bug report #768476, regarding openssl: Removes symbol without SONAME bump to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: Should djbdns be removed?

Processing commands for cont...@bugs.debian.org: > reassign 796118 ftp.debian.org Bug #796118 [src:djbdns] Should djbdns be removed? Bug reassigned from package 'src:djbdns' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #796118 to the same values previously set Ignoring req

Bug#796118: Should djbdns be removed?

reassign 796118 ftp.debian.org retitle 796118 RM: djbdns thanks On Wed, Aug 19, 2015 at 05:45:30PM +0200, Moritz Muehlenhoff wrote: > Source: djbdns > Severity: serious > > djbdns is RC-buggy for many years now and was out of testing since 2009. > Should we remove it from unstable? No objections

Processed: tagging 708044, tagging 721090, tagging 797651, tagging 797438, tagging 793885, tagging 798143 ...

Processing commands for cont...@bugs.debian.org: > tags 708044 + sid stretch Bug #708044 [padevchooser] padevchooser: depends on libgnomedesktop2 which is going away Added tag(s) sid and stretch. > tags 721090 - jessie Bug #721090 [libgnomedesktop2.20-cil] libgnomedesktop2.20-cil: depends on lib

Bug#798394: mriconvert: FTBFS on s390x: relocation truncated to fit

Source: mriconvert Version: 1:2.0.8-1 Severity: serious Justification: fails to build from source Your package no longer builds on s390x, see the logs at https://buildd.debian.org/status/logs.php?pkg=mriconvert&arch=s390x Cheers, Julien signature.asc Description: Digital signature

Bug#798393: FTBFS: build killed after N minutes of inactivity

Source: mathgl Version: 2.3.3-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Your package no longer builds on the buildds, see https://buildd.debian.org/status/logs.php?pkg=mathgl&ver=2.3.3-1&suite=sid Cheers, Julien signature.asc Description:

Bug#797068: marked as done (goobook: depends on python-httplib2 v0.9, but crashes requiring v0.9.1.)

Your message dated Tue, 8 Sep 2015 20:49:24 +0300 with message-id <20150908174924.gb2...@gmail.com> and subject line Closing #797068 has caused the Debian Bug report #797068, regarding goobook: depends on python-httplib2 v0.9, but crashes requiring v0.9.1. to be marked as done. This means that yo

Bug#737435: marked as done ([src:luakit] Sourceless file (minified))

Your message dated Tue, 08 Sep 2015 16:49:18 + with message-id and subject line Bug#737435: fixed in luakit 2012.09.13-r1-8 has caused the Debian Bug report #737435, regarding [src:luakit] Sourceless file (minified) to be marked as done. This means that you claim that the problem has been dea

Bug#793608: linux: update "Recommends" of linux on armel/sh4 due to package renamed

Control: retitle -1 linux: update "Recommends" of linux on armel/sh4 due to package renamed

Processed: Re: linux: update "Recommends" of linux on armel/sh4 due to package renamed

Processing control commands: > retitle -1 linux: update "Recommends" of linux on armel/sh4 Bug #793608 {Done: Ben Hutchings } [linux] linux: update "Depends" of linux on armel/sh4 due to package renamed Changed Bug title to 'linux: update "Recommends" of linux on armel/sh4' from 'linux: update "

Bug#798358: cryptmount: fails to install: cryptmount.postinst: deb-systemd-helper: not found

Hello Andreas, Thanks for reporting this bug. I have already been working on a cleaner version of the postinst script making better use dh-systemd, which should fix other piuparts problems relating to unwanted files left after uninstallation. I hope to have a 5.1-3 available very soon. Th

Bug#793189: Status of this bug

Not that this RC bug is being looked at by the autoremoval process even though the bug is fixed, because of a number (possibly) of interwined issues: * the i386 build was not available until recently (I uploaded it on Saturday) * possibly because of the erroneous (non-alternative) depedency by r

Bug#798347: fdisk-udeb: not installable, depends on libtinfo5

Andreas Henriksson, le Tue 08 Sep 2015 18:01:08 +0200, a écrit : > Are there any issues I should be aware of that would outweigh the > benefits mentioned above? (I'm aware it's not perfectly optimal > to build staticly, but can anyone forsee any actual practical or > policy issue with doing so?) T

Bug#798347: fdisk-udeb: not installable, depends on libtinfo5

Hello. On Tue, Sep 08, 2015 at 05:47:13PM +0200, Samuel Thibault wrote: > Cyril Brulebois, le Tue 08 Sep 2015 17:39:24 +0200, a écrit : > > (Adding -boot@ for further discussion.) > > > I'm pondering just building static versions of fdisk,sfdisk,blkid > > > to put in the udebs instead to avoid cur

Bug#798347: fdisk-udeb: not installable, depends on libtinfo5

Cyril Brulebois, le Tue 08 Sep 2015 17:39:24 +0200, a écrit : > (Adding -boot@ for further discussion.) > > I'm pondering just building static versions of fdisk,sfdisk,blkid > > to put in the udebs instead to avoid current and future dependency > > issues. Would that be acceptable? > > > > (That w

Processed: Re: Bug#798363: fusionforge-web: fails to install: /usr/share/fusionforge/post-install.d/web/web.sh: line 77: openssl: command not found

Processing control commands: > severity -1 normal Bug #798363 [fusionforge-web] fusionforge-web: fails to install: /usr/share/fusionforge/post-install.d/web/web.sh: line 77: openssl: command not found Severity set to 'normal' from 'serious' -- 798363: http://bugs.debian.org/cgi-bin/bugreport.c

Processed: found 798383 in 4.2.11-3

Processing commands for cont...@bugs.debian.org: > found 798383 4.2.11-3 Bug #798383 [rt4-apache2] request-tracker4: Depends on non-free libapache2-mod-fastcgi Marked as found in versions request-tracker4/4.2.11-3. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#798347: fdisk-udeb: not installable, depends on libtinfo5

(Adding -boot@ for further discussion.) Hi, Andreas Henriksson (2015-09-08): > Hello Cyril Brulebois. > > Thanks for your bug report. > > On Tue, Sep 08, 2015 at 01:13:58PM +0200, Cyril Brulebois wrote: > > Package: fdisk-udeb > > Version: 2.27-1 > > Severity: grave > > Justification: renders

Bug#798363: fusionforge-web: fails to install: /usr/share/fusionforge/post-install.d/web/web.sh: line 77: openssl: command not found

Control: severity -1 normal Hi, Lowering severity since only piuparts is stumbling upon this (i.e.: neither the FusionForge rebuild testsuite nor any of our production installs triggered this issue, hence widespread usage works). I wish you didn't wait until right when FusionForge is back in tes

Bug#798383: request-tracker4: Depends on non-free libapache2-mod-fastcgi

Package: rt4-apache2 Version: 4.2.12-1 Severity: serious Justification: maintainer, policy violation In I erroneously introduced a non-alternative dependency on libapache2

Bug#798347: fdisk-udeb: not installable, depends on libtinfo5

Hello Cyril Brulebois. Thanks for your bug report. On Tue, Sep 08, 2015 at 01:13:58PM +0200, Cyril Brulebois wrote: > Package: fdisk-udeb > Version: 2.27-1 > Severity: grave > Justification: renders package unusable > > Hi, > > Your package gained a dependency on libtinfo5, which makes it no lo

Bug#748737: [request-tracker-maintainers] Bug#748737: Bug#748737: Bug#748737: rt4-extension-assettracker: fails to upgrade from wheezy

Hi Jerome et al, (Hi! I’m Shawn, one of the upstream engineers on Request Tracker) > 2015/09/04 17:09、Jerome Charaoui のメール： > >>> Is this a good place to suggest Best Practical's own RT::Extension::Assets >>> (http://bestpractical.com/assets) as a candidate for packaging? > > The recommended

Processed: tagging 797661, user debian...@lists.debian.org, usertagging 797661, found 769146 in 1:5.7p3-1 ...

Processing commands for cont...@bugs.debian.org: > tags 797661 + pending Bug #797661 [xserver-xorg-core] Fails to upgrade, file conflict with x11-common Added tag(s) pending. > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 797661 piupa

Bug#798367: marked as done ([libavcodec-ffmpeg56] Binary-only upload renders package uninstallable on multi-arch)

Your message dated Tue, 8 Sep 2015 15:27:53 +0200 with message-id <20150908132753.gd4...@ramacher.at> and subject line Re: Bug#798367: [libavcodec-ffmpeg56] Binary-only upload renders package uninstallable on multi-arch has caused the Debian Bug report #798367, regarding [libavcodec-ffmpeg56] Bina

Bug#798367: [libavcodec-ffmpeg56] Binary-only upload renders package uninstallable on multi-arch

Package: libavcodec-ffmpeg56 Version: 7:2.7.2-2+b1 Severity: serious --- Please enter the report below this line. --- Since this package is needed by libasound2-plugins and that in turn is needed to have pulse audio work, on multi-arch systems it is likely to be needed as both 32 and 64-bit ver

Bug#777946: marked as done (libgnatcoll: ftbfs with GCC-5)

Your message dated Tue, 08 Sep 2015 13:06:32 + with message-id and subject line Bug#777946: fixed in libgnatcoll 1.6gpl2014-8 has caused the Debian Bug report #777946, regarding libgnatcoll: ftbfs with GCC-5 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#798363: fusionforge-web: fails to install: /usr/share/fusionforge/post-install.d/web/web.sh: line 77: openssl: command not found

Package: fusionforge-web Version: 6.0.2+20150901-1 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 severit

Bug#798362: acpi-support: ails to install due to insserv rejecting the script header

Package: acpi-support Version: 0.142-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install due to insserv rejecting the script header. Some notes are available from at https://wiki.debian.org/LSBInitScripts

Bug#798361: mercurial-server: fails to install: mercurial-server.postinst: update-python-modules: not found

Package: mercurial-server Version: 1.2-2.1 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. >Fro

Bug#798360: vim-voom: fails to install: vim-voom.postinst: line 23: vim-addon-manager: command not found

Package: vim-voom Version: 5.1-2 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. >From the atta

Bug#798358: cryptmount: fails to install: cryptmount.postinst: deb-systemd-helper: not found

Package: cryptmount Version: 5.1-2 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. >From the at

Processed: Re: Bug#797228: filezilla: FTBFS on mips/mipsel/powerpc (undefined reference to __atomic_store_8)

Processing commands for cont...@bugs.debian.org: > tags 797228 + patch Bug #797228 [src:filezilla] filezilla: FTBFS on mips/mipsel/powerpc (undefined reference to __atomic_store_8) Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 797228: http:/

Bug#797228: filezilla: FTBFS on mips/mipsel/powerpc (undefined reference to __atomic_store_8)

tags 797228 + patch thanks Hello, I have attached patch created from upstream source: 2015-08-16 17:57 codesquid, revision 6931 * M /FileZilla3/trunk/configure.ac

Processed: seqdiag: diff for NMU version 0.9.3-4.1

Processing control commands: > tags 796481 + patch Bug #796481 [src:seqdiag] seqdiag: FTBFS: TypeError: coercing to Unicode: need string or buffer, bool found Added tag(s) patch. > tags 796481 + pending Bug #796481 [src:seqdiag] seqdiag: FTBFS: TypeError: coercing to Unicode: need string or buff

Bug#796481: seqdiag: diff for NMU version 0.9.3-4.1

Control: tags 796481 + patch Control: tags 796481 + pending Dear maintainer, I've prepared an NMU for seqdiag (versioned as 0.9.3-4.1) which I'll have a...@debian.org review and potentially upload. Please feel free to tell me if we should delay the upload. Regards, Stein Magnus Jodal diff -Nru s

Bug#797793: Test failure of python-htseq on 32bit arches

Hi Simon, I guess/hope you know that the Debian Med team (namely Diane Trout) packaged htslib for the Debian distribution. Recently we upgraded to the latest version (0.6.1p1) which caused some trouble with one test (out of 37) for 32 bit architectures. The issue is reported as Debian bug #79779

Processed: Re: Bug#795518: selinux-utils: neither labels set or SELinux enabled

Processing control commands: > severity -1 important Bug #795518 [selinux-basics] selinux-utils: neither labels set or SELinux enabled Severity set to 'important' from 'grave' -- 795518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795518 Debian Bug Tracking System Contact ow...@bugs.debian

Bug#798357: libnetcdf-cxx-legacy-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/share/info/netcdf-cxx.info.gz

Package: libnetcdf-cxx-legacy-dev Version: 4.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts 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 because it tries to over

Bug#795518: selinux-utils: neither labels set or SELinux enabled

Control: severity -1 important On Fri, 14 Aug 2015, Richard Jasmin wrote: > when using "sudo selinux-activate" to enable SELinux and setting rcS properly, > nothing actually happens once you reboot.The system respawns itself into a > working state once more but SELinux remains disabled with no clu

Processed: fixed 795597 in 1.0~~pre-1+git150409-1, tagging 795597

Processing commands for cont...@bugs.debian.org: > # Now that we know that this has been fixed upstream, we can use version > tracking instead of the jessie tag > fixed 795597 1.0~~pre-1+git150409-1 Bug #795597 [conkeror] Conkeror crashes on start up with SyntaxError, ReferenceError and TypeErro

Processed: Re: Bug#795597: Conkeror crashes on start up with SyntaxError, ReferenceError and TypeError

Processing control commands: > tag -1 = confirmed jessie patch Bug #795597 [conkeror] Conkeror crashes on start up with SyntaxError, ReferenceError and TypeError Added tag(s) patch and confirmed; removed tag(s) unreproducible and moreinfo. > severity -1 grave Bug #795597 [conkeror] Conkeror crash

Bug#798355: colord-sensor-argyll: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/x86_64-linux-gnu/colord-sensors/libcolord_sensor_argyll.so

Package: colord-sensor-argyll Version: 1.2.11-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts 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 because it tries to overw

Processed: severity of 798348 is serious

Processing commands for cont...@bugs.debian.org: > severity 798348 serious Bug #798348 [ruby-tzinfo] ruby-tzinfo: Loading tzdata may break because of encoding Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 798348: http://b

Bug#798353: libsndio-dev and libroar-dev: error when trying to install together

Followup-For: Bug #798353 libsndio-dev still needs to add Breaks+Replaces against the buggy libroar-dev versions. Andreas

Bug#777934: libalog: ftbfs with GCC-5

Package: src:libalog Followup-For: Bug #777934 Hello. You may be interested in the last commit of branch org.debian.libgnatcoll in the Ada France monotone repository, closing the exact same issue.

  1   2   >