Bug#1022282: staden-io-lib: FTBFS: ./data/9827_rand3.cram.fai: No such file or directory

2022-10-27 Thread Andreas Tille
Dear Bernhard,

> A short term solution might be the patch in [7] which makes
> the build and tests succeed without "implicit declarations".

Thanks a lot for your explicit explanation and the helpful patch.

I've just uploaded your patch
   Andreas.

-- 
http://fam-tille.de



Bug#1022173: Update (tested on bullseye, several kernels, only Libreoffice 1:7.4.1-1~bpo11+2 fixes the issue)

2022-10-27 Thread Robin
Hi all!

Good news:

The Libreoffice backport from bookworm seems to fix this issue. I've checked 
this on different kernels:
Besides of the 4.9.0 kernel I've tested this on
  linux-image-5.10.137-antix.1-686-smp-pae
  linux-image-5.10.142-antix.2-686-smp-pae
  linux-image-5.10.0-18-686-pae (signed)
  linux-image-5.10.0-19-686-pae (signed)

and additionally from on most recent one from Bullseye-Backports:
  linux-image-5.19.0-0.deb11.2-686-pae

Really great thing is, that this most recent backport kernel comes up with 
noveau driver properly now, this is first time I see noveau running mostly 
equivalent to old proprietary driver stuff from nvidia. Everything efficient, 
fast and fluent, clear view now. Great work, whoever did this, many thanks! 
This allows me now to switch to 5.x kernel series finally, dumping old nvidia 
proprietary driver stuff (which was single way to achieve this result until 
now). But unfortunately this doesn't fix Libreoffice issue all the same: The 
most recent Libreoffice bullseye version (not the one from backports) shows the 
originally described issue on all these kernels listed above. Only the 
Libreoffice backport doesn't show this behaviour any longer, CPU load from 
Libreoffice backport (details below) stays perfectly normal when it looses 
focus. Checked for several hours. Many thanks!

Maybe you can transfer the fix to the stable bullseye version, so people can 
run the default version instead of backports, in order to get security updates 
(above you've stated there are none on backports, which would be bad).


Technical details:

Version: 7.4.1.2 / LibreOffice Community
Build ID: 40(Build:2)
CPU threads: 1; OS: Linux 4.9; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Debian package version: 1:7.4.1-1~bpo11+2
Calc: threaded

$ apt-cache policy libreoffice* | grep -v '(keine)' | grep -B1 Installiert
libreoffice-calc:
  Installiert:   1:7.4.1-1~bpo11+2
libreoffice-base-core:
  Installiert:   1:7.4.1-1~bpo11+2
libreoffice-core:
  Installiert:   1:7.4.1-1~bpo11+2
libreoffice-common:
  Installiert:   1:7.4.1-1~bpo11+2
libreoffice-draw:
  Installiert:   1:7.4.1-1~bpo11+2
libreoffice-impress:
  Installiert:   1:7.4.1-1~bpo11+2
libreoffice-l10n-de:
  Installiert:   1:7.4.1-1~bpo11+2
libreoffice-style-colibre:
  Installiert:   1:7.4.1-1~bpo11+2
libreoffice-writer:
  Installiert:   1:7.4.1-1~bpo11+2
libreoffice-help-de:
  Installiert:   1:7.4.1-1~bpo11+2
libreoffice-help-common:
  Installiert:   1:7.4.1-1~bpo11+2
libreoffice-math:
  Installiert:   1:7.4.1-1~bpo11+2
libreoffice-gtk3:
  Installiert:   1:7.4.1-1~bpo11+2

ucf:
  Installiert:   3.0043
libabw-0.1-1:
  Installiert:   0.1.3-1
libc6:
  Installiert:   2.31-13+deb11u5
libe-book-0.1-1:
  Installiert:   0.1.3-2
libepubgen-0.1-1:
  Installiert:   0.1.1-1
libetonyek-0.1-1:
  Installiert:   0.1.9-4
libgcc-s1:
  Installiert:   10.2.1-6
libicu67:
  Installiert:   67.1-7
libodfgen-0.1-1:
  Installiert:   0.1.8-2
librevenge-0.0-0:
  Installiert:   0.0.4-6+b1
libstaroffice-0.0-0:
  Installiert:   0.0.7-1
libstdc++6:
  Installiert:   10.2.1-6
libuno-cppu3:
  Installiert:   1:7.0.4-4+deb11u4
libuno-cppuhelpergcc3-3:
  Installiert:   1:7.4.1-1~bpo11+2
libuno-sal3:
  Installiert:   1:7.4.1-1~bpo11+2
libuno-salhelpergcc3-3:
  Installiert:   1:7.0.4-4+deb11u4
libwpd-0.10-10:
  Installiert:   0.10.3-1
libwpg-0.3-3:
  Installiert:   0.3.3-1
libwps-0.4-4:
  Installiert:   0.4.12-1
libxml2:
  Installiert:   2.9.10+dfsg-6.7+deb11u2
uno-libs-private:
  Installiert:   1:7.4.1-1~bpo11+2
zlib1g:
  Installiert:   1:1.2.11.dfsg-2+deb11u2
fonts-opensymbol:
  Installiert:   2:102.12+LibO7.4.1-1~bpo11+2
ure:
  Installiert:   1:7.4.1-1~bpo11+2

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye

uname -r
4.9.0-326-antix.1-686-smp-pae
5.19.0-0.deb11.2-686-pae
and others, see listing in introductional text

$ lscpu
(same as above)

$ free
  gesamt   benutzt frei  gemns.  Puffer/Cache verfügbar
Speicher:2061064  196896  708752   26012 1155416 1771420
Swap:2097148   0 2097148


Regards
Robin



Bug#1022940: tiger: diff for NMU version 1:3.2.4~rc1-3.2

2022-10-27 Thread Francois Marier
Control: tags 1022940 + patch
Control: tags 1022940 + pending

Dear maintainer,

I've prepared an NMU for tiger (versioned as 1:3.2.4~rc1-3.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

Francois

-- 
https://fmarier.org/
diff -u tiger-3.2.4~rc1/debian/changelog tiger-3.2.4~rc1/debian/changelog
--- tiger-3.2.4~rc1/debian/changelog
+++ tiger-3.2.4~rc1/debian/changelog
@@ -1,3 +1,10 @@
+tiger (1:3.2.4~rc1-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: add symlink for Linux 6 (Closes: #1022940)
+
+ -- Francois Marier   Thu, 27 Oct 2022 21:35:23 -0700
+
 tiger (1:3.2.4~rc1-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u tiger-3.2.4~rc1/debian/rules tiger-3.2.4~rc1/debian/rules
--- tiger-3.2.4~rc1/debian/rules
+++ tiger-3.2.4~rc1/debian/rules
@@ -60,13 +60,15 @@
 	# Adjust the permissions of directories that might contain confidential information
 	chmod 0700 debian/tiger/var/lib/tiger/work
 	chmod 0700 debian/tiger/var/log/tiger
-	# Create symbolic links for Linux versions 3, 4, 5, and default
+	# Create symbolic links for Linux versions 3, 4, 5, 6 and default
 	[ -e debian/tiger/usr/lib/tiger/systems/Linux/3 ] || \
 		ln -fs 2 debian/tiger/usr/lib/tiger/systems/Linux/3
 	[ -e debian/tiger/usr/lib/tiger/systems/Linux/4 ] || \
 		ln -fs 2 debian/tiger/usr/lib/tiger/systems/Linux/4
 	[ -e debian/tiger/usr/lib/tiger/systems/Linux/5 ] || \
 		ln -fs 2 debian/tiger/usr/lib/tiger/systems/Linux/5
+	[ -e debian/tiger/usr/lib/tiger/systems/Linux/6 ] || \
+		ln -fs 2 debian/tiger/usr/lib/tiger/systems/Linux/6
 	[ -e debian/tiger/usr/lib/tiger/systems/Linux/default ] || \
 		ln -fs 2 debian/tiger/usr/lib/tiger/systems/Linux/default
 	# Remove unneeded Makefile files.


Bug#1022848: linux: 6.0.5 fixes critical btrfs bug

2022-10-27 Thread Salvatore Bonaccorso
Control: severity -1 serious

Hi Christoph,

Thanks for the quick feedback!

On Thu, Oct 27, 2022 at 09:10:53PM +0200, Christoph Anton Mitterer wrote:
> Am 27. Oktober 2022 20:56:49 MESZ schrieb Salvatore Bonaccorso 
> :
> >According to your references there is the workaround of mounting  with
> >clear_cache,space_cache=v2 and convert the filesystem.
> >
> >What would one prevent doing so?
> 
> v2 space cache is still rather new and had only recently some bug
> that could have caused catastrophic data corruption... so not
> everyone might want to switch.
> 
> Similarly,  people may want to have these filesystems mounted with
> older kernels, whose v2 support isn't that good yet. 

Thanks, this is very important input.

> >I'm downgrading the severity to important as it does not make the
> >kernel unbootable or unstable on common hardware or all systems that a
> >flavour is supposed to support. 
> 
> But now it a) migrates to testing an possibly leaves even more
> systems with an unbootable system... b) with severity important,
> people using e.g. apr-listbugs won't see it.
> 
> OTOH, fixing the CVE is of course important, too.

I did decide to still do so, so we can have the CVE fix migrate
finally to testing (which took some time as well given there was the
perl transition ongoing). 

I did import already 6.0.5 and will upload next so we get the btrfs
fix. And I have made the bug now as well again back RC severity.

Thank you!

Regards,
Salvatore



Bug#1022940: tiger doesn't support version 6 of the Linux kernel properly

2022-10-27 Thread Francois Marier
Package: tiger
Version: 1:3.2.4~rc1-3.1
Severity: important

While there is a `default` symlink in /usr/lib/tiger/systems/Linux/, it
doesn't seem to work because I received a very large number of bogus
warnings after upgrading to Linux 6:

NEW: --WARN-- [lin003w] The process `NetworkMa' is listening on socket 24455 
(raw6 on 24455 interface) is run by root.
NEW: --WARN-- [lin003w] The process `NetworkMa' is listening on socket 28195 
(IPv6 on 28195 interface) is run by 1596.
NEW: --WARN-- [lin003w] The process `NetworkMa' is listening on socket 28195 
(IPv6 on 28195 interface) is run by 1599.
NEW: --WARN-- [lin003w] The process `NetworkMa' is listening on socket UDP (0t0 
on UDP interface) is run by root.
NEW: --WARN-- [lin003w] The process `NetworkMa' is listening on socket raw6 
(root on raw6 interface) is run by 1596.
NEW: --WARN-- [lin003w] The process `NetworkMa' is listening on socket raw6 
(root on raw6 interface) is run by 1599.
NEW: --WARN-- [lin003w] The process `apache2' is listening on socket TCP (0t0 
on TCP interface) is run by root.
NEW: --WARN-- [lin003w] The process `apache2' is listening on socket TCP (0t0 
on TCP interface) is run by www-data.
NEW: --WARN-- [lin003w] The process `avahi-dae' is listening on socket UDP (0t0 
on UDP interface) is run by avahi.
NEW: --WARN-- [lin003w] The process `cupsd' is listening on socket TCP (0t0 on 
TCP interface) is run by root.
NEW: --WARN-- [lin003w] The process `dnsmasq' is listening on socket TCP (0t0 
on TCP interface) is run by dnsmasq.
NEW: --WARN-- [lin003w] The process `dnsmasq' is listening on socket UDP (0t0 
on UDP interface) is run by dnsmasq.
...

The fix is to create a symlink for version 6 of the kernel explicitly:

  cd /usr/lib/tiger/systems/Linux/
  sudo ln -s 5 6

Francois

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

Kernel: Linux 6.0.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (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 tiger depends on:
ii  binutils   2.39-8
ii  bsdutils   1:2.38.1-1.1+b1
ii  debconf [debconf-2.0]  1.5.79
ii  debianutils5.7-0.3
ii  libc6  2.35-3
ii  lsb-release12.0-1
ii  net-tools  1.60+git20181103.0eebece-1
ii  ucf3.0043

Versions of packages tiger recommends:
ii  chkrootkit  0.55-4+b2
pn  john
ii  postfix [mail-transport-agent]  3.7.3-2
pn  tripwire | aide 

Versions of packages tiger suggests:
ii  lsof   4.95.0-1
ii  lynis  3.0.8-1.1

-- Configuration Files:
/etc/cron.d/tiger [Errno 13] Permission non accordée: '/etc/cron.d/tiger'

-- debconf information:
* tiger/mail_rcpt: root
* tiger/policy_adapt:

-- 
https://fmarier.org/



Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists

2022-10-27 Thread Felix Miata
Oland [Radeon HD 8570 / R5 430 OEM R7 240/340 Radeon 520 OEM]
vendor: Dell driver: radeon v: kernel arch: GCN-1 pcie: speed: 2.5 GT/s
lanes: 8 ports: active: DP-1,DVI-I-1 empty: none bus-ID: 01:00.0
chip-ID: 1002:6611

Same failure as in my previous comment #45 about GCN2. In Bullseye in both PCs,
workaround is to omit 'plymouth.enable=0 radeon.si_support=1' from linu line in
Grub, which absent installation of radeon DDX, forces use of modesetting DIX
instead of amdgpu DDX, which was working just fine until
linux-image-5.10.0-19-amd64 was installed. The resulting change in display 
output
names requires the xrandr script locating all the displays to be rewritten. On
this one I've not as yet attempted installation of backport kernel.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata



Bug#1022939: linux-image-6.0.0-2-amd64: 6.0.0-2-amd64 regressions: Lenovo Carbon X1 gen7 can't suspend, sound card not instantiated

2022-10-27 Thread Akkana Peck
Package: src:linux
Version: 6.0.3-1
Severity: important
X-Debbugs-Cc: d...@shallowsky.com

Dear Maintainer,

As of a sid full-upgrade two days ago (Tue Oct 25), I'm seeing two
regressions on my Lenovo Carbon X1 gen7:

- systemctl suspend no longer works: instead of suspending, it freezes,
  and I have to hold the power button for 10 seconds to force a power down
- the laptop's built-in sound card (intel, using the firmware-intel-sound
  package) is no longer seen. In dmesg there's a "failed to instantiate
  card" error

Both of these were working fine as of a system update a day or two earlier.

The problem seem to be due to 6.0.0-2-amd64. If I reboot into my old
kernel, 6.0.0-1-amd64, the sound card is found and suspend works.

I hope it's not too presumptuous to put these both in the same error
report; they seem very different but they happened at the same time
and they're both cured by using the old kernel.

For the suspend problem, I'm not sure how to debug a freeze or what
additional info would be useful, but I'm happy to run any tests you suggest.

