Bug#836669: caja: Crashes due to theme errors

Control: reassign -1 mate-themes Control: found -1 3.20.8-1 Re-assigning to mate-themes On Sa 10 Sep 2016 01:40:26 CEST, Frank McCormick wrote: Package: caja Version: 1.14.2-1 Followup-For: Bug #836669 Caja just stated doing this: click on home icon on desktop...all desktop icons disap

Processed: Re: Bug#836669: caja: Crashes due to theme errors

Processing control commands: > reassign -1 mate-themes Bug #836669 [caja] caja: Crashes due to theme errors Bug reassigned from package 'caja' to 'mate-themes'. No longer marked as found in versions caja/1.14.2-1. Ignoring request to alter fixed versions of bug #836669 to the same values previous

Processed: reassign 837495 to src:gnome-shell-extension-suspend-button, forcibly merging 837592 837495

Processing commands for cont...@bugs.debian.org: > reassign 837495 src:gnome-shell-extension-suspend-button Bug #837495 [gnome-shell-extension-suspend-button] gnome-shell-extension-suspend-button: uninstallable in sid: Depends: gnome-shell (< 3.21) but 3.21.91-2 is to be installed Bug reassigned

Bug#837012: tachyon: FTBFS: ld: tachyon_ogl-glwin.o: undefined reference to symbol 'XNextEvent'

Hi, I've uploaded an NMU of tachyon that fixes this to DELAYED/5. The debdiff is: dpkg-source: warning: extracting unsigned source package (/srv/build/tachyon/tachyon_0.99~b6+dsx-5.1.dsc) diff -Nru tachyon-0.99~b6+dsx/debian/changelog tachyon-0.99~b6+dsx/debian/changelog --- tachyon-0.99~b6+dsx/

Bug#836642: marked as done (openafs: please drop the build dependency on hardening-wrapper)

Your message dated Tue, 13 Sep 2016 05:25:55 + with message-id and subject line Bug#836642: fixed in openafs 1.6.18.3-2 has caused the Debian Bug report #836642, regarding openafs: please drop the build dependency on hardening-wrapper to be marked as done. This means that you claim that the p

Bug#837619: marked as done (jdeb: FTBFS: Failed tests: org.vafer.jdeb.signing.PGPSignerTestCase#testClearSign)

Your message dated Tue, 13 Sep 2016 05:21:36 + with message-id and subject line Bug#837619: fixed in jdeb 1.5-3 has caused the Debian Bug report #837619, regarding jdeb: FTBFS: Failed tests: org.vafer.jdeb.signing.PGPSignerTestCase#testClearSign to be marked as done. This means that you clai

Bug#837012: marked as done (tachyon: FTBFS: ld: tachyon_ogl-glwin.o: undefined reference to symbol 'XNextEvent')

Your message dated Tue, 13 Sep 2016 04:33:17 + with message-id and subject line Bug#837012: fixed in tachyon 0.99~b6+dsx-6 has caused the Debian Bug report #837012, regarding tachyon: FTBFS: ld: tachyon_ogl-glwin.o: undefined reference to symbol 'XNextEvent' to be marked as done. This means

Bug#836585: celery: FTBFS in testing (failing tests)

On Sun, 4 Sep 2016 11:54:01 +0200 (CEST) Santiago Vila wrote: > 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: I can't reproduce this build failure using `pdebuild --debbuildopts -A`. Which

Bug#835280: marked as pending

tag 835280 pending thanks Hello, Bug #835280 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: http://git.debian.org/?p=pkg-openoffice/libabw.git;a=commitdiff;h=7a7d0d3 --- commit 7a7d0d326963e9fddc425c59af5eb0d8

Processed: Bug#835280 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 835280 pending Bug #835280 {Done: Rene Engelhard } [src:libabw] libabw: FTBFS: libabw-0.1.so: undefined reference to `boost::system::system_category()' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need as

Bug#816593: (no subject)

Hi, after checking some information, I guessyour error will be fixed if 1. you add -lrt flag appropriately. or 2. you upgrade glibc (libc6 package) from 2.13 to 2.19. For more detail, you can see this thread: http://stackoverflow.com/questions/2418157/ubuntu-linux-c-error-undefined-reference-to

Bug#837085: marked as done (neurodebian-archive-keyring: fails to install: Error: gnupg, gnupg2 and gnupg1 do not seem to be installed, )

