Bug#1008063: transition: nodejs

[Jérémy Lal]

Le lun. 28 mars 2022 à 21:30, Adrian Bunk  a écrit :

> On Mon, Mar 28, 2022 at 04:59:58PM +0200, Jérémy Lal wrote:
> >
> > Yes, actually all packages depending on libnode-dev/sid now need to
> depend
> > on nodejs/sid, or else autopkgtest runs the tests against nodejs/testing,
> > and that fails.
> > I'll reupload them if that's all right.
> >
> > The other solution is to have /usr/bin/node12, /usr/bin/node14 and
> > /usr/bin/node
> > as an alternative link. Which is not going to happen for that transition.
>
> Isn't the actual bug that the Breaks of libnode83 against libnode72 does
> not cover the version in testing permitting obviously non-working
> combinations of packages, and the correct solution is to make the
> Breaks of libnode83 against libnode72 unversioned?
>
> libnode is not a standalone library but a way to embed into a specific
> nodejs version, is there a reason why libnode is a separate package and
> not part of the nodejs package with Provides: libnode83?
>
> Other ecosystems are doing it in a similar way, e.g. with perlapi-5.34.0


Transition happened anyway...

>

Bug#218605: apt: misleading dependency problem message

[Thomas Nemeth]

On Sat, 01 Nov 2003 15:21:42 + Henning Makholm  
wrote:


  The following packages have unmet dependencies:
autoconf2.13: Depends: autoconf (>= 2.50) but it is not going to be 
installed
  Depends: perl but it is not going to be installed
  Depends: libfile-temp-perl
  E: Broken packages
  $

The message from apt about unmet dependencies is grossly misleading;
I do have all of autoconf (>=2.50), perl and libfile-temp-perl.


I concur.

I've met this annoying, misleading error message. Today I wanted to
check why the wine-development package could not upgrade:

The following packages have unmet dependencies:
  wine-development : Depends: wine64-development (>= 6.18~repack-1) but 
6.0+repack-4 is to be installed or

  wine32-development (>= 6.18~repack-1)
E: Broken packages

wine-development depends on both wine..-developement in the new
6.18~repack-1 version. "But 6.0+repack-4 is to be installed" ? WTF,
The 6.0+repack-4 version is _already_ installed.

$ dpkg -l | grep wine..-deve
ii  wine32-development:i386  6.0+repack-4 
i386 Windows API implementation - 32-bit binary loader
ii  wine64-development   6.0+repack-4 
amd64Windows API implementation - 64-bit binary loader


It would be more useful to tell us what's blocking the upgrade (I
imagine it might be hard to know at the moment the error message
is displayed).

Something as "package xxx not found (not yet in the yyy repository)"
or "package xxx conflicts with installed package yyy". And actions
to take to fix the problem.

Aptitude may have the solution but really the apt error message
isn't helping at all.

Bug#1008790: RFS: tango-icon-theme/0.8.90-9 [ITA] -- Tango icon library

[Jeroen Ploemen]

Control: tags -1 moreinfo

On Fri, 01 Apr 2022 17:34:09 +
Matteo Bini  wrote:

> I am looking for a sponsor for my package tango-icon-theme:

hi Matteo,

the package as uploaded to mentors fails to build from source. Maybe
the time has come to convert it to the dh sequencer?

Tail of the buildlog:
```
I: Running cd /build/tango-icon-theme-0.8.90/ && env 
PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us 
-uc 
dpkg-buildpackage: info: source package tango-icon-theme
dpkg-buildpackage: info: source version 0.8.90-9
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Matteo Bini 

 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 debian/rules clean
test -x debian/rules
rm -f debian/stamp-makefile-build debian/stamp-makefile-install
GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1 /usr/bin/make -C . -k distclean
make[1]: Entering directory '/build/tango-icon-theme-0.8.90'
make[1]: *** No rule to make target 'distclean'.
make[1]: Leaving directory '/build/tango-icon-theme-0.8.90'
make: [/usr/share/cdbs/1/class/makefile.mk:91: makefile-clean] Error 2 (ignored)
rm -f debian/stamp-autotools
rmdir --ignore-fail-on-non-empty .
rmdir: failed to remove '.': Invalid argument
make: [/usr/share/cdbs/1/class/autotools.mk:64: makefile-clean] Error 1 
(ignored)
set -e;
dh_clean 
rm -f debian/stamp-autotools-files
cd "." && rm -f intltool-extract intltool-merge intltool-update 
po/.intltool-merge-cache
 dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building tango-icon-theme using existing 
./tango-icon-theme_0.8.90.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building tango-icon-theme in 
tango-icon-theme_0.8.90-9.debian.tar.xz
dpkg-source: info: building tango-icon-theme in tango-icon-theme_0.8.90-9.dsc
 debian/rules binary
test -x debian/rules
dh_testroot
dh_clean -k 
dh_clean: warning: The -k option is not supported in compat 12; use dh_prep 
instead
dh_clean: error: This feature was removed in compat 12.
make: *** [/usr/share/cdbs/1/rules/debhelper.mk:215: 
common-install-prehook-impl] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
I: copying local configuration
E: Failed autobuilding of package
I: unmounting dev/pts filesystem
I: unmounting proc filesystem
I: unmounting sys filesystem
I: cleaning the build env 
I: removing directory /var/cache/pbuilder/build//54322 and its subdirectories
```


pgp_ecWC_AcZ_.pgp
Description: OpenPGP digital signature

Bug#1008818: needrestart: creates root-owned .rpmdb in non-root user $HOME, possibly corrupting existing one

[Thorsten Glaser]

Package: needrestart
Version: 3.5-4
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: t...@mirbsd.de

I did notice root-owned .rpmdb directories in my user home and,
after log inspection, was able to track it down to apt-get runs.

Some reproducing and grepping later I found it’s needrestart
which does that.


-- Package-specific info:
needrestart output:
Your outdated processes:
dbus-daemon[18689], dconf-service[25185], dirmngr[19601], lynx[690], 
mksh[13426, 2187, 19552], screen[2866, 2185], xdg-desktop-por[25155], 
xdg-document-po[25162], xdg-permission-[25166]



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

Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages needrestart depends on:
ii  binutils   2.35.2-2
ii  dpkg   1.20.9
ii  gettext-base   0.21-4
ii  libintl-perl   1.26-3
ii  libmodule-find-perl0.15-1
ii  libmodule-scandeps-perl1.30-1
ii  libproc-processtable-perl  0.59-2+b1
ii  libsort-naturally-perl 1.03-2
ii  libterm-readkey-perl   2.38-1+b2
ii  perl   5.32.1-4+deb11u2
ii  xz-utils   5.2.5-2

Versions of packages needrestart recommends:
ii  sysvinit-core  2.96-7+deb11u1

Versions of packages needrestart suggests:
ii  iucode-tool  2.3.1-1
pn  needrestart-session | libnotify-bin  

-- no debconf information

Bug#1008819: mirror submission for mirrors.bkns.vn

[Thinh Van Hanh]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: mirrors.bkns.vn
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Thinh Van Hanh 
Country: VN Vietnam
Location: Hanoi/Vietnam/Asian
Sponsor: BKNS.VN https://www.bkns.vn




Trace Url: http://mirrors.bkns.vn/debian/project/trace/
Trace Url: http://mirrors.bkns.vn/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirrors.bkns.vn/debian/project/trace/mirrors.bkns.vn

Bug#1008820: lemonldap-ng: Latest stable update overwrites the config file with default

[Romain]

Package: lemonldap-ng
Version: 2.0.11+ds-4+deb11u1
Severity: important

Dear Maintainer,

Updating from Debian 11.2 to 11.3 lemonldap-ng package have replaced the 
lemondldap-ng config file 

/var/lib/lemonldap-ng/conf/lmConf-1.json with default

with the package one, making the system unusable as it basically contains all 
the configuration related to hosted apps, redirection urls, authentication 
backends and many more.

Luckily I had a backup - restoring the backup file and restarting apache2 fixed 
the problem.

I suggest that the newer releases do not overwrite anymore the files in 
/var/lib/lemonldap-ng/conf/, or moves this default configuration directory into 
etc

Cheers,

farfade


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

Kernel: Linux 5.10.0-13-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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 lemonldap-ng depends on:
ii  lemonldap-ng-handler  2.0.11+ds-4+deb11u1
ii  liblemonldap-ng-manager-perl  2.0.11+ds-4+deb11u1
ii  liblemonldap-ng-portal-perl   2.0.11+ds-4+deb11u1

lemonldap-ng recommends no packages.

lemonldap-ng suggests no packages.

-- no debconf information

Bug#1008821: apt-show-versions: cron job is deprecated

[Martin-Éric Racine]

Package: apt-show-versions
Version: 0.22.13
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

apt-show-versions still ships its own cron job. This is deprecated. It should 
instead leverage APT's own cron job (/etc/cron.daily/apt-compat, which in turn 
executes /usr/lib/apt/apt.systemd.daily).

Martin-Éric

- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 5.10.0-13-amd64 (SMP w/8 CPU threads)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages apt-show-versions depends on:
ii  apt  2.4.4
ii  libapt-pkg-perl  0.1.40+b1
ii  perl [libstorable-perl]  5.34.0-3

apt-show-versions recommends no packages.

apt-show-versions suggests no packages.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmJICLcACgkQrh+Cd8S0
17acjA//YiJu9iA2LzOUrZi3NncJcN5ACFD5oBr6Ap5UD9rOJLeaNiBHI2wWKdor
34J0wO+yIWZLBM+8vZX9Bix3wVfkkUlzmYKGAUcCKwvNGrJCH3zLaxU07KKmQP0N
cZKuuansBDFpzedVYARU01MAQevomdb7shwB7uN6/u428dSaSShz2eQWFPXxH/ts
Hz00kuhmiznwuqKMxzGO6udyrVJwIyRGfPa1sDYZAVpN1auKWkpVOsY0Lqe/06SK
onL/JRnr5bmngIhv2hml3WqNOHNKV8CqL43GbBpkQrvz8sXfTI7Dg3OXl9dqQ7PP
KggKMPqUtzGoXPeuMB/R9B4ZKI6iAi5T5tKzKWbaBl/V4oR5mdy6xbPWfhwZSTnk
hoZMB8Jgf2pbyoh9EOghIyXG6ZRKUC26ytFF+HDUi6pIUtLm7eAB56jqGjubPTdg
S7XpSPz9eWojfh1nbvhs+LWhhOOgDJuE3u/9hhyGgout1+j+6pTcEucW6NSNOJrD
r+nVhPLmB86M7N7SzSALoBO1H5kuvLDiDRREuVa+q0SeHrttppZ/m9foVWnw++P/
7eOFMDkqg+wlOcVjM1OxqvTah2+1FNfTX4Ep0AqTlBRXE3J8y3u2CVgAH2NKPC+4
wfnmB+X12qpop2FqTrUQ3I1AgxSqcvulev6QSLiVwn9GZmFCCjc=
=OOyc
-END PGP SIGNATURE-

Bug#1008784: upgrade-system: Please restore cron.daily snippet for non-systemd systems

[Martin-Éric Racine]

On Sat, Apr 2, 2022 at 11:23 AM Mark Hindley  wrote:
> On Sat, Apr 02, 2022 at 09:44:49AM +0300, Martin-Éric Racine wrote:
> > The key problem is APT updating its lists several times in a row
> > whenever cron.daily is run i.e. via every package that installs a
> > similar snipet either via cron or via apt.conf.d, which quickly
> > becomes redundant.
>
> Didn't the test
>
> # Don't bother if /sbin/init is systemd. APT ships native timers nowadays.
> if [ -d /run/systemd/system ]; then exit 0; fi
>
> already protect against that?

As I've repeatedly noticed on my Testing host, it doesn't. At some
point, I wondered why daily cron jobs took forever and noticed that
APT updates its lists several times. One of those was upgrade-system's
script. This made it clear to me that there's some pointless
redundancy. Looking closer at APT configuration options, it appears
that enabling the following does the same as the cron job's update and
autoclean:

APT {
Periodic {
Enable "1";
Update-Package-Lists "1";
Download-Upgradeable-Packages "1";
Download-Upgradeable-Packages-Debdelta "1";
AutocleanInterval "1";
CleanInterval "1";
};
};

As it so happens, unattended-upgrades leverages that too. This leaves
exactly one feature of the script...

> > Which part of the cron snipet specifically do you find essential?
>
> Well, not essential but after upgrading I noticed I no longer got the daily
> email I had come to expect about upgradable packages.

... and apt-show-versions covers that. Would that work for you?

Martin-Éric

Bug#1008784: upgrade-system: Please restore cron.daily snippet for non-systemd systems

[Mark Hindley]

Martin-Éric,

On Sat, Apr 02, 2022 at 09:44:49AM +0300, Martin-Éric Racine wrote:
> Is there such a thing as Debian systems that don't run off systemd nowadays?

Absolutely. Alternative inits which are still viable include runit, openrc and
sysvinit. I use all 3 in various places.

> The key problem is APT updating its lists several times in a row
> whenever cron.daily is run i.e. via every package that installs a
> similar snipet either via cron or via apt.conf.d, which quickly
> becomes redundant.

Didn't the test 

# Don't bother if /sbin/init is systemd. APT ships native timers nowadays.
if [ -d /run/systemd/system ]; then exit 0; fi

already protect against that?

> Which part of the cron snipet specifically do you find essential?

Well, not essential but after upgrading I noticed I no longer got the daily
email I had come to expect about upgradable packages.

Thanks

Mark

Bug#977647: 5.10.4 Debian kernel does not boot on amd64 with btrfs rootfs

[Salvatore Bonaccorso]

Control; tags -1 + moreinfo

On Thu, Mar 04, 2021 at 10:43:23AM +0900, Ryutaroh Matsumoto wrote:
> Package: src:linux
> Version: 5.10.19-1
> Followup-For: Bug #977647
> Control: retitle -1 5.10.19 Debian kernel has mysterious tpm error in dmesg
> Control: severity -1 minor
> 
> Dear Maintainer,
> 
> The boot failure problem originally reported as #977647 somehow gets fixed
> in Debian kernel 5.10.19.
> 
> The severity seems now minor.
> It has still the mysterious dmesg error on tpm as follows.
> The full dmesg log is attached.

Do you still have the issues? Otherwise let's close this bug.

Regards,
Salvatore

Bug#692917: printer-driver-escpr: color error on armel

[Thorsten Alteholz]

Hi Kurt and Patrik,

thanks a lot for your reports. Can you please check whether the problem 
still exists after a few new upstream versions?


Thanks!
 Thorsten

Bug#1008820: lemonldap-ng: Latest stable update overwrites the config file with default

[Yadd]

On 02/04/2022 10:25, Romain wrote:

Package: lemonldap-ng
Version: 2.0.11+ds-4+deb11u1
Severity: important

Dear Maintainer,

Updating from Debian 11.2 to 11.3 lemonldap-ng package have replaced the 
lemondldap-ng config file

/var/lib/lemonldap-ng/conf/lmConf-1.json with default

with the package one, making the system unusable as it basically contains all 
the configuration related to hosted apps, redirection urls, authentication 
backends and many more.

Luckily I had a backup - restoring the backup file and restarting apache2 fixed 
the problem.

I suggest that the newer releases do not overwrite anymore the files in 
/var/lib/lemonldap-ng/conf/, or moves this default configuration directory into 
etc

Cheers,

farfade


Hi,

LLNG adds a configuration file on each update. If you want to customize 
default configuration, simply copy it into 
/var/lib/lemonldap-ng/conf/lmConf-2.json (and change cfgNum value), then 
updates won't overwrite it.


Cheers,
Yadd

Bug#981325: logcheck: Remove support of syslog-summary package.

[Jon Daley]

Package: logcheck
Version: 1.3.23
Followup-For: Bug #981325

I've used syslog-summary for a long time in conjunction with logcheck. 
I see that it has been removed from Debian.

Is there any plans for having something similar so that the logcheck reports 
can be smaller 
and avoid the repeated messages?


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

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

Versions of packages logcheck depends on:
ii  adduser 3.118
ii  cron [cron-daemon]  3.0pl1-137
ii  lockfile-progs  0.1.18
ii  logtail 1.3.23
ii  mime-construct  1.11+nmu3
ii  postfix [mail-transport-agent]  3.5.6-1+b1
ii  rsyslog [system-log-daemon] 8.2102.0-2

Versions of packages logcheck recommends:
ii  logcheck-database  1.3.23

Versions of packages logcheck suggests:
pn  syslog-summary  

