Bug#1012987: libpodofo: ftbfs with GCC-12

Hi Nicholas > It looks like the a "Source" or "Forwarded" DEP3 header with a link to > Pino's pull request is missing. > https://dep-team.pages.debian.net/deps/dep3 I was updated my salsa merge request. https://salsa.debian.org/debian/libpodofo/-/merge_requests/2 -- YOKOTA Hiroshi

Bug#984131: marked as done (flmsg: ftbfs with GCC-11)

Your message dated Sat, 20 Aug 2022 02:40:27 + with message-id and subject line Bug#984131: fixed in flmsg 4.0.20-1 has caused the Debian Bug report #984131, regarding flmsg: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1012329: marked as done (intel-vc-intrinsics: Please upgrade to llvm-toolchain-14)

Your message dated Sat, 20 Aug 2022 00:19:01 + with message-id and subject line Bug#1012329: fixed in intel-vc-intrinsics 0.5.0-2 has caused the Debian Bug report #1012329, regarding intel-vc-intrinsics: Please upgrade to llvm-toolchain-14 to be marked as done. This means that you claim that

Processed: owner 984131

Processing commands for cont...@bugs.debian.org: > owner 984131 tmanc...@debian.org Bug #984131 [src:flmsg] flmsg: ftbfs with GCC-11 Owner recorded as tmanc...@debian.org. > thanks Stopping processing here. Please contact me if you need assistance. -- 984131:

Processed: tag 1017596 pending

Processing commands for cont...@bugs.debian.org: > tags 1017596 + pending Bug #1017596 [src:openrct2] openrct2: FTBFS with warnings as errors Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 1017596:

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 1017760 src:linux Bug #1017760 [src:linux] linux-image-5.10.0-17-amd64: No space for directory leaf checksum. Please run e2fsck -D. Ignoring request to reassign bug #1017760 to the same package > found 1017760 5.10.136-1 Bug #1017760

Processed: severity of 1017544 is important, severity of 1017564 is important, severity of 1017652 is important

Processing commands for cont...@bugs.debian.org: > severity 1017544 important Bug #1017544 [src:golang-github-anacrolix-missinggo] golang-github-anacrolix-missinggo: FTBFS: test failures Severity set to 'important' from 'serious' > severity 1017564 important Bug #1017564 [src:consul] consul:

Processed: affects 1017356

Processing commands for cont...@bugs.debian.org: > affects 1017356 openmpi Bug #1017356 [libpmix2] libpmix2: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load Added indication that 1017356 affects openmpi > thanks Stopping

Processed: affects 1017356

Processing commands for cont...@bugs.debian.org: > affects 1017356 dolfin Bug #1017356 [libpmix2] libpmix2: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load Added indication that 1017356 affects dolfin > thanks Stopping

Processed: forcibly merging 1017756 1017731

Processing commands for cont...@bugs.debian.org: > forcemerge 1017756 1017731 Bug #1017756 [src:iem-plugin-suite] iem-plugin-suite FTBFS: error: no matching function for call to ‘juce::Matrix3D::Matrix3D(juce::Vector3D)’ Bug #1017731 [src:iem-plugin-suite] iem-plugin-suite: fails to build with

Bug#1017748: libuv1 breaks siridb-server autopkgtest: test times out

Hi folks, Some recent small changes in libuv had unexpected outcomes, I suppose upstream siridb should be made aware of it. Le ven. 19 août 2022 à 22:42, Paul Gevers a écrit : > Hi Jeroen, > > On 19-08-2022 21:39, Paul Gevers wrote: > > With a recent upload of libuv1 the autopkgtest of

Processed (with 1 error): merging 1017756 1017731

Processing commands for cont...@bugs.debian.org: > merge 1017756 1017731 Bug #1017756 [src:iem-plugin-suite] iem-plugin-suite FTBFS: error: no matching function for call to ‘juce::Matrix3D::Matrix3D(juce::Vector3D)’ Unable to merge bugs because: severity of #1017731 is 'normal' not 'serious'

Bug#1017760: linux-image-5.10.0-17-amd64: No space for directory leaf checksum. Please run e2fsck -D.

Package: src:linux Version: 5.10.136-1 Severity: grave Justification: causes non-serious data loss X-Debbugs-Cc: t...@mirbsd.de I’ve recently been getting filesystem corruption on this system, which, incidentally, is a fresh-ish installation since I’ve been hit by the “forgot LUKS password for

Processed: found 993014 in 2:6.11-3

Processing commands for cont...@bugs.debian.org: > found 993014 2:6.11-3 Bug #993014 [src:cifs-utils] cifs-utils non-parallel FTBFS Marked as found in versions cifs-utils/2:6.11-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 993014:

Bug#1017756: iem-plugin-suite FTBFS: error: no matching function for call to ‘juce::Matrix3D::Matrix3D(juce::Vector3D)’

Source: iem-plugin-suite Version: 1.13.0-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=iem-plugin-suite=amd64=1.13.0-2%2Bb2=1660937897=0 ... In file included from /<>/AllRADecoder/Source/PluginEditor.h:36, from

Bug#1017748: libuv1 breaks siridb-server autopkgtest: test times out

Hi Jeroen, On 19-08-2022 21:39, Paul Gevers wrote: With a recent upload of libuv1 the autopkgtest of siridb-server fails in testing when that autopkgtest is run with the binary packages of libuv1 from unstable. It passes when run with only packages from testing. In tabular form: I quickly

Processed: Re: sambamba: FTBFS: ../meson.build:9:0: ERROR: Unable to detect linker for compiler `ldc2 -L=--version /tmp/tmp1izbdod0.d -Wl,-z,relro -O -g -release -wi`

Processing control commands: > reassign -1 meson 0.63.1-1 Bug #1017237 [src:sambamba] sambamba: FTBFS: ../meson.build:9:0: ERROR: Unable to detect linker for compiler `ldc2 -L=--version /tmp/tmp1izbdod0.d -Wl,-z,relro -O -g -release -wi` Bug reassigned from package 'src:sambamba' to 'meson'. No

Bug#1017237: sambamba: FTBFS: ../meson.build:9:0: ERROR: Unable to detect linker for compiler `ldc2 -L=--version /tmp/tmp1izbdod0.d -Wl,-z,relro -O -g -release -wi`

Control: reassign -1 meson 0.63.1-1 Control: forcemerge -1 1017087 Control: affects 1017087 + sambamba This is due to bug #1017087 in meson itself which I reported a few days ago. I am re-assigning, merging and adding in an affects. On Sun, 14 Aug 2022 09:51:09 +0200 Lucas Nussbaum wrote: >

Processed: severity of 1017552 is important

Processing commands for cont...@bugs.debian.org: > #retried on buildd > severity 1017552 important Bug #1017552 [src:alertmanager-irc-relay] alertmanager-irc-relay: FTBFS on armel Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need

Bug#1017753: autopkgtest-virt-lxc regularly fails to start or return from reboot

Hi On 19-08-2022 21:59, Paul Gevers wrote: The following is seen, but not on every reboot. $ autopkgtest . --apt-upgrade --shell-fail -- lxc --sudo autopkgtest-unstable-amd64 [...] autopkgtest [21:45:36]: rebooting testbed after setup commands that affected boot autopkgtest-virt-lxc

Bug#1017753: autopkgtest-virt-lxc regularly fails to start or return from reboot

Package: autopkgtest Version: 5.24 Severity: serious Dear colleagues, I was just trying to fix some package of mine and was running autopkgtest to see if the hang I see on ci.d.n is reproducible. However, autopkgtest has issues running reliably. Simon already reported this on IRC when releasing

Bug#1017752: nheko: FTBFS on mipsel: virtual memory exhausted: Cannot allocate memory

Source: nheko Version: 0.10.0-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: z...@debian.org https://buildd.debian.org/status/fetch.php?pkg=nheko=mipsel=0.10.0-1=1659971124=0 [ 68%] Building CXX object CMakeFiles/nheko.dir/src/ReadReceiptsModel.cpp.o virtual memory exhausted: Cannot allocate

Processed: bug 1016321 is forwarded to https://github.com/boostorg/boostbook/issues/14

Processing commands for cont...@bugs.debian.org: > forwarded 1016321 https://github.com/boostorg/boostbook/issues/14 Bug #1016321 [src:boost1.74] boost1.74: FTBFS: runtime error: file /<>/tools/boostbook/xsl/annotation.xsl line 432 element element xsl:element: The effective name '' is not a

Bug#1017748: libuv1 breaks siridb-server autopkgtest: test times out

Source: libuv1, siridb-server Control: found -1 libuv1/1.44.2-1 Control: found -1 siridb-server/2.0.45-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of libuv1 the autopkgtest of siridb-server fails

Processed: libuv1 breaks siridb-server autopkgtest: test times out

Processing control commands: > found -1 libuv1/1.44.2-1 Bug #1017748 [src:libuv1, src:siridb-server] libuv1 breaks siridb-server autopkgtest: test times out Marked as found in versions libuv1/1.44.2-1. > found -1 siridb-server/2.0.45-1 Bug #1017748 [src:libuv1, src:siridb-server] libuv1 breaks

