Bug#1037244: dhcpcd-ui: new upstream 0.7.9 release

[Martin-Éric Racine]

On Wed, Jun 21, 2023 at 8:11 AM Leandro Cunha  wrote:
> All open bugs have been closed including the one linked below, thanks
> for the feedback! I think it's very important when they come to me.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031092

The dependency on dhcpcd is sitll missing.

Also, as far as I can tell, upstream no longer ships a separate
dhcpcd-dbus. Unless I misread, this has been merged in dhcpcd-ui
(which can now produce a QT front-end in additon to the GTK one).

Martin-Éric

Bug#1037244: dhcpcd-ui: new upstream 0.7.9 release

[Leandro Cunha]

Hi,

On Sun, Jun 18, 2023 at 2:08 PM Martintxo  wrote:
>
> Hello!!
>
> I test dhcpcd-gtk 0.7.9-1 that is now in Sid, in a Emachines ancient laptop
> (i386) with stable (bookworm). In all my quick test all works as expected.
>
> First I test de Debian oficial binary package in that machine with an sysvinit
> init. All ok.
>
> Later I recompile the Debian oficial source package with gtk2, for work better
> in that old machine (fewer consumed resources). And I test it, first with
> sysvinit and later with systemd. It work ok, aswell, in both cases. Maybe it
> works better with systemd.
>
> My tests are to connect to my home wiffi and browse in internet. Later, I
> conect my mobile phone to the data connection and start the WIFI zone on it.
> With systemd dhcpcd detects almost immediately the new wifi network from my
> mobile. And with sysvinit it takes about a minute to detect the new network...
>
> But in both cases, it works as expected. And the feature of network changes is
> not important for me, normally I only conect to one network, and the change
> speed  is not important for me. So I will remain in sysvinit, that is ligther
> in that old box.
>
> Many thanks for your work in Debian. Greetings. Martintxo.
>
>
> 2023/06/09 08:24 (or.) eguna,
> Martin-Éric Racine (e)k idatzi zuen:
>
> > On Fri, Jun 9, 2023 at 7:53 AM Leandro Cunha 
> > wrote:
> > > Thank you, but I am already aware of this and leave this bug open that
> > > I must close it with the update.
> > > Just remember that I am a volunteer who helps the Debian QA team on
> > > unmaintained packages and I am not a maintainer of this package.
> >
> > Sure, no problem.
> >
> > Btw, Matintxo (above in CC) is one dhcpcd-ui user that I know of. He
> > would be in a good position to help you test any future commit before
> > uploads to Debian.
> >
> > Martin-Éric
>
>
> 
> Sustrai Erakuntza: respuesta jurídico-técnica a proyectos insostenibles.
>   proiektu jasangaitzei erantzun 
> juridiko-teknikoa.
>   https://www.fundacionsustrai.org
>   https://www.sustraierakuntza.org

All open bugs have been closed including the one linked below, thanks
for the feedback! I think it's very important when they come to me.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031092

-- 
Cheers,
Leandro Cunha

Bug#1038686: RFS: zpb-ttf/1.0.6-1 [QA] -- Access TrueType fonts with Common Lisp

[Leandro Cunha]

Hi,

On Tue, Jun 20, 2023 at 8:54 AM Bastian Germann  wrote:
>
> On Tue, 20 Jun 2023 03:11:39 -0300 Leandro Cunha  
> wrote:
> > [1] https://salsa.debian.org/leandrocunha/zpb-ttf
>
> Please drop this repo and work on the Vcs-Git one for future updates.
> I have invited you to join.

Thanks!
I didn't have permission to commit in the repository, but I usually
make the changes in a fork to test and then release.
Adam (kilobyte) had already uploaded when a rejection email arrived
here and thank you both!

-- 
Cheers,
Leandro Cunha
-BEGIN PGP PUBLIC KEY BLOCK-

mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN
pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh
0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR
gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd
A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas
sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb
RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7
ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD
w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S
eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm
hjAM8s+rUtG40mcUWePd8kZtgE9IV1eQ+Qt8/SNpSdRnUunmIGl3JjHvEwARAQAB
tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT
AQoAOBYhBLT5oBCvKN3HzFEPK8LZ4zKUW9A8BQJf4EPIAhsDBQsJCAcCBhUKCQgL
AgQWAgMBAh4BAheAAAoJEMLZ4zKUW9A8FjAQAKWYqiLpLUD+DLB+NSy3DI3rf9z3
k0vE7TLaEjdEM5CQWN+j4vBqMnAckdcARvSWPndTjp8K+mtFF4PyfhNbS64z/a7L
F3DdhmX73n7LKFG8Ow9NZwcrkmPwH5WcP7mXTh6R+6/+OSL/K85NB8MLlxQTJOni
julVax9JEZjwBaP2HLCu53Zq9gZcvJlXoAoTHyTxKdp8Mh8V+Qit26E78o9c6SQD
Dq9eyMRG8hYCRfreDjKceRkYHjECySlk+VoI1ssVs07Dqvxg6qSyP4RnW+1+W74C
s0yIyuC/eRJpMAf1PBQEOOrVcTfRfpN+go955t21yIAvT58vqotTM5eaqXYIQn/y
sC4lThZai/ZBZHxl5Mbv42WkkYdjisLQOCALIMBpj5nq4oh2C+kvMupcuBKfERgV
dguU51MzfQktKb6d5y777zYnDaFMQDD2IfiD/C7ln5A9LP/L54ixlA3uRmWx/yAx
/m+Zusws98j4Eq/jw5T54XW655m6lMCTE9WXLJkgxrRcEonHSllbgRSsToEmWq0Z
doxcnpagHdcGQzW+cu2VOGi1da73ZFmrn+ptJgc8cW2suO06IeArOi0TzIg7e65j
Xp2DbJCpFrfzEuBb1u71WvB8V2MkAfJZx/uZJPCA936B4HT8YGPEMzlQRIHI2Y9C
+DloyzlBLTS1EMKuuQINBF/gQ8gBEAC47o9u1Wm9jZ6RC+lfxEDEvVS7MmI5VzSy
q04rFttWwbKix13pc65aDlk47LxWrb84N3Gnf1E/OTsLTXqC7u5JZ7YJkC6CsPbo
D1sQkfCiJCFCTgf7dydEVt8ujS/Uu1kz86ufdRwaMRcvBZAORGdB58LEsLB65WN4
hLRYF7xvcxu6t7FGrIYereaxUAWLA2B/ZnCEdOY94w7s0uaPjHdf4lfHebuZ7T08
iG5ACDvKBjgaFArGfdNYWchXJgbOEg14bGj40/8LuBKQMZASiFSqLPZxoporK9FY
xBw+D080dUWWD5g868TZ3pkM3DXO9bdq22IBKqKOep8CnuKgoDpUvA8dTEY/UDCn
sdOlBUK/Y9zTGVmD/90cO/xkvkV78suqiBnwBSddPzVS0EuiWwrLGu8gaY4EyM/X
7khlbTcMgh4njzUCAE6Tq+TbXSxn86wuOybVY5Y+I99LNdsocI5SIn2nDh2IOi00
4dE/iwO2MatWIOLFBC7pw8Xv4UHZY+WIf3Y/6XjExpllhUkeB6BwZpTr1SXk+cug
q5Dj5i4aGn2LrvQJ57terqUWYyDUBFgXTc4SPOzT5og8CavBgHfrQoFwSnRZ2oyX
xtZhEDI5Pk2j1qTbOhXZ29po4rPNWHMq2HQgM0I+BqQndsoVdkPOFzS2wKkdXjCz
bNYcyanusQARAQABiQI2BBgBCgAgFiEEtPmgEK8o3cfMUQ8rwtnjMpRb0DwFAl/g
Q8gCGwwACgkQwtnjMpRb0Dzh6g//ZjXaWSzKmG5ZS6XJa/ZOokkE2hFOFusWX8Qa
hEwLAnTFEy02dLfV54rKwmu2jHPDKLhE+iYtusvytueZAzVRyQahv0RE4BH8Emqw
gQdBwyJ/L+QhUp/lMdJ6Hh/2ZSZmzU29U24vnY+U+haoB1fLnA3lXgOP59kMLGud
lERR2Vluuc7TcpzvcaRWgrQRU2vSrrBBEp6y07iVKbRM/9yhE/aHJahLbhKh2Dk9
WJvHPnhYJY5yU+Y5vTl3BiW5+EuzMBdPUawOWKhqCq9dswn0GL1g/vlt/bdU/6DO
jECQ6fssTAtDjRClXySsS3X0mh8y8qlGvMPB4anfvOy4+4nUV6IESdJftKn2SMGd
CA3MaQ+S7frWn5v7GIWSC9vumCsiu1JTOugLmbVmu5m5nFsyllavm/k9LtOtswuF
fHM/SlXLFuGBWU6XceqaM2dpP8i5jGz0vIGMhqoFNgXWGO1NhwR1rmeU1CMpnM5e
Wue4h/+mJiuEzuZcmzOcwq3HGMUXO0jZDgLEmlnenO9czhrLuGZaMXGdwnIk0G3O
+SqH36v7blnDh96RXpgaa+ifTHd0qKeoVXVwSq/9jNtHSQrI+NJcTpMhu73xtxhX
UFPr/31+IFLWepC5GDwdu/gQm5E6ntGyxE2p2v76pcjz7SGdXjPFZjqekBveEJuW
fNdY6Ns=
=rdCA
-END PGP PUBLIC KEY BLOCK-

Bug#1038689: pbuilder: creates /etc/pbuilderrc with invalid (debug repo) MIRRORSITE -- does not parse *.sources files

[Martin Pitt]

Hello all,

Thorsten Glaser [2023-06-20 19:39 +]:
> Ideally, let debootstrap use its default if no pbuilderrc.

Yes, agreed.

Thanks,

Martin

Bug#1038317: nautilus: new tab with ctrl+t keyboard set completely gray window

[Sergio Zamora]

Good day,


Got the same issue again without using nextcloud files, just opening 
another tab.


Here's the output log:


jun 20 22:50:43 debian nautilus[67044]: Trying to snapshot AdwFlap 
0x55bf3e8ee1d0 without a current allocation
jun 20 22:50:43 debian nautilus[67044]: Trying to snapshot AdwFlap 
0x55bf3e8ee1d0 without a current allocation
jun 20 22:50:43 debian nautilus[67044]: Trying to snapshot AdwFlap 
0x55bf3e8ee1d0 without a current allocation
jun 20 22:50:43 debian nautilus[67044]: Trying to snapshot AdwFlap 
0x55bf3e8ee1d0 without a current allocation
jun 20 22:50:43 debian nautilus[67044]: Trying to snapshot AdwFlap 
0x55bf3e8ee1d0 without a current allocation
jun 20 22:50:43 debian nautilus[67044]: Trying to snapshot AdwFlap 
0x55bf3e8ee1d0 without a current allocation
jun 20 22:50:43 debian systemd[2404]: Started 
vte-spawn-8042f708-1fa6-4dc4-af50-fcbedcaef432.scope - VTE child process 
77805 launched by kgx process 77783.
jun 20 22:50:43 debian gnome-shell[2716]: Window manager warning: Buggy 
client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x64
jun 20 22:50:44 debian gnome-shell[2716]: Can't update stage views actor 
[:0x55c789d6ed10] is on because it needs an 
allocation.
jun 20 22:50:44 debian gnome-shell[2716]: Can't update stage views actor 
[:0x55c789977240] is on because it needs 
an allocation.





Screenshot ( right after ctrl+t for a second tab )




Best Regards.



On 17-06-23 16:54, Simon McVittie wrote:

Control: tags -1 + moreinfo unreproducible

On Fri, 16 Jun 2023 at 23:51:04 -0400, zezamoral wrote:

* What led up to the situation?
 launch new tab with ctrl+t keyboard combination

I wasn't able to reproduce this issue on a fresh installation from
debian-live-12.0.0-amd64-gnome.iso using debian-installer, or on my usual
development system.

Is there anything special about the current directory when you see this
bug occur? I tried navigating to a directory with many files (/usr/bin)
but still didn't see it.

Are any warnings logged in the system log (systemd Journal) when this
happens? You can watch for new journal messages by running
"journalctl -f" in a Terminal window.


Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE

Is this the NVIDIA graphics drivers? If yes, I wonder whether that might
be relevant...

Thanks,
 smcv

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

[Eriberto]

Hi Adrian,

Initially, thanks for your help.

Em ter., 20 de jun. de 2023 às 18:18, Adrian Bunk  escreveu:
>
> Package: libjodycode2
> Version: 3.0.1-1
> Severity: serious
> Tags: ftbfs
> Control: affects -1 src:phcpack jdupes
>
> https://buildd.debian.org/status/fetch.php?pkg=phcpack=amd64=2.4.86%2Bdfsg-5=1687282110=0
>
> ...
> jdupes -l src/Python/PHCpy3/doc/build/html/_images/math
> jdupes: error while loading shared libraries: libjodycode.so.2: cannot open 
> shared object file: No such file or directory
> make[1]: *** [debian/rules:44: override_dh_auto_build-arch] Error 127


I packaged this lib after the freeze and I sent it to NEW queue in
June, 13. The package was approved in June, 15. However, the upstream
dropped the libjodycode2 in June, 16, releasing libjodycode3. The
jdupes in stable don't depend on a lib. jdupes 1.24 depends on the
libjodycode2 and the new jdupes 1.25 depends on the libjodycode3. I
uploaded libjodycode3 to unstable this morning, but jdupes was 1.24,
depending on the libjdupes2. Some hours after this, I uploaded jdupes
1.25.


> A shared library package libjodycode2 provides the shared library
> libjodycode.so.2, and not providing it breaks reverse dependencies.
>
> libjodycode2 must either provide libjodycode.so.2 by shipping it
> or depending on a package that does ship it, or libjodycode2 must
> be dropped. Anything other than dropping it would be highly unusual.


In at the moment, only jdupes depends of the libjodycode"X" on Debian,
so I think that libjodycode2 (transitional) must be dropped, right?
(jdupes 1.24 was replaced by jdupes 1.25, that depends of the
libjodycode3).


> A transitional package libjodycode2-dev would be possible,
> but there is no real benefit for a just created package.
>
> The -dev package should be named libjodycode-dev,
> which is a stable name.

What is the right way to make this? Renaming to libjodycode-dev,
dropping libjodycode3-dev and sending again to NEW? Should I use
Breaks and Replaces to make a reference to libjodycode3-dev?

Thanks for your attention.

Cheers,

Eriberto

Bug#1037238: debian-installer: separate /usr ruins opening a shell in rescue

[tomas k]

On Fri, 2023-06-09 at 13:32 +0200, Pascal Hambourg wrote:
> On 09/06/2023 at 01:27, tomas k wrote:
> > 
> > I'm on a different system than the problem one. For years I have
> > had to boot knoppix
> > and run a chroot to change a password I've forgotten, because I use
> > a separate usr partition,
> > and rescue thinks it's the root directory. Butr without etc it's
> > not going to work.
> 
> Rescue mode does not "think" anything about any partition. It is up
> to 
> the user to select the proper root partition, although I admit this 
> might be improved by providing more information about available 
> partitions to the user.
> 
> With /usr-merged layout (default since buster IIRC), a separate /usr 
> must be mounted before running any program. The initramfs mounts a 
> separate /usr before running init, but the installer rescue mode did
> not 
> before running a shell. This feature has been added to bookworm 
> installer (rescue 1.86) but not backported to bullseye installer
> AFAIK.
> 
That explains it. I can't open the root patitiion, because rescue
system says it's not a root partition until I try what is actually
/usr. But, I have finally given up separate /usr, and just lumped it in
with the pile. But in bookworm it should work?



> > My suggestion is, if a user wants a separate usr, to place a hidden
> > flag file in root, the presence of which
> > informs the system to mount THAT partition AND look in /etc/fstab,
> > and mount usr.
> 
> /etc/fstab already exists in the root filesystem, so no need to
> create a 
> flag file.

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

[solneman33]

I was able to reproduce with two of my machines running unstable.

xserver-xorg and xinit were removed during the upgrade and I wasn't aware.

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.

Regards,

