Bug#969552: marked as done (phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: �)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Sep 2020 06:48:27 + with message-id and subject line Bug#969552: fixed in phipack 0.0.20160614-5 has caused the Debian Bug report #969552, regarding phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: � to be marked as done. This means that you cl

Bug#966653: Any progress?

2020-09-08 Thread Thomas Goirand
Hi Laszlo, Thanks for your prompt reply. On 9/8/20 5:20 PM, László Böszörményi (GCS) wrote: > Hi Thomas, > > On Tue, Sep 8, 2020 at 1:27 PM Thomas Goirand wrote: >> I'm not seeing any progress on this bug. Is anyone working on this? > The bug report is too wide, "GitLab can't start" doesn't he

Bug#969552: [Help] Re: Bug#969552: phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: �

2020-09-08 Thread Andreas Tille
Control: tags -1 pending Hi Lennart, On Tue, Sep 08, 2020 at 07:23:15PM -0400, Lennart Sorensen wrote: > > I don't have access to an arm64 system at the moment, but a good start > > might be to fix the compiler warnings, such as the array subscript out > > of bounds in global.c line 44. The rest

Bug#969909: marked as done (xmoto-data: Broken links to DejaVu fonts)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Sep 2020 06:33:29 + with message-id and subject line Bug#969909: fixed in xmoto 0.6.1+repack-3 has caused the Debian Bug report #969909, regarding xmoto-data: Broken links to DejaVu fonts to be marked as done. This means that you claim that the problem has been deal

Processed: Re: [Help] Re: Bug#969552: phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: �

2020-09-08 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #969552 [src:phipack] phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: � Added tag(s) pending. -- 969552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969552 Debian Bug Tracking System Contact ow...@bugs.debian.org wit

Bug#969938: debirf: bullseye: switch from /updates to -security

2020-09-08 Thread Paul Wise
Package: debirf Severity: serious File: /usr/share/debirf/modules/a0_add_security_repos User: debian-de...@lists.debian.org Usertags: bullseye-security The above script references /updates instead of -security for the bullseye release and later. This means that images generated for bullseye will b

Bug#969936: bullseye: add support, switch from /updates to -security

2020-09-08 Thread Paul Wise
Package: debian-lan-config Version: 0.26 Severity: serious File: /usr/share/debian-lan-config/fai/config/scripts/LAST/50-misc User: debian-de...@lists.debian.org Usertags: bullseye-security The above script references $release/updates but when bullseye is released that should be replaced by $relea

Processed: bug 969926 is forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=20338

2020-09-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 969926 https://sourceware.org/bugzilla/show_bug.cgi?id=20338 Bug #969926 [src:glibc] glibc: Parsing of /etc/gshadow can return bad pointers causing segfaults in applications Set Bug forwarded-to-address to 'https://sourceware.org/bugzi

Bug#962651: marked as done (rst2pdf depends and build depends on python3-pdfrw that might not be in bullseye)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Sep 2020 03:19:10 + with message-id and subject line Bug#962651: fixed in rst2pdf 0.98-1 has caused the Debian Bug report #962651, regarding rst2pdf depends and build depends on python3-pdfrw that might not be in bullseye to be marked as done. This means that you c

Bug#969930: calamares-settings-debian: switch security.d.o apt sources entry from bullseye/updates to bullseye-security

2020-09-08 Thread Paul Wise
Package: calamares-settings-debian Severity: serious Please switch the security.d.o apt sources entry from bullseye/updates to bullseye-security otherwise folks who install bullseye from the bullseye live images using the Calamares installer will not get any security updates after the bullseye rel

Bug#962651: marked as pending in pdfposter

2020-09-08 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #962651 in pdfposter 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: https://salsa.debian.org/python-team/applications/rst2pdf/-/commit/2155cf3f77e28e

Processed: Bug#962651 marked as pending in pdfposter

2020-09-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #962651 [rst2pdf] rst2pdf depends and build depends on python3-pdfrw that might not be in bullseye Added tag(s) pending. -- 962651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962651 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#969815: marked as done (comprez: autopkgtest should be marked superficial)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Sep 2020 02:33:47 + with message-id and subject line Bug#969815: fixed in comprez 2.7.3-2 has caused the Debian Bug report #969815, regarding comprez: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has been

