Bug#970067: lxc-templates: bullseye: /updates -> -security

Package: lxc-templates Version: 3.0.4-3 Severity: serious File: /usr/share/lxc/templates/lxc-debian User: debian-de...@lists.debian.org Usertags: bullseye-security With the release of Debian bullseye and later, security updates are provided in the bullseye-security suite instead of

Processed: #933116 : Update ownership

Processing commands for cont...@bugs.debian.org: > owner 933116 Richard Hansen Bug #933116 [libcgi-application-plugin-viewcode-perl] libcgi-application-plugin-viewcode-perl: build-depends on pkg-components that won't be in Bullseye unless it finds a new upstream maintainer Owner changed from

Bug#969863: marked as done (rifiuti2: autopkgtest should be marked superficial)

Your message dated Thu, 10 Sep 2020 21:22:13 + with message-id and subject line Bug#969863: fixed in rifiuti2 0.7.0-2 has caused the Debian Bug report #969863, regarding rifiuti2: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has

Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 forwarded 969592 https://gitlab.com/sane-project/backends/-/issues/352 thanks Hello Sebastian, the version 1.0.31-1~experimental1 was build successful on armel and armhf.But qcam wasn't build. So I forward this bug to upstream. CU Jörg - --

Processed: Re: Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

Processing commands for cont...@bugs.debian.org: > forwarded 969592 https://gitlab.com/sane-project/backends/-/issues/352 Bug #969592 [src:sane-backends] sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 Set Bug forwarded-to-address to

Bug#969863: marked as pending in rifiuti2

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

Processing control commands: > tag -1 pending Bug #969863 [src:rifiuti2] rifiuti2: autopkgtest should be marked superficial Added tag(s) pending. -- 969863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#970051: gr-gsm: FTBFS on mips64el

Source: gr-gsm Version: 0.42.2.20200214-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) The rebuild of gr-gsm for the gnuradio transition failed to build on mips64el: | 14/19 Test #14: qa_tch_f_chans_demapper

Bug#957948: marked as done (wmmatrix: ftbfs with GCC-10)

Your message dated Thu, 10 Sep 2020 20:39:04 + with message-id and subject line Bug#957948: fixed in wmmatrix 0.2-12.1 has caused the Debian Bug report #957948, regarding wmmatrix: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#970050: haskell-gi-gtk: FTBFS: ghc: out of memory (requested 1048576 bytes)