Your message dated Tue, 13 Sep 2016 01:34:03 + with message-id and subject line Bug#837085: fixed in neurodebian 0.37.5 has caused the Debian Bug report #837085, regarding neurodebian-archive-keyring: fails to install: Error: gnupg, gnupg2 and gnupg1 do not seem to be installed, to be marked

Bug#837012: tachyon: FTBFS: ld: tachyon_ogl-glwin.o: undefined reference to symbol 'XNextEvent'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello Lucas, thanks for the report. On 07/09/16 23:18, Lucas Nussbaum wrote: > Source: tachyon > Version: 0.99~b6+dsx-5 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20160906 qa-ftbfs > Justificati

Bug#836347: gkrellweather: weather.noaa.gov has been shut down

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This has fixed the problem for me as well. Thank you Roland! Cheers, Dario Susman On Fri, 02 Sep 2016 01:18:06 +0200 Roland Hieber wrote: > Package: gkrellweather > Version: 2.0.8-2 > Severity: grave > Tags: patch > Justification: renders pac

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

Yes! At long last 231-6 seems to have cleared the systemd issue I was observing on Raspberry Pi: -- root@pi ~ # systemctl status ● pi State: running Jobs: 0 queued Failed: 0 units

Processed (with 1 error): forcibly merging 837592 837495

Processing commands for cont...@bugs.debian.org: > forcemerge 837592 837495 Bug #837592 [src:gnome-shell-extension-suspend-button] gnome-shell-extension-suspend-button: Not compatible with gnome-shell 3.21.x/3.22 Unable to merge bugs because: package of #837495 is 'gnome-shell-extension-suspend-

Bug#835742: marked as done (golang-google-cloud: FTBFS: dh_auto_build: go install -v -p 1 google.golang.org/cloud google.golang.org/cloud/bigquery google.golang.org/cloud/bigtable google.golang.org/cl

Your message dated Mon, 12 Sep 2016 23:22:49 + with message-id and subject line Bug#835742: fixed in golang-google-cloud 0.0~git20160615-1 has caused the Debian Bug report #835742, regarding golang-google-cloud: FTBFS: dh_auto_build: go install -v -p 1 google.golang.org/cloud google.golang.or

Bug#837624: golang-goleveldb: FTBFS in testing (failing tests)

Note: Yes, I know that this bug is apparently similar to #834959, but I have been advised that it's better to err on the side of filing duplicate bugs than mixing two different problems in the same bug report (which usually results in a big mess). Whether they are the same or not, I don't really k

Processed: Re: Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

Processing commands for cont...@bugs.debian.org: > retitle 837613 libconfig-model-itself-perl: FTBFS in sid (failing tests) Bug #837613 {Done: gregor herrmann } [src:libconfig-model-itself-perl] libconfig-model-itself-perl: FTBFS in testing (failing tests) Changed Bug title to 'libconfig-model-i

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

retitle 837613 libconfig-model-itself-perl: FTBFS in sid (failing tests) thanks Here is the build log in sid. It uses libconfig-model-perl version 2.090-1. My guess is that this is not really the same bug (well, it may still be "essentially the same bug", just in a different package :-). Ok to r

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

I am not even sure that we are doing it right. I've just built libconfig-model-itself-perl in sid. The libconfig-model-perl version used in the build-dependency was 2.090-1, which is supposed to be the fixed version. And the package failed to build as well. So: Are you sure that it was libconfi

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

On Mon, 12 Sep 2016 23:24:03 +0100, Santiago Vila wrote: > > > If, OTOH, you mean that the reason this package fails is in another > > > package which is in the build-depends of this one, then please use > > > affects to avoid more duplicates. > > Everything there already :) > > https://bugs.debia

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

affects 837133 = src:libconfig-model-itself-perl thanks On Tue, Sep 13, 2016 at 12:10:09AM +0200, gregor herrmann wrote: > On Mon, 12 Sep 2016 22:57:08 +0100, Santiago Vila wrote: > > > > This is a duplicate of #837133 which is fixed since yesterday, > > > therefore closing this bug report. > > I

Processed: Re: Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

Processing commands for cont...@bugs.debian.org: > affects 837133 = src:libconfig-model-itself-perl Bug #837133 {Done: Dominique Dumont } [libconfig-model-perl] Dump of value containing hash is broken Removed indication that 837133 affects libconfig-model-itself-perl Added indication that 837133

Bug#836615: marked as done (array-info: please drop the build dependency on hardening-wrapper)

