Bug#863267: [Python-modules-team] Bug#863267: Associated removals

On May 26, 2017 12:30:17 AM EDT, Neil Williams wrote: >On Fri, 26 May 2017 04:11:49 + >Scott Kitterman wrote: > >> I don't see any way to completely resolve this before stretch >> releases other than removing lava-server. > >This is a *django*

Bug#863267: [Python-modules-team] Bug#863267: Associated removals

On Fri, 26 May 2017 04:11:49 + Scott Kitterman wrote: > I don't see any way to completely resolve this before stretch > releases other than removing lava-server. This is a *django* bug! There is no evidence that lava-server is responsible for this - it just has to use

Bug#863267: Associated removals

I don't see any way to completely resolve this before stretch releases other than removing lava-server. Scott K

Bug#863387: Acknowledgement (dh produces incomplete binary packages)

Am 26.05.2017 um 05:48 schrieb Debian Bug Tracking System: > As you can see from the 10.3 log, a lot of helpers are not run, like > dh_installdirs, dh_bugfiles, dh_lintian, etc. Comparing the output, I see the following helpers are not run with 10.3: dh_installdirs dh_installman dh_bugfiles

Processed: Miscalculates MigrationHistory dependencies between multiple django apps - regression from 1.8

Processing commands for cont...@bugs.debian.org: > reopen 863267 Bug #863267 {Done: Scott Kitterman } [src:python-django] python-django: Upgrades from jessie to stretch Bug reopened Ignoring request to alter fixed versions of bug #863267 to the same values previously set >

Bug#863387: dh produces incomplete binary packages

Package: debhelper Version: 10.3 Severity: grave Hi, I just noticed that debhelper from experimental produces incomplete binary packages. I've attached log building init-system-helpers with 10.2.5 and 10.3 As you can see from the 10.3 log, a lot of helpers are not run, like dh_installdirs,

Bug#861282: marked as done (packer: FTBFS)

Your message dated Fri, 26 May 2017 00:33:50 + with message-id and subject line Bug#861282: fixed in packer 0.10.2+dfsg-6 has caused the Debian Bug report #861282, regarding packer: FTBFS to be marked as done. This means that you claim that the problem

Bug#861548: marked as done (packer: FTBFS with latest golang-go.crypto)

Your message dated Fri, 26 May 2017 00:33:50 + with message-id and subject line Bug#861282: fixed in packer 0.10.2+dfsg-6 has caused the Debian Bug report #861282, regarding packer: FTBFS with latest golang-go.crypto to be marked as done. This means that

Bug#861282: packer: FTBFS

On Thu, 25 May 2017 13:00:39 -0400 (EDT) JD Friedrikson wrote: > The new changes package nicely and pass the tests just fine. I can confirm > that the fix works for qemu. I'm having some issues with Virtualbox, but I've > also always had trouble with Virtualbox and

Processed: This FTBFS is not in jessie

Processing commands for cont...@bugs.debian.org: > tags 857897 stretch sid Bug #857897 {Done: Andreas Beckmann } [src:qtads] qtads FTBFS on 32bit: error: exception cleanup for this placement new selects non-placement operator delete Added tag(s) stretch and sid. > thanks

Bug#846677: tomcatjss: FTBFS: [javac] /<>/src/org/apache/tomcat/util/net/jss/IJSSFactory.java:26: error: cannot find symbol

Hi, I just came across this problem when trying to compile myself. This is due to the fact upstream don't yet support tomcat 8.5. The support for tomcat 8.5 is being tracked at https://pagure.io/tomcatjss/issue/1

Processed: The nickle FTBFS are not in jessie

Processing commands for cont...@bugs.debian.org: > tags 857814 stretch sid Bug #857814 {Done: Keith Packard } [src:nickle] nickle FTBFS on mips: 14 of 14 tests failed Bug #857840 {Done: Keith Packard } [src:nickle] nickle: FTBFS on mips - value.h:980:

Processed: Not a problem with the version of python-tornado in jessie

