Bug#1003812: build-rdeps: broken after libxml-libxml-perl update

[Mattia Rizzolo]

Control: reassign -1 dpkg-repack
Control: forcemerge 1003814 -1
Control: affects 1003814 devscripts

On Sun, Jan 16, 2022 at 03:54:38AM +, Mathias Gibbens wrote:
> Package: devscripts
> Version: 2.21.7
> Severity: important
> 
>   A new version of libxml-libxml-perl has just been uploaded to
> unstable, which unfortunately breaks the build-rdep utility

That's totally unrelated to libxml-libxml-perl, see #1003814

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1003769: RFS: byacc/1.0-2 [ITA] -- public domain Berkeley LALR Yacc parser generator

[Andreas Metzler]

On 2022-01-15 Thomas Dickey  wrote:
[...]
> I am looking for a sponsor for my package "byacc":

>  * Package name: byacc
>Version : 1:2.0.20220114-1
>Upstream Author :  (Thomas E. Dickey)
>  * URL : https://invisible-island.net/byacc/
>  * License : GPL-3, public-domain, other-BSD
>  * Vcs : https://salsa.debian.org/debian/byacc
>Section : devel

> It builds those binary packages:

>   byacc - public domain Berkeley LALR Yacc parser generator
>   byacc2 - public domain Berkeley LALR Yacc parser generator, with 
> back-tracking
[...]

Hello Thomas,

I would like to question the introduction of another binary package:
* "byacc2" seems to be a (newly introduced) Debiansm. Googling for
  "byacc2" only finds links related to this RFS.
* The packages are tiny (about 100k) and have no conflicting files.
  /usr/bin/byacc2 and /usr/bin/byacc could be shipped in on binary
  package.
* Is the double compilation/binary necessary? - Is /usr/bin/byacc2
  incompatible with /usr/bin/byacc2? A quick glance at the yacc.1 seems
  to suggests that /usr/bin/byacc2 is a backward compatible extension of
  /usr/bin/byacc the only difference being that it additionally supports
  | -B   create a backtracking parser

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

Bug#1003774: bind9-host: Incorrect formatting in host.1 man page

[Ondřej Surý]

Control: tags -1 pending

Thanks,

I have merged the fix upstream and it will be also fixed in Debian when we 
update
the upstream version here.

Ondrej
--
Ondřej Surý (He/Him)
ond...@sury.org

> On 15. 1. 2022, at 20:45, Adam Dinwoodie 
>  wrote:
> 
> On Sat, Jan 15, 2022 at 06:16:58PM +0100, Ondřej Surý wrote:
>> Hi Adam,
>> 
>> thanks for the patch, but it cannot be used as the host.rst needs to be 
>> fixed. The man page is generated using sphinx-build from the rst source.
>> 
>> Ondřej 
> 
> Ah, I had misunderstood how the man page was built.  Try this version?
> 

Bug#1003751: In NEW queue

[Felix Lechner]

The sources were uploaded and are now in the NEW queue.

Bug#1003816: i3 session does not activate systemd graphical-session.target

[smheidrich]

Package: i3
Version: 4.19.1-1
Severity: wishlist
X-Debbugs-Cc: smheidr...@weltenfunktion.de

systemd defines a special (user) target called graphical-session.target [1]
which should be active when the user is logged into a graphical session.
Currently, when I'm logged into a default i3 session (entered via GDM), this
target is inactive:

  $ systemctl --user status graphical-session.target
  ● graphical-session.target - Current graphical user session
   Loaded: loaded (/usr/lib/systemd/user/graphical-session.target; static)
   Active: inactive (dead)
 Docs: man:systemd.special(7)