For the sound card problem, pacmd list-sinks prints what seems to be a
placeholder in the absence of finding an actual sound card (and the same
for list-sources, it doesn't see the mic either):

$ pacmd list-sinks
1 sink(s) available.
  * index: 0
name: 
driver: 
flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE
priority: 1000
volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 0.00 ms
max request: 375 KiB
max rewind: 375 KiB
monitor source: 0
sample spec: s16le 2ch 48000Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 0
configured latency: 0.00 ms; range is 0.50 .. 2000.00 ms
module: 11
properties:
device.description = "Dummy Output"
device.class = "abstract"
device.icon_name = "audio-card"

Here's the same command under 6.0.0-1-amd64 (where sound works):

$ pacmd list-sinks
2 sink(s) available.
index: 0
name: 
driver: 
flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE
priority: 9030
volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 0.00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 0
sample spec: s16le 2ch 48000Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 0
configured latency: 0.00 ms; range is 0.50 .. 341.33 ms
module: 0
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = ""
alsa.id = "HDA Analog (*)"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "sof-hda-dsp"
alsa.long_card_name = "LENOVO-20QDCTO1WW-ThinkPadX1Carbon7th"
alsa.driver_name = "snd_soc_skl_hda_dsp"
device.bus_path = 
"pci-:00:1f.3-platform-skl_hda_dsp_generic"
sysfs.path = 
"/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "9dc8"
device.product.name = "Cannon Point-LP High Definition Audio 
Controller"
device.string = "hw:0,0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "16384"
device.access_mode = "mmap+timer"
device.description = "Cannon Point-LP High Definition Audio 
Controller"
device.icon_name = "audio-card-pci"
  * index: 1
name: 

driver: 
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE
priority: 9030
volume: front-left: 64155 /  98% / -0.55 dB,   front-right: 64155 /  
98% / -0.55 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 0.00 ms
max request: 0 KiB
max rewind: 0 KiB

Bug#1022938: ITP: junit-clptr -- ClassLoader per Test runner for JUnit 4.12+ based on myfaces-test "TestPerClassLoaderRunner".

2022-10-27 Thread sunmin
Package: wnpp
Severity: wishlist
Owner: sunmin 
X-Debbugs-Cc: debian-de...@lists.debian.org,debian-j...@lists.debian.org

* Package name: junit-clptr
  Version : 1.2.2
  Upstream Author : Pino Silvaggio
* URL : https://github.com/bitstrings/junit-clptr
* License : Apache License 2.0 
  Programming Lang: Java 
  Description : ClassLoader per Test runner for JUnit 4.12+ based on 
myfaces-test "TestPerClassLoaderRunner".

ClassLoader per Test runner for JUnit 4.12+ based on myfaces-test 
"TestPerClassLoaderRunner".

Each test method will run with its very own ClassLoader which can be very 
useful for a variety of use cases (testing classes with static fields for 
example).

Maven dependency

  org.bitstrings.test
  junit-clptr
  1.2.2

Usage
import org.bitstrings.test.junit.runner.ClassLoaderPerTestRunner;

@RunWith( ClassLoaderPerTestRunner.class )
public class Test
{
  ...
}
Exclude classes using @ClptrExclude annotation
You can exclude a package or a specific class.

@RunWith( ClassLoaderPerTestRunner.class )
@ClptrExclude( "mockit." )
public class Test
{
...
}
@RunWith( ClassLoaderPerTestRunner.class )
@ClptrExclude( { "mockit.", "org.somethings.MyClass" } )
public class Test
{
...
}
You may use @ClptrExclude on classes and methods.

Globally exclude classes from isolation using file
Use the default file clptr-excludes.properties to add excluded packages or 
classes from isolation.

The file should be on the classpath.

You can override the excludes file location using the system property 
org.bitstrings.test.junit.runner.TestClassLoader.excludes.

org.bitstrings.test.junit.runner.TestClassLoader.excludes=com/company/res/clptr-excludes.properties
The file is simply a list of packages and classes (see @ClptrExclude):

jmockit.
org.apache.
com.company.test.TestClass
What's new
@ClptrExclude annotation;
Fix for "@Rule" annotated field and method;
Threadsafe (Hopeful...);
Support excludes.


This package is a new dependency of the latest upstream 
libcommons-validator-java v1.7 
(https://github.com/apache/commons-validator/releases/tag/VALIDATOR_1_7)



Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists

2022-10-27 Thread Felix Miata
5.10.149-2 produced no improvement for my A10-7850K Radeon R7.

5.19.0-0.deb11.2-amd64 solves the problem for me, which is no surprise given
Bookworm has been working fine on same PC using its latest 5.19 kernel.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata



Bug#1022025: Fwd: Bug#1022051: Acknowledgement (linux-image-5.10.0-19-amd64: no boot possible)

2022-10-27 Thread Felix Miata
On Sun, 23 Oct 2022 10:12:17 +0200 Michael Becker wrote:

> 5.10.149-2 solved the problem 

5.10.149-2 was no help with A10-7850K Radeon R7.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata



Bug#1022937: RFP: aws-sdk-go-v2 -- AWS SDK for the Go programming language, version 2

2022-10-27 Thread Noah Meyerhans
Package: wnpp
Severity: wishlist

* Package name: aws-sdk-go-v2
  Version : 2022-10-27
  Upstream Author : Amazon Web Services (https://aws.amazon.com/)
* URL : https://github.com/aws/aws-sdk-go-v2
* License : Apache 2.0
  Programming Lang: Go
  Description : AWS SDK for the Go programming language, version 2

aws-sdk-go-v2 is a replacement for the original AWS SDK for go, currently
packaged as golang-github-aws-aws-sdk-go.  Version 2 uses a more modular
interface consistent with current Go packaging idioms.

A number of applications packaged by Debian have migrated to the v2 SDK,
including amazon-ecr-credential-helper, which I'm looking to update.



Bug#664396: vsdump: Helping to update to packaging format 3.0

2022-10-27 Thread Ralf Treinen
Raising severity to serious as dpatch is now removed from sid, which
makes the package FTBFS.

-Ralf.



Bug#1022705: unplanned transition: ghostscript

2022-10-27 Thread Sebastian Ramacher
On 2022-10-24 15:15:09 +0200, Jonas Smedegaard wrote:
> > Also, it would have been nice to disentangle the -common rename from the 
> > SONAME 
> > bump.
> 
> Yes, I agree that would have been more elegant.

I have uploaded a new version that partially reverts the change.
Unfortunately, libgs9-common contained the unversioned ICC profiles, so
we will end up some Breaks+Replaces for the bullseye to bookworm
upgrade. With that in mind, the new version keeps the ICC profiles in
libgs-common and the version specific files are moved back to
libgs10-common.

Cheers
-- 
Sebastian Ramacher



Bug#1022936: usrmerge: Suggestion to add Conflicts: on old 'kbd' version 2.0.3-2+b1 from stretch (debian 9) that provides /bin/open

2022-10-27 Thread Vasily Galkin
Package: usrmerge
Version: 33
Severity: important

Dear Maintainer,

I have and debian8-based install with most-but-not-all packages updated to
random releases, but the `kbd` package wasn't updated from stretch version
2.0.3-2+b1.
Trying to install usrmerge lead to following error message:

```
Setting up usrmerge (33) ...

FATAL ERROR:
Both /bin/open and /usr/bin/open exist.

You can try correcting the errors reported and running again
/usr/lib/usrmerge/convert-usrmerge until it will complete without errors.
Do not install or update other Debian packages until the program
has been run successfully.

E: usrmerge failed.
```

I suggest adding conflicts declaration to usrmerge to avoid installing it
before kbd is upgraded at least version 2.0.4-4 from buster.

I understand that such mixed package updates are discouraged, but really I have
tons of modern work software installed fine and the rule "if apt
doesn't show any incompatibilities - it will work fine" - works in 99% cases.
This is what makes debian reliable)
For the last 1% of a cases a manual intervention is needed. Most of the times I
didn't report such oldoldstable incompatibility bugs, but usrmerge is special -
its error message explicitly states that I shouldn't update any packages, but
manual resolution that I intuitively do - would be updating kbd - exactly the
opposite behavior. So its unobvious what to do even for experienced user.


Actually after manually executing `sudo apt install kbd` it seems that usrmerge
succeeded.

```
Preparing to unpack .../archives/kbd_2.5.1-1_amd64.deb ...
Unpacking kbd (2.5.1-1) over (2.0.3-2+b1) ...
Setting up usrmerge (33) ...
The system has been successfully converted.
Setting up kbd (2.5.1-1) ...
Processing triggers for man-db (2.10.1-1~bpo11+1) ...
```

After this I ran `sudo apt install --reinstall kbd` second time to be sure that
upgrading it before usrmerge was setup



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

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

Versions of packages usrmerge depends on:
ii  libfile-find-rule-perl  0.34-1
ii  perl5.32.1-6

usrmerge recommends no packages.

usrmerge suggests no packages.

-- no debconf information



Bug#1022935: gcc-12: libstd++6.symbols.armel is missing GLIBCXX_3.4.30

2022-10-27 Thread Sebastian Ramacher
Source: gcc-12
Version: 12.2.0-7
Severity: normal
Tags: patch
X-Debbugs-Cc: sramac...@debian.org

Not sure why libstdc++6 has a different symbols file on armel
(especially since debian/libstdc++.symbols also mentions armel), but
debian/libstdc++6.symbols is not up-to-date. At least a symbol for
GLIBCXX_3.4.30 is missing there and hence the installed symbols file
has a the current debian version as minimal version. Consequently,
almost any non-trivial package depending on libstd++6 on armel gets to
tight dependencies. Whenever gcc-12 is unable to migrate for some time,
packages get stuck in unstable due to that.

The attached patch adds the missing symbol on armel. Please consider
applying the patch soon.

Thanks for considering
Cheers
-- 
Sebastian Ramacher
diff -Nru gcc-12-12.2.0/debian/libstdc++6.symbols.armel gcc-12-12.2.0/debian/libstdc++6.symbols.armel
--- gcc-12-12.2.0/debian/libstdc++6.symbols.armel	2020-11-28 12:48:09.0 +0100
+++ gcc-12-12.2.0/debian/libstdc++6.symbols.armel	2022-10-28 00:32:56.0 +0200
@@ -45,3 +45,4 @@
  (symver)GLIBCXX_3.4.27 9.1
  (symver)GLIBCXX_3.4.28 10.2
  (symver)GLIBCXX_3.4.29 11
+ (symver)GLIBCXX_3.4.30 12


Bug#959498: efibootmgr: Any new progress on this report?

2022-10-27 Thread Manuel A. Fernandez Montecelo
Control: tags -1 + pending

Hi,

On Mon, 26 Sept 2022 at 19:24, Yifan Xu  wrote:
>
> Dear Maintainer,
>
> Any new progress on this report? The code is same as the ubuntu version, and 
> EFI support on riscv will need this package.
>
> Thank you.
>
> Yifan Xu

It seems that the current source in Salsa [1] already contains the
architecture field for riscv64, and another few new ones.

To the maintainers: It would be great if you could make a new release,
if you need any help from porters please let us know.


[1] https://salsa.debian.org/efi-team/efibootmgr/-/blob/debian/debian/control


Cheers.
-- 
Manuel A. Fernandez Montecelo 



Bug#1022934: libpappsomspp: FTBFS on i386

2022-10-27 Thread Sebastian Ramacher
Source: libpappsomspp
Version: 0.8.55-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=libpappsomspp=i386=0.8.55-1%2Bb1=1666460310=0

term_listb.size= 8
 MOD:00397 mass=57.021463721083
 MOD:00429 mass=28.031300128964
 MOD:00382 mass=-20.026214748524
 MOD:00234 mass=305.068156389475
 MOD:00838 mass=3.018830236677
 A 71.037113785565
 R 156.10025652
 C 103.009184959665
 D 115.026943024685
 E 129.042593089167
 F 147.068413914529
 G 57.021463721083
 H 137.058911859647
 I 113.084063979011
 K 128.094963016052
 L 113.084063979011
 M 131.040485088629
 N 114.042927442166
 P 97.052763850047
 Q 128.058577506648
 R 156.10025652
 S 87.032028405125
 T 101.047678469607
 V 99.068413914529
 W 186.07931295157
 Y 163.063328534089
 U 168.964198469607
 O 255.158291550141
0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 
0% 
0% 10% 20% 

..:: Test 1 OK ::..

..:: second test, new calibration parameters ::..

..:: Test 2 OK ::..
===
test cases:  32 |  31 passed | 1 failed
assertions: 345 | 343 passed | 2 failed



94% tests passed, 1 tests failed out of 18

Total Test time (real) =   3.47 sec

The following tests FAILED:
  1 - catch2-only-tests (Failed)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8

Cheers
-- 
Sebastian Ramacher



Bug#1004638: openjfx: diff for NMU version 11.0.11+0-1.1

2022-10-27 Thread Sebastian Ramacher
[Note that mails to nnn...@bug.debian.org does not reach the submitter.]

On 2022-10-26 18:33:39 +0200, Emmanuel Bourg wrote:
> Le 26/10/2022 à 01:27, Sebastian Ramacher a écrit :
> 
> > Dear maintainer,
> > 
> > I've prepared an NMU for openjfx (versioned as 11.0.11+0-1.1) and
> > uploaded it to DELAYED/2. Please feel free to tell me if I
> > should delay it longer.
> 
> Hi Sebastian,
> 
> Thank you for the update, but could you send a PR on Salsa instead of
> uploading NMUs please?

As there is no bookworm branch (or something similar) available, I
cannot create a PR on salsa. You can take the changes from
https://salsa.debian.org/sramacher/openjfx/-/tree/bookworm

Cheers
-- 
Sebastian Ramacher



Bug#937049: mini-buildd: Python2 removal in sid/bullseye

2022-10-27 Thread Moritz Mühlenhoff
Am Fri, Aug 30, 2019 at 07:26:40AM + schrieb Matthias Klose:
> Package: src:mini-buildd
> Version: 1.0.41
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
> 
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html

How close is the 2.x branch in experimental from being a replacement?
python2 will be dropped in bookworm and also removed from the archive.

Cheers,
Moritz



Bug#1022933: gnome-session-common: gnome-mimeapps.list still points to org.gnome.gedit.desktop

2022-10-27 Thread Sven Geuer
Package: gnome-session-common
Version: 43.0-1
Severity: normal

Dear Maintainer,

gedit has been replaced by gnome-text-editor. Consequently references to
org.gnome.gedit.desktop should be replaced by org.gnome.TextEditor.desktop in
gnome-mimeapps.list.

Double-clicking a text file in nautilus used to open the file in gedit in my
environment, which was the default before if I remember correctly, while now it
opens the file in a terminal window running vim what is not ideal.


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

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

-- no debconf information



Bug#1022932: Should fbpanel be removed?

2022-10-27 Thread Moritz Muehlenhoff
Source: fbpanel
Version: 7.0-4.3
Severity: serious

Your package came up as a candidate for removal from Debian:
- Depends on Python 2, which will soon be removed
- Last maintainer upload five years ago
- Dead upstream

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz



Bug#1022931: Should viewmol be removed?

2022-10-27 Thread Moritz Muehlenhoff
Source: viewmol
Version: 2.4.1-26
Severity: serious

Your package came up as a candidate for removal from Debian:
- Still depends on Python 2 (which will soon be removed)
- Dead upstream
- Dropped from testing for over two years


If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz



Bug#1022930: ITP: golang-github-iancoleman-strcase -- converting string case to various cases

2022-10-27 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: golang-github-iancoleman-strcase
  Version : 0.2.0
  Upstream Author : Ian Coleman 
* URL : https://github.com/iancoleman/strcase
* License : Expat
  Programming Lang: Golang
  Description : converting string case to various cases

 Strcase is a go package for converting string case to various cases (like
 snake case, or camel case). Strcase can deal with common acronyms that it
 knows it shouldn't modify.

Note: this is a dependency for mgmt-config that I'm packaging.



Bug#1022248: transition: icu

2022-10-27 Thread Sebastian Ramacher
Control: tags -1 moreinfo
Control: forwarded -1 https://release.debian.org/transitions/html/icu72.html

On 2022-10-22 19:17:58 +0200, László Böszörményi wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hi RMs,
> 
> My intention is to release Bookworm with ICU 72.1 which is already
> packaged and is in experimental. As Sid has the previous,71.1 release
> the transition is plain, I don't expect any breakage. The rebuilds are
> ongoing and only level1 and level2 are ready at this time.
> Transition is similar to the previous ones, this time boost1.74 needs
> to be binNMUed after level1 before other level2 packages and pyicu
> will need a sourceful upload (its Git version seems to be ready, but I
> wait for its release).

I've set up the tracker. Please remove the moreinfo tag once the test
builds are done.

Cheers

> 
> The only FTBFS is from the Sid version of nodejs (18.10.0+dfsg-6) due
> to a flaky self-test - its experimental version (18.11.0+dfsg-3)
> doesn't suffer from it. I will post more when I build all levels of
> the transition.
> 
> Regards,
> Laszlo/GCS
> 

-- 
Sebastian Ramacher



Bug#609426: runit-services: memory limit too low to send email

2022-10-27 Thread Lorenzo
Control: tags -1 moreinfo unreproducible

Hello,

On Sun, 09 Jan 2011 14:09:05 +0100 Lorenzo Beretta
 wrote:
> Package: runit-services
> Version: 0.4.0
> Severity: minor
> 
> It fails with
> 2011-01-09_12:49:07.17058 /usr/lib/sendmail: error while loading
> shared libraries: libcrypt.so.1: failed to map segment from shared
> object: Cannot allocate memory
> 
The package currently imposes no limit to services except for dhclient.
Even with the old version (0.4.0) exim and postfix had no memory limits;
so I can't tell, which service is/was affected?

> 
> -- Configuration Files:
> /etc/sv/chrony/run changed [not included]
> 
if the reported message came from the chrony service, this is fixed in
0.5.0.

I intend to close this bug on timeout unless someone can reproduce with
0.5.0 and posts more details.

Lorenzo



Bug#1022857: [PATCH] printf: with \U syntax, support all valid unicode points

2022-10-27 Thread Pádraig Brady

On 27/10/2022 21:46, Bernhard Voelker wrote:

On 10/27/22 16:41, Pádraig Brady wrote:

Previously this was restricted to the C standard subset
which restricted most values <= 0x9F, as that simplifies the C lexer.
However printf(1) doesn't need this restriction.
Note also the bash builtin printf already supports all values <= 0x9F.


Nice one.

BTW: do we also want to support the new modifier that bash has since version 
5.2?

r. The `printf' builtin has a new format specifier: %Q. This acts like %q 
but
  applies any specified precision to the original unquoted argument, then
  quotes and outputs the result.


That does sound useful.
However we yet don't support qualifiers on %q
which would need to come first.

  $ printf '%.4q\n' 'sp ace'  # builtin
  sp\

  $ env printf '%.4q\n' 'sp ace'
  printf: %.4q: invalid conversion specification

cheers,
Pádraig



Bug#1022929: ITP: golang-github-coredhcp-coredhcp -- multithreaded, modular and extensible DHCP server

2022-10-27 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: golang-github-coredhcp-coredhcp
  Version : 0.0.0+git.2022.04.07.a2552c5c1b
  Upstream Author : The CoreDHCP Authors
* URL : https://github.com/coredhcp/coredhcp
* License : Expat
  Programming Lang: Golang
  Description : multithreaded, modular and extensible DHCP server

 Coredhcp is a fast, multithreaded, modular and extensible DHCP server written
 in Go. In CoreDHCP almost everything is implemented as a plugin. Every request
 is evaluated calling each plugin in order, until one breaks the evaluation and
 responds to, or drops, the request.

Note: this is a dependency of mgmt-config that I'm packaging.



Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists

2022-10-27 Thread Diederik de Haas
On woensdag 26 oktober 2022 12:43:02 CEST Alexis Huxley wrote:
> Following other reports of post-grub kernel hangs on systems with
> amdgpu, I waited for new release of linux-image-5.10.0-19-amd64,
> which came quickly, but it did not solve the problem for me.
> 
> Symptoms are: grub loads kernel and a few seconds into the
> scrolling messages from the kernel the system hangs. The screen
> is blank. The system is not accessible over the network.

AFAICT, which may be incorrect, the issue is slightly different from the other 
related bug report (#1022042) in that here it is a system which does not boot.
The other problem that is fixed, is where the system does boot, but the 
graphics don't work correctly.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042#105 is where Andreas 
Wirooks (See also https://gitlab.freedesktop.org/drm/amd/-/issues/
2216#note_1601632) reported on that/this issue and in msg 110 'inasprecali' 
reported the same issue (AFAICT). See also the msgs that follow, which may 
give hints as to where the non-boot issue may come from.

It _may_ also be related to older chipset variants.

HTH,
  Diederik

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


Bug#1022928: ITP: golang-github-d-tux-go-fstab -- simple fstab parser

2022-10-27 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: golang-github-d-tux-go-fstab
  Version : 0.0.0+git.2014.12.04.eb4090f265
  Upstream Author : Denis Wernert 
* URL : https://github.com/d-tux/go-fstab
* License : BSD-3-clause
  Programming Lang: Golang
  Description : simple fstab parser

 This Go package provides a /etc/fstab parser, and facitities to be able to
 mount and unmount. It supports UUID, labels, partuuid, parlabel, nfs, swap,
 and more.

Note: This is a dependency for mgmt-config



Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists

2022-10-27 Thread Alexis Huxley
Hi All,

> Would you be able to start own kenel builds, confirming it does not
> happen with 5.10.140 upstream but with 5.10.149, and isolate the
> breaking change?
> 
> (Are you able to boot the kernel from bullseye-backports?)

I will try to do this, but owing to my schedule, it will
be only Tuesday before I can try.

If you did the kernel building and sent me download links
then I can test them, which is obviously a lot less work
for me, but a lot more for you. Otherwise I'll let you
know how I get on next week.

Sorry to have submitted tbe report and then immediatey not
be available to do the followup.

Regards,

Alexis



Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists

2022-10-27 Thread Salvatore Bonaccorso
Hi Alexis,

[Cc'ing Alex Deucher who addressed the previous regressions as well]

On Wed, Oct 26, 2022 at 12:43:02PM +0200, Alexis Huxley wrote:
> Package: src:linux
> Version: 5.10.149-2
> Severity: serious
> Justification: 1022025, 1022051, 1022062, 1022070, 1022097, 1022147 marked 
> serious so this marked serious too
> 
> Dear Maintainer,
> 
> Following other reports of post-grub kernel hangs on systems with
> amdgpu, I waited for new release of linux-image-5.10.0-19-amd64,
> which came quickly, but it did not solve the problem for me.
> 
> Symptoms are: grub loads kernel and a few seconds into the 
> scrolling messages from the kernel the system hangs. The screen
> is blank. The system is not accessible over the network.
> 
> I reverted to linux-image-5.10.0-18-amd64 and all is okay again.
> 
> The crash happens pretty early on: I believe X has not yet tried
> to start. Both /var/log/syslog and /var/log/messages contain
> no entries pertaining to the hanging boot (only messages from
> where the earlier shutdown of 18 and the later start of 18).
> 
> Output from lscpu is below.
> 
> Automatically included output (e.g. kernel version) pertains
> to linux-image-5.10.0-18-amd64, as I am unable to boot
> linux-image-5.10.0-19-amd64.  I don't remove it in case it contains
> other pertinent information.
> 
> I'm happy to test with other kernels or provide any requested
> files/output.

Would you be able to start own kenel builds, confirming it does not
happen with 5.10.140 upstream but with 5.10.149, and isolate the
breaking change?

(Are you able to boot the kernel from bullseye-backports?)

Regards,
Salvatore



Bug#1019425: dkms 3.0.6-2 not signing modules

2022-10-27 Thread Siddh Raman Pant
On Thu, 27 Oct 2022 20:31:47 +0200, Maurizio Avogadro  
wrote:> Hi Siddh
> 
> since dkms is supposed to run as root, it's not clear to me which keyring is 
> the signing key passphrase going to be stored to. I definitely wouldn't 
> recommend running Gnome/KDE keyrings as root, and user keyrings seem to be 
> unreachable via D-bus in a console where root has been gained with su 
I used libsecret (which is used as backend by the Python program named keyring),
with the keyring being stored as root (isn't visible outside root in seahorse).
Can you tell why that may be a bad idea?

Anyways, the main point was that one can use a bash script. The keyring usage
was just a personal config choice for convenience, one can use other methods
for getting the passphrase from the user.

> BTW, by adding a configuration snippet in /etc/dkms/framework.conf.d/ 
> containing
> 
> export KBUILD_SIGN_PIN='my_mok_key_pin'
> 
> (permissions 600 recommended) seems to work 

I won't really want to store password in plaintext...

> (given the kernel you are running 
> is configured to use the SHA512 hash algorithm; official Debian kernels use 
> SHA256 [1]).

I didn't know that, thanks.

> We also have to face the problem that only official Debian kernels store the 
> sign-file executable in
> 
> /usr/lib/linux-kbuild-${kernelver%.*}/scripts/
> 
> where dkms looks in Debian: Xanmod and Liquorix for example store this file in
> 
> /usr/src/linux-headers-${kernelver}/scripts/
> 
> but this path can't be easily changed in current dkms version (v3.0.6-4) 
> because the $kernelver variable isn't available when sourcing the 
> configuration 
> files; dkms in current master tree fixed this issue by adding a fallback to
> 
> /lib/modules/${kernelver}/build/scripts/
> 
> in distro detection code, which makes signing work with any kernel I could 
> test 
> till now.

What I pointed out was setting sign_file to a bash script. It would solve this
issue too, as the correct path to the actual sign_file binary could be used in
the bash script / handler. dkms would call the bash script with its arguments,
and the script will call the correct binary (passing the arguments to it), as
$kernelver variable would be available to the script.

Also, v3.0.6-4 seems to have the fallback you mentioned. Refer:
https://salsa.debian.org/debian/dkms/-/blob/debian/3.0.6-4/dkms.in#L870

Thanks,
Siddh



Bug#1022927: libghc-aeson-dev depends on non-existing libghc-semialign-dev-1.2.0.1-ebc3a

2022-10-27 Thread Ralf Treinen
Package: libghc-aeson-dev 
Version: 2.0.3.0-1+b4
Severity: serious

Hi,

libghc-aeson-dev on amd64c depends on libghc-semialign-dev-1.2.0.1-ebc3a
which does not exist in the archive. The situation is the same on other
arches with a different hash of libghc-semialign-dev-1.2.0.1.

-Ralf.



Bug#1020087: guile-ssh: FTBFS: dh_auto_test: error: cd debian/build/guile-3.0 && make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2

2022-10-27 Thread Vagrant Cascadian
Control: forwarded 1020087 https://github.com/artyom-poptsov/guile-ssh/issues/34

On 2022-09-18, Lucas Nussbaum wrote:
>> make[5]: Entering directory '/<>/debian/build/guile-3.0/tests'
>> PASS: log.scm
>> FAIL: server.scm
>> PASS: session.scm
>> FAIL: client-server.scm
>> PASS: popen.scm
>> PASS: shell.scm
>> PASS: server-client.scm
>> PASS: sssh-ssshd.scm
>> FAIL: key.scm
>> PASS: tunnel.scm
>> PASS: dist.scm
>> 
>>Guile-SSH 0.13.1: tests/test-suite.log
>> 
>> 
>> # TOTAL: 11
>> # PASS:  8
>> # SKIP:  0
>> # XFAIL: 0
>> # FAIL:  3
>> # XPASS: 0
>> # ERROR: 0

I believe this is due to the new libssh 0.10.x version introduced middle
of september 2022 and compatibility issues in guile-ssh's test suite.

I've confirmed the issue on guile-ssh 0.13.x, 0.15.x and 0.16.x locally,
and the reproducible builds tests also confirm this rough timing:

  https://tests.reproducible-builds.org/debian/history/amd64/guile-ssh.html

Forwarded the bug upstream.

live well,
  vagrant


signature.asc
Description: PGP signature


Bug#1022806: Bug#1022025: fixed in linux 5.10.149-2

2022-10-27 Thread Salvatore Bonaccorso
Hi,

On Thu, Oct 27, 2022 at 07:12:43PM +, inasprecali wrote:
> On Thu, 27 Oct 2022 21:01:15 +0200 Salvatore Bonaccorso
>  wrote:
> > Can you please fill a new bug for your issue, which would still
> > be
> > present in the 5.10.149-2 release? There are two users which
> > report
> > that they still have problems with the amdgpu driver still in
> > 5.10.149-2.
> 
> I think bug 1022806 is a recent one referring to 5.10.149-2
> specifically, which is about this same issue.  I don't think there
> is a need to report yet another bug about it.

Yes this is indeed enough.

Regards,
Salvatore



Bug#1022926: transition: glibc 2.36

2022-10-27 Thread Aurelien Jarno
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: debian-gl...@lists.debian.org

Dear release team,

I would like to get a transition slot for glibc 2.36. It has been
available in experimental for a bit more than one month and does not
have any known major issue. It has been built successfully on all
release architectures and many ports architectures. A few issues found
through the autopkgtest pseudo excuses for experimental have been fixed.
The remaining ones are due to britney bugs, broken autopkgtest or
packages parts of the transition.

As glibc is using symbol versioning, there is no soname change. That
said a few packages are using libc internal symbols and have to be
rebuilt for this transition. Here is the corresponding ben file:

  title = "glibc";
  is_affected = .depends ~ /libc[0-9.]* \(<

Bug#1022848: linux: 6.0.5 fixes critical btrfs bug

2022-10-27 Thread Christoph Anton Mitterer



Am 27. Oktober 2022 20:56:49 MESZ schrieb Salvatore Bonaccorso 
:
>According to your references there is the workaround of mounting  with
>clear_cache,space_cache=v2 and convert the filesystem.
>
>What would one prevent doing so?

v2 space cache is still rather new and had only recently some bug that could 
have caused catastrophic data corruption... so not everyone might want to 
switch.

Similarly,  people may want to have these filesystems mounted with older 
kernels, whose v2 support isn't that good yet. 


>I'm downgrading the severity to important as it does not make the
>kernel unbootable or unstable on common hardware or all systems that a
>flavour is supposed to support. 

But now it a) migrates to testing an possibly leaves even more systems with an 
unbootable system... b) with severity important, people using e.g. apr-listbugs 
won't see it.

OTOH, fixing the CVE is of course important, too.


Cheers, 
Chris.



Bug#1022925: nheko: Version in bullseye(-backports) is vulnerable to DoS and secret poisoning

2022-10-27 Thread Val Lorentz

Package: nheko
Version: 0.9.3-2~bpo11+1
Severity: important

Dear maintainers,


Since version 0.9.3 (currently in bullseye-backports), Nheko fix at 
least two major issues:


1. Crash on events with oversized state key, when used with Synapse

https://github.com/Nheko-Reborn/nheko/issues/1172

In particular, because such an event was sent to Nheko's official 
support room (#nheko:nheko.im), it means Nheko is unusable with any 
account joined to that room, showing an endless spinner on startup.


This was fixed in v0.10.1:

* 
https://github.com/Nheko-Reborn/nheko/commit/47189240a219cfe0260463c82cc68aeaaae2f823
* 
https://github.com/Nheko-Reborn/mtxclient/commit/ce47f0b280c7e5241a556d63c518267d5e6b9c1c



2. Secret poisoning (CVE-2022-39264)

https://github.com/Nheko-Reborn/nheko/security/advisories/GHSA-8jcp-8jq4-5mm7

This was fixed in v0.10.2:

* 
https://github.com/Nheko-Reborn/nheko/commit/67bee15a389f9b8a9f6c3a340558d1e2319e7199




Thanks in advance,
Val Lorentz


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1022025: fixed in linux 5.10.149-2

2022-10-27 Thread inasprecali
On Thu, 27 Oct 2022 21:01:15 +0200 Salvatore Bonaccorso
 wrote:
> Can you please fill a new bug for your issue, which would still
> be
> present in the 5.10.149-2 release? There are two users which
> report
> that they still have problems with the amdgpu driver still in
> 5.10.149-2.

I think bug 1022806 is a recent one referring to 5.10.149-2
specifically, which is about this same issue.  I don't think there
is a need to report yet another bug about it.

Best regards.

--
inasprecali



Bug#1022025: fixed in linux 5.10.149-2

2022-10-27 Thread Salvatore Bonaccorso
Hi

On Thu, Oct 27, 2022 at 05:21:32PM +, inasprecali wrote:
> On Thu, 27 Oct 2022 06:17:10 + Debian FTP Masters
>  wrote:
> > Source: linux
> > Source-Version: 5.10.149-2
> > Done: Salvatore Bonaccorso 
> > 
> > We believe that the bug you reported is fixed in the latest
> version of
> > linux, which is due to be installed in the Debian FTP archive.
> 
> I'm sorry, but your belief seems to be mistaken, since we have
> multiple reports o 5.10.149-2 still not booting with the amdgpu
> driver.

Can you please fill a new bug for your issue, which would still be
present in the 5.10.149-2 release? There are two users which report
that they still have problems with the amdgpu driver still in
5.10.149-2.

Thanks already, let's folloup there with some questions.

Regards,
Salvatore



Bug#1022848: linux: 6.0.5 fixes critical btrfs bug

2022-10-27 Thread Salvatore Bonaccorso
Control: severity -1 important

Hi,

On Wed, Oct 26, 2022 at 10:23:35PM +0200, Christoph Anton Mitterer wrote:
> Source: linux
> Version: 5.19.6-1
> Severity: critical
> Justification: breaks the whole system
> 
> 
> Hi.
> 
> 6.0.3 introduced a commit that causes (permanent) CPU soft lockups
> for some people with btrfs filesystems, effectively breaking the
> system, e.g. when booting.

According to your references there is the workaround of mounting  with
clear_cache,space_cache=v2 and convert the filesystem.

What would one prevent doing so?

I'm downgrading the severity to important as it does not make the
kernel unbootable or unstable on common hardware or all systems that a
flavour is supposed to support. 

While I agree it is important to fix, this issue should not block the
migration of the current kernel to address CVE-2022-2602.

I will work next on importing the newer 6.0.y versions which include a
fix for this issue as well.

Regards,
Salvatore



Bug#1022779: dosbox: could dosbox-x be a future to dosbox?

2022-10-27 Thread Stephen Kitt
I’ve heard of DOSBox Staging, but AFAICT all its features are in DOSBox-X.
Someone else is working on packaging that, see
https://bugs.debian.org/973822

Regards,

Stephen


On Wed, 26 Oct 2022 19:53:22 +0200, Patrice  wrote:

> So nice!
> 
> Do you know this one https://github.com/dosbox-staging/dosbox-staging ?
> I found some packagings on Salsa like:
> https://salsa.debian.org/okias/dosbox-staging
> but it remained at the version 0.76.0 and now the upstream is 0.79.1.
> I haven't tried it yet.
> 
> Best,
> Patrice
> 
> On Wed, 26 Oct 2022 11:59:29 +0200 Stephen Kitt  wrote:
> > Hi Patrice,
> > 
> > Le 25/10/2022 19:55, Patrice Duroux a écrit :  
> > > The dosbox-x project (https://dosbox-x.com/) is currently version 
> > > 0.84.3
> > > (2022.09.0)
> > > and seems to be SDL 2 compatible.
> > > Have you tried it?  
> > 
> > I have, and I’m actually working on packaging it. I’ve just filed an ITP 
> > to trace that fact, https://bugs.debian.org/1022800
> > 
> > Regards,
> > 
> > Stephen
> > 
> >   


pgpl6nL3AvU2B.pgp
Description: OpenPGP digital signature


Bug#1022903: made a merge request/patch

2022-10-27 Thread Antoine Beaupré
Control: tags -1 +patch

https://salsa.debian.org/debian-hamradio-team/soundmodem/-/merge_requests/4

Patch attached as well.

>From 3129562671c2c2241db052460b8d7fdd9bb0b4ce Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= 
Date: Thu, 27 Oct 2022 14:37:21 -0400
Subject: [PATCH] start service only when a config file is present (Closes:
 #1022903)

---
 debian/soundmodem.service | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/soundmodem.service b/debian/soundmodem.service
index 4313e52..f5536d3 100644
--- a/debian/soundmodem.service
+++ b/debian/soundmodem.service
@@ -1,6 +1,7 @@
 [Unit]
 Description=Soundmodem systemD service file to fix device permissions
 After=sound.target network.target multi-user.target
+ConditionPathExists=/etc/ax25/soundmodem.conf
 
 [Service]
 Type=forking
-- 
2.30.2



Bug#1022003: transition: gssdp/gupnp 1.2->1.6 (+ rygel 0.42.0)

2022-10-27 Thread Andreas Henriksson
Hello Sebastian Ramacher,

On Thu, Oct 27, 2022 at 07:38:14PM +0200, Sebastian Ramacher wrote:
> Control: tags -1 = confirmed
> 
> On 2022-10-18 21:24:03 +0200, Andreas Henriksson wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > 
> > Hello release team,
> > 
> > I'd like to transition gssdp/gupnp to 1.6 version as part of current
> > GNOME release.
> 
> Please go ahead

I'll hold off a few more days if that's not a problem.

Both because I'll be a bit busy the next couple of days but also
because there was a (newly added) test that failed on s390x
in gupnp/experimental.

With help from upstream the actual bug in gssdp/experimental should
be fixed, new gssdp/experimental has built (except on ppc64el) and I've
done a giveback of gupnp/experimental on s390x but it has still not
built yet confirming if the problem is actually fixed and the test
passes.
Is there any chance you have a way to give some priority to
gupnp/experimental on s390x?
https://buildd.debian.org/status/package.php?p=gupnp=experimental

I'll probably also look into doing some NMUs to experimental of rdeps
before kicking off the actual transition.

If this means you want to put me back on hold and give the slot to
someone else, that's fine with me! I just want to make sure we get this
transition done before freeze so gnome versions are all synced up.

Regards,
Andreas Henriksson


PS. Thanks for being very responsive through this process. A few years ago
waiting several months without hearing anything was common and kind of
what I still was expecting. This feels alot more like coordinating
in the real sense of the word.



Bug#1019425: dkms 3.0.6-2 not signing modules

2022-10-27 Thread Maurizio Avogadro

Il 27/10/22 17:38, Siddh Raman Pant ha scritto:


We can use the sign_helper.sh which was used in sign_tool config prior to v3 in
the sign_file config option in /etc/dkms/framework.conf.

Courtesy: https://github.com/dell/dkms/issues/273.

I use it with keyring in the following way:
https://gist.github.com/siddhpant/19c07b07d912811f5a4b2893ca706c99

Thanks,
Siddh



Hi Siddh

since dkms is supposed to run as root, it's not clear to me which keyring is 
the signing key passphrase going to be stored to. I definitely wouldn't 
recommend running Gnome/KDE keyrings as root, and user keyrings seem to be 
unreachable via D-bus in a console where root has been gained with su -.


BTW, by adding a configuration snippet in /etc/dkms/framework.conf.d/ containing

export KBUILD_SIGN_PIN='my_mok_key_pin'

(permissions 600 recommended) seems to work (given the kernel you are running 
is configured to use the SHA512 hash algorithm; official Debian kernels use 
SHA256 [1]).


We also have to face the problem that only official Debian kernels store the 
sign-file executable in


/usr/lib/linux-kbuild-${kernelver%.*}/scripts/

where dkms looks in Debian: Xanmod and Liquorix for example store this file in

/usr/src/linux-headers-${kernelver}/scripts/

but this path can't be easily changed in current dkms version (v3.0.6-4) 
because the $kernelver variable isn't available when sourcing the configuration 
files; dkms in current master tree fixed this issue by adding a fallback to


/lib/modules/${kernelver}/build/scripts/

in distro detection code, which makes signing work with any kernel I could test 
till now.



[1] https://github.com/dell/dkms/issues/266



Bug#1022789: texinfo: UTF-8 is not the default input encoding

2022-10-27 Thread Vincent Lefevre
Control: tags -1 fixed-upstream

On 2022-10-27 08:32:12 +0200, Hilmar Preuße wrote:
> Am 26.10.2022 um 13:35 teilte Vincent Lefevre mit:
> 
> Hi,
> 
> > According to
> > 
> >https://lists.gnu.org/archive/html/bug-texinfo/2022-10/msg00336.html
> > 
> > this is probably an upstream bug, apparently fixed (to be confirmed).
> > 
> Are you willing to test using latest upstream snapshot yourself?

I've just done that and can confirm that this is fixed.

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



Bug#1002600: Firefox ESR crashes on pre-SSE2 CPUs

2022-10-27 Thread karogyoker999
It seems that firefox-esr_102.4.0esr-1 works again. I don't know why though.



Bug#1022003: transition: gssdp/gupnp 1.2->1.6 (+ rygel 0.42.0)

2022-10-27 Thread Sebastian Ramacher
Control: tags -1 = confirmed

On 2022-10-18 21:24:03 +0200, Andreas Henriksson wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hello release team,
> 
> I'd like to transition gssdp/gupnp to 1.6 version as part of current
> GNOME release.

Please go ahead

Cheers

> 
> I've just uploaded the new versions of gssdp and gupnp 1.6.0 to
> binary-NEW/experimental.
> 
> I will team-upload new releases of the following reverse dependencies as
> part of gnome-team:
> 
> * rygel (0.42.0-1 just uploaded to binary-NEW/experimental) 
>   - FYI internal soname bump for broken plugin ABI, but there are no
> external plugins (all built from src:rygel).
> * gupnp-tools (0.12.0-1 just uploaded to experimental)
> * gupnp-igd (needs cherry-pick 
> https://gitlab.gnome.org/GNOME/gupnp-igd/-/commit/79a1e4cf8c256132978a1d8ab718c8ad132386de
>  )
> 
> I've just done QA uploads to unstable for latest version of
> dleyna-{core,renderer,server} to make it easier to cherry-pick upstream
> changes for gssdp/gupnp 1.6 (not yet in a released version).
> I can do qa uploads of dleyna-* but would prefer if these packages where
> simply removed from testing as they've been orphaned for many years
> (since their initial upload to debian).
> Will file a bug for each package and point out the upstream commits
> respectively:
> * 
> https://github.com/phako/dleyna-core/commit/b88f231affc697be813d7c77c17e3130df81cb9a
> * 
> https://github.com/phako/dleyna-renderer/commit/b3a06c8bc4b91803d7bde312f49a68109b8ad8d4
> * 
> https://github.com/phako/dleyna-server/commit/e7f64192643f5783e19482a11697de9ec3eea033
> 
> I will file bugs for remaining (and offer to NMU if no response),
> fixed-upstream (not yet in a released version):
> 
> * caja-extensions -- 
> https://github.com/mate-desktop/caja-extensions/issues/110
> * librm -- 
> https://gitlab.com/tabos/librm/-/commit/c9aae663ff40c1ab171476652eba68c174d96ba2
>  + 
> https://gitlab.com/tabos/librm/-/commit/a849d9a6a6624d5f3c6a70dd63590d1a2b79d1af
> 
> 
> Regards,
> Andreas Henriksson
> 
> 
> PS. Once I've filed all bug reports I'll set them as blockers for this bug
> report.
> 
> 
> Ben file:
> 
> title = "gupnp";
> is_affected = .depends ~ "libgupnp-1.2-1" | .depends ~ "libgssdp-1.2-0" | 
> .depends ~ "libgupnp-1.6-0" | .depends ~ "libgssdp-1.6-0";
> is_good = .depends ~ "libgupnp-1.6-0" | .depends ~ "libgssdp-1.6-0";
> is_bad = .depends ~ "libgupnp-1.2-1" | .depends ~ "libgssdp-1.2-0";
> 

-- 
Sebastian Ramacher



Bug#1021187: gnome-keyring: /usr/bin/gnome-keyring-daemon --daemonize --login 100% CPU usage

2022-10-27 Thread Elmar Ludwig
Just for the record:

This issue has been reported upstream today in the GNOME gitlab:

https://gitlab.gnome.org/GNOME/glib/-/issues/2795

confirming that a change in glib-2.74.1 caused the breakage.
So, I guess this bug should be reassigned to glib2.0?



Bug#1022851: xorriso: -clone across sessions copies, not clones

2022-10-27 Thread Thomas Schmitt
Hi,

i have pushed the libisofs bug fix upstream

  
https://dev.lovelyhq.com/libburnia/libisofs/commit/acb4bd143c6374319e4f0fd91c23cd5bd93a3616

(Small but decisive.)

If you or any bystanders prefer a GNU xorriso development tarball, i can
upload one. For now i guess that you are prepared to build a new libisofs
from git.


Have a nice day :)

Thomas



Bug#1022025: fixed in linux 5.10.149-2

2022-10-27 Thread inasprecali
On Thu, 27 Oct 2022 06:17:10 + Debian FTP Masters
 wrote:
> Source: linux
> Source-Version: 5.10.149-2
> Done: Salvatore Bonaccorso 
> 
> We believe that the bug you reported is fixed in the latest
version of
> linux, which is due to be installed in the Debian FTP archive.

I'm sorry, but your belief seems to be mistaken, since we have
multiple reports o 5.10.149-2 still not booting with the amdgpu
driver.

Best regards.

--
inasprecali



Bug#1022924: flim: Package requires oauth2.el

2022-10-27 Thread Leo Butler
Package: flim

Dear Maintainer,

This package includes sasl-xoauth2.el. That file's second line is

(require 'oauth2)

But this emacs package is not listed as a dependency nor is it even
available in the debian repos. Hence, loading that file fails.

Please package oauth2.el with flim or as a separate stand-alone
package.


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

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

Versions of packages flim depends on:
ii  apel   10.8+0.20201106-1
ii  dpkg   1.21.9+b1
ii  emacs  1:27.1+1-3.1
ii  emacs-gtk [emacs]  1:27.1+1-3.1+b1
ii  emacsen-common 3.0.4
ii  install-info   6.8-6

flim recommends no packages.

Versions of packages flim suggests:
pn  semi  
pn  wl | wl-beta  
pn  xemacs21-bin  

-- no debconf information
--



Bug#1022923: RFP: python3-surt -- transform Universal Resource Identifiers into an easily-sorted format

2022-10-27 Thread James Addison
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: j...@jp-hosting.net

* Package name: python3-surt
  Version : 0.3.1
  Upstream Author : Raj 
* URL : https://github.com/internetarchive/surt.git/
* License : AGPLv3
  Programming Lang: Python
  Description : transform Universal Resource Identifiers into an 
easily-sorted format

This library provides a Python implementation of the Internet Archive's SURT 
(Sort-friendly URI Reordering Transform) algorithm.

This is useful for situations where it's desirable to sort a set of URIs in a 
way that maintains contiguity based on DNS topological hierarchy followed by 
path hierarchy.



Bug#1008602: Thic client (X2Go) workaround

2022-10-27 Thread Mike Gabriel

Hi,

On  Do 27 Okt 2022 18:04:41 CEST, Dashamir Hoxha wrote:


On Thu, Oct 27, 2022 at 5:54 PM Mike Gabriel <
mike.gabr...@das-netzwerkteam.de> wrote:



> Is there no way for the NX-based X2Go to handle compositing properly?
> I think this should be the real fix.

Nope. That is a won't fix. Compositing decreases performance by many
(milli)seconds (latency) per round trip. Compositing is for local
hardware, not for remote connections.



Maybe you are right. I am not an expert on these issues (I don't even know
what "compositing" is).
It just seems to me that RDP is doing fine with it (at least I don't notice
any issues), but maybe it is a wrong perception.


in another project I am currently working on an Enterprise Desktop  
based on MATE and we test stuff via xRDP and see so so so many  
graphical glitches (rectangles not filled with the window color, but  
desktop background shining through, etc.).


So, I am not so convinced about xRDP (at least on openSUSE 15.4 and in  
combination with MATE desktop's window manager).


Greets,
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



pgp1YB6vB1rBf.pgp
Description: Digitale PGP-Signatur


Bug#1022830: apt ignores versioned provides if non-matching version is installed via another dep

2022-10-27 Thread duck

Quack,

On 2022-10-27 08:51, David Kalnischkies wrote:


You are right that libruby3.0 which provides 3.1.9 is not enough to
satisfy the build-dependency of redmine, but libruby3.1 is installed,
too, and that certainly does satisfy ruby-csv (>= 3.2.0). It is
therefore correct for apt to not install the real ruby-csv package
as that dependency is already satisfied.


Indeed, thank you for finding this out.


You might or might not be able to workaround this with Build-Conflicts,
but in the end libruby3.1 and ruby-csv should really agree on what they
are providing at what version or not… hence reassigning to both.


This is due to ruby-all-dev (needed by gem2deb) dragging all supported 
versions. As long as we build multiple versions in the same source 
package I do not see how we fix this.
In the archall case then we may modify all the dep chain to only use the 
latest supported Ruby version but that won't solve the problem globally.


I added the Ruby list to the discussion.

Regards.
\_o<

--
Marc Dequènes



Bug#1022922: graphite-carbon: debian/watch regex is outdated

2022-10-27 Thread James Addison
Package: graphite-carbon
Severity: minor
Tags: patch
X-Debbugs-Cc: j...@jp-hosting.net

Dear Maintainer,

It looks like the 'debian/watch' file for graphite-carbon may be outdated.

PyPi has updated their simple package index pages to update the hash format 
associated with each published package from md5sum to sha256sum.

Please find attached a patch that updates the 'debian/watch' regex 
correspondingly.

Thank you,
James
diff --git a/debian/watch b/debian/watch
index 8379d9c..e5ba3e0 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,3 +1,3 @@
 version=3
-opts="filenamemangle=s/\S+\/([^\/]+\.tar\.gz)#md5=[[:alnum:]]+$/$1/" \
-https://pypi.python.org/simple/carbon .*carbon-(.*)\.tar\.gz#md5=[[:alnum:]]+
+opts="filenamemangle=s/\S+\/([^\/]+\.tar\.gz)#sha256=[[:alnum:]]+$/$1/" \
+https://pypi.python.org/simple/carbon 
.*carbon-(.*)\.tar\.gz#sha256=[[:alnum:]]+


Bug#1008602: Thic client (X2Go) workaround

2022-10-27 Thread Dashamir Hoxha
On Thu, Oct 27, 2022 at 5:54 PM Mike Gabriel <
mike.gabr...@das-netzwerkteam.de> wrote:

>
> > Is there no way for the NX-based X2Go to handle compositing properly?
> > I think this should be the real fix.
>
> Nope. That is a won't fix. Compositing decreases performance by many
> (milli)seconds (latency) per round trip. Compositing is for local
> hardware, not for remote connections.
>

Maybe you are right. I am not an expert on these issues (I don't even know
what "compositing" is).
It just seems to me that RDP is doing fine with it (at least I don't notice
any issues), but maybe it is a wrong perception.


Bug#1022921: wine: broken packages after running dist-upgrade

2022-10-27 Thread Tobias Koeck
Package: wine
Version: 5.0.3-3
Severity: important

Dear Maintainer,

unfortunately the system installed or wanted to install the newer
version after running.

apt-get dist-upgrade -t bullseye-backports

Now the old one doesn't work, too.


root@tron-nb:~# apt-get install wine -t bullseye-backports wine wine64 libwine 
wine32 libz-mingw-w64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libz-mingw-w64 is already the newest version (1.2.11+dfsg-2).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libwine : Depends: libz-mingw-w64 (>= 1.2.11+dfsg-4) but 1.2.11+dfsg-2 is to 
be installed
 libwine:i386 : Depends: libz-mingw-w64:i386 (>= 1.2.11+dfsg-4)
Recommends: libcups2:i386 (>= 1.4.0) but it is not going to be 
installed
Recommends: libodbc1:i386 (>= 2.3.1) but it is not going to be 
installed
Recommends: libosmesa6:i386 (>= 10.2~) but it is not going to 
be installed
Recommends: libsdl2-2.0-0:i386 (>= 2.0.12) but it is not going 
to be installed
Recommends: libv4l-0:i386 (>= 0.5.0) but it is not going to be 
installed
Recommends: libxcomposite1:i386 (>= 1:0.4.5) but it is not 
going to be installed
Recommends: libxcursor1:i386 (> 1.1.2) but it is not going to 
be installed
Recommends: libxi6:i386 but it is not going to be installed
Recommends: libxrandr2:i386 but it is not going to be installed
Recommends: gstreamer1.0-plugins-good:i386 but it is not going 
to be installed
E: Unable to correct problems, you have held broken packages.
root@tron-nb:~#

Greetings
Tobias

-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-stable.

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

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

Versions of packages wine depends on:
ii  wine64  5.0.3-3

wine recommends no packages.

Versions of packages wine suggests:
pn  dosbox   
ii  kio-extras   4:20.12.2-1
pn  playonlinux  
ii  q4wine   1.3.12-1
pn  winbind  
pn  wine-binfmt  
pn  winetricks   

Versions of packages wine is related to:
pn  dxvk 
pn  dxvk-wine32-development  
pn  dxvk-wine64-development  
ii  fonts-wine   7.0~repack-10~bpo11+1
ii  wine [wine]  5.0.3-3
pn  wine32   
ii  wine64   5.0.3-3

-- no debconf information


Bug#993089: marked as pending in freecad

2022-10-27 Thread Kurt Kremitzki
Sorry for the noise, looks like we have an automation double-fire from 
when I merged the master branch into a PPA one and pushed it.




Bug#1008602: Thic client (X2Go) workaround

2022-10-27 Thread Mike Gabriel

Hi,

On  Do 27 Okt 2022 17:42:25 CEST, Dashamir Hoxha wrote:


On Thu, Oct 27, 2022 at 2:41 PM Mike Gabriel <
mike.gabr...@das-netzwerkteam.de> wrote:



But the real fix would be: XFCE4 recognizes that it is running in an
NX-based X2Go session and disables compositing automatically.



Is there no way for the NX-based X2Go to handle compositing properly?
I think this should be the real fix.


Nope. That is a won't fix. Compositing decreases performance by many  
(milli)seconds (latency) per round trip. Compositing is for local  
hardware, not for remote connections.


Another "fix" would be using the next generation X2Go backend X2Go  
KDrive. But that's not in Debian, yet. But also with KDrive (where  
Compositing works), it would be advisable to disable it for  
performance sake.


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



pgp7HRgxMriGn.pgp
Description: Digitale PGP-Signatur


Bug#1008602: Thic client (X2Go) workaround

2022-10-27 Thread Dashamir Hoxha
On Thu, Oct 27, 2022 at 2:41 PM Mike Gabriel <
mike.gabr...@das-netzwerkteam.de> wrote:

>
> But the real fix would be: XFCE4 recognizes that it is running in an
> NX-based X2Go session and disables compositing automatically.
>

Is there no way for the NX-based X2Go to handle compositing properly?
I think this should be the real fix.


Bug#1022892: rsyslog uses "localhost" instead of the real hostname

2022-10-27 Thread Michael Biebl

forcemerge 1022128 1022892 1022891
thanks

Am 27.10.22 um 14:25 schrieb zieg...@uni-freiburg.de:

Package: rsyslog
Version: 8.2210.0-1
Severity: normal
X-Debbugs-Cc: zieg...@uni-freiburg.de

Dear Maintainer,

After updating to 8.2210.0-1 the log messages
contained "localdomain" instead of the real hostname.

The contents of /etc/hosts /etc/hostname were not changed.
The command "hostname" and the C-library function "gethostname"
still return the correct hostname.


Duplicates of 1022128, merging accordingly





OpenPGP_signature
Description: OpenPGP digital signature


Bug#1019425: dkms 3.0.6-2 not signing modules

2022-10-27 Thread Siddh Raman Pant
On Wed, 21 Sep 2022 10:49:46 +0200 Maurizio Avogadro  wrote:
> ... and support for MOK keys with a passphrase seem to have disappeared all 
> at 
> once...
> 
> Furthermore, I'm unable to find any documentation on changes regarding module 
> signing, and there are no useful comments on config files.

We can use the sign_helper.sh which was used in sign_tool config prior to v3 in
the sign_file config option in /etc/dkms/framework.conf.

Courtesy: https://github.com/dell/dkms/issues/273.

I use it with keyring in the following way:
https://gist.github.com/siddhpant/19c07b07d912811f5a4b2893ca706c99

Thanks,
Siddh



Bug#1022920: Removal notice: obsolete

2022-10-27 Thread Ilias Tsitsimpis
Source: haskell-thyme
Version: 0.3.5.5-5
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 7 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias



Bug#1022917: ITP: nemo-qml-plugin-dbus -- Nemo QML Plugin D-Bus

2022-10-27 Thread Sebastian Spaeth
Package: wnpp
Severity: wishlist
Owner: Sebastian Spaeth 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: nemo-qml-plugin-dbus
  Version : 2.1.30
  Upstream Author : 2013-2021 Jolla OY & many contributors
* URL : https://github.com/sailfishos/nemo-qml-plugin-dbus
* License : LGPL & BSD
  Programming Lang: C++
  Description : Nemo QML Plugin D-Bus

 The nemo-dbus library provides C++11 extensions to QtDBus to make it easier
 to call and handle the replies from asynchronous DBus methods.

The package is a required dependency of puremaps, which is one of the few
navigation applications that is both mobile-screen friendly and capable of
offline routing.

I would like to introduce puremaps in the long run into Debian. It would
probably be maintained by the DebianOnMobile team (of which I am a member), if
the KDE/QML side is not interested.
I am happy if sponsors would volunteer, but I am capable of finding one myself
if needed.



Bug#1022918: Removal notice: obsolete

2022-10-27 Thread Ilias Tsitsimpis
Source: haskell-text-format
Version: 0.3.2-4
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 3 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias



Bug#931440: wireguard module needs signing to work with secureboot

2022-10-27 Thread Siddh Raman Pant
On Fri, 7 Oct 2022 11:41:31 +0530, I wrote:
> For some reason it isn't signing while using apt, but is signing when I 
> manually
> remove and add the modules. I infer signing is being done when it is shown in
> the output, which was not the case when I installed nvidia-driver.

So it was due to MOK key locations in DKMS config not being set to distro 
defaults.
That's all what is needed if your keys aren't protected by a passphrase. 
Otherwise,
we can use the sign_helper.sh which was used to in sign_tool config prior to v3 
in
the sign_file config.

If anyone stumbles upon this thread, my config can be found on:
https://gist.github.com/siddhpant/19c07b07d912811f5a4b2893ca706c99

Thanks,
Siddh



Bug#1022915: ITP: golang-github-pin-tftp -- TFTP server and client library for Golang

2022-10-27 Thread Shengjing Zhu
On Thu, Oct 27, 2022 at 11:18 PM Thomas Goirand  wrote:
>
> Package: wnpp
> Severity: wishlist
> Owner: Thomas Goirand 
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: golang-github-pin-tftp
>   Version : 3.0.0
>   Upstream Author : Dmitri Popov 
> * URL : https://github.com/pin/tftp
> * License : Expat
>   Programming Lang: Golang
>   Description : TFTP server and client library for Golang
>
>  This package provides a TFTP server and client library for Golang. It
>  implements:
>   * RFC 1350 - The TFTP Protocol (Revision 2)
>   * RFC 2347 - TFTP Option Extension
>   * RFC 2348 - TFTP Blocksize Option
>  .
>  Partially implements (tsize server side only):
>   * RFC 2349 - TFTP Timeout Interval and Transfer Size Options
>  .
>  Its set of features is sufficient for PXE boot support.
>
> Note: this is another dependency for mgmt-config that I'm packaging.
>

It's already packaged.
https://tracker.debian.org/pkg/golang-github-pin-tftp

-- 
Shengjing Zhu



Bug#1022916: ITP: jstyleson -- python library to parse JSON with js-style comments

2022-10-27 Thread Christian Marillat
Package: wnpp
Severity: wishlist
Owner: Christian Marillat 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-jstyleson
  Version : 0.0.2
  Upstream Author : linjackson
* URL : https://pypi.org/project/jstyleson/
* License : MIT
  Programming Lang: Python
  Description : library to parse JSON with js-style comments

 JSON by standard does not allow comments and trailing comma, and the
 python standard json module does not offer options to parse such
 informal JSON.

 jstyleson try to make it happy with your js-style commented JSON, by
 first removing all elements inside (comments and trailing comma),
 then hand it to the standard json module. 

 jstyleson supports parsing JSON with:

single-line comment
multi-line comment
inline comment
trailing comma

 This package is a dependency for python-extruct



Bug#1022915: ITP: golang-github-pin-tftp -- TFTP server and client library for Golang

2022-10-27 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: golang-github-pin-tftp
  Version : 3.0.0
  Upstream Author : Dmitri Popov 
* URL : https://github.com/pin/tftp
* License : Expat
  Programming Lang: Golang
  Description : TFTP server and client library for Golang

 This package provides a TFTP server and client library for Golang. It
 implements:
  * RFC 1350 - The TFTP Protocol (Revision 2)
  * RFC 2347 - TFTP Option Extension
  * RFC 2348 - TFTP Blocksize Option
 .
 Partially implements (tsize server side only):
  * RFC 2349 - TFTP Timeout Interval and Transfer Size Options
 .
 Its set of features is sufficient for PXE boot support.

Note: this is another dependency for mgmt-config that I'm packaging.



Bug#1022914: Removal notice: obsolete

2022-10-27 Thread Ilias Tsitsimpis
Source: haskell-test-framework-th
Version: 0.2.4-12
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * Seems unmaintained; Last upload more than 10 years ago
  * It's not part of the latest Stackage LTS
  * Depends on deprecated software (see #1022040)

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias



Bug#1022913: Removal notice: obsolete

2022-10-27 Thread Ilias Tsitsimpis
Source: haskell-test-framework-th-prime
Version: 0.0.10-4
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias



Bug#1022912: mutt: cache unencrypted copies of encrypted e-mail bodies

2022-10-27 Thread eingousef
Package: mutt
Version: 2.2.7-1
Severity: normal
X-Debbugs-Cc: eingousef+debb...@rhizogen.es.eu.org

Dear Maintainer,

Currently using mutt on a mailbox which contains OpenPGP-encrypted e-mails is a 
bit of a hassle, especially when I want to search through them. I run a 
research on e-mail bodies from the index section, which takes some time, so I 
let it run in the background and come back a few minutes later, only to find 
out that it reached an encrypted e-mail at some point and prompted me for the 
GPG key passphrase, blocking the interface until I give it. Depending on the 
size of the mail archive it can be a significant waste of time.

When I have several encrypted e-mails, encrypted with different keys, and some 
using expired keys, that's even more annoying.

OpenPGP is meant to secure messages over the various network links and 
intermediate servers between the sender's MUA and the recipient's MUA. Securing 
e-mails on the recipient's local computer isn't OpenPGP's job : this is done 
via file permissions and/or folder / disk encryption.

See this demand concerning an other MUA : 
https://bugzilla.mozilla.org/show_bug.cgi?id=280588

I think mutt should provide the possibility to locally store unencrypted copies 
of e-mails which are encrypted on the distant IMAP server, without uploading 
those back to the IMAP server of course. This way the user could search through 
all messages and treat them like clear text, without having to deal with 
prompts that could induce delays and errors. The message_cachedir would 
probably be the proper place for that.

So two complementary proposals :

  1. allow to use message_cachedir under any condition ( not just when using an 
imap(s):// folder, but also when using a local ~/Mail folder );

  2. give an option to store message bodies in a clear-text form in the 
message_cachedir folder once they've been decrypted. I propose to have it as an 
option so the extra-paranoid could keep those mail bodies encrypted ;

Regards,

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

System: Linux 5.19.0-2-amd64 (x86_64)
ncurses: ncurses 6.3.20220423 (compiled with 6.3)
libidn2: 2.3.3 (compiled with 2.3.3)
hcache backend: tokyocabinet 1.4.48

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

Configure options: --build=x86_64-linux-gnu --prefix=/usr 
'--includedir=${prefix}/include' '--mandir=${prefix}/share/man' 
'--infodir=${prefix}/share/info' --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
'--libdir=${prefix}/lib/x86_64-linux-gnu' --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking 
--with-mailpath=/var/mail --enable-compressed --enable-debug --enable-fcntl 
--enable-hcache --enable-gpgme --enable-imap --enable-smtp --enable-pop 
--enable-sidebar --enable-dotlock --disable-fmemopen --with-curses 
--with-gnutls --with-gss --with-idn2 --with-mixmaster --with-gsasl 
--without-gdbm --without-bdb --without-qdbm --with-tokyocabinet 
build_alias=x86_64-linux-gnu 'CFLAGS=-g -O2 
-ffile-prefix-map=/build/mutt-lJbrpQ/mutt-2.2.7=. -fstack-protector-strong 
-Wformat -Werror=format-security' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now' 
'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'

Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2 

Bug#1022911: ITP: python-html-text -- extract text from HTML

2022-10-27 Thread Christian Marillat
Package: wnpp
Severity: wishlist
Owner: Christian Marillat 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-html-text
  Version : 0.5.2
  Upstream Author : Scrapinghub Inc
* URL : https://github.com/TeamHG-Memex/html-text
* License : MIT
  Programming Lang: Python
  Description : extract text from HTML

  How is html_text different from .xpath('//text()') from LXML or
  .get_text() from Beautiful Soup? 

  Text extracted with html_text does not contain inline styles,
  javascript, comments  and other text that is not normally visible to users;

  html_text normalizes whitespace, but in a way smarter than
  .xpath('normalize-space()), adding spaces around inline elements
  (which are often used as block elements in html markup), and trying
  to avoid adding extra spaces for punctuation;

  html-text can add newlines (e.g. after headers or paragraphs), so
  that the output text looks more like how it is rendered in
  browsers. 


 This package is a dependency for python-extruct



Bug#1022910: Removal notice: obsolete

2022-10-27 Thread Ilias Tsitsimpis
Source: haskell-regex-compat-tdfa
Version: 0.95.1.4-8
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 9 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias



Bug#1022900: grub-install, efibootmgr etc. not working with new kernel

2022-10-27 Thread Diederik de Haas
On Thursday, 27 October 2022 15:56:28 CEST Stephan Verbücheln wrote:
> Version: 6.0.3-1
> 
> When I boot with kernel 6.0.x, grub-install, efibootmgr etc. keep
> failing. With kernel 5.19.x it works on the same machine with the same
> userland.

Can you try whether applying the following patch fixes that issue?

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?
h=linux-6.0.y=c2a000ad03bb3a0d0f389adcfc9f8c61622da363

That is part of upstream's v6.0.4 tag/release.

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


Bug#1022909: Removal notice: obsolete

2022-10-27 Thread Ilias Tsitsimpis
Source: haskell-pipes-aeson
Version: 0.4.1.8-4
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 8 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias



Bug#1022857: [PATCH] printf: with \U syntax, support all valid unicode points

2022-10-27 Thread Pádraig Brady
Previously this was restricted to the C standard subset
which restricted most values <= 0x9F, as that simplifies the C lexer.
However printf(1) doesn't need this restriction.
Note also the bash builtin printf already supports all values <= 0x9F.

* src/printf.c (main): Relax the restriction on points <= 0x9F.
* doc/coreutils.texi (printf invocation): Adjust description.
* tests/misc/printf-cov.pl: Adjust accordingly.  Add new cases.
* NEWS: Mention the change in behavior.
Reported at https://bugs.debian.org/1022857
---
 NEWS |  4 
 doc/coreutils.texi   |  5 ++---
 src/printf.c | 11 +++
 tests/misc/printf-cov.pl | 11 ---
 4 files changed, 17 insertions(+), 14 deletions(-)

diff --git a/NEWS b/NEWS
index 31b04fe9f..b6b5201e7 100644
--- a/NEWS
+++ b/NEWS
@@ -41,6 +41,10 @@ GNU coreutils NEWS-*- 
outline -*-
   reverting to the behavior in coreutils-9.0 and earlier.
   This behavior is now documented.
 
+  printf unicode \u, \U syntax, now supports all valid
+  unicode code points.  Previously is was restricted to the C
+  universal character subset, which restricted most points <= 0x9F.
+
   runcon now exits with status 125 for internal errors.  Previously upon
   internal errors it would exit with status 1, which was less distinguishable
   from errors from the invoked command.
diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 8ce23898b..764a7c897 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -13216,9 +13216,8 @@ characters, specified as
 four hexadecimal digits @var{}, and @samp{\U} for 32-bit Unicode
 characters, specified as eight hexadecimal digits @var{}.
 @command{printf} outputs the Unicode characters
-according to the @env{LC_CTYPE} locale.  Unicode characters in the ranges
-U+@dots{}U+009F, U+D800@dots{}U+DFFF cannot be specified by this syntax,
-except for U+0024 ($), U+0040 (@@), and U+0060 (@`).
+according to the @env{LC_CTYPE} locale.  Unicode characters in the range
+U+D800@dots{}U+DFFF cannot be specified by this syntax.
 
 The processing of @samp{\u} and @samp{\U} requires a full-featured
 @code{iconv} facility.  It is activated on systems with glibc 2.2 (or newer),
diff --git a/src/printf.c b/src/printf.c
index 68c388341..5d420cef2 100644
--- a/src/printf.c
+++ b/src/printf.c
@@ -298,14 +298,9 @@ print_esc (char const *escstart, bool octal_0)
   uni_value = uni_value * 16 + hextobin (*p);
 }
 
-  /* A universal character name shall not specify a character short
- identifier in the range  through 0020, 007F through
- 009F, or D800 through DFFF inclusive. A universal
- character name shall not designate a character in the required
- character set.  */
-  if ((uni_value <= 0x9f
-   && uni_value != 0x24 && uni_value != 0x40 && uni_value != 0x60)
-  || (uni_value >= 0xd800 && uni_value <= 0xdfff))
+  /* Error for invalid code points D800 through DFFF inclusive.
+ Note print_unicode_char() would print the literal \u.. in this case. 
*/
+  if (uni_value >= 0xd800 && uni_value <= 0xdfff)
 die (EXIT_FAILURE, 0, _("invalid universal character name \\%c%0*x"),
  esc_char, (esc_char == 'u' ? 4 : 8), uni_value);
 
diff --git a/tests/misc/printf-cov.pl b/tests/misc/printf-cov.pl
index ab6bd159b..59c85cb66 100755
--- a/tests/misc/printf-cov.pl
+++ b/tests/misc/printf-cov.pl
@@ -66,9 +66,14 @@ my @Tests =
   ['esc', q('\xaa\0377'),  {OUT=>"\xaa\0377"}],
   ['esc-bad-hex', q('\x'), {EXIT=>1},
 {ERR=>"$prog: missing hexadecimal number in escape\n"}],