-- Configuration Files:
/etc/logcheck/logcheck.conf [Errno 13] Permission denied: 
'/etc/logcheck/logcheck.conf'
/etc/logcheck/logcheck.logfiles [Errno 13] Permission denied: 
'/etc/logcheck/logcheck.logfiles'

-- no debconf information

Bug#1008822: sane-utils: error while purging package

[Martin-Éric Racine]

Package: sane-utils
Version: 1.1.1-5
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Purging configuration files for sane-utils (1.1.1-5) ...
Use of uninitialized value $_ in pattern match (m//) at 
/usr/share/perl5/DebianNet.pm line 589.
/usr/sbin/deluser: `saned' still has `saned' as their primary group!

- -- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 'testing')
Architecture: i386 (i586)

Kernel: Linux 5.16.0-5-686 (SMP w/1 CPU thread; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sane-utils depends on:
ii  adduser3.121
ii  debconf [debconf-2.0]  1.5.79
ii  init-system-helpers1.62
ii  libavahi-client3   0.8-5
ii  libavahi-common3   0.8-5
ii  libc6  2.33-7
ii  libieee1284-3  0.2.11-14
ii  libjpeg62-turbo1:2.1.2-1
ii  libpng16-161.6.37-3
pn  libsane1   
ii  libsystemd0250.4-1
ii  libusb-1.0-0   2:1.0.25-1
ii  libxml22.9.13+dfsg-1
ii  lsb-base   11.1.0
ii  update-inetd   4.51

sane-utils recommends no packages.

Versions of packages sane-utils suggests:
pn  avahi-daemon  
pn  unpaper   

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmJIGHcACgkQrh+Cd8S0
17aS3w/+I/iZ/fQjI3rp/r2CSTPyHnykvlsQuuNwGsWWgRS9sujiLaKofTBz95k6
5S4AtPXk1zVVLW+yMB1eARrkANCjXS9Mr8BziFE39bIV4UJbvHmqHJbHz8valEeT
Wfl7WruUYrwrWTkN/w+fFews/Hjfeq0L4hRegsrXUNO8JAWVdp01H8M7/wzCzTSa
WMr3+nR2MgyNT6lL2O2981/4RUvp8zm5gFOaFxDXL5bNmCSJhrhB21bx6/ofr46e
Def/sz4Ed1WR2rXx26KAVLUXvdDqhlda2K9jiucvZRM6P5BGT8EGnc5RmkZyXvPD
ZAXHti3HWlXS2RDhymSqLD5wxCaD+Apu6EJelipkmU8GMj32Nn8hKgi7MhY02J0J
ntUf65Jkmf2cDgWd9AWXSh3sMJtnGRYzUfJI6kP1mDMtR6hGi6XBCEf0WiYchbIj
T00R0DwXg/sm2g1S3ln2q3FR2/i9sdkDj0e2RArOuTccd0JdJGD3pjcxNa2YNIJO
DyPgJvmxlhEITccvNqqe443PJK+8EW1TrzNUl2vhL6TY0uNgkEw1VQ4u91s9bB9m
esgypSSZIEleCkc9kRKerdfHMXVL9SCzigyL2xInNJqAcULNYOTjaK+UnL48ojLj
thGBh3/bt2Pk3Oyu0oDeQW9f1+1YtVUY9+NhlUQIKv4A9OfpNrs=
=5cIs
-END PGP SIGNATURE-

Bug#851883: printer-driver-escpr: Rear Paper Feed Slot Not Selectable for WF-3540

[Thorsten Alteholz]

Hi George,

can you please check whether the problem exists after a few new upstream 
version?


Probably the upstream report from you and Brian had been a success.

Thanks!
 Thorsten

Bug#839245: printer-driver-escpr: no printing at maximum resolution

[Thorsten Alteholz]

Hi Laurent,

thanks a lot for your report. Can you please check whether the problem 
exists after a few new upstream versions?


However, the ppd file was provided by Epson, so there has to be a reason 
why they didn't use the maximum resolution in it.


Thanks!
 Thorsten

Bug#1008823: transition: thrift

[GCS]

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

Hi RMs,

A quick transition of thrift from 0.13.0 to 0.16.0 as the only reverse
build dependency is gnuradio. It builds with the new thrift version as
well.

Thanks for considering,
Laszlo/GCS

Bug#1008287: [Pkg-javascript-devel] Bug#1008287: Failed install of npm backports package

[Christian P. MOMON]

Le 26/03/2022 à 18:12, Christian P. MOMON a écrit :
  And reading the package page, 
https://packages.debian.org/bullseye-backports/npm, we can see:

- title: Package: npm (8.3.1~ds-1~bpo11+1)
- Download Source Package npm: [npm_8.5.5~ds1-1~bpo11+1.dsc]


 I checked today and now it is:
- title: Package: npm (8.5.5~ds1-1~bpo11+1)
- Download Source Package npm: [npm_8.5.5~ds1-1~bpo11+1.dsc]

 So the problem seems solved \o/

 Librement,

 Cpm.
--
Christian Pierre MOMON
Tél. +33 (0)6 26 72 40 04


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008824: gourmand: Can't print or export to PDF

[Jon Daley]

Package: gourmand
Version: 1.0.0-6
Severity: normal

I'm back again...

A number of years ago, I reported that gourmet couldn't print due to poppler 
not being 
depended upon, and you fixed it by adding the dependency.  I see there is a 
python3-poppler-qt5 package, but I installed that, and it doesn't seem to work.

I am running a bullseye distribution, but downloaded gourmand from bookworm, 
since 
gourmet can no longer print either, because I no longer have python2.

gourmand is reporting poppler errors, so that code is still there even though 
the 
dependency was removed in gourmet 0.17.4-5

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

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

Versions of packages gourmand depends on:
ii  gir1.2-gtk-3.0   3.24.24-4+deb11u2
ii  python3  3.9.2-3
ii  python3-argcomplete  1.8.1-1.5
ii  python3-bs4  4.9.3-1
ii  python3-gi   3.38.0-2
ii  python3-gst-1.0  1.18.3-1
ii  python3-lxml 4.6.3+dfsg-0.1+deb11u1
ii  python3-pil  8.1.2+dfsg-0.3+deb11u1
ii  python3-reportlab3.5.59-2
ii  python3-requests 2.25.1+dfsg-2
ii  python3-sqlalchemy   1.3.22+ds1-1
ii  python3-toml 0.10.1-1

Versions of packages gourmand recommends:
pn  python3-gtkspellcheck  
pn  python3-pyglet 

Versions of packages gourmand suggests:
pn  python3-ebooklib  

-- no debconf information

Bug#1008825: glom FTBFS with Python 3.10

[Adrian Bunk]

Source: glom
Version: 1.30.4-6.1
Severity: serious
Tags: ftbfs bookworm sid patch
Forwarded: 
https://gitlab.gnome.org/GNOME/glom/-/commit/118563d2693626c73cdeeb5af917b3eb0e158c6d

https://buildd.debian.org/status/logs.php?pkg=glom&ver=1.30.4-6.1%2Bb5

...
checking for the distutils Python package... no
configure: error: cannot import Python module "distutils".
Please check your Python installation. The error was:
:1: DeprecationWarning: The distutils package is deprecated and slated 
for removal in Python 3.12. Use setuptools or check PEP 632 for potential 
alternatives
tail -v -n \+0 config.log

Bug#1008826: seafile-gui: Depends: libseafile0 (>= 8.0.6+ds1) but 8.0.6-1 is to be installed

[Adrian Bunk]

Package: seafile-gui
Version: 8.0.6+ds1-1
Severity: serious

The following packages have unmet dependencies:
 seafile-gui : Depends: libseafile0 (>= 8.0.6+ds1) but 8.0.6-1 is to be 
installed
   Depends: seafile-daemon (>= 8.0.6+ds1) but it is not going to be 
installed

Bug#1008828: python3-spf-engine: fails with ImportError: cannot import name 'own_socketfile' from 'spf_engine.util'

[Bjørn Mork]

Package: python3-spf-engine
Version: 2.9.2-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

Installing pyspf-milter with default dependencies and settings results
in

# journalctl -u pyspf-milter
- -- Journal begins at Sat 2022-03-26 15:26:01 CET, ends at Sat 2022-04-02 
12:11:13 CEST. --
Apr 02 12:04:07 canardo systemd[1]: Started pySPF Milter.
Apr 02 12:04:07 canardo pyspf-milter[372481]: Traceback (most recent call last):
Apr 02 12:04:07 canardo pyspf-milter[372481]: Traceback (most recent call last):
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File "/usr/bin/pyspf-milter", 
line 11, in 
Apr 02 12:04:07 canardo pyspf-milter[372481]: 
load_entry_point('spf-engine==2.9.2', 'console_scripts', 'pyspf-milter')()
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 474, in 
load_entry_point
Apr 02 12:04:07 canardo pyspf-milter[372481]: return 
get_distribution(dist).load_entry_point(group, name)
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2846, in 
load_entry_point
Apr 02 12:04:07 canardo pyspf-milter[372481]: return ep.load()
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2450, in load
Apr 02 12:04:07 canardo pyspf-milter[372481]: return self.resolve()
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2456, in 
resolve
Apr 02 12:04:07 canardo pyspf-milter[372481]: module = 
__import__(self.module_name, fromlist=['__name__'], level=0)
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/spf_engine/milter_spf.py", line 40, in 
Apr 02 12:04:07 canardo pyspf-milter[372481]: from spf_engine.util import 
own_socketfile
Apr 02 12:04:07 canardo pyspf-milter[372481]: ImportError: cannot import name 
'own_socketfile' from 'spf_engine.util' 
(/usr/lib/python3/dist-packages/spf_engine/util.py)
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File "/usr/bin/pyspf-milter", 
line 11, in 
  
load_entry_point('spf-engine==2.9.2', 'console_scripts', 'pyspf-milter')()
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 474, in 
load_entry_point
  return 
get_distribution(dist).load_entry_point(group, name)
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2846, in 
load_entry_point
  return ep.load()
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2450, in load
  return self.resolve()
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2456, in 
resolve
  module = 
__import__(self.module_name, fromlist=['__name__'], level=0)
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/spf_engine/milter_spf.py", line 40, in 
  from spf_engine.util import 
own_socketfile
Apr 02 12:04:07 canardo pyspf-milter[372481]: ImportError: cannot import name 
'own_socketfile' from 'spf_engine.util' 
(/usr/lib/python3/dist-packages/spf_engine/util.py)
Apr 02 12:04:07 canardo systemd[1]: pyspf-milter.service: Main process exited, 
code=exited, status=1/FAILURE
Apr 02 12:04:07 canardo systemd[1]: pyspf-milter.service: Failed with result 
'exit-code'.


No need to clutter the archive with completely broken and untested packages.


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

Kernel: Linux 5.10.0-13-amd64 (SMP w/8 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)

Versions of packages python3-spf-engine depends on:
ii  python3  3.9.2-3
ii  python3-authres  1.2.0-2
ii  python3-spf  2.0.14-2

python3-spf-engine recommends no packages.

python3-spf-engine suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iGwEARECACwWIQR3fjfc8EF8nPbC0aDXSuqSjBsiyQUCYkgi8Q4cYmpvcm5AbW9y
ay5ubwAKCRDXSuqSjBsiyarCAKCAzlYvQ8KoeYFTwu57/rcZUaVWZgCeJh9IDyHM
qzAsx/mDicjW7tkbafU=
=TY8J
-END PGP SIGNATURE-

Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'

[Bjørn Mork]

Package: pysrs-bin
Version: 1.0.3-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

# envfrom2srs
Traceback (most recent call last):
  File "/usr/bin/envfrom2srs", line 14, in 
from ConfigParser import ConfigParser, DuplicateSectionError
ModuleNotFoundError: No module named 'ConfigParser'

# srs2envtol
Traceback (most recent call last):
  File "/usr/bin/srs2envtol", line 14, in 
from ConfigParser import ConfigParser, DuplicateSectionError
ModuleNotFoundError: No module named 'ConfigParser'

No need to clutter the archive with broken and untested packages.
Please remove

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

Kernel: Linux 5.10.0-13-amd64 (SMP w/8 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)

Versions of packages pysrs-bin depends on:
ii  python3  3.9.2-3
ii  python3-srs  1.0.3-2

pysrs-bin recommends no packages.

pysrs-bin suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iGwEARECACwWIQR3fjfc8EF8nPbC0aDXSuqSjBsiyQUCYkgktA4cYmpvcm5AbW9y
ay5ubwAKCRDXSuqSjBsiyUJdAJ4zvzZBL6hIfzScL01SNMcAQDNSEQCfZZJU9yuy
jyC6TtdcMxqBEPpi278=
=yarJ
-END PGP SIGNATURE-

Bug#944485: mmdebstrap: please implement the creation of QEMU/KVM images for autopkgtest-virt-qemu

[Christian Kastner]

On 2022-04-02 07:58, Johannes Schauer Marin Rodrigues wrote:
> Quoting Christian Kastner (2022-03-23 21:36:59)
>> I initially wondered whether foreign architecture guestfish/supermin
>> binaries couldn't be run through qemu-user-static, but that solution
>> would be just far too hacky I think.
> 
> I think how "hacky" it is depends on how you look at it. The advantage is, 
> that
> then you only have to maintain the "native" codepath which you run under
> emulation if you want a foreign arch binary. I just tried it out and it seems
> to work as expected.

Well, that's cool to hear!

> Big downside: running qemu (from guestfish) inside qemu (from
> qemu-user-static) is *ralllyy sloow*. XD

How slow? On my end, IIRC sbuild-qemu-create takes 2mins to build a
native image, and 12-13mins to build a foreign one.

However, that's wall-time, for a process that can run unattended. Having
a one-time, slow, non-interactive process might not be that bad,
compared to needing root.

> But I think it's a good idea to have for the sake of symmetry. We'd then have:
> 
>  - guestfish
>  - fastest method when creating a native image
>  - slowest method when creating a foreign image
>  - initramfs
>  - medium speed for both native and foreign images
> 
> Then the new tool could have a --method switch with possible values:
> 
>  - "auto" choose guestfish if installed for native images and initramfs
>otherwise
>  - "guestfish" forces guestfish for native and foreign
>  - "initramfs" forces initramfs for native and foreign

Sounds good.

>> Since these are QEMU options, I think autopkgtest-virt-qemu's existing
>> --qemu-options could be used to supply kernel/initrd/rootfs?
> 
> Yes, that might work. Though from reading the autopkgtest-virt-qemu man page I
> think this will not support paths with spaces. On the other hand, the man page
> also says that additional arguments can be supplied via a file that contains
> one argument per line.

Indeed, I just checked and autopkgtest-virt-qemu just calls .split() on
the string. The file workaround should be fine, though.

> I'm not so sure whether it's a fantastic idea. First I want to evaluate other
> existing tools like debos and see if they can do the job or not. I want to
> resist the NIH syndrome.

Full ACK. Hence the focus on extending vmdb2 if possible, or using
guestfish or debos, but I myself don't favor any particular tool. My
first choice would simply be the tool that accomplishes it.

> Another question that I'm still pondering is how much configuration this new
> tool should allow. I'm tempted to make it just fit for the use-case of
> autopkgtest backend or porterbox or sbuild-qemu backend just to keep it 
> simple.

Indeed, I have asked myself the same question a number of times.

It's tempting to make this as flexible as possible, but in the end, it's
main use cases are build and test environments. From experience, this
means that one frequently needs to configure hardware (e.g. number of
CPUs), or modify the build environment (configure external repos,
pre-install packages, copy files e.g. SSH keys).

So it can be helpful to facilitate a few common uses, but it's probably
overkill to allow for all, and it's probably also not needed: after all,
one can always boot the image, and modify interactively.

> And lastly, the name is also still an open question.

The hardest part :D

> Alas, I'll probably not get to working on this much in the next two weeks.

Best of luck! I wish I could do more to help, but still swamped at the
moment, with little time for Debian.

Best,
Christian

Bug#1008830: gnome depends on gedit-plugins whereas gnome-core depends on gnome-text-editor | gedit

[Patrice Duroux]

Package: gnome
Version: 1:42+2
Severity: wishlist

Dear Maintainer,

Should this be changed also?

Thanks,
Patrice


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

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

Versions of packages gnome depends on:
ii  avahi-daemon 0.8-5
ii  cheese   41.1-1
ii  cups-pk-helper   0.2.6-1+b1
ii  desktop-base 11.0.3
ii  evolution3.44.0-2
ii  evolution-plugins3.44.0-2
ii  file-roller  3.42.0-1
ii  gedit-plugins41.0-1
ii  gnome-calendar   42.0-1
ii  gnome-clocks 42.0-1
ii  gnome-color-manager  3.36.0-1+b1
ii  gnome-core   1:42+2
ii  gnome-maps   42.0-1
ii  gnome-music  42.0-1
ii  gnome-sound-recorder 42.0-1
ii  gnome-todo   41.0-1
ii  gnome-tweaks 42~beta-1
ii  gnome-weather42.0-1
ii  gstreamer1.0-libav   1.20.1-1
ii  gstreamer1.0-plugins-ugly1.20.1-1
ii  libgsf-bin   1.14.49-1
ii  libproxy1-plugin-networkmanager  0.4.17-2
ii  libreoffice-calc 1:7.3.2~rc2-1
ii  libreoffice-gnome1:7.3.2~rc2-1
ii  libreoffice-impress  1:7.3.2~rc2-1
ii  libreoffice-writer   1:7.3.2~rc2-1
ii  network-manager-gnome1.26.0-1
ii  orca 42.0-1
ii  rhythmbox3.4.4-5+b1
ii  rhythmbox-plugin-cdrecorder  3.4.4-5+b1
ii  rhythmbox-plugins3.4.4-5+b1
ii  rygel-playbin0.40.3-1+b1
ii  rygel-tracker0.40.3-1+b1
ii  seahorse 41.0-2+b1
ii  shotwell 0.30.14-2
ii  simple-scan  42.0-1
ii  totem-plugins42.0-1
ii  xdg-user-dirs-gtk0.10-3

Versions of packages gnome recommends:
ii  gnome-games 1:42+2
ii  gnome-remote-desktop42.0-1
ii  nautilus-extension-brasero  3.12.3-1
ii  transmission-gtk3.00-2

Versions of packages gnome suggests:
ii  alacarte 3.44.1-1
pn  empathy  
pn  firefox-esr-l10n-all | firefox-l10n-all  
pn  goobox | sound-juicer
ii  polari   42.0-1
pn  vinagre  
pn  webext-ublock-origin 

Versions of packages gnome-core depends on:
ii  adwaita-icon-theme42~really41.0-1
ii  at-spi2-core  2.44.0-3
ii  baobab42.0-1
ii  caribou   0.4.21-7.2
ii  dconf-cli 0.40.0-3
ii  dconf-gsettings-backend   0.40.0-3
ii  eog   42.0-1
ii  evince42.1-2
ii  evolution-data-server 3.44.0-3
ii  firefox   98.0-2
ii  fonts-cantarell   0.303-2
ii  gdm3  42.0-1
ii  gedit 41.0-3
ii  gkbd-capplet  3.26.1-2
ii  glib-networking   2.72.0-1
ii  gnome-backgrounds 42.0-1
ii  gnome-bluetooth   3.34.5-7
ii  gnome-calculator  1:42.0-3
ii  gnome-characters  42.0-1
ii  gnome-console 42~beta-2
ii  gnome-contacts42.0-1
ii  gnome-control-center  1:42.0-1
ii  gnome-disk-utility42.0-1
ii  gnome-font-viewer 42.0-1
ii  gnome-keyring 40.0-3
ii  gnome-logs42.0-1
ii  gnome-menus   3.36.0-1
ii  gnome-online-accounts 3.44.0-1
ii  gnome-online-miners   3.34.0-4
ii  gnome-session 42.0-1
ii  gnome-settings-daemon 42.1-2
ii  gnome-shell   42.0-2
ii  gnome-shell-extensions42.0-2
ii  gnome-software42.0-1
ii  gnome-sushi   41.1-1
ii  gnome-system-monitor  42.0-1
ii  gnome-terminal3.44.0-1
ii  gnome-text-editor 42.0-2
ii  gnome-themes-extra3.28-1
ii  gnome-user-docs   42.0-1
ii  gnome-user-share  3.34.0-5
ii  gsettings-desktop-schemas 42.0-1
ii  gstreamer1.0-packagekit   1.2.5-3
ii  gstreamer1.0-plugins-base 1.20.1-1
ii  gstreamer1.0-plugins-good 1.20.1-1
ii  gvfs-backends 1.50.0-1
ii  gvfs-fuse 1.50

Bug#1008831: ITP: graide -- GRAphite Integrated Development Environment

[Bastian Germann]

Package: wnpp
Owner: Bastian Germann 

* Package name: graide
  Upstream Author : SIL International
* URL : https://github.com/silnrsi/graide
* License : LGPL-2.1+
  Programming Lang: Python
  Description : integrated development environment for fonts with Graphite 
features

Graide is an integrated development environment that can be used to develop fonts with Graphite 
features. Graphite is a "smart font" system developed specifically to handle the complexities of 
lesser-known languages of the world and is already available in Debian (library and compiler).

Bug#1008718: src:yosys: fails to migrate to testing for too long: FTBFS on mips64el and s390x & autopkgtest regression

[Paul Gevers]

Hi Daniel,

On 01-04-2022 23:09, Daniel Gröber wrote:

How would I go about documenting and excluding s390x from building yosys


You'll need to ask for the removal of the s390x binary from unstable at 
least (ftp.debian.org pseudo packages). If you fear it could start 
building successfully by accident again you could document that in the 
Architecture field in the debian/control file, which is meant for that 
purpose (but if you believe this will be fixed in the future and no 
accidental successful build will happen before it's really fixed, it's 
typically recommended to leave "Architecture: any").



and is there anything I need to do about the non-offical Debian ports
architectures or can I just let those builds fail without it affecting
yosys' migration?


No, ports don't count for migration, only release architectures.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1007799: Backport to bullseye

[David Schiller]

Hi!

Any chance we can get this into the bullseye kernel?

Best regards,
David


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

Bug#1008832: freeradius-python3: Module not linked with libpython when built with Python 3.10

[Adrian Bunk]

Package: freeradius-python3
Version: 3.0.25+dfsg-1
Severity: serious
Forwarded: https://github.com/FreeRADIUS/freeradius-server/issues/4441

Package: freeradius-python3
Version: 3.0.25+dfsg-1+b1
Depends: freeradius (= 3.0.25+dfsg-1+b1), libc6 (>= 2.4), libpython3.9 (>= 
3.9.1)

$ objdump -p /usr/lib/freeradius/rlm_python3.so | grep NEEDED  NEEDED   
libpython3.9.so.1.0
  NEEDED   libpthread.so.0
  NEEDED   libdl.so.2
  NEEDED   libc.so.6
  NEEDED   ld-linux-x86-64.so.2
$

Package: freeradius-python3
Version: 3.0.25+dfsg-1+b2
Depends: freeradius (= 3.0.25+dfsg-1+b2), libc6 (>= 2.4)

$ objdump -p /usr/lib/freeradius/rlm_python3.so | grep NEEDED
  NEEDED   libpthread.so.0
  NEEDED   libdl.so.2
  NEEDED   libc.so.6
  NEEDED   ld-linux-x86-64.so.2
$

Bug#1008780: dpkg: protection shouldn't apply to foreign-arch packages

[Guillem Jover]

Hi!

On Fri, 2022-04-01 at 14:41:51 +0200, Stephen Kitt wrote:
> Package: dpkg
> Version: 1.20.9
> Severity: normal

> Protection is applied to foreign-arch packages (e.g. libgcc-s1:i386 on
> amd64) even though they aren't relevant to the scenarios that
> protection is designed to prevent (as I understand it):

Right, AFAIR this was a workaround used to try to help apt with an
upgrade scenario where otherwise it was unable to cope well with the
libgcc1 to libgcc-s1 transition.

> > Protected packages contain mostly important system boot
> > infrastructure. Removing them might cause the whole system to be
> > unable to boot, so use with caution.
> 
> Would it be possible for removal of such packages not to require
> --force-remove-protected, at least if the corresponding native arch
> package is installed? The latter check isn't useful with libraries
> (where, if nothing depends on them, we can be certain that they are
> not needed for the system to boot), but would catch situations where
> e.g. the system's init is not the native package. (I imagine there's a
> better approach to this.)

In principle shared libraries should never be marked Essential:yes nor
Protected:yes, I think this was a special case, that will go away once
the shared library gets the Protected filed dropped after the
transition is over.

I think at least the description for the field in dpkg(1), deb-control(5)
and probably «/usr/share/doc/dpkg/protected-field.txt» should be made more
clear. I'll try to prepare a patch for this today.


And while I think in this specific case that you mention, the heuristic
that you propose might make sense. I'm not sure that is generalizable
or can be encoded in a neutral way in dpkg itself. As I don't think it
would be appropriate for dpkg to assume that all Mulit-Arch:same packages
are going to be shared libraries, or say encode specific package name
patterns or even assumed semantics out of section names.

Thanks,
Guillem

Bug#1008833: gnome-console: Package should recommend nautilus-extension-gnome-console

[Santiago Batista]

Package: gnome-console
Version: 42~beta-2
Severity: wishlist
X-Debbugs-Cc: santibati...@gmail.com

Dear Maintainer,

In light of using gnome-console as a replacement of gnome-terminal, it would be 
nice if
this package recommended nautilus-extension-gnome-console.

This is similar to how gnome-terminal recommends 
nautilus-extension-gnome-terminal.

Thank you for your time packaging this application!

Best regards,
Santiago

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

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

Versions of packages gnome-console depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  gsettings-desktop-schemas42.0-1
ii  libc62.33-7
ii  libglib2.0-0 2.72.0-1
ii  libgtk-3-0   3.24.33-1
ii  libgtop-2.0-11   2.40.0-2
ii  libhandy-1-0 1.5.91-1
ii  libpango-1.0-0   1.50.6+ds-1
ii  libvte-2.91-00.67.90-2

gnome-console recommends no packages.

gnome-console suggests no packages.

-- no debconf information

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

[Francesco C]

linux-image-5.16.0-6-686 (5.16.18-1) still does not boot on a
different machine with the same controller.

Vanilla kernel 5.16.18 built with custom .config for the specific
machine fails to boot at the same point too.

I'm also trying to track stable patches in the stable tree queue
(https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/log/)
but it seems to me at the moment there not any patch about ata_pxii in
the 5.16.x branch and in the 5.17.x either.

Bug#1000980: kubernetes: diff for NMU version 1.20.5+really1.20.2-1.1

[Florian Ernst]

Control: tags 1000980 + patch
Control: tags 1000980 + pending

Dear maintainer,

I've prepared an NMU for kubernetes (versioned as 1.20.5+really1.20.2-1.1)
and uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

The diff is based on what I previously sent to this bugreport in
.
The binary package debdiff just lists
| $ debdiff kubernetes-client_1.20.5+really1.20.2-1_amd64.deb 
kubernetes-client_1.20.5+really1.20.2-1.1_amd64.deb
| File lists identical (after any substitutions)
| 
| Control files: lines which differ (wdiff format)
| 
| Installed-Size: [-40405-] {+38907+}
| Version: [-1.20.5+really1.20.2-1-] {+1.20.5+really1.20.2-1.1+}

I tested the kubectl binary against a local KinD cluster and found no
issues. Basic testing as follows:
| 15:47:27 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl create deployment nginx 
--image=nginx
| deployment.apps/nginx created
| 15:47:57 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl expose deployment nginx 
--type LoadBalancer --port 80
| service/nginx exposed
| 15:48:04 ⌁0% 1d :~/debian/temp/kubernetes $ kubectl get svc nginx
| NAMETYPE   CLUSTER-IP EXTERNAL-IPPORT(S)AGE
| nginx   LoadBalancer   10.96.54.121   172.19.255.1   80:30032/TCP   14s
| 15:48:18 ⌁0% 1d :~/debian/temp/kubernetes $ curl 172.19.255.1
| 
| 
| 
| Welcome to nginx!
| 
| html { color-scheme: light dark; }
| body { width: 35em; margin: 0 auto;
| font-family: Tahoma, Verdana, Arial, sans-serif; }
| 
| 
| 
| Welcome to nginx!
| If you see this page, the nginx web server is successfully installed and
| working. Further configuration is required.
| 
| For online documentation and support please refer to
| http://nginx.org/";>nginx.org.
| Commercial support is available at
| http://nginx.com/";>nginx.com.
| 
| Thank you for using nginx.
| 
| 
| 15:48:25 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl get po
| NAME READY   STATUSRESTARTS   AGE
| nginx-6799fc88d8-v5ms9   1/1 Running   0  77s
| 15:48:59 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl exec -it 
nginx-6799fc88d8-v5ms9 -- hostname
| nginx-6799fc88d8-v5ms9
| 15:49:20 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl delete deploy,svc nginx
| deployment.apps "nginx" deleted
| service "nginx" deleted
| 15:49:36 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl get po
| No resources found in default namespace.
| 15:49:41 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl version
| Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", 
GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"archive", 
BuildDate:"2022-04-02T13:36:06Z", GoVersion:"go1.17.8", Compiler:"gc", 
Platform:"linux/amd64"}
| Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", 
GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", 
BuildDate:"2021-05-21T23:01:33Z", GoVersion:"go1.16.4", Compiler:"gc", 
Platform:"linux/amd64"}

Please also find attached the local build log.