Processing commands for cont...@bugs.debian.org: > tags 806969 stretch sid Bug #806969 {Done: Debian FTP Masters } [python-tornadio2] auto_start option crashes with current tornado Added tag(s) stretch and sid. > tags 807029 stretch sid Bug #807029 {Done: Debian

Processed: Bug was introduced in 1.3.0-1

Processing commands for cont...@bugs.debian.org: > found 794461 1.3.0-1 Bug #794461 {Done: Thomas Goirand } [python-mock] RequirementParseError: Expected version spec in funcsigs; python_version<"3.3" at ; python_version<"3.3" Marked as found in versions python-mock/1.3.0-1. >

Processed: tagging 861515

Processing commands for cont...@bugs.debian.org: > # arch:all, builds fine on amd64 > tags 861515 + stretch-ignore Bug #861515 [src:node-grunt-contrib-copy] src:node-grunt-contrib-copy: FTBFS on armhf i386: test failure: ✖ copy - timestamp_equal Ignoring request to alter tags of bug #861515 to

Bug#839575: marked as done (hangs waiting for openssl)

Your message dated Thu, 25 May 2017 21:33:55 + with message-id and subject line Bug#839575: fixed in openssl 1.1.0f-1 has caused the Debian Bug report #839575, regarding hangs waiting for openssl to be marked as done. This means that you claim that the

Bug#861591: libgnupg-interface-perl: FTBFS: Failed 10/22 test programs. 23/53 subtests failed.

On Thu 2017-05-25 18:35:13 +0200, Chris Lamb wrote: > Daniel Kahn Gillmor wrote: > >> The failures on repeat are presumably because of something related to >> the gpg-agent daemon persisting across the tests.I'll look into >> invoking "gpgconf --kill all" at the start of the test suite > > Is

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > forcemerge 808433 824718 Bug #808433 {Done: Arnout Engelen } [nethogs] nethogs doesn't start, saying "creating socket failed" Bug #811273 {Done: Arnout Engelen } [nethogs] nethogs: creating socket failed

Bug#851564: nslcd fails to start: postinst sets tls_cacertdir wrong

On Tue, Jan 17, 2017 at 02:46:01PM +0100, Arthur de Jong wrote: >... > This fix is pretty simple and a patch is attached for reference. I will > prepare a fix for unstable and try to get a fix into jessie soon. ping regarding the jessie fix. > Thanks, Thanks Adrian -- "Is there not

Processed: Add found version to phyml bugs that are not in jessie

Processing commands for cont...@bugs.debian.org: > found 853211 3:3.2.0+dfsg-2 Bug #853211 {Done: Andreas Tille } [phyml] phyml: Fails to use mpi Marked as found in versions phyml/3:3.2.0+dfsg-2. > found 853738 3:3.2.0+dfsg-2 Bug #853738 {Done: Andreas Tille }

Processed: viva builds for me in jessie

Processing commands for cont...@bugs.debian.org: > tags 827349 stretch sid Bug #827349 {Done: Martin Quinson } [pajeng] viva: FTBFS: Parse error at "BOOST_JOIN" Added tag(s) sid and stretch. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: Problem is not in jessie

Processing commands for cont...@bugs.debian.org: > tags 855324 stretch sid Bug #855324 {Done: Markus Koschany } [pdfsam] pdfsam fails to start Added tag(s) sid and stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 855324:

Bug#861165: marked as done (padre does not start - DBD::SQLite::db do failed ...)

Your message dated Thu, 25 May 2017 22:19:38 +0300 with message-id <20170525191938.wws5v22fbkykqxn7@localhost> and subject line padre starts in jessie and was removed after jessie has caused the Debian Bug report #861165, regarding padre does not start - DBD::SQLite::db do failed ... to be marked

Bug#860830: marked as done (debian-archive-keyring: ftp-master key for stretch)

Your message dated Thu, 25 May 2017 19:18:42 + with message-id and subject line Bug#860830: fixed in debian-archive-keyring 2017.5 has caused the Debian Bug report #860830, regarding debian-archive-keyring: ftp-master key for stretch to be marked as done.

Bug#860831: marked as done (debian-archive-keyring: release key for stretch?)

