Bug#1058122: python-griddataformats: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?

2024-01-12 Thread Yogeswaran Umasankar
Hi, I created a patch for fixing AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. I've attached the debdiff for you to check out. Cheers! diff -Nru python-griddataformats-1.0.1/debian/changelog python-griddataformats-1.0.1/debian/changelog ---

Bug#1058027: pybj: FTBFS with Python 3.12

2024-01-12 Thread s3v
Dear Maintainer, Python 3.12 changed recursion mechanism [1]  sys.setrecursionlimit() and sys.getrecursionlimit(). The recursion limit  now applies only to Python code. Builtin functions do not use the recursion  limit, but are protected by a different mechanism that prevents recursion  from

Bug#1060698: yubioath-desktop: Doesn't see yubikeys anymore.

2024-01-12 Thread Freagarach
Package: yubioath-desktop Version: 5.1.0-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: freagar...@tuta.io Dear Maintainer, since yesterday the problem holding back python3-ykman (and related packages) was resolved, I upgraded my system today. When trying to use the GUI

Bug#1056476: python-importlib-metadata's autopkg tests fail with Python 3.12

2024-01-12 Thread s3v
Dear Maintainer, > 450s   File > "/tmp/autopkgtest.5EvlHX/autopkgtest_tmp/tests/test_main.py", line 8, in > > 450s import pyfakefs.fake_filesystem_unittest as ffs > 450s   File > "/usr/lib/python3/dist-packages/pyfakefs/fake_filesystem_unittest.py", > line 72, in > 450s from pyfakefs

Bug#1060671: marked as done (libdbd-oracle-perl: requires rebuild for perl 5.38)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Sat, 13 Jan 2024 01:04:19 + with message-id and subject line Bug#1060671: fixed in libdbd-oracle-perl 1.83-2 has caused the Debian Bug report #1060671, regarding libdbd-oracle-perl: requires rebuild for perl 5.38 to be marked as done. This means that you claim that the

Bug#1056474: python-ibm-cloud-sdk-core's autopkg tests fail with Python 3.12

2024-01-12 Thread Yogeswaran Umasankar
Hi, Uploaded a patch in salsa [0] to fix the autopkgtest issue with Py 3.12. Updated the package with new upstream version too. [0] https://salsa.debian.org/python-team/packages/python-ibm-cloud-sdk-core Cheers! signature.asc Description: PGP signature

Bug#1058310: python-ibm-cloud-sdk-core: FTBFS: failed tests

2024-01-12 Thread Yogeswaran Umasankar
Hi, Uploaded a patch in salsa [0] to fix the autopkgtest issue with Py 3.12. Updated the package with new upstream version too. [0] https://salsa.debian.org/python-team/packages/python-ibm-cloud-sdk-core Cheers! signature.asc Description: PGP signature

Bug#1041089: thin-provisioning-tools FTBFS with googletest 1.13.0

2024-01-12 Thread Karsten Kruse
Hello, Is there something else that needs to be done to get the package back into testing? My system prints a "missing binary: /usr/sbin/check_cache" at boot time when assembling my lvmcache(7). Thanks, Karsten

Processed: tagging 1058997

2024-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1058997 + patch Bug #1058997 [src:flask-autoindex] flask-autoindex is incompatible with Py3.12 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058997:

Processed: closing 1052899

2024-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1052899 Bug #1052899 [src:python-fido2] python-fido2: FTBFS: chmod: cannot access 'fido2.egg-info/*': No such file or directory Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1052899:

Bug#1052899: closing 1052899

2024-01-12 Thread Florian Schlichting
close 1052899 thanks python-fido2 1.1.2-2 uploaded to unstable, closing.

Bug#1060455: marked as done (awscli: Please drop python-cryptography upper limit or increase it)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 21:50:11 + with message-id and subject line Bug#1060455: fixed in awscli 2.15.9-1 has caused the Debian Bug report #1060455, regarding awscli: Please drop python-cryptography upper limit or increase it to be marked as done. This means that you claim that

