Accepted neovim 0.3.4-3 (source) into unstable

[James McCoy]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Jun 2019 21:21:33 -0400
Source: neovim
Architecture: source
Version: 0.3.4-3
Distribution: unstable
Urgency: high
Maintainer: Debian Vim Maintainers 
Changed-By: James McCoy 
Closes: 930024
Changes:
 neovim (0.3.4-3) unstable; urgency=high
 .
   * Backport additional changes to address CVE-2019-12735 (Closes: #930024)
 + vim-patch:8.1.0177: defining function in sandbox is inconsistent
 + vim-patch:8.1.0189: function defined in sandbox not tested
 + vim-patch:8.1.0538: evaluating a modeline might invoke using a shell
   command
 + vim-patch:8.1.0539: cannot build without the sandbox
 + vim-patch:8.1.0540: may evaluate insecure value when appending to option
 + vim-patch:8.1.0544: setting 'filetype' in a modeline causes an error
 + vim-patch:8.1.0613: when executing an insecure function the secure flag
   is stuck
 + vim-patch:8.1.1046: the "secure" variable is used inconsistently
 + vim-patch:8.1.0205: invalid memory access with invalid modeline
 + vim-patch:8.1.0206: duplicate test function name
 + vim-patch:8.1.0506: modeline test fails when run by root
 + vim-patch:8.1.0546: modeline test with keymap fails
 + vim-patch:8.1.0547: modeline test with keymap still fails
 + vim-patch:8.1.1366: using expressions in a modeline is unsafe
 + vim-patch:8.1.1367: can set 'modelineexpr' in modeline
 + vim-patch:8.1.1368: modeline test fails with python but without
   pythonhome
 + vim-patch:8.1.1382: error when editing test file
 + vim-patch:8.1.1401: misspelled mkspellmem as makespellmem
   * Backport patch to prevent use of nvim's API within the sandbox
Checksums-Sha1:
 2b469eb20f9c15a791f55f880b795fae43cb1e2a 2639 neovim_0.3.4-3.dsc
 92e3dc08924e1554fe78e592433b1b598f3b0296 26884 neovim_0.3.4-3.debian.tar.xz
 be038d319b0e6cbead906a4c39ba9db1b21cf5af 8218 neovim_0.3.4-3_amd64.buildinfo
Checksums-Sha256:
 317fddb847548883de032b71c8923e79ba03568e14285cd78077cf22ead8230a 2639 
neovim_0.3.4-3.dsc
 aea5b17551716f438a0a061c027850f0ec09b0b36cc0c37b4055703e06b4f9b6 26884 
neovim_0.3.4-3.debian.tar.xz
 b000ccded8321f145249b904bd199a4b294cabf6bbbded621eb0179ba6083e6a 8218 
neovim_0.3.4-3_amd64.buildinfo
Files:
 b7df3c0ff912856357144c08e3f7b5ca 2639 editors optional neovim_0.3.4-3.dsc
 381c3d4d41720d420dec4e0d8b71996f 26884 editors optional 
neovim_0.3.4-3.debian.tar.xz
 b9e96215f900b27e988793b8467b8587 8218 editors optional 
neovim_0.3.4-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKSBAEBCgB9FiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAl0UIJtfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx
QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIACgkQ3+aRrjMb
o9sxTQ/2OGjnJNnlDyOQeYBQO+4KOxfBLyEI0Nc3JejAqBGt37AYu1fQcl7uetDm
G7DkC/vOfZzCV98h0R+VOAj/2KszTXu7oKNyJbNXmW0mqqH66VaiJMWtQgwTqfyE
rJS6rUY7Hnx9x4LF/fv85W0jM0/SrTTEC0knHLRxlwUe7VUf1zeKueOT0yg+Tpcx
oz2lWWK4foa4Nja/7/HvW3DSQiSzofZoCa5uKugcO5RPrpBrPBC90fSAKsACtlz1
DP1MpympljqqBBx26/91eM28vLQJZPpN82KZW5CTVgp56z8EPmyuQf8IOHFAKqOe
NM8bYz0C3uGceyMXzVMOnLIKUQ0nb44pj+SBkDkGGXCq1P5NBuI3cZ0Uexz3SMeW
GIDtVuyQFp7uHqZXViC8QQlrqeubZdK7+GkkDXPGEcG4ETdppyo047wv7Evk6TmZ
12ElUwmeX5We/78ZqbWZQjKW6EAx7fCS8eQh13In5SKtZJxRIkKly4tSpgdMpHdb
wlYoV/KeukSX5VbVjm6XMFzCVhQ0tpG5TN1cFT0TwS+dzqpED7GORBhfw0y4MQeH
4rXnU+m5ll2HzrCnlPs0u++QeMk+8gxiBfi+OTAYqbEkqo5l7gUJbX13rVziaakO
Ra+Dp1aREA7/U0D0Ju6kXu+cX9CCH5SHu4YHVmmZOI+M8y4H1w==
=H36Y
-END PGP SIGNATURE-

Re: getting rid of "testing"

[Paul Wise]

On Wed, 2019-06-26 at 14:54 -0400, Michael Stone wrote:

> Wouldn't it be nicer to have a reliable and simple source of version 
> ordering rather than relying on ugly names and symlinks? As a bonus, it 
> would be useful for a lot more things and for more than n-2 
> calculations.

That doesn't seem useful for my use-case since it would mean I have to
update my chdist sources.list after every release, while using the
suite names doesn't require work after every release.

I don't think this has to be a one-or-the-other scenario where the
different use-case factions try to kill off the features used by other
factions rather than living in harmony through co-existing features.

I think we can support all use-cases quite simply by:

Keeping the existing suite names and adding new *-backports ones.

Adding a way for folks to use version-based sources.list entries.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Re: Content Rating System in Debian

[Bagas Sanjaya]

On 26/06/19 23.09, Dmitry Eremin-Solenikov wrote:

ГI'd say that we should never be touching anything like this.

вт, 25 июн. 2019 г., 7:57 Bagas Sanjaya >:


In order to inform to users, especially parents, about potentially 
objectionable content in Debian packages, Content
Rating System (CRS) can be deployed to Debian. With CRS, users can choose 
to install packages that is rated for their
age. In some cases, CRS also filter or block certain contents in certain 
jurisdictions when legally required.

Exactly for this reason. By filtering you will limit the freedom of 
users. And if the legal guardian of the user disagrees with the 
rating, either he or the user will have to lye about  their age. 
Please, do not ever consider to add such rating system to Debian.


Someone's freedom is always limited by others one. So freedom is not 
absolute, but relative


In case at home, children's freedom are limited by parents because 
parents need to protect their children from mental damage long-term.

Re: Content Rating System in Debian

[Dmitry Eremin-Solenikov]

чт, 27 июн. 2019 г. в 03:32, Bagas Sanjaya :
>
>
> On 26/06/19 23.09, Dmitry Eremin-Solenikov wrote:
>
> ГI'd say that we should never be touching anything like this.
>
> вт, 25 июн. 2019 г., 7:57 Bagas Sanjaya :
>>
>> In order to inform to users, especially parents, about potentially 
>> objectionable content in Debian packages, Content
>> Rating System (CRS) can be deployed to Debian. With CRS, users can choose to 
>> install packages that is rated for their
>> age. In some cases, CRS also filter or block certain contents in certain 
>> jurisdictions when legally required.
>
> Exactly for this reason. By filtering you will limit the freedom of users. 
> And if the legal guardian of the user disagrees with the rating, either he or 
> the user will have to lye about  their age. Please, do not ever consider to 
> add such rating system to Debian.
>
> Someone's freedom is always limited by others one. So freedom is not 
> absolute, but relative
>
> In case at home, children's freedom are limited by parents because parents 
> need to protect their children from mental damage long-term.

As I parent I do try to protect my children's mental health. However I
do not need any extra layer that will
make filtering decisions based on abstract assumptions. Depending on
my level of child-confidence, I might
or might not allow my kid to use different kinds of software. But it
should be my decision, not some CRS system.
Because CRS system does not know a thing about my kids.

The typical motto of Open Souce Software always was 'to provide
possibility rather than policy'. We should not
step away from that rule.

-- 
With best wishes
Dmitry

Accepted gost-crypto 0.3.2-1 (source all) into unstable

[Dmitry Eremin-Solenikov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 27 Jun 2019 01:06:58 +0300
Source: gost-crypto
Binary: gost-crypto-dkms
Architecture: source all
Version: 0.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Eremin-Solenikov 
Changed-By: Dmitry Eremin-Solenikov 
Description:
 gost-crypto-dkms - Linux kernel modules implementing GOST cryptography
Changes:
 gost-crypto (0.3.2-1) unstable; urgency=medium
 .
   * New upstream version 0.3.2
   * d/control: Add VCS-* fields pointing to Salsa.
   * d/gitlab-ci.yml: add Salsa CI configuration
   * d/gbp.conf: import GBP configuration
   * d/control: bump Standards-Version to 4.3.0 (no changes needed)
   * d/copyright: drop internal.h file
Checksums-Sha1:
 5e717a7f9ac2155b8e39fd4078ad7c6b7ace9b5d 1564 gost-crypto_0.3.2-1.dsc
 5a99930041755596106f55c3dffa50b671f65023 417364 gost-crypto_0.3.2.orig.tar.gz
 a30d47798bbe590f5efeff4bb05761f82780ca58 3040 gost-crypto_0.3.2-1.debian.tar.xz
 b3125d8f4f3d024eff8f1a4ede96e190674090f6 222104 
gost-crypto-dkms_0.3.2-1_all.deb
 5f1031e9a228e2ee671b2696c5e3d26d8f8f8fe2 5443 
gost-crypto_0.3.2-1_amd64.buildinfo
Checksums-Sha256:
 caa81194596f80b5dfc32a1a95bd3b88025af65933d32a00e6ad80afcdb26083 1564 
gost-crypto_0.3.2-1.dsc
 a830166748640bed22e8981978762f4be82dd9a16196290aa0d105b988420d0e 417364 
gost-crypto_0.3.2.orig.tar.gz
 86147d13274d187682bfecfedfb05c5a7060b2659db7699d0c8294a5c825914b 3040 
gost-crypto_0.3.2-1.debian.tar.xz
 386072d887169d31776149a0de2fa7813d8256edc19e413e21bd13466fb4d506 222104 
gost-crypto-dkms_0.3.2-1_all.deb
 56369fc1e9079a9eb5999cbd67fb7c47739dc165e1f57483f644550ac84c588d 5443 
gost-crypto_0.3.2-1_amd64.buildinfo
Files:
 eb60526bfeb5deb4f43c4329713457e6 1564 kernel optional gost-crypto_0.3.2-1.dsc
 9d9cbd7b3bf2c24c3a578d110f98bde4 417364 kernel optional 
gost-crypto_0.3.2.orig.tar.gz
 c4c161564ee0260c79bfef7737bd438b 3040 kernel optional 
gost-crypto_0.3.2-1.debian.tar.xz
 c57425992d219cc475a1760bd85ff8a2 222104 kernel optional 
gost-crypto-dkms_0.3.2-1_all.deb
 2f01b83920120baf84071d1caaf5508d 5443 kernel optional 
gost-crypto_0.3.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEETHCElVyyY1bwuJV/izyKPgIpKNUFAl0T7LoACgkQizyKPgIp
KNUdmggAjoUjTDYZhoK/8jxdISycU3rQCFgaGwm29g+uC5bFhug4DIjer3lAWD50
TovtOKKApjj3gi/Hqj845TX1AoxD0aPhMxXUWm3AeTKacPWskMvGpaYPxIMzwYf+
k/W2bmMnHmGncJkkERxiav0ypiaeMLbssjZkpk9d1DUkNdJ8RXZZ23USIm35ekNo
dls3Ea+f0ZEp+e47vRtwnVliSOOgDcAkdpqXAH3q0viSz4aOR91G/xR6s0QlCPZj
GpRpSVibJ0pclHfVC5QeLDCVLuclV5275Oi1QPYlKwwwk3PtwkACrhdrbzEMJOcS
xIiu+rqsJmXG0CY5GGja5bg3e8hxgg==
=O34u
-END PGP SIGNATURE-

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

[Svante Signell]

On Wed, 2019-06-26 at 12:14 -0300, elementar wrote:
> Where do I find kFreeBSD-amd64 isos, from testing or unstable?
> 
> Em sex, 12 de abr de 2019 17:49, Joerg Jaspert 
> escreveu:
> > Hi
> > 
> > back in August 2018 we discussed architecture inclusion into
> > unstable/experimental.
> > 
> > Today we had our regular FTPMaster meeting and discussed hurd and
> > both kfreebsd architecture and decided to remove them from unstable
> > and experimental 2 weeks from now.

You can find an old image you can upgrade from at:
https://people.debian.org/~jrtc27/debian-unofficial-kfreebsd-amd64-NETINST-1.iso

and then use (selected parts of) for sources.list for upgrades:
deb http://ftp.ports.debian.org/debian-ports sid main
deb http://ftp.ports.debian.org/debian-ports unreleased main
deb-src http://ftp.ports.debian.org/debian-ports unreleased main
deb http://ftp.ports.debian.org/debian-ports experimental main
deb-src http://ftp.se.debian.org/debian/ sid main contrib non-free

Re: getting rid of "testing"

[Sam Hartman]

> "Michael" == Michael Stone  writes:

Michael> On Wed, Jun 26, 2019 at 09:01:03AM +0800, Paul Wise wrote:
>> I also should mention that I use all of stable stable-updates
>> proposed-updates and the equivalents for old/oldold. I have them
>> in the apt sources of a chdist so I can easily look up old
>> versions, do apt-file searches on old versions, look up non-amd64
>> architecture info etc.

Michael> Wouldn't it be nicer to have a reliable and simple source
Michael> of version ordering rather than relying on ugly names and
Michael> symlinks? As a bonus, it would be useful for a lot more
Michael> things and for more than n-2 calculations.

No, not really.
People have enumerated a couple of cases where stable et al are the
right cases.
You want a sources.list entry that changes what it points to over time.

The examples seem to fall into the category of things that intentionally
rebuild their environment or things that are providing data based on
what is currently Debian's stable/whatever distribution.

These are valid use cases and they really do seem to be served better by
stable and friends than by things that require the sources.list to
change.

Testing and unstable have clear demonstrated utility in a sources.list
entry as well.


--Sam

Re: getting rid of "testing"

[Andrew M.A. Cater]

On 26/06/2019 19:58, Michael Stone wrote:
> On Wed, Jun 26, 2019 at 02:23:40PM -0500, Andrej Shadura wrote:
>> On Wed, 26 Jun 2019 at 14:13, Michael Stone  wrote:
>>>
>>> On Wed, Jun 26, 2019 at 03:10:27PM +0200, Philip Hands wrote:
>>> >I'm perfectly capable of typing slink when I meant stretch.  The coming
>>> >era of b* releases is going to be a right pain for me.
>>>
>>> FWIW, I still confuse bo and buzz. :)
>>
>> How about buzz and buzzter? :)
> 
> They're all terrible. I routinely say squeeze when I mean stretch, and
> then when I log in somewhere and see stretch I wonder why it's running
> such an old release. :(
> 

Think again about why we have release names at all: Debian 1.0 never
happened because somebody packaged a pre-release semi-broken version as
Debian 1.0 on their CDs. At that point, Debian chose to also use
codenames to refer to releases in progress.

For me, I like the idea of being able to use the codename as soon as it
is usable - that means that the distro tracks from unstable -> testing
-> stable without a change.

Pinning to stable is a silly idea in /etc/apt/sources.list - as soon as
a release state changes - so if I have "stable" as my referent with 9.9,
there'll be chaos as Buster is released and a forced upgrade

Having stable, testing, unstable as labels does mean I have to explain
more to colleagues but it also means that I can confidently tell my
colleagues:

"Use the latest released stable Debian version if you want longer term
support"

That, and the fact that security updates refuse to apply with an error
message if you're too far behind / the clock is wrong are both fantastic
features IMHO.

All the very best, as ever,

Andy C.

Accepted rust-packed-simd 0.3.3-1 (source) into unstable

[kpcyrd]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jun 2019 22:11:53 +0200
Source: rust-packed-simd
Architecture: source
Version: 0.3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: kpcyrd 
Changes:
 rust-packed-simd (0.3.3-1) unstable; urgency=medium
 .
   * Package packed_simd 0.3.3 from crates.io using debcargo 2.2.10
Checksums-Sha1:
 dc4132f511dd9dbccba3f129bb8835ffe4a2e0f9 2509 rust-packed-simd_0.3.3-1.dsc
 a8ec47e7dc049d3683bdf090a0c4ba214522aee4 86929 
rust-packed-simd_0.3.3.orig.tar.gz
 59843b1b52d9ffb10a2e98316a136b250bfdbba3 3088 
rust-packed-simd_0.3.3-1.debian.tar.xz
 042493463d44d9c54a66b8402948c7d21d893c21 7205 
rust-packed-simd_0.3.3-1_amd64.buildinfo
Checksums-Sha256:
 95941ba3d5746fd38fd1302e34a0bb4d7f54ee2f0574ba3678e9c2bac253d851 2509 
rust-packed-simd_0.3.3-1.dsc
 55d3b0dd18060beac664fc0de36e661d8336f304ad9b5a89b2d5b716146527db 86929 
rust-packed-simd_0.3.3.orig.tar.gz
 8bda2d85946d4682832a8c17d4168662d71edd1b021d7b78a185f4301724c4b9 3088 
rust-packed-simd_0.3.3-1.debian.tar.xz
 45c7f19fb13eeb060c774e36556eb8600971f77b2a9b069600710dcaa53e5eca 7205 
rust-packed-simd_0.3.3-1_amd64.buildinfo
Files:
 3936e002a55e09805999fa11e3a8ea8d 2509 rust optional 
rust-packed-simd_0.3.3-1.dsc
 572afe0eab9c1d4185e4252f80f0a65c 86929 rust optional 
rust-packed-simd_0.3.3.orig.tar.gz
 c685eea8bdeb550d4c8758e1269fb427 3088 rust optional 
rust-packed-simd_0.3.3-1.debian.tar.xz
 b33235de6ec5a558c70f5714c54780c1 7205 rust optional 
rust-packed-simd_0.3.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl0T01QACgkQfmUo2nUv
G+EoFw/+JthVUWeZs4AbkS/wZjhON0m0FvBCT0N5CQciG0i7nVPVeRdhLJmPVS8w
2MAZOXwWycUYSRGxPDp+SipTAvZzgmQSfJckEdl3GBoYJNOIa9RK0iRGYS85LyH8
n3QTG2r810r8oRsjFs/zZIQALELCLeaIwjBvKatlHwPWFPG/rXgL3cMfUYLjxioL
kBfT7PNCYTIqEWt5/8eP7Q7rxnaUokDpC/RFBz8UJT6UOcaTUmO1I8zDdQrYQQ+U
U/Gx+SemYOrZQvH+cnzn/v8OIxU6sSeJGD3kpLgSed6oVat+IqSCtTxyr8XhkjnX
3uS38ZB6FfYKtakvn8ia986BUYDzCvNrf4KxYXW18hjznnwfy3E6jUCqrEEoUdxr
Z3rR0s51wsnbuKHaZsl46IAZfMPkZzGQ7E8TapvI9VavHTuV5/q1hrJj9IKMwXt4
om5yCn3BHxz8DmVE/TL5JDCUnj1EXMM0vv8209RT45up34byE8f5PqdtIgldFyq3
jslHoRMVQ+ZXBINCgMJ/Y/VRFLMruynJaW+u2UrqcXkVGp2lXt9vXoM8ki+EBO6U
oHIciFUYqfLzX9ah/LI6LCXMOQhlQYnIZsZ+5mMHZp6rEUdfwhjqeFQ5nHf1ubQU
oj8e8LsEwI1DjKUuckwFcYp/eEa/iBaRcOZQvAGn+HK73eMVXx8=
=Sx3Q
-END PGP SIGNATURE-

Re: getting rid of "testing"

[Michael Stone]

On Wed, Jun 26, 2019 at 02:23:40PM -0500, Andrej Shadura wrote:

On Wed, 26 Jun 2019 at 14:13, Michael Stone  wrote:


On Wed, Jun 26, 2019 at 03:10:27PM +0200, Philip Hands wrote:
>I'm perfectly capable of typing slink when I meant stretch.  The coming
>era of b* releases is going to be a right pain for me.

FWIW, I still confuse bo and buzz. :)


