Control: tag -1 pending
Hello,
Bug #1054813 in python-dmidecode 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 #1054813 [src:python-dmidecode] python-dmidecode: FTBFS: make[2]: ***
[Makefile:4: test] Error 1
Ignoring request to alter tags of bug #1054813 to the same tags previously set
--
1054813:
Your message dated Sat, 20 Jan 2024 07:49:04 +
with message-id
and subject line Bug#1056802: fixed in gensim 4.3.2+dfsg-1
has caused the Debian Bug report #1056802,
regarding gensim: ftbfs with cython 3.0.x
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing commands for cont...@bugs.debian.org:
> found 1061162 2.12.1-3
Bug #1061162 [src:pypdf2] pypdf2: Do not release with Trixie
Marked as found in versions pypdf2/2.12.1-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1061162:
Your message dated Fri, 19 Jan 2024 20:30:06 -0500
with message-id <87a5p0pza9@gnu.org>
and subject line Re: Bug#1057430: ring: FTBFS: configure: error: sdbus-c++ not
found
has caused the Debian Bug report #1057430,
regarding ring: FTBFS: configure: error: sdbus-c++ not found
to be marked as
Processing commands for cont...@bugs.debian.org:
> block 1057430 by 1059422
Bug #1057430 [src:ring] ring: FTBFS: configure: error: sdbus-c++ not found
1057430 was not blocked by any bugs.
1057430 was not blocking any bugs.
Added blocking bug(s) of 1057430: 1059422
> thanks
Stopping processing
Your message dated Fri, 19 Jan 2024 22:49:08 +
with message-id
and subject line Bug#1056787: fixed in astra-toolbox 2.1.0-4
has caused the Debian Bug report #1056787,
regarding astra-toolbox: ftbfs with cython 3.0.x
to be marked as done.
This means that you claim that the problem has been
Source: pypdf2
Version: 2.12.1-4
Severity: serious
Tags: upstream
Justification: Maintainer opinion
PyPDF2 has been replaced by pypdf upstream. We should not release this
package with Trixie. Rdepends should be either ported or removed.
Scott K
Am Fri, Jan 19, 2024 at 08:22:21PM +0100 schrieb Drew Parsons:
> On 2024-01-19 18:52, Drew Parsons wrote:
> >
> > Hi Andreas, could you push your upstream and pristine-tar branches?
> > Otherwise we can't use your 2023.12.18 branch.
>
> I see what you mean. The tag is there, the orig tarball
Your message dated Fri, 19 Jan 2024 21:42:14 +
with message-id
and subject line Bug#1060935: fixed in python-crontab 3.0.0-3
has caused the Debian Bug report #1060935,
regarding python-crontab: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11"
Your message dated Fri, 19 Jan 2024 21:34:22 +
with message-id
and subject line Bug#1055686: fixed in dm-tree 0.1.8-3
has caused the Debian Bug report #1055686,
regarding dm-tree ftbfs with Python 3.12
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Control: tag -1 pending
Hello,
Bug #1060935 in python-crontab 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 #1060935 [src:python-crontab] python-crontab: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit
code 13
Added tag(s) pending.
--
1060935:
Source: sdaps
Version: 1.9.8-0.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
sdaps fails to build from source. From my build log on amd64:
| dpkg-buildpackage: info: source package sdaps
| dpkg-buildpackage: info:
Your message dated Fri, 19 Jan 2024 20:25:02 +0100
with message-id
and subject line Re: Bug#1061018: octave-splines: FTBFS: make: ***
[debian/rules:5: binary] Error 134
has caused the Debian Bug report #1061018,
regarding octave-splines: FTBFS: make: *** [debian/rules:5: binary] Error 134
to be
Your message dated Fri, 19 Jan 2024 20:24:41 +0100
with message-id
and subject line Re: Bug#1061017: octave-divand: FTBFS: make: ***
[debian/rules:5: binary] Error 134
has caused the Debian Bug report #1061017,
regarding octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134
to be
On 2024-01-19 18:52, Drew Parsons wrote:
Hi Andreas, could you push your upstream and pristine-tar branches?
Otherwise we can't use your 2023.12.18 branch.
I see what you mean. The tag is there, the orig tarball can be
regenerated with
gbp export-orig.
Source: pymatgen
Followup-For: Bug #1058040
No, other way around. The new monty is causing the problem.
Will need to patch or upgrade pymatgen.
Source: pymatgen
Followup-For: Bug #1058040
Sounds like it will need the new version of monty
Package: cron
Version: 3.0pl1-182
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
* What led up to the situation?
1. A user ran "crontab -e"
2. He added the line (note the space):
MAILTO=a...@example.org, b...@example.com
3. He saved and exited
4. No errors
Processing commands for cont...@bugs.debian.org:
> retitle 1060965 q2-feature-classifier: AttributeError: module 'bibtexparser'
> has no attribute 'bparser'
Bug #1060965 [src:qiime] q2-feature-classifier: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.11 -s custom
Processing commands for cont...@bugs.debian.org:
> affects 1060965 - q2-feature-classifier
Bug #1060965 [src:qiime] q2-feature-classifier: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.11 -s custom "--test-args=cd
{build_dir}; py.test-3 --cov=q2_feature_classifier" returned
Control: reassign -1 src:qiime 2022.11.1-2
Control: affects -1 + q2-feature-classifier
Control: merge -1 1060987
This is another manifestation of #1060987, this time affecting
q2-feature-classifier:
> /usr/lib/python3/dist-packages/qiime2/core/cite.py:26: in load
> parser =
Processing control commands:
> reassign -1 src:qiime 2022.11.1-2
Bug #1060965 [src:q2-feature-classifier] q2-feature-classifier: FTBFS:
dh_auto_test: error: pybuild --test -i python{version} -p 3.11 -s custom
"--test-args=cd {build_dir}; py.test-3 --cov=q2_feature_classifier" returned
exit
Processing commands for cont...@bugs.debian.org:
> reassign 1060987 src:qiime 2022.11.1-2
Bug #1060987 [src:q2cli] qiime: FTBFS: AttributeError: module 'bibtexparser'
has no attribute 'bparser'
Bug reassigned from package 'src:q2cli' to 'src:qiime'.
No longer marked as found in versions
Processing commands for cont...@bugs.debian.org:
> reassign 1056042 python3-uncertainties
Bug #1056042 [src:xrayutilities] xrayutilities ftbfs with Python 3.12
Bug reassigned from package 'src:xrayutilities' to 'python3-uncertainties'.
No longer marked as found in versions xrayutilities/1.7.4-1.
Processing control commands:
> reassign -1 src:qiime/2022.11.1-2
Unknown command or malformed arguments to command.
> retitle -1 qiime: FTBFS: AttributeError: module 'bibtexparser' has no
> attribute 'bparser'
Bug #1060987 [src:q2cli] q2cli: FTBFS: dh_auto_test: error: pybuild --test
Control: reassign -1 src:qiime/2022.11.1-2
Control: retitle -1 qiime: FTBFS: AttributeError: module 'bibtexparser' has no
attribute 'bparser'
Control: affects -1 + q2cli
This looks to be the main issue:
> /usr/lib/python3/dist-packages/qiime2/core/cite.py:26: in load
> parser =
On 2024-01-16 17:55, Andreas Tille wrote:
Control: tags -1 pending
Hi,
I've applied the patch in Git and also tried to upgrade to latest
upstream since there is a chance that other Python3.12 issues might be
fixed. Unfortunately the upgrade is all but straightforward and
I gave up finally
Your message dated Fri, 19 Jan 2024 17:40:12 +
with message-id
and subject line Bug#1061049: fixed in suitesparse 1:7.5.1+dfsg-2
has caused the Debian Bug report #1061049,
regarding openturns: FTBFS: make[2]: *** [Makefile:94: test] Error 8
to be marked as done.
This means that you claim
Your message dated Fri, 19 Jan 2024 17:40:12 +
with message-id
and subject line Bug#1061049: fixed in suitesparse 1:7.5.1+dfsg-2
has caused the Debian Bug report #1061049,
regarding suitesparse breaks octave autopkgtest: it hangs
to be marked as done.
This means that you claim that the
Your message dated Fri, 19 Jan 2024 17:40:12 +
with message-id
and subject line Bug#1061049: fixed in suitesparse 1:7.5.1+dfsg-2
has caused the Debian Bug report #1061049,
regarding persalys: FTBFS: make[2]: *** [Makefile:94: test] Error 8
to be marked as done.
This means that you claim that
Your message dated Fri, 19 Jan 2024 17:40:12 +
with message-id
and subject line Bug#1061049: fixed in suitesparse 1:7.5.1+dfsg-2
has caused the Debian Bug report #1061049,
regarding libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in
libcholmod5 without bumping to "libcholmod6"
Your message dated Fri, 19 Jan 2024 17:17:45 +
with message-id
and subject line Bug#1061126: fixed in mysql-8.0 8.0.36-1
has caused the Debian Bug report #1061126,
regarding mysql-8.0: Security fixes from January 2024 CPU
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> tags 1061049 - ftbfs
Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0
has an ABI break in libcholmod5 without bumping to "libcholmod6"
Bug #1060952 [libsuitesparse-dev] persalys: FTBFS: make[2]: *** [Makefile:94:
Processing commands for cont...@bugs.debian.org:
> reassign 1060952 libsuitesparse-dev
Bug #1060952 [src:persalys] persalys: FTBFS: make[2]: *** [Makefile:94: test]
Error 8
Bug reassigned from package 'src:persalys' to 'libsuitesparse-dev'.
No longer marked as found in versions
Processing commands for cont...@bugs.debian.org:
> forcemerge 1061049 1060952 1060970
Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0
has an ABI break in libcholmod5 without bumping to "libcholmod6"
Bug #1061123 [libsuitesparse-dev] suitesparse breaks octave
Processing control commands:
> forwarded 1061063 https://github.com/h5py/h5py/issues/1927
Bug #1061063 [src:h5py] armhf: h5py's tests expose unaligned memory accesses
during the build
Set Bug forwarded-to-address to 'https://github.com/h5py/h5py/issues/1927'.
--
1061063:
Source: h5py
Followup-For: Bug #1061063
Control: forwarded 1061063 https://github.com/h5py/h5py/issues/1927
The problem was raised upstream at
https://github.com/h5py/h5py/issues/1927
Makes it difficult to test if we can't reproduce it on all armhf
environments.
A patch was suggested for the
Your message dated Fri, 19 Jan 2024 17:04:27 +0100
with message-id <7df9c5244c1140426702f0986cdc5a767d67cafc.ca...@debian.org>
and subject line Re: Bug#1060937: ionit: FTBFS: AttributeError: module
'astroid.nodes' has no attribute 'TryExcept'
has caused the Debian Bug report #1060937,
regarding
Your message dated Fri, 19 Jan 2024 17:04:30 +0100
with message-id
and subject line Re: Bug#1061031: bdebstrap: FTBFS: AttributeError: module
'astroid.nodes' has no attribute 'TryExcept'
has caused the Debian Bug report #1061031,
regarding bdebstrap: FTBFS: AttributeError: module 'astroid.nodes'
Hi,
> > please push this packaging effort to a personal (but publicly
> > accessible) git repo on salsa, so that i can cherry pick the changes i
> > like, thanks
>
> Here:
>
>
> https://salsa.debian.org/niol/transmission/-/tree/master-candidate?ref_type=heads
I've also updated my pull
Your message dated Fri, 19 Jan 2024 15:21:04 +
with message-id
and subject line Bug#1042529: fixed in sogo 5.9.0-1
has caused the Debian Bug report #1042529,
regarding sogo: Multiple embdeded and minified javascript library
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 19 Jan 2024 13:49:54 +
with message-id
and subject line Bug#983619: fixed in vdr-plugin-markad 3.4.5-3
has caused the Debian Bug report #983619,
regarding vdr-markad: fails to install: chown: invalid user: 'vdr:vdr'
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> notfound 1014862 3.4.5-1
Bug #1014862 [src:vdr-plugin-markad] vdr-plugin-markad: FTBFS: Cannot find (any
matches for) "command/markad"
Ignoring request to alter found versions of bug #1014862 to the same values
previously set
> thanks
Stopping
notfound 1014862 3.4.5-1
thanks
In the current build this bug does not exist.
OpenPGP_signature.asc
Description: OpenPGP digital signature
Your message dated Fri, 19 Jan 2024 19:36:23 +0800
with message-id
and subject line Re: Bug#1050431: binutils-mipsen: FTBFS on all architectures
has caused the Debian Bug report #1050431,
regarding binutils-mipsen: FTBFS: ld: mips.o:(.data.rel.ro+0x740): undefined
reference to
Your message dated Fri, 19 Jan 2024 19:36:23 +0800
with message-id
and subject line Re: Bug#1050431: binutils-mipsen: FTBFS on all architectures
has caused the Debian Bug report #1050431,
regarding binutils-mipsen: FTBFS on all architectures
to be marked as done.
This means that you claim that
It's now buildable.
Your message dated Fri, 19 Jan 2024 10:49:10 +
with message-id
and subject line Bug#1056529: fixed in sphinx-autoapi 3.0.0-0.1
has caused the Debian Bug report #1056529,
regarding sphinx-autoapi's autopkg tests fail with Python 3.12
to be marked as done.
This means that you claim that the
Control: tag -1 pending
Hello,
Bug #1058408 in sphinx-autoapi 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 #1058408 [src:sphinx-autoapi] sphinx-autoapi: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit
code 13
Added tag(s) pending.
--
1058408:
Control: tag -1 pending
Hello,
Bug #1056529 in sphinx-autoapi 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 #1056529 [src:sphinx-autoapi] sphinx-autoapi's autopkg tests fail with
Python 3.12
Added tag(s) pending.
--
1056529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
I've now been able to setup autopkgtest locally based on sbuild.
I get failures in an autopkgtest (sbuild sid) chroot, but not when I do
a clean pbuilder chroot via sid to do "pbuilder login".
Investigating the differences between what should be identical chroots.
Alastair
--
Alastair
Your message dated Fri, 19 Jan 2024 09:04:05 +
with message-id
and subject line Bug#1061000: fixed in dqlite 1.16.0-4
has caused the Debian Bug report #1061000,
regarding dqlite: FTBFS: dh_auto_test: error: make -j8 check
"TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
to be
56 matches
Mail list logo