Bug#1060266: marked as done (python3-ykman: Package uninstallable)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 21:35:21 + with message-id and subject line Bug#1060266: fixed in yubikey-manager 5.2.1-1 has caused the Debian Bug report #1060266, regarding python3-ykman: Package uninstallable to be marked as done. This means that you claim that the problem has been

Bug#1060285: marked as done (mptcpd: FTBFS with a segmentation fault in the testsuite when SCTP disabled and no /etc/protocols)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 21:34:24 + with message-id and subject line Bug#1060285: fixed in mptcpd 0.12-3 has caused the Debian Bug report #1060285, regarding mptcpd: FTBFS with a segmentation fault in the testsuite when SCTP disabled and no /etc/protocols to be marked as done.

Bug#1060285: mptcpd: FTBFS with a segmentation fault in the testsuite when SCTP disabled and no /etc/protocols

2024-01-12 Thread Aurelien Jarno
Hi Matthieu, On 2024-01-12 11:06, Matthieu Baerts wrote: > Hi Aurélien, > > On 10/01/2024 19:13, Matthieu Baerts wrote: > > On 08/01/2024 21:18, Aurelien Jarno wrote: > > (...) > > >> In the latest rebuild of mptpcd, the conditions where met only on the > >> riscv64 buildd, and riscv64 is not

Bug#1059040: libxml2: ABI change? (undefined references)

2024-01-12 Thread Rafael Laboissière
* Thorsten Glaser [2024-01-12 17:56]: On Fri, 12 Jan 2024, Rafael Laboissière wrote: experimental, the configure script does detect the absence of the xmlNanoFTPNewCtxt function in the libxml2 library (version 2.12.3+dfsg-0exp1) and disables the call to the xmlNanoFTP* functions.

Bug#1060687: libwacom-dev: Needs Depends: libevdev-dev

2024-01-12 Thread Jeremy Bícha
Source: libwacom Version: 2.9.0-1 Severity: serious libwacom.pc now has this line: Requires.private: gudev-1.0, glib-2.0, libevdev Therefore, please add libevdev-dev to libwacom-dev's Depends. I noticed this issue when building another package that uses libwacom but it was also detected by

Bug#1056764: grub-efi-amd64: can't boot with GRUB 2.12~rc1-12

2024-01-12 Thread debian
Good day, does grub 2.12 (without rc1) help? There are a good pile of fixups between rc1 and release. E.g. https://git.savannah.gnu.org/cgit/grub.git/commit/?h=grub-2.12=1f5b180742ff2706bc3a696d115ddbc677ec75b9 or

Bug#1060455: marked as pending in awscli

2024-01-12 Thread Noah Meyerhans
Control: tag -1 pending Hello, Bug #1060455 in awscli 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:

Processed: Bug#1060455 marked as pending in awscli

2024-01-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1060455 [src:awscli] awscli: Please drop python-cryptography upper limit or increase it Ignoring request to alter tags of bug #1060455 to the same tags previously set -- 1060455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060455 Debian

Bug#1060455: awscli: Please drop python-cryptography upper limit or increase it

2024-01-12 Thread Noah Meyerhans
On Thu, Jan 11, 2024 at 02:27:23PM -0500, Jeremy Bícha wrote: > There is a diff at > https://launchpad.net/ubuntu/+source/awscli/2.14.6-1ubuntu1 for this > issue. You can ignore the build failure since that doesn't seem to > currently affect Debian Unstable. Thanks, I've applied that patch and

Processed: tagging 1060455

2024-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1060455 + pending Bug #1060455 [src:awscli] awscli: Please drop python-cryptography upper limit or increase it Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060455:

Bug#1059525: linux-image-6.1.0-16-amd64: Secure Boot is active but mokutil and dmesg says "Secure boot disabled" but just with an NVME not with an HDD/SSD

