Your message dated Sun, 01 Oct 2023 22:55:23 +
with message-id
and subject line Bug#1053289: fixed in libzypp 17.31.21-2
has caused the Debian Bug report #1053289,
regarding libzypp FTBFS on slower buildds: 87 - EvDownloader_test (Failed)
to be marked as done.
This means that you claim that
Source: bettercap-caplets
Version: 0+git20210429-1
Severity: serious
Control: block -1 by 1024640
bettercap-caplets is uninstallable because it depends on bettercap-ui
which does not exist in Debian.
Thank you,
Jeremy Bícha
Control: tag -1 pending
Hello,
Bug #1053289 in libzypp 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 #1053289 [src:libzypp] libzypp FTBFS on slower buildds: 87 -
EvDownloader_test (Failed)
Added tag(s) pending.
--
1053289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> block -1 by 1024640
Bug #1053331 [src:bettercap-caplets] bettercap-caplets: Unsatisfiable
dependency on bettercap-ui
1053331 was not blocked by any bugs.
1053331 was not blocking any bugs.
Added blocking bug(s) of 1053331: 1024640
--
1053331:
Dear Ondřej,
I just saw you had prepared an NMU version 4.6.4-1.1 for unstable
for this bug per [1,2] but it seems it was never actually uploaded.
I was wondering if there's any particular reason for that, or
if you would consider uploading it, if there's no reason not to?
Thanks,
-a
[1]
Control: forwarded -1 https://github.com/Nheko-Reborn/nheko/issues/1574
On Sun, 24 Sep 2023 10:11:23 + ZenWalker wrote:
Did you report it at upstream?
https://github.com/Nheko-Reborn/nheko/issues
I've just done so.
Processing control commands:
> forwarded -1 https://github.com/Nheko-Reborn/nheko/issues/1574
Bug #1042967 [nheko] nheko crashes on first launch in arm64 (librem 5)
Set Bug forwarded-to-address to
'https://github.com/Nheko-Reborn/nheko/issues/1574'.
--
1042967:
Your message dated Sun, 01 Oct 2023 21:46:53 +
with message-id
and subject line Bug#1051886: fixed in pyside2 5.15.10-4
has caused the Debian Bug report #1051886,
regarding pyside2: FTBFS with llvm-toolchain-16 as default
to be marked as done.
This means that you claim that the problem has
Source: pycryptodome
Version: 3.18.0+dfsg1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=pycryptodome=3.18.0%2Bdfsg1-1
...
[ 1%] Building C object CMakeFiles/mont.dir/<>/src/mont.c.o
cc: error: unrecognized command-line option ‘-mssse3’
cc: error: unrecognized
Processing commands for cont...@bugs.debian.org:
> # Fixed by src:pilkit-2.0-5.
> close 1042286
Bug #1042286 [src:python-django-imagekit] python-django-imagekit: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11
returned exit code 13
Marked Bug as done
> thanks
Processing commands for cont...@bugs.debian.org:
> # I was unable to reproduce it with 4.1.0-2 and 5.0-1.
> close 991650
Bug #991650 [src:python-django-imagekit] python-django-imagekit: FTBFS:
dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit
code 13
Marked Bug as done
Processing control commands:
> close -1 23.8-1
Bug #1053326 [src:python-xsdata] src:python-xsdata: fails to migrate to testing
for too long: uploader built arch:all
Marked as fixed in versions python-xsdata/23.8-1.
Bug #1053326 [src:python-xsdata] src:python-xsdata: fails to migrate to testing
Source: python-xsdata
Version: 23.7-1
Severity: serious
Control: close -1 23.8-1
Tags: sid trixie pending
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 control commands:
> close -1 0.120-2
Bug #1053325 [src:sugar-artwork] src:sugar-artwork: fails to migrate to testing
for too long: cruft not auto removed
Marked as fixed in versions sugar-artwork/0.120-2.
Bug #1053325 [src:sugar-artwork] src:sugar-artwork: fails to migrate to testing
Source: sugar-artwork
Version: 0.120-1
Severity: serious
Control: close -1 0.120-2
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
On 2023-10-01 Andreas Metzler wrote:
> On 2023-10-01 Rainer Dorsch wrote:
[...]
> > It would help if there would be a statement by the Debian exim
> > maintainer team, by when updates are expected to arrive.
> > This would at least help to judge, if I should migrate my systems to
> > postfix or
Processing commands for cont...@bugs.debian.org:
> tags 1051241 +patch
Bug #1051241 [helvum] headsup for gtk + pipewire update
Added tag(s) patch.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1051241:
Processing commands for cont...@bugs.debian.org:
> tags 1023021 + bookworm
Bug #1023021 [src:gitit] gitit: FTBFS on mipsel
Added tag(s) bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1023021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023021
Processing commands for cont...@bugs.debian.org:
> #
> https://buildd.debian.org/status/fetch.php?pkg=gitit=mipsel=0.15.1.0%2Bdfsg-2%2Bb6=1696186257=0
> severity 1023021 serious
Bug #1023021 [src:gitit] gitit: FTBFS on mipsel
Severity set to 'serious' from 'important'
> thanks
Stopping
Your message dated Sun, 01 Oct 2023 19:02:09 +
with message-id
and subject line Bug#1040179: fixed in rmlint 2.9.0-2.5~deb12u1
has caused the Debian Bug report #1040179,
regarding rmlint-gui: invalid Python version number breaks other packages
to be marked as done.
This means that you claim
Your message dated Sun, 01 Oct 2023 19:02:28 +
with message-id
and subject line Bug#1035364: fixed in lttng-modules 2.12.5-1+deb11u1
has caused the Debian Bug report #1035364,
regarding lttng-modules-dkms: fails to build module on bullseye for Linux
5.10.0-22-amd64
to be marked as done.
Thanks for the patch.
I've applied it and uploaded a new version of hickle.
Cheers,
Edward
Your message dated Sun, 01 Oct 2023 18:34:12 +
with message-id
and subject line Bug#1053267: fixed in hickle 5.0.2-6
has caused the Debian Bug report #1053267,
regarding hickle: test_H5NodeFilterProxy fails with h5py 3.9.0: Unable to
delete attribute (no write intent on file)
to be marked as
Control: tag -1 pending
Hello,
Bug #1051886 in pyside2 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 #1051886 [src:pyside2] pyside2: FTBFS with llvm-toolchain-16 as default
Ignoring request to alter tags of bug #1051886 to the same tags previously set
--
1051886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051886
Debian Bug Tracking
Source: ceres-solver
Version: 2.1.0+really2.1.0+dfsg-2
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/ceres-solver/ceres-solver/issues/1009
Control: affects -1 src:colmap src:openturns src:sight
Processing control commands:
> affects -1 src:colmap src:openturns src:sight
Bug #1053322 [src:ceres-solver] ceres-solver FTBFS with suitesparse 7.2.0
Added indication that 1053322 affects src:colmap, src:openturns, and src:sight
--
1053322:
Processing control commands:
> tags -1 patch
Bug #1053267 [src:hickle] hickle: test_H5NodeFilterProxy fails with h5py 3.9.0:
Unable to delete attribute (no write intent on file)
Added tag(s) patch.
--
1053267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053267
Debian Bug Tracking System
Control: tags -1 patch
Hi Edward,
Quoting Drew Parsons:
62s """
62s
62s # load data and try to directly modify 'type' and 'base_type'
Attributes
62s # which will fail cause hdf5 file is opened for read only
62s h5_node = h5_data['somedata']
62s
Your message dated Sun, 01 Oct 2023 17:33:58 +
with message-id
and subject line Bug#1053266: fixed in h5sparse 0.1.0-7
has caused the Debian Bug report #1053266,
regarding python3-h5sparse incomplete Depends: python3-h5py-serial
to be marked as done.
This means that you claim that the
Your message dated Sun, 01 Oct 2023 16:47:08 +
with message-id
and subject line Bug#1053182: fixed in libvpx 1.12.0-1+deb12u1
has caused the Debian Bug report #1053182,
regarding libvpx: CVE-2023-5217
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 01 Oct 2023 16:47:08 +
with message-id
and subject line Bug#1051953: fixed in cups 2.4.2-3+deb12u2
has caused the Debian Bug report #1051953,
regarding cups: CVE-2023-32360
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sun, 01 Oct 2023 16:20:03 +
with message-id
and subject line Bug#1052823: fixed in python-django-timezone-field 6.0.1-1
has caused the Debian Bug report #1052823,
regarding python-django-timezone-field: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i
Your message dated Sun, 01 Oct 2023 15:55:59 +
with message-id
and subject line Bug#1053274: fixed in ont-fast5-api 4.1.1+dfsg-3
has caused the Debian Bug report #1053274,
regarding ont-fast5-api: test_001_read_events fails with h5py 3.9.0:
'AstypeWrapper' object does not support the context
Your message dated Sun, 01 Oct 2023 15:20:16 +
with message-id
and subject line Bug#1052843: fixed in python-django-modelcluster 6.0-3
has caused the Debian Bug report #1052843,
regarding python-django-modelcluster: FTBFS: AssertionError: !=
to be marked as done.
This means that you claim
Your message dated Sun, 01 Oct 2023 14:39:21 +
with message-id
and subject line Bug#1052260: fixed in pytorch 2.0.1+dfsg-5
has caused the Debian Bug report #1052260,
regarding libcpuinfo-dev,libtorch-cuda-dev,libtorch-dev: all ship
/usr/include/clog.h
to be marked as done.
This means that
Package: xmds2
Version: 3.1.0+dfsg2-4
Severity: serious
Justification: debci
xmds2 Depends: python3-h5py-mpi without depending on python3-h5py
python3-h5py-mpi only provides the h5py._debian_h5py_mpi namespace,
not h5py. Hence tests using h5py without specifying _debian_h5py_mpi
fail. This is
Your message dated Sun, 01 Oct 2023 13:50:02 +
with message-id
and subject line Bug#1053312: fixed in packeth 2.1-0.2
has caused the Debian Bug report #1053312,
regarding packeth: FTBFS on non-x86 due to x86 asm
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 01 Oct 2023 13:22:27 +
with message-id
and subject line Bug#1052782: fixed in python-djangorestframework-flex-fields
1.0.2-2
has caused the Debian Bug report #1052782,
regarding python-djangorestframework-flex-fields: FTBFS: dh_auto_test: error:
pybuild --test
I am uploading a NMU once again to fix this. The debdiff is attached.diff -Nru packeth-2.1/debian/changelog packeth-2.1/debian/changelog
--- packeth-2.1/debian/changelog2023-09-20 17:54:49.0 +
+++ packeth-2.1/debian/changelog2023-10-01 12:56:11.0 +
@@ -1,3
On 2023-10-01 Rainer Dorsch wrote:
> Package: exim4-base
> Version: 4.94.2-7
> Severity: critical
> Justification: breaks the whole system
> Dear Maintainer,
> *** Reporter, please consider answering these questions, where appropriate ***
> There are various CVE report with a rating of 9.8/10.
Source: packeth
Version: 2.1-0.1
Severity: serious
With my NMU, I have introduced a FTBFS on non-x86 platforms:
cli_send.c: In function ‘ip_fast_csum’:
cli_send.c:1737:5: error: invalid 'asm': invalid operand for code 'w'
1737 | asm(" movl (%1), %0\n"
| ^~~
cli_send.c:1737:5:
Control: tag -1 pending
Hello,
Bug #1052782 in python-djangorestframework-flex-fields 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 #1052782 [src:python-djangorestframework-flex-fields]
python-djangorestframework-flex-fields: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) pending.
--
1052782:
Package: exim4-base
Version: 4.94.2-7
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
There are various CVE report with a rating of 9.8/10.
CVE-2023-42119
CVE-2023-42118
CVE-2023-42117
Your message dated Sun, 01 Oct 2023 12:20:29 +
with message-id
and subject line Bug#1052719: fixed in python-djantic 0.7.0-4
has caused the Debian Bug report #1052719,
regarding python-djantic: FTBFS: ModuleNotFoundError: No module named 'pymdownx'
to be marked as done.
This means that you
Your message dated Sun, 01 Oct 2023 12:17:26 +
with message-id
and subject line Bug#1051953: fixed in cups 2.3.3op2-3+deb11u4
has caused the Debian Bug report #1051953,
regarding cups: CVE-2023-32360
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 01 Oct 2023 12:17:28 +
with message-id
and subject line Bug#1053182: fixed in libvpx 1.9.0-1+deb11u1
has caused the Debian Bug report #1053182,
regarding libvpx: CVE-2023-5217
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Control: tag -1 pending
Hello,
Bug #1052719 in python-djantic 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 #1052719 [src:python-djantic] python-djantic: FTBFS: ModuleNotFoundError:
No module named 'pymdownx'
Added tag(s) pending.
--
1052719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052719
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> tags 1052696 + ftbfs
Bug #1052696 [src:sccache] sccache: FTBFS in sid
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1052696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052696
Debian
Hi Enrico, hi Frannoe,
you have both contributed to packagesearch in the past (Frannoe
contributed the Spanish Translation, Enrico quite some code changes).
Bug #1050896 now states that I should clarify copyright:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050896
I would like to switch to
Your message dated Sun, 01 Oct 2023 10:36:00 +
with message-id
and subject line Bug#1040521: fixed in tpm2-tss 4.0.1-3
has caused the Debian Bug report #1040521,
regarding tpm2-tss: FTBFS (test failures)
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Source: haskell-aeson
Version: 2.1.2.1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=haskell-aeson=amd64=2.1.2.1-3=1695492428=0
1 out of 1611 tests
Source: pytorch-sparse
Version: 0.6.17-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=pytorch-sparse=arm64=0.6.17-1=1694243524=0
Hi Vincent
On 2023-09-15 23:29:27 +0200, Vincent Bernat wrote:
> On 2023-09-15 21:04, Sebastian Ramacher wrote:
> > Source: libcbor
> > Version: 0.10.2-1
> > Severity: serious
> > X-Debbugs-Cc: sramac...@debian.org
> >
> > https://qa.debian.org/excuses.php?package=libcbor
> >
> > Issues
57 matches
Mail list logo