How about buzz and buzzter? :)


They're all terrible. I routinely say squeeze when I mean stretch, and 
then when I log in somewhere and see stretch I wonder why it's running 
such an old release. :(

Re: getting rid of "testing"

[Alf Gaida]

Only a last thought: Didn't we have really important problems to solve? 
It might be only me, but i see the discussion as a minor variation of 
bike shedding.


To sum it up: Some people like codenames, some not, same for numbers - 
the real question is: Does it really matters?


Over and out
Alf

Re: getting rid of "testing"

[Michael Stone]

On Wed, Jun 26, 2019 at 03:10:27PM +0200, Philip Hands wrote:

I'm perfectly capable of typing slink when I meant stretch.  The coming
era of b* releases is going to be a right pain for me.


FWIW, I still confuse bo and buzz. :)

Re: getting rid of "testing"

[Michael Stone]

On Wed, Jun 26, 2019 at 01:29:44PM -0300, Antonio Terceiro wrote:

As a data point, having "stable" and "testing" stay around is very
useful for CI purposes. For example on ci.debian.net all our setup uses
"stable" and "testing" instead of the release codenames, and it's useful
to have a system that does not need manual intervention when the meaning
of "stable" and "testing" changes.


Ideally, a mapping of what is currently "stable" or "testing" or at 
other levels of support would be easy to determine programatically, so 
you could avoid manual intervention for those cases and make it easy to 
support other cases without having to either manually configure things 
*or* make a bunch of new ugly symlinks.

Re: getting rid of "testing"

[Michael Stone]

On Wed, Jun 26, 2019 at 04:13:00PM +0100, Ian Jackson wrote:

Andreas Tille writes ("Re: getting rid of "testing""):

 I never really understood why we need these codenames.

Simon McVittie wrote:
| Back when the release team decided on a per-release basis whether
| this was a "major" or "minor" release, we had the excuse that we had
| to use a codename for testing because we didn't know whether etch
| would be released as Debian 3.2 or Debian 4.0

I was around at the time and I have a vague recollection which roughly
matches Simon's.  


Not just that: after the faux-release debacle there was a push to avoid 
numbers in case someone polluted one. We're much less dependent on CD 
vendors these days, of course.

Re: getting rid of "testing"

[Michael Stone]

On Wed, Jun 26, 2019 at 09:01:03AM +0800, Paul Wise wrote:

I also should mention that I use all of stable stable-updates
proposed-updates and the equivalents for old/oldold. I have them in
the apt sources of a chdist so I can easily look up old versions, do
apt-file searches on old versions, look up non-amd64 architecture info
etc.


Wouldn't it be nicer to have a reliable and simple source of version 
ordering rather than relying on ugly names and symlinks? As a bonus, it 
would be useful for a lot more things and for more than n-2 
calculations.

Accepted xpilot-extra 4.7.4 (source) into unstable

[Boyuan Yang]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Jun 2019 13:30:08 -0400
Source: xpilot-extra
Architecture: source
Version: 4.7.4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Changes:
 xpilot-extra (4.7.4) unstable; urgency=medium
 .
   * QA upload.
   * debian/control:
 + Bump debhelper compat to v12.
 + Bump Standards-Version to 4.3.0.
 + Add Vcs-* fields to use git packaging repo under Salsa Debian
   Group.
   * debian/compat: Removed, useless now.
   * debian/dirs: Removed, useless now.
   * debian/rules: Rewrite using dh sequencer.
   * debian/source/format: Explicitly use "3.0 (native)" format.