2024-01-12 Thread .
In a Debian Testing System one of the packages solved my problem. Secure Boot is now displayed as active. Start-Date: 2024-01-12 18:59:31 Commandline: apt full-upgrade Requested-By: user (1000) Upgrade: orca:amd64 (45.1-2, 45.2-1), dmeventd:amd64 (2:1.02.185-2, 2:1.02.185-3), libldb2:amd64

Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable

2024-01-12 Thread Paul Gevers
Hi, On 12-01-2024 12:36, Chris Hofstaedtler wrote: can you confirm two additional things please: 1) this happens only on the large host? https://ci.debian.net/packages/p/pdns/testing/s390x/41650331/ Seems it happens on our s390x host too (which has 10 debci workers running in parallel).

Bug#1059222: src:pv: fails to migrate to testing for too long: FTBFS on armhf

2024-01-12 Thread Andrew Wood
> This is a quick word to let you know that I've disabled valgrind tests > on armhf in the Debian package. They were failing since the 1.8.5 upload > [...] Thank you, I agree with this approach. The evidence I have seen so far suggests that the failures are due to issues with the way valgrind

Bug#1059040: libxml2: ABI change? (undefined references)

2024-01-12 Thread Thorsten Glaser
On Fri, 12 Jan 2024, Rafael Laboissière wrote: > experimental, the configure script does detect the absence of the > xmlNanoFTPNewCtxt function in the libxml2 library (version > 2.12.3+dfsg-0exp1) and disables the call to the xmlNanoFTP* functions. > However, this rebuilt will not be

Processed: [Pending] django-session-security: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx'

2024-01-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #1042590 [src:django-session-security] django-session-security: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' Added tag(s) pending. -- 1042590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042590 Debian Bug

Bug#1057607: marked as done (sphinx-design: FTBFS: failing tests)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 16:51:08 + with message-id and subject line Bug#1057607: fixed in sphinx-design 0.5.0-2 has caused the Debian Bug report #1057607, regarding sphinx-design: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been dealt

Bug#1042590: [Pending] django-session-security: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx'

2024-01-12 Thread Andreas Tille
Control: tags -1 pending Hi, I've fixed this problem in Git[1] but did not uploaded since autopkgtest is failing in Salsa CI[2]. Kind regards Andreas. [1] https://salsa.debian.org/python-team/packages/django-session-security/-/commit/af1ebc734a33cf1b629a2626bad508b833eb2706 [2]

Processed: bug 1060251 is forwarded to https://bugs.kde.org/show_bug.cgi?id=479699

2024-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1060251 https://bugs.kde.org/show_bug.cgi?id=479699 Bug #1060251 {Done: Paul Gevers } [valgrind] valgrind: apt autopkgtests on armhf fail with: Access not within mapped region Set Bug forwarded-to-address to

Bug#1042674: marked as done (flufl.bounce: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 16:34:34 + with message-id and subject line Bug#1042674: fixed in flufl.bounce 4.0-4 has caused the Debian Bug report #1042674, regarding flufl.bounce: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' to be marked as done. This

Bug#1060067: marked as done (fuse3: FTBFS: dh_missing: error: missing files, aborting)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 16:19:24 + with message-id and subject line Bug#1060067: fixed in fuse3 3.14.0-5 has caused the Debian Bug report #1060067, regarding fuse3: FTBFS: dh_missing: error: missing files, aborting to be marked as done. This means that you claim that the problem

Bug#1060251: Bug#1059352: src:apt: fails to migrate to testing for too long: autopkgtest regression on armhf

2024-01-12 Thread Emanuele Rocca
Hi Julian! On 2024-01-12 01:47, Julian Andres Klode wrote: > Either way, these are harmless I'm not saying they're harmful, what I'm saying is: 1) the errors you see on armhf when building apt without stack-clash-protection are the same valgrind reports on amd64 as well. Hence, you could