If I understood the clarifications in a thread [2] on systemd's mailing list
and the linked slides [3] correctly, this target should be activated by
specifying the session in question as a systemd service with BindsTo=graphical-
session.target and launching this service from the relevant
/usr/share/xsessions/*.desktop instead of launching the session directly.

In i3's case, the /usr/share/xsessions/i3.desktop session definition is
provided by the i3-wm package and just launches i3 directly. This makes perfect
sense, as systemd isn't mandatory on Debian and the aforementioned session-as-
service mechanism wouldn't work at all for people using SysVinit. But perhaps
there could be two session definitions, one with and one without an associated
systemd service?

An objection I expect is that users should just write their own session files
if they need this "feature", but the same would apply to the default
/usr/share/xsessions/i3.desktop file, which is only included for compatibility
with common display/login managers. Ditto for the argument that this is out of
scope for a window manager and gets into desktop environment territory.
Besides, it's not merely a missing feature but a bug (not necessarily in the i3
package but somewhere in the Debian distribution): Promises that are made in
systemd's documentation [1] are not kept when using distribution-provided
graphical session definitions.

Unfortunately, the only precedent for this type of session file in other window
manager or desktop environment packages I could find is in the gnome-session-
common package (apt-file search session.target), so perhaps it would in fact be
better to provide this via a separate package? There are a bunch of packages
for the Openbox window manager that do nothing but provide sessions for running
it along with the non-WM processes of common desktop environments (openbox-
gnome-session, openbox-lxde-session, openbox-kde-session, ...), so a package
providing only a session file for running i3 in a systemd-compatible manner
doesn't sound totally unreasonable to me. This could then be suggested by the
i3 package.

Let me know your thoughts.

Kind regards


[1]:
https://www.freedesktop.org/software/systemd/man/systemd.special.html#graphical-
session.target
[2]: https://systemd-devel.freedesktop.narkive.com/J9pItAjq/graphical-session-
targets-as-standard#post10
[3]: https://people.debian.org/~mpitt/systemd.conf-2016-graphical-session.pdf



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

Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=C.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 i3 depends on:
ii  i3-wm  4.19.1-1

Versions of packages i3 recommends:
ii  dunst   1.5.0-1
ii  i3lock  2.13-1+b1
ii  i3status2.13-3
ii  suckless-tools  46-1

i3 suggests no packages.

Bug#984063: Closing bug (Was: Bug#984063: itk libtiff test issues (Was: Bug#984063))

[Andreas Tille]

Am Sun, Jan 16, 2022 at 07:07:01AM +0100 schrieb Sebastiaan Couwenberg:
> On 1/15/22 21:45, Andreas Tille wrote:
> > > There is no RM bug for insighttoolkit4 yet,
> > 
> > Steve simply bumped the version right in d/changelog[1]
> 
> How does the insighttoolkit5 package in unstable cause the removal of
> insighttoolkit4?

It does not.  However, from simply using the same repository you can
draw the conclusion that there is no intention to maintain two different
versions.  Well, for sure we could use another branch - but Steve in
some mail on Debian Med list stated he has no intention to maintain
more than one version.
 
> > IMHO it would be sad to loose OTB.  When I once started looking at the
> > packaging upstream was quite responsive.  Did you discussed the issue?
> 
> I did, see the comments in the MR linked above. OTB 9 should support ITK5,
> but is not expected until the end of the year.

Thanks for the information.  I'm absolutely not in a hurry to file RM
requests for insighttoolkit4 and I think it is not sensible to remove
OTB just to reinject it later and waiting in new for a couple of months.
So we can simply leave the situation as is if you ask me.  In case you
might stumble upon a patch for insighttoolkit4 to build with recent gcc
and there are good reasons to keep this and current otb in testing I'd
volunteer to upload a fix for insighttoolkit4 (which I would not touch
personally otherwise).

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#984063: Closing bug (Was: Bug#984063: itk libtiff test issues (Was: Bug#984063))

[Sebastiaan Couwenberg]

On 1/15/22 21:45, Andreas Tille wrote:

Hi Bas,

Am Sat, Jan 15, 2022 at 08:30:26PM +0100 schrieb Sebastiaan Couwenberg:

Insighttoolkit4 will be removed from Debian.  We are now building
insighttoolkit5 and do not support insighttoolkit4 any more.


Good to know.

OTB won't support ITK5 for quite a while, though:

  https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/merge_requests/528

Removing itk4 will be difficult with rdeps still depending on it.

There is no RM bug for insighttoolkit4 yet,


Steve simply bumped the version right in d/changelog[1]


How does the insighttoolkit5 package in unstable cause the removal of 
insighttoolkit4?



when you file one feel free to
file one for otb as well and have it block the one for itk4, but please CC
pkg-grass-de...@lists.alioth.debian.org when you do.


IMHO it would be sad to loose OTB.  When I once started looking at the
packaging upstream was quite responsive.  Did you discussed the issue?


I did, see the comments in the MR linked above. OTB 9 should support 
ITK5, but is not expected until the end of the year.


Kind Regards,

Bas

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

Bug#1003815: ITP: makemkv -- One-click solution to convert video that you own into free format that can be played everywhere

[Ben Westover]

Package: wnpp
X-Debbugs-Cc: debian-de...@lists.debian.org
Owner: Ben Westover 
X-Debbugs-Cc: kwestover...@gmail.com
Severity: wishlist

* Package name: makemkv
  Version : 1.16.5
  Upstream Author : GuinpinSoft inc.
* URL : https://makemkv.com/
* License : GPL, LGPL, MIT, OpenSSL, custom
  Programming Lang: C++
  Description : One-click solution to convert video that you own 
into free format that can be played everywhere


MakeMKV is a format converter, otherwise called "transcoder".
It converts the video clips from proprietary discs into a set
of MKV files, preserving most information but not changing it
in any way. Additionally MakeMKV can instantly stream decrypted
video without intermediate conversion to wide range of players,
so you may watch Blu-ray and DVD discs with your favorite player
on your favorite OS or on your favorite device.

I do not plan to maintain this package in a team. I do not need any 
co-maintainers, but I will be needing a sponsor.


OpenPGP_0xC311C5F54E89B698.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003814: dpkg-repack: build profile with a slash breaks dose-builddebcheck

[Helmut Grohne]

Source: dpkg-repack
Version: 1.49
Severity: important
Control: affects -1 + dose-builddebcheck

Hi Guillem,

dose-repack's Build-Depends now contain a Build-Profile with a slash.
That's possibly an experiment for a dpkg time travel fix and possibly an
accident. Please clarify.

The most direct effect is breaking dose-builddebcheck:

The applications raised this exception : Dose_common.Format822.ParseError(_, 
"Build-Depends", "Field Build-Depends has a wrong value: 'debhelper-compat (= 
13), libtest-strict-perl , libtest-perl-critic-perl 
'")

As a consequence, rebootstrap and debcheck
(https://qa.debian.org/dose/debcheck/src_unstable_main/) are broken.
Given that the autobuilder is stuck on 1.48, I guess it also broke
buildd.d.o.

$Something will have to change. Either we revert the build profile or we
fix dose to handle this situation. This bug can be reassigned to the
proper place if necessary, but it tracks the need for change.

Helmut

Bug#1003813: libghc-lzma-dev: static C library missing as a prerequisite

[Felix Lechner]

Package: libghc-lzma-dev
Severity: normal

Hi,

I am new to Debian's ecosystem for Haskell, so please forgive me if
this filing is perhaps not entirely justified.

When building my new package 'kickoff' [1] using sbuild in a fresh
'unstable' chroot, I received the build error below. It looks to me
like the linker could not find the static LZMA library.

I believe the library is available in the installable 'liblzma-dev'.
(Your package [2] only pulls in the shared version via liblzma5.) Are
consuming sources supposed to depend on the C library separately?

The full build log was attached to this message. Thank you for your guidance!

Kind regards
Felix Lechner

[1] https://bugs.debian.org/1003751
[2] https://packages.debian.org/sid/libghc-lzma-dev

* * *

/usr/bin/ld.gold: error: cannot find -llzma
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/lzma-0.0.0.3-2n8nD73xk8SLYSVlgeU5jz/libHSlzma-0.0.0.3-2n8nD73xk8SLYSVlgeU5jz.a(lzma_wrapper.o):function
hs_lzma_init_decoder: error: undefined reference to
'lzma_stream_decoder'
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/lzma-0.0.0.3-2n8nD73xk8SLYSVlgeU5jz/libHSlzma-0.0.0.3-2n8nD73xk8SLYSVlgeU5jz.a(lzma_wrapper.o):function
hs_lzma_init_decoder: error: undefined reference to
'lzma_auto_decoder'
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/lzma-0.0.0.3-2n8nD73xk8SLYSVlgeU5jz/libHSlzma-0.0.0.3-2n8nD73xk8SLYSVlgeU5jz.a(lzma_wrapper.o):function
hs_lzma_init_encoder: error: undefined reference to
'lzma_easy_encoder'
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/lzma-0.0.0.3-2n8nD73xk8SLYSVlgeU5jz/libHSlzma-0.0.0.3-2n8nD73xk8SLYSVlgeU5jz.a(lzma_wrapper.o):function
hs_lzma_run: error: undefined reference to 'lzma_code'
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/lzma-0.0.0.3-2n8nD73xk8SLYSVlgeU5jz/libHSlzma-0.0.0.3-2n8nD73xk8SLYSVlgeU5jz.a(lzma_wrapper.o):function
hs_lzma_done: error: undefined reference to 'lzma_end'
collect2: error: ld returned 1 exit status
`x86_64-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1)
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


kickoff_0.1.0_amd64-2022-01-16T04:50:08Z.build.xz
Description: application/xz

Bug#1003805: python3-numpy: depends on two different Python versions

[Sandro Tosi]

control: tags -1 +wontfix

On Sat, Jan 15, 2022 at 7:33 PM Ian Bruce  wrote:
>
> Package: python3-numpy
> Version: 1:1.21.5-1
> Severity: important
>
> Depends:
>   python3 (<< 3.11),
>   python3 (>= 3.9~),
>   python3.10:any,
>   python3.9:any,
>   python3:any
>
> This bug recurs over and over again, with different Python versions;
> see, for example:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945824
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903663
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878281
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800620
>
> The stated explanation, that the package supports two different Python
> versions,
> so must depend on both of them, has always been completely nonsensical.

way to start a constructive discussion.

> The dependency can obviously be expressed as "python3.9:any | python3.10:any",
> rather than requiring both of them to be installed. This makes no sense at 
> all.
>
> No other package does this. It's completely irrational, and should not be
> allowed.

come up with a patch that works in every single situation and submit
it to the bts, anything less than that and you're wasting my time.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#1003394: xkbset-gui: Calling xkbset-gui creates a broken .xsession file

[ank]

I need to update something.

There is no xkbset-gui package, but xkbset exists. xkbset-gui appears to 
be part of xkbset. xkbset itsef seems to work fine.


Further appears xkbset-gui to be an API, not being called by a user. Thus 
xkbset-gui might also be okay.


If, this bug report can be closed. Sorry for filing it.

Bug#1003812: build-rdeps: broken after libxml-libxml-perl update

[Mathias Gibbens]

Package: devscripts
Version: 2.21.7
Severity: important

  A new version of libxml-libxml-perl has just been uploaded to
unstable, which unfortunately breaks the build-rdep utility:

> gibmat@build:~$ build-rdeps golang-github-j-keck-arping-dev
> Reverse Build-depends in main:
> --
> 
> golang-github-containernetworking-plugins
> singularity-container
> 
> Found a total of 2 reverse build-depend(s) for 
> golang-github-j-keck-arping-dev.
> 
> gibmat@build:~$ sudo apt upgrade
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Calculating upgrade... Done
> The following packages will be upgraded:
>   libxml-libxml-perl
> 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 340 kB of archives.
> After this operation, 6,144 B of additional disk space will be used.
> Do you want to continue? [Y/n] 
> Get:1 http://deb.debian.org/debian sid/main amd64 libxml-libxml-perl amd64 
> 2.0207+dfsg-2 [340 kB]
> Fetched 340 kB in 0s (20.0 MB/s)   
> (Reading database ... 37740 files and directories currently installed.)
> Preparing to unpack .../libxml-libxml-perl_2.0207+dfsg-2_amd64.deb ...
> update-perl-sax-parsers: Unregistering Perl SAX parser 
> XML::LibXML::SAX::Parser with priority 50...
> update-perl-sax-parsers: Unregistering Perl SAX parser XML::LibXML::SAX with 
> priority 50...
> update-perl-sax-parsers: Updating overall Perl SAX parser modules info file...
> Replacing config file /etc/perl/XML/SAX/ParserDetails.ini with new version
> Unpacking libxml-libxml-perl (2.0207+dfsg-2) over (2.0134+dfsg-2+b1) ...
> Setting up libxml-libxml-perl (2.0207+dfsg-2) ...
> update-perl-sax-parsers: Registering Perl SAX parser XML::LibXML::SAX::Parser 
> with priority 50...
> update-perl-sax-parsers: Registering Perl SAX parser XML::LibXML::SAX with 
> priority 50...
> update-perl-sax-parsers: Updating overall Perl SAX parser modules info file...
> Replacing config file /etc/perl/XML/SAX/ParserDetails.ini with new version
> Processing triggers for man-db (2.9.4-4) ...
> gibmat@build:~$ build-rdeps golang-github-j-keck-arping-dev
> Reverse Build-depends in main:
> --
> 
> The applications raised this exception : Dose_common.Format822.ParseError(_, 
> "Build-Depends", "Field Build-Depends has a wrong value: 'debhelper-compat (= 
> 13), libtest-strict-perl , libtest-perl-critic-perl 
> '")
> No reverse build-depends found for golang-github-j-keck-arping-dev.

  (I'm not sure if there's some update that will be needed for build-
rdep, or if this is an issue with libxml-libxml-perl; please
reassign/update this bug as needed.)


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

Bug#1003811: ITP: lunar-calendar -- Chinese Lunar Calendar widget for GTK+

[肖盛文]

Package: wnpp
Severity: wishlist
Owner: xiao sheng wen(肖盛文) 
X-Debbugs-Cc: debian-de...@lists.debian.org, atzli...@sina.com, 
u...@atzlinux.com

* Package name: lunar-calendar
  Version : 3.0.1
  Upstream Author : yetist 
* URL : https://github.com/yetist/lunar-calendar
* License : LGPL
  Programming Lang: C, C++, Python
  Description : Chinese Lunar Calendar widget for GTK+
 The LunarCalendar provide Chinese lunar Calendar Wieget for GTK+ .
 .
 It support the application that use GTK3 calendar to display Chinese Lunar
 Calendar, such as xfce4-panel, mate-panel, gtk3-widget-factory, etc.

 This package is useful for Chinese GUI Desktop user to display Chinese Lunar
 Calendar.It dependency on liblunar-date-3.0-1.

 There are not other packages providing similar functionality.

 lunar-calendar will be team-maintained by  Debian Chinese Team
 .
 I need a sponsor.

Bug#1003810: libxml-libxml-perl: getElementById is broken (regression)

[Vincent Lefevre]

Package: libxml-libxml-perl
Version: 2.0207+dfsg-2
Severity: grave
Justification: renders package unusable

getElementById no longer works.

There were no issues up to version 2.0134+dfsg-2+b1.

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.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 libxml-libxml-perl depends on:
ii  libc6 2.33-2
ii  libxml-namespacesupport-perl  1.12-1.1
ii  libxml-sax-perl   1.02+dfsg-3
ii  libxml2   2.9.12+dfsg-5+b1
ii  perl  5.32.1-6
ii  perl-base [perlapi-5.32.1]5.32.1-6

libxml-libxml-perl recommends no packages.

libxml-libxml-perl suggests no packages.

-- no debconf information

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

Bug#640881: 0.8.0 prepared in Salsa

[Matija Nalis]

I've prepared Salsa MRs for new 0.8.0 release.

I've done basic testing on amd64 and it seems to work fine, but if
someone else would like to test it, it would be great.

https://salsa.debian.org/games-team/uqm/-/merge_requests/4
https://salsa.debian.org/games-team/uqm-content/-/merge_requests/2

-- 
Opinions above are GNU-copylefted.

Bug#1003809: node-postcss: reproducible-builds: build path embedded in pkgjs-lock.json

[Vagrant Cascadian]

Source: node-postcss
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The build path of is embedded in a pkgjs-lock.json file:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-postcss.html

  /usr/share/nodejs/nanoid/pkgjs-lock.json

  "/build/1st/node-postcss-8.4.5+~cs7.1.51":·{
  vs.
  "/build/2/node-postcss-8.4.5+~cs7.1.51/2nd":·{

The attached patch to debian/rules works around this by replacing the
build path with a package and version string in a dh_compress override.


The pkgjs-lock.json files appear to be generated from pkg-js-tools and
might be possible to fix there instead; I'm not sure why the other
pkgjs-lock.json files in node-postcss do not have embedded build paths.


With this patch applied, node-postcss should build reproducibly on
tests.reproducible-builds.org!


Thanks for maintaining node-postcss!


live well,
  vagrant
From d91ed1d45facb624d5ac53a9271d0873686ee8c5 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 16 Jan 2022 02:38:43 +
Subject: [PATCH] debian/rules: Remove the build path from pkgjs-lock.json
 file.

The full build path is most likely not present on the end-user's
system, so replace it with PACKAGE-VERSION.
---
 debian/rules | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/debian/rules b/debian/rules
index 31a1f14..2f6ba64 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,9 +1,16 @@
 #!/usr/bin/make -f
 # -*- makefile -*-
 
+include /usr/share/dpkg/pkg-info.mk
+
 %:
 	dh $@
 
 override_dh_fixperms:
 	dh_fixperms
 	chmod +x debian/node-postcss/usr/share/nodejs/nanoid/bin/nanoid.cjs
+
+override_dh_compress:
+	# Remove build path for reproducibility
+	sed -i -e "s,$(CURDIR),$(DEB_SOURCE)-$(DEB_VERSION_UPSTREAM),g" debian/node-postcss/usr/share/nodejs/nanoid/pkgjs-lock.json
+	dh_compress
-- 
2.30.2



signature.asc
Description: PGP signature

Bug#1003808: libvcflib: reproducible-builds: BuildId differences triggered by RPATH

[Vagrant Cascadian]

Source: libvcflib
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The RPATH contains the build path resulting in different buildid:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libvcflib.html

The attached patch to debian/rules passes
-DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override,
which should use a relative path for RPATH.

Alternately, updating the packaging to debhelper compat level 14 should
fix this, although it is currently an experimental compat level.


With this patch applied, libvcflib should build reproducibly on
tests.reproducible-builds.org!


Thanks for maintaining libvcflib!


live well,
  vagrant
From 28fa4ee3a093404e5bb38df628660a8c004f3666 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sat, 15 Jan 2022 23:00:25 +
Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via
 dh_auto_configure override.

This avoids embedding the full path in RPATH, which triggers BuildId
differences.

https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html
---
 debian/rules | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/rules b/debian/rules
index c66b57f..03cb3e7 100755
--- a/debian/rules
+++ b/debian/rules
@@ -20,6 +20,7 @@ endif
 override_dh_auto_configure:
 	dh_auto_configure -- \
 		-DDOCS=$(BUILDDOC) \
+		-DCMAKE_BUILD_RPATH_USE_ORIGIN=ON \
 		-DPYTHON=ON
 
 # https://github.com/AcademySoftwareFoundation/Imath/issues/226
-- 
2.34.1



signature.asc
Description: PGP signature

Bug#1003806: Acknowledgement (firefox-esr: Screen tearing (diagonal line) when scrolling web pages)

[Matt Roberds]

I Googled and found this Reddit post, by Reddit user Shamaoke, from
June 2021:

https://old.reddit.com/r/firefox/comments/nq5dy2/ff_89_tearing/

They were using Firefox 89 on Arch, but since they also reported screen
tearing, I decided to try their fixes.  The first fix they reported
worked:


Update 1: It seems that for some reason Firefox WebRender doesn't work
correctly on my machine. Since it is enabled by default starting with
Firefox 89, I have to disable it by using the
gfx.webrender.force-disabled = true about:config setting while
preserving layers.acceleration.force-enabled = true. After that tearing
has disappeared.


I changed those two settings in about:config in Firefox and the problem
stopped happening - I can scroll web pages without observing the tearing
anymore.

Since the need for changing those settings might depend on what window
manager / X server / video driver / video card you have, here are the
versions I have installed of possibly-relevant packages, from dpkg:

ii  xfce4  4.12.5
ii  xfce4-panel4.12.2-1
ii  xfce4-session  4.12.1-6
ii  xfce4-settings 4.12.4-1
ii  xfce4-xkb-plugin   1:0.8.1-2
ii  xfconf 4.12.1-1
ii  xfwm4  4.12.5-1
ii  xserver-common 2:1.20.4-1+deb10u4
ii  xserver-xorg   1:7.7+19
ii  xserver-xorg-core  2:1.20.4-1+deb10u4
ii  xserver-xorg-video-all 1:7.7+19
ii  xserver-xorg-video-radeon  1:19.0.1-1

Here is what "lspci -v" says about my video card:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar 
[Radeon HD 5000/6000/7350/8350 Series] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Cedar [Radeon HD 5000/6000/7350/8350 Series]
  Flags: bus master, fast devsel, latency 0, IRQ 33
  Memory at e000 (64-bit, prefetchable) [size=256M]
  Memory at f7de (64-bit, non-prefetchable) [size=128K]
  I/O ports at dc00 [size=256]
  Expansion ROM at 000c [disabled] [size=128K]
  Capabilities: [50] Power Management version 3
  Capabilities: [58] Express Legacy Endpoint, MSI 00
  Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
  Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 
  Capabilities: [150] Advanced Error Reporting
  Kernel driver in use: radeon
  Kernel modules: radeon

What I think Debian should do:

If it's possible to detect the need for these settings at install time
(based on what window manager is installed, or what X says it supports),
the Firefox package should adjust those settings as needed after it
installs Firefox.

A difficulty there is that I'm pretty sure the about:config settings are
unique to each Firefox profile.  Since there may be many Firefox profiles
on the system, the installer would have to look for and change them all.

If it's not possible or not a good idea to set this up at install time,
perhaps having WebRender disabled should be the default in the Firefox
package.  However, this may cause lower graphics performance in Firefox
for users that have software and hardware that supports WebRender
correctly.

Other notes:

Shamaoke also reported a few other things in their Reddit post which
probably don't directly affect this bug, but might be useful in the
future.  In particular, one of the settings changes names at Firefox 92:


Update 2: Apparently WebRender doesn't work in window managers which
don't support composition. To enable it, you will need to install
additional software, e. g. picom. Only after installing and running
the compositor, you'll be able to use WebRender in Firefox.



Update 3: In FF 92 the layers.acceleration.force-enabled setting was
removed. The gfx.webrender.force-legacy-layers = true setting should
be used instead of it. This setting will change the rendering method
form WebRender to OpenGL. Go to about:support > Graphics > Features >
Compositing to check what rendering method is being used by the
browser.


Thanks!

Matt Roberds

Bug#1003807: libopenjp2-7-dev: broken symlinks: libopenjp3d.so -> libopenjp3d.so.7, libopenjpip.so -> libopenjpip.so.7

[Paul Wise]

Package: libopenjp2-7-dev
Version: 2.4.0-5
Severity: normal
File: /usr/lib/x86_64-linux-gnu/libopenjp3d.so
File: /usr/lib/x86_64-linux-gnu/libopenjpip.so
User: debian...@lists.debian.org
Usertags: adequate broken-symlink
Tags: patch

libopenjp2-7-dev 2.4.0-5 introduced two broken symlinks.

It looks like the usual .so symlinks were added without a dependency
on the two packages that provide the targets of those symlinks.

This means that reverse dependencies of libopenjp2-7-dev will not be
able to link against libopenjp3d or libopenjpip.

Since there are no packages in Debian that link against libopenjp3d or
libopenjpip this isn't a major issue, hence filed at normal severity.

So I think that the fix for this is to update the depends:

   -Depends: libopenjp2-7 (= ${binary:Version}), ${misc:Depends}
   +Depends: libopenjp2-7 (= ${binary:Version}), libopenjpip7 (= 
${binary:Version}), libopenjp3d7 (= ${binary:Version}), ${misc:Depends}

Alternatively all the files for linking libopenjp3d and libopenjpip
could be split into separate -dev packages for each library.

Here is some more information about the broken symlinks:

   Log started: 2022-01-15  12:01:35
   apt-listchanges: Reading changelogs...
   apt-listchanges: Mailing root: apt-listchanges: changelogs for chianamo
   apt-listchanges: Reading changelogs...
   Preparing to unpack .../libopenjp2-7-dbgsym_2.4.0-5_amd64.deb ...
   Unpacking libopenjp2-7-dbgsym:amd64 (2.4.0-5) over (2.4.0-3) ...
   Preparing to unpack .../libopenjp2-7-dev_2.4.0-5_amd64.deb ...
   Unpacking libopenjp2-7-dev:amd64 (2.4.0-5) over (2.4.0-3) ...
   Preparing to unpack .../libopenjp2-7_2.4.0-5_amd64.deb ...
   Unpacking libopenjp2-7:amd64 (2.4.0-5) over (2.4.0-3) ...
   Setting up libopenjp2-7:amd64 (2.4.0-5) ...
   Setting up libopenjp2-7-dbgsym:amd64 (2.4.0-5) ...
   Setting up libopenjp2-7-dev:amd64 (2.4.0-5) ...
   Processing triggers for man-db (2.9.4-4) ...
   Processing triggers for libc-bin (2.33-2) ...
   Log ended: 2022-01-15  12:02:03
   
   $ adequate libopenjp2-7-dev 
   libopenjp2-7-dev:amd64: broken-symlink 
/usr/lib/x86_64-linux-gnu/libopenjp3d.so -> libopenjp3d.so.7
   libopenjp2-7-dev:amd64: broken-symlink 
/usr/lib/x86_64-linux-gnu/libopenjpip.so -> libopenjpip.so.7
   
   $ ls -l /usr/lib/x86_64-linux-gnu/*openjp*.so*
   lrwxrwxrwx 1 root root   15 Jan 14 23:18 
/usr/lib/x86_64-linux-gnu/libopenjp2.so -> libopenjp2.so.7
   -rw-r--r-- 1 root root 367K Jan 14 23:18 
/usr/lib/x86_64-linux-gnu/libopenjp2.so.2.4.0
   lrwxrwxrwx 1 root root   19 Jan 14 23:18 
/usr/lib/x86_64-linux-gnu/libopenjp2.so.7 -> libopenjp2.so.2.4.0
   lrwxrwxrwx 1 root root   16 Jan 14 23:18 
/usr/lib/x86_64-linux-gnu/libopenjp3d.so -> libopenjp3d.so.7
   lrwxrwxrwx 1 root root   16 Jan 14 23:18 
/usr/lib/x86_64-linux-gnu/libopenjpip.so -> libopenjpip.so.7
   
   $ chase /usr/lib/x86_64-linux-gnu/*openjp*.so*
   /usr/lib/x86_64-linux-gnu/libopenjp2.so.2.4.0
   /usr/lib/x86_64-linux-gnu/libopenjp2.so.2.4.0
   /usr/lib/x86_64-linux-gnu/libopenjp2.so.2.4.0
   chase: /usr/lib/x86_64-linux-gnu/libopenjp3d.so.7: No such file or directory
   chase: /usr/lib/x86_64-linux-gnu/libopenjpip.so.7: No such file or directory
   
   $ apt-cache show libopenjp2-7-dev=2.4.0-5 | grep Depends
   Depends: libopenjp2-7 (= 2.4.0-5)
   
   $ apt-file search libopenjp3d.so.7
   libopenjp3d7: /usr/lib/x86_64-linux-gnu/libopenjp3d.so.7
   
   $ apt-file search libopenjpip.so.7
   libopenjpip7: /usr/lib/x86_64-linux-gnu/libopenjpip.so.7

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

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

Versions of packages libopenjp2-7-dev depends on:
ii  libopenjp2-7  2.4.0-5

libopenjp2-7-dev recommends no packages.

libopenjp2-7-dev suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1003806: firefox-esr: Screen tearing (diagonal line) when scrolling web pages

[Matt Roberds]

Package: firefox-esr
Version: 91.5.0esr-1~deb10u1
Severity: normal

Dear Maintainer,

I recently upgraded from Firefox 78 ESR to 91.5.0 ESR.  After doing
that, I observed screen tearing in the browser window when scrolling a
web page.  I did not expect the tearing; I expected the web page to
scroll smoothly, as it did in 78 ESR.

The tear appeared for me as a diagonal line; it started at the upper
right corner of the web page display area and ran "southwest" (down and
to the left) to about the center of the web page display area.  The line
did not extend to the menus or toolbars in the browser; it was only
visible in the web page display area.

The tear only appeared when I was scrolling a web page that was taller
than the browser window.  It appeared when I was scrolling both up and
down.  It appeared both with using the mouse wheel to scroll, and using
the scroll bar at the side of the window to scroll.  The tear wasn't
"permanent" - when I stopped scrolling, everything on the web page
displayed correctly.

A good test case was any long Wikipedia page.  Scrolling such a page
made the tear visible on the lines of text or images on the page.

I Googled and found a solution (changing things in about:config), which
I will post as a follow-up.

Thanks!

Matt Roberds

-- Package-specific info:


-- Addons package information

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

Kernel: Linux 4.19.0-18-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages firefox-esr depends on:
ii  debianutils 4.8.6.1
ii  fontconfig  2.13.1-2
ii  libatk1.0-0 2.30.0-2
ii  libc6   2.28-10
ii  libcairo-gobject2   1.16.0-4+deb10u1
ii  libcairo2   1.16.0-4+deb10u1
ii  libdbus-1-3 1.12.20-0+deb10u1
ii  libdbus-glib-1-20.110-4
ii  libevent-2.1-6  2.1.8-stable-4
ii  libffi6 3.2.1-9
ii  libfontconfig1  2.13.1-2
ii  libfreetype62.9.1-3+deb10u2
ii  libgcc1 1:8.3.0-6
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.58.3-2+deb10u3
ii  libgtk-3-0  3.24.5-1
ii  libpango-1.0-0  1.42.4-8~deb10u1
ii  libstdc++6  8.3.0-6
ii  libx11-62:1.6.7-1+deb10u2
ii  libx11-xcb1 2:1.6.7-1+deb10u2
ii  libxcb-shm0 1.13.1-2
ii  libxcb1 1.13.1-2
ii  libxcomposite1  1:0.4.4-2
ii  libxdamage1 1:1.1.4-3+b3
ii  libxext62:1.3.3-1+b2
ii  libxfixes3  1:5.0.3-1
ii  libxrender1 1:0.9.10-1
ii  procps  2:3.3.15-2
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages firefox-esr recommends:
ii  libavcodec58  7:4.1.8-0+deb10u1

Versions of packages firefox-esr suggests:
ii  fonts-lmodern  2.004.5-6
ii  fonts-stix [otf-stix]  1.1.1-4
ii  libcanberra0   0.30-7
ii  libgssapi-krb5-2   1.17-3+deb10u3
pn  pulseaudio 

-- no debconf information

Bug#1003804: imath: reproducible-builds: BuildId differences triggered by RPATH

[Vagrant Cascadian]

Source: imath
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The RPATH contains the build path resulting in different buildid:

  https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/imath.html

The attached patch to debian/rules passes
-DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override,
which should use a relative path for RPATH.

Alternately, updating the packaging to debhelper compat level 14 should
fix this, although it is currently an experimental compat level.


There are still other outstanding reproducibility issues even with this
patch applied, but applying this patch should reduce the diff
significantly, allowing diffoscope runs on tests.reproducible-builds.org
to complete before timing out.


Thanks for maintaining imath!


live well,
  vagrant
From 28fa4ee3a093404e5bb38df628660a8c004f3666 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sat, 15 Jan 2022 23:00:25 +
Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via
 dh_auto_configure override.

This avoids embedding the full path in RPATH, which triggers BuildId
differences.

https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html
---
 debian/rules | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/rules b/debian/rules
index c66b57f..03cb3e7 100755
--- a/debian/rules
+++ b/debian/rules
@@ -20,6 +20,7 @@ endif
 override_dh_auto_configure:
 	dh_auto_configure -- \
 		-DDOCS=$(BUILDDOC) \
+		-DCMAKE_BUILD_RPATH_USE_ORIGIN=ON \
 		-DPYTHON=ON
 
 # https://github.com/AcademySoftwareFoundation/Imath/issues/226
-- 
2.34.1



signature.asc
Description: PGP signature

Bug#1003794: apt-listbugs: segmentation fault causing apt-listbugs to fail

[Brian Paterni]

On Sat, Jan 15, 2022 at 5:29 PM Francesco Poli 
wrote:

> On Sun, 16 Jan 2022 00:15:07 +0100 Francesco Poli wrote:
>
> [...]
> > Are you using a different Ruby interpreter than the one in the official
> > Debian package? Did you compile it from source, by chance?
>
> Oh, sorry, I got confused by the ruby package (which has version
> 1:2.7.6, but depends on ruby2.7): maybe you are just using ruby2.7
> version 2.7.5-1, which is the package currently in unstable.
>
> Is this the case?
>

That's correct, I've only ever (As far as I remember) had ruby installed
from distro packages. Never had a reason to compile ruby from source.

Bug#982055: dia Debian package and bug #982055

[François Mazen]

Hello Philippe and Nicolas,

I would be happy to help maintaining this package that I use regularly!
So feel free to ping me if help needed.

By the way, do you use a VCS where we could get the WIP package and
eventually contribute? Salsa [1] is usually the way to go.

Best Regards,
François

[1] : https://salsa.debian.org



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

Bug#1003803: paho.mqtt.c: reproducible-builds: BuildId differences triggered by RPATH

[Vagrant Cascadian]

Source: paho.mqtt.c
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The RPATH contains the build path resulting in different buildid:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/paho.mqtt.c.html

The attached patch to debian/rules passes
-DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override,
which should use a relative path for RPATH.

Alternately, updating the packaging to debhelper compat level 14 should
fix this, although it is currently an experimental compat level.


With this patch applied, paho.mqtt.c should build reproducibly on
tests.reproducible-builds.org!


Thanks for maintaining paho.mqtt.c!


live well,
  vagrant
From 20edacbf62c7869bc5461660313149644040773f Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sat, 15 Jan 2022 23:51:40 +
Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via
 dh_auto_configure override.

This avoids embedding the full path in RPATH, which triggers BuildId
differences.

https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 3acf17b..8c24767 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,7 +11,7 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 override_dh_auto_configure:
 	dh_auto_configure -- -DPAHO_WITH_SSL=TRUE -DPAHO_ENABLE_TESTING=FALSE \
-	-DPAHO_BUILD_STATIC=TRUE -DPAHO_BUILD_SAMPLES=TRUE
+	-DPAHO_BUILD_STATIC=TRUE -DPAHO_BUILD_SAMPLES=TRUE -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON
 
 override_dh_auto_install:
 	dh_auto_install
-- 
2.34.1



signature.asc
Description: PGP signature

Bug#1003120: git-lfs: After "git lfs install", "git push" doesn't work with an ssh key asking for a passphrase.

[Stephen Gelman]

On Jan 4, 2022 at 7:53:27 AM, Jean-Jacques Brucker <
jeanjacquesbruc...@gmail.com> wrote:

> "git push" was stuck asking forever the passphrase of my ssh key (even if
> I wrote it correcty).
>
> A workaround is to remove the passphrase (using "ssh-keygen -p"), but it
> is not an acceptable solution.
>
> It seems like a problem of closed or badly redirected stdin file
> descriptor.
>

I think there are two potential options here. The first option would be to
use an ssh-agent. If you add your key to the agent git-lfs will be able to
use it. The second option would be to install ssh-askpass and set the
SSH_ASKPASS environment variable so that it prompts you for your passphrase.

Stephen

Bug#1003802: upb: reproducible-builds: BuildId differences triggered by RPATH

[Vagrant Cascadian]

Source: upb
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The RPATH contains the build path resulting in different buildid:

  https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/upb.html

The attached patch to debian/rules passes
-DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override,
which should use a relative path for RPATH.

Alternately, updating the packaging to debhelper compat level 14 should
fix this, although it is currently an experimental compat level.


With this patch applied, upb should build reproducibly on
tests.reproducible-builds.org!


Thanks for maintaining upb!


live well,
  vagrant
From 19d90874187bb3cfc9bc41f68f085d587fd6d01f Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sat, 15 Jan 2022 23:43:37 +
Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via
 dh_auto_configure override.

This avoids embedding the full path in RPATH, which triggers BuildId
differences.

https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 10c5c7f..6aab9d8 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,7 +6,7 @@
 
 
 override_dh_auto_configure:
-	dh_auto_configure -- -DBUILD_SHARED_LIBS:BOOL=ON
+	dh_auto_configure -- -DBUILD_SHARED_LIBS:BOOL=ON -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON
 
 %:
 	dh $@
-- 
2.34.1



signature.asc
Description: PGP signature

Bug#1000138: /usr/bin/screen: command arguments beyond 62 silently discarded

[Axel Beckert]

Control: severity -1 important
Control: tag -1 + confirmed - patch

Hi Ian,

thanks for forwarding this issue.

I meant to reply quite a while ago, but in the end seem to have
forgotton to actually send it. Most of it was written already in the
beginning of December.

Ian Jackson wrote:
> Steps to reproduce and observed behaviour:
> 
>   $ cat t.sh
>   #!/bin/sh
>   echo $#
>   sleep 5
>   $ ./t.sh {0..999}
>   1000
>   $ screen ./t.sh {0..999}
>   [ displays 1000 and exits ]
>   $ screen screen ./t.sh {0..999}
>   [ displays 62 and exits ]
>   $
> 
> Expected behaviour: 1000 in all cases.

So this issue basically solely exists at startup. Or possibly if
someone types in more than 62 parameters manually at "Ctrl-A :screen"
(which I can't imagine that it really happens).

> This is a potential data loss bug so might justify even "grave" but I
> thought that was overkill.  I hope you will agree that this deserves
> an RC bug.

I thought about that a while (but didn't come to a conclusion quickly,
so I only started a few weeks after the bug report), but while I agree
that this is "data loss", the actual impact of this issue seems so
small that it IMHO does not deserve RC status.

I'm also not really happy with the attached patch (from your second
mail) and still undecided if I should really apply a patch that
deliberately causes a crash.

Then again, it might just be poorly named as it does not seem to cause
a crash (like a segmentation fault), just exiting in panic.

I'm removing the patch tag as the patch doesn't fix the issue but just
makes it more visible. 

> This has been reported upstream here:
>   https://savannah.gnu.org/bugs/?61504

Marked as forwarded, thanks. (Already did that back then after I saw
the bug report.)

Also note that upstream marked the bug report in Savannah as confirmed
as well. So there's hope that upstream finds a proper patch for it.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

[D.J.J. Ring, Jr.]

Is there anything else I can do to help solve this problem?

I just tried the last daily iso with firmware with no luck.

Also I've discussed the problem with GRUB inserting an entry in the EFI
boot automatically which overrides user setting in BIOS.  That means if I
last booted into Debian I will go directly to Debian without having the
ability to press F2 (or whatever key is needed to access BIOS settings)..
I mentioned that this caused a problem on a multi system boot, especially
for those of us who cannot see well, but  also for everyone because the
only way to change this is either to open up the computer or laptop and
reset the BIOS by pressing a rubber domed switch which I suppose grounds
the capacitor is there to  holds a voltage on the computer CMOS to keep
settings, pushing the little switch puts the voltage to zero and restore
the factory settings.

There is a problem and I'm trying to get someone to fix it.   It's probably
an unfortunate consequence of this "feature" - GRUB would work just right
without this feature, and I cannot think of any reason that this "feature"
exists. It appears to be a bug.  It's certainly understandable to those who
who must  now take extraordinary measures to reset their BIOS by resetting
the CMOS. For blind persons who have already obtained sighted help to et up
their BIOS the way they want it, to boot from USB HD - a USB stick, it's
totally unwanted and very inconvenient. I have no idea if GRUB is aware of
this bug.

I believe even if GRUB is intended to do this, it shouldn't, it seems to be
be an unfortunate consequence of their work.   Even if it can be
overridden, it is much too complicated for the average computer user.
(Some kind member of this list sent me instructions to override this new
behavior of GRUB, but they are extremely complicated. If anything this
"feature" should be enabled only as an option.  I've just subscribed to
GRUB bugs list to tell them of this, hopefully it can be fixed because it
overrides the user's BIOS settings.

Best wishes to all,
David


On Tue, Jan 4, 2022 at 2:54 PM D.J.J. Ring, Jr.  wrote:

> I have already done that, did it not go through? I did receive a message
> saying that the message I sent because it didn't mention a package would be
> disregarded.
> It would have been sent from n...@arrll.net - any way of checking
> further? Darn it,  I should have BCC it to you, Samuel.
>
> Thanks,
>
> David
>
> On Tue, Jan 4, 2022 at 3:53 AM Samuel Thibault 
> wrote:
>
>> Hello,
>>
>> As already mentioned, please do this:
>>
>> install with the Buster image, and use reportbug to send the
>> installation information, just like you did with Bullseye on Mon, 3 Jan
>> 2022 14:18:39 -0500.
>>
>> Really, do please do that.
>>
>> Samuel
>>
>

Bug#1003801: why3 FTBFS: Error: File graph.cmo not found

[Adrian Bunk]

Source: why3
Version: 1.4.0-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/why3.html

...
Linking  lib/plugins/hypothesis_selection.cmo
File "_none_", line 1:
Error: File graph.cmo not found
make[2]: *** [Makefile:591: lib/plugins/hypothesis_selection.cmo] Error 2

Bug#1003798: fluxbox: replace FbRootWindow::depth with maxDepth

[Phil Dibowitz]

Package: fluxbox
Version: 1.3.7-1~exp1
Severity: grave
Tags: patch upstream
Justification: renders package unusable

Dear Maintainer,

There is a bug in upstream fluxbox which has been patched which causes
new 32-bit windows to appear without borders, and unable to be
interacted with in anyway. This includes Firefox, Thunderbird and a
variety of other applications.

Large windows that cannot be moved, closed, or otherwise interacted with
renders fluxbox nearly useless.

There is an upstream patch:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=fluxbox

There is more discussion here:
https://sourceforge.net/p/fluxbox/bugs/1102/

and in this mozilla bug I had originally filed thinking it was a problem
over there:
https://bugzilla.mozilla.org/show_bug.cgi?id=1714353

Fluxbox has not released a new version, unfortunately, but if we could
apply this patch, that would be greatly appreciated.

Thanks!
- Phil

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

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

Versions of packages fluxbox depends on:
ii  libc62.33-1
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.11.1+dfsg-1
ii  libfribidi0  1.0.8-2
ii  libgcc-s1 [libgcc1]  11.2.0-12
ii  libimlib21.7.4-1
ii  libstdc++6   11.2.0-12
ii  libx11-6 2:1.7.2-2+b1
ii  libxext6 2:1.3.4-1
ii  libxft2  2.3.2-2
ii  libxinerama1 2:1.1.4-2
ii  libxpm4  1:3.5.12-1
ii  libxrandr2   2:1.5.2-1
ii  libxrender1  1:0.9.10-1
ii  menu 2.1.48

Versions of packages fluxbox recommends:
ii  feh  3.6.3-1
ii  xfonts-terminus  4.48-3.1

Versions of packages fluxbox suggests:
pn  fbautostart  
pn  fbdesk   
pn  fbpager  

-- no debconf information

Bug#1003797: libssreflect-coq: Depends: coq-8.14.0+4.11.1 but it is not installable

[Adrian Bunk]

Package: libssreflect-coq
Version: 1.13.0-1
Severity: serious

The following packages have unmet dependencies:
 libssreflect-coq : Depends: coq-8.14.0+4.11.1 but it is not installable

libssreflect-coq is binary-all, therefore requires a source upload.

Bug#1003796: ITP: ifupdown-ng -- network device manager compatible with ifupdown

[Daniel Gröber]

Package: wnpp
Severity: wishlist
Owner: Daniel Gröber 
X-Debbugs-Cc: debian-de...@lists.debian.org, d...@darkboxed.org

Hi,

* Package name: ifupdown-ng
  Version : 0.11.3
  Upstream Author : Ariadne Conill 
Maximilian Wilhelm 
* URL : https://github.com/ifupdown-ng/ifupdown-ng
* License : ISC
  Programming Lang: C, Shell
  Description : network device manager compatible with ifupdown

ifupdown-ng is a network device manager which is backwards compatible with
traditional ifup and ifdown as used on Debian and Alpine systems, while
solving many design deficits with the original approach through robust
error handling and the use of a dependency-solver to determine interface
bring-up order.

Unlike ifupdown2 (already in Debian) ifudown-ng's core is written in plain
C with "executors" written in Shell talking to the kernel and system
services, making it quite light yet easy to extend.

See also Maximilian Wilhelm's Debconf21 talk:
  
https://debconf21.debconf.org/talks/52-contemporary-networking-configuration-with-ifupdown-ng/

I plan on maintaining this package by myself, however I am looking for
a sponsor.

--Daniel

Bug#1003795: buster-pu: package evolution-data-server/3.30.5-1+deb10u2

[Adrian Bunk]

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

  * CVE-2020-16117: Crash on malformed server response with
minimal capabilities.
diff -Nru evolution-data-server-3.30.5/debian/changelog 
evolution-data-server-3.30.5/debian/changelog
--- evolution-data-server-3.30.5/debian/changelog   2020-07-14 
22:09:35.0 +0300
+++ evolution-data-server-3.30.5/debian/changelog   2022-01-16 
00:17:04.0 +0200
@@ -1,3 +1,11 @@
+evolution-data-server (3.30.5-1+deb10u2) buster; urgency=medium
+
+  * Non-maintainer upload.
+  * CVE-2020-16117: Crash on malformed server response with
+minimal capabilities.
+
+ -- Adrian Bunk   Sun, 16 Jan 2022 00:17:04 +0200
+
 evolution-data-server (3.30.5-1+deb10u1) buster-security; urgency=medium
 
   * CVE-2020-14928: Response Injection via STARTTLS in SMTP and POP3.
diff -Nru 
evolution-data-server-3.30.5/debian/patches/0001-I-189-Crash-on-malformed-server-response-with-minima.patch
 
evolution-data-server-3.30.5/debian/patches/0001-I-189-Crash-on-malformed-server-response-with-minima.patch
--- 
evolution-data-server-3.30.5/debian/patches/0001-I-189-Crash-on-malformed-server-response-with-minima.patch
 1970-01-01 02:00:00.0 +0200
+++ 
evolution-data-server-3.30.5/debian/patches/0001-I-189-Crash-on-malformed-server-response-with-minima.patch
 2022-01-16 00:16:26.0 +0200
@@ -0,0 +1,27 @@
+From 9e540466b1c84f492207d3e43749384cde73e46c Mon Sep 17 00:00:00 2001
+From: Milan Crha 
+Date: Mon, 10 Feb 2020 10:00:32 +0100
+Subject: I#189 - Crash on malformed server response with minimal capabilities
+
+Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/189
+---
+ src/camel/providers/imapx/camel-imapx-server.c | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/src/camel/providers/imapx/camel-imapx-server.c 
b/src/camel/providers/imapx/camel-imapx-server.c
+index 20bc160e4..65690f0d0 100644
+--- a/src/camel/providers/imapx/camel-imapx-server.c
 b/src/camel/providers/imapx/camel-imapx-server.c
+@@ -3049,7 +3049,8 @@ connected:
+ 
+   /* See if we got new capabilities
+* in the STARTTLS response. */
+-  imapx_free_capability (is->priv->cinfo);
++  if (is->priv->cinfo)
++  imapx_free_capability (is->priv->cinfo);
+   is->priv->cinfo = NULL;
+   if (ic->status->condition == IMAPX_CAPABILITY) {
+   is->priv->cinfo = ic->status->u.cinfo;
+-- 
+2.20.1
+
diff -Nru evolution-data-server-3.30.5/debian/patches/series 
evolution-data-server-3.30.5/debian/patches/series
--- evolution-data-server-3.30.5/debian/patches/series  2020-07-09 
15:27:45.0 +0300
+++ evolution-data-server-3.30.5/debian/patches/series  2022-01-16 
00:16:54.0 +0200
@@ -2,3 +2,4 @@
 ubuntu_gettext_domain.patch
 CVE-2020-14928-1.patch
 CVE-2020-14928-2.patch
+0001-I-189-Crash-on-malformed-server-response-with-minima.patch

Bug#1000896: Bug#997829: libipc-shareable-perl: autopkgtest regression on armhf and i386

[gregor herrmann]

On Mon, 25 Oct 2021 19:59:39 +0200, gregor herrmann wrote:

> I'm going the forward the bug upstream.

No reaction so far at https://github.com/stevieb9/ipc-shareable/issues/14

Failures are visible at
https://qa.debian.org/excuses.php?package=libipc-shareable-perl

And can easily be reproduced by building in an i386 chroot.

After some looking at the the code I have no idea what's broken
there.
Anyone else?


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#1003794: apt-listbugs: segmentation fault causing apt-listbugs to fail

[Brian Paterni]

Package: apt-listbugs
Version: 0.1.36
Severity: important
X-Debbugs-Cc: bpate...@gmail.com

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

Recently upon apt upgrade, apt-listbugs sometimes fails. This time it failed
due to a segmentation fault that spit out a bunch of info.

Please see the following for details surrounding the segmentation fault.

Thanks!



/usr/lib/ruby/vendor_ruby/aptlistbugs/logic.rb:1359: [BUG] Segmentation fault
at 0x0034612d
ruby 2.7.5p203 (2021-11-24 revision f69aeb8314) [x86_64-linux-gnu]

-- Control frame information ---
c:0006 p: s:0044 e:43 CFUNC  :width
c:0005 p:0025 s:0039 e:36 METHOD
/usr/lib/ruby/vendor_ruby/aptlistbugs/logic.rb:1359
c:0004 p:0021 s:0031 e:30 BLOCK  /usr/bin/apt-listbugs:594
c:0003 p:0142 s:0026 e:25 METHOD
/usr/lib/ruby/vendor_ruby/aptlistbugs/logic.rb:1104
c:0002 p:0527 s:0016 E:001fe0 EVAL   /usr/bin/apt-listbugs:593 [FINISH]
c:0001 p: s:0003 E:001290 (none) [FINISH]

-- Ruby level backtrace information 
/usr/bin/apt-listbugs:593:in `'
/usr/lib/ruby/vendor_ruby/aptlistbugs/logic.rb:1104:in `create'
/usr/bin/apt-listbugs:594:in `block in '
/usr/lib/ruby/vendor_ruby/aptlistbugs/logic.rb:1359:in `progress'
/usr/lib/ruby/vendor_ruby/aptlistbugs/logic.rb:1359:in `width'

-- Machine register context 
 RIP: 0x7f1346555b37 RBP: 0x5556b90d4138 RSP: 0x7fff61e88980
 RAX: 0x RBX: 0x0052 RCX: 0x5556ba8c4a40
 RDX: 0x7fff61e889d0 RDI: 0x00346125 RSI: 0x00a5
  R8: 0x5556ba8c4a50  R9: 0x7f134638bc00 R10: 0x0002
 R11: 0x R12: 0x00346125 R13: 0x7fff61e889d0
 R14: 0x0052 R15: 0x00a5 EFL: 0x00010202

-- C level backtrace information ---
/usr/lib/x86_64-linux-gnu/libruby-2.7.so.2.7(0x7f13465cec9a) [0x7f13465cec9a]
/usr/lib/x86_64-linux-gnu/libruby-2.7.so.2.7(0x7f134643eb07) [0x7f134643eb07]
/usr/lib/x86_64-linux-gnu/libruby-2.7.so.2.7(0x7f134654b7a9) [0x7f134654b7a9]
/lib/x86_64-linux-gnu/libc.so.6(0x7f134620a910) [0x7f134620a910]
/usr/lib/x86_64-linux-gnu/libruby-2.7.so.2.7(rb_st_lookup+0x17)
[0x7f1346555b37]
/usr/lib/x86_64-linux-gnu/libruby-2.7.so.2.7(rb_hash_aref+0x59)
[0x7f1346469399]
/usr/lib/x86_64-linux-
gnu/ruby/vendor_ruby/2.7.0/unicode/unicode_native.so(get_unidata+0x18)
[0x7f1341d83ed8]
/usr/lib/x86_64-linux-
gnu/ruby/vendor_ruby/2.7.0/unicode/unicode_native.so(unicode_wcswidth+0x1a7)
[0x7f1341d84287]
/usr/lib/x86_64-linux-gnu/libruby-2.7.so.2.7(0x7f13465b46d2) [0x7f13465b46d2]
/usr/lib/x86_64-linux-gnu/libruby-2.7.so.2.7(0x7f13465a8fd6) [0x7f13465a8fd6]
/usr/lib/x86_64-linux-gnu/libruby-2.7.so.2.7(0x7f13465b8a3b) [0x7f13465b8a3b]
/usr/lib/x86_64-linux-gnu/libruby-2.7.so.2.7(rb_vm_exec+0x1bb) [0x7f13465be8bb]
/usr/lib/x86_64-linux-gnu/libruby-2.7.so.2.7(0x7f1346442c00) [0x7f1346442c00]
/usr/lib/x86_64-linux-gnu/libruby-2.7.so.2.7(ruby_run_node+0x48)
[0x7f13464470d8]
/usr/bin/ruby(0x5556b716910b) [0x5556b716910b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xcd) [0x7f13461f57ed]
/usr/bin/ruby(_start+0x2a) [0x5556b716915a]

-- Other runtime information ---

* Loaded script: /usr/bin/apt-listbugs

* Loaded features:

0 enumerator.so
1 thread.rb
2 rational.so
3 complex.so
4 ruby2_keywords.rb
5 /usr/lib/x86_64-linux-gnu/ruby/2.7.0/enc/encdb.so
6 /usr/lib/x86_64-linux-gnu/ruby/2.7.0/enc/trans/transdb.so
7 /usr/lib/x86_64-linux-gnu/ruby/2.7.0/rbconfig.rb
8 /usr/lib/ruby/vendor_ruby/rubygems/compatibility.rb
9 /usr/lib/ruby/vendor_ruby/rubygems/defaults.rb
   10 /usr/lib/ruby/vendor_ruby/rubygems/deprecate.rb
   11 /usr/lib/ruby/vendor_ruby/rubygems/errors.rb
   12 /usr/lib/ruby/vendor_ruby/rubygems/exceptions.rb
   13 /usr/lib/ruby/vendor_ruby/rubygems/basic_specification.rb
   14 /usr/lib/ruby/vendor_ruby/rubygems/stub_specification.rb
   15 /usr/lib/ruby/vendor_ruby/rubygems/text.rb
   16 /usr/lib/ruby/vendor_ruby/rubygems/user_interaction.rb
/usr/lib/ruby/vendor_ruby/aptlistbugs/logic.rb:1359: [BUG] Segmentation fault
at 0x0034612d
ruby 2.7.5p203 (2021-11-24 revision f69aeb8314) [x86_64-linux-gnu]

-- Control frame information ---
c:0006 p: s:0044 e:43 CFUNC  :width
c:0005 p:0025 s:0039 e:36 METHOD
/usr/lib/ruby/vendor_ruby/aptlistbugs/logic.rb:1359
c:0004 p:0021 s:0031 e:30 BLOCK  /usr/bin/apt-listbugs:594
c:0003 p:0142 s:0026 e:25 METHOD
/usr/lib/ruby

Bug#1003783: /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead.

[gregor herrmann]

Control: reassign -1 ucf
Control: merge 1001011 -1

On Sun, 16 Jan 2022 04:07:02 +0800, 積丹尼 Dan Jacobson wrote:

> Package: libxml-libxml-perl
> Version: 2.0207+dfsg-2
> 
> Preparing to unpack .../8-libxml-libxml-perl_2.0207+dfsg-2_amd64.deb ...
> update-perl-sax-parsers: Unregistering Perl SAX parser 
> XML::LibXML::SAX::Parser with priority 50...
> update-perl-sax-parsers: Unregistering Perl SAX parser XML::LibXML::SAX with 
> priority 50...
> update-perl-sax-parsers: Updating overall Perl SAX parser modules info file...
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in 
> scripts instead.
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in 
> scripts instead.

`which' does not come from libxml-libxml-perl, but from
libxml-sax-perl's update-perl-sax-parsers; which also doesn't contain
any call to `which' but it uses ucf. Cf. #993654

Updating the bug metadata accordingly …


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#1003793: [PATCH] lesspipe; lesspipe.1: consistency, cleanup, #995948, #720520; rewrite, #988570

[наб]

On Sat, Jan 15, 2022 at 10:55:00PM +0100, наб wrote:
> Attached, you'll find patches, applying to less-590-1,
> that improve consistency, fix some bugs, and rewrite the manual.

If I had more than two functional brain-cells I wouldn't've forgotten to
actually attach them; soz.

Please consider the patches below :)

наб
Date: Sat, 15 Jan 2022 02:58:08 +0100
From: наб 
Subject: lesspipe: modernise

This patch applies the following trivial transformations:
  * replaces all `s with $(s
  * replaces [ -x `which CMD` ] (???) with command -v CMD >/dev/null
(command -v is now in base XSH;
 which is undergoing a Debian-wide pruning and spews errors
 (though those are swallowed by the 2>/dev/null))
  * properly escapes escapes which are meant to be escapes but aren't
(e.g. in iso_list)
  * wraps variable subsititutions in ""s
  * drops needless TMPDIR and umask
for superfluous mktemp instrumentation
  * makes redirects consistently unspaced and at EOL
  * fixes all space indents
  * simplifies BASENAME and FULLPATH,
as directed by "please send me a patch"
  * reformats the case entries for consistency:
  1. just compressor/just archiver as
   if CMD; then CMD $1
   else echo no CMD; fi ;;
  2. pipeline as
   if CMD; then
  CMD $1 | tar tvvf -
   else echo no CMD; fi ;;
  3. others left as-were
  * and fixes spurious end-of-sentence in lesspipe.1

---
debian/lesspipe   +79 -108
debian/lesspipe.1 +1  -1

--- less-590.orig/debian/lesspipe
+++ less-590/debian/lesspipe
@@ -17,23 +17,22 @@
 # throughout the code.  If you don't want lessfile to be called that,
 # you'll need to change the LESSFILE envar below.
 #
-# Usage: eval `lessfile`  or eval `lesspipe`
+# Usage: eval "$(lessfile)"  or eval "$(lesspipe)"
 #
 # less passes in:
 #$1  filename to be viewed with less  (used by LESSOPEN)
 # and possibly (if used by lessfile)
 #$2  filename that was created during LESSOPEN
 
-TMPDIR=${TMPDIR:-/tmp}
 CONFIGDIR=${XDG_CONFIG_HOME:-~/.config}
-BASENAME=`basename $0`
+BASENAME=${0##*/}
 LESSFILE=lessfile
 
 # Helper function to list contents of ISO files (CD images)
 iso_list() {
 	isoinfo -d -i "$1"
-	isoinfo -d -i "$1" | grep -q ^Rock\.Ridge && iiopts="$iiopts -R"
-	isoinfo -d -i "$1" | grep -q ^Joliet && iiopts="$iiopts -J"
+	isoinfo -d -i "$1" | grep -q '^Rock\.Ridge' && iiopts="$iiopts -R"
+	isoinfo -d -i "$1" | grep -q '^Joliet' && iiopts="$iiopts -J"
 	echo
 	isoinfo -f $iiopts -i "$1"
 }
@@ -47,12 +46,11 @@ if [ $# -eq 1 ] ; then
 	fi
 
 	# generate filename for possible use by lesspipe
-	umask 077
-	if [ $BASENAME = $LESSFILE ]; then
-		TMPFILE=`mktemp -p $TMPDIR lessfXX`
+	if [ "$BASENAME" = "$LESSFILE" ]; then
+		TMPFILE=$(mktemp -t lessfXX)
 		if [ -z "$TMPFILE" ]; then
-			echo >&2 "TMPFILE variable is empty. Exiting"
-		exit 1
+			echo "TMPFILE variable is empty. Exiting" >&2
+			exit 1
 		fi
 	fi
 
@@ -65,17 +63,17 @@ if [ $# -eq 1 ] ; then
 			USERFILTER=~/.lessfilter
 		fi
 		if [ -n "$USERFILTER" ]; then
-			if [ $BASENAME = $LESSFILE ]; then
-"$USERFILTER" "$1" > $TMPFILE
+			if [ "$BASENAME" = "$LESSFILE" ]; then
+"$USERFILTER" "$1" >"$TMPFILE"
 if [ $? -eq 0 ]; then
-	if [ -s $TMPFILE ]; then
-		echo $TMPFILE
+	if [ -s "$TMPFILE" ]; then
+		echo "$TMPFILE"
 	else
-		rm -f $TMPFILE
+		rm -f "$TMPFILE"
 	fi
 	exit 0
 else
-	rm -f $TMPFILE
+	rm -f "$TMPFILE"
 fi
 			else
 "$USERFILTER" "$1" && exit 0
@@ -83,29 +81,29 @@ if [ $# -eq 1 ] ; then
 		fi
 
 		# possibly redirect stdout to a file for lessfile
-		if [ $BASENAME = $LESSFILE ]; then exec > $TMPFILE; fi
+		if [ "$BASENAME" = "$LESSFILE" ]; then exec >"$TMPFILE"; fi
 
 		# Decode file for less
-		case `echo "$1" | tr '[:upper:]' '[:lower:]'` in
+		case "$(echo "$1" | tr '[:upper:]' '[:lower:]')" in
 			*.a)
-if [ -x "`which ar`" ]; then ar tv "$1"
+if command -v ar >/dev/null; then ar tv "$1"
 else echo "No ar available"; fi ;;
 
 			*.arj)
-if [ -x "`which unarj`" ]; then unarj l "$1"
+if command -v unarj >/dev/null; then unarj l "$1"
 else echo "No unarj available"; fi ;;
 
 			*.tar.bz2)
-if [ -x "`which bunzip2`" ]; then
+if command -v bunzip2 >/dev/null; then
 	bunzip2 -dc "$1" | tar tvvf -
 else echo "No bunzip2 available"; fi ;;
 
 			*.bz)
-if [ -x "`which bunzip`" ]; then bunzip -c "$1"
+if command -v bunzip >/dev/null; then bunzip -c "$1"
 else echo "No bunzip available"; fi ;;
 
 			*.bz2)
-if [ -x "`which bunzip2`" ]; then bunzip2 -dc "$1"
+if command -v bunzip2 >/dev/null; then bunzip2 -dc "$1"
 else echo "No bunzip2 available"; fi ;;
 
 			*.deb|*.udeb|*.ddeb|*.ipk)
