Bug#1006941: checkname logic

2022-07-03 Thread Marc Haber
Hi Matt,

thanks for checking this.

On Sun, Jul 03, 2022 at 09:16:49PM -0400, Matt Barry wrote:
> 1st check: all-numeric, always rejected
> 2nd check: ieee 1003.1-2001, minimal requirements [0]
> 3rd check: user-configurable *NAME_REGEX
> 4th: (possible override --allow-badname)

So the hardcoded
if ($name !~ /^[_.A-Za-z0-9][-\@_.A-Za-z0-9]*\$?$/) {
is the IEEE 1003.1-2001 check? Does it make sense to have this
non-overridable?

While the error message is clear, how about having this at least in a
variable like $ieee1003_regex?


> The docs desribe --force-badname as "weak checks applied"; this could
> be clarified, but I don't think its urgent.

We have this in #774046, I planned to do some work o this myself.

> As I write this, the most confusing part is that there are three
> separate checks for all-numeric names; I have a patch to simplify this.

Thank you.

How deeply are we testing the username checks in the suite? I'd like the
test suite to throw some corner cases on both sides of the red line at
adduser and see whether it does what is intended.

Greetings
Marc



Bug#1013931: libtorrent-rasterbar2.0: Crash on exit

2022-07-03 Thread Christian Marillat
On 04 juil. 2022 08:22, Christian Marillat  wrote:

> On 27 juin 2022 18:47, Hilko Bengen  wrote:
>
>> (It might be a good idea to add a Built-Using line to debian/control.)
>
> Built-Using doesn't work with virtual package.

Well, virtual isn't the right word, but libboost-dev is an empty
package and dh_gencontrol return nothing. dh_gencontrol need to be
called with libboost1.74-dev completely unusable for the long term.

Christian



Bug#1013812: (no subject)

2022-07-03 Thread Jean Baptiste Favre

Control: fixed 1013812 9.1.2+ds-13


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1013931: libtorrent-rasterbar2.0: Crash on exit

2022-07-03 Thread Christian Marillat
On 27 juin 2022 18:47, Hilko Bengen  wrote:

> (It might be a good idea to add a Built-Using line to debian/control.)

Built-Using doesn't work with virtual package.

Christian



Bug#1013437: cups: Nothing prints from driverless IPP queues unless added via lpadmin

2022-07-03 Thread Gareth Evans
I had forgotten that the testing in my previous message was with

cups 2.3.3op2-3+deb11u1 

where deleting all queues and restarting cups at least results in reliable 
queue creation for the autodetected printer.

The situation is worse with 2.3.3op2-3+deb11u2.

The queue for the auto-detected printer is only created if no other queue 
already exists.
It still doesn't print.

And even worse:

$ sudo lpadmin -p testqhostname -v ipp://192.168.0.14/ipp/print -E -m 
driverless:ipp://192.168.0.14/ipp/print
lpadmin: Printer drivers are deprecated and will stop working in a future 
version of CUPS.
lpadmin: Unable to open PPD "/tmp/3986562c28d87": Missing PPD-Adobe-4.x header 
on line 0.

No queue is created even after reboot, retry.

I will update upstream with the details of both sets of problems.

Thanks,
Gareth



Bug#1014321: reportbug: emacsclient crashes emacs daemon when another emacsclient is suspended

2022-07-03 Thread Steve VanDevender
Package: emacs
Version: 1:27.1+1-3.1
Severity: important

Dear Maintainer,

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

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

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

This is a known bug in Emacs 27.1 which has been fixed in later versions,
so rather than reiterate the full description I will refer to the Emacs
bug report and the patch(es) that fix it.

https://lists.gnu.org/archive/html/bug-gnu-emacs/2020-10/msg00703.html
https://git.savannah.gnu.org/cgit/emacs.git/log/?qt=grep&q=43886

The fix, relative to the Emacs 27.1 release, effectively just comments out
one line of code.

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

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

Versions of packages emacs depends on:
ii  emacs-gtk  1:27.1+1-3.1

emacs recommends no packages.

emacs suggests no packages.

-- no debconf information



Bug#1010247: ITP: greetd -- minimal and flexible login manager daemon

2022-07-03 Thread Johannes Schauer Marin Rodrigues
Hi,

On Wed, 27 Apr 2022 15:19:59 +0900 =?UTF-8?Q?Marc_Dequ=C3=A8nes_=28duck=29?= 
 wrote:
> greetd makes no assumptions about what you want to launch. Use gtkgreet to
> launch sway if you want a fully graphical session, or use agreety to launch a
> shell if you want a drop-in replacement for agetty(8) and login(1). If you
> can run it from your shell in a TTY, greetd can start it. If it can be taught
> to speak a simple JSON-based IPC protocol, then it can be a greeter.
> 
> 
> Most login managers historically assumes X11. The most compatible one is
> probably GDM but unless you use GNOME you may wish to have a more
> lightweight solution. Lightdm worked well until recently despite not
> having Walyland support itself but it is now afflicted by this bug:
>https://github.com/swaywm/sway/issues/6655
> The last release dates 2018 and there is no recent coding activity.
> I think greetd's architecture properly decouples authentication and the
> login UI and makes for a good replacement for Wayland users.
> 
> I was thinking about maintaining it into the Rust team but I have not joined
> yet.

how is the packaging going? Are you still intending to package it? Is there
already a git repository on salsa?

Thanks!

cheers, josch

signature.asc
Description: signature


Bug#1014319: depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or directory

2022-07-03 Thread Konomi Kitten
Package: initramfs-tools
Version: 0.141
Severity: minor
X-Debbugs-Cc: konomikit...@gmail.com

When update-initramfs runs I receive the following message:

depmod: WARNING: could not open modules.builtin.modinfo at
/var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or
directory


-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 56M Jul  4 14:01 /boot/initrd.img-5.16.0-6-amd64
-rw-r--r-- 1 root root 58M Jul  4 14:01 /boot/initrd.img-5.17.0-3-amd64
-rw-r--r-- 1 root root 58M Jul  4 14:00 /boot/initrd.img-5.18.0-1-amd64
-rw-r--r-- 1 root root 58M Jul  4 14:56 /boot/initrd.img-5.18.0-2-amd64
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.18.0-2-amd64 
root=UUID=e7b71052-3dff-454b-9730-7b146ebdf115 ro quiet systemd.show_status=true

-- /proc/filesystems
btrfs
fuseblk
vfat
ext3
ext2
ext4

-- lsmod
Module  Size  Used by
ext4  946176  1
mbcache16384  1 ext4
jbd2  163840  1 ext4
dm_crypt   61440  1
dm_mod176128  3 dm_crypt
tcp_diag   16384  0
inet_diag  24576  1 tcp_diag
ctr16384  3
ccm20480  9
vboxnetadp 28672  0
vboxnetflt 32768  0
vboxdrv   532480  2 vboxnetadp,vboxnetflt
rfcomm 90112  16
ip6t_REJECT16384  1
nf_reject_ipv6 20480  1 ip6t_REJECT
xt_hl  16384  22
ip6_tables 36864  52
ip6t_rt20480  3
ipt_REJECT 16384  1
nf_reject_ipv4 16384  1 ipt_REJECT
xt_LOG 20480  14
qrtr   45056  4
cpufreq_userspace  20480  0
cpufreq_powersave  20480  0
cpufreq_ondemand   16384  0
cpufreq_conservative16384  0
nf_log_syslog  20480  14
cmac   16384  3
nft_limit  16384  17
algif_hash 16384  1
algif_skcipher 16384  1
af_alg 36864  6 algif_hash,algif_skcipher
bnep   28672  2
zstd   16384  12
zram   40960  2
zsmalloc   32768  1 zram
xt_limit   16384  0
xt_addrtype16384  5
nft_chain_nat  16384  2
xt_nat 16384  4
nf_nat 57344  2 xt_nat,nft_chain_nat
xt_conntrack   16384  20
nf_conntrack  176128  3 xt_conntrack,nf_nat,xt_nat
nf_defrag_ipv6 24576  1 nf_conntrack
nf_defrag_ipv4 16384  1 nf_conntrack
xt_tcpudp  20480  0
nft_compat 20480  130
nf_tables 278528  759 nft_compat,nft_chain_nat,nft_limit
binfmt_misc24576  1
nfnetlink  20480  2 nft_compat,nf_tables
nls_ascii  16384  1
nls_cp437  20480  1
vfat   20480  1
fat86016  1 vfat
btusb  65536  0
btrtl  28672  1 btusb
btbcm  24576  1 btusb
btintel45056  1 btusb
iwlmvm368640  0
btmtk  16384  1 btusb
intel_rapl_msr 20480  0
intel_rapl_common  28672  1 intel_rapl_msr
bluetooth 876544  44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
mac80211 1085440  1 iwlmvm
edac_mce_amd   36864  0
snd_hda_codec_realtek   167936  1
jitterentropy_rng  16384  1
snd_hda_codec_generic98304  1 snd_hda_codec_realtek
ledtrig_audio  16384  1 snd_hda_codec_generic
sha512_ssse3   49152  1
snd_hda_codec_hdmi 73728  1
sha512_generic 16384  1 sha512_ssse3
kvm_amd   151552  0
snd_hda_intel  57344  5
snd_usb_audio 356352  4
drbg   40960  1
libarc416384  1 mac80211
snd_intel_dspcfg   32768  1 snd_hda_intel
snd_usbmidi_lib45056  1 snd_usb_audio
snd_intel_sdw_acpi 20480  1 snd_intel_dspcfg
ansi_cprng 16384  0
kvm  1060864  1 kvm_amd
iwlwifi   344064  1 iwlmvm
snd_rawmidi45056  1 snd_usbmidi_lib
snd_hda_codec 176128  4 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_seq_device 16384  1 snd_rawmidi
snd_hda_core  110592  5 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
irqbypass  16384  1 kvm
mc 65536  1 snd_usb_audio
snd_hwdep  16384  2 snd_usb_audio,snd_hda_codec
ecdh_generic   16384  2 bluetooth
joydev 28672  0
ecc40960  1 ecdh_generic
rapl   20480  0
snd_pcm   147456  8 
snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core
crc16  16384  2 bluetooth,ext4
cfg80211 1056768  3 iwlmvm,iwlwifi,mac80211
snd_timer  45056  1 snd_pcm
snd   110592  27 
snd_hda_codec_generic,snd_seq_device,snd_hda_

Bug#1004831: transition: ffmpeg

2022-07-03 Thread Steven Robbins
Hello,

On Wed, 22 Jun 2022 22:13:11 +0200 Sebastian Ramacher  
wrote:

> ffmpeg got a new major release including API and ABI breakage. Hence, it
> needs a transition. The reverse dependencies are not yet ready, so this
> bug is just a heads up and should help to track progress. Due to
> ffmpeg's security record, we should complete this transition for
> bookworm.

Reverse dependencies had 4 months to fix their bugs, so I'm going ahead
with this one.

Yes, well as noted: this is a major release with ABI and API breakage.  It is 
unrealistic to expect the entire open source world to adopt this all at once.  
Digikam upstream, for example, is working on the transition, but it is not 
straightforward.  Current recommendation is to continue to build against the 
version 4 API [1].

Consider reintroducing the ffmpeg 4 libraries alongside version 5.

Thank you,
-Steve

[1] https://mail.kde.org/pipermail/digikam-users/2022-July/033796.html



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


Bug#1014318: rocm-smi-lib: ftbfs on riscv64(error: some symbols or patterns disappeared in the symbols file)

2022-07-03 Thread Bo YU
Source: rocm-smi-lib
Version: 5.2.0-1
Severity: normal
Tags: ftbfs, patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org

Dear rocm-smi-lib Maintainer,

The rocm-smi-lib package has a ftbfs issue due to :

```
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/librocm-smi64-1/DEBIAN/symbols doesn't match 
completely debian/librocm-smi64-1.symbols
--- debian/librocm-smi64-1.symbols (librocm-smi64-1_5.2.0-1_riscv64)
+++ dpkg-gensymbolsIBeNBq   2022-07-04 00:53:31.834782542 +
@@ -809,32 +809,50 @@
  (arch=any-i386 armel armhf mipsel hppa m68k powerpc 
sh4)_ZN9__gnu_cxx13new_allocatorISt13_Rb_tree_nodeISt4pairIKySt10shared_ptrISt6vectorIySaIyEEC2Ev@Base
 5.1.0
  (arch=any-i386 armel armhf mipsel hppa m68k powerpc 
sh4)_ZN9__gnu_cxx13new_allocatorISt13_Rb_tree_nodeISt4pairIKySt10shared_ptrISt6vectorIySaIyEED1Ev@Base
 5.1.0
  (arch=any-i386 armel armhf mipsel hppa m68k powerpc 
sh4)_ZN9__gnu_cxx13new_allocatorISt13_Rb_tree_nodeISt4pairIKySt10shared_ptrISt6vectorIySaIyEED2Ev@Base
 5.1.0
+ 
_ZN9__gnu_cxx13new_allocatorISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS7_ELNS_12_Lock_policyE1EEE10deallocateEPSA_m@Base
 5.2.0-1
+ 
_ZN9__gnu_cxx13new_allocatorISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS7_ELNS_12_Lock_policyE1EEE8allocateEmPKv@Base
 5.2.0-1
+ 
_ZN9__gnu_cxx13new_allocatorISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS7_ELNS_12_Lock_policyE1EEEC1Ev@Base
 5.2.0-1
+ 
_ZN9__gnu_cxx13new_allocatorISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS7_ELNS_12_Lock_policyE1EEEC2Ev@Base
 5.2.0-1
+ 
_ZN9__gnu_cxx13new_allocatorISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS7_ELNS_12_Lock_policyE1EEED1Ev@Base
 5.2.0-1
+ 
_ZN9__gnu_cxx13new_allocatorISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS7_ELNS_12_Lock_policyE1EEED2Ev@Base
 5.2.0-1
...
```
The full buildd log is here:

https://buildd.debian.org/status/fetch.php?pkg=rocm-smi-lib&arch=riscv64&ver=5.2.0-1&stamp=1656896064&raw=0

The symbols file attached is to fix the issue and I can build the package
successfully on my locally real riscv64 hardware(Unmatched board).
But it still give warning about some new symbols appeared in the 
symbols file. Although I have tried several times to update the symbol 
file from the riscv64 build log. So do we wait to new upload and get new
others arch buildd log to clear those warnings[0]?

Please let me know if there are any issues.

Bo

[0]: https://www.eyrie.org/~eagle/journal/2012-01/008.html
-- 
Best Regards,



signature.asc
Description: PGP signature


Bug#1013300: openbsd-inetd: default services (echo, discard, chargen, {,day}time) not provided nor documented

2022-07-03 Thread Marco d'Itri
On Jun 21, Thorsten Glaser  wrote:

> The /etc/inetd.conf file does not contain even commented-out
> lines for the standard services.
I am surely not going to encourage people configuring the UDP small 
services, which are a source of reflection DoS attacks.

> It’d also be a good idea to document all internal services in the
> manual pages.
They are:

 inetd provides several “trivial” services internally by use of routines
 within itself.  These services are “echo”, “discard”, “chargen” (charac‐
 ter generator), “daytime” (human readable time), and “time” (machine
 readable time, in the form of the number of seconds since midnight, Janu‐
 ary 1, 1900).  All of these services are TCP based.  For details of these
 services, consult the appropriate RFC from the Network Information Cen‐
 ter.


-- 
ciao,
Marco


signature.asc
Description: PGP signature


Bug#1014309: libpod - FTBFS: FAIL: TestMonitorTwoDirGood (1.08s)

2022-07-03 Thread Shengjing Zhu
On Sun, Jul 03, 2022 at 10:28:46PM +0200, Bastian Blank wrote:
> On Mon, Jul 04, 2022 at 04:09:40AM +0800, Shengjing Zhu wrote:
> > Looks like flaky tests.
> > 
> > For example, debci runs these tests without problem. And I just
> > verified in local sbuild as well.
> > https://ci.debian.net/data/autopkgtest/testing/amd64/libp/libpod/23064901/log.gz
> 
> And you should check the correct version (yes, I goofed up), see
> https://buildd.debian.org/status/package.php?p=libpod&suite=experimental
> 

There is race with the bug report and a new version upload to experimental.
With the new version, it does FTBFS in experimental now. But the failed test
is TestEnvVarValue, not TestMonitorTwoDirGood.

As for s390x, for the version in unstable, the test doesn't fail on debci too.
https://ci.debian.net/data/autopkgtest/testing/s390x/libp/libpod/23186547/log.gz



Bug#1014317: ITP: yarsync -- file synchronization and backup tool

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

* Package name: yarsync
  Version : 0.1.1
  Upstream Author : Yaroslav Nikitenko .
* URL : https://github.com/ynikitenko/yarsync
* License : GPL3
  Programming Lang: Python
  Description : file synchronization and backup tool

 can be used to synchronize data between different hosts
 or locally. (eg for a backup drive).
 .
 provides a familiar git command interface when working with files.



Bug#1014314: lvm2: Missing 69-lvm-metad.rules causes lvm2 initramfs-tools hook to fail

2022-07-03 Thread Kentaro Hayashi
FYI: similar issue was reported in the past

lvm2: initramfs generation fails if neither 
/etc/udev/rules.d/69-lvm-metad.rules nor 
/lib/udev/rules.d/69-lvm-metad.rules exists

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881916



Bug#1006941: checkname logic

2022-07-03 Thread Matt Barry
The logic as it is now is fairly straightforward:

1st check: all-numeric, always rejected
2nd check: ieee 1003.1-2001, minimal requirements [0]
3rd check: user-configurable *NAME_REGEX
4th: (possible override --allow-badname)

The docs desribe --force-badname as "weak checks applied"; this could
be clarified, but I don't think its urgent.

As I write this, the most confusing part is that there are three
separate checks for all-numeric names; I have a patch to simplify this.

Cheers,
Matt

[0] this ties us to ascii mostly alpha-num usernames, obviously.  I
think it is okay to have a sanity check hard-coded to limit user's
creativity here, at least until we support anything wider.


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


Bug#1014316: Unexpected behavior at login prompt

2022-07-03 Thread Joseph Carter
Package: kmscon
Version: 9.0.0-1+b1
Severity: minor

I recently wound up with an ulltrawide monitor that is effectively a 4k
screen with a haircut at 1600 lines … and I'm legally blind. So let me
say that I greatly appreciate this package and the ease with which I
specified a custom DPI to get readable fonts at the console—thank you
for packaging it.

I also appreciate the standard getty fallback. The other distribution
thus far that seems to have kmscon as an option is arch (because of
course it does) and … they describe configuring a specific tty for getty
in case kmscon fails. An automatic fallback seems more elegant.

That said, it behaves a bit strangely prior to logging in, and these
things cause minor usability issues. Chief among these is that backspace
doesn't work. My password is deliberately not short (as in xkcd 936 not
short), and I sometimes mistype it. I've learned that the backspace key
does not work at this login prompt.

It also doesn't display /etc/issue which might be a symptom of the same
issue, being a different login process than is typically used by Debian
at the console? There might be a workaround, in that case, to run the
more traditional login process under kmscon, but I haven't really
researched that yet and that wouldn't change the default anyway, so a
report is still warranted IMO.

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

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

Versions of packages kmscon depends on:
ii  libc6  2.33-7
ii  libdrm22.4.110-1
ii  libegl11.4.0-1
ii  libgbm122.0.5-1
ii  libgles2   1.4.0-1
ii  libglib2.0-0   2.72.3-1
ii  libpango-1.0-0 1.50.7+ds-1
ii  libpangoft2-1.0-0  1.50.7+ds-1
ii  libpixman-1-0  0.40.0-1
ii  libsystemd0251.2-7
ii  libtsm44.0.2-0.3
ii  libudev1   251.2-7
ii  libxkbcommon0  1.4.0-1

kmscon recommends no packages.

kmscon suggests no packages.

-- no debconf information


Bug#1014259: sscg: ftbfs on riscv64: (create_csr_test TIMEOUT 30.10s killed by signal 15 SIGTERM)

2022-07-03 Thread 肖盛文

在 2022/7/3 16:00, Boyuan Yang 写道:


Hi all,

Martin: is it possible to patch the package to get around the timeout for slow
archs such as riscv64? My current thoughts include (1) force non-parallel test
(override_dh_auto_test: dh_auto_test --no-parallel), and/or (2) patch


Is there a way to only do " --no-parallel" test under riscv arch?



--
肖盛文 xiao sheng wen
https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
Debian salsa: https://salsa.debian.org/atzlinux-guest
GnuPG Public Key: 0x00186602339240CB



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1011594: Please import new upstream snapshot (currently at 0.0~git20220518.60ebf56)

2022-07-03 Thread Nicholas D Steeves
Hi Joshua,

Here's gentle ping to take a look at this bug.

Cheers,
Nicholas


signature.asc
Description: PGP signature


Bug#1014289: vile: FTBFS with Perl 5.36: ‘regexp_aligned’ undeclared here

2022-07-03 Thread Thomas Dickey
On Sun, Jul 03, 2022 at 04:57:01PM +0300, Niko Tyni wrote:
> Source: vile
> Version: 9.8v-2
> Severity: normal
> Tags: ftbfs
> User: debian-p...@lists.debian.org
> Usertags: perl-5.36-transition
> 
> This package fails to build from source with Perl 5.36 (currently in 
> experimental).

fix attached.

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net
===
RCS file: RCS/perl.xs,v
retrieving revision 1.143
diff -u -r1.143 perl.xs
--- perl.xs	2021/12/07 01:40:25	1.143
+++ perl.xs	2022/07/03 18:02:36
@@ -13,7 +13,7 @@
  * vile.  The file api.c (sometimes) provides a middle layer between
  * this interface and the rest of vile.
  *
- * $Id: perl.xs,v 1.143 2021/12/07 01:40:25 tom Exp $
+ * $Id: perl.xs,v 1.144 2022/07/03 18:02:36 tom Exp $
  */
 
 /*
@@ -21,7 +21,6 @@
  */
 #ifdef __GNUC__
 #pragma GCC diagnostic ignored "-Wcast-qual"
-#pragma GCC diagnostic ignored "-Wcompound-token-split-by-macro"
 #pragma GCC diagnostic ignored "-Wconversion"
 #pragma GCC diagnostic ignored "-Wnested-externs"
 #pragma GCC diagnostic ignored "-Wshadow"
@@ -119,20 +118,20 @@
 
 /* for vile */
 #define MARK vile_MARK
+#define regexp vile_regexp
 #include "estruct.h"
 #include "edef.h"
 #include "api.h"
+#undef regexp
 #undef MARK
 #undef ABORT
 
 /* for perl */
 #define main perl_main
-#define regexp perl_regexp
 #include 
 #include 
 #include 
 #undef main
-#undef regexp
 #undef dofile
 
 #ifdef __GNUC__


signature.asc
Description: PGP signature


Bug#929339: RFP: qsmtp - drop-in replacement for qmail STMP programs

2022-07-03 Thread Bastian Germann

This is available at https://opensource.sf-tec.de/Qsmtp/



Bug#1009712: sv: fails to control the service on Hurd

2022-07-03 Thread Samuel Thibault
João Pedro Malhado, le lun. 04 juil. 2022 00:14:43 +0200, a ecrit:
> Below is a step by step debug trace with libc symbols. At the last step gdb 
> (or
> the whole machine?) locks up. I would say strange, but maybe I shouldn't ;)

That's also expected: you're stepping into very critical sections, which
don't allow the process to interact with gdb any more. You can however
use "next" to go over a whole function call.

Samuel



Bug#739417: ITP: qmplay2 -- a video player

2022-07-03 Thread Bastian Germann

On Fri, 2 Mar 2018 00:18:33 +0100 pavroo wrote:

I debianize the package for a while so should works fine.


I think that there are enough video players in Debian but if you want to pursue this please make this bug an ITP and 
search for a sponsor.




Bug#1013729: rust-zbus: Please upgrade to version 2.2.0

2022-07-03 Thread Reinhard Tartler



On 7/2/22 15:52, Peter Michael Green wrote:
> There seems to be a group of 4 closely related packages, zbus, zbus-macros, 
> zvariant and zvariant-derive which
> should probably be upgraded in lockstep.
> 
> 2.x (3.x for zvariant) is a semver break, so reverse dependencies need to be 
> investigated.
> 
> rust-ashpd - fixed upstream, upstream fix involves a semver bump but there 
> are no rdeps.
> rust-libslirp - no upstream fix, no rdeps, but does produce a binary crate. 
> Popcon is low, but we did get a bug report from a real user, so it's not 
> totally unused.
> rust-secret-service - no upstream fix, no rdeps, no binarys
> squeekboard - no upstream fix, seems to be used by the "phosh" desktop.
> 
> I can't find any upstream changelog, but I did a quick attempt at bumping the 
> dependencies in libslirp-helper and came to the conclusion it would be a 
> non-trivial porting job.
> 

According to https://crates.io/crates/libslirp/4.3.0/dependencies zvariant is 
mentioned as an optional dependency. Can we take the option to avoid the 
dependency, maybe at the expense of unit tests?

> There is also the problem that squeekboard is currently failing to build on 
> ppc64el due to what may or may not
> be a rust bug ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013273 )

ppc64el is a tier 2 architecture. Maybe we can stop building in it on ppc64el 
for the time being?

> 
> The other option would be to introduce seperate packages for the old versions 
> of the crates, so that the
> main packages could be upgraded to the new semver, we try to avoid such 
> duplication if possible
> though and I do not intend to introduce packages myself.
> 
> I belive hntourne was also showing an interest in zbus, putting him in cc.

Do we want to update zbus, zbus-macros, zvariant and zvariant-derive in 
experimental to ease with the porting effort?

-rt



Bug#886900: RFP: python-epub -- Python2 Library to open and read files in the epub version 2

2022-07-03 Thread Bastian Germann

Control: block 886899 by -1
Control: retitle -1 RFP: python-epub -- open and read epub version 2 files

The library is tagged as compatible with Python :: 3.2 and seems to be 
abandoned.
It is still available at https://pypi.org/project/epub/



Bug#1009712: sv: fails to control the service on Hurd

2022-07-03 Thread João Pedro Malhado
Hello Samuel,

On Sun, Jul 03, 2022 at 10:09:04PM +0200, Samuel Thibault wrote:
> João Pedro Malhado, le dim. 03 juil. 2022 21:41:05 +0200, a ecrit:
> > > This looks strange and I cannot interpret what is going on.
> 
> This is not strange, see the values of E* macros

I'm glad that you don't find it strange, and that you can look beyond what I can
see :)

> ENOSYS = 0x404e, /* Function not implemented */
> 
> So that's it.
> 
> Getting ENOSYS is odd, though, since open64 is defined in
> glibc/sysdeps/mach/hurd/open.c
> 
> It's probably useful to debug step by step to see what function is
> actually getting called.

Below is a step by step debug trace with libc symbols. At the last step gdb (or
the whole machine?) locks up. I would say strange, but maybe I shouldn't ;)

Best regards,
João
Breakpoint 1 at 0x17b0: control. (2 locations)
Starting program: /usr/bin/sv start cron
[New Thread 763.5]

