Bug#893651: marked as done (isso FTBFS with node-almond 0.3.3+dfsg-1)

Your message dated Thu, 04 Oct 2018 05:20:04 + with message-id and subject line Bug#893651: fixed in isso 0.10.6+git20181001+dfsg-1 has caused the Debian Bug report #893651, regarding isso FTBFS with node-almond 0.3.3+dfsg-1 to be marked as done. This means that you claim that the problem

Bug#898705: android-platform-libcore 8.1 upload to unstable?

Hello, I maintain a package that depends on libandroid-json-java that will soon to be evicted from testing due to the FTBFS bug (898705) filed against src:android-platform-libcore. Would it be possible for you to upload the newer package in experimental to unstable? If not, would it be possible

Bug#910258: debmake-doc parallel FTBFS

Source: debmake-doc Version: 1.11-1 Severity: serious Tags: ftbfs debmake-doc randomly fails to build from source when performing a parallel build (difficult to trigger). The issue lies in test case debhello-3.0. Its Makefile says: | all: data/hello.desktop po/ja.mo | | data/hello.desktop

Processed: affects 898705

Processing commands for cont...@bugs.debian.org: > affects 898705 zabbix Bug #898705 {Done: Saif Abdul Cassim } [src:android-platform-libcore] android-platform-libcore FTBFS with debhelper v11 Added indication that 898705 affects zabbix > thanks Stopping processing here. Please contact me if

Bug#905180: marked as done (libmoe-dev: missing Breaks+Replaces: libmoe1.5 (<< 1.5.8-3))

Your message dated Thu, 04 Oct 2018 02:42:45 + with message-id and subject line Bug#905180: fixed in libmoe 1.5.8-5 has caused the Debian Bug report #905180, regarding libmoe-dev: missing Breaks+Replaces: libmoe1.5 (<< 1.5.8-3) to be marked as done. This means that you claim that the problem

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forwarded 906147 https://github.com/zeroSteiner/smoke-zephyr/issues/4 Bug #906147 [src:python-smoke-zephyr] python-smoke-zephyr ftbfs (failing tests) Warning: Unknown package 'src:python-smoke-zephyr' Set Bug forwarded-to-address to

Bug#906147:

Control: forwarded ! https://github.com/zeroSteiner/smoke-zephyr/issues/4#issuecomment-426854295 thanks Upstream is aware of it -- Samuel Henrique

Bug#909971: marked as done (remove unneeded dependency on backports.ssl-match-hostname)

Your message dated Thu, 04 Oct 2018 01:34:53 + with message-id and subject line Bug#909971: fixed in libcloud 2.3.0-3 has caused the Debian Bug report #909971, regarding remove unneeded dependency on backports.ssl-match-hostname to be marked as done. This means that you claim that the

Processed: Bug #909971 in libcloud marked as pending

Processing control commands: > tag -1 pending Bug #909971 [libcloud] remove unneeded dependency on backports.ssl-match-hostname Added tag(s) pending. -- 909971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#909971: Bug #909971 in libcloud marked as pending

Control: tag -1 pending Hello, Bug #909971 in libcloud reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#910233: libsvn-{dev,java}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

On Wed, Oct 03, 2018 at 07:49:35PM +0200, Andreas Beckmann wrote: > an upgrade test with piuparts revealed that your package installs files > over existing symlinks and possibly overwrites files owned by other > packages. This usually means an old version of the package shipped a > symlink but

Bug#910249: marked as done (Bumping up encryption to AES-256 by default)

Your message dated Wed, 3 Oct 2018 20:45:38 -0400 with message-id and subject line Re: Bug#910249: Bumping up encryption to AES-256 by default has caused the Debian Bug report #910249, regarding Bumping up encryption to AES-256 by default to be marked as done. This means that you claim that the

Bug#910249: Bumping up encryption to AES-256 by default

Jeremy Bicha: > On Wed, Oct 3, 2018 at 6:36 PM procmem wrote: >> Package: gnome-disk-utility >> Version: all >> Severity: serious >> >> Hi. I noticed Gnome Disks uses AES-128 by default instead of AES-256 >> like Debian does out of the box. Having 256 bit symmetric keys is good >> practice for

