Bug#838994: Bug#891493: unresolved gtk2-engines-murrine situation (was: numix-gtk-theme: Undocumented and very likely also broken Breaks against murrine-themes since 2.6.7-2)

Hi Yves-Alexi, On Do 14 Nov 2019 08:03:57 CET, Yves-Alexis Perez wrote: On Wed, 2019-11-13 at 20:58 +, Mike Gabriel wrote: One last question: For the themes you maintain, is it ok if I provide the "Provides: any-murrine-theme" patches (as MRs or pushed commits) and possibly even NMU them

Bug#940127: ghostscript makes c2esp autopkgtest timeout

Quoting Didier 'OdyX' Raboud (2019-09-22 15:30:53) > Le dimanche, 22 septembre 2019, 13.25:19 h CEST Brian Potkin a écrit : > > On Sat 21 Sep 2019 at 17:39:20 +0200, Didier 'OdyX' Raboud wrote: > > > Le samedi, 21 septembre 2019, 16.24:30 h CEST Brian Potkin a écrit : > > > > > There's clearly a

Bug#944671: [Debian-med-packaging] Bug#944671: orthanc-dicomweb: missing build on armel

Dear Ivo, Please could you indicate where I can find information about how to remove the old armel build? some info is here: https://wiki.debian.org/ftpmaster_Removals Note that you can close this bug once the removal is done (otherwise this bug would prevent migration to testing).

Bug#944696: python-apt: relies on MD5 internally to download packages

I am no expert but on my opinion a temporary fix would be to bring back MD5 for the time being and then fixing/extending python-apt functions to check for more secure sums like SHA* first and then if not found fallback to MD5. But just for the backwards-compatibility since MD5 are know to be

Bug#944726: systemd undefined symbol

Control: severity -1 normal Am 14.11.19 um 13:22 schrieb Jan Sindelar: > Package: systemd > Version: 243-5 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > >* What led up to the situation? > Installing latest systemd package using apt full-upgrade in

Bug#944739: fail2ban must not email start stop actions by default

Package: fail2ban Version: 0.10.2-2.1 Severity: serious Dear Maintainer, fail2ban must not email start stop actions by default.

Processed: Re: Bug#944726: systemd undefined symbol

Processing control commands: > severity -1 normal Bug #944726 [systemd] systemd undefined symbol Severity set to 'normal' from 'critical' -- 944726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#944742: assimp: testsuite regression

Source: assimp Version: 5.0.0~ds2-1 Severity: serious Hello, looks like the autopkgtest is failing... Can you please have a look? https://ci.debian.net/packages/a/assimp/ [3 4 5] [3 5 6]]bash: line 1: 1849 Segmentation fault

Bug#944688: deal.ii ftbfs everywhere it build before during binNMU's for assimp 5.0.0

On Wed, Nov 13, 2019 at 08:32:46PM +0100, Paul Gevers wrote: >... > Looking at the reproducible-builds infra, it seems your package started to > FTBFS before this transition with the same error. Maybe this is related to the > gcc-9 change? Relevant part of the log: ... -- Found

Bug#944748: nftables: no init script

Package: nftables Version: 0.9.2-2 Followup-For: Bug #944748 This release-critical bug is also extant in sid. -- System Information: Debian Release: bullseye/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100, 'experimental')

Bug#944753: libglu FTBFS: src/libutil/error.c:60:10: error: ‘NULL’ undeclared here

Source: libglu Version: 9.0.0-2.1 Severity: serious Tags: ftbfs libglu fails to build from source: | /bin/bash ./libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"glu\" -DPACKAGE_TARNAME=\"glu\" -DPACKAGE_VERSION=\"9.0.0\" -DPACKAGE_STRING=\"glu\ 9.0.0\"

Bug#944752: libdrm FTBFS on arm* due to dh_missing exynos_fimg2d_*

Source: libdrm Version: 2.4.100-3 Severity: serious Tags: ftbfs libdrm fails to build from source on buildds: | dh_install --fail-missing | dh_install: Please use dh_missing --list-missing/--fail-missing instead | dh_install: This feature will be removed in compat 12. | dh_missing:

Bug#938691: trace-cmd: Python2 removal in sid/bullseye

On Thu, 14 Nov 2019 07:21:42 + Sudip Mukherjee wrote: > Hi All, > > On Fri, Aug 30, 2019 at 07:56:16AM +, Matthias Klose wrote: > > Package: src:trace-cmd > > Version: 2.6.1-0.1 > > Severity: normal > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2removal >

Bug#944748: nftables: no init script

Package: nftables Version: 0.9.0-2 Severity: serious Justification: Policy 9.11 I’m trying to set up a simple firewall (just filter an exposed servive so only select source IP addresses can use it) and was told that nftables should be used for new setups. While https://wiki.debian.org/nftables

Bug#944709: autopkgtests failure with OCaml 4.08.1

Package: src:diffoscope Version: 129 Severity: serious User: debian-ocaml-ma...@lists.debian.org Usertags: ocaml-4.08-transition Dear Maintainer, Diffoscope's autopkgtests fail with OCaml 4.08.1. It looks like they just need to be updated. This prevents migration of ocaml to testing. Cheers,

Bug#944668: marked as done (mupen64plus-core: FTBFS against opencv 4.1: "No OpenCV development libraries found!" during debian/rules clean)

Your message dated Thu, 14 Nov 2019 20:49:33 + with message-id and subject line Bug#944668: fixed in mupen64plus-core 2.5.9-2 has caused the Debian Bug report #944668, regarding mupen64plus-core: FTBFS against opencv 4.1: "No OpenCV development libraries found!" during debian/rules clean to

Bug#939101: marked as done (elogind: elogind 239 in bullseye FTBFS with gcc-9)

Your message dated Thu, 14 Nov 2019 21:00:23 + with message-id <20191114210022.gb3...@hindley.org.uk> and subject line Re: elogind: elogind 239 in bullseye FTBFS with gcc-9 has caused the Debian Bug report #939101, regarding elogind: elogind 239 in bullseye FTBFS with gcc-9 to be marked as

Bug#885529: marked as done (trace-cmd: Build-Depends on unmaintained pygtk)

Your message dated Thu, 14 Nov 2019 21:30:36 + with message-id <20191114213036.wha6us5eqhtm2c4r@debian> and subject line Re: trace-cmd: Build-Depends on unmaintained pygtk has caused the Debian Bug report #885529, regarding trace-cmd: Build-Depends on unmaintained pygtk to be marked as done.

Bug#938691: marked as done (trace-cmd: Python2 removal in sid/bullseye)

Your message dated Thu, 14 Nov 2019 21:33:45 + with message-id <20191114213345.wgsvbi6zbsso4asq@debian> and subject line Re: trace-cmd: Python2 removal in sid/bullseye has caused the Debian Bug report #938691, regarding trace-cmd: Python2 removal in sid/bullseye to be marked as done. This

Processed: ghostscript: CVE-2019-14869

Processing control commands: > found -1 9.26a~dfsg-0+deb9u5 Bug #944760 [src:ghostscript] ghostscript: CVE-2019-14869 Marked as found in versions ghostscript/9.26a~dfsg-0+deb9u5. > found -1 9.26a~dfsg-0+deb9u1 Bug #944760 [src:ghostscript] ghostscript: CVE-2019-14869 Marked as found in versions

Bug#944760: ghostscript: CVE-2019-14869

Source: ghostscript Version: 9.50~dfsg-2 Severity: grave Tags: security upstream Control: found -1 9.26a~dfsg-0+deb9u5 Control: found -1 9.26a~dfsg-0+deb9u1 Control: found -1 9.27~dfsg-2+deb10u2 Control: found -1 9.27~dfsg-1 Control: found -1 9.27~dfsg-3.1 Control: fixed -1 9.26a~dfsg-0+deb9u6

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