Bug#968689: marked as done (python3-commonmark: file conflict with cmark, php-league-commonmark)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Sep 2020 02:33:34 + with message-id and subject line Bug#968689: fixed in commonmark 0.9.1-3 has caused the Debian Bug report #968689, regarding python3-commonmark: file conflict with cmark, php-league-commonmark to be marked as done. This means that you claim that

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

2020-09-08 Thread Jiri Kanicky
$ dpkg-reconfigure nvidia-kernel-dkms Does not seem to build the modules for 5.8.0-1. Building initial module for 5.8.0-1-amd64 Error! Bad return status for module build on kernel: 5.8.0-1-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/440.82/build/make.log for more information. make.lo

Bug#969926: glibc: Parsing of /etc/gshadow can return bad pointers causing segfaults in applications

2020-09-08 Thread Bernd Zeimetz
Source: glibc Version: 2.28-10 Severity: serious Tags: security upstream patch X-Debbugs-Cc: Debian Security Team Hi, we are running into the bug https://sourceware.org/bugzilla/show_bug.cgi?id=20338 causing systemd-sysusers to segfault. Patch is available in the linked bug report. As it was f

Bug#968913: marked as done (perl-base: IO::Socket::IP: AI_ADDRCONFIG breaks many test suites on IPv6-only hosts)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Sep 2020 00:04:20 + with message-id and subject line Bug#968913: fixed in perl 5.32.0-3 has caused the Debian Bug report #968913, regarding perl-base: IO::Socket::IP: AI_ADDRCONFIG breaks many test suites on IPv6-only hosts to be marked as done. This means that you

Bug#969552: [Help] Re: Bug#969552: phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: �

2020-09-08 Thread Lennart Sorensen
On Tue, Sep 08, 2020 at 05:35:45PM -0400, Lennart Sorensen wrote: > On Tue, Sep 08, 2020 at 10:35:26PM +0200, Andreas Tille wrote: > > Control: tags -1 help > > > > Hi Debian Arm team, > > > > I admit I have no idea how to deal with this except by excluding > > arm64 from the list of supported ar

Bug#966433: marked as done (seqan autopkg test failures triggered by gcc-defaults)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 23:19:00 + with message-id and subject line Bug#966433: fixed in seqan3 3.0.2~rc1+bf04354+ds-1 has caused the Debian Bug report #966433, regarding seqan autopkg test failures triggered by gcc-defaults to be marked as done. This means that you claim that the

Bug#966270: marked as done (seqan3 FTBFS with gcc 10)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 23:19:00 + with message-id and subject line Bug#966270: fixed in seqan3 3.0.2~rc1+bf04354+ds-1 has caused the Debian Bug report #966270, regarding seqan3 FTBFS with gcc 10 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#969552: [Help] Re: Bug#969552: phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: �

2020-09-08 Thread Lennart Sorensen
On Tue, Sep 08, 2020 at 10:35:26PM +0200, Andreas Tille wrote: > Control: tags -1 help > > Hi Debian Arm team, > > I admit I have no idea how to deal with this except by excluding > arm64 from the list of supported architectures which is definitely > not my prefered way of action. > > Any help w

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

2020-09-08 Thread Marek Straka
Does thunarx-python depends on Python2 ? See dependencies on https://git.xfce.org/bindings/thunarx-python/about/ - Thunar (1.7.0 or later) - pygobject (3.20.0 or later) - gtk+3 (3.20.0 or later)

Bug#957468: libpsm2: ftbfs with GCC-10

2020-09-08 Thread Brian Smith
I have uploaded libpsm 11.2.185-1, which addresses this bug. As requested, I'm leaving Bug #957468 open. -- Brian T. Smith System Fabric Works Senior Principal Engineer bsm...@systemfabricworks.com GPG Key: 0xB3C2C7B73BA3CD7F

