Bug#984561: Pre-approval for uploading vorta/0.7.5-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Dear Release Team,
With the exception of added translations (the bulk of the changes),
six small features added by samuel-w ("papercut" class bugs), and
commits irrelevant to the Debian package, all of the changes to
yet-to-be-uploaded vorta/0.7.5-1 since 0.7.1-4 have been to polish and
stabilise Vorta in time for Debian Bullseye. Locking/race/thread
safety issues were found along the way, and this release will close
#978105 and #983265.
Unfortunately we were a few days late due to difficulties tracking
down CI failures on armhf (and scarcity of free time). I have since
learned how to use porterboxes and qemu virtualised arm, and have
confirmed 10 runs of self-tests pass on able.debian.org, and 10 runs
of formal autopkgtests in virtualised armhf. All this time, Manuel,
the upstream maintainer was eager to learn how I was discovering these
issues, and how to replicate the test-bed, and our correspondences
make up the beginnings of a
Testing-my-upstream-Application-on-Debian-HOWTO.
Working with Manuel to stabilise Vorta has been the most inspiring and
fulfilling Debian work I've done this year, and I hope that you will
consider making an unblock exception for an upstream who has gone
above and beyond to prepare their software for its first release in
Debian stable. How many of our upstreams took the initiative to learn
to QA against a local virtualised DebCI instance, virtualised on
armhf?
It's a couple of days late, the commit list looks long, and there are
a half-dozen commits that aren't targetted fixes. I understand these
count against my case, and I trust you will consider the
community-building and technical benefits of allowing the 0.7.5
release to be part of Bullseye. I believe 0.7.5 is of significantly
higher quality than 0.7.1, and that this is the release we want in
Bullseye.
Debdiff and commit shortlog provided below, and I've additionally
attached diffs between the upstream source (with Debian patches
applied) of each Debian unstable release made (none which migrated to
testing).
= DEBDIFF =
debdiff vorta_0.7.1-4_all.deb vorta_0.7.5-1_all.deb
Files in second .deb but not in first
-
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta-0.7.5.egg-info/PKG-INFO
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta-0.7.5.egg-info/dependency_links.txt
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta-0.7.5.egg-info/entry_points.txt
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta-0.7.5.egg-info/requires.txt
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta-0.7.5.egg-info/top_level.txt
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta/assets/icons/eject.svg
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta/assets/icons/ellipsis-v.svg
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta/assets/icons/eye-slash.svg
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta/assets/icons/eye.svg
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta/assets/icons/icon.svg
-rw-r--r-- root/root /usr/lib/python3/dist-packages/vorta/borg/break_lock.py
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta/borg/info_archive.py
-rw-r--r-- root/root /usr/lib/python3/dist-packages/vorta/borg/info_repo.py
-rw-r--r-- root/root /usr/lib/python3/dist-packages/vorta/borg/rename.py
-rw-r--r-- root/root /usr/lib/python3/dist-packages/vorta/i18n/qm/vorta.gl.qm
-rw-r--r-- root/root /usr/lib/python3/dist-packages/vorta/i18n/qm/vorta.ru.qm
-rw-r--r-- root/root /usr/lib/python3/dist-packages/vorta/i18n/qm/vorta.sv.qm
-rw-r--r-- root/root /usr/lib/python3/dist-packages/vorta/keyring/kwallet.py
Files in first .deb but not in second
-
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta-0.7.1.egg-info/PKG-INFO
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta-0.7.1.egg-info/dependency_links.txt
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta-0.7.1.egg-info/entry_points.txt
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta-0.7.1.egg-info/requires.txt
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/vorta-0.7.1.egg-info/top_level.txt
-rw-r--r-- root/root /usr/lib/python3/dist-packages/vorta/borg/info.py
Control files: lines which differ (wdiff format)
Installed-Size: [-802-] {+1003+}
Version: [-0.7.1-4-] {+0.7.5-1+}
= COMMIT SHORT LOG =
af2d6a9 (HEAD, tag: v0.7.5, master) Bump version to v0.7.5, update translations
c66b102 Use json mode to list archive files. By @rblenis (#885)
bd3c479 Add untranslated strings. By @samuel-w (#902)
f7533b7 Disable codecov comments (#904)
6d8ad90 Allow to fully disable using the system keychain. (#898)
824707c Fix issue with unassigned self.handle (#899)
84c3d3c (tag: v0.7.4)
Bug#984557: unblock: ansible-base/2.10.5+dfsg-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: deb...@rocketjump.eu, hlieber...@setec.io Please unblock package ansible-base [ Reason ] Due to missing upload ACLs I unfortunately missed the soft freeze by a few days. With 2.10, upstream ansible is split into two parts, "ansible-base" and "ansible". This split is also reflected in the two source/binary packages of the same name in Debian. ansible-base is a hard-dep for ansible. I've personally been using the split packages for over two months now, and I've tested upgrades and of course used the package extensively. The packages have also been in experimental for about 6 weeks, and have been tested by several volunteers. 2.10 comes with support for ansible collections, which is the new format with which 3rd party modules/plugins are be shipped. With 2.9 currently in testing users won't be able to use those (as collection support is incomplete in 2.9). The next 2.10 upload will also come with autopkgtests which I have been working on for the last month. [ Impact ] If the unblock is not granted, I will have to upload an epoch version 2:2.9.16-1 to revert the ansible package in unstable, and ansible will ship with an older version. Backporting security fixes will be more difficult, as I'd have to correlate the changes of 2.10+ with the pre-split code of 2.9 after upstream security support runs out. Ansible-base 2.10 will also have about 12 months longer upstream security support than ansible 2.9, depending on the release schedule of 2.11+. [ Tests ] Automated tests is piuparts currently, which runs through fine. Manual tests involve running my personal playbook against my server fleet. With the next 2.10 upload there will be working autopkgtests that I've been working on for the last month. [ Risks ] ansible/ansible-base are leaf packages, with only ansible-lint and ansible-mitogen depending on those. ansible-lint works fine without changes. ansible-mitogen will need an update that's already packaged in experimental. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [ ] attach debdiff against the package in testing -> doesn't apply as currently not included in testing. [ Other info ] (Anything else the release team should know.) unblock ansible-base/2.10.5+dfsg-1
Bug#984478: marked as done (nmu: jgmenu_4.3.0-1)
Your message dated Fri, 5 Mar 2021 00:00:06 +0100 with message-id and subject line Re: Bug#984478: nmu: jgmenu_4.3.0-1 has caused the Debian Bug report #984478, regarding nmu: jgmenu_4.3.0-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: by...@debian.org Severity: normal Package jgmenu needs a binNMU to have the amd64 binary packages rebuilt on buildd after passing the NEW queue. nmu jgmenu_4.3.0-1 . amd64 . unstable . -m "Rebuild on buildd" -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- On 2021-03-03 20:36:36 -0500, Boyuan Yang wrote: > Package: release.debian.org > User: release.debian@packages.debian.org > Usertags: binnmu > X-Debbugs-Cc: by...@debian.org > Severity: normal > > Package jgmenu needs a binNMU to have the amd64 binary packages rebuilt > on buildd after passing the NEW queue. > > > nmu jgmenu_4.3.0-1 . amd64 . unstable . -m "Rebuild on buildd" Scheduled -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Processed: Re: Bug#984468: Pre-approval for uploading KDE Apps 20.12.3
Processing commands for cont...@bugs.debian.org: > tags 984468 confirmed moreinfo Bug #984468 [release.debian.org] Pre-approval for uploading KDE Apps 20.12.3 Added tag(s) confirmed and moreinfo. > user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was elb...@debian.org). > usertag 984468 unblock There were no usertags set. Usertags are now: unblock. > thanks Stopping processing here. Please contact me if you need assistance. -- 984468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984468: Pre-approval for uploading KDE Apps 20.12.3
tags 984468 confirmed moreinfo user release.debian@packages.debian.org usertag 984468 unblock thanks Hi Aurélien, On 03-03-2021 23:50, Aurélien COUDERC wrote: > I’d like to get a pre-aproval for uploading the packages listed below as > they will not have migrated to testing before the hard freeze. This seems OK. Please remove the moreinfo tag once the upload happened and retitle appropriately. Paul PS: please use reportbug next time (at least to get the contents of the report), it sets the right meta-data and provides you with a useful template too (making our review easier). OpenPGP_signature Description: OpenPGP digital signature
Bug#984494: marked as done (unblock: xpdf/3.04+git20210103-2)
Your message dated Thu, 4 Mar 2021 21:12:09 +0100
with message-id
and subject line Re: Bug#984494: unblock: xpdf/3.04+git20210103-2
has caused the Debian Bug report #984494,
regarding unblock: xpdf/3.04+git20210103-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
984494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package xpdf
-2 that I just uploaded contains a one-line patch correctly initializing the
psLevel variable. This fixes the PostScript generated for printing in
all cases where the user hasn't set a psLevel manually in the config
file. This was reported in #983880 and promptly fixed by Upstream.
I think printing PDFs is one of the most common things people do with
xpdf (apart from simply viewing them, of course), and since this is a
regression from the previous version, getting a fixed version into
bullseye is very important IMHO.
see source debdiff below.
unblock xpdf/3.04+git20210103-2
As an unrelated issue, I just noticed after uploading -2 that the
-D_FORTIFY_SOURCE=2 hardening buildflag fails to be correctly injected.
This can apparently be fixed by a small change to debian/rules:
export DEB_BUILD_MAINT_OPTIONS=hardening=+all
-export CPPFLAGS+=-DHAVE_PAPER_H
+export DEB_CPPFLAGS_MAINT_APPEND = -DHAVE_PAPER_H
Does the release team consider this a permissible change for the hard
freeze, and should I upload a -3 straight away so that one unblock will
suffice for both fixes?
thanks,
Florian
diff -Nru xpdf-3.04+git20210103/debian/changelog
xpdf-3.04+git20210103/debian/changelog
--- xpdf-3.04+git20210103/debian/changelog 2021-01-28 15:58:32.0
+0800
+++ xpdf-3.04+git20210103/debian/changelog 2021-03-04 14:20:04.0
+0800
@@ -1,3 +1,9 @@
+xpdf (3.04+git20210103-2) unstable; urgency=medium
+
+ * Fix printing when no psLevel is defined in xpdfrc (closes: #983880)
+
+ -- Florian Schlichting Thu, 04 Mar 2021 14:20:04 +0800
+
xpdf (3.04+git20210103-1) unstable; urgency=medium
* Import new upstream version 3.04+git20210103
diff -Nru xpdf-3.04+git20210103/debian/patches/983880.patch
xpdf-3.04+git20210103/debian/patches/983880.patch
--- xpdf-3.04+git20210103/debian/patches/983880.patch 1970-01-01
08:00:00.0 +0800
+++ xpdf-3.04+git20210103/debian/patches/983880.patch 2021-03-04
14:17:41.0 +0800
@@ -0,0 +1,23 @@
+commit 1b27cc5bb4491aed9d65c9f98704a693e3aabe59
+Author: Adam Sampson
+Date: Wed Mar 3 14:14:52 2021 +
+
+Initialise XPDFParams::psLevel.
+
+This meant that PostScript output didn't work unless you specified
+psLevel explicitly in the config file.
+
+Reported by Frédéric Brière in Debian bug #983880.
+
+diff --git a/xpdf/XPDFParams.cc b/xpdf/XPDFParams.cc
+index 4929bed..f33dd1e 100644
+--- a/xpdf/XPDFParams.cc
b/xpdf/XPDFParams.cc
+@@ -159,6 +159,7 @@ XPDFParams::XPDFParams(const char *cfgFileName) {
+ psImageableURY = psPaperHeight;
+ psCrop = true;
+ psDuplex = false;
++ psLevel = psLevel2;
+ initialZoom = "125";
+ continuousView = false;
+ createDefaultKeyBindings();
diff -Nru xpdf-3.04+git20210103/debian/patches/series
xpdf-3.04+git20210103/debian/patches/series
--- xpdf-3.04+git20210103/debian/patches/series 2021-01-28 14:22:16.0
+0800
+++ xpdf-3.04+git20210103/debian/patches/series 2021-03-04 14:17:21.0
+0800
@@ -1 +1,2 @@
wrapper-options-manpage.patch
+983880.patch
--- End Message ---
--- Begin Message ---
Hi Florian,
On 04-03-2021 15:51, Florian Schlichting wrote:
> xpdf 3.04+git20210103-3 is on its way to the archive, the complete
> debdiff follows below.
unblocked, thanks.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
Bug#983071: unblock: xz-utils/5.2.5-1.1
On 2021-03-04 12:32:48 [+0100], Paul Gevers wrote:
> Hi Sebastian
Hi,
> Can you please send a debdiff where you undo the renaming (where
> applicable), such that we get a better understanding of the real changes?
Sure. Please find attached.
> What I *think* we're going to do is accept the package in unstable, but
> have it age a bit in unstable before unblocking (which is going to
> happen automatically due to the hard freeze).
Oki.
> Paul
Sebastian
diff -Nru xz-utils-5.2.5/debian/changelog xz-utils-5.2.5/debian/changelog
--- xz-utils-5.2.5/debian/changelog 2020-12-28 11:25:06.0 +0100
+++ xz-utils-5.2.5/debian/changelog 2021-03-02 21:50:25.0 +0100
@@ -1,3 +1,11 @@
+xz-utils (5.2.5-1.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Update the patches for #844770 and #975981 to what upstream applied.
+ * Add a SIGPIPE fix to xzgrep (similar to xzcmp in #844770).
+
+ -- Sebastian Andrzej Siewior Tue, 02 Mar 2021 21:50:25 +0100
+
xz-utils (5.2.5-1.0) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru xz-utils-5.2.5/debian/patches/0001-Scripts-Fix-exit-status-of-xzdiff-xzcmp.patch xz-utils-5.2.5/debian/patches/0001-Scripts-Fix-exit-status-of-xzdiff-xzcmp.patch
--- xz-utils-5.2.5/debian/patches/0001-Scripts-Fix-exit-status-of-xzdiff-xzcmp.patch 1970-01-01 01:00:00.0 +0100
+++ xz-utils-5.2.5/debian/patches/0001-Scripts-Fix-exit-status-of-xzdiff-xzcmp.patch 2021-03-02 21:50:25.0 +0100
@@ -0,0 +1,118 @@
+From: Lasse Collin
+Date: Mon, 11 Jan 2021 22:01:51 +0200
+Subject: Scripts: Fix exit status of xzdiff/xzcmp.
+MIME-Version: 1.0
+Content-Type: text/plain; charset="utf-8"
+Content-Transfer-Encoding: 8bit
+
+This is a minor fix since this affects only the situation when
+the files differ and the exit status is something else than 0.
+In such case there could be SIGPIPE from a decompression tool
+and that would result in exit status of 2 from xzdiff/xzcmp
+while the correct behavior would be to return 1 or whatever
+else diff or cmp may have returned.
+
+This commit omits the -q option from xz/gzip/bzip2/lzop arguments.
+I'm not sure why the -q was used in the first place, perhaps it
+hides warnings in some situation that I cannot see at the moment.
+Hopefully the removal won't introduce a new bug.
+
+With gzip the -q option was harmful because it made gzip return 2
+instead of >= 128 with SIGPIPE. Ignoring exit status 2 (warning
+from gzip) isn't practical because bzip2 uses exit status 2 to
+indicate corrupt input file. It's better if SIGPIPE results in
+exit status >= 128.
+
+With bzip2 the removal of -q seems to be good because with -q
+it prints nothing if input is corrupt. The other tools aren't
+silent in this situation even with -q. On the other hand, if
+zstd support is added, it will need -q since otherwise it's
+noisy in normal situations.
+
+Thanks to Étienne Mollier and Sebastian Andrzej Siewior.
+---
+ src/scripts/xzdiff.in | 35 +--
+ 1 file changed, 21 insertions(+), 14 deletions(-)
+
+diff --git a/src/scripts/xzdiff.in b/src/scripts/xzdiff.in
+index eb7825c..98ac0e5 100644
+--- a/src/scripts/xzdiff.in
b/src/scripts/xzdiff.in
+@@ -116,23 +116,18 @@ elif test $# -eq 2; then
+ if test "$1$2" = --; then
+ xz_status=$(
+ exec 4>&1
+- ($xz1 -cdfq - 4>&-; echo $? >&4) 3>&- |
++ ($xz1 -cdf - 4>&-; echo $? >&4) 3>&- |
+ eval "$cmp" - - >&3
+ )
+ elif # Reject Solaris 8's buggy /bin/bash 2.03.
+ echo X | (echo X | eval "$cmp" /dev/fd/5 - >/dev/null 2>&1) 5<&0; then
++# NOTE: xz_status will contain two numbers.
+ xz_status=$(
+ exec 4>&1
+- ($xz1 -cdfq -- "$1" 4>&-; echo $? >&4) 3>&- |
+-( ($xz2 -cdfq -- "$2" 4>&-; echo $? >&4) 3>&- 5<&- &-; echo $? >&4) 3>&- |
++( ($xz2 -cdf -- "$2" 4>&-; echo $? >&4) 3>&- 5<&- &3) 5<&0
+ )
+-cmp_status=$?
+-case $xz_status in
+- *[1-9]*) xz_status=1;;
+- *) xz_status=0;;
+-esac
+-(exit $cmp_status)
+ else
+ F=`expr "/$2" : '.*/\(.*\)[-.][ablmotxz2]*$'` || F=$prog
+ tmp=
+@@ -161,10 +156,10 @@ elif test $# -eq 2; then
+ mkdir -- "${TMPDIR-/tmp}/$prog.$$" || exit 2
+ tmp="${TMPDIR-/tmp}/$prog.$$"
+ fi
+-$xz2 -cdfq -- "$2" > "$tmp/$F" || exit 2
++$xz2 -cdf -- "$2" > "$tmp/$F" || exit 2
+ xz_status=$(
+ exec 4>&1
+- ($xz1 -cdfq -- "$1" 4>&-; echo $? >&4) 3>&- |
++ ($xz1 -cdf -- "$1" 4>&-; echo $? >&4) 3>&- |
+ eval "$cmp" - '"$tmp/$F"' >&3
+ )
+ cmp_status=$?
+@@ -175,7 +170,7 @@ elif test $# -eq 2; then
+ *)
+ xz_status=$(
+ exec 4>&1
+- ($xz1 -cdfq -- "$1" 4>&-; echo $?
Bug#984494: unblock: xpdf/3.04+git20210103-2
Hi Paul,
> > As an unrelated issue, I just noticed after uploading -2 that the
> > -D_FORTIFY_SOURCE=2 hardening buildflag fails to be correctly injected.
> > This can apparently be fixed by a small change to debian/rules:
> >
> > export DEB_BUILD_MAINT_OPTIONS=hardening=+all
> >
> > -export CPPFLAGS+=-DHAVE_PAPER_H
> > +export DEB_CPPFLAGS_MAINT_APPEND = -DHAVE_PAPER_H
> >
> > Does the release team consider this a permissible change for the hard
> > freeze, and should I upload a -3 straight away so that one unblock will
> > suffice for both fixes?
>
> Please go ahead with that. Sounds like something we want for a PDF viewer.
yes, thank you!
xpdf 3.04+git20210103-3 is on its way to the archive, the complete
debdiff follows below.
Florian
diff -Nru xpdf-3.04+git20210103/debian/changelog
xpdf-3.04+git20210103/debian/changelog
--- xpdf-3.04+git20210103/debian/changelog 2021-01-28 15:58:32.0
+0800
+++ xpdf-3.04+git20210103/debian/changelog 2021-03-04 22:41:56.0
+0800
@@ -1,3 +1,15 @@
+xpdf (3.04+git20210103-3) unstable; urgency=medium
+
+ * Fix automatic injection of hardening buildflags
+
+ -- Florian Schlichting Thu, 04 Mar 2021 22:41:56 +0800
+
+xpdf (3.04+git20210103-2) unstable; urgency=medium
+
+ * Fix printing when no psLevel is defined in xpdfrc (closes: #983880)
+
+ -- Florian Schlichting Thu, 04 Mar 2021 14:20:04 +0800
+
xpdf (3.04+git20210103-1) unstable; urgency=medium
* Import new upstream version 3.04+git20210103
diff -Nru xpdf-3.04+git20210103/debian/patches/983880.patch
xpdf-3.04+git20210103/debian/patches/983880.patch
--- xpdf-3.04+git20210103/debian/patches/983880.patch 1970-01-01
08:00:00.0 +0800
+++ xpdf-3.04+git20210103/debian/patches/983880.patch 2021-03-04
14:17:41.0 +0800
@@ -0,0 +1,23 @@
+commit 1b27cc5bb4491aed9d65c9f98704a693e3aabe59
+Author: Adam Sampson
+Date: Wed Mar 3 14:14:52 2021 +
+
+Initialise XPDFParams::psLevel.
+
+This meant that PostScript output didn't work unless you specified
+psLevel explicitly in the config file.
+
+Reported by Frédéric Brière in Debian bug #983880.
+
+diff --git a/xpdf/XPDFParams.cc b/xpdf/XPDFParams.cc
+index 4929bed..f33dd1e 100644
+--- a/xpdf/XPDFParams.cc
b/xpdf/XPDFParams.cc
+@@ -159,6 +159,7 @@ XPDFParams::XPDFParams(const char *cfgFileName) {
+ psImageableURY = psPaperHeight;
+ psCrop = true;
+ psDuplex = false;
++ psLevel = psLevel2;
+ initialZoom = "125";
+ continuousView = false;
+ createDefaultKeyBindings();
diff -Nru xpdf-3.04+git20210103/debian/patches/series
xpdf-3.04+git20210103/debian/patches/series
--- xpdf-3.04+git20210103/debian/patches/series 2021-01-28 14:22:16.0
+0800
+++ xpdf-3.04+git20210103/debian/patches/series 2021-03-04 15:09:53.0
+0800
@@ -1 +1,2 @@
wrapper-options-manpage.patch
+983880.patch
diff -Nru xpdf-3.04+git20210103/debian/rules xpdf-3.04+git20210103/debian/rules
--- xpdf-3.04+git20210103/debian/rules 2021-01-28 14:12:37.0 +0800
+++ xpdf-3.04+git20210103/debian/rules 2021-03-04 15:10:10.0 +0800
@@ -2,7 +2,7 @@
export DEB_BUILD_MAINT_OPTIONS=hardening=+all
-export CPPFLAGS+=-DHAVE_PAPER_H
+export DEB_CPPFLAGS_MAINT_APPEND = -DHAVE_PAPER_H
export LIBS+=-lpaper
%:
Processed: Re: Bug#983071: unblock: xz-utils/5.2.5-1.1
Processing control commands: > tags -1 moreinfo Bug #983071 [release.debian.org] unblock: xz-utils/5.2.5-1.1 Added tag(s) moreinfo. -- 983071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983071: unblock: xz-utils/5.2.5-1.1
Control: tags -1 moreinfo Hi Sebastian On 02-03-2021 21:55, Sebastian Andrzej Siewior wrote: >> Unfortunately we haven't made up our mind yet, but to get some (albeit >> limited) exposure and autopkgtest coverage (via the pseudo-excuses) [2], >> I think your chances for a go are higher if the proposed package is >> available in experimental. > > Just uploaded to experimental. I added the SIGPIPE fix to xzgrep (as > mentioned). The diff for your upload to experimental is awkward as you renamed seemingly all patches, making the review much harder than it needs to be. 19 files changed, 822 insertions(+), 628 deletions(-) Can you please send a debdiff where you undo the renaming (where applicable), such that we get a better understanding of the real changes? What I *think* we're going to do is accept the package in unstable, but have it age a bit in unstable before unblocking (which is going to happen automatically due to the hard freeze). Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#984501: unblock: libqb/2.0.3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libqb Dear Release Team, Upstream made a new minor release of libqb yesterday. Since a new upload wouldn't migrate before the hard freeze with the current 10 day delay, I'm asking for an unblock in advance. 2.0.3 contains a single new feature extending the API and ABI in a backwards-compatible way with a message-id parameter, which isn't the main reason for this request. Included are two doxygen2man fixes, one of them already present in the current 2.0.2-1 package as a Debian patch, and another fixing a groff error in libqb's own manual pages. The really interesting stuff is a memory safety fix in the internal strlcpy() implementation and a more thorough cleanup procedure, which avoids filling up /dev/shm with stale files in certain error and recovery conditions. Locking errors (insufficient locking) are also fixed in the timer code, and the unit tests are extended appropriately. The last fix corrects another unit test but entails no change in behaviour. It would be possible to cherry pick the fix commits into Debian patches leaving out the final one adding the new API, but I'd prefer the cleaner solution of uploading 2.0.3 at this stage. debdiff against the package in testing: diff -Nru libqb-2.0.2/ChangeLog libqb-2.0.3/ChangeLog --- libqb-2.0.2/ChangeLog 2020-12-03 14:07:32.0 +0100 +++ libqb-2.0.3/ChangeLog 2021-03-03 09:34:26.0 +0100 @@ -1,3 +1,57 @@ +2021-03-03 Christine Caulfield + + release: bump library version for 2.0.3 release + +2021-03-01 Aleksei Burlakov + root + + syslog: Add a message-id parameter for messages (#433) + The message-id parameter will enable systemd catalogs. + To enable message-id's the libqb should be configured with the +--enable-systemd-journal option. + +2021-02-08 Chrissie Caulfield + + tests: Fix up resources.test (#435) + resources.test has not checked the right filenames for a while. + Fix this, and also make sure we don't count (but remove) the dlock + test files. + + timers: Add some locking (#436) + Fix several locking issues reported by helgrind + +2021-01-25 Chrissie Caulfield + + ipcc: Have a few goes at tidying up after a dead server (#434) + This is an attempt to make sure that /dev/shm is cleaned up when a + server exits unexpectedly. Normally it's the server's responsibility + to tidy up sockets, but if it crashes or is killed with SIGKILL then + the client (us) makes a reasonable attempt to tidy up the server sockets + we have connected. The extra delay here just gives the server chance to + disappear fully. As a client we can get here pretty quickly but shutting + down a large server may take a little longer even when SIGKILLed. + The 1/100th of a second is an arbitrary delay (of course) but seems to + catch most servers in 2 tries or less. + +2021-01-13 Chrissie Caulfield + + strlcpy: Check for maxlen underflow (#432) + * strlcpy: Check for maxlen underflow + https://github.com/ClusterLabs/libqb/issues/429 + * Always terminate the string if maxlen is > 0 + +2021-01-07 Chrissie Caulfield + + doxygen2man: fix printing of lines starting with '.' (#431) + if a line starts with a '.' (eg the '...' in qbarray.h) then + nroff thinks it's looking for a macro called '..'. + The easiest solution is to add a dummy format at the start of the line + (just adding \ seems not to work). + +2021-01-04 wferi + + doxygen2man: ignore all-whitespace brief descriptions (#430) + 2020-12-03 Christine Caulfield lib: Update library version for 2.0.2 release diff -Nru libqb-2.0.2/configure libqb-2.0.3/configure --- libqb-2.0.2/configure 2020-12-03 14:07:14.0 +0100 +++ libqb-2.0.3/configure 2021-03-03 09:34:07.0 +0100 @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.69 for libqb 2.0.2. +# Generated by GNU Autoconf 2.69 for libqb 2.0.3. # # Report bugs to . # @@ -590,8 +590,8 @@ # Identity of this package. PACKAGE_NAME='libqb' PACKAGE_TARNAME='libqb' -PACKAGE_VERSION='2.0.2' -PACKAGE_STRING='libqb 2.0.2' +PACKAGE_VERSION='2.0.3' +PACKAGE_STRING='libqb 2.0.3' PACKAGE_BUGREPORT='develop...@clusterlabs.org' PACKAGE_URL='' @@ -1426,7 +1426,7 @@ # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat <<_ACEOF -\`configure' configures libqb 2.0.2 to adapt to many kinds of systems. +\`configure' configures libqb 2.0.3 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1496,7 +1496,7 @@ if test -n "$ac_init_help"; then case $ac_init_help in - short |
Bug#983628: marked as done (unblock: geeqie/1:1.6-7)
Your message dated Thu, 4 Mar 2021 11:47:15 +0100
with message-id <223c3f45-87a4-b43b-2cbf-f0ee43c8d...@debian.org>
and subject line Re: Bug#983628: unblock: geeqie/1:1.6-7
has caused the Debian Bug report #983628,
regarding unblock: geeqie/1:1.6-7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package geeqie
This new version fixes a recently discovered regression, in remote
handling in geeqie. It closes #983546 - a regression in the way you
could show an image in an already running geeqie, instead of starting a
new instance of the program. (Without the fix and running remote
geeqie instance it always starts new instances of the program).
Leaf package, small fix, not many alternatives to this particular usage
according to the bug reporter.
(The patch also removes a trailing whitespace in d/changelog, which
itself isn't mentioned in the changelog.)
unblock geeqie/1:1.6-7
-- Andreas Rönnquist
gus...@debian.org
diff -Nru geeqie-1.6/debian/changelog geeqie-1.6/debian/changelog
--- geeqie-1.6/debian/changelog 2021-01-16 15:05:21.0 +0100
+++ geeqie-1.6/debian/changelog 2021-02-27 13:36:57.0 +0100
@@ -1,3 +1,10 @@
+geeqie (1:1.6-7) unstable; urgency=medium
+
+ * Add patch fixing regression --remote option failing
+(Closes: #983546)
+
+ -- Andreas Rönnquist Sat, 27 Feb 2021 13:36:57 +0100
+
geeqie (1:1.6-6) unstable; urgency=medium
* Add patch to fix which image rotatation-keys affect
@@ -13,7 +20,7 @@
geeqie (1:1.6-4) unstable; urgency=medium
- * Add patch to fix segfault on X with clutter
+ * Add patch to fix segfault on X with clutter
(Closes: #979463, #979561, #971403)
-- Andreas Rönnquist Sat, 09 Jan 2021 13:47:51 +0100
diff -Nru geeqie-1.6/debian/patches/0006-Fix-860-871-remote-and-slideshow-on-startup.patch geeqie-1.6/debian/patches/0006-Fix-860-871-remote-and-slideshow-on-startup.patch
--- geeqie-1.6/debian/patches/0006-Fix-860-871-remote-and-slideshow-on-startup.patch 1970-01-01 01:00:00.0 +0100
+++ geeqie-1.6/debian/patches/0006-Fix-860-871-remote-and-slideshow-on-startup.patch 2021-02-27 13:30:35.0 +0100
@@ -0,0 +1,32 @@
+From: Colin Clark
+Date: Sat, 27 Feb 2021 09:12:40 +
+Subject: Fix #860, #871: --remote and --slideshow on startup
+
+https://github.com/BestImageViewer/geeqie/issues/860
+https://github.com/BestImageViewer/geeqie/issues/871
+
+Remote slideshow delay is ignored
+
+--remote --File=IMAGE fails: not displaying image, not using running
+instance, not forking
+---
+ src/main.c | 6 --
+ 1 file changed, 6 deletions(-)
+
+diff --git a/src/main.c b/src/main.c
+index 1356f9a..54c10ea 100644
+--- a/src/main.c
b/src/main.c
+@@ -453,12 +453,6 @@ static void parse_command_line(gint argc, gchar *argv[])
+ }
+ remote_list = g_list_prepend(remote_list, "--new-window");
+ }
+- else if (!remote_server_exists(app_lock))
+- {
+- /* Geeqie started for first time but with --remote option
+- */
+- remote_do = FALSE;
+- }
+ g_free(app_lock);
+ }
+
diff -Nru geeqie-1.6/debian/patches/series geeqie-1.6/debian/patches/series
--- geeqie-1.6/debian/patches/series 2021-01-16 15:04:01.0 +0100
+++ geeqie-1.6/debian/patches/series 2021-02-27 13:30:35.0 +0100
@@ -3,3 +3,4 @@
0003-Fix-832-Geeqie-remembers-desktop.patch
0004-Fix-829-segfault-with-clutter-gtk.patch
0005-Fix-822-The-image-rotation-keys-and-affect-the-wrong.patch
+0006-Fix-860-871-remote-and-slideshow-on-startup.patch
--- End Message ---
--- Begin Message ---
Hi Andreas,
On 27-02-2021 14:49, Andreas Ronnquist wrote:
> Please unblock package geeqie
Assuming that no issues pop up, the package will migrate before the hard
freeze, so nothing actionable for us here.
Closing.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
Bug#984494: unblock: xpdf/3.04+git20210103-2
Control: tags -1 confirmed Hi Florian, On 04-03-2021 08:53, Florian Schlichting wrote: > Please unblock package xpdf Sure, but see below. > As an unrelated issue, I just noticed after uploading -2 that the > -D_FORTIFY_SOURCE=2 hardening buildflag fails to be correctly injected. > This can apparently be fixed by a small change to debian/rules: > > export DEB_BUILD_MAINT_OPTIONS=hardening=+all > > -export CPPFLAGS+=-DHAVE_PAPER_H > +export DEB_CPPFLAGS_MAINT_APPEND = -DHAVE_PAPER_H > > Does the release team consider this a permissible change for the hard > freeze, and should I upload a -3 straight away so that one unblock will > suffice for both fixes? Please go ahead with that. Sounds like something we want for a PDF viewer. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#984494: unblock: xpdf/3.04+git20210103-2
Processing control commands: > tags -1 confirmed Bug #984494 [release.debian.org] unblock: xpdf/3.04+git20210103-2 Added tag(s) confirmed. -- 984494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983908: marked as done (unblock: terminews/1.2.1-1)
Your message dated Thu, 4 Mar 2021 10:04:15 +0100 with message-id <3ca2dac8-1d1f-7fac-3b7e-fc4bd1e43...@debian.org> and subject line Re: Bug#983908: unblock: terminews/1.2.1-1 has caused the Debian Bug report #983908, regarding unblock: terminews/1.2.1-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package terminews. I've been working on packaging Terminews for Debian but miss the soft freeze by a few days. Therefore terminews didn't made it to testing at all. I know testing transition are prohibited as this point as part of our freeze policy, but I wanted to know if we can made an exception as this is a leaf package, with autopkgtest (that run successfully). The package has been for testing for 9days, it therefore only needs one more day & a possible unblock? Thanks in advance, Cheers! -- Aloïs Micard (creekorful) GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2 --- End Message --- --- Begin Message --- Hi Alois, On 03-03-2021 09:09, Alois Micard wrote: > The package has been for testing for 9days, it > therefore only needs one more day & a possible > unblock? If we would be taking such exceptions, there would not be a reason for the soft freeze at all. Sorry, you're too late. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#983340: marked as done (unblock/preapproval: perl/5.32.1-3 with cross build fixes)
Your message dated Thu, 4 Mar 2021 10:01:41 +0100 with message-id <17bf2e9e-b829-1bb8-e996-c9b6da8a1...@debian.org> and subject line Re: Bug#983340: unblock/preapproval: perl/5.32.1-3 with cross build fixes has caused the Debian Bug report #983340, regarding unblock/preapproval: perl/5.32.1-3 with cross build fixes to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: p...@packages.debian.org, Helmut Grohne This is a pre-approval request as perl is part of build-essential and currently frozen. I'd like to fix #983099 by refreshing the cross build support files in the perl source package and updating the documentation a bit. The cross build support files are a workaround for the lack of cross configuration support in perl's Configure system. They need to be refreshed for new upstream versions, and this has not been done for 5.32.1 yet. As Helmut argues in #983099, having a cross buildable perl in stable would be desirable. These updates have been done routinely for several years now. The files have no run time effect, they are only used for cross builds, which are currently failing. The debdiff is unfortunately big; I'm only attaching the diffstat. The full proposed diff is available at https://people.debian.org/~ntyni/perl/perl_5.32.1-3.debdiff Thanks for your work on the release, -- Niko Tyni nt...@debian.org debian/README.source | 12 ++ debian/changelog |8 debian/cross/README | 23 +++ debian/cross/alpha/config.sh.debug.patch | 22 +-- debian/cross/alpha/config.sh.shared.patch | 26 ++--- debian/cross/alpha/config.sh.static | 52 +- debian/cross/amd64/config.sh.debug.patch | 22 +-- debian/cross/amd64/config.sh.shared.patch | 26 ++--- debian/cross/amd64/config.sh.static | 52 +- debian/cross/arm64/config.sh.debug.patch | 22 +-- debian/cross/arm64/config.sh.shared.patch | 26 ++--- debian/cross/arm64/config.sh.static | 52 +- debian/cross/armel/config.sh.debug.patch | 22 +-- debian/cross/armel/config.sh.shared.patch | 26 ++--- debian/cross/armel/config.sh.static | 52 +- debian/cross/armhf/config.sh.debug.patch | 22 +-- debian/cross/armhf/config.sh.shared.patch | 26 ++--- debian/cross/armhf/config.sh.static | 52 +- debian/cross/hppa/config.sh.debug.patch | 22 +-- debian/cross/hppa/config.sh.shared.patch | 26 ++--- debian/cross/hppa/config.sh.static| 52 +- debian/cross/hurd-i386/config.sh.debug.patch | 22 +-- debian/cross/hurd-i386/config.sh.shared.patch | 26 ++--- debian/cross/hurd-i386/config.sh.static | 52 +- debian/cross/i386/config.sh.debug.patch | 22 +-- debian/cross/i386/config.sh.shared.patch | 26 ++--- debian/cross/i386/config.sh.static| 52 +- debian/cross/ia64/config.sh.debug.patch | 22 +-- debian/cross/ia64/config.sh.shared.patch | 26 ++--- debian/cross/ia64/config.sh.static| 52 +- debian/cross/m68k/config.sh.debug.patch | 22 +-- debian/cross/m68k/config.sh.shared.patch | 26 ++--- debian/cross/m68k/config.sh.static| 52 +- debian/cross/mips64el/config.sh.debug.patch | 22 +-- debian/cross/mips64el/config.sh.shared.patch | 26 ++--- debian/cross/mips64el/config.sh.static| 52 +- debian/cross/mipsel/config.sh.debug.patch | 22 +-- debian/cross/mipsel/config.sh.shared.patch| 26 ++--- debian/cross/mipsel/config.sh.static | 52 +- debian/cross/powerpc/config.sh.debug.patch| 22 +-- debian/cross/powerpc/config.sh.shared.patch | 26 ++--- debian/cross/powerpc/config.sh.static | 52 +-
Processed: Re: Bug#983499: unblock: python3-defaults/3.9.2~rc1-1, python3.9/3.9.2~rc1-1
Processing control commands: > tag -1 moreinfo Bug #983499 [release.debian.org] unblock: python3-defaults/3.9.2~rc1-1, python3.9/3.9.2~rc1-1 Ignoring request to alter tags of bug #983499 to the same tags previously set -- 983499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983499: unblock: python3-defaults/3.9.2~rc1-1, python3.9/3.9.2~rc1-1
Control: tag -1 moreinfo Hi Stefano, On 25-02-2021 07:17, Stefano Rivera wrote: > Please unblock package python3-defaults and python3.9 The python3-defaults package is currently blocked by autopkgtest regressions. As usual, I suspect these are transient failures (either infrastructure or flaky tests). If your going to inspect, flaky tests are RC and can be filed, all failures are retried after a day. Please remove the moreinfo bug if there's something that needs our attention. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#982480: marked as done (unblock: manpages-l10n/4.9.2-1)
Your message dated Thu, 4 Mar 2021 09:53:44 +0100 with message-id <07a81369-92b6-ac42-ceac-6e4a9cfeb...@debian.org> and subject line Re: Bug#982480: unblock: manpages-l10n/4.9.2-1 has caused the Debian Bug report #982480, regarding unblock: manpages-l10n/4.9.2-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: Mario Blättermann , Craig Small Please unblock package manpages-l10n This version will be upload soon and I need your advise. Please note that 4.9.2-1 has (as of this writing) not yet hit the archive and will go through NEW unfortunately. I give a brief background for the unfortunate situation for this package in [ Other info ] below. [ Reason ] manpages-l10n contains translations of manpages contained in Debian into many languages. This is achieved by downloading the manpages from Debian Unstable, converting them into po files, translating them and if the translation is 80% or more complete, including it in the next release. To have current translations for bullsey, upstream agreed to provide a release close to the Freeze date. This release has happend last weekend. "Unfortunately" afterwards psmics and procps decided to ship translated man pages themeselves (which in itself is good), which required them to be excluded by manpages-l10n. To cater for this, upstream has made another release today (4.9.2) which I will package in a moment and and ask my current sponsor (Craig) for upload. Since we ship new languages (i.e. packages), manpages-l10n will need to get through NEW and will not be able to reach the freeze date by 2021-02-12. The rationale for this is in [ Other info ]. Now to the question: Due to the late changes, the upstream version now contains man pages shipped in manpages-es-extra. Some time ago, we requested this package to be removed (#980885), as we believe, shipping this package is a disservice to Debian users. However, the maintainer has not responded. 4.9.2-1 will not ship the files, so no conflict is present, but ideally manpages-es-extra would be removed and the much (!) more current files would be shipped by manpages-es (from manpages-l10n). If you feel this is possible, I would prepare another upload for this. [ Impact ] a) Some users will get old translations, i.e. from October, b) some (for ES, IT and MK) will get no current translated man pages at all. [ Tests ] There is no code, but I rebuild the entire set of man pages daily (also during the build) and look for possible build errors. [ Risks ] This is a leave and pure documentation package. Users can always switch to the english man page if for whatever reason there should be a problem with the translation. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [ ] attach debdiff against the package in testing If an debdiff is really required, please tell me the version you would like to have it against. [ Other info ] Toddy, the original (and main) maintainer is caught in real life, so he transferred me (a Debian maintainer) the appropriate rights to upload manpages-l10n. Howerver, as DM I'm not allowed to get packages through NEW (needed to support ES, IT and MK) and hence I spend the last weeks looking for a DD who could sponser this upload. Fortunately, Craig was so kind to fill in this role. Once NEW is passed I'm available and capable of performing subsequent uploads (if necessary), i.e. for fixing further bugs. (I'm a DM for ~ 10 years) If you need any further information regarding the unblock request, I'm available and usually respond within 24 hours latest. unblock manpages-l10n/4.9.2-1 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc
