Bug#1052052: ping?

[Rene Engelhard]

Am 02.11.23 um 23:25 schrieb Gabor Karsay:
thank you, I tried your fix with experimental libreoffice and pushed 
it to https://salsa.debian.org/gkarsay/parlatype-libreoffice-extension


I haven't uploaded it yet, I don't know if I should target 
experimental or unstable?
unstable, please. It should work with sids libreoffice too. This makes 
the way of uploading it open instead of needing to nudge you again to 
upload experimental->unstable
I also don't understand why the build i386 pipeline failed complaining 
about unmet dependencies.


Neither me, but maybe it fell into some temporary issue (e.gf. caused by 
the 7.5.8-1 upload)?



Regards,


Rene

Bug#1055039: redis-server: Crash every two hours (oom), seemingly due to systemd's ProcSubset=pid

[Arnaud Rebillout]

On 02/11/2023 21:31, Chris Lamb wrote:

Chris Lamb wrote:

D'oh, of course! As you might have guessed, I had a "brain typo" and
had completely forgotten that stable = bookworm (and not bullseye).
I'll get onto this presently.

This has been filed as #1055229.


Thanks very much Chris !

Best,

--
Arnaud Rebillout / OffSec / Kali Linux Developer

Bug#1055260: Wayland and sound server connection

[Osamu Aoki]

Source: debian-reference
Version: 2.105
Severity: wishlist

Although we have "7.8. X server connection", there is no mention of
Wayland and sound server connection.

Of course, Wayland server connection is limitted to local machine, it
should be given at least minimum pointer for people using lxd or kvm.

This should be carefully written without getting into too much details.

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

