Bug#1051143: bookworm-pu: package dput-ng/1.35+deb12u1

2023-09-03 Thread Mattia Rizzolo
Package: release.debian.org
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: dput...@packages.debian.org
Control: affects -1 + src:dput-ng


[ Reason ]

Fix FTBFS.
Allow upload to bookworm-backports from bookworm hosts.

[ Tests ]
Both automated and manual tests done.

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

[ Other info ]
I will find a way to fix this time bomb once and for all during this
cycle, since this was postponed several times in the last half decade…


Also, I already uploaded this package.

-- 
regards,
Mattia Rizzolo

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

 debian/changelog |   14 ++
 debian/control   |2 +-
 debian/gbp.conf  |1 +
 skel/codenames/debian.json   |   15 ++-
 tests/dputng/codenames/debian.json   |   15 ++-
 tests/fake_package/fake-package-1.0/debian/changelog |2 +-
 tests/fake_package/fake-package-1.1/debian/changelog |2 +-
 7 files changed, 38 insertions(+), 13 deletions(-)

diff -Nru dput-ng-1.35/debian/changelog dput-ng-1.35+deb12u1/debian/changelog
--- dput-ng-1.35/debian/changelog	2022-08-29 15:11:49.0 +0530
+++ dput-ng-1.35+deb12u1/debian/changelog	2023-09-03 18:26:54.0 +0530
@@ -1,3 +1,17 @@
+dput-ng (1.35+deb12u1) bookworm; urgency=medium
+
+  * Team upload.
+
+  [ Mattia Rizzolo ]
+  * Update codenames of allowed upload targets.  Closes: #1051142
+Add bookworm-backports, bullseye-backports-sloppy, and trixie.
+
+  [ Gianfranco Costamagna ]
+  * Fix FTBFS due to time bomb, move from bionic to jammy in test fixtures,
+also postpone another time bomb due to focal.  Closes: #1042271
+
+ -- Mattia Rizzolo   Sun, 03 Sep 2023 18:26:54 +0530
+
 dput-ng (1.35) unstable; urgency=medium
 
   [ Stefano Rivera ]
diff -Nru dput-ng-1.35/debian/control dput-ng-1.35+deb12u1/debian/control
--- dput-ng-1.35/debian/control	2022-08-29 15:11:49.0 +0530
+++ dput-ng-1.35+deb12u1/debian/control	2023-09-03 18:26:42.0 +0530
@@ -28,7 +28,7 @@
 Standards-Version: 4.6.0
 Rules-Requires-Root: no
 Vcs-Browser: https://salsa.debian.org/debian/dput-ng
-Vcs-Git: https://salsa.debian.org/debian/dput-ng.git
+Vcs-Git: https://salsa.debian.org/debian/dput-ng.git -b bookworm
 Homepage: https://debian.pages.debian.net/dput-ng
 
 Package: dput-ng
diff -Nru dput-ng-1.35/debian/gbp.conf dput-ng-1.35+deb12u1/debian/gbp.conf
--- dput-ng-1.35/debian/gbp.conf	2019-07-19 11:46:20.0 +0530
+++ dput-ng-1.35+deb12u1/debian/gbp.conf	2023-09-03 18:26:52.0 +0530
@@ -1,3 +1,4 @@
 [DEFAULT]
 pristine-tar = True
 debian-tag = %(version)s