Chris Lamb wrote: > > Or, do I need to backport the patch to that specific version? > > If you mean backport it to that particular branch... then no; we just > need to do a regular backport upload. I do that after its migrated to > testing to follow the rules, so we are a few days off this

Bug#942235: dask: autopkgtest needs update for new version of pytest

Ubuntu have dask 2.6.0 and fsspec, but still have a few autopkgtest failures: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html dask itself - looks like trying to use a nonexistent temporary directory pyfftw - looks like a test treating a new (unexpected)

Bug#934843: parsedatetime: FTBFS in stretch

tag 934843 +unreproducible thanks On Thu, 15 Aug 2019 19:12:49 + Santiago Vila wrote: > I tried to build this package in stretch but it failed: Hello! This is quite strange. I've tried rebuilding it several times in my stretch sbuild, and it worked every time without error. I also

Processed: Re: parsedatetime: FTBFS in stretch

Processing commands for cont...@bugs.debian.org: > tag 934843 +unreproducible Bug #934843 [src:parsedatetime] parsedatetime: FTBFS in stretch Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 934843:

Bug#885305: marked as done (hijra: Depends on unmaintained pygtk)

Your message dated Thu, 14 Nov 2019 22:00:12 + with message-id and subject line Bug#885305: fixed in hijra 0.4.1-2 has caused the Debian Bug report #885305, regarding hijra: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#906578: [makehuman] Future Qt4 removal

On Sun, Oct 13, 2019 at 02:56:00PM -0400, Boyuan Yang wrote: > Looks like makehuman upstream is working on the Qt5 version but it hasn't > finished yet. There's only alpha versions at > https://github.com/makehumancommunity/makehuman . I guess we should move on > and have it removed if upstream

Bug#943972: marked as done (akonadi-backend-sqlite: expermental version impossible to install due to old qt dependency)

Your message dated Thu, 14 Nov 2019 23:19:38 + with message-id and subject line Bug#943972: fixed in akonadi 4:18.08.3-11 has caused the Debian Bug report #943972, regarding akonadi-backend-sqlite: expermental version impossible to install due to old qt dependency to be marked as done. This

Bug#944753: marked as done (libglu FTBFS: src/libutil/error.c:60:10: error: ‘NULL’ undeclared here)

Your message dated Fri, 15 Nov 2019 06:05:59 + with message-id and subject line Bug#944753: fixed in libglu 9.0.1-1 has caused the Debian Bug report #944753, regarding libglu FTBFS: src/libutil/error.c:60:10: error: ‘NULL’ undeclared here to be marked as done. This means that you claim that

Bug#885529: bumping severity of pygtk bugs

Hi Jeremy, On Thu, Nov 14, 2019 at 07:40:41PM -0500, Jeremy Bicha wrote: > On Wed, Nov 13, 2019 at 3:08 PM Sudip Mukherjee > wrote: > > trace-cmd/2.8.3-1 is fixing this as it now uses qt and not pygtk. But > > I am not sure if I should close this bug now or wait for you to verify > > and close

Processed: Re: python3-h5py fails to import if offline due to apparent MPI failure

Processing control commands: > severity -1 important Bug #944769 [python3-h5py] python3-h5py fails to import if offline due to apparent MPI failure Severity set to 'important' from 'serious' -- 944769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944769 Debian Bug Tracking System Contact

Bug#864012: marked as done (lepton: Upstream requires sse4.1 in Intel platform which is not available in all build machines)

Your message dated Fri, 15 Nov 2019 07:34:03 + with message-id and subject line Bug#941799: Removed package(s) from unstable has caused the Debian Bug report #864012, regarding lepton: Upstream requires sse4.1 in Intel platform which is not available in all build machines to be marked as

Bug#885302: marked as done (gtklick: Depends on unmaintained pygtk)

Your message dated Fri, 15 Nov 2019 07:35:53 + with message-id and subject line Bug#944570: Removed package(s) from unstable has caused the Debian Bug report #885302, regarding gtklick: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has been

Bug#936887: marked as done (liblarch: Python2 removal in sid/bullseye)

