Bug#1033625: closed by Brian Potkin (Re: Bug#1033625:)

[Johan Kröckel]

So this is a bug in cups-browsed?

Am Do., 30. März 2023 um 19:23 Uhr schrieb Brian Potkin <
claremont...@gmail.com>:

> On Thu 30 Mar 2023 at 15:54:09 +0200, Johan Kröckel wrote:
>
> > Hi Brian,
> >
> > thanks for your help. But isn't it still a bug that cups is creating a
> > printer(-queue) that not only does not work, but also when using it opens
> > connections to the printer for hours? I think about the situation, that
> you
> > have many bookworm clients in the network, this could amount to a denial
> of
> > service.
> >
> > I deleted the not working Kyocera_ECOSYS_M5526cdw but cups keeps
> recreating
> > it when I connect to the corresponding network.
>
> The auto-creation of the queue (the one shown by 'lpstat -t' and that keeps
> coming back after deletion) is done by cups-browsed, not by CUPS. Let's try
> this:
>
> Purge cups-browsed with
>
>  apt purge cups-browsed
>
> Then do
>
>  rm  rm /var/cache/cups/*
>
> (the files will be regenerated) and restart cups.
>
>  systemctl restart cups
>
> 'lstsat -l -e' should show a printer name. Can it be used to print?
> 'lpstat -t'
> should not have implicitclass and should show the manually set up printer,
>
> Cheers,
>
> Brian.
>

Bug#580152: Still an issue in current apt

[Josh Triplett]

I ran into this recently.

For .d directories like /etc/apt/preferences.d, it'd be nice if apt were
silent about the directory not existing, and if it just treated that the
same as an empty directory.

Bug#1034076: unblock: spf-engine/3.0.4-1

[Scott Kitterman]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package spf-engine

(Please provide enough (but not too much) information to help
the release team to judge the request efficiently. E.g. by
filling in the sections below.)

[ Reason ]
Fixes a bug that will cause mail processing to stop for systems which
send mail to/from local users that doesn't have a fully qualified domain
name.  This a regression from Bullseye.

[ Impact ]
For most users, none, but for users sending to local addresses, mail
will stop flowing after upgrade from Bullseye to Bookworm.

[ Tests ]
The affected code was tested by the original bug reporter and they
verified that the fix worked without unwanted side effects.

[Risks ]
Risk is negligible.  Very small code change that's been tested.  There
is not autopkgtest as the upstream test suite (such as it is, I'm not
proud of it) isn't suitable.  This is a leaf package, so there's no risk
of negative effects on other packages.

[ Checklist ]
  [*] all changes are documented in the d/changelog
  [*] I reviewed all changes and I approve them
  [*] attach debdiff against the package in testing

[ Other info ]
I haven't uploaded this yet, but it's prepared in git locally for upload
if approved.  The only thing I have to do relative to what's in the
debdiff is dch -r to mark it released.

This is something I would ask for a post-release update to fix if I
didn't find out about until after Bookworm's release.

unblock spf-engine/3.0.4-1
diff -Nru spf-engine-3.0.3/CHANGES spf-engine-3.0.4/CHANGES
--- spf-engine-3.0.3/CHANGES2023-02-19 19:30:05.819651600 -0500
+++ spf-engine-3.0.4/CHANGES2023-04-07 20:46:47.963843000 -0400
@@ -4,6 +4,10 @@
 #   ! = Changed something significant, or removed a feature
 #   * = Fixed a bug, or made a minor improvement
 
+--- 3.0.4 (2023-04-07)
+  * Fix recipient logging to not cause an error for local (not fully
+qualified) email addresses (LP: #2015609)
+
 --- 3.0.3 (2023-02-19)
   * Fix reference to QueueID in policydspfsupp.py (LP: #2007123), thanks to
 Wolfgang Karall-Ahlborn for the bug and the fix
diff -Nru spf-engine-3.0.3/debian/changelog spf-engine-3.0.4/debian/changelog
--- spf-engine-3.0.3/debian/changelog   2023-02-19 20:13:27.0 -0500
+++ spf-engine-3.0.4/debian/changelog   2023-04-08 00:06:57.0 -0400
@@ -1,3 +1,9 @@
+spf-engine (3.0.4-1) UNRELEASED; urgency=medium
+
+  * New upstream release
+
+ -- Scott Kitterman   Sat, 08 Apr 2023 00:06:57 -0400
+
 spf-engine (3.0.3-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru spf-engine-3.0.3/PKG-INFO spf-engine-3.0.4/PKG-INFO
--- spf-engine-3.0.3/PKG-INFO   1969-12-31 19:00:00.0 -0500
+++ spf-engine-3.0.4/PKG-INFO   1969-12-31 19:00:00.0 -0500
@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: spf-engine
-Version: 3.0.3
+Version: 3.0.4
 Summary: SPF (Sender Policy Framework) processing engine for Postfix policy 
server and Milter implemented in Python.
 Keywords: Postfix,Sendmail,milter,spf,email
 Author-email: Scott Kitterman 
diff -Nru spf-engine-3.0.3/spf_engine/__init__.py 
spf-engine-3.0.4/spf_engine/__init__.py
--- spf-engine-3.0.3/spf_engine/__init__.py 2023-02-19 19:30:53.016298500 
-0500
+++ spf-engine-3.0.4/spf_engine/__init__.py 2023-04-07 22:36:19.567618000 
-0400
@@ -40,7 +40,7 @@
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 '''
 
-__version__ = "3.0.3"
+__version__ = "3.0.4"
 
 import syslog
 import os
diff -Nru spf-engine-3.0.3/spf_engine/policyd_spf.py 
spf-engine-3.0.4/spf_engine/policyd_spf.py
--- spf-engine-3.0.3/spf_engine/policyd_spf.py  2022-12-01 21:07:37.670749200 
-0500
+++ spf-engine-3.0.4/spf_engine/policyd_spf.py  2023-04-07 20:44:54.125643300 
-0400
@@ -94,7 +94,10 @@
 elif configData.get('Hide_Receiver') != 'No':
 data['recipient'] = ''
 elif data.get('recipient') != 'none':
-data['recipient'] = data.get('recipient').split('@')[1]
+try:
+data['recipient'] = data.get('recipient').split('@')[1]
+except IndexError:
+pass # local recipients may not be fully qualified, so no 
"@".
 if debugLevel >= 3: syslog.syslog('Config: %s' % str(configData))
 #  run the checkers  {{{3
 checkerValue = None

Bug#1034062: netcfg prompts for hostname even though preseeded, preventing unattended installation

[Oliver Freyermuth]

Hello Cyril,

Am 07.04.23 um 23:23 schrieb Cyril Brulebois:

Oliver Freyermuth  (2023-04-07):

Potentially relevant kernel commandline parameters:
netcfg/disable_dhcp=false ethdetect/prompt_missing_firmware=false 
hw-detect/load_firmware=false locale=en_US.UTF-8 hostname=laptop.example.com 
domain=example.com


This is likely #1031643, try using the full netcfg/get_hostname name
instead of the hostname alias on the kernel command line?


indeed, that seems to be the case — I can confirm using the full 
netcfg/get_hostname name on the kernel command line prevents the question from 
being shown,
and preseeding proceeds unattendedly again. :-)
That easily explains why I did not find any code changes in netcfg which could 
explain this change in behaviour, since the reason is due to a kernel behavipur 
change.

So this can probably be closed as a duplicate of #1031643.

I concur that the question is where to go from here — my real-world use case is using 
Foreman [0] for machine deployment, which currently passes "hostname" 
exclusively in its preseed/PXE templates.
If the decision is to drop support for the hostname alias, deployment software 
like this one will of course need to be adapted (considering the alternatives, 
that is certainly a viable option).
I'll hold back on upstreaming this change to Foreman until a decision on how to 
proceed with #1031643 is made.

Thanks a lot and cheers,
Oliver

[0] https://theforeman.org/

Bug#1034071: u-boot-menu: Does not show a menu due to 'prompt 0'

[Vagrant Cascadian]

On 2023-04-08, Diederik de Haas wrote:
> As the subject says, u-boot-menu doesn't show a (boot) menu as the
> 'prompt' setting has a hardcoded value of '0'. If you'd change that to
> say '5' then you do see a menu from which you can choose.
> But the next time you'd run 'u-boot-update' that value gets overwritten.

Old versions of u-boot basically ignore this value in my experience, but
that bug was fixed in upstream u-boot 2023.04:

  
https://source.denx.de/u-boot/u-boot/-/commit/739e8361f3fe78038251216df6096a32bc2d5839


> It would be great if this could still make it into Bookworm and I do
> believe this is a targeted fix. I set 'Severity: normal', but a case can
> be made for a higher severity as 'u-boot-menu' doesn't show a menu.
> I'd be also fine with a default value of '0', so that the only change
> would be to make 'prompt' configurable.

The version of u-boot in bookworm (2023.01) should not be affected, so
it is somewhat less urgent... or are you experiencing this issue with
u-boot as shipped in bookworm?

Before changing the default behavior, I was thinking of proposing a
patch for bookworm that kept the current behavior but allowed overriding
it... that would at least be reasonably cautious.

I had intended to test a few different versions to see how they were
affected before moving forward with that... but I did not get around to
it and we are now very late in the freeze.

If it proves harmless on the version of u-boot in bookworm (2023.01*)
and bullseye (2021.01*), and if we are being really careful, buster
(2019.01*) ... then I think it would be good to consider for bookworm,
or maybe the first bookworm point release?


Thanks for submitting the patch and merge request!

> diff --git a/u-boot-update b/u-boot-update
> index 90c4087..c726c9e 100755
> --- a/u-boot-update
> +++ b/u-boot-update
> @@ -96,6 +96,7 @@ fi
>  
>  U_BOOT_ALTERNATIVES="${U_BOOT_ALTERNATIVES:-default recovery}"
>  U_BOOT_DEFAULT="${U_BOOT_DEFAULT:-l0}"
> +U_BOOT_PROMPT="${U_BOOT_PROMPT:-5}"
>  U_BOOT_ENTRIES="${U_BOOT_ENTRIES:-all}"
>  U_BOOT_TIMEOUT="${U_BOOT_TIMEOUT:-50}"
>  U_BOOT_MENU_LABEL="${U_BOOT_MENU_LABEL:-${PRETTY_NAME:-Debian GNU/Linux 
> kernel}}"

My only question here is why "5" vs. say, "1"? I *think* it is
effectively a zero/non-zero boolean.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1005369: xserver-xorg-core: Breaks middle button trackpoint scrolling

[Alban Browaeys]

Could you check that your bug is reproducible with xorg libinput (that
you do not want but still if only xserver-xorg-input-synaptics is at
fault there should this bug be moved to)?

Your issue was with xserver-xorg-core 2:21.1.3-2 and you told that
reverting to the version in testing fixed the issue. Which version was
this testing xserver-xorg-core that fixed the issue?

Nowadays testing and unstable both have xserver-xorg-core 21.1.7-2.
With xserver-xorg-input-libinput 1.2.1-1+b1, on my Lenovo Thinkpad Yoga
S1 I can scroll with middle button press and trackpoint up and down.

If you do not want to even test with xserver-xorg-input-libinput (and 
xserver-xorg-input-synaptics at least temporiraly uninstalled if
installed else it will take precedence. I believe xserver-xorg-input-
evdev is lower priority thant xserver-xorg-input-libinput but you might
want to temporiraly uninstall it too) could you confirm the issue still
exists with current packages (and with all upgrades done ... partial
upgrade might break functionality.



xserver-xorg-input-synaptics is not supported anymore by gnome.
Migrating from Debian to another distribution will not change the fact
that any upstreams are now requiring libinput.



Cheers,
Alban


Le mercredi 05 avril 2023 à 23:56 +0200, Salvo Tomaselli a écrit :
> Yes it has some options. Not as many as the alternatives. Some of
> those options happen to be ones that I change.
> 
> Il giorno mer 5 apr 2023 alle ore 02:22 Alban Browaeys
>  ha scritto:
> > 
> > I am on a thinkapd (the Yoga S1) and xorg libinput driver works
> > fine (I
> > configure it through gnome-control-center).
> > 
> > I really do not know what you mean by "avoid libinput's opinions on
> > how
> > my input should work". Could you give example?
> > 
> > https://www.mankier.com/4/libinput
> > these do not count as configuration options?
> > 
> > Cheers,
> > 
> > Alban
> > 
> > 
> > Le mardi 04 avril 2023 à 21:21 +0200, Salvo Tomaselli a écrit :
> > > No the libinput one is bad.
> > > 
> > > libinput's author doesn't want options, so there is no way to
> > > have
> > > usable input that feels good on thinkpads.
> > > 
> > > I'm using the xserver-xorg-input-evdev one. I guess when Xorg
> > > will be
> > > kicked out of debian, I will need to move to devuan or something
> > > like
> > > that, just to avoid libinput's opinions on how my input should
> > > work.
> > > 
> > > Il giorno mar 4 apr 2023 alle ore 18:45 Alban Browaeys
> > >  ha scritto:
> > > > 
> > > > Try removing
> > > > xserver-xorg-input-synaptics
> > > > then restart xorg.
> > > > 
> > > > xserver-xorg-input-synaptics i sno longer supported by GNOME as
> > > > far
> > > > as
> > > > know.
> > > > xserver-xorg-input-libinput is the replacment.
> > > > 
> > > > Cheers,
> > > > Alban
> > > > 
> > > > On Sat, 12 Feb 2022 09:53:16 +0100 "Salvo \"LtWorf\" Tomaselli"
> > > >  wrote:
> > > > > Package: xserver-xorg-core
> > > > > Version: 2:21.1.3-2
> > > > > Severity: critical
> > > > > Tags: upstream
> > > > > Justification: breaks unrelated software
> > > > > X-Debbugs-Cc: tipos...@tiscali.it
> > > > > 
> > > > > Dear Maintainer,
> > > > > 
> > > > > on thinkpads it is common to scroll by holding down the
> > > > > middle
> > > > > button
> > > > and
> > > > > pushing the trackpoint up or down.
> > > > > 
> > > > > After upgrading, this feature is broken.
> > > > > 
> > > > > Reverting to the version found in testing makes it work
> > > > > again.
> > > > > 
> > > > > In a wayland session it works (but my keyboard layout doesn't
> > > > > exist
> > > > in wayland
> > > > > so using it permanently is not a viable solution).
> > > > > 
> > > > > It is strange because the input drivers have not received an
> > > > > update,
> > > > so I'm not
> > > > > really sure of what the interaction is here.
> > > > > 
> > > > > Anyway, I'm creating this issue with a high priority in order
> > > > > to
> > > > > stop
> > > > the package
> > > > > from migrating and make scrolling suddenly unavailable to
> > > > > other
> > > > people as well.
> > > > > 
> > > > > -- Package-specific info:
> > > > > /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
> > > > TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01)
> > > > > 
> > > > > /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 5.16.0-1-amd64 (debian-ker...@lists.debian.org)
> > > > > (gcc-11
> > > > (Debian 11.2.0-16) 11.2.0, GNU ld (GNU Binutils for Debian)
> > > > 2.37.90.20220130) #1 SMP PREEMPT Debi

Bug#1025069: pavucontrol

[Alban Browaeys]

Do you have jackd installed and runnning at the same time as pipewire-
pulse?
Maybe you want to try piepwire-jack instead?

Cheers,
Alban


On Fri, 31 Mar 2023 06:22:38 -0500 Lucas  wrote:
> Here's a correction:  I shutdown and started it again, and the
> pavucontrol setup was retained.  So, I continued testing by running
> ardour, knowing it's set to use JACK through ALSA.  It played fine,
> but when I quit it, I wasn't able to hear pulseaudio, nor select the
> same pavucontrol profile.  Luckily, there's a "Pro Audio"
> Configuration in pavucontrol that works too.  I retested ardour with
> it and later standard pulseaudio playback, and it continues to work!
> I wouldn't say this is fixed, but I consider it much improved, by
> these findings, and almost tolerable.
> 
> 

Bug#1034075: ITP: tree-sitter-lua -- Lua grammar for tree-sitter

[James McCoy]

Package: wnpp
Severity: wishlist
Owner: James McCoy 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: tree-sitter-lua
  Version : 0.0.14
  Upstream Contact: Munif Tanjim 
* URL : https://github.com/MunifTanjim/tree-sitter-lua
* License : MIT
  Programming Lang: JavaScript, C, Rust
  Description : Lua grammar for tree-sitter

This package provides a tree-sitter parser for Lua.

This is needed for Neovim's tests and is one of the tree-sitter parsers
expected to be available.  It will be maintained in the tree-sitter
team.

Bug#1034038: Please push babel.sty v3.87 or later into the upcoming distribution

[Al Ma]

Thank you, Hilmar, the result looks good: your packages resolve the issue 
http://tex.stackexchange.com/questions/680690 
http://tex.stackexchange.com/questions/680690.  While installing your packages, 
I had to use dpkg -i -B (rather than the usual dpkg -i ); if this is how the 
installation is supposed to succeed, please feel free to push them to Debian. 
(Caveat: I have not tested xetex and I have not installed texlive-full, so I 
can say nothing about these two packages.)

Bug#1034050: fonts-creep2: generated font is TrueType, not OpenType

[Agathe Porte]

Hi Nate,

2023-04-07 16:14 CEST, nwil...@glyphography.com:
> > The generated font is a TrueType font, not an OpenType font. This does
> > not impact the useability of the package to my knowledge, but would be
>
> On the contrary, all TrueType fonts are also OpenType fonts. OpenType is a
> superset of TrueType, which is older.

Thanks, TIL.

> Similarly, if the intent is to make some sort of distinction based on the
> contents of the tables (e.g., GSUB and GPOS), then the filename extension
> still isn't adequate, because .ttf files can and do include those tables
> (see Noto and many many others).

I do not know how to inspect the tables, but the `file` tool indicates
that creep2.ttf (provided by upstream) and creep2.otb (built by the
package) are reported as TrueType fonts with BDF tables:

$ file creep2.{ttf,otb}
$ creep2.ttf: TrueType Font data, 16 tables, 1st "BDF ", 14 names, Macintosh
$ creep2.otb: TrueType Font data, 15 tables, 1st "BDF ", 14 names, Macintosh

If I take an other font in the opentype directory, the `file` tool
report the file as OpenType:

$ file /usr/share/fonts/opentype/cantarell/Cantarell-Bold.otf
/usr/share/fonts/opentype/cantarell/Cantarell-Bold.otf: OpenType font data

> > nice to be fixed. This bug is reported by Lintian under the tag
> > `truetype-font-wrong-filename`.
>
> Well, if that's so, then this indicates that Lintian is likely overdue for a
> refresh on how it determines these things. That might be a big undertaking;
> I don't know at the moment.

I have looked at the source code of Lintian, and the current checks [1]
are quite simple. Quoting:

return
  unless $file->file_type =~ /^TrueType Font data/;

$self->pointed_hint('truetype-font-wrong-filename', $file->pointer)
  unless $file->name =~ /\.ttf$/i;

So the check is "if the file type is TrueType and extension != .ttf,
report warning".

[1] 
https://salsa.debian.org/lintian/lintian/-/blob/ea05801918ed0e87824d89bf16a6ee166450b977/lib/Lintian/Check/Fonts/Truetype.pm

> However, with this particular font:
> >
> > The problem is that the font is located in /usr/share/fonts/opentype
> > instead of /usr/share/fonts/truetype, and that its name is creep2.otb
> > instead of creep2.ttf.
>
> The .otb extension (as well as the .bdf in the package) indicates that this
> is a bitmap font re-wrapped in an OpenType table structure (see
> https://github.com/fonttools/fonttools/issues/684 for the history, and code
> at https://github.com/freedesktop/fonttosfnt or possibly
> https://github.com/ctrlcctrlv/bitmapfont2otb for the internal details); that
> definitely makes it an OpenType font and not a TrueType font, because the
> older TrueType spec did not allow that sort of skullduggery: it required
> vector outlines.

I really have the impression that the generated file has a TrueType
table structure instead of an OpenType table structure according to the
`file` command (and the check done by lintian on the file_type). I
really need to find a way to be sure that the creep2.otb file is really
an Opentype file and not "just" a TrueType file.

I manually add this .otb extension in the fontforge script, but I think
sourceforge is not generating what I want.

> Not all proprietary apps and platforms recognize this usage nor the ".otb"
> extension itself, but HarfBuzz / FreeType / Pango do.

In fact I think that this font is the first "otb" font in Debian, so I
think we should take time to discuss if the resulting font is properly
generated as an example for future other Opentype bitmap fonts.

> > Proposed solution is to rename the directory and the font itself to
> > match the TTF filetype.
>
> Just doing a rename of the binary file could trigger accidental breakage for
> users on apps/stacks who aren't running HarfBuzz / FreeType etc (as above)
> via the standard, modern stack. That would not seem to be a beneficial
> change.
>
> Long term, the underlying fix is that Lintian's font-detection likely needs
> a scrubbing by somebody with a lot more free time at hand than me (although
> billionaires who wish to fund this should still reach out...).
>
> *Long* long term, the FHS and so on likely really need to drop the
> */truetype/ */opentype/ directory distinction, since it's not doing anything
> useful. It's a bit like saying there should be separate /jpg/ and /jpeg/
> directories and older images should only be put in one of them
>
> I know this TTF/OTF confusion is widespread, but I maintain that fixing it
> is still possible