Bug#1058192: marked as done (debiancontributors: FTBFS: AttributeError: 'TestTypes' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 15:49:10 + with message-id and subject line Bug#1058192: fixed in debiancontributors 0.7.9-1 has caused the Debian Bug report #1058192, regarding debiancontributors: FTBFS: AttributeError: 'TestTypes' object has no attribute 'assertEquals'. Did you mean:

Bug#1037883: marked as done (vimix: ftbfs with GCC-13)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 15:36:02 + with message-id and subject line Bug#1037883: fixed in vimix 0.7.2+git20221123+ds-2 has caused the Debian Bug report #1037883, regarding vimix: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt

Bug#1056423: [Help] Started to replace future but failed

2024-01-12 Thread Andreas Tille
Am Fri, Jan 12, 2024 at 11:45:02AM +0100 schrieb Alexandre Detiste: > > -class ExtensionNode(with_metaclass(ExtensionNodeMetaclass, object)): > +class ExtensionNode(metaclass=ExtensionNodeMetaclass, object_=True): > > Just simply > +class ExtensionNode(metaclass=ExtensionNodeMetaclass): > , but

Bug#1060432: [Python-modules-team] Bug#1060432: rpds-py ftbfs in unstable

2024-01-12 Thread Roland Mas
Le 11/01/2024 à 10:27, Matthias Klose a écrit : Package: src:rpds-py Version: 0.12.0-2 Severity: serious Tags: sid trixie ftbfs rpds-py ftbfs in unstable, because of missing build dependencies: Issues preventing migration: ∙ ∙ rpds-py unsatisfiable Build-Depends(-Arch) on amd64:

Bug#1058344: marked as done (python-ocspbuilder: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 14:34:42 + with message-id and subject line Bug#1056489: fixed in python-ocspbuilder 0.10.2-3 has caused the Debian Bug report #1056489, regarding python-ocspbuilder: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12

Bug#1060266: [Pkg-auth-maintainers] Some help for coordinated uploads needed

2024-01-12 Thread Philip Rinn
Hi Florian, On 12.01.24 at 12:08, Florian Schlichting: I would like to do an upload of yubikey-manager very soon in order to fix #1060266 (serious) in python3-ykman. Can we perhaps do an upload of python-fido2 to unstable in the course of this weekend? Do you want to do that yourself, so you

Bug#1056489: marked as done (python-ocspbuilder's autopkg tests fail with Python 3.12)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 14:34:42 + with message-id and subject line Bug#1056489: fixed in python-ocspbuilder 0.10.2-3 has caused the Debian Bug report #1056489, regarding python-ocspbuilder's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that

Bug#1058997: flask-autoindex is incompatible with Py3.12

2024-01-12 Thread Alexandre Detiste
control: -1 tag +patch Please apply this patch and remove "python3-future ," from debian/control. Greetings remove-future Description: Binary data

Bug#1060671: libdbd-oracle-perl: requires rebuild for perl 5.38

2024-01-12 Thread Sebastian Ramacher
Source: libdbd-oracle-perl Version: 1.83-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org The perl 5.38 has started. Since libdbd-oracle-perl is in contrib and not auto-buildable, it requires a manual rebuild on amd64 and i386. Cheers -- Sebastian Ramacher

Processed: merging 1056489 1058344

2024-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 1056489 1058344 Bug #1056489 [src:python-ocspbuilder] python-ocspbuilder's autopkg tests fail with Python 3.12 Bug #1056489 [src:python-ocspbuilder] python-ocspbuilder's autopkg tests fail with Python 3.12 Added tag(s) ftbfs. Bug #1058344

Processed: closing 1058125

2024-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Fixed by src:hypercorn-0.16.0-1. > close 1058125 Bug #1058125 [src:hypercorn] hypercorn: FTBFS: make[1]: *** [debian/rules:17: execute_before_dh_sphinxdoc] Error 2 Marked Bug as done > thanks Stopping processing here. Please contact me if you