Your message dated Fri, 15 Nov 2019 07:34:56 + with message-id and subject line Bug#944568: Removed package(s) from unstable has caused the Debian Bug report #936887, regarding liblarch: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#936672: marked as done (gtklick: Python2 removal in sid/bullseye)

Your message dated Fri, 15 Nov 2019 07:35:53 + with message-id and subject line Bug#944570: Removed package(s) from unstable has caused the Debian Bug report #936672, regarding gtklick: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#885356: marked as done (ndisgtk: Depends on unmaintained pygtk)

Your message dated Fri, 15 Nov 2019 07:35:29 + with message-id and subject line Bug#944569: Removed package(s) from unstable has caused the Debian Bug report #885356, regarding ndisgtk: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has been

Bug#906578: marked as done ([makehuman] Future Qt4 removal)

Your message dated Fri, 15 Nov 2019 07:39:24 + with message-id and subject line Bug#944761: Removed package(s) from unstable has caused the Debian Bug report #906578, regarding [makehuman] Future Qt4 removal to be marked as done. This means that you claim that the problem has been dealt

Bug#885379: marked as done (liblarch: Depends on unmaintained pygtk)

Your message dated Fri, 15 Nov 2019 07:34:56 + with message-id and subject line Bug#944568: Removed package(s) from unstable has caused the Debian Bug report #885379, regarding liblarch: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has been

Bug#944769: python3-h5py fails to import if offline due to apparent MPI failure

Package: python3-h5py Version: 2.10.0-2 Followup-For: Bug #944769 Control: severity -1 important I don't think this issue warrants severity Serious. The failure is not triggered simply by having no network connection. It is only triggered if there is no network interface at all. The only way

Bug#943899: marked as done (Should ndisgtk be removed?)

Your message dated Fri, 15 Nov 2019 07:35:29 + with message-id and subject line Bug#944569: Removed package(s) from unstable has caused the Debian Bug report #943899, regarding Should ndisgtk be removed? to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#937123: marked as done (ndisgtk: Python2 removal in sid/bullseye)

Your message dated Fri, 15 Nov 2019 07:35:29 + with message-id and subject line Bug#944569: Removed package(s) from unstable has caused the Debian Bug report #937123, regarding ndisgtk: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#944766: design-desktop: Stop depending on volti

Package: design-desktop Version: 3.0.15 Severity: serious Tags: bullseye sid design-desktop depends on volti. Because volti is unmaintained with low popcorn and depends on pygtk and Python2, volti will likely be removed from Debian soon. Please remove the dependency so that volti can be removed

Bug#944767: python3-hijra: uninstallable

Source: hijra Version: 0.4.1-2 X-Debbugs-CC: aelmahmo...@users.sourceforge.net Severity: grave python3-hijra is uninstallable: Setting up python3-hijra (0.4.1-2) ... Sorry: TabError: inconsistent use of tabs and spaces in indentation (HijriCal.py, line 83) dpkg: error processing package

Bug#944768: gnome-shell-extension-hijra: Uninstallable

Source: hijra Version: 0.4.1-2 X-Debugs-CC: aelmahmo...@users.sourceforge.net Severity: serious gnome-shell-extension-hijra depends on gnome-shell (<< 3.31) but Debian Testing has gnome-shell 3.34. The extension looks simple enough that I think you could probably drop the upper dependency limit

Bug#944769: python3-h5py fails to import if offline due to apparent MPI failure

Package: python3-h5py Version: 2.10.0-2 Severity: serious The latest version of h5py compiled against MPI completely fails to import if there is no network connection: servo:~ 0$ python3 -c 'import h5py; print("foo")' -- No

Bug#885529: bumping severity of pygtk bugs

On Wed, Nov 13, 2019 at 3:08 PM Sudip Mukherjee wrote: > trace-cmd/2.8.3-1 is fixing this as it now uses qt and not pygtk. But > I am not sure if I should close this bug now or wait for you to verify > and close it. Yes, it was fine that you closed this bug. It looks like trace-cmd still uses

