Processed: Bug#1026497 marked as pending in python-kafka
Processing control commands: > tag -1 pending Bug #1026497 [src:python-kafka] python-kafka: FTBFS: failed tests Added tag(s) pending. -- 1026497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026497: marked as pending in python-kafka
Control: tag -1 pending Hello, Bug #1026497 in python-kafka reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-kafka/-/commit/d43f49435e640a24fce977f8c7d436e03d4f4ed9 Add Fixes-ypeError_Population_must_be_a_sequence.patch (Closes: #1026497). (this message was generated automatically) -- Greetings https://bugs.debian.org/1026497
Bug#1026743: closing 1026743
close 1026743 thanks Howdy, Given barrier continues to build in up to date chroots, lack of further detail, and release of bookworm approaching, I'm closing this bug. ~Unit 193
Processed: closing 1026743
Processing commands for cont...@bugs.debian.org: > close 1026743 Bug #1026743 [src:barrier] barrier: FTBFS: make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1026743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028390: marked as done (boost1.81: autopkgtests test boost-defaults)
Your message dated Fri, 13 Jan 2023 07:22:39 + with message-id and subject line Bug#1028390: fixed in boost1.81 1.81.0-2 has caused the Debian Bug report #1028390, regarding boost1.81: autopkgtests test boost-defaults to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1028390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: boost1.81 Version 1.81.0-1 Severity: serious Hi Maintainer boost1.81's autopkgtests depend on packages from boost-defaults, so the autopkgtests are actually run against boost1.74. The autopkgtests used to have versioned dependencies, but that was changed [1] some time ago. Regards Graham [1] https://salsa.debian.org/debian/boost/-/commit/0bf0df0680f9255771424b7b0cd1aa040d847cdd --- End Message --- --- Begin Message --- Source: boost1.81 Source-Version: 1.81.0-2 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of boost1.81, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated boost1.81 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 13 Jan 2023 07:45:19 +0100 Source: boost1.81 Architecture: source Version: 1.81.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Boost Team Changed-By: Anton Gladky Closes: 1028390 Changes: boost1.81 (1.81.0-2) unstable; urgency=medium . * [b340cb8] Fix autopkgtests. Use 1.81 version. (Closes: #1028390) * [4835103] Avoid boost::phoenix::placeholders violations. * [f09f5a5] Trim trailing whitespace. * [f3a250a] Update standards version to 4.6.2, no changes needed. Checksums-Sha1: 67bfbf95aefe387c5f1d850353317df87aad628f 8898 boost1.81_1.81.0-2.dsc 53a8e56f73b254825f97d6276acae0f1c6cd7466 375076 boost1.81_1.81.0-2.debian.tar.xz ad14dccb2ac4a03197d287803e99a17b88b7473c 12710 boost1.81_1.81.0-2_source.buildinfo Checksums-Sha256: 0d474deca2ea0910656c31a22688876b4bd9456613fe70090449f112280fe9b5 8898 boost1.81_1.81.0-2.dsc 3b50c61d05773e89215c4dceb2ce307fe8c9e0f7536853f1318a900b948e0c73 375076 boost1.81_1.81.0-2.debian.tar.xz 6ece9c13ebfdf81f4a0bb56078a060be9e0cdb3436f986886e697d6f5ef4 12710 boost1.81_1.81.0-2_source.buildinfo Files: dabaed6eca1b3f1be0de10202ad327f6 8898 libs optional boost1.81_1.81.0-2.dsc 384bb3b36e943e1d6ed4d7e2df75cd94 375076 libs optional boost1.81_1.81.0-2.debian.tar.xz 48f09ab898c4dae8003111efab97e3ba 12710 libs optional boost1.81_1.81.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmPA/r4ACgkQ0+Fzg8+n /wZYBg/8DibJ3VGWHJarNjm9Sqe+mmJoEpL3v5RQixjIAXX3n+6eE018P4pQRGrQ 5Fw7t6IL2V5ipCJpLqi4ht58KwVbBe+RVGK+QixwxrAM9sd94a8Mk7KhQ+KRJPu6 mUSzn21SciqjdcPYBZVi4cHtEoqqmCnawtM5Csfg2PsbeF25UIujId1YhCHYQuDQ i68IrF5fxymzzgBqCCYFZB5MPbzxO2A/NCJ9OLggqnMxmotjetu7nNMLLzXw594V bXuqqip4pB90rpC95VaGTFzZ1lT3wC6gmrS+QUXS755x/GXFLNkWjywkkiReXVVU h+18ByYiLbN9P1f1MuaNJSxwKTD1VMK4OjKaruDI5sx4j37WZOwghF6Wba3tFOBq +dvDo3sB+xOveVbeL1pgvyFL7PHpMTgOrm3Ml44wRIO6FHRvwhmsDX/LK2t7TTMW 0AslIAJTqseBe37LQNSxZ43KqQc4bIxcRwjwvv+7CiOtCmSy0UzNkXo7laaeGicH BMbL3KCbQGwZ307yfhMM2kYhRtwueNpf59YYCfvq0oLKxeCzMBVsWtNMJ94BBdct ZSplu33lDD/+pzfOvTaZK7bZqYNeuxDRRmI60tY2Yt2d9Tiw3Aanm45zJjgOBz3v fd+wkLTwLW7Di7CkwGnFhNu9OH/ANPnq+BC9ze4n9S1cu0eltKI= =CVhl -END PGP SIGNATURE End Message ---
Bug#1028189: marked as done (gnustep-base/1.28.1-2 should not migrate to testing)
Your message dated Fri, 13 Jan 2023 07:25:32 + with message-id and subject line Bug#1028189: fixed in gnustep-base 1.28.1+really1.28.0-5 has caused the Debian Bug report #1028189, regarding gnustep-base/1.28.1-2 should not migrate to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1028189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnustep-base Version: 1.28.1-1 Severity: serious Justification: API/ABI break Filing this bug to block migration to testing. This upload will be reverted as it introduced silent API/ABI break. --- End Message --- --- Begin Message --- Source: gnustep-base Source-Version: 1.28.1+really1.28.0-5 Done: Yavor Doganov We believe that the bug you reported is fixed in the latest version of gnustep-base, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yavor Doganov (supplier of updated gnustep-base package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 09 Jan 2023 16:54:48 +0200 Source: gnustep-base Architecture: source Version: 1.28.1+really1.28.0-5 Distribution: unstable Urgency: medium Maintainer: Debian GNUstep maintainers Changed-By: Yavor Doganov Closes: 1028189 Changes: gnustep-base (1.28.1+really1.28.0-5) unstable; urgency=medium . * Revert uploads 1.28.1-1 and 1.28.1-2 thus restoring upstream 1.28.0 release. 1.28.1 was mistakently uploaded to unstable as it introduced an ABI break discovered post-factum (Closes: #1028189). * debian/gbp.conf: Set debian-branch to snafu. Checksums-Sha1: ae21db7a82d6e242027f70668495c6b68475be01 3055 gnustep-base_1.28.1+really1.28.0-5.dsc 5d33602d1e34274a5ed1c8379c1479c61f6ad907 4246622 gnustep-base_1.28.1+really1.28.0.orig.tar.gz 365c0bcbe5e4f8db248503b79a849b8d604b1544 232 gnustep-base_1.28.1+really1.28.0.orig.tar.gz.asc d53284a832116a9be58edbec9e2271a72e6ca8d4 32888 gnustep-base_1.28.1+really1.28.0-5.debian.tar.xz 6791206ef7932edcd3109b247d1022caf28f9078 7929 gnustep-base_1.28.1+really1.28.0-5_source.buildinfo Checksums-Sha256: f12505332c1331c31ddef07fb06a4e4b1007c3cda6756052127d4576d75f9b7d 3055 gnustep-base_1.28.1+really1.28.0-5.dsc c7d7c6e64ac5f5d0a4d5c4369170fc24ed503209e91935eb0e2979d1601039ed 4246622 gnustep-base_1.28.1+really1.28.0.orig.tar.gz e51a47c832edfd166da1d1ed961730865755004a84acd82ecd4b7761c03ea6fc 232 gnustep-base_1.28.1+really1.28.0.orig.tar.gz.asc 296d40be08980874bb84232c4e65f3a10c2fe135c1555dca5ab589cb99b8267a 32888 gnustep-base_1.28.1+really1.28.0-5.debian.tar.xz 789adf81c4d4ff8e74dbdc1e1921c8adde6ba8b2cab5142a652c63819aea468e 7929 gnustep-base_1.28.1+really1.28.0-5_source.buildinfo Files: ea29d4ed1eb73b37b598425d54888c2f 3055 gnustep optional gnustep-base_1.28.1+really1.28.0-5.dsc 776cc378b35483d046a8bb4da4b9ea18 4246622 gnustep optional gnustep-base_1.28.1+really1.28.0.orig.tar.gz 8c99d8143ef21272147b1422ebb54c11 232 gnustep optional gnustep-base_1.28.1+really1.28.0.orig.tar.gz.asc 9710a7dda3f6bf92eb15a22098b3f3ed 32888 gnustep optional gnustep-base_1.28.1+really1.28.0-5.debian.tar.xz 77ccca5acee031e426862840b477dfff 7929 gnustep optional gnustep-base_1.28.1+really1.28.0-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmPA+ZQACgkQEWhSvN91 FcCVExAAjh0lod7N92lKvnxuSYDqjwi7vurY/csI0qbAv1AHcwlGbvyIsR722eGX qP0O4qMs8MXgprD8+4qrFJGLeCWep53ObTPRo6vPlIUSq3cps2rTLuyu8lhtzrHH NoEG47T0cGcXj3jI5m7Bbeg8ksD83cqhLSPlvg5czf2Aa6NFWFMwZvvkuOkRNM8V L++OJ0Rgc4ZLEFXW0mw9rb9xsHIsqpxBiWp+JVJMt+BRA/EhGikr602oB+D1pHGc 3t3Hej6bjZkR0HoH0WOYXR7YvwvjJXsVWGfug+SMPD1+oljkM0A8qvB2i3uLb8MP ivcCA7s/bpIQbENV8cieI567DdC1VDrKgVBFooGe0aJTkuKNmve5gL0oEFxJq1ho 8GY00jUcWonkL1iOtIVKJcTPsn2fxQF9Vc6JrQeG5wVf4O8Prvbec4wqwFaCEYij OIs0xf1p0zM//LfCS2Ei//LlYcRMNbUHBgYsVlf3Rs6fEGpdCKpqfCPFBszPG/yt vL3SRbrwo3qY3tEDLQ4R/adVQ721Jr/1Bqepdfw5OcnFNrkmVYgpna4BZZyQKFGp D5ybOvGvZ9rJFM9oKKsA42tX3knktkKxhcNtZe4n3Yydl4OtBl9l/rPPhR1jSTA+ v6a9m6mzp234/ppPRlh8NkngEXPstUOPfwYaRdlft436zZysE4Q= =UGIb -END PGP SIGNATURE End
Processed: Re: emperor: FTBFS/autopkgtest fail with pandas 1.5
Processing control commands: > tags -1 help Bug #1024820 [python3-emperor] emperor: FTBFS/autopkgtest fail with pandas 1.5 Added tag(s) help. -- 1024820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024820: emperor: FTBFS/autopkgtest fail with pandas 1.5
Control: tags -1 help Hi, I just uploaded 1.0.3+ds-6 where the affected test suite error was ignored just to have some installable python3-emperor in unstable and enable building its Depends. However, the problem is not fixed yet (as per Salsa CI which has a fresh build log[1]) and upstream has not responded for months[2]. Thus I'm hoping for help from the Debian Python community. Kind regards Andreas. [1] https://salsa.debian.org/med-team/emperor/-/jobs/3789138 [2] https://github.com/biocore/emperor/issues/810 -- http://fam-tille.de
Bug#895531: Unable to import neuron in python3
Hi Étienne, Am Thu, Jan 12, 2023 at 08:57:33PM +0100 schrieb Étienne Mollier: > Note your upload didn't make it to the archive because for some > reason one of the orig.tar.gz has a discrepancy when trying to > reconstruct it from the VCS, Argh. > so I glued our changes in a version > 7.6.3-4 (to avoid confuse the BTS further and avoid git tag > collision). Hope you're okay with that? Sure I am! I'm always happy if people clean up behind me and watch my steps. ;-) Thanks a lot for your support Andreas. -- http://fam-tille.de
Bug#1027209: marked as done (pyzmq: autopkgtest fail with numpy/1.24.1)
Your message dated Fri, 13 Jan 2023 03:35:40 + with message-id and subject line Bug#1027209: fixed in pyzmq 24.0.1-2 has caused the Debian Bug report #1027209, regarding pyzmq: autopkgtest fail with numpy/1.24.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyzmq Severity: important User: debian-pyt...@lists.debian.org Usertags: numpy1.24 Hello, recently numpy/1.24.1 has been uploaded to experimental, and this package autopkgtest fail when running against it. An overview of the upstream changes in the 1.24.x series is available at: https://numpy.org/doc/stable/release/1.24.0-notes.html Several of the errors are in the form of: AttributeError: module 'numpy' has no attribute 'X' with X in [float, int, bool, object, ...]. This is because, numpy upstream in 1.24.0, finally decided to expire https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases some deprecations introduced in 1.20.0 https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated (released almost 2 years ago). All of those are quite straightforward to fix, since often it's just necessary to stop importing them from numpy and use the python native types. Other changes may requires a bit more rework to be addressed. Currently numpy/1.24.x is in experimental, but given the possible longer support that it'll receive from upstream, we're hopeful to include this in bookworm, so your help is necessary to address this bug ASAP. Regards, Sandro --- End Message --- --- Begin Message --- Source: pyzmq Source-Version: 24.0.1-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of pyzmq, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated pyzmq package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 13 Jan 2023 08:41:54 +0530 Source: pyzmq Architecture: source Version: 24.0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Nilesh Patra Closes: 1018605 1027209 Changes: pyzmq (24.0.1-2) unstable; urgency=medium . [ Gordon Ball ] * Team Upload. * Drop obsolete dependency on python3-nose (Closes: #1018605) . [ Nilesh Patra ] * Bump Standards-Version to 4.6.2 (no changes needed) * Add patch to increase test timeout (Closes: #1027209) * Run autopkgtest for supported pyvers instead of requested Checksums-Sha1: 43d9c1f2746b86afbec1c8526080e01c7da7410c 1722 pyzmq_24.0.1-2.dsc 53efaae333ce06f5423089edc9b7b951b18301dc 10452 pyzmq_24.0.1-2.debian.tar.xz 65e5e9e340575def7f05a7e9523b31bc83b8d06f 8199 pyzmq_24.0.1-2_amd64.buildinfo Checksums-Sha256: 2b156c59b93efb1ebe0f4a847e8b1dc464173e92d51708c3713cd2c721f71dc0 1722 pyzmq_24.0.1-2.dsc 9bd05773e30a310b617f90ac9c89322904125edd941f44dd0fbc6d35ee28cf80 10452 pyzmq_24.0.1-2.debian.tar.xz 4fd675b6e66aa96759a2bd802eaeac2f36f6ef93cadcf561f8a5d4277b66f1a6 8199 pyzmq_24.0.1-2_amd64.buildinfo Files: 86995fbbce7fe477ab882fd084bfeb0b 1722 python optional pyzmq_24.0.1-2.dsc 63e695d77845aefdb5f6eaec349ab747 10452 python optional pyzmq_24.0.1-2.debian.tar.xz 098b1834b0049f0f7a6672db57a3313e 8199 python optional pyzmq_24.0.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCY8DONwAKCRAqJ5BL1yQ+ 2gpkAP0c4VNkC8dAnEixSu7PbTGC4WZITVh5rQ+AQEqB1gtZbwD+OkhqCZgCLCGN 2aE6yFxyb2wvX15/aWEghG+OJD+DpgI= =jKea -END PGP SIGNATURE End Message ---
Processed: Bug#1027209 marked as pending in pyzmq
Processing control commands: > tag -1 pending Bug #1027209 [src:pyzmq] pyzmq: autopkgtest fail with numpy/1.24.1 Added tag(s) pending. -- 1027209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027209: marked as pending in pyzmq
Control: tag -1 pending Hello, Bug #1027209 in pyzmq reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/pyzmq/-/commit/8d2ed46be2a65f2b132e0e71205f7a02f1926d84 Add patch to increase test timeout (Closes: #1027209) (this message was generated automatically) -- Greetings https://bugs.debian.org/1027209
Bug#1028438: closed by Francisco Vilmar Cardoso Ruviaro (Re: Bug#1028438: otpclient: OTP values are all 000000)
Thank you for looking into this. The problem occurs on my original database, as well as in any new database i create. both the new and old databases were created by exporting unencrypted JSONs from Aegis (android). creating a completely new db and adding entries manually also result in 00. i believe the databases are in good working order because they both function properly when used with the flatpak release of otpclient (v3.1.1). thanks again, bk > On 01/12/2023 10:27 PM JST Debian Bug Tracking System > wrote: > > > This is an automatic notification regarding your Bug report > which was filed against the otpclient package: > > #1028438: otpclient: OTP values are all 00 > > It has been closed by Francisco Vilmar Cardoso Ruviaro . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Francisco Vilmar Cardoso > Ruviaro by > replying to this email. > > > -- > 1028438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028438 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > Hi Buster Keaton, > I just upgraded otpclient from 2.6.3-2 to 3.1.1-1 and everything went fine, > this error you reported did not occur*. > > Here is part of my /var/log/apt/history.log: > Commandline: apt install otpclient > Upgrade: otpclient-cli:amd64 (2.6.3-2, 3.1.1-1), otpclient:amd64 (2.6.3-2, > 3.1.1-1) > > > The fact that you have deleted otpclient config (~/.config/otpclient.cfg) > would not solve the problem, what we need to preserve would be the > ~/otpclient.enc file, if you have the backup file of ~/otpclient.enc you > can try to restore and test if the OTP Values are valid. > > > * I close the bug after checking what has been reported, > so far I have not encountered any problems. > > Thanks! > -- > Francisco Vilmar Cardoso Ruviaro > 4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00 > Package: otpclient > Version: 3.1.1-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > the update from 2.6.3-2 to 3.1.1-1 seems to be when the issue was > introduced > >* What exactly did you do (or not do) that was effective (or > ineffective)? > ineffective measures taken: > reboot > uninstall (apt remove --purge otpclient), then reinstall (apt install > otpclient) > created a new database > deleted otpclient config (~/.config/otpclient.cfg) > i no longer have a deb for the previous version, so i am unable to > test that > >* What was the outcome of this action? > 00 is always returned for every entry (about 20 distinct entriest > to choose from) > >* What outcome did you expect instead? > valid OTP codes > > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.1.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) > 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 otpclient depends on: > ii libbaseencode1 1.0.15-1 > ii libc62.36-8 > ii libcotp121.2.7-1 > ii libgcrypt20 1.10.1-3 > ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1 > ii libglib2.0-0 2.74.4-1 > ii libgtk-3-0 3.24.36-1 > ii libjansson4 2.14-2 > ii libpng16-16 1.6.39-2 > ii libprotobuf-c1 1.4.1-1+b1 > ii libqrencode4 4.1.1-1 > ii libsecret-1-00.20.5-3 > ii libuuid1 2.38.1-4 > ii libzbar0 0.23.92-7 > > otpclient recommends no packages. > > Versions of packages otpclient suggests: > pn otpclient-cli > > -- no debconf information
Bug#1021551: bullseye-pu: package voms-api-java_3.3.2-1+deb11u1
bullseye-pu: package voms-api-java_3.3.2-1+deb11u1 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028546 signature.asc Description: This is a digitally signed message part
Bug#1026163: marked as done (Uses Java 11)
Your message dated Thu, 12 Jan 2023 23:11:38 + with message-id and subject line Bug#1026163: fixed in puppetdb 7.12.0-1 has caused the Debian Bug report #1026163, regarding Uses Java 11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: puppetdb Version: 7.11.2-3 Severity: grave Thanks for all the great work on Puppetdb! I was trying to setup a test environment with Puppetdb 7.11.2 from current testing and I noticed that it's using openjdk-11-jre-headless. While openjdk-11 is currently still in testing, Bookworm will only include openjdk-17 (#1023237). Cheers, Moritz --- End Message --- --- Begin Message --- Source: puppetdb Source-Version: 7.12.0-1 Done: Jérôme Charaoui We believe that the bug you reported is fixed in the latest version of puppetdb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérôme Charaoui (supplier of updated puppetdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 12 Jan 2023 10:57:15 -0500 Source: puppetdb Architecture: source Version: 7.12.0-1 Distribution: unstable Urgency: medium Maintainer: Puppet Package Maintainers Changed-By: Jérôme Charaoui Closes: 1026163 Changes: puppetdb (7.12.0-1) unstable; urgency=medium . * New upstream version 7.12.0 * d/control: switch back binary dep to default JRE (Closes: #1026163) * d/control: bump honeysql dependency to v2 * d/patches: refresh patches for new upstream version Checksums-Sha1: ed7a003f041d232d9ff5e15d0db073271cded04c 3365 puppetdb_7.12.0-1.dsc c69eac457eeaa659ae98acc1808a4d4546af3149 1193024 puppetdb_7.12.0.orig.tar.xz e49d260f433a5025c4dda488f94da9f83ef67838 19200 puppetdb_7.12.0-1.debian.tar.xz 91ba91cce16bb7191d32625effe33debbcbcb822 16283 puppetdb_7.12.0-1_amd64.buildinfo Checksums-Sha256: 3a7c7b9a5b9907d510982b6740621429511138e21f9fcbefc7837822d8a8ede6 3365 puppetdb_7.12.0-1.dsc 52221f8d6ce38150c4ef73c3873fcbd1f9cd8729a1fea76943db8e1729cf4e46 1193024 puppetdb_7.12.0.orig.tar.xz 1c41736f8a60a721752d703dbd0ccb4770f55d397f0710a276acf1318ce4b937 19200 puppetdb_7.12.0-1.debian.tar.xz 45c016f3db832eb94499d538ff2e36d17c8c3632b3418f249b2c2d20237adc7c 16283 puppetdb_7.12.0-1_amd64.buildinfo Files: d66cf1c1e87b2245a2396a0714f03ba3 3365 admin optional puppetdb_7.12.0-1.dsc 350b863de8b37896b3b07299d63d8121 1193024 admin optional puppetdb_7.12.0.orig.tar.xz fcedf0444dfd9ffc0b14e608bd7fa581 19200 admin optional puppetdb_7.12.0-1.debian.tar.xz 3c79e2a34dce105c8fac35f1e8a49ebf 16283 admin optional puppetdb_7.12.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQTAq04Rv2xblqv/eu5pxS9ljpiFQgUCY8CNMAAKCRBpxS9ljpiF QhMGAQD18aXWEyBxa9QYSU3QZvyWmM3Q0Y7TNIxBqm8q8NUI5gEA242zFPQooinG 6XPZjBH0t/YBCeJgX5RM696nXjBhzws= =BIen -END PGP SIGNATURE End Message ---
Bug#1027939: clang-14 lost its (indirect) dependency on libclang-rt-14-dev
Dear Maintainer, Please find a merge request hyperlinked below that is intended to address the build failure described in this bug: https://salsa.debian.org/pkg-llvm-team/halide/-/merge_requests/2 Thank you, James
Bug#1028187: marked as done (libcommons-validator-java: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:aggregate (default-cli))
Your message dated Thu, 12 Jan 2023 22:54:36 + with message-id and subject line Bug#1028187: fixed in libcommons-validator-java 1:1.6-3 has caused the Debian Bug report #1028187, regarding libcommons-validator-java: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:aggregate (default-cli) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1028187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcommons-validator-java Version: 1:1.6-2 Severity: normal Tags: ftbfs X-Debbugs-Cc: debian-j...@lists.debian.org Dear Maintainer, I downloaded the source through 'apt source libcommons-validator-java'. When I try to package it with sbuild,it complains,and stopped building. The build log says: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:aggregate (default-cli) on project commons-validator: Execution default-cli of goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:aggregate failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:aggregate: java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.siterenderer.sink.SiteRendererSink.(org.apache.maven.doxia.sink.render.RenderingContext)' [ERROR] - [ERROR] realm =plugin>org.apache.maven.plugins:maven-javadoc-plugin:3.0.1 [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy [ERROR] urls[0] = file:/<>/debian/maven-repo/org/apache/maven/plugins/maven-javadoc-plugin/3.0.1/maven-javadoc-plugin-3.0.1.jar [ERROR] urls[1] = file:/<>/debian/maven-repo/org/codehaus/plexus/plexus-sec-dispatcher/debian/plexus-sec-dispatcher-debian.jar [ERROR] urls[2] = file:/<>/debian/maven-repo/org/codehaus/plexus/plexus-cipher/debian/plexus-cipher-debian.jar [ERROR] urls[3] = file:/<>/debian/maven-repo/org/apache/maven/maven-builder-support/3.x/maven-builder-support-3.x.jar [ERROR] urls[4] = file:/<>/debian/maven-repo/org/apache/maven/resolver/maven-resolver-util/debian/maven-resolver-util-debian.jar [ERROR] urls[5] = file:/<>/debian/maven-repo/org/apache/maven/shared/maven-shared-utils/debian/maven-shared-utils-debian.jar [ERROR] urls[6] = file:/<>/debian/maven-repo/org/eclipse/sisu/org.eclipse.sisu.inject/debian/org.eclipse.sisu.inject-debian.jar [ERROR] urls[7] = file:/<>/debian/maven-repo/javax/enterprise/cdi-api/debian/cdi-api-debian.jar [ERROR] urls[8] = file:/<>/debian/maven-repo/org/apache/geronimo/specs/geronimo-interceptor_3.0_spec/debian/geronimo-interceptor_3.0_spec-debian.jar [ERROR] urls[9] = file:/<>/debian/maven-repo/com/google/inject/guice/debian/guice-debian-no_aop.jar [ERROR] urls[10] = file:/<>/debian/maven-repo/aopalliance/aopalliance/debian/aopalliance-debian.jar [ERROR] urls[11] = file:/<>/debian/maven-repo/com/google/guava/guava/debian/guava-debian.jar [ERROR] urls[12] = file:/<>/debian/maven-repo/org/jsr-305/jsr305/0.x/jsr305-0.x.jar [ERROR] urls[13] = file:/<>/debian/maven-repo/com/google/errorprone/error_prone_annotations/debian/error_prone_annotations-debian.jar [ERROR] urls[14] = file:/<>/debian/maven-repo/org/codehaus/plexus/plexus-interpolation/debian/plexus-interpolation-debian.jar [ERROR] urls[15] = file:/<>/debian/maven-repo/org/codehaus/plexus/plexus-component-annotations/debian/plexus-component-annotations-debian.jar [ERROR] urls[16] = file:/<>/debian/maven-repo/org/apache/maven/reporting/maven-reporting-api/3.x/maven-reporting-api-3.x.jar [ERROR] urls[17] = file:/<>/debian/maven-repo/org/apache/maven/maven-archiver/debian/maven-archiver-debian.jar [ERROR] urls[18] = file:/<>/debian/maven-repo/org/codehaus/plexus/plexus-io/debian/plexus-io-debian.jar [ERROR] urls[19] = file:/<>/debian/maven-repo/org/apache/maven/shared/maven-invoker/debian/maven-invoker-debian.jar [ERROR] urls[20] = file:/<>/debian/maven-repo/org/apache/maven/shared/maven-common-artifact-filters/debian/maven-common-artifact-filters-debian.jar [ERROR] urls[21] = file:/<>/debian/maven-repo/org/apache/maven/shared/maven-artifact-transfer/debian/maven-artifact-transfer-debian.jar [ERROR] urls[22] = file:/<>/debian/maven-repo/org/apache/maven/doxia/doxia-sink-api/debian/doxia-sink-api-debian.jar [ERROR] urls[23] = file:/<>/debian/maven-repo/org/apache/maven/doxia/doxia-logging-api/debian/doxia-logging-api-debian.jar [ERROR] urls[24] = file:/<>/debian/maven-repo/org/apache/maven/doxia/doxia-site-renderer/debian/doxia-site-renderer-debian.jar [ERROR] urls[25] =
Processed: pandas 1.5 now in unstable
Processing control commands: > severity 1025393 serious Bug #1025393 [python3-dask] dask: autopkgtest fail with pandas 1.5 Severity set to 'serious' from 'normal' > severity 1024820 serious Bug #1024820 [python3-emperor] emperor: FTBFS/autopkgtest fail with pandas 1.5 Severity set to 'serious' from 'normal' -- 1022571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022571 1024820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024820 1025393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027690: marked as done (lmms: Segfault on startup with kwidgetsaddons 5.101.0)
Your message dated Thu, 12 Jan 2023 22:26:21 + with message-id and subject line Bug#1027690: fixed in lmms 1.2.2+dfsg1-5 has caused the Debian Bug report #1027690, regarding lmms: Segfault on startup with kwidgetsaddons 5.101.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lmms Version: 1.2.2+dfsg1-4+b3 Severity: grave Tags: patch upstream Justification: renders package unusable Forwarded: https://github.com/LMMS/lmms/issues/6587 Dear Maintainer, LMMS experiences a segmentation fault on startup. According to an upstream bug report [1], this appears to be due to a specific workaround for an old bug in KXMLGUI [2], which breaks with kwidgetsaddons 5.101.0. As the comments on the upstream bug report suggest, a workaround is to downgrade kwidgetsaddons to 5.100.0. I can confirm that downgrading the libkf5widgetsaddons5 and libkf5widgetsaddons-data packages works on my system. The fix for this segmentation fault is to remove the workaround [3], as the KXMLGUI bug has been fixed for some time (since version 5.55.0). Philip Chung [1] https://github.com/LMMS/lmms/issues/6587 [2] https://bugs.kde.org/show_bug.cgi?id=337491 [3] See this fix in another distribution: https://github.com/void-linux/void-packages/pull/41313 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 lmms depends on: ii libasound21.2.8-1 ii libc6 2.36-7 ii libfftw3-single3 3.3.10-1 ii libfltk1.31.3.8-5 ii libfluidsynth32.3.0-1+b1 ii libgcc-s1 12.2.0-11 ii libgig10 4.3.0~ds1-2+b1 ii libmp3lame0 3.100-6 ii libogg0 1.3.5-3 ii libportaudio2 19.6.0-1.2 ii libpulse0 16.1+dfsg1-2+b1 ii libqt5core5a 5.15.7+dfsg-2 ii libqt5gui55.15.7+dfsg-2 ii libqt5widgets55.15.7+dfsg-2 ii libqt5xml55.15.7+dfsg-2 ii libsamplerate00.2.2-3 ii libsdl1.2debian 1.2.15+dfsg2-8 ii libsndfile1 1.1.0-3+b1 ii libsndio7.0 1.9.0-0.3+b1 ii libsoundio2 2.0.0-2 ii libstdc++612.2.0-11 ii libstk-4.6.2 4.6.2+dfsg-2 ii libvorbis0a 1.3.7-1 ii libvorbisenc2 1.3.7-1 ii libvorbisfile31.3.7-1 ii lmms-common 1.2.2+dfsg1-4 ii stk 4.6.2+dfsg-2 ii zlib1g1:1.2.13.dfsg-1 Versions of packages lmms recommends: ii caps 0.9.26-1 pn lmms-vst-server ii tap-plugins 1.0.0-1 Versions of packages lmms suggests: ii caps [ladspa-plugin] 0.9.26-1 pn fil-plugins pn fluid-soundfont-gm pn freepats pn mcp-plugins pn omins ii tap-plugins [ladspa-plugin] 1.0.0-1 -- no debconf information --- End Message --- --- Begin Message --- Source: lmms Source-Version: 1.2.2+dfsg1-5 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of lmms, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated lmms package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Jan 2023 16:37:37 -0500 Source: lmms Architecture: source Version: 1.2.2+dfsg1-5 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Boyuan Yang Closes: 1025804 1027690 Changes: lmms (1.2.2+dfsg1-5) unstable; urgency=medium . * Team upload. * debian/rules: Re-enable i386 wine support. (Closes: #1025804) + Also fix for debian/lmms-vst-server.install. * debian/patches/fix-qt-crash-kwidgetsaddons-5.101.0.patch: Add patch to fix
Bug#1028359: marked as done (pygpu: fails to import in numpy 1.24)
Your message dated Thu, 12 Jan 2023 22:21:57 +
with message-id
and subject line Bug#1028359: fixed in libgpuarray 0.7.6-13
has caused the Debian Bug report #1028359,
regarding pygpu: fails to import in numpy 1.24
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1028359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pygpu
Version: 0.7.6-12
Severity: grave
numpy 1.24 no longer has np.bool, which makes pygpu fail to import:
pygpu/dtypes.py:74: in _fill_dtype_registry
register_dtype(np.bool, ["ga_bool", "bool"])
numpy/__init__.py:284: in __getattr__
raise AttributeError("module {!r} has no attribute "
E AttributeError: module 'numpy' has no attribute 'bool'
Full log: https://salsa.debian.org/science-team/theano/-/jobs/3771271
--- End Message ---
--- Begin Message ---
Source: libgpuarray
Source-Version: 0.7.6-13
Done: Rebecca N. Palmer
We believe that the bug you reported is fixed in the latest version of
libgpuarray, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rebecca N. Palmer (supplier of updated libgpuarray
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 11 Jan 2023 21:19:30 +
Source: libgpuarray
Architecture: source
Version: 0.7.6-13
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Rebecca N. Palmer
Closes: 1028359
Changes:
libgpuarray (0.7.6-13) unstable; urgency=medium
.
* Don't use np.bool, as it no longer exists. (Closes: #1028359)
Checksums-Sha1:
651f08b50f3d40f319859ebba4d075068ab26537 2689 libgpuarray_0.7.6-13.dsc
14ba61c162d581e09d438541323d7ef265af20b0 21172
libgpuarray_0.7.6-13.debian.tar.xz
e717a6de7cc3e9b75a4fa27f05b8f8950aa54747 5791
libgpuarray_0.7.6-13_source.buildinfo
Checksums-Sha256:
769c593c947b739fc0cd31d8774f70030e57d2bd9bb4af40266c762cf6ce2938 2689
libgpuarray_0.7.6-13.dsc
30e10133a7fe6c977f23bd7668aa231c10b0fce198b138da55cd7e40969fcbd1 21172
libgpuarray_0.7.6-13.debian.tar.xz
f15e66b6d39351e02bd1c551f5d575aa74f1bc09b9616787ae26b66ed7d83c06 5791
libgpuarray_0.7.6-13_source.buildinfo
Files:
6b83a48e2074ed849ac114b108c7cafc 2689 libs optional libgpuarray_0.7.6-13.dsc
d5104e5607ee1bc2f2cb44ee5876cfb1 21172 libs optional
libgpuarray_0.7.6-13.debian.tar.xz
c59bd18ed3bdc3e751addeb55d23fbf3 5791 libs optional
libgpuarray_0.7.6-13_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJMBAEBCgA2FiEEZ8sxEAXE7b4yF1MI3uUNDVZ+omYFAmPAgUcYHHJlYmVjY2Ff
cGFsbWVyQHpvaG8uY29tAAoJEN7lDQ1WfqJmSkkQAMFs8xC+WfroEjUSPT71jR1h
oQqs9LEZsSVmnw+pdD1Jmvt4VRdPEDnvcnQP9g9OAKB+KHe6az0jee4r6Iy4UiK6
5U6t5HQo6S56G7vQPCYzML7yn3TuT9ijTVKDlGddyHNmdV2Q8mOBxO+5tKdul9U/
6YwM5OG2EAwvj+LHsoX+h36kLmMBTd0TBUpzz8q3vDu76PQziuRZwgIr6EkU0ZA9
S3i9B5SYkOllrGh3VEPBg2nqRvzIaIlNuLfm3Dqxfuqf/xyQ/+MDfwKrBDx5EdUC
m8+lMNTm+9nmoNWXLS0uStca0iJOtHl46X7XXfzR9nbaj7j5aRnLSsNeioRw0bj6
ML5K87gEAMnDyeScB0ZWM4dlfzj6jTsS/pblIkLhY5nibYtF7x2Mbo9Mv3aKzvsD
+QORoiWYA9T2NDEW9XoSJcRk1MV6D0lOtF4Jz8bBSz5kINlobuwJwGE38tsbzWpO
ki84LCsj+zwIGP3M38z9dGuMlnVLorJza3/Gdbrtij67L1uW9A6Z6qwdm+QWX/6A
GPlXCHqjGZt9EEZz8umVV/hp0Dr4dTSukmSvxbxDRq3nRXdgCqIgHIogGDVXUryE
JmXjzYURxJhUEicl3ZQR9ufZNhPFca/fCYY7q4ssdOX10qzTcrFVYEDz2TwnWmka
xNdxKGU0PhVd8znLTgEh
=3/+J
-END PGP SIGNATURE End Message ---
Bug#1028567: acetoneiso: should not download and run random binaries off the internet
Package: acetoneiso
Version: 2.4-3
Severity: serious
Tags: security
While looking through the code to see about replacing youtube-dl
(#1024231), I noticed the following in acetoneiso/sources/utube.h's
metacafe() function:
if (system ("cd $HOME/.acetoneiso/;wget
> /dev/null
2>&1")) {
yutubbodl.setPermissions(QFile::ReadOwner | QFile::WriteOwner |
QFile::ExeOwner | QFile::ExeGroup | QFile::ReadGroup | QFile::ReadOther
| QFile::ExeOther);
[...]
QFile utube_file( acetone_bin.path() + "/metacafe-dl");
[...]
UTube->start( utube_file.fileName(), QStringList() << "-o" <<
file << text );
Perhaps I'm wrong, but this appears to download and run whatever
is. That web
server no longer appears to be reachable, but that could be anything
and is not guaranteed to be DFSG-compliant and could even do something
malicious - we don't know.
That should probably be patched out of the program.
Processed: severity of 1028368 is serious
Processing commands for cont...@bugs.debian.org: > severity 1028368 serious Bug #1028368 [dahdi-dkms] dahdi-dkms fails to install after arrival of 6.1.0-1 kernel Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1028368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028375: marked as done (Provide proper package relationship with manpages-xx)
Your message dated Thu, 12 Jan 2023 21:09:12 +
with message-id
and subject line Bug#1028375: fixed in xz-utils 5.4.1-0.0
has caused the Debian Bug report #1028375,
regarding Provide proper package relationship with manpages-xx
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1028375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xz-utils
Version: 5.4.0-0.1
Dear developer,
I'm not sure if it's the right place to report the bug since it involves
a conflict with a backport.
Today I tried to upgrade a Bullseye laptop to Bookworm.
The upgrade crashed with xz-utils trying to overwrite
/usr/share/man/fr/man1/xz.1.gz which belonged to manpages-fr from
backports (4.16.0-3~bpo11+1).
After running dpkg --force-overwrite (it's the only way I know of in
such situations), a whole bunch of manual pages were overwritten :
/usr/share/man/fr/man1/xz.1.gz
/usr/share/man/fr/man1/xzdiff.1.gz
/usr/share/man/fr/man1/xzless.1.gz
/usr/share/man/fr/man1/xzmore.1.gz
/usr/share/man/fr/man1/lzcat.1.gz
/usr/share/man/fr/man1/lzcmp.1.gz
/usr/share/man/fr/man1/lzdiff.1.gz
/usr/share/man/fr/man1/lzless.1.gz
/usr/share/man/fr/man1/lzma.1.gz
/usr/share/man/fr/man1/lzmore.1.gz
/usr/share/man/fr/man1/unlzma.1.gz
/usr/share/man/fr/man1/unxz.1.gz
/usr/share/man/fr/man1/xzcat.1.gz
/usr/share/man/fr/man1/xzcmp.1.gz
I don't see a clean solution to ensure a smooth upgrade for people who
have installed this backport. Maybe coordinate with manpages-fr
maintainer and release updated backports for both packages, before
Bookworm is released ?
Regards,
--
Raphaël Halimi
--- End Message ---
--- Begin Message ---
Source: xz-utils
Source-Version: 5.4.1-0.0
Done: Sebastian Andrzej Siewior
We believe that the bug you reported is fixed in the latest version of
xz-utils, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior (supplier of updated
xz-utils package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 11 Jan 2023 23:00:00 +0100
Source: xz-utils
Architecture: source
Version: 5.4.1-0.0
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Nieder
Changed-By: Sebastian Andrzej Siewior
Closes: 1028375
Changes:
xz-utils (5.4.1-0.0) unstable; urgency=medium
.
* Non-maintainer upload.
* Import 5.4.1.
* Provide proper package relationship with manpages-{de|fr}
(Closes: #1028375).
Checksums-Sha1:
2a57bf9c5f1f6bf13e6d13b2cdfaf3b52eeb9ae8 2517 xz-utils_5.4.1-0.0.dsc
8facb914772e5963d86f9cdd781c928009879b3b 1485272 xz-utils_5.4.1.orig.tar.xz
7c8305fda4dbb47a962858e3e3496da0af715c4b 833 xz-utils_5.4.1.orig.tar.xz.asc
c87f1874f59730069e393e0031eb94756db740f8 24076 xz-utils_5.4.1-0.0.debian.tar.xz
Checksums-Sha256:
f49fcdedd79128916473d79182f8cafbdeabfc28e1f1be0d789afc835ba61d34 2517
xz-utils_5.4.1-0.0.dsc
5d9827aa1875b21c288f78864bb26d2650b436ea8d2cad364e4921eb6266a5a5 1485272
xz-utils_5.4.1.orig.tar.xz
4b0c7707114996092a5f75a98333de2102db83a27218e4903b8fb7c24a8d0233 833
xz-utils_5.4.1.orig.tar.xz.asc
f898d2ffa4942158e4861a9428f6c00bbf7beeb4236edffa5a9d5032b42b73ec 24076
xz-utils_5.4.1-0.0.debian.tar.xz
Files:
e035ec3317d62bcd9054ddd705074cdd 2517 utils optional xz-utils_5.4.1-0.0.dsc
47d831c659e94071d5dd384d0d1ed4c6 1485272 utils optional
xz-utils_5.4.1.orig.tar.xz
6bc67b7cf68811620ef641ed53ecea3f 833 utils optional
xz-utils_5.4.1.orig.tar.xz.asc
b8c842a976572466404c3cbb52ec2a78 24076 utils optional
xz-utils_5.4.1-0.0.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEZCVGlf/wqkRmzBnme5boFiqM9dEFAmPAdAcACgkQe5boFiqM
9dEsyRAAuROZEemHTWlUK/U84g3cXbUfr9hEvo0nuy0AIlGzmvmnGOi+URXGz0tF
i9DRAcoB1sVjSTkL9dhWwgkaDSleNr/mcEV9tdQVdUIGiedgJsWeko1lvy7H4qns
Hmdk1ZEogR3IcsHwjsj3/SdYbTOXkvZ8HXskvHutqKFOl+XzNcLNwGVzbgyMvb+r
F29r/kHpOFZ+Wfc8+Uq0yDtHwvS08zPYdn3LCEB0h7kAsySHSx+ADmEmPAa22OSh
Y0JXKwbUFxKPUElMR0Dy9DIV2si+hY+o5wwDk7RdaDNHGCOiivKYVu7XUgW87eIC
Bl0c8eXOVIM6gt8etLJM1gjxXUeID2KCdDqouaIS/WX68JW9eoblQ45vIlq6IXUG
Bug#895531: marked as done (Unable to import neuron in python3)
Your message dated Thu, 12 Jan 2023 21:06:46 + with message-id and subject line Bug#895531: fixed in neuron 7.6.3-4 has caused the Debian Bug report #895531, regarding Unable to import neuron in python3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 895531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: python3-neuron 7.5-1 Unable to import neuron from python 3. See example below:? $ python3 Python 3.6.5rc1 (default, Mar 14 2018, 06:54:23) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import neuron Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/neuron/__init__.py", line 114, in import nrn ModuleNotFoundError: No module named 'nrn' >>> I am running Debian/testing. Linux terpsichore 4.15.0-2-amd64 #1 SMP Debian 4.15.11-1 (2018-03-20) x86_64 GNU/Linux --- End Message --- --- Begin Message --- Source: neuron Source-Version: 7.6.3-4 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of neuron, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 895...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated neuron package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Jan 2023 21:07:14 +0100 Source: neuron Architecture: source Version: 7.6.3-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Étienne Mollier Closes: 895531 Changes: neuron (7.6.3-4) unstable; urgency=medium . * Team upload. . [ Andreas Tille ] * Testsuite: autopkgtest-pkg-python * Bump debhelper from old 11 to 13 (lintian-brush) * Add salsa-ci.yml * Lintian-overrides for library-not-linked-against-libc . [ Étienne Mollier ] * d/control: python3-neuron depends on python3-pkg-resources. * d/rules: fix neuron and hoc modules location. (Closes: #895531) * d/python3-neuron.lintian-overrides: refresh after moving hoc. * d/control: target python3.11 for autopkgtest. Checksums-Sha1: 2b44d13c46038f3a5e864e030ca3f0fe75584e4a 2504 neuron_7.6.3-4.dsc 183094e5377540b21b535ee702edee57a2ea274a 13664 neuron_7.6.3-4.debian.tar.xz 3c0b5b4cb102a24401acb54e5a7ef6a9ff43ed58 10388 neuron_7.6.3-4_amd64.buildinfo Checksums-Sha256: 17fa3becba997519b5545869fe937d1914241666c0665c2ef77fb654fbd4b8b4 2504 neuron_7.6.3-4.dsc c9168ff625e10ff9d5abb2b4a6f994573b47d6586f5bc75baf499e97a16f5033 13664 neuron_7.6.3-4.debian.tar.xz 2304ada7ebcc9118547f4381dcafa21433855803c28ec4c60ba8729db8d336ff 10388 neuron_7.6.3-4_amd64.buildinfo Files: e1bac95872db792765c860dcbfe1d3ef 2504 science optional neuron_7.6.3-4.dsc ce6e515e3c815d458097eb5d198e61be 13664 science optional neuron_7.6.3-4.debian.tar.xz d4a16f814a57742ca80f94a86439505b 10388 science optional neuron_7.6.3-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmPAbwQUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqlvxAAw/HHweBlOlD4hu1G4nHDzTTZ9RgO U97bUVAMlfzm0wsyPB/DfMZGEKIHEBzpCm/vMUG4KRaHQwRcJCuHh3JPb8+SRuPa IXvkHf9/2/107/q+YogSrhyoSzJdoBjKzypAIgvP+bLbFqm8RqA5NEuVHcTciBxZ pP7zA8AusEUeKpTr8L3nJVf8TgY80FnD3+JTBTsTInlZwytqzpD6A2+3G2ao4rk9 TabFjLMk0ssbm4Ke750BTCbQ5qyq3/Hqaaggd2stmpHQDV/FPX9BKwli98XSD5GR wtetg6c6fKarTf0PxUckqWcUNtukP3zBFOiHCL1KtWBeN1lXGfe+gCJDeA3KQAr6 8tPwrAq3X1Fy7flk9Jj2z2HkR6mUZWBVNzPp7KZqeJCWzrCDA9fn/CpCU2JCQUat t2VsdVNGccWO+PRqNV7AOtWixKWNRu6pQggq4bVO87k1JACoXqMUdFf8rEn0Zo5f VNrfMASvvFkexlky7A79uQesVw8O125GGfi9E7Ey0oyDJuPfeGlimZiQck30fEBF hnwFSLjMsgUV0fhrrQAysUGlALialm319f2auJrMFlW63Ft2vL5FAQLPvNXC5FmU O+3UchiHIwteubn5tXMV4VTKToJfOVh1VDEBLmeiduGSB5qdnpgRcGFmjKvIZ7je xfJwrJmzkkZ7Ssg= =ViMI -END PGP SIGNATURE End Message ---
Bug#1028022: marked as done (libclamunrar9: Not buildable/installable with clamav 1.0/libclamav11)
Your message dated Thu, 12 Jan 2023 21:05:54 + with message-id and subject line Bug#1028022: fixed in libclamunrar 1.0.0-2 has caused the Debian Bug report #1028022, regarding libclamunrar9: Not buildable/installable with clamav 1.0/libclamav11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1028022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libclamunrar9 Version: 0.102.3-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) It will take some time to update libclamunrar to provide libclamunrar11. This should not block the clamav transition, so libclamunrar will probably need to be (at least temporarily) removed from Testing. This bug is to make sure it doesn't prematurely migrate back. Scott K --- End Message --- --- Begin Message --- Source: libclamunrar Source-Version: 1.0.0-2 Done: Sebastian Andrzej Siewior We believe that the bug you reported is fixed in the latest version of libclamunrar, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Andrzej Siewior (supplier of updated libclamunrar package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Jan 2023 21:05:44 +0100 Source: libclamunrar Architecture: source Version: 1.0.0-2 Distribution: unstable Urgency: medium Maintainer: ClamAV Team Changed-By: Sebastian Andrzej Siewior Closes: 1028022 Changes: libclamunrar (1.0.0-2) unstable; urgency=medium . * Upload to unstable * Provide the matching library for libclamav11 (Closes: #1028022). Checksums-Sha1: 423e4416e9a9aa7848f283dd61926ec249df5e3d 2477 libclamunrar_1.0.0-2.dsc ad59de9f79ac51066c06de63168469bada039c24 23456 libclamunrar_1.0.0-2.debian.tar.xz Checksums-Sha256: 59371e21de3b79fe0a222907a743f0e351e9187c2ce90c3d9d8e0771b6034a73 2477 libclamunrar_1.0.0-2.dsc 7d57c4f662d1853bc4bd9fea7453421319dfa06ade92bd6baf5af0fac401cdda 23456 libclamunrar_1.0.0-2.debian.tar.xz Files: a2ef4839440420e247c6967eae54a762 2477 non-free/libs optional libclamunrar_1.0.0-2.dsc 37e4540511d5993a3e2aba2d5147172b 23456 non-free/libs optional libclamunrar_1.0.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZCVGlf/wqkRmzBnme5boFiqM9dEFAmPAc1MACgkQe5boFiqM 9dHh6hAAvdIzcvmeoLIECdvfymLeFtH9d+Nw1dtv8Wq/bVXt9lAs8IzftQdmpj24 vhQ22vxcVi9qwo0p+yximafi/IEOkfSnc20h+BoLiM0Syu+/96jyGNpFGSZ9XCml 0Dlnw2ZHzNFhnT3UfQLv6SMjeNU/C70upsA/Fh9yh9x+4xoi644IeuCi/Kg17rL5 d8MLGUGffZehfXRsIUwr1fnCQoFq3F+8Nhhc8i1RDPNrKwKbp6c6ST/tECp+PqoO cM21gQpRIVhFvQ4qD+3nPTIz21nEPfxeLLs2ZfGTZZJ/rDPXMf22Nfrl3KbSue52 PgaCXwt9bMciY+4zwH9Fj4Pc5NBA5VEYtViThjwvaojYn4dRvoN75ekQmqFiLaJJ 2okuThYh5NFte73tT2tvz3THooYXAE9/49U9mL/zIVXOYW3PcMNXQ74k1VetFccT UuutnJ7DorsRnJ5GbxinvuZs8+sxtJFJJ5d6YQbYvESugJOblIzzGhsxmMWG/5j5 gIhyjSzfv1T6JQQ4bosHwdJgdZiU8PZdiIkoK2Ru/oeCAjSvGPwsX7jzVofkn4Fw rJM0Um9ZR0b5v9zFz0glmOBCX2KXCJVlU54rUO+6+19z+NM/ymTtoEu0ek0c6Da4 gsuqXm691kT7+h7yVmN76FpFLBQvjmxJP/xDHjD2uIFapqqAbKk= =D/dn -END PGP SIGNATURE End Message ---
Bug#1027201: marked as done (indexed-gzip: autopkgtest fail with numpy/1.24.1)
Your message dated Thu, 12 Jan 2023 21:05:08 + with message-id and subject line Bug#1027201: fixed in indexed-gzip 1.7.0-1 has caused the Debian Bug report #1027201, regarding indexed-gzip: autopkgtest fail with numpy/1.24.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: indexed-gzip Severity: important User: debian-pyt...@lists.debian.org Usertags: numpy1.24 Hello, recently numpy/1.24.1 has been uploaded to experimental, and this package autopkgtest fail when running against it. An overview of the upstream changes in the 1.24.x series is available at: https://numpy.org/doc/stable/release/1.24.0-notes.html Several of the errors are in the form of: AttributeError: module 'numpy' has no attribute 'X' with X in [float, int, bool, object, ...]. This is because, numpy upstream in 1.24.0, finally decided to expire https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases some deprecations introduced in 1.20.0 https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated (released almost 2 years ago). All of those are quite straightforward to fix, since often it's just necessary to stop importing them from numpy and use the python native types. Other changes may requires a bit more rework to be addressed. Currently numpy/1.24.x is in experimental, but given the possible longer support that it'll receive from upstream, we're hopeful to include this in bookworm, so your help is necessary to address this bug ASAP. Regards, Sandro --- End Message --- --- Begin Message --- Source: indexed-gzip Source-Version: 1.7.0-1 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of indexed-gzip, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated indexed-gzip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 13 Jan 2023 01:01:31 +0530 Source: indexed-gzip Architecture: source Version: 1.7.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Nilesh Patra Closes: 1019469 1027201 Changes: indexed-gzip (1.7.0-1) unstable; urgency=medium . * Team Upload. * New upstream version 1.7.0 * Bump Standards-Version to 4.6.2 (no changes needed) * Add patch to fix FTBFS with new numpy (Closes: #1027201) * Remove patches to skip nocov, no longer valid * Apply riscv64 patch from Eric Long (Closes: #1019469) Checksums-Sha1: 865e3f5fb1d63f13675ce5056ab28015243a5de7 1585 indexed-gzip_1.7.0-1.dsc 1a6b8f11cdf67e8783859ea469240029c0d576b7 103849 indexed-gzip_1.7.0.orig.tar.gz 6fc0b2343c36f69db0a62d20a61ccaf916039608 5732 indexed-gzip_1.7.0-1.debian.tar.xz 6460f1ce5a76ef04fdd6358dbf533a633279b93f 7726 indexed-gzip_1.7.0-1_amd64.buildinfo Checksums-Sha256: 69e99740cf63363c9a17cb3549796f4e5942cd3042f3bbe599a2aa9e6600b67f 1585 indexed-gzip_1.7.0-1.dsc dbe9f4040c46574c894cb4a96a0fffce82ff672caec78753d76d906189ade4d5 103849 indexed-gzip_1.7.0.orig.tar.gz dcfbc25780e970aab84c4693f8c21fddd1ccc5084c26759b0ec355510ac0afb1 5732 indexed-gzip_1.7.0-1.debian.tar.xz dc419ffacd8313b947acd642b6c35ecb98e983c290b182995f7cefc5ddeaf3e8 7726 indexed-gzip_1.7.0-1_amd64.buildinfo Files: e4db75023ac3bdfbae082757c2ab00f0 1585 python optional indexed-gzip_1.7.0-1.dsc 274aa14b238653c0de66dc3216b494b8 103849 python optional indexed-gzip_1.7.0.orig.tar.gz 2d420f5ab9acc1358a1e001b6a2fa6e1 5732 python optional indexed-gzip_1.7.0-1.debian.tar.xz f421aa58322db8b24f456a977c91b82f 7726 python optional indexed-gzip_1.7.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCY8BwvwAKCRAqJ5BL1yQ+ 2tq2AP9ipqYEtSz+tJ4CqnsqwFj6yBC0szygs8dA/VqGDq5d8wD9E+HG4VtbUs+t /bLB8166MghyJkjQsxHnpgboB/BcdQs= =sbTX -END PGP SIGNATURE End Message ---
Processed: severity of 1028187 is serious
Processing commands for cont...@bugs.debian.org: > severity 1028187 serious Bug #1028187 [libcommons-validator-java] libcommons-validator-java: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:aggregate (default-cli) Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1028187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1026097
Processing commands for cont...@bugs.debian.org: > tags 1026097 + pending Bug #1026097 [lua-curl] lua-curl: there are no OPT_* constants in the module Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014957: marked as done (dogtag-pki: CVE-2022-2414)
Your message dated Thu, 12 Jan 2023 19:35:20 + with message-id and subject line Bug#1014957: fixed in dogtag-pki 11.0.6-1 has caused the Debian Bug report #1014957, regarding dogtag-pki: CVE-2022-2414 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1014957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dogtag-pki X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for dogtag-pki. CVE-2022-2414[0]: https://bugzilla.redhat.com/show_bug.cgi?id=2104676 https://github.com/dogtagpki/pki/pull/4021 https://github.com/dogtagpki/pki/commit/4e893243d72ad766558c10c907841f5f9c047055 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-2414 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2414 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: dogtag-pki Source-Version: 11.0.6-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of dogtag-pki, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated dogtag-pki package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Jan 2023 20:49:28 +0200 Source: dogtag-pki Built-For-Profiles: noudeb Architecture: source Version: 11.0.6-1 Distribution: unstable Urgency: medium Maintainer: Debian FreeIPA Team Changed-By: Timo Aaltonen Closes: 1014957 1024462 Changes: dogtag-pki (11.0.6-1) unstable; urgency=medium . * New upstream release. - CVE-2022-2414 (Closes: #1014957) * control: Fix pki-base-java to depend on default-jre-headless instead of a versioned one, it shouldn't be necessary to hardcode it anymore. (Closes: #1024462) * control: Bump dependency on jss, ldapjdk, tomcatjss. * dont-use-deprecated-python-ldap-options.diff: Drop constants removed in python-ldap 3.4. * rules: Bump JAVA_HOME to match java 17. Checksums-Sha1: f9c6c7ef6abc020664ef967a2609ef07c3712ea7 3786 dogtag-pki_11.0.6-1.dsc 1d5acd7acceb2fc8e6655e2b31d386c749444f6a 6846728 dogtag-pki_11.0.6.orig.tar.xz 88b10c46aa4b02c2ad172dea1ff6c9dcc6c469b9 43464 dogtag-pki_11.0.6-1.debian.tar.xz cac1ce2a08b8b8d11cf8c4a662a420dd99531763 16054 dogtag-pki_11.0.6-1_source.buildinfo Checksums-Sha256: a0de1237c7f74431209cdbffb5f90d5cb21353e51c8f72d3f705c636af35f1c5 3786 dogtag-pki_11.0.6-1.dsc d1dad801fcd20d91a2914af55fcdd9e6665ff679812ad0bf76109dca9588da7d 6846728 dogtag-pki_11.0.6.orig.tar.xz ecee6888299af32b9826cb66936d719c7bb2c80171609c91e0045294a4e246e5 43464 dogtag-pki_11.0.6-1.debian.tar.xz 0440c1a8a150a687738684079f5670480db75c51fba94708fcce08d3d7b8fa76 16054 dogtag-pki_11.0.6-1_source.buildinfo Files: 76c4bf876cdf84fc90f7567ad61d68ff 3786 java optional dogtag-pki_11.0.6-1.dsc cd19f620d38c8fc931b98f10f3c61332 6846728 java optional dogtag-pki_11.0.6.orig.tar.xz 5361c2546b16f39c19684d876cc2c967 43464 java optional dogtag-pki_11.0.6-1.debian.tar.xz fbd74e24d28ef7919ac80eeb5b923b9a 16054 java optional dogtag-pki_11.0.6-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmPAVk8ACgkQy3AxZaiJ hNwiQQ/9GN3vqrG0zL9szBQXufjG7Abbof5d2mLreiSsZTO93jWEwvgan3sb2A9H L/8BhenrtEcY2UNKbGRKsJUcrvu1o6PI8PI4yl3CHjCrR8Pyn2fFoqUqIJ7knHgf Kh5GMLl228A4nPdtchlwj3d7TGnCYM58TLBJQheyJRKbaUI745CjhyyPW1lJ54Pw aHBD4F0GRdhBVTgWPAHvmhhZhw8fa2ocE5Uas3EFrP0izOxRz29TJkhQnk0ui9cy d5hkKsxb6KmBrMO66RPpmxbcFHKtlTCl5qsWljJb56N9ihbiz2rEfvlLx4VQJE0H 3ShqgR9tOuIgQ41DDM06n3bYzWp24z3zYkJEKMbK7XZA3HOJk6JfODhjzqn8/mmN F4TiA/85Ceba6GoPFDVVTOWfNMLXSOaw0LQqY2YVFNSt+WOEBV82h+tbttpqUDr4 u26aOu1iq2NRB128/oc0PDAltPbm6R6x8McHboTA9eKV2LQti97jnqw/8uU/r/HO pO/G18i4PGDPXQVFlLRayp51kBJq5mpi92lz+oe0e1wRKfeiqThSfsEFsu7ppuKp
Bug#1024462: marked as done (pki-base-java depends on openjdk-11-jre-headless that will not be in bookworm)
Your message dated Thu, 12 Jan 2023 19:35:20 + with message-id and subject line Bug#1024462: fixed in dogtag-pki 11.0.6-1 has caused the Debian Bug report #1024462, regarding pki-base-java depends on openjdk-11-jre-headless that will not be in bookworm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pki-base-java Version: 11.0.3-4 Severity: serious Please update the dependency to default-jre-headless. --- End Message --- --- Begin Message --- Source: dogtag-pki Source-Version: 11.0.6-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of dogtag-pki, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated dogtag-pki package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Jan 2023 20:49:28 +0200 Source: dogtag-pki Built-For-Profiles: noudeb Architecture: source Version: 11.0.6-1 Distribution: unstable Urgency: medium Maintainer: Debian FreeIPA Team Changed-By: Timo Aaltonen Closes: 1014957 1024462 Changes: dogtag-pki (11.0.6-1) unstable; urgency=medium . * New upstream release. - CVE-2022-2414 (Closes: #1014957) * control: Fix pki-base-java to depend on default-jre-headless instead of a versioned one, it shouldn't be necessary to hardcode it anymore. (Closes: #1024462) * control: Bump dependency on jss, ldapjdk, tomcatjss. * dont-use-deprecated-python-ldap-options.diff: Drop constants removed in python-ldap 3.4. * rules: Bump JAVA_HOME to match java 17. Checksums-Sha1: f9c6c7ef6abc020664ef967a2609ef07c3712ea7 3786 dogtag-pki_11.0.6-1.dsc 1d5acd7acceb2fc8e6655e2b31d386c749444f6a 6846728 dogtag-pki_11.0.6.orig.tar.xz 88b10c46aa4b02c2ad172dea1ff6c9dcc6c469b9 43464 dogtag-pki_11.0.6-1.debian.tar.xz cac1ce2a08b8b8d11cf8c4a662a420dd99531763 16054 dogtag-pki_11.0.6-1_source.buildinfo Checksums-Sha256: a0de1237c7f74431209cdbffb5f90d5cb21353e51c8f72d3f705c636af35f1c5 3786 dogtag-pki_11.0.6-1.dsc d1dad801fcd20d91a2914af55fcdd9e6665ff679812ad0bf76109dca9588da7d 6846728 dogtag-pki_11.0.6.orig.tar.xz ecee6888299af32b9826cb66936d719c7bb2c80171609c91e0045294a4e246e5 43464 dogtag-pki_11.0.6-1.debian.tar.xz 0440c1a8a150a687738684079f5670480db75c51fba94708fcce08d3d7b8fa76 16054 dogtag-pki_11.0.6-1_source.buildinfo Files: 76c4bf876cdf84fc90f7567ad61d68ff 3786 java optional dogtag-pki_11.0.6-1.dsc cd19f620d38c8fc931b98f10f3c61332 6846728 java optional dogtag-pki_11.0.6.orig.tar.xz 5361c2546b16f39c19684d876cc2c967 43464 java optional dogtag-pki_11.0.6-1.debian.tar.xz fbd74e24d28ef7919ac80eeb5b923b9a 16054 java optional dogtag-pki_11.0.6-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmPAVk8ACgkQy3AxZaiJ hNwiQQ/9GN3vqrG0zL9szBQXufjG7Abbof5d2mLreiSsZTO93jWEwvgan3sb2A9H L/8BhenrtEcY2UNKbGRKsJUcrvu1o6PI8PI4yl3CHjCrR8Pyn2fFoqUqIJ7knHgf Kh5GMLl228A4nPdtchlwj3d7TGnCYM58TLBJQheyJRKbaUI745CjhyyPW1lJ54Pw aHBD4F0GRdhBVTgWPAHvmhhZhw8fa2ocE5Uas3EFrP0izOxRz29TJkhQnk0ui9cy d5hkKsxb6KmBrMO66RPpmxbcFHKtlTCl5qsWljJb56N9ihbiz2rEfvlLx4VQJE0H 3ShqgR9tOuIgQ41DDM06n3bYzWp24z3zYkJEKMbK7XZA3HOJk6JfODhjzqn8/mmN F4TiA/85Ceba6GoPFDVVTOWfNMLXSOaw0LQqY2YVFNSt+WOEBV82h+tbttpqUDr4 u26aOu1iq2NRB128/oc0PDAltPbm6R6x8McHboTA9eKV2LQti97jnqw/8uU/r/HO pO/G18i4PGDPXQVFlLRayp51kBJq5mpi92lz+oe0e1wRKfeiqThSfsEFsu7ppuKp DWRsF/qh+KlZ72S6LNsztG8sixLBwUVvObco5A7ens+dgjtEkLaF9nFwZko0kCpW c7oMYlYZV2+EWa4d4Y3gHHilmy/QJTmAT1RkCJHwZKFCX8iLKoU= =tuNd -END PGP SIGNATURE End Message ---
Bug#1019799: Proposed MBF: wxwidgets3.2 transition
On Thu, 12 Jan 2023 00:15:17 +0100, gregor herrmann wrote: > We haven't decided yet what's the best way out: > - skip use.t > - s/gcc/g++/ (which would pull in libc6-dev at the cost of adding > more dependencies for reverse dependencies of libwx-perl) > - and/or some more refined solutions around libwx-perl's runtime > dependencies I've uploaded 0.69+dfsg-6 now with: - gcc removed from Depends - debian/tests/autopkgtest-pkg-perl.conf with "extra_depends: g++" to get g++, libc6-dev etc. for autopkgtests > I hope that either the night shift fixes the issue one way or > another, or we'll come to a conclusion tomorrow :) Let's hope this works out as planned :) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1013935: [Pkg-freeipa-devel] Bug#1013935: dogtag-pki: flaky autopkgtest: regularly times out on amd64, armhf and s390x
Paul Gevers kirjoitti 27.6.2022 klo 21.31: Source: dogtag-pki Version: 11.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of you package because it was showing up on our "slow" page [1]. I noticed that there were several runs that took 2:47 (our timeout time), while successful runs more in the order of minutes. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. On top of that, when a test just hangs that's not good for our infrastructure. I'll put dogtag-pki on our reject_list for amd64, armhf, and s390x. Don't hesitate to reach out if you need help and some more information from our infrastructure. E.g. I note that the runs on amd64 that I happen to check are run on ci-worker13 that, together with our armhf worker is running on a host with lots of CPUs (64 and 160) and RAM (256GB and 511GB) and also our s390x has 10 CPUs and 32 GB. Paul [1] https://ci.debian.net/status/slow/ Hi, I've finally updated dogtag-pki to fix some grave bugs, but this still remains. I don't know if the update fixes these racy tests (which they are, something goes wrong and it gets stuck), but is there a way for me to manually trigger them on ci.debian.net? They do pass on salsa-ci, but it's not the same thing.. -- t
Processed: Re: quintuple: autopkgtest fail with numpy/1.24.1
Processing control commands: > tags -1 patch Bug #1027228 [src:quintuple] quintuple: autopkgtest fail with numpy/1.24.1 Added tag(s) patch. -- 1027228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027228: quintuple: autopkgtest fail with numpy/1.24.1
Control: tags -1 patch
The attached patch resolves the issue.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1diff -Nru quintuple-0~20171222/debian/changelog
quintuple-0~20171222/debian/changelog
--- quintuple-0~20171222/debian/changelog 2019-11-03 22:30:37.0
+0100
+++ quintuple-0~20171222/debian/changelog 2023-01-12 19:21:36.0
+0100
@@ -1,3 +1,11 @@
+quintuple (0~20171222-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch to fix test failure with Numpy 1.24.
+(closes: #1027228)
+
+ -- Bas Couwenberg Thu, 12 Jan 2023 19:21:36 +0100
+
quintuple (0~20171222-4) unstable; urgency=medium
* Update standards to 4.4.1.
diff -Nru quintuple-0~20171222/debian/patches/numpy-1.24.patch
quintuple-0~20171222/debian/patches/numpy-1.24.patch
--- quintuple-0~20171222/debian/patches/numpy-1.24.patch1970-01-01
01:00:00.0 +0100
+++ quintuple-0~20171222/debian/patches/numpy-1.24.patch2023-01-12
19:21:34.0 +0100
@@ -0,0 +1,24 @@
+Description: Fix test failure with Numpy 1.24.
+Author: Bas Couwenberg
+Bug-Debian: https://bugs.debian.org/1027228
+
+--- a/QuantumComputer.py
b/QuantumComputer.py
+@@ -13,7 +13,7 @@ import time
+ ## Gates
+
+ class Gate(object):
+- i_=np.complex(0,1)
++ i_=complex(0,1)
+ ## One qubit gates
+ # Hadamard gate
+ H=1./sqrt(2)*np.matrix('1 1; 1 -1')
+@@ -115,7 +115,7 @@ class Gate(object):
+ ## States
+
+ class State(object):
+- i_=np.complex(0,1)
++ i_=complex(0,1)
+ ## One qubit states (basis)
+ # standard basis (z)
+ zero_state=np.matrix('1; 0')
diff -Nru quintuple-0~20171222/debian/patches/series
quintuple-0~20171222/debian/patches/series
--- quintuple-0~20171222/debian/patches/series 2018-02-24 07:00:37.0
+0100
+++ quintuple-0~20171222/debian/patches/series 2023-01-12 19:19:46.0
+0100
@@ -1,2 +1,3 @@
documentation.patch
+numpy-1.24.patch
Bug#1028174: marked as done (zfs-linux FTBFS due to python3-packaging)
Your message dated Thu, 12 Jan 2023 18:24:20 + with message-id and subject line Bug#1028174: fixed in zfs-linux 2.1.7-2 has caused the Debian Bug report #1028174, regarding zfs-linux FTBFS due to python3-packaging to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1028174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:zfs-linux Version: 2.1.7-1 X-Debbugs-Cc: aeru...@aerusso.net Severity: grave Tags: patch The recent upgrade of python3-packaging from 21.3-1.1 to 22.0-2 breaks packaging.version.LegacyVersion (specifically, it removed it). The configure script will fail because it tries to use the unavailable class. Matthew Ahrens has fixed this with upstream commit b72efb751 [1]. Best, Antonio Russo [1] https://github.com/openzfs/zfs/commit/b72efb751147ab57afd1588a15910f547cb22600 --- End Message --- --- Begin Message --- Source: zfs-linux Source-Version: 2.1.7-2 Done: Aron Xu We believe that the bug you reported is fixed in the latest version of zfs-linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aron Xu (supplier of updated zfs-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 13 Jan 2023 01:47:49 +0800 Source: zfs-linux Architecture: source Version: 2.1.7-2 Distribution: unstable Urgency: medium Maintainer: Debian ZFS on Linux maintainers Changed-By: Aron Xu Closes: 1023070 1026402 1028174 1028242 Changes: zfs-linux (2.1.7-2) unstable; urgency=medium . [ Mo Zhou ] * Add script for testing bullseye->bookworm upgrade. (irrelevant to packaging) (See: #1024326) . [ Paulo Henrique de Lima Santana ] * Add Brazilian Portuguese debconf templates translation (Closes: #1026402) . [ Aron Xu ] * Add upstream patch to avoid packaging.version.LegacyVersion (Closes: #1028174) * libzfslinux-dev: Depends on libblkid-dev (Closes: #1023070) * Add upstream patch for linux 6.1 and 6.2 compatibility (Closes: #1028242) Checksums-Sha1: cb73421c07c961d3bdd5c99636183423f42f06c0 3164 zfs-linux_2.1.7-2.dsc 4b8650c1c54318d121142aab89e956a6c468c77c 109632 zfs-linux_2.1.7-2.debian.tar.xz 4aa5df833aa009392ba33b6b28193431f651303a 7871 zfs-linux_2.1.7-2_source.buildinfo Checksums-Sha256: 8eee6f91bbb4df6f4c085f0c010f18c6e0af83217adac123b4c75953a5cad5a1 3164 zfs-linux_2.1.7-2.dsc e852572fdb23bebb03d1a6178bbef61cc3eaecae08e13412d1b855cfb0e41f19 109632 zfs-linux_2.1.7-2.debian.tar.xz 9f1af768f3edd29fe1f30e90f2b91dff4ef1c1756f9eb1d0e9062c26e3ed3281 7871 zfs-linux_2.1.7-2_source.buildinfo Files: 6ddf48e7fea4dbfd216d017c9c982911 3164 contrib/kernel optional zfs-linux_2.1.7-2.dsc 1fa022b32921383a0767f14883140cfa 109632 contrib/kernel optional zfs-linux_2.1.7-2.debian.tar.xz e2279c7f93d5bda69abd161c0f0cf48f 7871 contrib/kernel optional zfs-linux_2.1.7-2_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhhz+aYQl/Bp4OTA7O1LKKgqv2VQFAmPASoIACgkQO1LKKgqv 2VR0kggAvGKDZoB4vYpz0i6hWUafGlSK2aVxLcMXu7x5rkTxr0eQ/v9mO1wjYKNk V659B/e1InCwnbg67LE1ihpx4c152kfWia8Mk7sLlOMOtKdgoFUhewzdVxDTEOyj iYx6Pwr2yArUyObplIV6FQLO2h0DJRXVQfG0xKFGi5HxqcYCYs0u/hQYue3pEN4y e1uwYmlLFpyixJ6bs+BGCFLjaPhBSP4iW9d1lJXY2VEg+vup38Qr2O+RcZ1kFV7h oog/mNqcad3c98KDB/yz2xEG1UVgdXYZ5toK11b3+5Pl6uIsBzdqNgN4WbcyQUSd 0CFINAlA1mehYF7rDKqg//D6xWlgMA== =Q2mY -END PGP SIGNATURE End Message ---
Bug#1028440: marked as done (warzone2100 build fixes)
Your message dated Thu, 12 Jan 2023 18:09:28 +
with message-id
and subject line Bug#1028440: fixed in warzone2100 4.3.3-3
has caused the Debian Bug report #1028440,
regarding warzone2100 build fixes
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1028440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: warzone2100
Version: 4.3.3-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=warzone2100=armel=4.3.3-2=1673284889=0
1. Wcast-align build errors on mipsel/riscv64/sparc64:
Attached is the fix/workaround I submitted upstream at
https://github.com/Warzone2100/warzone2100/pull/3084
2. The -latomic workaround for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
needs expansion:
--- debian/rules.old2023-01-10 00:02:52.580028340 +
+++ debian/rules2023-01-10 06:45:42.213281490 +
@@ -4,9 +4,9 @@
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
export DEB_CPPFLAGS_MAINT_APPEND = -DNDEBUG
-# riscv64 needs explicit -latomic
-ifneq (,$(filter $(DEB_HOST_ARCH), riscv64))
-export DEB_LDFLAGS_MAINT_APPEND = -latomic
+# workaround for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
+ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mipsel powerpc riscv64 sh4))
+export DEB_LDFLAGS_MAINT_APPEND = -Wl,--no-as-needed -latomic
-Wl,--as-needed
endif
%:
--- End Message ---
--- Begin Message ---
Source: warzone2100
Source-Version: 4.3.3-3
Done: Boyuan Yang
We believe that the bug you reported is fixed in the latest version of
warzone2100, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Boyuan Yang (supplier of updated warzone2100 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 12 Jan 2023 12:28:45 -0500
Source: warzone2100
Architecture: source
Version: 4.3.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team
Changed-By: Boyuan Yang
Closes: 1028440
Changes:
warzone2100 (4.3.3-3) unstable; urgency=medium
.
* Team upload.
* debian/*.{substvars,stamp,debhelper}: Dropped, they shall not
exist in packaging dir.
* debian/control: Bump Standards-Version to 4.6.2.
.
[ Adrian Bunk ]
* debian/rules: Update -latomic workaround for more architectures.
* debian/patches/0001: Add patch for Wcast-align build errors.
(Closes: #1028440)
Checksums-Sha1:
e4e2ef4292e8def502a58fcba75e6e4428c37c1c 2687 warzone2100_4.3.3-3.dsc
9a27693e5430c9a9c84d24d27b4f6941cc0c7dc2 320439712
warzone2100_4.3.3.orig.tar.xz
13955bc74163e9e1aa4dc246da0ff7016d5ed504 26016
warzone2100_4.3.3-3.debian.tar.xz
560658ef31d5d91a15ca5475154d10b278dfebfd 15618
warzone2100_4.3.3-3_amd64.buildinfo
Checksums-Sha256:
b0f98410890dfdd10f119cd9b39bea81895343ef79bef2ef16acaab84c60c744 2687
warzone2100_4.3.3-3.dsc
3c3cb9988600a10f5500909344c881a94951b4a22a54788cb818a8cd3b47e59e 320439712
warzone2100_4.3.3.orig.tar.xz
0ae4f1213a92fa5541a32811ff72351f66c7c58117133e61c358cae043270c92 26016
warzone2100_4.3.3-3.debian.tar.xz
8e56241a00f0fd1a09d63a71d8b6728121226cb9e854e17cdb93ecda1d141594 15618
warzone2100_4.3.3-3_amd64.buildinfo
Files:
652b4bd9fc1c76444f8be217e8a73c45 2687 games optional warzone2100_4.3.3-3.dsc
93c37e634703f85f22405f0ce063a5f9 320439712 games optional
warzone2100_4.3.3.orig.tar.xz
402d6bd392da711e3229b74ac6f30f8f 26016 games optional
warzone2100_4.3.3-3.debian.tar.xz
0ccfa71fac25bab1cc2e237b1b082a31 15618 games optional
warzone2100_4.3.3-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmPASCEACgkQwpPntGGC
Ws63bQ/8CP9iinonHRrCV8VWkWALXH/68Rn8Cb3vdlXsNm7ncTVa2nvhP/iTgtPh
3Lrg6dIkt4vNxPMAweMiWPdP6C3IAM6Ms+OrlsdfbagHeXXhJVcWZhs1KgaQFVKR
EJSTnPBfu7HngXgaSIiqGMaawqDohsBDbhUrjSYob5XWNUDXRD0+SqMi1D+n3QVu
i0aMOLUXDPC+r74qB/kWfdThbrGq4cMTCpI4x9xHLFmCu9cMk5gDCgatoNGqxnBC
q+RvJDh72KTvIs1hcZX52B/7cHRllF8NGvsEamX7wmhfcdapiZBCabP1Q5HojRmR
BEsDfGgAhCPHiB+pJCtRSz6Y/qmecM6J12AgZoyU01Mae59XIKA7+vCXIojmY36U
Bug#1026734: mricron: FTBFS: /usr/bin/ld.bfd: cannot find -lX11: No such file or directory
Hi Santiago, thanks again for watching me. ;-) Am Thu, Jan 12, 2023 at 05:10:50PM +0100 schrieb Santiago Vila: > This is really weird. +1 > This package also failed for me on bookworm, with the same error > which happened to Lucas (the one in the Subject). > > But today I tried again (in bookworm) and it worked, without any source > change at all. > (mricron version 1.2.20211006+dfsg-1). > > I see that this change was made to try to fix the bug: > > * Build-Depends: libx11-dev. Closes: #1026734 > > but libx11-dev was already being installed when the package was built: > > https://buildd.debian.org/status/fetch.php?pkg=mricron=amd64=1.2.20211006%2Bdfsg-1=1637004231=0 > > (probably because of a build-dependency which in turn had a dependency on > libx11-dev). Yes, this is what I assumed ... but I wanted to be super sure. > So, even if adding libx11-dev was probably correct and formally necessary, > as -lX11 was being used, I think it was not the real reason for the failure. > > (Cc to Lucas, just in case he reported similar bugs in other packages). I'd be also curious what might have caused that problem. > Thanks. Thanks to you Andreas. -- http://fam-tille.de
Bug#1027930: marked as done (src:xml2rfc: fails to migrate to testing for too long: autopkgtest regression)
Your message dated Thu, 12 Jan 2023 17:23:19 + with message-id and subject line Bug#1027930: fixed in xml2rfc 3.15.3-1 has caused the Debian Bug report #1027930, regarding src:xml2rfc: fails to migrate to testing for too long: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xml2rfc Version: 3.13.1-1 Severity: serious Control: close -1 3.15.2-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:xml2rfc has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package is blocked because the autopkgtest regressed on all architectures we run it on. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=xml2rfc OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: xml2rfc Source-Version: 3.15.3-1 Done: Daniel Kahn Gillmor We believe that the bug you reported is fixed in the latest version of xml2rfc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Kahn Gillmor (supplier of updated xml2rfc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 12 Jan 2023 09:38:22 -0500 Source: xml2rfc Architecture: source Version: 3.15.3-1 Distribution: unstable Urgency: medium Maintainer: Daniel Kahn Gillmor Changed-By: Daniel Kahn Gillmor Closes: 1027930 Changes: xml2rfc (3.15.3-1) unstable; urgency=medium . * New upstream release * Work around brittle test (Closes: #1027930) Checksums-Sha1: 07717a4a530f804e2fd22ba0d7e44b287aa90f58 2067 xml2rfc_3.15.3-1.dsc da9f31835b09eaa13749a8b3c52e8c3f456f1e59 2645561 xml2rfc_3.15.3.orig.tar.gz cac4111f0a1d3eb5b58cb781cf3c4175b36120ef 850 xml2rfc_3.15.3.orig.tar.gz.asc 6d0766a97434f9e12ad161e6824d6afef915 24020 xml2rfc_3.15.3-1.debian.tar.xz b52d619f35238ca72d96eceff109e8766f263d9f 8572 xml2rfc_3.15.3-1_amd64.buildinfo Checksums-Sha256: 09b45a6afcad25a7f95656fb6248bff3d51d9b4e4e1d7ad51c21a067d45cedee 2067 xml2rfc_3.15.3-1.dsc 5d1c1d6f0bcaa7f53221b5fe712213d65d8a69ac84c6c64b16e6f88aee595788 2645561 xml2rfc_3.15.3.orig.tar.gz fc7f49edeacbe7ad3443399ca66bbc1f2ae746d5ec5d874e0b5d617ea35f 850 xml2rfc_3.15.3.orig.tar.gz.asc 516cc4ea8a7a23b0e1c796bba7be40f78de7452b32c34196c506e2facd35814e 24020 xml2rfc_3.15.3-1.debian.tar.xz 5292f7eedad6f7ae758eb72e1efdc4d6da817f2955044d8593297a75e1f1d860 8572 xml2rfc_3.15.3-1_amd64.buildinfo Files: 9bce7741e3faf2bfc58908e52434593a 2067 non-free/text optional xml2rfc_3.15.3-1.dsc d83972610d018427e594ad6b6af6208b 2645561 non-free/text optional xml2rfc_3.15.3.orig.tar.gz 285d7d1b6359379bc6f00295d95cb400 850 non-free/text
Bug#1026328: marked as done (libbpp-core breaks bppsuite autopkgtest)
Your message dated Thu, 12 Jan 2023 18:16:41 +0100 with message-id and subject line Test is fixed thus closing the bug (Was: libbpp-core breaks bppsuite autopkgtest) has caused the Debian Bug report #1026328, regarding libbpp-core breaks bppsuite autopkgtest to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-core, bppsuite Control: found -1 libbpp-core/2.4.1-9 Control: found -1 bppsuite/2.4.1-5 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of libbpp-core the autopkgtest of bppsuite fails in testing when that autopkgtest is run with the binary packages of libbpp-core from unstable. It passes when run with only packages from testing. In tabular form: passfail libbpp-corefrom testing2.4.1-9 bppsuite from testing2.4.1-5 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of libbpp-core to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=libbpp-core https://ci.debian.net/data/autopkgtest/testing/arm64/b/bppsuite/29470275/log.gz Test 1 ** * Bio++ Maximum Likelihood Computation, version 2.4.0 * ** * Authors: J. Dutheil Last Modif. 19/02/18 * * B. Boussau* * L. Guéguen* * M. Groussin * ** Parsing options: Parsing file ML.bpp for options. Alphabet type .: Codon(letter=DNA) Genetic Code...: Standard Sequence file .: ../../../Data/lysozymeLarge.fasta Sequence format ...: FASTA file Sites to use...: all Remove sites with gaps.: [ ] 0% [= ] 3% [==] 6% [=== ] 9% [ ] 12% [= ] 15% [=== ] 18% [ ] 21% [= ] 24% [==] 27% [=== ] 31% [ ] 34% [==] 37% [=== ] 40% [ ] 43% [= ] 46% [==] 49% [ ] 52% [= ] 55% [==] 58% [=== ] 62% [ ] 65% [= ] 68% [=== ] 71% [ ] 74% [= ] 77% [==] 80% [=== ] 83% [ ] 86% [==] 89% [=== ] 93% [ ] 96% [= ] 99% [==] 100%Done. Remove Stop Codons.: yes Number of sequences: 19 Number of sites: 130 Input tree.: user Input tree file ...: ../../../Data/lysozymeLarge.dnd Input tree format .: Newick Number of leaves...: 19 Output tree file ..:
Processed: bug 1027930 is forwarded to https://github.com/ietf-tools/xml2rfc/issues/957
Processing commands for cont...@bugs.debian.org:
> forwarded 1027930 https://github.com/ietf-tools/xml2rfc/issues/957
Bug #1027930 {Done: Paul Gevers } [src:xml2rfc] src:xml2rfc:
fails to migrate to testing for too long: autopkgtest regression
Set Bug forwarded-to-address to
'https://github.com/ietf-tools/xml2rfc/issues/957'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Unable to import neuron in python3
Processing control commands: > found -1 7.6.3-3 Bug #895531 [python3-neuron] Unable to import neuron in python3 There is no source info for the package 'python3-neuron' at version '7.6.3-3' with architecture '' Unable to make a source version for version '7.6.3-3' Marked as found in versions 7.6.3-3. > severity -1 serious Bug #895531 [python3-neuron] Unable to import neuron in python3 Severity set to 'serious' from 'normal' -- 895531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026734: mricron: FTBFS: /usr/bin/ld.bfd: cannot find -lX11: No such file or directory
Hi. This is really weird. This package also failed for me on bookworm, with the same error which happened to Lucas (the one in the Subject). But today I tried again (in bookworm) and it worked, without any source change at all. (mricron version 1.2.20211006+dfsg-1). I see that this change was made to try to fix the bug: * Build-Depends: libx11-dev. Closes: #1026734 but libx11-dev was already being installed when the package was built: https://buildd.debian.org/status/fetch.php?pkg=mricron=amd64=1.2.20211006%2Bdfsg-1=1637004231=0 (probably because of a build-dependency which in turn had a dependency on libx11-dev). So, even if adding libx11-dev was probably correct and formally necessary, as -lX11 was being used, I think it was not the real reason for the failure. (Cc to Lucas, just in case he reported similar bugs in other packages). Thanks.
Processed: block 997475 with 1028548
Processing commands for cont...@bugs.debian.org:
> block 997475 with 1028548
Bug #997475 [src:hyperspy] hyperspy: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
997475 was not blocked by any bugs.
997475 was not blocking any bugs.
Added blocking bug(s) of 997475: 1028548
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: block 1028548 with 1025393 1027254
Processing commands for cont...@bugs.debian.org: > block 1028548 with 1025393 1027254 Bug #1028548 [hyperspy] New upstream version needed 1028548 was not blocked by any bugs. 1028548 was not blocking any bugs. Added blocking bug(s) of 1028548: 1027254 and 1025393 > thanks Stopping processing here. Please contact me if you need assistance. -- 1028548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1025102
Processing commands for cont...@bugs.debian.org: > tags 1025102 + pending Bug #1025102 [src:python-gbulb] python-gbulb: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1025102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027908: marked as done (golang-github-jedib0t-go-pretty: FTBFS in bookworm (undeclared build-dependency on tzdata))
Your message dated Thu, 12 Jan 2023 14:37:27 + with message-id and subject line Bug#1027908: fixed in golang-github-jedib0t-go-pretty 6.4.4-2 has caused the Debian Bug report #1027908, regarding golang-github-jedib0t-go-pretty: FTBFS in bookworm (undeclared build-dependency on tzdata) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:golang-github-jedib0t-go-pretty Version: 6.3.3-1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -i -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build: warning: github.com/jedib0t/go-pretty contains no non-test Go files, removing it from build cd _build && go install -trimpath -v -p 1 github.com/jedib0t/go-pretty/list github.com/jedib0t/go-pretty/progress github.com/jedib0t/go-pretty/table github.com/jedib0t/go-pretty/text internal/goarch internal/unsafeheader internal/abi internal/cpu internal/bytealg internal/goexperiment internal/goos runtime/internal/atomic runtime/internal/math runtime/internal/sys runtime/internal/syscall runtime internal/reflectlite errors internal/itoa math/bits math unicode/utf8 strconv internal/race sync/atomic sync unicode reflect sort internal/fmtsort io internal/oserror syscall internal/syscall/unix time internal/poll internal/syscall/execenv internal/testlog path io/fs os fmt bytes encoding encoding/binary encoding/base64 strings unicode/utf16 encoding/json github.com/rivo/uniseg regexp/syntax regexp github.com/mattn/go-runewidth github.com/jedib0t/go-pretty/text html github.com/jedib0t/go-pretty/list github.com/jedib0t/go-pretty/progress github.com/jedib0t/go-pretty/table dh_auto_test -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 1 github.com/jedib0t/go-pretty github.com/jedib0t/go-pretty/list github.com/jedib0t/go-pretty/progress github.com/jedib0t/go-pretty/table github.com/jedib0t/go-pretty/text testing: warning: no tests to run PASS ok github.com/jedib0t/go-pretty0.002s [no tests to run] === RUN TestNewWriter --- PASS: TestNewWriter (0.00s) === RUN TestList_AppendItem --- PASS: TestList_AppendItem (0.00s) === RUN TestList_AppendItems --- PASS: TestList_AppendItems (0.00s) === RUN TestList_Indent --- PASS: TestList_Indent (0.00s) === RUN TestList_Length --- PASS: TestList_Length (0.00s) === RUN TestList_Reset --- PASS: TestList_Reset (0.00s) === RUN TestList_SetHTMLCSSClass --- PASS: TestList_SetHTMLCSSClass (0.00s) === RUN TestList_SetOutputMirror --- PASS: TestList_SetOutputMirror (0.00s) === RUN TestList_SetStyle --- PASS: TestList_SetStyle (0.00s) === RUN TestList_UnIndent --- PASS: TestList_UnIndent (0.00s) === RUN TestList_RenderHTML --- PASS: TestList_RenderHTML (0.00s) === RUN TestList_RenderHTML_Complex --- PASS: TestList_RenderHTML_Complex (0.00s) === RUN TestList_RenderMarkdown --- PASS: TestList_RenderMarkdown (0.00s) === RUN TestList_Render --- PASS: TestList_Render (0.00s) === RUN TestList_Render_Complex --- PASS: TestList_Render_Complex (0.00s) === RUN TestList_Render_Connected --- PASS: TestList_Render_Connected (0.00s) === RUN TestList_Render_MultiLine --- PASS: TestList_Render_MultiLine (0.00s) === RUN TestList_Render_Styles --- PASS: TestList_Render_Styles (0.00s) === RUN Example --- PASS: Example (0.00s) PASS ok github.com/jedib0t/go-pretty/list 0.008s === RUN TestIndeterminateIndicatorDominoes --- PASS: TestIndeterminateIndicatorDominoes (0.31s) === RUN TestIndeterminateIndicatorMovingBackAndForth --- PASS: TestIndeterminateIndicatorMovingBackAndForth (0.29s) === RUN Test_indeterminateIndicatorMovingBackAndForth1 --- PASS: Test_indeterminateIndicatorMovingBackAndForth1 (0.00s) === RUN Test_indeterminateIndicatorMovingBackAndForth2 --- PASS: Test_indeterminateIndicatorMovingBackAndForth2 (0.00s) === RUN Test_indeterminateIndicatorMovingBackAndForth3 --- PASS: Test_indeterminateIndicatorMovingBackAndForth3 (0.00s) === RUN
Bug#1028540: xrdp 0.9.21 black screen with cursor
Package: xrdp Version: 0.9.21.1-1 Severity: critical xrdp 0.9.12-1.1: RDP works fine. xrdp 0.9.21.1-1: RDP didn't works (black screen with cursor) See upstream bug for more details: https://github.com/neutrinolabs/xrdp/issues/2496
Bug#1028451: 2nd DisplayPort doesn't get video
On Thursday, 12 January 2023 12:03:24 CET Sjoerd Simons wrote:
> Fwiw there is a general regression with AMDGPU MST on linux 6.1; tracked
> upstream here:
> https://gitlab.freedesktop.org/drm/amd/-/issues/2171
Thanks! About an hour ago the suggested fix was to revert commit
4d07b0bc403403438d9cf88450506240c5faf92f part of v6.1-rc1
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
describes a procedure to build a kernel with the proposed patch (attached).
OdyX: Can you try to see whether that resolves the issue?diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
index 77277d90b6e2..674f5dc1102b 100644
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
@@ -6548,7 +6548,6 @@ static int dm_encoder_helper_atomic_check(struct drm_encoder *encoder,
const struct drm_display_mode *adjusted_mode = _state->adjusted_mode;
struct drm_dp_mst_topology_mgr *mst_mgr;
struct drm_dp_mst_port *mst_port;
- struct drm_dp_mst_topology_state *mst_state;
enum dc_color_depth color_depth;
int clock, bpp = 0;
bool is_y420 = false;
@@ -6562,13 +6561,6 @@ static int dm_encoder_helper_atomic_check(struct drm_encoder *encoder,
if (!crtc_state->connectors_changed && !crtc_state->mode_changed)
return 0;
- mst_state = drm_atomic_get_mst_topology_state(state, mst_mgr);
- if (IS_ERR(mst_state))
- return PTR_ERR(mst_state);
-
- if (!mst_state->pbn_div)
- mst_state->pbn_div = dm_mst_get_pbn_divider(aconnector->mst_port->dc_link);
-
if (!state->duplicated) {
int max_bpc = conn_state->max_requested_bpc;
is_y420 = drm_mode_is_420_also(>display_info, adjusted_mode) &&
@@ -6580,10 +6572,11 @@ static int dm_encoder_helper_atomic_check(struct drm_encoder *encoder,
clock = adjusted_mode->clock;
dm_new_connector_state->pbn = drm_dp_calc_pbn_mode(clock, bpp, false);
}
-
- dm_new_connector_state->vcpi_slots =
- drm_dp_atomic_find_time_slots(state, mst_mgr, mst_port,
- dm_new_connector_state->pbn);
+ dm_new_connector_state->vcpi_slots = drm_dp_atomic_find_time_slots(state,
+ mst_mgr,
+ mst_port,
+ dm_new_connector_state->pbn,
+ dm_mst_get_pbn_divider(aconnector->dc_link));
if (dm_new_connector_state->vcpi_slots < 0) {
DRM_DEBUG_ATOMIC("failed finding vcpi slots: %d\n", (int)dm_new_connector_state->vcpi_slots);
return dm_new_connector_state->vcpi_slots;
@@ -6654,14 +6647,17 @@ static int dm_update_mst_vcpi_slots_for_dsc(struct drm_atomic_state *state,
dm_conn_state->vcpi_slots = slot_num;
ret = drm_dp_mst_atomic_enable_dsc(state, aconnector->port,
- dm_conn_state->pbn, false);
+ dm_conn_state->pbn, 0, false);
if (ret < 0)
return ret;
continue;
}
- vcpi = drm_dp_mst_atomic_enable_dsc(state, aconnector->port, pbn, true);
+ vcpi = drm_dp_mst_atomic_enable_dsc(state,
+ aconnector->port,
+ pbn, pbn_div,
+ true);
if (vcpi < 0)
return vcpi;
@@ -9497,6 +9493,8 @@ static int amdgpu_dm_atomic_check(struct drm_device *dev,
struct dm_crtc_state *dm_old_crtc_state, *dm_new_crtc_state;
#if defined(CONFIG_DRM_AMD_DC_DCN)
struct dsc_mst_fairness_vars vars[MAX_PIPES];
+ struct drm_dp_mst_topology_state *mst_state;
+ struct drm_dp_mst_topology_mgr *mgr;
#endif
trace_amdgpu_dm_atomic_check_begin(state);
@@ -9744,6 +9742,33 @@ static int amdgpu_dm_atomic_check(struct drm_device *dev,
lock_and_validation_needed = true;
}
+#if defined(CONFIG_DRM_AMD_DC_DCN)
+ /* set the slot info for each mst_state based on the link encoding format */
+ for_each_new_mst_mgr_in_state(state, mgr, mst_state, i) {
+ struct amdgpu_dm_connector *aconnector;
+ struct drm_connector *connector;
+ struct drm_connector_list_iter iter;
+ u8 link_coding_cap;
+
+ if (!mgr->mst_state )
+ continue;
+
+ drm_connector_list_iter_begin(dev, );
+ drm_for_each_connector_iter(connector, ) {
+ int id = connector->index;
+
+ if (id == mst_state->mgr->conn_base_id) {
+aconnector = to_amdgpu_dm_connector(connector);
+link_coding_cap = dc_link_dp_mst_decide_link_encoding_format(aconnector->dc_link);
+drm_dp_mst_update_slots(mst_state, link_coding_cap);
+
+break;
+ }
+ }
+ drm_connector_list_iter_end();
+
+ }
+#endif
/**
* Streams and planes are reset when there are changes that affect
* bandwidth. Anything that affects bandwidth needs to go through
diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c
index 6994c9a1ed85..ac5a8cad0695 100644
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c
@@ -27,7 +27,6 @@
#include
#include
-#include
#include
#include
#include
@@ -120,27 +119,40 @@ enum dc_edid_status dm_helpers_parse_edid_caps(
}
static void
Bug#1027679: marked as done (qtimageformats-opensource-src: FTBFS with tiff 4.5.0+)
Your message dated Thu, 12 Jan 2023 13:52:11 +
with message-id
and subject line Bug#1027679: fixed in qtimageformats-opensource-src 5.15.7-3
has caused the Debian Bug report #1027679,
regarding qtimageformats-opensource-src: FTBFS with tiff 4.5.0+
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1027679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtimageformats-opensource-src
Version: 5.15.7-2
Severity: important
Justification: FTBFS
Usertags: tiff4_5
Tags: sid bookworm ftbfs patch
Hi,
Your package fails to build with the new major tiff release. During
self-testing two tiff RGB tests fail, I think maybe due to broken
images. Fixing it is easy, just disable those two tests, patch is
attached.
Regards,
Laszlo/GCS
Description: disable non-working, TIFF RGB tests
Don't run TIFF RGB tests.
Author: Laszlo Boszormenyi (GCS)
Last-Update: 2023-01-01
---
--- qtimageformats-opensource-src-5.15.7.orig/tests/auto/tiff/tst_qtiff.cpp
+++ qtimageformats-opensource-src-5.15.7/tests/auto/tiff/tst_qtiff.cpp
@@ -168,7 +168,7 @@ void tst_qtiff::readImage_data()
QTest::newRow("teapot") << QString("teapot.tiff") << QSize(256, 256);
QTest::newRow("oddsize_grayscale") << QString("oddsize_grayscale.tiff") << QSize(59, 71);
QTest::newRow("oddsize_mono") << QString("oddsize_mono.tiff") << QSize(59, 71);
-QTest::newRow("tiled_rgb") << QString("tiled_rgb.tiff") << QSize(64, 64);
+//QTest::newRow("tiled_rgb") << QString("tiled_rgb.tiff") << QSize(64, 64);
QTest::newRow("tiled_indexed") << QString("tiled_indexed.tiff") << QSize(64, 64);
QTest::newRow("tiled_grayscale") << QString("tiled_grayscale.tiff") << QSize(64, 64);
QTest::newRow("tiled_mono") << QString("tiled_mono.tiff") << QSize(64, 64);
@@ -596,7 +596,7 @@ void tst_qtiff::tiled_data()
{
QTest::addColumn("expectedFile");
QTest::addColumn("tiledFile");
-QTest::newRow("RGB") << "original_rgb.tiff" << "tiled_rgb.tiff";
+//QTest::newRow("RGB") << "original_rgb.tiff" << "tiled_rgb.tiff";
QTest::newRow("Indexed") << "original_indexed.tiff" << "tiled_indexed.tiff";
QTest::newRow("Grayscale") << "original_grayscale.tiff" << "tiled_grayscale.tiff";
QTest::newRow("Mono") << "original_mono.tiff" << "tiled_mono.tiff";
--- End Message ---
--- Begin Message ---
Source: qtimageformats-opensource-src
Source-Version: 5.15.7-3
Done: Dmitry Shachnev
We believe that the bug you reported is fixed in the latest version of
qtimageformats-opensource-src, which is due to be installed in the Debian FTP
archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1027...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Shachnev (supplier of updated
qtimageformats-opensource-src package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 12 Jan 2023 17:35:55 +0400
Source: qtimageformats-opensource-src
Architecture: source
Version: 5.15.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers
Changed-By: Dmitry Shachnev
Closes: 1027679
Changes:
qtimageformats-opensource-src (5.15.7-3) unstable; urgency=medium
.
* Fix tests with libtiff 4.5 (closes: #1027679).
- Depend on qtbase version which has image_deletion_order.diff.
- Add a patch to implement support for file memory mapping for tiff.
Checksums-Sha1:
dd9470858e45e6c51dbf8896beb4127b8276696e 2499
qtimageformats-opensource-src_5.15.7-3.dsc
efaccf9038df7f21afc14ae3a8da3629032f30bb 7528
qtimageformats-opensource-src_5.15.7-3.debian.tar.xz
d2bbd1a63de0bcdd7acda743e86722893527aa3c 10860
qtimageformats-opensource-src_5.15.7-3_source.buildinfo
Checksums-Sha256:
c837302e8e7afe44dbdca21082b3ff67af8bf1f6c3ed621015cee8c3bd49ba91 2499
qtimageformats-opensource-src_5.15.7-3.dsc
0fca2327ad80f6a210d83e92bbd7eb78ddea550c6864d3f755ef4d62e55007ad 7528
qtimageformats-opensource-src_5.15.7-3.debian.tar.xz
6dd952ddcb58cb4dcd678676b60b07c453470b2e52fe9e21d0b307a61a0bf782 10860
qtimageformats-opensource-src_5.15.7-3_source.buildinfo
Files:
b9342d52fab9a31dd8b5e6adb14a14fc 2499 libs optional
Processed: Bug#1027908 marked as pending in golang-github-jedib0t-go-pretty
Processing control commands: > tag -1 pending Bug #1027908 [src:golang-github-jedib0t-go-pretty] golang-github-jedib0t-go-pretty: FTBFS in bookworm (undeclared build-dependency on tzdata) Added tag(s) pending. -- 1027908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027908: marked as pending in golang-github-jedib0t-go-pretty
Control: tag -1 pending Hello, Bug #1027908 in golang-github-jedib0t-go-pretty 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/go-team/packages/golang-github-jedib0t-go-pretty/-/commit/a24cbfcb2fdfa10c7a9a1d73413f6f5a20491b76 Add tzdata in Build-Depends (Closes: #1027908) (this message was generated automatically) -- Greetings https://bugs.debian.org/1027908
Bug#1027679: marked as pending in qtimageformats-opensource-src
Control: tag -1 pending Hello, Bug #1027679 in qtimageformats-opensource-src 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/qt-kde-team/qt/qtimageformats/-/commit/6ced0af17cf93588ea68d3d7e1be66097cc02ea3 Fix tests with libtiff 4.5. - Depend on qtbase version which has image_deletion_order.diff. - Add a patch to implement support for file memory mapping for tiff. Closes: #1027679. (this message was generated automatically) -- Greetings https://bugs.debian.org/1027679
Processed: Bug#1027679 marked as pending in qtimageformats-opensource-src
Processing control commands: > tag -1 pending Bug #1027679 [src:qtimageformats-opensource-src] qtimageformats-opensource-src: FTBFS with tiff 4.5.0+ Added tag(s) pending. -- 1027679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002188: Blocked by #1017905 ?
The problem is that #1017905 probably blocks the whole thing from being updated which is likely needed for resvg if you want to introduce a newer upstream (that is, if you want to do that. the rust GTK bindings had some API incompatibility issues between versions). Updating and uploading the GTK stack is on my todo-list but tbh I don't see why I should prioritize it if I don't know if it will be rejected. Cheers werdahias
Bug#1028438: marked as done (otpclient: OTP values are all 000000)
Your message dated Thu, 12 Jan 2023 13:26:12 + with message-id <92b5516b-4b1e-8efa-1367-f7137606f...@debian.org> and subject line Re: Bug#1028438: otpclient: OTP values are all 00 has caused the Debian Bug report #1028438, regarding otpclient: OTP values are all 00 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1028438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: otpclient Version: 3.1.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? the update from 2.6.3-2 to 3.1.1-1 seems to be when the issue was introduced * What exactly did you do (or not do) that was effective (or ineffective)? ineffective measures taken: reboot uninstall (apt remove --purge otpclient), then reinstall (apt install otpclient) created a new database deleted otpclient config (~/.config/otpclient.cfg) i no longer have a deb for the previous version, so i am unable to test that * What was the outcome of this action? 00 is always returned for every entry (about 20 distinct entriest to choose from) * What outcome did you expect instead? valid OTP codes -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) 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 otpclient depends on: ii libbaseencode1 1.0.15-1 ii libc62.36-8 ii libcotp121.2.7-1 ii libgcrypt20 1.10.1-3 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1 ii libglib2.0-0 2.74.4-1 ii libgtk-3-0 3.24.36-1 ii libjansson4 2.14-2 ii libpng16-16 1.6.39-2 ii libprotobuf-c1 1.4.1-1+b1 ii libqrencode4 4.1.1-1 ii libsecret-1-00.20.5-3 ii libuuid1 2.38.1-4 ii libzbar0 0.23.92-7 otpclient recommends no packages. Versions of packages otpclient suggests: pn otpclient-cli -- no debconf information --- End Message --- --- Begin Message --- Hi Buster Keaton, I just upgraded otpclient from 2.6.3-2 to 3.1.1-1 and everything went fine, this error you reported did not occur*. Here is part of my /var/log/apt/history.log: Commandline: apt install otpclient Upgrade: otpclient-cli:amd64 (2.6.3-2, 3.1.1-1), otpclient:amd64 (2.6.3-2, 3.1.1-1) The fact that you have deleted otpclient config (~/.config/otpclient.cfg) would not solve the problem, what we need to preserve would be the ~/otpclient.enc file, if you have the backup file of ~/otpclient.enc you can try to restore and test if the OTP Values are valid. * I close the bug after checking what has been reported, so far I have not encountered any problems. Thanks! -- Francisco Vilmar Cardoso Ruviaro 4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00 OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Processed: bug 1027606 is forwarded to https://github.com/sarugaku/resolvelib/issues/114
Processing commands for cont...@bugs.debian.org:
> forwarded 1027606 https://github.com/sarugaku/resolvelib/issues/114
Bug #1027606 [src:python-resolvelib] python-resolvelib: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned
exit code 13
Set Bug forwarded-to-address to
'https://github.com/sarugaku/resolvelib/issues/114'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1027094: marked as done (FTBFS against bind9 9.18.10)
Your message dated Thu, 12 Jan 2023 13:19:09 +
with message-id
and subject line Bug#1027094: fixed in bind-dyndb-ldap 11.10-2
has caused the Debian Bug report #1027094,
regarding FTBFS against bind9 9.18.10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1027094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind-dyndb-ldap
Version: 11.10-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: team+...@tracker.debian.org
bind-dyndb-ldap has a tight dependency on the upstream version of bind9-libs
(built by src:bind9) and needs to be rebuilt on every new upstream version
until https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014503 is fixed.
This worked fine until bind9 9.18.8, but fails in 9.18.10
https://buildd.debian.org/status/fetch.php?pkg=bind-dyndb-ldap=amd64=11.10-1%2Bb5=1671812545=0
This is rather serious as it prevents the migration of 9.18.10 to testing
which includes systemd notify support and upstream bugfixes. Also bind9 has
followed upstream security releases during bullseye already, so it will
break later if 9.18.10 misses the freeze due to this issue.
Possible commits:
https://gitlab.isc.org/isc-projects/bind9/-/compare/v9_18_8...v9_18_10?from_project_id=1
In file included from ../../src/zone_register.h:8,
from ../../src/ldap_convert.c:28:
/usr/include/dns/zt.h:171:28: error: unknown type name ‘isc_rwlocktype_t’; did
you mean ‘isc_rwlock_t’?
171 | dns_zt_apply(dns_zt_t *zt, isc_rwlocktype_t lock, bool stop,
isc_result_t *sub,
|^~~~
|isc_rwlock_t
make[3]: *** [Makefile:592: ldap_la-ldap_convert.lo] Error 1
make[3]: *** Waiting for unfinished jobs
In file included from ../../src/util.h:17,
from ../../src/bindcfg.h:10,
from ../../src/ldap_driver.c:39:
../../src/ldap_driver.c: In function ‘beginload’:
../../src/log.h:21:9: error: too few arguments to function ‘isc_error_fatal’
21 | isc_error_fatal(__FILE__, __LINE__, __VA_ARGS__)
| ^~~
../../src/ldap_driver.c:220:9: note: in expansion of macro ‘fatal_error’
220 | fatal_error("ldapdb: method beginload() should never be
called");
| ^~~
In file included from /usr/include/isc/util.h:312,
from /usr/include/isc/atomic.h:22,
from /usr/include/isc/refcount.h:19,
from ../../src/ldap_driver.c:16:
/usr/include/isc/error.h:42:1: note: declared here
42 | isc_error_fatal(const char *, int, const char *, const char *, ...)
| ^~~
../../src/ldap_driver.c: In function ‘endload’:
../../src/log.h:21:9: error: too few arguments to function ‘isc_error_fatal’
21 | isc_error_fatal(__FILE__, __LINE__, __VA_ARGS__)
| ^~~
../../src/ldap_driver.c:237:9: note: in expansion of macro ‘fatal_error’
237 | fatal_error("ldapdb: method endload() should never be called");
| ^~~
/usr/include/isc/error.h:42:1: note: declared here
42 | isc_error_fatal(const char *, int, const char *, const char *, ...)
| ^~~
../../src/ldap_driver.c: In function ‘dump’:
../../src/log.h:21:9: error: too few arguments to function ‘isc_error_fatal’
21 | isc_error_fatal(__FILE__, __LINE__, __VA_ARGS__)
| ^~~
../../src/ldap_driver.c:266:9: note: in expansion of macro ‘fatal_error’
266 | fatal_error("ldapdb: method dump() should never be called");
| ^~~
/usr/include/isc/error.h:42:1: note: declared here
42 | isc_error_fatal(const char *, int, const char *, const char *, ...)
| ^~~
../../src/ldap_driver.c: In function ‘allrdatasets’:
../../src/ldap_driver.c:474:71: error: passing argument 5 of
‘dns_db_allrdatasets’ makes integer from pointer without a cast
[-Werror=int-conversion]
474 | return dns_db_allrdatasets(ldapdb->rbtdb, node, version, now,
iteratorp);
|
^
| |
|
dns_rdatasetiter_t ** {aka struct dns_rdatasetiter **}
In file included from ../../src/ldap_driver.c:22:
/usr/include/dns/db.h:1162:57: note: expected ‘isc_stdtime_t’ {aka
Bug#1027606: python-resolvelib: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
On Sun, 1 Jan 2023 15:34:12 +0100 Lucas Nussbaum wrote: > Source: python-resolvelib > Version: 0.9.0-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20230101 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. This is a result of the recent upgrade of python-packaging from version 21.3 to 22.0. All tests pass if python3-packaging is downgraded to the old version. There is an unpackaged version 23.0. Tests also fail with that, so this is presumably a deliberate design decision in python-packaging and not a bug. No one appears to have filed an upstream issue with python-resolvelib yet. I'll do that and see what they say. It appears that the Python definition of valid version numbers has gotten more strict. It's not clear what the correct solution is for resolvelib. Scott K signature.asc Description: This is a digitally signed message part.
Bug#1023805: marked as done (guilt: autopkgtest needs update for new version of git: git log --decorate slightly different output)
Your message dated Thu, 12 Jan 2023 13:05:57 +
with message-id
and subject line Bug#1023805: fixed in guilt 0.36-3
has caused the Debian Bug report #1023805,
regarding guilt: autopkgtest needs update for new version of git: git log
--decorate slightly different output
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1023805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guilt
Version: 0.36-2
Severity: serious
X-Debbugs-CC: g...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git
Dear maintainer(s),
With a recent upload of git the autopkgtest of guilt fails in testing
when that autopkgtest is run with the binary packages of git from
unstable. It passes when run with only packages from testing. In tabular
form:
passfail
gitfrom testing1:2.38.1-1
guilt from testing0.36-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of git to testing
[1]. Of course, git shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in git was
intended and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from git should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=git
https://ci.debian.net/data/autopkgtest/testing/amd64/g/guilt/28079229/log.gz
034: --- t-034.out 2022-11-09 20:14:59.570042679 +
+++ /tmp/guilt.log.218772022-11-09 20:15:20.238478229 +
@@ -307,133 +307,133 @@
Applying patch..can-have-embedded-single-slashes.patch
Patch applied.
% git log --decorate
-commit 434e07cacdd8e7eb4723e67cb2d100b3a4121a3a (HEAD -> guilt/master,
refs/patches/master/can-have-embedded-single-slashes.patch)
+commit 434e07cacdd8e7eb4723e67cb2d100b3a4121a3a (HEAD -> guilt/master)
Author: Author Name
Date: Mon Jan 1 00:00:00 2007 +
Can/have/embedded/single/slashes
-commit 7c3ffa4f940c862e9f11f5d4a5ae421f7a8d3141
(refs/patches/master/backslash-is-forbidden.patch)
+commit 7c3ffa4f940c862e9f11f5d4a5ae421f7a8d3141
Author: Author Name
Date: Mon Jan 1 00:00:00 2007 +
Backslash\is\forbidden.
-commit ea46f435d4d8f3c5349dce1aabc1a39fbf7ef803
(refs/patches/master/x.patch)
+commit ea46f435d4d8f3c5349dce1aabc1a39fbf7ef803
Author: Author Name
Date: Mon Jan 1 00:00:00 2007 +
@
-commit a275ed5d7f10ea88c986852ee95a7d5a61663b5f
(refs/patches/master/cannot@have@the@sequence@at-brace.patch)
+commit a275ed5d7f10ea88c986852ee95a7d5a61663b5f
Author: Author Name
Date: Mon Jan 1 00:00:00 2007 +
Cannot@{have@{the@{sequence@{at-brace.
-commit f091fee39457e64ebd35410c1cf95e6613816a54
(refs/patches/master/cannot_end_in_.patch)
+commit f091fee39457e64ebd35410c1cf95e6613816a54
Author: Author Name
Date: Mon Jan 1 00:00:00 2007 +
Cannot end in ..
-commit 025672497aff5c910c8ff86aaedc662f14c2f4ad
(refs/patches/master/cannot-end-in-slash-.patch)
+commit 025672497aff5c910c8ff86aaedc662f14c2f4ad
Author: Author Name
Date: Mon Jan 1 00:00:00 2007 +
Cannot/end/in/slash/
-commit f13e243c7c56f39422567a431bccceec8b789596
(refs/patches/master/multiple-slashes--are--forbidden.patch)
+commit f13e243c7c56f39422567a431bccceec8b789596
Author: Author Name
Date: Mon Jan 1 00:00:00 2007 +
Multiple/slashes//are//forbidden.
-commit edef5e925083d445f71c170d3293fac9619bc7a2
(refs/patches/master/openbracketisforbidden.patch)
+commit edef5e925083d445f71c170d3293fac9619bc7a2
Author: Author Name
Date: Mon Jan 1 00:00:00 2007 +
Open[bracket[is[forbidden.
-commit 1626a11d979a1e9e775c766484172212277153df
(refs/patches/master/asterisk-is-forbidden.patch)
+commit 1626a11d979a1e9e775c766484172212277153df
Author: Author Name
Date: Mon Jan 1 00:00:00 2007 +
Asterisk*is*forbidden.
-commit
Bug#1028533: symfony: FTBFS
Source: symfony Version: 5.4.18+dfsg-2 Severity: serious Tags: ftbfs Justification: ftbfs Dear maintianer(s), Your most recent upload of symfony FTBFS. The test suite fails. Paul https://buildd.debian.org/status/fetch.php?pkg=symfony=all=5.4.18%2Bdfsg-2=1673508040=0
Bug#1021549: marked as pending in maven-artifact-transfer
Control: tag -1 pending Hello, Bug #1021549 in maven-artifact-transfer 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/java-team/maven-artifact-transfer/-/commit/5c4e3c07c5ad2e1e3d6b4a756a3fdacf9795021a Fixed the build failure with Maven 3.8 (Closes: #1021549) (this message was generated automatically) -- Greetings https://bugs.debian.org/1021549
Processed: Bug#1021549 marked as pending in maven-artifact-transfer
Processing control commands: > tag -1 pending Bug #1021549 [src:maven-artifact-transfer] FTBFS: Compilation failure Added tag(s) pending. -- 1021549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027233: marked as done (prody: autopkgtest fail with numpy/1.24.1)
Your message dated Thu, 12 Jan 2023 11:35:32 + with message-id and subject line Bug#1027233: fixed in prody 2.3.1+dfsg-3 has caused the Debian Bug report #1027233, regarding prody: autopkgtest fail with numpy/1.24.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prody Severity: important User: debian-pyt...@lists.debian.org Usertags: numpy1.24 Hello, recently numpy/1.24.1 has been uploaded to experimental, and this package autopkgtest fail when running against it. An overview of the upstream changes in the 1.24.x series is available at: https://numpy.org/doc/stable/release/1.24.0-notes.html Several of the errors are in the form of: AttributeError: module 'numpy' has no attribute 'X' with X in [float, int, bool, object, ...]. This is because, numpy upstream in 1.24.0, finally decided to expire https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases some deprecations introduced in 1.20.0 https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated (released almost 2 years ago). All of those are quite straightforward to fix, since often it's just necessary to stop importing them from numpy and use the python native types. Other changes may requires a bit more rework to be addressed. Currently numpy/1.24.x is in experimental, but given the possible longer support that it'll receive from upstream, we're hopeful to include this in bookworm, so your help is necessary to address this bug ASAP. Regards, Sandro --- End Message --- --- Begin Message --- Source: prody Source-Version: 2.3.1+dfsg-3 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of prody, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated prody package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Jan 2023 06:08:16 -0500 Source: prody Architecture: source Version: 2.3.1+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Andrius Merkys Closes: 1027233 Changes: prody (2.3.1+dfsg-3) unstable; urgency=medium . * Add patch to fix test failure with Numpy 1.24 (Closes: #1027233). Thanks Sebastiaan Couwenberg. Checksums-Sha1: 49c43400e7366edd4ea1b9b6434d943caca0ebea 2235 prody_2.3.1+dfsg-3.dsc b94a7fafa50f2c7000990fe668de3d144ae5c580 5860 prody_2.3.1+dfsg-3.debian.tar.xz a5c9569b362985c793c482e1e8a2b52962df4432 10193 prody_2.3.1+dfsg-3_source.buildinfo Checksums-Sha256: e6ccfbf8325d81e44c6a031edcb2a3ee85b849a4b590a84378de1c1568521a1e 2235 prody_2.3.1+dfsg-3.dsc a91b295381a85cb3e9640ea415a005c3c502c35dfe8199dd68f48dbbeaefe6ca 5860 prody_2.3.1+dfsg-3.debian.tar.xz 3fd8caccb920e884516b7747bde14a8c8ce6dda19e2f69a299ac976777fc491f 10193 prody_2.3.1+dfsg-3_source.buildinfo Files: c88ce761c82f48f1f7b45f6e87b17509 2235 science optional prody_2.3.1+dfsg-3.dsc f5806f680b8388bb8cdacb8bfff508a8 5860 science optional prody_2.3.1+dfsg-3.debian.tar.xz e755787beb062ea332011e7aa9642ac7 10193 science optional prody_2.3.1+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmO/6qISHG1lcmt5c0Bk ZWJpYW4ub3JnAAoJEOX0P5wnNPKHgcEQAIbaiz0+LVaoMqZpJO7TCuDgDcY8ToGn TwYgNxwJZT2dcXQ+p9yU5CMCoFFV6kFPoVxB9X8cVpV45qNnQkUZvTbXnqptwohz Hfc5ncZHlh5Vx2OVeTG0v8o6/VZCRL3tfQHPXGrepoBSGY45HFDPWlcFTSl/g7TT HPO9FCt7z+KHdT8Ghf/ixuE/Osv+62Ou6XjNlVIc1cRBHJUDCDAPKhGMjCzCL5eZ oSMZTXmYD4Ot3dmvNpLcJdjw2kZ2MTWlvQHXw4LrimJIMb9TJ9UxO6dQC4XMzSZH prMp6SIuwWKm3/JUiX8Nn87Rp6Fy9WgRqn3oobnRw3ql2Js4NzLAjPapYSxDhTuy jGZ+xKWI/fzgQnn5DeDYuYcTCwe+CeSaTXiAACDFlhytgzJGMgS6Xuq3VMMg9tuG 4wMDi6T8wOyNHNX1WvVS7WCtVRs6g7VdbaGlILXvazhBzQoFPa3oqJj8TQ2s4BRh 7Eow3/pOXOTuS2b8F5rek4je+VFMzM9/XFSyt4m8Ox4XwaP+wwPupbcutV3PD/Id sGZK/fq5c8IrjVf1iT5Iku5hL76qkaAnp3VQ6xgVUY9z0SEvBgNmqJir1ymWRzX2
Bug#1028451: 2nd DisplayPort doesn't get video
Source: linux Followup-For: Bug #1028451 Fwiw there is a general regression with AMDGPU MST on linux 6.1; tracked upstream here: https://gitlab.freedesktop.org/drm/amd/-/issues/2171 As the original report was about a second displayport on a docking station I would guess it's the same issue. For reference i'm hit by the same issue due to using MST for daisy-chaining monitors. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf, arm64 Kernel: Linux 6.0.0-6-amd64 (SMP w/32 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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
Bug#1028527: i2masschroq: FTBFS in local pbuilder
Source: i2masschroq Version: 0.4.54-1 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, I've observerd that the package is currently not built for sid. It is in state "Dep-Wait (libodsstream-dev (>= 0.9.1-2.1))", so to investiate the reason I've tried to locally build it in a sid pbuilder env. It fails with CMake Error at /usr/lib/x86_64-linux-gnu/cmake/QCustomPlot/QCustomPlotTargets.cmake:71 (set_target_properties): The link interface of target "QCustomPlot::QCustomPlot" contains: Qt5::Widgets but the target was not found. Possible reasons include: * There is a typo in the target name. * A find_package call is missing for an IMPORTED target. * An ALIAS target is missing. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/QCustomPlot/QCustomPlotConfig.cmake:37 (include) CMakeStuff/toolchains/unix-toolchain.cmake:23 (find_package) CMakeLists.txt:118 (include) CMake Error at /usr/lib/x86_64-linux-gnu/cmake/odsstream/OdsStreamTargets.cmake:71 (set_target_properties): The link interface of target "OdsStream::Core" contains: Qt6::Xml but the target was not found. Possible reasons include: * There is a typo in the target name. * A find_package call is missing for an IMPORTED target. * An ALIAS target is missing. Interestingly, it seems to mix Qt5 with Qt6… That looks weird. (It seems to be *possible* to do so, but it is not officially supported, according to [1]) Said that, it might be that this bug is either in libqcustomplot or libodsstream or both… Please reassign if you think so… [1] https://doc.qt.io/qt-6/cmake-qt5-and-qt6-compatibility.html#mixing-qt-5-and-qt-6 -- tobi
Bug#1027912: marked as done (golang-go.uber-atomic: FTBFS in bookworm (undeclared build-dependency on tzdata))
Your message dated Thu, 12 Jan 2023 11:19:17 + with message-id and subject line Bug#1027912: fixed in golang-go.uber-atomic 1.10.0-2 has caused the Debian Bug report #1027912, regarding golang-go.uber-atomic: FTBFS in bookworm (undeclared build-dependency on tzdata) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:golang-go.uber-atomic Version: 1.10.0-1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep dh binary-indep --buildsystem=golang dh_update_autotools_config -i -O--buildsystem=golang dh_autoreconf -i -O--buildsystem=golang dh_auto_configure -i -O--buildsystem=golang dh_auto_build -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 go.uber.org/atomic go.uber.org/atomic/internal/gen-atomicint go.uber.org/atomic/internal/gen-atomicwrapper internal/goarch internal/unsafeheader internal/abi internal/cpu internal/bytealg internal/goexperiment internal/goos runtime/internal/atomic runtime/internal/math runtime/internal/sys runtime/internal/syscall runtime internal/reflectlite errors internal/race sync/atomic sync io unicode unicode/utf8 bytes encoding math/bits math internal/itoa strconv reflect encoding/binary encoding/base64 sort internal/fmtsort internal/oserror syscall internal/syscall/unix time internal/poll internal/syscall/execenv internal/testlog path io/fs os fmt strings unicode/utf16 encoding/json go.uber.org/atomic flag go/token path/filepath go/scanner go/ast go/internal/typeparams go/parser go/build/constraint go/doc/comment text/tabwriter go/printer go/format log net/url text/template/parse text/template go.uber.org/atomic/internal/gen-atomicint go.uber.org/atomic/internal/gen-atomicwrapper dh_auto_test -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 go.uber.org/atomic go.uber.org/atomic/internal/gen-atomicint go.uber.org/atomic/internal/gen-atomicwrapper === RUN TestBool === RUN TestBool/JSON/Marshal === RUN TestBool/JSON/Unmarshal === RUN TestBool/JSON/Unmarshal/Error === RUN TestBool/String === RUN TestBool/String/true === RUN TestBool/String/false --- PASS: TestBool (0.00s) --- PASS: TestBool/JSON/Marshal (0.00s) --- PASS: TestBool/JSON/Unmarshal (0.00s) --- PASS: TestBool/JSON/Unmarshal/Error (0.00s) --- PASS: TestBool/String (0.00s) --- PASS: TestBool/String/true (0.00s) --- PASS: TestBool/String/false (0.00s) === RUN TestDuration === RUN TestDuration/JSON/Marshal === RUN TestDuration/JSON/Unmarshal === RUN TestDuration/JSON/Unmarshal/Error === RUN TestDuration/String --- PASS: TestDuration (0.00s) --- PASS: TestDuration/JSON/Marshal (0.00s) --- PASS: TestDuration/JSON/Unmarshal (0.00s) --- PASS: TestDuration/JSON/Unmarshal/Error (0.00s) --- PASS: TestDuration/String (0.00s) === RUN TestErrorByValue --- PASS: TestErrorByValue (0.00s) === RUN TestNewErrorWithNilArgument --- PASS: TestNewErrorWithNilArgument (0.00s) === RUN TestErrorCanStoreNil --- PASS: TestErrorCanStoreNil (0.00s) === RUN TestNewErrorWithError --- PASS: TestNewErrorWithError (0.00s) === RUN TestErrorSwap --- PASS: TestErrorSwap (0.00s) === RUN TestErrorCompareAndSwap --- PASS: TestErrorCompareAndSwap (0.00s) === RUN TestFloat32 === RUN TestFloat32/JSON/Marshal === RUN TestFloat32/JSON/Unmarshal === RUN TestFloat32/JSON/Unmarshal/Error === RUN TestFloat32/String --- PASS: TestFloat32 (0.00s) --- PASS: TestFloat32/JSON/Marshal (0.00s) --- PASS: TestFloat32/JSON/Unmarshal (0.00s) --- PASS: TestFloat32/JSON/Unmarshal/Error (0.00s) --- PASS: TestFloat32/String (0.00s) === RUN TestFloat64 === RUN TestFloat64/JSON/Marshal === RUN TestFloat64/JSON/Unmarshal === RUN TestFloat64/JSON/Unmarshal/Error === RUN TestFloat64/String --- PASS: TestFloat64 (0.00s) --- PASS: TestFloat64/JSON/Marshal (0.00s) --- PASS: TestFloat64/JSON/Unmarshal (0.00s) --- PASS: TestFloat64/JSON/Unmarshal/Error (0.00s) --- PASS: TestFloat64/String (0.00s) === RUN TestInt32 === RUN TestInt32/JSON/Marshal === RUN TestInt32/JSON/Unmarshal === RUN TestInt32/JSON/Unmarshal/Error === RUN TestInt32/String === RUN TestInt32/String/positive === RUN TestInt32/String/negative ---
Processed: Bug#1027912 marked as pending in golang-go.uber-atomic
Processing control commands: > tag -1 pending Bug #1027912 [src:golang-go.uber-atomic] golang-go.uber-atomic: FTBFS in bookworm (undeclared build-dependency on tzdata) Added tag(s) pending. -- 1027912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027912: marked as pending in golang-go.uber-atomic
Control: tag -1 pending Hello, Bug #1027912 in golang-go.uber-atomic 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/go-team/packages/golang-go.uber-atomic/-/commit/f995364b842cdb125d5f02aeb45b8f04a4887faa Add tzdata to Build-Depends (Closes: #1027912) (this message was generated automatically) -- Greetings https://bugs.debian.org/1027912
Processed: retitle 1023030 to pysha3: CVE-2022-37454, fixed 995961 in 2.4.53-1, notfixed 844351 in 2.4.40 ...
Processing commands for cont...@bugs.debian.org:
> retitle 1023030 pysha3: CVE-2022-37454
Bug #1023030 {Done: Ben Finney } [src:pysha3] pysha3:
Affected by CVE-2022-37454, unmaintained, remove from Debian?
Changed Bug title to 'pysha3: CVE-2022-37454' from 'pysha3: Affected by
CVE-2022-37454, unmaintained, remove from Debian?'.
> fixed 995961 2.4.53-1
Bug #995961 {Done: Hendrik Jäger } [apache2]
libapache2-mpm-itk: Error "AH00052: child pid exit signal Segmentation fault"
after update to apache 2.4.51-1~deb11u1
Marked as fixed in versions apache2/2.4.53-1.
> notfixed 844351 2.4.40
Bug #844351 {Done: Hendrik Jäger } [apache2]
apache2: as a reverse proxy, a 100 continue response is sent prematurely when
request contains expects continue
There is no source info for the package 'apache2' at version '2.4.40' with
architecture ''
Unable to make a source version for version '2.4.40'
No longer marked as fixed in versions 2.4.40.
> fixed 844351 2.4.41-1
Bug #844351 {Done: Hendrik Jäger } [apache2]
apache2: as a reverse proxy, a 100 continue response is sent prematurely when
request contains expects continue
Marked as fixed in versions apache2/2.4.41-1.
> tags 1028514 + sid bookworm
Bug #1028514 [apper] apper depends on the removed software-properties-kde
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1023030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023030
1028514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028514
844351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844351
995961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1027679: qtimageformats-opensource-src: FTBFS with tiff 4.5.0+
Hi László! On Sun, Jan 01, 2023 at 08:20:00PM +0100, László Böszörményi wrote: > Hi, > > Your package fails to build with the new major tiff release. During > self-testing two tiff RGB tests fail, I think maybe due to broken > images. Fixing it is easy, just disable those two tests, patch is > attached. I don't think disabling the tests is the right fix. It looks like this test uncovered a real bug in libtiff, which is described here: https://gitlab.com/libtiff/libtiff/-/issues/505 -- Dmitry Shachnev signature.asc Description: PGP signature
Processed (with 1 error): Re: Bug#885563: vte: Do not release with trixie
Processing control commands: > retitle -1 vte: Do not release with trixie Bug #885563 [src:vte] vte: Do not release with bookworm Changed Bug title to 'vte: Do not release with trixie' from 'vte: Do not release with bookworm'. > tags -1 = trixie forky sid Unknown tag/s: forky. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore. Bug #885563 [src:vte] vte: Do not release with trixie Added tag(s) trixie; removed tag(s) bookworm. -- 885563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#885563: vte: Do not release with trixie
Control: retitle -1 vte: Do not release with trixie Control: tags -1 = trixie forky sid On Sun, 23 Dec 2018 at 08:55:05 -0500, Jeremy Bicha wrote: > The only thing using the old vte in Debian is cdebconf-terminal. But > since that's a critical package that hasn't been converted yet, let's > defer vte's removal until Bullseye. The transition/toolchain freeze for bookworm is today, so it's clearly too late to port d-i to GTK 3 for bookworm, and we are stuck with vte for another cycle. smcv
Bug#1028510: marked as done (crmsh: Fails with python3.11)
Your message dated Thu, 12 Jan 2023 10:07:08 +0100 with message-id <0b063819-5ee3-c7af-7b64-5d2d856f3...@xs4all.nl> and subject line Re: crmsh: Fails with python3.11 has caused the Debian Bug report #1028510, regarding crmsh: Fails with python3.11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1028510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: crmsh Version: 4.4.0-3 Severity: serious Tags: upstream patch Dear Maintainer, Your package fails with python3.11: autopkgtest [17:21:55]: test pacemaker-node-status.sh: [--- + DAEMON_TIMEOUT=60 + CRM_TIMEOUT=5 + ulimit -H -l unlimited + service corosync start + service pacemaker start + sleep 60 + crm_node -n + NODE=node1 + [ -z node1 ] + getent hosts node1 + echo 127.0.0.1 node1 + crm status + grep Online:.*node1 Traceback (most recent call last): File "/usr/sbin/crm", line 35, in from crmsh import main File "/usr/lib/python3/dist-packages/crmsh/main.py", line 17, in from . import ui_root File "/usr/lib/python3/dist-packages/crmsh/ui_root.py", line 201, in Root.init_ui() File "/usr/lib/python3/dist-packages/crmsh/command.py", line 503, in init_ui prepare(children, child, aliases) File "/usr/lib/python3/dist-packages/crmsh/command.py", line 488, in prepare info = ChildInfo(child, cls) ^ File "/usr/lib/python3/dist-packages/crmsh/command.py", line 558, in __init__ self.children = self.level.init_ui() File "/usr/lib/python3/dist-packages/crmsh/command.py", line 503, in init_ui prepare(children, child, aliases) File "/usr/lib/python3/dist-packages/crmsh/command.py", line 488, in prepare info = ChildInfo(child, cls) ^ File "/usr/lib/python3/dist-packages/crmsh/command.py", line 558, in __init__ self.children = self.level.init_ui() File "/usr/lib/python3/dist-packages/crmsh/command.py", line 503, in init_ui prepare(children, child, aliases) File "/usr/lib/python3/dist-packages/crmsh/command.py", line 494, in prepare add_help(info) File "/usr/lib/python3/dist-packages/crmsh/command.py", line 476, in add_help ui_utils.pretty_arguments(info.function, nskip=2)), ^ File "/usr/lib/python3/dist-packages/crmsh/ui_utils.py", line 116, in pretty_arguments specs = inspect.getargspec(f) ^^ AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 'getargs'? autopkgtest [17:22:56]: test pacemaker-node-status.sh: ---] autopkgtest [17:22:57]: test pacemaker-node-status.sh: - - - - - - - - - - results - - - - - - - - - - pacemaker-node-status.sh FAIL non-zero exit status 1 The attached patch resolves the issue by using inspect.getfullargspec() instead. Kind Regards, Bas diff -Nru crmsh-4.4.0/debian/changelog crmsh-4.4.0/debian/changelog --- crmsh-4.4.0/debian/changelog2022-11-13 13:18:35.0 +0100 +++ crmsh-4.4.0/debian/changelog2023-01-12 07:13:14.0 +0100 @@ -1,3 +1,10 @@ +crmsh (4.4.0-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add patch to not use inspect.getargspec, removed from python3.11. + + -- Bas Couwenberg Thu, 12 Jan 2023 07:13:14 +0100 + crmsh (4.4.0-3) unstable; urgency=medium * d/patches: fix crmadmin parsing (Closes: #1023824) diff -Nru crmsh-4.4.0/debian/patches/getargspec.patch crmsh-4.4.0/debian/patches/getargspec.patch --- crmsh-4.4.0/debian/patches/getargspec.patch 1970-01-01 01:00:00.0 +0100 +++ crmsh-4.4.0/debian/patches/getargspec.patch 2023-01-12 07:13:14.0 +0100 @@ -0,0 +1,24 @@ +Description: Don't use inspect.getargspec, removed in Python 3.11. +Author: Bas Couwenberg +Forwarded: https://github.com/ClusterLabs/crmsh/pull/1112 + +--- a/crmsh/ui_utils.py b/crmsh/ui_utils.py +@@ -113,7 +113,7 @@ def pretty_arguments(f, nskip=0): + Returns a prettified representation + of the command arguments + ''' +-specs = inspect.getargspec(f) ++specs = inspect.getfullargspec(f) + named_args = [] + if specs.defaults is None: + named_args += specs.args +@@ -140,7 +140,7 @@ def validate_arguments(f, args, nskip=0) + + Note: Does not support keyword arguments. + ''' +-specs = inspect.getargspec(f) ++specs = inspect.getfullargspec(f)
Processed: Re: crmsh: Fails with python3.11
Processing commands for cont...@bugs.debian.org: > fixed 1028510 crmsh/4.4.0-4 Bug #1028510 [src:crmsh] crmsh: Fails with python3.11 The source crmsh and version 4.4.0-4 do not appear to match any binary packages Marked as fixed in versions crmsh/4.4.0-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 1028510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: crmsh: Fails with python3.11
Processing control commands: > tags -1 pending Bug #1028510 [src:crmsh] crmsh: Fails with python3.11 Added tag(s) pending. -- 1028510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028510: crmsh: Fails with python3.11
Control: tags -1 pending On 1/12/23 07:37, Bas Couwenberg wrote: The attached patch resolves the issue by using inspect.getfullargspec() instead. The patch has been applied in git. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1027219: marked as done (python-skbio: autopkgtest fail with numpy/1.24.1)
Your message dated Thu, 12 Jan 2023 08:58:10 +0100 with message-id and subject line Closing: python-skbio: autopkgtest fail with numpy/1.24.1 has caused the Debian Bug report #1027219, regarding python-skbio: autopkgtest fail with numpy/1.24.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-skbio Severity: important User: debian-pyt...@lists.debian.org Usertags: numpy1.24 Hello, recently numpy/1.24.1 has been uploaded to experimental, and this package autopkgtest fail when running against it. An overview of the upstream changes in the 1.24.x series is available at: https://numpy.org/doc/stable/release/1.24.0-notes.html Several of the errors are in the form of: AttributeError: module 'numpy' has no attribute 'X' with X in [float, int, bool, object, ...]. This is because, numpy upstream in 1.24.0, finally decided to expire https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases some deprecations introduced in 1.20.0 https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated (released almost 2 years ago). All of those are quite straightforward to fix, since often it's just necessary to stop importing them from numpy and use the python native types. Other changes may requires a bit more rework to be addressed. Currently numpy/1.24.x is in experimental, but given the possible longer support that it'll receive from upstream, we're hopeful to include this in bookworm, so your help is necessary to address this bug ASAP. Regards, Sandro --- End Message --- --- Begin Message --- With the upload of the new version 0.5.8-1 all tests are passing thus closing this bug. Kind regards Andreas. -- http://fam-tille.de--- End Message ---