@@ -115,20 +113,20 @@ if [ $# -eq 1 ] ; then
 ;;
 
 			*.doc)
-if [ -x "`which catdoc`" ]; then
+if command -v catdoc >/dev/null; then
 	catdoc "$1"
 else
 	# no catdoc, read normally if file is text.
-	if ( file "$1" | grep ASCI

Bug#1003793: lesspipe; lesspipe.1: consistency, cleanup, #995948, #720520; rewrite, #988570

[наб]

Source: less
Version: 590-1
Severity: normal
Tags: patch

Dear Maintainer,

Hi!

Attached, you'll find patches, applying to less-590-1,
that improve consistency, fix some bugs, and rewrite the manual.
There was also a long-standing TODO note, which I fixed.

Details in commit messages. The bug numbers in the title is what
reportbug gave me when filtering for lesspipe and, from their titles,
I assume this also fixes.

Best,
наб

-- System Information:
Debian Release: 11.2
  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-10-amd64 (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information


signature.asc
Description: PGP signature

Bug#1003792: postfix: milter_header_checks does not find /usr/lib/postfix/postfix-pcre.so

[Jens Metschkoll]

Package: postfix
Version: 3.5.6-1+b1
Severity: normal

Dear Maintainer,

i have the following problem: postfix does not find 
/usr/lib/postfix/postfix-pcre.so when i call a pcre file via 
milter_header_checks. It is the same error as described in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845750#60

The following steps (as Bartosz wrote) solved the issue:

1. Change master.cf:

Original: "cleanup   unix  n   -   y   -   0   cleanup"
Changed: "cleanup   unix  n   -   n   -   0   cleanup"

2. "chmod o+x /etc/postfix/"

3. Restart postfix

I think pcre in milter_header_checks should work out of the box whithout making 
these changes.

Greetings

Jens


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

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

Versions of packages postfix depends on:
ii  adduser3.118
ii  cpio   2.13+dfsg-4
ii  debconf [debconf-2.0]  1.5.77
ii  dpkg   1.20.9
ii  e2fsprogs  1.46.2-2
ii  libc6  2.31-13+deb11u2
ii  libdb5.3   5.3.28+dfsg1-0.8
ii  libicu67   67.1-7
ii  libnsl21.3.0-2
ii  libsasl2-2 2.1.27+dfsg-2.1
ii  libssl1.1  1.1.1k-1+deb11u1
ii  lsb-base   11.1.0
ii  netbase6.3
ii  ssl-cert   1.1.0+nmu1

Versions of packages postfix recommends:
ii  ca-certificates  20210119
ii  python3  3.9.2-3

Versions of packages postfix suggests:
ii  dovecot-core [dovecot-common]  1:2.3.13+dfsg1-2
ii  libsasl2-modules   2.1.27+dfsg-2.1
pn  mail-reader
pn  postfix-cdb
pn  postfix-doc
pn  postfix-ldap   
pn  postfix-lmdb   
ii  postfix-mysql  3.5.6-1+b1
ii  postfix-pcre   3.5.6-1+b1
pn  postfix-pgsql  
pn  postfix-sqlite 
pn  procmail   
ii  resolvconf 1.87
ii  ufw0.36-7.1

-- debconf information:
  postfix/root_address:
  postfix/mailbox_limit: 0
  postfix/protocols:
  postfix/relayhost:
  postfix/mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
  postfix/chattr: false
* postfix/main_mailer_type: No configuration
  postfix/mailname: /etc/mailname
  postfix/kernel_version_warning:
  postfix/procmail:
  postfix/mydomain_warning:
  postfix/tlsmgr_upgrade_warning:
  postfix/bad_recipient_delimiter:
  postfix/relay_restrictions_warning:
  postfix/main_cf_conversion_warning: true
  postfix/rfc1035_violation: false
  postfix/sqlite_warning:
  postfix/compat_conversion_warning: true
  postfix/dynamicmaps_conversion_warning:
  postfix/destinations:
  postfix/recipient_delim: +
  postfix/retry_upgrade_warning:
  postfix/lmtp_retired_warning: true
  postfix/not_configured:
  postfix/newaliases: false

Bug#1003791: elinks: upstream project seems dead - please switch to fork felinks

[Jonas Smedegaard]

Package: elinks
Version: 0.13.2-1+b2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Upstream project is inactive for more than 10 years.

Perhaps makes sense to switch to the active fork at
https://github.com/rkd77/elinks

Kind regards,

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmHjQYwACgkQLHwxRsGg
ASFSPA//ff7uj81Rk3kQN8H0fElUVGJfzH43r1i7TJgDQvTglore1/ThC6tAflKr
rZo7VmV/9SrMx0GXrCGoyNOsZwoa8yUeDt9WNw/w75+gd2UCBhpWyc/s2APbkk50
UOJH9FFNfZJhqyVgxhmfCApAeARIzY8mrNiGn+pOAnawScnIbCuEdVlJTh0Wl5aO
pza2wnCbG+ruROZ7+5Uh4wP5abABqEiHe9Xl3QEIV21hApFDfh9dtAQvlbM8ogJ7
LKGRfrOwlI8AyrPNfgs7N/NBNpVxX/H+O2j4EwjUs/+ZjVrq6C5XlOfbwyyH+M1M
qMSLd4tbFy0HeIhszJSp9d6CPpnuLP6eNkE/qgGdmLK5UZkXKyz5PfLKuGYcNlPw
YwemfBvgCb7S1qqEC3/anvClo07fa/Y2Oc+gVXluzCLRM0KzM8YBtywZVe2dkJ0q
o48ZnP0Y8sXpw1y+IuSDQzPG/UD1XLFbhkWIcXkoZo4Do9Sh3zkMEYvTK8OqU9At
gzlzx/ZCFblVXVoPgOOIxbNeiRD/PTNppvGFpGItsgge75aE5UDMPAS8rie1AVSz
+LulupoHTnlBkieltYYsdcxMKQfOh+E4rRgYDrXMcOXILUs17YdNzRvekavCwqI1
UMDliimuxJFi4R/a+Btuq3SEm+AFoDY7EUTzSSpvwfVbaxHoXLI=
=qPMM
-END PGP SIGNATURE-

Bug#986227: Update packages to recent version

[Phil Morrell]

Control: retitle -1 ITP: paperless-ng -- scan, index and archive all your 
physical documents
Control: owner -1 Mechtilde Stehmann 
thanks

On Thu, Jan 13, 2022 at 09:25:14PM +0100, Mechtilde Stehmann wrote:
> I intend to package paperless-ng.
> 
> Many of its dependencies are packaged in Debian but in an older version. You
> can see the list at
> https://salsa.debian.org/mechtilde/paperless-ng/-/wikis/home

Thanks for working on this, I currently use it on my home system and
would be interested in testing a packaged version.


signature.asc
Description: PGP signature

Bug#1003790: dart: FTBFS on i386: test_SkelParser hangs

[Andreas Beckmann]

Package: dart
Version: 6.12.1+dfsg4-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

dart/experimental FTBFS on i386 due to a hanging test:

https://buildd.debian.org/status/fetch.php?pkg=dart&arch=i386&ver=6.12.1%2Bdfsg4-3&stamp=1642208825&raw=0

[...]
34: [==] 8 tests from 1 test suite ran. (5623 ms total)
34: [  PASSED  ] 8 tests.
61/62 Test #34: test_Issue1193    Passed5.64 sec
E: Build killed with signal TERM after 150 minutes of inactivity

I could reproduce this locally and found the process
/build/dart-6.12.1+dfsg4/.pybuild/cpython3_3.10/build/unittests/unit/test_SkelParser
running and eating 100% of a cpu core.


Andreas

Bug#1003789: golang-github-libgit2-git2go-v32: missing Build-Depends: tzdata

[Andreas Beckmann]

Source: golang-github-libgit2-git2go-v32
Version: 32.1.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

golang-github-libgit2-git2go-v32 FTBFS in a minimal chroot without
tzdata (which is neither build-essential nor pulled in by any build
dependency).

...
=== RUN   TestApplyDiffAddfile
index_test.go:281: Fail at 
/build/golang-github-libgit2-git2go-v32-32.1.4/obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v32/git_test.go:97;
 unknown time zone Europe/Berlin
--- FAIL: TestApplyDiffAddfile (0.00s)
=== RUN   TestApplyToTree
index_test.go:281: Fail at 
/build/golang-github-libgit2-git2go-v32-32.1.4/obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v32/git_test.go:97;
 unknown time zone Europe/Berlin
--- FAIL: TestApplyToTree (0.00s)
...

There are a lot more tests failing with the same error...

(With tzdata installed everything works fine.)


Andreas

Bug#1003788: sunxi-tools: please build newer snapshot supporting more platforms and 64bit boot

[Jonas Smedegaard]

Package: sunxi-tools
Version: 1.4.2+git20181114.6d598a-3
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Several exciting improvements has landed since the now more than 3 years
old snapshot currently packaged.

Please package a newer snapshot to detect more boards and features, and
to support booting FIT images in Aarch64 mode.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmHjNngACgkQLHwxRsGg
ASH5xRAAhoddOU5Nl8U4DRhYzRzTSCuBS1SYFzLWybe9IPwCRcJRwV1mbVTyoQGH
1Yy5EulTqQ7/4cBNd9tBsFnfzQ6Aiou9b7ZGQ1l0/To2eJKWbAqyKhBYXrHIwzcR
yOJYyA+45KBgdDgM16XYPx1t8CrPftQcoKMoaAO5/lhdorgp9kQHTUn6cKhNFKh8
C+X05tyKla5YXzlpgJan17iwHiXDcbVrMETMfW37+h3M6gVtSzEU3ij2IvDLwZ4F
OtGMgwuvwrkfOIGzdLWgtDsF6jdq7oAcgwRC1HG+6JSHBUOzMSfnSKpkQF3/9mjo
9YmQ+hjegzg95cHHYSSzIKJyop4Sr9KCeorQPsHuf/isJM6n4qbrYiuZre45JMpe
hXIB98SoB0zPw3M172DEEPjEU8o6X8OUCE2o6h+ok57Np8nFE93wlMgzOtq4Vnv9
sLhrhtNMaAXhKMYwXU4Gwb9jMNLJ4/hdWpeG2i9q3pkLn+AbYUdljJcrvnYU9Xvm
BOFymrXHY8sULQZ6pTwmcibTlq02ddiZqhk34KRu/PEa7e5UetYOmQbTtfOd9Fjb
0YczxxTJFjFtN+UkBsnK+gSrA+u0IWK+L37AdMNRg44xk/xjYgek+1N4m0OHXWKS
tTzIziltXKOoT7+b33j4L5H+mk2LP55Qbuklf7FRwlnzS9mYQvg=
=RROY
-END PGP SIGNATURE-

Bug#1003787: pesign: reproducible-builds: build path embedded in include

[Vagrant Cascadian]

Source: pesign
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

pesign does not appear to build reproducibly in unstable due to build
paths (which is not varied in testing/bookworm):

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/pesign.html

This appears due to an include directory that embeds the full path.


The attached patch fixes this by passing a relative path to the include
directory in Make.defaults.


With this patch applied, pesign should build reproducibly on
tests.reproducible-builds.org!


Thanks for maintaining pesign!

live well,
  vagrant
From f5cb0d11f73a3b3b6b6c58b8f96ebb3da58bf5d0 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sat, 15 Jan 2022 20:43:57 +
Subject: [PATCH] Make.defaults: Use relative path to include dir.

This allows for reproducible builds even when the build path differs
between two builds.

https://reproducible-builds.org/docs/build-path/
---
 Make.defaults | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Make.defaults b/Make.defaults
index c97b452..9986da9 100644
--- a/Make.defaults
+++ b/Make.defaults
@@ -40,7 +40,7 @@ cflags	= $(CFLAGS) $(ARCH3264) \
 	-Wno-unused-function\
 	-std=gnu11 -fshort-wchar -fPIC -flto -fno-strict-aliasing \
 	-fno-merge-constants -fkeep-inline-functions \
-	-D_GNU_SOURCE -DCONFIG_$(ARCH) -I${TOPDIR}/include \
+	-D_GNU_SOURCE -DCONFIG_$(ARCH) -I../include \
 	$(if $(filter $(CC),clang),$(clang_cflags), ) \
 	$(if $(filter $(CC),gcc),$(gcc_cflags), ) \
 	$(call pkg-config-cflags) -Werror
-- 
2.34.1



signature.asc
Description: PGP signature

Bug#1003786: bat: missing source for syntaxes/themes.

[peter green]

Package: bat
Severity: serious

While checking on the testing migration of rust source packages I noticed that
librust-bat-dev was uninstallable because the old version of syntect did not
offer all the required features. When I started looking at the issue I noticed
there was a new version of bat.

I started working on packaging the new upstream of bat, unfortunately while 
investigating
the changes to debian/copyright.debcargo.hint, I discovered a problem.
tests/integration_tests.rs had references to copyright holders that did not 
appear to
be mentioned anywhere else in the source code.

Following the trail, it appears the syntaxes and themes are included in the 
source package
in binary form in syntaxes.bin and themes.bin, but their sources are not 
included, they
are merely referenced by a .gitmodules file.

Does anyone have any thoughts on the best way to sort this out?

I have held off uploading the new version of bat (and performed a fix upload 
for the version
currently in Debian instead) so we have freedom in the content of the orig 
tarball when
sorting this out.

Bug#984063: Closing bug (Was: Bug#984063: itk libtiff test issues (Was: Bug#984063))

[Andreas Tille]

Hi Bas,

Am Sat, Jan 15, 2022 at 08:30:26PM +0100 schrieb Sebastiaan Couwenberg:
> > Insighttoolkit4 will be removed from Debian.  We are now building
> > insighttoolkit5 and do not support insighttoolkit4 any more.
> 
> Good to know.
> 
> OTB won't support ITK5 for quite a while, though:
> 
>  https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/merge_requests/528
> 
> Removing itk4 will be difficult with rdeps still depending on it.
> 
> There is no RM bug for insighttoolkit4 yet,

Steve simply bumped the version right in d/changelog[1]

> when you file one feel free to
> file one for otb as well and have it block the one for itk4, but please CC
> pkg-grass-de...@lists.alioth.debian.org when you do.

IMHO it would be sad to loose OTB.  When I once started looking at the
packaging upstream was quite responsive.  Did you discussed the issue?

Kind regards

   Andreas.


[1] 
https://salsa.debian.org/med-team/insighttoolkit/-/blob/master/debian/changelog 

-- 
http://fam-tille.de

Bug#1003785: gmerlin: FTBFS: format not a string literal and no format arguments

[Andreas Beckmann]

Source: gmerlin
Version: 1.2.0+svn6244~dfsg0-1~exp1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

gmerlin/experimental recently started to FTBFS after some toolchain
package or build dependency was updated (probably when the default
compiler was switched to GCC 11):

frontend_player_ncurses.c: In function 'draw_status':
frontend_player_ncurses.c:164:5: error: format not a string literal and no 
format arguments [-Werror=format-security]
  164 | mvwprintw(p->player_win, 2, p->win_w - 4, status_str);
  | ^


Andreas


gmerlin_1.2.0+svn6244~dfsg0-1~exp1.log.gz
Description: application/gzip

Bug#1001545: pyopencl, build-depends on package that is no longer in testing

[Andreas Beckmann]

Control: severity -1 normal

pocl is back in testing

On 12/01/2022 20.33, Rebecca N. Palmer wrote:
Probably just Build-Depends: pocl-opencl-icd [amd64 arm64 armel armhf 
i386 hurd-i386] and skip the tests on the other architectures.  (Linking 
uses libopencl1, not *-opencl-icd.)


I'll keep this bug open for improving the tests and dependencies.
I won't go away from pocl first - it has caused enough autopkgtest 
regressions in the past ;-) But using mesa as an alternative would allow 
building pyopencl on more platforms even if it has (probably) no test 
coverage (due to lack of gpu hardware), yet.


Andreas

Bug#1003784: php-horde-wicked: (autopkgtest) needs update for php8.1: Text_Wiki_Parse_Paragraph::process(): Argument #1 ($matches) must be passed by reference, value given

[Paul Gevers]

Source: php-horde-wicked
Version: 2.0.8-8
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults
Control: block 976811 by -1


Dear maintainer(s),

We are in the transition of replacing php7.4 with php8.1 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-wicked fails 
in testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing92
php-horde-wicked   from testing2.0.8-8
versioned deps from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php list the changes since 
7.4 and may help to identify what needs to be updated.


php-commom added a whole set of versioned Breaks to make sure the right 
packages from current unstable are pulled in during testing. If the 
issue is caused by a missing breaks, please reasign this bug to php-common.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] https://bugs.debian.org/976811
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-wicked/18338271/log.gz

PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.1.1
Configuration: 
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/test/Wicked/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/test/Wicked/Unit/Driver/SqlTest.php
   Class name was 'Wicked_Unit_Driver_SqlTest', expected 
'SqlTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/test/Wicked/Unit/RstTest.php

   Class name was 'Wicked_Unit_RstTest', expected 'RstTest'

EE34 / 
34 (100%)


Time: 00:00.016, Memory: 6.00 MB

There were 22 errors:

1) Wicked_Unit_RstTest::testEmpty
Text_Wiki_Parse_Paragraph::process(): Argument #1 ($matches) must be 
passed by reference, value given


/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/lib/Text_Wiki/Text/Wiki/Parse.php:155
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/lib/Text_Wiki/Text/Wiki.php:949
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/lib/Text_Wiki/Text/Wiki.php:909
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/test/Wicked/Unit/RstTest.php:51

2) Wicked_Unit_RstTest::testHeaderOne
Text_Wiki_Parse_Heading::process(): Argument #1 ($matches) must be 
passed by reference, value given


/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/lib/Text_Wiki/Text/Wiki/Parse.php:155
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/lib/Text_Wiki/Text/Wiki.php:949
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/lib/Text_Wiki/Text/Wiki.php:909
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/test/Wicked/Unit/RstTest.php:63

3) Wicked_Unit_RstTest::testHeaderTwo
Text_Wiki_Parse_Heading::process(): Argument #1 ($matches) must be 
passed by reference, value given


/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/lib/Text_Wiki/Text/Wiki/Parse.php:155
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/lib/Text_Wiki/Text/Wiki.php:949
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/lib/Text_Wiki/Text/Wiki.php:909
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/test/Wicked/Unit/RstTest.php:75

4) Wicked_Unit_RstTest::testHeaderThree
Text_Wiki_Parse_Heading::process(): Argument #1 ($matches) must be 
passed by reference, value given


/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/lib/Text_Wiki/Text/Wiki/Parse.php:155
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/lib/Text_Wiki/Text/Wiki.php:949
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/lib/Text_Wiki/Text/Wiki.php:909
/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/test/Wicked/Unit/RstTest.php:86

5) Wicked_Unit_RstTest::testHeaderFour
Text_Wiki_Parse_Heading::process(): Argument #1 ($matches) must be 
passed by reference, value given


/tmp/autopkgtest-lxc.cuoy_m84/downtmp/build.jOz/src/wicked-2.0.8/l

Bug#1003783: /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead.

[積丹尼 Dan Jacobson]

Package: libxml-libxml-perl
Version: 2.0207+dfsg-2

Preparing to unpack .../8-libxml-libxml-perl_2.0207+dfsg-2_amd64.deb ...
update-perl-sax-parsers: Unregistering Perl SAX parser XML::LibXML::SAX::Parser 
with priority 50...
update-perl-sax-parsers: Unregistering Perl SAX parser XML::LibXML::SAX with 
priority 50...
update-perl-sax-parsers: Updating overall Perl SAX parser modules info file...
/usr/bin/which: this version of `which' is deprecated; use `command -v' in 
scripts instead.
/usr/bin/which: this version of `which' is deprecated; use `command -v' in 
scripts instead.