Bug#930869: Please keep pm-utils

Hi, I just stumbled on this bugreport. I'm a happy pm-utils user and would like the package to stick around. I use it on dozens of computers ranging from servers to desktops to laptops. >From reading the bugreport, there doesn't appear to be any identifiable, specific, actionable reason for

Bug#944711: Failed to set session cookie

Package: phpmyadmin Version: 4:4.9.1+dfsg1-2 Severity: grave Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, I get on login [quote] Failed to set session cookie. Maybe you are using HTTP instead of HTTPS to access phpMyAdmin. [/quote] Upstream has fix this issue:

Bug#925653: marked as done (clamfs: ftbfs with GCC-9)

Your message dated Thu, 14 Nov 2019 08:45:55 + with message-id and subject line Bug#925653: fixed in clamfs 1.1.0-1 has caused the Debian Bug report #925653, regarding clamfs: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#944681: marked as done (py-libzfs: FTBFS: libzfs.c:1:2: error: #error Do not use this file, it is the result of a failed Cython compilation.)

Your message dated Thu, 14 Nov 2019 08:49:55 + with message-id and subject line Bug#944681: fixed in py-libzfs 0.0+git20191113.2991805-1 has caused the Debian Bug report #944681, regarding py-libzfs: FTBFS: libzfs.c:1:2: error: #error Do not use this file, it is the result of a failed Cython

Bug#943867: marked as done (stressant: non-buildd binaries)

Your message dated Thu, 14 Nov 2019 08:50:17 + with message-id and subject line Bug#943867: fixed in stressant 0.5.0+nmu1 has caused the Debian Bug report #943867, regarding stressant: non-buildd binaries to be marked as done. This means that you claim that the problem has been dealt with.

Bug#944715: thunderbird ftbfs on mips64el during rebuild for libevent 2.1.7

Source: thunderbird Version: 1:68.2.2-1 Severity: serious Tags: ftbfs sid bullseye Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainers, Your package is part of the libevent transition. I binNMU'ed your package but if fails to build on mips64el. Can you please

Bug#936997: marked as done (mcomix: Python2 removal in sid/bullseye)

Your message dated Thu, 14 Nov 2019 17:00:07 +0800 with message-id and subject line close this bug has caused the Debian Bug report #936997, regarding mcomix: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#885351: marked as done (mcomix: Depends on unmaintained pygtk)

Your message dated Thu, 14 Nov 2019 16:58:47 +0800 with message-id and subject line close this bug has caused the Debian Bug report #885351, regarding mcomix: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Processed: Bug#927250 marked as pending in golang-github-getlantern-errors

Processing control commands: > tag -1 pending Bug #927250 [src:golang-github-getlantern-errors] golang-github-getlantern-errors: FTBFS in sid (missing build-depends) Added tag(s) pending. -- 927250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927250 Debian Bug Tracking System Contact

Bug#927250: marked as pending in golang-github-getlantern-errors

Control: tag -1 pending Hello, Bug #927250 in golang-github-getlantern-errors 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: tagging 944341

Processing commands for cont...@bugs.debian.org: > tags 944341 + ftbfs sid bullseye Bug #944341 [libopencv-imgcodecs-dev] libopencv-imgcodecs-dev depends on cruft package. Added tag(s) sid, bullseye, and ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: tagging 944601

Processing commands for cont...@bugs.debian.org: > tags 944601 + ftbfs sid bullseye Bug #944601 [src:ocamlviz] FTBFS with OCaml 4.08.1 (safe strings) Added tag(s) sid, ftbfs, and bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 944601:

Bug#944718: octave-dicom Build-Depends on libgdcm2-dev which isn't build from source anymore

Source: octave-dicom Version: 0.2.2-3 Severity: serious Tags: ftbfs sid bullseye -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainers, Your package Build-Depends on libgdcm2-dev, but the src:gdcm package transitioned to 3 and dropped that package. Please fix your package to use the

Bug#944714: moonshot-trust-router ftbfs during rebuilds for libevent 2.1.7

