Bug#828387: Pending fixes for bugs in the libcrypt-openssl-rsa-perl package

tag 828387 + pending thanks Some bugs in the libcrypt-openssl-rsa-perl package are closed in revision 40c5bc9cb73ba6a7b33fc77725b49d7da1faffac in branch 'master' by gregor herrmann The full diff can be seen at

Processed: Pending fixes for bugs in the libcrypt-openssl-rsa-perl package

Processing commands for cont...@bugs.debian.org: > tag 828387 + pending Bug #828387 [src:libcrypt-openssl-rsa-perl] libcrypt-openssl-rsa-perl: FTBFS with openssl 1.1.0 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 828387:

Bug#828387: libcrypt-openssl-rsa-perl: FTBFS with openssl 1.1.0

On Mon, 12 Dec 2016 22:30:53 +0100, gregor herrmann wrote: > On Mon, 12 Dec 2016 21:51:01 +0100, Sebastian Andrzej Siewior wrote: > > Gregor, is there anything you want me to do? The difference is mostly > > that I tried to keep the "ifdef openssl version" check in one spot and > > got rid of

Processed: found 848024 2.4~rc1-1

Processing commands for cont...@bugs.debian.org: > found 848024 2.4~rc1-1 Bug #848024 [openvpn] Fails to connect after upgrade to openvpn 2.4 Marked as found in versions openvpn/2.4~rc1-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 848024:

Processed: Re: [Pkg-utopia-maintainers] Bug#848024: Fails to connect after upgrade to openvpn 2.4

Processing control commands: > reassign -1 openvpn Bug #848024 [network-manager-openvpn] Fails to connect after upgrade to openvpn 2.4 Bug reassigned from package 'network-manager-openvpn' to 'openvpn'. No longer marked as found in versions network-manager-openvpn/1.2.6-2. Ignoring request to

Bug#844921: marked as done (python-django-compressor: FTBFS: Tests failures)

Your message dated Tue, 13 Dec 2016 15:19:16 + with message-id and subject line Bug#844921: fixed in python-django-compressor 2.1-1 has caused the Debian Bug report #844921, regarding python-django-compressor: FTBFS: Tests failures to be marked as done.

Bug#843467: marked as done (libxbase64-1: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

Your message dated Tue, 13 Dec 2016 15:11:19 + with message-id and subject line Bug#843467: fixed in xbase64 3.1.2-11 has caused the Debian Bug report #843467, regarding libxbase64-1: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE to be

Bug#847966: marked as done (python-cylc: ails to upgrade from 'jessie' - trying to overwrite /usr/lib/python2.7/dist-packages/xdot.py)

Your message dated Tue, 13 Dec 2016 15:06:37 + with message-id and subject line Bug#847966: fixed in cylc 6.11.2-2 has caused the Debian Bug report #847966, regarding python-cylc: ails to upgrade from 'jessie' - trying to overwrite

Bug#847789: [Pkg-javascript-devel] Bug#847789: On the new problem

On 2016, ഡിസംബർ 13 7:13:24 PM IST, Julien Puydt wrote: >Hi, > >I found the time to compile the deps to check for myself, as it would >be >easier than having you report issues one by one, but I'm stuck with >node-glob-stream, which build-depends on node-extend (>=

Bug#847757: testdisk FTBFS on mips: common.h:128:2: error: initializer element is not constant

I tried Christophe's patch. It does not fix the build. Package still FTBFS with "initializer element is not constant" error. Currently gcc-6 is used as default compiler, by changing the compiler to gcc-5 testdisk builds successfully.

Bug#845737: drop the problematic testcase?

I would just drop the `test_symlink_time_handling` testcase and check with upstream what might be going on here. Apart from that, it looks like the internet access errors are fixed. Ghis

Bug#845737: Also new upstream version has test failures

On Tue, 13 Dec 2016 09:27:17 +0100 Andreas Tille wrote: > Hi Kevin, > > you injected a "Closes: #845737" in the latest changelog but I get: > > > == > FAIL: tests.tests.test_symlink_time_handling >