Your message dated Thu, 25 May 2017 19:18:42 + with message-id and subject line Bug#860831: fixed in debian-archive-keyring 2017.5 has caused the Debian Bug report #860831, regarding debian-archive-keyring: release key for stretch? to be marked as done.

Processed: Bug was introduced in 1.1.0

Processing commands for cont...@bugs.debian.org: > found 839575 1.1.0-1 Bug #839575 [openssl] hangs waiting for openssl Marked as found in versions openssl/1.1.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 839575:

Bug#740893: Patch for python-coverage bug #740893

I did some further testing around changing the version of jquery.hotkeys.js in libjs-jquery-hotkeys to the upstream jeresig version, and behavior of the various libraries that depend on it. For python-coverage, the bug is still there, with the addition of a new error related to differences in

Bug#863367: libecryptfs-dev: unable to install because of unmet dependency

Package: libecryptfs-dev Severity: grave Justification: renders package unusable Currently libecryptfs-dev is uninstallable on Stretch. This is the output when trying to install: # apt-get install libecryptfs-dev Reading package lists... Done Building dependency tree Reading state

Processed: PIE issue, not in jessie

Processing commands for cont...@bugs.debian.org: > tags 86 stretch sid Bug #86 {Done: Gilles Filippini } [paw] pawX11 crashes at start Added tag(s) stretch and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 86:

Processed: Nothing to be fixed in jessie

Processing commands for cont...@bugs.debian.org: > tags 848111 stretch sid Bug #848111 {Done: Ondřej Surý } [opendnssec-enforcer-mysql] opendnssec-enforcer-mysql: fails to upgrade from 'jessie': dpkg-maintscript-helper: error: conffile 'conf.xml' is not an absolute path Added

Processed: Bug was introduced in 1.3.2~Beta0+dfsg-3

Processing commands for cont...@bugs.debian.org: > found 863173 1.3.2~Beta0+dfsg-3 Bug #863173 {Done: Scott Kitterman } [opendmarc] opendmarc: forcefully removes conffile on upgrade Marked as found in versions opendmarc/1.3.2~Beta0+dfsg-3. > thanks Stopping processing here.

Processed: limit source to debian-archive-keyring, tagging 860831, tagging 863303, tagging 860830

Processing commands for cont...@bugs.debian.org: > limit source debian-archive-keyring Limiting to bugs with field 'source' containing at least one of 'debian-archive-keyring' Limit currently set to 'source':'debian-archive-keyring' > tags 860831 + pending Bug #860831

Processed: Processed: Bug was introduced in 1:1.2.8-9.1

Processing commands for cont...@bugs.debian.org: > notfound 828826 1:1.2.8-9 Bug #828826 {Done: Andreas Henriksson } [nfs-common] nfs-common: move of rpc_pipefs mountpoint to /run breaks blkmapd No longer marked as found in versions nfs-utils/1:1.2.8-9. > thanks Stopping

Processed: Bug was introduced in 1:1.2.8-9.1

Processing commands for cont...@bugs.debian.org: > found 828826 1:1.2.8-9.1 Bug #828826 {Done: Andreas Henriksson } [nfs-common] nfs-common: move of rpc_pipefs mountpoint to /run breaks blkmapd Marked as found in versions nfs-utils/1:1.2.8-9.1. > thanks Stopping processing

Processed: Bug was introduced in 1.1-2

Processing commands for cont...@bugs.debian.org: > found 801582 1.1-2 Bug #801582 {Done: Tobias Grimm } [nvram-wakeup] grub-pc: default entry becomes Halt once (for setting alarm) => no boot There is no source info for the package 'nvram-wakeup' at version '1.1-2' with

Bug#851385: need to shed big-endian B-Dependencies?

Hi! It looks like fixing this FTBFS isn't viewed as high priority. Understandably, as big endian is basically dead: in Debian, only release archs left are mips and s390x; the former seems to be on its way out (in favour of mips64el), the latter has no graphical hardware whatsoever. There's no

Bug#793796: This package should be removed

It's not compatible with plasma5, it would need porting. The maintainer doesn't seem active and only has this one package.