+debian-branch = bookworm
diff -Nru dput-ng-1.35/skel/codenames/debian.json dput-ng-1.35+deb12u1/skel/codenames/debian.json
--- dput-ng-1.35/skel/codenames/debian.json	2021-06-24 19:01:59.0 +0530
+++ dput-ng-1.35+deb12u1/skel/codenames/debian.json	2023-09-03 18:22:51.0 +0530
@@ -2,7 +2,9 @@
 "backport": [
 "stable-backports",
 "oldstable-backports",
+"bookworm-backports",
 "bullseye-backports",
+"bullseye-backports-sloppy",
 "buster-backports",
 "buster-backports-sloppy",
 "stretch-backports",
@@ -18,6 +20,11 @@
 "testing",
 "stable",
 "oldstable",
+"testing-proposed-updates",
+"stable-proposed-updates",
+"oldstable-proposed-updates",
+"trixie",
+"trixie-proposed-updates",
 "bookworm",
 "bookworm-proposed-updates",
 "bullseye",
@@ -27,10 +34,7 @@
 "stretch",
 "stretch-proposed-updates",
 "jessie",
-"jessie-proposed-updates",
-"testing-proposed-updates",
-"stable-proposed-updates",
-"oldstable-proposed-updates"
+"jessie-proposed-updates"
 ],
 "security": [
 "testing-security",
@@ -40,7 +44,8 @@
 "stretch-security",
 "buster-security",
 "bullseye-security",
-"bookworm-security"
+"bookworm-security

Bug#1039961: transition: libexecs

2023-06-30 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: libex...@packages.debian.org
Control: affects -1 + src:libexecs
Control: submitter -1 Renzo Davoli 

Hi,

I'd like to ask for permission to carry out this small transition here:
https://release.debian.org/transitions/html/auto-libexecs.html

All the relevant rev-deps are OK and binNMUs would take care of them.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#1033837: unblock: devscripts/2.23.3

2023-04-02 Thread Mattia Rizzolo
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: devscri...@packages.debian.org
Control: affects -1 + src:devscripts

Please unblock package devscripts

[ Reason ]
2.23.3 is only bugfix, including one RC.
Also, it fixes the description generation.

[ Tests ]
most of the changes include tests, and autopkgtest passed great.

[ Risks ]
the changes are quite trivial by themselves.

[ 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 devscripts/2.23.3

-- 
regards,
Mattia Rizzolo

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

 README|2 
 debian/changelog  |   29 
 debian/control|5 
 debian/rules  |2 
 lib/Devscripts/Salsa/Hooks.pm |  246 +--
 lib/Devscripts/Salsa/check_repo.pm|   16 
 po4a/po/de.po |5 
 po4a/po/devscripts.pot|5 
 po4a/po/fr.po |8 
 po4a/po/pt.po |7 
 scripts/bts.pl|2 
 scripts/deb-janitor   |6 
 scripts/debootsnap|   37 -
 scripts/debootsnap.py |  694 ++
 scripts/devscripts/test/test_debootsnap.py|   56 +
 scripts/devscripts/test/test_suspicious_source.py |   41 +
 scripts/edit-patch.sh |   12 
 scripts/sadt  |2 
 scripts/suspicious-source |2 
 19 files changed, 929 insertions(+), 248 deletions(-)

diff -Nru devscripts-2.23.2/debian/changelog devscripts-2.23.3/debian/changelog
--- devscripts-2.23.2/debian/changelog	2023-02-19 00:56:21.0 +0100
+++ devscripts-2.23.3/debian/changelog	2023-03-15 23:52:52.0 +0100
@@ -1,3 +1,32 @@
+devscripts (2.23.3) unstable; urgency=medium
+
+  [ Samuel Henrique ]
+  * Fix generation of the extended description (Closes: #1032337)
+
+  [ Benjamin Drung ]
+  * Fix complaints from pylint 2.16.2
+  * suspicious-source: Fix MIME type name for Python code
+  * Add myself to uploaders
+
+  [ Zixing Liu ]
+  * Salsa/check_repo: avoid dependency on Digest::MD5::File (LP: #2007279)
+  * Salsa/Hooks: using if-elsif chains to avoid Switch which is a deprecated
+package (LP: #2007279)
+
+  [ Johannes Schauer Marin Rodrigues ]
+  * debootsnap:
+- check to make sure that equivs-build, apt-ftparchive, mmdebstrap,
+  apt-get and dpkg-name exist
+- allow reading package list from a file
+
+  [ Rémy Martin ]
+  * edit-patch: Fix failure on creating new patch (LP: #1222364)
+
+  [ Paul Wise ]
+  * bts: Fix mangled UTF-8 name
+
+ -- Benjamin Drung   Wed, 15 Mar 2023 23:52:52 +0100
+
 devscripts (2.23.2) unstable; urgency=medium
 
   * Team upload.
diff -Nru devscripts-2.23.2/debian/control devscripts-2.23.3/debian/control
--- devscripts-2.23.2/debian/control	2023-02-05 01:14:44.0 +0100
+++ devscripts-2.23.3/debian/control	2023-03-15 23:36:26.0 +0100
@@ -4,6 +4,7 @@
 Maintainer: Devscripts Maintainers 
 Uploaders:
  Mattia Rizzolo ,
+ Benjamin Drung ,
 Build-Depends:
  autodep8 ,
  bash-completion,
@@ -18,7 +19,6 @@
  gnupg  | gnupg2 ,
  help2man,
  isort ,
- libdigest-md5-file-perl ,
  libdistro-info-perl ,
  libdpkg-perl ,
  libfile-desktopentry-perl ,
@@ -32,7 +32,6 @@
  liblist-compare-perl ,
  libmoo-perl ,
  libstring-shellquote-perl ,
- libswitch-perl ,
  libtest-output-perl ,
  libtimedate-perl ,
  libtry-tiny-perl ,
@@ -78,14 +77,12 @@
  file,
  gnupg | gnupg2,
  gpgv | gpgv2,
- libdigest-md5-file-perl,
  libfile-dirlist-perl,
  libfile-homedir-perl,
  libfile-touch-perl,
  libfile-which-perl,
  libipc-run-perl,
  libmoo-perl,
- libswitch-perl,
  libwww-perl,
  patchutils,
  sensible-utils,
diff -Nru devscripts-2.23.2/debian/rules devscripts-2.23.3/debian/rules
--- devscripts-2.23.2/debian/rules	2023-02-10 09:57:47.0 +0100
+++ devscripts-2.23.3/debian/rules	2023-02-27 16:46:00.0 +0100
@@ -14,4 +14,4 @@
 
 override_dh_gencontrol:
 	dh_gencontrol -- $(SUBSTVARS) \
-		-V"devscripts:LongDesc=$$(cat README| awk '/^- annotate-output/,/^  exim script for sorting//'|sed -e '/^[[:space:]]*$$/d' -e 's/^/ /g')"
+		-V"devscripts:LongDesc=$$(cat README | awk '/^- annotate-output/,/^  exim script for sorting/' | sed

Bug#1032991: nmu: scribus_1.5.8+dfsg-4+b3

2023-03-15 Thread Mattia Rizzolo
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: scri...@packages.debian.org
Control: affects -1 + src:scribus

Hello release team,

I'd like to ask you to binNMU scribus to pick up a newer harfbuzz
feature (hurfbuzz-subset) that was added in harfbuzz 6.0.0+dfsg-2, which
landed in unstable last month.

See #1030331

I'm not really planning on making it a mandatory feature (by using a
versioned build-dep), but I figured I'd have scribus built with this
newever feature before bookworm release, given that a random rebuild
during a point release later would trigger this new dependency, etc.

nmu scribus_1.5.8+dfsg-4+b3 . ANY . unstable . -m "Rebuild against newer 
hurfbuzz to pick up hurfbuzz-subset."


Thank you for considering.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#1016374: bullseye-pu: twitter-bootstrap4/4.5.2+dfsg1-8~deb11u1

2022-07-30 Thread Mattia Rizzolo
Package: release.debian.org
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

Dear SRM,

See attached a debdiff that I just uploaded so to fix
https://bugs.debian.org/991939 in stable.

This is a plain backport of the bugfix-only -8 revision, leading to a
.deb that is pretty much identical to the -8 .deb; compared to the -7
currently in stable it's only adding the missing file.

-- 
regards,
Mattia Rizzolo

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

 changelog |   13 +
 rules |1 +
 2 files changed, 14 insertions(+)

diff -Nru twitter-bootstrap4-4.5.2+dfsg1/debian/changelog 
twitter-bootstrap4-4.5.2+dfsg1/debian/changelog
--- twitter-bootstrap4-4.5.2+dfsg1/debian/changelog 2021-07-30 
06:53:34.0 +0200
+++ twitter-bootstrap4-4.5.2+dfsg1/debian/changelog 2022-07-30 
15:39:25.0 +0200
@@ -1,3 +1,16 @@
+twitter-bootstrap4 (4.5.2+dfsg1-8~deb11u1) bullseye; urgency=medium
+
+  * Team upload.
+  * Backport the fix for #991939 to bullseye.
+
+ -- Mattia Rizzolo   Sat, 30 Jul 2022 15:39:25 +0200
+
+twitter-bootstrap4 (4.5.2+dfsg1-8) unstable; urgency=medium
+
+  * Add missing .map files (Closes: #991939)
+
+ -- Yadd   Sat, 07 Aug 2021 07:07:47 +0200
+
 twitter-bootstrap4 (4.5.2+dfsg1-7) unstable; urgency=medium
 
   [ Pirate Praveen ]
diff -Nru twitter-bootstrap4-4.5.2+dfsg1/debian/rules 
twitter-bootstrap4-4.5.2+dfsg1/debian/rules
--- twitter-bootstrap4-4.5.2+dfsg1/debian/rules 2021-07-30 06:53:34.0 
+0200
+++ twitter-bootstrap4-4.5.2+dfsg1/debian/rules 2022-07-30 15:39:11.0 
+0200
@@ -12,6 +12,7 @@
sassc --sourcemap=auto scss/bootstrap-reboot.scss 
dist/tmp/bootstrap-reboot.css
node debian/postcss.js
cp -v dist/tmp/*.css dist/css/
+   cp -v dist/tmp/*.css.map dist/css/
sassc --sourcemap=auto --style compressed dist/tmp/bootstrap.css 
dist/css/bootstrap.min.css
sassc --sourcemap=auto --style compressed dist/tmp/bootstrap-grid.css 
dist/css/bootstrap-grid.min.css
sassc --sourcemap=auto --style compressed dist/tmp/bootstrap-reboot.css 
dist/css/bootstrap-reboot.min.css


signature.asc
Description: PGP signature


Bug#1010607: transition: libpodofo

2022-05-06 Thread Mattia Rizzolo
On Fri, May 06, 2022 at 12:42:30AM +0200, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> 
> On 2022-05-05 13:29:43 +0200, Mattia Rizzolo wrote:
> > Package: release.debian.org
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > Forwarded: https://release.debian.org/transitions/html/auto-libpodofo.html
> > 
> > Please schedule a transition for libpodofo.
> > 
> > I test-built all of the reverse deps (calibre, gimagereader,
> > horizon-eda, krename, scribus) and they all build.
> 
> Please go ahead

Thank you, uploaded!

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#1010607: transition: libpodofo

2022-05-05 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
Forwarded: https://release.debian.org/transitions/html/auto-libpodofo.html

Please schedule a transition for libpodofo.

I test-built all of the reverse deps (calibre, gimagereader,
horizon-eda, krename, scribus) and they all build.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#1010037: bullseye-pu: package hexchat/2.14.3-6

2022-04-22 Thread Mattia Rizzolo
Package: release.debian.org
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu


[ Reason ]
Missing dependency on the python3 extension package.

I added this dependency some time ago, but only in bookworm, didn't
really thing of bullseye.

[ Impact ]
In a simple installation where this dependency is not available, trying
to load the python extensions leads to this traceback on the console,
and the ui just doesn't consider the python3 extension available.

|% hexchat
|Failed to initialize the Python-CFFI embedding logic:
|
|Traceback (most recent call last):
|  File "", line 1007, in _find_and_load
|  File "", line 984, in _find_and_load_unlocked
|ModuleNotFoundError: No module named '_cffi_backend'
|
|From: _hexchat_embedded
|compiled with cffi version: 1.14.5
|_cffi_backend module: not loaded
|sys.path: ['/usr/lib/python39.zip', '/usr/lib/python3.9', 
'/usr/lib/python3.9/lib-dynload']
|
|function _hexchat_embedded._on_plugin_init() called, but initialization code 
failed.  Returning 0.

This has also been reported via IRC on the upstream channel.

[ Tests ]
No automatic tests, trivial to manual check.

[ Risks ]
Nothing interesting, just an extra dep, no risks at all.

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



I already uploaded the package.

-- 
regards,
        Mattia Rizzolo

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

 changelog |7 +++
 control   |1 +
 2 files changed, 8 insertions(+)

diff -Nru hexchat-2.14.3/debian/changelog hexchat-2.14.3/debian/changelog
--- hexchat-2.14.3/debian/changelog 2021-05-26 14:55:10.0 +0200
+++ hexchat-2.14.3/debian/changelog 2022-04-22 21:40:55.0 +0200
@@ -1,3 +1,10 @@
+hexchat (2.14.3-6+deb11u1) bullseye; urgency=medium
+
+  * hexchat-python3: Add missing dependency on python3-cffi-backend.
+Closes: #1009877
+
+ -- Mattia Rizzolo   Fri, 22 Apr 2022 21:40:55 +0200
+
 hexchat (2.14.3-6) unstable; urgency=medium
 
   * Add Recommends:ca-certificates.
diff -Nru hexchat-2.14.3/debian/control hexchat-2.14.3/debian/control
--- hexchat-2.14.3/debian/control   2021-05-26 14:54:00.0 +0200
+++ hexchat-2.14.3/debian/control   2022-04-22 21:39:07.0 +0200
@@ -81,6 +81,7 @@
 Architecture: any
 Multi-Arch: same
 Depends:
+ python3-cffi-backend,
  ${misc:Depends},
  ${shlibs:Depends},
 Recommends:


signature.asc
Description: PGP signature


Re: discover is marked for autoremoval from testing

2022-01-11 Thread Mattia Rizzolo
On Tue, Jan 11, 2022 at 05:00:59PM +0100, Diederik de Haas wrote:
> *) https://tracker.debian.org/pkg/discover also (still) shows it as a high 
> priority problem, while the problem is already fixed/addressed.
> As I've seen it on t.d.o quite a lot of times, it's either a problem in 
> tracker or whatever feeds the data which renders the tracker page.

It's not "fixed" yet. It's a relevant status until the package migrates
to testing, which might or might not happen until it actually happens.
-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-11 Thread Mattia Rizzolo
On Mon, Jan 10, 2022 at 02:21:48PM -0500, Andres Salomon wrote:
> On 1/10/22 05:01, Mattia Rizzolo wrote:
> > On Sun, Jan 09, 2022 at 11:23:20PM -0500, Andres Salomon wrote:
> > > Btw, https://salsa.debian.org/dilinger/chromium/-/tree/stable is my branch
> > > with cleaned-up commits. That's what I'll use for the NMU, which I'm
> > > preparing now.
> > If you all agree, you could finalize the tree, then I'll build again,
> > after which I could sponsor this after a couple days of testing.
> > 
> > I see that you changed debian/copyright compared to the one I used in my
> > build here, so I'll export the orig tarball again.  (normally with
> > Michel we'd share the sha256 of one's produced tarball to check we are
> > building with the same thing, so please share yours?)
> 
> 
> Thank you so much for testing! The sha256 that I have is
> cca093107bf6991b4777889012646455f8e520b446c9f27250653f98ed4bb7e0

Cool, this matches with the new tarball I produced.

Guess I'll restart a build with the stable branch now then.


BTW, my current build (from the v97 branch), just crashed on me.  Not
sure where, and I couldn't quickly reproduce it either; I was just
clicking ont he "extension bar", but I'm not even sure what I was
doing..  just saying :)

> I don't need a sponsor (I'm a developer), but thank you for the offer.

Ah!
Apologies!  I didn't look your name up, and I just assumed so from the
n...@debian.org address.  Well, happy then, less "work" for me :D

> Btw, hopefully Michael is just currently busy and is still interested in
> working on chromium?

I ralized that riku retaired formally last month (indeed, please drop
him from Uploaders, I also opened a bug (as MIA team) against chromium
last month).
About Micheal, that's unclear to me: he stated less than one year ago
that he would keep working on chromium, but he really is not answering
to anybody... so well, even if he is still interested, in a case as big
as chromium I think you really needs to show consideration and be at
least reachable.  Though it might just be my own opinion.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-10 Thread Mattia Rizzolo
On Sun, Jan 09, 2022 at 11:23:20PM -0500, Andres Salomon wrote:
> Btw, https://salsa.debian.org/dilinger/chromium/-/tree/stable is my branch
> with cleaned-up commits. That's what I'll use for the NMU, which I'm
> preparing now.

If you all agree, you could finalize the tree, then I'll build again,
after which I could sponsor this after a couple days of testing.

I see that you changed debian/copyright compared to the one I used in my
build here, so I'll export the orig tarball again.  (normally with
Michel we'd share the sha256 of one's produced tarball to check we are
building with the same thing, so please share yours?)


Regarding the git repository/team on salsa.  What would you all think
about asking the salsa admins to bypass the team admins (gilbert and
riku) that have been silent all this time?
When Micheal started taking over, I didn't want to be too involved so I
didn't ask to be added to team together with him, but I suppose I got
sucked in by this matter a bit too much.
Otherwise I wonder about simply creating a new repository under debian/.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-10 Thread Mattia Rizzolo
On Sun, Jan 09, 2022 at 12:56:28AM -0500, Andres Salomon wrote:
> 
> On 1/8/22 15:57, Mattia Rizzolo wrote:
> > On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote:
> > > If you want to try with chromium 97; it now builds as an official build, 
> > > so
> > > those DCHECKs shouldn't even be compiled in. It also supports wayland
> > > automatically, in case that's related to your slowdowns.
> > > 
> > > https://salsa.debian.org/dilinger/chromium/-/tree/v97
> > I wanted to do this, but could it be that this version is for some
> > reason taking much more space than the previous one?  Here I have ~40 GB
> > free, and v96 built just fine (though I wasn't looking when it was
> > running), but now this failed already twice due to ENSPC.
> > 
> > I'll try looking for someplace more spacy but it's odd :)
> > 
> 
> Yeah, I think it's the debugging info; it's also breaking lld. It's a result
> of enabling official build, I'm working on it.

I see.

Well, it took me longer than I would have liked, but I finally got a
build out of that v97 branch (commit
2c2685aee67a677c85dd752aea08a7e571312116).

This one looks fully functional, gmail is as reactive as it used to be
(u.U after a few days with v96 and that slowness, now it feels so much
better lol) in the past, and after ~15 minutes of random usage it hasn't
crashed on me yet! \o/


It also fixed a problem I had with v93 where document google sheets
would look totally blank... so double happy now!

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-08 Thread Mattia Rizzolo
On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote:
> If you want to try with chromium 97; it now builds as an official build, so
> those DCHECKs shouldn't even be compiled in. It also supports wayland
> automatically, in case that's related to your slowdowns.
> 
> https://salsa.debian.org/dilinger/chromium/-/tree/v97

I wanted to do this, but could it be that this version is for some
reason taking much more space than the previous one?  Here I have ~40 GB
free, and v96 built just fine (though I wasn't looking when it was
running), but now this failed already twice due to ENSPC.

I'll try looking for someplace more spacy but it's odd :)

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-07 Thread Mattia Rizzolo
On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote:
> If you want to try with chromium 97; it now builds as an official build, so
> those DCHECKs shouldn't even be compiled in. It also supports wayland
> automatically, in case that's related to your slowdowns.
> 
> https://salsa.debian.org/dilinger/chromium/-/tree/v97

Thank you, let's try with this.

I've just started the build! :)


Also thanks for handling the py2 thing, however you should be aware that
build-depending on python-is-python3 is also not allowed :3
(however I personally prefer that than to have to inject an old binary..)

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-05 Thread Mattia Rizzolo
On Wed, Jan 05, 2022 at 01:52:33PM +0100, Mattia Rizzolo wrote:
> I suppose I'll see how it goes in the coming few days.

So it's not crashing but it's being unbearably slow in gmail, to the
point that I just wasn't able to type a mail there, while throwing one
CPU core to 100%.
Also it was kind go generally slow in several other sites, compared to
v93.  Always compared to v93, it takes far longer (and by far much much
more CPU) to reopen the whole session (I keep ~50 tabs in 3 windows open
all the time, trusting the browser to reopen them where I left when I
close it).

I didn't mesure anything and I don't have any numbers to share, but
that's what I see.


At least, it looks like it has not been leaking as much memory as v93
was (that in this regard was buggier than v90).

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-05 Thread Mattia Rizzolo
On Tue, Jan 04, 2022 at 06:46:46PM -0500, Andres Salomon wrote:
> On 1/4/22 15:15, Mattia Rizzolo wrote:
> > On Tue, Jan 04, 2022 at 02:50:20PM -0500, Andres Salomon wrote:
> > > I pushed a commit to the skip-a11y-checks branch, please give that a try. 
> > > I
> > > need to take a look at other distributions that are shipping chromium to 
> > > see
> > > if they're just disabling DCHECKs outright, or what.
> 
> Just took a look at fedora, arch, and ungoogle-chromium debian packaging.
> They're all setting is_official_build=true, which completely disables those
> DCHECKs. We should probably set it like that as well, although the
> dcheck_is_configurable=true thing that I added to the skip-a11y-checks
> branch should at least allow the DCHECKs to not be fatal - so there's no
> need to restart your build.


So, this one at least didn't crash on me as soon as I started.
Also, it looks like the saved passwords that went away came back, so I
reckon perhaps the local storage format changed in the upgrade, so v93
wasn't able to see them anymore, or something similar.

I suppose I'll see how it goes in the coming few days.


Thank you for your work!

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-04 Thread Mattia Rizzolo
On Tue, Jan 04, 2022 at 02:50:20PM -0500, Andres Salomon wrote:
> Okay, that's funny - appears to be a fatal error due to being run under gdb.

Well, it was also crashing outside of gdb ^^

> I pushed a commit to the skip-a11y-checks branch, please give that a try. I
> need to take a look at other distributions that are shipping chromium to see
> if they're just disabling DCHECKs outright, or what.

build started...

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-04 Thread Mattia Rizzolo
)]
 Cannot use V8 Proxy resolver in single process mode.
[413:413:0104/174404.300230:FATAL:render_process_host_impl.cc(4227)] 
Check failed: host->GetBrowserContext() == browser_context (0x645f47d0 vs. 
0x658dcb30) Single-process mode does not support multiple browser contexts.

Thread 1 "chromium" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
49  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#1  0x74653536 in __GI_abort () at abort.c:79
#2  0x5d79e9e5 in base::debug::BreakDebuggerAsyncSafe() ()
#3  0x5d6ea9f4 in logging::LogMessage::~LogMessage() ()
#4  0x5d6eaffe in logging::LogMessage::~LogMessage() ()
#5  0x5aba348a in 
content::RenderProcessHostImpl::IsSuitableHost(content::RenderProcessHost*, 
content::IsolationContext const&, content::SiteInfo const&) ()
#6  0x5aba4733 in 
content::RenderProcessHostImpl::GetExistingProcessHost(content::SiteInstanceImpl*)
 ()
#7  0x5aba5b71 in 
content::RenderProcessHostImpl::GetProcessHostForSiteInstance(content::SiteInstanceImpl*)
 ()
#8  0x5acb37dc in content::SiteInstanceImpl::GetProcess() ()
#9  0x5ab7b3c4 in 
content::RenderFrameHostManager::CreateRenderFrameHost(content::RenderFrameHostManager::CreateFrameCase,
 content::SiteInstance*, int, 
mojo::PendingAssociatedRemote, 
base::TokenType const&, bool) ()
#10 0x5ab7b235 in 
content::RenderFrameHostManager::InitRoot(content::SiteInstance*, bool) ()
#11 0x5aa4d59e in content::FrameTree::Init(content::SiteInstance*, 
bool, std::__cxx11::basic_string, 
std::allocator > const&)
()
#12 0x5ad1a896 in 
content::WebContentsImpl::Init(content::WebContents::CreateParams const&) ()
#13 0x5ad0cbb1 in 
content::WebContentsImpl::CreateWithOpener(content::WebContents::CreateParams 
const&, content::RenderFrameHostImpl*) ()
#14 0x5ad0c8b1 in 
content::WebContents::Create(content::WebContents::CreateParams const&) ()
#15 0x608c633b in ProfilePickerView::Init(Profile*) ()
#16 0x608c61f0 in ProfilePickerView::OnSystemProfileCreated(Profile*, 
Profile::CreateStatus) ()
#17 0x5a62fec0 in 
base::internal::Invoker, std::allocator > const&, 
web_app::InstallResultCode), base::WeakPtr >, 
void (std::__cxx11::basic_string, 
std::allocator > const&, 
web_app::InstallResultCode)>::RunOnce(base::internal::BindStateBase*, 
std::__cxx11::basic_string, std::allocator > 
const&, web_app::InstallResultCode) ()
#18 0x5d399bcb in ProfileManager::CreateProfileAsync(base::FilePath 
const&, base::RepeatingCallback const&) 
()
#19 0x608c4442 in ProfilePickerView::Display(ProfilePicker::EntryPoint) 
()
#20 0x6076c476 in 
StartupBrowserCreator::LaunchBrowserForLastProfiles(base::CommandLine const&, 
base::FilePath const&, bool, Profile*, std::vector > const&) ()
#21 0x6076df14 in 
StartupBrowserCreator::ContinueProcessingCommandLineAfterEarlyWebAppCheck(base::CommandLine
 const&, base::FilePath const&, Profile*, bool, Profile*, std::vector > const&) ()
#22 0x6076bcd8 in 
StartupBrowserCreator::ProcessCmdLineImpl(base::CommandLine const&, 
base::FilePath const&, bool, Profile*, std::vector > const&) ()
#23 0x6076ae30 in StartupBrowserCreator::Start(base::CommandLine 
const&, base::FilePath const&, Profile*, std::vector > const&) ()
#24 0x5d1b86ef in ChromeBrowserMainParts::PreMainMessageLoopRunImpl() ()
#25 0x5d1b7ea8 in ChromeBrowserMainParts::PreMainMessageLoopRun() ()
#26 0x5a6b6ddc in content::BrowserMainLoop::PreMainMessageLoopRun() ()
#27 0x5acd2c36 in content::StartupTaskRunner::RunAllTasksNow() ()
#28 0x5a6b69ca in content::BrowserMainLoop::CreateStartupTasks() ()
#29 0x5a6b9598 in 
content::BrowserMainRunnerImpl::Initialize(content::MainFunctionParams const&) 
()
#30 0x5a6b4e22 in content::BrowserMain(content::MainFunctionParams 
const&) ()
#31 0x5d176f7d in 
content::ContentMainRunnerImpl::RunBrowser(content::MainFunctionParams&, bool) 
()
#32 0x5d1768df in content::ContentMainRunnerImpl::Run(bool) ()
#33 0x5d17419a in content::RunContentProcess(content::ContentMainParams 
const&, content::ContentMainRunner*) ()
#34 0x5d174a8b in content::ContentMain(content::ContentMainParams 
const&) ()
#35 0x555558e0d721 in ChromeMain ()
#36 0x746547ed in __libc_start_main (main=0x58e0d5f0 , 
argc=11, argv=0x7fffdd38, init=, fini=, 
rtld_fini=, stack_end=0x7fffdd28) at 
../csu/libc-start.c:332
#37 0x58e0d52a in _start ()


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-03 Thread Mattia Rizzolo
On Mon, Jan 03, 2022 at 01:39:21PM +0100, Mattia Rizzolo wrote:
> On Sun, Jan 02, 2022 at 06:53:52PM +0100, Mattia Rizzolo wrote:
> > > > the v96 branch of https://salsa.debian.org/dilinger/chromium
> > 
> > FWIW, I'm trying to build it myself as well
> 
> Here it started chrashing as soon as I tried to open a new tab, and
> after that it refuses to load my main profile (but it loads others).

After rolling back, it seems to have nuked all of the saved passwords
and login information I had (I don't know if this is only an effect of
the rollback and they are actually there somewhere), as well as all
cookies.


-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-03 Thread Mattia Rizzolo
On Sun, Jan 02, 2022 at 06:53:52PM +0100, Mattia Rizzolo wrote:
> > > the v96 branch of https://salsa.debian.org/dilinger/chromium
> 
> FWIW, I'm trying to build it myself as well

Here it started chrashing as soon as I tried to open a new tab, and
after that it refuses to load my main profile (but it loads others).


Here is what it prints on the console:

mattia@warren /tmp % chromium
[3249439:3249439:0103/133254.120313:ERROR:power_monitor_device_source_stub.cc(11)]
 Not implemented reached in virtual bool 
base::PowerMonitorDeviceSource::IsOnBatteryPower()
[3249485:3249485:0103/133254.419923:ERROR:gpu_init.cc(457)] Passthrough is not 
supported, GL is desktop, ANGLE is
[3249485:3249485:0103/133254.445016:ERROR:sandbox_linux.cc(376)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[3249439:3249468:0103/133258.019370:ERROR:chrome_browser_main_extra_parts_metrics.cc(226)]
 crbug.com/1216328: Checking Bluetooth availability started. Please report if 
there is no report that this ends.
[3249439:3249468:0103/133258.020176:ERROR:chrome_browser_main_extra_parts_metrics.cc(229)]
 crbug.com/1216328: Checking Bluetooth availability ended.
[3249439:3249468:0103/133258.020199:ERROR:chrome_browser_main_extra_parts_metrics.cc(232)]
 crbug.com/1216328: Checking default browser status started. Please report if 
there is no report that this ends.
[3249439:3249468:0103/133258.284415:ERROR:chrome_browser_main_extra_parts_metrics.cc(236)]
 crbug.com/1216328: Checking default browser status ended.
[3249439:3249439:0103/133259.591406:FATAL:accessibility_paint_checks.cc(60)] 
Check failed: node_data.GetNameFrom() == 
ax::mojom::NameFrom::kAttributeExplicitlyEmpty (kAttribute vs. 
kAttributeExplicitlyEmpty) 0x55c6fb7c92d0: BookmarkButton is focusable but has 
no accessible name or placeholder, and is not explicitly marked as empty.
BrowserRootView -> NonClientView -> OpaqueBrowserFrameView -> BrowserView -> 
TopContainerView -> BookmarkBarView -> BookmarkButton
#0 0x55c6ef3a2d79 (/usr/lib/chromium/chromium+0x824bd78)
#1 0x55c6ef2d2353 (/usr/lib/chromium/chromium+0x817b352)
#2 0x55c6ef2ed596 (/usr/lib/chromium/chromium+0x8196595)
#3 0x55c6ef2edffe (/usr/lib/chromium/chromium+0x8196ffd)
#4 0x55c6f1fd483a (/usr/lib/chromium/chromium+0xae7d839)
#5 0x55c6f1fc7e92 (/usr/lib/chromium/chromium+0xae70e91)
#6 0x55c6f1fcb985 (/usr/lib/chromium/chromium+0xae74984)
#7 0x55c6f1fcb7a8 (/usr/lib/chromium/chromium+0xae747a7)
#8 0x55c6f25a21bc (/usr/lib/chromium/chromium+0xb44b1bb)
#9 0x55c6f1fc86ec (/usr/lib/chromium/chromium+0xae716eb)
#10 0x55c6f1fcc72c (/usr/lib/chromium/chromium+0xae7572b)
#11 0x55c6f0a59f58 (/usr/lib/chromium/chromium+0x9902f57)
#12 0x55c6f05f0b71 (/usr/lib/chromium/chromium+0x9499b70)
#13 0x55c6f063ef56 (/usr/lib/chromium/chromium+0x94e7f55)
#14 0x55c6f063e891 (/usr/lib/chromium/chromium+0x94e7890)
#15 0x55c6f0704e02 (/usr/lib/chromium/chromium+0x95ade01)
#16 0x55c6f0705928 (/usr/lib/chromium/chromium+0x95ae927)
#17 0x55c6eeead34a (/usr/lib/chromium/chromium+0x7d56349)
#18 0x55c6ef3421cd (/usr/lib/chromium/chromium+0x81eb1cc)
#19 0x55c6ef3632d6 (/usr/lib/chromium/chromium+0x820c2d5)
#20 0x55c6ef362a88 (/usr/lib/chromium/chromium+0x820ba87)
#21 0x55c6ef363892 (/usr/lib/chromium/chromium+0x820c891)
#22 0x55c6ef2f655f (/usr/lib/chromium/chromium+0x819f55e)
#23 0x55c6ef363e28 (/usr/lib/chromium/chromium+0x820ce27)
#24 0x55c6ef322a15 (/usr/lib/chromium/chromium+0x81cba14)
#25 0x55c6ec2baa33 (/usr/lib/chromium/chromium+0x5163a32)
#26 0x55c6ec2bc9de (/usr/lib/chromium/chromium+0x51659dd)
#27 0x55c6ec2b7e32 (/usr/lib/chromium/chromium+0x5160e31)
#28 0x55c6eed79f7d (/usr/lib/chromium/chromium+0x7c22f7c)
#29 0x55c6eed798df (/usr/lib/chromium/chromium+0x7c228de)
#30 0x55c6eed7719a (/usr/lib/chromium/chromium+0x7c20199)
#31 0x55c6eed77a8b (/usr/lib/chromium/chromium+0x7c20a8a)
#32 0x55c6eaa10721 ChromeMain
#33 0x7f7cbdfd17ed __libc_start_main
#34 0x55c6eaa1052a _start
Task trace:
#0 0x55c6f0705676 (/usr/lib/chromium/chromium+0x95ae675)
#1 0x55c6ef58b1c0 (/usr/lib/chromium/chromium+0x84341bf)
#2 0x55c6ef5b62dc (/usr/lib/chromium/chromium+0x845f2db)
IPC message handler context: 0xB99CF134
Crash keys:
  "total-discardable-memory-allocated" = "8388608"
  "gpu-gl-renderer" = "Mesa Intel(R) HD Graphics 520 (SKL GT2)"
  "gpu-gl-vendor" = "Intel"
  "gpu-generation-intel" = "9"
  "gpu-vsver" = "4.60"
  "gpu-psver" = "4.60"
  "gpu-driver" = "21.2.6"
  "gpu-devid" = "0x1916"
  "gpu-venid" = "0x8086"
  "ui_scheduler_async_stack" = "0x55C6F0705676 0x55C6EF58B1C0"
  "extension-1" = "oboonakemofpalcgghocfoadofidjkkk"
  "num-extensions" = "1"
  "switch-12" = "--origin-trial-disabled-features=CaptureHandle"
  "switch-11" = &qu

Re: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-02 Thread Mattia Rizzolo
On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote:
> > I've got 96.0.4664.110 building on both bullseye and sid

Trying it, I see it still build-depends on python-jinja2.  That package
is now gone, so it's not actually buildable in sid anymore.

Correlated, do you know how long do they plan on keeping using python2?
That's plainly unsuitable, it really is not going to last much longer in
debian.

> > the v96 branch of https://salsa.debian.org/dilinger/chromium

FWIW, I'm trying to build it myself as well (after injecting an old
python-jinja2 and an old python-markupsafe).

> Alright, crashes are solved and the packages are now usable. After some
> cleanups (listing CVEs in changelogs,

This doesn't seem to be done as of the current tip of you v96 branch.

> merging/pushing a bunch of
> commits in my branch, possibly dropping strong stack protection from
> builds to silence warnings from older clang versions, and going through
> lintian errors/warnings), it should be ready to upload.

TBH, I don't think I am able to judge the appropriateness of most of
those changes...
Though I suspect I could close most of my eyes and upload it to
unstable: can't be much worse than what we have...

> How should I handle this? NMU to sid, let people try it out, and then
> deal with buster/bullseye? Upload everything all at once?

Procedure would be NMU to unstable first, IMHO.

> I also haven't heard from anyone on the chromium team yet - should I
> add myself as an uploader and do a normal (non-NMU) upload? Do any of
> them care?

Without hearing from them, adding yourself to Uploaders would be
inappropriate.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

2021-12-06 Thread Mattia Rizzolo
On Mon, Dec 06, 2021 at 08:53:37PM +0100, Paul Gevers wrote:
> I have good experience with some of my upstreams where they supported me by
> adapting their build system to enable building without the bundled/vendored
> dependencies. Has this been tried? Would it be worth pursuing?

It has been, yes.

I was looking when Micheal reported a few bugs (after my prodding) to
get a few build issues solved (actual FTBFS when building with specific
build flags).  Even those bug reports were completely ignored with no
answer whatsoever; the patches also ignored.

I'm led to believe the chromium team is not really playing with the
community at all, rather they are just following their internal bug
tracker instead.
Likewise, they are obviously not interested in supporting anything that
is not the official Google Chrome build (if it can even said they are
"supoprting" that).

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-12-06 Thread Mattia Rizzolo
Hi Dirk,

On Mon, Dec 06, 2021 at 03:15:22PM -0600, Dirk Eddelbuettel wrote:
> | Instead of doing that, this could also be solved with a build profile.
> | See https://wiki.debian.org/BuildProfileSpec and the attached patch. See
> | also gtk4 and libgtk-4-media-ffmpeg for an example.
> 
> I can apply the patch, that is easy enough.
> 
> The angle in debian/control in 'Build-Profiles: ' are on
> purpose? Odd syntaxt.  Anyway, will give it a whirl in a bit.

Yes!  See https://wiki.debian.org/BuildProfileSpec for the
documentation.

Unfortunately there have been a few troubles getting a formal and good
specifical text that was "good enough" for the Debian Policy.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: chromium: Update to version 94.0.4606.61 (security-fixes)

2021-12-05 Thread Mattia Rizzolo
> Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers:
> > The problem really is lack of maintenance. In my opinion, chromium deserves
> > an active *team* to support it in Debian.
[..]
> > We'll not ship it in bookworm unless we see steady uploads
> > in unstable and we see security uploads in stable.

FWIW, as the person currently sponsoring the (few) uploads thatt happen,
I also approve of this.
I had some hopes for the current "team" (m)ilbert and Michel), but
gilbert's mail even started bouncing, and Micheal became less and less
responsive :(  - I understand it's a complicated package so yes, there
needs to be a real team: I also recommend you require an active (as
gilbert is not) DD in the team that actually maintains chromium (so not
me who just sponsor the uploads).

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#999434: bullseye-pu: package freeipmi/1.6.6-4+deb11u1

2021-11-10 Thread Mattia Rizzolo
On Wed, Nov 10, 2021 at 11:55:03PM +0100, Fabio Fantoni wrote:
>   [x] attach debdiff against the package in (old)stable

Since this is a small likely uncontroversial change, I proceeded to
upload it already.

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: Bug#995928: acorn: doc directory shipped by both binaries

2021-10-12 Thread Mattia Rizzolo
Hi release team,

concerning this bug, I'd like to hear advice from you on how you'd best
like to see this fixed in stable.

The current bug causes trouble for reproducible builds operations
(basically, it throws away all build involving node-acorn in bullseye).

See the last paragraph on my thoughts about the potential solutions; I'm
happy to implement what you think would be best.


On Fri, Oct 08, 2021 at 12:07:36PM +0200, Mattia Rizzolo wrote:
> Source: acorn
> Version: 8.0.5+ds+~cs19.19.27-3
> Severity: serious
> Control: fixed -1 8.5.0+ds+~cs23.9.6-2
> 
> This happens in bullseye:
> 
> root@warren:/# apt install node-acorn
> ...
> The following NEW packages will be installed:
>   libbrotli1 libc-ares2 libicu67 libnghttp2-14 libnode72 libuv1 node-acorn 
> node-debbundle-acorn node-xtend nodejs
> ...
> root@warren:/# apt install --reinstall node-debbundle-acorn
> ...
> (Reading database ... 12963 files and directories currently installed.)
> Preparing to unpack .../node-debbundle-acorn_8.0.5+ds+~cs19.19.27-3_all.deb 
> ...
> Unpacking node-debbundle-acorn (8.0.5+ds+~cs19.19.27-3) over 
> (8.0.5+ds+~cs19.19.27-3) ...
> (Noting disappearance of node-acorn, which has been completely replaced.)
> Setting up node-debbundle-acorn (8.0.5+ds+~cs19.19.27-3) ...
> The following package disappeared from your system as
> all files have been overwritten by other packages:
>   node-acorn
> Note: This is done automatically and on purpose by dpkg.
> 
> 
> This is due to node-acorn shipping /usr/share/doc/node-acorn (type:
> symlink) which is *also* shipping by node-debbundle-acorn (type:
> directory).
> dpkg seems to always overwrite the symlink anyway, but it doesn't detect
> that it's gone until later when reinstalling it.
> 
> 
> To be honest, I'm not sure what was the wanted situation, but I *think*
> the symlink is just wrong.  Looking at the content of the
> /usr/share/doc/node-acorn/ directory as present in node-debbundle-acorn,
> I think that is the appropriate content.  So, probably, the best fix is
> to just get rid of the symlink from node-acorn, however that would leave
> the package totally empty, which dpkg is not totally thrilled about.
> So more likely at least the 2 symlinks of copyright and
> changelog.Debian.gz in /usr/share/doc/node-acorn could be moved from
> node-debbundle-acorn to node-acorn, so effectively shipping the
> directory from both packages.
> 
> 
> 
> This is fixed in 8.5.0+ds+~cs23.9.6-2 by moving everything to node-acorn
> and turning node-debbundle-acorn into a pure transitional package.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#992435: bullseye-pu: devscripts/2.21.3+deb11u1

2021-08-18 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: bullseye

Hi,

attached an update to retarget `dch --bpo` (and `dch --stable`) from
buster to bullseye.
I kind of forgot to push it during the last days of the freeze.

I already uploaded the package.

-- 
regards,
Mattia Rizzolo

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

 .gitlab-ci.yml |   16 ++--
 debian/changelog   |8 
 po4a/po/de.po  |6 +++---
 po4a/po/devscripts.pot |4 ++--
 po4a/po/fr.po  |6 +++---
 po4a/po/pt.po  |6 +++---
 scripts/debchange.1|2 +-
 scripts/debchange.pl   |6 +++---
 test/test_debchange|6 +++---
 9 files changed, 28 insertions(+), 32 deletions(-)

diff -Nru devscripts-2.21.3/debian/changelog devscripts-2.21.3+deb11u1/debian/changelog
--- devscripts-2.21.3/debian/changelog	2021-06-30 15:11:06.0 +0200
+++ devscripts-2.21.3+deb11u1/debian/changelog	2021-08-18 17:02:14.0 +0200
@@ -1,3 +1,11 @@
+devscripts (2.21.3+deb11u1) bullseye; urgency=medium
+
+  [ Mattia Rizzolo ]
+  * debchange:
++ Target bullseye-backports with --bpo.
+
+ -- Mattia Rizzolo   Wed, 18 Aug 2021 17:02:14 +0200
+
 devscripts (2.21.3) unstable; urgency=medium
 
   [ Johannes Schauer Marin Rodrigues ]
diff -Nru devscripts-2.21.3/.gitlab-ci.yml devscripts-2.21.3+deb11u1/.gitlab-ci.yml
--- devscripts-2.21.3/.gitlab-ci.yml	2021-03-16 14:16:39.0 +0100
+++ devscripts-2.21.3+deb11u1/.gitlab-ci.yml	2021-08-18 17:00:29.0 +0200
@@ -11,18 +11,6 @@
 - make test
 - make destructive-test
 
-unstable:
+bullseye:
   <<: *test
-  image: debian:unstable
-
-testing:
-  <<: *test
-  image: debian:testing
-
-stable-bpo:
-  <<: *test
-  image: debian:stable-backports
-
-ubuntu-devel:
-  <<: *test
-  image: ubuntu:devel
+  image: debian:bullseye
diff -Nru devscripts-2.21.3/po4a/po/de.po devscripts-2.21.3+deb11u1/po4a/po/de.po
--- devscripts-2.21.3/po4a/po/de.po	2021-05-02 20:54:46.0 +0200
+++ devscripts-2.21.3+deb11u1/po4a/po/de.po	2021-08-18 17:01:41.0 +0200
@@ -7,7 +7,7 @@
 msgstr ""
 "Project-Id-Version: devscripts 2.18.9\n"
 "Report-Msgid-Bugs-To: devscri...@packages.debian.org\n"
-"POT-Creation-Date: 2021-05-02 20:51+0200\n"
+"POT-Creation-Date: 2021-08-18 17:00+0200\n"
 "PO-Revision-Date: 2020-04-25 23:04+0200\n"
 "Last-Translator: Chris Leick \n"
 "Language-Team: de \n"
@@ -7222,10 +7222,10 @@
 #. type: Plain text
 #: ../scripts/debchange.1:265
 msgid ""
-"Increment the Debian release number for an upload to buster-backports, and "
+"Increment the Debian release number for an upload to bullseye-backports, and "
 "add a backport upload changelog comment."
 msgstr ""
-"erhöht die Debian-Veröffentlichungsnummer für ein Hochladen nach buster-"
+"erhöht die Debian-Veröffentlichungsnummer für ein Hochladen nach bullseye-"
 "backports und fügt einen Changelog-Kommentar »backport upload« hinzu."
 
 #. type: TP
diff -Nru devscripts-2.21.3/po4a/po/devscripts.pot devscripts-2.21.3+deb11u1/po4a/po/devscripts.pot
--- devscripts-2.21.3/po4a/po/devscripts.pot	2021-06-30 15:11:06.0 +0200
+++ devscripts-2.21.3+deb11u1/po4a/po/devscripts.pot	2021-08-18 17:02:14.0 +0200
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-05-02 20:51+0200\n"
+"POT-Creation-Date: 2021-08-18 17:00+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME \n"
 "Language-Team: LANGUAGE \n"
@@ -5799,7 +5799,7 @@
 #. type: Plain text
 #: ../scripts/debchange.1:265
 msgid ""
-"Increment the Debian release number for an upload to buster-backports, and "
+"Increment the Debian release number for an upload to bullseye-backports, and "
 "add a backport upload changelog comment."
 msgstr ""
 
diff -Nru devscripts-2.21.3/po4a/po/fr.po devscripts-2.21.3+deb11u1/po4a/po/fr.po
--- devscripts-2.21.3/po4a/po/fr.po	2021-05-02 20:54:46.0 +0200
+++ devscripts-2.21.3+deb11u1/po4a/po/fr.po	2021-08-18 17:01:05.0 +0200
@@ -14,7 +14,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: devscripts\n"
-"POT-Creation-Date: 2021-05-02 20:51+0200\n"
+"POT-Creation-Date: 2021-08-18 17:00+0200\n"
 "PO-Revision-Date: 2021-05-02 20:52+0200\n"
 "Last-Translator: Xavier Gui

Bug#991239: unblock: django-qr-code/2.2.0-1

2021-07-18 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package django-qr-code

[ Reason ]
New upstream release, targeted release fixing 1 bug.

[ Impact ]
this bug is being fixed: 
https://github.com/dprog-philippe-docourt/django-qr-code/issues/31
with this 2-line diff: 
https://github.com/dprog-philippe-docourt/django-qr-code/commit/f2aee3315d3dbca4e1da72ce5b5ad5ef50c1d01f

The rest of the diff is only doc changes, with no inpact on anything.

[ Tests ]
the commit adds a test, that is run both at build time and autopkgtest.

[ Risks ]
trivial fix, tested, leaf package.  I'd say risk is null.

[ 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 django-qr-code/2.2.0-1

-- 
regards,
Mattia Rizzolo

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

 .travis.yml |2 +-
 CHANGELOG.md|9 +
 README.md   |2 +-
 debian/changelog|6 ++
 qr_code/__init__.py |2 +-
 qr_code/qrcode/utils.py |4 ++--
 qr_code/tests/tests.py  |4 
 requirements-web-deployment.txt |2 +-
 scripts/run-tests.sh|2 +-
 9 files changed, 26 insertions(+), 7 deletions(-)

diff -Nru django-qr-code-2.1.0/CHANGELOG.md django-qr-code-2.2.0/CHANGELOG.md
--- django-qr-code-2.1.0/CHANGELOG.md   2021-01-24 00:38:55.0 +0100
+++ django-qr-code-2.2.0/CHANGELOG.md   2021-06-05 11:30:06.0 +0200
@@ -1,9 +1,18 @@
 # Change Log
 
+## 2.2.0 (2021-06-03)
+* Change encoding from URL-safe Base64 to standard Base64 for `text` query 
argument (used for serving QR code images).
+* Fix #31 by passing the border parameter for segno.QRCode.save.
+* Ensure compatibility with Django 3.2.
+* Drop support for Django 3.0.
+
+
 ## 2.1.0 (2021-01-23)
 * Change encoding from URL-safe Base64 to standard Base64 for `text` query 
argument (used for serving QR code images).
 * Introduce setting `SERVE_QR_CODE_IMAGE_PATH` to configure the path under 
which QR Code images are served.
 * Reorganize and improve documentation.
+* Fix #23
+* Introduce usage of type hints.
 
 ## 2.0.1 (2020-11-24)
 * Update the install_requires after the move from qrcode to Segno.
diff -Nru django-qr-code-2.1.0/debian/changelog 
django-qr-code-2.2.0/debian/changelog
--- django-qr-code-2.1.0/debian/changelog   2021-01-27 19:34:54.0 
+0100
+++ django-qr-code-2.2.0/debian/changelog   2021-07-18 11:45:54.0 
+0200
@@ -1,3 +1,9 @@
+django-qr-code (2.2.0-1) unstable; urgency=medium
+
+  * New upstream version 2.2.0.
+
+ -- Mattia Rizzolo   Sun, 18 Jul 2021 11:45:54 +0200
+
 django-qr-code (2.1.0-1) unstable; urgency=medium
 
   [ Mattia Rizzolo ]
diff -Nru django-qr-code-2.1.0/qr_code/__init__.py 
django-qr-code-2.2.0/qr_code/__init__.py
--- django-qr-code-2.1.0/qr_code/__init__.py2021-01-24 00:38:55.0 
+0100
+++ django-qr-code-2.2.0/qr_code/__init__.py2021-06-05 11:30:06.0 
+0200
@@ -1 +1 @@
-__version__ = '2.1.0'
+__version__ = '2.2.0'
diff -Nru django-qr-code-2.1.0/qr_code/qrcode/utils.py 
django-qr-code-2.2.0/qr_code/qrcode/utils.py
--- django-qr-code-2.1.0/qr_code/qrcode/utils.py2021-01-24 
00:38:55.0 +0100
+++ django-qr-code-2.2.0/qr_code/qrcode/utils.py2021-06-05 
11:30:06.0 +0200
@@ -85,7 +85,7 @@
 :raises: TypeError in case an unknown argument is given.
 """
 self._size = size
-self._border = border
+self._border = int(border)
 if _can_be_cast_to_int(version):
 version = int(version)  # type: ignore
 if not 1 <= version <= 40:
@@ -142,7 +142,7 @@
 :rtype: dict
 """
 image_format = self._image_format
-kw = dict(kind=image_format, scale=self._size_as_int())
+kw = dict(border=self.border, kind=image_format, 
scale=self._size_as_int())
 # Change the color mapping into the keywords Segno expects
 # (remove the "_color" suffix from the module names)
 kw.update({k[:-6]: v for k, v in self.color_mapping().items()})
diff -Nru django-qr-code-2.1.0/qr_code/tests/tests.py 
django-qr-code-2.2.0/qr_code/tests/tests.py
--- django-qr-code-2.1.0/qr_code/tests/tests.py 2021-01-24 00:38:55.0 
+0100
+++ django-qr-code-2.2.0/qr_code/tests/tests.py 2021-06-05 11:30:06.0 
+0200
@@ -94,6 +94,10 @@
 options = QRCodeOptions(image_format='invalid-image-format')
 self.assertEqual(options.

Bug#990551: unblock: devscripts/2.21.3

2021-07-01 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package devscripts/2.21.3.

[ Reason ]
There was a bug in the makefile, which made `debbisect` completely
broken.
Apologize, as I knew of the brokeness for quite some time, but I totally
forgot to merge the fixing patch and release :(

The diff is minimal, with only that fix plus another trivial change also
fixig things.

[ Impact ]
`debbisect` just won't work at all.

[ Tests ]
There is no automated test covering that part, but also josch confirmed
it's fixed now :P
Plus, looking at a binary diff is self-explanatory…

[ Risks ]
no unrelated risks besides the bit being fixed.

[ 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 devscripts/2.21.3

-- 
regards,
Mattia Rizzolo

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

 debian/changelog   |   10 ++
 debian/copyright   |6 +++---
 scripts/Makefile   |1 +
 scripts/build-rdeps.pl |2 +-
 scripts/debbisect  |9 ++---
 scripts/debrebuild.pl  |2 +-
 scripts/run_bisect.sh  |2 +-
 scripts/run_bisect_qemu.sh |2 +-
 8 files changed, 24 insertions(+), 10 deletions(-)

diff -Nru devscripts-2.21.2/debian/changelog devscripts-2.21.3/debian/changelog
--- devscripts-2.21.2/debian/changelog	2021-05-02 20:57:28.0 +0200
+++ devscripts-2.21.3/debian/changelog	2021-06-30 15:11:06.0 +0200
@@ -1,3 +1,13 @@
+devscripts (2.21.3) unstable; urgency=medium
+
+  [ Johannes Schauer Marin Rodrigues ]
+  * "Update" my name in the copyright claims.  MR: !230
+  * debbisect:  MR: !229
++ Fix installation of helper scripts.
++ Improve the HTTP proxy handling of 200 and 404.
+
+ -- Mattia Rizzolo   Wed, 30 Jun 2021 15:11:06 +0200
+
 devscripts (2.21.2) unstable; urgency=medium
 
   [ Mattia Rizzolo ]
diff -Nru devscripts-2.21.2/debian/copyright devscripts-2.21.3/debian/copyright
--- devscripts-2.21.2/debian/copyright	2021-03-16 14:16:39.0 +0100
+++ devscripts-2.21.3/debian/copyright	2021-05-30 19:55:29.0 +0200
@@ -103,7 +103,7 @@
 
 Files: scripts/build-rdeps.pl
 Copyright: Patrick Schoenfeld
- 2015, Johannes Schauer 
+ 2015, Johannes Schauer Marin Rodrigues 
  2017, James McCoy 
 License: GPL-2+
 
@@ -312,14 +312,14 @@
  2018, Aran Deltac 
 
 Files: scripts/debrebuild.pl
-Copyright: 2014-2016, Johannes Schauer 
+Copyright: 2014-2016, Johannes Schauer Marin Rodrigues 
2020   Niels Thykier 
 License: Expat
 
 Files: scripts/debbisect
scripts/run_bisect.sh
scripts/run_bisect_qemu.sh
-Copyright: 2014-2020, Johannes Schauer 
+Copyright: 2014-2020, Johannes Schauer Marin Rodrigues 
 License: Expat
 
 Files: scripts/tagpending.pl scripts/transition-check.pl
diff -Nru devscripts-2.21.2/scripts/build-rdeps.pl devscripts-2.21.3/scripts/build-rdeps.pl
--- devscripts-2.21.2/scripts/build-rdeps.pl	2021-03-22 15:56:10.0 +0100
+++ devscripts-2.21.3/scripts/build-rdeps.pl	2021-05-30 19:55:29.0 +0200
@@ -2,7 +2,7 @@
 # -*- tab-width: 4; indent-tabs-mode: t; cperl-indent-level: 4 -*-
 # vim: set ai shiftwidth=4 tabstop=4 expandtab:
 #   Copyright (C) Patrick Schoenfeld
-# 2015 Johannes Schauer 
+# 2015 Johannes Schauer Marin Rodrigues 
 # 2017 James McCoy 
 #
 # This program is free software; you can redistribute it and/or modify
diff -Nru devscripts-2.21.2/scripts/debbisect devscripts-2.21.3/scripts/debbisect
--- devscripts-2.21.2/scripts/debbisect	2021-03-16 14:16:39.0 +0100
+++ devscripts-2.21.3/scripts/debbisect	2021-06-30 15:09:05.0 +0200
@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 #
-# Copyright 2020 Johannes 'josch' Schauer 
+# Copyright 2020 Johannes Schauer Marin Rodrigues 
 #
 # Permission is hereby granted, free of charge, to any person obtaining a copy
 # of this software and associated documentation files (the "Software"), to deal
@@ -161,7 +161,6 @@
 maxtries = 3
 head, _ = os.path.split(path)
 os.makedirs(head, exist_ok=True)
-self.send_response(HTTPStatus.OK)
 totalsize = -1
 downloaded = 0
 for trynum in range(maxtries):
@@ -181,6 +180,7 @@
 ) as out:
 out.seek(downloaded)
 if trynum == 0:
+self.send_response(HTTPStatus.OK)
 self.send_header("Content-type", f.headers["Content-type"])
 self.send_header(&qu

Bug#989257: unblock: kodi/2:19.1+dfsg2-1

2021-06-07 Thread Mattia Rizzolo
Control: tag -1 -moreinfo

On Mon, Jun 07, 2021 at 09:50:07AM +0200, Sebastian Ramacher wrote:
> please go ahead. Remove the moreinfo tag once the new version is
> available in unstable.

Uploaded.

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#988615: unblock: kodi-inputstream-adaptive/2.6.14+ds1-1

2021-06-04 Thread Mattia Rizzolo
Control: tag -1 -moreinfo

On Fri, Jun 04, 2021 at 10:27:13PM +0200, Sebastian Ramacher wrote:
> On 2021-05-30 10:43:01 +, Vasyl Gello wrote:
> > Hi Sebastian!
> > 
> > Please check this pending unblock request as we need it to close #988862.
> 
> ACK, please remove the moreinfo tag once the new version is available in
> unstable.

Uploaded.

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#988611: unblock: kodi/2:19.1+dfsg1-1

2021-05-30 Thread Mattia Rizzolo
Control: tag -1 -moreinfo

On Sun, May 30, 2021 at 04:10:02PM +0200, Sebastian Ramacher wrote:
> On 2021-05-30 09:25:27 +, Vasyl Gello wrote:
> > I prepared 2:19.0+dfsg1-2 fixing only bugs reported to Debian.
> > Debdiff against 2:19.0+dfsg1-1 attached.
> 
> ACK, please remove the moreinfo tag once that version is available in
> unstable.

Uploaded.
Please also consider aging a bit the upload, so that we can talk about
#989257 while there are still chances to get it in before the bullseye
release...

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#989257: unblock: kodi/2:19.1+dfsg2-1

2021-05-30 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: Vasyl Gello 
Control: submitter -1 Vasyl Gello 

Following #988611, I'm opening a new unblock bug to discuss the proposed
update of src:kodi to the 19.1 point release.

Here, I'm forwarding the message that Vasyl already sent to the
previous bug.

> I also prepared (but have not uploaded to Salsa yet) the 2:19.1+dfsg2-1 that 
> uses
> the same embedded copies that were used in 2:19.0+dfsg1-1 that is currently in
> bullseye.
> 
> Filtered diff from 2:19.0+dfsg1-2 to 2:19.1+dfsg2-1 is attached with the 
> following
> filtrdiff options:
> 
> filterdiff kodi_19.0+dfsg1-2_19.1+dfsg2-1.diff \
> -x "*/addons/*.xml" \
> -x "*/cmake/scripts/windows/*" \
> -x "*/docs/*" \
> -x "*/Changelog" \
> -x "*/Makefile.in" \
> -x "*/*.m4" \
> -x "*/configure" \
> -x "*/msvc/*" \
> -x "*/media/*" \
> -x "*/system/*" \
> -x "*/tools/buildsteps/windows/*" \
> -x "*/xbmc/cores/VideoPlayer/VideoRenderers/windows/*" \
> -x "*/xbmc/windowing/win10/*" \
> -x "*/xbmc/windowing/windows/*" \
> 1>kodi_19.0+dfsg1-2_19.1+dfsg2-1.filtered.diff


Also, two other messages to give some context:

On 2021-05-30 16:10:02 +0200, Sebastian Ramacher wrote:
> On 2021-05-30 09:25:27 +, Vasyl Gello wrote:
> > As I wrote in the private message to you earlier this week, I don't want to 
> > take
> > responsibility from the Kodi upstream and cherry-pick only some bugfixes 
> > that might
> > be considered "important" from my PoV. This creates an inconsistent user 
> > experience
> > across vanilla Kodi and Kodi from Debian, plus requires me to spend even 
> > more time
> > carefully testing each combination of cherry-picked commits in addition to 
> > all the
> > time I already spent fixing a lot of stuff upstream and in Debian.
> >
> > The Kodi upstream has an estabilished testing and backport culture, and it 
> > is not that
> > easy to slip a risky change into a stable branch (which 19.x currently is). 
> > Plus all
> > upstream changes must pass CI before getting merged.
> >
> > If it is not possible to have 19.x point (bugfix) releases in bullseye, I 
> > think
> > I will upload next point releases to experimental during the bullseye 
> > freeze,
> > then to bullseye-backports after bookworm development cycle starts. And for 
> > stable
> > branch I will port only CVE fixes and bug fixes reported to Debian.
> 
> I don't think my previous answer implied that the 19.x bugfix release
> is unfit for bullseye. It was an attempt to get some important fixes
> into the release as -2 first, and to then have a look at the
> other changes.
> 
> Unfortunately your descriptions of the changes in kodi (and all the
> plugins) are very terse and only highlight changes that sound like they
> would fit the freeze policy. The other changes -- like the
> reimplementation of kodi's logging which is a few hundred lines if not
> more or newly added features -- are swept under the rug. We do not have
> the time to dig into upstream's decision to include those changes and the
> associated risks. If you as maintainer think that it's worth having
> these changes in bullseye, please help us reviewing the changes by
> explaining why the changes are needed and the potential regressions
> they could introduce.


-- 
regards,
Mattia Rizzolo

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


kodi_19.0+dfsg1-2_19.1+dfsg2-1.filtered.diff.gz
Description: application/gzip


signature.asc
Description: PGP signature


Bug#989135: unblock: hexchat/2.14.3-6

2021-05-26 Thread Mattia Rizzolo
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package hexchat

[ Reason ]
Moving away from Freenode to Libera.chat.

[ Impact ]
Probably little changes for debian, since the default network has been
OFTC for a while, but I still think it's relevant to add Libera.Chat to
the available networks, at the very least.

[ Tests ]
manually tested all the changes.

[ Risks ]
none, probably.

[ 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 ]
It's quite relevant for ubuntu, as you can guess from the diff, but that
part is in a patch that is not built in debian, so…

unblock hexchat/2.14.3-6

-- 
regards,
Mattia Rizzolo

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

 changelog  |   11 
 control|1 
 default_servers/debian |4 -
 default_servers/ubuntu |   15 +++---
 patches/a25f2381689d2c2279a0e43b33f6c0ec8305a096.patch |   20 
 patches/d3545f37cd5f551ed8bc0ab7b20e5c8140adc0a6.patch |   39 +
 patches/series |4 +
 7 files changed, 85 insertions(+), 9 deletions(-)

diff -Nru hexchat-2.14.3/debian/changelog hexchat-2.14.3/debian/changelog
--- hexchat-2.14.3/debian/changelog 2021-01-02 16:31:39.0 +0100
+++ hexchat-2.14.3/debian/changelog 2021-05-26 14:55:10.0 +0200
@@ -1,3 +1,14 @@
+hexchat (2.14.3-6) unstable; urgency=medium
+
+  * Add Recommends:ca-certificates.
+  * Add patches from upstream to add Libera.Chat to the network list.
+  * Adapt default servers patches for the upstream changes.
+  * Ubuntu default server:
++ Change from Freenode to Libera.Chat.
++ Ore-select the "join channel" button, like we do in Debian.
+
+ -- Mattia Rizzolo   Wed, 26 May 2021 14:55:10 +0200
+
 hexchat (2.14.3-5) unstable; urgency=medium
 
   * Bump copyright for 2021.
diff -Nru hexchat-2.14.3/debian/control hexchat-2.14.3/debian/control
--- hexchat-2.14.3/debian/control   2020-12-16 21:56:22.0 +0100
+++ hexchat-2.14.3/debian/control   2021-05-26 14:54:00.0 +0200
@@ -34,6 +34,7 @@
  ${misc:Depends},
  ${shlibs:Depends},
 Recommends:
+ ca-certificates,
  hexchat-perl,
  hexchat-plugins,
  hexchat-python3,
diff -Nru hexchat-2.14.3/debian/default_servers/debian 
hexchat-2.14.3/debian/default_servers/debian
--- hexchat-2.14.3/debian/default_servers/debian2018-12-03 
14:24:00.0 +0100
+++ hexchat-2.14.3/debian/default_servers/debian2021-05-26 
14:23:45.0 +0200
@@ -17,7 +17,7 @@
  {
int i = 0, j = 0;
ircnet *net = NULL;
--  guint def_hash = g_str_hash ("freenode");
+-  guint def_hash = g_str_hash ("Libera.Chat");
 +  guint def_hash = g_str_hash ("OFTC");
  
while (1)
@@ -36,7 +36,7 @@
 +  gtk_entry_set_text (GTK_ENTRY (entry1), "#debian");
 +  gtk_toggle_button_set_active 
(GTK_TOGGLE_BUTTON(radiobutton2), TRUE);
 +  }
-   if (g_ascii_strcasecmp(((ircnet*)serv->network)->name, 
"freenode") == 0)
+   if (g_ascii_strcasecmp(((ircnet*)serv->network)->name, 
"Libera.Chat") == 0)
{
 -  gtk_entry_set_text (GTK_ENTRY (entry1), "#hexchat");
 +  gtk_entry_set_text (GTK_ENTRY (entry1), "#debian");
diff -Nru hexchat-2.14.3/debian/default_servers/ubuntu 
hexchat-2.14.3/debian/default_servers/ubuntu
--- hexchat-2.14.3/debian/default_servers/ubuntu2020-01-02 
09:39:26.0 +0100
+++ hexchat-2.14.3/debian/default_servers/ubuntu2021-05-26 
14:51:19.0 +0200
@@ -17,8 +17,8 @@
/* irc. points to chat. but many users and urls still reference it */
{0, "irc.freenode.net"},
  
-+  {"Ubuntu Servers (freenode)", 0, 0, 0, LOGIN_SASL, 0, TRUE},
-+  {0, "chat.freenode.net"},
++  {"Ubuntu Servers (Libera.Chat)", 0, 0, 0, LOGIN_SASL, 0, TRUE},
++  {0, "irc.libera.chat"},
 +
{"GalaxyNet",   0},
{0, "irc.galaxynet.org"},
@@ -27,8 +27,8 @@
  {
int i = 0, j = 0;
ircnet *net = NULL;
--  guint def_hash = g_str_hash ("

Bug#988619: Acknowledgement (unblock: kodi-pvr-mythtv/7.3.1+ds1-1)

2021-05-25 Thread Mattia Rizzolo
Control: tag -1 -moreinfo

On Sat, May 22, 2021 at 09:22:44AM +0200, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> 
> On 2021-05-18 08:38:47 +, Vasyl Gello wrote:
> > This is a fixup release implementing seek feature.
> 
> Please go ahead and remove the moreinfo tag once the new version is
> available in unstable.

uploaded.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#988622: Acknowledgement (unblock: kodi-pvr-vuplus/7.4.3+ds1-1)

2021-05-19 Thread Mattia Rizzolo
Control: tag -1 -moreinfo

On Wed, May 19, 2021 at 09:02:25PM +0200, Sebastian Ramacher wrote:
> On 2021-05-18 08:51:37 +, Vasyl Gello wrote:
> > This is mostly a code cleanup release fixing memory leaks viewing some 
> > still images.
> 
> Please go ahead and remove the moreinfo tag once the new version is
> available in unstable.

uploaded.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#988620: Acknowledgement (unblock: kodi-pvr-mediaportal-tvserver/8.1.2+ds1-1)

2021-05-19 Thread Mattia Rizzolo
Control: tag -1 -moreinfo

On Wed, May 19, 2021 at 09:05:14PM +0200, Sebastian Ramacher wrote:
> On 2021-05-18 08:46:09 +, Vasyl Gello wrote:
> > This release drops p8-platform dependency (code cleanup) and fixes OOB read 
> > in MultiByteToWideChar.
> 
> The first part was done via patch before that. Please go ahead and
> remove the moreinfo tag once the new version is available in unstable.

uploaded.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#988625: Acknowledgement (unblock: kodi-vfs-libarchive/2.0.1+ds1-1)

2021-05-19 Thread Mattia Rizzolo
Control: tag -1 -moreinfo

On Tue, May 18, 2021 at 09:09:50PM +0200, Sebastian Ramacher wrote:
> On 2021-05-18 09:04:03 +, Vasyl Gello wrote:
> > This is a maintenance release dropping ISO playback support because Kodi 
> > now plays ISO / BD natively to avoid unnecessary heisenbugs.
> 
> Please go ahead and remove the moreinfo tag once the new version is
> available in unstable.

Uploaded.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#988624: Acknowledgement (unblock: kodi-pvr-zattoo/19.7.9+ds1-1)

2021-05-19 Thread Mattia Rizzolo
Control: tag -1 -moreinfo

On Tue, May 18, 2021 at 09:10:53PM +0200, Sebastian Ramacher wrote:
> On 2021-05-18 08:58:05 +, Vasyl Gello wrote:
> > Thos paych release fixes handling of a changed EPG format returned by 
> > Zattoo OTT provider.
> 
> Please go ahead and remove the moreinfo tag once the new version is
> available in unstable.

Uploaded.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#988621: Acknowledgement (unblock: kodi-pvr-nextpvr/8.2.3+ds1-1)

2021-05-19 Thread Mattia Rizzolo
Control: tag -1 - moreinfo

On Tue, May 18, 2021 at 09:13:32PM +0200, Sebastian Ramacher wrote:
> On 2021-05-18 08:49:03 +, Vasyl Gello wrote:
> > This release adds missing "break" statement (bugfix) and re-adds recording 
> > directories dropped in 7.4.0 (regression fix).
> 
> Please go ahead and remove the moreinfo tag once the upload is available
> in unstable.

Uploaded.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#988617: Acknowledgement (unblock: kodi-pvr-hts/8.3.0+ds1-1)

2021-05-19 Thread Mattia Rizzolo
Control: tag -1 - moreinfo

On Tue, May 18, 2021 at 09:16:55PM +0200, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> 
> On 2021-05-18 08:36:30 +, Vasyl Gello wrote:
> > Fixes in this request:
> > 
> > * 8.2.3: Fixed: Timer settings: Add missing duplicate detection values
> > * 8.3.0: Fixed regular expression in search dialog
> 
> Please go ahead and remove the moreinfo tag once the upload is available
> in unstable.

Uploaded.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#986602: unblock: mkvtoolnix/54.0.0-2

2021-04-08 Thread Mattia Rizzolo
On Thu, Apr 08, 2021 at 05:34:40PM +0200, Sebastian Ramacher wrote:
> * Mark #986520 as bullseye-ignore and if a there is a need to fix
>   another issues in a bullsey-pu upload, switch CXX to g++-9 in that
>   upload. From what I understand, this workaround is supposed to also
>   work for 52.0.0.

Something like that usually is approved for a p-u, as release team
member is your right to decide what to tag bullseye-ignore, but that
would also pretty much hide the bugs from the list of bullseye bugs.  If
you really went down that route I'd rather see you use your usertags to
hide it from the udd view only during the release process rather tha
ignore it forever.
And, since this is p-u material in stable, couldn't one upload
52.0.0-1+deb11u1 to t-p-u just changing CXX?

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#985792: buster-pu: package dput-ng/1.25+deb10u2

2021-03-23 Thread Mattia Rizzolo
Package: release.debian.org
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Hi!

Please consider the proposed dput-ng update, which I already uploaded.

Here is the changelog, and find attached the debdiff from what's
currently in buster.

dput-ng (1.25+deb10u2) buster; urgency=medium

  [ Philippe Pepiot ]
  * Fix a TypeError in http upload exception handling.  MR: !9

  [ Mattia Rizzolo ]
  * Fix crash in the sftp uploader in case of EACCES from the server.
Closes: #953357
  * Update codenames:
+ Drop squeeze*, wheezy* and jessie-backports*.
+ Add bullseye-backports, buster-backports-sloppy.
+ Add bookworm, bookworm-proposed-updates, bookworm-security.

  [ nicoo ]
  * Make `dcut dm` also accept non-uploading DDs, since they are nowadays
treated the same as DMs when concerning upload permissions.
Closes: #985618; MR: !16

  [ Dominic Hargreaves ]
  * In dak-commands files, don't try and construct uploader email from system
hostname, instead skip the whole Uploader field, since it's optional
anyway.  Closes: #984466; MR: !15

 -- Mattia Rizzolo   Tue, 23 Mar 2021 19:20:55 +0100


-- 
regards,
Mattia Rizzolo

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

 .gitlab-ci.yml |2 +-
 debian/changelog   |   25 +
 dput/command.py|   13 ++---
 dput/commands/dm.py|   22 +-
 dput/uploaders/http.py |3 ++-
 dput/uploaders/sftp.py |5 +++--
 skel/codenames/debian.json |   20 +++-
 tests/dputng/codenames/debian.json |   20 +++-
 8 files changed, 64 insertions(+), 46 deletions(-)

diff -Nru dput-ng-1.25+deb10u1/debian/changelog 
dput-ng-1.25+deb10u2/debian/changelog
--- dput-ng-1.25+deb10u1/debian/changelog   2019-07-19 08:15:00.0 
+0200
+++ dput-ng-1.25+deb10u2/debian/changelog   2021-03-23 19:20:55.0 
+0100
@@ -1,3 +1,28 @@
+dput-ng (1.25+deb10u2) buster; urgency=medium
+
+  [ Philippe Pepiot ]
+  * Fix a TypeError in http upload exception handling.  MR: !9
+
+  [ Mattia Rizzolo ]
+  * Fix crash in the sftp uploader in case of EACCES from the server.
+Closes: #953357
+  * Update codenames:
++ Drop squeeze*, wheezy* and jessie-backports*.
++ Add bullseye-backports, buster-backports-sloppy.
++ Add bookworm, bookworm-proposed-updates, bookworm-security.
+
+  [ nicoo ]
+  * Make `dcut dm` also accept non-uploading DDs, since they are nowadays
+treated the same as DMs when concerning upload permissions.
+Closes: #985618; MR: !16
+
+  [ Dominic Hargreaves ]
+  * In dak-commands files, don't try and construct uploader email from system
+hostname, instead skip the whole Uploader field, since it's optional
+anyway.  Closes: #984466; MR: !15
+
+ -- Mattia Rizzolo   Tue, 23 Mar 2021 19:20:55 +0100
+
 dput-ng (1.25+deb10u1) buster; urgency=medium
 
   [ Kunal Mehta ]
diff -Nru dput-ng-1.25+deb10u1/dput/command.py 
dput-ng-1.25+deb10u2/dput/command.py
--- dput-ng-1.25+deb10u1/dput/command.py2018-08-25 10:39:16.0 
+0200
+++ dput-ng-1.25+deb10u2/dput/command.py2021-03-22 20:10:04.0 
+0100
@@ -107,15 +107,13 @@
 name = gecos_name[0]
 else:
 name = pwd_entry.pw_gecos
-if not email_address:
-email_address = socket.getfqdn(socket.gethostname())
 
 if args.maintainer:
 (name, email_address) = email.utils.parseaddr(args.maintainer)
 
 logger.debug("Using %s <%s> as uploader identity" % (name, email_address))
 
-if not name or not email_address:
+if not (name or email_address):
 raise DcutError("Your name or email could not be retrieved."
 "Please set DEBEMAIL and DEBFULLNAME or provide"
 " a full identity through --maintainer")
@@ -134,12 +132,14 @@
 if keyid:
 identity_hint = keyid
 else:
-# hard to see here, but name and email is  guaranteed to be set in
+# at least one of name or email is guaranteed to be set in
 # write_header()
 if name:
 identity_hint = name
-if email:
-identity_hint += " <%s>" % (email)
+if email:
+identity_hint += " <%s>" % (email)
+else:
+identity_hint = email
 
 logger.trace("GPG identity hint: %s" % (identity_hint))
 
@@ -221,7 +221,6 @@
 (name, email) = write_header(fh, profile, args)
 command.prod

Bug#979651: transition: libpodofo

2021-01-12 Thread Mattia Rizzolo
On Tue, Jan 12, 2021 at 09:21:09AM +0100, Sebastian Ramacher wrote:
> On 2021-01-10 19:19:12 +0100, Mattia Rizzolo wrote:
> > Control: forwarded -1 
> > https://release.debian.org/transitions/html/auto-libpodofo.html
> > Control: tag -1 moreinfo
> > 
> > On Sat, Jan 09, 2021 at 07:03:34PM +0100, Mattia Rizzolo wrote:
> > > I haven't yet rebuilt the rdeps, but since the API didn't change I don't
> > > expect any breakage; I'll follow up once I've confirmed everything's
> > > fine.
> > 
> > I rebuilt the 5 rdeps and it turns out scribus failed with it.
> > 
> > I'll be back once I get it building.
> 
> Any news on that? Otherwise I'd postpone this until after the bullseye
> release.

So it seems scribus upstream committed a fix for this.
I'll test the build locally. If it works, may I upload both libpodofo
and scribus myself (and so to save a round on binNMUs for scribus)?

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#979651: transition: libpodofo

2021-01-10 Thread Mattia Rizzolo
Control: forwarded -1 
https://release.debian.org/transitions/html/auto-libpodofo.html
Control: tag -1 moreinfo

On Sat, Jan 09, 2021 at 07:03:34PM +0100, Mattia Rizzolo wrote:
> I haven't yet rebuilt the rdeps, but since the API didn't change I don't
> expect any breakage; I'll follow up once I've confirmed everything's
> fine.

I rebuilt the 5 rdeps and it turns out scribus failed with it.

I'll be back once I get it building.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#979651: transition: libpodofo

2021-01-09 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition

Hi!

PoDoFo upstream decided to drop in a new release today, and I've just
uploaded it to experimental (NEW).

Due to the very low number of reverse dependencies (5), and the fact
that CVEs do pop up every so often here (I'm referring to the fact that
backporting patches in the future will be easier), I'd like an exception
ot the transition freeze for this.

I haven't yet rebuilt the rdeps, but since the API didn't change I don't
expect any breakage; I'll follow up once I've confirmed everything's
fine.


Thanks for considering.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#966825: transition: libcdio

2020-09-03 Thread Mattia Rizzolo
On Thu, Sep 03, 2020 at 06:49:54AM +, Vasyl Gello wrote:
> Hi Gabriel!
> 
> If I understand the info from tracker.d.o correctly, libcdio 2.1.0-2 migrated 
> to testing and transition is complete, isn't it?
> If that's true, can you please push buster backport?

That has nothing to do with the release team (i.e. this bug report), so
please ask in a different forum.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#961868: release.debian.org: RM: broccoli, broccoli-python, broccoli-ruby

2020-05-30 Thread Mattia Rizzolo
Control: reassign -1 ftp.debian.org
Control: clone -1 -2 -3
Control: retitle -1 RM: broccoli -- ROM; deprecated
Control: retitle -2 RM: broccoli-python -- ROM; deprecated
Control: retitle -3 RM: broccoli-ruby -- ROM; deprecated
Control: block -1 by -2 -3

On Sat, May 30, 2020 at 06:00:34PM +0200, Hilko Bengen wrote:
> Package: release.debian.org
> 
> Please remove broccoli, broccoli-python, broccoli-ruby from unstable.
> These packages have been deprecated upstream.

removals from unstable are handled by the ftp masters, reassigning (and
retitling correctly, they like one bug per source package).

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: Why does transition auto-jquery-rm exist?

2020-05-08 Thread Mattia Rizzolo
On Thu, May 07, 2020 at 04:06:21PM +0200, Paul Gevers wrote:
> On 07-05-2020 15:06, Rebecca N. Palmer wrote:
> > Given the above, this is probably not useful: can it be turned off?
> but given the frequency of binary package
> take over, I'm am not going to spend my time on enhancing or fixing the
> script now. (Obviously I am not speaking for anybody else here).

Also, it will go away as soon as src:node-jquery goes away, so there is
no need to be overly concerned.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#947758: buster-pu: package node-handlebars/3:4.1.0-1+deb10u1

2020-05-04 Thread Mattia Rizzolo
Hi,

let me reply before adsb has a chance ;)

On Mon, May 04, 2020 at 02:24:20PM +0200, Xavier wrote:
> Finally I found a way to fix CVE and keep autopkgtest OK
> (node-markdown-it-html5-embed). Here is a debdiff for a future point release

This is good, however,

> diff --git a/debian/changelog b/debian/changelog
> index b985661..64df8db 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,11 @@
> +node-handlebars (3:4.1.0-1+deb10u1) buster; urgency=medium
> +
> +  * Team upload
> +  * Disallow calling "helperMissing" and "blockHelperMissing" directly
> +(Closes: CVE-2019-19919)
> +
> + -- Xavier Guimard   Mon, 04 May 2020 14:21:11 +0200

By now 3:4.1.0-1+deb10u1 is already accepted in p-u, built and all, and
it can't really be removed from there and replaced by a same-versined
pacakge.

Please prepare a +deb10u2 version, and post here a debdiff against the
already uploaded +deb10u1 one.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#959505: release.debian.org: Is erlang autoremoval is necessary?

2020-05-04 Thread Mattia Rizzolo
On Sun, May 03, 2020 at 09:02:11PM +0200, Paul Gevers wrote:
> > Alright, then I recommend this:
> > reassign 958841 src:erlang 1:22.3.2+dfsg-1
> > clone 958841 -1
> > reassign -1 src:elixir-lang 1.9.1.dfsg-1.3
> > retitle -1 elixir-lang: incompatible with erlang 22
> > # consider also leaving a longer message somewhere…?
> > close 958841 1:22.3.3+dfsg-1
> > 
> > Doing that should live a RC bug in elixir-lang, and cause its autorm in
> > a while, and leave erlang where it is, letting it migrate to testing as
> > soon as elixir-lang is out.  The rm from testing of elixir-lang could be
> > expedited if nothing happens.
> 
> I agree with this approach. It leaves the maintainers of elixir-lang
> some time to fix the situation. If they don't fix it, it will be removed
> and erlang can migrate. Unless there is some issue that I am not aware
> of that warrants a faster migration (and hence removal of elixir-lang).

Very well, I've now send that to command@, and added a `summary` to the
cloned bug to explain a bit what's happening.
The new bug against elixir-lang is #959701.

> Given the issue as I understand it, I don't want to binNMU it. I think
> the binNMU'd package can migrate before erlang and then the package in
> testing is broken (until erlang migrates) which isn't cool

I don't think that would happen.  bin:elixir depends on
erlang-pcre-8.43, which is provided by bin:erlang-core in testing, but
erlang-core in unstable only provides erlang-pcre-8.43-1 instead.
(I believe that's the original cause of the breakage, an ABI break in
that thing.)

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#959505: release.debian.org: Is erlang autoremoval is necessary?

2020-05-03 Thread Mattia Rizzolo
On Sun, May 03, 2020 at 12:58:19PM +0300, Sergei Golovan wrote:
> > Well, that bug is assigned to *both* erlang and erlang-elixir, and in
> > fact, the fix was done in erlang, so it really much looks like an erlang
> > bug?
> 
> It wasn't really a fix, I just bumped the erlang-pcre virtual package version
> exactly to make elixir-lang uninstallable because it's broken.

ACK.
Though it still means that indeed you had to do something in erlang as
well ;)

> > Now, it seems that wasn't enough, since erlang-elixir still doesn't pass
> > its autopkgtest with the new erlang; worse, it makes elixir-lang
> > uninstallable.
> 
> Elixir-lang (at least its current version in Debian) uses some
> unstable interface
> in Erlang, so it's sometimes requires to be rebuilt with the new erlang.
> As far as I can see now, elixir-lang is basically unmaintained, so nobody
> will ask for binNMU (it should be sufficient, but I havent't checked this).

I see.

> It's not a desirable output here. This means that without some changes
> in elixir-lang
> new erlang packages will never reach testing. I'm not sure that an 
> unmaintained
> package should stall development of its reverse dependencies like that.

Alright, then I recommend this:
reassign 958841 src:erlang 1:22.3.2+dfsg-1
clone 958841 -1
reassign -1 src:elixir-lang 1.9.1.dfsg-1.3
retitle -1 elixir-lang: incompatible with erlang 22
# consider also leaving a longer message somewhere…?
close 958841 1:22.3.3+dfsg-1

Doing that should live a RC bug in elixir-lang, and cause its autorm in
a while, and leave erlang where it is, letting it migrate to testing as
soon as elixir-lang is out.  The rm from testing of elixir-lang could be
expedited if nothing happens.

> > Lastly, I recommend you just don't spend too much time on understanding
> > the autorm situation, rather just fix whatever is broken and make
> > elixir-lang pass the autopkgtest again; the autorm date is more than a
> > month away after all.
> 
> I would say that binNMU would be sufficient for now, but I wouldn't like to
> constantly monitor this elixir-lang situation.

ACK, if really that package is unmaintained it's probably best to not do
anything even if a simple binNMU was enough.  Or we could just try it
and wait till the next breakage before removing elixir-lang from
testing.

I'm not sure I'd call a package "unmaintained" when the last maintainer
upload was last September, so perhaps I'd still try to give it another
chance by binNMUing it.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#959505: release.debian.org: Is erlang autoremoval is necessary?

2020-05-03 Thread Mattia Rizzolo
On Sun, May 03, 2020 at 09:39:51AM +0300, Sergei Golovan wrote:
> Today, I've got an autoremoval mails for erlang and a whole bunch of related
> packages because of #958841 (see [1] for details).
> 
> Is it really necessary to remove erlang and all its reverse dependencies,
> while it's elixir-lang which is the culprit?

Well, that bug is assigned to *both* erlang and erlang-elixir, and in
fact, the fix was done in erlang, so it really much looks like an erlang
bug?

Now, it seems that wasn't enough, since erlang-elixir still doesn't pass
its autopkgtest with the new erlang; worse, it makes elixir-lang
uninstallable.

> As far as I can see, removal
> of all erlang related packages (which includes elixir-lang) should lead to
> moving them back except for elixir-lang which is now uninstallable.

What do you mean with "moving back"?

> On the other hand, just removing elixir-lang from testing achieves the same
> outcome without removing/moving back many packages.

The autoremoval is quite confusing (perhaps actually buggy?) when bugs
are assigned against multiple packages.  In fact, only erlang is being
autoremoved, elixir-lang is being removed only due to being a rdep of
erlang.

Please read with more attention the text of the bug:
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958841
| Due to the nature of this issue, I filed this bug report against
| both packages. Can you please investigate the situation and reassign the
| bug to the right package?
I'm confident that if you reassign this bug to erlang only (and properly
changing the 'found', 'fixed' and 'done' values), nothing
would be autoremoved, simply because that bug won't affect erlang in
testing anymore.

Lastly, I recommend you just don't spend too much time on understanding
the autorm situation, rather just fix whatever is broken and make
elixir-lang pass the autopkgtest again; the autorm date is more than a
month away after all.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#958192: stretch-pu: package xdg-utils/1.1.1-1+deb9u1

2020-04-25 Thread Mattia Rizzolo
On Sat, Apr 25, 2020 at 07:15:41PM +0100, Adam D. Barratt wrote:
> On Sun, 2020-04-19 at 17:16 +0300, Nicholas Guriev wrote:
> > Along with 1.1.3-1+deb10u1 for buster I propose an update for stretch
> > with the same fixes that applicable for 1.1.1 version.
> > 
> 
> Please go ahead.

Uploaded.

(Nicholas: I know you didn't ask me to, hope I didn't just in too soon)

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#958141: buster-pu: package xdg-utils/1.1.3-1

2020-04-21 Thread Mattia Rizzolo
On Tue, Apr 21, 2020 at 07:07:59PM +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Sat, 2020-04-18 at 23:53 +0300, Nicholas Guriev wrote:
> > There are a number of bugs fixed in the 1.1.3-2 version of the xdg-
> > utils package that now is available in testing and unstable archives.
> > It would be good to have the fixes in buster also.
> > 
> > If you think these changes are okay for stable update, please
> > consider to sponsor upload to stable-proposed-updates.
> 
> The Release Team don't generally sponsor uploads to stable, but feel
> free to go ahead and get it uploaded.

I can upload that.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: Bug#956590: tracker.debian.org: provide excuse for not migrating to testing

2020-04-13 Thread Mattia Rizzolo
f4-python/s390x libvigraimpex/i386 
octave/ppc64el caffe/i386 fast5/ppc64el petsc/armel ncl/armhf 
libvigraimpex/mips64el caffe/amd64 pbseqlib/ppc64el blasr/ppc64el octave/i386 
qgis petsc/mips64el nexus/armhf grads/amd64 openems/ppc64el lammps/s390x 
labplot/arm64 ncl/armel cbflib/arm64 labplot/i386 grads/i386 
libvigraimpex/ppc64el deal.ii/amd64 trilinos/amd64 petsc/amd64 petsc/i386 
fclib/ppc64el ismrmrd/arm64 caffe/mips64el libmatio/i386 fast5/amd64 
netcdf4-python/mipsel libmatio/armel cbflib/mipsel netcdf4-python/amd64 
pdal/armhf libmatio/mipsel labplot/mips64el libminc/mipsel fclib/arm64 
insighttoolkit4/i386 libminc/i386 grads/mipsel ismrmrd/armel lammps/arm64 
fast5/mipsel octave/amd64 caffe/armel pandas/armel ismrmrd/mips64el 
openems/mipsel octave/mipsel lammps/ppc64el octave/armhf ncl/ppc64el 
libvigraimpex/s390x libmatio/ppc64el libvigraimpex/amd64 openems/amd64 
libmatio/amd64 pdal/ppc64el fclib/i386 ncl/arm64 cbflib/i386 nexus/amd64 
fast5/armhf lammps/i386 libvigraimpex/arm64 nexus/mipsel octave/armel 
caffe/arm64 fclib/mipsel octave/mips64el pdal/arm64 libmatio/armhf scilab/i386 
lammps/armhf labplot/s390x pdal/amd64 fclib/armhf grads/armhf 
netcdf4-python/armel grads/s390x caffe/mipsel grads/armel scilab/ppc64el 
libmatio/mips64el fast5/armel nexus/ppc64el ncl/mipsel insighttoolkit4/amd64 
libminc/amd64 pdal/mipsel labplot/amd64 labplot/armel cbflib/mips64el 
cbflib/amd64 libminc/mips64el libmatio/arm64 openems/i386 scilab/arm64 
grads/ppc64el fast5/arm64 cbflib/ppc64el ncl/s390x libminc/armel petsc/armhf 
lammps/mipsel ismrmrd/i386 nexus/s390x libminc/arm64 openems/mips64el 
scilab/armhf fclib/amd64 cbflib/s390x fast5/i386 fast5/mips64el pdal/mips64el 
(10, 37, 270)
got: 61+0: a-1:a-0:a-0:a-0:i-20:m-0:m-0:p-0:s-40
* s390x: cdo, code-saturne, code-saturne-include, fenics, harp, lammps, 
libadios-bin, libdolfin-dev, libdolfin2019.1, libharp-dev, libharp10, 
liblammps-dev, liblammps0, libmedc-dev, libmedimport-dev, libmia-2.4-4, 
libmia-2.4-dev, libmiaviewit-dev, libmiaviewit0, libmshr-dev, libmshr2019.1, 
libncarg-bin, libncarg-dev, libncarg0, libpcl-conversions-dev, libpcl-dev, 
libpcl-ros-dev, libvtk7-dev, libvtk7-qt-dev, mia-tools, mia-viewit, ncl-ncarg, 
python3-cdo, python3-dolfin, python3-harp, python3-lammps, python3-mia, 
python3-mshr, python3-sfepy


> But the tracker page for hdf5 does not say that's the problem, does
> not declare what is holding it up.
> 
> Obviously some part of the Debian infrastructure, dak or dinstall or
> something, knows what's holding up package migration, otherwise it
> would have migrated already.

The only file that knows that information is
https://release.debian.org/britney/update_output.txt - and it's not
really parsable.
The answer to "why doesn't it migrate" is: "migrating it would make
*something* not installable".

It's really not trivial to properly hunt down the reason, and often
needs to be tweaked in a case-by-case basis.


If we really want to do this, it should probably be done by the release
team, and, for example, have brtiney invoke dose and produce a report
for every migration group item.
I'm reassigning this with this in mind.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: state of the rust ecosystem (and particularly rust-cbindgen) in Debian (was: Requesting backport of cbindgen > 0.10.0 to buster)

2020-04-11 Thread Mattia Rizzolo
On Fri, Apr 10, 2020 at 05:47:33PM +0100, peter green wrote:
> It seems that in the end Paul Gevers (elbrus) decided to just do a
> mass removal of rust stuff from testing, this did un-jam some stuff
> but it also excarbated the autopkgtest issues because a test that is
> already failing in testing is not a blocker for a new version to
> migrate, but once a package is out of testing the autopkgtest will
> stop it re-entering.

This is not something you should be complaining about: there are plans
(I don't know at which point they are) to *also* consider failing
autopkgtest in testing as RC.  This would mean that at some point soon,
even if a package starts to fail its autopkgtests in testing, it would
end up being removed as well.
The reasoning behind this is that it doesn't help anybody to have a
known-failing test without any other banchmark.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#955622: release.debian.org: Testing auto removal claims moonshot-ui to be removed for bug it fixesmoonsot

2020-04-03 Thread Mattia Rizzolo
On Fri, Apr 03, 2020 at 10:29:08AM -0400, Sam Hartman wrote:
> >moonshot-ui 1.1.0+libsecret~2 is marked for autoremoval from testing on 
> >2020-04-27
> 
> I'm guessing that this is probably some race condition between migration and 
> removals data sources updating.
> But it seems odd that the testing auto removal script knows about the new 
> version but doesn't know that the new version  fixes the RC bug in question.

It's more likely that the race lies within the BTS.  The BTS only
exports data about whether a bug affects testing or not, without version
information.

> If the removal notice is correct and moonshot-ui is still scheduled for 
> removal even though I fixed the bug, I'd like to better understand what's up.

At this writing, from what I see it's not scheduled for removal anymore.

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#941126: stretch-pu: package dehydrated/0.6.2-2+deb9u1

2020-01-28 Thread Mattia Rizzolo
On Sat, Jan 25, 2020 at 06:08:34PM +0100, Mattia Rizzolo wrote:
> On Fri, Jan 24, 2020 at 09:28:29PM +, Adam D. Barratt wrote:
> > I'm aware that you both called them trivialities and quoted
> > "breakages", but is it worth documenting any of them somewhere in the
> > package?
> 
> I could probably add a NEWS item for the ACMEv2 default move, as that's
> probably something interesting to many.

I've no added this:

diff --git a/debian/dehydrated.NEWS b/debian/dehydrated.NEWS
new file mode 100644
index 000..1bc0fae
--- /dev/null
+++ b/debian/dehydrated.NEWS
@@ -0,0 +1,12 @@
+dehydrated (0.6.2-2+deb10u1~deb9u1) stretch; urgency=medium
+
+  This update changes the default API endpoint to use ACMEv2, as ACMEv1 is
+  in the process of being deprecated and Let's Encrypt will stop supporting it
+  in the upcoming months.
+  This change will, amongst others, bring new features like wildcard
+  certificates support; however, it also slightly changes the authorization
+  flow, which may impact a few users, especially those using DNS validation.
+  Another incompatible change, is the addition of a new --accept-terms command
+  line flag, required when registering a new account.
+
+ -- Mattia Rizzolo   Tue, 28 Jan 2020 17:33:15 +0100


Apart from that and an updated d/changelog, the thing is the same of the
previously sent diff.
With that, I've uploaed the package for convenience of your review.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#941126: stretch-pu: package dehydrated/0.6.2-2+deb9u1

2020-01-25 Thread Mattia Rizzolo
On Fri, Jan 24, 2020 at 09:28:29PM +, Adam D. Barratt wrote:
> I'm aware that you both called them trivialities and quoted
> "breakages", but is it worth documenting any of them somewhere in the
> package?

I could probably add a NEWS item for the ACMEv2 default move, as that's
probably something interesting to many.

The --acept-terms thing is something that affects only new accounts, so
it's not useful to show it on upgrades (not to mention that it already
doesn't work since November…), and the other DNS thing is something that
I don't consider worth warning about.  What do you say?


In the meantime I tried on a stretch system with the stretch version
getting a cert from that (I had to re-use an account from another
installation since I couldn't register a new account with ACMEv1), and
then update to the proposed version and renew.  I only tested http-01
tbh, but dns-01 has no reasons to fail if http works… (if it does it
really should only be for how the local hooks does things).

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#947365: transition: libvigraimpex

2019-12-31 Thread Mattia Rizzolo
On Tue, Dec 31, 2019 at 04:35:22PM +0100, Sebastiaan Couwenberg wrote:
> On 12/31/19 4:20 PM, Andreas Metzler wrote:
> > as Bas correctly diagnoses I am not currently building for all supported
> > versions but only for the default one because it is not trivial but
> > requires some work. Looking at python policy I think that is acceptable
> > but not perfect.
> > 
> > Is my reading of polic correct?
> 
> AFAIK the python policy doesn't document the build dependencies.

It does: 
https://www.debian.org/doc/packaging-manuals/python-policy/build_dependencies.html

> doko filed bugs for at least one of my packages that had python3-all-dev
> in B-D but only built for the default interpreter with the request to
> change the B-D or build for all supported versions, so either option is
> fine.

Indeed.  Building for all supported python versions makes these kind of
transitions much easier, but either variant is fine.

> > Shall I make a timely upload fixing the
> > build-dependency or can I wait for propagation of vigra packages to
> > testing?
> 
> I would commit the change now, and upload it after the testing migration
> unless there are other blockers that hold up the migration for more than
> 5 days, then I would upload it now.

ACK.  I likewise recommend waiting those 2 more days and then upload the
build-dep change.  Either that or add an autopkgtest in the same upload
now ;)

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: Severity bump script

2019-12-02 Thread Mattia Rizzolo
On Mon, 2 Dec 2019, 10:25 pm Paul Gevers,  wrote:

> Hi,
>
> On 02-12-2019 22:15, Sandro Tosi wrote:
> > the blocks are only between py2removal packages, so if a package
> > un-related to the py2removal effort
> > depend/recomments/b-deps/autotest-triggers a py2removal *application*,
> that
> > is still considered a leaf package
>
> You'll fix that, right? Because why would the tree stop at Python? A
> leaf package is a package without Depends/Build-Depends in Debian.


Because the python2 removal is about python2.  If you depend on a python2
package then the dependant application needs to likewise be dropped or
updated, but it also is at the same time somewhat out of scope from "us".

So it's either file py2removal bugs also against packages that don't depend
on python, but just use an application that happens to use python2, or the
current status quo.
That's my take at least.

Also, I am one of those that think we should be much more forceful, and the
current situation looks just fine for me, so I might be biased.


Bug#945957: release.debian.org: Package pymecavideo falsely trageted for AUTORM

2019-12-01 Thread Mattia Rizzolo
On Sun, Dec 01, 2019 at 07:34:53PM +0100, Georges Khaznadar wrote:
> pymecavideo 6.5.1-1 is marked for autoremoval from testing on 2019-12-28
> 
> It (build-)depends on packages with these RC bugs:
> 942999: doxypy: Python2 removal in sid/bullseye
> 
> 
> 
> I double-checked this package, it does NOT build-depend on doxypy.
> Can you help me to prevent the AUTORM action?

I'm pretty sure that it's becuase of some recursive (build-)dep, but I'm
too lazy to chase it right now.  Regardless, I trust the software to be
right.

> By the way, I am pushing a NEW
> package doxypypy (not doxypy), which is maintained upstream and provides the
> same features, and some improvements.

I wonder, is that a drop-in replacement?  Could it instead be uploaded
in place of the current doxpy?

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#944865: buster-pu: package limnoria/2019.02.23-1+deb10u1

2019-11-24 Thread Mattia Rizzolo
Control: tag -1 - moreinfo

On Sat, Nov 23, 2019 at 06:45:27PM +0100, Julien Cristau wrote:
> Control: tag -1 moreinfo
> 
> On Sat, Nov 16, 2019 at 05:36:13PM +0100, Mattia Rizzolo wrote:
> > Limnoria is affected by a security issue the security team deemed not
> > DSA-worthy.  See https://security-tracker.debian.org/tracker/CVE-2019-19010
> > 
> What's the test coverage like for this code, and what's the regression
> risk?

limnoria's whole code (including this plugin) is completely covered by a
comprehensive test suite.  And even if there was a regression it would
be limited to this single plugin, not affecting the regular operation of
the rest of the program.  For this plugin, the tests check all the
operations: 
https://sources.debian.org/src/limnoria/2019.11.09-2/plugins/Math/test.py/
As a test for this particular bug, since this was a bad eval(), now that
there is no eval() anymore that sufficies as a test.

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#944865: buster-pu: package limnoria/2019.02.23-1+deb10u1

2019-11-16 Thread Mattia Rizzolo
<pre>Package: release.debian.org
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Control: clone -1 -2
Control: retitle -2 stretch-pu: package limnoria/2017.01.10-1+deb9u1
Control: tag -2 = stretch
X-Debbugs-Cc: unit...@ubuntu.com


Hello SRMs,

Limnoria is affected by a security issue the security team deemed not
DSA-worthy.  See <a  rel="nofollow" href="https://security-tracker.debian.org/tracker/CVE-2019-19010">https://security-tracker.debian.org/tracker/CVE-2019-19010</a>

I'm uploading fixed packages for both stretch and buster; the patch is
pretty much the same, so I'm opening a single bug, attached are the two
diffs.


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  <a  rel="nofollow" href="https://mapreri.org">https://mapreri.org</a> : :'  :
Launchpad user: <a  rel="nofollow" href="https://launchpad.net/~mapreri">https://launchpad.net/~mapreri</a>  `. `'`
Debian QA page: <a  rel="nofollow" href="https://qa.debian.org/developer.php?login=mattia">https://qa.debian.org/developer.php?login=mattia</a>  `-
</pre><pre>diffstat for limnoria-2019.02.23 limnoria-2019.02.23

 changelog |7 
 patches/fix-unsafe-eval.patch |  394 ++
 patches/series|1 
 3 files changed, 402 insertions(+)

diff -Nru limnoria-2019.02.23/debian/changelog limnoria-2019.02.23/debian/changelog
--- limnoria-2019.02.23/debian/changelog	2019-02-23 01:52:11.0 +0100
+++ limnoria-2019.02.23/debian/changelog	2019-11-12 16:43:35.0 +0100
@@ -1,3 +1,10 @@
+limnoria (2019.02.23-1+deb10u1) buster; urgency=medium
+
+  * Add patch from upstream to fix remote information disclosure and
+possibly remote code execution in the Math plugin.  CVE-2019-19010
+
+ -- Mattia Rizzolo <mat...@debian.org>  Tue, 12 Nov 2019 16:43:35 +0100
+
 limnoria (2019.02.23-1) unstable; urgency=medium
 
   * New upstream version 2019.02.23
diff -Nru limnoria-2019.02.23/debian/patches/fix-unsafe-eval.patch limnoria-2019.02.23/debian/patches/fix-unsafe-eval.patch
--- limnoria-2019.02.23/debian/patches/fix-unsafe-eval.patch	1970-01-01 01:00:00.0 +0100
+++ limnoria-2019.02.23/debian/patches/fix-unsafe-eval.patch	2019-11-12 16:43:35.0 +0100
@@ -0,0 +1,394 @@
+commit 3848ae78de45b35c029cc333963d436b9d2f0a35
+Author: Valentin Lorentz <progval+...@progval.net>
+AuthorDate: Sat Nov 9 15:24:37 2019 +0100
+Commit: Valentin Lorentz <progval+...@progval.net>
+CommitDate: Sat Nov 9 15:49:31 2019 +0100
+
+Math: Rewrite calc functions with a proper evaluator.
+
+Instead of hacking around eval(), which everyone knows is a bad idea
+even with prior expression sanitizing.
+
+diff --git a/plugins/Math/evaluator.py b/plugins/Math/evaluator.py
+new file mode 100644
+index ..9e7208ef
+--- /dev/null
 b/plugins/Math/evaluator.py
+@@ -0,0 +1,169 @@
++###
++# Copyright (c) 2019, Valentin Lorentz
++# All rights reserved.
++#
++# Redistribution and use in source and binary forms, with or without
++# modification, are permitted provided that the following conditions are met:
++#
++#   * Redistributions of source code must retain the above copyright notice,
++# this list of conditions, and the following disclaimer.
++#   * Redistributions in binary form must reproduce the above copyright notice,
++# this list of conditions, and the following disclaimer in the
++# documentation and/or other materials provided with the distribution.
++#   * Neither the name of the author of this software nor the name of
++# contributors to this software may be used to endorse or promote products
++# derived from this software without specific prior written consent.
++#
++# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
++# AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
++# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
++# ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
++# LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
++# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
++# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
++# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
++# CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
++# ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
++# POSSIBILITY OF SUCH DAMAGE.
++###
++
++import ast
++import math
++import cmath
++import operator
++
++class InvalidNode(Exception):
++pass
++
++def filter_module(module, safe_names):
++ret

Bug#944186: stretch-pu: package dehydrated/0.3.1-3+deb9u3

2019-11-05 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: stretch
Control: unblock 941414 by 941126
Control: block 941414 by -1

As a follow-up to Julien's comment in #941126 - here is a targeted pu
fixing that single bug only.

-- 
regards,
Mattia Rizzolo

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

 changelog   |7 ++
 patches/Fixes-559-when-HTTP-2-is-used-header-names-are-lower-case.patch |   26 ++
 patches/Update-the-default-License-Subscriber-Agreement-URL.patch   |6 +-
 patches/series  |1 
 4 files changed, 37 insertions(+), 3 deletions(-)

diff -Nru dehydrated-0.3.1/debian/changelog dehydrated-0.3.1/debian/changelog
--- dehydrated-0.3.1/debian/changelog	2018-03-12 11:48:10.0 +0100
+++ dehydrated-0.3.1/debian/changelog	2019-11-05 14:20:34.0 +0100
@@ -1,3 +1,10 @@
+dehydrated (0.3.1-3+deb9u3) stretch; urgency=medium
+
+  * Add patch from upstream to fix cert renewal when using HTTP/2.
+Closes: #941414
+
+ -- Mattia Rizzolo   Tue, 05 Nov 2019 14:20:34 +0100
+
 dehydrated (0.3.1-3+deb9u2) stretch; urgency=medium
 
   * Add patch from upstream to follow redirects on HTTP GET.
diff -Nru dehydrated-0.3.1/debian/patches/Fixes-559-when-HTTP-2-is-used-header-names-are-lower-case.patch dehydrated-0.3.1/debian/patches/Fixes-559-when-HTTP-2-is-used-header-names-are-lower-case.patch
--- dehydrated-0.3.1/debian/patches/Fixes-559-when-HTTP-2-is-used-header-names-are-lower-case.patch	1970-01-01 01:00:00.0 +0100
+++ dehydrated-0.3.1/debian/patches/Fixes-559-when-HTTP-2-is-used-header-names-are-lower-case.patch	2019-11-05 14:17:57.0 +0100
@@ -0,0 +1,26 @@
+From: Florent <>
+Date: Wed, 9 May 2018 19:29:21 +0200
+Subject: Fixes #559 : when HTTP/2 is used,
+ header names are lower case. So adding ignore case option (-i) to grep's.
+
+Acked-By: Mattia Rizzolo 
+Bug: https://github.com/lukas2511/dehydrated/issues/559
+Bug-Debian: https://bugs.debian.org/941414
+Origin: upstream, e4e712c03ad70bd5100af1333c2801f4b5baa89a
+---
+ dehydrated | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/dehydrated b/dehydrated
+index a0dbf04..c17b0d0 100755
+--- a/dehydrated
 b/dehydrated
+@@ -381,7 +381,7 @@ signed_request() {
+   payload64="$(printf '%s' "${2}" | urlbase64)"
+ 
+   # Retrieve nonce from acme-server
+-  nonce="$(http_request head "${CA}" | grep Replay-Nonce: | awk -F ': ' '{print $2}' | tr -d '\n\r')"
++  nonce="$(http_request head "${CA}" | grep -i Replay-Nonce: | awk -F ': ' '{print $2}' | tr -d '\n\r')"
+ 
+   # Build header with just our public key and algorithm information
+   header='{"alg": "RS256", "jwk": {"e": "'"${pubExponent64}"'", "kty": "RSA", "n": "'"${pubMod64}"'"}}'
diff -Nru dehydrated-0.3.1/debian/patches/series dehydrated-0.3.1/debian/patches/series
--- dehydrated-0.3.1/debian/patches/series	2018-03-12 11:48:10.0 +0100
+++ dehydrated-0.3.1/debian/patches/series	2019-11-05 14:17:57.0 +0100
@@ -6,3 +6,4 @@
 Support-both-config.sh-and-config-as-config-filenames-for.patch
 Update-the-default-License-Subscriber-Agreement-URL.patch
 follow-location-on-http-get-requests.patch
+Fixes-559-when-HTTP-2-is-used-header-names-are-lower-case.patch
diff -Nru dehydrated-0.3.1/debian/patches/Update-the-default-License-Subscriber-Agreement-URL.patch dehydrated-0.3.1/debian/patches/Update-the-default-License-Subscriber-Agreement-URL.patch
--- dehydrated-0.3.1/debian/patches/Update-the-default-License-Subscriber-Agreement-URL.patch	2018-03-12 11:48:10.0 +0100
+++ dehydrated-0.3.1/debian/patches/Update-the-default-License-Subscriber-Agreement-URL.patch	2019-11-05 14:17:57.0 +0100
@@ -5,9 +5,9 @@
 Closes: #881974
 Signed-off-by: Mattia Rizzolo 
 ---
- dehydrated| 2 +-
- docs/examples/config  | 4 ++--
- 3 files changed, 4 insertions(+), 3 deletions(-)
+ dehydrated   | 2 +-
+ docs/examples/config | 4 ++--
+ 2 files changed, 3 insertions(+), 3 deletions(-)
 
 diff --git a/dehydrated b/dehydrated
 index 7b88ae9..882c6bd 100755


signature.asc
Description: PGP signature


Bug#941093: ping!

2019-11-02 Thread Mattia Rizzolo
On Sat, Nov 02, 2019 at 11:18:16PM +0900, Norbert Preining wrote:
> I am fine with both, but I feel like RM is necessary, since without
> qtwebengine reading ebooks does not work.
> 
> Any suggestions of what I should do?

I filed the RM myself, I x-debbugs-cc'ed calibre@.

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#943882: buster-pu: distro-info-data/0.41+deb10u1

2019-10-31 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: buster
X-Debbugs-Cc: distro-info-d...@packages.debian.org

Hi SRM,

I wish to update distro-info-data in stable, so that it contains
up-to-date data regarding the latest ubuntu development release.

I actually plan to do the same to stretch at a later date.

Below is the complete debdiff, which I already uploaded.

diffstat for distro-info-data-0.41 distro-info-data-0.41+deb10u1

 debian/changelog |7 +++
 ubuntu.csv   |1 +
 2 files changed, 8 insertions(+)

diff -Nru distro-info-data-0.41/debian/changelog 
distro-info-data-0.41+deb10u1/debian/changelog
--- distro-info-data-0.41/debian/changelog  2019-06-14 19:50:04.0 
+0200
+++ distro-info-data-0.41+deb10u1/debian/changelog  2019-10-31 
12:00:12.0 +0100
@@ -1,3 +1,10 @@
+distro-info-data (0.41+deb10u1) buster; urgency=medium
+
+  [ Stefano Rivera ]
+  * Add Ubuntu 20.04 LTS, Focal Fossa.
+
+ -- Mattia Rizzolo   Thu, 31 Oct 2019 12:00:12 +0100
+
 distro-info-data (0.41) unstable; urgency=medium

   * Add final animal name for Ubuntu 19.10 Eoan Ermine.
diff -Nru distro-info-data-0.41/ubuntu.csv 
distro-info-data-0.41+deb10u1/ubuntu.csv
--- distro-info-data-0.41/ubuntu.csv2019-06-14 19:50:04.0 +0200
+++ distro-info-data-0.41+deb10u1/ubuntu.csv2019-10-31 11:58:33.0 
+0100
@@ -30,3 +30,4 @@
 18.10,Cosmic Cuttlefish,cosmic,2018-04-26,2018-10-18,2019-07-18
 19.04,Disco Dingo,disco,2018-10-18,2019-04-18,2020-01-18
 19.10,Eoan Ermine,eoan,2019-04-18,2019-10-17,2020-07-17
+20.04 LTS,Focal Fossa,focal,2019-10-17,2020-04-23,2025-04-23


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#941126: stretch-pu: package dehydrated/0.6.2-2+deb9u1

2019-10-01 Thread Mattia Rizzolo
On Wed, Sep 25, 2019 at 10:59:58AM +0200, Mattia Rizzolo wrote:
> From my side, the buster version is much more tested by me, as well as
> somewhat "looked after" by the upstream developer (who, for example,
> contacted me a few months ago to be sure it had a few patches).
> 
> Updating the stretch version would also bring in a few features that
> might be interesting for some users:
>  * ACMEv2 support (related, ISTR hearing LE wanted to retire ACMEv1 at
>some point, so bringing in support for v2 into stretch earlier would
>be a good idea)

It seems that I've been living out of this world.
So, LE will disable new registrations at ACMEv1 starting next month:
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430/2

AFAIK there is no plan to disable issueance of renewing certs, but
still, that's a breakage that we should fix.

Either way, I don't think there is a need to rush anything to
stretch-updates, even leaving that broken till the December-ish .-r
should be fine.

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#941126: stretch-pu: package dehydrated/0.6.2-2+deb9u1

2019-09-25 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: stretch

Hi SRM,

It was brought to my attention that stretch's version of dehydrated has
a few issues.  They could be resolved by adding a bunch of patches on
top of the current versions, but I'd like to propose to instead
backport the buster version as it is into stretch.

From my side, the buster version is much more tested by me, as well as
somewhat "looked after" by the upstream developer (who, for example,
contacted me a few months ago to be sure it had a few patches).

Updating the stretch version would also bring in a few features that
might be interesting for some users:
 * ACMEv2 support (related, ISTR hearing LE wanted to retire ACMEv1 at
   some point, so bringing in support for v2 into stretch earlier would
   be a good idea)
 * a bunch of new hook types
 * support for OCSP

From what I can see, the breakages would pretty much account to the
following:
 * you need a new --accept-terms flag while creating a new account
   (might break autoamted deployments who need to create a new account?)
 * only since v0.6.0 the upstream developer made clear that users should
   not hardcode a list of hook, and it's known many users did it, so
   hook scripts may break due to unknown hook types
 * this also changes the default endpoint to ACMEv2.  It should be
   totally transparent for most users, and those who really need ACMEv1
   (why?) would need to explicitly specify it.


IMHO, it would be best to just take the buster version as-is, without
starting a whack-a-mole in backporting fixes, even if it would be
somewhat trivial (the lack of ACMEv2 means many can be skipped), but
they would have so many conflicts that missing bits and causing (also
subtle… it's bash after all) bugs makes me prefer not to try it.

If this route is accepted, I'd keep both stretch and buster updated at
the same time, if case further changes are required in the future.


What's your opinion?

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: Haskell binnmus is there a problem?

2019-08-21 Thread Mattia Rizzolo
On Wed, Aug 21, 2019 at 10:06:00AM +0200, Joachim Breitner wrote:
> I used to schedule these, but for many months it seems it wasn't
> necessary, not sure if someone else scheduled them

At the very least, quite some times pochu did them the last year, fwiw.

> Going forward, it is not sustainable for this to depend on manual
> interaction by me. We at least need to allow a more active member of
> the Haskell team do these, or finally automate this tedious task.

It's the problem all statically liked languages have, be that haskell,
ocaml, or the "new" golang (that came to the spotlight due to a somewhat
worse implementation than the other two).  Please do try to coordinate
and decide on a sane method to process auto-binNMUs or something like
that.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#935095: nmu: znc-backlog

2019-08-19 Thread Mattia Rizzolo
Control: close -1

On Mon, Aug 19, 2019 at 02:36:42PM +0200, Mattia Rizzolo wrote:
> please bin-nmu znc-backlog against the new znc, so that then znc can
> finally migrate.
> 
> We are discussing in #917222 on how to improve the situation, but in the
> meantime it would be better to not to block znc…
> 
> wb nmu znc-backlog_0.20180824-1 . ANY . -m "Rebuild against the last znc"

Actually, nvm.
We unblocked our situation sooner than I expected, so I'll now upload a
src:znc building znc-backlog, and there won't be any other issue like
this one.

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#935095: nmu: znc-backlog

2019-08-19 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: nmu

Dear RT,

please bin-nmu znc-backlog against the new znc, so that then znc can
finally migrate.

We are discussing in #917222 on how to improve the situation, but in the
meantime it would be better to not to block znc…

wb nmu znc-backlog_0.20180824-1 . ANY . -m "Rebuild against the last znc"

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: Bits from the Release Team: ride like the wind, Bullseye!

2019-08-18 Thread Mattia Rizzolo
On Sun, Aug 18, 2019 at 08:54:21AM +0100, Ian Jackson wrote:
> > On 19/08/08 09:46, Paul Gevers wrote:
> > > I think we should also try to improve the visibility towards reverse
> > > dependencies that their autopkgtest is blocking other packages. I would
> > > love tracker (and the old pts) to show this on their page. (Working on
> > > such a patch is on my TODO list, except not at the top).
> 
> I already made grep-excuses print this information.  It has been very
> helpful to me.  Maybe we should make --autopkgtests the default ?

I think no: --autopkgtests requires quite a bit more computation and
connecting to udd and whatnot, I don't think that should be the default.
Especially because udd-mirror is starting to be under-dimensioned so
it's sometimes quite slow to serve responses (like in the times when its
importing a new dump).

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#933983: RM: storm/0.19-2 -- RoQA; orphaned; no Py3 and no revdeps

2019-08-05 Thread Mattia Rizzolo
Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: storm -- RoQA; orphaned; no Python 3 port and no 
reverse dependencies

On Tue, Aug 06, 2019 at 12:11:15AM +0500, Andrey Rahmatullin wrote:
> > From which suite?
> From unstable please.

Reassigning accordingly.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#933984: RM: pyramid-beaker/0.6.1+ds1-1 -- RoM; no Py3 and no revdeps

2019-08-05 Thread Mattia Rizzolo
Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: pyramid-beaker -- RoM; No Python3 port and no rerverse 
dependencies


On Tue, Aug 06, 2019 at 12:11:54AM +0500, Andrey Rahmatullin wrote:
> Removal from unstable.

Removals from unstable are handled by ftp-master.  Reassigning.
(and also has a singly differnet format for the title)

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#933899: buster-pu: package devscripts/2.19.5+deb10u1

2019-08-04 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: buster

Dear SRM,

I'm proposing the attached update to devscripts, with the only change
being the update to the default target for `dch --bpo` (and
`dch --stable`, but nobody uses that :P).

I have already uplodaded it to buster, please consider this update in
the upcoming point release.

TIA.

-- 
regards,
Mattia Rizzolo

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

 debian/changelog   |8 
 po4a/po/de.po  |6 +++---
 po4a/po/devscripts.pot |4 ++--
 po4a/po/fr.po  |6 +++---
 scripts/debchange.1|2 +-
 scripts/debchange.pl   |6 +++---
 test/test_debchange|8 
 7 files changed, 24 insertions(+), 16 deletions(-)

diff -Nru devscripts-2.19.5/debian/changelog devscripts-2.19.5+deb10u1/debian/changelog
--- devscripts-2.19.5/debian/changelog	2019-05-09 17:01:29.0 +0200
+++ devscripts-2.19.5+deb10u1/debian/changelog	2019-08-04 23:15:44.0 +0200
@@ -1,3 +1,11 @@
+devscripts (2.19.5+deb10u1) buster; urgency=medium
+
+  [ Thomas Goirand ]
+  * debchange:
++ Target buster-backports with --bpo.  Closes: #931614
+
+ -- Mattia Rizzolo   Sun, 04 Aug 2019 23:15:44 +0200
+
 devscripts (2.19.5) unstable; urgency=medium
 
   [ Topi Miettinen ]
diff -Nru devscripts-2.19.5/po4a/po/de.po devscripts-2.19.5+deb10u1/po4a/po/de.po
--- devscripts-2.19.5/po4a/po/de.po	2019-05-09 16:52:23.0 +0200
+++ devscripts-2.19.5+deb10u1/po4a/po/de.po	2019-08-04 23:15:42.0 +0200
@@ -7,7 +7,7 @@
 msgstr ""
 "Project-Id-Version: devscripts 2.18.9\n"
 "Report-Msgid-Bugs-To: devscri...@packages.debian.org\n"
-"POT-Creation-Date: 2019-04-28 16:23+0200\n"
+"POT-Creation-Date: 2019-07-09 11:23+0200\n"
 "PO-Revision-Date: 2019-01-27 10:18+0200\n"
 "Last-Translator: Chris Leick \n"
 "Language-Team: de \n"
@@ -7368,10 +7368,10 @@
 #. type: Plain text
 #: ../scripts/debchange.1:264
 msgid ""
-"Increment the Debian release number for an upload to stretch-backports, and "
+"Increment the Debian release number for an upload to buster-backports, and "
 "add a backport upload changelog comment."
 msgstr ""
-"erhöht die Debian-Veröffentlichungsnummer für ein Hochladen nach stretch-"
+"erhöht die Debian-Veröffentlichungsnummer für ein Hochladen nach buster-"
 "backports und fügt einen Changelog-Kommentar »backport upload« hinzu."
 
 #. type: TP
diff -Nru devscripts-2.19.5/po4a/po/devscripts.pot devscripts-2.19.5+deb10u1/po4a/po/devscripts.pot
--- devscripts-2.19.5/po4a/po/devscripts.pot	2019-05-09 17:01:29.0 +0200
+++ devscripts-2.19.5+deb10u1/po4a/po/devscripts.pot	2019-08-04 23:15:44.0 +0200
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2019-04-28 16:23+0200\n"
+"POT-Creation-Date: 2019-07-09 11:23+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME \n"
 "Language-Team: LANGUAGE \n"
@@ -5590,7 +5590,7 @@
 #. type: Plain text
 #: ../scripts/debchange.1:264
 msgid ""
-"Increment the Debian release number for an upload to stretch-backports, and "
+"Increment the Debian release number for an upload to buster-backports, and "
 "add a backport upload changelog comment."
 msgstr ""
 
diff -Nru devscripts-2.19.5/po4a/po/fr.po devscripts-2.19.5+deb10u1/po4a/po/fr.po
--- devscripts-2.19.5/po4a/po/fr.po	2019-05-09 16:52:23.0 +0200
+++ devscripts-2.19.5+deb10u1/po4a/po/fr.po	2019-08-04 23:15:42.0 +0200
@@ -14,7 +14,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: devscripts\n"
-"POT-Creation-Date: 2019-04-28 16:23+0200\n"
+"POT-Creation-Date: 2019-07-09 11:23+0200\n"
 "PO-Revision-Date: 2019-04-28 16:32+0200\n"
 "Last-Translator: Xavier Guimard \n"
 "Language-Team: French \n"
@@ -7386,10 +7386,10 @@
 #. type: Plain text
 #: ../scripts/debchange.1:264
 msgid ""
-"Increment the Debian release number for an upload to stretch-backports, and "
+"Increment the Debian release number for an upload to buster-backports, and "
 "add a backport upload changelog comment."
 msgstr ""
-"Incrémenter le numéro de publication de Debian pour un envoi dans stretch-"
+"Incrémenter le numéro de publication de Debian pour un envoi dans buster-"
 

Bug#932417: nmu: ocamlnet_4.1.2-3

2019-07-22 Thread Mattia Rizzolo
On Mon, Jul 22, 2019 at 09:21:19PM +0200, Paul Gevers wrote:
> Hi,
> 
> On 22-07-2019 20:54, Mattia Rizzolo wrote:
> > On Mon, Jul 22, 2019 at 08:41:09PM +0200, Paul Gevers wrote:
> >> I'm relatively new on the team so give me some slack. There is a
> >> permanent transition tracker for ocaml, so I *guess* this is handled
> >> differently than via regular binNMU requests:
> >> https://release.debian.org/transitions/html/ocaml.html Is there anything
> >> special here?
> > 
> > nomeata has scripts to detect this kind of stuff, for ocaml here:
> > https://people.debian.org/~nomeata/binNMUs-ocaml.txt
> > Those files are written in a way you can just pipe them into `wb`.
> 
> I noticed that. But is the RT doing that? Or do ocaml people have access
> to wb to do this themselves?

nomeata himself has wb access, and has been doing quite some of those
binnmus in the past.
However, at least in the last year, quite some of them were done by
pochu instead, coordinated on IRC on #-haskell or similar channels.

This is to say: I don't actually know where we are left, but I actually
believe there is nothing really set and properly decided, it just
happened to come up like that and that worked well enough that it stuck
there (the fact that they run in a private cronjob on people.d.o should
say enough).

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#932417: nmu: ocamlnet_4.1.2-3

2019-07-22 Thread Mattia Rizzolo
On Mon, Jul 22, 2019 at 08:41:09PM +0200, Paul Gevers wrote:
> I'm relatively new on the team so give me some slack. There is a
> permanent transition tracker for ocaml, so I *guess* this is handled
> differently than via regular binNMU requests:
> https://release.debian.org/transitions/html/ocaml.html Is there anything
> special here?

nomeata has scripts to detect this kind of stuff, for ocaml here:
https://people.debian.org/~nomeata/binNMUs-ocaml.txt
Those files are written in a way you can just pipe them into `wb`.

Incidentally, IMHO ocaml and haskell have the same issue golang has
regarding security and stuff, but the release team never really bothered
with them much, I think you should definitely try to work out something
to track decently all these statically linked languages.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: Remove package from testing even if it has reverse dependencies?

2019-07-20 Thread Mattia Rizzolo
On Sat, Jul 20, 2019 at 03:35:21PM -0500, Kenneth Pronovici wrote:
> Ok.  The bugs are already filed, so I guess I'll just wait to have that
> conversation there.

Another thing that is usually done is set all the relevant bugs as
blockers of the RM bug, so they are easily reachable and it's easy to
see what is missing.
Also, those bugs you filed last year, they should all be RC, and so
packages would be autoremoved from testing.

-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#932508: RM: cross-toolchain-base-mipsen/2 gcc-8-cross-mipsen/2~c2 gcc-defaults-mipsen/1.181.1

2019-07-20 Thread Mattia Rizzolo
On Sat, Jul 20, 2019 at 05:02:51PM +0800, YunQiang Su wrote:
> Mattia Rizzolo  于2019年7月20日周六 下午4:33写道:
> >
> > Package: release.debian.org
> > User: release.debian@packages.debian.org
> > Usertags: rm
> > X-Debbugs-Cc: d...@debian.org, s...@debian.org, debian-m...@lists.debian.org
> >
> > cross-toolchain-base-mipsen is failing its autopkgtest on testing with
> > the new binutils, and that prevents migrating the new binutils and
> > everything that depends on it (including updates to gcc-8 and gcc-9).
> 
> why it happens? why the bug of cross-toolchain-base-mipsen will effect
> binutils and gcc-8/9?
> 
> I think that they have no relationship?

check 
https://ci.debian.net/packages/c/cross-toolchain-base-mipsen/testing/amd64/
cross-toolchain-base-mipsen/2 fails its tests with
binutils/2.32.51.20190707-1, and from what I understand that's quite
expected actually.

In turn, it blocks gcc-* because they require the new binutils.
And quite a few other packages all waiting on binutils, look at
https://release.debian.org/britney/update_excuses.html and grep for
"binutils (not considered)".

Having a package tangled with the toolchain is very easy for it to cause
quite some stalls.

> > From my knowledge, Matthias already warned the porters about this
> > potential removal if cross-toolchain-base-mipsen went unfixed, but
> > nothing happened.
> 
> I am very sorry for it as I forgot it.

According to Matthias, he is quite unhappy about how the mips porters
deal with this, with him asking "you" to fix stuff but then he found
himself forced to do it instead.  Please consider being more proactive
in the maintenance of these kind of packages, as you otherwise risk
irking people…

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#932508: RM: cross-toolchain-base-mipsen/2 gcc-8-cross-mipsen/2~c2 gcc-defaults-mipsen/1.181.1

2019-07-20 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
X-Debbugs-Cc: d...@debian.org, s...@debian.org, debian-m...@lists.debian.org

cross-toolchain-base-mipsen is failing its autopkgtest on testing with
the new binutils, and that prevents migrating the new binutils and
everything that depends on it (including updates to gcc-8 and gcc-9).

Formally you could just ignore the test, but that package is just
broken and it doesn't make sense to keep it in that state.  Once the
mips porters fix it, it can then migrate again.

From my knowledge, Matthias already warned the porters about this
potential removal if cross-toolchain-base-mipsen went unfixed, but
nothing happened.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#932448: buster-pu: package dehydrated/0.6.2-2+deb10u1

2019-07-19 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Tags: buster
Usertags: pu

Dear SRM,

I'm seeking approval to do this update in buster.
The goal is fixing a set of bugs stemming from upcoming changes on the
Let's Encrypt API.
See:
https://github.com/lukas2511/dehydrated/pull/648
https://github.com/lukas2511/dehydrated/issues/650
https://github.com/lukas2511/dehydrated/issues/647
https://github.com/lukas2511/dehydrated/issues/652

The original fix caused a couple of regression, so it's splitted in 3
commits (→ 3 patch files).
The changes are already in bullseye.

Thank you for your attention.

-- 
regards,
Mattia Rizzolo

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

 changelog   |9 +
 gbp.conf|2 
 patches/Fixes-559-when-HTTP-2-is-used-header-names-are-lower-case.patch |2 
 patches/fixed-fetching-of-account-information-fixes-652-fixes-647.patch |   30 +
 patches/release-0.6.4-fixed-account-id-handling-again.patch |   57 ++
 patches/release-0.6.5-fixed-apiv1-compatibility.patch   |   45 +++
 patches/series  |3 
 7 files changed, 146 insertions(+), 2 deletions(-)

diff -Nru dehydrated-0.6.2/debian/changelog dehydrated-0.6.2/debian/changelog
--- dehydrated-0.6.2/debian/changelog	2019-03-11 16:25:53.0 +0100
+++ dehydrated-0.6.2/debian/changelog	2019-07-19 14:59:11.0 +0200
@@ -1,3 +1,12 @@
+dehydrated (0.6.2-2+deb10u1) buster; urgency=medium
+
+  * Add three more patches from upstream.
+Fixing the following bug:
+ + Fixed fetching of account information.
+ + Followup fixes for account ID handling, and APIv1 compatibility.
+
+ -- Mattia Rizzolo   Fri, 19 Jul 2019 14:59:11 +0200
+
 dehydrated (0.6.2-2) unstable; urgency=medium
 
   * Add a number of patches from upstream.
diff -Nru dehydrated-0.6.2/debian/gbp.conf dehydrated-0.6.2/debian/gbp.conf
--- dehydrated-0.6.2/debian/gbp.conf	2018-05-08 12:08:48.0 +0200
+++ dehydrated-0.6.2/debian/gbp.conf	2019-07-19 14:58:48.0 +0200
@@ -1,6 +1,6 @@
 [DEFAULT]
 upstream-branch = upstream/master
-debian-branch = debian/master
+debian-branch = debian/buster
 upstream-tag = v%(version)s
 pristine-tar = True
 pristine-tar-commit = True
diff -Nru dehydrated-0.6.2/debian/patches/fixed-fetching-of-account-information-fixes-652-fixes-647.patch dehydrated-0.6.2/debian/patches/fixed-fetching-of-account-information-fixes-652-fixes-647.patch
--- dehydrated-0.6.2/debian/patches/fixed-fetching-of-account-information-fixes-652-fixes-647.patch	1970-01-01 01:00:00.0 +0100
+++ dehydrated-0.6.2/debian/patches/fixed-fetching-of-account-information-fixes-652-fixes-647.patch	2019-07-19 14:52:44.0 +0200
@@ -0,0 +1,30 @@
+From: Lukas Schauer 
+Date: Tue, 25 Jun 2019 12:19:20 +0200
+Subject: fixed fetching of account information (fixes #652, fixes #647,
+ fixes #650, closes #648)
+
+---
+ dehydrated | 9 +
+ 1 file changed, 9 insertions(+)
+
+diff --git a/dehydrated b/dehydrated
+index 69057e7..a29910b 100755
+--- a/dehydrated
 b/dehydrated
+@@ -396,7 +396,16 @@ init_system() {
+ 
+   # Read account information or request from CA if missing
+   if [[ -e "${ACCOUNT_KEY_JSON}" ]]; then
++if [[ -z "$(cat "${ACCOUNT_KEY_JSON}" | get_json_int_value id)" ]]; then
++  echo "+ Fetching account information..."
++  ACCOUNT_URL="$(signed_request "${CA_NEW_ACCOUNT}" '{"onlyReturnExisting": true}' 4>&1 | grep -i ^Location: | awk '{print $2}' | tr -d '\r\n')"
++  ACCOUNT_INFO="$(signed_request "${ACCOUNT_URL}" '{}')"
++  echo "${ACCOUNT_INFO}" > "${ACCOUNT_KEY_JSON}"
++fi
+ ACCOUNT_ID="$(cat "${ACCOUNT_KEY_JSON}" | get_json_int_value id)"
++if [[ -z "${ACCOUNT_ID}" ]]; then
++  _exiterr "Unknown error on fetching account information"
++fi
+ if [[ ${API} -eq 1 ]]; then
+   ACCOUNT_URL="${CA_REG}/${ACCOUNT_ID}"
+ else
diff -Nru dehydrated-0.6.2/debian/patches/Fixes-559-when-HTTP-2-is-used-header-names-are-lower-case.patch dehydrated-0.6.2/debian/patches/Fixes-559-when-HTTP-2-is-used-header-names-are-lower-case.patch
--- dehydrated-0.6.2/debian/patches/Fixes-559-when-HTTP-2-is-used-header-names-are-lower-case.patch	2019-03-11 16:21:33.0 +0100
+++ dehydrated-0.6.2/debian/patches/Fixes-559-when-HTTP-2-is-used-header-names-are-lower-case.patch	2019-07-19 1

Bug#932441: buster-pu: package dput-ng/1.25+deb10u1

2019-07-19 Thread Mattia Rizzolo
Package: release.debian.org
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Dear SRM,

I'm uploading an update for dput-ng to allow uploading packages to
buster-backports and stretch-backports-sloppy.
We also did a similar update in the last release, but this time the diff
is much smaller…
While on it, I also added a bunch of packages to autopkgtests' depends
that should make the package pass it.

-- 
regards,
Mattia Rizzolo

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

 debian/changelog   |   10 ++
 debian/tests/control   |5 +
 skel/codenames/debian.json |2 ++
 tests/dputng/codenames/debian.json |2 ++
 4 files changed, 19 insertions(+)

diff -Nru dput-ng-1.25/debian/changelog dput-ng-1.25+deb10u1/debian/changelog
--- dput-ng-1.25/debian/changelog	2019-04-23 15:49:34.0 +0200
+++ dput-ng-1.25+deb10u1/debian/changelog	2019-07-19 08:15:00.0 +0200
@@ -1,3 +1,13 @@
+dput-ng (1.25+deb10u1) buster; urgency=medium
+
+  [ Kunal Mehta ]
+  * Add buster-backports and stretch-backports-sloppy codenames.  MR: !7
+
+  [ Mattia Rizzolo ]
+  * autopkgtest: add missing test dependencies and restrictions.
+
+ -- Mattia Rizzolo   Fri, 19 Jul 2019 08:15:00 +0200
+
 dput-ng (1.25) unstable; urgency=medium
 
   * Team upload.
diff -Nru dput-ng-1.25/debian/tests/control dput-ng-1.25+deb10u1/debian/tests/control
--- dput-ng-1.25/debian/tests/control	2019-02-12 20:21:16.0 +0100
+++ dput-ng-1.25+deb10u1/debian/tests/control	2019-07-19 08:15:00.0 +0200
@@ -1,4 +1,9 @@
 Test-Command: cp -rv setup.cfg skel tests "$AUTOPKGTEST_TMP" && cd "$AUTOPKGTEST_TMP" && nosetests3 -v
 Depends:
+ build-essential,
+ debhelper,
+ python3-distro-info,
  python3-nose,
+ python3-validictory,
  @,
+Restrictions: allow-stderr
diff -Nru dput-ng-1.25/skel/codenames/debian.json dput-ng-1.25+deb10u1/skel/codenames/debian.json
--- dput-ng-1.25/skel/codenames/debian.json	2018-05-24 10:55:21.0 +0200
+++ dput-ng-1.25+deb10u1/skel/codenames/debian.json	2019-07-18 15:46:22.0 +0200
@@ -2,7 +2,9 @@
 "backport": [
 "stable-backports",
 "oldstable-backports",
+"buster-backports",
 "stretch-backports",
+"stretch-backports-sloppy",
 "jessie-backports",
 "jessie-backports-sloppy",
 "wheezy-backports",
diff -Nru dput-ng-1.25/tests/dputng/codenames/debian.json dput-ng-1.25+deb10u1/tests/dputng/codenames/debian.json
--- dput-ng-1.25/tests/dputng/codenames/debian.json	2018-05-24 10:55:21.0 +0200
+++ dput-ng-1.25+deb10u1/tests/dputng/codenames/debian.json	2019-07-18 15:46:22.0 +0200
@@ -2,7 +2,9 @@
 "backport": [
 "stable-backports",
 "oldstable-backports",
+"buster-backports",
 "stretch-backports",
+"stretch-backports-sloppy",
 "jessie-backports",
 "jessie-backports-sloppy",
 "wheezy-backports",


signature.asc
Description: PGP signature


Bug#931118: unblock: debian-keyring/2019.06.25

2019-06-30 Thread Mattia Rizzolo
On Sun, Jun 30, 2019 at 08:38:52PM +0200, Paul Gevers wrote:
> On 26-06-2019 16:10, Mattia Rizzolo wrote:
> > The last upload of debian-keyring done yesterday updates the security
> > team key.  See #928222 for more context.
> > 
> > I think it would be good if this change could find its way into buster.
> > With this package providing data only, there are no regression
> > potentials, imho.  Also, with it shipping mostly binary files, a debdiff
> > is quite useless.
> 
> The time for unblocks for buster has come and gone. The deadline was
> last Tuesday, we are now in deep freeze and we were not able to process
> your unblock request and give it an exception. I assume this could be
> fixed via a stable release update targeting buster, such that this can
> be fixed in the first point release. If that doesn't work for you and I
> am wrong, please just close this bug.

Sure, it can be done, it just feels incredibly silly from my point of
view (with this package being data only, and either way I'd suspect a pu
upload being less "tested" in a case like this).

Not to mention that I personally have little interest in doing this
work (I just recalled the security team opening that bug, then it being
fixed very late, so I asked an explicit unblock).

-- 
regards,
Mattia Rizzolo

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



Bug#931118: unblock: debian-keyring/2019.06.25

2019-06-26 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-keyr...@packages.debian.org

Dear RT,

The last upload of debian-keyring done yesterday updates the security
team key.  See #928222 for more context.

I think it would be good if this change could find its way into buster.
With this package providing data only, there are no regression
potentials, imho.  Also, with it shipping mostly binary files, a debdiff
is quite useless.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#929576: unblock: hexchat/2.14.2-4

2019-05-26 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

please consider unblocking this new release of hexchat.

It fixes a crash on exit in the python plugin, caused by something that
python 3.7 did.

From my side it went unnoticed till now because nothing notifies me of
crashes, and clearly my window manager hid it from me... I never though
of running it off a terminal…  also I'm sorry I misinterpreted/ignored
the relevant bug, only a recent bug in ubuntu triggered me to act on it.

While on it I also renamed (really, just renumbered) the other two
patches… sorry for the littel noise in the debdiff, but it really is not
doing anything extra apart the renaming (git is more clear).

-- 
regards,
Mattia Rizzolo

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

 changelog   |7 
 patches/0001-Build-for-both-python2-and-python3-by-default.patch|  100 ++
 patches/0002-Build-for-both-python2-and-python3-by-default.patch|  100 --
 patches/0002-Fix-FTBFS-on-non-linux.patch   |   29 ++
 patches/0003-Fix-FTBFS-on-non-linux.patch   |   29 --
 patches/0003-Python-plugin-Call-EndInterpreter-when-deinit-ing-th.patch |   35 +++
 patches/series  |5 
 7 files changed, 174 insertions(+), 131 deletions(-)

diff -Nru hexchat-2.14.2/debian/changelog hexchat-2.14.2/debian/changelog
--- hexchat-2.14.2/debian/changelog	2018-12-03 14:17:35.0 +0100
+++ hexchat-2.14.2/debian/changelog	2019-05-25 11:48:26.0 +0200
@@ -1,3 +1,10 @@
+hexchat (2.14.2-4) unstable; urgency=medium
+
+  * Add a patch to fix a probable crash while unloading the Python plugin
+when using Python 3.7.  LP: #1830246; Closes: #921208
+
+ -- Mattia Rizzolo   Sat, 25 May 2019 11:48:26 +0200
+
 hexchat (2.14.2-3) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru hexchat-2.14.2/debian/patches/0001-Build-for-both-python2-and-python3-by-default.patch hexchat-2.14.2/debian/patches/0001-Build-for-both-python2-and-python3-by-default.patch
--- hexchat-2.14.2/debian/patches/0001-Build-for-both-python2-and-python3-by-default.patch	1970-01-01 01:00:00.0 +0100
+++ hexchat-2.14.2/debian/patches/0001-Build-for-both-python2-and-python3-by-default.patch	2019-05-25 11:48:26.0 +0200
@@ -0,0 +1,100 @@
+From: Mattia Rizzolo 
+Date: Tue, 13 Mar 2018 23:41:47 +0100
+Subject: Build for both python2 and python3 by default
+
+Forwarded: not-needed
+---
+ data/misc/meson.build  | 11 ---
+ meson_options.txt  |  7 +--
+ plugins/meson.build|  2 +-
+ plugins/python/meson.build | 20 
+ 4 files changed, 26 insertions(+), 14 deletions(-)
+
+diff --git a/data/misc/meson.build b/data/misc/meson.build
+index f7f1c27..ca091e8 100644
+--- a/data/misc/meson.build
 b/data/misc/meson.build
+@@ -98,9 +98,14 @@ if get_option('with-plugin') and get_option('with-appdata')
+ ]
+   endif
+ 
+-  if get_option('with-python') != 'false'
++  if get_option('with-python2') != 'false'
+ plugin_metainfo += [
+-  ['Python', 'Provides a scripting interface in Python', 'GPL-2.0+']
++  ['Python2', 'Provides a scripting interface in Python2', 'GPL-2.0+']
++]
++  endif
++  if get_option('with-python3') != 'false'
++plugin_metainfo += [
++  ['Python3', 'Provides a scripting interface in Python3', 'GPL-2.0+']
+ ]
+   endif
+ 
+@@ -124,4 +129,4 @@ if get_option('with-plugin') and get_option('with-appdata')
+   install_dir: get_option('install-plugin-metainfo') ? metainfodir : '',
+ )
+   endforeach
+-endif
+\ No newline at end of file
++endif
+diff --git a/meson_options.txt b/meson_options.txt
+index 100a5ee..083da91 100644
+--- a/meson_options.txt
 b/meson_options.txt
+@@ -48,8 +48,11 @@ option('with-lua', type: 'string', value: 'luajit',
+ option('with-perl', type: 'string', value: 'perl',
+   description: 'Perl scripting plugin, value is path to perl executable or "false"'
+ )
+-option('with-python', type: 'string', value: 'python3',
+-  description: 'Python scripting plugin. value is pkg-config name to use or "false"'
++option('with-python2', type: 'string', value: 'python2',
++  description: 'Python 2 scripting plugin. value is pkg-config name to use or "false"'
++)
++option('with-python3', type: 'string', value: 'python3',
++  description: 'Python 3 scripting plugin. value is pkg-config name to use or "false"'
+ )
+ option('with-sysinfo', type: 'boolean',
+   description: 'System information plug

Bug#928720: unblock: devscripts/2.19.5

2019-05-09 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

please unblock devscripts/2.19.5 - debdiff (filtering out the po files)
is attached.

Changes are:
 * typos in documentation
 * small fixes in salsa(1) and a tiny one in uscan(1)
 * important fixes in mk-origtargz(1) - see the recent post on d-d@ from
   guillem

Thanks for considering.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
 debian/changelog|   34 ++-
 lib/Devscripts/MkOrigtargz.pm   |   42 +---
 lib/Devscripts/Salsa/Config.pm  |4 +-
 lib/Devscripts/Salsa/check_repo.pm  |1 
 lib/Devscripts/Salsa/update_repo.pm |6 +++
 lib/Devscripts/Uscan/WatchFile.pm   |2 -
 scripts/hardening-check.pl  |   10 ++---
 scripts/salsa.pl|6 ++-
 scripts/uscan.pl|3 +
 test/lib_test_uscan |2 -
 test/test_mk-origtargz  |   63 ++--
 11 files changed, 147 insertions(+), 26 deletions(-)
diffstat for devscripts-2.19.4 devscripts-2.19.5

diff -Nru devscripts-2.19.4/debian/changelog devscripts-2.19.5/debian/changelog
--- devscripts-2.19.4/debian/changelog	2019-03-20 16:57:59.0 +0100
+++ devscripts-2.19.5/debian/changelog	2019-05-09 17:01:29.0 +0200
@@ -1,3 +1,35 @@
+devscripts (2.19.5) unstable; urgency=medium
+
+  [ Topi Miettinen ]
+  * hardening-check:
++ Fix some typos in the documentation.  MR: !118
+
+  [ Xavier Guimard ]
+  * Update French translation.
+  * uscan:
++ Don't fail on first error when using multiple watch files.
+  Closes: #927864; MR: !119
+  * salsa:  MR: !117
++ Fix token regexp to allow "-" in GitLab tokens.
++ Fix useless warnings when old description is null.  Closes: #927367
++ Accept sub-groups in --group parameter.  Closes: #927350
++ Fix bad warning if user is an inherited member of a subgroup.
+  Closes: #927373
+
+  [ Edward Betts ]
+  * Correct some spelling errors in documentation.  MR: !116
+
+  [ Guillem Jover ]
+  * mk-origtargz:  MR: !120
++ Do not enarmor already armored OpenPGP signatures.  This actively caused
+  broken .asc files to be uploaded to the archive.
++ Pass --no-options to gpg.
++ Prevent duplicating the signature in case mk-origtargz is called twice.
++ Fix OpenPGP signature ASCII enarmor normalization.
++ Minore code improvements.
+
+ -- Mattia Rizzolo   Thu, 09 May 2019 17:01:29 +0200
+
 devscripts (2.19.4) unstable; urgency=medium
 
   [ Antonio Terceiro ]
@@ -41,7 +73,7 @@
 + Add KGB options configuration.  Closes: #921641; MR: !115
   * uscan:
 + Fix bad check for "verbose" in Config.pm.  Closes: #923441; MR: !111
-  * Update French translation
+  * Update French translation.
 
   [ Reiner Herrmann ]
   * Update German translation.
diff -Nru devscripts-2.19.4/lib/Devscripts/MkOrigtargz.pm devscripts-2.19.5/lib/Devscripts/MkOrigtargz.pm
--- devscripts-2.19.4/lib/Devscripts/MkOrigtargz.pm	2019-03-01 10:39:51.0 +0100
+++ devscripts-2.19.5/lib/Devscripts/MkOrigtargz.pm	2019-05-09 16:52:33.0 +0200
@@ -307,9 +307,6 @@
 
 # Final step: symlink, copy or rename for signature file.
 
-my $is_ascfile = $self->config->signature_file =~ /\.asc$/i;
-my $is_gpgfile = $self->config->signature_file =~ /\.(gpg|pgp|sig|sign)$/i;
-
 my $destsigfile;
 if ($self->config->signature == 1) {
 $destsigfile = sprintf "%s.asc", $destfile;
@@ -324,22 +321,43 @@
 }
 
 if ($self->config->signature == 1 or $self->config->signature == 2) {
-if ($is_gpgfile) {
-my $enarmor
-  = `gpg --output - --enarmor $self->{config}->{signature_file} 2>&1`;
+my $is_openpgp_ascii_armor = 0;
+my $fh_sig;
+unless (open($fh_sig, '<', $self->config->signature_file)) {
+ds_die "Cannot open $self->{config}->{signature_file}\n";
+return $self->status(1);
+}
+while (<$fh_sig>) {
+if (m/^-BEGIN PGP /) {
+$is_openpgp_ascii_armor = 1;
+last;
+}
+}
+close($fh_sig);
+
+if (not $is_openpgp_ascii_armor) {
+my @enarmor
+  = `gpg --no-options --output - --enarmor $self->{config}->{signature_file} 2>&1`;
 unless ($? == 0) {
 ds_die
-"mk-origtargz: Failed to convert $self->{config}->{signature_file} to *.asc\n";
+"Failed to convert $self->{c

Bug#928111: [pre-approval] unblock: icu/63.2-1

2019-05-05 Thread Mattia Rizzolo
On Sun, May 05, 2019 at 02:25:01PM +0200, Ivo De Decker wrote:
> Secondly, the fact that chromium needs a rebuild suggest there is a change
> that breaks something.
> 
> I suggest you upload the new version to experimental. That way we can look at
> the differences and people can test the new packages.

And check the symbols and other parts of the ABI, as it would be
important to understand why chromium needs a rebuild.

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#927704: unblock: libpodofo/0.9.6+dfsg-5

2019-04-21 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

I uploaded a new libpodofo cherry-picking two security patches from
upstream.

I was waiting to see if more CVEs were going to be fixed, but I guess
the rest will have to wait.

debdiff attached.

-- 
regards,
Mattia Rizzolo

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

 changelog   |8 +
 patches/CVE-2019-9199.patch |   23 
 patches/CVE-2019-9687.patch |   61 
 patches/series  |2 +
 4 files changed, 94 insertions(+)

diff -Nru libpodofo-0.9.6+dfsg/debian/changelog 
libpodofo-0.9.6+dfsg/debian/changelog
--- libpodofo-0.9.6+dfsg/debian/changelog   2019-02-11 18:49:43.0 
+0100
+++ libpodofo-0.9.6+dfsg/debian/changelog   2019-04-21 17:13:10.0 
+0200
@@ -1,3 +1,11 @@
+libpodofo (0.9.6+dfsg-5) unstable; urgency=medium
+
+  * Add upstream patches for security issues:
+CVE-2019-9199 Closes: #923469
+CVE-2019-9687 Closes: #924430
+
+ -- Mattia Rizzolo   Sun, 21 Apr 2019 17:13:10 +0200
+
 libpodofo (0.9.6+dfsg-4) unstable; urgency=medium
 
   * Add upstream patches for security issues:
diff -Nru libpodofo-0.9.6+dfsg/debian/patches/CVE-2019-9199.patch 
libpodofo-0.9.6+dfsg/debian/patches/CVE-2019-9199.patch
--- libpodofo-0.9.6+dfsg/debian/patches/CVE-2019-9199.patch 1970-01-01 
01:00:00.0 +0100
+++ libpodofo-0.9.6+dfsg/debian/patches/CVE-2019-9199.patch 2019-03-27 
15:48:28.0 +0100
@@ -0,0 +1,23 @@
+Description: CVE-2019-9199 - NULL pointer dereference
+Author: Matthew Brincke
+Origin: upstream, https://sourceforge.net/p/podofo/code/1971/
+Bug: https://sourceforge.net/p/podofo/tickets/40/
+Bug-Debian: https://bugs.debian.org/923469
+Bug-Debian: https://security-tracker.debian.org/tracker/CVE-2019-9199
+
+--- a/tools/podofoimpose/pdftranslator.cpp
 b/tools/podofoimpose/pdftranslator.cpp
+@@ -148,7 +148,12 @@
+ //std::cerr << "Document has "<< pcount << " page(s) " << endl;
+   if ( pcount > 0 ) // only here to avoid possible 
segfault, but PDF without page is not conform IIRC
+   {
+-  PoDoFo::PdfRect rect ( sourceDoc->GetPage ( 0 
)->GetMediaBox() );
++PoDoFo::PdfPage* pFirstPage = sourceDoc->GetPage ( 0 );
++if ( NULL == pFirstPage ) // Fixes CVE-2019-9199 (issue #40)
++{
++PODOFO_RAISE_ERROR_INFO( ePdfError_PageNotFound, "First 
page (0) of source document not found" );
++}
++PoDoFo::PdfRect rect ( pFirstPage->GetMediaBox() );
+   // keep in mind it’s just a hint since PDF can 
have different page sizes in a same doc
+   sourceWidth =  rect.GetWidth() - rect.GetLeft();
+   sourceHeight =  rect.GetHeight() - 
rect.GetBottom() ;
diff -Nru libpodofo-0.9.6+dfsg/debian/patches/CVE-2019-9687.patch 
libpodofo-0.9.6+dfsg/debian/patches/CVE-2019-9687.patch
--- libpodofo-0.9.6+dfsg/debian/patches/CVE-2019-9687.patch 1970-01-01 
01:00:00.0 +0100
+++ libpodofo-0.9.6+dfsg/debian/patches/CVE-2019-9687.patch 2019-03-27 
15:56:25.0 +0100
@@ -0,0 +1,61 @@
+Description: CVE-2019-9687 - heap-based buffer overflow in 
PdfString::ConvertUTF16toUTF8
+Origin: upstream, https://sourceforge.net/p/podofo/code/1969
+Bug-Debian: https://bugs.debian.org/924430
+Bug-Debian: https://security-tracker.debian.org/tracker/CVE-2019-9687
+
+--- a/src/base/PdfString.cpp
 b/src/base/PdfString.cpp
+@@ -626,8 +626,19 @@
+ pdf_long lUtf8 = PdfString::ConvertUTF16toUTF8( 
reinterpret_cast(m_buffer.GetBuffer()), 
+ this->GetUnicodeLength(), 
+ 
reinterpret_cast(pBuffer), lBufferLen, ePdfStringConversion_Lenient 
);
++if (lUtf8 + 1 > lBufferLen) // + 1 to account for 2 bytes termination 
here vs. 1 byte there
++{
++pBuffer = static_cast(podofo_realloc( pBuffer, lUtf8 + 1 ) 
);
++if( !pBuffer )
++{
++PODOFO_RAISE_ERROR( ePdfError_OutOfMemory );
++}
++if (lUtf8 - 1 > lBufferLen)
++lUtf8 = PdfString::ConvertUTF16toUTF8( reinterpret_cast(m_buffer.GetBuffer()),
++   
this->GetUnicodeLength(), reinterpret_cast(pBuffer), lUtf8 + 1);
++}
+ 
+-pBuffer[lUt

Re: Summary of the Arm ports BoF at DC18

2019-04-15 Thread Mattia Rizzolo
On Sun, Apr 14, 2019 at 09:06:06PM -0300, Antonio Terceiro wrote:
> can you please add Paul? I signed up, but never had the bandwidth to
> actually do anything, and now with DebConf getting closer I will have
> even less time.

ACK, done.

> BTW Amazon also has arm64 instances now so maybe it would be easier to
> use those instead.

I thought one goal was also to avoid being excessively tied to a single
provider?

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


Re: Summary of the Arm ports BoF at DC18

2019-04-14 Thread Mattia Rizzolo
Hi,

On Sun, Apr 14, 2019 at 09:20:51PM +0200, Paul Gevers wrote:
> On 07-11-2018 20:15, Steve McIntyre wrote:
> >> Currently all the amd64 CI nodes are VM's on Amazon EC2. There is
> >> currently no arrangement for hosting actual hardware.
> > 
> > Right. I didn't realise that. In that case for arm*, would VMs on
> > packet.net or similar work for us then?
> 
> While I was at the BSP in Paris, you promised ivodd that you would pass
> us credentials for (I assume) packet.net. I assume you either didn't
> have time yet, or forgot. In the latter case consider this a polite ping.

I'm assuming you are talking about the packet.net stuff that has been
provided to debian.  TBOMK  nothing is using those credits atm.  I have
admin access to the project and the team, so I can add you
(incidentally, I don't see Steve in the least, so I wouldn't know how he
would do it; there is only zumbi as an "owner", me as an "admin" and a
few other people as "collaborator", including terceiro - so I expected
you as a Debian CI to already have access).

Could you please check with terceiro?  He should have been CCed in a
private thread back then, otherwise feel free to get in touch with me.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#926224: unblock pbuilder/0.230.4

2019-04-02 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

it seems we accidentally introduced a serious bug in the last upload.
Luckily the fix is trivial, but it was reported privately to me too late
to block the migration to testing.

anyway, here is the diff:


diffstat for pbuilder-0.230.3 pbuilder-0.230.4

 debian/changelog|8 
 pbuilder-createbuildenv |   12 
 2 files changed, 16 insertions(+), 4 deletions(-)

diff -Nru pbuilder-0.230.3/debian/changelog pbuilder-0.230.4/debian/changelog
--- pbuilder-0.230.3/debian/changelog   2019-03-26 15:44:52.0 +0100
+++ pbuilder-0.230.4/debian/changelog   2019-04-02 11:32:38.0 +0200
@@ -1,3 +1,11 @@
+pbuilder (0.230.4) unstable; urgency=medium
+
+  * createbuildenv:
++ Only try to print debootstrap.log if the file really exists.
++ Properly handle the case of a disabled internal cache.  Closes: #926115
+
+ -- Mattia Rizzolo   Tue, 02 Apr 2019 11:32:38 +0200
+
 pbuilder (0.230.3) unstable; urgency=medium

   [ Marcin Sulikowski ]
diff -Nru pbuilder-0.230.3/pbuilder-createbuildenv 
pbuilder-0.230.4/pbuilder-createbuildenv
--- pbuilder-0.230.3/pbuilder-createbuildenv2019-03-15 15:33:18.0 
+0100
+++ pbuilder-0.230.4/pbuilder-createbuildenv2019-04-02 11:25:17.0 
+0200
@@ -75,16 +75,20 @@
 if ! ( "${DEBOOTSTRAP}" \
 ${ARCHITECTURE:+--arch=$ARCHITECTURE} \
 --include=apt \
-"$USE_CACHE" \
+${USE_CACHE:+"$USE_CACHE"} \
 "${DEBOOTSTRAPOPTS[@]}" \
 "$DISTRIBUTION" \
 "$BUILDPLACE" \
 "$MIRRORSITE" \
 $DEBOOTSTRAPSCRIPT ) ; then
 log.e "$DEBOOTSTRAP failed"
-log.e "Tail of debootstrap.log:"
-tail -n 50 "$BUILDPLACE/debootstrap/debootstrap.log"
-log.e "End of debootstrap.log"
+if [ -f "$BUILDPLACE/debootstrap/debootstrap.log" ]; then
+log.e "Tail of debootstrap.log:"
+tail -n 50 "$BUILDPLACE/debootstrap/debootstrap.log"
+log.e "End of debootstrap.log"
+else
+log.e "debootstrap.log not present"
+fi
 exit 1
 fi



-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#925613: unblock: strip-nondeterminism/1.1.2-1

2019-03-27 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear RT,

please consider unblocking strip-nondeterminism; the version in unstable
is a minimal thing fixing a single bug.  Full diff:

diffstat for strip-nondeterminism-1.1.1 strip-nondeterminism-1.1.2

 debian/changelog|8 
 lib/File/StripNondeterminism.pm |4 ++--
 2 files changed, 10 insertions(+), 2 deletions(-)

diff -Nru strip-nondeterminism-1.1.1/debian/changelog 
strip-nondeterminism-1.1.2/debian/changelog
--- strip-nondeterminism-1.1.1/debian/changelog 2019-02-13 09:31:59.0 
+0100
+++ strip-nondeterminism-1.1.2/debian/changelog 2019-03-12 18:47:40.0 
+0100
@@ -1,3 +1,11 @@
+strip-nondeterminism (1.1.2-1) unstable; urgency=medium
+
+  * Call file(1) with the "--" argument placeholder to fix normalisation of
+files starting with a hyphen.
+(Closes: reproducible-builds/strip-nondeterminism#6, #924407)
+
+ -- Chris Lamb   Tue, 12 Mar 2019 17:47:40 +
+
 strip-nondeterminism (1.1.1-1) unstable; urgency=medium

   * dh_strip_nondeterminism: Deduplicate hardlinks via stat(2) to avoid issues
diff -Nru strip-nondeterminism-1.1.1/lib/File/StripNondeterminism.pm 
strip-nondeterminism-1.1.2/lib/File/StripNondeterminism.pm
--- strip-nondeterminism-1.1.1/lib/File/StripNondeterminism.pm  2019-02-13 
09:29:48.0 +0100
+++ strip-nondeterminism-1.1.2/lib/File/StripNondeterminism.pm  2019-03-12 
18:47:00.0 +0100
@@ -25,7 +25,7 @@

 our($VERSION, $canonical_time, $clamp_time);

-$VERSION = '1.1.1'; # <https://semver.org/>
+$VERSION = '1.1.2'; # <https://semver.org/>

 sub init() {
$ENV{'TZ'} = 'UTC';
@@ -35,7 +35,7 @@
 sub _get_file_type($) {
my $file=shift;
open(FILE, '-|') # handle all filenames safely
- || exec('file', $file)
+ || exec('file', '--', $file)
  || die "can't exec file: $!";
my $type=;
close FILE;


-- 
regards,
    Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#925536: unblock: pbuilder/0.230.3

2019-03-26 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertag: unblock

Dear RT,

please unblock pbuilder/0.230.3, fixing a couple of bugs.
You could argue they are minor, but at least the systemd slice thingy,
and the cross-build one are quite annoying.

The other two new "features" are tiny and easily reviewable (and the
more scary one is covered by the testsuite).

Thanks for considering.

-- 
regards,
        Mattia Rizzolo

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

 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/Documentation/pbuilder-doc.de.po   |4 -
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/Documentation/pbuilder-doc.fr.po   |2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/Documentation/pbuilder-doc.ja.po   |2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/Documentation/pbuilder-doc.po  |2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/Documentation/pbuilder-doc.xml |2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/debian/changelog   |   29 +++
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/debian/control |2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder-apt-config|2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder-buildpackage  |4 -
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder-buildpackage-funcs|   33 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder-checkparams   |2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder-createbuildenv|6 +
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder-modules   |4 -
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder.8 |3 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/t/test_pbuilder-buildpackage-funcs |   23 +-
 t/data/fool's \"data /dsc   |   37 ++
 16 files changed, 125 insertions(+), 32 deletions(-)

diff -Nru pbuilder-0.230.2/debian/changelog pbuilder-0.230.3/debian/changelog
--- pbuilder-0.230.2/debian/changelog	2019-02-28 16:42:09.0 +0100
+++ pbuilder-0.230.3/debian/changelog	2019-03-26 15:44:52.0 +0100
@@ -1,9 +1,38 @@
+pbuilder (0.230.3) unstable; urgency=medium
+
+  [ Marcin Sulikowski ]
+  * buildpackage-funcs: Fix whitespace handling in .dsc paths.  MR: !4
+
+  [ Hideki Yamane ]
+  * createbuildenv:
++ Use packages from APTCACHE during debootstrap.  Closes: #432088; MR: !6
+  * doc:
++ Use deb.debian.org as defalut example.  MR: !5
+  * pbuilder.8:
++ Mention qemu-debootstrap as a valid --debootstrap option.  MR: !7
+
+  [ Mattia Rizzolo ]
+  * modules:
++ Always call `systemctl stop` if using systemd's cgroups, preventing
+  stray slices from being left behind.
+
+  [ James Clarke ]
+  * buildpackage-funcs:
++ While setting up the cross-build env, only look at installed bin:gcc,
+  not all available ones.
++ Print a useful error if GCC version detection fails.
++ Handle minor GCC versions and unversioned GCC dependencies.
+
+ -- Mattia Rizzolo   Tue, 26 Mar 2019 15:44:52 +0100
+
 pbuilder (0.230.2) unstable; urgency=medium
 
   [ Mattia Rizzolo ]
   * buildpackage:
 + Fixup the dpkg-dev 1.13.19 check for dpkg-source not supporting
   specifying the extraction directory.  Closes: #918368
++ Do not hardcode libstdc++-6-dev while setting up a cross-build
+  environment, instead check at runtime which version to use.
   Thanks to Helmut and James for finding the (maybe) best formula.
   * d/control:
 + Bump Standards-Version to 4.3.0, no changes needed.
diff -Nru pbuilder-0.230.2/debian/control pbuilder-0.230.3/debian/control
--- pbuilder-0.230.2/debian/control	2019-02-21 11:40:54.0 +0100
+++ pbuilder-0.230.3/debian/control	2019-03-15 15:33:18.0 +0100
@@ -24,7 +24,7 @@
 Architecture: all
 Multi-Arch: foreign
 Depends:
- debootstrap | cdebootstrap,
+ debootstrap (>= 1.0.97) | cdebootstrap,
  dpkg-dev (>= 1.17.0),
  ${misc:Depends},
 Recommends:
diff -Nru pbuilder-0.230.2/Documentation/pbuilder-doc.de.po pbuilder-0.230.3/Documentation/pbuilder-doc.de.po
--- pbuilder-0.230.2/Documentation/pbuilder-doc.de.po	2018-11-23 11:51:49.0 +0100
+++ pbuilder-0.230.3/Documentation/pbuilder-doc.de.po	2019-03-15 15:29:22.0 +0100
@@ -2359,11 +2359,11 @@
 #, no-wrap
 msgid ""
 "pbuilder create --distribution sid --debootstrapopts --arch --debootstrapopts i386 \\\n"
-"  --basetgz /var/cache/pbuilder/base-i386.tgz --mirror http://ftp.jp.debian.org/debian\n"
+"  --basetgz /var/cache/pbuilder/base-i386.tgz --mirror http://deb.debian.org/debian\n"
 "linux32 pbuilder build --basetgz /var/cache/pbuilder/base-i386.tgz"
 msgstr ""
 "pbuilder create --dis

Bug#925219: unblock: sigil/0.9.13-1

2019-03-21 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Dear RT,

I've just uploaded a sigil/0.9.13-1, with the latest upstream release.

It's a mostly bugfix release, that once stripped of the doc changes and
translation updates boils down to
 57 files changed, 643 insertions(+), 883 deletions(-)

According to upstream, 0.9.12 (released in February) is "very buggy"
(https://github.com/Sigil-Ebook/Sigil/wiki#versions-0911-and-0912-of-sigil-are-very-buggy)
and are not quite fit for usage.

Also, there is finally built-in support for system-wide mathjs, so we
are not patch-free, which is a great thing by itself for me :)

Please find attached the stripped down debdiff created with
/usr/bin/debdiff sigil_0.9.12+dfsg-1.dsc sigil_0.9.13+dfsg-1.dsc | 
filterdiff -x '*/ts/*' | filterdiff -x '*/docs/*'

Thanks for considering.

-- 
regards,
        Mattia Rizzolo

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

 CMakeLists.txt |2 
 ChangeLog.txt  |   23 
 README.md  |2 
 appveyor.yml   |   13 
 debian/changelog   |   11 
 debian/control |2 
 debian/copyright   |8 
 debian/patches/mathajx |   50 -
 debian/patches/series  |1 
 debian/rules   |3 
 debian/sigil-data.install  |1 
 internal/gumbo/tokenizer.c |6 
 src/CMakeLists.txt |   40 
 src/Dialogs/ClipEditor.cpp |   22 
 src/Dialogs/ClipboardHistorySelector.cpp   |3 
 src/Dialogs/Reports.cpp|1 
 src/Dialogs/ReportsWidgets/AllFilesWidget.cpp  |7 
 src/Dialogs/ReportsWidgets/AllFilesWidget.h|2 
 src/Dialogs/ReportsWidgets/CSSFilesWidget.cpp  |7 
 src/Dialogs/ReportsWidgets/CSSFilesWidget.h|2 
 src/Dialogs/ReportsWidgets/CharactersInHTMLFilesWidget.cpp |6 
 src/Dialogs/ReportsWidgets/CharactersInHTMLFilesWidget.h   |2 
 src/Dialogs/ReportsWidgets/ClassesInHTMLFilesWidget.cpp|6 
 src/Dialogs/ReportsWidgets/ClassesInHTMLFilesWidget.h  |2 
 src/Dialogs/ReportsWidgets/HTMLFilesWidget.cpp |7 
 src/Dialogs/ReportsWidgets/HTMLFilesWidget.h   |2 
 src/Dialogs/ReportsWidgets/ImageFilesWidget.cpp|7 
 src/Dialogs/ReportsWidgets/ImageFilesWidget.h  |2 
 src/Dialogs/ReportsWidgets/LinksWidget.cpp |6 
 src/Dialogs/ReportsWidgets/LinksWidget.h   |2 
 src/Dialogs/ReportsWidgets/StylesInCSSFilesWidget.cpp  |6 
 src/Dialogs/ReportsWidgets/StylesInCSSFilesWidget.h|2 
 src/Dialogs/SearchEditor.cpp   |   15 
 src/MainUI/FindReplace.cpp |5 
 src/MainUI/FindReplace.h   |1 
 src/MainUI/MainWindow.cpp  |   60 +
 src/MainUI/MainWindow.h|1 
 src/MainUI/PreviewWindow.cpp   |   22 
 src/Misc/CSSInfo.cpp   |   24 
 src/Misc/CSSInfo.h |3 
 src/Misc/EmbeddedPythonPkg.cpp |  617 -
 src/Misc/FilenameDelegate.cpp  |   13 
 src/Misc/SettingsStore.cpp |   10 
 src/MiscEditors/ClipEditorModel.cpp|   99 +-
 src/MiscEditors/ClipEditorModel.h  |1 
 src/MiscEditors/IndexEditorModel.cpp   |  103 +-
 src/MiscEditors/SearchEditorModel.cpp  |  106 +-
 src/Resource_Files/plugin_launchers/python/wrapper.py  |2 
 src/Resource_Files/polyfills/SIGIL_EBOOK_MML_SVG.js|   23 
 src/Resource_Files/windows/version.rc.in   |2 
 src/SourceUpdates/PerformCSSUpdates.cpp|2 
 src/Tabs/TabManager.cpp|   33 
 src/ViewEditors/BookViewPreview.cpp|   17 
 src/ViewEditors/CodeViewEditor.cpp |9 
 sr

Bug#925183: unblock: inkscape/0.92.4-3

2019-03-20 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Hi RT!

I just uploaded an inkscpe fixing a couple of annoyances that I think
would be best if it could be in buster.

tiny debdiff attached, please consider it for unblocking.

unblock inkscape/0.92.4-3

-- 
regards,
Mattia Rizzolo

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

 changelog   |9 +
 control |4 
 patches/series  |1 
 patches/upstream/0008-Show-helpful-message-if-tutorials-are-not-installed.patch |   59 ++
 4 files changed, 71 insertions(+), 2 deletions(-)

diff -Nru inkscape-0.92.4/debian/changelog inkscape-0.92.4/debian/changelog
--- inkscape-0.92.4/debian/changelog	2019-01-24 19:29:41.0 +0100
+++ inkscape-0.92.4/debian/changelog	2019-03-20 21:54:39.0 +0100
@@ -1,3 +1,12 @@
+inkscape (0.92.4-3) unstable; urgency=medium
+
+  * Add patch from upstream master branch to output a useful error if the
+tutorials aren't installed.  LP: #1803021
+  * d/control: switch Recommends from non-existent transfig to fig2dev.
+Closes: #925171
+
+ -- Mattia Rizzolo   Wed, 20 Mar 2019 21:54:39 +0100
+
 inkscape (0.92.4-2) unstable; urgency=medium
 
   [ Matteo F. Vescovi ]
diff -Nru inkscape-0.92.4/debian/control inkscape-0.92.4/debian/control
--- inkscape-0.92.4/debian/control	2019-01-24 19:25:45.0 +0100
+++ inkscape-0.92.4/debian/control	2019-03-20 21:44:41.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian Multimedia Maintainers 
 Uploaders:
- Mattia Rizzolo 
+ Mattia Rizzolo ,
 Build-Depends:
  bash-completion (>= 1:2.1-4.2),
  cmake,
@@ -57,13 +57,13 @@
  ${shlibs:Depends},
 Recommends:
  aspell,
+ fig2dev,
  imagemagick,
  libimage-magick-perl,
  libwmf-bin,
  python-lxml,
  python-numpy,
  python-scour,
- transfig,
 Suggests:
  dia,
  inkscape-tutorials,
diff -Nru inkscape-0.92.4/debian/patches/series inkscape-0.92.4/debian/patches/series
--- inkscape-0.92.4/debian/patches/series	2019-01-24 19:28:14.0 +0100
+++ inkscape-0.92.4/debian/patches/series	2019-02-17 16:16:58.0 +0100
@@ -5,3 +5,4 @@
 upstream/0005-Make-the-command-line-PDF-output-reproducible.patch
 upstream/0006-Fix-typo-s-Distrubute-Distribute.patch
 upstream/0007-Update-the-appstream-metadata-file-from-the-upstream.patch
+upstream/0008-Show-helpful-message-if-tutorials-are-not-installed.patch
diff -Nru inkscape-0.92.4/debian/patches/upstream/0008-Show-helpful-message-if-tutorials-are-not-installed.patch inkscape-0.92.4/debian/patches/upstream/0008-Show-helpful-message-if-tutorials-are-not-installed.patch
--- inkscape-0.92.4/debian/patches/upstream/0008-Show-helpful-message-if-tutorials-are-not-installed.patch	1970-01-01 01:00:00.0 +0100
+++ inkscape-0.92.4/debian/patches/upstream/0008-Show-helpful-message-if-tutorials-are-not-installed.patch	2019-02-17 16:16:58.0 +0100
@@ -0,0 +1,59 @@
+From: Max Gaukler 
+Date: Sun, 10 Feb 2019 15:47:44 +0100
+Subject: Show helpful message if tutorials are not installed
+
+Fixes https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1803021  (for 1.0-alpha)
+
+LP: #1803021
+Signed-off-by: Mattia Rizzolo 
+---
+ po/POTFILES.in |  1 +
+ src/help.cpp   | 11 ++-
+ 2 files changed, 11 insertions(+), 1 deletion(-)
+
+diff --git a/po/POTFILES.in b/po/POTFILES.in
+index 9e305f8..7142d3d 100644
+--- a/po/POTFILES.in
 b/po/POTFILES.in
+@@ -110,6 +110,7 @@ src/file.cpp
+ src/filter-enums.cpp
+ src/gradient-chemistry.cpp
+ src/gradient-drag.cpp
++src/help.cpp
+ src/inkscape.cpp
+ src/knot.cpp
+ src/knotholder.cpp
+diff --git a/src/help.cpp b/src/help.cpp
+index 643945a..50d3696 100644
+--- a/src/help.cpp
 b/src/help.cpp
+@@ -16,11 +16,14 @@
+ #endif
+ 
+ #include 
++#include 
+ 
+ #include "file.h"
+ #include "help.h"
++#include "io/sys.h"
+ #include "path-prefix.h"
+ #include "ui/dialog/aboutbox.h"
++#include "ui/interface.h"
+ 
+ void sp_help_about()
+ {
+@@ -31,7 +34,13 @@ void sp_help_open_tutorial(GtkMenuItem *, void* data)
+ {
+ gchar const *name = static_cast(data);
+ gchar *c = g_build_filename(INKSCAPE_TUTORIALSDIR, name, NULL);
+-sp_file_open(c, NULL, false, false);
++if (Inkscape::IO::file_test(c, G_FILE_TEST_EXISTS)) {
++sp_file_open(c, NULL, false, false);
++} else {
++sp_ui_error_dialog(_("The tutorial files are not installed.\nFor Linux, you may need to install "
++   

Bug#925161: stretch-pu: package diffoscope/78+deb9u1

2019-03-20 Thread Mattia Rizzolo
Package: release.debian.org
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Dear SRM,

I've just uploaded an update to diffoscope, versioned as 78+deb9u1, to
fix the FTBFS caused by the updated ghostscripts that arrived through
stretch-security some months ago.

It's a cherry-pick of several commits that have been in buster for quite
some time already.

I also had to tweak the sanity version check in d/rules; I haven't
documented that change, with it being a completely transparent change to
everything.

Thanks for considering.

-- 
regards,
Mattia Rizzolo

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

 debian/changelog |7 +++
 debian/rules |6 +-
 tests/comparators/test_ps.py |   23 +++
 tests/data/ps_text_expected_diff |   11 ---
 4 files changed, 35 insertions(+), 12 deletions(-)

diff -Nru diffoscope-78/debian/changelog diffoscope-78+deb9u1/debian/changelog
--- diffoscope-78/debian/changelog	2017-02-26 17:26:48.0 +0100
+++ diffoscope-78+deb9u1/debian/changelog	2019-03-20 17:27:42.0 +0100
@@ -1,3 +1,10 @@
+diffoscope (78+deb9u1) stretch; urgency=medium
+
+  * tests:
++ Fix ps tests to pass with the new ghostscript 9.26.  Closes: #925051
+
+ -- Mattia Rizzolo   Wed, 20 Mar 2019 17:27:42 +0100
+
 diffoscope (78) unstable; urgency=medium
 
   [ Brett Smith ]
diff -Nru diffoscope-78/debian/rules diffoscope-78+deb9u1/debian/rules
--- diffoscope-78/debian/rules	2017-02-13 13:24:56.0 +0100
+++ diffoscope-78+deb9u1/debian/rules	2019-03-20 17:27:42.0 +0100
@@ -14,7 +14,11 @@
  $(error Version in debian/changelog does not match diffoscope version or backport policy)
 endif
   else
-   $(error Version in debian/changelog does not match diffoscope version)
+ifeq ($(DIST),stretch)
+ $(info "Stable update!  ☺")
+else
+ $(error Version in debian/changelog does not match diffoscope version)
+endif
   endif
  endif
 endif
diff -Nru diffoscope-78/tests/comparators/test_ps.py diffoscope-78+deb9u1/tests/comparators/test_ps.py
--- diffoscope-78/tests/comparators/test_ps.py	2017-02-10 23:54:34.0 +0100
+++ diffoscope-78+deb9u1/tests/comparators/test_ps.py	2019-03-20 17:26:47.0 +0100
@@ -18,38 +18,53 @@
 # along with diffoscope.  If not, see <https://www.gnu.org/licenses/>.
 
 import pytest
+import subprocess
 
 from diffoscope.comparators.ps import PsFile
 
 from utils.data import load_fixture, get_data
-from utils.tools import skip_unless_tools_exist
+from utils.tools import skip_unless_tools_exist, \
+skip_unless_tool_is_at_least
 from utils.nonexisting import assert_non_existing
 
 
 ps1 = load_fixture('test1.ps')
 ps2 = load_fixture('test2.ps')
 
+
+def ps2ascii_version():
+return subprocess.check_output(('ps2ascii', '--version')).decode('utf-8')
+
+
 def test_identification(ps1):
 assert isinstance(ps1, PsFile)
 
+
+@skip_unless_tool_is_at_least('ps2ascii', ps2ascii_version, '9.21')
 def test_no_differences(ps1):
 difference = ps1.compare(ps1)
 assert difference is None
 
+
 @pytest.fixture
 def differences(ps1, ps2):
 return ps1.compare(ps2)
 
-@skip_unless_tools_exist('ps2ascii')
+
+@skip_unless_tool_is_at_least('ps2ascii', ps2ascii_version, '9.21')
 def test_internal_diff(differences):
 expected_diff = get_data('ps_internal_expected_diff')
 assert differences.unified_diff == expected_diff
 
-@skip_unless_tools_exist('ps2ascii')
+
+@skip_unless_tool_is_at_least('ps2ascii', ps2ascii_version, '9.26')
 def test_text_diff(differences):
+computed_diff = differences.details[0].unified_diff.replace('\r\n', '\n')
 expected_diff = get_data('ps_text_expected_diff')
-assert differences.details[0].unified_diff == expected_diff
+assert computed_diff == expected_diff
+
 
 @skip_unless_tools_exist('ps2ascii')
+@skip_unless_tool_is_at_least('ps2ascii', ps2ascii_version, '9.21')
 def test_compare_non_existing(monkeypatch, ps1):
 assert_non_existing(monkeypatch, ps1, has_null_source=False)
diff -Nru diffoscope-78/tests/data/ps_text_expected_diff diffoscope-78+deb9u1/tests/data/ps_text_expected_diff
--- diffoscope-78/tests/data/ps_text_expected_diff	2017-01-14 11:59:14.0 +0100
+++ diffoscope-78+deb9u1/tests/data/ps_text_expected_diff	2019-03-20 17:26:29.0 +0100
@@ -1,7 +1,4 @@
-@@ -1,5 +1,5 @@
- 
- 
--Today's date: February 28, 2016
-+Today's date: February 27, 2016
- 
- 1
+@@ -1,2 +1,2 @@
+-Today’s date: February 28, 2016
++Today’s date: February 27, 2016
+1


signature.asc
Description: PGP signature


Bug#924320: unblock: dehydrated/0.6.2-2

2019-03-11 Thread Mattia Rizzolo
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Dear RT,

please consider unblocking this revision of dehydrated.
I cherry-picked a few patches from upstream, fixing bugs in a few corner
cases, plus doc updates.

Full debdiff attached.

unblock dehydrated/0.6.2-2

-- 
regards,
Mattia Rizzolo

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

 changelog   |   14 +++
 control |2 
 patches/Fixes-559-when-HTTP-2-is-used-header-names-are-lower-case.patch |   34 +++
 patches/Only-match-Replace-Nonce-header-at-beginning-of-line.patch  |   24 +
 patches/document-DOMAINS_D-parameter-in-example-config-fixes-575-.patch |   25 +
 patches/fixed-a-bug-that-resulted-in-a-deleted-domains.txt-when-u.patch |   22 +
 patches/implement-POST-as-GET-closes-626.patch  |   43 ++
 patches/series  |6 +
 patches/tiny-documentation-fix-per-certificate-config-can-overrid.patch |   21 
 9 files changed, 190 insertions(+), 1 deletion(-)

diff -Nru dehydrated-0.6.2/debian/changelog dehydrated-0.6.2/debian/changelog
--- dehydrated-0.6.2/debian/changelog	2018-05-08 12:14:45.0 +0200
+++ dehydrated-0.6.2/debian/changelog	2019-03-11 16:25:53.0 +0100
@@ -1,3 +1,17 @@
+dehydrated (0.6.2-2) unstable; urgency=medium
+
+  * Add a number of patches from upstream.
+Fixing the following bugs:
+ + HTTP/2 support, where header names are lowercase
+ + Avoid over matching, checking for the Replay-Nonce header only at BOL
+ + A bug causing deletion of domains.txt when incorrect parameters are used
+ + Document the DOMAINS_D config option
+ + Impoent POST-as-GET, for the upcoming change in LE's API
+ + Document PRIVATE_KEY_ROLLOVER per-cert config option
+  * d/control: bump Standards-Version to 4.3.0, no changes needed.
+
+ -- Mattia Rizzolo   Mon, 11 Mar 2019 16:25:53 +0100
+
 dehydrated (0.6.2-1) unstable; urgency=medium
 
   * New upstream release 0.6.2.
diff -Nru dehydrated-0.6.2/debian/control dehydrated-0.6.2/debian/control
--- dehydrated-0.6.2/debian/control	2018-05-08 12:10:08.0 +0200
+++ dehydrated-0.6.2/debian/control	2019-03-11 16:25:53.0 +0100
@@ -10,7 +10,7 @@
  debhelper (>= 11),
  dh-apache2,
  dh-exec,
-Standards-Version: 4.1.4
+Standards-Version: 4.3.0
 Rules-Requires-Root: no
 Vcs-Git: https://salsa.debian.org/letsencrypt-team/dehydrated.git
 Vcs-Browser: https://salsa.debian.org/letsencrypt-team/dehydrated
diff -Nru dehydrated-0.6.2/debian/patches/document-DOMAINS_D-parameter-in-example-config-fixes-575-.patch dehydrated-0.6.2/debian/patches/document-DOMAINS_D-parameter-in-example-config-fixes-575-.patch
--- dehydrated-0.6.2/debian/patches/document-DOMAINS_D-parameter-in-example-config-fixes-575-.patch	1970-01-01 01:00:00.0 +0100
+++ dehydrated-0.6.2/debian/patches/document-DOMAINS_D-parameter-in-example-config-fixes-575-.patch	2019-03-11 16:21:33.0 +0100
@@ -0,0 +1,25 @@
+From: Lukas Schauer 
+Date: Sat, 20 Oct 2018 13:05:20 +0200
+Subject: document DOMAINS_D parameter in example config (fixes #575,
+ closes #582)
+
+---
+ docs/examples/config | 5 +
+ 1 file changed, 5 insertions(+)
+
+diff --git a/docs/examples/config b/docs/examples/config
+index 665704d..c1f9276 100644
+--- a/docs/examples/config
 b/docs/examples/config
+@@ -40,6 +40,11 @@
+ # default: 
+ #CONFIG_D=
+ 
++# Directory for per-domain configuration files.
++# If not set, per-domain configurations are sourced from each certificates output directory.
++# default: 
++#DOMAINS_D=
++
+ # Base directory for account key, generated certificates and list of domains (default: $SCRIPTDIR -- uses config directory if undefined)
+ #BASEDIR=$SCRIPTDIR
+ 
diff -Nru dehydrated-0.6.2/debian/patches/fixed-a-bug-that-resulted-in-a-deleted-domains.txt-when-u.patch dehydrated-0.6.2/debian/patches/fixed-a-bug-that-resulted-in-a-deleted-domains.txt-when-u.patch
--- dehydrated-0.6.2/debian/patches/fixed-a-bug-that-resulted-in-a-deleted-domains.txt-when-u.patch	1970-01-01 01:00:00.0 +0100
+++ dehydrated-0.6.2/debian/patches/fixed-a-bug-that-resulted-in-a-deleted-domains.txt-when-u.patch	2019-03-11 16:21:33.0 +0100
@@ -0,0 +1,22 @@
+From: Lukas Schauer 
+Date: Sat, 20 Oct 2018 12:27:23 +0200
+Subject: fixed a bug that resulted in a deleted domains.txt when using
+ incorrect parameters in combination with signcsr (fixes #597)
+
+---
+ dehydrated | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --

Re: Advocating for unstable->testing flow

2019-03-07 Thread Mattia Rizzolo
Hi,

On Thu, Mar 07, 2019 at 09:55:00AM +0100, Filippo Rusconi wrote:
> Greetings, Fellow Debianites and Release Managers,
> 
> I would like to advocate for two pacakges to enter testing if no critical bugs
> are found in them:

Please file a proper unblock bug for each of them, stating your case
there.
Mails in the mailing list are easily overlooked, and the regular process
asks for bugs anyway.

> - isospec: a very small library for science;

This one is already in buster, and looking at the changelog I think it
should really be unblocked (using -march is a RC bug, you should
actually file one affecting the version in buster and fixed in
unstable…)

> - daps: an all-architecture package to build documentation;

-- 
regards,
        Mattia Rizzolo

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


signature.asc
Description: PGP signature


  1   2   3   >