Bug#1070063: Remmina fails to connect with Windows systems: Protocol Security Negotiation Failure (older release works)

[Daniel Leidert]

Package: remmina
Version: 1.4.35+dfsg-1+b1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

when I try to connect to a windows (11) system, I get errors saying something
like "check security protocol negotiation". When I set it the security protocol
negotiation to automatic detection, there is a connection attempt, but the
credentials are not accepted. As I haven't changed anything in the RDP setup, I
tried downgrading to version 1.4.34, and everything works now as expected
again. I'm not quite sure if this issue is related to
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2062177 and/or
https://gitlab.com/Remmina/Remmina/-/issues/3090, or if this is a complete
different issue.

Regards, Daniel


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

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

Versions of packages remmina depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.14.10-4+b1
ii  libavahi-client3  0.8-13+b2
ii  libavahi-common3  0.8-13+b2
ii  libavahi-ui-gtk3-00.8-13+b2
ii  libayatana-appindicator3-10.5.93-1+b1
ii  libc6 2.37-19
ii  libcairo2 1.18.0-3+b1
ii  libcurl4t64 [libcurl4]8.7.1-4
ii  libgcrypt20   1.10.3-2+b1
ii  libglib2.0-0t64 [libglib2.0-0]2.78.4-7
ii  libgtk-3-0t64 [libgtk-3-0]3.24.41-4
ii  libjson-glib-1.0-01.8.0-2+b1
ii  libpango-1.0-01.52.1+ds-1
ii  libsodium23   1.0.18-1+b1
ii  libssh-4  0.10.6-2+b1
ii  libssl3t64 [libssl3]  3.2.1-3
ii  libvte-2.91-0 0.75.92-1
ii  remmina-common1.4.34+dfsg-1

Versions of packages remmina recommends:
ii  remmina-plugin-rdp 1.4.34+dfsg-1
ii  remmina-plugin-secret  1.4.34+dfsg-1
ii  remmina-plugin-vnc 1.4.34+dfsg-1

Versions of packages remmina suggests:
ii  remmina-plugin-exec 1.4.34+dfsg-1
pn  remmina-plugin-kwallet  
pn  remmina-plugin-python   
ii  remmina-plugin-spice1.4.34+dfsg-1
ii  remmina-plugin-www  1.4.34+dfsg-1
pn  remmina-plugin-x2go 

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmYvo20ACgkQS80FZ8KW
0F019w/+L5a7P2ISCuVfYN0TDIXNvW97noLHv0798jJ3cX2zX1DJ0CSyF5oLXLbt
ctVCobfZitMax1mUCpxgQYbEody6bZVRMdnb1SQEbiue+sx5iqsd+tYDmfwNThV9
FpLs203BuFg2CmjblhxpJ2AWlpCxQJUv39EVNtYFDnCHFW0hFbtdtIx48d6n7Byt
N4Ys0d5z9c+BeTpSMgT26DeVoxE0dIGaL2/tC1X4/mjlf23NMZyweKHS1YSo8/v7
Or6Z0tAFhdSF49320LNCqu6Y/jLwW9/gcJuzkRT6QBc6kBThOJvtSiLvREdlfytm
Ou421mvqU7nG3FKM0g987wgCZw/3ZmizsZESh4J1b2yrXc/Lr+T+XmEA8v3u5e+j
XMy7rJ7a5mWZt3iaikCxuq3RHQJM4eAhtfp1Obp5gyS06+65SB2vppWPHIjIcOfh
X6uqULCcSITwesyOWvd0w/iPmVrGaSjJCp6VrzWVXngKOdYWnyU+cV+yPVcP+GKE
T/iSDmssoeoFE1AjF8O+fSu/qP2E0VnsJ+cYpkU4LrcZ+RiLpNolTlws0Jgw1Q/n
4x3pDc01KH7aSdEqZU8DB4/CXgiPsvxEWqcTX3gTX33Q5LXXtOmZOsSnfD7X3OqG
9CQsUosvRuEQyaxFG4KGgiwnllJHcSvn1Moa1uaIGBqeJuxBgvI=
=2ZY6
-END PGP SIGNATURE-

Bug#1067124: Ping

[Daniel Leidert]

Hi,

I would like to send a ping. If this was fixed, I could upload the
pdns-recursor to Buster LTS. Your help is appreciated.

Regards, Daniel


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

Bug#1067124: ftp.debian.org: LTS package upload of pdns-recursor 4.1.11-1+deb10u2 REJECTED

[Daniel Leidert]

Package: ftp.debian.org
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I tried to upload pdns-recursor_4.1.11-1+deb10u2 to buster-security as part of
LTS, but it failed with:

pdns-recursor_4.1.11-1+deb10u2_amd64.deb: Built-Using refers to non-existing 
source package publicsuffix (= 20220811.1734-0+deb10u1)

Please inject the required source package onto security-master.

Regards, Daniel

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmX4zdoACgkQS80FZ8KW
0F3DYBAAnaPAergxP6wrHUb4dJsD61GYRtXZO60LIAcalTxZsmT6zTr0mP+1vtVt
RIkqFlXB+Pte31lcwMQsuILpCZslTYk43kL9MqB5qEK2bt56gJuMGtDx9e5zfbhq
UWCIgBefKSrnCr1ZksIqD12zUN7/wpxsX/unUpRdyx8N/4kRvjM2bUUAhjheNf4V
U702oQ0ugtsEU/E/kpJXls/P1PfVpWzzs21D2GGblRO/ynnQr8dRtK/1bSZdIx04
nGrCVUGZ1U23+SFvLdSkt6Z0s9ACHnBi2FEPdji+2/ZfwX0euHdpcIuyt6y9fa9T
e/BzouaqNyGuq7VJkU1MG/wPBt6IcpNKX4z4gROaSceKG511XNEUIO8amGH4Y8F4
liwhT0MeuupNRpk+WcrH0EVbWtniYq3yek6gbUoAJrJ1vWLgUWjQDr6/jj2X/LOw
+J0ySvPl0GkfphZnflopLVzXMvfpAOlvgxfokSQqw+C0jsspq1P9GF6RJzedR7ZA
+8Qy4w5M9izWpksrSzvot38b42965mgoTRAasG9SXjAcOxQu1T211ukFJTUPlqpT
IghCXg1sC4AA9+lAFP9Yri+JYftflvh47BocKJ9nNghT5NDJAHgdXk6/eqldW+sl
n9ldmYzZOqoVgYU632tefvNx5J0Cuvxu02oIihPgYHCUkE4HYEI=
=9sWI
-END PGP SIGNATURE-

Bug#1059622: mcelog and pnputils don't have installation candidates

[Daniel Leidert]

Package: hw-probe
Version: 1.6.5-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The package recommends mcelog and pnputils. Both of these do not exist in
Debian. rmadison doesn't show any installation candidates at all. mcelog had
been removed in 2018, pnputils even in 2012. Please drop them from Recommends
or switch to existing alternatives.

Regards, Daniel



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

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

Versions of packages hw-probe depends on:
ii  acpica-tools   20230628-1
ii  curl   8.5.0-1
ii  dmidecode  3.5-3
ii  hdparm 9.65+ds-1
ii  hwinfo 21.82-1
ii  libwww-perl6.72-1
ii  lm-sensors 1:3.6.0-8
ii  lsb-release12.0-2
ii  mesa-utils 8.5.0-1
ii  pciutils   1:3.10.0-2
ii  perl [libdigest-sha-perl]  5.36.0-10
ii  perl-base  5.36.0-10
ii  smartmontools  7.4-2
ii  usbutils   1:015-1

Versions of packages hw-probe recommends:
ii  alsa-utils 1.2.10-1
ii  cpuid  20230614-1
ii  edid-decode0.1~git20220315.cb74358c2896-1.1
ii  ethtool1:6.6-1
ii  fdisk  2.39.3-2
ii  i2c-tools  4.3-4+b1
ii  iw 5.19-1
pn  mcelog 
ii  memtester  4.6.0-1
pn  pnputils   
ii  sysstat12.6.1-1.1
ii  upower 1.90.2-7
ii  vainfo 2.12.0+ds1-1
ii  vdpauinfo  1.5-2
ii  vulkan-tools   1.3.268.0+dfsg1-1
ii  wireless-tools 30~pre9-16
ii  x11-utils  7.7+6
ii  x11-xserver-utils  7.7+10
ii  xinput 1.6.4-1

hw-probe suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmWOylkACgkQS80FZ8KW
0F0Z2BAA2dr5Zi7oWMQE9D62IO6I9aTU4RxFWT/6gWsO6gDX5SOobJhfKjvYnxdL
AActD9uCORdKZKmW841CmufnzqNDNSohdF0IGeWPdV/IBDGZlCgdmgnVm3UxKyhX
vNAZXozfzgpIrWldpoW5jRcAFyWn8JO3sSmwtCBiaUqr/U1tKGQuXIBYcJY86Kwz
xjUzXGqTA9hx1rjOZusGUx3WnJET1thr/Y1tQI1SAztAV9OBLgNqAkBSUafNM7SV
tkQhMdspw1QWE8Qfn+cIEz3MHKv3VdnYRf07Jw7Lxj97heKW+/R2hAboesbFgtAM
jHNheCPOt6SQSUNwCp/ZL2OOT851eWYHzY5sLDwLtqQllLfdtgNMA9fipYuW/wFs
dYAZldiIn1BonMgA9sLx008FuDL+UtYtzm2mBux2SpQdRRlIGelql99BdMCSYLjH
9gT6CKuYNc/ZdT7DccrUaraPpzkBg+vVLMgZ8+ho6nL3JWqNWp4l186UzV4gn37P
kMJgeaFsTfz2I0wKdBm6BHvYCea1EbAlAA1f9wlaXu0fH6iQVD2hIRiFUvqGlO7i
+b+TGuTVOFlVpgZEp9PInaXwI6RonFspEmFfpyZ+99qBdYt2bCLb4k4r7cxmaEV8
0Ai/Db6whulN2bBEfyIkHe1JAYTwx3CGqE87+L2mQcqNJObMyOo=
=lniF
-END PGP SIGNATURE-

Bug#1059132: Missed to ship /lib/firmware/i915/mtl_huc_gsc.bin, available in the source?

[Daniel Leidert]

Source: firmware-misc-nonfree
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The file i915/mtl_huc_gsc.bin is part of the source. However, it is not shipped
and leads to the usual:

W: Possible missing firmware /lib/firmware/i915/mtl_huc_gsc.bin for module i915

I wonder if it has been missed, or if it is not shipped on purpose.

Regards, Daniel


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

Kernel: Linux 6.5.0-5-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmWCyyMACgkQS80FZ8KW
0F10dA//b7TbFQTAXZXoog/i0gELCJ5oEGaTfNmUilmV1g3xiKb317henCX2dhx9
YcQ67JohfS+0j8M9GCWYOC+CN8IWhIZEhOAN8CMYiaAYGltzPxrGgzaYJEgTGDVj
gpk/7JZcW5chnCodQAdvyRWVvMprToeJv76CmrdkBKwnL9+xAhwl/pgkHqN9Cy+s
emzwf9yRaqWjzsXoxnJwt2hvIBUAZePxLIS3KT927xR2oAMLgdOte8bXN9av5gaQ
CB3xIDPD171bAJNYchuUgyWQeiVmKTp6tOE62iO0BYeTfSsmk+UHI3HJ0lB91GbZ
SK1/EkkL+eMiw4GCXlVQ1gqVymVdDXKYmU81UEB+zj9Sl6bGslYv0VlO0EwwrQH5
dXalv7lAEyr9WYjMjT8kS7KK+pNHXC403cEvrr3+l7htbJB8wJIBkbm4Z0zC2VeL
WC4z8YHQx8yEroMb+gDttBNGj3CZxuISh9DtV31QhCItK4X1bdplAOh2lC2m7B98
kZJ+EAXJpq9n/+rpMHSEatdcoKxAqJUdCOdwXXCLsRmdTYeE9qr39scQ6hlqQGyI
GPi+6IFgf/aXJcG07J3nM5kUsRIQAK2X4KktBN0V3kPwijHQhswHFnNwkjFCxrti
YYca7kDaoDI0etz485yumGfzVJYIov2xX7gWEZ7jp1rF3rr6wpg=
=Hgoa
-END PGP SIGNATURE-

Bug#1056601: No module named

[Daniel Leidert]

Package: ansible
Version: 7.7.0+dfsg-3
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

When trying to use the community.general.ssh_config module, I receive:

An exception occurred during task execution. To see the full traceback, use
- -vvv. The error was: ModuleNotFoundError: No module named 'paramiko' fatal:
[localhost]: FAILED! => {"changed": false, "msg": "Failed to import the
required Python library (PARAMIKO) on [hostname]'s Python /usr/bin/python3.
Please read the module documentation and install it in the appropriate
location. If the required library is installed, but Ansible is using the wrong
Python interpreter, please consult the documentation on
ansible_python_interpreter"}

Regards, Daniel


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

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

Versions of packages ansible depends on:
ii  ansible-core   2.14.11-2
ii  openssh-client 1:9.4p1-1
ii  python33.11.4-5+b1
ii  python3-distutils  3.11.5-1
ii  python3-dnspython  2.4.2-1
ii  python3-httplib2   0.20.4-3
ii  python3-jinja2 3.1.2-1
ii  python3-netaddr0.8.0-2
ii  python3-yaml   6.0.1-1

Versions of packages ansible recommends:
ii  python3-argcomplete   3.1.4-1
ii  python3-cryptography  38.0.4-4
ii  python3-jmespath  1.0.1-1
ii  python3-kerberos  1.1.14-3.1+b7
ii  python3-libcloud  3.4.1-5
ii  python3-selinux   3.5-1
ii  python3-winrm 0.4.3-1
ii  python3-xmltodict 0.13.0-1

Versions of packages ansible suggests:
pn  cowsay   
ii  sshpass  1.09-1+b1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmVfoxMACgkQS80FZ8KW
0F05SA//efTf36NuG0AAA/KlctZC9MsqhtNHUtlN8lxqeRrMJ4gEqOJtHimwt+3n
iE4ofPaFwU/fYWjKpmDbLoiu7WQ8AlDlgz1Xy3c4xue/KjGi6e5RvUBq70uEOuIq
qErnRFc5yiSRtOEGLeEGpfGsHw0UZrahpGVO9p1DMIWCwbLRaRcohbe1ok7Mlo6f
ynkK00Npvs8cumobsDolbyT7ofZo47NPZFAH3WugGLNsvcuHeCjLsxmpRzDq5UzS
XeaFUEIwRS5rTX6a3e+iKj/HBlIo5Oleorus0Ehyprkgbo9tyMqZEOY/+Cdexhud
VSt3bA/8fprfdOvl0JAftNTM71XwdlppwioO6NLpfQBiYtVzTZ2w3461QbSKzTHs
0rSUFgGYMzEzas54Bvra9ygCyk5hxc6IJVkwC+jX8q3ME07bej3G1PjX78z72RQY
PWCPU92/Oa7shAEwn+Xtd/MMNZEU5wCALql6WGdaVgq9NhT3CYtQNOCwf2M1z27L
SfAoVXVXKGTve8spwZxhI6QGMpD1431IarWVRsFNr3qolk/YgseWWmz27T3rdxQA
Gi97MnqvMPSL48Q7GMzavzZ1u9nqdS+4gmPigtDOjNEi3eh8k3473TXctzJpqi5K
TUSNCCNA74BbblacuNlBdMIyJrNF226ubnM3zwoakpOu2E007So=
=bCRB
-END PGP SIGNATURE-

Bug#1056546: When using a cached root-fs, vmdb2 runs apt before mounting the virtual filesystems, leading to some errors

[Daniel Leidert]

Package: vmdb2
Version: 0.28-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I have a chached rootfs. Here the snippet from the .vmdb2 file:

  - mount: /

  - unpack-rootfs: /

  - debootstrap: bookworm
target: /
mirror: https://deb.debian.org/debian
arch: amd64
components:
  - main
  - contrib
  - non-free
exclude: info
require_empty_target: false
unless: rootfs_unpacked

  - virtual-filesystems: /

  - shell: |
  [.. some commands ..]



Here the log:

Exec: ['mount', '/dev/mapper/loop5p2', '/tmp/tmplyhry3x_']
Exec: ['tar', '-C', '/tmp/tmplyhry3x_', '-xf', 'production-vm.amd64.tar.gz', 
'--numeric-owner']
Exec: ['cp', '/etc/resolv.conf', '/tmp/tmplyhry3x_/etc/resolv.conf']
debootstrap plugin set architecture to amd64
Exec: ['chroot', '/tmp/tmplyhry3x_', 'apt-get', 'update']
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Sub-process apt-key returned an error code (29)/usr/bin/apt-key: 95: cannot 
create /dev/null: Permission denied
Err:1 http://deb.debian.org/debian bookworm InRelease
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Sub-process apt-key returned an error code (29)/usr/bin/apt-key: 95: cannot 
create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
  gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
Err:2 http://deb.debian.org/debian bookworm-updates InRelease
E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Sub-process apt-key returned an error code (29)W: An error occurred during the 
signature verification. The repository is not updated and the previous index 
files will be used. GPG error: http://deb.debian.org/debian bookworm InRelease: 
gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
  gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Err:3 http://deb.debian.org/debian-security bookworm-security InRelease
W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://deb.debian.org/debian bookworm-updates InRelease: gpgv, gpgv2 or gpgv1 
required for verification, but neither seems installed
  gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Reading package lists...
W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://deb.debian.org/debian-security bookworm-security InRelease: gpgv, gpgv2 
or gpgv1 required for verification, but neither seems installed
W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease  gpgv, 
gpgv2 or gpgv1 required for verification, but neither seems installed
W: Failed to fetch 
http://deb.debian.org/debian/dists/bookworm-updates/InRelease  gpgv, gpgv2 or 
gpgv1 required for verification, but neither seems installed
W: Failed to fetch 
http://deb.debian.org/debian-security/dists/bookworm-security/InRelease  gpgv, 
gpgv2 or gpgv1 required for verification, but neither seems installed
W: Some index files failed to download. They have been ignored, or old ones 
used instead.
Exec: ['mount', 'none', '/tmp/tmplyhry3x_/proc', '-t', 'proc']
Exec: ['mount', '/dev', '/tmp/tmplyhry3x_/dev', '--bind']
Exec: ['mount', 'none', '/tmp/tmplyhry3x_/dev/pts', '-t', 'devpts']
Exec: ['mount', 'none', '/tmp/tmplyhry3x_/dev/shm', '-t', 'tmpfs']
Exec: ['mount', 'none', '/tmp/tmplyhry3x_/run', '-t', 'tmpfs']
Exec: ['mount', 'none', '/tmp/tmplyhry3x_/run/lock', '-t', 'tmpfs']
Exec: ['mount', 'none', '/tmp/tmplyhry3x_/sys', '-t', 'sysfs']
Exec: ['sh', '-ec', ... the commands from the shell target ... ]

I'm not quite sure about this, but shouldn't "virtual-filesystems" be a
requirement before running apt (which seems to be called by vmdb2 internally,
not by a target).

Regards, Daniel


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

Kernel: Linux 6.5.0-4-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: 

Bug#1055672: Depends on python3-typed-ast, which has been removed from testing and unstable due to #1051802

[Daniel Leidert]

Package: prospector
Version: 1.1.7-4
Severity: serious
X-Debbugs-Cc: daniel.leid...@ext.secunet.com

The package declares a dependency on python3-typed-ast. However, due to
#1051802, this package is no longer available. It is my understanding that
python3-typed-ast has been superseeded by the "ast" standard library in Python
3.8+. Thus, prospector is currently uninstallable.

Regards, Daniel


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

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

Versions of packages prospector depends on:
ii  dodgy  0.1.9-5
ii  libjs-sphinxdoc7.2.6-2
ii  pylint 2.17.4-1
ii  python33.11.4-5+b1
ii  python3-astroid2.15.6-1
ii  python3-mccabe 0.7.0-1
ii  python3-mypy   1.6.1-1
ii  python3-pep8-naming0.10.0-2
ii  python3-pycodestyle2.10.0-1
ii  python3-pydocstyle 6.3.0-1
ii  python3-pyflakes   2.5.0-1
ii  python3-pylint-celery  0.3-7
ii  python3-pylint-django  2.0.13-3
ii  python3-pylint-flask   0.5-5
ii  python3-pylint-plugin-utils0.7-3
ii  python3-pyroma 2.6b2-1
ii  python3-requirements-detector  0.6-4
ii  python3-setoptconf 0.3.0-2
ii  python3-typed-ast  1.5.4-1+b1
ii  python3-yaml   6.0.1-1

Versions of packages prospector recommends:
ii  vulture  2.7-1

prospector suggests no packages.

-- no debconf information

Bug#1055503: Suggests non-existent package vulkan-utils

[Daniel Leidert]

Package: nvidia-vulkan-icd
Version: 525.125.06-2
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

the package vulkan-utils does not exist (anymore). Please remove the suggestion
or replace it by vulkan-tools.

Regards, Daniel



- -- Package-specific info:
uname -a:
Linux gargravarr 6.5.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.10-1 
(2023-11-03) x86_64 GNU/Linux

/proc/version:
Linux version 6.5.0-4-amd64 (debian-ker...@lists.debian.org) (gcc-13 (Debian 
13.2.0-6) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC 
Debian 6.5.10-1 (2023-11-03)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.125.06  Tue May 30 05:11:37 
UTC 2023
GCC version:  gcc version 13.2.0 (Debian 13.2.0-6) 

[snip]

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmVKNp0ACgkQS80FZ8KW
0F1GHw//btZt26yfj6GN/hrimoAYTADJtmbraMCrBdxHbF3BOvsIT+D0fF767fVL
NDXMC/B2uWFRK2vt7kT0RF/r0S1K1qXJp+Kwzwk7B+ccEkJO9HFskfavgelJjvH7
YP0/yOrtsJgALlLfqSQWAUFllSyDzAp7Jyj4H4FdL90Xx7o/gRAOHifoudN3OrVn
Q96bWXzX3Q9zUhSY2kUHF1BYK0OACAGRROgObRBms1Zk+FQjaDCBO48qmWgbB6nu
cEcdjYvGA6W+Is7A2Cd6ufVMygAI0lmU/OgIYjqnFkdZ0kmXZ833jMzQSF5RmCOD
koc4BtzSkBFdWcc5uuwE/ImrpO18gi9cGgQ9Abds1xSE92oh4WK9KWhrXXBiXqCY
ibD4NhDgl1QQyFzvJ6a7hS/2mHK6oaOAhOSqNyeBlE/qCQgFVtJY4MDeniu5cWpA
IynPQJBPgQjJ3j5kEe63/r4dkVKIOVHwMC2sso5qh5TVLBmI7ijBTWQDQgLT2qVd
CNZ3GlhpuPjlmsCc4VwUsEqG5aeWO4tIYdyxfvFoVJ4J4yi3Daib+ZH+zouuORUr
JTkw6Bp6IPPS7ROesIKcJ2GiFxu2oGUcP4CWqNLT3kUbk0ae58MH+MlCa6lDBeqX
0v80dyb2aWLz+RyIjj0xRoX7l90T6QCljflVRcdBgu+VMJvdoIY=
=IWot
-END PGP SIGNATURE-

Bug#1053558: Impossible to add VPN connection or change settings of existing profiles

[Daniel Leidert]

Package: network-manager-openconnect-gnome
Version: 1.2.10-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

I have existing network-manager profiles for openconnect (anyconnect) and I try
to create new ones.  If I want to create a new profile, the dialog appears, but
after adding the necessary informtion and hitting the "Apply" button, nothing
has been saved.  There is no new connection shown in the VPN settings page. I
also tried to add a route to an existing connection profile. While it seems to
save the setting for automatically/manually setting routes, the route itself is
also not saved.  Right now, I have to write the profiles by hand. I don't see
any errors in the logs (except for "openconnect[...]: Failed to open
/dev/vhost-net", which I think is irrelevant).

There might be some relevance in these reports, though:

https://gitlab.gnome.org/GNOME/NetworkManager-openconnect/-/issues/106
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2499

Regards, Daniel


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

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

Versions of packages network-manager-openconnect-gnome depends on:
ii  libc62.37-12
ii  libgcr-base-3-1  3.41.1-3
ii  libgcr-ui-3-13.41.1-3
ii  libglib2.0-0 2.78.0-2
ii  libgtk-3-0   3.24.38-5
ii  libgtk-4-1   4.12.2+ds-1
ii  libnm0   1.44.0-1
ii  libnma-gtk4-01.10.6-1
ii  libnma0  1.10.6-1
ii  libopenconnect5  9.12-1
ii  libsecret-1-00.21.1-1
ii  libsoup2.4-1 2.74.3-1
ii  libwebkit2gtk-4.0-37 2.42.1-1
ii  libxml2  2.9.14+dfsg-1.3
ii  network-manager-openconnect  1.2.10-1

network-manager-openconnect-gnome recommends no packages.

network-manager-openconnect-gnome suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmUf0vUACgkQS80FZ8KW
0F28BhAAyfR7dmdgjUZJQwiy0lzYZ3adDS6qqaE1yKh/20U0JamyOCMIaOx4a/gq
+EaRWLsQhqUEAgauTZovLrwMsqC3Xb7yKGNLwqYH8+kJqErmj2JjpjbRzJVgZLat
zuWl9yey1GlWYTbhSmNTBv6Vm+YbebSfAq6jblJZJuMwkBWG6JMa1RqeP4eXoS8Q
t/dcNIE0WW8rz78oJy+qYVGsRQBESiT+7/XRfPGjJIDbWqWysg3oeSMQmDlauiT3
09hQTF+m5vAMaKCE7Iu4SBlA717FmLS1iFB31BJ35gE7k4m+GF8D7uUQ1LQEaGHR
cSnGQMkumXp9Usa1QICgMGPmSF2GoFIzvIVV9Z35le2nPHuGKCEpbshrCV/6eBWr
j5wTc0aQ59w2ZQGYDtYc5RBfFLHoj/UVr7bwx1zspGNLTAZt3sYLBy9VfBMs27qf
6AQLEyLT3icgIwLIGT7tX+2ubusstgljTlnCWjDE+QDOzNm0kdO/I9sPfldsdPkh
kQk+YvZdmule00DcP1jV2ljwOSuATkdZ6Ky+YmYAK+SajSaPmjNd29W2jWK7oNjM
QBVh9O/WP0Gnaot39Nr2oSaDy+98mKYy8ZOrxPmXWKNqP3O2njjhMdJI/T/HlGNL
hzHuj0GigyJ1FvI0kEmEYdnShkT4/MXLNcYZGdms0AST/2GiMKI=
=EkRK
-END PGP SIGNATURE-

Bug#1043283: resize-rootfs service takes a very long time with a Bookworm image: Timed out for waiting the udev queue being empty

[Daniel Leidert]

Package: vmdb2
Version: 0.27+really.0.26-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The images I built in the past started very quickly. In a recent Image based on
Debian Bookworm, the boot process needs several minutes. The `systemd-analyze
blame` command shows over 4 minutes of the process being caused by the
resize-rootfs service. The logs contain this:

[..]
Aug 08 12:30:11 production resize-rootfs[289]: Checking that no-one is using 
this disk right now ... FAILED
Aug 08 12:30:11 production resize-rootfs[289]: This disk is currently in use - 
repartitioning is probably a bad idea.
Aug 08 12:30:11 production resize-rootfs[289]: Umount all file systems, and 
swapoff all swap partitions on this disk.
Aug 08 12:30:11 production resize-rootfs[289]: Use the --no-reread flag to 
suppress this check.
Aug 08 12:30:12 production resize-rootfs[289]: Disk /dev/vda: 8 GiB, 8589934592 
bytes, 16777216 sectors
Aug 08 12:30:12 production resize-rootfs[289]: Units: sectors of 1 * 512 = 512 
bytes
Aug 08 12:30:12 production resize-rootfs[289]: Sector size (logical/physical): 
512 bytes / 512 bytes
Aug 08 12:30:12 production resize-rootfs[289]: I/O size (minimum/optimal): 512 
bytes / 512 bytes
Aug 08 12:30:12 production resize-rootfs[289]: Disklabel type: dos
Aug 08 12:30:12 production resize-rootfs[289]: Disk identifier: 0x3ae6c4c9
Aug 08 12:30:12 production resize-rootfs[289]: Old situation:
Aug 08 12:30:12 production resize-rootfs[289]: Device Boot  Start  End  
Sectors  Size Id Type
Aug 08 12:30:12 production resize-rootfs[289]: /dev/vda1 8192   819199  
 811008  396M ef EFI (FAT-12/16/32)
Aug 08 12:30:12 production resize-rootfs[289]: /dev/vda2   827392 16777215 
15949824  7,6G 83 Linux
Aug 08 12:30:12 production resize-rootfs[289]: /dev/vda1:
Aug 08 12:30:12 production resize-rootfs[289]: New situation:
Aug 08 12:30:12 production resize-rootfs[289]: Disklabel type: dos
Aug 08 12:30:12 production resize-rootfs[289]: Disk identifier: 0x3ae6c4c9
Aug 08 12:30:12 production resize-rootfs[289]: Device Boot  Start  End  
Sectors  Size Id Type
Aug 08 12:30:12 production resize-rootfs[289]: /dev/vda1 8192   827391  
 819200  400M ef EFI (FAT-12/16/32)
Aug 08 12:30:12 production resize-rootfs[289]: /dev/vda2   827392 16777215 
15949824  7,6G 83 Linux
Aug 08 12:30:12 production resize-rootfs[289]: The partition table has been 
altered.
Aug 08 12:30:12 production resize-rootfs[289]: Calling ioctl() to re-read 
partition table.
Aug 08 12:30:12 production resize-rootfs[289]: Re-reading the partition table 
failed.: Das Gerät oder die Ressource ist belegt
Aug 08 12:30:12 production resize-rootfs[289]: The kernel still uses the old 
table. The new table will be used at the next reboot or after you run 
partprobe(8) or partx(8).
Aug 08 12:30:12 production resize-rootfs[289]: Syncing disks.
Aug 08 12:32:22 production resize-rootfs[465]: Timed out for waiting the udev 
queue being empty.
Aug 08 12:34:22 production resize-rootfs[467]: Timed out for waiting the udev 
queue being empty.
Aug 08 12:34:22 production resize-rootfs[470]: resize2fs 1.47.0 (5-Feb-2023)
Aug 08 12:34:22 production resize-rootfs[470]: The filesystem is already 
1993728 (4k) blocks long.  Nothing to do!
Aug 08 12:34:22 production systemctl[471]: Removed 
"/etc/systemd/system/systemd-remount-fs.service.requires/resize-rootfs.service".
[..]

Two observations: The first check actually fails in both Bookworm and Bullseye.
However, the Bookworm image contains the two additional lines:

Aug 08 12:32:22 production resize-rootfs[465]: Timed out for waiting the udev 
queue being empty.
Aug 08 12:34:22 production resize-rootfs[467]: Timed out for waiting the udev 
queue being empty.

which seem to cause the delay.

I have not yet been able to examine the situation further. I'll try as soon as
I find some time.

Regards, Daniel


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

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

Versions of packages vmdb2 depends on:
ii  cmdtest 0.32.14.gcdfe14e-5
ii  debootstrap 1.0.128+nmu5
ii  e2fsprogs   1.47.0-2
ii  kpartx  0.9.4-5
ii  parted  3.6-3
ii  python3 3.11.4-5+b1
ii  python3-jinja2  3.1.2-1
ii  python3-yaml6.0.1-1
ii  qemu-utils  1:8.0.3+dfsg-5

Versions of packages vmdb2 recommends:
ii  ansible   7.7.0+dfsg-1
ii  dosfstools4.2-1
ii  qemu-user-static  1:8.0.3+dfsg-5

vmdb2 suggests no packages.

- -- no debconf information

-BEGIN PGP 

Bug#1041771: postinst: Unknown option: q

[Daniel Leidert]

Package: open-vm-tools-containerinfo
Version: 2:12.2.5-1
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The postinst throws this warning:

open-vm-tools-containerinfo (2:12.2.5-1) [..]
Unknown option: q
inactive

The -q switch used does not exist. The output ćan be redirected to /dev/null.

Regards, Daniel



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

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

Versions of packages open-vm-tools-containerinfo depends on:
ii  libabsl20220623  20220623.1-1
ii  libc62.37-6
ii  libcurl4 7.88.1-10
ii  libgcc-s113.1.0-9
ii  libglib2.0-0 2.76.4-3
ii  libgrpc++1.511.51.1-3+b2
ii  libgrpc291.51.1-3+b2
ii  libprotobuf323.21.12-6
ii  libstdc++6   13.1.0-9
ii  open-vm-tools2:12.2.5-1

open-vm-tools-containerinfo recommends no packages.

open-vm-tools-containerinfo suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmS9EzkACgkQS80FZ8KW
0F1aKQ//Zr/NgG70m5TGB3mts1bUgd/HCKzlAb+YIzalf7ZgyvEzzmhai+g5ZViM
l1IS8m/gGLi+e7DzFTC1fZJdJF59ZUoFZscY5V5G9DRy0wdCn6tshd1NqJ+GfyMK
ufkLBsbAiJOEI5XuFKNKJEpqVy2vOEX9SSEBOGg9VKaLRWsLRyQXsXoJL3kLhx1D
HIAMuvZ1Q4fh0If8BQrUo8ghztNFkUl+mUfadcwlb5HEZYGpvpM7m+5nXiBu7jZ5
aiQShB9NzWpi2udkz3W/Xv/YKbGZ6py7yfR1lyBHgOHabWHU0II+N6hdi9PZBT3X
Ib1RZThV5pxqx4smzBGnjfZoBcB6U0q3kGw2I9b2e/I11m747d4xlqV5DgIwMu5O
O6kG6ujL2/z7WQnuwGVqzP86864bbiurM7N4BxaKqPFW4Ji+aa1oU9Lnrnqhaq8O
4CssZxZAy3e995JvGHLLtrs/r4cLSObsXkfRrf65EC0I+SVDcmhGMHT5mxQa1HQp
8DAtVdM8A+P0BU8F7Uhb9dZ9VxYmZdKmEIY6Ce+dx2YI7dKOHEsChTWkEIyKvQIe
jMWqzwPka7AuBCddFSXgoDwKCYfM2U+zyq3rkn3coTgUxnQZ7qOYveKUqF+JcdU9
mBR+awgVsLwa8A+Xw7OvPtkziHs3/DqY5ZwXpsRuxYPKnx9NqN8=
=1r/4
-END PGP SIGNATURE-

Bug#1041642: dh_missing: Doesn't work if used in $(CURDIR)

[Daniel Leidert]

Package: debhelper
Version: 13.11.4
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I have a native package source from which I build multiple binary packages. The
files are organized as they would be on the target system with their full
destination path. As an example, the souirce directory contains:

./usr/share/applications/foo.desktop

Now I want to make sure that all files become part of a package and I don't
miss to ship any source files. I have multiple .install files in debian/ for
each package. There isn't any Makefile involved, nor do I install all files
into a temporary location first. I just want to make sure that all files,
except for the debian/ directory, are part of a package.

If I run:

dh_missing -XREADME.md -Xdebian/ --fail-missing

I don't get any error, even if I missed a file. This can be easily verified by
just removing one of the -X switches. It should throw an error then, but it
doesn't. But if I add the source directory like:

dh_missing -XREADME.md -Xdebian/ --sourcedir=$(CURDIR) --fail-missing

I get an error for all files, even if they are part of a package. The weird
part is that debhelper then says:

As an example, you might want to replace:
 * usr/share/applications/foo.desktop
with:
 * usr/share/applications/foo.desktop

Note that both paths are the same. Also, there is a .install file installing
usr/share/applications/foo.desktop.

This might be a cornercase, but I find it quite weird that it isn't working and
I could really use this. Is that a bug or a feature request?

Regards, Daniel


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

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

Versions of packages debhelper depends on:
ii  autotools-dev20220109.1
ii  dh-autoreconf20
ii  dh-strip-nondeterminism  1.13.1-1
ii  dpkg 1.21.22
ii  dpkg-dev 1.21.22
ii  dwz  0.15-1
ii  file 1:5.44-3
ii  libdebhelper-perl13.11.4
ii  libdpkg-perl 1.21.22
ii  man-db   2.11.2-2
ii  perl 5.36.0-7
ii  po-debconf   1.0.21+nmu1

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.202301

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmS6rjYACgkQS80FZ8KW
0F0WQQ//Y9WCIzZBOiOPGt6CN57N4l08JE3K0kIt/RqyT8Tif7mVSlvNsih4mV9R
G0i44C2s6RVOJ7LB8bPW3UYH2Jj3VO2I7RbNUc6TSCZ0cH4b5/l3OwktzvAh39AZ
L7zV6rgNfCLFVuy6MCyEGp01k88uE2yYX5swCMlf7vhoD+8N2a0otdyAU0RhlrXe
TQEcsZ3qhwNHU7QIyBrJZSA6Vzg0txrL9+z6mROAo5i0Qyk6f5CFV2PkgPpoU5Xh
6nw8N6C06ScSkbIF28O9WjI8VeI//RRoXZIjAxj8nDpxBLPt1qEGR08x2X5fW+2M
wE+9zb1iKPWzHD/8GsZ6BW4SEYktc6L8UsuprIvHi1d0o493rfGXgCVFF3xuJwGi
LuFfJIkPvL8CesVwYmI4rcL3ttF74LatoI9UxwnlLJLtErMX4FhTmQQwU1s6b1bl
yljR6QycPEZRhqCijO2reP2exMD1MsPkDyRIFSW6u3JKVWr6+Kz0uLsZIFBWGKFm
KgcsZcKk0Cf9K/mGOqvPe7Qb5LydWlZ8rub/Du0aW8T1kiSF1UrleGZgaXt3Ujy9
rDKIGmEZ05zKg6/1O0eHfD4bXJv/QIp+Js5TBNnJMkRMk77LB9AQo90NQBgLuX0y
MLaWIf2RthtcJ0quPoQ/wS1bPVJszusb20N9ySYkzHNfeV5i0Gc=
=L/9u
-END PGP SIGNATURE-

Bug#1040012: Possible missing firmware /lib/firmware/i915/dg2_huc_gsc.bin for module i915 that is part of the source

[Daniel Leidert]

Package: firmware-misc-nonfree
Version: 20230515-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The file dg2_huc_gsc.bin is part of the source, but it is not shipped as part
of firmware-misc-nonfree. I cannot find any reason, why it is not packaged as
well. So I wonder if this was simply an oversight?

Regards, Daniel



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

Kernel: Linux 6.3.0-1-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_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

firmware-misc-nonfree depends on no packages.

firmware-misc-nonfree recommends no packages.

Versions of packages firmware-misc-nonfree suggests:
ii  initramfs-tools  0.142

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmSfb/MACgkQS80FZ8KW
0F2zFRAAugH53qTDc9yWhh/0rVvAwTknHkWaWuiK2+u2MfHCrcQGCvPemfapJQSv
33W21sd7msHUf/ObRBRWcVrAWW3iJ1sDeZlllsfRi4+tOWLWiKD0ThoJ+GbNNM9c
aIDxUQNk0duR2RE7B7u1b4iSuf1qRda3oJ6Zg+5ywR4nn0PmAkaL0bru4zFHb0mr
vesINnlACtbPUKln3dyepbMhFNpCxQi9CTemkt+ctTvNQPG5ZOBvLnJLz6Xi7Deg
NXA2OcbBHKyoNp9XVz0L6dIFrKYYZyoqrvdP86s8Nk0u36Bxz/bIfIqzIl21JPZk
Ddyu+m62jCjgMfY+OecPM4dMbFQl2rpND5Tiz4a4HJ2n1v8tjilXATGLrTtfldU6
olxEWCLHVb2At+QEmFXuwEG5nzC1HlfIpl5vfFrIqY+bA15KUrahPbYJsjPf2DjW
uZhp9XrFbvbC2+pKFfYlLJaCmI28CoDaj3ih7KffmbuVbLmnhRyyixNCD6VtaEJ2
E6gUuO0t3QThSjjOHpjsKJvLuCjMBJsYIdm1OiaQbFsZq+zCSvfnRsdj5bY2tL1n
s8wsHhNhQhQOCSQSAOyrLg/mtTyCN5/xjwHUPKNdAumqAkcqcUGO0ZvD4ekgJsVt
RfX10Rmbtdl4zXSYwxkclgAxKnPZZ+M9LMFPS8To9pqwFT7Cy30=
=3K4y
-END PGP SIGNATURE-

Bug#1034771: generate_firmware_patterns failed: 512 at ./tmp/debian-cd/tools/make_disc_trees.pl line 1257

[Daniel Leidert]

Package: simple-cdd
Version: 0.6.9
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

With debian-cd 3.2.0, simple-cdd fails to create an installer image with the
following errors:

2023-04-24 03:07:41 ERROR build/debian-cd exited with code 2
2023-04-24 03:07:41 ERROR Last 5 lines of standard error:
2023-04-24 03:07:41 ERROR build/debian-cd: + exit 0
2023-04-24 03:07:41 ERROR build/debian-cd: xorriso 1.5.4 : RockRidge filesystem 
manipulator, libburnia project.
2023-04-24 03:07:41 ERROR build/debian-cd: missing metadata file 
./tmp/mirror/dists/bullseye/main/dep11/Components-amd64.yml.gz at 
./tmp/debian-cd/tools/generate_firmware_patterns line 172.
2023-04-24 03:07:41 ERROR build/debian-cd: generate_firmware_patterns failed: 
512 at ./tmp/debian-cd/tools/make_disc_trees.pl line 1257.
2023-04-24 03:07:41 ERROR build/debian-cd: make: *** [Makefile:487: 
image-trees] Error 2
2023-04-24 03:07:41 ERROR build/debian-cd exited with code 2, full log can be 
found in ./cdd/tmp/log/build-debian-cd

If I downgrade to debian-cdi 3.1.36, the build (a bullseye image) process
succeeds. The related build profile exports NONFREE, NONFREE_COMPONENTS, and
FORCE_FIRMWARE, and requires several firmware packages.

This might be worth fixing for Bookworm.

Regards, Daniel


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

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

Versions of packages simple-cdd depends on:
ii  dctrl-tools 2.24-3+b1
ii  debian-cd   3.1.36
ii  lsb-release 12.0-1
ii  python3 3.11.2-1+b1
ii  python3-simple-cdd  0.6.9
ii  reprepro5.3.1-1
ii  rsync   3.2.7-1
ii  wget1.21.3-1+b2

Versions of packages simple-cdd recommends:
ii  dose-distcheck  7.0.0-1+b2

Versions of packages simple-cdd suggests:
ii  qemu-system-x86 [qemu-kvm]  1:7.2+dfsg-5

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmRF2OAACgkQS80FZ8KW
0F2Awg/8DIJ4G7pr3rWCRbp+AZwtvJxPB459QjSR8fJ7FeRBA8OBcHtlhCzAtiHF
tQjjQRGyepbte2l0lpVVXEgzF5RWmovuHJ8T/QZWWd86MsBL0NSCt4vszCWhZ5pb
oQin7j+evt4gKx6noUQfQWgPfiwEwCSb6XBkvVv/oq2VY3mPl6AjbQIGd87NwjuV
ZtoyO+ywxW8LloI/AgA7iirStfu0xG28DCflzJZMnvJh4Ejj4RfxgkdvyAVn78PX
jlTPtaiUnC6E/XH9S0sGEK8uX6/eamOFoqPfjNWwxXtQ0mAUucvn7HiqGg+0K+aV
Up9gznKC3UP4FQMDjDl2C875IDVIeLaTrWN43KJQ+DH2okTmzM2lbusNw76n1eXg
oBJj+tjGsgtprJBw4YncR2fijS3MaSbotyY10H3jFTol91NxLx6Q5sXBi+RDgpm6
VvAAdHDNdy6i5idOfRUiGOpqk74WRMYxU3eFvWqARnHEcSv/iTHxXIeUdRONqbrX
atFcIEIpjNwPyxySsxHzaKO/wSkcfquUflNG0adQ4wcuf1jOY/HrrpS9SotP5WDR
uTnrRDS42V/K5ggpvB6Qozp1/zawch0dtd7+KRQWg3luiFNdDvjlJayBd+PFlQKb
qcWppktTZdQVOAkZTuGK9Xacd6flt8e8VeKW3jtUn/7PBRvRU8Y=
=59sG
-END PGP SIGNATURE-

Bug#1029588: bts: Changes in libio-socket-ssl-perl 2.078 make bts fail to send mail to mail-server via SSL/TLS - hostname verification failed

[Daniel Leidert]

Hi,

Am Mittwoch, dem 29.03.2023 um 18:42 +0200 schrieb Dominique Dumont:
> 
> Turns out that Perl module Net::SMTP supports SSL since 2014 [1], but
> bts still use Net::SMTPS which is an old wrapper around Net::SMTP.
> 
> I've patched bts to use Net::SMTP instead of Net::STMPS and I can
> connect to Daniel's server:

I'm really sorry for not getting back earlier. I was just too busy.


I'll test the updated package asap.

Thank you so much for working on this.

Regards, Daniel

Bug#1031441: Potential RM candidate ?

[Daniel Leidert]

Am Mittwoch, dem 15.03.2023 um 21:19 +0530 schrieb Pirate Praveen:
> On Mon, 13 Mar 2023 23:17:02 +0530 Mohd Bilal  
> wrote:
>  > Hello,
>  >
>  > The upstream[1] for ruby-github-api has been inactive for over 2 years
>  > now and this is affecting other packages like ruby-oauth2[2] and
>  > ruby-faraday[3] from migrating.
>  >
>  > $ reverse-depends -b ruby-github-api
>  > Reverse-Build-Depends
>  > * ruby-jeweler
>  >
>  > $ reverse-depends -b ruby-jeweler
>  > No reverse dependencies found
>  >
>  > So should we remove these 2 packages ? or as a workaround we could relax
>  > the versions in Gemfile to actually fix this bug since the Debian source
>  > doesn't ship the upstream test suite.
> 
> I think we can remove these two packages.

I agree. Without migrating github-api to oauth2, IMHO/AFAIR it is also
dysfunctional right now.

JFTR: The upstream author is still very much active on github, just not
working on that gem, it seems.

Regards, Daniel

Bug#1032363: Using ansible is broken: ERROR: Ansible requires the locale encoding to be UTF-8; Detected None.

[Daniel Leidert]

Package: vmdb2
Version: 0.26-2
Severity: important
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

I recently started to receive errors when building images using the ansible
directive:

DEBUG STDERR: ERROR: Ansible requires the locale encoding to be UTF-8; Detected 
None.

There is a check in /usr/lib/python3/dist-packages/ansible/cli/__init__.py in
initialize_locale() to ensure that the locale is an UTF-8 locale. However, the
vmdb2 ansible plugin runs ansible-playbook via vmdb.runcmd() and this sets
LC_ALL to "C", thus the ansible test is failing.

Unfortunately, there is no way for the user to override this. The quick and
easy solution would be to set:

env["LC_ALL"] = "C.UTF-8"

in vmdb/runcmd.py in runcmd().

Please consider fixing this for Bookworm, otherwise using ansible will be 
broken.

Regards, Daniel

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

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

Versions of packages vmdb2 depends on:
ii  cmdtest 0.32.14.gcdfe14e-5
ii  debootstrap 1.0.128+nmu2
hi  e2fsprogs   1.46.6-1
ii  kpartx  0.9.4-3
ii  parted  3.5-3
ii  python3 3.11.2-1
ii  python3-jinja2  3.1.2-1
ii  python3-yaml6.0-3+b2
ii  qemu-utils  1:7.2+dfsg-4

Versions of packages vmdb2 recommends:
ii  ansible   7.3.0+dfsg-1
ii  dosfstools4.2-1
ii  qemu-user-static  1:7.2+dfsg-4

vmdb2 suggests no packages.

- -- no debconf information

- -- debsums errors found:
debsums: changed file /usr/lib/python3/dist-packages/vmdb/runcmd.py (from vmdb2 
package)

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmQD/o4ACgkQS80FZ8KW
0F1aoBAA2WFaRlX6pW+BNWTx+sc5MPnIh4rrK6yvWpwX0Mb0IDfFnSezlz64HHaj
MHT8mI7mdD2wpEuHyUF6jxD/7IzAIyd4L3yaUV2d7pYjL3IDfeLa6GqKRYhthfiF
UtSLuy2Q4kUnfllWxOC7Y3BUd5sAVcw/L+dwoEQKwjz0XAHLPMq1A9gHvZlt5pcX
g03dvIimobNzeELvOY4Caa2CpfVxIRkVIaSz/s99qE9p0jPgD8LDhg4oJfF3migv
VTCb6k3g/bHgyuUI0h8GWEre4J/B+H7DPfVFb3p+av5p3fI1PhgsD6Tk+U5m7OJm
nR+R0zmCTnzT5YxS45TLeSFJJ5Yq34ae6jKASup3s6UIVM288ALDgSNm18+akjdo
E50hwBH2mMGkKfqcg15MkNOc3XWJFGT9g4ymXP/lmwnucHcPIvqfl8Bjy5m0RPfg
Z3F4BwkmE83NcF6v7L1MK/YogjeRC7EO85Xsb1puuUBER2ripIj6d2c7HzpEHuAr
PqxSTIhVjBFDItINnNqY6Cd6PBbcfxkUGIBbKUEOSOJTVTIBC+baj76JzrhR92G7
rCNgQNVk+FOm4Ysau4/Qawnex0xivNvnqQUt5RR5vxv0msokoXGWI9ZUCCqGhCKc
63mspc20+PP2xvLsGjQ34ye5JnrWgjhrGIp6UQhNksPqTxPke4M=
=ZE4q
-END PGP SIGNATURE-

Bug#1032221: cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work

[Daniel Leidert]

Booting an older kernel/initrd and then downgrading libargon2-1 to the
version in Testing and updating the initrd resolves the situation for
now. Thanks to Kai and Guilhem.

Regards, Daniel


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

Bug#1031548: FTBFS with ruby-jekyll-github-metadata 2.15.0

[Daniel Leidert]

Am Sonntag, dem 26.02.2023 um 16:57 +0200 schrieb Adrian Bunk:
> On Sun, Feb 26, 2023 at 03:47:49PM +0100, Daniel Leidert wrote:
> > Am Samstag, dem 25.02.2023 um 16:15 +0200 schrieb Adrian Bunk:
> > 
> > [..]
> > > FYI:
> > > 
> > > The package in bookworm builds with jekyll-github-metadata
> > > 2.15.0:
> > > https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/ruby-jekyll-remote-theme.html
> > > (the buildinfo link has the complete package list)
> > 
> > That is due to this environments not running the failing test. The
> > test-file checks if there is an internet connection and adds or
> > removes
> > tests depending on the outcome). The test in question is one that
> > requires an internet connection.
> > ...
> 
> Accessing the internet during the build is an RC bug.

It would be pretty stupid to generally disable tests for a *remote
theme* plugin (or any other package) that by defition relies on the
internet. This would disable the majority of tests here. We (as in "the
Ruby team") instead handle the tests if there is no internet, and
whenever possible, run them via autopkgtest (needs-internet
restriction) at least.

IMHO this is a valid approach and in this case spotted a regression. To
my understanding, builds must not fail due to access attempts and the
build itself must not rely on downloaded resources. However, this is
the test stage, not the build stage. But if you feel that strongly
about that, please show me the exact ruling. It won't change the fact
though, that this package will fail autopkgtest anyway due to a
regression.


Daniel

Bug#1031548: FTBFS with ruby-jekyll-github-metadata 2.15.0

[Daniel Leidert]

Am Samstag, dem 25.02.2023 um 16:15 +0200 schrieb Adrian Bunk:

[..]
> FYI:
> 
> The package in bookworm builds with jekyll-github-metadata 2.15.0:
> https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/ruby-jekyll-remote-theme.html
> (the buildinfo link has the complete package list)

That is due to this environments not running the failing test. The
test-file checks if there is an internet connection and adds or removes
tests depending on the outcome). The test in question is one that
requires an internet connection.

The package currently doesn't build in a Bookworm nor a Sid chroot if
the test in question is running. I can also reproduce the issue in a
chrooot with a Ruby-only environment. It has already been forwarded to
upstream, and I might simply revert the commit in jekyll-github-
metadata 2.15.0 that is causing this regression, or disable this one
test for now.


Regards, Daniel


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

Bug#1031548: FTBFS with ruby-jekyll-github-metadata 2.15.0

[Daniel Leidert]

Source: ruby-jekyll-remote-theme
Version: 0.4.3-3
Severity: serious
Forwarded: 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The package fails to build right now with jekyll-github-metadata 2.15.0. The
culprit seems to be

https://github.com/jekyll/github-metadata/commit/a771d0d7457a7bff42b129ce0bed70c74514a506

The issue has been forwarded to

https://github.com/benbalter/jekyll-remote-theme/issues/98

Regards, Daniel

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

Kernel: Linux 6.1.0-4-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPwtkgACgkQS80FZ8KW
0F2IUg//R+DwQrb/S78zLPMtd3eL/6Xl7rF0lrubOnakzRhWj0zykVxzQq1iFgX0
6BrTARWOK2XDTZOTWB4+4FhPuhZd1SPiyC6XDg/PSBCZb+blyyhG/zY7X7p9faPm
GbWSq6QIo470HEVwC4E5crDdIWEG4ApLocEX2A7+GbJeb0tbXGxI0A6HrkxnILJr
5aqds/+5D842QU0Tro+otAeMvM+jPffk6vY8tgRDzxGf8X8HU4oBYQeoPeoczrc9
fr4M6yrGKZ3gPleLHijktUsza8yUFaQKZwTalbesQfxfAdwKdLKS05Uv+wQPz3w8
79Z09ZLK4b1XqU4njQYPRWrr8WOFGqzkWaF0g2qGlwdZXQv3bcWhug6PGoP+A2/M
ehYGjry1kldPzXBhRZKFAJsk90zcQbmmqlZ6uiwMa8gtoQhX5JEMebPJ+iFk+PSt
U3aKQSXdsp2ey6jAwjkuOf+OWfTB+YVVvzwKs6hecdM7DkSye3Qh9Dw4GyYg7lh+
KxyKJf4NSdmkaOIBYdOBwtYdIId4krg+um5nJSfE9D8xOafvGbkvsialfz2WBOuv
+3CQQbuVcYYOrY3NM9gRT5cvem+kals67n9gITsr87QXH10s3tbijTvpl2vf5fZk
bid9XIIpQMIOfo1QryLqbRCj4r/Y083p9YSULQvjyN40OIxTaGc=
=woiX
-END PGP SIGNATURE-

Bug#1031441: Relax oauth2 dependency

[Daniel Leidert]

I just rebuilt ruby-github-api by relaxing the dependency on oauth2. I
pulled the test cases from github to check if anything happens. It
built just fine. 6 tests failed, but none related to OAuth2 (seems some
keywords/options mismatch).

I think we could fix this by relaxing the dep on oauth2 for now.

There is an upstream report asking for supporting oauth2 2.x at
https://github.com/piotrmurach/github/issues/386.

Regards, Daniel

Bug#1031457: Unreproducible

[Daniel Leidert]

Hi,

I cannot reproduce the issue. Buildd and autopkgtest also don't
indicate any problem. I guess that is a one-off (maybe redis didn't
start for some reason?)

Regards, Daniel


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

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Daniel Leidert]

Am Donnerstag, dem 16.02.2023 um 20:10 +0200 schrieb Adrian Bunk:

[..]
> I am currently spending time trying to summarize the situation and open
> questions, and I am a bit underwhelmed by the inaccuracies and lack of
> technical detail in your emails.

Well, I didn't have weeks to prepare. I had <24 hours and gave you
already enough information so you did not have to start from scratch.

I will summarize my points at the bottom.

> The instructions you cite in [1] are for installing bullseye from
> non-Debian systems.

That is simply not true. Those are general instructions, they are not
limited to non-Debian systems. Most server providers have exctly *one*
rescue system from where I can do a clean installation with deboostrap
(and that even usually is a Debian). I cannot choose to use one that
hasn't an e2fsprogs that has this breaking change enabled. Say for
example, grml, used by multiple providers I know as rescue system and
based on Debian, picks up Bookworm with e2fsprogs with that change. Now
users trying to install anything other than a Debian Bookworm using the
deboostrap method will run into the situation that "grub-install" will
fail, and it won't even indicate that they will have to tune the just
created ext4 filesystem or even change /etc/mke2fs.conf. I spent a few
hours until I tracked it down. And the situation right now is, that I
can simply install any system with the deboostrap method. I'm not aware
that there are any breakages or incompatibilities.

> What bookworm ships does not matter much there,
> these instructions will be wrong as soon as some *other* distribution
> like Fedora changes the default.

Fedora isn't used much as a rescue system, don't you think? Have you
ever encountered that? I do custom server setups with deboostrap for
almost two decades now. I haven't seen any distribution so far that
changed the created filesystem to be incomatible with grub-install from
the systems that might be installed. Most of the rescue systems were
Debian based, JFTR.

> I am wondering how exactly your often repeated "there is no grub 
> upstream release with support for it" would be relevant in practice.
> Whether it's 2.06-8 or 2.07-1 in bookworm shouldn't make a difference.

You completely miss the point here. It would lead to exactly the same
situation if 2.07 would be the *first* to support it and could be
shipped with Bookworm as long as e2fsprogs makes this breaking change
now. But it makes a huge difference if 2.07 with a fix is released in
around the same time as Bookworm and can spread until Trixie is
prepared and the breaking change is postponed to Trixie. Ubuntu 24
would have picked up that fix by then. 22 and maybe even 20 would
probably have picked it up either. Even bullseye could get a patch to
deal with that. The breakage would have less impact than it has now,
while nothing is prepared.

And it is completely illusional to say that people should first create
a Bullseye chroot to then do a deboostrap setup of a target system from
that chroot, as Theodore suggested. Well, I'm more than underwhlemed by
suggestions like this.

> Sebastian has now created #1031364 for your original vmdb2 problem, 
> everyone discussing in #1030939 seems to have missed that tools in 
> bookworm creating images for < bookworm must handle such changes.
> That's not different from debootstrap having code to handle 
> apt-transport-https being required in some older releases.

I agree. So don't you think introducing this now is a really bad
timing?

I checked a search engine to find out what this feature even does.
Turns out, there were less than 500 hits. It is a feature available
since kernel 4.4 and not widely used nor default. So what is the gain
here? I also tried to understand why our users would need to be able to
change the UUID of the filesystem. In 20 years with Debian, I haven't
encountered a situation where this has been necessary (I didn't even
know that one could). My gut feeling is, that this feature is only
useful to a handful of people. I haven't heard any explanation so far
why this needs to be turned on by default just now. The whole
discussion so far has been Theodore argueing why he doesn't care about
his actions and why he doesn't have to.

If this feature should be turned on, then I still think that doing this
for Trixie is the better choice. The tools affected can be fixed to
work around the issue. The other distributions can pick up the grub-
install fix.

And JFTR: The attitude I preceived since I got into the discussion with
the simple sentence that fixing grub in Bookworm might not be enough,
can be summarized as "I/we don't care". So, sorry, I care, even if my
less excellent mails might be underwhelming for you.

Daniel

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Daniel Leidert]

Am Donnerstag, dem 16.02.2023 um 18:37 +0200 schrieb Adrian Bunk:
> On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote:
> > ...
> > Reasons:
> > ...
> > - - the change makes it impossible to create filesystems with this version 
> > of
> >   e2fsprogs and then run a grub-install from a target system that does not 
> > cope
> >   with that feature; basically breaking the debootstrap method of installing
> >   Debian or Ubuntu onto a server (violating #4 of the Debian social 
> > contract)
> > ...
> > Instead, turning on this feature should be postponed for the next release 
> > cycle
> > where a proper transition can be done.
> > ...
> 
> Daniel, you are contradicting yourself when claiming that a change that 
> would allegedly violate the Debian social contract could be done in the 
> next release cycle.

Actually, I'm not. I have never said that I reject the introduction of
that change. But I reject it in the current situation, and I reject the
way it is handled. And if you read the whole report and the discussion
I was involved in, then maybe you can understand that I perceive it
that both, Steve and Theodore, were very well with the idea of breaking
with Bullseye and Ubuntu and other systems, where grub doesn't support
that feature, right now and "just like that". And I think this is a
violation of #4. I have also written in [1] how I think the transition
should be handled (IMO), especially given the fact that grub has no
upstream release with a fix yet.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030939#108

Regards, Daniel

Bug#1031395: tzdata 2022g-3 removes /etc/timezone while other packages depend on it, breaking these packages

[Daniel Leidert]

Package: tzdata
Version: 2022g-3
Severity: critical

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

in version 2022g-3, the /etc/timezone file has been removed and gets purged
from user's computers. This makes unrelated software break that relies on this
file. Examples are samizdat and ruby-et-orbi. But codesearch.d.o shows more
code-snippets that rely on the existence of that file. There hasn't been any
announcement, any transition, nor any mass-bug filing, leaving multiple
packages broken at this stage. I reported that issue to the release team as
#1031376 and have been asked to open a bug report against tzdata.

Regards, Daniel

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

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

Versions of packages tzdata depends on:
ii  debconf [debconf-2.0]  1.5.82

tzdata recommends no packages.

tzdata suggests no packages.

- -- debconf information excluded

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPuJ/gACgkQS80FZ8KW
0F2CPQ/+M+A8ok4famSAdTA6Tpjw+ydaYGO2E4+NoQy/diq8KKhFMiOOdduiQji4
6J8no1J7K00eEPgqBko3lQXDJByDuRKHWXD3NFmQJme/pL9Wf4yc7+Zx4QhaBI96
UuUV4M8khv89bA9Bb6TWGUD0OkEOgpze7HAZAQqc8gnaGA2yRkh3JC9DmHe9boQJ
ywODuoFmlPIgyv+Jx8KlXgGdZWWoJpQtm8ol21WeYRtAWxPL+b/FbC1rTrSSEgka
wmw+pa4VbKC8sQIyGQPbJJk0q3PTIqKu1ia59KGKSrCox4cfAvV3EccgyH1xYliI
BRrlSEG1mau1O8jz4fq7oqMVs6W/KMRuj+pSI4n5DEFU9tEJ2G3trysusnS531tj
L++pD/aWISx76rpVzizVQjw1J63pr9sK8sh9/s/jz4s3Ddwiij/HVMaA6t7X+2DU
I3O8jgUq4N6taWw7NcBLDSyFRESqc0BcZYwfsvD7DD0UHSUeZmE5PnetHVWLwqeg
O/ljWDNuIiB61DfVWJr5nfhKXOZYFWXJEOOwDQ5zxWviHlahEGsu3wOQLGW7OA9E
bKUO2IpAOMHX0Oxx752t9eParFqs2yfAX338PGC73w7dCIB5bVowD9SHRCJi6FRX
8HhD5hgq8SsuJEej0eBS63QqN3uqxZKbZsoQgA5aS3eMffxEPRM=
=i0wy
-END PGP SIGNATURE-

Bug#1031376: tzdata 2022g-3 removed /etc/timezone without a proper transition, breaking multiple packages

[Daniel Leidert]

Am Donnerstag, dem 16.02.2023 um 08:41 +0100 schrieb Paul Gevers:
> Control: tags -1 moreinfo
> Control: severity -1 normal
> 
> Hi Daniel,
> 
> On 16-02-2023 01:11, Daniel Leidert wrote:
> > I ask you to
> > find a reasonable approach to deal with this for the Bookworm
> > release.
> 
> That's not how we normally work. Please come with concrete proposals and 
> we can evaluate them.

Hi Paul. That is the release team's job. Your team should be on top of
that situation and control that. There is already a freeze in process.
You made that very clear. New transitions are not allowed. The date has
passed that re-introductions into Testing are not allowed anymore. And
people break other packages just like that? It is my expectation that
your team evaluates the situation together with the maintainer of
tzdata now, and then comes to a conclusion and a decision, how this
should be handled. codesearch.d.o proves that multiple packages use
code that relies on the existence of /etc/timezone. So, its removal
should have been handled in a coordinated way in the first place.
Either the maintainer of tzdata does a mass-bug filing, or this change
should be reverted.

I have already spent two dozen unpaid hours of tracking down and
handling breakages introduced since February 7th(!!) by fellow DDs. I
spent multiple dozen hours of bug-fixing and uploading since the new
year started, to make sure users will get the software they expect in
Bookworm, also unpaid of course. And now I have to evaluate the impact
of the change in tzdata as well and create proposals? No. I'm not the
tzdata maintainer and I'm not a member of the release team. It is your
job to handle transitions.


And I suggest that you finally do your job and make sure that people
stop uploading breaking changes, so the work for Bookworm gets less and
not constantly more.


Daniel

Bug#1031376: tzdata 2022g-3 removed /etc/timezone without a proper transition, breaking multiple packages

[Daniel Leidert]

Package: release.debian.org
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

A recent upload of tzdata [1] removes the file /etc/timezone from user's
computers. This broke multiple packages of the ruby-team (samizdat and
ruby-et-orbi being two of them). A quick search on codesearch.d.o [2] for the
usage of the file reveals more packages that are likely affected. While the
change itself is not unreasnable, it has a bad timing, and since it went
unannounced, multiple package require fixing now for Bookworm. I ask you to
find a reasonable approach to deal with this for the Bookworm release.

[1] 
https://tracker.debian.org/news/1418475/accepted-tzdata-2022g-3-source-into-unstable/
[2] https://codesearch.debian.net/search?q=%2Fetc%2Ftimezone=1

Regards, Daniel

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPtdMMACgkQS80FZ8KW
0F11txAAxzQK/ackamzXJT8RChyY+EurntwQaMCuS6GzgVV/cdHEklSUzT51XAWk
Su4C3umDtcjmBQgMNqP94umV/Xp32zHJboVxC1RDmjxcK0CoWlgVNiCtNOO7K/sm
3t+oIMlsIsFbjxsJaCKuW1Q7Ob+ebJ9cEUI7y59zt0hWKxtgeqBeDbrgyuwguW/y
THigG9PnF4ObosO8HV8EgvdREl5GjynYALLlEv1quWX9lc6JKgt8uTW8+txjsE0o
jRiz7iXxHZdPwnVV10WFZM3MXO5Nbibe0YDd4lRIqBC58owE8KmeDv3eDpdl5vyA
CLBDlFUyq5gysgpte7veN0OMUh0HCL5akFc1EBda6xwI5+PqehQoULaTKvmSZ25A
HcY15c6eLJ+qPVYWZC7XFsnYH9ETOtRhkiuKEOxuVsKq+dwgaX1PYQiSo/OHqmXF
cOQQ7R0Mwc6CNnDVVbFHerUdS8Ur42MRm7OkaFfoBP/qkIBjjNBxlMgmkuV0GZw6
pLkTltK+ITooSXBh4307uo0qybq6QesE81NEbMGAB94yTSi1YIn0yXikd1JT2PYR
tdvxn9z1X6ssmAUSiy9y9q6wFqv/GTTGSXe33ieRGah11OD+oP1GcLx5ESo7W9Cz
IhHCX0nQxdS1EQbSnl6ZkM4ephqZ/41P4z+2MQLoHAJyBNNyMSo=
=ASWO
-END PGP SIGNATURE-

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Dienstag, dem 14.02.2023 um 16:53 -0500 schrieb Theodore Ts'o:

[snip]

Your arrogant and ignorant attitude is frustrating, to say the least.
You don't care about the mess you create, for a feature, that probably
only a handful of people will ever need (I did a quick search and
didn't find anything regarding this feature - so why turn it on by
default then?). But yet you have to make it the default and break
running toolchains and methods. Talking to you is pointless. You cost
me hours of useless work yesterday and today because you ignore the
rules we have set out as a project to not frustrate each other.

I have reported this to the release team now.

Daniel

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Daniel Leidert]

Package: release.debian.org
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

A week ago, Theodore Ts'o uploaded e2fsprogs 1.47.0 into Debian unstable. This
version contains a unannounced change that basically breaks grub2 (and
grub-install). This issue has been reported as #1030939 [1] and #1030846 [2].
To "fix" the issue, instead of turning the feature off, a patch to grub2 in Sid
has been committed recently. Unfortunately, that only fixes grub in Sid. Grub
in Bullseye or any current Ubuntu release *cannot* deal with a filesystem
created by this version of e2fsprogs. This basically breaks the debootstrap
method of installing a Debian or Ubuntu. If e2fsprogs 1.47.0 is allowed into
Testing, we can no longer use the debootstrap method to install a Debian
Bullseye (or older) or any Ubuntu release. It requires to manually change the
filesystem features before it can be used again. It also makes e.g. vmdb2 in
Sid unusable to create images of Bullseye or older Debian releases, or Ubuntu
releases.

The gain of enabling the metadata_csum_seed feature by default is not
noteworthy. It is a feature that hardly anybody needs. I have not seen one
use-case nor even relevant search hits. But the loss is heavy. User's can no
longer simply follow [3] to install any Debian or Ubuntu system if the
filesystem has been created with e2fsprogs 1.47.0. It also breaks software in
the midst of the freeze.

I hereby ask the release team to step in and either make sure that the
metadata_csum_seed feature is not turned on by default in e2fsprogs in Bookworm
or that version 1.47.0 is not shipped as part of Bookworm.

Reasons:

- - this breaks existing tools for no apparant reason

- - introducing this breaking change is too late in the release cycle to deal
  with it properly

- - the metadata_csum_seed feature is hardly useful or requested; it can be
  turned on if necessary; no need to make it the default in Bookworm

- - there is no grub upstream release with support for it; only patched grub
  versions can cope with it