Best regards,
Flo
diff -Nru kubernetes-1.20.5+really1.20.2/debian/changelog kubernetes-1.20.5+really1.20.2/debian/changelog
--- kubernetes-1.20.5+really1.20.2/debian/changelog	2021-06-13 09:08:18.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/changelog	2022-04-02 15:36:06.0 +0200
@@ -1,3 +1,10 @@
+kubernetes (1.20.5+really1.20.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build using golang-1.17-go (Closes: #1000980)
+
+ -- Florian Ernst   Sat, 02 Apr 2022 15:36:06 +0200
+
 kubernetes (1.20.5+really1.20.2-1) unstable; urgency=medium
 
   * This is actually still 1.20.2
diff -Nru kubernetes-1.20.5+really1.20.2/debian/control kubernetes-1.20.5+really1.20.2/debian/control
--- kubernetes-1.20.5+really1.20.2/debian/control	2021-06-13 09:08:18.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/control	2022-02-27 13:55:20.0 +0100
@@ -2,7 +2,7 @@
 Section: admin
 Priority: optional
 Maintainer: Janos Lenart 
-Build-Depends: debhelper (>= 12~), bash-completion, golang-1.15-go, jq, rsync
+Build-Depends: debhelper (>= 12~), bash-completion, golang-1.17-go, jq, rsync
 Standards-Version: 4.5.0
 Homepage: http://kubernetes.io/
 
diff -Nru kubernetes-1.20.5+really1.20.2/debian/rules kubernetes-1.20.5+really1.20.2/debian/rules
--- kubernetes-1.20.5+really1.20.2/debian/rules	2020-10-21 13:29:24.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/rules	2022-02-27 13:55:20.0 +0100
@@ -2,7 +2,7 @@
 
 export DH_VERBOSE = 1
 export GOPATH = $(CURDIR)/.go
-export PATH := /usr/lib/go-1.15/bin:$(PATH)
+export PATH := /usr/lib/go-1.17/bin:$(PATH)
 export CGO_ENABLED = 0
 
 %:
sbuild (Debian sbuild) 0.81.2 (31 January 2021) on fernst.no-ip.org

+==+
| kubernetes 1.20.5+really1.20.2-1.1 (amd64)   Sat, 02 Apr 2022 13:38:32 + |
+

Bug#706518: python3-serial: rfc2217 support broken (cannot even import serial.rfc2217)

[Bastian Germann]

Control: retitle -1 python3-serial: rfc2217 support broken

The original issue was solved upstream with 
https://github.com/pyserial/pyserial/pull/183 in v3.3

Bug#1008834: pyserial: Upstream version 3.5 available

[Bastian Germann]

Source: pyserial
Version: 3.5~b0-1
Severity: wishlist

pyserial 3.5 is available. Please import it to Debian.

Bug#1000980: kubernetes: diff for NMU version 1.20.5+really1.20.2-1.1

[Shengjing Zhu]

Hi

On Sat, Apr 2, 2022 at 9:57 PM Florian Ernst  wrote:
>
> Control: tags 1000980 + patch
> Control: tags 1000980 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for kubernetes (versioned as 1.20.5+really1.20.2-1.1)
> and uploaded it to DELAYED/7. Please feel free to tell me if I should
> delay it longer.
>
> The diff is based on what I previously sent to this bugreport in
> .

Could you upgrade to golang-1.18 too? It would be even better if you
could just use the meta package `golang-go`.

We intend to remove golang-1.17 from the archive soon as well.

-- 
Shengjing Zhu

Bug#1008835: python3-pytest-cov: Please drop obsolete dependency python3-cov-core

[Boyuan Yang]

Package: python3-pytest-cov
Severity: normal
X-Debbugs-CC: feder...@debian.org
Version: 3.0.0-1
Tags: sid  bookworm

Dear Debian python-pytest-cov maintainer,

Reading debian/control, I found that package python3-pytest-cov has a hard
dependency on python3-cov-core. I believe that it is no longer the case, since
current python-pytest-cov source code never mentions cov_core anywhere and
that the README.rst indicates that cov_core is only a leftover from older
versions and needs manual cleanup upon upgrade.

Could you please take a look drop such hard dependency so that we can
eventually remove src:cov-core from Debian archive? I can help to make an
upload if you find it OK.

Thanks!
Boyuan Yang


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

Bug#692917: printer-driver-escpr: color error on armel

[Kurt Roeckx]

On Sat, Apr 02, 2022 at 11:19:26AM +0200, Thorsten Alteholz wrote:
> Hi Kurt and Patrik,
> 
> thanks a lot for your reports. Can you please check whether the problem
> still exists after a few new upstream versions?

Both the printer and the armel server have been replaced in the mean time.


Kurt

Bug#1008836: Broken with Python 3.10

[Jochen Sprickerhof]

Package: weechat-matrix
Version: 0.3.0-3
Severity: important
Tags: patch
X-Debbugs-Cc: jspri...@debian.org

Hi Kyle,

can you please add this patch so weechat-matrix works with Python 3.10:

https://github.com/poljar/weechat-matrix/commit/4e585d5f4628e6fbeba9ec4560b440d731e076f5

(I can do a NMU if you want)

Cheers 

Jochen

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armhf (armv7l)

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

Versions of packages weechat-matrix depends on:
ii  python3-aiohttp   3.8.1-4
ii  python3-atomicwrites  1.4.0-2
ii  python3-future0.18.2-5
ii  python3-logbook   1.5.3-4+b2
ii  python3-magic 2:0.4.25-1
ii  python3-matrix-nio0.19.0-2
ii  python3-openssl   21.0.0-1
ii  python3-pygments  2.11.2+dfsg-2
ii  python3-requests  2.27.1+dfsg-1
ii  python3-webcolors 1.11.1-1

Versions of packages weechat-matrix recommends:
pn  weechat  

weechat-matrix suggests no packages.

-- no debconf information

Bug#1008837: Broken with Python 3.10

[Jochen Sprickerhof]

Package: weechat-matrix
Version: 0.3.0-3
Severity: important
Tags: patch
X-Debbugs-Cc: jspri...@debian.org

Hi Kyle,

can you please add this patch so weechat-matrix works with Python 3.10:

https://github.com/poljar/weechat-matrix/commit/4e585d5f4628e6fbeba9ec4560b440d731e076f5

(I can do a NMU if you want)

Cheers 

Jochen

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armhf (armv7l)

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

Versions of packages weechat-matrix depends on:
ii  python3-aiohttp   3.8.1-4
ii  python3-atomicwrites  1.4.0-2
ii  python3-future0.18.2-5
ii  python3-logbook   1.5.3-4+b2
ii  python3-magic 2:0.4.25-1
ii  python3-matrix-nio0.19.0-2
ii  python3-openssl   21.0.0-1
ii  python3-pygments  2.11.2+dfsg-2
ii  python3-requests  2.27.1+dfsg-1
ii  python3-webcolors 1.11.1-1

Versions of packages weechat-matrix recommends:
pn  weechat  

weechat-matrix suggests no packages.

-- no debconf information

Bug#1008839: RFP: python-scrap-engine -- A 2D ascii game engine for the terminal

[Elena Grandi]

Package: wnpp
Severity: wishlist

* Package name: python-scrap-engine
  Version : 1.2.0
  Upstream Author : lxgr 
* URL : https://github.com/lxgr-linux/scrap_engine
* License : GPLv3
  Programming Lang: Python
  Description : A 2D ascii game engine for the terminal

This is used by Pokete (a terminal based Pokemon like game), for which
I'm opening a different RFP.

I believe that this package could find a good home in either the Python
or the Games team.

Bug#1008841: imagemagick: compare falsely deems two identical images different

[Dennis Filder]

Source: imagemagick
Version: 8:6.9.11.60+dfsg-1.3
Architecture: amd64

Running

  compare-im6.q16hdri wizard: wizard: null:

yields an exit status of 1 ("Images are dissimilar"), but it should be
0 ("Images are similar").  Running

  compare-im6.q16hdri -metric ncc wizard: wizard: null:

prints "0.97", but it should be "1".  Since NCC is the default
metric this renders the compare command broken.  For comparison:

  compare-im6.q16hdri -metric AE wizard: wizard: null:

This correctly prints "0" as you would expect for the AE metric.

The delta image produced is also useless for finding differences since
it merely produces a fainter version of the original image, e.g. by
running

  compare-im6.q16hdri wizard: wizard: /tmp/delta.png

No idea what's going wrong here.

The bug is present in both the q16 and the q16hdri flavors of the
package, thus I file it against the source package.

Bug#1008842: exfat-fuse does not provide exfat filesystem driver

[MichaIng]

Package: exfat-fuse
Version: 1.3.0-2

Since Debian Bullseye (also tested on Bookworm), the exfat-fuse package 
does not provide the (FUSE-based) "exfat" filesystem driver, i.e. the 
following commands fail if the exfat kernel module is not present, e.g. 
when a different kernel is used, often the case with ARM SBCs:

---
mount  
mount  # with related "exfat" entry in /etc/fstab
mount -t exfat  
---

Until Buster, when the exfat filesystem type is detected or passed via 
mount option, the FUSE driver is automatically invoked, since Bullseye 
one needs to pass "exfat-fuse" as filesystem type explicitly, since 
autodetection, as well as blkid and lsblk, still detect "exfat".


While it makes sense, respectively the FUSE driver for exFAT is obsolete 
with a recent Linux version, including the Debian kernel on Bullseye, it 
is not too uncommon that other older kernel versions are used, 
especially on embedded devices, ARM SBCs etc where manufacturers enable 
additional features, not present in upstream Linux yet, respectively not 
present in the Linux version shipped with Debian Bullseye yet. So 
generally it would be nice if "exfat-fuse" did enable mounting exFAT 
drives as "exfat", like it did before. But of course when the native 
exfat kernel module is present, it should be preferred.


The other option would be to have lsblk/blkid/mount detecting the 
filesystem type as "exfat-fuse" instead of as "exfat", when the kernel 
module is not present but "exfat-fuse" installed. But this wouldn't 
cover cases where e.g. a Buster system with older non-Debian kernel and 
explicit "exfat" fstab entry is upgraded to Bullseye.


I hope there is a way to keep exfat-fuse fully backwards compatible.

Related is that the package does not provide mount.exfat anymore, but 
mount.exfat-fuse only. Probably a dpkg-alternative or postinst script 
provided symlink could re-enable backwards compatibility. But an open 
issue remains that "exfatprogs" does not provide mount.exfat either, so 
I guess mounts would then keep invoking FUSE (using mount.exfat => 
mount.exfat-fuse) even if the kernel module + exfatprogs are installed 
as well. A conflict between exfatprogs and exfat-fuse could then help 
solving it, like it exists for exfat-utils.


Best regards,

Micha

Bug#1000980: kubernetes: diff for NMU version 1.20.5+really1.20.2-1.1

[Florian Ernst]

Dear maintainer,

I've prepared an NMU for kubernetes (versioned as 1.20.5+really1.20.2-1.1)
and uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.
(Note: the previous upload as per
 has been
canceled, this one here will replace it.)

The diff is based on what I previously sent to this bugreport in
, but now
updated to use "golang-go" as per Shengjing Zhu's hint in
 (and yes,
we could have saved a roundtrip here ...).

The binary package debdiff just lists
| $ debdiff kubernetes-client_1.20.5+really1.20.2-1_amd64.deb 
kubernetes-client_1.20.5+really1.20.2-1.1_amd64.deb
| File lists identical (after any substitutions)
| 
| Control files: lines which differ (wdiff format)
| 
| Installed-Size: [-40405-] {+37547+}
| Version: [-1.20.5+really1.20.2-1-] {+1.20.5+really1.20.2-1.1+}

I tested the kubectl binary against a local KinD cluster and found no
issues. Basic testing as follows:
| [ ... same (successful) results as before snipped ...]
| $ ./kubectl version
| Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", 
GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"archive", 
BuildDate:"2022-04-02T14:49:13Z", GoVersion:"go1.18", Compiler:"gc", 
Platform:"linux/amd64"}
| Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", 
GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", 
BuildDate:"2021-05-21T23:01:33Z", GoVersion:"go1.16.4", Compiler:"gc", 
Platform:"linux/amd64"}

Please also find attached the local build log.

Best regards,
Flo
diff -Nru kubernetes-1.20.5+really1.20.2/debian/changelog kubernetes-1.20.5+really1.20.2/debian/changelog
--- kubernetes-1.20.5+really1.20.2/debian/changelog	2021-06-13 09:08:18.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/changelog	2022-04-02 16:49:13.0 +0200
@@ -1,3 +1,10 @@
+kubernetes (1.20.5+really1.20.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build using golang-go (Closes: #1000980)
+
+ -- Florian Ernst   Sat, 02 Apr 2022 16:49:13 +0200
+
 kubernetes (1.20.5+really1.20.2-1) unstable; urgency=medium
 
   * This is actually still 1.20.2
diff -Nru kubernetes-1.20.5+really1.20.2/debian/control kubernetes-1.20.5+really1.20.2/debian/control
--- kubernetes-1.20.5+really1.20.2/debian/control	2021-06-13 09:08:18.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/control	2022-04-02 16:49:00.0 +0200
@@ -2,7 +2,7 @@
 Section: admin
 Priority: optional
 Maintainer: Janos Lenart 
-Build-Depends: debhelper (>= 12~), bash-completion, golang-1.15-go, jq, rsync
+Build-Depends: debhelper (>= 12~), bash-completion, golang-go, jq, rsync
 Standards-Version: 4.5.0
 Homepage: http://kubernetes.io/
 
diff -Nru kubernetes-1.20.5+really1.20.2/debian/rules kubernetes-1.20.5+really1.20.2/debian/rules
--- kubernetes-1.20.5+really1.20.2/debian/rules	2020-10-21 13:29:24.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/rules	2022-04-02 16:49:00.0 +0200
@@ -2,7 +2,7 @@
 
 export DH_VERBOSE = 1
 export GOPATH = $(CURDIR)/.go
-export PATH := /usr/lib/go-1.15/bin:$(PATH)
+export PATH := /usr/lib/go/bin:$(PATH)
 export CGO_ENABLED = 0
 
 %:
sbuild (Debian sbuild) 0.81.2 (31 January 2021) on fernst.no-ip.org

+==+
| kubernetes 1.20.5+really1.20.2-1.1 (amd64)   Sat, 02 Apr 2022 14:51:12 + |
+==+

Package: kubernetes
Version: 1.20.5+really1.20.2-1.1
Source Version: 1.20.5+really1.20.2-1.1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-84aad74e-1348-46a6-8c5c-123eb8e424d9'
 with '<>'
I: NOTICE: Log filtering will replace 'build/kubernetes-6AFsTn/resolver-UBQyvV' 
with '<>'

+--+
| Update chroot|
+--+

Get:1 http://127.0.0.1:3142/deb.debian.org/debian unstable InRelease [165 kB]
Get:2 http://127.0.0.1:3142/deb.debian.org/debian unstable/main 
Sources.diff/Index [63.6 kB]
Get:3 http://127.0.0.1:3142/deb.debian.org/debian unstable/main amd64 
Packages.diff/Index [63.6 kB]
Get:4 http://127.0.0.1:3142/deb.debian.org/debian unstable/main Sources 
T-2022-04-02-1404.31-F-2022-04-02-0803.27.pdiff [12.7 kB]
Get:4 http://127.0.0.1:3142/deb.debian.org/debian unstable/main Sources 
T-2022-04-02-1404.31-F-2022-04-02-0803.27.pdiff [12.7 kB]
Get:5 http://127.0.0.1:3142/deb.debian.org/debian unst

Bug#1008817: libphonenumber8: breaks evolution

[tony mancill]

On Sat, Apr 02, 2022 at 07:34:59AM +0200, Christoph Anton Mitterer wrote:
> Package: libphonenumber8
> Version: 8.12.46-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> 
> Hi.
> 
> 8.12.46-1 causes evolution to fail:
> $ evolution
> evolution: symbol lookup error: 
> /usr/lib/x86_64-linux-gnu/libphonenumber.so.8: undefined symbol: 
> _ZN4absl7debian213hash_internal9HashState5kSeedE

Hi Chris,

Thank you for the bug report Chris, for setting the severity so
as to block the migration, and noting the affected packages.

I will work on patching 8.12.46 and also mention this upstream.  The
changelogs for 8.12.45 and 8.12.46 only reference metadata updates.

Thank you,
tony

Bug#1008843: RFP: pokete -- A terminal based Pokemon like game

[Elena Grandi]

Package: wnpp
Severity: wishlist

* Package name: pokete
  Version : 0.6.0
  Upstream Author : lxgr 
* URL : https://github.com/lxgr-linux/pokete
* License : GPLv3
  Programming Lang: Python
  Description : A terminal based Pokemon like game

I believe that this package could find a good home in either the Python
or the Games team.

Packaging this will require packaging also python-scrap-engine, from the
same author (RFP: 1008839).

One issue that I noticed is that upstream instructs to run the game from
a git checkout and there is no pypi package for it, so I suspect that
there may be issues with finding the resources once the game has been
installed.

Bug#1008817: libphonenumber8: breaks evolution

[Christoph Anton Mitterer]

On Sat, 2022-04-02 at 08:14 -0700, tony mancill wrote:
> Thank you for the bug report Chris, for setting the severity so
> as to block the migration, and noting the affected packages.

Actually, the latter two were done by some other helpers :-)


Thanks,
Chris.

Bug#1007970: ITP: cloudflare-ddns -- dynamically update a DNS record using Cloudflare

[Stephan Lachnit]

Hi Andrea,

uploaded :)

Cheers,
Stephan

On Sat, Apr 2, 2022 at 2:57 PM Andrea Pappacoda  wrote:
>
> Hi Stephan, I've reuploaded my package to Mentors, following Thorsten
> Alteholz's advice about the rejection; all the files should now have a
> proper entry in d/copyright.
>
> You can find it here:
> https://mentors.debian.net/package/cloudflare-ddns/
>
> Thanks again :)
>
> --
> OpenPGP key: 66DE F152 8299 0C21 99EF  A801 A8A1 28A8 AB1C EE49
>
>

Bug#1008845: cryfs: /usr/bin/cryfs-unmount is missing in 0.11.2-4

[Thomas R. Shemanske]

Package: cryfs
Version: 0.11.2-4
Severity: important
X-Debbugs-Cc: thomas.r.sheman...@dartmouth.edu

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 ***

cryfs 0.11.2-4 ships without /usr/bin/cryfs-unmount



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

Kernel: Linux 5.16.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.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 cryfs depends on:
ii  fuse3 [fuse]3.10.5-1
ii  libboost-chrono1.74.0   1.74.0-14
ii  libboost-filesystem1.74.0   1.74.0-14
ii  libboost-program-options1.74.0  1.74.0-14
ii  libboost-thread1.74.0   1.74.0-14
ii  libc6   2.33-7
ii  libcurl47.82.0-2
ii  libfmt8 8.1.1+ds1-2
ii  libfuse22.9.9-5
ii  libgcc-s1   12-20220319-1
ii  libgomp112-20220319-1
ii  libspdlog1 [libspdlog1-fmt8]1:1.9.2+ds-0.2
ii  libstdc++6  12-20220319-1

cryfs recommends no packages.

cryfs suggests no packages.

-- no debconf information

Bug#1008844: gitsome gh fails to run with python3.10

[Anthony Fok]

Package: gitsome
Version: 0.8.0+ds-6
Severity: important
Tags: patch upstream
X-Debbugs-Cc: f...@debian.org

/usr/bin/gh provided by gitsome (as of 0.8.0+ds-6) fails to run with python3.10
which has become the default Python 3 in Debian sid:


$ gh
Traceback (most recent call last):
  File "/usr/bin/gh", line 34, in 
sys.exit(load_entry_point('gitsome==0.8.0', 'console_scripts', 'gh')())
  File "/usr/bin/gh", line 26, in importlib_load_entry_point
return next(matches).load()
  File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 171, in load