Your message dated Mon, 12 Sep 2016 22:19:43 + with message-id and subject line Bug#836615: fixed in array-info 0.16-2 has caused the Debian Bug report #836615, regarding array-info: please drop the build dependency on hardening-wrapper to be marked as done. This means that you claim that the

Bug#837534: marked as done (apt-listchanges: postinst runs a Python script out of /tmp/)

Your message dated Mon, 12 Sep 2016 22:19:38 + with message-id and subject line Bug#837534: fixed in apt-listchanges 3.4 has caused the Debian Bug report #837534, regarding apt-listchanges: postinst runs a Python script out of /tmp/ to be marked as done. This means that you claim that the pro

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

On Mon, 12 Sep 2016 23:03:19 +0100, Santiago Vila wrote: > > fixed since yesterday, > BTW: I usually build only packages which are in the same version in > testing and unstable (i.e. in sync), so if you want to apply bayesian > analysis to my bug reports, you can assign a high probability that > w

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

On Mon, 12 Sep 2016 22:57:08 +0100, Santiago Vila wrote: > > This is a duplicate of #837133 which is fixed since yesterday, > > therefore closing this bug report. > It may not be a duplicate because the package in #837133 is > libconfig-model-perl > and the package that FTBFS now is libconfig-mod

Bug#837622: python-stetl: FTBFS in testing (failing tests)

Package: src:python-stetl Version: 1.0.9+ds-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: --

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

On Mon, Sep 12, 2016 at 11:39:27PM +0200, gregor herrmann wrote: > fixed since yesterday, BTW: I usually build only packages which are in the same version in testing and unstable (i.e. in sync), so if you want to apply bayesian analysis to my bug reports, you can assign a high probability that wh

Bug#837620: w3-dtd-mathml: FTBFS: dh_installxmlcatalogs: Unexpected debhelper version format

Source: w3-dtd-mathml Version: 2.0.0.0-5 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, w3-dtd-mathml fails to build from source in unstable/am

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

On Mon, Sep 12, 2016 at 11:39:27PM +0200, gregor herrmann wrote: > This is a duplicate of #837133 which is fixed since yesterday, > therefore closing this bug report. It may not be a duplicate because the package in #837133 is libconfig-model-perl and the package that FTBFS now is libconfig-model

Bug#837619: jdeb: FTBFS: Failed tests: org.vafer.jdeb.signing.PGPSignerTestCase#testClearSign

Source: jdeb Version: 1.5-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, jdeb fails to build from source in unstable/amd64: [..] Adding

Bug#837615: [debian-mysql] Bug#837615: Don't include in stretch

On Mon, Sep 12, 2016 at 10:42:31PM +0100, Robie Basak wrote: > On Mon, Sep 12, 2016 at 11:37:49PM +0200, Moritz Muehlenhoff wrote: > > As per previous discussion, don't include in stretch/blocker bug to > > keep it out. > > What previous discussion? I'm aware of a decision for things to depend > o

Bug#837618: docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected debhelper version format

Source: docbook-slides Version: 3.4.0-5 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, docbook-slides fails to build from source in unstable/am

Bug#837615: [debian-mysql] Bug#837615: Don't include in stretch

On Mon, Sep 12, 2016 at 11:37:49PM +0200, Moritz Muehlenhoff wrote: > As per previous discussion, don't include in stretch/blocker bug to > keep it out. What previous discussion? I'm aware of a decision for things to depend on src:mariadb-10.0 instead, not of any decision to keep src:mysql-5.6 out

Bug#837613: marked as done (libconfig-model-itself-perl: FTBFS in testing (failing tests))

Your message dated Mon, 12 Sep 2016 23:39:27 +0200 with message-id <20160912213927.slz6fouc2zgvh...@jadzia.comodo.priv.at> and subject line Re: Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests) has caused the Debian Bug report #837613, regarding libconfig-model-itself-perl:

Bug#837615: Don't include in stretch

Source: mysql-5.6 Severity: serious As per previous discussion, don't include in stretch/blocker bug to keep it out. Cheers, Moritz

Bug#834281: libgnupg-interface-perl not migrating to testing

On Mon, 12 Sep 2016 20:40:34 +0100, Adam D. Barratt wrote: > On Mon, 2016-09-12 at 20:37 +0200, intrigeri wrote: > > Can anyone please help me understand about why libgnupg-interface-perl > > is not migrating to testing? > The log - https://release.debian.org/britney/update_output.txt - should > b

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