Sent with [Proton Mail](https://proton.me/) secure email.

Bug#1038763: RFP: portmidi2 -- PortMidi - Cross-Platform MIDI IO

[Nicholas D Steeves]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: Paul Brossier , 
debian-multime...@lists.debian.org

* Package name: portmidi2
  Version : 2.0.4
  Upstream Author : Ross Bencina and Phil Burk, Roger B. Dannenberg
* URL : https://github.com/PortMidi/PortMidi
* License : Expat
  Programming Lang: C
  Description : PortMidi - Cross-Platform MIDI IO

PortMidi is a Cross-Platform MIDI IO that supports both real and
virtual midi input and output devices.

I recently learned that future releases of Hydrogen Drum Kit (v1.3.x
series) will depend on the new PortMIDI series.  The most recent
stable release of Hydrogen (1.2.1) depends on portmidi >=2; however,
it's still easy to patch Hydrogen to use Portmidi 217

To be honest, I'm not sure if a new source package will be required,
but I'm supposing that it will be necessary because we've had
portaudio "217" since 2016, and I assume that there will be many
breaking changes.  If this is not the case, please reasign this bug to
src:portmidi and make it a standard request for new upstream version.

Regards,
Nicholas

Bug#1038761: startx.1: a few remarks and editing fixes for the manual

[Guillem Jover]

Control: reassign -1 xinit

Hi!

[ It seems this got misfiled, leaving the bulk of the mail for context. ]

On Wed, 2023-06-21 at 00:30:04 +, Bjarni Ingi Gislason wrote:
> Package: dpkg
> Version: 1.21.22
> Severity: minor
> Tags: patch
> 
> Dear Maintainer,
> 
> here are a few notes and fixes for the manual.
> 
> ###
> 
> Input file is startx.1
> 
> Change two HYPHEN-MINUSES (code 0x055, 2D) to an em-dash (\(em), if one
> is intended.  An en-dash is usually surrounded by a space, while an em-dash
> is used without spaces. "man" (1 byte characters) transforms an en-dash
> (\(en to one HYPHEN-MINUS, and an em-dash to two HYPHEN-MINUSES without
> considering the space around it.
> If "--" are two single "-" (end of options) then use "\-\-".
> 
> startx.1:71:startx -- -depth 16
> startx.1:73:startx -- -dpi 100
> startx.1:75:startx -- -layout Multihead
> 
> #
> 
> Use the word (in)valid instead of (il)legal if not related to legal
> matters.
> See "www.gnu.org/prep/standards".
> Think about translations into other languages!
> 
> startx.1:68:the manual page for your X server to determine which arguments 
> are legal.
> 
> #
> 
> Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
> name for an option.
> 
> 57:.RB '--'
> 71:startx -- -depth 16
> 73:startx -- -dpi 100
> 75:startx -- -layout Multihead
> 
> #
> 
> Wrong distance between sentences.
> 
>   Separate the sentences and subordinate clauses; each begins on a new
> line.  See man-pages(7) ("Conventions for source file layout") and
> "info groff" ("Input Conventions").
> 
>   The best procedure is to always start a new sentence on a new line,
> at least, if you are typing on a computer.
> 
> Remember coding: Only one command ("sentence") on each (logical) line.
> 
> E-mail: Easier to quote exactly the relevant lines.
> 
> Generally: Easier to edit the sentence.
> 
> Patches: Less unaffected text.
> 
>   The amount of space between sentences in the output can then be
> controlled with the ".ss" request.
> 
> 87:is used to start the X session. All discussion of the
> 
> #
> 
> Split a punctuation mark from a single argument for a two-font macro
> 
> 92:.IR .xsession.
> 
> #
> 
> Output from "test-nroff -man -b -ww -z":
> 
> 
> [ "test-groff" is a developmental version of "groff" ]
> 
> Input file is ./startx.1
> 
> Output from test-groff -b -mandoc -dAD=l -rF0 -rHY=0 -t -w w -z :
> an.tmac:/tmp/chk_manuals.temp.Vnx9bq:57: style: .RB expects at least 2 
> arguments, got 1
> an.tmac:/tmp/chk_manuals.temp.Vnx9bq:92: style: .IR expects at least 2 
> arguments, got 1
> 
> 
> 
> --- startx.1  2023-06-20 23:50:11.0 +
> +++ startx.1.new  2023-06-21 00:13:05.0 +
> @@ -54,7 +54,7 @@ Arguments immediately following the
>  command are used to start a client in the same manner as
>  .BR xinit (1).
>  The special argument
> -.RB '--'
> +.RB ' \-\- '
>  marks the end of client arguments and the beginning of server options.
>  It may be convenient to specify server options with startx to change on a
>  per-session basis the
> @@ -65,14 +65,14 @@ permitted by the
>  server and specified in the
>  .BR xorg.conf (5)
>  configuration.  Some examples of specifying server arguments follow; consult
> -the manual page for your X server to determine which arguments are legal.
> +the manual page for your X server to determine which arguments are valid.
>  .RS
>  .PP
> -startx -- -depth 16
> +startx \-\- \-depth 16
>  .PP
> -startx -- -dpi 100
> +startx \-\- \-dpi 100
>  .PP
> -startx -- -layout Multihead
> +startx \-\- \-layout Multihead
>  .RE
>  .PP
>  Note that in the Debian system, what many people traditionally put in the
> @@ -84,12 +84,13 @@ instead; this permits the same X environ
>  .IR xdm ,
>  or
>  .I xinit
> -is used to start the X session. All discussion of the
> +is used to start the X session.
> +All discussion of the
>  .I .xinitrc
>  file in the
>  .IR xinit (1)
>  manual page applies equally well to
> -.IR .xsession.
> +.IR .xsession .
>  Keep in mind that
>  .I .xinitrc
>  is used only by

Thanks,
Guillem

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

[Michael Biebl]

Am 21.06.23 um 03:02 schrieb Michael Biebl:

Am 21.06.23 um 02:34 schrieb Lyndon Brown:

The latest package update (to unstable) has broken login keyboard-
layout support. I'm marking this as critical due to the chaotic
potential for locking many users out of their accounts / systems, some
of whom unlike myself may have no clue what's wrong and how to get
around it, if they can.


Afaics, this only affects gdm, which directly queries localed, which no 
longer reports the keymap state:



$ localectl
System Locale: LANG=C.UTF-8
     VC Keymap: (unset)
    X11 Layout: (unset)

This is a result of
https://salsa.debian.org/systemd-team/systemd/-/commit/8d0405b0cfb9c84791da5b8f7288453e23624acf


Hm, actually, it seems to be the result of dropping
debian/patches/debian/Use-Debian-specific-config-files.patch

See the discussion in 
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/189


As a quick/temporary workaround, you can run

ln -s /etc/default/keyboard /etc/vconsole.conf




OpenPGP_signature
Description: OpenPGP digital signature

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

[Michael Biebl]

Am 21.06.23 um 02:34 schrieb Lyndon Brown:

The latest package update (to unstable) has broken login keyboard-
layout support. I'm marking this as critical due to the chaotic
potential for locking many users out of their accounts / systems, some
of whom unlike myself may have no clue what's wrong and how to get
around it, if they can.


Afaics, this only affects gdm, which directly queries localed, which no 
longer reports the keymap state:



$ localectl
System Locale: LANG=C.UTF-8
VC Keymap: (unset)
   X11 Layout: (unset)

This is a result of
https://salsa.debian.org/systemd-team/systemd/-/commit/8d0405b0cfb9c84791da5b8f7288453e23624acf

See the discussion in 
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/189






OpenPGP_signature
Description: OpenPGP digital signature

Bug#1038648: Xspice crashes on start

[Frank Heckenbach]

Control: tags patch

I think I found the problem. It seems to be
Fix-a-build-error-with-Xorg-master.patch

To be honest, I don't really understand the patch. According to the
comment, instead of just changing one renamed parameter, it changes
the calling conventions at the cost of an unnecessary "slight
performance drop" in not one but three functions "for consistency"
and goes on to explain why it should work which sounds questionable
to me and apparently doesn't work after all.

So instead doing the simple thing seems to work. I suggest replacing
the patch with this one:

Index: xserver-xorg-video-qxl-0.1.5+git20200331/src/qxl_option_helpers.c
===
--- xserver-xorg-video-qxl-0.1.5+git20200331.orig/src/qxl_option_helpers.c
+++ xserver-xorg-video-qxl-0.1.5+git20200331/src/qxl_option_helpers.c
@@ -34,7 +34,7 @@ int get_bool_option(OptionInfoPtr option
 const char* value = getenv(env_name);
 
 if (!value) {
-return options[option_index].value.bool;
+return options[option_index].value.boolean;
 }
 if (strcmp(value, "0") == 0 ||
 strcasecmp(value, "off") == 0 ||

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

[Lyndon Brown]

package: src:systemd
version: 253-3
severity: critical

The latest package update (to unstable) has broken login keyboard-
layout support. I'm marking this as critical due to the chaotic
potential for locking many users out of their accounts / systems, some
of whom unlike myself may have no clue what's wrong and how to get
around it, if they can.

I'm from the UK and my locale / keyboard-layout is setup accordingly.

Systemd packages were updated from 252.11-1 to 253-3 today on my
unstable/sid system. I happened to hit an OOM condition that killed my
user session a little while after having installed these updates,
kicking me back to the Gnome login screen. I tried to log back in but I
couldn't. After many tries, confident I was typing in my password
correctly, and rebooting having made no difference, I toggled the
feature to see what I was typing and discovered that a certain special
character was not matching what I typed. I was able to find a key with
which to enter the correct symbol and thus was able to get back in. I
presume it's defaulting to US layout for some reason.

I checked out the updates that had been installed today and I then
tried downgrading all of the systemd packages (listed below) to those
from testing (252.11-1). This solves the problem.

With 253-3 installed, if I lock my account it seems to be using the
correct layout, but if I logout or reboot then it's using the wrong
one. With the 252.11-1 downgrade everything uses the correct layout
again. Reinstating 253-3 the problem is back, confirming that the
problem relates to the upgrade of systemd packages.

Apt package log (systemd only):
Install: systemd-dev:amd64 (253-3, automatic)
Upgrade: udev:amd64 (252.11-1, 253-3), systemd-container:amd64 (252.11-
1, 253-3), libnss-myhostname:amd64 (252.11-1, 253-3), libpam-
systemd:amd64 (252.11-1, 253-3), libsystemd0:amd64 (252.11-1, 253-3),
libudev-dev:amd64 (252.11-1, 253-3), systemd:amd64 (252.11-1, 253-3),
libudev1:amd64 (252.11-1, 253-3), libnss-mymachines:amd64 (252.11-1,
253-3), libsystemd-shared:amd64 (252.11-1, 253-3), systemd-sysv:amd64
(252.11-1, 253-3), libsystemd-dev:amd64 (252.11-1, 253-3)

Apt term log (systemd only):
Preparing to unpack .../0-libnss-mymachines_253-3_amd64.deb ...
Unpacking libnss-mymachines:amd64 (253-3) over (252.11-1) ...
Preparing to unpack .../1-systemd-container_253-3_amd64.deb ...
Unpacking systemd-container (253-3) over (252.11-1) ...
Preparing to unpack .../2-systemd-oomd_253-3_amd64.deb ...
Unpacking systemd-oomd (253-3) over (252.11-1) ...
Preparing to unpack .../3-libpam-systemd_253-3_amd64.deb ...
Unpacking libpam-systemd:amd64 (253-3) over (252.11-1) ...
Preparing to unpack .../4-systemd_253-3_amd64.deb ...
Unpacking systemd (253-3) over (252.11-1) ...
Preparing to unpack .../5-libsystemd-shared_253-3_amd64.deb ...
Unpacking libsystemd-shared:amd64 (253-3) over (252.11-1) ...
Preparing to unpack .../6-libsystemd0_253-3_amd64.deb ...
Unpacking libsystemd0:amd64 (253-3) over (252.11-1) ...
Setting up libsystemd0:amd64 (253-3) ...
Preparing to unpack .../archives/udev_253-3_amd64.deb ...
Unpacking udev (253-3) over (252.11-1) ...
Selecting previously unselected package systemd-dev.
Preparing to unpack .../systemd-dev_253-3_all.deb ...
Unpacking systemd-dev (253-3) ...
Setting up systemd-dev (253-3) ...
Setting up libsystemd-shared:amd64 (253-3) ...
Setting up systemd (253-3) ...
Installing new version of config file /etc/systemd/journald.conf ...
Installing new version of config file /etc/systemd/system.conf ...
Installing new version of config file /etc/systemd/user.conf ...
Preparing to unpack .../systemd-sysv_253-3_amd64.deb ...
Unpacking systemd-sysv (253-3) over (252.11-1) ...
Preparing to unpack .../libsystemd-dev_253-3_amd64.deb ...
Unpacking libsystemd-dev:amd64 (253-3) over (252.11-1) ...
Preparing to unpack .../libudev-dev_253-3_amd64.deb ...
Unpacking libudev-dev:amd64 (253-3) over (252.11-1) ...
Preparing to unpack .../libudev1_253-3_amd64.deb ...
Unpacking libudev1:amd64 (253-3) over (252.11-1) ...
Setting up libudev1:amd64 (253-3) ...
Preparing to unpack .../libnss-myhostname_253-3_amd64.deb ...
Unpacking libnss-myhostname:amd64 (253-3) over (252.11-1) ...
Setting up systemd-sysv (253-3) ...
Setting up udev (253-3) ...
Setting up libnss-myhostname:amd64 (253-3) ...
Setting up libudev-dev:amd64 (253-3) ...
Setting up systemd-container (253-3) ...
Setting up libpam-systemd:amd64 (253-3) ...
Setting up systemd-oomd (253-3) ...
Setting up libsystemd-dev:amd64 (253-3) ...
Setting up libnss-mymachines:amd64 (253-3) ...
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.3.0-1-amd64
Processing triggers for libc-bin (2.36-9) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for dbus (1.14.8-1) ...

I noticed that the systemd changelog for 253-rc2-1 states "make
/etc/default/locale a symlink to /etc/locale.conf". With 253-3
installed I indeed have this symlink (with owner 

Bug#1037351: rust-base64 migration dependency adjustment

[Ian Jackson]

Control: tags -1 + trixie-ignore

hippotat 1.1.7 FTBFS with rust-base64 0.21.
hippotat 1.1.9 build-depends on rust-base64 0.21.

So the plan is for these to migrate together, and ISTM from reading
tracker that that is what will happen as soon as the remaining
blockers for rust-bsee64 migration are disposed of.

In principle hippotat's build-dependencies could have been adjusted to
depend on rust-base64 0.13, and then we could have waited for that to
enter testing, and then done the update.  But thst seems otiose, given
that the plan is that trixie should have base64 0.21.

Therefore I am tagging this bug trixie-ignore to avoid getting
autoremoval warnings etc.  I hope I'm not overstepping the mark.

PS, with my upstream hat on: It is a shame that the Rust base64 crate
has such a cavalier approach to API stability.  I am considering my
options in this area for hippotat (eg data-encoding or base64ct), but
without better tests and test vectors I am reluctant to switch right
now.

Ian.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1038761: startx.1: a few remarks and editing fixes for the manual

[Bjarni Ingi Gislason]

Package: dpkg
Version: 1.21.22
Severity: minor
Tags: patch

Dear Maintainer,

here are a few notes and fixes for the manual.

###

Input file is startx.1

Change two HYPHEN-MINUSES (code 0x055, 2D) to an em-dash (\(em), if one
is intended.  An en-dash is usually surrounded by a space, while an em-dash
is used without spaces. "man" (1 byte characters) transforms an en-dash
(\(en to one HYPHEN-MINUS, and an em-dash to two HYPHEN-MINUSES without
considering the space around it.
If "--" are two single "-" (end of options) then use "\-\-".

startx.1:71:startx -- -depth 16
startx.1:73:startx -- -dpi 100
startx.1:75:startx -- -layout Multihead

#

Use the word (in)valid instead of (il)legal if not related to legal
matters.
See "www.gnu.org/prep/standards".
Think about translations into other languages!

startx.1:68:the manual page for your X server to determine which arguments are 
legal.

#

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

57:.RB '--'
71:startx -- -depth 16
73:startx -- -dpi 100
75:startx -- -layout Multihead

#

Wrong distance between sentences.

  Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").

  The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.

  The amount of space between sentences in the output can then be
controlled with the ".ss" request.

87:is used to start the X session. All discussion of the

#

Split a punctuation mark from a single argument for a two-font macro

92:.IR .xsession.

#

Output from "test-nroff -man -b -ww -z":


[ "test-groff" is a developmental version of "groff" ]

Input file is ./startx.1

Output from test-groff -b -mandoc -dAD=l -rF0 -rHY=0 -t -w w -z :
an.tmac:/tmp/chk_manuals.temp.Vnx9bq:57: style: .RB expects at least 2 
arguments, got 1
an.tmac:/tmp/chk_manuals.temp.Vnx9bq:92: style: .IR expects at least 2 
arguments, got 1



--- startx.12023-06-20 23:50:11.0 +
+++ startx.1.new2023-06-21 00:13:05.0 +
@@ -54,7 +54,7 @@ Arguments immediately following the
 command are used to start a client in the same manner as
 .BR xinit (1).
 The special argument
-.RB '--'
+.RB ' \-\- '
 marks the end of client arguments and the beginning of server options.
 It may be convenient to specify server options with startx to change on a
 per-session basis the
@@ -65,14 +65,14 @@ permitted by the
 server and specified in the
 .BR xorg.conf (5)
 configuration.  Some examples of specifying server arguments follow; consult
-the manual page for your X server to determine which arguments are legal.
+the manual page for your X server to determine which arguments are valid.
 .RS
 .PP
-startx -- -depth 16
+startx \-\- \-depth 16
 .PP
-startx -- -dpi 100
+startx \-\- \-dpi 100
 .PP
-startx -- -layout Multihead
+startx \-\- \-layout Multihead
 .RE
 .PP
 Note that in the Debian system, what many people traditionally put in the
@@ -84,12 +84,13 @@ instead; this permits the same X environ
 .IR xdm ,
 or
 .I xinit
-is used to start the X session. All discussion of the
+is used to start the X session.
+All discussion of the
 .I .xinitrc
 file in the
 .IR xinit (1)
 manual page applies equally well to
-.IR .xsession.
+.IR .xsession .
 Keep in mind that
 .I .xinitrc
 is used only by


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.27-1 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.8-5+b1
ii  libc62.36-9
ii  liblzma5 5.4.1-0.2
ii  libmd0   1.1.0-1
ii  libselinux1  3.4-1+b6
ii  libzstd1 1.5.4+dfsg2-5
ii  tar  1.34+dfsg-1.2
ii  zlib1g   1:1.2.13.dfsg-1

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt2.6.1
pn  debsig-verify  

-- no debconf information

Bug#1038760: aflplusplus: gcc-multilib is not available on all architectures

[Adrian Bunk]

Source: aflplusplus
Version: 4.07c-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=aflplusplus

The list of architectures where gcc-multilib is currently available is at:
https://salsa.debian.org/toolchain-team/gcc-defaults/-/blob/master/debian/control#L46

Bug#1038729: xkb-data: Upgrade wants to remove nVidia drivers

[Gunnar Hjalmarsson]

Control: tags -1 moreinfo

Hi Nicolas,

Nicolas Patrois wrote:

Upgrading xkb-data wants me to remove these automatically installed packages:


Are you talking about upgrading *to* xkb-data 2.35.1-1 or *from* 
xkb-data 2.35.1-1 to xkb-data 2.38-2?


Also, can you please show us the complete output of the command:

apt install xkb-data

--
Rgds,
Gunnar Hjalmarsson

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

[Adilson dos Santos Dantas]

Hi Yves-Alexis,

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.

Regards,

Adilson

Em ter., 20 de jun. de 2023 às 18:13, Yves-Alexis Perez 
escreveu:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Tue, 2023-06-20 at 12:45 +0200, Carlos Laviola wrote:
> > Package: lightdm
> > Followup-For: Bug #1038611
> >
> > Can't reproduce, starts up just fine for me.
> >
> > Could you perhaps include the logs from `/var/log/lightdm/´?
>
> Hi Adilson,
>
> I'm running 1.32 just fine since it was uploaded to experimental so I can't
> reproduce either. Logs would help indeed, and if you can investigate a bit
> more on your side (the info about downgrading helps identifying lightdm but
> besides that...)
>
> Regards,
> - --
> Yves-Alexis
> -BEGIN PGP SIGNATURE-
>
> iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSFncACgkQ3rYcyPpX
> RFuFvwgAlSLsGtGtw8gWLSKh9j53R90TnQFXO815eCtpu4v332YxbTEc8ZyqUPVF
> zndG+48/CWRtlhSi6PHlAorg3rMk7NgTSB29Oi1XD9Re3UX7z7Xvu/P92XbipzVg
> D0TqCHN34PkPqoImgoNoHVjdgzaJukgGcTMoTZqbU/EguAHudkDqnHdXKbps6JUA
> Pq1fXi2P6BP9nqDSpWjPmO4aA/o59Evb+D1q5MRHm43sZS3z9Vwj5zalLl2MiPG3
> 0EcBg/STIOV8Om+GBPYAsvQau4/3gWqyziVQw1/v4A8LYnH4BTLB+W6rVbHk/Fj6
> PKbmA5VO3GjJfl4LABIPkpAwkB+gwg==
> =SArv
> -END PGP SIGNATURE-
>


-- 
Adilson dos Santos Dantas
http://www.adilson.net.br
http://twitter.com/adilsond
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=30230
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/40-kde-plasma-kf5.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.00s] DEBUG: Monitoring logind for seats
[+0.00s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.00s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1004 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1005 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1003 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1002 added
[+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

Bug#1038693: qt6-declarative-dev: inappropriately included cmake file

[Lisandro Damián Nicanor Pérez Meyer]

Hi,

On Tue, 20 Jun 2023 at 09:42, Oswald Buddenhagen
 wrote:
>
> cmake files are necessary for static builds, because the "plugins"
> aren't actually plugins then. at least i'm assuming that this
> functionality wasn't lost during the cmake port ...
>
> plugins may also be listed as runtime dependencies for deployment.
> theoretically - whether that was actually implemented, i don't know.

Exactly, and these are not expected Debian targets...

> neither of these are immediately relevant for a regular desktop build,
> but you shouldn't be surprised when applications fail to build due to
> formally missing dependencies.

...but we already found a couple of examples on which they way the
CMake files are done you need to install them non the less. So ideally
we shouldn't ship the CMake files, but sometimes there is no way
around it :-/


-- 
Lisandro Damián Nicanor Pérez Meyer
https://perezmeyer.com.ar/

Bug#1037563: tech-ctte: Call for votes on TC membership of Timo Röhling

[Simon McVittie]

On Wed, 14 Jun 2023 at 10:04:54 +0100, Sean Whitton wrote:
> ===BEGIN
> The Technical Committee recommends that Timo Röhling  be
> appointed by the Debian Project Leader to the Technical Committee.
> 
> R: Recommend to appoint Timo Röhling 
> F: Further discussion
> ===END

I vote R > F.


signature.asc
Description: PGP signature

Bug#1037562: tech-ctte: Call for votes on TC membership of Stefano Rivera

[Simon McVittie]

On Wed, 14 Jun 2023 at 10:03:19 +0100, Sean Whitton wrote:
> ===BEGIN
> The Technical Committee recommends that Stefano Rivera  be
> appointed by the Debian Project Leader to the Technical Committee.
> 
> R: Recommend to appoint Stefano Rivera 
> F: Further discussion
> ===END

I vote R > F.

smcv


signature.asc
Description: PGP signature

Bug#1036858: bookworm-pu: package gnome-shell/43.6-1~deb12u1

[Simon McVittie]

On Wed, 07 Jun 2023 at 17:12:49 +0100, Simon McVittie wrote:
> On Sun, 28 May 2023 at 00:29:58 +0100, Simon McVittie wrote:
> > The gnome-shell 43.5 release from GNOME upstream seems like something
> > we should have in a bookworm update.
> 
> So does 43.6.
> 
> > This requires mutter 43.5, for which see #1036856.
> 
> Still true.
...
>   [ ] the issue is verified as fixed in unstable
>   - intentionally not done during the full freeze

As with mutter, I uploaded this to unstable after the bookworm release and
it has now reached testing. I've uploaded this in the hope that it can be
accepted into 12.1.

Updated debdiff attached.

smcv
git diff patch-queue/43.4.. | filterdiff -p1 -x'debian/patches/*.patch' -x.gitlab-ci.yml -x'.gitlab-ci/*' -x'po/*.po'

diffstat for gnome-shell-43.4 gnome-shell-43.6

 .gitlab-ci.yml|6 
 .gitlab-ci/install-meson-project.sh   |   84 
 NEWS  |   31 
 debian/changelog  |   56 
 debian/control|8 
 debian/control.in |8 
 debian/patches/Update-Abkhazian-translation.patch | 4910 --
 debian/patches/debian/Revert-build-Port-to-gcr4.patch |2 
 debian/patches/series |1 
 js/misc/ibusManager.js|2 
 js/misc/objectManager.js  |2 
 js/ui/appDisplay.js   |3 
 js/ui/components/autorunManager.js|2 
 js/ui/components/polkitAgent.js   |1 
 js/ui/dash.js |3 
 js/ui/dnd.js  |1 
 js/ui/messageTray.js  |5 
 js/ui/modalDialog.js  |2 
 js/ui/panelMenu.js|3 
 js/ui/screenshot.js   |8 
 js/ui/search.js   |7 
 js/ui/status/location.js  |2 
 js/ui/windowPreview.js|4 
 js/ui/workspacesView.js   |2 
 meson.build   |2 
 po/pt_BR.po   |  394 
 po/zh_CN.po   |  366 
 src/shell-app-system.c|   37 
 src/shell-window-preview-layout.c |4 
 subprojects/extensions-app/data/metainfo/org.gnome.Extensions.metainfo.xml.in |2 
 subprojects/extensions-app/generate-translations.sh   |2 
 subprojects/extensions-app/meson.build|2 
 subprojects/extensions-app/subprojects/shew/meson.build   |2 
 subprojects/extensions-tool/generate-translations.sh  |2 
 subprojects/extensions-tool/meson.build   |2 
 subprojects/shew/meson.build  |2 
 36 files changed, 634 insertions(+), 5336 deletions(-)

diff -Nru gnome-shell-43.4/debian/changelog gnome-shell-43.6/debian/changelog
--- gnome-shell-43.4/debian/changelog	2023-04-10 14:07:38.0 +0100
+++ gnome-shell-43.6/debian/changelog	2023-06-11 00:08:43.0 +0100
@@ -1,3 +1,59 @@
+gnome-shell (43.6-1~deb12u1) bookworm; urgency=medium
+
+  * Rebuild for bookworm
+
+ -- Simon McVittie   Sun, 11 Jun 2023 00:08:43 +0100
+
+gnome-shell (43.6-1) unstable; urgency=medium
+
+  * New upstream stable release 43.5
+- Fix a regression in 43~beta involving detection of hotplugged media
+  with autorunnable content (gnome-shell!2745)
+- Make search results fill unused space as intended (gnome-shell#5924)
+- Improve matching of app StartupWMClass to a .desktop file, giving
+  priority to apps that were not hidden by OnlyShowIn under the current
+  desktop environment, in particular preferring gnome-system-monitor's
+  non-KDE-specific .desktop file while running GNOME (gnome-shell!2721)
+

Bug#1036856: bookworm-pu: package mutter/43.6-1~deb12u1

[Simon McVittie]

On Wed, 21 Jun 2023 at 00:06:15 +0100, Simon McVittie wrote:
> On Wed, 07 Jun 2023 at 17:05:37 +0100, Simon McVittie wrote:
> > On Sun, 28 May 2023 at 00:15:26 +0100, Simon McVittie wrote:
> > > The mutter 43.5 release from GNOME upstream seems like something we should
> > > have in a bookworm update.
> > 
> > So does the 43.6 release.
> 
> Updated debdiff attached (everything is the same as mutter_43.6-pre.diff,
> except for debian/changelog)

Really attached now...

smcv
diffstat for mutter-43.4 mutter-43.6

 NEWS  |   21 
 debian/changelog  |   27 
 debian/libmutter-11-0.symbols |1 
 debian/patches/Update-Abkhazian-translation.patch | 4262 --
 debian/patches/clutter-actor-Get-next-action-from-list-before-handling-c.patch|   51 
 debian/patches/cursor-tracker-Don-t-leak-window-cursor-on-exit.patch  |   22 
 debian/patches/debian/Mark-xwayland-test-case-as-known-to-be-flaky-on-32-bit-AR.patch |4 
 debian/patches/debian/meson-Do-not-mark-CI-test-tools-as-required.patch   |4 
 debian/patches/debian/tests-Disable-restore-size-test.patch   |4 
 debian/patches/debian/tests-Tag-unstable-tests-as-flaky.patch |4 
 debian/patches/meson-add-back-default_driver-option.patch |6 
 debian/patches/series |7 
 debian/patches/tests-Break-up-stacking-installed-tests-into-more-smaller.patch|4 
 debian/patches/wayland-Skip-subsurface-desync-if-parent-is-NULL.patch |   35 
 debian/patches/wayland-cursor-surface-Update-cursor-on-dispose.patch  |  701 -
 debian/patches/wayland-outputs-Fix-potential-crash-when-output-has-no-mo.patch|   40 
 debian/patches/wayland-xdg-shell-Dismiss-instead-of-destroy-invalid-popu.patch|   28 
 meson.build   |2 
 src/backends/meta-screen-cast-window-stream.c |   14 
 src/backends/meta-screen-cast-window.c|   12 
 src/backends/meta-screen-cast-window.h|6 
 src/backends/native/meta-kms-impl-device-dummy.c  |7 
 src/compositor/meta-compositor-view.c |2 
 src/compositor/meta-surface-actor-wayland.c   |   50 
 src/compositor/meta-window-actor-private.h|2 
 src/compositor/meta-window-actor.c|   32 
 src/core/window-private.h |2 
 src/meta/window.h |3 
 src/wayland/meta-wayland-actor-surface.c  |   17 
 src/wayland/meta-wayland-outputs.c|7 
 30 files changed, 229 insertions(+), 5148 deletions(-)

diff -Nru mutter-43.4/debian/changelog mutter-43.6/debian/changelog
--- mutter-43.4/debian/changelog	2023-04-21 10:10:24.0 +0100
+++ mutter-43.6/debian/changelog	2023-06-10 22:59:13.0 +0100
@@ -1,3 +1,30 @@
+mutter (43.6-1~deb12u1) bookworm; urgency=medium
+
+  * Rebuild for bookworm
+
+ -- Simon McVittie   Sat, 10 Jun 2023 22:59:13 +0100
+
+mutter (43.6-1) unstable; urgency=medium
+
+  * New upstream stable release 43.5
+- Always update surfaces belonging to a window that is being recorded
+  or included in a screencast, even if the window is not visible
+  on a local display (mutter#2538, mutter!2789)
+- Export previously-private meta_window_has_pointer(), needed by
+  screenshot UI fixes in gnome-shell 43.5 (mutter!2928)
+  + d/libmutter-11-0.symbols: Update to add that symbol
+- All other changes were already present in 43.4-2
+  * New upstream stable release 43.6
+- Fix a resource leak when a compositor view is destroyed (mutter!2991)
+- Fix a crash when headless gdm greeter via gnome-remote-desktop
+  attempts to blank the screen (mutter#2841)
+  * d/patches: Drop patches that were applied upstream
+  * d/p/wayland-outputs-Fix-potential-crash-when-output-has-no-mo.patch:
+Backport patch from 44~beta to fix a crash during suspend/resume on
+some systems (mutter#2570, Closes: #1036268)
+
+ -- Simon McVittie   Sat, 10 Jun 2023 21:17:19 +0100
+
 mutter (43.4-2) unstable; urgency=medium
 
   * Team upload
diff -Nru mutter-43.4/debian/libmutter-11-0.symbols 

Bug#1036856: bookworm-pu: package mutter/43.6-1~deb12u1

[Simon McVittie]

On Wed, 07 Jun 2023 at 17:05:37 +0100, Simon McVittie wrote:
> On Sun, 28 May 2023 at 00:15:26 +0100, Simon McVittie wrote:
> > The mutter 43.5 release from GNOME upstream seems like something we should
> > have in a bookworm update.
> 
> So does the 43.6 release.
...
>   [ ] the issue is verified as fixed in unstable
>   - intentionally not done yet, due to full freeze

I uploaded the version from which this is a backport after the bookworm
release, and it has now migrated to testing.

Updated debdiff attached (everything is the same as mutter_43.6-pre.diff,
except for debian/changelog). I've uploaded this version in the hope that
it will be accepted.

I have only tested this and gnome-shell (#1036858) together, so please
accept both or neither.

smcv

Bug#1038388: shotcut: Shotcut 23 timeline widget is blank

[david]

On Mon, 19 Jun 2023 20:34:32 -0400 Doug Larrick  wrote:
> On Mon, 19 Jun 2023 15:46:40 +0200
> Gürkan Myczko  wrote:
> > I've uploaded -2 which should prevent more users running into the
> > same issue.
> > I hope to get to test/check the packaging rest of the week...
> > 
> 
> Hmm, it seems you've named some packages that don't exist. See attached.

I have installed shotcut version 23.06.14+git20230616+ds-3, that fixes that
problem too, but shotcut itself doesn't work yet. The timeline is not usable in
my system :(

-- 
David

Bug#1038759: console-setup: Build against xkb-data 2.38-2 needed

[Gunnar Hjalmarsson]

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

Bug#1038758: pymupdf FTBFS with mupdf 1.22.1

[Adrian Bunk]

Source: pymupdf
Version: 1.21.1+ds1-1
Severity: serious
Tags: ftbfs trixie sid

https://buildd.debian.org/status/logs.php?pkg=pymupdf=1.21.1%2Bds1-1%2Bb3

...
x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g 
-fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/mupdf -I/usr/local/include/mupdf -I/usr/include/freetype2 
-I/usr/include/python3.11 -c fitz/fitz_wrap.c -o 
build/temp.linux-x86_64-cpython-311/fitz/fitz_wrap.o 
-Wno-incompatible-pointer-types -Wno-pointer-sign -Wno-sign-compare
fitz/fitz_wrap.c: In function ‘JM_filter_content_stream’:
fitz/fitz_wrap.c:9228:27: error: ‘pdf_filter_options’ has no member named 
‘sanitize’
 9228 | if (filter->sanitize) {
  |   ^~
fitz/fitz_wrap.c:9230:39: warning: implicit declaration of function 
‘pdf_new_filter_processor’; did you mean ‘pdf_new_buffer_processor’? 
[-Wimplicit-function-declaration]
 9230 | proc_filter = pdf_new_filter_processor(ctx, 
doc, proc_buffer, in_res, *out_res, struct_parents, transform, filter);
  |   ^~~~
  |   pdf_new_buffer_processor
fitz/fitz_wrap.c:9230:37: warning: assignment to ‘pdf_processor *’ from ‘int’ 
makes pointer from integer without a cast [-Wint-conversion]
 9230 | proc_filter = pdf_new_filter_processor(ctx, 
doc, proc_buffer, in_res, *out_res, struct_parents, transform, filter);
  | ^
fitz/fitz_wrap.c:9231:25: error: too few arguments to function 
‘pdf_process_contents’
 9231 | pdf_process_contents(ctx, proc_filter, doc, 
in_res, in_stm, NULL);
  | ^~~~
In file included from /usr/include/mupdf/pdf/page.h:26,
 from /usr/include/mupdf/pdf.h:38,
 from fitz/fitz_wrap.c:3077:
/usr/include/mupdf/pdf/interpret.h:403:6: note: declared here
  403 | void pdf_process_contents(fz_context *ctx, pdf_processor *proc, 
pdf_document *doc, pdf_obj *obj, pdf_obj *res, fz_cookie *cookie, pdf_obj 
**out_res);
  |  ^~~~
fitz/fitz_wrap.c:9235:25: error: too few arguments to function 
‘pdf_process_contents’
 9235 | pdf_process_contents(ctx, proc_buffer, doc, 
in_res, in_stm, NULL);
  | ^~~~
/usr/include/mupdf/pdf/interpret.h:403:6: note: declared here
  403 | void pdf_process_contents(fz_context *ctx, pdf_processor *proc, 
pdf_document *doc, pdf_obj *obj, pdf_obj *res, fz_cookie *cookie, pdf_obj 
**out_res);
  |  ^~~~
fitz/fitz_wrap.c: In function ‘JM_image_reporter’:
fitz/fitz_wrap.c:9259:11: error: ‘pdf_filter_options’ has no member named 
‘text_filter’
 9259 | filter.text_filter = NULL;
  |   ^
fitz/fitz_wrap.c:9260:11: error: ‘pdf_filter_options’ has no member named 
‘image_filter’
 9260 | filter.image_filter = JM_image_filter;
  |   ^
fitz/fitz_wrap.c:9261:11: error: ‘pdf_filter_options’ has no member named 
‘end_page’
 9261 | filter.end_page = NULL;
  |   ^
fitz/fitz_wrap.c:9264:11: error: ‘pdf_filter_options’ has no member named 
‘sanitize’
 9264 | filter.sanitize = 1;
  |   ^
fitz/fitz_wrap.c: In function ‘Document_has_xref_streams’:
fitz/fitz_wrap.c:11958:20: error: ‘pdf_document’ {aka ‘struct pdf_document’} 
has no member named ‘has_xref_streams’
11958 | if (pdf->has_xref_streams) Py_RETURN_TRUE;
  |^~
fitz/fitz_wrap.c: In function ‘Document_has_old_style_xrefs’:
fitz/fitz_wrap.c:11964:20: error: ‘pdf_document’ {aka ‘struct pdf_document’} 
has no member named ‘has_old_style_xrefs’
11964 | if (pdf->has_old_style_xrefs) Py_RETURN_TRUE;
  |^~
fitz/fitz_wrap.c: In function ‘Page_clean_contents’:
fitz/fitz_wrap.c:14662:17: warning: initialization of ‘int’ from ‘void *’ makes 
integer from pointer without a cast [-Wint-conversion]
14662 | NULL,  // opaque
  | ^~~~
fitz/fitz_wrap.c:14662:17: note: (near initialization for ‘filter.recurse’)
fitz/fitz_wrap.c:14663:17: warning: initialization of ‘int’ from ‘void *’ makes 
integer from pointer without a cast [-Wint-conversion]
14663 | NULL,  // image filter
  | ^~~~
fitz/fitz_wrap.c:14663:17: note: (near initialization for 
‘filter.instance_forms’)
fitz/fitz_wrap.c:14664:17: warning: initialization of ‘int’ from ‘void *’ makes 
integer from pointer without a cast [-Wint-conversion]
14664 | NULL,  // text filter
  | ^~~~
fitz/fitz_wrap.c:14664:17: note: (near initialization for ‘filter.ascii’)
fitz/fitz_wrap.c:14665:17: warning: 

Bug#1038749: Acknowledgement (foxtrotgps: new upstream commit)

[Bastian Germann]

I am uploading a LowNMU to DELAYED/10 to fix this. The debdiff is attached.diff -Nru foxtrotgps-1.2.2+bzr331/changelog/ChangeLog 
foxtrotgps-1.2.2+bzr332/changelog/ChangeLog
--- foxtrotgps-1.2.2+bzr331/changelog/ChangeLog 2021-08-17 14:19:23.0 
+0200
+++ foxtrotgps-1.2.2+bzr332/changelog/ChangeLog 2023-06-20 23:47:03.0 
+0200
@@ -1,4 +1,15 @@
 
+revno: 332
+committer: Paul Wise 
+branch nick: bzr
+timestamp: Wed 2023-05-17 09:38:04 +0800
+message:
+  Add support for gpsd API version 12
+
+  Reported-by: Boian Bonev 
+modified:
+  src/gps_functions.c
+
 revno: 331
 fixes bug: https://launchpad.net/bugs/1876744
 author: Jesse Gardner 
diff -Nru foxtrotgps-1.2.2+bzr331/debian/changelog 
foxtrotgps-1.2.2+bzr332/debian/changelog
--- foxtrotgps-1.2.2+bzr331/debian/changelog2021-08-17 14:24:50.0 
+0200
+++ foxtrotgps-1.2.2+bzr332/debian/changelog2023-06-20 23:37:19.0 
+0200
@@ -1,3 +1,10 @@
+foxtrotgps (1.2.2+bzr332-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream snapshot. (Closes: #1038749)
+
+ -- Bastian Germann   Tue, 20 Jun 2023 23:37:19 +0200
+
 foxtrotgps (1.2.2+bzr331-1) unstable; urgency=medium
 
   * New upstream snapshot.
diff -Nru foxtrotgps-1.2.2+bzr331/src/gps_functions.c 
foxtrotgps-1.2.2+bzr332/src/gps_functions.c
--- foxtrotgps-1.2.2+bzr331/src/gps_functions.c 2021-08-17 08:01:48.0 
+0200
+++ foxtrotgps-1.2.2+bzr332/src/gps_functions.c 2023-05-17 03:38:04.0 
+0200
@@ -762,7 +762,9 @@
{
gpsdata->fix.time = (time_t) 0;
}
-#if GPSD_API_MAJOR_VERSION >= 10
+#if GPSD_API_MAJOR_VERSION >= 12
+   gpsdata->valid = (libgps_gpsdata.fix.status != STATUS_UNK || 
libgps_gpsdata.fix.mode >= MODE_2D);
+#elif GPSD_API_MAJOR_VERSION >= 10
gpsdata->valid = (libgps_gpsdata.fix.status != STATUS_NO_FIX || 
libgps_gpsdata.fix.mode >= MODE_2D);
 #else
gpsdata->valid = (libgps_gpsdata.status != STATUS_NO_FIX);

Bug#1038757: Package: rio

[Raphael Amorim]

Package: rio

Dear mentors,

I am looking for a sponsor for my package "rio":

 * Package name : rio (or alternatively rio-term)
   Version  : 0.0.7
   Upstream contact : Raphael Amorim 
 * URL  : https://raphamorim.io/rio/
 * License  : MIT
 * Vcs  : https://github.com/raphamorim/rio

The source builds the following binary packages:
https://github.com/raphamorim/rio/releases

To access further information about this package, please visit the
following URL:
https://raphamorim.io/rio/docs

Changes since the last upload:


   - Fix Background color not entirely set on vim #88
   
   - Scroll now works for x11 and wayland.
   - No longer renders to macos and x11 windows that are fully occluded /
   not directly visible.
   - Introduced window-opacity config property for WebAssembly and Wayland
   builds.
   - Add permissions instructions to Rio macos builds (Fix #99
   ).
   - Fixes for x11 and wayland rendering (Related: #98
    and #100
   ).
   - Performance fixes (Related: #101
   ).
   - Sugarloaf WebAssembly support.
   - Fixed resize for all contexts: removed the glitch when resizing and
   switching between tabs.
   - Fixed cursor inconsistencies #95
   .
   - Added command line interface support (--help, --version, -e and
   --command).
   - Added a fallback for WPGU request device operation: downlevel limits,
   which will allow the code to run on all possible hardware.
   - Added padding-x to configuration.
   - Reload automatically when the configuration file is changed (#69
   ).
   - Fix Ctrl+D.
   - Fix exit command not closing the app (#87
   ).
   - Changed default light-black color.

Regards,
-- 
  R. Amorim

Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

[Luca Boccassi]

On Sun, 18 Jun 2023 13:38:12 +0100 Luca Boccassi 
wrote:
> On Sun, 18 Jun 2023 at 13:03, Sean Whitton 
wrote:
> >
> > Hello,
> >
> > On Fri 16 Jun 2023 at 05:57PM +01, Luca Boccassi wrote:
> >
> > > Is there anything needed from me to make progress on this? Any
changes
> > > required to the last revision posted?
> >
> > Yes, Russ posted some comments on your most recent revision, I
believe.
> 
> Last one I can find with specifics is:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945269#140
> 
> Which I think I have addressed in a follow-up. Did I miss something?

Russ, anything I've missed that you want me to change from the most
recent revision at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945269#160 ?

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

Bug#1034903: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin navi10_mes.bin for module amdgpu

[Ben Hutchings]

On Thu, 27 Apr 2023 15:43:28 +0800 xiao sheng wen(肖盛文）
 wrote:
> Package: firmware-amd-graphics
> Version: 20230310-1~exp1
> Severity: normal
> X-Debbugs-Cc: atzli...@sina.com
> 
> Hi,
> 
>  When I upgrade to kernel 5.10.0-22-arm64, there are following error
>  infos:
> 
> W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for 
> module amdgpu
> W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
> amdgpu
[...]

I see that the amdgpu driver has had references to these files for
several years, but they've never been added to linux-firmware.git.
More recently amdgpu added:

MODULE_FIRMWARE("amdgpu/gc_11_0_3_mes.bin");
MODULE_FIRMWARE("amdgpu/gc_11_0_3_mes_2.bin");
MODULE_FIRMWARE("amdgpu/gc_11_0_3_mes1.bin");

and these are also missing from linux-firmware.git.

Is this firmware intended to be available to the public?

Ben.

-- 
Ben Hutchings
compatible: Gracefully accepts erroneous data from any source



signature.asc
Description: This is a digitally signed message part

Bug#1038753: udev should not depend on systemd-dev?

[Luca Boccassi]

Control: tags -1 wontfix
Control: close -1

On Tue, 20 Jun 2023 23:24:48 +0200 Diederik de Haas
 wrote:
> Package: udev
> Version: 253-2
> Severity: normal
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On the upgrade of systemd/udev to 253-2 (or -3), aptitude now wants
to
> install systemd-dev as that's (now) a dependency of udev.
> 
> But shouldn't systemd-dev (Section: devel) only be installed when you
> want to develop *for* systemd?
> AFAIK, *-dev packages should not be *runtime* dependencies?
> 
> If systemd-dev is indeed intended to be a runtime dependency of udev,
> feel free to close this bug report.

It's intended. It's just pkg-config files for now, and if anything is
added in the future, it will be more static arch-independent stuff. It
doesn't make sense to have an udev-specific package for a single pkg-
config file, and if one is needed, most likely the other is needed too,
to get files installation paths.
And the dependency is there because files moved, so it would break
reverse dependencies expecting to find them. Also they are intended to
be available at runtime too, for scripts that want to know where to
install things.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

Bug#1038115: transition: gdal

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2023-06-15 17:15:27 +0200, Bas Couwenberg wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: g...@packages.debian.org
> Control: affects -1 + src:gdal
> Control: forwarded -1 
> https://release.debian.org/transitions/html/auto-gdal.html
> Control: block -1 by 1030129 998833 1037920 984398 1037976
> 
> For the Debian GIS team I'd like to transition to GDAL 3.7.0.

Please go ahead.

Cheers
-- 
Sebastian Ramacher

Bug#1037474: transition: openmm

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2023-06-13 11:20:02 +0300, Andrius Merkys wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hello,
> 
> I would like to request a transition slot for openmm
> (experimental -> unstable) due to soname bump. Current ben tracker [1]
> is OK.

Please go ahead

Cheers
-- 
Sebastian Ramacher

Bug#1038720: Missing hyperv_fb.ko in debian 12.0 kernel image 6.1.0-9-amd64

[Bastian Blank]

On Tue, Jun 20, 2023 at 06:50:10PM +0200, Ben Hutchings wrote:
> > This was replaced by hyperv_drm, which provides a standard mode
> > selection output.
> ...although we do still build hyperv_fb for the cloud-amd64 flavour,
> which seems like a mistake.

Because the cloud-amd64 flavour disables DRM alltogether.

Bastian

-- 
Each kiss is as the first.
-- Miramanee, Kirk's wife, "The Paradise Syndrome",
   stardate 4842.6

Bug#1038756: librust-zbus-dev: impossible to install: depends on missing librust-quick-xml-0.26-dev

[Jonas Smedegaard]

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-

Bug#1038755: rust-trivialdb FTBFS on architectures where char is unsigned

[Adrian Bunk]

Source: rust-trivialdb
Version: 0.1.1-1
Severity: important
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=rust-trivialdb=0.1.1-1

...
[trivialdb 0.1.1] /usr/include/aarch64-linux-gnu/sys/types.h:69:18: error: 
typedef redefinition with different types ('__mode_t' (aka 'unsigned int') vs 
'int')
[trivialdb 0.1.1] /<>/tdb.h:1:13: note: previous definition is here
...

Bug#1038754: random hangs during boot inside qemu

[Johannes Schauer Marin Rodrigues]

Source: linux
Severity: normal
Tags: patch

Hi,

the jenkins job of my package mmdebstrap spawns ~260 qemu virtual
machines on amd64 to run the test cases in. For about a week now I'm
seeing random (about every ~300) hangs during boot. The effect can be
seen in these logs:

 - https://jenkins.debian.net/job/mmdebstrap-jenkins-worker/311/consoleText
 - https://jenkins.debian.net/job/mmdebstrap-jenkins-worker/313/consoleText
 - https://jenkins.debian.net/job/mmdebstrap-jenkins-worker/314/consoleText

Ctrl+F the logs for "qemu-system-x86_64: terminating on signal 15 from
pid XXX (timeout)".

On #debian-devel, f_g suggested that this is a fixed problem:

https://lore.kernel.org/stable/c4724b40-89f6-5aa7-720d-c4a4af57c...@amazon.com/#r
https://lore.kernel.org/all/5a56290d-806e-b9a5-f37c-f21958b5a...@grsecurity.net
https://lore.kernel.org/stable/20230615091830.rxmv2...@linutronix.de/

Is there a chance to see a stable update with
e9523a0d81899361214d118ad60ef76f0e92f71d applied?

Thanks!

cheers, josch

Bug#1038701: lightdm logs "lightdm[1166]: gkr-pam: unable to locate daemon control file" error on boot

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

control: forwarded -1 https://github.com/canonical/lightdm/issues/70

On Tue, 2023-06-20 at 12:44 +0300, Yura wrote:
> Dear Maintainer,
> 
> I've noticed that on boot system logs the "lightdm[1166]: gkr-pam: unable to
> locate daemon control file" error message from lightdm, which indicates that
> there is some issue.
> 
> Nevertheless, the booting process succeeds.
> 
> The expectation is that such error shouldn't occur.

Hey,
 
this looks to be https://github.com/canonical/lightdm/issues/70 but there's
not definite conclusion in that issue. It looks like gnome-keyring is launched
for the lightdm user but lacks space to write some files. I don't think we
really need gnome-keyring as part of the lightdm session anyway so I don't
think it's really problematic, mostly cosmetic at that point.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSGOMACgkQ3rYcyPpX
RFu2mwgAtSXk2CbNNaPObACSEhVIbL3uZYFPMDyHucZQ2vXYYp/occiOlAaf1rNF
efANrjxSFNngBuGrGvWyki5uGyw14GHKudSb4KJgg6qMbW4meCES4cvf/m6VP+p8
Is2Vbj6Dk4c3c0+JEZyWJD6Me9h6nMhu1g4RAyrxPo3K6kzbmcsWx2ZzAr3Yo686
NyrEy0jdBuea/C/eBh4q+fFNVB6BnXkwLBDYd0vHes/V3lfxAxG9Wv08L47B5elP
ixr2pfX0Bx6h4thaloj8C88PR2sDNgGM95CJHktxKxX7By8tEp8yIKQg7x/NnR6D
IoN3d/HUQFqbJYz+A8iiYKsgK9EsNw==
=6fHb
-END PGP SIGNATURE-

Bug#1038747: gnome-software may overwrite debian-security with invalid entry

[Simon McVittie]

Control: reassign -1 software-properties-gtk 0.99.30-4
Control: retitle -1 software-properties-gtk: may overwrite debian-security with 
non-working entry
Control: affects -1 + gnome-software

On Tue, 20 Jun 2023 at 15:21:42 -0400, Jesse Rhodes wrote:
> I was alerted to this issue by an IRC user and was able to reproduce
> it in a clean bookworm vm.
> 
> Steps to reproduce:
> 1 - install bookworm from 12.0.0 media, selecting the gnome desktop task
> 2 - log in and run Software from the Activites menu
> 3 - select Software Repositories from the upper right menu
> 4 - select any option in the "Download from:" menu, press close, and
> press refresh
> 
> This results in an error dialog from gnome-software, with the relevant line
> "E: The repository 'https://deb.debian.org/debian bookworm-security
> Release' does not have a Release file."
> 
> The correct entry would be deb.debian.org/debian-security bookworm-security.
> 
> Marked as critical severity because it disables all updates from
> debian-security.

The "Software & Updates" window opened by gnome-software's
"Software Repositories" menu item isn't actually part of gnome-software,
so I'm reassigning this to the package that seems to provide it.

smcv

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

[Adrian Bunk]

Package: libjodycode2
Version: 3.0.1-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:phcpack jdupes

https://buildd.debian.org/status/fetch.php?pkg=phcpack=amd64=2.4.86%2Bdfsg-5=1687282110=0

...
jdupes -l src/Python/PHCpy3/doc/build/html/_images/math
jdupes: error while loading shared libraries: libjodycode.so.2: cannot open 
shared object file: No such file or directory
make[1]: *** [debian/rules:44: override_dh_auto_build-arch] Error 127


A shared library package libjodycode2 provides the shared library
libjodycode.so.2, and not providing it breaks reverse dependencies.

libjodycode2 must either provide libjodycode.so.2 by shipping it
or depending on a package that does ship it, or libjodycode2 must
be dropped. Anything other than dropping it would be highly unusual.

A transitional package libjodycode2-dev would be possible,
but there is no real benefit for a just created package.

The -dev package should be named libjodycode-dev,
which is a stable name.

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

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, 2023-06-20 at 12:45 +0200, Carlos Laviola wrote:
> Package: lightdm
> Followup-For: Bug #1038611
> 
> Can't reproduce, starts up just fine for me.
> 
> Could you perhaps include the logs from `/var/log/lightdm/´?

Hi Adilson,

I'm running 1.32 just fine since it was uploaded to experimental so I can't
reproduce either. Logs would help indeed, and if you can investigate a bit
more on your side (the info about downgrading helps identifying lightdm but
besides that...)

Regards, 
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSFncACgkQ3rYcyPpX
RFuFvwgAlSLsGtGtw8gWLSKh9j53R90TnQFXO815eCtpu4v332YxbTEc8ZyqUPVF
zndG+48/CWRtlhSi6PHlAorg3rMk7NgTSB29Oi1XD9Re3UX7z7Xvu/P92XbipzVg
D0TqCHN34PkPqoImgoNoHVjdgzaJukgGcTMoTZqbU/EguAHudkDqnHdXKbps6JUA
Pq1fXi2P6BP9nqDSpWjPmO4aA/o59Evb+D1q5MRHm43sZS3z9Vwj5zalLl2MiPG3
0EcBg/STIOV8Om+GBPYAsvQau4/3gWqyziVQw1/v4A8LYnH4BTLB+W6rVbHk/Fj6
PKbmA5VO3GjJfl4LABIPkpAwkB+gwg==
=SArv
-END PGP SIGNATURE-

Bug#1038750: file.1: a few remarks and editorial fixes for the manual

[Bjarni Ingi Gislason]

Package: file
Version: 1:5.44-3
Severity: minor
Tags: patch

Dear Maintainer,

here are some notes and fixes for the man page.



Input file is file.1

Output from "mandoc -T lint file.1":

  Not in the patch

mandoc: file.1:52:2: STYLE: useless macro: Tn
mandoc: file.1:97:2: STYLE: useless macro: Tn

  In the patch

mandoc: file.1:391:9: STYLE: no blank before trailing delimiter: Em Note:
mandoc: file.1:521:33: WARNING: undefined escape, printing literally: \ 
###

Change '-' (\-) to '\(en' (en-dash) for a numeric range.

file.1:628:2007-2011, to improve MIME support, merge MIME and non-MIME magic,

#

Mark a full stop (.) with "\&",
if it does not mean an end of a sentence.
This is a preventive action,
the paragraph could be reshaped, e.g., after changes.

When typing, one does not always notice when the line wraps after the
period.
There are too many examples of input lines in manual pages,
that end with an abbreviation point.

This marking is robust, and independent of the position on the line.

It corresponds to "\ " in TeX, and to "@:" in Texinfo.


386:i.e. when the
688:Make file -ki work, i.e. give multiple MIME types.
696:types (e.g. have a magic value for !:mime which causes the resulting

#

Output from "test-nroff -man -b -ww -z":

[ "test-groff" is a developmental version of "groff" ]

Input file is ./file.1

Output from test-groff -b -mandoc -dAD=l -rF0 -rHY=0 -t -w w -z :

troff: backtrace: file '/tmp/chk_manuals.temp.A0PKLx':521
troff:/tmp/chk_manuals.temp.A0PKLx:521: warning: escape character ignored 
before a tab character



--- file.1  2023-06-20 15:09:55.0 +
+++ file.1.new  2023-06-20 20:28:01.0 +
@@ -383,12 +383,12 @@ option disables sandboxing which is enab
 This option is needed for
 .Nm
 to execute external decompressing programs,
-i.e. when the
+i.e.\& when the
 .Fl z
 option is specified and the built-in decompressors are not available.
 On systems where sandboxing is not available, this option has no effect.
 .Pp
-.Em Note:
+.Em Note :
 This Debian version of file was built without seccomp support, so this option
 has no effect.
 .It Fl v , Fl Fl version
@@ -518,7 +518,7 @@ is that this version treats any white sp
 as a delimiter, so that spaces in pattern strings must be escaped.
 For example,
 .Bd -literal -offset indent
-\*[Gt]10   string  language impress\   (imPRESS data)
+\*[Gt]10   string  language impress(imPRESS data)
 .Ed
 .Pp
 in an existing magic file would have to be changed to
@@ -625,7 +625,7 @@ of non-ASCII files.
 .Pp
 Altered by Reuben Thomas
 .Aq r...@sc3d.org ,
-2007-2011, to improve MIME support, merge MIME and non-MIME magic,
+2007\(en2011, to improve MIME support, merge MIME and non-MIME magic,
 support directories as well as files of magic, apply many bug fixes,
 update and fix a lot of magic, improve the build system, improve the
 documentation, and rewrite the Python bindings in pure Python.
@@ -685,7 +685,7 @@ pointers to relative offsets from the st
 .Pp
 Add syntax for relative offsets after current level (Debian bug #466037).
 .Pp
-Make file -ki work, i.e. give multiple MIME types.
+Make file \-ki work, i.e.\& give multiple MIME types.
 .Pp
 Add a zip library so we can peek inside Office2007 documents to
 print more details about their contents.
@@ -693,7 +693,7 @@ print more details about their contents.
 Add an option to print URLs for the sources of the file descriptions.
 .Pp
 Combine script searches and add a way to map executable names to MIME
-types (e.g. have a magic value for !:mime which causes the resulting
+types (e.g.\& have a magic value for !:mime which causes the resulting
 string to be looked up in a table).
 This would avoid adding the same magic repeatedly for each new
 hash-bang interpreter.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.27-1 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages file depends on:
ii  libc6  2.36-9
ii  libmagic1  1:5.44-3

file recommends no packages.

file suggests no packages.

-- no debconf information

Bug#1038749: foxtrotgps: new upstream commit

[Bastian Germann]

Source: foxtrotgps
Version: 1.2.2+bzr331-1
Severity: minor

Please import the new upstream commit that enables building with newer 
libgps-dev.

Bug#1037595: blasr: ftbfs with GCC-13

[Nilesh Patra]

Control: reassign -1 pbseqlib 5.3.5+dfsg-4
Control: affects -1 src:blasr
Control: forcemerge -1 1037815

On Wed, 14 Jun 2023 09:22:06 + Matthias Klose  wrote:
> Package: src:blasr
> Version: 5.3.5+dfsg-6
> Severity: normal
> Tags: sid trixie
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-13

This is stemming from pbseqlib. merging BR.

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1038450: patch probably available

[Adrien Nader]

On Tue, Jun 20, 2023, julien.pu...@gmail.com wrote:
> Hi,
> 
> Le mardi 20 juin 2023 à 15:35 +0200, Adrien Nader a écrit :
> > I was looking at the migration for coq on Ubuntu and a build failure
> > on armhf is preventing it.
> > 
> > I expect that this issue is fixed by the following commit:
> >  
> > https://github.com/UniMath/UniMath/commit/1716c078b00c18dcabf63f671e414d7ba33cb23c
> > 
> >   Split the proof of associators_equiv to make sure it fits inside 32
> > b…
> > 
> >   …its (#1687)
> > 
> >   This is necessary to create a jscoq addon for UniMath
> >   (https://github.com/UniMath/UniMath-jsCoq).
> > 
> > I haven't tried the patch yet and wanted to ask first if you're
> > interested in restoring support for 32-bit arches. I honestly don't
> > know
> > if there's a lot of users on these (except maybe for JS).
> 
> If you can confirm that commit solves the issue, I'll add it as a patch
> to the Debian packaging and drop my latest change. I'm interested in
> having different platforms to detect subtle breakages.
> 
> Notice that I also reported to Coq upstream:
>   https://github.com/coq/coq/issues/17749

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.

-- 
Adrien

Bug#1025970: steam: SteamVR cannot find "getcap" to finish its installation

[Julian Groß]

For reference, someone reported the bug upstream: 
https://github.com/ValveSoftware/SteamVR-for-Linux/issues/563


Though with Valves track record when it comes to SteamVR support, they 
will likely never fix it.


OpenPGP_0xAF605C87F9E5AE94.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1033845: u-boot fails to boot on pinebook pro if installed on internal emmc

[Vagrant Cascadian]

On 2023-05-02, Wolf wrote:
> On 04/04/2023 17:14, Wolfgang Zarre wrote:
>>> It can still be useful to file a bug with Debian in case it make sense
>>> to backport a patch from upstream, too. This way we can track when the
>>> issue is resolved.
>>>
>>> So, in some cases, file bugs/patches/etc in both. :)
>>>
>> 
>> Ok, I agree, maybe then also mentioning the upstream report if done.
>> 
>
> Did some additional investigation and reported upstream:
> https://lists.denx.de/pipermail/u-boot/2023-May/516951.html

Thanks!

I nudged upstream, as it seems to be marked "accepted" in patchwork, but
I do not see it in upstream git yet:

  https://lists.denx.de/pipermail/u-boot/2023-June/520776.html

Presumably, it is on a maintainer branch or possibly deferred till
2023.10...


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1038689: pbuilder: creates /etc/pbuilderrc with invalid (debug repo) MIRRORSITE -- does not parse *.sources files

[Thorsten Glaser]

Martin Pitt dixit:

>/etc/pbuilderrc has
[…]
>So it smells like pbuilder's auto-detection cannot parse the (not-so-)new style

I’d argue to turn this into a request to remove this autodetection
altogether. I’ve had nothing but trouble with it, in some cases
even overwriting/appending the /etc/pbuilderrc after I had replaced
it with my own¹.

Use deb.debian.org (or, for derivatives, the relevant default mirror
of theirs) if no pbuilderrc is configured. Ideally, let debootstrap
use its default if no pbuilderrc.

① http://cvs.mirbsd.de/contrib/hosted/tg/deb/pbuilderrc?rev=HEAD

bye,
//mirabilos
-- 
 you introduced a merge commit│ % g rebase -i HEAD^^
 sorry, no idea and rebasing just fscked │ Segmentation
 should have cloned into a clean repo  │  fault (core dumped)
 if I rebase that now, it's really ugh │ wuahh

Bug#1037214: bullseye-pu: package appstream-glib/0.7.18-1+deb11u1

[Simon McVittie]

Control: tags -1 - moreinfo

On Sat, 17 Jun 2023 at 18:45:31 +0200, Matthias Klumpp wrote:
> Thank you for working on this! It will be nice to have this issue
> fixed in bullseye soon, as it seems to affect quite a bunch of users!

I've assumed that counts as a "yes" from the maintainer, and uploaded
the proposed version for the stable release team's review.

Thanks,
smcv

Bug#1038748: opther: clinfo, glxinfo and vulkaninfo not installed by default

[G. Allard]

Package: other
Severity: minor
X-Debbugs-Cc: gall...@technologue.net

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***
clinfo, glxinfo and vulkaninfo are requires by KDE " Centre d'informations" but 
are not installed by default.
Since packages are not specified, a beginner may have difficulties to find them.

-- 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/4 CPU threads; PREEMPT)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1036701: closed by Debian FTP Masters (reply to Reinhard Tartler ) (Bug#1036701: fixed in gpac 2.2.1+dfsg1-1)

[Salvatore Bonaccorso]

Control: reopen -1 
Hi

Looking at the upstream tag v2.2.1 thos echanges are not yet included.
Can you double check please as well? For instance
https://github.com/gpac/gpac/commit/ba59206b3225f0e8e95a27eff41cb1c49ddf9a3
for CVE-2023-2840 still applies.

Regards,
Salvatore

Bug#1028137: [Pkg-electronics-devel] Bug#1028137: nextpnr: Support for more FPGA architectures (esp. ECP5)

[Daniel Gröber]

Hi Jonathan,

On Tue, Jun 20, 2023 at 02:24:11PM +0200, Daniel Gröber wrote:
> Great. I've uploaded the packages to my testing archive you should be able
> to install nextpnr=0.6-2~dxld1 on unstable using this sources.list entry:

I've fixed some more packaging bugs, please try with nextpnr=0.6-2~dxld2
when you get around to it.

Thanks,
--Daniel

Bug#1034890: closed by Debian FTP Masters (reply to Reinhard Tartler ) (Bug#1034890: fixed in gpac 2.2.1+dfsg1-1)

[Salvatore Bonaccorso]

Control: reopen -1 

Hi Reinhard,

I'm unsure on this one, can you elaborate where CVE-2023-0841 has been
fixed with the 2.2.1 upstream version? This was particularly confusing
as the only reference given for the CVE is as Moritz mentioned,
https://github.com/qianshuidewajueji/poc/blob/main/gpac/mp3_dmx_process_poc3
. Unclear if it ever was reported upstream.

Can you have a look?

Regards,
Salvatore

Bug#1038747: gnome-software may overwrite debian-security with invalid entry

[Jesse Rhodes]

Package: gnome-software
Version: 43.4-1
Severity: critical
X-Debbugs-Cc: je...@sney.ca

Dear Maintainer,

I was alerted to this issue by an IRC user and was able to reproduce
it in a clean bookworm vm.

Steps to reproduce:
1 - install bookworm from 12.0.0 media, selecting the gnome desktop task
2 - log in and run Software from the Activites menu
3 - select Software Repositories from the upper right menu
4 - select any option in the "Download from:" menu, press close, and
press refresh

This results in an error dialog from gnome-software, with the relevant line
"E: The repository 'https://deb.debian.org/debian bookworm-security
Release' does not have a Release file."

The correct entry would be deb.debian.org/debian-security bookworm-security.

Marked as critical severity because it disables all updates from
debian-security.

sney


-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-software depends on:
ii  appstream0.16.1-2
ii  apt-config-icons 0.16.1-2
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
pn  gnome-software-common
ii  gsettings-desktop-schemas43.0-1
pn  libadwaita-1-0   
ii  libappstream40.16.1-2
ii  libc62.36-9
ii  libcairo21.16.0-7
ii  libfwupd21.8.12-2
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgtk-4-1   4.8.3+ds-2
pn  libgtk3-perl 
ii  libgudev-1.0-0   237-2
ii  libjson-glib-1.0-0   1.6.6-1
pn  libmalcontent-0-0
ii  libpackagekit-glib2-18   1.2.6-5
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpolkit-gobject-1-0122-3
ii  libsoup-3.0-03.2.2-2
ii  libxmlb2 0.3.10-2
ii  packagekit   1.2.6-5
pn  software-properties-gtk  

Versions of packages gnome-software recommends:
ii  fwupd  1.8.12-2

Versions of packages gnome-software suggests:
pn  apt-config-icons-hidpi 
pn  gnome-software-plugin-flatpak  
pn  gnome-software-plugin-snap 

Bug#1038590: vlc: Depends on SDL 1.2

[Rémi Denis-Courmont]

tags 1038590 + fixed-upstream
thanks

Le sunnuntaina 18. kesäkuuta 2023, 20.09.12 EEST Simon McVittie a écrit :
> Source: vlc
> Tags: trixie sid
> User: pkg-sdl-maintain...@lists.alioth.debian.org
> Usertags: libsdl1.2
> 
> This package has a Depends or Build-Depends on SDL version 1.2, which
> is unmaintained upstream.

Upstream VLC has dropped SDL almost 3 years ago, but there has not been a 
release since then. It should be fine to just turn it off in the mean time.

-- 
Rémi Denis-Courmont
http://www.remlab.net/

Bug#1037538: gerbera: FTBFS with libupnp17

[Bastian Germann]

Hi Adrian,

On Sun, 18 Jun 2023 13:20:17 +0300 Adrian Bunk  wrote:
There is also a later build error, but updating to the latest upstream 
version 1.12.1 gave me a build:

1. uscan finds the correct version after updating debian/watch to
   https://github.com/gerbera/gerbera/tags
2. build dependencies need some adjustment
3. debian/gerbera.docs needs some adjustment

I haven't done 2. and 3. properly and haven't tested the resulting package.


This is the last package that prevents fulfilling the pupnp transition.
Would you please go ahead with a team upload? I do not think James is still 
around.

Thanks,
Bastian

Bug#1037511: silverjuke: FTBFS with libupnp17

[Bastian Germann]

I am uploading a NMU with a trivial patch to fix this. The debdiff is attached 
and also available in the git repo.diff -Nru silverjuke-18.2.1/debian/changelog silverjuke-18.2.1/debian/changelog
--- silverjuke-18.2.1/debian/changelog  2022-09-18 20:21:55.0 +0200
+++ silverjuke-18.2.1/debian/changelog  2023-06-20 20:55:56.0 +0200
@@ -1,3 +1,13 @@
+silverjuke (18.2.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use newer UpnpInit2 API (Closes: #1037511)
+
+  [ Debian Janitor ]
+  * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, 
Repository-Browse.
+
+ -- Bastian Germann   Tue, 20 Jun 2023 20:55:56 +0200
+
 silverjuke (18.2.1-4) unstable; urgency=medium
 
   [ Dr. Tobias Quathamer ]
diff -Nru silverjuke-18.2.1/debian/patches/0003-Use-newer-UpnpInit2-API.patch 
silverjuke-18.2.1/debian/patches/0003-Use-newer-UpnpInit2-API.patch
--- silverjuke-18.2.1/debian/patches/0003-Use-newer-UpnpInit2-API.patch 
1970-01-01 01:00:00.0 +0100
+++ silverjuke-18.2.1/debian/patches/0003-Use-newer-UpnpInit2-API.patch 
2023-06-20 20:54:09.0 +0200
@@ -0,0 +1,21 @@
+From: Bastian Germann 
+Date: Tue, 20 Jun 2023 20:52:15 +0200
+Subject: Use newer UpnpInit2 API
+
+---
+ src/sjmodules/upnp.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/sjmodules/upnp.cpp b/src/sjmodules/upnp.cpp
+index a41b0e3..fa80f25 100644
+--- a/src/sjmodules/upnp.cpp
 b/src/sjmodules/upnp.cpp
+@@ -178,7 +178,7 @@ bool SjUpnpModule::InitLibupnp()
+ 
+   // init library - NB: we may be in a working thread here (eg. 
ImgThread), however, this seems not to be a problem
+   int error;
+-  if( (error=UpnpInit(NULL, 0)) != UPNP_E_SUCCESS ) {
++  if( (error=UpnpInit2(NULL, 0)) != UPNP_E_SUCCESS ) {
+   LogUpnpError("Cannot init", error);
+   ExitLibupnp();
+   return false; // error
diff -Nru silverjuke-18.2.1/debian/patches/series 
silverjuke-18.2.1/debian/patches/series
--- silverjuke-18.2.1/debian/patches/series 2022-09-18 20:21:40.0 
+0200
+++ silverjuke-18.2.1/debian/patches/series 2023-06-20 20:53:15.0 
+0200
@@ -1,3 +1,4 @@
 0001-Force-X11-for-wxGLCanvas.patch
 0002-Replace-URL-of-freedb-with-gnudb.gnudb.org.patch
+0003-Use-newer-UpnpInit2-API.patch
 wx3.2-compat.patch
diff -Nru silverjuke-18.2.1/debian/upstream/metadata 
silverjuke-18.2.1/debian/upstream/metadata
--- silverjuke-18.2.1/debian/upstream/metadata  1970-01-01 01:00:00.0 
+0100
+++ silverjuke-18.2.1/debian/upstream/metadata  2023-06-20 20:37:25.0 
+0200
@@ -0,0 +1,5 @@
+---
+Bug-Database: https://github.com/silverjuke/silverjuke/issues
+Bug-Submit: https://github.com/silverjuke/silverjuke/issues/new
+Repository: https://github.com/silverjuke/silverjuke.git
+Repository-Browse: https://github.com/silverjuke/silverjuke

Bug#1033257: Accepted libde265 1.0.12-1 (source) into unstable

[Salvatore Bonaccorso]

Source: libde265
Source-Version: 1.0.12-1

- Forwarded message from Debian FTP Masters 
 -

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Jun 2023 09:10:00 +0200
Source: libde265
Architecture: source
Version: 1.0.12-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Joachim Bauch 
Changes:
 libde265 (1.0.12-1) unstable; urgency=medium
 .
   * New upstream version 1.0.12
   * Fixes CVE-2023-27102, CVE-2023-27103
Checksums-Sha1:
 bb31cc1fe71a8296116741f0c97821822d8c1e93 2190 libde265_1.0.12-1.dsc
 e35ecaf9f92ee9ac16a00c4c46a08265db1875ad 846345 libde265_1.0.12.orig.tar.gz
 6dea97aa73959056cb71cc681205578c00f850f4 13856 libde265_1.0.12-1.debian.tar.xz
 3923d67bd5e56435a08f156529be18673252232f 12057 
libde265_1.0.12-1_amd64.buildinfo
Checksums-Sha256:
 1f385757f4b184d97065fd5ea6ac59d008644ca469441a4c897a7d25c2a75873 2190 
libde265_1.0.12-1.dsc
 62185ea2182e68cf68bba20cc6eb4c287407b509cf0a827d7ddb75614db77b5c 846345 
libde265_1.0.12.orig.tar.gz
 ee94aa14e49de8496f2edcb2cb736e924ef5b1b830a09c78c5aefd09e16d2ead 13856 
libde265_1.0.12-1.debian.tar.xz
 03c39d0fdc1333eff844face7304808c236a76197c2b71ee3198a61e2c756f2b 12057 
libde265_1.0.12-1_amd64.buildinfo
Files:
 42447cc1528bd9cab7e80b3c2b299a56 2190 libs optional libde265_1.0.12-1.dsc
 b4abfb8a1c38c1270afae91bc96e661d 846345 libs optional 
libde265_1.0.12.orig.tar.gz
 8fc0be8991998a2402cc5e012814 13856 libs optional 
libde265_1.0.12-1.debian.tar.xz
 9fcdc5703e9e60066f56da244ff396ec 12057 libs optional 
libde265_1.0.12-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmSRqmwACgkQkWT6HRe9
XTbe+Q/+LRNdf7ArYcjYJLBB5Y/qY2cVyIpx9MwtEEoCCEr6p1hQlcANWoRgYIgL
y0K8tQ9pWKYhq776TWaQ3IjEIz5/MLqUl3exmzdGXWlquUB/YiaW49Z0fEDWectD
IJFYzZHpm/DmV6VNiipfQ03+NNHeuytOhErZErwm06Sq3pZ6U0MtmMcs+eQj0ht/
jGzr4Vux7cAhwuz4cyIPF4heyilAXqo2o0XirvoU0vmS3T8f1I8Tr6rg9R3vyKIb
zB4OVb6z4hMRXA9YZ7L8V+QPF2AxX1b9rSmS0WciBU8MqZtCRdeyrNNOtOm/NRbm
qBjw2gxnW4LRWSeOued15X0J2M/q3GHcrmi15q2kKp9d+cEqUlYbcka9wSPg++ax
esbUxyPVho/GTYP6mMtHg8HZqZw5SI7oF6CP2ttuOBYafU24z3H/aIV0ieGJg/nX
6KH2shmAL3E4ulLYCEqxWnZJLnIV3bykiKHtnuyHvQVQ5Xd/YoNxdcB6Uff4rALO
KyRfVrg4YPkVwQLcgbK6QzamwbYI5XCdwYVoPExtlNEydjQIu3Cpdn05x+xdm7vm
w1/cN/FLsbdb44EtrzUpN/Cv9DidYsgC6/JLy+nKpqlpMqmVdPdHpAH3WtJjU9/y
xemHLdNTq5NNbEBm9WIVhkOC9iBeALhj0uwzs7gvNG0lAbUMWNA=
=QRgB
-END PGP SIGNATURE-


- End forwarded message -

Bug#1038746: build dependency missing in testing

[Paul Gevers]

Source: python-cryptography
Version: 38.0.4-3
Severity: serious
User: debian...@lists.debian.org
Usertag: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting issues with your packages. Normally your build 
dependencies shouldn't be removed from testing without removal all 
reverse build dependencies too, nor should a package be allowed to 
migrate unless all build dependencies are candidate for migration too. 
However, somehow we ended up in the current state and your source 
package is missing some Build-Depends for now. Not being able to build 
from source in a suite is an RC bug in that suite.


Can you please solve the situation by either helping the maintainer of 
your Build-Depends to enable migration to testing, or by working around 
the lack of this build dependency?


Paul

[1] https://qa.debian.org/dose/debcheck/src_testing_main/index.html


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1031034: apr: Missing LFS support triggers FTBFS on other packages

[Stefan Fritsch]

It seems a large transition will be needed for 64bit time_t, anyway. And 
glibc enforces _FILE_OFFSET_BITS=64 if _TIME_BITS=64 is set. apr should 
do both transitions at the same time.


It seems there won't be a transition for i386 but the whole point of 
i386 is running old binaries.


https://wiki.debian.org/ReleaseGoals/64bit-time

Bug#1034732: fixed in gpac 2.2.1+dfsg1-1

[Moritz Mühlenhoff]

Am Tue, Jun 20, 2023 at 06:06:26PM + schrieb Debian FTP Masters:
> Source: gpac
> Source-Version: 2.2.1+dfsg1-1
> Done: Reinhard Tartler 
> Changes:
>  gpac (2.2.1+dfsg1-1) experimental; urgency=medium
>  .
>* New upstream version,
>  closes: #1033116, #1034732, #1034187, #1036701, #1034890

A single upload a week after the release doesn't change the fact that
gpac isn't supportable unless you massively step up in maintenance
(which would also involve taking care of bullseye-security), so
#1034732 should not be closed with the upload to unstable.

If GPAC magically becomes more stable over the next 1.5 years,
we can reconsider.

Cheers,
Moritz

Bug#1038745: dunst: Please package new upstream release 1.9.2

[Boyuan Yang]

Source: dunst
Version: 1.9.0-0.1
Severity: normal
Tags: sid
X-Debbugs-CC: ni...@tsipinakis.com

Dear Debian dunst package maintainer,

According to https://github.com/dunst-project/dunst/releases , a new release
1.9.2 is now available. Please consider packaging latest upstream version.
If you need any help in packaging such as technical issues or sponsorship
needs, please feel free to let me know. Thanks!

Best,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part

Bug#1038416: (no subject)

[Francesco P. Lovergine]

For reference, all this is a side effect of the proposed fix for #991266,
strangely not caught at the time.

On Tue, Jun 20, 2023 at 08:00:19PM +0200, Francesco P. Lovergine wrote:

Bruno, that's right

Unfortunately yes: originally the socket unit file was concepted as an example
file to keep into the documentation and the Conflicts there does not 
ensure that the .socket unit is ignored when the .service is enabled.


The simplest workaroud is

systemctl disable --now proftpd.socket
systemctl enable --now proftpd.service

but the initial installation is definitively broken, because proftpd 
starts as a systemd socket, which is not intended by the distributed 
proftpd.conf.


Hilmar, the simplest thing to do is probably addig a mask/disable of 
proftpd.socket at postinst time,
and an enable --now for the proftpd.service, when server should be run 
in standalone mode (check via grepping proftpd.conf), after installing 
systemd stuff in --no-enable --no-start mode.


This is of course not completely fair because ignores xinetd/inetd setup.



--
Francesco P. Lovergine

Bug#989441: Missing Nvidia /lib/firmware/nouveau/nv106_fuc084

[Ben Hutchings]

Control: tag -1 wontfix

I don't think we're allowed to extract and redistribute firmware from
the Nvidia package.

Ben.

-- 
Ben Hutchings
compatible: Gracefully accepts erroneous data from any source



signature.asc
Description: This is a digitally signed message part

Bug#1038744: Update Kotlin to 1.3.40 or higher to enable reflection for Jitsi

[Timothy Pearson]

Package: kotlin
Version: 1.3.31

When attempting to package Jitsi for Debian, I ran into a blocking issue due to 
Kotlin 1.3.31 not providing the typeOf() reflection function, which was 
introduced as experimental in Kotlin 1.3.40.  Since the lift to move from one 
minor version to another is probably less than the lift needed to rewrite 
Jitsi's reflection code through its entire codebase, it would be useful to 
upgrade Kotlin to at least 1.3.40 in the Debian archives.

Bug#1035875: Arbitrary code execution vulnerability in versions < 2.3

[Sylvain Beucler]

Hi,

I requested a CVE at cveform.mitre.org so we can start a discussion with 
upstream on clear grounds, and possibly involve other distros :)


From https://github.com/mtrojnar/osslsigncode/compare/2.2...2.3 there 
are a lot of commits that fixes memory issues, e.g.

  fix double free in msi_dirent_new()
  Fix more fuzzer errors
  etc.
so most probably there isn't a single clean patch to apply :/

We might want to just bump to buster and bullseye to 2.3, there's only 
one rdep AFAICS.


Cheers!
Sylvain Beucler
Debian LTS Team
(this week's Front-Desk person)

Bug#1038743: src:ruby-prometheus-client-mmap: fails to migrate to testing for too long: FTBFS on ppc64el

[Paul Gevers]

Source: ruby-prometheus-client-mmap
Version: 0.16.2-1
Severity: serious
Control: close -1 0.19.1-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1034565

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:ruby-prometheus-client-mmap has been 
trying to migrate for 64 days [2]. Hence, I am filing this bug. The 
package fails to build from source on ppc64el, which was reported in bug 
1034565.


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.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=ruby-prometheus-client-mmap



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1038610: firmware-bnx2x has an older version of broadcom drivers. This has been fixed for bookworm but not bullseye

[Ben Hutchings]

Control: fixed -1 20220913-1
Control: tag -1 bullseye
Control: severity -1 important

On Sun, 2023-06-18 at 18:15 -0500, tomas347 wrote:
> Package: firmware-bnx2x
> Version: 20210315-3
> Severity: minor
> Tags: patch
> X-Debbugs-Cc: tomas.leite.cas...@tecnico.ulisboa.pt
> 
> Dear Maintainer,
> 
> 
>* What led up to the situation?
>I found that my network card was crashing and eventually lost all
>network connectivity and the OS stopped recognizing the card. I
>initially had to replace the card but the same thing happened on
>bullseye.
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>  I manually installed bnx2x-e1-7.13.21.0.fw, bnx2x-e1h-7.13.21.0.fw,
>  bnx2x-e2-7.13.21.0.fw, and now it works perfectly. This has been
>  fixed for bookworm but not bullseye. There are many people with
>  this issue and I found this workaround after many people debugged
>  it.
[...]

I think we never added this because we didn't expect stable kernel
changes to require newer firmware.

I'll try to get this fixed in the next point release for bullseye.

Ben.


-- 
Ben Hutchings
compatible: Gracefully accepts erroneous data from any source



signature.asc
Description: This is a digitally signed message part

Bug#1036094: nss: libnss3 libnss3-dev fails to debuild -us -uc

[Paul Gevers]

Hi,

On 17-06-2023 20:33, Paul Gevers wrote:
It think this problem solved itself, but the reproducible-builds 
infrastructure [1] claims nss still FTBFS. I'm not understanding what 
the tail of the log means thought.


I understand that this was "fixed" on the reproducible build side of the 
infrastructure, and nss now builds in unstable on amd64 there. I propose 
to close this bug.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1038741: sdl12-compat + bumprace: game becomes unresponsive during "CRASHED" death message

[Simon McVittie]

Package: libsdl1.2-compat,bumprace
Severity: important
Forwarded: https://github.com/libsdl-org/sdl12-compat/issues/253
Control: found -1 libsdl1.2-compat/1.2.60-1
Control: found -1 libsdl1.2-compat/1.2.64-2
Control: found -1 bumprace/1.5.8-1
User: pkg-sdl-maintain...@lists.alioth.debian.org
Usertags: sdl12-compat-regression

sdl12-compat is a compatibility layer that implements the SDL 1.2 API/ABI
by dlopening SDL 2 and using that instead. During the Debian 13 cycle,
I want to replace the unmaintained "classic SDL 1.2" with sdl12-compat.
I tested lots of older games with sdl12-compat during the Debian
12 freeze and upstream was able to apply fixes or workarounds, but
unfortunately bumprace is one of the few for which using sdl12-compat
exhibits a regression.  It's not clear whether this is a bumprace bug,
or a sdl12-compat bug.

Prerequisites:

* Debian 12 system (with or without upgrading libsdl1.2-compat from
  unstable)
* A Wayland environment with Xwayland
* sudo apt install bumprace libsdl1.2-compat

To reproduce:

export SDL12COMPAT_DEBUG_LOGGING=1
bumprace
SDL_VIDEODRIVER=x11 LD_LIBRARY_PATH='/usr/$LIB/sdl12-compat' bumprace
SDL_VIDEODRIVER=wayland LD_LIBRARY_PATH='/usr/$LIB/sdl12-compat' bumprace

While the LD_LIBRARY_PATH is set, check that you see this as the first line
of output:
> INFO: sdl12-compat 1.2.60, built on (date) at (time), talking to SDL2 2.26.5

Use arrow keys and Enter to select "1 player game",
"Flying saucer (Best steering)".

Use Left/Right arrow keys to rotate (the red tick mark on the flying
saucer is the back end) and Up arrow key to fire the engine. Steer
yourself into an enemy (grey shuriken-looking things) or obstacle
(electricity). If necessary exit the level (press Esc repeatedly) and
start again to get a level where there is electricity closer to your
starting position.

Expected result:

* After colliding, an explosion and "CRASHED" appear, reasonably promptly,
  and the level restarts

Actual result:

* With classic SDL 1.2 (simple "asc" command), it works as expected.

* With libsdl1.2-compat, often (maybe half the time), the game freezes for
  a while (music continues to play but the game is unresponsive).
  In GNOME this often triggers a "Bumprace is not responding" dialog.

According to SDL upstream, the problem is that the game doesn't iterate
the SDL main loop while fading in and out the red "CRASHED" message. It
seems that this might have been OK in SDL 1.2, but in SDL 2 the result
is that it fades in extremely slowly.

Workaround: using native X11 (for example "GNOME on Xorg") doesn't seem
to trigger this for whatever reason.

smcv

Bug#907384: Bug#1037996: Acknowledgement (xfce4: xfce-Desktop will be crashed at start and than black Desktop)opa

[Dr. Hanisch]

Hello,

the Trick with Ctrl+Alt+h is only a pragmatic solution.

What mean the message from: sudo nala upgrade:

" ... xfce4-session outdated"

with regards
Ch. Hanisch

-- Mein öffentlicher Schlüssel ist auf dem Keyserver 
'https://keys.openpgp.org' unter ch-hani...@t-online.de (E53DF487)

Bug#990486: mtools 4.0.33-1+really4.0.32-1: Internal error, size too big

[Silvio Knizek]

Hi,

so I use [simplediskimage](https://pypi.org/project/simplediskimage/), a python 
wrapper for several tools (including `mtools`) to build a simple disk image.

When I run my script inside the official 3.11-bookworm container from 
hub.docker.io, `mcopy -i  -bQ  ` 
fails with

```
Internal error, size too big
Streamcache allocation problem:: 3
```

This does not happen with the 3.11-bullseye container with `mtools` 4.0.26. 
According to [the 
internet](https://github.com/PartialVolume/shredos.x86_64/issues/120) this is 
fixed as well in 4.0.42.

As I can't change the way `simplediskimage` is calling `mcopy` and remove the 
`-b` option, I would like to have the fix (whatever it is) back ported.

BR
Silvio

Bug#1038625: firmware-realtek: Add configuration for stable connection (rtw88)

[Ben Hutchings]

Control: reassign -1 src:linux 6.1.27-1
Control: retitle -1 rtw88_pci: RX DMA errors despite rx_no_aspm workaround
Control: tag -1 upstream patch moreinfo

On Mon, 2023-06-19 at 03:20 -0300, Leandro Cunha wrote:
> Package: firmware-realtek
> Version: 20230404-1
> Severity: important
> 
> This firmware contains the rtw88 module

It doesn't - firmware and drivers are two different things.

> and needs some settings to
> have a stable connection, like disabling the ASPM (Active State Power
> Management)
[...]

OK, but if this is a general problem it should be fixed in the driver
and not by adding a configuration file.

This *was* supposed to have been fixed by

but apparently not.

Could you please test whether the attached patch fixes this (without
also using disable_aspm=1)?  Instructions for rebuilding the kernel are
at
.

Ben.

-- 
Ben Hutchings
compatible: Gracefully accepts erroneous data from any source

From 44b626514f8064f721c694ce977cf3a14da75047 Mon Sep 17 00:00:00 2001
From: Ben Hutchings 
Date: Tue, 20 Jun 2023 19:46:47 +0200
Subject: [PATCH] rtw88_pci: Apply rx_no_aspm workaround for longer

In certain configurations we need to keep the PCIe link in L0 to avoid
RX DMA errors.  Currently we do this while the poll function is
running, but this only roughly corresponds to when RX DMA is
happening.

Instead, keep the link in L0 for the whole time that NAPI polling is
enabled.  Use napi_schedule_prep()+__napi_schedule() rather than
napi_schedule(), so that we know for sure when we start and stop
polling.

Signed-off-by: Ben Hutchings 
---
 drivers/net/wireless/realtek/rtw88/pci.c | 27 +---
 1 file changed, 19 insertions(+), 8 deletions(-)

diff --git a/drivers/net/wireless/realtek/rtw88/pci.c b/drivers/net/wireless/realtek/rtw88/pci.c
index 672ddde80816..406bb12374d1 100644
--- a/drivers/net/wireless/realtek/rtw88/pci.c
+++ b/drivers/net/wireless/realtek/rtw88/pci.c
@@ -1014,7 +1014,15 @@ static void rtw_pci_rx_isr(struct rtw_dev *rtwdev)
 	struct rtw_pci *rtwpci = (struct rtw_pci *)rtwdev->priv;
 	struct napi_struct *napi = >napi;
 
-	napi_schedule(napi);
+	if (napi_schedule_prep(napi)) {
+		__napi_schedule(napi);
+
+		/* If necessary, keep link in L0 so long as we are in
+		 * NAPI polling
+		 */
+		if (rtwpci->rx_no_aspm)
+			rtw_pci_link_ps(rtwdev, false);
+	}
 }
 
 static int rtw_pci_get_hw_rx_ring_nr(struct rtw_dev *rtwdev,
@@ -1644,9 +1652,6 @@ static int rtw_pci_napi_poll(struct napi_struct *napi, int budget)
 	  priv);
 	int work_done = 0;
 
-	if (rtwpci->rx_no_aspm)
-		rtw_pci_link_ps(rtwdev, false);
-
 	while (work_done < budget) {
 		u32 work_done_once;
 
@@ -1667,11 +1672,17 @@ static int rtw_pci_napi_poll(struct napi_struct *napi, int budget)
 		 * not be processed immediately. Check whether dma ring is
 		 * empty and perform napi_schedule accordingly.
 		 */
-		if (rtw_pci_get_hw_rx_ring_nr(rtwdev, rtwpci))
-			napi_schedule(napi);
+		if (rtw_pci_get_hw_rx_ring_nr(rtwdev, rtwpci) &&
+		napi_schedule_prep(napi)) {
+			__napi_schedule(napi);
+		} else {
+			/* If we kept link into L0, allow it to
+			 * re-enter L1 until next IRQ
+			 */
+			if (rtwpci->rx_no_aspm)
+rtw_pci_link_ps(rtwdev, true);
+		}
 	}
-	if (rtwpci->rx_no_aspm)
-		rtw_pci_link_ps(rtwdev, true);
 
 	return work_done;
 }


signature.asc
Description: This is a digitally signed message part

Bug#1038739: mirror submission for is.mirror.flokinet.net

[FlokiNET]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: is.mirror.flokinet.net
Type: leaf
Archive-architecture: amd64
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: FlokiNET 
Country: IS Iceland
Location: Reykjavík




Trace Url: http://is.mirror.flokinet.net/debian/project/trace/
Trace Url: 
http://is.mirror.flokinet.net/debian/project/trace/ftp-master.debian.org
Trace Url: 
http://is.mirror.flokinet.net/debian/project/trace/is.mirror.flokinet.net

Bug#1038738: sdl12-compat + asc: mouse cursor cannot reach top of fullscreen window under GNOME + Xwayland

[Simon McVittie]

Package: libsdl1.2-compat,asc
Severity: important
Forwarded: https://github.com/libsdl-org/sdl12-compat/issues/256
Control: found -1 libsdl1.2-compat/1.2.60-1
Control: found -1 libsdl1.2-compat/1.2.64-2
Control: found -1 asc/2.6.1.0-9+b4
User: pkg-sdl-maintain...@lists.alioth.debian.org
Usertags: sdl12-compat-regression

sdl12-compat is a compatibility layer that implements the SDL 1.2 API/ABI
by dlopening SDL 2 and using that instead. During the Debian 13 cycle,
I want to replace the unmaintained "classic SDL 1.2" with sdl12-compat.
I tested lots of older games with sdl12-compat during the Debian 12 freeze
and upstream was able to apply fixes or workarounds, but unfortunately asc
is one of the few for which using sdl12-compat exhibits a regression.
It's not clear whether this is an asc bug, or a sdl12-compat bug.

Prerequisites:

* Debian 12 system (with or without upgrading libsdl1.2-compat from
  unstable)
* GNOME 43 in Wayland mode (*not* "GNOME on Xorg")
* sudo apt install asc libsdl1.2-compat

To reproduce:

export SDL12COMPAT_DEBUG_LOGGING=1
asc
SDL_VIDEODRIVER=x11 LD_LIBRARY_PATH='/usr/$LIB/sdl12-compat' asc
SDL_VIDEODRIVER=wayland LD_LIBRARY_PATH='/usr/$LIB/sdl12-compat' asc

While the LD_LIBRARY_PATH is set, check that you see this as the first line
of output:
> INFO: sdl12-compat 1.2.60, built on (date) at (time), talking to SDL2 2.26.5

Expected result:

* Mouse cursor can be moved anywhere in the fullscreen window

Actual result:

* With classic SDL 1.2 (simple "asc" command), it works as expected.

* With libsdl1.2-compat and X11 via Xwayland, I can't move the cursor
  into the top few rows of pixels. The inaccessible region is rougly the
  same height as the menubar at the top; I think its exact size might
  vary between runs.

* With libsdl1.2-compat and SDL_VIDEODRIVER=wayland, I can't move the
  cursor into a larger area at the top (I would estimate 4x the height
  of the menubar), and I also can't move it into a region to the left
  (about the same width as the minimap on the right).

Workarounds:

1. Log out from GNOME, log back in to "GNOME on Xorg" and run the game
   that way; in this case it works fine.
2. Alt+Tab to another window (like the terminal you ran it from)
   and back to the game
3. Press the Super (Windows) key to zoom out to the GNOME Overview, then
   click on the game window to zoom back in to it

Any of these seems sufficient to make asc work as expected.

SDL upstream speculates that there might be something unusual about the
exact sequence of SDL API calls that result from asc using sdl12-compat.

KDE Plasma in Wayland mode does not seem to exhibit this issue, so it's
possible that it's a compositor/window manager bug, but it's weird that
it only happens with sdl12-compat.

smcv

Bug#1038710: src:procmail: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Hi,

On 20-06-2023 14:47, Santiago Vila wrote:
Because the release was close, I raised the bug to "serious" to prevent 
the migration.


Full ack, and thanks for doing that.

In either case, I've just (privately) forwarded this (by email) to the 
author to see if
he can help to fix the regression, as the github issue I opened for that 
is still unanswered.


That's a good outcome already from me filing this bug (pinging relevant 
stakeholders to think about the problem). Thanks again.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1038416: (no subject)

[Francesco P. Lovergine]

Bruno, that's right

Unfortunately yes: originally the socket unit file was concepted as an example
file to keep into the documentation and the Conflicts there does not ensure that 
the .socket unit is ignored when the .service is enabled. 

The simplest workaroud is 


systemctl disable --now proftpd.socket
systemctl enable --now proftpd.service

but the initial installation is definitively broken, because proftpd 
starts as a systemd socket, which is not intended by the distributed proftpd.conf.


Hilmar, the simplest thing to do is probably addig a mask/disable of 
proftpd.socket at postinst time,
and an enable --now for the proftpd.service, when server should be run in standalone mode (check via grepping proftpd.conf), 
after installing systemd stuff in --no-enable --no-start mode.


This is of course not completely fair because ignores xinetd/inetd setup.

On Tue, Jun 20, 2023 at 04:21:41PM +0200, Bruno wrote:

I guess that the systemd unit protfpd.socket should be disabled

$ systemctl is-enabled proftpd.sockets 
disabled



May be the Debian package postinst script wrongly enabled it





___
Pkg-proftpd-maintainers mailing list
pkg-proftpd-maintain...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-proftpd-maintainers



--
Francesco P. Lovergine

Bug#1037408: v2.11.5

[Martin Dosch]

Dear Maintainer,

it looks like v2.5.11 should be able to build against current go-crypto: 
https://github.com/sylabs/sif/releases/tag/v2.11.5

Best regards,
Martin


signature.asc
Description: PGP signature

Bug#947685: still occuring on Linux 6.1.0-9-amd64 x86_64

[Vincas Dargis]

Here's some more info - it first crashes and then starts logging these messages:

Jun 20 19:37:31 kernel: [ cut here ]
Jun 20 19:37:31 kernel: NETDEV WATCHDOG: enp5s0f1 (r8169): transmit queue 0 
timed out
Jun 20 19:37:31 kernel: WARNING: CPU: 7 PID: 0 at net/sched/sch_generic.c:525 
dev_watchdog+0x20b/0x220
Jun 20 19:37:31 kernel: Modules linked in: xt_recent nft_limit nft_log ipt_REJECT nf_reject_ipv4 xt_limit xt_multiport 
xt_conntrack xt_hashlimit xt_addrtype xt_mark nft_chain_nat xt_comment xt_CT xt_owner xt_tcpudp nft_compat xt_NFLOG 
xt_LOG nf_log_syslog nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc nf_nat_h323 
nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_nat nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip 
nf_conntrack_pptp nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 
nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nf_tables 
qrtr cmac algif_hash algif_skcipher af_alg bnep nfnetlink_log nfnetlink nvidia_drm(POE) nvidia_modeset(POE) 
intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
ghash_clmulni_intel btusb btrtl btbcm aesni_intel btintel btmtk crypto_simd cryptd iwlmvm bluetooth snd_hda_codec_realtek
Jun 20 19:37:31 kernel:  binfmt_misc mac80211 snd_hda_codec_generic snd_hda_codec_hdmi jitterentropy_rng snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi uvcvideo sha512_ssse3 snd_hda_codec sha512_generic videobuf2_vmalloc nls_ascii ctr 
uvc nls_cp437 snd_hda_core libarc4 videobuf2_memops videobuf2_v4l2 vfat rapl fat iwlwifi drbg snd_hwdep videodev 
asus_nb_wmi intel_cstate ansi_cprng asus_wmi videobuf2_common snd_pcm iTCO_wdt ledtrig_audio intel_pmc_bxt cfg80211 
sparse_keymap iTCO_vendor_support ecdh_generic snd_timer platform_profile nvidia(POE) intel_uncore ecc mc at24 pcspkr 
watchdog rfkill snd soundcore ac asus_wireless joydev evdev serio_raw sg msr parport_pc ppdev lp parport fuse dm_mod 
loop efi_pstore configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 btrfs blake2b_generic efivarfs raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid1 raid0 
multipath linear md_mod hid_logitech_hidpp hid_logitech_dj hid_generic sd_mod usbhid t10_pi hid sr_mod cdrom
Jun 20 19:37:31 kernel:  crc64_rocksoft crc64 crc_t10dif crct10dif_generic i915 drm_buddy i2c_algo_bit 
drm_display_helper ahci libahci xhci_pci libata cec xhci_hcd rc_core ttm rtsx_pci_sdmmc mmc_core scsi_mod r8169 
drm_kms_helper ehci_pci ehci_hcd crct10dif_pclmul crct10dif_common realtek i2c_i801 crc32_pclmul mdio_devres drm 
crc32c_intel psmouse usbcore libphy rtsx_pci i2c_smbus mxm_wmi lpc_ich scsi_common usb_common video battery wmi button

Jun 20 19:37:31 kernel: CPU: 7 PID: 0 Comm: swapper/7 Tainted: P   OE   
   6.3.0-1-amd64 #1  Debian 6.3.7-1
Jun 20 19:37:31 kernel: Hardware name: ASUSTeK COMPUTER INC. N551JM/N551JM, 
BIOS N551JM.205 02/13/2015
Jun 20 19:37:31 kernel: RIP: 0010:dev_watchdog+0x20b/0x220
Jun 20 19:37:31 kernel: Code: 00 e9 40 ff ff ff 48 89 df c6 05 e8 0c 06 01 01 e8 fa 52 fa ff 44 89 e9 48 89 de 48 c7 c7 
08 e2 8e 87 48 89 c2 e8 b5 40 71 ff <0f> 0b e9 22 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 90

Jun 20 19:37:31 kernel: RSP: 0018:b34e40278e80 EFLAGS: 00010282
Jun 20 19:37:31 kernel: RAX:  RBX: 9af11333 RCX: 

Jun 20 19:37:31 kernel: RDX: 0104 RSI: 878371d5 RDI: 

Jun 20 19:37:31 kernel: RBP: 9af1133304c8 R08:  R09: 
b34e40278d10
Jun 20 19:37:31 kernel: R10: 0003 R11: 87ed1fe8 R12: 
9af11333041c
Jun 20 19:37:31 kernel: R13:  R14: b34e40278ef8 R15: 
9af41f3e1d00
Jun 20 19:37:31 kernel: FS:  () GS:9af41f3c() 
knlGS:
Jun 20 19:37:31 kernel: CS:  0010 DS:  ES:  CR0: 80050033
Jun 20 19:37:31 kernel: CR2: 7f46faff4000 CR3: 00024b020002 CR4: 
001706e0
Jun 20 19:37:31 kernel: Call Trace:
Jun 20 19:37:31 kernel:  
Jun 20 19:37:31 kernel:  ? dev_watchdog+0x20b/0x220
Jun 20 19:37:31 kernel:  ? __warn+0x81/0x130
Jun 20 19:37:31 kernel:  ? dev_watchdog+0x20b/0x220
Jun 20 19:37:31 kernel:  ? report_bug+0x191/0x1c0
Jun 20 19:37:31 kernel:  ? prb_read_valid+0x1b/0x30
Jun 20 19:37:31 kernel:  ? handle_bug+0x41/0x70
Jun 20 19:37:31 kernel:  ? exc_invalid_op+0x17/0x70
Jun 20 19:37:31 kernel:  ? asm_exc_invalid_op+0x1a/0x20
Jun 20 19:37:31 kernel:  ? dev_watchdog+0x20b/0x220
Jun 20 19:37:31 kernel:  ? __pfx_dev_watchdog+0x10/0x10
Jun 20 19:37:31 kernel:  call_timer_fn+0x27/0x130
Jun 20 19:37:31 kernel:  ? __pfx_dev_watchdog+0x10/0x10
Jun 20 19:37:31 kernel:  __run_timers+0x222/0x2c0
Jun 20 19:37:31 kernel:  run_timer_softirq+0x2f/0x50
Jun 20 19:37:31 kernel:  

Bug#1038703: dtkcore: FTBFS: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported

[Dmitry Shachnev]

Control: tags -1 + patch

On Tue, Jun 20, 2023 at 12:52:53PM +0300, Dmitry Shachnev wrote:
> [...]
> 
> googletest 1.13 was uploaded to unstable recently, and it dropped support
> for C++ versions less than C++14:
> 
> https://github.com/google/googletest/releases/tag/v1.13.0
> 
> But dtkcore sets CONFIG += c++11 in its .pro files.

Attaching a patch that fixes the build failure.

--
Dmitry Shachnev
Description: don't force old C++ version for tests
Author: Dmitry Shachnev 
Forwarded: no
Last-Update: 2023-06-20

--- a/tests/ddesktopentry/ddesktopentry.pro
+++ b/tests/ddesktopentry/ddesktopentry.pro
@@ -3,7 +3,6 @@ QT -= gui
 
 TARGET = tst_ddesktopentrytest
 TEMPLATE = app
-CONFIG += c++11
 CONFIG -= app_bundle
 
 !isEmpty(DTK_STATIC_LIB){
--- a/tests/dthreadutils/dthreadutils.pro
+++ b/tests/dthreadutils/dthreadutils.pro
@@ -2,7 +2,6 @@ QT += testlib concurrent
 QT -= gui
 
 TEMPLATE = app
-CONFIG += c++11
 
 !isEmpty(DTK_STATIC_LIB){
 DEFINES += DTK_STATIC_LIB
--- a/tests/dutils/dutils.pro
+++ b/tests/dutils/dutils.pro
@@ -2,7 +2,6 @@ QT += testlib dbus
 QT -= gui
 
 TEMPLATE = app
-CONFIG += c++11
 
 !isEmpty(DTK_STATIC_LIB){
 DEFINES += DTK_STATIC_LIB
--- a/tests/dvtablehook/dvtablehook.pro
+++ b/tests/dvtablehook/dvtablehook.pro
@@ -2,7 +2,6 @@ QT += testlib
 QT -= gui
 
 TEMPLATE = app
-CONFIG += c++11
 
 # TODO: vtabhook release test failed
 QMAKE_CXXFLAGS_RELEASE -= -O2
--- a/tests/tests.pro
+++ b/tests/tests.pro
@@ -1,6 +1,6 @@
 TEMPLATE = app
 QT += core dbus xml testlib concurrent
-CONFIG += thread c++11 link_pkgconfig
+CONFIG += thread link_pkgconfig
 CONFIG -= app_bundle
 
 QMAKE_LFLAGS += -Wl,--export-dynamic


signature.asc
Description: PGP signature

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

[Dmitry Shachnev]

Source: photoqt
Version: 3.3+ds-1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

The latest photoqt upload failed to build on mips64el, m68k and riscv64.
mips64el is a release architecture, this I set severity to serious.

The error is:

  Traceback (most recent call last):
File "", line 1, in 
  ModuleNotFoundError: No module named 'pychromecast'
  CMake Error at CMakeLists.txt:386 (message):
** Unable to import PyChromecast, make sure it is installed.  Enabling the
CHROMECAST_PIPINSTALL option allows CMake to try to install it locally
using pip.


  -- Configuring incomplete, errors occurred!

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.

--
Dmitry Shachnev
--- photoqt-3.3+ds/debian/rules
+++ photoqt-3.3+ds/debian/rules
@@ -13,10 +13,7 @@
 ifeq ($(DEB_BUILD_ARCH_OS),kfreebsd)
 MAGICK = -DGRAPHICSMAGICK=OFF -DIMAGEMAGICK=OFF
 endif
-ifeq ($(DEB_BUILD_ARCH_OS),ia64)
-CHROMECAST = -DCHROMECAST=OFF
-endif
-ifeq ($(DEB_BUILD_ARCH_OS),x86_64)
+ifneq (,$(filter $(DEB_BUILD_ARCH),ia64 kfreebsd-amd64 kfreebsd-i386 sparc64 sh4 riscv64 m68k hppa mips64el))
 CHROMECAST = -DCHROMECAST=OFF
 endif
 ifeq ($(DEB_BUILD_ARCH_OS),hppa)


signature.asc
Description: PGP signature

Bug#1038735: python3-mapscript: python hook /usr/share/doc content (Policy 12.3): /usr/share/doc/python3-mapscript/examples/__init__.py

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 6/20/23 19:05, Andreas Beckmann wrote:

This piuparts test prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.


From the attached log (scroll to the bottom...):


   Setting up python3 (3.11.2-1+b1) ...
   [Errno 2] No such file or directory: 
'/usr/share/doc/python3-mapscript/examples/__init__.py'error running python 
rtupdate hook python3-mapscript
   dpkg: error processing package python3 (--configure):
installed python3 package post-installation script subprocess returned 
error exit status 4
   Setting up libgdal32 (3.6.4+dfsg-1) ...
   dpkg: dependency problems prevent configuration of python3-mapscript:
python3-mapscript depends on python3 (<< 3.12); however:
 Package python3 is not configured yet.

In this case it's probably sufficient to exclude the examples from the
hook.


This is done by dh_python3:

 # Automatically added by dh_python3
 if command -v py3compile >/dev/null 2>&1; then
 py3compile -p python3-mapscript:amd64 
/usr/share/doc/python3-mapscript/examples

 fi
 if command -v pypy3compile >/dev/null 2>&1; then
 pypy3compile -p python3-mapscript:amd64 
/usr/share/doc/python3-mapscript/examples || true

 fi

dh_python3 is used to rewrite the shebang, we'll just ignore the 
example-unusual-interpreter lintian issue then.


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1038736: mesa-va-drivers: constant brake

[Leandro]

Package: mesa-va-drivers
Version: 22.3.6-1+deb12u1
Severity: important
X-Debbugs-Cc: genteboapesso...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***
Hi, on my laptop, for more general support, I installed some extra codecs, vlc 
and rhythmbox, 
I'll send the command line from the terminal.

I use Google Chrome (.deb) from the official website.
On youtube, the videos at:
1080p60fps gets a constant brake,
2k60fps keeps stalling constantly,
4k60fps just keeps stalling even more, constantly.
8k60fps too.

In windows 11, the videos flow well, even in 4k.
On Linux, 4k didn't run well so far.
The only Linux-based distribution that ran well at 4k60fps was ChromiumOS Flex.

In the system settings, I didn't find the option to edit the energy parameters,
so I installed tlp linrunner, and in the tlp.conf file it has priority for 
maximum performance when plugged in,
and maximum economy when using battery power.
The cpu governor in the tlp.conf file is in performance for both AC and BAT.
I just installed and configured. 
In tlp-stat -v, it shows that my pc is missing a driver, and even putting the 
governor in performance,
there are some parameters that are performance schedutil.
It could be that tlp is getting parameters from Debian's power mode.
I installed tlp linrunner, because I like the way of editing energy parameters, 
as allowed in the configuration panel of energy plans found in windows 11.
However, I did not find anything on the tlp website about the energy standard 
of Debian for edit, to use tlp at 100%. 

I also edited the audio parameters file through the terminal, to increase the 
maximum quality.
I didn't find the way to increase it in the system settings, so I used the 
terminal anyway. 

Terminal:
apt install --install-recommends libavcodec-extra libavfilter-extra 
libavformat-extra gstreamer1.0-vaapi vlc rhythmbox

/etc/tlp.conf

/etc/pulse/default.pa

/etc/pulse/daemon.conf

resample-method = src-sinc-best-quality

default-sample-format = float32le
; default-sample-rate = 50
; alternate-sample-rate = 50



Drivers for my pc, manufacturer's official website:
 
https://pcsupport.lenovo.com/br/en/products/laptops-and-netbooks/300-series/330-15igm/81fn/downloads/driver-list



Lenovo Ideapad 330-15IGM 81FN
Debian 12
KDE Plasma
Intel Celeron N4000 (2) 1.10GHz Max 2.60GHz
Intel UHD 600 i915 Geminilake GLK2
Ram 4GB
SSD 256GB
PtBr UTF8
Abnt2 with numerical keyboard

Thanks in advance, 


   * What led up to the situation? I believe the lack of drivers for my pc.

   * What exactly did you do (or not do) that was effective (or
 ineffective)? updated, installed more codecs, and some things I use. But 
continued the brake

   * What was the outcome of this action? still got the constant brake, and the 
drivers are still missing for my pc.

   * What outcome did you expect instead? That the 4k60fps videos could be very 
fluid, 
and in future updates the missing drivers will be installed, as well as the 
brake disappear. 
The distribution will have 100% hardware support for my pc, like in windows 11.
Also even more powerful drivers and codecs, versions of extreme power and 
performance. :)


-- Package-specific info:
glxinfo:

glxinfo is not available (missing mesa-utils package).

/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation GeminiLake [UHD 
Graphics 600] [8086:3185] (rev 03)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 0

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 6.1.0-9-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 29372 Jun 20 12:21 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 9.066] (--) Log file renamed from "/var/log/Xorg.pid-982.log" to 
"/var/log/Xorg.0.log"
[ 9.067] 
X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
[ 9.067] Current Operating System: Linux PC 6.1.0-9-amd64 #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) x86_64
[ 9.067] Kernel command line: 
BOOT_IMAGE=/@rootfs/boot/vmlinuz-6.1.0-9-amd64 
root=UUID=a20386bd-5e2f-4993-a419-b5c7617d86fc ro rootflags=subvol=@rootfs quiet
[ 9.067] xorg-server 2:21.1.7-3 (https://www.debian.org/support) 
[ 9.067] Current version of pixman: 0.42.2
[ 9.067]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 9.067] Markers: 

Bug#1038735: python3-mapscript: python hook /usr/share/doc content (Policy 12.3): /usr/share/doc/python3-mapscript/examples/__init__.py

[Andreas Beckmann]

Package: python3-mapscript
Version: 8.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts test prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

>From the attached log (scroll to the bottom...):

  Setting up python3 (3.11.2-1+b1) ...
  [Errno 2] No such file or directory: 
'/usr/share/doc/python3-mapscript/examples/__init__.py'error running python 
rtupdate hook python3-mapscript
  dpkg: error processing package python3 (--configure):
   installed python3 package post-installation script subprocess returned error 
exit status 4
  Setting up libgdal32 (3.6.4+dfsg-1) ...
  dpkg: dependency problems prevent configuration of python3-mapscript:
   python3-mapscript depends on python3 (<< 3.12); however:
Package python3 is not configured yet.

In this case it's probably sufficient to exclude the examples from the
hook.


Cheers,

Andreas


python3-mapscript_8.0.1-1.log.gz
Description: application/gzip

Bug#1038734: src:gnumail: FTBFS with pantomime/1.4.0: MailboxManagerController.m:801:33: error: ‘struct CWFolder’ has no member named ‘allMessages’

[Yavor Doganov]

Source: gnumail
Version: 1.3.0-1
Severity: important
Tags: ftbfs sid trixie
User: pkg-gnustep-maintain...@lists.alioth.debian.org
Usertags: pantomime1.4-transition gnustep-transition

This package fails to build with pantomime/1.4.0+dfsg-1 from
experimental:

gcc MailboxManagerController.m -c \
  -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DGNUSTEP 
-DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 
-DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions -fobjc-exceptions 
-D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE 
-Wno-import -g -O2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-import 
-I/usr/kerberos/include -I/usr/local/ssl/include 
-fconstant-string-class=NSConstantString -I. -I./derived_src -I. 
-I/usr/local/include/GNUstep -I/usr/include/GNUstep \
   -o obj/GNUMail.obj/MailboxManagerController.m.o
MailboxManagerController.m: In function ‘-[MailboxManagerController 
outlineView:acceptDrop:item:childIndex:]’:
MailboxManagerController.m:801:33: error: ‘struct CWFolder’ has no member named 
‘allMessages’; did you mean ‘_allMessages’?
  801 | [aSourceFolder->allMessages objectAtIndex:
  | ^~~
  | _allMessages
...
make[5]: *** [/usr/share/GNUstep/Makefiles/rules.make:521: 
obj/GNUMail.obj/MailboxManagerController.m.o] Error 1
...
make[1]: *** [debian/rules:31: override_dh_auto_build] Error 25

The severity of this bug will be raised to "serious" as soon as
pantomime/1.4.0 is uploaded to unstable.

Bug#1038733: r-cran-rgeos: autopkgtest failure with GEOS 3.12

[Bas Couwenberg]

Source: r-cran-rgeos
Version: 0.6-1-1
Severity: important
Tags: upstream patch
User: debian-...@lists.debian.org
Usertags: geos-3.12

Dear Maintainer,

The autopkgtest of your package fail with GEOS 3.12 from experimental:

 == Failed tests 

 -- Error ('test-misc.R:50'): gNearestPoints works with different geometries as 
inputs --
 Error: Unable to parse: MULTIPOLYGON(((34 54, 60 34, 60 54, 34 54),
   (50 50, 52 50, 52 48, 50 48, 50 50)),
  ((100 100, 150 100, 150 150, 100 150, 100 100),   
(120 120, 120 130, 130 130, 130 120, 120 120
 GEOS reported: "rgeos_readWKT: unable to read wkt"
 Backtrace:
 x
  1. \-rgeos::readWKT("MULTIPOLYGON(((34 54, 60 34, 60 54, 34 54),\n
   (50 50, 52 50, 52 48, 50 48, 50 50)),\n  
((100 100, 150 100, 150 150, 100 150, 100 100),\n   
(120 120, 120 130, 130 130, 130 120, 120 120") at test-misc.R:50:2
  2.   \-base::tryCatch(...)
  3. \-base (local) tryCatchList(expr, classes, parentenv, handlers)
  4.   \-base (local) tryCatchOne(expr, names, parentenv, handlers[[1L]])
  5. \-value[[3L]](cond)
 
 [ FAIL 1 | WARN 28 | SKIP 0 | PASS 116 ]
 Error: Test failures

https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-rgeos/34462234/log.gz

The attached patch resolves the issue.

Upstream mentioned they fixed the issue in 0.6-4 which is not on CRAN yet at 
time of writing.

See: https://lists.osgeo.org/pipermail/geos-devel/2023-June/010957.html

Kind Regards,

Bas
Description: Fix test failure with GEOS 3.12.0.
 Should be fixed upstream in 0.6-4:
 .
 https://lists.osgeo.org/pipermail/geos-devel/2023-June/010957.html
Author: Bas Couwenberg 
Forwarded: not-needed

--- a/tests/testthat/test-misc.R
+++ b/tests/testthat/test-misc.R
@@ -50,7 +50,7 @@ test_that("gNearestPoints works with dif
   g2 <- readWKT("MULTIPOLYGON(((34 54, 60 34, 60 54, 34 54),
(50 50, 52 50, 52 48, 50 48, 50 50)),
   ((100 100, 150 100, 150 150, 100 150, 100 100),
-   (120 120, 120 130, 130 130, 130 120, 120 
120")
+   (120 120, 120 130, 130 130, 130 120, 120 
120)))")
   expect_identical(coord(gNearestPoints(g1, g2)),
coord(readWKT("MULTIPOINT(35 60, 35 54)")))
   expect_identical(gDistance(g1, g2), 6)

Bug#1038732: ara-server: fails to install: AttributeError: 'zoneinfo.ZoneInfo' object has no attribute 'zone'

[Andreas Beckmann]

Package: ara-server
Version: 1.5.8-1.1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up ara-server (1.5.8-1.1) ...
  [ara] No setting found for SECRET_KEY. Generating a random key...
  Traceback (most recent call last):
File "/usr/bin/ara-manage", line 10, in 
  sys.exit(main())
   ^^
File "/usr/lib/python3/dist-packages/ara/server/__main__.py", line 43, in 
main
  if not os.path.exists(settings.ARA_SETTINGS):
^
File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 82, in 
__getattr__
  self._setup(name)
File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 69, in 
_setup
  self._wrapped = Settings(settings_module)
  ^
File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 170, in 
__init__
  mod = importlib.import_module(self.SETTINGS_MODULE)
^
File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
 
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1147, in _find_and_load_unlocked
File "", line 690, in _load_unlocked
File "", line 940, in exec_module
File "", line 241, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/ara/server/settings.py", line 216, in 

  LOCAL_TIME_ZONE = tzlocal.get_localzone().zone

  AttributeError: 'zoneinfo.ZoneInfo' object has no attribute 'zone'
  [ESC][0mdpkg: error processing package ara-server (--configure):
   installed ara-server package post-installation script subprocess returned 
error exit status 1
  Processing triggers for ca-certificates (20230311) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Errors were encountered while processing:
   ara-server


cheers,

Andreas


ara-server_1.5.8-1.1.log.gz
Description: application/gzip

Bug#1038731: initramfs-tools: LVM setup becomes unbootable when adding to the VG additional encrypted PVs

[Javier Miqueleiz (ethereal)]

Package: initramfs-tools
Version: 0.142
Severity: important


After upgrading one of my systems running Debian 11 to bookworm, I've noticed 
the system has become unbootable. I think it's due to a regression in the 
initramfs-tools package, that doesn't properly activate the LVM VG with the 
rootfs if some of its PVs are not available at the initramfs stage. This will 
happen when using, for example, encrypted PVs (LUKS cryptsetup), or PVs with 
integrity protection (integritysetup), that require proper activation by 
systemd. In the tests I've performed, the bug occurs as long the VG with the 
rootfs has some missing PV at the early initramfs stage.




Steps to reproduce (using an encrypted PV as an example, as I guess it's the 
most common scenario for the majority of users).

Perform a clean install of Debian 12 on a virtual machine, using LVM (you can 
use any of these Debian installer's options: "Guided - use entire disk and set 
up LMV" or "Guided - use entire disk and set up encrypted LMV")

Update everything to the latest versions available:
apt update && apt upgrade

Now add a second disk to the VM and boot it.

Create a partition for the LVM PV and format it with cryptsetup:
parted /dev/vdb mklabel gpt
Information: You may need to update /etc/fstab.

parted /dev/vdb mkpart vdb1 xfs 1MiB 100%
Information: You may need to update /etc/fstab.

cryptsetup luksFormat /dev/vdb1

WARNING!

This will overwrite data on /dev/vdb1 irrevocably.

Are you sure? (Type 'yes' in capital letters): YES
Enter passphrase for /dev/vdb1:
Verify passphrase:

cryptsetup open /dev/vdb1 crypt_vdb1
Enter passphrase for /dev/vdb1:

pvcreate /dev/mapper/crypt_vdb1
  Physical volume "/dev/mapper/crypt_vdb1" successfully created.

(Now you can edit /etc/crypttab so that systemd activates the mapping, but this 
is not necessary for showing how to reproduce the bug.)

Now, extend the LVM VG with the new encrypted PV.
vgextend vg00 /dev/mapper/crypt_vdb1
  Volume group "vg00" successfully extended

After the last step, the system will become unbootable and the initramfs will 
drop you to an emergency shell. In order for the system to be able to boot, you 
have to manually activate the LVM VG:

(Command issued at the initramfs shell)
vgchange -ay
  WARNING: Couldn't find device with uuid 
yaTV5V-EkG3-3QvY-eYr4-rwfE-3U3I-vcbrA4.
  WARNING: VG vg00 is missing PV yaTV5V-EkG3-3QvY-eYr4-rwfE-3U3I-vcbrA4 (last 
written to /dev/mapper/crypt_vdb1).
  2 logical volume(s) in volume group "vg00" now active

(The warning message is expected as at this stage the VG has some missing PVs. 
The LV containing the rootfs can be activated because it has no extents on 
those missing PVs. In prior Debian versions the initramfs would properly 
activate such LVM VGs, with the available LVs at that time. Now a manual 
activation is needed.)

After exiting the initramfs shell, the system will boot just fine.



As a workaround, it's possible to split the LVM VG, so that it has no missing 
PVs at the initramfs stage. But there are some setups such as LVM cache that 
require that all involved PVs be on the same VG, so there is some loss of 
functionality with this workaround.

vgsplit vg00 vg01 /dev/mapper/crypt_vdb1

After the last step, the system will again boot fine.




Expected results: the initramfs should behave in a similar way to previous 
versions, activating the LVM LVs available at that stage, so that the rootfs 
can be properly mounted.

Bug#1038730: fribidi: please make the build reproducible

[Chris Lamb]

Source: fribidi
Version: 1.0.13-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed that
fribidi could not be built reproducibly.

This is because the new-to-unstable code to alter CFLAGS (added via
#930791) resulted in the build dropping the -fdebug-prefix-map GCC
flags.

A patch is attached that ensures that the 'fallback' CFLAGS will
always be included.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2023-06-20 17:52:39.441913687 +0100
--- b/debian/rules  2023-06-20 17:57:00.402466109 +0100
@@ -15,7 +15,7 @@
dh $@
 
 override_dh_auto_configure:
-   dh_auto_configure -- --enable-malloc --enable-static 
CFLAGS="${DEB_CFLAGS}"
+   dh_auto_configure -- --enable-malloc --enable-static CFLAGS="$(shell 
dpkg-buildflags --get CFLAGS) ${DEB_CFLAGS}"
 
 override_dh_makeshlibs:
dh_makeshlibs -V --add-udeb="$(FRIBIDI_UDEB)"

Bug#1038720: Missing hyperv_fb.ko in debian 12.0 kernel image 6.1.0-9-amd64

[Ben Hutchings]

On Tue, 2023-06-20 at 17:03 +0200, Bastian Blank wrote:
> On Tue, Jun 20, 2023 at 03:32:19PM +0200, RSA wrote:
> > Hello, I think kernel module hyperv_fb.ko is missing in the package. It was 
> > present in version 5.10.0-22 before upgrading to debian 12.
> > 
> > $ find /lib/modules/5.10.0-23-amd64 -name hyperv_fb.ko
> > /lib/modules/5.10.0-23-amd64/kernel/drivers/video/fbdev/hyperv_fb.ko
> > $ find /lib/modules/6.1.0-9-amd64 -name hyperv_fb.ko
> > 
> > The impact is a regression when using debian as an Hyper-V vm. Screen 
> > resolution can not be changed anymore when editing 
> > GRUB_CMDLINE_LINUX_DEFAULT.
> 
> This was replaced by hyperv_drm, which provides a standard mode
> selection output.

...although we do still build hyperv_fb for the cloud-amd64 flavour,
which seems like a mistake.

Ben.

> Not sure what you did with the kernel command line.

-- 
Ben Hutchings
compatible: Gracefully accepts erroneous data from any source



signature.asc
Description: This is a digitally signed message part

Bug#1034495: ITP: linux-board-support-package-dragonboard845c -- Firmware for dragonboard845c / RB3

[Dmitry Baryshkov]

Hi Roger,

Just to note, we have updated linux-firmware with the files from
http://releases.linaro.org/96boards/dragonboard845c/qualcomm/firmware/RB3_firmware_2022112100-v5.zip

Please consider following this change.

-- 
With best wishes
Dmitry

Bug#1034546: RFS: luametatex/2.10.07-1 [ITP] -- Next generation ConTeXt processing engine

[Preuße]

Control: severity -1 normal

On 01.06.2023 09:53, Preuße...@buxtehude.debian.org, Hilmar wrote:

On 17.04.2023 23:44, Hilmar Preusse wrote:


Hi,

Ping! Would anybody so kind to upload to experimental? That package is 
prereq for the next version of ConTeXt.



Setting to Sev. normal.

Hilmar
--
sigfault



OpenPGP_0x0C871C4C653C1F59.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1038729: xkb-data: Upgrade wants to remove nVidia drivers

[Nicolas Patrois]

Package: xkb-data
Version: 2.35.1-1
Severity: normal

Dear Maintainer,

Upgrading xkb-data wants me to remove these automatically installed packages:

  libegl-nvidia-legacy-390xx0 libgl1-nvidia-legacy-390xx-glvnd-glx libgles-
nvidia-legacy-390xx1
  libgles-nvidia-legacy-390xx2 libnvidia-legacy-390xx-eglcore libnvidia-
legacy-390xx-encode1
  libnvidia-legacy-390xx-nvcuvid1 nvidia-egl-common nvidia-legacy-390xx-driver-
bin
  nvidia-legacy-390xx-driver-libs nvidia-legacy-390xx-egl-icd nvidia-settings-
legacy-390xx virtualbox-guest-utils
  xcvt xserver-xorg-legacy

Sorry xkb-data but I need them for my old graphic card.

Yours,
n.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 5.16.0-6-686-pae (SMP w/3 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Bug#1038728: Coordinating libzstd 1.5.5 + python-zstandard 0.21.0 upload

[Boyuan Yang]

Source: libzstd
Severity: normal
Version: 1.5.4+dfsg2-5
Tags: sid
Control: affects -1 src:python-zstandard
X-Debbugs-CC: r...@debian.org

Dear Debian libzstd maintainer,

As we discussed months ago, we would like to coordinate on the package
upload between src:libzstd and src:python-zstandard to use libzstd with
matched versions.

Please let me know when you plan to upgrade libzstd, and I shall coordinate
the upgrade of src:python-zstandard to match libzstd release. Currently
python-zstandard/0.21.0 needs libzstd/1.5.5.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part

Bug#1038727: bookworm-pu: package nftables/1.0.6-2+deb12u1

[Arturo Borrero Gonzalez]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: nftab...@packages.debian.org
Control: affects -1 + src:nftables

There has been a behavior regression reported in nftables when
upgrading from Debian 11 Bullseye to Debian 12 Bookworm.

The change is in how nftables prints the set definitions, with
or without set elements by default.

Some user tools relying on 'nft -j list sets' fail after upgrading
to Debian Bookworm from Debian Bullseye because the behavior change.

The small upstream fix makes the behavior coherent and predictable for the
set listing action.

There is not much risk in this update:
* The fix patch has been provided directly by upstream
* The fix has been applied to upstream main branch already
* The fix is already in Debian Sid

Find debdiff attached against the current Debian stable package.

See also:
 * https://marc.info/?l=netfilter=168704941828372=2 (original report)
 * https://bugs.debian.org/1038724 (debian bug)
 * 
https://git.netfilter.org/nftables/commit/?id=29bed4fa594c3f6e343a8b5669d61e20c7129cca
 (upstream fix)
diff -Nru nftables-1.0.6/debian/changelog nftables-1.0.6/debian/changelog
--- nftables-1.0.6/debian/changelog 2023-01-29 12:33:00.0 +0100
+++ nftables-1.0.6/debian/changelog 2023-06-20 16:55:52.0 +0200
@@ -1,3 +1,9 @@
+nftables (1.0.6-2+deb12u1) bookworm; urgency=medium
+
+  * [7edf72e] d/patches: add 0001-debian-bug-1038724.patch (Closes: #1038724)
+
+ -- Arturo Borrero Gonzalez   Tue, 20 Jun 2023 16:55:52 
+0200
+
 nftables (1.0.6-2) unstable; urgency=medium
 
   [ Jeremy Sowden ]
diff -Nru nftables-1.0.6/debian/patches/0001-debian-bug-1038724.patch 
nftables-1.0.6/debian/patches/0001-debian-bug-1038724.patch
--- nftables-1.0.6/debian/patches/0001-debian-bug-1038724.patch 1970-01-01 
01:00:00.0 +0100
+++ nftables-1.0.6/debian/patches/0001-debian-bug-1038724.patch 2023-06-20 
16:55:52.0 +0200
@@ -0,0 +1,66 @@
+From 29bed4fa594c3f6e343a8b5669d61e20c7129cca Mon Sep 17 00:00:00 2001
+From: Florian Westphal 
+Date: Sun, 18 Jun 2023 18:39:45 +0200
+Subject: cache: include set elements in "nft set list"
+
+Make "nft list sets" include set elements in listing by default.
+In nftables 1.0.0, "nft list sets" did not include the set elements,
+but with "--json" they were included.
+
+1.0.1 and newer never include them.
+This causes a problem for people updating from 1.0.0 and relying
+on the presence of the set elements.
+
+Change nftables to always include the set elements.
+The "--terse" option is honored to get the "no elements" behaviour.
+
+Fixes: a1a6b0a5c3c4 ("cache: finer grain cache population for list commands")
+Link: https://marc.info/?l=netfilter=168704941828372=2
+Signed-off-by: Florian Westphal 
+---
+ src/cache.c | 2 ++
+ src/rule.c  | 8 +---
+ 2 files changed, 3 insertions(+), 7 deletions(-)
+
+diff --git a/src/cache.c b/src/cache.c
+index 95adee7f..becfa57f 100644
+--- a/src/cache.c
 b/src/cache.c
+@@ -235,6 +235,8 @@ static unsigned int evaluate_cache_list(struct nft_ctx 
*nft, struct cmd *cmd,
+   case CMD_OBJ_SETS:
+   case CMD_OBJ_MAPS:
+   flags |= NFT_CACHE_TABLE | NFT_CACHE_SET;
++  if (!nft_output_terse(>output))
++  flags |= NFT_CACHE_SETELEM;
+   break;
+   case CMD_OBJ_FLOWTABLE:
+   if (filter &&
+diff --git a/src/rule.c b/src/rule.c
+index 633a5a12..1faa1a27 100644
+--- a/src/rule.c
 b/src/rule.c
+@@ -1574,11 +1574,6 @@ static int do_list_table(struct netlink_ctx *ctx, 
struct table *table)
+ 
+ static int do_list_sets(struct netlink_ctx *ctx, struct cmd *cmd)
+ {
+-  struct print_fmt_options opts = {
+-  .tab= "\t",
+-  .nl = "\n",
+-  .stmt_separator = "\n",
+-  };
+   struct table *table;
+   struct set *set;
+ 
+@@ -1601,8 +1596,7 @@ static int do_list_sets(struct netlink_ctx *ctx, struct 
cmd *cmd)
+   if (cmd->obj == CMD_OBJ_MAPS &&
+   !map_is_literal(set->flags))
+   continue;
+-  set_print_declaration(set, , >nft->output);
+-  nft_print(>nft->output, "%s}%s", opts.tab, 
opts.nl);
++  set_print(set, >nft->output);
+   }
+ 
+   nft_print(>nft->output, "}\n");
+-- 
+cgit v1.2.3
+
diff -Nru nftables-1.0.6/debian/patches/series 
nftables-1.0.6/debian/patches/series
--- nftables-1.0.6/debian/patches/series2023-01-29 12:33:00.0 
+0100
+++ nftables-1.0.6/debian/patches/series2023-06-20 16:55:52.0 
+0200
@@ -1 +1,2 @@
+0001-debian-bug-1038724.patch
 invalid-octal-fix.patch

Bug#1038720: Missing hyperv_fb.ko in debian 12.0 kernel image 6.1.0-9-amd64

[Bastian Blank]

On Tue, Jun 20, 2023 at 03:32:19PM +0200, RSA wrote:
> Hello, I think kernel module hyperv_fb.ko is missing in the package. It was 
> present in version 5.10.0-22 before upgrading to debian 12.
> 
> $ find /lib/modules/5.10.0-23-amd64 -name hyperv_fb.ko
> /lib/modules/5.10.0-23-amd64/kernel/drivers/video/fbdev/hyperv_fb.ko
> $ find /lib/modules/6.1.0-9-amd64 -name hyperv_fb.ko
> 
> The impact is a regression when using debian as an Hyper-V vm. Screen 
> resolution can not be changed anymore when editing GRUB_CMDLINE_LINUX_DEFAULT.

This was replaced by hyperv_drm, which provides a standard mode
selection output.

Not sure what you did with the kernel command line.

Bastian

-- 
Where there's no emotion, there's no motive for violence.
-- Spock, "Dagger of the Mind", stardate 2715.1

Bug#1038726: ITP: qatlib -- Intel(R) QuickAssist Technology hardware accelleration for security authentication and compression

[Colin King (gmail)]

Package: wnpp
Severity: wishlist
Owner: Colin Ian King 
X-Debbugs-Cc: debian-de...@lists.debian.org, colin.i.k...@gmail.com

* Package name: qatlib
  Version : 23.02.0
  Upstream Contact: giovanni.cabi...@intel.com
* URL : https://github.com/intel/qatlib
* License : BSD-3-Clause
  Programming Lang: C, x86 assemvler
  Description : Intel(R) QuickAssist Technology hardware 
accelleration for security authentication and compression


Intel(R) QuickAssist Technology (Intel(R) QAT) provides hardware
acceleration for offloading security, authentication and compression
services from the CPU, thus significantly increasing the performance
and efficiency of standard platform solutions.

Its services include symmetric encryption and authentication, asymmetric
encryption, digital signatures, RSA, DH and ECC, and lossless data
compression.

It provides user space libraries that allow access to Intel(R) 
QuickAssist devices and expose the Intel(R) QuickAssist APIs and sample 
codes.


See also: https://wiki.debian.org/QAT

I intend to maintain this much like other Intel related Debian packages

Sincerely,

Colin Ian King

Bug#1038725: gnustep-base: NSURL tests can fail due to httpbin.org being unreliable

[Adrien Nader]

Source: gnustep-base
Version: 1.29.0-4
Severity: normal
Tags: patch upstream

Hi,

While working on Ubuntu's migrations, I noticed gnustep-base would
FTBFS due to network tests failing.
There's an upstream commit to improve this:

  
https://github.com/gnustep/libs-base/commit/7e14fd1979963cf413a231ef6e9deefad89f233e

  Change NSURL tests to use example.com

  httpbin.org has lately been unreliable, leading to spurious test failures on 
CI.

While the package for unstable built successfully and the issues with
httpbin.org seem fixed, I still wanted to report this since it is
possible you encounter the issue with a future upload.

If this happens more frequently, maybe a solution would be to use a
debian hostname since they should not be failing when the CI is working.

-- 
Adrien