-  # ['u4', q('\u09ac'), {OUT=>"\xe0a6ac"}],
-  ['u-invalid', q('\u'), {EXIT=>1},
-{ERR=>"$prog: invalid universal character name \\u\n"}],
+  ['u-bad-hex', q('\u00'), {EXIT=>1},
+{ERR=>"$prog: missing hexadecimal number in escape\n"}],
+  ['U-bad-hex', q('\U'), {EXIT=>1},
+{ERR=>"$prog: missing hexadecimal number in escape\n"}],
+  ['u4', q('\u0030'), {OUT=>"0"}],
+  ['U8', q('\U0030'), {OUT=>"0"}],
+  ['u-invalid', q('\ud800'), {EXIT=>1},
+{ERR=>"$prog: invalid universal character name \\ud800\n"}],
   ['u-missing', q('\u'), {EXIT=>1},
 {ERR=>"$prog: missing hexadecimal number in escape\n"}],
   ['d-invalid', '%d no-num', {OUT=>'0'}, {EXIT=>1},
-- 
2.26.2



Bug#1022908: Removal notice: obsolete

2022-10-27 Thread Ilias Tsitsimpis
Source: haskell-pipes-aeson
Version: 0.4.1.8-4
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias



Bug#1022907: ITP: python-mf2py -- Microformats2 parser

2022-10-27 Thread Christian Marillat
Package: wnpp
Severity: wishlist
Owner: Christian Marillat 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-mf2py
  Version : 1.1.2
  Upstream Author : Tom Morris
* URL : https://github.com/microformats/mf2py
* License : MIT
  Programming Lang: Python
  Description : Parser for Microformats2

 Full-featured and mostly stable. Implements the full mf2 spec, including
 backward compatibility with microformats1.

 This package is a dependency for python-extruct



Bug#1022906: Removal notice: obsolete

2022-10-27 Thread Ilias Tsitsimpis
Source: haskell-monad-unlift
Version: 0.2.0-6
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * It's not part of the latest Stackage LTS
  * Deprecated in favor of unliftio-core, unliftio, rio

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias



Bug#1022905: Removal notice: obsolete

2022-10-27 Thread Ilias Tsitsimpis
Source: haskell-maths
Version: 0.4.9-2
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 4 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias



Bug#1022282: staden-io-lib: FTBFS: ./data/9827_rand3.cram.fai: No such file or directory

2022-10-27 Thread Bernhard Übelacker

Dear Maintainer,
the original staden-io-lib seems to be built with
libhtscodecs2 in version 1.2.2-1 [1].

The rebuild seems to be using libhtscodecs2 in version 1.3.0-4.

Unfortunately htscodecs upstream integrated this commit [3],
which renamed e.g. function encode_names to tok3_encode_names.
It added a compatibility function encode_names, but does not
declare it in the header file.
Therefore in the build of staden-io-lib the function encode_names
is implicitly declared - therefore seems to default to
a return type of int [4] - and therefore the returned pointer
gets truncated to the lower 4 bytes [5].
This get through unnoticed until the pointer is freed and
produces a segfault there [6].

I guess the right thing would be to have the short function name
in the header file of htscodecs, therefore solve this issue for
other packages using htscodecs.

A short term solution might be the patch in [7] which makes
the build and tests succeed without "implicit declarations".

Kind regards,
Bernhard



[1] 
https://buildd.debian.org/status/fetch.php?pkg=staden-io-lib=amd64=1.14.14%2Bdfsg-1%2Bb1=1663567926=0
[2] https://tracker.debian.org/pkg/htscodecs
[3] 
https://github.com/jkbonfield/htscodecs/commit/6211b208d2bd21e93f3f62c0cd0d8c43546f98b5

[4]
cram_io.c: In function ‘cram_compress_by_method’:
cram_io.c:2420:23: warning: implicit declaration of function 
‘encode_names’; did you mean ‘tok3_encode_names’? 
[-Wimplicit-function-declaration]
2420 | uint8_t *cp = encode_names(in, in_size, lev, strat, 
_len, NULL);
|   ^~~~
|   tok3_encode_names
cram_io.c:2420:23: warning: initialization of ‘uint8_t *’ {aka ‘unsigned 
char *’} from ‘int’ makes pointer from integer without a cast [-Wint-conversion]


[5]
(rr) bt
#0  tok3_encode_names (blk=, len=, level=, 
use_arith=, out_len=, last_start_p=) at 
./htscodecs/tokenise_name3.c:1540
#1  0x7f281aa34454 in cram_compress_by_method (s=s@entry=0x55e9af757e50, in=0x7f281000e930 
"s0", in_size=9, out_size=out_size@entry=0x7f2819611730, method=method@entry=TOK3, 
level=, strat=0, content_id=) at ./io_lib/cram_io.c:2420
#2  0x7f281aa38ebe in cram_compress_block (fd=fd@entry=0x55e9af71f930, 
s=s@entry=0x55e9af757e50, b=0x55e9af758830, metrics=0x55e9af731f50, 
method=65794, level=level@entry=5) at ./io_lib/cram_io.c:2562
#3  0x7f281aa22d75 in cram_compress_slice (s=0x55e9af757e50, c=, fd=0x55e9af71f930) at ./io_lib/cram_encode.c:951
#4  cram_encode_slice (fd=fd@entry=0x55e9af71f930, 
c=c@entry=0x55e9af73c270, h=h@entry=0x55e9af73c520, s=0x55e9af757e50) at 
./io_lib/cram_encode.c:1219
#5  0x7f281aa27881 in cram_encode_container (fd=, 
c=) at ./io_lib/cram_encode.c:2119
#6  0x7f281aa33fb0 in cram_flush_thread (arg=0x55e9af4d0500) at 
./io_lib/cram_io.c:4328
#7  0x7f281aa44272 in t_pool_worker (arg=0x55e9af737460) at 
./io_lib/thread_pool.c:434
#8  0x7f281a68784a in start_thread (arg=) at 
./nptl/pthread_create.c:442
#9  0x7f281a70a530 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:100
(rr) print out
$6 = (uint8_t *) 0x7f2810010320 "\t"
(rr) finish
Run till exit from #0  tok3_encode_names (blk=, len=, 
level=, use_arith=, out_len=, 
last_start_p=) at ./htscodecs/tokenise_name3.c:1540
0x7f281aa34454 in cram_compress_by_method (s=s@entry=0x55e9af757e50, in=0x7f281000e930 
"s0", in_size=9, out_size=out_size@entry=0x7f2819611730, method=method@entry=TOK3, 
level=, strat=0, content_id=) at ./io_lib/cram_io.c:2420
2420uint8_t *cp = encode_names(in, in_size, lev, strat, 
_len, NULL);
Value returned is $8 = (uint8_t *) 0x7f2810010320 "\t"
(rr) stepi
2421*out_size = out_len;
(rr) print cp
$7 = (uint8_t *) 0x10010320 
(rr) list
2416int out_len;
2417int lev = level;
2418if (method == NAME_TOK3 && lev > 3)
2419lev = 3;
2420uint8_t *cp = encode_names(in, in_size, lev, strat, 
_len, NULL);
2421*out_size = out_len;
2422return (char *)cp;
2423}
2424
2425case RAW:


[6]
Thread 2 received signal SIGSEGV, Segmentation fault.
0x7f281a69788a in __GI___libc_free (mem=0x10010320) at 
./malloc/malloc.c:3363
3363./malloc/malloc.c: Datei oder Verzeichnis nicht gefunden.
(rr) bt
#0  0x7f281a69788a in __GI___libc_free (mem=0x10010320) at 
./malloc/malloc.c:3363
#1  0x7f281aa39238 in cram_compress_block (fd=fd@entry=0x55e9af71f930, 
s=s@entry=0x55e9af757e50, b=0x55e9af758830, metrics=0x55e9af731f50, 
method=65794, level=level@entry=5) at ./io_lib/cram_io.c:2575
#2  0x7f281aa22d75 in cram_compress_slice (s=0x55e9af757e50, c=, fd=0x55e9af71f930) at ./io_lib/cram_encode.c:951
#3  cram_encode_slice (fd=fd@entry=0x55e9af71f930, 
c=c@entry=0x55e9af73c270, 

Bug#1022904: ITP: phog -- greetd-compatible greeter for mobile phones

2022-10-27 Thread Arnaud Ferraris
Package: wnpp
Severity: wishlist
Owner: Arnaud Ferraris 
X-Debbugs-Cc: debian-de...@lists.debian.org, aferra...@debian.org

