Your message dated Sun, 19 Nov 2023 06:04:37 +
with message-id
and subject line Bug#1054909: fixed in activemq 5.17.6+dfsg-1
has caused the Debian Bug report #1054909,
regarding activemq: CVE-2023-46604
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 19 Nov 2023 00:34:00 +
with message-id
and subject line Bug#1042853: fixed in docknot 7.01-2
has caused the Debian Bug report #1042853,
regarding docknot: FTBFS with Perl 5.38: t/spin/errors.t failure
to be marked as done.
This means that you claim that the problem
On Sat, 18 Nov 2023 16:21:57 -0800, Russ Allbery wrote:
> > in the light of #1055955 (perl5.38 transition bug) -- do you think
> > you can upload a fixed version (the current version plus a patch or a
> > new release) in the near future, or should I upload an NMU with your
> > upstream commit or
gregor herrmann writes:
> On Wed, 06 Sep 2023 08:21:24 -0700, Russ Allbery wrote:
>> gregor herrmann writes:
>>> According to https://github.com/rra/docknot/issues/6 fixed upstream
>>> (in git, not released yet).
>> Yeah, I'm sorry about the delay here. I'm trying to get a new release
>> out
Package: tex-common
Version: 6.18
Followup-For: Bug #1051243
Dear Maintainer,
This issue is still present in current Sid.
Setting up tex-common (6.18) ...
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ...
Root cause found, merge request here:
https://salsa.debian.org/kernel-team/linux/-/merge_requests/917
Processing commands for cont...@bugs.debian.org:
> reopen 1051243
Bug #1051243 {Done: Hilmar Preuße } [tex-common] tex-common:
fmtutil failed on tex-common upgrade
Bug reopened
Ignoring request to alter fixed versions of bug #1051243 to the same values
previously set
> thanks
Stopping
Processing commands for cont...@bugs.debian.org:
> forwarded 1032104
> https://lore.kernel.org/linuxppc-dev/1105090647.48374193.1700351103830.javamail.zim...@raptorengineeringinc.com/T/#u
>
>
Processing control commands:
> severity -1 important
Bug #1056204 [release.debian.org] nmu: texlive-bin_2023.20230311.66589-7
Severity set to 'important' from 'normal'
> block 1056183 by -1
Bug #1056183 [texlive-binaries] texlive-luatex: lualatex exits immediately due
to new zlib
Bug #1056186
Your message dated Sat, 18 Nov 2023 21:37:36 +
with message-id
and subject line Bug#1056108: fixed in systemd 255~rc2-2
has caused the Debian Bug report #1056108,
regarding v255 breaks boot with dracut
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> tag -1 pending
Bug #1056108 [systemd] v255 breaks boot with dracut
Added tag(s) pending.
--
1056108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1056108 in systemd 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:
I will not engage any more with debian-r. But this is now at the BTS so a
clarification may be in order. This started as I had sent an email as a
heads-up to fellow maintainers (via that mostly pointless list) informing
them that their packages would exhibit a bug following a bug in package
Processing control commands:
> affects -1 ibus-table
Bug #1051243 [tex-common] tex-common: fmtutil failed on tex-common upgrade
Added indication that 1051243 affects ibus-table
> severity -1 serious
Bug #1051243 [tex-common] tex-common: fmtutil failed on tex-common upgrade
Severity set to
Processing commands for cont...@bugs.debian.org:
> # see the Perl 5.38 transition bug #1055955
> severity 1042521 serious
Bug #1042521 [src:polymake] polymake: FTBFS with Perl 5.38: ‘Perl_ck_fun’ was
not declared in this scope
Severity set to 'serious' from 'important'
> block 1055955 with
Am Fri, Nov 17, 2023 at 12:52:29PM -0600 schrieb Dirk Eddelbuettel:
> | Anyway. Now that you made it a bug I let you drive this. Upstream just made
> | an unrelated bugfix Matrix 1.6-3 which I just sent to unstable.
>
> There are two known failures left which the maintainer(s) do not want to
On Fri, Nov 17, 2023 at 06:28:30PM +0100, gregor herrmann wrote:
> Source: libeval-context-perl
> Version: 0.09.11-5
> Severity: serious
> Tags: ftbfs trixie sid
> Justification: fails to build from source
> As noted by ci.debian.net, t/012_safe.t started to fail recently:
This seems to have
Source: benchmark
Version: 1.7.1-1
Severity: serious
Control: close -1 1.8.3-1
Tags: sid trixie
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 30 days as
Processing control commands:
> close -1 1.8.3-1
Bug #1056202 [src:benchmark] src:benchmark: fails to migrate to testing for too
long: triggers autopkgtest issues
Marked as fixed in versions benchmark/1.8.3-1.
Bug #1056202 [src:benchmark] src:benchmark: fails to migrate to testing for too
long:
Processing control commands:
> close -1 2.2-1
Bug #1056199 [src:procdump] src:procdump: fails to migrate to testing for too
long: FTBFS on armel, mips64el and ppc64el
Marked as fixed in versions procdump/2.2-1.
Bug #1056199 [src:procdump] src:procdump: fails to migrate to testing for too
long:
Source: procdump
Version: 1.2-4
Severity: serious
Control: close -1 2.2-1
Tags: sid trixie ftbfs
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 30 days as
Source: setuptools
Version: 68.1.2-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package: it Build-Depends
on dh-python, which Depends on python3-setuptools, but
Processing control commands:
> close -1 2:9.0.2103-1
Bug #1056197 [src:vim] src:vim: fails to migrate to testing for too long: FTBFS
on armel
Marked as fixed in versions vim/2:9.0.2103-1.
Bug #1056197 [src:vim] src:vim: fails to migrate to testing for too long: FTBFS
on armel
Marked Bug as done
Source: vim
Version: 2:9.0.1894-1
Severity: serious
Control: close -1 2:9.0.2103-1
Tags: sid trixie ftbfs
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
Processing commands for cont...@bugs.debian.org:
> close 1052972 2.0-3
Bug #1052972 [src:pg-auto-failover] pg-auto-failover: FTBFS: Error:
debian/control needs updating from debian/control.in. Run 'pg_buildext
updatecontrol'.
Marked as fixed in versions pg-auto-failover/2.0-3.
Bug #1052972
Hi Lorenzo,
On Sat, Nov 18, 2023 at 03:26:37PM +0100, Lorenzo wrote:
> Could you please clarify how this is blocking the usrmerge transition,
> besides runit itself missing a trigger?
This is not blocking the transition. I don't see how deferring a runit
update could impact unrelated aspects.
Your message dated Sat, 18 Nov 2023 16:19:07 +
with message-id
and subject line Bug#1055414: fixed in bedtools 2.31.0+dfsg-2
has caused the Debian Bug report #1055414,
regarding bedtools: FTBFS on i386: "intersect" tool failure
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 18 Nov 2023 15:51:43 +
with message-id
and subject line Bug#1056185: fixed in gi-docgen 2023.1+ds-5
has caused the Debian Bug report #1056185,
regarding /usr/lib/python3/dist-packages/gidocgen/gir/ast.py: Debian specific
multiarch detection fails when called outside
Processing control commands:
> tag -1 pending
Bug #1055414 [src:bedtools] bedtools: FTBFS on i386: "intersect" tool failure
Added tag(s) pending.
--
1055414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1055414 in bedtools 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:
Control: tag -1 pending
Hello,
Bug #1056185 in gi-docgen 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:
Processing control commands:
> tag -1 pending
Bug #1056185 [gi-docgen] /usr/lib/python3/dist-packages/gidocgen/gir/ast.py:
Debian specific multiarch detection fails when called outside of dpkg build
Ignoring request to alter tags of bug #1056185 to the same tags previously set
--
1056185:
Processing control commands:
> severity -1 grave
Bug #1056189 [texlive-binaries] luahbtex: PANIC: unprotected error in call to
Lua API (zlib library version does not match - header: 1.2.13, library: 1.3)
Severity set to 'grave' from 'important'
> merge -1 1056186
Bug #1056189 [texlive-binaries]
Your message dated Sat, 18 Nov 2023 15:17:57 +
with message-id
and subject line Bug#1052002: fixed in llvm-toolchain-16 1:16.0.6-18
has caused the Debian Bug report #1052002,
regarding wasmedge: autopkgtest regression: 'cstdint' file not found
to be marked as done.
This means that you claim
Your message dated Sat, 18 Nov 2023 15:17:57 +
with message-id
and subject line Bug#1052002: fixed in llvm-toolchain-16 1:16.0.6-18
has caused the Debian Bug report #1052002,
regarding C++ compilation for wasm32-wasi broken due to missing include paths
to be marked as done.
This means that
Hello Hilmar, thanks for your prompt reply.
To clarify things,
the message is not only irritating but also aborting:
the package tex-common cannot currently configure.
Best wishes,
Jerome
PS: I merged my report with the first report,
and I redirected the first report to texlive-binaries.
On
Processing commands for cont...@bugs.debian.org:
> severity 1056185 serious
Bug #1056185 [gi-docgen] /usr/lib/python3/dist-packages/gidocgen/gir/ast.py:
Debian specific multiarch detection fails when called outside of dpkg build
Severity set to 'serious' from 'normal'
> thanks
Stopping
On 18.11.2023 15:42, Jerome BENOIT wrote:
Hi,
To clarify things,
the message is not only irritating but also aborting:
the package tex-common cannot currently configure.
I'm aware of this: the other user reported a core dump and in our output
an aborted message is visible. Therefore I'm
Your message dated Sat, 18 Nov 2023 14:37:34 +
with message-id
and subject line Bug#1042667: fixed in poezio 0.14-3
has caused the Debian Bug report #1042667,
regarding poezio: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: ***
[debian/rules:28: override_dh_auto_build] Error 2
to be marked
On 18.11.2023 14:57, Jerome Benoit wrote:
Hi,
Hi, the issue appeared to me within a Sid schroot environment
at postinstallation time of tex-common.
I traced it back to texlive-binaries by looking the logfile at
the fmutils stage. The issue seems to originate from the recent migration
from zlib
Hi Helmut,
On Sat, 18 Nov 2023 09:19:46 +0100
Helmut Grohne wrote:
> Control: severity -1 serious
>
Could you please clarify how this is blocking the usrmerge transition,
besides runit itself missing a trigger?
Lorenzo
> I am raising the bug about missing trigger interest to severity
>
Processing commands for cont...@bugs.debian.org:
> merge 1056183 1056186
Bug #1056183 [texlive-binaries] texlive-luatex: lualatex exits immediately due
to new zlib
Bug #1056183 [texlive-binaries] texlive-luatex: lualatex exits immediately due
to new zlib
Marked as found in versions
Processing commands for cont...@bugs.debian.org:
> severity 1056183 grave
Bug #1056183 [texlive-luatex] texlive-luatex: lualatex exits immediately due to
new zlib
Severity set to 'grave' from 'important'
> reassign 1056183 texlive-binaries
Bug #1056183 [texlive-luatex] texlive-luatex: lualatex
Package: texlive-binaries
Version: 2023.20230311.66589-7
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: calcu...@rezozer.net
Hi, the issue appeared to me within a Sid schroot environment
at postinstallation time of tex-common.
I traced it back to texlive-binaries by
Source: python-ase
Version: 3.22.1-3
Severity: serious
Tags: ftbfs
Dear maintainer:
During an incremental rebuild of all packages in trixie,
this package failed to build:
[...]
/<>/doc/about.rst:51: ERROR: Broken link: :git:`COPYING`:
Non-existing path: ../COPYING
/<>/doc/about.rst:51: ERROR:
Processing commands for cont...@bugs.debian.org:
> close 1056163 0.9.0~hg4144-1
Bug #1056163 [libervia-backend] libervia-backend: start fails without
pre-existing configuration
Ignoring request to alter fixed versions of bug #1056163 to the same values
previously set
Bug #1056163
Hello Jonas,
On Sat, Nov 18, 2023 at 10:31:56AM +0100, Jonas Smedegaard wrote:
> Package: librust-tikv-jemalloc-ctl-dev
> Version: 0.5.4-1
> Severity: grave
> Justification: renders package unusable
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Depends on packages
Your message dated Sat, 18 Nov 2023 10:04:12 +
with message-id
and subject line Bug#1055990: fixed in geany-plugins 2.0-4
has caused the Debian Bug report #1055990,
regarding geany-plugins: FTBFS with build=all
to be marked as done.
This means that you claim that the problem has been dealt
Package: librust-tikv-jemalloc-ctl-dev
Version: 0.5.4-1
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Depends on packages librust-tikv-jemalloc-sys-0.5+default-dev and
librust-tikv-jemalloc-sys-0.5+disable-initial-exec-tls-dev that are
Processing control commands:
> severity -1 serious
Bug #1043419 {Done: Lorenzo Puliti } [runit] runit:
ineffective trigger interest due to /usr-merge
Severity set to 'serious' from 'important'
--
1043419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043419
Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:
> forwarded 1052975 https://github.com/phillord/assess/issues/19
Bug #1052975 [src:assess-el] assess-el: FTBFS: make: *** [debian/rules:4:
binary] Error 25
Set Bug forwarded-to-address to 'https://github.com/phillord/assess/issues/19'.
> forwarded
51 matches
Mail list logo