Bug#847232: marked as done (nvme-cli FTBFS on 32 bit: format error in nvme-print.c)

Your message dated Tue, 13 Dec 2016 13:50:56 + with message-id and subject line Bug#847232: fixed in nvme-cli 1.0-2 has caused the Debian Bug report #847232, regarding nvme-cli FTBFS on 32 bit: format error in nvme-print.c to be marked as done. This means

Bug#847789: On the new problem

Hi, I found the time to compile the deps to check for myself, as it would be easier than having you report issues one by one, but I'm stuck with node-glob-stream, which build-depends on node-extend (>= 2.0.0) (available) but depends on node-extend (>= 3.0.0), which isn't available, even in

Bug#846877: plasma-desktop: Sddm can not start kde. Then panel is not working.

Control: severity -1 important Control: tag -1 - upstream ¡Hola laurent! El 2016-12-03 a las 22:14 +0100, laurent B escribió: Package: plasma-desktop Version: 4:5.8.4-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, *** Reporter, please

Processed: Re: Bug#846877: plasma-desktop: Sddm can not start kde. Then panel is not working.

Processing control commands: > severity -1 important Bug #846877 [plasma-desktop] plasma-desktop: Sddm can not start kde. Then panel is not working. Severity set to 'important' from 'grave' > tag -1 - upstream Bug #846877 [plasma-desktop] plasma-desktop: Sddm can not start kde. Then panel is

Bug#831857: Security update for libupnp (CVE-2016-6255, CVE-2016-8863)

On Dec/13, Uwe Kleine-König wrote: > Do you consider CVE-2016-6255 and CVE-2016-8863 bad enough to make a > security update for it? If so, I suggest the following debdiff. Yes, the first one is bad, so let's fix both via a DSA. Could you please provide a debdiff with

Bug#848037: android-libdex-dev: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/android/libdex.so

Package: android-libdex-dev Version: 7.0.0+r1-2 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

Bug#847966: python-cylc: ails to upgrade from 'jessie' - trying to overwrite /usr/lib/python2.7/dist-packages/xdot.py

On 2016-12-13 13:03, Alastair McKinstry wrote: > Hi Andreas, > > AIUI, I need to just add a > Breaks: xdot (<< 0.7-2) > > for python-cylc. This is because I want to force xdot to be upgraded > first in the jessie->stretch upgrade, and I'm not replacing files in > xdot (so, not adding Replaces:)

Bug#831857: Security update for libupnp (CVE-2016-6255, CVE-2016-8863)

Hello, Do you consider CVE-2016-6255 and CVE-2016-8863 bad enough to make a security update for it? If so, I suggest the following debdiff. Best regards Uwe diff -Nru libupnp-1.6.19+git20141001/debian/changelog libupnp-1.6.19+git20141001/debian/changelog ---

Bug#829230: marked as done (cloud-sptheme: FTBFS: index_styling.py [..] ValueError: too many values to unpack)

Your message dated Tue, 13 Dec 2016 12:33:30 + with message-id and subject line Bug#829230: fixed in cloud-sptheme 1.8.0-1 has caused the Debian Bug report #829230, regarding cloud-sptheme: FTBFS: index_styling.py [..] ValueError: too many values to

Bug#838358: marked as done (icinga2: FTBFS on armhf: test failures)

Your message dated Tue, 13 Dec 2016 12:33:55 + with message-id and subject line Bug#838358: fixed in icinga2 2.6.0-1 has caused the Debian Bug report #838358, regarding icinga2: FTBFS on armhf: test failures to be marked as done. This means that you claim

Bug#845753: Help: r-cran-treescape does not build on i386, armel and armhf any more

On Tue, Dec 13, 2016 at 11:47:43AM +0100, gregor herrmann wrote: > [..] > > So what exactly do you mean by "didn't add it yet" ? > > I guess pabs meant that you're not actually using it in debian/rules. Urgs, thanks for opening my eyes. ;-) So I tried: Index: rules

Bug#848034: hovercraft: FTBFS with docutils 0.13, hardcodes 0.12 version number