Package: src:libconfig-model-itself-perl Version: 2.005-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: --

Bug#837614: python-geopandas: FTBFS in testing (failing tests)

Package: src:python-geopandas Version: 0.2.1-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: -

Processed: found 836259 in 2.1.11-7

Processing commands for cont...@bugs.debian.org: > found 836259 2.1.11-7 Bug #836259 [src:gnupg2] gnupg2: accesses the internet during build Marked as found in versions gnupg2/2.1.11-7. > thanks Stopping processing here. Please contact me if you need assistance. -- 836259: http://bugs.debian.org

Bug#818448: fixed in imapcopy 1.04-2.1

On 12/09/16 20:51, Gianfranco Costamagna wrote: Gianfranco, as per Policy §4.4, please put your own name in the changelog trailer when making an upload. well, it seems unfair wrt Peter, IMO what the changelog should look like in a case like this is imapcopy (1.04-2.1) unstable; ur

Processed: Re: Bug#837495: gnome-shell-extension-suspend-button: uninstallable in sid: Depends: gnome-shell (< 3.21) but 3.21.91-2 is to be installed

Processing control commands: > forwarded -1 > https://github.com/laserb/gnome-shell-extension-suspend-button/issues/20 Bug #837495 [gnome-shell-extension-suspend-button] gnome-shell-extension-suspend-button: uninstallable in sid: Depends: gnome-shell (< 3.21) but 3.21.91-2 is to be installed Se

Bug#837495: gnome-shell-extension-suspend-button: uninstallable in sid: Depends: gnome-shell (< 3.21) but 3.21.91-2 is to be installed

Control: forwarded -1 https://github.com/laserb/gnome-shell-extension-suspend-button/issues/20 Control: tags -1 upstream On Mon, Sep 12, 2016 at 01:33:27AM +0200, Andreas Beckmann wrote: > Package: gnome-shell-extension-suspend-button > Version: 0~git20160525-1 > Severity: serious > User: debian.

Bug#837594: gnome-shell-extension-autohidetopbar: Not compatible with gnome-shell 3.21.x/3.22

Package: src:gnome-shell-extension-autohidetopbar Followup-For: Bug #837594 Control: tags -1 upstream Control: forwarded -1 https://github.com/mlutfy/hidetopbar/issues/107 Upstream has already a bug recorded, setting forwarded accordingly. -- tobi -- System Information: Debian Release: stretch

Bug#834683: [pkg-gnupg-maint] Bug#834683: fixed in mini-buildd 1.0.17

On Mon, Sep 12, 2016 at 07:34:09PM +0200, Daniel Kahn Gillmor wrote: > An even easier approach might be to do the following within the build: > > * ln -sf /dev/urandom /dev/random > > why would we need the blocking kernel RNG in the buildd anyway? Either that, or maybe a build-depends on a pa

Processed: Re: gnome-shell-extension-autohidetopbar: Not compatible with gnome-shell 3.21.x/3.22

Processing control commands: > tags -1 upstream Bug #837594 [src:gnome-shell-extension-autohidetopbar] gnome-shell-extension-autohidetopbar: Not compatible with gnome-shell 3.21.x/3.22 Added tag(s) upstream. > forwarded -1 https://github.com/mlutfy/hidetopbar/issues/107 Bug #837594 [src:gnome-sh

Processed: your mail

Processing commands for cont...@bugs.debian.org: > found 829752 1.0.4 Bug #829752 [netfilter-persistent] netfilter-persistent systemd service does not lock the network if netfilter-persistent wrapper is failing at system bootup Marked as found in versions iptables-persistent/1.0.4. > thanks Stopp

Bug#834683: [pkg-gnupg-maint] Bug#834683: fixed in mini-buildd 1.0.17

Hi Santiago and all-- On Sun 2016-09-11 21:30:22 +0200, Santiago Vila wrote: > Well, maybe the problem has always been there. > > Maybe official autobuilders have a lot of entropy and we have never > found the problem there, but IMHO we should not take that for granted > in the general case. I wo

Bug#818448: fixed in imapcopy 1.04-2.1

Hi >This upload looks like it was made by Peter Green. >But I was told on IRC that his only involvement was posting a patch to >the BTS (with a comment that the patch was only build-tested). >The actual upload was made by Gianfranco Costamagna. yes this is true >Gianfranco, as per Policy §4.4,

Bug#836505: marked as done (elog: CVE-2016-6342: posting entry as arbitrary username by improper authentication)