You seem to really know your stuff more than I do. I packaged this font
for fun and to use it sometimes. My current problem is that I am not
sure that the creep2.otb font is *actually* an OpenType font.

But if you say that all TrueType fonts are OpenType fonts, then I guess
I cannot verify this easily. I need your expertise to know if the file
is correct and I should ignore lintian, or if the file is incorrect and
I should fix it somehow.

Thanks,

Agathe.

Bug#996367: pipewire issues with M-Audio 410

[Alban Browaeys]

Alexandre, could you close this bug report as you told it to
be solved?

See https://www.debian.org/Bugs/Developer#closing
That is, if you know the version that fixed the issue, add the pseudo-
header
Version: 
if you do not know the version, do not include this Version pseudo-
header.

If you know what fixed the bug tell in the email body.


and then send this email to 996367-d...@bugs.debian.org to close this
bug.
 

Cheers,
Alban


On Fri, 18 Nov 2022 19:33:34 -0300 Alexandre Lymberopoulos
 wrote:
> Hello, Dylan!
> 
> Things are going much better with the new releases: 996367 seems to
be 
> solved, but 997915 persists. For the latter it seems to be something 
> like capturing sources with different sample rates (like 48Khz and 
> 44Khz). This guess is due to the resulting sound: the "default" 
> recording device (as selected with pavucontrol - have pipewire, pulse
> and jack installed here! more on this later) have nice sound and the 
> other sounds like playing a standard 33rpm vinyl in 45rpm (revealing
my 
> age here) with a lot of clips.
> 
> To make things tidy and clean here I would like to know if there is a
> way to keep just pipewire running here (over ALSA, probably) and if 
> there are some mixer software to use with pipewire (ffado-mixer
stopped 
> working with M-Audio 410 here).
> 
> Best,
> Alexandre
> 
>
===

> Alexandre Lymberopoulos - lym...@gmail.com
>
===

> 
> 
> On Fri, Nov 18 2022 at 02:54:57 PM +01:00:00, Dylan Aïssi 
>  wrote:
> > Hello Alexandre,
> > 
> > My apologies for not responding earlier.
> > 
> > Do you still have these problems with pipewire or have they been 
> > solved
> > with the new versions?
> > 
> > Best,
> > Dylan
> 
> 
> 
> 

Bug#1034074: RFP: rtlsdr-scanner -- radio frequency scanning GUI using the OsmoSDR rtl-sdr library

[Petter Reinholdtsen]

Package: wnpp
Severity: wishlist

  Package name: rtlsdr-scanner
  Version : 1.3.2
  Upstream Author :
  URL : https://github.com/ParrotSec/rtlsdr-scanner
  License : GPL
  Programming Lang: Python
  Description : radio frequency scanning GUI using the OsmoSDR rtl-sdr 
library

The package is already in Kali and the source of their Debian package
is available from
https://gitlab.com/kalilinux/packages/rtlsdr-scanner.git >.
In addition two runtime dependencies
https://gitlab.com/kalilinux/packages/python-visvis.git > and 
https://gitlab.com/kalilinux/packages/python-rtlsdr.git > are
needed.

-- 
Happy hacking
Petter Reinholdtsen

Bug#1034023: nmu: python-libzim_2.1.0+ds-1

[Bastian Germann]

Am 07.04.23 um 21:15 schrieb Paul Gevers:

Hi Bastian,

On 07-04-2023 21:01, Paul Gevers wrote:

Hi,

On 06-04-2023 18:47, Bastian Germann wrote:

Please rebuild python-libzim against the new zimlib.


But zimlib should not have been uploaded to unstable before the bookworm 
release. Please see bug 1027959 for discussion.


If the breaking change that that bug mentions is the one why 8.1.0 was reverted 
it is gone in 8.1.1.
I had built the reverse deps including kiwix before uploading and they were 
fine.

Bug#1034073: ITP: ruby-digest-crc -- A gem that adds support for calculating Cyclic Redundancy Check (CRC) to the Digest module

[Ravi Dwivedi]

package: wnpp
Severity: wishlist
Owner: 'Ravi Dwivedi' 

*Package Name : ruby-digest-crc
 Version : 0.4.0
 Upstream Author : Postmodern
*URL :  https://github.com/postmodern/digest-crc
*License : Expat
*Description :  Adds support for calculating Cyclic Redundancy Check 
(CRC) to the Digest module.



I am packaging ruby-digest-crc as it is a dependency of gitlab 15.9.2.

---
Ravi Dwivedi


OpenPGP_0xE0E5BAFD3BBF70B3.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034072: Wireless interfaces trigger error messages about invalid WPA passphrases gets stuck during install

[Cyril Brulebois]

Control: retitle -1 Wireless interfaces trigger error messages about invalid 
WPA passphrases

Adjusting title since I suppose you spotted #1031643 and forgot to
change the title when filing this bug about something else.

Reto Schneider  (2023-04-08):
> Until in Bullseye and Bookworm Alpha 1, passing the arguments ...
> 
> /install.amd/vmlinuz auto=true priority=critical vga=off interface=auto
> initrd=/install.amd/initrd.gz --- console=ttyS0,115200n8
> 
> ... boots the installer and progresses on its own up to the point where it
> needs to ask about the location of the preseed file ("Download debconf
> preconfiguration file").
> 
> For Bookworm Alpha 2 and RC1 however, the installer, during the detection of
> network link on each interface, once testing the Wi-Fi ones, complains about
> the WPA passphrase being invalid:
> 
> [!]! Configure the network
> Invalid passphrase
> The WPA/WPA2 PSK passphrase was either too long (more than 64 characters) or
> too short (less than 8 characters).
> 
> I can either chose "Continue" (presents the same error message again) or back
> (which allows me to store the logs), but there seems to be no way of
> progressing with the installation.

Alpha 2 is the first release with official support for firmware packages,
which is likely the triggering bit here: they show up and are usable now.

I'm not familiar with the netcfg code enough to suggest anything at the
moment (e.g. something that would notice no passphrases have been
specified, meaning one should skip the interface or prompt for a
passphrase?), but I'll add another workaround in passing:

> Possible workarounds:
>  - Remove Wi-Fi cards from machine during installation
>  - Specify interface to be used (e.g. interface=enp2s0)

Disable firmware support:
 - https://www.debian.org/releases/bookworm/amd64/ch02s02.en.html


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1034038: Please push babel.sty v3.87 or later into the upcoming distribution

[Preuße]

On 07.04.2023 01:34, Al Ma wrote:

Hi,


Package: texlive-latex-base
Version: 2022.20230122-2
Severity: wishlist

Please push the changes in babel.dtx due to commit cd59ff0 (cf.
https://github.com/latex3/babel/commit/cd59ff0,
 changes in line
15797-15798) into Debian.  This amounts to babel v3.87 or later and
solves https://tex.stackexchange.com/questions/680690
 .  Ideally, the update
should have a chance to propagate to the upcoming stable before the
final freeze.



Updated packages containing just this specific hunk are on [1]. Let me
know if they solve your issue.

Hilmar

[1] https://freeshell.de/~hille42/tl_base/
--
sigfault

Bug#1034070: installation-reports: Successful netinstall on RTL8822CE wlan (with included non-free firmware)

[Kostas Papadakis]

Package: installation-reports
Severity: wishlist
Tags: d-i
X-Debbugs-Cc: karaka...@gmail.com

Boot method: USB
Image version: 
https://cdimage.debian.org/cdimage/bookworm_di_rc1/amd64/iso-cd/debian-bookworm-DI-rc1-amd64-netinst.iso
Date: 2023-04-05 19:00:00 UTC

Machine: Lenovo IdeaPad 3 15ALC6
Partitions: 
Filesystem  Type 1K-blocks Used Available Use% Mounted 
on
udevdevtmpfs   96101200   9610120   0% /dev
tmpfs   tmpfs  1930072 1636   1928436   1% /run
/dev/mapper/nvme0n1p2_crypt ext4 123266624  7324764 114667208   7% /
tmpfs   tmpfs  96503440   9650344   0% /dev/shm
tmpfs   tmpfs 51200  5120   0% /run/lock
/dev/nvme0n1p1  vfat52324811168512080   3% /boot/efi
/dev/mapper/nvme0n1p3_crypt ext4 205311976 23129960 182165632  12% /home
tmpfs   tmpfs  1930068   254148   1675920  14% 
/run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [E]
Partition hard drives:  [ ]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

Compared to the bullseye installer I had used in the past, I didn't
had to copy the non-free firmware drivers for my wlan to
work. Additionally the bookworm RC1 installer kept the wlan setup
stored after boot and I had internet access from the very first boot,
which wasn't the case with the old bullseye installer.

I had several other problems which were related to my decision to keep
the previous partitioning with encrypted root filesystem and no
separate boot partition, and another encrypted home partition with my
data (which I kept intact), which were solved by roughly following
this guide:
https://www.blakehartshorn.com/installing-debian-on-existing-encrypted-lvm/
and eventually copying encryption keys to initramfs in order to avoid
the multiple password prompts.

Maybe the part that existing partitions are encrypted and offering to
luksOpen them from within the installer, could be provided as an
option though the installer in the future. This isn't a request
specific to bookworm/RC1 of course.

The install was made with TPM disabled. This laptop has a TPM module
and by default is enabled. I hadn't tried if the installation works
with TPM enabled.

-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230401"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux kos 6.1.0-7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-1 
(2023-03-19) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Renoir/Cezanne Root Complex [1022:1630]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
Root Complex [1022:1630]
lspci -knn: 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] 
Renoir/Cezanne IOMMU [1022:1631]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
IOMMU [1022:1631]
lspci -knn: 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Renoir PCIe Dummy Host Bridge [1022:1632]
lspci -knn: 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Renoir PCIe Dummy Host Bridge [1022:1632]
lspci -knn: 00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 
Renoir/Cezanne PCIe GPP Bridge [1022:1634]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 
Renoir/Cezanne PCIe GPP Bridge [1022:1634]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Renoir PCIe Dummy Host Bridge [1022:1632]
lspci -knn: 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 
Renoir Internal PCIe GPP Bridge to Bus [1022:1635]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Internal 
PCIe GPP Bridge to Bus [1022:1635]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 
Renoir Internal PCIe GPP Bridge to Bus [1022:1635]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Internal 
PCIe GPP Bridge to Bus [1022:163

Bug#1034071: u-boot-menu: Does not show a menu due to 'prompt 0'

[Diederik de Haas]

Package: u-boot-menu
Version: 4.2.1
Severity: normal
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As the subject says, u-boot-menu doesn't show a (boot) menu as the
'prompt' setting has a hardcoded value of '0'. If you'd change that to
say '5' then you do see a menu from which you can choose.
But the next time you'd run 'u-boot-update' that value gets overwritten.

https://salsa.debian.org/debian/u-boot-menu/-/merge_requests/13 is my MR
to make the 'prompt' value configurable with a default value of '5'.

It would be great if this could still make it into Bookworm and I do
believe this is a targeted fix. I set 'Severity: normal', but a case can
be made for a higher severity as 'u-boot-menu' doesn't show a menu.
I'd be also fine with a default value of '0', so that the only change
would be to make 'prompt' configurable.

I'll also attach the patch of MR 13 as a patch file.

- -- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (990, 'testing-security'), (990, 'testing'), (500, 'unstable')
Architecture: arm64 (aarch64)

Kernel: Linux 6.1.0-7-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages u-boot-menu depends on:
ii  linux-base  4.9

u-boot-menu recommends no packages.

Versions of packages u-boot-menu suggests:
pn  flash-kernel  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZDCVcQAKCRDXblvOeH7b
buLOAP9yKZNz0+Vfk+Y186OcFVIpetwPWIr+XFEw8IVAFLs17QEA7OHU0vY4KWFs
1Wh7DR5LuMimmcbIQcKjxRz3Fdt/wQc=
=uIwT
-END PGP SIGNATURE-
>From 382c1e20b0809d5dd9dcba757e574b4bfbcca0dc Mon Sep 17 00:00:00 2001
From: Diederik de Haas 
Date: Thu, 6 Apr 2023 18:10:12 +0200
Subject: [PATCH] u-boot-update: Make 'prompt' configurable with default value
 of 5

The 'prompt' value was hard-coded to 0, which means the menu isn't
actually shown, thereby losing its function as a 'menu' list from which
the user can choose from.

So create an `U_BOOT_PROMPT` variable to make it configurable and set
the default value to 5, so the menu is actually shown and the user can
make a choice from the menu.
---
 debian/changelog | 6 ++
 default  | 1 +
 u-boot-update| 3 ++-
 3 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 5192c3a..cf371ca 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+u-boot-menu (4.2.2) UNRELEASED; urgency=medium
+
+  * u-boot-update: Make 'prompt' configurable with default value of 5
+
+ -- Diederik de Haas   Thu, 06 Apr 2023 18:08:55 +0200
+
 u-boot-menu (4.2.1) unstable; urgency=medium
 
   * Revert "add kalsrseed support" (Closes: #1025954)
diff --git a/default b/default
index 2e29c83..1d17be7 100644
--- a/default
+++ b/default
@@ -4,6 +4,7 @@
 
 #U_BOOT_ALTERNATIVES="default recovery"
 #U_BOOT_DEFAULT="l0"
+#U_BOOT_PROMPT="5"
 #U_BOOT_ENTRIES="all"
 #U_BOOT_MENU_LABEL="Debian GNU/Linux"
 #U_BOOT_PARAMETERS="ro quiet"
diff --git a/u-boot-update b/u-boot-update
index 90c4087..c726c9e 100755
--- a/u-boot-update
+++ b/u-boot-update
@@ -96,6 +96,7 @@ fi
 
 U_BOOT_ALTERNATIVES="${U_BOOT_ALTERNATIVES:-default recovery}"
 U_BOOT_DEFAULT="${U_BOOT_DEFAULT:-l0}"
+U_BOOT_PROMPT="${U_BOOT_PROMPT:-5}"
 U_BOOT_ENTRIES="${U_BOOT_ENTRIES:-all}"
 U_BOOT_TIMEOUT="${U_BOOT_TIMEOUT:-50}"
 U_BOOT_MENU_LABEL="${U_BOOT_MENU_LABEL:-${PRETTY_NAME:-Debian GNU/Linux 
kernel}}"
@@ -162,7 +163,7 @@ _CONFIG="\
 
 default ${U_BOOT_DEFAULT}
 menu title U-Boot menu