Bug#1016940: marked as done (php-luasandbox: flaky autopkgtest: timer pausing and unpausing [tests/timer.phpt])

Your message dated Fri, 19 Aug 2022 19:39:15 + with message-id and subject line Bug#1016940: fixed in php-luasandbox 4.0.2-4 has caused the Debian Bug report #1016940, regarding php-luasandbox: flaky autopkgtest: timer pausing and unpausing [tests/timer.phpt] to be marked as done. This

Bug#1017747: imdbpy: autopkgtest regression: KeyError: 'top 1000 voters'

Source: imdbpy Version: 2021.04.18-3 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer, I happened to look at the results of the autopkgtest of your package and noticed it regressed some months ago. Unfortunately, it went by unnoticed, and the artifacts

Bug#1017739: emacs-lucid cannot start after upgrade

Package: emacs-lucid Version: 1:28.1+1-1 Severity: grave X-Debbugs-Cc: r...@debian.org The 28.1 version of emacs-lucid fails on startup with a cryptic error message: % emacs Cannot find suitable directory for output in ‘comp-native-load-path’. Running emacs -q allows it to start, but it still

Bug#1017554: marked as done (juce-7.0.1~ds0/debian/extra/juce_audio_processors/format_types/juce_VSTInterface.h needs updating for 7.0.1)

Your message dated Fri, 19 Aug 2022 18:34:37 + with message-id and subject line Bug#1017554: fixed in juce 7.0.2~ds0-1 has caused the Debian Bug report #1017554, regarding juce-7.0.1~ds0/debian/extra/juce_audio_processors/format_types/juce_VSTInterface.h needs updating for 7.0.1 to be

Bug#995640: marked as done (boxbackup: FTBFS with OpenSSL 3.0)

Your message dated Fri, 19 Aug 2022 18:19:04 + with message-id and subject line Bug#995640: fixed in boxbackup 0.13~~git20220405.g7703ac8-2 has caused the Debian Bug report #995640, regarding boxbackup: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem

Bug#995640: boxbackup: FTBFS with OpenSSL 3.0

Am 19.08.22 um 16:54 schrieb Ileana Dumitrescu: I fixed the control file email and copyright file in the most recent commits The copyright file is not fixed but I will upload because closing the RC bug is an improvement. Just read the upstream license. The project is dual licensed with GPL

Processed: bug 1004548 is forwarded to https://github.com/RainLoop/rainloop-webmail/issues/2134 ...

Processing commands for cont...@bugs.debian.org: > forwarded 1004548 https://github.com/RainLoop/rainloop-webmail/issues/2134 Bug #1004548 [rainloop] Security Vulnerability /_data_/…/storage/cfg/…/…/accounts Set Bug forwarded-to-address to

Bug#1017616: Unicode

I would agree that this is a package bug. But I think that this is not related to "packaging" only. Upstream too would like to fix the licensing issue in a proper way. Feel free to remove the upstream reference though.

Processed: Cannot reproduce either -- downgrading

Processing control commands: > severity -1 important Bug #1013578 [src:golang-github-prometheus-exporter-toolkit] golang-github-prometheus-exporter-toolkit: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/prometheus/exporter-toolkit/web

Bug#1013578: Cannot reproduce either -- downgrading

Control: severity -1 important Hi, I am also not being able to reproduce this issue, even when setting GOMAXPROC to 1, and since there has been no more activity I am downgrading the severity to prevent the package from being autoremoved. Please, feel free to raise severity again if you can

Bug#1017616: bibledit: Unicode data license violation

This is a package bug only and not relevant for upstream.

Processed: Re: mplayer: FTBFS with ffmpeg 5.0

Processing control commands: > tags -1 patch Bug #1004579 [src:mplayer] mplayer: FTBFS with ffmpeg 5.0 Added tag(s) patch. -- 1004579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1004579: mplayer: FTBFS with ffmpeg 5.0

Package: mplayer Version: 2:1.4+ds1-3 Followup-For: Bug #1004579 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Control: tags -1 patch Dear Maintainer, The upstream release 1.5 supports ffmpeg 5 and would solve this issue. In the meantime, I have attempted to

Bug#1017732: gnuradio: Missing build dependency on cppzmq-dev

Source: gnuradio Version: 3.10.3.0-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=gnuradio=3.10.3.0-3%2Bb1 ... -- Checking for module 'libzmq' -- Found libzmq, version 4.3.4 -- Could NOT find ZeroMQ (missing: ZEROMQ_INCLUDE_DIRS) -- -- Configuring gr-zeromq

Processed: Re: Bug#1017729: cinnamon-l10n: Upgrading to 5.4.2-2 breaks cinnamon