Source: hovercraft Version: 2.1-1 Severity: serious Justification: fails to build from source Dear Maintainer, When I am building hovercraft against latest sid, I am getting a test failure in SlideMakerTests.test_transition_levels function: AssertionError: b'\n[490 chars]ent>' That happens

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

Hi >Based on the stack trace, the exception is thrown because a managed >buffer that is being freed isn't actually registered to the buffer manager. >his shouldn't happen, since the only way to get a buffer is to request >it from the manager in the first place. It's possible there's a memory

Bug#846707: marked as done (greenbone-security-assistant: FTBFS: build-dependency not installable: libopenvas-dev (>= 8.0.7))

Your message dated Tue, 13 Dec 2016 12:04:24 + with message-id and subject line Bug#846232: fixed in openvas-libraries 8.0.8-2 has caused the Debian Bug report #846232, regarding greenbone-security-assistant: FTBFS: build-dependency not installable:

Bug#846739: marked as done (openvas-cli: FTBFS: build-dependency not installable: libopenvas-dev (>= 8.0.4))

Your message dated Tue, 13 Dec 2016 12:04:24 + with message-id and subject line Bug#846232: fixed in openvas-libraries 8.0.8-2 has caused the Debian Bug report #846232, regarding openvas-cli: FTBFS: build-dependency not installable: libopenvas-dev (>=

Bug#847966: python-cylc: ails to upgrade from 'jessie' - trying to overwrite /usr/lib/python2.7/dist-packages/xdot.py

Hi Andreas, AIUI, I need to just add a Breaks: xdot (<< 0.7-2) for python-cylc. This is because I want to force xdot to be upgraded first in the jessie->stretch upgrade, and I'm not replacing files in xdot (so, not adding Replaces:) Is this correct ? How do I do a piuparts upgrade to test this?

Bug#846232: marked as done (openvas should depend on libgpgme-dev instead of libgpgme11-dev)

Your message dated Tue, 13 Dec 2016 12:04:24 + with message-id and subject line Bug#846232: fixed in openvas-libraries 8.0.8-2 has caused the Debian Bug report #846232, regarding openvas should depend on libgpgme-dev instead of libgpgme11-dev to be marked

Bug#846732: marked as done (openvas-manager: FTBFS: build-dependency not installable: libopenvas-dev (>= 8.0.8))

Your message dated Tue, 13 Dec 2016 12:04:24 + with message-id and subject line Bug#846232: fixed in openvas-libraries 8.0.8-2 has caused the Debian Bug report #846232, regarding openvas-manager: FTBFS: build-dependency not installable: libopenvas-dev (>=

Bug#846672: marked as done (openvas-scanner: FTBFS: build-dependency not installable: libopenvas-dev (>= 8.0.2))

Your message dated Tue, 13 Dec 2016 12:04:24 + with message-id and subject line Bug#846232: fixed in openvas-libraries 8.0.8-2 has caused the Debian Bug report #846232, regarding openvas-scanner: FTBFS: build-dependency not installable: libopenvas-dev (>=

Bug#848031: manpages: Can not be installed with initscripts

Package: manpages Version: 4.09-1 Severity: serious An upgrade fails: |Preparing to unpack .../manpages_4.09-1_all.deb ... |Unpacking manpages (4.09-1) over (4.08-1) ... |dpkg: error processing archive /var/cache/apt/archives/manpages_4.09-1_all.deb (--unpack): | trying to overwrite

Processed: Merge bugs

Processing commands for cont...@bugs.debian.org: > forcemerge 847998 848007 848010 Bug #847998 [manpages] manpages: file conflicts with initscripts Bug #847998 [manpages] manpages: file conflicts with initscripts Marked as found in versions manpages/4.08-1. Bug #848007 [manpages] manpages:

Bug#845753: Help: r-cran-treescape does not build on i386, armel and armhf any more

On Tue, 13 Dec 2016 11:30:41 +0100, Andreas Tille wrote: > > > Well, adding xvfb was the usual trick to cope with "unable to open X11 > > > display" messages and thus I added it ... > > To me it looks like you didn't add it yet, at least not to the version > > in Debian. > Hmmm, > $ apt-get