* Package name: phog
  Version : 0.1.0
  Upstream Author : Arnaud Ferraris 
* URL : https://gitlab.com/mobian1/phog/
* License : GPL
  Programming Lang: C
  Description : greetd-compatible greeter for mobile phones

Phog is a graphical greeter speaking the `greetd` protocol and aimed at mobile
devices like smart phones and tablets using touch based inputs and small
screens.

It was initially designed for the Phosh Mobile Environment (based on GNOME/GTK)
but can spawn any graphical session.

This package will be maintained within the DebianOnMobile team.



Bug#1022903: systemd unit fails by default

2022-10-27 Thread Antoine Beaupre
Package: soundmodem
Version: 0.20-6+b1
Severity: normal

On a newly installed system, the systemd unit fails with this:

oct 06 12:15:58 angela systemd[1]: Starting Soundmodem systemD service file to 
fix device permissions...
oct 06 12:15:58 angela soundmodem[2069]: Configuartion not found
oct 06 12:15:58 angela soundmodem[2063]: SoundModem init failed
oct 06 12:15:58 angela systemd[1]: soundmodem.service: Control process exited, 
code=exited, status=1/FAILURE
oct 06 12:15:58 angela systemd[1]: soundmodem.service: Failed with result 
'exit-code'.
oct 06 12:15:58 angela systemd[1]: Failed to start Soundmodem systemD service 
file to fix device permissions.

