Bug#1038450: patch probably available
Le mercredi 21 juin 2023 à 22:56 +0200, Adrien Nader a écrit : > On Wed, Jun 21, 2023, julien.pu...@gmail.com wrote: > > Le mardi 20 juin 2023 à 22:38 +0200, Adrien Nader a écrit : > > > > > > > > > The patch seems to fix the issue. I say "seem" because the build > > > compiled the file that was failing to build but the build is not > > > done > > > yet: emulated armhf isn't fast. :) > > > > > > But since I reprocued the build failure before, I am fairly > > > confident > > > this build will succeed. > > > > I took the commit and added it to the Debian packaging ; I now have > > a > > 20230420-4 almost ready for upload. > > > > I'm waiting for two feedbacks before I do so : > > > > 1. yours so I trust it fixes the 32-bit issue ; > > > > 2. the sbuild I started on my box to check the patch on more usual > > architectures. > > > > Thanks for your help! > > My build just finished. It only took 27 hours. It failed at the > lintian step but that was due to network issues. Uploaded, thanks again! J
Bug#1038860: trafficserver: Wrong version for trafficserver security-update in DSA-5435-1
Source: trafficserver Version: 9.2.0+ds-1~deb12u1 Severity: serious Justification: wrong version number, does not allow updates to fixed version X-Debbugs-Cc: car...@debian.org,t...@security.debian.org Control: affects -1 + security.debian.org,release.debian.org Hi The update for trafficserver in DSA-5435-1 for bookworm, while sourcewise built on top of 9.2.0+ds-2, has an odd version going backwards, 9.2.0+ds-1~deb12u1. This should bee 9.2.0+ds-2+deb12u1 instead (as the patches are applied on top of 9.2.0+ds-2). Currently it's not possible to install the security update as $ dpkg --compare-versions 9.2.0+ds-1~deb12u1 gt 9.2.0+ds-2 $ echo $? 1 Regards, Salvatore
Processed: trafficserver: Wrong version for trafficserver security-update in DSA-5435-1
Processing control commands: > affects -1 + security.debian.org,release.debian.org Bug #1038860 [src:trafficserver] trafficserver: Wrong version for trafficserver security-update in DSA-5435-1 Added indication that 1038860 affects security.debian.org and release.debian.org -- 1038860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038676: marked as done (rocsparse: binary-all FTBFS)
Your message dated Thu, 22 Jun 2023 04:49:09 + with message-id and subject line Bug#1038676: fixed in rocsparse 5.3.0+dfsg-7 has caused the Debian Bug report #1038676, regarding rocsparse: binary-all FTBFS 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.) -- 1038676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rocsparse Version: 5.3.0+dfsg-6 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=rocsparse=all=5.3.0%2Bdfsg-6=1686900579=0 ... debian/rules execute_before_dh_install make[1]: Entering directory '/<>' # Note the rpath field setting may cause reproducible build issues. # This should be removed earlier in the toolchain if possible. patchelf --remove-rpath ./debian/tmp/usr/lib/x86_64-linux-gnu/librocsparse.so.0.1 patchelf: getting info about './debian/tmp/usr/lib/x86_64-linux-gnu/librocsparse.so.0.1': No such file or directory make[1]: *** [debian/rules:37: execute_before_dh_install] Error 1 --- End Message --- --- Begin Message --- Source: rocsparse Source-Version: 5.3.0+dfsg-7 Done: Cordell Bloor We believe that the bug you reported is fixed in the latest version of rocsparse, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cordell Bloor (supplier of updated rocsparse 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: Tue, 20 Jun 2023 00:05:33 -0600 Source: rocsparse Architecture: source Version: 5.3.0+dfsg-7 Distribution: unstable Urgency: medium Maintainer: Debian ROCm Team Changed-By: Cordell Bloor Closes: 1038676 Changes: rocsparse (5.3.0+dfsg-7) unstable; urgency=medium . * Split additional arch-specific and arch-independent build steps to fix binary-all FTBFS. (Closes: #1038676) Checksums-Sha1: 8dabcb9667193cc137707d49e1a9b63c0c62aee7 2894 rocsparse_5.3.0+dfsg-7.dsc bd2ca4194f4b3940af2c2cb1f2dc736c20b40429 13880 rocsparse_5.3.0+dfsg-7.debian.tar.xz dbfff90b2387562da649f40e0c97b8d7505d47c8 8246 rocsparse_5.3.0+dfsg-7_source.buildinfo Checksums-Sha256: 0d135f492142f158d7499c349b6f699853de30428b073c4ab51ca1b1ecdccbb8 2894 rocsparse_5.3.0+dfsg-7.dsc 0a29a0cae512a22abfdb04303ae406b5b0f0f84bc97bbe132d9fa7f1e8112229 13880 rocsparse_5.3.0+dfsg-7.debian.tar.xz 3319e612a1b35c663a11ee422d02497fe4db576eaa1f012965a4fdbfddc3748b 8246 rocsparse_5.3.0+dfsg-7_source.buildinfo Files: 13c6800664a9e41b8a3fd60bb3dea63f 2894 devel optional rocsparse_5.3.0+dfsg-7.dsc b5dede88168a7d9a9623eb22c5f30aa8 13880 devel optional rocsparse_5.3.0+dfsg-7.debian.tar.xz 21a99e97500616305be5b7a159831f17 8246 devel optional rocsparse_5.3.0+dfsg-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEDOBv45KqSPjSLkRx+e+O4MAhYw8FAmSTzLEPHGNnbWJAc2xl cnAueHl6AAoJEPnvjuDAIWMPVFMP/18RElO2VDcfhG3zcJzGxKlBm+1oeebEbTVr XDRM0ONwfU/pVaUY4PVRnFmdco74EMvadiQiiKftH/i1CVam0CcKk9y60ErBNwk8 ML2iKXVPpT/8Gty+8CmHT0iUPmS4NDJQtXxeCc7t0WCuDKoHbs2pW8j2TsWelXUp QRAOUjJKAfmCiPU3IMbJt4OcYd+IDfvmujHtj7MJJRFS3YUxuH4UxJCRg6lQT2lO VMHR8HorX+0oxxwDMR15KJu0IyhZwDU7VZ4VKAor/txznnvmzVRs0ZYhL9pmVX73 I+2N6TeHjWZCO1wDTXbxEopvBqO1gFWtN9usZlMBr0mURDPWbaU3/helo8csnE6E pV8ywYuXe9vOpeOU+KgD84SHpDd0dgTbAkpp3oRyRP9bYwDLKbKH81zXoQt6iGyE 83Q1AUx5G1iQtID1JpqLwDcXT16romb5W1/jp/v2WpH0Ojc8pTFXyiDW/WhoRQ81 hCT8fC3hi9+AyTbf+yWcLjmZVdFwEOTvRcVvlUgYmWWC4CCUi+9zBhSVo1U7luT5 Kj2GoJNRnxnyyqyHOkQP2YreSK0meB2jq/d0FSyWHrd/0BYoJeDYCHUPznzJEzvW kvWdnN0ORhUIgTzvsxjfWkYSO274X3DtSgcaH5x9vwDlWLmAtydm7nvM3oxJ/aZ6 DdYEpkqE =q7kt -END PGP SIGNATURE End Message ---
Processed: fixed 1038723 in 0.4.0-2
Processing commands for cont...@bugs.debian.org:
> fixed 1038723 0.4.0-2
Bug #1038723 {Done: Petter Reinholdtsen } [src:tiktoken]
tiktoken FTBFS: error: failed to select a version for the requirement `pyo3 =
"^0.17.3"`
Marked as fixed in versions tiktoken/0.4.0-2; no longer marked as fixed in
versions 0.4.0-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1038723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
I tested with the nouveau driver and it worked. Maybe there is something between 1.26 and 1.32 that conflicts with nvidia driver. And it is also similar to #996503 which affects sddm and it worked too with nouveau. I tried to fix this by removing some module options from https://forums.developer.nvidia.com/t/display-manager-sddm-lightdm-not-starting-with-nvidia-driver/243992 but it had no effect. Maybe forwarding this to nvidia-driver should get some hints about this issue. Regards, Adilson Em qua., 21 de jun. de 2023 às 15:23, Yves-Alexis Perez escreveu: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Wed, 2023-06-21 at 09:40 -0300, Adilson dos Santos Dantas wrote: > > These messages are when I stop lightdm. > > Ah ok. > > > > > > > > > Also is there something peculiar about your hardware (Nvidia/AMD GPU > for > > > example?) or software (specific configuration or something). > > > > > > I'm using Nvidia GPU: > > > > 01:00.0 VGA compatible controller: NVIDIA Corporation TU117 [GeForce GTX > > 1650] (rev a1) > > > > And it is using its official drivers: > > > > dpkg -l xserver-xorg > > Desired=Unknown/Install/Remove/Purge/Hold > > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- > > pend > > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > > ||/ Nome Versão Arquitectura Descrição > > +++-==--- > > = > > ii xserver-xorg 1:7.7+23 amd64X.Org X server > > > > dpkg -l xserver-xorg-video-nvidia > > Desired=Unknown/Install/Remove/Purge/Hold > > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- > > pend > > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > > ||/ Nome Versão Arquitectura Descrição > > +++-=--- > > = > > ii xserver-xorg-video-nvidia 530.41.03-1 amd64NVIDIA binary > Xorg > > driver > > Yup, that's likely related. Honestly we (I) don't really support > binary/proprietary drivers. It'd help if you could test with free drivers > (nouveau or something maybe). > > Regards, > - -- > Yves-Alexis > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSTQAAACgkQ3rYcyPpX > RFu7Ggf9FCsjsiXteQ+xDSolGEtK2a9eBlnCnI9MY3wY2OdOHJlNCpbEjamWVbw3 > CwEn4//IWPgFmLcKBD1A9ySYein2tY3CDdNH5fii7ZZ/MNAlL1vuKAVuV30ayQtU > V/4xxQXgJ+1JUCPzzKNGMdLs/yumAiLGAs3XzhjUmjVPQWMRWanCOf8dFavDyFG3 > 4sPS6niMeFUWqM17K0ja7VPVj2QbQQSe34jec93W+zcbnxbWZZuJY9nQ2PsQjRDd > /FY0fBQtzopnZMBgRUdYNj09QGuI8kn6dZdD93+/MS2uP95ES7v1nG0bKARrGor7 > pNaWlBMeMGI/+bL89SFEQdR52n/uFw== > =tTX8 > -END PGP SIGNATURE- > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 1038752 pending Bug #1038752 [libjodycode2] libjodycode2: A shared library package cannot be a transitional package on a different soversion Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 1038752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion
Em qua., 21 de jun. de 2023 às 23:58, Jody Bruchon escreveu: > > Thanks for all that information! While I'm here, I should also point out > that another Debian package will eventually have to adopt libjodycode as > well: winregfs [1]. Fortunately it doesn't use any of the APIs that > changed between libjodycode 2 and 3 so changing what it needs to link to > is as simple as recompiling and pointing it to the correct libjodycode.h > header. > > [1] https://packages.debian.org/sid/utils/winregfs Thanks again Jody. The winregfs is maintained by my close friend Giovani. I am ending the revision libjodycode_3.0.1-3. > On 2023-06-21 10:14 PM, Eriberto wrote: > > Hi Jody! > > > > Em qua., 21 de jun. de 2023 às 21:09, Tritech - Jody > > escreveu: > >> Hi! I'm upstream. Would it be helpful if I provided a way to build a > >> compatibility shim libjodycode.so.2 with the old API 2 interfaces that > >> translates and links to the API 3 version? I'd be happy to provide that if > >> desired. > > I think this is not needed because all these new packages don't > > arrived to Debian Testing yet. The jdupes 1.25.0 already killed the > > 1.24.0, so libjodycode2 is no longer useful for Debian. I will follow > > the changes purposed by Adrian. I will start changing the packaging of > > the lib. Furthermore, I was wrong when making a -dev package with > > soname number attached. It was a mistake. The changes will make the > > lib arrives to NEW queue again. > > > > Thanks a lot Adrian and Jody. > > > > Cheers, > > > > Eriberto >
Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion
Thanks for all that information! While I'm here, I should also point out that another Debian package will eventually have to adopt libjodycode as well: winregfs [1]. Fortunately it doesn't use any of the APIs that changed between libjodycode 2 and 3 so changing what it needs to link to is as simple as recompiling and pointing it to the correct libjodycode.h header. [1] https://packages.debian.org/sid/utils/winregfs On 2023-06-21 10:14 PM, Eriberto wrote: Hi Jody! Em qua., 21 de jun. de 2023 às 21:09, Tritech - Jody escreveu: Hi! I'm upstream. Would it be helpful if I provided a way to build a compatibility shim libjodycode.so.2 with the old API 2 interfaces that translates and links to the API 3 version? I'd be happy to provide that if desired. I think this is not needed because all these new packages don't arrived to Debian Testing yet. The jdupes 1.25.0 already killed the 1.24.0, so libjodycode2 is no longer useful for Debian. I will follow the changes purposed by Adrian. I will start changing the packaging of the lib. Furthermore, I was wrong when making a -dev package with soname number attached. It was a mistake. The changes will make the lib arrives to NEW queue again. Thanks a lot Adrian and Jody. Cheers, Eriberto
Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion
Hi Jody! Em qua., 21 de jun. de 2023 às 21:09, Tritech - Jody escreveu: > > Hi! I'm upstream. Would it be helpful if I provided a way to build a > compatibility shim libjodycode.so.2 with the old API 2 interfaces that > translates and links to the API 3 version? I'd be happy to provide that if > desired. I think this is not needed because all these new packages don't arrived to Debian Testing yet. The jdupes 1.25.0 already killed the 1.24.0, so libjodycode2 is no longer useful for Debian. I will follow the changes purposed by Adrian. I will start changing the packaging of the lib. Furthermore, I was wrong when making a -dev package with soname number attached. It was a mistake. The changes will make the lib arrives to NEW queue again. Thanks a lot Adrian and Jody. Cheers, Eriberto
Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion
Hi! I'm upstream. Would it be helpful if I provided a way to build a compatibility shim libjodycode.so.2 with the old API 2 interfaces that translates and links to the API 3 version? I'd be happy to provide that if desired. Jody Bruchon
Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion
Apologies, I sent my last email from the wrong account. j...@jodybruchon.com is the correct account if replying directly. Thanks! On June 21, 2023 7:54:54 PM EDT, Tritech - Jody wrote:
Bug#1038823: marked as done (pysdl2: autopkgtest failure with SDL 2.28.0: cannot create a Renderer)
Your message dated Wed, 21 Jun 2023 21:21:39 + with message-id and subject line Bug#1038823: fixed in pysdl2 0.9.15+dfsg-2 has caused the Debian Bug report #1038823, regarding pysdl2: autopkgtest failure with SDL 2.28.0: cannot create a Renderer 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.) -- 1038823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pysdl2 Version: 0.9.9+dfsg1-6 Severity: serious Tags: fixed-upstream Justification: https://release.debian.org/testing/rc_policy.txt 6a X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: needs-update pysdl2's autopkgtest is failing since I uploaded libsdl2 version 2.28.0 to unstable. This appears to be a test issue, rather than a regression in libsdl2. An example of one of the failures: 70s self = 70s 70s def test_SDL_CreateDestroyRenderer(self): 70s failed = 0 70s rcount = render.SDL_GetNumRenderDrivers() 70s for i in range(rcount): 70s window = video.SDL_CreateWindow(b"Test", 10, 10, 10, 10, 70s video.SDL_WINDOW_SHOWN) 70s assert isinstance(window.contents, video.SDL_Window) 70s renderer = render.SDL_CreateRenderer(window, i, self._RENDERFLAGS) 70s if not (renderer and renderer.contents): 70s failed += 1 70s video.SDL_DestroyWindow(window) 70s continue 70s assert isinstance(renderer.contents, render.SDL_Renderer) 70s render.SDL_DestroyRenderer(renderer) 70s 70s # TODO: using -1 as index for the call below leads to random 70s # access violations on Win32 70s renderer = render.SDL_CreateRenderer(window, i, 70s render.SDL_RENDERER_SOFTWARE) 70s > assert isinstance(renderer.contents, render.SDL_Renderer) 70s E ValueError: NULL pointer access If I hack in some extra debug, it seems that the SDL error message is "Surface already associated with window", which is related to: - https://github.com/pygame-community/pygame-ce/issues/2190 - https://github.com/libsdl-org/SDL/issues/7793 - https://github.com/libsdl-org/SDL/pull/7795 Briefly, SDL upstream considers it to be a programming error to attempt to create a Renderer for a window that already has a window surface, and some video drivers imply creation of a window surface. SDL 2.28.0 is better at detecting and diagnosing this situation than previous releases. pysdl2/experimental seems to have fixed the test, so I'm going to upload that to unstable if successful. smcv --- End Message --- --- Begin Message --- Source: pysdl2 Source-Version: 0.9.15+dfsg-2 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of pysdl2, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated pysdl2 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: Wed, 21 Jun 2023 21:29:18 +0100 Source: pysdl2 Architecture: source Version: 0.9.15+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Simon McVittie Closes: 1031412 1038823 Changes: pysdl2 (0.9.15+dfsg-2) unstable; urgency=medium . * Team upload * d/p/tests-Don-t-try-to-create-more-than-one-Renderer-for-the-.patch: Add patch fixing test failure with SDL 2.28 (Closes: #1038823) * d/p/Make-the-build-reproducible.patch: Add patch from Chris Lamb to make the documentation reproducible (Closes: #1031412) * Add Lintian override to ignore a use of distutils in upstream CI scripts. We don't use these in Debian, so they aren't relevant for reducing our dependence on distutils. * Upload to unstable . pysdl2 (0.9.15+dfsg-1) experimental; urgency=medium . * Team upload * New upstream release *
Bug#1038450: patch probably available
On Wed, Jun 21, 2023, julien.pu...@gmail.com wrote: > Le mardi 20 juin 2023 à 22:38 +0200, Adrien Nader a écrit : > > > > > > The patch seems to fix the issue. I say "seem" because the build > > compiled the file that was failing to build but the build is not done > > yet: emulated armhf isn't fast. :) > > > > But since I reprocued the build failure before, I am fairly confident > > this build will succeed. > > I took the commit and added it to the Debian packaging ; I now have a > 20230420-4 almost ready for upload. > > I'm waiting for two feedbacks before I do so : > > 1. yours so I trust it fixes the 32-bit issue ; > > 2. the sbuild I started on my box to check the patch on more usual > architectures. > > Thanks for your help! My build just finished. It only took 27 hours. It failed at the lintian step but that was due to network issues.
Bug#1038759: marked as done (console-setup: Build against xkb-data 2.38-2 needed)
Your message dated Wed, 21 Jun 2023 20:53:07 + with message-id and subject line Bug#1038759: fixed in console-setup 1.222 has caused the Debian Bug report #1038759, regarding console-setup: Build against xkb-data 2.38-2 needed 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.) -- 1038759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:console-setup Version: 1.221 Severity: important X-Debbugs-Cc: debia...@lists.debian.org, gunna...@debian.org Control: affects -1 src:xkeyboard-config Dear maintainers, xkeyboard-config 2.38-2 was recently uploaded to unstable, but it won't migrate to testing until console-setup has been (re-)built against the new version of xkb-data. https://release.debian.org/transitions/html/auto-upperlimit-xkb-data.html So could somebody please do a no-change upload (or an upload for other reasons) of console-setup. -- Cheers, Gunnar Hjalmarsson --- End Message --- --- Begin Message --- Source: console-setup Source-Version: 1.222 Done: Gunnar Hjalmarsson We believe that the bug you reported is fixed in the latest version of console-setup, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gunnar Hjalmarsson (supplier of updated console-setup 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: Wed, 21 Jun 2023 21:34:22 +0200 Source: console-setup Built-For-Profiles: noudeb Architecture: source Version: 1.222 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Gunnar Hjalmarsson Closes: 1038729 1038759 Changes: console-setup (1.222) unstable; urgency=medium . * Team upload * New no-change upload, since the NMU failed to build - I suspect the '+nmu1' in the version string has something to do with it. Also the BTS seems to not understand that version string, so again: closes: #1038759, #1038729 . . console-setup (1.221+nmu1) unstable; urgency=medium . * Non-maintainer upload * No-change upload to build against xkb-data 2.38-2 (merge request !19, closes: #1038759, #1038729) Checksums-Sha1: 5c4badf8fd17283f689a678adbabac3a1120071b 2857 console-setup_1.222.dsc 38007c31cc6f52968c75c9ca339127b778b61a17 2601648 console-setup_1.222.tar.xz 21755181bba38b897a3835790cd82277ec0d52fc 14598 console-setup_1.222_source.buildinfo Checksums-Sha256: 4ae3c2a84516d907f4a2fbc14975f2ed8841409716f059c6f6239c427bdee149 2857 console-setup_1.222.dsc 60f759afed744b0242f75c90e25a168a7c360d4f2c4278b9a9badc850f2c5e02 2601648 console-setup_1.222.tar.xz c8d6c2d4277ebccb6aa025bd36e0dfde72ff380c31026a909b45cdbbb31df0c4 14598 console-setup_1.222_source.buildinfo Files: d8e991f411562eb067d072a3cfbd95b9 2857 utils optional console-setup_1.222.dsc f41dab27660127f4198b828d33388b86 2601648 utils optional console-setup_1.222.tar.xz 22284486a6ab470f6e62ae2d91058511 14598 utils optional console-setup_1.222_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEDP6Ze3JFgKf6cvjP8LEQ51ppLzIFAmSTU9cACgkQ8LEQ51pp LzKHjAgAooBD5W8rucur2YrtZESiK6NPaFC3knk1FPNBk91CwAWsMmQHRgz5+NBu j6hgSdGYtSO10dY6VWZ/HLPiEGj2Vkz7KlS8YzyZigoI4lnkRIjZgVjtAHysQ//g 0h++6tr/3HwPmJlF7tHGNbZK27xBzmY6eshDUPR10uNOZE84XXTTsf1grEQ50f0s VEm0aSNFHEzc/p7656/OMecCbVcBWt9RGdNFpySeSV8CsP8nc3M1CcQA6/NKyVto PPbb2WUYJG3g3+pFxjG8sNWBKe6cxxl1qMtvjeyBQH6scRcO4+HQ/Q9pxCnwfo2g hvuTdMSt14qqtdpZ7uctw61UYrInHQ== =H2gL -END PGP SIGNATURE End Message ---
Processed: tagging 1038823
Processing commands for cont...@bugs.debian.org: > tags 1038823 - fixed-upstream Bug #1038823 [src:pysdl2] pysdl2: autopkgtest failure with SDL 2.28.0: cannot create a Renderer Removed tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1038823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037052: marked as done (minidlna: CVE-2023-33476)
Your message dated Wed, 21 Jun 2023 19:51:05 + with message-id and subject line Bug#1037052: fixed in minidlna 1.3.2+dfsg-1.1 has caused the Debian Bug report #1037052, regarding minidlna: CVE-2023-33476 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.) -- 1037052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: minidlna Version: 1.3.2+dfsg-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for minidlna. CVE-2023-33476[0]: | ReadyMedia (MiniDLNA) versions from 1.1.15 up to 1.3.2 is vulnerable | to Buffer Overflow. The vulnerability is caused by incorrect | validation logic when handling HTTP requests using chunked transport | encoding. This results in other code later using attacker-controlled | chunk values that exceed the length of the allocated buffer, resulting | in out-of-bounds read/write. 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-2023-33476 https://www.cve.org/CVERecord?id=CVE-2023-33476 [1] https://blog.coffinsec.com/0day/2023/05/31/minidlna-heap-overflow-rca.html [2] https://sourceforge.net/p/minidlna/git/ci/9bd58553fae5aef3e6dd22f51642d2c851225aec/ Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: minidlna Source-Version: 1.3.2+dfsg-1.1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of minidlna, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated minidlna 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: Mon, 19 Jun 2023 21:14:33 +0200 Source: minidlna Architecture: source Version: 1.3.2+dfsg-1.1 Distribution: unstable Urgency: medium Maintainer: Alexander GQ Gerasiov Changed-By: Salvatore Bonaccorso Closes: 1037052 Changes: minidlna (1.3.2+dfsg-1.1) unstable; urgency=medium . * Non-maintainer upload. * upnphttp: Fix chunk length parsing (CVE-2023-33476) (Closes: #1037052) Checksums-Sha1: 6e17d263c48e1e4265af13dec3126653b9319659 2190 minidlna_1.3.2+dfsg-1.1.dsc abe29630a0e991282144339440ce830d3065f374 24352 minidlna_1.3.2+dfsg-1.1.debian.tar.xz Checksums-Sha256: a9f44dfa744939d9c6d520870913e78c09180fba90b10a5a8c485614e6aa8903 2190 minidlna_1.3.2+dfsg-1.1.dsc 772788f38d248a30f0bfb507848ddc804364c82cd7540810a445723fca38edcc 24352 minidlna_1.3.2+dfsg-1.1.debian.tar.xz Files: 53a9374f909ada24e618cf09764ef459 2190 net optional minidlna_1.3.2+dfsg-1.1.dsc 7ae358c8d955b7f5c33bf4847e1bf744 24352 net optional minidlna_1.3.2+dfsg-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmSQqrpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89E+OkQAJWw8r3Am9uj7PQHDth5w3sgqFGC5JOo HR8ztKIq4g8JiLso0YKH74RDyMIfDJrB+o48OypPgZkNSfu1FJCqTm9Wh804THQq cUWHKmyX7rOzh1pmUkQYLFEGccopIdmkj9vESDg1zdVy1YdQlqyL8dDDCX8Rvt7T DP5s3UIF4ECOl+iSRqJLRmjSGpTtN0AHJGSN+UR5cgLMx6Mn+fQ/kLMq+unFNBHW L1oqqFk2LONbiVbL4KGRE+JfvgckasdV2gIP7+VcdCsObwEkVLM6teU0dGhOnZv1 1DB5Afi+3fShBrb0Fv7WVAkirvlY4OhkYx0NvQUrrFl5VhmKrgPFYu/VPHyQhmUG pHDa80nYZOGI2yVEEFtB+x7J0DXd7jNBQFcIKw3EpxzhvfvoaEE5o//o3nv6r43T zxB4GWZw7pGhfgHRBHfELv5gF7nxgylV5wAlMI+WtTevmJtqooBvNEMsghcEXw1e pwOGCa9+p5AhgWuspJW9SUxmWP02IUuYXmq3GPSM7iH4O/BOuqBi/SMcutM2onUZ 3K3m0yCgY4fvjLvNOn7MRJiFy/CyQuxaFvnW2i1o8uCwUyZLt58Psnfa5qa/DBP6 dgYBbkdzJBAmJfTgPXNfl97m9Fw2/+BcONX0NtfCsi2yNqMpujZOc+0Cs8GgMOK3 66w8rewObXVv =2Orf -END PGP SIGNATURE End Message ---
Processed: tagging 1038823
Processing commands for cont...@bugs.debian.org: > tags 1038823 + trixie sid Bug #1038823 [src:pysdl2] pysdl2: autopkgtest failure with SDL 2.28.0: cannot create a Renderer Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1038823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038823: pysdl2: autopkgtest failure with SDL 2.28.0: cannot create a Renderer
Source: pysdl2 Version: 0.9.9+dfsg1-6 Severity: serious Tags: fixed-upstream Justification: https://release.debian.org/testing/rc_policy.txt 6a X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: needs-update pysdl2's autopkgtest is failing since I uploaded libsdl2 version 2.28.0 to unstable. This appears to be a test issue, rather than a regression in libsdl2. An example of one of the failures: 70s self = 70s 70s def test_SDL_CreateDestroyRenderer(self): 70s failed = 0 70s rcount = render.SDL_GetNumRenderDrivers() 70s for i in range(rcount): 70s window = video.SDL_CreateWindow(b"Test", 10, 10, 10, 10, 70s video.SDL_WINDOW_SHOWN) 70s assert isinstance(window.contents, video.SDL_Window) 70s renderer = render.SDL_CreateRenderer(window, i, self._RENDERFLAGS) 70s if not (renderer and renderer.contents): 70s failed += 1 70s video.SDL_DestroyWindow(window) 70s continue 70s assert isinstance(renderer.contents, render.SDL_Renderer) 70s render.SDL_DestroyRenderer(renderer) 70s 70s # TODO: using -1 as index for the call below leads to random 70s # access violations on Win32 70s renderer = render.SDL_CreateRenderer(window, i, 70s render.SDL_RENDERER_SOFTWARE) 70s > assert isinstance(renderer.contents, render.SDL_Renderer) 70s E ValueError: NULL pointer access If I hack in some extra debug, it seems that the SDL error message is "Surface already associated with window", which is related to: - https://github.com/pygame-community/pygame-ce/issues/2190 - https://github.com/libsdl-org/SDL/issues/7793 - https://github.com/libsdl-org/SDL/pull/7795 Briefly, SDL upstream considers it to be a programming error to attempt to create a Renderer for a window that already has a window surface, and some video drivers imply creation of a window surface. SDL 2.28.0 is better at detecting and diagnosing this situation than previous releases. pysdl2/experimental seems to have fixed the test, so I'm going to upload that to unstable if successful. smcv
Bug#1034683: marked as done (r-base: new upstream release unintentionally uploaded to unstable)
Your message dated Wed, 21 Jun 2023 14:00:48 -0500 with message-id <25747.18656.127202.613...@rob.eddelbuettel.com> and subject line Re: Bug#1034683: r-base: new upstream release unintentionally uploaded to unstable has caused the Debian Bug report #1034683, regarding r-base: new upstream release unintentionally uploaded to unstable 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.) -- 1034683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-base Version: 4.3.0-1 Severity: serious Justification: maintainer presumably considers this version to be unsuitable for bookworm > r-base (4.3.0-1) unstable; urgency=medium > . > * New upstream release (into 'experimental' while Debian is frozen) I'm assuming that mismatch between the changelog message and the header wasn't intentional... Hopefully we're close enough to the release that no further uploads of r-base for bookworm will be necessary. smcv --- End Message --- --- Begin Message --- Hi Philip, On 21 June 2023 at 20:15, Philip Rinn wrote: | Hi, | | could we please close this bug? We released bookworm some days ago and | propagating to testing should be fine now. [It blocks R packages to propagate to | testing currently.] Thanks for the reminder. I think we had informal consensus to leave it open during the freeze leading up to the release to avoid any last minute transfer but this can now be closed -- especially as we by now have R 4.3.1 (released at the end of last week) in unstable. So closing now. Best, Dirk | Thanks | Philip | x[DELETED ATTACHMENT OpenPGP_signature, application/pgp-signature] -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org--- End Message ---
Bug#1034683: r-base: new upstream release unintentionally uploaded to unstable
Hi Philip, On 21 June 2023 at 20:15, Philip Rinn wrote: | Hi, | | could we please close this bug? We released bookworm some days ago and | propagating to testing should be fine now. [It blocks R packages to propagate to | testing currently.] Thanks for the reminder. I think we had informal consensus to leave it open during the freeze leading up to the release to avoid any last minute transfer but this can now be closed -- especially as we by now have R 4.3.1 (released at the end of last week) in unstable. So closing now. Best, Dirk | Thanks | Philip | x[DELETED ATTACHMENT OpenPGP_signature, application/pgp-signature] -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1038756: marked as done (librust-zbus-dev: impossible to install: depends on missing librust-quick-xml-0.26-dev)
Your message dated Wed, 21 Jun 2023 18:50:39 + with message-id and subject line Bug#1038756: fixed in rust-zbus 3.12.0-3 has caused the Debian Bug report #1038756, regarding librust-zbus-dev: impossible to install: depends on missing librust-quick-xml-0.26-dev 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.) -- 1038756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-zbus-dev Version: 3.12.0-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package depends on librust-quick-xml-0.26 which is gone. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmSSHhsACgkQLHwxRsGg ASGMhQ//c542ccb2CiKa1t60dmlpXTHy5hQ9QzqKDmFbTlvku4qJfwnnUp1QPyTH iwU5CVvNFWRdexTxDnyqCIOts4lTlMv59eOeWJq2mMT9ZnWOtfv2j9glarISS3fs xhbWYxowDv1nuASYS2WvBN8LGcBi4yIN7mdx7AzitXaLhkHfHy1puoshpZcQjrZc SE4ZK9XBXyeIPwNm9Yr5nBkdIOzajdFcymVSypIyOqqMJ+rg0jDGy+7YtVKcd0Bq m/0Q45gg8JwnzhqJkm1+vlTIpMzYnE/QYrQWJ2tt+NxQB8GjLjH6UHQfMfbJ4njV RrdH26cESFxBOy7X30dxhMR3otiX1tRHfFewfctwHadbvE38eRF9+nH0NRrKXoS2 BvlSRim0UbchiMYPHdO2WZUQpup12+WrGA6pACT4BftqO++wlWIifN/bqVBolpK2 JYUNpOFfuWMiGjm005U97o0Jewij7YDZRVPOzElBl9xcR048XPhyPC4ReUnR3BNY kBeTqLzSSkNCrMh6dZ7rq5jHVaEFoxx7RYBZe/gDyYCsmUE9c4xKUz2CIsXFqEIv vqfTsXKs/5M/RnqDWr4WF4plC/glwluSVpbyr8uzS87rNnleqJW8h1Y2S13UQojJ 81SkxBP6Z9mP38diurUZx61uaahDrz0kKX+ryIOdSiIvwwfJiJ0= =29YD -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: rust-zbus Source-Version: 3.12.0-3 Done: Matthias Geiger We believe that the bug you reported is fixed in the latest version of rust-zbus, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Geiger (supplier of updated rust-zbus 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, 21 Jun 2023 20:35:12 +0200 Source: rust-zbus Architecture: source Version: 3.12.0-3 Distribution: experimental Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Matthias Geiger Closes: 1038756 Changes: rust-zbus (3.12.0-3) experimental; urgency=medium . * Team upload. * Package zbus 3.12.0 from crates.io using debcargo 2.6.0 * Amend patch to relax dependency on quick-xml (Closes: #1038756) Checksums-Sha1: aae1d2c827f983ac4dcd088425c555a2072dab1d 4572 rust-zbus_3.12.0-3.dsc fa72817c9cc7536c7812ffda8c65a9c95c6e736d 5024 rust-zbus_3.12.0-3.debian.tar.xz 44d9387945a9db6cd77378dd9b31fc985965fb2b 7275 rust-zbus_3.12.0-3_source.buildinfo Checksums-Sha256: 9462667b0090b4b3811bc5f5478960571e854d5b316ace41487ce2165c54c88b 4572 rust-zbus_3.12.0-3.dsc 454ced09d2bba0d9d74545163f0443893616d109188fb6474117f5fc64ee0e42 5024 rust-zbus_3.12.0-3.debian.tar.xz 1319263df4675033ec6972f10c2e4987cc8c9333282d2f173d4cf33ff2662bc0 7275 rust-zbus_3.12.0-3_source.buildinfo Files: 035caab05314fa4e9fc0daef1f309c88 4572 rust optional rust-zbus_3.12.0-3.dsc 497b2603e79767005e22e6a329f127d2 5024 rust optional rust-zbus_3.12.0-3.debian.tar.xz 2cfaff53a55d590001d91888b4d191d4 7275 rust optional rust-zbus_3.12.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJUBAEBCgA+FiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmSTQuMgHG1hdHRoaWFz LmdlaWdlcjEwMjRAdHV0YW5vdGEuZGUACgkQGL0QaztsVHU70BAAvmkZT/nvuumY JPTyPRkAwZnlArtO5Jv0gtO+1DD6UhPcladrMKe8K22fH3/b3CftszOvcMxLmUaX AXEWjYNarK7I8G8h1jtBl75Z4Bq4Nr+hXzjrPMa/u0yx+w8gfpSblvx6HwuCKxYu vlGbbuG3BJEoDo0RFzBCBvI6OBHdwbV1WVRQIzC2MxJlZcbN3udL+f++NT5iyeUD 9xUZVTwfzMG3tB66n5Kl3GwPXTtu+NpvuwD71fIGDgoqLmbSGX3OpFzqJsrp099D 0xxgXtR2yrnfxEad0nlQM4kFYlqgxR+FU4nu51gIzW9WDyHReCBioulObK3KG00W B99gwugpxvgqJYLi3Lo1IVMJXbGUefCsjnOAWjEk7xzxvSnTfa/4foWtyQ5InceS x6Et6x4nZE2FwaSj7G4+K+9IZz3Y83G0dB31CMdwgYh/wiGeSOzJ8A2qaWUKqRu3 uLjmjISH985oW0nStPoLlnq7yc65SzHb5tMXgp8UYAVFVjJY4ty/0I2lRsnNpy8C pa3Kvrs2MbhooneEd5mFFjOClzlgXJhm/0N6GOSWI8IDJIMECrwp9/kAOEWRrvWg MGhfDoO4TSly3MCfS0jX+pI7vTa02MZKXkcp6kXfnV2mWf3b/RmmUW51f0q04XIJ +zynLFMeSQZqODj2PH1CaQZ6XigyAio= =1lXg -END PGP SIGNATURE End Message ---
Bug#1038723: marked as done (tiktoken FTBFS: error: failed to select a version for the requirement `pyo3 = "^0.17.3"`)
Your message dated Wed, 21 Jun 2023 20:41:43 +0200
with message-id
and subject line (fwd) Accepted tiktoken 0.4.0-2 (source) into unstable
has caused the Debian Bug report #1038723,
regarding tiktoken FTBFS: error: failed to select a version for the requirement
`pyo3 = "^0.17.3"`
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.)
--
1038723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiktoken
Version: 0.4.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=tiktoken=0.4.0-1
...
running build_ext
running build_rust
cargo rustc --lib --message-format=json-render-diagnostics --manifest-path
Cargo.toml --release -v --features pyo3/extension-module -- --crate-type cdylib
error: failed to select a version for the requirement `pyo3 = "^0.17.3"`
candidate versions found which didn't match: 0.19.0
location searched: directory source `/usr/share/cargo/registry` (which is
replacing registry `crates-io`)
required by package `tiktoken v0.4.0 (/<>)`
perhaps a crate was updated and forgotten to be re-vendored?
error: `cargo rustc --lib --message-format=json-render-diagnostics
--manifest-path Cargo.toml --release -v --features pyo3/extension-module --
--crate-type cdylib` failed with code 101
ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:388: build: plugin pyproject failed with: exit code=1:
python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir
/<>/.pybuild/cpython3_3.11_tiktoken
dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned exit
code 13
make: *** [debian/rules:9: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.4.0-2
Forgot to close this bug with the latest upload.
Start of forwarded message
From: Debian FTP Masters
To: debian-devel-chan...@lists.debian.org
Subject: Accepted tiktoken 0.4.0-2 (source) into unstable
Date: Wed, 21 Jun 2023 16:55:04 +
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 21 Jun 2023 18:00:56 +0200
Source: tiktoken
Architecture: source
Version: 0.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Deep Learning Team
Changed-By: Petter Reinholdtsen
Changes:
tiktoken (0.4.0-2) unstable; urgency=medium
.
* Added 1010-lower-dep-version-pyo3.patch.
Checksums-Sha1:
e544e995af4e896e5e4cbf527da48908e79da4af 2189 tiktoken_0.4.0-2.dsc
c7bda0b9c644e206cfed22fdd0da4070af4e8947 3216 tiktoken_0.4.0-2.debian.tar.xz
6a8e2e2e6e3e6392b7092dad5ebdeb6fa9b2ca6e 16976
tiktoken_0.4.0-2_source.buildinfo
Checksums-Sha256:
deeaa2e83dc4500559fbfe4c0d234657b46a99e6efa86a71fa4b94b8af3cd245 2189
tiktoken_0.4.0-2.dsc
f9859afd7d837fadaa43e6bf7317021b2277f4c43a6b88e96bbb9bfba400d556 3216
tiktoken_0.4.0-2.debian.tar.xz
69db64ecb284209a5d783ca3054196f5c962c685c8ed25196bd51e4304914edf 16976
tiktoken_0.4.0-2_source.buildinfo
Files:
db9720b9b5e868c4c10dfb144f40ed6b 2189 python optional tiktoken_0.4.0-2.dsc
df64a3772bffafdc84ed3a32fdd63764 3216 python optional
tiktoken_0.4.0-2.debian.tar.xz
7181da8d04889f57a1d4dc800460a833 16976 python optional
tiktoken_0.4.0-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmSTILoACgkQgSgKoIe6
+w7wwxAAtnuryFpBYlpfj2/0lxlRJSFXgT/xSSDuK+0pLi/QObeN0CEW3vG4kcYC
zByCroP9Sj6C8OnQo+Pw4Tm+5uosau2GsiHTpRLf26xV/Vq22pwyVaLxTEQv+WFc
8dwRVtLXTlO2TZLd51I5J1uoehWfQZx8GGF0dFDqPrXwSf8om5NSXk/2rt8J+KHa
52eKXT40az+F1gT+zumTgv72DDJ6m5OLQMsEHqfaZBbT/uEUYNl5ygBovwG3upkl
vGuVNabYH3CtTbTiE3XJJd/2cvUG0rRL5attnEvndT+X3JciHjDd+Hsv5sF2w8nJ
43huraw7wVyab5cTx/DSNLiv7kr3ujqsanKOkE/k7o+VFIVma2aWntRZxHxabg+n
/MZYQu0oKbIqA5uvioSXWoFyaZJAy3yb8IURXb7Few08TQr+putN/qIae/cYxpCs
pJPAVQLUhsWm+C6ILzUsHs3U4FYNi1MSVY7LKA3uAn9bdL6csRC8kPVQ5glcyKDl
ZfG6xdWfsklDxIfDhgDaDcDUc4Vl4YxRHODf1BnV8SNjYsacqdQ33DJwKPmOK/xP
+b6aHs2dO3/49X1H9zYmWto5jbdVcvdUJ3jSFmlgFKw1R5+oD3GB6L+osa+aL5+8
4qAXjrB1GfH6fnlAB6TPlSrDo5Dc/qCVrqN4Ob+Je/1faFWiJ/c=
=9njZ
-END PGP SIGNATURE-
End of forwarded message --- End Message ---
Bug#1038762: [src:systemd]: login (gnome) uses wrong keyboard layout
On Wed, 2023-06-21 at 03:06 +0200, Michael Biebl wrote: > As a quick/temporary workaround, you can run > > ln -s /etc/default/keyboard /etc/vconsole.conf Indeed removing the the latter file and creating the suggested symlink works. Thanks. Should it be of interest to you, the `localectl` output before doing this was as follows: System Locale: LANG=en_GB.UTF-8 VC Keymap: uk X11 Layout: (unset) And after: System Locale: LANG=en_GB.UTF-8 VC Keymap: (unset) X11 Layout: gb X11 Model: pc105
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2023-06-21 at 09:40 -0300, Adilson dos Santos Dantas wrote: > These messages are when I stop lightdm. Ah ok. > > > > > > Also is there something peculiar about your hardware (Nvidia/AMD GPU for > > example?) or software (specific configuration or something). > > > I'm using Nvidia GPU: > > 01:00.0 VGA compatible controller: NVIDIA Corporation TU117 [GeForce GTX > 1650] (rev a1) > > And it is using its official drivers: > > dpkg -l xserver-xorg > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- > pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Nome Versão Arquitectura Descrição > +++-==--- > = > ii xserver-xorg 1:7.7+23 amd64 X.Org X server > > dpkg -l xserver-xorg-video-nvidia > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- > pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Nome Versão Arquitectura Descrição > +++-=--- > = > ii xserver-xorg-video-nvidia 530.41.03-1 amd64 NVIDIA binary Xorg > driver Yup, that's likely related. Honestly we (I) don't really support binary/proprietary drivers. It'd help if you could test with free drivers (nouveau or something maybe). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSTQAAACgkQ3rYcyPpX RFu7Ggf9FCsjsiXteQ+xDSolGEtK2a9eBlnCnI9MY3wY2OdOHJlNCpbEjamWVbw3 CwEn4//IWPgFmLcKBD1A9ySYein2tY3CDdNH5fii7ZZ/MNAlL1vuKAVuV30ayQtU V/4xxQXgJ+1JUCPzzKNGMdLs/yumAiLGAs3XzhjUmjVPQWMRWanCOf8dFavDyFG3 4sPS6niMeFUWqM17K0ja7VPVj2QbQQSe34jec93W+zcbnxbWZZuJY9nQ2PsQjRDd /FY0fBQtzopnZMBgRUdYNj09QGuI8kn6dZdD93+/MS2uP95ES7v1nG0bKARrGor7 pNaWlBMeMGI/+bL89SFEQdR52n/uFw== =tTX8 -END PGP SIGNATURE-
Bug#1034683: r-base: new upstream release unintentionally uploaded to unstable
Hi, could we please close this bug? We released bookworm some days ago and propagating to testing should be fine now. [It blocks R packages to propagate to testing currently.] Thanks Philip OpenPGP_signature Description: OpenPGP digital signature
Bug#1038759: marked as done (console-setup: Build against xkb-data 2.38-2 needed)
Your message dated Wed, 21 Jun 2023 17:49:23 + with message-id and subject line Bug#1038759: fixed in console-setup 1.221+nmu1 has caused the Debian Bug report #1038759, regarding console-setup: Build against xkb-data 2.38-2 needed 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.) -- 1038759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:console-setup Version: 1.221 Severity: important X-Debbugs-Cc: debia...@lists.debian.org, gunna...@debian.org Control: affects -1 src:xkeyboard-config Dear maintainers, xkeyboard-config 2.38-2 was recently uploaded to unstable, but it won't migrate to testing until console-setup has been (re-)built against the new version of xkb-data. https://release.debian.org/transitions/html/auto-upperlimit-xkb-data.html So could somebody please do a no-change upload (or an upload for other reasons) of console-setup. -- Cheers, Gunnar Hjalmarsson --- End Message --- --- Begin Message --- Source: console-setup Source-Version: 1.221+nmu1 Done: Gunnar Hjalmarsson We believe that the bug you reported is fixed in the latest version of console-setup, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gunnar Hjalmarsson (supplier of updated console-setup 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: Wed, 21 Jun 2023 19:20:15 +0200 Source: console-setup Built-For-Profiles: noudeb Architecture: source Version: 1.221+nmu1 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Gunnar Hjalmarsson Closes: 1038729 1038759 Changes: console-setup (1.221+nmu1) unstable; urgency=medium . * Non-maintainer upload * No-change upload to build against xkb-data 2.38-2 (merge request !19, closes: #1038759, #1038729) Checksums-Sha1: 8115f081e2921885898763a20887b5adb973f708 2877 console-setup_1.221+nmu1.dsc 251b1d80f68abea007f82c4db3d042adcfb66b2b 2601584 console-setup_1.221+nmu1.tar.xz 0b9ad7a310d55832f231c2004a8f6cde6444c526 14618 console-setup_1.221+nmu1_source.buildinfo Checksums-Sha256: 190bff315d5857f375ca6f315cfc0d48c0c1172545cb28f1185c9249325cc749 2877 console-setup_1.221+nmu1.dsc 813aa18f90cb311c1c99ce7b7d36d70a756b11ce9dec575223e70a106a7a85e4 2601584 console-setup_1.221+nmu1.tar.xz 4dea33e32ec3853c1be0327503c99a8c09755cf1fc44f7820f2ab719b4e8baa0 14618 console-setup_1.221+nmu1_source.buildinfo Files: f8ccb4755c28177348503cd4c641b747 2877 utils optional console-setup_1.221+nmu1.dsc 4c47620bb36d3f04f055da58a0e96fcd 2601584 utils optional console-setup_1.221+nmu1.tar.xz 2d89017652a98bc61ff73085792353b9 14618 utils optional console-setup_1.221+nmu1_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEDP6Ze3JFgKf6cvjP8LEQ51ppLzIFAmSTMgMACgkQ8LEQ51pp LzIAcggAi2Rct7zJ47Ip4ktwaJWJEahuMtG/wlr20DZUsKrPw5vCEyxCfbFcrW4a 7ReOwTY9+ypxAQOU6axJ/60AIP1sMjnZsoEqI15xWFivkF9t+Hn8241S2+Yk5mJU ry1VFUTKrCExrD2WAUwiH0ZbSRM2oXFnt34XNYoj/sPX0NYFdHzCUrUbcl3SgU/d 1AWhfwm1/Uk4SXEN31+8lvwqR/75jAPotgxm1X8BwSpzWROLxAAkT51m8v8C+uaV /WN3keHDJK2TqfiHN7tCW1l/W3Ba7lkZTqq297qUNkMd1wkEExaOXqElypmO+f/n z6kX2g4KCguPKfyAHjADJctz0VLomA== =q/QA -END PGP SIGNATURE End Message ---
Bug#1038416: marked as done (proftpd-basic: proftpd service fails to start on next server reboot)
Your message dated Wed, 21 Jun 2023 17:20:05 + with message-id and subject line Bug#1038416: fixed in proftpd-dfsg 1.3.8+dfsg-5 has caused the Debian Bug report #1038416, regarding proftpd-basic: proftpd service fails to start on next server reboot 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.) -- 1038416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: proftpd-basic Version: 1.3.8+dfsg-4 Severity: normal Dear Maintainer, * What led up to the situation? Even on clean Debian12, with just proftpd installed, proftpd service will not start om next server reboot. * What exactly did you do (or not do) that was effective (or ineffective)? Service is installed this way: # apt install proftpd Note, selecting 'proftpd-core' instead of 'proftpd' The following additional packages will be installed: libhashkit2 libhiredis0.14 libmemcached11 libmemcachedutil2 libpcre2-posix3 The following NEW packages will be installed: libhashkit2 libhiredis0.14 libmemcached11 libmemcachedutil2 libpcre2-posix3 proftpd-core I also did: # systemctl enable proftpd Output is: Synchronizing state of proftpd.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable proftpd ...but on next reboot proftpd service will not be automatically started. So, after reboot, if I do: # systemctl status proftpd Output is: ○ proftpd.service - ProFTPD FTP Server Loaded: loaded (/lib/systemd/system/proftpd.service; enabled; preset: enabled) Active: inactive (dead) It's clearly not started. If I do: # grep 'proftpd' /var/log/syslog Output is only this line: 2023-06-17T21:34:40.157071+00:00 vesna systemd[1]: Listening on proftpd.socket - ProFTPD FTP Server Activation Socket. Also: # ps -Af | grep 'proftp' gives nothing. But if I run: # cat /var/log/proftpd/proftpd.log I get: 2023-06-17 21:34:19,440 vesna proftpd[35867] xxx.xxx.xxx.xxx: ProFTPD killed (signal 15) 2023-06-17 21:34:19,440 vesna proftpd[35867] xxx.xxx.xxx.xxx: ProFTPD 1.3.8 standalone mode SHUTDOWN 2023-06-17 21:40:21,401 vesna proftpd[2593] xxx.xxx.xxx.xxx: Failed binding to ::, port 21: Address already in use 2023-06-17 21:40:21,402 vesna proftpd[2593] xxx.xxx.xxx.xxx: Check the ServerType directive to ensure you are configured correctly 2023-06-17 21:40:21,402 vesna proftpd[2593] xxx.xxx.xxx.xxx: Check to see if inetd/xinetd, or another proftpd instance, is already using ::, port 21 2023-06-17 21:40:21,402 vesna proftpd[2593] xxx.xxx.xxx.xxx: Unable to start proftpd; check logs for more details Looks like it is killed by something (inetd?), but when incoming connection comes, it says port 21 is in use. Then, when I check netstat: # netstat -tuapen | grep ':21' I get: tcp6 0 0 :::21 :::*LISTEN 0 15323 1/init Now if I start proftpd manually: # systemctl start proftpd # netstat -tuapen | grep ':21' gives: tcp6 0 0 :::21 :::*LISTEN 10931548 6990/proftpd: (acce # ps -Af | grep 'proftp' gives: proftpd 6990 1 0 22:25 ?00:00:00 proftpd: (accepting connections) ... and proftpd service perfectly works... On next reboot the situation is the same as on the beginning of this report. My /etc/proftpd/proftpd.conf is default one, I didn't changed anything after proftpd is installed. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/2 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) Versions of packages proftpd-basic depends on: ii proftpd-core1.3.8+dfsg-4 ii proftpd-mod-crypto 1.3.8+dfsg-4 ii proftpd-mod-wrap1.3.8+dfsg-4 proftpd-basic recommends no packages. proftpd-basic suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: proftpd-dfsg Source-Version: 1.3.8+dfsg-5 Done: Francesco Paolo Lovergine We believe that the bug you reported is fixed in the latest version of proftpd-dfsg, which is due to be
Processed: libsys-gamin-perl: Please consider removal
Processing control commands: > severity -1 serious Bug #982088 [libsys-gamin-perl] libsys-gamin-perl: Please consider removal Severity set to 'serious' from 'wishlist' > block 1008205 by -1 Bug #1008205 [src:gamin] gamin: unmaintained upstream 1008205 was blocked by: 1038806 1038809 1038808 1038805 1038807 1008205 was not blocking any bugs. Added blocking bug(s) of 1008205: 982088 -- 1008205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008205 982088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 886087 is serious
Processing commands for cont...@bugs.debian.org: > severity 886087 serious Bug #886087 [src:alarm-clock-applet] alarm-clock-applet: Depends on gconf Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 886087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038005: marked as done (vpoll-dkms: module fails to build for Linux 6.3)
Your message dated Wed, 21 Jun 2023 15:04:52 +
with message-id
and subject line Bug#1038005: fixed in libvpoll-eventfd 0.1.1-1
has caused the Debian Bug report #1038005,
regarding vpoll-dkms: module fails to build for Linux 6.3
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.)
--
1038005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vpoll-dkms
Version: 0.1-3
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts
DKMS make.log for vpoll-0.1 for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 10:27:14 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
CC [M] /var/lib/dkms/vpoll/0.1/build/vpoll.o
/var/lib/dkms/vpoll/0.1/build/vpoll.c: In function 'myinit':
/var/lib/dkms/vpoll/0.1/build/vpoll.c:117:38: error: assignment to 'char *
(*)(const struct device *, umode_t *)' {aka 'char * (*)(const struct device *,
short unsigned int *)'} from incompatible pointer type 'char * (*)(struct
device *, umode_t *)' {aka 'char * (*)(struct device *, short unsigned int *)'}
[-Werror=incompatible-pointer-types]
117 | vpoll_class->devnode = vpoll_devnode;
| ^
cc1: some warnings being treated as errors
make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.build:257:
/var/lib/dkms/vpoll/0.1/build/vpoll.o] Error 1
make: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050:
/var/lib/dkms/vpoll/0.1/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.3.0-1-amd64'
Andreas
--- End Message ---
--- Begin Message ---
Source: libvpoll-eventfd
Source-Version: 0.1.1-1
Done: Renzo Davoli
We believe that the bug you reported is fixed in the latest version of
libvpoll-eventfd, 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 1038...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Renzo Davoli (supplier of updated libvpoll-eventfd 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: Sun, 18 Jun 2023 18:28:25 +0200
Source: libvpoll-eventfd
Architecture: source
Version: 0.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VirtualSquare Team
Changed-By: Renzo Davoli
Closes: 1038005
Changes:
libvpoll-eventfd (0.1.1-1) unstable; urgency=medium
.
[ Renzo Davoli ]
* New upstream release 0.1.1.
+ Fix support for Linux 6.2+. Closes: #1038005
* Bump Standards-Version to 4.6.2, no changes needed.
.
[ Mattia Rizzolo ]
* Drop uupdate from d/watch.
Checksums-Sha1:
440ed8ad30f945a7e19c697597e821925a5b8487 2264 libvpoll-eventfd_0.1.1-1.dsc
fcabbfd6c1ee0abe1226e55ed3589b5d9211a352 24271
libvpoll-eventfd_0.1.1.orig.tar.gz
3f96dd444ccbc18ab6ebb28c2f7e4348f9d0 3060
libvpoll-eventfd_0.1.1-1.debian.tar.xz
b6e30abf80d266b87386345f67d0c2159d9fb804 7608
libvpoll-eventfd_0.1.1-1_amd64.buildinfo
Checksums-Sha256:
3cfc59300e54fc99f85b72ff63506b32cb0cdd590b08ddfb4564aecf39f6c92b 2264
libvpoll-eventfd_0.1.1-1.dsc
e72104632bbbacbaf6c7c07aad2ce636527507ff04334c1835d78d402a269f19 24271
libvpoll-eventfd_0.1.1.orig.tar.gz
4e0ee5f91718ac1ac7d3ce1ff0be0d5eb5004b3deb9d05babaa7ee71ec4ee817 3060
libvpoll-eventfd_0.1.1-1.debian.tar.xz
47c04a91062c98fd9e352df2e86b55e36ac503f056de73b403f174b8379bee65 7608
libvpoll-eventfd_0.1.1-1_amd64.buildinfo
Files:
f14fc5a70ef5875ffa0db5ea2b3315c7 2264 libs optional
libvpoll-eventfd_0.1.1-1.dsc
f0c523862ecc394546be35934cb57d39 24271 libs optional
libvpoll-eventfd_0.1.1.orig.tar.gz
3e6b5b723fd137f615c3774b2fa54277 3060 libs optional
libvpoll-eventfd_0.1.1-1.debian.tar.xz
a2786a887063c2a6ed03565d6ae4efe9 7608 libs optional
libvpoll-eventfd_0.1.1-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmSTDMcACgkQCBa54Yx2
K63x8Q/8DSx7/gOvG1MWJ6tR43kwvEdjtkQxyP34+6My9XzwaS/aydrJU1B0OtWV
8XL/ovFn89bqyGOJMBvY4cbk02QZ9FwtxGcjiR3pFf5mNuN9buA+4Bk7KDnO+H6R
PW6VklrnOcA4jk6uNLoShe4SQcRhxqbcyXqkG8k303gHFGYzUVdG/96T6fO0uKof
Y4lyHnycoQlkZoCC03ffSbDuu6XTLcUB9XmubsWX7f+xp+wVpVgUg3ZQSF5Hzzlq
Bug#1038793: unmaintained fork for jwt-go
Source: golang-github-form3tech-oss-jwt-go Version: 3.2.3-1 Severity: serious X-Debbugs-Cc: z...@debian.org I don't see any reason to introduce another unmaintained fork of jwt-go. Since it hasn't be in testing before, no existing code depends on that. New code should use https://tracker.debian.org/pkg/golang-github-golang-jwt-jwt -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/16 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
Bug#1037480: marked as done (autopkgtest fails with golang-1.20)
Your message dated Wed, 21 Jun 2023 12:52:03 + with message-id and subject line Bug#1037480: fixed in ycmd 0+20230611+git3392251+ds-1 has caused the Debian Bug report #1037480, regarding autopkgtest fails with golang-1.20 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.) -- 1037480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ycmd Version: 0+20230103+gitf53e7ac+ds-1 Severity: serious X-Debbugs-Cc: z...@debian.org Control: forworded -1 https://github.com/ycm-core/ycmd/commit/01a1f543 I've updated golang-defaults to 1.20 in unstable, your package's autopkgtest fails with that. I've sent the fix to upstream, could you backport the commit or package a new snapshot. https://github.com/ycm-core/ycmd/commit/01a1f543 -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/16 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 --- End Message --- --- Begin Message --- Source: ycmd Source-Version: 0+20230611+git3392251+ds-1 Done: David Kalnischkies We believe that the bug you reported is fixed in the latest version of ycmd, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Kalnischkies (supplier of updated ycmd 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, 21 Jun 2023 14:05:18 +0200 Source: ycmd Architecture: source Version: 0+20230611+git3392251+ds-1 Distribution: unstable Urgency: medium Maintainer: David Kalnischkies Changed-By: David Kalnischkies Closes: 1037480 Changes: ycmd (0+20230611+git3392251+ds-1) unstable; urgency=medium . * New upstream version 0+20230611+git3392251+ds - Refresh patches - Make tests compatible with golang-1.20 (Closes: #1037480) * Support GDScript (Godot) completion out of the box * Prefer upstream-blessed clangd-16 before other versioned clangs * Drop as-needed linker flag from debian/rules (lintian) * Bump Standards-Version to 4.6.2 (no change needed) Checksums-Sha1: b08d23beea3eca9db535df15bc9adfbeb844f9c9 2323 ycmd_0+20230611+git3392251+ds-1.dsc f1a10955cd978cfa038449c6ad33a7cb408c3ac9 394184 ycmd_0+20230611+git3392251+ds.orig.tar.xz 8c92d7bc3950ac4719745d48fbcf2557cc7b13f9 29140 ycmd_0+20230611+git3392251+ds-1.debian.tar.xz c2b472dc49b73c34a718fed1081ccef8f8b8d72a 8560 ycmd_0+20230611+git3392251+ds-1_amd64.buildinfo Checksums-Sha256: f6763c21b4e66c8900fe65460d3b71924498175c5d2aa7d0196fea6c14960680 2323 ycmd_0+20230611+git3392251+ds-1.dsc 7d55cb2f63c786457dfa4dbe8791928454f4d6879d22f0f7af4db77bd6658c24 394184 ycmd_0+20230611+git3392251+ds.orig.tar.xz f0399ae03eb078ebd35eadf45021e078de32c3c7b26bb56aa5debdbaaf9a983d 29140 ycmd_0+20230611+git3392251+ds-1.debian.tar.xz 224ec7eea6a3098280fe881f5e768fd7d10e2d0bd32769c00cff012a231d3427 8560 ycmd_0+20230611+git3392251+ds-1_amd64.buildinfo Files: 844cd21d6e9d0ad289d3869bec5e7532 2323 devel optional ycmd_0+20230611+git3392251+ds-1.dsc 65b688323ba70d99d0ca528cfd72c927 394184 devel optional ycmd_0+20230611+git3392251+ds.orig.tar.xz 54f17f806fe3ed3a080cc54627fbd3e8 29140 devel optional ycmd_0+20230611+git3392251+ds-1.debian.tar.xz 8a3ac3642bbe0bf1fdf32015e073bdae 8560 devel optional ycmd_0+20230611+git3392251+ds-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE5sn+Q4uCja/tn0GrMRvlz3HQeIMFAmSS7JkTHGRvbmt1bHRA ZGViaWFuLm9yZwAKCRAxG+XPcdB4g9O9EACffD7hvkVgRPtNBT/LWNsTYd5b6FI4 XzOhRUYUXCwtWqmpFdOBpWlDvXA3lVqiK9L1F5Ftc5UNsO8D4WpnZKaWZiRufQeX Kg8+Tlto7yCdAQ9uKoFOhwCRuPFLj1fo08scw8/xBqyqWwtLtkUX0TrwOCh4Rt2B lyRc2DnFA+XrRXC+lBhiAz/wKB2Crz2Y1/sX49nPFL5Pe390jQjKG7SqaLgphAr0 y+pJqQIclJs8f1OH7NiN0Nt6qsSJWKKXMJKNftQhS2vY8B78i5tuZTtmHX6TehNi 2JzMN9SVbl1LcGd581j9kiCTCijCiUUlOnrm+38968RLtBIwzEF4VE0BR0iwAYXM
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Em qua., 21 de jun. de 2023 às 03:33, Yves-Alexis Perez escreveu: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Tue, 2023-06-20 at 20:37 -0300, Adilson dos Santos Dantas wrote: > > I tried to use 1.32 again and it only > > generates /var/log/lightdm/lightdm.log. It doesn't generate seat0- > > greeter.log and x-0.lo. From the log attached below, one difference is > that > > 1.26 starts seat0 and 1.32 does not start it. I got an X session from > 1.26 > > and X does not even start from 1.32. > > In the log there's definitely a bad sign: > > [+69.14s] DEBUG: Got signal 15 from process 1 > [+69.14s] DEBUG: Caught Terminated signal, shutting down > [+69.14s] DEBUG: Stopping display manager > [+69.14s] DEBUG: Display manager stopped > [+69.14s] DEBUG: Stopping daemon > [+69.14s] DEBUG: Exiting with return value 0 > These messages are when I stop lightdm. > > > Can you check also the system logs (/var/log/syslog, /var/log/daemon.log, > the > journal, dmesg...) so we have more information? > I will send some system logs from journalctl when I start and stop lightdm 1.32 and 1.26. > > Also is there something peculiar about your hardware (Nvidia/AMD GPU for > example?) or software (specific configuration or something). > I'm using Nvidia GPU: 01:00.0 VGA compatible controller: NVIDIA Corporation TU117 [GeForce GTX 1650] (rev a1) And it is using its official drivers: dpkg -l xserver-xorg Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Nome Versão Arquitectura Descrição +++-==---= ii xserver-xorg 1:7.7+23 amd64X.Org X server dpkg -l xserver-xorg-video-nvidia Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Nome Versão Arquitectura Descrição +++-=---= ii xserver-xorg-video-nvidia 530.41.03-1 amd64NVIDIA binary Xorg driver > > Regards, > - -- > Yves-Alexis > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSmacACgkQ3rYcyPpX > RFu3MQf9Hpnj5rWRK71USdZCS9Gx4vQZ+octjX/3TZWtlB8vb3eDbLAj4ZAEkZzZ > YjyFBCOx2zSV7HbY2l7fgb9/q7njngHuFr/ux+Z8nxRsyWy4fkhdQKh/4mfOt7sy > wDa7WH5y+z96f9ekBLtauWe7YBFocEiEFPsgQ6WApvLmNzMwl2oXFP/bTKBv6BWi > NWe5//R4gdt2yDKHIlZrBWGQfItg4KzG6wUuBfkrz/53PicafeFxcrOcZILoYzJK > PU6uWij2Imebdzq+02rgYWz0Qq7fqI3PxNNfiWq6fMMa+rWXM5cTEGs7XC//Vqe1 > hHbM8JXrzsc2ZcMaYCQyJ0PaqnS18w== > =4Egr > -END PGP SIGNATURE- > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond Using lightdm 1.32 Jun 21 07:49:59 yoda systemd[1]: Starting lightdm.service - Light Display Manager... jun 21 07:49:59 yoda systemd[1]: Started lightdm.service - Light Display Manager. jun 21 07:49:59 yoda audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' jun 21 07:49:59 yoda kernel: audit: type=1130 audit(1687344599.571:939): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' jun 21 07:50:15 yoda systemd[50261]: emacs.service: start operation timed out. Terminating. jun 21 07:50:15 yoda systemd[50261]: emacs.service: Failed with result 'timeout'. jun 21 07:50:15 yoda systemd[50261]: Failed to start emacs.service - Emacs text editor. jun 21 07:50:15 yoda systemd[50261]: emacs.service: Scheduled restart job, restart counter is at 8. jun 21 07:50:15 yoda systemd[50261]: Stopped emacs.service - Emacs text editor. jun 21 07:50:15 yoda systemd[50261]: Starting emacs.service - Emacs text editor... jun 21 07:50:15 yoda emacs[56260]: Warning: due to a long standing Gtk+ bug jun 21 07:50:15 yoda emacs[56260]: https://gitlab.gnome.org/GNOME/gtk/issues/221 jun 21 07:50:15 yoda emacs[56260]: Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost. jun 21 07:50:15 yoda emacs[56260]: Using an Emacs configured with --with-x-toolkit=lucid does not have this problem. jun 21 07:50:15 yoda emacs[56260]: Warning (initialization): Unable to create `user-emacs-directory' (~/.emacs.d/). jun 21 07:50:15 yoda emacs[56260]: Any data that would normally be written there may be lost! jun 21 07:50:15 yoda emacs[56260]: If you never want to see this message again, jun 21 07:50:15 yoda emacs[56260]: customize the variable `user-emacs-directory-warning'. Disable showing Disable logging jun 21 07:50:18 yoda dbus-daemon[50309]: [session uid=33 pid=50309] Failed to activate service 'org.freedesktop.Tracker3.Miner.Files': timed out
Bug#1037472: marked as done (molmodel: FTBFS with gemmi 0.6.2+ds-1)
Your message dated Wed, 21 Jun 2023 11:53:25 + with message-id and subject line Bug#1037472: fixed in molmodel 3.1.0-3 has caused the Debian Bug report #1037472, regarding molmodel: FTBFS with gemmi 0.6.2+ds-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.) -- 1037472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: molmodel Severity: serious Version: 3.1.0-2 Hello, molmodel FTBFS after recent update of gemmi to 0.6.2+ds-1: /home/merkys/molmodel-3.1.0/src/PDBReader.cpp: In function 'gemmi::Structure getStructureFromFile(const std::string&)': /home/merkys/molmodel-3.1.0/src/PDBReader.cpp:98:29: error: 'make_structure_from_block' is not a member of 'gemmi::impl'; did you mean 'gemmi::make_structure_from_block'? 98 | return gemmi::impl::make_structure_from_block ( gemmiDoc.blocks.at(0) ); | ^ In file included from /usr/include/gemmi/mmread.hpp:13, from /home/merkys/molmodel-3.1.0/./include/molmodel/internal/Compound.h:48, from /home/merkys/molmodel-3.1.0/./include/molmodel/internal/CompoundSystem.h:6, from /home/merkys/molmodel-3.1.0/./include/molmodel/internal/PDBReader.h:36, from /home/merkys/molmodel-3.1.0/src/PDBReader.cpp:33: /usr/include/gemmi/mmcif.hpp:15:21: note: 'gemmi::make_structure_from_block' declared here 15 | GEMMI_DLL Structure make_structure_from_block(const cif::Block& block); | ^ make[3]: *** [CMakeFiles/SimTKmolmodel.dir/build.make:219: CMakeFiles/SimTKmolmodel.dir/src/PDBReader.cpp.o] Error 1 make[3]: *** Waiting for unfinished jobs /home/merkys/molmodel-3.1.0/src/Pdb.cpp: In function 'gemmi::Structure gemmiStructFromDoc(const gemmi::cif::Document&)': /home/merkys/molmodel-3.1.0/src/Pdb.cpp:39:25: error: 'make_structure_from_block' is not a member of 'gemmi::impl'; did you mean 'gemmi::make_structure_from_block'? 39 | return gemmi::impl::make_structure_from_block(doc.blocks.front()); | ^ In file included from /usr/include/gemmi/mmread.hpp:13, from /home/merkys/molmodel-3.1.0/./include/molmodel/internal/Compound.h:48, from /home/merkys/molmodel-3.1.0/./include/molmodel/internal/Pdb.h:6, from /home/merkys/molmodel-3.1.0/src/Pdb.cpp:4: /usr/include/gemmi/mmcif.hpp:15:21: note: 'gemmi::make_structure_from_block' declared here 15 | GEMMI_DLL Structure make_structure_from_block(const cif::Block& block); | ^ The issue is better fixed upstream, I will forward the report. In the meantime it is OK to remove molmodel from testing to not obstruct the upcoming openmm transition. Andrius --- End Message --- --- Begin Message --- Source: molmodel Source-Version: 3.1.0-3 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of molmodel, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated molmodel 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, 21 Jun 2023 07:13:00 -0400 Source: molmodel Architecture: source Version: 3.1.0-3 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Andrius Merkys Closes: 1037472 Changes: molmodel (3.1.0-3) unstable; urgency=medium . * Adapt upstream fix to restore compatibility with gemmi (Closes: #1037472) * Set upstream metadata fields: Repository-Browse. * Update standards version to 4.6.2, no changes needed. Checksums-Sha1: cae4490c3441010d424553430686dd96a0677bc4 2227 molmodel_3.1.0-3.dsc c86745073312ff781b6ce3986af8c92a679cadb5 4252 molmodel_3.1.0-3.debian.tar.xz a1f38d5c3efe2a0c93c9dbea791274f5d8762b7c 7486 molmodel_3.1.0-3_source.buildinfo Checksums-Sha256: 8df83bac9d1b47ba77c233f45c39b9ae1c47ac18723aa3b90c2365d19d476a2d 2227
Bug#1034304: marked as done (geoalchemy2: autopkgtest regression on s390x: AssertionError)
Your message dated Wed, 21 Jun 2023 11:53:13 +
with message-id
and subject line Bug#1034304: fixed in geoalchemy2 0.13.3-2
has caused the Debian Bug report #1034304,
regarding geoalchemy2: autopkgtest regression on s390x: AssertionError
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.)
--
1034304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geoalchemy2
Version: 0.13.1-2
Severity: serious
Tags: sid bookworm bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of geoalchemy2 the autopkgtest of geoalchemy2 fails
in testing on s390x when that autopkgtest is run with the binary
packages of geoalchemy2 from unstable. It passes when run with only
packages from testing. In tabular form:
passfail
geoalchemy2from testing0.13.1-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 to testing [1]. Can
you please investigate the situation and fix it? Please be reminded that
s390x is our only big endian architecture.
[Release Team member hat on] Because we're currently in the hard freeze
for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes
are still welcome.
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=geoalchemy2
https://ci.debian.net/data/autopkgtest/testing/s390x/g/geoalchemy2/32779104/log.gz
=== FAILURES
===
_ TestInsertionORM.test_WKTElement[postgresql]
_
self =
session =
Lake = .Lake'>, setup_tables
= None
def test_WKTElement(self, session, Lake, setup_tables):
lake = Lake(WKTElement("LINESTRING(0 0,1 1)", srid=4326))
session.add(lake)
session.flush()
session.expire(lake)
assert isinstance(lake.geom, WKBElement)
assert str(lake.geom) == (
"010220e61002000"
"000f03ff03f"
)
E AssertionError: assert '00200200...0' ==
'010220e6...0f03f'
E -
010220e6100200f03ff03f
E ? - ^
^ -- - --
E +
00200210e600023ff03ff0
E ?++ + ^
+++ ^
tests/test_functional.py:297: AssertionError
_ TestInsertionORM.test_WKBElement[postgresql]
_
self =
session =
Lake = .Lake'>, setup_tables
= None
def test_WKBElement(self, session, Lake, setup_tables):
shape = LineString([[0, 0], [1, 1]])
lake = Lake(from_shape(shape, srid=4326))
session.add(lake)
session.flush()
session.expire(lake)
assert isinstance(lake.geom, WKBElement)
assert str(lake.geom) == (
"010220e61002000"
"000f03ff03f"
)
E AssertionError: assert '00200200...0' ==
'010220e6...0f03f'
E -
010220e6100200f03ff03f
E ? - ^
^ -- - --
E +
00200210e600023ff03ff0
E ?++ + ^
+++ ^
tests/test_functional.py:313: AssertionError
TestUpdateORM.test_Raster[postgresql]
_
self = 0x3ff8900de90>
session =
Ocean = .Ocean'>
setup_tables = None
def test_Raster(self, session, Ocean, setup_tables):
skip_postgis1(session)
polygon = WKTElement("POLYGON((0 0,1 1,0 1,0 0))", srid=4326)
o = Ocean(polygon.ST_AsRaster(5, 5))
session.add(o)
session.flush()
session.expire(o)
assert isinstance(o.rast, RasterElement)
rast_data = (
"0101009A99C93F9A99C9BFF03"
"FE61005000500440001010101010101010100"
"01010101010001"
)
> assert o.rast.data
Bug#1038737: FTBFS on mips64el: Unable to import PyChromecast
Hi Adrian! On Wed, Jun 21, 2023 at 12:25:53PM +0300, Adrian Bunk wrote: > python3-pychromecast is also an unconditional runtime dependency, > so building on an architecture without it would anyway be pointless > (and for release architectures break testing migration). > > Trying on the porterbox for mips64el, I think the original problem was > just a timeout in the cmake "import pychromecast" test, the patch below > works for me. Indeed, your patch is the proper fix. Thank you! -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: reopening 1034732
Processing commands for cont...@bugs.debian.org:
> reopen 1034732
Bug #1034732 {Done: Reinhard Tartler } [gpac] Keep out of
testing
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gpac/2.2.1+dfsg1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1034732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 1038759 is serious
Processing commands for cont...@bugs.debian.org: > severity 1038759 serious Bug #1038759 [src:console-setup] console-setup: Build against xkb-data 2.38-2 needed Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1038759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1031765 is normal
Processing commands for cont...@bugs.debian.org: > severity 1031765 normal Bug #1031765 [procps] pgrep: signal handler matching breaks argument parsing Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1031765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038776: dcmtk: fails to purge: rm: cannot remove '/var/lib/dcmtk/db/STORESCP': Is a directory
Package: dcmtk Version: 3.6.7-8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to purge if the installation originated in jessie or before: >From the attached log (scroll to the bottom...): (Reading database ... 10105 files and directories currently installed.) Purging configuration files for dcmtk (3.6.7-8+b1) ... rm: cannot remove '/var/lib/dcmtk/db/STORESCP': Is a directory dpkg: error processing package dcmtk (--purge): installed dcmtk package post-removal script subprocess returned error exit status 1 Errors were encountered while processing: dcmtk The postrm contains if [ -d /var/lib/dcmtk/db/STORESCP ]; then rm -f /var/lib/dcmtk/db/STORESCP fi This directory only exists on upgrades from the jessie version or earlier. cheers, Andreas dcmtk_3.6.7-8+b1.log.gz Description: application/gzip
Bug#1038737: FTBFS on mips64el: Unable to import PyChromecast
On Tue, Jun 20, 2023 at 08:31:34PM +0300, Dmitry Shachnev wrote:
> Source: photoqt
> Version: 3.3+ds-1
>...
> I have attached a patch which should fix this problem. At least it seems to
> do so on riscv64.
>
> Also, I think with my change you can drop disable-pychromecast patch which
> is currently commented out anyway.
python3-pychromecast is also an unconditional runtime dependency,
so building on an architecture without it would anyway be pointless
(and for release architectures break testing migration).
Trying on the porterbox for mips64el, I think the original problem was
just a timeout in the cmake "import pychromecast" test, the patch below
works for me.
> Dmitry Shachnev
cu
Adrian
diff -Nru photoqt-3.3+ds/debian/control photoqt-3.3+ds/debian/control
--- photoqt-3.3+ds/debian/control 2023-06-19 07:17:44.0 +
+++ photoqt-3.3+ds/debian/control 2023-06-19 07:17:44.0 +
@@ -23,7 +23,7 @@
python3-pip,
python3-dev,
python3-requests,
- python3-pychromecast [!ia64 !kfreebsd-amd64 !kfreebsd-i386 !sparc64 !sh4
!riscv64 !m68k !hppa !mips64el],
+ python3-pychromecast,
qtbase5-dev,
qt5-qmake,
qttools5-dev,
diff -Nru photoqt-3.3+ds/debian/patches/disable-pychromecast
photoqt-3.3+ds/debian/patches/disable-pychromecast
--- photoqt-3.3+ds/debian/patches/disable-pychromecast 2022-04-08
07:02:42.0 +
+++ photoqt-3.3+ds/debian/patches/disable-pychromecast 1970-01-01
00:00:00.0 +
@@ -1,56 +0,0 @@
-Description:
- TODO: Put a short summary on the line above and replace this paragraph
- with a longer explanation of this change. Complete the meta-information
- with other relevant fields (see below for details). To make it easier, the
- information below has been extracted from the changelog. Adjust it or drop
- it.
- .
- photoqt (2.6-1) unstable; urgency=medium
- .
- * New upstream version.
-Author: Gürkan Myczko
-
-The information above should follow the Patch Tagging Guidelines, please
-checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
-are templates for supplementary fields that you might want to add:
-
-Origin: ,
-Bug:
-Bug-Debian: https://bugs.debian.org/
-Bug-Ubuntu: https://launchpad.net/bugs/
-Forwarded:
-Reviewed-By:
-Last-Update: 2022-04-08
-
photoqt-2.6.orig/CMakeLists.txt
-+++ photoqt-2.6/CMakeLists.txt
-@@ -318,17 +318,17 @@ if(CHROMECAST)
- message(FATAL_ERROR "** Unable to locate Python3 Interpreter... is it
installed?")
- else()
- execute_process(COMMAND ${Python3_EXECUTABLE} -c "import
pychromecast" RESULT_VARIABLE EXIT_CODE OUTPUT_QUIET TIMEOUT 2)
--if(NOT ${EXIT_CODE} EQUAL 0)
--# try installing it with pip
--message(">> Attempt to install pychromecast locally using pip...")
--execute_process(COMMAND ${Python3_EXECUTABLE} -m pip install
pychromecast --user RESULT_VARIABLE EXIT_CODE OUTPUT_QUIET TIMEOUT 2)
--execute_process(COMMAND ${Python3_EXECUTABLE} -c "import
pychromecast" RESULT_VARIABLE EXIT_CODE OUTPUT_QUIET TIMEOUT 2)
--if(NOT ${EXIT_CODE} EQUAL 0)
--message(FATAL_ERROR "** Unable to locate Python3 module
pychromecast. Please first install it or disable Chromecast support.")
--else()
--message(">> Success!")
--endif()
--endif()
-+#if(NOT ${EXIT_CODE} EQUAL 0)
-+## try installing it with pip
-+#message(">> Attempt to install pychromecast locally using
pip...")
-+#execute_process(COMMAND ${Python3_EXECUTABLE} -m pip install
pychromecast --user RESULT_VARIABLE EXIT_CODE OUTPUT_QUIET TIMEOUT 2)
-+#execute_process(COMMAND ${Python3_EXECUTABLE} -c "import
pychromecast" RESULT_VARIABLE EXIT_CODE OUTPUT_QUIET TIMEOUT 2)
-+#if(NOT ${EXIT_CODE} EQUAL 0)
-+#message(FATAL_ERROR "** Unable to locate Python3 module
pychromecast. Please first install it or disable Chromecast support.")
-+#else()
-+#message(">> Success!")
-+#endif()
-+#endif()
- include_directories(${Python3_INCLUDE_DIRS})
- target_link_libraries(${PROJECT_NAME} ${Python3_LIBRARIES})
- message("** Chromecast support enabled")
diff -Nru
photoqt-3.3+ds/debian/patches/increase-pychromecast-test-timeout.patch
photoqt-3.3+ds/debian/patches/increase-pychromecast-test-timeout.patch
--- photoqt-3.3+ds/debian/patches/increase-pychromecast-test-timeout.patch
1970-01-01 00:00:00.0 +
+++ photoqt-3.3+ds/debian/patches/increase-pychromecast-test-timeout.patch
2023-06-19 07:17:44.0 +
@@ -0,0 +1,14 @@
+Description: Increase the timeout for the pychromecast test
+Author: Adrian Bunk
+
+--- photoqt-3.3+ds.orig/CMakeLists.txt
photoqt-3.3+ds/CMakeLists.txt
+@@ -370,7 +370,7 @@ if(CHROMECAST)
+ elseif(NOT ${Python3_Interpreter_FOUND})
+ message(FATAL_ERROR "** Unable to locate
Processed: Re: Bug#1038416: possible fix
Processing commands for cont...@bugs.debian.org: > severity 1038416 serious Bug #1038416 [proftpd-basic] proftpd-basic: proftpd service fails to start on next server reboot Severity set to 'serious' from 'normal' > tags 1038416 + patch bookworm Bug #1038416 [proftpd-basic] proftpd-basic: proftpd service fails to start on next server reboot Added tag(s) patch and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1038416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038450: patch probably available
Le mardi 20 juin 2023 à 22:38 +0200, Adrien Nader a écrit : > > > The patch seems to fix the issue. I say "seem" because the build > compiled the file that was failing to build but the build is not done > yet: emulated armhf isn't fast. :) > > But since I reprocued the build failure before, I am fairly confident > this build will succeed. I took the commit and added it to the Debian packaging ; I now have a 20230420-4 almost ready for upload. I'm waiting for two feedbacks before I do so : 1. yours so I trust it fixes the 32-bit issue ; 2. the sbuild I started on my box to check the patch on more usual architectures. Thanks for your help! J
Bug#1038160: googletest on armel
Investigating the armel build on the armmel porterbox
(abel.debian.org).
Commenting out line 1394 in gmock-matchers-misc_test.cc results in that
the test succeeds:
EXPECT_THAT(some_list, Contains(3).Times(2));
EXPECT_THAT(some_list, Contains(2).Times(1));
EXPECT_THAT(some_list, Contains(Ge(2)).Times(3));
// EXPECT_THAT(some_list, Contains(Ge(2)).Times(Gt(2)));
EXPECT_THAT(some_list, Contains(4).Times(0));
EXPECT_THAT(some_list, Contains(_).Times(4));
EXPECT_THAT(some_list, Not(Contains(5).Times(1)));
Compiling the unmodified file with -O1 insted of -O2 also results in
that the test succeeds.
The output of the test says:
[ RUN ] ContainsTimes.ListMatchesWhenElementQuantityMatches
./googlemock/test/gmock-matchers-misc_test.cc:1394: Failure
Value of: some_list
Expected: quantity of elements that match is >= 2 is > 3
Actual: { 3, 1, 2, 3 }, whose elements (0, 2, 3) match but whose
match quantity of 3 does not match
[ FAILED ] ContainsTimes.ListMatchesWhenElementQuantityMatches (0 ms)
Contains(Ge(2)).Times(Gt(2)) should mean:
Expected: quantity of elements that match is >= 2 is > 2
But according to the test output the actual test performed is
Expected: quantity of elements that match is >= 2 is > 3
which fails.
It looks like a compiler bug. With -O2 the line
EXPECT_THAT(some_list, Contains(Ge(2)).Times(Gt(2)));
is miscompiled as
EXPECT_THAT(some_list, Contains(Ge(2)).Times(Gt(3)));
Consider reporting this against gcc-12 package.
Mattias Ellert
signature.asc
Description: This is a digitally signed message part
Bug#1038764: src:crosshurd: fails to migrate to testing for too long: uploader built arch:all
Source: crosshurd Version: 1.7.58 Severity: serious Control: close -1 1.7.59 Tags: sid trixie pending 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 30 days as having a Release Critical bug in testing [1]. Your package src:crosshurd has been trying to migrate for 31 days [2]. Hence, I am filing this bug, but see my last paragraph. 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 trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=crosshurd OpenPGP_signature Description: OpenPGP digital signature
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2023-06-21 at 01:59 +, solneman33 wrote: > I downgraded to xkb-data=2.35.1-1 lightdm=1.26.0-8 from testing repo and > reinstalled xserver-xorg and xinit. That resolved the issue for me on both > machines. > > I've never reported a bug before, my apologies if this is incorrect > procedure. Well, can you check by reinstalling lightdm 1.32 but making sure you have xserver-xorg? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSnMIACgkQ3rYcyPpX RFs1Hwf9HgLiSwVwW4gMRS2ajXiUXmTRcgNe/jF5libmZllhhKXrMGlq2W/Whf7q 9oIjZ8BYq2x5M3y/VVCH9vYihxFRT6D9Fpg2yw9ojFmJDt0shJuYf2ErJ/2Ymbpy n5JO/1MXtEKbczhmu1ngc23Z9LzOxeuEiZwGJWZoFmhQDlkitD6uOWYByYA4LdA1 W+OsL7tVdE6rUMX9WPJ75mcIgp5+U8mC05Y/pH5+m40/55ZvD1mJotkt4ME6V6f7 fKggPqz8rVZukvXEiTp4oW5CGy/C4zqC5nWiPF8hY8rhZrwpEo9/VFBneEi5Ouze vzSQCUzeQvxMbA1VdXB4EL03t3rt2w== =Fg2s -END PGP SIGNATURE-
Processed: src:crosshurd: fails to migrate to testing for too long: uploader built arch:all
Processing control commands: > close -1 1.7.59 Bug #1038764 [src:crosshurd] src:crosshurd: fails to migrate to testing for too long: uploader built arch:all Marked as fixed in versions crosshurd/1.7.59. Bug #1038764 [src:crosshurd] src:crosshurd: fails to migrate to testing for too long: uploader built arch:all Marked Bug as done -- 1038764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037351: rust-base64 migration dependency adjustment
Hi Ian, On 21-06-2023 02:30, Ian Jackson wrote: Therefore I am tagging this bug trixie-ignore to avoid getting autoremoval warnings etc. As the rust-base64 migration seems to be just waiting (AFAIK at this moment) on rust-ruma-common autopkgtest-ing on ppc64el, I agree that this is OK. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2023-06-20 at 20:37 -0300, Adilson dos Santos Dantas wrote: > I tried to use 1.32 again and it only > generates /var/log/lightdm/lightdm.log. It doesn't generate seat0- > greeter.log and x-0.lo. From the log attached below, one difference is that > 1.26 starts seat0 and 1.32 does not start it. I got an X session from 1.26 > and X does not even start from 1.32. In the log there's definitely a bad sign: [+69.14s] DEBUG: Got signal 15 from process 1 [+69.14s] DEBUG: Caught Terminated signal, shutting down [+69.14s] DEBUG: Stopping display manager [+69.14s] DEBUG: Display manager stopped [+69.14s] DEBUG: Stopping daemon [+69.14s] DEBUG: Exiting with return value 0 Can you check also the system logs (/var/log/syslog, /var/log/daemon.log, the journal, dmesg...) so we have more information? Also is there something peculiar about your hardware (Nvidia/AMD GPU for example?) or software (specific configuration or something). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSmacACgkQ3rYcyPpX RFu3MQf9Hpnj5rWRK71USdZCS9Gx4vQZ+octjX/3TZWtlB8vb3eDbLAj4ZAEkZzZ YjyFBCOx2zSV7HbY2l7fgb9/q7njngHuFr/ux+Z8nxRsyWy4fkhdQKh/4mfOt7sy wDa7WH5y+z96f9ekBLtauWe7YBFocEiEFPsgQ6WApvLmNzMwl2oXFP/bTKBv6BWi NWe5//R4gdt2yDKHIlZrBWGQfItg4KzG6wUuBfkrz/53PicafeFxcrOcZILoYzJK PU6uWij2Imebdzq+02rgYWz0Qq7fqI3PxNNfiWq6fMMa+rWXM5cTEGs7XC//Vqe1 hHbM8JXrzsc2ZcMaYCQyJ0PaqnS18w== =4Egr -END PGP SIGNATURE-
Bug#1038648: marked as done (Xspice crashes on start)
Your message dated Wed, 21 Jun 2023 06:20:26 + with message-id and subject line Bug#1038648: fixed in xserver-xorg-video-qxl 0.1.6-1 has caused the Debian Bug report #1038648, regarding Xspice crashes on start 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.) -- 1038648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xspice Version: 0.1.5+git20200331-3 Severity: grave Justification: renders package unusable Since upgrading to bookworm, Xspice always crashes when I try to start it: Xspice --config xspice.1.conf :25 (EE) Caught signal 6 (Aborted). Server aborting Full log: xspice.1.log https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/issues/14 describes a similar problem and suggest to add some options in the config file. When I do this, I get a segfault instead: Xspice --config xspice.2.conf :25 (EE) Caught signal 11 (Segmentation fault). Server aborting Full log: xspice.2.log The page above mentions this too and refers to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1967719 That report was closed since they were "confident it was fixed in https://launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/0.1.5+git20200331-3;. However, the same version seems to be in bookworm (unless Debian made its own changes to it), and the problem does occur. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages xserver-xspice depends on: ii libc6 2.36-9 ii libspice-server1 0.15.1-1 ii libxfont2 1:2.0.6-1 ii python33.11.2-1+b1 ii xserver-xorg 1:7.7+23 ii xserver-xorg-core [xorg-video-abi-25] 2:21.1.7-3 xserver-xspice recommends no packages. xserver-xspice suggests no packages. -- no debconf information xspice.1.conf Description: Binary data xspice.1.log Description: Binary data xspice.2.conf Description: Binary data xspice.2.log Description: Binary data --- End Message --- --- Begin Message --- Source: xserver-xorg-video-qxl Source-Version: 0.1.6-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of xserver-xorg-video-qxl, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated xserver-xorg-video-qxl 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, 21 Jun 2023 08:58:45 +0300 Source: xserver-xorg-video-qxl Built-For-Profiles: noudeb Architecture: source Version: 0.1.6-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1038648 Changes: xserver-xorg-video-qxl (0.1.6-1) unstable; urgency=medium . * New upstream release. * patches: Drop obsolete patches. (Closes: #1038648) * watch: Updated. * Update signing-key.asc. Checksums-Sha1: 23a067a1d70d146e8366686d405f71e8ebdd216a 2305 xserver-xorg-video-qxl_0.1.6-1.dsc b6a097e30b9edc19291bb5b9e155859f8e5c4453 654220 xserver-xorg-video-qxl_0.1.6.orig.tar.gz 3a670f9b1f71177729dc771f2b495b5344a4f97e 16899 xserver-xorg-video-qxl_0.1.6-1.diff.gz a6c86e43cc294ed531956b96bbf8e90858ef392f 9883 xserver-xorg-video-qxl_0.1.6-1_source.buildinfo Checksums-Sha256: 6696faf82c2324e9e5866d806957c919b45bc820f6f5bd266113361649d4bd34 2305 xserver-xorg-video-qxl_0.1.6-1.dsc d582a4602b29baba1237d2da920825389249e92d060b183e27a5de90547aac54 654220 xserver-xorg-video-qxl_0.1.6.orig.tar.gz 2fcd6ef440c9517664ef3df9831ce4e1802802c8399ed4c192efdb7305c45f8e 16899