Bug#906147: python-smoke-zephyr ftbfs (failing tests)

Hello Matthias, Thanks for reporting it, I think I will have to check with upstream about this. > Please also make it clear which Python version is used during the tests. I didn't understand this part, what do you mean exactly by making the version clear? Feel free to point me to examples or

Bug#910249: Bumping up encryption to AES-256 by default

On Wed, Oct 3, 2018 at 6:36 PM procmem wrote: > Package: gnome-disk-utility > Version: all > Severity: serious > > Hi. I noticed Gnome Disks uses AES-128 by default instead of AES-256 > like Debian does out of the box. Having 256 bit symmetric keys is good > practice for long term security

Bug#897883: marked as done (varconf: ftbfs with GCC-8)

Your message dated Wed, 03 Oct 2018 23:13:55 + with message-id and subject line Bug#897883: fixed in varconf 1.0.1-6 has caused the Debian Bug report #897883, regarding varconf: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#909602: [Pkg-mailman-hackers] Bug#909602: mailmanclient causes python3-mailman-hyperkitty and mailman3-web to fail to install in buster

Le mercredi 26 septembre 2018 à 20:32:47+0200, Paul Gevers a écrit : > Hi > > On Tue, 25 Sep 2018 21:33:18 +0200 Paul Gevers wrote: > > If the right binary package(s) from mailmanclient would have had a > > versioned Breaks on the broken versions of mailman3-web and > >

Bug#908827: mesa: Fails to build on Stretch, missing min build dep

Commit has made it into the queue for 18.2.2. On Thu, 27 Sep 2018 at 18:12, Stuart Young wrote: > This was an upstream issue due to new work in the vulkan driver that uses > newer libxcb functions (only in 1.13+). > > For Mesa 18.2.1, the following upstream commit resolves the build issue: >

Bug#910249: Bumping up encryption to AES-256 by default

