Bug#901818: marked as done (libmdc3: trying to overwrite '/usr/lib/x86_64-linux-gnu/libmdc.so.3.0.0', which is also in package libmdc2 0.15.0-1)

Your message dated Tue, 19 Jun 2018 05:04:02 + with message-id and subject line Bug#901818: fixed in xmedcon 0.15.0+dfsg-2 has caused the Debian Bug report #901818, regarding libmdc3: trying to overwrite '/usr/lib/x86_64-linux-gnu/libmdc.so.3.0.0', which is also in package libmdc2 0.15.0-1

Bug#899552: marked as done (intone: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org)

Your message dated Tue, 19 Jun 2018 04:01:58 + with message-id and subject line Bug#901560: Removed package(s) from unstable has caused the Debian Bug report #899552, regarding intone: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org to be marked as done. This means that you

Bug#899810: marked as done (xf86-video-glamo: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org)

Your message dated Tue, 19 Jun 2018 03:58:01 + with message-id and subject line Bug#901403: Removed package(s) from unstable has caused the Debian Bug report #899810, regarding xf86-video-glamo: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org to be marked as done. This

Bug#784524: marked as done ([robojournal] Qt4's WebKit removal)

Your message dated Tue, 19 Jun 2018 03:59:08 + with message-id and subject line Bug#901447: Removed package(s) from unstable has caused the Debian Bug report #784524, regarding [robojournal] Qt4's WebKit removal to be marked as done. This means that you claim that the problem has been dealt

Bug#845637: marked as done (FTBFS with xserver 1.19)

Your message dated Tue, 19 Jun 2018 03:58:01 + with message-id and subject line Bug#901403: Removed package(s) from unstable has caused the Debian Bug report #845637, regarding FTBFS with xserver 1.19 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#899608: marked as done (mdbus: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org)

Your message dated Tue, 19 Jun 2018 03:57:24 + with message-id and subject line Bug#901396: Removed package(s) from unstable has caused the Debian Bug report #899608, regarding mdbus: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org to be marked as done. This means that you

Bug#899918: marked as done (fso-specs: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org)

Your message dated Tue, 19 Jun 2018 03:54:48 + with message-id and subject line Bug#901395: Removed package(s) from unstable has caused the Debian Bug report #899918, regarding fso-specs: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org to be marked as done. This means that

Bug#899954: marked as done (libgsm0710: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org)

Your message dated Tue, 19 Jun 2018 03:56:23 + with message-id and subject line Bug#901395: Removed package(s) from unstable has caused the Debian Bug report #899954, regarding libgsm0710: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org to be marked as done. This means that

Bug#899570: marked as done (libfso-glib: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org)

Your message dated Tue, 19 Jun 2018 03:55:20 + with message-id and subject line Bug#901395: Removed package(s) from unstable has caused the Debian Bug report #899570, regarding libfso-glib: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org to be marked as done. This means

Bug#899853: marked as done (libfsoframework: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org)

Your message dated Tue, 19 Jun 2018 03:55:54 + with message-id and subject line Bug#901395: Removed package(s) from unstable has caused the Debian Bug report #899853, regarding libfsoframework: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org to be marked as done. This means

Bug#859717: marked as done (skipfish: Please migrate to openssl1.1 in Buster)

Your message dated Tue, 19 Jun 2018 03:42:41 + with message-id and subject line Bug#900848: Removed package(s) from unstable has caused the Debian Bug report #859717, regarding skipfish: Please migrate to openssl1.1 in Buster to be marked as done. This means that you claim that the problem

Bug#830193: marked as done (libuv: accesses the internet during build)

Your message dated Tue, 19 Jun 2018 03:40:08 + with message-id and subject line Bug#900432: Removed package(s) from unstable has caused the Debian Bug report #830193, regarding libuv: accesses the internet during build to be marked as done. This means that you claim that the problem has been

Bug#859228: marked as done (mod-authn-webid: Please migrate to openssl1.1 in buster)

Your message dated Tue, 19 Jun 2018 03:36:38 + with message-id and subject line Bug#900221: Removed package(s) from unstable has caused the Debian Bug report #859228, regarding mod-authn-webid: Please migrate to openssl1.1 in buster to be marked as done. This means that you claim that the

Bug#859720: marked as done (stone: Please migrate to openssl1.1 in Buster)