Source: moonshot-trust-router Version: 3.5.0+1 Severity: serious Tags: ftbfs sid bullseye Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Sam, Your package is part of the libevent transition. I scheduled binNMU's, but your package FTBFS on all supported archs. Paul

Bug#927250: marked as done (golang-github-getlantern-errors: FTBFS in sid (missing build-depends))

Your message dated Thu, 14 Nov 2019 09:35:17 + with message-id and subject line Bug#927250: fixed in golang-github-getlantern-errors 0.0~git20190325.abdb3e3-2 has caused the Debian Bug report #927250, regarding golang-github-getlantern-errors: FTBFS in sid (missing build-depends) to be

Bug#944719: golang-gopkg-stretchr-testify.v1: duplicate of golang-testify

Source: golang-gopkg-stretchr-testify.v1 Version: 1.3.0-2 Severity: serious Dear Maintainer, It seems to me like this package is a duplicate of the already existing golang-testify package. I assume the duplication happened because the same component has multiple import paths. I asked about

Bug#944517: openscenegraph-3.4: FTBFS in sid after latest openscenegraph

Hello Alberto, On Mon, 11 Nov 2019 12:13:11 + =?utf-8?B?QWxiZXJ0byBMdWFjZXMgRmVybsOhbmRleg==?= wrote: > Thank you for the report. > > The plan is to remove this package altogether from the archive and > replace it with openscenegraph. > > I am going to fill the bug reports for the rdeps,

Bug#944722: orthanc-webviewer Build-Depends on libgdcm2-dev which isn't build from source anymore

Source: orthanc-webviewer Version: 2.5-1 Severity: serious Tags: ftbfs sid bullseye Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainers, Your package Build-Depends on libgdcm2-dev, but the src:gdcm package transitioned to 3 and dropped that package. Please fix

Bug#944721: orthanc-dicomweb Build-Depends on libgdcm2-dev which isn't build from source anymore

Source: orthanc-dicomweb Version: 1.0+dfsg-1 Severity: serious Tags: ftbfs sid bullseye Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainers, Your package Build-Depends on libgdcm2-dev, but the src:gdcm package transitioned to 3 and dropped that package. Please

Bug#944722: marked as done (orthanc-webviewer Build-Depends on libgdcm2-dev which isn't build from source anymore)

Your message dated Thu, 14 Nov 2019 11:50:25 + with message-id and subject line Bug#944722: fixed in orthanc-webviewer 2.5-2 has caused the Debian Bug report #944722, regarding orthanc-webviewer Build-Depends on libgdcm2-dev which isn't build from source anymore to be marked as done. This

Bug#944671: [Debian-med-packaging] Bug#944671: orthanc-dicomweb: missing build on armel

Hello, Thanks for your feedback. Indeed, "node-axios" is needed to build the orthanc-dicomweb package. Please could you indicate where I can find information about how to remove the old armel build? Regards, Sébastien- On 13/11/19 16:45, Ivo De Decker wrote: package:

Bug#930869: Please keep pm-utils

On Thu, Nov 14, 2019 at 09:13:51AM +0100, Andras Korn wrote: > I just stumbled on this bugreport. > > I'm a happy pm-utils user and would like the package to stick around. I use > it on dozens of computers ranging from servers to desktops to laptops. > > From reading the bugreport, there doesn't

Processed: tagging 944697

Processing commands for cont...@bugs.debian.org: > tags 944697 + confirmed Bug #944697 [ftp.debian.org] security.debian.org: please bring back MD5Sum, at least for buster/updates Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 944697:

Bug#944697: security.debian.org: please bring back MD5Sum, at least for buster/updates

On Thu, 2019-11-14 at 01:47 +0100, Cyril Brulebois wrote: > Assuming the FTP team is responsible for security's dak setup as well, > we'd like to get MD5Sum back in buster/updates. > > python-apt relies on md5 fields internally, as documented in #944696, > and a current symptom is live-wrapper's