Bug#1060429: marked as done (solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 13:05:46 + with message-id and subject line Bug#1060429: fixed in python-django-solo 2.1.0-2 has caused the Debian Bug report #1060429, regarding solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py to be marked as

Processed: merging 1056469 1058333

2024-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 1056469 1058333 Bug #1056469 [src:python-docformatter] python-docformatter's autopkg tests fail with Python 3.12 Bug #1056469 [src:python-docformatter] python-docformatter's autopkg tests fail with Python 3.12 Added tag(s) ftbfs. Bug

Bug#1060251: Bug#1059352: src:apt: fails to migrate to testing for too long: autopkgtest regression on armhf

2024-01-12 Thread Julian Andres Klode
On Thu, Jan 11, 2024 at 10:18:58PM +0100, Emanuele Rocca wrote: > Hi Julian, > > On 2024-01-11 05:46, Julian Andres Klode wrote: > > And there aren't any hard errors. We could zero initialize > > those or add supressions to make things look nicer I suppose. > > Mmmh no, they are all actual

Bug#1060323: libosp-dev: missing dependency on libosp5

2024-01-12 Thread gregor herrmann
On Fri, 12 Jan 2024 07:21:14 -0500, Neil Roeth wrote: > I took the second approach suggested by Gregor, of changing the install > order.  Massive rewrite of d/rules to happen at a later date.  :-) Thanks for the quick upload! Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian

Bug#1060323: libosp-dev: missing dependency on libosp5

2024-01-12 Thread Neil Roeth
I took the second approach suggested by Gregor, of changing the install order.  Massive rewrite of d/rules to happen at a later date.  :-) -- Neil Roeth

Bug#1055713: marked as done (python-http-parser ftbfs with Python 3.12)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 12:05:09 + with message-id and subject line Bug#1055713: fixed in python-http-parser 0.9.0+ds-1 has caused the Debian Bug report #1055713, regarding python-http-parser ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem

Processed: closing 1056467

2024-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Fixed by src:python-xmlschema-1.10.0-7. > close 1056467 Bug #1056467 [src:python-djangosaml2] python-djangosaml2's autopkg tests fail with Python 3.12 Marked Bug as done > thanks Stopping processing here. Please contact me if you need

Processed: closing 1058194

2024-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Fixed by src:python-xmlschema-1.10.0-7. > close 1058194 Bug #1058194 [src:python-djangosaml2] python-djangosaml2: FTBFS: AttributeError: type object '_PurePosixPath' has no attribute '_from_parts'. Did you mean: '_load_parts'? Marked Bug as

Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable

2024-01-12 Thread Chris Hofstaedtler
Hi, can you confirm two additional things please: 1) this happens only on the large host? 2) this does not or does happen with other packages also requesting the same settings from systemd, e.g. dnsdist or pdns-recursor? Chris

Bug#1060266: [Pkg-auth-maintainers] Some help for coordinated uploads needed

2024-01-12 Thread Florian Schlichting
Hi Philip, On Sun, Dec 24, 2023 at 10:25:21PM +0100, Philip Rinn wrote: > things changed a bit - Arch Linux picked up my patch and I think with > testing in two distributions, we will have enough momentum to get possible > bugs ironed out. > > I'll prepare an upload of solo1-cli with my patch

Bug#1056423: [Help] Started to replace future but failed

2024-01-12 Thread Alexandre Detiste
Ok I'll pick it up this evening ! -class ExtensionNode(with_metaclass(ExtensionNodeMetaclass, object)): +class ExtensionNode(metaclass=ExtensionNodeMetaclass, object_=True): Just simply +class ExtensionNode(metaclass=ExtensionNodeMetaclass): , but I can't test here: Greetings Le ven. 12 janv.

Bug#1060665: orphan-sysvinit-scripts: needs to ship /etc/init.d/

2024-01-12 Thread Andreas Beckmann
Package: orphan-sysvinit-scripts Version: 0.15 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity.