Processing control commands: > severity -1 important Bug #1017729 [cinnamon-l10n] cinnamon-l10n: Upgrading to 5.4.2-2 breaks cinnamon Severity set to 'important' from 'grave' -- 1017729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017729 Debian Bug Tracking System Contact

Bug#1017729: cinnamon-l10n: Upgrading to 5.4.2-2 breaks cinnamon

Control: severity -1 important Il 19/08/2022 17:55, xioren huan ha scritto: Package: cinnamon-l10n Version: 5.4.2-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: xioren00+deb...@protonmail.com Dear Maintainer, Updating cinnamon-l10n from 5.2.2-1 to 5.4.2-2 removes the

Bug#903374: marked as done (tracker: autopkgtest regressed in September 2021)

Your message dated Fri, 19 Aug 2022 16:25:52 + with message-id and subject line Bug#903374: fixed in tracker 3.3.3-1 has caused the Debian Bug report #903374, regarding tracker: autopkgtest regressed in September 2021 to be marked as done. This means that you claim that the problem has been

Bug#1014904: marked as done (Upgrading from 14.9.x to 14.10.5 produces PGSQL errors on some page views)

Your message dated Fri, 19 Aug 2022 16:22:41 + with message-id and subject line Bug#1014904: fixed in gitlab 15.2.2+ds1-4 has caused the Debian Bug report #1014904, regarding Upgrading from 14.9.x to 14.10.5 produces PGSQL errors on some page views to be marked as done. This means that you

Bug#1017284: fenics-dolfinx: FTBFS: CheckSymbolExists.c:8:19: error: ‘PETSC_USE_COMPLEX’ undeclared (first use in this function); did you mean ‘PETSC_HAVE_COMPLEX’?

On Wed, Aug 17, 2022 at 07:31:30PM +0200, Drew Parsons wrote: > Source: fenics-dolfinx > Followup-For: Bug #1017284 > > The cmake error logs can be too effusive, they tend to obscure the > error. In this case the real problem seems to be that it never found > scotch, even though it found it. A

Bug#1017053: marked as done (fenics-dolfinx: FTBFS on mips64el)

Your message dated Fri, 19 Aug 2022 18:06:30 +0200 with message-id and subject line Re: Bug#1017053 fenics-dolfinx: FTBFS on mips64el has caused the Debian Bug report #1017053, regarding fenics-dolfinx: FTBFS on mips64el to be marked as done. This means that you claim that the problem has been

Processed: Bug#903374 marked as pending in tracker

Processing control commands: > tag -1 pending Bug #903374 [src:tracker] tracker: autopkgtest regressed in September 2021 Added tag(s) pending. -- 903374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#903374: marked as pending in tracker

Control: tag -1 pending Hello, Bug #903374 in tracker 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: Forwarded to https://github.com/bibledit/cloud/issues/821

Processing commands for cont...@bugs.debian.org: > forwarded 1017616 https://github.com/bibledit/cloud/issues/821 Bug #1017616 [src:bibledit] bibledit: Unicode data license violation Set Bug forwarded-to-address to 'https://github.com/bibledit/cloud/issues/821'. > thanks Stopping processing here.

Processed: src:restic: fails to migrate to testing for too long: new Build-Depends fails to migrate to testing

Processing control commands: > close -1 0.13.1-1 Bug #1017728 [src:restic] src:restic: fails to migrate to testing for too long: new Build-Depends fails to migrate to testing Marked as fixed in versions restic/0.13.1-1. Bug #1017728 [src:restic] src:restic: fails to migrate to testing for too

Bug#1017728: src:restic: fails to migrate to testing for too long: new Build-Depends fails to migrate to testing

Source: restic Version: 0.12.1-2 Severity: serious Control: close -1 0.13.1-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as

Bug#1017727: autoconf-archive: ax_cc_maxopt.m4 change breaks code due to syntax error

Package: autoconf-archive Version: 20220211-1 Severity: serious Tags: patch Justification: Policy 4.6 m4/ax_cc_maxopt.m4 has a syntax error that causes silo-llnl to FTBFS. See #1017240. The following patch fixes it: --- ax_cc_maxopt.m4.orig2022-08-19 16:13:36.230050352 +0100 +++

Processed: forwarded to https://github.com/bibledit/cloud/issues/820

Processing commands for cont...@bugs.debian.org: > forwarded 1017083 https://github.com/bibledit/cloud/issues/820 Bug #1017083 [src:bibledit] bibledit: Some sources are not included in your package Set Bug forwarded-to-address to 'https://github.com/bibledit/cloud/issues/820'. > thanks Stopping

