Bug#1038450: patch probably available

2023-06-21 Thread julien . puydt
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

Bug#1038860: trafficserver: Wrong version for trafficserver security-update in DSA-5435-1

2023-06-21 Thread Salvatore Bonaccorso
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

Processed: trafficserver: Wrong version for trafficserver security-update in DSA-5435-1

2023-06-21 Thread Debian Bug Tracking System
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:

Bug#1038676: marked as done (rocsparse: binary-all FTBFS)

2023-06-21 Thread Debian Bug Tracking System
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.

Processed: fixed 1038723 in 0.4.0-2

2023-06-21 Thread Debian Bug Tracking System
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

Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0

2023-06-21 Thread Adilson dos Santos Dantas
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

Processed: your mail

2023-06-21 Thread Debian Bug Tracking System
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

Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion

2023-06-21 Thread Eriberto
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

Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion

2023-06-21 Thread Jody Bruchon
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

Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion

2023-06-21 Thread Eriberto
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

Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion

2023-06-21 Thread Tritech - Jody
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

2023-06-21 Thread Jody Bruchon
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)

2023-06-21 Thread Debian Bug Tracking System
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

Bug#1038450: patch probably available

2023-06-21 Thread Adrien Nader
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

Bug#1038759: marked as done (console-setup: Build against xkb-data 2.38-2 needed)

2023-06-21 Thread Debian Bug Tracking System
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

Processed: tagging 1038823

2023-06-21 Thread Debian Bug Tracking System
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. --

Bug#1037052: marked as done (minidlna: CVE-2023-33476)

2023-06-21 Thread Debian Bug Tracking System
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

Processed: tagging 1038823

2023-06-21 Thread Debian Bug Tracking System
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:

Bug#1038823: pysdl2: autopkgtest failure with SDL 2.28.0: cannot create a Renderer

2023-06-21 Thread Simon McVittie
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

Bug#1034683: marked as done (r-base: new upstream release unintentionally uploaded to unstable)

2023-06-21 Thread Debian Bug Tracking System
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

Bug#1034683: r-base: new upstream release unintentionally uploaded to unstable

2023-06-21 Thread Dirk Eddelbuettel
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

Bug#1038756: marked as done (librust-zbus-dev: impossible to install: depends on missing librust-quick-xml-0.26-dev)

2023-06-21 Thread Debian Bug Tracking System
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

Bug#1038723: marked as done (tiktoken FTBFS: error: failed to select a version for the requirement `pyo3 = "^0.17.3"`)

2023-06-21 Thread Debian Bug Tracking System
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

Bug#1038762: [src:systemd]: login (gnome) uses wrong keyboard layout

2023-06-21 Thread Lyndon Brown
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

Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0

2023-06-21 Thread Yves-Alexis Perez
-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

Bug#1034683: r-base: new upstream release unintentionally uploaded to unstable

2023-06-21 Thread Philip Rinn
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)

2023-06-21 Thread Debian Bug Tracking System
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

Bug#1038416: marked as done (proftpd-basic: proftpd service fails to start on next server reboot)

2023-06-21 Thread Debian Bug Tracking System
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

Processed: libsys-gamin-perl: Please consider removal

2023-06-21 Thread Debian Bug Tracking System
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

Processed: severity of 886087 is serious

2023-06-21 Thread Debian Bug Tracking System
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:

Bug#1038005: marked as done (vpoll-dkms: module fails to build for Linux 6.3)

2023-06-21 Thread Debian Bug Tracking System
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

Bug#1038793: unmaintained fork for jwt-go

2023-06-21 Thread Shengjing Zhu
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

Bug#1037480: marked as done (autopkgtest fails with golang-1.20)

2023-06-21 Thread Debian Bug Tracking System
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

Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0

2023-06-21 Thread Adilson dos Santos Dantas
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

Bug#1037472: marked as done (molmodel: FTBFS with gemmi 0.6.2+ds-1)

2023-06-21 Thread Debian Bug Tracking System
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

Bug#1034304: marked as done (geoalchemy2: autopkgtest regression on s390x: AssertionError)

2023-06-21 Thread Debian Bug Tracking System
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

Bug#1038737: FTBFS on mips64el: Unable to import PyChromecast

2023-06-21 Thread Dmitry Shachnev
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

Processed: reopening 1034732

2023-06-21 Thread Debian Bug Tracking System
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

Processed: severity of 1038759 is serious

2023-06-21 Thread Debian Bug Tracking System
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:

Processed: severity of 1031765 is normal

2023-06-21 Thread Debian Bug Tracking System
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:

Bug#1038776: dcmtk: fails to purge: rm: cannot remove '/var/lib/dcmtk/db/STORESCP': Is a directory

2023-06-21 Thread Andreas Beckmann
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

Bug#1038737: FTBFS on mips64el: Unable to import PyChromecast

2023-06-21 Thread Adrian Bunk
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

Processed: Re: Bug#1038416: possible fix

2023-06-21 Thread Debian Bug Tracking System
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

Bug#1038450: patch probably available

2023-06-21 Thread julien . puydt
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

Bug#1038160: googletest on armel

2023-06-21 Thread Mattias Ellert
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,

Bug#1038764: src:crosshurd: fails to migrate to testing for too long: uploader built arch:all

2023-06-21 Thread Paul Gevers
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

Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0

2023-06-21 Thread Yves-Alexis Perez
-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

Processed: src:crosshurd: fails to migrate to testing for too long: uploader built arch:all

2023-06-21 Thread Debian Bug Tracking System
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:

Bug#1037351: rust-base64 migration dependency adjustment

2023-06-21 Thread Paul Gevers
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.

Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0

2023-06-21 Thread Yves-Alexis Perez
-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

Bug#1038648: marked as done (Xspice crashes on start)

2023-06-21 Thread Debian Bug Tracking System
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