On 2025-01-16 12:00:39 +0530, Pushkar Kulkarni wrote:
> I have raised an MR [1] with patches backported from upstream. I modified
> one of the patches. I also proposed the update upstream.
We are in the process of preparing a new upstream release. I will update
the Debian package afterwards.
Chee
Processing commands for cont...@bugs.debian.org:
> forwarded 1093086 https://github.com/rdkit/rdkit/issues/8172
Bug #1093086 [src:rdkit] rdkit: FTBFS on big-endian architectures
Set Bug forwarded-to-address to 'https://github.com/rdkit/rdkit/issues/8172'.
> thanks
Stopping processing here.
Please
forwarded 1093086 https://github.com/rdkit/rdkit/issues/8172
thanks
Hi,
On Thu, Jan 16, 2025 at 09:39:08AM +0200, Andrius Merkys wrote:
> However, the issue with FTBFS on big-endian architectures persists.
Yeah :-/
> We may have to drop the support for big-endians as well.
I opened an upstream
Processing control commands:
> found -1 202409.4-1
Bug #1093086 [src:rdkit] rdkit: FTBFS on big-endian architectures
Marked as found in versions rdkit/202409.4-1.
--
1093086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with p
Control: found -1 202409.4-1
Hi Michael,
On 2025-01-15 19:44, Michael Banck wrote:
I did not have a problem building it, so I uploaded 202409.4-1, let's
see how that one goes on the autobuilders.
Thanks a lot for uploading 202409.4-1. Interestingly, the problem with
'convert' does not resurf
Source: py-libzfs
Version: 0.0+git20240510.5ae7d5e-1
Severity: serious
Control: block 1067200 by -1
Your package build-depends or depends on cython-legacy, which was
requested to be removed.
Please switch away from cython-legacy ASAP.
Note that cython-legacy is blocked from re-entering testing, s
Guillem,
Can you help here?
Background: I implemented DPKG_FORCE conf{def,ask,new,old} support in ucf[1].
Chris opened this bug as there was an issue with confdef handling (now
resolved). But a side issue has arisen regarding the interpretation of the
options in dpkg(1).
As you will see, FAI spe
Processing commands for cont...@bugs.debian.org:
> # PHPUnit11 seems like it is Trixie or later
> tags 1092117 sid trixie experimental
Bug #1092117 {Done: David Prévot } [symfony] php-pimple:
debci failure with PHPUnit 11
Added tag(s) trixie.
> thanks
Stopping processing here.
Please contact me
Processing control commands:
> block 1067200 by -1
Bug #1067200 [ftp.debian.org] RM: cython-legacy -- ROM; Legacy transition
package no longer needed
1067200 was blocked by: 1076515 1089717 1092776 1092777 1092778 1092779 1092780
1092781 1092782 1092783 1092784 1092785 1092786
1067200 was not bl
Processing commands for cont...@bugs.debian.org:
> block 1087970 with 1093170
Bug #1087970 [src:pep8] pep8: old version of pycodestyle
1087970 was blocked by: 949937 1092997 1093039 1093078 1093079 1093080
1087970 was not blocking any bugs.
Added blocking bug(s) of 1087970: 1093170
> thanks
Stoppi
Your message dated Thu, 16 Jan 2025 07:05:14 +
with message-id
and subject line Bug#1092091: fixed in sbuild 0.88.2
has caused the Debian Bug report #1092091,
regarding sbuild: autopkgtests fail with new dpkg - test-pkg is not "R³:no"-safe
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> # PHPUnit11 seems like it is Trixie or later
> tags 1092117 sid testing experimental
Unknown tag/s: testing.
Recognized are: patch wontfix moreinfo unreproducible help security upstream
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixe
I have raised an MR [1] with patches backported from upstream. I modified
one of the patches. I also proposed the update upstream.
[1] https://salsa.debian.org/sramacher/bpython/-/merge_requests/3
Hi,
Quoting Stéphane Glondu (2025-01-16 04:55:00)
> Le 15/01/2025 à 11:41, Johannes Schauer Marin Rodrigues a écrit :
> > sorry that you ran into this. This one was already filed as #1092479 but
> > since
> > that bug was not tagged as "ftbfs" it doesn't show up in tools like debftbfs
> > and cau
Your message dated Thu, 16 Jan 2025 06:04:54 +
with message-id
and subject line Bug#1092956: fixed in progress-linux-metapackages 20221002-21
has caused the Debian Bug report #1092956,
regarding progress-linux-container: incorrect --rename flags in duplicated
diversions (DEP17)
to be marked a
Your message dated Thu, 16 Jan 2025 06:04:14 +
with message-id
and subject line Bug#1092955: fixed in bfh-metapackages 20211009-32
has caused the Debian Bug report #1092955,
regarding bfh-metapackages: incorrect --rename flags in duplicated diversions
(DEP17)
to be marked as done.
This means
Processing control commands:
> tags -1 + moreinfo
Bug #1093160 [rsync] rsync: failed verification -- update discarded
Added tag(s) moreinfo.
--
1093160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + moreinfo
Hi Vincent,
On Wed, Jan 15, 2025 at 11:38:12PM +0100, Vincent Lefevre wrote:
> On 2025-01-15 23:30:22 +0100, Vincent Lefevre wrote:
> > When updated a directory with "rsync -KRlptzv --progress",
> > I now get errors like
> >
> > ERROR: public_html/cine/index.fr.html f
Processing commands for cont...@bugs.debian.org:
> unarchive 307575
Bug #307575 {Done: Moritz Muehlenhoff } [sqwebmail] cross-site
scripting attack via redirect parameter (CAN-2005-1308)
Unarchived Bug 307575
> notfound 307575 0.47-4
Bug #307575 {Done: Moritz Muehlenhoff } [sqwebmail] cross-site
Hi,
Le 15/01/2025 à 11:41, Johannes Schauer Marin Rodrigues a écrit :
sorry that you ran into this. This one was already filed as #1092479 but since
that bug was not tagged as "ftbfs" it doesn't show up in tools like debftbfs
and caused you needless time and effort, sorry for that. I should've t
Your message dated Thu, 16 Jan 2025 11:17:52 +0800
with message-id <97fe2a3a-51cd-4cd2-b866-b4a34fc7f...@isrc.iscas.ac.cn>
and subject line Re: gcc-14-cross-mipsen: FTBFS with make 4.4.1
has caused the Debian Bug report #1089262,
regarding gcc-14-cross-mipsen: FTBFS with make 4.4.1
to be marked as
On Thu, 16 Jan 2025, Luca Boccassi wrote:
>This is an anti-pattern, and best avoided. What's the problem if the
>script runs twice? If it just detects things it should be just fine,
Extra effort, though. And, in general, TOCTOU, but probably not
applicable here.
bye,
//mirabilos
--
den AGP ste
On Wed, 15 Jan 2025 at 23:12, Sven Geuer wrote:
>
> On Wed, 2025-01-15 at 20:28 +0100, Thorsten Glaser wrote:
> > On Wed, 15 Jan 2025, Sven Geuer wrote:
> >
> > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504044#162
> >
> > > Applying ExecCondition to me seems the most reasonable solutio
Your message dated Thu, 16 Jan 2025 00:49:16 +
with message-id
and subject line Bug#1074854: fixed in brasero 3.12.3-3
has caused the Debian Bug report #1074854,
regarding brasero: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> close 1087426 0.20.0+ds-2.1
Bug #1087426 [src:jsonnet] jsonnet: Python 3.13 build fails silently
Marked as fixed in versions jsonnet/0.20.0+ds-2.1.
Bug #1087426 [src:jsonnet] jsonnet: Python 3.13 build fails silently
Marked Bug as done
> thanks
St
Your message dated Thu, 16 Jan 2025 00:19:20 +
with message-id
and subject line Bug#1086096: fixed in courier 1.3.13-1
has caused the Debian Bug report #1086096,
regarding Replace obsolete Build-Depends: libidn11-dev with libidn-dev
to be marked as done.
This means that you claim that the pro
Your message dated Thu, 16 Jan 2025 00:19:20 +
with message-id
and subject line Bug#153: fixed in courier 1.3.13-1
has caused the Debian Bug report #153,
regarding courier: depends on obsolete pcre3 library
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Thu, 16 Jan 2025 00:19:20 +
with message-id
and subject line Bug#989375: fixed in courier 1.3.13-1
has caused the Debian Bug report #989375,
regarding courier: CVE-2021-38084
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Your message dated Thu, 16 Jan 2025 00:19:20 +
with message-id
and subject line Bug#1069307: fixed in courier 1.3.13-1
has caused the Debian Bug report #1069307,
regarding FTBFS: configure: error: must specify --with-locking-method option
to be marked as done.
This means that you claim that t
Your message dated Thu, 16 Jan 2025 00:19:20 +
with message-id
and subject line Bug#153: fixed in courier 1.3.13-1
has caused the Debian Bug report #153,
regarding courier: depends on obsolete pcre3 library
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Wed, 15 Jan 2025 23:52:30 +
with message-id
and subject line Bug#1091123: fixed in gnucash 1:5.10-0.1
has caused the Debian Bug report #1091123,
regarding gnucash: FTBFS: gnucash_core.c:10892:19: error: too few arguments to
function ‘SWIG_Python_AppendOutput’
to be marked a
Your message dated Wed, 15 Jan 2025 23:52:30 +
with message-id
and subject line Bug#1091409: fixed in gnucash 1:5.10-0.1
has caused the Debian Bug report #1091409,
regarding gnucash: FTBFS: gnucash_core.c:10892:19: error: too few arguments to
function ‘SWIG_Python_AppendOutput’
to be marked a
Your message dated Wed, 15 Jan 2025 23:52:30 +
with message-id
and subject line Bug#1091123: fixed in gnucash 1:5.10-0.1
has caused the Debian Bug report #1091123,
regarding gnucash FTBFS with Python 3.13 as default
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Wed, 15 Jan 2025 23:52:30 +
with message-id
and subject line Bug#1091409: fixed in gnucash 1:5.10-0.1
has caused the Debian Bug report #1091409,
regarding gnucash FTBFS with Python 3.13 as default
to be marked as done.
This means that you claim that the problem has been dea
On Thu, 16 Jan 2025, Sven Geuer wrote:
>> If not, I’d lean towards one (which?) of the errorlevel-using ones,
>> because otherwise we’d have to run the detection code twice.
>
>Not sure what you mean by 'one of the errorlevel-using ones'. Please
>explain your idea in more details.
SuccessExitStat
Your message dated Wed, 15 Jan 2025 16:33:01 -0700
with message-id <3525644.uBEoKPz9u1@soren-desktop>
and subject line the stretch-pu: package courier/0.76.3-5+deb9u1 still are
broken
has caused the Debian Bug report #979545,
regarding the stretch-pu: package courier/0.76.3-5+deb9u1 still are brok
Your message dated Wed, 15 Jan 2025 23:22:58 +
with message-id
and subject line Bug#1091398: fixed in osmo-tetra 0.0~git20230902.c0956b9-2
has caused the Debian Bug report #1091398,
regarding osmo-tetra and uml-utilities have an undeclared file conflict on
/usr/bin/tunctl
to be marked as done
On 2025-01-11 16:21:43 +0100, mister...@web.de wrote:
> Control: found -1 3.0.1+ds-1
>
> Hi,
>
> I'm just adding a package version to this bug, so that people using
> apt-listbugs may be warned about this.
No, this has no effect for the tex-common upgrade: I've just got
hit by this bug and got n
Your message dated Wed, 15 Jan 2025 23:19:23 +
with message-id
and subject line Bug#1074674: fixed in buildstream 1.6.9-1.1
has caused the Debian Bug report #1074674,
regarding buildstream: FTBFS: AttributeError: module 'configparser' has no
attribute 'SafeConfigParser'. Did you mean: 'RawCon
Hi Ian,
On Wed, Jan 15, 2025 at 07:29:54PM +, Ian Jackson wrote:
> It seems that current faketime in sid is capable of persuading
> xapian-omega's upstream tests that faketime is working, but does not
> actually manage to fake it well enough:
>
> 40s expected: «Query((Y2000 ... Y2014 OR M2
On Wed, 2025-01-15 at 20:28 +0100, Thorsten Glaser wrote:
> On Wed, 15 Jan 2025, Sven Geuer wrote:
>
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504044#162
>
> > Applying ExecCondition to me seems the most reasonable solution to this
> > bug.
>
> Can the script behind ExecCondition p
Dear Maintainer,
After applying this commit [1], I was able to build your package in
a sid chroot environment and autopkgtests pass as well.
Kind Regards
[1]
https://git.launchpad.net/ufw/commit/?id=b129ab51e701af22dd5a046864f0d8a65252c669
Your message dated Wed, 15 Jan 2025 22:53:25 +
with message-id
and subject line Bug#1093156: fixed in ucf 3.0048
has caused the Debian Bug report #1093156,
regarding ucf: Unable to determine DPKG_FORCE keep file; aborts installation
to be marked as done.
This means that you claim that the pro
Your message dated Wed, 15 Jan 2025 22:51:55 +
with message-id
and subject line Bug#1093011: fixed in music 1.2.1-0.7
has caused the Debian Bug report #1093011,
regarding music FTBFS on 32-bit
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Wed, 15 Jan 2025 22:52:12 +
with message-id
and subject line Bug#1086473: fixed in nx-libs 2:3.5.99.27-2
has caused the Debian Bug report #1086473,
regarding nx-libs FTBFS on 32-bit with gcc 14
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> tags 1091161 + upstream
Bug #1091161 [g++-14] g++14/g++-15 arm64 regression: ICE in
simplify_context::simplify_subreg()
Added tag(s) upstream.
> forwarded 1091161 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118501
Bug #1091161 [g++-14] g++14/g++
On 2025-01-15 23:30:22 +0100, Vincent Lefevre wrote:
> When updated a directory with "rsync -KRlptzv --progress",
> I now get errors like
>
> ERROR: public_html/cine/index.fr.html failed verification -- update discarded.
> ERROR: public_html/cine/perso-lyon.txt failed verification -- update
> dis
Control: tag -1 pending
Hello,
Bug #1086473 in nx-libs 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/debian-remote-team/nx-libs/-/commit/93d2f16a50fb5b954ab20
Processing control commands:
> tag -1 pending
Bug #1086473 [src:nx-libs] nx-libs FTBFS on 32-bit with gcc 14
Added tag(s) pending.
--
1086473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: rsync
Version: 3.3.0+ds1-2
Severity: grave
Justification: renders package unusable
When updated a directory with "rsync -KRlptzv --progress",
I now get errors like
ERROR: public_html/cine/index.fr.html failed verification -- update discarded.
ERROR: public_html/cine/perso-lyon.txt failed
> This also caught my eye:
>
> > $ podman run -it --rm debian:unstable apt --update install -y -o
> > Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confnew
> > --allow-change-held-packages nfs-common
>
> Why both --force-confnew and --force-confdef? My reading of dpkg(1) sugges
* Mark Hindley [250115 22:25]:
> On Wed, Jan 15, 2025 at 09:48:35PM +0100, Chris Hofstaedtler wrote:
> > Judging by the message, this is probably caused by the new
> > DPKG_FORCE support in ucf.
>
> Yes. Can you verify the patch below fixes for you?
Yes, the patch makes it work.
> This also cau
Processing commands for cont...@bugs.debian.org:
> # gettext 0.23.1 is in unstable now
> severity 1092225 serious
Bug #1092225 [src:ganyremote] ganyremote: FTBFS with gettext 0.23.x
Severity set to 'serious' from 'important'
> severity 1092227 serious
Bug #1092227 [src:grig] grig: FTBFS with gette
Your message dated Wed, 15 Jan 2025 21:31:37 +
with message-id
and subject line Bug#1092871: fixed in onboard 1.4.1-10
has caused the Debian Bug report #1092871,
regarding FTBFS on riscv64: AssertionError: Lists differ: [['en_US.lm', 1]] !=
[['user.lm', 1]]
to be marked as done.
This means t
Processing control commands:
> tags -1 patch
Bug #1093156 [ucf] ucf: Unable to determine DPKG_FORCE keep file; aborts
installation
Added tag(s) patch.
--
1093156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 patch
Chris,
Thanks.
On Wed, Jan 15, 2025 at 09:48:35PM +0100, Chris Hofstaedtler wrote:
> Judging by the message, this is probably caused by the new
> DPKG_FORCE support in ucf.
Yes. Can you verify the patch below fixes for you?
This also caught my eye:
> $ podman run -it
Your message dated Wed, 15 Jan 2025 21:06:21 +
with message-id
and subject line Bug#1092936: fixed in agg 1:2.7.0.r145+dfsg-2
has caused the Debian Bug report #1092936,
regarding wrong package name in symbols file
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 15 Jan 2025 21:06:21 +
with message-id
and subject line Bug#1092936: fixed in agg 1:2.7.0.r145+dfsg-2
has caused the Debian Bug report #1092936,
regarding Linked packages depends on libagg2 (>= 2.6.0) but it is not
installable
to be marked as done.
This means that you
Your message dated Wed, 15 Jan 2025 21:06:21 +
with message-id
and subject line Bug#1092915: fixed in agg 1:2.7.0.r145+dfsg-2
has caused the Debian Bug report #1092915,
regarding wrong package name in symbols file
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 15 Jan 2025 21:06:21 +
with message-id
and subject line Bug#1092915: fixed in agg 1:2.7.0.r145+dfsg-2
has caused the Debian Bug report #1092915,
regarding Linked packages depends on libagg2 (>= 2.6.0) but it is not
installable
to be marked as done.
This means that you
Package: cumin
Version: 4.2.0-1
Severity: grave
cumin is currently completely broken in trixie:
anarcat@angela:~> cumin '*' 'uptime'
Caught AttributeError exception: type object 'GreenSocket' has no attribute
'sendmsg'
anarcat@angela:~[99]>
Not sure what's going on here, it might be related to
Package: ucf
Version: 3.0047
Severity: serious
Control: affects -1 nfs-common
X-Debbugs-CC: t...@grml.org, nfs-com...@packages.debian.org
Dear ucf maintainer,
since today the Grml Live image builds fail while installing
nfs-common, with this error:
Setting up nfs-common (1:2.8.2-1) ...
ucf:
Processing control commands:
> affects -1 nfs-common
Bug #1093156 [ucf] ucf: Unable to determine DPKG_FORCE keep file; aborts
installation
Added indication that 1093156 affects nfs-common
--
1093156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093156
Debian Bug Tracking System
Contact ow
Hi Bo,
On Mi 15 Jan 2025 16:24:55 CET, Bo YU wrote:
Control: tags -1 patch
Hi,
On Sun, Jan 12, 2025 at 08:42:29PM +0500, Andrey Rakhmatullin wrote:
Source: onboard
Version: 1.4.1-9
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=onboard&arch=riscv64&ver=1.4.1-9
Processing control commands:
> tag -1 pending
Bug #1092871 [src:onboard] FTBFS on riscv64: AssertionError: Lists differ:
[['en_US.lm', 1]] != [['user.lm', 1]]
Added tag(s) pending.
--
1092871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092871
Debian Bug Tracking System
Contact ow...@bug
Control: tag -1 pending
Hello,
Bug #1092871 in onboard 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/debian-mate-team/onboard/-/commit/82461e905d402743009f8cb
Your message dated Wed, 15 Jan 2025 20:00:58 +
with message-id
and subject line Bug#1066998: fixed in sift 6.2.1-1
has caused the Debian Bug report #1066998,
regarding sift: FTBFS with -Werror=implicit-function-declaration
to be marked as done.
This means that you claim that the problem has b
Le mer. 15 janv. 2025 à 20:59, Patrice Duroux
a écrit :
>
> Source: xsok
> Followup-For: Bug #1091286
> Control: tags -1 patch ftbfs
>
> Hi,
>
> I made the attached small fix very simple to resolve the compilation error.
> But how do I test that it works correctly at runtime?
> The data array p[]
Source: xsok
Followup-For: Bug #1091286
Control: tags -1 patch ftbfs
Hi,
I made the attached small fix very simple to resolve the compilation error.
But how do I test that it works correctly at runtime?
The data array p[] is long integers and this represents data read from a
file and I did not ch
Processing control commands:
> tags -1 patch ftbfs
Bug #1091286 [src:xsok] xsok: FTBFS on armhf: showscore.c:75:15: error: passing
argument 1 of ‘ctime’ from incompatible pointer type
[-Wincompatible-pointer-types]
Added tag(s) patch.
--
1091286: https://bugs.debian.org/cgi-bin/bugreport.cgi?b
Your message dated Wed, 15 Jan 2025 19:33:45 +
with message-id
and subject line Bug#1093052: fixed in rsync 3.3.0+ds1-4
has caused the Debian Bug report #1093052,
regarding rsync: Error in 3.2.7-1+deb12u1: "Internal hashtable error: illegal
key supplied!" using -rH
to be marked as done.
This
Your message dated Wed, 15 Jan 2025 19:33:45 +
with message-id
and subject line Bug#1093089: fixed in rsync 3.3.0+ds1-4
has caused the Debian Bug report #1093089,
regarding rsync: Error in 3.2.7-1+deb12u1: "Internal hashtable error: illegal
key supplied!" using -rH
to be marked as done.
This
Your message dated Wed, 15 Jan 2025 19:33:45 +
with message-id
and subject line Bug#1093089: fixed in rsync 3.3.0+ds1-4
has caused the Debian Bug report #1093089,
regarding rsync: "Internal hashtable error: illegal key supplied" when
preserving hardlinks (i.e also with --archive)
to be marked
Your message dated Wed, 15 Jan 2025 19:33:45 +
with message-id
and subject line Bug#1093052: fixed in rsync 3.3.0+ds1-4
has caused the Debian Bug report #1093052,
regarding rsync: "Internal hashtable error: illegal key supplied" when
preserving hardlinks (i.e also with --archive)
to be marked
On Wed, 15 Jan 2025, Sven Geuer wrote:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504044#162
>Applying ExecCondition to me seems the most reasonable solution to this
>bug.
Can the script behind ExecCondition pass variables to the script
behind ExecStart or, even better, the unit itself
Source: xapian-omega
Version: 1.4.25-2
Severity: serious
Justification: preventing migration of fixed faketime on 32-bit arches
Hi.
xapian-omega uses faketime in its tests. (`omegatest.pl`, starting
nearl l.565.) The 32?64-bit time_t transition broke faketime
completely on 32-bit platforms for
Your message dated Wed, 15 Jan 2025 20:20:17 +0100
with message-id <8dd65d89-90cb-40f5-bac5-b86a682da...@debian.org>
and subject line Re: Bug#1093151: libn32gcc-14-dev: Not installable on mips64el
has caused the Debian Bug report #1093151,
regarding libn32gcc-14-dev: Not installable on mips64el
to
Control: tag -1 pending
Hello,
Bug #1093089 in rsync 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/debian/rsync/-/commit/073bb0d483e44341c200ce150c629207c9f34
Control: tag -1 pending
Hello,
Bug #1093052 in rsync 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/debian/rsync/-/commit/073bb0d483e44341c200ce150c629207c9f34
Processing control commands:
> tag -1 pending
Bug #1093052 [rsync] rsync: Error in 3.2.7-1+deb12u1: "Internal hashtable
error: illegal key supplied!" using -rH
Bug #1093089 [rsync] rsync: "Internal hashtable error: illegal key supplied"
when preserving hardlinks (i.e also with --archive)
Ignorin
Your message dated Wed, 15 Jan 2025 18:58:06 +
with message-id
and subject line Bug#1092111: fixed in php-image-text 0.7.0-4
has caused the Debian Bug report #1092111,
regarding php-image-text: debci failure with PHPUnit 11
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> tag -1 pending
Bug #1093089 [rsync] rsync: "Internal hashtable error: illegal key supplied"
when preserving hardlinks (i.e also with --archive)
Bug #1093052 [rsync] rsync: Error in 3.2.7-1+deb12u1: "Internal hashtable
error: illegal key supplied!" using -rH
Ignorin
On Wed, Jan 15, 2025 at 11:22:38AM +0100, Helmut Grohne wrote:
> So I set out rewrite the preinst script avoiding --rename as much as
> possible and instead handling all of the renames manually. This may
> sound backwards, but it appears to practically work much better. At
> least the tests I wrote
Control: tag -1 pending
Hello,
Bug #1093089 in rsync 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/debian/rsync/-/commit/34dc3f2f9b4f0af62ce58008daed4bb6fcad7
Control: tag -1 pending
Hello,
Bug #1093052 in rsync 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/debian/rsync/-/commit/34dc3f2f9b4f0af62ce58008daed4bb6fcad7
Processing control commands:
> tag -1 pending
Bug #1093089 [rsync] rsync: "Internal hashtable error: illegal key supplied"
when preserving hardlinks (i.e also with --archive)
Bug #1093052 [rsync] rsync: Error in 3.2.7-1+deb12u1: "Internal hashtable
error: illegal key supplied!" using -rH
Ignorin
Processing control commands:
> tag -1 pending
Bug #1093052 [rsync] rsync: Error in 3.2.7-1+deb12u1: "Internal hashtable
error: illegal key supplied!" using -rH
Bug #1093089 [rsync] rsync: "Internal hashtable error: illegal key supplied"
when preserving hardlinks (i.e also with --archive)
Ignorin
Processing commands for cont...@bugs.debian.org:
> severity 1093151 grave
Bug #1093151 [libn32gcc-14-dev] libn32gcc-14-dev: Not installable on mips64el
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1093151: https://bugs.debi
Your message dated Wed, 15 Jan 2025 18:28:43 +
with message-id
and subject line Bug#1087008: fixed in raku-license-spdx 3.18.0-2
has caused the Debian Bug report #1087008,
regarding raku-test-meta, raku-license-spdx: File conflict causes unpack failure
to be marked as done.
This means that yo
Your message dated Wed, 15 Jan 2025 18:28:43 +
with message-id
and subject line Bug#1087008: fixed in raku-license-spdx 3.18.0-2
has caused the Debian Bug report #1087008,
regarding raku-license-spdx and raku-test-meta have an undeclared file conflict
on
/usr/lib/perl6/vendor/precomp/B202134
Hi,
On Wed, Jan 15, 2025 at 05:36:48PM +0100, Michael Banck wrote:
> On Wed, Jan 15, 2025 at 04:56:10PM +0200, Andrius Merkys wrote:
> > On 2025-01-15 09:54, Andrius Merkys wrote:
> > > From a quick glance it seems that a lot of problems are related to
> > > Python pickle reading. Upstream has ma
Processing commands for cont...@bugs.debian.org:
> reassign 1093140 src:python-django
Bug #1093140 [python-django] python-django: CVE-2024-56374
Bug reassigned from package 'python-django' to 'src:python-django'.
No longer marked as found in versions 2:2.2.28-1~deb11u4.
Ignoring request to alter f
Processing commands for cont...@bugs.debian.org:
> forcemerge 1093049 1093140
Bug #1093049 [src:python-django] python-django: CVE-2024-56374
Unable to merge bugs because:
package of #1093140 is 'python-django' not 'src:python-django'
Failed to forcibly merge 1093049: Did not alter merged bugs.
>
Your message dated Wed, 15 Jan 2025 17:26:08 +
with message-id
and subject line Bug#1087738: fixed in hkl 5.1.3-1
has caused the Debian Bug report #1087738,
regarding hkl: FTBFS against HDF5 1.14: Module ‘Bindings.HDF5.Raw’ does not
export ‘H5L_info_t’
to be marked as done.
This means that y
tag 1093007 + unreproducible
tag 1093007 + moreinfo
thanks
Hi,
Am 14.01.25 um 15:27 schrieb Jörg Frings-Fürst:
only blank white pages are displayed in the print preview and the pdf export.
Regardless of what I wrote already, this - as I was quite sure of - isn't even
reproducible.
Start
Processing commands for cont...@bugs.debian.org:
> tag 1093007 + unreproducible
Bug #1093007 {Done: René Engelhard } [src:libreoffice]
Print preview and pdf export only show blank pages
Added tag(s) unreproducible.
> tag 1093007 + moreinfo
Bug #1093007 {Done: René Engelhard } [src:libreoffice]
P
Processing commands for cont...@bugs.debian.org:
> merge 1093049 1093140
Bug #1093049 [src:python-django] python-django: CVE-2024-56374
Unable to merge bugs because:
severity of #1093140 is 'grave' not 'important'
package of #1093140 is 'python-django' not 'src:python-django'
Failed to merge 10930
Your message dated Wed, 15 Jan 2025 16:55:44 +
with message-id
and subject line Bug#1092853: fixed in phpmyadmin
4:5.2.2-really5.2.2+20250114+dfsg-1
has caused the Debian Bug report #1092853,
regarding autopkgtest failure with PHPUnit 11 on armel, armhf and i386
to be marked as done.
This me
Your message dated Wed, 15 Jan 2025 16:55:13 +
with message-id
and subject line Bug#1093144: fixed in openturns 1.24-4
has caused the Debian Bug report #1093144,
regarding openturns: FTBFS on amd64: build hangs
to be marked as done.
This means that you claim that the problem has been dealt wi
Processing control commands:
> fixed -1 rsync/3.3.0+ds1-2
Bug #1093052 [rsync] rsync: Error in 3.2.7-1+deb12u1: "Internal hashtable
error: illegal key supplied!" using -rH
Bug #1093089 [rsync] rsync: "Internal hashtable error: illegal key supplied"
when preserving hardlinks (i.e also with --arch
1 - 100 of 194 matches
Mail list logo