Checksums-Sha1:
 df5df171a5570be2ebab4152d3810e7f1498 1550 xpilot-extra_4.7.4.dsc
 e01b4558e54d0586fe40ecf3778bbaf543a1d6fc 352356 xpilot-extra_4.7.4.tar.xz
 ed07e340f269ffdcaeb6754a97ee37e3203032d8 5313 
xpilot-extra_4.7.4_amd64.buildinfo
Checksums-Sha256:
 7d94cb0d98c0136a0b6a6b0c70357084ec5ba30d002ff2e0f52fa442348e38ae 1550 
xpilot-extra_4.7.4.dsc
 fcb2f648a29c025a2ab513116a5a94eaac6773bca6e0c3b4b922ef61b846b93a 352356 
xpilot-extra_4.7.4.tar.xz
 2ce1e37e4a6217a6a7e97732b86cfb2236b09d0e63e197a9d395d38f2412bdff 5313 
xpilot-extra_4.7.4_amd64.buildinfo
Files:
 705904faf8684d29189bafcd4b29292b 1550 games optional xpilot-extra_4.7.4.dsc
 1c254d149dc5c0112a6ec06c742ac12a 352356 games optional 
xpilot-extra_4.7.4.tar.xz
 361358afaba952c3146fd6c89a456336 5313 games optional 
xpilot-extra_4.7.4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl0TsYkACgkQwpPntGGC
Ws48HA//XkJ2KA4cljD8+ZT3qo/zzc2VyNdPM1akvMc7jUmvddb2VkqwIWn7ONYI
+VdJWoLGIll0nHmBvNCVy0TJp9guYWaD+gzDR/lyJrcT78sMysFr1CTsOWp7EHNd
tIrhDA1vR7CHcMstIIGJaY77b3+lefxcv0jTgqGCH/IRhgnXHCoPg6KmjMe5IT59
nHe8X0BKemyp0prK2pFLI18kD837DhCReTDlS4/fX/15qax0OKW9Z2yvGGOKMwG9
BaFxeCWvaHtD+allH8F5HXgNtnM7YesdSmwKZzWs+Vl6UxSASOIddQNB+N4hHeBT
Stn6WTtzT42YuNWDcy+NQgba2V65WlKoY/Fj02pVT53/4/MpWO6zoswQhSYGNI2k
w/JrrZNpQwajuqb1ynKKTB97jWj5wV3Q8o7Wi9fgLEJKNYj3i6omdr+gzzg8sJZh
ffEK1L8wNRrgCRJyUVLRa+LQcq2JUE51Di2SSRZ4IMRzPgUcFkBhSN6NTDJiuxk8
Fd6tM7My/wkXba5GOdXhjzFbXCWIwxgxor/WCVg6a9zQ4TPLw3XchLmZqzq2a1UH
9dbPxZ03Ysg9gwsJyh2xp4S1jY2eHkfLKlHHUMCe6XnMjaFOa4m7V4tKsZZJIByJ
SXKilxD1m/Hs7rD+Flw+wLPWH/732fOFbY0T08RAtUdfYDccG1M=
=k5GT
-END PGP SIGNATURE-

Accepted matrix-synapse 1.0.0-2 (source) into unstable

[Andrej Shadura]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jun 2019 13:09:57 -0500
Source: matrix-synapse
Architecture: source
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Matrix Packaging Team 

Changed-By: Andrej Shadura 
Changes:
 matrix-synapse (1.0.0-2) unstable; urgency=medium
 .
   * Upload to unstable.
 .
 matrix-synapse (1.0.0-1) experimental; urgency=medium
 .
   * New upstream release.
   * Bump dependencies.
   * Use dh 11 and compat level 11.
   * Refresh patches.
 .
 matrix-synapse (0.99.5.2-1) experimental; urgency=medium
 .
   * New upstream release.
 .
 matrix-synapse (0.99.5.1-1) experimental; urgency=medium
 .
   * New upstream release.
 .
 matrix-synapse (0.99.3.2-1) experimental; urgency=medium
 .
   * Upload to experimental.
   * New upstream release.
Checksums-Sha1:
 b21c1f8dcd1ec47c3d44c0abc1a3b7ea673ced76 2520 matrix-synapse_1.0.0-2.dsc
 71a1cc5e8ebd836eb2a7f964806dbcfaf28e7bfb 89652 
matrix-synapse_1.0.0-2.debian.tar.xz
Checksums-Sha256:
 a7192f55778c6a6bc1f71f0c9397299da58e777d6812ef936f92ad34d9de8082 2520 
matrix-synapse_1.0.0-2.dsc
 0193a9ee982819c82b52f2dfba5d5731fef8f731dc7a89fdf309004493b1f1bc 89652 
matrix-synapse_1.0.0-2.debian.tar.xz
Files:
 1544f360e9c5b1d164fad9cb45e34733 2520 net optional matrix-synapse_1.0.0-2.dsc
 934546eb664db5816351e6b8b60a8f51 89652 net optional 
matrix-synapse_1.0.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl0TthkACgkQXkCM2RzY
OdLwJQf+M7TituaopH/8QJFGZW3KLL/ygG1ayHo+ulgsmV6hZjTOd/T1+E2Q1PZo
Nq9MnEbYaskF4K2ELlcIBRlu1AvsFemzuA00WmXwoB1wG98PGGdOFgRn7aIFCdmn
scEJXE60JhonOEwd6mXTO6LcTvgLDnHqsuFwJAu04kyB5/WMA9wuyg3ti0PVzF9H
NZiAKCU/MmLccZkffcHsUF++HzltS2whbwdUMOxv/drF7r9M6odVzlAkKplCyWLl
oS1eEKs683l5bsrT3WWMR0DicWGZlCpBi5hovopKQuCvaSwcT/wj4JdEvaDtZpwb
vxEPE7g8n2yhtfP9JfyD/yxxgjbHVw==
=l3uS
-END PGP SIGNATURE-

Accepted debian-cd 3.1.25 (source) into unstable

