Bug#1002656: bridge-utils: bridge_hw: add random option like for ifupdown hwaddress

[Martin-Éric Racine]

On Fri, Oct 7, 2022 at 1:01 AM Santiago Garcia Mantinan
 wrote:
> > It would be desirable for bridge_hw to be able to generate a random MAC
> > address as per ifupdown's generic hwaddress syntax.
>
> I don't know if I get this right or not... if you don't want to specify a
> MAC or get it from an interface... then you better not assign any MAC and so
> systemd will do his thing and assign a "random" one.
>
> I really don't think that the code on bridge-utils should generate such a
> random MAC, systemd already causes a lot of trouble by overriding the
> address that the kernel would select, I don't think we need another actor
> here.
>
> Can you justify your request?

The kernel using the MAC of a real device, if none is specified, is
precisely what we wanna avoid.  Systemd is not involed.

Martin-Éric

Bug#1020073: [Debian-pan-maintainers] Bug#1020073: pyfai: FTBFS: distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w

[Adrian Bunk]

On Tue, Sep 27, 2022 at 11:32:32AM +0200, Jerome Kieffer wrote:
> Hi Lucas,
> 
> All my packages (and probably many more) are marked for removal because of 
> this bug.
> 
> I believe this bugs comes from a specificity of Debian which does not
> install python3-pip together with python3. If python3-pip is now needed by
> pybuild it should be a build dependency.

No, the problem is specific to pyfai:

>...
> > > subprocess.CalledProcessError: Command '['/usr/bin/python3.10', '-m', 
> > > 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', 
> > > '/tmp/tmpymrbi1ta', '--quiet', 'setuptools<60.0.0']' returned non-zero 
> > > exit status 1.
>...

It tries to use python3-pip to download an older version of setuptools 
from the internet during the build (downloading from the internet during 
the build is not allowed) because setup.py disallows the version in Debian.

The fix is to make pyfai work with more recent version of setuptools.

cu
Adrian

Bug#642906: RFH: balsa -- An e-mail client for GNOME

[Gervase]

Hi.

I noticed the following in the "Work-needing packages report for Sep 30,
2022" e-mail sent from w...@debian.org to debian-de...@lists.debian.org
on Sep 30...

> For the following packages help is requested:

>balsa (#642906), requested 4022 days ago
>  Description: An e-mail client for GNOME
>  Reverse Depends: balsa
>  Installations reported by Popcon: 604
>  Bug Report URL: https://bugs.debian.org/642906

I might be able to help out here.  But can you tell me exactly what help
is needed?  I may need to do a little preparation work before hand
though.

Thanks,
Gervase.

PS. I noticed that the request for help is also in 
https://www.debian.org/devel/wnpp/help_requested, but there are no
details there about how to reach out to offer help.

Bug#1021376: etckeeper: add commit before running `apt update` using APT::Update::Pre-Invoke

[Paul Wise]

Package: etckeeper
Version: 1.18.18-1
Severity: wishlist

Currently when one changes apt sources and does `apt update`,
the changes to apt sources are only committed later when the
`apt upgrade` command is being run, which means they are somewhat
misattributed to the upgrade, when really they occurred earlier just
before the `apt update` run. The APT::Update::Pre-Invoke option can be
used to commit the apt sources before an `apt update`. The sources
could also be committed afterwards but apt generally doesn't change
/etc during `apt update` but some apt hooks might do that though.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1021375: nmu: intel-compute-runtime_22.39.24347-1

[Andreas Beckmann]

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

nmu intel-compute-runtime_22.39.24347-1 . ANY . unstable . -m "Rebuild against 
intel-graphics-compiler 1.0.11702.15"

intel-compute-runtime has a tight dependency on the
intel-graphics-compiler upstream version.


Andreas

Bug#1021289: apt-listbugs: automatic pinning is not added under unattended-upgrades

[Paul Wise]

Control: retitle -1 apt-listbugs: automatic pinning is not added under 
unattended-upgrades

Refocusing this bug report on the pinning issue.

On Fri, 2022-10-07 at 00:26 +0200, Francesco Poli wrote:

> Specifically, when apt-listbugs sees that its stdout is not a terminal,
> it automatically assume the following options: --quiet --force-pin
> --force-no
> This automatic behavior change should ensure that all buggy packages
> (of the upgrade/installation that is about to happen) are pinned,
> without any interactive prompt.

I tested this again and it definitely is not happening, see below.

Reading the code, it seems the issue is that the save() function is
only ever called by the view() function when the answer is y/n but
never when the answer is p which is set by --force-pin.

> I assume unattended-upgrades runs the package manager without connecting
> stdout to a terminal...

I think that is correct given the output below.

> More investigation is needed in order to figure out why you didn't see
> the pinning added.

Provided some debugging at the end of this mail.

> I assume unattended-upgrades runs the package manager with root
> privileges...

Correct.

> Did you configure unattended-upgrades to attempt the upgrade twice in a
> row (as suggested in the FAQ[^note])?

I hadn't read the FAQ, thanks for the pointer. In this case the pinning
issue would prevent it from working anyway.

> I admit that I am not familiar with unattended-upgrades, hence I am not
> sure how to configure it for the twice-in-a-row upgrade.
> I hope it's easy enough.

I can only configure unattended-upgrades to run more often, there is no
option to ignore failure of a particular upgrade and retry it.

> I think this cannot work, unfortunately.
> 
> In order to know which packages are going to be upgraded (or newly
> installed!), apt-listbugs must receive information from the upgrade (or
> install) session of the package manager.

I see, that makes sense.

Here is the debugging for the pinning issue.

$ apt list --upgradable 
Listing... Done
libreadline-dev/testing,unstable 8.2-1 amd64 [upgradable from: 8.2~rc2-2]
libreadline8-dbgsym/testing-debug,unstable-debug 8.2-1 amd64 [upgradable from: 
8.2~rc2-2]
libreadline8/testing,unstable 8.2-1 amd64 [upgradable from: 8.2~rc2-2]

$ apt upgrade -s
NOTE: This is only a simulation!
  apt needs root privileges for real execution.
  Keep also in mind that locking is deactivated,
  so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libreadline-dev libreadline8 libreadline8-dbgsym
3 upgraded, 0 newly installed, 0 to remove and 20 not upgraded.
Inst libreadline8-dbgsym [8.2~rc2-2] (8.2-1 Debian debug:testing-debug, Debian 
debug:unstable-debug [amd64]) []
Inst libreadline-dev [8.2~rc2-2] (8.2-1 Debian:testing, Debian:unstable 
[amd64]) []
Inst libreadline8 [8.2~rc2-2] (8.2-1 Debian:testing, Debian:unstable [amd64])
Conf libreadline8-dbgsym (8.2-1 Debian debug:testing-debug, Debian 
debug:unstable-debug [amd64])
Conf libreadline-dev (8.2-1 Debian:testing, Debian:unstable [amd64])
Conf libreadline8 (8.2-1 Debian:testing, Debian:unstable [amd64])

$ apt-listbugs list libreadline-dev libreadline8 libreadline8-dbgsym
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of libreadline8 (-> ) 
 b1 - #1021062 - bash: non existent locale crashes bash
Summary:
 libreadline8(1 bug)

$ cat /etc/apt/preferences.d/apt-listbugs 
$

$ systemctl start apt-daily-upgrade.service

$ cat /etc/apt/preferences.d/apt-listbugs 
$

$ tail -n12 /var/log/unattended-upgrades/unattended-upgrades.log
2022-10-07 07:42:26,918 INFO Starting unattended upgrades script
2022-10-07 07:42:26,919 INFO Allowed origins are: 
origin=Debian,codename=bookworm,label=Debian, 
origin=Debian,codename=bookworm,label=Debian-Security, 
origin=Debian,codename=bookworm-security,label=Debian-Security, origin=Debian
2022-10-07 07:42:26,919 INFO Initial blacklist: 
2022-10-07 07:42:26,919 INFO Initial whitelist (not strict): 
2022-10-07 07:42:41,539 INFO Packages that will be upgraded: libreadline-dev 
libreadline8 libreadline8-dbgsym
2022-10-07 07:42:41,540 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2022-10-07 07:42:45,879 ERROR Installing the upgrades failed!
2022-10-07 07:42:45,879 ERROR error message: installArchives() failed
2022-10-07 07:42:45,879 ERROR dpkg returned a error! See 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log for details
2022-10-07 07:42:46,439 INFO Package libreadline-dev is kept back because a 
related package is kept back or due to local apt_preferences(5).
2022-10-07 07:42:46,443 INFO Package libreadline8 is kept back because a 
related package is kept back or due to local apt_preferences(5).
2022-10-07 07:42:46,452 INFO Package libreadline8-dbgsym is 

Bug#845782: NMU for reproducible builds and cross building

[Vagrant Cascadian]

Control: tags 845782 pending
Control: tags 901260 pending

On 2022-10-06, Vagrant Cascadian wrote:
> I've submitted NMUs to DELAYED/10 fixing reproducible builds and cross
> building issues:

Marking as pending.

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#901260: NMU for reproducible builds and cross building

[Vagrant Cascadian]

I've submitted NMUs to DELAYED/10 fixing reproducible builds and cross
building issues:

diff -Nru hannah-1.0/debian/changelog hannah-1.0/debian/changelog
--- hannah-1.0/debian/changelog 2021-01-03 03:25:33.0 -0800
+++ hannah-1.0/debian/changelog 2022-10-06 17:14:03.0 -0700
@@ -1,3 +1,23 @@
+hannah (1.0-3.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make.
+(Closes: #901260)
+
+ -- Vagrant Cascadian   Thu, 06 Oct 2022 
17:14:03 -0700
+
+hannah (1.0-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Reiner Herrmann ]
+  * Sort source files so that objects are linked in deterministic order
+(Closes: #845782)
+
+ -- Vagrant Cascadian   Thu, 06 Oct 2022 
16:48:01 -0700
+
 hannah (1.0-3.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -Nru hannah-1.0/debian/patches/series hannah-1.0/debian/patches/series
--- hannah-1.0/debian/patches/series2015-06-07 10:03:18.0 -0700
+++ hannah-1.0/debian/patches/series2022-10-06 17:14:03.0 -0700
@@ -1,2 +1,3 @@
 fix_score_dir.diff
 fix-compiler-errors
+sort-source-files-so-that-objects-are-li.patch
diff -Nru 
hannah-1.0/debian/patches/sort-source-files-so-that-objects-are-li.patch 
hannah-1.0/debian/patches/sort-source-files-so-that-objects-are-li.patch
--- hannah-1.0/debian/patches/sort-source-files-so-that-objects-are-li.patch
1969-12-31 16:00:00.0 -0800
+++ hannah-1.0/debian/patches/sort-source-files-so-that-objects-are-li.patch
2022-10-06 17:14:03.0 -0700
@@ -0,0 +1,22 @@
+From: Reiner Herrmann 
+Date: Sat, 26 Nov 2016 18:09:46 +0100
+X-Dgit-Generated: 1.0-3.2 643a1240bd171728e30fc90e2af81db2b5a9c9a9
+Subject: Sort source files so that objects are linked in deterministic order
+
+(Closes: #845782)
+
+---
+
+diff --git a/Makefile b/Makefile
+index 643a8e8..4a55a77 100644
+--- a/Makefile
 b/Makefile
+@@ -24,7 +24,7 @@ LIBS = $(shell sdl-config --libs) -lSDL_image -lSDL_ttf 
-lSDL_mixer
+ # target binary and directory name
+ OUT = hhh
+ # source and object files
+-SRCS = $(wildcard *.cc)
++SRCS = $(sort $(wildcard *.cc))
+ OBJS = $(patsubst %.cc, %.o, $(SRCS))
+ 
+ # what to build
diff -Nru hannah-1.0/debian/rules hannah-1.0/debian/rules
--- hannah-1.0/debian/rules 2015-06-07 10:03:18.0 -0700
+++ hannah-1.0/debian/rules 2022-10-06 17:14:03.0 -0700
@@ -9,7 +9,7 @@
dh $@
 
 override_dh_auto_build-arch:
-   $(MAKE) DATA_INSTALL_DIR=/usr/share/games/hannah/ \
+   dh_auto_build -- DATA_INSTALL_DIR=/usr/share/games/hannah/ \
SCOREDIR=/var/games/hannah/ CXXFLAGS="$(CXXFLAGS)" 
CFLAGS="$(CFLAGS)" \
LDFLAGS="$(LDFLAGS)"
 
live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1021374: zephyr: reproducible-builds: build path embedded in libzephyr.so.4.0.0

[Vagrant Cascadian]

Source: zephyr
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 is embedded in
/usr/lib/x86_64-linux-gnu/libzephyr.so.4.0.0:

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

  /build/1st/zephyr-3.1.2/krb5/lib/zephyr_err.c:61
  vs.
  /build/2/zephyr-3.1.2/2nd/krb5/lib/zephyr_err.c:61

The attached patch to debian/rules fixes this by adding
-ffile-prefix-map to CFLAGS.

According to my local tests, with this patch and the patch for #828867
applied, zephyr should build reproducibly on
tests.reproducible-builds.org!

Thanks for maintaining zephyr!

live well,
  vagrant
 From c1dd58714b0bf41effbc7ce4162ac2e0d347fc61 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Fri, 7 Oct 2022 00:06:50 +
Subject: [PATCH 2/2] debian/rules: Pass -ffile-prefix-map via CFLAGS to avoid
 embedding the build path.

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

diff --git a/debian/rules b/debian/rules
index f81ecc9..1e8f9ed 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,7 +9,7 @@
 # Uncomment this to turn on verbose mode. 
 #export DH_VERBOSE=1
 VARIETALS=krb5
-CFLAGS=-g -O
+CFLAGS=-g -O -ffile-prefix-map=$(CURDIR)=.
 
 PACKAGES:=-plibzephyr4 -pzephyr-clients -pzephyr-server -plibzephyr-dev $(foreach i,$(VARIETALS),-plibzephyr4-$(i) -pzephyr-server-$(i))
 
-- 
2.37.2



signature.asc
Description: PGP signature

Bug#1021347: fonts-texgyre: please demote fonts-texgyre-math to Recommends

[Norbert Preining]

Hi

> So, texlive-fonts-recommended recommends tex-gyre and texlive-full pulls it
> in. tex-gyre in turn contains the full set of Type1 fonts, just recommends
> the OpenType fonts (fonts-texgyre & fonts-texgyre-math). So I don't see any
> need for action here.

Ok, that looks ok.

On Thu, 06 Oct 2022, fab...@greffrath.com wrote:
> the fonts-texgyre-* packages contain only the OpenType variants of the

Which are used by luatex ... so "only" is a bit incorrect.

> LaTeX world will be completely unaffected by this.

Disagree.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1021290: apt-listbugs: pinning explanation: add requester and apt command-line

[Paul Wise]

On Fri, 2022-10-07 at 00:33 +0200, Francesco Poli wrote:

> I am not sure I see the use of such additional information

It is useful for accountability on systems where there are multiple
sysadmins who use sudo/etc to get root, to know who did what when.

> but anyway reading /var/log/apt/history.log means that we are
> assuming that apt-listbugs will always be invoked from apt.
> But apt-listbugs supports other package managers, which do not provide
> Commandline/Requested-By fields in history.log (aptitude) or, maybe, do
> not log to /var/log/apt/history.log at all (cupt?).

Sorry, I should have been clearer in my initial bug report.

I was asking for the requestor and command-line to be documented, but
not really for those to be read from the apt history log. The requestor
can be got from the SUDO_* or PKEXEC_UID environment variables, and the
command-line can be got from either SUDO_COMMAND and or by inspecting
the command-line of the parent process using the /proc/12345/cmdline
file. The PKEXEC_UID would need translating to the username of course.

$ sudo env -u FOO env | grep SUDO
SUDO_COMMAND=/usr/bin/env -u FOO env
SUDO_USER=pabs
SUDO_UID=1000
SUDO_GID=1000

$ pkexec env -u FOO env | grep PKEXEC
PKEXEC_UID=1000

$ su 
Password: 
root@localhost /home/pabs # env | grep =pabs$
LOGNAME=pabs
USERNAME=pabs
USER=pabs

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1021373: librep: reproducible-builds: build path embedded in provided libtool

[Vagrant Cascadian]

Source: librep
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 is embedded in /usr/lib/x86_64-linux-gnu/rep/libtool:

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

  
LTCFLAGS="-g·-O2·-ffile-prefix-map=/build/1st/librep-0.92.7=.·-fstack-protector-strong
 ...
  vs.
  
LTCFLAGS="-g·-O2·-ffile-prefix-map=/build/2/librep-0.92.7/2nd=.·-fstack-protector-strong
 ...


According to my local tests, with this patch and the patch for
https://bugs.debian.org/834534 applied, librep should build reproducibly
on tests.reproducible-builds.org!

This patch should apply on either the version in sid or experimental
(which already has the patch for #834534 applied).

Thanks for maintaining librep!

live well,
  vagrant
From 769a91c0c274dc41767d0525db9625ccf677d392 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Thu, 6 Oct 2022 23:04:22 +
Subject: [PATCH 2/2] debian/rules: Remove embedded build path from libtool in
 dh_install override.

https://reproducible-builds.org/docs/build-path/
---
 debian/rules | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/debian/rules b/debian/rules
index c384f44..efdf15d 100755
--- a/debian/rules
+++ b/debian/rules
@@ -35,6 +35,8 @@ override_dh_install:
 	dh_install
 	find $(dev_extras) | $(dh_install_auto) -plibrep-dev
 	find $(rep_extras) | $(dh_install_auto) -prep
+	# Replace build path with placeholder string for reproducible builds
+	sed -i -e "s,$(CURDIR),BUILDPATH,g" debian/librep-dev/usr/lib/$(DEB_HOST_MULTIARCH)/rep/libtool
 
 override_dh_strip:
 	dh_strip -a --dbg-package=librep-dbg
-- 
2.37.2



signature.asc
Description: PGP signature

Bug#1019610: ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError)

[Adrian Bunk]

On Mon, Sep 12, 2022 at 08:24:43PM -0300, Antonio Terceiro wrote:
> Source: ruby-ahoy-email
> Version: 1.1.1-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: debian-r...@lists.debian.org
> Usertags: ruby3.1
> 
> Hi,
> 
> We are about to start the ruby3.1 transition in unstable. While trying to
> rebuild ruby-ahoy-email with ruby3.1 enabled, the build failed.
> 
> Relevant part of the build log (hopefully):
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
> >  `require': cannot load such file -- net/smtp (LoadError)

Do you have any ides where this dependency is required and why it isn't found?

> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
> >  `block in require'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:299:in
> >  `load_dependency'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
> >  `require'
> > from /usr/lib/ruby/vendor_ruby/mail.rb:9:in `'
> > from /usr/lib/ruby/vendor_ruby/mail.rb:3:in `'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
> >  `require'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
> >  `block in require'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:299:in
> >  `load_dependency'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
> >  `require'
> > from 
> > /usr/share/rubygems-integration/all/gems/actionmailer-6.1.6.1/lib/action_mailer/mail_with_error_handling.rb:4:in
> >  `'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
> >  `require'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
> >  `block in require'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:299:in
> >  `load_dependency'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
> >  `require'
> > from 
> > /usr/share/rubygems-integration/all/gems/actionmailer-6.1.6.1/lib/action_mailer/base.rb:3:in
> >  `'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
> >  `require'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
> >  `block in require'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:299:in
> >  `load_dependency'
> > from 
> > /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
> >  `require'
> > from /<>/test/test_helper.rb:21:in `'
> > from /<>/test/click_test.rb:1:in `require_relative'
> > from /<>/test/click_test.rb:1:in `'
> > from 
> > :85:in
> >  `require'
> > from 
> > :85:in
> >  `require'
> > from 
> > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
> >  `block in '
> > from 
> > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in 
> > `select'
> > from 
> > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in 
> > `'
> > rake aborted!
> > Command failed with status (1)
> > 
> > Tasks: TOP => default => test
> > (See full trace by running task with --trace)
> > mv ./.gem2deb.Gemfile.lock Gemfile.lock
> > ERROR: Test "ruby3.1" failed: 
> 
> 
> The full build log is available from:
> https://people.debian.org/~terceiro/ruby3.1/17/ruby-ahoy-email/ruby-ahoy-email_1.1.1-2+rebuild1663007340_amd64-2022-09-12T18:29:01Z.build
>...

cu
Adrian

Bug#1014815: kiwipy initial packaging

[Guilherme Xavier]

Hi Bastian,

I did check the correct package dependencies.

I believe that if you had researched I sent the aio-pika package on
03/08/2022 
(https://tracker.debian.org/news/1351353/accepted-python-aio-pika-803-1-source-all-
into-unstable-unstable/) and the kiwipy package upstream entered the
package's dependency version information in the develop branch on
5/8/2022 
(https://github.com/aiidateam/kiwipy/commit/7750921d7f69f55005a9f69a854f5e0d1a16feb0).

Best,
Guilherme

Em qui., 6 de out. de 2022 às 19:04, Eriberto
 escreveu:
>
> Em qui., 6 de out. de 2022 às 18:45, Bastian Germann  
> escreveu:
> >
> > Am 06.10.22 um 20:19 schrieb Eriberto Mota:
> > > Am 05.10.22 um 14:59 schrieb Guilherme Xavier:
> > >>> Hi,
> > >>>
> > >>> Agree, downgrading would be an option.
> > >>> I don't know how this can be done, but I'm open to doing it.
> > >>
> > >> You import the older version as 8.1.1+really6.8.1-1
> > >
> > >
> > > Nope. Downgrading is a workaround for new upstream versions full broken,
> > > but already sent to Debian. Is dangerous and undesirable to reintroduce
> > > an old version of a software to make it "a good dependency". This action
> > > may generate critical bugs or introduce security holes. The right way is
> > > ask to the upstream to update the software to use the current version of
> > > a dependency. In other words, "+really" must be used in very extreme
> > > cases only, not for adjustments.
> >
> > In general, I agree with you. But as far as I can see, Guilherme introduced
> > python-aio-pika for the sake of packaging kiwipy and probably has not 
> > checked
> > compatiblity before packaging that. It is not in use by any other package.
> > So for me this would be okay. It is in the archive for two months now and
> > popcon is at 1. I do not think that upstream will have the issue fixed soon
> > and it would be a pity if Guilherme's packaging work (there are some more 
> > deps
> > introduced for kiwipy) would not be fruitful for him in the sense of having 
> > it
> > available in bookworm.
>
> Ok, this is commendable. However, keeping Debian (as OS) secure is
> more important than any effort to package anything.



-- 
Guilherme de Paula Xavier Segundo
GPG: 4096R/976B8AC9
GPG Fingerprint: 1808D92674863C2E07B7B08C1B140644976B8AC9

Bug#850735: the: FTBFS if ncurses5-config is not present

[Vagrant Cascadian]

Control: tags 850735 moreinfo

On 2018-02-28, Sven Joachim wrote:
> On 2017-01-09 21:08 +0100, Sven Joachim wrote:
>> Source: the
>> Version: 3.3~rc1-3
>> User: ncur...@packages.debian.org
>> Usertags: ncurses5-config
>>
>> The ncurses development packages are going to see a change after the
>> Stretch release, ncurses5-config will be replaced by ncurses6-config.
>> Your package FTBFS if ncurses5-config is not present on the build
>> system.  From my pbuilder log:
>>
>> ,
>> | checking for ncurses5-config... no
>> | checking for location of ncurses.h header file... found in /usr/include
>> | checking for location of ncurses library file... configure: error:
>> | Cannot find curses library file: ncurses; cannot configure
>> | debian/rules:23: recipe for target 'stamp-configure' failed
>> | make: *** [stamp-configure] Error 1
>> | dpkg-buildpackage: error: debian/rules build gave error exit status 2
>> `
>
> This still happens, now reproducible by installing libncurses-dev from
> experimental.

I was able to build it just now, and the reproducible-builds
infrastructure is able to build it (though not currently reproducibly)
as recently as August:

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

What is needed to trigger this failure, or can this bug be closed?

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1021372: libsqlite0: not coïnstallable

[Thorsten Glaser]

Package: libsqlite0
Version: 2.8.17-15
Severity: important
X-Debbugs-Cc: t...@mirbsd.de

This library package lacks the Multi-Arch: same annotation
but looks like it could easily get it.

I have legacy applications that are hard to recompile for which I
need libsqlite0:i386, but to install that apt wants to remove sqlite
(so I had to install sqlite:i386 which pulls in other :i386 libs
unnecessarily).


-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (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_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages libsqlite0 depends on:
ii  libc6  2.31-13+deb11u4

libsqlite0 recommends no packages.

libsqlite0 suggests no packages.

-- no debconf information

Bug#1021290: apt-listbugs: pinning explanation: add requester and apt command-line

[Francesco Poli]

Control: tags -1 + wontfix


On Wed, 05 Oct 2022 09:31:27 +0800 Paul Wise wrote:

> Package: apt-listbugs
> Version: 0.1.36
> Severity: wishlist

Hello again Paul,
thanks for filing this other bug report!

> 
> The explanation for apt pinning currently looks like the one below.
> 
>Explanation: Pinned by apt-listbugs at 2022-10-05 09:10:39 +0800
>Explanation:   #1021062: bash: non existent locale crashes bash
>Package: libreadline8
>Pin: version 8.2~rc2-2
>Pin-Priority: 3
> 
> It would be useful to sysadmins if the apt Commandline/Requested-By
> fields from the apt history.log were present too, something like this:
> 
>Explanation: Pinned by apt-listbugs at 2022-10-05 09:10:39 +0800
>Explanation: Pinning requested by pabs (1000) during command: apt upgrade
>Explanation:   #1021062: bash: non existent locale crashes bash
>Package: libreadline8
>Pin: version 8.2~rc2-2
>Pin-Priority: 3

I am not sure I see the use of such additional information, but anyway
reading /var/log/apt/history.log means that we are assuming that
apt-listbugs will always be invoked from apt.
But apt-listbugs supports other package managers, which do not provide
Commandline/Requested-By fields in history.log (aptitude) or, maybe, do
not log to /var/log/apt/history.log at all (cupt?).

Hence, I am afraid this feature cannot be added.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpE5w3QrlMuZ.pgp
Description: PGP signature

Bug#1021371: (no subject)

[Albert Nash]

severity 1021371 important
affects 1021371 - control:
affects 1021371 - severity:
affects 1021371 - important
affects 1021371 - affects
affects 1021371 - version:
affects 1021371 - -1
affects 1021371 - 1:3.38.4-1
thanks
Some more data:
$ sudo aptitude show libsmbclient | grep Version
Version: 2:4.13.13+dfsg-1~deb11u5
$ sudo aptitude show samba-libs | grep Version
Version: 2:4.13.13+dfsg-1~deb11u5
(Sorry for the mess with the header: I tried my best to say that exactly two 
packages are affected: gnome-control-center and samba-libs. Something went 
wrong with the header 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1021371;msg=5 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1021371;msg=5; I don't 
know what.)

Bug#842550: the: please make the build reproducible

[Vagrant Cascadian]

Control: tags 842550 pending

On 2016-10-30, Reiner Herrmann wrote:
> While working on the "reproducible builds" effort [1], we have noticed
> that 'the' could not be built reproducibly.
> The sorting of the md5sums file varies with different locales, and the
> generated documentation contains build timestamps.
>
> The attached patch fixes this.

Upload an NMU to DELAYED/10 applying a variation of this patch:

diff -Nru the-3.3~rc1/debian/changelog the-3.3~rc1/debian/changelog
--- the-3.3~rc1/debian/changelog2016-08-10 00:56:45.0 -0700
+++ the-3.3~rc1/debian/changelog2022-10-06 15:12:42.0 -0700
@@ -1,3 +1,13 @@
+the (3.3~rc1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Reiner Herrmann ]
+  * Generate reproducible documentation (Closes: #842550)
+  * Sort the md5sums file. (Closes: #842550)
+
+ -- Vagrant Cascadian   Thu, 06 Oct 2022 
15:12:42 -0700
+
 the (3.3~rc1-3) unstable; urgency=low
 
   * Applied patches from Maria Valentina Marin 
diff -Nru the-3.3~rc1/debian/md5_sums the-3.3~rc1/debian/md5_sums
--- the-3.3~rc1/debian/md5_sums 2010-01-28 09:34:54.0 -0800
+++ the-3.3~rc1/debian/md5_sums 2022-10-06 15:12:42.0 -0700
@@ -7,7 +7,7 @@
 for TMPDIR; do
find debian/${TMPDIR}/* -type f ! -regex "^debian/${TMPDIR}/DEBIAN/.*" \
  ! -regex "^debian/${TMPDIR}/etc/.*" | \
-  sed s@debian/${TMPDIR}/@@g | sort > ${TMP_FILE}
+  sed s@debian/${TMPDIR}/@@g | LC_ALL=C sort > 
${TMP_FILE}
cd debian/${TMPDIR}  
xargs < ../../${TMP_FILE} md5sum > DEBIAN/md5sums
cd ../../
diff -Nru 
the-3.3~rc1/debian/patches/generate-reproducible-documentation-clos.patch 
the-3.3~rc1/debian/patches/generate-reproducible-documentation-clos.patch
--- the-3.3~rc1/debian/patches/generate-reproducible-documentation-clos.patch   
1969-12-31 16:00:00.0 -0800
+++ the-3.3~rc1/debian/patches/generate-reproducible-documentation-clos.patch   
2022-10-06 15:12:42.0 -0700
@@ -0,0 +1,40 @@
+From: Reiner Herrmann 
+Date: Sun, 30 Oct 2016 12:47:53 +0100
+X-Dgit-Generated: 3.3~rc1-3.1 634e2b177616b31752934f174a55a6f70fe1f239
+Subject: Generate reproducible documentation (Closes: #842550)
+
+- Use fixed copyright year
+- Don't embed generation timestamp
+
+---
+
+diff --git a/man2html.rex b/man2html.rex
+index 4505f8c..2ab6ae5 100644
+--- a/man2html.rex
 b/man2html.rex
+@@ -1137,9 +1137,8 @@ Return
+ footing: Procedure Expose html_ext
+ Parse Arg src .
+ Say ''
+-Say 'The Hessling Editor is Copyright  http://www.rexx.org/;>Mark Hessling, 1990-'Left( Date('S'), 4 )
++Say 'The Hessling Editor is Copyright  http://www.rexx.org/;>Mark Hessling, 1990-2011'
+ Say 'mailto:m...@rexx.org;>m...@rexx.org'
+-Say 'Generated on:' Date()
+ Say ''
+ If src \= 'TOC' Then Say 'Return to  
Table of Contents '
+ Say ' '
+diff --git a/man2hv.rex b/man2hv.rex
+index 19bc63e..ad22752 100644
+--- a/man2hv.rex
 b/man2hv.rex
+@@ -1228,9 +1228,8 @@ Return
+ footing: Procedure Expose html_ext ?port ?slash ?os
+ Parse Arg fn src .
+ Call Lineout fn, ''
+-Call Lineout fn, 'The Hessling Editor is Copyright  http://www.rexx.org/;>Mark Hessling, 1990-'Left( Date('S'), 4 )
++Call Lineout fn, 'The Hessling Editor is Copyright  http://www.rexx.org/;>Mark Hessling, 1990-2011'
+ Call Lineout fn, 'mailto:m...@rexx.org;>m...@rexx.org'
+-Call Lineout fn, 'Generated on:' Date()
+ Call Lineout fn, ''
+ If src \= 'TOC' Then Call Lineout fn, 'Return to  Table of Contents '
+ Call Lineout fn, ' '
diff -Nru the-3.3~rc1/debian/patches/series the-3.3~rc1/debian/patches/series
--- the-3.3~rc1/debian/patches/series   2012-06-30 08:20:52.0 -0700
+++ the-3.3~rc1/debian/patches/series   2022-10-06 15:12:42.0 -0700
@@ -1 +1,2 @@
 az-patch-01
+generate-reproducible-documentation-clos.patch






signature.asc
Description: PGP signature

Bug#1021289: apt-listbugs: behaviour under unattended-upgrades is suboptimal; do pinning in `apt update` step?

[Francesco Poli]

Control: tags -1 + moreinfo


On Wed, 05 Oct 2022 09:18:55 +0800 Paul Wise wrote:

> Package: apt-listbugs
> Version: 0.1.36
> Severity: normal

Hi Paul,
thanks for your bug report.

> 
> The behaviour of apt-listbugs under unattended-upgrades is suboptimal:
> 
>  * It causes the apt run to abort before it can start.
>     - With minimal steps mode some packages may be upgraded, but once a
>   bug is found, no subsequent package upgrade steps can be run.
>  * The messages say that pinning is being added but they are not added.

This sounds awkward to me, since there's code in apt-listbugs to detect
non-interactive sessions and modify the behavior accordingly.

Specifically, when apt-listbugs sees that its stdout is not a terminal,
it automatically assume the following options: --quiet --force-pin
--force-no
This automatic behavior change should ensure that all buggy packages
(of the upgrade/installation that is about to happen) are pinned,
without any interactive prompt.

I assume unattended-upgrades runs the package manager without connecting
stdout to a terminal...
More investigation is needed in order to figure out why you didn't see
the pinning added.
I assume unattended-upgrades runs the package manager with root
privileges...

> 
> Since unattended-upgrades are not interactive the user can never
> interact with apt-listbugs to add pinning and cannot restart the apt
> session, which is currently required for the pinning to take effect.

Did you configure unattended-upgrades to attempt the upgrade twice in a
row (as suggested in the FAQ[^note])?

[^note]: see /usr/share/doc/apt-listbugs/FAQ.md.gz

I admit that I am not familiar with unattended-upgrades, hence I am not
sure how to configure it for the twice-in-a-row upgrade.
I hope it's easy enough.

> 
> For this reason I suggest that when in non-interactive mode, a hook for
> APT::Update::Post-Invoke (run by `apt update`) is added that will
> invoke apt-listbugs and add pinning for any packages that need pinning
> added and removing any that no longer apply.

I think this cannot work, unfortunately.

In order to know which packages are going to be upgraded (or newly
installed!), apt-listbugs must receive information from the upgrade (or
install) session of the package manager.

The update of the repository indexes is not enough, since the package
manager does not yet know what the user will request (just install one
or two packages? upgrade all the package that can be upgraded? upgrade
only some packages? nothing at all for the time being, since the
upgrade/install will happen later?).

And apt-listbugs would anyway be unable to distinguish between
non-interactive repository index updates and non-interactive updates
immediately followed by non-interactive upgrades.
I mean: some users desire unattended repository index updates, but want
to do the package upgrade interactively. If apt-listbugs is invoked
during an "update" and sees that stdout is not a terminal, how can it
tell whether this is an unattended "update" or an unattended "update +
upgrade"?

[...]
> Please set the Explanation field to say that the package pin was added
> automatically, so that sysadmins reading it understand that the pin was
> added by apt-listbugs rather than being set by a sysadmin.

This could perhaps be done, but I am not sure I see its usefulness.

A sysadmin who uses some unattended package upgrade mechanism will see
a good number of automatically added pins. Possibly (almost) never a
pin added during an interactive session.
On the other hand, a sysadmin who does not use any unattended package
upgrade mechanism, will only see interactively added pins.



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp136t3XhTFX.pgp
Description: PGP signature

Bug#1021186: bullseye-pu: package debmirror/1:2.35+deb11u1

[Colin Watson]

On Tue, Oct 04, 2022 at 06:38:49PM +0100, Adam D. Barratt wrote:
> On Mon, 2022-10-03 at 14:05 +0100, Colin Watson wrote:
> > +debmirror (1:2.35+deb11u1) UNRELEASED; urgency=medium
> > +
> > +  * Add non-free-firmware to the default sections.
> 
> With the presumed s/UNRELEASED/bullseye/, please go ahead.

Indeed.  Uploaded, thanks.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1021371: gnome-control-center doesn't start, saying libsamdb-common.so.0 requires version `LDB_2.2.4'

[Albert Nash]

Package: gnome-control-center Version: 1:3.38.4-1 Severity: important Control: 
affects -1 samba-libs
The control center starts neither from gnome (Alt+F1 > Settings) nor from an 
xterm. In the last case, we get some (hopefully, useful) output:
$ gnome-control-center
gnome-control-center: /lib/x86_64-linux-gnu/libldb.so.2: version `LDB_2.2.4' 
not found (required by /usr/lib/x86_64-linux-gnu/samba/libsamdb-common.so.0)
$
(I presume that some dependencies of samba-libs or gnome-control-center are 
outdated or simply wrong.) The system is Debian stable 11 “bullseye” with a few 
updated packages from Debian testing. I'd be happy if this bug report finds 
attention soon because the package, as of now, is useless to me: the control 
center won't start (e.g., I have no means to adjust printers or screens).
Thanks in advance, Albert

Bug#1019609: ruby-activerecord-import: diff for NMU version 1.4.0-0.1

[Adrian Bunk]

Control: tags 1019609 + patch
Control: tags 1019609 + pending

Dear maintainer,

I've prepared an NMU for ruby-activerecord-import (versioned as 1.4.0-0.1)
and uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru ruby-activerecord-import-1.2.0/activerecord-import.gemspec ruby-activerecord-import-1.4.0/activerecord-import.gemspec
--- ruby-activerecord-import-1.2.0/activerecord-import.gemspec	2021-08-22 17:59:37.0 +0300
+++ ruby-activerecord-import-1.4.0/activerecord-import.gemspec	2022-05-06 10:10:54.0 +0300
@@ -16,8 +16,8 @@
   gem.require_paths = ["lib"]
   gem.version   = ActiveRecord::Import::VERSION
 
-  gem.required_ruby_version = ">= 2.0.0"
+  gem.required_ruby_version = ">= 2.4.0"
 
-  gem.add_runtime_dependency "activerecord", ">= 3.2"
+  gem.add_runtime_dependency "activerecord", ">= 4.2"
   gem.add_development_dependency "rake"
 end
diff -Nru ruby-activerecord-import-1.2.0/benchmarks/benchmark.rb ruby-activerecord-import-1.4.0/benchmarks/benchmark.rb
--- ruby-activerecord-import-1.2.0/benchmarks/benchmark.rb	2021-08-22 17:59:37.0 +0300
+++ ruby-activerecord-import-1.4.0/benchmarks/benchmark.rb	2022-05-06 10:10:54.0 +0300
@@ -20,7 +20,11 @@
 ActiveRecord::Base.configurations["test"] = YAML.load_file(File.join(benchmark_dir, "../test/database.yml"))[options.adapter]
 ActiveRecord::Base.logger = Logger.new("log/test.log")
 ActiveRecord::Base.logger.level = Logger::DEBUG
-ActiveRecord::Base.default_timezone = :utc
+if ActiveRecord.respond_to?(:default_timezone)
+  ActiveRecord.default_timezone = :utc
+else
+  ActiveRecord::Base.default_timezone = :utc
+end
 
 require "activerecord-import"
 ActiveRecord::Base.establish_connection(:test)
diff -Nru ruby-activerecord-import-1.2.0/CHANGELOG.md ruby-activerecord-import-1.4.0/CHANGELOG.md
--- ruby-activerecord-import-1.2.0/CHANGELOG.md	2021-08-22 17:59:37.0 +0300
+++ ruby-activerecord-import-1.4.0/CHANGELOG.md	2022-05-06 10:10:54.0 +0300
@@ -1,3 +1,22 @@
+## Changes in 1.4.0
+
+### New Features
+
+  * Enable compatibility with frozen string literals. Thanks to @desheikh via \##760.
+
+## Changes in 1.3.0
+
+### Fixes
+
+* Ensure correct timestamp values are returned for models after insert. Thanks to @kos1kov via \##756.
+* Restore database_version method to public scope. Thanks to @beauraF via \##753.
+
+### New Features
+
+* Add support for ActiveRecord 7.0. Thanks to @nickhammond, @ryanwood, @jkowens via \##749 and \##752.
+* Add support for compound foreign keys. Thanks to @Uladzimiro via \##750.
+* Add support for :recursive combined with on_duplicate_key_update: :all. Thanks to @deathwish via \##746.
+
 ## Changes in 1.2.0
 
 ### Fixes
diff -Nru ruby-activerecord-import-1.2.0/debian/changelog ruby-activerecord-import-1.4.0/debian/changelog
--- ruby-activerecord-import-1.2.0/debian/changelog	2021-11-21 21:51:35.0 +0200
+++ ruby-activerecord-import-1.4.0/debian/changelog	2022-10-07 00:54:00.0 +0300
@@ -1,3 +1,11 @@
+ruby-activerecord-import (1.4.0-0.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * New upstream release.
+- Fixes FTBFS. (Closes: #1019609)
+
+ -- Adrian Bunk   Fri, 07 Oct 2022 00:54:00 +0300
+
 ruby-activerecord-import (1.2.0-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru ruby-activerecord-import-1.2.0/Gemfile ruby-activerecord-import-1.4.0/Gemfile
--- ruby-activerecord-import-1.2.0/Gemfile	2021-08-22 17:59:37.0 +0300
+++ ruby-activerecord-import-1.4.0/Gemfile	2022-05-06 10:10:54.0 +0300
@@ -22,11 +22,12 @@
   gem "mysql2", "~> #{mysql2_version}"
   gem "pg", "~> #{pg_version}"
   gem "sqlite3","~> #{sqlite3_version}"
-  gem "seamless_database_pool", "~> 1.0.20"
+  # seamless_database_pool requires Ruby ~> 2.0
+  gem "seamless_database_pool", "~> 1.0.20" if Gem::Version.new(RUBY_VERSION) < Gem::Version.new('3.0.0')
 end
 
 platforms :jruby do
-  gem 'jdbc-mysql', '< 8', require: false
+  gem "jdbc-mysql"
   gem "jdbc-postgres"
   gem "activerecord-jdbcsqlite3-adapter","~> 1.3"
   gem "activerecord-jdbcmysql-adapter",  "~> 1.3"
@@ -44,14 +45,9 @@
   gem "ruby-debug", "= 0.10.4"
 end
 
-platforms :mri_19 do
-  gem "debugger"
-end
-
 platforms :ruby do
   gem "pry-byebug"
   gem "pry", "~> 0.12.0"
-  gem "rb-readline"
 end
 
 if version >= 4.0
diff -Nru ruby-activerecord-import-1.2.0/gemfiles/3.2.gemfile ruby-activerecord-import-1.4.0/gemfiles/3.2.gemfile
--- ruby-activerecord-import-1.2.0/gemfiles/3.2.gemfile	2021-08-22 17:59:37.0 +0300
+++ ruby-activerecord-import-1.4.0/gemfiles/3.2.gemfile	1970-01-01 02:00:00.0 +0200
@@ -1,2 +0,0 @@
-gem 'activerecord', '~> 3.2.0'
-gem 'composite_primary_keys', '~> 5.0'
diff -Nru ruby-activerecord-import-1.2.0/gemfiles/4.0.gemfile ruby-activerecord-import-1.4.0/gemfiles/4.0.gemfile
--- ruby-activerecord-import-1.2.0/gemfiles/4.0.gemfile	2021-08-22 17:59:37.0 +0300
+++ 

Bug#1021370: pipewire: build with bluez5-codec-aac=enabled

[KeyofBlueS]

Package: pipewire
Version: 0.3.59-1
Severity: wishlist
X-Debbugs-Cc: keyofbl...@gmail.com

Dear Maintainer,

please build pipewire with aac codec support enabled. If this is not possible
due to legal\patent issues, please mention it somewhere in the readme and/or in
the description, maybe in the debian wiki too.
I've spent months to understand why my bluetooth (aac) devices wont pick this
codec, looking in config files, installing and removing packages ecc...
Now i've compiled and installed from sources and it's working, but as i said,
mention it somewhere can be usefull to other users, giving us some clues on
what's going on.

Thanks and best regards.


-- 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.18.5-custom (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 pipewire depends on:
ii  init-system-helpers  1.65.2
ii  libpipewire-0.3-modules  0.3.59-1-custom
ii  pipewire-bin 0.3.59-1-custom

pipewire recommends no packages.

pipewire suggests no packages.

-- no debconf information

Bug#1019340: Segfaults on startup

[Daniele Forsi]

Christoph Berg wrote:

> Is it just broken for me and Bernhard, or for most people?

the version from package 4.36-2 works for me, with "LC_ALL=C tucnak"
and without LC_ALL set

-- 
73 de IU5HKX Daniele

Bug#1002656: bridge-utils: bridge_hw: add random option like for ifupdown hwaddress

[Santiago Garcia Mantinan]

Hi!

> It would be desirable for bridge_hw to be able to generate a random MAC
> address as per ifupdown's generic hwaddress syntax.

I don't know if I get this right or not... if you don't want to specify a
MAC or get it from an interface... then you better not assign any MAC and so
systemd will do his thing and assign a "random" one.

I really don't think that the code on bridge-utils should generate such a
random MAC, systemd already causes a lot of trouble by overriding the
address that the kernel would select, I don't think we need another actor
here.

Can you justify your request?

Otherwise I'll close the bug.

Regards.
-- 
Manty/BestiaTester -> http://manty.net

Bug#1014815: kiwipy initial packaging

[Eriberto]

Em qui., 6 de out. de 2022 às 18:45, Bastian Germann  escreveu:
>
> Am 06.10.22 um 20:19 schrieb Eriberto Mota:
> > Am 05.10.22 um 14:59 schrieb Guilherme Xavier:
> >>> Hi,
> >>>
> >>> Agree, downgrading would be an option.
> >>> I don't know how this can be done, but I'm open to doing it.
> >>
> >> You import the older version as 8.1.1+really6.8.1-1
> >
> >
> > Nope. Downgrading is a workaround for new upstream versions full broken,
> > but already sent to Debian. Is dangerous and undesirable to reintroduce
> > an old version of a software to make it "a good dependency". This action
> > may generate critical bugs or introduce security holes. The right way is
> > ask to the upstream to update the software to use the current version of
> > a dependency. In other words, "+really" must be used in very extreme
> > cases only, not for adjustments.
>
> In general, I agree with you. But as far as I can see, Guilherme introduced
> python-aio-pika for the sake of packaging kiwipy and probably has not checked
> compatiblity before packaging that. It is not in use by any other package.
> So for me this would be okay. It is in the archive for two months now and
> popcon is at 1. I do not think that upstream will have the issue fixed soon
> and it would be a pity if Guilherme's packaging work (there are some more deps
> introduced for kiwipy) would not be fruitful for him in the sense of having it
> available in bookworm.

Ok, this is commendable. However, keeping Debian (as OS) secure is
more important than any effort to package anything.

Bug#1010875: ust: Bogus Build-Dependency makes package BD-Uninstallable on hppa

[John David Anglin]

Source: ust
Version: 2.13.4-1
Followup-For: Bug #1010875

Dear Maintainer,

Changing the control file to use "" instead of ""
resolves the dependency problem on hppa.

Regards,
Dave Anglin

-- System Information:
Debian Release: bookworm/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 5.19.14+ (SMP w/4 CPU threads)
Locale: LANG=C, 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)

Bug#1014815: kiwipy initial packaging

[Bastian Germann]

Am 06.10.22 um 20:19 schrieb Eriberto Mota:

Am 05.10.22 um 14:59 schrieb Guilherme Xavier:

Hi,

Agree, downgrading would be an option.
I don't know how this can be done, but I'm open to doing it.


You import the older version as 8.1.1+really6.8.1-1



Nope. Downgrading is a workaround for new upstream versions full broken,
but already sent to Debian. Is dangerous and undesirable to reintroduce
an old version of a software to make it "a good dependency". This action
may generate critical bugs or introduce security holes. The right way is
ask to the upstream to update the software to use the current version of
a dependency. In other words, "+really" must be used in very extreme
cases only, not for adjustments.


In general, I agree with you. But as far as I can see, Guilherme introduced
python-aio-pika for the sake of packaging kiwipy and probably has not checked
compatiblity before packaging that. It is not in use by any other package.
So for me this would be okay. It is in the archive for two months now and
popcon is at 1. I do not think that upstream will have the issue fixed soon
and it would be a pity if Guilherme's packaging work (there are some more deps
introduced for kiwipy) would not be fruitful for him in the sense of having it
available in bookworm.

Bug#829755: NMU fixing reproducible builds and cross building issues

[Vagrant Cascadian]

Control: tags 829755 pending
Control: tags 901345 pending

I've uploaded an NMU to DELAYED/10 fixing reproducible builds and cross
building issues:

diff -Nru elvis-tiny-1.4/debian/changelog elvis-tiny-1.4/debian/changelog
--- elvis-tiny-1.4/debian/changelog 2016-11-11 07:20:53.0 -0800
+++ elvis-tiny-1.4/debian/changelog 2022-10-06 14:10:44.0 -0700
@@ -1,3 +1,16 @@
+elvis-tiny (1.4-24.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Reiner Herrmann ]
+  * Strip build date to enable reproducible building. (Closes: #829755)
+
+  [ Helmut Grohne ]
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make.
+(Closes: #901345)
+
+ -- Vagrant Cascadian   Thu, 06 Oct 2022 
14:10:44 -0700
+
 elvis-tiny (1.4-24) unstable; urgency=low
 
   * remove bin/vi wrapper, incompatible with / + /usr merge (closes: 
#540928,#813857)
diff -Nru elvis-tiny-1.4/debian/patches/series 
elvis-tiny-1.4/debian/patches/series
--- elvis-tiny-1.4/debian/patches/series2012-06-29 13:36:03.0 
-0700
+++ elvis-tiny-1.4/debian/patches/series2022-10-06 14:10:44.0 
-0700
@@ -11,3 +11,4 @@
 patch-bug-258640.diff
 patch-siglongjmp.diff
 patch-fix-resize.diff
+strip-build-date-to-enable-reproducible-.patch
diff -Nru 
elvis-tiny-1.4/debian/patches/strip-build-date-to-enable-reproducible-.patch 
elvis-tiny-1.4/debian/patches/strip-build-date-to-enable-reproducible-.patch
--- 
elvis-tiny-1.4/debian/patches/strip-build-date-to-enable-reproducible-.patch
1969-12-31 16:00:00.0 -0800
+++ 
elvis-tiny-1.4/debian/patches/strip-build-date-to-enable-reproducible-.patch
2022-10-06 14:10:44.0 -0700
@@ -0,0 +1,24 @@
+From: Reiner Herrmann 
+Date: Tue, 5 Jul 2016 21:25:37 +0200
+X-Dgit-Generated: 1.4-24.1 a916d656222970d87859c16014646663d51286e1
+Subject: Strip build date to enable reproducible building
+
+(Closes: #829755)
+
+If DATE is not defined, the C file doesn't embed it, so no change is
+required there.
+
+---
+
+diff --git a/Makefile.mix b/Makefile.mix
+index 38f2774..bd7a8d0 100644
+--- a/Makefile.mix
 b/Makefile.mix
+@@ -49,7 +49,6 @@ CFLAGS=  -O2 -DM_SYSV -DCRUNCH -DNO_MKEXRC 
-DNO_CURSORSHAPE -DNO_CHARATTR \
+   -fsigned-char $(EXTRA_CFLAGS)
+ OF=   -o 
+ RF=   -c
+-DATE= -DDATE=\'\"`date`\"\'
+ EVAL= eval 
+ PROGS=elvis
+ CHMEM=
diff -Nru elvis-tiny-1.4/debian/rules elvis-tiny-1.4/debian/rules
--- elvis-tiny-1.4/debian/rules 2016-11-11 07:05:43.0 -0800
+++ elvis-tiny-1.4/debian/rules 2022-10-06 14:10:44.0 -0700
@@ -6,10 +6,10 @@
 endif
 
 %:
-   dh $@
+   dh $@ --buildsystem=makefile
 
 override_dh_auto_build:
-   make -f Makefile.mix EXTRA_CFLAGS="$(EXTRA_CFLAGS)"
+   dh_auto_build -- -f Makefile.mix EXTRA_CFLAGS="$(EXTRA_CFLAGS)"
 
 override_dh_auto_install:
install -m 755 -d $(tmp)/bin


signature.asc
Description: PGP signature

Bug#993716: I think this should be fixed on ifupdown

[Santiago Garcia Mantinan]

Hi!

I'd like to sum this up.

The problem comes when we create a bridge with an IPv6 but without assigning
any ports to it.

What happens then is that DAD is triggered and ifupdown fails to bring the
interface up as DAD times out.

Waiting for DAD... Timed out
ifup: failed to bring up br1

We can just sugest to set dad-attempts to 0 when using bridges without
ports, but maybe that's not a good thing as the bridge can have the ports
attached later and DAD would be needed then.

Other than that, all I can think of is fixing it on ifupdown by not failing
on DAD timeout or even not doing DAD at all if the interface is a bridge
without ports, but maybe that is too complicated.

I'll be around with an eye on the bug, in case you need help or want to
discuss anything just cc me.

Regards...
-- 
Manty/BestiaTester -> http://manty.net

Bug#993716: bridge-utils: IPv6 network bridge fails after upgrading Buster to Bullseye

[Santiago Garcia Mantinan]

Hi!

On Set 06 2021, Pieter Hollander wrote:
> PS: Additionally, I forgot to mention that adding dad-attempts 0 to the br0
> inet6 config also solves the issues of networking failing.

> > Using a dummy port to perform DAD sounds like the best solution to me.

> > Back to the workaround: It also solves the problems I encountered with
> > Unbound & PostgreSQL being unable to bind to the IPv6 interface address
> > specified.

Sorry for coming back to this so late... going over it now I see that I
didn't get which of the workarounds worked for you.

Did you add a dummy port? if so... can you send a config example?

If not... how did you fixed this?

Regards.
-- 
Manty/BestiaTester -> http://manty.net

Bug#980507: Closing this bug

[Santiago Garcia Mantinan]

It looks like the latest changes we did before Bullseye are working, so I'm
changing the interfaces man page removing the stp warning pointing to the
736336 bug report as that was no longer true.

With this change I'm marking this bug closed.

Regards.
-- 
Manty/BestiaTester -> http://manty.net

Bug#1021320: isc-dhcp: diff for NMU version 4.4.3-2.1

[Salvatore Bonaccorso]

Control: tags 1021320 + patch
Control: tags 1021320 + pending


Dear maintainer,

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

This follows for updates already done in bullseye, so we have not a
regression. Cf. DSA 5251-1.

Pushed as well to

https://salsa.debian.org/debian/isc-dhcp/-/tree/security-2022-10-05
https://salsa.debian.org/debian/isc-dhcp/-/tags/debian%2F4.4.3-2.1

(creating a proper merge request does not seem possible for the
project), but the tag can be merged into master branch once/if the NMU
is accepted in the archive.

Let me as well know if you would be fine with the NMU and have it
moved faster.

Regards,
Salvatore
diff -Nru isc-dhcp-4.4.3/debian/changelog isc-dhcp-4.4.3/debian/changelog
--- isc-dhcp-4.4.3/debian/changelog	2022-05-26 21:31:55.0 +0200
+++ isc-dhcp-4.4.3/debian/changelog	2022-10-06 22:20:47.0 +0200
@@ -1,3 +1,12 @@
+isc-dhcp (4.4.3-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * An option refcount overflow exists in dhcpd (CVE-2022-2928)
+(Closes: #1021320)
+  * DHCP memory leak (CVE-2022-2929) (Closes: #1021320)
+
+ -- Salvatore Bonaccorso   Thu, 06 Oct 2022 22:20:47 +0200
+
 isc-dhcp (4.4.3-2) unstable; urgency=medium
 
   * Explicitly link against -latomic to fix FTBFS on mipsel, m68k, powerpc and
diff -Nru isc-dhcp-4.4.3/debian/patches/CVE-2022-2928.patch isc-dhcp-4.4.3/debian/patches/CVE-2022-2928.patch
--- isc-dhcp-4.4.3/debian/patches/CVE-2022-2928.patch	1970-01-01 01:00:00.0 +0100
+++ isc-dhcp-4.4.3/debian/patches/CVE-2022-2928.patch	2022-10-06 22:20:47.0 +0200
@@ -0,0 +1,111 @@
+Description: An option refcount overflow exists in dhcpd
+Origin: upstream
+Bug-Debian: https://bugs.debian.org/1021320
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2022-2928
+Forwarded: not-needed
+Last-Update: 2022-10-04
+
+diff --git a/common/options.c b/common/options.c
+index 92c8fee6..f0959cb2 100644
+--- a/common/options.c
 b/common/options.c
+@@ -4452,6 +4452,8 @@ add_option(struct option_state *options,
+ 	if (!option_cache_allocate(, MDL)) {
+ 		log_error("No memory for option cache adding %s (option %d).",
+ 			  option->name, option_num);
++		/* Get rid of reference created during hash lookup. */
++		option_dereference(, MDL);
+ 		return 0;
+ 	}
+ 
+@@ -4463,6 +4465,8 @@ add_option(struct option_state *options,
+ 			 MDL)) {
+ 		log_error("No memory for constant data adding %s (option %d).",
+ 			  option->name, option_num);
++		/* Get rid of reference created during hash lookup. */
++		option_dereference(, MDL);
+ 		option_cache_dereference(, MDL);
+ 		return 0;
+ 	}
+@@ -4471,6 +4475,9 @@ add_option(struct option_state *options,
+ 	save_option(_universe, options, oc);
+ 	option_cache_dereference(, MDL);
+ 
++	/* Get rid of reference created during hash lookup. */
++	option_dereference(, MDL);
++
+ 	return 1;
+ }
+ 
+diff --git a/common/tests/option_unittest.c b/common/tests/option_unittest.c
+index 600ebe60..963b5663 100644
+--- a/common/tests/option_unittest.c
 b/common/tests/option_unittest.c
+@@ -213,6 +213,59 @@ ATF_TC_BODY(parse_X, tc)
+ }
+ }
+ 
++ATF_TC(add_option_ref_cnt);
++
++ATF_TC_HEAD(add_option_ref_cnt, tc)
++{
++atf_tc_set_md_var(tc, "descr",
++"Verify add_option() does not leak option ref counts.");
++}
++
++ATF_TC_BODY(add_option_ref_cnt, tc)
++{
++struct option_state *options = NULL;
++struct option *option = NULL;
++unsigned int cid_code = DHO_DHCP_CLIENT_IDENTIFIER;
++char *cid_str = "1234";
++int refcnt_before = 0;
++
++// Look up the option we're going to add.
++initialize_common_option_spaces();
++if (!option_code_hash_lookup(, dhcp_universe.code_hash,
++ _code, 0, MDL)) {
++atf_tc_fail("cannot find option definition?");
++}
++
++// Get the option's reference count before we call add_options.
++refcnt_before = option->refcnt;
++
++// Allocate a option_state to which to add an option.
++if (!option_state_allocate(, MDL)) {
++	atf_tc_fail("cannot allocat options state");
++}
++
++// Call add_option() to add the option to the option state.
++if (!add_option(options, cid_code, cid_str, strlen(cid_str))) {
++	atf_tc_fail("add_option returned 0");
++}
++
++// Verify that calling add_option() only adds 1 to the option ref count.
++if (option->refcnt != (refcnt_before + 1)) {
++atf_tc_fail("after add_option(), count is wrong, before %d, after: %d",
++refcnt_before, option->refcnt);
++}
++
++// Derefrence the option_state, this should reduce the ref count to
++// it's starting value.
++option_state_dereference(, MDL);
++
++// Verify that dereferencing option_state restores option ref count.
++if (option->refcnt != refcnt_before) {
++atf_tc_fail("after state deref, count is 

Bug#1016279: libzypp: diff for NMU version 17.25.7-2.2

[Adrian Bunk]

Control: tags 1016279 + patch
Control: tags 1016279 + pending

Dear maintainer,

I've prepared an NMU for libzypp (versioned as 17.25.7-2.2) and uploaded 
it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru libzypp-17.25.7/debian/changelog libzypp-17.25.7/debian/changelog
--- libzypp-17.25.7/debian/changelog	2021-12-09 19:34:44.0 +0200
+++ libzypp-17.25.7/debian/changelog	2022-10-06 23:17:51.0 +0300
@@ -1,3 +1,10 @@
+libzypp (17.25.7-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for FTBFS with gcc 12. (Closes: #1016279)
+
+ -- Adrian Bunk   Thu, 06 Oct 2022 23:17:51 +0300
+
 libzypp (17.25.7-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libzypp-17.25.7/debian/patches/0001-Fix-building-with-GCC-12.x-release.patch libzypp-17.25.7/debian/patches/0001-Fix-building-with-GCC-12.x-release.patch
--- libzypp-17.25.7/debian/patches/0001-Fix-building-with-GCC-12.x-release.patch	1970-01-01 02:00:00.0 +0200
+++ libzypp-17.25.7/debian/patches/0001-Fix-building-with-GCC-12.x-release.patch	2022-10-06 23:16:58.0 +0300
@@ -0,0 +1,26 @@
+From 874744548898ec1f3d7f4481cca5b546d416cf6c Mon Sep 17 00:00:00 2001
+From: Martin Liska 
+Date: Wed, 29 Jun 2022 11:05:01 +0200
+Subject: Fix building with GCC 12.x release.
+
+Add missing header file.
+
+Fixes: #396
+---
+ zypp/base/Random.cc | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/zypp/base/Random.cc b/zypp/base/Random.cc
+index c5dba8083..9f40a3871 100644
+--- a/zypp/base/Random.cc
 b/zypp/base/Random.cc
+@@ -1,5 +1,6 @@
+ #include 
+ #include 
++#include 
+ #include 
+ 
+ 
+-- 
+2.30.2
+
diff -Nru libzypp-17.25.7/debian/patches/series libzypp-17.25.7/debian/patches/series
--- libzypp-17.25.7/debian/patches/series	2021-12-09 19:33:06.0 +0200
+++ libzypp-17.25.7/debian/patches/series	2022-10-06 23:17:48.0 +0300
@@ -2,3 +2,4 @@
 1003_various-typo-fixes.patch
 1004_fix-fastcgi-includes.patch
 0001-Add-missing-includes-for-GCC-11-bsc-1181874.patch
+0001-Fix-building-with-GCC-12.x-release.patch

Bug#828752: mod-dnssd: please make the build reproducible

[Vagrant Cascadian]

Control: tags 828752 pending

On 2022-10-06, Vagrant Cascadian wrote:
> I intend to NMU with these patches applied, though will likely use
> DELAYED/10 to give time for the maintainer to respond.

Uploaded an NMU to DELAYED/10:

diff -Nru mod-dnssd-0.6/debian/changelog mod-dnssd-0.6/debian/changelog
--- mod-dnssd-0.6/debian/changelog  2017-11-26 09:49:30.0 -0800
+++ mod-dnssd-0.6/debian/changelog  2022-10-06 11:11:40.0 -0700
@@ -1,3 +1,13 @@
+mod-dnssd (0.6-3.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  * debian/rules: Pass --disable-lynx in dh_auto_configure override.
+(Closes: #828752)
+  * debian/control: Remove lynx from Build-Depends.
+
+ -- Vagrant Cascadian   Thu, 06 Oct 2022 
11:11:40 -0700
+
 mod-dnssd (0.6-3.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru mod-dnssd-0.6/debian/control mod-dnssd-0.6/debian/control
--- mod-dnssd-0.6/debian/control2017-11-26 09:49:30.0 -0800
+++ mod-dnssd-0.6/debian/control2022-10-06 11:11:40.0 -0700
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Regis Boudin 
 Uploaders: Sebastien ESTIENNE 
-Build-Depends: debhelper (>= 10), apache2-dev, dh-apache2,libavahi-client-dev 
(>= 0.6.4), lynx, libapr1-dev
+Build-Depends: debhelper (>= 10), apache2-dev, dh-apache2,libavahi-client-dev 
(>= 0.6.4), libapr1-dev
 Standards-Version: 4.1.1
 Homepage: http://0pointer.de/lennart/projects/mod_dnssd/
 
diff -Nru mod-dnssd-0.6/debian/rules mod-dnssd-0.6/debian/rules
--- mod-dnssd-0.6/debian/rules  2017-11-26 09:49:30.0 -0800
+++ mod-dnssd-0.6/debian/rules  2022-10-06 11:11:40.0 -0700
@@ -6,3 +6,6 @@
dh $@ --with apache2
 
 override_dh_auto_install:
+
+override_dh_auto_configure:
+   dh_auto_configure -- --disable-lynx


signature.asc
Description: PGP signature

Bug#829715: NMU for reproducible builds and cross building issues

[Vagrant Cascadian]

Control: tags 913734 pending
Control: tags 829715 pending

Uploaded an NMU to DELAYED/10 fixing the cross building and reproducible
builds patches submitted in 2018 and 2016:

diff -Nru snake4-1.0.14/debian/changelog snake4-1.0.14/debian/changelog
--- snake4-1.0.14/debian/changelog  2014-08-18 06:07:37.0 -0700
+++ snake4-1.0.14/debian/changelog  2022-10-06 13:24:22.0 -0700
@@ -1,3 +1,16 @@
+snake4 (1.0.14-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Reiner Herrmann ]
+  * Strip build date/user to enable reproducible building.
+(Closes: #829715)
+
+  [ Helmut Grohne ]
+  * Fix FTCBFS: Don't strip during make install. (Closes: #913734)
+
+ -- Vagrant Cascadian   Thu, 06 Oct 2022 
13:24:22 -0700
+
 snake4 (1.0.14-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru 
snake4-1.0.14/debian/patches/makefile-use-install-variable-rather-tha.patch 
snake4-1.0.14/debian/patches/makefile-use-install-variable-rather-tha.patch
--- snake4-1.0.14/debian/patches/makefile-use-install-variable-rather-tha.patch 
1969-12-31 16:00:00.0 -0800
+++ snake4-1.0.14/debian/patches/makefile-use-install-variable-rather-tha.patch 
2022-10-06 13:24:22.0 -0700
@@ -0,0 +1,40 @@
+From: Helmut Grohne 
+Date: Wed, 14 Nov 2018 14:00:58 +0100
+X-Dgit-Generated: 1.0.14-1.1 cc12e06821c48f4a94bfa55ea275a6de3b2979b9
+Subject: Makefile: Use INSTALL variable rather than hard-coded install.
+
+Patch from https://bugs.debian.org/913734
+
+Patch description by Vagrant Cascadian 
+
+---
+
+diff --git a/Makefile b/Makefile
+index bf234f9..6ac7b99 100644
+--- a/Makefile
 b/Makefile
+@@ -63,6 +63,7 @@ DEFINES  = -DVERSION=\"$(VERSION)\" \
+ ###
+ 
+ CC= gcc
++INSTALL   ?= install
+ 
+ OPTIM = -s -O2
+ CCOPT = -Wall $(OPTIM) $(INCDIR) $(DEFINES) $(CFLAGS)
+@@ -90,12 +91,12 @@ clean:
+   rm -f *.o core depend *~ $(PROG)
+ 
+ install: $(PROG)
+-  install -d -m 755 $(INSTBINDIR) $(INSTLIBDIR) $(INSTMANDIR)
+-  install -s -m 4755 -o $(OWNER) -g $(GROUP) $(PROG) $(INSTBINDIR)
++  $(INSTALL) -d -m 755 $(INSTBINDIR) $(INSTLIBDIR) $(INSTMANDIR)
++  $(INSTALL) -s -m 4755 -o $(OWNER) -g $(GROUP) $(PROG) $(INSTBINDIR)
+   ln -sf $(PROG) $(INSTBINDIR)/snake4scores
+-  install -m 644 $(DIST).6 $(INSTMANDIR)
++  $(INSTALL) -m 644 $(DIST).6 $(INSTMANDIR)
+   if test ! -f $(SCOREFILE); then \
+-install -m 644 -o $(OWNER) -g $(GROUP) \
++$(INSTALL) -m 644 -o $(OWNER) -g $(GROUP) \
+ $(SCOREBASEFILE) $(INSTLIBDIR); fi
+ 
+ depend dep:
diff -Nru snake4-1.0.14/debian/patches/series 
snake4-1.0.14/debian/patches/series
--- snake4-1.0.14/debian/patches/series 2014-08-18 04:43:09.0 -0700
+++ snake4-1.0.14/debian/patches/series 2022-10-06 13:24:22.0 -0700
@@ -1,3 +1,5 @@
 useless-linkage.patch
 hardening.patch
 standard-install-directories.patch
+strip-build-dateuser-to-enable-reproduci.patch
+makefile-use-install-variable-rather-tha.patch
diff -Nru 
snake4-1.0.14/debian/patches/strip-build-dateuser-to-enable-reproduci.patch 
snake4-1.0.14/debian/patches/strip-build-dateuser-to-enable-reproduci.patch
--- snake4-1.0.14/debian/patches/strip-build-dateuser-to-enable-reproduci.patch 
1969-12-31 16:00:00.0 -0800
+++ snake4-1.0.14/debian/patches/strip-build-dateuser-to-enable-reproduci.patch 
2022-10-06 13:24:22.0 -0700
@@ -0,0 +1,35 @@
+From: Reiner Herrmann 
+Date: Tue, 5 Jul 2016 16:43:38 +0200
+X-Dgit-Generated: 1.0.14-1.1 a00bd8404731fe2738413108aee6fcb249a5727e
+Subject: Strip build date/user to enable reproducible building (Closes: 
#829715).
+
+
+---
+
+diff --git a/Makefile b/Makefile
+index bfe5a78..bf234f9 100644
+--- a/Makefile
 b/Makefile
+@@ -57,8 +57,6 @@ GROUP= games
+ SCOREBASEFILE = $(PROG).score
+ SCOREFILE = $(INSTLIBDIR)/$(SCOREBASEFILE)
+ DEFINES   = -DVERSION=\"$(VERSION)\" \
+-"-DCOMPILED_DATE=\"$(COMPILED_DATE)\"" \
+-"-DCOMPILED_BY=\"$(COMPILED_BY)\"" \
+ -DSCOREFILE=\"$(SCOREFILE)\" \
+ -DXK_MISCELLANY -DXK_LATIN1 
+ 
+diff --git a/snake4.c b/snake4.c
+index 13c5b25..1180adc 100644
+--- a/snake4.c
 b/snake4.c
+@@ -31,8 +31,7 @@ static void
+ version(void)
+ {
+ printf(
+-  "snake4 " VERSION ", by Sverre H. Huseby "
+-  "(compiled " COMPILED_DATE " by " COMPILED_BY ")\n"
++  "snake4 " VERSION ", by Sverre H. Huseby\n"
+ );
+ exit(0);
+ }
diff -Nru snake4-1.0.14/debian/rules snake4-1.0.14/debian/rules
--- snake4-1.0.14/debian/rules  2014-08-14 16:45:50.0 -0700
+++ snake4-1.0.14/debian/rules  2022-10-06 13:24:22.0 -0700
@@ -5,6 +5,9 @@
 %:
dh $@ --parallel
 
+override_dh_auto_install: # drop with debhelper compat 10
+   dh_auto_install -- 'INSTALL=install --strip-program=true'
+
 override_dh_fixperms:

Bug#1021369: ITP: lomiri-notifications -- Lomiri Notifications - QML module

[Mike Gabriel]

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

* Package name: lomiri-notifications
  Version : 1.3.0
  Upstream Author : UBports Foundation 
* URL : 
https://gitlab.com/ubports/development/core/lomiri-notifications/
* License : GPL-3
  Programming Lang: C++ / QML
  Description : Lomiri Notifications - QML module

 Lomiri's implementation of a Free Desktop Notification server. It also
 provides some additional features as needed on alternative platforms,
 such as mobile.
 .
 Since the shell is implemented in QML, this functionality is implemented
 as a QML plugin. Notification status is provided as a
 QAbstractListModel, making integration simple. The exact form of the API
 is defined by the shell, Lomiri notifications only implements it.
 .
 Lomiri notifications does not and will not provide a C/C++ API for
 sending or receiving notifications. It is QML only.
 .
 This package will be maintained by the Debian's UBports Packaging Team.

Bug#1021368: autopkgtest: quilt patches not applied on arm64, ppc64el, or s390x

[Paul Gevers]

Hi Olek,

On 06-10-2022 22:05, Paul Gevers wrote:

On 06-10-2022 21:38, Olek Wojnar wrote:
It's entirely possible that this is also a problem in may package, 
which is
why I have the test suite there in the first place. However, I have 
not been

able to discover a reason why the tests run correctly on amd64 but fail,
exactly as they did before I wrote the patch, on the other architectures.

Thanks and happy to provide any additional information if it will help!


I notice this in the log, is that the patch you're talking about?

dpkg-source: warning: unexpected end of diff 
'src/debian/patches/remove_javac.patch'


I have just started the test on one of our workers manually and I can 
confirm that the patches are all applied.


With the following:

root@ci-worker-arm64-09:~# /usr/bin/autopkgtest --no-built-binaries 
--shell-fail --user debci --apt-upgrade --add-apt-release=unstable 
--pin-packages=unstable=src:bazel-bootstrap bazel-bootstrap -- lxc 
--sudo --name elbrus autopkgtest-testing-arm64


I get to test java-1 and after installing quilt I get this:
root@elbrus:/tmp/autopkgtest-lxc.7zdkbsmk/downtmp/build.loA/src# quilt push
File series fully applied, ends at patch debian/patches/remove_skylib.patch

and $(quilt pop -a) confirms I can removal all patches normally.

Is there anything else you want me to run in the testbed of the broken 
test (please be verbose)?


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008263: plans to upload memtest86+ 6 to unstable?

[Fabio Fantoni]

Il 06/10/2022 17:44, Antoine Beaupré ha scritto:

Hello Fabio!

Below is an excerpt of a discussion that happened in bug #1008263 about
removing pcmemtest from Debian, to remove the duplication of work with
memtest86+:

On 2022-09-09 17:08:34, Felix Zielcke wrote:

I wasn't sure if I should wait until the new memtest86+ gets out of
beta and uploaded to unstable. But yeah, maybe it's better to just file
the RM now

I am wondering if you had any plans to upload memtest86+ 6 to unstable
already? It looks like it could fix a *lot* of issues that currently
affect memtest86, which is basically unusable on modern platforms right
now.

For example, on my Framework laptop -- which only boots from EFI --
memtest86 from testing/unstable just doesn't boot at all. I am just
testing the version from experimental and, so far so good, it seems to
work fine!

Thanks for any update!

Hi, I was waiting the release of the definitive (stable) version before 
upload to unstable, unfortunately the release scheduled for a month ago 
was delayed, however x86fr said there is a last patch missing that he 
needs to add shortly and then 6.00 will be released




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021368: autopkgtest: quilt patches not applied on arm64, ppc64el, or s390x

[Paul Gevers]

Hi Olek,

On 06-10-2022 21:38, Olek Wojnar wrote:

It's entirely possible that this is also a problem in may package, which is
why I have the test suite there in the first place. However, I have not been
able to discover a reason why the tests run correctly on amd64 but fail,
exactly as they did before I wrote the patch, on the other architectures.

Thanks and happy to provide any additional information if it will help!


I notice this in the log, is that the patch you're talking about?

dpkg-source: warning: unexpected end of diff 
'src/debian/patches/remove_javac.patch'


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#920158: stterm: Crash when displaying emoji

[Don]

On Wed, 30 Jan 2019 22:03:58 +0100 Paride Legovini  wrote:
> control: forwarded 920158
> https://gitlab.freedesktop.org/xorg/lib/libxft/issues/6
>
> Timothy Allen wrote on 30/01/2019:
> > On Tue, 2019-01-29 at 23:56 +0100, Paride Legovini wrote:
> >> I will report it there, unless you want to report it
> >> yourself (see https://suckless.org/community/).
>
> Turns out the issue is known and it's actually an Xft bug:
>
> https://lists.suckless.org/dev/1901/33147.html
>
> https://gitlab.freedesktop.org/xorg/lib/libxft/issues/6
>
> Paride

Hello,

It seems libxft devs have fixed the bug in 2.3.5 [1][2].
It would be nice to see that version available in testing soon.

[1]: https://gitlab.freedesktop.org/xorg/lib/libxft/-/blob/libXft-2.3.5/NEWS
[2]: https://lists.suckless.org/dev/2209/34965.html

Don

Bug#828683: mc: please make the build reproducible

[Vagrant Cascadian]

On 2016-06-27, Yury V. Zaytsev wrote:
> On Mon, 27 Jun 2016, Reiner Herrmann wrote:

Going through some old outstanding reproducible builds related bugs...

>> You are right, the mtime of the file is used for the manpage timestamp. 
>> But there is still a patch modifying the manpage: 
>> mcedit_full_path.patch. When this patch is upstreamed, the 
>> SOURCE_DATE_EPOCH patch is not needed, though it would still help when 
>> the manpages are patched.
>
> Thank you for the confirmation that my guesses are correct!
>
> However, I'm hesitant to apply SOURCE_DATE_EPOCH to anything that looks 
> like a nail. I believe that patching of upstream sources by Debian is such 
> an oft occurring situation, that I would rather look for at solution at 
> the packaging level. After all, builds from *upstream* sources are 
> *already* reproducible, in this case, it's the Debian build procedure that 
> is injecting randomness here.

I am biased, but I do think using SOURCE_DATE_EPOCH could still be a
reasonable approach upstream. There are some examples of how to use this
in various languages:

  https://reproducible-builds.org/docs/source-date-epoch/

I did notice some things in the upstream code
doc/man/date-of-man-include.am:

MAN_DATE_CMD = \
LC_ALL=$(DATE_LANG) @PERL@ -CS -MPOSIX -e '\
@fi=lstat("'$${MAN_FILE}'"); \
print POSIX::strftime("$(DATE_FORMAT)", localtime($$fi[9]));' 
2>/dev/null

This uses localtime, which could be affected by timezone differences. To
my surprise, it doesn't appear to affect the results, as only the
patched manpage is affected:

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

Setting LC_ALL explicitly avoids variations due to the build
environment's locale(yay!), although the specified locales are not
guaranteed to be available (adding locales-all to build-depends could
fix that).

Again, surprisingly, this has not appeared to affect the results for the
locales tested on tests.reproducible-builds.org, though that may mean
the default locale is used even for the translated pages...


> For instance, it seems to me that it is only logical to set the mtime of 
> patched files to the mtime of the last patch that touched them, and this 
> will make the source mtime dependent builds fully reproducible.

The attached alternate implements this for mc by touching the potential
files before running configure with a consistent timestamp.

According to my local tests, applying this patch should make mc build
reproducibly once it lands in testing/bookworm! There are outstanding
build path issues tested in unstable and experimental.

It doesn't address the larger issue of files modified by debian/patches
having the current timestamp, which is a much more complicated
intersection of issues.


live well,
  vagrant
From 4e69587954d29ec6bfc7d85b4b618724b16b840e Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Thu, 6 Oct 2022 19:25:11 +
Subject: [PATCH 5/5] debian/rules: Ensure consistent timestamp on manpages.

The upstream build system uses the file modification time of the .in
file for the manpage to embed into the generatated manpage, but if
debian/patches modify the .in files, the timestamp is updated,
resulting in builds performed in different months or years embedding a
different date.
---
 debian/rules | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/debian/rules b/debian/rules
index c633a73..bf8eb5e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -25,6 +25,8 @@ override_dh_autoreconf:
 # AWK="awk" is inheritance of 4.7.* series, see http://bugs.debian.org/499723
 # might be still necessary for extfs scripts
 override_dh_auto_configure:
+	# Ensure reproducible timestamp on manpages
+	touch -d@$(SOURCE_DATE_EPOCH) doc/man/*.1.in doc/man/*/*.1.in
 	dh_auto_configure -- AWK="awk" X11_WWW="x-www-browser" \
 		--libexecdir='/usr/lib' \
 		--with-x \
-- 
2.37.2



signature.asc
Description: PGP signature

Bug#1020120: taking ownership of BTS 1020120

[Louis-Philippe Véronneau]

Even better, I think that the upstream .flake8 file isn't copied by 
pybuild when running tests? A d/pybuild.testfiles file should do the 
trick and I'll try that when that pam build fix has propagated.


The same should be done for the autopkgtests.

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_0xE1E5457C8BAD4113.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1020120: taking ownership of BTS 1020120

[Louis-Philippe Véronneau]

I started looking at this bug, but bug #1021336 currently breaks my 
sbuild, so I might as well take ownership of it.


flake8 tests clearly aren't important to us, so the "easy" way out is 
disabling those.


I'll try upgrading the package to the latest upstream version before 
doing this though, as 2.1.0 has official python 3.10 support.


Cheers,

--
   ⢀⣴⠾⠻⢶⣦⠀
   ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
   ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
   ⠈⠳⣄


OpenPGP_0xE1E5457C8BAD4113.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016939: Adrian Bunk

[Dennis Braun]

Hi Adrian,

sorry for the late reply. You can cancel it, because i prepared a new 
version with that fix already.

Will upload it asap.

Best regards,
Dennis

Bug#1021368: autopkgtest: quilt patches not applied on arm64, ppc64el, or s390x

[Olek Wojnar]

Package: autopkgtest
Version: 5.25
Severity: normal

Dear Maintainer,

I noticed some autopkgtest failures [1][2][3] in a recent package upload. I
also noticed that the amd64 build [4] was consistently successful. In
addition, the autopkgtest that I run automatically during my build process
(also on amd64) has been consistently successful. After some investigation,
it seems that a patch fixing a build failure [5] is only being applied on
amd64. I'm not sure if this is in any way related to 844454 [6] and I
did not see any recent commits on Salsa that seem related.

It's entirely possible that this is also a problem in may package, which is
why I have the test suite there in the first place. However, I have not been
able to discover a reason why the tests run correctly on amd64 but fail,
exactly as they did before I wrote the patch, on the other architectures.

Thanks and happy to provide any additional information if it will help!

-Olek


[1] 
https://ci.debian.net/data/autopkgtest/testing/arm64/b/bazel-bootstrap/26782992/log.gz
[2] 
https://ci.debian.net/data/autopkgtest/testing/ppc64el/b/bazel-bootstrap/26736720/log.gz
[3] 
https://ci.debian.net/data/autopkgtest/testing/s390x/b/bazel-bootstrap/26736769/log.gz
[4] 
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bazel-bootstrap/26736486/log.gz
[5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983982
[6] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844454

Bug#1021367: pgcli: needs psycopg>=3.0.14

[Yannick Roehlly]

Package: pgcli
Version: 3.5.0-1
Severity: grave
Justification: renders package unusable

Hi,

Starting pgcli fails with

pkg_resources.DistributionNotFound: The 'psycopg>=3.0.14' distribution
was not found and is required by pgcli

The current package depends on python3-psycopg2. The python3-psycopg3 package
currently in Debian is for version 3.0.1.

Making and installing a package for python3-psycopg3 version 3.1.3 fixes the
issue.

Best,

Yannick


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

Kernel: Linux 5.19.12 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr:en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pgcli depends on:
ii  python3 3.10.6-1
ii  python3-cli-helpers 2.2.1-1
ii  python3-click   8.1.3-0.1
ii  python3-configobj   5.0.6-5
ii  python3-pendulum2.1.2-4
ii  python3-pgspecial   1.13.0-0.1
ii  python3-pkg-resources   65.3.0-1.1
ii  python3-prompt-toolkit  3.0.31-1
ii  python3-psycopg22.9.3-1
ii  python3-pygments2.12.0+dfsg-2
ii  python3-setproctitle1.3.1-1
ii  python3-sqlparse0.4.2-1
ii  python3-tabulate0.8.9-1
ii  python3-terminaltables  3.1.10-1

pgcli recommends no packages.

pgcli suggests no packages.

-- no debconf information

Bug#1017377: libstb: incomplete clean target

[David Paul]

On Tue, 27 Sep 2022 12:39:17 -0400
Boyuan Yang  wrote:

> On Mon, 15 Aug 2022 00:54:23 -0500 "David (Plasma) Paul"
>  wrote:
> > Source: libstb
> > Version: 0.0~git20210910.af1a5bc+ds-1
> > Severity: minor
> > X-Debbugs-CC: davidp...@librem.one
...
> > The 'clean' target for the libstb Makefile is incomplete and leaves
> > behind two files, stb_c_lexer.c and stb_divide.c, generated by the
> > '%.c' target.
> > 
> > I have prepared a patch to correct this. I will submit the patch
> > momentarily once I update the changelog entry with the bug number
> > created by this report.  
> 
> While we will fix this issue in Debian, I am just wondering, have you
> reported this issue (possibly together with the patch) to upstream
> project?

I haven't. Given that my patch is limited to editing a Makefile that is
not in the upstream source and is instead added by the Debian
packaging, I saw little reason to do so. Upstream is, of course,
welcome to incorporate the Makefile into the upstream source tree, but
AFAICT the upstream-recommended way of using libstb is to simply copy
individual header files into a program source tree as-needed.

-- 
Plasma

Bug#1021366: nvidia-tesla-470-driver: 'Failed to load module "nvidia"' when forcing to use nvidia instead of intel by default

[Vincas Dargis]

Package: nvidia-tesla-470-driver
Version: 470.141.03-2
Severity: normal

Dear Maintainer,

I am using
https://wiki.debian.org/NVIDIA%20Optimus#Using_NVIDIA_GPU_as_the_primary_GPU
setup to enable NVIDIA by default on my Asus N551JM with GM107M [GeForce
GTX 860M] for quite some time successfully.

I had modified /usr/share/sddm/scripts/Xsetup as specified too.

Thogh after I got NEWS warning that I should not upgrade nvidia driver,
but to install nvidia-tesla, that setup no longer works, due to X11
error:

```
[ 6.171] (II) Module glx: vendor="X.Org Foundation"
[ 6.171]compiled for 1.21.1.4, module version = 1.0.0
[ 6.171]ABI class: X.Org Server Extension, version 10.0
[ 6.171] (II) LoadModule: "nvidia"
[ 6.172] (WW) Warning, couldn't open module nvidia
[ 6.172] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 6.172] (II) LoadModule: "modesetting"
[ 6.172] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so

```

For time being I do not use custom xorg.conf, so it runs successfully Intel.

Also, I had to manually blacklist nouveau, as nvidia package did not
create any symlinks in /etc/modprobe.d/.


-- Package-specific info:
uname -a:
Linux vinco 5.19.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24) 
x86_64 GNU/Linux

/proc/version:
Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 
11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38.90.20220713) #1 SMP 
PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.141.03  Thu Jun 30 18:45:31 
UTC 2022
GCC version:  gcc version 11.3.0 (Debian 11.3.0-8) 

lspci 'display controller [030?]':
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core 
Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA 
controller])
Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:177d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 860M] 
[10de:1392] (rev a2)
Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 860M] [1043:177d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_tesla_470, nvidia_tesla_470_drm

dmesg:

Device node permissions:
crw-rw+ 1 root video  226,   0 Oct  6 22:05 /dev/dri/card0
crw-rw+ 1 root video  226,   1 Oct  6 22:05 /dev/dri/card1
crw-rw+ 1 root render 226, 128 Oct  6 22:05 /dev/dri/renderD128
crw-rw+ 1 root render 226, 129 Oct  6 22:05 /dev/dri/renderD129

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Oct  6 22:05 pci-:00:02.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Oct  6 22:05 pci-:00:02.0-render -> ../renderD128
lrwxrwxrwx 1 root root  8 Oct  6 22:05 pci-:01:00.0-card -> ../card1
lrwxrwxrwx 1 root root 13 Oct  6 22:05 pci-:01:00.0-render -> ../renderD129
video:x:44:vincas

Alternative 'nvidia':
nvidia - auto mode
  link best version is /usr/lib/nvidia/tesla
  link currently points to /usr/lib/nvidia/tesla
  link nvidia is /usr/lib/nvidia/nvidia
  slave nvidia--libEGL_nvidia.so.0-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libEGL_nvidia.so.0
  slave nvidia--libEGL_nvidia.so.0-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libEGL_nvidia.so.0
  slave nvidia--libGLESv1_CM_nvidia.so.1-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libGLESv1_CM_nvidia.so.1
  slave nvidia--libGLESv1_CM_nvidia.so.1-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libGLESv1_CM_nvidia.so.1
  slave nvidia--libGLESv2_nvidia.so.2-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libGLESv2_nvidia.so.2
  slave nvidia--libGLESv2_nvidia.so.2-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libGLESv2_nvidia.so.2
  slave nvidia--libGLX_nvidia.so.0-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libGLX_nvidia.so.0
  slave nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
  slave nvidia--libcuda.so-i386-linux-gnu is /usr/lib/i386-linux-gnu/libcuda.so
  slave nvidia--libcuda.so-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libcuda.so
  slave nvidia--libcuda.so.1-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libcuda.so.1
  slave nvidia--libcuda.so.1-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libcuda.so.1
  slave nvidia--libglxserver_nvidia.so is /usr/lib/nvidia/libglxserver_nvidia.so
  slave nvidia--libnvcuvid.so-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libnvcuvid.so
  slave nvidia--libnvcuvid.so-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libnvcuvid.so
  

Bug#1021249: new upstream version required

[Tomasz Rybak]

Thanks for working on package.
At the same time I have few doubts related to your changes:

1. It looks like you took package as it is currently in archive
(i.e. 3.0.1) and brough it up to new version. Is this correct?
I haven't noticed neither new commits nor merge requests.

Package is maitained inside Python Team (the same as for psycopg2)
under https://salsa.debian.org/python-team/packages/psycopg3
and therefore should follow Team's Policy
https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
, including usage of git-buildpackageworkflow.
Repository contains yet-unreleased changes, including
update to 3.0.14 (yeah, currently quite old), updates
to debian/copyright (especially for new modules and files),
other fixes to metadata (05f60589535f3bc6ccb479c832500b24a4280b7c and
35559675c2d2225041faacf3f7c922a65858c91d), and ones proposed by
Janitor.

While I don't mind other DDs working on package and uploading
new versions and even welcome that (that's why it's team-maintained),
please do it taking already-existing changes into consideration,
and following Team's policy.

2. Have you fully built package, including binary documentation *.deb?
I had problems with that after upgrading to 3.0.14; building
documentation required network access - therefore my patches and
this is the main reason of delay with uploading 3.0.14.
If you succeeded, this might mean that older version had some
problems which were fixed in 3.1.2.

Best regards


On Wed, 2022-10-05 at 15:19 +0200, Daniel Baumann wrote:
> > Hi,
> > 
> > I've took the liberty to upload a NMU to delayed 5, diff is attached:
> > 
> >   * If you're ok with the diff, I would be happy to cancel it and upload
> > directly to unstable.
> >   * If you're not ok with the diff, I'm happy to cancel the upload and
> > let you do it.
> > 
> > Regards,
> > Daniel

-- 
Tomasz Rybak, Debian Developer 
GPG: A565 CE64 F866 A258 4DDC F9C7 ECB7 3E37 E887 AA8C

-- 
Tomasz Rybak, Debian Developer 
GPG: A565 CE64 F866 A258 4DDC F9C7 ECB7 3E37 E887 AA8C


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

Bug#1016939: padthv1: diff for NMU version 0.9.26-1.1

[Adrian Bunk]

Control: tags 1016939 + patch

Dear maintainer,

I've prepared an NMU for padthv1 (versioned as 0.9.26-1.1) and uploaded 
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru padthv1-0.9.26/debian/changelog padthv1-0.9.26/debian/changelog
--- padthv1-0.9.26/debian/changelog	2022-06-08 18:04:00.0 +0300
+++ padthv1-0.9.26/debian/changelog	2022-10-06 21:59:32.0 +0300
@@ -1,3 +1,10 @@
+padthv1 (0.9.26-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use a simpler and less fragile autopkgtest. (Closes: #1016939)
+
+ -- Adrian Bunk   Thu, 06 Oct 2022 21:59:32 +0300
+
 padthv1 (0.9.26-1) unstable; urgency=medium
 
   * New upstream version 0.9.26
diff -Nru padthv1-0.9.26/debian/tests/control padthv1-0.9.26/debian/tests/control
--- padthv1-0.9.26/debian/tests/control	2020-12-22 01:42:20.0 +0200
+++ padthv1-0.9.26/debian/tests/control	2022-10-06 21:59:32.0 +0300
@@ -1,3 +1,3 @@
 Tests: simpletest
-Depends: @, psmisc
-Restrictions: superficial, allow-stderr
+Depends: @
+Restrictions: superficial
diff -Nru padthv1-0.9.26/debian/tests/simpletest padthv1-0.9.26/debian/tests/simpletest
--- padthv1-0.9.26/debian/tests/simpletest	2020-12-22 01:42:20.0 +0200
+++ padthv1-0.9.26/debian/tests/simpletest	2022-10-06 21:59:30.0 +0300
@@ -4,8 +4,4 @@
 
 set -e
 
-padthv1_jack -g &
-echo 'Simple test success!'
-
-echo 'We kill padthv1_jack because it doesn’t close itself in the testbed'
-killall padthv1_jack
+padthv1_jack -g --version

Bug#1020840: arcanist fails with 'Toolset "arcanist" is unknown'

[Christoph Biedl]

Control: severity 1020840 important
Control: tags 1020840 pending

Taavi Väänänen wrote...

> Hello. A recent update to the Arcanist packaging moved the binary from
> /usr/bin/arc to /usr/bin/arcanist. The binary name change makes the CLI
> fail to function properly:

#919697 has the full story: There was a file conflict on /usr/bin/arc, use
the arc executable from /usr/share/arcanist/bin/ as told in postinst.

Fix to enhance the program to understand usr/bin/arcanist as well is underway.

Christoph


signature.asc
Description: PGP signature

Bug#1021365: wishlist: support same syntax for ipv6 addresse4s as other tools (RFC2291)

[Marc Lehmann]

Package: nftables
Version: 0.9.8-3.1
Severity: wishlist

Dear Maintainer,

virtually all tools accepting ipv6 addresses use the format defined in RFC
4291 (IP Version 6 Addressing Architecture) section 2.2 (specifically form
3 is what I am talking about).

In fact, the only exception known to me is nftables, which defines its
own format ("Addresses are specified as a host name or as hexadecimal
halfwords separated by colons.").

This makes interoperability between other network tools and nftables
a hassle, as converting from standard IPv6 addressses toi the format
required by nft is quite hard to do e.g. in shell scripts.

I think it would be a very useful improvement if nft used the same IPv6
address format as other tools (in addition to hostnames, of course).

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

Kernel: Linux 6.0.0-schmorp (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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 nftables depends on:
ii  dpkg  1.20.12
ii  libc6 2.31-13+deb11u4
ii  libedit2  3.1-20191231-2+b1
ii  libnftables1  0.9.8-3.1

nftables recommends no packages.

Versions of packages nftables suggests:
pn  firewalld  

-- no debconf information

Bug#1021336: Acknowledgement (libpam-modules-bin: trying to overwrite '/usr/share/man/man5/namespace.conf.5.gz')

[Steve Langasek]

Control: reopen 1021336

On Thu, Oct 06, 2022 at 07:49:24AM +0200, Christian Marillat wrote:
> On 06 oct. 2022 05:42, "Debian Bug Tracking System"  
> wrote:

> I see more errors :

> trying to overwrite '/usr/share/man/man8/pam_namespace_helper.8.gz', which
> is also in package libpam-modules:powerpc 1.5.2-2

Hngh.  Will fix.

> trying to overwrite '/usr/share/man/man5/namespace.conf.5.gz', which is also 
> in package libpam-modules-bin 1.5.2-3

But that looks like you forced the install of -3?

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1021337: linux-image-5.19.0-2-amd64: Please enable building of the idxd module for the IntelData Accelerator support

[Gunnar Wolf]

Vincent Blut dijo [Thu, Oct 06, 2022 at 12:48:58PM +0200]:
> > > Specifically, the required configuration options to enable all of its
> > > features are:
> > >CONFIG_INTEL_IDXD=m
> > >CONFIG_INTEL_IDXD_SVM=y
> > 
> > Is this only applicable for the amd64 architecture or is it useful for 
> > others 
> > as well?
> 
> Since these depend on X86_64, only amd64 is concerned.

Right. And as I mentioned in the bug report,

The driver enables the Data Streaming Accelerator or DSA
capability for the 4th generation of the Intel Scalable Xeon
processor family, with code name Sapphire Rapids, and for future
Intel processors.

So, yes, it is relevant only for relatively recent x86_64 chips
produced by Intel (> 2019). For further details,

https://01.org/blogs/2019/introducing-intel-data-streaming-accelerator


signature.asc
Description: PGP signature

Bug#1021364: RFS: ghostwriter/2.2.0-1 [RC] -- Distraction-free, themeable Markdown editor

[Sebastien Chavaux]

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name : ghostwriter
   Version  : 2.2.0-1
   Upstream contact : wereturtle 
 * URL  : https://wereturtle.github.io/ghostwriter/
 * License  : Expat, GPL-3.0+, CC-BY-SA-4.0, GPL-3.0, ISC
 * Vcs  : https://salsa.debian.org/seb95-guest/ghostwriter
   Section  : editors

The source builds the following binary packages:

  ghostwriter - Distraction-free, themeable Markdown editor

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/g/ghostwriter/ghostwriter_2.2.0-1.dsc

Changes since the last upload:

 ghostwriter (2.2.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * debian/control: set Standards-Version: to 4.6.1
   * debian/control: address correction
   * debian/watch: address correction
   * CVE-2022-24724 (Closes: #1006757)

Regards,

Bug#1014815: kiwipy initial packaging

[Eriberto Mota]

Am 05.10.22 um 14:59 schrieb Guilherme Xavier:
>> Hi,
>> 
>> Agree, downgrading would be an option.
>> I don't know how this can be done, but I'm open to doing it.
>
> You import the older version as 8.1.1+really6.8.1-1


Nope. Downgrading is a workaround for new upstream versions full broken,
but already sent to Debian. Is dangerous and undesirable to reintroduce
an old version of a software to make it "a good dependency". This action
may generate critical bugs or introduce security holes. The right way is
ask to the upstream to update the software to use the current version of
a dependency. In other words, "+really" must be used in very extreme
cases only, not for adjustments.

Eriberto

Bug#1021363: codec2: ships test artifacts that disappear when built with nocheck

[Paul Gevers]

Source: codec2
Version: 1.0.5-1
Severity: normal
Tags: patch

Dear maintainer,

While scratching my (Release Team member's) itch in my merge request
number 2, I noticed that your package ships test artifacts in
codec2-examples that are absent when the build is run with the nocheck
option. Policy isn't totally clear on it, but the build profile spec
[2] assumes that the content shouldn't change and I tend to agree with
that part of the spec.

Please prevent test artifacts in codec2-examples. I'll update my MR
shortly to include *an* implementation to achieve that. I'm not
totally happy with the implementation, because it hardcodes somewhat
which files shouldn't be installed, but my other efforts didn't
work. I have to note that completely disabling the dh_auto_test line
achieves the same. You ignore failure of the test, so build wise it
wouldn't harm to remove it but I assume you look at it once in a
while, so didn't want to drop the test altogehter.

Paul

[1] https://salsa.debian.org/bottoms/pkg-codec2/-/merge_requests/2
[2] https://wiki.debian.org/BuildProfileSpec

Bug#777403: leave: please make the build reproducible

[Chris Lamb]

tags 777403 + pending patch
tags 967002 + pending patch
tags 999259 + pending patch
thanks

I've just uploaded leave 1.12-2.2 to DELAYED/10:
  
  leave (1.12-2.2) unstable; urgency=medium
  .
* Non-maintainer upload.
* Pass -n to gzip(1) to make the manual page and changelog reproducible, as
  well as pass CFLAGS to the C compiler to ensure that, for instance,
  -ffile-prefix-map is used. (Closes: #777403)
* Apply a patch by Helmut Grohne to correctly cross-build the leave binary.
  (Closes: #967002)
* Add the missing required debian/rules targets, build-arch and build-indep.
  (Closes: #999259)
* Remove a "debian/changelog~" editor backup file.

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for leave_1.12-2.1 leave_1.12-2.2

 debian/changelog~   |   88 
 leave-1.12/debian/changelog |   14 +++
 leave-1.12/debian/rules |   17 
 3 files changed, 23 insertions(+), 96 deletions(-)

diff -u leave-1.12/debian/changelog leave-1.12/debian/changelog
--- leave-1.12/debian/changelog
+++ leave-1.12/debian/changelog
@@ -1,3 +1,17 @@
+leave (1.12-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Pass -n to gzip(1) to make the manual page and changelog reproducible, as
+well as pass CFLAGS to the C compiler to ensure that, for instance,
+-ffile-prefix-map is used. (Closes: #777403)
+  * Apply a patch by Helmut Grohne to correctly cross-build the leave binary.
+(Closes: #967002)
+  * Add the missing required debian/rules targets, build-arch and build-indep.
+(Closes: #999259)
+  * Remove a "debian/changelog~" editor backup file.
+
+ -- Chris Lamb   Thu, 06 Oct 2022 10:59:51 -0700
+
 leave (1.12-2.1) unstable; urgency=low
 
   * Non-maintainer upload.
reverted:
--- leave-1.12/debian/changelog~
+++ leave-1.12.orig/debian/changelog~
@@ -1,88 +0,0 @@
-leave (1.12-2) unstable; urgency=low
-
-  * Exited with 0 instead of 1 for binary-indep, just for people who obsess
-with pointless details, closes: #395734.
-
- -- Josip Rodin   Sat, 28 Oct 2006 00:10:22 +0200
-
-leave (1.12-1) unstable; urgency=low
-
-  * New upstream version.
-  * Added an unportable glibc-only variable to get the program name,
-because the unportable NetBSD-only variable didn't work.
-
- -- Josip Rodin   Fri, 15 Aug 2003 21:10:23 +0200
-
-leave (1.10-1) unstable; urgency=low
-
-  * New upstream version, closes: #143720.
-Abolished our patches for handling 24-hour time formats, and used
-the upstream's. The behaviour is unchanged, AFAICT.
-  * Updated for Policy 3.5.6. debian/rules in shell,
-removed the use of both debhelper and pmake -> no Build-Depends :)
-
- -- Josip Rodin   Mon, 26 Aug 2002 14:40:30 +0200
-
-leave (1.8-2) unstable; urgency=low
-
-  * Fixed those long standing bugs in the handling of 24h-clock
-arguments, by making leave not convert times to 12h clock, but check
-whether the time is between 1 and 12, and then interpret it according
-to a 12-hour clock. Let's hope it all works.
-Thanks to Sergio Gelato , who provided
-the patch both for the code and for the manual page.
-(closes #25150 #26000 #31250 #31872)
-  * Updated for Policy 3.x. Removed the full text of the BSD license from
-the copyright file and referenced the /usr/share/common-licenses/BSD
-file.
-
- -- Josip Rodin   Mon, 18 Oct 1999 23:13:16 +0200
-
-leave (1.8-1) unstable; urgency=low
-
-  * New maintainer, new upstream source (with exactly two (2) new lines
-of code), new debian/* files.
-
- -- Josip Rodin   Wed, 19 May 1999 18:13:22 +0200
-
-leave (1.6-2) unstable; urgency=low
-
-  * debian/control (Maintainer): new address.
-  * debian/copyright: ditto.
-  * debian/control (Standards-Version): updated to 2.5.0.0.
-  * debian/rules: replace $(package) with a string literal and other minor
-clean ups.
-
- -- James Troup   Tue, 10 Nov 1998 15:46:23 +
-
-leave (1.6-1) unstable; urgency=low
-
-  * New upstream version.
-  * debian/rules: Use BSD make not GNU make to build.
-  * debian/rules: Build with -g.
-  * debian/rules: Call dpkg-gencontrol with -isp.
-  * debian/rules: remove leave.cat1 on clean.
-  * debian/rules: no more {,} usage.
-  * debian/rules: chmod go=rX not g-ws.
-  * debian/control: Standards-Version 2.3.0.1.
-  * debian/control: section is really utils not misc.
-  * debian/copyright: removed over-keen "famous" from description.
-
- -- James Troup   Mon,  8 Dec 1997 21:03:01 +
-
-leave (1.4-3) unstable; urgency=low
- 
-  * Rebuilt libc6. 
-
- -- James Troup   Wed, 25 Jan 1997 18:30:06 +
-
-leave (1.4-2) unstable; urgency=low
- 
-  * New Maintainer.
-  * Updated package to standards version 2.1.1.2.
-
- -- James Troup   Wed, 22 Jan 1997 00:30:17 +
-
-Local variables:
-mode: debian-changelog
-End:
diff -u leave-1.12/debian/rules 

Bug#828752: mod-dnssd: please make the build reproducible

[Vagrant Cascadian]

On 2016-06-27, Reiner Herrmann wrote:
> While working on the "reproducible builds" effort [1], we have noticed
> that mod-dnssd could not be built reproducibly.
> The README file generated with lyxn contains differently translated
> lynx-output depending on locale/language settings.
>
> The attached patch fixes this by using 'C' as the used language.

The locales issue does not appear to affect the locales currently used
on tests.reproducible-builds.org, but I was able to sometimes reproduce
the issue with reprotest depending on which locale reprotest used.

I've attached simpler patches which just avoid using lynx by passing
--disable-lynx to configure and removing lynx from build-depends, as
using lynx also embeds build paths in a way that makes the README
reference files that do not even exist:

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

  file:///build/1st/mod-dnssd-0.6/doc/README.html#license
  vs.
  file:///build/2/mod-dnssd-0.6/2nd/doc/README.html#license

The package does not even ship a README.html, as this is a byproduct of
using lynx on the generated .html file to dump a plain-text README.

By not using lynx, it simply ships the provided readme.

I intend to NMU with these patches applied, though will likely use
DELAYED/10 to give time for the maintainer to respond.

live well,
  vagrant
From 726c21a87f728defba54cc206c42838c73c1032c Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Thu, 6 Oct 2022 17:02:08 +
Subject: [PATCH 1/3] debian/rules: Pass --disable-lynx in dh_auto_configure
 override. (Closes: #828752)

Using lynx embeds the build path and sometimes locale-specific
differences in the generated README.
---
 debian/rules | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/debian/rules b/debian/rules
index 0d40890..f211bad 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,3 +6,6 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 	dh $@ --with apache2
 
 override_dh_auto_install:
+
+override_dh_auto_configure:
+	dh_auto_configure -- --disable-lynx
-- 
2.30.2

From af404126fb9080662fb2fc67a602334c0d431c9b Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Thu, 6 Oct 2022 17:04:13 +
Subject: [PATCH 2/3] debian/control: Remove lynx from Build-Depends.

---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index d31ca56..ce371f7 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: httpd
 Priority: optional
 Maintainer: Regis Boudin 
 Uploaders: Sebastien ESTIENNE 
-Build-Depends: debhelper (>= 10), apache2-dev, dh-apache2,libavahi-client-dev (>= 0.6.4), lynx, libapr1-dev
+Build-Depends: debhelper (>= 10), apache2-dev, dh-apache2,libavahi-client-dev (>= 0.6.4), libapr1-dev
 Standards-Version: 4.1.1
 Homepage: http://0pointer.de/lennart/projects/mod_dnssd/
 
-- 
2.30.2



signature.asc
Description: PGP signature

Bug#829754: bibclean: please make the build reproducible

[Chris Lamb]

tags 829754 + pending patch
tags 929036 + pending patch
thanks

I've just uploaded bibclean 2.11.4.1-4.1 to DELAYED/10:
  
  bibclean (2.11.4.1-4.1) unstable; urgency=medium
  .
* Non-maintainer upload.
* Export CFLAGS from dpkg-buildflags(1) and FORCE_SOURCE_DATE to make the
  build reproducible. Based on a patch by Vagrant Cascadian.
  (Closes: #829754)
* Apply a patch by Helmut Grohne to add support for using a C compiler
  suitable for cross-building. (Closes: #929036)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for bibclean-2.11.4.1 bibclean-2.11.4.1

 changelog |   11 +++
 rules |   15 ---
 2 files changed, 15 insertions(+), 11 deletions(-)

diff -Nru bibclean-2.11.4.1/debian/changelog bibclean-2.11.4.1/debian/changelog
--- bibclean-2.11.4.1/debian/changelog  2011-12-07 05:26:23.0 -0800
+++ bibclean-2.11.4.1/debian/changelog  2022-10-06 10:42:07.0 -0700
@@ -1,3 +1,14 @@
+bibclean (2.11.4.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Export CFLAGS from dpkg-buildflags(1) and FORCE_SOURCE_DATE to make the
+build reproducible. Based on a patch by Vagrant Cascadian.
+(Closes: #829754)
+  * Apply a patch by Helmut Grohne to add support for using a C compiler
+suitable for cross-building. (Closes: #929036)
+
+ -- Chris Lamb   Thu, 06 Oct 2022 10:42:07 -0700
+
 bibclean (2.11.4.1-4) unstable; urgency=low
 
   * build targets changed to recommendation from lintian
diff -Nru bibclean-2.11.4.1/debian/rules bibclean-2.11.4.1/debian/rules
--- bibclean-2.11.4.1/debian/rules  2011-12-07 05:17:38.0 -0800
+++ bibclean-2.11.4.1/debian/rules  2022-10-06 10:42:07.0 -0700
@@ -4,17 +4,11 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-# These are used for cross-compiling and for saving the configure script
-# from having to guess our platform (since we know it already)
-DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
-DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
+DPKG_EXPORT_BUILDFLAGS = 1
+include /usr/share/dpkg/default.mk
 
-CFLAGS = -Wall -g
-ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
-   CFLAGS += -O0
-else
-   CFLAGS += -O2
-endif
+export CC
+export FORCE_SOURCE_DATE=1
 
 # This target makes sure that timestamps of files are in the
 # right order after dpkg-deb has unpacked the package. It prevents
@@ -29,7 +23,6 @@
 config.status: autogen-check
CFLAGS="$(CFLAGS)" ./configure \
--with-pager=/usr/bin/pager --with-fhs-rcfiles \
-   --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
 --prefix=/usr --mandir=\$${prefix}/share/man
 
 build: build-arch build-indep

Bug#828876: ario: please make the build reproducible

[Vagrant Cascadian]

On 2016-06-28, Reiner Herrmann wrote:
> While working on the "reproducible builds" effort [1], we have noticed
> that ario could not be built reproducibly.
> It embeds the current year into the binary.
>
> The attached patch replaces it with a static value.

I can confirm this patch is still needed, but when I tried applying this
patch, it fails to build asking for automake-1.15 (which is no longer in
debian, but automake-1.16 is):

  Making all in src
  make[3]: Entering directory '/<>/src'
  cd .. && /bin/bash /<>/missing automake-1.15 --foreign 
src/Makefile
  /<>/missing: line 81: automake-1.15: command not found
  WARNING: 'automake-1.15' is missing on your system.
  You should only need it if you modified 'Makefile.am' or
  'configure.ac' or m4 files included by 'configure.ac'.

Struggling to figure out how to get cdbs to actually regenerate the
files with a newer automake...

live well,
  vagrant


> [1]: https://wiki.debian.org/ReproducibleBuilds
> diff --git a/debian/patches/reproducible-build.patch 
> b/debian/patches/reproducible-build.patch
> new file mode 100644
> index 000..9377027
> --- /dev/null
> +++ b/debian/patches/reproducible-build.patch
> @@ -0,0 +1,26 @@
> +Author: Reiner Herrmann 
> +Description: Replace current year with static value to get reproducible build
> +
> +--- a/src/Makefile.am
>  b/src/Makefile.am
> +@@ -214,8 +214,7 @@
> + -DDATA_PATH=\""$(pkgdatadir)/data/"\"\
> + -DUI_PATH=\""$(pkgdatadir)/ui/"\"\
> + -DARIO_PLUGIN_DIR=\"$(PLUGINDIR)\"\
> +--DARIO_PLUGIN_DATA_DIR=\"$(PLUGIN_DATA_DIR)\"\
> +--DCURRENT_DATE="\"`date +%G`\""
> ++-DARIO_PLUGIN_DATA_DIR=\"$(PLUGIN_DATA_DIR)\"
> + 
> + if MPD_GLIB
> + AM_CPPFLAGS += -DMPD_GLIB
> +--- a/src/shell/ario-shell.c
>  b/src/shell/ario-shell.c
> +@@ -821,7 +821,7 @@
> +"name", "Ario",
> +"program-name", "Ario",
> +"version", PACKAGE_VERSION,
> +-   "copyright", "Copyright \xc2\xa9 2005-" 
> CURRENT_DATE " Marc Pavot",
> ++   "copyright", "Copyright \xc2\xa9 2005-2011 
> Marc Pavot",
> +"comments", _("GTK client for MPD"),
> +"translator-credits", 
> _("translator-credits"),
> +"authors", (const char **) authors,
> diff --git a/debian/patches/series b/debian/patches/series
> index 7e66345..60ef58f 100644
> --- a/debian/patches/series
> +++ b/debian/patches/series
> @@ -1 +1,2 @@
>  glib-single-include.patch
> +reproducible-build.patch


signature.asc
Description: PGP signature

Bug#1021362: linux-image-amd64-5.19.0-2-amd64

[karol]

Package: linux-image-amd64
Version: 5.19.11-1
Severity: normal
X-Debbugs-Cc: karol...@gmail.com

Hello, i915 video module driver crashes which is visible in the below stack 
trace. Problem is repeatable.
My operating system is Debian testing (bookworm) and computer Lenovo Thinkpad 
X1 Carbon 10th.


paź 06 19:39:00 karol kernel: [ cut here ]
paź 06 19:39:00 karol kernel: i915 :00:02.0: Block 42 min_size is zero
paź 06 19:39:00 karol kernel: WARNING: CPU: 6 PID: 226 at 
drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x64c/0x720 [i915]
paź 06 19:39:00 karol kernel: Modules linked in: i915(+) crc32_pclmul 
crc32c_intel hid_generic drm_buddy i2c_algo_bit ghash_clmulni_intel xhci_pci 
drm_display_helper nvme xhci_hcd nvme_core cec rc_core t>
paź 06 19:39:00 karol kernel: CPU: 6 PID: 226 Comm: systemd-udevd Not tainted 
5.19.0-2-amd64 #1  Debian 5.19.11-1
paź 06 19:39:00 karol kernel: Hardware name: LENOVO 21CB007BPB/21CB007BPB, BIOS 
N3AET66W (1.31 ) 09/09/2022
paź 06 19:39:00 karol kernel: RIP: 0010:init_bdb_block+0x64c/0x720 [i915]
paź 06 19:39:00 karol kernel: Code: 8b 5f 50 48 85 db 0f 84 95 00 00 00 4c 89 
0c 24 e8 69 81 08 cf 44 89 e9 48 89 da 48 c7 c7 b8 c3 73 c0 48 89 c6 e8 88 6f 
34 cf <0f> 0b 4c 8b 0c 24 e9 f9 f9 ff ff 48 83 >
paź 06 19:39:00 karol kernel: RSP: 0018:aabb809b3a70 EFLAGS: 00010282
paź 06 19:39:00 karol kernel: RAX:  RBX: 9b54c1d97df0 RCX: 

paź 06 19:39:00 karol kernel: RDX: 0001 RSI: 4ffb RDI: 

paź 06 19:39:00 karol kernel: RBP: aabb807988f3 R08:  R09: 
efff
paź 06 19:39:00 karol kernel: R10: aabb809b3910 R11: 908d1f08 R12: 
9b54fca18000
paź 06 19:39:00 karol kernel: R13: 002a R14:  R15: 
aabb80798048
paź 06 19:39:00 karol kernel: FS:  7f3b159098c0() 
GS:9b5bff58() knlGS:
paź 06 19:39:00 karol kernel: CS:  0010 DS:  ES:  CR0: 80050033
paź 06 19:39:00 karol kernel: CR2: 72b9ea58 CR3: 000151cae004 CR4: 
00770ee0
paź 06 19:39:00 karol kernel: PKRU: 5554
paź 06 19:39:00 karol kernel: Call Trace:
paź 06 19:39:00 karol kernel:  
paź 06 19:39:00 karol kernel:  ? kfree+0xc9/0x2f0
paź 06 19:39:00 karol kernel:  intel_bios_init+0x18e/0x3130 [i915]
paź 06 19:39:00 karol kernel:  ? sched_set_fifo+0x54/0x80
paź 06 19:39:00 karol kernel:  ? drm_vblank_worker_init+0x67/0x70 [drm]
paź 06 19:39:00 karol kernel:  intel_modeset_init_noirq+0x35/0x240 [i915]
paź 06 19:39:00 karol kernel:  i915_driver_probe+0x572/0xd70 [i915]
paź 06 19:39:00 karol kernel:  ? intel_modeset_probe_defer+0x53/0x60 [i915]
paź 06 19:39:00 karol kernel:  ? i915_pci_probe+0x3f/0x150 [i915]
paź 06 19:39:00 karol kernel:  local_pci_probe+0x42/0x80
paź 06 19:39:00 karol kernel:  ? pci_match_device+0xdb/0x130
paź 06 19:39:00 karol kernel:  pci_device_probe+0xc5/0x230
paź 06 19:39:00 karol kernel:  really_probe+0x1ba/0x3a0
paź 06 19:39:00 karol kernel:  __driver_probe_device+0x105/0x180
paź 06 19:39:00 karol kernel:  driver_probe_device+0x1e/0x90
paź 06 19:39:00 karol kernel:  __driver_attach+0x9d/0x1f0
paź 06 19:39:00 karol kernel:  ? __device_attach_driver+0x110/0x110
paź 06 19:39:00 karol kernel:  ? __device_attach_driver+0x110/0x110
paź 06 19:39:00 karol kernel:  bus_for_each_dev+0x75/0xc0
paź 06 19:39:00 karol kernel:  bus_add_driver+0x15c/0x210
paź 06 19:39:00 karol kernel:  driver_register+0x8f/0xf0
paź 06 19:39:00 karol kernel:  i915_init+0x1d/0x80 [i915]
paź 06 19:39:00 karol kernel:  ? 0xc0853000
paź 06 19:39:00 karol kernel:  do_one_initcall+0x41/0x200
paź 06 19:39:00 karol kernel:  ? kmem_cache_alloc_trace+0x177/0x2a0
paź 06 19:39:00 karol kernel:  do_init_module+0x4c/0x200
paź 06 19:39:00 karol kernel:  __do_sys_finit_module+0xb4/0x130
paź 06 19:39:00 karol kernel:  do_syscall_64+0x38/0xc0
paź 06 19:39:00 karol kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
paź 06 19:39:00 karol kernel: RIP: 0033:0x7f3b16012719
paź 06 19:39:00 karol kernel: Code: 08 44 89 e0 5b 41 5c c3 66 0f 1f 84 00 00 
00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 
0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c7 >
paź 06 19:39:00 karol kernel: RSP: 002b:72baaf38 EFLAGS: 0246 
ORIG_RAX: 0139
paź 06 19:39:00 karol kernel: RAX: ffda RBX: 56210a2b9bb0 RCX: 
7f3b16012719
paź 06 19:39:00 karol kernel: RDX:  RSI: 7f3b161c2efd RDI: 
0012
paź 06 19:39:00 karol kernel: RBP: 7f3b161c2efd R08:  R09: 
56210a266010
paź 06 19:39:00 karol kernel: R10: 0012 R11: 0246 R12: 
0002
paź 06 19:39:00 karol kernel: R13:  R14: 56210a2b3d80 R15: 
562108c77cc1
paź 06 19:39:00 karol kernel:  
paź 06 19:39:00 karol kernel: ---[ end trace  ]---


-- System Information:
Debian Release: 

Bug#1020814: dradio: reproducible-builds: build path embedded in /usr/bin/dradio

[Chris Lamb]

tags 1020814 + pending patch
thanks

I've just uploaded dradio 3.8-2.1 to DELAYED/10:
  
  dradio (3.8-2.1) unstable; urgency=medium
  .
* Non-maintainer upload.
* Pass dpkg-buildflags(1) to upstream's build system to ensure that
  reproducibility-related CFLAGS are used; this was based on a patch by
  Vagrant Cascadian. This required the disabling of -Werror=format-security
  via DEB_BUILD_MAINT_OPTIONS due to suspicious calls to snprintf(3).
  (Closes: #1020814)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for dradio-3.8 dradio-3.8

 changelog |   11 +++
 rules |6 ++
 2 files changed, 17 insertions(+)

diff -Nru dradio-3.8/debian/changelog dradio-3.8/debian/changelog
--- dradio-3.8/debian/changelog 2011-10-07 22:06:27.0 -0700
+++ dradio-3.8/debian/changelog 2022-10-06 10:32:46.0 -0700
@@ -1,3 +1,14 @@
+dradio (3.8-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Pass dpkg-buildflags(1) to upstream's build system to ensure that
+reproducibility-related CFLAGS are used; this was based on a patch by
+Vagrant Cascadian. This required the disabling of -Werror=format-security
+via DEB_BUILD_MAINT_OPTIONS due to suspicious calls to snprintf(3).
+(Closes: #1020814)
+
+ -- Chris Lamb   Thu, 06 Oct 2022 10:32:46 -0700
+
 dradio (3.8-2) unstable; urgency=low
 
   * d/control: 
diff -Nru dradio-3.8/debian/rules dradio-3.8/debian/rules
--- dradio-3.8/debian/rules 2011-10-07 22:06:27.0 -0700
+++ dradio-3.8/debian/rules 2022-10-06 10:32:46.0 -0700
@@ -1,4 +1,10 @@
 #!/usr/bin/make -f
 
+# Disable -Werror=format-security due to upstream calls to snprintf(3)
+export DEB_BUILD_MAINT_OPTIONS=hardening=-format
+
 %:
dh $@
+
+override_dh_auto_configure:
+   dh_auto_configure -- CFLAGS="$(shell dpkg-buildflags --get CFLAGS)"

Bug#1019801: xmlcopyeditor: Please transition to wxwidgets3.2

[Scott Talbert]

reopen -1
found -1 1.3.0.0-1
severity -1 important
thanks

Resent to not -maintonly.

Bug#829721: remote-tty: please make the build reproducible

[Chris Lamb]

tags 829721 + pending patch
tags 977280 + pending patch
thanks

I've just uploaded remote-tty 4.0-13.1 to DELAYED/10:
  
  remote-tty (4.0-13.1) unstable; urgency=medium
  .
* Non-maintainer upload.
* Apply a patch by Vagrant Cascadian to make the build reproducible.
  (Closes: #829721)
* Apply a patch by Helmut Grohne to correctly pass cross-building to
  upstream's build system. (Closes: #977280)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for remote-tty_4.0-13 remote-tty_4.0-13.1

 changelog |   10 ++
 rules |2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -u remote-tty-4.0/debian/changelog remote-tty-4.0/debian/changelog
--- remote-tty-4.0/debian/changelog
+++ remote-tty-4.0/debian/changelog
@@ -1,3 +1,13 @@
+remote-tty (4.0-13.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply a patch by Vagrant Cascadian to make the build reproducible.
+(Closes: #829721)
+  * Apply a patch by Helmut Grohne to correctly pass cross-building to
+upstream's build system. (Closes: #977280)
+
+ -- Chris Lamb   Thu, 06 Oct 2022 10:19:32 -0700
+
 remote-tty (4.0-13) unstable; urgency=low
 
   * Fold in Ubuntu changes for tmpfs /var/run (closes: #587107)
diff -u remote-tty-4.0/debian/rules remote-tty-4.0/debian/rules
--- remote-tty-4.0/debian/rules
+++ remote-tty-4.0/debian/rules
@@ -17,7 +17,7 @@
 build-indep: build-stamp
 build-stamp:
dh_testdir
-   $(MAKE)
+   dh_auto_build
touch build-stamp
 
 clean:

Bug#1021358: libpam-modules-bin: fails when upgrading from 1.5.2-2 revision

[Eriberto Mota]

To avoid a new breaking when upgrading my jail, I made a "local" NMU
to remove the duplicate manpage from a package. I am not familiar with
pam packaging, so I choosen libpam-modules-bin.manpages. When
installing my "local NMU", I got:

dpkg: error processing archive
/PKGS/libpam-modules-bin/libpam-modules-bin_1.5.2-3.1_amd64.deb
(--unpack):
trying to overwrite '/usr/share/man/man8/pam_namespace_helper.8.gz',
which is also in package libpam-module
s:amd64 1.5.2-2
Errors were encountered while processing:
/PKGS/libpam-modules-bin/libpam-modules-bin_1.5.2-3.1_amd64.deb

After fixing this new issue, the package was installed fine.

Regards,

Eriberto

Bug#1007421: ascii2binary: reproducible-builds: build path embedded in /usr/bin/ascii2binary

[Chris Lamb]

tags 1020812 + pending patch
tags 998758 + pending patch
tags 1007421 + pending patch
thanks

I've just uploaded ascii2binary 2.14-1.1 to DELAYED/10:
  
  ascii2binary (2.14-1.1) unstable; urgency=medium
  .
* Non-maintainer upload.
* Use dpkg-buildflags(1) to ensure reproducibility-related CFLAGS are
  passed to the upstream build system. This change was based on a patch by
  Vagrant Cascadian. (Closes: #1020812)
* Switch to dpkg-source 3.0 (quilt) format. (Closes: #998758, #1007421)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for ascii2binary-2.14 ascii2binary-2.14

 changelog |   10 ++
 rules |3 +++
 source/format |1 +
 3 files changed, 14 insertions(+)

diff -Nru ascii2binary-2.14/debian/changelog ascii2binary-2.14/debian/changelog
--- ascii2binary-2.14/debian/changelog  2022-10-06 10:11:52.0 -0700
+++ ascii2binary-2.14/debian/changelog  2022-10-06 10:08:45.0 -0700
@@ -1,3 +1,13 @@
+ascii2binary (2.14-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use dpkg-buildflags(1) to ensure reproducibility-related CFLAGS are
+passed to the upstream build system. This change was based on a patch by
+Vagrant Cascadian. (Closes: #1020812)
+  * Switch to dpkg-source 3.0 (quilt) format. (Closes: #998758, #1007421)
+
+ -- Chris Lamb   Thu, 06 Oct 2022 10:08:45 -0700
+
 ascii2binary (2.14-1) unstable; urgency=low
 
   * New upstream release (Closes: #598600, #625025).
diff -Nru ascii2binary-2.14/debian/rules ascii2binary-2.14/debian/rules
--- ascii2binary-2.14/debian/rules  2022-10-06 10:11:52.0 -0700
+++ ascii2binary-2.14/debian/rules  2022-10-06 10:08:45.0 -0700
@@ -6,3 +6,6 @@
 
 %:
dh $@
+
+override_dh_auto_configure:
+   dh_auto_configure -- CFLAGS="$(shell dpkg-buildflags --get CFLAGS)"
diff -Nru ascii2binary-2.14/debian/source/format 
ascii2binary-2.14/debian/source/format
--- ascii2binary-2.14/debian/source/format  1969-12-31 16:00:00.0 
-0800
+++ ascii2binary-2.14/debian/source/format  2022-10-06 10:08:45.0 
-0700
@@ -0,0 +1 @@
+3.0 (quilt)

Bug#1020875: z80asm: reproducible-builds: build path embedded in /usr/bin/z80asm

[Chris Lamb]

Hey,

Thanks for your blessing. However, I'll leave it in DELAYED/10 just
in case I discover something over the next week or so. :)

Chris


> Thanks! I didn't get around to this. I probably won't get around to uploading
> it myself either, so feel free to skip the delayed queue, or else it'll get in
> in 10 days.
>
> On Thu, Oct 06, 2022 at 09:16:23AM -0700, Chris Lamb wrote:
>> tags 1020875 + pending patch
>> tags 939775 + pending patch
>> thanks
>> 
>> I've uploaded z80asm 1.8-1.1 to DELAYED/10:
>>   
>>   z80asm (1.8-1.1) unstable; urgency=medium
>>   .
>> * Non-maintainer upload.
>> * Apply a patch by Vagrant Cascadian to make the build reproducible. The
>>   build path was being embedded in /usr/bin/z80asm. (Closes: #1020875)
>> * Apply patch from Helmut Grohne to make as z80asm cross build 
>> correctly. It
>>   was failing because it ran its own testsuite despite the value of
>>   DEB_BUILD_OPTIONS=nocheck; the upstream build system ran them as part 
>> of
>>   the "build" target and offers no specific test target. (Closes: 
>> #939775)
>> 
>> The full debdiff is attached.
>> 
>> 
>> Regards,
>> 
>> -- 
>>   ,''`.
>>  : :'  : Chris Lamb
>>  `. `'`  la...@debian.org / chris-lamb.co.uk
>>`-
>
>> diffstat for z80asm_1.8-1 z80asm_1.8-1.1
>> 
>>  Makefile|1 -
>>  z80asm-1.8/debian/changelog |   12 
>>  z80asm-1.8/debian/rules |8 
>>  3 files changed, 20 insertions(+), 1 deletion(-)
>> 
>> diff -u z80asm-1.8/debian/changelog z80asm-1.8/debian/changelog
>> --- z80asm-1.8/debian/changelog
>> +++ z80asm-1.8/debian/changelog
>> @@ -1,3 +1,15 @@
>> +z80asm (1.8-1.1) unstable; urgency=medium
>> +
>> +  * Non-maintainer upload.
>> +  * Apply a patch by Vagrant Cascadian to make the build reproducible. The
>> +build path was being embedded in /usr/bin/z80asm. (Closes: #1020875)
>> +  * Apply patch from Helmut Grohne to make as z80asm cross build correctly. 
>> It
>> +was failing because it ran its own testsuite despite the value of
>> +DEB_BUILD_OPTIONS=nocheck; the upstream build system ran them as part of
>> +the "build" target and offers no specific test target. (Closes: #939775)
>> +
>> + -- Chris Lamb   Thu, 06 Oct 2022 09:09:08 -0700
>> +
>>  z80asm (1.8-1) unstable; urgency=low
>>  
>>* New upstream release.  Fixes defw bug.  (Closes: #519098)
>> diff -u z80asm-1.8/debian/rules z80asm-1.8/debian/rules
>> --- z80asm-1.8/debian/rules
>> +++ z80asm-1.8/debian/rules
>> @@ -1,3 +1,11 @@
>>  #!/usr/bin/make -f
>>  %:
>>  dh $@
>> +
>> +override_dh_auto_build:
>> +dh_auto_build -- CFLAGS="$(shell dpkg-buildflags --get CFLAGS)"
>> +
>> +override_dh_auto_test:
>> +ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
>> +$(MAKE) -C tests
>> +endif
>> --- z80asm-1.8.orig/Makefile
>> +++ z80asm-1.8/Makefile
>> @@ -25,7 +25,6 @@
>>  
>>  z80asm: z80asm.o expressions.o Makefile gnulib/getopt.o gnulib/getopt1.o
>>  $(CC) $(LDFLAGS) $(filter %.o,$^) -o $@
>> -$(MAKE) -C tests || rm $@
>>  
>>  %.o:%.c z80asm.h gnulib/getopt.h Makefile
>>  $(CC) $(CFLAGS) -c $< -o $@ -DVERSION=\"$(shell cat VERSION)\"

Bug#1020875: z80asm: reproducible-builds: build path embedded in /usr/bin/z80asm

[Dr. Bas Wijnen]

Thanks! I didn't get around to this. I probably won't get around to uploading
it myself either, so feel free to skip the delayed queue, or else it'll get in
in 10 days.

On Thu, Oct 06, 2022 at 09:16:23AM -0700, Chris Lamb wrote:
> tags 1020875 + pending patch
> tags 939775 + pending patch
> thanks
> 
> I've uploaded z80asm 1.8-1.1 to DELAYED/10:
>   
>   z80asm (1.8-1.1) unstable; urgency=medium
>   .
> * Non-maintainer upload.
> * Apply a patch by Vagrant Cascadian to make the build reproducible. The
>   build path was being embedded in /usr/bin/z80asm. (Closes: #1020875)
> * Apply patch from Helmut Grohne to make as z80asm cross build correctly. 
> It
>   was failing because it ran its own testsuite despite the value of
>   DEB_BUILD_OPTIONS=nocheck; the upstream build system ran them as part of
>   the "build" target and offers no specific test target. (Closes: #939775)
> 
> The full debdiff is attached.
> 
> 
> Regards,
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-

> diffstat for z80asm_1.8-1 z80asm_1.8-1.1
> 
>  Makefile|1 -
>  z80asm-1.8/debian/changelog |   12 
>  z80asm-1.8/debian/rules |8 
>  3 files changed, 20 insertions(+), 1 deletion(-)
> 
> diff -u z80asm-1.8/debian/changelog z80asm-1.8/debian/changelog
> --- z80asm-1.8/debian/changelog
> +++ z80asm-1.8/debian/changelog
> @@ -1,3 +1,15 @@
> +z80asm (1.8-1.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Apply a patch by Vagrant Cascadian to make the build reproducible. The
> +build path was being embedded in /usr/bin/z80asm. (Closes: #1020875)
> +  * Apply patch from Helmut Grohne to make as z80asm cross build correctly. 
> It
> +was failing because it ran its own testsuite despite the value of
> +DEB_BUILD_OPTIONS=nocheck; the upstream build system ran them as part of
> +the "build" target and offers no specific test target. (Closes: #939775)
> +
> + -- Chris Lamb   Thu, 06 Oct 2022 09:09:08 -0700
> +
>  z80asm (1.8-1) unstable; urgency=low
>  
>* New upstream release.  Fixes defw bug.  (Closes: #519098)
> diff -u z80asm-1.8/debian/rules z80asm-1.8/debian/rules
> --- z80asm-1.8/debian/rules
> +++ z80asm-1.8/debian/rules
> @@ -1,3 +1,11 @@
>  #!/usr/bin/make -f
>  %:
>   dh $@
> +
> +override_dh_auto_build:
> + dh_auto_build -- CFLAGS="$(shell dpkg-buildflags --get CFLAGS)"
> +
> +override_dh_auto_test:
> +ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
> + $(MAKE) -C tests
> +endif
> --- z80asm-1.8.orig/Makefile
> +++ z80asm-1.8/Makefile
> @@ -25,7 +25,6 @@
>  
>  z80asm: z80asm.o expressions.o Makefile gnulib/getopt.o gnulib/getopt1.o
>   $(CC) $(LDFLAGS) $(filter %.o,$^) -o $@
> - $(MAKE) -C tests || rm $@
>  
>  %.o:%.c z80asm.h gnulib/getopt.h Makefile
>   $(CC) $(CFLAGS) -c $< -o $@ -DVERSION=\"$(shell cat VERSION)\"



signature.asc
Description: PGP signature

Bug#1020665: libimage-imlib2-perl: reproducible-builds: Embedded build path in Imlib2.so

[Chris Lamb]

tags 1020665 + pending patch
thanks

I've just uploaded libimage-imlib2-perl 2.03-1.1 to DELAYED/10:
  
  libimage-imlib2-perl (2.03-1.1) unstable; urgency=medium
  .
* Non-maintainer upload.
* Apply a patch by Vagrant Cascadian to avoid embedding the build path
  in Imlib2.so. (Closes: #1020665)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for libimage-imlib2-perl-2.03 libimage-imlib2-perl-2.03

 changelog   |8 
 patches/reproducible_build.diff |   21 +
 patches/series  |1 +
 3 files changed, 30 insertions(+)

diff -Nru libimage-imlib2-perl-2.03/debian/changelog 
libimage-imlib2-perl-2.03/debian/changelog
--- libimage-imlib2-perl-2.03/debian/changelog  2011-10-15 16:36:13.0 
-0700
+++ libimage-imlib2-perl-2.03/debian/changelog  2022-10-06 09:56:50.0 
-0700
@@ -1,3 +1,11 @@
+libimage-imlib2-perl (2.03-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply a patch by Vagrant Cascadian to avoid embedding the build path
+in Imlib2.so. (Closes: #1020665)
+
+ -- Chris Lamb   Thu, 06 Oct 2022 09:56:50 -0700
+
 libimage-imlib2-perl (2.03-1) unstable; urgency=low
 
   * New upstream release
diff -Nru libimage-imlib2-perl-2.03/debian/patches/reproducible_build.diff 
libimage-imlib2-perl-2.03/debian/patches/reproducible_build.diff
--- libimage-imlib2-perl-2.03/debian/patches/reproducible_build.diff
1969-12-31 16:00:00.0 -0800
+++ libimage-imlib2-perl-2.03/debian/patches/reproducible_build.diff
2022-10-06 09:56:50.0 -0700
@@ -0,0 +1,21 @@
+Description: Pass -ffile-prefix-map via $cflags to avoid embedding build path.
+Author: Vagrant Cascadian 
+
+--- libimage-imlib2-perl-2.03.orig/Build.PL
 libimage-imlib2-perl-2.03/Build.PL
+@@ -1,5 +1,6 @@
+ use Module::Build;
+ use strict;
++use Cwd;
+ 
+ # We need to find imlib2-config
+ my $CONFIG = "imlib2-config";
+@@ -20,7 +21,7 @@ point to the imlib2-config program that
+ }
+ 
+ my $libs = `$CONFIG --libs`;
+-my $cflags = "-DX_DISPLAY_MISSING " . `$CONFIG --cflags`;
++my $cflags = "-DX_DISPLAY_MISSING " . `$CONFIG --cflags` . 
"-ffile-prefix-map=" . getcwd() . "=." ;
+ 
+ my $build = Module::Build->new(
+   c_source => './lib/Image',
diff -Nru libimage-imlib2-perl-2.03/debian/patches/series 
libimage-imlib2-perl-2.03/debian/patches/series
--- libimage-imlib2-perl-2.03/debian/patches/series 2011-10-15 
16:36:13.0 -0700
+++ libimage-imlib2-perl-2.03/debian/patches/series 2022-10-06 
09:56:50.0 -0700
@@ -1 +1,2 @@
 add_more_error_reporting.diff
+reproducible_build.diff

Bug#1021361: pulseaudio: No sound, the output device changed to Dummy Output

[lisenik]

Package: pulseaudio
Version: 16.1+dfsg1-2
Severity: normal
X-Debbugs-Cc: lise...@mail.ru

Dear Maintainer,

I have performed an upgrade, after which the soung output changed to Dummy
Output. There is no sound in the system and no configuration changes available,
when I try to  check the sound in the Sound Settings, it does not respond and
crashes.
I tried to reinstall and restart pulseaudio, to no effect. I expected to have
the sound back.



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

Kernel: Linux 5.19.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 pulseaudio depends on:
ii  adduser 3.129
ii  init-system-helpers 1.64
ii  libasound2  1.2.7.2-1
ii  libasound2-plugins  1.2.7.1-1
ii  libc6   2.35-1
ii  libcap2 1:2.44-1
ii  libdbus-1-3 1.14.2-1
ii  libfftw3-single33.3.8-2
ii  libgcc-s1   12.2.0-3
ii  libglib2.0-02.74.0-2
ii  libgstreamer-plugins-base1.0-0  1.20.3-2
ii  libgstreamer1.0-0   1.20.3-1
ii  libice6 2:1.0.10-1
ii  libltdl72.4.7-4
ii  liborc-0.4-01:0.4.32-2
ii  libpulse0   16.1+dfsg1-2
ii  libsm6  2:1.2.3-1
ii  libsndfile1 1.1.0-2
ii  libsoxr00.1.3-4
ii  libspeexdsp11.2.1-1
ii  libstdc++6  12.2.0-3
ii  libsystemd0 251.4-3
ii  libtdb1 1.4.7-1
ii  libudev1251.4-3
ii  libwebrtc-audio-processing1 0.3-1+b1
ii  libwrap07.6.q-31
ii  libx11-62:1.8.1-2
ii  libx11-xcb1 2:1.8.1-2
ii  libxcb1 1.15-1
ii  libxtst62:1.2.3-1.1
ii  lsb-base11.4
ii  pulseaudio-utils16.1+dfsg1-2
ii  sysvinit-utils [lsb-base]   3.05-6

Versions of packages pulseaudio recommends:
ii  dbus-user-session1.14.2-1
ii  libpam-systemd [logind]  251.4-3
ii  rtkit0.13-4

Versions of packages pulseaudio suggests:
pn  paprefs  
ii  pavucontrol  5.0-2
pn  pavumeter
ii  udev 251.4-3

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = 

Bug#1021360: no video output from HDMI ports on Radeon RX 6600 [amdgpu]

[Michael Gold]

Package: src:linux
Version: 5.19.11-1
Severity: important

Dear Maintainer,

I just bought a new video card:
"Gigabyte EAGLE Radeon RX 6600 8GB PCI-E w/ Dual HDMI, Dual DP"

After installing it (as the sole video card) and connecting two monitors
via the HDMI ports (with HDMI-to-DVI adapters/cables), everything seemed
fine at first: the firmware, GRUB, and early Linux messages were visible
on my primary monitor.  Near the point in the boot process when the font
visibly changes (10-20 seconds in), it lost its signal and both monitors
remained unusable.

I was able to SSH in, and see that no monitors were detected by Linux or
the X server.  dmesg showed:
 [   16.211071] amdgpu :0a:00.0: [drm] Cannot find any crtc or sizes
xrandr showed "disconnected" beside each output ("HDMI-A-0", "HDMI-A-1",
"DisplayPort-0", and "DisplayPort-1").

Based on some web searching, I passed "amdgpu.dc=0" and "amdgpu.runpm=0"
to the kernel; neither helped.  "nomodeset" got my primary monitor going
(seeing a 1920×1080 signal, stretched unevenly from 1280-by-something).

After looking at the kernel code, I found the outputs could be forced on
using kernel options: "video=HDMI-A-1:D video=HDMI-A-2:D".  That kind of
worked.  The primary monitor (NEC EA231WMi) is fully working.  The other
one (BenQ BL2400) was detected--the X server read the EDID and created a
proper mode list--but just showed "no signal" on a black screen (or, one
time, on a blue screen after I tried forcing some custom modes).

The BenQ monitor started working as soon as I tried a DisplayPort cable.
Naturally, I'd had no such cable on hand when I noticed the problem, nor
any device with an HDMI input.  I'm wondering if something is broken for
the "DVI over HDMI" support.  I consider it an important feature: around
10 years ago, when I bought the monitors, many manufacturers were trying
to avoid paying HDMI's per-port fees, and DisplayPort was not yet common
in the (several-year-old) video cards people were likely to connect them
to.  (So, others are likely to have similar cables/adapters plugged into
their monitors.)

Additionally, the feature of disabling all video outputs when nothing is
detected seems like something that ought to be reconsidered.

- Michael


-- Package-specific info:
** Version:
Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 
11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38.90.20220713) #1 SMP 
PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24)

** Command line:
BOOT_IMAGE=/vmlinuz-5.19.0-2-amd64 root=UUID= ro 
rootflags=subvol=@rootfs quiet

** Not tainted

** Kernel log:
Attached.

** Model information
sys_vendor: ASUS
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 2403
board_vendor: ASUSTeK COMPUTER INC.
board_name: ROG STRIX B550-E GAMING
board_version: Rev X.0x

** Loaded modules:
snd_seq_dummy
snd_hrtimer
snd_seq
snd_seq_device
nft_redir
nft_chain_nat
nf_nat
nft_reject_inet
nf_reject_ipv4
nf_reject_ipv6
nft_reject
nft_ct
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
nf_tables
nfnetlink
binfmt_misc
amdgpu
btusb
iwlmvm
btrtl
btbcm
btintel
btmtk
bluetooth
snd_hda_codec_realtek
mac80211
snd_hda_codec_generic
ledtrig_audio
snd_hda_codec_hdmi
intel_rapl_msr
intel_rapl_common
snd_hda_intel
jitterentropy_rng
amd64_edac
snd_intel_dspcfg
edac_mce_amd
joydev
libarc4
asus_ec_sensors
gpu_sched
snd_intel_sdw_acpi
snd_hda_codec
drm_display_helper
kvm_amd
sha512_ssse3
iwlwifi
sha512_generic
cec
snd_hda_core
eeepc_wmi
kvm
snd_hwdep
asus_wmi
rc_core
cfg80211
drm_ttm_helper
snd_pcm
platform_profile
irqbypass
battery
ttm
drbg
sparse_keymap
video
evdev
rapl
snd_timer
ansi_cprng
drm_kms_helper
wmi_bmof
mxm_wmi
snd
pcspkr
sp5100_tco
efi_pstore
ccp
ecdh_generic
k10temp
soundcore
watchdog
i2c_algo_bit
xpad
rng_core
rfkill
ecc
ff_memless
acpi_cpufreq
button
sg
nct6775
nct6775_core
hwmon_vid
parport_pc
ppdev
lp
drm
parport
fuse
configfs
ip_tables
x_tables
autofs4
btrfs
blake2b_generic
zstd_compress
nls_ascii
nls_cp437
vfat
fat
ext4
crc16
mbcache
jbd2
dm_crypt
dm_mod
efivarfs
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
libcrc32c
crc32c_generic
raid0
multipath
linear
ses
enclosure
sd_mod
scsi_transport_sas
hid_generic
raid1
uas
usbhid
usb_storage
hid
crc32_pclmul
crc32c_intel
md_mod
ahci
libahci
ghash_clmulni_intel
xhci_pci
nvme
libata
xhci_hcd
nvme_core
t10_pi
aesni_intel
usbcore
igc
scsi_mod
crc64_rocksoft_generic
crypto_simd
cryptd
crc64_rocksoft
ptp
crc_t10dif
i2c_piix4
crct10dif_generic
crct10dif_pclmul
pps_core
crc64
usb_common
scsi_common
crct10dif_common
gpio_amdpt
wmi
gpio_generic

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
Root Complex [1022:1480]
Subsystem: ASUSTeK Computer Inc. Starship/Matisse Root Complex 
[1043:8808]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- 

Bug#1020748: xcolmix: reproducible-builds: Embedded build path in /usr/bin/xcolmix

[Chris Lamb]

tags 1020748 + pending patch
tags 999219 + pending patch
tags 988018 + pending patch

thanks

I've just uploaded xcolmix 1.07-10.1 to DELAYED/10:
  
  xcolmix (1.07-10.1) unstable; urgency=medium
  .
* Non-maintainer upload.
* Add missing required debian/rules targets build-arch and/or build-indep.
  (Closes: #999219)
* Apply a patch by Helmut Grohne to correctly pass cross-building tools to
  Make. (Closes: #988018)
* Make the build reproducible by adapting debian/rules to use CFLAGS from
  dpkg-buildflags(1), appending -ffile-prefix-map. (Closes: #1020748)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for xcolmix-1.07 xcolmix-1.07

 changelog |   12 
 rules |5 -
 2 files changed, 16 insertions(+), 1 deletion(-)

diff -Nru xcolmix-1.07/debian/changelog xcolmix-1.07/debian/changelog
--- xcolmix-1.07/debian/changelog   2010-05-27 17:47:37.0 -0700
+++ xcolmix-1.07/debian/changelog   2022-10-06 09:41:37.0 -0700
@@ -1,3 +1,15 @@
+xcolmix (1.07-10.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing required debian/rules targets build-arch and/or build-indep.
+(Closes: #999219)
+  * Apply a patch by Helmut Grohne to correctly pass cross-building tools to
+Make. (Closes: #988018)
+  * Make the build reproducible by adapting debian/rules to use CFLAGS from
+dpkg-buildflags(1), appending -ffile-prefix-map. (Closes: #1020748)
+
+ -- Chris Lamb   Thu, 06 Oct 2022 09:41:37 -0700
+
 xcolmix (1.07-10) unstable; urgency=low
 
   * Rebuild against libforms2.
diff -Nru xcolmix-1.07/debian/rules xcolmix-1.07/debian/rules
--- xcolmix-1.07/debian/rules   2010-05-27 17:45:10.0 -0700
+++ xcolmix-1.07/debian/rules   2022-10-06 09:41:37.0 -0700
@@ -7,10 +7,13 @@
 
 package=xcolmix
 
+build-arch: build
+build-indep: build
+
 build:
$(checkdir)
 
-   (cd src; make final STDLFLAGS="-L /usr/X11R6/lib" STDCFLAGS="-c -O2 
-Wall $(XFINCDIR) -g")
+   dh_auto_build --sourcedirectory=src -- final STDLFLAGS="-L 
/usr/X11R6/lib" STDCFLAGS="$(XFINCDIR) $(shell dpkg-buildflags --get CFLAGS)"
touch build
 
 clean:

Bug#1021235: python-pymeasure: please switch to QtWidgets.QTreeWidgetItem

[Michael R. Crusoe]

On Tue, 4 Oct 2022 07:52:21 +0200 Gianfranco Costamagna 
 wrote:

> Source: python-pymeasure
> Version: 0.9.0-1
> Severity: serious
>
> Hello, I noticed there is also a 0.10.0 version, but probably in 
order to fix autopkgtests/build against new python-pyqtgraph

> some additional patches are needed, e.g.
> 4d35e9eebb548453867b4c562a80eb5851918186
> fcd8df95e9f1da17c87917c64f3f5abf96a9aa3d
> 7014231851cf731aa253c41da9e6e38abfd81ead
> 26f8bdbf236527bbe3c1800f37ccbe1e6be8b841
> ee586f4f5ee0fba1b77d48f3052549b99f520324
>
>
> Sorry for breaking your package in sid, I didn't know there was this 
reverse-dependency when I uploaded.


Hello Gianfranco,

Can you send us a merge request with those patches applied?


https://salsa.debian.org/science-team/python-pymeasure/-/merge_requests


Thanks,


Michael R. Crusoe

Bug#1021359: qtmir FTBFS on 32bit and riscv64: symbols differences

[Adrian Bunk]

Source: qtmir
Version: 0.7.0-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=qtmir

Bug#777413: mailto: please make the build reproducible

[Chris Lamb]

tags 777413 + pending patch
thanks

I've just uploaded mailto 1.3.2-3.1 to DELAYED/10:
  
  mailto (1.3.2-3.1) unstable; urgency=medium
  .
* Non-maintainer upload.
* Implement the required build-arch and build-indep targets in debian/rules.
  (Closes: #998978)
* Make the build reproducible by adding "-n" to the gzip(1) invocation.
  (Closes: #777413)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for mailto_1.3.2-3 mailto_1.3.2-3.1

 changelog |   10 ++
 rules |5 -
 2 files changed, 14 insertions(+), 1 deletion(-)

diff -u mailto-1.3.2/debian/changelog mailto-1.3.2/debian/changelog
--- mailto-1.3.2/debian/changelog
+++ mailto-1.3.2/debian/changelog
@@ -1,3 +1,13 @@
+mailto (1.3.2-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Implement the required build-arch and build-indep targets in debian/rules.
+(Closes: #998978)
+  * Make the build reproducible by adding "-n" to the gzip(1) invocation.
+(Closes: #777413)
+
+ -- Chris Lamb   Thu, 06 Oct 2022 09:26:08 -0700
+
 mailto (1.3.2-3) unstable; urgency=low
 
   * Disable included version of getline() since it is unused and produce
diff -u mailto-1.3.2/debian/rules mailto-1.3.2/debian/rules
--- mailto-1.3.2/debian/rules
+++ mailto-1.3.2/debian/rules
@@ -37,6 +37,9 @@
 installdoc= install -g root -o root -m 644
 installscript = install -g root -o root -m 755
 
+build-arch: build
+build-indep: build
+
 build:
$(MAKE) CFLAGS="$(CFLAGS)"
touch stamp-build
@@ -66,7 +69,7 @@
#
$(installdoc) debian/changes 
debian/tmp/usr/share/doc/$(package)/changelog
$(installdoc) debian/{readme,usage}.txt 
debian/tmp/usr/share/doc/$(package)
-   gzip -9f 
debian/tmp/usr/share/doc/$(package)/{changelog{,.Debian},{readme,usage}.txt}
+   gzip -9fn 
debian/tmp/usr/share/doc/$(package)/{changelog{,.Debian},{readme,usage}.txt}
#
$(installdir) debian/tmp/etc
$(installdoc) debian/mailto.conf debian/tmp/etc

Bug#1009890: Fixed

[Ron Murray]

It turns out that the problem is, in fact, in package qca2. 

When decrypting or signing a file, qca would invoke gpg with the
pinentry mode set to "loopback". This would normally cause gpg to ask
for a password on the console, but, of course, there isn't one in a GUI
application.

This patch sets the pinentry mode to "default" when we're decrypting or
signing, which should cause the normal pinentry dialog to be
displayed.

Tags: Patch provided

-- 
Ron Murray 
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761

When decrypting or signing a file, qca would invoke gpg with the
pinentry mode set to "loopback". This would normally cause gpg to ask
for a password on the console, but, of course, there isn't one.

This patch sets the pinentry mode to "default" when we're decrypting
or signing, which should cause the normal pinentry dialog to be
displayed.

--- qca2-2.3.4.orig/plugins/qca-gnupg/gpgaction.cpp
+++ qca2-2.3.4/plugins/qca-gnupg/gpgaction.cpp
@@ -329,6 +329,7 @@ void GpgAction::start()
 extra = true;
 collectOutput = false;
 allowInput= true;
+		proc.needPass = true;
 if (input.opt_ascii)
 writeText = true;
 break;
@@ -341,6 +342,7 @@ void GpgAction::start()
 extra = true;
 collectOutput = false;
 allowInput= true;
+		proc.needPass = true;
 if (input.opt_ascii)
 readText = true;
 signing = true;
@@ -361,6 +363,7 @@ void GpgAction::start()
 extra = true;
 collectOutput = false;
 allowInput= true;
+		proc.needPass = true;
 if (input.opt_ascii)
 readText = true;
 signing = true;
--- qca2-2.3.4.orig/plugins/qca-gnupg/gpgproc/gpgproc.cpp
+++ qca2-2.3.4/plugins/qca-gnupg/gpgproc/gpgproc.cpp
@@ -27,6 +27,8 @@ using namespace QCA;
 
 namespace gpgQCAPlugin {
 
+bool GPGProc::needPass;
+
 void releaseAndDeleteLater(QObject *owner, QObject *obj)
 {
 obj->disconnect(owner);
@@ -166,7 +168,12 @@ void GPGProc::Private::setupArguments()
 QStringList fullargs;
 fullargs += QStringLiteral("--no-tty");
 fullargs += QStringLiteral("--pinentry-mode");
-fullargs += QStringLiteral("loopback");
+
+	// Change pinentry-mode if we need to get a passphrase from the user
+	if (needPass)
+		fullargs += QStringLiteral("default");
+	else
+		fullargs += QStringLiteral("loopback");
 
 if (mode == ExtendedMode) {
 fullargs += QStringLiteral("--enable-special-filenames");
@@ -459,6 +466,7 @@ GPGProc::GPGProc(QObject *parent)
 : QObject(parent)
 {
 d = new Private(this);
+	needPass = false;
 }
 
 GPGProc::~GPGProc()
--- qca2-2.3.4.orig/plugins/qca-gnupg/gpgproc/gpgproc.h
+++ qca2-2.3.4/plugins/qca-gnupg/gpgproc/gpgproc.h
@@ -64,6 +64,7 @@ public:
 void closeStdin();
 void closeAux();
 void closeCommand();
+	static bool needPass;
 
 Q_SIGNALS:
 void error(gpgQCAPlugin::GPGProc::Error error);


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

Bug#1021358: libpam-modules-bin: fails when upgrading from 1.5.2-2 revision

[Joao Eriberto Mota Filho]

Package: libpam-modules-bin
Version: 1.5.2-3
Severity: grave
Justification: renders package unusable

Dear maintainer,

When upgrading my jail Sid, I got:

Preparing to unpack .../libpam-modules-bin_1.5.2-3_amd64.deb ...
Unpacking libpam-modules-bin (1.5.2-3) over (1.5.2-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/libpam-modules-bin_1.5.2-3_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man5/namespace.conf.5.gz', which is also
 in package libpam-modules:amd64 1.5.2-2
Errors were encountered while processing:
 /var/cache/apt/archives/libpam-modules-bin_1.5.2-3_amd64.deb

Thanks!

Eriberto

Bug#1020875: z80asm: reproducible-builds: build path embedded in /usr/bin/z80asm

[Chris Lamb]

tags 1020875 + pending patch
tags 939775 + pending patch
thanks

I've uploaded z80asm 1.8-1.1 to DELAYED/10:
  
  z80asm (1.8-1.1) unstable; urgency=medium
  .
* Non-maintainer upload.
* Apply a patch by Vagrant Cascadian to make the build reproducible. The
  build path was being embedded in /usr/bin/z80asm. (Closes: #1020875)
* Apply patch from Helmut Grohne to make as z80asm cross build correctly. It
  was failing because it ran its own testsuite despite the value of
  DEB_BUILD_OPTIONS=nocheck; the upstream build system ran them as part of
  the "build" target and offers no specific test target. (Closes: #939775)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for z80asm_1.8-1 z80asm_1.8-1.1

 Makefile|1 -
 z80asm-1.8/debian/changelog |   12 
 z80asm-1.8/debian/rules |8 
 3 files changed, 20 insertions(+), 1 deletion(-)

diff -u z80asm-1.8/debian/changelog z80asm-1.8/debian/changelog
--- z80asm-1.8/debian/changelog
+++ z80asm-1.8/debian/changelog
@@ -1,3 +1,15 @@
+z80asm (1.8-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply a patch by Vagrant Cascadian to make the build reproducible. The
+build path was being embedded in /usr/bin/z80asm. (Closes: #1020875)
+  * Apply patch from Helmut Grohne to make as z80asm cross build correctly. It
+was failing because it ran its own testsuite despite the value of
+DEB_BUILD_OPTIONS=nocheck; the upstream build system ran them as part of
+the "build" target and offers no specific test target. (Closes: #939775)
+
+ -- Chris Lamb   Thu, 06 Oct 2022 09:09:08 -0700
+
 z80asm (1.8-1) unstable; urgency=low
 
   * New upstream release.  Fixes defw bug.  (Closes: #519098)
diff -u z80asm-1.8/debian/rules z80asm-1.8/debian/rules
--- z80asm-1.8/debian/rules
+++ z80asm-1.8/debian/rules
@@ -1,3 +1,11 @@
 #!/usr/bin/make -f
 %:
dh $@
+
+override_dh_auto_build:
+   dh_auto_build -- CFLAGS="$(shell dpkg-buildflags --get CFLAGS)"
+
+override_dh_auto_test:
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
+   $(MAKE) -C tests
+endif
--- z80asm-1.8.orig/Makefile
+++ z80asm-1.8/Makefile
@@ -25,7 +25,6 @@
 
 z80asm: z80asm.o expressions.o Makefile gnulib/getopt.o gnulib/getopt1.o
$(CC) $(LDFLAGS) $(filter %.o,$^) -o $@
-   $(MAKE) -C tests || rm $@
 
 %.o:%.c z80asm.h gnulib/getopt.h Makefile
$(CC) $(CFLAGS) -c $< -o $@ -DVERSION=\"$(shell cat VERSION)\"

Bug#725434: workaround for injected TMPDIR

[David Schmitt]

This also affects sbuild. To avoid the issue, I've added the following to
my ~/.sbuildrc:

$external_commands = {
"chroot-setup-commands" => [
'runuser -u sbuild -- mkdir -v -m 1777 -p "/tmp/user/1000"',
],
};

Regards, David

Bug#1021357: gcc-12: FTBFS on hurd-i386

[Svante Signell]

Source: gcc-12
Version: 12_12.2.0-5
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
Affects: gcc-11, gcc-snapshot
X-Debbugs-CC: debian-h...@lists.debian.org

Hi,

gcc-12-12.2.0-4/5 in sid FTBFS on hurd-i386 due to failing linkage of
pthread_once (same error for gcc-11, gcc-12, gcc-snapshot):
/<>/build/i686-gnu/libstdc++-v3/include/i686-gnu/bits/gthr-
default.h:700: undefined reference to `pthread_once'

Patches have already submitted upstream by Samuel Thibault in August and
September, see
https://gcc.gnu.org/pipermail/gcc-patches/2022-August/600469.html
https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601754.html

Unfortunately upstream is not very responsive. Therefore I have taken the time
to send these patches to Debian in the mean time.

Patches extracted and attached from that mail message are:
1.diff-6.diff. Note that 1.diff does not apply to gcc-12, it is related to the
git repo. This is reflected in attached debian_rules.patch by commenting out
1.diff.

Just a reflection: Matthias you are really doing a great job with the
gcc releases: Kudos!

Thanks!

diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index ba5939d9003..dd288cce2ca 100644
--- a/src/libstdc++-v3/ChangeLog
+++ b/src/libstdc++-v3/ChangeLog
@@ -1,3 +1,11 @@
+2022-08-28  Samuel Thibault  
+
+   * config/os/gnu/os_defines.h: New file.
+   * config/os/gnu/ctype_base.h: New file.
+   * config/os/gnu/ctype_configure_char.cc: New file.
+   * config/os/gnu/ctype_inline.h: New file.
+   * configure.host: On gnu* host, use os/gnu instead of os/gnu-linux.
+
 2022-08-27  Patrick Palka  
diff --git a/src/libstdc++-v3/config/os/gnu/ctype_base.h b/src/libstdc++-v3/config/os/gnu/ctype_base.h
new file mode 100644
index 000..955146543db
--- /dev/null
+++ b/src/libstdc++-v3/config/os/gnu/ctype_base.h
@@ -0,0 +1,66 @@
+// Locale support -*- C++ -*-
+
+// Copyright (C) 1997-2022 Free Software Foundation, Inc.
+//
+// This file is part of the GNU ISO C++ Library.  This library is free
+// software; you can redistribute it and/or modify it under the
+// terms of the GNU General Public License as published by the
+// Free Software Foundation; either version 3, or (at your option)
+// any later version.
+
+// This library is distributed in the hope that it will be useful,
+// but WITHOUT ANY WARRANTY; without even the implied warranty of
+// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+// GNU General Public License for more details.
+
+// Under Section 7 of GPL version 3, you are granted additional
+// permissions described in the GCC Runtime Library Exception, version
+// 3.1, as published by the Free Software Foundation.
+
+// You should have received a copy of the GNU General Public License and
+// a copy of the GCC Runtime Library Exception along with this program;
+// see the files COPYING3 and COPYING.RUNTIME respectively.  If not, see
+// .
+
+/** @file bits/ctype_base.h
+ *  This is an internal header file, included by other library headers.
+ *  Do not attempt to use it directly. @headername{locale}
+ */
+
+//
+// ISO C++ 14882: 22.1  Locales
+//
+
+// Information as gleaned from /usr/include/ctype.h
+
+namespace std _GLIBCXX_VISIBILITY(default)
+{
+_GLIBCXX_BEGIN_NAMESPACE_VERSION
+
+  /// @brief  Base class for ctype.
+  struct ctype_base
+  {
+// Non-standard typedefs.
+typedef const int* 		__to_type;
+
+// NB: Offsets into ctype::_M_table force a particular size
+// on the mask type. Because of this, we don't use an enum.
+typedef unsigned short 	mask;
+static const mask upper	= _ISupper;
+static const mask lower 	= _ISlower;
+static const mask alpha 	= _ISalpha;
+static const mask digit 	= _ISdigit;
+static const mask xdigit 	= _ISxdigit;
+static const mask space 	= _ISspace;
+static const mask print 	= _ISprint;
+static const mask graph 	= _ISalpha | _ISdigit | _ISpunct;
+static const mask cntrl 	= _IScntrl;
+static const mask punct 	= _ISpunct;
+static const mask alnum 	= _ISalpha | _ISdigit;
+#if __cplusplus >= 201103L
+static const mask blank	= _ISblank;
+#endif
+  };
+
+_GLIBCXX_END_NAMESPACE_VERSION
+} // namespace
diff --git a/src/libstdc++-v3/config/os/gnu/ctype_configure_char.cc b/src/libstdc++-v3/config/os/gnu/ctype_configure_char.cc
new file mode 100644
index 000..5a88fc11ab3
--- /dev/null
+++ b/src/libstdc++-v3/config/os/gnu/ctype_configure_char.cc
@@ -0,0 +1,196 @@
+// Locale support -*- C++ -*-
+
+// Copyright (C) 2011-2022 Free Software Foundation, Inc.
+//
+// This file is part of the GNU ISO C++ Library.  This library is free
+// software; you can redistribute it and/or modify it under the
+// terms of the GNU General Public License as published by the
+// Free Software Foundation; either version 3, or (at your option)
+// any later version.
+
+// This library is distributed in the hope that it will be useful,
+// but 

Bug#1021356: greylistd: hash built-in function in python3 is salted

[Fernando M. Maresca (Monitoring Station S.A.)]

Package: greylistd
Version: 0.9.0.2
Severity: important

Dear Maintainer,


The hash() function used to hash triplets in python3 has a different
behaviour that the python2 version. 

py3 hash() is salted, so the hash it produces for the same input text differs 
between runs.

That produces two problems in greylistd:
- multiple entries added to the lists 
- checks produces different keys

To reproduce:
- start greylistd

- greylist clear
- greylist list --white (verify is empty)
- greylist add --white a.com
- greylist list --white (verify a.com is in wl)
- greylist check a.com (should be white)

- restart greylistd
- greylist list --white (verify a.com is in wl)
- greylist check a.com (returns grey, should be white)

Thank you.


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

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

Versions of packages greylistd depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.77
ii  init-system-helpers1.60
ii  lsb-base   11.1.0
ii  python33.9.2-3

Versions of packages greylistd recommends:
ii  exim4  4.94.2-7

greylistd suggests no packages.

-- debconf information excluded

Bug#1008263: plans to upload memtest86+ 6 to unstable?

[Antoine Beaupré]

Hello Fabio!

Below is an excerpt of a discussion that happened in bug #1008263 about
removing pcmemtest from Debian, to remove the duplication of work with
memtest86+:

On 2022-09-09 17:08:34, Felix Zielcke wrote:
> I wasn't sure if I should wait until the new memtest86+ gets out of
> beta and uploaded to unstable. But yeah, maybe it's better to just file
> the RM now

I am wondering if you had any plans to upload memtest86+ 6 to unstable
already? It looks like it could fix a *lot* of issues that currently
affect memtest86, which is basically unusable on modern platforms right
now.

For example, on my Framework laptop -- which only boots from EFI --
memtest86 from testing/unstable just doesn't boot at all. I am just
testing the version from experimental and, so far so good, it seems to
work fine!

Thanks for any update!

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of speech
because I have nothing to say."
- Edward Snowden

Bug#1012196: buglist

[André]

Is there an easier way to obtain all used licenses?
Actually I use
`licensecheck --check '.py|js|html|rst|sh' --recursive --deb-machine 
--merge-licenses --lines 0 *`


Or can I use just its output?

Bug#1021347: fonts-texgyre: please demote fonts-texgyre-math to Recommends

[fabian]

Hi Norbert,

Am 06.10.2022 15:55, schrieb Norbert Preining:

So dropping the depends to recommends or suggests is in principle fine,
but then we need to check which of the texlive-* packages depend on
texgyre and might need an additional dependency.


the fonts-texgyre-* packages contain only the OpenType variants of the 
fonts. The Type1 fonts and metrics are all in the tex-gyre package 
which, in turn, already merely recommends the fonts-texgyre* packages.


So, I see no reason why the fonts-texgyre* packages should have a 
stronger relationship than Recommends (or maybe even Suggests) with each 
other. The LaTeX world will be completely unaffected by this.


Cheers,

 - Fabian

Bug#1021347: fonts-texgyre: please demote fonts-texgyre-math to Recommends

[Hilmar Preuße]

Am 06.10.2022 um 15:55 teilte Norbert Preining mit:

Hi Norbert,


Not really ... I am probably most nervous about other dependencies
within TeX Live onto TeX Gyre fonts which then expects to have
the math fonts installed.

So dropping the depends to recommends or suggests is in principle fine,
but then we need to check which of the texlive-* packages depend on
texgyre and might need an additional dependency.

hille@sid-amd64:~/devel/TeXLive/github/texlive-nonbin$ grep -r gyre 
*|grep -v Data.tlpdb.lua

all/debian/cfg.d/debian-replacement.cfg:blacklist;tpm;tex-gyre;*
all/debian/cfg.d/debian-replacement.cfg:blacklist;tpm;tex-gyre-math;*
all/debian/cfg.d/debian-replacement.cfg:recommends;texlive-fonts-recommended;tex-gyre
all/debian/cfg.d/debian-replacement.cfg:depends;texlive-full;tex-gyre

So, texlive-fonts-recommended recommends tex-gyre and texlive-full pulls 
it in. tex-gyre in turn contains the full set of Type1 fonts, just 
recommends the OpenType fonts (fonts-texgyre & fonts-texgyre-math). So I 
don't see any need for action here.


Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021355: RFS: csv2latex/0.23-1 -- command-line CSV to LaTeX file converter

[Benoît Rouits]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : csv2latex
   Version  : 0.23-1
   Upstream contact : Benoît Rouits 
 * URL  : http://brouits.free.fr/csv2latex/
 * License  : GPL-2
 * Vcs  : https://git.noise.rocks/ben/csv2latex
   Section  : tex

The source builds the following binary packages:

  csv2latex - command-line CSV to LaTeX file converter

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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/c/csv2latex/csv2latex_0.23-1.dsc


Changes since the last upload:

 csv2latex (0.23-1) unstable; urgency=medium
 .
   * New upstream release 0.23 (improve stdin reading)
   * Update debian/watch (version=4)
   * Avoid usage of cdbs
   * Remove debian/compat
   * Update debian/control
   * Add debian/upstream/metadata
   * Set Standards-version to 4.6.1

Regards,
 Benoît

Bug#1021354: mouse wheel doesn't work on gnome-remote-desktop when connected remotely

[Yiyi Hu]

Package: gnome-remote-desktop
X-Debbugs-Cc: yiy...@gmail.com
Version: 43.0-2
Severity: important

Hi, dear Maintainer,

I'm using debian testing, last month, when gnome is not upgraded to
43.0-2, The mouse wheel works well when connected remotely.

After upgraded to latest gnome, with gnome-remote-desktop 43.0-2, the mouse
wheel doesn't work when we connect remotely.

But in gnome Settings app, the mouse wheel works, When I use
chrome(106.0.5249.91), firefox(102.3.0esr), telegram, the mouse wheel
doesn't
work at all.

in chrome, up/down scroll don't work, but middle click works fine
anyway.

This issue causes people have to use mouse like 15 years ago, Which is very
inconvenient, So please check this bug,

Thanks.

Bug#1013326: Tests: please add isolation-machine restriction for smoke-tests

[Paride Legovini]

Hi Reiner,

Reiner Herrmann wrote on 01/10/2022:
> Hi Paride,
> 
> On Wed, Jun 22, 2022 at 12:03:50PM +0200, Paride Legovini wrote:
>> I'll take care of merging 0.9.70-1 in Ubuntu, keeping the aforementioned
>> delta. If you end up adding skip-not-installable (or any other
>> workaround for the lack of firefox package on some Ubuntu archs) feel
>> free to ping me and I'll bring the package back in sync, so it will also
>> auto-sync in the future.
> 
> I have just uploaded firejail 0.9.70-2 to unstable, which has the
> architecture restriction in the autopkgtest from the Ubuntu diff.
> 
> Can you please enable syncing again?

Thanks for the ping, much appreciated. The Ubuntu archive is currently
in pre-release freeze for the Kinetic Kudu release, so this isn't a
good moment to do a sync from Debian. I'll do it once the new
development cycle opens (likely at the end of October).

Paride

Bug#1021353: RFS: zvbi/0.2.37-1 -- Vertical Blanking Interval (VBI) utilities

[Ileana Dumitrescu]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : zvbi
   Version  : 0.2.37-1
   Upstream contact : Ileana Dumitrescu 
 * URL  : https://github.com/zapping-vbi/zvbi
 * License  : LGPL-2+, MIT, GPL-2+, LGPL-2.1+, GPL-2+ or
BSD-3-Clause, GPL-2, BSD-2-Clause
 * Vcs  : https://salsa.debian.org/debian/zvbi
   Section  : devel

The source builds the following binary packages:

  libzvbi0 - Vertical Blanking Interval decoder (VBI) - runtime files
  libzvbi-dev - Vertical Blanking Interval decoder (VBI) - development files
  libzvbi-common - Vertical Blanking Interval decoder (VBI) - common files
  libzvbi-doc - Vertical Blanking Interval decoder (VBI) - documentation files
  zvbi - Vertical Blanking Interval (VBI) utilities

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/z/zvbi/zvbi_0.2.37-1.dsc

Changes since the last upload:

 zvbi (0.2.37-1) unstable; urgency=medium
 .
   [ Ileana Dumitrescu ]
   * New upstream release.
   * debian/control: updated maintainer email, project homepage
 bumped Standards-Version to 4.6.1 (no changes)
   * debian/copyright: updated debian copyright year, upstream contact, source
   updated licensing
   * debian/patches: removed all patches (fixed in upstream)
   * debian/rules: README.md in override_dh_installdocs
   override_dh_autoreconf to run autogen.sh
   * debian/watch: switched to new upstream repo location
 .
   [ Debian Janitor ]
   * debian/control: Use secure URI in Homepage field
   - Remove constraints unnecessary since buster (oldstable):
 + libzvbi-dev: Drop versioned constraint on libzvbi0 in Replaces.
 + libzvbi-doc: Drop versioned constraint on libzvbi-dev in Replaces.
 + zvbi: Drop versioned constraint on lsb-base in Depends.

Regards,
-- 
  Ileana Dumitrescu

GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354

Bug#1021347: fonts-texgyre: please demote fonts-texgyre-math to Recommends

[Norbert Preining]

Hi Hilmar,

> @Norbert: do you still remember why you wrote:

Not really ... I am probably most nervous about other dependencies
within TeX Live onto TeX Gyre fonts which then expects to have
the math fonts installed.

So dropping the depends to recommends or suggests is in principle fine,
but then we need to check which of the texlive-* packages depend on
texgyre and might need an additional dependency.

Hope that helps

All the best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1021350: assaultcube: Fails to configure on IPv6-only hosts

[Tobias Frost]

Thanks Axel for bringing that to my attention and pointing out that github
does not do IPv6…

I'll bring that topic upstream, maybe they can advice another place
where to download the assests…

Cheers,
--
tobi

Bug#1021347: fonts-texgyre: please demote fonts-texgyre-math to Recommends

[Hilmar Preuße]

Am 06.10.2022 um 12:57 teilte Fabian Greffrath mit:

Hi,

while I was glad to see that the math fonts have finally been split 
off of the fonts-texgyre package, I was a bit disappointed to

realize that I would have to install them anyway, because
fonts-texgyre has a hard dependency on fonts-texgyre-math. Please
consider demoting this relation to a Recommends.

I simply took over the implementation from Norbert, I also noticed that 
Dep. The only advantage would be, that one could install math fonts w/o 
having all other fonts installed.


@Norbert: do you still remember why you wrote:

Package: fonts-texgyre
Section: fonts
Architecture: all
Pre-Depends: ${misc:Pre-Depends}
Depends: fonts-texgyre-math (= ${source:Version}), ${misc:Depends}

Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021350: assaultcube: Fails to configure on IPv6-only hosts

[Axel Beckert]

Package: assaultcube
Version: 1.3.0.2+dfsg-4
Severity: minor
Tags: ipv6
Forwarded: https://github.com/orgs/community/discussions/10539

Dear Tobi,

at least on one host, the new assaultcube package fails to upgrade as
follows:

Setting up assaultcube (1.3.0.2+dfsg-4) ...
Downloading game data…dpkg: error processing package assaultcube (--configure):
 installed assaultcube package post-installation script subprocess returned 
error exit status 4
[…]
Errors were encountered while processing:
 assaultcube

Interestingly there's not even an error message from the postinst
script. It just seems to die.

Adding a "set -x" reveals that it aborts at this position:

# dpkg --configure -a
Setting up assaultcube (1.3.0.2+dfsg-4) ...
+ set -e
+ version=1.3.0.2
+ hash=9b3118e7929253f0114fa06cad8310faab646d177b4660406011152f34086b55
+ file=AssaultCube_v1.3.0.2_LockdownEdition_RC1.tar.bz2
+ 
url=https://github.com/assaultcube/AC/releases/download/v1.3.0.2/AssaultCube_v1.3.0.2_LockdownEdition_RC1.tar.bz2
+ fqfn=/var/cache/assaultcube/AssaultCube_v1.3.0.2_LockdownEdition_RC1.tar.bz2
+ targetdir=/var/lib/assaultcube/gamedata/
+ cachedir=/var/cache/assaultcube/
+ [ configure = configure ]
+ rm -rf /var/cache/assaultcube/
+ mkdir -p /var/cache/assaultcube/
+ echo -n Downloading game data…
Downloading game data…+ wget -q 
https://github.com/assaultcube/AC/releases/download/v1.3.0.2/AssaultCube_v1.3.0.2_LockdownEdition_RC1.tar.bz2
 -O /var/cache/assaultcube/AssaultCube_v1.3.0.2_LockdownEdition_RC1.tar.bz2
dpkg: error processing package assaultcube (--configure):
 installed assaultcube package post-installation script subprocess returned 
error exit status 4
Errors were encountered while processing:
 assaultcube

Running the wget call without "-q" reveals that
https://github.com/orgs/community/discussions/10539 (Github lacking IPv6
support in many places) is actually the culprit:

# wget 
https://github.com/assaultcube/AC/releases/download/v1.3.0.2/AssaultCube_v1.3.0.2_LockdownEdition_RC1.tar.bz2
 -O /var/cache/assaultcube/AssaultCube_v1.3.0.2_LockdownEdition_RC1.tar.bz2
--2022-10-06 14:34:26--  
https://github.com/assaultcube/AC/releases/download/v1.3.0.2/AssaultCube_v1.3.0.2_LockdownEdition_RC1.tar.bz2
Resolving github.com (github.com)... 140.82.121.4
Connecting to github.com (github.com)|140.82.121.4|:443... failed: Network is 
unreachable.
# echo $?
4

Unfortunately I see no possibility to fix this easily without Github
finally supporting IPv6. (Hence setting the above mention Github issue as
"forwarded" URL. Feel free to change that.)

So please at least remove that "-q" from the wget call in the postinst
script for easier diagnostics of such download failures.

(And feel free to clone this bug report if you want to track the removal
of -q separated from the download issue itself.)

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (110, 'experimental')
merged-usr: no
Architecture: i386 (i686)

Kernel: Linux 5.19.0-2-686-pae (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: OpenRC (via /run/openrc), PID 1: init

Versions of packages assaultcube depends on:
ii  bzip21.0.8-5+b1
ii  libc62.35-2
ii  libgcc-s112.2.0-5
ii  libgl1   1.5.0-1
ii  libopenal1   1:1.19.1-2
ii  libsdl2-2.0-02.24.1+dfsg-1
ii  libsdl2-image-2.0-0  2.6.2+dfsg-1
ii  libstdc++6   12.2.0-5
ii  libvorbisfile3   1.3.7-1
ii  libx11-6 2:1.8.1-2
ii  wget 1.21.3-1+b1
ii  zlib1g   1:1.2.11.dfsg-4.1

assaultcube recommends no packages.

assaultcube suggests no packages.

-- no debconf information

Bug#973861: apt: http acquire method still failing with "Undetermined error" or "Data left in the buffer"

[Julian Andres Klode]

On Thu, Oct 06, 2022 at 02:11:49PM +0200, Alexander Thomas wrote:
> We are also regularly bumping into this issue.
> Part of our build process gathers changed Debian packages w.r.t. a
> reference environment, such that the packages can be updated in an
> offline environment. The packages are gathered by means of a
> `dist-upgrade --download-only` invocation of apt-get. This can easily
> result in hundreds of packages being downloaded in one operation.
> 
> Our local APT mirror server is served through nginx/1.18.0.

Have you tried to switch it to Apache?

> The Undetermined Error is obviously caused by the `keepalive_requests`
> setting of Nginx. It defaulted to 100, hence we saw download failures
> on Gets with indices that were multiples of 100 (not consistently,
> only occasionally). Then we bumped keepalive_requests to 1000, and the
> randomly failing builds went away, until we had to handle a
> distribution upgrade in our builds, which resulted in more than 1000
> packages to be downloaded in a single operation:
> 
> Get:999 http://our.local.mirrror/jammy-merged-20220816 jammy/main
> amd64 liblapack3 amd64 3.10.0-2ubuntu1 [2504 kB]
> Get:1000 http://our.local.mirrror/jammy-merged-20220816 jammy/main
> amd64 liblbfgsb0 amd64 3.0+dfsg.3-10 [29.9 kB]
> Err:1000 http://our.local.mirrror/jammy-merged-20220816 jammy/main
> amd64 liblbfgsb0 amd64 3.0+dfsg.3-10
>   Undetermined Error [IP: 192.168.123.45 80]
> 
> The APT config has `Acquire::Retries "10";` but this does not seem to
> help with this particular failure.
> So, now we have further bumped keepalive_requests to 2000, but this
> feels like a game of whack-a-mole.

I would happily accept patches to make this work in development
releases, obviously this is not something that we can fix or analyse
on our side as the bugs depend on your specific network timing.

Instead of playing whackamole, you can presumably also set
Acquire::Max-Pipeline-Depth to 0
or
Acquire::http::Pipeline-Depth to 0
to disable pipelining.

I could also just disable pipelining for nginx.

But the problem is that apt is far too slow without pipelining
enabled, so it needs to be on by default.

Actually, browsers use up to 6 parallel connections today. I'd
prefer doing this too. My suggestion is to use min(ceil(N/6), 6)
queues for N items, so <=6 items -> 1 queue, 7-12 -> 2q, 13-18 => 3q,
etc.

This is configurable. If you set a maximum of 3 connections
per servers, you need at least 7 items (1-3, 4-6, 7-9). For
9 connections it's going to be 9*(9-1)+1=73 items to use all
queues.

But I don't know how the browsers scale this tbh.

This will also enable us to drop all our custom HTTP code
and switch to libcurl with curl_multi, gaining HTTP/2 and HTTP/3
support for deb.debian.org and HTTPS mirrors.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1021336: libpam-modules-bin: trying to overwrite '/usr/share/man/man5/namespace.conf.5.gz'

[Diederik de Haas]

Control: notfound -1 1.5.2-2
Control: found -1 1.5.2-3

On 06 Oct 2022 07:39:06 +0200 Christian Marillat  wrote:
> Package: libpam-modules-bin
> Version: 1.5.2-2
> 
> After an apt-get dist-upgrade
> 
> 
> Unpacking libpam-modules-bin (1.5.2-3) over (1.5.2-2) ...
> dpkg: error processing archive /var/cache/apt/archives/libpam-modules-
bin_1.5.2-3_powerpc.deb (--unpack):
>  trying to overwrite '/usr/share/man/man5/namespace.conf.5.gz', which is 
also in package libpam-modules:powerpc 1.5.2-2
> Errors were encountered while processing:
>  /var/cache/apt/archives/libpam-modules-bin_1.5.2-3_powerpc.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)

AFAICT 1.5.2-2 is fine; the issue is with 1.5.2-3. Updated metadata accordingly

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

Bug#1021336: libpam-modules-bin: trying to overwrite '/usr/share/man/man5/namespace.conf.5.gz'

[Diederik de Haas]

On Thu, 06 Oct 2022 12:45:08 +0200 Andreas Beckmann  wrote:
> Followup-For: Bug #1021336
> Control: severity -1 grave
> 
> It happens on all architectures, and does not seem limited upgrades:
> both libpam-modules and libpam-modules-bin in sid ship
> usr/share/man/man5/namespace.conf.5.gz
> usr/share/man/man8/pam_namespace_helper.8.gz
> 
> grave since it breaks sid chroot creation, I don't know how (or rather when)
> this will seriously affect the buildd infrastructure.

It also makes salsa's CI builds fail :-/
With the Debian kernel pipeline, these jobs now fail:
piuparts, autopkgtest and piuparts-signed

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

Bug#727343: chise-base: diff for NMU version 0.3.0-2.3

[Emanuele Rocca]

Control: tags 727343 + patch
Control: tags 727343 + pending


Dear maintainer,

I've prepared an NMU for chise-base (versioned as 0.3.0-2.3) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -u chise-base-0.3.0/debian/changelog chise-base-0.3.0/debian/changelog
--- chise-base-0.3.0/debian/changelog
+++ chise-base-0.3.0/debian/changelog
@@ -1,3 +1,14 @@
+chise-base (0.3.0-2.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use dh_update_autotools_config, dh_autoreconf and dh_autoreconf_clean in
+debian/rules. Closes: #727343
+  * Do not manually copy /usr/share/misc/config.{sub,guess} over
+libchise/config.{sub,guess} in the clean target, dh_clean takes care of
+doing that.
+
+ -- Emanuele Rocca   Thu, 06 Oct 2022 11:35:07 +0200
+
 chise-base (0.3.0-2.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u chise-base-0.3.0/debian/rules chise-base-0.3.0/debian/rules
--- chise-base-0.3.0/debian/rules
+++ chise-base-0.3.0/debian/rules
@@ -35,6 +35,9 @@
 
 libchise/config.status: libchise/configure
 	dh_testdir
+	cp libchise/libtool debian/libtool.bkp
+	dh_update_autotools_config
+	dh_autoreconf
 	cd libchise && CFLAGS="$(CFLAGS)" ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info
 
 
@@ -49,15 +52,11 @@
 clean:
 	dh_testdir
 	dh_testroot
-	rm -f build-stamp 
+	rm -f build-stamp
 	cd libchise && [ ! -f Makefile ] || $(MAKE) distclean
-ifneq "$(wildcard /usr/share/misc/config.sub)" ""
-	cp -f /usr/share/misc/config.sub libchise/config.sub
-endif
-ifneq "$(wildcard /usr/share/misc/config.guess)" ""
-	cp -f /usr/share/misc/config.guess libchise/config.guess
-endif
+	dh_autoreconf_clean
 	dh_clean 
+	-mv debian/libtool.bkp libchise/libtool
 
 install: build
 	dh_testdir