Package: gnome-disk-utility Version: all Severity: serious Hi. I noticed Gnome Disks uses AES-128 by default instead of AES-256 like Debian does out of the box. Having 256 bit symmetric keys is good practice for long term security especially in a coming era of quantum computers. (Whether they

Bug#910248: kmymoney: KMyMoney needs to be recompiled against KDE PIM 18.08.

Source: kmymoney Version: 5.0.1-2 Severity: serious Control: block 909288 by -1 Hey, KDE PIM 18.08 changes ABI, so KMyMoney needs to recompiled against the new version. But as KMyMoney 5.0.1 is currently in experimental, this can't be done via the normal transition (so far as I unserstand.

Processed: kmymoney: KMyMoney needs to be recompiled against KDE PIM 18.08.

Processing control commands: > block 909288 by -1 Bug #909288 [release.debian.org] transition: kdepim 18.08 909288 was blocked by: 908869 909288 was not blocking any bugs. Added blocking bug(s) of 909288: 910248 -- 909288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909288 910248:

Processed: Re: [Epoptes] Bug#910216: epoptes-client: removed shipped file: /etc/network/if-up.d/epoptes-client

Processing control commands: > tags 910216 pending Bug #910216 [epoptes-client] epoptes-client: removed shipped file: /etc/network/if-up.d/epoptes-client Added tag(s) pending. -- 910216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910216 Debian Bug Tracking System Contact

Bug#910216: [Epoptes] Bug#910216: epoptes-client: removed shipped file: /etc/network/if-up.d/epoptes-client

Control: tags 910216 pending On 2018-10-03, Andreas Beckmann wrote: > during a test with piuparts I noticed your package removes files that > it has shipped. > > From the attached log (scroll to the bottom...): > > 1m6.1s ERROR: FAIL: debsums reports modifications inside the chroot: > debsums:

Bug#909214: marked as done (mailman-hyperkitty FTBFS: FAIL: test_archive_message_unserializable (mailman_hyperkitty.tests.test_archiver.ArchiverTestCase))

Your message dated Wed, 03 Oct 2018 22:07:03 + with message-id and subject line Bug#909214: fixed in mailman-hyperkitty 1.1.0-9 has caused the Debian Bug report #909214, regarding mailman-hyperkitty FTBFS: FAIL: test_archive_message_unserializable

Bug#907788: marked as done ("dh key too small" since openssl upgrade)

Your message dated Wed, 3 Oct 2018 22:55:30 +0100 with message-id <20181003215530.GA30589@pinky.flat11.house> and subject line Re: Bug#907788: "dh key too small" since openssl upgrade has caused the Debian Bug report #907788, regarding "dh key too small" since openssl upgrade to be marked as done.

Bug#896759: [gui-ufw] FTBFS and no maintainer activity since 2016

Hello Everyone, I'm not sure if I should have CC'ed everyone, sorry if I shouldn't. Today a Brazilian user was asking help installing gufw on Testing, he said it was only on unstable and stable, I decided to have a look and discovered: * The last upload was a NMU on 2017-05-13 * The last

Bug#905481: marked as done (mediastreamer2: FTBFS with GCC-8)

Your message dated Wed, 03 Oct 2018 21:41:49 + with message-id and subject line Bug#905481: fixed in mediastreamer2 1:2.16.1-3 has caused the Debian Bug report #905481, regarding mediastreamer2: FTBFS with GCC-8 to be marked as done. This means that you claim that the problem has been dealt

Bug#910206: marked as done (libpbbam-dev: missing Breaks+Replaces: libpbbam (<< 0.18))

Your message dated Wed, 03 Oct 2018 21:42:23 + with message-id and subject line Bug#910206: fixed in pbbam 0.18.0+dfsg-2 has caused the Debian Bug report #910206, regarding libpbbam-dev: missing Breaks+Replaces: libpbbam (<< 0.18) to be marked as done. This means that you claim that the

Bug#910230: marked as done (libactivation-java: missing Breaks+Replaces: glassfish-activation)

Your message dated Wed, 03 Oct 2018 21:39:18 + with message-id and subject line Bug#910230: fixed in javabeans-activation-framework 1.2.0-2 has caused the Debian Bug report #910230, regarding libactivation-java: missing Breaks+Replaces: glassfish-activation to be marked as done. This means

Bug#910230: Bug #910230 in javabeans-activation-framework marked as pending

Control: tag -1 pending Hello, Bug #910230 in javabeans-activation-framework reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #910230 in javabeans-activation-framework marked as pending

Processing control commands: > tag -1 pending Bug #910230 [libactivation-java] libactivation-java: missing Breaks+Replaces: glassfish-activation Added tag(s) pending. -- 910230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910230 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#906358: marked as done (gimp-help: FTBFS in buster/sid (You must have automake 1.10 or newer installed))

Your message dated Wed, 03 Oct 2018 20:43:07 + with message-id and subject line Bug#906358: fixed in gimp-help 2.8.2-0.2 has caused the Debian Bug report #906358, regarding gimp-help: FTBFS in buster/sid (You must have automake 1.10 or newer installed) to be marked as done. This means that

Bug#897743: marked as done (eris: ftbfs with GCC-8)

Your message dated Wed, 03 Oct 2018 20:39:48 + with message-id and subject line Bug#897743: fixed in eris 1.3.23-7 has caused the Debian Bug report #897743, regarding eris: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#909539: dds: test failures on multiple Ubuntu architectures

On Wed, Oct 03, 2018 at 10:01:58PM +0200, Christoph Berg wrote: > It is parsing the `free` output to probe available memory. The code is > utterly wrong since free had been changed to output only two lines > instead of three, so it looks at the amount of swap available. I > haven't checked, but my

Bug#909352: Was severity serious intended?

śr., 3 paź 2018, 21:49 użytkownik Adrian Bunk napisał: > On Wed, Oct 03, 2018 at 09:14:15PM +0200, Marcin Owsiany wrote: > > Maybe I'm missing something, but what was the reason for filing #909352 > as > > serious? Looking at #892016 it does not seem like it was the cause of the > > segfault? Or

Bug#909539: dds: test failures on multiple Ubuntu architectures

Re: Helmut Grohne 2018-10-03 <20181003191607.ga11...@alf.mars> > > make[2]: Leaving directory '/<>/examples' > > LD_LIBRARY_PATH=src examples/DealerPar > > Memory::GetPtr: 0 vs. 0 > > I got exactly this with sbuild in unstable/amd64 with a stretch kernel > on a haswell cpu. On another system

Bug#909352: Was severity serious intended?

On Wed, Oct 03, 2018 at 09:14:15PM +0200, Marcin Owsiany wrote: > Maybe I'm missing something, but what was the reason for filing #909352 as > serious? Looking at #892016 it does not seem like it was the cause of the > segfault? Or was it? No. > If not, then getting rid of squeak-plugins-scratch

Bug#910182: cloud-init FTBFS: tests fail

On 10/3/18 1:44 PM, Helmut Grohne wrote: > Source: cloud-init > Version: 0.7.9-5 > Severity: serious > Tags: ftbfs > > Building cloud-init in unstable on amd64 fails in sbuild. The build ends > with: That's kind of fine, as I'm planning for uploading the version which is currently in

Processed: Re: Bug#909539: dds: test failures on multiple Ubuntu architectures

Processing control commands: > tags -1 + ftbfs Bug #909539 [src:dds] dds: test failures on multiple Ubuntu architectures Added tag(s) ftbfs. > severity -1 serious Bug #909539 [src:dds] dds: test failures on multiple Ubuntu architectures Severity set to 'serious' from 'normal' -- 909539:

Bug#909352: Was severity serious intended?

Maybe I'm missing something, but what was the reason for filing #909352 as serious? Looking at #892016 it does not seem like it was the cause of the segfault? Or was it? If not, then getting rid of squeak-plugins-scratch sounds more like a wishlist cleanup request to me than a serious bug. All

Bug#908580: marked as done (ibus-table-createdb fails with nonexisting $HOME)

Your message dated Wed, 03 Oct 2018 15:12:24 -0400 with message-id <6f6782d6f470e09ee68f6030d230978180cb506d.ca...@gmail.com> and subject line Properly close bug #908580 has caused the Debian Bug report #908580, regarding ibus-table-createdb fails with nonexisting $HOME to be marked as done. This

Bug#910242: samba-libs: missing Breaks+Replaces: libndr-standard0

Package: samba-libs Version: 2:4.8.5+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy' to 'jessie' to 'stretch' to 'buster'. Its successor installed fine in 'wheezy', and upgraded to

Bug#905180: libmoe-dev: missing Breaks+Replaces: libmoe1.5 (<< 1.5.8-3)

Followup-For: Bug #905180 Hi, you added Breaks and Replaces against libmoe (<< 1.5.8-3) but this needs to be libmoe1.5 (<< 1.5.8-3) Andreas

Processed: found 910199 in 1.13.1-7

Processing commands for cont...@bugs.debian.org: > found 910199 1.13.1-7 Bug #910199 [python3-adios] python3-adios: fails to install: python3-adios.postinst: Syntax error: "(" unexpected Marked as found in versions adios/1.13.1-7. > thanks Stopping processing here. Please contact me if you need

Processed: severity of 910199 is serious

Processing commands for cont...@bugs.debian.org: > severity 910199 serious Bug #910199 [python3-adios] python3-adios: fails to install: python3-adios.postinst: Syntax error: "(" unexpected Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need

Processed: Re: Bug#910128: bash-completion parallel FTBFS

Processing control commands: > forwarded -1 https://github.com/scop/bash-completion/issues/212 Bug #910128 [src:bash-completion] bash-completion parallel FTBFS Set Bug forwarded-to-address to 'https://github.com/scop/bash-completion/issues/212'. > tags -1 fixed-upstream patch Bug #910128

Bug#910128: bash-completion parallel FTBFS

Control: forwarded -1 https://github.com/scop/bash-completion/issues/212 Control: tags -1 fixed-upstream patch On Wed, Oct 03, 2018 at 07:33:34AM +0200, Helmut Grohne wrote: >... > Notably, the completion directory is created after adding symlinks into > it. Looking at the generated

Bug#910234: python-minimal: add Conflicts against python-central

Package: python-minimal Version: 2.7.15-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that packages using python-central (last seen in oldstable) may have been kept installed over all distupgrade steps to buster. But these

Bug#910233: libsvn-{dev,java}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

Package: libsvn-dev,libsvn-java Version: 1.10.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an

Processed: add ftbfs tag

Processing commands for cont...@bugs.debian.org: > tags 806100 + ftbfs Bug #806100 [src:pyviennacl] pyviennacl: FTBFS when built with dpkg-buildpackage -A (No such file or directory) Added tag(s) ftbfs. > tags 806127 + ftbfs Bug #806127 [src:zope2.13] zope2.13: FTBFS when built with

Bug#902753: marked as done (fflas-ffpack FTBFS on 32bit big endian: test failure)

Your message dated Wed, 03 Oct 2018 17:19:17 + with message-id and subject line Bug#902753: fixed in fflas-ffpack 2.3.2-3 has caused the Debian Bug report #902753, regarding fflas-ffpack FTBFS on 32bit big endian: test failure to be marked as done. This means that you claim that the problem

Bug#907010: marked as done (fflas-ffpack: baseline violation on i386)

Your message dated Wed, 03 Oct 2018 17:19:17 + with message-id and subject line Bug#907010: fixed in fflas-ffpack 2.3.2-3 has caused the Debian Bug report #907010, regarding fflas-ffpack: baseline violation on i386 to be marked as done. This means that you claim that the problem has been

Bug#910230: libactivation-java: missing Breaks+Replaces: glassfish-activation

Package: libactivation-java Version: 1.2.0-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' to 'stretch' to 'buster'. It installed fine in 'jessie', and upgraded to 'stretch'

Bug#910229: python-gitlab: File conflict with ruby-gitlab

Source: python-gitlab Version: 1:1.6.0-1 Severity: serious Affects: src:ruby-gitlab Both ruby-gitlab and gitlab-cli ship /usr/bin/gitlab and /usr/share/man/man1/gitlab.1.gz This is a violation of the first paragraph of Debian Policy § 10.1 https://www.debian.org/doc/debian-policy/ch-files.html

Bug#910228: ruby-gitlab: file conflict with gitlab-cli

Source: ruby-gitlab Version: 4.5.00-1 Severity: serious Affects: src:python-gitlab X-Debbugs-CC: bou...@debian.org, sop...@freexian.com Both ruby-gitlab and gitlab-cli ship /usr/bin/gitlab and /usr/share/man/man1/gitlab.1.gz This is a violation of the first paragraph of Debian Policy § 10.1

Processed (with 2 errors): user debian...@lists.debian.org, usertagging 910008, reassign 910008 to libghc-mtl-dev ...

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 910008 piuparts There were no usertags set. Usertags are now: piuparts. > reassign 910008 libghc-mtl-dev 2.2.2-2 Bug #910008

Bug#910226: expeyes-web: fails to upgrade from 'stretch': Exception: cannot get content of python3-expeyes

Package: expeyes-web Version: 4.4.4+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails. >From the attached log

Processed: openstack-dashboard: fails to upgrade from stretch with python-ironic-ui installed

Processing control commands: > affects -1 + python-ironic-ui Bug #910225 [openstack-dashboard] openstack-dashboard: fails to upgrade from stretch with python-ironic-ui installed Added indication that 910225 affects python-ironic-ui -- 910225:

Bug#906826: xul-ext-spdy-indicator no longer works with firefox-esr 60

On Thursday, 4 October 2018 1:20:42 AM AEST Moritz Mühlenhoff wrote: > On Tue, Aug 21, 2018 at 06:56:13PM +0300, Adrian Bunk wrote: > > Package: xul-ext-spdy-indicator > > Version: 2.2-1 > > Severity: serious > > > > XUL addons are no longer supported. > > Dmitry, > shall we remove it from the

Bug#910222: opam: copyright file missing after upgrade (policy 12.5)

Package: opam Version: 2.0.0-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade, which is a violation of Policy 12.5:

Bug#881971: fixed in lightbeam 2.1.0-1

On Thursday, 4 October 2018 1:19:56 AM AEST Moritz Mühlenhoff wrote: > On Wed, Jul 25, 2018 at 04:19:18AM +, Dmitry Smirnov wrote: > >* New upstream release [February 2018]. > > > > + WebExtensions version (Closes: #881971). > > lightbeam is also broken in stretch, do you plan to

Bug#910220: libdmtx-dev: copyright file missing after upgrade (policy 12.5)

Package: libdmtx-dev Version: 0.7.5-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade, which is a violation of Policy 12.5:

Bug#910219: libdeps-renderer-dot-perl: copyright file missing after upgrade (policy 12.5)

Package: libdeps-renderer-dot-perl Version: 0.13-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade, which is a violation of Policy 12.5:

Bug#910218: libapache2-mod-proxy-uwsgi: copyright file missing after upgrade (policy 12.5)

Package: libapache2-mod-proxy-uwsgi Version: 2.4.34-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade, which is a violation of Policy 12.5:

Processed: tagging 909460

Processing commands for cont...@bugs.debian.org: > tags 909460 + pending Bug #909460 [src:bacula] Trouble with the sqlite3 upgrade path Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 909460:

Bug#910217: apparmor: removed shipped file: /var/cache/apparmor/CACHEDIR.TAG

Package: apparmor Version: 2.13-8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package removes files that it has shipped. >From the attached log (scroll to the bottom...): 0m35.9s ERROR: FAIL: debsums reports modifications

Bug#910216: epoptes-client: removed shipped file: /etc/network/if-up.d/epoptes-client

Package: epoptes-client Version: 1.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package removes files that it has shipped. >From the attached log (scroll to the bottom...): 1m6.1s ERROR: FAIL: debsums reports

Bug#906609: fixed in gnucash 1:3.3-1

On Thursday, 4 October 2018 1:01:12 AM AEST Bernhard Übelacker wrote: > Hello Dimitry, > I saw that a version 3.3-1 got uploaded so I had a look at the build > logs, Thank you for checking build logs. > but found some of them failing with this error: > >

Bug#910215: murano-agent: prompting due to modified conffiles which were not modified by the user: /etc/murano-agent/muranoagent.conf

Package: murano-agent Version: 1:3.5.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As

Bug#910214: softflowd: prompting due to modified conffiles which were not modified by the user: /etc/softflowd/default.conf

Package: softflowd Version: 0.9.9-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there

Bug#906826: xul-ext-spdy-indicator no longer works with firefox-esr 60

On Tue, Aug 21, 2018 at 06:56:13PM +0300, Adrian Bunk wrote: > Package: xul-ext-spdy-indicator > Version: 2.2-1 > Severity: serious > > XUL addons are no longer supported. Dmitry, shall we remove it from the archive? SPDY itself is deprecated as well. Cheers, Moritz

Bug#882287: xul-ext-noscript: new upstream version

On Mon, Sep 17, 2018 at 01:13:18PM +0400, Jerome BENOIT wrote: > Please consider to the new upstream version 10 > given that the current version of noscript provided in Stretch > does not work with firefox-esr 60.2 recently brought in Stretch. What's the plan for noscript in stretch? Is a

Bug#909719: marked as done (dpkg breaks devscripts autopkgtest due to syntax/behavior change)

Your message dated Wed, 03 Oct 2018 15:19:13 + with message-id and subject line Bug#909719: fixed in devscripts 2.18.5 has caused the Debian Bug report #909719, regarding dpkg breaks devscripts autopkgtest due to syntax/behavior change to be marked as done. This means that you claim that the

Bug#881894: xul-ext-cookie-monster: dead upstream, broken in FF57

On Thu, Nov 16, 2017 at 06:21:56AM +0100, Christoph Anton Mitterer wrote: > Package: xul-ext-cookie-monster > Version: 1.3.0.5-1 > Severity: normal > > > > Hi. > > Seems this addon is dead upstream (at least: > https://addons.mozilla.org/en-US/firefox/addon/cookie-monster/ > says "This add-on

Bug#906859: xul-ext-dom-inspector no longer works with firefox-esr 60

On Sat, Sep 08, 2018 at 03:12:40PM +0800, Paul Wise wrote: > On Tue, 21 Aug 2018 21:11:16 +0300 Adrian Bunk wrote: > > > Package: xul-ext-dom-inspector > > > > XUL addons are no longer supported. > > The native Firefox developer tools are almost a replacement, > so I think this package can just

Bug#906843: xul-ext-custom-tab-width no longer works with firefox-esr 60

On Tue, Aug 21, 2018 at 08:04:57PM +0300, Adrian Bunk wrote: > Package: xul-ext-custom-tab-width > Version: 1.1-1 > Severity: serious > > XUL addons are no longer supported. This is dead upstream and broken even in ESR, let's remove it from the archive? Cheers, Moritz

Bug#865305: Does not work with firefox 54

On Tue, Jun 20, 2017 at 02:30:11PM +0200, Javier Barroso wrote: > Package: xul-ext-pentadactyl > Version: 1.2~r20170308-1 > Severity: important > > Maybe add a README if the package can work with firefox 54 (seems that > multiprocess have to be disable). > Not sure if would be good idea to add

Bug#881971: fixed in lightbeam 2.1.0-1

On Wed, Jul 25, 2018 at 04:19:18AM +, Dmitry Smirnov wrote: >* New upstream release [February 2018]. > + WebExtensions version (Closes: #881971). lightbeam is also broken in stretch, do you plan to update it there or should it be removed from stable? Cheers, Moritz

Bug#906832: xul-ext-kwallet5 no longer works with firefox-esr 60

On Tue, Aug 21, 2018 at 07:53:52PM +0300, Adrian Bunk wrote: > On Tue, Aug 21, 2018 at 07:11:59PM +0300, Adrian Bunk wrote: > > Package: xul-ext-kwallet5 > > Version: 1.0-2 > > Severity: serious > > > > XUL addons are no longer supported. > > If it is confirmed that this package works with

Bug#910212: fusiondirectory: fails to upgrade from 'stretch': pre-installation script subprocess returned error exit status 30

Package: fusiondirectory Version: 1.2.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails. >From the attached log

Bug#910158: marked as done (libpmix-dev: broken symlink: /usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so -> libpmix.so.2.2.0)

Your message dated Wed, 03 Oct 2018 15:08:30 + with message-id and subject line Bug#910158: fixed in pmix 3.0.2-2 has caused the Debian Bug report #910158, regarding libpmix-dev: broken symlink: /usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so -> libpmix.so.2.2.0 to be marked as done. This

Bug#910211: python-werkzeug-doc: unhandled symlink to directory conversion: /usr/share/doc/python-werkzeug/examples

Package: python-werkzeug-doc Version: 0.14.1+dfsg1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means

Bug#906609: fixed in gnucash 1:3.3-1

Hello Dimitry, I saw that a version 3.3-1 got uploaded so I had a look at the build logs, but found some of them failing with this error: /<>/libgnucash/engine/gnc-timezone.cpp:55:22: error: operator '!' has no right operand #if ! WORDS_BIGENDIAN ^ I fear this happens

Bug#910208: Crash at encoding change

Package: libvte-2.91-0 Version: 0.54.0-1 Severity: grave Open gnome-terminal, and use its Terminal -> Set Character Encoding menu to switch to another encoding. Switch back, then again to something different. gnome-terminal crashes. Mainstream vte 0.54.1 fixes this issue. Could you please

Processed: linux-headers-4.18.0-*: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

Processing control commands: > affects -1 + linux-headers-4.18.0-1-amd64 Bug #910207 [src:linux] linux-headers-4.18.0-*: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE Added indication that 910207 affects linux-headers-4.18.0-1-amd64 -- 910207:

Bug#910207: linux-headers-4.18.0-*: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

Source: linux Version: 4.18.8-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + linux-headers-4.18.0-1-amd64 Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other

Bug#910206: libpbbam-dev: missing Breaks+Replaces: libpbbam (<< 0.18)

Package: libpbbam-dev Version: 0.18.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite

Bug#910205: libadios-bin: fails to remove: update-alternatives: error: no alternatives for adios

Package: libadios-bin Version: 1.13.1-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. >From the attached log (scroll to the bottom...): Removing libadios-bin (1.13.1-7) ... update-alternatives:

Bug#908681: libsane1: nothing provides libsane so xsane uninstallable

On Wed, Oct 03, 2018 at 10:25:31AM +1300, Ben Caradoc-Davies wrote: > The removal of "Provides: libsane" in libsane1 1.0.27-2 makes xsane > uninstallable because nothing provides libsane. Hi all, I am aware that keeping "libsane" name with "Provides: libsane1" is under consideration. In case

Bug#906388: nipy: FTBFS in buster/sid (failing tests)

update: - uploaded sympy 1.3 which resolves sympy bug - running by upstream the resolution for the other failed test: https://github.com/nipy/nipy/pull/445 and will upload fixed up package tomorrow On Tue, 02 Oct 2018, Yaroslav Halchenko wrote: > FWIW, two of the errors are caused by a bug

Bug#909974: backports.ssl-match-hostname should be removed for buster

Hi, On 10/02/2018 09:22 PM, Felipe Sateler wrote: Hi Matthias, Ivo, On Sun, 30 Sep 2018 22:59:26 +0200 Ivo De Decker > wrote: > clone 869896 -1 > retitle -1 remove unneeded dependency on backports.ssl-match-hostname > block 869896 by -1 > clone -1 -2 -3 -4 -5 >

Bug#910202: libghc-parsec3-dev: ships /var/lib/ghc/package.conf.d/parsec-3.1.13.0.conf which is now also in ghc

Package: libghc-parsec3-dev Version: 3.1.13.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...):

Processed: clone 907751

Processing commands for cont...@bugs.debian.org: > clone 907751 -1 Bug #907751 [ftp.debian.org] RM: vmdebootstrap -- ROM; upstream discontinued, obsolete, better options exist Bug 907751 cloned as bug 910201 > reassign -1 vmdebootstrap Bug #910201 [ftp.debian.org] RM: vmdebootstrap -- ROM;

Processed: tagging 909286

Processing commands for cont...@bugs.debian.org: > tags 909286 - newcomer Bug #909286 [firefox] firefox: "The bookmarks and history system will not be functional" message always Removed tag(s) newcomer. > thanks Stopping processing here. Please contact me if you need assistance. -- 909286:

Bug#907953: marked as done (network-manager-strongswan FTBFS with glib 2.58)

Your message dated Wed, 03 Oct 2018 13:49:47 + with message-id and subject line Bug#907953: fixed in network-manager-strongswan 1.4.4-2 has caused the Debian Bug report #907953, regarding network-manager-strongswan FTBFS with glib 2.58 to be marked as done. This means that you claim that the

Bug#857299: Package builds again

On Wed, Oct 03, 2018 at 02:37:23PM +0200, Frédéric Bonnard wrote: > does this bug still appear for rebootstrap ? > How can I simply reproduce it within rebootstrap ? > Building inside sbuild works. This is/was a native problem. It was filed against the natively built ppc64el package (noticed as a

Bug#906050: marked as done (python-plplot-qt lost its generated python dependencies)

Your message dated Wed, 03 Oct 2018 13:34:41 + with message-id and subject line Bug#906050: fixed in plplot 5.13.0+dfsg-9 has caused the Debian Bug report #906050, regarding python-plplot-qt lost its generated python dependencies to be marked as done. This means that you claim that the

Bug#907953: network-manager-strongswan FTBFS with glib 2.58

Harald Dunkel writes ("Re: network-manager-strongswan FTBFS with glib 2.58"): > I have created a new source package. It just disables the error message. > When upstream releases a fixed version, this patch can be removed again. > > Ian, would you mind to sponsor an upload? I have signed the new

Bug#909000: Enigmail 2.0 needed in Stretch after Thunderbird 60 upload

On Wed 2018-10-03 11:38:41 +0200, Jonas Meurer wrote: > That's great news! Thanks a ton for working so hard on getting Enigmail > 2.0 to run without OpenPGP.js. Will these changes be adapted upstream or > will upstream keep using OpenPGP? some of my changes are not upstreamable because i've

Bug#907267: marked as done (openmpi: liggghts build on i386 times out)

Your message dated Wed, 03 Oct 2018 13:20:09 + with message-id and subject line Bug#907267: fixed in openmpi 3.1.2-5 has caused the Debian Bug report #907267, regarding openmpi: liggghts build on i386 times out to be marked as done. This means that you claim that the problem has been dealt

  1   2   >