... this marks the whole system as "degraded" which is really kind of
inaccurate, because the system is actually perfectly functional;
soundmodem is just not configured yet.

I can think of two ways of fixing this:

 1. add a condition in the systemd unit so that it doesn't try to
 start the service when it's unconfigured

 2. add a sample config file so that the service *does* start by
 default

I would favor the former. I think it needs a ConditionPathExists=
entry in the [Unit] section of the service file. I'm not sure which
actual config file we're talking about anymore though, but I figured I
would just mention it. :)


-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages soundmodem depends on:
ii  libasound2   1.2.7.2-1
ii  libatk1.0-0  2.46.0-3
ii  libaudiofile10.3.6-5+b1
ii  libc62.35-3
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libglib2.0-0 2.74.0-3
ii  libgtk2.0-0  2.24.33-2
ii  libhamlib4   4.3.1-1+b3
ii  libpango-1.0-0   1.50.10+ds-1
ii  libxml2  2.9.14+dfsg-1+b1

soundmodem recommends no packages.

soundmodem suggests no packages.

-- no debconf information



Bug#1022902: ITP: golang-github-libvirt-libvirt-go-xml -- API for manipulating libvirt XML documents

2022-10-27 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: golang-github-libvirt-libvirt-go-xml
  Version : 7.4.0
  Upstream Author : Lian Duan 
* URL : https://github.com/libvirt/libvirt-go-xml
* License : Expat
  Programming Lang: Golang
  Description : API for manipulating libvirt XML documents

 This package provides a Go API that defines a set of structs, annotated for
 use with "encoding/xml", that can represent libvirt XML documents. There is no
 dependency on the libvirt library itself, so this can be used regardless of
 the way in which the application talks to libvirt.

Note: This is a dependency of mgmt-config that I'm packaging.



Bug#992304: Dell PowerEdge T140

2022-10-27 Thread Gabriel Rolland [Res Novae]
Same problem with the Dell PowerEdge T140 with LSI MegaRAID SAS-3 3008 
[Fury] (rev 02) and linux-image-5.10.0-19-amd64 (NO UEFI)


No problem booting with the old 4.19.0-22-amd64 kernel



Bug#1022900: grub-install, efibootmgr etc. not working with new kernel

2022-10-27 Thread Stephan Verbücheln
Package: src:linux
Version: 6.0.3-1

When I boot with kernel 6.0.x, grub-install, efibootmgr etc. keep
failing. With kernel 5.19.x it works on the same machine with the same
userland.

Hardware: MacBookPro11,1, Intel(R) Core(TM) i7-4578U CPU @ 3.00GHz



I am not sure if this app is Apple specific. I recommend developers to
test grub-install and efibootmgr on other hardware setups.



grub-install: info: copying `/usr/lib/shim/shimx64.efi.signed' ->
`/boot/efi/EFI/debian/shimx64.efi'.
grub-install: info: copying `/usr/lib/grub/x86_64-efi-
signed/grubx64.efi.signed' -> `/boot/efi/EFI/debian/grubx64.efi'.
grub-install: info: copying `/usr/lib/shim/mmx64.efi.signed' ->
`/boot/efi/EFI/debian/mmx64.efi'.
grub-install: info: copying `/usr/lib/shim/fbx64.efi.signed' ->
`/boot/efi/EFI/debian/fbx64.efi'.
grub-install: info: copying `/usr/lib/shim/BOOTX64.CSV' ->
`/boot/efi/EFI/debian/BOOTX64.CSV'.
grub-install: info: copying `/boot/grub/x86_64-efi/load.cfg' ->
`/boot/efi/EFI/debian/grub.cfg'.
grub-install: info: Registering with EFI: distributor = `debian', path
= `\EFI\debian\shimx64.efi', ESP at hostdisk//dev/sda,gpt1.
grub-install: info: executing modprobe efivars 2>/dev/null.
grub-install: info: setting EFI variable Boot.
grub-install: warning: Cannot set EFI variable Boot.
grub-install: warning: efivarfs_set_variable: writing to fd 6 failed:
Invalid argument.
grub-install: warning: _efi_set_variable_mode: ops->set_variable()
failed: Invalid argument.
grub-install: error: failed to register the EFI boot entry: Invalid
argument.




Regards



Bug#1022901: Removal notice: obsolete

2022-10-27 Thread Ilias Tsitsimpis
Source: haskell-ghc-mtl
Version: 1.2.1.0-10
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 7 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias



Bug#1022899: [INTL:es] Spanish translation of the debconf template

2022-10-27 Thread Camaleón
Package: tryton-server
Severity: wishlist
Tags: patch l10n

Hello,
You can find enclosed the Spanish translation template to be uploaded with the 
latest package build.
Cheers,

-- 
Camaleón# tryton-server po-debconf translation to Spanish.
# Copyright (C) 2022
# This file is distributed under the same license as the tryton-server package.
# Camaleón , 2022.
#
msgid ""
msgstr ""
"Project-Id-Version: tryton-server\n"
"Report-Msgid-Bugs-To: tryton-ser...@packages.debian.org\n"
"POT-Creation-Date: 2022-07-26 18:26+0200\n"
"PO-Revision-Date: 2022-10-16 17:16+0200\n"
"Language-Team: Debian Spanish \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"
"Last-Translator: Camaleón \n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"Language: es\n"

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:1001
msgid "Initial admin password for Tryton:"
msgstr "Contraseña inicial del administrador de Tryton:"

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:1001
msgid ""
"The Tryton database will be populated with an initial superuser, named "
"'admin', and the password you provide here will be used as the initial "
"password of this superuser. This password will be required for the first "
"login."
msgstr ""
"La base de datos de Tryton se rellenará con un súperusuario inicial llamado "
"«admin» y la contraseña que proporcione en este apartado se usará como "
"contraseña inicial de este súperusuario. Necesitará esta contraseña para el "
"primer inicio de sesión."

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:1001
msgid ""
"If left empty a random password will be used. You can reset this password "
"from the command line with"
msgstr ""
"Si la deja en blanco, se usará una contraseña aleatoria. Podrá restablecer "
"esta contraseña desde la línea de órdenes con"

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:1001
msgid ""
"$ sudo -u tryton trytond-admin -c /etc/tryton/trytond.conf --password -d "
""
msgstr ""
"$ sudo -u tryton trytond-admin -c /etc/tryton/trytond.conf --password -d "
""

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:1001
msgid ""
"Note: The initialization of the database may take some time, please be "
"patient."
msgstr ""
"Nota: La inicialización de la base de datos puede llevar algún tiempo, tenga "
"paciencia."

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:2001
msgid "Email address for the admin user:"
msgstr "Dirección de correo electrónico del usuario administrador:"

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:2001
msgid ""
"This email address receives all kind of administrative messages for the  "
"admin user."
msgstr ""
"Esta dirección de correo electrónico recibe todo tipo de mensajes "
"administrativos dirigidos al usuario administrador."

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:2001
msgid "The value should be a FQDN (Full Qualified Domain Name)."
msgstr "Debe introducir un nombre de dominio completamente cualificado (FQDN)."