module = import_module(match.group('module'))
  File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1050, in _gcd_import
  File "", line 1027, in _find_and_load
  File "", line 1006, in _find_and_load_unlocked
  File "", line 688, in _load_unlocked
  File "", line 883, in exec_module
  File "", line 241, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/gitsome/main_cli.py", line 20, in 

from .githubcli import GitHubCli
  File "/usr/lib/python3/dist-packages/gitsome/githubcli.py", line 21, in 

from .github import GitHub
  File "/usr/lib/python3/dist-packages/gitsome/github.py", line 25, in 
from .lib.github3 import null
  File "/usr/lib/python3/dist-packages/gitsome/lib/github3/__init__.py", line 
18, in 
from .api import (
  File "/usr/lib/python3/dist-packages/gitsome/lib/github3/api.py", line 11, in 

from .github import GitHub, GitHubEnterprise
  File "/usr/lib/python3/dist-packages/gitsome/lib/github3/github.py", line 13, 
in 
from .auths import Authorization
  File "/usr/lib/python3/dist-packages/gitsome/lib/github3/auths.py", line 12, 
in 
from .models import GitHubCore
  File "/usr/lib/python3/dist-packages/gitsome/lib/github3/models.py", line 19, 
in 
from .session import GitHubSession
  File "/usr/lib/python3/dist-packages/gitsome/lib/github3/session.py", line 4, 
in 
from collections import Callable
ImportError: cannot import name 'Callable' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)


This bug was reported to and fixed in Ubuntu on 2022-01-28
by Alexandre Ghiti ;
see https://bugs.launchpad.net/ubuntu/+source/gitsome/+bug/1959377

You may consider downloading his patch from
https://bugs.launchpad.net/ubuntu/+source/gitsome/+bug/1959377/+attachment/5557913/+files/debdiff_python3.10.patch

The whole Ubuntu patch with other unrelated changes is available at
https://patches.ubuntu.com/g/gitsome/gitsome_0.8.0+ds-6ubuntu1.patch

Alexandre Ghiti has also forwarded his patch upstream as PR #191:
https://github.com/donnemartin/gitsome/pull/191

Add support for python 3.10" at

Use 'collections.abc' instead of 'collections' since python 3.10 does not 
accept
this syntax anymore, it has been deprecated since python 3.3.

Cheers,

Anthony

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

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

Versions of packages gitsome depends on:
ii  python3   3.10.4-1
ii  python3-click 8.0.3-1
ii  python3-colorama  0.4.4-1
ii  python3-docopt0.6.2-4
ii  python3-feedparser6.0.8-1
ii  python3-numpydoc  1.2.1-1
ii  python3-ply   3.11-5
ii  python3-prompt-toolkit3.0.28-1
ii  python3-pygments  2.11.2+dfsg-2
ii  python3-requests  2.27.1+dfsg-1
ii  python3-sigmavirus24-urltemplate  4.1.1-1
ii  python3-tz2022.1-1
ii  xonsh 0.11.0+dfsg-1

gitsome recommends no packages.

gitsome suggests no packages.

-- no debconf information
diff -Nru gitsome-0.8.0+ds/debian/changelog gitsome-0.8.0+ds/debian/changelog
--- gitsome-0.8.0+ds/debian/changelog   2021-11-06 17:24:54.0 +0100
+++ gitsome-0.8.0+ds/debian/changelog   2022-01-28 10:43:07.0 +0100
@@ -1,3 +1,10 @@
+gitsome (0.8.0+ds-6ubuntu1) jammy; urgency=medium
+
+  * d/patches:
+- Add support for python3.10
+
+ -- Alexandre Ghiti   Fri, 28 Jan 2022 10:43:07 
+0100
+
 gitsome (0.8.0+ds-6) unstable; urgency=medium
 
   * Fix FTBFS issue (Closes: #997316)
diff -Nru gitsome-0.8.0+ds/debian/patches/python3.10-support.patch 
gitsome-0.8.0+ds/debian/patches/python3.10-support.patch
--- gitsome-

Bug#1008846: motion aborts with stack smashing detected

[Pelzi]

Package: motion
Version: 4.3.2-1 armhf

Dear maintainer,

Motion does not start anymore after an update, it aborts with a stack smashing 
message:


$ sudo -u motion motion
*** stack smashing detected ***: terminated
Abgebrochen



Generating a core and analysing the stack trace with gdb yields:

Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Core was generated by `motion'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht 
gefunden.
(gdb) where
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x7522f804 in __GI_abort () at abort.c:79
#2  0x75281af4 in __libc_message (action=action@entry=do_abort, fmt=) at ../sysdeps/posix/libc_fatal.c:155
#3  0x75303f10 in __GI___fortify_fail (msg=0x7534f358 "stack smashing 
detected") at fortify_fail.c:26
#4  0x75303eec in __stack_chk_fail () at stack_chk_fail.c:24
#5  0x75bf99e0 in msmpeg4v2_encode_motion (s=0x74c41e6c, val=) 
at src/libavcodec/msmpeg4enc.c:374
#6  0x in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)


The behaviour is reproducible, it happens at any startup.

Package version and dependency:
$ dpkg-query --show -f '${Package} ${Version} ${Depends}\n' motion libavcodec58
libavcodec58 7:4.3.3-0+rpt3+deb11u1 libaom0 (>= 1.0.0), libavutil56 (= 
7:4.3.3-0+rpt3+deb11u1), libc6 (>= 2.29), libcairo2 (>= 1.2.4), libcodec2-0.9 
(>= 0.9.2), libdav1d4 (>= 0.2.1), libglib2.0-0 (>= 2.12.0), libgsm1 (>= 
1.0.18), liblzma5 (>= 5.1.1alpha+20120614), libmp3lame0 (>= 3.100), 
libopenjp2-7 (>= 2.0.0), libopus0 (>= 1.1), libraspberrypi0, librsvg2-2 (>= 
2.14.4), libshine3 (>= 3.1.0), libsnappy1v5 (>= 1.1.8), libspeex1 (>= 
1.2~beta3-1), libswresample3 (= 7:4.3.3-0+rpt3+deb11u1), libtheora0 (>= 1.0), 
libtwolame0 (>= 0.3.10), libudev1 (>= 183), libva2 (>= 2.2.0), libvorbis0a (>= 
1.1.2), libvorbisenc2 (>= 1.1.2), libvpx6 (>= 1.6.0), libwavpack1 (>= 4.40.0), 
libwebp6 (>= 0.5.1), libwebpmux3 (>= 0.6.1-2.1), libx264-160 (>= 
2:0.160.3011+gitcde9a93), libx265-192 (>= 3.2), libxvidcore4 (>= 1.2.2), 
libzvbi0 (>= 0.2.35), zlib1g (>= 1:1.2.0)
motion 4.3.2-1 libavcodec58 (>= 7:4.2), libavdevice58 (>= 7:4.0), libavformat58 
(>= 7:4.2), libavutil56 (>= 7:4.0), libc6 (>= 2.28), libjpeg62-turbo (>= 
1.3.1), libmariadb3 (>= 3.0.0), libmicrohttpd12 (>= 0.9.50), libpq5, 
libsqlite3-0 (>= 3.6.0), libswscale5 (>= 7:4.0), debconf (>= 0.5) | 
debconf-2.0, lsb-base (>= 3.0-6), adduser

Bug#1008840: linphone: Recording does not work due to lack of mkv support

[Dennis Filder]

X-Debbugs-CC: Rainer Dorsch 

On Sat, Apr 02, 2022 at 04:23:34PM +0200, Rainer Dorsch wrote:

> as a side note, even though reportbug reports that there is a newer
> version of linphone (4.4.21-2) for stable, I cannot install it. apt
> does not find it, rmadison has even two entries:
>
> rd@h370:~$ apt-cache policy linphone
> linphone:
>   Installiert:   4.2.5-3
>   Installationskandidat: 4.2.5-3
>   Versionstabelle:
>  *** 4.2.5-3 500
> 500 http://ftp-stud.hs-esslingen.de/debian bullseye/main amd64 
> Packages
> 500 http://ftp-stud.hs-esslingen.de/debian bullseye/main i386 Packages
> 100 http://deb.debian.org/debian sid/main amd64 Packages
> 100 http://deb.debian.org/debian sid/main i386 Packages
> 105 http://deb.debian.org/debian bookworm/main amd64 Packages
> 105 http://deb.debian.org/debian bookworm/main i386 Packages
> 100 /var/lib/dpkg/status
> rd@h370:~$ rmadison linphone
> linphone   | 3.6.1-2.4 | oldoldoldstable | source
> linphone   | 3.6.1-2.4+b1  | oldoldoldstable | amd64, armel, armhf, i386
> linphone   | 3.6.1-3   | oldoldstable| source, amd64, arm64, armel, 
> armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> linphone   | 3.12.0-3  | oldstable   | source, amd64, arm64, armel, 
> armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> linphone   | 4.2.5-3   | stable  | all
> linphone   | 4.2.5-3   | testing | all
> linphone   | 4.2.5-3   | unstable| all
> linphone   | 4.4.21-2  | stable  | source
> linphone   | 4.4.21-2  | testing | source
> linphone   | 4.4.21-2  | unstable| source
> linphone   | 4.4.21-2  | unstable-debug  | source

This is most likely due to a package renaming.  Can you try running?:

  rmadison -S linphone

The CLI version is now in "linphone-cli" and the Qt version (which was
formerly in "linphone") is now in "linphone-desktop".  "linphone" from
now on only exists as a source package name.  But the 4.2.5-3
"linphone" transitional package should still show up under bullseye.
The versioning is confusing because the desktop app and the core
libraries (of which the CLI version is a component) are not versioned
according to the same scheme.

> which suggests that linphone was built w/o mkv support.
>
> Can you confirm that?

Yes.  Version 4.3.2 of linphone-desktop and its dependencies have been
packaged already in Salsa, are waiting for an upload and are planned
to ship with Matroska support.

> Previously the recording were in wav format. Is it possible to
> switch back to wav, if mkv is troublesome?

You can try to record in WAV by supplying a file name that ends in
".wav".  If that does not work then I don't know what can be done
besides waiting.

Regards.

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

[Diederik de Haas]

On Saturday, 2 April 2022 15:36:53 CEST Francesco C wrote:
> Vanilla kernel 5.16.18 built with custom .config for the specific
> machine fails to boot at the same point too.

As you appear to be familiar with kernel building, could you look at the 
patches that Damien Le Moal posted in this bug report?

> I'm also trying to track stable patches in the stable tree queue
> (https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/log
> /) but it seems to me at the moment there not any patch about ata_pxii in
> the 5.16.x branch and in the 5.17.x either.

AFAICT, we're still at the stage of identifying the problem, so I don't expect 
anything in the stable-queue until we're past that stage.

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

Bug#1008817: libphonenumber8: breaks evolution

[Neil Mayhew]

On 2022-04-02 09:14, tony mancill wrote:
I will work on patching 8.12.46 and also mention this upstream. The 
changelogs for 8.12.45 and 8.12.46 only reference metadata updates.


If there was a non-metadata change that wasn't mentioned in the 
changelog, it will be the second time this has happened in a fairly 
short period. The other one was 
https://github.com/google/libphonenumber/pull/2698 which was merged on 
Jan 7.

Bug#999659: perdition: diff for NMU version 2.2-3.2

[Marcos Talau]

Control: tags 999659 + patch
Control: tags 999659 + pending

Dear maintainer,

I've prepared an NMU for perdition (versioned as 2.2-3.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru perdition-2.2/debian/changelog perdition-2.2/debian/changelog
--- perdition-2.2/debian/changelog	2019-08-02 08:11:02.0 -0300
+++ perdition-2.2/debian/changelog	2022-03-31 22:39:14.0 -0300
@@ -1,3 +1,22 @@
+perdition (2.2-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add exit code true after invoke-rc.d in the files below (Closes: #999659).
+Thanks to Sergey Spiridonov.
+- perdition-ldap.postinst
+- perdition-ldap.prerm
+- perdition-mysql.postinst
+- perdition-mysql.prerm
+- perdition-odbc.postinst
+- perdition-odbc.prerm
+- perdition-postgresql.postinst
+- perdition-postgresql.prerm
+- perdition.postinst
+- perdition.preinst
+- perdition.prerm
+
+ -- Marcos Talau   Thu, 31 Mar 2022 22:39:14 -0300
+
 perdition (2.2-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru perdition-2.2/debian/perdition-ldap.postinst perdition-2.2/debian/perdition-ldap.postinst
--- perdition-2.2/debian/perdition-ldap.postinst	2016-11-28 07:58:24.0 -0200
+++ perdition-2.2/debian/perdition-ldap.postinst	2022-03-31 21:37:32.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "configure" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-ldap.prerm perdition-2.2/debian/perdition-ldap.prerm
--- perdition-2.2/debian/perdition-ldap.prerm	2014-09-11 00:40:14.0 -0300
+++ perdition-2.2/debian/perdition-ldap.prerm	2022-03-31 21:39:51.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "purge"  -o "$1" = "remove" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-mysql.postinst perdition-2.2/debian/perdition-mysql.postinst
--- perdition-2.2/debian/perdition-mysql.postinst	2016-11-28 07:58:24.0 -0200
+++ perdition-2.2/debian/perdition-mysql.postinst	2022-03-31 21:40:01.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "configure" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-mysql.prerm perdition-2.2/debian/perdition-mysql.prerm
--- perdition-2.2/debian/perdition-mysql.prerm	2014-09-11 00:40:14.0 -0300
+++ perdition-2.2/debian/perdition-mysql.prerm	2022-03-31 21:40:12.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "purge"  -o "$1" = "remove" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-odbc.postinst perdition-2.2/debian/perdition-odbc.postinst
--- perdition-2.2/debian/perdition-odbc.postinst	2016-11-28 07:58:24.0 -0200
+++ perdition-2.2/debian/perdition-odbc.postinst	2022-03-31 21:40:22.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "configure" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-odbc.prerm perdition-2.2/debian/perdition-odbc.prerm
--- perdition-2.2/debian/perdition-odbc.prerm	2014-09-11 00:40:14.0 -0300
+++ perdition-2.2/debian/perdition-odbc.prerm	2022-03-31 21:40:57.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "purge"  -o "$1" = "remove" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-postgresql.postinst perdition-2.2/debian/perdition-postgresql.postinst
--- perdition-2.2/debian/perdition-postgresql.postinst	2016-11-28 07:58:24.0 -0200
+++ perdition-2.2/debian/perdition-postgresql.postinst	2022-03-31 21:41:09.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "configure" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-postgresql.prerm perdition-2.2/debian/perdition-postgresql.prerm
--- perdition-2.2/debian/perdition-postgresql.prerm	2014-09-11 00:40:14.0 -0300
+++ perdition-2.2/debian/perdition-postgresql.prerm	2022-03-31 21:41:20.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$

Bug#821926: Group upload of geolocation enable fgallery (Was: Please support geolocation)

[Andreas Tille]

Hi Daniel,

I've seen that you updated the packaging of fgallery in Git.  I'd like
to join you as Uploader of this package and would love to inject my
patch for geolocation.  I'm using my patch since six years now
successfully.  It seems upstream is dead and so I think if we want
to provide this functionality to our users we are on our own.  I'm
happily support this patch since I use it in all my galleries.

What do you think?

Kind regards

  Andreas.


-- 
http://fam-tille.de

Bug#1008817: libphonenumber8: breaks evolution

[Adrian Bunk]

On Sat, Apr 02, 2022 at 10:39:13AM -0600, Neil Mayhew wrote:
> On 2022-04-02 09:14, tony mancill wrote:
> > I will work on patching 8.12.46 and also mention this upstream. The
> > changelogs for 8.12.45 and 8.12.46 only reference metadata updates.
> 
> If there was a non-metadata change that wasn't mentioned in the changelog,
> it will be the second time this has happened in a fairly short period. The
> other one was https://github.com/google/libphonenumber/pull/2698 which was
> merged on Jan 7.

The problem is 
https://github.com/google/libphonenumber/commit/5719f3a724d254b21196393d952b71ec3052e6a3

I have an approximate fix I can polish later this evening,
unless Tony already has something similar.

cu
Adrian

Bug#1008842: exfat-fuse does not provide exfat filesystem driver

[MichaIng]

I would also love to be able to ship recent Linux versions in all cases, 
but as of sadly common practice of many SoC and SBC manufacturers, to 
not produce open source hardware/firmware/drivers, and to provide own 
outdated kernel versions with driver and firmware blobs instead of 
contributing those upstream in the first place, often SBCs are not 
(fully) functional with upstream and Debian Linux versions.


However, I fully understand the decision to not put efforts in 
"supporting" this manufacturer behaviour.


Interesting is, that I now successfully solved it by creating the 
/sbin/mount.exfat => mount.exfat-fuse symlink. I though I tested this 
already, without success. That seems sufficiently simple. When the 
kernel modules becomes available later and exfat-fuse it purged, even 
leaving the symlink pointing to nowhere in place does not break mounting 
exfat filesystems with the native Linux driver, so it is quite save to 
create it, when stuck with an old Linux version:


---
ln -s mount.exfat-fuse /sbin/mount.exfat
---

Best regards,

Micha

Bug#1005912: hydrogen: autopkgtest regression on arm64 and ppc64el: H2Core::Instrument::dequeue(): Assertion `__queued > 0' failed.

[Paul Gevers]

Hi Nicholas

On 02-04-2022 00:13, Nicholas D Steeves wrote:

On 24-02-2022 06:13, Nicholas D Steeves wrote:

Paul and Debian CI team, do you know if a dummy alsa driver (and dummy
sequencer driver) can be enabled on DebCI systems?


You are in control of your testbed, can't you do this in your test? Or
can you only do this in isolation-machine testbeds (not sure how this
driver thing works)?


I was thinking that this would require a `modprobe snd-dummy`, and I'm
assuming loading arbitrary kernel modules is blocked on DebCI systems.


We don't "block" anything. But on ci.d.n things need to work in lxc for 
now. Again, I'm not into the details, but I think indeed that you need 
isolation-machine for that.



It's been a few months since I contacted the CI Team about
isolation-machines, but they're not yet ready for use either.


That's still correct, and I don't expect that to change in the short 
term. We're more focused on adding other architectures to enable the 
Release Team to test all release architectures and maintaining the 
infrastructure as-is. That's already more work that I'd expected upfront.



My request for snd-dummy on DebCI isn't arm64 specific; I noticed that
jackd2 doesn't have autopkgtest enabled, and hypothesised that missing
audio hardware was the reason why.  Jackd2 maintainers are now in CC
because would know better than I :-)


I see a lot of flaky tests with jack mentioned in the error (failure to 
start or something). Maybe that's remotely related?



To be honest, I don't really like tweaking the hosts, as other
autopkgtest instances outside our control would need to learn to do this
too.



I completely understand, and the only way this request would be
justifiable is if it provided a meaningful boost in quality assurance
for audio-related packages.


I'm wondering if this warrants a new autopkgtest restrictions (probably 
not): isolation-machine-or-needs-${group-of-defined-kernel-modules}. I 
have the feeling that could become a big list for all kind of use cases.



When I run autopkgtests locally they now error due to missing audio
hardware where previously they passed, and this wasn't the case when the
package was uploaded.


The test on ppc64el now passed after several failure due to segmentation
faults. Not sure if this is now a highly flaky test, or just that the
issue has been fixed in the mean time on ppc64el



When I contacted upstream, I learned that the cause may be that the CLI
utilities are poorly maintained.  Is this sufficient justification for
disabling the autopkgtests ie: that it's due diligence and not laziness?


Well, if a test is truly flaky for whatever reason, ci.d.n and the 
Release Team agree that the test should either not be run or marked as 
flaky. The latter only has value if some human still regularly checks. 
The same goes for failure on a particular architecture. If you believe 
the failure is due to CI and not because the package itself is wrong, 
then just don't test there (Architecture field in d/t/control). If the 
package is broken and can't reasonably be fixed, have it removed from 
that architecture (in unstable; ftp.debian.org pseudo package) and don't 
build on that architecture anymore. In that case CI found out that the 
package is broken and that's a good thing.



Thank you again for having this conversation.  I want to support our CI
team and technical excellence rather than just "unblock migration to
testing", but will of course defer to your recommendations.


Sometimes you need to (for the time being) take a practical stance. I'm 
not saying yet that we'll not enable the snd-dummy module (I hope for 
follow-up), but in the present case, if the test can't reliably run on 
the present infrastructure, and nobody is promising a solution on the 
short term, you should not make your own live too hard and you should 
not run the tests for now. Or prepare for the isolation-machine 
situation (I think Ubuntu has that on most architectures) and hope it 
will arrive someday in Debian too.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008817: libphonenumber8: breaks evolution

[tony mancill]

On Sat, Apr 02, 2022 at 08:11:39PM +0300, Adrian Bunk wrote:
> On Sat, Apr 02, 2022 at 10:39:13AM -0600, Neil Mayhew wrote:
> > On 2022-04-02 09:14, tony mancill wrote:
> > > I will work on patching 8.12.46 and also mention this upstream. The
> > > changelogs for 8.12.45 and 8.12.46 only reference metadata updates.
> > 
> > If there was a non-metadata change that wasn't mentioned in the changelog,
> > it will be the second time this has happened in a fairly short period. The
> > other one was https://github.com/google/libphonenumber/pull/2698 which was
> > merged on Jan 7.
> 
> The problem is 
> https://github.com/google/libphonenumber/commit/5719f3a724d254b21196393d952b71ec3052e6a3
> 
> I have an approximate fix I can polish later this evening,
> unless Tony already has something similar.

Hi Adrian,

Thank you for the pointer.  I started picking through the delta between
8.12.44 and 8.12.46 and it appears that libphonenumber needs to ensure
that absl/hash/internal/hash.cc is linked.  I won't have a chance to
work on patch until later in my day (GMT-7) and so would be glad to
receive yours.  Otherwise, I will work on it tonight.

I will do a full reverse build-deps (ratt) build before uploading.

Cheers,
tony

Bug#821926: Group upload of geolocation enable fgallery (Was: Please support geolocation)

[Guus Sliepen]

On Sat, Apr 02, 2022 at 07:00:15PM +0200, Andreas Tille wrote:

> I've seen that you updated the packaging of fgallery in Git.  I'd like
> to join you as Uploader of this package and would love to inject my
> patch for geolocation.  I'm using my patch since six years now
> successfully.  It seems upstream is dead and so I think if we want
> to provide this functionality to our users we are on our own.  I'm
> happily support this patch since I use it in all my galleries.

As a bystander, I would say: great idea! Maybe even better would be to
check with the original upstream to see if you can take over? That way
not just Debian will benefit from your geolocation patch.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: PGP signature

Bug#1008620: hplip: Please make hplip compatible with Python 3.10 transition

[Thorsten Alteholz]

Hi Eric,

On 29.03.22 18:36, Eric Valette wrote:

Hplip is not mentionned in the python 3.10-add transition but is still not 
installable with
python3.10 default.


I seem to have missed something here. What did you mean by this bug report?

  Thorsten

Bug#1008847: rust-atk-sys

[Samuel Thibault]

Source: rust-atk-sys
Version: 0.7.0-1
Severity: serious
Tags: upstream patch
Justification: Prevents atk1.0 migration
Control: fixed-upstream -1

Hello,

rust-atk-sys was hardcoding the value of ATK_STATE_LAST_DEFINED,
and thus its autopkgtest fails with the newer atk1.0 package
version 2.38, which introduces ATK_STATE_COLLAPSED thus bumping
ATK_STATE_LAST_DEFINED.  Upstream actually stopped hardcoding the value
in 22f00076493c040b5b20d434bd0348d047027f61 

Until that newer upstream version gets packaged, could you please apply
the attached patch to update ATK_STATE_LAST_DEFINED so atk1.0 version
2.38 can migrate to testing?

Samuel

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

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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -255,7 +255,8 @@ pub const ATK_STATE_CHECKABLE: AtkStateT
 pub const ATK_STATE_HAS_POPUP: AtkStateType = 40;
 pub const ATK_STATE_HAS_TOOLTIP: AtkStateType = 41;
 pub const ATK_STATE_READ_ONLY: AtkStateType = 42;
-pub const ATK_STATE_LAST_DEFINED: AtkStateType = 43;
+pub const ATK_STATE_COLLAPSED: AtkStateType = 43;
+pub const ATK_STATE_LAST_DEFINED: AtkStateType = 44;
 
 pub type AtkTextAttribute = c_int;
 pub const ATK_TEXT_ATTR_INVALID: AtkTextAttribute = 0;
--- a/tests/abi.rs
+++ b/tests/abi.rs
@@ -829,6 +829,7 @@ const RUST_CONSTANTS: &[(&str, &str)] =
 ("(gint) ATK_STATE_BUSY", "3"),
 ("(gint) ATK_STATE_CHECKABLE", "39"),
 ("(gint) ATK_STATE_CHECKED", "4"),
+("(gint) ATK_STATE_COLLAPSED", "43"),
 ("(gint) ATK_STATE_DEFAULT", "36"),
 ("(gint) ATK_STATE_DEFUNCT", "5"),
 ("(gint) ATK_STATE_EDITABLE", "6"),
@@ -844,7 +845,7 @@ const RUST_CONSTANTS: &[(&str, &str)] =
 ("(gint) ATK_STATE_INDETERMINATE", "30"),
 ("(gint) ATK_STATE_INVALID", "0"),
 ("(gint) ATK_STATE_INVALID_ENTRY", "33"),
-("(gint) ATK_STATE_LAST_DEFINED", "43"),
+("(gint) ATK_STATE_LAST_DEFINED", "44"),
 ("(gint) ATK_STATE_MANAGES_DESCENDANTS", "29"),
 ("(gint) ATK_STATE_MODAL", "14"),
 ("(gint) ATK_STATE_MULTISELECTABLE", "16"),