Your message dated Mon, 12 Sep 2016 19:48:47 + with message-id and subject line Bug#836505: fixed in elog 3.1.2-1-1 has caused the Debian Bug report #836505, regarding elog: CVE-2016-6342: posting entry as arbitrary username by improper authentication to be marked as done. This means that yo

Bug#818448: fixed in imapcopy 1.04-2.1

* Peter Michael Green , 2016-09-11, 16:20: Changed-By: Peter Michael Green Description: imapcopy - IMAP backup, copy and migration tool Closes: 818448 Changes: imapcopy (1.04-2.1) unstable; urgency=medium . * Non-maintainer upload. * Fix build with fpc 3.0.0 (Closes: 818448) This upload

Bug#837530: [Debichem-devel] Bug#837530: elpa: FTBFS due to symbols changes

On 12 September 2016 at 11:00, Bas Couwenberg wrote: > The upload of openmpi (2.0.1-3) to unstable has triggered an > uncoordinated transition (#836917). Unfortunately your package FTBFS due > to symbols changes: Interesting that these two symbols disappeared everywhere except on amd64. I've just

Bug#837604: openjpeg2: CVE-2016-7163: Integer overflow in opj_pi_create_decode

Source: openjpeg2 Version: 2.1.0-2 Severity: grave Tags: security upstream patch Control: fixed -1 2.1.0-2+deb8u1 Hi, the following vulnerability was published for openjpeg2. CVE-2016-7163[0]: Integer overflow in opj_pi_create_decode If you fix the vulnerability please also make sure to include

Processed: openjpeg2: CVE-2016-7163: Integer overflow in opj_pi_create_decode

Processing control commands: > fixed -1 2.1.0-2+deb8u1 Bug #837604 [src:openjpeg2] openjpeg2: CVE-2016-7163: Integer overflow in opj_pi_create_decode Marked as fixed in versions openjpeg2/2.1.0-2+deb8u1. -- 837604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837604 Debian Bug Tracking Syst

Bug#811818: crrcsim: FTBFS with GCC 6: no match for

Control: tags -1 patch Dear maintainer, please find enclosed a patch that fixes building with gcc-6. Note that the patch makes the assumption that a newline was expected in the output instead of std::cerr. best regards, Gert Description: Correct compilation with gcc-6 The patch assumes th

Processed: Re: crrcsim: FTBFS with GCC 6: no match for

Processing control commands: > tags -1 patch Bug #811818 [crrcsim] crrcsim: FTBFS with GCC 6: no match for Added tag(s) patch. -- 811818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#821976: marked as done (crack: Build arch:all+arch:any but is missing build-{arch,indep} targets)

Your message dated Mon, 12 Sep 2016 18:49:36 + with message-id and subject line Bug#821976: fixed in crack 5.0a-9.4 has caused the Debian Bug report #821976, regarding crack: Build arch:all+arch:any but is missing build-{arch,indep} targets to be marked as done. This means that you claim tha

Bug#817319: marked as done (crack: Mandatory debian/compat for debhelper)

Your message dated Mon, 12 Sep 2016 18:49:35 + with message-id and subject line Bug#817319: fixed in crack 5.0a-9.4 has caused the Debian Bug report #817319, regarding crack: Mandatory debian/compat for debhelper to be marked as done. This means that you claim that the problem has been dealt

Bug#817411: marked as done (crack: Removal of debhelper compat 4)

Your message dated Mon, 12 Sep 2016 18:49:36 + with message-id and subject line Bug#817411: fixed in crack 5.0a-9.4 has caused the Debian Bug report #817411, regarding crack: Removal of debhelper compat 4 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#837599: autotrace: CVE-2016-7392: heap-based buffer overflow in pstoedit_suffix_table_init (output-pstoedit.c)

Source: autotrace Version: 0.31.1-16 Severity: grave Tags: security upstream Hi, the following vulnerability was published for autotrace. CVE-2016-7392[0]: heap-based buffer overflow in pstoedit_suffix_table_init (output-pstoedit.c) If you fix the vulnerability please also make sure to include

Bug#837534: apt-listchanges: postinst runs a Python script out of /tmp/

Hi, On Mon, 12 Sep 2016, Robert Luberda wrote: > Thanks, I will create temporary directory instead: [...] > python3 -B "$temp" "$@" > > Do you think this will be OK? Yes. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Lea

Processed: reassign 837468 to libcsound64-dev, forcibly merging 837273 837468

Processing commands for cont...@bugs.debian.org: > reassign 837468 libcsound64-dev Bug #837468 [src:csoundqt] csoundqt: FTBFS: Project ERROR: A valid csound library was not found. Bug reassigned from package 'src:csoundqt' to 'libcsound64-dev'. No longer marked as found in versions csoundqt/0.9.2

Processed (with 1 error): forcibly merging 837273 837468

Processing commands for cont...@bugs.debian.org: > forcemerge 837273 837468 Bug #837273 {Done: Felipe Sateler } [libcsound64-dev] libcsound64-dev: missing .so symlink Unable to merge bugs because: package of #837468 is 'src:csoundqt' not 'libcsound64-dev' Failed to forcibly merge 837273: Did not

Bug#811432: Krita no longer part of Calligra

Hi, In data lunedì 12 settembre 2016 14:56:12 CEST, juichenieder-deb...@yahoo.co.uk ha scritto: > root/debian/changelog > This contains only the line for this package, this seems a bit odd to ditch > the > changelog from before. While Krita technically goes in to debian as a new > package, > i

Bug#837534: apt-listchanges: postinst runs a Python script out of /tmp/

Raphaël Hertzog writes: > > You should thus create that temporary file in a root-owned > directory which is specific to apt-listchanges. Thanks, I will create temporary directory instead: tempdir=`mktemp --directory --sufix=.aptlc` trap "rm -rf $tempdir" EXIT temp="$tempdir/debconf-

Processed: [bts-link] source package src:request-tracker4

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:request-tracker4 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.al

Processed: Re: Bug#837595: gnome-shell-pomodoro: Not compatible with gnome-shell 3.21.x/3.22

Processing control commands: > forwarded -1 https://github.com/codito/gnome-pomodoro/issues/236 Bug #837595 [src:gnome-shell-pomodoro] gnome-shell-pomodoro: Not compatible with gnome-shell 3.21.x/3.22 Set Bug forwarded-to-address to 'https://github.com/codito/gnome-pomodoro/issues/236'. -- 837

Bug#837595: gnome-shell-pomodoro: Not compatible with gnome-shell 3.21.x/3.22

Control: forwarded -1 https://github.com/codito/gnome-pomodoro/issues/236 Hi Michael, Thanks for your report. I was going to release the latest version of the package this week, but I see it's still not claiming compatibility with these versions of gnome-shell, so checking with upstream. Joseph

Processed: [bts-link] source package src:python-scipy

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:python-scipy > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth

Bug#837594: gnome-shell-extension-autohidetopbar: Not compatible with gnome-shell 3.21.x/3.22

Source: gnome-shell-extension-autohidetopbar Version: 20160828-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-3-22 Hi, your package gnome-shell-extension-autohidetopbar declares a strictly versioned dependency on gnome-shell. We've uploaded gnome-she

Bug#837593: gnome-shell-extension-redshift: Not compatible with gnome-shell 3.21.x/3.22

Source: gnome-shell-extension-redshift Version: 3.20.1-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-3-22 Hi, your package gnome-shell-extension-redshift declares a strictly versioned dependency on gnome-shell. We've uploaded gnome-shell 3.21.91 to

Bug#837595: gnome-shell-pomodoro: Not compatible with gnome-shell 3.21.x/3.22

Source: gnome-shell-pomodoro Version: 0.11.2-2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-3-22 Hi, your package gnome-shell-pomodoro declares a strictly versioned dependency on gnome-shell. We've uploaded gnome-shell 3.21.91 to unstable, which make

Bug#837592: gnome-shell-extension-suspend-button: Not compatible with gnome-shell 3.21.x/3.22

Source: gnome-shell-extension-suspend-button Version: 0~git20160525-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-3-22 Hi, your package gnome-shell-extension-suspend-button declares a strictly versioned dependency on gnome-shell. We've uploaded gnom

Bug#836536: ruby-concurrent: FTBFS too much often (failed examples)

On Mon, Sep 12, 2016 at 11:12:26AM +0530, Balasankar C wrote: > On Sat, 3 Sep 2016 21:49:13 +0200 (CEST) Santiago Vila > wrote: > > BTW: I think the "Randomized with seed xxx" above is a bad idea. > > Maintainers often ask bug reporters for "a way to reproduce the error". > > But if the build i

Processed: Re: [Pkg-alsa-devel] Bug#837590: alsa-tools FTBFS on armel: gcc-6 narrowing conversions

Processing control commands: > forwarded -1 > http://mailman.alsa-project.org/pipermail/alsa-devel/2016-September/112697.html Bug #837590 [src:alsa-tools] alsa-tools FTBFS on armel: gcc-6 narrowing conversions Set Bug forwarded-to-address to 'http://mailman.alsa-project.org/pipermail/alsa-devel

Bug#837590: [Pkg-alsa-devel] Bug#837590: alsa-tools FTBFS on armel: gcc-6 narrowing conversions

Control: forwarded -1 http://mailman.alsa-project.org/pipermail/alsa-devel/2016-September/112697.html * Helmut Grohne [2016-09-12 18:23 +0200]: > Source: alsa-tools > Version: 1.1.0-1 > Severity: serious > > I noticed that alsa-tools fails to cross build from source for armel due > to gcc-6 na

Bug#837536: marked as done (mpi4py: FTBFS with openmpi 2.0.1-4)

Your message dated Mon, 12 Sep 2016 16:43:50 + with message-id and subject line Bug#837536: fixed in openmpi 2.0.1-5 has caused the Debian Bug report #837536, regarding mpi4py: FTBFS with openmpi 2.0.1-4 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#835075: marked as done (libmail-gnupg-perl: FTBFS: Failed 1/10 test programs. 0/4 subtests failed.)

Your message dated Mon, 12 Sep 2016 16:37:46 + with message-id and subject line Bug#835075: fixed in libmail-gnupg-perl 0.23-1 has caused the Debian Bug report #835075, regarding libmail-gnupg-perl: FTBFS: Failed 1/10 test programs. 0/4 subtests failed. to be marked as done. This means that

Bug#822049: marked as done (linux-wlan-ng: Build arch:all+arch:any but is missing build-{arch,indep} targets)

Your message dated Mon, 12 Sep 2016 16:42:21 + with message-id and subject line Bug#822049: fixed in linux-wlan-ng 0.2.9+dfsg-6 has caused the Debian Bug report #822049, regarding linux-wlan-ng: Build arch:all+arch:any but is missing build-{arch,indep} targets to be marked as done. This mean

Bug#837591: leaves user (and files?) behind on purge

Package: irker Version: 2.13+dfsg-1 Severity: serious Version 2.13 of the debian package introduces a regression where the `irker` user is left behind when the package is removed. I understand why that was done (files were left behind unowned), but I was expecting the user to be removed during pu

Bug#837590: alsa-tools FTBFS on armel: gcc-6 narrowing conversions

Source: alsa-tools Version: 1.1.0-1 Severity: serious I noticed that alsa-tools fails to cross build from source for armel due to gcc-6 narrowing conversion issues. Issues about narrowing conversions are generally not cross compilation specific and reproducible natively. Thus filing at RC severity

Bug#835075: [PATCH] use fake-pinentry (Closes: #835075)

On Sun, 11 Sep 2016 16:38:05 +0200, gregor herrmann wrote: > > > 3) This is in schroot-on-lvm. And here unmounting fails because of the > > >running gpg-agents leaving my schroot/lvm setup in a sad state. > > right, but this is a different issue, related to gpg-agent not. > > terminating rapid