- - the change makes it impossible to create filesystems with this version of
  e2fsprogs and then run a grub-install from a target system that does not cope
  with that feature; basically breaking the debootstrap method of installing
  Debian or Ubuntu onto a server (violating #4 of the Debian social contract)

- - to cope with the former issues, users will have to know about that
  incompatibility and ways to deal with it; none of that is prepared; the
  package maintainer even refuses a NEWS entry

- - it breaks vmdb2, only allowing to make images of Debian Bookworm and Sid (if
  grub is involved)

- - pushing this metadata_csum_seed feature violates #4 of the Debian social
  contract

Instead, turning on this feature should be postponed for the next release cycle
where a proper transition can be done.

[1] https://bugs.debian.org/1030939
[2] https://bugs.debian.org/1030846
[3] https://www.debian.org/releases/stable/amd64/apds03

Daniel Leidert

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPsE8UACgkQS80FZ8KW
0F0Aug/+Kb6xrQcILq+VYpKk/161UXgQA47ccydz78uT3r1eRBVJIPReULZPdjvk
W4PDDOYypScsx4+EahdOVViAMiOyzI0eroivZmDItxY1HR6LpKdeQFPLET6FdbfM
pDHezFKXqsulYQWLu5M6yPCtMWGCmAtiH9NeppzUY7+dnBr2yzZGitH4pPSh7MmS
9jxRIKG0xGa3wF+a1yEgHE0nPvqD5a97GlwL5+MTg580k/e1VRpaQaYrTRr3CHyK
EJbVOu70K+qXgP837x6B5eyYmihJWiNBMxm9JqF1TrwTKXwk26zpZ2+T1uKVgVKj
Y5AlZX8Gypdxq0Q3uFPSlzBhetd2wvrUt9hKEb52fdzw3L4AsY2Ken98sAhqy7Xi
PGVdihiUSAT5gslthm3qB3fGQQMIEXI3UdHqSx7ARgZJ6Gkf/zIjk5sKl/xiGe+t
jJExPdCR7H8+tPNZhJEhx6BLtLs8tLm+zhOAr3rZVekEn3PJJAHOKPs1KPBWinYr
FsVBsWBWzOgKNARu31u/o4s5BFV99M45gZqHLs3Mp5TvJqIxkbwS0FDoCa/TausP
vojuW4kDPM7Jjw568W4O8csXBiI/qEcEPXZGPrgGVs3Yo1hV/KkJUOkQ9y/VvRps
POx+RwF400ov8zOxGPqETkqDjl/2JQ47OOvogJMi6FDRQk+YE2w=
=bKh7
-END PGP SIGNATURE-

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Dienstag, dem 14.02.2023 um 12:34 -0500 schrieb Theodore Ts'o:
> 
[..]
> In any case, a version of grub that will support the csum_seed feature
> will be landing in Bookworm in just a few days.  So at that point,
> you'll be able to create VM images for Bookworm and Sid that will work
> with the e2fsprogs in sid.  The current plan of record is that it will
> only be at that point that e2fsprogs will be allowed to migrate into
> Bookworm.

As soon as this version hits testing, you have successfully disabled
the last working environment to use vmdb2 to create images of Ubuntu
and Debian. As soon as this version hits Testing, one then can no
longer build images for either any Ubuntu release nor Debian Bullseye
or older. I can then only build images for Bookworm and Sid. Please
think about that.

You *seriously* break the debootstrap method of installing Debian or
Ubuntu. vmdb2 ist just another tool that is broken by now, a tool that
I use very often. I explained the impacts of what you are doing often
enough now. By now the impact should be clear. And you are still not
dealing with the aftermath of your intended action?! You haven't done a
proper transition. You haven't given any affected toolchain the
necessary time to adopt. You haven't documented how to disable that
breaking change when creating filesystems for distributions where grub
does not support this (there is not even a NEWS entry). You haven't
even announced that breaking change. And yet you are going to break one
of our two standard methods of installing Debian or Ubuntu. How is any
of what you have been saying so far addressing any of these issues? 

> [..]
> By the way, in the case of the csum_seed feature, it's pretty
> straightforward to just run "tune2fs -O ^metadata_csum_seed
> /tmp/boot.img".  If the UUID has been changed since the file system
> was created, you'll have to do this while the file system is
> unmounted
> and it will take a few seconds, but that's almost certainly not the
> case with vmdb2.

Well, how do you intend to distribute that information, so people who
have to use the deboostrap method to install a Debian or Ubuntu release
with a grub not supporting csum_seed (basically all existing releases,
except for the upcoming Bookworm) know that?

I do not understand why you are pushing 1.47.0 over 1.46.6, which you
had uploaded just five days before the former. You haven't even
presented a reason yet.

Regards, Daniel

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Dienstag, dem 14.02.2023 um 14:58 + schrieb Steve McIntyre:
> On Tue, Feb 14, 2023 at 12:50:18PM +0100, Daniel Leidert wrote:
> 
> 
[..]
> Breakages happen like this,

This breakage is *unnecessary* and it breaks at the momnent *all*
debootstrap installations except for doing a bookworm/sid installation
themselves. That is just stupid.

Get down from your high horse and ackknowledge the problems your
behavior causes.

> and this has happened before in similar
> circumstances.

No it has not. You are doing a breakage on purpose during a freeze
period while the transition period is over. Do it with a proper
transition during the next release cycle.


> > 
[..]
> > Whe whole handling is completely wrong here. First, grub should have
> > been fixed upstream. And the change in e2fsprogs should have been done
> > only after "fixed" grub versions had settled. If we do it the other way
> > around, we have to patch grub in affected distributions as well. And
> > for Debian that means at least to patch Bullseye and any other release
> > we want to be able to install from Bookworm. I even a lot of companies
> > using Buster still.
> 
> And I know of folks still working on Stretch and Jessie. How far back
> do you want to tie things??

How about staying on topic and explaining, why this transition is
necessary and has to be done the wrong way around, instead of picking
the fact that older systems still exist? You break almost *all*
installation right now. You also broke an Ubuntu 20.04 or 22.04 LTS
installation. Are they new enough?

[..]
> > 
> > I'm critizicing the way of handling that breaking change and the
> > ignorance shown reagarding the impact, not that fact that there is a
> > breaking change. And it breaks a lot! This doesn't affect just a few
> > minor use cases. It affects the basic way of installing a clean Ubuntu
> > or Debian (or derivative) on a remote server using the debootstrap
> > method.
> 
> People using these tools need to be aware of the potential issue. What
> would happen if you ran debootstrap with a filesystem that the target
> distro doesn't know how to mount at all, for example?

That is different from introducing a breaking change for which no grub
upstream release has a fix yet. So basically the only system able to
handle a filesystem created with e2fsprogs 1.47.0 is Sid right now. Can
you please ignore your ego and see the problems you are causing?

You push a breaking change for no reason at all. What is the gain here
compared to the issues you are causing?

> > And again: We are in the middle of a freeze here. And e2fsprogs
> > pushes
> > a breaking change that is not even handled by any existing grub
> > upstream release, and is also not properly handled within Debian?!
> 
> Grub upstream is already known to be problematic in terms of release
> cycles.

That is not enough and it is not a solution for the problem. There is
*no* grub version out there supporting this, except for the patched
version is Sid. Is this the sign for a working transition?

> We now know about this particular issue (thanks Ted!) and
> we've fixed it in unstable (and soon testing).

Which helps exactly nobody, as it still breaks all other Debian or
Ubuntu installation.

I cannot belive that you intentionally break one of the standard
methods to install Debian or Ubuntu for no reason at all and without a
proper transition. Version 1.47.0 of e2fsprogs contains nothing
necessary for Bookworm. I'll bring this to the attention of the release
team. I'm sick of your ignorance. Do a proper transition and don't
start it during a freeze.


Daniel

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Dienstag, dem 14.02.2023 um 10:45 + schrieb Steve McIntyre:
> On Tue, Feb 14, 2023 at 11:34:13AM +0100, Daniel Leidert wrote:
> > Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o:
> 
> ...
> 
> > > But a generalized requirement that we be able to use debootstrap and
> > > vmdb2 to be able to bootstrap an arbitrarily old distribution doesn't
> > > seem to be reasonable.
> > 
> > You are completyl wrong. This breaks a standard way of installing any
> > system supported by deboostrap with a grub without a fix to deal with
> > this version of e2fsprogs. This isn't just about vmdb2.
> > 
> > What you are saying is ignorant.
> > 
> > If this isn't cared about, then this version of e2fsprogs shouldn't
> > make it into Bookworm. We are in the middle of a freeze and this breaks
> > toolchains and a standard way (see [1]) of installing Debian.
> 
> Sorry Daniel, but I have to (mostly!) agree with Ted here. If you're
> creating an image of an older release using newer tools then you'll
> need to be aware that sometimes the newer tools will create things
> that don't work there. If there's a bug here, I would strongly argue
> that it's in vmdb2. deboostrap (for example) includes some
> release-specific knowledge to cope with issues like this.

debootstrap does nothing related to grub. So it is a bad example. Again
I refer to [1]: If the host system contains the problematic e2fsprogs
and the target system doesn't contain a grub with the fix [2], then
this breaks installations. This breaks older systems *and* current
systems. For example, I neither see the necessary grub patch in both
Ubuntu 20.04 and 22.04 either. So they also cannot be installed using
the deboostrap method and the toolchain in Sid (and Bookworm if
e2fsprogs makes it there). 

[1] https://www.debian.org/releases/stable/amd64/apds03
[2] Even "our" grub only contains a patch and not an upstream version
with support. So how can you even expect the target system to contain a
fix and be able to handle the created filesystem?!

Whe whole handling is completely wrong here. First, grub should have
been fixed upstream. And the change in e2fsprogs should have been done
only after "fixed" grub versions had settled. If we do it the other way
around, we have to patch grub in affected distributions as well. And
for Debian that means at least to patch Bullseye and any other release
we want to be able to install from Bookworm. I even a lot of companies
using Buster still.

> If we don't allow for this kind of change, that wouldn't allow us to
> *ever* make breaking changes in some packages, and that's just not
> sustainable.

I'm critizicing the way of handling that breaking change and the
ignorance shown reagarding the impact, not that fact that there is a
breaking change. And it breaks a lot! This doesn't affect just a few
minor use cases. It affects the basic way of installing a clean Ubuntu
or Debian (or derivative) on a remote server using the debootstrap
method.


And again: We are in the middle of a freeze here. And e2fsprogs pushes
a breaking change that is not even handled by any existing grub
upstream release, and is also not properly handled within Debian?!

Daniel

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o:
> On Tue, Feb 14, 2023 at 01:01:38AM +0100, Daniel Leidert wrote:
> > Hi Steve,
> > 
> > I believe that your fix to grub2 in Sid is not enough to handle
> > #1030939/#1030846.
> > 
> > This problem breaks e.g. vmdb2. I can no longer create a Bullseye
> > system image with vmdb2 on Sid, because the grub-install step in the
> > Bullseye chroot now fails, because the created filesystem (created with
> > e2fsprogs on Sid) cannot be recognized by grub.
> 
> I'm confused, why does using vmdb2 on *sid* involve running
> grub-install on a *bulleye* chroot?

My workstation is running Sid. I want to create an image for Bullseye
(in this case using vmdb2, but I could do it manually as well). First,
one creates the paritioning and the filesystems for the target system
with the tools provided by the host system. This involves running the
unfortunate version of e2fsprogs with the breaking change. Then, one
installs the base system with deboostrap (also from the host system)
into the created partitions/filesystem. Then one (bind-)mounts the
virtual filesystems into the target systems, does a chroot into it, and
then one finishes the installation inside the chroot, including running
grub-install.

This is standard and common behavior. I have never ever seen in my
whole life someone to use grub2 from Sid to make a grub-install for a
Bullseye target. I have not even seen anybody suggest that.

Consider another example: Server providers use GRML or Bookworm with
e2fsprogs 1.47.0 as their rescue system. Now people are no longer able
to create a Bullseye system using the deboostrap method [1]. If the
host system uses e2fsprogs 1.47.0 or above and the target system for
[1] uses a grub without a fix, then this no longer works.

[1] https://www.debian.org/releases/stable/amd64/apds03

> That seems to be extremely ill-advised.

I'm sorry? I think you are completely missing the point.

> If you are trying to install a bullseye system, why
> can't you using vmdb2 on bullseye?

Because I am using Sid and because I use features of vmdb2 which are
not available in the version in Bullseye. And this feature breaks vmdb2
and similar tools. It also breaks a standard way of installing Debian
systems.

> And if you are trying to install a sid or bookworm system using vmdb2,
> why can't you (or vmdb2) use a sid or bookworm chroot for doing the
> grub-install?

What are you talking about? You basically break the toolchains and then
you suggest to do non-standard stuff to handle this or even avoid doing
installations of affected systems?!

> > I guess that the fix applied to grub2 in Sid would have to be applied
> > to grub2 in Bullseye as well (and basically to any grub2 package in any
> > Debian or Ubuntu or Raspbian release supported by debootstrap).
> 
> I can understand why we need to keep things synchronized so that a
> debian installer for Bookworm be able to generate a bootable system
> using the version of grub and e2fsprogs in Bookworm.
> 
> But a generalized requirement that we be able to use debootstrap and
> vmdb2 to be able to bootstrap an arbitrarily old distribution doesn't
> seem to be reasonable.

You are completyl wrong. This breaks a standard way of installing any
system supported by deboostrap with a grub without a fix to deal with
this version of e2fsprogs. This isn't just about vmdb2.

What you are saying is ignorant.

If this isn't cared about, then this version of e2fsprogs shouldn't
make it into Bookworm. We are in the middle of a freeze and this breaks
toolchains and a standard way (see [1]) of installing Debian.

Daniel

Bug#1030846: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Hi Steve,

I believe that your fix to grub2 in Sid is not enough to handle
#1030939/#1030846.

This problem breaks e.g. vmdb2. I can no longer create a Bullseye
system image with vmdb2 on Sid, because the grub-install step in the
Bullseye chroot now fails, because the created filesystem (created with
e2fsprogs on Sid) cannot be recognized by grub. I have to downgrade
e2fsprogs to the version in Testing to get the build going again. It
also means that a Bookworm system can never be used to format and
debootstrap a Bullseye or Buster system that requires a grub
installation.

I guess that the fix applied to grub2 in Sid would have to be applied
to grub2 in Bullseye as well (and basically to any grub2 package in any
Debian or Ubuntu or Raspbian release supported by debootstrap).

This situation is really messy. It breaks basically all my image builds
with vmdb2.

Regards, Daniel


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

Bug#1030698: Tests failing on 32bit architectures

[Daniel Leidert]

Source: ruby-riddle
Version: 2.4.2-3
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The tests fail in 32bit architectures. For more information, see
.

Regards, Daniel

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

Kernel: Linux 6.1.0-3-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPhINAACgkQS80FZ8KW
0F3qzRAAqQXcboxAuGWi/46AP95VaL4awfwzu946sPWHxxNWMKulc87IWCPm0GU4
V1m2i/EfZGusMJJMVe7Fp9jDJklycrYE9KARiI/NDWmqf5nV4OXk/13u8hW3TLdh
y4bU0oYqrFvi3YRjhNJQkLhYLN8aOxDC1rk6bF8nxQcwcidS+cKBazPmagZFbvNJ
DwtG5jGxwuzw7ANCVpiGtWeEU0ZVsl8haHefW7U4ws7OZ74Qbvy6by/t50Dnsxdc
mMvQRWZMy9xumDAJzJDoGAyo0d9o/vgO9kBon6zK36QNdHUxrzp1pZ6WH3FjKStA
3CjlRFr7JD3ABm1rsmbpODnwG4REMJy0M8/ye9I3uvarcpIvsUA3AgBIV72fnvN0
rrixFQ6tEXa7EmcxusBSTLwMyGdyzAwGJ5IyWLN+MSye6ic7eeWsbkHRKDbixy2d
EISCm0REOrKjGBwaUl2zYQ23FFQFXwh5kER9QM6o/4/AMR/PVWjtCsbWJBdpCI6L
+xAqQdDwk2NVlPu21n6dn2ITq+Ic0vTW6pulVp6C9qBqFA7meJ1p3qFbJ7zgM13D
6S62xL5zWed/8IeL5YewaR8bpy3u39jw9ScP7eYn7YxGlQ6vM33t28OKoKgVxYue
4mRFMnyB4zt/X/d8/G7W2VoGWWGkjGNEnP4hFu7gBbj9AIQvI3o=
=z4Qy
-END PGP SIGNATURE-

Bug#1024177: Cannot use jekyll-feed plugin due to incompatibility?

[Daniel Leidert]

Hi,

this issue was caused by an upload of ruby-liquid not compatible with Jekyll 3.
The latest Jekyll release has just entered Debian Sid and this problem has been
resolved. I'm going to close this report.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1029588: bts: Changes in libio-socket-ssl-perl 2.078 make bts fail to send mail to mail-server via SSL/TLS - hostname verification failed

[Daniel Leidert]

Package: devscripts
Version: 2.22.2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

I'm running a mail server. The server is using wildcard-certificates issued by
letsencrypt (but the same issue happens with a dedicated certificate). Since
the last update of libio-socket-ssl-perl, whenever I try to send mails via the
bts command, I receive the following error:

bts: failed to open SMTPS connection to smtps://mail.wgdd.de
(hostname verification failed)

Same happens if I use TLS. I checked the certificates and I cannot find any
issues. All other tools work well. If I downgrade libio-socket-ssl-perl to
version 2.077-1, everything works fine. The main change between versions 2.077
and 2.078 in libio-socket-ssl-perl is:

2.078 2022/12/11
- - revert decision from 2014 to not verify hostname by default if hostname is
  IP address but no explicit verification scheme given
  https://github.com/noxxi/p5-io-socket-ssl/issues/121

I found some hints, that Net::SMTPS, used by bts, does not support
SSL_verifycn_scheme smtp.  But this is not my expertise. I'd just like to see
bts fixed and being able to send mail to a mailserver via SSL/TLS.

Issues with SSL support in bts have come up multiple times. I remember, that I
even had to patch some code myself in the past to make it work. There are even
now patches (e.g. #853991), which might improve the situation. But like this,
bts is unusable.

Regards, Daniel



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

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

Versions of packages libio-socket-ssl-perl depends on:
ii  libnet-ssleay-perl  1.92-2+b1
ii  netbase 6.4
ii  perl5.36.0-7

Versions of packages libio-socket-ssl-perl recommends:
pn  libio-socket-ip-perl | libio-socket-inet6-perl  
ii  libnet-idn-encode-perl  2.500-3+b1
ii  libnet-libidn-perl  0.12.ds-4+b1
ii  liburi-perl 5.17-1
ii  perl-base [libsocket-perl]  5.36.0-7

Versions of packages libio-socket-ssl-perl suggests:
ii  ca-certificates  20211016

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPQmXwACgkQS80FZ8KW
0F1P+hAA1KcFh8/lqTRkrrL85H0vGbr82KNFvNRLGwqOyzL9N4vLjfIedlt+hzbU
6/YzRznl5dCzTHCwju4BYyZfrpo6NPPtfLjjwPRtajwUnbw3Q9INGACTupkTtwoC
eKCFQM2dpGODERD1zjPN16iBfoGc97pWzE3nCZpxUFZxhKTKw78tpmbr7LMnHx2j
DKXAJgejlmhtYxVLk9YKynLR0x8MoSNlYRB1T7hdoQt0lo5KnbQbEsZjlXSg9AFb
8I/T29YO9n2dA2litq4RMVONtDN9p1YyCsY+fBO8RUnLS6v+Wy+vCEhwBYPm/dQp
DajXqxmWwU94oMF3UT8NuvgGW2OCWOhbrpFaSRRnGctXoTHTzJ/D7qMza5Qakdxh
SdORO9d5LRAwFDti54zx9c62Z42wUn2P7tIIhYJpI/VcqMeVIlPw9lOzb/Xkur2e
lX2ARUbFxFuyP87pn90LNv+GIsNe6lrXfY9GXQ080RZ9lozui1YKk9bGVvLHYOVR
XGEIPSBX9FqosBA8ZQ6FrJiUZ7yC+1Cz0dToHMiGNaDSlS/naxadQCSp3ZHuHl0g
Esxq7MnnKIgzjqLx7PSgGzDNan5mnS+k0c5T6uC+6jL9z2m5czPqGLUVaAFYjwd3
X3+dsBZY34R1qZ1qzzqJutp0nZXO4NiIwSINbXVO8dcdsjTACoE=
=+f0s
-END PGP SIGNATURE-

Bug#1029225: Announced soft freeze date clashes with Ruby team's team-meeting to prepare for Bookworm

[Daniel Leidert]

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: debian-r...@lists.debian.org, terce...@debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

on December 19th, 2022, the Ruby team announced a proposed meeting from
February 6th to 10th 2023 [1,2]. One of the main tasks will be the preparation
for Bookworm and the final switch to Ruby 3.1.

Yesterday, the release team announced the final freeze dates [3].
Unfortunately, the date for the soft freeze is scheduled for February 12th,
which will make it virtually impossible for us to get the packages, which are
not yet in Testing (e.g. the whole Jekyll ecosystem), and the packages, which
are scheduled for removal before the meeting, back into Testing and therefore
into Bookworm.

We would like to ask you to postpone the freeze date(s) by a full week, so we
can care about all affected packages properly and ship them with Bookworm.

I know, that these dates have been proposed a year ago. Unfortunately, nobody
spotted this timing issue sooner. Otherwise, we would have contacted you, of
course.

Regards, Daniel

[1] https://lists.debian.org/debian-sprints/2022/12/msg2.html
[2] https://wiki.debian.org/Teams/Ruby/Meeting/Paris2023
[3] https://lists.debian.org/debian-devel-announce/2023/01/msg4.html

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPJ31wACgkQS80FZ8KW
0F0+XQ//SX5f0NO5tbfHhV0bqMziEZneXJ5TQVAd/0C0owkCigWy5LprofRyMRUe
DR70CJwd1xsNVqQD9qnN0NrvJX2iT7R0sU28So7u3lefpMh9ISMp3NyqWYnO/CEI
BZ3b8w1iy73REg9pHnYBtvB2z2+WSfwVY6yqq2lpCmN1EDx/tezY2IAtpq/FZ2Up
Vn4f83E7nD/3LgPao/jYzPRtARxod2DfKKTkHUzLged5dSXvSGZPY6Nm1kkIdpCj
mw7o8+5ilsIAc11FiZ6u2Yfy6bj7Qwgds3hGrkA1cZH0lVMlyVyBExY1SRCgqmUO
nSymzomKsfqEOjuZnknVwwz0k2R8ZaId+KfbwSmWt7VtVtZEpT1ztHBPBUuURBeS
B/44Rv6+PLfENB6DT0GjzdidQPNiOGPtbe8tX2qvotbXHmpxSu2820c4eYsdnoMm
6G1xnt6JieFw7FdC6w0BZnA8SJG3KZ9hS5AUe+SVj3BT6CQU1X1HBEEm6CP1JFlT
t7+GqrVjyaiR7FYsTTF6Uc+ZJeprkn2IXF9awYGKzNe1KegXgu4GlsqHF3QSn2lM
4XZ7Jl007PLmez6GhPCvAI+L6jHLcxLqJ90cSFFEhzvpIzjbb2XcZecNENTUY6CT
S3bthBRtZerAIdJxVJfL2f5j9XRLvkoAFjOpVv8AjzXScf9Lve4=
=S4nU
-END PGP SIGNATURE-

Bug#1023660: On every download it reports: "Cannot upload file changes/creation: .crdownload: No such file or directory"

[Daniel Leidert]

Package: onedrive
Version: 2.4.21-1+b1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Whenever I download a file via Chrome into the OneDrive folder directly, I see
the following error message appear as notification popping up, which is quite
annoying if one downloads a lot of files.

Cannot upload file changes/creation: .crdownload: No such file or 
directory

The target file itself, however, seems to have been uploaded correctly.

Regards, Daniel


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

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

Versions of packages onedrive depends on:
ii  init-system-helpers   1.65.2
ii  libc6 2.36-4
ii  libgcc-s1 12.2.0-9
ii  libglib2.0-0  2.74.1-1
ii  libnotify40.8.1-1
ii  libphobos2-ldc-shared100  1:1.30.0-1+b1
ii  libsqlite3-0  3.39.4-1

onedrive recommends no packages.

onedrive suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmNqYowACgkQS80FZ8KW
0F1YrBAAwQUcGgyke4c2Uw5ptHasvDAcxJ3hGA6wPo/fLWpltofBLJZAZr+j3bqV
GkYFXHYRifUTnGO/crcUtH5RyO3kaUowk0qq2UOqiaH5tFhI8d/9Z88oSG9gEg3F
Pmei1bV4pa8Lgz2hF6pgPmSn3D9m2j0PmD9r+ylqE4X8mwedCG9z8vq1wItKgXez
nFamaP5HPp+HPGgvs44BYnqQz/DKc2j1Aw/qV1wuhO8R4jjhjEMqY5MFz0WQ9VwH
AirmE4/EBUHAp7oqgIQ5api9MuXbsKVls5W2e4TfLxMqIz/WkonN/SEZuqT3ofNp
XVu53pRSM31fcBwzlKJ5LzwNek+1+lTx+rhzG+Tdtpy1LyPs+ihQkUq82NtWXspi
U4+CS8DKOo8Hnxl9pN5h8NqU7xohv6KV2nJ9juuYL0/y+JdSUrWZdmgoyHoFvSTH
vPqw+MO4Q39IROkRx00xTVXUaas2THAHDDpMibQHz9rfXma2fZOKP2ZaCBnpDKfu
SBB0dsY5qwOecB5t0ON4NssQjMVjAMVlhkL6XABRR8ZMDu3dMZVN6eHq9gbN70X1
iIgsDe6qNa/dINbjjd1P2qUm+dQ+4dq9wSYXYRgN2mvKxBVRBAmTmtXVGWwP+PgI
cFFQkgwNmrFg/5yfFZ57qmOOYxMB0PyQg0/6Eu8zCDM4/qcuVWU=
=nGzO
-END PGP SIGNATURE-

Bug#1015224: Illegal instruction (SIGILL) on arm64

[Daniel Leidert]

Package: librocksdb6.11
Version: 6.11.4-3
Followup-For: Bug #1015224

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Attached is a possible debdiff.


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

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

Versions of packages librocksdb6.11 depends on:
ii  libbz2-1.01.0.8-5
ii  libc6 2.34-4
ii  libgcc-s1 12.1.0-8
pn  libgflags2.2  
ii  liblz4-1  1.9.3-2
ii  libsnappy1v5  1.1.9-2
ii  libstdc++612.1.0-8
ii  libzstd1  1.5.2+dfsg-1
ii  zlib1g1:1.2.11.dfsg-4.1

librocksdb6.11 recommends no packages.

librocksdb6.11 suggests no packages.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmMDoyQACgkQS80FZ8KW
0F007w//dKCqzbe+82TIHobnj18BEq0ilHiTwkh6vkP7pFEsJJE/fqrOzQfgaAV/
77jGf8sZDDn0tpetdAvIGXuQFRQqjNlahNLCepX40sxfUpLl04wlMhs5PnQw4hX3
+NK6k3KTWR2k+ViAGL6VeAzmVuqe5l7BcWluf6y3tQbTYNCIWy+qmcybshR/Azn3
j0e/xHoJA9PQ3r3+WFsElXw1Cm8mqHSKq5XMld4cMYlq6S9BZxNBlQ5Lzk7lPILA
Q44aTcKCAjAGUW9pRYZCvcRca9LGoIWckWTvmSvEyjodbqJwXgFAp4Z794o2UIp4
MYnYvVGEn/LmHhi0TrPTiFvyH3K3Zs+Du1ZDMZwE+Sdl7DDiPvvXRa5Qo4j/16jw
qMp3MDL4CQc82nNWKHqZ8uh1rGz8EMyAAlkj/DoM21ygrQ04ZhexyrT8bBWXjBcm
1I3bADg97GoxQLA5b8pycgKTKGqM1U/SxnMVzocacbOOaOdeskiCKTtg5PJJM4Zt
9qz90H6tyXbNn9NnofRgfiok70dItamDSKsYWavaAsp3wO4ikoydc3guKIzasTJp
l+BNqUPmnym7fI90r93LFvxlxhTTYnzoJ+98Rkp8WzMRXRUfIaxPF0ls8k6W7ZZP
CCFRNJdm8T5fECoXf0eURwpKyGxtqy2VON7J34FRaFdBieACUqk=
=U1bp
-END PGP SIGNATURE-
diff -Nru rocksdb-6.11.4/debian/changelog rocksdb-6.11.4/debian/changelog
--- rocksdb-6.11.4/debian/changelog 2020-12-10 17:13:16.0 +
+++ rocksdb-6.11.4/debian/changelog 2022-07-18 21:51:17.0 +
@@ -1,3 +1,10 @@
+rocksdb (6.11.4-3.1) bullseye; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix illegal instruction (closes: #1015224).
+
+ -- Daniel Leidert   Mon, 18 Jul 2022 21:51:17 
+
+
 rocksdb (6.11.4-3) unstable; urgency=medium
 
   * Explicitly link shared library with dynamic linking library
diff -Nru rocksdb-6.11.4/debian/patches/fix_illegal_instruction.patch 
rocksdb-6.11.4/debian/patches/fix_illegal_instruction.patch
--- rocksdb-6.11.4/debian/patches/fix_illegal_instruction.patch 1970-01-01 
00:00:00.0 +
+++ rocksdb-6.11.4/debian/patches/fix_illegal_instruction.patch 2022-07-18 
21:48:42.0 +
@@ -0,0 +1,225 @@
+From 29f7bbef995bdf83098963799c66af742e95373f Mon Sep 17 00:00:00 2001
+From: Yuqi Gu 
+Date: Tue, 22 Sep 2020 10:39:54 -0700
+Subject: [PATCH] Fix RocksDB SIGILL error on Raspberry PI 4 (#7233)
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Summary:
+Issue：https://github.com/facebook/rocksdb/issues/7042
+
+No PMULL runtime check will lead to SIGILL on a Raspberry pi 4.
+
+Leverage 'getauxval' to get Hardware-Cap to detect whether target
+platform does support PMULL or not in runtime.
+
+Consider the condition that the target platform does support crc32 but not 
support PMULL.
+In this condition, the code should leverage the crc32 instruction
+rather than skip all hardware crc32 instruction.
+
+Pull Request resolved: https://github.com/facebook/rocksdb/pull/7233
+
+Reviewed By: jay-zhuang
+
+Differential Revision: D23790116
+
+fbshipit-source-id: a3ebd821fbd4a38dd2f59064adbb7c3013ee8140
+---
+ util/crc32c.cc   |   6 +++
+ util/crc32c_arm64.cc | 111 ++-
+ util/crc32c_arm64.h  |   1 +
+ 3 files changed, 74 insertions(+), 44 deletions(-)
+
+Index: rocksdb-6.11.4/util/crc32c.cc
+===
+--- rocksdb-6.11.4.orig/util/crc32c.cc
 rocksdb-6.11.4/util/crc32c.cc
+@@ -41,6 +41,10 @@
+ 
+ #endif
+ 
++#if defined(__linux__) && defined(HAVE_ARM64_CRC)
++bool pmull_runtime_flag = false;
++#endif
++
+ namespace ROCKSDB_NAMESPACE {
+ namespace crc32c {
+ 
+@@ -494,6 +498,7 @@ std::string IsFastCrc32Supported() {
+   if (crc32c_runtime_check()) {
+ has_fast_crc = true;
+ arch = "Arm64";
++pmull_runtime_flag = crc32c_pmull_runtime_check();
+   } else {
+ has_fast_crc = false;
+ arch = "Arm64";
+@@ -1224,6 +1229,7 @@ static inline Function Choose_Extend() {
+   return isAltiVec() ? ExtendPPCImpl : ExtendImpl;
+ #elif defined(__linux__) && defined(HAVE_ARM64_CRC)
+   if(crc32c_runtime_check()) {
++pmull_runtime_flag = crc32c_pmull_runtime_check();
+ return ExtendARMImpl;
+   } else {
+ return Ext

Bug#1016093: Grub UEFI installation fails when EFI partition has already been mounted

[Daniel Leidert]

Package: vmdb2
Version: 0.26-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

When the EFI system partition is already mounted, the grub UEFI install fails
with

2022-07-27 00:47:13 DEBUG STDERR: mount: /tmp/tmpXXX/boot/efi: 
/dev/mapper/loopYp1 already mounted on /tmp/tmpXXX/boot/efi.

One can easily reproduce it with the uefi.vmdb example by simply mounting the
EFI partition to /boot/efi after mounting the root filesystem:

  - mount: efi
mount-on: /
dirname: '/boot/efi'

The workaround at the moment is to not have the EFI system partition mounted.
But it seems rather weird to have this as a requirement.

Regards, Daniel


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

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

Versions of packages vmdb2 depends on:
ii  cmdtest 0.32.14.gcdfe14e-4
ii  debootstrap 1.0.126+nmu1
ii  e2fsprogs   1.46.5-2
ii  kpartx  0.8.8-1
ii  parted  3.5-1
ii  python3 3.10.5-2
ii  python3-jinja2  3.0.3-1
ii  python3-yaml5.4.1-1+b1
ii  qemu-utils  1:7.0+dfsg-7

Versions of packages vmdb2 recommends:
ii  ansible   5.5.0-1
ii  dosfstools4.2-1
ii  qemu-user-static  1:7.0+dfsg-7

vmdb2 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIB9kcJqmmF4VguFXclr8JZgo7DMFAmLgcYIACgkQclr8JZgo
7DMohRAAu9Bzz2r2dVaI9yIo+906kfqoSdMr7w+8oWEj0buZPI0qZ2pIbnY4Que8
LxmdHctRGAqA32/AFM4mpcEbApQB9UXEW9IXToqxdrJvRyMznYYWFJWJExWy64wb
EqHWWcZKNFVEKWXLnZfbQc7cYEvyIAntBgdwt88SVViYlumw2vJsElSZls4SWiL6
F4TloYlaUuJaOCfpXCM/lSpePFhAj3XUPpQ6odvwBWVLQNO41IBBMfDNbfJogtsx
yhD5CnBQAWYC7pkpIezGuG+HNBMiYWm1Z0c2DxQIT5a+rV4qLRktzpekgtTQ0KYC
4pbIKaGmW9EA1CUHNwDJx/BTt64T2eZ/bFPrPC02AXOvD/c/YA0QryUyZ27kFv4x
hf+I1EB8JRtwmwPSrY1Tqsz+1tGKhGQQSrIKI2fzH3+3e56Ne6gvt+NltvBOgEe9
P4jqF9uGoImIAkwoRyyyxk4b2+TnTyDRM4C3WQCr2x0B6Nb3ibDUVI2yG+vlHUlu
ZZks3/IJLYTne/UDveubizOUDoeFMjDl03Cwr0Fs+YIq/gpjxqBiuGpE99g8b49M
0S39LDW+Kvn3EM86nYz0JY0sob8GTE9sNsVDOW5eBTevu/BWwkAXlW490SrPfFS+
SrMTa3SPEvWa5O8hXk57fIwax8GN7hCxgEAIEzjvuiEJuNdnFBE=
=1MDK
-END PGP SIGNATURE-

Bug#1015224: Illegal instruction (SIGILL) on arm64

[Daniel Leidert]

Package: librocksdb6.11
Version: 6.11.4-3
Severity: grave
Tags: bullseye, patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I got just hit by https://github.com/facebook/rocksdb/pull/7233 on my RPI 400
running Debian Bullseye. I rebuilt the librocksdb6.11 package with the patch
from
https://github.com/facebook/rocksdb/commit/29f7bbef995bdf83098963799c66af742e95373f
and I can confirm that this patch fixes the SIGILL issue.

Is there any chance to push that fix into Bullseye? Without it, librocksdb is
not working for me on my Raspberry PI.

Regards, Daniel


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

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

Versions of packages librocksdb6.11 depends on:
ii  libbz2-1.01.0.8-5
ii  libc6 2.33-8
ii  libgcc-s1 12.1.0-5
pn  libgflags2.2  
ii  liblz4-1  1.9.3-2
ii  libsnappy1v5  1.1.9-2
ii  libstdc++612.1.0-5
ii  libzstd1  1.5.2+dfsg-1
ii  zlib1g1:1.2.11.dfsg-4

librocksdb6.11 recommends no packages.

librocksdb6.11 suggests no packages.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIB9kcJqmmF4VguFXclr8JZgo7DMFAmLUhqkACgkQclr8JZgo
7DPsPRAAtqU9d0WaXdqYIfrjyMNnJkvcCzGTM211mRIq5tFk9PqiyRAWZqjhCwn3
7QNA4uYQbECXgd6Bgc+hP+GDoPlbwPYRe6VeNIzPc87LpAVh2BR2jG2D4tzCtG1/
hHqolpGbDsMmTyr1hSQwfZWwCZJ5uIsIk60Of3O1TD/PM2dFpSqwFb/dwKJ2B/v+
oqqaZDLOxeh87vqEmFmCxubstk9giNWtID9tMXfE8c5ot9naAViNBlHzRyj9L2PC
xJ7dPSmS4qqWouZUSOM/PaIYjmK2oFB2OVJ/w1isao0SNkQIePRMg43R8x5TGKI+
x3pUvPyBe5lekq2yVD/wigOSFF2fLh+FhM/5+Noq+c6aEIRAU16pa0iMA5SF/w9C
5l0tapF/T0RYM8zaAfZe95hqCgq4OtUwHry1OEEL/r0ngEPnLkjUwHaOVPr0PGNh
ZZhmBrpg23NR17m+4H4OksyGB3D8w8I5X2EiljKBiIXZzOVUO5ATGedZOM2nWXH7
EYCZqhbjVWCYuGZtNBuzlFaeK5bGA0UWTj+LG1LQcaAXIWLnWJQ7vKeXDiDeJ+m/
hposcBS9yR3ndCX0Wp418EvgQVYgnmCABbeH/o2PJ1JgvpFDLajUHeWOhSSU7iGu
yAvryTvY/Hc/4uXRr7V0F+YKoBCbNOVKrnS/ypZbxBHSt/p9Yu4=
=GH1z
-END PGP SIGNATURE-

Bug#1013291: gdbus monitor is not receiving signals

[Daniel Leidert]

Package: libglib2.0-bin
Version: 2.72.2-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Contrary to Bullseye, gdbus monitor does not report emitted signals in Sid. As
an example.

In tab 1 I run:

gdbus monitor --session --dest=org.freedesktop.Notifications

In tab 2 I run:

gdbus call --session --dest=org.freedesktop.Notifications 
--object-path=/org/freedesktop/Notifications  
--method=org.freedesktop.Notifications.Notify "" 0 "" 'Hello world!' 'This is 
an example notification.' '[]' '{"urgency": <1>}' 5000

When I close the notification, the monitor should actually receive 
a org.freedesktop.Notifications.NotificationClosed signal. And in Bullseye it
does, and dbus-monitor shows it as well, but gdbus does not show it in Sid.
Also emitting the signal via dbus-send or similar does not lead to any event on
the monitor.

Regards, Daniel


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

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

Versions of packages libglib2.0-bin depends on:
ii  libc62.33-7
ii  libelf1  0.187-1
ii  libglib2.0-0 2.72.2-2
ii  libglib2.0-data  2.72.2-2

libglib2.0-bin recommends no packages.

libglib2.0-bin suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIB9kcJqmmF4VguFXclr8JZgo7DMFAmKxFAsACgkQclr8JZgo
7DPO1xAAxx1JmxU5Q79jlcCulm3RADZeg5oTJfiPS9AIl4YFm4Sf2+iQmQBkuMrB
1HkzGChgKOr7c/Wjkqg67YI/6KDOgguxPOXupsidFCBPYGiuHHlxPGxUdk9lW0yF
ZvogbiKbKvcD8miompWDFmblikOzjHv77Gi85YzMGoqhGK1PEke6U3TuaPzLaMmi
JMwdOifwZAQy1t1yaQCbhD1bBgA42CaktGN78eX1rFlDekUmsrQt/bFBvZao8BzB
/ThklYRn6YBDvAKtO47Mmnpn+V/LMcoVUUKB3C5CUuInGXkrUeHlumrpEq1W0kWa
DAH68L2RBt4CIM1fZF5IyYZ01TwmrpVFN/ruKOwteYFHIR/0+aqQ5Ujo/Zq89FX2
P2HwDZ8unQbykzEoHrIhSQGBl2sIFiGhS8M78/OIyIVsQl+Hpbbbdl6Qa4LkE8m4
40wlWu+O6KuRRrVbmGiHZGbM7t7bQPTOLhnQ3oZIX2xctxQfeBoKs8ushdPjKAQz
/TTkCkTAdsrM5ELWk/SXB4fExjJem70Gmhb+kR2f0khEVSL2WhyOE/XAww+l8qcf
HzRfoEaJsSUvpElOBNI1atiWxM/arnjybWgqRncuODo3q3WB6vchHoNgqU8HSiK+
aqnVSgvd5f6FtiESiIzbYmkqPMcqNZjuQv0koQrwn8OJKLEguVs=
=xqvR
-END PGP SIGNATURE-

Bug#1011105: ./easyrsa build-ca nopass still asks for PEM password

[Daniel Leidert]

Package: easy-rsa
Version: 3.0.8-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I encounter the following problem:

./easyrsa build-ca nopass

Using SSL: openssl OpenSSL 3.0.3 3 May 2022 (Library: OpenSSL 3.0.3 3 May 2022)
Enter PEM pass phrase:

That shouldn't happen. The issue has been reported upstream, but was supposed
to have been closed already (https://github.com/OpenVPN/easy-rsa/issues/454).
Can you please check that out?

Regards, Daniel



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

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

Versions of packages easy-rsa depends on:
ii  openssl  3.0.3-3

Versions of packages easy-rsa recommends:
pn  opensc  

easy-rsa suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIB9kcJqmmF4VguFXclr8JZgo7DMFAmKC1pEACgkQclr8JZgo
7DNijhAAurcP50qUKPt3IsLfk5sviL1h3GhnqBhhZXVAwoc9PPTfYLXZJBFBCmMk
zu5aE6U9WtKlFQBAnWBbKOn/qGMdg1bfWOuMKmGmVGhJ29iQM7nCw6M9P9ev4iv4
ApNOW3J27ikCiE9CBowl+XsaQYe+BDGFpQp/KUMi6uw18JihyrVP6SUh4n9RzpvA
RFeKSrzOITTIFTLPs8H0nxunmEt2jevpv6ZWEntjfYg1KYvMXv1rN90ovRuxxPHL
cOV5OI1IynghODu8EAXSkX19c8hQsF7f+d6WCzJ/NIWgI/0H1A6lcHqlK5dtf2tX
kt2k3X0bDitaNvN6kYjN5TWJXpMuhjnq4beHGR4n4ZrrCioLVLdBK3/9SLNWeyT0
t+/ACf0t/8bPert0G3W9sj1NTJe3SzrmWArV3Vkz10NwT8lsfpo38F2MckLBpICm
2GnnKZ9bPHXQlmaEEvfYhhFFLhg6H76siO8TBi2AHvkCLsC9dSe69q+GEO5uOwwI
s/WOjg0X+zFCXKCezLkLhnODY4wnKe5X06J09QMyicl5UrBUlMJouLGxeA+rmb8P
LzuI1+D0VeLFoqYiMQ/0WImy/rZYhljspifxzhM5N7CxJ02ep75YoDzKVA1mcY5d
no0wLTeviCdB0UuR4EfGLt6kSkAStKgf0dLVPJvXyY/OrcreY/g=
=ZV9W
-END PGP SIGNATURE-

Bug#1010734: kpartx fails, but the image is created anyways

[Daniel Leidert]

Package: vmdb2
Version: 0.26-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I see the following error even with successful builds:

[..]
Removing /tmp/tmpe5io4xoc.yaml
Removing /tmp/tmp7_tev8wl
Exec: ['zerofree', '-v', '/dev/mapper/loop0p2']
Exec: ['kpartx', '-dsv', 'fantronics.arm64.img']
ERROR: Program failed: 1
ERROR: RuncmdError('Program failed: 1')
All went fine.


This is from the .log file:

[..]
2022-05-08 16:48:04 INFO Exec: ['kpartx', '-dsv', 'myproject.arm64.img']
2022-05-08 16:48:05 DEBUG STDOUT: del devmap : loop0p1
loop0p2 is in use. Not removing
???

2022-05-08 16:48:05 DEBUG STDERR: loop deleted : /dev/loop0

2022-05-08 16:48:05 ERROR Program failed: 1
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/vmdb/app.py", line 243, in 
run_steps_helper
method(values, settings, state)
  File "/usr/lib/python3/dist-packages/vmdb/plugins/kpartx_plugin.py", line 51, 
in teardown
vmdb.runcmd(["kpartx", "-dsv", device])
  File "/usr/lib/python3/dist-packages/vmdb/runcmd.py", line 58, in runcmd
raise RuncmdError("Program failed: {}".format(p.returncode))
vmdb.runcmd.RuncmdError: Program failed: 1
2022-05-08 16:48:05 ERROR RuncmdError('Program failed: 1')
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/vmdb/app.py", line 243, in 
run_steps_helper
method(values, settings, state)
  File "/usr/lib/python3/dist-packages/vmdb/plugins/kpartx_plugin.py", line 51, 
in teardown
vmdb.runcmd(["kpartx", "-dsv", device])
  File "/usr/lib/python3/dist-packages/vmdb/runcmd.py", line 58, in runcmd
raise RuncmdError("Program failed: {}".format(p.returncode))
vmdb.runcmd.RuncmdError: Program failed: 1

Is it the underlined line? Interestingly this works fine in a docker container.

If I can provide more information, please let me know.

Regards, Daniel


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

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

Versions of packages vmdb2 depends on:
ii  cmdtest 0.32.14.gcdfe14e-2
ii  debootstrap 1.0.126+nmu1
ii  e2fsprogs   1.46.5-2
ii  kpartx  0.8.8-1
ii  parted  3.5-1
ii  python3 3.10.4-1+b1
ii  python3-jinja2  3.0.3-1
ii  python3-yaml5.4.1-1+b1
ii  qemu-utils  1:7.0+dfsg-5

Versions of packages vmdb2 recommends:
ii  ansible   5.5.0-1
ii  dosfstools4.2-1
ii  qemu-user-static  1:7.0+dfsg-5

vmdb2 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIB9kcJqmmF4VguFXclr8JZgo7DMFAmJ4AdIACgkQclr8JZgo
7DMKWQ/+Ju9gSdfcd/kmKyBs0sRLG/1ZFAWQ8VWpYaG7Dn3yiyo1W+KdemVvIZlS
SzPpiI+NOuY+AVC9QuC8LwuQeAvJ+koSsw8XQDHF9rzu3YM+63DchJIenUca4xdi
EgB73i4LTvE3AyAMoacCooz1Jwu18xQ2ZRUVYNnKZYpIhZE1xYUKeRUcZ8eIb2hC
7CteZIU3DUcb7sA8/XMhWwRuqS8v+q1lniw+2HPTDA23KT9GHxAeItJ5NVMd9D9k
JmZcWsL16+PUmFLN9GEdIIcebTUVP4GSqGg8ZfpA8IIADdkgUtixXi9a5zh+5Z90
rVgCuYM/4ZVw1Iu2IqjjNWU+uibY1YwrF2wD7GMg2FwyhQJapIs8dIOMpAniFlMG
lgcItd3IkftMYYjjtYE7luiiMOlhwGRlS0QTWIKGrzD0BLYQWEx1QD5hPtoIH+om
IxicYb+FraHc6JsHmY9m3NODjYRULeUR3z8tqQUMGbCF0EyRuzEzrri424hbtZHG
bffQTNlSWLKqU1G8ygE/bn5bqnCSZ5ZMqcGFiPVLmAFi+ssK5MioxdVZrwHjh4ZW
OIyxINh2oxcXk+r0ke0+Tyvy+cV2uMYnFLFhOS6pss5a76rw2WeasahJzim8xEVa
uHIxiwjIzLi9v+WjqlNOnL3+BoYaFRD7iOz+tESO0XEvv0wiXwk=
=nSGu
-END PGP SIGNATURE-

Bug#1008811: Won't start without python3-dbus (misses dependency)

[Daniel Leidert]

Package: snapper-gui
Version: 0git.960a94834f-3.1
Severity: serious

snapper-gui doesn't start without python3-dbus:

$ snapper-gui 
Traceback (most recent call last):
  File "/usr/bin/snapper-gui", line 33, in 
sys.exit(load_entry_point('snappergui==0.1', 'gui_scripts', 
'snapper-gui')())
  File "/usr/bin/snapper-gui", line 25, in importlib_load_entry_point
return next(matches).load()
  File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1030, in _gcd_import
  File "", line 1007, in _find_and_load
  File "", line 972, in _find_and_load_unlocked
  File "", line 228, in _call_with_frames_removed
  File "", line 1030, in _gcd_import
  File "", line 1007, in _find_and_load
  File "", line 986, in _find_and_load_unlocked
  File "", line 680, in _load_unlocked
  File "", line 790, in exec_module
  File "", line 228, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/snappergui/__init__.py", line 1, in 

import dbus
ModuleNotFoundError: No module named 'dbus'

It seems this dependency is missing.

Regards, Daniel


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

Kernel: Linux 5.10.0-13-amd64 (SMP w/12 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages snapper-gui depends on:
ii  gir1.2-gtksource-3.0  3.24.11-2
ii  python3   3.9.2-3
ii  snapper   0.8.15-1

snapper-gui recommends no packages.

snapper-gui suggests no packages.

-- no debconf information

Bug#1007248: nodejs trying to overwrite /usr/share/systemtap/tapset/node.stp

[Daniel Leidert]

reopen 1007248
thanks

I just got hit by this bug as well:

Entpacken von nodejs (16.13.2+really14.19.1~dfsg-5) über (12.22.9~dfsg-1) ...
dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-DvPfq0/442-
nodejs_16.13.2+really14.19.1~dfsg-5_amd64.deb (--unpack):
 Versuch, »/usr/share/systemtap/tapset/node.stp« zu überschreiben, welches auch
in Paket libnode72:amd64 12.22.9~dfsg-1 ist

It seems this issue is not yet fixed or this is a regression.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#993678: Patch fixes problem

[Daniel Leidert]

I can confirm that the patch fixes the reported issue.

Regards, Daniel

Bug#1006521: ITP: ttyplot -- realtime plotting utility for text mode consoles and terminals

[Daniel Leidert]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: ttyplot
  Version : 1.4 + git commits since then
  Upstream Author : Antoni Sawicki 
* URL : https://github.com/tenox7/ttyplot
* License : Apache-2.0
  Programming Lang: C
  Description : realtime plotting utility for text mode consoles and 
terminals

ttyplot takes data from standard input or a unix pipeline and plots in text
mode on a terminal in real time. It supports rate calculation for counters
and up to two graphs on a single display using reverse video for the second
line.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmIaaxIACgkQS80FZ8KW
0F1OgA//bAlGNJgjWrXdne+rtJfFHvL5naGYCkW/e7vStspw1kl81/gtJ4s/mMNe
U2qEkTPy6+oUQk/9Khb0liH9tE3h+dIaMFak0u+FSWle4DMcau9CI0rsQOYi6mYz
d6AZz02vbHezxMUR9oWKASqOIl6PyMF0fcdFzfanT900n4GfAyCzjlS4hAkxqd92
VDfQ6PcXUeOYTG7X/5FfQZtkfjFqW4OUIUaDAfJE4IoFy7LqVLKG1JsBXMGIzBqK
UF3KzG1+p1G+l12sHM4ENPKB2/5v1g6tcDcs8aez+XF/LvGIkS+gd+g1n4l1esYj
S8A7b5WspJXyLclu2RMsDta7R/Mp0WUfp5R5h7FYJgohGMiXtO87wzSkmquudL14
lxXifQj+mJjJ8D3/5GIMP4wMvYHEHoQ0I4rayJyIKPNvDpnnv1zV2o6nVNou+CCr
GR3lCBspCdY1xuIpidmC+udhdZnyQ0lfoXAOUu/lAOcjt7fmQGE4Ht+cHkMU4sh1
FV6p19jkdIdScxvkbs58H0AYOpPTs/yci+Ol/RnbTGJfZerc+GpBenv75VGcWtXZ
hGJwgSETXFd05+YN6tvLuLuxLHIpKknjec2DjqW3KCIUxOPK2ibLZRJ2BX3g2/RA
GJ/OA45hiXlJTSlQygMmluq4N8PD6ijauWY1YpD8RCxkih/iV5o=
=F4oI
-END PGP SIGNATURE-

Bug#982666: Alternative solution

[Daniel Leidert]

Hi,

so this issue just bit me on a newly created Bullseye. Instead of dealing with
symlinks or copying files around, I just ran the scripts by including
/etc/migrationtools in INC:

PERL5LIB="${PERL5LIB}:/etc/migrationtools" ./migrate_...

IMHO this should be fixed one way or another in Bullseye.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1006279: Please update to latest release 1.4.1 including configuration file and systemd support

[Daniel Leidert]

Source: wondershaper
Version: 1.1a-10.1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

It seems the develolment of wondershaper has been moved to github and there has
been some development going on since the last release packaged in Debian.

https://github.com/magnific0/wondershaper

Packaging this might also provide fixes for some of the outstanding bug reports.

Regards, Daniel


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

Kernel: Linux 5.16.0-1-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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmIVF/EACgkQS80FZ8KW
0F1vKw//ep3y7l5gFQvGlfo5BZMFsLXSA4aXXWSThD/5ShFb4/fN3V//nXCktnhs
o+cf/iKCRqq77tgsd081TrZriKrVB5fc6TDETI+GV6GXbhUm8zALWoK7yLIRuuq5
s9Kokfl5BJyID9O3VUNZpSyn4B69pWpWpMTgoYM9sh6AB+6LeHdBewFESSWxHuVe
6WPyfSqZvINSZ4U1As7YRcCMcAmwH/SvIBvEA8YIvsnkBo+ijMvI7RqDSoUoQBXA
v/lmZJV6YBeqqlnNDKX8SUHnJHp7AfH8ULkIhl2L0CnnmS7HSbChTwrvgVb/bxEE
OzrBpOuKeBgfzqM3JkSJQCHJstyegpXGO3BmbdQ9xNp77udbbR/jFMhjlgGxlUK3
BHz9tPLcvQa/SFoO8ar0x+DlLU4Od4f0l7trxnjVneeiHGbqMf/tAmRlfJHT/yki
8bErOtV2BHeS/54bUYbd4hCm46c/yHp6RDXoDNgg/uRotLrM9gHpqOwnNqxXq8aQ
5AdYUSnUuZiuTiT9YmN1RMpSRZAKFjJZ/xup2bhMKY+fjdw0ddJ1+yUQLYGlrb3v
VjwppBz9/NhfdZYkr16mhBL7N1W5u5fbCxYbHRu3CJf89+yIRU7ZUgb3AcYNvBnV
N0uXSKiZRENFQpIHJpPiAaAxSfmrDrfOJLfDVgvdrhWPl9n+6aE=
=VbZZ
-END PGP SIGNATURE-

Bug#1006198: docbook: Packaging license incompatible with the upstream

[Daniel Leidert]

Am Montag, dem 21.02.2022 um 10:57 -0300 schrieb Eriberto Mota:
> 

[..]
> Considering that docbook is orphan plus your reply (or your very
> aggressive reply),

Maybe you should re-consider your approach and reflect on the actions you were
announcing. I cannot even believe that a DD threatens to relicense without
proper permissions by the authors. And you haven't layed out what you consider
to be the problem, which makes it impossible to even come up with a sensible
solution.

Also: How should the Docbook license, which clearly restricts itself to the
"[..] DocBook XML DTD and its accompanying documentation [..]", cover the
packaging files?

JFTR: Most of the original Debian package maintainers cannot be reached
anymore. Your chances to get the required permissions are slim.

> I am closing this bug.

There is IMHO no "hampering" condition. The patches that are part of the
package will not be accepted into upstream for the reasons I have layed out
earlier. The DocBook project is not changing their releases, not even for bug
fixes. Those have always gone into the next release or the RC for the next
release. Thus the existing patches pose no problem at all IMO.

New patches also pose no problem. The patch author has the authority to provide
their contribution to the DocBook project under the DocBook license and also
ship it with the docbook-Debian package if necessary.

And then again: We always had the intention to not deviate from upstream - the
Debian packages should always behave like the upstream releases. Thus we were
always working closely with upstream (Debian even had a chair in the OASIS,
IIRC). And I fail to see good reasons. why we would want to change that, as
well.

Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1006198: docbook: Packaging license incompatible with the upstream

[Daniel Leidert]

Am Montag, dem 21.02.2022 um 00:55 -0300 schrieb Joao Eriberto Mota Filho:
> Package: docbook
> Version: 4.5-9
> Severity: normal
> X-Debbugs-Cc: Mark W. Eichin , Adam Di Carlo
> , J.H.M. Dassen (Ray) , Yann Dirson
> , Steve Langasek , Daniel Leidert
> (dale) , Jakub Wilk , Mathieu
> Malaterre , Helmut Grohne 
> 
> The current packaging license (GPL-2+) is incompatible with upstream
> licensing (DocBook License). It is a hampering condition to submit patches
> from Debian to the upstream.

Can you elaborate on the problems you observe?

The docbook* packages are not supposed to differ from upstream, so bug fixes
should always go back to upstream. There is no interest to create our own
variant. There was just one problem: issues in older releases don't get fixed
by upstream anymore - or better: upstream fixed those issues and then released
the fixes with the next version. They don't touch older releases. That's why we
have a set of patches to fix problems in e.g. DocBook 4.3. Those patches will
not be accepted by upstream anyway, so there is IMHO no issue having those
under GPL.

> I would like to change the packaging licensing to 'DocBook' and I will
> wait 15 days to know if anyone has any objection.

You want to relicense the code because you don't like the license, and you want
to do it without permission of all the authors/contributors that added their
work under the GPL-2+ by delcaring them not to answer to silently agreeing?
Interesting take on relicensing, purely illegal though ... 

Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1003958: Tries to remove ansible diectoriy several times in a row, leading to: ERROR: [Errno 2] No such file or directory

[Daniel Leidert]

Package: vmdb2
Version: 0.24-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I'm using vmdb2 with multiple ansible playbooks. And I'm seeing this:

[..]
Created /tmp/tmpj0x17zzv for Ansible inventory
Created /tmp/tmpttvwe7id for Ansible variables
Exec: ['ansible-playbook', ...]
Created /tmp/tmpqjtb15c0 for Ansible inventory
Created /tmp/tmpxdyg2rez for Ansible variables
Exec: ['ansible-playbook', ..]
Created /tmp/tmpbsgvk2dz for Ansible inventory   that's the 
directory
Created /tmp/tmpwa3gb4e9 for Ansible variables
Exec: ['ansible-playbook', ..last playbook..]
Removing /tmp/tmpbsgvk2dz
Removing /tmp/tmpbsgvk2dz
ERROR: [Errno 2] No such file or directory: '/tmp/tmpbsgvk2dz'
ERROR: FileNotFoundError(2, 'No such file or directory')
Removing /tmp/tmpbsgvk2dz
ERROR: [Errno 2] No such file or directory: '/tmp/tmpbsgvk2dz'
ERROR: FileNotFoundError(2, 'No such file or directory')
Exec: ['kpartx', '-dsv', 'fantronics.img']
All went fine.
[..]

Is it possible that vmdb2 should instead iterate over a directory list? It is
weired that it tries to remove the same directory three times, the same amount
of playbooks I run.

Regards, Daniel


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

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

Versions of packages vmdb2 depends on:
ii  cmdtest 0.32.14.gcdfe14e-2
ii  debootstrap 1.0.126+nmu1
ii  e2fsprogs   1.46.5-2
ii  kpartx  0.8.5-2+b1
ii  parted  3.4-2
ii  python3 3.9.8-1
ii  python3-jinja2  3.0.1-2
ii  python3-yaml5.4.1-1+b1
ii  qemu-utils  1:6.2+dfsg-1

Versions of packages vmdb2 recommends:
ii  ansible   2.10.7+merged+base+2.10.8+dfsg-1
ii  dosfstools4.2-1
ii  qemu-user-static  1:6.2+dfsg-1

vmdb2 suggests no packages.

- -- no debconf information

- -- debsums errors found:
debsums: changed file 
/usr/lib/python3/dist-packages/vmdb/plugins/ansible_plugin.py (from vmdb2 
package)
debsums: changed file 
/usr/lib/python3/dist-packages/vmdb/plugins/grub_plugin.py (from vmdb2 package)

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmHm7AoACgkQS80FZ8KW
0F30pBAAx85eHPwRhG7scfUmCEsO0nOznu+9LVg3il5PGGm3myPGo1Q6WYogVkL3
AjeuflntSQtEwUu1tbd4nF3VuSEU6ZHo41f0pDfmNIlnhSvujoEz9+ZRvP61wkrT
F/XSTu2tKA49NMDo7J8WXgxkmF15ltSuywgObfRCbKjixCS+Xn88c3IGezkqeMhc
MGZ0RV1ZffMcuUzrhCdKJ824XrFQNONT7z96i/4Fc4BPavey2FmJ3AXbHP8DA8PY
RbGrHqS+Zf9yiGa0jFPzwnwTD3zM3N9pSb67OeSkdoll3kh4OIhr8xZewz8OHOMX
AiJO6ZHiUjR8T+9RnaFT2E0PX05sylZtzFMm7SddsgrWAVpdsmYQcSPeRUG4EzXN
UvnRtgOFvZwGUMXFhbmx1ArQYauK+8sb5iXnxq6Ui8/LBluYj3ftSu2a3sZzAxSu
HZc66gDNYpEUon82QKGs6ORZcy3lEgqxNQnMHsa8yjh7MazZMFj8k9ooxjg5hJIL
MLtbp7bnio/4Ki8QdFN98SHE/hrDMjnw9ITWtpl8qDGPRQ90DRpmP3doF888pJuP
9DX8aCO1CHPinHpVRixvwmZKMVx1okq/K42J+BHqVLgEA4Fe27K+ZeJ8ouPCCTTG
n98Tre4Nx++SerFxFuHfJXcHU9bo2Z2Ru5mDHWWOK+8LjcW0xTU=
=mPoC
-END PGP SIGNATURE-

Bug#1003959: E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)

[Daniel Leidert]

Package: vmdb2
Version: 0.24-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Whenever I run an apt-related step, I see this error message in the log:

 DEBUG STDERR: E: Can not write log (Is /dev/pts mounted?) - posix_openpt 
(19: No such device)

Should this be bind-mounted into the chroot?

Regards, Daniel


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

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

Versions of packages vmdb2 depends on:
ii  cmdtest 0.32.14.gcdfe14e-2
ii  debootstrap 1.0.126+nmu1
ii  e2fsprogs   1.46.5-2
ii  kpartx  0.8.5-2+b1
ii  parted  3.4-2
ii  python3 3.9.8-1
ii  python3-jinja2  3.0.1-2
ii  python3-yaml5.4.1-1+b1
ii  qemu-utils  1:6.2+dfsg-1

Versions of packages vmdb2 recommends:
ii  ansible   2.10.7+merged+base+2.10.8+dfsg-1
ii  dosfstools4.2-1
ii  qemu-user-static  1:6.2+dfsg-1

vmdb2 suggests no packages.

- -- no debconf information

- -- debsums errors found:
debsums: changed file 
/usr/lib/python3/dist-packages/vmdb/plugins/ansible_plugin.py (from vmdb2 
package)
debsums: changed file 
/usr/lib/python3/dist-packages/vmdb/plugins/grub_plugin.py (from vmdb2 package)

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmHm7MsACgkQS80FZ8KW
0F33UQ/+LkE7qXdvgdsIEVRGb8SXdzLQBQEEIaqkuCiWvfk//oRVy0uGPXvgb4kN
Iitl6B6MPfmLqDkYllSK6WGBrB+ykH2JbjziJ8SZpEdy6T4C+U7vdvVAnyuPEunM
V1ia4sPJZ+g8w+iM6v/OXnP61rlTVFmfWbwVP1TSN+mULdPi/4aftUVDwN+o7nuE
xFlBlQyhpFrJwCarlIj7LnLNp/kwjsgCnkZ7DakkhFUbQOr8d3AQefq0O/vH9UHt
xeE0hkz4wltsXSW5jryheLkWOmK1FFcrjGGv5JismU7cgOA2BbRixUEgd7aMPPOM
V6qMLU/qXvArTvhfY+0Vr+NAM2GS396AgbxlSoWerdojM0Ys4XAONlmOEReBXi2q
7gGxhlr861tAIjPxIYJkfFa2abWQFZSPXx3IsFUpuMjd543kKF1ERbJ14Lj66K29
3wRquvcCjzWrgdmvFPxRn/qnBpRle176LrxOSnL7lJNYCr4wtiBSd4Qr2MuCj7hQ
h9RGK/OQ7EM41Yc8/QAmXuKXn1HrJXGG9BY9Acv41an96q2nf0NV6+A5C1iHvV5I
V2ZBDp8WH8ieI29kU1oSAQsvs/NX6EBEWTeOPghNmys7C3XdHFNmZ+9W5maHH9F0
3RuiVdj4ZvHb8dljLtZzUwH+r9roIA6x3DBKff++hf9NBcuIbIk=
=piBa
-END PGP SIGNATURE-

Bug#886617: Please package version 2.1

[Daniel Leidert]

unblock 886617 by 936212
block  936212 by 886617
block 1003405 by 886617
retitle 886617 python-pmw: Please package version 2.1 and include Python 3 
support
thanks

Hi,

there is finally a bkchem version ported to python 3 and it has already been
packaged. However, it requires the update pf pmw to version 2.1
(https://pypi.org/project/Pmw-py3/).

This would close a lot of open bug reports, and maybe even allow the final
removal of python2.

Should we prepare an NMU?

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1003405: misses dependency on python3-pmw

[Daniel Leidert]

Source: bkchem
Version: 0.14.0~pre4+git20211228-1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

bkchem requires the pmw module. But it ships neither a dependency on
python3-pmw, nor has python3-pmw been uploaded to the archive yet.

There is a working module though:
https://pypi.org/project/Pmw-py3/

Regards, Daniel

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmHbFIQACgkQS80FZ8KW
0F2tNA/9Fzmqc73T5VYN11Nt6Le+DG/+XH6JiH6q5oKNiw6NglO3ZI2h47NcfKVn
c7R6LwINax/Dzb721IQJAeK6yQpnsMA+twAu0WCKbTsM7R1AgqP5qjE+8CBBwpby
zCRo/RhA0nJZO+nbzdCVF/we2+X318oR3j9BA9zjavWCFBwyz6WTySPvRCjm4KPX
vzhWJigbak32CF3D2eKFUUlLph/UcuIFLKMJtKrC3jWC/PpJX6hV/rUqRZzLjV3q
Zz5jPqidtHovGoq/UGq3bKoxVkuj+dfnsbjT0pLUb2zDn7ct8sGWnBJqyPnU53Cb
GD8mN1UWS2cLiiFzuySWns4O/z+bt44RJpakTd7vr1JZMKbzNP9WOE9AwsYMk3Aa
8YEzMwQ7736hINQnXBRdTHAUxR00SxOvzBLrXPeOVo7h99IZdZ7bmPD9A3bcXVoN
Ub9hu47LiUIODjyeu5zbmhR1asVA3BMGbE3KYcasFwTlVapRjGscyau1XEUuDGN9
D5wGT+EdHvoB8eGZJ8mDA6TaHz+VlRjFBuyG772oboCiYIYsFmucwPIe6CdR8rfn
2cR/gtvhDvxTdMrC+7AuOMRgSvHwg5yxct6Eh2OS3fVPIoUdgTL3hPHkXp+PCTnG
7m1hq/ciZPMm/7uPFe7puqgImVz5zPB0kNHgNoM3rx57s0gtmIE=
=qWAi
-END PGP SIGNATURE-

Bug#1003014: make_disc_trees.pl misdetects files missing for debootstrap when a proxy is used to retrieve packages - essentially making the installer ignore packages on the CDROM

[Daniel Leidert]

Hi Steve and a Happy New Year to you as well!

Am Donnerstag, dem 06.01.2022 um 11:27 + schrieb Steve McIntyre:

[..]
> Argh, OK. That's clearly the apt wrapper getting confused by the extra
> output from apt. I'm guessing you have extra environment config to set
> up the proxy here?

I run squid-deb-proxy and squid-deb-proxy-client locally, and the latter
installs /etc/apt/apt.conf.d/30autoproxy with the proxy configuration:

Acquire::http::ProxyAutoDetect 
"/usr/share/squid-deb-proxy-client/apt-avahi-discover";

And on this system I then use simple-cdd to build custom installer images.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1003015: Makefile creates a symlink testing/buster -> unstable/sid, while it should be testing/bookworm -> unstable/sid

[Daniel Leidert]

Package: debian-cd
Version: 3.1.35
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The Makefile contains this code:

# Make sure unstable/sid points to testing/buster, as there is no build
# rule for unstable/sid.
unstable-map:
$(Q)if [ ! -d $(BASEDIR)/data/sid ] ; then \
ln -s buster $(BASEDIR)/data/sid ; \
fi
$(Q)if [ ! -d $(BASEDIR)/tools/boot/sid ] ; then \
ln -s buster $(BASEDIR)/tools/boot/sid ; \
fi

This clearly needs to be updated to "bookworm".

Regards, Daniel



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

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

Versions of packages debian-cd depends on:
ii  apt2.3.13
ii  bc 1.07.1-3+b1
ii  bzip2  1.0.8-5
ii  cpp4:11.2.0-2
ii  curl   7.80.0-3
ii  dctrl-tools [grep-dctrl]   2.24-3+b1
ii  dpkg-dev   1.21.1
ii  genisoimage9:1.1.11-3.2
pn  libcompress-zlib-perl  
pn  libdigest-md5-perl 
ii  libdpkg-perl   1.21.1
ii  libfile-slurp-perl .32-1
ii  libyaml-libyaml-perl   0.83+ds-1
ii  lynx   2.9.0dev.10-1
ii  make   4.3-4.1
ii  perl [libdigest-sha-perl]  5.32.1-6
ii  tofrodos   1.7.13+ds-5
ii  wget   1.21.2-2+b1
ii  xorriso1.5.4-2

Versions of packages debian-cd recommends:
ii  dosfstools   4.2-1
ii  hfsutils 3.2.6-15
ii  isolinux 3:6.04~git20190206.bf6db5b4+dfsg1-3
ii  mtools   4.0.33-1+really4.0.32-1
ii  syslinux-common  3:6.04~git20190206.bf6db5b4+dfsg1-3

debian-cd suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmHR/eIACgkQS80FZ8KW
0F13VQ/+LLRXQP6vVxion6boTgg9LEEEnaUPHeprePLNoe5hA0S0wFnIyt3fU/w/
+/QVs4csEpZkLK397gAqR3/au5I/UGzW24lYwMwCtnRdZlwMeYnsRoQx1MPhWerb
oX53/kfbesUDT8TOT3TZnNtZg2d2wZlH7+KUA6BrHjlRNFLxYrh7CBYzQ14CxVz0
pCxtyub1RQKUFGhfJ/Sv+C70sStiooECpMoLPmQhvC0XWoZU0E+ZJPkUJTFzeIvJ
a3hclib2BNzFTTduPKG8SYgytfTyHKrkZx81J1s9955ZDEMxqoc+QnpuaNFqW2yJ
dqyJorijFYki5rnw4p70zzWtX3VDaQkVxtrDPmTmKa9V+HB57/Vw7nk8Jw0KnKxC
vdRWYH5WVobeNLdJ5rzgZRhlaeqf99DHFcUhTp7oK9kxheqxlnvKskGdCPvlG+2b
ocIx7okMxTWRQYXuzUW0x6U+oQq+2hrTW8Ia9894APNswdsbYw6aNkAydWs2WsOs
z/c1wE7M1WdDpYCTGLewIo6kdzaD5NXg4ACwZozJPRjjrdjWvEL/tX7QANbkHxbY
G1TRv8I+sWb2uEYRqPEhBX6BA555QJo6srYUuzyYROG/fvOX3moR3AIVY8N+RWiU
qKHt63FXf7ClQxY92tq3kpk+jmhIVEaGE2axZ+KBpx0dtcwny9s=
=eDGz
-END PGP SIGNATURE-

Bug#1003014: make_disc_trees.pl misdetects files missing for debootstrap when a proxy is used to retrieve packages - essentially making the installer ignore packages on the CDROM

[Daniel Leidert]

Package: debian-cd
Version: 3.1.35
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I was recently building custom images using simple-cdd, and for some reason the
installer was completely ignoring the packages shipped with the media. With
some digging I found the installer reporting:

cdrom-detect: Base system not installable from CD, requesting choose-mirror

With some more digging I found that make_disc_trees.pl was reporting:

5 files missing for debootstrap, not creating base_installable

But the relevant make_disc_tree.log file only contained this at the end:

Missing debootstrap-required I:
Missing debootstrap-required Using
Missing debootstrap-required auto-detected
Missing debootstrap-required proxy:
Missing debootstrap-required http://127.0.0.1:8000/

So actually there were no packages missing. Disabling the proxy then "fixed"
the issue. There were no more complaints by make_disc_trees.pl, and the
installer was using all the package put on the CD.

So we somehow need to ignore messages like the above, which do not indicate
packages missing.

Regards, Daniel



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

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

Versions of packages debian-cd depends on:
ii  apt2.3.13
ii  bc 1.07.1-3+b1
ii  bzip2  1.0.8-5
ii  cpp4:11.2.0-2
ii  curl   7.80.0-3
ii  dctrl-tools [grep-dctrl]   2.24-3+b1
ii  dpkg-dev   1.21.1
ii  genisoimage9:1.1.11-3.2
pn  libcompress-zlib-perl  
pn  libdigest-md5-perl 
ii  libdpkg-perl   1.21.1
ii  libfile-slurp-perl .32-1
ii  libyaml-libyaml-perl   0.83+ds-1
ii  lynx   2.9.0dev.10-1
ii  make   4.3-4.1
ii  perl [libdigest-sha-perl]  5.32.1-6
ii  tofrodos   1.7.13+ds-5
ii  wget   1.21.2-2+b1
ii  xorriso1.5.4-2

Versions of packages debian-cd recommends:
ii  dosfstools   4.2-1
ii  hfsutils 3.2.6-15
ii  isolinux 3:6.04~git20190206.bf6db5b4+dfsg1-3
ii  mtools   4.0.33-1+really4.0.32-1
ii  syslinux-common  3:6.04~git20190206.bf6db5b4+dfsg1-3

debian-cd suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmHR/WUACgkQS80FZ8KW
0F3rbBAAzjD2Il4Oqjxj69IBaJe5luKnFOX8L66WEY6yG05MKGzJfICWKuuATHyy
B4wVFRhslM+4LvxcIqsY+V5ruFKssy1QxHRxRC6tQZ2gpwlGn5UzaA7chrPJ/Mgc
mEY3zgsiw7HiK0Vf4zBmT21G3op1jzTpoEiey8IPbIhA8KVv3b8agkt/aqTyIUna
GlEoxnAqRvcRgtcM0Xkk1JhriPlU6IKSBsvr+0vmMoXzDYC0Yss2WtRP/R8zrmU/
3ae2yQSXNq8knclIftQQunufDounOgjyTr8WPk2iFVkb9HtEAi/EGbnkiR4i7ssm
EXOHh6lyw4SKlEC0Fz3jrvqBoESaDALUFus3vIpwvHZ9oEg9rY9sxU5JYIpgVM6g
lVrochACh0gifIiM8fL30FEYhkT1AtYh3AHH59SrzSS5rmUjyE/0GdZKRAwDFRvN
RbbcqArFuR3hQmC08GuMrktAQNciwtDpiMhY/IZEvv3uV7R9pKbO+Xw4g8QIGS8+
XutWfsIlJWojm1p2msAZZ39kvz7+6PjNaxhc+mxcd84fYADEOeXifsdIpJUs3aFT
yzRToheDrjFoB4ZP79atvE+WJ/e8CZJoKqgmvvoR2BjjIS5TYZHng2ugZihhqMks
hEAvVDs0AmHPvvJHcrvVIwuhjWQl+B9dxqH0DeGT7ypPfY7M4Jk=
=F62J
-END PGP SIGNATURE-

Bug#929700: [Debichem-devel] [help] pymol: Deprecation warning during startup

[Daniel Leidert]

Am Dienstag, dem 14.12.2021 um 21:17 +0100 schrieb Andreas Tille:
> Hi,
> 
> I think I've fixed the issue[1] and it works nicely at command line. 
> Unfortunately
> Salsa-CI[2] shows a new issue
> 
>    AttributeError: module 'importlib' has no attribute 'util'
> 
> which I do not understand at all since at command line there is the attribute
> 'util'.

importlib/util.py is part of libpython3.x-minimal, and while libpython3.10-
minimal gets installed, libpython3.9-minimal is not and it seems, python3.9 is
the default. So technically the error would be correct.

As I said in my other mail, maybe use

import importlib.util; ...

Not sure of that fixes your dependencies. You have to depend on the right
libpython3.x-minimal, it seems.

HTH Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1001329: [DRE-maint] Bug#1001329: rubocop: ftbfs with ruby-regexp-parser 2.1.1 in experimental

[Daniel Leidert]

Am Mittwoch, dem 08.12.2021 um 22:16 +0530 schrieb Pirate Praveen:
> Package: rubocop
> Version: 0.89.1+dfsg-1
> Severity: important
> 
> Build log attached. In roughly 2 weeks ruby-regexp-parser will be 
> uploaded to unstable.
> 
> There are many new upstream versions with regexp_parser dependency 
> updated so likely updating to new upstream versions should fix this.

Seems this is the relevant patch:
https://github.com/rubocop/rubocop/commit/9b90cae54d96b28ac25d81847f009e448965655f

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#997657: NMU

[Daniel Leidert]

Hi,

I've just uploaded an NMU to fix this issue. Please find attached the debdiff.
Please note that your Git repository is not in sync with the Debian archive. It
is missing version 3.0.0, this NMU applies to.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert
diff -Nru ruby-prawn-icon-3.0.0/debian/changelog ruby-prawn-icon-3.0.0/debian/changelog
--- ruby-prawn-icon-3.0.0/debian/changelog	2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/changelog	2021-12-07 11:14:30.0 +0100
@@ -1,3 +1,12 @@
+ruby-prawn-icon (3.0.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use gem installation layout, so the font files can be found in the
+expected path (closes: #997657).
+  * Enable tests and add ruby-pdf-inspector to build dependencies.
+
+ -- Daniel Leidert   Tue, 07 Dec 2021 11:14:30 +0100
+
 ruby-prawn-icon (3.0.0-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru ruby-prawn-icon-3.0.0/debian/control ruby-prawn-icon-3.0.0/debian/control
--- ruby-prawn-icon-3.0.0/debian/control	2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/control	2021-12-07 11:14:30.0 +0100
@@ -6,6 +6,7 @@
 Build-Depends: debhelper-compat (= 13),
gem2deb,
rake,
+   ruby-pdf-inspector,
ruby-prawn (<< 3.0.0),
ruby-prawn (>= 1.1.0),
ruby-rspec
@@ -20,8 +21,8 @@
 Package: ruby-prawn-icon
 Architecture: all
 XB-Ruby-Versions: ${ruby:Versions}
-Depends: ${ruby:Depends},
- ${misc:Depends}
+Depends: ${misc:Depends},
+ ${ruby:Depends}
 Description: Provides icon fonts for PrawnPDF
  Prawn::Icon provides various icon fonts including
  FontAwesome, PaymentFont and Foundation Icons
diff -Nru ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch
--- ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch	1970-01-01 01:00:00.0 +0100
+++ ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch	2021-12-07 11:14:30.0 +0100
@@ -0,0 +1,31 @@
+Author: Daniel Leidert
+Date: 2021-12-07
+Subject: Remove bundler and simplecov usage
+
+Forwarded: not-needed
+
+--- a/spec/spec_helper.rb
 b/spec/spec_helper.rb
+@@ -5,11 +5,11 @@
+ # This is free software. Please see the LICENSE and COPYING files for details.
+ #
+ #
+-require 'simplecov'
+-SimpleCov.start
++#require 'simplecov'
++#SimpleCov.start
+ 
+-require "bundler"
+-Bundler.setup
++#require "bundler"
++#Bundler.setup
+ 
+ require "prawn/icon"
+ require 'pdf/inspector'
+@@ -22,4 +22,4 @@
+ RSpec.configure do |config|
+   config.include PDFHelper
+   config.include ParserHelper
+-end
+\ No newline at end of file
++end
diff -Nru ruby-prawn-icon-3.0.0/debian/patches/series ruby-prawn-icon-3.0.0/debian/patches/series
--- ruby-prawn-icon-3.0.0/debian/patches/series	2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/patches/series	2021-12-07 11:14:30.0 +0100
@@ -1,2 +1,3 @@
 0001-Clear-executable-bit-on-data-fonts-pf.patch
-0002-Access-data-files-from-usr-share-ruby-prawn-icon.patch
+#0002-Access-data-files-from-usr-share-ruby-prawn-icon.patch
+0003-Remove-bundler-and-simplecov.patch
diff -Nru ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install
--- ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install	2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-data/fonts/[a-z]* /usr/share/ruby-prawn-icon/data/fonts/
diff -Nru ruby-prawn-icon-3.0.0/debian/ruby-tests.rake ruby-prawn-icon-3.0.0/debian/ruby-tests.rake
--- ruby-prawn-icon-3.0.0/debian/ruby-tests.rake	2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/ruby-tests.rake	2021-12-07 11:14:30.0 +0100
@@ -1,4 +1,5 @@
-task default: %w[test]
+require 'gem2deb/rake/spectask'
 
-task :test do
+Gem2Deb::Rake::RSpecTask.new do |spec|
+  spec.pattern = './spec/**/*_spec.rb'
 end
diff -Nru ruby-prawn-icon-3.0.0/debian/rules ruby-prawn-icon-3.0.0/debian/rules
--- ruby-prawn-icon-3.0.0/debian/rules	2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/rules	2021-12-07 11:09:32.0 +0100
@@ -5,5 +5,7 @@
 # Uncomment this to turn on verbose mode.
 export DH_VERBOSE=1
 
+export DH_RUBY = --gem-install
+
 %:
 	dh $@ --buildsystem=ruby --with ruby


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

Bug#997657: Problem is in ruby-prawn-icon

[Daniel Leidert]

Hi,

the problem is actually in ruby-prawn-icon in the files
/usr/lib/ruby/vendor_ruby/prawn/icon/font_data.rb and
/usr/lib/ruby/vendor_ruby/prawn/icon/configuration.rb.

In the first the path to the fonts relies on 

Icon.configuration.font_directory

which is defined in the second and leads to the non-existent directory
/usr/lib/ruby/data/fonts, whereas the fonts are actually in
/usr/share/ruby-prawn-icon/data/fonts/.

The quick fix might be to change to the gem installation layout. Otherwise the
font_directory default must be adjusted.

Reassigning to ruby-prawn-icon.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1001129: Ruby 3.0: puppet/util.rb:469:in `uri_encode': undefined method `escape' for URI:Module (NoMethodError)

[Daniel Leidert]

Package: puppet
Version: 5.5.22-2
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The version is not ruby 3.0 compatible:

ruby3.0 -e "require 'puppet'"
/usr/lib/ruby/vendor_ruby/puppet/util.rb:469:in `uri_encode': undefined method 
`escape' for URI:Module (NoMethodError)
from /usr/lib/ruby/vendor_ruby/puppet/util.rb:337:in `path_to_uri'
from /usr/lib/ruby/vendor_ruby/puppet/pops/model/ast.rb:4863:in 
`register_pcore_types'
from /usr/lib/ruby/vendor_ruby/puppet/pops.rb:119:in `'
from /usr/lib/ruby/vendor_ruby/puppet/pops.rb:1:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /usr/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:8:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /usr/lib/ruby/vendor_ruby/puppet/parser.rb:6:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /usr/lib/ruby/vendor_ruby/puppet.rb:302:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from -e:1:in `'

I'm intending to do a quick NMU to fix this.

Regards, Daniel



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

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

Versions of packages puppet depends on:
ii  adduser  3.118
ii  facter   3.14.12-1.1
ii  hiera3.2.0-2.1
ii  init-system-helpers  1.60
ii  lsb-base 11.1.0
ii  ruby 1:2.7.6
ii  ruby-augeas  1:0.5.0-3+b9
ii  ruby-deep-merge  1.1.1-1
ii  ruby-shadow  2.5.0+gh-1+b1

Versions of packages puppet recommends:
ii  debconf-utils  1.5.79
ii  lsb-release11.1.0
pn  ruby-selinux   

Versions of packages puppet suggests:
pn  ruby-hocon  
pn  ruby-rrd

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGsALEACgkQS80FZ8KW
0F1nHQ/6AyVaWCMDdPHi0AyhhQZiEISZP0GYNqdrnD/LYF9SdZ2PRlXxQrQfJ7RI
F226bh4sRgzY/pcgfeUmiizaDfCyKxtGrvyjPqOvnoFACDRHDJm/rhjybdsTDCF7
MnHCNjIEic6qoPBqQmG20W15pshRzxbnSojTrZ+4QpHicn7shGYe2EmEJW2ZD6J3
Wsf/YB0Ny7AXKjZzWBqz3TFbBWObo47LC7XiutuirmjM7xe5f+QB5VtGiBk4448f
XgWIPU9LwyAS9uUYWbXd+jxSVZ/92YoR83KyfGTd861Gj042EFXvu/zHRYru+FGj
zM/H2PoQRudDUVlsVX4LXjKdaPJWxYjqhFOYeESRh86paZJFTzCp2VFdCMnCjAyo
y42hH4SFjYsZhysNyDjEMwwSBKjQguKKqkRCjdJ1PeFYWc8CEQwlgAZLtLGSFdPA
d22BplnTtZHT3AEweXUNWDvjfmDjAgObe85u/p5YQgAYldrj5f0C9BoWHpJ02P5I
6pi2KzWDgApuVk8OEbMrgoxsKnGxaXKEGRqoYxYZe8MWvDRJ8vlwTgXqZk3Us0LB
taAXdHCdzvQ3NxYT6JgWkOeBwcfKY14sVzPfeKE7vzB/Ib/HxqdR4qyAdkWqt2V0
ujonrXF3NDPL5ZAi2QIkb/7v42p3B1nc2PeJJ2z/SoIbq1nfqh8=
=CMGz
-END PGP SIGNATURE-

Bug#978500: Version 4 ships a gemspec file

[Daniel Leidert]

In Version 4 there is a gemspec file.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1001085: ITP: ruby-thread-local -- provide a class-level mixin to make thread local state easy

[Daniel Leidert]

Package: wnpp
Severity: wishlist
Owner: Daniel Leidert 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-r...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: ruby-thread-local
  Version : 1.1.0
  Upstream Author : Samuel Williams
* URL : https://github.com/socketry/thread-local
* License : MIT/X
  Programming Lang: Ruby
  Description : provide a class-level mixin to make thread local state easy

This gem provides a simple high level interface for per-class thread locals,
and it implements a standard interface for "shared global state". Using this
implementation avoids reinventing thread-local semantics in your own code.
.
Global variables are often not thread-safe and encourage poor programming
style. In many cases it is desirable to have thread-local state, but
implementing this directly in Ruby is unpleasant. This gem provides a
best-practice wrapper which can extend existing classes to provide per-thread
instances.
.
Conceptually, a thread is a container for application state. This works well
when servers consider applications to be isolated on a per-thread basis, but
this isn't always the case:


This is a new dependency of ruby-async-http and necessary to update this
package to fix #995354.


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGqlgoACgkQS80FZ8KW
0F0vvxAAgy1bTR4g7pHBb8KqIwGRcouUYzFfSakiEqflJkxxHBOtbq4iHBOfWx/c
RKAl0CnFeEd+XVAMCvPIOziTlYLUJOubzIPRIRkHQYEas19mX5/LbT1SFgeQPuL5
iRaaW45oGiUOCLdGWniuQTE4wP6VjJjowU23YWqwdLCk+hQSUZmBrpJtA+IZmVSR
2tOL7vkGAIR1FhRxppy85D+Q1U/kgNUh8LYRaNHWvgQoie4u2dyWro6+UuYpvNRN
fTNF+oLqPUqcYYVq7l5rbWUDW+E2VgWyRE9aUKomJwVSgK+N8Yyc25aPhppuzapK
MjLpuRNgAo0fpAw+J0Bh4Bu+Ly75FUvhqPJkxpgquYJxtJIQVkwpPf4Td1hDI+Ht
0k56r+GJ55BPCofUkwecbXNPt5bek4s881Pz1TNsXjd9R6omgNQFp3eXb/frAhMv
TbtTyONoNGSruLtXT/4yr5d4Ks0HkfEy+vtVYKxsmsChkLnagEsF8OSbi/cpfRd0
1uG40RQGq+heLzjnpOS/1llrw3OlpqvglMCQz6KFooK+LQh83WuHl37j/zcJVYDe
x+6f/rc8Hl62gTaEhnrD1yblfxHOQa5ebaT3nsU1Hz5VoI+pf5D3CpTX4F0uYypk
vXR4xHifz6NGN0+Bo8Sw5NbqWnpD+zPoVj7XT7t0+BzLkB688ng=
=PCUC
-END PGP SIGNATURE-

Bug#1001022: ruby-pathutil: Not Ruby 3.0 compatible due to kwargs issues

[Daniel Leidert]

Package: ruby-pathutil
Version: 0.16.1-1.1
Severity: serious
Tags: patch upstream bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

During tests to fix Jekyll 3 it was discovered, that some issues are caused by
ruby-pathutil. There is a new version of this gem available, but this patch:

https://github.com/envygeeks/pathutil/pull/5/files

will be necessary as well to make it Ruby 3.0 compatible.

Regards, Daniel


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

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

Versions of packages ruby-pathutil depends on:
ii  ruby   1:2.7.6
ii  ruby-forwardable-extended  2.6.0-1.1

ruby-pathutil recommends no packages.

ruby-pathutil suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGpH9AACgkQS80FZ8KW
0F0Quw//TSe8FYttG0mg/0uoc+k2t4gLqet8o/38C2mHwJI3aLDD8WiRvjfmnEaX
7Kvlyhtbz+d3Or1iSAcMU3IWXXeBdv/0M9KqQ9LvSJG7C91SrkUOkpPiLj5ungeK
1IgG+FERjHCvYWeesnMDePn68yqEG10ULeHqyS6qjjitTCvUELV0MV/vg1wOGL+8
6w1uz00/3smgpMivdvPp+AsVGwBGW/q3MzsZ2vjg0JTKLbpDtB7pivFk35vY8CzB
GJK+qzoMIY87IrF/W1HvlMwh/08FP+CjqT6d/6qc11nQcCKBEUbrI5GQg1fZHnNR
13uCWXovjLA5DLf0o7kobpy8/TKao8wnJyRv69z7YsLrMjIEJJW9/+sw8K+86/en
VNRiYP81i9weTd+KEadkyV7ZUtW8OfCF7zwO2Yqo4/og7ILIixA34anttwZHjCGp
ocVPSmvBBfkeG2vi0qUDsaXwFMNjYMpgQ/jU5tU2zo9e4Tc9l0YD1YdrByLBtt8A
kzJnHh7UoAVXZhzAv+vsuHw6wpuQdPEmVdK6Ff0tU2VSSAnwYeG9paGwM1uBt2va
sbuLHkrC2YK25wsEdg63ZD+WuKJ0BKyFXfkOeCX3719J5Rtvh2s+iFHH3pNiFNxY
1/4ndoVPY2eTshJPdq0ZSGhyecPDtNVWCQbBRdwMnibHvi3mJQE=
=Rkmc
-END PGP SIGNATURE-

Bug#995353: Info

[Daniel Leidert]

We need to restart the autopkgtest runs as soon as the fixed version of ruby-
rspec-memory hits Testing.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#995354: Requires to package ruby-thread-local

[Daniel Leidert]

Fixing this issue requires to update the gem version to 0.56.x. However in this
version a new dependency was added on thread-local:
https://github.com/socketry/thread-local

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#996451: GSL and ruby-gsl

[Daniel Leidert]

Hi,

I just had a look at ruby-gsl. The package builds and tests fine with the GSL
version is was built with. However, the tests break when the version built
against 2.7 is run with GSL 2.6 and vice-versa. Maybe this is also due to the
ABI breakage (#993324).

IMHO you could add a

Breaks: ruby-gsl (<< 2.1.0.3+dfsg1-4~)

to help the transition. or we wait and rebuild as soon as you upload your
latest changes to unstable.

Regards, Daniel


-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#996294: Change in webrick 1.7.0 is causing a problem with the tests in Ruby 2.7 (at least)

[Daniel Leidert]

I did some debugging on the issue reported that the tests fail after adding
ruby-webrick 1.7.0 to b-d for Ruby 3.0.

The problem is in parse_header() (lib/httpclient/session.rb) in the line

828 line = socket.gets("\n")

With webrick 1.7.0 it stalls here. This is caused by this small change in
webrick:

https://github.com/ruby/webrick/commit/069e9b1908aad3a30a0dcf67b6d3bb13c3216d2c

If I revert this, the tests no longer timeout and succeed under Ruby 2.7.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1000729: ruby-hamster FTBFS caused by ruby-rbtree and ruby-sorted-set

[Daniel Leidert]

Source: ruby-sorted-set
Version: 1.0.3-2
Severity: serious
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Tags: help


After doing some debugging on the ruby-hamster FTBFS, the problem seems to be
ruby-btree and ruby-sorted-set breaking the tests. In a pure Ruby 2.7
environment, this is true:

SortedSet.new([1,3,2]).eql?(SortedSet.new([1,2,3])) => true

Installing ruby-rbtree, and the same matcher becomes false:

SortedSet.new([1,3,2]).eql?(SortedSet.new([1,2,3])) => false

Now adding ruby-sorted-set in the mix for the Ruby3.0 transition, which depends
on ruby-rbtree, more tests fail. This is causing ruby-hamster's tests to fail.

This bug report is to indicate that this blocks the ruby-hamster fix.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#996350: Problem can be tracked down to ruby-rr

[Daniel Leidert]

I was examining the problem. The problem seems to be ruby-rr 3.x. rabl actually
requires rr 1.x, and with this version it works. I verified this by building
against ruby-rr from Stable. But with ruby-rr 3.x in Testing/Unstable it fails.

I don't have a fix for that.
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1000623: The tests hide a programming bug: NameError: uninitialized constant I18n::Inflector::Rails::BadInflectionKind

[Daniel Leidert]

Source: ruby-i18n-inflector-rails
Version: 1.0.7-4.1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

While fixing the package for the Ruby 3.0 and Rails 6.1 transition, I
discovered that the tests actually hide a bug in the code. Several tests
throw:

  NameError: uninitialized constant I18n::Inflector::Rails::BadInflectionKind

and indeed, this class is called twice via

  I18n::Inflector::Rails::BadInflectionKind.new()

but I cannot find any definiton. The i18n-inflector gem contains a
I18n::BadInflectionKind class, but it requires to pass the locale as well,
which is not available in the no_inflection_method_for() method.

This looks like a genuine bug and the upstream project hasn't seen any
development since 2013. The only package using this gem is diaspora.

Regards, Daniel


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

Kernel: Linux 5.14.0-4-amd64 (SMP w/8 CPU threads)
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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGgL9MACgkQS80FZ8KW
0F15bw//f8p2/V2FElGchMN7QUt1JsswDs4NYDOXjGf9OIAA62VQCzP3a5izgYgb
9XFoSyh8DzU1CVXH908+kwHkhbQfVfaQSdj0IopdztCiRztlHgbsYQXLf6meQqpT
9OHBTL4HeUFaObI915IR1F9YmHfL7c9Pu0zwxTjkGwEBmX/5iAtR7NE6YELL2fBT
uvOdqKAcnbc+kf8hbWbVBC/efcx+I7ajdax77q7QYrTnLjjQsdwys878ZxrkYg0p
Tbrm2YE01P3t20PLSIDrsIVNrdA96tru6IyFaqnZZARI/WIi1b8MKryYrPA1/qjd
SczUOFZbgslaWN3nc7RS7ybA5bbAEhF6H3ZORtlEvcGvKLnCa7LKPOqwt3JEh5G+
97XJD/vLOzn26rco2LhuPU35B8Ls1WWT3TPQPr/AdLRdE4jzHepAioy9V2d1EXI3
FmT6KxD4QoJ8e0OcVXr50Abz+Ftmoi4VjEZNJyHV5Nr+icIUFwpoFWPuMJ4FTxyQ
VMGYBYct5Z6C/HiKPn554+BlmhGp9FD7LJIqmHv+kcHmJLdFGHxfTS1cdeZ7uNFc
B9S3aZLG3QBZPL1T2BKsk+D7YOOxGF8ng4AWKqEzxW56KfoGbvF/TllJwXq0VxOm
c/x/1nVsMOrWRaDveDWm03UpJF5o0930G63lOLXHmWEUBYlNNLM=
=a9YU
-END PGP SIGNATURE-

Bug#911735: pdfwalker unusable due to ruby-gtk2 module issue

[Daniel Leidert]

There is currently a problem with origami caused by ruby-gtk2 (#990443), a gem
which has been deprecated and is likely to vanish due to the Gtk2 removal in
Debian.

This problem (#990443), for which we do not have a solution at the moment,
prevents pdfwalker from starting, even after fixing the other bugs.

The project itself seems unmaintained for some years now. If it is not ported
to Gtk3 soon, it has no future in Debian.
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#990443: [DRE-maint] Bug#990443: Issue seems to be ruby-gtk2

[Daniel Leidert]

Am Donnerstag, dem 25.11.2021 um 22:15 +0100 schrieb Daniel Leidert:
> I did some debugging with this issue and it actually seems to be caused by
> ruby-gtk2. It is easy to reproduce. In irb:
> 
> require 'gtk2'
> include Gtk
> require 'openssl'
> 
> => crash (happens when openssl loads openssl.so):

Correkt traceback:

14: from test.rb:3:in `'
13: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
12: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
11: from /usr/lib/ruby/2.7.0/openssl.rb:20:in `'
10: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 9: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 8: from /usr/lib/ruby/2.7.0/openssl/ssl.rb:15:in `'
 7: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 6: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 5: from /usr/lib/ruby/2.7.0/ipaddr.rb:19:in `'
 4: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 3: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 2: from /usr/lib/ruby/2.7.0/socket.rb:4:in `'
 1: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': 
superclass mismatch for class Socket (TypeError)


-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#990443: Issue seems to be ruby-gtk2

[Daniel Leidert]

I did some debugging with this issue and it actually seems to be caused by
ruby-gtk2. It is easy to reproduce. In irb:

require 'gtk2'
include Gtk
require 'openssl'

=> crash (happens when openssl loads openssl.so):

Traceback (most recent call last):
28: from /usr/bin/pdfwalker:25:in `'
27: from /usr/bin/pdfwalker:25:in `load'
26: from 
/usr/share/rubygems-integration/all/gems/origami-2.0.4/bin/pdfwalker:4:in `'
25: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
24: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
23: from /usr/share/origami/gui/walker.rb:31:in `'
22: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
21: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
20: from 
/usr/share/rubygems-integration/all/gems/origami-2.0.4/lib/origami.rb:41:in 
`'
19: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
18: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
17: from 
/usr/share/rubygems-integration/all/gems/origami-2.0.4/lib/origami/pdf.rb:49:in 
`'
16: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
15: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
14: from 
/usr/share/rubygems-integration/all/gems/origami-2.0.4/lib/origami/encryption.rb:21:in
 `'
13: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
12: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
11: from /usr/lib/ruby/2.7.0/openssl.rb:20:in `'
10: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 9: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 8: from /usr/lib/ruby/2.7.0/openssl/ssl.rb:15:in `'
 7: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 6: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 5: from /usr/lib/ruby/2.7.0/ipaddr.rb:19:in `'
 4: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 3: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 2: from /usr/lib/ruby/2.7.0/socket.rb:4:in `'
 1: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': 
superclass mismatch for class Socket (TypeError)

That's not a bug in origami.

I'll have a look at ruby-gtk2. However, I guess as soon as Gtk2 vanishes from
Debian, pdfwalker will become dysfunctional.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#964607: Massive update necessary

[Daniel Leidert]

This gem is out-of-date. Upstream is at 3.2.2, which requires packaging for
google-cloud-translate-v2 and google-cloud-translate-v3 and updating google-
cloud-core to >= 1.6. The tests require packageing google-style.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#996319: Builds fine

[Daniel Leidert]

The package builds and tests without errors.

There errors show problems with file recognition and also errors that files are
not found. It actually looks weird and if there were problems with /tmp.

Let's wait and see if this re-appears.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1000463: Please re-enable TLS support (even if only for a subset of architectures)

[Daniel Leidert]

Package: memcached
Version: 1.6.12+dfsg-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

during debugging some test failures with a Ruby gem we discovered that
memcached is built without TLS support. Now it seems you had it enabled, but
disabled it completely with one of your recent commits. However, the changelog
and commit message are not verbose about the why. I built memcached on my amd64
machine and it builds and tests just fine. The commit and changelog messages
also imply that TLS support may only be a problem for a subset of
architectures.

Would you be willing to re-enable TLS support? Maybe just for a subset of
architectures?

Regards, Daniel



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

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

Versions of packages memcached depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libc62.32-4
ii  libevent-2.1-7   2.1.12-stable-1
ii  libsasl2-2   2.1.27+dfsg2-2
ii  libssl1.11.1.1l-1
ii  lsb-base 11.1.0
ii  perl 5.32.1-6

memcached recommends no packages.

Versions of packages memcached suggests:
pn  libanyevent-perl 
pn  libcache-memcached-perl  
pn  libmemcached 
ii  libterm-readkey-perl 2.38-1+b2
ii  libyaml-perl 1.30-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGdGDcACgkQS80FZ8KW
0F2Hlw//dSX36rlVR0XwOSW7NFvP1jHMf86LHA8N/Oj36EJ5o5uqxhlDQyHE2GwD
wUT7xXph0sGNis7OiZTO1ud9cxYGIi5Weknan+lmIYzoZL090FY/TfJ781tmGndz
clEILfDe7YXloU4sUkHMie/KZU3Ltg2wBQhCAevdh32mBuquo+3/9q+IJZiNgtcz
cbWhQ7mlkW8r3mFrNGI4eD4V3c7aqjc6r/hJPPAQuKBO7nhggIwPLKuUwtfmFGw9
GwcygUFgLz8pScmuIEsVpdoa3iTsBw2pS3tY1rBWqFkZm+RBynphG1rTKcDIduVS
qgrgW5N5tu2abfpwbTtqdFDzl0LGuGX+F2jlhzPCeWVgVTuvaJ85Z2iMT58jqmBj
WjHoL1LxmYJ9ku+08CeMdkJd+6eFPRnk/mWAmRKYT87Pm7Rt+eVXRXGbLlcZsv9w
VvcknlYeCnF5IGCezYfAU/ARcsrDRVNyTQNya3dvU80ImAFgxGB0Y6JHQktQ5Hll
PZyszfIrch47PrikpaGgWfARuHjz+75YsgxIKD4lYlvxG8VZnkd+MQY9BuO/cMrR
18YBNT3AHeDhDfpOrv7iT/IsJ+PkzNctJAtpaPzcZZDAAgumCwnFqsGMzfh0bb7n
d9/dq4aTxYTGEBnla9mWpDnEVEo9tAvB0RjxgRufvrJr74WSme0=
=muJy
-END PGP SIGNATURE-

Bug#996380: Explanation

[Daniel Leidert]

It seems here is an explanation of the problem:
https://github.com/paolobrasolin/jekyll-antex/issues/16

I cannot find any patches so far.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#996212: Fix require dalli 3.x

[Daniel Leidert]

After having a look at the issue, the 2.x series is not compatible with Rails
6.1. We need to upload dalli 3.x instead.

https://github.com/petergoldstein/dalli/issues/771

I checked and the 3.x series builds fine (except for one test which requires
network access and must be disabled).

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#996297: Ruby 3 freezes Ranges by default

[Daniel Leidert]

The problem is caused by Ruby 3 freezing Ranges by default [1,2]. Thus the
tests try to handle already frozen objects and some code is not working as
well. I've forwarded the problem to upstream, but they have been inactive for
some time.

[1] https://bugs.ruby-lang.org/issues/15504
[2] https://github.com/ruby/ruby/pull/3583/files
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1000347: RM: ruby-factory-girl-rails -- ROM; obsolete, unused

[Daniel Leidert]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: debian-r...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As explained for ruby-factory-girl, this package is obsolete because it has
been renamed in the past and the successor has already been packaged. It is
unused in the archive.

Regards, Daniel

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGawEsACgkQS80FZ8KW
0F16Kg//ayNMkbw5Bno1rGqug5fDgbq2T5gSkGrw4p2fbTenXJ637h+p/kEtDQYQ
HKUDwhFvB0sEbOuHsdifag2z3DEayj7aj3I2ro80as3c+6DvWnEc+tzoJZbKP0Sq
T4f0d0l9AXTlJ6aKeMjv7wB6NCtZFQ88MvFPprEgLY+9VQQiy1uL7wGQzNCfPaUe
HDxowP0eUYm2OufKOwBHToHNpcsw3slV2y8ninHPMQi+Mk+/YqrL0fGiVY6o2i02
tUjfUGzalNU9//b6j33pCJSarsl0asU0p2kD9hbZR4RN1ZLtqvaO/IIwmOXkwzLE
4Hw3FHTGLPINA4+JTn3bBl+j7LAYr2sDynQYhSDzT8i4zGeKLN9AMRNY7EaMr46y
ms5QtWnSEmAet2urWA4GfoTNK8I6NCK3fFmZolFv1vw+CCgJ5RcXddQ1O1WlpK+V
wdIcNgN9IRz65r+FrgXjpR4r9pd6O8cQEZDxJTePO1noiLl2N/547ei/ACo8xb9q
E9t/9WcoJlMvaRd3nwrsb6bQ0nu+Pb11t3WXCRqW3CLUWk5VJwi+mGPO5eZOLhc6
8sKJbSlkIKIjYDVjaAMcgNBmCZsn6wl4YS5Iy4Gf9yCgjkqmIneqF0Yw9LYpnCzz
g0RLOz5BFMkJEniALR7dMWEVVQafF3gOQ7JW1D6eNJymdbyPkLY=
=bnWt
-END PGP SIGNATURE-

Bug#1000346: RM: ruby-factory-girl -- ROM; obsolete, unused, RC-buggy

[Daniel Leidert]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: debian-r...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

This gem has been renamed to ruby-factory-bot quite some time ago, which we
have packaged already. It is therefor obsolete. It is used by
ruby-factory-girl-rails for which another RM request will be sent. Otherwise
it is unsued in unstable (and will be in testing as soon as
ruby-activerecord-import migrates).

Regards, Daniel

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGav+AACgkQS80FZ8KW
0F1/HxAAsiEWmq9k+ML4sNnMo5EOQ9S5xsoLtruj//nnxEe7hKWaALwGew1286fp
vAFAPe0Wz5Hkqkgo+38iVHLkMYhRHX+q1P/SIh7ZKZxApQqnmKK4oZ+HELVPwuaK
cqTJgzbx4xYBnMFLU7V4FkhGVQvMbdFbSt1nJTmZAzALuljRCE3K1m2SrpCrKtZw
OeqS6I3D0jJt7px2rLgyZmFflfYIxAHp9TiOfelvWOI8rodgETW9NvCme0Rqef4q
7ZXomNKoMdn4H2AsXjwuLQP3my43KlNDTJLabBRtuygMpcuGvCtJ+2ddJh3/Dnhk
3VyzcA5D8N2WjjEYxK5l5Z0L1Mtu7fgW3DFjxozW5CALCOEuE1+TtolxaWR8CEBY
b2YQq4nPu0nlyxqgDZW8tA6hDDcy96xxgvqfdsyXGIdfdRI5fyTqQAJcTUu/QyS7
zFPkUuRleOEmF278UvaSHnMh3SeiCtRjkIgXr8tO6r9jA9h6Cfz4GKFX/DGc56vH
/88qeWRDAa3LGV5dDpCEWbxez/HViS07XL7jfLWBgcu2fk0+SjaAK8OQOq40OfX4
+ap8TrgJe3jl6HPr6PN3RLTbwV2770Ckcr68pLpnBtr8uN1m0ft1vjwCD4Eadp+3
KMzzJ9D7bWmFBNhlMXO0tdWPsEPHgB3pwxjnaYGlXxrpFcaII8s=
=ePXv
-END PGP SIGNATURE-

Bug#1000345: RM: ruby-cocaine -- ROM; archived upstream, obsolete, unused

[Daniel Leidert]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: debian-r...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

This gem has been renamed to terrapin almost 4 years ago and we have packaged
terrapin already, so the replacemant has been available for quite some time.
ruby-cocaine is obsolete, has no reverse dependencies and popcon indicates low
usage as well. Please remove it.

Regards, Daniel

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGavuEACgkQS80FZ8KW
0F3gwQ//SgqIxhI2+foN16ypL4EBgZWMhGGm7eAiBwEiUL+9z7f/Mn0nZKKSIFtz
9Zfg20CakMOqekgocRwVMtoNQ6VjLH0J47/o/8p5H/SxSKtlosUGLHQzNmXUh9m/
tZN65M86HBXOL+MeACSDsqg1wAerQdCkl2PQiggpUHZeX3l/GmOjDISf7ukGOkSP
scn+mTGEup90F/UHyuJBjhgdWFCqBJIQN1Cfm7G4MacnpUgyH1CelYE7vnGbWbIp
+yFW3XcaQEU42gQCj15xc4xho51OxGuo9TpROp8z/rcgOwzpbY46zfa5nggug7Fn
cQy2y/7hCvl49CREAuMKX8P3XglXdn1ooG/o3AQVbwMl7ibwLv3v2PJSeK2r+ewV
ZyJ8qTjt5vNBx8HOQHFd98pFdZZ/cCEt+3sztBVq2AkEpqBsP/sWx2sgs/wBVvF5
ca1VlOgWYYom2BUtwndVyurOytIjfIWc27jmpHVjPx1pDH7G0kbMlInusfWnyZpl
ieJ18cB6GCi1yxqbXTuEz7ApxqbbFT5lMtu1eWQCSuG2EBHBJ8pgfTvTK2l0G82K
bOohcF1kItF/MLQzC43okueLB4wME8+xAEOJvCe/5X8aTJxmyGzxc4Iojw2lOYc/
akoe9KTxlk6jzsYPrGbW4DWz38xXBVK6UcQgN9IGzkj4lnZHJlU=
=kC8g
-END PGP SIGNATURE-

Bug#996117: Update after uploading Rails 6.1

[Daniel Leidert]

Am Samstag, dem 20.11.2021 um 00:18 +0100 schrieb Daniel Leidert:
> With Rails 6.1 the package now fails to build with Ruby 2.7 and a bunch of
> errors like this:
> 
> Failure:
> ActionController::Serialization::ImplicitSerializerTest#test_render_array_using
> _custom_root
> [/<>/test/action_controller/serialization_test.rb:186]:
> --- expected
> +++ actual
> @@ -1 +1 @@
> -"application/json"
> +"application/json; charset=utf-8"
> 
> 
> rails test /<>/test/action_controller/serialization_test.rb:181
> 

I think that this commit was supposed to fix this test issue:
https://github.com/rails-api/active_model_serializers/commit/55a6b23cd84395029aa92605f8aae73f37f57c4a

However, it doesn't work and this issue says that it has a different meaning:
https://github.com/rails/rails/issues/40376

It is possible that this problem is unsolved at the moment.

-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#996117: Update after uploading Rails 6.1

[Daniel Leidert]

With Rails 6.1 the package now fails to build with Ruby 2.7 and a bunch of
errors like this:

Failure:
ActionController::Serialization::ImplicitSerializerTest#test_render_array_using_custom_root
 [/<>/test/action_controller/serialization_test.rb:186]:
--- expected
+++ actual
@@ -1 +1 @@
-"application/json"
+"application/json; charset=utf-8"


rails test /<>/test/action_controller/serialization_test.rb:181


-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#996369: Info

[Daniel Leidert]

This issue seems to be caused by rails. The issue is gone when using rails
6.1.4 from experimental.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#998448: Rename source and binary version to ruy-ruby-magic

[Daniel Leidert]

Package: ruby-ruby-file-magic
Version: 0.5.0-1
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I think the package names, both source and binary, are not correct anymore and
need to be changed. According to the gemspec it should probably be
ruby-ruby-magic.

Regards, Daniel



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

Kernel: Linux 5.14.0-3-amd64 (SMP w/8 CPU threads)
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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGDv1QACgkQS80FZ8KW
0F3X/A//eegtEITlGXWGKY1Kt3no4u5mw2t4EHcUVfKnIzI9jBd5QyDc+Y3J3WnU
Wkf8Ph73Hgy/IZ+WYoMywS+TamjzWEqPrJm3LRYBqyAgI/MIBfbP2rbNk7X3t0be
tw5YWFeAuqnnzFvVZ5TbJ6zO/UfREvnfrV2qb1+cXjHP5x3P7w/fGfXeoJ5vCf/q
pI/NTE4EopRgOVM0npl8x0Dumjal6N/YtzP/MZFPh7+yZGyW2C0/dGcjBjpd0NsI
6irWBxLgvtzZyumx/+/39h9l2zFDNiPlQJH08HRwJMdAwx7IJnr1rtV8ZlSM/Cs6
H7fpKRLnz5alHwQRTh1HJNxe5bJR/rdCFqfmrxhHY8SEdTmdcZTm91m+nE2D58wI
LFnSm7DNVntk2dojhljvAzHDPpa2yfyGl6opfP7/rkZaVztWlX1gDuVkqx+IvMpY
wB+BDBY5DjUep9IloIeMlXGYhWISyEt/a3tbNr2CJKxEmYFK2UdX0m/sHBprRbNm
u4VqDuZY9hucGbOeihO45C5zgNNiOxuizlTDjuvwyoVwCp0LKkbEeJutMtHJuuAn
ZCl8mAOmVE91cIVtkUAE8vRBpKlyChMLF6uqDrG0vJUqLlNoVa7OASfY65ZNZcOQ
dLBiHhGQwqykPF4r3GspefKU9i4dvsIoav/ESERDefCN95pPz0Y=
=HIBh
-END PGP SIGNATURE-

Bug#996117: Bug is actually in ruby-activesupport

[Daniel Leidert]

clone 996117 -1
severity -1 serious
retitle -1 ArgumentError: wrong number of arguments (given 2, expected 3) 
caused by lib/active_support/cache.rb:330
block 996117 by -1
thanks

I had a look at the issue. It actually seems that ruby-activesupport, to which
the following files belong, is to blame and incompatible with Ruby 3:

> ArgumentError: wrong number of arguments (given 2, expected 3)
> 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/cache.rb:710:in
>  `get_entry_value'
> 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/cache.rb:330:in
>  `fetch'

The error is actually caused when the options argument to the get_entry_value()
function is empty ('{}'). This doesn't fail with Ruby 2.7, but it fails with
Ruby 3 (possibly due to the changes of handling keyword and positional
arguments). 

This seems to have been fixed in RC1 of version 6.1.0 and therefor in version
6.1.4 as well.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#998390: buster-pu: package ruby-activeldap/5.2.2-2+deb10u1

[Daniel Leidert]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

There is an open bug report about ruby-activeldap missing a dependency on
ruby-builder. This issue is only present in Buster and the fix is quite easy.
Please consider this minor update.

https://bugs.debian.org/982522

[ Impact ]
The user has to manually install ruby-builder to be able to use
ruby-activeldap or hope another package will pull it in.

[ Tests ]
This update adds only a dependency. It doesn't change the behavior. The package
did not have the tests enabled at this point (was done in 5.2.4-1). I could
enable the tests, but it will make the diff significantly larger because it
requires applying more of the package changes done in version 5.2.4-1. I
actually don't see any benefit here.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
The only change is that ruby-builder was added to the dependency list.

Regards, Daniel

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGCmnkACgkQS80FZ8KW
0F2JxxAAq2WraAFBeXlkpzED0MQseNgOzAG9oGEKgoFauzweMbYx4V4yIHuLYIgj
xQC5/2xQJwXx11/v9yr+uyq4/7g3r66oRWk4k/pG2YhS0PYV5QeM7dUFRWTadFI+
+ZtL17AA4+Z9uwVouH2gdSvGT/f3hP92iVYJtKSxY7KZMoolHqfasHrdHArwx/ZS
u1rmrWHZdonp0FCFqlrc1yUEkYhXtqBSSHQQJRjyyTBeCVMwHBkaJ1UMHpER+CbV
9ZEque/cC2KDAc4opfy/YYECYrZhTDLQal4YZlQvEtxIeqOKtdqZ3EAuZSIEZP0O
60ntpPSZlSJfOZ9t/ewKKnopojVJDfbp1JzTOw7BMFGvUmUkqheVu1ntR270UovR
01oy0Dj5QsTphOmwYvLp+LECCWpcWandjoYPYRSmSSsoh/C+PXjUBhQW2oyxeOjo
Zde0yYWn6F51/dZtG32Gond4A60O6zsNfCTLHaf/ZlGUjnFxhuEH+5IDSfMRDNC5
fSW9HmH5mh4SFcgvz3neRPY9m3JpZu/Us6fxmtJVgVEAapjdX+tpJmJFxpTu2EKF
j87APMe8cEFiDeezNQRlkJzTHOQlVLsiJrOJ3DcE0Kqvz0LNSlld0ZRaI0sX4YRP
2akbvKPeXpwsdjUGshk1VS1aWfhzLtC9i+q/pMl8ORkVxyENAl8=
=JmsM
-END PGP SIGNATURE-
diff --git a/debian/changelog b/debian/changelog
index 6c9ba2a..20756aa 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+ruby-activeldap (5.2.2-2+deb10u1) buster; urgency=medium
+
+  * Add missing dependency on ruby-builder (closes: #982522).
+
+ -- Daniel Leidert   Wed, 03 Nov 2021 15:10:29 +0100
+
 ruby-activeldap (5.2.2-2) unstable; urgency=medium
 
   * Removed dependency on ruby-gettext-i18n-rails, not needed since
diff --git a/debian/control b/debian/control
index e92b671..b2452b9 100644
--- a/debian/control
+++ b/debian/control
@@ -22,6 +22,7 @@ XB-Ruby-Versions: ${ruby:Versions}
 Depends: ruby | ruby-interpreter,
  ruby-activemodel,
  ruby-activesupport,
+ ruby-builder,
  ruby-gettext,
  ruby-locale,
  ruby-net-ldap (>= 0.9.13),

Bug#977979: Current state?

[Daniel Leidert]

Hi,

the fix for this issue is pending for almost 9 months now. I can see that there
have been attempts to update jruby as well. As this is blocking some other
fixes I'd like to ask the current state of jruby and when to expect an upload?

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#980627: ruby-databojects-mysql

[Daniel Leidert]

Am Dienstag, dem 02.11.2021 um 13:36 +0100 schrieb Daniel Leidert:
> Am Mittwoch, dem 27.10.2021 um 11:02 -0300 schrieb Lucas Kanashiro:
> 
> [..]
> > * ruby-databojects-mysql
> [..]

Digging some more: This project has been archived upstream and the homepage
points to https://rom-rb.org/ now, which has active repositories. 

These packages:

* ruby-dataobjects
* ruby-dataobjects-mysql
* ruby-dataobjects-postgres
* ruby-dataobjects-sqlite3

only relate to and depend on each other. They seem to be unused otherwise. I
wonder if we should remove (RoM) them altogether.

Regards, Daniel

-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#980627: ruby-databojects-mysql (was: [RFH] Fix FTBFSes to kick off the ruby3.0 transition)

[Daniel Leidert]

Am Mittwoch, dem 27.10.2021 um 11:02 -0300 schrieb Lucas Kanashiro:

[..]
> * ruby-databojects-mysql
[..]

My finding so far is that the debian/start_mysqld_and_auto_install.sh scripts
requires elevated permissions, but fakeroot is not enough:

> + mysql_install_db --no-defaults --datadir=/tmp/tmp.BZtu29C6kk --force 
> --skip-name-resolve --user=root
> chown: cannot access '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool': 
> Permission denied
> Couldn't set an owner to 
> '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool'.
> It must be root, the PAM authentication plugin doesn't work otherwise..

If I run the whole thing as root, it works (also if I run `sudo gbp
buildpackage`). But I don't see a way to achieve this by default.

I was reading the documentation about Rules-Requires-Root and DEB_GAIN_ROOT_CMD
in our policy and also looked at the libpcap2 package. But all my attempts
failed.

As long as DEB_GAIN_ROOT_CMD is "fakeroot" (default; e.g. set when using Rules-
Requires-Root: binary-targets or dpkg/target-subcommand) the above error
appears. If try to set DEB_GAIN_ROOT_CMD to 'sudo -nE --' (as suggested in the
policy) I either get "not found" or "requires a password" error (and I don't
want to change my sudo policy). I also tried to set the setuid bit for
debian/start_mysqld_and_auto_install.sh and I still get the above error.

I don't have any other ideas. Maybe we can use mysql-sandbox? Maybe we have to
avoid running mysql_install_db or use a fake .my.cnf? I don't know. 

PS: The autopkgtests need elevated permissions as well it seems (and also a
running mysql server judging from the error message).

HTH and regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#996227: ruby-ferret (was: [RFH] Fix FTBFSes to kick off the ruby3.0 transition)

[Daniel Leidert]

Am Montag, dem 01.11.2021 um 16:53 +0100 schrieb Daniel Leidert:
> Am Mittwoch, dem 27.10.2021 um 11:02 -0300 schrieb Lucas Kanashiro:
> 
> [..]
> > * ruby-ferret
> [..]
> 
> Also a candidate for an RoM. Dead for 4 years, no reverse build-deps. Requires
> a lot of patches and seems to be seriously broken with Ruby 3.0 [1].
> 
> [1] https://github.com/dbalmain/ferret/issues/14

Well, it seems the NetBSD community has a patch:
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/textproc/ruby-ferret/patches/

Please note, that Fedora applied a bunch of other patches as well before they
removed the package:

https://src.fedoraproject.org/rpms/rubygem-ferret/tree/a0b3fd879133bf69f6ea59d35b54ec857358e959

I haven't checked, if all of them have been applied to the Debian package as
well.

Regards, Daniel

-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#996145: The issue

[Daniel Leidert]

The problem is that executing exe/byebug fails:

RUBYLIB=. GEM_PATH=/build/ruby-byebug-tmDpwr/ruby-byebug-11.1.3/debian/ruby-
byebug/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0:/build/ruby-byebug-
tmDpwr/ruby-byebug-
11.1.3/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/va
r/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/l
ib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-
integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-
gnu/rubygems-integration/3.0.0 exe/byebug
Ignoring byebug-11.1.3 because its extensions are not built. Try: gem pristine
byebug --version 11.1.3
Traceback (most recent call last):
2: from exe/byebug:4:in `'
1: from
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require':
cannot load such file -- byebug/runner (LoadError)


-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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