[Steve McIntyre]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jun 2019 18:26:02 +0100
Source: debian-cd
Architecture: source
Version: 3.1.25
Distribution: unstable
Urgency: medium
Maintainer: Debian CD Group 
Changed-By: Steve McIntyre <93...@debian.org>
Changes:
 debian-cd (3.1.25) unstable; urgency=medium
 .
   [ Steve McIntyre ]
   * Fix for stupid bug in 3.1.24 - rebuild without my locally-hacked
 CONF.sh in the package build. :-(
Checksums-Sha1:
 62b63373d1c5b557be79fd9c1bf95e718324c996 1766 debian-cd_3.1.25.dsc
 4fd580a13cbe3626463989df31d4d55d3ab8a217 1161996 debian-cd_3.1.25.tar.xz
 9ed028afd9af641bb7e6f120e4dcfcfb3c18f49d 5144 debian-cd_3.1.25_source.buildinfo
Checksums-Sha256:
 71b5a9a708702705e6f6ec9383ade36b3bc0776e3f087df3f4111a9619512a06 1766 
debian-cd_3.1.25.dsc
 6d9306490a46e88135c51b9bff063367e3edf9d5e11ab4eb01b77f926aedb4dc 1161996 
debian-cd_3.1.25.tar.xz
 2f244946d25ab20eef6f709c2c786bef19cfc57e9c81b26c0c39746844299b95 5144 
debian-cd_3.1.25_source.buildinfo
Files:
 506a9223ef32d7f7395a384d16ad5c21 1766 admin optional debian-cd_3.1.25.dsc
 8a8ec7f589ffee5d6de67ee89c0c9416 1161996 admin optional debian-cd_3.1.25.tar.xz
 4a164fb94e81790559ef242abfb8c2bc 5144 admin optional 
debian-cd_3.1.25_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAl0Trt8RHDkzc2FtQGRl
Ymlhbi5vcmcACgkQWHl5VzRCaE5kKRAAnTtszUNe9pDjshNd9c7//npiTDjmTCwv
JMsRurGOimSPxoHYI+maVrZvJ7Su6fuEoRHwqXCSWwmb/BWYvWDAOY4NePI37B1H
BkUlTWNzM5e1RjIIRtJreT2GtDPQBkMR0+SyeoYQkA68+MUdMwdvMejwsDRauBE/
CnLbFs6Y+crW/iikx0V1/B2XDouyEb0PcVFCMfzmkhN9bYjy10uKTZPTsZYtFdAs
wZekIPNWq+AwpB27LNtO+HyokfjGJsfEpwKfsGwnOEKt1FaVJvgXEazg80iIMYEw
UtcCm6i633NuwSJuuFBDDIMhV1q8twWqyJb2WWqc+l2yC80sg/wGYX51cwo8AChA
6XOCBUtd9siFqmAG4/qL7LU6WaeWrhyq7GDXC80EgmfnxDCsx5C+lEhSqGKUB/dy
cspx6tQtdjvrJ1vkcoVwoDnC2aYia12k5awXfb7rd1V50XDmuRR0adVKg4HyDXrh
vMm2r0txQmQEBDGyWC5Xq0yoShRE4omVld4PaFPtuufRDzqhOwzL6Rd5dcl804Fr
lsaWu2a4DhlobNzfHs6DiMxIQ+/d30Z9eMiX1PwLsOSNAA85xFTzG9b35L5zrAt9
Sg4zUS0BcN31aVgy/MnlbAeTfdipHUvYtBVCwlsYfAz47qOoD7Pr7eMHF9KbUq6q
Q7IvkaOgsSE=
=D4Ej
-END PGP SIGNATURE-

Accepted python-service-identity 18.1.0-3 (source) into unstable

[Andrej Shadura]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jun 2019 12:59:52 -0500
Source: python-service-identity
Architecture: source
Version: 18.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Changes:
 python-service-identity (18.1.0-3) unstable; urgency=medium
 .
   * Skip tests when not present in the upstream tarball.
Checksums-Sha1:
 5fb0fda7b940cc9cd13a9d72bc0b36a9153c3a83 2718 
python-service-identity_18.1.0-3.dsc
 9270ed012a44c0d6fe707d5aab822a2d64feef03 4872 
python-service-identity_18.1.0-3.debian.tar.xz
Checksums-Sha256:
 91655df53bd0f181342f45fe84d4f43d3be0b9ee5be5fb7e8e8d34e235917292 2718 
python-service-identity_18.1.0-3.dsc
 c1a9b54aafca3a0d7d36a7fd726363e96d162e6b452f211a78a1c86b7b8d20c6 4872 
python-service-identity_18.1.0-3.debian.tar.xz
Files:
 377298e5179072c3283377cad58dd463 2718 python optional 
python-service-identity_18.1.0-3.dsc
 28a4eb30a6e5b80d527d0c24e5a248b3 4872 python optional 
python-service-identity_18.1.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl0TsugACgkQXkCM2RzY
OdIpkAf9G8FqfOm23Wq13GPjT5qFnbsuWK7Yj6jetQxx1ePHvgMi5C78oGltRT2T
cwiomAeTRkFZPr0kCzmi/DntR8c/xC66wyK/a88nadHqD27lUj1kq4kJoA4SJbA8
4gkwvUgUa+eJlYSeItJccYeh/5YtB61asQgzmUd/MuDkaMtyITv0Yo6Zh/JAAndb
w6VIhR5Ct1h0agc9IWciQyS52j+mbMud/AjgN9iprT3H+oOaucHvquvYm8Q4+MSU
GVf2ch6R0qCCIcRE0/bjhTjwmRZKYmGEL4KsSdCFrYYNXUwh75kQhH4Wla8gVuXy
coK+a7gnxkOInog7xYmdssB3EEcIMA==
=NnJN
-END PGP SIGNATURE-

Accepted libcircle-be-perl 0.173320-2 (source) into unstable

[Andrej Shadura]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jun 2019 12:50:01 -0500
Source: libcircle-be-perl
Architecture: source
Version: 0.173320-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Andrej Shadura 
Changes:
 libcircle-be-perl (0.173320-2) unstable; urgency=medium
 .
   * Use debhelper-compat 12.
   * Ship a systemd user service (disabled by default).
Checksums-Sha1:
 41edd83cc0aee7847afebd47d2fd1c286fb7575c 2290 libcircle-be-perl_0.173320-2.dsc
 9e681ca258f47f84fc56012836a26fe7f6c3d550 1936 
libcircle-be-perl_0.173320-2.debian.tar.xz
Checksums-Sha256:
 0ef3d57511c7ce01184531fd5843ad8b7344328e65df1b9a27bafb3775ff2c18 2290 
libcircle-be-perl_0.173320-2.dsc
 5f22d89356f3f667728cf61be1e7d47c7bccf782cc1cdd90e2149edb11414d5f 1936 
libcircle-be-perl_0.173320-2.debian.tar.xz
Files:
 2cbafdbff8cd14ec8799b7de9e2b219d 2290 perl optional 
libcircle-be-perl_0.173320-2.dsc
 b4b7255653869766c256fd9adf30704c 1936 perl optional 
libcircle-be-perl_0.173320-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl0TsLAACgkQXkCM2RzY
OdIwtgf6A3ay2ULqMfMPDhCpiMXYMnqOQ/4ZD5BzMHYCqN5gUeE7U11uqYNx+T2O
m90UbOesNCy+1cNJM/zYPjwi5FS65w9Xr3G9AXsNsyyD32DbTwJQQggQdwd/51z9
iBYeZdZKmHIsPBrCC2ADQ0XKzel3RlKCLbKeML5LULb46qtNWyd5DP1AnXQDTDQS
cdmGl180PpiDPXwFrtiqaex2bdCtMHYcUcTx7+0AdmUV8KJc1yezQDiS2XbyMeLq
+f/T4BpAzLkQnkoj5Nw1h3cQ5cbOipYqRzPQMWIMdsgFrifTLYkw0uM3SzaDaHzP
9LZtn+4ARYGfab5RQmcEDomaw/aoeQ==
=HJ6W
-END PGP SIGNATURE-

Accepted altermime 0.3.10-10 (source) into unstable

[Boyuan Yang]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Jun 2019 12:44:58 -0400
Source: altermime
Architecture: source
Version: 0.3.10-10
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Changes:
 altermime (0.3.10-10) unstable; urgency=medium
 .
   * QA upload.
   * debian/control:
 + Update homepage field to use secure URI.
 + Bump debhelper compat to v12.
 + Bump Standards-Version to 4.3.0.
   * debian/watch: Use secure URI.
Checksums-Sha1:
 1a05697c76c8bc37418f5caed0682688203df4d0 1864 altermime_0.3.10-10.dsc
 b7948d467b1aa15446302ac0f540852e0c01b4b2 13196 
altermime_0.3.10-10.debian.tar.xz
 011fd7a652044437c1a29317aece4c8b5b61472f 5761 
altermime_0.3.10-10_amd64.buildinfo
Checksums-Sha256:
 34a1a305512202397cadebfd2c58a3ddf064243f1aac48c972653ee8740be38e 1864 
altermime_0.3.10-10.dsc
 c221dd2c34432bb95f5a7c9b3ae22a5b8ec235e35d5fcf5db94459799d82ae3a 13196 
altermime_0.3.10-10.debian.tar.xz
 27b43c34d0595d54e03805f0ee0147bb8ecf57732de8154f892ce2a37486047a 5761 
altermime_0.3.10-10_amd64.buildinfo
Files:
 c4e3e0ab08d36eb114fbb9f464c626e9 1864 mail optional altermime_0.3.10-10.dsc
 81b2064ae3870175a097d3ee6dbe9f4a 13196 mail optional 
altermime_0.3.10-10.debian.tar.xz
 8deef84c6008af46bcab9f94933c616a 5761 mail optional 
altermime_0.3.10-10_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl0TpHkACgkQwpPntGGC
Ws4nwRAAmthNz6wJg5/ixIcf+M6gTEm4NFh7+27gjVfhqCPvhfUM+pfZyV9mDsGV
0D0JxtC+GWkKTZsWImBV20CTX1ThqgdGoxh8aMQacBYgVvRU9Fuc02D3BC3OR9qA
faUpauU15oX/ZtT9yMnThmwoH9y7S536MXFJQBAcx4gtSw833bPGr0kfwi0E2B6K
ts++ye7l7diFB59SMtFibkL4yFKsHLe0+XOIbBoCFtd+X5X8UV1EKQfzm4wDpvgI
YZa4FjzF+be6WB9zHAqrSFsxOezhQz6QplG9Uk4m3B96dkvwp3iT2pI5SZ7yIdPp
VGVuHYfV757Cc8ebuRPM3A7Ibf/CPu6N8DeZ7qTFbbCK9gl89Fbh8g5j4wsTYiM1
184JabV68IXGrGw0XbgjqMUvN3Vlm2aa0SgiwvTPUtP8W9O1hIzIN/u9QOVnTXa/
9A7CNu70ZVoY7/6Te5gTzGTGfjuHcA+9cmTl3g2w0uxqPQGAM6cQPjcC3GRKon2A
1MRf48cz7PQQ73PopUXSnuGYxY1EN+zu9LKlF9GOcvl9MmmYyIz+tfS9VlysnsuU
USb3HXwtUXZJT6wscpuHV7sCXwxMb1VUfOhW2+xVa9pMm6EW3nfOTZZKP279nG4u
XuBw4wKfC2s/H0KmqQlhTARyO2ForgdvQLopUaYeRRSynHPyH8A=
=R+01
-END PGP SIGNATURE-

Re: getting rid of "testing"

[Antonio Terceiro]

On Tue, Jun 25, 2019 at 08:08:22AM +0200, Ansgar wrote:
> Hi,
> 
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes?  We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
> 
> Related to that I would like to be able to write something like
> 
>   deb http://deb.debian.org/debian debian11 main
>   deb http://security.debian.org/debian-security debian11-security main
> 
> in sources.list as codenames confuse people.

As a data point, having "stable" and "testing" stay around is very
useful for CI purposes. For example on ci.debian.net all our setup uses
"stable" and "testing" instead of the release codenames, and it's useful
to have a system that does not need manual intervention when the meaning
of "stable" and "testing" changes.

With that said, I think that for regular user systems, having suites
called debian11 and the like is a great improvement.


signature.asc
Description: PGP signature

Re: Content Rating System in Debian

[Dmitry Eremin-Solenikov]

ГI'd say that we should never be touching anything like this.

вт, 25 июн. 2019 г., 7:57 Bagas Sanjaya :

> In order to inform to users, especially parents, about potentially 
> objectionable content in Debian packages, Content
> Rating System (CRS) can be deployed to Debian. With CRS, users can choose to 
> install packages that is rated for their
> age. In some cases, CRS also filter or block certain contents in certain 
> jurisdictions when legally required.
>
> Exactly for this reason. By filtering you will limit the freedom of users.
And if the legal guardian of the user disagrees with the rating, either he
or the user will have to lye about  their age. Please, do not ever consider
to add such rating system to Debian.

Re: Content Rating System in Debian

[Matthias Klumpp]

Am Mi., 26. Juni 2019 um 10:40 Uhr schrieb Bagas Sanjaya :
>
> On 25/06/19 20.19, Matthias Klumpp wrote:
> > [...]
>
> So APT need to do what you mention, that is determining age rating not
> only based on AppStream metadata, but also on system locale?

Yes. Since the things that determine age ratings depend on regional
(!) legislation, varying wildly between different countries or even
within countries, that is the only way.
I am currently working on a plan to centralize the age mapping in
libappstream, but tbh I do not thing that we will ever have a fully
legally sound solution for this without employing a lot of lawyers.
There is just so much stuff to take care of, and so much regional
variation, that a software solution will likely not be able to cover
all cases.

See https://hughsie.github.io/oars/ (which is used in AppStream) for
details. As the intro text says, we rely on people being honest about
things and are purely informational.

Cheers,
Matthias



-- 
I welcome VSRE emails. See http://vsre.info/

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

[elementar]

Where do I find kFreeBSD-amd64 isos, from testing or unstable?

Em sex, 12 de abr de 2019 17:49, Joerg Jaspert  escreveu:

> Hi
>
> back in August 2018 we discussed architecture inclusion into
> unstable/experimental.
>
> Today we had our regular FTPMaster meeting and discussed hurd and both
> kfreebsd architecture and decided to remove them from unstable and
> experimental 2 weeks from now.
>
> --
> bye, Joerg
> The sun? That’s the hottest place on Earth.
>

Re: getting rid of "testing"

[Ian Jackson]

Andreas Tille writes ("Re: getting rid of "testing""):
>  I never really understood why we need these codenames.

Simon McVittie wrote:

| Back when the release team decided on a per-release basis whether
| this was a "major" or "minor" release, we had the excuse that we had
| to use a codename for testing because we didn't know whether etch
| would be released as Debian 3.2 or Debian 4.0

I was around at the time and I have a vague recollection which roughly
matches Simon's.  This reason no longer applies, of course.

I regularly make mistakes about the sort order of these codenames.

I agree with the rest of Andreas's message.

>  Please leave testing as a name

As I said, I see no reason why [[old]old]stable and unstable need to
be abolished as names.  They will still be useful in conversation,
even if they were never very useful in apt soruces.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Re: getting rid of "testing"

[Andreas Tille]

Hi,

On Wed, Jun 26, 2019 at 03:10:27PM +0200, Philip Hands wrote:
> The version numbers are also showing up on login and desktop backgrounds
> so I'd guess the bulk of users know exactly which number they're up to,
> but a pretty vague about which codename goes with that.
> 
> Oh, and for me that also applies to speech -- if you say 10 to me,
> there's no way I'll later remember 9, but if you say buster, I'm quite
> likely to remember "two sylables, begins with B".
> 
> Can we not just have both?

I know +1 postings are not really welcome.  However, in this case:  I
never really understood why we need these codenames.  IMHO some
marketing thingy which I tend to ignore.  I fully agree with Phil that
these can lead to confusion and the usage should be restricted to not so
important use case.  Please leave testing as a name as is - I'm using it
most of the time on development machines and it serves a really good
purpose.  Those who do not like it can easily ignore it.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Accepted pgbadger 11.0-1 (source) into unstable

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jun 2019 14:42:10 +0200
Source: pgbadger
Architecture: source
Version: 11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
Changed-By: Christoph Berg 
Changes:
 pgbadger (11.0-1) unstable; urgency=medium
 .
   * New upstream release.
Checksums-Sha1:
 0a62f215c7b0d9c67ff7f48ae78900291e32abf9 2031 pgbadger_11.0-1.dsc
 0c8f4552aab487d5b0a95e714503dfd8d6f14f3c 1661028 pgbadger_11.0.orig.tar.gz
 3a721a33a7a22cf42dc6c82d4cbf8d4a351b824e 5744 pgbadger_11.0-1.debian.tar.xz
 5e9ef622aaebe81d0d1acda9e1e0ba5396a5053d 5496 pgbadger_11.0-1_source.buildinfo
Checksums-Sha256:
 0863145f752045919ab282b04b21eb8ee157920b4f5d67daea0fe4af977c7629 2031 
pgbadger_11.0-1.dsc
 ec295214fb4dba7762082cfd1ea2491e23a5fa5ecc3590fcfd6fc6b8d229d174 1661028 
pgbadger_11.0.orig.tar.gz
 caf4aca192c2cebd9456a42ec2dad89339621b4e279616bc4023df966d155fb1 5744 
pgbadger_11.0-1.debian.tar.xz
 1a9a70973812b0bbc5b49d9bf7266d35a44748486fe7227826114e6a067e8e55 5496 
pgbadger_11.0-1_source.buildinfo
Files:
 c61f6bb67a309806717f1c1f52ac90e3 2031 database optional pgbadger_11.0-1.dsc
 6850dc24ad0753b646cdd1967d447338 1661028 database optional 
pgbadger_11.0.orig.tar.gz
 0e7c9f0922b1e7c494ebe6a43c4d9487 5744 database optional 
pgbadger_11.0-1.debian.tar.xz
 c45516f7a141f9640a23d7d5f9c84962 5496 database optional 
pgbadger_11.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl0TaWcACgkQTFprqxLS
p64CphAAjVE+7nwLYMwxPJZkc5PQ2TnHbGk8ougs/sXsfcO5f50ckMYKhf+STAL6
0DK9Ubf2aoL9ETg6pzqTUiQ/QaVbef+PDMZtI6B9HmKA5XdQTCjdnT/ngZVztypP
86ebw3w7srbP/DVf+MnAhV0/qS0p+3vMgR6C4qWj643fBhVnJ1BuKjNkPIKxj9Iq
xTM6m0I+ffEfY3RATCbLESeYl7/3ZR+zhzuBnokkDg5kknuO19u+qI9BPwz6knKw
Ok2WETlIg/HU081W7AByLR/oxUcclJIAeGYCcmifaNh91BpML99siiBpfT+KItkj
q+W6GSfQ9FAdpv5ett9aSQsEYnatxQM3PTo5q7KagxgOTEG1nVzfR7wrzhwqpOxc
lCCAndxBlH1aAOJZm97qty5h1t2F4VrTHSu1FeiCXzgssFy6eSUWoQpogCNuPZSK
2Ughoy+8+qT4qNxrp60W8Lb+2Xv0X8eq/KgrowNmFK9FTuF135s4jpUSs2jfOKIw
Q7fJkuStDuhdAWBZLTtEQmG8UOCw9WNms68g9X6DcWMxW2Hlnb4mjKyva7sJ4LIl
xaGuPqBQEUfRU6kntQo3pDuVDmoep+uQWgzsOjwjZDel+TXPW0f1HxJwBfya2GSK
pB6nYzWfgs9hTtBgp8r4S/3xycqPVYmv7fu07nTvNzfziqwlHuU=
=owvV
-END PGP SIGNATURE-

Accepted openjdk-11 11.0.4+9-1 (source) into unstable

[Matthias Klose]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jun 2019 13:51:07 +0200
Source: openjdk-11
Architecture: source
Version: 11.0.4+9-1
Distribution: unstable
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Closes: 931115
Changes:
 openjdk-11 (11.0.4+9-1) unstable; urgency=medium
 .
   * OpenJDK 11.0.4+9 build (early access).
   * Add another break for libequinox-osgi-java (<< 3.9.1). Closes: #931115.
Checksums-Sha1:
 e448a8afa3dea129dc8fc73874e165923d9db3fb 4692 openjdk-11_11.0.4+9-1.dsc
 b1c0d67a75c7edaa24905864f596e1355951a4db 75536908 
openjdk-11_11.0.4+9.orig.tar.xz
 5c9a1620ffd5eedc65cdaed3d0fa340075e7cd9f 16 
openjdk-11_11.0.4+9-1.debian.tar.xz
 4f29b87499538659f730880b622690ce25d8fe19 17709 
openjdk-11_11.0.4+9-1_source.buildinfo
Checksums-Sha256:
 5bec35601d0204ea195df5ae4db1a79d923775a289c6195248f409c2e573ff97 4692 
openjdk-11_11.0.4+9-1.dsc
 ee3998e9dac9b12ee34857ec14520f3ecd4f0c5b03ced923ee02bd9493a7b98d 75536908 
openjdk-11_11.0.4+9.orig.tar.xz
 57dc2d4c7021b40b9bb3ebc35b946113c46b3a2b9d9fa849eb6f2da2ea32b7d1 16 
openjdk-11_11.0.4+9-1.debian.tar.xz
 6957d02971f9059aabf0bc810cbb8d648416a3f85634c88c77586df54b23f650 17709 
openjdk-11_11.0.4+9-1_source.buildinfo
Files:
 b05f3d9c78e38086a96f7c45af6c2717 4692 java optional openjdk-11_11.0.4+9-1.dsc
 aab5f2a6c93c2072ce8720831cd0dea2 75536908 java optional 
openjdk-11_11.0.4+9.orig.tar.xz
 c7dbcd756617a30df307a60d0877fbae 16 java optional 
openjdk-11_11.0.4+9-1.debian.tar.xz
 2d58c1ce57479cc9424eb211356a8321 17709 java optional 
openjdk-11_11.0.4+9-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl0TXV8QHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9eulD/0Yd/hrc4m9O/KidvXuDvtVbGhwhykxMAQd
kZXdIa04crcQueuXXr2H9xsd/wKvMpxU7GzyoZPMEYIe73yp7gbwfB0T5ETKCzEh
wehS8eQlKvPqrY12xiVUKsY0ZHMQdeyeKgj5j8LAAj6fhUOhMqtO2UCmLDQhIlXW
gf7OyXfHSgtYJsEYRG9VBa3tiXQVPe/gcQTs/5UismY91ZMmM4zRcESgyFp9Cu4n
89L4w4ZHH1x84gE8lojYwq+25ArfQYscdTjTG9oBwpa9w3Do5qBvT6CE9G9YKffq
siqd5IKWWPNDCH0zUquMiTfr1ELibMhn0Fz2Yais+6P9EV6LnuJIQdhCXSQ11c5O
3Rcl0pZn+oIwazESvIbDmh0yzURRS1f115XyNzVlcmLO9WbLfywKsGNKaYO9Wrsr
+akh0DGXeFbV8mLfw8wCvCk0IYoDn6+XxJyQqD5lHEkqKsXp6nNzxIhFszHi65us
CLCBCTg2YaEkA8xg2YjhksCXtYMlK+dYbNVDYs4TZcW7ZwMyr8bLpTKS/SJQxs+l
0mbLr5fSEzNsTqAch9jPXto7bZtlsDu1xhB14RTnSiHgswJBX2cjLM2LryTE0EjQ
JmZN8ThiYcyJ5ozToxRMv43AUMHRJdOmJSn0S9v1mAEoreKQ4nQjC/m4/ngtStVN
HsMQoYJ0PA==
=Dxlg
-END PGP SIGNATURE-

Accepted moment-timezone.js 0.5.25+dfsg1-1~exp2 (source all) into experimental

[Kyle Robbertze]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Jun 2019 12:42:01 +0200
Source: moment-timezone.js
Binary: libjs-moment-timezone node-moment-timezone
Architecture: source all
Version: 0.5.25+dfsg1-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Kyle Robbertze 
Description:
 libjs-moment-timezone - Parse and display dates in any timezone
 node-moment-timezone - Parse and display dates in any timezone (node.js 
library)
Changes:
 moment-timezone.js (0.5.25+dfsg1-1~exp2) experimental; urgency=medium
 .
   * Make package compliant with JS policy
   * Move package into JS team
Checksums-Sha1:
 0b2485a00dbeb9f87688ff9e0ffaa45277a62c73 2300 
moment-timezone.js_0.5.25+dfsg1-1~exp2.dsc
 f6170cb3f53db3dc1533af812c1ee36c7e3c2d28 2768 
moment-timezone.js_0.5.25+dfsg1-1~exp2.debian.tar.xz
 b03915ad53cc4cc1081e696b595e6435895b7a54 700332 
libjs-moment-timezone_0.5.25+dfsg1-1~exp2_all.deb
 dfb613ab3ef70bef0eca7f4b776755e41442fa71 6078 
moment-timezone.js_0.5.25+dfsg1-1~exp2_amd64.buildinfo
 00a85f0fd28e46aa02f3dc12715ec93c55ff5dd9 6412 
node-moment-timezone_0.5.25+dfsg1-1~exp2_all.deb
Checksums-Sha256:
 e7f7943673c1bd8e29f7200c38021c595f821c4929e741e66449680666cca3e3 2300 
moment-timezone.js_0.5.25+dfsg1-1~exp2.dsc
 f8d0bb362639830f4cfaa0157ead581dcfea54ae66845dfa2af6d75fe7ea26f1 2768 
moment-timezone.js_0.5.25+dfsg1-1~exp2.debian.tar.xz
 5acaef876646dbd1a20f80506bb0b8ebbaa2b3f7cd03c743d46d3592370d770a 700332 
libjs-moment-timezone_0.5.25+dfsg1-1~exp2_all.deb
 eeb0de3b7082cfe26810e5b61873811c1d4766bb0cd38bafc2e4bf3a97f05e04 6078 
moment-timezone.js_0.5.25+dfsg1-1~exp2_amd64.buildinfo
 7af8f95841dd0e1de5761917cf6e41748b47a36fed90b0383b57040cdee32bad 6412 
node-moment-timezone_0.5.25+dfsg1-1~exp2_all.deb
Files:
 6178b7cac2aeeeb5cdcb050a40a59e15 2300 javascript optional 
moment-timezone.js_0.5.25+dfsg1-1~exp2.dsc
 02bdbb6d86302806bbefd7b3277359bf 2768 javascript optional 
moment-timezone.js_0.5.25+dfsg1-1~exp2.debian.tar.xz
 4918af4b17792f0d8f4640c47a8b63ed 700332 javascript optional 
libjs-moment-timezone_0.5.25+dfsg1-1~exp2_all.deb
 f790efbaf9917c6ae05adf3154bff152 6078 javascript optional 
moment-timezone.js_0.5.25+dfsg1-1~exp2_amd64.buildinfo
 2b493802a06fd6148b73931f325e6339 6412 javascript optional 
node-moment-timezone_0.5.25+dfsg1-1~exp2_all.deb

-BEGIN PGP SIGNATURE-

iQJMBAEBCgA2FiEElqWPGCu4+bgcXyczhU8Hvggt8U8FAl0TaqYYHHBhZGRhdHJh
cHBlckBkZWJpYW4ub3JnAAoJEIVPB74ILfFPNrwQAKkia7pKUdgNbb1DWXYvx5kK
OnNpYme5Vp3/fdjHWWHQ5r8sF71hCJLFBwDqBrEmPImNVJHVEshbf8XMdkYB6K1L
8v2CWvJPZgCFhZEAd3zhDCh77ia+UndqCafGi3CJBIzBFg8sAZAJ6rBzbyk4laa1
PPV4uXRr40iXmcDWh7lMPw/PkHlxeY/F+Z9aM8SewxMI/xbj1SAYG/GZbZgBteOt
lM/fGMu8J4DryLvVuKtYeVO76GW66scDYANlMZHzbWB5eqvh1ghqMx8LoaXz/VGy
pv0f7jMe1P1TCB0iO/7YHADRnM6L+F0g6RNmB7CMjEk43dUcKP5b4DVAVbfcDItx
m2qiqzscaKZtPZHOctsvyJq5fU0r/4d3NJLx+fYlTNPQU/VncJS3eYkwoHK8w6U7
bYDwAxI2AWbH8yPmOa8v475k5O/TOSIdNQpcBfHfMt9Op0cxp8hpPxLlgVj/vf/V
7KmIE1NVv+Psyqm0/qtPhkYX8TVZrjafNaN0Ue24UhRlYas6AIK84YSYa2xkD/Yc
VlJW52UfllWoVbaUBtgEFsg9YdaTznykRWkrR0EEMDGpIku3LTkG4197N+xh7L5A
hAzOvEEDysXFHvXYSZ6dLQvWY5oZVFDkyU1Zv7HAuco/pSAR5ec3xzeMhOD4VqlZ
Lnf6khvJFxksm6SZNAHQ
=Eb+H
-END PGP SIGNATURE-

Accepted jstimezonedetect.js 1.0.6-3~exp2 (source all) into experimental

[Kyle Robbertze]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Jun 2019 12:11:26 +0200
Source: jstimezonedetect.js
Binary: libjs-jstimezonedetect node-jstimezonedetect
Architecture: source all
Version: 1.0.6-3~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Kyle Robbertze 
Description:
 libjs-jstimezonedetect - Finds the zone info key representing the timezone 
setting
 node-jstimezonedetect - Finds the zone info key representing timezone setting 
in node
Changes:
 jstimezonedetect.js (1.0.6-3~exp2) experimental; urgency=medium
 .
   * Make compatible with Javascript team policy
   * Move package to JS team maintainer and update VCS-* accordingly
Checksums-Sha1:
 03d663d48dd23ef897cd179c166b4300295d8a2b 2245 
jstimezonedetect.js_1.0.6-3~exp2.dsc
 f046ab0d75cd7771b0af9feffaf776f8321c9f42 3128 
jstimezonedetect.js_1.0.6-3~exp2.debian.tar.xz
 8ed2bf999553a8d79101aa34bbee2a5699a39fee 6011 
jstimezonedetect.js_1.0.6-3~exp2_amd64.buildinfo
 06284f0148c02c5566516fb586699577c6f2dff7 11912 
libjs-jstimezonedetect_1.0.6-3~exp2_all.deb
 2a2fab6e32b6ec7603e1751c5cc21e53f9f417ad 3096 
node-jstimezonedetect_1.0.6-3~exp2_all.deb
Checksums-Sha256:
 397c740dd9d63d30b134eacb99b7b561f44be4b3e82f20eb6ef5f6be899e8c95 2245 
jstimezonedetect.js_1.0.6-3~exp2.dsc
 ee5ac1f3a9a57bf9f30e8fbf7de99280229b11434b86c446a7c707af1c7f3ebb 3128 
jstimezonedetect.js_1.0.6-3~exp2.debian.tar.xz
 afef650082bd840372a6264b342c2d0b805ed33341b987f71912e8b08a6d11ab 6011 
jstimezonedetect.js_1.0.6-3~exp2_amd64.buildinfo
 b9f09fa69c97f2e57b304cf8d76196796cef3bdb24208501aed1f9fb8f844f25 11912 
libjs-jstimezonedetect_1.0.6-3~exp2_all.deb
 6b56f1016417d7049dd02de69857bb8cd5a0d9baa19c9e1eaff1d6e0c63a7e1f 3096 
node-jstimezonedetect_1.0.6-3~exp2_all.deb
Files:
 08256bf8978044545f2f3ccd6b36f58a 2245 javascript optional 
jstimezonedetect.js_1.0.6-3~exp2.dsc
 5404288f948c0f8876c668e0fe574581 3128 javascript optional 
jstimezonedetect.js_1.0.6-3~exp2.debian.tar.xz
 a5e02de89e13836c4dbaf8371c897337 6011 javascript optional 
jstimezonedetect.js_1.0.6-3~exp2_amd64.buildinfo
 8bed25729fb4e97f44fdf78118199488 11912 javascript optional 
libjs-jstimezonedetect_1.0.6-3~exp2_all.deb
 38f07ecf7e685b6595a930401858b00f 3096 javascript optional 
node-jstimezonedetect_1.0.6-3~exp2_all.deb

-BEGIN PGP SIGNATURE-

iQJMBAEBCgA2FiEElqWPGCu4+bgcXyczhU8Hvggt8U8FAl0TYP4YHHBhZGRhdHJh
cHBlckBkZWJpYW4ub3JnAAoJEIVPB74ILfFPmPkP/3Yz97X3UtOS00gIB4kRf2Kz
cJNskwlOzsEaYUer/oL4pULIW/A6zwZB9/b/iUll7xpIoT0QnoVaFM1lNHepkn3K
4ZDdFPgs3fB7N0QNNixDfeONMUarp5j7m2mppAvA5lbs+Qz3XwUY6hzyZFSdg7NN
t4HPg46OOdas0r7pJ8n/IlcaOxWMlrPHxz8e3Vx6Y1PRiBZVIuTGSxGI7moLfmWr
J1xQ7kWovAQw3Judj0hKNVYfZae0tD5Vfu0NZDvN6X6atJjMDIVvmnOi4GyF4THN
q0tDwUZwOYqyRYWp+1TTwMsZz91CldNcuwm+yyrMjtg+3MQVTjD0k0ZGyDcufN22
fyTgofJyfA62yyk/0L96ro7cr1KB4AlX9v5MqdHDGlZyxClqqeB/t96Huss0mwwA
PsjU+Z9zcgQNb2GbwKY2rNROwUH+J1eh4ocedThM9c4RhUkN0IHdJ59mzauENpNR
tJx65bt23o5Q3ogfbcYlPPbLegt5pfYdvbm7PDOBfzD6DOkBEZK/dw9ef9devYLA
jScIV2k7MPHARWqaGVLCTHNBqWfb+UOkxHs0jvm25DpD6/MIj2Vu9Vc/k3TiVYkt
/4G6sd0HEzon9iqi81HNWD7dCijtav7Yc6YJKowa8+ycdCov89/Zn8etb8QtYPvO
DHQlwdKWrwUoultW9jA0
=qtf1
-END PGP SIGNATURE-

Accepted cockpit 197-1 (source) into experimental

[Martin Pitt]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jun 2019 12:53:30 +
Source: cockpit
Architecture: source
Version: 197-1
Distribution: experimental
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Martin Pitt 
Changes:
 cockpit (197-1) experimental; urgency=medium
 .
   * New upstream release:
 - Machines: Support all storage pool types for new disks
 - Machines: Show available space on host at VM creation
Checksums-Sha1:
 58ae09462ef9db380ac6a1136137c8adf061c7a4 3047 cockpit_197-1.dsc
 8dd81933d230b654a140785cf544c322b2a57ee9 8995456 cockpit_197.orig.tar.xz
 18afe80b249f1c5de4aad6f50b36b3a445983e61 15160 cockpit_197-1.debian.tar.xz
 def0f2c9f3eea78233737f08d614d1cd2584c8fc 9673 cockpit_197-1_source.buildinfo
Checksums-Sha256:
 6e0e94ed35ba9d00798a7447b570767300be47c79731f2984bb9078bae88a660 3047 
cockpit_197-1.dsc
 19a8cd2fbf742c66b2b61cc84ab517888b6956652950ee5a375742dd877c687a 8995456 
cockpit_197.orig.tar.xz
 c33f2ce6ff36d3a79eb1743d7895df726ac61da999fdb860d772665384e17550 15160 
cockpit_197-1.debian.tar.xz
 df5a18645f55095d8bc82191986b2e4b32c50284d5a38f3deda8aa80ee437e1b 9673 
cockpit_197-1_source.buildinfo
Files:
 b282a8a739871b603619d811bd69a9a5 3047 admin optional cockpit_197-1.dsc
 75cd7cff3731150ea350f3354d23f836 8995456 admin optional cockpit_197.orig.tar.xz
 7659c98def13250f2146f4900fe9d302 15160 admin optional 
cockpit_197-1.debian.tar.xz
 ac2fb0e02973e3977adef06e7e13ec17 9673 admin optional 
cockpit_197-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEPbRrVe+lnUDmIyFI0U7xXa/hE0cFAl0TazQACgkQ0U7xXa/h
E0cV1Q/+OdzcY56rmEIxCLmIgWyyQxkIk5yXluB/C65zwfFC58wwuXFAKDQroNKS
QeTSpKbYNv7oN5pSC4zPLlSPzenV9NiZprf2lyWzPmTsVPsj1gNt+sG9BGY4oXuI
9QRacEBmKfUV3a7u1xv54st3InP4BKPaScbTsdtITvgxMLMLfmBlzui4f2SUrdRh
JyUbjAOrLoWhnqv87k+xPLhhiI0Z+OvGaMn2nyTuxFWIVPGox8ZvbGbHAmS+5qoh
ptefKbch6f59ayX3EWGIIdav8o7tB1wdyyiMjOmBBCePH8LPVQoMbRRjp3qvibvt
60FRStz8iDPg7C6G2wCVJesKqlmfvzvGpc6La2LSvjmWX8OAuyfhmkL1FNuQk8zz
HqjSE6NF8aIuk28F2uQP2ilmUA9Md8Eq7qWyB97qwm3ptNN/IDfdKhZYpOoiPpea
NQHuEEpu2dQvxW8ge39OW6G22Emm7EODkeVnFFxqlZRcD43pheBv8oI5jOsuudKw
jlnru6yAFZlqFWOTD+SWAIVpEE4XrXxyedm0+b7EJhWQ6iu8vGDL69irsxvxl9Tt
r7rERFEfZvm24b5G+/hJm739HRaEvlLwpPJIYSQ1DIe9BlpWKt3t6UeUMNMiSFRk
PGHBfrP9q3/WkCqxHyS6acD/675QM3kqwVTc6a3pYbcwisrCEFc=
=+Fxx
-END PGP SIGNATURE-

Re: getting rid of "testing"

[Philip Hands]

Michael Stone  writes:

> On Tue, Jun 25, 2019 at 08:07:51PM +0800, Paul Wise wrote:
>>On Tue, Jun 25, 2019 at 8:04 PM Michael Stone wrote:
>>> Having "stable" in sources.list is broken, because one day stuff goes
>>> from working to not working, which requires manual intervention, at
>>> which point someone could have just changed the name. Having codenames
>>> in sources.list is broken, because even people who have been developers
>>> for two decades can't remember which release is which without looking it
>>> up. (Which is harder than it should be; maybe we should have had
>>> /etc/debian-releasenames or somesuch from the beginning. lsb_release -a
>>> is helpful when available but doesn't have context, and many users don't
>>> know it exists.)
>>
>>Personally, I can remember the names and their order much better than
>>which version goes with which codename or suite :)
>
> Well, every problem domain has its rainman :) For the rest of us, 
> there's google.