Processed: [Help] Started to replace future but failed

2024-01-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #1056423 [src:mdp] mdp's autopkg tests fail with Python 3.12 Added tag(s) help. -- 1056423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1056423: [Help] Started to replace future but failed

2024-01-12 Thread Andreas Tille
Control: tags -1 help Hi Alexandre, I started to follow your hint to replace future inside the code but I'm obviously struck as you can see in Salsa-CI[1]. Any help would be welcome (please also review my patch since I'm not sure about all changes). Kind regards Andreas. [1]

Bug#1060429: solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py

2024-01-12 Thread Jérémy Lal
I've reassigned it to solo1-cli, because I thought it wasn't a library (and the start of the docs lead me to it), but actually it is a library. My mistake, re-reassigning to django_solo, the newcomer has to go elsewhere.

Processed: reassign 1060429 to python-django-solo

2024-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1060429 python-django-solo Bug #1060429 [solo1-cli] solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py Bug reassigned from package 'solo1-cli' to 'python-django-solo'. Ignoring request to alter

Processed: reassign 1060429 to solo1-cli

2024-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1060429 solo1-cli Bug #1060429 [python-django-solo] solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py Bug reassigned from package 'python-django-solo' to 'solo1-cli'. No longer marked as found

Bug#1060285: mptcpd: FTBFS with a segmentation fault in the testsuite when SCTP disabled and no /etc/protocols

2024-01-12 Thread Matthieu Baerts
Hi Aurélien, On 10/01/2024 19:13, Matthieu Baerts wrote: > On 08/01/2024 21:18, Aurelien Jarno wrote: (...) >> In the latest rebuild of mptpcd, the conditions where met only on the >> riscv64 buildd, and riscv64 is not a release architecture. That said a >> few mips64el buildds also met the 3

Processed: severity of 1059922 is important

2024-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1059922 important Bug #1059922 [nut-server] nut-server: upsd fails to start since version 2.8.1 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1059922:

Bug#1059922: nut-server: upsd fails to start since version 2.8.1

2024-01-12 Thread Laurent Bigonville
severity  1059922 important thanks > Dear Laurent Bigonville, Hello Jörg, > with version 2.8.0-7 an EATON UPS connected to a debian computer via > USB was working in standalone mode as expected. The only change in the > config files was in /etc/nut/ups.conf where I added the following lines: >

Processed: netplan-generator: ineffective Replaces for /usr/lib/systemd/system-generators/netplan due to /usr-move

2024-01-12 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + netplan.io Bug #1060661 [netplan-generator] netplan-generator: ineffective Replaces for /usr/lib/systemd/system-generators/netplan due to /usr-move Added indication that 1060661 affects netplan.io -- 1060661:

Processed: Re: solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py

2024-01-12 Thread Debian Bug Tracking System
Processing control commands: > found -1 python3-django-solo/2.1.0-1 Bug #1060429 [python-django-solo] solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py The source python3-django-solo and version 2.1.0-1 do not appear to match any binary packages Marked

Bug#1060429: solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py

2024-01-12 Thread Helmut Grohne
Control: found -1 python3-django-solo/2.1.0-1 Control: affects -1 = solo1-cli Philip Rinn wrote: > thanks for the bug report, but I guess you missed that solo1-cli.ships this > file for years (in stable, testing, unstable) while python-django-solo was > just uploaded yesterday. So I think the

Bug#1060661: netplan-generator: ineffective Replaces for /usr/lib/systemd/system-generators/netplan due to /usr-move

2024-01-12 Thread Helmut Grohne
Package: netplan-generator Version: 0.107.1-1 Severity: serious Justification: file loss in package upgrade User: helm...@debian.org Usertags: dep17p1 Control: affects -1 + netplan.io Hi Lukas, netplan was on my radar for /usr-merge for a while, but unfortunately I didn't get down to it before

Bug#1060660: newt: does not trap errors from python extension build (policy 4.6)