Bug#1017083: marked as forwarded (bibledit: Some sources are not included in your package)

Your message dated Fri, 19 Aug 2022 17:18:03 +0200 with message-id has caused the report #1017083, regarding bibledit: Some sources are not included in your package to be marked as having been forwarded to the upstream software author(s) (NB: If you are a system administrator and have no

Bug#1017320: marked as done (grads: FTBFS: (.text+0xc8): undefined reference to `libdap::DDS::var_begin()')

Your message dated Fri, 19 Aug 2022 15:19:04 + with message-id and subject line Bug#1017320: fixed in gadap 2.0-15 has caused the Debian Bug report #1017320, regarding grads: FTBFS: (.text+0xc8): undefined reference to `libdap::DDS::var_begin()' to be marked as done. This means that you

Bug#1017083: Forwarded upstream to https://github.com/bibledit/cloud/issues/820

forwarded 1017083 https://github.com/bibledit/cloud/issues/820 thanks

Bug#1017724: libaperture-0: flaky autopkgtest on multiple architectures: timeout_reached: code should not be reached

Source: libaperture-0 Version: 0.1.0+git20200908-3 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky The autopkgtest for libaperture-0 seems to be intermittently failing with a timeout, particularly on armel and armhf. Some examples: -

Bug#995640: boxbackup: FTBFS with OpenSSL 3.0

>> Also please note that .gitattributes makes the repo have an unclean state on checkout when you are not on Windows. >> You should fix that in future uploads by exluding or patching that file or by importing the crlf files with the expected >> line ending. Ok I will look out for that. >> I can

Bug#1017164: marked as done (mpd: FTBFS: ./obj-x86_64-linux-gnu/../src/decoder/plugins/FfmpegIo.cxx:102: undefined reference to `av_malloc(unsigned long)')

Your message dated Fri, 19 Aug 2022 14:43:31 + with message-id and subject line Bug#1017164: fixed in mpd 0.23.9-1 has caused the Debian Bug report #1017164, regarding mpd: FTBFS: ./obj-x86_64-linux-gnu/../src/decoder/plugins/FfmpegIo.cxx:102: undefined reference to `av_malloc(unsigned

Bug#1017107: marked as done (libpmix2: dangling /usr/lib/x86_64-linux-gnu/libpmix.so.2 symlink)

Your message dated Fri, 19 Aug 2022 13:51:34 + with message-id and subject line Bug#1017107: fixed in pmix 4.2.0~rc2-1 has caused the Debian Bug report #1017107, regarding libpmix2: dangling /usr/lib/x86_64-linux-gnu/libpmix.so.2 symlink to be marked as done. This means that you claim that

Bug#1017717: cp2k: FTBFS: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load