Personally, I use wikipedia's page about debian revisions, and it's not
that uncommon an event for me to need to look that up just to make sure
I've not made a stupid typo.

I like the idea of adding the list of releases somewhere (probably under
/usr/share/doc though, and including dates for start and end of support
etc. perhaps)

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

Re: getting rid of "testing"

[Philip Hands]

Adam Borowski  writes:

> On Tue, Jun 25, 2019 at 08:08:22AM +0200, Ansgar wrote:
>> Hi,
>> 
>> what do people think about getting rid of current suite names ("stable",
>> "testing", "unstable") for most purposes?  We already recommend using
>> codenames instead as those don't change their meaning when a new release
>> happens.
>
> And for this exact reason so many people want "testing" not "buster".
>
> This way they get 5-days-newest versions of everything, without having to
> suffer broken uploads, broken dependencies, etc.
>
> Using "buster" would mean that at some moment their updates suddenly stop,
> and they have to manually migrate to the next version.
>
>> Related to that I would like to be able to write something like
>> 
>>   deb http://deb.debian.org/debian debian11 main
>>   deb http://security.debian.org/debian-security debian11-security main
>> 
>> in sources.list as codenames confuse people.
>
> Hell no!  Even though I'm among most active DDs around, I just had to look
> up whether "debian11" means Buster or Bullseye.
>
> It's same eg. for processor names: "Skylake" means Skylake, which is used
> within 6 or 7 different numbering schemes.  Even people who care what
> processor that is will so often need to look up versioning numbers -- as the
> public names are about marketing segments and so on, not about how a
> processor behaves.
>
> A code name is also so much easier to talk about, especially in speech -- a
> codename is one or two fairly unique syllables, while a number is longer,
> and it's usually surrounded by other numeric values within other semantic
> domains.