Setting up libxml-libxml-perl (2.0207+dfsg-2) ...
update-perl-sax-parsers: Registering Perl SAX parser XML::LibXML::SAX::Parser 
with priority 50...
update-perl-sax-parsers: Registering Perl SAX parser XML::LibXML::SAX with 
priority 50...
update-perl-sax-parsers: Updating overall Perl SAX parser modules info file...
/usr/bin/which: this version of `which' is deprecated; use `command -v' in 
scripts instead.
/usr/bin/which: this version of `which' is deprecated; use `command -v' in 
scripts instead.

Bug#1003775: ansible-mitogen: not working with ansible from experimental

[stefanor]

Hi Reiner (2022.01.15_17:40:48_+)
> In the update you also added a dependency on ansible << 2.13.
> Unfortunately this is no longer installable with ansible from
> experimental, because the packaging has recently changed there.
> src:ansible-core now contains the ansible binaries (2.12.0 currently)
> and src:ansible contains the collections, which is versioned with
> 4.6.0-1 in experimental.

Ah, right, I forgot about that split.

> Can you please update the dependency to allow newer ansible versions,
> but keep the << 2.13 restriction for ansible-core?

For backportability and smooth upgrades, I think I'll make the Depends:
ansible-core (<< 2.13) | ansible (<< 2.13)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1003781: Edict-el: deprecated macro syntax (w/ patch).

[abegui]

Package: edict-el
Version: 1.06-11.1
Tags: patch

Calling 'M-x edict-search-kanji' produces no visible result, and the following 
error message:

eval-buffer: Loading ‘/usr/share/emacs/site-lisp/edict-el/edict-morphology.el’: 
old-style backquotes detected!


Apparently, elisp has an old and new syntax for quoting within macros, and 
starting with Emacs 27 the old syntax is no longer supported.

Only the file 'edict-morphology.el' is affected, in a short fragment between 
lines 274 and 276. Despite my poor understanding of lisp macros, I could swear 
I have produced a patch that fixes it.

Because I'm inexperienced in submitting bugs and the patch is short, I shall 
reproduce it in text here, lest the attachment fail to make it through.