Bug#823803: [Debichem-devel] NMU for libint2 : FTBFS (blocking openmpi transition)

Hi, On Mon, Sep 12, 2016 at 11:07:59AM +0100, Alastair McKinstry wrote: > I've uploaded an NMU for libint2 to fix a FTBFS that was blocking the > openmpi2 transition. > > Please find the debdiff attached. According to your changelog, the debdiff appears to be backwards, or am I reading it wrong?

Bug#811432: Krita no longer part of Calligra

Thanks Pino, A few comments/questions... root/debian/changelog This contains only the line for this package, this seems a bit odd to ditch the changelog from before. While Krita technically goes in to debian as a new package, it just replaces the older krita package, and I do not presume that u

Bug#750228: package python-glpk

Control: tags 750228 +help This bug requests to update GLPK's dependency to a newer version; but this is a rather substantial update, as changes in GLPK's interface imply a deep restructuring in python-glpk. João Pedro

Processed: package python-glpk

Processing control commands: > tags 750228 +help Bug #750228 [python-glpk] python-glpk: FTBFS - build-dep libglpk-dev (<< 4.53) is unsatisfiable Added tag(s) help. -- 750228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750228 Debian Bug Tracking System Contact ow...@bugs.debian.org with pr

Bug#833020: marked as done (ldc: FTBFS on armel, powerpc)

Your message dated Mon, 12 Sep 2016 12:35:51 + with message-id and subject line Bug#833020: fixed in ldc 1:1.1.0git216c112-1 has caused the Debian Bug report #833020, regarding ldc: FTBFS on armel, powerpc to be marked as done. This means that you claim that the problem has been dealt with. I

Processed: tagging 836638, tagging 836628

Processing commands for cont...@bugs.debian.org: > tags 836638 - pending Bug #836638 [nagios3] nagios3: please drop the build dependency on hardening-wrapper Removed tag(s) pending. > tags 836628 + pending Bug #836628 [gsmartcontrol] gsmartcontrol: please drop the build dependency on hardening-w

Bug#818926: perl6-panda: panda doesn't start up / find needed libraries

On Monday, 5 September 2016 23:29:27 CEST gregor herrmann wrote: > Maybe zef is in option: > https://github.com/ugexe/zef Thanks for the hint. Unfortuantely, I don't know when I'll find the time to look at this issue :-/ All the best -- https://github.com/dod38fr/ -o- http://search.cpan.org

Bug#837133: marked as done (Dump of value containing hash is broken)

Your message dated Mon, 12 Sep 2016 11:50:08 + with message-id and subject line Bug#837133: fixed in libconfig-model-perl 2.090-1 has caused the Debian Bug report #837133, regarding Dump of value containing hash is broken to be marked as done. This means that you claim that the problem has be