These things are clearly a matter of taste.

For me, the numbers would be _much_ more useful.

I'm perfectly capable of typing slink when I meant stretch.  The coming
era of b* releases is going to be a right pain for me.

I would certainly not end up typing 2.1 when I meant 9 though, and if
somehow I did, I would be able to notice the mistake instantly, whereas
my dyslexia will cheerfully hide the wrong name for long enough to allow
quite a lot of hair pulling.

The version numbers are also showing up on login and desktop backgrounds
so I'd guess the bulk of users know exactly which number they're up to,
but a pretty vague about which codename goes with that.

Oh, and for me that also applies to speech -- if you say 10 to me,
there's no way I'll later remember 9, but if you say buster, I'm quite
likely to remember "two sylables, begins with B".

Can we not just have both?

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

Accepted python-mimeparse 1.6.0-1 (source) into experimental

[Sahid Orentino Ferdjaoui]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jun 2019 11:27:10 +0200
Source: python-mimeparse
Binary: python-mimeparse python3-mimeparse
Architecture: source
Version: 1.6.0-1
Distribution: experimental
Urgency: medium
Maintainer: Mathias Ertl 
Changed-By: Sahid Orentino Ferdjaoui 
Description:
 python-mimeparse - Parse mime-types and quality parameters - Python 2.x
 python3-mimeparse - Parse mime-types and quality parameters - Python 3.x