274,276c274,276
< (` (define-edict-rule-internal '(, name) '(, pattern) '(, filter)
<'(, from) '(, to)
<(function (, function)) (quote ((,@ additional-args)))
---
> `(define-edict-rule-internal (quote ,name) (quote ,pattern) (quote 
> ,filter)
>(quote ,from) (quote ,to)
>(function ,function) (quote (,@additional-args)
274,276c274,276
< (` (define-edict-rule-internal '(, name) '(, pattern) '(, filter)
< 	 '(, from) '(, to)
< 	 (function (, function)) (quote ((,@ additional-args)))
---
> `(define-edict-rule-internal (quote ,name) (quote ,pattern) (quote ,filter)
> 	 (quote ,from) (quote ,to)
> 	 (function ,function) (quote (,@additional-args)

Bug#1003782: ITP: megan-ce -- interactive tool to explore and analyse microbiome sequencing data

[Pierre Gruet]

Package: wnpp
Severity: wishlist
Owner: Debian-med team 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-...@lists.debian.org

* Package name: megan-ce
  Version : 6.21.1
  Upstream Author : Daniel Huson 
* URL : https://github.com/danielhuson/megan-ce
* License : GPL-3+
  Programming Lang: Java
  Description : interactive tool to explore and analyse microbiome 
sequencing data

MEGAN Community Edition is a shotgun sequencer to analyze microbiome samples.
It is a rewrite and extension of the widely-used microbiome analysis tool
MEGAN so as to facilitate the interactive analysis of the taxonomic and
functional content of very large microbiome datasets. Other new features
include a functional classifier called InterPro2GO, gene-centric read
assembly, principal coordinate analysis of taxonomy and function, and support
for metadata.  By integrating MEGAN CE with the high-throughput DNA-to-protein
alignment tool DIAMOND a powerful and complete pipeline for the analysis of
metagenome shotgun sequences can be provided.

megan-ce will be team-maintained by Debian-med team.

Bug#984063: Closing bug (Was: Bug#984063: itk libtiff test issues (Was: Bug#984063))

[Sebastiaan Couwenberg]

On 1/15/22 20:11, Andreas Tille wrote:

Am Sat, Jan 15, 2022 at 06:45:11PM +0100 schrieb Sebastiaan Couwenberg:

On Mon, 10 Jan 2022 16:58:42 +0100 Andreas Tille wrote:

This bug has been fixed in the meantime.


insighttoolkit4 still FTBFS with GCC 11:

  error: ISO C++17 does not allow dynamic exception specifications

The same error as in the original buildlog.


Insighttoolkit4 will be removed from Debian.  We are now building
insighttoolkit5 and do not support insighttoolkit4 any more.


Good to know.

OTB won't support ITK5 for quite a while, though:

 https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/merge_requests/528

Removing itk4 will be difficult with rdeps still depending on it.

There is no RM bug for insighttoolkit4 yet, when you file one feel free 
to file one for otb as well and have it block the one for itk4, but 
please CC pkg-grass-de...@lists.alioth.debian.org when you do.


Kind Regards,

Bas

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

Bug#1003622: chromium: microphone stopped working after upgrade

[Andres Salomon]

On 1/15/22 13:53, Francesco Poli wrote:

On Sat, 15 Jan 2022 13:20:23 -0500 Andres Salomon wrote:


On 1/15/22 12:58, Francesco Poli wrote:

[...]

ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library 
libasound_module_pcm_jack.so 
(/usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_jack.so: cannot open 
shared object file: Permission denied)

Please take into account that I use the jack sound server (which
however works flawlessly with chromium/93.0.4577.82-1 and with other
applications that use the mic).

What version of libasound2-plugins do you have installed? If you don't
have it installed, please install it and try again.

   $ apt policy libasound2-plugins
   libasound2-plugins:
 Installed: 1.2.5-2
 Candidate: 1.2.5-2
 Version table:
1.2.6-1 500
   500 http://deb.debian.org/debian unstable/main amd64 Packages
*** 1.2.5-2 800
   800 http://deb.debian.org/debian testing/main amd64 Packages
   100 /var/lib/dpkg/status

Are you aware of some incompatibility of chromium/97.0.4692.71-0.1 with
any version of libasound2-plugins?
Other applications (including chromium/93.0.4577.82-1) work with
libasound2-plugins/1.2.5-2 ...

Should I try with libasound2-plugins/1.2.6-1 ?


Before you change anything, just do a "debsums libasound2-plugins|grep 
-v OK" and also just "ls -lah /usr/lib/x86_64-linux-gnu/alsa-lib/" just 
to make sure there's no weird corruption or filesystem permission 
oddities happening.


Then, you can try libasound2-plugins 1.2.6 (and if that doesn't work, 
1.2.2 from stable). You may need to restart sound daemons after 
upgrading. I'm not sure if you'll also need to upgrade libasound2 or not 
at the same time, but you could try different variations and see what 
does and doesn't work.

Bug#1003780: Weechat scripts fail to parse due to mixed indentation.

[abegui]

Package: weechat-scripts
Version: 20200815-1

Some of the Python scripts included in the package mix spaces and tabs
within the same block, causing a parse error. The offending files and
lines follow.

Tabs used among mostly spaces:

/usr/share/weechat/python/chanstat.py  663-664
/usr/share/weechat/python/ichatts.py  50-56, 92

Spaces used among mostly tabs:

/usr/share/weechat/python/mplayer.py  63, 66, 75, 80-82, 87
/usr/share/weechat/python/queue.py  277-278


Only with queue.py, I have confirmed that switching to uniform
indentation solves the issue, as one would expect.

There are other files in the collection that mix indentation styles,
but none within the same block, so they should be safe. For the record,
however, here is a list of all files that contain both types of
indentation (obtained with grep, contains false positives):

/usr/share/weechat/python/arespond.py
/usr/share/weechat/python/autosort.py
/usr/share/weechat/python/chanstat.py
/usr/share/weechat/python/grep_filter.py
/usr/share/weechat/python/ichatts.py
/usr/share/weechat/python/ircrypt.py
/usr/share/weechat/python/latex_unicode.py
/usr/share/weechat/python/mplayer.py
/usr/share/weechat/python/queue.py
/usr/share/weechat/python/snotify.py
/usr/share/weechat/python/spotify_nowplaying.py
/usr/share/weechat/python/tinyurl.py

Bug#984063: Closing bug (Was: Bug#984063: itk libtiff test issues (Was: Bug#984063))

[Andreas Tille]

Am Sat, Jan 15, 2022 at 06:45:11PM +0100 schrieb Sebastiaan Couwenberg:
> reopen -1
> 
> On Mon, 10 Jan 2022 16:58:42 +0100 Andreas Tille wrote:
> > > > This bug has been fixed in the meantime.
> 
> insighttoolkit4 still FTBFS with GCC 11:
> 
>  error: ISO C++17 does not allow dynamic exception specifications
> 
> The same error as in the original buildlog.

Insighttoolkit4 will be removed from Debian.  We are now building
insighttoolkit5 and do not support insighttoolkit4 any more.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#1003779: RFP: ffsubsync -- Language-agnostic automatic synchronization of subtitles with video, so that subtitles are aligned to the correct starting point within the video.

[shirish शिरीष]

Package: wnpp
Severity: wishlist

* Package name: ffsubsync
  Version : 0.4.17
  Upstream Author : Stephen Macke 
* URL : https://github.com/smacke/ffsubsync
* License : (MIT)
  Programming Lang: (Python2-3.)
  Description : Language-agnostic automatic synchronization of
subtitles with video, so that subtitles are aligned to the correct
starting point within the video.

(Include the long description here.)

Please also include as much relevant information as possible.
For example, consider answering the following questions:
 - why is this package useful/relevant? is it a dependency for
   another package? do you use it? if there are other packages
   providing similar functionality, how does it compare?
 - how do you plan to maintain it? inside a packaging team
   (check list at https://wiki.debian.org/Teams)? are you
   looking for co-maintainers? do you need a sponsor?


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/


E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Bug#1003778: libiksemel: new upstream home (or at least place to cherry-pick from)

[Jonas Smedegaard]

Source: libiksemel
Version: 1.4-3
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Project seems dead upstream.

Most active fork seems to be https://github.com/Zaryob/iksemel

Maybe switch to use that as upstream source and Homepage URI?
Or if not, then at least looks like a relevant source for cherry-picking
patches from.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmHjGdwACgkQLHwxRsGg
ASHBXQ//dWIEkilktafQqm0LeBrFyRRfXPvJ2bQLbuWGIo5O4cIp4Ztv3bVJp9hG
m7zIB8TY3PEcT8ay7JAFpQ9kvNGMujYxJpCvIoAjAdwp80NakdrnCR1n3XKXAdyC
2jSbnXIdn1NwHlZoVB1jVlellN8Xf/S1tWbEryOYa4CUPGwdbF3L6jzuIQ+bz+jD
fkk6jUJJGk647n+gQ6DLHRMPdoz/gitNX+lIkoJasxIUMQdv3hDbrj8zHPa2Dk/M
WPVnaTkMKdfeOde5mQupSDTquXSfdNx01WrNj2h6KTVK9WETTFpLkt4rLjUSW1yG
eqOR2ZzJQQ+1+VGyzN+QJDTa+jmsguXWDLT8KG6E6DblxW10dg+lfctpAXxCK0ig
U2H0f8VZ89EHlo2R4Co5HS4YlcpfWc8dfiq1elDcm5hkVFAaOAUa3tAsHq0lV712
v9jaaSOVryzw28xnFxWiY53gAQZ8K9PpxeYk5QWlc42W+BUZxjUyX6E3p4rM/QvG
JQCLvDnc5a/09GAPCUde3fZ77SG7/e1Niv8WvBCKp4W5bK7q1UBtThqW0B60j265
HPbjoIETqfHTWB1yRTeSe8mxFyGv8O0wnVHx7theqG3FlZaZpTMhAUgYVjn5BBsA
m8zAE+g1gP5RT0KlJxvVHs2D7qf7AV6QXR6MKTVzlmQuiPUy3w0=
=vmWW
-END PGP SIGNATURE-

Bug#1003777: mdevctl: Missing /etc/mdevctl.d/ directory

[Martin Otzen]

Package: mdevctl
Version: 1.1.0-1
Severity: normal
Tags: d-i

Dear Maintainer,

Please take a look at mdevctl issue on github [1]

Quote from cohuck's answer
"Can you check whether /etc/mdevctl.d/ exists? (The rpm spec file takes 
care of

it, not sure how the Debian packaging does it.)"

I can confirm that the deb installer does not create this folder on my
installation.


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

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.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 mdevctl depends on:
ii libc6 2.33-1
ii libgcc-s1 11.2.0-13
ii udev 249.7-1

mdevctl recommends no packages.

mdevctl suggests no packages.

-- no debconf information

--
 |
   @(~Ô^Ô~)@
-oOo---U---oOo-
| |
| Ing.|
|  Martin A. Otzen|
| |
| "klogest er den som ved,|
|  hvad han ikke ved" |
| Ooo |
|_ooO(   )|
 (   )) /
  \ ((_/
   \_)

Bug#1001593: php-easyrdf: diff for NMU version 1.0.0-2.1

[Adrian Bunk]

Control: tags 1001593 + patch
Control: tags 1001593 + pending

Dear maintainer,

I've prepared an NMU for php-easyrdf (versioned as 1.0.0-2.1) and 
uploaded it to DELAYED/2. Please feel free to tell me if I should
cancel it.

cu
Adrian
diff -Nru php-easyrdf-1.0.0/debian/changelog php-easyrdf-1.0.0/debian/changelog
--- php-easyrdf-1.0.0/debian/changelog	2021-02-10 17:03:28.0 +0200
+++ php-easyrdf-1.0.0/debian/changelog	2022-01-15 20:45:23.0 +0200
@@ -1,3 +1,11 @@
+php-easyrdf (1.0.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply patch from Christian Ehrhardt to fix flaky autopkgtest.
+(Closes: #1001593)
+
+ -- Adrian Bunk   Sat, 15 Jan 2022 20:45:23 +0200
+
 php-easyrdf (1.0.0-2) unstable; urgency=medium
 
   * Change gbp to use debian/bullseye for the maintenance branch
diff -Nru php-easyrdf-1.0.0/debian/tests/rapper.sh php-easyrdf-1.0.0/debian/tests/rapper.sh
--- php-easyrdf-1.0.0/debian/tests/rapper.sh	2021-01-19 05:44:42.0 +0200
+++ php-easyrdf-1.0.0/debian/tests/rapper.sh	2022-01-15 20:45:08.0 +0200
@@ -6,6 +6,15 @@
 php --server localhost:10101 --docroot debian/tests/data &
 SERVER_PID=$!
 
+# the startup can be racy making the test a false-positive
+# wait up to 10 seconds until it is ready
+r=0
+until [ "$r" -ge 100 ]; do
+nc -z localhost 10101 && echo "PRE: Connection ready" && break
+sleep 0.1
+echo "PRE: Retry Connection"
+done
+
 # A graphviz source file can be created.
 php debian/tests/rapper.php > sample.dot
 

Bug#1003776: backintime: version 1.3.1 is available from upstream but not recognized bei debian/watch

[Sven Geuer]

Source: backintime
Version: 1.2.1-3
Severity: normal

Dear Maintainer,

Upstream meanwhile released versions 1.3.0 and 1.3.1 but the pattern in
debian/watch is to specific for uscan to detect these, the prefix 'v' to the
version number has been dropped.

Please see the attached patch for a fix.

Please package version 1.3.1.


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

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/watch b/debian/watch
index 1ff675b..604ae98 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,2 +1,2 @@
 version=4
-https://github.com/bit-team/backintime/releases 
.*/v(\d\S*)/backintime-\1\.tar\.(?:gz|bz2|xz)
+https://github.com/bit-team/backintime/releases 
.*/v?(\d\S*)/backintime-\1\.tar\.(?:gz|bz2|xz)

Bug#994278: Chromium freezes (rarely) and partially locks up my WM (xfce4)

[Leandro Cunha]

On Sat, Jan 15, 2022 at 1:03 PM Craig Sanders  wrote:
>
> On Tue, Jan 11, 2022 at 03:33:21PM -0500, Andres Salomon wrote:
> > On Wed, 15 Sep 2021 11:29:48 +1000 Craig Sanders wrote:
> > > Package: chromium
> > > Version: 90.0.4430.212-1
>
> > Can you please tell me if you see this with chromium 97 or above? This
> > sounds like a bug related to X11 API usage (ie, grabbing window focus and
> > not letting go). We switched backends to ozone (which should be better
> > supported), and I'm curious if it still occurs with ozone-x11.
>
> 97?  Is that in experimental?  Latest in sid is 93.0.4577.82-1

No, this version (97) is in sid and stable-security now.
97.0.4692.71 is the current version.

-- 
Cheers,
Leandro Cunha

Bug#1003622: chromium: microphone stopped working after upgrade

[Andres Salomon]

On 1/15/22 12:58, Francesco Poli wrote:
[...]

# Test 1

I start chromium and join a meet.jit.si meeting.
I fail to enable the mic, other users do not hear me, I do not hear
them.
All available microphones are seen as non-working (see the attached
screenshot).
What is sent to stderr is attached.
I think the most important error message is:

   ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library 
libasound_module_pcm_jack.so 
(/usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_jack.so: cannot open 
shared object file: Permission denied)

Please take into account that I use the jack sound server (which
however works flawlessly with chromium/93.0.4577.82-1 and with other
applications that use the mic).


What version of libasound2-plugins do you have installed? If you don't 
have it installed, please install it and try again.

Bug#984063: Closing bug (Was: Bug#984063: itk libtiff test issues (Was: Bug#984063))

[Sebastiaan Couwenberg]

reopen -1

On Mon, 10 Jan 2022 16:58:42 +0100 Andreas Tille wrote:

Am Mon, Jan 10, 2022 at 05:25:59PM +0200 schrieb Adrian Bunk:
> On Sat, Dec 11, 2021 at 04:02:09PM +0100, Étienne Mollier wrote:
> > About the build error I caught with itk4 on , this
> > looks to be caused by a gcc bug in the headers files [1],
> > causing failures to build source code including  with
> > clang, compiler which is in use through castxml, which in turn
> > is used for constructing the wrapper ITKCommonBase.  itk5 dsc is
> > not affected as wrappers are not built anymore on its side, so
> > disabling wrappers for itk4 too might be a viable option while
> > #1000398 is being worked on (to at least reproduce the tiff test
> > failures).  The build error may otherwise solve by itself with
> > an upcoming gcc version.
> > 
> > [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000398

> >...
> 
> This bug has been fixed in the meantime.


insighttoolkit4 still FTBFS with GCC 11:

 error: ISO C++17 does not allow dynamic exception specifications

The same error as in the original buildlog.

Kind Regards,

Bas

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

Bug#1003771: Not (properly?) wrapping the stat call

[Shachar Shemesh]

  
  
Are you sure this is a problem?


Fakeroot cannot wrap the open syscall. As a result, it has no way
  of knowing whether a file was created before or after fakeroot was
  run. To compensate for that, it treats all unknown files as owned
  by root.


Fakeroot-ng does wrap the open syscall, and thus does not do
  that. A file will only be shown as owned by root if it was created
  through fakeroot-ng. This is the intended behavior, as it more
  closely matches that or running as real root.



Please verify that this is still a bug.


On 15/01/2022 17:16, Christoph Biedl
  wrote:


  Package: fakeroot-ng
Version: 0.18-4.1
Severity: normal

Dear maintainer,

while working on #1001961 in fakeroot, I noticed the stat() call is not
properly wrapped by fakeoot-ng, and appearently never did - I checked
back to Debian 8 ("jessie").

Reproducer: Build the program below and run under either fakeroot or
fakeroot-ng.

Expected output (observed with fakeroot):

I: UID is 0, '.' is owned by 0
I: Pass

Received output:

I: UID is 0, '.' is owned by 1000
E: UID mismatch


While I haven't checked it, this should also break the python-apt
autopkgtest if it were run using fakeroot-ng instead of fakeroot.
See the bug# mentioned above for an explanation.

To me, it seems prudent to add this to have feature parity.

Regards,

Christoph

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

Kernel: Linux 5.10.89 (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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fakeroot-ng depends on:
ii  libc6   2.33-2
ii  libgcc-s1   11.2.0-14
ii  libstdc++6  11.2.0-14

fakeroot-ng recommends no packages.

fakeroot-ng suggests no packages.

-- no debconf information


-
#include 
#include 
#include 
#include 
#include 

int main (int argc, char **argv) {
struct stat statbuf;
if (stat (".", &statbuf)) {
perror("Cannot stat '.'");
exit(1);
}
uid_t uid = getuid();
printf("I: UID is %u, '.' is owned by %u\n", uid, statbuf.st_uid);
if (uid == statbuf.st_uid) {
if (uid) {
printf("W: UID is not zero - not running under fakeroot?\n");
} else {
printf("I: Pass\n");
}
} else {
printf("E: UID mismatch\n");
}
}
-



  

Bug#1003775: ansible-mitogen: not working with ansible from experimental

[Reiner Herrmann]

Package: ansible-mitogen
Version: 0.3.1-1

Dear maintainer,

thanks for updating ansible-mitogen which is now compatible with newer
ansible releases.
In the update you also added a dependency on ansible << 2.13.
Unfortunately this is no longer installable with ansible from
experimental, because the packaging has recently changed there.
src:ansible-core now contains the ansible binaries (2.12.0 currently)
and src:ansible contains the collections, which is versioned with
4.6.0-1 in experimental.

Can you please update the dependency to allow newer ansible versions,
but keep the << 2.13 restriction for ansible-core?

Kind regards,
  Reiner


signature.asc
Description: PGP signature

Bug#988423: Repeatable crash when doing VP9 simulcast

[Juliusz Chroboczek]

>> Chromium crashes immediately when attempting VP9 simulcast. To reproduce, go 
>> to
>> 
>> https://janus-legacy.conf.meetecho.com/echotest.html?simulcast2=true&vcodec=vp9

> I just tried this on sid and bullseye with v97 and it didn't crash.

I couldn't reproduce the issue with 97.0.4692.71-0.1.  Thanks for getting
back to me.

Bug#1003774: bind9-host: Incorrect formatting in host.1 man page

[Ondřej Surý]

Hi Adam,

thanks for the patch, but it cannot be used as the host.rst needs to be fixed. 
The man page is generated using sphinx-build from the rst source.

Ondřej 
--
Ondřej Surý  (He/Him)

> On 15. 1. 2022, at 17:45, Adam Dinwoodie 
>  wrote:
> 
> Package: bind9-host
> Version: 1:9.17.21-1
> Severity: minor
> Tags: patch
> 
> Dear Maintainer,
> 
> The man page at host.1 in this package has an error in the formatting
> for the description of the `-l` option; for me it renders as below (I've
> added *s to indicate the bits in bright white):
> 
>This option tells *named` to list the zone, meaning the ``host*
>command performs a zone ...
> 
> I rather suspect it should instead be rendered as below:
> 
>This option tells *named* to list the zone, meaning the *host*
>command performs a zone ...
> 
> I've verified that the attached patch resolves this.
> 
> -- System Information:
> Distributor ID:Raspbian
> Description:Raspbian GNU/Linux 11 (bullseye)
> Release:11
> Codename:bullseye
> Architecture: armv7l
> 
> Kernel: Linux 5.10.63-v7l+ (SMP w/4 CPU threads)
> Kernel taint flags: TAINT_CRAP
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages bind9-host depends on:
> ii  bind9-libs  1:9.17.21-1
> ii  libc6   2.32-4+rpi1
> ii  libidn2-0   2.3.0-5
> 
> bind9-host recommends no packages.
> 
> bind9-host suggests no packages.
> 
> -- no debconf information


diff.diff
Description: Binary data

Bug#1003774: bind9-host: Incorrect formatting in host.1 man page

[Adam Dinwoodie]

Package: bind9-host
Version: 1:9.17.21-1
Severity: minor
Tags: patch

Dear Maintainer,

The man page at host.1 in this package has an error in the formatting
for the description of the `-l` option; for me it renders as below (I've
added *s to indicate the bits in bright white):

This option tells *named` to list the zone, meaning the ``host*
command performs a zone ...

I rather suspect it should instead be rendered as below:

This option tells *named* to list the zone, meaning the *host*
command performs a zone ...

I've verified that the attached patch resolves this.

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
Architecture: armv7l

Kernel: Linux 5.10.63-v7l+ (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bind9-host depends on:
ii  bind9-libs  1:9.17.21-1
ii  libc6   2.32-4+rpi1
ii  libidn2-0   2.3.0-5

bind9-host recommends no packages.

bind9-host suggests no packages.

-- no debconf information
diff --git a/doc/man/host.1in b/doc/man/host.1in
index 4d419423e..a94f12ae0 100644
--- a/doc/man/host.1in
+++ b/doc/man/host.1in
@@ -77,7 +77,7 @@ found for the zone.
 This option prints debugging traces, and is equivalent to the \fB\-v\fP 
verbose option.
 .TP
 .B \fB\-l\fP
-This option tells \fBnamed\(ga to list the zone, meaning the \(ga\(gahost\fP 
command performs a zone transfer of zone
+This option tells \fBnamed\fP to list the zone, meaning the \fBhost\fP command 
performs a zone transfer of zone
 \fBname\fP and prints out the NS, PTR, and address records (A/).
 .sp
 Together, the \fB\-l \-a\fP options print all records in the zone.

Bug#1003773: aerc: please update Homepage (and probably debian/copyright URIs as well)

[Jonas Smedegaard]

Package: aerc
Version: 0.7.1-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Homepage is listed as https://aerc-mail.org which points to
https://git.sr.ht/~sircmpwn/aerc for its source and currently lists
0.5.2 as its latest release.

But the Debian package mysteriously has 0.7.0 as latest release - how?

Seems the package tracks a fork of aerc at
https://git.sr.ht/~rjarry/aerc - please reflect that in the various
packaging metadata (I only checked and got mislead by the Homepage URI -
don't know if other hints like those in debian/copyright are similarly
misleading).

Kind regards, and thanks for maintaining this wonderful piece of code,

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmHi9kcACgkQLHwxRsGg
ASECFw/9HCSWSLGn5rzqlm27w4XPn870F6M8KsCHaUPY78AVljDmapVagXRXaoxD
q4k5Nq7uTgIi+089VcDnUdqgWNuF0a6PjitqjUDxPEzmYpYI3fUZRHGazqqThHxV
hkCXvVh4gPrk4+GeQZ3knXfK5Ns8lAGiHEUqYya7RJOIR7lZ+59CFoi74qRYmuiS
SiDcuu6La73YIz1vjIWXi8YqW8+pfvr9dJDPcFjeceHAXzWrez8zAuKJvntofQgc
Sz25yPOxfEUtCmNLvR6DvX+Yqvm0C5E76//sOwRgaRELZbKlyV6yuTn+HnO88/sy
Qn8KE37q4e9+uHy3LdJH0+HzNNy32j+bc7MZJoFPVUhRXwgEelKlrwD7iLfFDYgs
uBG09mA54rn9KLllGBDXscg/sTzPi5YsAWsUAW8hYA3TfwRJsaTrBfNauk+OROWT
c7Qw4dxZi+Oi/KRgFOnni73A2D7z6Gejudmx4ofkoXVAQ+eQZGhVr3/SuWoEzyGM
kTUiM0lW6X3DIRpn1B6LSB30JUOAKn21PQuonQu8gMrEeUheWkaNEDCQ4nACdnmR
Mag0CwuaLKt+eRRb4vsAO9y8KDL3ChBxnxzqjHCQWJH35RRCi5jAH3gvjJj6PHpN
49mQZn/XwMJDgtV1lWUKq7BrM0I5rPpMHuCj6ucB3+rBVcmw0Pk=
=CtPG
-END PGP SIGNATURE-

Bug#994278: Chromium freezes (rarely) and partially locks up my WM (xfce4)

[Craig Sanders]

On Tue, Jan 11, 2022 at 03:33:21PM -0500, Andres Salomon wrote:
> On Wed, 15 Sep 2021 11:29:48 +1000 Craig Sanders wrote:
> > Package: chromium
> > Version: 90.0.4430.212-1

> Can you please tell me if you see this with chromium 97 or above? This
> sounds like a bug related to X11 API usage (ie, grabbing window focus and
> not letting go). We switched backends to ozone (which should be better
> supported), and I'm curious if it still occurs with ozone-x11.

97?  Is that in experimental?  Latest in sid is 93.0.4577.82-1

According to my /var/log/dpkg.log files, I upgraded to that on Sep 22 last
year, about a week after my bug report.

I haven't seen it with this version yet, which is a good sign. It happened
infrequently anyway but I would have expected to see it at least once since
then.

I'll need to check if 97 breaks any of my essential plugins (umatrix, ublock
origin, stylus) before I upgrade to that.

craig

Bug#1003772: Installation of sid successfully at Acer Aspire One A532h

[Bernhard]

Package: installation-reports

Boot method: Network PXE Boot
Image version: PXE Boot with daily:

https://d-i.debian.org/daily-images/i386/daily/netboot/debian-installer/i386/initrd.gz
https://d-i.debian.org/daily-images/i386/daily/netboot/debian-installer/i386/linux

Date: 2022-01-15

Machine: Netbook Acer Aspire One AO532h
Processor: Intel(R) Atom(TM) CPU N450   @ 1.66GHz
Memory: 2GB
Partitions:

> DateisystemTyp  1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
> udev   devtmpfs   1009652   0   10096520% /dev
> tmpfs  tmpfs   205044 8322042121% /run
> /dev/sda1  ext4  57357152 9162560  45248596   17% /
> tmpfs  tmpfs  1025204   0   10252040% /dev/shm
> tmpfs  tmpfs 5120   4  51161% /run/lock
> tmpfs  tmpfs   205040  562049841% /run/user/1000

Output of lspci -knn:

> 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
> D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010]
>   Subsystem: Acer Incorporated [ALI] Atom Processor D4xx/D5xx/N4xx/N5xx 
> DMI Bridge [1025:0349]
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor 
> D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011]
>   Subsystem: Acer Incorporated [ALI] Atom Processor D4xx/D5xx/N4xx/N5xx 
> Integrated Graphics Controller [1025:0349]
>   Kernel driver in use: i915
>   Kernel modules: i915
> 00:02.1 Display controller [0380]: Intel Corporation Atom Processor 
> D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012]
>   Subsystem: Acer Incorporated [ALI] Atom Processor D4xx/D5xx/N4xx/N5xx 
> Integrated Graphics Controller [1025:0349]
> 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High 
> Definition Audio Controller [8086:27d8] (rev 02)
>   Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family High Definition 
> Audio Controller [1025:0349]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel
> 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express 
> Port 1 [8086:27d0] (rev 02)
>   Kernel driver in use: pcieport
> 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express 
> Port 2 [8086:27d2] (rev 02)
>   Kernel driver in use: pcieport
> 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #1 [8086:27c8] (rev 02)
>   Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family USB UHCI Controller 
> [1025:0349]
>   Kernel driver in use: uhci_hcd
>   Kernel modules: uhci_hcd
> 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #2 [8086:27c9] (rev 02)
>   Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family USB UHCI Controller 
> [1025:0349]
>   Kernel driver in use: uhci_hcd
>   Kernel modules: uhci_hcd
> 00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #3 [8086:27ca] (rev 02)
>   Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family USB UHCI Controller 
> [1025:0349]
>   Kernel driver in use: uhci_hcd
>   Kernel modules: uhci_hcd
> 00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #4 [8086:27cb] (rev 02)
>   Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family USB UHCI Controller 
> [1025:0349]
>   Kernel driver in use: uhci_hcd
>   Kernel modules: uhci_hcd
> 00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI 
> Controller [8086:27cc] (rev 02)
>   Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family USB2 EHCI 
> Controller [1025:0349]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge 
> [8086:2448] (rev e2)
> 00:1f.0 ISA bridge [0601]: Intel Corporation NM10 Family LPC Controller 
> [8086:27bc] (rev 02)
>   Subsystem: Acer Incorporated [ALI] NM10 Family LPC Controller 
> [1025:0349]
>   Kernel modules: lpc_ich
> 00:1f.2 SATA controller [0106]: Intel Corporation NM10/ICH7 Family SATA 
> Controller [AHCI mode] [8086:27c1] (rev 02)
>   Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family SATA Controller 
> [AHCI mode] [1025:0349]
>   Kernel driver in use: ahci
>   Kernel modules: ahci
> 00:1f.3 SMBus [0c05]: Intel Corporation NM10/ICH7 Family SMBus Controller 
> [8086:27da] (rev 02)
>   Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family SMBus Controller 
> [1025:0349]
>   Kernel driver in use: i801_smbus
>   Kernel modules: i2c_i801
> 01:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8132 Fast Ethernet 
> [1969:1062] (rev c0)
>   Subsystem: Acer Incorporated [ALI] AR8132 Fast Ethernet [1025:0349]
>   Kernel driver in use: atl1c
>   Kernel modules: atl1c
> 02:00.0 Network controller [0280]: Qualcomm Atheros AR9285 Wireless Network 
> Adapter (PCI-Express) [168c:002b] (rev 01)
>   Subsystem: Foxconn International, In

Bug#1003490: u-boot: FTBFS on arch:all with qemu-ppce500 target

[Aurelien Jarno]

control: tag -1 + upstream
control: tag -1 + patch

On 2022-01-11 16:40, Vagrant Cascadian wrote:
> On 2022-01-11, Lennart Sorensen wrote:
> > On Mon, Jan 10, 2022 at 05:10:04PM -0800, Vagrant Cascadian wrote:
> >> Package: u-boot
> >> Version: 2022.01+dfsg1-1
> >> Severity: serious
> >> X-Debbugs-Cc: debian-powe...@lists.debian.org, q...@packages.debian.org, 
> >> binut...@packages.debian.org
> >> 
> >> Something in the toolchain recently changed which causes u-boot arch:all
> >> build to FTBFS... I suspect binutils, as building in "bookworm" still
> >> works fine where binutils hasn't yet migrated.
> >> 
> >> On arch:all builds the qemu-ppce500 target is cross-compiled.
> >> 
> >> Full log:
> >> 
> >>   
> >> https://buildd.debian.org/status/fetch.php?pkg=u-boot&arch=all&ver=2022.01%2Bdfsg-1&stamp=1641860624&raw=0
> >> 
> >> The hopefully relevent lines from the build log:
> >> 
> >>   powerpc-linux-gnu-gcc -Wp,-MD,arch/powerpc/cpu/mpc85xx/.tlb.o.d 
> >> -nostdinc -isystem /usr/lib/gcc-cross/powerpc-linux-gnu/11/include 
> >> -Iinclude  -I/<>/include  
> >> -I/<>/arch/powerpc/include -include 
> >> /<>/include/linux/kconfig.h  
> >> -I/<>/arch/powerpc/cpu/mpc85xx -Iarch/powerpc/cpu/mpc85xx 
> >> -D__KERNEL__ -D__UBOOT__ -Wall -Wstrict-prototypes -Wno-format-security 
> >> -fno-builtin -ffreestanding -std=gnu11 -fshort-wchar -fno-strict-aliasing 
> >> -fno-PIE -Os -fno-stack-protector -fno-delete-null-pointer-checks 
> >> -Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds 
> >> -Wno-array-bounds -Wno-stringop-overflow -Wno-maybe-uninitialized 
> >> -fmacro-prefix-map=/<>/= -g -fstack-usage 
> >> -Wno-format-nonliteral -Wno-address-of-packed-member 
> >> -Wno-unused-but-set-variable -Werror=date-time -Wno-packed-not-aligned 
> >> -D__powerpc__ -ffixed-r2 -m32 -fno-ira-hoist-pressure -Wa,-me500 
> >> -msoft-float -mno-string -fpic -mrelocatable -ffunction-sections 
> >> -fdata-sections -mcall-linux -msingle-pic-base -fno-jump-tables -pipe
> >> -DKBUILD_BASENAME='"tlb"'  -DKBUILD_MODNAME='"tlb"' -c -o 
> >> arch/powerpc/cpu/mpc85xx/tlb.o 
> >> /<>/arch/powerpc/cpu/mpc85xx/tlb.c
> >> ...
> >> {standard input}: Assembler messages:
> >> {standard input}:127: Error: unrecognized opcode: `tlbre'
> >> {standard input}:418: Error: unrecognized opcode: `tlbre'
> >> {standard input}:821: Error: unrecognized opcode: `msync'
> >> {standard input}:821: Error: unrecognized opcode: `tlbwe'
> >> {standard input}:884: Error: unrecognized opcode: `tlbsx'
> >> make[4]: *** [/<>/scripts/Makefile.build:253: 
> >> arch/powerpc/cpu/mpc85xx/tlb.o] Error 1
> >> make[3]: *** [/<>/Makefile:1810: arch/powerpc/cpu/mpc85xx] 
> >> Error 2
> >> make[3]: *** Waiting for unfinished jobs
> >>   powerpc-linux-gnu-gcc -Wp,-MD,arch/powerpc/lib/.traps.o.d -nost
> >> 
> >> 
> >> If anyone has thoughts what might be the issue, please chime in!
> >> 
> >> 
> >> I could remove qemu-ppce500 from the build targets(all other targets
> >> build fine); I am not sure if it is used by qemu or if qemu builds all
> >> it's own firmwares.
> >
> > Which gcc version?  I believe gcc 9 removed the code for powerpcspe
> > which gcc 8 deprecated.  So at this point I think only llvm/clang supports
> > the powerpcspe targets.
> 
> gcc-11 11.2.0-13 in both the successfull (bookworm) and
> failing case (sid).
> 
> Which is why I suspect binutils, which differs between bookworm and
> sid...
> 
> > I don't recall if binutils also dropped support or have kept it around.
> 
> The binutils versions appear to be:
> 
>   succeeding, bookworm 2.37-10.1
>   failing, sid 2.37.50.20220106-2
> 

Yep, this is due to commit b25f942e18d6ecd7ec3e2d2e9930eb4f996c258a on
the binutils side [1], which changes the behavior of `.machine`
directives to override, rather than augment, the base CPU. GCC is called
with -Wa,-me500 to enable PowerPC e500 instructions on the assembler
side, but as the default GCC machine is ppc, a `.set machine ppc` is
emitted at the beginning of the assembly code.

One option would be to force the CPU to e500 on the GCC side, however
support for it has been removed. The options is therefore to force the
machine in the assembly code. This is what the attached patch does.

Regards,
Aurelien

[1] 
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=b25f942e18d6ecd7ec3e2d2e9930eb4f996c258a

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--- u-boot-2022.01+dfsg.orig/arch/powerpc/cpu/mpc85xx/tlb.c
+++ u-boot-2022.01+dfsg/arch/powerpc/cpu/mpc85xx/tlb.c
@@ -50,7 +50,10 @@ void read_tlbcam_entry(int idx, u32 *val
 	u32 _mas1;
 
 	mtspr(MAS0, FSL_BOOKE_MAS0(1, idx, 0));
-	asm volatile("tlbre;isync");
+	asm volatile(".machine push;\n"
+		 ".machine e500;\n"
+		 "tlbre;isync;\n"
+		 ".machine pop;\n");
 	_mas1 = mfspr(MAS1);
 
 	*valid = (_mas1 & MAS1_VALID);
@@ -109,7 +112,10 @@ void init_used_tlb_cams(void)
 	/* walk all the entries */
 	for (i = 0; i < num

Bug#1003771: Not (properly?) wrapping the stat call

[Christoph Biedl]

Package: fakeroot-ng
Version: 0.18-4.1
Severity: normal

Dear maintainer,

while working on #1001961 in fakeroot, I noticed the stat() call is not
properly wrapped by fakeoot-ng, and appearently never did - I checked
back to Debian 8 ("jessie").

Reproducer: Build the program below and run under either fakeroot or
fakeroot-ng.

Expected output (observed with fakeroot):

I: UID is 0, '.' is owned by 0
I: Pass

Received output:

I: UID is 0, '.' is owned by 1000
E: UID mismatch


While I haven't checked it, this should also break the python-apt
autopkgtest if it were run using fakeroot-ng instead of fakeroot.
See the bug# mentioned above for an explanation.

To me, it seems prudent to add this to have feature parity.

Regards,

Christoph

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

Kernel: Linux 5.10.89 (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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fakeroot-ng depends on:
ii  libc6   2.33-2
ii  libgcc-s1   11.2.0-14
ii  libstdc++6  11.2.0-14

fakeroot-ng recommends no packages.

fakeroot-ng suggests no packages.

-- no debconf information


-
#include 
#include 
#include 
#include 
#include 

int main (int argc, char **argv) {
struct stat statbuf;
if (stat (".", &statbuf)) {
perror("Cannot stat '.'");
exit(1);
}
uid_t uid = getuid();
printf("I: UID is %u, '.' is owned by %u\n", uid, statbuf.st_uid);
if (uid == statbuf.st_uid) {
if (uid) {
printf("W: UID is not zero - not running under fakeroot?\n");
} else {
printf("I: Pass\n");
}
} else {
printf("E: UID mismatch\n");
}
}
-



signature.asc
Description: PGP signature

Bug#1003707: nvidia-legacy-340xx-driver

[Сергей Petrov]

On Fri, 14 Jan 2022 14:10:31 +0100 Andreas Beckmann  wrote:
> On 14/01/2022 02.03, Сергей Petrov wrote:
> > Package: nvidia-legacy-340xx-driver
> > Version: 340.108-12
>
> There is not much infomation in this bug report. I'll try to guess, if
> I'm wrong please install reportbug and run
> reportbug -N 1003707
> to collect additional information about your setup and have it sent to
> the bug report. (Creating the initial bug report with reportbug is
> recommended.)
>
> So you want to use the unsupported 340xx legacy driver?
>
> But there are also some packages from the current driver installed?
> You can probably remove them (unless you really want to have both
> drivers installed). That might already fix your problem.
>
> It it doesn't, what are the nvidia and glx alternatives pointing to?
> update-glx --display glx
> update-glx --display nvidia
> (that information would have been collected by reportbug)
> if glx is not pointing to nvidia or nvidia is not pointing to the legacy
> driver, you can change that with
> update-glx --config glx
> update-glx --config nvidia
>
> Andreas
>
>


apt-file search libnvidia-cfg.so.460.91.03
libnvidia-cfg1:
/usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-cfg.so.460.91.03
libnvidia-tesla-460-cfg1:
/usr/lib/x86_64-linux-gnu/nvidia/tesla-460/libnvidia-cfg.so.460.91.03

Why, if I install nvidia-legacy-340xx-driver in my system available
/usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-cfg.so.460.91.03
File from another driver version. This normal or wrong?

Bug#992649: run-parts in /usr/bin breaks systemd-cron

[Dominique Dumont]

On Sun, 2 Jan 2022 19:03:28 +0100 Alexandre Detiste 
 wrote:
> ./configure --runparts="/usr/bin/env run-parts"

The changelog of debianutils 5.0-1 (Aug 2021) shows:
  * Move run-parts to /usr/bin

I guess there are 2 ways to fix this.

Either a compat link (or a script with a deprecation warning) should be 
provided by debianutils as /bin/run-parts or systemd-cron should be modified
to use /usr/bin/run-parts.

What's preventing such a fix ?

Note that locate is also impacted by this bug :

$ locate foobarbaz
locate: warning: database ‘/var/cache/locate/locatedb’ is more than 8 jours 
old (actual age is 135,0 jours)

All the best

Dod

Bug#1001392: (no subject)

[Ayoyimika Ajibade]

After installing node-uglifyjs-webpack-plugin package i am faced with 
another error as the source package using webpack3 has not migrated to 
webpack5.


Here is the new error message:

   debian/rules override_dh_auto_build
make[1]: Entering directory 
'/home/ayoyimika/debian-js-packaging/axios/node-axios'

grunt build
Running "clean:dist" (clean) task
>> 0 paths cleaned.

Running "webpack" task
10% building 0/1 entries 0/0 dependencies 0/0 modules(node:19516) 
[DEP_WEBPACK_COMPILATION_OPTIMIZE_CHUNK_ASSETS] DeprecationWarning: 
optimizeChunkAssets is deprecated (use Compilation.hooks.processAssets 
instead and use one of Compilation.PROCESS_ASSETS_STAGE_* as stage option)
92% sealing asset processing UglifyJSPlugin(node:19516) 
[DEP_WEBPACK_DEPRECATION_ARRAY_TO_SET] DeprecationWarning: 
Compilation.chunks was changed from Array to Set (using Array method 
'reduce' is deprecated)
(node:19516) [DEP_WEBPACK_DEPRECATION_ARRAY_TO_SET_LENGTH] 
DeprecationWarning: chunk.files was changed from Array to Set (using 
Array property 'length' is deprecated)
(node:19516) [DEP_WEBPACK_DEPRECATION_ARRAY_TO_SET_INDEXER] 
DeprecationWarning: chunk.files was changed from Array to Set (indexing 
Array is deprecated)

99% cache begin idleasset axios.js 99 bytes [emitted] (name: main)

ERROR in main
Module not found: Error: Recursion in resolving
Stack:
  undefined: (/home/ayoyimika/debian-js-packaging/axios/node-axios) 
./index.js


webpack 5.65.0 compiled with 1 error in 446 ms
Warning:  Use --force to continue.

Aborted due to warnings.
make[1]: *** [debian/rules:11: override_dh_auto_build] Error 3
make[1]: Leaving directory 
'/home/ayoyimika/debian-js-packaging/axios/node-axios'

make: *** [debian/rules:8: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2


The full log is attached to this mail
sbuild (Debian sbuild) 0.81.2 (31 January 2021) on Ayoyimika-PC.localdomain

+==+
| node-axios 0.24.0+dfsg-1 (amd64) Sat, 15 Jan 2022 14:10:13 + |
+==+

Package: node-axios
Version: 0.24.0+dfsg-1
Source Version: 0.24.0+dfsg-1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-069edc55-bb6f-4a70-8c57-a3dab6425079'
 with '<>'
W: ./node-mini-css-extract-plugin_2.4.5-1_all.deb is neither a regular file nor 
a directory. Skipping...
I: NOTICE: Log filtering will replace 'build/node-axios-wCZwlG/resolver-NHWML9' 
with '<>'

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

Get:1 file:/build/node-axios-wCZwlG/resolver-zLBiiY/apt_archive ./ InRelease
Ign:1 file:/build/node-axios-wCZwlG/resolver-zLBiiY/apt_archive ./ InRelease
Get:2 file:/build/node-axios-wCZwlG/resolver-zLBiiY/apt_archive ./ Release [951 
B]
Get:2 file:/build/node-axios-wCZwlG/resolver-zLBiiY/apt_archive ./ Release [951 
B]
Get:3 file:/build/node-axios-wCZwlG/resolver-zLBiiY/apt_archive ./ Release.gpg
Ign:3 file:/build/node-axios-wCZwlG/resolver-zLBiiY/apt_archive ./ Release.gpg
Get:4 file:/build/node-axios-wCZwlG/resolver-zLBiiY/apt_archive ./ Packages 
[811 B]
Err:4 file:/build/node-axios-wCZwlG/resolver-zLBiiY/apt_archive ./ Packages
  Could not open file 
/build/node-axios-wCZwlG/resolver-zLBiiY/apt_archive/./Packages - open (13: 
Permission denied)
Get:4 file:/build/node-axios-wCZwlG/resolver-zLBiiY/apt_archive ./ Packages 
[1405 B]
Get:5 http://deb.debian.org/debian unstable InRelease [165 kB]
Get:6 http://deb.debian.org/debian experimental InRelease [75.4 kB]
Get:7 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index 
[63.6 kB]
Get:9 http://deb.debian.org/debian unstable/main amd64 Contents 
(deb).diff/Index [63.8 kB]
Get:10 http://deb.debian.org/debian unstable/main all Contents (deb).diff/Index 
[63.8 kB]
Get:11 http://deb.debian.org/debian experimental/main Sources.diff/Index [63.3 
kB]
Get:12 http://deb.debian.org/debian experimental/main amd64 Packages.diff/Index 
[63.3 kB]
Get:13 http://deb.debian.org/debian experimental/main amd64 Contents 
(deb).diff/Index [63.6 kB]
Get:14 http://deb.debian.org/debian experimental/main all Contents 
(deb).diff/Index [63.6 kB]
Get:15 http://deb.debian.org/debian unstable/main Sources 
T-2022-01-15-0801.48-F-2022-01-14-0206.23.pdiff [81.9 kB]
Get:16 http://deb.debian.org/debian unstable/main amd64 Packages 
T-2022-01-15-0801.48-F-2022-01-14-0206.23.pdiff [107 kB]
Get:15 http://deb.debian.org/debian unstable/main Sources 
T-2022-01-15-0801.48-F-2022-01-14-0206.23.pdiff [81.9 kB]
Ge

Bug#1003755: mailutils: mail(1) completely broken, fails with "undefined symbol: mu_stream_timed_getdelim" on start

[наб]

Control: severity -1 important
Control: reassign -1 libmailutils8 1:3.14-1
Control: retitle -1 libmailutils8: 1:3.14-1 breaks ABI vs 1:3.13-1, doesn't 
bump abiver

Hi!

On Sat, Jan 15, 2022 at 09:40:45AM +0100, Jordi Mallach wrote:
> El ds. 15 de 01 de 2022 a les 05:10 +0100, en/na наб va escriure:
> > Versions of packages mailutils depends on:
> > ii  libmailutils8 1:3.13-1
> > ii  mailutils-common  1:3.14-1
> This version mismatch between mailutils and its libs.
> 
> It shouldn't happen, but if this is the problem, I'll look into it and
> will tighten the dependency.

You got it! Additionally: libmailutils8 not only adds, but also removes
symbols (diff from nm -D libmailutils.so.8 | cut -c10- | sort),
without bumping abiver (both are 8.0.0):

diff --git a/libmailutils.so.8-3.13-1 b/libmailutils.so.8-3.14-1
index 3495a2a..ad40684 100644
--- a/libmailutils.so.8-3.13-1
+++ b/libmailutils.so.8-3.14-1
@@ -1,6 +1,7 @@
 B dup_args
 B filter_monitor
 B long_opt_col
+B mimetypes_yydebug
 B monitor_lock
 B mu_alloc_die_hook
 B mu_cfg_error_count
@@ -119,6 +120,7 @@ T amd_reset_uidvalidity
 T amd_sort
 T amd_update_uidnext
 T bstr_done
+T compare_bytes
 T connection_loop
 T destroy_connection
 T fd_done
@@ -136,9 +138,49 @@ T getword
 T header_seek
 T ISO_8601_weekdays
 T iterator_get_owner
+T lex_next_rule
 T _mailbox_create_from_record
 T make_fdset
 T _message_error_string
+T mime_debug
+T mimetypes_scanner_open
+T mimetypes_yyalloc
+T mimetypes_yy_create_buffer
+T mimetypes_yy_delete_buffer
+T mimetypes_yyerror
+T mimetypes_yy_flush_buffer
+T mimetypes_yyfree
+T mimetypes_yyget_column
+T mimetypes_yyget_debug
+T mimetypes_yyget_extra
+T mimetypes_yyget_in
+T mimetypes_yyget_leng
+T mimetypes_yyget_lineno
+T mimetypes_yyget_lloc
+T mimetypes_yyget_lval
+T mimetypes_yyget_out
+T mimetypes_yyget_text
+T mimetypes_yylex
+T mimetypes_yylex_destroy
+T mimetypes_yylex_init
+T mimetypes_yylex_init_extra
+T mimetypes_yyparse
+T mimetypes_yypop_buffer_state
+T mimetypes_yypush_buffer_state
+T mimetypes_yyrealloc
+T mimetypes_yyrestart
+T mimetypes_yy_scan_buffer
+T mimetypes_yy_scan_bytes
+T mimetypes_yy_scan_string
+T mimetypes_yyset_column
+T mimetypes_yyset_debug
+T mimetypes_yyset_extra
+T mimetypes_yyset_in
+T mimetypes_yyset_lineno
+T mimetypes_yyset_lloc
+T mimetypes_yyset_lval
+T mimetypes_yyset_out
+T mimetypes_yy_switch_to_buffer
 T mu_2nrealloc
 T mu_acl_action_to_string
 T mu_acl_append
@@ -609,6 +651,7 @@ T mu_imapio_getline
 T mu_imapio_get_streams
 T mu_imapio_get_trace
 T mu_imapio_get_trace_payload
+T mu_imapio_get_transport
 T mu_imapio_get_words
 T mu_imapio_last_error
 T mu_imapio_printf
@@ -625,6 +668,7 @@ T mu_imapio_send_qstring
 T mu_imapio_send_qstring_unfold
 T mu_imapio_send_time
 T mu_imapio_set_streams
+T mu_imapio_set_transport
 T mu_imapio_set_xscript_level
 T mu_imapio_trace_disable
 T mu_imapio_trace_enable
@@ -784,6 +828,7 @@ T mu_ltrim_class
 T mu_ltrim_cset
 T mu_mailbox_access_time
 T mu_mailbox_append_message
+T mu_mailbox_append_message_ext
 T mu_mailbox_attach_ticket
 T mu_mailbox_close
 T mu_mailbox_create
@@ -986,6 +1031,12 @@ T mu_mime_ref
 T mu_mime_sget_content_subtype
 T mu_mime_sget_content_type
 T mu_mime_to_message
+T mu_mimetypes_builtin
+T mu_mimetypes_close
+T mu_mimetypes_fd_type
+T mu_mimetypes_file_type
+T mu_mimetypes_open
+T mu_mimetypes_stream_type
 T mu_mime_unref
 T mu_monitor_create
 T mu_monitor_destroy
@@ -1301,9 +1352,7 @@ T mu_stream_flags_to_mode
 T mu_stream_flush
 T mu_stream_format_address
 T mu_stream_get_buffer
-T mu_stream_getdelim
 T mu_stream_get_flags
-T mu_stream_getline
 T mu_stream_get_stat
 T mu_stream_header_copy
 T mu_stream_ioctl
@@ -1316,8 +1365,6 @@ T mu_stream_printf
 T mu_stream_print_locus_point
 T mu_stream_print_locus_range
 T mu_stream_read
-T mu_stream_readdelim
-T mu_stream_readline
 T mu_stream_ref
 T mu_streamref_create
 T mu_streamref_create_abridged
@@ -1333,6 +1380,8 @@ T mu_stream_shutdown
 T mu_stream_size
 T mu_stream_skip_input_bytes
 T mu_stream_strerror
+T mu_stream_timed_getdelim
+T mu_stream_timed_readdelim
 T mu_stream_to_message
 T mu_stream_truncate
 T mu_stream_unref
@@ -1515,7 +1564,6 @@ T remove_connection
 T _run_entry
 T send_fragments
 T _socket_shutdown
-T _stream_scandelim
 T _syslog_setbuf_hook
 T _tcp_shutdown
 T _tcp_wait
@@ -1565,9 +1613,9 @@ U fputc@GLIBC_2.16
 U fread@GLIBC_2.16
 U freeaddrinfo@GLIBC_2.16
 U free@GLIBC_2.16
+U fstat@GLIBC_2.33
 U ftruncate@GLIBC_2.16
 U fwrite@GLIBC_2.16
-U __fxstat@GLIBC_2.16
 U gai_strerror@GLIBC_2.16
 U getaddrinfo@GLIBC_2.16
 U getc@GLIBC_2.16
@@ -1604,7 +1652,7 @@ U listen@GLIBC_2.16
 U localtime@GLIBC_2.16
 U longjmp@GLIBC_2.16
 U lseek@GLIBC_2.16
-U __lxstat@GLIBC_2.16
+U lstat@GLIBC_2.33
 U malloc@GLIBC_2.16
 U memchr@GLIBC_2.16
 U memcmp@GLIBC_2.16
@@ -1613,6 +1661,7 @@ U memmove@GLIBC_2.16
 U memset@GLIBC_2.16
 U mkdir@GLIBC_2.16
 U mkfifo@GLIBC_2.16
+U mknod@GLIBC_2.33
 U mktime@GLIBC_2.16
 U mmap@GLIBC_2.16
 U msync@GLIBC_2.16
@@ -1626,6 +1675,7 @@ U 

Bug#1003770: RFS: luit/2.0.20220111-1 [ITP] -- locale and ISO 2022 support for Unicode terminals

[Thomas Dickey]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name: luit
   Version : 2.0.20220111-1
   Upstream Author : Thomas Dickey 
 * URL : http://invisible-island.net/luit/
 * License : GPL-3, X11
 * Vcs : https://salsa.debian.org/dickey/luit
   Section : utils

It builds those binary packages:

  luit2 - locale and ISO 2022 support for Unicode terminals

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/l/luit/luit_2.0.20220111-1.dsc

Changes for the initial release:

 luit (2.0.20220111-1) unstable; urgency=low
 .
   * Initial package release (Closes: #1003130)

Regards,

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature

Bug#1001549: (no subject)

[Ayoyimika Ajibade]

Upon updating webpack5 to version to 5.65.0+dfsg+~cs9.20.9-2 
node-mermaid that previously passed failed to build due to update made 
check repo here => 
https://salsa.debian.org/js-team/node-webpack/-/tree/master-5.


Error message thrown by node-mermaid:

webpack --progress --colors
[webpack-cli] Unable load 
'/home/ayoyimika/debian-js-packaging/mermaid/node-mermaid/.webpack/webpack.config.babel.js'

[webpack-cli] Unable to use specified module loaders for ".babel.js".
[webpack-cli] Cannot find module '@babel/register' from 
'/home/ayoyimika/debian-js-packaging/mermaid/node-mermaid/.webpack'
[webpack-cli] Cannot find module 'babel-register' from 
'/home/ayoyimika/debian-js-packaging/mermaid/node-mermaid/.webpack'
[webpack-cli] Cannot find module 'babel-core/register' from 
'/home/ayoyimika/debian-js-packaging/mermaid/node-mermaid/.webpack'
[webpack-cli] Cannot find module 'babel/register' from 
'/home/ayoyimika/debian-js-packaging/mermaid/node-mermaid/.webpack'

[webpack-cli] Please install one of them
[webpack-cli] Error: Unable to use specified module loaders for ".babel.js".
at Object.exports.prepare (/usr/share/nodejs/rechoir/index.js:58:11)
at loadConfigByPath 
(/usr/share/nodejs/webpack-cli/lib/webpack-cli.js:1699:19)
at WebpackCLI.loadConfig 
(/usr/share/nodejs/webpack-cli/lib/webpack-cli.js:1843:36)
at WebpackCLI.createCompiler 
(/usr/share/nodejs/webpack-cli/lib/webpack-cli.js:2198:29)
at WebpackCLI.runWebpack 
(/usr/share/nodejs/webpack-cli/lib/webpack-cli.js:2334:27)
at Command. 
(/usr/share/nodejs/webpack-cli/lib/webpack-cli.js:1067:24)
at Command.listener [as _actionHandler] 
(/usr/share/nodejs/commander/lib/command.js:488:17)

at /usr/share/nodejs/commander/lib/command.js:1227:65
at Command._chainOrCall 
(/usr/share/nodejs/commander/lib/command.js:1144:12)
at Command._parseCommand 
(/usr/share/nodejs/commander/lib/command.js:1227:27) {

  failures: [
{ moduleName: '@babel/register', module: null, error: [Error] },
{ moduleName: 'babel-register', module: null, error: [Error] },
{ moduleName: 'babel-core/register', module: null, error: [Error] },
{ moduleName: 'babel/register', module: null, error: [Error] }
  ]
}
[webpack-cli] Failed to load 
'/home/ayoyimika/debian-js-packaging/mermaid/node-mermaid/.webpack/webpack.config.babel.js' 
config
[webpack-cli] 
/home/ayoyimika/debian-js-packaging/mermaid/node-mermaid/.webpack/webpack.config.babel.js:1

import { merge, mergeWithCustomize, customizeObject } from 'webpack-merge';
^^

SyntaxError: Cannot use import statement outside a module
at wrapSafe (internal/modules/cjs/loader.js:915:16)
at Module._compile (internal/modules/cjs/loader.js:963:27)
at Object.Module._extensions..js 
(internal/modules/cjs/loader.js:1027:10)

at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at WebpackCLI.tryRequireThenImport 
(/usr/share/nodejs/webpack-cli/lib/webpack-cli.js:249:16)
at loadConfigByPath 
(/usr/share/nodejs/webpack-cli/lib/webpack-cli.js:1723:30)
at WebpackCLI.loadConfig 
(/usr/share/nodejs/webpack-cli/lib/webpack-cli.js:1843:36)

make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2
make[1]: Leaving directory 
'/home/ayoyimika/debian-js-packaging/mermaid/node-mermaid'

make: *** [debian/rules:8: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status


The full log is attached to this mail
sbuild (Debian sbuild) 0.81.2 (31 January 2021) on Ayoyimika-PC.localdomain

+==+
| node-mermaid 8.13.8+~cs10.4.16-1 (amd64) Fri, 14 Jan 2022 02:11:41 + |
+==+

Package: node-mermaid
Version: 8.13.8+~cs10.4.16-1
Source Version: 8.13.8+~cs10.4.16-1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-e02ba97e-086e-4d6a-a61b-2f56f45a3481'
 with '<>'
W: ./node-mini-css-extract-plugin_2.4.5-1_all.deb is neither a regular file nor 
a directory. Skipping...
I: NOTICE: Log filtering will replace 
'build/node-mermaid-uIJP9n/resolver-yBhr98' with '<>'

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

Get:1 file:/build/node-mermaid-uIJP9n/resolver-ksobBL/apt_archive ./ InRelease
Ign:1 file:/build/node-mermaid-uIJP9n/resolver-ksobBL/apt_archive ./ InRelease
Get:2 file:/build/node-mermaid-uIJP9n/resolver-ksobBL/apt_archive ./ Release 
[951 B]
Get:2 file:/build

Bug#1003769: RFS: byacc/1.0-2 [ITA] -- public domain Berkeley LALR Yacc parser generator

[Thomas Dickey]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: byacc
   Version : 1:2.0.20220114-1
   Upstream Author :  (Thomas E. Dickey)
 * URL : https://invisible-island.net/byacc/
 * License : GPL-3, public-domain, other-BSD
 * Vcs : https://salsa.debian.org/debian/byacc
   Section : devel

It builds those binary packages:

  byacc - public domain Berkeley LALR Yacc parser generator
  byacc2 - public domain Berkeley LALR Yacc parser generator, with back-tracking

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/byacc/byacc_2.0.20220114-1.dsc

Changes since the last upload:

 byacc (1:2.0.20220114-1) unstable; urgency=medium
 .
   * work around git-buildpackage's absence of configurability regarding uscan.
   * fix lintian issues reported in update.

Regards,
-- 
  Thomas Dickey

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature

Bug#1003768: RFS: guerillabackup/0.1.1-1 [ITP] -- resilient, distributed backup and archiving solution

[halfdog]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name: guerillabackup
   Version : 0.1.1-1
   Upstream Author : m...@halfdog.net
 * URL : https://github.com/halfdog/guerillabackup
 * License : LGPL-3.0+
 * Vcs : https://salsa.debian.org/halfdog-guest/guerillabackup
   Section : misc

It builds those binary packages:

  guerillabackup - resilient, distributed backup and archiving solution

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/guerillabackup/guerillabackup_0.1.1-1.dsc

Changes for the initial release:

 guerillabackup (0.1.1-1) unstable; urgency=medium
 .
   * Initial packaging of guerillabackup (Closes: #849714)

Regards,
-- 
  halfdog

Bug#1003535: meson: fails to build vala if 'metadata_dirs' option is specified

[Jussi Pakkanen]

On Tue, 11 Jan 2022 at 16:30, Arnaud Ferraris  wrote:

> This bug has been fixed upstream[1] and the corresponding patch should be
> backported
> while waiting for the next point release.

There are a couple of other Gnome stack issues so just fixing this on
its own would not be that beneficial. We'll fix all of them in one go
in the point release due out on Monday.

Bug#1003767: libyang: autopkgtest failure (and tests the src:libyang2 packages)

[Adrian Bunk]

Source: libyang
Version: 1.0.225-1.1
Severity: serious
Tags: bookworm sid

https://ci.debian.net/data/autopkgtest/testing/amd64/liby/libyang/18315507/log.gz

...
The following additional packages will be installed:
  libyang-tools libyang2 libyang2-tools
The following NEW packages will be installed:
  libyang-tools libyang2 libyang2-tools
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 486 kB of archives.
After this operation, 1,353 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian unstable/main amd64 libyang2 amd64 2.0.112-6 
[397 kB]
Get:2 http://deb.debian.org/debian unstable/main amd64 libyang2-tools amd64 
2.0.112-6 [80.8 kB]
Get:3 http://deb.debian.org/debian unstable/main amd64 libyang-tools all 
2.0.112-6 [8,136 B]
...
autopkgtest [18:35:29]: test yanglint: [---
cp: cannot stat '/usr/share/doc/libyang-tools/examples/ietf-interfaces.yang': 
No such file or directory
autopkgtest [18:35:29]: test yanglint: ---]
autopkgtest [18:35:29]: test yanglint:  - - - - - - - - - - results - - - - - - 
- - - -
yanglint FAIL non-zero exit status 1
autopkgtest [18:35:29]: test yanglint:  - - - - - - - - - - stderr - - - - - - 
- - - -
cp: cannot stat '/usr/share/doc/libyang-tools/examples/ietf-interfaces.yang': 
No such file or directory
autopkgtest [18:35:29]:  summary
yanglint FAIL non-zero exit status 1

Bug#1003689: chromium: Chromium doesn't start

[Adrien Ponchelet]

Dear Andres,

I have the same problem as Martin.

The "--use-gl=desktop" option doesn't work for me to. Open is ok, but 
window is figed. I cannot do anything.
When I commenting the line 61 to 63 (/usr/bin/chromium) which refer to 
Wayland, it works fine.
The "--ozone-platform-hint=auto" option (without lines commented) 
doesn't work, same as launching the "chromium" command.


Below, my console log :

$> uname -a
Linux portable 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) 
x86_64 GNU/Linux


$> chromium --version
Chromium 97.0.4692.71 built on Debian 11.2, running on Debian 11.2

$> chromium --use-gl=desktop
[9055:9055:0115/143258.305656:ERROR:gl_factory.cc(146)] Requested GL 
implementation is not available.
[9055:9055:0115/143258.310224:ERROR:viz_main_impl.cc(161)] Exiting GPU 
process due to errors during initialization
[9007:9036:0115/143258.827916:ERROR:nss_util.cc(286)] After loading Root 
Certs, loaded==false: NSS error code: -8018
[9119:9119:0115/143259.057540:ERROR:gl_factory.cc(146)] Requested GL 
implementation is not available.
[9119:9119:0115/143259.061447:ERROR:viz_main_impl.cc(161)] Exiting GPU 
process due to errors during initialization
[9183:9183:0115/143259.416071:ERROR:gl_factory.cc(146)] Requested GL 
implementation is not available.
[9183:9183:0115/143259.433760:ERROR:viz_main_impl.cc(161)] Exiting GPU 
process due to errors during initialization
[9196:9196:0115/143259.992476:ERROR:gpu_init.cc(457)] Passthrough is not 
supported, GL is disabled, ANGLE is
[9196:9196:0115/143259.993159:ERROR:sandbox_linux.cc(378)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[9196:9212:0115/143300.028018:ERROR:wayland_buffer_manager_gpu.cc(124)] 
WaylandBufferManagerGpu is not initialized. Can't register a surface.
[9007:9052:0115/143301.229936:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] 
START: ReportBluetoothAvailability(). If you don't see the END: message, 
this is crbug.com/1216328.
[9007:9052:0115/143301.230020:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] 
END: ReportBluetoothAvailability()

*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated

$> chromium (with lines commented in /usr/bin/chromium)
[9308:9369:0115/143528.235577:ERROR:nss_util.cc(286)] After loading Root 
Certs, loaded==false: NSS error code: -8018
libva error: vaGetDriverNameByIndex() failed with unknown libva error, 
driver_name = (null)
[9352:9352:0115/143528.823080:ERROR:sandbox_linux.cc(378)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[9308:9370:0115/143530.646896:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] 
START: ReportBluetoothAvailability(). If you don't see the END: message, 
this is crbug.com/1216328.
[9308:9370:0115/143530.646943:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] 
END: ReportBluetoothAvailability()

*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[0115/143550.781276:ERROR:scoped_ptrace_attach.cc(27)] ptrace: No such 
process (3)

*** stack smashing detected ***: terminated
Fontconfig error: Cannot load default config file
*** stack smashing detected ***: terminated

$> chromium --ozone-platform-hint=auto
[9807:9807:0115/143805.240618:ERROR:gpu_init.cc(457)] Passthrough is not 
supported, GL is egl, ANGLE is
[9807:9807:0115/143805.247921:ERROR:sandbox_linux.cc(378)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[9759:9790:0115/143805.688139:ERROR:nss_util.cc(286)] After loading Root 
Certs, loaded==false: NSS error code: -8018
[9759:9788:0115/143807.847431:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] 
START: ReportBluetoothAvailability(). If you don't see the END: message, 
this is crbug.com/1216328.
[9759:9788:0115/143807.847472:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] 
END: ReportBluetoothAvailability()

*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[9892:1:0115/143814.653495:ERROR:command_buffer_proxy_impl.cc(125)] 
ContextResult::kTransientFailure: Failed to send 
GpuControl.CreateCommandBuffer.
[9904:1:0115/143814.653495:ERROR:command_buffer_proxy_impl.cc(125)] 
ContextResult::kTransientFailure: Failed to send 
GpuControl.CreateCommandBuffer.
[9759:9759:0115/143815.797128:ERROR:gpu_process_host.cc(968)] GPU 
process exited unexpectedly: exit_code=11
[9947:9947:0115/143816.024628:ERROR:gpu_init.cc(457)] Passthrough is not 
supported, GL is egl, ANGLE is
[9947:9947:0115/143816.031839:ERROR:sandbox_linux.cc(378)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[9892:1:0115/143823.657122:ERROR:command_buffer_proxy_impl.cc(328)] GPU 
state invalid after WaitForGetOffsetInRange.
[9904:1:0115/143823.657142:ERROR:command_buffer_proxy_impl.cc(328)] GPU 
state invalid after WaitForGetOffsetInRange.
[9759:9759:0115/143824.78802

Bug#1001976: ITS: libppd

[A Mennucc1]

Dear Christoph

if you wish to adopt this package, go ahead.

Thanks

a.

Il 06/01/22 15:37, Christoph Biedl ha scritto:

X-Debbugs-CC: mennu...@debian.org, m...@qa.debian.org

[ Re-sending as I forgot about X-Debbugs-CC ]

| Source: libppd
| Version: 2:0.10-7.3
| Severity: important
|
| Greetings,
|
| hereby I declare my intention to salvage the "libppd" package using the
| procedure described in the Developer's Reference (5.12) and the Debian
| Wiki .
|
| Criteria are met as follows:
|
| * The package is in clear need of some love and care: There is an open
|   RC bug: .
| AND
| * An upload is needed to fix this.
| AND
| * At least one to the following applies (non-applicable omitted):
|   * There is no visible activity regarding the package for six months.
|   * A previous NMU was not acknowledged, and a bug justifying another
| NMU is pending for one month.
|   * The last upload was an NMU and there was no maintainer upload within
| one year.
|
| My objective is to have this package in Debian, and in good shape. So
| if you (maintainer) want to resume taking care of it, please do. And in
| case you object or already have other plans, just let me know.
|
| Kind regards,
|
| Christoph





OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003766: libyang must stop building libyang-tools

[Adrian Bunk]

Control: retitle -1 libyang must stop building libyang-tools
Control: tags -1 bookworm sid

On Sat, Jan 15, 2022 at 03:17:22PM +0200, Adrian Bunk wrote:
> Source: libyang
> Version: 1.0.225-1.1
> Severity: serious
> 
> yang-tools is now built by src:libyang2.

Sorry, libyang-tools, not yang-tools.

cu
Adrian

Bug#1003766: libyang must stop building yang-tools

[Adrian Bunk]

Source: libyang
Version: 1.0.225-1.1
Severity: serious

yang-tools is now built by src:libyang2.

Bug#1003714: ITP: oci-cli -- Command Line Interface for Oracle Cloud Infrastructure

[Paul Wise]

On Sat, 2022-01-15 at 12:25 +0100, Thomas Goirand wrote:

> Just please make sure it doesn't conflict with:
> packages.debian.org/openstack-cluster-installer-cli

AFAICT there is nothing that conflicts, except the OCI acronym, which
seems to also be shared with the Open Containers Images specification.

> Hopefully, yours will be oci-cli, when mine is ocicli ...

It is even more generic than that, it claims /usr/bin/oci:

entry_points={
'console_scripts': ["oci=oci_cli.cli:cli",

"create_backup_from_onprem=oci_cli.scripts.database.dbaas:create_backup_from_onprem"]
},

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1003722: jupyter-notebook: blank page in firefox

[Yuri D'Elia]

Package: jupyter-notebook
Version: 6.4.5-3
Followup-For: Bug #1003722

This should be higher priority.

I can confirm I get a JS error upon starting 'jupyter notebook' from the
CLI using either Firefox:

Uncaught ReferenceError: exports is not defined
 
http://localhost:/static/tree/js/main.min.js?v=1165e50a1bd56de1d3cb2eb1f607c410d26e4dc418d1e016a4a3721ca5d697af4ef59e61b3be7082890269c3728083992695ad6156881a27d4b45d88802a4e8b:13852

Or chrome:

marked.js:14 Uncaught ReferenceError: exports is not defined
at marked.js:14:1

This happens when loading the default entry page http://localhost:/tree

A relevant marked.js bug seems to be #1003601 which seems already fixed.
However jupiter might be bundling a broken version?

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

Kernel: Linux 5.15.0-2-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages jupyter-notebook depends on:
ii  init-system-helpers  1.61
ii  jupyter-core 4.9.1-1
ii  python3  3.9.8-1
ii  python3-notebook 6.4.5-3

jupyter-notebook recommends no packages.

jupyter-notebook suggests no packages.

Bug#990168: ejabberd: legacy conffiles leftover

[Jonas Smedegaard]

Hi Phillipp (and Christoph),

Quoting Philipp Huebner (2022-01-15 12:51:53)
> what you have reported here is a leftover of #895371 which only 
> happens on installations << 18.04-1, which is << oldstable a.k.a. 
> Stretch and older.
> 
> I'm reluctant to address this since it does no harm and does not 
> affect any fresh installation on Debian >= 10.

I disagree: I think this still violates Debian Policy § 10.7.3 and 
therefore **does** harm, just only on long-time maintained systems.

I think that a crude way to "solve" this issue might be to add a preinst 
script that checked if the file was registered as a conffile and then 
fail the install with an error message instructing the user to purge 
their too old incompatible installation and then install again from 
scratch.

Slightly less crude (but still pretty crude) might be the above + adding 
a NEWS entry warning that migration from old releases is unsupported and 
requires purge before fresh install.

Ideal would obviously be if there was a way to explicitly tell dpkg to 
stop treating a file as a conffile.

I recommend to ask about this at debian-devel@l.d.o.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

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

signature.asc
Description: signature

Bug#965829:

[Evangelos Ribeiro Tzaras]

Hi,

so I've made a new minimal patch that would only bump the debhelper
compat and not touch anything else.

The resulting binary packages are only minimally different, except for
the doc-package: Superficially it looks the same from browsing through
the html, but some images are now svg instead of png and some
additional html/js files are present which I would attribute to changes
in doxygen.

The revised (minimal) patch is attached. Is there someone willing to
NMU this with the patch applied? I'm only a lowly DM, so I can't upload
myself.

Side note: Trying to use debdiff on the .dsc's it only outputted
changes in debian/changelog, but not in other files (in case you're
wondering why I've not attached a .debdiff)

-- 
Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19



diff -r sofia-sip-1.12.11+20110422.1/debian/changelog sofia-sip-1.12.11+20110422.1.untouched/debian/changelog
1,7d0
< sofia-sip (1.12.11+20110422.1-2.2) unstable; urgency=medium
< 
<   * Non-maintainer upload.
<   * Bump dh-compat to 13 (Closes: #965829)
< 
<  -- Evangelos Ribeiro Tzaras   Sat, 15 Jan 2022 12:03:56 +0100
< 
diff -r sofia-sip-1.12.11+20110422.1/debian/compat sofia-sip-1.12.11+20110422.1.untouched/debian/compat
1c1
< 13
---
> 5
diff -r sofia-sip-1.12.11+20110422.1/debian/control sofia-sip-1.12.11+20110422.1.untouched/debian/control
5c5
< Build-Depends: debhelper (>= 13), pkg-config, libglib2.0-dev, libssl-dev,
---
> Build-Depends: debhelper (>= 5), pkg-config, libglib2.0-dev, libssl-dev,

Bug#965829: sofia-sip: Removal of obsolete debhelper compat 5 and 6 in bookworm

[Evangelos Ribeiro Tzaras]

Hi Niels,

On Mon, 2021-12-27 at 09:54 +0100, Niels Thykier wrote:
> On Wed, 22 Dec 2021 09:37:46 +0100 Evangelos Ribeiro Tzaras
>  wrote:
> > Just as a follow up:
> > 
> > I could imagine adopting the package (possibly within the VoIP
> > team)
> > in case the maintainer is willing to part with it. I don't want to
> > be
> > stepping on any toes, which is why I'm cautiously putting that
> > option
> > on the table :)
> > 
> > Cheers
> > -- 
> > Evangelos
> > PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19
> > 
> > 
> 
> Hi,
> 
> FTR, I think this package might be a candidate for the [ITS process]
> in
> case you are interested in maintaining it.

Thanks for the link! Jonas has filed an [ITS bug].

> 
> ~Niels
> 
> [ITS process]:
> https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
> 
> 

[ITS bug] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003706

Cheers
-- 
Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19

Bug#1003765: bullseye-pu: package node-markdown-it/10.0.0+dfsg-2+deb11u1

[Yadd]

On 15/01/2022 12:52, Yadd wrote:

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

[ Reason ]
node-markdown-it is vulnerable to regex denial of service
(CVE-2022-21670)

[ Impact ]
Little security issue

[ Tests ]
Test passed

[ Risks ]
Low risk, just a better check

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

[ Changes ]
Replace regex by substitute

Same patch applied to unstable.

Cheers,
Yadd


With the debdiff, sorrydiff --git a/debian/changelog b/debian/changelog
index 3f20b0f..1fa8e51 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+node-markdown-it (10.0.0+dfsg-2+deb11u1) bullseye; urgency=medium
+
+  * Fix ReDoS (Closes: CVE-2022-21670)
+
+ -- Yadd   Sat, 15 Jan 2022 12:48:26 +0100
+
 node-markdown-it (10.0.0+dfsg-2) unstable; urgency=medium
 
   * Team Upload
diff --git a/debian/patches/CVE-2022-21670.patch b/debian/patches/CVE-2022-21670.patch
new file mode 100644
index 000..e801f06
--- /dev/null
+++ b/debian/patches/CVE-2022-21670.patch
@@ -0,0 +1,32 @@
+Description: Fix possible ReDOS in newline rule
+Author: Vitaly Puzrin 
+Origin: upstream, https://github.com/markdown-it/markdown-it/commit/ffc49ab4
+Bug: https://github.com/markdown-it/markdown-it/security/advisories/GHSA-6vfc-qv3f-vr6c
+Forwarded: not-needed
+Reviewed-By: Yadd 
+Last-Update: 2022-01-15
+
+--- a/lib/rules_inline/newline.js
 b/lib/rules_inline/newline.js
+@@ -6,7 +6,7 @@
+ 
+ 
+ module.exports = function newline(state, silent) {
+-  var pmax, max, pos = state.pos;
++  var pmax, max, ws, pos = state.pos;
+ 
+   if (state.src.charCodeAt(pos) !== 0x0A/* \n */) { return false; }
+ 
+@@ -20,7 +20,11 @@
+   if (!silent) {
+ if (pmax >= 0 && state.pending.charCodeAt(pmax) === 0x20) {
+   if (pmax >= 1 && state.pending.charCodeAt(pmax - 1) === 0x20) {
+-state.pending = state.pending.replace(/ +$/, '');
++// Find whitespaces tail of pending chars.
++ws = pmax - 1;
++while (ws >= 1 && state.pending.charCodeAt(ws - 1) === 0x20) ws--;
++
++state.pending = state.pending.slice(0, ws);
+ state.push('hardbreak', 'br', 0);
+   } else {
+ state.pending = state.pending.slice(0, -1);
diff --git a/debian/patches/series b/debian/patches/series
index 8c5fbef..3d7d982 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 update_shebang
 disable_babelmark-responder_test
+CVE-2022-21670.patch

Bug#990168: ejabberd: legacy conffiles leftover

[Philipp Huebner]

Hi,

what you have reported here is a leftover of #895371 which only happens
on installations << 18.04-1, which is << oldstable a.k.a. Stretch and older.

I'm reluctant to address this since it does no harm and does not affect
any fresh installation on Debian >= 10.

What I'd need to fix this is a way to unregister /etc/default/ejabberd
as a conffile but leave the file in place.

Using dpkg-maintscript-helper or deb-conffiles would remove the actual
file, which is unacceptable.
Backup+Restore of that file around either of those tools seems to me
like not worth the hassle.

You could simply remove the line from
/var/lib/dpkg/info/ejabberd.conffiles,
but I'm pretty sure I am not allowed to do that from a maintainer script.

I'm CCing Jonas, who reported #895371, for maybe he has a good idea how
to clean this up.

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


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003765: bullseye-pu: package node-markdown-it/10.0.0+dfsg-2+deb11u1

[Yadd]

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

[ Reason ]
node-markdown-it is vulnerable to regex denial of service
(CVE-2022-21670)

[ Impact ]
Little security issue

[ Tests ]
Test passed

[ Risks ]
Low risk, just a better check

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

[ Changes ]
Replace regex by substitute

Same patch applied to unstable.

Cheers,
Yadd

Bug#1003764: argparse: empty mutually_exclusive_group breaks --help

[Trent W. Buck]

Package: libpython3.9-minimal
Version: 3.9.2-1
Severity: normal
File: /usr/lib/python3.9/argparse.py

This works:

#!/usr/bin/python3
import argparse
parser = argparse.ArgumentParser(description='Demonstrate a dumbness in 
python 3.9')
parser.add_mutually_exclusive_group().add_argument('--fred')
parser.parse_args(['--help'])

This errors:

#!/usr/bin/python3
import argparse
parser = argparse.ArgumentParser(description='Demonstrate a dumbness in 
python 3.9')
parser.add_mutually_exclusive_group()
parser.parse_args(['--help'])

This is the error:

Traceback (most recent call last):
  File "", line 5, in 
  File "/usr/lib/python3.9/argparse.py", line 1830, in parse_args
args, argv = self.parse_known_args(args, namespace)
  File "/usr/lib/python3.9/argparse.py", line 1863, in parse_known_args
namespace, args = self._parse_known_args(args, namespace)
  File "/usr/lib/python3.9/argparse.py", line 2072, in _parse_known_args
start_index = consume_optional(start_index)
  File "/usr/lib/python3.9/argparse.py", line 2012, in consume_optional
take_action(action, args, option_string)
  File "/usr/lib/python3.9/argparse.py", line 1940, in take_action
action(self, namespace, argument_values, option_string)
  File "/usr/lib/python3.9/argparse.py", line 1104, in __call__
parser.print_help()
  File "/usr/lib/python3.9/argparse.py", line 2560, in print_help
self._print_message(self.format_help(), file)
  File "/usr/lib/python3.9/argparse.py", line 2544, in format_help
return formatter.format_help()
  File "/usr/lib/python3.9/argparse.py", line 295, in format_help
help = self._root_section.format_help()
  File "/usr/lib/python3.9/argparse.py", line 226, in format_help
item_help = join([func(*args) for func, args in self.items])
  File "/usr/lib/python3.9/argparse.py", line 226, in 
item_help = join([func(*args) for func, args in self.items])
  File "/usr/lib/python3.9/argparse.py", line 333, in _format_usage
action_usage = format(optionals + positionals, groups)
  File "/usr/lib/python3.9/argparse.py", line 408, in _format_actions_usage
start = actions.index(group._group_actions[0])
IndexError: list index out of range


The problem only affects --help; an empty mutex group (without
required=True) still works in regular (non --help) usage.

I think the default --help provider should just skip empty mutex groups.

I think this (UNTESTED!) patch is probably sufficient:

diff -ud --label /tmp/argparse.py --label \#\ 
/tmp/argparse.py /tmp/buffer-content-7I3lfM
--- /tmp/argparse.py
+++ #
@@ -404,6 +404,8 @@
 group_actions = set()
 inserts = {}
 for group in groups:
+if len(group._group_actions) == 0:
+continue
 try:
 start = actions.index(group._group_actions[0])
 except ValueError:

Diff finished.  Sat Jan 15 22:28:23 2022

I guess this is an upstream issue, but
I haven't time today to compare Debian's python to upstream's python.
Sorry about that.



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

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

Versions of packages libpython3.9-minimal:amd64 depends on:
ii  libc6  2.31-13+deb11u2
ii  libssl1.1  1.1.1k-1+deb11u1

Versions of packages libpython3.9-minimal:amd64 recommends:
ii  libpython3.9-stdlib  3.9.2-1

libpython3.9-minimal:amd64 suggests no packages.

-- no debconf information