--- a/tests/constant.c
+++ b/tests/constant.c
@@ -203,6 +203,7 @@ int main() {
 PRINT_CONSTANT((gint) ATK_STATE_BUSY);
 PRINT_CONSTANT((gint) ATK_STATE_CHECKABLE);
 PRINT_CONSTANT((gint) ATK_STATE_CHECKED);
+PRINT_CONSTANT((gint) ATK_STATE_COLLAPSED);
 PRINT_CONSTANT((gint) ATK_STATE_DEFAULT);
 PRINT_CONSTANT((gint) ATK_STATE_DEFUNCT);
 PRINT_CONSTANT((gint) ATK_STATE_EDITABLE);

Bug#1008620: hplip: Please make hplip compatible with Python 3.10 transition

[Éric Valette]

That à rebuild was missing to remove the python 3.9 dependency. But this has 
been donne it the meantime.

2 avr. 2022 19:50:08 Thorsten Alteholz :

> Hi Eric,
> 
> On 29.03.22 18:36, Eric Valette wrote:
>> Hplip is not mentionned in the python 3.10-add transition but is still not 
>> installable with
>> python3.10 default.
> 
> I seem to have missed something here. What did you mean by this bug report?
> 
>   Thorsten

Bug#1008848: viking: dependency on yelp should be Recommends

[Denis Danilov]

Package: viking
Version: 1.10-2
Severity: minor

Dear Maintainer,

the yelp dependency should go to Recommends instead of Depends, like for example
gnome applications do: gedit, gnome-terminal etc.
Recommended packages are installed in default setup anyway. But then other uses
with tweaked apt settings will be able to avoid installing yelp without
stumbling over viking.

Best regards,
Denis

Bug#907174: New version available

[Andrew Ayer]

Hi Flo,

On Thu, 31 Mar 2022 17:42:37 +0200
Florian Ernst  wrote:
> [...]
> On Wed, Mar 30, 2022 at 07:47:52PM -0400, Andrew Ayer wrote:
> > [...]
> > I am thinking of putting libndp up for adoption - might you be
> > willing to take over?
> 
> Well, I am willing to help, and if that means I take over that'd be
> fine with me, thanks for considering. No need to file an RFA in that
> case, I could just refer to this bugreport here if you approve.

I approve.  Thanks again!

Andrew

Bug#1008801: gnucash: FTBFS on armel

[Adrian Bunk]

Control: retitle -1 gnucash: FTBFS on armhf when built on 64bit hardware
Control: found -1 1:4.4-1

On Fri, Apr 01, 2022 at 08:53:42PM +0200, Sebastian Ramacher wrote:
> Source: gnucash
> Version: 1:4.10-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
>...
> The following tests FAILED:
>57 - test-gnc-timezone (Bus error)
>58 - test-gnc-datetime (Bus error)
>...

It is an old existing alignment issue on 64bit hardware:
https://buildd.debian.org/status/logs.php?pkg=gnucash&arch=armhf

I've written more information in the upstream bug.

> Cheers

cu
Adrian

Bug#1008849: Needs tighter dependency on python3

[Yuri D'Elia]

Package: libshiboken2-py3-5.15
Version: 5.15.2-2+b2
Severity: important

shiboken2 depends on a sepecific major+minor version of python.

/usr/lib/x86_64-linux-gnu/cmake/Shiboken2-5.15.2/shiboken_helpers.cmake
checks for this.

As a result, attempting to build any package cmake package using
shiboken2 currently fails:

-- Found PythonInterp: /usr/bin/python3.10 (found suitable version "3.10.4", 
minimum required is "3")
CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/Shiboken2-5.15.2/shiboken_helpers.cmake:468 
(message):
  The detected Python minor version is not compatible with the Python minor
  version which was used when Shiboken was built.  Consider building shiboken
  with FORCE_LIMITED_API set to '1', so that only the Python major version
  matters.

  Built with: '3.9' Detected: '3.10'

due to python3 now defaulting to python3.10.

One can set PYTHON_EXECUTABLE to the proper version, but that implies
that libshiboken2-py3-5.15 should depend on a specific python3 version,
not just on any minor version.

This also requires that shiboken2 should be currently rebuilt.

Either the python3 dependency should be tightened, or FORCE_LIMITED_API
should be used.

Bug#1008850: tulip: FTBFS on s390x

[Sebastian Ramacher]

Source: tulip
Version: 5.4.0+dfsg-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

tulip FTBFS on s390x:


/<>/thirdparty/OGDF/include/coin/CoinHelperFunctions.hpp:707:66: 
warning: ISO C++17 does not allow ‘register’ storage class specifier 
[-Wregister]
  707 | CoinDeleteEntriesFromArray(register T * arrayFirst, register T * 
arrayLast,
  |  
^
/<>/thirdparty/OGDF/src/coin/CoinUtils/CoinMessageHandler.cpp: In 
member function ‘CoinMessageHandler& CoinMessageHandler::operator<<(double)’:
/<>/thirdparty/OGDF/src/coin/CoinUtils/CoinMessageHandler.cpp:764:20:
 error: format not a string literal and no format arguments 
[-Werror=format-security]
  764 | sprintf(messageOut_,format_+2);
  | ~~~^~~
In file included from 
/<>/thirdparty/OGDF/src/coin/CoinUtils/CoinMessageHandler.cpp:7:


See
https://buildd.debian.org/status/fetch.php?pkg=tulip&arch=s390x&ver=5.4.0%2Bdfsg-3%2Bb2&stamp=1648507220&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1008851: Compress kicad 3D models to reduce installed size

[Carsten Andrich]

Package: kicad-packages3d
Version: 6.0.4-1|Severity: wishlist |

|KiCad supports compressed 3D models since version 6 [1, 2, 3]. 
Compressing the .step and .wrl files contained in the current 
kicad-packages3d package reduces its installed size from ||5468M to 923M 
(measured with du on a tmpfs).
Unfortunately, simply compressing and renaming the files to .stpz [2] or 
.wrz [3], respectively, is insufficient, because 3D models are referred 
to by name in the footprint files [4]. Therefore, AFAIK, every single 
upstream footprint file would have to be modified accordingly to 
implement 3D model compression.

|

||

|[1] https://gitlab.com/kicad/code/kicad/-/issues/5360 [2] 
https://gitlab.com/kicad/code/kicad/-/blob/6.0/plugins/3d/oce/loadmodel.cpp#L286 
[3] 
https://gitlab.com/kicad/code/kicad/-/blob/6.0/plugins/3d/vrml/vrml.cpp#L177 
[4] 
https://gitlab.com/kicad/libraries/kicad-footprints/-/blob/6.0.4/Connector_PinSocket_2.54mm.pretty/PinSocket_1x02_P2.54mm_Vertical.kicad_mod#L36 
|

Bug#1008785: ITP: fonts-creep -- Pretty sweet 4px wide pixel font

[Roland Clobus]

Hello Agata,

On 01/04/2022 17:25, Agathe Porte wrote:
...
I already packaged fonts-creep first, then fonts-creep2, but I do not 
know how to resolve #1006953 .


I remembered that bitmap fonts were disabled some time ago in Pango 
(#939748).


See the last entry of
https://forums.debian.net/viewtopic.php?t=136305
for a possible solution.

With kind regards,
Roland


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008840: linphone: Recording does not work due to lack of mkv support

[Dennis Filder]

X-Debbugs-CC: Rainer Dorsch 

On Sat, Apr 02, 2022 at 08:27:19PM +0200, Rainer Dorsch wrote:
> HmmI just configured the path for in Settings->User Interface. Can you 
> tell
> where I can configure the file name?

I just looked at the code and the ".mkv" suffix is hard-coded in the
Qt version, so currently there is no way to record in WAV despite
Mediastreamer2 supporting it.  The command line version ("linphonec")
still supports it with the "record" command.  I'll add this to the
list of things to bring up once I get around to discussing bugs with
the upstream developers.

A work-around can be to record straight from the Pulseaudio monitor of
an on-going call (oggenc is part of vorbis-tools):

  pacmd list-sink-inputs # the index for Linphone was 58
  parec --monitor-stream=58 | oggenc -o /tmp/linphone.ogg --raw -

The volume may need to be cranked up quite high.  Working with
Pulseaudio like this can also get somewhat finicky.

Regards

Bug#1008851: Compress kicad 3D models to reduce installed size

[Carsten Andrich]

Version: 6.0.4-1
Severity: wishlist

Bug#821926: Group upload of geolocation enable fgallery (Was: Please support geolocation)

[Andreas Tille]

Hi Guus,

Am Sat, Apr 02, 2022 at 07:39:25PM +0200 schrieb Guus Sliepen:
> On Sat, Apr 02, 2022 at 07:00:15PM +0200, Andreas Tille wrote:
> 
> > I've seen that you updated the packaging of fgallery in Git.  I'd like
> > to join you as Uploader of this package and would love to inject my
> > patch for geolocation.  I'm using my patch since six years now
> > successfully.  It seems upstream is dead and so I think if we want
> > to provide this functionality to our users we are on our own.  I'm
> > happily support this patch since I use it in all my galleries.
> 
> As a bystander, I would say: great idea! Maybe even better would be to
> check with the original upstream to see if you can take over? That way
> not just Debian will benefit from your geolocation patch.

I agree that this would be the best solution in principle.  However, I'm
not really the person to maintain some Perl software officially.  I can
read Perl a bit and it was enough for a simple patch.  But I can not
really claim to maintain this software neither will my time permit to
work honestly on things that are on the published todo list.

So I think I'll add myself to Uploaders, upload including the patch
and ping the according upstream issue about the status.

Thanks a lot for your and Daniel's trust and support

Andreas.

-- 
http://fam-tille.de

Bug#1008840: linphone: Recording does not work due to lack of mkv support

[Dennis Filder]

X-Debbugs-CC: Rainer Dorsch 

Oops, forgot something:

On Sat, Apr 02, 2022 at 08:27:19PM +0200, Rainer Dorsch wrote:
> Do you think 4.3.2 builds also on bullseye or does it have dependencies, which
> are not in bullseye?

It should work and a backport is planned.

Regards.

Bug#821926: Group upload of geolocation enable fgallery (Was: Please support geolocation)

[Daniel Lenharo]

Hi Andreas!

Em 02/04/2022 14:00, Andreas Tille escreveu:

Hi Daniel,

I've seen that you updated the packaging of fgallery in Git.  I'd like
to join you as Uploader of this package and would love to inject my
patch for geolocation.  I'm using my patch since six years now
successfully.  It seems upstream is dead and so I think if we want
to provide this functionality to our users we are on our own.  I'm
happily support this patch since I use it in all my galleries.



I had some personal problems and didn't yet finish my ITA,

Of course you are very welcome to join!!

thanks!!

--
Daniel Lenharo
Curitiba - Brazil
www.sombra.eti.br
31D8 0509 460E FB31 DF4B
9629 FB0E 132D DB0A A5B1


OpenPGP_0xFB0E132DDB0AA5B1.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008853: RFS: sfeed/1.3-1 [ITP] -- Command-line tools for processing RSS and Atom feeds

[Sebastian Crane]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name: sfeed
   Version : 1.3-1
   Upstream Author : Hiltjo Posthuma 
 * URL : https://codemadness.org/sfeed-simple-feed-parser.html
 * License : ISC
 * Vcs : https://salsa.debian.org/seabass/sfeed
   Section : net

The source builds the following binary packages:

  sfeed - Command-line tools for processing RSS and Atom feeds

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/s/sfeed/sfeed_1.3-1.dsc

Changes for the initial release:

 sfeed (1.3-1) unstable; urgency=low
 .
   * Initial release. (Closes: 1000594)

Looking forward to reading any comments or suggestions you might have,
and thank you for reading!

Best wishes,

Sebastian

Bug#1008854: Packages using gnuradio-dev FTBFS

[Adrian Bunk]

Package: gnuradio-dev
Version: 3.10.1.1-2
Severity: serious
Tags: ftbfs
Control: affects -1 src:gr-limesdr src:gr-funcube src:gr-rds src:gr-hpsdr 
src:gr-fosphor src:gr-satellites src:gr-radar src:gr-iqbal

https://buildd.debian.org/status/fetch.php?pkg=gr-limesdr&arch=amd64&ver=3.0.1-4%2Bb1&stamp=1648925444&raw=0

...
   dh_install -a
dh_install: warning: Cannot find (any matches for) "usr/lib/python*" (tried in 
., debian/tmp)

dh_install: warning: gr-limesdr missing files: usr/lib/python*
dh_install: error: missing files, aborting



This might be related to #1008794 ?

Bug#1008855: Please package newer NGINX Stable version 1.20.0

[Thomas Ward]

Source: nginx
Severity: wishlist

NGINX 1.18 was released back in 2020. This is substantially older than 
Upstream versions, which released 1.20 in April of 2021 (nearly a year ago).


Please upgrade the package version in Debian to 1.20 as soon as 
possible, and then when NGINX 1.22.0 releases this year (within the 
month!) please include that version as well in your updates.


It should never have gotten to the point that this is so neglected - 
historically the package has ALWAYS been kept up to date, hasn't had 
FTBFSes, and has always tracked the yearly Stable branch from upstream.



Thomas

Bug#1008856: Homepage field points to broken nginx.net site

[Antoine Beaupre]

Package: nginx
Version: 1.18.0-6.1
Severity: minor

It seems like the nginx package points to https://nginx.net/ in its
Homepage: field.

Both curl and Firefox fail to load that webpage:

$ curl https://nginx.net/
curl: (35) error:14094458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name

It might also explain why the package doesn't show as missing an
upstream release in the tracker.

Maybe the debian/watch file also needs an update then, but I haven't
checked that specifically.

See also #1008855.


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

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

Versions of packages nginx depends on:
ii  nginx-core  1.18.0-6.1
ii  nginx-full  1.18.0-6.1

nginx recommends no packages.

nginx suggests no packages.

-- no debconf information

Bug#1008840: linphone: Recording does not work due to lack of mkv support

[Dennis Filder]

X-Debbugs-CC: Rainer Dorsch 

On Sat, Apr 02, 2022 at 10:24:49PM +0200, Rainer Dorsch wrote:
> Thanks for the analysis. Do you think it would be sufficient to replace the 
> .mkv
> with .wav in ./linphone-app/src/components/call/CallModel.cpp
>
> [...]
>
> and rebuild the Debian package?

You'll have to find out by trying.  From my cursory reading
Mediastreamer2 determines the backend from the extension, so the
chances are somewhat high that it will work.  But I cannot say if
something else in linphone-desktop won't break, e.g. when trying to
append to an existing recording.

Regards.

Bug#1008787: Deep dive discovered partial fix

[Thomas Ward]

So, it seems that this problem leads to a deeper problem, one with a 
fix, and one that leaves the s390x support at an impasse.


Firstly, mips64el has libluajit available.  We can fix the mips64el 
builds by adding libluajit-5.1-dev as an explicit dependency for mips64el.


However, we can NO LONGER use lua-nginx on any Debian release that has 
no libluajit because Upstream has changed dependencies. As such, we 
cannot package the Lua module for s390x, which makes this package still 
unsuitable for s390x as a result of nginx-extras depending on the Lua 
module.  Per upstream on that module:


> Since version |v0.10.16| of this module, the standard Lua interpreter 
(also known as "PUC-Rio Lua") is not supported anymore. [1]


This means that s390x support for NGINX will need to be dropped, or the 
Lua module will need to be dropped, or the Lua module will need 
*downgraded* to v0.10.15 which was the last version of the module to 
support liblua as a dependency.


If it is chosen to drop s390x support in nginx here, then the liblua 
dependency can be dropped entirely from build depends.  If it is chosen 
to downgrade the module to v0.10.15 then liblua will still work and the 
build dependencies will not need changed.


(Note that downstream in Ubuntu, the Lua module was dropped because of 
the problem with it later now requiring resty-core as a dependency, 
which the Ubuntu Server Team downstream no longer wishes to include just 
to get Lua working, and is pushing people who need Lua module to just 
use Open Resty.)




Thomas

[1]: https://github.com/openresty/lua-nginx-module#description

Bug#1008857: fsck: Automatic filesystem check skipped

[Elliott Mitchell]

Package: util-linux
Version: 2.36.1-8+devuan2
Severity: important

For some reason on this aarch64 device, the automated filesystem checks
which should be done via `fsck -T -M -A -a -t ext4` are getting skipped.
When trying to run this manually, no error messages of any sort was
observed.

During boot I am observing the message "warning: maximal mount count
reached, running e2fsck is recommended".

I'm aware of two system quirks which might cause `fsck` to fail.

This is an aarch64 (ARM64) system.

The main storage device is UAS and features a hybrid MBR.  Most utilities
and the Linux kernel find the valid GPT and ignore the hybrid GPT.

I recall running into an issue like this on a mipsel system many years
ago.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Bug#1008854: Packages using gnuradio-dev FTBFS

[A. Maitland Bottoms]

>> affects -1 src:gr-limesdr src:gr-funcube src:gr-rds src:gr-hpsdr 
>> src:gr-fosphor src:gr-satellites src:gr-radar src:gr-iqbal
> Bug #1008854 [gnuradio-dev] Packages using gnuradio-dev FTBFS
> Added indication that 1008854 affects src:gr-limesdr, src:gr-funcube, 
> src:gr-rds, src:gr-hpsdr, src:gr-fosphor, src:gr-satellites, src:gr-radar, 
> and src:gr-iqbal
>
> -- 
> 1008854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008854
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

OK.

I am preparing gnuradio_3.10.2.0-2 which explicitly uses 'posix_prefix'
from Python3's sysconfig in GrPython.cmake

The other gr-* packages will then have the expected python path for the
.install files to work as well.

Lots of other improvements - uploading to unstable.

-Maitland

Bug#1008858: Please support s390x

[Thomas Ward]

Source: luajit
Severity: wishlist

Please support s390x if possible.  NGINX's Lua module support depends on 
libluajit exclusively now, and would need s390x support for proper support.


Thomas

Bug#631280: libphp-jpgraph: uses deprecated PHP functions

[Thorsten Glaser]

Package: libphp-jpgraph
Version: 1.5.2-13.1
Followup-For: Bug #631280
Control: severity -1 serious

It’s not just that:

PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; LinePlot has a deprecated constructor 
in /usr/share/jpgraph/jpgraph_line.php on line 52

This is a warning in bullseye, but bookworm’s PHP 8 will error out there.


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

Kernel: Linux 5.10.0-13-amd64 (SMP w/1 CPU thread)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages libphp-jpgraph depends on:
ii  fonts-arkpandora2.04-1.1
ii  fonts-liberation1:1.07.4-11
ii  libapache2-mod-php  2:7.4+76
ii  libapache2-mod-php7.4 [libapache2-mod-php]  7.4.28-1+deb11u1
ii  php-cgi 2:7.4+76
ii  php-gd  2:7.4+76
ii  php7.4-cgi [php-cgi]7.4.28-1+deb11u1
ii  php7.4-gd [php-gd]  7.4.28-1+deb11u1

libphp-jpgraph recommends no packages.

libphp-jpgraph suggests no packages.

-- no debconf information

Bug#1008858: [pkg-lua-devel] Bug#1008858: Please support s390x

[Jérémy Lal]

On Sun, Apr 3, 2022 at 12:21 AM Thomas Ward  wrote:

> Source: luajit
> Severity: wishlist
>
> Please support s390x if possible.  NGINX's Lua module support depends on
> libluajit exclusively now, and would need s390x support for proper support.
>

There is a PR for that
https://github.com/LuaJIT/LuaJIT/pull/395

however it still requires to be tested and reviewed.

Bug#1008402: khmer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Stefano Rivera]

Hi Lucas (2022.03.26_17:21:07_-0400)
> > self = FileType('wb'), string = '-'
> > 
> > def __call__(self, string):
> > # the special argument "-" means sys.std{in,out}
> > if string == '-':
> > if 'r' in self._mode:
> > return _sys.stdin.buffer if 'b' in self._mode else 
> > _sys.stdin
> > elif any(c in self._mode for c in 'wax'):
> > >   return _sys.stdout.buffer if 'b' in self._mode else 
> > > _sys.stdout
> > E   AttributeError: '_io.StringIO' object has no attribute 
> > 'buffer'

I assume the big relevant change here is
https://bugs.python.org/issue14156 being fixed

I experimented a little and got to this patch, but it isn't complete
yet.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
--- a/tests/khmer_tst_utils.py
+++ b/tests/khmer_tst_utils.py
@@ -44,18 +44,13 @@
 import sys
 import traceback
 import subprocess
-from io import open  # pylint: disable=redefined-builtin
+from io import BufferedWriter, BytesIO, StringIO, TextIOWrapper
 from hashlib import md5
 
 from khmer import reverse_complement as revcomp
 
 import pytest
 
-try:
-from StringIO import StringIO
-except ImportError:
-from io import StringIO
-
 
 def _equals_rc(query, match):
 return (query == match) or (revcomp(query) == match)
@@ -151,6 +146,25 @@
 return -1
 
 
+class StdIOBuffer(TextIOWrapper):
+'''Replacement for writable io.StringIO that behaves more like real file
+Unlike StringIO, provides a buffer attribute that holds the underlying
+binary data, allowing it to replace sys.stdout/sys.stderr in more
+contexts.
+'''
+
+name = 'StdIOBuffer'
+
+def __init__(self, initial_value='', newline='\n'):
+initial_value = initial_value.encode('utf-8')
+super().__init__(BufferedWriter(BytesIO(initial_value)),
+ 'utf-8', newline=newline)
+
+def getvalue(self):
+self.flush()
+return self.buffer.raw.getvalue().decode('utf-8')
+
+
 def runscript(scriptname, args, in_directory=None,
   fail_ok=False, sandbox=False):
 """Run a Python script using exec().
@@ -172,9 +186,8 @@
 sys.argv = sysargs
 
 oldout, olderr = sys.stdout, sys.stderr
-sys.stdout = StringIO()
-sys.stdout.name = "StringIO"
-sys.stderr = StringIO()
+sys.stdout = StdIOBuffer()
+sys.stderr = StdIOBuffer()
 
 if in_directory:
 os.chdir(in_directory)
--- a/khmer/khmer_args.py
+++ b/khmer/khmer_args.py
@@ -158,14 +158,16 @@
 
 # Temporary fix to argparse FileType which ignores the
 # binary mode flag. Upstream bug tracked in https://bugs.python.org/issue14156
+# Fixed in 3.9.12 and 3.10.3.
 # pylint: disable=too-few-public-methods,missing-docstring
 class FileType(argparse.FileType):
 def __call__(self, fname):
 # detect if stdout is being faked (StringIO during unit tests) in
 # which case we do not have to do anything
 if (fname == '-' and
-sys.version_info.major == 3 and
-not isinstance(sys.stdout, StringIO)):
+not isinstance(sys.stdout, StringIO) and
+(sys.version_info < (3, 9, 12) or
+ (3, 10) < sys.version_info < (3, 10, 3))):
 if 'r' in self._mode:
 fname = sys.stdin.fileno()
 elif 'w' in self._mode:
--- a/khmer/kfile.py
+++ b/khmer/kfile.py
@@ -209,6 +209,8 @@
 """Take in a file object and checks to see if it's a block or fifo."""
 if fthing is sys.stdout or fthing is sys.stdin:
 return True
+elif not hasattr(fthing, 'name'):
+return True
 else:
 mode = os.stat(fthing.name).st_mode
 return S_ISBLK(mode) or S_ISCHR(mode)
--- a/scripts/trim-low-abund.py
+++ b/scripts/trim-low-abund.py
@@ -512,7 +512,7 @@
 
 if args.output is None:
 log_info('output in *.abundtrim')
-elif args.output.name == 1:
+elif not hasattr(args.output, 'name') or args.output.name == 1:
 log_info('output streamed to stdout')
 elif args.output.name:
 log_info('output in {}'.format(args.output.name))

Bug#1008859: RFS: solarwolf/1.5+dfsg1-5 -- Collect the boxes and don't become mad

[Judit Foglszinger]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: solarwolf
   Version : 1.5+dfsg1-5
   Upstream Author : Pete Shinners 
 * URL : https://www.pygame.org/shredwheat/solarwolf/index.shtml
 * License : LGPL-2.1, GPL-2
 * Vcs : https://salsa.debian.org/games-team/solarwolf
   Section : games

Solarwolf has transparency problems with a few pictures,
with pygame version 2.1.2, that is in sid now.
This upload is to fix those.

The source builds the following binary packages:

  solarwolf - Collect the boxes and don't become mad

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/solarwolf/solarwolf_1.5+dfsg1-5.dsc

Changes since the last upload:

 solarwolf (1.5+dfsg1-5) unstable; urgency=low
 .
   * patches: Fixing transparency loss of powerup symbols/bullet time effect
  due to transition to pygame2 (Closes: #1008771)

Regards,
-- 
  Judit Foglszinger

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

Bug#1008860: O: node-keygrip -- Key signing and verification for rotated credentials for Node.js

[Boyuan Yang]

Package: wnpp
Severity: normal
Control: affects -1 node-keygrip

According to https://bugs.debian.org/909902 , I orphan this package.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly. You do not need others'
permission to adopt a package.

Some information about this package:

Package: node-keygrip
Binary: node-keygrip
Version: 1.1.0-2
Maintainer: Debian Javascript Maintainers

Uploaders: Andrew Kelley 
Build-Depends: debhelper-compat (= 13), dh-sequence-nodejs, mocha 
Architecture: all
Standards-Version: 4.6.0
Format: 3.0 (quilt)
Files:
 b52a786b10263c68825e8010fcb35fab 2303 node-keygrip_1.1.0-2.dsc
 bc797977b65eade14e695784201b982b 3795 node-keygrip_1.1.0.orig-tsscmp.tar.gz
 16f8a5a3b8b51577c7e9d7c880f792b2 5468 node-keygrip_1.1.0.orig.tar.gz
 e308fdbdf854d6d846ce5e8aa6e4d8a0 2900 node-keygrip_1.1.0-2.debian.tar.xz
Vcs-Browser: https://salsa.debian.org/js-team/node-keygrip
Vcs-Git: https://salsa.debian.org/js-team/node-keygrip.git

Package: node-keygrip
Version: 1.1.0-2
Priority: optional
Section: javascript
Maintainer: Debian Javascript Maintainers

Installed-Size: 23.6 kB
Homepage: https://github.com/expressjs/keygrip
Download-Size: 6,620 B
APT-Sources: http://deb.debian.org/debian unstable/main amd64 Packages
Description: Key signing and verification for rotated credentials for Node.js
 This module helps signing and verifying data through a rotating credential
 system, in which new server keys can be added and old ones removed regularly,
 without invalidating client credentials.
 .
 Node.js is an event-based server-side JavaScript engine.


-- 
Thanks,
Boyuan Yang




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

Bug#1008861: network-manager-ssh: uses incorrect local tap interface

[Max Filippov]

Package: network-manager-ssh
Version: 1.2.11-1
Severity: normal

Hello,

on a Debian system with /bin/sh pointing to dash network-manager-ssh
incorrectly decides that tap0 is available for use as a local interface.
When tap0 is in use by some other application this results in inability
to connect to the ssh-based VPN.

My expectation is that network-manager-ssh should be able to find an
unused tap interface name regardless of the default shell type.

I have reported it and proposed a fix to the upstream here:
  
https://github.com/danfruehauf/NetworkManager-ssh/pull/105/commits/82b4217e89e1abb5554609c6096b2e21c4e4eab2

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

Kernel: Linux 5.10.0-11-amd64 (SMP w/8 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 network-manager-ssh depends on:
ii  libc6   2.31-13+deb11u3
ii  libglib2.0-02.66.8-1
ii  libnm0  1.30.0-2
ii  openssh-client  1:8.4p1-5
ii  sshpass 1.09-1+b1

Versions of packages network-manager-ssh recommends:
ii  network-manager-ssh-gnome  1.2.11-1

network-manager-ssh suggests no packages.

-- no debconf information

-- 
Thanks.
-- Max

Bug#1008280: pstoedit: silently fails with success return for some purifyeps use cases

[Thorsten Glaser]

Package: pstoedit
Version: 3.78-1
Followup-For: Bug #1008280
X-Debbugs-Cc: t...@mirbsd.de

This is reproducible on sid.

It also occurs on buster, although with a different failure mode:

-BEGIN cutting here may damage your screen surface-
$ purifyeps test1-a.eps test1-b.eps
pstoedit: version 3.73 / DLL interface 108 (built: Jul 11 2018 - release build 
- g++ 7.3.0 - 32-bit) : Copyright (C) 1993 - 2018 Wolfgang Glunz
Error: /undefined in .makeoperator
Operand stack:
   false   rectfill   rectfill   --nostringval--
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   1991   1   3   %oparray_pop   
1990   1   3   %oparray_pop   1978   1   3   %oparray_pop   1833   1   3   
%oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   
--nostringval--   --nostringval--   2   %stopped_push   --nostringval--   
--nostringval--   --nostringval--
Dictionary stack:
   --dict:1033/1123(G)--   --dict:0/20(G)--   --dict:216/300(L)--   
--dict:1033/1123(G)--
Current allocation mode is global
Current file position is 14841
GPL Ghostscript 9.27: Unrecoverable error, exit code 1
PostScript/PDF Interpreter finished. Return status 256 executed command : gs -q 
-dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS "/tmp/psinbqMIs2"
The interpreter seems to have failed, cannot proceed !
purifyeps: The following command failed with exit code 1:
pstoedit -ssp -f mpost -fontmap "/usr/share/pstoedit/mpost.fmp" 
"test1-a.eps" "/tmp/purifyeps-hn9Vq58x.mp"
-END cutting here may damage your screen surface-

stretch looks similar to bullseye though:

-BEGIN cutting here may damage your screen surface-
$ purifyeps test1-a.eps test1-b.eps
pstoedit: version 3.70 / DLL interface 108 (built: Oct 11 2016 - release build 
- g++ 6.2.1 20161215 - 32-bit) : Copyright (C) 1993 - 2014 Wolfgang Glunz
This is MetaPost, version 1.9991 (TeX Live 2016/Debian) (kpathsea version 6.2.2)
(/usr/share/texlive/texmf-dist/metapost/base/mpost.mp
(/usr/share/texlive/texmf-dist/metapost/base/plain.mp
Preloading the plain mem file, version 1.005) ) (/tmp/purifyeps-nUGj2O9a.mp )
Transcript written on purifyeps-nUGj2O9a.log.
purifyeps: No such file or directory (/tmp/purifyeps-nUGj2O9a.1)
-END cutting here may damage your screen surface-

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

Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages pstoedit depends on:
ii  ghostscript  9.55.0~dfsg-3
ii  libc62.33-7
ii  libpstoedit0c2a  3.78-1
ii  libstdc++6   12-20220319-1

pstoedit recommends no packages.

Versions of packages pstoedit suggests:
pn  xfig | ivtools-bin | tgif | transfig  

-- no debconf information

Bug#977647: 5.10.4 Debian kernel does not boot on amd64 with btrfs rootfs

[Ryutaroh Matsumoto]

Control: close -1

>> The severity seems now minor.
>> It has still the mysterious dmesg error on tpm as follows.
>> The full dmesg log is attached.
> 
> Do you still have the issues? Otherwise let's close this bug.

No. Let's close this. Ryutaroh

Bug#1008280: pstoedit: silently fails with success return for some purifyeps use cases

[Thorsten Glaser]

Dixi quod…

>Package: pstoedit
>Version: 3.78-1
>Followup-For: Bug #1008280

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008280
for the full story and reproducer.

With the help of http://www.calvina.de/pstoedit/pstoedit.htm#section_69
I may have found a workaround (which indicates a bug in pstoedit’s ps
handling, per the instructions there).

The bug appears when doing:

$ inkscape -D --export-filename=test1.pdf --export-type=pdf \
--export-pdf-version=1.4 teckids_logo_image.svg
$ pdftops -eps test1.pdf test1-a.eps
$ purifyeps test1-a.eps test1-b.eps
 which calls
  pstoedit -ssp -f mpost -fontmap /usr/share/pstoedit/mpost.fmp \
test1-a.eps tmp.mp

If I instead run…
$ purifyeps test1.pdf test3.eps
(which is NOT documented, purifyeps says it takes PostScript only
as input but since it relies on pstoedit, this seems to work) then
I get a result file that at least looks the same with gs.

So something weird happens in pdftops from poppler-utils :/
(Huh. I’d have thought pdftops is part of ghostscript… apparently not.)

Looking at this more: pdftops -eps test1.pdf test1a-$distro.eps
followed by purifyeps test1a-$distro.eps test1b-$distro.eps

This fails on all chroots I tested: stretch 0.48.0-2+deb9u4,
buster 0.71.0-5, bullseye 20.09.0-3.1, sid 22.02.0-3

Another experiment, getting rid of poppler-utils in the middle:

-BEGIN cutting here may damage your screen surface-
$ pdf2ps test1.pdf test4-1.ps
$ ps2eps test4-1.ps
Input files: test4-1.ps
Processing: test4-1.ps
Rendering with existing %%BoundingBox: 0 0 234 187
Calculating Bounding Box...ready. %%BoundingBox: 0 0 234 187
Creating output file test4-1.eps ... ready.
$ purifyeps test4-1.eps test4-2.eps
pstoedit: version 3.75 / DLL interface 108 (built: Jan  2 2020 - release build 
- g++ 9.2.1 20191130 - 64-bit) : Copyright (C) 1993 - 2020 Wolfgang Glunz
This is MetaPost, version 2.00 (TeX Live 2020/Debian) (kpathsea version 6.3.2)
(/usr/share/texlive/texmf-dist/metapost/base/mpost.mp
(/usr/share/texlive/texmf-dist/metapost/base/plain.mp
Preloading the plain mem file, version 1.005) ) (/tmp/purifyeps-PG1MlbvQ.mp )
Transcript written on purifyeps-PG1MlbvQ.log.
purifyeps: No such file or directory (/tmp/purifyeps-PG1MlbvQ.1)
-END cutting here may damage your screen surface-

Looks like it’s not poppler at fault here though :~

Any idea? (Also, I can’t find where pstoedit’s bugtracker is.)

bye,
//mirabilos
-- 
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit
gerechnet, darum bin ich blutverschmiert… wer konnte ahnen, daß SIE so
reagier’n… gestern Nacht ist mein IRC-Netzwerk explodiert~~~
(as of 2021-06-15 The MirOS Project temporarily reconvenes on OFTC)

Bug#1008863: python3-service-identity: Would you mind considering upgrade to 21.1.0?

[Takahide Nojima]

Package: python3-service-identity
Version: 18.1.0-6
Severity: normal

Dear Maintainer,

 Would you mind considering an upgrade to 21.1.0? The upstream has
released a newer version than the Debian package.

I would be grateful if you could upgrade.

Best Regards,
Takahide Nojima


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

Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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 python3-service-identity depends on:
ii  python3 3.10.4-1
ii  python3-attr    21.2.0-1
ii  python3-cryptography    3.4.8-1
ii  python3-pyasn1  0.4.8-1
ii  python3-pyasn1-modules  0.2.1-1

Versions of packages python3-service-identity recommends:
ii  python3-idna  3.3-1

python3-service-identity suggests no packages.

-- no debconf information

Bug#984049: enblend-enfuse: ftbfs with GCC-11

[Andreas Metzler]

On 2022-04-02 Florian Ernst  wrote:
[...]
> With the attached patch the package built here, cf. the also-attached
> libvigraimpex_1.11.1+dfsg-9_amd64-2022-04-02T17:52:42Z.build.

> A debdiff comparing the resulting binary packages against those from
> 1.11.1+dfsg-8 looks sane to me, cf. 984049.debdiff.

> I successfully tested building hugin and enblend-enfuse against the
> resulting binary packages, local logs available on demand.

> Please note that further patches might be required in the future, see
> e.g. . However, at the
> moment the build fails when I apply that patch ...

Thank you.

FWIW upstream stil looks pretty dead. I am subscribed to the whole
project and there are about two messages per month.

cu Andreas

Bug#998092: python3-coloredlogs: Please upgrade to the latest version of upstream.

[Takahide Nojima]

Dear Maintainer

The newest version of coloredlogs seems to have many enhanced features.
See. https://github.com/xolox/python-coloredlogs/compare/7.3...15.0.1

Would you mind upgrading to the latest version in the Debian package?

If you have some trouble keeping up with the upstream version, I would
be grateful if you could write here.

Best Regards,
Takahide Nojima

Bug#1008810: thrift: FTBFS with Python 3.10

[GCS]

Control: tags -1 +pending

On Sat, Apr 2, 2022 at 12:27 AM Stefano Rivera  wrote:
> Source: thrift
> Version: 0.13.0-7
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
>
> I see that thrift FTBFS now that Python 3.10 is default.
>
> GOPATH=`pwd`/gopath /usr/bin/go test thrift tests dontexportrwtest
 With all due respect, it's a Golang FTBFS and not a Python one.
Already reported [1] and fixed in experimental. Waiting for the ACK on
my transition request [2].
Hope it will be allowed soon and will close this bug report when I
upload thrift to Sid.

Regards,
Laszlo/GCS
[1] https://bugs.debian.org/1008458
[2] https://bugs.debian.org/1008823

Bug#907174: New version available

[Florian Ernst]

Hello Andrew,

On Sat, Apr 02, 2022 at 02:32:07PM -0400, Andrew Ayer wrote:
> On Thu, 31 Mar 2022 17:42:37 +0200
> Florian Ernst  wrote:
> > [...]
> > On Wed, Mar 30, 2022 at 07:47:52PM -0400, Andrew Ayer wrote:
> > > [...]
> > > I am thinking of putting libndp up for adoption - might you be
> > > willing to take over?
> > 
> > Well, I am willing to help, and if that means I take over that'd be
> > fine with me, thanks for considering. No need to file an RFA in that
> > case, I could just refer to this bugreport here if you approve.
> 
> I approve.  Thanks again!

Thank you, and also thanks for all the work you have invested in
introducing and maintaining libndp. All the best for your future
endeavors!

I have now populated https://salsa.debian.org/debian/libndp with my
latest changes, an upload will follow as soon as the Salsa pipeline
finishes successfully.

Best regards,
Flo


signature.asc
Description: PGP signature

Bug#1008817: libphonenumber8: breaks evolution

[Adrian Bunk]

On Sat, Apr 02, 2022 at 10:29:05AM -0700, tony mancill wrote:
> On Sat, Apr 02, 2022 at 08:11:39PM +0300, Adrian Bunk wrote:
> > On Sat, Apr 02, 2022 at 10:39:13AM -0600, Neil Mayhew wrote:
> > > On 2022-04-02 09:14, tony mancill wrote:
> > > > I will work on patching 8.12.46 and also mention this upstream. The
> > > > changelogs for 8.12.45 and 8.12.46 only reference metadata updates.
> > > 
> > > If there was a non-metadata change that wasn't mentioned in the changelog,
> > > it will be the second time this has happened in a fairly short period. The
> > > other one was https://github.com/google/libphonenumber/pull/2698 which was
> > > merged on Jan 7.
> > 
> > The problem is 
> > https://github.com/google/libphonenumber/commit/5719f3a724d254b21196393d952b71ec3052e6a3
> > 
> > I have an approximate fix I can polish later this evening,
> > unless Tony already has something similar.
> 
> Hi Adrian,

Hi Tony,

> Thank you for the pointer.  I started picking through the delta between
> 8.12.44 and 8.12.46 and it appears that libphonenumber needs to ensure
> that absl/hash/internal/hash.cc is linked.  I won't have a chance to
> work on patch until later in my day (GMT-7) and so would be glad to
> receive yours.  Otherwise, I will work on it tonight.

sorry, I didn't get to it yesterday evening.

In case you don't already have something similar, my fix is:
https://github.com/AdrianBunk/libphonenumber/commit/a7337f0072293ae07431d5efe7d2f9efa54bfd2d

> I will do a full reverse build-deps (ratt) build before uploading.

My testcase was the kitinerary FTBFS, which is fixed by the change above.

> Cheers,
> tony

cu
Adrian