Closes: 844409 930499
Changes:
 python-mimeparse (1.6.0-1) experimental; urgency=medium
 .
   [ Gianfranco Costamagna ]
   * Fix capitalization error
   * Team upload
   * Upload to experimental
   * Fixup wrong dependency on python3
   * Bump std-version to 4.3.0, no changes required
   * Bump compat level to 12, drop version check from python-all deps
   * Convert to pybuild, run testsuite in the right way(TM)
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Fix Format URL to correct one
   * d/changelog: Remove trailing whitespaces
   * d/control: Remove ancient XS-Python-Version field
 .
   [ Sahid Orentino Ferdjaoui ]
   * d/watch: Use github tags to download taballs.
   * New upstream release 1.6.0 (Closes: #844409, Closes: #930499).
   * d/control: Add dh-python dependency.
   * d/python(3)-mimeparse.docs: Align with the change
 s/README/README.rst
Checksums-Sha1:
 6850e9a2a3de7dec64aa9eba71a1a062a1307742 2159 python-mimeparse_1.6.0-1.dsc
 b3f7ec8959a2f07b12e480bdb41a7b54572c3a5b 6468 
python-mimeparse_1.6.0.orig.tar.gz
 e14ba8088f2162d926878eb9743a4e0c02361d84 3076 
python-mimeparse_1.6.0-1.debian.tar.xz
 11d5aaf9a218abea7a2fac9197930acff3fcc284 8341 
python-mimeparse_1.6.0-1_source.buildinfo
Checksums-Sha256:
 2d6020af44380a9ca045cdc666227d9b8d6ce3b8a247acc8dd11f06ed5254af1 2159 
python-mimeparse_1.6.0-1.dsc
 515b964bbcf0d7b6bf2a148a7d53c72ff64402e276f6202b95810545a1576b9d 6468 
python-mimeparse_1.6.0.orig.tar.gz
 4566f4271ab29630e8b0f6e378cda4d22529faee18ba815652c18a70e0ce058f 3076 
python-mimeparse_1.6.0-1.debian.tar.xz
 d66fa43082363f37797807e1f5e11b7745d16d13613fd523f376412d6e853da3 8341 
python-mimeparse_1.6.0-1_source.buildinfo
Files:
 3c11aa06cb64c9bdfb3b5513288f6c76 2159 python optional 
python-mimeparse_1.6.0-1.dsc
 554c116437eb2bc76ca8d0bdc46c569a 6468 python optional 
python-mimeparse_1.6.0.orig.tar.gz
 563a01d846f8c5fd1f79b970de1b390e 3076 python optional 
python-mimeparse_1.6.0-1.debian.tar.xz
 225aa7d42924852fe62f0b5d7d3c53a0 8341 python optional 
python-mimeparse_1.6.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl0TTxIACgkQ808JdE6f
XdnJiA/+Kqckk0SuXxG6pv7AZ1VTXNa7grhBUpS0kvgn8vGOpaJS8aQj9NsyM/+n
dEaJmon0nvcDz5F9pK4WvuQDDdAYsMni1dWH0FN8vdYLQr069vbEWVqXW2ZEjos1
SmnKgH6PKJ0mV4/SzJQ29rmaePXb53Asce84Tc8iODBu3fE72rSb/5v1/OzyKL6D
f3TCpHoTome2HYGKNutuMbYwEEdoUvT8x7Hgoa1aZXa+rLE0lVvFP7Sy1WvlONWI
mN6skKN/yeonax+17gXTSRFR8bd54SprbHjb2TjucNYK+2lKyDPW7yn6avXWt100
g70CplpKjndzEXKVMIPaSBPOqSzz3Pq493vKz2jUSZLU0B8hwPPl/GituPIScb7B
G2TC/j+AIOFHrJr5CI0yxvY6l8eR7OxzM+c6aR+oFSGFjxt4FGlsxl4mF+l2R8RS
bL8/FATRff7s4onJCa9Er2ERv2LhR5uobqFVf46Ba69psPYka9K35AegOuKLmrb5
8LHSBlmLEl4DLTROe4fz0Jmv42zxl5aZiMBND79wia+BFOhimOy+AqC5fexqErCV
zhWyL7yujbRnIR7YNhaJQneuVbUEA075h4m7xLXtJAdvnx+WojFN2pNwDW6MnHvw
0nv4P/KH4uqI1VOp8z9iz1xquboI+G7IlqKxSMrhZtQup6b5tQE=
=lOfY
-END PGP SIGNATURE-

Accepted python-periodictable 1.5.0-8 (source) into unstable

[Drew Parsons]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jun 2019 16:18:35 +0800
Source: python-periodictable
Architecture: source
Version: 1.5.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 923744
Changes:
 python-periodictable (1.5.0-8) unstable; urgency=medium
 .
   [ Stuart Prescott ]
   * Fix typo in Suggests entry for documentation (Closes: #923744).
Checksums-Sha1:
 75fec634be959e1ce9854d693591dccafce41786 2645 python-periodictable_1.5.0-8.dsc
 b5b2cd5bbe17e8520bd6bc78cd6d62694072c2e5 7160 
python-periodictable_1.5.0-8.debian.tar.xz
Checksums-Sha256:
 8a11b1193a583a99a2e1eb69598de4db28ec6865cd6f79b562eae529472ca598 2645 
python-periodictable_1.5.0-8.dsc
 75a096e2fe0a2085b83bd63fe67d07a22d06d2046e869650cdf7a5128df556fe 7160 
python-periodictable_1.5.0-8.debian.tar.xz
Files:
 3519f5351efbd0dcbd41dba22daac59a 2645 science optional 
python-periodictable_1.5.0-8.dsc
 0e2b9897d8b17ccd22ed1ee34522b27e 7160 science optional 
python-periodictable_1.5.0-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl0TK98ACgkQVz7x5L1a
AfrUbRAAinINpmcQrzD5rl0cAYAJdiugR4R0qRj99X0bBgtV+5c4Akpjx92CzFka
0O0DeRhSyibd2hydwVEWSo9tvz16mZI6GvxnfyYPqHtmfyiqOYDYdnDyh7fpVB/7
YguCZVfEWC6ZLmo9DwaIM4M8d7qZRRvir+2cEuQdl/1DFiAw50ldAPtOcw+2Wueq
wyZAr2Cq5nqdelsf3+lknmI4SBQHKcRbf2aW49f48mSQlvcJMkW65ndWpUY5687o
CmNFUo57RwWsLSmuxdCxha9KBKXL3R+waC5I2t7NP1z+lP+oZkINgR9v8IUWVcnz
OfniVnMzGyEWhI2umvvTsZAjyIqQr2wbAoOSF6+Iyp+1Y1Ys70vit+37abkUiwXO
PUuZ/efoe83Xny6cgrRYTj7LD9Aj9+RpIS4BiK+0g2qi3MSgGsfdydOS+cJseDdY
xdUz07yHkiMG6T15IU3zZBF/DN3ZCGwmFWKDxPxSn2FR6c+ADqOY2EyfopNrYL3A
mt4zsNDlpEO5acBzD/3IckmfdFbPn+7JHf74+HxpU9gQtsDqNQNDSWpLaSp8wQ3X
3KTHIkgHp2xIeJoSqZQlam+JLn1TxHExaghOwb7AKDEceTjeDuGM1RPzJcbHA5Nf
ySs6M1RtR3gtjbGGPTF0VXsQnLRQASLoXFuI5miD+vW56q7SPhs=
=4oc+
-END PGP SIGNATURE-

Re: Content Rating System in Debian

[Bagas Sanjaya]

On 25/06/19 20.19, Matthias Klumpp wrote:

Am Di., 25. Juni 2019 um 11:51 Uhr schrieb Bagas Sanjaya :

Simon McVittie:

Appstream metadata, which is canonically provided by upstreams and is
distro- and package-type-agnostic (available in at least apt and Flatpak),
has this as an optional field for self-rating:

https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-content_rating
https://hughsie.github.io/oars/

I suspect that's the only way this could possibly work without money
changing hands.

There are no age classifications, however.

So based on content_rating tag on AppStream metadata, we can add logic to apt 
in order to determine age rating for our
packages. However, external review (maintainers) may be need in order to 
prevent misleading information on
content_rating.

To clarify: Age ratings vary wildly between countries. So what we
expect is that software centers will not actually display
content_rating information, but instead compile an age rating out of
it based on the user's current location/locale and then display that.
Having a "one-size fits all" generic rating isn't very practical.

Cheers,
 Matthias

So APT need to do what you mention, that is determining age rating not 
only based on AppStream metadata, but also on system locale?

Re: Content Rating System in Debian

[Michael Kesper]

Dear Bagas,

On 26.06.19 04:50, Bagas Sanjaya wrote:
> Emmanuel Arias:
>> IMO this idea represent a big work. And if you want to involved upstream, 
>> maybe will be a problem. Some upstream, could not be interest on participate 
>> because could be a "extra" work. But if we implement a content rating 
>> system, the freedom could be affected because the opinion on a package may 
>> be affected by this new system. 
> 
> Regarding freedom, yes it can be affected by CRS because CRS can limit 
> freedom to use programs for some users
> (particularly non-adults). But CRS limit such freedom in order to protect 
> psychology users for long term from negative
> impacts of programs they used.

I don't think this problem is solvable by technical means at all.
You need caring parents (need not be 'real parents' necessarily) to really 
protect children.

Bye
Michael



signature.asc
Description: OpenPGP digital signature

Re: Content Rating System in Debian

[Gard Spreemann]

Bagas Sanjaya  writes:

> Regarding freedom, yes it can be affected by CRS because CRS can limit 
> freedom to use programs for some users
> (particularly non-adults). But CRS limit such freedom in order to protect 
> psychology users for long term from negative
> impacts of programs they used.

Surely this would be a direct conflict with the DFSG?


 Best,
 Gard

Accepted modsecurity-crs 3.1.1-1 (source all) into unstable

[Alberto Gonzalez Iniesta]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jun 2019 08:42:44 +0200
Source: modsecurity-crs
Binary: modsecurity-crs
Architecture: source all
Version: 3.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Alberto Gonzalez Iniesta 
Changed-By: Alberto Gonzalez Iniesta 
Description:
 modsecurity-crs - OWASP ModSecurity Core Rule Set
Closes: 928053
Changes:
 modsecurity-crs (3.1.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Fixes CVE-2019-11387 (Closes: #928053)
Checksums-Sha1:
 0354e64d026ec8377dac328de905a06d629a9d0f 1794 modsecurity-crs_3.1.1-1.dsc
 f868ce19fd5418b3559db11a9f465904b23fa106 251210 
modsecurity-crs_3.1.1.orig.tar.gz
 3b118cee096ace1df3cfe202261b32a5731f1f39 4168 
modsecurity-crs_3.1.1-1.debian.tar.xz
 863d929eb7768fcabd0571db981f44611d15 198596 modsecurity-crs_3.1.1-1_all.deb
 91b43af195f91bc3735046ac2c8e5441d8ea9469 5816 
modsecurity-crs_3.1.1-1_amd64.buildinfo
Checksums-Sha256:
 3d43cdef926d54e7716bc3a79877b19cb8c7142f0bd6ee74259a94663cd52f94 1794 
modsecurity-crs_3.1.1-1.dsc
 e57824fecc043bff38dac66fc3b6c2aeb4ba1648b746636bc7a6c50b9ca19e57 251210 
modsecurity-crs_3.1.1.orig.tar.gz
 509940d72097ae20832066a670c03c6e7fd5fdec4d5e32246ab7a4e071d82963 4168 
modsecurity-crs_3.1.1-1.debian.tar.xz
 210ddb65de6fdcd29ec01c404003791b9e50f2ce2888adb0b6deffba58006320 198596 
modsecurity-crs_3.1.1-1_all.deb
 f826f17de1c210c84f5edc936b41aec46cb53529df9140c33ea2b5167d08b5f9 5816 
modsecurity-crs_3.1.1-1_amd64.buildinfo
Files:
 84012c77ab25e4b87c51a30a6c664d82 1794 httpd optional 
modsecurity-crs_3.1.1-1.dsc
 30413d26cb15cb5cb446a4b13ebb1ef5 251210 httpd optional 
modsecurity-crs_3.1.1.orig.tar.gz
 c08f2938e23e7eeed754947917c24088 4168 httpd optional 
modsecurity-crs_3.1.1-1.debian.tar.xz
 92b67baa4ad44c78cae6599694c7667f 198596 httpd optional 
modsecurity-crs_3.1.1-1_all.deb
 7bba4d6864b0ccf53023ad9ae7cc2352 5816 httpd optional 
modsecurity-crs_3.1.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEEU0fL2D4wqetNfUvyAJszdWuaqlUFAl0TFLMQHGFnaUBpbml0
dGFiLm9yZwAKCRAAmzN1a5qqVWJhD/9TI24qLqN92QMvBU/alBcfp9BjbPyHRclI
56L366L8bF5Y0JXTiXCSsu5WSmi/vg/pzHJMcVmo3SBX+BOoAQkeELz/m5TFA8Nw
zuFKurraVAOVFKGVFR1PO9UcvuVkbHky6MayrF92/3VJZVUiN9bZKmptD9yAXN7q
PWmiOjRphlQI5PmEWf4ObJlZGNEU5uubVsdIhJ5pMa+RrkalEdG/tJxchwe+4we1
gwtPkNC2Vn66F7sxjqh1aMJ1MkASB4WHJDXAvYPv7Ha5ah4JJQ5G7WI3iJjK7gna
PTklXRkM6BTtGKISve09KBBTbqbH2ivRYD2xj45Eix2QiRMZz9RPXFV59kaVlEdd
INiojsjk0SvAnpb8IXSKzQ5c4+hGtaQpVadqX6ICUsYOiZoUskP9PJb3yb04JQ5Y
sgA7+yB1qugKy3GUW/nSRp1mOgpzkAFaxZFbK0qXAaNhk4Z/4xxzHqya5W3FtXkd
am0GHqb5I822YRZBXih/IdY6r1oeY3rMnet1oxO0FEnGnz3kj9bnj1MS2pEHx/9X
7Dz4KG4l3wq/da+JoxgNgxcLScCtjC4NSeGmZdO3GLLJlW59xhVml/oYQK1wkYGy
wae/fjYY+FzudPaPfIpIrsYcW6+BqprXePu0TLthsPP8EnaaXrUu0hUSrnQJj0H5
56CrRCGOtg==
=5U9V
-END PGP SIGNATURE-

Accepted bpftrace 0.9.1-1 (source amd64) into unstable

[Vincent Bernat]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jun 2019 08:31:30 +0200
Source: bpftrace
Binary: bpftrace bpftrace-dbgsym
Architecture: source amd64
Version: 0.9.1-1
Distribution: unstable
Urgency: medium
Maintainer: Vincent Bernat 
Changed-By: Vincent Bernat 
Description:
 bpftrace   - high-level tracing language for Linux eBPF
Changes:
 bpftrace (0.9.1-1) unstable; urgency=medium
 .
   * New upstream release.
Checksums-Sha1:
 42ae8ea85c68a08d207f0e2e1dabf18b529d1e59 1977 bpftrace_0.9.1-1.dsc
 e9b45e187abbdf9a22e8a19bdd6f033e36dd8bf3 704365 bpftrace_0.9.1.orig.tar.gz
 595cc77b673ccc6e9f16cf07f89ee734b63c32f5 3164 bpftrace_0.9.1-1.debian.tar.xz
 2ab04ee135d4503d34b3292196c4e762e6509c3c 9370196 
bpftrace-dbgsym_0.9.1-1_amd64.deb
 3f3fb520faad596ee55a110adc6feb9727414b67 7505 bpftrace_0.9.1-1_amd64.buildinfo
 9e92c37b3e1894a9d50ea0e3616f4a10f2acd5d5 378688 bpftrace_0.9.1-1_amd64.deb
Checksums-Sha256:
 f52e9af38fe35f0400d0d214c911769aa955d4d5243d747c15dd420faa4ec0cd 1977 
bpftrace_0.9.1-1.dsc
 1abd09c7e5e91774fca6a8d092bdd991a0509b0b9418b6c8590a3949157c6e4b 704365 
bpftrace_0.9.1.orig.tar.gz
 891bad4f60183e2278af7b82f2663f1e6b19991f03df0ec82aa787818d4e3d96 3164 
bpftrace_0.9.1-1.debian.tar.xz
 1f96d07ca7c7c96e0bacdc0a1b908d388d1c504ac4e1ae91b46603621f4efa1e 9370196 
bpftrace-dbgsym_0.9.1-1_amd64.deb
 e5b74807afec673e1e61b6d14125e6c51674c8e1bd14d694a3cd5af07040f1fb 7505 
bpftrace_0.9.1-1_amd64.buildinfo
 4e18f7ffa0498e2865d54ae6a32bd6ec0eeb98045ac64ad1f2c930f520a2d967 378688 
bpftrace_0.9.1-1_amd64.deb
Files:
 1ef5e57ab26693026fdf22d6f51c0e7d 1977 utils optional bpftrace_0.9.1-1.dsc
 5a89b833f28d6e7824841a9789c8c36e 704365 utils optional 
bpftrace_0.9.1.orig.tar.gz
 66f8701cf5fc9ac6b3ba1c04c23760bc 3164 utils optional 
bpftrace_0.9.1-1.debian.tar.xz
 21bc10a95bb0b9fbc4c5d3fc50fd6a74 9370196 debug optional 
bpftrace-dbgsym_0.9.1-1_amd64.deb
 b8bbf2f4182e589177611df1886f24fe 7505 utils optional 
bpftrace_0.9.1-1_amd64.buildinfo
 93e7a7d4058341cb13dfbc09a36aa27d 378688 utils optional 
bpftrace_0.9.1-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl0TEnASHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5duAQAJ2I678Bh0ajo+h4zCHRj9gEeydoHWkf
a5gdZQi+hWVr/pmmC3kHJxqIi5hCG0HT2cAOdj+K1WYILsoz9lR+GypKUGrZs1/u
kYmK/bLDUVNG2Ff6ynQ+QqgkI29Or1h7XXleLVVyfNrJL9g/helpWVw0mtXtIx0N
uZeWIsxwGhZSLx5rS2XKzA76IhGk8gsSVnC/p3uduP5xPVwgP4U0ekjUoY7a0Qf9
TIdGknupm+1/9MVDHqd2Gw1gXVuJAetyZO6BH4juSi7kQXYo2jI10mGYXASjjPKH
YPHU9AIMDSFzsdag2Xk0K/Bz438KsPrXJhKDMRmojKL5aVYx/3vNa6dGFOzDNg5P
mFFZ9FZV0GLMxwaIfNfbMPJuRhWu/kqsS1N4caq5lASITHD3w8G/GyM3QMKrmuMd
D1Byh/G5+JD6XsAB8/3TMPgQ8SQ8rXRuTazt+JpCXggXXLqM3DL0mdlf5rfw4yAS
fc+8QxTjbjiXbenRMKotUD6O7PfBGH+Twgm4YLKY4g8+C9kxd3+cpHaUrTenc5pu
9yObOmQ6J+mJQrExTmTk3hHf4A7YqG46HzkO5/y4n3Zzf5UgzlR4BqO7HMj0LELC
6Mj39tn1vsuEFje1fLzbdhjL7/u2f9eOP79EFZX1RisXslZ46xlCk56AjTncTmXN
5LH/JvBNRJBd
=gYst
-END PGP SIGNATURE-

Accepted node-dagre-layout 0.8.8-2 (source) into unstable

[Pirate Praveen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Jun 2019 11:38:22 +0530
Source: node-dagre-layout
Architecture: source
Version: 0.8.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Changes:
 node-dagre-layout (0.8.8-2) unstable; urgency=medium
 .
   * Explain why tests are disabled
   * Add explicit module field in package.json for import to work
Checksums-Sha1:
 309f60442bc8b552f6ee16bd0bad0534bd0998bf 2539 node-dagre-layout_0.8.8-2.dsc
 50a1b3667a1ba64f8264a5a3ddea7b3e4ca02544 3004 
node-dagre-layout_0.8.8-2.debian.tar.xz
 85dde3579baa6526f654a18daa942076d5f4dd54 5551 
node-dagre-layout_0.8.8-2_source.buildinfo
Checksums-Sha256:
 a0d2c506fe4480781accde0169bbb303a3ef840a584b2d27a59ab97b9e73b779 2539 
node-dagre-layout_0.8.8-2.dsc
 171a195a344b0d5d4479b9f66544300d0179380fe5ac17c37063e1c9738e5328 3004 
node-dagre-layout_0.8.8-2.debian.tar.xz
 f5ffd506dcd88c3279ef35885f91aba8c098a5b9e1291266dff1070ae3c4a495 5551 
node-dagre-layout_0.8.8-2_source.buildinfo
Files:
 730ced1f1a46f2f1a4f586aa7782a950 2539 javascript optional 
node-dagre-layout_0.8.8-2.dsc
 bc90a31cbc6be60e3deff10dac471e36 3004 javascript optional 
node-dagre-layout_0.8.8-2.debian.tar.xz
 5774a25740ab61a9332358e2090752f3 5551 javascript optional 
node-dagre-layout_0.8.8-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE/OFtr184QaN6dPMgC3aSB2Kmt4UFAl0TDjAACgkQC3aSB2Km
t4VBExAAo0mOlOQpY8Ik0ZeNeT4NJADkj6Hw5ft8qD03v7URe7/fB9uev80tjJtb
SHn7qlqphf75UUueAqCzn3qWtrHLuKTvdwaLOsUleLnZjcGSUtv2EysYwCcit2ra
8wxvOypuGDDFRp3vEwmUk+27G1nJeOwUdm/b3w9p5C7LBm0I/q39C+nsHB9KPwfF
nERmviqEQerPbp3dBpbmCg5TvgE6p522ezGiSdMbQByJlJCO2zRg4gEA9x/bQ0Np
Fq36n/JAcQkRtI+Sa4zkPev6P14f74VMySGWLzQwlCnw+gLAglp53hJ8FXcZmB2l
/CQS9GusmwvtQmcmZrDTp81ldZi+Ri42opWiPl+KtDhon9Ln6b06cBUwFRwR+znQ
uKpS81m/Qlu2Cn2fx/Tdn8J3SY9uTUrGUtRrEXHo32l9KZZgRawFNCSOxsyI42Up
h9cld8poWDi2GllS+O5Y7SQD/vXOryByxxQvenA2UxdX+a5gWTp4E2dzHMP5CmdV
u8wsGWXIEw0wLXmCe8FhtmWkKah2rFz0MweTojeGXdTnKYGpjbiVqgJMtWL7TpsQ
gQUIwSw3gh+xBsXFDiZJftuHrcJRQLQ5MC3UJtySMwHD6u8hTrFe+njxugYEiK/N
+MDTUOiMdfwCQ/S4hwP9maLTFA910wB4QKrN9dn30zCvyS4h9Y0=
=goAw
-END PGP SIGNATURE-