Bug#943474: marked as done (Doesn't build with Django 2.2)

Your message dated Thu, 14 Nov 2019 10:07:06 + with message-id and subject line Bug#943474: fixed in django-modeltranslation 0.13.3-0.1 has caused the Debian Bug report #943474, regarding Doesn't build with Django 2.2 to be marked as done. This means that you claim that the problem has been

Bug#944709: marked as done (autopkgtests failure with OCaml 4.08.1)

Your message dated Thu, 14 Nov 2019 10:49:32 + with message-id and subject line Bug#944709: fixed in diffoscope 130 has caused the Debian Bug report #944709, regarding autopkgtests failure with OCaml 4.08.1 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#944683: marked as done (FTBFS: missing file /usr/lib/nodejs/axios/dist/axios.min.js)

Your message dated Thu, 14 Nov 2019 11:20:20 + with message-id and subject line Bug#944683: fixed in orthanc-dicomweb 1.0+dfsg-2 has caused the Debian Bug report #944683, regarding FTBFS: missing file /usr/lib/nodejs/axios/dist/axios.min.js to be marked as done. This means that you claim

Bug#944721: marked as done (orthanc-dicomweb Build-Depends on libgdcm2-dev which isn't build from source anymore)

Your message dated Thu, 14 Nov 2019 11:20:20 + with message-id and subject line Bug#944721: fixed in orthanc-dicomweb 1.0+dfsg-2 has caused the Debian Bug report #944721, regarding orthanc-dicomweb Build-Depends on libgdcm2-dev which isn't build from source anymore to be marked as done.

Bug#944726: systemd undefined symbol

Package: systemd Version: 243-5 Severity: critical Justification: breaks the whole system Dear Maintainer, * What led up to the situation? Installing latest systemd package using apt full-upgrade in testing * What exactly did you do (or not do) that was effective (or ineffective)?

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

On 14/Nov - 07:45, Pirate Praveen wrote: > has protobuf 3.7 and grpc 1.19. > You need to downgrade both and use gitaly 1.59.3+dfsg-1~bpo10+2 (which > allows these versions). > > And because of

Processed: Re: Bug#944726: systemd undefined symbol

Processing control commands: > tags -1 + moreinfo Bug #944726 [systemd] systemd undefined symbol Added tag(s) moreinfo. -- 944726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#944726: systemd undefined symbol

Control: tags -1 + moreinfo Am 14.11.19 um 13:22 schrieb Jan Sindelar: > Package: systemd > Version: 243-5 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > >* What led up to the situation? > Installing latest systemd package using apt full-upgrade in

Bug#944042: Help needed to adapt python-skbio to Python3(?) / Pandas

Control: tags -1 help Control: tags -1 upstream Control: forwarded -1 https://github.com/biocore/scikit-bio/issues/1678 Hi Rebecca, thanks a lot for working on the Pandas migration. On Wed, Nov 13, 2019 at 10:19:56PM +, Rebecca N. Palmer wrote: > The ones that are blocking pandas [1] are

Processed: Help needed to adapt python-skbio to Python3(?) / Pandas

Processing control commands: > tags -1 help Bug #944042 [python3-skbio] python3-skbio: FTBFS and autopkgtest fail with pandas 0.25 Added tag(s) help. > tags -1 upstream Bug #944042 [python3-skbio] python3-skbio: FTBFS and autopkgtest fail with pandas 0.25 Added tag(s) upstream. > forwarded -1

Processed: tagging 925797

Processing commands for cont...@bugs.debian.org: > tags 925797 + ftbfs Bug #925797 [src:opensurgsim] opensurgsim: ftbfs with GCC-9 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 925797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925797

Bug#944671: [Debian-med-packaging] Bug#944671: orthanc-dicomweb: missing build on armel

Hi, On 11/14/19 12:44 PM, Sébastien Jodogne wrote: Hello, Thanks for your feedback. Indeed, "node-axios" is needed to build the orthanc-dicomweb package. Please could you indicate where I can find information about how to remove the old armel build? some info is here: