Bug#995281: lomiri-download-manager: FTBFS due to symbols changes

Source: lomiri-download-manager Version: 0.1.0-8 Severity: serious Hi Mike, The lomiri-download-manager package fails to build in unstable, because of some symbols file mismatches: [...] dpkg-gensymbols: warning: debian/liblomiri-download-manager-common0/DEBIAN/symbols doesn't match

Bug#995282: amule crashes on start

Package: amule Version: 1:2.3.3-1 Severity: grave (gdb) run Starting program: /usr/bin/amule [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Detaching after vfork from child process 7263] 2021-09-29 07:08:05: Initialising

Processed: ayatana-indicator-datetime: Fails to build from source

Processing commands for cont...@bugs.debian.org: > block 993945 by 995279 Bug #993945 [release.debian.org] transition: evolution-data-server 993945 was blocked by: 992870 993934 993945 was blocking: 993850 Added blocking bug(s) of 993945: 995279 > tags 995279 +ftbfs Bug #995279

Bug#995279: ayatana-indicator-datetime: Fails to build from source

Source: ayatana-indicator-datetime Version: 0.8.2-1 Severity: serious Tags: patch sid bookworm Control: blocks 993945 by -1 Please apply this commit to Debian to fix this package's failure to build from source. https://github.com/AyatanaIndicators/ayatana-indicator-datetime/commit/19923632 This

Bug#995187: qtwebengine-opensource-src FTBFS on mips*: unistd_nr_{n32,n64,o32}.h no linger exported by the kernel

YunQiang Su 于2021年9月28日周二 下午12:20写道： > > Adrian Bunk 于2021年9月28日周二 上午12:06写道： > > > > Source: qtwebengine-opensource-src > > Version: 5.15.5+dfsg-2 > > Severity: serious > > Tags: ftbfs > > > >

Processed: user release.debian....@packages.debian.org, usertagging 994451, tagging 994451

Processing commands for cont...@bugs.debian.org: > user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was siret...@tauware.de). > usertags 994451 pu There were no usertags set. Usertags are now: pu. > tags 994451 + bullseye Bug #994451

Bug#995223: libffi: SIGILL on powerpc and ppc64 systems since libffi8

Hello! On 9/29/21 00:38, John Paul Adrian Glaubitz wrote: > There is actually a baseline violation on i386 as "-march=amdfam10" is > passed to the compiler, see the build log in [1], for example. Comparing the build logs, it seems that this an issue with the newer version of autoconf that was

Bug#995223: libffi: SIGILL on powerpc and ppc64 systems since libffi8

Hi! On 9/28/21 22:40, John Paul Adrian Glaubitz wrote: > We should therefore pass "--enable-portable-binary" in debian/rules. There is actually a baseline violation on i386 as "-march=amdfam10" is passed to the compiler, see the build log in [1], for example. Adrian > [1] >

Bug#957954: wmwave: diff for NMU version 0.4-11.1

Control: tags 957954 + patch Control: tags 957954 + pending Dear maintainer, I've prepared an NMU for wmwave (versioned as 0.4-11.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer or cancel the NMU. Regards. diff -Nru wmwave-0.4/debian/changelog

Processed: wmwave: diff for NMU version 0.4-11.1

Processing control commands: > tags 957954 + patch Bug #957954 [src:wmwave] wmwave: ftbfs with GCC-10 Ignoring request to alter tags of bug #957954 to the same tags previously set > tags 957954 + pending Bug #957954 [src:wmwave] wmwave: ftbfs with GCC-10 Added tag(s) pending. -- 957954:

Processed: webalizer: diff for NMU version 2.23.08-3.2

Processing control commands: > tags 957923 + patch Bug #957923 [src:webalizer] webalizer: ftbfs with GCC-10 Ignoring request to alter tags of bug #957923 to the same tags previously set > tags 957923 + pending Bug #957923 [src:webalizer] webalizer: ftbfs with GCC-10 Added tag(s) pending. --

Bug#957923: webalizer: diff for NMU version 2.23.08-3.2

Control: tags 957923 + patch Control: tags 957923 + pending Dear maintainer, I've prepared an NMU for webalizer (versioned as 2.23.08-3.2) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer or cancel the NMU. Regards. diff -Nru

Bug#983206: [libupnp13] Please update for CVE-2020-12695 & fixes

With bullseye now released, can we please now progress with the necessary transition to upgrade and thus address the security issue?

Bug#995272: libsql-abstract-pg-perl: trying to overwrite '/usr/share/man/man3/SQL::Abstract::Pg.3pm.gz', which is also in package libmojo-pg-perl 4.24-1