Bug#848013: marked as done (node-temporary: FTBFS: Error: Cannot find module 'sinon')

Your message dated Tue, 13 Dec 2016 10:49:08 + with message-id and subject line Bug#848013: fixed in node-temporary 0.0.8-2 has caused the Debian Bug report #848013, regarding node-temporary: FTBFS: Error: Cannot find module 'sinon' to be marked as done.

Bug#845753: Help: r-cran-treescape does not build on i386, armel and armhf any more

On Tue, Dec 13, 2016 at 03:50:32PM +0800, Paul Wise wrote: > On Tue, Dec 13, 2016 at 3:47 PM, Andreas Tille wrote: > > > Well, adding xvfb was the usual trick to cope with "unable to open X11 > > display" messages and thus I added it ... > > To me it looks like you didn't add it yet, at least

Bug#848022: linux-image-4.7.0-1-grsec-amd64: fails to use hp-health. hpasmlited segfault

Package: src:linux-grsec Version: 4.7.8-1+grsec201610161720+1~bpo8+1 Severity: critical Justification: breaks unrelated software * What led up to the situation? : service hp-health won't start anymore. * What exactly did you do (or not do) that was effective (or ineffective)? :

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

On Thu, Dec 08, 2016 at 02:21:21 +, Ben Hutchings wrote: [...] > I agree we need to stop this version of firmware-nonfree going into > testing before initramfs-tools is fixed, so I'm assigning this bug > back. This keeps #838858 (missing SI/CI smc firmware files) open in testing, leaving

Processed: Setting tags

Processing commands for cont...@bugs.debian.org: > tag 847998 pending Bug #847998 [manpages] manpages: file conflicts with initscripts Added tag(s) pending. > tag 848007 pending Bug #848007 [manpages] manpages: Installation of latest manpages 4.09-1 fails Added tag(s) pending. > tag 848010

Bug#833741: pepperflash-nonfree: patch/nmu ?

ydir...@free.fr wrote: > tags 833741 + patch > thanks > > Is there any reason not to apply that patch ? Unfortunately that patch does not apply cleanly now and also has a few bugs in it such as accidentally coding in version 23.0.0.162 into the download. Plus it added a dependency upon the "jq"

Bug#846232: [pkg-gnupg-maint] Bug#846232: libgpgme-dev: Provides: libgpgme11-dev must be versioned

Since libsnmp-dev is not the mandatory library for openvas and issue #846569 got no reply after 10 days, I will remove libsnmp-dev dependency to avoid conflict issue. -- Sun-Ze Lin (林上智) 2016-12-02 17:45 GMT+08:00 Raphael Hertzog : > On Thu, 01 Dec 2016, Daniel Kahn

Bug#847998: manpages: file conflicts with initscripts

>>> And there's certainly precedent for section 5 pages on filesystems. >>> For example, among others, we have ext4(5), btrfs(5), and nfs(5). >> >> But section 5 is for configuration files. You could move them >> to section 7 (general concepts), though. > > I can't move "them" as they come from

Bug#847998: manpages: file conflicts with initscripts

On 13 December 2016 at 10:56, Thorsten Glaser wrote: > On Tue, 13 Dec 2016, Michael Kerrisk (man-pages) wrote: > >> I can't move "them" as they come from diverse projects (nfs-utils, > > OK. > >> e2fsprogs, btrfs-progs). Obviously, various projects came to the same >>

Bug#847998: manpages: file conflicts with initscripts

On Tue, 13 Dec 2016, Michael Kerrisk (man-pages) wrote: > I can't move "them" as they come from diverse projects (nfs-utils, OK. > e2fsprogs, btrfs-progs). Obviously, various projects came to the same > conclusion (or copied each other's idea) that Section 5 was the right > place. And in the

Bug#847998: manpages: file conflicts with initscripts