Source: haskell-gi-gtk Version: 3.0.36-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) haskell-gi-gtk failed to build on armhf: | [472 of 504] Compiling GI.Gtk.Objects.TextTagTable ( GI/Gtk/Objects/TextTagTable.hs,

Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

Control: tags -1 - moreinfo On 2020-09-10 18:37:24 +0200, Jörg Frings-Fürst wrote: > tags 969592 +moreinfo > thanks > > Hello Sebastian, > > from the log I see > > *** qcam backend requires (ioperm, inb and outb) or portaccess functions - > disabling > > which comes through > > checking

Processed: Re: Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

Processing control commands: > tags -1 - moreinfo Bug #969592 [src:sane-backends] sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 Removed tag(s) moreinfo. -- 969592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969592 Debian Bug Tracking System Contact

Bug#961841: fontforge FTBFS on 64bit big endian: test failures

Hello! This bug blocks a couple of packages from being built on big-endian targets in Debian Ports and also causes the package to be still affected by an RC for too long. Any chance this can be fixed the next days? Apparently the necessary changes have already been merged in Salsa. Adrian --

Bug#969812: marked as done (cldump: autopkgtest should be marked superficial)

Your message dated Thu, 10 Sep 2020 19:18:34 + with message-id and subject line Bug#969812: fixed in cldump 0.11~dfsg-4 has caused the Debian Bug report #969812, regarding cldump: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has

Bug#969788: nextcloud-desktop: Upgrade removed part of configuration

On Thu, 10 Sep 2020 19:27:37 +0200 Tobias Frost wrote: > I'll see if I can find some logs… Ok, it seems so that my instance deletes its configuration itself… But I think that needs a word on my configuration: ~/Documents is synced with my Nextcloud intance I have setup XDG_DATA and XDG_CONFIG

Bug#970036: libopenmpi-dev fails to install

control: tags -1 patch On Thu, 10 Sep 2020 21:05:09 +0300 Adrian Bunk wrote: > Package: libopenmpi-dev > Version: 4.0.5-2 > Severity: grave > Tags: ftbfs > Control: affects -1 src:scotch src:starpu > > ... > Setting up libopenmpi-dev:amd64 (4.0.5-2) ... > update-alternatives: error: alternative

Processed: Re: libopenmpi-dev fails to install

Processing control commands: > tags -1 patch Bug #970036 [libopenmpi-dev] libopenmpi-dev fails to install Added tag(s) patch. -- 970036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#966653: Any progress?

Hi Thomas, On Wed, Sep 9, 2020 at 8:42 AM Thomas Goirand wrote: > On 9/8/20 5:20 PM, László Böszörményi (GCS) wrote: > > I even suspect the real bug is in GitLab itself, it > > may not (correctly) handle the new gRPC version. > > If so, can we lower the severity of the bug to important? It's

Bug#970036: libopenmpi-dev fails to install

Package: libopenmpi-dev Version: 4.0.5-2 Severity: grave Tags: ftbfs Control: affects -1 src:scotch src:starpu ... Setting up libopenmpi-dev:amd64 (4.0.5-2) ... update-alternatives: error: alternative path /usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/include doesn't exist dpkg: error processing

Processed: libopenmpi-dev fails to install

Processing control commands: > affects -1 src:scotch src:starpu Bug #970036 [libopenmpi-dev] libopenmpi-dev fails to install Added indication that 970036 affects src:scotch and src:starpu -- 970036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970036 Debian Bug Tracking System Contact

Bug#969788: nextcloud-desktop: Upgrade removed part of configuration

> > Can anyone confirm the problems of Erwan? \o I had 3 server configuration; after upgrade and reboot all those configurations were gone. I was prompted with an "first run" wizard. apt.log says I was updating nextcloud-desktop:amd64 (2.6.4-1 -> 3.0.1-1) Obersvations: - I did not instantly

Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 tags 969592 +moreinfo thanks Hello Sebastian, from the log I see *** qcam backend requires (ioperm, inb and outb) or portaccess functions - disabling which comes through checking for ioperm... no checking for i386_set_ioperm... no I don't

Processed: Re: Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

Processing commands for cont...@bugs.debian.org: > tags 969592 +moreinfo Bug #969592 [src:sane-backends] sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 969592:

Bug#962936: marked as done (sane-backends: please still keep libsane transitional package around)

Your message dated Thu, 10 Sep 2020 16:19:04 + with message-id and subject line Bug#962936: fixed in sane-backends 1.0.31-1~experimental1 has caused the Debian Bug report #962936, regarding sane-backends: please still keep libsane transitional package around to be marked as done. This means

Bug#955440: marked as done (passenger: FTBFS on armel and armhf)

Your message dated Thu, 10 Sep 2020 15:51:24 + with message-id and subject line Bug#955440: fixed in passenger 5.0.30-1.2 has caused the Debian Bug report #955440, regarding passenger: FTBFS on armel and armhf to be marked as done. This means that you claim that the problem has been dealt

Bug#954954: marked as done (libstdc++6: symbols file on armel incomplete)

: Thu, 10 Sep 2020 17:24:36 +0200 Source: gcc-10 Architecture: source Version: 10.2.0-7 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 954954 Changes: gcc-10 (10.2.0-7) unstable; urgency=medium . * Update to git 20200910 from the gcc

Bug#967033: marked as done (passenger: Unversioned Python removal in sid/bullseye)

Your message dated Thu, 10 Sep 2020 15:51:24 + with message-id and subject line Bug#967033: fixed in passenger 5.0.30-1.2 has caused the Debian Bug report #967033, regarding passenger: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#965352: libopenmpi3: breaks tests in client programs

Source: openmpi Followup-For: Bug #965352 As far as the client programs go (dolfin mpi4py petsc4py scalapack), they are all building now (with mpi4py now patched to ignore the bug). Please close this bug if we don't need to monitor the problem any more.

Bug#969852: marked as done (pompem: autopkgtest should be marked superficial)

Your message dated Thu, 10 Sep 2020 14:48:49 + with message-id and subject line Bug#969852: fixed in pompem 0.2.0-6 has caused the Debian Bug report #969852, regarding pompem: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has been

Bug#962596: ca-certificates: Removal of GeoTrust Global CA requires investigation

Happy three-month bug birthday! Any news? Thanks, Michael

Processed: Bug#969852 marked as pending in pompem

Processing control commands: > tag -1 pending Bug #969852 [src:pompem] pompem: autopkgtest should be marked superficial Added tag(s) pending. -- 969852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#969852: marked as pending in pompem

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

Bug#970029: llvm-toolchain-8: should not be part of bullseye

Le 10/09/2020 à 15:25, Sebastian Ramacher a écrit : Source: llvm-toolchain-8 Version: 1:8.0.1-10 Severity: serious Tags: sid bullseye So I think it's time to get llvm-toolchain-8 removed from testing (and from sid in the long run). Agreed, many thanks for filling this bug. It was on my todo

Bug#941685: marked as pending in libspring-java

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

Processing control commands: > tag -1 pending Bug #941685 [src:libspring-java] libspring-java: FTBFS package org.hibernate.validator.method does not exist Added tag(s) pending. -- 941685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941685 Debian Bug Tracking System Contact

Bug#970029: llvm-toolchain-8: should not be part of bullseye

Source: llvm-toolchain-8 Version: 1:8.0.1-10 Severity: serious Tags: sid bullseye $ dak rm -Rn llvm-toolchain-8 -s testin Will remove the following packages from testing: clang-8 | 1:8.0.1-10 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x clang-8-doc | 1:8.0.1-10 | all

Bug#963979: marked as done (libhibernate-validator{,4}-java: both ship /usr/share/java/hibernate-validator.jar)

Your message dated Thu, 10 Sep 2020 12:48:56 + with message-id and subject line Bug#963979: fixed in libhibernate-validator4-java 4.3.4-3 has caused the Debian Bug report #963979, regarding libhibernate-validator{,4}-java: both ship /usr/share/java/hibernate-validator.jar to be marked as

Processed: Bug#963979 marked as pending in libhibernate-validator4-java

Processing control commands: > tag -1 pending Bug #963979 [libhibernate-validator-java,libhibernate-validator4-java] libhibernate-validator{,4}-java: both ship /usr/share/java/hibernate-validator.jar Added tag(s) pending. -- 963979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963979

Bug#963979: marked as pending in libhibernate-validator4-java

Control: tag -1 pending Hello, Bug #963979 in libhibernate-validator4-java 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:

Bug#969666: marked as done (cwltool: autopkgtest regression: No module named 'arcp')

Your message dated Thu, 10 Sep 2020 12:33:36 + with message-id and subject line Bug#969666: fixed in cwltool 3.0.20200807132242-2 has caused the Debian Bug report #969666, regarding cwltool: autopkgtest regression: No module named 'arcp' to be marked as done. This means that you claim that

Bug#969638: marked as done (gwyddion: Many modules (15) failed to register.)

Your message dated Thu, 10 Sep 2020 12:33:44 + with message-id and subject line Bug#969638: fixed in gwyddion 2.56-1 has caused the Debian Bug report #969638, regarding gwyddion: Many modules (15) failed to register. to be marked as done. This means that you claim that the problem has been

Bug#969638: gwyddion: Many modules (15) failed to register.

Hi Laszlo, thanks a lot for your bug report. I've just uploaded version 2.56 of gwyddion to Debian. Please note that I'm not a user of gwyddion nor do I have the slightest idea how to use it nor what input files I could use for testing. Without having any input file it looks OK for me now and

Bug#968884: marked as done (elisa-player FTBFS: elisaqmltests (Failed))

Your message dated Thu, 10 Sep 2020 14:17:32 +0200 with message-id <4d79c0d5-c7d8-42af-b27f-cacb4ba07...@debian.org> and subject line has caused the Debian Bug report #968884, regarding elisa-player FTBFS: elisaqmltests (Failed) to be marked as done. This means that you claim that the problem

Bug#969493: src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries

Hi Paul, On Thu, Sep 10, 2020 at 12:02:10PM +0200, Paul Gevers wrote: > On 08-09-2020 22:21, Andreas Tille wrote: > >> I'm back on internet. I have just uploaded to DELAYED/15. Please let me > >> know if I should delay or cancel. > > > > Thanks a lot. There is no point in any delay for Debian

Bug#968210: statsmodels: still broken on armel

Control: severity -1 important Control: retitle -1 statsmodels: on armel may give wrong answer or crash This bug is no longer an FTBFS as the tests are now ignored on armel, but still exists. (At least as a crash; we stopped using --forked, so don't know if there are still also wrong

Bug#969493: src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries

Hi Andreas, On 08-09-2020 22:21, Andreas Tille wrote: >> I'm back on internet. I have just uploaded to DELAYED/15. Please let me >> know if I should delay or cancel. > > Thanks a lot. There is no point in any delay for Debian Med packages. Ack, but the NMU is scripted [1]. If I need to change

Bug#969804: bart: autopkgtest should be marked superficial

Hi Sudip, On Thu, Sep 10, 2020 at 10:45:07AM +0100, Sudip Mukherjee wrote: > Apologies for not mentioning it as 'serious' bug in my mass-bug mail > on debian-devel. That was my first mass-bug mail and I was wondering > what I have missed in it. :( No need to apologize. Its great that you care

Bug#969804: bart: autopkgtest should be marked superficial

HI Andreas, On Thu, Sep 10, 2020 at 8:02 AM Andreas Tille wrote: > > Hi Sudip, > > I fully agree that this is a bug and I'm currently building a fix for > this. However, I fail to see in how far this bug fulfills the criterion > for a serious bug. IMHO, important or normal is OK, but if you

Bug#969894: nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel

On 2020-09-10 13:00:10 +1000, Jiri Kanicky wrote: > This issue has been resolved with new nvidia-kernel-dkms version 450.66-1 But what about the status of nvidia-legacy-390xx-kernel-dkms? -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#969804: marked as done (bart: autopkgtest should be marked superficial)

Your message dated Thu, 10 Sep 2020 07:18:23 + with message-id and subject line Bug#969804: fixed in bart 0.6.00-2 has caused the Debian Bug report #969804, regarding bart: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has been

Processed: statsmodels: still broken on armel

Processing control commands: > severity -1 important Bug #968210 [python3-statsmodels] statsmodels: arm* test failures/crashes Severity set to 'important' from 'serious' > retitle -1 statsmodels: on armel may give wrong answer or crash Bug #968210 [python3-statsmodels] statsmodels: arm* test

Bug#969804: bart: autopkgtest should be marked superficial

Hi Sudip, I fully agree that this is a bug and I'm currently building a fix for this. However, I fail to see in how far this bug fulfills the criterion for a serious bug. IMHO, important or normal is OK, but if you think this kind of bug should be serious please discuss this on debian-devel