Your message dated Tue, 19 Jun 2018 03:36:07 + with message-id and subject line Bug#900220: Removed package(s) from unstable has caused the Debian Bug report #859720, regarding stone: Please migrate to openssl1.1 in Buster to be marked as done. This means that you claim that the problem has

Bug#858929: marked as done (ike: Please migrate to openssl1.1 in buster)

Your message dated Tue, 19 Jun 2018 03:38:38 + with message-id and subject line Bug#900380: Removed package(s) from unstable has caused the Debian Bug report #858929, regarding ike: Please migrate to openssl1.1 in buster to be marked as done. This means that you claim that the problem has

Bug#859146: marked as done (linuxdcpp: Please migrate to openssl1.1 in buster)

Your message dated Tue, 19 Jun 2018 03:38:08 + with message-id and subject line Bug#900330: Removed package(s) from unstable has caused the Debian Bug report #859146, regarding linuxdcpp: Please migrate to openssl1.1 in buster to be marked as done. This means that you claim that the problem

Bug#859556: marked as done (polygraph: Please migrate to openssl1.1 in buster)

Your message dated Tue, 19 Jun 2018 03:37:06 + with message-id and subject line Bug#900222: Removed package(s) from unstable has caused the Debian Bug report #859556, regarding polygraph: Please migrate to openssl1.1 in buster to be marked as done. This means that you claim that the problem

Bug#900176: marked as done (tripleo-heat-templates: CVE-2017-12155)

Your message dated Tue, 19 Jun 2018 03:37:36 + with message-id and subject line Bug#900281: Removed package(s) from unstable has caused the Debian Bug report #900176, regarding tripleo-heat-templates: CVE-2017-12155 to be marked as done. This means that you claim that the problem has been

Bug#882561: marked as done (pyelliptic: Please migrate to openssl1.1 in Buster)

Your message dated Tue, 19 Jun 2018 03:33:27 + with message-id and subject line Bug#900030: Removed package(s) from unstable has caused the Debian Bug report #882561, regarding pyelliptic: Please migrate to openssl1.1 in Buster to be marked as done. This means that you claim that the problem

Bug#901798: marked as done (cantata: source contains insecure mount.cifs wrapper, cantata-mounter)

Your message dated Tue, 19 Jun 2018 02:33:55 + with message-id and subject line Bug#901798: fixed in cantata 2.3.0.ds1-2 has caused the Debian Bug report #901798, regarding cantata: source contains insecure mount.cifs wrapper, cantata-mounter to be marked as done. This means that you claim

Bug#875423:

Processed: tagging 901822

Processing commands for cont...@bugs.debian.org: > tags 901822 + buster sid Bug #901822 [ocaml-flac] ocaml-flac: FTBFS: Unbound type constructor Ogg.Stream.t Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 901822:

Bug#896290: marked as done (python-ipcalc: ipcalc fails to import)

Your message dated Mon, 18 Jun 2018 21:19:09 + with message-id and subject line Bug#896290: fixed in python-ipcalc 1.99.0-3.1 has caused the Debian Bug report #896290, regarding python-ipcalc: ipcalc fails to import to be marked as done. This means that you claim that the problem has been

Bug#899965: inspircd: Invalid maintainer address pkg-irc-maintain...@lists.alioth.debian.org

Christoph Biedl wrote... > I've prepared an NMU for inspircd (versioned as 2.0.24-1.1) and > uploaded it to DELAYED/3. Please feel free to tell me if I > should delay it longer. Adrian Bunk pointed out I created a format error in debian/control. A new upload will follow as soon as I've managed

Processed: tagging 901822

Processing commands for cont...@bugs.debian.org: > tags 901822 + pending Bug #901822 [ocaml-flac] ocaml-flac: FTBFS: Unbound type constructor Ogg.Stream.t Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 901822:

Bug#893542: ntpsec-ntpviz: shares /var/log/ntpstats with ntp, which gets zapped when ntp is purged

On 06/18/2018 01:46 PM, Paride Legovini wrote: > Just a friendly ping on this, as I'd like to see ntpsec migrate to > testing. What are your plans for this patch? I've been in some communication with an ntp maintainer, but no updates as of recently. At this point, my intention is to package the

Processed: tagging 901823

Processing commands for cont...@bugs.debian.org: > tags 901823 + ftbfs Bug #901823 [src:ocaml-atd] ocaml-atd FTBFS on i386: tests failure Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 901823:

Bug#896291: marked as done (python-pgspecial: pgspecial fails to import)

Your message dated Mon, 18 Jun 2018 20:36:18 + with message-id and subject line Bug#896291: fixed in python-pgspecial 1.9.0-1.1 has caused the Debian Bug report #896291, regarding python-pgspecial: pgspecial fails to import to be marked as done. This means that you claim that the problem has

Bug#896246: marked as done (python3-pgspecial: pgspecial fails to import)

Your message dated Mon, 18 Jun 2018 20:36:18 + with message-id and subject line Bug#896246: fixed in python-pgspecial 1.9.0-1.1 has caused the Debian Bug report #896246, regarding python3-pgspecial: pgspecial fails to import to be marked as done. This means that you claim that the problem

Bug#901823: ocaml-atd FTBFS on i386: tests failure

Source: ocaml-atd Version: 1.12.0-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=ocaml-atd=i386=1.12.0-1=1527061667=0 ... dh_auto_test -a make -j4 check make[1]: Entering directory '/<>' jbuilder runtest File "atd/test/jbuild", line 6, characters 11-14: Warning:

Bug#901822: ocaml-flac: FTBFS: Unbound type constructor Ogg.Stream.t

Package: ocaml-flac Version: 0.1.1-4 Severity: serious BinNMUs of this package failed to build on almost all architectures back in May. It also fails to build for me on current sid/amd64. https://buildd.debian.org/status/package.php?p=ocaml-flac ar rcs libflac_stubs.a flac_stubs.o

Bug#831551: marked as done (soundmanager2: mtasc removal)

Your message dated Mon, 18 Jun 2018 20:17:29 + with message-id and subject line Bug#831551: fixed in soundmanager2 2.97a.20150601+dfsg2-2 has caused the Debian Bug report #831551, regarding soundmanager2: mtasc removal to be marked as done. This means that you claim that the problem has been

Bug#901784: libmypaint-1.3-0: Can't install libmypaint-1.3-0

Hi, On 18/06/18 14:35, José Couto wrote: > Sorry, I forgot to cc bugs.debian.org . > > Hi, James. Thank you for your help. [...] > I can't install libmypaint-common by hand either: > > ### > # apt-get -o Debug::pkgProblemResolver=yes install libmypaint-commo > n   > >

Processed: fixed 899152 in 3.8.0-1

Processing commands for cont...@bugs.debian.org: > fixed 899152 3.8.0-1 Bug #899152 {Done: Mohan Devarajulu } [src:openhpi] FTBFS: ipmi.h:85:2: error: unknown type name 'selector_t' Marked as fixed in versions openhpi/3.8.0-1. > thanks Stopping processing here. Please contact me if you need

Bug#901784: libmypaint-1.3-0: Can't install libmypaint-1.3-0

Hi, Sorry I accidentally sent the last email by mistake before it was finished. On 18/06/18 14:35, José Couto wrote: > Sorry, I forgot to cc bugs.debian.org . > > Hi, James. Thank you for your help. [...] > I can't install libmypaint-common by hand either: > > ### > #

Processed: Re: Bug#901798: cantata: source contains insecure mount.cifs wrapper, cantata-mounter

Processing control commands: > severity -1 grave Bug #901798 [src:cantata] cantata: source contains insecure mount.cifs wrapper, cantata-mounter Severity set to 'grave' from 'important' -- 901798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901798 Debian Bug Tracking System Contact

Bug#901769: marked as done (sphinx: crash with numbered toctrees)

Your message dated Mon, 18 Jun 2018 19:49:23 + with message-id and subject line Bug#901769: fixed in sphinx 1.7.5-3 has caused the Debian Bug report #901769, regarding sphinx: crash with numbered toctrees to be marked as done. This means that you claim that the problem has been dealt with.

Bug#901818: libmdc3: trying to overwrite '/usr/lib/x86_64-linux-gnu/libmdc.so.3.0.0', which is also in package libmdc2 0.15.0-1

Package: libmdc3 Severity: serious Version: 0.15.0+dfsg-1 Hi, trying to upgrade medcon and xmedcon fails during the installation of libmdc3 as follows: Selecting previously unselected package libmdc3. Preparing to unpack .../282-libmdc3_0.15.0+dfsg-1_amd64.deb ... Unpacking libmdc3