Kernel: Linux 6.4.0-0.deb12.2-amd64 (SMP w/12 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

Bug#1054657: transition: r-bioc-biocgenerics

[Charles Plessy]

> Am Wed, Nov 01, 2023 at 09:02:10AM -0100 schrieb Graham Inggs:
> > Again, we are not asking for the entire transition to happen in
> > experimental.  We are only asking for the NEW packages, so that NEW
> > processing happens before the transition, and not during.

Le Wed, Nov 01, 2023 at 11:28:38AM +0100, Andreas Tille a écrit :
> Understood this item now - but I'm lacking any clue how to find out
> what new packages are needed.

Hi Graham and Andreas,

I just finished inspecting by eye the homepage of each of the 69 new
Bioconductor packages.  None of them declare a reverse-dependency to
an existing Bioc package that we ship in Debian.  Therefore, I do not
expect that this transition will require NEW processing.

https://bioconductor.org/news/bioc_3_18_release/

Graham, please let us know when we can start uploading.

Have a nice day,

Charles

-- 
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team http://www.debian.org/devel/debian-med
Tooting from home  https://framapiaf.org/@charles_plessy
- You  do not have  my permission  to use  this email  to train  an AI -

Bug#1055259: please include MPTCP patch

[Steinar H. Gunderson]

Source: openssh
Version: 1:9.2p1-2+deb12u1
Severity: wishlist

Hi,

MPTCP support has been available in a pull request against upstream for a while:

  https://github.com/openssh/openssh-portable/pull/335

Unfortunately, upstream does not want it because OpenBSD doesn't support MPTCP.
Would it be possible for Debian to pull it in? I believe network-manager and
everything else should be MPTCP-ready now, giving you essentially mosh-like
roaming straight out of the box. The patch is essentially only adding an option
to change from IPPROTO_TCP to IPPROTO_MPTCP and then add some documentation.


-- System Information:
Debian Release: 12.2
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.10 (SMP w/56 CPU threads; PREEMPT)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NO:en_US:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#1055258: Should pesign be Architecture: any ?

[Steve McIntyre]

On Fri, Nov 03, 2023 at 12:31:22AM +0200, Adrian Bunk wrote:
>Source: pesign
>Version: 116-3
>Severity: normal
>
>Is there a reason for maintaining a manual architecture list
>instead of having the buildds determine this automatically
>based on where efivar is available?
>
>IOW, is there a reason why pesign shouldn't be built
>on ia64/mips64el/x32 ?

Actually, I think you're right. I'll tweak again for the next upload.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Yes, of course duct tape works in a near-vacuum. Duct tape works
 anywhere. Duct tape is magic and should be worshipped."
   -― Andy Weir, "The Martian"

Bug#1055258: Should pesign be Architecture: any ?

[Adrian Bunk]

Source: pesign
Version: 116-3
Severity: normal

Is there a reason for maintaining a manual architecture list
instead of having the buildds determine this automatically
based on where efivar is available?

IOW, is there a reason why pesign shouldn't be built
on ia64/mips64el/x32 ?

Bug#931225: Please make Classic style the default

[Ian Jackson]

Four and half years ago I reported what were then already longstanding
and severe bugs in the custom theme we use as the default theme for
the Debian wiki.

I also requested that the default be changed to the "Classic" theme
(which as I understand it is provided by upstream), pending a fix to
those bugs in our own theme.

As I wrote three years ago

> If those who really dislike the Classic theme find it too ugly, then
> I think it would be reasonable to expect those people to maintain
> that theme.  That includes fixing serious defects in a reasonable
> time.

There has been no progress.  No-one authoritative has given the
go-ahead, and said that this change should be made.  But, neither has
anyone authoritative vetoed it.

It appears that no-one with the relevant authority is interested in
this problem.  That's fine; I'm not demanding that anyone do work that
they're not interested in.

However, I wish this problem to be unblocked.  It doesn't seem like
simply changing the default will be very difficult.  So:

I suspect that this default is part of the MoinMoin configuration
files, which we have perhaps modifed.  Or, that it is stored in the
MoinMoin database.  It will probably be obvious from insepcting the
running system where this change has been made.

In either case, I believe DSA would be able to either change the
default themselves, or grant me sufficient technical privilege to make
the change myself.

If I don't hear to the contrary within (say) 28 days, I will ask DSA
to make "Classic" the default theme on wiki.debian.org, or to enable
me to make that change myself.

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.  

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

Bug#1052052: ping?

[Gabor Karsay]

Hi,

thank you, I tried your fix with experimental libreoffice and pushed it 
to https://salsa.debian.org/gkarsay/parlatype-libreoffice-extension


I haven't uploaded it yet, I don't know if I should target experimental 
or unstable? I also don't understand why the build i386 pipeline failed 
complaining about unmet dependencies.


Regards,
Gabor


OpenPGP_0xC892C2F1310F600B.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055257: tcpdump fails to change ownership of savefile if built with libcap-ng

[Alex Kompel]

Package: tcpdump
Version: 4.99.3-1

If the binary is built with lipcap-ng, tcpdump fails with "Couldn't change 
ownership of savefile". If HAVE_LIBCAP_NG is defined, chown is called after 
CAP_CHOWN capability is dropped.
I believe this is caused by the recent patch introduced as part of 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935112 : 
https://salsa.debian.org/rfrancoise/tcpdump/-/blob/master/debian/patches/drop-privs-after-opening-savefile.diff

dget http://deb.debian.org/debian/pool/main/t/tcpdump/tcpdump_4.99.3-1.dsc
sudo apt install libcap-ng-dev
cd tcpdump-4.99.3
debian/rules build

Test:
sudo strace -e "capset,capget,chown"  /home/ubuntu/c/tcpdump-4.99.3/tcpdump -w 
/tmp/test.pcap

capget({version=0 /* _LINUX_CAPABILITY_VERSION_??? */, pid=0}, NULL) = 0
capget({version=_LINUX_CAPABILITY_VERSION_3, pid=18467}, 
{effective=1<

Bug#1054621: lutris: new dependencies

[at46]

fluidsynth is problematic. It blocked my sound device on every second 
boot until I disabled it. And I'm not the only one with that problem see 
#1053245


Regards
Axel

Bug#1053245: fluidsynth: Fluidsynth starts at boot and blocks the sound device, no obvious way to disable it

[at46]

I had the same problem and it took me quite some time to find that 
fluidsynth was the root cause of this. Fluidsynth was installed as new 
dependency from lutris 0.5.14 and blocked my sound device each ~second 
boot.


@Patrick I could check the status with "systemctl --user status 
fluidsynth" and disable it with "sudo systemctl --global disable 
fluidsynth.service"


Regards,
Axel

Bug#1055146: zydis: Compilation error on the LoongArch architecture

[Andrea Pappacoda]

Il giorno mer 1 nov 2023 alle 08:16:48 +00:00:00, wuruilong 
 ha scritto:

There is a compilation error for zydis on the loongarch machine.
Tested the patch attached to the email on the LoongArch machine and 
it resolved the issue.


Hi wuruilong, thanks for the patch! Since it has been upstreamed too, 
I'll look into adding it to the Zydis package soon.


Thanks again :)

Bug#1055256: colmap: Missing build dependency on libcgal-dev

[Adrian Bunk]

Source: colmap
Version: 3.8+git20231101+ds-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=colmap=3.8%2Bgit20231101%2Bds-1

...
CMake Error at cmake/FindDependencies.cmake:62 (find_package):
  By not providing "FindCGAL.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "CGAL", but
  CMake did not find one.

  Could not find a package configuration file provided by "CGAL" with any of
  the following names:

CGALConfig.cmake
cgal-config.cmake

  Add the installation prefix of "CGAL" to CMAKE_PREFIX_PATH or set
  "CGAL_DIR" to a directory containing one of the above files.  If "CGAL"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  CMakeLists.txt:86 (include)


-- Configuring incomplete, errors occurred!

Bug#1055255: matrix-synapse: CVE-2023-43796

[Salvatore Bonaccorso]

Source: matrix-synapse
Version: 1.95.0-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for matrix-synapse.

CVE-2023-43796[0]:
| Synapse is an open-source Matrix homeserver Prior to versions 1.95.1
| and 1.96.0rc1, cached device information of remote users can be
| queried from Synapse. This can be used to enumerate the remote users
| known to a homeserver. System administrators are encouraged to
| upgrade to Synapse 1.95.1 or 1.96.0rc1 to receive a patch. As a
| workaround, the `federation_domain_whitelist` can be used to limit
| federation traffic with a homeserver.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-43796
https://www.cve.org/CVERecord?id=CVE-2023-43796
[1] 
https://github.com/matrix-org/synapse/security/advisories/GHSA-mp92-3jfm-3575
[2] 
https://github.com/matrix-org/synapse/commit/daec55e1fe120c564240c5386e77941372bf458f
 

Regards,
Salvatore

Bug#1014017: soundmodem: Fails to build with HID support

[Alan Crosswell]

Dave: This patch would be mostly invisible to existing users. It would add
the gpio attribute to the soundmodem configuration with a default empty
value.

73

On Thu, Nov 2, 2023 at 11:25 AM Dave Hibberd  wrote:

> Hi Alan,
>
> I'm part of quite an active packet communtiy (
> https://ukpacketradio.network/) - DINAH looks like a cool item a number
> of folks would be itnerested in! Not many of our users are on soundmodem -
> direwolf, G8BPQ's QtSoundmodem (which I plan to upload to Debian) and (in
> hardware) NinoTNC are the flavour of the month for us.
>
> I know of a few CM108 mods (our sister communtiy even has a guide -
> https://wiki.oarc.uk/cm108_sound_interface_smd)
> , so extending
> functionality to more people would be generally of benefit to all.
>
> Soundmodem is a little old, but it's also not moving very fast so I don't
> see too much overhead in maintaining a patch for it unless it's likely to
> degrade the experience for other users?
>
> Cheers
>
> DH
>
> --
>   Hibby
>   MM0RFN
>
> On Thu, 2 Nov 2023, at 2:45 PM, Alan Crosswell wrote:
>
> Hey Daniele,
>
> It's been about a year and I've just now gotten around to building a
> Raspberry Pi connected to a DINAH and can confirm that this PTT patch still
> works on the latest Raspi Bullseye distro. I don't know if there's any
> interest in carrying this forward to a committed patch for soundmodem. I
> can always keep patching it myself if I'm the only one who still thinks
> soundmodem is a nice small tool for AX.25.
>
> Regarding many more CM108's, I wonder how many of them are integrated such
> that a spare GPIO pin is used for PTT? Given it's probably not a lot, I
> wouldn't think removing the device test entirely would be a huge issue.
> Would you like me to submit a revised PR to do that?
>
> 73 de N2YGK
>
> On Mon, 24 Oct 2022 09:14:23 -0400 Alan Crosswell  wrote:
> > Yeah I don't know that ignoring the device code would be much of a
> problem.
> > It's not like it searches available devices to see which one to use; the
> > specific device to use is specified.
> >
> > On Sun, Oct 23, 2022 at 3:10 PM Daniele Forsi  wrote:
> >
> > > Hello Alan,
> > >
> > > I committed your patch to configure.ac in a branch and I think that we
> > > should merge it to master:
> > > https://salsa.debian.org/debian-hamradio-team/soundmodem/-/tree/hidraw
> > >
> > > I didn't commit your patch to ptt.c yet.
> > > What happens if we drop the check for hiddevinfo.product for C-Media
> > > entirely?
> > >
> > > You changed the test to work with your hardware, which is fine, but it
> > > seems that there are many more CM108s out there (I have one with ID
> > > 0d8c:013c).
> > > I'm copying the list from https://usb-ids.gowdy.us/read/UD/0d8c so it
> > > is archived with this bug report.
> > >
> > > Id Name
> > > 0001 Audio Device
> > > 0002 Composite Device
> > > 0003 Sound Device
> > > 0004 CM6631A Audio Processor
> > > 0005 Blue Snowball
> > > 0006 Storm HP-USB500 5.1 Headset
> > > 000c Audio Adapter
> > > 000d Composite Device
> > > 000e Audio Adapter (Planet UP-100, Genius G-Talk)
> > > 0012
> > > 0014 Audio Adapter (Unitek Y-247A)
> > > 001f CM108 Audio Controller
> > > 0029
> > > 0102 CM106 Like Sound Device
> > > 0103 CM102-A+/102S+ Audio Controller
> > > 0104 CM103+ Audio Controller
> > > 0105 CM108 Audio Controller
> > > 0107 CM108 Audio Controller
> > > 010f CM108 Audio Controller
> > > 0115 CM108 Audio Controller
> > > 0134
> > > 0139 Multimedia Headset [Gigaware by Ignition L.P.]
> > > 013c CM108 Audio Controller
> > > 0201 CM6501
> > > 5000 Mass Storage Controller
> > > 5200 Mass Storage Controller(0D8C,5200)
> > > b213 USB Phone CM109 (aka CT2000,VPT1000)
> > >
> > > --
> > > 73 de IU5HKX Daniele
> > >
>
>
>

Bug#1055108: Acknowledgement (/usr/libexec/gnome-remote-desktop-daemon: Every time I reboot my remote desktop password is reset)

[Jonathan Kamens]

One difference between the two systems that may or may not be relevant: 
the one where this problem is occurring has a fingerprint reader, the 
other one does not.


If I disable automatic login on the system having this problem and then 
log in with my password, this problem does not occur. If on the other 
hand with automatic login disabled I log in with my fingerprint, this 
problem does occur.


So it appears that on the system where I'm not having this problem, 
something in the login sequence is forcing GNOME to prompt for my 
keyring password on login and that happens before gnome-remote-desktop 
starts up, whereas on the system where I'm having this problem, that's 
not happening so when gnome-remote-desktop starts up it can't get to the 
password stored in the keyring to it creates a new, random password.

Bug#941804: exim4: remote_smtp_smarthost transport does not set DKIM variables

[Larry Doolittle]

Andreas -

On Thu, Nov 02, 2023 at 04:51:55PM +0100, Andreas Metzler wrote:
> Just to be clear: You have got a domain but lack both control of a
> machine that is not blocked from accessing outgoing port 25 (and could
> deliver)

Right.  Standard for a "modern" consumer-grade ISP in the U.S.

> and the domain package does also lack a smarthost for that
> domain that would apply a dkim signature?

Yes.  The boa.org domain infrastructure and maintenance is
self-serve and all-volunteer.  (Thanks, Russ!)

How would a domain-package smarthost help, if I couldn't get to
its port 25 because of the ISP firewall?

Of course I don't know the individual situations of others who have
posted this question and its answer to various on-line forums.
But it's common enough that it was easy to find the answer and
patch my Debian exim4 setup to get the desired results.

You can see the DKIM my exim4 added, before passing to an ISP smarthost,
if you look at the headers of this email.

  - Larry

Bug#1055254: transition: dav1d

[Dylan Aïssi]

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

Dear Release Team,

Please schedule a transition slot for dav1d.

The auto-generated ben tracker looks good:
https://release.debian.org/transitions/html/auto-dav1d.html

All reverse deps (ffmpeg, libavif, libheif, vlc and xine-lib-1.2) build fine
with the new version in experimental.

Thanks,
Dylan

Bug#1055253: amanda: CVE-2023-30577

[Salvatore Bonaccorso]

Source: amanda
Version: 1:3.5.1-11
Severity: grave
Tags: security upstream
Forwarded: https://github.com/zmanda/amanda/pull/228
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1:3.5.1-7

Hi,

The following vulnerability was published for amanda.

CVE-2023-30577[0]:
| AMANDA (Advanced Maryland Automatic Network Disk Archiver) before
| tag-community-3.5.4 mishandles argument checking for runtar.c, a
| different vulnerability than CVE-2022-37705.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-30577
https://www.cve.org/CVERecord?id=CVE-2023-30577
[1] https://github.com/zmanda/amanda/security/advisories/GHSA-crrw-v393-h5q3
[2] https://github.com/zmanda/amanda/pull/228

Regards,
Salvatore

Bug#1055252: squid: CVE-2023-46724: SQUID-2023:4 Denial of Service in SSL Certificate validation

[Salvatore Bonaccorso]

Source: squid
Version: 6.3-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for squid.

CVE-2023-46724[0]:
| Squid is a caching proxy for the Web. Due to an Improper Validation
| of Specified Index bug, Squid versions 3.3.0.1 through 5.9 and 6.0
| prior to 6.4 compiled using `--with-openssl` are vulnerable to a
| Denial of Service attack against SSL Certificate validation. This
| problem allows a remote server to perform Denial of Service against
| Squid Proxy by initiating a TLS Handshake with a specially crafted
| SSL Certificate in a server certificate chain. This attack is
| limited to HTTPS and SSL-Bump. This bug is fixed in Squid version
| 6.4. In addition, patches addressing this problem for the stable
| releases can be found in Squid's patch archives. Those who you use a
| prepackaged version of Squid should refer to the package vendor for
| availability information on updated packages.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-46724
https://www.cve.org/CVERecord?id=CVE-2023-46724
[1] 
https://github.com/squid-cache/squid/commit/792ef23e6e1c05780fe17f733859eef6eb8c8be3
[2] https://megamansec.github.io/Squid-Security-Audit/ssl-bufferunderread.html
[3] https://github.com/squid-cache/squid/security/advisories/GHSA-73m6-jm96-c6r3

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1055244: linux-image-amd64: Please enable CONFIG_MTK_T7XX for the Intel/Mediatek FM350-GL 5G modem

[Vincent Blut]

Hi Martin,

Le 2023-11-02 20:10, Martin Sofaru a écrit :
> Source: linux
> Version: linux/6.5.0-3
> Severity: wishlist
> X-Debbugs-Cc: debian-b...@fhloston.org
> 
> Dear Maintainer,
> 
> please set CONFIG_MTK_T7XX=m to build the mtk_t7xx kernel module.
> 
> This module is necessary to use some 5G modems built into newer Lenovo 
> Laptops like X1 Yoga Gen7/Gen8 and X1 Carbon Gen10/Gen11.
> 
> As long as this [1] patch is not merged upstream, it might be sensible to 
> also include this. 
> 
> The modem itself also needs some kind of FCC unlock which can be found here 
> [2].

I'll send a merge request soon. The patch to have the modem part work has been
merged in Linux 6.6-rc1.
 
> Thank you
> 
> Martin

Cheers,
Vincent


signature.asc
Description: PGP signature

Bug#1009067: How can I help move this along?

[Charles Suprin]

Howdy,

This seems to be fixed but not moving forward.

Thanks.

Bug#1055248: bookworm-pu: pipewire/0.3.65-3+deb12u1

[Dylan Aïssi]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
Control: affects -1 + src:pipewire

[ Reason ]
Fix memory leak in pipewire-pulse #1015915.

[ Impact ]
If not fixed, unnecessary memory consumption.

[ Tests ]
Tested in a VM without any sound issue.

[ Risks ]
Low, The change is small and already applied since several versions
in testing/unstable.

[ 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 (old)stable
  [x] the issue is verified as fixed in unstable (and trixie)


Best regards,
Dylan


pw_0.3.65-3+deb12u1.debdiff
Description: Binary data

Bug#1055247: mini-dinstall: throws repeated deprecation warnings

[Sven Geuer]

Package: mini-dinstall
Version: 0.7.2
Severity: normal

Dear Maintainer,

after having done a fresh install and configuration of mini-dinstall the first
call

  $ mini-dinstall -b

results in repeated deprecation warnings

  /usr/bin/mini-dinstall:523: DeprecationWarning: getName() is deprecated, get
the name attribute instead
self._logger.info('Created new installer thread (%s)' % self.getName())
  /usr/bin/mini-dinstall:1624: DeprecationWarning: getName() is deprecated, get
the name attribute instead
logger.debug('Starting archive %s' % archive.getName())
  /usr/bin/mini-dinstall:1228: DeprecationWarning: getName() is deprecated, get
the name attribute instead
self._logger.info('Created new thread (%s) for archive indexer %s' %
(self.getName(), self._name))
  /usr/bin/mini-dinstall:1632: DeprecationWarning: getName() is deprecated, get
the name attribute instead
logger.debug('Waiting for archive %s to finish' % archive.getName())
  /usr/bin/mini-dinstall:1241: DeprecationWarning: getName() is deprecated, get
the name attribute instead
self._logger.info('Thread "%s" exiting' % self.getName())

also the subsequent upload by

  $ dput local 

cause such warnings, partly for other line numbers

  Uploading to local (via local to localhost):
  Successfully uploaded packages.
  /usr/bin/mini-dinstall:523: DeprecationWarning: getName() is deprecated, get
the name attribute instead
self._logger.info('Created new installer thread (%s)' % self.getName())
  /usr/bin/mini-dinstall:593: DeprecationWarning: getName() is deprecated, get
the name attribute instead
logger.debug('Installing %s in archive %s' % (changefilename,
self._archivemap[dist][1].getName()))
  /usr/bin/mini-dinstall:600: DeprecationWarning: getName() is deprecated, get
the name attribute instead
logger.debug('Notifying archive %s of change' %
self._archivemap[dist][1].getName())
  /usr/bin/mini-dinstall:1624: DeprecationWarning: getName() is deprecated, get
the name attribute instead
logger.debug('Starting archive %s' % archive.getName())
  /usr/bin/mini-dinstall:1228: DeprecationWarning: getName() is deprecated, get
the name attribute instead
self._logger.info('Created new thread (%s) for archive indexer %s' %
(self.getName(), self._name))
  /usr/bin/mini-dinstall:1632: DeprecationWarning: getName() is deprecated, get
the name attribute instead
logger.debug('Waiting for archive %s to finish' % archive.getName())
  /usr/bin/mini-dinstall:1241: DeprecationWarning: getName() is deprecated, get
the name attribute instead
self._logger.info('Thread "%s" exiting' % self.getName())

Looks like the python code needs an update.


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

Kernel: Linux 6.5.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 mini-dinstall depends on:
ii  apt-utils2.7.6
ii  python3  3.11.4-5+b1
ii  python3-apt  2.6.0

Versions of packages mini-dinstall recommends:
ii  gpgv  2.2.40-1.1

Versions of packages mini-dinstall suggests:
ii  debian-keyring  2023.09.24

-- no debconf information

Bug#840955: Status of ITP/RFP courier-zdkimfilter

[Markus Wanner]

Hello Helge,

On 11/1/23 10:18, Helge Kreutzmann wrote:

I haven't done anything besides doing a testbuild. Before proceeding
further I wanted to inquire about the status of your work on this
package, so I don't waste time redoing Debian integration.


thanks for reaching out. Unfortunately, I can only tell you that I plan 
to abandon packaging of courier altogether. It's been a struggle for me 
to keep up the community work recently and many people were far less 
than appreciative.


Noticing that upstream now runs their own packaging convinced me it's 
not worth for me to keep maintaining this for Debian proper.


Sorry for the rather bad news.

Markus

Bug#1054376: liborcus: FTBFS on hppa - segmentation fault in orcus-test-xml-mapped

[Rene Engelhard]

Hi,

Am 01.11.23 um 16:37 schrieb John David Anglin:

The attached change fixes orcus_test_xml_mapped test on hppa hardware:
https://buildd.debian.org/status/fetch.php?pkg=liborcus=hppa=0.17.2-4=1698851675=0


Erm? Please don't tell me you apply stuff on packages extra to what's in 
the archive proper and reuse the same version number?


That's a recipe for deasaster and confusion.


Anyways, it's fixed upstream so will be in 0.19.2 whenever it will be 
released. (0.17.x in sid is dead and only will get updates for 
transitions or release-critical stuff, which is one definitely is not)


Regards,


Rene

Bug#1055246: kde-config-plymouth: Does not appear in system settings

[Luke W Faraone]

Package: kde-config-plymouth
Version: 5.27.8-1
Severity: normal
X-Debbugs-Cc: lfara...@debian.org

Despite having Plymouth installed, no "Boot Splash Settings" panel appears in
KCM, contrary to what is shown in https://screenshots.debian.net/package/kde-
config-plymouth


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

Kernel: Linux 6.5.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
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 kde-config-plymouth depends on:
ii  kio  5.107.0-1
ii  libc62.37-12
ii  libkf5archive5   5.107.0-1
ii  libkf5authcore5  5.107.0-1
ii  libkf5configcore55.107.0-1
ii  libkf5coreaddons55.107.0-1
ii  libkf5i18n5  5.107.0-1+b1
ii  libkf5kiocore5   5.107.0-1
ii  libkf5newstuffcore5  5.107.0-1
ii  libkf5quickaddons5   5.107.0-1
ii  libqt5core5a 5.15.10+dfsg-4
ii  libqt5gui5   5.15.10+dfsg-4
ii  libqt5qml5   5.15.10+dfsg-2
ii  libstdc++6   13.2.0-5
ii  plasma-framework 5.107.0-1
ii  qml-module-org-kde-kquickcontrolsaddons  5.107.0-1
ii  systemsettings   4:5.27.8-1

kde-config-plymouth recommends no packages.

kde-config-plymouth suggests no packages.

-- no debconf information

Bug#1052052: ping?

[Rene Engelhard]

Hi,

I just saw that you uploaded parlatype fixing its RC bug [1]

Can you fix this bug, too? I just uploaded the last LibreOffice of 7.5.x 
series ever to unstable. I think we should move to LibreOffice 7.6 asap, 
especially since 24.2 is around the corner too and we need experimental 
to test that one...


Regards,

Rene

[1] for me unfortunately, the autorm would have made it possible to just 
upload it straight ahead and just bump this bug to serious ;-)

Bug#1055245: RFS: tint2/17.0.1-1.1 [NMU] [RC] -- lightweight taskbar

[Mateusz Łukasik]

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name : tint2
   Version  : 17.0.1-1.1
   Upstream contact : [fill in name and email of upstream]
 * URL  :https://gitlab.com/o9000/tint2/
 * License  : GPL-2, GPL-2+
 * Vcs  :https://salsa.debian.org/debian/tint2
   Section  : x11

The source builds the following binary packages:

  tint2 - lightweight taskbar

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

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

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

  dget 
-xhttps://mentors.debian.net/debian/pool/main/t/tint2/tint2_17.0.1-1.1.dsc

Changes since the last upload:

 tint2 (17.0.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch for fix crash with glib 2.76. (Closes: #1054261) (LP: #2015052)

Regards,
--
  Mateusz Łukasik

Bug#1055244: linux-image-amd64: Please enable CONFIG_MTK_T7XX for the Intel/Mediatek FM350-GL 5G modem

[Martin Sofaru]

Source: linux
Version: linux/6.5.0-3
Severity: wishlist
X-Debbugs-Cc: debian-b...@fhloston.org

Dear Maintainer,

please set CONFIG_MTK_T7XX=m to build the mtk_t7xx kernel module.

This module is necessary to use some 5G modems built into newer Lenovo Laptops 
like X1 Yoga Gen7/Gen8 and X1 Carbon Gen10/Gen11.

As long as this [1] patch is not merged upstream, it might be sensible to also 
include this. 

The modem itself also needs some kind of FCC unlock which can be found here [2].

Thank you

Martin


[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/patch/?id=ba2274dcfda859b8a27193e68ad37bfe4da28ddc
[2] 
https://pcsupport.lenovo.com/us/en/downloads/ds563599-fibocom-wireless-wan-l860-gl-16-fcc-unlock-and-sar-config-tool-for-linux-thinkpad




-- System Information:
Debian Release: trixie/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en_US:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1055242: pkg-config files have empty Version

[Jelmer Vernooij]

Package: libsvn-dev
Version: 1.14.2-4+b3
Severity: normal

The pkg-config files for the libsvn libraries have an empty Version string. 
E.g.:

...
Name: libsvn_client
Description: Subversion Client Library
Version:
Requires: apr-util-1, apr-1
Requires.private: libsvn_wc, libsvn_ra, libsvn_delta, libsvn_diff, libsvn_subr
...

(in /usr/lib/x86_64-linux-gnu/pkgconfig/libsvn_client.pc)

This makes it hard to e.g. check for what version is present.

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

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

Versions of packages libsvn-dev depends on:
ii  libapr1-dev  1.7.2-3
ii  libaprutil1-dev  1.6.3-1
ii  libsvn1  1.14.2-4+b3

libsvn-dev recommends no packages.

Versions of packages libsvn-dev suggests:
pn  libserf-dev  
pn  libsvn-doc   
ii  zlib1g-dev   1:1.2.13.dfsg-3

-- debconf-show failed

Bug#1055243: libinput10: invalid URL in Xorg logs due to incorrect HTTP_DOC_LINK value

[Vincent Lefevre]

Package: libinput10
Version: 1.22.1-1
Severity: minor

In my Xorg logs (e.g. Keyb/var/log/Xorg.0.log), I get messages like

[ 10491.518] (EE) event14 - VEN_04F3:00 04F3:311C Touchpad: kernel bug: Touch 
jump detected and discarded.
See 
https://wayland.freedesktop.org/libinput/doc/1.22.1/touchpad-jumping-cursors.html
 for details

But when I want to open this URL for details, I get a 404 error.

It seems that the value of the HTTP_DOC_LINK macro is incorrect:
at https://wayland.freedesktop.org/libinput/doc/ I can see various
directories such as "1.22.0" and "1.23.0", but not the "1.22.1" one.

-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (900, 'stable-updates'), (900, 'stable-security'), (900, 
'stable'), (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-13-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=POSIX, LC_CTYPE=C.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 libinput10 depends on:
ii  libc6 2.36-9+deb12u3
ii  libevdev2 1.13.0+dfsg-1
ii  libinput-bin  1.22.1-1
ii  libmtdev1 1.1.6-1
ii  libudev1  252.17-1~deb12u1
ii  libwacom9 2.6.0-1

libinput10 recommends no packages.

libinput10 suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1055241: bookworm-pu: package crun/1.8.1-1+deb12u1 (bookworm regression)

[Faidon Liambotis]

Package: release.debian.org
Severity: important
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: c...@packages.debian.org
Control: affects -1 + src:crun

[ Reason ]
Linux v6.6 blocked the mode change of symlinks, with commit
5d1f903f75a80daa4dfb3d84e114ec8ecbf29956 ("attr: block mode changes of
symlinks").

This was in turn backported to v6.1.55, with
6a84939cc7dd6f970c2621ded82c4d9ea0068b1b, and is part of src:linux
6.1.55-1, which is the version currently in bookworm.

This breaks crun 1.8.1, as found in bookworm, when running containers
with systemd as the init system.

The issue has been addressed upstream with commit
57262a2710c83fa08767f0ce3ba7a80993515bb2 ("ignore ENOTSUP when chmod a
symlink"), as well as 14afa8a46e2e83608a3a219402bce8ea8d071192 ("utils:
fix ignore ENOTSUP when chmod a symlink"), both part of crun 1.9.1.

[ Impact ]
Users are unable to start containers running systemd as their init
system. For example this now fails:
  podman run --rm -d docker.io/jrei/systemd-debian:12

[ Tests ]
The manual test as mentioned above, as well as non-systemd images that
continue to work, like:
  podman run --rm -it debian:sid

(Sadly we don't have any automated tests. crun in unstable now has
autopkgtests, but even these have the isolation-machine restriction and
are thus inoperable in Debian's CI, so I've elected to not backport them
here.)

[ Risks ]
The code is pretty trivial, I think, and has been part of upstream since
v1.9.1, released in September 26. trixie has v1.11, and sid has v1.11.1.

No alternatives that I know of.

[ 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 (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
One change, effectively: to ignore ENOTSUP when chmod'ing a symlink,
/run/shm in the most popular broken case.

[ Other info ]
This has been reported by multiple users, cf. #1053821.

Given this constitutes a regression introduced by another package's
stable update, I consider this is an urgent issue, and ask for RMs to
copy this to stable-updates.

Thanks,
Faidon
diff -Nru crun-1.8.1/debian/changelog crun-1.8.1/debian/changelog
--- crun-1.8.1/debian/changelog 2023-02-27 22:01:38.0 +0200
+++ crun-1.8.1/debian/changelog 2023-11-02 18:52:46.0 +0200
@@ -1,3 +1,13 @@
+crun (1.8.1-1+deb12u1) bookworm; urgency=medium
+
+  * Backport two commits from upstream ("ignore ENOTSUP when chmod a
+symlink"), that restore containers with systemd as their init system, when
+running under Linux >= v6.6 and >= v6.1.55, i.e. bookworm's current stable
+kernel. (Closes: #1053821)
+  * Move myself to Maintainer, and Dmitry to Uploaders.
+
+ -- Faidon Liambotis   Thu, 02 Nov 2023 18:52:46 +0200
+
 crun (1.8.1-1) unstable; urgency=medium
 
   * New bugfix upstream release.
diff -Nru crun-1.8.1/debian/control crun-1.8.1/debian/control
--- crun-1.8.1/debian/control   2023-02-27 22:01:38.0 +0200
+++ crun-1.8.1/debian/control   2023-11-02 18:52:46.0 +0200
@@ -2,9 +2,9 @@
 Section: admin
 Priority: optional
 Standards-Version: 4.6.2
-Maintainer: Dmitry Smirnov 
+Maintainer: Faidon Liambotis 
 Uploaders:
- Faidon Liambotis ,
+ Dmitry Smirnov ,
  Reinhard Tartler ,
 Build-Depends:
  automake,
diff -Nru crun-1.8.1/debian/patches/series crun-1.8.1/debian/patches/series
--- crun-1.8.1/debian/patches/series1970-01-01 02:00:00.0 +0200
+++ crun-1.8.1/debian/patches/series2023-11-02 18:52:46.0 +0200
@@ -0,0 +1,2 @@
+utils-ignore-ENOTSUP-when-chmod-a-symlink.patch
+utils-fix-ignore-ENOTSUP-when-chmod-a-symlink.patch
diff -Nru 
crun-1.8.1/debian/patches/utils-fix-ignore-ENOTSUP-when-chmod-a-symlink.patch 
crun-1.8.1/debian/patches/utils-fix-ignore-ENOTSUP-when-chmod-a-symlink.patch
--- 
crun-1.8.1/debian/patches/utils-fix-ignore-ENOTSUP-when-chmod-a-symlink.patch   
1970-01-01 02:00:00.0 +0200
+++ 
crun-1.8.1/debian/patches/utils-fix-ignore-ENOTSUP-when-chmod-a-symlink.patch   
2023-11-02 18:52:46.0 +0200
@@ -0,0 +1,36 @@
+From 60296f112fddc74f4926f8ca6f6e1ef7a61ef5b9 Mon Sep 17 00:00:00 2001
+From: Giuseppe Scrivano 
+Date: Tue, 26 Sep 2023 11:51:19 +0200
+Subject: [PATCH] utils: fix ignore ENOTSUP when chmod a symlink
+
+when ENOTSUP is encountered we must continue copying the other files,
+not doing an early return.
+
+commit 57262a2710c83fa08767f0ce3ba7a80993515bb2 introduced the
+regression with the Podman CI.
+
+Signed-off-by: Giuseppe Scrivano 
+
+Origin: upstream, 
https://github.com/containers/crun/commit/14afa8a46e2e83608a3a219402bce8ea8d071192
+Bug: https://github.com/containers/crun/issues/1308
+Bug-Debian: https://bugs.debian.org/1053821
+---
+ src/libcrun/utils.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/libcrun/utils.c b/src/libcrun/utils.c
+index e5a82be..74bcf62 100644
+--- a/src/libcrun/utils.c
 

Bug#1055240: apt-listchanges: [INTL:fr] French translation for the apt-listchanges man page

[Jean-Pierre Giraud]

Package: apt-listchanges
Severity: wishlist
Tags: patch l10n

Hi!

Please find attached the french translation for the apt-listchanges man
page, proofread by the debian-l10n-french mailing list contributors.

This file should be put as doc/po/fr.po in your package build tree.

Kind Regards

jipege


fr.po.gz
Description: application/gzip


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

Bug#958692: node-matrix-js-sdk: Remove dependency to node-request

[Pirate Praveen]

On 2/11/23 10:27 PM, Hubert Chathi wrote:

On Sun, 29 Oct 2023 22:43:55 +0530, Praveen Arimbrathodiyil 
 said:


On Fri, 24 Apr 2020 13:52:39 +0200 y...@debian.org wrote:

Upstream has deprecated node-request:
https://github.com/request/request/issues/3142 It can be replaced by
node-got



Hi Jonas, Hubert,



Are you planning to update matrix-js-sdk? We'd like to remove
deprecated node-request from the archive and this package is a
blocker.


I don't currently have time to update matrix-js-sdk.  Feel free to
remove it from testing so that it doesn't block anything else.  I can
always upload a new version later.



This is already not in testing for 525 days. We can't remove a package 
from the archive if any package (build) depends on it.

Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

[Diederik de Haas]

Control: found -1 6.1.37-1

On Thursday, 2 November 2023 18:03:25 CET Jose M Calhariz wrote:
> On Thu, Nov 02, 2023 at 03:37:39PM +0100, Diederik de Haas wrote:
> > On Wednesday, 5 July 2023 19:07:15 CET Jose M Calhariz wrote:
> > > Package: src:linux
> > > Version: 6.1.27-1
> > 
> > Can you try with the latest version in the 6.1.x series to see if the
> > problem is still there?
> 
> As I need to setup ASAP the servers in production I do not know if I
> have time in the next days.  It works with backports kernels.

No problem.

> The latest kernels I tested were:
> Fail : Linux afs31 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.37-1
> (2023-07-03) x86_64 GNU/Linux

Ok. Please test (when you have time) 6.1.55-1.
Also verify if it's also present in 6.1~rc3-1~exp1 to make sure it's present 
in the whole 6.1 series.
Use https://snapshot.debian.org/binary/linux-image-amd64/ to get it/them.

If the bug is NOT present in either the latest or the first, then try other 
versions till you find the last one that work and the first one that fails.

> OK : Linux afs31 6.4.0-0.deb12.2-amd64 #1 SMP PREEMPT_DYNAMIC Debian
> 6.4.4-3~bpo12+1 (2023-08-08) x86_64 GNU/Linux

It was fixed in 6.3.7-1, so it was expected that a later versions also works.
But let's ignore bpo as it likely won't provide useful data points.

Unfortunately there isn't a 6.2 kernel uploaded to the Debian archive and thus 
not available on snapshot.d.o, but testing 6.3.1-1~exp1 should be useful.

> The bug is present on Debian v11 too.  So is an old bug with fixes on
> kernel 6.2 rc something.

I'd recommend to focus first on the 6.1 series for now.
If at a later point testing with 5.10 may be useful, we can do that then.

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

Bug#1055239: apt-listchanges: [INTL:fr] French program translation

[Jean-Pierre Giraud]

Package: apt-listchanges
Severity: wishlist
Tags: patch l10n

Hi!

Please find attached the french translation for the apt-lischange
program, proofread by the debian-l10n-french mailing list contributors.

This file should be put as /po/fr.po in your package build tree.

Kind Regards

jipege


fr.po.gz
Description: application/gzip


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

Bug#1055225: libpango1.0-0: Please drop transitional package

[Patrice Duroux]

Added a section here:
https://wiki.debian.org/DebianRepository/Unofficial
Do not hesitate to modify it.

Bug#1054323: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected

[Paul Gevers]

Hi,

On 02-11-2023 15:13, Andreas Tille wrote:

There is probably one remaining problem.  As per file R/zzz.R[2] the
function checkMatrixPackageVersion verifies that TMB is running always
with the Matrix version it was built against.


Well, I suggested before to just patch that check out. Is it really 
doing any good? If the test suite is remotely well done, it should catch 
the case where rmatrix breaks the package, while enabling running it 
against any version that works.



Do you see some automatic
method to approach this which is better than simply waiting for a CI
test to fail (which should happen once a r-cran-matrix package of a new
Matrix version is uploaded)?
Well, if you get the version tightly recorded, the migration software 
will refuse to migrate r-cran-matrix because it would break the version 
in testing. No CI is needed for that. But tight version relations are a 
pain, i.e. they limit apt in finding upgrade orders, so if too many 
packages do that, it might prevent people from upgrading their system.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1053821: bookworm patch?

[Faidon Liambotis]

Control: severity -1 important 

On Thu, Nov 02, 2023 at 10:43:46AM -0500, Jesse Hathaway wrote:
> Since this bug affects the current version in bookworm, v1.8.1, would
> there be a possibility of adding the upstream patch to bookworm's
> version? I tested applying the patches atop v1.8.1 and they apply
> cleanly, and fix the issue as well.
> 
> git checkout -b bookworm 1.8.1
> git cherry-pick 57262a2710c83fa08767f0ce3ba7a80993515bb2
> git cherry-pick 14afa8a46e2e83608a3a219402bce8ea8d071192

Despite Austin's description noting this, I had read the bug a bit in
haste and thought this was only affecting crun 1.8.1 + Linux >= 6.6 (as
crun's commit message mentioned). In other words, a combination of (crun
from bookworm) + (Linux from sid), which, while not great, wasn't that
big of an issue.

However, after discussing this further with Jesse, I realized that the
kernel commit in question (5d1f903f75a80daa4dfb3d84e114ec8ecbf29956,
"attr: block mode changes of symlinks") has been backported as a stable
upate to 6.1.55 (6a84939cc7dd6f970c2621ded82c4d9ea0068b1b), in turn part
of src:linux 6.1.55-1, currently in bookworm.

This means that bookworm's crun, combined with bookworm's current
kernel, is broken when running containers with systemd as the init
system.

A simple test case is:
  podman run --rm -d docker.io/jrei/systemd-debian:12

I'm going to prepare a stable update backporting these two commits,
hopefully resolving this incompatibility.

Thanks all!
Faidon

Bug#1055238: pinentry: Please add bootstrapping profile

[Samuel Thibault]

Source: pinentry
Severity: normal
Tags: patch

Hello,

When bootstrapping a new port, buildds needs to use gnupg to sign
packages, which depends on gpg-agent, which depends on pinentry. But
pinentry build-deps on qt, gtk etc. which we don't really want to
bootstrap by hand. The attached patch adds build profiles that can be
used to easily build pinentry-tty, then install buildds, and let them
build the rest.

(I had to switch the no-secret/secret configuration, otherwise the
pinentry.info file doesn't get found in the nogtk profile)

Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- debian/control.original 2023-11-02 18:12:13.454799542 +0100
+++ debian/control  2023-11-02 18:12:30.682864897 +0100
@@ -7,18 +7,18 @@
 Build-Depends:
  debhelper-compat (= 13),
  libassuan-dev (>= 2.1.0),
- libfltk1.3-dev,
- libgcr-3-dev,
- libglib2.0-dev (>= 2.15.5),
+ libfltk1.3-dev ,
+ libgcr-3-dev ,
+ libglib2.0-dev (>= 2.15.5) ,
  libgpg-error-dev (>= 1.16),
- libgtk2.0-dev (>= 2.4.0),
- libncurses5-dev,
- libncursesw5-dev,
- libqt5waylandclient5-dev,
- libsecret-1-dev,
+ libgtk2.0-dev (>= 2.4.0) ,
+ libncurses5-dev ,
+ libncursesw5-dev ,
+ libqt5waylandclient5-dev ,
+ libsecret-1-dev ,
  m4,
  pkg-config,
- qtbase5-dev,
+ qtbase5-dev ,
  texinfo,
 Standards-Version: 4.6.1
 Homepage: https://www.gnupg.org/related_software/pinentry/
@@ -29,6 +29,7 @@
 Package: pinentry-curses
 Architecture: any
 Multi-Arch: foreign
+Build-Profiles: 
 Depends:
  ${misc:Depends},
  ${shlibs:Depends},
@@ -87,6 +88,7 @@
 Package: pinentry-qt
 Architecture: any
 Multi-Arch: foreign
+Build-Profiles: 
 Depends:
  ${misc:Depends},
  ${shlibs:Depends},
@@ -111,6 +113,7 @@
 
 Package: pinentry-gtk2
 Architecture: any
+Build-Profiles: 
 Depends:
  ${misc:Depends},
  ${shlibs:Depends},
@@ -139,6 +142,7 @@
 Package: pinentry-fltk
 Architecture: any
 Multi-Arch: foreign
+Build-Profiles: 
 Depends:
  ${misc:Depends},
  ${shlibs:Depends},
@@ -167,6 +171,7 @@
 Package: pinentry-gnome3
 Architecture: any
 Multi-Arch: foreign
+Build-Profiles: 
 Depends:
  gcr,
  ${misc:Depends},
--- debian/rules.original   2023-11-02 18:12:18.838819816 +0100
+++ debian/rules2023-11-02 18:14:39.283391832 +0100
@@ -2,34 +2,60 @@
 
 QT_SELECT = qt5
 export QT_SELECT
-SHARED_CONFIGS = --disable-rpath --without-libcap --disable-pinentry-emacs 
--disable-inside-emacs --enable-fallback-curses --disable-pinentry-tqt 
--disable-pinentry-efl
+SHARED_CONFIGS = --disable-rpath --without-libcap --disable-pinentry-emacs 
--disable-inside-emacs --disable-pinentry-tqt --disable-pinentry-efl
 export DEB_BUILD_MAINT_OPTIONS = hardening=+bindnow
 
+ifeq (,$(filter pkg.pinentry.nocurses,$(DEB_BUILD_PROFILES)))
+ENABLE_CURSES = --enable-pinentry-curses
+FALLBACK_CURSES = --enable-fallback-curses 
+else
+ENABLE_CURSES = --disable-pinentry-curses
+FALLBACK_CURSES = --disable-fallback-curses 
+endif
+
+ifeq (,$(filter pkg.pinentry.noqt,$(DEB_BUILD_PROFILES)))
+ENABLE_QT = --enable-pinentry-qt
+else
+ENABLE_QT = --disable-pinentry-qt
+endif
+
+ifeq (,$(filter pkg.pinentry.nofltk,$(DEB_BUILD_PROFILES)))
+ENABLE_FLTK = --enable-pinentry-fltk
+else
+ENABLE_FLTK = --disable-pinentry-fltk
+endif
+
 %:
dh $@
 
 override_dh_auto_configure:
-   dh_auto_configure --builddirectory=build-no-libsecret -- \
+   dh_auto_configure -- \
$(SHARED_CONFIGS) --disable-libsecret \
--enable-pinentry-tty \
-   --enable-pinentry-curses \
-   --enable-pinentry-qt \
+   $(ENABLE_CURSES) \
+   $(FALLBACK_CURSES) \
+   $(ENABLE_QT) \
--disable-pinentry-qt4 \
-   --enable-pinentry-fltk \
+   $(ENABLE_FLTK) \
--disable-pinentry-gtk2 \
--disable-pinentry-gnome3
-   dh_auto_configure -- $(SHARED_CONFIGS) \
+ifeq (,$(filter pkg.pinentry.nogtk,$(DEB_BUILD_PROFILES)))
+   dh_auto_configure --builddirectory=build-libsecret -- $(SHARED_CONFIGS) 
\

Bug#1055233: Several math features break in new version

[Hilmar Preuße]

On 11/2/23 16:17, Kumar Appaiah wrote:

Hello Kumar,


I've inserted a begin-math/end-math symbol since I think you left one out.
Proceed, with fingers crossed.
mtx-context | fatal error: return code: 1


Please let me know what I can do to help. I am downgrading temporarily though.



I don't use ConTeXt at all, hence I can't tell, if this is function as 
designed or a bug. Would you be so kind to contact the people of the NTG 
Mailing list (ntg-cont...@ntg.nl)? Maybe they have a solution for you or 
at least clarify if this is a bug or not.


Thanks,
  Hilmar
--
Testmail



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055221: qemu-system is not compiled with pipewire audio support

[Francesco C]

> Personally I don't see value in pw support in qemu for now.

I didn't even know that qemu has introduced pipewire support in the
latest version.
I discovered it while trying to find an alternative for the audiodev
driver because of the issue I've experienced :

- pulse+vga , pulse+virgl , pulse without graphics -> audio stream
loses samples ( probably because of my low end hardware )

- the same with sdl

- alsa doesn't work for any reason

- dbus,jack not viable

- spice works perfectly but I have to use qxl driver for graphics that
suffers of a nasty bug on the host side that leads to an unrecoverable
crash of the guest graphics since a couple of months ("failed to
allocate VRAM BO"
:https://groups.google.com/g/linux.kernel/c/w7Ee-j9YonY ).

- pulse+spice the same as above

That's it.

Regards.

Bug#1055237: does not conform to the standards for library packaging

[Pierre Gruet]

Source: catch2
Version: 3.4.0-1
Severity: serious

Dear Maintainer,

Recently catch2/3.4.0-1 was uploaded to Debian, great. Yet the binary packages
do not follow the layout for libraries that is described in Policy Section 8.
For instance I think we should provide a shared library and if there are enough
reasons not to do so (see Policy 8.3), at least the binary package name should
be changed to libcatch2-dev.

Also this is not a header-only library anymore, the description of the package
should be changed.

As a side note, the upload of the major version 3.x came out with many breaking
interface changes giving rise to RC bugs in e.g. genomicsdb, netgen, spdlog,
therion just to name a few, also to failing autopkgtests in many rdeps. I would
have been more comfortable with such a huge version change being advertised and
more prepared, with some kind of a library transition process for instance.

In any case, thanks for your work on catch2,

Best regards,

-- 
Pierre

Bug#958692: node-matrix-js-sdk: Remove dependency to node-request

[Hubert Chathi]

On Sun, 29 Oct 2023 22:43:55 +0530, Praveen Arimbrathodiyil 
 said:

> On Fri, 24 Apr 2020 13:52:39 +0200 y...@debian.org wrote:
>> Upstream has deprecated node-request:
>> https://github.com/request/request/issues/3142 It can be replaced by
>> node-got

> Hi Jonas, Hubert,

> Are you planning to update matrix-js-sdk? We'd like to remove
> deprecated node-request from the archive and this package is a
> blocker.

I don't currently have time to update matrix-js-sdk.  Feel free to
remove it from testing so that it doesn't block anything else.  I can
always upload a new version later.

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

[Jose M Calhariz]

On Thu, Nov 02, 2023 at 03:37:39PM +0100, Diederik de Haas wrote:
> Control: tag -1 moreinfo
> 
> On Wednesday, 5 July 2023 19:07:15 CET Jose M Calhariz wrote:
> > Package: src:linux
> > Version: 6.1.27-1
> 
> Can you try with the latest version in the 6.1.x series to see if the problem 
> is still there?

As I need to setup ASAP the servers in production I do not know if I
have time in the next days.  It works with backports kernels.

The latest kernels I tested were:

Fail : Linux afs31 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.37-1 
(2023-07-03) x86_64 GNU/Linux

OK : Linux afs31 6.4.0-0.deb12.2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.4.4-3~bpo12+1 (2023-08-08) x86_64 GNU/Linux



> 
> > On this hardware I am chasing a data corruption for several months on
> > Debian V11 and Debian v12.  Now that I was pointed that linux kernel
> > had some problems with XFS solved in later 6.3 kernel I can reproduce
> > the problem.
> > 
> > It seams the problem went away with current Debian testing kernel:
> > 
> > ii  linux-image-6.3.0-1-amd646.3.7-1  amd64Linux 6.3
> > for 64-bit PCs (signed)
> > 
> > Is there anyone willing to backport the XFS fixes into
> > linux-image-6.1.0 and linux-image-5.10.0?
> 
> If the problem is still present in the latest 6.1 kernel, then you need to 
> find 
> out which patch(es) actually fix the problem.
> The easiest way to start with that is to find the last kernel which exhibits 
> the issue and then the first one where it is fixed.
> https://snapshot.debian.org/binary/linux-image-amd64/ should help
> with that.

The bug is present on Debian v11 too.  So is an old bug with fixes on
kernel 6.2 rc something.

> 
> When the range has been narrowed, a `git bisect` should identify the specific 
> commit(s) which fixes the issue.
> https://wiki.debian.org/DebianKernel/GitBisect should help with that
> 
> When that/those have been identified, it should be reported to the upstream 
> kernel so that they can incorporate those fixes in their LTS kernel(s) which 
> Debian then will pick up automatically.
> 
> HTH



-- 
--
A vida feliz, meu Deus, consiste em nos alegrarmos em vos,
de vos e por vos


signature.asc
Description: PGP signature

Bug#932491: python3-apt: segfault reading from lzma stream

[Julian Andres Klode]

Control: clone -1 -2
Control: retitle -2 python3-apt: add support for non-gzip compressed file 
objects
Control: severity -2 wishlist

On Thu, Nov 02, 2023 at 01:18:23PM +0100, Cyril Brulebois wrote:
> Cyril Brulebois  (2023-11-02):
> > Today I had a few more minutes to spend on this, so here's a little
> > debugging session. My main system is still bullseye, but the same tests
> > in a bookworm chroots fail the same way.
> 
> “But maybe it's a bug in the lzma library?” one might ask.
> 
> Adding a bzip2 test between gzip and lzma leads to the following, again
> on both bullseye and bookworm (after creating a Test.bz2/Packages.bz2
> from one of the other files):
> 
> With bug-932491-aa.py (bug-932491-a.py + bzip2):
> 
> $ ./bug-932491-aa.py Test
> gz == bz: True
> gz == xz: True
> gz: section 1 size: 29
> gz: section 1 keys: ['Package', 'Desc']
> gz: section 2 size: 47
> gz: section 2 keys: ['Package', 'Desc']
> Traceback (most recent call last):
>   File "/home/kibi/tmp/./bug-932491-c.py", line 37, in 
> tf_bz.step()
> apt_pkg.Error: E:Unable to parse package file  (1)
> 
> $ ./bug-932491-aa.py Packages
> gz == bz: True
> gz == xz: True
> gz: section 1 size: 1281
> gz: section 1 keys: ['Package', 'Version', 'Installed-Size', 
> 'Maintainer', 'Architecture', 'Depends', 'Pre-Depends', 'Description', 
> 'Homepage', 'Description-md5', 'Tag', 'Section', 'Priority', 'Filename', 
> 'Size', 'MD5sum', 'SHA256']
> gz: section 2 size: 585
> gz: section 2 keys: ['Package', 'Version', 'Installed-Size', 
> 'Maintainer', 'Architecture', 'Pre-Depends', 'Suggests', 'Description', 
> 'Homepage', 'Description-md5', 'Tag', 'Section', 'Priority', 'Filename', 
> 'Size', 'MD5sum', 'SHA256']
> bz: section 1 size: 1410
> Segmentation fault
> 
> With bug-932491-bb.py (bug-932491-b.py + bzip2):
> 
> $ ./bug-932491-bb.py Test
> gz packages: 2
> Traceback (most recent call last):
>   File "/home/kibi/tmp/./bug-932491-bb.py", line 26, in 
> for stanza in tf_bz:
> apt_pkg.Error: E:Unable to parse package file  (1)
> 
> $ ./bug-932491-bb.py Packages
> gz packages: 50771
> Traceback (most recent call last):
>   File "/home/kibi/tmp/./bug-932491-bb.py", line 27, in 
> bz_packages.append(stanza['Package'])
>~~^^^
> KeyError: 'Package'
> 
> 
> It looks like we might be getting chunks of different sizes depending on
> the underlying file objects, and some buffering/seeking code is buggy on
> the apt_pkg side?

You are literally just fuzzing the tagfile parser with compressed
streams, there is no decompression going on.

We don't talk to the the file-like object you pass to at all, we just
call it's fileno() method to get the underlying file descriptor, and
then apt's gzip support reads from that, and that works automagically
because zlib just passes through uncompressed content.

If you want it to automatically guess the compressor, you can do that
by passing a filename with the right file extension.

For existing open files, the right way to approach this arguably is
o provide apt_pkg.FileFd bindings to the FileFd class such that you
can specify a decompressor, and then parse the FileFd to TagFile.

But I think this is a different issue than the segfault because we
probably still should not be segfaulting on fuzzing with random
data like you do, we probably ought to error out at some point.


-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en


signature.asc
Description: PGP signature

Bug#1055235: nmu: libgnatcoll_24.1.20230921-2

[Nicolas Boulenguez]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: libgnatc...@packages.debian.org
Control: affects -1 + src:libgnatcoll

Hello.

This follows the NMU requested at
  https://bugs.debian.org/1055063
  nmu: gprbuild_2024.1.20231009-2 in experimental
The NMU did fix the hash sum in the libgnatprj-dev-HASH virtual
packages provided by libgnatprj-dev.

Now, the exact same issue affects a reverse dependency:
  src:libgnatcoll libgnatcoll-dev libgnatcoll-dev-HASH.
Please also fix this one with a similar NMU.

There should be no more surprise. The only remaining affected package
is libgnatcoll-bindings, and it requires a full upload anyways (in
order to increase the shared object versions).

nmu libgnatcoll_24.1.20230921-2 . amd64 . experimental . -m "nmu: 
libgnatcoll_24.1.20230921-2 in experimental"

Bug#1055205: closed by Vincent Blut (Re: Bug#1055205: chrony: SysV problems after upgrade)

[Richard Lucassen]

On Thu, 02 Nov 2023 12:27:05 +
"Debian Bug Tracking System"  wrote:

Hello Vincent,

Ok, thnx for your explanation! I changed it to disable (and
indeed there is only a K link) and I'll see at the next upgrade.

Richard.

> This is an automatic notification regarding your Bug report
> which was filed against the chrony package:
> 
> #1055205: chrony: SysV problems after upgrade
> 
> It has been closed by Vincent Blut .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Vincent Blut
>  by replying to this email.
> 
> 


-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+

Bug#1055005: [Pkg-pascal-devel] Bug#1055005: lazarus-ide-2.2: gdb 13 dynamic array crash (regression: gdb 10 working)

[Peter B]

On 29/10/2023 08:27, Jonas Bechtel wrote:

Following conditions have to be met to reproduce the problem:

* The line must be in an extra unit (not application form class unit)
* gdb 13 must be installed (gdb 10 does not crash)


Given that the crash only occurs with gdb 13 and not with gdb 10,
surely this is a bug in gdb, not with the Lazarus IDE?

gdb is pretty flakey...
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=gdb;dist=unstable


Regards,
Peter

Bug#1051418: Info received (obs-studio: clicking on an xcomposite window source makes obs segfault)

[Brian Bostwick]

On Mon, 23 Oct 2023 22:20:04 + (UTC) Michael Neilly 
wrote:
> Sending in plain text so it is readable:
>
>
> I'm seeing the same bug in the latest Debian testing updated this
> morning. Specifically, if I have the following github page open in my
> browser clicking the xcomposite window source cases a seg fault as
> reported.
>
>
> Â  Â  https://github.com/pjreddie/darknet/issues/553
>
>
> This results in a window name of
>
>
>     "Error on make: 'cuda_runtime.h: No such file or directory' ·
Issue #553 · pjreddie/darknet - Brave"
>
>
> In xcompcap_props(), the name_lower variable has zero values in the
> struct which is then pushed to window_strings.array. I can't currently
> step into dstr_to_lower().
>
>
> The following shows the array entry in window_strings.array:
>
>
> Â  Â  $18 = {
> Â  Â  name_lower = {array = 0x0, len = 0, capacity = 0},
> Â  Â  name = {
> Â  Â  Â  Â  array = 0x570b88e0 "Error on make: 'cuda_runtime.h: No
such file or directory' · Issue #553 · pjreddie/darknet - Brave",
> Â  Â  Â  Â  len = 100,
> Â  Â  Â  Â  capacity = 101
> Â  Â  },
> Â  Â  desc = {
> Â  Â  Â  Â  array = 0x55c24560 "54525967\r\nError on make:
'cuda_runtime.h: No such file or directory' · Issue #553 ·
pjreddie/darknet - Brave\r\nbrave-browser",
> Â  Â  Â  Â  len = 125,
> Â  Â  Â  Â  capacity = 126
> Â  Â  }
> Â  Â  }
>
>
> The following is the gdb backtrace with frame 11 being the frame where
> the above was observed.
>
>
> (gdb) bt
> #0Â  __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:283
> #1Â  0x73e5de65 in msort_with_tmp (p=p@entry=0x7fffc510,
b=b@entry=0x7fffc448, n=n@entry=3) at ./stdlib/msort.c:123
> #2Â  0x73e5ddb1 in msort_with_tmp (n=3, b=0x7fffc448,
p=0x7fffc510) at ./stdlib/msort.c:44
> #3Â  msort_with_tmp (p=p@entry=0x7fffc510, b=b@entry=0x7fffc430,
n=n@entry=6) at ./stdlib/msort.c:53
> #4Â  0x73e5dd94 in msort_with_tmp (n=6, b=0x7fffc430,
p=0x7fffc510) at ./stdlib/msort.c:44
> #5Â  msort_with_tmp (p=p@entry=0x7fffc510, b=b@entry=0x7fffc430,
n=n@entry=12) at ./stdlib/msort.c:52
> #6Â  0x73e5ddb1 in msort_with_tmp (n=12, b=0x7fffc430,
p=0x7fffc510) at ./stdlib/msort.c:44
> #7Â  msort_with_tmp (p=p@entry=0x7fffc510, b=0x7fffc3d8, n=n@entry=23)
at ./stdlib/msort.c:53
> #8Â  0x73e5e23b in msort_with_tmp (n=23, b=,
p=0x7fffc510) at ./stdlib/msort.c:44
> #9Â  __GI___qsort_r (b=b@entry=0x570e2320, n=n@entry=23, s=s@entry=72,
cmp=cmp@entry=0x7fffe1fdaac0 , arg=arg@entry=0x0) at
./stdlib/msort.c:253
> #10 0x73e5e3c8 in __GI_qsort (b=b@entry=0x570e2320, n=n@entry=23,
s=s@entry=72, cmp=cmp@entry=0x7fffe1fdaac0 ) at ./stdlib/msort.c:307
> #11 0x7fffe1fdbcb5 in xcompcap_props (unused=) at
./plugins/linux-capture/xcomposite-input.c:750
> #12 0x765629f6 in obs_source_properties () at
/lib/x86_64-linux-gnu/libobs.so.0
> #13 0x5564c3d5 in SourceToolbar::SourceToolbar(QWidget*,
OBSSafeRef)
(source=..., parent=0x55ea89a0, this=0x56074fd0) at
./libobs/obs.hpp:103

Installing testing's nvidia-cuda-toolkit and nvidia-driver packages
resolved this for me. Originally, I installed the driver via the .run file,
which I still think can work if you ensure the cuda libs are selected
during the setup process.

Bug#941804: exim4: remote_smtp_smarthost transport does not set DKIM variables

[Andreas Metzler]

On 2023-10-28 Larry Doolittle  wrote:
> Andreas -

> On Mon, Oct 16, 2023 at 10:53:17AM -0700, Larry Doolittle wrote:
> > My use case is being stuck behind an ISP's firewall,
> > so the smarthost is supplied by the ISP.  When the ISP
> > delivers the mail to gmail, google needs some indication
> > that the mail I sent is really from me.  That's where DKIM comes in.
> > I _am_ me, so I can make my exim MTA "sign" the message with DKIM
> > on its way to the smarthost.

> And to complete the story, my ISP's smarthost _isn't_ me, and its
> smarthost therefore not qualified/authorized/entrusted-with-the-domainkey
> and _can_not_ add the DKIM headers itself.

> Are you convinced?  Is further discussion needed?

Just to be clear: You have got a domain but lack both control of a
machine that is not blocked from accessing outgoing port 25 (and could
deliver) and the domain package does also lack a smarthost for that
domain that would apply a dkim signature?

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1053821: bookworm patch?

[Jesse Hathaway]

Hey Faidon, I hope you are well!

Since this bug affects the current version in bookworm, v1.8.1, would
there be a possibility of adding the upstream patch to bookworm's
version? I tested applying the patches atop v1.8.1 and they apply
cleanly, and fix the issue as well.

git checkout -b bookworm 1.8.1
git cherry-pick 57262a2710c83fa08767f0ce3ba7a80993515bb2
git cherry-pick 14afa8a46e2e83608a3a219402bce8ea8d071192

Yours kindly, Jesse Hathaway

Bug#1055232: ITP: cue-music-player -- command-line music player

[Matthias Geiger]

Package: wnpp
Severity: wishlist
Owner: Matthias Geiger 
X-Debbugs-Cc: debian-de...@lists.debian.org, werdah...@riseup.net
Control: block -1 by 950181

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: cue-music-player
  Version : 1.2.0
  Upstream Contact: Ravachol 
* URL : https://github.com/ravachol/cue-music-command
* License : GPL-2.0+
  Programming Lang: C
  Description : command-line music player

cue is a command-line music player for a local music library written in C.
Features it has over existing players:

- - album cover support, displayed as ascii or regular image
- - visualizer 
- - vim-like keybinds
- - playlist export
- - fully offline

I already use this to play my local music and would maintain it myself as
it's just a small C application.

best,

werdahias

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmVDvQUVHHdlcmRhaGlh
c0ByaXNldXAubmV0AAoJEBi9EGs7bFR1QyMP/ih0OZ6owYrfel/vauJB1FT1PepT
wudRRJ0wIVP2XUBQPttehVqcy6gy2bDjOv4b7oSf+19lJlxl+cj2ajZkIZb4e/O9
yYdOONKabzGDnc9HNOn2GwgXAw88qtch9Xn/DMvOHWKLYc7cU+vmoSV50GXvWdos
MGlzGeW9LTX7tppSdH0pUTGfKhQIdXFr7WdsRlGiZlScG38XJXhGhFvXGayGLMN/
8n2NklzlBm4lPdHP3XEZLsQE8Rp/dtYpDJ3v8N9j+Z7asTJyTs9T82RhRTGQxP2d
paMV4RRVKK5tFP8my5VljR1LyqisCkeD4/pOlEZLnRJ5E3FRZkbfc1vPHSKZ2T+q
hcfTCjqcEWkYIYNBzVHXEqFm4gJ1F9h2uq7zNDXLacSv3KXLLItPq3/OlmyFA6oU
B/mRry6jtkbwte52oNmBhfs/K1CV7NIQ3SgzFapLM/rufYwWVcxcd1UauFDv0FSm
hG7QN/AIn0Kr+d5bG9zjHtz+CHI1feVTUEEkRB5V/7NdCJdUYJ+LsucmkWNmevgW
RTeb3knbenOoBh8Ujar2vPu5gjQEb0I70Lg03Yz4AhlyssLBIiuqWHofRotiIrZF
XPu+wkqq3X+nzKx2iZ6mTETO0yF5WxEwkIwG5srAyDz4Ek/0dEurrh7JJ1j0eLqI
iwt/mjIBR1qKJxJs
=eeqq
-END PGP SIGNATURE-

Bug#1054422: RFS: pointback/0.2-5 [RC] [Team] -- restore window points when returning to buffers

[Xiyue Deng]

Tobias Frost  writes:

> On Mon, Oct 23, 2023 at 10:12:50AM -0700, Xiyue Deng wrote:
>> Package: sponsorship-requests
>> Severity: important
>> X-Debbugs-CC: debian-emac...@lists.debian.org
>> 
>> Dear mentors,
>> 
>> I am looking for a sponsor for my package "pointback":
>> 
>>  * Package name : pointback
>>Version  : 0.2-5
>>Upstream contact : Markus Triska 
>>  * URL  : https://www.metalevel.at/pointback/
>>  * License  : GPL-3+
>>  * Vcs  : https://salsa.debian.org/emacsen-team/pointback
>>Section  : lisp
>> 
>> The source builds the following binary packages:
>> 
>>   elpa-pointback - restore window points when returning to buffers
>> 
>> To access further information about this package, please visit the following 
>> URL:
>> 
>>   https://mentors.debian.net/package/pointback/
>> 
>> Alternatively, you can download the package with 'dget' using this command:
>> 
>>   dget -x 
>> https://mentors.debian.net/debian/pool/main/p/pointback/pointback_0.2-5.dsc
>> 
>> Changes since the last upload:
>> 
>>  pointback (0.2-5) unstable; urgency=medium
>>  .
>>* Team upload.
>>  .
>>[ Nicholas D Steeves ]
>>* Drop emacs24 and emacs25 from Enhances (packages do not exist in
>>  bullseye).
>>  .
>>[ Debian Janitor ]
>>* Bump debhelper from old 10 to 13.
>>* Set debhelper-compat version in Build-Depends.
>>  .
>>[ Xiyue Deng ]
>>* Add patch migrate-from-removed-assoc-el.patch to migrate from
>>  obsoleted functions in assoc.el which has been removed since Emacs
>>  29.1 (Closes: #1042900).
>>* Drop Built-Using which should not be used for an "arch: all" package.
>>* Update Standards-Version to 4.6.2.  No change needed.
>>* Drop emacs version in Recommends which is from oldoldstable.
>>* Add d/watch with comments of no real upstream version control.
>>* Update d/copyright year and add Upstream-Contact.
>> 
>> Regards,
>> -- 
>> Xiyue Deng
>
> Looks good, but one question:
> Upstream says: 
>
> As of Emacs 26.1, switch-to-buffer-preserve-window-point defaults to t, which 
> solves the problem that pointback.el addresses.
>

Indeed, I've tested that this flag enables the same effect of pointback.el.

> Is this pacakge (pointback) obsolete and should it be kept in Debian?
>

Will file an RM request.  Thanks for looking into this!

> (As the package is fine, I'm uploadig it, but if it is obsolete, please
> file a bug for removal.)
>
>
> Please also investiate: 
>  I: elpa-pointback: wrong-section-according-to-package-name lisp => editors

-- 
Xiyue Deng

Bug#1055233: Several math features break in new version

[Kumar Appaiah]

Package: context
Version: 2023.05.05.20230730+dfsg-2
Severity: important
X-Debbugs-Cc: a.ku...@alumni.iitm.ac.in

Hello.

Upon upgrading to ConTeXt 2023.05.05.20230730+dfsg-2, several math
features seem to break for me. Here is an example:

\starttext
Hello world!
\startformula
 X(f) = \startcases[align={right,left},distance=3pt]
   \NC T, \NC{} $|f| < \frac{1}{2T}$ \NR
   \NC 0, \NC{} $|f| \geq \frac{1}{2T}$ \NR
 \stopcases
\stopformula
\stoptext

The above works very well in 2021.03.05.20230120+dfsg-1+deb12u1 but
gives me this error in 2023.05.05.20230730+dfsg-2:


resolvers   | formats | executing runner 'run luametatex format': 
/usr/bin/luametatex --jobname="./test.tex" --socket --shell-escape 
--fmt=/home/kumar/.texlive2023/texmf-var/luametatex-cache/context/f919750633122078d706dd10f1cfd39b/formats/luametatex/cont-en.fmt
 
--lua=/home/kumar/.texlive2023/texmf-var/luametatex-cache/context/f919750633122078d706dd10f1cfd39b/formats/luametatex/cont-en.lui
  --c:currentrun=1 --c:fulljobname="./test.tex" --c:input="./test.tex" 
--c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="/usr/bin"
job > passes > version mismatch: 1.32 <> 1.33
system  > 
system  > ConTeXt  ver: 2023.05.05 18:36 LMTX  fmt: 2023.11.2  int: 
english/english
system  > 
system  > 'cont-new.mkxl' loaded
open source > level 1, order 1, name 
'/usr/share/texmf/tex/context/base/mkxl/cont-new.mkxl'
system  > beware: some patches loaded from cont-new.mkiv
close source> level 1, order 1, name 
'/usr/share/texmf/tex/context/base/mkxl/cont-new.mkxl'
system  > files > jobname './test', input './test.tex', result './test'
fonts   > latin modern fonts are not preloaded
languages   > language 'en' is active
open source > level 1, order 2, name './test.tex'
fonts   > preloading latin modern fonts (second stage)
mathematics > tweak > 'LatinModernMath-Regular', size 6, math size 3, 
version 'Version 1.959' found, version 'Version 1.958' expected
fonts   > 'fallback modern rm 12pt' is loaded
tex error   > tex error on line 5 in file ./test.tex: Missing $ inserted

 

$
 

\mathatom 
 \math_atom_by_parameter_indeed 
#1->\mathatom 
\s!class \mathcodechecked {#1}
 \math_frac 
#1#*[#2]->\beginmathgroup \setlocalmathfractioncurrent {#1}\ifparameter 
#2\or \setupcurrentmathfraction [#2]\fi \edef \p_math_fraction_fences 
{\mathfractionparameter \c!fences }\math_atom_by_parameter 
\mathfractionparameter 
\bgroup \ifempty \p_math_f
 

{
 
   \NC T, \NC{} $|f| < \frac{
1}{2T}$ \NR

 1 \starttext
 2 Hello world!
 3 \startformula
 4  X(f) = \startcases[align={right,left},distance=3pt]
 5 >> \NC T, \NC{} $|f| < \frac{1}{2T}$ \NR
 6\NC 0, \NC{} $|f| \geq \frac{1}{2T}$ \NR
 7  \stopcases
 8 \stopformula
 9 \stoptext
10 
I've inserted a begin-math/end-math symbol since I think you left one out.
Proceed, with fingers crossed.
mtx-context | fatal error: return code: 1


Please let me know what I can do to help. I am downgrading temporarily though.

Thanks.

Kumar

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages context depends on:
ii  lmodern   2.005-1
ii  luametatex2.10.08+ds-1+b1
ii  ruby  1:3.1
ii  tex-common6.18
ii  tex-gyre  20180621-6
ii  texlive-base  2023.20230613-3
ii  texlive-binaries  2023.20230311.66589-6
ii  texlive-metapost  2023.20230613-3

Versions of packages context recommends:
ii  context-modules   20230730-2
ii  fonts-freefont-otf20211204+svn4273-2
ii  fonts-gfs-artemisia   1.1-6
ii  fonts-gfs-baskerville 1.1-6
ii  fonts-gfs-bodoni-classic  1.1-6
ii  fonts-gfs-didot   1.1-7
ii  fonts-gfs-didot-classic   1.1-6
ii  fonts-gfs-gazis   1.1-6
ii  fonts-gfs-neohellenic 1.1-7
ii  fonts-gfs-olga1.1-6
ii  fonts-gfs-porson  1.1-7
ii  fonts-gfs-solomos 1.1-6
ii  fonts-gfs-theokritos  1.1-6
ii  fonts-sil-gentium 20081126:1.03-4

Versions of packages context suggests:
ii  context-nonfree 2007.03.22-2
pn  fontforge   
ii  libxml-parser-perl  2.46-4
pn  perl-tk 

-- no debconf information

Bug#1014017: soundmodem: Fails to build with HID support

[Dave Hibberd]

Hi Alan,

I'm part of quite an active packet communtiy (https://ukpacketradio.network/) - 
DINAH looks like a cool item a number of folks would be itnerested in! Not many 
of our users are on soundmodem - direwolf, G8BPQ's QtSoundmodem (which I plan 
to upload to Debian) and (in hardware) NinoTNC are the flavour of the month for 
us.

I know of a few CM108 mods (our sister communtiy even has a guide - 
https://wiki.oarc.uk/cm108_sound_interface_smd) 
, so extending 
functionality to more people would be generally of benefit to all.

Soundmodem is a little old, but it's also not moving very fast so I don't see 
too much overhead in maintaining a patch for it unless it's likely to degrade 
the experience for other users?

Cheers
DH

-- 
  Hibby
  MM0RFN

On Thu, 2 Nov 2023, at 2:45 PM, Alan Crosswell wrote:
> Hey Daniele,
> 
> It's been about a year and I've just now gotten around to building a 
> Raspberry Pi connected to a DINAH and can confirm that this PTT patch still 
> works on the latest Raspi Bullseye distro. I don't know if there's any 
> interest in carrying this forward to a committed patch for soundmodem. I can 
> always keep patching it myself if I'm the only one who still thinks 
> soundmodem is a nice small tool for AX.25.
> 
> Regarding many more CM108's, I wonder how many of them are integrated such 
> that a spare GPIO pin is used for PTT? Given it's probably not a lot, I 
> wouldn't think removing the device test entirely would be a huge issue. Would 
> you like me to submit a revised PR to do that?
> 
> 73 de N2YGK
> 
> On Mon, 24 Oct 2022 09:14:23 -0400 Alan Crosswell  wrote:
> > Yeah I don't know that ignoring the device code would be much of a problem.
> > It's not like it searches available devices to see which one to use; the
> > specific device to use is specified.
> > 
> > On Sun, Oct 23, 2022 at 3:10 PM Daniele Forsi  wrote:
> > 
> > > Hello Alan,
> > >
> > > I committed your patch to configure.ac in a branch and I think that we
> > > should merge it to master:
> > > https://salsa.debian.org/debian-hamradio-team/soundmodem/-/tree/hidraw
> > >
> > > I didn't commit your patch to ptt.c yet.
> > > What happens if we drop the check for hiddevinfo.product for C-Media
> > > entirely?
> > >
> > > You changed the test to work with your hardware, which is fine, but it
> > > seems that there are many more CM108s out there (I have one with ID
> > > 0d8c:013c).
> > > I'm copying the list from https://usb-ids.gowdy.us/read/UD/0d8c so it
> > > is archived with this bug report.
> > >
> > > Id Name
> > > 0001 Audio Device
> > > 0002 Composite Device
> > > 0003 Sound Device
> > > 0004 CM6631A Audio Processor
> > > 0005 Blue Snowball
> > > 0006 Storm HP-USB500 5.1 Headset
> > > 000c Audio Adapter
> > > 000d Composite Device
> > > 000e Audio Adapter (Planet UP-100, Genius G-Talk)
> > > 0012
> > > 0014 Audio Adapter (Unitek Y-247A)
> > > 001f CM108 Audio Controller
> > > 0029
> > > 0102 CM106 Like Sound Device
> > > 0103 CM102-A+/102S+ Audio Controller
> > > 0104 CM103+ Audio Controller
> > > 0105 CM108 Audio Controller
> > > 0107 CM108 Audio Controller
> > > 010f CM108 Audio Controller
> > > 0115 CM108 Audio Controller
> > > 0134
> > > 0139 Multimedia Headset [Gigaware by Ignition L.P.]
> > > 013c CM108 Audio Controller
> > > 0201 CM6501
> > > 5000 Mass Storage Controller
> > > 5200 Mass Storage Controller(0D8C,5200)
> > > b213 USB Phone CM109 (aka CT2000,VPT1000)
> > >
> > > --
> > > 73 de IU5HKX Daniele
> > >

Bug#1039883: The issue impacts SSD disks as well

[Diederik de Haas]

On Monday, 24 July 2023 11:23:19 CET Salvatore Bonaccorso wrote:
> On Sun, Jul 02, 2023 at 09:14:50PM +, Hervé Werner wrote:
> > I've just faced this issue on the SSD disk as well, so it seems that
> > the probability is just lower on a speedier disk.
> 
> Are you able to reliably preoeduce the issue and can bisect it to the
> introducing commit?
> 
> Can you retest please with recent kernel, 6.3.11-1 and ideally 6.4.4-1
> as recently uploaded to unstable?

Friendly ping. Please test it with kernel(s) currently available in Debian.

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

Bug#1055234: ITP: python-zombie-imp -- copy of the `imp` module that was removed in Python 3.12

[Gianfranco Costamagna]

Package: wnpp
Severity: wishlist
Owner: Gianfranco Costamagna 

* Package name: zombie-imp
  Version : 0.0.2
  Upstream Author :  1991 - 1995, Stichting Mathematisch Centrum Amsterdam
* URL : https://github.com/encukou/zombie-imp
* License : Python-license
  Programming Lang: Python
  Description : copy of the `imp` module that was removed in Python 3.12

Binary package names: python3-zombie-imp

 # zombie-imp
 .
 ~~A particularly mischevious act of necromancy. That is,~~
 A copy of the `imp` module that was removed in Python 3.12.
 .
 Don't use this, it'll probably trick and bite you.
 .
 .
 # Usage
 .
 Can be summoned by `import zombie_imp`.
 .
 On Python versions where `imp` was banished, reanimate it using `import imp`.
 It promises (with a sneer) to be the same as before.
 .
 Some functionality that was severed from `pkgutil` is interred
 in `zombie_imp.pkgutil`, ready for reattachment:
 .
 - `ImpImporter`
 - `ImpLoader`
 .
 .


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

[Diederik de Haas]

Control: tag -1 moreinfo

On Wednesday, 5 July 2023 19:07:15 CET Jose M Calhariz wrote:
> Package: src:linux
> Version: 6.1.27-1

Can you try with the latest version in the 6.1.x series to see if the problem 
is still there?

> On this hardware I am chasing a data corruption for several months on
> Debian V11 and Debian v12.  Now that I was pointed that linux kernel
> had some problems with XFS solved in later 6.3 kernel I can reproduce
> the problem.
> 
> It seams the problem went away with current Debian testing kernel:
> 
> ii  linux-image-6.3.0-1-amd646.3.7-1  amd64Linux 6.3
> for 64-bit PCs (signed)
> 
> Is there anyone willing to backport the XFS fixes into
> linux-image-6.1.0 and linux-image-5.10.0?

If the problem is still present in the latest 6.1 kernel, then you need to find 
out which patch(es) actually fix the problem.
The easiest way to start with that is to find the last kernel which exhibits 
the issue and then the first one where it is fixed.
https://snapshot.debian.org/binary/linux-image-amd64/ should help with that.

When the range has been narrowed, a `git bisect` should identify the specific 
commit(s) which fixes the issue.
https://wiki.debian.org/DebianKernel/GitBisect should help with that

When that/those have been identified, it should be reported to the upstream 
kernel so that they can incorporate those fixes in their LTS kernel(s) which 
Debian then will pick up automatically.

HTH

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

Bug#1014017: soundmodem: Fails to build with HID support

[Alan Crosswell]

Hey Daniele,

It's been about a year and I've just now gotten around to building a
Raspberry Pi connected to a DINAH and can confirm that this PTT patch still
works on the latest Raspi Bullseye distro. I don't know if there's any
interest in carrying this forward to a committed patch for soundmodem. I
can always keep patching it myself if I'm the only one who still thinks
soundmodem is a nice small tool for AX.25.

Regarding many more CM108's, I wonder how many of them are integrated such
that a spare GPIO pin is used for PTT? Given it's probably not a lot, I
wouldn't think removing the device test entirely would be a huge issue.
Would you like me to submit a revised PR to do that?

73 de N2YGK

On Mon, 24 Oct 2022 09:14:23 -0400 Alan Crosswell  wrote:
> Yeah I don't know that ignoring the device code would be much of a
problem.
> It's not like it searches available devices to see which one to use; the
> specific device to use is specified.
>
> On Sun, Oct 23, 2022 at 3:10 PM Daniele Forsi  wrote:
>
> > Hello Alan,
> >
> > I committed your patch to configure.ac in a branch and I think that we
> > should merge it to master:
> > https://salsa.debian.org/debian-hamradio-team/soundmodem/-/tree/hidraw
> >
> > I didn't commit your patch to ptt.c yet.
> > What happens if we drop the check for hiddevinfo.product for C-Media
> > entirely?
> >
> > You changed the test to work with your hardware, which is fine, but it
> > seems that there are many more CM108s out there (I have one with ID
> > 0d8c:013c).
> > I'm copying the list from https://usb-ids.gowdy.us/read/UD/0d8c so it
> > is archived with this bug report.
> >
> > Id Name
> > 0001 Audio Device
> > 0002 Composite Device
> > 0003 Sound Device
> > 0004 CM6631A Audio Processor
> > 0005 Blue Snowball
> > 0006 Storm HP-USB500 5.1 Headset
> > 000c Audio Adapter
> > 000d Composite Device
> > 000e Audio Adapter (Planet UP-100, Genius G-Talk)
> > 0012
> > 0014 Audio Adapter (Unitek Y-247A)
> > 001f CM108 Audio Controller
> > 0029
> > 0102 CM106 Like Sound Device
> > 0103 CM102-A+/102S+ Audio Controller
> > 0104 CM103+ Audio Controller
> > 0105 CM108 Audio Controller
> > 0107 CM108 Audio Controller
> > 010f CM108 Audio Controller
> > 0115 CM108 Audio Controller
> > 0134
> > 0139 Multimedia Headset [Gigaware by Ignition L.P.]
> > 013c CM108 Audio Controller
> > 0201 CM6501
> > 5000 Mass Storage Controller
> > 5200 Mass Storage Controller(0D8C,5200)
> > b213 USB Phone CM109 (aka CT2000,VPT1000)
> >
> > --
> > 73 de IU5HKX Daniele
> >

Bug#967764: sylpheed: depends on deprecated GTK 2

[Ricardo Mones]

Hi,

On Wed, 1 Nov 2023 23:47:17 +0100
Alexandre Detiste  wrote:

> Hi,
> 
> I had been using sylpheed before & clawsmail
> more recently. I do think it's time to drop the ball:
> 
> i.e:
>  1) RM src:sylpheed
>  2) let src:claws-mail provide a "sylpheed" transitional package,
>   3) maybe with a config migration script, but this step is not mandatory
>   to get 1 & 2 done.

For this route I think is mandatory the existing configurations of sylpheed
do still work after being replaced by claws-mail. IMO better than leaving
users with a migrated configuration that doesn't work is preferable to let
the users to configure claws-mail from scratch.

Note that claws-mail has migration code for sylpheed configurations since the
early days, but with the years passed since they forked this could be easily
missing some change.

> Conveniently the version number of claws-mail is higher than sylpheed's
> one, so no need for extra debhelper wizardy.
> 
> (I did somethink like "3" for residualvm -> scummvm but MR was rejected...
> it's better to discuss first)
> 
> Greetings
> 
> > From: Bastian Germann 
> > Date: Wed, 25 Oct 2023 20:15:53 +0200
> >
> > With claws-mail, there is a sylpheed fork available in Debian that has
> > the porting to GTK 3 done. sylpheed upstream development seems to have
> > stalled. Please consider to have a good migration story for users and
> > get rid of sylpheed for trixie.  


My feeling, from the decades I've been subscribed to upstream ML, is that
for most of Sylpheed users migration to Claws Mail is not an option. Of
course I could be wrong, and not having it in Debian could also lean the
scale for some of those users, but, although the core function is still the
same, this is not a trivial change from the users' point of view IMO.

To summarize: I think is better to some slightly annoyed users who had to
install claws-mail by hand than a bunch of angry users because they got
claws-mail installed when they simply requested to upgrade sylpheed.

Said that, we're still at the beginning of the cycle and there's still a lot
of time before trixie is released, no need to make a rushed decision now.

best regards,
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «Whistler's Law: You never know who is right, but you always know who 
 is in charge.»


pgpA6XDGGV9lF.pgp
Description: Firma digital OpenPGP

Bug#1055228: plplot: FTBFS on armhf (test segfault)

[Gianfranco Costamagna]

Source: plplot
Version: 5.15.0+dfsg2-6
Severity: serious

Hello, I found the package FTBFS on Ubuntu, checked on amdahl and found the 
same issue.

/usr/bin/make  -f examples/fortran/CMakeFiles/x31f.dir/build.make 
examples/fortran/CMakeFiles/x31f.dir/build
make[5]: Entering directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
make[5]: Nothing to be done for 'examples/fortran/CMakeFiles/x31f.dir/build'.
make[5]: Leaving directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
[ 46%] Built target x31f
/usr/bin/make  -f examples/CMakeFiles/test_fortran_svg.dir/build.make 
examples/CMakeFiles/test_fortran_svg.dir/depend
make[5]: Entering directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
cd /home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" /home/locutusofborg/plplot-5.15.0+dfsg2 
/home/locutusofborg/plplot-5.15.0+dfsg2/examples 
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf 
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples 
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples/CMakeFiles/test_fortran_svg.dir/DependInfo.cmake
 "--color="
make[5]: Leaving directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
/usr/bin/make  -f examples/CMakeFiles/test_fortran_svg.dir/build.make 
examples/CMakeFiles/test_fortran_svg.dir/build
make[5]: Entering directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
cd /home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples && 
/usr/bin/cmake -E echo "Generate fortran results for svg device"
Generate fortran results for svg device
cd /home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples && 
env 
EXAMPLES_PREFIX=/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples
 SRC_EXAMPLES_PREFIX=/home/locutusofborg/plplot-5.15.0+dfsg2/examples 
OUTPUT_DIR=/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples/test_examples_output_dir
 /bin/bash 
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/plplot_test/plplot-test.sh
 --verbose --front-end=fortran --device=svg
Testing front-end fortran
x16af
x00f
x01f
x02f
x03f
x04f
x05f
x06f
x07f
x08f
x09f
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/plplot_test/test_fortran.sh: line 54: 3932208 Bus 
error   $DEBUG_CMD "$fortrandir"/x${index}f -dev $device -o 
"${OUTPUT_DIR}"/x${index}${lang}%n.$dsuffix $options 2> fortran_${device}_test.error >| 
"${OUTPUT_DIR}"/x${index}${lang}_${dsuffix}.txt

Program received signal SIGBUS: Access to an undefined portion of a memory 
object.

Backtrace for this error:
make[5]: *** [examples/CMakeFiles/test_fortran_svg.dir/build.make:388: 
examples/test_examples_output_dir/x00f01.svg] Error 1
make[5]: *** Deleting file 'examples/test_examples_output_dir/x00f01.svg'
make[5]: Leaving directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
make[4]: *** [CMakeFiles/Makefile2:5049: 
examples/CMakeFiles/test_fortran_svg.dir/all] Error 2
make[4]: Leaving directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
make[3]: *** [CMakeFiles/Makefile2:7121: 
examples/CMakeFiles/test_noninteractive.dir/rule] Error 2
make[3]: Leaving directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
make[2]: *** [Makefile:2243: test_noninteractive] Error 2
make[2]: Leaving directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
make[1]: *** [debian/rules:55: override_dh_auto_test] Error 2
make[1]: Leaving directory '/home/locutusofborg/plplot-5.15.0+dfsg2'
make: *** [debian/rules:48: binary] Error 2


Full log attached


G.


log.gz
Description: application/gzip


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055231: libgpiod: Can only use gpio* programs as root, not as normal user

[Diederik de Haas]

Source: libgpiod
Version: 1.6.3-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

When looking at the upstream README, I see this in 'examples':
$ gpiodetect

Which indicates it can/should be run as a normal user.
But when I try it on my PC, I get the following error:
diederik@pc:~$ gpiodetect
gpiodetect: unable to access GPIO chips: Permission denied

It works when I do it as root though.
It would be great if (f.e.) there was a `gpio` group setup by this
package which grants access to the gpio devices, so that normal users
can interact with the GPIO chips/subsystem.

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

Kernel: Linux 6.5.0-3-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

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZUO29gAKCRDXblvOeH7b
blSCAP9M2Mt1TfQaGyhbLfr5eF1OI6/at7z6FCIdYTiX1tSkwAEAgxF6N1pmX1yB
vRKGDgxFcO0Q3XVWA79lE2f6FIp3agg=
=E/J4
-END PGP SIGNATURE-

Bug#1040314: devscripts: uscan(1) github.com example could be improved

[Patrice Duroux]

Hi,

And Jan Niehusmann recently changes at Debian Wiki (
https://wiki.debian.org/debian/watch?action=diff=108=107) to:

version=4opts="searchmode=plain,\filenamemangle=s%.*/v?@ANY_VERSION@%@PACKAGE@-$1.tar.xz%"
\https://api.github.com/repos///releases?per_page=50
\https://api.github.com/repos/[^/]+/[^/]+/tarball/v?@ANY_VERSION@


uscan(1) in devscripts-2.23.6 writes:

version=4
opts="filenamemangle=s%(?:.*?)?v?@ANY_VERSION@(@ARCHIVE_EXT@)%@PACKAGE@-$1$2%"
\
https://github.com///tags \
(?:.*?/)?v?@ANY_VERSION@@ARCHIVE_EXT@

I don't know how/who could better coordinate that.
Maybe removing some sections in the Debian Wiki as there is already a link
to uscan(1)?

Regards,
Patrice

On Tue, 04 Jul 2023 06:33:01 -0500 Daniel Lewart  wrote:
> Package: devscripts
> Version: 2.23.4
> Severity: minor
>
> Devscripts Maintainers,
>
> The uscan(1) github.com example is:
>   version=4
>   
> opts="filenamemangle=s%(?:.*?)?v?@ANY_VERSION@(@ARCHIVE_EXT@)%@PACKAGE@-$1$2%"
\
>   https://github.com///tags \
>   (?:.*?/)?v?@ANY_VERSION@@ARCHIVE_EXT@
>
> The beginning of the pattern, which will be discarded, is:
> (?:.*?)?v?
> It should be simplified to:
> .*?
> or made to correspond to the matching pattern:
> (?:.*?/)?v?
>
> Also, the debian/watch wiki:
> https://wiki.debian.org/debian/watch
>  seems to be not as good
as uscan(1), which is confusing.
>
> Of course, the best solution would be the following:
> #1010604 Support commonly used providers like github.com and
gitlab.com
> within watch file:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010604
> 
> Thank you!
> Daniel Lewart
> Urbana, Illinois
>
>

Bug#1055039: redis-server: Crash every two hours (oom), seemingly due to systemd's ProcSubset=pid

[Chris Lamb]

Chris Lamb wrote:

>> you mean with 'stable'? ProcSubset=pid definitely exists in 
>> bookworm, and that's debian stable.
>
> D'oh, of course! As you might have guessed, I had a "brain typo" and
> had completely forgotten that stable = bookworm (and not bullseye).
> I'll get onto this presently.

This has been filed as #1055229.


Regards,

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

Bug#1055230: thunderbird: Freeze while compacting folders

[rpnpif]

Package: thunderbird
Version: 1:115.4.1-1~deb11u1
Severity: normal

Dear Maintainer,

Thunderbird 115.x freezes while compacting a folder.
The locking duration can be until 30 s.
This is very annoying.

Regards.

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

Kernel: Linux 6.1.0-0.deb11.11-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 thunderbird depends on:
ii  debianutils  4.11.2
ii  fontconfig   2.13.1-4.2
ii  libasound2   1.2.4-1.1
ii  libatk1.0-0  2.38.0-1~bpo11+1
ii  libc62.31-13+deb11u7
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.28-0+deb11u1
ii  libdbus-glib-1-2 0.110-6
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi7  3.3-6
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1+deb11u1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1+deb11u1
ii  libglib2.0-0 2.66.8-1
ii  libgtk-3-0   3.24.24-4+deb11u3
ii  libotr5  4.1.1-4
ii  libpango-1.0-0   1.46.2-3
ii  libstdc++6   10.2.1-6
ii  libx11-6 2:1.7.2-1+deb11u2
ii  libx11-xcb1  2:1.7.2-1+deb11u2
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxext6 2:1.3.3-1.1
ii  libxrandr2   2:1.5.1-1
ii  psmisc   23.4-2
ii  x11-utils7.7+5
ii  zenity   3.32.0-6
ii  zlib1g   1:1.2.11.dfsg-2+deb11u2

Versions of packages thunderbird recommends:
ii  hunspell-en-gb [hunspell-dictionary] 1:7.1.0~rc3-3
ii  hunspell-en-us [hunspell-dictionary] 1:2019.10.06-1
ii  hunspell-fr-classical [hunspell-dictionary]  1:7.0-1

Versions of packages thunderbird suggests:
ii  apparmor  2.13.6-10
ii  fonts-lyx 2.3.6-1
ii  libgssapi-krb5-2  1.18.3-6+deb11u4

-- no debconf information

Bug#1054889: linux-image-6.5.0-2-amd64: Kernel 6.5 amdgpu, with refreshrate above 120Hz, black screen appears when certain graphical element appear

[Diederik de Haas]

Please, always keep the bug address in To/CC so everyone can track progress!

I think proton is quite horrible as it encourages top posting and generally
makes using email properly difficult, but please adjust for their shortcomings.

On Thursday, 2 November 2023 14:46:05 CET Peter Malmberg wrote:
> Good news!
> The problem seems to have been fixed in the rc4 kernel.

No, it means the bug was not present in Debian's 6.5-rc4 kernel.
But the bug is reported against version 6.5.6-1, so this *could* be a
regression ... assuming the bug is also present in a Debian kernel ...

http://snapshot.debian.org/package/linux-signed-amd64/ has other/newer
kernels then 6.5~rc4. Please try if the bug still appears with this one:
http://snapshot.debian.org/archive/debian/20230915T084305Z/pool/main/l/linux-signed-amd64/linux-image-6.5.0-1-rt-amd64_6.5.3-1_amd64.deb

If that still doesn't show the problem, then you'd need to try a
non-rt kernel as the RT patch set has been disabled since 6.5.6-1.
But RT or not should not make a difference for this issue.

> Do you know if this fix will find itself into the other zen and liquorix
> kernels?

I do not know nor care about zen or liquorix kernels; you should ask them.

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

Bug#1055229: bookworm-pu: package redis/5:7.0.11-1+deb12u1

[Chris Lamb]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu

Dear stable release managers,

Please consider redis (5:7.0.11-1+deb12u1) for bookworm:
  
  redis (5:7.0.11-1+deb12u1) bookworm; urgency=medium
  .
* Drop ProcSubset=pid hardening flag from the systemd unit files it causes
  difficult-to-reproduce crashes with memory allocation errors. A big thanks
  to Arnaud Rebillout  for the extensive investigation.
  (Closes: #1055039)
* Update debian/gbp.conf for the debian/bookworm branch.


The full diff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/changelog b/debian/changelog
index 2c77a5d1..2f74a30f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+redis (5:7.0.11-1+deb12u1) bookworm; urgency=medium
+
+  * Drop ProcSubset=pid hardening flag from the systemd unit files it causes
+difficult-to-reproduce crashes with memory allocation errors. A big thanks
+to Arnaud Rebillout  for the extensive investigation.
+(Closes: #1055039)
+  * Update debian/gbp.conf for the debian/bookworm branch.
+
+ -- Chris Lamb   Thu, 02 Nov 2023 15:24:45 +0100
+
 redis (5:7.0.11-1) unstable; urgency=high
 
   * New upstream security release:
diff --git a/debian/bin/generate-systemd-service-files 
b/debian/bin/generate-systemd-service-files
index b1e43c86..c7eafabe 100755
--- a/debian/bin/generate-systemd-service-files
+++ b/debian/bin/generate-systemd-service-files
@@ -96,7 +96,6 @@ LockPersonality=true
 MemoryDenyWriteExecute=true
 NoNewPrivileges=true
 PrivateUsers=true
-ProcSubset=pid
 ProtectClock=true
 ProtectControlGroups=true
 ProtectHostname=true
diff --git a/debian/gbp.conf b/debian/gbp.conf
index 24e95b17..14717f8e 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,3 +1,3 @@
 [DEFAULT]
-debian-branch=debian/sid
-upstream-branch=upstream/sid
+debian-branch=debian/bookworm
+upstream-branch=upstream/bookworm

Bug#1055088: game-data-packager: jazz_jackrabbit_collection information outdated

[fabian]

Am 2023-11-02 15:10, schrieb Alexandre Detiste:

Do you know what "_csv2" means ?


Nope, sorry. I have just taken the archive as it comes.

Cheers,

 - Fabian

Bug#1055227: libgom: FTBFS on i386

[Bastian Germann]

Source: libgom
Version: 0.4-1
Severity: serious

libgom fails to build from source on i386 due to a test failing:

 3/12 
test: test-gom-insert
start time:   14:03:26
duration: 0.08s
result:   killed by signal 6 SIGABRT
command:  MALLOC_PERTURB_=71 LD_LIBRARY_PATH=... 
libgom-0.4/obj-i686-linux-gnu/tests/test-gom-insert
--- stdout ---
TAP version 13
# random seed: R02S7791a8ec950e3900d687ca4fec1d2b7b
1..2
# Start of GomRepository tests
# DEBUG: Binding gtype guint (28).
# DEBUG: Binding gtype gchararray (64).
# DEBUG: Binding gtype gchararray (64).
# DEBUG: Binding gtype gchararray (64).
# DEBUG: Binding gtype gchararray (64).
# DEBUG: Binding gtype gchararray (64).
--- stderr ---
malloc_consolidate(): unaligned fastbin chunk detected

Bug#1032391: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

[Jose M Calhariz]

Hi,

After some research it was found the problem was not HW related, but
related with XFS driver and is present until linux 6.1.  So I opened
new bug report on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040416

Kind regards
Jose M Calhariz


-- 
--
A vida feliz, meu Deus, consiste em nos alegrarmos em vos,
de vos e por vos


signature.asc
Description: PGP signature

Bug#1054323: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected

[Andreas Tille]

Hi Graham,

Am Sun, Oct 29, 2023 at 10:12:56AM -0100 schrieb Graham Inggs:
> I found that in debian/control, r-cran-tmb has Depends:
> r-cran-matrix (>= 1.5-3-1~), but this is somehow replaced in the
> binary package, presumably by dh-r?

dh-r creates a variable R:Depends
 
> Andreas, would it be possible for dh-r to always replace the version
> in r-cran-tmb's Depends with r-cran-matrix (>= [the version of
> r-cran-matrix it was built with]) ?

Well, the *version* was correct even in r-cran-tmb 1.9.6-4.  However,
due to the '-' in the GNU R Matrix version the dpkg sorting mechanism
failed and we need the correct revision of the Debian package.  To
approach this I decided against hacking this exception into dh-r but
rather added override_dh_gencontrol to d/rules where I'm editing the
variable accordingly to have the r-cran-matrix Debian package revision
that was used at build time.

> Then you can avoid modifying Build-Depends and upstream's DESCRIPTION,
> and will allow r-cran-tmb to be binNMU'd when needed.  It should also
> allow for easier backporting.

I hope this will also work for backporting but with the current
dependency of TMB it also needs Matrix from testing.


There is probably one remaining problem.  As per file R/zzz.R[2] the
function checkMatrixPackageVersion verifies that TMB is running always
with the Matrix version it was built against.  Do you see some automatic
method to approach this which is better than simply waiting for a CI
test to fail (which should happen once a r-cran-matrix package of a new
Matrix version is uploaded)?

Kind regards
Andreas.

[1] 
https://salsa.debian.org/r-pkg-team/r-cran-tmb/-/blob/master/debian/rules#L10-13
[2] https://salsa.debian.org/r-pkg-team/r-cran-tmb/-/blob/master/R/zzz.R

-- 
http://fam-tille.de

Bug#1055088: game-data-packager: jazz_jackrabbit_collection information outdated

[Alexandre Detiste]

Maybe diffiscope can (be made to) understand InnoSetup archives.

Do you know what "_csv2" means ?

Greets,

Bug#1039050: Please test latest upload

[Brian Vaughan]

foliate 2.6.4-1+dfsg5 wasn't in unstable, but it was in experimental. I tried 
it and it seems to be working.

Bug#996765: neomutt/gnutls/nntp is not verifying a Lets Encrypt trust path correctly (news.gmane.io)

[Carlos Henrique Lima Melara]

Hi,

Upstream has answered [1] with:

> on Nov 6, 2021:
> This only seems to affect ./configure --gnutls

And:

> on Nov 20, 2021:
> Debugging, I see that the only thing wrong with the certificate is that it's 
> out of date.
> Fortunately, there's a workaround for this case:
>
> set ssl_verify_dates = no

Cheers,
Charles

[1] https://github.com/neomutt/neomutt/issues/3123


signature.asc
Description: PGP signature

Bug#1055039: redis-server: Crash every two hours (oom), seemingly due to systemd's ProcSubset=pid

[Chris Lamb]

Hi Arnaud

> you mean with 'stable'? ProcSubset=pid definitely exists in 
> bookworm, and that's debian stable.

D'oh, of course! As you might have guessed, I had a "brain typo" and
had completely forgotten that stable = bookworm (and not bullseye).
I'll get onto this presently.


Best wishes,

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

Bug#1055134: ITP: golang-github-bits-and-blooms-bloom -- Go package implementing Bloom filters, used by Milvus and Beego.

[Shengjing Zhu]

Hi,

On Wed, Nov 1, 2023 at 11:21 AM John Goerzen  wrote:
>
> Package: wnpp
> Severity: wishlist
> Owner: John Goerzen 
>
> * Package name: golang-github-bits-and-blooms-bloom
>   Version : 3.6.0-1
>   Upstream Author : Will Fitzgerald
> * URL : https://github.com/bits-and-blooms/bloom
> * License : BSD-2-clause
>   Programming Lang: Go
>   Description : Go package implementing Bloom filters, used by Milvus and 
> Beego.
>

This package was called golang-github-willf-bloom previously. Upstream
just renamed.

And golang-github-willf-bloom also adds
github.com/bits-and-blooms/bloom as import path.

https://tracker.debian.org/pkg/golang-github-willf-bloom

-- 
Shengjing Zhu

Bug#1055226: bookworm-pu: package yuzu/0-1335-1+deb12u1

[Bastian Germann]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: bookworm
X-Debbugs-Cc: b...@debian.org, and...@pappacoda.it
Severity: normal

[ Reason ]
The package FTBFS in stable: #1041491.

[ Impact ]
Rebuilding is impossible.

[ Risks ]
Just a build-dependency correction. No risk.

[ 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 (old)stable
  [x] the issue is verified as fixed in unstablediff -Nru yuzu-0-1335+ds/debian/changelog yuzu-0-1335+ds/debian/changelog
--- yuzu-0-1335+ds/debian/changelog 2023-02-11 12:29:45.0 +0100
+++ yuzu-0-1335+ds/debian/changelog 2023-11-02 13:48:32.0 +0100
@@ -1,3 +1,9 @@
+yuzu (0-1335+ds-1+deb12u1) bookworm; urgency=medium
+
+  * strip :native from glslang-tools build dependency (Closes: #1041491)
+
+ -- Bastian Germann   Thu, 02 Nov 2023 13:48:32 +0100
+
 yuzu (0-1335+ds-1) unstable; urgency=medium
 
   * New upstream version 0-1335+ds
diff -Nru yuzu-0-1335+ds/debian/control yuzu-0-1335+ds/debian/control
--- yuzu-0-1335+ds/debian/control   2023-02-11 12:27:17.0 +0100
+++ yuzu-0-1335+ds/debian/control   2023-11-02 13:47:35.0 +0100
@@ -5,7 +5,7 @@
 Build-Depends: debhelper-compat (= 13)
 Build-Depends-Arch: catch2 (>= 2.13.7) ,
 cmake (>= 3.15),
-glslang-tools:native,
+glslang-tools,
 libavcodec-dev,
 libavutil-dev,
 libboost-context-dev,

Bug#1055225: libpango1.0-0: Please drop transitional package

[Patrice Duroux]

 Two cents.
Promoting the equivs package to solve such a situation is also something to
consider, no?
It happens to me many times with some unofficial packages.
Currently, I did not find equivs anywhere in the Debian Wiki where it could
be useful to cite regarding unofficial packages or repositories. Listing
some old (removed) «classic» transitional packages there could help then
maybe, any opinion?
Regards,
Patrice

On Thu, 2 Nov 2023 12:32:19 + Simon McVittie  wrote:
> On Thu, 02 Nov 2023 at 12:54:54 +0100, Bastian Germann wrote:
> > Please drop the package libpango1.0-0 which was transitional for
> > several releases.
>
> Thanks for the reminder. We tried removing that package once already,
> but had to revert its removal during the bullseye cycle because it broke
> a lot of third-party .debs (see #958035, #956520, #959978, #958477).
>
> Now that bullseye (and bookworm) has been released with a libpango1.0-0
> whose versioned dependencies are all of the form (>= x) rather than (= x),
> allowing users to keep the bullseye or bookworm version of libpango1.0-0
> installed if they need it, we can have another try at this.
>
> smcv
>
>

Bug#1055205: chrony: SysV problems after upgrade

[Paul Gevers]

Hi Vincent,

On 02-11-2023 13:21, Vincent Blut wrote:

I'm closing this bug report as this is, to me, not something that should
handled on the packaging side.


Thank you for repairing my lack of looking these things up. I suspected 
as much (but failed to express that).


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055225: libpango1.0-0: Please drop transitional package

[Simon McVittie]

On Thu, 02 Nov 2023 at 12:54:54 +0100, Bastian Germann wrote:
> Please drop the package libpango1.0-0 which was transitional for
> several releases.

Thanks for the reminder. We tried removing that package once already,
but had to revert its removal during the bullseye cycle because it broke
a lot of third-party .debs (see #958035, #956520, #959978, #958477).

Now that bullseye (and bookworm) has been released with a libpango1.0-0
whose versioned dependencies are all of the form (>= x) rather than (= x),
allowing users to keep the bullseye or bookworm version of libpango1.0-0
installed if they need it, we can have another try at this.

smcv

Bug#1054889: linux-image-6.5.0-2-amd64: Kernel 6.5 amdgpu, with refreshrate above 120Hz, black screen appears when certain graphical element appear

[Diederik de Haas]

On Sunday, 29 October 2023 03:39:22 CET Peter Malmberg wrote:
> Which files should I download?

My bad, I referenced the meta package which depends on the 'actual' package:
https://snapshot.debian.org/archive/debian/20230807T150823Z/pool/main/l/linux-signed-amd64/linux-image-6.5.0-0-rt-amd64_6.5~rc4-1~exp1_amd64.deb

> Which cli commands do I use?

So just DL that file and do (as root or with sudo):
apt install ./linux-image-6.5.0-0-rt-amd64_6.5~rc4-1~exp1_amd64.deb

> 2. chmod +x

There's no need for that

> I have both experimental and backports activated in apt:
> deb http://deb.debian.org/debian experimental main contrib
> and
> deb http://deb.debian.org/debian bookworm main contrib non-free-firmware
> deb-src http://deb.debian.org/debian bookworm main contrib non-free-firmware
> Still can't find the linux-image-6.5.0.0-amd anywhere.

You can remove those. The file has '~exp1' as it was uploaded to experimental
in the past, but it's not available in current experimental; only on 
snapshot.d.o
I do assume you have 'trixie' in your sources.list



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

Bug#1055205: chrony: SysV problems after upgrade

[Vincent Blut]

Hi Richard,

Le 2023-11-02 09:01, Richard Lucassen a écrit :
> Package: chrony
> Version: 4.4-3
> Severity: normal
> 
> I run chronyd supervised. Therefore I removed symlinks in /etc/rc2.d/ 
> (update-rc.d chrony remove).
> But after an upgrade the deb package installs new symlinks in /etc/rc2.d/ and 
> starts chronyd, even though chronyd is SysV disabled.
> 
> Please check if /etc/rc2.d/*chrony symlinks exist, if not, don't add these 
> and do not start chronyd. Maybe it's a good idea to just display a warning in 
> that case.
> 

I'm closing this bug report as this is, to me, not something that should
handled on the packaging side. From update-rc.d(8):

A common system administration error is to delete the links with the  
thought  that  this  will
"disable"  the  service, i.e., that this will prevent the service from 
being started.  However,
if all links have been deleted then the next  time  the  package  is  
upgraded,  the  package's
postinst  script  will run update-rc.d again and this will reinstall links 
at their factory de-
fault locations.  The correct way to disable services is to configure the 
service as stopped in
all runlevels in which it is started by default.  In the System V init 
system this means renam-
ing the service's symbolic links from S to K.  .P The script .BI 
/etc/init.d/ name  must  exist
before update-rc.d is run to create the links.

Running 'update-rc.d chrony disable' as root should work too.

> Richard.

Have a good day,
Vincent


signature.asc
Description: PGP signature

Bug#932491: python3-apt: segfault reading from lzma stream

[Cyril Brulebois]

Cyril Brulebois  (2023-11-02):
> Today I had a few more minutes to spend on this, so here's a little
> debugging session. My main system is still bullseye, but the same tests
> in a bookworm chroots fail the same way.

“But maybe it's a bug in the lzma library?” one might ask.

Adding a bzip2 test between gzip and lzma leads to the following, again
on both bullseye and bookworm (after creating a Test.bz2/Packages.bz2
from one of the other files):

With bug-932491-aa.py (bug-932491-a.py + bzip2):

$ ./bug-932491-aa.py Test
gz == bz: True
gz == xz: True
gz: section 1 size: 29
gz: section 1 keys: ['Package', 'Desc']
gz: section 2 size: 47
gz: section 2 keys: ['Package', 'Desc']
Traceback (most recent call last):
  File "/home/kibi/tmp/./bug-932491-c.py", line 37, in 
tf_bz.step()
apt_pkg.Error: E:Unable to parse package file  (1)

$ ./bug-932491-aa.py Packages
gz == bz: True
gz == xz: True
gz: section 1 size: 1281
gz: section 1 keys: ['Package', 'Version', 'Installed-Size', 'Maintainer', 
'Architecture', 'Depends', 'Pre-Depends', 'Description', 'Homepage', 
'Description-md5', 'Tag', 'Section', 'Priority', 'Filename', 'Size', 'MD5sum', 
'SHA256']
gz: section 2 size: 585
gz: section 2 keys: ['Package', 'Version', 'Installed-Size', 'Maintainer', 
'Architecture', 'Pre-Depends', 'Suggests', 'Description', 'Homepage', 
'Description-md5', 'Tag', 'Section', 'Priority', 'Filename', 'Size', 'MD5sum', 
'SHA256']
bz: section 1 size: 1410
Segmentation fault

With bug-932491-bb.py (bug-932491-b.py + bzip2):

$ ./bug-932491-bb.py Test
gz packages: 2
Traceback (most recent call last):
  File "/home/kibi/tmp/./bug-932491-bb.py", line 26, in 
for stanza in tf_bz:
apt_pkg.Error: E:Unable to parse package file  (1)

$ ./bug-932491-bb.py Packages
gz packages: 50771
Traceback (most recent call last):
  File "/home/kibi/tmp/./bug-932491-bb.py", line 27, in 
bz_packages.append(stanza['Package'])
   ~~^^^
KeyError: 'Package'


It looks like we might be getting chunks of different sizes depending on
the underlying file objects, and some buffering/seeking code is buggy on
the apt_pkg side?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
#!/usr/bin/python3
"""
Test case for #932491, version a+bz2
"""
import bz2
import gzip
import lzma
import sys

import apt_pkg

root = sys.argv[1]

# Check data decompression works fine:
with gzip.open(f'{root}.gz') as gz:
gz_text = gz.read()
with bz2.open(f'{root}.bz2') as bz:
bz_text = bz.read()
with lzma.open(f'{root}.xz') as xz:
xz_text = xz.read()
print(f'gz == bz: {gz_text == bz_text}')
print(f'gz == xz: {gz_text == xz_text}')

# Perform 2 manual steps with gz:
with gzip.open(f'{root}.gz') as gz:
tf_gz = apt_pkg.TagFile(gz)
tf_gz.step()
print(f'gz: section 1 size: {tf_gz.section.bytes()}')
print(f'gz: section 1 keys: {tf_gz.section.keys()}')
tf_gz.step()
print(f'gz: section 2 size: {tf_gz.section.bytes()}')
print(f'gz: section 2 keys: {tf_gz.section.keys()}')

# Perform 2 manual steps with bz:
with bz2.open(f'{root}.bz2') as bz:
tf_bz = apt_pkg.TagFile(bz)
tf_bz.step()
print(f'bz: section 1 size: {tf_bz.section.bytes()}')
print(f'bz: section 1 keys: {tf_bz.section.keys()}')
tf_bz.step()
print(f'bz: section 2 size: {tf_bz.section.bytes()}')
print(f'bz: section 2 keys: {tf_bz.section.keys()}')

# Perform 2 manual steps with xz:
with lzma.open(f'{root}.xz') as xz:
tf_xz = apt_pkg.TagFile(xz)
tf_xz.step()
print(f'xz: section 1 size: {tf_xz.section.bytes()}')
print(f'xz: section 1 keys: {tf_xz.section.keys()}')
tf_xz.step()
print(f'xz: section 2 size: {tf_xz.section.bytes()}')
print(f'xz: section 2 keys: {tf_xz.section.keys()}')
#!/usr/bin/python3
"""
Test case for #932491: version b+bz2
"""
import bz2
import gzip
import lzma
import sys

import apt_pkg

root = sys.argv[1]

# Start a loop:
gz_packages = []
with gzip.open(f'{root}.gz') as gz:
tf_gz = apt_pkg.TagFile(gz)
for stanza in tf_gz:
gz_packages.append(stanza['Package'])
print(f'gz packages: {len(gz_packages)}')

# Start a loop:
bz_packages = []
with bz2.open(f'{root}.bz2') as bz:
tf_bz = apt_pkg.TagFile(bz)
for stanza in tf_bz:
bz_packages.append(stanza['Package'])
print(f'bz packages: {len(bz_packages)}')

# Start a loop:
xz_packages = []
with lzma.open(f'{root}.xz') as xz:
tf_xz = apt_pkg.TagFile(xz)
for stanza in tf_xz:
print('.', end='')
xz_packages.append(stanza['Package'])
print()
print(f'xz packages: {len(xz_packages)}')


signature.asc
Description: PGP signature

Bug#1040373: lsof does not work correctly with btrfs subvolumes

[Tj]

Package: lsof
Version: 4.95.0-1
Followup-For: Bug #1040373

This seems to be related to upstream issue:

https://github.com/lsof-org/lsof/issues/152 "LTlock fails on btrfs"

Small test-case:

 SUBVOL_FILE="/mnt/machines_old/test";
 sudo findmnt -oTARGET,SOURCE,FSTYPE,MAJ:MIN "${SUBVOL_FILE%/*}"
 sudo stat --format="%n%Hd:%Ld" 
"$SUBVOL_FILE"
 flock "$SUBVOL_FILE" grep ":$(stat --format="%i" "$SUBVOL_FILE")" /proc/locks 
| tee >(bc <<< "ibase=16; $(cut -d: -f 3)")

TARGETSOURCE FSTYPE MAJ:MIN
/mnt/machines_old /dev/mapper/SUNNY-machines_old btrfs0:100
/mnt/machines_old/test0:101
20: FLOCK  ADVISORY  WRITE 378526 00:64:395 0 EOF
100

Bug#1055225: libpango1.0-0: Please drop transitional package

[Bastian Germann]

Package: libpango1.0-0
Severity: minor

Please drop the package libpango1.0-0 which was transitional for several 
releases.

Bug#1055171: fpga-icestorm: icebram incompatible with yosys 0.23

[Andras Pal]

Hi Daniel,

thank you - i removed the trixie packages, added your repo and upgraded 
the fpga-icestorm* packages accoringly. Tested on both this minimal 
example and on my larger projects - all passed and now working fine!


Yes, this thread is very interesting and discusses indeed the same issue. 
This distribution of BRAM cells for larger memory blocks is indeed 
implying an ambiguous solition and/or and interesting trade-offs (if we 
also consider things like power consumption vs. path lengths).


Thanks again, Andras

On Thu, 2 Nov 2023, Daniel Gröber wrote:


Hi Andras,

On Thu, Nov 02, 2023 at 08:44:31AM +0100, Andras Pal wrote:

sure, please find attached this simplistic example for this issue. Just
enter `make`. Under bullseye, it should print:

Found and replaced 1 instances of the memory.

Under bookworm, it prints:

Found and replaced 0 instances of the memory.


Yup, I can reproduce the issue.

I've sent a request to the release team and uploaded the proposed
fpga-icestorm=0~20230218gitd20a5e9-1~deb12u1 to my repo at
https://dxld.at/localdebs/ (sources.list instructions within) please test.

Note to self: the upstream discussion is at
https://github.com/YosysHQ/icestorm/issues/301
https://github.com/YosysHQ/icestorm/pull/309

--Daniel

Bug#1055102: odbcinst1debian2: Error while installing package

[Hugh McMaster]

Hi Janos,

On Wed, 1 Nov 2023 at 00:51, Janos Katein wrote:
>
> I wanted to install the odbcint1debian2 package and I expected it to
> install properly. But instead I got the following error message:
>
> Package failed to install:
> Error while installing package: trying to overwrite 
> '/usr/lib/x86_64-linux-gnu/libodbcinst.so.2.0.0', which is also in package 
> libodbcinst2

Do you use the Microsoft ODBC driver for SQL Server by any chance?

This bug has been reported a few times in recent months. In each case,
the submitter is trying to install unixodbc packages from Microsoft's
repository instead of Debian's repository.

The Microsoft packages contain a few different files, making them
incompatible with the Debian versions.

In any case, I spun up a VM with Debian Stable and had no problems
installing odbcinst1debian2 and libodbcinst2.

Bug#1032792: please drop transitional package libuim-data from src:uim

[Bastian Germann]

Hm... It looks like the dependency direction of the transitional package is 
wrong.
The non-transitional uim-data depends on the transitional libuim-data. So the 
package was
not really transitional. It should be dropped anyway but please also dop the 
dependency.

Bug#1041491: yuzu: FTBFS: Unmet build dependencies: glslang-tools:native

[Santiago Vila]

reopen 1041491
tags 1041491 + bookworm
fixed 1041491 0-1335+ds-1.1
thanks

Hello. I'm reopening this because packages in stable must build in stable.

Cc:ing all involved parties: Please keep FTBFS bugs open when they happen
in stable, otherwise they become a lot more difficult to find, as they
have a tendency to be archived by the BTS.

Thanks.

Bug#1032735: please drop transitional package tor-arm from src:nyx

[Ulises Vitulli]

Thanks, have my blessing to push it straight without delay.


On 11/2/23 08:06, Bastian Germann wrote:

I am uploading a NMU to DELAYED/10 in order to fix this.
The changes are included in git.

Bug#1055224: ITP: endesive -- library for digital signing and verification of signatures in docs

[Josenilson Ferreira da Silva]

Package: wnpp
Severity: wishlist
Owner: Josenilson Ferreira da Silva 
X-Debbugs-Cc: debian-de...@lists.debian.org, nilsonfsi...@hotmail.com

* Package name: endesive
  Version : 2.16
  Upstream Contact: Grzegorz Makarewicz 
* URL : https://github.com/m32/endesive
* License : MIT/expat
  Programming Lang: Python
  Description : library for digital signing and verification of signatures 
in docs

This package contains a Python library for digital signing and verification of
 digital signatures in mail, PDF and XML documents.
 .
 The ASN.1 implementation depends on asn1crypto. Cryptographic routines depends
 on cryptography library.
 .
 For certificate verification CertValidator is used.
 .
 This library implements S/MIME handler which can encrypt and decrypt S/MIME
 messages using a public RSA key, in AES-128/192/256 CBC/OFB modes. It can also
 sign and verify S/MIME messages.
 .
 This library implements CAdES-B handler for signing and verifying PDF
 documents in Adobe.PPKLite/adbe.pkcs7.detached form. It can sign documents
 during generation using a modified version of pyfpdf which is included in this
 library. It can also sign documents generated by external programs.
 .
 This library implements XADES BES/T with enveloped and enveloping format for
 creating signed xml files.
 .
 This library implements CMS handler for signing and verifying plain text files
 with detached signature files.

Bug#1055221: qemu-system is not compiled with pipewire audio support

[Michael Tokarev]

Control: severity -1 wishlist
Control: tag -1 + confirmed

02.11.2023 14:10, Francesco C:

Package: qemu-system
Version: 1:8.1.2+ds-1
Severity: normal

Dear Maintainer,

Qemu mainline version 8.1.2 claims supporting pipewire audio as host
audio driver , but debian packages is not compiled with that feature :


I deliberately did not enable pipewire which has just landed in qemu
and had a number of issues. I plan to enable it when 8.2 packages will
come to debian.

Personally I don't see value in pw support in qemu for now.

/mjt

Bug#1055223: src:slurm-wlm-contrib: fails to migrate to testing for too long: missing binaries

[Paul Gevers]

Source: slurm-wlm-contrib
Version: 23.02.3-2.1
Severity: serious
Control: close -1 23.02.6-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:slurm-wlm-contrib has been trying to 
migrate for 31 days [2]. Hence, I am filing this bug. This package has 
build dependencies that exist in non-free, so it can't be build on the 
buildd [3]. Please upload the binaries for at least amd64.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=slurm-wlm-contrib
[3] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#source-and-binary-uploads


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055222: fuse: backport unprivileged usage via /dev/fd/N to support usage in namespaces

[Helmut Grohne]

Package: libfuse2
Version: 2.9.9-6+b1
Tags: patch upstream fixed-upstream

Hello Laszlo,

I have a slightly unusual request. I know libfuse 2.x is a legacy in
maintenance mode slated for removal eventually. Unfortunately, 2/3 of
fuse users still use the 2.x branch so it seems like we will have to
support it a bit longer than expected.

You may have heared about Linux and namespaces and this is an area where
fuse < 3.3 falls short. While we think of mount as a privileged
operation in need of a setuid helper, you can perform an unprivileged
mount operation on standard Debian systems by employing user and mount
namespaces now. Getting there is a bit non-trivial, so let me explain
how it works with fuse >= 3.3. Typically, the goal is to perform the
mount operation in a different namespaces from the namespace running the
fuse userspace driver. Currently, one invokes a fuse driver with a mount
point and it first tries to mount directly and failing that executes a
setuid helper process fusermount to perform that operation with root
rights. Both happen in the same namespace as the driver process, which
is very much not what we want here. When launching the fusermount
process, it opens /dev/fuse, mounts it and communicates the fuse
connection via a unix domain socket using SCM_RIGHTS back to the driver
process. So what we really need here is a way of passing such a fuse
connection to a fuse driver and having it not perform the mount itself
(neither directly nor via fusermount). This need was recognized and
since fuse 3.3, the path /dev/fd/N is treated differently when passed as
a mountpoint. Upon seeing such a path, it'll skip all mounting and just
use the referenced file descriptor. Thus a process in a namespace can
open a fuse connection there, mount it and send back the file descriptor
(again using SCM_RIGHTS) to some other process outside the namespace
that ultimately launches the fuse driver while inheriting that file
descriptor.

Unfortunately, this currently requires fuse >= 3.3 and e.g. fuse2fs from
e2fsprogs still uses fuse 2.x. Last time Ted Ts'o was inquired about
porting to 3.x, he was unenthusiastic and when I spent a look, it is
quite non-trivial as the API changed a lot. It's not just fuse2fs that
is affected but still 2/3 of drivers. On the flip side, backporting this
function into fuse 2.x was relatively easy and the chances of breaking
something are fairly low as that path is intentionally so special that
people will only use it for this very functionality.

So I think we should backport this into fuse 2.x. This is not to say
that we should stop porting drivers to the 3.x API. It also slightly
improves compatibility between 2.x and 3.x, so that seems like a sane
trade-off to me. Do you agree?

I'm attaching a patch ready to be dropped into debian/patches for your
convenience.

Helmut
From: Helmut Grohne 
Subject: backport support for /dev/fd/NN
Origin: https://github.com/libfuse/libfuse/commit/64e11073b9347fcf9c6d1eea143763ba9e946f70
Forwarded: not-needed

This is a backport of 64e11073b9347fcf9c6d1eea143763ba9e946f70 ("Allow passing
`/dev/fuse` file descriptor from parent process") and enables fuse 2.9 to
perform the unprivileged part in much the same way as fuse >= 3.3 does. Since
fuse changed significantly, this is a reimplementation of the original idea on
the older code base.

An alternative to applying this patch is porting users of this library to 3.x.
In reality, progress has been slow and very many packages still use 2.x. While
such porting is a good thing in principle, it also is a huge task when a
relatively simple alternative is available.

--- fuse-2.9.9.orig/lib/mount.c
+++ fuse-2.9.9/lib/mount.c
@@ -575,6 +575,15 @@
 	return 0;
 }
 
+static int parse_fuse_fd(const char *mountpoint)
+{
+	int fd = -1, len = 0;
+
+	if (sscanf(mountpoint, "/dev/fd/%u%n", , ) == 1 && len == strlen(mountpoint))
+		return fd;
+	return -1;
+}
+
 int fuse_kern_mount(const char *mountpoint, struct fuse_args *args)
 {
 	struct mount_opts mo;
@@ -604,6 +613,15 @@
 	if (mo.mtab_opts &&  fuse_opt_add_opt(_opts, mo.mtab_opts) == -1)
 		goto out;
 
+	res = parse_fuse_fd(mountpoint);
+	if (res >= 0) {
+		if (fcntl(res, F_GETFD) == -1) {
+			fprintf(stderr, "fuse: Invalid filesystem /dev/fd/%u\n", res);
+			res = -1;
+		}
+		goto out;
+	}
+
 	res = fuse_mount_sys(mountpoint, , mnt_opts);
 	if (res == -2) {
 		if (mo.fusermount_opts &&
--- fuse-2.9.9.orig/lib/helper.c
+++ fuse-2.9.9/lib/helper.c
@@ -105,7 +105,11 @@
 
 	case FUSE_OPT_KEY_NONOPT:
 		if (!hopts->mountpoint) {
+			int fd, len=0;
 			char mountpoint[PATH_MAX];
+			/* fuse_kern_mount matches /dev/fd/N */
+			if (sscanf(arg, "/dev/fd/%u%n", , ) == 1 && len == strlen(arg))
+return fuse_opt_add_opt(>mountpoint, arg);
 			if (realpath(arg, mountpoint) == NULL) {
 fprintf(stderr,
 	"fuse: bad mount point `%s': %s\n",

Bug#1055221: qemu-system is not compiled with pipewire audio support

[Francesco C]

Package: qemu-system
Version: 1:8.1.2+ds-1
Severity: normal

Dear Maintainer,

Qemu mainline version 8.1.2 claims supporting pipewire audio as host
audio driver , but debian packages is not compiled with that feature :

> qemu-system-amd64 -audiodev help
Available audio drivers:
none
alsa
dbus
jack
oss
pa
sdl
spice
wav

The changelog in the main site explains that pipewire support is
enabled when the build system detects libpipewire installed on the
system.

Debian package should (build-)depends on libpipewire-*-dev to enable
pipewire audio host support.

Bug#1055220: pdudaemon: incomplete dependency list?

[Andrej Shadura]

Package: pdudaemon
Version: 0.0.8.58.g597052b-1
Severity: normal

Hello,

Upon installing pdudaemon and running it without any argument, I am
greeted with the following error message:

ModuleNotFoundError: No module named 'aiohttp'

(I have omitted the stack trace.) After installing python3-aiohttp and
re-running the command, I’ve got this:

ModuleNotFoundError: No module named 'pymodbus'

Installing python3-pymodbus finally allowed me to run pdudaemon.

These packages are not in Depends, Recommends or even Suggests.
It appears to me ${python3:Depends} in your debian/control is not
catching these for some reason. Could you please verify and potentially
add these by hand?

Thanks!

-- 
Cheers,
  Andrej

Bug#1032735: please drop transitional package tor-arm from src:nyx

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
The changes are included in git.