Processed: Conpletely broken in jessie, fixed in stretch

Processing commands for cont...@bugs.debian.org: > severity 855453 serious Bug #855453 [mps-youtube] mps-youtube can't search anything Severity set to 'serious' from 'important' > fixed 855453 0.2.7.1-2 Bug #855453 [mps-youtube] mps-youtube can't search anything Marked as fixed in versions

Bug#863224: acl2: build fails on mips (mips-aql-05)

Greetings, and thanks for your report! How much memory is on the build machine? Please note mipsel builds fine. The log you report seems to indicate a very tight build space and endless garbage collection. Take care, Héctor Orón Martínez writes: > Source: acl2 >

Processed: Bug#828159: iceweasel -> firefox-esr upgrades won't be relevant for buster

Processing commands for cont...@bugs.debian.org: > tags 828159 wheezy jessie stretch Bug #828159 [firefox-esr] firefox-esr: session tabs lost after upgrade from iceweasel to firefox-esr Added tag(s) jessie, stretch, and wheezy. > thanks Stopping processing here. Please contact me if you need

Bug#828159: iceweasel -> firefox-esr upgrades won't be relevant for buster

tags 828159 wheezy jessie stretch thanks iceweasel -> firefox-esr upgrades won't be relevant for buster since iceweasel won't ever be in post-release stretch. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain

Bug#861282: packer: FTBFS

> > Thanks for your info! > I pushed a commit to new branch fix_861282, that applied: > ee5d13611fb8aca1f1014f9bcd65c18fffdd1b2b > a0052fdb687f80ac07e67d7a0f39dcf3a66e32dd > > (https://anonscm.debian.org/cgit/pkg-go/packages/packer.git/log/?h=fix_861282) > > Please help

Bug#861591: libgnupg-interface-perl: FTBFS: Failed 10/22 test programs. 23/53 subtests failed.

Daniel Kahn Gillmor wrote: > The failures on repeat are presumably because of something related to > the gpg-agent daemon persisting across the tests.I'll look into > invoking "gpgconf --kill all" at the start of the test suite Is that safe? What if I'm running gpgconf outside of the build?

Bug#861591: libgnupg-interface-perl: FTBFS: Failed 10/22 test programs. 23/53 subtests failed.

On Mon 2017-05-01 10:11:51 +0200, Salvatore Bonaccorso wrote: >> HOME=/home/lamby >> LOGNAME=lamby >> SHLVL=1 >> PWD=/home/lamby/temp/cdt.20170430222311.WuN76MAfhh.db.libgnupg-interface-perl/libgnupg-interface-perl-0.52 >>

Bug#817837: closed by Jonathan McDowell <nood...@earth.li> (Bug#817837: fixed in l2tpns 2.2.1-2)

On Thu, May 18, 2017 at 08:02:49PM +0100, Jonathan McDowell wrote: > On Sun, May 14, 2017 at 09:15:50PM +0300, Adrian Bunk wrote: > > On Tue, Jul 05, 2016 at 10:09:57AM +, Debian Bug Tracking System wrote: > > >... > > > l2tpns (2.2.1-2) unstable; urgency=low > > > . > > >* Fix log

Bug#863042: marked as done (dehydrated: insecure file permissions by default)

Your message dated Thu, 25 May 2017 18:10:47 +0300 with message-id <20170525181047.46bec...@brick.gerasiov.net> and subject line Re: [Letsencrypt-devel] Bug#863042: dehydrated: insecure file permissions by default has caused the Debian Bug report #863042, regarding dehydrated: insecure file

Processed: Not a problem with the irssi in jessie

Processing commands for cont...@bugs.debian.org: > tags 817172 stretch sid Bug #817172 {Done: Holger Levsen } [irssi-plugin-otr] irssi-plugin-otr: plugin not in multiarch directory Added tag(s) stretch and sid. > thanks Stopping processing here. Please contact me if you

Processed: Re: Bug#863276: nvidia-driver: nvidia fails to initialize Xorg with linux-image-4.9.0-0.bpo.3-amd64

Processing control commands: > severity -1 normal Bug #863276 [nvidia-driver] nvidia-driver: nvidia fails to initialize Xorg with linux-image-4.9.0-0.bpo.3-amd64 Severity set to 'normal' from 'grave' -- 863276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863276 Debian Bug Tracking System

Bug#863276: nvidia-driver: nvidia fails to initialize Xorg with linux-image-4.9.0-0.bpo.3-amd64

Control: severity -1 normal On Thu, 2017-05-25 at 09:18 +0200, Harald Dunkel wrote: > I am still running nvidia-graphics-drivers 375.26-1~bpo8+1 together > with the > new linux-image-4.9.0-0.bpo.3-amd64:amd64. This combination seems to > work > fine. > > Other interesting packages in this

Processed: severity of 847277 is grave

Processing commands for cont...@bugs.debian.org: > severity 847277 grave Bug #847277 [lava-server] django migrations in jessie require django from jessie-backports to upgrade to stretch Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need

Bug#863337: visualvm: Typos in launcher script - does not start anymore

Package: visualvm Version: 1.3.9-1 Severity: grave Justification: renders package unusable visualvm does not start anymore with the error: Unknown option -L-XX:PermSize=32m This is caused by a trivial typo in the start script, which supposedly should use -J (like "Java options") instead of -L

Processed: Also add an affects

Processing commands for cont...@bugs.debian.org: > affects 861575 tilix Bug #861575 [src:gtk-d] libgtkd-3-0 and libvted-3-0 shlibs need a version Added indication that 861575 affects tilix > thanks Stopping processing here. Please contact me if you need assistance. -- 861575:

Processed: Re: Bug#861575: tilix: Does not start on Stretch (symbol lookup error: undefined symbol)

Processing control commands: > reassign -1 src:gtk-d Bug #861575 [tilix] tilix: Does not start on Stretch (symbol lookup error: undefined symbol) Bug reassigned from package 'tilix' to 'src:gtk-d'. No longer marked as found in versions tilix/1.5.4-1. Ignoring request to alter fixed versions of

Bug#861575: tilix: Does not start on Stretch (symbol lookup error: undefined symbol)

Control: reassign -1 src:gtk-d Control: retitle -1 libgtkd-3-0 and libvted-3-0 shlibs need a version On Wed, May 03, 2017 at 01:19:16PM -0400, Mathieu Basille wrote: >... > Thanks for looking it up! As a matter of fact, it looks like both > libgtkd-3-0 and libvted-3-0 needs to be >= 3.5.1-1.

Bug#861178: nodejs-dev: broken/uninstallable backports

2017-05-25 13:19 GMT+02:00 Łukasz Stelmach : > Control: merge -1 862962 > > The problem still exists in 4.8.2~dfsg-1~bpo8+1 and apt-cache shows > nodejs-dev depends on libssl1.0-dev. > It's a fact that nodejs depends on libssl 1.0. If the backport only has libssl-dev

Bug#861178: nodejs-dev: broken/uninstallable backports

Control: merge -1 862962 The problem still exists in 4.8.2~dfsg-1~bpo8+1 and apt-cache shows nodejs-dev depends on libssl1.0-dev. --8<---cut here---start->8--- Package: nodejs-dev Source: nodejs Version: 4.8.2~dfsg-1~bpo8+1 Installed-Size: 1329 Maintainer:

Processed (with 1 error): nodejs-dev: broken/uninstallable backports

Processing control commands: > merge -1 862962 Bug #861178 {Done: Gianfranco Costamagna } [nodejs-dev] nodejs-dev: broken/uninstallable backports Unable to merge bugs because: severity of #862962 is 'important' not 'grave' done of #862962 is '' not 'Gianfranco

Bug#852732: marked as done (torbrowser-launcher: upon upggrade 6.0.8 to 6.5: "SIGNATURE VERIFICATION FAILED: You might be under attack ...")

Your message dated Thu, 25 May 2017 10:18:46 + with message-id and subject line Bug#852732: fixed in torbrowser-launcher 0.2.7-2 has caused the Debian Bug report #852732, regarding torbrowser-launcher: upon upggrade 6.0.8 to 6.5: "SIGNATURE VERIFICATION

Processed: tagging 861515

Processing commands for cont...@bugs.debian.org: > # arch:all, builds fine on amd64 > tags 861515 + stretch-ignore Bug #861515 [src:node-grunt-contrib-copy] src:node-grunt-contrib-copy: FTBFS on armhf i386: test failure: ✖ copy - timestamp_equal Added tag(s) stretch-ignore. > thanks Stopping

Processed: libtasn1-6: diff for NMU version 4.10-1.1

Processing control commands: > tags 863186 + pending Bug #863186 [src:libtasn1-6] libtasn1-6: CVE-2017-6891 Added tag(s) pending. -- 863186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#863186: libtasn1-6: diff for NMU version 4.10-1.1

Control: tags 863186 + pending Dear maintainer, I've prepared an NMU for libtasn1-6 (versioned as 4.10-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer (or reschedule to earlier, or cancel if you would like to do an upload on your own). Regards,

Bug#860830: debian-archive-keyring: ftp-master key for stretch

Please include the new automatic signing keys for 9/stretch. The keys are signed by the current ftp masters and the previous archive signing keys. They were announced at [1]. Ansgar [1] https://lists.debian.org/debian-devel-announce/2017/05/msg1.html -BEGIN PGP PUBLIC KEY BLOCK-

Processed: found 863301 in 0.99+dfsg-1

Processing commands for cont...@bugs.debian.org: > # add found version for version tracking > found 863301 0.99+dfsg-1 Bug #863301 {Done: Johannes Schauer } [src:vcmi] vcmi: removing a mod can recursively delete $HOME Marked as found in versions vcmi/0.99+dfsg-1. > thanks

Processed: tagging 861952

Processing commands for cont...@bugs.debian.org: > # Maintainer removed it from stretch > tags 861952 - stretch-ignore Bug #861952 {Done: Debian FTP Masters } [src:libcgi-validop-perl] libcgi-validop-perl: FTBFS on May 1st (?) Removed tag(s) stretch-ignore. >

Bug#857444: marked as done (mysql-server-5.5: upgrade from jessie to stretch leaves mysql server uninstalled)

Your message dated Thu, 25 May 2017 09:24:01 +0200 with message-id <1495697041.3725029.988032192.35810...@webmail.messagingengine.com> and subject line Re: [debian-mysql] Bug#857444: Bug#857444: Moving to src:mariadb-10.1 has caused the Debian Bug report #857444, regarding mysql-server-5.5:

Bug#854819: GnuPG 2 support in Horde_Crypt

Mathieu Parent: > severity 854819 serious > tag 854819 - patch + upstream > tag 849151 - patch > thanks > > Some news about this: upstream has worked on this, but I needed two > more patches for complete support > (https://github.com/horde/horde/pull/221). > > Niels, I plan to do the following:

Bug#863236: kodi: Kodi advising to upgrade to 17.2, due to security flaw - there is an update from Kodi

Package: kodi Version: 2:17.1+dfsg1-2 Followup-For: Bug #863236 Dear Maintainer, Just an update. I see, today, on twitter, Kodi is requesting to upgrade to 17.3 and not 17.2, as I previously reported. Links(s) : https://twitter.com/TVADDONS/status/867565348115107841 More here:

Bug#863301: marked as done (vcmi: removing a mod can recursively delete $HOME)

Your message dated Thu, 25 May 2017 07:03:40 + with message-id and subject line Bug#863301: fixed in vcmi 0.99+dfsg-2 has caused the Debian Bug report #863301, regarding vcmi: removing a mod can recursively delete $HOME to be marked as done. This means

Bug#863301: vcmi: removing a mod can recursively delete $HOME

Source: vcmi Severity: critical Tags: patch Justification: causes serious data loss Under the right circumstances, removing a mod can recursively remove $HOME. For more details see the upstream bugs: http://bugs.vcmi.eu/view.php?id=2673 http://bugs.vcmi.eu/view.php?id=2680 Patch is attached.