Your message dated Mon, 03 Mar 2025 15:43:58 +
with message-id
and subject line Bug#1099293: fixed in tahoe-lafs 1.20.0-4
has caused the Debian Bug report #1099293,
regarding tahoe-lafs: FTBFS: E ModuleNotFoundError: No module named 'fixtures'
to be marked as done.
This means that you claim
Control: forwared -1 https://github.com/randy408/libspng/issues/276
Hi Santiago,
On Sun Mar 2, 2025 at 7:09 PM CET, Santiago Vila wrote:
When a library change triggers a bunch of similar FTBFS problems in
packages having it in their build-depends, it may be the case that
there is a bug in the
Your message dated Mon, 03 Mar 2025 16:37:42 +
with message-id
and subject line Bug#1098729: fixed in prometheus-pgbouncer-exporter 1:0.10.2-2
has caused the Debian Bug report #1098729,
regarding prometheus-pgbouncer-exporter has an undeclared file conflict on
/usr/bin/pgbouncer_exporter
to b
Processing commands for cont...@bugs.debian.org:
> # Note: versioned affects does not seem to work
> # The aim is still to make the bug to be shown here:
> # https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=kitty
> # so let's try this now:
> affects 1099240 = src:kitty
Bug #1099240 [fish] kitty:
Processing commands for cont...@bugs.debian.org:
> tags 1099073 + confirmed
Bug #1099073 [adduser] adduser: warnings when package creating system users is
upgraded
Ignoring request to alter tags of bug #1099073 to the same tags previously set
> tags 1099397 + confirmed
Bug #1099397 [adduser] impo
Your message dated Mon, 03 Mar 2025 15:34:47 +
with message-id
and subject line Bug#1087850: fixed in abseil 20230802.1-4.1
has caused the Debian Bug report #1087850,
regarding abseil: autopkgtest regression due to new CMake deprecation warning
to be marked as done.
This means that you claim
Your message dated Mon, 03 Mar 2025 15:34:59 +
with message-id
and subject line Bug#1087850: fixed in abseil 20240722.0-1.1
has caused the Debian Bug report #1087850,
regarding abseil: autopkgtest regression due to new CMake deprecation warning
to be marked as done.
This means that you claim
Your message dated Mon, 03 Mar 2025 16:07:09 +
with message-id
and subject line Bug#1099276: fixed in python-testscenarios 0.5.0-5
has caused the Debian Bug report #1099276,
regarding python-testscenarios: FTBFS: ModuleNotFoundError: No module named
'pbr'
to be marked as done.
This means tha
Your message dated Mon, 03 Mar 2025 09:31:15 +
with message-id
and subject line Bug#1099269: fixed in pytest-httpx 0.35.0-1
has caused the Debian Bug report #1099269,
regarding pytest-httpx: FTBFS: E assert 'No response ... 2} json
body' == 'No response ... 2} json body'
to be marke
Your message dated Mon, 03 Mar 2025 09:29:49 +
with message-id
and subject line Bug#1075354: fixed in pachi 1:1.0-14
has caused the Debian Bug report #1075354,
regarding pachi: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated Mon, 03 Mar 2025 09:56:13 +
with message-id
and subject line Bug#1090984: fixed in opensm 3.3.23-3.1
has caused the Debian Bug report #1090984,
regarding opensm: fails to build for arch:all
to be marked as done.
This means that you claim that the problem has been dealt with
Source: python-sqt
Version: 0.8.0-8
Followup-For: Bug #1098613
Control: tags -1 patch ftbfs
Dear Maintainer,
I'm able to replicate this FTBFS locally using a Debian testing (trixie)
environment during autopkgtests.
After using cython, gcc and Python 3.13 to run a minimized subset of the
failing
Source: samhain
Version: 4.1.4-5
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: debian-am...@lists.debian.org
User: debian-am...@lists.debian.org
Usertags: amd64
On my up to date testing system:
# apt-get source samhain
(As root)
# apt install libgmp3-dev libext2fs-dev libauparse-dev
cd samhain-4.
Processing control commands:
> tags -1 patch ftbfs
Bug #1098613 [src:python-sqt] python-sqt: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.12 3.13" returned exit code 13
Added tag(s) patch.
--
1098613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098613
Your message dated Sat, 01 Mar 2025 02:41:28 +
with message-id
and subject line Bug#1091292: fixed in asymptote 2.95+ds-2
has caused the Debian Bug report #1091292,
regarding asymptote: FTBFS on armhf: make[4]: *** [Makefile:14: hatch.png]
Error 1
to be marked as done.
This means that you cl
Source: gbdfed
Version: 1.6-4
Severity: serious
Justification: grab attention of maintainer
X-Debbugs-Cc: Andrew Shadura , 1032...@bugs.debian.org,
967...@bugs.debian.org, 980...@bugs.debian.org, 1096...@bugs.debian.org,
Package Salvaging Team
Dear maintainer,
I suggest removing gbdfed from De
Your message dated Mon, 03 Mar 2025 10:57:42 +
with message-id
and subject line Bug#1099271: fixed in python-a2wsgi 1.10.8-2
has caused the Debian Bug report #1099271,
regarding python-a2wsgi: FTBFS: E assert '{"example":123}' ==
'{"example": 123}'
to be marked as done.
This means
Source: librep
Version: 0.92.7-3
Severity: serious
Tags: ftbfs patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear Maintainer,
The latest version of librep has one FTBFS issue on riscv64:
```
...
REPLISPDIR=../lisp REP_DL_LOAD_PATH=../src/
Your message dated Mon, 03 Mar 2025 09:50:19 +
with message-id
and subject line Bug#1099237: fixed in isochron 0.9-0.2
has caused the Debian Bug report #1099237,
regarding isochron: FTBFS: src/common.h:41:8: error: redefinition of 'struct
sched_attr'
to be marked as done.
This means that you
Processing control commands:
> severity -1 serious
Bug #1098411 [src:nix] Please backport lowdown>=1.4.0 compatibility fix to
unstable
Severity set to 'serious' from 'important'
--
1098411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098411
Debian Bug Tracking System
Contact ow...@bugs.d
Hi Michael,
On 2025-01-16 09:45, Michael Banck wrote:
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 issue yesterday
Your message dated Mon, 03 Mar 2025 10:23:01 +
with message-id
and subject line Bug#1099179: fixed in komposter 0+git20201216+ds-7
has caused the Debian Bug report #1099179,
regarding komposter: FTBFS on amd64: patch.c:575:11: error: assignment to
‘unsigned int *’ from incompatible pointer ty
Your message dated Mon, 03 Mar 2025 10:30:49 +
with message-id
and subject line Bug#1099275: fixed in python-respx 0.22.0-1
has caused the Debian Bug report #1099275,
regarding python-respx: FTBFS: FAIL Required test coverage of 95% not reached.
Total coverage: 87.44%
to be marked as done.
T
Hi,
> The fixing is very easy and it works on my local Unmatched board, but I
> am not sure if it's appropriate to send this patch given there is one
> beta hint on uploading.
The affected version is the one I want to see in Trixie, so yeah,
a patch to fix this is useful and greatly appreciated,
Your message dated Mon, 03 Mar 2025 11:26:26 +
with message-id
and subject line Bug#1098898: fixed in satdump 1.2.0-3
has caused the Debian Bug report #1098898,
regarding satdump: Build dependency libomp-dev no longer available on i386
to be marked as done.
This means that you claim that the
Your message dated Mon, 03 Mar 2025 11:52:35 +
with message-id
and subject line Bug#1095059: fixed in libsdl3-ttf 3.2.0+ds-1
has caused the Debian Bug report #1095059,
regarding libsdl3-ttf: not yet suitable for a stable release
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> close 1099410
Bug #1099410 [src:gbdfed] gbdfed: Should this package be removed from Debian?
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1099410: https://bugs.debian.org/cgi-bin/bugreport.cgi
Your message dated Mon, 03 Mar 2025 13:08:13 +
with message-id
and subject line Bug#1071137: fixed in pytorch-audio 2.6.0-1
has caused the Debian Bug report #1071137,
regarding pytorch-audio FTBFS with pytorch 2.1.2
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Mon, 03 Mar 2025 13:39:40 +
with message-id
and subject line Bug#1098611: fixed in python-scrapy 2.12.0-2
has caused the Debian Bug report #1098611,
regarding python-scrapy: FTBFS: E AssertionError: 1 responses
remaining in queue.
to be marked as done.
This means
Control: reassign -1 fish
Control: found -1 4.0.0-2
Control: affects -1 kitty/0.39.1-1
Control: forwarded -1 https://github.com/kovidgoyal/kitty/issues/8385
This is a regression caused due to fish's new version. It is fixed in [1].
[1]
https://github.com/fish-shell/fish-shell/commit/4378e73fc746
Processing control commands:
> reassign -1 fish
Bug #1099240 [src:kitty] kitty: FTBFS: ERROR: test_fish_integration
(kitty_tests.shell_integration.ShellIntegrationWithKitten.test_fish_integration)
Bug reassigned from package 'src:kitty' to 'fish'.
No longer marked as found in versions kitty/0.39.
Hi,
On Mon, Mar 3, 2025 at 6:53 PM intrigeri wrote:
>
> Hi,
>
> > The fixing is very easy and it works on my local Unmatched board, but I
> > am not sure if it's appropriate to send this patch given there is one
> > beta hint on uploading.
>
> The affected version is the one I want to see in Trix
Package: gimp
Version: 3.0.0~RC3-1
Severity: grave
Tags: patch
Justification: renders package unusable
X-Debbugs-Cc: jeremy.bi...@canonical.com
I have found a problem with Gimp 3.0 (RC1, RC2, RC3) crashing on startup.
The crash is caused by Gimp not able to open gimp.svg icon file, 100%
reprodu
Hello,
On Mon, 3 Mar 2025, at 10:42, Andreas Tille wrote:
> Dear maintainer,
>
> I suggest removing gbdfed from Debian for the following reasons:
>
> * It accumulated several bugs where every single one is a symptom
>of the age of the package
> - #980914: "Wrong Homepage" where even sugge
Package: nala
Version: 0.15.4
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: f...@ndrewsebastiangunawan.mozmail.com
the output I get from installing rofi-dev for example:
severity 1099415 important
thanks
Hello Santiago,
Am Mon, Mar 03, 2025 at 12:51:17PM +0100 schrieb Santiago Vila:
> I tried building samhain on testing and it worked for me.
Ok, I was really suprised myself and tried it twice in my main system.
> Can you try building it with sbuild on a chroot u
Processing commands for cont...@bugs.debian.org:
> severity 1099415 important
Bug #1099415 [src:samhain] samhain: FTBFS in Testing
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1099415: https://bugs.debian.org/cgi-bin/b
Processing commands for cont...@bugs.debian.org:
> severity 1099212 serious
Bug #1099212 [nautilus] nautilus: Crash when starting with assertion failed in
../src/libtracker-common/tracker-parser.c
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.
Please conta
Control: found -1 6.13.5-1~exp1
with pahole available, the next script is missing:
/usr/src/linux-headers-@KVERS@/tools/bpf/resolve_btfids/resolve_btfids
DKMS (dkms-3.1.5) make.log for dkms_test/1.0 for kernel 6.13-amd64 (x86_64)
Sat Mar 1 01:09:31 UTC 2025
Building module(s)
# command: make -
Your message dated Fri, 28 Feb 2025 17:34:43 +
with message-id
and subject line Bug#1098658: Removed package(s) from unstable
has caused the Debian Bug report #1098582,
regarding ocaml-speex: FTBFS: Error: The value "restart" has type
"Ogg.Stream.stream -> unit"
to be marked as done.
This me
Your message dated Sat, 01 Mar 2025 15:36:49 +
with message-id
and subject line Bug#1099181: fixed in linphone 5.3.105-1
has caused the Debian Bug report #1099181,
regarding linphone: FTBFS: Could not find a package configuration file provided
by "ortp"
to be marked as done.
This means that
Source: r-cran-rmpfr
Version: 1.0-0-1
Severity: serious
Tags: ftbfs patch
X-Debbugs-Cc: Charles Plessy
https://buildd.debian.org/status/logs.php?pkg=r-cran-rmpfr&ver=1.0-0-1
...
convert.c: In function ‘R_mpfr_GET_EXP’:
convert.c:71:21: error: ‘mpft_exp_t’ undeclared (first use in this function);
Hello.
I tried building samhain on testing and it worked for me.
Can you try building it with sbuild on a chroot using only build-essential
packages?
I would really worry if it also fails to build that way. For now it
seems there is something wrong in your system, or maybe you have
discovered
Hello Stefano,
My understanding is that bugs against backports aren't meant to be filed
in the ordinary BTS.
Xiyue has been looking for a solution for these issues and perhaps this
is a fine place to discuss them, so I'll leave this bug open.
--
Sean Whitton
signature.asc
Description: PGP sig
(adding Xiyue)
On Mon 03 Mar 2025 at 08:44pm +08, Sean Whitton wrote:
> Hello Stefano,
>
> My understanding is that bugs against backports aren't meant to be filed
> in the ordinary BTS.
>
> Xiyue has been looking for a solution for these issues and perhaps this
> is a fine place to discuss them,
Processing commands for cont...@bugs.debian.org:
> # This is so that the bug is shown here:
> # https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=kitty
> affects 1099240 = src:kitty/0.39.1-1
Bug #1099240 [fish] kitty: FTBFS: ERROR: test_fish_integration
(kitty_tests.shell_integration.ShellIntegra
Hi,
Bo YU (2025-03-03):
> On Mon, Mar 3, 2025 at 6:53 PM intrigeri wrote:
>> Do you want to submit your patch upstream
>> (https://gitlab.com/apparmor/apparmor/) or should I?
>>
>
> In general, I should forward the patch to upstream. But here I am not
> sure if this makes sense or not because thi
Processing commands for cont...@bugs.debian.org:
> close 1094089
Bug #1094089 [src:linphone-desktop] linphone-desktop: FTBFS: unsatisfiable
build-dependencies: libmbedcrypto7t64 (>= 2.28.0), libmbedtls14t64 (>= 2.28.0),
libmbedx509-1t64 (>= 2.28.0)
Marked Bug as done
> thanks
Stopping processing
Processing control commands:
> tag -1 pending
Bug #1095375 [src:rst2pdf] rst2pdf: FTBFS: test_jpg_scaling fails
Added tag(s) pending.
--
1095375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 03 Mar 2025 17:34:05 +
with message-id
and subject line Bug#1077527: fixed in abseil 20230802.1-4.2
has caused the Debian Bug report #1077527,
regarding abseil: FTBFS: civil_time_test.cc:875:29: error: ‘setfill’ is not a
member of ‘std’
to be marked as done.
This mean
Processing control commands:
> tag -1 pending
Bug #1099397 [adduser] impossible to add a user to a system group with leading _
Added tag(s) pending.
--
1099397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 serious
Bug #1099185 [courier-unicode] libcourier-unicode4: wrong .so version vs
package version
Severity set to 'serious' from 'important'
--
1099185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099185
Debian Bug Tracking System
Contact ow...@b
Processing commands for cont...@bugs.debian.org:
> unarchive 1068745
Bug #1068745 {Done: Michael R. Crusoe }
[src:coinor-symphony] coinor-symphony: FTBFS with coinutils 2.11.10
Unarchived Bug 1068745
> reopen 1068745
Bug #1068745 {Done: Michael R. Crusoe }
[src:coinor-symphony] coinor-symphony:
Processing commands for cont...@bugs.debian.org:
> # glibc 2.41 transition started
> severity 1098892 serious
Bug #1098892 [python3-mrgingham] python3-mrgingham: autopkgtest failure with
glibc 2.41 due to use of executable stack
Severity set to 'serious' from 'important'
> thanks
Stopping process
Processing control commands:
> severity -1 normal
Bug #1095791 [src:dpkg] dpkg: incompatible and Policy-violating R³ default
change breaks packages’ builds
Severity set to 'normal' from 'serious'
--
1095791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095791
Debian Bug Tracking System
Co
Control: severity -1 normal
Hi Thorsten
As you can see, I have downgraded the bug to normal. I will come back to
my reasons for that below, but I would like to start elsewhere first.
Thorsten Glaser:
> On Fri, 14 Feb 2025, Guillem Jover wrote:
> [...]
Yes, I know. I’m sorry for having a life
Processing commands for cont...@bugs.debian.org:
> notfound 1094064 libosmo-netif/1.5.1-1
Bug #1094064 {Done: Bastian Germann }
[src:libosmo-netif] libosmo-netif: FTBFS: unsatisfiable build-dependencies:
libmbedcrypto7t64 (>= 2.28.0), libmbedtls14t64 (>= 2.28.0), libmbedx509-1t64
(>= 2.28.0)
No
Package: libc6-arm64-cross
Version: 2.40-4cross1
Severity: serious
X-Debbugs-Cc: wa...@debian.org
libc6-dev-arm64-cross is uninstallable:
| Unsatisfied dependencies:
| libc6-dev:arm64 : Breaks: libc6-dev-arm64-cross (< 2.41~) but 2.40-4cross1
is to be installed
Bastian
-- System Information:
Hi,
On Mon, 2025-03-03 at 13:59 -0500, Jeremy Bícha wrote:
> Thank you for today's upload of gnome-shell-extension-blur-my-shell.
> Could you do another upload, source-only, with urgency=high ? The
> high
> urgency helps it to not slow down the GNOME Shell transition without
> needing Release Team
Processing commands for cont...@bugs.debian.org:
> notfound 1094081 osmo-hlr/1.8.0+dfsg1-2
Bug #1094081 [src:osmo-hlr] osmo-hlr: FTBFS: unsatisfiable build-dependencies:
libmbedcrypto7t64 (>= 2.28.0), libmbedtls14t64 (>= 2.28.0), libmbedx509-1t64
(>= 2.28.0)
No longer marked as found in versions
Source: nanovna-saver
Version: 0.7.2-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
nanovna-saver depends on libpyside6-py3-6.7. The latest uploads of
pyside6 bumped this version to libpyside6-py3-6.8. Since nanovna-saver
only builds Arch: all packages, it requires a manual change to updat
Your message dated Mon, 3 Mar 2025 19:57:45 +0100
with message-id
and subject line Bugs fixes by new golang-golang-x-tools 1:0.25.0+ds-1 upload
has caused the Debian Bug report #1098551,
regarding golang-github-cockroachdb-apd: FTBFS: stringer: internal error:
package "fmt" without types was impo
Your message dated Mon, 3 Mar 2025 19:57:45 +0100
with message-id
and subject line Bugs fixes by new golang-golang-x-tools 1:0.25.0+ds-1 upload
has caused the Debian Bug report #1098556,
regarding golang-github-klauspost-compress: FTBFS: stringer: internal error:
package "encoding/binary" without
Your message dated Mon, 3 Mar 2025 19:57:45 +0100
with message-id
and subject line Bugs fixes by new golang-golang-x-tools 1:0.25.0+ds-1 upload
has caused the Debian Bug report #1098559,
regarding golang-github-miekg-dns: FTBFS: 2025/02/21 13:21:43 internal error:
package "context" without types
Your message dated Mon, 3 Mar 2025 19:57:45 +0100
with message-id
and subject line Bugs fixes by new golang-golang-x-tools 1:0.25.0+ds-1 upload
has caused the Debian Bug report #1098561,
regarding golang-github-smartystreets-assertions: FTBFS: stringer: internal
error: package "bytes" without typ
Your message dated Mon, 3 Mar 2025 19:57:45 +0100
with message-id
and subject line Bugs fixes by new golang-golang-x-tools 1:0.25.0+ds-1 upload
has caused the Debian Bug report #1098560,
regarding golang-github-minio-madmin-go: FTBFS: stringer: internal error:
package "strconv" without types was
Your message dated Mon, 3 Mar 2025 19:49:35 +0100
with message-id
and subject line Re: Bug#1082974: golang-golang-x-tools: FTBFS: diagnostic
"types.Alias requires go1.22 or later (module is go1.21)" does not match
pattern `types.Alias requires go1.22 or later (file is go1.16)`
has caused the Deb
Hello,
Am Montag, 3. März 2025, 15:21 schrieb intrigeri:
> Bo YU (2025-03-03):
> > On Mon, Mar 3, 2025 at 6:53 PM intrigeri wrote:
> >> Do you want to submit your patch upstream
> >> (https://gitlab.com/apparmor/apparmor/) or should I?
> >
> > In general, I should forward the patch to upstream. B
Your message dated Tue, 04 Mar 2025 00:51:52 +
with message-id
and subject line Bug#1093086: fixed in rdkit 202409.6-1
has caused the Debian Bug report #1093086,
regarding rdkit: FTBFS on big-endian architectures
to be marked as done.
This means that you claim that the problem has been dealt
Hi,
On Mon, Mar 03, 2025 at 12:22:17PM +0200, Andrius Merkys wrote:
> I think this is high time to proceed with architecture limiting. Are you
> planning to update rdkit to 202409.5, or are you fine with me performing the
> architecture limiting ASAP?
I did that now, thanks for the reminder!
Mi
Source: sddm
Version: 0.21.0+git20250131.c2b97dd-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=sddm&arch=all&ver=0.21.0%2Bgit20250131.c2b97dd-1&stamp=1741010690&raw=0
...
dh_qmldeps -i
I: dh_qmldeps dh_qmldeps:138: Execute /usr/bin/pkgkde-getqmldepends -i -p
sd
Your message dated Mon, 03 Mar 2025 23:06:05 +
with message-id
and subject line Bug#1094895: fixed in camitk 5.2.0-3
has caused the Debian Bug report #1094895,
regarding camitk: FTBFS with ITK 5.4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Control: severity 1099470 critical
Control: affects 1099477 colord
Control: merge 1099470 1099477
Correctly merging...
Note that the consequence of the incorrect test may even be worse:
It would not notice when the user is not a system user. This might
give unexpected rights to a normal user.
--
Processing control commands:
> severity 1099470 critical
Bug #1099470 [adduser] adduser: spurious fatal error "The user `colord' already
exists, but is not a system user."
Ignoring request to change severity of Bug 1099470 to the same value.
> affects 1099477 colord
Bug #1099477 [adduser] adduser
Processing commands for cont...@bugs.debian.org:
> affects 1099477 colord
Bug #1099477 [adduser] adduser: Re-adding existing system user fails, when * as
password set
Bug #1099470 [adduser] adduser: spurious fatal error "The user `colord' already
exists, but is not a system user."
Ignoring reque
Hi Emmanuel,
Emmanuel Promayon, on 2025-02-28:
> Thank you very much for your detailed bug report.
> I am currently adding a patch (simply disabling this specific test), that
> should be hopefully pushed today on salsa.
>
> As the test compare input data with output data, a update in the source c
Package: adduser
Version: 3.143
Followup-For: Bug #1099470
Control: merge 1099470 1099477
Hi Vincent,
> So, if EXISTING_LOCKED is set, then the test will be false and will not
> trigger the error.
yes, looked into the code and changes and came to the same conclusion.
I will mark by bug report i
Package: libideep-dev
Version: 0.0~git20250115.9873ffc-1
Severity: serious
The following packages have unmet dependencies:
libideep-dev : Depends: libdnnl-dev (< 3.7.0~) but 3.7.1+ds-1 is to be
installed
Processing commands for cont...@bugs.debian.org:
> forcemerge 1099141 1099142
Bug #1099141 [gpg] GnuPG: Defense against DoS breaks verification of signatures
from expired or revoked keys
Bug #1099142 [gpg] GnuPG: Defense against DoS breaks verification of signatures
from expired or revoked keys
On Sun, Feb 23, 2025 at 06:35:23PM +0100, Sebastian Ramacher wrote:
> Source: mame
> Version: 0.274+dfsg.1-2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: debian-...@lists.debian.org, sramac...@debian.org
> User: d
Control: tag -1 pending
Hello,
Bug #1093086 in rdkit 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/debichem-team/rdkit/-/commit/6a1088646ac832c26f79b0da6997ad
Processing control commands:
> tag -1 pending
Bug #1093086 [src:rdkit] rdkit: FTBFS on big-endian architectures
Added tag(s) pending.
--
1093086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: adduser
Version: 3.143
Followup-For: Bug #1099470
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outco
Package: colord
Version: 1.4.7-3
Severity: serious
When upgrading colord with aptitude:
Setting up colord (1.4.7-3) ...
warn: The home dir /var/lib/colord you specified already exists.
fatal: The user `colord' already exists, but is not a system user. Exiting.
dpkg: error processing package colo
Your message dated Mon, 03 Mar 2025 21:39:29 +
with message-id
and subject line Bug#1068733: fixed in lvm2 2.03.31-1
has caused the Debian Bug report #1068733,
regarding lvm2: lvresize --resizefs fails due to missing
/usr/libexec/lvresize_fs_helper
to be marked as done.
This means that you c
Your message dated Mon, 03 Mar 2025 21:39:29 +
with message-id
and subject line Bug#1068733: fixed in lvm2 2.03.31-1
has caused the Debian Bug report #1068733,
regarding lvm2: resize lv error "/usr/libexec/lvresize_fs_helper: execvp failed"
to be marked as done.
This means that you claim that
Package: dh-elpa-helper
Version: 2.0.16
Severity: serious
There are several reports against Emacs 30.1 backports that some
packages are seeing byte-compilation errors when upgrading to Emacs
30.1[1][2].
Currently we identified that this could be caused by the install script
from dh-elpa-helper wh
Your message dated Mon, 03 Mar 2025 22:06:53 +
with message-id
and subject line Bug#1099242: fixed in libpdfbox-graphics2d-java 0.43-2
has caused the Debian Bug report #1099242,
regarding libpdfbox-graphics2d-java: FTBFS: cannot find symbol
to be marked as done.
This means that you claim that
On 2025-03-03 22:42:28 +0100, Vincent Lefevre wrote:
> When upgrading colord with aptitude:
>
> Setting up colord (1.4.7-3) ...
> warn: The home dir /var/lib/colord you specified already exists.
>
> fatal: The user `colord' already exists, but is not a system user. Exiting.
> dpkg: error processi
Source: shutter
Version: 0.99.6-1
Severity: serious
Tags: ftbfs
X-Debbugs-CC: andre...@debian.org
shutter fails to build because of a build test failure. Here is an
excerpt from the build log:
Can't locate Test/Strict.pm in @INC (you may need to install the
Test::Strict module) (@INC entries chec
Processing control commands:
> reassign -1 adduser 3.143
Bug #1099470 [colord] colord: upgrade to colord 1.4.7-3 fails: The user
`colord' already exists, but is not a system user.
Bug reassigned from package 'colord' to 'adduser'.
No longer marked as found in versions colord/1.4.7-3.
Ignoring req
Package: colord
Version: 1.4.7-3
Followup-For: Bug #1099470
Hi,
I stumbled over the same issue, and tried to have a look into what is the
problem.
But apperently I failed to see it, yes a colord user already exists, but is a
system user and uses the same home-dir.
According to `man adduser` thi
On 2025-03-03 23:18:35 +0100, Michael Musenbrock wrote:
> This maybe looks more like an issue in adduser?
Yes, I've just reassigned the bug to adduser.
> So changing the shadow password field from '*' (no pwd) to '!'
> (locked) allows adduser to pass.
Because
use constant {
EXISTING_NOT_FOU
Sean Whitton writes:
> (adding Xiyue)
>
Thanks Sean!
> On Mon 03 Mar 2025 at 08:44pm +08, Sean Whitton wrote:
>
>> Hello Stefano,
>>
>> My understanding is that bugs against backports aren't meant to be filed
>> in the ordinary BTS.
>>
>> Xiyue has been looking for a solution for these issues a
On 2025-03-03 23:26:17 +0100, Vincent Lefevre wrote:
> BTW, the adduser code looks suspicious:
>
> my $ret = existing_user_status($new_name, $new_uid);
> if ($ret == (EXISTING_FOUND|EXISTING_SYSTEM)) {
> # a user with this name already exists; it's a problem when it's not
> a syst
Processing control commands:
> affects -1 + incus
Bug #1099444 [incus-base] incus-base: ineffective Replaces for incus due to
/usr-move (DEP17 P1)
Added indication that 1099444 affects incus
--
1099444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099444
Debian Bug Tracking System
Contact
Package: oar-common
Version: 2.6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + oar-node
oar-common has an undeclared file conflict. This may result in an unpack
error from dpkg.
The file /usr/sbin/pam_oar_adopt is contained in the packages
*
Processing control commands:
> affects -1 + jdim
Bug #1099443 [python3-juliandate] python3-juliandate has an undeclared file
conflict on /usr/bin/jd
Added indication that 1099443 affects jdim
--
1099443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099443
Debian Bug Tracking System
Contac
Processing control commands:
> affects -1 + oar-node
Bug #1099442 [oar-common] oar-common has an undeclared file conflict on
/usr/sbin/pam_oar_adopt
Added indication that 1099442 affects oar-node
--
1099442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099442
Debian Bug Tracking System
Co
Package: python3-juliandate
Version: 1.0.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + jdim
python3-juliandate has an undeclared file conflict. This may result in
an unpack error from dpkg.
The file /usr/bin/jd is contained in the packages
*
1 - 100 of 151 matches
Mail list logo