Bug#969797: marked as done (altermime: autopkgtest should be marked superficial)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 21:03:26 + with message-id and subject line Bug#969797: fixed in altermime 0.3.10-12 has caused the Debian Bug report #969797, regarding altermime: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has

Bug#969364: marked as done (ignition-math: FTBFS in sid)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 21:03:39 + with message-id and subject line Bug#969364: fixed in ignition-math 6.4.0+ds-10 has caused the Debian Bug report #969364, regarding ignition-math: FTBFS in sid to be marked as done. This means that you claim that the problem has been dealt with.

Bug#969552: [Help] Re: Bug#969552: phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: �

2020-09-08 Thread Andreas Tille
Control: tags -1 help Hi Debian Arm team, I admit I have no idea how to deal with this except by excluding arm64 from the list of supported architectures which is definitely not my prefered way of action. Any help would be really appreciated. Kind regards Andreas. On Fri, Sep 04, 2020 at

Processed: [Help] Re: Bug#969552: phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: �

2020-09-08 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #969552 [src:phipack] phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: � Added tag(s) help. -- 969552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969552 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#969609: [Pkg-rust-maintainers] Bug#969609: rust-zstd: unbuildable, uninstallable, depends on non-existent rust-zstd-safe

2020-09-08 Thread Ximin Luo
Steve, You keep filing these same bugs. I have told you this many times before already: this is just how rust packaging works, Britney's migration policy already prevents these packages from reaching Debian Testing, so there is no problem, no users are affected. You filing these bug reports ac

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

2020-09-08 Thread Andreas Tille
Hi Paul, On Mon, Sep 07, 2020 at 08:13:54PM +0200, Paul Gevers wrote: > Control: tags -1 pending > > On 03-09-2020 20:46, Paul Gevers wrote: > > Your package is only blocked because the arch:all binary package(s) > > aren't built on a buildd. Unfortunately the Debian infrastructure > > doesn't al

Bug#969917: trimage: Trimage crashes with 10 or more png images

2020-09-08 Thread Daniel
Package: trimage Version: 1.0.6-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: antonucci.d...@gmail.com Dear Maintainer, if you try to compress 10 or more images Trimage crashes with this output: File "/usr/lib/python3/dist-packages/trimage/trimage.py", line 286, in dat

Bug#957948: wmmatrix: diff for NMU version 0.2-12.1

2020-09-08 Thread Sudip Mukherjee
Control: tags 957948 + patch Control: tags 957948 + pending -- Dear maintainer, I've prepared an NMU for wmmatrix (versioned as 0.2-12.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -u wmmatrix-0.2/debian/changelog wmmatrix-0.2/debian/c

Processed: wmmatrix: diff for NMU version 0.2-12.1

2020-09-08 Thread Debian Bug Tracking System
Processing control commands: > tags 957948 + patch Bug #957948 [src:wmmatrix] wmmatrix: ftbfs with GCC-10 Added tag(s) patch. > tags 957948 + pending Bug #957948 [src:wmmatrix] wmmatrix: ftbfs with GCC-10 Added tag(s) pending. -- 957948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957948 D

Bug#957920: marked as done (vpcs: ftbfs with GCC-10)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 19:50:09 + with message-id and subject line Bug#957920: fixed in vpcs 0.5b2-2.2 has caused the Debian Bug report #957920, regarding vpcs: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#966982: Uploading disabling that test to DELAYED/2

2020-09-08 Thread Håvard Flaget Aasen
tir. 8. sep. 2020 kl. 14:29 skrev Thomas Goirand : > > On 9/8/20 2:01 PM, Håvard Flaget Aasen wrote: > > On Tue, 8 Sep 2020 13:40:25 +0200 Thomas Goirand wrote: > >> Hi, > >> > >> Since nobody seem to care about this, I've uploaded disabling that > >> failing test to DELAYED/2. Indeed, to me, it l

Bug#965026: [CONFIRM] grub-emu is unusable with orca nor BRLTTY

2020-09-08 Thread Dennis Filder
I can reproduce the problem only by running grub-emu as root. It is reproducible in both the 2.02+dfsg1-20+deb10u2 (Buster) and 2.04-8 (current Bullseye). The severity is not an exaggeration IMO as afterwards your machine will be headless. Recovering with Alt+SysRq+k does not work; neither does

Bug#969803: awscli: autopkgtest should be marked superficial

2020-09-08 Thread Noah Meyerhans
On Tue, Sep 08, 2020 at 07:33:13PM +0100, Sudip Mukherjee wrote: > > Short of communicating with a remote service, I'm not sure how we can > > get more meaningful functional test coverage in this package, but it > > would be nice to do so. > > There is also another "Restrictions: needs-internet" w

Bug#969880: marked as done (wig: autopkgtest should be marked superficial)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 18:48:40 + with message-id and subject line Bug#969880: fixed in wig 0.6-2 has caused the Debian Bug report #969880, regarding wig: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has been dealt with

Bug#969803: awscli: autopkgtest should be marked superficial

2020-09-08 Thread Paul Gevers
Hi Noah, all, On 08-09-2020 20:33, Sudip Mukherjee wrote: > On Tue, Sep 8, 2020 at 5:48 PM Noah Meyerhans wrote: >> >> On Tue, Sep 08, 2020 at 10:38:18AM +0100, Sudip Mukherjee wrote: >>> The test done in the autopkgtest of 'awscli' does not provide >>> significant test coverage and it should be

Bug#969872: marked as done (termineter: autopkgtest should be marked superficial)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 18:37:22 + with message-id and subject line Bug#969872: fixed in termineter 1.0.4-2 has caused the Debian Bug report #969872, regarding termineter: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has

Bug#957133: marked as done (dia2code: ftbfs with GCC-10)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 18:33:49 + with message-id and subject line Bug#957133: fixed in dia2code 0.8.3-4.1 has caused the Debian Bug report #957133, regarding dia2code: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#969803: awscli: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Hi Noah, On Tue, Sep 8, 2020 at 5:48 PM Noah Meyerhans wrote: > > On Tue, Sep 08, 2020 at 10:38:18AM +0100, Sudip Mukherjee wrote: > > The test done in the autopkgtest of 'awscli' does not provide > > significant test coverage and it should be marked with "Restrictions: > > superficial". > > The

Processed: [Help] Re: r-cran-rstanarm: FTBFS: error: (converted from warning) TBB library not found.

2020-09-08 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #963392 [src:r-cran-rstanarm] r-cran-rstanarm: FTBFS: error: (converted from warning) TBB library not found. Added tag(s) help. -- 963392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963392 Debian Bug Tracking System Contact ow...@bugs.debi

Bug#963392: [Help] Re: r-cran-rstanarm: FTBFS: error: (converted from warning) TBB library not found.

2020-09-08 Thread Andreas Tille
Control: tags -1 help Hi, any help why TBB is not found? I think this issue is actually causes by r-cran-rcppparallel since the code copy of libtbb was removed there - but it seems to not provide the Debian packaged lib properly. Kind regards Andreas. -- http://fam-tille.de

Bug#969880: marked as pending in wig

2020-09-08 Thread Samuel Henrique
Control: tag -1 pending Hello, Bug #969880 in wig 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: https://salsa.debian.org/pkg-security-team/wig/-/commit/16c84ecf61e3d9d48e73a7913e76163

Processed: Bug#969880 marked as pending in wig

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

Bug#969810: marked as done (changeme: autopkgtest should be marked superficial)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 18:18:39 + with message-id and subject line Bug#969810: fixed in changeme 1.2.3-2 has caused the Debian Bug report #969810, regarding changeme: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has bee

Processed: Bug#969872 marked as pending in termineter

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

Bug#969872: marked as pending in termineter

2020-09-08 Thread Samuel Henrique
Control: tag -1 pending Hello, Bug #969872 in termineter 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: https://salsa.debian.org/pkg-security-team/termineter/-/commit/f1334dab0521dcb9b

Bug#969868: marked as done (smbmap: autopkgtest should be marked superficial)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 18:06:22 + with message-id and subject line Bug#969868: fixed in smbmap 1.8.2-2 has caused the Debian Bug report #969868, regarding smbmap: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has been de

Bug#969810: marked as pending in changeme

2020-09-08 Thread Samuel Henrique
Control: tag -1 pending Hello, Bug #969810 in changeme 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: https://salsa.debian.org/pkg-security-team/changeme/-/commit/fb963c7447da14d6dd93a

Processed: Bug#969810 marked as pending in changeme

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

Processed: Bug#969868 marked as pending in smbmap

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

Bug#969868: marked as pending in smbmap

2020-09-08 Thread Samuel Henrique
Control: tag -1 pending Hello, Bug #969868 in smbmap 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: https://salsa.debian.org/pkg-security-team/smbmap/-/commit/6922fd85020fb525caa54e215

Bug#969901: marked as done (torbrowser-launcher: depends on /usr/bin/gpg2 but dependency not expressed)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 17:34:10 + with message-id and subject line Bug#969901: fixed in torbrowser-launcher 0.3.2-13 has caused the Debian Bug report #969901, regarding torbrowser-launcher: depends on /usr/bin/gpg2 but dependency not expressed to be marked as done. This means th

Bug#969803: awscli: autopkgtest should be marked superficial

2020-09-08 Thread Noah Meyerhans
On Tue, Sep 08, 2020 at 10:38:18AM +0100, Sudip Mukherjee wrote: > The test done in the autopkgtest of 'awscli' does not provide > significant test coverage and it should be marked with "Restrictions: > superficial". The current test merely invokes "/usr/bin/aws help". Is there any actual value i

Bug#966982: Uploading disabling that test to DELAYED/2

2020-09-08 Thread Håvard Flaget Aasen
On Tue, 8 Sep 2020 13:40:25 +0200 Thomas Goirand wrote: > Hi, > > Since nobody seem to care about this, I've uploaded disabling that > failing test to DELAYED/2. Indeed, to me, it looked like a broken test, > rather than a broken package. Otherwise, a long list of reverse > dependency will be rem

Processed: reopening 969907

2020-09-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 969907 Bug #969907 {Done: David Bremner } [libpoppler-glib8] libpoppler-glib8: introduces new ABI without bumping shlibs version Bug reopened Ignoring request to alter fixed versions of bug #969907 to the same values previously set > than

Processed: found 964902 in 0.39-1

2020-09-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 964902 0.39-1 Bug #964902 {Done: Dominic Hargreaves } [libio-socket-ip-perl] libio-socket-ip-perl: AI_ADDRCONFIG breaks many test suites on IPv6-only hosts Marked as found in versions libio-socket-ip-perl/0.39-1. > thanks Stopping processin

Bug#957526: marked as done (medusa: ftbfs with GCC-10)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 15:35:30 + with message-id and subject line Bug#957526: fixed in medusa 2.2-7 has caused the Debian Bug report #957526, regarding medusa: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#961211: marked as done (r-cran-lwgeom: autopkgtest failures on s390x)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 15:26:04 + with message-id and subject line Bug#961211: fixed in r-cran-lwgeom 0.2-5-2 has caused the Debian Bug report #961211, regarding r-cran-lwgeom: autopkgtest failures on s390x to be marked as done. This means that you claim that the problem has been

Bug#969909: xmoto-data: Broken links to DejaVu fonts

2020-09-08 Thread Pavel Reznicek
Package: xmoto-data Version: 0.6.1+repack-2 Severity: serious Justification: 4 Dear Maintainer, the links to DejaVu fonts are pointing to non-existent locations: /usr/share/games/xmoto/Textures/Fonts/DejaVuSans.ttf -> ../../../../fonts/truetype/ttf-dejavu/DejaVuSans.ttf /usr/share/games/xmoto

Bug#962318: marked as done (libmojolicious-perl: build fails on IPv6-only buildds)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 15:21:56 + with message-id and subject line Bug#962318: fixed in libmojolicious-perl 8.58+dfsg-2 has caused the Debian Bug report #962318, regarding libmojolicious-perl: build fails on IPv6-only buildds to be marked as done. This means that you claim that t

Bug#966653: Any progress?

2020-09-08 Thread GCS
Hi Thomas, On Tue, Sep 8, 2020 at 1:27 PM Thomas Goirand wrote: > I'm not seeing any progress on this bug. Is anyone working on this? The bug report is too wide, "GitLab can't start" doesn't help to narrow it down. I even suspect the real bug is in GitLab itself, it may not (correctly) handle th

Bug#969823: marked as done (etktab: autopkgtest should be marked superficial)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 15:03:28 + with message-id and subject line Bug#969823: fixed in etktab 3.2-12 has caused the Debian Bug report #969823, regarding etktab: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has been dea

Bug#966523: r-bioc-rsubread FTBFS on 32bit: error: conflicting types for ‘uintptr_t’

2020-09-08 Thread Andreas Tille
Hi, I'm hereby forwarding a problem that was detected on the Debian packaged version of Rsubread. Any idea how to fix this? Kind regards Andreas. On Thu, Jul 30, 2020 at 08:50:31AM +0300, Adrian Bunk wrote: > Source: r-bioc-rsubread > Version: 2.2.5-1 > Severity: serious > Tags: ftbfs >

Processed: cloning 969537, reassign -1 to libpoppler-glib8 ...

2020-09-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 969537 -1 Bug #969537 {Done: David Bremner } [elpa-pdf-tools-server] elpa-pdf-tools-server: broken when compiled against libpoppler102 Bug 969537 cloned as bug 969907 > reassign -1 libpoppler-glib8 20.09.0-2 Bug #969907 {Done: David Bremner

Processed: Bug#962318 marked as pending in libmojolicious-perl

2020-09-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #962318 [src:libmojolicious-perl] libmojolicious-perl: build fails on IPv6-only buildds Added tag(s) pending. -- 962318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962318 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Bug#962318: marked as pending in libmojolicious-perl

2020-09-08 Thread gregor herrmann
Control: tag -1 pending Hello, Bug #962318 in libmojolicious-perl 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: https://salsa.debian.org/perl-team/modules/packages/libmojolicious-perl

Bug#966982: Uploading disabling that test to DELAYED/2

2020-09-08 Thread Thomas Goirand
On 9/8/20 2:01 PM, Håvard Flaget Aasen wrote: > On Tue, 8 Sep 2020 13:40:25 +0200 Thomas Goirand wrote: >> Hi, >> >> Since nobody seem to care about this, I've uploaded disabling that >> failing test to DELAYED/2. Indeed, to me, it looked like a broken test, >> rather than a broken package. Otherw

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

2020-09-08 Thread Marek Straka
It looks like after reboot old config is back.

Bug#954855: php7.4-enchant: API/ABI change for enchant-2

2020-09-08 Thread Tommy Wu
linux-vdso.so.1 (0x7fffe0938000) libenchant-2.so.2 => /usr/lib/x86_64-linux-gnu/libenchant-2.so.2 (0x7f1264539000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1264374000) libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00

Bug#968661: marked as done (peony-extensions: hardcodes dependency on libpeony2)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 14:10:19 + with message-id and subject line Bug#968661: fixed in peony-extensions 3.0.0-1 has caused the Debian Bug report #968661, regarding peony-extensions: hardcodes dependency on libpeony2 to be marked as done. This means that you claim that the proble

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

2020-09-08 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:nvidia-graphics-drivers-legacy-390xx Bug #969894 [nvidia-legacy-390xx-driver] nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel Bug reassigned from package 'nvidia-legacy-390xx-driver' to 'src:nvidia-graphi

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

2020-09-08 Thread Vincent Lefevre
Control: reassign -1 src:nvidia-graphics-drivers-legacy-390xx Control: affects -1 linux-image-5.8.0-1-amd64 Control: merge 969889 -1 On 2020-09-08 07:17:18 -0500, allan grossman wrote: > Upgraded Sid this morning and X will not start with 5.8 kernel with nvidia- > legacy-390xx-driver. Works fine

Bug#969901: torbrowser-launcher: depends on /usr/bin/gpg2 but dependency not expressed

2020-09-08 Thread Jonathan Dowland
Package: torbrowser-launcher Version: 0.3.2-11~bpo10+1 Severity: serious Justification: Policy 3.5 There's a few things going on in this session, but this bug report is about the last backtrace in particular: $ torbrowser-launcher Tor Browser Launcher By Micah Lee, licensed under MIT version 0.3.

Bug#962213: package ftbfs on arm64 and armhf

2020-09-08 Thread Alec Leamas
On Mon, 20 Jul 2020 12:38:36 +0200 Alec Leamas wrote: > I have not been able to test the arm builds, taking your word that > lindrm-dev should fix it. ubuntu test builds at https://launchpad.net/~leamas-alec/+archive/ubuntu/opencpn/+sourcepub/11570928/+listing-archive-extra The package builds o

Processed: Re: Bug#969889: linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work

2020-09-08 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #969889 [src:nvidia-graphics-drivers-legacy-390xx] linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work Severity set to 'grave' from 'important' > tags -1 - moreinfo Bug #969889 [src:nvidia-graphics-drivers-legacy-390xx] li

Bug#969074: [PATCH] d/p/lp-1894129-*: fix FTBFS (LP: #1894129 Closes: #969074)

2020-09-08 Thread Christian Ehrhardt
Signed-off-by: Christian Ehrhardt --- ...raseReserved-override-driver-queue_p.patch | 74 ...BlockEraseReserved-skip-unless-iSCSI.patch | 39 ...e-Write-override-driver-queue_pdu-ca.patch | 71 ...e-Write-skip-InvalidDataOutSize-unle.patch | 39 ...EraseReserved-ov

Bug#966921: marked as done (path in libdpdk.pc must be versioned with tooling version)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 12:49:50 + with message-id and subject line Bug#966921: fixed in dpdk 19.11.4-1 has caused the Debian Bug report #966921, regarding path in libdpdk.pc must be versioned with tooling version to be marked as done. This means that you claim that the problem ha

Bug#969074: Reported upstream and partial fix exists already

2020-09-08 Thread Christian Ehrhardt
FYI: - https://github.com/sahlberg/libiscsi/issues/340 - https://github.com/sahlberg/libiscsi/commit/dd17293bcc188dbefc420ee23b77bc9bb7c5e9a2 But that isn't everything. I'm looking at this for https://bugs.launchpad.net/ubuntu/+source/libiscsi/+bug/1894129 and will send patches here once it works

Bug#954855: php7.4-enchant: API/ABI change for enchant-2

2020-09-08 Thread Tommy Wu
Package: php7.4-enchant Version: 7.4.9-2 Followup-For: Bug #954855 Dear Maintainer, Error message like this: PHP Warning: PHP Startup: Unable to load dynamic library 'enchant.so' (tried: /usr/lib/php/20190902/enchant.so (/usr/lib/php/20190902/enchant.so: undefined symbol: enchant_dict_is_in_se

Bug#946733: marked as done (rust-curl: autopkgtest failure: no matching package named `openssl-probe` found)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 8 Sep 2020 13:20:41 +0100 with message-id and subject line rust-curl: autopkgtest failure: no matching package named `openssl-probe` found has caused the Debian Bug report #946733, regarding rust-curl: autopkgtest failure: no matching package named `openssl-probe` found t

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

2020-09-08 Thread allan grossman
Package: nvidia-legacy-390xx-driver Version: 390.138-2 Severity: grave Justification: renders package unusable Dear Maintainer, Upgraded Sid this morning and X will not start with 5.8 kernel with nvidia- legacy-390xx-driver. Works fine with 5.7.x kernel. -- Package-specific info: uname -a: Li

Bug#964742: marked as done (src:binutils-mingw-w64: FTBFS on s390x: FAIL: objcopy executable (pr25662))

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 12:18:27 + with message-id and subject line Bug#964742: fixed in binutils-mingw-w64 8.11 has caused the Debian Bug report #964742, regarding src:binutils-mingw-w64: FTBFS on s390x: FAIL: objcopy executable (pr25662) to be marked as done. This means that yo

