Bug#929606: ITP: dataset-fashion-mnist -- (DL-Policy) A MNIST-like fashion product database.

[Mo Zhou]

Package: wnpp
Severity: wishlist
Owner: Mo Zhou 

* Package name: dataset-fashion-mnist
* URL : https://github.com/zalandoresearch/fashion-mnist
* License : MIT
  Description : A MNIST-like fashion product database.

This is a part of DL-Policy[1]'s experiments.

The first, typical dataset used by everyone who started to learn machine
learning and deep learning is very possibly MNIST[2].  MNIST had been
used for over 30 years by researchers and engineers to valiate their
algorithms and learning frameworks, etc. However, The original MNIST
dataset doesn't have (I didn't find it) an explict license. And I have
to use an alternative -- the modern replacement of that MNIST dataset,
i.e. fashion-mnist. It has an explicit MIT license.

Packaging this dataset is to some extent meaningful:

  1. Dataset size: ~30MiB. Very friendly to any modern storage devices.
  2. A "UnitTest" dataset for virtually any deep learning framework.
 Developers can use this dataset to validate any machine learning
 or deep learning frameworks.
  3. Very easy to train and validate. This is a tiny "toy" dataset.
 A weak CPU can train models on this dataset in a reasonable timeframe.
  4. As an DL-Policy-compliant dataset package example.
  5. The dataset it self is frozen. Subsequent maintainance burden after
 the initial upload is nearly zero ...

See also:
https://github.com/zalandoresearch/fashion-mnist#why-we-made-fashion-mnist

[1] https://salsa.debian.org/lumin/deeplearning-policy
[2] http://yann.lecun.com/exdb/mnist/

Re: Consensus Call: Do We Want to Require or Recommend DH; comments by 2019-06-16

[Scott Kitterman]

On May 25, 2019 5:26:47 PM UTC, Sam Hartman  wrote:
>
>Hi. Almost two weeks ago [1] I  started a discussion on whether we
>wanted to increase the strength of our recommendation of the dh
>sequencer from debhelper.
>This message is a consensus call summarizing my reading of the
>discussion.
...
>
>Please send any comments by 2019-06-16.
>Please distinguish cases where you believe I've misread the discussion
>from new contributions intended to change the community's view.
>
>...
>Is Not Using DH a Bug?
>==
>
>It's certainly not an RC bug.  There was some talk of it eventually
>being an RC bug if a new package doesn't use DH (and doesn't fall under
>an exception).  I don't think there's consensus for that today.
>
>It's obviously not a bug if one of the exceptions applies, but once the
>lintian tag exists, overriding that tag sounds to me like best practice
>to document the exception.  (Presumably for things like Haskell we'd
>want Lintian to be smart enough to figure that out on its own)
>
>To some extent I'm extrapolating from implications of the rest of the
>consensus call for the rest of this section.  There was some discussion
>of whether not using dh should be a normal bug, but the comments about
>that were inconsistent with the rest of the discussion.  But if the
>consensus call above that existing packages (absent exceptional
>circumstances) should use dh stands, that's approximately the
>definition
>of a normal bug.  So my reading is that absent exceptional
>circumstances, not using dh is a normal severity bug.
>
>It doesn't mean you should file that bug and it doesn't mean that you
>should go fix that bug.  We definitely didn't get the kind of support
>we'd be needing for a mass bug filing or anything like that.  It
>wouldn't serve a point.  This isn't atypical.  There are a lot of
>things
>lintian flags that are technically bugs, but we wouldn't want to mass
>file all lintian tags (even if we could filter out false positives) as
>bugs.
>
>This paragraph is very much my interpretation.  I'd personally say that
>if you're going to file a bug that a particular package doesn't use dh,
>have a good reason and document it in that bug.  Your reason might be
>"I
>want to contribute; I'm willing to dedicate time and updating the
>packaging would make it much more appealing to work on."  Often your
>reason will be that there's some other problem, migrating to dh will
>fix
>that problem, and between the time you're willing to spend and the time
>you hope the maintainer will spend it's worth doing a good job of that
>migration.
>
>My interpretation of our standard practices is that maintainers have
>wide discretion in which bugs they work on.  That said, if someone
>submits a patch, it's good if you review it.  It's fine to ask them to
>do the necessary testing work and it's fine to hold them to the same
>high standards that you hold yourself to.  If they are less experienced
>with the package it might make sense for them to do tests that make up
>for that experience gap.  None of this  changes any of that or asks
>maintainers to treat bugs about dh differently than other bugs.

On what basis is it a bug of any kind?

A lintian check does not a buggy package make.

Assuming a package that is otherwise working correctly, you have a policy 
compliant, fully functional package.  That seems to me like the very definition 
of not a bug.

If we want to make not using dh except in certain situations a bug, it seems 
like something for a policy should kind of item.  We have an existing process 
for updating policy, so this should probably be kicked over there for further 
evaluation.

Scott K

Re: Consensus Call: Do We Want to Require or Recommend DH; comments by 2019-06-16

[Andreas Tille]

On Sun, May 26, 2019 at 07:28:55PM +0200, Vincent Bernat wrote:
> > We "uphold this reputation" by maintaining many packages, which is
> > good.
> 
> Do we? I am now using nix to get packages for stuff not in Debian. Our
> package count is artificially inflated by *-perl packages, golang-*
> packages which may not be present in some other distributions. But for
> some ecosystems, we are severely behind. We may argue we are better on
> some metrics, but this has nothing to do with the fact we have so many
> ways to build a package.

Some Debian Med people are concerned about the droping usage of Debian
Med packages since people prefer BioConda[1] over it.  There is even a
scientific paper (I've only seen a printed version not online yet) who
compares ways to package biology software.  We are way better than other
distributions - but we are lagging begind BioConda a lot.  We have some
upstreams who are doing Debian packaging by the help of the Debian Med
team but that's just a minor fraction.  Lots of BioConda packages are
maintained by Upstream since they consider it easy.

In short:  Our "reputation" is scaring people away to favour other
techniques. 

Kind regards

   Andreas.

[1] https://bioconda.github.io/

-- 
http://fam-tille.de

Accepted dgit 8.5 (all source) into unstable

[Ian Jackson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 May 2019 00:20:58 +0100
Source: dgit
Binary: dgit git-debrebase dgit-infrastructure
Architecture: all source
Version: 8.5
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Closes: 929549
Description: 
 dgit   - git interoperability with the Debian archive
 dgit-infrastructure - dgit server backend infrastructure
 git-debrebase - rebasing git workflow tool for Debian packaging
Changes:
 dgit (8.5) unstable; urgency=medium
 .
   * Replace `confess $!' with `confess "$!"', to actually print errno
 when crashing.  Closes:#929549.
Checksums-Sha1: 
 d90f5afc6e62bd4993d7e931fa82fbc32abd519a 1665 dgit_8.5.dsc
 ac8b5873e26713aeb2a1280d2da8b040b551015d 667324 dgit_8.5.tar.gz
 7025da430801026feb7c7abc2721be77a3bfc875 64192 dgit-infrastructure_8.5_all.deb
 bf130b4629931b8ddee1de559465132d2c217b3e 210876 dgit_8.5_all.deb
 ef8d605c7d1e8ec0eadf7a37b476bdff72090068 5855 dgit_8.5_amd64.buildinfo
 da1f8c99e3f74e87e80c099fdb259e81267fda87 92856 git-debrebase_8.5_all.deb
Checksums-Sha256: 
 7a7f876d7b79bbb12623e14f075b5a4892cf84880be882887dffad9b1b50046b 1665 
dgit_8.5.dsc
 5a75b7a86c5cc4fb8e8c39433f89bf6bd427ca91604c8369a394599760690593 667324 
dgit_8.5.tar.gz
 037d41c217d1f8cc18b8b40e9f82e445fc90639be95f8b9486febf17ccd08bf3 64192 
dgit-infrastructure_8.5_all.deb
 741b9b21ca392db4916e1889097954e9d3d774172cef2c7b991151c924eedc1a 210876 
dgit_8.5_all.deb
 99523b8b85d7f3648d0b9075b5c868adc45c08ed030ff0cd7fce2e70c9521424 5855 
dgit_8.5_amd64.buildinfo
 8542a15512ad4e015c66d227a98e9077168f522ffb224dd1edec1f5ba00765b8 92856 
git-debrebase_8.5_all.deb
Files: 
 472868a4d17827640cd41d5c3bf48cc2 1665 devel optional dgit_8.5.dsc
 e29a71b6cca6890294550f1bcc6c8bb8 667324 devel optional dgit_8.5.tar.gz
 30790f6ec6ec42d0eb4607d828ab1c0d 64192 devel extra 
dgit-infrastructure_8.5_all.deb
 14718c7fb12c203f299c3b6649c6f6b3 210876 devel optional dgit_8.5_all.deb
 2b9b41a1f636bb2ed220a2104797d9b5 5855 devel optional dgit_8.5_amd64.buildinfo
 acff5a4580be48f826acb6de45b78f80 92856 devel optional git-debrebase_8.5_all.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAlzrIBwACgkQ4+M5I0i1
DTl59wf/fYok8zyXFugD5PQ7i/gb9U/XbPKKRZnv/PDxFcveJjRoHYcwvEPGOhD/
7DunHM6BsAQImu0ARUW/nO4eE0Dkv9gcH7M0zbYrLqqXpePeK8fnkDBZCbgoMxDF
ad4akesxWX2QmORq0E/irZK2lhVTR5TR5VJxAJlGMu4Fk+MdWriz1TH5NjMPRMaK
Ulr/UnOmbUbvuNTEn3R9qeGSgw+GPBrBskU/IHhXp236LBtKTMY7Plx4ymFWprpG
zfPyksSWhiVs7Z5fFiZx/aDbMljmiTRqV4/s2L5ZCOqeVZR2wwyyiPHTkqa1e0kF
uJrY3Wg9n1QtKSwQcW+o65KabkcBmA==
=kf5I
-END PGP SIGNATURE-

Re: Difficult Packaging Practices

[Russ Allbery]

Sam Hartman  writes:

> I think it's a combination of a lot of things.  We have high standards,
> a lot of complexity, and you have to get most or all of that right to
> contribute.  You have to have a package that meets our standards.  You
> have to have a copyright file that meets our standards.  You have to be
> able to figure out our processes.  You have to be willing to follow our
> processes.  And you eventually have to deal with the PGP mess.

> If you don't find value in the things where we have high standards,
> Debian doesn't make a lot of sense.  If you just want to get upstream's
> idea of their package onto a system with their release schedule and
> their recommended dependency versions, there are better ways than
> getting a package into Debian.

This is my experience as well.  I've occasionally tried to get people at
work (at various jobs) interested in packaging software for Debian,
without all that much success.  The problem seems less any one specific
thing and more that they're perfectly content with a Debian package
created by running fpm on some install tree, and don't see the point in
doing any more work than that.  This is usually in the context where
there's some other config management system in use, so to them all the
packaging format is good for is as a container of files with a version
number attached.

It's not that they don't understand the merits of having what they think
of as the base operating system properly maintained and integrated; it's
more that they don't see any value in doing that work for the incremental
thing that they're adding.  They cobble together some combination of local
config management and a deployment method until it works and then move on
to some (from their perspective) more interesting problem.

-- 
Russ Allbery (r...@debian.org)   

Re: Difficult Packaging Practices

[Jérémy Lal]

Le dim. 26 mai 2019 à 23:01, Sam Hartman  a écrit :

> > "Adrian" == Adrian Bunk  writes:
>
> Adrian> It is a problem for people making their first contributions
> Adrian> to Debian to get them into unstable. The problem here is
> Adrian> lack of sponsors willing to do proper reviews and then
> Adrian> uploads. Usually the package in question is already using
> Adrian> dh.
>
> My experience is consistent with the above.
> I can't send links because most of my conversations with people getting
> started contributing to Debian  have been that: actual conversations
> with lungs compressing air to blow out mouths.
>
> Unfortunately, I've found that it's often a combination of factors.
>
> The one first cited is  the difficulty finding a sponsor.
>

There's a gap between getting some unknown software into debian,
and getting well-known software into debian.
Some well-determined upstream develop can manage to get software
into debian, and even get it into stable, and then just quit maintaining it
!
On the other hand, when a fellow DD uploads a software it usually means
that piece is worth it. So i'm not that keen on making it easier to get any
kind
of software into debian.


> But in at least some cases it's more complex than that.
>
> for example in one case someone was talking about finding a sponsor.  I
> said that I didn't normally sponsor packages I couldn't adequately test,
> so that limited what I'd sponsor, but if the contributor could find
> something within that set I'd sponsor it.
>
> He came up with something.
> Then he said but really the hard part there was not the sponsorship, but
> the dependency problem
> Apparently upstream had forked some library already in Debian and you
> had to use the fork for the package to work.
>

It might also mean the upstream software is still maturing and not ready for
prime time.

I think it's a combination of a lot of things.  We have high standards,
> a lot of complexity, and you have to get most or all of that right to
> contribute.  You have to have a package that meets our standards.  You
> have to have a copyright file that meets our standards.


When it's hard to make upstream conform to DFSG it's either easy to fix,
or impossible to fix. So it's not that hard to deal with.


> You have to be
> able to figure out our processes.  You have to be willing to follow our
> processes.  And you eventually have to deal with the PGP mess.
>

Are you referring to the identity check ?
That mess is onto the uploader's hand.
You don't need to have your identity checked as an upstream author, and
the identity check is the best part of subscribing to a community.


> If you don't find value in the things where we have high standards,
> Debian doesn't make a lot of sense.
> If you just want to get upstream's idea of their package onto a system
> with their release schedule and their recommended dependency versions,
> there are better ways than getting a package into Debian.
>

There are even ways that are supported by software available in Debian !
(thinking of flatpak but many other ways to allow users to install software
easily).

--
Jérémy

Accepted dpkg-cross 2.6.15-3 (source all) into unstable

[Wookey]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 26 May 2019 22:33:37 +0100
Source: dpkg-cross
Binary: cross-config dpkg-cross libdebian-dpkgcross-perl
Architecture: source all
Version: 2.6.15-3
Distribution: unstable
Urgency: medium
Maintainer: Wookey 
Changed-By: Wookey 
Description:
 cross-config - autotools support for cross-compilation
 dpkg-cross - tools for cross compiling Debian packages
 libdebian-dpkgcross-perl - functions to aid cross-compiling Debian packages
Closes: 868483
Changes:
 dpkg-cross (2.6.15-3) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * cross-config: Ensure that every release arch uses the common file.
 (Closes: #868483)
Checksums-Sha1:
 a0f25d1cbe7626d87f3f4e15893144f95940fc73 1766 dpkg-cross_2.6.15-3.dsc
 5ddb3676b47774c0b3376e6bdd6016653ffd0683 75123 dpkg-cross_2.6.15-3.tar.gz
 2f78949335214cce66d50f4e299b4f570c04c02a 39908 cross-config_2.6.15-3_all.deb
 3e6cba44ea7e87bee55671c44078013767721822 49344 dpkg-cross_2.6.15-3_all.deb
 12ed5ff13b264a8330f8004e4b7988445d9948b0 5824 
dpkg-cross_2.6.15-3_amd64.buildinfo
 4a448503ef8e076383e051e3e9a0b401959e8c33 38652 
libdebian-dpkgcross-perl_2.6.15-3_all.deb
Checksums-Sha256:
 8ad9e06dd29a724882d1aee358c8ef0f2dbc88493844fba33909283ebd2836e0 1766 
dpkg-cross_2.6.15-3.dsc
 b3ddbc5b2ac43c05332aac74035bb0e994150bbe5c656e2cbfe0bd8a4634e789 75123 
dpkg-cross_2.6.15-3.tar.gz
 a17323352bfbd879831a886b0ec33d40603348b85383a41ad35dfb1134ce0294 39908 
cross-config_2.6.15-3_all.deb
 849a1645098cfeae8c8d0676ab987d4bf5e4060d3ee1042e679fb2c75a879dc6 49344 
dpkg-cross_2.6.15-3_all.deb
 69edbd3bf9f6eb6967af3926accf205c3bcca7dd589e225735b994434cb28443 5824 
dpkg-cross_2.6.15-3_amd64.buildinfo
 b18440a3022e9a78bb06ffecb6aa03900ed47fa131e01fb0cdaa335546ed2572 38652 
libdebian-dpkgcross-perl_2.6.15-3_all.deb
Files:
 72ee43bf0352f0d9a072b64eee292bb2 1766 utils extra dpkg-cross_2.6.15-3.dsc
 5d1a1391d3543c6bc849a17cdef7ce1b 75123 utils extra dpkg-cross_2.6.15-3.tar.gz
 cfb5d8af75a98972a8cc3ebd1568941b 39908 utils extra 
cross-config_2.6.15-3_all.deb
 1188db3931f7710dd3bd1f967ad1c261 49344 utils extra dpkg-cross_2.6.15-3_all.deb
 900cc1d424aad3f51203fe156bd82233 5824 utils extra 
dpkg-cross_2.6.15-3_amd64.buildinfo
 f7dbddf9bcdf0fe96670d8552c4dd1a5 38652 perl extra 
libdebian-dpkgcross-perl_2.6.15-3_all.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEER4nvI8Pe/wVWh5yq+4YyUahvnkcFAlzrBmMSHHdvb2tleUBk
ZWJpYW4ub3JnAAoJEPuGMlGob55HI4wQAMhUbcW2JOeMAb90eTzM+XTCTwHwWfl8
8+h9oSL4nH1Ya1JMIH//gL6kFPDMkiVDj11MkbWki9JA3r2P07EGzbnUOMfaCEAJ
ZWrfofqC/nKLdgqosKFK8cy0DdisfLlS/ZKGXfoESWYNbun0mGt4tpa+fOjb7omF
85ey2XAPt9LnAECzBGpp64zLd10dz2pxH17YtQpgu9Qdh5QzfavK2WiXh5mmnCui
9CHXUFBaK6q/SoxzjmQvVzorhFC4WGyhth582R36O0FIkm0zAlDJzs/TS9dUpWxP
K+xC1TGHvhm7NatOtuKbOGlweIC3H5VsvaGweg1EbhIGOy9mGSZws8PXfXV0V29i
GywU9qbpqzEDDGsMp9sndP/KeeIEBxaDc/6IOPtgocGzT9yuQPKdaHmOxQZPUoEh
jwJCFa19xjAhIkHewfDocEFWmBx7pNoBcJoOtJGBoSb10oTv7ABhs8Y2FWa8M3ww
qQw08ThGZRot9+QBkTrM3Nu2s3W9nq8Xtk/XuffUMHtPuFx9kIAtMuZh/1na3I6X
7cx8y6g8u9EjVeOEAIuKhH4vAq4q6G9hHvA7PspNI+vYfDYD1o9EuQPn7GMPYgTR
qwFStdQtGCLjEwRdVHOj76ayHkfuEnJh7Kbbon7rAn/ypY2oJzOpMzLnRX9wHy5f
sbsR50REQss3
=gmQQ
-END PGP SIGNATURE-

Re: Consensus Call: Do We Want to Require or Recommend DH; comments by 2019-06-16

[Philip Hands]

Adrian Bunk  writes:

...
> Often the most difficult part of packaging are the unique rules the 
> Debian ftp team requires for debian/copyright that are not required in 
> distributions with actual lawyers. That's a completely separate topic.

That seems needlessly snide, and glosses over the fact that we are bound
by constraints that other distributions are not, such as giving a damn
about the license conditions we inflict on our downstreams, which I
suspect the lawyers you allude to are not being retained to contemplate.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Difficult Packaging Practices

[Sam Hartman]

> "Adrian" == Adrian Bunk  writes:

Adrian> It is a problem for people making their first contributions
Adrian> to Debian to get them into unstable. The problem here is
Adrian> lack of sponsors willing to do proper reviews and then
Adrian> uploads. Usually the package in question is already using
Adrian> dh.

My experience is consistent with the above.
I can't send links because most of my conversations with people getting
started contributing to Debian  have been that: actual conversations
with lungs compressing air to blow out mouths.

Unfortunately, I've found that it's often a combination of factors.

The one first cited is  the difficulty finding a sponsor.
But in at least some cases it's more complex than that.

for example in one case someone was talking about finding a sponsor.  I
said that I didn't normally sponsor packages I couldn't adequately test,
so that limited what I'd sponsor, but if the contributor could find
something within that set I'd sponsor it.

He came up with something.
Then he said but really the hard part there was not the sponsorship, but
the dependency problem
Apparently upstream had forked some library already in Debian and you
had to use the fork for the package to work.

I think it's a combination of a lot of things.  We have high standards,
a lot of complexity, and you have to get most or all of that right to
contribute.  You have to have a package that meets our standards.  You
have to have a copyright file that meets our standards.  You have to be
able to figure out our processes.  You have to be willing to follow our
processes.  And you eventually have to deal with the PGP mess.

If you don't find value in the things where we have high standards,
Debian doesn't make a lot of sense.
If you just want to get upstream's idea of their package onto a system
with their release schedule and their recommended dependency versions,
there are better ways than getting a package into Debian.


--Sam

Accepted libhmsbeagle 3.1.2+dfsg-6 (source) into unstable

[Dylan Aïssi]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 26 May 2019 22:06:37 +0200
Source: libhmsbeagle
Architecture: source
Version: 3.1.2+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Dylan Aïssi 
Closes: 929560
Changes:
 libhmsbeagle (3.1.2+dfsg-6) unstable; urgency=medium
 .
   * Team upload.
   * Replace DEB_HOST_GNU_TYPE by DEB_HOST_MULTIARCH
 Closes: #929560
Checksums-Sha1:
 2a0ce8c85243a797895458b37785538b6ed889c4 2403 libhmsbeagle_3.1.2+dfsg-6.dsc
 417ad2f262d72ea2440467ed1e5648c62f931d83 36144 
libhmsbeagle_3.1.2+dfsg-6.debian.tar.xz
 7622ef4776de958f87a27dee5cd34233c33c25fb 13239 
libhmsbeagle_3.1.2+dfsg-6_amd64.buildinfo
Checksums-Sha256:
 e2fc2a808b958ad872417758e2ab0c2c7c85c7888ceea723ca9a72c340bf7666 2403 
libhmsbeagle_3.1.2+dfsg-6.dsc
 90fca93d40fa5f8b06bab827ff1a5fd6879a809c01fb73beb7af17993e8364b2 36144 
libhmsbeagle_3.1.2+dfsg-6.debian.tar.xz
 906277c7a3258be18fd6439a26baa45b2267bc4b89dfdc7445ffdcfbfae33146 13239 
libhmsbeagle_3.1.2+dfsg-6_amd64.buildinfo
Files:
 69f86e71131f8a68449d7d5b79c41a86 2403 libs optional 
libhmsbeagle_3.1.2+dfsg-6.dsc
 1e1e11d1d75be898efdf1eecc6871f8a 36144 libs optional 
libhmsbeagle_3.1.2+dfsg-6.debian.tar.xz
 d4667b69ff0b766c3a6ddaec4888cbc1 13239 libs optional 
libhmsbeagle_3.1.2+dfsg-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlzq+CwOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtHAGQ//aMbhQ3pXsZXmgBnEcAc60HktiUWE9s7f/f2L
9IYQ8owGB7Tb2SiJBRh72wGlgGC49YVj85vjxG4psIUCi/GEOBDkpe3IeBv1nAYm
2P575cHf3YC/acBxK6Ltbw0pTOwDbpH3bh5+Slf6ji8/owULwxhmj564FoRjGa8k
9Abbzdpdhad5YLNNwAtbNrrjYq8XUMNIDWhiyz471Qf9km4iB8Wdu5nOmh3J660U
DbxCRoTteErVbM8hYesUoNq6EmDT3L6E07o43zLfWwp9m4Krpbblq3dRmukdEThf
J1u7jYv53ThgUnk6oLqstK3fuffGa6YVjo1iPg2zPnF6WtR3eutXwwLW4LnQAKvF
gsjRAlWfCWdDRWkoc6a/umIDgeqGUi1mHVC6r6MJzEqYxmlysV6Qzt9BeXnaL2pK
MsV129Uvq6wntQd+PUTq6Yuz/oek2VIK81JJhXq60rLviPInuH3t4TUX8b8u7uQN
d24vpK3Vd3yo8xOGh7iqTbcC6iPBJcV9E7Q2NyCqb7T5h/2zCIODZlTLP7XhiQpo
xis74XjHoqWybgMz6DCQrfqkkfbjpdBDQ4HQHseo1vYCLl/ZLB6g1CwRHYlVDYmT
fc70E00ARgZgAGoDP5+ZsrVo3tNX+46xnzNYWc5lbFqk5fBsCoOlEvMODVtVeBy4
uescAh4=
=lKdS
-END PGP SIGNATURE-

Re: Consensus Call: Do We Want to Require or Recommend DH; comments by 2019-06-16

[Adrian Bunk]

On Sun, May 26, 2019 at 11:34:39AM +0200, Vincent Bernat wrote:
>...
> We have a reputation of having difficult
> packaging practices. We uphold this reputation as long as we have so
> many ways to do the same thing.

  [citation needed]

I do honestly not know what statements/comparisons from people outside
Debian are the basis for this claim, and whether making dh more mandatory
is even related to them.

It is a problem for people making their first contributions to Debian to 
get them into unstable. The problem here is lack of sponsors willing to 
do proper reviews and then uploads. Usually the package in question is 
already using dh.

Often the most difficult part of packaging are the unique rules the 
Debian ftp team requires for debian/copyright that are not required in 
distributions with actual lawyers. That's a completely separate topic.

It is perfectly possible that there is something else I am not aware
of, and you are assuming everyone in this discussion is.

It would therefore be really useful if you could send some links to 
statements from people outside Debian *why* they consider Debian to
have difficult packaging practices.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Accepted node-liftoff 3.1.0-1 (source) into experimental

[Pirate Praveen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 May 2019 00:20:43 +0530
Source: node-liftoff
Architecture: source
Version: 3.1.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Changes:
 node-liftoff (3.1.0-1) experimental; urgency=medium
 .
   * Team upload
 .
   [ Paolo Greppi ]
   * New upstream release
   * Update Vcs fields for migration to https://salsa.debian.org/
 .
   [ Pirate Praveen ]
   * New upstream version 3.1.0
   * Drop dependency on dh-buildinfo (not required from compat 10)
   * Update patches
   * Add object.map and make-iterator modules using multiple tarballs
   * Set absolute NODE_PATH in d/rules
   * Disable failing tests temporarily
Checksums-Sha1:
 645db8e521da9290035665942820d932129e230c 2755 node-liftoff_3.1.0-1.dsc
 29b33f312aa8f547c4a5e490f56afcec99133ad6 3340 
node-liftoff_3.1.0.orig-make-iterator.tar.gz
 cf83e59dc8fcc0ad5f4250e1f78b3b81bd801d37 2672 
node-liftoff_3.1.0.orig-object-map.tar.gz
 51367d9abb0ddbdbdf3604ce1c5b876c2919eac3 571880 node-liftoff_3.1.0.orig.tar.gz
 7dcd25ce7bd9812151caab7e09bb3b35995f39c2 4648 
node-liftoff_3.1.0-1.debian.tar.xz
 5cc0912496058406dc0681331865ca61404ec449 10436 
node-liftoff_3.1.0-1_source.buildinfo
Checksums-Sha256:
 f5092bb1bb27dfc7ede1f0c6006768e008158c33dd07de4707c73594dfc4cb3c 2755 
node-liftoff_3.1.0-1.dsc
 2da16272887ed764ce3d8b763af5dd824c3fadb8b64d0518a97cd78beaad536b 3340 
node-liftoff_3.1.0.orig-make-iterator.tar.gz
 b27dfce6b63a591b86caea16705eb9e14949170ba0629645ed93ef8fa082080f 2672 
node-liftoff_3.1.0.orig-object-map.tar.gz
 5d2157ad4241127120d208907befca85ae075787775f8a7da2dd22c572502ab4 571880 
node-liftoff_3.1.0.orig.tar.gz
 35a54b697919bad247a513b7107cb4f8a43ae0dd5a4f6cac731299d394f5dc78 4648 
node-liftoff_3.1.0-1.debian.tar.xz
 f47d2703a46eea8962446717e521577e2f5ac659f167d16bc6fc3309db9942b3 10436 
node-liftoff_3.1.0-1_source.buildinfo
Files:
 5cc5b454d9d3b2cfa28f08211d8f99db 2755 javascript optional 
node-liftoff_3.1.0-1.dsc
 00db37fa649cf22ee768b93b63e81300 3340 javascript optional 
node-liftoff_3.1.0.orig-make-iterator.tar.gz
 924d9c0b75cca130ab61f00a2ecc6599 2672 javascript optional 
node-liftoff_3.1.0.orig-object-map.tar.gz
 038a0a64ac2ac39eeb0be91cb9b95e49 571880 javascript optional 
node-liftoff_3.1.0.orig.tar.gz
 92317a8afc5f3d4a5bc58c1829517cb2 4648 javascript optional 
node-liftoff_3.1.0-1.debian.tar.xz
 a903aee7419eec03dc242da85c2fae07 10436 javascript optional 
node-liftoff_3.1.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlzq47IACgkQzh+cZ0US
wioSOxAAqsM8PYrzept5U+STi2fV0It/tUPiLgm4j/5//XKEbajLHD/x0n0ZoOAJ
dkWyX7U0RWu2Vjtg+Vi8kzgAdMjjvD5N7XDOE/UnX8glWYkQ7+IPokrjHFG6Fvw/
lRrD/jgVAacU1SSnLOoE90LpWY/2vYk01ix7NQH2cRTjt6Dsd9rTJD0gvPsAXdVT
CBInZN+NCl5mlkUvscN2nJ8iJ6kXxEWgZW8zIkhpVP6sE0kVsvJ7+6XE54aFhYeV
x6EWeszbm8kiRDsxHW4V6BNdgI3KmfkZtPP1v60QgXZ9eO38ieCOaCHz4m0mPwlB
AxeLqvxLTCtM2sI1z5myYYpmjDd7x8GQMY6cmXPquJI4NagcCmHXkH7KOs5YRFWA
8Pjp8WZl3j+ZmuHGP0Q0UnNcRf5N21yDFOUcEz+ckTDUsdJ+QzolRB0AyjVBmom+
eQ3Bwzv77ljcCnMYuLu/J92Tkc/wpJQsaatFudssz+fgld8JiS8YzAX6vi1Dt0/+
TxC78UODp3ivmWuuoedA3W3P65u3oZLNX6WJbL4tAC+1Gx4ru/gk58khURAfKKPG
ISY3qc2IPf683WdhgEyysylSVYQxO6BcYaVlC981+vAWxF/VohqafmudDvfVh3me
0csxQUPcEEOfo6IEVhEX0UQWViC5i9F4EOPQ4k32lkYz54XY5b4=
=+ySw
-END PGP SIGNATURE-

Accepted libical3 3.0.5-1 (source amd64 all) into unstable

[Nicolas Mora]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 25 May 2019 10:17:19 -0400
Source: libical3
Binary: gir1.2-ical-3.0 libical-dev libical-doc libical3 libical3-dbgsym
Architecture: source amd64 all
Version: 3.0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Mora 
Changed-By: Nicolas Mora 
Description:
 gir1.2-ical-3.0 - iCalendar library implementation in C (GObject Introspection)
 libical-dev - iCalendar library implementation in C (development)
 libical-doc - iCalendar library implementation in C (documentation)
 libical3   - iCalendar library implementation in C (runtime)
Closes: 929126
Changes:
 libical3 (3.0.5-1) unstable; urgency=medium
 .
   * New upstream version. (Closes: #929126)
   * debian/control: Add Multi-Arch: foreign to package libical-doc
Checksums-Sha1:
 a1d0ac35031d831a985cfc525a1dce126cc1e475 2302 libical3_3.0.5-1.dsc
 711b86787ab3007c73c301824850c24b63823bd1 881800 libical3_3.0.5.orig.tar.gz
 9fdf214559829f0a20ddd8f9de965b0f1b5dbd52 20176 libical3_3.0.5-1.debian.tar.xz
 56b23811bf4008b88a016bc045cfe5d8d15ec032 49348 
gir1.2-ical-3.0_3.0.5-1_amd64.deb
 09cc97b0ea162f955a5c7f5ce086101a2329ad8c 416416 libical-dev_3.0.5-1_amd64.deb
 6e49e91c6c259fd2fcecde0c7955c7825958 114296 libical-doc_3.0.5-1_all.deb
 b19379870be0634e22522331bb23fa15f363faf8 1094084 
libical3-dbgsym_3.0.5-1_amd64.deb
 5225e490ad12addd3f4a14827cc51170ec024bd1 10044 libical3_3.0.5-1_amd64.buildinfo
 96022b9db9d41f4614017144ff987fa2f679a2a5 278048 libical3_3.0.5-1_amd64.deb
Checksums-Sha256:
 0c0641604e84e30621cfa13af0aa076bc47a4adb3287eed873a21d32f2d6a5ac 2302 
libical3_3.0.5-1.dsc
 7ad550c8c49c9b9983658e3ab3e68b1eee2439ec17b169a6b1e6ecb5274e78e6 881800 
libical3_3.0.5.orig.tar.gz
 b22e7a85f3664979fce479b74a7ea29ec92e5d98f869af84ec2ea30d066ab21c 20176 
libical3_3.0.5-1.debian.tar.xz
 d5a0bef5ea0e618edb5c74e864b0d1124e87c47c656c454811e98c1814a03d71 49348 
gir1.2-ical-3.0_3.0.5-1_amd64.deb
 41906294424d26e21c5a78305d04a7b273dd98b2da25a663efec7052ddb140df 416416 
libical-dev_3.0.5-1_amd64.deb
 432a757ef20b1bd7d552284091a82fe0a95a619975e7241624e12ed1cef4d00e 114296 
libical-doc_3.0.5-1_all.deb
 05623ed49fe84920d8b81515a33f98d7217cd549366e573b44d05d41a046189c 1094084 
libical3-dbgsym_3.0.5-1_amd64.deb
 54ad8b6872c25a0388f3f0036e5e202a191c637e4818f9066c288521100f679b 10044 
libical3_3.0.5-1_amd64.buildinfo
 acdab44202764c704f33c87334da8bb0c772b59d06711d2fe16437540d83ff5b 278048 
libical3_3.0.5-1_amd64.deb
Files:
 7733495fb53cef40286a339e63e9fcf7 2302 libs optional libical3_3.0.5-1.dsc
 9be4e8a1739a9c27e06aa8ce66b8cb34 881800 libs optional 
libical3_3.0.5.orig.tar.gz
 4e6df031dde3be2d4bb970bb51f0dcd4 20176 libs optional 
libical3_3.0.5-1.debian.tar.xz
 9912b5b7afdd9212ed490ade498e293d 49348 introspection optional 
gir1.2-ical-3.0_3.0.5-1_amd64.deb
 dc183669197a8d890558e02af83096a4 416416 libdevel optional 
libical-dev_3.0.5-1_amd64.deb
 2f4f1293176e00a75e74a6aaec6eb722 114296 doc optional 
libical-doc_3.0.5-1_all.deb
 a83ead16e1e2d105e29d3958be62bdfc 1094084 debug optional 
libical3-dbgsym_3.0.5-1_amd64.deb
 69f6e737a57bd7f3d3160a1641dadcdf 10044 libs optional 
libical3_3.0.5-1_amd64.buildinfo
 a1ceb42c0dda61a830669fa8a821d58d 278048 libs optional 
libical3_3.0.5-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEhAWwL8wo75dEyPJT/oITlEC9IrkFAlzq1rIACgkQ/oITlEC9
Irnx2w/+MCMGA279JvceW4p863+oYLVFnpt8ORA4TQPlxf0fYhU9kEG0cfhwLZjT
CpXnbpuOD7v0GsHosAza/yI0BaEoZF9g8ToseuPLfl9uV5Ju190I0PU8J+qZ1uag
jcCSrMPrc/FwY4LlCZMUo4uUvGfxcWXJVeFrsTtfdxsRVaDLoaHU7EyZMbJt/Ua2
MlFAsUZoJIxfOMxE1WAGNwpLJTI0LBtu44P6yqhllM216Pd9G/BA1m0ctDxAB+i4
dVP3t1xH53igT9TfZQ/qb2lg2EzeeTCnT+reWOu3rYnJE6s0LwYdsUAlgpKoJkmV
s4frDojQ5ZI5uQYeSt0Od1NJj0xYij7Mm0Cqx+Kt0/Nwkkr4EyQa/rmyrTz98bWS
gIlTfZoeQpA/WkR+a68BY6VpssDgK8bN2jiXwHrHGFacEJRCrOQUWCJav57+XmYX
93MWfeNCpishI9zfE8N0rdvdhlb8FGX15xl0dluRnsIOstEZOvpOLajVJcXjXGVU
uuXVUsMOOLXHJfKqa6uKcZr/8Gtauf2b4XYkTdkkDtElmZmpzqQbZwqeuXfPQ0wO
Kb2yHjJ+Lh9aLV2TsZXefcZZTPGpCH5FTWCEF86hXs9JyhnkjehUTw4+2atgKynz
e4cYUamYS0faVAUpGc3KAgjgJtrpqPaYWlNI3lNqtSJ8mNlp32s=
=j7pv
-END PGP SIGNATURE-

Re: Consensus Call: Do We Want to Require or Recommend DH; comments by 2019-06-16

[Vincent Bernat]

 ❦ 26 mai 2019 12:04 +02, Jonas Smedegaard :

>> > * People who make changes across the archive such as enabling 
>> >   hardening, cross-building, bootstrapping, etc benefit 
>> >   significantly from more uniformity in packaging practices.  The 
>> >   time they spend working on packages that use dh is significantly 
>> >   less.  That is, people working on making Debian more reproducible 
>> >   benefit from when we adopt more uniform practices.
>> 
>> It has also been said that non-unformity makes also the life of 
>> everybody more difficult when they look at a random package. This 
>> includes non-DD/DM people. We have a reputation of having difficult 
>> packaging practices. We uphold this reputation as long as we have so 
>> many ways to do the same thing.
>
> We "uphold this reputation" by maintaining many packages, which is
> good.

Do we? I am now using nix to get packages for stuff not in Debian. Our
package count is artificially inflated by *-perl packages, golang-*
packages which may not be present in some other distributions. But for
some ecosystems, we are severely behind. We may argue we are better on
some metrics, but this has nothing to do with the fact we have so many
ways to build a package.
-- 
English literature's performing flea.
-- Sean O'Casey on P. G. Wodehouse


signature.asc
Description: PGP signature

Accepted hexchat 2.14.2-4 (source) into unstable

[Mattia Rizzolo]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 25 May 2019 11:48:26 +0200
Source: hexchat
Architecture: source
Version: 2.14.2-4
Distribution: unstable
Urgency: medium
Maintainer: Mattia Rizzolo 
Changed-By: Mattia Rizzolo 
Closes: 921208
Changes:
 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
Checksums-Sha1:
 258ddcde1492888fbd8b09420046e6ae8b5df628 2672 hexchat_2.14.2-4.dsc
 1f0153be196e65369cdfed58a74578e27357a730 34488 hexchat_2.14.2-4.debian.tar.xz
 f91a25c9b9f917ca14b7dbd4bba08606246d02e8 15444 hexchat_2.14.2-4_amd64.buildinfo
Checksums-Sha256:
 21fddc80936eb5059fbdcd247700e716ce8bf2152effb677b75a15ad22cf9690 2672 
hexchat_2.14.2-4.dsc
 e7dd79e6f2d3cafd4ec96e77cadde1392d52ddf08b43a101c9e8525ffcdd63b1 34488 
hexchat_2.14.2-4.debian.tar.xz
 27de8f9e214262531edee482842585b8e089e246411bb3e7f88faf50d219597a 15444 
hexchat_2.14.2-4_amd64.buildinfo
Files:
 60b8fab682e018b808d60a7bd8aa7a43 2672 net optional hexchat_2.14.2-4.dsc
 3e4651e9300aa61099417a17536b7c48 34488 net optional 
hexchat_2.14.2-4.debian.tar.xz
 6d3a6b1d3b8601e74101d9d16aa5bf6e 15444 net optional 
hexchat_2.14.2-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlzqoG0ACgkQCBa54Yx2
K63XMA//ZqNMEKsJoM7elvg3OkfBmzRp3emshfCs/ZoLQcGk86OdCpQvppS63dw1
O7EC/7sGLTfIHOkvErfOUxf2SaUA+kh9CEWk2Dlz84sXzHpw+6By4DFeWpx848/8
IcRwqkGptSiQQtCtehZuvlsqiTJIsfKLKYL04HtlkXxrHFabGtq4gX5hhlULZfMB
XuCBfwdF1UkJv45wwsNDmJGQNPd8oKW+Qk1LH8Ug8ssQhSjQ1pXmzBkkrICjEi2J
M2vg9a5GCjcaRxcp+BaLCCeJLiIfNTy0wU5lkQVQp+zB/fX+jnEgE+Pchzydjlpj
sgHhwGLj0V4FGsiJFDcbLmmqFryUGQKV9AZHg0Ym9r9T2v4opmysjZqBuJE1V5D6
qFgmQY1/FqXTA/oCzxLD60VHNdgNAa9Fh+DzO2KJwdJdeB698qTDBb2qJpT3b+0s
qrcvUouo2O1ctD/nIKV14L/m3v6WI8Dx+6nnIAeto5f1NTzNncY9Q0LSWHvuAa4f
fUWHzItIIrjYqXZ6MS42q9SuM9d8jC8UgzlCdKypbI5wtQEwmvpRMXyyhmb9B8dV
2mmaoOtHsM+Lg3hXpDk6fyh7ygmzPp5AENQx7MYomr1Sups6u1KMA9Q0tQMFN+92
YTzbgAIhM6qL8ioLK9wk+BqfvzaCE/54G8yk5H9qjQx84XtSn+s=
=FmJK
-END PGP SIGNATURE-

Accepted lintian 2.15.0 (source all) into unstable

[Chris Lamb]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 26 May 2019 14:12:53 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.15.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 927970 929428 929430 929501
Changes:
 lintian (2.15.0) unstable; urgency=medium
 .
   [ Chris Lamb ]
   * t/bin/runtests: Correct equality operator preventing the correct
 parsing of --onlyrun="" used when (eg.) executing autopkgtests and
 apply a patch from Felix Lechner to specify a missing --work-dir
 argument when building test packages. (Closes: #929430)
   * Add references to Debian Policy §4.9.2 and §5.6.31 for checks
 regarding Rules-Requires-Root. (Closes: #929428)
   * Correct more false-positives for missing-systemd-timer-for-cron-script
 due to an incorrect regular expression. Thanks again to Francesco Poli
 (wintermute) for the patch. (Closes: #927970)
   * Remove unnecessary commas from tag long descriptions and
 improve grammar in the description of testsuite-autopkgtest-missing.
 .
   [ Vagrant Cascadian ]
   * Add Guile 2.0 & 2.2 to and remove "ancient" versions 1.6 & 1.8 from the
 list of versioned interpreters. (Closes: #929501)
 .
   [ Paul Wise ]
   * spelling: Add several corrections
Checksums-Sha1:
 d3427db5f0cbff7b0ec121eac569ad685642bbcc 3878 lintian_2.15.0.dsc
 3310b8c84dcbd5fd668e689c733c63800650cc1e 1713420 lintian_2.15.0.tar.xz
 bae8b544b340806bf32de374fde16cb70ccf21d4 1181408 lintian_2.15.0_all.deb
 ceecf48d27b4e7460e984d709d48b8e3b771e1e7 18114 lintian_2.15.0_amd64.buildinfo
Checksums-Sha256:
 803be7db6a3fe196fad780791d926093a1e0dde9bb492dea40f2f18c7ef32899 3878 
lintian_2.15.0.dsc
 e8b69c925f06cbdacfa8ffce2b7686299f0cd0cf95b0cfca85061f7d37199c0b 1713420 
lintian_2.15.0.tar.xz
 d98de401cdbc137c4a19b35e688149c767818829d70b5f5a89c48aceb2a81767 1181408 
lintian_2.15.0_all.deb
 fc09faf7980818779dbc529cd0df1c8c495613859e58f562606de7290fb47246 18114 
lintian_2.15.0_amd64.buildinfo
Files:
 9607acd0d4908ed5246af70de17ecd2e 3878 devel optional lintian_2.15.0.dsc
 81f4ff718dcca00cfa9fb4521c164407 1713420 devel optional lintian_2.15.0.tar.xz
 636ddd3f8a7de56202a902120f8b6507 1181408 devel optional lintian_2.15.0_all.deb
 6404176d2d5a902880b0571c9edda828 18114 devel optional 
lintian_2.15.0_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlzqo5MACgkQHpU+J9Qx
Hlg6ABAAm1NtR91919krPKrPNM5X5Fu12IISA5ma8d6H0QFRg2KmteNlI7QwUkh/
ko+in08/ZPUDlFE/kE+s/QgjmQp0pNLFUOOvIF+P53PLL705DQmv4kewR0PwTf9p
W6KHnTCtPGPodeSLItI9DHzbEoY04tVS074OOkC62TmPCMGs41UpbA3u+NnS8xW8
VLyDv0XaQNxMO3PxCb+6AO8LK7N0O83M7OKFhWzZpizI+lxCDgj87n/ba+77CKKY
9Xv4F5iCwZOMul7TUnl/loTDT284sgFqmc7EZkx7pEO1o+di/EOWagMmFIWDIco7
ouw/G/kN4hPIcfmzx1k5M7GJsCsNc8FVZA7zOOiLPHrdew36LmN/vJtHXJw4xRoy
rYhjo6y6tOW1Kvgnr+xlaqlHff1z+hTkv3U8tIlJJsETUUx0vGgLzfCiXa6vGepI
Zrveq80rJy+J6+FpcHkreLd541JrfgyZW0rt9HFGmOa8pXDt4Zpoq3bsmDyrjK2J
XBzK1lm8bdd7kWyqEUG5V0SE1oWTvEZUhpWgt7RuYnGQAYFYRpa7wOm/s9upARgx
1Vv3XYCkwIiApUwh7LCWrF2DoHQHIQAyQo/wjazB+rGdCqotGcteQFR3h8K7/wMI
0138wf1Yw3Ch+cEFmd6iYnpCaT5SLbLuWZ5kMfjiEJBmo4BaMHM=
=kcbv
-END PGP SIGNATURE-

Accepted p11-kit 0.23.16.1-1 (source) into experimental

[Andreas Metzler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 May 2019 14:20:35 +0200
Source: p11-kit
Architecture: source
Version: 0.23.16.1-1
Distribution: experimental
Urgency: low
Maintainer: Debian GnuTLS Maintainers 
Changed-By: Andreas Metzler 
Changes:
 p11-kit (0.23.16.1-1) experimental; urgency=low
 .
   * Refresh upstream signing key 462225C3B46F34879FC8496CD605848ED7E69871.
   * New upstream version.
 + Drop 45_01-extract-jks-Prefer-_p11_extract_jks_timestamp-to-SOU.patch.
 + Unfuzz patches.
   * debian/copyright: Update Format specifier, merge copyright lists.
Checksums-Sha1: 
 d6c980db298645434acde3aa70e9a87f9d241078 2440 p11-kit_0.23.16.1-1.dsc
 5522b60d90bd2dc8aac23cd0c0b0aded693f7c46 1292783 p11-kit_0.23.16.1.orig.tar.gz
 0ce76414c018fb9d03169bbbf5e40baa011f33dc 833 p11-kit_0.23.16.1.orig.tar.gz.asc
 3715f1339e0ca1eb88b0e134fc5ac4a1f583a5d1 21568 
p11-kit_0.23.16.1-1.debian.tar.xz
Checksums-Sha256: 
 af1e8fde1d147ce1c344467746837078c321e9b5063cc23b40596b804b594424 2440 
p11-kit_0.23.16.1-1.dsc
 4b34e92ae36fa493e0d94366c767f06d5f9951e3d8581d10fd935d738db1574d 1292783 
p11-kit_0.23.16.1.orig.tar.gz
 d6466013c87038d69d3d838d87fd8ad0e052d927ba56bf5658366351f7bb0099 833 
p11-kit_0.23.16.1.orig.tar.gz.asc
 b2ad1064299409b5e68e99fd80f57d5e997c773c5454e29147591f416167fe5a 21568 
p11-kit_0.23.16.1-1.debian.tar.xz
Files: 
 2ee0650f2c5aa7a721242f6ec39f9a0a 2440 libs optional p11-kit_0.23.16.1-1.dsc
 090a9cf689efd8d4899600c3093b3735 1292783 libs optional 
p11-kit_0.23.16.1.orig.tar.gz
 b5a51995a27944e510ae2d4e67aa3eef 833 libs optional 
p11-kit_0.23.16.1.orig.tar.gz.asc
 dd69b72877b4f8b97b2d16227f28f73f 21568 libs optional 
p11-kit_0.23.16.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAlzqie0ACgkQpU8BhUOC
FIR1vg//fQlOm7TrqayuFRLbId+7g9WnwXhBdzLYrnzYu8RvIuY1HCOXUC85K/MV
xkiO8peOGnTViTHDVMA97yN+pS73wJwNafqfQJio/Cs7oYTyLAUVnnVlNZKZNMCd
uh00nd7AeN4VZdhtw8v8+GwhHgDOzbLTeqNkdR0OFld0Y3xTCDn0u5n+8d46hTt6
f2v3m+BZ4MFEe3UVFESYqKJDNihm9Se8hzsbIYTksTUFuxvGOye7+2UYTJyDC9en
3mfYRSqfLdIHqO1tl13wZad9JQdJ2gLt8wQNthQF1nm5dfccAXPCFAkBqbznf/9d
vrZtmPhRUI7G8nubFGJ/nhL+tceU0unYNVvyE38q+LoIGXisjV6+q9I5qzS7YshE
RflrpuoeozdrCb18D3HuKf+fS8y3VX+OOWLKyAKA33j+Xd25jIuQKWPLpwR5Kw1h
fE2TefS29imh+HPr5aKPAlH5tEXWhbqnKSlUGwsoeMS7jcQ85YapjcEsH7Y7Vcpd
soWyQv2xEMq75/9s1+FkvhX/u/qQ8cSMx6A5ppWMn03MLRFp48e0KH6tphKutGVB
qxHEddtYkITIenwwrcuQGX9b+/rgJYs5JmnT3veMcoEncoT18rDi+IcBt+ONBK9P
XeucSdpIPpZW3boYdGNWsimIqHT8B2pYr2QBP1JUv47JUlkMXtY=
=ZHzV
-END PGP SIGNATURE-

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

[John Paul Adrian Glaubitz]

On 5/26/19 1:22 PM, Bastian Blank wrote:
> [SN: Trimmed Cc list]
> 
> Hi John

My name is Adrian. Thanks.

> On Sun, May 26, 2019 at 06:48:36AM +0200, John Paul Adrian Glaubitz wrote:
>> Could you PLEASE stop posting to debian-ports@? You are sending these mails 
>> to every Debian Ports architecture mailing list.
> 
> Please stop shouting.  Please fix your MUA to produce readable mails.
> Thank you.

Please stop sending mails to users which are not affected by your discussion.

I'm sorry but after kindly asking two times not to use this address for
this discussion as you are reaching way too many unrelated lists, I think
it's a fair thing to spell that "please" in capital letters.

> Also -ports goes to all port specific mailing lists.

No, debian-ports goes to every architecture list which is really annoying
when you're on all these lists.

I got this email through the following mailing lists:

debian-arm, debian-alpha, debian-hppa, debian-ia64, debian-68k, debian-powerpc,
debian-sparc, debian-superh, debian-riscv. None of these are related to BSD
or Hurd yet the discussion was on these lists.

It's not related to Debian Ports and therefore not too much to ask to reduce
the noise on unrelated mailing lists. And I would also like to continue using
Thunderbird without having to mess with the configuration now.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

[Bastian Blank]

[SN: Trimmed Cc list]

Hi John

On Sun, May 26, 2019 at 06:48:36AM +0200, John Paul Adrian Glaubitz wrote:
> Could you PLEASE stop posting to debian-ports@? You are sending these mails 
> to every Debian Ports architecture mailing list.

Please stop shouting.  Please fix your MUA to produce readable mails.
Thank you.

Also -ports goes to all port specific mailing lists.

Bastian

-- 
Without facts, the decision cannot be made logically.  You must rely on
your human intuition.
-- Spock, "Assignment: Earth", stardate unknown

Re: Consensus Call: Do We Want to Require or Recommend DH; comments by 2019-06-16

[Jonas Smedegaard]

Quoting Vincent Bernat (2019-05-26 11:34:39)
>  ❦ 25 mai 2019 13:26 -04, Sam Hartman :
> 
> > * People who make changes across the archive such as enabling 
> >   hardening, cross-building, bootstrapping, etc benefit 
> >   significantly from more uniformity in packaging practices.  The 
> >   time they spend working on packages that use dh is significantly 
> >   less.  That is, people working on making Debian more reproducible 
> >   benefit from when we adopt more uniform practices.
> 
> It has also been said that non-unformity makes also the life of 
> everybody more difficult when they look at a random package. This 
> includes non-DD/DM people. We have a reputation of having difficult 
> packaging practices. We uphold this reputation as long as we have so 
> many ways to do the same thing.

We "uphold this reputation" by maintaining many packages, which is good.


 - Jonas

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

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


signature.asc
Description: signature

Re: Consensus Call: Do We Want to Require or Recommend DH; comments by 2019-06-16

[Vincent Bernat]

 ❦ 25 mai 2019 13:26 -04, Sam Hartman :

> * People who make changes across the archive such as enabling hardening,
>   cross-building, bootstrapping, etc benefit significantly from more
>   uniformity in packaging practices.  The time they spend working on
>   packages that use dh is significantly less.  That is, people working
>   on making Debian more reproducible benefit from when we adopt more
>   uniform practices.

It has also been said that non-unformity makes also the life of
everybody more difficult when they look at a random package. This
includes non-DD/DM people. We have a reputation of having difficult
packaging practices. We uphold this reputation as long as we have so
many ways to do the same thing.
-- 
Say what you mean, simply and directly.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Accepted node-yazl 2.0.2-2 (source) into unstable

[Graham Inggs]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 May 2019 09:00:59 +
Source: node-yazl
Architecture: source
Version: 2.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Graham Inggs 
Closes: 894957
Changes:
 node-yazl (2.0.2-2) unstable; urgency=medium
 .
   * Team upload
   * Switch to autopkgtest-pkg-nodejs (Closes: #894957)
   * Update Vcs-* fields for move to salsa
   * Switch to Section: javascript, Priority: optional
   * Use secure copyright format URI
   * Bump Standards-Version to 4.3.0, no further changes
Checksums-Sha1:
 22d7381a6de3f7b6160d9be26180111ed9af076e 2030 node-yazl_2.0.2-2.dsc
 fa83d3921a11f5621c47c0c5a9185cd3292eda3a 2384 node-yazl_2.0.2-2.debian.tar.xz
Checksums-Sha256:
 3c22cb4f90df79e0aa2548a353b10138a55d3b3462d55de2b536cae0bcc79f98 2030 
node-yazl_2.0.2-2.dsc
 6cb48b2340456b9f092efdfd30ea79c9b10347bfbbb019fb9dbe96f00516f161 2384 
node-yazl_2.0.2-2.debian.tar.xz
Files:
 5e905253032875add066035f66bd52f1 2030 javascript optional node-yazl_2.0.2-2.dsc
 e8834a26d88dae892f3b70071dc5f898 2384 javascript optional 
node-yazl_2.0.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAlzqVwoACgkQr8/sjmac
4cKRexAAr3TWtuB9qycjRo8Ujs0L1dbDvlwD9A3Ofj4Qk61CoYngvyEGFIPwaSBp
48P9Fm8l8KWSgS5ACPaLeVPCzQv/RuJEFEoujqE2qPYhi/JH1P6LNQTFdXV7mc+S
5aeu8iV8dZy3IlSsdp5vADiNXwmlsk+k1L2+PeOel+rfNm+r/Q9A0ON+2XNyuGny
/NFXUogwr5OzSsy/8/uorRPU1LTjmGXbQcb3lGa+yKtJ+lSOZSgdIViwVdQe2Tic
RbhibR31mRE68n86btRe/b51sbnpIjwPDcwuIvRT6ub28mfpvTk81r+NZe/S+WuX
eMMThpj4ckjbc4+h6ATpxVEFveeka+EMUlVYIt1IiDB1hsAx2hWpy0HfCnbaVqmB
lCWifWWY0tK5eUyokRPtzpU7r4vvwnQ5sNUKnTDyYfDCzefob9YEj60PCTD6L1d8
9GSWFO12VCldHpWCtgo3hUkppeVTaIRBGA+hjXnSp8oTWVkdHbMwM+K3MZSJDydS
jZ9PJ+/VbwjmEsolWTQOTI9TQiygML9UizshPSxm4TCOI6/aIoLA/sAA/ymX+jPm
so0ECVgZJIgkXYgvQGwpNOdmt6WgYsdhSmGzxqjlXg/bbwljV55irP1NrVF63OwR
ClmNASThnz3QRPs1hQHWHtb9Cy0IZzvu7DJ+YgDHmPOl4hXpriU=
=mcsY
-END PGP SIGNATURE-

Accepted node-music-library-index 1.2.2-2 (source) into unstable

[Graham Inggs]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 May 2019 07:47:01 +
Source: node-music-library-index
Architecture: source
Version: 1.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Graham Inggs 
Closes: 894946
Changes:
 node-music-library-index (1.2.2-2) unstable; urgency=medium
 .
   * Team upload
   * Switch to autopkgtest-pkg-nodejs (Closes: #894946)
   * Update Vcs-* fields for move to salsa
   * Switch to Section: javascript, Priority: optional
   * Use secure copyright format URI
   * Bump Standards-Version to 4.3.0, no further changes
Checksums-Sha1:
 2285470ee7042d56389806fa470118feaee59196 2197 
node-music-library-index_1.2.2-2.dsc
 02dfb02898494045c82e98748a0387a4a6070a4d 2284 
node-music-library-index_1.2.2-2.debian.tar.xz
Checksums-Sha256:
 ec35cab8d792dc9d20f331c8309825142aa8c4ac52e60786c3284d3130266954 2197 
node-music-library-index_1.2.2-2.dsc
 4ca9e639f76fc301ea9fc6a7f25c0a3f47f252e633d5dd451a3221691c8991ac 2284 
node-music-library-index_1.2.2-2.debian.tar.xz
Files:
 cfa4194cc79d6b8559b1d7259bbf9acd 2197 javascript optional 
node-music-library-index_1.2.2-2.dsc
 398031da7d57a2d0b81597586605db26 2284 javascript optional 
node-music-library-index_1.2.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAlzqRkAACgkQr8/sjmac
4cIT+g//fcPz3yea74jx9+2FJid7iV6HUiZx/hv63FBvldAPyZxKHMSX91gTsTAd
Ss1EgUvCypBYvh6gEQ+c/uqmojWpDaQfloExrnQlIZCI+U7ZQlkkE4GGCtHENTNk
PjLDoa8AbPpw7PMuwp2biBxa4MpVbzq7Fb4Z7vMKYLS29RKVMFLu4rjYZfpldP7a
lJKIxSeg8xNNBrR1WItvbQBcZ+oJeuqiUc9/4bTYW+zXKkd4isiYJWIf/hnopRVH
h/TCJc26cweMS4MVTpWjUQMaeVqVukHR7HK6GlBSuqlMUcEjmiDfhL9HiO8Ggy/n
18GoJIzfks2191BQ0ucXg8RMdxAI7EZyHR9anlAX4AlBRK7pXWa+9+aXFPlh0OLH
TAMi/M+4CC3Ir4LcHnOZyMq7yjoiazFiDvT1mkABxzSwGHBAJK1oHmF9nTkrSabO
uGPiB8qXPANJJbzGd4tOX2NF9tCX4hy4CF2fOOLPjM2IEvVaoVlp/m67PeBLQ4Tg
wX3UFUBx9ok2OREtp4rZ6pL2QyNrKCrhE06++CtTDWzJX3k0RHS647WvnJwH6hXd
///wMnJfWflDUabPRFEw601J3EyyNSYzAeKN17pRUZ/EsHgWcAS917s9Wq7Qu443
qTe9xGGaWhoWMUSYT4bZkX1leW0ynlgX4xTRPHkD0d4mgikKrtI=
=6vaO
-END PGP SIGNATURE-

Accepted gap-toric 1.9.4+ds-2 (source) into experimental

[Jerome Benoit]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 May 2019 08:21:47 +
Source: gap-toric
Architecture: source
Version: 1.9.4+ds-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jerome Benoit 
Closes: 924186
Changes:
 gap-toric (1.9.4+ds-2) experimental; urgency=medium
 .
   * Debianization:
 - debian/gap-toric.links, correct (Closes: #924186);
 - debian/copyright:
   - Copyright field, year tuple, update;
 - debian/control:
   - Standards Version, bump to 4.3.0 (no change);
   - debhelper, bump to 12;
   - Depends fields:
 - gap, bump to 4r10p0;
 - gap-gapdoc, bump to 1.6.2;
 - gap-autodoc, bump to 2018.09.20;
 - debian/compat, discard.
Checksums-Sha1:
 3cd2b3724b74ae73e5474a334d5b1f0887482d06 2831 gap-toric_1.9.4+ds-2.dsc
 3fad45e7f68270ac9b86ebc896701e56a5444260 3568 
gap-toric_1.9.4+ds-2.debian.tar.xz
 3ead69172c451d259c1348152d7dd7c6371c1c8c 9045 
gap-toric_1.9.4+ds-2_source.buildinfo
Checksums-Sha256:
 b2aea7d1661e1c56dfeb8e3a0941b2376e92fe9ae7076b1be5040f9a6492db7c 2831 
gap-toric_1.9.4+ds-2.dsc
 3316ab8899d14c8c10a35ef573917029f8972d26762f7bb3b34d6f5000600ef0 3568 
gap-toric_1.9.4+ds-2.debian.tar.xz
 88f8d0aee60a8214171aa44cafe4a55a0eb90df1bc72781104db1fcf1b78ea55 9045 
gap-toric_1.9.4+ds-2_source.buildinfo
Files:
 27488d550ef76171b6616203d5d97c20 2831 math optional gap-toric_1.9.4+ds-2.dsc
 7e6c7fd1206805b699071f70e7cf17dd 3568 math optional 
gap-toric_1.9.4+ds-2.debian.tar.xz
 daf37e3a597f7ce6c3d6aceba9dfd8e8 9045 math optional 
gap-toric_1.9.4+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAlzqTrwVHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLiewf/0OV6Z5ia+wNRJrVKbWa2qrnNpv3
swyAwssZhl31YEFpcFzZATu9dpgb7OBhFIAe2CP3f92fSHbdyWlEclZ6cSJpLY6A
KFQkcXe0a3Hcz/8srf0XcDrCFRo0Ckp66S3SHf/WMAeNJ2CvpLQW2INO9jtqnfKo
T3na52sFZHrUEUkz5D0XgBH3yoUvGGgd4mFqjXj/et+5rXAyJWjhW2GpmejTDUMb
/OYL2tTePq4iO/eYv8mAW5C/OiSg4rGV6zqVTHhGkqHEFp8MMJgCpwxpp0QKS9Tu
3XRrMz9V7LuMotTztd718WoMepByg+2JqMBw2M0YsATA6NMKxcBVP1mB4PcorGaX
mQk30MjvLwEGfAa6dkhj01DWd3RZ3xwE5YgY0lyMDFQapsyPennxiYQX5MkY/luu
ojn5fvaMAps1RKDfbu0sUQn6rF9IjK58fZS1Q7mGfWHRFwedKrrTKYvfJgIEPYDU
zBzEFiOuRkQVjoxcClnAi01nVhHSPB64TdtWw3ovuZekO31lhJeVVR4L0H3lJhSf
Vid9f+aNPZd53mv/Z3HgjeaJtIYjUwGiKOjgIpeJ1zzg/D5o7mVJJAmgqZXRGHeZ
GlPWhh+o7YAAKnFd/paSwto0vC7qhYB2iD6RcOFRf9Wn6odcgFMCtIk2QlwoATzl
xT5tpOxfbVn90eMgIw2vZntnI7B0MCqR5ht/U4fA1J1sSVuaN5YGl2zy6PdobStI
1k+77kjTXqiV/uhW3oRRIpYa8YFAiJzfanPKAQHS0t6Y3/6PmlXmpe4sOGQ+dZjN
CQMFEr6SYIVYcAr/2yNvrGiIIac8DN2hdkexDwaXhqhWnYjS1WoLo3Zuw5cGUJ+t
gc1WNs0jMAVPM+HIOUdGdQPOJ63nKxkjERSIAqJjlModogaOG5vG+V3JmVOpo6Lg
UJ2+93cNWDfHvbSHyLRnmpYFehtXNhScpgk7CWBrkOn6KkCoxvrJIDvI+vaEtl2p
YehhjKW7UokHHg9Kmw6RlVHKIBkt3i4yclp3GyTSyWjl29H9vkk3VvlN4zCbw/O3
xWhNZxcv/k4NJq00IxPh/sAsxI8NXPO/DJ8h8J6+/tnWftU3QENcgjCYEYqOUXsA
E9YGFfxtpNW51M5dS4jrzcUN8PHGQ/FW0Yzx1xj0cqE8k7bQKluqkh9kqXbVcf6Z
y/zG+qeVisw0PKumiWsP82KovFezEbKPLMgBtZ7lTuTUExJTvh0kNRdKLxFOEQU6
DqYOmye8XkkWT4H/GBj0yTrhmYueo+sf6vSgplGz9K6ePAQUADl9NRIq10Rf4KaM
wfyGNyzPJpN6Crv3C9IfyZqpZz4w53jLArCbLcDUsY6S58p/b+rQ1t5n/X4=
=Adfj
-END PGP SIGNATURE-

Accepted wordpress 5.2.1+dfsg1-1 (source all) into unstable

[Craig Small]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 May 2019 16:42:33 +1000
Source: wordpress
Binary: wordpress wordpress-l10n wordpress-theme-twentynineteen 
wordpress-theme-twentyseventeen wordpress-theme-twentysixteen
Architecture: source all
Version: 5.2.1+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
 wordpress-theme-twentynineteen - weblog manager - twentynineteen theme files
 wordpress-theme-twentyseventeen - weblog manager - twentyseventeen theme files
 wordpress-theme-twentysixteen - weblog manager - twentysixteen theme files
Changes:
 wordpress (5.2.1+dfsg1-1) unstable; urgency=medium
 .
   *  New upstream release
Checksums-Sha1:
 1d922aab7af27db2228ccdba00270c59b181168e 2442 wordpress_5.2.1+dfsg1-1.dsc
 9696a0279aa467e654de8a8621d7221e0b8536eb 7915568 
wordpress_5.2.1+dfsg1.orig.tar.xz
 335979ece4cd833af09097a4b974b4ee2614cfda 6818976 
wordpress_5.2.1+dfsg1-1.debian.tar.xz
 109749e555cdd05a3768e751e9e6ba7f51e1b879 4382996 
wordpress-l10n_5.2.1+dfsg1-1_all.deb
 e361ce71af456b4d36478e72e120b3fe047b989c 314796 
wordpress-theme-twentynineteen_5.2.1+dfsg1-1_all.deb
 25fefb8258920be132371870202cba95a01fcff2 945864 
wordpress-theme-twentyseventeen_5.2.1+dfsg1-1_all.deb
 bae281006d6b28e2c48266dabcde34a1f4a8ac40 593688 
wordpress-theme-twentysixteen_5.2.1+dfsg1-1_all.deb
 7bba7b4a813a3c4426f53564331675fab9239503 6097620 
wordpress_5.2.1+dfsg1-1_all.deb
 9ab8bcf3d3a453324119a112f9fbb8ca2e2dd378 7250 
wordpress_5.2.1+dfsg1-1_amd64.buildinfo
Checksums-Sha256:
 f2432f0f620b4bb4ee4dc48bc5ad10c98bbd7db6feef6522833ed10951de8bb6 2442 
wordpress_5.2.1+dfsg1-1.dsc
 c6f8029d47c6f7b68de4a1d649efb7efc318cc165f267b989a37dd0e5221f388 7915568 
wordpress_5.2.1+dfsg1.orig.tar.xz
 ce956132d45e365e9c8aecda2d3958d89c6f25d943d95c46b19cea26d4803d2d 6818976 
wordpress_5.2.1+dfsg1-1.debian.tar.xz
 2b2e1c6a04375e22c56bf615609c805019979cfce26b591c6cad6f1be967101d 4382996 
wordpress-l10n_5.2.1+dfsg1-1_all.deb
 5c1dcda4881394b429efb44d9770253f5330e3a8e44d05afe2cf3a8cf3ffc733 314796 
wordpress-theme-twentynineteen_5.2.1+dfsg1-1_all.deb
 05865b96430b5215d99f5c24032ee0a0f6d56c5dbcf9001a3e26b93cb38c8552 945864 
wordpress-theme-twentyseventeen_5.2.1+dfsg1-1_all.deb
 e28b563c78c9bf06a71592bcbcc921d1068113dd1cda52c1ee9c463211422566 593688 
wordpress-theme-twentysixteen_5.2.1+dfsg1-1_all.deb
 2a122e0cdb347e42099583911d498d314db96b19ae919c938a5fc9516c6a3bb3 6097620 
wordpress_5.2.1+dfsg1-1_all.deb
 28601b18ec3159af36e7d66f8340ae2723970ca46ae708e2a91a2b611997 7250 
wordpress_5.2.1+dfsg1-1_amd64.buildinfo
Files:
 fa58aae9913419de292c7500b7e5f920 2442 web optional wordpress_5.2.1+dfsg1-1.dsc
 3131c21bf1acb44f93d6e8a4b185e898 7915568 web optional 
wordpress_5.2.1+dfsg1.orig.tar.xz
 0eeaf694cb63e093f72628b8dd08ef22 6818976 web optional 
wordpress_5.2.1+dfsg1-1.debian.tar.xz
 d078fcd9597a8e55844dda5c6304bec7 4382996 localization optional 
wordpress-l10n_5.2.1+dfsg1-1_all.deb
 874064a1f7166f81796789316b7a96a0 314796 web optional 
wordpress-theme-twentynineteen_5.2.1+dfsg1-1_all.deb
 ce33e848e26a8ac9b6c8c2f21540d642 945864 web optional 
wordpress-theme-twentyseventeen_5.2.1+dfsg1-1_all.deb
 eb8788623cc3c5754161ee23cacc57ca 593688 web optional 
wordpress-theme-twentysixteen_5.2.1+dfsg1-1_all.deb
 41a922d0963e7b080de865bcf02d679f 6097620 web optional 
wordpress_5.2.1+dfsg1-1_all.deb
 9bb83027faa96624b3f19e01067119a2 7250 web optional 
wordpress_5.2.1+dfsg1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAlzqNuwACgkQAiFmwP88
hOPA1g/8C3r1ka2RCOFCytoI8fmmoppuLOPEyo+m12ij/mioc9K4Oww63m+V2TmX
EzaOEq9seyHYTuOARGKhgA5qoDCw+xeNTgZ1KR10zY284gogY9D8apWSFBMmH6Ug
imq3ctGpZxqePNXsg96JSCnHcLATTu6oM8QVnp6RPYbyo9KDNjNYql5DYjqtrCHx
aEGPNGkC4qWi6CtGKjbPjaM+WPAw3O4zt/5wWk2d6KJkRi+rn7WjHkQhCgbtsCHo
bvyuYHf0HHksZWh1pnLiLbCaV0gwEaHYUkeYkea6bHEviB5/ZCusL2XkS5O6/Gth
XuoWH4WXNPlFwDwID5hgHnfRHTTZicsG4NupD2LvtCFqefaCRGAjVbzaBhkQHpv6
pzq2EpH4XGR0DGoHaGOOgshiQKlguL74jBgvI9fnkAuAmcM2MesJNApa3HQi5j9x
1czzFZ1RsuESar8rpIVVSrLGh0qbm3XlOuNRDQPSLNS9rODSlphKGgPlp8zXMc9o
Qqi8hyH9cXjL4YItU76w3ok2If1235KIYyPFGZlZy/7rlizEQ7omOS5qaJm0mUaU
O0qii2Yp/8wKl3r/xphkf0IPhooSBeXFtsF7hPJCU1MCEbOxFMjfKQ3lUpDIoXom
RvgJYxTmIUXRO0ekCYXNoYQrOT53Q6J6A8qpgicV1eptuje8mzg=
=efdt
-END PGP SIGNATURE-