Source: cp2k Version: 9.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hello, cp2k fails to build on amd64: cd tools/manual && \ /home/merkys/cp2k-9.1/exe/*/cp2k.psmp --xml && \ saxonb-xslt -o index.html -ext:on cp2k_input.xml cp2k_input.xsl orted: symbol

Bug#1017700: marked as done (libspdlog1.10: Try to overwrite '/usr/lib/x86_64-linux-gnu/libspdlog.so.1.10.0')

Your message dated Fri, 19 Aug 2022 12:55:13 + with message-id and subject line Bug#1017700: fixed in spdlog 1:1.10.0+ds-0.4 has caused the Debian Bug report #1017700, regarding libspdlog1.10: Try to overwrite '/usr/lib/x86_64-linux-gnu/libspdlog.so.1.10.0' to be marked as done. This means

Processed: affects

Processing commands for cont...@bugs.debian.org: > affects 1017698 src:gettext Bug #1017698 [emacs-gtk] emacs-gtk: core dump with unsorted double linked list corrupted Added indication that 1017698 affects src:gettext > thanks Stopping processing here. Please contact me if you need assistance.

Bug#1017698: core dump with unsorted double linked list corrupted

Note: emacs-nox seems also to be affected, as I get a similar error when installing the build-dependencies of gettext: Setting up emacs-nox (1:28.1+1-1) ... update-alternatives: using /usr/bin/emacs-nox to provide /usr/bin/emacs (emacs) in auto mode Install emacsen-common for emacs

Bug#1017425: [PATCH] x86/speculation: Avoid LFENCE in FILL_RETURN_BUFFER on CPUs that lack it

On Fri, Aug 19, 2022 at 01:38:27PM +0200, Ben Hutchings wrote: > So that puts the whole __FILL_RETURN_BUFFER inside an alternative, and > we can't have nested alternatives. That's unfortunate. Well, both alternatives end with the LFENCE instruction, so I could pull it out and do two consequtive

Bug#1017698: gdb backtrace

On 19 août 2022 12:37, Vincent Lefevre wrote: > Hi, > > On 2022-08-19 09:40:55 +0200, Christian Marillat wrote: >> After libc-dbg installation. Do you want more debug ? > > I think that you should install emacs-gtk-dbgsym too. I discovered errors mixed with the apt-get output : 'l'entrée

Bug#1017425: [PATCH] x86/speculation: Avoid LFENCE in FILL_RETURN_BUFFER on CPUs that lack it

On Fri, Aug 19, 2022 at 10:47:21AM +0200, Peter Zijlstra wrote: > On Fri, Aug 19, 2022 at 02:33:08AM +0200, Ben Hutchings wrote: > > From: Ben Hutchings > > > > The mitigation for PBRSB includes adding LFENCE instructions to the > > RSB filling sequence. However, RSB filling is done on some

Bug#1017425: [PATCH] x86/speculation: Avoid LFENCE in FILL_RETURN_BUFFER on CPUs that lack it

On Fri, 2022-08-19 at 13:01 +0200, Peter Zijlstra wrote: > On Fri, Aug 19, 2022 at 10:47:21AM +0200, Peter Zijlstra wrote: > > On Fri, Aug 19, 2022 at 02:33:08AM +0200, Ben Hutchings wrote: > > > From: Ben Hutchings > > > > > > The mitigation for PBRSB includes adding LFENCE instructions to the

Bug#1017425: [PATCH] x86/speculation: Avoid LFENCE in FILL_RETURN_BUFFER on CPUs that lack it

On Fri, Aug 19, 2022 at 2:01 PM Peter Zijlstra wrote: > I'm not entirly sure what to do here. On the one hand, it's 32bit, so > who gives a crap, otoh we shouldn't break these ancient chips either I > suppose. This is something that I've repeatedly had to bring up, whenever something breaks

Processed: Re: systemd: upgrade breaks DNS resolution in some cases

Processing control commands: > severity -1 wishlist Bug #1017713 [systemd] systemd: upgrade breaks DNS resolution in some cases Severity set to 'wishlist' from 'critical' > tags -1 wontfix Bug #1017713 [systemd] systemd: upgrade breaks DNS resolution in some cases Added tag(s) wontfix. > close -1

Bug#1017713: systemd: upgrade breaks DNS resolution in some cases

Control: severity -1 wishlist Control: tags -1 wontfix Control: close -1 On Fri, 19 Aug 2022 13:01:10 +0200 =?UTF-8?Q?Rapha=c3=abl_Halimi?= wrote: > Package: systemd > Version: 251.3-2~exp1 > Severity: critical > > (filing the bug as critical since it "makes unrelated software on the > system

Processed: Re: systemd-resolved: deletes /etc/resolv.conf after package removal

Processing control commands: > severity -1 wishlist Bug #1017714 [systemd-resolved] systemd-resolved: deletes /etc/resolv.conf after package removal Severity set to 'wishlist' from 'critical' > tags -1 wontfix Bug #1017714 [systemd-resolved] systemd-resolved: deletes /etc/resolv.conf after

Bug#1017714: systemd-resolved: deletes /etc/resolv.conf after package removal

Control: severity -1 wishlist Control: tags -1 wontfix Control: close -1 On Fri, 19 Aug 2022 13:01:36 +0200 =?UTF-8?Q?Rapha=c3=abl_Halimi?= wrote: > Package: systemd-resolved > Version: 251.3-2~exp1 > Severity: critical > > (filing the bug as critical since it "makes unrelated software on the >

Bug#1017425: [PATCH] x86/speculation: Avoid LFENCE in FILL_RETURN_BUFFER on CPUs that lack it

On Fri, 2022-08-19 at 10:47 +0200, Peter Zijlstra wrote: > On Fri, Aug 19, 2022 at 02:33:08AM +0200, Ben Hutchings wrote: > > From: Ben Hutchings > > > > The mitigation for PBRSB includes adding LFENCE instructions to the > > RSB filling sequence. However, RSB filling is done on some older CPUs

Bug#1017714: systemd-resolved: deletes /etc/resolv.conf after package removal

Package: systemd-resolved Version: 251.3-2~exp1 Severity: critical (filing the bug as critical since it "makes unrelated software on the system (or the whole system) break", feel free to downgrade) Dear developers, The new systemd-resolved package takes over /etc/resolv.conf, and

Bug#1017713: systemd: upgrade breaks DNS resolution in some cases

Package: systemd Version: 251.3-2~exp1 Severity: critical (filing the bug as critical since it "makes unrelated software on the system (or the whole system) break", feel free to downgrade) Dear developers, A recent update of systemd splits systemd-resolved in its own package, and the new

Bug#1017698: gdb backtrace

On 19 août 2022 12:37, Vincent Lefevre wrote: > Hi, > > On 2022-08-19 09:40:55 +0200, Christian Marillat wrote: >> After libc-dbg installation. Do you want more debug ? > > I think that you should install emacs-gtk-dbgsym too. Here it is : , | Reading symbols from /usr/bin/emacs-gtk... |

Bug#1017698: gdb backtrace

Hi, On 2022-08-19 09:40:55 +0200, Christian Marillat wrote: > After libc-dbg installation. Do you want more debug ? I think that you should install emacs-gtk-dbgsym too. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#1017700: libspdlog1.10: Try to overwrite '/usr/lib/x86_64-linux-gnu/libspdlog.so.1.10.0'

Package: libspdlog-dev Version: 1:1.10.0+ds-0.3 Followup-For: Bug #1017700 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Trying to upgrade packages: am64:/usr/src/linux# aptitude -u Performing actions...

Bug#1017706: marked as done (postgresql-set-user: Boilerplate instead of description in d/control)

Your message dated Fri, 19 Aug 2022 10:06:06 + with message-id and subject line Bug#1017706: fixed in postgresql-set-user 3.0.0-3 has caused the Debian Bug report #1017706, regarding postgresql-set-user: Boilerplate instead of description in d/control to be marked as done. This means that

Bug#1013063: w1retap: diff for NMU version 1.4.6-1.1

On 18 Aug 2022, at 16:39, Adrian Bunk wrote: > I've prepared an NMU for w1retap (versioned as 1.4.6-1.1) and uploaded > it to DELAYED/14. Please feel free to tell me if I should cancel it. Thanks for that Adrain, it's been on my TODO list for far too long. Kind Regards -- Tom

Bug#1017706: marked as pending in postgresql-set-user

Control: tag -1 pending Hello, Bug #1017706 in postgresql-set-user 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#1017706 marked as pending in postgresql-set-user

Processing control commands: > tag -1 pending Bug #1017706 [src:postgresql-set-user] postgresql-set-user: Boilerplate instead of description in d/control Added tag(s) pending. -- 1017706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017706 Debian Bug Tracking System Contact

Bug#1016976: marked as done (connman: CVE-2022-32292 CVE-2022-32293)

Your message dated Fri, 19 Aug 2022 09:48:57 + with message-id and subject line Bug#1016976: fixed in connman 1.41-2 has caused the Debian Bug report #1016976, regarding connman: CVE-2022-32292 CVE-2022-32293 to be marked as done. This means that you claim that the problem has been dealt

Bug#1017425: 5.10.0-17-686-pae: repeatedly crashes during initrd loading [PIII]

On Fri, Aug 19, 2022 at 12:32 PM Etienne Vogt wrote: > > On Thu, 18 Aug 2022, Ben Hutchings wrote: > > >> I suspect someone thought it would be a good idea to compile the kernel > >> for P4 only, as both PIII and Athlon XP processors lack the SSE2 > >> instruction set. > > > > That was a good

Bug#1017425: 5.10.0-17-686-pae: repeatedly crashes during initrd loading [PIII]

On Thu, 18 Aug 2022, Ben Hutchings wrote: I suspect someone thought it would be a good idea to compile the kernel for P4 only, as both PIII and Athlon XP processors lack the SSE2 instruction set. That was a good guess, though we don't change the configuration like that in stable updates.

Bug#1017425: [PATCH] x86/speculation: Avoid LFENCE in FILL_RETURN_BUFFER on CPUs that lack it

On Fri, Aug 19, 2022 at 02:33:08AM +0200, Ben Hutchings wrote: > From: Ben Hutchings > > The mitigation for PBRSB includes adding LFENCE instructions to the > RSB filling sequence. However, RSB filling is done on some older CPUs > that don't support the LFENCE instruction. > Wait; what? There

Processed: bug 1017425 is forwarded to https://lore.kernel.org/lkml/yv7arj%2fsvvhsd...@decadent.org.uk/

Processing commands for cont...@bugs.debian.org: > forwarded 1017425 > https://lore.kernel.org/lkml/yv7arj%2fsvvhsd...@decadent.org.uk/ Bug #1017425 [src:linux] [i386] Unconditional LFENCE instructions in FILL_RETURN_BUFFER Bug #1017494 [src:linux] [i386] Unconditional LFENCE instructions in

Processed: reassign 1012936 to src:juce

Processing commands for cont...@bugs.debian.org: > reassign 1012936 src:juce Bug #1012936 [src:giada] giada: ftbfs with GCC-12 Bug #1015036 [src:giada] giada: FTBFS: pluginHost.h:63:22: error: ‘bool giada::m::PluginHost::Info::getCurrentPosition(juce::AudioPlayHead::CurrentPositionInfo&)’

Bug#1015715: marked as done (src:libtree: fails to migrate to testing for too long: FTBFS on most architectures)

Your message dated Fri, 19 Aug 2022 08:35:22 + with message-id and subject line Bug#1015715: fixed in libtree 3.1.1-2 has caused the Debian Bug report #1015715, regarding src:libtree: fails to migrate to testing for too long: FTBFS on most architectures to be marked as done. This means that

Bug#1017706: postgresql-set-user: Boilerplate instead of description in d/control

Source: postgresql-set-user Version: 3.0.0-2 Severity: serious Justification: Policy 5.6.13 Hi, your package is missing a description. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64)

Bug#1016321: boost1.74: FTBFS: runtime error: file /<>/tools/boostbook/xsl/annotation.xsl line 432 element element xsl:element: The effective name '' is not a valid QName.

Hi, On Thu, 18 Aug 2022 15:32:41 +0200 Giovanni Mascellani wrote:> If you still have version 1.1.34 (or downgrade), then everything will work and the output file output.boostbook will be generated (a couple of warnings will be printed, but they are not problematic; or, at least, they are a

Processed: retitle 1017579 to Freeciv < 2.6.7, freeciv-3.0 < 3.0.3, Modpack Installer buffer overflow

Processing commands for cont...@bugs.debian.org: > retitle 1017579 Freeciv < 2.6.7, freeciv-3.0 < 3.0.3, Modpack Installer > buffer overflow Bug #1017579 [src:freeciv] freeciv: freeciv modpack installer buffer overflow Changed Bug title to 'Freeciv < 2.6.7, freeciv-3.0 < 3.0.3, Modpack Installer

Processed: retitle 1017579 to freeciv: freeciv modpack installer buffer overflow

Processing commands for cont...@bugs.debian.org: > retitle 1017579 freeciv: freeciv modpack installer buffer overflow Bug #1017579 [src:freeciv] freeciv: modpack installer buffer overflow Changed Bug title to 'freeciv: freeciv modpack installer buffer overflow' from 'freeciv: modpack installer

Bug#1017698: gdb backtrace

On 19 août 2022 06:33, "Debian Bug Tracking System" wrote: Hi, After libc-dbg installation. Do you want more debug ? , | Reading symbols from /usr/bin/emacs-gtk... | (No debugging symbols found in /usr/bin/emacs-gtk) | [New LWP 160070] | [New LWP 160071] | [Thread debugging using

Bug#1017700: libspdlog1.10: Try to overwrite '/usr/lib/x86_64-linux-gnu/libspdlog.so.1.10.0'

Package: libspdlog1.10 Version: 1:1.10.0+ds-0.3 Severity: serious Dear Maintainer, sudo pat-get dist-upgrade Preparing to unpack .../libspdlog1.10_1%3a1.10.0+ds-0.3_amd64.deb ... Unpacking libspdlog1.10:amd64 (1:1.10.0+ds-0.3) ... dpkg: error processing archive

Processed: retitle 1017698 to emacs-gtk: core dump with unsorted double linked list corrupted

Processing commands for cont...@bugs.debian.org: > retitle 1017698 emacs-gtk: core dump with unsorted double linked list > corrupted Bug #1017698 [emacs-gtk] emacsen-common: core dump with unsorted double linked list corrupted Changed Bug title to 'emacs-gtk: core dump with unsorted double

Processed: Re: Bug#1017698: Acknowledgement (emacsen-common: core dump with unsorted double linked list corrupted)

Processing commands for cont...@bugs.debian.org: > reassign 1017698 emacs-gtk Bug #1017698 [emacsen-common] emacsen-common: core dump with unsorted double linked list corrupted Bug reassigned from package 'emacsen-common' to 'emacs-gtk'. No longer marked as found in versions

Bug#1017698: Acknowledgement (emacsen-common: core dump with unsorted double linked list corrupted)

reassign 1017698 emacs-gtk thanks On 19 août 2022 06:33, "Debian Bug Tracking System" wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1017698: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017698. Filled against the wrong

Bug#1017698: emacsen-common: core dump with unsorted double linked list corrupted

Package: emacsen-common Version: 3.0.4 Severity: grave Dear Maintainer, After an apt-get dist-upgrade Setting up emacs-gtk (1:28.1+1-1) ... Install a2ps for emacs Install bbdb3 for emacs Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs malloc(): unsorted