Processed: Re: Bug#969889: linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work

2020-09-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #969889 [src:linux] linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work Added tag(s) moreinfo. > severity -1 important Bug #969889 [src:linux] linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work Severity

Bug#969889: linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work

2020-09-08 Thread Bastian Blank
Control: tag -1 moreinfo Control: severity -1 important On Tue, Sep 08, 2020 at 01:36:45PM +0200, Vincent Lefevre wrote: > This version fails to load kernel modules (no issues with previous > Linux kernels provided by Debian). As a consequence, X does not work. > ** Loaded modules: > rfcomm > ipt

Bug#969753: diffoscope: autopkgtest failures

2020-09-08 Thread Chris Lamb
Hi Gianfranco, > Hello, autopkgtests looks sad, pytest-with-recommends works, while > pytest doesn't, because of missing pgpdump > > I did add some @skip_unless_tools_exist("pgpdump") around the failing > tests (attached the diff), however I don't know > if this is the right solution, or something

Processed: owner 969888

2020-09-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 969888 woodrow.s...@gmail.com Bug #969888 [src:pdf2djvu] pdf2djvu FTBFS with poppler 20 Owner recorded as woodrow.s...@gmail.com. > thanks Stopping processing here. Please contact me if you need assistance. -- 969888: https://bugs.debian.o

Bug#966982: Uploading disabling that test to DELAYED/2

2020-09-08 Thread Thomas Goirand
Hi, Since nobody seem to care about this, I've uploaded disabling that failing test to DELAYED/2. Indeed, to me, it looked like a broken test, rather than a broken package. Otherwise, a long list of reverse dependency will be removed from testing in 8 days. Debdiff of the change attached. Let me

Bug#969889: linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work

2020-09-08 Thread Vincent Lefevre
Package: src:linux Version: 5.8.7-1 Severity: grave Justification: renders package unusable This version fails to load kernel modules (no issues with previous Linux kernels provided by Debian). As a consequence, X does not work. I've attached the dmesg output. -- Package-specific info: ** Versio

Bug#969888: pdf2djvu FTBFS with poppler 20

2020-09-08 Thread peter green
Source: pdf2djvu Version: 0.9.17-1 Severity: serious Tags: ftbfs, fixed-upstream pdf2djvu's configure script fails to parse the poppler version with the newly released poppler 20. This results in a bunch of errors. This is fixed upstream in version 0.9.17.1

Bug#966653: Any progress?

2020-09-08 Thread Thomas Goirand
Hi, I'm not seeing any progress on this bug. Is anyone working on this? Without any action, this going to trigger the removal of most of OpenStack from testing... :/ Cheers, Thomas Goirand (zigo)

Bug#963827: [virtualbox] guests limited to 800x600

2020-09-08 Thread Gianfranco Costamagna
Hello, On Sat, 27 Jun 2020 23:25:26 +0100 Lyndon Brown wrote: > Package: src:virtualbox > Version: 6.1.10-dfsg-1 > Severity: important > > After installing a handful of updates in a Sid guest and rebooting it, > it's now stuck with an unusable display area of 800x600. > should be fixed now G

Bug#969883: yowsup: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: yowsup Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'yowsup' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package

Bug#969880: wig: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: wig Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'wig' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package-tests

Bug#969882: wmxres: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: wmxres Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'wmxres' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package

Bug#969879: wifite: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: wifite Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'wifite' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package

Bug#969878: virt-what: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: virt-what Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'virt-what' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.p

Bug#969156: marked as done (rumur FTBFS on armel/armhf/mipsel/mips64el: test failures)

2020-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2020 10:49:24 + with message-id and subject line Bug#969156: fixed in rumur 2020.09.06-1 has caused the Debian Bug report #969156, regarding rumur FTBFS on armel/armhf/mipsel/mips64el: test failures to be marked as done. This means that you claim that the proble

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

2020-09-08 Thread Marek Straka
I always synchronized only some directories from nextcloud server. After upgrade nextcloud client started to synchronize everything because all folders was checked.

  1   2   >