Package: libsql-abstract-pg-perl,libmojo-pg-perl Severity: serious Version: libsql-abstract-pg-perl/1.0-1 Version: libmojo-pg-perl/4.24-1 Trying to install libsql-abstract-pg-perl when libmojo-pg-perl is already installed results in a file conflict as follows: Preparing to unpack

Bug#994971: OpenCL not working with latest Nvidia driver

On 2021-09-26 18:58:48 +0200, Andreas Beckmann wrote: > Control: severity -1 serious > > On 26/09/2021 18.07, Klaus Ethgen wrote: > > > available somewhere in /var/log/apt/term.log*, it might give some hints > > > what > > > happened. > > > > Here it is. > > Thanks. You had modifications in

Bug#994567: marked as done (black: autopkgtest regression: ModuleNotFoundError: No module named 'aiohttp_cors')

Your message dated Tue, 28 Sep 2021 21:20:47 + with message-id and subject line Bug#994567: fixed in black 21.4b2-2 has caused the Debian Bug report #994567, regarding black: autopkgtest regression: ModuleNotFoundError: No module named 'aiohttp_cors' to be marked as done. This means that

Bug#981699: fixed in thinkfan 1.2.1-3.1

Debian FTP Masters dixit: > * Don't ship an example config in /etc/thinkfan.yaml (Closes: #983727) > * Ship example config in /usr/share/doc/thinkfan/examples/ I don’t think these resolve my issue with the newer thinkfan releases. I’ve looked at the example configuration, and it refers to

Processed: Re: Bug#995223: libffi: SIGILL on powerpc and ppc64 systems since libffi8

Processing control commands: > severity -1 serious Bug #995223 [src:libffi] libffi: SIGILL on powerpc and ppc64 systems since libffi8 Severity set to 'serious' from 'important' -- 995223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995223 Debian Bug Tracking System Contact

Processed: severity of 995051 is important

Processing commands for cont...@bugs.debian.org: > # only times out on some buildds > severity 995051 important Bug #995051 [src:python3.9] python3.9: FTBFS on i386: test timeout Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need

Processed: tagging 995175

Processing commands for cont...@bugs.debian.org: > tags 995175 + upstream fixed-upstream Bug #995175 [src:request-tracker4] request-tracker4: CVE-2021-38562 Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 995175:

Bug#981699: marked as done (thinkfan: fails on upgrade)

Your message dated Tue, 28 Sep 2021 17:19:44 + with message-id and subject line Bug#981699: fixed in thinkfan 1.2.1-3.1 has caused the Debian Bug report #981699, regarding thinkfan: fails on upgrade to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#983727: marked as done (thinkfan should not ship an example in /etc/thinkfan.yaml)

Your message dated Tue, 28 Sep 2021 17:19:44 + with message-id and subject line Bug#983727: fixed in thinkfan 1.2.1-3.1 has caused the Debian Bug report #983727, regarding thinkfan should not ship an example in /etc/thinkfan.yaml to be marked as done. This means that you claim that the

Bug#995266: openmpi: binary-all FTBFS

Source: openmpi Version: 4.1.2~rc1-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=openmpi=all=4.1.2~rc1-3=1632846883=0 ... dh_missing -i dh_missing: warning: usr/share/doc/openmpi/javadoc-openmpi/allclasses-index.html exists in debian/tmp but is not installed

Bug#995260: closed by Vincent Blut (Re: Bug#995260: chrony: Mismatched filename for UNIX socket between client and daemon)

so why did it not use the Unix socket but fell back to 127.0.0.1 approach? i wonder what happens if i do ‘cmddeny all’?

Bug#995260: marked as done (chrony: Mismatched filename for UNIX socket between client and daemon)

Your message dated Tue, 28 Sep 2021 18:59:37 +0200 with message-id and subject line Re: Bug#995260: chrony: Mismatched filename for UNIX socket between client and daemon has caused the Debian Bug report #995260, regarding chrony: Mismatched filename for UNIX socket between client and daemon to

Bug#995260: chrony: Mismatched filename for UNIX socket between client and daemon

Hi, Le 2021-09-28 11:55, Steve Egbert a écrit : > Package: chrony > Version: 4.0-8 > Severity: grave > Tags: upstream > Justification: renders package unusable > X-Debbugs-Cc: s.egb...@sbcglobal.net > > Dear Maintainer, > > > The filename construct for a UNIX socket to be shared > between the

Bug#995263: user-mode-linux: build-depends on removed package.

Source: user-mode-linux Version: 5.10um3 Severity: serious Justification: rc policy - "Packages must be buildable within the same release." Tags: bookworm, sid user-mode-linux build-depends on linux-source-5.10 which is no longer built by the linux source package. It is still present in

Bug#995150: marked as done (openmpi: segfault in mca_io_romio_dist_MPI_File_iwrite_all)

Your message dated Tue, 28 Sep 2021 16:08:06 + with message-id and subject line Bug#995150: fixed in openmpi 4.1.2~rc1-3 has caused the Debian Bug report #995150, regarding openmpi: segfault in mca_io_romio_dist_MPI_File_iwrite_all to be marked as done. This means that you claim that the

Processed: fixed 995215 in 0.31.1-2

Processing commands for cont...@bugs.debian.org: > fixed 995215 0.31.1-2 Bug #995215 [postgresql-semver] postgresql-semver: Wait for acceptance of backport There is no source info for the package 'postgresql-semver' at version '0.31.1-2' with architecture '' Unable to make a source version for

Bug#995260: chrony: Mismatched filename for UNIX socket between client and daemon

Package: chrony Version: 4.0-8 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: s.egb...@sbcglobal.net Dear Maintainer, The filename construct for a UNIX socket to be shared between the Chrony (chronyd) daemon and its Chrony CLI (chronyc) client admin tool

Bug#995199: marked as done (r-bioc-ioniser: autopkgtest regression)

Your message dated Tue, 28 Sep 2021 15:49:43 + with message-id and subject line Bug#995199: fixed in r-bioc-ioniser 2.16.0+dfsg-2 has caused the Debian Bug report #995199, regarding r-bioc-ioniser: autopkgtest regression to be marked as done. This means that you claim that the problem has

Bug#995114: marked as done (python3-pyroute2.{core,ndb}: missing Breaks+Replaces: python3-pyroute2 (<< 0.6))

Your message dated Tue, 28 Sep 2021 15:38:36 + with message-id and subject line Bug#995114: fixed in pyroute2 0.6.4-2 has caused the Debian Bug report #995114, regarding python3-pyroute2.{core,ndb}: missing Breaks+Replaces: python3-pyroute2 (<< 0.6) to be marked as done. This means that you

Bug#994896: marked as done (pyhst2: FTBFS due to missing B-D: python3-six)

Your message dated Tue, 28 Sep 2021 15:19:05 + with message-id and subject line Bug#994896: fixed in pyhst2 2020c-2 has caused the Debian Bug report #994896, regarding pyhst2: FTBFS due to missing B-D: python3-six to be marked as done. This means that you claim that the problem has been

Bug#995241: marked as done (rdkit FTBFS with sphinx 4.2)

Your message dated Tue, 28 Sep 2021 14:48:30 + with message-id and subject line Bug#995241: fixed in rdkit 202009.5-2 has caused the Debian Bug report #995241, regarding rdkit FTBFS with sphinx 4.2 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: limit source to pyhst2, tagging 994896

Processing commands for cont...@bugs.debian.org: > limit source pyhst2 Limiting to bugs with field 'source' containing at least one of 'pyhst2' Limit currently set to 'source':'pyhst2' > tags 994896 + pending Bug #994896 [src:pyhst2] pyhst2: FTBFS due to missing B-D: python3-six Added tag(s)

Bug#995242: isc-dhcp-server: omshell returns inconsistent results or segfaults

Package: isc-dhcp-server Version: 4.4.1-2.3 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 11.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel:

Bug#995241: rdkit FTBFS with sphinx 4.2