Bug#831551: Bug #831551 in soundmanager2 marked as pending

Control: tag -1 pending Hello, Bug #831551 in soundmanager2 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 #831551 in soundmanager2 marked as pending

Processing control commands: > tag -1 pending Bug #831551 [src:soundmanager2] soundmanager2: mtasc removal Ignoring request to alter tags of bug #831551 to the same tags previously set -- 831551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831551 Debian Bug Tracking System Contact

Bug#901562: invesalius: Segmentation fault at startup

Hi Thiago, On Sat, Jun 16, 2018 at 05:10:21PM -0300, Thiago Franco Moraes wrote: > Hi Torquil, > > I think the problem is with WXPython or VTK. Please, try to run the > code from url >

Bug#898943: marked as done (Multiple vulnerabiliities in Mongoose)

Your message dated Mon, 18 Jun 2018 19:35:01 + with message-id and subject line Bug#898943: fixed in smplayer 18.5.0~ds1-1 has caused the Debian Bug report #898943, regarding Multiple vulnerabiliities in Mongoose to be marked as done. This means that you claim that the problem has been dealt

Bug#849308:

dkg and I had a discussion about this recently and he asked me to summarize my understanding of it. - WireGuard still prefers to operate on a rolling basis, with new snapshots totally replacing old ones, with no stability, security, or other long term guarantees. - WireGuard probably won't be

Bug#893542: ntpsec-ntpviz: shares /var/log/ntpstats with ntp, which gets zapped when ntp is purged

On Fri, 30 Mar 2018 Richard Laager wrote: > If this coordination is acceptable, I believe it solves the various > interactions. I'm happy to test more scenarios if anyone thinks I missed > something. Hello Richard, Just a friendly ping on this, as I'd like to see ntpsec migrate to testing. What

Processed: Re: making wireguard work on RHEL7/etc.

Processing control commands: > retitle 894909 wireguard-dkms should build on jessie Bug #894909 [wireguard-dkms] wireguard-dkms: dev_recursion_level definition problem Changed Bug title to 'wireguard-dkms should build on jessie' from 'wireguard-dkms: dev_recursion_level definition problem'. >

Bug#894909: making wireguard work on RHEL7/etc.

Control: retitle 894909 wireguard-dkms should build on jessie Control: severity 894909 wishlist I'm retitling https://bugs.debian.org/894909 to clarify that it's only a problem on jessie (currently, oldstable), and to mark it as wishlist -- we're currently only really supporting wireguard in

Bug#891395: closed by Roland Fehrenbacher (Bug#891395: fixed in libfabric 1.6.1-1)

On Mon, Jun 18, 2018 at 06:10:04PM +0200, Roland Fehrenbacher wrote: > > "HG" == Helmut Grohne writes: > HG> You moved the programs and the corresponding manual pages, but > HG> the development manual pages still live in libfabric1 and are > HG> still problematic for the very same

Bug#896772: marked as done (pypolicyd-spf: missing build dependency on python3-distutils)

Your message dated Mon, 18 Jun 2018 14:10:55 -0400 with message-id <2264858.9cFXaouNit@kitterma-e6430> and subject line Closing due to source removed has caused the Debian Bug report #896772, regarding pypolicyd-spf: missing build dependency on python3-distutils to be marked as done. This means

Bug#899060: FTBFS: even if tests pass, dh_auto_test fails

On Sun, Jun 17, 2018 at 11:47:17PM -0700, Jameson Graef Rollins wrote: > I am unclear how to test this right now as I don't have direct access to > an armhf system. It builds fine on the systems I have access to. > > Given that it seems to build fine on other systems, I'm tempted to solve > this

Bug#898953: med-fichier: FTBFS on armhf i386: FAIL: filterBlockOfentities.sh *** stack smashing detected ***

On Mon, Jun 18, 2018 at 07:33:50PM +0300, Adrian Bunk wrote: > Whatever caused this seems to be fixed now: > https://tests.reproducible-builds.org/debian/history/med-fichier.html > https://buildd.debian.org/status/package.php?p=med-fichier Confirmed: works fine on my test rig as well. --

Bug#900596: [chromium-browser] unicode non free license