Hello Thorsten, On 13 December 2016 at 10:43, Thorsten Glaser wrote: > On Tue, 13 Dec 2016, Michael Kerrisk (man-pages) wrote: > >> Upstream man-pages maintainer here; I just added tmpfs(5), unaware >> that it would create a conflict for Debian; I assume the conflicting >>

Bug#847998: manpages: file conflicts with initscripts

Am 13. Dezember 2016 04:49:46 MEZ, schrieb Michael Biebl : >On Tue, 13 Dec 2016 00:44:24 +0100 Sebastian Ramacher > wrote: >> Package: manpages >> Version: 4.09-1 >> Severity: serious >> >> manpages fails to install because it shares tmpfs(5) with

Bug#847998: manpages: file conflicts with initscripts

Upstream man-pages maintainer here; I just added tmpfs(5), unaware that it would create a conflict for Debian; I assume the conflicting page is Debian-specific(?). (I don't have such a page on my Fedora system.) On 13 December 2016 at 10:00, Thorsten Glaser wrote: > On Tue,

Bug#847998: manpages: file conflicts with initscripts

On Tue, 13 Dec 2016, Michael Kerrisk (man-pages) wrote: > Upstream man-pages maintainer here; I just added tmpfs(5), unaware > that it would create a conflict for Debian; I assume the conflicting > page is Debian-specific(?). (I don't have such a page on my Fedora Yes. > > The manpage about the

Bug#835947: marked as done (golang: non-standard gcc/g++ used for build (gcc-5))

Your message dated Tue, 13 Dec 2016 10:15:34 +0100 with message-id <6e4ee07a-43f3-91fc-7263-d1fe81815...@debian.org> and subject line Re: golang: non-standard gcc/g++ used for build (gcc-5) has caused the Debian Bug report #835947, regarding golang: non-standard gcc/g++ used for build (gcc-5) to

Bug#828336: marked as done (gvpe: FTBFS with openssl 1.1.0)

Your message dated Tue, 13 Dec 2016 09:03:49 + with message-id and subject line Bug#828336: fixed in gvpe 2.25-3 has caused the Debian Bug report #828336, regarding gvpe: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the

Bug#847998: manpages: file conflicts with initscripts

On Tue, 13 Dec 2016, Michael Biebl wrote: > The tmpfs man page shipped by the manpages package talks about the tmpfs > file system. > The man page shipped by initscripts talks about the debian/initscripts > specific config file /etc/default/tmpfs. > > My gut feeling is, that debian specific tmpfs

Bug#794466: VIrtualBox future in Debian

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Mon, 2016-12-12 at 21:59 -0800, Gordon Farquharson wrote: > 3. Do you recommend migrating existing VirtualBox images to KVM? Migration should be doable. I'm not sure if there are any issues in migration, but you may give it a shot. Should you

Bug#844275: [debian-mysql] Bug#844275: mysql_config injects build flags which breaks the build for other packages

Hi, We've had a fix for this prepared for some time now, but haven't been able to find anyone to sponsor an upload to unstable. Do you know anyone who might be able to help? It's ready to go from the mysql-5.7/debian/master branch at https://anonscm.debian.org/cgit/pkg-mysql/mysql.git --

Bug#845737: Also new upstream version has test failures

Hi Kevin, you injected a "Closes: #845737" in the latest changelog but I get: == FAIL: tests.tests.test_symlink_time_handling -- Traceback (most recent call

Bug#848015: ciphersaber: Fails to build from source, missing dependency on libtest-warn-perl

Package: ciphersaber Version: 1.01-2 Severity: serious ciphersaber fails to build from source in a clean sid chroot. Adding libtest-warn-perl to Build-Depends fixes this. Thanks, Jeremy Bicha Excerpt from build log below: dh_auto_configure perl -I. Build.PL --installdirs vendor --config

Processed: block 835941 with 835940

Processing commands for cont...@bugs.debian.org: > block 835941 with 835940 Bug #835941 [starpu-contrib] starpu-contrib: non-standard gcc/g++ used for build (gcc-5) 835941 was not blocked by any bugs. 835941 was not blocking any bugs. Added blocking bug(s) of 835941: 835940 > thanks Stopping

<    1   2