Source: rdkit Version: 202009.5-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=rdkit=202009.5-1%2Bb2 ... ! LaTeX Error: File `tgtermes.sty' not found. ... Latexmk: Errors, so I did not complete making targets make[3]: *** [Makefile:29: RDKit.pdf] Error 12 A build

Bug#993198: gnome-shell-extension-system-monitor: does not declare compatibility with GNOME Shell 40

On Tue, Sep 28, 2021 at 12:27 AM Samuel Henrique wrote: > I gave you permission to that repo (best I can do on my side), and I > set an expiration date of the end of this year, until then you will > end up in the salsa group and inherit permissions so it should be > good. Perfect, thanks! >

Bug#994699: marked as done (libtest-xml-simple-perl: Test failure in t/03valid.t)

Your message dated Tue, 28 Sep 2021 10:23:08 + with message-id and subject line Bug#994699: fixed in libtest-xml-simple-perl 1.05-3 has caused the Debian Bug report #994699, regarding libtest-xml-simple-perl: Test failure in t/03valid.t to be marked as done. This means that you claim that

Processed: Bug#994699 marked as pending in libtest-xml-simple-perl

Processing control commands: > tag -1 pending Bug #994699 [libtest-xml-simple-perl] libtest-xml-simple-perl: Test failure in t/03valid.t Added tag(s) pending. -- 994699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994699 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#994699: marked as pending in libtest-xml-simple-perl

Control: tag -1 pending Hello, Bug #994699 in libtest-xml-simple-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:

Processed: upstream

Processing commands for cont...@bugs.debian.org: > forwarded 995150 https://github.com/open-mpi/ompi/issues/9432 Bug #995150 [src:openmpi] openmpi: segfault in mca_io_romio_dist_MPI_File_iwrite_all Set Bug forwarded-to-address to 'https://github.com/open-mpi/ompi/issues/9432'. > thanks Stopping

Processed: Re: Bug#995216: simple-scan: B Text scans saved as gibberish

Processing commands for cont...@bugs.debian.org: > severity 995216 normal Bug #995216 [simple-scan] simple-scan: B Text scans saved as gibberish Severity set to 'normal' from 'grave' > tags 995216 + moreinfo Bug #995216 [simple-scan] simple-scan: B Text scans saved as gibberish Added tag(s)

Bug#995216: simple-scan: B Text scans saved as gibberish

severity 995216 normal tags 995216 + moreinfo thanks Hello Felix, thank you for spending your time helping to make Debian better with this bug report. First of all, I set the severity to normal, because there is no data loss in the sense of grave, but only an erroneous output. For a better

Processed: affects 995150

Processing commands for cont...@bugs.debian.org: > affects 995150 src:mpi4py Bug #995150 [src:openmpi] openmpi: segfault in mca_io_romio_dist_MPI_File_iwrite_all Added indication that 995150 affects src:mpi4py > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: tagging 995150

Processing commands for cont...@bugs.debian.org: > tags 995150 + ftbfs Bug #995150 [src:openmpi] openmpi: segfault in mca_io_romio_dist_MPI_File_iwrite_all Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 995150:

Bug#995228: Old bug is back, needs a rebuild.

I've just rebuilt qtcreator locally, and the bug is gone. Dear maintainer, please rebuild the package. Roman. On Tue, Sep 28, 2021 at 11:24 AM Roman Lebedev wrote: > > Package: qtcreator > Version: 5.0.1-1 > Severity: serious > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Looks like

Bug#995228: Old bug is back, needs a rebuild.

Package: qtcreator Version: 5.0.1-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Looks like qtcreator (and iwyu/etc) need to be rebuilt again. After some recent updates, qtcreator again shows errors about certain C++ types not being known. Roman - -- System Information:

Bug#995224: relion-cuda: FTBFS with cub 1.14

Source: relion-cuda Version: 3.1.0-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source Hi, relion-cuda FTBFS with cub 1.14 which was just uploaded to unstable: make[4]: Entering directory '/build/relion-cuda-3.1.0/build' [ 1%] Building NVCC (Device) object

Bug#994673: marked as done (slcfitsio FTBFS: error: too many decimal points in number)

Your message dated Tue, 28 Sep 2021 07:19:07 + with message-id and subject line Bug#994673: fixed in slcfitsio 0.3.8+nosvn-6 has caused the Debian Bug report #994673, regarding slcfitsio FTBFS: error: too many decimal points in number to be marked as done. This means that you claim that the

Bug#995187: qtwebengine-opensource-src FTBFS on mips*: unistd_nr_{n32,n64,o32}.h no linger exported by the kernel

Adrian Bunk 于2021年9月28日周二 上午12:06写道： > > Source: qtwebengine-opensource-src > Version: 5.15.5+dfsg-2 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src=mips64el=5.15.6%2Bdfsg-1=1632387575=0 > > ... > FAILED:

Bug#995216: simple-scan: B Text scans saved as gibberish

Package: simple-scan Found: 3.38.1-1 Severity: grave Hi, Starting earlier today (between scans) simple-scan on bullseye became unable to save B text scans properly. Now they are saved as gibberish. It is possible the files are being saved in a format not understood by my PDF reader, but I could

Bug#995206: marked as done (r-bioc-altcdfenvs: autopkgtest regression)

Your message dated Tue, 28 Sep 2021 06:04:20 + with message-id and subject line Bug#995206: fixed in r-bioc-altcdfenvs 1:2.54.0-2 has caused the Debian Bug report #995206, regarding r-bioc-altcdfenvs: autopkgtest regression to be marked as done. This means that you claim that the problem has

Bug#995215: postgresql-semver: Wait for acceptance of backport

Package: postgresql-semver Severity: serious The sole purpose of this bug is to keep version 0.31.1-3 out of testing until version 0.31.1-2~bpo11+1 is in backports.