Hi, On Fri, 01 Jun 2018 21:56:51 +0200 "Bastien =?ISO-8859-1?Q?ROUCARI=C8S?=" wrote: > Package: chromium-browser > Severity: serious > version: 67.0.3396.62-1 > > The following file are non free: > third_party/breakpad/breakpad/src/common/convert_UTF.c >

Bug#900232: collectd: FTBFS: sed: can't read /usr/lib/pkgconfig/OpenIPMIpthread.pc: No such file or directory

Control: tag -1 + patch On Sun, 27 May 2018 22:09:07 +0300, Niko Tyni wrote: > It probably broke with > > openipmi (2.0.25-1) unstable; urgency=medium > > [...] > * move pkg-config files to a multiarch location. Thanks Helmut > closes: Bug#852739 > [...] > > -- Noël Köthe Fri, 18

Processed: Re: Bug#900232: collectd: FTBFS: sed: can't read /usr/lib/pkgconfig/OpenIPMIpthread.pc: No such file or directory

Processing control commands: > tag -1 + patch Bug #900232 [src:collectd] collectd: FTBFS: sed: can't read /usr/lib/pkgconfig/OpenIPMIpthread.pc: No such file or directory Added tag(s) patch. -- 900232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900232 Debian Bug Tracking System Contact

Processed: [bts-link] source package src:haskell-derive

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:haskell-derive > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Processed: affects 901769

Processing commands for cont...@bugs.debian.org: > affects 901769 src:buildbot Bug #901769 [src:sphinx] sphinx: crash with numbered toctrees Added indication that 901769 affects src:buildbot > thanks Stopping processing here. Please contact me if you need assistance. -- 901769:

Bug#891395: closed by Roland Fehrenbacher (Bug#891395: fixed in libfabric 1.6.1-1)