#. Type: boolean
#. Description
#: ../tryton-server-uwsgi.templates:1001
msgid "Configure workers for the Tryton server?"
msgstr ""
"¿Desea configurar servicios de trabajo («workers») para el servidor Tryton?"

#. Type: boolean
#. Description
#: ../tryton-server-uwsgi.templates:1001
msgid ""
"Some Tryton server tasks may be performed in the background asynchronically "
"by workers in a task queue."
msgstr ""
"Algunas tareas del servidor Tryton las pueden ejecutar servicios de trabajo "
"en segundo plano de manera asíncrona en una cola de tareas."

#. Type: boolean
#. Description
#: ../tryton-server-uwsgi.templates:1001
msgid ""
"If workers are configured those tasks (like e.g. the processing of sales, "
"invoices or purchases) can be automatically performed by workers. They do "
"not wait for completion in the clients thus removing the need of waiting and "
"doing serialized steps."
msgstr ""
"Si configura servicios de trabajo, las tareas como procesamiento de ventas, "
"facturas o compras, se pueden ejecutar automáticamente por los servicios de "
"trabajo. Este tipo de tareas no tienen que esperar a finalizar en los "
"clientes, y por lo tanto, evitan que tenga que esperar y realizar pasos en "
"serie."

#. Type: boolean
#. Description
#: ../tryton-server-uwsgi.templates:2001
msgid "Configure cron for the Tryton server?"
msgstr "¿Desea configurar cron para el servidor Tryton?"

#. Type: boolean
#. Description
#: ../tryton-server-uwsgi.templates:2001
msgid ""
"There exist several Tryton server cron jobs that mainly run periodically "
"some maintenance tasks on the database. They can be configured with the "
"clients."
msgstr ""
"Existen varias tareas de cron que principalmente ejecutan algunas tareas de "
"mantenimiento en la base de datos. Puede configurar estas tareas con los "

Bug#1022857: coreutils: printf refuses ~all unicode values smaller than 0x7F for \u and \U?

2022-10-27 Thread Pádraig Brady

On 27/10/2022 01:23, наб wrote:

Package: coreutils
Version: 8.32-4+b1
Severity: normal

Dear Maintainer,

On both of the above versions, on both LC_ALL=en_GB.UTF-8 and
LC_ALL=C.UTF-8, I get:
-- >8 --
$ for i in $(seq 0 255); do /bin/printf '\U'$(printf '%08X' $i)'\n'; done  2>&1 
| paste - - - -
/bin/printf: invalid universal character name \U/bin/printf: 
invalid universal character name \U0001


Right. This is an explicit restriction in printf(1)
which comes from the C standard.  That's so that
C compilers that don't support universal characters
don't have to consider them in other contexts.

Now printf(1) is not C, so we should lift this restriction I think.

I'll do that upstream now.

thanks,
Pádraig



Bug#1022898: find-dbgsym-packages: improve error message for missing library

2022-10-27 Thread Jakub Wilk

Package: debian-goodies
Version: 0.88.1
Severity: wishlist
Tags: patch

--
Jakub Wilk
From: Jakub Wilk 
Date: Thu, 27 Oct 2022 15:39:41 +0200
Subject: [PATCH] find-dbgsym-packages: improve error message for missing
 library

Before:

$ find-dbgsym-packages /usr/lib/firefox-esr/libxul.so > /dev/null
W: Cannot parse ldd output: '	libmozsandbox.so => not found'
W: Cannot parse ldd output: '	liblgpllibs.so => not found'
W: Cannot parse ldd output: '	libmozsqlite3.so => not found'
W: Cannot parse ldd output: '	libmozgtk.so => not found'
W: Cannot parse ldd output: '	libmozwayland.so => not found'

After:

$ find-dbgsym-packages /usr/lib/firefox-esr/libxul.so > /dev/null
W: Library not found: libmozsandbox.so
W: Library not found: liblgpllibs.so
W: Library not found: libmozsqlite3.so
W: Library not found: libmozgtk.so
W: Library not found: libmozwayland.so
---
 find-dbgsym-packages | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/find-dbgsym-packages b/find-dbgsym-packages
index 81eb3cc..07789c8 100755
--- a/find-dbgsym-packages
+++ b/find-dbgsym-packages
@@ -251,6 +251,8 @@ sub get_files_from_elf
 push @libs, $1;
 } elsif ($line =~ /^\t(.+) \(0x[0-9a-f]+\)$/) {
 push @libs, $1;
+} elsif ($line =~ /^\t(.+) => not found$/) {
+warn "W: Library not found: $1\n";
 } else {
 warn "W: Cannot parse ldd output: '$line'\n";
 }
-- 
2.37.2



Bug#1022897: ITP: rust-ws -- lightweight, event-driven WebSockets for Rust

2022-10-27 Thread Jonas Smedegaard
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 
X-Debbugs-Cc: debian-de...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: rust-ws
  Version : 0.9.2
  Upstream Author : Jason Housley 
* URL : https://github.com/housleyjk/ws-rs
* License : Expat
  Programming Lang: Rust
  Description : lightweight, event-driven WebSockets for Rust

 This library provides an implementation of WebSockets,
 RFC6455 using MIO.
 It allows for handling multiple connections on a single thread,
 and even spawning new client connections on the same thread.
 This makes for very fast and resource efficient WebSockets.
 The API design abstracts away the menial parts of the WebSocket protocol
 and allows you to focus on application code
 without worrying about protocol conformance.
 However, it is also possible to get low-level access
 to individual WebSocket frames
 if you need to write extensions
 or want to optimize around the WebSocket protocol.

This package will be maintained in the collaborative Debian section of
Salsa, at .

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNahT4ACgkQLHwxRsGg
ASG0+A/7B+eCdv5I/kkINGFgwUoEn7uskDTymXc3LPED9G/+aGE5S4Z/i/2+H8YS
Z+pCYO+yEYhqLG9TrOcO/qbZh3QcrQ0OgUPkkWxRCmw2shaKPd9tuEOKpuyivtoK
E0DP0fx/W6XH0L+lWk1wrgG7AUTx5tR0UA9QqeoKI8BIlOvcvQYbRmjKSYBrgXrR
XlNnjrecxsUr6yo+BIVoRSoKX3Bgd0jpwW4tdd5MyHT2BV9cxruH18Z7zegaAcN8
cq31i9CTcqqdbiFseb6IDcnNYHkEgUeHlkztcXmQXtIaeKoX5cLbnUMK1BZ7FuDS
9PIIXZILo/WuSrbitmvM5mW5zXMb7GvMqfvvWvzuApt6OF4Nl7imnPfZsjmLicL0
CTvFyTmyRJcEsVXyTJYC9XEyQiyE9QQ9ARTpwNgVY0AZml9l8ipHMN9HytZDN7qr
SkAGWx0QqrRLLqpDUO4t6KpOgUhOftAXfaVWxbdoj4yPAURnhEVwYPM4qwk9woa3
YmnEh29CXnpdD2nrmHvUZJu865CxOHt6hf61E4Gxo346v8Kbz+jJXzC6up0ctqvA
LsMDgmDQmyaaT/n3N+qKOKQTMJ8ss1BJTXSJk/d2qkD7t31MVwzE/7SpPDdXK0AN
xmW41UrRgwoRBkzSSV5Au+VGZTpOS7xK7bkUPyn5bZ0MWiUDU0c=
=SL3n
-END PGP SIGNATURE-



Bug#1022566: fonts-mplus: upgrade of mplus leaves an old /usr/share/fonts/truetype/mplus behind

2022-10-27 Thread Alexandre Detiste
Le mer. 26 oct. 2022 à 12:31, Hideki Yamane  a écrit :
>
>  It was not created by fonts packages, but by fontconfig.
>  And, it seemed to be fixed in upstream now.
>  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897040

Hi, thanks, but will fontconfig clean-up everything;
all those directories with the .uuid file but nothig else;
or is it too late and all individual font package will have
to clean up individualy the old directories ...?


Greeting,

Alexandre Detiste



Bug#1022896: rust-rusty-pool: autopkgtest failure

2022-10-27 Thread Adrian Bunk
Source: rust-rusty-pool
Version: 0.7.0-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-rusty-pool/27568708/log.gz

...
autopkgtest [03:39:50]: test librust-rusty-pool+default-dev:default: 
/usr/share/cargo/bin/cargo-auto-test rusty_pool 0.7.0 --all-targets
autopkgtest [03:39:50]: test librust-rusty-pool+default-dev:default: 
[---
crate directory not found: /usr/share/cargo/registry/rusty_pool-0.7.0
autopkgtest [03:39:50]: test librust-rusty-pool+default-dev:default: 
---]
autopkgtest [03:39:51]: test librust-rusty-pool+default-dev:default:  - - - - - 
- - - - - results - - - - - - - - - -
librust-rusty-pool+default-dev:default FAIL non-zero exit status 1
autopkgtest [03:39:51]:  summary
rust-rusty-pool:@FAIL non-zero exit status 1



Bug#1022895: rust-rusty-pool FTBFS on 32bit

2022-10-27 Thread Adrian Bunk
Source: rust-rusty-pool
Version: 0.7.0-2
Severity: important
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=rust-rusty-pool=0.7.0-2

...
failures:

 tests::test_try_increment_worker_total stdout 
thread 'tests::test_try_increment_worker_total' panicked at 'assertion failed: 
`(left == right)`
  left: `65536`,
 right: `0`', src/lib.rs:1802:9
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.61.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.61.0/library/core/src/panicking.rs:143:14
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
 at /usr/src/rustc-1.61.0/library/core/src/panicking.rs:182:5
   4: rusty_pool::tests::test_try_increment_worker_total
   5: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.61.0/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.

 tests::worker_count_test stdout 
thread 'tests::worker_count_test' panicked at 'assertion failed: `(left == 
right)`
  left: `63581`,
 right: `456797`', src/lib.rs:1766:9
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.61.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.61.0/library/core/src/panicking.rs:143:14
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
 at /usr/src/rustc-1.61.0/library/core/src/panicking.rs:182:5
   4: rusty_pool::tests::worker_count_test
   5: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.61.0/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.


failures:
tests::test_try_increment_worker_total
tests::worker_count_test

test result: FAILED. 33 passed; 2 failed; 1 ignored; 0 measured; 0 filtered 
out; finished in 82.06s

error: test failed, to rerun pass '--lib'
dh_auto_test: error: /<>/debian/dh-cargo/bin/cargo test returned 
exit code 101
make: *** [debian/rules:9: binary-arch] Error 25



Bug#1022890: cruft-ng: Broken symlinks not yet implemented

2022-10-27 Thread Alexandre Detiste
Hi,

I think you are right, it is misleading.
But this would be better implemented another way
or in other tools (e.g. "adequate" ?).

So I will simply remove this line from now.

Thanks

Alexandre

>
> cruft-ng does not yet support reporting of broken symlinks
>
> But the report still produces the line
>
>  broken symlinks: / 
>
> with no broken symlinks listed, which could be misleading



Bug#1022894: libunistring/1.1-1~experimental1 -- Unicode string library for C

2022-10-27 Thread Jörg Frings-Fürst
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

   Package name : libunistring
   Version  : 1.1-1~experimental1
   Upstream contact : Bruno Haible 
   URL  : https://www.gnu.org/software/libunistring/
   License  : GPL-2+ with distribution exception, GPL-3+, 
  GPL-3+ or GFDL-1.2+, MIT, GPL-2+,
  LGPL-3+ or GPL-2+, FreeSoftware
   Vcs  : https://jff.email/cgit/libunistring.git
   Section  : libs

The source builds the following binary packages:

  libunistring-dev - Unicode string library for C - development files
  libunistring5 - Unicode string library for C
  libunistring2 - Unicode string library for C [transitional package]

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

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

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

 dget -x 
https://mentors.debian.net/debian/pool/main/libu/libunistring/libunistring_1.1-1~experimental1.dsc

or from 

 git 
https://jff.email/cgit/libunistring.git?h=release%2Fdebian%2F1.1-1_experimental1



Changes since the last upload:

 libunistring (1.1-1~experimental1) experimental; urgency=medium
 .
   * New upstream release.
   * Transition from libunistring2 to libunistring5:
 - Rename debian/libunistring2.* to libunistring5.*.
 - debian/control:
   + Rename package libunistring2 to libunistring5,
 Add Breaks and Replace.
   + New transitional package libunistring2.
 - debian/rule:
   + Change dpkg-gensymbols to the new package.
 - Refresh / Rebuild symbols file.
 - Remove debian/libunistring5.symbols.hurd-i386.
   * Remove unused patches:
 - debian/patches/0010-AC_INIT.patch
 - debian/patches/0005-fix_build_musl.patch
 - debian/patches/0705-gcc-9.patch




Regards,
-- 
  Jörg Frings-Fürst
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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


Bug#1022851: xorriso: -clone across sessions copies, not clones

2022-10-27 Thread Thomas Schmitt
Hi,

the miracle of staying or moving is decided by the alphabetic sequence
of imported original and freshly made clone.
This lets the files keep their old data storage address:
  -clone /hello/hello.world /hello/hello.z
This causes data storage in the new session:
  -clone /hello/hello.world /hello/hello.clone

By a shortcomming of the static function iso_tree_clone_file() in
libisofs/tree.c the cloned file is not marked as being imported from
the loaded ISO, as is its original. This mark is important for the
decision at image write time, whether a node can re-use its data storage
or needs data storage in the new session.

When the image production traverses the tree in alphabetic order it
meets "hello.clone" before "hello.world" and decides the storage need
of both by the missing import mark of "hello.clone".
When it encounters "hello.world" before "hello.z", then it decides that
no new storage is needed.

Please verify this behavior with your local experiment.

I plan to fix the bug in libisofs this evening.


Have a nice day :)

Thomas



Bug#1022893: golang-github-etcd-io-gofail: binary-any FTBFS

2022-10-27 Thread Adrian Bunk
Source: golang-github-etcd-io-gofail
Version: 0.0.0+git.2022.09.25.d0d2a96a6e-3
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Thomas Goirand 

https://buildd.debian.org/status/logs.php?pkg=golang-github-etcd-io-gofail=0.0.0%2Bgit.2022.09.25.d0d2a96a6e-3

...
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
rm 
/<>/debian/golang-github-etcd-io-gofail-dev/usr/share/gocode/src/go.etcd.io/gofail/.gitignore
rm: cannot remove 
'/<>/debian/golang-github-etcd-io-gofail-dev/usr/share/gocode/src/go.etcd.io/gofail/.gitignore':
 No such file or directory
make[1]: *** [debian/rules:15: override_dh_install] Error 1



  1   2   >