Bug#885525: [Pkg-utopia-maintainers] Bug#885525: better log output

Hey Russel, Would you mind trying out my patch? To rebuild yourself with the patch you can follow this. It will grab the dependencies needed, and the source of nm-applet. ``` apt-get build-dep network-manager-gnome apt-get source network-manager-gnome cd network-manager-applet-1.8.10/debian/patch

Bug#886710: cp2k: uses deprecated BLACS

Package: cp2k Version: 5.1-2 Severity: serious Justification: deprecated dependency You have not incorporated nmu 4.1-1.1 into your cp2k packaging. libblacs-mpi-dev is no longer provided as a separate package since it is now provided by libscalapack-mpi-dev 2.0.2. So libblacs-mpi-dev should not

Processed: bug 886683 is forwarded to https://github.com/spesmilo/electrum/issues/3374, tagging 886683

Processing commands for cont...@bugs.debian.org: > forwarded 886683 https://github.com/spesmilo/electrum/issues/3374 Bug #886683 [electrum] electrum: Security vulnerability in electrum Set Bug forwarded-to-address to 'https://github.com/spesmilo/electrum/issues/3374'. > tags 886683 + upstream fix

Bug#876931: marked as done (psycopg2 FTBFS with Sphinx 1.6: Could not import extension dbapi_extension)

Your message dated Tue, 09 Jan 2018 06:04:19 + with message-id and subject line Bug#876931: fixed in psycopg2 2.7.3-2 has caused the Debian Bug report #876931, regarding psycopg2 FTBFS with Sphinx 1.6: Could not import extension dbapi_extension to be marked as done. This means that you claim

Processed: Bug#876931 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 876931 pending Bug #876931 [src:psycopg2] psycopg2 FTBFS with Sphinx 1.6: Could not import extension dbapi_extension Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 876931: https://bugs.

Bug#876931: marked as pending

tag 876931 pending thanks Hello, Bug #876931 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: https://anonscm.debian.org/cgit/python-modules/packages/psycopg2.git/commit/?id=4ac0466 --- commit 4ac0466e80ea6ae1c

Processed: Re: ed: ships /usr/share/info/dir.gz on arm64

Processing commands for cont...@bugs.debian.org: > close 799702 Bug #799702 [ed] ed: ships /usr/share/info/dir.gz on arm64 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 799702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799702 Debian Bu

Bug#886704: fotoxx: unsatisfiable dep on fotoxx-common

Package: fotoxx Version: 18.01.1-1 Severity: grave Justification: renders package unusable It seems fotoxx-common got lost but is still a dependency, so the package is uninstallable. Thanks -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstab

Bug#886683: [Pkg-bitcoin-devel] Bug#886683: electrum: Security vulnerability in electrum

Control: found -1 2.4.2+dfsg1-1 Control: fixed -1 3.0.5-1 On Tue, 9 Jan 2018 at 00:21 Daniel Koszta wrote: > A new, fixed version is already available in debian unstable, but it > should be included in stable and testing as soon as possible. > Unfortunately the version in stable is too old to b

Processed: Re: [Pkg-bitcoin-devel] Bug#886683: electrum: Security vulnerability in electrum

Processing control commands: > found -1 2.4.2+dfsg1-1 Bug #886683 [electrum] electrum: Security vulnerability in electrum Marked as found in versions electrum/2.4.2+dfsg1-1. > fixed -1 3.0.5-1 Bug #886683 [electrum] electrum: Security vulnerability in electrum Marked as fixed in versions electrum/

Bug#885889: marked as done (sasview: FTBFS: debian/sasview might not exist)

Your message dated Tue, 09 Jan 2018 03:05:16 + with message-id and subject line Bug#885889: fixed in sasview 4.2.0~git20171031-3 has caused the Debian Bug report #885889, regarding sasview: FTBFS: debian/sasview might not exist to be marked as done. This means that you claim that the problem

Bug#886700: python-pyasn1-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc-base/python-pyasn1

Package: python-pyasn1-doc Version: 0.4.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite oth

Bug#886698: sollya-doc: fails to upgrade from 'stretch' - trying to overwrite /usr/share/doc/sollya/AUTHORS

Package: sollya-doc Version: 6.0+ds-4 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 because it tries to overwrite othe

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

> I’m very very sorry, that you think I’m NOT understanding „Specter" and > what this shows. - I understand this very well! ;) > > *FOR YOU:* > *== > * > PLEASE look at the possibilities of the new *version 57.0.4 of Firefox*. > *With this special created release (of this browser) you can PATC

Bug#886695: svxlink-calibration-tools: fails to upgrade from 'stretch' - trying to overwrite /usr/bin/siglevdetcal

Package: svxlink-calibration-tools Version: 15.11+20171207~git445-380e5333-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' f

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

I’m very very sorry, that you think I’m NOT understanding „Specter" and what this shows. - I understand this very well! ;) FOR YOU: == PLEASE look at the possibilities of the new version 57.0.4 of Firefox. With this special created release (of this browser) you can PATCH the Microcode AGAIN

Bug#886050: marked as done (openbox-gnome-session: Depends on gconf)

Your message dated Mon, 08 Jan 2018 23:50:11 + with message-id and subject line Bug#886050: fixed in openbox 3.6.1-6 has caused the Debian Bug report #886050, regarding openbox-gnome-session: Depends on gconf to be marked as done. This means that you claim that the problem has been dealt with

Bug#886683: electrum: Security vulnerability in electrum

Package: electrum Version: 3.0.3-1 Severity: grave Tags: security Justification: user security hole Dear Maintainer, Many Electrum versions are vulnerable, see https://github.com/spesmilo/electrum/issues/3374. A new, fixed version is already available in debian unstable, but it should be include

Bug#886431: marked as done (snapd binary-all FTBFS: install: failed to access debian/snapd///usr/lib/snapd: No such file or directory)

Your message dated Mon, 08 Jan 2018 22:05:00 + with message-id and subject line Bug#886431: fixed in snapd 2.30-2 has caused the Debian Bug report #886431, regarding snapd binary-all FTBFS: install: failed to access debian/snapd///usr/lib/snapd: No such file or directory to be marked as done.

Bug#886572: marked as done (texstudio FTBFS: does not find quazip)

Your message dated Mon, 08 Jan 2018 22:05:11 + with message-id and subject line Bug#886572: fixed in texstudio 2.12.6+debian-2 has caused the Debian Bug report #886572, regarding texstudio FTBFS: does not find quazip to be marked as done. This means that you claim that the problem has been de

Processed: reassign 878201 to src:audiocd-kio, fixed 878201 in 4:17.08.3-1 ..., fixed 886374 in 2017.20180103-2

Processing commands for cont...@bugs.debian.org: > reassign 878201 src:audiocd-kio 4:16.08.3-1 Bug #878201 {Done: Pino Toscano } [kdemultimedia-kio-plugins,kdemultimedia-dev] please drop transitional packages kdemultimedia-kio-plugins and kdemultimedia-dev Bug reassigned from package 'kdemultime

Bug#886676: debian-parl: needs to depend on hunspell-nl instead of myspell-nl

Source: debian-parl Version: 1.9.13 Severity: serious Hi, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761032. myspell-nl is (supposed to be) gone and renamed to hunspell-nl. Please adapt. Regards, Rene

Processed: severity of 886674 is important

Processing commands for cont...@bugs.debian.org: > severity 886674 important Bug #886674 [src:opencv] opencv: CVE-2018-5268 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 886674: https://bugs.debian.org/cgi-bin/bugreport.c

Processed (with 1 error): Re: Bug#886674: opencv: CVE-2018-5268

Processing control commands: > severity important Unknown command or malformed arguments to command. > tags -1 + upstream Bug #886674 [src:opencv] opencv: CVE-2018-5268 Added tag(s) upstream. -- 886674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886674 Debian Bug Tracking System Contact

Bug#886674: opencv: CVE-2018-5268

Control: severity important Control: tags -1 + upstream Adjusting severity, got wrong before sending bug. Regards, Salvatore

Bug#886674: opencv: CVE-2018-5268

Source: opencv Version: 3.2.0+dfsg-1 Severity: grave Tags: security Forwarded: https://github.com/opencv/opencv/issues/10541 Hi, the following vulnerability was published for opencv, please double-check. CVE-2018-5268[0]: | In OpenCV 3.3.1, a heap-based buffer overflow happens in | cv::Jpeg2KDec

Bug#866495: marked as done (woo: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Mon, 08 Jan 2018 21:05:18 + with message-id and subject line Bug#866495: fixed in woo 1.0+dfsg1-2 has caused the Debian Bug report #866495, regarding woo: depends on obsolete python-imaging (replace with python3-pil or python-pil) to be marked as done. This means that you

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

Sorry it’s NOT enough. Don’t worry I trust Intel for changing Intel CPUs; I trust AMD for changing AMD CPUs, etc. NO problem with that! - But SIMPLYFYED: How can Firefox 57.0.4 change the Intel CPU/MMU - Microcode if such change need a secret code signature and don’t know anything secured from m

Bug#884078: marked as done (rapidjson: Source includes "bin/jsonchecker/fail1.json etc." listed in Files-Excluded header)

Your message dated Mon, 08 Jan 2018 20:51:55 + with message-id and subject line Bug#884078: fixed in rapidjson 1.1.0+dfsg2-1 has caused the Debian Bug report #884078, regarding rapidjson: Source includes "bin/jsonchecker/fail1.json etc." listed in Files-Excluded header to be marked as done.

Bug#886432: marked as done (snapd FTBFS on 32bit: json.go:320:7: constant 9007199254740992 overflows int)

Your message dated Mon, 08 Jan 2018 20:51:11 + with message-id and subject line Bug#886432: fixed in golang-gopkg-mgo.v2 2016.08.01-2 has caused the Debian Bug report #886432, regarding snapd FTBFS on 32bit: json.go:320:7: constant 9007199254740992 overflows int to be marked as done. This me

Bug#886662: wireguard-dkms should depend on libelf-dev

On Mon 2018-01-08 13:34:53 -0500, Robert Edmonds wrote: > You may want to hold off on fixing this in wireguard. It looks like this > is a regression in src:linux (#886474). Given this failure is coming > from the kernel build system apparently before the module itself even > starts building, it wou

Bug#862851: vblade-persist: diff for NMU version 0.6-2.1

On Sat 2018-01-06 14:56:50 +, Luca Boccassi wrote: > Control: tags 862851 + patch > Control: tags 862851 + pending > > [Replace XX with correct value] > Dear maintainer, > > I've prepared an NMU for vblade-persist (versioned as 0.6-2.1) and > uploaded it to DELAYED/XX. Please feel free to tell

Bug#886494: polymake: Can't locate loadable object for module Polymake::Ext in @INC

On Sun, Jan 07, 2018 at 05:04:17PM +0200, Niko Tyni wrote: > The wasted stats could certainly be fixed by modifying our relevant > changes to perl.c > > https://sources.debian.org/src/perl/5.26.1-3/debian/patches/debian/mod_paths.diff/ > but I haven't looked into that properly yet. I did this n

Bug#886431: snapd binary-all FTBFS: install: failed to access debian/snapd///usr/lib/snapd: No such file or directory

Thanks for the report. This is fixed in git, will wait until my gopkg.in/mgo.v2 upload for the 32 bit issues gets published before uploading. On 6 January 2018 at 10:59, Adrian Bunk wrote: > Source: snapd > Version: 2.30-1 > Severity: serious > > https://buildd.debian.org/status/fetch.php?pkg=sn

Bug#753719: ucarp: diff for NMU version 1.5.2-2.1

[ Luca Boccassi ] > [ ... ] > > I've prepared an NMU for ucarp (versioned as 1.5.2-2.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should delay it longer. No, that's fine; Thanks for the help Luca! -- Eric Evans eev...@debian.org

Processed: limit source to qca2, tagging 850897, tagging 874758

Processing commands for cont...@bugs.debian.org: > limit source qca2 Limiting to bugs with field 'source' containing at least one of 'qca2' Limit currently set to 'source':'qca2' > tags 850897 + pending Bug #850897 [src:qca2] qca2: Please migrate to openssl1.1 in buster Added tag(s) pending. > ta

Bug#869994: proposed fix

> Greetings all using FindBin and adding the current directory everywhere > sql-ledger calls perl should fix the issue in all versions. I appreciate the example perl script you provided but since it's known where the package is installing sql-ledger to, I don't think using "FindBin" is necessar

Processed: reassign 885570 to src:linux, forcibly merging 884061 885570 884116 884001

Processing commands for cont...@bugs.debian.org: > reassign 885570 src:linux Bug #885570 [linux-image-4.9.0-4-amd64] linux-image-4.9.0-4-amd64: display breakage with Intel HD Graphics 5500 Bug reassigned from package 'linux-image-4.9.0-4-amd64' to 'src:linux'. No longer marked as found in version

Processed (with 1 error): Re: Bug#885570: Duplicate of 884061 ?

Processing control commands: > forcemerge 884061 885570 884116 884001 Bug #884061 [src:linux] linux-image-4.9.0-4-amd64: screen scrolls wildly Unable to merge bugs because: package of #885570 is 'linux-image-4.9.0-4-amd64' not 'src:linux' Failed to forcibly merge 884061: Did not alter merged bugs.

Bug#885570: Duplicate of 884061 ?

control: forcemerge 884061 885570 884116 884001 On Sun, 2017-12-31 at 01:35 +0100, Adrien Plan wrote: > Hi, > > I got the same issue on my i915 notebook (Dell E7450) and I had to boot > on previous kernel (linux-image-4.9.0-3-amd64) > > This bug report seems the same and suggest a tested revert

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

*Sorry it’s NOT enough.* Don’t worry I trust Intel for changing Intel CPUs; I trust AMD for changing AMD CPUs, etc. NO problem with that! - But SIMPLYFYED: How can Firefox 57.0.4 change the Intel CPU/MMU - Microcode if such change need a secret code signature and don’t know anything secured fr

Processed: reassign 886432 to src:golang-gopkg-mgo.v2

Processing commands for cont...@bugs.debian.org: > reassign 886432 src:golang-gopkg-mgo.v2 Bug #886432 [src:snapd] snapd FTBFS on 32bit: json.go:320:7: constant 9007199254740992 overflows int Bug reassigned from package 'src:snapd' to 'src:golang-gopkg-mgo.v2'. No longer marked as found in versio

Bug#885570: linux-image-4.9.0-5-amd64

Hi, Same problem with linux-image-4.9.0-5-amd64. The bad thing is: now we have the choice between being protected against meltdown and have terrible artifacts, or go back to linux-image-4.9.0-3-amd64, but being vulnerable to meltdown. Pierre.

Processed: The debian/rules change fixes it

Processing commands for cont...@bugs.debian.org: > tags 883986 patch Bug #883986 [src:openscad] openscad: FTBFS on mips/mipsel: virtual memory exhausted: Cannot allocate memory Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 883986: https://bu

Bug#883986: openscad: FTBFS on mips/mipsel: virtual memory exhausted: Cannot allocate memory

On Sun, Dec 10, 2017 at 03:52:04AM +0100, Andreas Beckmann wrote: > Source: openscad > Version: 2015.03-2+dfsg-2 > Severity: serious > Tags: sid buster > Justification: fails to build from source (but built successfully in the past) > > Hi, > > openscad did run out of memory during the recent bin

Bug#886670: libcgal-dev: CGAL_CXX_FLAGS_INIT contains flags that shouldn't be there

Package: libcgal-dev Version: 4.11-2 Severity: serious Control: block 883986 by -1 While looking into fixing #883986 I ran into the following problem due to openscad using CGAL_CXX_FLAGS_INIT: /usr/lib/x86_64-linux-gnu/cmake/CGAL/CGALConfig.cmake: set(CGAL_CXX_FLAGS_INIT "-g -O2

Processed: libcgal-dev: CGAL_CXX_FLAGS_INIT contains flags that shouldn't be there

Processing control commands: > block 883986 by -1 Bug #883986 [src:openscad] openscad: FTBFS on mips/mipsel: virtual memory exhausted: Cannot allocate memory 883986 was not blocked by any bugs. 883986 was not blocking any bugs. Added blocking bug(s) of 883986: 886670 -- 883986: https://bugs.deb

Processed: Version tracking fix

Processing commands for cont...@bugs.debian.org: > fixed 866460 0.14.2+dfsg-6 Bug #866460 {Done: Andreas Tille } [src:pyfai] pyfai: depends on obsolete python-imaging (replace with python3-pil or python-pil) Marked as fixed in versions pyfai/0.14.2+dfsg-6. > thanks Stopping processing here. Plea

Bug#886662: wireguard-dkms should depend on libelf-dev

Daniel Kahn Gillmor wrote: > make: Entering directory '/usr/src/linux-headers-4.14.0-3-amd64' > /usr/src/linux-headers-4.14.0-3-common/Makefile:947: *** "Cannot generate ORC > metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel > or elfutils-libelf-devel". Stop. > Makefil

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

*Second:* I’m not willing to accept, that CPU/MMU - Microcode can be changed just by some OS/SW-Updates *without* any physical and local interventions or with *a secret „ONE WAY“* passwords/ticket *directly coming from the manufacture company*. Otherwise "very bad hackers" are able to change th

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 886629 linux-headers-4.14.0-3-amd64 Bug #886629 [virtualbox-dkms] virtualbox-dkms: missing dependency libelf-dev Bug reassigned from package 'virtualbox-dkms' to 'linux-headers-4.14.0-3-amd64'. No longer marked as found in versions virtua

Bug#886666: node-d3-shape FTBFS

Source: node-d3-shape Version: 1.2.0-2 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=node-d3-shape&arch=all&ver=1.2.0-2&stamp=1515264095&raw=0 ... debian/rules override_dh_auto_build make[1]: Entering directory '/<>' webpack --config debian/webpack.config.js \ --output-libra

Bug#886664: node-d3-timer FTBFS: test failure

Source: node-d3-timer Version: 1.0.7-3 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=node-d3-timer&arch=all&ver=1.0.7-3&stamp=1515230593&raw=0 ... not ok 11 should be in range --- operator: inRange expected: [ 440, 460 ] actual: 466 at: Test.tape.Test.inRang

Bug#866435: marked as done (ipe-tools: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Mon, 08 Jan 2018 18:05:14 + with message-id and subject line Bug#866435: fixed in ipe-tools 1:7.2.7-1 has caused the Debian Bug report #866435, regarding ipe-tools: depends on obsolete python-imaging (replace with python3-pil or python-pil) to be marked as done. This means

Bug#886663: golang-go-patricia FTBFS: cannot find package "github.com/satori/go.uuid"

Source: golang-go-patricia Version: 2.2.6-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=golang-go-patricia&arch=all&ver=2.2.6-1&stamp=1515263839&raw=0 ... dh_auto_build -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -gcflags=\"-trimpath=/<>/obj-x8

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

On Sat, 6 Jan 2018 13:32:30 +0100 Patrik Lori wrote: > > If Intel, AMD, ARM, .. now communicating, that they can change the CPU/MMU-Microcode outside there secured factories; they send (with this) very dangerous messages to all hackers. > > Hackers can use "the same procedure" to do the oposit

Bug#886662: wireguard-dkms should depend on libelf-dev

Control: tags 886662 + confirmed On Mon 2018-01-08 17:50:55 +0100, C. Dominik Bodi wrote: > Package: wireguard-dkms > Version: 0.0.20171221-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > as of today, wireguard-dkms fails to build the module for > linux-4.14.

Processed: Re: Bug#886662: wireguard-dkms should depend on libelf-dev

Processing control commands: > tags 886662 + confirmed Bug #886662 [wireguard-dkms] wireguard-dkms should depend on libelf-dev Added tag(s) confirmed. -- 886662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

How can I connect to the box ? I read on https://db.debian.org/machines.cgi it is public, but the connection fails if I naively try to login with: ~ % ssh sakharov.debian.net Permission denied (publickey). Thanks. Flavien. Le 08/12/2017 à 10:16, John Paul Adrian Glaubitz a écrit : > We have a

Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

Ah I see maybe I should email Ben Collins as stated here https://www.debian.org/ports/sparc/porting.en.html ? Le 08/12/2017 à 10:16, John Paul Adrian Glaubitz a écrit : > We have a new sparc64 porterbox called sakharov.debian.net. Feel free to test > your code there

Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/08/2018 06:13 PM, Flavien Bridault wrote: > Ah I see maybe I should email Ben Collins > as stated here > https://www.debian.org/ports/sparc/porting.en.html ? No, that information is unfortunately outdated. We ne

Processed: [bts-link] source package src:qca2

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:qca2 > # 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.debian.

Processed: [bts-link] source package ohcount

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package ohcount > # 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.debian.o

Bug#886662: wireguard-dkms should depend on libelf-dev

Package: wireguard-dkms Version: 0.0.20171221-1 Severity: grave Justification: renders package unusable Dear Maintainer, as of today, wireguard-dkms fails to build the module for linux-4.14.0-3 version 4.14.12-1 if libelf-dev is not installed. Installing libelf-dev manually fixes the problem. I s

Bug#886629: virtualbox-dkms: missing dependency libelf-dev

severity 886629 serious thanks failed for me too, bumping severity accordingly. Regards, Daniel

Processed: Re: virtualbox-dkms: missing dependency libelf-dev

Processing commands for cont...@bugs.debian.org: > severity 886629 serious Bug #886629 [virtualbox-dkms] virtualbox-dkms: missing dependency libelf-dev Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 886629: https://bugs.deb

Bug#886367: intel-microcode: coming updates for meltdown/spectre

Ah I see... thanks for the information :-) Cheers, Chris.

Processed: tagging 886382

Processing commands for cont...@bugs.debian.org: > tags 886382 + pending Bug #886382 [amd64-microcode] Coming updates for meltdown/spectre Ignoring request to alter tags of bug #886382 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: tagging 886367

Processing commands for cont...@bugs.debian.org: > tags 886367 + security Bug #886367 {Done: Henrique de Moraes Holschuh } [intel-microcode] intel-microcode: coming updates for meltdown/spectre Added tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: tagging 886382

Processing commands for cont...@bugs.debian.org: > tags 886382 + security Bug #886382 [amd64-microcode] Coming updates for meltdown/spectre Added tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. -- 886382: https://bugs.debian.org/cgi-bin/bugreport.cgi

Bug#886367: intel-microcode: coming updates for meltdown/spectre

On Mon, 08 Jan 2018, Christoph Anton Mitterer wrote: > Shouldn't that go to stable security updates as well? The current plans are for stable to wait for Intel's official microcode update pack. It is not like this set of microcode updates will get you anything without the kernel IBRS and IPBP sup

Processed: severity of 886630 is important

Processing commands for cont...@bugs.debian.org: > severity 886630 important Bug #886630 [src:linux] linux-image-3.2.0-5-amd64 Kernel panic after upgrading when use hidepid Debian wheezy Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need ass

Processed: tagging 886382

Processing commands for cont...@bugs.debian.org: > tags 886382 + pending Bug #886382 [amd64-microcode] Coming updates for meltdown/spectre Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 886382: https://bugs.debian.org/cgi-bin/bugreport.cgi?b

Bug#885965: FTBFS: Test: Run pylint on Python source code ... FAIL

control: severity -1 normal >> (unused-variable)" is not false : pylint3 found errors: >> * Module distro_info_test.test_help >> W: 30, 0: Unused variable '__class__' (unused-variable) >> W: 30, 0: Unused variable '__class__' (unused-variable) >> * Module distro_info_test.t

Processed: Re: Bug#885965: FTBFS: Test: Run pylint on Python source code ... FAIL

Processing control commands: > severity -1 normal Bug #885965 [pylint3] FTBFS: Test: Run pylint on Python source code ... FAIL Severity set to 'normal' from 'serious' -- 885965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885965 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#885295: gpodder: Depends on unmaintained pygtk

Control: severity -1 important On Mon, Jan 8, 2018 at 9:55 AM, tony mancill wrote: > Status update... The gPodder 3.10.0 packaging is ready, but as the > package is now built only for python3, it requires an new binary package > python3-mygpoclient (from the existing src:mygpoclient) which is >

Processed: Re: Bug#885295: gpodder: Depends on unmaintained pygtk

Processing control commands: > severity -1 important Bug #885295 [src:gpodder] gpodder: Depends on unmaintained pygtk Severity set to 'important' from 'serious' -- 885295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885295 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Bug#885295: gpodder: Depends on unmaintained pygtk

On Fri, Dec 29, 2017 at 10:50:17AM -0500, Jeremy Bicha wrote: > On Fri, Dec 29, 2017 at 10:46 AM, Thomas Perl wrote: > > Upstream here. > > > > gPodder 3.10.0 (just released today) should fix that. > > Thank you! Status update... The gPodder 3.10.0 packaging is ready, but as the package is now

Bug#886367: intel-microcode: coming updates for meltdown/spectre

Hey. Shouldn't that go to stable security updates as well? Cheers, Chris.

Bug#885633: [Debichem-devel] gnome-chemistry-utils: Please drop Build-Depends on rarian-compat

Hello Andreas, > I'd volunteer to fix this if you give me permission to move the package > from > SVN to Git. Sorry, but no. If you wanna go and fix this, you can easily do this by an NMU without touching the VCS. If that is not acceptable to you, I'll take care of this issue myself asap. Regard

Bug#866454: plastex: depends on obsolete python-imaging (replace with python3-pil or python-pil)

Control: tags -1 patch The attached patch does the minimum that is required to update the package. There's a lot more that could be done with this package (including a new upstream release from a few years ago) but this is a start... -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

On Sun, Jan 07, 2018 at 07:36:40PM +0100, Hans van Kranenburg wrote: > Recently a tool was added to "dump guest grant table info". You could > see if it compiles on the 4.8 source and see if it works? Would be > interesting to get some idea about how high or low these numbers are in > different sce

Processed: Re: Bug#866454: plastex: depends on obsolete python-imaging (replace with python3-pil or python-pil)

Processing control commands: > tags -1 patch Bug #866454 [src:plastex] plastex: depends on obsolete python-imaging (replace with python3-pil or python-pil) Added tag(s) patch. -- 866454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866454 Debian Bug Tracking System Contact ow...@bugs.debia

Bug#884993: marked as done (sucrose: Please don't recommend python-sugar-toolkit)

Your message dated Mon, 08 Jan 2018 12:04:32 + with message-id and subject line Bug#884993: fixed in sugar 0.112-2 has caused the Debian Bug report #884993, regarding sucrose: Please don't recommend python-sugar-toolkit to be marked as done. This means that you claim that the problem has been

Bug#867185: BTS is wrong about version graph

Control: fixed -1 3.13 Control: fixed -1 4.1 (Let's try the BTS syntax again.0 None of the 3.x series contain the changes from 4.0. This bug was fixed in the 3.x branch in 3.11. That was merged into the 4.x series in 4.1. -- Ian JacksonThese opinions are my own. If I emailed you from an

Processed: BTS is wrong about version graph

Processing control commands: > fixed -1 3.13 Bug #867185 {Done: Ian Jackson } [dgit] dgit: Perl error trying to clone Gtk+ Bug #867309 {Done: Ian Jackson } [dgit] dgit: Use of uninitialized value $got in concatenation Marked as fixed in versions dgit/3.13. Marked as fixed in versions dgit/3.13.

Bug#867185: BTS is wrong about version graph

Control: tags -1 notfound 3.13 Control: tags -1 notfound 4.1 None of the 3.x series contain the changes from 4.0. This bug was fixed in the 3.x branch in 3.11. That was merged into the 4.x series in 4.1. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net

Bug#866414: marked as done (apitrace: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Mon, 08 Jan 2018 10:24:32 + with message-id and subject line Bug#866414: fixed in apitrace 7.1+git20170623.d38a69d6+repack-3 has caused the Debian Bug report #866414, regarding apitrace: depends on obsolete python-imaging (replace with python3-pil or python-pil) to be marke

Bug#886630: linux-image-3.2.0-5-amd64 Kernel panic after upgrading when use hidepid Debian wheezy

Package: src:linux Version: 3.2.96-3 Severity: grave Justification: renders package unusable with hidepid proc mount option After updating the linux-image-amd64 system package, when we try to mount proc with the hidepid option the server throws a kernel panic. mount -o remount,hidepid=2,gid=

Processed: severity

Processing commands for cont...@bugs.debian.org: > severity 886483 grave Bug #886483 [sssd] sssd gets confused by existing config file Severity set to 'grave' from 'minor' > thanks Stopping processing here. Please contact me if you need assistance. -- 886483: https://bugs.debian.org/cgi-bin/bugr

Processed: severity of 866477 is normal

Processing commands for cont...@bugs.debian.org: > severity 866477 normal Bug #866477 [src:rst2pdf] rst2pdf: depends on obsolete python-imaging (replace with python3-pil or python-pil) Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assist

Bug#866477: python-imaging package will be dropped

On 2018-01-07 at 19:10:58 +0100, Andrej Shadura wrote: > In fact, the binary package only Suggests: python-imaging, isn't this a > normal severity bug then? You're right. I misremembered it as a build-dependency, but there isn't one. Severity changed back to normal. -- Elena ``of Valhalla''