Bug#1028513: dovecot: autopkgtest failure with python3.11
Control: tags -1 pending On 1/12/23 08:10, Bas Couwenberg wrote: The attached patch resolves the issue by using python3-passlib which has a pure Python implementation to fall back on when the crypt module is not available. I've uploaded a 0-day NMU with the patch from this issue. The changes are attached and pushed to the repo on Salsa: https://salsa.debian.org/debian/dovecot/-/commits/debian/1%252.3.19.1+dfsg1-2.1 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 diff --git a/debian/changelog b/debian/changelog index 14c1e62e2..22c9a9ce8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +dovecot (1:2.3.19.1+dfsg1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * [b02ebc9] Don't use deprecated crypt module. +(closes: #1028513) + + -- Bas Couwenberg Fri, 20 Jan 2023 07:01:26 +0100 + dovecot (1:2.3.19.1+dfsg1-2) unstable; urgency=medium [ Christian Göttsche ] diff --git a/debian/tests/control b/debian/tests/control index 106e5d04a..496cfcc0b 100644 --- a/debian/tests/control +++ b/debian/tests/control @@ -11,4 +11,4 @@ Restrictions: needs-root, breaks-testbed, allow-stderr Tests: testmails Restrictions: needs-root, breaks-testbed -Depends: dovecot-imapd, dovecot-pop3d, lsb-release, python3 +Depends: dovecot-imapd, dovecot-pop3d, lsb-release, python3, python3-passlib diff --git a/debian/tests/testmails b/debian/tests/testmails index 71ae3caab..3329809b5 100755 --- a/debian/tests/testmails +++ b/debian/tests/testmails @@ -1,6 +1,5 @@ #!/usr/bin/python3 -import crypt import grp import imaplib import os @@ -13,6 +12,8 @@ import subprocess import sys import unittest +from passlib.hash import des_crypt + def random_string(length): '''Return a random string, consisting of ASCII letters, with given @@ -57,7 +58,7 @@ class TestUser: self.salt = random_string(2) self.password = random_string(8) -self.crypted = crypt.crypt(self.password, self.salt) +self.crypted = des_crypt.using(salt=self.salt).hash(self.password) subprocess.check_call(['useradd', '-p', self.crypted, '-m', login])
Processed: Re: dovecot: autopkgtest failure with python3.11
Processing control commands: > tags -1 pending Bug #1028513 [src:dovecot] dovecot: autopkgtest failure with python3.11 Added tag(s) pending. -- 1028513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates, still in testing
Processing commands for cont...@bugs.debian.org:
> found 1026510 11.0.11+0-1.1
Bug #1026510 {Done: tony mancill } [src:openjfx] openjfx:
FTBFS: ReadOnlyJavaBeanObjectPropertyBuilder.java:58: error: invalid use of
@param
Marked as found in versions openjfx/11.0.11+0-1.1.
> reassign 1011535 src:openjfx
Bug #1011535 [openjfx] openjfx: FTBFS with OpenJDK 17 due to javadoc errors
Bug reassigned from package 'openjfx' to 'src:openjfx'.
No longer marked as found in versions openjfx/11.0.11+1-1.
Ignoring request to alter fixed versions of bug #1011535 to the same values
previously set
> forcemerge 1026510 1011535
Bug #1026510 {Done: tony mancill } [src:openjfx] openjfx:
FTBFS: ReadOnlyJavaBeanObjectPropertyBuilder.java:58: error: invalid use of
@param
Bug #1011535 [src:openjfx] openjfx: FTBFS with OpenJDK 17 due to javadoc errors
Marked Bug as done
Marked as fixed in versions openjfx/11.0.11+1-2.
Marked as found in versions openjfx/11.0.11+0-1.1 and openjfx/11.0.11+1-1.1.
Merged 1011535 1026510
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1011535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011535
1026510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1028617: marked as done (ipython: autopkgtest is faling after updating pygments to 2.14.0+dfsg-1)
Your message dated Fri, 20 Jan 2023 07:37:32 + with message-id and subject line Bug#1028617: fixed in ipython 8.5.0-4 has caused the Debian Bug report #1028617, regarding ipython: autopkgtest is faling after updating pygments to 2.14.0+dfsg-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1028617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ipython Version: 8.5.0-3 Severity: serious Dear Maintainer, after the upload of pygments 2.14.0+dfsg-1 your package is failung while running the autopkgtest. The failed part in detail is: === FAILURES === _ TestLexers.testIPythonLexer __ self = def testIPythonLexer(self): fragment = '!echo $HOME\n' tokens = [ (Token.Operator, '!'), ] tokens.extend(self.bash_lexer.get_tokens(fragment[1:])) > self.assertEqual(tokens, list(self.lexer.get_tokens(fragment))) E AssertionError: Lists differ: [(Tok[78 chars] (Token.Name.Variable, '$HOME'), (Token.Text.Whitespace, '\n')] != [(Tok[78 chars] (Token.Name.Variable, '$HOME'), (Token.Text, '\n')] E E First differing element 4: E (Token.Text.Whitespace, '\n') E (Token.Text, '\n') E E [(Token.Operator, '!'), E (Token.Name.Builtin, 'echo'), E (Token.Text.Whitespace, ' '), E (Token.Name.Variable, '$HOME'), E - (Token.Text.Whitespace, '\n')] E ? --- E E + (Token.Text, '\n')] IPython/lib/tests/test_lexers.py:25: AssertionError Updating the package to version 8.8.0 should fix the issue, it's containing the commit https://github.com/ipython/ipython/commit/ed7f35f8b721d4b4dcafea173ce724bee25704c7 which addresses the changes done by recent pygments. Regards Carsten -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/20 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: ipython Source-Version: 8.5.0-4 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of ipython, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated ipython package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 20 Jan 2023 08:19:58 +0100 Source: ipython Architecture: source Version: 8.5.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jochen Sprickerhof Closes: 1028617 Changes: ipython (8.5.0-4) unstable; urgency=medium . * Team upload. * Add upstream patch for pygments > 2.14 (Closes: #1028617) Checksums-Sha1: f01773757a09d1c84502c4bdc467123d14b04a9b 2732 ipython_8.5.0-4.dsc 701e78b26fe649aae984e3822d569cbf482cb7c0 11000 ipython_8.5.0-4.debian.tar.xz e2fde2cfb4c7df12b971c8eb55454f64f4d84ac6 7537 ipython_8.5.0-4_source.buildinfo Checksums-Sha256: e138e68fb5e79e03104a8551fa6cebc898278dc5ae090206ad795453fe68f17f 2732 ipython_8.5.0-4.dsc 47fbe0c131939bf06dd4012d9966497d87d84c3ee78a5ed1b245cb2617b0698b 11000 ipython_8.5.0-4.debian.tar.xz 837636b789f205b430e1d5b64d118fee57dad71a5ea9876ff60f1d916e56fbb4 7537 ipython_8.5.0-4_source.buildinfo Files: 5a36f3b978bc37624d5ee3fb2c71839a 2732 python optional ipython_8.5.0-4.dsc 0cde6e79282f642056b475cc5df96cf0 11000 python optional ipython_8.5.0-4.debian.tar.xz 28a2114c094bf992c5ed028cbf507aab 7537 python optional ipython_8.5.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmPKQd0ACgkQW//cwljm lDMo7g//fhbxhkwIs5wBro2PJfrbDGALlRNr3Me0PBj+ArpJlIZtKTec/hrsOk0J
Bug#1028617: marked as pending in ipython4
Control: tag -1 pending Hello, Bug #1028617 in ipython4 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/python-team/packages/ipython/-/commit/2253653a27dfbdb7d998aea446fa39bf055c20de Add upstream patch for pygments > 2.14 Closes: #1028617 (this message was generated automatically) -- Greetings https://bugs.debian.org/1028617
Processed: Bug#1028617 marked as pending in ipython4
Processing control commands: > tag -1 pending Bug #1028617 [src:ipython] ipython: autopkgtest is faling after updating pygments to 2.14.0+dfsg-1 Added tag(s) pending. -- 1028617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015123: latex-cjk-chinese-arphic: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Am 20.12.2022 um 04:08 teilte Danai SAE-HAN (韓達耐) mit: Hi, Sorry, I forgot all about this! I figured out it was a regression so in Unstable you need to go two versions back for Fontforge, which will ignore the warnings instead of halting the process. I'll be back home on 30 December. Meanwhile I'll send a message upstream. With the latest upload of fontforge the issue is solved: #1015092 . We could simply close the bug or tighten the build dep. Hilmar -- sigfault
Processed: fixed 1029174 in 9.4.1-14
Processing commands for cont...@bugs.debian.org: > fixed 1029174 9.4.1-14 Bug #1029174 [dhcpcd-base] dhcpcd-base: Brakes networking completely Marked as fixed in versions dhcpcd5/9.4.1-14. > thanks Stopping processing here. Please contact me if you need assistance. -- 1029174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029066: diffoscope: FTBFS if no internet is available (using internet connection during build)
* Chris Lamb [2023-01-20 01:47]:
[...]
> As to a solution, though, I think this is somewhat blocking on Mattia's
> expertise in the generation of the Python test recommends. Are we, in
> essence, trying to parse the following data in setup.py?
>
> install_requires=[
> "python-magic",
> "libarchive-c",
> ],
> extras_require={
> "distro_detection": ["distro"],
> "cmdline": ["argcomplete", "progressbar"],
> "comparators": [
> "androguard",
> "binwalk",
> "defusedxml",
> "guestfs",
> "jsondiff",
> "python-debian",
> "pypdf",
> "pyxattr",
> "rpm-python",
> "tlsh",
> ],
> },
>
> If so, we don't necessarily have to wholesale move to pyproject.toml;
> instead, we could rejig setup.py...?
It seems that way. And doing so via pep517, which uses pip to install
the requirements in a temporary environment, which I assume is why it
accesses the network sometimes (but not always): to install missing
requirements when the Debian package is not already installed on the
system.
I've proposed an MR [1] that moves the extras_require to a JSON file
and uses that from both setup.py and generate-recommends.py; I've
confirmed it produces the same debian/tests/control.tmp as before.
- FC
[1] https://salsa.debian.org/reproducible-builds/diffoscope/-/merge_requests/121
Bug#1029066: diffoscope: FTBFS if no internet is available (using internet connection during build)
Hi all,
> […]
As Mattia writes on the Salsa bug [0], I now don't think this is a
network issue. In other words, the package FTBFS regardless of whether
you have network access or not.
To make debugging this easier, I've split out the inline Python code
in c341b63a [1], and simply running the new script results in:
$ ping -q -c1 google.com 2>&1 | grep packet
1 packets transmitted, 1 received, 0% packet loss, time 0ms
$ debian/tests/generate-recommends.py
ERROR: Could not find an activated virtualenv (required).
Traceback (most recent call last):
File
"/home/lamby/git/debian/reproducible-builds/diffoscope/debian/tests/generate-recommends.py",
line 7, in
dist = meta.load(".")
^^
File "/usr/lib/python3/dist-packages/pep517/meta.py", line 72, in load
path = Path(build_as_zip(builder))
^
File "/usr/lib/python3/dist-packages/pep517/meta.py", line 59, in
build_as_zip
builder(dest=out_dir)
File "/usr/lib/python3/dist-packages/pep517/meta.py", line 53, in build
env.pip_install(system['requires'])
File "/usr/lib/python3/dist-packages/pep517/envbuild.py", line 103, in
pip_install
check_call(
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3', '-m',
'pip', 'install', '--ignore-installed', '--prefix',
'/tmp/pep517-build-env-jzvg739_', 'setuptools', 'wheel']' returned
non-zero exit status 3.
Regarding when this was introduced, I think a confounding factor is
that this behaviour is reliant on the behaviour of the python3-pep517
package. (Maybe this *was* a network-related issue in the past as
well… but this matters very little now.)
As to a solution, though, I think this is somewhat blocking on Mattia's
expertise in the generation of the Python test recommends. Are we, in
essence, trying to parse the following data in setup.py?
install_requires=[
"python-magic",
"libarchive-c",
],
extras_require={
"distro_detection": ["distro"],
"cmdline": ["argcomplete", "progressbar"],
"comparators": [
"androguard",
"binwalk",
"defusedxml",
"guestfs",
"jsondiff",
"python-debian",
"pypdf",
"pyxattr",
"rpm-python",
"tlsh",
],
},
If so, we don't necessarily have to wholesale move to pyproject.toml;
instead, we could rejig setup.py...?
Chris
[0]
https://salsa.debian.org/reproducible-builds/diffoscope/-/issues/325#note_366185
[1]
https://salsa.debian.org/reproducible-builds/diffoscope/commit/c341b63a4c8cfe56be883b43b4e4faff71fc060e
Bug#1028877: flask-dance: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
Hello, I have uploaded a fix for this bug to Ubuntu, and uploaded it to the DELAYED/5 queue also. If you would rather this be a team upload or would like the delay shortened, please do let me know. Thanks, -- Simon Quigley si...@tsimonq2.net tsimonq2 on LiberaChat and OFTC @tsimonq2:linuxdelta.com on Matrix 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 OpenPGP_signature Description: OpenPGP digital signature
Bug#1024428: marked as done (lava: CVE-2022-45132: Code execution in jinja templates)
Your message dated Thu, 19 Jan 2023 23:50:30 + with message-id and subject line Bug#1024428: fixed in lava 2023.01-1 has caused the Debian Bug report #1024428, regarding lava: CVE-2022-45132: Code execution in jinja templates to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lava Version: 2022.10-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for lava. CVE-2022-45132[0]: | In Linaro Automated Validation Architecture (LAVA) before 2022.11.1, | remote code execution can be achieved through user-submitted Jinja2 | template. The REST API endpoint for validating device configuration | files in lava-server loads input as a Jinja2 template in a way that | can be used to trigger remote code execution in the LAVA server. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-45132 https://www.cve.org/CVERecord?id=CVE-2022-45132 [1] https://lists.lavasoftware.org/archives/list/lava-annou...@lists.lavasoftware.org/thread/WHXGQMIZAPW3GCQEXYHC32N2ZAAAIYCY/ [2] https://git.lavasoftware.org/lava/lava/-/commit/ab17e8304f10c7c0fe912067f2ed85a4753241c7 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: lava Source-Version: 2023.01-1 Done: Rémi Duraffort We believe that the bug you reported is fixed in the latest version of lava, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rémi Duraffort (supplier of updated lava package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 19 Jan 2023 10:23:15 +0100 Source: lava Architecture: source Version: 2023.01-1 Distribution: unstable Urgency: medium Maintainer: Debian LAVA team Changed-By: Rémi Duraffort Closes: 1016849 1024428 1024429 Changes: lava (2023.01-1) unstable; urgency=medium . * LAVA Software 2023.01 release - Adds alternative dependency on telnet-client (Closes: #1016849) - Includes fix for Code execution in jinja templates [CVE-2022-45132] (Closes: #1024428) - Includes fix for Recursive XML entity expansion [CVE-2022-44641] (Closes: #1024429) . [ Antonio Terceiro ] * [c3eb0b19e] debian/tests/management: fix device management command Checksums-Sha1: 2a65ce6f1ba3f96dcb452fa7c9164f4ccd78e313 2946 lava_2023.01-1.dsc 9646714ca2f5b020461fe2a5820f7f40e0524fae 7564634 lava_2023.01.orig.tar.gz cb5511ed8dae7ac6e37e17bc8d183ece03bf1f1a 92456 lava_2023.01-1.debian.tar.xz de860bde34441609acc554879c414041657cde88 10160 lava_2023.01-1_source.buildinfo Checksums-Sha256: 3904cfe7d2c87dabf65bf768af83c11c70143f97b4415532f1a1215b4d449fc7 2946 lava_2023.01-1.dsc a57c7859af44e23694d2026636dff91b10cab1dade32e7815e7d59a03877899e 7564634 lava_2023.01.orig.tar.gz c76dd479ee4e43b798b56b475915128ab595df7f43da163de4258a3741bbe7b9 92456 lava_2023.01-1.debian.tar.xz aad4575854d9a7a3f9eb4670ebeb7ceb9c2a69fe4d6d4a3ba61728974566f5b3 10160 lava_2023.01-1_source.buildinfo Files: c4b026af17fdff3d7abf87f352f1b24d 2946 net optional lava_2023.01-1.dsc e307355a5abaa03ffbc4a28ea8dfc3e8 7564634 net optional lava_2023.01.orig.tar.gz 5de37c3ef61f5b624d80220e7a3f10a4 92456 net optional lava_2023.01-1.debian.tar.xz 5c5facb425c527407907f47152ef90af 10160 net optional lava_2023.01-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmPJ0doACgkQ/A2xu81G C94SFw/9Hu4PgeaYtIXouwo8/yaSRD5M1asSyLGTlzyVCUN3/WtW7V3JId6W/Bjl PtqduxZdjKG9Iftx4QYrP7TNog4vSTDy9lmnqwcbXirbeht/R11h0COWevYNBe9K 48Mzll9hIOShHxSC94WDh6cdnCszF8LE/noRw+RpT95oUS6e9SGv0fvnb3XmKDp2 iJNljKoGXsF72nuvOoDQSczXCVacF1htxCOIAX4TEUgrJN11SK9CIUui26CJslQr
Bug#1028416: systemctl kexec doesn't shutdown system properly and corrupts mounted filesystems
On 1/11/23 15:40, Michael Biebl wrote: Control: reassign -1 kexec-tools Am 10.01.23 um 20:34 schrieb KOLANICH: Package: systemd Version: 252.4-1 Severity: grave So do kexec-tools if a user has chosen to use it for reboots during package configuration. Either of the following can cause fs corruption (to the point one has to use `fsck -y`): a) the procedure described in https://wiki.archlinux.org/title/Kexec#Manually 1. `kexec -l /boot/vmlinuz-6.0.0-6-amd64 --initrd=/boot/initrd-6.0.0-6-amd64 --reuse-cmdline` 2. `systemctl kexec` b) Just choosing to use kexec for reboots when installing it, and then rebooting. Since systemd basically just calls kexec [1] and running kexec directly shows the same issue, let's reassign this to kexec-tools Michael [1] https://github.com/systemd/systemd/blob/main/src/shutdown/shutdown.c#L584 Can you give me the version of kexec-tools package that you saw this issue with? Thanks, Khalid
Processed: Re: ffado-mixer-qt4 fails to start with python 3.10
Processing control commands: > severity -1 grave Bug #1017907 [ffado-mixer-qt4] ffado-mixer-qt4 fails to start with python 3.10 Severity set to 'grave' from 'normal' -- 1017907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014166: Is this still accurate?
Hi, On Thu, Jan 19, 2023 at 04:56:44PM -0500, Ben Westover wrote: > Hello, > > The CVE description states that versions 0.12.0 - 0.21.1 are vulnerable, but > this package is currently version 22.0. Can this bug be closed? A CVE description might only refer to a specific point in time's state and might not be accurate. It needs first to be confirmed the issue would be fixed in 0.22.0. What are the references confirming the CVE is fixed in 0.22.0? Can you refer to them so we can re-check? Regards, Salvatore
Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Hi, On Thu, Jan 19, 2023 at 04:12:14PM +0100, Sebastian Reichel wrote: > On Wed, Jan 18, 2023 at 09:48:33PM +, Martin wrote: > > Control: severity -1 grave > > > > Justification for grave: Crashes Gajim for some users. RC, IMHO. If I understood it correctly libproxy is only used by glib networking code when not running GNOME. > > On 2023-01-17 21:56, Sebastian Reichel wrote: > > > I just got the new package through testing and now gajim segfaults > > > ony my system with stacktrace pointing to libproxy. So this is not > > > magically solved. > > > > :-( > > > > Could you check, if a downgrade to libproxy 0.4.15-15 helps? > > That certainly helps to find the bug! > > I tried downgrading libproxy1v5 and libproxy-tools to 0.4.15-15 and > glib-networking to 2.66.0. This did not change anything. > > With libproxy from testing gajim does work when being downgraded to > 1.5.4-1 (which requires also downgrading python3-nbxmpp to > 3.2.5-1 to be functional). This has been reported upstream: https://github.com/libproxy/libproxy/issues/199 Also these apparently describe the same bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970687 https://github.com/exaile/exaile/issues/737 Both workarounds mentioned in those bug reports (removing either /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so or /usr/lib/x86_64-linux-gnu/libproxy.so.1.0.0) fix the crash and gajim successfully connects. -- Sebastian signature.asc Description: PGP signature
Bug#1014166: Is this still accurate?
Hello, The CVE description states that versions 0.12.0 - 0.21.1 are vulnerable, but this package is currently version 22.0. Can this bug be closed? Thanks, -- Ben Westover OpenPGP_signature Description: OpenPGP digital signature
Bug#1029182: Just rebuild with psycopg 3.1.7-4
I noticed this bug, and similar for python-pgspecial. You can fix it by rebuilding with python3-psycopg 3.1.7-4, like I've just done with python-pgspecial. Long story short - dh_python3 has hardcoded mapping of psycopg to python3-psycopg3, and this is added to binary dependencies via python3:Depends; you can find details in https://lists.debian.org/debian-python/2023/01/msg00051.html I added pydist override to psycopg 3.1.7-4. I also experimented a bit with rebuilding pgcli; you could replace line 28 of debian/control python3-psycopg | python3-psycopg3 (>= 3.0.14) with python3-psycopg, (see attached diff file) and it'll generate proper dependency on python3-psycopg (>= 3.0.14). Full dependency after this change looks like: Depends: python3-cli-helpers, python3-pendulum, python3-pgspecial (>= 2), python3-pkg-resources, python3-prompt-toolkit (>= 3.0), python3- psycopg (>= 3.0.14), python3-sqlparse (>= 0.3), python3-tabulate, python3-terminaltables, python3-click, python3-configobj, python3- pygments, python3-setproctitle, python3:any Best regards. -- Tomasz Rybak, Debian Developer GPG: A565 CE64 F866 A258 4DDC F9C7 ECB7 3E37 E887 AA8C diff --git a/debian/control b/debian/control index c414842..9cc1f84 100644 --- a/debian/control +++ b/debian/control @@ -25,7 +25,7 @@ Depends: python3-pgspecial (>= 2), python3-pkg-resources, python3-prompt-toolkit (>= 3.0), - python3-psycopg | python3-psycopg3 (>= 3.0.14), + python3-psycopg, python3-sqlparse (>= 0.3), python3-tabulate, python3-terminaltables, signature.asc Description: This is a digitally signed message part
Bug#1028748: marked as done (bottleneck: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13)
Your message dated Thu, 19 Jan 2023 21:19:46 +
with message-id
and subject line Bug#1028748: fixed in bottleneck 1.3.5+ds1-2
has caused the Debian Bug report #1028748,
regarding bottleneck: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.10 3.11" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1028748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bottleneck
Version: 1.3.5+ds1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 setup.py build_ext --inplace
> running build_ext
> running config
> building 'bottleneck.reduce' extension
> creating build
> creating build/temp.linux-x86_64-cpython-311
> creating build/temp.linux-x86_64-cpython-311/bottleneck
> creating build/temp.linux-x86_64-cpython-311/bottleneck/src
> x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
> -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.11
> -Ibottleneck/src -c bottleneck/src/reduce.c -o
> build/temp.linux-x86_64-cpython-311/bottleneck/src/reduce.o -O2
> creating build/lib.linux-x86_64-cpython-311
> creating build/lib.linux-x86_64-cpython-311/bottleneck
> x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2
> -Wl,-z,relro -Wl,-z,now -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2
> build/temp.linux-x86_64-cpython-311/bottleneck/src/reduce.o
> -L/usr/lib/x86_64-linux-gnu -o
> build/lib.linux-x86_64-cpython-311/bottleneck/reduce.cpython-311-x86_64-linux-gnu.so
> building 'bottleneck.move' extension
> creating build/temp.linux-x86_64-cpython-311/bottleneck/src/move_median
> x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
> -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.11
> -Ibottleneck/src -c bottleneck/src/move.c -o
> build/temp.linux-x86_64-cpython-311/bottleneck/src/move.o -O2
> x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
> -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.11
> -Ibottleneck/src -c bottleneck/src/move_median/move_median.c -o
> build/temp.linux-x86_64-cpython-311/bottleneck/src/move_median/move_median.o
> -O2
> x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2
> -Wl,-z,relro -Wl,-z,now -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-cpython-311/bottleneck/src/move.o
> build/temp.linux-x86_64-cpython-311/bottleneck/src/move_median/move_median.o
> -L/usr/lib/x86_64-linux-gnu -o
> build/lib.linux-x86_64-cpython-311/bottleneck/move.cpython-311-x86_64-linux-gnu.so
> building 'bottleneck.nonreduce' extension
> x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
> -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.11
> -Ibottleneck/src -c bottleneck/src/nonreduce.c -o
> build/temp.linux-x86_64-cpython-311/bottleneck/src/nonreduce.o -O2
> x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2
> -Wl,-z,relro -Wl,-z,now -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2
> build/temp.linux-x86_64-cpython-311/bottleneck/src/nonreduce.o
> -L/usr/lib/x86_64-linux-gnu -o
>
Processed: now in testing, too
Processing commands for cont...@bugs.debian.org:
> # fontconfig 2.14.1 migrated to testing
> found 1029104 1:7.4.4~rc2-2
Bug #1029104 {Done: Rene Engelhard } [src:libreoffice] FTBFS
with fontconfig 2.14.1 (doesn't expect RGB stripes
Marked as found in versions libreoffice/1:7.4.4~rc2-2.
> found 1029104 1:7.4.4~rc2-2+b2
Bug #1029104 {Done: Rene Engelhard } [src:libreoffice] FTBFS
with fontconfig 2.14.1 (doesn't expect RGB stripes
The source 'libreoffice' and version '1:7.4.4~rc2-2+b2' do not appear to match
any binary packages
Marked as found in versions libreoffice/1:7.4.4~rc2-2+b2.
> tag 1029104 + bullseye
Bug #1029104 {Done: Rene Engelhard } [src:libreoffice] FTBFS
with fontconfig 2.14.1 (doesn't expect RGB stripes
Added tag(s) bullseye.
> tag 1029104 + sid
Bug #1029104 {Done: Rene Engelhard } [src:libreoffice] FTBFS
with fontconfig 2.14.1 (doesn't expect RGB stripes
Added tag(s) sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1029104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#1028748 marked as pending in bottleneck
Processing control commands:
> tag -1 pending
Bug #1028748 [src:bottleneck] bottleneck: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
Added tag(s) pending.
--
1028748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1028748: marked as pending in bottleneck
Control: tag -1 pending Hello, Bug #1028748 in bottleneck 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/python-team/packages/bottleneck/-/commit/1e9826700e19c07757d48a71856998f8ff3219d1 Cherry-pick upstream patch to fix numpy 1.24 FTBFS (Closes: #1028748) (this message was generated automatically) -- Greetings https://bugs.debian.org/1028748
Bug#1029183: marked as done (python-pgspecial: Dependency and build dependency must be updated to python3-psycopg3 -> python3-psycopg)
Your message dated Thu, 19 Jan 2023 20:40:13 + with message-id and subject line Bug#1029183: fixed in python-pgspecial 2.0.1-2 has caused the Debian Bug report #1029183, regarding python-pgspecial: Dependency and build dependency must be updated to python3-psycopg3 -> python3-psycopg to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1029183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pgspecial Version: 2.0.1-1 Severity: serious Tags: ftbfs Control: affects -1 python3-pgspecial python3-psycopg3 does not exist anymore, see #1016031. --- End Message --- --- Begin Message --- Source: python-pgspecial Source-Version: 2.0.1-2 Done: Tomasz Rybak We believe that the bug you reported is fixed in the latest version of python-pgspecial, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tomasz Rybak (supplier of updated python-pgspecial package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 19 Jan 2023 20:30:41 +0100 Source: python-pgspecial Architecture: source Version: 2.0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Tomasz Rybak Closes: 1029183 Changes: python-pgspecial (2.0.1-2) unstable; urgency=medium . * Team upload. * Fix psycopg dependency (Closes: #1029183). * Bump Standards-Version to 4.6.2. Checksums-Sha1: fe1cd3e358bc5f027f0447a9db9ccd7feac7d86a 2108 python-pgspecial_2.0.1-2.dsc d8c524368060d1df0f97085406630bb079ecfdad 3072 python-pgspecial_2.0.1-2.debian.tar.xz c0b2fd6607e9a839cd37a7573abff5d21c69215e 6924 python-pgspecial_2.0.1-2_amd64.buildinfo Checksums-Sha256: 474dd1fa6c5df4ce7708bf0b7339fe3564ecf91d963be3fa25bf9ac6aeb3a3bd 2108 python-pgspecial_2.0.1-2.dsc e3f0aba3694137f59bdc0219503da00fe2b9a35d309e169eff93a3610f564c7c 3072 python-pgspecial_2.0.1-2.debian.tar.xz a09c1900b6c87806c37b213e291c117f762fdbeeb3975cb2fe65635f8c7e6e3c 6924 python-pgspecial_2.0.1-2_amd64.buildinfo Files: b6a92f9aabf131071a79abab01c24b07 2108 python optional python-pgspecial_2.0.1-2.dsc f44b4114420acbce49b68f3060c9f4b8 3072 python optional python-pgspecial_2.0.1-2.debian.tar.xz fc66354de6fcf3ae3b83d729f76d5c66 6924 python optional python-pgspecial_2.0.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE1bhtbqZEgXjcK9cyggqgxGY3jWkFAmPJm8YACgkQggqgxGY3 jWl2AA/+It0j8kVG33iqPKTB7tfqA/ffNlu/6rdUl6a34BUKqPy9JdJlXNv6ytbk SgKDm+3eGVyD6hN65OP+Q+r/ofWqyAwIP42y6SnQZjAueAZ2vlPh5CnRYRmaFu3d PO6dISnQ/ruZ3hpujzsuhC4d5lT650n2Yi6BnlHc85H72YUhr+MpuNDlHOvmnWGW dU1kRyzzySTo3KWZ1cFXj+lpB9s6OlEzkG2bfdfR4SUJHyOlJJjh1WBZSKUTiMZj UakOItl1B9j/zsUccRgrv5ggnFpRzl8fgJoa6MapqRoqHbszradQmPJ9j+f7QaVS RzYAxcvsZ2y+YBnzcj5/JmhqxYHYH+24CU593baIy+q+jJbgSF+ovVsceFPXRjOw f0lqgAOP6Zoc8+V4R6syOc72Cgv8G3DMZtTduKBeM+0la7482E1DqUI0jHpfXjnN +yfTUc9LlgouIcQjaKk4onohEJ/I3VX0SNVxCzLN++BsgUgK72dpLa/5ybAvvJE6 lQJ2b6Tz129Eo2+hgF3h8d8v9whVrOoAOZ10NXLNEjW9hcGlsvayQpgUVr9FVuMm 5ahOjqVyYjAfREbqSO6zr6GvFDCD15IgQimKDNj2Y+y0t49sna8P1WOAyEJPbP9K iGWT0dUGSqk/AOc6u+6okW0sVnVk8z7JHnIJNkzTl5cV+DBkGSU= =IUEE -END PGP SIGNATURE End Message ---
Bug#1029174: Bug#1029176: please check dhcpcd 9.4.1-14 in unstable
On 19.01.23 16:35, Martin-Éric Racine wrote: Greetings, Something tells me that both of you have encountered the same bug. Yes, I assumed so, too. We've just pushed dhcpcd 9.4.1-14 into unstable. Can you please check whether that fixes it? Indeed, this new version works. Thanks! Beat -- https://drbeat.li tel:+41-79-7706774 gpg: 0x506A903A; 49D5 794A EA77 F907 764F D89E 304B 93CF 506A 903A icbm: 47.0452 N, 7.2715 E "It takes love over gold, and mind over matter" — Dire Straits
Bug#1029174: dhcpcd-base: Brakes networking completely
Package: dhcpcd-base Followup-For: Bug #1029174 X-Debbugs-Cc: krzpyrk...@gmail.com Dear Maintainer, I've ran onto the same issue on a riscv64 board yesteday. Upgrading to 9.4.1-14 solved the problem.
Bug#1029212: marked as done (libgraphicsmagick-q16-3: hardcode depends on libtiff5.)
Your message dated Thu, 19 Jan 2023 19:34:20 + with message-id and subject line Bug#1029212: fixed in graphicsmagick 1.4+really1.3.40-2 has caused the Debian Bug report #1029212, regarding libgraphicsmagick-q16-3: hardcode depends on libtiff5. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1029212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgraphicsmagick-q16-3 Version: 1.4+really1.3.39-2 Severity: serious libgraphicsmagick-q16-3 has a hardcoded dependency on libtiff5, so even after binnmuing for the tiff transition it still depends on it This affects both the version in bookworm and the version in sid, I have not checked other versions. --- End Message --- --- Begin Message --- Source: graphicsmagick Source-Version: 1.4+really1.3.40-2 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of graphicsmagick, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated graphicsmagick package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 19 Jan 2023 19:44:45 +0100 Source: graphicsmagick Architecture: source Version: 1.4+really1.3.40-2 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 1029212 Changes: graphicsmagick (1.4+really1.3.40-2) unstable; urgency=medium . * Don't force tiff dependency, let shlibs handle it (closes: #1029212). Checksums-Sha1: df4f2326212decd09ae15db3847ccb4b34e67fcc 3208 graphicsmagick_1.4+really1.3.40-2.dsc bc8165b94636d6c773cdb8e0581f888fdc55b42f 156804 graphicsmagick_1.4+really1.3.40-2.debian.tar.xz Checksums-Sha256: 4ea2666a74c3af7f2d41f39ba3e545b007f963ab03bb8a275ec815df60e44c3a 3208 graphicsmagick_1.4+really1.3.40-2.dsc c6bb72bba79fb130974ace01d9e0bf6bef4bdf2be38566c0552805a8b52cbd22 156804 graphicsmagick_1.4+really1.3.40-2.debian.tar.xz Files: f0775741dee11eb47de8c33435182935 3208 graphics optional graphicsmagick_1.4+really1.3.40-2.dsc bf8c7ada0b6be8c503aeb226e204a043 156804 graphics optional graphicsmagick_1.4+really1.3.40-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmPJl+UACgkQ3OMQ54ZM yL+WiQ/9GGU8mPGB++7bXgIXt+3bATJ+VeNuFpaZeoSNo5kla4QzgKRKP/x5Gtxr CUysLQ4axC33bCcOEiG8I8u8WdXU4tbbYuHIwxPQyAvprpSxT4a/jGc3KNnqGmdn lCfpFbXfFO6u1RzU96ufsz1Gtb0ESVFpkh4CQU1EFY11V6Eowx4DGbbon3Bup+ow yKMe4PMR+hHQQUsKYgwDPNuRco7BZWPYJfNeMqhie/p8JTfduiuxfpfbu3FGAWx8 EMVLdTYEsam0i4eXkKiSo0QwmW2oaOmTMiqpDX//TDUcSY61mGWa1D/vWh3s77jD WfUTNmI74iqfhpNNx2nqYWdPpfhBgHGI0Qb4+yvJLKnUd3luiVGnoJcnpsaWqLte KaKeTax8ljPoChIjZNeWP4jAyvGktV6szv2j0aA731FyuI8lkHd+t5j1+NW0Z5Dy t4wUSI9k/X8U7cqhHqaxsw0qtN5531ZAfk3nl0Gg2ZfeHI6LdDmkp1YzldCtAqK0 fSgnGrVzlEsrdosLVkMQDfxXTqSnCTmEcNF6i0V1n/fEGAt26pH9R9A1gxqfOtmo XES7j9jj6Pamh4F+XvJEUqWCGxSim+3V2pYVcHqobGcbjGc517r41Y2Wba/FcvUU RMer44cjhNGwngXOt53PBmCpZP3Kva53JEPluMyRCl55fkgcymo= =CB3T -END PGP SIGNATURE End Message ---
Bug#1029213: marked as done (libgraphicsmagick-q16-3 has a hardcoded dependency on libtiff5)
Your message dated Thu, 19 Jan 2023 19:34:20 +
with message-id
and subject line Bug#1029212: fixed in graphicsmagick 1.4+really1.3.40-2
has caused the Debian Bug report #1029212,
regarding libgraphicsmagick-q16-3 has a hardcoded dependency on libtiff5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1029212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgraphicsmagick-q16-3
Version: 1.4+really1.3.39-2
Severity: serious
libgraphicsmagick-q16-3 has a hardcoded dependency on the cruft libtiff5:
https://sources.debian.org/src/graphicsmagick/1.4%2Breally1.3.40-1/debian/control/#L44
Please drop this, ${shlibs:Depends} already generates a correct dependency
on libtiff6.
--- End Message ---
--- Begin Message ---
Source: graphicsmagick
Source-Version: 1.4+really1.3.40-2
Done: Laszlo Boszormenyi (GCS)
We believe that the bug you reported is fixed in the latest version of
graphicsmagick, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1029...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) (supplier of updated graphicsmagick
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 19 Jan 2023 19:44:45 +0100
Source: graphicsmagick
Architecture: source
Version: 1.4+really1.3.40-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS)
Changed-By: Laszlo Boszormenyi (GCS)
Closes: 1029212
Changes:
graphicsmagick (1.4+really1.3.40-2) unstable; urgency=medium
.
* Don't force tiff dependency, let shlibs handle it (closes: #1029212).
Checksums-Sha1:
df4f2326212decd09ae15db3847ccb4b34e67fcc 3208
graphicsmagick_1.4+really1.3.40-2.dsc
bc8165b94636d6c773cdb8e0581f888fdc55b42f 156804
graphicsmagick_1.4+really1.3.40-2.debian.tar.xz
Checksums-Sha256:
4ea2666a74c3af7f2d41f39ba3e545b007f963ab03bb8a275ec815df60e44c3a 3208
graphicsmagick_1.4+really1.3.40-2.dsc
c6bb72bba79fb130974ace01d9e0bf6bef4bdf2be38566c0552805a8b52cbd22 156804
graphicsmagick_1.4+really1.3.40-2.debian.tar.xz
Files:
f0775741dee11eb47de8c33435182935 3208 graphics optional
graphicsmagick_1.4+really1.3.40-2.dsc
bf8c7ada0b6be8c503aeb226e204a043 156804 graphics optional
graphicsmagick_1.4+really1.3.40-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmPJl+UACgkQ3OMQ54ZM
yL+WiQ/9GGU8mPGB++7bXgIXt+3bATJ+VeNuFpaZeoSNo5kla4QzgKRKP/x5Gtxr
CUysLQ4axC33bCcOEiG8I8u8WdXU4tbbYuHIwxPQyAvprpSxT4a/jGc3KNnqGmdn
lCfpFbXfFO6u1RzU96ufsz1Gtb0ESVFpkh4CQU1EFY11V6Eowx4DGbbon3Bup+ow
yKMe4PMR+hHQQUsKYgwDPNuRco7BZWPYJfNeMqhie/p8JTfduiuxfpfbu3FGAWx8
EMVLdTYEsam0i4eXkKiSo0QwmW2oaOmTMiqpDX//TDUcSY61mGWa1D/vWh3s77jD
WfUTNmI74iqfhpNNx2nqYWdPpfhBgHGI0Qb4+yvJLKnUd3luiVGnoJcnpsaWqLte
KaKeTax8ljPoChIjZNeWP4jAyvGktV6szv2j0aA731FyuI8lkHd+t5j1+NW0Z5Dy
t4wUSI9k/X8U7cqhHqaxsw0qtN5531ZAfk3nl0Gg2ZfeHI6LdDmkp1YzldCtAqK0
fSgnGrVzlEsrdosLVkMQDfxXTqSnCTmEcNF6i0V1n/fEGAt26pH9R9A1gxqfOtmo
XES7j9jj6Pamh4F+XvJEUqWCGxSim+3V2pYVcHqobGcbjGc517r41Y2Wba/FcvUU
RMer44cjhNGwngXOt53PBmCpZP3Kva53JEPluMyRCl55fkgcymo=
=CB3T
-END PGP SIGNATURE End Message ---
Processed: Re: Bug#1029213: libgraphicsmagick-q16-3 has a hardcoded dependency on libtiff5
Processing control commands: > merge -1 1029212 Bug #1029213 [libgraphicsmagick-q16-3] libgraphicsmagick-q16-3 has a hardcoded dependency on libtiff5 Bug #1029212 [libgraphicsmagick-q16-3] libgraphicsmagick-q16-3: hardcode depends on libtiff5. Merged 1029212 1029213 -- 1029212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029212 1029213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029213: libgraphicsmagick-q16-3 has a hardcoded dependency on libtiff5
Control: merge -1 1029212
On Thu, Jan 19, 2023 at 7:15 PM Adrian Bunk wrote:
> libgraphicsmagick-q16-3 has a hardcoded dependency on the cruft libtiff5:
> https://sources.debian.org/src/graphicsmagick/1.4%2Breally1.3.40-1/debian/control/#L44
>
> Please drop this, ${shlibs:Depends} already generates a correct dependency
> on libtiff6.
Indeed and already reported. Will fix this shortly.
Regards,
Laszlo/GCS
Processed: Bug#1026603 marked as pending in foolscap
Processing control commands: > tag -1 pending Bug #1026603 [src:foolscap] foolscap: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec' Added tag(s) pending. -- 1026603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026603: marked as pending in foolscap
Control: tag -1 pending Hello, Bug #1026603 in foolscap 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/python-team/packages/foolscap/-/commit/f6175eefdec6ef8583054b016a9f21f9a32112c5 Patch: Python 3.11 support. (Closes: #1026603) (this message was generated automatically) -- Greetings https://bugs.debian.org/1026603
Bug#1029215: debian-archive-keyring: bookworm SRM key
Source: debian-archive-keyring Version: 2021.1.1 Severity: serious X-Debbugs-Cc: debian-rele...@lists.debian.org Hi, We need an SRM key for bookworm, so that we can include it in the release. Regards, Adam
Bug#1029214: debian-archive-keyring: bookworm archive signing keys
Source: debian-archive-keyring Version: 2021.1.1 Severity: serious X-Debbugs-Cc: ftpmas...@debian.org, debian-rele...@lists.debian.org Hi, We need new archive signing keys for bookworm, so that we can include them in the release. Regards, Adam
Bug#1029021: marked as done (mutt-wizard: /usr/bin/mailsync is already shipped by the mailsync package)
Your message dated Thu, 19 Jan 2023 18:19:39 + with message-id and subject line Bug#1029021: fixed in mutt-wizard 3.3.1-2 has caused the Debian Bug report #1029021, regarding mutt-wizard: /usr/bin/mailsync is already shipped by the mailsync package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1029021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mutt-wizard Version: 3.3.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../mutt-wizard_3.3.1-1_all.deb ... Unpacking mutt-wizard (3.3.1-1) ... dpkg: error processing archive /var/cache/apt/archives/mutt-wizard_3.3.1-1_all.deb (--unpack): trying to overwrite '/usr/bin/mailsync', which is also in package mailsync 5.2.7-3.1+b1 Errors were encountered while processing: /var/cache/apt/archives/mutt-wizard_3.3.1-1_all.deb These files are in conflict: /usr/bin/mailsync /usr/share/man/man1/mailsync.1.gz cheers, Andreas mailsync=5.2.7-3.1+b1_mutt-wizard=3.3.1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: mutt-wizard Source-Version: 3.3.1-2 Done: Braulio Henrique Marques Souto We believe that the bug you reported is fixed in the latest version of mutt-wizard, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Braulio Henrique Marques Souto (supplier of updated mutt-wizard package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 19 Jan 2023 11:19:10 -0300 Source: mutt-wizard Architecture: source Version: 3.3.1-2 Distribution: unstable Urgency: medium Maintainer: Braulio Henrique Marques Souto Changed-By: Braulio Henrique Marques Souto Closes: 1029021 Changes: mutt-wizard (3.3.1-2) unstable; urgency=medium . * Upload to unstable. * debian/control: - Added Josenilson Ferreira da Silva in Uploaders. - Bumped Standards-Version to 4.6.2. * debian/copyright: updated packaging copyright years. * debian/patches/040_change-name-mailsync.patch: created to change the binary name from mailsync to mw-mailsync in upstream files. * debian/rules: added target 'execute_after_dh_install' to fix conflict. Thanks to Andreas Beckmann . (Closes: #1029021) * debian/tests/control: - Added new test command4. - Change name from mailsync to mw-mailsync in command3. Checksums-Sha1: b9354c40b4bc4ac809c1d42c16b887a5bd7c2f70 1994 mutt-wizard_3.3.1-2.dsc 356660d4d0569bb89ecd445eae71848da60bffcf 7156 mutt-wizard_3.3.1-2.debian.tar.xz fd8f5c288bc198ac26b67d9703486a8518beff7a 5686 mutt-wizard_3.3.1-2_source.buildinfo Checksums-Sha256: c48d960cb11b3b3b0384d403c9cd91590b095b5d6fab9ec93dba802b785bf5e2 1994 mutt-wizard_3.3.1-2.dsc 26fdb50c459d6b4f008156b696f44f5ca85e13c0c7fdd139b50de7f73fe51ea7 7156 mutt-wizard_3.3.1-2.debian.tar.xz 39383396d3ba333f4c28053c92a47228937aca628b29ecfdf29dd9e6e3504cf0 5686 mutt-wizard_3.3.1-2_source.buildinfo Files: ef7bb207784144891f60762c85236169 1994 mail optional mutt-wizard_3.3.1-2.dsc 1611eebe99540bbec8f85c4697c92e23 7156 mail optional mutt-wizard_3.3.1-2.debian.tar.xz 4ff418205ba812d5fb3eb98984f6c8dc 5686 mail optional mutt-wizard_3.3.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE+zneYYafSdXMyDrg1ToV2YOhC5QFAmPJhjcACgkQ1ToV2YOh C5QnKhAAuq8Br557lqYvH40+pX/ttVemMvnjiRNPA928/sWXFcTovZov44oOJ9K9 OCSmRTq6gLsSQIBBEfap9Clu3NrYssOeojdXXrv2R0Eb1wdtYgMCCrA1GpdSrJNc EWJeOwYpjwz0q/grQUkKXW38E6mTF8vJomCL1t7vTSeB4eQXNQfuA8b1Bd7ARxBB zB2PEJTXurmHo89tCKEWpCCrSibRWlxS2H5pBOSw/AYYnwXkiTpo51ohpNufxBIN 935df+eZIhi2N7A0ZTjKMrQ3G+3Bch7stVkR6vuqYiAiN8kcrHYn/JBM0h0kcgxK EfFflgStz4gGcNJSw2EDqqHMTdKwegm6G+aifh9EuOrP7GwCq0af+kL8b5/wpDB5 uPmoIbysTQd0Mlzd8G7WMBjlTrZttUirWTNxAYgOJ0AMobsRbyzwGukvlplysPR6 WcvADcRucvEHnXPenRsnwtDrp5OJGHjgyfKWmbpmj4pcUBbG+xh+Mpd80qSufmxG
Processed: reassign 1028813 to src:python-stem, forcibly merging 1028998 1028813, affects 1028998
Processing commands for cont...@bugs.debian.org:
> reassign 1028813 src:python-stem
Bug #1028813 {Done: YOKOTA Hiroshi } [python-stem] nyx:
FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec'
Bug reassigned from package 'python-stem' to 'src:python-stem'.
Ignoring request to alter found versions of bug #1028813 to the same values
previously set
Ignoring request to alter fixed versions of bug #1028813 to the same values
previously set
> forcemerge 1028998 1028813
Bug #1028998 [src:python-stem] python-stem: (autopkgtest) needs update for
Python 3.11
Bug #1028813 {Done: YOKOTA Hiroshi } [src:python-stem]
nyx: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec'
Severity set to 'serious' from 'normal'
Bug reopened
Ignoring request to alter fixed versions of bug #1028813 to the same values
previously set
Removed indication that 1028813 affects src:nyx, src:python-ironic-lib, and
src:pychromecast
Added indication that 1028813 affects src:python3-defaults
Marked as found in versions python-stem/1.8.1-1.1.
Bug #1028998 [src:python-stem] python-stem: (autopkgtest) needs update for
Python 3.11
Added tag(s) bookworm, ftbfs, and sid.
Merged 1028813 1028998
> affects 1028998 src:nyx
Bug #1028998 [src:python-stem] python-stem: (autopkgtest) needs update for
Python 3.11
Bug #1028813 [src:python-stem] nyx: FTBFS: AttributeError: module 'inspect' has
no attribute 'getargspec'
Added indication that 1028998 affects src:nyx
Added indication that 1028813 affects src:nyx
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1028813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028813
1028998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): unmerging 1028813, reassign 1028813 to python-stem, forcibly merging 1028998 1028813, affects 1028998 ...
Processing commands for cont...@bugs.debian.org:
> unmerge 1028813
Bug #1028813 {Done: YOKOTA Hiroshi } [python-zeroconf]
nyx: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec'
Bug #1028606 {Done: YOKOTA Hiroshi } [python-zeroconf]
python-zeroconf: Explicitly depend on python3-async-timeout.
Bug #1028688 {Done: YOKOTA Hiroshi } [python-zeroconf]
pychromecast: FTBFS: ModuleNotFoundError: No module named 'async_timeout'
Bug #1028775 {Done: YOKOTA Hiroshi } [python-zeroconf]
python-ironic-lib: FTBFS: ModuleNotFoundError: No module named 'async_timeout'
Disconnected #1028813 from all other report(s).
> reassign 1028813 python-stem
Bug #1028813 {Done: YOKOTA Hiroshi } [python-zeroconf]
nyx: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec'
Bug reassigned from package 'python-zeroconf' to 'python-stem'.
Ignoring request to alter found versions of bug #1028813 to the same values
previously set
No longer marked as fixed in versions python-zeroconf/0.47.1-2.
> forcemerge 1028998 1028813
Bug #1028998 [src:python-stem] python-stem: (autopkgtest) needs update for
Python 3.11
Unable to merge bugs because:
package of #1028813 is 'python-stem' not 'src:python-stem'
Failed to forcibly merge 1028998: Did not alter merged bugs.
> affects 1028998 src:nyx
Failed to mark 1028998 as affecting package(s): failed to get lock on
/srv/bugs.debian.org/spool/lock/1028998 -- Unable to lock
/srv/bugs.debian.org/spool/lock/1028998 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/1028998 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1028998 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1028998 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1028998 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1028998 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1028998 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1028998 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1028998 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1028998 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.
> affects 1028606 - src:nyx
Bug #1028606 {Done: YOKOTA Hiroshi } [python-zeroconf]
python-zeroconf: Explicitly depend on python3-async-timeout.
Bug #1028688 {Done: YOKOTA Hiroshi } [python-zeroconf]
pychromecast: FTBFS: ModuleNotFoundError: No module named 'async_timeout'
Bug #1028775 {Done: YOKOTA Hiroshi } [python-zeroconf]
python-ironic-lib: FTBFS: ModuleNotFoundError: No module named 'async_timeout'
Removed indication that 1028606 affects src:nyx
Removed indication that 1028688 affects src:nyx
Removed indication that 1028775 affects src:nyx
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1028606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028606
1028688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028688
1028775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028775
1028813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028813
1028998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1029213: libgraphicsmagick-q16-3 has a hardcoded dependency on libtiff5
Package: libgraphicsmagick-q16-3
Version: 1.4+really1.3.39-2
Severity: serious
libgraphicsmagick-q16-3 has a hardcoded dependency on the cruft libtiff5:
https://sources.debian.org/src/graphicsmagick/1.4%2Breally1.3.40-1/debian/control/#L44
Please drop this, ${shlibs:Depends} already generates a correct dependency
on libtiff6.
Processed: reassign 1028775 to python-zeroconf, forcibly merging 1028606 1028775, affects 1028606
Processing commands for cont...@bugs.debian.org:
> reassign 1028775 python-zeroconf
Bug #1028775 [src:python-ironic-lib] python-ironic-lib: FTBFS:
ModuleNotFoundError: No module named 'async_timeout'
Bug reassigned from package 'src:python-ironic-lib' to 'python-zeroconf'.
No longer marked as found in versions python-ironic-lib/5.3.0-2.
Ignoring request to alter fixed versions of bug #1028775 to the same values
previously set
> forcemerge 1028606 1028775
Bug #1028606 {Done: YOKOTA Hiroshi } [python-zeroconf]
python-zeroconf: Explicitly depend on python3-async-timeout.
Bug #1028688 {Done: YOKOTA Hiroshi } [python-zeroconf]
pychromecast: FTBFS: ModuleNotFoundError: No module named 'async_timeout'
Bug #1028813 {Done: YOKOTA Hiroshi } [python-zeroconf]
nyx: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec'
Bug #1028813 {Done: YOKOTA Hiroshi } [python-zeroconf]
nyx: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec'
Removed indication that 1028813 affects src:pychromecast and src:nyx
Added indication that 1028813 affects src:nyx,src:pychromecast
Removed indication that 1028606 affects src:nyx and src:pychromecast
Added indication that 1028606 affects src:nyx,src:pychromecast
Removed indication that 1028688 affects src:pychromecast and src:nyx
Added indication that 1028688 affects src:nyx,src:pychromecast
Bug #1028775 [python-zeroconf] python-ironic-lib: FTBFS: ModuleNotFoundError:
No module named 'async_timeout'
Severity set to 'normal' from 'serious'
Marked Bug as done
Added indication that 1028775 affects src:nyx,src:pychromecast
Marked as fixed in versions python-zeroconf/0.47.1-2.
Added tag(s) patch.
Bug #1028688 {Done: YOKOTA Hiroshi } [python-zeroconf]
pychromecast: FTBFS: ModuleNotFoundError: No module named 'async_timeout'
Merged 1028606 1028688 1028775 1028813
> affects 1028606 src:python-ironic-lib
Bug #1028606 {Done: YOKOTA Hiroshi } [python-zeroconf]
python-zeroconf: Explicitly depend on python3-async-timeout.
Bug #1028688 {Done: YOKOTA Hiroshi } [python-zeroconf]
pychromecast: FTBFS: ModuleNotFoundError: No module named 'async_timeout'
Bug #1028775 {Done: YOKOTA Hiroshi } [python-zeroconf]
python-ironic-lib: FTBFS: ModuleNotFoundError: No module named 'async_timeout'
Bug #1028813 {Done: YOKOTA Hiroshi } [python-zeroconf]
nyx: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec'
Added indication that 1028606 affects src:python-ironic-lib
Added indication that 1028688 affects src:python-ironic-lib
Added indication that 1028775 affects src:python-ironic-lib
Added indication that 1028813 affects src:python-ironic-lib
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1028606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028606
1028688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028688
1028775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028775
1028813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: willow: FTBFS: AttributeError: module 'PIL._imaging' has no attribute 'libtiff_decoder'
Processing commands for cont...@bugs.debian.org: > notfound 1028719 willow/1.4-3 Bug #1028719 [src:willow] willow: FTBFS: AttributeError: module 'PIL._imaging' has no attribute 'libtiff_decoder' No longer marked as found in versions willow/1.4-3. > severity 1028719 normal Bug #1028719 [src:willow] willow: FTBFS: AttributeError: module 'PIL._imaging' has no attribute 'libtiff_decoder' Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1028719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029212: libgraphicsmagick-q16-3: hardcode depends on libtiff5.
Package: libgraphicsmagick-q16-3 Version: 1.4+really1.3.39-2 Severity: serious libgraphicsmagick-q16-3 has a hardcoded dependency on libtiff5, so even after binnmuing for the tiff transition it still depends on it This affects both the version in bookworm and the version in sid, I have not checked other versions.
Processed: tagging 1026615
Processing commands for cont...@bugs.debian.org: > tags 1026615 + patch Bug #1026615 [src:magic-wormhole-mailbox-server] magic-wormhole-mailbox-server: FTBFS: ValueError: invalid mode: 'rU' Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: openpyxl: FTBFS: ValueError: I/O operation on closed file.
Processing commands for cont...@bugs.debian.org: > notfound 1028843 openpyxl/3.0.9-1 Bug #1028843 [src:openpyxl] openpyxl: FTBFS: ValueError: I/O operation on closed file. No longer marked as found in versions openpyxl/3.0.9-1. > severity 1028843 normal Bug #1028843 [src:openpyxl] openpyxl: FTBFS: ValueError: I/O operation on closed file. Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1028843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: img2pdf: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
Processing commands for cont...@bugs.debian.org:
> notfound 1028887 img2pdf/0.4.4-3
Bug #1028887 [src:img2pdf] img2pdf: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
No longer marked as found in versions img2pdf/0.4.4-3.
> severity 1028887 normal
Bug #1028887 [src:img2pdf] img2pdf: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1028887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: RC Bug #1028795: forwarded upstream
Processing commands for cont...@bugs.debian.org: > forwarded 1028795 > https://github.com/kernelslacker/trinity/commit/99a1822383a676e0bacfe1cd8ff0e2e2dfb8ba76 Bug #1028795 [src:trinity] trinity: FTBFS: net/proto-decnet.c:5:10: fatal error: linux/dn.h: No such file or directory Set Bug forwarded-to-address to 'https://github.com/kernelslacker/trinity/commit/99a1822383a676e0bacfe1cd8ff0e2e2dfb8ba76'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1028795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: glymur: FTBFS: tests fail
Processing commands for cont...@bugs.debian.org: > notfound 1028889 glymur/0.12.2-2 Bug #1028889 [src:glymur] glymur: FTBFS: tests fail No longer marked as found in versions glymur/0.12.2-2. > severity 1028889 normal Bug #1028889 [src:glymur] glymur: FTBFS: tests fail Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1028889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: RC bug #1028835: forwarded upstream
Processing commands for cont...@bugs.debian.org: > forwarded 1028835 https://github.com/horazont/aioxmpp/issues/385 Bug #1028835 [src:python-aioxmpp] python-aioxmpp: FTBFS: AttributeError: property of 'Mock' object has no setter Set Bug forwarded-to-address to 'https://github.com/horazont/aioxmpp/issues/385'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1028835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: celery FTBFS with Python 3.11 as default version
Processing control commands: > tags -1 patch Bug #1028148 [src:celery] celery FTBFS with Python 3.11 as default version Added tag(s) patch. -- 1028148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028148: marked as pending in celery
Control: tag -1 pending Hello, Bug #1028148 in celery 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/python-team/packages/celery/-/commit/c94d7c031d3686596305d435898199e3d452e87c Add upstream patch to fix FTBFS with python3.11. (closes: #1028148) (this message was generated automatically) -- Greetings https://bugs.debian.org/1028148
Bug#1028148: celery FTBFS with Python 3.11 as default version
Control: tags -1 patch A patch has been committed in git: https://salsa.debian.org/python-team/packages/celery/-/commit/c94d7c031d3686596305d435898199e3d452e87c Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Bug#1028148 marked as pending in celery
Processing control commands: > tag -1 pending Bug #1028148 [src:celery] celery FTBFS with Python 3.11 as default version Added tag(s) pending. -- 1028148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028333: [Pkg-puppet-devel] Bug#1028333: puppetserver: find an upgrade path from puppet-master
On 2023-01-19 11:30:31, Jérôme Charaoui wrote: > So considering all this I'm currently leaning towards adding a > transitional "puppet-master" and/or "puppet-master-passenger" package > for the purpose of shipping a NEWS file recommending that users migrate > to the puppetserver package manually. Agreed. We should also probably make an entry in the release notes. According to the RT, this should be done in a MR here: https://salsa.debian.org/ddp-team/release-notes/ -- Never underestimate the bandwidth of a station wagon full of tapes hurtling down the highway. - Andrew S. Tanenbaum, "Computer Networks"
Bug#1028333: puppetserver: find an upgrade path from puppet-master
The old "puppet-master" and "puppet-master-passenger" were basically just configuration files for the systemd/sysvinit and Apache2/Passenger, because the main (ruby) code was always in the "puppet" package. I think the way forward here is that first, we should make the 7.x transitional dummy package "puppet" "Breaks: puppet-master, puppet-master-passenger", to make clear that the old master packages cannot function with the libraries shipping in the latest puppet-agent package. And secondly, we should carefully consider whether a "seamless" transition is even possible at all. Puppetserver is completely different software which is configured differently than the old master, and as such I doubt that one can simple replace one package with the other and expect things to "just work". Even if it does, important bits of the configuration may likely be lost in translation (eg. auth.conf). So considering all this I'm currently leaning towards adding a transitional "puppet-master" and/or "puppet-master-passenger" package for the purpose of shipping a NEWS file recommending that users migrate to the puppetserver package manually. -- Jérôme
Processed (with 5 errors): Re: navarp: FTBFS: AttributeError: module 'numpy' has no attribute 'complex'
Processing commands for cont...@bugs.debian.org: > notfound 1028665 navarp/1.3.0-1 Bug #1028665 [src:navarp] navarp: FTBFS: AttributeError: module 'numpy' has no attribute 'complex' No longer marked as found in versions navarp/1.3.0-1. > severity 1028665 normal Bug #1028665 [src:navarp] navarp: FTBFS: AttributeError: module 'numpy' has no attribute 'complex' Severity set to 'normal' from 'serious' > affects 1028825 src:navarp Bug #1028825 [src:python-igor] python-igor: FTBFS: AttributeError: module 'numpy' has no attribute 'complex' Added indication that 1028825 affects src:navarp > On Sat, 14 Jan 2023 13:41:38 +0100 Lucas Nussbaum wrote:> Traceback Unknown command or malformed arguments to command. > (most recent call last): Unknown command or malformed arguments to command. > > File "/<>/examples/plot_gr_hv_scan.py", line 27, in Unknown command or malformed arguments to command. > > from navarp.extras.simulation import get_tbgraphene_hv Unknown command or malformed arguments to command. > > File "/<>/navarp/extras/simulation.py", line 34, in Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 1028665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028665 1028825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029188: marked as pending in node-readable-stream
Control: tag -1 pending Hello, Bug #1029188 in node-readable-stream 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/js-team/node-readable-stream/-/commit/cd076a116fb59a8c5f8aedcae92364b20654 Fix typescript configuration Closes: #1029188 (this message was generated automatically) -- Greetings https://bugs.debian.org/1029188
Processed: Bug#1029188 marked as pending in node-readable-stream
Processing control commands: > tag -1 pending Bug #1029188 [src:node-readable-stream] node-readable-stream: FTBFS: Cannot find module 'fs' Added tag(s) pending. -- 1029188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028671: python-django-tagging: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.11" --system=custom "--test-args=PYTHONPATH=. DJANGO_SETTINGS_MODULE=tagging.tests.settings
Control: tags -1 patch A patch has been committed in git: https://salsa.debian.org/python-team/packages/python-django-tagging/-/commit/580dfcf54791ea0613c0edc622867b44e5738fb5 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Re: python-django-tagging: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.11" --system=custom "--test-args=PYTHONPATH=. DJANGO_SETTINGS_MODULE=tagging.tests.settin
Processing control commands:
> tags -1 patch
Bug #1028671 [src:python-django-tagging] python-django-tagging: FTBFS:
dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.11"
--system=custom "--test-args=PYTHONPATH=.
DJANGO_SETTINGS_MODULE=tagging.tests.settings django-admin test --verbosity=2"
returned exit code 13
Added tag(s) patch.
--
1028671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1029154: closing 1029154
close 1029154 2.30.0-4 thanks
Bug#1026476: marked as pending in python-django
Control: tag -1 pending Hello, Bug #1026476 in python-django 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/python-team/packages/python-django/-/commit/8a412be6bee1a89e400fc63ecc7cf685b2e89bd9 Make unit tests compatible with Python 3.11 to fix build errors Closes: #1026476 LP: #2002012 (this message was generated automatically) -- Greetings https://bugs.debian.org/1026476
Processed: Bug#1026476 marked as pending in python-django
Processing control commands: > tag -1 pending Bug #1026476 [src:python-django] python-django: FTBFS: AssertionError Added tag(s) pending. -- 1026476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1029154
Processing commands for cont...@bugs.debian.org: > close 1029154 2.30.0-4 Bug #1029154 [src:swift] swift: CVE-2022-47950 Bug #1029200 [src:swift] CVE-2022-47950: Arbitrary file access through custom S3 XML entities Marked as fixed in versions swift/2.30.0-4. Marked as fixed in versions swift/2.30.0-4. Bug #1029154 [src:swift] swift: CVE-2022-47950 Bug #1029200 [src:swift] CVE-2022-47950: Arbitrary file access through custom S3 XML entities Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1029154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029154 1029200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1029200 to src:swift, forcibly merging 1029154 1029200, found 1029154 in 2.26.0-10
Processing commands for cont...@bugs.debian.org:
> reassign 1029200 src:swift
Bug #1029200 {Done: Thomas Goirand } [src:swift-proxy]
CVE-2022-47950: Arbitrary file access through custom S3 XML entities
Warning: Unknown package 'src:swift-proxy'
Bug reassigned from package 'src:swift-proxy' to 'src:swift'.
No longer marked as found in versions swift-proxy/2.26.0-10.
No longer marked as fixed in versions swift/2.30.0-4.
> forcemerge 1029154 1029200
Bug #1029154 [src:swift] swift: CVE-2022-47950
Bug #1029154 [src:swift] swift: CVE-2022-47950
Added tag(s) patch.
Bug #1029200 {Done: Thomas Goirand } [src:swift]
CVE-2022-47950: Arbitrary file access through custom S3 XML entities
Severity set to 'grave' from 'serious'
Bug reopened
Ignoring request to alter fixed versions of bug #1029200 to the same values
previously set
Marked as found in versions swift/2.30.0-3.
Added tag(s) upstream and security.
Merged 1029154 1029200
> found 1029154 2.26.0-10
Bug #1029154 [src:swift] swift: CVE-2022-47950
Bug #1029200 [src:swift] CVE-2022-47950: Arbitrary file access through custom
S3 XML entities
Marked as found in versions swift/2.26.0-10.
Marked as found in versions swift/2.26.0-10.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1029154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029154
1029200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: termbox: FTBFS: ValueError: invalid mode: 'rUb'
Processing control commands: > tags -1 patch Bug #1028687 [src:termbox] termbox: FTBFS: ValueError: invalid mode: 'rUb' Added tag(s) patch. -- 1028687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1027077 is forwarded to https://github.com/markets/invisible_captcha/pull/113
Processing commands for cont...@bugs.debian.org: > forwarded 1027077 https://github.com/markets/invisible_captcha/pull/113 Bug #1027077 [src:ruby-invisible-captcha] ruby-invisible-captcha: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: Set Bug forwarded-to-address to 'https://github.com/markets/invisible_captcha/pull/113'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028687: termbox: FTBFS: ValueError: invalid mode: 'rUb'
Control: tags -1 patch A patch has been committed in git: https://salsa.debian.org/debian/termbox/-/commit/814a247912b907d66adb8b761c616e1f1a5f471f Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Re: python-hdf5storage: FTBFS: build-dependency not installable: python-numpy-doc
Processing control commands: > tags -1 pending Bug #1028695 [src:python-hdf5storage] python-hdf5storage: FTBFS: build-dependency not installable: python-numpy-doc Added tag(s) pending. -- 1028695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028695: python-hdf5storage: FTBFS: build-dependency not installable: python-numpy-doc
Control: tags -1 pending A fix has been committed in git: https://salsa.debian.org/science-team/python-hdf5storage/-/commit/78d2bc277af59a8d2881b2290d175822b39ca65b Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028673: pydl: FTBFS: ImportError: cannot import name 'float' from 'numpy' (/usr/lib/python3/dist-packages/numpy/__init__.py)
Control: tags -1 patch A patch has been committed in git: https://salsa.debian.org/debian-astro-team/pydl/-/commit/3cd70897436e4166f495aee204bcf0c7b026a5bc Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Re: pydl: FTBFS: ImportError: cannot import name 'float' from 'numpy' (/usr/lib/python3/dist-packages/numpy/__init__.py)
Processing control commands: > tags -1 patch Bug #1028673 [src:pydl] pydl: FTBFS: ImportError: cannot import name 'float' from 'numpy' (/usr/lib/python3/dist-packages/numpy/__init__.py) Added tag(s) patch. -- 1028673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029174: please check dhcpcd 9.4.1-14 in unstable
Greetings, Something tells me that both of you have encountered the same bug. We've just pushed dhcpcd 9.4.1-14 into unstable. Can you please check whether that fixes it? Martin-Éric
Bug#1029200: marked as done (CVE-2022-47950: Arbitrary file access through custom S3 XML entities)
Your message dated Thu, 19 Jan 2023 15:21:16 + with message-id and subject line Bug#1029200: fixed in swift 2.30.0-4 has caused the Debian Bug report #1029200, regarding CVE-2022-47950: Arbitrary file access through custom S3 XML entities to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1029200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: swift-proxy Version: 2.26.0-10 Severity: serious Tags: patch Title: Arbitrary file access through custom S3 XML entities Reporter: Sébastien Meriot (OVH) Products: Swift Affects: <2.28.1, >=2.29.0 <2.29.2, ==2.30.0 Description: Sébastien Meriot (OVH) reported a vulnerability in Swift's S3 XML parser. By supplying specially crafted XML files an authenticated user may coerce the S3 API into returning arbitrary file contents from the host server resulting in unauthorized read access to potentially sensitive data; this impacts both s3api deployments (Rocky or later), and swift3 deployments (Queens and earlier, no longer actively developed). Only deployments with S3 compatibility enabled are affected. See attached patches. Unless a flaw is discovered in them, these patches will be merged to their corresponding branches on the public disclosure date. The master branch patch applies cleanly to stable/zed, stable/yoga, stable/xena and stable/wallaby branches, but separate copies of it are attached for each for the sake of clarity. The fix could be applied with some fuzz to branches as old as stable/train, and with some minor unit test adjustments as far back as stable/rocky. Note that the stable/wallaby branch is under extended maintenance (as are older branches) and will receive no new point releases, but a patch for it is provided as a courtesy. CVE: CVE-2022-47950 Proposed public disclosure date/time: 2023-01-17, 1500UTC Please do not make the issue public (or release public patches) before this coordinated embargo date. Original private report: https://launchpad.net/bugs/1998625 For access to read and comment on this report, please reply to me with your Launchpad username and I will subscribe you. --- End Message --- --- Begin Message --- Source: swift Source-Version: 2.30.0-4 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of swift, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated swift package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 19 Jan 2023 15:43:31 +0100 Source: swift Architecture: source Version: 2.30.0-4 Distribution: unstable Urgency: high Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 1029200 Changes: swift (2.30.0-4) unstable; urgency=high . * CVE-2022-47950: Arbitrary file access through custom S3 XML entities. Added upstream patch: CVE-2022-47950-stable-zed.patch (Closes: #1029200). * debian/watch: use git mode. Checksums-Sha1: 6bb01119dcbd36acba85111eec55885f53d47701 3354 swift_2.30.0-4.dsc c2603fcb0d71e9a83ced923b81629fb6415a5ddc 28240 swift_2.30.0-4.debian.tar.xz 60e2d08d694d77b4dec6cc645ccc8228e9f73431 15029 swift_2.30.0-4_amd64.buildinfo Checksums-Sha256: c5f8c8e1fb852754d91224cf897b82369f8926aaf28fb3100f7f09ffa8a38b00 3354 swift_2.30.0-4.dsc 4b180bda5efbfe66031d6af10df20a0e28c0cd06c6cb7024239fb91ef3540fa8 28240 swift_2.30.0-4.debian.tar.xz e45b6c63abb03a4eccb30d6c439c384c36d464ec6a80370c9fb84083dcfe 15029 swift_2.30.0-4_amd64.buildinfo Files: 5e01c57238ff6e3b1e2b1a3fcd5662a8 3354 net optional swift_2.30.0-4.dsc 32709a76c8530ad5f327ef647efd80f8 28240 net optional swift_2.30.0-4.debian.tar.xz 76eb605971b486cec7c62ae5d73d7bbe 15029 net optional swift_2.30.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmPJWo8ACgkQ1BatFaxr Q/5jGQ//VwOCT0yqC6ipLIZZSe+/O9ms6BGR90QTdb/xGmD4nrLbKOOkIQuyB1Dc jN6EnmzdSJQAL1prPDdZvJDQBAsXKpHz/tZRnpxnL+vIjskrK4VhF4M8J5aXHO3q njur78XNgArHpgUBeSEbZywA7bbXnArvKfM9PMxEkgRDsfLSRx9yTKprpeReaYWn
Bug#1028920: marked as done (libpysal: FTBFS with new numpy)
Your message dated Thu, 19 Jan 2023 15:20:19 + with message-id and subject line Bug#1028920: fixed in libpysal 4.7.0-1 has caused the Debian Bug report #1028920, regarding libpysal: FTBFS with new numpy to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1028920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libpysal Version: 4.6.2-2 Severity: serious libpysal FTBFS currently: == short test summary info == FAILED libpysal/weights/tests/test_gabriel.py::test_delaunay - numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend) FAILED libpysal/weights/tests/test_gabriel.py::test_gabriel - numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend) FAILED libpysal/weights/tests/test_gabriel.py::test_rng - numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend) FAILED libpysal/weights/tests/test_raster.py::Testraster::test_da2W - numba.core.errors.LoweringError: Failed in nopython mode pipeline (step: native lowering) FAILED libpysal/weights/tests/test_raster.py::Testraster::test_da2WSP - numba.core.errors.LoweringError: Failed in nopython mode pipeline (step: native lowering) FAILED libpysal/weights/tests/test_raster.py::Testraster::test_wsp2da - numba.core.errors.LoweringError: Failed in nopython mode pipeline (step: native lowering) FAILED libpysal/weights/tests/test_spatial_lag.py::Test_spatial_lag::test_lag_categorical - AttributeError: module 'numpy' has no attribute 'int' 7 failed, 416 passed, 41 skipped, 66 warnings in 18.00s = --- End Message --- --- Begin Message --- Source: libpysal Source-Version: 4.7.0-1 Done: Josenilson Ferreira da Silva We believe that the bug you reported is fixed in the latest version of libpysal, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josenilson Ferreira da Silva (supplier of updated libpysal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 19 Jan 2023 07:02:44 -0300 Source: libpysal Architecture: source Version: 4.7.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Josenilson Ferreira da Silva Closes: 1028920 Changes: libpysal (4.7.0-1) unstable; urgency=medium . * New upstream version 4.7.0 (Closes: #1028920) * debian/control: standards-Version to 4.6.2 * debian/copyright: updated year copyright * debian/rules: skipped tests with unknown errors * debian/source: removed unnecessary file Checksums-Sha1: 0bd504ce3caa9bbe8c912193f7e770cd244364b3 2471 libpysal_4.7.0-1.dsc 84f9d04a28049d8b6c841e98b642d1933b867639 6589916 libpysal_4.7.0.orig.tar.gz bb0463b2d7cfc8f40c5fb7c29d9cc6376d41ba5d 4308 libpysal_4.7.0-1.debian.tar.xz b34cb1d2fa6d5fe6e18e56e890d2a4f9484bf20e 7532 libpysal_4.7.0-1_source.buildinfo Checksums-Sha256: 6485b73432d70b378a8ddc675ebf816b345366b00cff0da7dcca3cd2dc8cbc32 2471 libpysal_4.7.0-1.dsc 568aa640436d1d9f8b3589ef3a63c9086396b592581f3c92fc8806551bb6cc44 6589916 libpysal_4.7.0.orig.tar.gz 0a8b1906f7557252cb278ba6343cf13a804c0f6353a27e0f41037206fec75d30 4308 libpysal_4.7.0-1.debian.tar.xz 34eb38d522d48c17fd7cae3b823c325d2cca28127fc3424671d02ea2e5d5afe9 7532 libpysal_4.7.0-1_source.buildinfo Files: 53fc9b8df19579c051f71e911cb59d05 2471 python optional libpysal_4.7.0-1.dsc 96ec403e75746a6e671ae005860bb96e 6589916 python optional libpysal_4.7.0.orig.tar.gz 4f89f790ab4e6233ebf67325aac79c25 4308 python optional libpysal_4.7.0-1.debian.tar.xz 786e9e06459e83d586143f982c05a5bc 7532 python optional libpysal_4.7.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmPJXbAQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFGZLC/wK4NyLN/MX/y0idr3VAGKHdh4yXwuDugDk hwGfNZs3Df97umoXR//aG/7DpxwopPTzOW9NHuUVOabsO/uoLkVmd6cMgh6aqpqP
Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Hi, On Wed, Jan 18, 2023 at 09:48:33PM +, Martin wrote: > Control: severity -1 grave > > Justification for grave: Crashes Gajim for some users. RC, IMHO. > > On 2023-01-17 21:56, Sebastian Reichel wrote: > > I just got the new package through testing and now gajim segfaults > > ony my system with stacktrace pointing to libproxy. So this is not > > magically solved. > > :-( > > Could you check, if a downgrade to libproxy 0.4.15-15 helps? > That certainly helps to find the bug! I tried downgrading libproxy1v5 and libproxy-tools to 0.4.15-15 and glib-networking to 2.66.0. This did not change anything. With libproxy from testing gajim does work when being downgraded to 1.5.4-1 (which requires also downgrading python3-nbxmpp to 3.2.5-1 to be functional). -- Sebastian signature.asc Description: PGP signature
Processed: Bug#1029200 marked as pending in swift
Processing control commands: > tag -1 pending Bug #1029200 [src:swift-proxy] CVE-2022-47950: Arbitrary file access through custom S3 XML entities Warning: Unknown package 'src:swift-proxy' Ignoring request to alter tags of bug #1029200 to the same tags previously set Warning: Unknown package 'src:swift-proxy' -- 1029200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1028592: Info received (Bug#1028592: Acknowledgement (tagcoll2 2.0.14-2 fails to build on sid))
Processing control commands: > reassign -1 src:tagcoll2,src:libwibble Bug #1028592 [tagcoll2] tagcoll2 2.0.14-2 fails to build on sid Bug reassigned from package 'tagcoll2' to 'src:tagcoll2,src:libwibble'. No longer marked as found in versions 2.0.14-2. Ignoring request to alter fixed versions of bug #1028592 to the same values previously set -- 1028592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029200: marked as pending in swift
Control: tag -1 pending Hello, Bug #1029200 in swift 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/openstack-team/services/swift/-/commit/016056b09df9cf152a084f165d2f70b147a8bb14 * CVE-2022-47950: Arbitrary file access through custom S3 XML entities. Added upstream patch: CVE-2022-47950-stable-zed.patch (Closes: #1029200). * debian/watch: use git mode. (this message was generated automatically) -- Greetings https://bugs.debian.org/1029200
Bug#1028592: Info received (Bug#1028592: Acknowledgement (tagcoll2 2.0.14-2 fails to build on sid))
control: reassign -1 src:tagcoll2,src:libwibble thanks -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ The wrong Amazon is burning.
Bug#1024012: [joshuaulrich/xts] Unit test failure when running on i386 (Issue #384)
Am Thu, Jan 19, 2023 at 06:49:24AM -0800 schrieb Adrian Bunk: > @tillea Confirmed by my testing is that the difference between failing and > passing autopkgtest of `r-cran-xts` is whether `r-base-core` is from Debian > unstable or from the same sources recompiled with `-ffloat-store`. > > `-ffloat-store` would cost some performance for FPU code in R on i386, but > given that it's 2023 this should not matter much since i386 is mainline > vintage hardware (multiarch usecases shouldn't apply here). I fully agree that users could live with performance issues on i386 since those who need performance will not use i386. > I would guess this change might also help with similar issues in other > packages, but that is just a guess. I'd agree with reassigning this to r-base.
Bug#1027656: marked as done (janus: FTBFS: turnrest.c:168:9: error: void value not ignored as it ought to be)
Your message dated Thu, 19 Jan 2023 14:50:12 + with message-id and subject line Bug#1027656: fixed in janus 1.1.2-1 has caused the Debian Bug report #1027656, regarding janus: FTBFS: turnrest.c:168:9: error: void value not ignored as it ought to be to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: janus Version: 1.1.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -DPACKAGE_NAME=\"Janus\ WebRTC\ Server\" > -DPACKAGE_TARNAME=\"janus-gateway\" -DPACKAGE_VERSION=\"1.1.1\" > -DPACKAGE_STRING=\"Janus\ WebRTC\ Server\ 1.1.1\" > -DPACKAGE_BUGREPORT=\"https://github.com/meetecho/janus-gateway\; > -DPACKAGE_URL=\"https://janus.conf.meetecho.com\; -DPACKAGE=\"janus-gateway\" > -DVERSION=\"1.1.1\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 > -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DHAVE_WCHAR_H=1 -DSTDC_HEADERS=1 > -D_ALL_SOURCE=1 -D_DARWIN_C_SOURCE=1 -D_GNU_SOURCE=1 > -D_HPUX_ALT_XOPEN_SOCKET_API=1 -D_NETBSD_SOURCE=1 -D_OPENBSD_SOURCE=1 > -D_POSIX_PTHREAD_SEMANTICS=1 -D__STDC_WANT_IEC_60559_ATTRIBS_EXT__=1 > -D__STDC_WANT_IEC_60559_BFP_EXT__=1 -D__STDC_WANT_IEC_60559_DFP_EXT__=1 > -D__STDC_WANT_IEC_60559_FUNCS_EXT__=1 -D__STDC_WANT_IEC_60559_TYPES_EXT__=1 > -D__STDC_WANT_LIB_EXT2__=1 -D__STDC_WANT_MATH_SPEC_FUNCS__=1 > -D_TANDEM_SOURCE=1 -D__EXTENSIONS__=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" > -DHAS_DTLS_WINDOW_SIZE=1 -DHAVE_SRTP_AESGCM=1 -DHAVE_PORTRANGE=1 > -DHAVE_LIBNICE_TCP=1 -DHAVE_CLOSE_ASYNC=1 -DHAVE_ICE_NOMINATION=1 > -DHAVE_SRTP_2=1 -DHAVE_SCTP=1 -DHAVE_LIBCURL=1 -DHAVE_TURNRESTAPI=1 > -DHAVE_SAMPLEEVH=1 -DHAVE_ENUM_MHD_RESULT=1 -DHAVE_WEBSOCKETS=1 > -DHAVE_LIBWEBSOCKETS_PEER_SIMPLE=1 -DHAVE_WSEVH=1 -DHAVE_RABBITMQ=1 > -DHAVE_RABBITMQEVH=1 -DHAVE_MQTT=1 -DHAVE_MQTTEVH=1 -DHAVE_NANOMSG=1 > -DHAVE_NANOMSGEVH=1 -DHAVE_PFUNIX=1 -DHAVE_LIBSYSTEMD=1 -DHAVE_LIBOGG=1 > -DHAVE_LIBPCAP=1 -I. -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/nice > -I/usr/include/p11-kit-1 -I/usr/include/gupnp-igd-1.0 > -I/usr/include/gupnp-1.6 -I/usr/include/gssdp-1.6 -I/usr/include/libsoup-3.0 > -I/usr/include/sysprof-4 -I/usr/include/libxml2 -pthread > -I/usr/include/x86_64-linux-gnu > -DPLUGINDIR=\"/usr/lib/x86_64-linux-gnu/janus/plugins\" > -DTRANSPORTDIR=\"/usr/lib/x86_64-linux-gnu/janus/transports\" > -DEVENTDIR=\"/usr/lib/x86_64-linux-gnu/janus/events\" > -DLOGGERDIR=\"/usr/lib/x86_64-linux-gnu/janus/loggers\" > -DCONFDIR=\"/etc/janus\" -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security-fPIC > -fstack-protector-all -fstrict-aliasing -ggdb3 -pthread-Wall > -Warray-bounds -Wextra -Wformat-nonliteral -Wformat-security > -Wformat=2 -Winit-self -Wlarger-than=65537 > -Wmissing-declarations -Wmissing-format-attribute > -Wmissing-include-dirs -Wmissing-noreturn -Wmissing-prototypes > -Wnested-externs-Wold-style-definition -Wpacked > -Wpointer-arith -Wsign-compare -Wstrict-prototypes > -Wswitch-default-Wunused-Wno-unused-parameter > -Wno-unused-result -Wwrite-strings > -Werror=implicit-function-declaration -Wcast-align > -Wno-override-init -Wunsafe-loop-optimizations > -Wunused-but-set-variable -c -o janus-utils.o `test -f 'utils.c' || echo > './'`utils.c > In file included from /usr/include/x86_64-linux-gnu/curl/curl.h:3195, > from turnrest.c:21: > turnrest.c: In function ‘janus_turnrest_request’: > turnrest.c:168:9: error: void value not ignored as it ought to be > 168 | curl_easy_setopt(curl, api_http_get ? CURLOPT_HTTPGET : > CURLOPT_POST, 1); > | ^ > make[4]: *** [Makefile:2506: janus-turnrest.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/01/01/janus_1.1.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or:
Bug#1029200: marked as pending in swift
Control: tag -1 pending Hello, Bug #1029200 in swift 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/openstack-team/services/swift/-/commit/80179904c61c32001f775afc92f9d97bea26224e * Add CVE-2022-47950-stable-xena.patch (Closes: #1029200). * Use git mode in debian/watch. (this message was generated automatically) -- Greetings https://bugs.debian.org/1029200
Processed: Bug#1029200 marked as pending in swift
Processing control commands: > tag -1 pending Bug #1029200 [src:swift-proxy] CVE-2022-47950: Arbitrary file access through custom S3 XML entities Warning: Unknown package 'src:swift-proxy' Ignoring request to alter tags of bug #1029200 to the same tags previously set Warning: Unknown package 'src:swift-proxy' -- 1029200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029200: marked as pending in swift
Control: tag -1 pending Hello, Bug #1029200 in swift 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/openstack-team/services/swift/-/commit/4fb07f640b293d20a378877d04572c1c2da57637 Add CVE-2022-47950-stable-xena.patch (Closes: #1029200). (this message was generated automatically) -- Greetings https://bugs.debian.org/1029200
Bug#1024012: Unit test failure when running on i386 (Issue #384)
@tillea I've got it passing by compiling R itself with `-ffloat-store` to mitigate the excess precision of the x87 FPU. I'll reassign the Debian bug with a patch in a while. -- Reply to this email directly or view it on GitHub: https://github.com/joshuaulrich/xts/issues/384#issuecomment-1397058448 You are receiving this because you were mentioned. Message ID:
Processed: Bug#1029200 marked as pending in swift
Processing control commands: > tag -1 pending Bug #1029200 [src:swift-proxy] CVE-2022-47950: Arbitrary file access through custom S3 XML entities Warning: Unknown package 'src:swift-proxy' Ignoring request to alter tags of bug #1029200 to the same tags previously set Warning: Unknown package 'src:swift-proxy' -- 1029200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1029200 marked as pending in swift
Processing control commands: > tag -1 pending Bug #1029200 [src:swift-proxy] CVE-2022-47950: Arbitrary file access through custom S3 XML entities Warning: Unknown package 'src:swift-proxy' Added tag(s) pending. Warning: Unknown package 'src:swift-proxy' -- 1029200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029200: marked as pending in swift
Control: tag -1 pending Hello, Bug #1029200 in swift 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/openstack-team/services/swift/-/commit/2a0edbf2675a358139ebfaffb8104080b3045ef7 Add CVE-2022-47950-stable-wallaby.patch (Closes: #1029200). (this message was generated automatically) -- Greetings https://bugs.debian.org/1029200
Bug#1029201: openbox-menu: do not release with bookworm
Package: openbox-menu Version:0.8.0+hg20161009-3.1 Severity: serious openbox-menu should not be shipped in bookworm. -- .''`. Mateusz Łukasik : :' : l0calh0st.pl `. `' Debian Member -mat...@linuxmint.pl `-GPG: D93B 0C12 C8D0 4D7A AFBC FA27 CCD9 1D61 11A0 6851
Bug#1029200: CVE-2022-47950: Arbitrary file access through custom S3 XML entities
Source: swift-proxy Version: 2.26.0-10 Severity: serious Tags: patch Title: Arbitrary file access through custom S3 XML entities Reporter: Sébastien Meriot (OVH) Products: Swift Affects: <2.28.1, >=2.29.0 <2.29.2, ==2.30.0 Description: Sébastien Meriot (OVH) reported a vulnerability in Swift's S3 XML parser. By supplying specially crafted XML files an authenticated user may coerce the S3 API into returning arbitrary file contents from the host server resulting in unauthorized read access to potentially sensitive data; this impacts both s3api deployments (Rocky or later), and swift3 deployments (Queens and earlier, no longer actively developed). Only deployments with S3 compatibility enabled are affected. See attached patches. Unless a flaw is discovered in them, these patches will be merged to their corresponding branches on the public disclosure date. The master branch patch applies cleanly to stable/zed, stable/yoga, stable/xena and stable/wallaby branches, but separate copies of it are attached for each for the sake of clarity. The fix could be applied with some fuzz to branches as old as stable/train, and with some minor unit test adjustments as far back as stable/rocky. Note that the stable/wallaby branch is under extended maintenance (as are older branches) and will receive no new point releases, but a patch for it is provided as a courtesy. CVE: CVE-2022-47950 Proposed public disclosure date/time: 2023-01-17, 1500UTC Please do not make the issue public (or release public patches) before this coordinated embargo date. Original private report: https://launchpad.net/bugs/1998625 For access to read and comment on this report, please reply to me with your Launchpad username and I will subscribe you.
Bug#1029196: kylin-video: Has hard dependency on libmpv1 which doesn't exist
Note: Hardcoded dependency on libffmpegthumbnailer4v5 in debian/control
is also highly suspicious and should probably be removed as well.
(this is what ${shlibs:Depends} is for)
Thanks.
Bug#1029198: Bug#102919: additional logfile
while apt ist trying to make DKMS it is mentioned to get further informations when reading /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/make.log ''' # cat /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/make.log DKMS make.log for xtrx-0.0.1+git20190320.5ae3a3e-3.1 for kernel 6.1.0-1-amd64 (x86_64) Thu 19 Jan 14:59:03 CET 2023 make: Entering directory '/usr/src/linux-headers-6.1.0-1-amd64' CC [M] /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/xtrx.o /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/xtrx.c:518:27: error: initialization of ‘void (*)(struct uart_port *, struct ktermios *, const struct ktermios *)’ from incompatible pointer type ‘void (*)(struct uart_port *, struct ktermios *, struct ktermios *)’ [-Werror=incompatible-pointer-types] 518 | .set_termios= xtrx_uart_set_termios, | ^ /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/xtrx.c:518:27: note: (near initialization for ‘xtrx_uart_ops.set_termios’) cc1: some warnings being treated as errors make[1]: *** [/usr/src/linux-headers-6.1.0-1-common/scripts/Makefile.build:255: /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/xtrx.o] Error 1 make: *** [/usr/src/linux-headers-6.1.0-1-common/Makefile:2017: /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build] Error 2 make: Leaving directory '/usr/src/linux-headers-6.1.0-1-amd64' ''' sorry carsten echo '118sd[q]sa74967291083970656100331110sn[ln0=alnld%Plnld/snlbx]sblbxq'|dc
Processed: reassign 1029198 to xtrx-dkms, forcibly merging 1029135 1029198
Processing commands for cont...@bugs.debian.org: > reassign 1029198 xtrx-dkms Bug #1029198 [bugs.debian.org] bugs.debian.org: linux-image-6.1.0-1-amd64/testing ERROR:M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/b Bug reassigned from package 'bugs.debian.org' to 'xtrx-dkms'. Ignoring request to alter found versions of bug #1029198 to the same values previously set Ignoring request to alter fixed versions of bug #1029198 to the same values previously set > forcemerge 1029135 1029198 Bug #1029135 [xtrx-dkms] xtrx-dkms: xtrx module fails to build for kernel version 6.1 Bug #1029198 [xtrx-dkms] bugs.debian.org: linux-image-6.1.0-1-amd64/testing ERROR:M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/b Severity set to 'serious' from 'normal' Marked as found in versions xtrx-dkms/0.0.1+git20190320.5ae3a3e-3.1. Added tag(s) ftbfs. Merged 1029135 1029198 > thanks Stopping processing here. Please contact me if you need assistance. -- 1029135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029135 1029198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1028904, block 1028719 with 1028904
Processing commands for cont...@bugs.debian.org: > affects 1028904 src:willow Bug #1028904 [src:pillow] pillow: Lost tiff support after binNMU with tiff 4.5.0 Added indication that 1028904 affects src:willow > block 1028719 with 1028904 Bug #1028719 [src:willow] willow: FTBFS: AttributeError: module 'PIL._imaging' has no attribute 'libtiff_decoder' 1028719 was not blocked by any bugs. 1028719 was not blocking any bugs. Added blocking bug(s) of 1028719: 1028904 > thanks Stopping processing here. Please contact me if you need assistance. -- 1028719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028719 1028904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: python-igor: FTBFS: AttributeError: module 'numpy' has no attribute 'complex'
Processing control commands: > affects -1 src:arpys Bug #1028825 [src:python-igor] python-igor: FTBFS: AttributeError: module 'numpy' has no attribute 'complex' Added indication that 1028825 affects src:arpys > tags -1 patch Bug #1028825 [src:python-igor] python-igor: FTBFS: AttributeError: module 'numpy' has no attribute 'complex' Added tag(s) patch. -- 1028825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028825: python-igor: FTBFS: AttributeError: module 'numpy' has no attribute 'complex'
Control: affects -1 src:arpys Control: tags -1 patch A patch has been committed in git: https://salsa.debian.org/science-team/igor/-/commit/4f292cca1d326fea9162c4d857ad76b9328b23ab Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Re: arpys: FTBFS: AttributeError: module 'numpy' has no attribute 'complex'
Processing commands for cont...@bugs.debian.org: > notfound 1028729 arpys/2.0.2-3 Bug #1028729 [src:arpys] arpys: FTBFS: AttributeError: module 'numpy' has no attribute 'complex' No longer marked as found in versions arpys/2.0.2-3. > severity 1028729 normal Bug #1028729 [src:arpys] arpys: FTBFS: AttributeError: module 'numpy' has no attribute 'complex' Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1028729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028731: python-crank: FTBFS: ImportError: cannot import name 'getargspec' from 'inspect' (/usr/lib/python3.11/inspect.py)
Control: tags -1 patch The attached patch resolves the issue. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1diff -Nru python-crank-0.7.2/debian/changelog python-crank-0.7.2/debian/changelog --- python-crank-0.7.2/debian/changelog 2019-10-06 12:11:53.0 +0200 +++ python-crank-0.7.2/debian/changelog 2023-01-19 14:29:02.0 +0100 @@ -1,3 +1,11 @@ +python-crank (0.7.2-5.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add patch to fix FTBFS with python3.11. +(closes: #1028731) + + -- Bas Couwenberg Thu, 19 Jan 2023 14:29:02 +0100 + python-crank (0.7.2-5) unstable; urgency=medium [ Ondřej Nový ] diff -Nru python-crank-0.7.2/debian/patches/python3.11.patch python-crank-0.7.2/debian/patches/python3.11.patch --- python-crank-0.7.2/debian/patches/python3.11.patch 1970-01-01 01:00:00.0 +0100 +++ python-crank-0.7.2/debian/patches/python3.11.patch 2023-01-19 14:29:01.0 +0100 @@ -0,0 +1,25 @@ +Description: Don't used getargspec, removed in python3.11. +Author: Bas Couwenberg +Forwarded: not-needed +Bug-Debian: https://bugs.debian.org/1028731 + +--- a/crank/util.py b/crank/util.py +@@ -6,7 +6,7 @@ MIT License + """ + + import collections, sys, string +-from inspect import getargspec ++from inspect import getfullargspec + + __all__ = [ + 'get_argspec', 'get_params_with_argspec', 'remove_argspec_params_from_params', +@@ -31,7 +31,7 @@ def get_argspec(func): + try: + argspec = _cached_argspecs[im_func] + except KeyError: +-spec = getargspec(im_func) ++spec = getfullargspec(im_func) + argvals = spec[3] + + # this is a work around for a crappy api choice in getargspec diff -Nru python-crank-0.7.2/debian/patches/series python-crank-0.7.2/debian/patches/series --- python-crank-0.7.2/debian/patches/series2019-10-06 12:11:53.0 +0200 +++ python-crank-0.7.2/debian/patches/series2023-01-19 14:26:26.0 +0100 @@ -1 +1,2 @@ remove-broken-test.patch +python3.11.patch
Processed: Re: python-crank: FTBFS: ImportError: cannot import name 'getargspec' from 'inspect' (/usr/lib/python3.11/inspect.py)
Processing control commands: > tags -1 patch Bug #1028731 [src:python-crank] python-crank: FTBFS: ImportError: cannot import name 'getargspec' from 'inspect' (/usr/lib/python3.11/inspect.py) Added tag(s) patch. -- 1028731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029196: kylin-video: Has hard dependency on libmpv1 which doesn't exist
Source: kylin-video Severity: serious Version: 3.1.3-4 X-Debbugs-CC: jianfen...@ubuntukylin.com kylin-video is unable to migrate to Testing because it has Depends: libmpv1 in debian/control. libmpv1 is no longer built in Debian Testing; the new version is libmpv2. Please remove that line. It will automatically get a dependency on libmpv2 when it builds against libmpv-dev. Thank you, Jeremy Bicha
Processed: Re: python-makefun: FTBFS: make: *** [debian/rules:4: clean] Error 25
Processing commands for cont...@bugs.debian.org: > notfound 1028750 python-makefun/1.9.5-2 Bug #1028750 [src:python-makefun] python-makefun: FTBFS: make: *** [debian/rules:4: clean] Error 25 No longer marked as found in versions python-makefun/1.9.5-2. > severity 1028750 normal Bug #1028750 [src:python-makefun] python-makefun: FTBFS: make: *** [debian/rules:4: clean] Error 25 Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1028750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028775: python-ironic-lib: FTBFS: ModuleNotFoundError: No module named 'async_timeout'
On Sat, 14 Jan 2023 13:43:55 +0100 Lucas Nussbaum wrote: = Failures during discovery = --- import errors --- Failed to import test module: ironic_lib.tests.test_mdns Traceback (most recent call last): File "/usr/lib/python3.10/unittest/loader.py", line 436, in _find_test_path module = self._get_module_from_name(name) File "/usr/lib/python3.10/unittest/loader.py", line 377, in _get_module_from_name __import__(name) File "/<>/ironic_lib/tests/test_mdns.py", line 17, in import zeroconf File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 26, in from ._core import Zeroconf File "/usr/lib/python3/dist-packages/zeroconf/_core.py", line 36, in from ._handlers import ( File "/usr/lib/python3/dist-packages/zeroconf/_handlers.py", line 45, in from ._services.info import ServiceInfo File "/usr/lib/python3/dist-packages/zeroconf/_services/info.py", line 40, in from .._utils.asyncio import get_running_loop, run_coro_with_timeout File "/usr/lib/python3/dist-packages/zeroconf/_utils/asyncio.py", line 30, in from async_timeout import timeout as asyncio_timeout ModuleNotFoundError: No module named 'async_timeout' python3-zeroconf has this dependency: python3-async-timeout (>= 4.0.1) | python3 (>> 3.11) Because python3.11 is now default python3-async-timeout doesn't get installed even though it's still required for python3.10. python3-async-timeout should probably be an hard dependency of python3-zeroconf until python3.10 is removed. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