-prompt 0
+prompt ${U_BOOT_PROMPT}
 timeout ${U_BOOT_TIMEOUT}
 "
 
-- 
2.40.0

Bug#1034069: /var/log/boot~ is never created

[Bjarni Ingi Gislason]

Package: bootlogd
Version: 3.06-2
Severity: important

Dear Maintainer,

   * What led up to the situation?

/var/log/boot*  was not updated after 28th September 2021.

  File is used in /etc/init.d/bootlogd.

  The conditional code

if [ -f /var/log/boot ] && [ -f /var/log/boot~ ]
then
[ "$VERBOSE" = no ] || log_action_begin_msg "Moving boot log 
file"
# bootlogd writes to boot, making backup at boot~
cd /var/log && {
chgrp adm boot || :
savelog -q -p -c 5 boot &&
mv boot.0 boot  &&
mv boot~ boot.0
}
ES=$?
[ "$VERBOSE" = no ] || log_action_end_msg $ES
fi

is therefore never used.

-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.20-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 bootlogd depends on:
ii  libc6   2.36-8
ii  sysvinit-utils  3.06-2

bootlogd recommends no packages.

bootlogd suggests no packages.

-- Configuration Files:
/etc/init.d/bootlogd changed [not included]
/etc/init.d/stop-bootlogd [Errno 2] No such file or directory: 
'/etc/init.d/stop-bootlogd'
/etc/init.d/stop-bootlogd-single [Errno 2] No such file or directory: 
'/etc/init.d/stop-bootlogd-single'

-- no debconf information

Bug#1034068: ITP: rcsw -- A collection of reusable embedded C software modules in the style of C++ STL

[John Harwell]

Package: rcsw
Severity: wishlist

* Package name: rcsw
  Version : 1.2.1
  Upstream Author : John Harwell
* URL : https://github.com/jharwell/rcsw
* License : MIT
  Programming Lang: C
  Description : A collection of reusable embedded C software 
modules in the style of C++ STL


Reusable C SoftWare (RCSW) is a collection of modules which tries to be 
generic in the same way that the C++ STL is. It mainly targets embedded 
systems/robotics development in computationally constrained environments.


It has many data structures, a pub-sub system, 
multi-thread/multi-process handling and utilities, and simple I/O 
routines for bare-metal applications such as bootstraps.


This package is actively maintained, and I contribute to it as I have a 
need.

Bug#1034035: marked as done (linux-image-6.1.0-7-amd64: linux image installation fails dkms step if headers are absent)

[Diederik de Haas]

On Friday, 7 April 2023 23:15:03 CEST Debian Bug Tracking System wrote:
> > Comments:
> > 1. If the kernel installation requires the headers to function properly,
> > then they should probably be a package dependency.
> 
> As said above, the kernel does need the headers installed.

Correction: the kernel does *NOT* need the headers installed

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

Bug#1034062: netcfg prompts for hostname even though preseeded, preventing unattended installation

[Cyril Brulebois]

Hallo Oliver,

Oliver Freyermuth  (2023-04-07):
> With both the Bookworm alpha2 and rc1 netinstaller, I am prompted to
> confirm the preseeded hostname (also sent via DHCP), preventing
> unattended installation.  The very same preseed file did not show any
> such prompt neither in Buster nor Bullseye.
> 
> The prompt is pre-filled with the correct hostname (not the FQDN, just
> the hostname part), but of course this prevents unattended preseed
> installation.
> 
> Relevant logs follow, hostname and FQDN modified to examples.
> 
> Potentially relevant kernel commandline parameters:
> netcfg/disable_dhcp=false ethdetect/prompt_missing_firmware=false 
> hw-detect/load_firmware=false locale=en_US.UTF-8 hostname=laptop.example.com 
> domain=example.com

This is likely #1031643, try using the full netcfg/get_hostname name
instead of the hostname alias on the kernel command line?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#986207: snapshot.debian.org: "debian-archive/.../debian-security/" is missing "wheezy"

[Tianon Gravi]

On Wed, 31 Mar 2021 at 08:57, Tianon Gravi  wrote:
> It would appear that archive.debian.org hasn't been snapshotted since
> 2019-03-28 10:54:44, but it has changed since then.  The notable change
> that caused me to notice was that [0] seems to be missing wheezy, even
> though [1] does include it (folder timestamp is 2019-03-31 19:18).
>
> [0]: 
> https://snapshot.debian.org/archive/debian-archive/20190328T105444Z/debian-security/dists/
> [1]: http://archive.debian.org/debian-security/dists/
>
> Any chance we could turn the wheels a little and get a newer snapshot of
> archive.debian.org? O:)
>
> Thank you for maintaining such an excellent service! :)

This is relevant again with the recent move of "jessie" security
updates to archive.debian.org (2023-02-18 11:34). 😇🙇❤

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#1034067: PCManFM-Qt is not using "x-terminal-emulator" from Debian Alternatives System

[Julien ROBIN]

Package: pcmanfm-qt
Version: 1.2.1-1
Severity: minor
X-Debbugs-Cc: julien.robi...@free.fr

Hello,

After having removed "qterminal" and replaced it by "lxterminal" for some
reason (bad handling of line splits when resizing), PCManFM-Qt was still trying
to open "qterminal" when pressing F4 or "Open in terminal", giving a "Failed to
execute child process" error.

It turns out Edit > Preferences > Advanced is allowing to manually replace this
behavior, but would it be a good idea to use "x-terminal-emulator" by default?
This would avoid users the need to repair PCManFM-Qt configuration when using
anything else than "qterminal", based on which one is the default one, using
the "Debian Alternatives System".

For now this is what I've done and it seems to works (at least with lxterminal,
but it also works when going back to qterminal as x-terminal-emulator).

Hoping this idea may help,

Best regards,

Julien ROBIN


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

Kernel: Linux 6.1.0-7-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pcmanfm-qt depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.14.6-1
ii  desktop-file-utils0.26-1
ii  libc6 2.36-8
ii  libfm-qt121.2.1-1+b1
ii  libglib2.0-0  2.74.6-1
ii  libqt5core5a  5.15.8+dfsg-3
ii  libqt5dbus5   5.15.8+dfsg-3
ii  libqt5gui55.15.8+dfsg-3
ii  libqt5widgets55.15.8+dfsg-3
ii  libqt5x11extras5  5.15.8-2
ii  libstdc++612.2.0-14
ii  libxcb1   1.15-1
ii  lxqt-sudo 1.2.0-1

Versions of packages pcmanfm-qt recommends:
ii  eject   2.38.1-5+b1
ii  ffmpegthumbnailer   2.2.2+git20220218+dfsg-1+b1
ii  gvfs-backends   1.50.3-1
ii  gvfs-fuse   1.50.3-1
ii  lximage-qt  1.2.0-2
ii  lxqt-policykit  1.2.0-1
ii  lxqt-qtplugin   1.2.0-3+b2
ii  oxygen-icon-theme   5:5.103.0-1
ii  papirus-icon-theme  20230104-2
ii  pcmanfm-qt-l10n 1.2.1-1

Versions of packages pcmanfm-qt suggests:
pn  cdtool  

-- no debconf information

Bug#1034064: roundcube-core: Default index file /usr/share/roundcube/index.php is missing closing PHP tag (?>).

[Guilhem Moulin]

Control: tag -1 moreinfo unreproducible

On Fri, 07 Apr 2023 at 14:52:01 -0500, Jonathan Hutchins wrote:
> Loading default page (.../mail) displays PHP code inestead of login page 
> after upgrade from buster to bullseye.

index.php ends with the exact same line on buster (1.3.17+dfsg.1-1~deb10u2)
and bullseye (1.4.13+dfsg.1-1~deb11u1), and neither ends with a closing tag.
Moreover https://www.php.net/manual/en/language.basic-syntax.phptags.php
reads “If a file contains only PHP code, it is preferable to omit the
PHP closing tag at the end of the file.”

If appending a closing tag, without any other change, passes to the file
to interpreter instead of serving it as is, then I guess you have a
highly non-standard environment (and perhaps even insecure since the
config file might be exposed to the internet).  FWIW the autopkgtests
would choke if missing the closing the tag was an issue.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#1034066: Shortcut keys are ignored in start menu (and some others menus and circumstances)

[Julien ROBIN]

Package: lxqt-globalkeys
Version: 1.2.0-1
Severity: normal
X-Debbugs-Cc: julien.robi...@free.fr

Hello,

I noticed shortcut keys are dropped / not working when into the LXQT start menu
(or in some contextual menus like PCManFM-Qt menu bar and right click menu).

The problem also appears while the title bar of a window is held with a mouse
press, and moving for example.

This makes impossible to make screen capture of some things, but others
shortcuts like volume keys for example, are also affected in the same
circumstances.

By the way, Print screen key also has to be manually added using "lxqt-config-
globalkeyshortcuts", to link a screenshot program like "screengrab",
"xfce4-screenshooter", "scrot", "gnome-screenshot", "kde-spectacle" or any
other one after having manually installed one of them.

Hoping this may help,

Best regards,
Julien ROBIN


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

Kernel: Linux 6.1.0-7-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lxqt-globalkeys depends on:
ii  libc6   2.36-8
ii  libgcc-s1   12.2.0-14
ii  liblxqt11.2.0-5
ii  libqt5core5a5.15.8+dfsg-3
ii  libqt5dbus5 5.15.8+dfsg-3
ii  libqt5gui5  5.15.8+dfsg-3
ii  libqt5widgets5  5.15.8+dfsg-3
ii  libstdc++6  12.2.0-14
ii  libx11-62:1.8.4-2

Versions of packages lxqt-globalkeys recommends:
ii  lxqt-globalkeys-l10n  1.2.0-1
ii  lxqt-qtplugin 1.2.0-3+b2
ii  lxqt-session  1.2.0-3

Versions of packages lxqt-globalkeys suggests:
pn  lxqt | lxqt-core  

-- no debconf information

Bug#1034065: sasl-xoauth2: FTBFS: ModuleNotFoundError: No module named 'distutils.core'

[Andreas Beckmann]

Source: sasl-xoauth2
Version: 0.19-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

sasl-xoauth2/experimental FTBFS on all architectures:
https://buildd.debian.org/status/package.php?p=sasl-xoauth2&suite=experimental

...
   debian/rules execute_after_dh_auto_build
make[1]: Entering directory '/<>'
mkdir -p completions manpages
register-python-argcomplete --shell bash sasl-xoauth2-tool > 
completions/sasl-xoauth2-tool
argparse-manpage --pyfile obj-x86_64-linux-gnu/scripts/sasl-xoauth2-tool 
--object parser \
--author 'Tarick Bedeir' --author-email 'tar...@bedeir.com' 
--project-name sasl-xoauth2 \
--url https://github.com/tarickb/sasl-xoauth2 --output 
manpages/sasl-xoauth2-tool.1
Traceback (most recent call last):
  File "/usr/bin/argparse-manpage", line 5, in 
from build_manpages.cli import main
  File "/usr/lib/python3/dist-packages/build_manpages/cli/__init__.py", line 5, 
in 
from build_manpages.build_manpage import ManPageWriter, get_parser
  File "/usr/lib/python3/dist-packages/build_manpages/build_manpage.py", line 
10, in 
from distutils.core import Command
ModuleNotFoundError: No module named 'distutils.core'
make[1]: *** [debian/rules:11: execute_after_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary-arch] Error 2
...


Andreas

Bug#1034064: roundcube-core: Default index file /usr/share/roundcube/index.php is missing closing PHP tag (?>).

[Jonathan Hutchins]

Package: roundcube
Version: 1.4.13+dfsg.1-1~deb11u1
Severity: important

Dear Maintainer,

Loading default page (.../mail) displays PHP code inestead of login page after 
upgrade from buster to bullseye.
Reinstall restores the error.