Thread 4 hit Breakpoint 1, control (a=0x803cbe0 "u")
at ./runit-2.1.2/src/sv.c:253
253 ./runit-2.1.2/src/sv.c: No such file or directory.
svstatus_get () at ./runit-2.1.2/src/sv.c:94
94  in ./runit-2.1.2/src/sv.c
open_write (fn=0x803caa0 "supervise/ok") at ./runit-2.1.2/src/open_write.c:8
8   ./runit-2.1.2/src/open_write.c: No such file or directory.
open64 (__oflag=10, __path=0x803caa0 "supervise/ok")
at /usr/include/i386-gnu/bits/fcntl2.h:53
53return __open_alias (__path, __oflag, __va_arg_pack ());
__GI___libc_open (file=0x803caa0 "supervise/ok", oflag=10)
at ../sysdeps/mach/hurd/open.c:35
35  ../sysdeps/mach/hurd/open.c: No such file or directory.
__x86.get_pc_thunk.bx () at ../sysdeps/i386/i686/multiarch/memset-sse2.S:108
108 ../sysdeps/i386/i686/multiarch/memset-sse2.S: No such file or directory.
__GI___libc_open (file=0x803caa0 "supervise/ok", oflag=10)
at ../sysdeps/mach/hurd/open.c:45
45  ../sysdeps/mach/hurd/open.c: No such file or directory.
46  in ../sysdeps/mach/hurd/open.c
__file_name_lookup (file_name=0x803caa0 "supervise/ok", flags=10, mode=0)
at hurdlookup.c:222
222 hurdlookup.c: No such file or directory.
__x86.get_pc_thunk.bx () at ../sysdeps/i386/i686/multiarch/memset-sse2.S:108
108 ../sysdeps/i386/i686/multiarch/memset-sse2.S: No such file or directory.
__file_name_lookup (file_name=0x803caa0 "supervise/ok", flags=10, mode=0)
at hurdlookup.c:226
226 hurdlookup.c: No such file or directory.
0x0106cbc7 in __hurd_file_name_lookup (
use_init_port=0x1064dc0 <_hurd_ports_use>, 
get_dtable_port=0x108cbe0 <__getdport>, lookup=0x0, 
file_name=0x803caa0 "supervise/ok", flags=10, mode=0, result=0x1039cd8)
at hurdlookup.c:50
50  in hurdlookup.c
62  in hurdlookup.c
63  in hurdlookup.c
65  in hurdlookup.c
68  in hurdlookup.c
69  in hurdlookup.c
72  in hurdlookup.c
75  in hurdlookup.c
93  in hurdlookup.c
_hurd_ports_use (which=0, operate=0x1039c78) at hurdinit.c:45
45  hurdinit.c: No such file or directory.
__x86.get_pc_thunk.bx () at ../sysdeps/i386/i686/multiarch/memset-sse2.S:108
108 ../sysdeps/i386/i686/multiarch/memset-sse2.S: No such file or directory.
_hurd_ports_use (which=0, operate=0x1039c78) at hurdinit.c:52
52  hurdinit.c: No such file or directory.
_hurd_port_get (link=0x1039804, port=0x1327f88) at ../hurd/hurd/port.h:121
121 ../hurd/hurd/port.h: No such file or directory.
_hurd_critical_section_lock () at ../hurd/hurd/signal.h:213
213 ../hurd/hurd/signal.h: No such file or directory.
218 in ../hurd/hurd/signal.h
219 in ../hurd/hurd/signal.h
232 in ../hurd/hurd/signal.h
__GI___spin_try_lock (__lock=0x132a808) at ../mach/lock-intern.h:82
82  ../mach/lock-intern.h: No such file or directory.
_hurd_port_get (link=0x1039804, port=0x1327f88) at ../hurd/hurd/port.h:122
122 ../hurd/hurd/port.h: No such file or directory.
__GI___spin_lock (__lock=0x1327f88) at ../mach/lock-intern.h:60
60  ../mach/lock-intern.h: No such file or directory.
_hurd_port_get (link=0x1039804, port=0x1327f88) at ../hurd/hurd/port.h:123
123 ../hurd/hurd/port.h: No such file or directory.
__GI__hurd_port_locked_get (link=0x1039804, port=0x1327f88)
at ../hurd/hurd/port.h:95
95  in ../hurd/hurd/port.h
96  in ../hurd/hurd/port.h
98  in ../hurd/hurd/port.h
99  in ../hurd/hurd/port.h
100 in ../hurd/hurd/port.h
_hurd_userlink_link (link=0x1039804, chainp=0x1327f8c)
at ../hurd/hurd/userlink.h:95
95  ../hurd/hurd/userlink.h: No such file or directory.
96  in ../hurd/hurd/userlink.h
98  in ../hurd/hurd/userlink.h
99  in ../hurd/hurd/userlink.h
102 in ../hurd/hurd/userlink.h
__GI__hurd_self_sigstate () at ../hurd/hurd/signal.h:168
168 ../hurd/hurd/signal.h: No such file or directory.
174 in ../hurd/hurd/signal.h
103 ../hurd/hurd/userlink.h: No such file or directory.
104 in ../hurd/hurd/userlink.h
106 in ../hurd/hurd/userlink.h
__GI__hurd_port_locked_get (link=0x1039804, por

Bug#1014272: src:linux: sign-file: correct error handling

2022-07-03 Thread Daniel Lewart
On Sun, 03 Jul 2022 11:47:51 +0200, Ansgar wrote:

> The functions CMS_final, i2d_CMS_bio_stream, i2d_PKCS7_bio and
> BIO_free all return 1 for success or 0 for failure. The old check
> for a value less than 0 would never catch an error.

> I tried signing a kernel module with the patched sign-file and that
> still worked.

Wow!  This may help solve the following signing bugs:
  * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012741
  * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014311

Thank you!
Daniel Lewart
Urbana, Illinois



Bug#1014278: statsmodels: s390x fails TestDynamicFactor test_mle with scipy 1.8 and pythran)

2022-07-03 Thread Drew Parsons
Small correction: statsmodels did pass tests with scipy/1.8.1-4 (18 June 
2022), so the test_mle failure can probably be attributed to use of 
pythran with scipy 1.8.




Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

2022-07-03 Thread Daniel Lewart
Ben, et al,

On Sun, 19 Jun 2022 12:59:55 +0200, Ben Hutchings wrote:
> In the mean time, we have another security update coming which might
> not hit this bug again.  But there are 28,679 signed binaries across
> the three architectures, so the probability is only about 65%.

I looked at the following new (Jul  2, 2022) binaries:
  * linux-image-4.19.0-21-686-pae_4.19.249-2_i386.deb
  * linux-image-4.19.0-21-686_4.19.249-2_i386.deb
  * linux-image-4.19.0-21-amd64_4.19.249-2_amd64.deb
  * linux-image-4.19.0-21-arm64_4.19.249-2_arm64.deb
  * linux-image-4.19.0-21-cloud-amd64_4.19.249-2_amd64.deb
  * linux-image-4.19.0-21-rt-686-pae_4.19.249-2_i386.deb
  * linux-image-4.19.0-21-rt-amd64_4.19.249-2_amd64.deb
  * linux-image-4.19.0-21-rt-arm64_4.19.249-2_arm64.deb

There were 25,011 signed kernel modules, with one bad signature:
  * binary package: linux-image-4.19.0-21-amd64
  * version: 4.19.249-2
  * file: lib/modules/4.19.0-21-amd64/kernel/net/openvswitch/vport-vxlan.ko

Perhaps this bug should be retitled?

Thank you!
Dan
Urbana, Illinois



Bug#583976: alligning UID==GID for user private groups

2022-07-03 Thread Marc Haber
Control: tags -1 
thanks

On Wed, Nov 23, 2011 at 11:06:45AM +0100, Marc Haber wrote:
> So the idea would be to iterate through the number space until a
> number is found that is free both as a UID and a GID if it is
> requested to create a user and the corresponding, identically named
> group?

According to #643561, uid identity is no longer needed for the PAM
feature to work.

Greetings
Marc



Bug#1012761: ITP: shtab -- generator for shell tab completion files for python projects

2022-07-03 Thread Johannes Schauer Marin Rodrigues
Hi Felix,

On Tue, 21 Jun 2022 14:30:38 + "Moessbauer, Felix" 
 wrote:
> the initial packaging of shtab is implemented in [1] and should be ready for
> a review.
> 
> @stephan It would be great if you could sponsor this package.
> We talked about that at Debian Reunion Hamburg.
> 
> [1] https://salsa.debian.org/python-team/packages/shtab

thank you for your packaging! I built and installed your shtab package locally
and it worked fine for me after some small adjustments to one of my packages
with a very complex CLI interface (img2pdf [1]).

Thanks!

cheers, josch

[1] https://manpages.debian.org/unstable/img2pdf/img2pdf.1.en.html

signature.asc
Description: signature


Bug#1014315: bullseye-pu: package dnsproxy/1.16-0.1+deb11u1

2022-07-03 Thread Marcos Talau
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

Dear team,

[ Reason ]
The dnsproxy package fails to install when you do not have the IP
address "192.168.168.1" configured on the machine. This bug remains
since its initial release.

[ Impact ]
A user that not have the address "192.168.168.1" configured on the machine
will not be able to install the package.

[ Tests ]
I did manual tests. I installed and removed the new deb file three times.

[ Risks ]
This code is trivial. No risks.

[ 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 ]
To fix the problem I just changed the file "debian/dnsproxy.conf" replacing
the line "listen 192.168.168.1" to "listen 127.0.0.1".

[ Other info ]
None.

Thanks!


Best Regards,
mt
diff -u dnsproxy-1.16/debian/dnsproxy.conf dnsproxy-1.16/debian/dnsproxy.conf
--- dnsproxy-1.16/debian/dnsproxy.conf
+++ dnsproxy-1.16/debian/dnsproxy.conf
@@ -20,7 +20,7 @@
 #
 # Local address and port of dnsproxy
 #
-listen 192.168.168.1
+listen 127.0.0.1
 port 53000
 
 #
diff -u dnsproxy-1.16/debian/changelog dnsproxy-1.16/debian/changelog
--- dnsproxy-1.16/debian/changelog
+++ dnsproxy-1.16/debian/changelog
@@ -1,3 +1,13 @@
+dnsproxy (1.16-0.1+deb11u1) bullseye; urgency=medium
+
+  * debian/dnsproxy.conf: Change the default listening IP address to localhost.
+This address is used by the daemon to bind a UDP port when it starts.
+Currently, the default listening address is "192.168.168.1", and if this
+address is not available on the machine, this will cause a dpkg error when 
+trying to install dnsproxy. Thanks to Marco d'Itri (Closes: #802918).
+
+ -- Marcos Talau   Sun, 03 Jul 2022 16:35:09 -0300
+
 dnsproxy (1.16-0.1) unstable; urgency=low
 
   * Non-maintainer upload.


Bug#1012492: /etc/adduser.conf.dpkg-save created by postinst

2022-07-03 Thread Marc Haber
On Wed, Jun 08, 2022 at 12:49:01PM -0400, Jason Franklin wrote:
> If we're on the same page here, should I put a patch together?

We are. Please go ahead. I apologize for not seeing this or losing
focus.

Greetings
Marc



Bug#887650: RFP: python3-nltk-doc -- Natural Language Processing with Python - book

2022-07-03 Thread Bastian Germann

Control: retitle -1 nltk-book -- Natural Language Processing with Python (book)

On Thu, 18 Jan 2018 12:56:09 -0500 Don Pellegrino 
 wrote:

* Package name: python3-nltk-doc
  Version : 268a3bb
  Upstream Author : NLTK Project
* URL : https://github.com/nltk/nltk_book
* License : CC BY-NC-ND 3.0 US


This would have to go to non-free. I do not think it is worth the packaging 
effort.



Bug#1014314: lvm2: Missing 69-lvm-metad.rules causes lvm2 initramfs-tools hook to fail

2022-07-03 Thread Salvatore Bonaccorso
Package: lvm2
Version: 2.03.15-1
Severity: serious
Justification: fails to upgrade (not exactly, but fails to update initramfs due 
to failing lvm2 hook)
X-Debbugs-Cc: car...@debian.org

Hi

Updating lvm2 (and related packages) from 2.03.11-2.1 to 2.03.15-1
causes the lvm2 initramfs-tools hook
/usr/share/initramfs-tools/hooks/lvm2 to exit with 1.

Calling hook lvm2
+ PREREQ=
+ . /usr/share/initramfs-tools/hook-functions
+ cp -a /etc/lvm/ /var/tmp/mkinitramfs_WUGPmN/etc/lvm/
+ mkdir -p /var/tmp/mkinitramfs_WUGPmN/lib/udev/rules.d/
+ [ -e /etc/udev/rules.d/56-lvm.rules ]
+ [ -e /lib/udev/rules.d/56-lvm.rules ]
+ cp -p /lib/udev/rules.d/56-lvm.rules 
/var/tmp/mkinitramfs_WUGPmN/lib/udev/rules.d/
+ [ -e /etc/udev/rules.d/69-lvm-metad.rules ]
+ [ -e /lib/udev/rules.d/69-lvm-metad.rules ]
+ exit 1
E: /usr/share/initramfs-tools/hooks/lvm2 failed with return 1. 

/lib/udev/rules.d/69-lvm-metad.rules is not shipped anymore in the new
package:

Files in second .deb but not in first
-
-rw-r--r--  root/root   /lib/udev/rules.d/69-lvm.rules

Files in first .deb but not in second
-
-rw-r--r--  root/root   /lib/systemd/system/lvm2-pvscan@.service
-rw-r--r--  root/root   /lib/udev/rules.d/69-lvm-metad.rules
-rw-r--r--  root/root   /usr/share/man/man8/lvm2-activation-generator.8.gz
-rwxr-xr-x  root/root   /lib/systemd/system-generators/lvm2-activation-generator
-rwxr-xr-x  root/root   /usr/share/initramfs-tools/scripts/local-block/lvm2
-rwxr-xr-x  root/root   /usr/share/initramfs-tools/scripts/local-top/lvm2

Does the initramfs-tools hook need updating for the new installed udev
rules files?

Regards,
Salvatore



Bug#541620: [Adduser-devel] Bug#541620: /etc/adduser.conf is not handled at all

2022-07-03 Thread Marc Haber
On Thu, Sep 10, 2009 at 09:08:22AM +0100, Stephen Gran wrote:
> In 2001, we only had dpkg's conffile handling, and we couldn't do any
> editing of the config file in postinst if we shipped it in place in
> the deb.  Now ucf exists, so it's probably a good idea to revisit the
> maintainer scripts.

otoh, that would pull in ucf on all systems. We'd need to build some
scaffolding for graceful operation if ucf is present so that we can live
with a Recommends: ucf or Suggests: ucf.

Greetings
Marc



Bug#1014309: libpod - FTBFS: FAIL: TestMonitorTwoDirGood (1.08s)

2022-07-03 Thread Bastian Blank
On Mon, Jul 04, 2022 at 04:09:40AM +0800, Shengjing Zhu wrote:
> Looks like flaky tests.
> 
> For example, debci runs these tests without problem. And I just
> verified in local sbuild as well.
> https://ci.debian.net/data/autopkgtest/testing/amd64/libp/libpod/23064901/log.gz

And you should check the correct version (yes, I goofed up), see
https://buildd.debian.org/status/package.php?p=libpod&suite=experimental

Bastian

-- 
Ahead warp factor one, Mr. Sulu.



Bug#1014309: libpod - FTBFS: FAIL: TestMonitorTwoDirGood (1.08s)

2022-07-03 Thread Bastian Blank
On Mon, Jul 04, 2022 at 04:09:40AM +0800, Shengjing Zhu wrote:
> Control: severity -1 important
> 
> On Mon, Jul 4, 2022 at 3:27 AM Bastian Blank  wrote:
> >
> > Source: libpod
> > Version: 3.4.7+ds1-3
> > Severity: serious
> > Tags: ftbfs
> >
> > libpod fails to build from source on several architectures:
> > |
> > | --- FAIL: TestMonitorTwoDirGood (1.08s)
> > | --- PASS: TestMonitorTwoDirGood/good-fallback-addition (0.10s)
> > | --- FAIL: TestMonitorTwoDirGood/good-primary-override (0.11s)
> > | --- FAIL: TestMonitorTwoDirGood/good-fallback-removal (0.10s)
> > | --- PASS: TestMonitorTwoDirGood/good-fallback-restore (0.17s)
> > | --- PASS: TestMonitorTwoDirGood/bad-primary-new-addition (0.10s)
> > | --- PASS: TestMonitorTwoDirGood/bad-primary-same-addition (0.10s)
> > | --- PASS: TestMonitorTwoDirGood/good-primary-removal (0.10s)
> > | --- PASS: TestMonitorTwoDirGood/good-non-json-addition (0.10s)
> > | --- PASS: TestMonitorTwoDirGood/good-fallback-removal#01 (0.19s)
> >
> 
> Looks like flaky tests.
> 
> For example, debci runs these tests without problem. And I just
> verified in local sbuild as well.
> https://ci.debian.net/data/autopkgtest/testing/amd64/libp/libpod/23064901/log.gz

Did you check on s390x?  And FTBFS, even on one architecture, is
serious.

Bastian

-- 
Schshschshchsch.
-- The Gorn, "Arena", stardate 3046.2



Bug#1014309: libpod - FTBFS: FAIL: TestMonitorTwoDirGood (1.08s)

2022-07-03 Thread Shengjing Zhu
Control: severity -1 important

On Mon, Jul 4, 2022 at 3:27 AM Bastian Blank  wrote:
>
> Source: libpod
> Version: 3.4.7+ds1-3
> Severity: serious
> Tags: ftbfs
>
> libpod fails to build from source on several architectures:
> |
> | --- FAIL: TestMonitorTwoDirGood (1.08s)
> | --- PASS: TestMonitorTwoDirGood/good-fallback-addition (0.10s)
> | --- FAIL: TestMonitorTwoDirGood/good-primary-override (0.11s)
> | --- FAIL: TestMonitorTwoDirGood/good-fallback-removal (0.10s)
> | --- PASS: TestMonitorTwoDirGood/good-fallback-restore (0.17s)
> | --- PASS: TestMonitorTwoDirGood/bad-primary-new-addition (0.10s)
> | --- PASS: TestMonitorTwoDirGood/bad-primary-same-addition (0.10s)
> | --- PASS: TestMonitorTwoDirGood/good-primary-removal (0.10s)
> | --- PASS: TestMonitorTwoDirGood/good-non-json-addition (0.10s)
> | --- PASS: TestMonitorTwoDirGood/good-fallback-removal#01 (0.19s)
>

Looks like flaky tests.

For example, debci runs these tests without problem. And I just
verified in local sbuild as well.
https://ci.debian.net/data/autopkgtest/testing/amd64/libp/libpod/23064901/log.gz

--- PASS: TestMonitorTwoDirGood (0.90s)
--- PASS: TestMonitorTwoDirGood/good-fallback-addition (0.10s)
--- PASS: TestMonitorTwoDirGood/good-primary-override (0.10s)
--- PASS: TestMonitorTwoDirGood/good-fallback-removal (0.10s)
--- PASS: TestMonitorTwoDirGood/good-fallback-restore (0.10s)
--- PASS: TestMonitorTwoDirGood/bad-primary-new-addition (0.10s)
--- PASS: TestMonitorTwoDirGood/bad-primary-same-addition (0.10s)
--- PASS: TestMonitorTwoDirGood/good-primary-removal (0.10s)
--- PASS: TestMonitorTwoDirGood/good-non-json-addition (0.10s)
--- PASS: TestMonitorTwoDirGood/good-fallback-removal#01 (0.10s)

-- 
Shengjing Zhu



Bug#1009712: sv: fails to control the service on Hurd

2022-07-03 Thread Samuel Thibault
João Pedro Malhado, le dim. 03 juil. 2022 21:41:05 +0200, a ecrit:
> On Sun, Jul 03, 2022 at 06:37:46PM +0200, Samuel Thibault wrote:
> > João, le sam. 02 juil. 2022 20:53:55 +0200, a ecrit:
> > > I don't know why open64() is returning -1.
> > 
> > That's usually given in errno.
> 
> Trying to print the errno on gdb just after open_write()/open64() have run 
> gives
> 1073741902
> This looks strange and I cannot interpret what is going on.

This is not strange, see the values of E* macros

ENOSYS = 0x404e, /* Function not implemented */

So that's it.

Getting ENOSYS is odd, though, since open64 is defined in
glibc/sysdeps/mach/hurd/open.c

It's probably useful to debug step by step to see what function is
actually getting called.

Samuel



Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!

2022-07-03 Thread Paul Gevers

Hi all,

Just a minor follow-up. I just had to restart one of my arm64 workers again.

root@ci-worker-arm64-05:~# uname -a
Linux ci-worker-arm64-05 5.10.0-15-arm64 #1 SMP Debian 5.10.120-1 
(2022-06-09) aarch64 GNU/Linux


Anything you want me to extract from the current logs?

Paul


OpenPGP_signature
Description: OpenPGP digital signature


Bug#958464: Openjdk issue

2022-07-03 Thread John Mayton
I've been chasing this bug and several others for days now. May I ask 
what vpn your using if any. This problem started without updates to 
openjdk or any other software except kernel, openjdk-11 and 17 are both 
affected. Please check your update logs prior to this incident.




Bug#966558: ITP: fast5-research -- command line executable tools for python3-fast5-research

2022-07-03 Thread Bastian Germann

Control: retitle -1 ITP: fast5-research -- fast5 reading and writing (API to 
HDF containers)

The description was misleading in that it claimed to introduce executable tools 
only.
The prepared source package contains python3-fast5-research as well.



Bug#1014286: perl/experimental: FTBFS on mips64el: test failures

2022-07-03 Thread Niko Tyni
On Sun, Jul 03, 2022 at 04:29:22PM +0300, Niko Tyni wrote:
> Source: perl
> Version: 5.36.0-1
> Severity: serious
> Tags: ftbfs
> User: debian-p...@lists.debian.org
> Usertags: perl-5.36-transition
> X-Debbugs-Cc: debian-m...@lists.debian.org
> 
> The perl package in experimental fails to build from source
> on mips64el.
> 
>   https://buildd.debian.org/status/package.php?p=perl&suite=experimental
> 
> It looks like the perl binary dies with SIGSEGV in thread related tests
> during the test suite. This happened twice on different buildds.
> 
> I'm running a test build now on eller.d.o to see if it's reproducible.

The package builds fine for me on eller, though it failed twice in the
same way on the buildds (mipsel-osuosl-0[13]).

@debian-mips: any ideas? Could somebody please check if the package
builds for you?
-- 
Niko Tyni   nt...@debian.org



Bug#1009712: sv: fails to control the service on Hurd

2022-07-03 Thread João Pedro Malhado
X-Debbugs-CC: debian-h...@lists.debian.org

Hello Samuel,

On Sun, Jul 03, 2022 at 06:37:46PM +0200, Samuel Thibault wrote:
> João, le sam. 02 juil. 2022 20:53:55 +0200, a ecrit:
> > I don't know why open64() is returning -1.
> 
> That's usually given in errno.

Trying to print the errno on gdb just after open_write()/open64() have run gives
1073741902
This looks strange and I cannot interpret what is going on.

Best regards,
João



Bug#1014313: ITP: golang-github-emersion-go-mbox -- Package mbox parses the mbox file format into messages and formats messages into mbox files

2022-07-03 Thread Robin Jarry
Package: wnpp
Severity: wishlist
Owner: Robin Jarry 

* Package name: golang-github-emersion-go-mbox
  Version : 1.0.3-1
  Upstream Author : Simon Ser
* URL : https://github.com/emersion/go-mbox
* License : Expat
  Programming Lang: Go
  Description : Package mbox parses the mbox file format into messages and 
formats messages into mbox files

New dependency for aerc.



Bug#1014312: RFS: apprise/0.9.9-1 [ITP] -- Push Notifications that work with just about every platform

2022-07-03 Thread Nilson Silva

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name: apprise
   Version : 0.9.9-1
   Upstream Author : https://github.com/caronc/apprise/issues
 * URL : https://github.com/caronc/apprise
 * License : Expat
 * Vcs : https://salsa.debian.org/debian/apprise
   Section : misc

The source builds the following binary packages:

  apprise - Push Notifications that work with just about every platform

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/a/apprise/apprise_0.9.9-1.dsc

  salsa   https://salsa.debian.org/nilsonfsilva/apprise

Changes for the initial release:

 apprise (0.9.9-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #1014123)

Regards,
--
  Nilson Silva


Bug#1014311: ftp.debian.org: Signing service occasionally generates bad 254-byte signatures

2022-07-03 Thread Daniel Lewart
Package: ftp.debian.org
Severity: important

FTP team,

The Signing service occasionally generates bad 254-byte signatures
for kernel modules, rendering them unloadable.

Ben Hutchings has done some excellent detective work.

Please see #1012741:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012741

Here is one example:
  * linux-image-5.10.0-15-amd64
5.10.120-1 lib/modules/5.10.0-15-amd64/kernel/net/netfilter/xt_l2tp.ko

1) Which version of OpenSSL/libssl does the signing service use?

2) Are signing logs available?  Perhaps they could provide a clue.

Thank you!
Daniel Lewart
Urbana, Illinois



Bug#1014310: src:openjfx: fails to migrate to testing for too long: FTBFS on arm64 and armhf

2022-07-03 Thread Paul Gevers

Source: openjfx
Version: 11.0.11+0-1
Severity: serious
Control: close -1 11.0.11+1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:openjfx has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package failed to build from 
source on arm64 and armhf while it built there successfully in the past.


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=openjfx



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1014309: libpod - FTBFS: FAIL: TestMonitorTwoDirGood (1.08s)

2022-07-03 Thread Bastian Blank
Source: libpod
Version: 3.4.7+ds1-3
Severity: serious
Tags: ftbfs

libpod fails to build from source on several architectures:
| 
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-fallback-3506184749/a.json: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-primary-2094757904/0a.json: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-primary-2094757904/0a.json: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| expected:  
| actual:  &{[{/bin/sh [] [] 0xc00012c118}] [] [] [] [] []}
| === RUN   TestMonitorTwoDirGood/bad-primary-same-addition
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-primary-2094757904/a.json: parsing hook 
\"/tmp/hooks-test-primary-2094757904/a.json\": unrecognized hook version: 
\"-1\": parsing hook \"/tmp/hooks-test-primary-2094757904/0a.json\": 
unrecognized hook version: \"-1\""
| === RUN   TestMonitorTwoDirGood/good-primary-removal
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-primary-2094757904/a.json: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| === RUN   TestMonitorTwoDirGood/good-non-json-addition
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-fallback-3506184749/README: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-fallback-3506184749/README: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| === RUN   TestMonitorTwoDirGood/good-fallback-removal#01
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for 
/tmp/hooks-test-fallback-3506184749/a.json: parsing hook 
\"/tmp/hooks-test-primary-2094757904/0a.json\": unrecognized hook version: 
\"-1\""
| --- FAIL: TestMonitorTwoDirGood (1.08s)
| --- PASS: TestMonitorTwoDirGood/good-fallback-addition (0.10s)
| --- FAIL: TestMonitorTwoDirGood/good-primary-override (0.11s)
| --- FAIL: TestMonitorTwoDirGood/good-fallback-removal (0.10s)
| --- PASS: TestMonitorTwoDirGood/good-fallback-restore (0.17s)
| --- PASS: TestMonitorTwoDirGood/bad-primary-new-addition (0.10s)
| --- PASS: TestMonitorTwoDirGood/bad-primary-same-addition (0.10s)
| --- PASS: TestMonitorTwoDirGood/good-primary-removal (0.10s)
| --- PASS: TestMonitorTwoDirGood/good-non-json-addition (0.10s)
| --- PASS: TestMonitorTwoDirGood/good-fallback-removal#01 (0.19s)

Bastian

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

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



Bug#1014308: bullseye-pu: package llvm-toolchain-13/1:13.0.1-6~deb11u1

2022-07-03 Thread Emilio Pozuelo Monfort
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: pkg-llvm-t...@lists.alioth.debian.org

Hi,

This is the first of a series of backports needed for the upcoming
Firefox/Thunderbird 102 ESR. This backport is pretty straightforward,
and is a requirement for the new rustc. I have already uploaded the
package, but if you have any comments do let me know.

Thanks,
Emilio
diff -Nru llvm-toolchain-13-13.0.1/debian/changelog 
llvm-toolchain-13-13.0.1/debian/changelog
--- llvm-toolchain-13-13.0.1/debian/changelog   2022-06-04 15:30:38.0 
+0200
+++ llvm-toolchain-13-13.0.1/debian/changelog   2022-06-16 12:00:08.0 
+0200
@@ -1,3 +1,10 @@
+llvm-toolchain-13 (1:13.0.1-6~deb11u1) bullseye; urgency=medium
+
+  * Non-maintainer upload.
+  * Backport to bullseye.
+
+ -- Emilio Pozuelo Monfort   Thu, 16 Jun 2022 12:00:08 +0200
+
 llvm-toolchain-13 (1:13.0.1-6) unstable; urgency=medium
 
   [ John Paul Adrian Glaubitz ]


Bug#1014307: src:openjdk-11-jre-dcevm: fails to migrate to testing for too long: FTBFS on i386

2022-07-03 Thread Paul Gevers

Source: openjdk-11-jre-dcevm
Version: 11.0.12+7-1
Severity: serious
Control: close -1 11.0.15+1-1
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:openjdk-11-jre-dcevm has been trying to 
migrate for 61 days [2]. Hence, I am filing this bug. Your package fails 
to build from source on i386 while it built there successfully in the past.


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=openjdk-11-jre-dcevm



OpenPGP_signature
Description: OpenPGP digital signature


Bug#993796: knot-resolver 5.3.1-1+deb11u1 flagged for acceptance

2022-07-03 Thread Adam D Barratt
package release.debian.org
tags 993796 = bullseye pending
thanks

Hi,

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

Thanks for your contribution!

Upload details
==

Package: knot-resolver
Version: 5.3.1-1+deb11u1

Explanation: fix possible assertion failure in NSEC3 edge-case [CVE-2021-40083]



Bug#1014306: crun - seriously out of date

2022-07-03 Thread Bastian Blank
Package: crun
Version: 0.17+dfsg-1.1+b1
Severity: serious

Moin

crun was not uploaded since before the release of Debian 11.  It is now
seriously out of date and even fails hard as root, see #1012053.

Bastian

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

Kernel: Linux 5.18.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 crun depends on:
ii  libc62.33-7
ii  libcap2  1:2.44-1
ii  libseccomp2  2.5.4-1
ii  libsystemd0  251.2-7
ii  libyajl2 2.1.0-3

crun recommends no packages.

crun suggests no packages.

-- no debconf information



Bug#1014244: dhelp: Cron weekly gives email with /etc/cron.weekly/dhelp: error

2022-07-03 Thread Tim McConnell
Package: swish++
Version: 6.1.5-6
Followup-For: Bug #1014244
X-Debbugs-Cc: tmcconnell...@gmail.com

Package: dhelp
Version: 0.6.28
Severity: normal
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,

What led up to the situation?Weekly Cron job failed so I ran it manually via
sudo /etc/cron.weekly/dhelp.

What exactly did you do (or not do) that was effective (or ineffective)?Not
sure it was either, I think the cron job ran successfully. It ended with line
numbers in /usr/sbin/dhelp_parse.

