Bug#1077749: Acknowledgement (samba-common: is missing its sid/repository (but is present in snapshot.debian.org)
$ apt policy samba-common samba-common: Installato: 2:4.21.0~rc1+dfsg-1 Candidato: 2:4.21.0~rc1+dfsg-1 Tabella versione: *** 2:4.21.0~rc1+dfsg-1 100 100 /var/lib/dpkg/status 2:4.17.12+dfsg-0+deb12u1 520 500 https://deb.debian.org/debian stable/main amd64 Packages 520 https://security.debian.org/debian-security stable-security/main amd64 Packages 2:4.17.9+dfsg-0+deb12u3 500 500 https://deb.debian.org/debian stable-updates/main amd64 Packages $ apt policy samba-common-bin samba-common-bin: Installato: 2:4.21.0~rc1+dfsg-1 Candidato: 2:4.21.0~rc1+dfsg-1 Tabella versione: *** 2:4.21.0~rc1+dfsg-1 700 700 https://deb.debian.org/debian sid/main amd64 Packages 100 /var/lib/dpkg/status 2:4.17.12+dfsg-0+deb12u1 520 500 https://deb.debian.org/debian stable/main amd64 Packages 520 https://security.debian.org/debian-security stable-security/main amd64 Packages 2:4.17.9+dfsg-0+deb12u3 500 500 https://deb.debian.org/debian stable-updates/main amd64 Packages # Sid Types: deb URIs: https://deb.debian.org/debian Suites: sid Components: main contrib non-free non-free-firmware Enabled: yes Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Bug#1077749: samba-common: is missing its sid/repository (but is present in snapshot.debian.org)
Package: samba-common Version: 2:4.21.0~rc1+dfsg-1 Severity: normal X-Debbugs-Cc: antde...@gmail.com Dear Maintainer, to inform that the latest updates of "samba" packages are blocked because "samba-common" rel. 2:4.21.0~rc1+really4.20.2+dfsg-11 does not seem to be present in Debian/sid repository (even if it is present on "https://packages.debian.org/sid/samba-common; it is present and on "snapshot.debian.org "https://snapshot.debian.org/archive/debian/20240730T204830Z/pool/main/s/samba/samba- common_4.21.0~rc1%2Breally4.20.2%2Bdfsg-11_all.deb") so I had to manually download this package from the snapshot site for continue the updates. Thanks, Antonio -- Package-specific info: * /etc/samba/smb.conf present, but not attached -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (700, 'unstable'), (520, 'stable-security'), (500, 'stable-updates'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.9.12-1-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages samba-common depends on: ii ucf 3.0043+nmu1 Versions of packages samba-common recommends: ii samba-common-bin 2:4.21.0~rc1+dfsg-1 samba-common suggests no packages. -- Configuration Files: /etc/samba/gdbcommands [Errno 2] File o directory non esistente: '/etc/samba/gdbcommands' -- debconf information excluded
Bug#1076729: Acknowledgement (libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1)
if I try to run in vm tremite kvm I get the same problem, however I can detect this error via ssh: lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: Refusing to try glamor on llvmpipe lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: EGL setup failed, disabling glamor lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: Failed to initialize glamor, falling back to sw lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) Backtrace: lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 0: /bin/Xwayland (0x617d65e6b000+0x188552) [0x617d65ff3552] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 1: /bin/Xwayland (0x617d65e6b000+0x18c08d) [0x617d65ff708d] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 2: /usr/lib/x86_64-linux-gnu/libc.so.6 (0x70a518a52000+0x3f59 0) [0x70a518a91590] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 3: /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 (wl_proxy _get_version+0x4) [0x70a5190e9244] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 4: /bin/Xwayland (0x617d65e6b000+0x46696) [0x617d65eb1696] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 5: /bin/Xwayland (0x617d65e6b000+0x406a6) [0x617d65eab6a6] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 6: /bin/Xwayland (0x617d65e6b000+0x115c95) [0x617d65f80c95] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 7: /bin/Xwayland (0x617d65e6b000+0xc10e4) [0x617d65f2c0e4] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 8: /bin/Xwayland (0x617d65e6b000+0xae572) [0x617d65f19572] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 9: /bin/Xwayland (0x617d65e6b000+0xaf646) [0x617d65f1a646] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 10: /bin/Xwayland (0x617d65e6b000+0xbaba9) [0x617d65f25ba9] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 11: /usr/lib/x86_64-linux-gnu/libc.so.6 (0x70a518a52000+0x29c 8a) [0x70a518a7bc8a] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 12: /usr/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x 85) [0x70a518a7bd45] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) 13: /bin/Xwayland (0x617d65e6b000+0x39ba1) [0x617d65ea4ba1] lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) Segmentation fault at address 0x40 lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: Fatal server error: lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE) Caught signal 11 (Segmentation fault). Server aborting lug 22 21:55:42 VIRTUAL kwin_wayland_wrapper[5367]: (EE)
Bug#1076729: Acknowledgement (libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1)
Operating System: Debian GNU/Linux sid KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Graphics Platform: Wayland Processors: 24 × 12th Gen Intel® Core™ i9-12900T Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 770 Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG STRIX B660-I GAMING WIFI
Bug#1076325: transition: c-blosc2
Package: release.debian.org Severity: normal X-Debbugs-Cc: c-blo...@packages.debian.org, antonio.valent...@tiscali.it Control: affects -1 + src:c-blosc2 User: release.debian@packages.debian.org Usertags: transition Hi dear release team, the upgrade from c-blosc2 v2.14.4 to v2.15.0 requires a change in the SONAME and hence a transition. The new version is already in experimental. The following source packages need to be rebuilt: pytables Ben file: title = "c-blosc2"; is_affected = .depends ~ "libblosc2-3" | .depends ~ "libblosc2-4"; is_good = .depends ~ "libblosc2-4"; is_bad = .depends ~ "libblosc2-3"; Please schedule binNMUs for the above mentioned packages on all architectures. Kind regards -- Antonio Valentino
Bug#1075803: failure piping "large" output to virtual machine
Package: autopkgtest Version: 5.28 Severity: normal X-Debbugs-Cc: aeru...@aerusso.net Dear Maintainer, I'm not sure if this bug belongs to sbuild, sbuild-qemu, or autopkgtest. The problem I am experiencing is that passing --extra-package with a large enough package (93 MB is the example I am running into). The copy to vm fails (hangs apparently indefinitely, and breaks further interaction with the VM). The stdin file on the 9p shared filesystem winds up the same size as stdin_eof flag-file. Is this limitation known and/or am I doing something wrong with the VM? Best, Antonio Russo OpenPGP_0xB01C53D5DED4A4EE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1074506: libsuitesparse-dev: Can't find: libspexpython.so.3
Hi Sébastien, El 30/6/24 a las 16:27, Sébastien Villemot escribió: Hi Jose, Le dimanche 30 juin 2024 à 06:58 +0200, Jose Antonio Salgueiro A. a écrit : Package: libsuitesparse-dev Version: 1:7.7.0+dfsg-2 Severity: normal X-Debbugs-Cc:jose.antonio...@gmail.com Your bug report does not contain any information. Do I understand correctly that this is a request for including the SPEX Python module in the Debian package for SuiteSparse? Or do you mean something else? Best wishes, There is a broken link: $ file /usr/lib/x86_64-linux-gnu/libspexpython.so /usr/lib/x86_64-linux-gnu/libspexpython.so: broken symbolic link to libspexpython.so.3 File libspexpython.so.3 does not exist. Now I am trying to look for the package with this file: /usr/lib/x86_64-linux-gnu/libspexpython.so.3 $apt-file search /usr/lib/x86_64-linux-gnu/libspexpython.so.3 No info. Thank you for your time! José Antonio S.A.
Bug#1033538: chkrootkit: Chkrootkit reports a false positive?
I had already set MAIL="" and it works, you can close this bug. Il 29/06/24 22:28, Richard Lewis ha scritto: On Tue, 28 Mar 2023 07:56:48 +0200 Antonio wrote: Thank Richard, I will do some tests with the diff mode. For now, I changed /etc/chkrootkit/chkrootkit.conf: MAILTO="journal" - and added this on "/usr/sbin/chkrootkit-daily": if [ "$MAILTO" = "journal" ]; then logger --file "$FILE" else mail -s "$SUBJECT" "$MAILTO" < "$FILE" fi for send the output to the journal. Reviewing this again -- I dont believe you need to edit chkrootkit-daily at all, simply set MAILTO="" in chkrootkit.conf and the output will end up on stdout, and systemd will put that into the journal So i think we might close this bug?
Bug#1074506: libsuitesparse-dev: Can't find: libspexpython.so.3
Package: libsuitesparse-dev Version: 1:7.7.0+dfsg-2 Severity: normal X-Debbugs-Cc: jose.antonio...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (800, 'testing'), (600, 'unstable'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.9.7-amd64 (SMP w/6 CPU threads; PREEMPT) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 Versions of packages libsuitesparse-dev depends on: ii libamd3 1:7.7.0+dfsg-2 ii libatlas-base-dev [liblapack.so]3.10.3-14 ii libblas-dev [libblas.so]3.12.0-3 ii libbtf2 1:7.7.0+dfsg-2 ii libcamd31:7.7.0+dfsg-2 ii libccolamd3 1:7.7.0+dfsg-2 ii libcholmod5 1:7.7.0+dfsg-2 ii libcolamd3 1:7.7.0+dfsg-2 ii libcxsparse41:7.7.0+dfsg-2 ii libklu2 1:7.7.0+dfsg-2 ii liblapack-dev [liblapack.so]3.12.0-3 ii libldl3 1:7.7.0+dfsg-2 ii libopenblas-pthread-dev [liblapack.so] 0.3.27+ds-2 ii libparu01:7.7.0+dfsg-2 ii librbio41:7.7.0+dfsg-2 ii libspex31:7.7.0+dfsg-2 ii libspqr41:7.7.0+dfsg-2 ii libsuitesparse-mongoose31:7.7.0+dfsg-2 ii libsuitesparseconfig7 1:7.7.0+dfsg-2 ii libumfpack6 1:7.7.0+dfsg-2 Versions of packages libsuitesparse-dev recommends: ii libgraphblas-dev 7.4.0+dfsg-1+b1 libsuitesparse-dev suggests no packages. -- no debconf information
Bug#1074406: release.debian.org: Help bpack migrate to testing
Package: release.debian.org Severity: normal X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org bpack (1.1.0-2) is not migrating to testing, apparently, due to an autopkgtest issue on s390x that is considered a regression https://qa.debian.org/excuses.php?package=bpack Looking at the logs the issue seems to be an unsatisfiable dependency, python3-bitstruct I would say. It is not clear to me why this is considered a regression, considering that bpack only recently has bee added to the archive and it never migrated to testing so far. Could you please help or suggest how to unlock the situation? Kind regards -- Antonio Valentino
Bug#1074353: libpython3.12-dev: Simple test file compilation failed with nuitka on Python 3.12
Package: libpython3.12-dev
Version: 3.12.4-1
Severity: normal
X-Debbugs-Cc: antde...@gmail.com
Dear Maintainer,
if I try to compile a simple test file with "nuitka":
print("TEST")
these errors return:
/bin/ld: /usr/lib/python3.12/config-3.12-x86_64-linux-
gnu/libpython3.12-pic.a(sha2module.o): in function
`SHA512Type_hexdigest':(.text+0x2ac): undefined reference to
`python_hashlib_Hacl_Hash_SHA2_digest_512'
/bin/ld: /usr/lib/python3.12/config-3.12-x86_64-linux-
gnu/libpython3.12-pic.a(sha2module.o): in function
`SHA512_dealloc':(.text+0x3c2): undefined reference to
`python_hashlib_Hacl_Hash_SHA2_free_512'
/bin/ld: /usr/lib/python3.12/config-3.12-x86_64-linux-
gnu/libpython3.12-pic.a(sha2module.o): in function
`SHA256Type_hexdigest':(.text+0x45c): undefined reference to
`python_hashlib_Hacl_Hash_SHA2_digest_256'
/bin/ld: /usr/lib/python3.12/config-3.12-x86_64-linux-
gnu/libpython3.12-pic.a(sha2module.o): in function
`SHA256Type_digest':(.text+0x4fc): undefined reference to
`python_hashlib_Hacl_Hash_SHA2_digest_256'
...
linux-gnu/libpython3.12-pic.a(sha2module.o): in function
`SHA512Type_update':(.text+0x8af): undefined reference to
`python_hashlib_Hacl_Hash_SHA2_update_512'/bin/ld: (.text+0x8c4): undefined
reference to `python_hashlib_Hacl_Hash_SHA2_update_512'/bin/ld: (.text+0x924):
undefined reference to `python_hashlib_Hacl_Hash_SHA2_update_512'/bin/ld:
(.text+0x9ef): undefined reference to
`python_hashlib_Hacl_Hash_SHA2_update_512'/bin/ld:
/usr/lib/python3.12/config-3.12-x86_64-linux-gnu/
...
libpython3.12-pic.a(sha2module.o): in function
`_sha2_sha384':(.text+0x1818): undefined reference to
`python_hashlib_Hacl_Hash_SHA2_malloc_384'/bin/ld: (.text+0x1851): undefined
reference to `python_hashlib_Hacl_Hash_SHA2_update_512'/bin/ld: (.text+0x18b6):
undefined reference to `python_hashlib_Hacl_Hash_SHA2_malloc_384'/bin/ld:
(.text+0x1977): undefined reference to
`python_hashlib_Hacl_Hash_SHA2_update_512'/bin/ld: (.text+0x1996): undefined
reference to `python_hashlib_Hacl_Hash_SHA2_update_512'collect2: error: ld
returned 1 exit status
while with the previous version of python 3.11 everything was fine: the problem
is in nuitka, or in the new python version?
I tested on Debian/sid, with "nuitka" 2.3.10 installed with "pipx" 1.6.0-1 (gcc
4:13.2.0-7).
command launched internally by scons:
gcc -o "/home/test/test.bin" -flto=24 -fuse-linker-plugin -fpartial-
inlining -freorder-functions -O2 -s -z noexecstack -Xlinker -export-dynamic
-rdynamic -Wl,-R,'/usr/lib' -Wl,--disable-new-dtags -Wl,-b -Wl,binary
-Wl,./__constants.bin -Wl,-b -Wl,elf64-x86-64 -Wl,-defsym
-Wl,constant_bin_data=_binary_constants_bin_start @"./@link_input.txt"
-L/usr/lib -ldl -lm "/usr/lib/python3.12/config-3.12-x86_64-linux-
gnu/libpython3.12-pic.a" -lz -lm -lutil -lpthread -lexpat
Thanks,
Antonio
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (700, 'unstable'), (520, 'stable-security'), (500,
'stable-updates'), (500, 'stable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.9.6-1-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libpython3.12-dev depends on:
ii libexpat1-dev 2.6.2-1
ii libpython3.12-stdlib 3.12.4-1
ii libpython3.12t64 3.12.4-1
ii zlib1g-dev1:1.3.dfsg+really1.3.1-1
Versions of packages libpython3.12-dev recommends:
ii libc6-dev [libc-dev] 2.38-13
libpython3.12-dev suggests no packages.
-- no debconf information
Bug#1072813: release.debian.org: Help doris migrate to testing
Dear Paul Il 10/06/24 20:38, Paul Gevers ha scritto: Hi, [...] If it is not a big issue on your side I would prefer to keep amd64 only. Ack, will do. Paul Thanks a lot -- Antonio Valentino
Bug#1072813: release.debian.org: Help doris migrate to testing
Dear Paul, thanks for your quick reply. On Sat, 8 Jun 2024 22:34:07 +0200 Paul Gevers wrote: Hi, On 08-06-2024 11:17 a.m., Antonio Valentino wrote: > Could you please clarify if there is something on my side that I should > do to allow doris to migrate? You could bootstrap doris on other architectures too, such that it's not only available on amd64 and this check of the migration tooling wouldn't block the package. It's a hint you might have not thought about doing it. If bootstrapping doris on non-amd64 isn't trivial, we can add a hint to ignore the installability on arm64. Paul The main problem with non-amd64 architecture is that I do not have easy access to them, I'm only DM. I think that in the past we had binaries for other platforms but it was quite a pain. For any small issue I needed to setup a quite lengthy process of requiring access to one of the porter-boxes, wait for the access to be granted, fix the issue, end them at the end, ask to a sponsor to build and upload binaries for different platforms. If it is not a big issue on your side I would prefer to keep amd64 only. kind regards -- Antonio Valentino
Bug#1072813: release.debian.org: Help doris migrate to testing
Package: release.debian.org Severity: normal X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org doris (5.0.3~beta+dfsg-17) is not migrating to testing, the excuses suggest this is due to unsatisfiable dependency for python3-doris/arm64: https://qa.debian.org/excuses.php?package=doris the missing dependency apparently is doris itself that is not build for arm64. Apparently this situation was file before the doris removal from testing due to one of the dependencies (fastkml [1]). Now fastkml is back in tasting so I would expect that doris could be able to migrate. Could you please clarify if there is something on my side that I should do to allow doris to migrate? [1] https://tracker.debian.org/news/1530835/doris-removed-from-testing/ Kind regards -- Antonio Valentino
Bug#1002996: [Bug #1002996] ITP: python-orjson -- fast, correct JSON library for Python
Dear Agathe, maturin is now packaged. Could I kindly ask an update on your plans for orjson? If you want I could try to help with the initial packaging work. Do you have some preliminary work somewhere? kind regards -- Antonio Valentino
Bug#1072343: transition: c-blosc2
Package: release.debian.org Severity: normal X-Debbugs-Cc: c-blo...@packages.debian.org, antonio.valent...@tiscali.it Control: affects -1 + src:c-blosc2 User: release.debian@packages.debian.org Usertags: transition Hi dear release team, the upgrade from c-blosc2 v2.13.1 to v2.14.4 requires a change in the SONAME and hence a transition. The new version is already in experimental. The following source packages need to be rebuilt: pytables Ben file: title = "c-blosc2"; is_affected = .depends ~ "libblosc2-2t64" | .depends ~ "libblosc2-3"; is_good = .depends ~ "libblosc2-3"; is_bad = .depends ~ "libblosc2-2t64"; Please schedule binNMUs for the above mentioned packages on all architectures. Kind regards -- Antonio Valentino
Bug#1072049: please provide a link to the artifacts on the page displaying the log
On Tue, May 28, 2024 at 08:38:04PM +0200, Paul Gevers wrote:
> Hi,
>
> Unfortunately
>
> On 28-05-2024 2:46 p.m., Antonio Terceiro wrote:
> > FWIW given this is pretty simple I also live patched the server.
>
> ..the link now is:
> https://ci.debian.net/packages/r/reform-setup-wizard/testing/s390x/47038806/%7B%20base_url%20%7D/artifacts.tar.gz
>
> Note the {base_url}/ which doesn't get replaced correctly... :(
meh. It's fixed now.
signature.asc
Description: PGP signature
Bug#1072049: please provide a link to the artifacts on the page displaying the log
On Tue, May 28, 2024 at 09:40:16AM -0300, Antonio Terceiro wrote: > Control: tag -1 + pending > > On Mon, May 27, 2024 at 10:10:46PM +0200, Johannes Schauer Marin Rodrigues > wrote: > > Source: debci > > Severity: wishlist > > > > Hi, > > > > when I stored artifacts for my autopkgtest job, I somehow expected the > > link to download the artifacts to be shown next to the log: > > > > https://ci.debian.net/packages/r/reform-setup-wizard/testing/s390x/47038806/ > > > > Because this is the page one is shown when clicking on failed results > > via tracker.d.o > > Yes. I have noticed this a few weeks ago and it has been done in git: > > https://salsa.debian.org/ci-team/debci/-/commit/f76020225d70bdd4573bbaf9570b8aae769dbc04 FWIW given this is pretty simple I also live patched the server. signature.asc Description: PGP signature
Bug#1072049: please provide a link to the artifacts on the page displaying the log
Control: tag -1 + pending On Mon, May 27, 2024 at 10:10:46PM +0200, Johannes Schauer Marin Rodrigues wrote: > Source: debci > Severity: wishlist > > Hi, > > when I stored artifacts for my autopkgtest job, I somehow expected the > link to download the artifacts to be shown next to the log: > > https://ci.debian.net/packages/r/reform-setup-wizard/testing/s390x/47038806/ > > Because this is the page one is shown when clicking on failed results > via tracker.d.o Yes. I have noticed this a few weeks ago and it has been done in git: https://salsa.debian.org/ci-team/debci/-/commit/f76020225d70bdd4573bbaf9570b8aae769dbc04 signature.asc Description: PGP signature
Bug#1068290: python3-fastkml: ImportError since python3-pygeoif 1.4.0
Dear Thomas and Andreas,
On Wed, 3 Apr 2024 01:22:14 +0100 Tomas Janousek wrote:
Hi,
On Wed, Apr 03, 2024 at 12:29:36AM +0100, Tomas Janousek wrote:
>I believe this is because both shapely and pygeoif deprecated
>asShape/as_shape respectively. The function is now called just "shape"
>in both.
>[…]
>I think it might be okay to just patch fastkml/geometry.py to
>
>from shapely.geometry import shape as asShape
>…
>from pygeoif.geometry import shape as asShape
>
>but it needs to be tested more thoroughly.
Yep, almost that. The following seems to work well (makes my CI pass):
https://github.com/liskin/liscopridge/commit/c44c3e6054af5a12bdf24d5687b6478d39480194#diff-e8ae9ced1dd6c13b4566c8a4a669116272e05115ce64aa743658523f4455ad5fR11
--
Tomáš "liskin" ("Pivník") Janoušek, https://lisk.in/
Apparently the fix was a little bit more complex that expected.
I think that I have managed to adapt the current version of the
python3-fastkml package to the new pygeoif.
A MR is available in salsa [1].
I would appreciate if you could review, apply the patch and proceed with
a new upload.
This would allow to "doris" one of my packages to migrate back in testing.
P.S:: @Andreas, I'm a DM and I would be happy to be listed as uploader
of this package if it is OK for you.
[1] https://salsa.debian.org/python-team/packages/fastkml/-/merge_requests/1
kind regards
--
Antonio Valentino
Bug#1058487: resampy: please (temporarily) drop python3-numba dependencies
Dear Graham On Tue, 12 Dec 2023 15:22:37 -0100 Graham Inggs wrote: Source: resampy Version: 0.4.2+ds-3 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer Your package has a dependency, build-dependency or autopkgtest dependency on python3-numba. Numba is currently not compatible with Python 3.12, although support is expected in the upcoming 0.59 release. Please drop these dependencies for now, so we can proceed with the Python 3.12 transition. As Numba often seems to lag behind major Python releases, please consider using Recommends instead of Depends to avoid having to make similar changes in future. Regards Graham I'm really sorry for the very late reply. I totally missed this bug. Currently resampy is not in testing so I assume that this is no longer blocking for you. Unfortunately this specific package does not make to much sense without numba, and the upstream code uses numba directly so it is not possible to run it without a working numba installation at the moment. It would require some heavy patching to put numba as a recommended dependency and, honestly, I would not be comfortable in having it not tested with numba. I'm not sure how to proceed with this bug. Unless you have any better suggestion probably I would tend to add the "wontfix" tag and close the bug. kind regards -- Antonio Valentino
Bug#1071443: unable to login as root at tty
Source: selinux-policy-default Version: 2:2.20221101-9 Severity: normal X-Debbugs-Cc: aeru...@aerusso.net Dear Maintainer, On a fresh bookworm installation, I have enabled selinux following [1]. I enabled enforcing mode, and tried to log in at the console tty (tty1, tty2, and tty6). journalctl -f shows an authentication error. Moreover, audit2why -al indicated that agetty was being denied when trying to use checkpoint_restore. I used audit2allow -m local to create a policy and then compile and load it. This eliminated the selinux denial audit event, but did not change the overall behavior: I cannot login as root at any ttys. I can, however, log in as regular user, and use su to elevate to root privileges, though. Creating a /etc/securetty file with tty0-tty6 and console does not change the situation. I've tried relabeling the filesystem several times. The remaining audit2why -al all seem innocuous: NetworkManager, run-parts, utmp, apcupds, ModemManager, wall The only possibly suspect one is comm="(spawn)" accessing files under /proc (scontext=system_u:system_r:udev_t:s0), thought I would think that's not a problem. I'm at a loss for what could be different between enforcing and permissive mode, and I'm not even sure what logs to look at. Best, Antonio [1] https://wiki.debian.org/SELinux/Setup OpenPGP_0xB01C53D5DED4A4EE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071405: gnome-calculator: Can't start on Gnome-46 Wayland: core dumped
Package: gnome-calculator Version: 1:46.0-1 Severity: important X-Debbugs-Cc: jose.antonio...@gmail.com Dear Maintainer, * What led up to the situation? I've update Debian. * What exactly did you do (or not do) that was effective (or ineffective)? Type gnome-calculator in gnome-terminal. * What was the outcome of this action? "core" * What outcome did you expect instead? Start graphical user interface. --- Sorry I can't attach core file, it's 256 MiB. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (800, 'testing'), (600, 'unstable'), (500, 'testing-proposed-updates'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.8.9-amd64 (SMP w/6 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-calculator depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4+b2 ii libadwaita-1-0 1.5.0-1 ii libc62.38-11 ii libglib2.0-0t64 2.80.2-1 ii libgtk-4-1 4.12.5+ds-6+b1 ii libgtksourceview-5-0 5.12.0-1 ii libmpc3 1.3.1-1+b2 ii libmpfr6 4.2.1-1+b1 ii libsoup-3.0-03.4.4-5+b1 ii libxml2 2.9.14+dfsg-1.3+b3 Versions of packages gnome-calculator recommends: ii gvfs 1.54.0-4 ii yelp 42.2-1+b2 gnome-calculator suggests no packages. -- no debconf information
Bug#1071201: systemd 256~rc2-1
I can confirm this version of systemd breaks my system's boot as well. I don't have any modified journald.conf settings. I'm running dracut, and the image that is built fails to start systemd-modules-load.service Running systemd-modules-load (rd.shell=1 rd.break=cmdline) at the (dracut) shell gave Failed to initialize libkmod context: Operation not supported I (too) was able to roll back to systemd 255.5-1 (dpkg -i /var/cache/apt/archives/*255.5-1*deb) fully restoring the system. Best, Antonio OpenPGP_0xB01C53D5DED4A4EE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071125: python3-donfig and python3-nabu have an undeclared file conflict on /usr/lib/python3/dist-packages/doc/conf.py
On Tue, 14 May 2024 22:23:45 +0200 Sebastiaan Couwenberg wrote: On 5/14/24 8:27 PM, Helmut Grohne wrote: > The file /usr/lib/python3/dist-packages/doc/conf.py is contained in the > packages > * python3-donfig/0.8.1+dfsg-2 as present in trixie|unstable > * python3-nabu/2024.1.6-1 as present in unstable Neither of these packages should be including this file. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ah, sorry. Should I reopen? -- Antonio Valentino
Bug#1070919: compyle: FTBFS in bullseye
Dear Santiago, Il 14/05/24 22:55, Santiago Vila ha scritto: El 14/5/24 a las 7:15, Antonio Valentino escribió: On Sat, 11 May 2024 21:46:59 +0200 Santiago Vila wrote: E error: unknown target CPU 'generic' I'm sorry but I have no clue about this issue. Looking at the log It seems that the CPU is not recognized. Yes, that's what it seems. Not sure, however if the issue is in compyle or in pyopencl. Do you have an idea if the updated versions of the package (e.g. the ones currently in stable or in unstable) build properly on the same platform? I tried building compyle_0.8.1-4 (bookworm version) in a bullseye chroot, and it failed with a similar error. On the other hand, both packages (compyle and pyopencl) build fine in bookworm (that's why the bugs are marked as closed in the bookworm version) in the same platform. So yes, this seems to be a problem in pyopencl. Because this is oldstable and packages are not expected to change, I think that whoever wants to build this from source will be able to use nocheck. Therefore, I think it would be ok to forget about this one. If you are curious, I'm filing these bugs because the last point release of bullseye will be the last one, so this is the last opportunity to have a distribution which builds from source. Release Policy does not apply anymore, so it is up to the individual maintainers to decide if they want to fix the bugs or not. Thanks. Thanks for dedicating time on this. Unfortunately I do not have better ideas so I think that we could leave things as they are now for the time being. kind regards -- Antonio Valentino
Bug#1070919: compyle: FTBFS in bullseye
Dear Santiago,
On Sat, 11 May 2024 21:46:59 +0200 Santiago Vila wrote:
Package: src:compyle
Version: 0.7-2
Severity: serious
Control: close -1 0.8.1-4
Tags: ftbfs bullseye
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
debian/rules binary
dh binary --with python3 --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:232: python3.9 setup.py config
running config
dh_auto_build -O--buildsystem=pybuild
I: pybuild base:232: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.9_compyle/build/compyle
copying compyle/ast_utils.py ->
/<>/.pybuild/cpython3_3.9_compyle/build/compyle
[... snipped ...]
E pyopencl._cl.RuntimeError: clBuildProgram failed: BUILD_PROGRAM_FAILURE
- clBuildProgram failed: BUILD_PROGRAM_FAILURE - clBuildProgram failed:
BUILD_PROGRAM_FAILURE
E
E Build on :
E
E error: unknown target CPU 'generic'
E
E (options: -I /usr/lib/python3/dist-packages/pyopencl/cl)
E (source saved as /tmp/tmp_oyjksbc.cl)
/usr/lib/python3/dist-packages/pyopencl/__init__.py:579: RuntimeError
TestParallelUtilsJIT.test_scan_works_with_external_func_opencl
func =
args = (,)
kwargs = {'ary': }
key = ('gintp', .input_f
at 0x7f95841ecb80>, .output_f at 0x7f957f8b1dc0>,
'a+b', 'opencl', False, ...)
@my_decorator
def _deco(func, *args, **kwargs):
# by Michele Simionato
# http://www.phyast.pitt.edu/~micheles/python/
key = key_func(*args, **kwargs)
try:
> return func._memoize_dic[key] # pylint: disable=protected-access
E KeyError: ('gintp', .input_f at 0x7f95841ecb80>,
.output_f at
0x7f957f8b1dc0>, 'a+b', 'opencl', False, True)
/usr/lib/python3/dist-packages/pytools/__init__.py:621: KeyError
During handling of the above exception, another exception occurred:
self =
I'm sorry but I have no clue about this issue.
Looking at the log It seems that the CPU is not recognized.
Not sure, however if the issue is in compyle or in pyopencl.
Do you have an idea if the updated versions of the package (e.g. the
ones currently in stable or in unstable) build properly on the same
platform?
kind regards
--
Antonio Valentino
Bug#1071034: unversioned libuv1 Provides: is inadequate
Source: libuv1
Version: 1.48.0-3
Severity: serious
X-Debbugs-Cc: aeru...@aerusso.net
Dear Maintainer,
libuv1 version 1.48.0-3 has an unversioned Provides: libuv1 line, but packages
(such as cmake) have
versioned dependencies on libuv1. This is breaking cmake in unstable right now.
It appears that dpkg-dev version 1.22.5 (or later) allows you to use
Provides: ${t64:Provides}
to automatically generate the versioned Provides: line.
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1063358: c-blosc2 tests fail with bus errors on armhf
Thanks Graham On Fri, 10 May 2024 13:14:41 + Graham Inggs wrote: Control: tags -1 + patch fixed-upstream This was fixed in Ubuntu and the patch forwarded upstream; https://github.com/Blosc/c-blosc2/pull/588 I will back port the patch immediately cheers -- Antonio Valentino
Bug#1070687: systemsettings: received signal SIGSEGV, Segmentation fault
Package: systemsettings
Version: 4:5.27.10-1+b1
Severity: normal
X-Debbugs-Cc: antde...@gmail.com
Dear Maintainer,
when I try to add a online account (Systemsettings->Pesonalization->Online
Accounts->Add new account... button) I get this error:
Thread 1 "systemsettings" received signal SIGSEGV, Segmentation fault.
0x7fffc40f8765 in Accounts::Provider::~Provider() () from
/usr/lib/x86_64-linux-gnu/libaccounts-qt5.so.1
where:
libaccounts-qt5-1=1.17-1
console log:
$ systemsettings
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding
loop detected for property "width"
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding
loop detected for property "width"
kf.runner: KRunner plugin "installer" still uses a .desktop file ("plasma-
runner-installer.desktop"). Please port it to JSON metadata.
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:288:18: QML QQuickItem*:
Binding loop detected for property "implicitWidth"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/templates/OverlaySheet.qml:603:17: QML
ColumnLayout: Binding loop detected for property "height"
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = systemsettings path = /usr/bin pid = 116311
KCrash: Arguments: /usr/bin/systemsettings
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
QSocketNotifier: Invalid socket 16 and type 'Read', disabling...
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
kf5idletime_wayland: This plugin does not support polling idle time
Thanks,
Antonio
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (700, 'unstable'), (500, 'stable-updates'), (500,
'stable-security'), (500, 'stable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.8.9-1-liquorix-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemsettings depends on:
ii kio 5.115.0-3
ii kpackagetool5 5.115.0-2
ii libc6 2.38-8
ii libkf5activities5 5.115.0-3
ii libkf5auth5 5.115.0-2
ii libkf5authcore5 5.115.0-2
ii libkf5completion5 5.115.0-2
ii libkf5configcore5 5.115.0-2
ii libkf5configgui55.115.0-2
ii libkf5configwidgets55.115.0-2
ii libkf5coreaddons5 5.115.0-2
ii libkf5crash55.115.0-2
ii libkf5dbusaddons5 5.115.0-2
ii libkf5i18n5 5.115.1-2
ii libkf5iconthemes5 5.115.0-2
ii libkf5itemmodels5 5.115.0-2
ii libkf5itemviews55.115.0-2
ii libkf5kcmutils5 5.115.0-2
ii libkf5kiocore5 5.115.0-3
ii libkf5kiogui5 5.115.0-3
ii libkf5kiowidgets5 5.115.0-3
ii libkf5kirigami2-5 5.115.0-2
ii libkf5notifications55.115.0-2
ii libkf5package5 5.115.0-2
ii libkf5runner5 5.115.0-2
ii libkf5service-bin 5.115.0-2
ii libkf5service5 5.115.0-2
ii libkf5widgetsaddons55.115.0-2
ii libkf5windowsystem5 5.115.0-2
ii libkf5xmlgui5 5.115.0-2
ii libkworkspace5-54:5.27.10-3+b1
ii libqt5core5t64 5.15.10+dfsg-7.2+b1
ii libqt5gui5t64 5.15.10+dfsg-7.2+b1
ii libqt5qml5 5.15.10+dfsg-2+b2
ii libqt5quick55.15.10+dfsg-2+b2
ii libqt5quickwidgets5 5.15.10+dfsg-2+b2
ii libqt5widgets5t64 5.15.10+dfsg-7.2+b1
ii libstdc++6 14-20240429-1
ii qml-module-org-kde-kcm 5.115.0-3
ii qml-module-org-kde-kcmutils 5.115.0-2
ii qml-module-org-kde-kirigami25.115.0-2
ii qml-module-org-kde-kitemmodels 5.115.0-2
ii qml-module-org-kde-newstuff 5.115.0-2
ii qml-module-qtquick-controls 5.15.10-2+b2
ii qml-module-qtquick-layouts 5.15.10+dfsg-2+b2
ii qml-module-qtquick-shapes 5.15.10+dfsg-2+b2
ii qml-module-qtquick2 5.15.10+dfsg-2+b2
systemsettings recommends no packages.
systemsettings suggests no packages.
-- no debconf information
Bug#1068422: possibly caused by python 3.12.3 Re: Bug#1068422: can't import dask.dataframe - TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' object
On Sun, 21 Apr 2024 13:07:41 +0100 "Rebecca N. Palmer" wrote: This bug is not *obviously* known to dask upstream, but their CI is failing and I haven't checked why. It happens only in Python 3.12, not 3.11: https://ci.debian.net/packages/d/dask/unstable/amd64/45013666/ and still doesn't happen in testing, but does happen in mostly-testing with src:python3-defaults,src:db5.3,src:keras,src:nodejs,src:openssl,src:python3-stdlib-extensions,src:python3.11,src:python3.12,src:readline,src:udisks2,src:viagee from unstable: https://ci.debian.net/packages/d/dask/testing/amd64/45564690/ This suggests that the trigger may be the upgrade of Python itself (3.12.2-1 in testing -> 3.12.3-1 in unstable). *Possibly* related items from the upstream Python changelog: https://github.com/python/cpython/issues/101293 https://github.com/python/cpython/issues/117110 Apparently this issue seems to be related to: https://github.com/dask/dask/pull/11035 regards -- Antonio Valentino
Bug#1069275: apt: random display of the "Summary:" line
Damn, I didn't notice, even though I had it under my nose the whole time...
Thanks for the explanation.
Il 19/04/24 15:26, David Kalnischkies ha scritto:
On Fri, Apr 19, 2024 at 02:06:44PM +0200, Antonio wrote:
If you find the "apt autoremove --purge" command in the sequence of the
commands I have indicated, you will notice that it appears three times:
- in second position produces this output:
$ apt autoremove --purge
^^^
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
- in seventh position it produces the same output
$ apt autoremove --purge
^^^
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
but the same command, in the fifteenth position produces a different output:
$ apt-get autoremove --purge
^^^
0 updated, 0 installed, 0 to be removed and 0 not updated.
what has changed? I would always expect the same output...
(Lets play a game! Lets call it: Spot the difference. )
As Julian already mentioned, "apt" and "apt-get" have different output.
This is intended (for compat) and not random, but yes, it can be a bit
confusing if your muscle memory lets you end up mix their use.
(Note that not only their output is different; they also have behaviour
differences e.g. "apt-get upgrade" vs "apt upgrade")
As an interactive user, its is probably best to forget apt-{get,cache,…}
exist and get used to 'apt'. If that is missing something compared to
the others feel free to report a bug so we can add it – or suggest an
alternative as sometimes that might be better approach.
Best regards
David Kalnischkies
Bug#1069292: libcurl4t64: regression: CURLINFO_REQUEST_SIZE returns 0
Package: libcurl4t64 Version: 8.7.1-2 Severity: important Tags: upstream patch Forwarded: https://github.com/curl/curl/issues/13269 Dear Maintainer, curl 8.7 no longer fills in the request_size field. This has been reported upstream in the following issue: https://github.com/curl/curl/issues/13269 This causes at least ruby-ethon, a Ruby library that wraps libcurl via FFI, to fail its test suite (after fixing it to not hardcode libcurl4 as a dependency), like this: 8<8<8<- Failures: 1) Ethon::Easy::Informations#request_size returns 53 Failure/Error: expect(easy.request_size).to eq(53) expected: 53 got: 0 (compared using ==) # ./spec/ethon/easy/informations_spec.rb:92:in `block (3 levels) in ' Finished in 5.06 seconds (files took 0.80166 seconds to load) 578 examples, 1 failure, 2 pending Failed examples: rspec ./spec/ethon/easy/informations_spec.rb:91 # Ethon::Easy::Informations#request_size returns 53 8<8<8<- (the same test suite passes just fine against libcurl4 8.6.0-3 from testing.) I have tested the patch in https://github.com/curl/curl/pull/13275 and it indeed fixes this. I'm including a patch against the Debian package in the archive that includes this patch in debian/patches, with the fuzzyness already removed, and updates debian/patches/series accordingly. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable-security'), (500, 'unstable'), (1, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 6.6.15-arm64 (SMP w/32 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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 Versions of packages libcurl4t64 depends on: ii libbrotli11.1.0-2+b3 ii libc6 2.37-15 ii libgssapi-krb5-2 1.20.1-5+b1 ii libidn2-0 2.3.7-2 ii libldap-2.5-0 2.5.13+dfsg-5+b3 ii libnghttp2-14 1.59.0-1 pn libpsl5t64 ii librtmp1 2.4+20151223.gitfa8646d.1-2+b2 pn libssh2-1t64 pn libssl3t64 ii libzstd1 1.5.5+dfsg2-2 ii zlib1g1:1.3.dfsg-3+b1 Versions of packages libcurl4t64 recommends: ii ca-certificates 20240203 libcurl4t64 suggests no packages. diff -Nru curl-8.7.1/debian/patches/Fix_CURLINFO_REQUEST_SIZE.patch curl-8.7.1/debian/patches/Fix_CURLINFO_REQUEST_SIZE.patch --- curl-8.7.1/debian/patches/Fix_CURLINFO_REQUEST_SIZE.patch 1970-01-01 00:00:00.0 + +++ curl-8.7.1/debian/patches/Fix_CURLINFO_REQUEST_SIZE.patch 2024-04-19 13:18:39.0 + @@ -0,0 +1,210 @@ +From 2793acbfc5e89fb130b1d4e045cb6cd7b6549412 Mon Sep 17 00:00:00 2001 +From: Stefan Eissing +Date: Thu, 4 Apr 2024 11:06:06 +0200 +Subject: [PATCH] Fix CURLINFO_REQUEST_SIZE, add tests for transfer infos + reported + +- refs #13269 +- tests for 'size_request' and other stats reported, for + presence and consistency +--- + lib/transfer.c | 3 + + tests/http/test_16_info.py | 162 + tests/http/testenv/httpd.py | 1 + + 3 files changed, 166 insertions(+) + create mode 100644 tests/http/test_16_info.py + +Index: curl-8.7.1/lib/transfer.c +=== +--- curl-8.7.1.orig/lib/transfer.c curl-8.7.1/lib/transfer.c +@@ -1221,6 +1221,9 @@ CURLcode Curl_xfer_send(struct Curl_easy + result = CURLE_OK; + *pnwritten = 0; + } ++ else if(!result && *pnwritten) ++data->info.request_size += *pnwritten; ++ + return result; + } + +Index: curl-8.7.1/tests/http/test_16_info.py +=== +--- /dev/null curl-8.7.1/tests/http/test_16_info.py +@@ -0,0 +1,162 @@ ++#!/usr/bin/env python3 ++# -*- coding: utf-8 -*- ++#*** ++# _ _ _ ++# Project ___| | | | _ \| | ++# / __| | | | |_) | | ++#| (__| |_| | _ <| |___ ++# \___|\___/|_| \_\_| ++# ++# Copyright (C) Daniel Stenberg, , et al. ++# ++# This software is licensed as described in the file COPYING, which ++# you should have received as part of this distribution. The terms ++# are also available at https://curl.se/docs/copyright.html. ++# ++# You may opt to use, copy, modify, merge, publish, distribute and/or sell ++# copies of the Software, and permit persons to whom the Software is ++# furnished to do so, under the terms of the COPYING file. ++# ++# This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY ++# KIND, either express or implied. ++# ++# SPDX-License-Identifier: curl ++#
Bug#1069275: apt: random display of the "Summary:" line
Hi,
I noticed this by chance, so I did some testing to find why the same
command produces two different outputs (note that I ran the commands one
after the other, as root, in the same session).
If you find the "apt autoremove --purge" command in the sequence of the
commands I have indicated, you will notice that it appears three times:
- in second position produces this output:
$ apt autoremove --purge
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
- in seventh position it produces the same output
$ apt autoremove --purge
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
but the same command, in the fifteenth position produces a different output:
$ apt-get autoremove --purge
0 updated, 0 installed, 0 to be removed and 0 not updated.
what has changed? I would always expect the same output...
It seems like this is a random issue because it doesn't always happen
(and I don't know how to reproduce it).
Il 19/04/24 13:28, Julian Andres Klode ha scritto:
On Fri, Apr 19, 2024 at 10:06:31AM +0200, Antonio wrote:
Package: apt
Version: 2.9.1
Severity: minor
X-Debbugs-Cc: antde...@gmail.com
Dear Maintainer,
I report a minor bug on apt that I sometimes get by running the commands
below
in sequence.
Note that in the last commands the "Summary:" line is not displayed whereas
previously, with the same commands, it was displayed.
I tried this sequence as root; as a user I see that the word "Summary" never
appears.
Seems to be a random problem.
Thank you for your bug report,
looking at your output, everything seems to be in order:
All your apt(8) executions use the apt(8) modern interface,
and all your apt-get(8) executions use the classic interface
- as they should for backwards-compatibility.
Is it possible your muscle memory is playing tricks on you, making
you type sudo apt-get whereas you use apt as a user?
But maybe I missed it, so do double check.
Have a nice day!
-- SEQUENCE --
$ apt autoremove
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
$ apt autoremove --purge
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
$ sudo apt autoremove --purge
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
$ (sudo apt autoremove --purge)
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
These are all apt(8) with the modern interface.
$ gawk '{print}'< <(sudo apt-get autoremove; sudo apt-get clean; sudo
apt-get
autoclean; sudo apt-get -f install; sudo apt-get check)
Lettura elenco dei pacchetti...
Generazione albero delle dipendenze...
Lettura informazioni sullo stato...
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
Lettura elenco dei pacchetti...
Generazione albero delle dipendenze...
Lettura informazioni sullo stato...
Lettura elenco dei pacchetti...
Generazione albero delle dipendenze...
Lettura informazioni sullo stato...
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
Lettura elenco dei pacchetti...
Generazione albero delle dipendenze...
Lettura informazioni sullo stato...
These are all apt-get(8) with the classic interface.
$ apt autoremove
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
$ apt autoremove --purge
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
$ (sudo apt autoremove --purge)
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
These are all apt(8) and all have the summary line.
$ sudo apt-get autoremove; sudo apt-get clean; sudo apt-get autoclean; sudo
apt-get -f install; sudo apt-get check
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
$ sudo apt-get autoremove
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
$ sudo apt-get autoremove
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
$ sudo apt-get autoremove --purge
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
$ sudo apt-get autoremove --purge
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
$ apt-get autoremove
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
$ apt-get autoremove --purge
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
These are all apt-get(8) which uses the classic interface.
Bug#1069275: apt: random display of the "Summary:" line
Package: apt
Version: 2.9.1
Severity: minor
X-Debbugs-Cc: antde...@gmail.com
Dear Maintainer,
I report a minor bug on apt that I sometimes get by running the commands
below
in sequence.
Note that in the last commands the "Summary:" line is not displayed whereas
previously, with the same commands, it was displayed.
I tried this sequence as root; as a user I see that the word "Summary" never
appears.
Seems to be a random problem.
Thanks,
Antonio
-- SEQUENCE --
$ apt autoremove
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
$ apt autoremove --purge
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
$ sudo apt autoremove --purge
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
$ (sudo apt autoremove --purge)
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
$ gawk '{print}'< <(sudo apt-get autoremove; sudo apt-get clean; sudo
apt-get
autoclean; sudo apt-get -f install; sudo apt-get check)
Lettura elenco dei pacchetti...
Generazione albero delle dipendenze...
Lettura informazioni sullo stato...
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
Lettura elenco dei pacchetti...
Generazione albero delle dipendenze...
Lettura informazioni sullo stato...
Lettura elenco dei pacchetti...
Generazione albero delle dipendenze...
Lettura informazioni sullo stato...
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
Lettura elenco dei pacchetti...
Generazione albero delle dipendenze...
Lettura informazioni sullo stato...
$ apt autoremove
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
$ apt autoremove --purge
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
$ (sudo apt autoremove --purge)
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
$ sudo apt-get autoremove; sudo apt-get clean; sudo apt-get autoclean; sudo
apt-get -f install; sudo apt-get check
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
$ sudo apt-get autoremove
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
$ sudo apt-get autoremove
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
$ sudo apt-get autoremove --purge
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
$ sudo apt-get autoremove --purge
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
$ apt-get autoremove
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
$ apt-get autoremove --purge
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (700, 'unstable'), (500, 'stable-updates'), (500,
'stable-security'), (500, 'stable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.8.6-3-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages apt depends on:
ii adduser 3.137
ii base-passwd 3.6.3
ii debian-archive-keyring 2023.4
ii gpgv 2.2.40-3
ii libapt-pkg6.0t64 2.9.1
ii libc6 2.37-17
ii libgcc-s1 14-20240330-1
ii libgnutls30t64 3.8.5-2
ii libseccomp2 2.5.5-1
ii libstdc++6 14-20240330-1
ii libsystemd0 255.4-1+b1
Versions of packages apt recommends:
ii ca-certificates 20240203
Versions of packages apt suggests:
pn apt-doc
ii aptitude 0.8.13-6
ii dpkg-dev 1.22.6
ii gnupg 2.2.40-3
ii gnupg2 2.2.40-3
ii powermgmt-base 1.37
ii synaptic 0.91.3+b1
-- no debconf information
Bug#1069217: pysolid ftbfs with Python 3.12
Dear Matthias, On Thu, 18 Apr 2024 07:33:50 +0200 Matthias Klose wrote: Package: src:pysolid Version: 0.3.2-1 Severity: important Tags: sid trixie patch User: debian-pyt...@lists.debian.org Usertags: python3.12 [...] dh binary --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild dh_auto_build -O--buildsystem=pybuild I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" module I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_pysolid * Building wheel... Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", line 353, in main() File "/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", line 335, in main json_out['return_val'] = hook(**hook_input['kwargs']) File "/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", line 251, in build_wheel return _build_backend().build_wheel(wheel_directory, config_settings, ^^ File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 434, in build_wheel return self._build_with_temp_dir( ^^ File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 419, in _build_with_temp_dir self.run_setup() File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 341, in run_setup exec(code, locals()) File "", line 6, in ModuleNotFoundError: No module named 'numpy.distutils' ERROR Backend subprocess exited when trying to invoke build_wheel Sorry I'm not able to reproduce. It seems more an issue in the setup rather than in pysolid. Moreover I see that this issue is tagged "patch" but I can't find a patch attached. Could you please provide more information about how to reproduce the issue? kind regards -- Antonio Valentino
Bug#1061661: python3-tables-lib [s390x] -- RoM ANAIS
Dear Paul, On Tue, 27 Feb 2024 19:56:21 +0100 Paul Gevers wrote: Hi all, On Sun, 28 Jan 2024 10:52:38 +0100 Antonio Valentino wrote: > Package: python3-tables-lib This bug would need to be reassigned to the ftp.debian.org pseudo package to actually do anything. > Version: 3.9.2-1 > Severity: normal > Tags: ftbfs > X-Debbugs-Cc: antonio.valent...@tiscali.it > > Dear Maintainer, > the new upstream version of pytables, v3.9.2, depends on c-blosc2 > that is not abailable on s390x. > Removing the python3-tables-lib binary package from s390x/unstable > should allow to pytables v3.9.2 to migrate into testing. Indeed. If nothing happens soon, I'll file an out-of-sync bug report which would lead to autoremoval starting. Paul any news on this issue? Is there still something missing on my side? kind regards -- Antonio Valentino
Bug#1068733: lvm2: resize lv error "/usr/libexec/lvresize_fs_helper: execvp failed"
Package: lvm2 Version: 2.03.22-1+b1 Severity: normal X-Debbugs-Cc: antde...@gmail.com Dear Maintainer, when I resize a logical volume I get this error: $ lvreduce --resizefs --size -5G /dev/system/test File system ext4 found on system/test. File system size (80,00 GiB) is larger than the requested size (76,00 GiB). File system reduce is required using resize2fs. File system fsck will be run before reduce. Reducing file system ext4 to 76,00 GiB (81604378624 bytes) on system/test... /usr/libexec/lvresize_fs_helper: execvp failed: File o directory non esistente Failed to reduce file system with lvresize_fs_helper. this issue is noted here: https://github.com/lvmteam/lvm2/issues/124 https://github.com/lvmteam/lvm2/blob/main/scripts/lvresize_fs_helper.sh because file missing: /usr/libexec/lvresize_fs_helper I solved it by downloading the file: sudo wget https://raw.githubusercontent.com/lvmteam/lvm2/main/scripts/lvresize_fs_helper.sh -O /usr/libexec/lvresize_fs_helper sudo chmod +x /usr/libexec/lvresize_fs_helper can you include this file in the package? Thanks, Antonio -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (700, 'unstable'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.8.4-2-liquorix-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lvm2 depends on: ii dmeventd 2:1.02.196-1+b1 ii dmsetup 2:1.02.196-1+b1 ii libaio1t640.3.113-8 ii libblkid1 2.40-5 ii libc6 2.37-16 ii libdevmapper-event1.02.1 2:1.02.196-1+b1 ii libedit2 3.1-20230828-1 ii libselinux1 3.5-2+b2 ii libsystemd0 255.4-1+b1 ii libudev1 255.4-1+b1 Versions of packages lvm2 recommends: ii thin-provisioning-tools 0.9.0-2 lvm2 suggests no packages. -- debconf information excluded
Bug#1068630: rsync: update to version 3.3.0
Package: rsync Version: 3.2.7-1+b2 Severity: wishlist X-Debbugs-Cc: antde...@gmail.com Dear Maintainer, can you update to the latest version? https://github.com/RsyncProject/rsync Thanks, Antonio -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (700, 'unstable'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.8.4-1-liquorix-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages rsync depends on: ii init-system-helpers1.66 ii libacl12.3.2-1 ii libc6 2.37-15.1 ii liblz4-1 1.9.4-2 ii libpopt0 1.19+dfsg-1+b1 ii libssl3t64 3.2.1-3 ii libxxhash0 0.8.2-2+b1 ii libzstd1 1.5.5+dfsg2-2 ii lsb-base 11.6 ii sysvinit-utils [lsb-base] 3.08-7 ii zlib1g 1:1.3.dfsg-3.1 rsync recommends no packages. Versions of packages rsync suggests: ii openssh-client 1:9.7p1-4 ii openssh-server 1:9.7p1-4 ii python3 3.11.8-1 pn python3-braceexpand -- Configuration Files: /etc/default/rsync changed [not included] -- no debconf information
Bug#1065348: chdist: perl warnings because of the deprecation of given ... when
On Sun, Mar 03, 2024 at 11:23:28AM +0100, Lucas Nussbaum wrote: > Package: devscripts > Version: 2.23.4+deb12u1 > Severity: normal > Tags: patch > > Hi, > > $ chdist list > given is deprecated at /usr/bin/chdist line 710. > when is deprecated at /usr/bin/chdist line 711. > when is deprecated at /usr/bin/chdist line 714. > when is deprecated at /usr/bin/chdist line 717. > when is deprecated at /usr/bin/chdist line 720. > when is deprecated at /usr/bin/chdist line 723. > when is deprecated at /usr/bin/chdist line 726. > when is deprecated at /usr/bin/chdist line 729. > when is deprecated at /usr/bin/chdist line 732. > when is deprecated at /usr/bin/chdist line 735. > when is deprecated at /usr/bin/chdist line 738. > when is deprecated at /usr/bin/chdist line 741. > when is deprecated at /usr/bin/chdist line 744. > when is deprecated at /usr/bin/chdist line 747. > when is deprecated at /usr/bin/chdist line 750. > when is deprecated at /usr/bin/chdist line 753. > when is deprecated at /usr/bin/chdist line 756. > when is deprecated at /usr/bin/chdist line 759. > when is deprecated at /usr/bin/chdist line 762. > > Attached is a patch that switches to if...elsif instead. You forgot the attachment. :-) signature.asc Description: PGP signature
Bug#1067229: metpy: autopkgtest regression with NumPy 1.26
Dear Timo, On Wed, 20 Mar 2024 16:58:12 +0100 =?utf-8?q?Timo_R=C3=B6hling?= wrote: Source: metpy Version: 1.6.1+ds-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package has an autopkgtest regression with NumPy 1.26. Hopefully relevant excerpt from the test log: 142s > if np.any(np.max(pressure, axis=vertical_dim) < 950 * units.hectopascal): 142s E TypeError: no implementation found for 'numpy.max' on types that implement __array_function__: [.Quantity'>] 142s 142s /usr/lib/python3/dist-packages/metpy/calc/thermo.py:4589: TypeError 142s === short test summary info 142s FAILED tests/calc/test_calc_tools.py::test_get_layer_heights_agl - TypeError:... 142s FAILED tests/calc/test_calc_tools.py::test_get_layer_heights_agl_bottom_no_interp 142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction - TypeError: no... 142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_edge - TypeErro... 142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_list - TypeErro... 142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_arr - TypeError... 142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_full - TypeErro... 142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_invalid_scalar 142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_invalid_arr - T... 142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_level_3 - TypeE... 142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_level_2 - TypeE... 142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_level_1 - TypeE... 142s FAILED tests/calc/test_kinematics.py::test_storm_relative_helicity_no_storm_motion 142s FAILED tests/calc/test_kinematics.py::test_storm_relative_helicity_storm_motion 142s FAILED tests/calc/test_kinematics.py::test_storm_relative_helicity_with_interpolation 142s FAILED tests/calc/test_kinematics.py::test_storm_relative_helicity - TypeErro... 142s FAILED tests/calc/test_kinematics.py::test_storm_relative_helicity_agl - Type... 142s FAILED tests/calc/test_kinematics.py::test_storm_relative_helicity_masked - T... 142s FAILED tests/calc/test_thermo.py::test_lfc_ml2 - TypeError: no implementation... 142s FAILED tests/calc/test_thermo.py::test_lfc_and_el_below_lcl - TypeError: no i... 142s FAILED tests/calc/test_thermo.py::test_gdi - TypeError: no implementation fou... 142s FAILED tests/calc/test_thermo.py::test_gdi_xarray - TypeError: no implementat... 142s FAILED tests/calc/test_thermo.py::test_gdi_arrays - TypeError: no implementat... 142s FAILED tests/calc/test_thermo.py::test_gdi_profile - TypeError: no implementa... 142s FAILED tests/calc/test_thermo.py::test_gdi_no_950_raises_valueerror - TypeErr... 142s = 25 failed, 937 passed, 25 skipped, 268 deselected in 21.69s == [CUT] According to what reported by upstream in https://github.com/Unidata/MetPy/issues/3453 the issue is linked to an outdated version of python3-pint. An update to Pint v0.22 should fix the issue. Reassign to point. kind reagrds -- Antonio Valentino
Bug#1067115: gross: diff for NMU version 1.0.2-4.1
On Sat, Mar 23, 2024 at 11:45:58PM +0200, Adrian Bunk wrote: > Control: tags 1067115 + patch > Control: tags 1067115 + pending > > Dear maintainer, > > I've prepared an NMU for gross (versioned as 1.0.2-4.1) and uploaded > it to DELAYED/2. Please feel free to tell me if I should cancel it. > Thanks for working on this, no reason to cancel it. Sorry I couldn't get to this faster enough
Bug#1066789: pycoast: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Dear Lucas, thanks for reporting. On Wed, 13 Mar 2024 15:58:32 +0100 Lucas Nussbaum wrote: Source: pycoast Version: 1.7.0+dfsg-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): [CUT] ERRORS ERROR collecting pycoast/tests/test_pycoast.py /usr/lib/python3/dist-packages/pluggy/_hooks.py:501: in __call__ return self._hookexec(self.name, self._hookimpls.copy(), kwargs, firstresult) /usr/lib/python3/dist-packages/pluggy/_manager.py:119: in _hookexec return self._inner_hookexec(hook_name, methods, kwargs, firstresult) /usr/lib/python3/dist-packages/_pytest/python.py:278: in pytest_pycollect_makeitem return list(collector._genfunctions(name, obj)) /usr/lib/python3/dist-packages/_pytest/python.py:507: in _genfunctions self.ihook.pytest_generate_tests.call_extra(methods, dict(metafunc=metafunc)) /usr/lib/python3/dist-packages/pluggy/_hooks.py:562: in call_extra return self._hookexec(self.name, hookimpls, kwargs, firstresult) /usr/lib/python3/dist-packages/pluggy/_manager.py:119: in _hookexec return self._inner_hookexec(hook_name, methods, kwargs, firstresult) /usr/lib/python3/dist-packages/pytest_lazyfixture.py:74: in pytest_generate_tests normalize_metafunc_calls(metafunc, 'funcargs') /usr/lib/python3/dist-packages/pytest_lazyfixture.py:81: in normalize_metafunc_calls calls = normalize_call(callspec, metafunc, valtype, used_keys) /usr/lib/python3/dist-packages/pytest_lazyfixture.py:105: in normalize_call valtype_keys = set(getattr(callspec, valtype).keys()) - used_keys E AttributeError: 'CallSpec2' object has no attribute 'funcargs' === warnings summary === ../../../../../../usr/lib/python3/dist-packages/_pytest/python.py:507 /usr/lib/python3/dist-packages/_pytest/python.py:507: PluggyTeardownRaisedWarning: A plugin raised an exception during an old-style hookwrapper teardown. Plugin: lazy-fixture, Hook: pytest_generate_tests AttributeError: 'CallSpec2' object has no attribute 'funcargs' For more information see https://pluggy.readthedocs.io/en/stable/api_reference.html#pluggy.PluggyTeardownRaisedWarning self.ihook.pytest_generate_tests.call_extra(methods, dict(metafunc=metafunc)) -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html === short test summary info ERROR ../../../pycoast/tests/test_pycoast.py - AttributeError: 'CallSpec2' ob... Interrupted: 1 error during collection = 1 warning, 1 error in 0.26s == the issue seems to be related to the pytest-lazyfixture package. See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063957. I will reassign. regards -- Antonio Valentino
Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2
On Tue, Mar 12, 2024 at 09:13:09PM +0100, Sebastian Andrzej Siewior wrote: > tried with 1.50+nmu2 which is in deferred for the next 11h. So tomorrow > it should be all good. Please make sure to commit the patch to the pristine-tar git repository as well. signature.asc Description: PGP signature
Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test
Dear maintainer, This bug is (apparently?) currently preventing the amd64 build of 1.20.1-6. I apologize if this is already understood (by the way, is there somewhere on [1] or elsewhere to see if the build is being retried?). I'm also assuming I am not authorized to "give back" and trigger another build attempt. So, I'm asking for someone to please "give back" the build to the buildds, so that we can spin the roulette wheel and hopefully get a buildd with an ipv4 address. Best, Antonio Russo [1] https://tracker.debian.org/pkg/krb5 OpenPGP_0xB01C53D5DED4A4EE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1065091: gtg: crashes on startup
Package: gtg Version: 0.6-6 Severity: grave Justification: renders package unusable Dear Maintainer, $ gtg 2024-02-29 14:44:05,373 - ERROR - application:do_activate:153 - Exception during activation Traceback (most recent call last): File "/usr/lib/python3/dist-packages/GTG/gtk/application.py", line 148, in do_activate self.init_shared() File "/usr/lib/python3/dist-packages/GTG/gtk/application.py", line 229, in init_shared self.init_plugin_engine() File "/usr/lib/python3/dist-packages/GTG/gtk/application.py", line 255, in init_plugin_engine self.plugin_engine.activate_plugins() File "/usr/lib/python3/dist-packages/GTG/core/plugins/engine.py", line 199, in activate_plugins plugin.active = True ^ File "/usr/lib/python3/dist-packages/GTG/core/plugins/engine.py", line 78, in _set_active self.instance = self.plugin_class() ^ AttributeError: 'Plugin' object has no attribute 'plugin_class' 2024-02-29 14:44:06,815 - INFO - errorhandler:handle_response:163 - Going to exit because either of fatal error or user choice Aborted Downgrading to 0.6-5 from snapshots makes it work again, so some change in 0.6-6 broke it entirely. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 6.6.15-arm64 (SMP w/32 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gtg depends on: ii gir1.2-gtk-3.0 [gir1.2-gdk-3.0] 3.24.41-1 ii gir1.2-gtksource-4 4.8.4-5+b1 ii gir1.2-pango-1.0 1.51.0+ds-4 ii gir1.2-secret-1 0.21.2-1 ii pdftk-java 3.3.3-2 ii python3 3.11.6-1 ii python3-caldav 0.11.0-2 ii python3-cheetah 3.3.3-1 ii python3-gi 3.47.0-3 ii python3-gi-cairo 3.47.0-3 ii python3-liblarch 3.2.0-3 ii python3-lxml 5.1.0-1 ii texlive-extra-utils 2023.20240207-1 ii texlive-latex-base 2023.20240207-1 gtg recommends no packages. gtg suggests no packages. -- no debconf information signature.asc Description: PGP signature
Bug#1059529: pybuild-autopkgtest: before-pybuild-autopkgtest target presence breaks autopkgtest
On Wed, Feb 28, 2024 at 10:51:31PM -0400, Stefano Rivera wrote: > Hi Antonio, > > Any thoughts on this bug? > > It seems dh doesn't like our hacks... > > > I have a package where I used a before-pybuild-autopkgtest in the > > debian/rules file, but when I run autopkgtest, it fails with the error > > message (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059334): > > > > dh before-pybuild-autopkgtest --buildsystem=pybuild > > dh: error: Unknown sequence before-pybuild-autopkgtest (choose from: binary > > binary-arch binary-indep build build-arch build-indep clean install > > install-arch install-indep) > > make: *** [debian/rules:13: before-pybuild-autopkgtest] Error 25 > > pybuild-autopkgtest: error: /tmp/pJ8OcCInAE/run before-pybuild-autopkgtest > > returned exit code 2 > > > > That's clearly wrong! It appears that that "%:" recipe overrides > > every other recipe in debian/rules, and is called when "debian/rules > > before-pybuild-autopkgtest" is called. I don't know if there's any > > way to override this behaviour. This was a bug in the python-bytecode debian/rules at that point: 40 │ before-pybuild-autopkgtest: 41 │ ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS))) 42 │ ifeq ($(DEB_BUILD_ARCH),armhf) 43 │ patch -p1 < debian/armhf.patch 44 │ endif 45 │ endif when the ifeq's don't evaluate to true (what happens everywhere but on armhf), the body of the `before-pybuild-autopkgtest` target is empty, and this causes make to call the default (%) target, which then calls `dh`. This can be reproduced in the following minimal example: 8<8<8<- $ cat Makefile ───┬─── │ File: Makefile ───┼─── 1 │ %: 2 │ @echo COMMON: $@ 3 │ 4 │ foo: 5 │ @echo FOO 6 │ 7 │ bar: ───┴─── $ make foo FOO $ make bar COMMON: bar 8<8<8<- This could have been fixed at the time by making the patching unconditional, or by patching the test itself to cause a skip on armhf. signature.asc Description: PGP signature
Bug#1064203: Typer is already available on Debian
Hi Sergio, On Thu, 22 Feb 2024 18:46:42 -0300 Sergio Cipriano wrote: Source: typer Source-Version: 0.9.0-2 Done: Sergio de Almeida Cipriano Junior Typer 0.9.0 is already available on Debian and it is being maintained in the python team. -- Sérgio Cipriano. Sorry, an oversight om my side. cheers -- Antonio Valentino
Bug#1062033: c-blosc2: NMU diff for 64-bit time_t transition
Hi Steve, On Wed, 31 Jan 2024 03:16:51 + Steve Langasek wrote: Source: c-blosc2 Version: 2.13.1+ds-1 Severity: serious Tags: patch pending Justification: library ABI skew on upgrade User: debian-...@lists.debian.org Usertags: time-t Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified c-blosc2 as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for c-blosc2 which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if information becomes available that your package should not be included in the transition, there is time for us to amend the planned uploads. Just uploaded to experimental a new version of the package with a small update of the symbol file. kind reards -- Antonio Valentino
Bug#1061620: autopkgtest: Ignores multiple comma-separated values in Testsuite
Control: forwarded -1
https://salsa.debian.org/ci-team/autodep8/-/merge_requests/33
On Sat, Jan 27, 2024 at 04:05:32PM +0100, Paul Gevers wrote:
> Hi,
>
> On 27-01-2024 15:41, Paul Gevers wrote:
> > Indeed, autopkgtest doesn't look at d/control at all. Both
> > autopkgtest-pkg-python and autopkgtest-pkg-pybuild are things that
> > autodep8 deals with and it needs to do the right thing. Reassigning.
>
> This seems to be problematic (note the "^" and "$" in the expression):
>
> detect_by_control_field() {
> local pkgtype="$1"
> [ -f debian/control ] &&
> grep-dctrl --quiet \
> -F XS-Testsuite,Testsuite \
> -r "^autopkgtest-pkg-$packagetype\$" debian/control
> }
>
> Paul
Fair enough. I have a proposed fix for this here:
https://salsa.debian.org/ci-team/autodep8/-/merge_requests/33
signature.asc
Description: PGP signature
Bug#1061661: python3-tables-lib [s390x] -- RoM ANAIS
Package: python3-tables-lib Version: 3.9.2-1 Severity: normal Tags: ftbfs X-Debbugs-Cc: antonio.valent...@tiscali.it Dear Maintainer, the new upstream version of pytables, v3.9.2, depends on c-blosc2 that is not abailable on s390x. Removing the python3-tables-lib binary package from s390x/unstable should allow to pytables v3.9.2 to migrate into testing. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 6.5.0-15-generic (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages python3-tables-lib depends on: ii libblosc1 1.21.5+ds-1+b1 ii libblosc2-2 2.13.1+ds-1 ii libbz2-1.0 1.0.8-5+b2 ii libc6 2.37-14 ii libhdf5-103-1 1.10.10+repack-3 ii liblzo2-2 2.10-2 ii python3 3.11.6-1 ii python3-numpy [python3-numpy-abi9] 1:1.24.2-2 Versions of packages python3-tables-lib recommends: pn python3-tables python3-tables-lib suggests no packages.
Bug#1061235: pandas: Unittest fail with PyTables 3.9.2
Source: pandas
Version: 1.5.3+dfsg-10
Severity: normal
Tags: ftbfs
X-Debbugs-Cc: antonio.valent...@tiscali.it
Dear Maintainer,
after the update of PyTables to v3.9.2 we observe a test failure in
Pandas 1.5.3
that prevents the migration of PyTables to testing.
It is just one single test failing. Please find below the relevant part
of the test loh:
1008s === FAILURES
===
1008s test_complibs
_
1008s 1008s setup_path = 'tmp.__c4b81039-45a4-414b-a25e-574aafd8d539__.h5'
1008s 1008s def test_complibs(setup_path):
1008s # GH14478
1008s df = tm.makeDataFrame()
1008s 1008s # Building list of all complibs and complevels
tuples
1008s all_complibs = tables.filters.all_complibs
1008s # Remove lzo if its not available on this platform
1008s if not tables.which_lib_version("lzo"):
1008s all_complibs.remove("lzo")
1008s # Remove bzip2 if its not available on this platform
1008s if not tables.which_lib_version("bzip2"):
1008s all_complibs.remove("bzip2")
1008s 1008s all_levels = range(0, 10)
1008s all_tests = [(lib, lvl) for lib in all_complibs for lvl in
all_levels]
1008s 1008s for (lib, lvl) in all_tests:
1008s with ensure_clean_path(setup_path) as tmpfile:
1008s gname = "foo"
1008s 1008s # Write and read file to see if data is
consistent
1008s df.to_hdf(tmpfile, gname, complib=lib, complevel=lvl)
1008s result = read_hdf(tmpfile, gname)
1008s tm.assert_frame_equal(result, df)
1008s 1008s # Open file and check metadata
1008s # for correct amount of compression
1008s h5table = tables.open_file(tmpfile, mode="r")
1008s for node in h5table.walk_nodes(where="/" + gname,
classname="Leaf"):
1008s assert node.filters.complevel == lvl
1008s if lvl == 0:
1008s assert node.filters.complib is None
1008s else:
1008s > assert node.filters.complib == lib
1008s E AssertionError: assert 'blosc2:blosclz' ==
'blosc2'
1008s E - blosc2
1008s E + blosc2:blosclz
1008s 1008s
/usr/lib/python3/dist-packages/pandas/tests/io/pytables/test_file_handling.py:266:
AssertionError
1008s === warnings summary
===
[CUT]
1008s -- Docs:
https://docs.pytest.org/en/stable/how-to/capture-warnings.html
1008s === short test summary info
1008s FAILED
../../../../usr/lib/python3/dist-packages/pandas/tests/io/pytables/test_file_handling.py::test_complibs
1008s = 1 failed, 10375 passed, 2570 skipped, 129 xfailed, 3 xpassed,
116 warnings in 206.35s (0:03:26) =
The probles seems more related to an issue in the test code rather then
a real bug in PyTables or Pandas.
Indeed the SW correctly report both the main compressor type, "blosc2"
and also the specific compression
filter by blosc2, "blosclz" in this case.
kind regards
antonio
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
Bug#1061058: RM: python3-compyle [ppc64el s390x] -- RoM ANAIS
Package: python3-compyle Version: 0.8.1-8 Severity: normal X-Debbugs-Cc: antonio.valent...@tiscali.it Dear Maintainer, apparently one of the build dependencies of compyle (pocl-opencl-icd) is no longer available on the ppc64el and s390x. This prevents the migration of compyle to testing. Removing python3-compyle for the ppc64el and s390x is expected to allow the migration of compyle to testing. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-14-generic (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages python3-compyle depends on: ii python3 3.11.6-1 pn python3-mako ii python3-numpy 1:1.24.2-2 pn python3-pytools ii python3-setuptools 68.1.2-2 python3-compyle recommends no packages. Versions of packages python3-compyle suggests: pn cython3 pn python3-pycuda pn python3-pyopencl
Bug#1060807: zfp: please compile zfp with -DBIT_STREAM_WORD_TYPE=uint8
Dear Frederic, On Sun, 14 Jan 2024 18:53:02 +0100 =?utf-8?q?Picca_Fr=C3=A9d=C3=A9ric-Emmanuel?= wrote: Source: zfp Severity: important Dear Maintainer, since the upload of zfp 1.0.1, the test of hdf5plugin are failing look at here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059842 It seems to me that the zfp library should be recompile with the previous flag. thanks Frederic. PS: Il also recompiled locally h5z-zfp and now the unit test is also failling with these errors H5Dcreate failed at line 405, errno=2 (No such file or directory) [ESC[31;01mFAILEDESC[0m] ./test_write_plugin zfpmode=2 prec=16 ...HDF5-DIAG: Error detected in HDF5 (1.10.10) thread 1: #000: ../../../src/H5D.c line 140 in H5Dcreate2(): unable to create dataset major: Dataset minor: Unable to initialize object [CUT] #011: ../../../src/H5Z.c line 852 in H5Z__prepare_prelude_callback_dcpl(): unable to apply filter major: Data filters minor: Error from filter 'can apply' callback #012: ../../../src/H5Z.c line 753 in H5Z__prelude_callback(): error during user callback the configuration of ZFP was changed in order to be able to run the ZFP automatic test suite. Apparently, the test code assumes `BIT_STREAM_WORD_TYPE=uint64` (see also [1]). If I revert the change I will need to disable many the ZFP tests. Apparently the problem seems to be linked to specific testing code bot on the ZFP and the python-hdf5plugin side. Honestly I cannot say what is the more appropriate configuration for `BIT_STREAM_WORD_TYPE`. How do you propose to proceed? [1] https://github.com/LLNL/zfp/issues/51 kind regards -- Antonio Valentino
Bug#1058301: resampy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
On Fri, 12 Jan 2024 08:07:41 +0100 s3v wrote: Dear Maintainer, > E If you are not working on Numba development, the original error was: 'cannot import name '_typeconv' from 'numba.core.typeconv' (/usr/lib/python3/dist-packages/numba/core/typeconv/__init__.py)'. > E For help, please visit: > E > E https://numba.readthedocs.io/en/stable/user/faq.html#numba-could-not-be-imported This is issue was fixed in numba/0.58.1+dfsg-1 [1] actually in unstable and I've verified your package builds fine locally and autopkg tests pass as well. Kind Regards [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058301 Thanks a lot -- Antonio Valentino
Bug#1060411: initramfs: can't boot bcachefs storage with multi devices
Package: initramfs-tools
Version: 0.142
Severity: minor
X-Debbugs-Cc: antde...@gmail.com
Dear Maintainer,
I report a problem encountered with initramfs, relating to the new bcachefs
file system.
To test it, I installed a debian/bookwork server, with kernel 6.7 vannilla
recompiled locally and prepared a storage with bcachefs (1 ssd cache + 2 hdd
for replicas):
disk1/ssd: /dev/sda -> /dev/sda1 for esp (LABEL=NEWEFI)
/dev/sda2 for cache bcachefs
(PARTUUID=ea702a10-728b-41d3-a80f-71cbf705dc28)
disk2/hdd: /dev/sdb -> /dev/sdb1 for storage bcachefs
(PARTUUID=679d2cdd-4dca-4707-83a8-0a86c095b345)
disk2/hdd: /dev/sdc -> /dev/sdc1 for storage bcachefs
(PARTUUID=09d070a2-449d-4c31-b214-cb225a0cbbaa)
I formatted it with command:
bcachefs format -LVMTEST --label=ssd.ssd1 /dev/sdb2 --label=hdd.hdd1 /dev/sdc1
--label=hdd.hdd2 /dev/sdd1 --replicas=2 --foreground_target=ssd
--promote_target=ssd --background_target=hdd
and mounted the root in the "/etc/fstab" file by adding the entries (indicating
"partuuid" of each device):
/dev/disk/by-partuuid/ea702a10-728b-41d3-a80f-71cbf705dc28:/dev/disk/by-
partuuid/679d2cdd-4dca-4707-83a8-0a86c095b345:/dev/disk/by-
partuuid/09d070a2-449d-4c31-b214-cb225a0cbbaa / bcachefs defaults,noatime 0
0
LABEL=NEWEFI /boot/efi vfatdefaults,noatime 0
0
using systemd loader with this entry:
title NEWTEST
linux /EFI/Linux/vmlinuz
options root=/dev/disk/by-
partuuid/ea702a10-728b-41d3-a80f-71cbf705dc28:/dev/disk/by-
partuuid/679d2cdd-4dca-4707-83a8-0a86c095b345:/dev/disk/by-
partuuid/09d070a2-449d-4c31-b214-cb225a0cbbaa rootfstype=bcachefs quiet
nosplash vga=791 noresume
initrd /EFI/Linux/initrd.img
This didn't work.
The problem is in the file "/usr/share/initramfs-tools/scripts/functions" and
depends on the "get_fstype" and "resolve_device" functions that cannot locate
or determine the file system (since bcachefs uses the form
device:device:device).
I managed to get it working by modifying these functions (see below)
Of course this is only a test, I just wanted to let you know about the issues
I've encountered.
Thanks,
Antonio
SIMPLE PATCH:
--- /usr/share/initramfs-tools/scripts/functions2023-10-04
07:43:51.432542921 +0200
+++ /desktop/functions 2024-01-10 20:52:19.103154941 +0100
@@ -198,6 +198,12 @@
# Return value: indicates if an fs could be recognized
get_fstype ()
{
+ if [ "$ROOTFSTYPE" == "bcachefs" ]; then
+ FSTYPE="$ROOTFSTYPE"
+ echo "$ROOTFSTYPE"
+ return 0
+ fi
+
local FS FSTYPE
FS="${1}"
@@ -429,12 +435,16 @@
resolve_device() {
DEV="$1"
- case "$DEV" in
- LABEL=* | UUID=* | PARTLABEL=* | PARTUUID=*)
- DEV="$(blkid -l -t "$DEV" -o device)" || return 1
- ;;
- esac
- [ -e "$DEV" ] && echo "$DEV"
+ if [ "$ROOTFSTYPE" != "bcachefs" ]; then
+ case "$DEV" in
+ LABEL=* | UUID=* | PARTLABEL=* | PARTUUID=*)
+ DEV="$(blkid -l -t "$DEV" -o device)" || return 1
+ ;;
+ esac
+ [ -e "$DEV" ] && echo "$DEV"
+ else
+ echo "$DEV"
+ fi
}
# Check a file system.
-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 63M Jan 8 19:04 /boot/initrd.img-6.6.10-3-liquorix-amd64
-- /proc/cmdline
audit=0 intel_pstate=disable rcupdate.rcu_expedited=1
initrd=\EFI\Linux\initrd.img root=LABEL=DEBIAN quiet nosplash vga=791
resume=LABEL=SWAP postazione=sat selinux=0
-- /proc/filesystems
cramfs
ext3
ext2
ext4
xfs
btrfs
nilfs2
jfs
f2fs
fuseblk
vfat
-- lsmod
Module Size Used by
snd_seq_dummy 12288 0
snd_hrtimer12288 1
rfcomm 69632 18
cmac 12288 3
algif_hash 12288 1
algif_skcipher 12288 1
af_alg 32768 6 algif_hash,algif_skcipher
qrtr 53248 4
bnep 20480 2
sunrpc835584 1
nls_utf8 12288 1
nls_cp437 16384 1
vfat 20480 1
fat98304 1 vfat
snd_hda_codec_hdmi 86016 1
snd_hda_codec_realtek 200704 1
snd_hda_codec_generic 114688 1 snd_hda_codec_realtek
rc_total_media_in_hand_0212288 0
si2157 16384 1
si2168 16384 1
snd_sof_pci_intel_tgl12288 0
snd_sof_intel_hda_common 192512 1 snd_sof_pci_intel_tgl
snd_soc_hdac_hda 20480 1 snd_sof_intel_hda_common
soundwire_intel57344 1 snd_sof_intel_hda_common
snd_sof_intel_hda_mlink32768 2 soundwire_intel,snd_sof_intel_hda_common
soundwire_cadence 40960 1 soundwire_intel
snd_
Bug#1059840: please bump --ram-size for qemu
On Wed, Jan 03, 2024 at 07:32:34AM +0100, Paul Gevers wrote: > Control: reassign -1 autopkgtest > > Hi Michael, > > On 02-01-2024 22:27, Michael Biebl wrote: > > You raise an interesting point though by framing this as an autopkgtest > > issue: Maybe the default in autopkgtest-virt-qemu should be bumped. > > This value was set in 2014 and systems have significantly more RAM > > nowadays. This way, one wouldn't have to remember to always pass > > --ram-size= when running autopkgtest by hand. > > A value of 2G or even 4G seems reasonable. WDYT? > > I think that sound reasonable, but I don't know how to sufficiently judge > this. Maybe my co-maintainers have ideas about it? I think we can use use the smaller of [4GB, 50% of the host RAM], to avoid killing a host where 4GB is more than what the host could reasonably afford. signature.asc Description: PGP signature
Bug#1059211: qemu-system-x86: QEMU/KVM guests: Window contents partially not updated
to reproduce the problem: qemu-system-x86_64 -machine q35,accel=kvm -cpu max -bios /usr/share/OVMF/OVMF_CODE.fd -audiodev id=alsa,drive r=alsa -device AC97,audiodev=alsa -m 8G -display gtk -full-screen -smp 16 -usb -device usb-tablet -drive file =redos,format=raw *-vga **virtio * adapters that work: - cirrus - qxl - vmware - std Il 22/12/23 12:23, Michael Tokarev ha scritto: Control: tag -1 + moreinfo 21.12.2023 13:36, Rainer Schwarzbach : Package: qemu-system-x86 Version: 1:8.2.0+ds-1 Severity: important X-Debbugs-Cc: rz49...@gmx.net Dear Maintainer, after the latest QEMU packages update, I noticed strange redraw issues in VM guests’ X windows. Please specify which vga device both of you are using, - is it virtio-vga or something else? Thanks, /mjt
Bug#1059211: qemu-system-x86: QEMU/KVM guests: Window contents partially not updated
Dear Maintainer, after updating to version "1:8.2.0+ds-1" I encountered the same problem with various VM relating to linux systems with Kde/Xfce graphical desktop (e.g. Debian, Arch etc...). Thank you, Anthony
Bug#1058937: /usr-move: Do we support upgrades without apt?
On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote: > ## Upgrading using dpkg directly? > > We already have quite a number of packages that use Conflicts to prevent > file loss in upgrades in a very similar way to #1058937 (Ben's > libnfsidmap1 bug) even in released versions of Debian. For instance, > dhcpcd-base's Replaces were upgraded to Conflicts, see #1053657. If you > employ dpkg, you can still experience the problem there. > > Is it ok to call upgrade scenarios failures that cannot be reproduced > using apt unsupported until we no longer deal with aliasing? I think so, yes. I don't think it's likely that there are people doing upgrades on running systems not using apt. If there are, they already need to deal with doing the dpkg calls in the right order anyway -- basically doing the apt dependency resolution by hand -- that this is just another corner case that they need to handle; there could be already Conflicts in there for other reasons than /usr-merge. signature.asc Description: PGP signature
Bug#1058301: resampy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
On Tue, 12 Dec 2023 09:24:48 +0100 Lucas Nussbaum wrote: Source: resampy Version: 0.4.2+ds-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_test > I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12_resampy/build; python3.12 -m pytest "" > = test session starts == > platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0 > rootdir: /<> > configfile: setup.cfg > plugins: cov-4.1.0 > collected 0 items / 3 errors > > ERRORS > ___ ERROR collecting .pybuild/cpython3_3.12_resampy/build/tests/test_core.py ___ > ImportError while importing test module '/<>/.pybuild/cpython3_3.12_resampy/build/tests/test_core.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > /usr/lib/python3/dist-packages/numba/core/typeconv/typeconv.py:4: in > from numba.core.typeconv import _typeconv > E ImportError: cannot import name '_typeconv' from 'numba.core.typeconv' (/usr/lib/python3/dist-packages/numba/core/typeconv/__init__.py) > > During handling of the above exception, another exception occurred: > /usr/lib/python3.12/importlib/__init__.py:90: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > tests/test_core.py:8: in > import resampy > resampy/__init__.py:7: in > from .core import * > resampy/core.py:7: in > import numba > /usr/lib/python3/dist-packages/numba/__init__.py:73: in > from numba.misc.special import ( > /usr/lib/python3/dist-packages/numba/misc/special.py:3: in > from numba.core.typing.typeof import typeof > /usr/lib/python3/dist-packages/numba/core/typing/__init__.py:1: in > from .context import BaseContext, Context > /usr/lib/python3/dist-packages/numba/core/typing/context.py:11: in > from numba.core.typeconv import Conversion, rules > /usr/lib/python3/dist-packages/numba/core/typeconv/rules.py:2: in > from .typeconv import TypeManager, TypeCastingRules > /usr/lib/python3/dist-packages/numba/core/typeconv/typeconv.py:16: in > raise ImportError(msg) > E ImportError: Numba could not be imported. > E > E If you are seeing this message and are undertaking Numba development work, you may need to rebuild Numba. > E Please see the development set up guide: > E The issue seems to be related to the fact that the numba package still do not support python 12. See also #1057461 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057461) cheers -- Antonio Valentino
Bug#1057688: aptitude: Stray input on window click when running under tmux
On 2023-12-08 09:01, Sven Joachim wrote: > > , > | @@ -8550,7 +8556,7 @@ tmux|tmux terminal multiplexer, > | use=ecma+italics, use=ecma+strikeout, use=xterm+edit, > | use=xterm+pcfkeys, use=xterm+sl, use=xterm+tmux, > | use=screen, use=bracketed+paste, use=report+version, > | - use=xterm+focus, > | + use=xterm+focus, use=xterm+sm+1006, > | > | tmux-256color|tmux with 256 colors, > | use=xterm+256setaf, use=tmux, > ` > > That seems to be not really intended and should likely be reverted, > given the issue at hand. I can confirm this change resolves the aptitude issue for me. I'll continue testing it. > >> (a change to the terminal description to help vim turned out to expose one >> of the VTE bugs - fixed by making it less likely for other applications >> to trigger the bug) > > There is no VTE involved in this case, I reproduced the problem in > xterm. > > Cheers, >Sven Thanks! Antonio OpenPGP_0xB01C53D5DED4A4EE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1055579: pytables and python 3.12
Dear Rebecca On Thu, 7 Dec 2023 08:05:05 + "Rebecca N. Palmer" wrote: That might not be enough: some of pandas' pytables-using tests are still failing in Python 3.12 (see salsa-ci). I will try to look at it during the weekend However, I don't know whether upgrading pytables to a newer upstream would break anything else. In this moment it is not an option because PyTables >= 3.8 requires c-blosc2 [1] that is still not in the archive. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038443 cheers -- Antonio Valentino
Bug#1057688: aptitude: Stray input on window click when running under tmux
Package: aptitude Version: 0.8.13-5 Severity: normal X-Debbugs-Cc: aeru...@aerusso.net Dear maintainer, If I run aptitude inside xterm, and click on an aptitude TUI element (say, a particular package), that package will be selected. If, instead, I am running aptitude inside tmux, and I click on said element, it appears many garbage characters are sent to aptitude, including probably m and M, (the symptom is the automatic install state of packages changes). If I manually set TERM=xterm inside the tmux window, everything works. Alternatively, outside of tmux, if I set TERM=tmux-256color I get the same bad behavior in aptitude. If I downgrade all ncurses packages to 6.4+20231016, I don't get this behavior. Maybe this bug should instead be assigned to ncurses? Best, Antonio Russo OpenPGP_0xB01C53D5DED4A4EE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1057105: dolphin: Dolphin File Explorer Selects Multiple Folders When Opening One Folder
Dear maintainer, I confirm the same occasional problem with version 4:23.08.1-1 (Debian/Sid) Thanks, Antonio
Bug#1056021: Link update
On Thu, 16 Nov 2023 22:51:11 +0100 (CET) gl...@debian.org wrote: Please use this link for logs http://qa-logs.debian.net/2023/10/26/pysolid_0.3.1-1_unstable_boost181.log Thanks Anton Sorry Anton, I'm not able to reproduce. Moreover I have to say that pysolid does not depend directly on boost. The only compiled code is a fortran file and the relative python extension generated automatically with f2py. Finally the log that you linked reports a successful build. Can we close this issue? kind regards -- Antonio Valentino
Bug#1056443: pysph ftbfs with Python 3.12
Dear Matthias, On Wed, 22 Nov 2023 13:49:03 +0100 Matthias Klose wrote: Package: src:pysph Version: 1.0~b1-6 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 pysph ftbfs with Python 3.12: [...] I: pybuild base:310: cd '/<>/.pybuild/cpython3_3.12/build'; python3.12 -m pytest -k "not test_sph_evaluator and not TestInterpolator and not test_get_points_from_mgrid and not test_get_surface_points_uniform" = test session starts == platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0 rootdir: /<> configfile: tox.ini collected 224 items / 29 errors / 91 deselected / 133 selected ERRORS _ ERROR collecting .pybuild/cpython3_3.12/build/pysph/base/tests/test_device_helper.py _ ImportError while importing test module '/<>/.pybuild/cpython3_3.12/build/pysph/base/tests/test_device_helper.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.12/importlib/__init__.py:90: in import_module return _bootstrap._gcd_import(name[level:], package, level) pysph/base/tests/test_device_helper.py:4: in from pysph.base.utils import get_particle_array # noqa: E402 pysph/base/utils.py:7: in from .particle_array import ParticleArray, \ pysph/base/particle_array.pyx:25: in init pysph.base.particle_array from compyle.array import Array, get_backend, to_device /usr/lib/python3/dist-packages/compyle/array.py:11: in from .sort import radix_sort /usr/lib/python3/dist-packages/compyle/sort.py:5: in from .transpiler import Transpiler, convert_to_float_if_needed /usr/lib/python3/dist-packages/compyle/transpiler.py:12: in from .ext_module import ExtModule /usr/lib/python3/dist-packages/compyle/ext_module.py:14: in from pyximport import pyxbuild /usr/lib/python3/dist-packages/pyximport/__init__.py:1: in from .pyximport import * /usr/lib/python3/dist-packages/pyximport/pyximport.py:51: in import imp E ModuleNotFoundError: No module named 'imp' _ ERROR collecting .pybuild/cpython3_3.12/build/pysph/base/tests/test_domain_manager.py _ ImportError while importing test module '/<>/.pybuild/cpython3_3.12/build/pysph/base/tests/test_domain_manager.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.12/importlib/__init__.py:90: in import_module return _bootstrap._gcd_import(name[level:], package, level) pysph/base/tests/test_domain_manager.py:8: in from pysph.base.nnps import DomainManager, BoxSortNNPS, LinkedListNNPS pysph/base/nnps.py:1: in This seems to be an issue in cython3. I will reassign it. cheers -- Antonio Valentino
Bug#1056525: sarsen's autopkg tests fail with Python 3.12
Dear Matthias,
On Wed, 22 Nov 2023 16:40:45 +0100 Matthias Klose wrote:
Package: src:sarsen
Version: 0.9.3+ds-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
sarsen's autopkg tests fail with Python 3.12:
[...]
624s import xarray_sentinel
624s File
"/usr/lib/python3/dist-packages/xarray_sentinel/__init__.py", line 23,
in
624s from .esa_safe import make_stac_item
624s File
"/usr/lib/python3/dist-packages/xarray_sentinel/esa_safe.py", line 8, in
624s import xmlschema
624s File "/usr/lib/python3/dist-packages/xmlschema/__init__.py", line
20, in
624s from .dataobjects import DataElement, DataElementConverter,
DataBindingConverter
624s File "/usr/lib/python3/dist-packages/xmlschema/dataobjects.py",
line 27, in
624s from . import validators
624s File
"/usr/lib/python3/dist-packages/xmlschema/validators/__init__.py", line
38, in
624s from .schemas import XMLSchemaMeta, XMLSchemaBase, XMLSchema,
XMLSchema10, XMLSchema11
624s File
"/usr/lib/python3/dist-packages/xmlschema/validators/schemas.py", line
2137, in
624s class XMLSchema10(XMLSchemaBase):
624s File
"/usr/lib/python3/dist-packages/xmlschema/validators/schemas.py", line
148, in __new__
624s meta_schema =
meta_schema_class.create_meta_schema(meta_schema_file)
624s
^^
624s File
"/usr/lib/python3/dist-packages/xmlschema/validators/schemas.py", line
763, in create_meta_schema
624s meta_schema = meta_schema_class(source, XSD_NAMESPACE,
global_maps=global_maps,
624s
^
624s File
"/usr/lib/python3/dist-packages/xmlschema/validators/schemas.py", line
357, in __init__
624s self.source = XMLResource(source, base_url, allow, defuse, timeout)
624s ^
624s File "/usr/lib/python3/dist-packages/xmlschema/resources.py",
line 511, in __init__
624s self.parse(source, lazy)
624s File "/usr/lib/python3/dist-packages/xmlschema/resources.py",
line 746, in parse
624s url = normalize_url(source, self._base_url)
624s ^
624s File "/usr/lib/python3/dist-packages/xmlschema/resources.py",
line 188, in normalize_url
624s path = _PurePath.from_uri(url)
624s^^^
624s File "/usr/lib/python3/dist-packages/xmlschema/resources.py",
line 109, in from_uri
624s return cls(uri)
624s
624s File "/usr/lib/python3/dist-packages/xmlschema/resources.py",
line 98, in __new__
624s return cast('_PurePath', cls._from_parts(args))
624s ^^^
624s AttributeError: type object '_PurePosixPath' has no attribute
'_from_parts'. Did you mean: '_load_parts'?
624s autopkgtest [20:06:43]: test autodep8-python3: ---]
624s autopkgtest [20:06:43]: test autodep8-python3: - - - - - - - - - -
results - - - - - - - - - -
624s autodep8-python3 FAIL non-zero exit status 1
This seems to be an issue related to xmlschema.
I will reassign.
cheers
--
Antonio Valentino
Bug#1056540: xarray-sentinel's autopkg tests fail with Python 3.12
Dear Matthias,
On Wed, 22 Nov 2023 17:11:47 +0100 Matthias Klose wrote:
Package: src:xarray-sentinel
Version: 0.9.5+ds-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
xarray-sentinel's autopkg tests fail with Python 3.12:
[...]
^
666s File
"/usr/lib/python3/dist-packages/xmlschema/validators/schemas.py", line
357, in __init__
666s self.source = XMLResource(source, base_url, allow, defuse, timeout)
666s ^
666s File "/usr/lib/python3/dist-packages/xmlschema/resources.py",
line 511, in __init__
666s self.parse(source, lazy)
666s File "/usr/lib/python3/dist-packages/xmlschema/resources.py",
line 746, in parse
666s url = normalize_url(source, self._base_url)
666s ^
666s File "/usr/lib/python3/dist-packages/xmlschema/resources.py",
line 188, in normalize_url
666s path = _PurePath.from_uri(url)
666s^^^
666s File "/usr/lib/python3/dist-packages/xmlschema/resources.py",
line 109, in from_uri
666s return cls(uri)
666s
666s File "/usr/lib/python3/dist-packages/xmlschema/resources.py",
line 98, in __new__
666s return cast('_PurePath', cls._from_parts(args))
666s ^^^
666s AttributeError: type object '_PurePosixPath' has no attribute
'_from_parts'. Did you mean: '_load_parts'?
666s autopkgtest [19:38:02]: test autodep8-python3: ---]
This seems to be an issue related to xmlschema.
I will reassign.
thanks
--
Antonio Valentino
Bug#1056539: xarray-safe-rcm's autopkg tests fail with Python 3.12
Dear Matthias,
On Wed, 22 Nov 2023 17:10:28 +0100 Matthias Klose wrote:
Package: src:xarray-safe-rcm
Version: 2023.06.1-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
xarray-safe-rcm's autopkg tests fail with Python 3.12:
[...]
232s /usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:186: in
exec_module
232s exec(co, module.__dict__)
232s
/usr/lib/python3/dist-packages/safe_rcm/tests/test_product_utils.py:7:
in
232s from safe_rcm.product import utils
232s /usr/lib/python3/dist-packages/safe_rcm/__init__.py:3: in
232s from .api import open_rcm # noqa: F401
232s /usr/lib/python3/dist-packages/safe_rcm/api.py:11: in
232s from .calibrations import read_noise_levels
232s /usr/lib/python3/dist-packages/safe_rcm/calibrations.py:10: in
232s from safe_rcm.product.reader import execute
232s /usr/lib/python3/dist-packages/safe_rcm/product/reader.py:7: in
232s from ..xml import read_xml
232s /usr/lib/python3/dist-packages/safe_rcm/xml.py:6: in
232s import xmlschema
232s /usr/lib/python3/dist-packages/xmlschema/__init__.py:20: in
232s from .dataobjects import DataElement, DataElementConverter,
DataBindingConverter
232s /usr/lib/python3/dist-packages/xmlschema/dataobjects.py:27: in
232s from . import validators
232s /usr/lib/python3/dist-packages/xmlschema/validators/__init__.py:38:
in
232s from .schemas import XMLSchemaMeta, XMLSchemaBase, XMLSchema,
XMLSchema10, XMLSchema11
232s
/usr/lib/python3/dist-packages/xmlschema/validators/schemas.py:2137: in
232s class XMLSchema10(XMLSchemaBase):
232s /usr/lib/python3/dist-packages/xmlschema/validators/schemas.py:148:
in __new__
232s meta_schema =
meta_schema_class.create_meta_schema(meta_schema_file)
232s /usr/lib/python3/dist-packages/xmlschema/validators/schemas.py:763:
in create_meta_schema
232s meta_schema = meta_schema_class(source, XSD_NAMESPACE,
global_maps=global_maps,
232s /usr/lib/python3/dist-packages/xmlschema/validators/schemas.py:357:
in __init__
232s self.source = XMLResource(source, base_url, allow, defuse, timeout)
232s /usr/lib/python3/dist-packages/xmlschema/resources.py:511: in __init__
232s self.parse(source, lazy)
232s /usr/lib/python3/dist-packages/xmlschema/resources.py:746: in parse
232s url = normalize_url(source, self._base_url)
232s /usr/lib/python3/dist-packages/xmlschema/resources.py:188: in
normalize_url
232s path = _PurePath.from_uri(url)
232s /usr/lib/python3/dist-packages/xmlschema/resources.py:109: in from_uri
232s return cls(uri)
232s /usr/lib/python3/dist-packages/xmlschema/resources.py:98: in __new__
232s return cast('_PurePath', cls._from_parts(args))
232s E AttributeError: type object '_PurePosixPath' has no attribute
'_from_parts'. Did you mean: '_load_parts'?
This seems to be an issue in xmlschema.
I will reassign.
cheers
--
Antonio Valentino
Bug#1056450: pytest-recording's autopkg tests fail with Python 3.12
Dear Matthias, On Wed, 22 Nov 2023 14:08:36 +0100 Matthias Klose wrote: Package: src:pytest-recording Version: 0.13.0-2 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 pytest-recording's autopkg tests fail with Python 3.12: [...] 382s I: pybuild base:310: cd /tmp/autopkgtest.KWZAe2/autopkgtest_tmp/build; python3.12 -m pytest --ignore=/tmp/autopkgtest.KWZAe2/autopkgtest_tmp/build/tests/test_recording.py -k "not test_blocked_network_recording and not test_block_network_with_allowed_hosts and not test_block_network_via_cmd_with_recording and not test_pycurl and not test_combine_cassettes" 383s Traceback (most recent call last): 383s File "", line 198, in _run_module_as_main 383s File "", line 88, in _run_code 383s File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 5, in 383s raise SystemExit(pytest.console_main()) 383s ^ [CUT] 383s File "", line 994, in exec_module 383s File "", line 488, in _call_with_frames_removed 383s File "/usr/lib/python3/dist-packages/pytest_httpbin/plugin.py", line 3, in 383s from httpbin import app as httpbin_app 383s File "/usr/lib/python3/dist-packages/httpbin/__init__.py", line 3, in 383s from .core import * 383s File "/usr/lib/python3/dist-packages/httpbin/core.py", line 36, in 383s from flasgger import Swagger, NO_SANITIZER 383s File "/usr/lib/python3/dist-packages/flasgger/__init__.py", line 10, in 383s from .base import Swagger, Flasgger, NO_SANITIZER, BR_SANITIZER, MK_SANITIZER, LazyJSONEncoder # noqa 383s ^^ 383s File "/usr/lib/python3/dist-packages/flasgger/base.py", line 36, in 383s from .utils import extract_definitions 383s File "/usr/lib/python3/dist-packages/flasgger/utils.py", line 5, in 383s import imp 383s ModuleNotFoundError: No module named 'imp' This seems to be an issue in flasgger. I will reassign. cheers -- Antonio Valentino
Bug#1056216: clinfo: Info Center...Graphics...OpenCL requires clinfo. Debian12 didn't install it.
Dear Maintainer, also add "wayland-utils" dependency, for fix wayland section. Thanks, Antonio
Bug#1055032: Please update to latest upstream version
On Fri, Nov 17, 2023 at 10:05:19AM +0100, Marcin Owsiany wrote: > Antonio, https://salsa.debian.org/terceiro/textual is now a 404. > Is your work available somwehere else? No, by mistake I ended up not making it public in the first place. It's public now. signature.asc Description: PGP signature
Bug#1055032: Please update to latest upstream version
On Sat, Nov 04, 2023 at 10:38:32AM -0300, Antonio Terceiro wrote: > On Fri, Nov 03, 2023 at 09:07:49PM -0300, Antonio Terceiro wrote: > > On Sun, Oct 29, 2023 at 09:29:04PM +0200, Jonathan Carter wrote: > > > Package: python3-textual > > > Severity: normal > > > X-Debbugs-Cc: > > > > > > Dear maintainer, > > > > > > The current version of python3-textual in Debian is quite out of date, > > > and it's not possible to run newer textual apps with it anymore., > > > Please upgrade to the latest upstream version (currenly (0.40.0) so > > > that this package can be useful again. > > > > I have a textual locally updated to the latest upstream version: > > https://salsa.debian.org/terceiro/textual > > > > I had to disable a few tests due to either missing dependencies, of > > mismatching expectations between the versions in Debian and the ones > > assumed by upstream (poetry.lock). There is still some work to do, e.g. > > converting the autopkgtest to use autopkgtest-pkg-pybuild. > > This is now done. > > BTW there is a new build dependency, python3-time-machine, which is in > NEW right now: > > https://salsa.debian.org/python-team/packages/python-time-machine FWIW this package has passed NEW and is even already in testing. signature.asc Description: PGP signature
Bug#1056034: systemd: some services don't start after systemd update)
You are not using a Debian kernel, so we cannot offer you support. Someone with the same broken kernel reported a similar issue upstream, and was redirected to the kernel supplier: https://github.com/damentz/liquorix-package/issues/147 I checked and in fact there are no problems with the latest version of the Debian kernel. Thanks for the information, I have reported it to the Liquorix maintainers. https://techpatterns.com/forums/about3055.html <https://techpatterns.com/forums/about3055.html> Antonio
Bug#1056034: systemd: some services don't start after systemd update
Package: systemd Version: 255~rc2-1 Severity: normal X-Debbugs-Cc: antde...@gmail.com Dear Maintainer, after updating "systemd" to version "255~rc2-1" some services do not start: - systemd-resolved.service: nov 16 08:57:37 SAT (resolved)[1183]: systemd-resolved.service: Failed to set up special execution directory in /run: Invalid argument - systemd-timesyncd.service: nov 16 08:57:37 SAT systemd[1]: Failed to start systemd-timesyncd.service - Network Time Synchronization. nov 16 08:57:37 SAT (imesyncd)[1249]: systemd-timesyncd.service: Failed to set up special execution directory in /run: Invalid argument - wpa_supplicant.service: nov 16 08:57:38 SAT (pplicant)[1943]: wpa_supplicant.service: Failed to set up special execution directory in /run: Invalid argument nov 16 08:57:38 SAT systemd[1]: Failed to start wpa_supplicant.service nov 16 08:58:46 SAT NetworkManager[1453]: [1700121526.2236] device (wlan0): Couldn't initialize supplicant interface: Failed to D-Bus activate wpa_supplicant service - systemd-tmpfiles nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/snd/seq failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/snd/timer failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/loop-control failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/net/tun failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/fuse failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/vfio/vfio failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/vhost-net failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/vhost-vsock failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/snd/seq failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/snd/timer failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/loop-control failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/net/tun failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/fuse failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/vfio/vfio failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/vhost-net failed: Invalid argument nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/vhost-vsock failed: Invalid argument nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/dbus/containers failed: Invalid argument nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/php failed: Invalid argument nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/rpcbind failed: Invalid argument nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/screen failed: Invalid argument nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/systemd/netif failed: Invalid argument nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/systemd/netif/links failed: Invalid argument nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/systemd/netif/leases failed: Invalid argument nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/systemd/netif/lldp failed: Invalid argument nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/utmp failed: Invalid argument nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/tpm2-tss/eventlog failed: Invalid argument nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/log/journal failed: Invalid argument nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /sys/kernel/security/tpm0/binary_bios_measurements failed: Invalid argument nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /sys/kernel/security/ima/binary_runtime_measurements failed: Invalid argument --- also note the truncated keywords "(pplicant)", "(imesyncd)" what has changed? Thanks, Antonio -- Package-specific info: -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (700, 'unstable'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.11-4-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii libacl12.3.1-3 ii libapparmor1 3.0.12-1 ii libaudit1 1:3.1.1-1 ii libblkid1 2.39.2-6 ii libc6 2.37-12 ii libcap21:2.66-4 ii libcryptsetup122:2.6.1-5 ii libfdisk1 2.39.2-6 ii libgcrypt201.10.2-3 ii libkmod2 30+2
Bug#1055753: debci: --config option is broken
On Fri, Nov 10, 2023 at 06:18:33PM +0100, Christian Kastner wrote: > Hi Antonio, > > On 2023-11-10 18:10, Antonio Terceiro wrote: > > Some shared options are defined in lib/environment.sh, I think that's > > why it currently loads lib/environment.sh before processing the command > > line options. > > > > OTH your analysis is correct, as this causes the --config option to be > > useless. A solution to this would be to break the common options into > > their own file, include that in the scripts, call getopt, process > > --config before anything else, then load lib/environment.sh for default > > values, and only then process the rest of the options. > > unless I'm misreading something badly, both default values *and* option > processing are in lib/environment.sh -- it's just that getopt is called > somewhat after some defaults have been set, like config_dir, arch, etc. > > My gut says moving getopt to the top of lib/environment.sh would fix > this, but its current position seemed like a deliberate choice, so I > assumed I was missing something. The currenty situation is more a product of oversight than of design. I'm wiling to review any solution you come up with. signature.asc Description: PGP signature
Bug#1055516: python3-jsonschema: New upstream version available
Hi, On Tue, 07 Nov 2023 18:27:49 +0100 Roland Mas wrote: Package: python3-jsonschema Version: 4.10.3-1 Severity: wishlist Dear Maintainer, There's a new upstream version (4.19) available, with at least one change in API (in the Draft*Validator constructors); jupyter-events, a package I'm working on, uses the new API, and therefore fails to run with the current 4.10 version. Could you provide an updated package? Thanks, Roland. I'm also interested in having and updated version of jsonschema to Support validation in pystack. Please not that the "referencing" package, a dependency on new jsonschema versions, is now available in Debian: https://tracker.debian.org/pkg/referencing kind regards -- Antonio Valentino
Bug#1055753: debci: --config option is broken
On Fri, Nov 10, 2023 at 04:42:10PM +0100, Christian Kastner wrote: > Package: debci > Version: 3.7 > Severity: normal > > The --config option to the debci subcommands does not work: > > $ mkdir /tmp/foo > $ echo 'debci_arch="i386"' > /tmp/foo/debci.conf > > $ debci config --config /tmp/foo config_dir > config_dir=/tmp/foo > > $ debci config --config /tmp/foo arch > arch=amd64 > > I believe that this is because it is processed too late. > > It is first processed at the top lib/environment.sh, where it is used to read > the config, and set important variables, like debci_arch above. > > Only after this has happened, its getopt(1) called. And I believe that all > that > --config does at that point, is to update debci_config_dir. > > > In fact, I believe all of the option parsing should be moved to the very top, > as least some other options are also broken this way: > > $ echo 'debci_arch_list="arm64 i386"' >> /tmp/foo/debci.conf > $ debci config --config /tmp/foo --arch=i386 arch > arch=i386 > $ debci config --config /tmp/foo --arch=i386 arch_list > arch_list=amd64 > > > I didn't want to file an MR outright, as I don't know the background behind > the > current solution, and there might be a good reason for it. Some shared options are defined in lib/environment.sh, I think that's why it currently loads lib/environment.sh before processing the command line options. OTH your analysis is correct, as this causes the --config option to be useless. A solution to this would be to break the common options into their own file, include that in the scripts, call getopt, process --config before anything else, then load lib/environment.sh for default values, and only then process the rest of the options. signature.asc Description: PGP signature
Bug#1055032: Please update to latest upstream version
On Fri, Nov 03, 2023 at 09:07:49PM -0300, Antonio Terceiro wrote: > On Sun, Oct 29, 2023 at 09:29:04PM +0200, Jonathan Carter wrote: > > Package: python3-textual > > Severity: normal > > X-Debbugs-Cc: > > > > Dear maintainer, > > > > The current version of python3-textual in Debian is quite out of date, > > and it's not possible to run newer textual apps with it anymore., > > Please upgrade to the latest upstream version (currenly (0.40.0) so > > that this package can be useful again. > > I have a textual locally updated to the latest upstream version: > https://salsa.debian.org/terceiro/textual > > I had to disable a few tests due to either missing dependencies, of > mismatching expectations between the versions in Debian and the ones > assumed by upstream (poetry.lock). There is still some work to do, e.g. > converting the autopkgtest to use autopkgtest-pkg-pybuild. This is now done. BTW there is a new build dependency, python3-time-machine, which is in NEW right now: https://salsa.debian.org/python-team/packages/python-time-machine signature.asc Description: PGP signature
Bug#1055032: Please update to latest upstream version
On Sun, Oct 29, 2023 at 09:29:04PM +0200, Jonathan Carter wrote: > Package: python3-textual > Severity: normal > X-Debbugs-Cc: > > Dear maintainer, > > The current version of python3-textual in Debian is quite out of date, > and it's not possible to run newer textual apps with it anymore., > Please upgrade to the latest upstream version (currenly (0.40.0) so > that this package can be useful again. I have a textual locally updated to the latest upstream version: https://salsa.debian.org/terceiro/textual I had to disable a few tests due to either missing dependencies, of mismatching expectations between the versions in Debian and the ones assumed by upstream (poetry.lock). There is still some work to do, e.g. converting the autopkgtest to use autopkgtest-pkg-pybuild. Sandro, Would it be OK if I push that into the python team repo and upload to the archive when I'm done? signature.asc Description: PGP signature
Bug#1055216: i915: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:84dffffb, in nautilus [191792]
Package: src:linux
Version: 6.1.55-1
Severity: important
File: i915
X-Debbugs-Cc: m...@apedik.dev
Dear Maintainer,
Nov 02 09:51:03 apedic gnome-shell[72591]: JS ERROR: TypeError: text is null
_processClipboardContent@/home/apedik/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:493:13
_refreshIndicator/<@/home/apedik/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:485:18
_refreshIndicator@/home/apedik/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:484:19
_onSelectionChange@/home/apedik/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:475:18
_setupSelectionTracking/this._selectionOwnerChangedId<@/home/apedik/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:556:18
Nov 02 09:51:20 apedic kernel: Asynchronous wait on fence
:00:02.0:gnome-shell[72591]:8487e timed out (hint:intel_atomic_commit_ready
[i915])
Nov 02 09:51:23 apedic kernel: i915 :00:02.0: [drm] GPU HANG: ecode
12:1:84db, in nautilus [191792]
Nov 02 09:51:23 apedic kernel: i915 :00:02.0: [drm] Resetting chip for
stopped heartbeat on rcs0
Nov 02 09:51:23 apedic kernel: i915 :00:02.0: [drm] *ERROR* rcs0 reset
request timed out: {request: 0001, RESET_CTL: 0001}
Nov 02 09:51:23 apedic kernel: i915 :00:02.0: [drm] *ERROR* rcs0 reset
request timed out: {request: 0001, RESET_CTL: 0001}
Nov 02 09:51:23 apedic kernel: i915 :00:02.0: [drm] nautilus[191792]
context reset due to GPU hang
Nov 02 09:51:23 apedic kernel: i915 :00:02.0: [drm] GuC firmware
i915/adlp_guc_70.bin version 70.5.1
Nov 02 09:51:23 apedic kernel: i915 :00:02.0: [drm] HuC firmware
i915/tgl_huc.bin version 7.9.3
Nov 02 09:51:24 apedic kernel: i915 :00:02.0: [drm] HuC authenticated
Nov 02 09:51:24 apedic kernel: i915 :00:02.0: [drm] GuC submission enabled
Nov 02 09:51:24 apedic kernel: i915 :00:02.0: [drm] GuC SLPC enabled
-- Package-specific info:
** Version:
Linux version 6.1.0-13-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP
PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64
root=UUID=3782c746-d533-4e01-8a7a-695a436d0af6 ro nvidia-drm.modeset=1 quiet
** Tainted: POE (12289)
* proprietary module was loaded
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
[4.954446] Bluetooth: hci0: Firmware Version: 107-51.22
[4.979191] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz,
REV=0x370
[4.979227] thermal thermal_zone12: failed to read out thermal zone (-61)
[5.133392] input: HDA Intel PCH Headphone Mic as
/devices/pci:00/:00:1f.3/sound/card0/input19
[5.133415] input: HDA Intel PCH HDMI/DP,pcm=3 as
/devices/pci:00/:00:1f.3/sound/card0/input20
[5.133432] input: HDA Intel PCH HDMI/DP,pcm=7 as
/devices/pci:00/:00:1f.3/sound/card0/input21
[5.133449] input: HDA Intel PCH HDMI/DP,pcm=8 as
/devices/pci:00/:00:1f.3/sound/card0/input22
[5.133465] input: HDA Intel PCH HDMI/DP,pcm=9 as
/devices/pci:00/:00:1f.3/sound/card0/input23
[5.151880] iwlwifi :00:14.3: firmware: direct-loading firmware
iwlwifi-so-a0-gf-a0.pnvm
[5.151897] iwlwifi :00:14.3: loaded PNVM version 64acdc51
[5.167435] iwlwifi :00:14.3: Detected RF GF, rfid=0x2010d000
[5.169589] audit: type=1400 audit(1698918793.372:2): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport"
pid=810 comm="apparmor_parser"
[5.169826] audit: type=1400 audit(1698918793.372:3): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="libreoffice-senddoc"
pid=808 comm="apparmor_parser"
[5.170243] audit: type=1400 audit(1698918793.376:4): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="lsb_release" pid=797
comm="apparmor_parser"
[5.170266] audit: type=1400 audit(1698918793.376:5): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="libreoffice-oosplash"
pid=807 comm="apparmor_parser"
[5.170688] audit: type=1400 audit(1698918793.376:6): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=800
comm="apparmor_parser"
[5.170690] audit: type=1400 audit(1698918793.376:7): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod"
pid=800 comm="apparmor_parser"
[5.170712] audit: type=1400 audit(1698918793.376:8): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/sbin/ntpd" pid=816
comm="apparmor_parser"
[
Bug#1054727: rails: FTBFS: build-dependency not installable: ruby-thin (>= 1.6.0)
Control: forcemerge 1054256 -1 Control affects 1054256 + src:rails On Fri, Oct 27, 2023 at 09:27:35PM +0200, Lucas Nussbaum wrote: > Source: rails > Version: 2:6.1.7.3+dfsg-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20231027 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > +--+ > > | Install package build dependencies > >| > > +--+ > > > > > > Setup apt archive > > - [...] > > Install main build dependencies (apt-based resolver) > > > > > > Installing build dependencies > > Reading package lists... > > Building dependency tree... > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > ruby-blade : Depends: ruby-thin (>= 1.6.0) but it is not installable > > E: Unable to correct problems, you have held broken packages. > > apt-get failed. This is caused by an issue with ruby-blade (already reported) signature.asc Description: PGP signature
Bug#1054256: ruby-blade: uninstallable in unstable (ruby-blade : Depends: ruby-thin (>= 1.6.0) but it is not installable)
Package: ruby-blade Version: 0.7.1-4 Severity: serious Justification: uninstallable After the last upload, ruby-blade ended up with a dependency on ruby-thin, which does not exist. 8<8<8<- $ LANG=C sudo apt install ruby-blade/unstable Reading package lists... Done Building dependency tree... Done Reading state information... Done Selected version '0.7.1-4' (Debian:unstable [all]) for 'ruby-blade' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ruby-blade : Depends: ruby-thin (>= 1.6.0) but it is not installable E: Unable to correct problems, you have held broken packages. 8<8<8<- The correct dependency would be on `thin`. This is actually caused by a bug in gem2deb (unreported), which was not finding the correct mapping between gem names and Debian package names for architecture dependent packages. In any case, ruby-blade will need a no changes upload to be rebuilt once gem2deb 2.2, just uploaded, is available. See https://salsa.debian.org/ruby-team/gem2deb/-/commit/827cb954c941872e24bb8f489d1a54cba416694b for more details. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 6.5.0-1-arm64 (SMP w/32 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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 Versions of packages ruby-blade depends on: ii ruby 1:3.1 ii ruby-activesupport2:6.1.7.3+dfsg-2 ii ruby-blade-qunit-adapter 2.0.1-2 ii ruby-curses 1.4.4-1+b2 ii ruby-eventmachine 1.3~pre20220315-df4ab006-3+b1 ii ruby-faye 1.4.0-1 ii ruby-sprockets3.7.2-4 pn ruby-thin ii ruby-thor 1.2.2-1 ii ruby-useragent0.16.8-1.1 ii thin 1.8.1-2 ruby-blade recommends no packages. ruby-blade suggests no packages. signature.asc Description: PGP signature
Bug#1053910: zfs: use zpool user properties instead of zfs user properties for scrub and trim cron scripts
What semantics are you thinking for handling upgrades? This does not appear to be a new zpool "feature", so we may want to support loading such a pool on an earlier version of our zfs packaging. How does this sound? - migrate the property if it exists (but do not remove the old, root filesystem one) - use the pool-level property if there's a conflict, but throw a warning if there's a discrepancy between the two - suggest people remove the old property if they don't need backwards compatibility in NEWS - in several version, start warning if the filesystem one is still around - several versions after that, stop even checking for the old property Antonio OpenPGP_0xB01C53D5DED4A4EE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1053473: xfce4-terminal version 1.0.4 has a bug and does not have the tab 'Shortcuts' in Terminal Preferences
Package: xfce4-terminal Version: 1.1.0-2 Severity: normal X-Debbugs-Cc: apmeirel...@gmail.com Dear Maintainer, xfce4-terminal version 1.0.4 has a bug and does not have the tab 'Shortcuts' in Terminal Preferences. If I install manually xfce4-terminal version 1.1.0 it shows the 'Shortcuts' tab correctly. This is how it was tested: Step 1: Manual download of the package: wget http://ftp.us.debian.org/debian/pool/main/x/xfce4-terminal/xfce4-terminal_1.1.0-2_amd64.deb Step 2: Installation of the package: sudo apt install ./xfce4-terminal_1.1.0-2_amd64.deb Step 3: Go to 'Terminal Preferences' and check for the presence of 'Shortcuts' tabs next to 'Advanced' tab -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-12-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xfce4-terminal depends on: ii exo-utils4.18.0-1 ii libatk1.0-0 2.46.0-5 ii libc62.36-9+deb12u3 ii libcairo21.16.0-7 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.74.6-2 ii libgtk-3-0 3.24.37-2 ii libpango-1.0-0 1.50.12+ds-1 ii libpcre2-8-0 10.42-1 ii libutempter0 1.2.1-3 ii libvte-2.91-00.70.6-1~deb12u1 ii libx11-6 2:1.8.4-2+deb12u1 ii libxfce4ui-2-0 4.18.2-2 ii libxfce4util74.18.1-2 ii libxfconf-0-34.18.0-2 ii perl 5.36.0-7 Versions of packages xfce4-terminal recommends: ii dbus-user-session [default-dbus-session-bus] 1.14.8-2~deb12u1 xfce4-terminal suggests no packages. -- no debconf information
Bug#1053296: RFS: kcollectd/0.12.1-1 -- simple collectd graphing front-end for KDE
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "kcollectd": * Package name : kcollectd Version : 0.12.1-1 Upstream contact : Antonio Russo * URL : https://www.antonioerusso.com/projects/kcollectd * License : GFDL-1.3+, PUBLIC-DOMAIN, GPL-3+ * Vcs : https://salsa.debian.org/qt-kde-team/extras/kcollectd Section : utils The source builds the following binary packages: kcollectd - simple collectd graphing front-end for KDE To access further information about this package, please visit the following URL: https://mentors.debian.net/package/kcollectd/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/k/kcollectd/kcollectd_0.12.1-1.dsc Changes since the last upload: kcollectd (0.12.1-1) unstable; urgency=medium . * New upstream release 0.12.1. - Align translations with source code (Closes: #1048793) * Bump Standards-Version to 4.6.2, no changes required. Best, Antonio Russo OpenPGP_0xB01C53D5DED4A4EE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1052817: sarsen: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
This seems to be the same issue reported in #1050832. The problem seems to be a regression in xarray v2023.08. The update to xarray > 2023.08 should fix the issue. See also https://github.com/bopen/sarsen/issues/54. I will reassign to xarray. [#1050832] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050832 -- Antonio Valentino
Bug#1051302: bookworm-pu: package jekyll/4.3.1+dfsg-3+deb12u1
On Sat, Sep 23, 2023 at 08:32:43PM +0100, Adam D. Barratt wrote: > Control: tags -1 confirmed > > This update fixes processing user configuration that used YAML > > aliases. > > > > [ Impact ] > > User configuration with YAML aliases will cause jekyll to crash while > > parsing it, and therefore jekyll will not work at all. > > > > Please go ahead. Uploaded. signature.asc Description: PGP signature
Bug#1051994: RFS: inkscape-textext/1.9.0-1 -- Re-editable LaTeX graphics for Inkscape
On 2023-09-22 07:29, Boyuan Yang wrote: > > You claimed that you are trying to validate upstream signatures, yet your > .dsc file as presented > on mentors.debian.net does not include tarball signature at all. Lintian is > also complaining > orig-tarball-missing-upstream-signature inkscape-textext_1.9.0.orig.tar.xz. > Do you want to try > to fix this problem, or let us upload the current version as-is first? > > Thanks, > Boyuan Yang Hello, Thanks for looking at this! Upstream does not release signed tarballs as far as I can tell. They sign git tags. I am using pgpmode=git for uscan. Is this the correct way to handle this? I have confirmed that uscan fails if I change upstream/signing-key.asc to another key : > gpgv: Signature made Wed Jul 26 03:24:55 2023 MDT > gpgv:using RSA key 32746E27876C1E5418BBBF7F7A9964831E98EED5 > gpgv: Can't check signature: No public key > uscan die: OpenPGP signature did not verify. at > /usr/share/perl5/Devscripts/Uscan/Output.pm line 77. I assume that means it is actually verifying the signature. Should I add a lintian override to capture this situation? Best, Antonio Russo OpenPGP_0xB01C53D5DED4A4EE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1041742: RFS: keepassxc-proxy-client/0.1.7-1 [ITP] -- Library to access a running KeepassXC instance
Dear mentors, I am looking for a sponsor for my package "keepassxc-proxy-client": * Package name : keepassxc-proxy-client Version : 0.1.7-1 Upstream contact : Henrik Böving * URL : https://github.com/hargoniX/keepassxc-proxy-client * License : ISC * Vcs : https://salsa.debian.org/aerusso-guest/keepassxc-proxy-client Section : python Description : Library to access a running KeepassXC instance KeepassXC is a password manager which exposes a interface to allow access-conntroled retrieval of passwords from its secure storage. keepassxc-proxy-client is a Python library that can speak this protocol, allowing programmatic access to passwords in the database. This packages also includes a simple CLI client build using the library. I am re-posting this RFS for this very small library in the hopes that I can get some feedback on the packaging. The source builds the following binary packages: keepassxc-proxy-client - Library to access a running KeepassXC instance To access further information about this package, please visit the following URL: https://mentors.debian.net/package/keepassxc-proxy-client/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/k/keepassxc-proxy-client/keepassxc-proxy-client_0.1.6-1.dsc Changes for the initial release: keepassxc-proxy-client (0.1.7-1) unstable; urgency=medium . * Initial release (Closes: #1041718) Best, Antonio Russo OpenPGP_0xB01C53D5DED4A4EE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1051994: RFS: inkscape-textext/1.9.0-1 -- Re-editable LaTeX graphics for Inkscape
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: aeru...@aerusso.net Dear mentors, I am looking for a sponsor for my package "inkscape-textext" * Package name: inkscape-textext Version : 1.9.0-1 Upstream Author : Jan Winkler * URL : https://textext.github.io/textext * License : BSD-3-clause * Vcs : https://salsa.debian.org/aerusso-guest/textext Section : graphics Description : Re-editable LaTeX graphics for Inkscape TexText is a Python plugin for the vector graphics editor Inkscape providing the possibility to add and re-edit LaTeX generated SVG elements to your drawing. Key features . Windows/Linux/MacOS support . LaTeX generated SVG elements can be re-edited later . Multi-line editor with syntax highlighting . Compilation with PdfLaTeX, XeLaTeX or LuaLaTex . Interoperable scaling in TexText and Inkscape . Font size match with Inkscape text . Customizable TeX preamble (additional packages, parskip, parindent, etc.) . Colorization via TeX commands/Inkscape is kept after re-editing . Alignment anchor of the produced output . Preview images It builds the binary packages: inkscape-textext - Re-editable LaTeX graphics for Inkscape inkscape-textext-doc - Re-editable LaTeX graphics for Inkscape (documentation) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/inkscape-textext/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/i/inkscape-textext/inkscape-textext_1.9.0-1.dsc Changes since the last upload: inkscape-textext (1.9.0-1) experimental; urgency=medium . * New upstream release * Refresh patches * Update debian/copyright * Bump standards version (no changes required) * Drop support for inkscape <1.3, matching upstream * Simplify build scripts * Validate upstream signatures * Relax architecture dependencies This upload is primarily to track upstream releases. Most notably, upstream has dropped support for inkscape <1.3, and I am tracking that change here. Best, Antonio Russo OpenPGP_0xB01C53D5DED4A4EE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1051900: ohcount: aborts with segfaul or bus error 90% of the time on arm64
Package: ohcount Version: 4.0.0-3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: debian-...@lists.debian.org Dear Maintainer, ohcount segfaults (and sometimes aborts with a Bus error) on arm64, almost 90% of the time. I tried this on an up to date arm64 Debian testing against the hexchat source code, but it's also reproducible on the ohcount source code itself. The same test, when performced on an up to date amd64 Debian testing, finishes successfully 100% of the time. For example this is a sample session with 10 runs against the source of ohcount itself: $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Bus error $ ohcount Examining 1192 file(s) Bus error $ ohcount Examining 1192 file(s) Bus error $ ohcount Examining 1192 file(s) Bus error $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Bus error -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 6.4.0-3-arm64 (SMP w/32 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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 Versions of packages ohcount depends on: ii file 1:5.45-2 ii libc6 2.37-7 ii libmagic1 1:5.45-2 ii libpcre3 2:8.39-15 ii ruby 1:3.1 ii ruby-diff-lcs 1.5.0-1 ohcount recommends no packages. Versions of packages ohcount suggests: pn ohcount-doc -- no debconf information signature.asc Description: PGP signature
Bug#1051563: mutt: CVE-2023-4874 CVE-2023-4875
On Sun, Sep 10, 2023 at 09:59:53PM +0200, Sebastian Andrzej Siewior wrote: > Hi Antonio! > > On 2023-09-10 15:57:58 [+0200], Antonio Radici wrote: > > On Sun, Sep 10, 2023 at 01:38:33PM +0200, Salvatore Bonaccorso wrote: > > > Hi Antonio, > > > > > > FWIW, I have done the bookworm-security upload already to > > > security-master, and still working on the bullseye-security one (with > > > plan to release the DSA tonight ideally). > > > > Ack, thanks for the update, I assume this was a particularly serious issue > > that > > had to be handled immediately! > > I pinged Salvatore on IRC about this and he was working on > stable/old-stable fix of the version at the time. So I suggest to help > out and prepare latest upstream from upstream for unstable (which was in > opinion only fixes). > Unfortunately I saw your reply to the bug after performing the update. > I'm sorry if I overstepped here. In the meantime I prepared a pull on > salsa for the changes I made. > As a matter of fact, I noticed that I somehow missed the latest > changelog from the package which I noticed while I tried to open the > pull request. After looking at it again, it looks like I just missed the > changelog entry. > > Once again, I'm sorry for any trouble I may have caused. Hi Sebastian, not a problem at all! It's just that I was unaware! You were much faster than me and that's definitely very good. Thanks a lot for your contribution to Debian, I really appreciate it :)
Bug#1051563: mutt: CVE-2023-4874 CVE-2023-4875
On Sun, Sep 10, 2023 at 01:47:30PM +0200, Salvatore Bonaccorso wrote: > Hi Antonio, > > On Sun, Sep 10, 2023 at 01:24:10PM +0200, Antonio Radici wrote: > > On Sun, Sep 10, 2023 at 01:05:31PM +0200, Antonio Radici wrote: > > > Thanks for raising this, I'm uploading the new packages with the fixes > > > today. > > > > apparently someone else did a NMU with the new version and incorrectly > > closed > > the bug. > > You mean the NMU by Sebastian? Yes > > > I reopened the bug because stable needs to be addressed (which I will do > > today > > as I just wrote) and then it's probably worth investigating how to integrate > > those NMU into the git repo > > Actually you do not need to reopen. A bug can be closed with mutliple > versions, that is 2.2.12-0.1 closes it, but as well so does then the > 2.2.9-1+deb12u1 upload and the 2.0.5-4.1+deb11u3 one. > > I think that was not the case several years ago, but nowdays BTS can > handle that, and will reflect it nicely as well in the version graph. > > Or were you meaning something different? Ah ok good, then I will add the extra versions if they are not there already
Bug#1051563: mutt: CVE-2023-4874 CVE-2023-4875
On Sun, Sep 10, 2023 at 01:38:33PM +0200, Salvatore Bonaccorso wrote: > Hi Antonio, > > FWIW, I have done the bookworm-security upload already to > security-master, and still working on the bullseye-security one (with > plan to release the DSA tonight ideally). Ack, thanks for the update, I assume this was a particularly serious issue that had to be handled immediately!
Bug#1051563: mutt: CVE-2023-4874 CVE-2023-4875
On Sun, Sep 10, 2023 at 01:05:31PM +0200, Antonio Radici wrote: > Thanks for raising this, I'm uploading the new packages with the fixes today. apparently someone else did a NMU with the new version and incorrectly closed the bug. I reopened the bug because stable needs to be addressed (which I will do today as I just wrote) and then it's probably worth investigating how to integrate those NMU into the git repo
Bug#1051563: mutt: CVE-2023-4874 CVE-2023-4875
On Sat, Sep 09, 2023 at 10:23:32PM +0200, Salvatore Bonaccorso wrote: > Source: mutt > Version: 2.2.9-1 > Severity: grave > Tags: security upstream > Justification: user security hole > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > > Hi, > > The following vulnerabilities were published for mutt. > > CVE-2023-4874[0]: > | Null pointer dereference when viewing a specially crafted email in > | Mutt >1.5.2 <2.2.12 > > > CVE-2023-4875[1]: > | Null pointer dereference when composing from a specially crafted > | draft message in Mutt >1.5.2 <2.2.12 > > Make sure to include all three commits referenced from [2], the last > one is technically not part of the two CVEs, but another crash found > by upstream. > > If you fix the vulnerabilities please also make sure to include the > CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. > > For further information see: > > [0] https://security-tracker.debian.org/tracker/CVE-2023-4874 > https://www.cve.org/CVERecord?id=CVE-2023-4874 > [1] https://security-tracker.debian.org/tracker/CVE-2023-4875 > https://www.cve.org/CVERecord?id=CVE-2023-4875 > [2] > http://lists.mutt.org/pipermail/mutt-announce/Week-of-Mon-20230904/56.html > > Please adjust the affected versions in the BTS as needed. Thanks for raising this, I'm uploading the new packages with the fixes today.
Bug#1050867: marked as pending in jekyll
On Fri, Sep 01, 2023 at 05:25:38PM +0200, Sébastien Villemot wrote: > Hi Antonio, > > Le mercredi 30 août 2023 à 15:33 +, Antonio Terceiro a écrit : > > Bug #1050867 in jekyll 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/ruby-team/jekyll/-/commit/78d57aff39390464d023660c55803806b6b7f06f > > > > > > Allow YAML aliases > > > > Closes: #1050867 > > > > Thanks for swiftly fixing this issue! > > Shouldn’t the fix be backported to bookworm? yes. I just submitted a stable update bug about it (#1051302) signature.asc Description: PGP signature
Bug#1051302: bookworm-pu: package jekyll/4.3.1+dfsg-3+deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: jek...@packages.debian.org Control: affects -1 + src:jekyll [ Reason ] This update fixes processing user configuration that used YAML aliases. [ Impact ] User configuration with YAML aliases will cause jekyll to crash while parsing it, and therefore jekyll will not work at all. [ Tests ] The change is trivial, and is already present in testing. [ Risks ] No risks. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] The only change is passing an extra parameter to Psych.safe_load, telling it to allow aliases in the YAML data. [ Other info ] n/a diff --git a/debian/changelog b/debian/changelog index b91ea6e..7ba5630 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +jekyll (4.3.1+dfsg-3+deb12u1) bookworm; urgency=medium + + [ Sébastien Villemot ] + * Allow YAML aliases (Closes: #1050867) + + -- Antonio Terceiro Tue, 05 Sep 2023 19:37:14 -0300 + jekyll (4.3.1+dfsg-2) unstable; urgency=medium * Team upload diff --git a/debian/patches/0016-Drop-usage-of-safe_yaml.patch b/debian/patches/0016-Drop-usage-of-safe_yaml.patch index 90aa06e..6caae5d 100644 --- a/debian/patches/0016-Drop-usage-of-safe_yaml.patch +++ b/debian/patches/0016-Drop-usage-of-safe_yaml.patch @@ -1,6 +1,9 @@ From: Antonio Terceiro Date: Sat, 21 Jan 2023 23:25:30 -0300 Subject: Drop usage of safe_yaml +MIME-Version: 1.0 +Content-Type: text/plain; charset="utf-8" +Content-Transfer-Encoding: 8bit Squashed commit of the following: @@ -22,6 +25,12 @@ Date: Thu Aug 19 13:42:39 2021 -0300 Use Psych as YAML parser +commit 5afe0f5acbc4cb9880bd2c752f45f39ba4f62835 +Author: Sébastien Villemot +Date: Wed, 30 Aug 2023 11:35:36 -0300 + +Enable YAML aliases + Source: https://github.com/jekyll/jekyll/pull/8772 Additional changes: - Also make the replacement of SafeYAML in lib/jekyll/commands/serve.rb @@ -193,7 +202,7 @@ index d6c5a0b..3757e04 100644 Jekyll.logger.info "Theme Config file:", theme_config_file diff --git a/lib/jekyll/utils.rb b/lib/jekyll/utils.rb -index 2a96527..0dfe2ec 100644 +index 2a96527..252541f 100644 --- a/lib/jekyll/utils.rb +++ b/lib/jekyll/utils.rb @@ -316,6 +316,20 @@ module Jekyll @@ -202,7 +211,7 @@ index 2a96527..0dfe2ec 100644 +# Safely load YAML strings +def safe_load_yaml(yaml) -+ Psych.safe_load(yaml, :permitted_classes => [Date, Time]) ++ Psych.safe_load(yaml, :permitted_classes => [Date, Time], aliases: true) +rescue ArgumentError + # Psych versions < 3.1 had a different safe_load API and used + # problematic language. signature.asc Description: PGP signature