> "HG" == Helmut Grohne writes: Hi Helmut, HG> Control: reopen -1 On Thu, May 31, 2018 at 09:03:09AM +, HG> Debian Bug Tracking System wrote: >> * Add package libfabric-bin (Closes: #891395) please close the bug again. HG> You moved the programs and the corresponding

Bug#901808: debootstrap: --merged-usr is silently ignored on "blacklisted" suites like stretch

Package: debootstrap Version: 1.0.102 Severity: serious Justification: https://lists.debian.org/debian-boot/2018/06/msg00238.html See the conversation around/following [1] for more context. [1]: https://lists.debian.org/debian-boot/2018/06/msg00175.html The TLDR is that the previous version of

Bug#901807: libmath-gsl-perl: incompatible with GSL >= 2.5

Source: libmath-gsl-perl Version: 0.39-1 Severity: serious Tags: upstream buster sid Justification: fails to build from source (but built successfully in the past) Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=123306 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As first seen on

Bug#900622: marked as done (missing dependency on cl-ppcre)

Your message dated Mon, 18 Jun 2018 14:17:37 + with message-id and subject line Bug#900622: fixed in cl-unicode 20180328-2 has caused the Debian Bug report #900622, regarding missing dependency on cl-ppcre to be marked as done. This means that you claim that the problem has been dealt with.

Processed: tagging 900282, tagging 901601

Processing commands for cont...@bugs.debian.org: > tags 900282 + sid buster Bug #900282 {Done: Alberto Garcia } [webkitgtk] webkitgtk FTBFS with new ICU Added tag(s) buster and sid. > tags 901601 + sid buster Bug #901601 [python3.6-venv] python3-venv: Please remove python3-venv from archive Bug

Processed: Re: Bug#901797: python3.6-venv: can't create virtualenv due to ensurepip failing

Processing commands for cont...@bugs.debian.org: > reassign 901601 python3.6-venv Bug #901601 [python3-venv] python3-venv: Please remove python3-venv from archive Bug reassigned from package 'python3-venv' to 'python3.6-venv'. No longer marked as found in versions python3-defaults/3.6.5-3 and

Bug#901784: libmypaint-1.3-0: Can't install libmypaint-1.3-0

Sorry, I forgot to cc bugs.debian.org. Hi, James. Thank you for your help. This is the output of apt-get: ### # apt-get -o Debug::pkgProblemResolver=yes install libmypaint-1.3-0 Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver

Bug#901800: python-gevent: (Build-)Depends on cruft packages python-greenlet-dbg python3-greenlet-dbg

Source: python-gevent Version: 1.2.2-2 Severity: serious Hi, * source package python-greenlet version 0.4.13-1 no longer builds binary package(s): python-greenlet-dbg python3-greenlet-dbg - broken Depends: python-gevent: python-gevent-dbg python3-gevent-dbg - broken

Bug#901778: gnome-shell: blank screen after "OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW" on VirtualBox

Control: retitle -1 gnome-shell: blank screen after "OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW" on VirtualBox Control: severity -1 important On Mon, 18 Jun 2018 at 10:41:33 +0100, Saman Ghannadzadeh wrote: > Upon login, gnome-shell crashes with the following

Processed: Re: Bug#901778: gnome-shell: blank screen after "OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW" on VirtualBox

Processing control commands: > retitle -1 gnome-shell: blank screen after "OpenGL Warning: vboxCall failed > with VBox status code VERR_BUFFER_OVERFLOW" on VirtualBox Bug #901778 [gnome-shell] gnome-shell crashes with "g_array_unref: assertion 'array' failed" Changed Bug title to 'gnome-shell:

Bug#901105: marked as done (ciftilib: FTBFS when built with dpkg-buildpackage -A)

Your message dated Mon, 18 Jun 2018 13:19:02 + with message-id and subject line Bug#901105: fixed in ciftilib 1.5.1-2 has caused the Debian Bug report #901105, regarding ciftilib: FTBFS when built with dpkg-buildpackage -A to be marked as done. This means that you claim that the problem has

Processed: reassign 901698 to libudev-dev, cloning 901136, reassign 901136 to sreview-common ..., reopening -1

Processing commands for cont...@bugs.debian.org: > reassign 901698 libudev-dev 232-25+deb9u2 Bug #901698 [libudev] libudev-dev fails to install Warning: Unknown package 'libudev' Bug reassigned from package 'libudev' to 'libudev-dev'. No longer marked as found in versions 232-25+deb9u2. Ignoring

Bug#901797: python3.6-venv: can't create virtualenv due to ensurepip failing

Package: python3.6-venv Version: 3.6.6~rc1-1 Severity: grave Justification: renders package unusable Dear Maintainer, This version of pyvenv can't create a working virtual env. The failing command is an ensurepip invocation. The error message also tells me to install python3-venv, but that

Processed: severity of 899838 is normal, retitle 897141 to RM: abstract-rendering -- RoM; no longer used

Processing commands for cont...@bugs.debian.org: > severity 899838 normal Bug #899838 [ftp.debian.org] RM: gst-fluendo-mp3: ROM; Obsolete - superseded by mpg123 in gstreamer1.0-plugins-good Severity set to 'normal' from 'serious' > retitle 897141 RM: abstract-rendering -- RoM; no longer used Bug

Bug#898108: marked as done (libgtp-dev is now built by the osmo-ggsn source)

Your message dated Mon, 18 Jun 2018 12:49:43 + with message-id and subject line Bug#898845: Removed package(s) from unstable has caused the Debian Bug report #898108, regarding libgtp-dev is now built by the osmo-ggsn source to be marked as done. This means that you claim that the problem

Bug#867946: marked as done (libsocialweb: Build-Depends on deprecated libgnome-keyring-dev)

Your message dated Mon, 18 Jun 2018 12:52:54 + with message-id and subject line Bug#899177: Removed package(s) from unstable has caused the Debian Bug report #867946, regarding libsocialweb: Build-Depends on deprecated libgnome-keyring-dev to be marked as done. This means that you claim that

Bug#862766: marked as done (Port from libnm-glib to libnm (or GNetworkMonitor))

Your message dated Mon, 18 Jun 2018 12:52:54 + with message-id and subject line Bug#899177: Removed package(s) from unstable has caused the Debian Bug report #862766, regarding Port from libnm-glib to libnm (or GNetworkMonitor) to be marked as done. This means that you claim that the problem

Bug#875982: marked as done (RM: obsolete with current Perl?)

Your message dated Mon, 18 Jun 2018 12:51:27 + with message-id and subject line Bug#898987: Removed package(s) from unstable has caused the Debian Bug report #875982, regarding RM: obsolete with current Perl? to be marked as done. This means that you claim that the problem has been dealt

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

Your message dated Mon, 18 Jun 2018 12:45:37 + with message-id and subject line Bug#898594: Removed package(s) from unstable has caused the Debian Bug report #866499, regarding xmms2tray: depends on obsolete python-imaging (replace with python3-pil or python-pil) to be marked as done. This

Bug#868414: marked as done (gnome-alsamixer: Please drop the (build-)dependency against gnome-vfs)

Your message dated Mon, 18 Jun 2018 12:43:47 + with message-id and subject line Bug#898584: Removed package(s) from unstable has caused the Debian Bug report #868414, regarding gnome-alsamixer: Please drop the (build-)dependency against gnome-vfs to be marked as done. This means that you

Bug#885743: marked as done (maximus: Depends on libgnomeui)

Your message dated Mon, 18 Jun 2018 12:44:15 + with message-id and subject line Bug#898585: Removed package(s) from unstable has caused the Debian Bug report #885743, regarding maximus: Depends on libgnomeui to be marked as done. This means that you claim that the problem has been dealt

Bug#899773: marked as done (exo: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

Your message dated Mon, 18 Jun 2018 12:33:59 + with message-id and subject line Bug#899773: fixed in exo 0.12.1-1 has caused the Debian Bug report #899773, regarding exo: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org to be marked as done. This means that you claim that

Bug#901769: Bug #901769 in sphinx marked as pending

Control: tag -1 pending Hello, Bug #901769 in sphinx 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 #901769 in sphinx marked as pending

Processing control commands: > tag -1 pending Bug #901769 [src:sphinx] sphinx: crash with numbered toctrees Added tag(s) pending. -- 901769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#880276: marked as done (test using GCM with IV option fails after fix for CVE-2016-7798)

Your message dated Mon, 18 Jun 2018 12:19:21 + with message-id and subject line Bug#880276: fixed in ruby-encryptor 3.0.0-2 has caused the Debian Bug report #880276, regarding test using GCM with IV option fails after fix for CVE-2016-7798 to be marked as done. This means that you claim that

Bug#901784: libmypaint-1.3-0: Can't install libmypaint-1.3-0

Hi, On 18/06/18 12:19, Coque Couto wrote: > Package: libmypaint-1.3-0 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > libmypaint-1.3-0 package seems to be broken. Trying to install gimp > reports the following error: [...] > It seems that libmypaint-common

Bug#901601: python3-venv: Please remove python3-venv from archive

I think this is a more recent regression than that bug report, which was filed against python3-venv-3.5.1-2. The package python3-venv 3.6.4-1 works fine, but not python3-venv-3.6.5-3. Best wishes, Kai On Fri, 15 Jun 2018 13:00:39 +0200 Salvo Tomaselli wrote: > Package: python3-venv > Version:

Bug#895990: gdm3: memory leak (known upstream)

On Wed, 18 Apr 2018 at 13:23:51 +0200, Dennis Grunert wrote: > the gdm3 process has a memory leak It's a lot more complicated than that, unfortunately. You're reporting the symptom, but the cause involves gjs and gnome-shell, and the solutions are also spread between packages. > This bug is

Bug#901547: seabios: Source tarball ships compiled binaries

On 15 June 2018 at 14:43, Chris Lamb wrote: > Michael Tokarev wrote: > >> We ensure the pre-built files are not used during build, and the source >> of them is included, so we comply to DFSG. > > Indeed, I don't see a DFSG violation here.. Vivia? OK then, seems I had misunderstood the DFSG.

Bug#901462: seabios: SeaBIOS fails to build from source on sid and testing

>From this error message: build/src/fw/ssdt-misc.dsl.i 4: DefinitionBlock ("ssdt-misc.aml", "SSDT", 0x01, "BXPC", "BXSSDTSUSP", 0x1) Error6155 - Invalid OEM Table ID ^ (Length cannot exceed 8 characters) Examining the shipped .hex files, I noticed that the TableID string is

Bug#901784: libmypaint-1.3-0: Can't install libmypaint-1.3-0

Package: libmypaint-1.3-0 Severity: grave Justification: renders package unusable Dear Maintainer, libmypaint-1.3-0 package seems to be broken. Trying to install gimp reports the following error: ### # apt install gimp Reading package lists... Done Building dependency tree Reading state

Bug#888095: [debian-mysql] Bug#888095: Bug#888095:

On Monday 18 June 2018 04:09 AM, Otto Kekäläinen wrote: > If you want to help, please make a pull request on Salsa or even at > upstream. I would prefer nobody forces a substandard version of > MariaDB 10.3 into Debian because the cost of fixing it afterwards > becomes so high. > I think you are

Bug#901780: linkchecker: Should depend on python-xdg

Package: linkchecker Version: 9.4.0-1 Severity: serious Justification: Policy 7.2 Dear Maintainer, This is what happens if python-xdg isn't installed: Traceback (most recent call last): File "/usr/bin/linkchecker", line 36, in from linkcheck.cmdline import print_version, print_usage,

Bug#901112: marked as done (openvswitch: FTBFS when built with dpkg-buildpackage -A)

Your message dated Mon, 18 Jun 2018 09:49:59 + with message-id and subject line Bug#901112: fixed in openvswitch 2.8.1+dfsg1-7 has caused the Debian Bug report #901112, regarding openvswitch: FTBFS when built with dpkg-buildpackage -A to be marked as done. This means that you claim that the

Bug#901778: gnome-shell crashes with "g_array_unref: assertion 'array' failed"

Package: gnome-shell Version: 3.28.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, Upon login, gnome-shell crashes with the following errors: Jun 18 10:22:27 debian gnome-shell[789]: g_array_unref: assertion 'array' failed Jun 18 10:22:27 debian gnome-shell[789]:

Bug#901112: Bug #901112 in openvswitch marked as pending

Control: tag -1 pending Hello, Bug #901112 in openvswitch 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 #901112 in openvswitch marked as pending

Processing control commands: > tag -1 pending Bug #901112 [src:openvswitch] openvswitch: FTBFS when built with dpkg-buildpackage -A Added tag(s) pending. -- 901112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: sphinx: crash with numbered toctrees

Processing control commands: > severity -1 serious Bug #901769 [src:sphinx] sphinx: crash with numbered toctrees Severity set to 'serious' from 'important' -- 901769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#901634: marked as done (libmdc2: soname changed but package name was not changed)

Your message dated Mon, 18 Jun 2018 08:02:38 + with message-id and subject line Bug#901634: fixed in xmedcon 0.15.0+dfsg-1 has caused the Debian Bug report #901634, regarding libmdc2: soname changed but package name was not changed to be marked as done. This means that you claim that the

Bug#888095: [debian-mysql] Bug#888095: Bug#888095: Bug#888095:

On Mon, Jun 18, 2018 at 12:39 AM, Otto Kekäläinen wrote: > su 17. kesäk. 2018 klo 10.27 Pirate Praveen (prav...@debian.org) kirjoitti: >> >> On Thu, 14 Jun 2018 15:57:18 +0800 Andy Li wrote: >> > I'm sure you have been busy, but this issue has been there unfixed for >> > several months. >> > I

Bug#895990: gdm3: memory leak (known upstream)

This patch to this bug is now committed upstream and can be backported by the Debian team: https://gitlab.gnome.org/GNOME/gjs/merge_requests/122 -- Dipl.-Math. Dennis Grunert Institute of Engineering and Computational Mechanics (name in German: Institut für Technische und Numerische Mechanik)

Bug#901128: marked as done (primesieve: please bump library package name to libprimesieve9)

Your message dated Mon, 18 Jun 2018 07:00:34 + with message-id and subject line Bug#901128: fixed in primesieve 7.0+ds-3 has caused the Debian Bug report #901128, regarding primesieve: please bump library package name to libprimesieve9 to be marked as done. This means that you claim that the

Bug#899060: FTBFS: even if tests pass, dh_auto_test fails

I am unclear how to test this right now as I don't have direct access to an armhf system. It builds fine on the systems I have access to. Given that it seems to build fine on other systems, I'm tempted to solve this problem in the short term by just excluding armhf. If anyone thinks that's a

Bug#901760: r-cran-spatstat: FTBFS Unmatched ( in regex; marked by <-- HERE in m/^RandomFieldsUtils(

Source: r-cran-spatstat Version: 1.56-0-1 Severity: serious Tags: ftbfs Hi R Package Team r-cran-spatstat FTBFS everywhere on the buildds, except on armel and mipsel [1], with the following error: ** testing if installed package can be loaded * DONE (spatstat) Unmatched ( in regex; marked by

Bug#901491: Bug #901491 in acbuild marked as pending

Control: tag -1 pending Hello, Bug #901491 in acbuild 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:

  1   2   >