What was the outcome of this action?Cron job ran but ended with:
using /usr/bin/index++ --config-file /usr/share/dhelp/config/swish++.conf
--index-file /var/lib/dhelp/documents.index --follow-links -
(/usr/lib/ruby/vendor_ruby/dhelp.rb:612:in `rescue in index'
/usr/lib/ruby/vendor_ruby/dhelp.rb:605:in `index'
/usr/sbin/dhelp_parse:171:in `do_deferred_indexing'
/usr/sbin/dhelp_parse:205:in `main'
/usr/sbin/dhelp_parse:221:in `')

What outcome did you expect instead? Not sure if that is a problem and if that
is why the weekly job failed? I checked the log file at /var/lib/dhelp/tmp and
in the earliest time 6:08 AM it shows:
Dhelp::IndexerError: Couldn't index  using /usr/bin/index++ --config-file
/usr/share/dhelp/config/swish++.conf --index-file
/var/lib/dhelp/documents.index --follow-links --incremental -
(/usr/lib/ruby/vendor_ruby/dhelp.rb:616:in `index'
/usr/sbin/dhelp_parse:171:in `do_deferred_indexing'
/usr/sbin/dhelp_parse:205:in `main'
/usr/sbin/dhelp_parse:221:in `')



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

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

Versions of packages dhelp depends on:
ii  doc-base0.11.1
ii  ghostscript 9.56.1~dfsg-1
ii  libcgi-pm-perl  4.54-1
ii  libdata-page-perl   2.03-1
ii  libhtml-parser-perl 3.78-1
ii  liblocale-gettext-perl  1.07-4+b2
ii  libtemplate-perl2.27-1+b4
ii  liburi-perl 5.10-1
ii  perl5.34.0-4
ii  poppler-utils   22.02.0-3
ii  ruby1:3.0+1
ii  ruby-debian 0.3.10+b6
ii  ruby-gettext3.3.3-2
ii  sensible-utils  0.0.17
ii  sgml-base   1.30
ii  swish++ 6.1.5-6
ii  ucf 3.0043

dhelp recommends no packages.

Versions of packages dhelp suggests:
ii  apache2 [httpd-cgi] 2.4.54-1
pn  catdvi  
ii  chromium [www-browser]  103.0.5060.53-1
ii  epiphany-browser [www-browser]  42.2-1
ii  firefox-esr [www-browser]   91.10.0esr-1
ii  info2www1.2.2.9-24.2
ii  links [www-browser] 2.27-1
ii  luakit [www-browser]1:2.3-1
ii  lynx [www-browser]  2.9.0dev.10-1
ii  man2html1.6g-14
ii  w3m [www-browser]   0.5.3+git20220429-1+b1

-- Configuration Files:
/etc/apache2/conf-available/dhelp.conf changed:

  Require local
  Options -Indexes -MultiViews


  Require local
  Options Indexes MultiViews FollowSymLinks

Alias /doc /usr/share/doc

/etc/apache2/conf.d/dhelp.conf changed:

  order deny,allow
  deny from all
  allow from localhost
  Options -Indexes -MultiViews


  order deny,allow
  deny from all
  allow from localhost
  Options Indexes MultiViews FollowSymLinks

Alias /doc /usr/share/doc
ScriptAlias /cgi-bin /usr/lib/cgi-bin

  AllowOverride None
  Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
  order allow,deny
  allow from all

Alias /doc/HTML /usr/share/doc/HTML
Alias /doc/dhelp/css /usr/share/doc/dhelp/css


-- no debconf information


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

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

Versions of packages swish++ depends on:
ii  libc6   2.33-7
ii  libstdc++6  12.1.0-2
ii  perl5.34.0-4
ii  zlib1g  1:1.2.11.dfsg-4

swish++ recommends no packages.

Versions of packages swish++ suggests:
pn  antiword
ii  poppler-utils [xpdf-utils]  22.02.0-3

-- no debconf information



Bug#1014305: ruby-net-sftp: Upgrade of ruby-net-ssh to 7.0.1 breaks the package

2022-07-03 Thread Philippe SWARTVAGHER

Package: ruby-net-sftp
Version: 1:3.0.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Control: affects -1 vagrant

Dear Maintainer,

I cannot use Vagrant anymore, and it turns out it comes from the ugprade
of ruby-net-ssh to version 7.0.1 which doesn't satisfy the dependency
requirements of ruby-net-sftp anymore
(https://sources.debian.org/src/ruby-net-sftp/1%3A3.0.0-1/net-sftp.gemspec/#L38)

% vagrant
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:2248:in
`raise_if_conflicts': Unable to activate net-sftp-3.0.0, because
net-ssh-7.0.1 conflicts with net-ssh (>= 5.0.0, < 7.0.0)
(Gem::ConflictError)
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1379:in `activate'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1417:in `block
in activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in
`activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in `activate'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:286:in `block in
activate_bin_path'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `synchronize'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `activate_bin_path'
from /usr/bin/vagrant:25:in `'

Philippe.



-- System Information:

Versions of packages ruby-net-sftp depends on:
ii ruby-net-ssh 1:7.0.1-1

ruby-net-sftp recommends no packages.

ruby-net-sftp suggests no packages.

-- no debconf information



Bug#1014304: nvidia-graphics-drivers-tesla-450: EoL (07/2023) driver should not be released with bookworm

2022-07-03 Thread Andreas Beckmann
Source: nvidia-graphics-drivers-tesla-450
Version: 450.191.01-2
Severity: normal
Tags: sid bookworm


The upstream support for the Tesla 450 driver series is scheduled to end
in 07/2023: https://docs.nvidia.com/datacenter/tesla/drivers/
i.e. around the expected release of bookworm.
It therefore shouldn't be released with bookworm.
The Tesla 470 driver series (EoL 07/2024) should support all devices and
features of the 450 series.
The severity of this bug will be raised once we approach the bookworm freeze.

Andreas



Bug#1014303: node-ajv-keywords: FTBFS: error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations.

2022-07-03 Thread Andreas Beckmann
Source: node-ajv-keywords
Version: 5.1.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

node-ajv-keywords/experimental recently started to FTBFS after
some (transitive) build-dependency got updated:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/node-ajv-keywords-5.1.0'
tsc
node_modules/@types/jest/index.d.ts(542,30): error TS2307: Cannot find module 
'jest-matcher-utils' or its corresponding type declarations.
make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/node-ajv-keywords-5.1.0'
make: *** [debian/rules:8: binary] Error 2

(The sid version still build fine.)


Andreas


node-ajv-keywords_5.1.0-2.log.gz
Description: application/gzip


Bug#972363: etesync-dav: unsatisfiable build dependencies: python3-radicale (<< 2.1.12)

2022-07-03 Thread Andreas Beckmann

Control: retitle -1 etesync-dav: unsatisfiable build dependencies: 
python3-radicale (< 3.1)
Control: found -1 0.20.4-1

On Fri, 16 Oct 2020 23:17:15 +0200 Andreas Beckmann  wrote:

etesync-dav/experimental cannot be built any more since it build-depends on
python3-radicale (<< 2.1.12) while sid already has 2.1.12-1.


That build-dependency had been bumped some time ago, but again the
requested version is no longer available. Sid currently has 3.1.7-1.

Andreas



Bug#1014300: nheko: Menus appear at unexpected places or not at all

2022-07-03 Thread Bruno Kleinert
Package: nheko
Version: 0.9.3+ds-1
Severity: normal
X-Debbugs-Cc: fu...@debian.org

Hi,

menus appear at unexpected places on the screen, i.e., not at the place where
the user clicks a button or when trying to open a context menu on an item.

Steps to reproduce:

1. Start nheko
2. Click on the '+' button on bottom left
3. The menu appears in upper left corner of the screen

Sometimes the expected menu does not show up anywhere on the screen at all.

Steps to reproduce:

1. Begin with the steps above
2. Move the mouse cursor into the menu which appeared in the upper left area
(don't click)
3. Press ESC
4. Now, click again the '+' button at the bottom left of nheko
5. The menu does not appear anywhere on the screen at all

I use GNOME 3 on Wayland to reproduce and don't know if the same issue occurs
with any other desktop environment or with an X11 based environment.

Cheers,
Bruno


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

Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.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 nheko depends on:
ii  gstreamer1.0-nice   0.1.18-2
ii  gstreamer1.0-qt51.20.3-1
ii  gstreamer1.0-vaapi  1.20.3-1
ii  libc6   2.33-7
ii  libcmark0.30.2  0.30.2-5
ii  libcurl47.84.0-1
ii  libevent-core-2.1-7 2.1.12-stable-5+b1
ii  libevent-pthreads-2.1-7 2.1.12-stable-5+b1
ii  libfmt8 8.1.1+ds1-2
ii  libgcc-s1   12.1.0-5
ii  libglib2.0-02.72.3-1
ii  libgstreamer-plugins-bad1.0-0   1.20.3-1
ii  libgstreamer-plugins-base1.0-0  1.20.3-2
ii  libgstreamer1.0-0   1.20.3-1
ii  liblmdb00.9.24-1
ii  libolm3 3.2.11~dfsg-1
ii  libqt5core5a5.15.4+dfsg-3
ii  libqt5dbus5 5.15.4+dfsg-3
ii  libqt5gui5  5.15.4+dfsg-3
ii  libqt5keychain1 0.13.2-5
ii  libqt5multimedia5   5.15.4-2
ii  libqt5multimedia5-plugins   5.15.4-2
ii  libqt5network5  5.15.4+dfsg-3
ii  libqt5qml5  5.15.4+dfsg-3
ii  libqt5quick55.15.4+dfsg-3
ii  libqt5svg5  5.15.4-2
ii  libqt5widgets5  5.15.4+dfsg-3
ii  libspdlog1 [libspdlog1-fmt8]1:1.9.2+ds-0.2
ii  libssl3 3.0.4-2
ii  libstdc++6  12.1.0-5
ii  libxcb-ewmh20.4.1-1.1
ii  libxcb1 1.14-3
ii  qml-module-qt-labs-animation5.15.4+dfsg-3
ii  qml-module-qt-labs-platform 5.15.4+dfsg-2
ii  qml-module-qt-labs-settings 5.15.4+dfsg-3
ii  qml-module-qtgraphicaleffects   5.15.4-2
ii  qml-module-qtmultimedia 5.15.4-2
ii  qml-module-qtquick-controls25.15.4+dfsg-2
ii  qml-module-qtquick-layouts  5.15.4+dfsg-3
ii  qml-module-qtquick-window2  5.15.4+dfsg-3
ii  qml-module-qtquick2 5.15.4+dfsg-3

Versions of packages nheko recommends:
ii  ca-certificates 20211016
ii  fonts-noto-color-emoji  2.034-1

nheko suggests no packages.

-- no debconf information



Bug#1014292: cyrus-imapd: FTBFS with Perl 5.36: expected expression before ‘{’ token

2022-07-03 Thread gregor herrmann
On Sun, 03 Jul 2022 17:06:15 +0300, Niko Tyni wrote:

>   x86_64-linux-gnu-gcc -c  -I../../../lib -I../../../perl/sieve 
> -I../../../perl/sieve/lib   -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv 
> -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -O2 -g   -DVERSION=\"0.01\" -DXS_VERSION=\"0.01\" 
> -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.36/CORE"  -DPERL_POLLUTE 
> managesieve.c
>   In file included from /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/perl.h:3855,
>from managesieve.xs:46:
>   /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/sv_inline.h: In function 
> ‘Perl_newSV_type’:
>   ../../../lib/assert.h:47:25: error: expected expression before ‘{’ token
>  47 | #define assert(ex)  {if (!(ex))assertionfailed(__FILE__, 
> __LINE__, #ex);}
> | ^
>   /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/handy.h:2787:28: note: in 
> expansion of macro ‘assert’
>2787 | #define perl_assert_ptr(p) assert( ((void*)(p)) != 0 )
> |^~
>   /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/handy.h:2792:47: note: in 
> expansion of macro ‘perl_assert_ptr’
>2792 | #define Zero(d,n,t) (MEM_WRAP_CHECK_(n,t) perl_assert_ptr(d), 
> (void)memzero((char*)(d), (n) * sizeof(t)))
> |   ^~~
>   /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/sv_inline.h:468:13: note: in 
> expansion of macro ‘Zero’
> 468 | Zero(new_body, type_details->body_size, char);
> | ^~~~
>   make[4]: *** [Makefile:346: managesieve.o] Error 1

This look like
https://github.com/cyrusimap/cyrus-imapd/issues/4123
and
https://github.com/cyrusimap/cyrus-imapd/pull/4140


Cheers,
gregor 

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


signature.asc
Description: Digital Signature


Bug#1014290: libgrokj2k: FTBFS with Perl 5.36: macro "utf8_to_utf16" requires 4 arguments, but only 1 given

2022-07-03 Thread gregor herrmann
On Sun, 03 Jul 2022 17:01:07 +0300, Niko Tyni wrote:

>   [ 68%] Building CXX object 
> src/bin/jp2/CMakeFiles/grk_decompress.dir/__/common/exif.cpp.o
>   cd /<>/obj-x86_64-linux-gnu/src/bin/jp2 && /usr/bin/c++ 
> -DSPDLOG_COMPILED_LIB -I/<>/obj-x86_64-linux-gnu/src/lib/jp2 
> -I/<>/obj-x86_64-linux-gnu/src/bin/common 
> -I/<>/src/lib/jp2 -I/<>/src/bin/common 
> -I/<>/src/bin/image_format -I/<>/src/bin/jp2 
> -I/<>/src/include -I/usr/lib/x86_64-linux-gnu/perl/5.36/CORE -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fvisibility=hidden -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wall -Wextra -Wconversion -Wsign-conversion -Wunused-parameter -std=gnu++20 
> -MD -MT src/bin/jp2/CMakeFiles/grk_decompress.dir/__/common/exif.cpp.o -MF 
> CMakeFiles/grk_decompress.dir/__/common/exif.cpp.o.d -o 
> CMakeFiles/grk_decompress.dir/__/common/exif.cpp.o -c 
> /<>/src/bin/common/exif.cpp
>   In file included from /<>/src/include/spdlog/fmt/fmt.h:25,
>from /<>/src/include/spdlog/common.h:45,
>from /<>/src/include/spdlog/spdlog.h:12,
>from /<>/src/bin/common/exif.cpp:38:
>   /<>/src/include/spdlog/fmt/bundled/format.h:1193:47: error: 
> macro "utf8_to_utf16" requires 4 arguments, but only 1 given
>1193 |   FMT_API explicit utf8_to_utf16(string_view s);
> |   ^

This might be addressed in the following upstream commit:
https://github.com/GrokImageCompression/grok/commit/5382e74729a56e7d9231f3fbc0f15b549ce22bfa


Cheers,
gregor

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


signature.asc
Description: Digital Signature


Bug#1009712: sv: fails to control the service on Hurd

2022-07-03 Thread Samuel Thibault
Hello,

João, le sam. 02 juil. 2022 20:53:55 +0200, a ecrit:
> I have put sv on a debugger and seems that the failure is happening when 
> trying
> to open the supervise/ok file (the file exists, and is a 0 bytes file),
> open_write() returns -1.

> I don't know why open64() is returning -1.

That's usually given in errno.

Samuel



Bug#1014293: libcpan-reporter-smoker-perl: FTBFS with Perl 5.36: tries to smoke the whole CPAN during build

2022-07-03 Thread gregor herrmann
On Sun, 03 Jul 2022 17:15:50 +0300, Niko Tyni wrote:

> This package fails to build from source with Perl 5.36 (currently in
> experimental.)
> 
> Build log at
> 
>   
> http://perl.debian.net/rebuild-logs/perl-5.36-throwaway/libcpan-reporter-smoker-perl_0.29-2/libcpan-reporter-smoker-perl_0.29-2_amd64-2022-06-13T03:37:58Z.build
> 
> It looks like the build times out because the test suite
> tries to test the whole CPAN. I believe this is because
> of the recent mitigations for CPAN checksums vulnerabilities.

This is interesting: In this log, t/parse_module_index.t finishes and
then there is no trace of any of the t/smoke-*.t tests.

In my local perl 5.36 chroot this looks different:

#v+
# Looks like your test exited with 2 just after 3.
t/smoke-all.t ... 
1..5
ok 1 - require CPAN::Reporter::Smoker;
ok 2 - CPAN::Reporter::Smoker->can('start')
ok 3 - Starting simulated smoke testing
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/5 subtests 
# Looks like your test exited with 2 just after 3.
t/smoke-disabled.t .. 
1..5
ok 1 - require CPAN::Reporter::Smoker;
ok 2 - CPAN::Reporter::Smoker->can('start')
ok 3 - Starting simulated smoke testing
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/5 subtests 

#   Failed test 'Number of reports in history'
#   at t/smoke-list-array.t line 60.
#  got: '0'
# expected: '2'
# Looks like you failed 1 test of 6.
t/smoke-list-array.t  
1..6
ok 1 - require CPAN::Reporter::Smoker;
ok 2 - CPAN::Reporter::Smoker->can('start')
ok 3 - Starting simulated smoke testing
ok 4 - Finished simulated smoke testing
ok 5 - require CPAN::Reporter::History;
not ok 6 - Number of reports in history
Lockfile removed.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/6 subtests 

#   Failed test 'Number of reports in history'
#   at t/smoke-list-file.t line 57.
#  got: '0'
# expected: '2'
# Looks like you failed 1 test of 6.
t/smoke-list-file.t . 
1..6
ok 1 - require CPAN::Reporter::Smoker;
ok 2 - CPAN::Reporter::Smoker->can('start')
ok 3 - Starting simulated smoke testing
ok 4 - Finished simulated smoke testing
ok 5 - require CPAN::Reporter::History;
not ok 6 - Number of reports in history
Lockfile removed.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/6 subtests 
# Looks like your test exited with 2 just after 3.
t/smoke-restart.t ... 
1..6
ok 1 - require CPAN::Reporter::Smoker;
ok 2 - CPAN::Reporter::Smoker->can('start')
ok 3 - Starting simulated smoke testing
Dubious, test returned 2 (wstat 512, 0x200)
Failed 3/6 subtests 

#   Failed test 'Number of reports in history'
#   at t/smoke-reverse.t line 63.
#  got: '0'
# expected: '2'
# Looks like you failed 1 test of 7.
t/smoke-reverse.t ... 
1..7
ok 1 - require CPAN::Reporter::Smoker;
ok 2 - CPAN::Reporter::Smoker->can('start')
ok 3 - Starting simulated smoke testing
ok 4 - Finished simulated smoke testing
ok 5 - saw dists in correct order
ok 6 - require CPAN::Reporter::History;
not ok 7 - Number of reports in history
Lockfile removed.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/7 subtests 

Test Summary Report
---
t/smoke-all.t (Wstat: 512 (exited 2) Tests: 3 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 5 tests but ran 3.
t/smoke-disabled.t(Wstat: 512 (exited 2) Tests: 3 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 5 tests but ran 3.
t/smoke-list-array.t  (Wstat: 256 (exited 1) Tests: 6 Failed: 1)
  Failed test:  6
  Non-zero exit status: 1
t/smoke-list-file.t   (Wstat: 256 (exited 1) Tests: 6 Failed: 1)
  Failed test:  6
  Non-zero exit status: 1
t/smoke-restart.t (Wstat: 512 (exited 2) Tests: 3 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 6 tests but ran 3.
t/smoke-reverse.t (Wstat: 256 (exited 1) Tests: 7 Failed: 1)
  Failed test:  7
  Non-zero exit status: 1
Files=10, Tests=88,  4 wallclock secs ( 0.03 usr  0.02 sys +  3.22 cusr  0.40 
csys =  3.67 CPU)
Result: FAIL
#v-
 
>   
> http://blogs.perl.org/users/neilb/2021/11/addressing-cpan-vulnerabilities-related-to-checksums.html
> 
>[CPAN.pm 2.29] now ignores any previously configured urllist and only
>uses cpan.org. If you want it to honour the urllist parameter instead,
>you must set the new pushy_https parameter to false.
> 
> I assume but haven't tested that setting pushy_https => 0 in
> t/data/MyConfig.pm will fix this.

With this change, the tests still fail under 5.36 (but pass with perl
5.34), but differently:

#v+
#   Failed test 'Number of reports in history'
#   at t/smoke-all.t line 47.
#  got: '0'
# expected: '6'
# Looks like you failed 1 test of 5.
t/smoke-all.t ... 
1..5
ok 1 - require CPAN::Reporter::Smoker;
ok 2 - CPAN::Reporter::Smoker->can('start')
ok 3 - Starting simulated smoke testing
ok 4 - require CPAN::Reporter::History;
not ok 5 - Number of reports in history
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/5 s

Bug#1013437: cups: Nothing prints from driverless IPP queues unless added via lpadmin

2022-07-03 Thread Brian Potkin
tags 1013437 - unreproducible
thanks



On Sun 03 Jul 2022 at 06:00:28 +0100, Gareth Evans wrote:

> On Sat  2 Jul 2022, at 23:43, Brian Potkin  wrote:
> [...]
> > On Fri 01 Jul 2022 at 13:37:07 +0100, Gareth Evans wrote:
> >> Driverless queues don't seem to work
> >> no matter how set up.
> >
> > Yet earlier (and at OpenPrinting) you said:
> >
> >   Having deleted all printers from system-config-printer,
> >   $ sudo lpadmin -p testq -v ipp://192.168.0.14/ipp/print -E -m 
> > driverless:ipp://192.168.0.14/ipp/print
> >   now succeeds, and so does printing to it.
> 
> Apologies, driverless queues only work if set up by lpadmin.
> Everywhere queues work from cups-web.

OK. That's clear enough.
> 
> May I suggest you may not be able to reproduce the bug as you (said
> you) don't have a fax-capable printer? 

Indeed you may. It had slipped my mind but it was the reason I thought
upstream was a reasonable place to go.

> It seems to me that my driverless print jobs end up in a fax queue if
> the queue is created by cups-web or s-c-p.  If this is the main
> symptom, I would be grateful if you would advise if this changes what
> the bug should be reported against.

The PPD generated by everywhere suits queues set up by lpadmin and the
CUPS web interface. One of the queues set up with cups-filters,
driverless doesn't work. I'd stick with cups-filters for the time being.

> I respect that you may no longer wish to be involved with this issue -
> thanks for your help - here is some further info for info's sake :)
> 
> At least one other user seems to have a similar problem:
> 
> "However, printing does not work, although the printer gets data, but
> then hangs."
> https://lists.debian.org/debian-user/2022/06/msg00558.html
> 
> The printer concerned there also appears to have airprint/fax
> https://productz.com/en/samsung-xpress-sl-c480fw/p/wxnG7
> 
> Substituting "gives up" for "hangs", this reflects my issue too.
> 
> I can find no significant difference between driverless PPDs, though
> everywhere PPDs do not include fax details, and everywhere queues
> added from cups-web succeed in printing.  Might this be another
> pointer to the issue?

You are making a good case.
> 
> $ history | grep testq-drvless
> sudo lpadmin -p testq-drvless -v ipp://192.168.0.14/ipp/print -E -m 
> driverless:ipp://192.168.0.14/ipp/print
> 
> $  sudo cat testq-drvless.ppd | grep -i fax
> *NickName: "Brother MFC-L2740DW series, Fax, driverless, cups-filters 1.28.7"
> *cupsIPPFaxOut: True
> *OpenUI *faxPrefix/Pre-Dial Number: PickOne
> *OrderDependency: 10 AnySetup *faxPrefix
> *DefaultfaxPrefix: None
> *faxPrefix None: ""
> *CloseUI: *faxPrefix
> *CustomfaxPrefix True: ""
> *ParamCustomfaxPrefix Text: 1 string 0 64
> 
> $ history | grep ippeve
> sudo lpadmin -p testq-ippeve -v ipp://192.168.0.14/ipp/print -E -m everywhere
> 
> $ sudo cat testq-ippeve.ppd | grep -i fax
> $ 
> 
> 
> Though even testq-drvless sometimes shows strange job attribs in s-c-p: 
> 
> "job-printer-state-message: Phone number for fax not valid! Fax cannot be 
> sent"
> "job-printer-uri: ipp://localhost/printers/testq-drvless"
> 
> though the job (from geany) actually printed.  
> 
> 
> $ sudo diff CUPSWEBDL.ppd testq-drvless.ppd
> 20c20
> < *APSupplies: "http://mfcl2740dw.local./net/net/airprint.html";
> ---
> > *APSupplies: "http://192.168.0.14/net/net/airprint.html";
> 
> $ sudo diff CUPSWEBDL.ppd SCPDL.ppd
> $
> 
> $ ping mfcl2740dw.local
> PING mfcl2740dw.local (192.168.0.14) 56(84) bytes of data.
> 64 bytes from 192.168.0.14 (192.168.0.14): icmp_seq=1 ttl=255 time=9.80 ms
> 
> $ ping mfcl2740dw.local.
> PING mfcl2740dw.local. (192.168.0.14) 56(84) bytes of data.
> 64 bytes from 192.168.0.14 (192.168.0.14): icmp_seq=1 ttl=255 time=3.62 ms
> 
> $ sudo lpadmin -p testqhostname -v ipp://mfcl2740dw.local/ipp/print -E -m 
> driverless:ipp://mfcl2740dw.local/ipp/print 
> lpadmin: Printer drivers are deprecated and will stop working in a future 
> version of CUPS.
> 
> $ sudo diff testqhostname.ppd CUPSWEBDL.ppd
> $ 
> 
> 
> $ lp -d testqhostname /etc/nsswitch.conf
> request id is testqhostname-56 (1 file(s))
> 
> Succeeds.

Good.

> /var/log/cups/error_log
> [...]
> 2833 D [03/Jul/2022:02:05:45 +0100] Create-Job 
> ipp://localhost/printers/testqhostname
> [...]
> 3359 D [03/Jul/2022:02:05:46 +0100] [Client 605] Processing GET 
> /printers/testqhostname.ppd
> 3360 D [03/Jul/2022:02:05:46 +0100] [Client 605] 
> filename="/etc/cups/ppd/testqhostname.ppd", type=application/vnd.cups-ppd
> [...]
> 3794 D [03/Jul/2022:02:05:47 +0100] [Job 56] job-uri uri 
> ipp://mfcl2740dw.local:631/ipp/print/job-225
> 3805 D [03/Jul/2022:02:05:47 +0100] [Job 56] printer-uri uri 
> ipp://mfcl2740dw.local:631/ipp/print
> 
> 
> $ lp -d CUPSWEBDL /etc/nsswitch.conf
> request id is CUPSWEBDL-55 (1 file(s))
> 
> Fails.

Not good, obviously.

> /var/log/cups/error_log
> [...]
> 70 D [03/Jul/2022:02:04:51 +0100] Create-Job 
> ipp://localhost/printers/CUPSWEBDL
> [from line 1349]
> 71 D [03/Jul/202

Bug#1014299: linux-image-5.10.0-15-amd64: No audio on Thinkpad Helix 2 (broadwell-rt286); "firmware ready timeout"

2022-07-03 Thread Benjamin Moody
Package: src:linux
Version: 5.10.120-1
Severity: normal
X-Debbugs-Cc: benjamin.mo...@gmail.com

Dear Maintainer,

On a Thinkpad Helix 2, the internal audio devices (speaker,
microphone, and headset port) work with kernel 4.19.0-20-amd64
(4.19.235-1), but are broken with kernel 5.10.0-15-amd64 (5.10.120-1).

For example:

pasuspender -- aplay -D plughw:CARD=broadwellrt286,DEV=0 \
 /usr/share/sounds/alsa/Front_Left.wav

This command works as expected on 4.19.0-20-amd64; on 5.10.0-15-amd64
it gives the error:

aplay: main:830: audio open error: Invalid argument

On the newer kernel, the following messages appear in dmesg:

intel_catpt INT3438:00: firmware: direct-loading firmware intel/IntcSST2.bin
intel_catpt INT3438:00: firmware ready timeout
intel_catpt INT3438:00: boot firmware failed: -110
intel_catpt INT3438:00: ASoC: error at snd_soc_pcm_component_pm_runtime_get 
on catpt-platform: -110
 Codec: ASoC: BE open failed -110
 System PCM: ASoC: failed to start some BEs -110

It looks like the broadwell-rt286 and other "soc" audio drivers were
somewhat restructured between these two kernel releases and I'm
guessing that's when this bug was introduced.

(Confusingly, the keyboard/dock (at least the "Ultrabook Pro" version)
has its own internal speaker which appears as a USB audio device.
That device seems to work properly, but is not so useful since it
doesn't have a headphone port or a microphone.)


-- Package-specific info:
** Version:
Linux version 5.10.0-15-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.120-1 (2022-06-09)

** Command line:
BOOT_IMAGE=/vmlinuz-5.10.0-15-amd64 
root=UUID=b5d1c7d2-b38b-475e-a0c8-5715770117e1 ro acpi.ec_no_wakeup=1 quiet

** Tainted: IOE (14336)
 * workaround for bug in platform firmware applied
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[   17.359747] input: Wacom HID 5014 Finger as 
/devices/pci:00/INT3432:00/i2c-0/i2c-WCOM5014:00/0018:056A:5014.0003/input/input25
[   17.369935] wacom 0018:056A:5014.0003: hidraw2: I2C HID v1.00 Device 
[WCOM5014:00 056A:5014] on i2c-WCOM5014:00
[   17.370134] input: broadwell-rt286 Headset as 
/devices/platform/broadwell-audio/sound/card1/input23
[   17.419836] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: 
(null)
[   17.419875] ext4 filesystem being mounted at /boot supports timestamps until 
2038 (0x7fff)
[   17.426114] input: HDA Intel HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.0/sound/card0/input19
[   17.426838] input: HDA Intel HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.0/sound/card0/input20
[   17.468644] input: HDA Intel HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.0/sound/card0/input21
[   17.468932] input: Wacom HID 114 Pen as 
/devices/pci:00/INT3433:00/i2c-1/i2c-WCOM0009:00/0018:056A:0114.0005/input/input27
[   17.469009] input: HDA Intel HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.0/sound/card0/input22
[   17.469108] wacom 0018:056A:0114.0005: hidraw3: I2C HID v1.00 Mouse 
[WCOM0009:00 056A:0114] on i2c-WCOM0009:00
[   17.505093] iwlwifi :06:00.0: Detected Intel(R) Dual Band Wireless AC 
7265, REV=0x210
[   17.519332] iwlwifi :06:00.0: Applying debug destination EXTERNAL_DRAM
[   17.520172] iwlwifi :06:00.0: Allocated 0x0040 bytes for firmware 
monitor.
[   17.530215] iwlwifi :06:00.0: base HW address: 34:13:e8:4d:47:39
[   17.590916] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[   17.591280] thermal thermal_zone10: failed to read out thermal zone (-61)
[   17.602813] iwlwifi :06:00.0 wlp6s0: renamed from wlan0
[   17.637654] audit: type=1400 audit(1656861896.225:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=736 comm="apparmor_parser"
[   17.640988] audit: type=1400 audit(1656861896.229:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" 
pid=731 comm="apparmor_parser"
[   17.644701] audit: type=1400 audit(1656861896.233:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/redshift" pid=733 
comm="apparmor_parser"
[   17.648641] audit: type=1400 audit(1656861896.237:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-oopslash" 
pid=743 comm="apparmor_parser"
[   17.652794] audit: type=1400 audit(1656861896.241:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=734 
comm="apparmor_parser"
[   17.652803] audit: type=1400 audit(1656861896.241:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=734 comm="apparmor_parser"
[   17.652845] audit: type=1400 audit(1656861896.241:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid

Bug#1013880: nvidia-graphics-drivers-tesla-470 470.129.06-6~deb11u1 flagged for acceptance

2022-07-03 Thread Adam D Barratt
package release.debian.org
tags 1013880 = bullseye pending
thanks

Hi,

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

Thanks for your contribution!

Upload details
==

Package: nvidia-graphics-drivers-tesla-470
Version: 470.129.06-6~deb11u1

Explanation: new upstream stable release; fix out-of-bounds write issue 
[CVE-2022-28181], out-of-bounds read issue [CVE-2022-28183], denial of service 
issues [CVE-2022-28184 CVE-2022-28191 CVE-2022-28192]



Bug#1013879: nvidia-graphics-drivers 470.129.06-6~deb11u1 flagged for acceptance

2022-07-03 Thread Adam D Barratt
package release.debian.org
tags 1013879 = bullseye pending
thanks

Hi,

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

Thanks for your contribution!

Upload details
==

Package: nvidia-graphics-drivers
Version: 470.129.06-6~deb11u1

Explanation: new upstream stable release; fix out-of-bounds write issue 
[CVE-2022-28181], out-of-bounds read issue [CVE-2022-28183], denial of service 
issues [CVE-2022-28184 CVE-2022-28191 CVE-2022-28192]



Bug#917541: ITP - Python-xxhash - Python Binding for xxHash

2022-07-03 Thread Bastian Germann

X-Debbugs-Cc: r...@finnie.org

On Sat, 5 Jan 2019 12:06:34 -0800 Ryan Finnie wrote:

I actually began (and finished) work on packaging python-xxhash before
noticing this ITP.  My initial packaging is at:
https://github.com/rfinnie/python-xxhash-pkg-debian

Since libxxhash0 was recently packaged, I've patched the Python module
to use the shared library instead of the module's local copy.  Aside
from that, relatively normal Python module.  The module itself is Python
2.7 compatible but I only packaged Python 3, per lintian
new-package-should-not-package-python2-module.

Feel free to use this packaging base if you want and set yourself as the
maintainer.  I'd also be happy with being the maintainer (I'm a DM, not
a DD so I would require an initial sponsorship as DMs aren't allowed to
upload new packages), your choice.



Ryan, please feel free to own this bug and go ahead with packaging.



Bug#1014280: pdl: please make the libtext-balanced-perl dependency versioned

2022-07-03 Thread Sebastiaan Couwenberg

Control: tags -1 pending

On 7/3/22 14:09, Niko Tyni wrote:

So, please make the pdl dependency (both build and run time if applicable)
versioned so I can add the metadata on the perl side after that.


This is fixed in git and an upload to unstable will follow shortly.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



Bug#1014297: ITP: pytoolconfig -- Python Tool Configuration

2022-07-03 Thread Boyuan Yang
Package: wnpp
Severity: wishlist
Owner: Boyuan Yang 

* Package name: pytoolconfig
  Version : 1.1.2
  Upstream Author : Bagel Jr
* URL : https://github.com/bageljrkhanofemus/pytoolconfig
* License : GPL-3.0-only
  Programming Lang: Python
  Description : Python Tool Configuration

 The goal of this project is to manage configuration for python tools,
 such as black and rope, and add support for a pyproject.toml
 configuration file.

I intend to maintain this package as part of the Debian Python Team.
Packaging work will be stored at
https://salsa.debian.org/python-team/packages/pytoolconfig .

Thanks,
Boyuan Yang


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


Bug#1014296: polymake: FTBFS with Perl 5.36: HVhek_UNSHARED’ was not declared in this scope

2022-07-03 Thread Benjamin Lorenz

Hi,

the attached patch should fix the build with perl 5.36:
- adapt to renamed HVhek_UNSHARED
- adjust for changes in the complement operation

Best,
Benjamin Lorenz

On 03/07/2022 16.33, Niko Tyni wrote:

Source: polymake
Version: 4.6-3
Tags: ftbfs
User: debian-p...@lists.debian.org
Usertags: perl-5.36-transition

This package fails to build from source with Perl 5.36 (currently in
experimental.)

Build log at

   
http://perl.debian.net/rebuild-logs/perl-5.36-throwaway/polymake_4.6-3/polymake_4.6-3_amd64-2022-06-09T09:42:58Z.build

Excerpt:

   FAILED: 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RefHash.o
 g++ -c -o /<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RefHash.o -MMD -MT 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RefHash.o -MF 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RefHash.o.d -fPIC -pipe -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -ftemplate-depth-200 -fno-strict-aliasing -fopenmp -Wshadow 
-Wlogical-op -Wconversion -Wzero-as-null-pointer-constant -Wno-parentheses -Wno-error=unused-function -Wno-stringop-overflow -Wno-array-bounds -Wno-maybe-uninitialized 
-Wno-free-nonheap-object -DPOLYMAKE_WITH_FLINT  -DPOLYMAKE_DEBUG=0 -DNDEBUG -O2 -I/usr/lib/x86_64-linux-gnu/perl/5.36/CORE -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv 
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -DPerlVersion=5360 -Wno-nonnull  
-I/<>/include/core-wrappers -I/<>/include/core 
/<>/build/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RefHash.cc && : 'COMPILER_USED=11.3.0'
   /<>/lib/core/src/perl/RefHash.xxs: In member function ‘SV* 
pm::perl::glue::{anonymous}::tmp_keysv::set(SV*)’:
   /<>/lib/core/src/perl/RefHash.xxs:74:22: error: 
‘HVhek_UNSHARED’ was not declared in this scope; did you mean ‘HVhek_NOTSHARED’?
  74 |HEK_FLAGS(hekp) = HVhek_UNSHARED;
 |  ^~
 |  HVhek_NOTSHARED
   [954/965]   g++ -c -o /<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/Poly.o -MMD -MT 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/Poly.o -MF 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/Poly.o.d -fPIC -pipe -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -ftemplate-depth-200 -fno-strict-aliasing -fopenmp -Wshadow 
-Wlogical-op -Wconversion -Wzero-as-null-pointer-constant -Wno-parentheses -Wno-error=unused-function -Wno-stringop-overflow -Wno-array-bounds -Wno-maybe-uninitialized 
-Wno-free-nonheap-object -DPOLYMAKE_WITH_FLINT  -DPOLYMAKE_DEBUG=0 -DNDEBUG -O2 -I/usr/lib/x86_64-linux-gnu/perl/5.36/CORE -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv 
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -DPerlVersion=5360 -Wno-nonnull  
-I/<>/include/core-wrappers -I/<>/include/core 
/<>/build/perlx/5.36.0/x86_64-linux-gnu-thread-multi/Poly.cc && : 'COMPILER_USED=11.3.0'
   [955/965]   g++ -c -o /<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RuleGraph.o -MMD -MT 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RuleGraph.o -MF 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RuleGraph.o.d -fPIC -pipe -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -ftemplate-depth-200 -fno-strict-aliasing -fopenmp -Wshadow 
-Wlogical-op -Wconversion -Wzero-as-null-pointer-constant -Wno-parentheses -Wno-error=unused-function -Wno-stringop-overflow -Wno-array-bounds -Wno-maybe-uninitialized 
-Wno-free-nonheap-object -DPOLYMAKE_WITH_FLINT  -DPOLYMAKE_DEBUG=0 -DNDEBUG -O2 -I/usr/lib/x86_64-linux-gnu/perl/5.36/CORE -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv 
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -DPerlVersion=5360 -Wno-nonnull  
-I/<>/include/core-wrappers -I/<>/include/core 
/<>/build/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RuleGraph.cc && : 'COMPILER_USED=11.3.0'
   ninja: build stopped: subcommand failed.
   make[1]: *** [debian/rules:56: override_dh_auto_build] Error 1
   make[1]: Leaving directory '/<>'
   make: *** [debian/rules:35: build] Error 2
  
diff --git a/lib/core/src/perl/RefHash.xxs b/lib/core/src/perl/RefHash.xxs
index f6087a10aa..fbf7309a50 100644
--- a/lib/core/src/perl/RefHash.xxs
+++ b/lib/core/src/perl/RefHash.xxs
@@ -71,7 +71,11 @@ SV* tmp_keysv::set(SV* keysv)
Copy(obj.keyp, HEK_KEY(hekp), sizeof(SV*), char);
HEK_LEN(hekp) = sizeof(SV*);
HEK_HASH(hekp) = U32(obj.keyl >> 4);  // hash value
+#if defined(HVhek_NOTSHARED)
+   HEK_FLAGS(hekp) = HVhek_NOTSHARED;
+#else
HEK_FLAGS(hekp) = HVhek_UNSHARED;
+#endif
sv.sv_any = &xpv;
sv.sv_refcnt = 1;
sv.sv_flags = SVt_PVIV | SVf_IVisUV | SVf_POK | 

Bug#898408: ITP: python3-aiohue -- Python3 asyncio package to talk to Philips Hue

2022-07-03 Thread Bastian Germann

Control: retitle -1 ITP: aiohue -- Python3 asyncio package to talk to Philips 
Hue

On Fri, 11 May 2018 13:52:39 +0500 Srujan Kumar Bojjam  
wrote:

Package: python3-aiohue
Severity: wishlist

Package name : aiohue
Version : 1.3.1
Upstream Author : Paulus Schoutsen 
Upstream URL : https://github.com/balloob/aiohue
License : Apache-2.0
Programming Lang: Python3
Description : Python3 asyncio package to talk to Philips Hue

Package Repository Url: 
https://salsa.debian.org/archanac-guest/python3-aiohue


Are you still interested in packaging this?
You should file a RFS on sponsorship-requests if the FreedomBox packaging team 
does not have
a specific way to RFS. Please do not use the python3- prefix for the source 
package name.

Thanks,
Bastian



Bug#1014296: polymake: FTBFS with Perl 5.36: HVhek_UNSHARED’ was not declared in this scope

2022-07-03 Thread Niko Tyni
Source: polymake
Version: 4.6-3
Tags: ftbfs
User: debian-p...@lists.debian.org
Usertags: perl-5.36-transition

This package fails to build from source with Perl 5.36 (currently in
experimental.)

Build log at

  
http://perl.debian.net/rebuild-logs/perl-5.36-throwaway/polymake_4.6-3/polymake_4.6-3_amd64-2022-06-09T09:42:58Z.build

Excerpt:

  FAILED: 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RefHash.o
 
g++ -c -o 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RefHash.o
 -MMD -MT 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RefHash.o
 -MF 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RefHash.o.d
 -fPIC -pipe -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++14 -ftemplate-depth-200 -fno-strict-aliasing 
-fopenmp -Wshadow -Wlogical-op -Wconversion -Wzero-as-null-pointer-constant 
-Wno-parentheses -Wno-error=unused-function -Wno-stringop-overflow 
-Wno-array-bounds -Wno-maybe-uninitialized -Wno-free-nonheap-object 
-DPOLYMAKE_WITH_FLINT  -DPOLYMAKE_DEBUG=0 -DNDEBUG -O2 
-I/usr/lib/x86_64-linux-gnu/perl/5.36/CORE -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64  -DPerlVersion=5360 -Wno-nonnull  
-I/<>/include/core-wrappers -I/<>/include/core 
/<>/build/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RefHash.cc && 
: 'COMPILER_USED=11.3.0'
  /<>/lib/core/src/perl/RefHash.xxs: In member function ‘SV* 
pm::perl::glue::{anonymous}::tmp_keysv::set(SV*)’:
  /<>/lib/core/src/perl/RefHash.xxs:74:22: error: ‘HVhek_UNSHARED’ 
was not declared in this scope; did you mean ‘HVhek_NOTSHARED’?
 74 |HEK_FLAGS(hekp) = HVhek_UNSHARED;
|  ^~
|  HVhek_NOTSHARED
  [954/965]   g++ -c -o 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/Poly.o
 -MMD -MT 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/Poly.o
 -MF 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/Poly.o.d
 -fPIC -pipe -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++14 -ftemplate-depth-200 -fno-strict-aliasing 
-fopenmp -Wshadow -Wlogical-op -Wconversion -Wzero-as-null-pointer-constant 
-Wno-parentheses -Wno-error=unused-function -Wno-stringop-overflow 
-Wno-array-bounds -Wno-maybe-uninitialized -Wno-free-nonheap-object 
-DPOLYMAKE_WITH_FLINT  -DPOLYMAKE_DEBUG=0 -DNDEBUG -O2 
-I/usr/lib/x86_64-linux-gnu/perl/5.36/CORE -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64  -DPerlVersion=5360 -Wno-nonnull  
-I/<>/include/core-wrappers -I/<>/include/core 
/<>/build/perlx/5.36.0/x86_64-linux-gnu-thread-multi/Poly.cc && : 
'COMPILER_USED=11.3.0'
  [955/965]   g++ -c -o 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RuleGraph.o
 -MMD -MT 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RuleGraph.o
 -MF 
/<>/build/Opt/lib/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RuleGraph.o.d
 -fPIC -pipe -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++14 -ftemplate-depth-200 -fno-strict-aliasing 
-fopenmp -Wshadow -Wlogical-op -Wconversion -Wzero-as-null-pointer-constant 
-Wno-parentheses -Wno-error=unused-function -Wno-stringop-overflow 
-Wno-array-bounds -Wno-maybe-uninitialized -Wno-free-nonheap-object 
-DPOLYMAKE_WITH_FLINT  -DPOLYMAKE_DEBUG=0 -DNDEBUG -O2 
-I/usr/lib/x86_64-linux-gnu/perl/5.36/CORE -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64  -DPerlVersion=5360 -Wno-nonnull  
-I/<>/include/core-wrappers -I/<>/include/core 
/<>/build/perlx/5.36.0/x86_64-linux-gnu-thread-multi/RuleGraph.cc 
&& : 'COMPILER_USED=11.3.0'
  ninja: build stopped: subcommand failed.
  make[1]: *** [debian/rules:56: override_dh_auto_build] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:35: build] Error 2
 
-- 
Niko Tyni   nt...@debian.org



Bug#1014295: libwx-perl-processstream-perl: FTBFS with Perl 5.36: build hangs

2022-07-03 Thread Niko Tyni
Source: libwx-perl-processstream-perl
Version: 0.32-1.1
Tags: ftbfs
User: debian-p...@lists.debian.org
Usertags: perl-5.36-transition

This package fails to build from source with Perl 5.36 (currently in
experimental.)

Build log at

  
http://perl.debian.net/rebuild-logs/perl-5.36-throwaway/libwx-perl-processstream-perl_0.32-1.1/libwx-perl-processstream-perl_0.32-1.1_amd64-2022-06-13T09:38:04Z.build

Excerpt:

  t/00-load.t  
  1..1
  ok 1 - use Wx::Perl::ProcessStream;
  ok
  
  #   Failed test at t/01-events.t line 59.
  #  got: undef
  # expected: '0'
  
  #   Failed test at t/01-events.t line 80.
  #  got: undef
  # expected: 'HELLO WORLD'
  
  #   Failed test at t/01-events.t line 94.
  #  got: undef
  # expected: 'HELLO WORLD'
  
  #   Failed test at t/01-events.t line 117.
  #  got: undef
  # expected: 'HELLO WORLD'
  
  #   Failed test at t/01-events.t line 131.
  #  got: undef
  # expected: 'HELLO WORLD'
  
  #   Failed test at t/01-events.t line 152.
  #  got: ''
  # expected: anything else
  
  #   Failed test at t/01-events.t line 170.
  #  got: ''
  # expected: 'ONE-TWO-THREE'
  
  #   Failed test at t/01-events.t line 174.
  #  got: ''
  # expected: 'FOUR'
  
  #   Failed test at t/01-events.t line 192.
  #  got: ''
  # expected: 'ECHO:TEST STDIN 1-TEST STDIN 2'
  E: Build killed with signal TERM after 150 minutes of inactivity

-- 
Niko Tyni   nt...@debian.org



Bug#1014294: libtap-formatter-junit-perl: FTBFS with Perl 5.36: Failed test 't/data/tests/bailout'

2022-07-03 Thread Niko Tyni
Source: libtap-formatter-junit-perl
Version: 0.11-1.1
Tags: ftbfs
User: debian-p...@lists.debian.org
Usertags: perl-5.36-transition

This package fails to build from source with Perl 5.36 (currently in
experimental.)

Build log at

  
http://perl.debian.net/rebuild-logs/perl-5.36-throwaway/libtap-formatter-junit-perl_0.11-1.1/libtap-formatter-junit-perl_0.11-1.1_amd64-2022-06-09T01:27:50Z.build

Excerpt:

  Building TAP-Formatter-JUnit
 dh_auto_test
  dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
/usr/bin/perl Build test --verbose 1
  
  #   Failed test 't/data/tests/bailout'
  #   at t/formatter.t line 40.
  # During compare:
  # no element found at line 1, column 0, byte -1
  # Looks like you failed 1 test of 22.
  t/formatter.t . 
  1..22
  ok 1 - t/data/tests/bad_chars
  not ok 2 - t/data/tests/bailout
  ok 3 - t/data/tests/descriptive
  ok 4 - t/data/tests/descriptive_trailing
  ok 5 - t/data/tests/die
  ok 6 - t/data/tests/die_head_end
  ok 7 - t/data/tests/die_last_minute
  ok 8 - t/data/tests/die_unfinished
  ok 9 - t/data/tests/empty
  ok 10 - t/data/tests/no_nums
  ok 11 - t/data/tests/simple
  ok 12 - t/data/tests/simple_fail
  ok 13 - t/data/tests/simple_yaml
  ok 14 - t/data/tests/skip
  ok 15 - t/data/tests/skip_nomsg
  ok 16 - t/data/tests/skipall
  ok 17 - t/data/tests/skipall_nomsg
  ok 18 - t/data/tests/stdout_stderr
  ok 19 - t/data/tests/todo
  ok 20 - t/data/tests/todo_inline
  ok 21 - t/data/tests/todo_misparse
  ok 22 - t/data/tests/too_many
  Dubious, test returned 1 (wstat 256, 0x100)
  Failed 1/22 subtests 

-- 
Niko Tyni   nt...@debian.org



Bug#1013526: libtickit-widget-scrollbox-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 255

2022-07-03 Thread Niko Tyni
Control: user debian-p...@lists.debian.org
Control: usertag -1 perl-5.36-transition

On Sat, Jun 25, 2022 at 10:09:46AM +0300, Damyan Ivanov wrote:
> Control: retitle -1 libtickit-widget-scrollbox-perl: intermittent memory 
> corruption in t/02input-key.t and t/03input-mouse.t
> 
> I can reproduce this when running 02input-key.t and 03input-key.t in 
> a loop. The symptom is the same - "malloc_consolidate(): unaligned 
> fastbin chunk detected" error message and the tests exits with Wstat 
> 134 after saying "All 14 subtests passed".
> 
> Wstat 134 is SIGABRT. Looks like a memory corruption of some sort.

We're seeing this too in Perl 5.36 test rebuilds. Possibly it's even
more reproducible there, seems to always fail for us.

  
http://perl.debian.net/rebuild-logs/perl-5.36-throwaway/libtickit-widget-scrollbox-perl_0.11-1/libtickit-widget-scrollbox-perl_0.11-1_amd64-2022-06-14T06:54:08Z.build

-- 
Niko Tyni   nt...@debian.org



Bug#775827: RFA: grok -- powerful pattern-matching and reacting tool

2022-07-03 Thread Ankit Pandey
Hello Stig,

I am interested in adopting this package. I have been using grok in
Elasticsearch stack and its power has no match for the use case. Also, it
will be the first package for me to maintain so I want to work on something
which I am a bit familiar with.
Let me know anything as needed.

Regards,
Ankit


Bug#1014293: libcpan-reporter-smoker-perl: FTBFS with Perl 5.36: tries to smoke the whole CPAN during build

2022-07-03 Thread Niko Tyni
Source: libcpan-reporter-smoker-perl
Version: 0.29-2
Tags: ftbfs upstream
User: debian-p...@lists.debian.org
Usertags: perl-5.36-transition

This package fails to build from source with Perl 5.36 (currently in
experimental.)

Build log at

  
http://perl.debian.net/rebuild-logs/perl-5.36-throwaway/libcpan-reporter-smoker-perl_0.29-2/libcpan-reporter-smoker-perl_0.29-2_amd64-2022-06-13T03:37:58Z.build

It looks like the build times out because the test suite
tries to test the whole CPAN. I believe this is because
of the recent mitigations for CPAN checksums vulnerabilities.

  
http://blogs.perl.org/users/neilb/2021/11/addressing-cpan-vulnerabilities-related-to-checksums.html

   [CPAN.pm 2.29] now ignores any previously configured urllist and only
   uses cpan.org. If you want it to honour the urllist parameter instead,
   you must set the new pushy_https parameter to false.

I assume but haven't tested that setting pushy_https => 0 in
t/data/MyConfig.pm will fix this.

Upstream is most probably affected similarly as there are no test reports
for CPAN-Reporter-Smoker since Perl 5.35.6.
-- 
Niko Tyni   nt...@debian.org



Bug#1014291: libaudio-ecasound-perl: FTBFS with Perl 5.36: test failure

2022-07-03 Thread Niko Tyni
Source: libaudio-ecasound-perl
Version: 1.01-4
Tags: ftbfs
User: debian-p...@lists.debian.org
Usertags: perl-5.36-transition

This package fails to build from source with Perl 5.36 (currently in
experimental.)

Build log at

  
http://perl.debian.net/rebuild-logs/perl-5.36/libaudio-ecasound-perl_1.01-4/libaudio-ecasound-perl_1.01-4+b5_amd64-2022-06-10T00:27:14Z.build

Excerpt:

  t/ecasound.t .. 
  1..46
  # Running under perl version 5.036000 for linux
  # Current time local: Fri Jun 10 00:27:31 2022
  # Current time GMT:   Fri Jun 10 00:27:31 2022
  # Using Test.pm version 1.31
  ok 1
  ok 2
  ok 3
  ok 4
  ok 5
  ok 6
  ok 7
  ok 8
  ok 9
  ok 10
  ok 11
  ok 12
  ok 13
  ok 14
  not ok 15
  ok 16
  ok 17
  ok 18
  ok 19
  ok 20
  ok 21
  ok 22
  ok 23
  ok 24
  ok 25
  ok 26
  ok 27
  ok 28
  ok 29
  ok 30
  ok 31
  ok 32
  ok 33
  ok 34
  ok 35
  ok 36
  ok 37
  ok 38
  ok 39
  ok 40
  ok 41
  ok 42
  ok 43
  ok 44
  ok 45
  ok 46
  Failed 1/46 subtests 
 
-- 
Niko Tyni   nt...@debian.org



Bug#1014292: cyrus-imapd: FTBFS with Perl 5.36: expected expression before ‘{’ token

2022-07-03 Thread Niko Tyni
Source: cyrus-imapd
Version: 3.6.0~beta2-3
Tags: ftbfs
User: debian-p...@lists.debian.org
Usertags: perl-5.36-transition

This package fails to build from source with Perl 5.36 (currently in
experimental.)

Build log at

  
http://perl.debian.net/rebuild-logs/perl-5.36/cyrus-imapd_3.6.0~beta2-3/cyrus-imapd_3.6.0~beta2-3+b2_amd64-2022-06-09T23:06:23Z.build

Excerpt:

  x86_64-linux-gnu-gcc -c  -I../../../lib -I../../../perl/sieve 
-I../../../perl/sieve/lib   -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv 
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -O2 -g   -DVERSION=\"0.01\" -DXS_VERSION=\"0.01\" -fPIC 
"-I/usr/lib/x86_64-linux-gnu/perl/5.36/CORE"  -DPERL_POLLUTE managesieve.c
  In file included from /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/perl.h:3855,
   from managesieve.xs:46:
  /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/sv_inline.h: In function 
‘Perl_newSV_type’:
  ../../../lib/assert.h:47:25: error: expected expression before ‘{’ token
 47 | #define assert(ex)  {if (!(ex))assertionfailed(__FILE__, 
__LINE__, #ex);}
| ^
  /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/handy.h:2787:28: note: in expansion 
of macro ‘assert’
   2787 | #define perl_assert_ptr(p) assert( ((void*)(p)) != 0 )
|^~
  /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/handy.h:2792:47: note: in expansion 
of macro ‘perl_assert_ptr’
   2792 | #define Zero(d,n,t) (MEM_WRAP_CHECK_(n,t) perl_assert_ptr(d), 
(void)memzero((char*)(d), (n) * sizeof(t)))
|   ^~~
  /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/sv_inline.h:468:13: note: in 
expansion of macro ‘Zero’
468 | Zero(new_body, type_details->body_size, char);
| ^~~~
  make[4]: *** [Makefile:346: managesieve.o] Error 1

-- 
Niko Tyni   nt...@debian.org



Bug#1014290: libgrokj2k: FTBFS with Perl 5.36: macro "utf8_to_utf16" requires 4 arguments, but only 1 given

2022-07-03 Thread Niko Tyni
Source: libgrokj2k
Version: 9.7.5-1
Tags: ftbfs
User: debian-p...@lists.debian.org
Usertags: perl-5.36-transition

This package fails to build from source with Perl 5.36 (currently in 
experimental).

Build log at

  
http://perl.debian.net/rebuild-logs/perl-5.36/libgrokj2k_9.7.5-1/libgrokj2k_9.7.5-1+b1_amd64-2022-06-10T01:11:12Z.build

Excerpt:

  [ 68%] Building CXX object 
src/bin/jp2/CMakeFiles/grk_decompress.dir/__/common/exif.cpp.o
  cd /<>/obj-x86_64-linux-gnu/src/bin/jp2 && /usr/bin/c++ 
-DSPDLOG_COMPILED_LIB -I/<>/obj-x86_64-linux-gnu/src/lib/jp2 
-I/<>/obj-x86_64-linux-gnu/src/bin/common 
-I/<>/src/lib/jp2 -I/<>/src/bin/common 
-I/<>/src/bin/image_format -I/<>/src/bin/jp2 
-I/<>/src/include -I/usr/lib/x86_64-linux-gnu/perl/5.36/CORE -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -Wdate-time -D_FORTIFY_SOURCE=2 
-Wall -Wextra -Wconversion -Wsign-conversion -Wunused-parameter -std=gnu++20 
-MD -MT src/bin/jp2/CMakeFiles/grk_decompress.dir/__/common/exif.cpp.o -MF 
CMakeFiles/grk_decompress.dir/__/common/exif.cpp.o.d -o 
CMakeFiles/grk_decompress.dir/__/common/exif.cpp.o -c 
/<>/src/bin/common/exif.cpp
  In file included from /<>/src/include/spdlog/fmt/fmt.h:25,
   from /<>/src/include/spdlog/common.h:45,
   from /<>/src/include/spdlog/spdlog.h:12,
   from /<>/src/bin/common/exif.cpp:38:
  /<>/src/include/spdlog/fmt/bundled/format.h:1193:47: error: 
macro "utf8_to_utf16" requires 4 arguments, but only 1 given
   1193 |   FMT_API explicit utf8_to_utf16(string_view s);
|   ^
  In file included from /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/regexp.h:21,
   from /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/perl.h:4156,
   from /<>/src/bin/common/exif.cpp:31:
  /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/utf8.h:89: note: macro 
"utf8_to_utf16" defined here
 89 | #define utf8_to_utf16(p, d, bytelen, newlen)  
  \
| 
  In file included from /<>/src/include/spdlog/fmt/fmt.h:25,
   from /<>/src/include/spdlog/common.h:45,
   from /<>/src/include/spdlog/spdlog.h:12,
   from /<>/src/bin/common/exif.cpp:38:
  /<>/src/include/spdlog/fmt/bundled/format.h:1193:20: error: 
declaration does not declare anything [-fpermissive]
   1193 |   FMT_API explicit utf8_to_utf16(string_view s);
|^
  make[3]: *** [src/bin/jp2/CMakeFiles/grk_decompress.dir/build.make:247: 
src/bin/jp2/CMakeFiles/grk_decompress.dir/__/common/exif.cpp.o] Error 1

-- 
Niko Tyni   nt...@debian.org



Bug#1014289: vile: FTBFS with Perl 5.36: ‘regexp_aligned’ undeclared here

2022-07-03 Thread Niko Tyni
Source: vile
Version: 9.8v-2
Severity: normal
Tags: ftbfs
User: debian-p...@lists.debian.org
Usertags: perl-5.36-transition

This package fails to build from source with Perl 5.36 (currently in 
experimental).

Build log at

   
http://perl.debian.net/rebuild-logs/perl-5.36/vile_9.8v-2/vile_9.8v-2+b1_amd64-2022-06-10T06:32:17Z.build

Excerpt:

   gcc -c -I. -I../.. -DHAVE_CONFIG_H -I../../filters -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=500 -D_REENTRANT 
-D_GNU_SOURCE -DDEBIAN -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -I/usr/lib/x86_64-linux-gnu/perl/5.36/CORE 
-DPROGRAM_NAME=\"vile\" -DVILE_ICON=\"icons/\" 
-DVILE_LIBDIR_PATH=\"/usr/lib/x86_64-linux-gnu/vile\" 
-DVILE_STARTUP_PATH=\"/usr/share/vile\" -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -fwrapv 
-fno-strict-aliasing -pipe -rdynamic -Werror=format-security  
-DHELP_LOC=\"/usr/share/vile\" perl.c
   ../../perl.xs:24:32: warning: unknown option after ‘#pragma GCC diagnostic’ 
kind [-Wpragmas]
  24 | #pragma GCC diagnostic ignored "-Wcompound-token-split-by-macro"
 |^
   In file included from /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/perl.h:7243,
from ../../perl.xs:132:
   /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/sv_inline.h:241:32: error: 
‘regexp_aligned’ undeclared here (not in a function); did you mean 
‘regexp_engine’?
 241 | { sizeof(ALIGNED_TYPE_NAME(regexp)),
 |^~
   /usr/lib/x86_64-linux-gnu/perl/5.36/CORE/sv_inline.h:135:33: note: in 
definition of macro ‘ALIGNED_TYPE_NAME’
 135 | #define ALIGNED_TYPE_NAME(name) name##_aligned
 | ^~~~
   make[1]: *** [makefile:135: perl.o] Error 1
   make[1]: Leaving directory '/<>/t/vile'
   make: *** [debian/rules:36: build-stamp] Error 2
 
-- 
Niko Tyni   nt...@debian.org



Bug#1014288: RM: apertium-spa -- ROM; No longer used

2022-07-03 Thread Kartik Mistry
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: kar...@debian.org
Usertags: rm

Dear FTP Team,

Please remove the apertium-spa from unstable. This package is
now no longer useful and dependency of apertium language pairs.

Thanks!

-- 
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com



Bug#1014286: perl/experimental: FTBFS on mips64el: test failures

2022-07-03 Thread Niko Tyni
Source: perl
Version: 5.36.0-1
Severity: serious
Tags: ftbfs
User: debian-p...@lists.debian.org
Usertags: perl-5.36-transition
X-Debbugs-Cc: debian-m...@lists.debian.org

The perl package in experimental fails to build from source
on mips64el.

  https://buildd.debian.org/status/package.php?p=perl&suite=experimental

It looks like the perl binary dies with SIGSEGV in thread related tests
during the test suite. This happened twice on different buildds.

I'm running a test build now on eller.d.o to see if it's reproducible.

Copying the debian-mips list. Help from porters would be welcome.
-- 
Niko Tyni   nt...@debian.org



Bug#1014285: nvtop: new version available with AMD GPU support

2022-07-03 Thread Giuseppe Bilotta
Package: nvtop
Version: 1.2.2-1
Severity: normal

Upstream has updated to version 2.0.2 that introduces support for AMD GPUs. 
Would it be possibel to update the package?


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

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

Versions of packages nvtop depends on:
ii  libc6 2.33-7
ii  libncursesw6  6.3+20220423-2
ii  libtinfo6 6.3+20220423-2

nvtop recommends no packages.

nvtop suggests no packages.

-- no debconf information



Bug#1014284: [kernel 5.18.5-1] [arm64 on Rock64 SBC]

2022-07-03 Thread Jean-Marc LACROIX

Package: linux-image-5.18.0-2-arm64
Version:  5.18.5-1
Severity: normal

Dear kernel team,

Please find in  attached file success story  (!)   on recent boot  for
target rock64 (pine64)  with 64 Go class10  MMC card with Debian  11.3
Bullseye and Bookworm 5.18.5-1 kernel with following configuration ...

ansible@hn-rock64-130:~$ uname -a
Linux hn-rock64-130 5.18.0-2-arm64 #1 SMP Debian 5.18.5-1 (2022-06-16) 
aarch64 GNU/Linux


ansible@hn-rock64-130:~$ dpkg -l |grep linux-image
ii  linux-image-5.10.0-3-arm64 5.10.13-1  arm64 
   Linux 5.10 for 64-bit ARMv8 machines (signed)
ii  linux-image-5.18.0-2-arm64 5.18.5-1   arm64 
   Linux 5.18 for 64-bit ARMv8 machines (signed)


ansible@hn-rock64-130:~$ cat 
/etc/apt/sources.list.d/debian_apt_v_11_bullseye_* |grep -v "#" |grep -v ^$

deb http://ftp.de.debian.org/debian/ bullseye main contrib non-free
deb http://ftp.de.debian.org/debian/ bookworm main contrib non-free
deb http://ftp.de.debian.org/debian/ oldstable main contrib non-free
deb http://security.debian.org/debian-security bullseye-security main 
contrib non-free

deb http://ftp.de.debian.org/debian bullseye-updates main contrib non-free


ansible@hn-rock64-130:~$ cat 
/etc/apt/preferences.d/preferences_debian_v_11_bullseye* |grep -v "#" 
|grep -v ^$

Package: vmdb2
Pin: release o=Debian,l=Debian,n=bullseye
Pin-Priority: 920
Package: *
Pin: release o=Debian,l=Debian,n=bullseye/updates
Pin-Priority: 500
Package: *
Pin: release o=Debian,l=Debian,n=bullseye-update
Pin-Priority: 500
Package: *
Pin: release o=Debian,l=Debian,n=bullseye
Pin-Priority: 500
Package: *
Pin: release o=Debian,l=Debian,n=bullseye-backports
Pin-Priority: 100
Package: *
Pin: release o=Debian,l=Debian,n=buster
Pin-Priority: 90
Package: *
Pin: release o=Debian,l=Debian,n=bookworm
Pin-Priority: 80
Package: *
Pin: release o=Debian,l=Debian,n=sid
Pin-Priority: 70
Package: *
Pin: release o=Debian,l=Debian,n=experimental
Pin-Priority: 60
Package: avahi-daemon
Pin: release *
Pin-Priority: -1
Package: dbus
Pin: release a=bullseye
Pin-Priority: -1

Package: dhcpcd5
Pin: release *
Pin-Priority: -1
Package: rtkit
Pin: release *
Pin-Priority: -1
Package: systemd
Pin: release *
Pin-Priority: -1


ansible@hn-rock64-130:~$ lsmod
Module   Size  Used by
nf_tables   212992  0
libcrc32c16384  1 nf_tables
nfnetlink20480  1 nf_tables
veth32768  0
bridge 258048  0
autofs4 49152  3
8021q   32768  0
garp24576  1 8021q
mrp 24576  1 8021q
stp 20480  2 bridge,garp
llc 20480  3 bridge,stp,garp
evdev   32768  0
snd_soc_hdmi_codec 24576  1
hantro_vpu  139264  0
v4l2_vp9 24576  1 hantro_vpu
v4l2_h26416384  1 hantro_vpu
dw_hdmi_i2s_audio 16384  0
dw_hdmi_cec  16384  0
v4l2_mem2mem 32768  1 hantro_vpu
aes_ce_blk   36864  0
snd_soc_rockchip_spdif16384  2
videobuf2_dma_contig24576  1 hantro_vpu
aes_ce_cipher 20480  1 aes_ce_blk
snd_soc_rockchip_i2s28672  2
snd_soc_simple_card24576  0
mcs7830 20480  0
pl2303  28672  0
snd_soc_spdif_tx  16384  1
snd_soc_rk332816384  0
videobuf2_memops  20480  1 videobuf2_dma_contig
snd_soc_simple_card_utils24576  1 snd_soc_simple_card
ghash_ce 24576  0
usbnet  45056  1 mcs7830
videobuf2_v4l224576  2 hantro_vpu,v4l2_mem2mem
gf128mul 16384  1 ghash_ce
snd_soc_core 208896  7 
snd_soc_spdif_tx,snd_soc_hdmi_codec,snd_soc_rockchip_spdif,snd_soc_rk3328,snd_soc_simple_card_utils,snd_soc_rockchip_i2s,snd_soc_simple_card 


usbserial49152  1 pl2303
mii 20480  2 mcs7830,usbnet
snd_pcm_dmaengine 20480  1 snd_soc_core
videobuf2_common  53248  5 
videobuf2_dma_contig,videobuf2_v4l2,hantro_vpu,v4l2_mem2mem,videobuf2_memops 

sha2_ce 20480  0snd_pcm 118784  4 
snd_soc_hdmi_codec,snd_soc_simple_card_utils,snd_soc_core,snd_pcm_dmaengine 


sha256_arm64 28672  1 sha2_ce
videodev225280  4 
videobuf2_v4l2,hantro_vpu,videobuf2_common,v4l2_mem2mem

ofpart  20480  0
lima65536  0
sha1_ce 20480  0
snd_timer40960  1 snd_pcm
snd 94208  4 snd_soc_hdmi_codec,snd_timer,snd_soc_core,snd_pcm
mc 53248  5 
videodev,videobuf2_v4l2,hantro_vpu,videobuf2_common,v4l2_mem2mem

spi_nor 90112  0
leds_gpio16384  0
gpu_sched40960  1 lima
soundcore20480  1 snd
nvmem_rockchip_efuse16384  0
drm_shmem_helper  24576  1 lima
io_domain24576  0
rockchip_thermal  28672  0
mtd 69632  3 spi_nor,ofpart
dw_wdt  20480  0
cpufreq_dt   20480  0
ext4   761856  37
crc16   16384  1 ext4
mbcache 24576  1 ext4
jbd2   143360  1 ext4
crc32c_generic16384  75
dm_mod 143360  108
dax 36864  1 dm_mod
realtek 32768  1
xhci_plat_hcd 20480  0
xhci_hcd253952  1 xhci_plat_hcd
dwmac_rk 28672  0
rockchipdrm 122880  0
stmmac_platform   24576  1 dwmac_rk
rk808_regulator   40960  14
stmmac 237568  2 stmmac_platform,dwmac_rk
drm_cma_helper20480  1 rockchipdrm
dw_hdmi 45056  2 dw_hdmi_i2s_audio,rockchipdrm
pcs_xpcs 24576  1 stmmac
phylink 45056  1 stmmac
cec 49152  2 dw_hdmi_cec,dw_hdmi
of_mdio 

Bug#1013299: Fwd: Patch "net/sched: move NULL ptr check to qdisc_put() too" has been added to the 4.19-stable tree

2022-07-03 Thread Diederik de Haas
Control: tag -1 fixed-upstream

On Thursday, 30 June 2022 16:31:54 CEST Diederik de Haas wrote:
> Patch has been added to the 4.19 queue:

And it's now part of the v4.19.250 release :-)

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


Bug#1010799: NMU: tpm-tools 1.3.9.2-0.1

2022-07-03 Thread Timo Lindfors

Hello Pierre,

I've prepared a package for the new tpm-tools upstream version 1.3.9.2.

Please see the attached diff (only the debian directory given) or if you 
prefer, visit https://salsa.debian.org/debian/tpm-tools


The package is currently in DELAYED/10 to give you time to react.

-Timo
diff -Naur tpm-tools-1.3.9.1/debian/changelog tpm-tools/debian/changelog
--- tpm-tools-1.3.9.1/debian/changelog	2017-05-22 01:20:40.0 +0300
+++ tpm-tools/debian/changelog	2022-07-03 14:46:00.952191745 +0300
@@ -1,3 +1,14 @@
+tpm-tools (1.3.9.2-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream release (Closes: #1010799).
+- Drop patches/05-openssl1.1_fix_data_mgmt.patch
+  * Bump Standards-Version to 4.6.1.
+  * Add compiler hardening flags.
+  * Add autokpkgtest for nvram handling.
+
+ -- Timo Lindfors   Fri, 01 Jul 2022 23:34:48 +0300
+
 tpm-tools (1.3.9.1-0.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Naur tpm-tools-1.3.9.1/debian/control tpm-tools/debian/control
--- tpm-tools-1.3.9.1/debian/control	2017-05-14 03:21:06.0 +0300
+++ tpm-tools/debian/control	2022-07-03 14:43:59.576089266 +0300
@@ -3,11 +3,14 @@
 Priority: optional
 Maintainer: Pierre Chifflier 
 Build-Depends:
- debhelper (>= 10), autotools-dev, automake, libopencryptoki-dev,
+ debhelper (>= 10), automake, libopencryptoki-dev,
  libtspi-dev (>= 0.3.10),
- quilt, dh-autoreconf, autopoint
-Standards-Version: 3.9.8
+ quilt, autopoint
+Standards-Version: 4.6.1
 Homepage: http://trousers.sourceforge.net/
+Rules-Requires-Root: no
+Vcs-Browser: https://salsa.debian.org/debian/tpm-tools
+Vcs-Git: https://salsa.debian.org/debian/tpm-tools.git
 
 Package: tpm-tools
 Architecture: any
diff -Naur tpm-tools-1.3.9.1/debian/copyright tpm-tools/debian/copyright
--- tpm-tools-1.3.9.1/debian/copyright	2015-03-25 19:03:39.0 +0200
+++ tpm-tools/debian/copyright	2022-07-03 14:43:59.576089266 +0300
@@ -1,5 +1,7 @@
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: tpm-tools
 Author: Kent Yoder 
-Download: http://trousers.sourceforge.net/
+Source: https://trousers.sourceforge.net/
 
 Files: *
 Copyright: 2005-2007 IBM, Corp. 
diff -Naur tpm-tools-1.3.9.1/debian/files tpm-tools/debian/files
--- tpm-tools-1.3.9.1/debian/files	1970-01-01 02:00:00.0 +0200
+++ tpm-tools/debian/files	2022-07-03 14:53:46.676706778 +0300
@@ -0,0 +1 @@
+tpm-tools_1.3.9.2-0.1_source.buildinfo admin optional
diff -Naur tpm-tools-1.3.9.1/debian/patches/05-openssl1.1_fix_data_mgmt.patch tpm-tools/debian/patches/05-openssl1.1_fix_data_mgmt.patch
--- tpm-tools-1.3.9.1/debian/patches/05-openssl1.1_fix_data_mgmt.patch	2017-02-05 23:05:18.0 +0200
+++ tpm-tools/debian/patches/05-openssl1.1_fix_data_mgmt.patch	1970-01-01 02:00:00.0 +0200
@@ -1,106 +0,0 @@
-Author: Philipp Kern 
-Subject: Fix openssl1.1 support in data_mgmt
-Date: Tue, 31 Jan 2017 22:40:10 +0100
-
-

- src/data_mgmt/data_import.c |   60 
- 1 file changed, 39 insertions(+), 21 deletions(-)
-
 a/src/data_mgmt/data_import.c
-+++ b/src/data_mgmt/data_import.c
-@@ -372,7 +372,7 @@ readX509Cert( const char  *a_pszFile,
- 		goto out;
- 	}
- 
--	if ( EVP_PKEY_type( pKey->type ) != EVP_PKEY_RSA ) {
-+	if ( EVP_PKEY_base_id( pKey ) != EVP_PKEY_RSA ) {
- 		logError( TOKEN_RSA_KEY_ERROR );
- 
- 		X509_free( pX509 );
-@@ -691,8 +691,13 @@ createRsaPubKeyObject( RSA
- 
- 	int  rc = -1;
- 
--	int  nLen = BN_num_bytes( a_pRsa->n );
--	int  eLen = BN_num_bytes( a_pRsa->e );
-+	const BIGNUM *bn;
-+	const BIGNUM *be;
-+
-+	RSA_get0_key( a_pRsa, &bn, &be, NULL );
-+
-+	int  nLen = BN_num_bytes( bn );
-+	int  eLen = BN_num_bytes( be );
- 
- 	CK_RV  rv;
- 
-@@ -732,8 +737,8 @@ createRsaPubKeyObject( RSA
- 	}
- 
- 	// Get binary representations of the RSA key information
--	BN_bn2bin( a_pRsa->n, n );
--	BN_bn2bin( a_pRsa->e, e );
-+	BN_bn2bin( bn, n );
-+	BN_bn2bin( be, e );
- 
- 	// Create the RSA public key object
- 	rv = createObject( a_hSession, tAttr, ulAttrCount, a_hObject );
-@@ -760,14 +765,27 @@ createRsaPrivKeyObject( RSA
- 
- 	int  rc = -1;
- 
--	int  nLen = BN_num_bytes( a_pRsa->n );
--	int  eLen = BN_num_bytes( a_pRsa->e );
--	int  dLen = BN_num_bytes( a_pRsa->d );
--	int  pLen = BN_num_bytes( a_pRsa->p );
--	int  qLen = BN_num_bytes( a_pRsa->q );
--	int  dmp1Len = BN_num_bytes( a_pRsa->dmp1 );
--	int  dmq1Len = BN_num_bytes( a_pRsa->dmq1 );
--	int  iqmpLen = BN_num_bytes( a_pRsa->iqmp );
-+	const BIGNUM *bn;
-+	const BIGNUM *be;
-+	const BIGNUM *bd;
-+	const BIGNUM *bp;
-+	const BIGNUM *bq;
-+	const BIGNUM *bdmp1;
-+	const BIGNUM *bdmq1;
-+	const BIGNUM *biqmp;
-+
-+	RSA_get0_key( a_pRsa, &bn, &be, &bd);
-+	RSA_get0_factors( a_pRsa, &bp, &bq);
-+	RSA_get0_crt_params( a_pRsa, &bdmp1, &bdmq1, &biqmp );
-+
-+	int  nLen = BN_num_bytes( bn );
-+	int  eLen = BN_num_bytes( be );
-+	int  dLen = BN_num_bytes( bd );
-+	int  pLen = BN_num_bytes( bp );
-+	i

Bug#1014282: perl: autopkgtest failure: needs Provides/Replaces/Breaks for libtext-balanced-perl

2022-07-03 Thread Niko Tyni
Source: perl
Version: 5.34.0-4
Severity: serious
Control: block -1 by 1014280

The perl package recently started failing its autopkgtest checks
in testing.

  #   Failed test 'no potential packages for new Provides/Replaces/Breaks found 
in the archive'
  #   at debian/t/control.t line 303.
  #  got: 'libtext-balanced-perl'
  # expected: ''
  # Looks like you failed 1 test of 590.
  debian/t/control.t .. 
 
This is because libtext-balanced-perl got introduced in the archive
and we need to add corresponding metadata for it in the perl package.

A complication is that pdl has added an unversioned dependency on
libtext-balanced-perl while it really needs a newer one.  So making the
perl core packages Provide libtext-balanced-perl will break pdl.

I've filed a separate bug about this, and would prefer to have
pdl changed first.
-- 
Niko Tyni   nt...@debian.org



Bug#1014281: ffdiaporama: Crashes on start with "malloc(): corrupted top size"

2022-07-03 Thread Shawn K. Quinn
Package: ffdiaporama
Version: 2.1+dfsg-1+b3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: skqu...@rushpost.com

Dear Maintainer,

   * What led up to the situation?

Trying to run ffdiaporama for the first time.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Run the executable "ffDiaporama" from a terminal.

   * What was the outcome of this action?

The program appears to start normally, but I get this output:

$ ffDiaporama
[07:09:12.213:INFO] QT Version:5.15.2
[07:09:12.213:INFO] StartupDir /home/skquinn
[07:09:12.213:INFO] Application not found in directory
/home/skquinn/BUILDVERSION.txt
[07:09:12.213:INFO] Application not found in directory
/../../ffDiaporama/BUILDVERSION.txt
[07:09:12.213:INFO] Application not found in directory
/../ffDiaporama/BUILDVERSION.txt
[07:09:12.213:INFO] Application not found in directory
/opt/share/ffDiaporama/BUILDVERSION.txt
[07:09:12.213:INFO] Application found in directory
/usr/share/ffDiaporama/BUILDVERSION.txt
[07:09:12.213:INFO] Set working path to /usr/share/ffDiaporama
[07:09:12.213:INFO] Start ffDiaporama 2.1 (20140209) ...
[07:09:12.286:INFO] Parse command line ...
[07:09:12.286:INFO] Set LogLevel to INFORMATION
[07:09:12.286:INFO] Start GUI ...
[07:09:12.287:INFO] Start ...
libpng warning: iCCP: known incorrect sRGB profile
[07:09:12.309:INFO] Init home user database...
[07:09:12.311:INFO] Init translations...
[07:09:12.312:INFO] Read configuration file
/usr/share/ffDiaporama/ffDiaporama.xml
[07:09:12.315:INFO] Read configuration file
/usr/share/ffDiaporama/Devices.xml
[07:09:12.321:INFO] Read configuration file
/home/skquinn/.ffDiaporama/ffDiaporama.xml
[07:09:12.321:INFO] Read configuration file
/home/skquinn/.ffDiaporama/Devices.xml
[07:09:12.322:ERROR]Restore from a previous crash...
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[07:09:13.075:INFO] Loading system icons...
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[07:09:13.104:INFO] Starting libav...
[07:09:13.105:INFO] Loading background library...
[07:09:13.114:INFO] Loading text frame library...
[07:09:13.139:INFO] Loading no-luma transitions...
[07:09:13.142:INFO] Loading luma transitions...
[07:09:13.310:INFO] Scan drives in computer...
[07:09:13.310:INFO] Register models...
[07:09:13.646:INFO] Reading directory content (~/)
[07:09:13.796:WARNING]  LIBAV: Warning: data is not aligned! This can lead to a
speed loss
[07:09:13.801:INFO] LIBAV: Statistics: 32768 bytes read, 0 seeks
[07:09:13.807:INFO] LIBAV: Reinit context to 960x528, pix_fmt: yuv420p
[07:09:13.814:INFO] LIBAV: Reinit context to 960x528, pix_fmt: yuv420p
[07:09:13.823:INFO] LIBAV: Statistics: 137773 bytes read, 2 seeks
[07:09:13.841:INFO] LIBAV: Reinit context to 1152x720, pix_fmt: yuv420p
[07:09:13.846:INFO] LIBAV: Reinit context to 1152x720, pix_fmt: yuv420p
[07:09:13.857:INFO] LIBAV: Statistics: 163840 bytes read, 0 seeks
[07:09:13.869:INFO] LIBAV: Statistics: 32768 bytes read, 0 seeks
[07:09:13.879:INFO] LIBAV: Reinit context to 1920x1088, pix_fmt: yuv420p
[07:09:13.888:INFO] LIBAV: Reinit context to 1920x1088, pix_fmt: yuv420p
[07:09:13.910:INFO] LIBAV: Statistics: 130938 bytes read, 2 seeks
[07:09:13.926:INFO] LIBAV: Statistics: 65536 bytes read, 0 seeks
malloc(): corrupted top size
Aborted


   * What outcome did you expect instead?

I expected to get at least as far as the main program screen.

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

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

Versions of packages ffdiaporama depends on:
ii  ffdiaporama-data 2.1+dfsg-1
ii  libavcodec58 7:4.3.4-0+deb11u1
ii  libavfilter7 7:4.3.4-0+deb11u1
ii  libavformat587:4.3.4-0+deb11u1
ii  libavutil56  7:4.3.4-0+deb11u1
ii  libc62.31-13+deb11u3
ii  libexiv2-2

Bug#1014280: pdl: please make the libtext-balanced-perl dependency versioned

2022-07-03 Thread Niko Tyni
Package: pdl
Version: 1:2.080-2

The recent addition of libtext-balanced-perl in the archive has broken
the src:perl autopkgtest checks, because perl doesn't currently have
the Breaks/Replaces/Provides entries for libtext-balanced-perl and the
autopkgtest checks notice that.

These entries are long established practice for dual life modules, primarily
making sure that outdated versions of separate packages can not override
newer versions in the core packages. This is not a concern currently,
given Text::Balanced 2.06 is not in core yet, but it would be good to
add the metadata in advance for consistency.

However, pdl currently has an unversioned dependency on
libtext-balanced-perl, so if I make perl Provide libtext-balanced-perl
(= 2.04), that will satisfy the pdl dependency even though pdl actually
needs the newer version (I understand this was the main reason for
introducing the separate package in the first place.)

So, please make the pdl dependency (both build and run time if applicable)
versioned so I can add the metadata on the perl side after that.

This has some urgency as perl is currently failing its autopkgtest
checks in testing. I'll file a separate bug about that and mark it as
blocked by this one. The autopkgtest issue could also be worked around
by whitelisting libtext-balanced-perl temporarily, but I'd prefer a long
term fix if possible.

Thanks for your work,
-- 
Niko Tyni   nt...@debian.org



Bug#1014278: statsmodels: s390x fails TestDynamicFactor test_mle with scipy 1.8 and pythran

2022-07-03 Thread Drew Parsons
Source: statsmodels
Version: 0.13.2+dfsg-2
Severity: normal

scipy 1.8.1 has been recently uploaded to unstable.

statsmodel is giving a test error on s390x:

 TestDynamicFactor_ar2_errors.test_mle _

self = 


def test_mle(self):
with warnings.catch_warnings(record=True):
# Depending on the system, this test can reach a greater precision,
# but for cross-platform results keep it at 1e-2
mod = self.model
res1 = mod.fit(maxiter=100, optim_score='approx', disp=False)
res = mod.fit(
res1.params, method='nm', maxiter=1,
optim_score='approx', disp=False)
# Added rtol to catch spurious failures on some platforms
>   assert_allclose(res.llf, self.results.llf, atol=1e-2, rtol=1e-4)
E   AssertionError: 
E   Not equal to tolerance rtol=0.0001, atol=0.01
E   
E   Mismatched elements: 1 / 1 (100%)
E   Max absolute difference: 1.11132149
E   Max relative difference: 0.00182958
Ex: array(606.308783)
Ey: array(607.420104)

/usr/lib/python3/dist-packages/statsmodels/tsa/statespace/tests/test_dynamic_factor.py:614:
 AssertionError


It's just a question of tolerance, thought the tolerance required to
pass is a little higher than we'd prefer (would need absolute difference 1.2
instead of 0.01)

At the same time scipy has been configured to use pythran, introduced
in scipy 1.8.1-5.  Because the s390x test machines have been flakey in
recent week, we missed the test of statsmodels against scipy 1.8.1
without pythran, so it's not clear if the test failure is due to scipy
1.8 itself, or due to scipy 1.8 using pythran 0.11.

In any case it's only one test among 16358, so one option is to just
skip this test on s390x, e.g.

import platform
@pytest.mark.skipif(platform.machine()=='s390x', reason="tolerance not 
reached on s390x")
def test_mle(self):



Bug#695835: Projekt

2022-07-03 Thread Dave E. Ramsden
Mam projekt do omówienia z tobą. Jeśli jesteś zainteresowany, odpowiedz po 
więcej szczegółów, jeśli to możliwe, w języku angielskim.
   
Z poważaniem,
Dave Ramsden
_
Sekretarz: Vanni Gilbert



Bug#1014277: dhcpcd5: dhcpcd fails to chroot and set PID file on startup, systemd eventually kills it after timeout

2022-07-03 Thread Tobias Klausmann
Package: dhcpcd5
Version: 9.4.1-3
Severity: important

Dear Maintainer,


   * What led up to the situation?

Recent system update, probably. 

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Restart dhcpcd, reboot the machine.

   * What was the outcome of this action?

systemd kills dhcpcd after 90s, despite it working correctly (mostly).

   * What outcome did you expect instead?

A working, running dhcpcd

Log:

Jul 03 12:20:07 felka systemd[1]: Starting DHCP Client Daemon on all 
interfaces...
░░ Subject: A start job for unit dhcpcd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit dhcpcd.service has begun execution.
░░
░░ The job identifier is 165.
Jul 03 12:20:07 felka dhcpcd[624]: dhcpcd-9.4.1 starting
Jul 03 12:20:07 felka dhcpcd[643]: ps_dropprivs: chroot: /usr/lib/dhcpcd: 
Operation not permitted
Jul 03 12:20:07 felka dhcpcd[643]: ps_dropprivs: chroot: /usr/lib/dhcpcd: 
Operation not permitted
Jul 03 12:20:07 felka dhcpcd[624]: ps_dropprivs: chroot: /usr/lib/dhcpcd: 
Operation not permitted
Jul 03 12:20:07 felka dhcpcd[624]: ps_dropprivs: chroot: /usr/lib/dhcpcd: 
Operation not permitted
Jul 03 12:20:07 felka dhcpcd[643]: DUID 
00:04:03:
Jul 03 12:20:07 felka systemd[1]: dhcpcd.service: Can't open PID file 
/run/dhcpcd.pid (yet?) after start: Operation not permi>
Jul 03 12:20:08 felka dhcpcd[643]: wan1: waiting for carrier
Jul 03 12:20:11 felka dhcpcd[643]: wan1: carrier acquired
Jul 03 12:20:11 felka dhcpcd[643]: wan1: IAID 99:ab:X
Jul 03 12:20:11 felka dhcpcd[643]: wan1: IA type 25 IAID 00:00:00:00
Jul 03 12:20:11 felka dhcpcd[643]: wan1: adding address 
fe80::b62e:f2
Jul 03 12:20:11 felka dhcpcd[643]: wan1: soliciting an IPv6 router
Jul 03 12:20:11 felka dhcpcd[643]: wan1: rebinding lease of 185.XX
Jul 03 12:20:11 felka dhcpcd[2012]: ps_dropprivs: chroot: /usr/lib/dhcpcd: 
Operation not permitted
Jul 03 12:20:11 felka dhcpcd[2013]: ps_dropprivs: chroot: /usr/lib/dhcpcd: 
Operation not permitted
Jul 03 12:20:11 felka dhcpcd[643]: wan1: probing address 185.1X/24
Jul 03 12:20:12 felka dhcpcd[643]: wan1: rebinding prior DHCPv6 lease
Jul 03 12:20:12 felka dhcpcd[643]: lan1: activating for delegation
Jul 03 12:20:12 felka dhcpcd[643]: lan1: IAID 99:ab:X
Jul 03 12:20:12 felka dhcpcd[643]: wlan1: activating for delegation
Jul 03 12:20:12 felka dhcpcd[643]: wlan1: waiting for carrier
Jul 03 12:20:13 felka dhcpcd[643]: wlan1: carrier acquired
Jul 03 12:20:13 felka dhcpcd[643]: wlan1: IAID 85:f5:X
Jul 03 12:20:13 felka dhcpcd[643]: wlan1: adding address 
fe80::52e0:XX
Jul 03 12:20:16 felka dhcpcd[643]: wan1: leased 185.XX for 4000 seconds
Jul 03 12:20:16 felka dhcpcd[643]: wan1: adding route to 185.X/24
Jul 03 12:20:16 felka dhcpcd[643]: wan1: adding default route via 185.X
Jul 03 12:20:18 felka dhcpcd[643]: wan1: Router Advertisement from 
fe80::200:X
Jul 03 12:20:18 felka dhcpcd[643]: wan1: adding address 
2a02:XXX/64
Jul 03 12:20:18 felka dhcpcd[643]: wan1: adding route to 2a02:X/64
Jul 03 12:20:18 felka dhcpcd[643]: wan1: adding default route via 
fe80::200:X
Jul 03 12:20:21 felka dhcpcd[643]: wan1: fe80::200:X is unreachable
Jul 03 12:20:21 felka dhcpcd[643]: wan1: fe80::200:X is reachable 
again
Jul 03 12:20:22 felka dhcpcd[643]: wan1: failed to rebind prior DHCPv6 
delegation
Jul 03 12:20:22 felka dhcpcd[643]: wan1: soliciting an IPv6 router
Jul 03 12:20:25 felka dhcpcd[643]: wan1: ADV 2a02:::/48 from 
fe80::200:X
Jul 03 12:20:25 felka dhcpcd[643]: wan1: REPLY6 received from 
fe80::200:X
Jul 03 12:20:25 felka dhcpcd[643]: wan1: renew in 1000, rebind in 2000, expire 
in 4000 seconds
Jul 03 12:20:25 felka dhcpcd[643]: lo: adding reject route to 2a02:XX/48
Jul 03 12:20:25 felka dhcpcd[643]: wan1: delegated prefix 2a02:XX/48
Jul 03 12:20:25 felka dhcpcd[643]: lan1: adding address 2a02:XXX/64
Jul 03 12:20:25 felka dhcpcd[643]: wlan1: adding address 2a02:X/64
Jul 03 12:20:25 felka dhcpcd[643]: lan1: adding route to 2a02:XX/64
Jul 03 12:20:25 felka dhcpcd[643]: wlan1: adding route to 2a02:/64
Jul 03 12:21:38 felka systemd[1]: dhcpcd.service: start operation timed out. 
Terminating.
Jul 03 12:21:38 felka dhcpcd[643]: received SIGTERM, stopping
Jul 03 12:21:38 felka dhcpcd[643]: wlan1: removing interface
Jul 03 12:21:38 felka dhcpcd[643]: lan1: removing interface
Jul 03 12:21:38 felka dhcpcd[643]: wan1: removing interface
Jul 03 12:21:38 felka systemd[1]: dhcpcd.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit dhcpcd.service has entered the 'failed' state with result 'timeout'.
Jul 03 12:21:38 felka systemd[1]: Faile

Bug#1014275: sakura: prints regex related warnings on startup

2022-07-03 Thread Andreas Rönnquist
tags -1 fixed-upstream
thanks

Thanks for your report - this has been fixed in the upstream git
repository [1] but hasn't been available in an upstream release yet -
If a new upstream release takes too long I will cherry-pick the fix and
make a new Debian release.

cheers
-- Andreas Rönnquist
gus...@debian.org

1: 
https://git.launchpad.net/sakura/commit/?id=24acf1a5a0c0a401c69c47dd61a8338c59be767e



Bug#1013644: erlang-p1-tls: FTBFS: test failed

2022-07-03 Thread Philipp Huebner
Hi Lucas,

unfortunately I am unable to reproduce this error.

How do you suggest to continue here?

Best wishes
-- 
 .''`.   Philipp Huebner 
: :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
`. `'`
  `-


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1014275: sakura: prints regex related warnings on startup

2022-07-03 Thread David Bremner
Package: sakura
Version: 3.8.5-1
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The following warnings are printed when I run sakura from a terminal:

(sakura:1554729): VTE-WARNING **: 04:31:01.477: (../src/vtegtk.cc:2841):int 
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32): runtime check 
failed: (_vte_regex_has_multiline_compile_flag(regex))

(sakura:1554729): VTE-WARNING **: 04:31:01.478: (../src/vtegtk.cc:2841):int 
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32): runtime check 
failed: (_vte_regex_has_multiline_compile_flag(regex))


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

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

Versions of packages sakura depends on:
ii  libc6   2.33-7
ii  libglib2.0-02.72.2-2
ii  libgtk-3-0  3.24.34-1
ii  libpango-1.0-0  1.50.7+ds-1
ii  libvte-2.91-0   0.68.0-1+b1

sakura recommends no packages.

sakura suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmLBblgACgkQA0U5G1Wq
FSGZkhAArmPhIS2h1u/CihMkO/2Xun8E9eG1zBeN5x15Jev3TuNE3NwjgT07VB/6
QTzJ8wW7Q2M1s5K26c1cV6I+8pAG2cb/teg265CtQo2vjfchV/dum6B/0EmAM8Dy
9E31baI7IA+alhSRqzg+igMBl7vwwHPMhptYE1hJBIZzGqQrax88ZofIFvSTlN/I
A4eLVxAsWGV1fuZRL9Uy4mKlGWbM1dIOI2VXmGa/inIZjxoocGEqEp4gESTZH8OJ
xdGr87lhNSECfAzzyULFuQ6nM2nIe+05wCGyGuT1DiJzUAkcQHTM9YE6YISU+iBj
MSOopysBSNzMIZ67XQnkh7/mTmpaEkG8zwl/e9LiscdtP4wdnfSQ+WDjWvfyyyGj
GhXtdidiRtTHljTOY4GKQ9TpHic2MgIOQD823a3jE/DCAPzKnS1EuRc24I9dSdiH
stCZVTej2knAWaRjh9pf+iAVRmH3myfc4ZPvamnxk1hySnkz+PWlUXqCFq0p9541
Gqv5Onkb3xMr3KR96FS4BXVLZbx4TQRIEFWIzu/O4iat+etLcEpw3eG62Bg8/gQm
jyafiSjeWYp7F2Q1I6h5FcumMQVfkwnqG1jgEY4g8FSbXhY8CLQEwgzsXXwPa9+8
xgCdgpILiRCHT9Ap3pCmQToekksKuhL1b1ngpo3UiQV90Lyzns0=
=Md2x
-END PGP SIGNATURE-



Bug#1010964: yosys: autopkgtest regression

2022-07-03 Thread Daniel Gröber
On Sun, Jul 03, 2022 at 08:49:38AM +0200, Petter Reinholdtsen wrote:
> I notice the new upload of 0.18 already happened, which is very nice to
> see.  But this bug was not closed in debian/changelog.  Does this mean
> bug #1010964 is not solved?
> 
> Also, remember to ask ftpmasters to remove any mips64el binaries from
> unstable when excluding it for the package, if you have not done so
> already.

Thanks for the reminder. The mips64el RM request is Bug#1014274 and seeing
that autopkgtest seems to succeed now I'm closing this bug.

--Daniel



Bug#1014274: RM: yosys [mips64el] -- RoM; ANAIS

2022-07-03 Thread Daniel Gröber
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: d...@darkboxed.org

Hi,

please remove the yosys binary package for misp64el from the archive
as it was excluded from the source package Architecture list in order
to unblock migrating to testing.

Thanks,
--Daniel



Bug#820625: [wrap-and-sort] removes all comments from debian/control

2022-07-03 Thread Andreas Metzler
On 2022-06-19 Niels Thykier  wrote:
> On Sun, 10 Apr 2016 21:02:05 +0200 Christoph Berg  wrote:
>> Package: devscripts
>> Version: 2.16.2
>> Severity: normal
>> User: devscri...@packages.debian.org
>> Usertag: wrap-and-sort
 
>> I've just had all comments removed from corosync's debian/control:

> Already mentioned to Christoph via IRC, but posting here in case others
> come across the bug.

> As of devscripts/2.22.2 (currently in unstable), we now have a temporary
> option called "--experimental-rts-parser" that should solve this
> problem.  Please try it out and report your successes/problems back to
> this bug.

> The goal is to remove the option again and have it be the new default
> behaviour once it has been properly tested.


Hello,

tested on enblend exim4 gnutls28 hugin findutils wothout problems. Thank
you.

The manpage says "This option requires python-debian version 0.1.43  or
later  to work.  However, some features will require 0.1.44 or later."

This should read "python3-debian" instead.

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



  1   2   >