Processed: tagging 769580, tagging 836638

Processing commands for cont...@bugs.debian.org: > tags 769580 + pending Bug #769580 [gsmartcontrol] [GSmartControl] New Homepage Added tag(s) pending. > tags 836638 + pending Bug #836638 [nagios3] nagios3: please drop the build dependency on hardening-wrapper Added tag(s) pending. > thanks Stopp

Processed: affects 837133

Processing commands for cont...@bugs.debian.org: > affects 837133 libconfig-model-itself-perl Bug #837133 [libconfig-model-perl] Dump of value containing hash is broken Added indication that 837133 affects libconfig-model-itself-perl > thanks Stopping processing here. Please contact me if you nee

Processed: reassign 837133 to libconfig-model-perl

Processing commands for cont...@bugs.debian.org: > reassign 837133 libconfig-model-perl 2.089-1 Bug #837133 [libconfig-model-itself-perl] Dump of value containing hash is broken Bug reassigned from package 'libconfig-model-itself-perl' to 'libconfig-model-perl'. No longer marked as found in vers

Processed: retitle 837133 to Dump of value containing hash is broken

Processing commands for cont...@bugs.debian.org: > retitle 837133 Dump of value containing hash is broken Bug #837133 [libconfig-model-itself-perl] libconfig-model-itself-perl: FTBFS: t/load_write_itself.t failure Changed Bug title to 'Dump of value containing hash is broken' from 'libconfig-mod

Processed: (no subject)

Processing commands for cont...@bugs.debian.org: > forwarded 836669 https://github.com/mate-desktop/caja/issues/634 Bug #836669 [caja] caja: Crashes due to theme errors Set Bug forwarded-to-address to 'https://github.com/mate-desktop/caja/issues/634'. > End of message, stopping processing here.

Bug#836391: gradle: recent update of jsch to version 0.1.54 breaks Gradle based projects

We did a binary upload to Debian, but seems that Ubuntu syncs the packages by source and builds them again. I think someone at the Ubuntu side should do a binary upload to e.g. 2.13-4ubuntu1. I filed a bug about this to Launchpad.

Bug#836846: marked as done (Remove "Recommends: socklog-run" due to clash with systemd)

Your message dated Mon, 12 Sep 2016 10:28:12 + with message-id and subject line Bug#836846: fixed in runit 2.1.2-8 has caused the Debian Bug report #836846, regarding Remove "Recommends: socklog-run" due to clash with systemd to be marked as done. This means that you claim that the problem ha

Bug#836961: marked as done (r8168-dkms: Compilation error with linux-image-4.7.0-1-amd64)

Your message dated Mon, 12 Sep 2016 10:27:31 + with message-id and subject line Bug#836961: fixed in r8168 8.042.00-2 has caused the Debian Bug report #836961, regarding r8168-dkms: Compilation error with linux-image-4.7.0-1-amd64 to be marked as done. This means that you claim that the probl

  1   2   >