NEW changes in stable-new
Processing changes file: exim4_4.92-8+deb10u5_mipsel-buildd.changes ACCEPT
Processed: Re: Bug#985606: unblock: apticron/1.2.4
Processing control commands: > tags -1 moreinfo Bug #985606 [release.debian.org] unblock: apticron/1.2.4 Added tag(s) moreinfo. -- 985606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985606: unblock: apticron/1.2.4
Control: tags -1 moreinfo Hi Tiago On 2021-03-20 12:28:21 -0400, Tiago Bortoletto Vaz wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > X-Debbugs-Cc: ti...@debian.org > > Please unblock package apticron. The only change is using `mktemp` instead of > deprecated `tempfile` command in two lines of apticron's code. > > [ Reason ] > Depecration warning produces an email every time apticron runs, see #962921 > > [ Impact ] > Daily useless emails > > [ Tests ] > Manual test > > [ Risks ] > I can't see any risk > > [ Checklist ] > [ X ] all changes are documented in the d/changelog > [ X ] I reviewed all changes and I approve them > [ X ] attach debdiff against the package in testing > > [ Other info ] > The reporter has kindly contacted the release team before proposing the patch, > according to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962921#17 > > unblock apticron/1.2.4 Beside the missing debdiff, apticfron will need a source only upload: apticron (1.2.3+nmu1 to 1.2.4) ... Not built on buildd: arch all binaries uploaded by tiago, a new source-only upload is needed to allow migration Cheers > > Bests, > > -- > Tiago > -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: Re: Bug#985606: unblock: apticron/1.2.4
Processing control commands: > tags -1 + confirmed Bug #985606 [release.debian.org] unblock: apticron/1.2.4 Added tag(s) confirmed. -- 985606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985606: unblock: apticron/1.2.4
Control: tags -1 + confirmed On 2021-03-21 11:27:49 +0100, Sebastian Ramacher wrote: > Control: tags -1 moreinfo > > Hi Tiago > > On 2021-03-20 12:28:21 -0400, Tiago Bortoletto Vaz wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: unblock > > X-Debbugs-Cc: ti...@debian.org > > > > Please unblock package apticron. The only change is using `mktemp` instead > > of > > deprecated `tempfile` command in two lines of apticron's code. > > > > [ Reason ] > > Depecration warning produces an email every time apticron runs, see #962921 > > > > [ Impact ] > > Daily useless emails > > > > [ Tests ] > > Manual test > > > > [ Risks ] > > I can't see any risk > > > > [ Checklist ] > > [ X ] all changes are documented in the d/changelog > > [ X ] I reviewed all changes and I approve them > > [ X ] attach debdiff against the package in testing > > > > [ Other info ] > > The reporter has kindly contacted the release team before proposing the > > patch, > > according to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962921#17 > > > > unblock apticron/1.2.4 > > Beside the missing debdiff, apticfron will need a source only upload: Sorry, just found the debdiff in your second message to the bug report. Cheers > > apticron (1.2.3+nmu1 to 1.2.4) > ... > Not built on buildd: arch all binaries uploaded by tiago, a new > source-only upload is needed to allow migration > > Cheers > > > > > Bests, > > > > -- > > Tiago > > > > -- > Sebastian Ramacher -- Sebastian Ramacher signature.asc Description: PGP signature
Re: Bug#985556: flatpak/1.2.5-0+deb10u4 FTBFS on i386
On 20.03.21 13:32, Simon McVittie wrote: > On Sat, 20 Mar 2021 at 09:16:45 +0100, Salvatore Bonaccorso wrote: >> On Sat, Mar 20, 2021 at 12:12:39AM +, Simon McVittie wrote: >>> Could x86-conova-01.debian.org be an IPv6-only buildd? > ... >>> Or, if not that, could it be the case that this buildd is firewalled or >>> otherwise restricted such that connections from the build to a test >>> server listening on an arbitrary high port number on the loopback >>> interface will fail? >> >> JFTR, this might indeed be the case. I gave it back a couple of times >> and building on x86-conova-01.debian.org failed. The last one got >> picked on buildd-x86-grnet-01 which now seems to have built. > > If we now have buildds that are more restrictive or limited than > the buildds that were used at the time stable was frozen, then > it would probably be good if it was possible to arrange for only > testing/unstable/experimental packages to be built on those buildds, > with stable updates built on buildds that more closely resemble the ones > they were originally tested on - otherwise we'll get random build > regressions. The buildd is IPv6-only. I'm somewhat torn given that we have enough buildd coverage that a give-back would likely solve the problem. At the same time you can't avoid a particular buildd either. So I concur, as much as it hurts me in this day and age, that we should at least temporarily disable stable/oldstable builds on the IPv6-only buildds. I have commented out stretch and buster (and their corresponding security and backports suites) on x86-conova-01 for now. I'll definitely leave bullseye on, though. Not sure if there's another IPv6-only buildd lingering around. Kind regards and thanks Philipp Kern
Bug#985646: unblock: odin/2.0.4-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package odin
[ Reason ]
odin/2.0.4-1 is affected by two RC critical bugs in Bullseye,
#985508, and #985577, which are fixed by odin/2.0.4-3 in Sid.
[ Impact ]
Impact of removal of odin in Bullseye would potentially affect
98 installations per popcon reports. This is an otherwise leaf
package, and wouldn't affect other elements from the archive.
[ Tests ]
* Built on all release architecture by buildd
* Went through Salsa CI, only reprotest is failing
* I ran piuparts --fail-on-broken-symlinks --no-upgrade-test
to check the package was not affected by #985508 anymore.
* I manually tested running most programs:
- I played around with a couple of GUI applications to make
sure they were not affected by #985577 anymore: no crashes
observed, but since I don't do magnetic resonance imaging
in my daily activities, I don't know how much my tests
covered regular use cases;
- I tested most command line applications to make sure they
were not affected by #985577; althought tests didn't go
way further than --help and --version, these were
initially sufficient to trigger the bug.
[ Risks ]
Changes have been kept as minimum as I could to fix bugs. This
is a leaf package, so shouldn't affect other Debian packages.
Furthermore, affected libraries are private to the namespace of
the odin progams, so shouldn't interfere with other packages run
time.
[ Checklist ]
[*] all changes are documented in the d/changelog
[*] I reviewed all changes and I approve them
[*] attach debdiff against the package in testing
[ Other info ]
reprotest failure is due to build flags with file path embedded
in the header file usr/include/tjutils/config.h. I have some
doubts on the cross-buildability of the package given the use of
DEB_HOST_MULTIARCH where I naively expect DEB_BUILD_MULTIARCH.
But I understand these are out of scope items in hard freeze.
unblock odin/2.0.4-3
Have a nice day, :)
--
Étienne Mollier
Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
Sent from /dev/pts/1, please excuse my verbosity.
diff -Nru odin-2.0.4/debian/changelog odin-2.0.4/debian/changelog
--- odin-2.0.4/debian/changelog 2020-12-15 21:11:56.0 +0100
+++ odin-2.0.4/debian/changelog 2021-03-20 13:49:44.0 +0100
@@ -1,3 +1,22 @@
+odin (2.0.4-3) unstable; urgency=medium
+
+ * Team upload.
+ * Configure build to target the libdir /usr/lib/$(DEB_HOST_MULTIARCH)/odin,
+and adjust install scripts to the new staging location: allows executables
+provided by packages mitools and odin to find their private shared objects.
+Closes: #985577
+
+ -- Étienne Mollier Sat, 20 Mar 2021 13:49:44
+0100
+
+odin (2.0.4-2) unstable; urgency=medium
+
+ * Team upload.
+ * Added mitools and qtchooser as dependency of libodin-dev; fixes broken
+symbolic links on libodin-dev installation.
+Closes: #985508
+
+ -- Étienne Mollier Fri, 19 Mar 2021 20:02:31
+0100
+
odin (2.0.4-1) unstable; urgency=medium
* Team upload.
diff -Nru odin-2.0.4/debian/control odin-2.0.4/debian/control
--- odin-2.0.4/debian/control 2020-12-15 21:11:56.0 +0100
+++ odin-2.0.4/debian/control 2021-03-19 19:54:39.0 +0100
@@ -65,6 +65,8 @@
Section: libdevel
Depends: ${shlibs:Depends},
${misc:Depends},
+ mitools,
+ qtchooser,
sensible-utils
Description: static libraries and header for ODIN sequences
This package provides static libraries and headers of the ODIN libraries
diff -Nru odin-2.0.4/debian/libodin-dev.install
odin-2.0.4/debian/libodin-dev.install
--- odin-2.0.4/debian/libodin-dev.install 2020-12-15 21:11:56.0
+0100
+++ odin-2.0.4/debian/libodin-dev.install 2021-03-20 13:09:27.0
+0100
@@ -1,4 +1,4 @@
#! /usr/bin/dh-exec
-usr/lib/odin/*.a usr/lib/${DEB_HOST_MULTIARCH}/odin
-usr/lib/odin/*[a-z].so usr/lib/${DEB_HOST_MULTIARCH}/odin
+usr/lib/${DEB_HOST_MULTIARCH}/odin/*.a usr/lib/${DEB_HOST_MULTIARCH}/odin
+usr/lib/${DEB_HOST_MULTIARCH}/odin/*[a-z].so
usr/lib/${DEB_HOST_MULTIARCH}/odin
usr/include
diff -Nru odin-2.0.4/debian/mitools.install odin-2.0.4/debian/mitools.install
--- odin-2.0.4/debian/mitools.install 2020-12-15 21:11:56.0 +0100
+++ odin-2.0.4/debian/mitools.install 2021-03-20 13:12:03.0 +0100
@@ -1,3 +1,3 @@
#! /usr/bin/dh-exec
-usr/lib/odin/*-*.sousr/lib/${DEB_HOST_MULTIARCH}/odin
+usr/lib/${DEB_HOST_MULTIARCH}/odin/*-*.so
usr/lib/${DEB_HOST_MULTIARCH}/odin
usr/bin/mi*usr/bin
diff -Nru odin-2.0.4/debian/rules odin-2.0.4/debian/rules
--- odin-2.0.4/debian/rules 2020-12-15 21:11:56.0 +0100
+++ odin-2.0.4/debian/rules 2021-03-20 13:29:05.0 +0100
@@ -14,7 +14,7 @@
override_dh_auto_configure:
dh_auto_configure -- \
---libdir="/usr/lib/odin" \
+--libdir="/usr/
Re: Bug#985556: flatpak/1.2.5-0+deb10u4 FTBFS on i386
Control: retitle -1 flatpak/1.2.5-0+deb10u4 FTBFS on IPv6-only buildds Control: reassign -1 glib2.0 2.50.0-1 Control: affects -1 + flatpak Control: severity -1 important Control: close -1 2.63.1-1 On Sun, 21 Mar 2021 at 12:15:15 +0100, Philipp Kern wrote: > I have commented out stretch and buster (and their corresponding > security and backports suites) on x86-conova-01 for now. I'll definitely > leave bullseye on, though. Not sure if there's another IPv6-only buildd > lingering around. Thanks, I think this is appropriate. I'm reassigning the bug to glib2.0, downgrading its severity and resolving it as fixed in bullseye. It's effectively the same thing as #948834. Justification for downgrade: it's a FTBFS, but it only affects (old)stable, only affects certain builder configurations (IPv6-only machines and some pbuilder configurations), and with Philipp's workaround it does not prevent us from doing security and stable updates. If anyone disagrees with the downgrade, we could backport the "let localhost be localhost" change into buster's glib2.0, but for a stable release that will soon become oldstable I'd prefer not to have the regression risk of that behaviour change. smcv
Bug#982669: portaudio19 19.6.0-1+deb10u1 flagged for acceptance
package release.debian.org tags 982669 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: portaudio19 Version: 19.6.0-1+deb10u1 Explanation:
Bug#985624: lirc 0.10.1-6.3~deb10u1 flagged for acceptance
package release.debian.org
tags 985624 = buster pending
thanks
Hi,
The upload referenced by this bug report has been flagged for acceptance into
the proposed-updates queue for Debian buster.
Thanks for your contribution!
Upload details
==
Package: lirc
Version: 0.10.1-6.3~deb10u1
Explanation: normalize embedded ${DEB_HOST_MULTIARCH} value in
/etc/lirc/lirc_options.conf to find unmodified configuration files on all
architectures; recommend gir1.2-vte-2.91 instead of non-existant gir1.2-vte
Processed: lirc 0.10.1-6.3~deb10u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 985624 = buster pending Bug #985624 [release.debian.org] buster-pu: package lirc/0.10.1-6.3~deb10u1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 985624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: portaudio19 19.6.0-1+deb10u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 982669 = buster pending Bug #982669 [release.debian.org] buster-pu: package portaudio19/19.6.0-1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 982669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in stable-new
Processing changes file: linux-signed-arm64_4.19.181+1_source.changes ACCEPT Processing changes file: linux-signed-i386_4.19.181+1_source.changes ACCEPT Processing changes file: lirc_0.10.1-6.3~deb10u1_source.changes ACCEPT Processing changes file: portaudio19_19.6.0-1+deb10u1_source.changes ACCEPT
Bug#984925: marked as done (pre-approval: updating python-networkmanager to 2.2 (bugfix release) in bullseye)
Your message dated Sun, 21 Mar 2021 14:10:04 +0100
with message-id <20210321131004.b35qhiaw6tfya...@fatal.se>
and subject line Re: Bug#984925: pre-approval: updating python-networkmanager
to 2.2 (bugfix release) in bullseye
has caused the Debian Bug report #984925,
regarding pre-approval: updating python-networkmanager to 2.2 (bugfix release)
in bullseye
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.)
--
984925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Hello release-team,
I'm asking for a pre-approval for updating python-networkmanager
to a new upstream release in bullseye. In my own opinion it
seems new version basically seems to consist 100% of crasher fixes
so trying to backport targeted fixes seems pointless. (In other words,
newly added constants for new features in bullseye version of NM to
avoid crashing when getting that kind of data from NM, plus fix for
#934743, plus whatever the 'address-data' + 'route-data' settings stuff
does).
In my opinion the current state is pretty useless since simple
operations like enumerating devices causes a crash, but at the same time
the ONE and only reverse dependency in bullseye (comitup) looks to be
actively maintained so presumably that one atleast works (OTOH with a
popcon of around 8 I don't have high confidence that users would have
reported a bug if it didn't).
If you think this (is ok to upload to unstable and) has a chance to get
unblocked, I'll get right on it (with the first step being filing the
bug report on python3-networkmanager with RC severity).
# git diff 2.1..2.2 | filterdiff -i '*.py' -x '*/.github/*' -x '*/ci/*' -x
'*/setup.py' -x '*/docs/*'
diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml
new file mode 100644
index 000..7a1361e
diff --git a/.github/workflows/python-publish.yml
b/.github/workflows/python-publish.yml
new file mode 100644
index 000..4e1ef42
diff --git a/NetworkManager.py b/NetworkManager.py
index 3d137fe..e66beba 100644
--- a/NetworkManager.py
+++ b/NetworkManager.py
@@ -1,7 +1,7 @@
# NetworkManager - a library to make interacting with the NetworkManager daemon
# easier.
#
-# (C)2011-2017 Dennis Kaarsemaker
+# (C)2011-2021 Dennis Kaarsemaker
# License: zlib
import copy
@@ -258,7 +258,7 @@ class NMDbusInterface(object):
@property
def proxy(self):
if not self._proxy:
-self._proxy = dbus.SystemBus().get_object(self.dbus_service,
self.object_path)
+self._proxy = dbus.SystemBus().get_object(self.dbus_service,
self.object_path, follow_name_owner_changes=True)
self._proxy.created = time.time()
elif self._proxy.created < self.last_disconnect:
if self.is_transient:
@@ -389,7 +389,12 @@ def device_class(typ):
NM_DEVICE_TYPE_PPP: PPP,
NM_DEVICE_TYPE_OVS_INTERFACE: OvsIf,
NM_DEVICE_TYPE_OVS_PORT: OvsPort,
-NM_DEVICE_TYPE_OVS_BRIDGE: OvsBridge
+NM_DEVICE_TYPE_OVS_BRIDGE: OvsBridge,
+NM_DEVICE_TYPE_WPAN: Wpan,
+NM_DEVICE_TYPE_6LOWPAN: SixLoWpan,
+NM_DEVICE_TYPE_WIREGUARD: WireGuard,
+NM_DEVICE_TYPE_VRF: Vrf,
+NM_DEVICE_TYPE_WIFI_P2P: WifiP2p,
}[typ]
class Adsl(Device): pass
@@ -416,6 +421,11 @@ class PPP(Device): pass
class OvsIf(Device): pass
class OvsPort(Device): pass
class OvsBridge(Device): pass
+class Wpan(Device): pass
+class SixLoWpan(Device): pass
+class WireGuard(Device): pass
+class WifiP2p(Device): pass
+class Vrf(Device): pass
class NSP(TransientNMDbusInterface):
interface_names = ['org.freedesktop.NetworkManager.Wimax.NSP']
@@ -504,6 +514,12 @@ class fixups(object):
settings['ipv4']['address-data'] = dbus.Array(
settings['ipv4']['address-data'],
signature=dbus.Signature('a{sv}'))
+if 'route-data' in settings['ipv4']:
+for item in settings['ipv4']['route-data']:
+item['prefix'] = dbus.UInt32(item['prefix'])
+settings['ipv4']['route-data'] = dbus.Array(
+settings['ipv4']['route-data'],
+signature=dbus.Signature('a{sv}'))
if 'addresses' in settings['ipv4']:
settings['ipv4']['addresses'] =
[fixups.addrconf_to_dbus(addr,socket.AF_INET) for addr in
settings['ipv4']['addresses']]
if 'routes' in settings['ipv4']:
@@ -511,6 +527,18
Bug#985589: unblock: jsonnet/0.17.0+ds-2
Control: tags -1 + confirmed moreinfo
On 2021-03-20 13:49:44 +, M. Zhou wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
>
>
> Please unblock package jsonnet
>
> [ Reason ]
>
> I missed the lib package in the Depends: field of its -dev package,
> resulting in dangling symlinks during anbe's tests. Not yet uploaded.
Looks good. Please remove the moreinfo tag once it's available in
unstable.
Cheers
>
> [ Checklist ]
> [x] all changes are documented in the d/changelog
> [x] I reviewed all changes and I approve them
> [x] attach debdiff against the package in testing
>
> unblock jsonnet/0.17.0+ds-2
>
>
>
> --- debdiff ---
>
> diff -Nru jsonnet-0.17.0+ds/debian/changelog jsonnet-
> 0.17.0+ds/debian/changelog
> --- jsonnet-0.17.0+ds/debian/changelog 2020-12-01 11:12:06.0
> +0800
> +++ jsonnet-0.17.0+ds/debian/changelog 2021-03-20 21:44:30.0
> +0800
> @@ -1,3 +1,9 @@
> +jsonnet (0.17.0+ds-2) UNRELEASED; urgency=medium
> +
> + * Fix broken symlinks in libjsonnet-dev due to missing deps (Closes:
> #985511)
> +
> + -- Mo Zhou Sat, 20 Mar 2021 21:44:30 +0800
> +
> jsonnet (0.17.0+ds-1) unstable; urgency=medium
>
>* New upstream version 0.17.0+ds
> diff -Nru jsonnet-0.17.0+ds/debian/control jsonnet-
> 0.17.0+ds/debian/control
> --- jsonnet-0.17.0+ds/debian/control2020-12-01 11:12:06.0
> +0800
> +++ jsonnet-0.17.0+ds/debian/control2021-03-20 21:27:53.0
> +0800
> @@ -64,7 +64,7 @@
> Package: libjsonnet-dev
> Section: libdevel
> Architecture: any
> -Depends: ${misc:Depends},
> +Depends: ${misc:Depends}, libjsonnet0 (= ${binary:Version})
> Description: data templating language (devel)
> A data templating language for app and tool developers
> .
>
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Processed: Re: Bug#985589: unblock: jsonnet/0.17.0+ds-2
Processing control commands: > tags -1 + confirmed moreinfo Bug #985589 [release.debian.org] unblock: jsonnet/0.17.0+ds-2 Added tag(s) moreinfo and confirmed. -- 985589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985605: marked as done (unblock: texlive-lang/2020.20210202-2)
Your message dated Sun, 21 Mar 2021 13:28:57 + with message-id and subject line unblock texlive-lang has caused the Debian Bug report #985605, regarding unblock: texlive-lang/2020.20210202-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.) -- 985605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985605 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: debian-tex-ma...@lists.debian.org Please unblock package texlive-lang The package texlive-lang-greek provides fonts to the TeX world from other packages by creating symbolic links into the TeX directory structure. During the last few months a few packages corrected their font locations: Opentype fonts now sit in /usr/share/fonts/opentype instead of /u/s/fonts/truetype. Hence our package contained broken symlinks, which was notified very late. We got RC bug #985504 for this. The latest upload of texlive-lang corrects these sym links. [ Reason ] Provide more fonts to TeX users. [ Impact ] A few fonts available in Debian will be not available to TeX users. [ Tests ] Tests were run using piuparts, which report no broken symlinks any more. [ Risks ] No risc, as no code was changed. [ Checklist ] [X] all changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in testing [ Other info ] (Anything else the release team should know.) unblock texlive-lang/2020.20210202-2 -- sigmentation fault diff -Nru texlive-lang-2020.20210202/debian/changelog texlive-lang-2020.20210202/debian/changelog --- texlive-lang-2020.20210202/debian/changelog 2021-02-02 05:04:30.0 +0100 +++ texlive-lang-2020.20210202/debian/changelog 2021-03-19 20:49:27.0 +0100 @@ -1,3 +1,9 @@ +texlive-lang (2020.20210202-2) unstable; urgency=medium + + * Fix sym link to GFSPorson.otf (Closess: #985504). + + -- Hilmar Preusse Fri, 19 Mar 2021 20:49:27 +0100 + texlive-lang (2020.20210202-1) unstable; urgency=medium * New upstream checkout. diff -Nru texlive-lang-2020.20210202/debian/texlive-lang-greek.links.dist texlive-lang-2020.20210202/debian/texlive-lang-greek.links.dist --- texlive-lang-2020.20210202/debian/texlive-lang-greek.links.dist 2012-09-04 03:01:46.0 +0200 +++ texlive-lang-2020.20210202/debian/texlive-lang-greek.links.dist 2021-03-19 20:46:21.0 +0100 @@ -1,2 +1,2 @@ usr/share/fonts/truetype/baskerville/GFSBaskerville.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsbaskerville/GFSBaskerville.otf -usr/share/fonts/truetype/porson/GFSPorson.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsporson/GFSPorson.otf +usr/share/fonts/opentype/porson/GFSPorson.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsporson/GFSPorson.otf signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Bug#985595: marked as done (unblock: reiser4progs/1.2.1-3)
Your message dated Sun, 21 Mar 2021 13:30:37 +
with message-id
and subject line unblock reiser4progs
has caused the Debian Bug report #985595,
regarding unblock: reiser4progs/1.2.1-3
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.)
--
985595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985595
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 reiser4progs
[ Reason ]
1.2.1-3 added 2 patches to make sure that the created reiser4
filesystem will have a correct UUID.
See also Debian bug #985586
[ Impact ]
There's a small chance that a reiser4 fs will end up without an UUID.
[ Tests ]
Small test script provided in the Debian bug #985586
[ Risks ]
Small code changes. Leaf package which isn't used much.
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in testing
unblock reiser4progs/1.2.1-3
diff -Nru reiser4progs-1.2.1/debian/changelog
reiser4progs-1.2.1/debian/changelog
--- reiser4progs-1.2.1/debian/changelog 2020-07-24 08:21:25.0 +0200
+++ reiser4progs-1.2.1/debian/changelog 2021-03-20 15:02:23.0 +0100
@@ -1,9 +1,17 @@
-reiser4progs (1.2.1-2) UNRELEASED; urgency=medium
+reiser4progs (1.2.1-3) unstable; urgency=medium
+
+ * Add patches to fix creation of filesystems without an UUID. Thanks
+Mike Fleetwood for the report + patches! (Closes: #985586)
+
+ -- Felix Zielcke Sat, 20 Mar 2021 15:02:23 +0100
+
+reiser4progs (1.2.1-2) unstable; urgency=medium
* Build with libedit instead of orphaned libreadline5. Thanks Bastian
Germann for the patch! (Closes: #966149)
+ * Bump Standards-Version to 4.5.0.
- -- Felix Zielcke Fri, 24 Jul 2020 08:21:25 +0200
+ -- Felix Zielcke Fri, 24 Jul 2020 08:25:47 +0200
reiser4progs (1.2.1-1) unstable; urgency=medium
diff -Nru reiser4progs-1.2.1/debian/control reiser4progs-1.2.1/debian/control
--- reiser4progs-1.2.1/debian/control 2020-07-24 08:17:36.0 +0200
+++ reiser4progs-1.2.1/debian/control 2020-07-24 08:25:43.0 +0200
@@ -7,7 +7,7 @@
libaal-dev (>= 1.0.7),
libedit-dev,
uuid-dev
-Standards-Version: 4.4.0
+Standards-Version: 4.5.0
Homepage: https://reiser4.wiki.kernel.org
Package: reiser4progs
diff -Nru reiser4progs-1.2.1/debian/patches/fix_null_uuid.patch
reiser4progs-1.2.1/debian/patches/fix_null_uuid.patch
--- reiser4progs-1.2.1/debian/patches/fix_null_uuid.patch 1970-01-01
01:00:00.0 +0100
+++ reiser4progs-1.2.1/debian/patches/fix_null_uuid.patch 2021-03-20
14:58:26.0 +0100
@@ -0,0 +1,52 @@
+Author: Mike Fleetwood
+Date: Mon Mar 15 21:09:17 2021 +
+Subject: Stop occasionally making file systems with null UUIDs
+
+mkfs.reiser4 was using strncpy() to copy a binary UUID into the
+in-memory copy of the superblock. So if there was a zero byte in the
+UUID, then from that point to the end was set to all zeros. If the
+first byte was zero, a 1 in 256 chance, then the whole UUID was set to
+zero generating a null UUID for the file system. Fix this.
+
+Test case:
+truncate -s 256M test.img
+i=0
+while :
+do
+mkfs.reiser4 --force --yes --label '' test.img
+line=`debugfs.reiser4 test.img 2> /dev/null | egrep '^uuid:'`
+((i++))
+echo "[$i] $line"
+echo "$line" | grep -q '' && break
+done
+
+Output fragment:
+[1] uuid: 17073919-e41d-4892-9b22-4294d1544c4a
+[2] uuid: af2821de-ea85-4f20-9621-4fbd128b3fb8
+[3] uuid: c0fb805b-e224-4695-a504-d87460d158ae
+...
+[34] uuid: b747540d-5280-4e0f-bae2-9222
+[35] uuid: d604794d-097f-4810-bbb3-01a1518f3ef1
+[36] uuid: 9634100c-1f98-42b3-a684-c9df77ab54e2
+[37] uuid:
+
+Signed-off-by: Mike Fleetwood
+
+Origin: upstream,
https://github.com/edward6/reiser4progs/commit/44cc024f398f60adef1519426d65f3f081ee826a
+Bug-Debian: https://bugs.debian.org/985586
+
+diff --git a/libreiser4/master.c b/libreiser4/master.c
+index 649434d96..825fd38d1 100644
+--- a/libreiser4/master.c
b/libreiser4/master.c
+@@ -295,8 +295,8 @@ void reiser4_master_set_uuid(reiser4_master_t *master,
+ sizeof(SUPER(master)->ms_uuid));
+
+ if (uuid) {
+- aal_strncpy(SUPER(master)->ms_uuid, uuid,
+- sizeof(S
Bug#985573: marked as done (unblock: texlive-extra/2020.20210202-3)
Your message dated Sun, 21 Mar 2021 13:39:06 + with message-id and subject line unblock texlive-extra has caused the Debian Bug report #985573, regarding unblock: texlive-extra/2020.20210202-3 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.) -- 985573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985573 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: debian-tex-ma...@lists.debian.org Please unblock package texlive-extra The package texlive-fonts-extra-links provides fonts to the TeX world from other packages by creating symbolic links into the TeX directory structure. During the last few months a few packages corrected their font locations: Opentype fonts now sit in /usr/share/fonts/opentype instead of /u/s/fonts/truetype. Hence our package contained broken symlinks, which was notified very late. We got RC bug #985437 for this. The latest upload of texlive-extra corrects these sym links. [ Reason ] Provide more fonts to TeX users. [ Impact ] A few fonts available in Debian will be not available to TeX users. [ Tests ] Tests were run using piuparts, which report no broken symlinks any more. [ Risks ] No risc, as no code was changed. [ Checklist ] [X] all changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in testing [ Other info ] (Anything else the release team should know.) unblock texlive-extra/2020.20210202-3 -- sigmentation fault diff -Nru texlive-extra-2020.20210202/debian/changelog texlive-extra-2020.20210202/debian/changelog --- texlive-extra-2020.20210202/debian/changelog 2021-02-02 05:04:20.0 +0100 +++ texlive-extra-2020.20210202/debian/changelog 2021-03-19 17:14:05.0 +0100 @@ -1,3 +1,17 @@ +texlive-extra (2020.20210202-3) unstable; urgency=medium + + * Correct location of GentiumPlusCompact TTF files. It is +/usr/share/fonts/truetype/gentiumplus-compact. ;-( + + -- Hilmar Preusse Fri, 19 Mar 2021 17:14:05 +0100 + +texlive-extra (2020.20210202-2) unstable; urgency=medium + + * Some packages install their OTF fonts now in /u/s/fonts/opentype: +fix broken symlinks (Closes: #985437). + + -- Hilmar Preusse Thu, 18 Mar 2021 23:20:06 +0100 + texlive-extra (2020.20210202-1) unstable; urgency=medium * New upstream checkout. diff -Nru texlive-extra-2020.20210202/debian/texlive-fonts-extra-links.links.dist texlive-extra-2020.20210202/debian/texlive-fonts-extra-links.links.dist --- texlive-extra-2020.20210202/debian/texlive-fonts-extra-links.links.dist 2020-08-04 07:50:26.0 +0200 +++ texlive-extra-2020.20210202/debian/texlive-fonts-extra-links.links.dist 2021-03-19 16:25:11.0 +0100 @@ -1,19 +1,19 @@ -usr/share/fonts/truetype/asana-math/Asana-Math.otf usr/share/texlive/texmf-dist/fonts/opentype/public/Asana-Math/Asana-Math.otf -usr/share/fonts/truetype/artemisia/GFSArtemisia.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsartemisia/GFSArtemisia.otf -usr/share/fonts/truetype/artemisia/GFSArtemisiaBold.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsartemisia/GFSArtemisiaBold.otf -usr/share/fonts/truetype/artemisia/GFSArtemisiaBoldIt.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsartemisia/GFSArtemisiaBoldIt.otf -usr/share/fonts/truetype/artemisia/GFSArtemisiaIt.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsartemisia/GFSArtemisiaIt.otf -usr/share/fonts/truetype/complutum/GFSPolyglot.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfscomplutum/GFSPolyglot.otf -usr/share/fonts/truetype/didot/GFSDidot.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsdidot/GFSDidot.otf -usr/share/fonts/truetype/didot/GFSDidotBold.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsdidot/GFSDidotBold.otf -usr/share/fonts/truetype/didot/GFSDidotBoldItalic.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsdidot/GFSDidotBoldItalic.otf -usr/share/fonts/truetype/didot/GFSDidotItalic.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsdidot/GFSDidotItalic.otf -usr/share/fonts/truetype/olga/GFSOlga.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsdidot/GFSOlga.otf -usr/share/fonts/truetype/neohellenic/GFSNeohellenic.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsneohellenic/GFSNeohellenic.otf -usr/share/fonts/truetype/neohellenic/GFSNeohellenicBold.otf usr/share/texlive/texmf-dist/fonts/opentype/public/gfsneohellenic/GFSNeohellenicBold.otf -usr/share/fon
Bug#985560: marked as done (unblock: wp2latex/3.94+ds-2)
Your message dated Sun, 21 Mar 2021 13:53:43 +
with message-id
and subject line unblock wp2latex
has caused the Debian Bug report #985560,
regarding unblock: wp2latex/3.94+ds-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.)
--
985560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985560
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 wp2latex
(Please provide enough (but not too much) information to help
the release team to judge the request efficiently. E.g. by
filling in the sections below.)
[ Reason ]
The new Debian version contains a small fix to fix EPS file generation for a
few corner cases.
[ Impact ]
If the new version is not unblocked, some EPS files (generated by wp2latex)
will be syntactically incorrect and will not be processed by ghostscript.
This will make some converted documents unusable.
[ Tests ]
Upstream provided a test file, which can't be converted into valid EPS code
using the old version, but works fine for the new version.
[ Risks ]
Rather trivial code change to prefix curly braces properly.
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in testing
[ Other info ]
(Anything else the release team should know.)
unblock wp2latex/3.94+ds-2
--
sigmentation fault
diff -Nru wp2latex-3.94+ds/debian/changelog wp2latex-3.94+ds/debian/changelog
--- wp2latex-3.94+ds/debian/changelog 2021-02-14 23:32:46.0 +0100
+++ wp2latex-3.94+ds/debian/changelog 2021-03-18 21:28:50.0 +0100
@@ -1,3 +1,10 @@
+wp2latex (3.94+ds-2) unstable; urgency=medium
+
+ * Fix a nasty bug, which could lead to invalid eps files. Got
+notification and patch from upstream. Thanks Jaroslav Fojtik!
+
+ -- Hilmar Preusse Thu, 18 Mar 2021 21:28:50 +0100
+
wp2latex (3.94+ds-1) unstable; urgency=medium
* New upstream release, remove merged patches.
diff -Nru wp2latex-3.94+ds/debian/patches/invalid_eps_files
wp2latex-3.94+ds/debian/patches/invalid_eps_files
--- wp2latex-3.94+ds/debian/patches/invalid_eps_files 1970-01-01
01:00:00.0 +0100
+++ wp2latex-3.94+ds/debian/patches/invalid_eps_files 2021-03-18
21:26:24.0 +0100
@@ -0,0 +1,26 @@
+Description: Fix nasty bug leading to invalid eps files.
+Origin: Jaroslav Fojtik
+Forwarded: Patch is from upstream, not needed.
+Author: Jaroslav Fojtik
+Last-Update: 20210318
+
+Index: wp2latex.git/sources.cc/images/vecimage.cc
+===
+--- wp2latex.git.orig/sources.cc/images/vecimage.cc2021-03-18
13:20:12.699391018 +0100
wp2latex.git/sources.cc/images/vecimage.cc 2021-03-18 13:20:12.691391041
+0100
+@@ -1068,9 +1068,12 @@
+ {
+ if(str[len-2]=='(' && str[len-1]==')')
+ {
+- if(len>=3 && str[len-3]==' ') len--;//Remove orphaned space.
+- str = copy(str,0,len-2);
+- return;
++ if(len>=3 && str[len-3]!='\\') // Is the curly brace preffixed?
++{
++if(len>=3 && str[len-3]==' ') len--; //Remove orphaned space.
++str = copy(str,0,len-2);
++return;
++}
+ }
+ }
+ str += "\nshow";
diff -Nru wp2latex-3.94+ds/debian/patches/series
wp2latex-3.94+ds/debian/patches/series
--- wp2latex-3.94+ds/debian/patches/series 2021-02-14 22:40:59.0
+0100
+++ wp2latex-3.94+ds/debian/patches/series 2021-03-18 13:20:07.0
+0100
@@ -5,3 +5,4 @@
#fix_groff-errors
#vecimage.cc_crash
#de.po_typo_adaption
+invalid_eps_files
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---
Bug#985613: marked as done (unblock: terminology/1.9.0-2)
Your message dated Sun, 21 Mar 2021 13:55:50 +
with message-id
and subject line unblock terminology
has caused the Debian Bug report #985613,
regarding unblock: terminology/1.9.0-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.)
--
985613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985613
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: rvandegr...@debian.org
Please unblock package terminology
[ Reason ]
terminology 1.9.0-1 is missing a dependency required for users on wayland.
1.9.0-2 fixes this. The package has non-trivial autopkgtests, but the test
suite doesn't work on all arches. Thus, it will not migrate automatically.
[ Impact ]
terminology won't start for wayland users that are missing
libevas1-engines-wayland
[ Tests ]
1.9.0-2 only contains packaging changes:
- add Depends on libevas1-engines-wayland
- remove unused cme files accidentally included in the 1.9.0-1 upload. This is
not in the changelog because I only just discovered the issue. I can do a
1.9.0-3 changelog-only release, if that's better.
[ Risks ]
terminology is a leaf package, so the risk is isolated.
[ Checklist ]
[ ] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in testing
[ Other info ]
unblock terminology/1.9.0-2
diff -Nru terminology-1.9.0/debian/changelog terminology-1.9.0/debian/changelog
--- terminology-1.9.0/debian/changelog 2021-01-20 23:15:33.0 -0800
+++ terminology-1.9.0/debian/changelog 2021-03-14 22:46:23.0 -0700
@@ -1,3 +1,9 @@
+terminology (1.9.0-2) unstable; urgency=medium
+
+ * d/control: Depend on libevas1-engines-wayland (Closes: #985208)
+
+ -- Ross Vandegrift Sun, 14 Mar 2021 22:46:23 -0700
+
terminology (1.9.0-1) unstable; urgency=medium
* New upstream version
diff -Nru terminology-1.9.0/debian/control terminology-1.9.0/debian/control
--- terminology-1.9.0/debian/control2021-01-20 22:21:53.0 -0800
+++ terminology-1.9.0/debian/control2021-03-14 22:34:15.0 -0700
@@ -16,7 +16,7 @@
Package: terminology
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, terminology-data (=
${source:Version}), libevas1-engines-x
+Depends: ${shlibs:Depends}, ${misc:Depends}, terminology-data (=
${source:Version}), libevas1-engines-x, libevas1-engines-wayland
Suggests: libelementary-bin, libemotion-players
Provides: x-terminal-emulator
Description: Enlightenment efl based terminal emulator
diff -Nru terminology-1.9.0/debian/copyright-scan-patterns.yml
terminology-1.9.0/debian/copyright-scan-patterns.yml
--- terminology-1.9.0/debian/copyright-scan-patterns.yml2021-01-20
22:32:09.0 -0800
+++ terminology-1.9.0/debian/copyright-scan-patterns.yml1969-12-31
16:00:00.0 -0800
@@ -1,41 +0,0 @@
-check:
- suffixes:
-- "*"
-
-ignore:
- pattern:
-- afl/
-- data/themes/
-- data/fonts/TERMINUS.txt
-- data/fonts/XFONT.txt
- suffixes:
-# cme/licensecheck barfs up garbage if binaries aren't excluded
-- bmp
-- dds
-- edc
-- eet
-- eps
-- gif
-- j2k
-- jp2
-- jpg
-- jpeg
-- md2
-- mo
-- ogg
-- ply
-- png
-- psd
-- svg
-- svgz
-- tga
-- tgv
-- ttf
-- wav
-- wbmp
-- webp
-- x
-- xcf
-- xcf.gz
-- xpm
diff -Nru terminology-1.9.0/debian/fill.copyright.blanks.yml
terminology-1.9.0/debian/fill.copyright.blanks.yml
--- terminology-1.9.0/debian/fill.copyright.blanks.yml 2021-01-20
22:31:22.0 -0800
+++ terminology-1.9.0/debian/fill.copyright.blanks.yml 1969-12-31
16:00:00.0 -0800
@@ -1,23 +0,0 @@
-.*:
- copyright: 2012-2020 Carsten Haitzler and various contributors (see AUTHORS)
- license: BSD-2-clause
-
-po/*:
- 'override-copyright': 2012-2020 Carsten Haitzler and various contributors
(see AUTHORS)
- 'override-license': BSD-2-clause
-
-meson.build:
- copyright: 2012-2020 Carsten Haitzler and various contributors (see AUTHORS)
- 'override-license': BSD-2-clause
-
-data/fonts/*.pcf:
- license: public-domain
- copyright: none
-
-data/fonts/nexus.pcf:
- copyright: 1996-2002 Carsten Haitzler, Jonathan Perkin, Tom Gilbert and
Simon Horman
- license: BSD-2-clause
-
-data/fonts/terminus*:
- copyright: 2011 Dimitar Toshkov Zhekov, with Reserved Font Name "Terminus
Font"
- license: SIL-OFL-1.1
--- End Message ---
--- Begin Message -
NEW changes in stable-new
Processing changes file: lirc_0.10.1-6.3~deb10u1_s390x.changes ACCEPT Processing changes file: portaudio19_19.6.0-1+deb10u1_all.changes ACCEPT Processing changes file: portaudio19_19.6.0-1+deb10u1_s390x.changes ACCEPT
NEW changes in stable-new
Processing changes file: linux-signed-arm64_4.19.181+1_arm64-buildd.changes ACCEPT Processing changes file: linux-signed-i386_4.19.181+1_i386.changes ACCEPT Processing changes file: lirc_0.10.1-6.3~deb10u1_all-buildd.changes ACCEPT Processing changes file: lirc_0.10.1-6.3~deb10u1_amd64-buildd.changes ACCEPT Processing changes file: lirc_0.10.1-6.3~deb10u1_arm64-buildd.changes ACCEPT Processing changes file: lirc_0.10.1-6.3~deb10u1_armel-buildd.changes ACCEPT Processing changes file: lirc_0.10.1-6.3~deb10u1_armhf-buildd.changes ACCEPT Processing changes file: lirc_0.10.1-6.3~deb10u1_i386-buildd.changes ACCEPT Processing changes file: lirc_0.10.1-6.3~deb10u1_mips-buildd.changes ACCEPT Processing changes file: lirc_0.10.1-6.3~deb10u1_ppc64el-buildd.changes ACCEPT Processing changes file: portaudio19_19.6.0-1+deb10u1_amd64-buildd.changes ACCEPT Processing changes file: portaudio19_19.6.0-1+deb10u1_arm64-buildd.changes ACCEPT Processing changes file: portaudio19_19.6.0-1+deb10u1_armel-buildd.changes ACCEPT Processing changes file: portaudio19_19.6.0-1+deb10u1_armhf-buildd.changes ACCEPT Processing changes file: portaudio19_19.6.0-1+deb10u1_i386-buildd.changes ACCEPT Processing changes file: portaudio19_19.6.0-1+deb10u1_mips-buildd.changes ACCEPT Processing changes file: portaudio19_19.6.0-1+deb10u1_ppc64el-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: lirc_0.10.1-6.3~deb10u1_mips64el-buildd.changes ACCEPT Processing changes file: portaudio19_19.6.0-1+deb10u1_mips64el-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: lirc_0.10.1-6.3~deb10u1_mipsel-buildd.changes ACCEPT Processing changes file: portaudio19_19.6.0-1+deb10u1_mipsel-buildd.changes ACCEPT
Bug#985662: unblock: gimp/2.10.22-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package gimp
[ Reason ]
gimp now needs a hard dependency on graphviz as it uses an optional
feature of libgegl that requires the "dot" executable. Adding an hard
dependency on graphviz in libgegl package looks overkill as the other
packages dont seem to use that feature.
I also added a patch that define PATH_MAX for hurd, this is not changing
anything on the release architectures.
[ Impact ]
Without the graphviz package installed, gimp fails to start
[ Tests ]
Gimp now starts, this has been confirmed by some users.
[ Risks ]
Adding the dependency has no risk
PATH_MAX should already be defined in all other architectures than hurd,
so there is also no risks possible here either
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
This has been reported multiple times on the r/debian subreddit, so
there are actuall users impacted by this
unblock gimp/2.10.22-3
diff -Nru gimp-2.10.22/debian/changelog gimp-2.10.22/debian/changelog
--- gimp-2.10.22/debian/changelog 2020-11-24 10:25:51.0 +0100
+++ gimp-2.10.22/debian/changelog 2021-03-20 12:21:08.0 +0100
@@ -1,3 +1,13 @@
+gimp (2.10.22-3) unstable; urgency=medium
+
+ * debian/control.in: Add graphviz to the dependencies.
+Some optional functionality of libgegl used in gimp now requires the dot
+executable shipped in the graphviz package (Closes: #985317)
+ * debian/patches/02_hurd_ftbfs.patch: Fix FTBFS on hurd-i386.
+Thanks to Svante Signell (Closes: #934077)
+
+ -- Laurent Bigonville Sat, 20 Mar 2021 12:21:08 +0100
+
gimp (2.10.22-2) unstable; urgency=medium
* Team upload
diff -Nru gimp-2.10.22/debian/control gimp-2.10.22/debian/control
--- gimp-2.10.22/debian/control 2020-11-24 10:25:51.0 +0100
+++ gimp-2.10.22/debian/control 2021-03-20 12:21:08.0 +0100
@@ -6,7 +6,7 @@
Priority: optional
Section: graphics
Maintainer: Debian GNOME Maintainers
-Uploaders: Iain Lane , Jeremy Bicha , Ari
Pollak
+Uploaders: Iain Lane , Jeremy Bicha ,
Laurent Bigonville , Ari Pollak
Build-Depends: debhelper-compat (= 13),
desktop-file-utils ,
dh-sequence-gnome,
@@ -74,6 +74,7 @@
libgimp2.0 (<= ${source:Upstream-Version}-z),
gimp-data (>= ${source:Upstream-Version}),
gimp-data (<= ${source:Upstream-Version}-z),
+ graphviz,
xdg-utils,
${shlibs:Depends},
${misc:Depends}
diff -Nru gimp-2.10.22/debian/control.in gimp-2.10.22/debian/control.in
--- gimp-2.10.22/debian/control.in 2020-11-24 10:25:51.0 +0100
+++ gimp-2.10.22/debian/control.in 2021-03-20 12:21:08.0 +0100
@@ -70,6 +70,7 @@
libgimp2.0 (<= ${source:Upstream-Version}-z),
gimp-data (>= ${source:Upstream-Version}),
gimp-data (<= ${source:Upstream-Version}-z),
+ graphviz,
xdg-utils,
${shlibs:Depends},
${misc:Depends}
diff -Nru gimp-2.10.22/debian/patches/02_hurd_ftbfs.patch
gimp-2.10.22/debian/patches/02_hurd_ftbfs.patch
--- gimp-2.10.22/debian/patches/02_hurd_ftbfs.patch 1970-01-01
01:00:00.0 +0100
+++ gimp-2.10.22/debian/patches/02_hurd_ftbfs.patch 2021-03-20
12:21:08.0 +0100
@@ -0,0 +1,12 @@
+--- a/plug-ins/common/qbist.c
b/plug-ins/common/qbist.c
+@@ -38,6 +38,9 @@
+
+ #include "libgimp/stdplugins-intl.h"
+
++#ifndef PATH_MAX
++#define PATH_MAX 4096
++#endif
+
+ /** qbist renderer
***/
+
diff -Nru gimp-2.10.22/debian/patches/series gimp-2.10.22/debian/patches/series
--- gimp-2.10.22/debian/patches/series 2020-11-24 10:25:51.0 +0100
+++ gimp-2.10.22/debian/patches/series 2021-03-20 12:21:08.0 +0100
@@ -1 +1,2 @@
01_hurd_ftbfs.patch
+02_hurd_ftbfs.patch
Processed: Re: Bug#985538: unblock: vala/0.48.15-1
Processing control commands: > tags -1 moreinfo Bug #985538 [release.debian.org] unblock: vala/0.48.15-1 Added tag(s) moreinfo. -- 985538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985662: marked as done (unblock: gimp/2.10.22-3)
Your message dated Sun, 21 Mar 2021 17:43:13 +
with message-id
and subject line unblock gimp
has caused the Debian Bug report #985662,
regarding unblock: gimp/2.10.22-3
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.)
--
985662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985662
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 gimp
[ Reason ]
gimp now needs a hard dependency on graphviz as it uses an optional
feature of libgegl that requires the "dot" executable. Adding an hard
dependency on graphviz in libgegl package looks overkill as the other
packages dont seem to use that feature.
I also added a patch that define PATH_MAX for hurd, this is not changing
anything on the release architectures.
[ Impact ]
Without the graphviz package installed, gimp fails to start
[ Tests ]
Gimp now starts, this has been confirmed by some users.
[ Risks ]
Adding the dependency has no risk
PATH_MAX should already be defined in all other architectures than hurd,
so there is also no risks possible here either
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
This has been reported multiple times on the r/debian subreddit, so
there are actuall users impacted by this
unblock gimp/2.10.22-3
diff -Nru gimp-2.10.22/debian/changelog gimp-2.10.22/debian/changelog
--- gimp-2.10.22/debian/changelog 2020-11-24 10:25:51.0 +0100
+++ gimp-2.10.22/debian/changelog 2021-03-20 12:21:08.0 +0100
@@ -1,3 +1,13 @@
+gimp (2.10.22-3) unstable; urgency=medium
+
+ * debian/control.in: Add graphviz to the dependencies.
+Some optional functionality of libgegl used in gimp now requires the dot
+executable shipped in the graphviz package (Closes: #985317)
+ * debian/patches/02_hurd_ftbfs.patch: Fix FTBFS on hurd-i386.
+Thanks to Svante Signell (Closes: #934077)
+
+ -- Laurent Bigonville Sat, 20 Mar 2021 12:21:08 +0100
+
gimp (2.10.22-2) unstable; urgency=medium
* Team upload
diff -Nru gimp-2.10.22/debian/control gimp-2.10.22/debian/control
--- gimp-2.10.22/debian/control 2020-11-24 10:25:51.0 +0100
+++ gimp-2.10.22/debian/control 2021-03-20 12:21:08.0 +0100
@@ -6,7 +6,7 @@
Priority: optional
Section: graphics
Maintainer: Debian GNOME Maintainers
-Uploaders: Iain Lane , Jeremy Bicha , Ari
Pollak
+Uploaders: Iain Lane , Jeremy Bicha ,
Laurent Bigonville , Ari Pollak
Build-Depends: debhelper-compat (= 13),
desktop-file-utils ,
dh-sequence-gnome,
@@ -74,6 +74,7 @@
libgimp2.0 (<= ${source:Upstream-Version}-z),
gimp-data (>= ${source:Upstream-Version}),
gimp-data (<= ${source:Upstream-Version}-z),
+ graphviz,
xdg-utils,
${shlibs:Depends},
${misc:Depends}
diff -Nru gimp-2.10.22/debian/control.in gimp-2.10.22/debian/control.in
--- gimp-2.10.22/debian/control.in 2020-11-24 10:25:51.0 +0100
+++ gimp-2.10.22/debian/control.in 2021-03-20 12:21:08.0 +0100
@@ -70,6 +70,7 @@
libgimp2.0 (<= ${source:Upstream-Version}-z),
gimp-data (>= ${source:Upstream-Version}),
gimp-data (<= ${source:Upstream-Version}-z),
+ graphviz,
xdg-utils,
${shlibs:Depends},
${misc:Depends}
diff -Nru gimp-2.10.22/debian/patches/02_hurd_ftbfs.patch
gimp-2.10.22/debian/patches/02_hurd_ftbfs.patch
--- gimp-2.10.22/debian/patches/02_hurd_ftbfs.patch 1970-01-01
01:00:00.0 +0100
+++ gimp-2.10.22/debian/patches/02_hurd_ftbfs.patch 2021-03-20
12:21:08.0 +0100
@@ -0,0 +1,12 @@
+--- a/plug-ins/common/qbist.c
b/plug-ins/common/qbist.c
+@@ -38,6 +38,9 @@
+
+ #include "libgimp/stdplugins-intl.h"
+
++#ifndef PATH_MAX
++#define PATH_MAX 4096
++#endif
+
+ /** qbist renderer
***/
+
diff -Nru gimp-2.10.22/debian/patches/series gimp-2.10.22/debian/patches/series
--- gimp-2.10.22/debian/patches/series 2020-11-24 10:25:51.0 +0100
+++ gimp-2.10.22/debian/patches/series 2021-03-20 12:21:08.0 +0100
@@ -1 +1,2 @@
01_hurd_ftbfs.patch
+02_hurd_ftbfs.patch
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---
Bug#985610: unblock (pre-approval): glib2.0/2.66.8-1
Control: tags -1 confirmed moreinfo On 2021-03-20 21:58:39 +, Simon McVittie wrote: > On Sat, 20 Mar 2021 at 17:08:14 +, Simon McVittie wrote: > > [x] attach debdiff against the package in testing > > (as with the recent mutter and gnome-shell unblocks, to minimize > > noise this is a diff between patched trees, excluding the patches > > themselves) > > Sorry, really attached now. Thanks, please go ahead and let us know once it reached unstable. Cheers > > smcv > git diff archive/debian/2.66.7-2..patch-queue/debian/master | filterdiff -p1 > --exclude 'debian/patches/*.patch' > > diff --git a/NEWS b/NEWS > index 0f0a6a28b..d4a4703d2 100644 > --- a/NEWS > +++ b/NEWS > @@ -1,3 +1,15 @@ > +Overview of changes in GLib 2.66.8 > +== > + > +* Fix a security issue when using `g_file_replace()` with > + `G_FILE_CREATE_REPLACE_DESTINATION` (#2325) > + > +* Bugs fixed: > + - #2325 file-roller symlink attack > + - !1982 Backport !2325 “file-roller symlink attack” to glib-2-66 > + - !1990 Backport !1976 “Use the right permissions for directory watching on > Win32” to glib-2-66 > + > + > Overview of changes in GLib 2.66.7 > == > > diff --git a/debian/changelog b/debian/changelog > index eefd875a6..80c0657ef 100644 > --- a/debian/changelog > +++ b/debian/changelog > @@ -1,3 +1,23 @@ > +glib2.0 (2.66.8-1) unstable; urgency=medium > + > + * d/watch: Only watch for 2.66.x versions. > +2.68.0 has been released but will not be in bullseye. > + * New upstream release > +- Functionally equivalent to 2.66.7-2, except for the version number > + and a change to Windows-specific code that is not used in Debian > + * Drop patches that were included in the new upstream release > + * d/p/glocalfileoutputstream-Tidy-up-error-handling.patch: > +Add patch from upstream to clean up error handling. > +After the fix for #984969, this function could end up calling close(-1), > +which is harmless but gets flagged as an error by static analysis and > +by error-checking instrumentation. Fixing this will prevent it from > +obscuring real errors. > + * Add CVE references in recent changelog entries. > +CVE IDs for the vulnerabilities were not available at the time they were > +fixed, but now they are. > + > + -- Simon McVittie Sat, 20 Mar 2021 15:35:19 + > + > glib2.0 (2.66.7-2) unstable; urgency=medium > >* d/changelog: Add bug numbers for integer overflows in previous versions > @@ -6,7 +26,7 @@ glib2.0 (2.66.7-2) unstable; urgency=medium > replace a path that is a dangling symlink, previously it would have also > created the target of the symlink as an empty file, which could > conceivably be security-sensitive if the symlink is attacker-controlled. > -(Closes: #984969) > +(Closes: #984969; CVE-2021-28153) > > -- Simon McVittie Thu, 11 Mar 2021 10:23:38 + > > @@ -16,7 +36,7 @@ glib2.0 (2.66.7-1) unstable; urgency=high > - Fix another regression caused by the GHSL-2021-045 fixes in 2.66.6 > - Warn and fail on integer overflow in g_byte_array_new_take() >for arrays larger than G_MAXUINT > - (Closes: #982779; similar to GHSL-2021-045) > + (Closes: #982779; CVE-2021-27218) > - Disallow using currently-undefined D-Bus connection or server flags, >to prevent forward-compatibility problems with new security-sensitive >flags that are likely to be introduced in GLib 2.68 > @@ -41,7 +61,7 @@ glib2.0 (2.66.6-1) unstable; urgency=high > >* New upstream release > - Fix various integer overflows, some of them potentially exploitable > - (Closes: #982778, GHSL-2021-045) > + (Closes: #982778; CVE-2021-27219, GHSL-2021-045) > > -- Simon McVittie Thu, 04 Feb 2021 20:24:20 + > > diff --git > a/debian/patches/glocalfileoutputstream-Tidy-up-error-handling.patch > b/debian/patches/glocalfileoutputstream-Tidy-up-error-handling.patch > new file mode 100644 > index 0..04f040d40 > diff --git a/debian/patches/series b/debian/patches/series > index 772de8095..8e7842b2f 100644 > --- a/debian/patches/series > +++ b/debian/patches/series > @@ -1,10 +1,6 @@ > -glocalfileoutputstream-Fix-a-typo-in-a-comment.patch > -tests-Stop-using-g_test_bug_base-in-file-tests.patch > -glocalfileoutputstream-Factor-out-a-flag-check.patch > -glocalfileoutputstream-Fix-CREATE_REPLACE_DESTINATION-wit.patch > -glocalfileoutputstream-Add-a-missing-O_CLOEXEC-flag-to-re.patch > glib-tests-fileutils-Make-more-use-of-g_assert_no_errno.patch > glib-tests-fileutils-Fix-expectations-when-running-as-roo.patch > +glocalfileoutputstream-Tidy-up-error-handling.patch > 01_gettext-desktopfiles.patch > 0001-timer-test-use-volatile-for-locals.patch > gwakeuptest-Be-less-parallel-unless-invoked-with-m-slow.patch > diff --git a/debian/watch b/debian/watch > index f028879b9..5a5e3cbab 100644 > --- a/debian/watch > +++
Processed: Re: Bug#985610: unblock (pre-approval): glib2.0/2.66.8-1
Processing control commands: > tags -1 confirmed moreinfo Bug #985610 [release.debian.org] unblock (pre-approval): glib2.0/2.66.8-1 Added tag(s) moreinfo and confirmed. -- 985610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985628: marked as done (unblock: docx2txt/1.4-5)
Your message dated Sun, 21 Mar 2021 17:44:34 + with message-id and subject line unblock docx2txt has caused the Debian Bug report #985628, regarding unblock: docx2txt/1.4-5 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.) -- 985628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985628 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 docx2txt [ Reason ] Fix mime security issue: '%s' [ Impact ] Potential vulnerability, or package unavailable if #985594 causes its removal. [ Tests ] none [ Risks ] change is trivial [ Checklist ] [X] all changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in testing unblock docx2txt/1.4-5 $ debdiff diff -Nru docx2txt-1.4/debian/changelog docx2txt-1.4/debian/changelog --- docx2txt-1.4/debian/changelog 2020-12-11 21:56:27.0 + +++ docx2txt-1.4/debian/changelog 2021-03-20 17:13:44.0 + @@ -1,3 +1,9 @@ +docx2txt (1.4-5) unstable; urgency=medium + + * Address security issue: do not quote %s in mailcap entry (closes: #985594) + + -- Barak A. Pearlmutter Sat, 20 Mar 2021 17:13:44 + + docx2txt (1.4-4) unstable; urgency=medium * debian/rules does not require root diff -Nru docx2txt-1.4/debian/docx2txt.mime docx2txt-1.4/debian/docx2txt.mime --- docx2txt-1.4/debian/docx2txt.mime 2020-12-11 21:55:16.0 + +++ docx2txt-1.4/debian/docx2txt.mime 2021-03-20 17:12:47.0 + @@ -1 +1 @@ -application/vnd.openxmlformats-officedocument.wordprocessingml.document; docx2txt '%s' - ; copiousoutput; description=Office Open XML Document +application/vnd.openxmlformats-officedocument.wordprocessingml.document; docx2txt %s - ; copiousoutput; description=Office Open XML Document --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Bug#985672: unblock: mumps/5.3.5-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package mumps
(Please provide enough (but not too much) information to help
the release team to judge the request efficiently. E.g. by
filling in the sections below.)
[ Reason ]
RC Bug#985514 reports that libmumps64-seq-dev has dangling library
symlinks. This is because the Depends field of libmumps64-seq-dev
was misconfigured, Depending on libmumps-seq-5.3 instead of
libmumps-64pord-seq-5.3
Release 5.3.5-2 fixes this.
5.3.5-2 also promotes the Standards-Version to 4.5.1
[ Impact ]
The unpatched libmumps64-seq-dev will not function correctly, containing
empty symlinks to the wrong package, unless libmumps-64pord-seq-5.3
happens to be installed (it is supposed to be required)
[ Tests ]
debci tests are passing in testing (bullseye).
[ Risks ]
The patch is trivial, one fix in Depends field of libmumps64-seq-dev,
and update to
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
unblock mumps/5.3.5-2
diff -Nru mumps-5.3.5/debian/changelog mumps-5.3.5/debian/changelog
--- mumps-5.3.5/debian/changelog2020-10-29 05:11:59.0 +0100
+++ mumps-5.3.5/debian/changelog2021-03-20 04:52:40.0 +0100
@@ -1,3 +1,12 @@
+mumps (5.3.5-2) unstable; urgency=medium
+
+ * Team upload.
+ * libmumps64-seq-dev Depends: libmumps-64pord-seq-5.3
+(not libmumps-seq-dev, libmumps-seq-5.3). Closes: #985514.
+ * Standards-Version: 4.5.1
+
+ -- Drew Parsons Sat, 20 Mar 2021 04:52:40 +0100
+
mumps (5.3.5-1) unstable; urgency=medium
* Team upload.
diff -Nru mumps-5.3.5/debian/control mumps-5.3.5/debian/control
--- mumps-5.3.5/debian/control 2020-10-29 05:11:59.0 +0100
+++ mumps-5.3.5/debian/control 2021-03-20 04:52:40.0 +0100
@@ -13,7 +13,7 @@
libscalapack-mpi-dev (>= 2.0.2),
libscotch-dev,
mpi-default-dev
-Standards-Version: 4.5.0
+Standards-Version: 4.5.1
Vcs-Git: https://salsa.debian.org/science-team/mumps.git
Vcs-Browser: https://salsa.debian.org/science-team/mumps
Homepage: http://mumps-solver.org/
@@ -192,8 +192,7 @@
Depends:
libmumps64-dev (= ${binary:Version}),
libmumps-headers-dev (= ${source:Version}),
- libmumps-seq-dev (= ${binary:Version}),
- libmumps-seq-5.3 (= ${binary:Version}),
+ libmumps-64pord-seq-5.3 (= ${binary:Version}),
${misc:Depends},
Description: Direct linear systems solver (64 bit) - non-parallel development
files
MUMPS implements a direct solver for large sparse linear systems, with a
Bug#985610: unblock (pre-approval): glib2.0/2.66.8-1
Control: tags -1 - moreinfo On Sun, 21 Mar 2021 at 18:46:05 +0100, Sebastian Ramacher wrote: > Thanks, please go ahead and let us know once it reached unstable. Uploaded to unstable, built on all release architectures except mips*el (which are pending). smcv
Processed: Re: Bug#985610: unblock (pre-approval): glib2.0/2.66.8-1
Processing control commands: > tags -1 - moreinfo Bug #985610 [release.debian.org] unblock (pre-approval): glib2.0/2.66.8-1 Removed tag(s) moreinfo. -- 985610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985610: marked as done (unblock (pre-approval): glib2.0/2.66.8-1)
Your message dated Sun, 21 Mar 2021 19:32:14 + with message-id and subject line unblock glib2.0 has caused the Debian Bug report #985610, regarding unblock (pre-approval): glib2.0/2.66.8-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.) -- 985610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985610 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 I'd like pre-approval to upload glib2.0/2.66.8-1 to unstable. [ Reason ] * Sync up with upstream 2.66.8 release, 95% of which we already apply via debian/patches * Add an error-handling patch from upstream that they recommended I consider including when backporting recent security fixes to buster * Add missing CVE ID references to changelog [ Impact ] Using 2.66.8 will make it more obvious that we have the CVE-2021-28153 fix. The error handling patch (gio/glocalfileoutputstream.c in the diff) is not critical, but it fixes an oversight in the CVE-2021-28153 fix. If we don't have it, GLib will attempt to close(-1) under some circumstances, which is harmless but gets flagged as an error by static analysis (e.g. Coverity) and debug instrumentation, obscuring more important issues. Upstream recommended that I include this in backports to buster, which I probably will unless the security team or SRMs ask me not to. [ Tests ] GLib has a large test suite which we run at build time and in autopkgtests. I run autopkgtests on amd64 and i386 qemu VMs before each upload. I haven't done any manual testing on this just yet, but I'll use it on my GNOME systems for a while before uploading. [ Risks ] It's an important key package and used in all our desktops, but the changes are targeted and obvious. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing (as with the recent mutter and gnome-shell unblocks, to minimize noise this is a diff between patched trees, excluding the patches themselves) [ Other info ] This is likely to be the last upstream release from the 2.66.x branch, so any subsequent fixes (security or otherwise) will be back to using the patch series. unblock glib2.0/2.66.8-1 --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Bug#985626: marked as done (unblock: lirc/0.10.1-6.3)
Your message dated Sun, 21 Mar 2021 19:31:06 +
with message-id
and subject line unblock lirc
has caused the Debian Bug report #985626,
regarding unblock: lirc/0.10.1-6.3
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.)
--
985626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985626
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 lirc
In my last update of lirc I overlooked that one of the conffiles
contains the value of $DEB_HOST_MULTIARCH and thus the detection of
known old conffiles by md5sum only worked on amd64. I've now fixed
that and verified that upgrades from stretch to buster or later
with this patch work on i386 as well as amd64.
The attached diff is a git diff because it better copes with the rename
of debian/lirc.preinst to debian/lirc.preinst.in
This fix will get rebuilt for buster as 0.10.1-6.3~deb10u1
unblock lirc/0.10.1-6.3
Andreas
diff --git a/debian/changelog b/debian/changelog
index b503742..14e651f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+lirc (0.10.1-6.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * d/lirc.preinst: Normalize embedded ${DEB_HOST_MULTIARCH} value in
+/etc/lirc/lirc_options.conf to find unmodified configuration files on all
+architectures.
+ * Recommend gir1.2-vte-2.91 instead of non-existant gir1.2-vte.
+(Closes: #983581)
+
+ -- Andreas Beckmann Thu, 18 Mar 2021 22:21:31 +0100
+
lirc (0.10.1-6.2) unstable; urgency=medium
* Non-maintainer upload.
diff --git a/debian/control b/debian/control
index 7f18471..a8deb3f 100644
--- a/debian/control
+++ b/debian/control
@@ -45,7 +45,7 @@ Depends:
${python3:Depends},
${shlibs:Depends}
Recommends:
- gir1.2-vte,
+ gir1.2-vte-2.91,
python3-yaml,
python3-gi,
systemd [linux-any]
diff --git a/debian/lirc.preinst b/debian/lirc.preinst.in
similarity index 76%
rename from debian/lirc.preinst
rename to debian/lirc.preinst.in
index 53a5c31..df3b9cc 100644
--- a/debian/lirc.preinst
+++ b/debian/lirc.preinst.in
@@ -3,13 +3,13 @@ set -e
md5sums_shipped="
92df549c82f58ea28b605e5045984e04 /etc/lirc/irexec.lircrc
-d2664e84bab19f7f36628d1de3f273dd /etc/lirc/lirc_options.conf #stretch
-6599e8ea08b5f4bf19409666cae22441 /etc/lirc/lirc_options.conf #buster
+6447d4261e0b8a80beb4b94e80ea /etc/lirc/lirc_options.conf #stretch,
normalized
+c2a8478e9eda95eb4216414a7979acb5 /etc/lirc/lirc_options.conf #buster,
normalized
810233d6f1bb15b64468beb95e4c670e /etc/lirc/lircd.conf
eca53bdc53bd5edc63cf06a4cff16b0d /etc/lirc/lircmd.conf
"
-if dpkg --compare-versions "$2" lt-nl "0.10.1-6.2~"
+if dpkg --compare-versions "$2" lt-nl "0.10.1-6.3~"
then
# * configuration files unknown to dpkg and identical to a known
# shipped version can be deleted to avoid prompting when replacing
@@ -26,7 +26,7 @@ then
continue
fi
case "$md5sums_shipped" in
- *"$(md5sum "$conffile")"*)
+ *"$(md5sum "$conffile")"*|*"$(sed
's%@DEB_HOST_MULTIARCH@%%g' "$conffile" | md5sum | sed
"s%-%$conffile%")"*)
echo "Removing unmodified configuration file
$conffile which is unknown to dpkg."
rm "$conffile"
;;
diff --git a/debian/rules b/debian/rules
index 84787ef..8223d80 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,11 +9,16 @@ export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
dh $@ --with python3
override_dh_clean:
+ $(RM) debian/lirc.preinst
dh_clean
override_dh_autoreconf:
dh_autoreconf $(CURDIR)/autogen.sh
+debian/lirc.preinst: debian/lirc.preinst.in
+ sed 's/@DEB_HOST_MULTIARCH@/$(DEB_HOST_MULTIARCH)/g' $< > $@
+
+override_dh_auto_configure: debian/lirc.preinst
override_dh_auto_configure:
ifeq ($(DEB_BUILD_ARCH_OS), linux)
dh_auto_configure -- \
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---
NEW changes in stable-new
Processing changes file: base-files_10.3+deb10u9_source.changes ACCEPT
NEW changes in stable-new
Processing changes file: base-files_10.3+deb10u9_amd64.changes ACCEPT Processing changes file: base-files_10.3+deb10u9_armel-buildd.changes ACCEPT Processing changes file: base-files_10.3+deb10u9_armhf-buildd.changes ACCEPT Processing changes file: base-files_10.3+deb10u9_i386.changes ACCEPT Processing changes file: base-files_10.3+deb10u9_s390x.changes ACCEPT
NEW changes in stable-new
Processing changes file: base-files_10.3+deb10u9_arm64-buildd.changes ACCEPT Processing changes file: base-files_10.3+deb10u9_mips-buildd.changes ACCEPT Processing changes file: base-files_10.3+deb10u9_ppc64el-buildd.changes ACCEPT
Bug#985683: unblock: powerline/2.8.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package powerline I'd like to update powerline to the latest release, it's a minor version bump, with all the changes being fair for a minor bump. powerline is a non-key package and a mature software at this point, our users will benefit from a considerable amount of bugfixes which would be too much work to port individually. I have verified all commits since the previous release and everything looks good. Note that powerline is only blocked because it doesn't have autopkgtest, but upstream does have good automated testing on their side. [ Reason ] * Use `--no-optional-locks` to reduce conflicts with other git editors * Fixes elapsed time that is provided with a ',' instead of a '.' * Render cpu_load_percent segment even when psutil returns 0.0 * Shifted away from (abandoned) Yahoo API to OpenWeatherMap * Prefer Python 3 in the Vim plugin * Fixed getcwd for tmux * Fix escaping of sh specific characters in tmux * Use updated i3ipc syntax in i3 segments/listers [ Impact ] Missing the fixes described above. [ Tests ] I use powerline daily and I have not found any issues with the latest release. Upstream also runs a lot of automated tests against different environments and found no regressions. https://travis-ci.org/github/powerline/powerline/builds/760903189 [ Risks ] non-key package The new release is mostly about fixinf existing problems, though there are a few functionality additions, all the commits were verified by me and can be seen here: https://github.com/powerline/powerline/compare/d137a88...2.8.2 powerline is a mature software at this point, and this being a minor release plus all the automated tests give me confidence we should ship this release to our users. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing unblock powerline/2.8.2-1
Bug#985390: Make this request valid for 4.13-8
Hi! While we were waiting for 4.13-7 to age and enter testing, we were filled a security bug for CVE-2020-25097. I decided to fix that security problem ASAP and that is what is on 4.13-8, just that. 4.13-8 just adds the patch to fix the CVE as available at: http://www.squid-cache.org/Versions/v4/changesets/SQUID-2020_11.patch You can see more info on all this on the bug that was assigned, #985068. Regards. -- Manty/BestiaTester -> http://manty.net
NEW changes in stable-new
Processing changes file: base-files_10.3+deb10u9_mips64el-buildd.changes ACCEPT Processing changes file: base-files_10.3+deb10u9_mipsel-buildd.changes ACCEPT