2024-01-12 Thread Helmut Grohne
Source: newt Version: 0.52.24-1 Severity: serious Justification: policy 4.6 Debian policy requires that failing a build step makes the package build fail. When the Python extension build fails, the upstream Makefile continues in violation of this policy and may result in a seemingly successful

Bug#1059869: marked as done (autopkgtest fails)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 09:34:24 + with message-id and subject line Bug#1059869: fixed in plakativ 0.5.2-1 has caused the Debian Bug report #1059869, regarding autopkgtest fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1042685: marked as done (flufl.password: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 09:34:09 + with message-id and subject line Bug#1042685: fixed in flufl.password 1.3-6 has caused the Debian Bug report #1042685, regarding flufl.password: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' to be marked as done.

Bug#965837: tart: Change of debhelper compat

2024-01-12 Thread i
On Fri, 12 Jan 2024 17:12:36 +0800 i...@0w.al wrote: > Hi. > > I have changed the compat version from 5 to 13 to fix the build error, and > fixed some lintian warnings > > Clansty > Hi. I forgot to close the bug-id. Here’s the update of the patch. Clansty tart_3.10-1.1.debdiff

Bug#1060658: megapixels don't start could not find any config file

2024-01-12 Thread Pirate Praveen
Package: megapixels Version: 1.7.0-1 Severity: grave Running megapixels from commandline on mobian trixie fails with this error /usr/share/megapixels/config/purism,librem5r4.ini not found.

Bug#1059869: autopkgtest fails

2024-01-12 Thread Johannes Schauer Marin Rodrigues
On 2024-01-11 23:40, Bastian Germann wrote: Ping. It is now 1 week until this will auto-remove several packages. Please consider releasing and packaging the new release. Whoops, sorry!! And thank you for the ping. This has now been taken care of. The version I just uploaded has the

Bug#965837: tart: Change of debhelper compat

2024-01-12 Thread i
Hi. I have changed the compat version from 5 to 13 to fix the build error, and fixed some lintian warnings Clansty tart_3.10-1.1.debdiff Description: Binary data

Bug#1052849: marked as done (python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 08:41:06 + with message-id and subject line Bug#1052849: fixed in python-pkginfo 1.9.6-1 has caused the Debian Bug report #1052849, regarding python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit

Bug#1042599: marked as done (python-pkginfo: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 08:41:06 + with message-id and subject line Bug#1042599: fixed in python-pkginfo 1.9.6-1 has caused the Debian Bug report #1042599, regarding python-pkginfo: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' to be marked as done.

Bug#1055718: python-openstep-plist ftbfs with Python 3.12

2024-01-12 Thread s3v
Dear Maintainer, I was able to build successfully python-openstep-plist/0.3.1-1~exp1 in a sid chroot environment for amd64 architecture. 0.3.1-1~exp1 landed in experimental for a while, Is there some concern that prevents upload to unstable? Please note that this issue affects (at least)

Bug#1042664: marked as done (flufl.enum: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

2024-01-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 08:38:28 + with message-id and subject line Bug#1042664: fixed in flufl.enum 4.1.1-6 has caused the Debian Bug report #1042664, regarding flufl.enum: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' to be marked as done. This

Bug#1058321: python-loompy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-12 Thread s3v
Dear Maintainer, > > E   If you are not working on Numba development, the original error was: > > 'cannot import name '_typeconv' from 'numba.core.typeconv' > > (/usr/lib/python3/dist-packages/numba/core/typeconv/__init__.py)'. > > E   For help, please visit: > > E    > > E   > >

Bug#1052849: [Help] Re: python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2024-01-12 Thread Andreas Tille
Hi Stefano, Am Thu, Jan 11, 2024 at 08:25:46PM + schrieb Stefano Rivera: > > The test is expecting the module to be installed in the test > environment. Either we could try harder to emulate that, or skip the > tests. I admit I tried to copy around the module before running the test with no