-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-21-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages roundcube-core depends on:
ii  dbconfig-common   2.0.19
ii  debconf [debconf-2.0] 1.5.77
ii  dpkg  1.20.12
ii  libapache2-mod-php2:7.4+76
ii  libapache2-mod-php7.4 [libapache2-mo  7.4.33-1+deb11u3
ii  libjs-bootstrap4  4.5.2+dfsg1-8~deb11u1
ii  libjs-codemirror  5.59.2+~cs0.23.109-1
ii  libjs-jquery  3.5.1+dfsg+~3.5.5-7
ii  libjs-jquery-minicolors   2.2.6+dfsg-4
ii  libjs-jquery-ui   1.12.1+dfsg-8+deb11u1
ii  libjs-jstimezonedetect1.0.6-5
ii  libmagic1 1:5.39-3
ii  php   2:7.4+76
ii  php-auth-sasl 1.1.0-1
ii  php-common2:76
ii  php-intl  2:7.4+76
ii  php-mail-mime 1.10.10-1
ii  php-masterminds-html5 2.7.4+dfsg-2
ii  php-mbstring  2:7.4+76
ii  php-net-sieve 1.4.4-2
ii  php-net-smtp  1.9.0-1
ii  php-net-socket1.2.2-2
ii  php-pear  1:1.10.12+submodules+notgz+20210212-1
ii  php7.4 [php]  7.4.33-1+deb11u3
ii  php7.4-cli [php-cli]  7.4.33-1+deb11u3
ii  php7.4-intl [php-intl]7.4.33-1+deb11u3
ii  php7.4-json [php-json]7.4.33-1+deb11u3
ii  php7.4-mbstring [php-mbstring]7.4.33-1+deb11u3
ii  roundcube-mysql   1.4.13+dfsg.1-1~deb11u1
ii  ucf   3.0043

Versions of packages roundcube-core recommends:
ii  apache2 [httpd-cgi] 2.4.56-1~deb11u1
ii  php-fpm 2:7.4+76
ii  php-gd  2:7.4+76
ii  php-pspell  2:7.4+76
ii  php7.4-fpm [php-fpm]7.4.33-1+deb11u3
ii  php7.4-gd [php-gd]  7.4.33-1+deb11u3
ii  php7.4-pspell [php-pspell]  7.4.33-1+deb11u3

Versions of packages roundcube-core suggests:
pn  php-crypt-gpg 
pn  php-mkopinsky-zxcvbn-php  
pn  php-net-ldap3 
ii  roundcube-plugins 1.4.13+dfsg.1-1~deb11u1

Versions of packages roundcube depends on:
ii  dpkg  1.20.12

-- Configuration Files:
/etc/roundcube/apache.conf changed [not included]
/etc/roundcube/defaults.inc.php changed [not included]

-- debconf information:
* roundcube/database-type: mysql
* roundcube/hosts: localhost
  roundcube/internal/skip-preseed: false
  roundcube/remote/newhost:
* roundcube/db/app-user: roundcube@localhost
  roundcube/missing-db-package-error: abort
  roundcube/remote/host: localhost
* roundcube/mysql/admin-user: root
  roundcube/dbconfig-remove: true
  roundcube/upgrade-backup: true
* roundcube/passwords-do-not-match:
  roundcube/upgrade-error: abort
  roundcube/remote/port:
* roundcube/db/dbname: roundcube
  roundcube/purge: false
* roundcube/dbconfig-install: true
* roundcube/dbconfig-reinstall: true
* roundcube/reconfigure-webserver: apache2
  roundcube/install-error: abort
* roundcube/mysql/method: Unix socket
* roundcube/dbconfig-upgrade: true
  roundcube/mysql/authplugin: default
* roundcube/language: en_US
  roundcube/internal/reconfiguring: false
* roundcube/restart-webserver: true
  roundcube/remove-error: abort

Bug#1000209: Bug #1000209

[Paul Gevers]

Control: tags -1 pending

Hi,

On Sat, 4 Mar 2023 00:50:04 +0100 Couret Charles-Antoine 
 wrote:
update-rc.d (provided by #DEBHELPER#) which is called after "invoke-rc.d 
timidity stop" which stops the service.



It means systemd was not able to find the relevant service to stop at 
this moment in time. Making this update just before does the trick.


The patch is in attachment.


I have based my NMU on the attachment and uploaded the attached debdiff 
to DELAYED/2. Please let me know if I should delay or cancel it (or you 
can do that yourself).


Paul
diff -Nru timidity-2.14.0/debian/changelog timidity-2.14.0/debian/changelog
--- timidity-2.14.0/debian/changelog2018-06-27 22:06:49.0 +0200
+++ timidity-2.14.0/debian/changelog2023-04-07 20:22:10.0 +0200
@@ -1,3 +1,11 @@
+timidity (2.14.0-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Fix fails to install: invoke update-rc.d before invoke-rc.d
+(Closes: #1000209)
+
+ -- Paul Gevers   Fri, 07 Apr 2023 20:22:10 +0200
+
 timidity (2.14.0-8) unstable; urgency=medium
 
   * Fix FTBFS due to test requiring /etc/timidity/timidity.cfg
diff -Nru timidity-2.14.0/debian/timidity-daemon.postinst 
timidity-2.14.0/debian/timidity-daemon.postinst
--- timidity-2.14.0/debian/timidity-daemon.postinst 2018-06-27 
21:58:00.0 +0200
+++ timidity-2.14.0/debian/timidity-daemon.postinst 2023-04-07 
20:22:10.0 +0200
@@ -56,6 +56,7 @@
 # make sure we really stop, because packaging system doesn't
 # understand what we're trying to do with migration to timidity-daemon
 [ -f "/etc/init.d/timidity" ] && if which invoke-rc.d >/dev/null 2>&1; then
+  update-rc.d timidity defaults >/dev/null
   invoke-rc.d timidity stop
 else
   /etc/init.d/timidity stop


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034023: nmu: python-libzim_2.1.0+ds-1

[Paul Gevers]

Hi Bastian,

On 07-04-2023 21:01, Paul Gevers wrote:

Hi,

On 06-04-2023 18:47, Bastian Germann wrote:

Please rebuild python-libzim against the new zimlib.


But zimlib should not have been uploaded to unstable before the bookworm 
release. Please see bug 1027959 for discussion.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034063: unblock: ruby-maven-libs/3.3.9+ds-4

[Nilesh Patra]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: ruby-maven-l...@packages.debian.org
Control: affects -1 + src:ruby-maven-libs

Please unblock package ruby-maven-libs

[ Reason ]
Letting this through helps fix RC bug#1033912 which indicates
autopkgtest failure

[ Impact ]
Package with failing autopkgtest would go through bookworm

[ Tests ]
Autopkgtests are now passing with new release. Since the test is
relatively minimal, a superficial tag has been added.

[ Risks ]
No risk, this is a leaf package with minimal changes.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock ruby-maven-libs/3.3.9+ds-4

Bug#1034055: fwknop-apparmor-profile: AppArmor profile installed in systemd system service path

[Francois Marier]

On 2023-04-07 at 07:23:07, Laurent Bigonville (bi...@debian.org) wrote:
> It seems that you install the apparmor profile in the path for systemd system 
> service
> 
> The following change should be reverted:
> https://salsa.debian.org/debian/fwknop/-/commit/d3a5aaef39fedc1bb94e26921afbf63f79b31af7

Hm, that does look like a mistake. I don't remember what might have caused
me to make that change.

I guess the apparmor profile hasn't been in use for a while then. It seems
like it's too late in the release process to re-add it in bookworm.

Here's what I'm thinking of doing:

- move it to /usr/share/apparmor/extra-profiles/ (so it's not turned on by
  default) for bookworm
- move it back to /etc/apparmor.d/ after bookworm

Alternatively, I could also not change anything for bookworm since it's not
enabled as an AppArmor profile and it will be ignored as a systemd unit
file.

What do you think?

Francois

Bug#1034062: netcfg prompts for hostname even though preseeded, preventing unattended installation

[Oliver Freyermuth]

Package: netcfg
Version: 1.184

With both the Bookworm alpha2 and rc1 netinstaller, I am prompted to confirm 
the preseeded hostname (also sent via DHCP), preventing unattended installation.
The very same preseed file did not show any such prompt neither in Buster nor 
Bullseye.

The prompt is pre-filled with the correct hostname (not the FQDN, just the 
hostname part), but of course this prevents unattended preseed installation.

Relevant logs follow, hostname and FQDN modified to examples.

Potentially relevant kernel commandline parameters:
netcfg/disable_dhcp=false ethdetect/prompt_missing_firmware=false 
hw-detect/load_firmware=false locale=en_US.UTF-8 hostname=laptop.example.com 
domain=example.com

Potentially relevant part of preseed file:
d-i ethdetect/prompt_missing_firmware boolean false
d-i netcfg/choose_interface select auto
d-i netcfg/get_hostname string laptop.exmaple.com
d-i netcfg/get_domain string example.com
d-i netcfg/wireless_wep string
d-i hw-detect/load_firmware boolean true


Relevant part of installer syslog:
Apr  6 16:56:31 netcfg[1051]: DEBUG: State is now 1
Apr  6 16:56:31 netcfg[1051]: DEBUG: State is now 2
Apr  6 16:56:31 netcfg[1051]: DEBUG: State is now 5
Apr  6 16:56:31 netcfg[1051]: INFO: DHCP hostname: "laptop.example.com"
Apr  6 16:56:31 netcfg[1051]: DEBUG: laptop.example.com is a valid FQDN
Apr  6 16:56:31 netcfg[1051]: DEBUG: We have a real FQDN
Apr  6 16:56:31 netcfg[1051]: DEBUG: Preseeding domain from global: example.com
< at this point, the prompt for the hostname is shown, pre-filled with "laptop" 
>

Bug#1034061: ponyorm: please update the python 3.11 patch to include latest fix.

[Louis-Philippe Véronneau]

Package: src:ponyorm

Timo Röhling has updated the 3.11 PR with a new commit fixing a bug:

https://github.com/ponyorm/pony/pull/671/commits/3ac71610c0c304c3200a2c583e94d3e93fe3889e

This should probably be included in the version that's going to end up 
in Bookworm.


--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Bug#1034060: unblock: aide/0.18.2-1

[Marc Haber]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: a...@packages.debian.org
Control: affects -1 + src:aide

This is a pre-upload request for guidance regarding aide 0.18.2.
upstream released a new version that fixes a number of locking issues,
each of which possible a release-critical bug.

Debian does not have reports of these bugs since aide is seldomly used on
unstable/testing machines, but they have shown up during testing on
upstream side and are fixed now.

All downstream dependencies of aide are either in-package or
Recommends/Suggests, so breaking other packages unlikely.

I am attaching the upstream diff between 0.18.1 and 0.18.2, pulled apart
to the respective commits, 273 lines length including commit messages,
comments and the noise caused by the release.

The aide package has autopkgtests.

I reviewed the changes and approve them.

Please indicate whether you would be ok with going with the upstream
release via unstable to bookworm.

A debdiff of the actual package will be delivered for approval before
upload once you have indicated that you would consider approval. Thanks
in advance.

Greetings
Marc

Bug#1032553: magic-wormhole: FTBFS in testing: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13

[Martin Hostettler]

tags 1032553 + patch

thanks

On Wed, Apr 05, 2023 at 09:22:45AM +0200, Sascha Steinbiss wrote:
> Hi all,
> 
> [...]
> > This is mentioned in
> > https://github.com/magic-wormhole/magic-wormhole/issues/458 as likely
> > a "timing issue". Not sure if it's fixed upstream. >
> 
> Could it make sense to also patch the tests to include the delay that is
> mentioned in the GitHub issue comments?

I've tried adding a 2 second delay in the failing test and that yields a
package that builds reliably for me. I just rebuild the package with the
patch 250 times successfully in a row.

This patch works without any other commits backported.

--- magic-wormhole-0.12.0/src/wormhole/test/test_wormhole.py2021-02-05 
02:16:21.0 +
+++ magic-wormhole-0.12.0.fix/src/wormhole/test/test_wormhole.py
2023-04-07 14:44:26.792819150 +
@@ -6,6 +6,7 @@
 from twisted.internet import reactor
 from twisted.internet.defer import gatherResults, inlineCallbacks, returnValue
 from twisted.internet.error import ConnectionRefusedError
+from twisted.internet.task import deferLater
 from twisted.trial import unittest
 
 import mock
@@ -505,6 +506,7 @@
 yield self.assertFailure(w1.get_welcome(), WrongPasswordError)  # late
 
 yield self.assertFailure(w1.close(), WrongPasswordError)
+yield deferLater(reactor, 2, lambda: None)
 yield self.assertFailure(w2.close(), WrongPasswordError)
 
 @inlineCallbacks


I'm not a DD, so i can't upload any fixes, but i would really appreciate
if we can get this fixed before the auto removal strikes.

Regards,

 - Martin
--- magic-wormhole-0.12.0/src/wormhole/test/test_wormhole.py	2021-02-05 02:16:21.0 +
+++ magic-wormhole-0.12.0.fix/src/wormhole/test/test_wormhole.py	2023-04-07 14:44:26.792819150 +
@@ -6,6 +6,7 @@
 from twisted.internet import reactor
 from twisted.internet.defer import gatherResults, inlineCallbacks, returnValue
 from twisted.internet.error import ConnectionRefusedError
+from twisted.internet.task import deferLater
 from twisted.trial import unittest
 
 import mock
@@ -505,6 +506,7 @@
 yield self.assertFailure(w1.get_welcome(), WrongPasswordError)  # late
 
 yield self.assertFailure(w1.close(), WrongPasswordError)
+yield deferLater(reactor, 2, lambda: None)
 yield self.assertFailure(w2.close(), WrongPasswordError)
 
 @inlineCallbacks

Bug#1034059: zstd-jni-java: FTBFS during binary-arch build: Plugin org.apache.maven.plugins:maven-resources-plugin:3.1.0 or one of its dependencies could not be resolved

[Andreas Beckmann]

Source: zstd-jni-java
Version: 1.5.2-5+ds-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: found -1 1.5.4-2+ds-1

Hi,

zstd-jni-java FTBFS during a binary-arch build (as it is done on the
buildd network), while binary-indep and combined binary-arch and
binary-indep builds succeed. Reproducible in bookworm, sid and
experimental.

...
   dh_auto_build -a -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/zstd-jni-java-1.5.2-5\+ds 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/zstd-jni-java-1.5.2-5\+ds/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/zstd-jni-java-1.5.2-5\+ds/debian 
-Dmaven.repo.local=/build/zstd-jni-java-1.5.2-5\+ds/debian/maven-repo package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
deprecated in JDK 13 and will likely be removed in a future release.
[INFO] Scanning for projects...
[INFO] 
[INFO] -< com.github.luben:zstd-jni >--
[INFO] Building zstd-jni 1.5.2-5
[INFO] [ jar ]-
[WARNING] The POM for org.apache.maven.plugins:maven-resources-plugin:jar:3.1.0 
is missing, no dependency information available
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  0.093 s
[INFO] Finished at: 2023-04-07T17:09:36Z
[INFO] 
[ERROR] Plugin org.apache.maven.plugins:maven-resources-plugin:3.1.0 or one of 
its dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-resources-plugin:jar:3.1.0 has not been 
downloaded from it before. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/zstd-jni-java-1.5.2-5\+ds 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/zstd-jni-java-1.5.2-5\+ds/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/zstd-jni-java-1.5.2-5\+ds/debian 
-Dmaven.repo.local=/build/zstd-jni-java-1.5.2-5\+ds/debian/maven-repo package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:8: binary-arch] Error 25

Note that maven-resources-plugin 3.3.0 was uploaded in December,
i.e. after the last zstd-jni-java upload to sid in November.

maven-resources-plugin | 3.1.0-1   | stable   | source
maven-resources-plugin | 3.3.0-1   | testing  | source
maven-resources-plugin | 3.3.0-1   | unstable | source

The last zstd-jni-java upload to experimental in March does FTBFS on all 
buildds:
https://buildd.debian.org/status/package.php?p=zstd-jni-java&suite=experimental


Andreas


zstd-jni-java.bookworm.build.gz
Description: application/gzip

Bug#1033176: linux: Future Android/Waydroid support

[Djhg2000]

I've worked on Waydroid support in Mobian and tried to keep our wiki article
(https://wiki.mobian-project.org/doku.php?id=waydroid) updated with installation
instructions from source.

In my opinion there are two main considerations regarding the binder modules:
1. Waydroid really wants to use binderfs as a replacement for the now legacy
method of predefining binder interfaces. From what I understand this isn't
really within the control of Waydroid but rather what Android expects of the
underlying kernel, but predefining the right ones when loading the module works
for now. I would expect this latter part could change in the future without much
notice from upstream (upstream in this case would be AOSP).
2. Until Waydroid is packaged for Debian we probably can't be expected to make
specific accommodations for Waydroid, given it's a very niche use case. On the
other hand Waydroid is almost essential for some Mobian users. Since Mobian aims
to reintegrate into Debian it's a problem we'll have to address sooner or later.

Both of these considerations would be easily solved by packaging Waydroid in
Debian. With official Debian packaging it would be possible to keep changes in
sync as they happen, in this case updating the binder interface names when
required by new versions of Waydroid. With official Debian packaging it would
also be easily justifiable to include the binder module in the Debian kernel
tree. Debian packaging of Waydroid and its dependencies mostly exists upstream
but with some trivial errors preventing easy builds.

With that in mind, until Waydroid is in the Debian repos I see two somewhat
readily available options:
1. Drop the "binder" string from CONFIG_ANDROID_BINDER_DEVICES and leave the
default value (which then becomes "binder,hwbinder,vndbinder"). This way we're
reducing the delta between the default linux config and makes Waydroid work out
of the box (for now). Supposedly this wasn't needed for some users where
Waydroid had explicitly loaded the module with the right device names, but that
does not match my experience on amd64 where I had to add 'options
binder_linux devices="binder,hwbinder,vndbinder"' to
"/etc/modprobe.d/binder-linux.conf".
2. Essentially option 1 but with binderfs enabled. This would ensure
compatibility with newer versions of Waydroid (with newer AOSP), at least for
the foreseeable future.

Option 2 is better in my opinion but currently "CONFIG_ANDROID_BINDERFS=y"
breaks compilation of "binder_linux" (modpost says "put_ipc_ns" and
"init_ipc_ns" is undefined). I don't know how easy of a fix this would be and I
would be more comfortable with having the modular build patch upstreamed to
ensure this is widely tested.

Ideally there would be a third option if the kernel could drop the legacy
device names entirely and only allow creation of devices through binderfs. In
that case I wouldn't see any reason to have this compiled as a module at all,
since there would be no devices to exploit security holes in without first
creating them through binderfs (and if you can create them without going through
Waydroid you probably have access to other exploitable code as well).

For reference, Mobian has both the current legacy device names in
CONFIG_ANDROID_BINDER_DEVICES and binderfs enabled.

Finally, it would be great if we could find someone who can take the role of a
Waydroid package maintainer. Updating the Mobian wiki on and off has proved to
me that I don't have the time to properly maintain the package, but I can assist
someone else in packaging it to the best of my abilities. I don't have enough
experience with Debian packaging to clean up the existing package without
assistance either but I think I have a decently good grasp of the Waydroid
internals at this point.

Bug#1034037: unblock: qt6-tools/6.4.2-1

[Paul Gevers]

Hi Patrick,

On 07-04-2023 00:42, Patrick Franz wrote:

We'd like to request an unblock such that qt6-tools 6.4.2-1 can migrate to 
testing
once llvm-toolchain-15 has migrated.


That's fine, but I don't expect llvm-toolchain-15 to migrate before the 
bookworm release, and I don't think this cosmetic issue warrants the tpu 
dance. So I think we'll just have 6.4.2~rc1-2 as the bookworm version.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034050: fonts-creep2: generated font is TrueType, not OpenType

[Nathan Willis]

On Fri, Apr 7, 2023 at 4:39 PM Fabian Greffrath  wrote:

>
> I'd say we make the distinction by container format. Though, I agree
> that this distinction is still pretty arbitrary.
>

But the container formats are the same, though: SFNT.

You can rename a foo.ttf file to foo.otf and it behaves exactly the same.
It's literally just a different file extension.

The only distinctions possible are down inside the optional contents, like
an OpenType font *might* include some tables (like CFF) that originated in
the Type-1 spec and not in Apple's version of the original TrueType. But
even in that case, it's table-level, not container-level. So if you renamed
a CFF-including bar.otf  to bar.ttf, an old enough Mac might ignore the CFF
table, but would see the rest fine.

20.odd years ago, proprietary systems had to stick to their conventions
because the big vendors (Apple, MS, and Adobe) didn't support
_each_other's_ contributions in their own various applications, but that's
changed since then and, way more importantly, the free-software stack today
is one pipeline that supports them all.

The MS spec even references this —
https://learn.microsoft.com/en-us/typography/opentype/spec/otff#filenames —
it's just Newton's First Law that keeps the old-timey ways stuck in
place

For the record, I do advocate for user-facing font managers to do better
here (on presenting the important internal distinctions, not the filename
extension), particularly because it would clear up more serious confusion
between the various emoji formats and in variable fonts, but it's
identifiably archaic stuff at the system and package level, which users and
apps shouldn't ever need to think about.

Hashtag cloudyelling,
Nate
-- 
nathan.p.willis
nwil...@glyphography.com 

Bug#1031511: RFS: reiserfsprogs/1:3.6.27-5 -- User-level tools for ReiserFS filesystems

[Felix Zielcke]

Am Freitag, dem 07.04.2023 um 16:41 +0200 schrieb Bastian Germann:
> Thanks for the update.

Thanks very much for uploading!
Patience pays off.

Bug#1034039: bullseye-pu: package libpod/3.0.1+dfsg1-3+deb11u1

[Reinhard Tartler]

Argh, my bad, I'll upload a new version later today

Thanks for spotting

-rt

On April 7, 2023 4:41:41 AM EST, "Adam D. Barratt"  
wrote:
>On Thu, 2023-04-06 at 19:46 -0400, Reinhard Tartler wrote:
>> This code change picks up code changes in golang-github-containers-
>> psgo
>> and golang-github-containers-storage to fix CVE-2022-1227. This is
>> reported
>> as 1020907. This addresses a priviledge escalation issue when using
>> 'podman top'. Upstream has more information in this issue in
>> https://bugzilla.redhat.com/show_bug.cgi?id=2070368
>> 
>
>I see this has already been uploaded; unfortunately:
>
>-,golang-github-containers-psgo-dev
>-,golang-github-containers-storage-dev (>= 1.24.6)
>+,golang-github-containers-psgo-dev (>= 1.5.2-1+deb11u1)
>+,golang-github-containers-storage-dev (>= 1.24.6+dfsg1-1+deb11u1)
>
>The updated golang-github-containers-storage-dev version there isn't
>actually sufficient to ensure that the fixed version is picked up - you
>want 1.24.*8*+dfsg1-1+deb11u1.
>
>At this point, either I can reject the current upload, and you can then
>re-upload a fixed +deb11u1 or (possibly easier all around) you can
>upload +deb11u2 as an incremental change on top of +deb11u1 which
>simply fixes the dependency version.
>
>Regards,
>
>Adam
>
>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#1034050: fonts-creep2: generated font is TrueType, not OpenType

[Fabian Greffrath]

Am Freitag, dem 07.04.2023 um 15:14 +0100 schrieb
nwil...@glyphography.com:
> based on the outline format contained within (quadratic vs cubic 
> Beziers), then filename extension alone is not adequate.
> 
> Similarly, if the intent is to make some sort of distinction based on
> the contents of the tables (e.g., GSUB and GPOS), then the filename 
> extension still isn't adequate, because .ttf files can and do include
> those tables (see Noto and many many others).

I'd say we make the distinction by container format. Though, I agree
that this distinction is still pretty arbitrary.

 - Fabian



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

Bug#1005318: Any update for this request?

[Ross Vandegrift]

On Fri, Apr 07, 2023 at 01:26:48AM +, Winnie Yue wrote:
> Could you please upgrade cloud-init to the latest release 23.1.1? Your
> help will be greatly appreciated. Thanks.

We are currently in the freeze period for the bookworm release, so this
won't happen until after the release is complete.

Ross

Bug#1034058: New upstream release

[Michael Deegan]

Package: python3-google-auth-oauthlib
Version: 0.4.2-1
Severity: normal

The packaged version is now about a dozen releases behind...

-- System Information:
Debian Release: 12.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'oldstable-updates'), (500, 'oldstable-debug'), (500, 'stable'), (500, 
'oldstable'), (490, 'testing'), (400, 'unstable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-google-auth-oauthlib depends on:
ii  python33.11.2-1
ii  python3-google-auth1.5.1-3
ii  python3-requests-oauthlib  1.0.0-1.1

python3-google-auth-oauthlib recommends no packages.

python3-google-auth-oauthlib suggests no packages.

-- no debconf information

-MD

-- 
-
Michael Deegan   Hugaholic  https://www.deegan.id.au/
  Jung, zr jbeel?  --

Bug#993048: additional request on this issue

[crichmon]

Aside from the init script updates to create the PID the directory, I’ll posit 
that

the config files also needs to have the pid_file directive removed or commented 
out.

/etc/mosquitto/mosquitto.conf

# pid_file /run/mosquitto/mosquitto.pid

The reason is that the start-stop-daemon used to start the daemon runs as root 
and creates

it’s own PID file based on the init code. When the mosquitto daemon starts, it 
does a setuid to

mosquitto, and if the pid_file directive is enabled with the same pid filename 
as the init script,

the mosquitto daemon will fail over-writing the existing pid file owned by root.

crichmon@testing:~$ ls -la /run/mosquitto/

total 4

drwxr-xr-x 2 root root 60 Apr 5 14:06 .

drwxr-xr-x 18 root root 680 Apr 6 06:40 ..

-rw-r--r-- 1 root root 5 Apr 5 14:06 mosquitto.pid

Thx, Chris

Bug#1034057: [RFP]: rebol -- Relative Expression Based Object Language

[David Oliva]

Package: wnpp
Severity: [wishlist]

Rebol was initially designed by Carl Sassenrath in 1997 as a closed source.
Its 3rd version was  open sourced in 2012, but abandoned by Carl just after
a few years. I am still maintaining sources in a separate fork:
https://github.com/Oldes/Rebol3

As I am not familiar with Debian packaging, I am trying to find some help
this way.
The main issue probably is that Rebol sources are partially generated using
Rebol itself. I can provide a pre-generated version for stage0.

Other links:
[1] http://rebol.com/
[2] https://en.wikipedia.org/wiki/Rebol
[3] https://github.com/rebol/rebol (original source files)

Thanks for any response,
Oldes

Bug#1034056: x11vnc: clipboard to server not working

[Stefan Schmohl]

Package: x11vnc
Version: 0.9.16-9
Severity: normal
X-Debbugs-Cc: x...@scntt.de

Dear Maintainer,

   * What led up to the situation?
1. Copy plain text, range x20 - x79, on vnc client side with STRG+INS.
 Tested with several versions of xthightvncviewer, UltraVNC ( Windows ).
2. Paste with SHIFT+INS on server side.
 Native / KVM.
 Debian 11 / 12.
 Crontab '@reboot x11vnc -auth guess -usepw -shared -forever -loop'.
 LXDE / XFCE.
 With / without clipboard manager.
 Into terminal / mousepad / firefox.
3. In the other direction, server to client, always works as expected.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Effective : Debian 10.
Ineffective : Any tested combination of the factors listed above.

   * What was the outcome of this action?
No insertion or
 insertion of the last clipboard content generated on the server itself.

   * What outcome did you expect instead?
Insertion of the clipboard content generated on the client.

-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 x11vnc depends on:
ii  libavahi-client3  0.8-9
ii  libavahi-common3  0.8-9
ii  libc6 2.36-8
ii  libcrypt1 1:4.4.33-2
ii  libssl3   3.0.8-1
ii  libvncclient1 0.9.14+dfsg-1
ii  libvncserver1 0.9.14+dfsg-1
ii  libx11-6  2:1.8.4-2
ii  libxdamage1   1:1.1.6-1
ii  libxext6  2:1.3.4-1+b1
ii  libxfixes31:6.0.0-2
ii  libxi62:1.8-1+b1
ii  libxinerama1  2:1.1.4-3
ii  libxrandr22:1.5.2-2+b1
ii  libxtst6  2:1.2.3-1.1
ii  openssl   3.0.8-1
ii  tk8.6.13

Versions of packages x11vnc recommends:
ii  x11-utils  7.7+5

x11vnc suggests no packages.

-- no debconf information

Bug#1034055: fwknop-apparmor-profile: AppArmor profile installed in systemd system service path

[Laurent Bigonville]

Package: fwknop-apparmor-profile
Version: 2.6.10-13
Severity: serious

Hello

It seems that you install the apparmor profile in the path for systemd system 
service

The following change should be reverted:
https://salsa.debian.org/debian/fwknop/-/commit/d3a5aaef39fedc1bb94e26921afbf63f79b31af7

Kind regards,
Laurent Bigonville

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fwknop-apparmor-profile depends on:
pn  fwknop-server  

fwknop-apparmor-profile recommends no packages.

fwknop-apparmor-profile suggests no packages.

Bug#1034050: fonts-creep2: generated font is TrueType, not OpenType

[nwillis]

Interesting dilemma 

On 2023-04-07 14:02, Agathe Porte wrote:

Package: fonts-creep2
Version: 0.0~git20210325.69dc0de+ds-4
Severity: minor
X-Debbugs-Cc: deb...@microjoe.org

Dear Maintainer (currently me, self-reporting for tracking),

The generated font is a TrueType font, not an OpenType font. This does
not impact the useability of the package to my knowledge, but would be


On the contrary, all TrueType fonts are also OpenType fonts. OpenType is 
a superset of TrueType, which is older.


That is clearly a misconception that the font industry has been battling 
unsuccessfully, but if the intent is to make some sort of distinction 
based on the outline format contained within (quadratic vs cubic 
Beziers), then filename extension alone is not adequate.


Similarly, if the intent is to make some sort of distinction based on 
the contents of the tables (e.g., GSUB and GPOS), then the filename 
extension still isn't adequate, because .ttf files can and do include 
those tables (see Noto and many many others).



nice to be fixed. This bug is reported by Lintian under the tag
`truetype-font-wrong-filename`.


Well, if that's so, then this indicates that Lintian is likely overdue 
for a refresh on how it determines these things. That might be a big 
undertaking; I don't know at the moment.


However, with this particular font:


The problem is that the font is located in /usr/share/fonts/opentype
instead of /usr/share/fonts/truetype, and that its name is creep2.otb
instead of creep2.ttf.


The .otb extension (as well as the .bdf in the package) indicates that 
this is a bitmap font re-wrapped in an OpenType table structure (see 
https://github.com/fonttools/fonttools/issues/684 for the history, and 
code at https://github.com/freedesktop/fonttosfnt or possibly 
https://github.com/ctrlcctrlv/bitmapfont2otb for the internal details); 
that definitely makes it an OpenType font and not a TrueType font, 
because the older TrueType spec did not allow that sort of skullduggery: 
it required vector outlines.


Not all proprietary apps and platforms recognize this usage nor the 
".otb" extension itself, but HarfBuzz / FreeType / Pango do.




Proposed solution is to rename the directory and the font itself to
match the TTF filetype.


Just doing a rename of the binary file could trigger accidental breakage 
for users on apps/stacks who aren't running HarfBuzz / FreeType etc (as 
above) via the standard, modern stack. That would not seem to be a 
beneficial change.


Long term, the underlying fix is that Lintian's font-detection likely 
needs a scrubbing by somebody with a lot more free time at hand than me 
(although billionaires who wish to fund this should still reach out...).


*Long* long term, the FHS and so on likely really need to drop the 
*/truetype/ */opentype/ directory distinction, since it's not doing 
anything useful. It's a bit like saying there should be separate /jpg/ 
and /jpeg/ directories and older images should only be put in one of 
them


I know this TTF/OTF confusion is widespread, but I maintain that fixing 
it is still possible

Nate

Bug#1034054: ../../src/xcb_io.c:626: _XAllocID Assertion `ret != inval_id' failed

[Marco d'Itri]

Package: fvwm
Version: 1:2.7.0-1
Severity: important

Since a few days/weeks fvwm has started crashing frequently with this 
"ret != inval_id" assertion.

(gdb) where
#0  __pthread_kill_implementation
(threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0)
at ./nptl/pthread_kill.c:44
#1  0x7fab8213ad2f in __pthread_kill_internal
(signo=6, threadid=) at ./nptl/pthread_kill.c:78
#2  0x7fab820ebef2 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/posix/raise.c:26
#3  0x7fab820d6472 in __GI_abort () at ./stdlib/abort.c:79
#4  0x7fab820d6395 in __assert_fail_base
(fmt=0x7fab8224aa70 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", 
assertion=assertion@entry=0x7fab8313db2a "ret != inval_id", 
file=file@entry=0x7fab8313da9b "../../src/xcb_io.c", line=line@entry=626, 
function=function@entry=0x7fab8313def0 <__PRETTY_FUNCTION__.2> "_XAllocID") at 
./assert/assert.c:92
#5  0x7fab820e4df2 in __GI___assert_fail
(assertion=assertion@entry=0x7fab8313db2a "ret != inval_id", 
file=file@entry=0x7fab8313da9b "../../src/xcb_io.c", line=line@entry=626, 
function=function@entry=0x7fab8313def0 <__PRETTY_FUNCTION__.2> "_XAllocID") at 
./assert/assert.c:101
#6  0x7fab830ca443 in _XAllocID (dpy=)
at ../../src/xcb_io.c:626
#7  0x7fab82f9f558 in XRenderCreatePicture
(dpy=dpy@entry=0x556a840d48b0, drawable=drawable@entry=35652809, 
format=0x556a840ecb48, valuemask=valuemask@entry=1, 
attributes=attributes@entry=0x7fff7e7491f0) at ../../src/Picture.c:90
#8  0x556a83873692 in FRenderRender
--Type  for more, q to quit, c to continue without paging--c
(dpy=dpy@entry=0x556a840d48b0, win=win@entry=35652813, 
pixmap=pixmap@entry=35652809, mask=mask@entry=0, alpha=alpha@entry=35652810, 
depth=depth@entry=24, added_alpha_percent=100, tint=0, tint_percent=0, 
d=35652813, gc=0x556a840ef970, alpha_gc=0x556a840efc30, src_x=, 
src_y=, src_w=48, src_h=48, dest_x=2, dest_y=2, dest_w=48, 
dest_h=48, do_repeat=0)
at ./libs/FRender.c:437
#9  0x556a8386938b in PGraphicsRenderPixmaps
(dpy=0x556a840d48b0, win=35652813, pixmap=35652809, mask=0, alpha=35652810, 
depth=24, fra=0x7fff7e7494e0, d=35652813, gc=0x556a840ef970, 
mono_gc=0x556a840efb80, alpha_gc=0x556a840efc30, src_x=0, src_y=0, src_w=48, 
src_h=48, dest_x=2, dest_y=2, dest_w=48, dest_h=48, do_repeat=0) at 
./libs/PictureGraphics.c:1012
#10 0x556a8381b73e in DrawIconPixmapWindow
(fw=fw@entry=0x556a841e8510, reset_bg=reset_bg@entry=0, 
pev=pev@entry=0x7fff7e7495e0, Shadow=Shadow@entry=0x556a840ef760, 
Relief=Relief@entry=0x556a840ec7a0, cs=cs@entry=-1) at ./fvwm/icons.c:1192
#11 0x556a8381ddcd in DrawIconWindow
(fw=fw@entry=0x556a841e8510, draw_title=draw_title@entry=1, 
draw_pixmap=, 
draw_pixmap@entry=1, focus_change=focus_change@entry=0, 
reset_bg=reset_bg@entry=0, pev=pev@entry=0x7fff7e7496f0) at ./fvwm/icons.c:1502
#12 0x556a837fedba in HandleExpose (ea=)
at ./fvwm/events.c:2361
#13 0x556a838024eb in dispatch_event (e=0x556a841eb058)
at ./fvwm/events.c:4160
#14 0x556a8380266c in _pred_weed_handle_expose
(display=, event=, arg=)
at ./fvwm/events.c:266
#15 0x556a83876189 in _fev_pred_weed_if
(display=, event=0x556a841eb058, arg=0x7fff7e749ac0 
"P&\200\203jU") at ./libs/FEvent.c:176
#16 0x556a8387620f in _fev_pred_check_peek
(display=, event=0x556a841eb058, arg=0x7fff7e7499d0 
"@a\207\203jU") at ./libs/FEvent.c:144
#17 0x7fab830a59da in XCheckIfEvent
(dpy=0x556a840d48b0, event=event@entry=0x7fff7e749910, 
predicate=predicate@entry=0x556a838761f0 <_fev_pred_check_peek>, 
arg=arg@entry=0x7fff7e7499d0 "@a\207\203jU") at ../../src/ChkIfEv.c:63
#18 0x556a83876b62 in FCheckPeekIfEvent
(display=, event_return=event_return@entry=0x7fff7e749b00, 
predicate=predicate@entry=0x556a83876140 <_fev_pred_weed_if>, 
arg=arg@entry=0x7fff7e749ac0 "P&\200\203jU") at ./libs/FEvent.c:590
#19 0x556a83876cb7 in FWeedIfEvents
(display=, 
weed_predicate=weed_predicate@entry=0x556a83802650 <_pred_weed_handle_expose>, 
arg=arg@entry=0x0) at ./libs/FEvent.c:527
#20 0x556a8380358a in handle_all_expose () at ./fvwm/events.c:4545
#21 0x556a83835581 in __raise_or_lower_window
(t=, mode=, 
allow_recursion=allow_recursion@entry=0, is_new_window=is_new_window@entry=1, 
is_client_request=is_client_request@entry=0) at ./fvwm/stack.c:1141
#22 0x556a83835e32 in raise_or_lower_window
(is_client_request=0, is_new_window=1, allow_recursion=0, mode=, t=0x556a841eb590) at ./fvwm/stack.c:1158
#23 position_new_window_in_stack_ring
(t=t@entry=0x556a841eb590, do_lower=) at ./fvwm/stack.c:1701
#24 0x556a83819b69 in AddWindow
(ret_initial_map_command=ret_initial_map_command@entry=0x7fff7e74a668, 
exc=, ReuseWin=ReuseWin@entry=0x0, 
win_opts=win_opts@entry=0x7fff7e74a730) at ./fvwm/add_window.c:2662
#25 0x556a838000be in HandleMapRequestKeepRaised
(ea=ea@entry=0x7fff7e74a708, KeepRaised=KeepRaised@entry=0, 
ReuseWin=ReuseWin@entry=0x0, win_opts=win_o

Bug#1034053: segfaulted on quit

[Marco d'Itri]

Package: mutt
Version: 2.2.9-1+b1
Severity: important

This happened while/after saving a mailbox on quit.
Apparently nothing was corrupted.

Also, why is the debugging info provided by debuginfod incomplete?

#0  rfc822_free_address (p=0x55a34941f100) at ../../rfc822.c:135
Download failed: Argomento non valido.  Continuing without source file 
./debian/build/../../rfc822.c.
135 ../../rfc822.c: File o directory non esistente.
(gdb) where
#0  rfc822_free_address (p=0x55a34941f100) at ../../rfc822.c:135
#1  0x55a347f0116c in mutt_free_envelope (p=0x55a34941f0e0)
at ../../muttlib.c:875
#2  0x55a347f015a7 in mutt_free_body (p=0x55a349302448)
at ../../muttlib.c:208
#3  0x55a347f015bc in mutt_free_body (p=0x55a3493022d8)
at ../../muttlib.c:211
#4  0x55a347f01376 in mutt_free_header (h=0x55a3493203e0)
at ../../muttlib.c:382
#5  0x55a347ec9dd1 in mx_fastclose_mailbox (ctx=ctx@entry=0x55a349117280)
at ../../mx.c:736
#6  0x55a347eca88b in mx_close_mailbox (ctx=0x55a349117280, 
index_hint=index_hint@entry=0x7ffc084da3f4) at ../../mx.c:1014
#7  0x55a347ea04f6 in mutt_index_menu () at ../../curs_main.c:1107
#8  0x55a347e7a107 in main (argc=1, argv=0x7ffc084db688, 
environ=) at ../../main.c:1400
(gdb) 
#0  rfc822_free_address (p=0x55a34941f100) at ../../rfc822.c:135
#1  0x55a347f0116c in mutt_free_envelope (p=0x55a34941f0e0)
at ../../muttlib.c:875
#2  0x55a347f015a7 in mutt_free_body (p=0x55a349302448)
at ../../muttlib.c:208
#3  0x55a347f015bc in mutt_free_body (p=0x55a3493022d8)
at ../../muttlib.c:211
#4  0x55a347f01376 in mutt_free_header (h=0x55a3493203e0)
at ../../muttlib.c:382
#5  0x55a347ec9dd1 in mx_fastclose_mailbox (ctx=ctx@entry=0x55a349117280)
at ../../mx.c:736
#6  0x55a347eca88b in mx_close_mailbox (ctx=0x55a349117280, 
index_hint=index_hint@entry=0x7ffc084da3f4) at ../../mx.c:1014
#7  0x55a347ea04f6 in mutt_index_menu () at ../../curs_main.c:1107
#8  0x55a347e7a107 in main (argc=1, argv=0x7ffc084db688, 
environ=) at ../../main.c:1400
(gdb) x 0x55a34941f100
0x55a34941f100: 0x616e696d
(gdb) x/s 0x55a34941f100
0x55a34941f100: "minap-tech"



-- Package-specific info:
Mutt 2.2.9 (2022-11-12)
Copyright (C) 1996-2022 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 6.1.0-7-amd64 (x86_64)
ncurses: ncurses 6.4.20221231 (compiled with 6.4)
libidn2: 2.3.3 (compiled with 2.3.3)
hcache backend: tokyocabinet 1.4.48

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 12.2.0-14' 
--with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-12 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin 
--enable-default-pie --with-system-zlib --enable-libphobos-checking=release 
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch 
--disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-12-bTRWOB/gcc-12-12.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-bTRWOB/gcc-12-12.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.0 (Debian 12.2.0-14) 

Configure options: --build=x86_64-linux-gnu --prefix=/usr 
'--includedir=${prefix}/include' '--mandir=${prefix}/share/man' 
'--infodir=${prefix}/share/info' --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
'--libdir=${prefix}/lib/x86_64-linux-gnu' --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking 
--with-mailpath=/var/mail --enable-compressed --enable-debug --enable-fcntl 
--enable-hcache --enable-gpgme --enable-imap --enable-smtp --enable-pop 
--enable-sidebar --enable-dotlock --disable-fmemopen --with-curses 
--with-gnutls --with-gss --with-idn2 --with-mixmaster --with-gsasl 
--without-gdbm --without-bdb --without-qdbm --with-tokyocabinet 
build_alias=x86_64-linux-gnu 'CFLAGS=-g -O2 
-ffile-prefix-map=/build/mutt-Fsss7h/mutt-2.2.9=. -fsta

Bug#1034052: winetricks: winetrick searches for 32 bit wine as wine32, not wine

[Thomas Dorner]

Package: winetricks
Version: 20230212-2
Severity: normal
X-Debbugs-Cc: debian-b...@th-dorner.de

Dear Maintainer,

I have the following wine multiarch installation in Sid:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version  Architecture Description
+++----==
ii  wine 8.0~repack-4 all  Windows API implementation - 
standard suite
ii  wine32:i386  8.0~repack-4 i386 Windows API implementation - 
32-bit binary loader
ii  wine64   8.0~repack-4 amd64Windows API implementation - 
64-bit binary loader
ii  winetricks   20230212-2   all  simple tool to work around 
common problems in Wine

While setting up a new Wine environment winetricks aborted with the
following error:


--
Using winetricks 20230212 - sha256sum: 
14afe10e8858e47f95fc6f02015003a6ffd8cd438249b25b85e1078e8e326949 with wine-8.0 
(Debian 8.0~repack-4) and WINEARCH=win64
Executing w_do_call vcrun2019
--
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 
32-bit versions of packages. If you encounter problems, please retest in a 
clean 32-bit WINEPREFIX before reporting a bug.
--
Executing load_vcrun2019 
Using native,builtin override for following DLLs: api-ms-win-crt-private-l1-1-0 
api-ms-win-crt-conio-l1-1-0 api-ms-win-crt-heap-l1-1-0 
api-ms-win-crt-locale-l1-1-0 api-ms-win-crt-math-l1-1-0 
api-ms-win-crt-runtime-l1-1-0 api-ms-win-crt-stdio-l1-1-0 
api-ms-win-crt-time-l1-1-0 atl140 concrt140 msvcp140 msvcp140_1 msvcp140_2 
msvcp140_atomic_wait msvcp140_codecvt_ids vcamp140 vccorlib140 vcomp140 
vcruntime140
Executing wine C:\windows\syswow64\regedit.exe C:\windows\Temp\override-dll.reg
it looks like wine32 is missing, you should install it.
multiarch needs to be enabled first.  as root, please
execute "dpkg --add-architecture i386 && apt-get update &&
apt-get install wine32:i386"
wine: failed to open "C:\\windows\\syswow64\\regedit.exe": c135
--
egedit.exe C:\windows\Temp\override-dll.reg returned status 53. Aborting.
--


After simply creating a hard-link between /usr/lib/wine/wine and
/usr/lib/wine/wine32 it worked.  I guess this is either a bug in the
winetricks or the wine (32 bit) package, at least it looks like
something not consistent.  The fix should be easy in each of them.  (I
did not try a soft-link, but that probably works as well.)

Best regards, Thomas

PS: Classified as "normal" as it has a very easy work-around.


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

Kernel: Linux 6.1.0-7-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages winetricks depends on:
ii  binutils 2.40-2
ii  curl 7.88.1-8
ii  wget 1.21.3-1+b2
ii  wine [wine]  8.0~repack-4

Versions of packages winetricks recommends:
ii  cabextract   1.9-3
ii  fuseiso  20070708-3.2+b1
ii  p7zip-full   16.02+dfsg-8
ii  pkexec   122-3
ii  policykit-1  122-3
ii  sudo 1.9.13p3-1
ii  unzip6.0-28
ii  x11-utils7.7+5
ii  xdg-utils1.1.3-4.1
ii  xz-utils 5.4.1-0.2
ii  zenity   3.44.0-1

Versions of packages winetricks suggests:
ii  tor0.4.7.13-1
ii  unrar  1:6.2.6-1

-- no debconf information

Bug#1034051: ITP: ripcalc -- simple network calculation and lookup tool

[ed neville]

Package: wnpp
Severity: wishlist
Owner: ed neville 
X-Debbugs-Cc: debian-de...@lists.debian.org, ed-deb...@s5h.net

* Package name: ripcalc
  Version : 0.1.6
  Upstream Author : Ed Neville 
* URL : https://www.usenix.org.uk/content/ripcalc.html
* License : GPL
  Programming Lang: (Rust)
  Description : simple network calculation and lookup tool

Calculate or lookup network addresses, then print results in a variety 
of formats.

Various datacenter audit/CMDB tools store reports in CSV, which can then 
be used as a source to lookup from. Ripcalc allows the end user to 
specify which parts of the CSV to include in output.

This will be maintained in the Debian Rust team.

Bug#1034050: fonts-creep2: generated font is TrueType, not OpenType

[Agathe Porte]

Package: fonts-creep2
Version: 0.0~git20210325.69dc0de+ds-4
Severity: minor
X-Debbugs-Cc: deb...@microjoe.org

Dear Maintainer (currently me, self-reporting for tracking),

The generated font is a TrueType font, not an OpenType font. This does
not impact the useability of the package to my knowledge, but would be
nice to be fixed. This bug is reported by Lintian under the tag
`truetype-font-wrong-filename`.

The problem is that the font is located in /usr/share/fonts/opentype
instead of /usr/share/fonts/truetype, and that its name is creep2.otb
instead of creep2.ttf.

Proposed solution is to rename the directory and the font itself to
match the TTF filetype.

Best regards,

Agathe.

Bug#1010347: cloudcompare: diff for NMU version 2.11.3-7.1

[Adrian Bunk]

Dear maintainer,

I've prepared an NMU for cloudcompare (versioned as 2.11.3-7.1) and 
uploaded it to DELAYED/2. Please feel free to tell me if I should
cancel it.

cu
Adrian
diff -Nru cloudcompare-2.11.3/debian/changelog cloudcompare-2.11.3/debian/changelog
--- cloudcompare-2.11.3/debian/changelog	2022-10-10 15:52:30.0 +0300
+++ cloudcompare-2.11.3/debian/changelog	2023-04-07 14:45:46.0 +0300
@@ -1,3 +1,11 @@
+cloudcompare (2.11.3-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * CVE-2021-21897: Heap-based buffer overflow loading a DXF file.
+(Closes: #1010347)
+
+ -- Adrian Bunk   Fri, 07 Apr 2023 14:45:46 +0300
+
 cloudcompare (2.11.3-7) unstable; urgency=medium
 
   * Drop png extension from desktop files. (Closes: #1021335)
diff -Nru cloudcompare-2.11.3/debian/patches/0001-check-vertexIndex-which-might-be-1-for-broken-DXF.patch cloudcompare-2.11.3/debian/patches/0001-check-vertexIndex-which-might-be-1-for-broken-DXF.patch
--- cloudcompare-2.11.3/debian/patches/0001-check-vertexIndex-which-might-be-1-for-broken-DXF.patch	1970-01-01 02:00:00.0 +0200
+++ cloudcompare-2.11.3/debian/patches/0001-check-vertexIndex-which-might-be-1-for-broken-DXF.patch	2023-03-20 10:27:04.0 +0200
@@ -0,0 +1,23 @@
+From 1eeffc5daf5a06cf6213ffc19e95923cdebb2eb8 Mon Sep 17 00:00:00 2001
+From: Andrew Mustun 
+Date: Wed, 4 Aug 2021 22:32:43 +0200
+Subject: check vertexIndex which might be -1 for broken DXF
+
+--- a/contrib/dxflib-3.17.0/src/dl_dxf.cpp
 b/contrib/dxflib-3.17.0/dl_dxf.cpp
+@@ -1448,10 +1448,10 @@ bool DL_Dxf::handleLWPolylineData(DL_CreationInterface* /*creationInterface*/) {
+ }
+ 
+ if (groupCode<=30) {
+-if (vertexIndex>=0 && vertexIndex=0 && vertexIndex=0) {
+ vertices[4*vertexIndex + (groupCode/10-1)] = toReal(groupValue);
+ }
+-} else if (groupCode==42 && vertexIndex=0) {
+ vertices[4*vertexIndex + 3] = toReal(groupValue);
+ }
+ return true;
+-- 
+2.30.2
+
diff -Nru cloudcompare-2.11.3/debian/patches/series cloudcompare-2.11.3/debian/patches/series
--- cloudcompare-2.11.3/debian/patches/series	2022-07-21 16:18:05.0 +0300
+++ cloudcompare-2.11.3/debian/patches/series	2023-04-07 14:45:46.0 +0300
@@ -1,3 +1,4 @@
 grr
 0-stdlib.h
 ffmpeg-5.0.patch
+0001-check-vertexIndex-which-might-be-1-for-broken-DXF.patch

Bug#1033225: openboard: Does not monitor user files added while running

[Mike Gabriel]

HI Yvan,

On  Mo 20 Mär 2023 12:16:47 CET, Yvan Masson wrote:


Package: openboard
X-Debbugs-Cc: y...@masson-informatique.fr
Version: 1.6.4+dfsg-1+b1
Severity: normal

Dear Maintainers,

If OpenBoard is running and the user adds a picture inside  
~/Pictures/OpenBoard/, the picture does not immediately appears  
inside OpenBoard's documents, it only appears when OpenBoard is  
restarted.


As a workaround, it is possible to drag and drop the picture from  
the file manager to OpenBoard's documents. In this case, OpenBoard  
takes care of copying the file to ~/Pictures/OpenBoard/.


The same symptom also appears with sounds and videos.

I did not see this issue reported upstream: do not hesitate to ask  
if you want me to report upstream.


Regards,
Yvan


Indeed, please file an upstream report and add a "Forwarded: "  
marker to this Debian bug. The problem needs to be solved by upstream.


Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpq8WH81UOHx.pgp
Description: Digitale PGP-Signatur

Bug#1034034: Does not know about Linux kernel module signatures

[Chris Lamb]

forwarded 1034034 
https://salsa.debian.org/reproducible-builds/diffoscope/-/issues/337
thanks

I've forwarded this 'upstream' to Salsa here:

  https://salsa.debian.org/reproducible-builds/diffoscope/-/issues/337

This is to help us triage, comment and ultimately fix this issue more
effectively.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#1034048: installation-reports: Hangs at graphical install

[Cyril Brulebois]

Hallo Martin,

Martin Dosch  (2023-04-07):
> I had to start the installation 3 times as the first 2 times the 
> installer hung after choosing "graphical install". The third time it 
> worked.

Anything visible on screen, any log lines? What about if you say replace
quiet with debug on the kernel command line?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1034049: RFS: wxmaxima/23.04.0-1 -- GUI for the computer algebra system Maxima

[Gunter Königsmann]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : wxmaxima
   Version  : 23.04.0-1
   Upstream contact : Gunter Königsmann 
 * URL  :http://wxmaxima-developers.github.io/wxmaxima/
 * License  : GPL-2, CC0-1.0, public-domain
 * Vcs  :https://github.com/wxMaxima-developers/wxmaxima
   Section  : math

The source builds the following binary packages:

  wxmaxima - GUI for the computer algebra system Maxima

what wxMaxima does do is: It is a quite featureful UI that allows to use 
maxima, the
computer algebra system. It displays the maths as nice 2d equations, converts 
them
to SVG or PNG, if requested, generates animated plots.
A sample wxMaxima session [as 1D maths] would be:

(%i1)   a*x+b*x^2+c=3;
(%o1)   b*x^2+a*x+c=3
(%i2)   solve(%,x);
(%o2)   [x=-(sqrt(-4*b*c+12*b+a^2)+a)/(2*b),x=(sqrt(-4*b*c+12*b+a^2)-a)/(2*b)]

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/wxmaxima/

Alternatively, you can download the package with 'dget' using this command:

  dget 
-xhttps://mentors.debian.net/debian/pool/main/w/wxmaxima/wxmaxima_23.04.0-1.dsc

Changes since the last upload:

 wxmaxima (23.04.0-1) unstable; urgency=medium
 .
   * New upstream version

Regards,
--
  Gunter Königsmann

Bug#1032914: phog: ships /etc/pam.d/greetd

[duck]

Quack Arnaud,

greetd was unblocked today. Thanks for your help :-).

\_o<

--
Marc Dequènes

Bug#1034048: installation-reports: Hangs at graphical install

[Martin Dosch]

Package: installation-reports
Severity: normal

Boot method: USB
Image version: Debian GNU/Linux bookworm-DI-rc1 "Bookworm" - Official RC amd64 
NETINST with firmware 20230401-21:39
Date: 2023-04-06

Machine: Acer Nitro5 Laptop
Partitions:
LC_ALL=C df -Tl
Filesystem  Type  1K-blocks   Used  
Available Use% Mounted on
udevdevtmpfs7082020  0  
  7082020   0% /dev
tmpfs   tmpfs   1424408   1648  
  1422760   1% /run
/dev/mapper/vg--schlepptop-vg--schlepptop--root ext4 1449640972  124483120 
1251446444  10% /
tmpfs   tmpfs   7122020   1004  
  7121016   1% /dev/shm
tmpfs   tmpfs  5120  0  
 5120   0% /run/lock
/dev/sda2   ext2 960348  92880  
   818624  11% /boot
/dev/sda1   vfat 523244   5948  
   517296   2% /boot/efi
tmpfs   tmpfs   1424404 52  
  1424352   1% /run/user/1000
/dev/sdb1   ext4 1922659820 1733732432  
 91235332  96% /media/martin/Backup
/dev/sdc1   iso9660  777216 777216  
0 100% /media/martin/Debian bookworm-DI-rc1 amd64 n

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

I had to start the installation 3 times as the first 2 times the 
installer hung after choosing "graphical install". The third time it 
worked.

-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230401"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux schlepptop 6.1.0-7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-1 
(2023-03-19) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2 Root Complex [1022:15d0]
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:1366]
lspci -knn: 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2 IOMMU [1022:15d1]
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:1366]
lspci -knn: 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
lspci -knn: 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:01.6 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:01.7 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
lspci -knn: 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A [1022:15db]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B [1022:15dc]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus 
Controller [1022:790b] (rev 61)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:1366]
lspci -knn: 00:14.3 ISA bridge [0601]

Bug#1033993: unbound 1.13.1-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1033993 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: unbound
Version: 1.13.1-1+deb11u1

Explanation: fix Non-Responsive Delegation Attack [CVE-2022-3204]; fix "ghost 
domain names" issue [CVE-2022-30698 CVE-2022-30699]

Bug#1026845: systemd 247.3-7+deb11u2 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1026845 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: systemd
Version: 247.3-7+deb11u2

Explanation: fix information leak issue [CVE-2022-4415], denial of service 
issue [CVE-2022-3821]; ata_id: fix getting Response Code from SCSI Sense Data; 
logind: fix getting property OnExternalPower via D-Bus; fix crash in 
systemd-machined

Bug#1033506: libreoffice 7.0.4-4+deb11u6 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1033506 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: libreoffice
Version: 7.0.4-4+deb11u6

Explanation: avoid empty -Djava.class.path= [CVE-2022-38745]

Bug#1032921: node-webpack 4.43.0-6+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1032921 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: node-webpack
Version: 4.43.0-6+deb11u1

Explanation: avoid cross-realm object access [CVE-2023-28154]

Bug#1032134: node-cookiejar 2.1.2-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1032134 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: node-cookiejar
Version: 2.1.2-1+deb11u1

Explanation: guard against maliciously-sized cookies [CVE-2022-25901]

Bug#1030598: lemonldap-ng 2.0.11+ds-4+deb11u4 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1030598 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: lemonldap-ng
Version: 2.0.11+ds-4+deb11u4

Explanation: fix URL validation bypass issue; fix 2FA issue when using 
AuthBasic handler [CVE-2023-28862]

Bug#1031948: libgit2 1.1.0+dfsg.1-4+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1031948 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: libgit2
Version: 1.1.0+dfsg.1-4+deb11u1

Explanation: enable SSH key verification by defualt [CVE-2023-22742]

Bug#1031410: postgis 3.1.1+dfsg-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1031410 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: postgis
Version: 3.1.1+dfsg-1+deb11u1

Explanation: fix wrong Polar stereographic axis order

Bug#1025703: libexplain 1.4.D001-11+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1025703 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: libexplain
Version: 1.4.D001-11+deb11u1

Explanation: enhance compatibility with newer kernel versions - Linux 5.11 no 
longer has if_frad.h, termiox removed since kernel 5.12

Bug#1033578: joblib 0.17.0-4+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1033578 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: joblib
Version: 0.17.0-4+deb11u1

Explanation: fix arbitrary code execution issue [CVE-2022-21797]

Bug#1033160: flatpak 1.10.8-0+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1033160 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: flatpak
Version: 1.10.8-0+deb11u1

Explanation: new upstream stable release; escape special characters when 
displaying permissions and metadata [CVE-2023-28101]; don't allow copy/paste 
via the TIOCLINUX ioctl when running in a Linux virtual console [CVE-2023-28100]

Bug#1031926: gtk+3.0 3.24.24-4+deb11u3 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1031926 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: gtk+3.0
Version: 3.24.24-4+deb11u3

Explanation: fix Wayland + EGL on GLES-only platforms

Bug#1031630: containerd 1.4.13~ds1-1~deb11u4 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1031630 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: containerd
Version: 1.4.13~ds1-1~deb11u4

Explanation: fix denial of service issue [CVE-2023-25153]; fix possible 
privilege escalation via incorrect setup of supplementary groups 
[CVE-2023-25173]

Bug#1031109: crun 0.17+dfsg-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1031109 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: crun
Version: 0.17+dfsg-1+deb11u1

Explanation: fix capability escalation issue due to containers being 
incorrectly started with non-empty default permissions [CVE-2022-27650]

Bug#1027258: golang-github-containers-psgo 1.5.2-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1027258 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: golang-github-containers-psgo
Version: 1.5.2-1+deb11u1

Explanation: do not enter the process user namespace [CVE-2022-1227]

Bug#1027257: golang-github-containers-storage 1.24.8+dfsg1-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1027257 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: golang-github-containers-storage
Version: 1.24.8+dfsg1-1+deb11u1

Explanation: make previously internal functions publicly accessible, required 
to allow fixing CVE-2022-1227 in other packages

Bug#1034047: fdm: Oauth2 support implemented upstream

[Marcel Fourné]

Package: fdm
Version: 1.9+git20181219-1+b2
Severity: normal

Dear maintainer,

I just found out that the Debian packaged version of fdm does not support 
Oauth2, but this feature has since been implemented upstream in the released 
version 2.0.
An update to this version would allow Debian users to use fdm for fetching mail 
from GMail and other services, if needed.


-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fdm depends on:
ii  adduser  3.132
ii  libc62.36-8
ii  libssl3  3.0.8-1
ii  libtdb1  1.4.8-2
ii  zlib1g   1:1.2.13.dfsg-1

fdm recommends no packages.

fdm suggests no packages.

-- debconf-show failed

Bug#1034039: bullseye-pu: package libpod/3.0.1+dfsg1-3+deb11u1

[Adam D. Barratt]

On Thu, 2023-04-06 at 19:46 -0400, Reinhard Tartler wrote:
> This code change picks up code changes in golang-github-containers-
> psgo
> and golang-github-containers-storage to fix CVE-2022-1227. This is
> reported
> as 1020907. This addresses a priviledge escalation issue when using
> 'podman top'. Upstream has more information in this issue in
> https://bugzilla.redhat.com/show_bug.cgi?id=2070368
> 

I see this has already been uploaded; unfortunately:

-,golang-github-containers-psgo-dev
-,golang-github-containers-storage-dev (>= 1.24.6)
+,golang-github-containers-psgo-dev (>= 1.5.2-1+deb11u1)
+,golang-github-containers-storage-dev (>= 1.24.6+dfsg1-1+deb11u1)

The updated golang-github-containers-storage-dev version there isn't
actually sufficient to ensure that the fixed version is picked up - you
want 1.24.*8*+dfsg1-1+deb11u1.

At this point, either I can reject the current upload, and you can then
re-upload a fixed +deb11u1 or (possibly easier all around) you can
upload +deb11u2 as an incremental change on top of +deb11u1 which
simply fixes the dependency version.

Regards,

Adam

Bug#1031042: mariadb-10.5 10.5.19-0+deb11u1 flagged for acceptance

[Adam D. Barratt]

On Sun, 2023-03-26 at 07:35 +0200, Paul Gevers wrote:
> Hi Otto,
> 
> On 26-03-2023 06:48, Otto Kekäläinen wrote:
> > Based on 
> > https://packages.debian.org/search?keywords=mariadb-server&searchon=names&suite=all§ion=all
> > this 10.5.19-0+deb11u1 is still pending and a stable update of
> > Debian
> > 11 "Bullseye" has not yet been made in March 2023?
> 
> https://lists.debian.org/debian-live/2023/03/msg00025.html
> 
> > Is it OK if I merge in one regression fix and upload a new version?
> 
> I'm not a stable release manager, but I'm pretty sure it's better to 
> file a new bug for that request than updating this bug (it's part of
> the workflow).

Yes, I have a preference for a second bug once the first upload has
been accepted and the second request is not fixing a regression from
the first. It makes some parts of our tracking simpler.

Regards,

Adam

Bug#1025654: bullseye-pu: package x4d-icons/1.2-2+deb11u1

[Adam D. Barratt]

Control: tags -1 -moreinfo +confirmed

On Sun, 2023-04-02 at 01:14 +0200, Santiago Vila wrote:
> El 1/4/23 a las 21:58, Adam D. Barratt escribió:
> > Have you confirmed via a binary debdiff that there are no changes
> > to
> > the resulting packages?
> 
> The package contents is the expected one:
> 
> $ debdiff x4d-icons_1.2-2_all.deb x4d-icons_1.2-2+deb11u1_all.deb
> File lists identical (after any substitutions)
> 
> Control files: lines which differ (wdiff format)
> 
> Installed-Size: [-1188-] {+1187+}
> Version: [-1.2-2-] {+1.2-2+deb11u1+}
> 
> 
> The icons themselves are not bit-for-bit identical, but I think
> they can't really be expected to be, considering that the old package
> was built in 2019-03-12 with possibly different libraries.
> 
> They look certainly the same to the eye when using a png/gif viewer
> or a eps viewer, so I believe everything is ok.
> 

Thanks; please go ahead.

Regards,

Adam

Bug#1033770: bullseye-pu: package apache2/2.4.56-1~deb11u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2023-04-02 at 07:08 +0400, Yadd wrote:
> Control: tags -1 - confirmed
> 
> On 4/1/23 22:47, Moritz Mühlenhoff wrote:
> > Am Sat, Apr 01, 2023 at 08:32:55AM +0400 schrieb Yadd:
[...]
> > > 
apache2 silently reenable apache2-doc.conf despite having been
> > > disabled
> > > (#1018718)
> > 
> > If we update Apache in Bullseye, how about also adding patches for
> > #1033408 and #1033284?
> > 
[...]
> here is the new debdiff
> 

Please go ahead.

Regards,

Adam

Bug#1032237: bullseye-pu: zfs-linux/2.0.3-9+deb11u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2023-04-02 at 10:53 +0800, Aron Xu wrote:
> Control: tags -1 - moreinfo
> 
> On Sun, Apr 2, 2023 at 3:10 AM Adam D. Barratt <
> a...@adam-barratt.org.uk> wrote:
> > Control: tags -1 + moreinfo
> > 
> > On Thu, 2023-03-02 at 15:33 +0800, Aron Xu wrote:
> > > I would like to apply a few patches to address some stability
> > > issues
> > > in the
> > > zfs-linux package in bullseye. All the patches are cherry-picked
> > > from
> > > upstream
> > > 
> > > 2.0.x and 2.1.x stable branches.
> > > 
> > 
> > +This change reworks the zfs_file_[get|put] interface to not rely
> > +on the file descriptor but instead pass the zfs_file_t pointer
> > around.
> > 
> > I'm assuming that nothing outside of zfs-linux depends on the
> > signature
> > of the affected functions?
> > 
> 
> No, there are no other packages depending on the signature of the
> affected functions.
> 

Thanks; please go ahead.

Regards,

Adam

Bug#1034045: clang-15: Segfault during compilation of rocthrust/testing/shuffle.cu

[Sylvestre Ledru]

Hello,

Le 07/04/2023 à 10:35, Cordell Bloor a écrit :

Package: clang-15
Version: 1:15.0.7-4
Severity: normal
X-Debbugs-Cc: c...@slerp.xyz, debian...@lists.debian.org

Dear Maintainer,

I'm having trouble reproducing this problem, but I figured I should
report it anyway in case other users had seen similar behaviour.
You should probably report this upstream with a reduced test case.


Cheers,
Sylvestre

Bug#1027257: bullseye-pu: package golang-github-containers-storage/1.24.8+dfsg1-2~deb11u1

[Adam D. Barratt]

On Sat, 2023-04-01 at 19:04 -0400, Reinhard Tartler wrote:
> 
> On 4/1/23 3:51 PM, Adam D. Barratt wrote:
> > Control: tags -1 + moreinfo
> > 
> > Apologies for the delay in getting back to you on this.
> > 
> > On Wed, 2022-12-28 at 22:26 -0500, Reinhard Tartler wrote:
> > > In order to fix CVE-2022-1227, an update to golang-github-
> > > containers-
> > > psgo
> > > is needed, more specifically,
> > > https://github.com/containers/psgo/pull/92
> > > 
> > > That patch introduces a dependency on golang-github-containers-
> > > storage, and uses
> > > the helper functions RawTo{Container,Host} which are introduced
> > > with
> > > this patch.
> > > 
> > [...]
> > > The code changes adds a helper function that isn't used otherwise
> > > yet.
> > 
> > Looking at the diff, it appears that what it actually does is
> > rename
> > two existing helper functions, with no functional change to either.
> > Am
> > I missing something?
> 
> You are correct. The patch renames the helper functions to an
> Uppercase spelling.
> This exposes the function to other packages, which is being used in
> the patch
> to fix CVE-2022-1227.
> 

Indeed. I write little enough Go these days that I forget about its
visibility rules.

Regards,

Adam

Bug#1034046: unblock: markdown-exec/1.4.0-1

[Carsten Schoenert]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: markdown-e...@packages.debian.org
Control: affects -1 + src:markdown-exec

Please unblock package markdown-exec

[ Reason ]
The package got rather small upstream modifications since 1.3.0 I'd like
to see in the bookworm release. Another reason is the mark as a core
package which requires a manually unblock by the RT.

An diff about the differences between 1.3.0 and 1.4.0 can be viewed on
the project GitHub website.

https://github.com/pawamoy/markdown-exec/compare/1.3.0...1.4.0

[ Impact ]
The user can use a improved Session handling which was added to 1.4.0.

[ Tests ]
All the tests while package build and within the autopkgtest run
succeeded. Using the newer Debian package in local projects working just
fine.

[ Risks ]
The risks are quite low as only extra functionality was added and no
changes did happen to the existing code.
No issues got reported since the upload of 1.4.0-1 almost 3 weeks ago.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing


diff -Nru markdown-exec-1.3.0/CHANGELOG.md markdown-exec-1.4.0/CHANGELOG.md
--- markdown-exec-1.3.0/CHANGELOG.md2023-02-18 13:54:04.0 +0100
+++ markdown-exec-1.4.0/CHANGELOG.md2023-03-15 21:43:25.0 +0100
@@ -5,6 +5,14 @@
 and this project adheres to [Semantic 
Versioning](http://semver.org/spec/v2.0.0.html).
 
 

+## [1.4.0](https://github.com/pawamoy/markdown-exec/releases/tag/1.4.0) - 
2023-03-15
+
+[Compare with 
1.3.0](https://github.com/pawamoy/markdown-exec/compare/1.3.0...1.4.0)
+
+### Features
+
+- Sessions: persist and reuse state for Python and Pycon code blocks 
([a8fef5e](https://github.com/pawamoy/markdown-exec/commit/a8fef5e90b1d7165e16ff5afe4b84e8441503098)
 by Timothée Mazzucotelli). [Issue 
#16](https://github.com/pawamoy/markdown-exec/issues/16)
+
 ## [1.3.0](https://github.com/pawamoy/markdown-exec/releases/tag/1.3.0) - 
2023-02-18
 
 [Compare with 1.2.0](https://github.com/pawamoy/markdown-exec/compare/1.2.0...1.3.0)

diff -Nru markdown-exec-1.3.0/debian/changelog 
markdown-exec-1.4.0/debian/changelog
--- markdown-exec-1.3.0/debian/changelog2023-02-27 12:21:30.0 
+0100
+++ markdown-exec-1.4.0/debian/changelog2023-03-19 07:26:01.0 
+0100
@@ -1,3 +1,9 @@
+markdown-exec (1.4.0-1) unstable; urgency=medium
+
+  * [2aede3c] New upstream version 1.4.0
+
+ -- Carsten Schoenert   Sun, 19 Mar 2023 07:26:01 
+0100
+
 markdown-exec (1.3.0-1) unstable; urgency=medium
 
   * [8a80096] New upstream version 1.3.0

diff -Nru markdown-exec-1.3.0/docs/usage/index.md 
markdown-exec-1.4.0/docs/usage/index.md
--- markdown-exec-1.3.0/docs/usage/index.md 2023-02-18 13:54:04.0 
+0100
+++ markdown-exec-1.4.0/docs/usage/index.md 2023-03-15 21:43:25.0 
+0100
@@ -258,6 +258,27 @@
 > WARNING  -  markdown_exec: Execution of python code block 'print world' 
exited with errors
 > ```
 
+## Sessions

+
+Markdown Exec makes it possible to persist state between executed code blocks.
+To persist state and reuse it in other code blocks, give a session name to 
your blocks:
+
+md exec="1" source="material-block" title="Sessions"
+```python exec="1" session="greet"
+def greet(name):
+print(f"Hello {name}!")
+```
+
+Hello Mushu!
+
+```python exec="1" session="greet"
+greet("Ping")
+```
+
+
+WARNING: **Limitation**  
+Sessions only work with Python and Pycon syntax for now.

+
 ## Literate Markdown
 
 With this extension, it is also possible to write "literate programming" Markdown.

diff -Nru markdown-exec-1.3.0/README.md markdown-exec-1.4.0/README.md
--- markdown-exec-1.3.0/README.md   2023-02-18 13:54:04.0 +0100
+++ markdown-exec-1.4.0/README.md   2023-03-15 21:43:25.0 +0100
@@ -91,5 +91,14 @@
 
 The `exec` option will be true for every possible value except `0`, `no`, `off` and `false` (case insensitive).
 
+Below you can see an example of running a bash script that is expected to

+return a non-zero exit code:
+
+md
+```bash exec="1" source="tabbed-left" returncode="2"
+grep extra_css README.md && exit 2
+```
+
+
 See [usage](https://pawamoy.github.io/markdown-exec/usage/) for more details,
 and the [gallery](https://pawamoy.github.io/markdown-exec/gallery/) for more 
examples!
diff -Nru markdown-exec-1.3.0/src/markdown_exec/formatters/base.py 
markdown-exec-1.4.0/src/markdown_exec/formatters/base.py
--- markdown-exec-1.3.0/src/markdown_exec/formatters/base.py2023-02-18 
13:54:04.0 +0100
+++ markdown-exec-1.4.0/src/markdown_exec/formatters/base.py2023-03-15 
21:43:25.0 +0100
@@ -50,6 +50,7 @@
 id: str = "",  # noqa: A002,VNE003
 returncode: int = 0,
 transform_source: Callable[[str], tuple[str, str]] | None = None,
+session: str | None = None,
 **options: Any,
 ) -> Markup:
  

Bug#1034045: clang-15: Segfault during compilation of rocthrust/testing/shuffle.cu

[Cordell Bloor]

Package: clang-15
Version: 1:15.0.7-4
Severity: normal
X-Debbugs-Cc: c...@slerp.xyz, debian...@lists.debian.org

Dear Maintainer,

I'm having trouble reproducing this problem, but I figured I should
report it anyway in case other users had seen similar behaviour.

While compiling the rocthrust test suite, I encountered a segfault in
the compiler. To move forward with my work, I decided to disable
building the test that triggered the segfault, with the intention of
returning to prepare a simple, self-contained example of the problem
later. Unfortunately, when I returned to prepare this bug report, I was
unable to reproduce the crash. I'm unsure of whether I have somehow
failed to reproduce the original conditions that caused the crash, or
if the crash is non-deterministic.

I originally thought this crash was a regression from 15.0.6, but I no
longer have any reason to believe that. It may just have been luck that
I never encountered this crash before.

The only information that I saved from the failure is this log snippet:

[ 90%] Building CXX object 
testing/CMakeFiles/test_thrust_zip_iterator_reduce_by_key.dir/zip_iterator_reduce_by_key.cu.o
cd /root/rocthrust/rocthrust/obj-x86_64-linux-gnu/testing && /usr/bin/hipcc 
-D__HIP_PLATFORM_AMD__=1 -D__HIP_PLATFORM_HCC__=1 
-I/root/rocthrust/rocthrust/obj-x86_64-linux-gnu/thrust/include 
-I/root/rocthrust/rocthrust/thrust/.. -isystem 
/root/rocthrust/rocthrust/testing -Wno-deprecated-builtins -g -O2 
-ffile-prefix-map=/root/rocthrust/rocthrust=. -Xarch_host 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wno-unused-command-line-argument -Wall -Wextra  -std=c++14 
-O3 -DNDEBUG -x hip --offload-arch=gfx803 --offload-arch=gfx900 
--offload-arch=gfx906 --offload-arch=gfx908 --offload-arch=gfx90a 
--offload-arch=gfx1010 --offload-arch=gfx1011 --offload-arch=gfx1030 
-DGTEST_HAS_PTHREAD=1 -std=c++14 -MD -MT 
testing/CMakeFiles/test_thrust_zip_iterator_reduce_by_key.dir/zip_iterator_reduce_by_key.cu.o
 -MF 
CMakeFiles/test_thrust_zip_iterator_reduce_by_key.dir/zip_iterator_reduce_by_key.cu.o.d
 -o 
CMakeFiles/test_thrust_zip_iterator_reduce_by_key.dir/zip_iterator_reduce_by_key.cu.o
 -c /root/rocthrust/rocthrust/testing/zip_iterator_reduce_by_key.cu
PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and 
include the crash backtrace, preprocessed source, and associated run script.
Stack dump:
0.  Program arguments: /usr/lib/llvm-15/bin/clang -cc1 -triple 
amdgcn-amd-amdhsa -aux-triple x86_64-pc-linux-gnu -emit-obj 
--mrelax-relocations -disable-free -clear-ast-before-backend 
-disable-llvm-verifier -discard-value-names -main-file-name shuffle.cu 
-mrelocation-model pic -pic-level 1 -fhalf-no-semantic-interposition 
-mframe-pointer=none -fno-rounding-math -mconstructor-aliases -aux-target-cpu 
x86-64 -fcuda-is-device -mllvm -amdgpu-internalize-symbols 
-fcuda-allow-variadic-functions -fvisibility hidden 
-fapply-global-visibility-to-externs -mlink-builtin-bitcode 
/usr/lib/x86_64-linux-gnu/amdgcn/bitcode/hip.bc -mlink-builtin-bitcode 
/usr/lib/x86_64-linux-gnu/amdgcn/bitcode/ocml.bc -mlink-builtin-bitcode 
/usr/lib/x86_64-linux-gnu/amdgcn/bitcode/ockl.bc -mlink-builtin-bitcode 
/usr/lib/x86_64-linux-gnu/amdgcn/bitcode/oclc_daz_opt_off.bc 
-mlink-builtin-bitcode 
/usr/lib/x86_64-linux-gnu/amdgcn/bitcode/oclc_unsafe_math_off.bc 
-mlink-builtin-bitcode 
/usr/lib/x86_64-linux-gnu/amdgcn/bitcode/oclc_finite_only_off.bc 
-mlink-builtin-bitcode 
/usr/lib/x86_64-linux-gnu/amdgcn/bitcode/oclc_correctly_rounded_sqrt_on.bc 
-mlink-builtin-bitcode 
/usr/lib/x86_64-linux-gnu/amdgcn/bitcode/oclc_wavefrontsize64_off.bc 
-mlink-builtin-bitcode 
/usr/lib/x86_64-linux-gnu/amdgcn/bitcode/oclc_isa_version_1030.bc 
-mlink-builtin-bitcode 
/usr/lib/x86_64-linux-gnu/amdgcn/bitcode/oclc_abi_version_400.bc -target-cpu 
gfx1030 -mllvm -treat-scalable-fixed-error-as-warning 
-debug-info-kind=constructor -dwarf-version=5 -debugger-tuning=gdb 
-resource-dir /usr/lib/llvm-15/lib/clang/15.0.7 -dependency-file 
CMakeFiles/test_thrust_shuffle.dir/shuffle.cu.o.d -MT 
testing/CMakeFiles/test_thrust_shuffle.dir/shuffle.cu.o -sys-header-deps 
-internal-isystem /usr/lib/llvm-15/lib/clang/15.0.7/include/cuda_wrappers 
-idirafter /usr/include -include __clang_hip_runtime_wrapper.h -isystem 
/usr/lib/llvm-15/lib/clang/15.0.7/include/.. -isystem /usr/hsa/include -isystem 
/root/rocthrust/rocthrust/testing -D __HIP_PLATFORM_AMD__=1 -D 
__HIP_PLATFORM_HCC__=1 -I 
/root/rocthrust/rocthrust/obj-x86_64-linux-gnu/thrust/include -I 
/root/rocthrust/rocthrust/thrust/.. -D _FORTIFY_SOURCE=2 -D NDEBUG -D 
GTEST_HAS_PTHREAD=1 -internal-isystem 
/usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12 
-internal-isystem 
/usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/x86_64-linux-gnu/c++/12
 -internal-isystem 
/usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/backward 
-internal-isystem 
/usr/bin/../lib/gcc/x86_

Bug#1034044: aptitude: please enable backup of pkgstates via a systemd timer

[Sven Joachim]

Package: aptitude
Version: 0.8.13-5
Severity: wishlist

There is a cron.daily script which creates backups of the
/var/lib/aptitude/pkgstates file.  It would be nice to have a systemd
service file and a timer for that job as well.  On my laptop, aptitude
is the only package that ships a cron job for which there is no systemd
timer alternative and would lose functionality if I were to remove cron
and anacron.

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

Bug#1034043: RFS: git-credential-oauth/0.5.2-1 -- Git credential helper for GitHub and other forges using OAuth

[M Hickford]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "git-credential-oauth":

 * Package name : git-credential-oauth
   Version  : 0.5.2-1
   Upstream contact : M Hickford 
 * URL  : https://github.com/hickford/git-credential-oauth
 * License  : Apache-2.0
 * Vcs  :
https://salsa.debian.org/go-team/packages/git-credential-oauth
   Section  : golang

The source builds the following binary packages:

  git-credential-oauth - Git credential helper for GitHub and other
forges using OAuth

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/git-credential-oauth/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/g/git-credential-oauth/git-credential-oauth_0.5.2-1.dsc

Changes since the last upload:

 git-credential-oauth (0.5.2-1) unstable; urgency=medium
 .
   * New upstream version.

Regards,