Accepted python-fakeredis 1.2.0-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Feb 2020 07:58:33 +0100
Source: python-fakeredis
Architecture: source
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Kobližek 
Changes:
 python-fakeredis (1.2.0-1) unstable; urgency=medium
 .
   * Bump Standards-Version to 4.5.0 (no changes)
   * New upstream release
Checksums-Sha1:
 5cfd3acdb69e002dd101b72f85e319bc906d08a0 2568 python-fakeredis_1.2.0-1.dsc
 f9192560ee6a0dba02bffea3ddca8471769fcd50 60648 
python-fakeredis_1.2.0.orig.tar.gz
 ddf3640599a69c9c677659e2c89dcd6f538c2941 56036 
python-fakeredis_1.2.0-1.debian.tar.xz
 70c750f35c917cf7adff84cbcd4d9ed3d593f0c7 7434 
python-fakeredis_1.2.0-1_amd64.buildinfo
Checksums-Sha256:
 ec0d75aa46f61aae7b0c09b86aee911be7b986116af6b4e8cdb0a95aadc7f7cf 2568 
python-fakeredis_1.2.0-1.dsc
 d849794edbd73f28ea3b2d3eeffcfdc1f6c19532e59e4f0fe7d52c2f6ed7ef80 60648 
python-fakeredis_1.2.0.orig.tar.gz
 74f8b25c12200ed8bda07f37cfc2f690044661c25bcf91c2136055e23907db3f 56036 
python-fakeredis_1.2.0-1.debian.tar.xz
 c9d50c4e432fe27dcd33e78005c55d10ecb4f1ff4e162abdba675721dddfb0d5 7434 
python-fakeredis_1.2.0-1_amd64.buildinfo
Files:
 909b10882f368b0689540a4359efb9af 2568 python optional 
python-fakeredis_1.2.0-1.dsc
 8540bb4425613dc0ae4c3e138e9bbb18 60648 python optional 
python-fakeredis_1.2.0.orig.tar.gz
 ef42ac89b4f77da7333af63717b71341 56036 python optional 
python-fakeredis_1.2.0-1.debian.tar.xz
 c62a7b03a9e5982667ac7e34b2a1de5a 7434 python optional 
python-fakeredis_1.2.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEdGzdNChg6561Y/4Q6tVdD9sFAl47vTMRHGtvYmxhQGRl
Ymlhbi5vcmcACgkQY/4Q6tVdD9t3sg/9FEdb2WMTcBB6NHBwgQp1DctfnC+dJhiL
61GmahcVSZBHm/EGJVcgF8NbTzQFcOctwrk5vjq8tf3RjrsQFkIl7ZKJrekPYAXq
KU4RmXf2KwMQVzJTob4zFJjGYiO2W9SgbjgCFqR9yhxRTo0QdnMduZ7rmwSp13K/
ZyRguaj8G4ADfIhw5LHxWwYwHLgpAzG8m5xTn0UHQ3StMwZiLYN02LiC9bdZttHP
BEO+z6RUTY4kF4iDmudwjx/egAhl01/qhfuoWHL0R+FH8zPR92A9/3OA7ksIlBr1
J9/hg4YPQGYo/mPc49jpRymeHsdobDAn9RNict/LzdCySbRuTbjPWlMg5EDMsNRM
OA9zqPNkNZiLIawTphlMkD8qawrEZOXXEdNe+OJuOyNZX7QAbkEivLkbeE5WmD5i
AvJgcBJgWXZyLNToGuCNbDqsjVq+4iHO5/chPO78u6/7r5OeVdW0P0gdHOl1gbvN
QC9M85dax8yxH+BiyKHdUOYPULYpwUo2QsqsuA9MzzOlOtgbZwoC2iKmGmLyGk/r
9ugC8fwsICqKfZOcatsoJtPvEDCzBTY0Zf1iY81+QQmhhokwnca7YjXeOrtL3fM9
11No94EkUydGcppYodkd19tcFo/jC1UDCo5Won9RVy9dXN03KgPOsBzsBczPODtp
y5dRHcAKgNs=
=OLTm
-END PGP SIGNATURE-

Bug#950775: RFP: boringtun -- userspace WireGuard implementation in Rust

[Dmitry Smirnov]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org, 
pkg-rust-maintain...@lists.alioth.debian.org

   Package name: boringtun
Version: 0.2.0
Upstream Author: Cloudflare, Inc.
License: BSD-3-Clause
URL: https://github.com/cloudflare/boringtun
Description: userspace WireGuard implementation in Rust



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

Re: Heads up: persistent journal has been enabled in systemd

[Vincent Bernat]

 ❦  6 février 2020 09:50 +11, Dmitry Smirnov :

>> and 2) continuing to use rsyslog isn't an option if the default changes.
>
> No. I just don't want default to change. IMHO rationale for this is weak but 
> everybody keeps arguing that it would not be a big deal. In time we will see 
> how that goes (what could possibly go wrong?) but why do the change in first 
> place?

To not have logs duplicated in two places.
-- 
Use statement labels that mean something.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Re: Salsa CI news

[Ondřej Surý]

From where I stand it seems to me that you actually don’t care about free 
software or DFSG or Debian and you only care about enforcing your worldview 
upon others. You need to stop, go read DFSG and come back only if you and come 
back with valid arguments how the DFSG is being violated. Or just stop and 
apologize.

Ondrej
--
Ondřej Surý 

> On 6 Feb 2020, at 01:33, Dmitry Smirnov  wrote:
> 
> On Thursday, 6 February 2020 10:22:24 AM AEDT Russ Allbery wrote:
>> I can't speak for Bernd, but I haven't seen any evidence in this thread
>> that the built binary is not DFSG-compliant.
> 
> So now you are going to nitpick on my language with all your eloquence? :(
> 
> The first problem is that packaged gitlab-runner (where all the issues are 
> addressed) is not used. I consider it to be a problem on its own.
> 
> Second, it that binary build, the way it is compiled upstream, would never be 
> accepted by ftp-masters due to lack of some sources in Debian "main".
> That's what I called problem with DFSG compliance.
> 
> On top of that there are minor things like sloppy upstream vendoring of many 
> packaged components. That is over 90 libraries that may or may not contain 
> some binary blobs, pre-generated files, or files licensed under non-DFSG 
> compliant terms. Do you really want me to dig there to find you "proof" or 
> did I say enough to demonstrate the problem?
> 
> User of upstream build (even self-compiled) can not be sure about DFSG 
> compliance due to extensive vendoring - a something that took months to 
> address in the package that was actually accepted into Debian.
> 
> -- 
> Cheers,
> Dmitry Smirnov.
> 
> ---
> 
> In theory, there is no difference between theory and practice. But, in
> practice, there is.
>-- Jan L. A. van de Snepscheut

Re: Salsa CI news

[Ondřej Surý]

And yet you *demand* in a very aggressive way that others dedicate their 
capacity on your misinterpretation of DFSG. Just stop.

Thanks,
--
Ondřej Surý 

> On 6 Feb 2020, at 00:27, Dmitry Smirnov  wrote:
> 
> I would have done so if I had enough capacity.

Accepted ocaml-sedlex 2.1-5 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Feb 2020 07:19:22 +0100
Source: ocaml-sedlex
Architecture: source
Version: 2.1-5
Distribution: unstable
Urgency: high
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Changes:
 ocaml-sedlex (2.1-5) unstable; urgency=high
 .
   * Team upload
   * Tighten the dependency to ocaml-dune
Checksums-Sha1:
 097ae41207b03d4d00406cae7a0268a5c1980ee9 1974 ocaml-sedlex_2.1-5.dsc
 4dc39c3ae3e579aa030ccdc2a50238f4cbcb4ef6 3132 ocaml-sedlex_2.1-5.debian.tar.xz
Checksums-Sha256:
 df5ea519dae33248000626c06380fa0f5b408763286988135e4840d2e819 1974 
ocaml-sedlex_2.1-5.dsc
 3661721669c5c7819a0d6f01099169a58f184f248eb8f60011b39b7efa62d070 3132 
ocaml-sedlex_2.1-5.debian.tar.xz
Files:
 e4c775bb9b1d1c18c29bb45b116cf7ee 1974 ocaml optional ocaml-sedlex_2.1-5.dsc
 66441b87fe474edab163a465828d7b44 3132 ocaml optional 
ocaml-sedlex_2.1-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAl47sBMACgkQIbju8bGJ
MIEiBAgAgV8ygkWJ4trcKAuvjLogORMTsHKaHN5fPqPgzDr1qFjY6ahb1PuGLAYT
lWqfk6uzP5XiUZzNcJb3dxWd4SXD/Ac3KuDzTnOHiH/o7b4Bb1a0YeDUbNeBkuph
T6L1CE3+yM62d0y8n7t/qWayA1LNUmWUV9wCY8NOlTlPLey1haZFOpl+6t2fpLTU
/FK811C3CaW0d9gXf8Dmxkc/pXCQDyfDn8dpYB5f0uBMvgDb1ZmpV9THEjjcsf3A
UbUylHRYRiHUtWOvPX7DzVtz5833GDdpmWMft4Ic1kDe5927MIOx2XbSvz0x93nh
KqJ1g/6t6abX1xfirQflLjvP0A0J2A==
=h9y3
-END PGP SIGNATURE-

Re: Salsa CI news

[Ondřej Surý]

I think you should stop here and now. You are misinterpreting DFSG to make a 
point. And instead of asking how you can help you just throw accusations. In 
both you recent threads. We are all in this together and your style is not 
helpful just hurtful.

Ondrej
--
Ondřej Surý 

> On 6 Feb 2020, at 00:13, Dmitry Smirnov  wrote:
> 
> On Thursday, 6 February 2020 9:53:09 AM AEDT Dmitry Smirnov wrote:
>>> On Thursday, 6 February 2020 9:25:29 AM AEDT intrigeri wrote:
>>> I'd love if you would use wording less morally/emotionally loaded than
>>> "excuse" here: for me at least, "excuse" is bound to the thought
>>> framework of guilt, accusation, and absolute right vs. absolute wrong.
>>> Framing the discussion this way can easily lead folks to react in
>>> a defensive, non-constructive way.
>>> 
>>> Maybe, instead, you meant something like "what reason is there to do
>>> X?", or "why do you think this trade-off is the current best
>>> solution?" :)
>> 
>> Valid, thanks. Though you could have lectured us both on the tone we have
>> used as I was merely responding to rather aggressive reply.
> 
> On second thought, yes I would use "excuse" anyway precisely for its moral 
> implications and accusation of wrongdoing. In another community it would not 
> be obvious that DFSG compliance is a good thing. But here in Debian where we 
> all agree that DFSG is good, and compliance concerns should be default, 
> ideally. It should not be necessary to call for DFSG compliance. It should be 
> on abuser to explain that it was not possible to build a service in a fully 
> DFSG compliant manner only from components provided by Debian. I'm not saying 
> that DFSG compliance is optional (or that it doesn't matter) yet you are 
> bothered with _my_ tone. I'm much more troubled by attitude of not caring for 
> DFSG...
> 
> -- 
> Best wishes,
> Dmitry Smirnov.
> 
> ---
> 
> Human beings, who are almost unique in having the ability to learn from the
> experience of others, are also remarkable for their apparent disinclination
> to do so.
>-- Mahatma Gandhi

Accepted poco 1.10.0-3 (source) into experimental

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Feb 2020 07:04:36 +0100
Source: poco
Architecture: source
Version: 1.10.0-3
Distribution: experimental
Urgency: medium
Maintainer: Krzysztof Burghardt 
Changed-By: Jochen Sprickerhof 
Changes:
 poco (1.10.0-3) experimental; urgency=medium
 .
   * Fix return value
Checksums-Sha1:
 7844ebd99a3d0a680f9f73a1a76e0d03af7d2456 3119 poco_1.10.0-3.dsc
 c3c36e5881a1224d05d394385d8c265dd1080b97 15432 poco_1.10.0-3.debian.tar.xz
 f522333705747c01140a679e599181585085d038 8258 poco_1.10.0-3_source.buildinfo
Checksums-Sha256:
 f6ad24c7051fc1b098e8bcc2463a56c69b70416298a87089a2ff9716b4a57659 3119 
poco_1.10.0-3.dsc
 eac9e61967e07cac1baa33d037434e9158dd1585dd6a61d58ca31db82dfca6a2 15432 
poco_1.10.0-3.debian.tar.xz
 82e0e55ef475be0d13ee2ff845a297bedded00d90404dfb8f286cce2f4d45fcc 8258 
poco_1.10.0-3_source.buildinfo
Files:
 ec2b1b34dd691de894e08301c7b03611 3119 libs optional poco_1.10.0-3.dsc
 31eae6eb72b285d8c5eaa13e03e94e00 15432 libs optional 
poco_1.10.0-3.debian.tar.xz
 06ff4f6f8133c8aad29cd28a3e1a1bde 8258 libs optional 
poco_1.10.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl47rJoACgkQW//cwljm
lDPqGA//VaszY7Qxtu/CfDdZghIapcQMgBMt3pMFVLOcj5HzuTsYoR351ot48vBe
EOuk9p/7/kXbOi7VfV+ZBDfq2poY9AfGrcoWVKSGKFe0uSfWx28i0+lVxI3N58EW
zKDlKbHlzcTi+/Gc1eFIlDFPXT5+O58cp/tl6fOuRyxjfMrWKo97qIMTU/rQ+TFP
hJ8+ZbfOgI+OBAjsyLyvjQkAgJyHArE3o1dh9y/jT8pQ6fT5QxGEicQsrlfRNl3C
BzI80Ra6NJ59ghvoJ1m/FN6Rc/ITmB4qQHH9C4fHW/aTGjRWC+UwYbRE7WzCHEt2
SrBuGCR1dy5CyA6u/AcOgJGzSZKJCW0aDnxmtLkOd23cMYWG9ki3pXRmHT+kJnsr
TJxpLwCAFz6KDb6qlNuGRBTca8/em6ZRHSBJU9TTMA0GcknOwuFwjS6GK01TYu0x
0eOM8m7ooHwNhyn7opLldLFdaGbgqMLf7cmCs3fA4U5CkhyWNayo9Tm7dcA0ix7j
4i2QRWrNLXwZBf7S7dfitY+ytbyEnzBWYqs6cUcYVTn2sPqlnyUDQVom3mZBdTTl
HZHVZ2NQUhmrOd0M6BSfvGTlpZTXRkk1/gjFCIu1wSfaR3EwdWs5qfQrCF9AB+Dl
KgSwgfzfF9St+I5NhEY1cJfspp6N8zaXDG2Tm0EJ2qVDyuNoODw=
=93Ij
-END PGP SIGNATURE-

Accepted ocaml-result 1.4-4 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Feb 2020 07:14:50 +0100
Source: ocaml-result
Architecture: source
Version: 1.4-4
Distribution: unstable
Urgency: high
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Changes:
 ocaml-result (1.4-4) unstable; urgency=high
 .
   * Tighten the dependency to ocaml-dune
Checksums-Sha1:
 4b1d4db92bb754eb94452d37bccfe123afdc7e9c 1835 ocaml-result_1.4-4.dsc
 8d320f48a0d84396e26b807e93a9f645116cf119 2500 ocaml-result_1.4-4.debian.tar.xz
Checksums-Sha256:
 2789fa4a2954da092c2f688ccebee60d9af9868eeb138c7d48ace0d744005844 1835 
ocaml-result_1.4-4.dsc
 745669771f1f1245a889433a6b7d536e867a53aa89bb71993267047f370c27e2 2500 
ocaml-result_1.4-4.debian.tar.xz
Files:
 f86118414285af18427308401760a1cf 1835 ocaml optional ocaml-result_1.4-4.dsc
 fd3acad3d47c24ed64f97c8a46ef2ded 2500 ocaml optional 
ocaml-result_1.4-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAl47r1MACgkQIbju8bGJ
MIFipgf/ZjfCP9ZQY3UUv/tP08zL89O0cKPkEEiiR+3Yid0H1+RDYYsUIdPPO4GT
HZ5q5oWudrpg832foLDqSXD/Z2PQZwDBd0N2Q4R29rmfAKTo3Ky/dW/KVHu2dGSg
vB/dNjgXApqCli/dc6qhc2ofYQ6/fUTXyYDpGl01jbIO5mCD4owb9QX9OgQGjQ5M
xoBtv6pDQ+uSBqsgDjPNB6eYBQ6M7RwAu0AkQpJpt7mDnq6eYOgiRd8CI66a1s0q
7J96DAt4io+iI2LOe+5mck3Rsrxxai7pfGA8JexRvH61eNGkX7k6yBrJjkXbSDcA
2/3eaIkCwowjMn7zJdHLyZg848QdRg==
=y2l1
-END PGP SIGNATURE-

Re: call for ftpmaster's transparency

[Mo Zhou]

Spiritually I really would like to see a transparent workflow of the FTP
team. If it were a couple years ago I may stand in the same position as
you. But now I'd kindly invite you to review the FTP team workflow (I
joined the FTP team in order to review it), review the functionalities
of dak (at least we trainees depend on it, which means what dak can do
directly decides whether the process can be made transparent), and think
of the possible ways we can make things better.

That could provide us a more constructive start. Isn't it?

Sam, IMHO DPL does not have to lead every important topics in this
community, as that would be exhausting.

On Thu, Feb 06, 2020 at 10:32:42AM +1100, Dmitry Smirnov wrote:
> IMHO it is disturbing that one of the most essential processes in Debian
> -- acceptance of new and modified packages -- operates almost in secrecy.
> 
> Unlike most Debian teams, ftp-masters communicate in private mail list.
> I understand why security team might need to operate without full public
> disclosure but I see no reason for ftp-masters to avoid transparency.
> Wouldn't it be easier to understand what to expect if everyone could see
> how team operates?
> 
> To make matters worse ftp-masters rarely leave their comments in ITP
> issues. As I've recently learned that have profound effect on processing of
> new packages.
> 
> One of my packages spent a year in the NEW queue at some point raising to
> position number 4. Apparently before release of Buster (2019-07-06) member
> of ftp-masters team left an internal (invisible to the public) comment on
> my package that was not communicated to me until 7 months later when my
> package was rejected based on that comment. The comment could have been
> addressed without delay if it was left on the corresponding ITP issue where
> it belong.
> 
> A precious time was lost but more importantly one can see that current
> process requires an extra effort to communicate with maintainers -- a
> something that would not be necessary if ftp-masters use the official
> channel that exist specifically to discuss introduction of new packages --
> ITP bug reports.
> 
> I'd like Debian project leader to engage in the matter of improving
> transparency of ftp-masters team operations and procedures.
> 
> As very minimum I recommend to change current ftp-master procedures to use
> ITP bugs instead of internal comments whenever possible, for the sake of
> transparency and to optimise communication.
> 
> I want to encourage a public discussion regarding opening of the ftp-master
> mail list to the public. Currently reasons for unjustified secrecy of ftp-
> master processes is not explained...
> 
>   https://wiki.debian.org/Teams/FTPMaster
>   https://wiki.debian.org/NewQueue
> 
> -- 
> All the best,
>  Dmitry Smirnov.
> 
> ---
> 
> Honesty is a gift we can give to others. It is also a source of power and
> an engine of simplicity. Knowing that we will attempt to tell the truth,
> whatever the circumstances, leaves us with little to prepare for. We can
> simply be ourselves.
> -- Sam Harris

Re: Heads up: persistent journal has been enabled in systemd

[Scott Kitterman]

On February 5, 2020 8:44:43 PM UTC, Dmitry Smirnov  wrote:
>On Wednesday, 5 February 2020 11:01:08 AM AEDT Scott Kitterman wrote:
>> We just had a GR where the project voted it was just fine to systemd
>all
>> the things, so this sort of thing is to be expected.
>
>Are you suggesting that voters fully understood the implications?
>Is this OK now to replace everything with systemd counterparts?
>
>I certainly voted with considerations for _init_ system.
>
>If I recall correctly, no GR option suggested to "use as much systemd 
>components as possible" or I think the outcome of GR could have been 
>different...
>
>Anyway the big disadvantage of changing default is that now random
>Debian 
>systems will have no traditional logging interface (rsyslog) and we're
>all 
>will be forced to adapt to the new interface in the absence of old one
>on 
>some systems...

I think you need to go reread the option that won.

I make no claims about what others understood or didn't, but to me this is 
exactly the kind of thing that the winning option makes likely.  That doesn't 
mean I like it, but we had a GR, now we're stuck with it.

Scott K

Re: Heads up: persistent journal has been enabled in systemd

[Scott Kitterman]

On February 5, 2020 8:43:43 AM UTC, Bastian Blank  wrote:
>Hi Scott
>
>On Wed, Feb 05, 2020 at 07:44:25AM +, Scott Kitterman wrote:
>> >> Of course the fact that I can't use all the tools available to
>> >manipulate text 
>> >> files to follow or analyze logs is problematic.  If I'm using
>> >journalctl, how 
>> >> do I replicate 'tail -f /var/log/mail.loog'?
>> >
>> >journalctl -f SYSLOG_IDENTIFIER=2
>> >
>> Do syslog facilities really have to be addressed by number rather
>than name?  That seems like a horrible interface.
>
>That's because you asked a pretty specific question and you've been
>told the exact replacement.
>
>However, you most likely don't actually want to tail this specific
>file.
>It is a solution for a more abstract problem, e.g. "I want to see logs
>from Postfix".  And this question got a different answer.

Yes, it's been demonstrated that what I'm after won't be impossible with 
journalctl, only far more difficult.  And yes, I quite frequently find myself 
tailing that specific file because it has exactly the information I need.  
Please don't explain to me what I want like you understand it better than I do.

I understand the premise that journalctl offers the promise of better 
interfaces to system logs.  I think it's a long way from that now and I don't 
think my uses of system logs are particularly niche.

Scott K

Accepted digikam 4:6.4.0+dfsg-2 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 23:11:57 -0600
Source: digikam
Architecture: source
Version: 4:6.4.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Steve M. Robbins 
Closes: 950731
Changes:
 digikam (4:6.4.0+dfsg-2) unstable; urgency=medium
 .
   [ Frédéric Bonnard ]
   * Fix FTBFS on ppc64el with opencv 4.  Closes: #950731.
Checksums-Sha1:
 25d0293a512bd8426b61424ed85b34906b893017 3122 digikam_6.4.0+dfsg-2.dsc
 6bbd2cd5a0043396a4fef36dd0efcf2883f6e5a8 37660 
digikam_6.4.0+dfsg-2.debian.tar.xz
 aa9e7e8e7fdc6d16b98baa6d28f932da0db83c7a 32750 
digikam_6.4.0+dfsg-2_source.buildinfo
Checksums-Sha256:
 3e5b4a76f3ab8ebdb4c80ac7d03278fc688ed01d971df2cd2a891ec9551118ea 3122 
digikam_6.4.0+dfsg-2.dsc
 e2dd00534a4376ff2faf3db906351017865eb73eaf84c4cdefd2f6485ababd30 37660 
digikam_6.4.0+dfsg-2.debian.tar.xz
 609b52302a02a98af20d553c51e1ef33635580e6a125793dd0f0e504cad8a07a 32750 
digikam_6.4.0+dfsg-2_source.buildinfo
Files:
 f9efa84fec4109d103ba667bb046817c 3122 graphics optional 
digikam_6.4.0+dfsg-2.dsc
 c03f512c5cacbff0f8d9ef8611da2d7d 37660 graphics optional 
digikam_6.4.0+dfsg-2.debian.tar.xz
 d38a3af4afe93b181edc9c4e8be9ff3f 32750 graphics optional 
digikam_6.4.0+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEEy89k8fa3rclNjyokyeVeL63I9LkFAl47oIcPHHNtckBkZWJp
YW4ub3JnAAoJEMnlXi+tyPS5mg0P/AuktxKnAQnrznWv0BgFbXbr/ja3gW0OxZyI
Fao6xIvu2Ihg0ljPsulYcyNTgc7HUR8iEXQpRip4t6ZBxcuhGvX9jbFBnItaaqBE
SuGrlZNuYG0gNM1fFB6MqRQT9n/1jvy+TimQPTOJdeEd8I8K06XkiDasSAuvWJAs
Yhdisc6ooF7OPhZh7CkRYAo8zml4XkIgVsT+bVjhhLNKwsVZ4BNSR0Ziukjpy+7n
oX3DZNdg9fGXDuq2bCS0k3Rwj5b0EzVZas9zq04iHV+B7CU3LTrCYFljbJrK05el
LzgV6mNByLLbXqAjgwss0CWfD7VH/C5Tn6IPVI2sxzMr6Wx8LBNb+LOLBnk8HOxl
8ytHmH6YgADt+GL4+jiMiFm+P4c1t9fgqhLaswnAv7oztQwGDB/bm/sg5OHdLabX
s/8vnn+G/K7NjJTFnjF5FhtFJGPE/UQOKE7Lm4JI5DUZOfZosfLHkh3cig3nHGiX
AF7xMIPrbtBpMp/Ix282uEEvFM+D6cIvWuLIR3aHvRN2KJad7VHXSr/mZqdarXJj
znnhHBAW7s5l4PEk/x1oQZapJzhTedTwyQyYT43pd4GqlSTLgzug9YR8wCZvUaaP
QmKoUQKYFejWtq2oLXwwyQUjtgXq5V3370BwzqwErvsg1w6Z2ZkKV5eNOlbFsQ35
tvfAHF4O
=PgdL
-END PGP SIGNATURE-

Accepted zookeeper 3.4.13-5 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 19:54:40 -0800
Source: zookeeper
Architecture: source
Version: 3.4.13-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 950755
Changes:
 zookeeper (3.4.13-5) unstable; urgency=medium
 .
   [ tony mancill ]
   * Source-only upload for testing migration (Closes: #950755)
   * Set "Rules-Requires-Root: no" in debian/control
 .
   [ Christoph Maser ]
   * Update debian/watch
Checksums-Sha1:
 b2e0d80fc08f211b03658eac1e09f0c7f38de005 3038 zookeeper_3.4.13-5.dsc
 44f61c8508415788c712f1112c0ea449935e6fea 59896 zookeeper_3.4.13-5.debian.tar.xz
 43d4469a3853c9ddf1f595e9fadc2943d6e32947 18071 
zookeeper_3.4.13-5_amd64.buildinfo
Checksums-Sha256:
 231473f8fdbde95b9fb1a9e1986c13964ea39d32b378dad5ea5f46aa07ba3f48 3038 
zookeeper_3.4.13-5.dsc
 d2b3713f6ff5ce46ecd19e8dc08714ca883478c80b2c4f6f5fb827f8b75d9c1a 59896 
zookeeper_3.4.13-5.debian.tar.xz
 3ae4b776e9c4af65a468a3bae93b615d712d7534c1c85d39924accfc0d10d7a7 18071 
zookeeper_3.4.13-5_amd64.buildinfo
Files:
 f064274703a7cd926e27f4449735f813 3038 java optional zookeeper_3.4.13-5.dsc
 58099a383c64f1df50f37eef3d7c6d7a 59896 java optional 
zookeeper_3.4.13-5.debian.tar.xz
 65849ec66dc37645cc7929f87b9ee8c8 18071 java optional 
zookeeper_3.4.13-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl47l9sUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpZWqg//VDQubEQtFrYrcf3u5r605Wyd/dVh
07w8tRaKt7plzysW7Lnqkv0x5O332SZ6H9btPZDfAdxkO0Q/mVqCvEuj/+Ms0p/v
kxhNzLzaAItTTBg2jW9Pi2OwN43SoWKneSkHP/ZAKmh7qdbr3B2jchUhWkreAipZ
nBqjIM7g/mKbYLWWcPX4Xe89/VJOa7AdnP7BIbeQqpUBEckHkAGr7gkmIQEgnfsq
osE6WSJh2/4c4JMojoxZBmLfAcfGNXDyySNxMb5rsNbjd082m7pcplUp8PoixHsz
O0PmnoEttSl+HnKaw0cwptoLyWP8XpHQjRWy2r7XLzKxDMJIKQh1+hJumXY42eOB
HsiNyeozBj06y4fAPv9CtqLYgaC+Ur4n+FG6ylgSvaA3l8Uq1a7s0hrVBT5s+OYV
EqqpIgWapyQY3x5xjzJ+tpUQ6utuHd2mY4VO01cUIN9MNJ7j3zEXsieQ3VpKB78/
gDBRlrKsRrh6rw8B6ukaNuot8CrhW+eVvl6CZzRJMiTApIj4ndhRmnYGdPtP3SEg
zjJ2w0b0Akioqo51TwCmbis8bcA5V7sbnE9lCs/TSbdu4mTvfGdEKW2uwZ6GMSHV
/YYIMMr9u4y/DWl5hA5DgK1uccYLUuHPYe62u359Dvw5JOjeNU83VZQAMDSVNJvI
5D35N2bonpzOSoA=
=RIxL
-END PGP SIGNATURE-

Re: GSoC projects about SUSI.AI

[Norbert Preining]

Hi Mo,

thanks for your interest in our projects.

> As you know, I cannot help to care about every topic about Debian + AI.

:-D You are doing already an incredible amount.

> For good wish, could you please make a list of packages involved in
> these projects, so I can inspect them and make sure that the
> ML-Policy[1] (mostly about software freedom) won't get in your way?

What do you mean "packages involved". The core ML related package is by
now not completely free (snowboy) thus we have prepared a project that
also tries to incorporate Mycroft or some other OSS hotword module
which allows for user-provided training.

>   1. does it use any kind of pre-trained machine learning model?

By now we use snowboy with a model trained using recordings we have
provided. In the future, as said, we want something that is completely
DFSG compliant, this is one of the aims.

>   2. is the pre-trained model free and DFSG-compliant?

What are the definitions of DFSG-compliant for models? I guess that is
written in [1]
> [1] ML-Policy is out of date ... well I was too busy ...

;-)

I agree, this is a complicated area and I think we can make good
progress with proper compliance with DFSG during GSOC.

Best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Accepted avogadrolibs 1.93.0-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 06 Feb 2020 11:59:39 +0800
Source: avogadrolibs
Architecture: source
Version: 1.93.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Drew Parsons 
Changes:
 avogadrolibs (1.93.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Standards-Version: 4.5.0
Checksums-Sha1:
 69569fb5a33178abd3c27367297b5e910754201b 2437 avogadrolibs_1.93.0-1.dsc
 80656cbf4ecbc85c99bd05a61f8f6985b17fef85 2735862 
avogadrolibs_1.93.0.orig.tar.gz
 61dfc4d5780ab2f64e7b83a545734980777266bc 6112 
avogadrolibs_1.93.0-1.debian.tar.xz
Checksums-Sha256:
 1616f4a1bef72cf03e922d52616ed635f91f666570a41ad22f216160596e6c1d 2437 
avogadrolibs_1.93.0-1.dsc
 01fea1f3b21c69091c60739616f86123db92f445e4c9ca53f1dec09624aceab4 2735862 
avogadrolibs_1.93.0.orig.tar.gz
 28448c140ab450c0ad5e7391f908f5b6dccacd3c215d58179af0707fdd575a07 6112 
avogadrolibs_1.93.0-1.debian.tar.xz
Files:
 a5236803932a1401bcd3b88e3870fe0b 2437 science optional 
avogadrolibs_1.93.0-1.dsc
 d27c6f1a4653577a063260969d3e72ce 2735862 science optional 
avogadrolibs_1.93.0.orig.tar.gz
 c541a9391f0793fda732c4401c8a476e 6112 science optional 
avogadrolibs_1.93.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl47lM4ACgkQVz7x5L1a
AfpFqA//ZL3GtdpY4OIhhpmnOJPMaTiS2Jy9aLHJdMk9Y6dHDTHxocVh/kkXvt/L
FiOF26L5QPJC5edyxUA/z82icP4spys2/WPLabow7oCAGY+gwporcFF3QEFdDfe8
4w5ZWfppTPtFJj4havHBt4TfLUQJ4jfkdD2heD3kY5t6QQCqbbJ/dR5UbH9xCluK
6BvykrZ71CXC6stUqePj6Awz5atJaR8bG0mNLwqCr/aHtixYXmsFYCdeMxqT3wX3
EgzCg4gaMrR3GsZdsyJYdgnKGs3OgS+TLkAyvkkpGnKqI0SxpztqPPJpWKGE1Vjh
hCbJGkm6Vnvrk3CXoleVpuZXaT288he5bPT0hKLSH+EEJ7EvYw8gvOnuPPV6Tko7
seeP222u5JwGHom2pI9gzPSFle5rk0XX+HAt/gNq+QabWZ9KfjZSJwXMob/tsuNL
mG+4/HUwRlSx7n8jxA99VZsy/+abkX9XD4UxpgRlGaSHGVujbJjMTnFz9rVhbe0e
0Rh4uZ4syaiMdw0qSEG1mY4l8vLwobTQb40Do3kIDkzmCduoUhfXqtAnFZLYmJW5
WjPGI9rAgUFZdbu6LnkmlGwhBiYAanDCPLDwmHupoa3tY+JVWmlWS3IL0jeThTlK
Yd22qyAuI440g6BVckcrY5cxqB3U2W2O9n4BRuywIKEBlRDVbDU=
=rvoC
-END PGP SIGNATURE-

Accepted csoundqt 0.9.7-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 06 Feb 2020 00:49:31 -0300
Source: csoundqt
Architecture: source
Version: 0.9.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Felipe Sateler 
Changes:
 csoundqt (0.9.7-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/changelog: Remove trailing whitespaces
   * d/control: Remove trailing whitespaces
   * Use debhelper-compat instead of debian/compat
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
   * New upstream version 0.9.7
   * Bump debhelper from old 10 to 12.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Drop unnecessary dh arguments: --parallel, --parallel
   * Drop all patches, applied upstream
   * Adjust examples, templates and docs for new version
Checksums-Sha1:
 849d977a936855908597f10dc6f5d46f37b9fc2d 2178 csoundqt_0.9.7-1.dsc
 73b66d4f51909f890287490b3473813d3237b1e0 66170886 csoundqt_0.9.7.orig.tar.gz
 332b884ba4325d53195038b0da758753ba49d29c 11636 csoundqt_0.9.7-1.debian.tar.xz
 515b69669bf67afe3748b0f3d201de18807adc69 11261 
csoundqt_0.9.7-1_source.buildinfo
Checksums-Sha256:
 8c458d97c559fe9170bf5a533440e3c3508418792ec7b4a51668a9528f34eaad 2178 
csoundqt_0.9.7-1.dsc
 c12242d4e1f745ac2c1ae23d1ef72661d68cb51baf110c17140deb1c994cfa1f 66170886 
csoundqt_0.9.7.orig.tar.gz
 5342a4b38d660e3e52f6d33cdaf20b7ecd4171be9785c5a412f6aef748fd7eb0 11636 
csoundqt_0.9.7-1.debian.tar.xz
 46b94f110212b18f7c26b436ec58d0f076f54bf5719ddfbb1e2e45a371b65641 11261 
csoundqt_0.9.7-1_source.buildinfo
Files:
 dbaaecb7e25277c321336f2ea751ba45 2178 sound optional csoundqt_0.9.7-1.dsc
 9862efee794bf4617241e650fa45b8ec 66170886 sound optional 
csoundqt_0.9.7.orig.tar.gz
 7e596d83f1303b10892543c235265729 11636 sound optional 
csoundqt_0.9.7-1.debian.tar.xz
 1defdf6b4023a183cf06f9b966f66cfc 11261 sound optional 
csoundqt_0.9.7-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEIY7gNiAzyHtsE1+ko7q64kCN1s8FAl47jOgUHGZzYXRlbGVy
QGRlYmlhbi5vcmcACgkQo7q64kCN1s83ZRAAhd3k3p5TC5L+k0DqOpHxQlSPOHdE
cLLD0lv68SJaOCARIPy6AdKfPYseJtZlAW2VKSO6sWRg4RDFSODK3VCHkBwPye3j
dR8wGwkanrRDGvS1qobuViwz/ziA1ZP2tfn0Wq7CJeDtX0oyQnpxEr4MfY/6Ftwr
mt39kwSZT3D6cHd6yI48nsUjgpueFlzshVycBR16CNODBjjef57UPjsfPpABaNoz
nmxV3L2YIOGv7Pn9c2S2x+Of+tRa7ogdBgtN4djd5N298YFKrWOb5kxOrbHd/wso
oN1nE3DPGy6q/V0I7PMWiHfHBjneccV/TkpdBaAAnrDlbPaccIoJn6hIHPns26IX
ecx7wtLXYbk9+NgFRBHfJ7EGS3AvYGAPaixB6+ZcgSsj1vzgajD9unaJpfKWP+r3
X62ExTMEtonS9PwSkqu6xpmqU4TrgmZPJ+41l3vHNQOggJBUToJJTcNELR5DIXkW
LBp6G1iah5RBFz2VgZpMusvq2KBDnzVpk+d9Q4nYOaLo4yCdcvZsgL4YhLgmHv4b
QTYz+LZHPpbOcf3a91PZNKHzmCKsJvLg57/PvZTiUeIzQHS3EG0AtKEdw1KVxOA+
gS2EWrPrE2VrD4YeT6HjH+myUOydhhF46+/ARMUjQlpf3r7VrcTH1QzxyN0QIx5B
vMQMKqF21TEbW4A=
=dWUm
-END PGP SIGNATURE-

Re: packages that are touching /srv?

[Richard Laager]

On 2/5/20 7:36 PM, Paul Wise wrote:
> AFAICT from Debian's FHS
> documentation, since /srv is laid out differently on different hosts
> packages should not rely on a particular layout. My interpretation is
> of this is that packages should never touch /srv unless directed to do
> so by the sysadmin.

That's been my interpretation too. My expectation as a sysadmin is that
/srv is available for my _exclusive_ use.

> FTP servers that default to using /srv/ftp to serve files.
> TFTP servers that default to using /srv/tftp to serve files.
> These also use those dirs as user home directories.

I actually use both /srv/ftp and /srv/tftp, but I still don't think
those are acceptable defaults.

> I wonder if any of these should be changed?

FWIW, I would say yes.

-- 
Richard



signature.asc
Description: OpenPGP digital signature

Re: Heads up: persistent journal has been enabled in systemd

[Michael Stone]

On Thu, Feb 06, 2020 at 09:50:36AM +1100, Dmitry Smirnov wrote:

On Thursday, 6 February 2020 9:04:33 AM AEDT Michael Stone wrote:

Nobody said "exclusively" except you!


It was suggested that default will change and I'm concerned about that.


And yet you said "exclusively" and generally argued in a confrontational 
manner that seems unwilling to accept a minor change because you just 
don't want to consider use cases other than your own habits.



Either option has benefits and
disadvantages, but for some reason you're arguing as though 1) only your
particular use cases matter


Nonsense. It is not "my case" but established default that remained stable
for as long as I can remember. That would be for about a decade.


Well, my memory goes back more than twice as long and I remember it 
changing before. I remember not being particularly happy with rsyslog 
when it became the default, but it didn't really matter that much so it 
didn't particularly bother me either. rsyslog was (and is) one of 
*several* alternatives, and has advantages and disadvantages compared to 
each of them.



and 2) continuing to use rsyslog isn't an option if the default changes.


No. I just don't want default to change.


Nothing is worse for the debian project than for every single suggestion 
that something change be met with opposition that boils down to 
opposition to change. Things have changed before, they will change 
again, and honestly the impact of most of those changes is very small 
(for either better or worse) and certainly they are not things that 
should be met with the level of emotional response that they are. If 
anything has changed for the worse in the project it's this sense we 
aren't allowed to change things anymore.

Accepted notary 0.6.1~ds2-5 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Feb 2020 08:53:34 +0700
Source: notary
Architecture: source
Version: 0.6.1~ds2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Arnaud Rebillout 
Closes: 944346
Changes:
 notary (0.6.1~ds2-5) unstable; urgency=medium
 .
   [ Dmitry Smirnov ]
   * New patch to fix FTBFS with golang-github-docker-distribution-dev >= 2.7.1
 (Closes: #944346).
 .
   [ Arnaud Rebillout ]
   * Vendor prometheus-client-golang
   * New upstream version 0.6.1~ds2
   * Add upstream patch to fix test for go 1.13
   * Add upstream patch to build against latest docker/distribution
   * Add vendored NOTICE file
   * Make sure keys and certificates are not executable
Checksums-Sha1:
 eba8c0a85671115960714f5cabaa4a93e55235b6 3175 notary_0.6.1~ds2-5.dsc
 88fd7defaac741869b1da40373dead090ae7a5a0 1291548 notary_0.6.1~ds2.orig.tar.xz
 9bf4f3cfabc94b38c74f4405452e3fbb6135609d 10812 notary_0.6.1~ds2-5.debian.tar.xz
 749c8c4761f51065d085096520a8529c1683bb18 17143 
notary_0.6.1~ds2-5_amd64.buildinfo
Checksums-Sha256:
 c998cc0ea0f2ce04f556419d96b88735b82780206f376dc5e55dbc22f3ee7321 3175 
notary_0.6.1~ds2-5.dsc
 d7fdf6df752aeb476cb82bff76a7915082429125b424c23f11ce0e2f54f7290f 1291548 
notary_0.6.1~ds2.orig.tar.xz
 f6e9edb58562c84c790a0cf56afb7c97c6703eb55df11dde918d8ceb5d929127 10812 
notary_0.6.1~ds2-5.debian.tar.xz
 0b9300f5760a2c291520535fdabadecb0516de4d2db208718cf0ea6be4d6947c 17143 
notary_0.6.1~ds2-5_amd64.buildinfo
Files:
 9f0ab1c9c3aad8a70a8475d04f24c2a8 3175 devel optional notary_0.6.1~ds2-5.dsc
 a5e5c7ccb7e35838dabc813ce4184a7a 1291548 devel optional 
notary_0.6.1~ds2.orig.tar.xz
 26a958ec59e81be93e6395d60f2ca39c 10812 devel optional 
notary_0.6.1~ds2-5.debian.tar.xz
 dc4a439d6fd65bbd1d2b2f4a6b2cdce1 17143 devel optional 
notary_0.6.1~ds2-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJTBAEBCgA9FiEE0Kl7ndbut+9n4bYs5yXoeRRgAhYFAl47c9MfHGFybmF1ZC5y
ZWJpbGxvdXRAY29sbGFib3JhLmNvbQAKCRDnJeh5FGACFl5ED/9fmEbwxjrx2dM3
c8z9s/9MIsBfFEQEwPFI3UGM2icKCEYmZWzB91H+yVopSS5oo3Ey2GqjSc/czEgG
q2F9tN+hh1G0/6w1nUSi1xCL77fh594ehStiEdyIL3n88imPzskP2q5GnmZUJDma
NMPmlibVBRINk7qBcfIRpAeoLnKvV8NuRKOBy7nk0bEFF7pi4Y/AbnJKfw34DJNh
mIq/D72X8U1cKwZ6zwgmI6tY773Setw3Gu4X4bqcLxWNdd+Ryr+YVaZjfnRyP5a/
eV3hNrnyUVaFQXWnnVz7zPyVnuFfREcIbwYmSOYyqXbmLyeqvc7DIrUmbQXC+UGY
phP09MlRPK4AVtuoYkMX0slx2Cs/0pWQviH8uodjmmkRLOw/8P9/YIqTvVdqrgBN
Iuu4GZD96c4xRCDjfXLiUVvSX4cui5qgd4FYWFMpCXXP2ZXj40MCuRRcyTrNzAGr
Z3GI1jlQTcpc/iORCj6iZLN43VrEblDtUL+nwWjBXQkclex7Bx/srQUdY6Btkh81
JdKFy0peeLfpYDkXv/r/0/P1KCpNGt6ZlHEhAkA6G5mUnPUM2dbgtZleAQOO4hWr
hlmhUtn9eA1ycagASR0HfDX5ED0MPr5JTD7U+rGCJWWFYiMFRQZLbxTKPEXleXmP
/ujP0aPzRztcQR/GIUnbpQTIgPeeYA==
=jBm3
-END PGP SIGNATURE-

Accepted pulseaudio 13.0-5 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 23:06:41 -0300
Source: pulseaudio
Architecture: source
Version: 13.0-5
Distribution: unstable
Urgency: medium
Maintainer: Pulseaudio maintenance team 

Changed-By: Felipe Sateler 
Closes: 950413
Changes:
 pulseaudio (13.0-5) unstable; urgency=medium
 .
   * Fix removal of 00-disable-autospawn.conf.
 The autoremoval script was wrongly put into the pulseaudio package, while
 it should have been in the libpulse0 package. Moreover, the version 
specified
 was wrong (set at 12.2 instead of 13.0) (Closes: #950413)
Checksums-Sha1:
 f1e27166b4f83e4b1e8a73cef3ba3fd68e998591 3695 pulseaudio_13.0-5.dsc
 79a404e43537b4c3e992b13be26b22fb37b6 35336 pulseaudio_13.0-5.debian.tar.xz
Checksums-Sha256:
 0942b9f44a3647e088cb92dc216b86a7140dcdea5cd9d6bc18e9f3b29f9489ed 3695 
pulseaudio_13.0-5.dsc
 685f5b19076ee27ecf1018671712931827b5112452229437d02e58803a313174 35336 
pulseaudio_13.0-5.debian.tar.xz
Files:
 ee1d0ce28ba33d69d30cfbd4ab0ca280 3695 sound optional pulseaudio_13.0-5.dsc
 522fd27080f48f9a0aa9d69ec3baccbd 35336 sound optional 
pulseaudio_13.0-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEIY7gNiAzyHtsE1+ko7q64kCN1s8FAl47dPcUHGZzYXRlbGVy
QGRlYmlhbi5vcmcACgkQo7q64kCN1s+NBQ/+KO3J28/E77kwfPBUys8FHmhTrrTh
fJReZr80TDAGfj+n/9gjt0oMy34a3v/RJaSWxvMPqMRdRAG7kX69JKkoak2yEfAR
ArqdWkjoDi2YLVkXKTwUqGk0Rj3xyHnEWrQM7U4XH/dCWp5sCzxCFT9in4SE8nb1
h53GpcpM3Oszm2miZdyvTT2V210C+Sv/XSHTdggrrc+1SGC7L84K2jyuy3gyVyEB
WpveJ/CgKIF+oAplVctt7cxhaslUanM+qyMIR1ckbP4vJKmpnyiJ02QR3ln34yvu
Y4yZSYN9ZcVwzNuSc3NqRS4L4fSm4oDyJUsutT/qtsfyGUXJOAh2ZLGvf7yxmuFD
x+jX0/+9jA2OsNj/ntVHwFiZxnfV8T0Ki7eU24bHmSQabz2dunOHbWad4Pn2PmQM
zVAhCjEzCxqO65kh2opfpS2jRYFa50rXRs2kGbP+pD8tuv4ot+uSmkaop5GA0fR/
DJiK4K/A9bKpONPw1w3knJEjVcdzNsZkj2C39htwDIXW7al1ksslHIrZ6N6Mgzs4
oQRAdmc0TFPcq+SwbdklPS+LvbabZrylNucQ6Uz7st+BkH8i1gNI5gbLp+eE2qqD
SFeJJ9uW8F8pz1nIRBFm+UWGjlPCogZq/XMP9QsWhveECnjFOpQoD1p3WCp1uzDv
TtQzWjebcGoAcOw=
=7hY8
-END PGP SIGNATURE-

Re: Producing verifiable initramfs images

[Sam Hartman]

This is not a disagreement with anything you write.

I've noticed that there is a lot more configuration that gets encoded in
the initramfs than I thought.
The most surprising for me is that if you want to control the names of
network devices or anything else set by the .link file,
that ends up needing to go on the initramfs, because udevd will set up
network devices even if they are not needed to find the root.
Unfortunately, that means that initramfs udev configuration (including
/etc/systemd/network/*.link) tends to need to be on the initramfs.

I realize you only gave crypttab as an example, but the set of initramfs
configuration is larger than I at least expected.

--Sam

Accepted reprotest 0.7.13 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Feb 2020 01:57:30 +0100
Source: reprotest
Architecture: source
Version: 0.7.13
Distribution: unstable
Urgency: medium
Maintainer: Reproducible builds folks 

Changed-By: Holger Levsen 
Changes:
 reprotest (0.7.13) unstable; urgency=medium
 .
   [ Holger Levsen ]
   * setup.py:
 - update classifier to express we are using python3.7 now.
 - bump version number for this release.
   * Bump standards version to 4.5.0, no changes needed.
 .
   [ Iñaki Malerba ]
   * Version test: split on + character.
Checksums-Sha1:
 da64f6c2f9a2059b80f6623eee44fde787611651 2099 reprotest_0.7.13.dsc
 39f741dc75ec9c41b63fb459bc5c31cf78b554b0 85516 reprotest_0.7.13.tar.xz
 a0af35ac72a976981acb424d41bba0022dfd28a6 10170 
reprotest_0.7.13_source.buildinfo
Checksums-Sha256:
 e054a2611813b2965a93d24051d7d54b06828552ff1f256eca8543251481aed5 2099 
reprotest_0.7.13.dsc
 955526467fb947f28a3834b41f21fa41c2287e8cd48f75abd2f8ba464738d75b 85516 
reprotest_0.7.13.tar.xz
 91acd2cb3c0c5c8273d13b810d1b4251e9e8263583ddaa355cd52c9c5cc5c38d 10170 
reprotest_0.7.13_source.buildinfo
Files:
 d796753c3315ddadff0f1510e589d1a2 2099 devel optional reprotest_0.7.13.dsc
 43da84b419c4cc396b9ea4e9240c3ed0 85516 devel optional reprotest_0.7.13.tar.xz
 4bdca219701d786ec04f0926cf85dac9 10170 devel optional 
reprotest_0.7.13_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAl47aAYACgkQCRq4Vgaa
qhyuQg/8DkaO9LkixePv612jioATICrBAcDSywBNPH4oo4jgV9JNIpbBBzI6mWzE
eL4pFB4AsOcu1gjw41iYCJy1AkgXNGEl/pyRFJnaglfYl2SPsHjGF/3h0vafPFTW
WY2tFVscS3lAn+qy7lLgtnxqUOSkQnZ/edQhS4ZaliD28Jcb9E3mfAM/RoaLPqOv
Acaa9CaE3MDAtYcQ/OSqUJGxis5OhjjsXdnCSY4qIBDSHEJ4wDKVR9BkPOwOi1rf
fkhXhLg0i/H7OvNe1oLlsCKHOo8NjxcJY8MJi40awAwqvaZzGKy6G93QocbV7uSL
pwAGq06d0VgyhHljyKhAXPfNDQfn9VWOHnk2QhMWBA1MpP+xAhpKbzpWwSf/CHBm
QyKBCP3t/w2XEWh25sgrH+h3oUppYJAsqnFoYIFqPiBSuhiNAqaCu2B9QLc+luPi
sjeufVSjHfzP9DmMPl9WuZGD+LpyS1hlfzMfHMWrbD43jiSFjQOVf+IxRPkQYgOp
Cy6j6LE8wf8YmfItZ/hiGyf2dKZjNPS6oQRx1mBeb7PhlFMjatk/bzZOguLQWKi9
zHFZQO9hOfxAD3lhXduDYvRcUe7ovi9/DVKwsQ+j+dqJmmdHc+uMRM+NarXXQhv+
AcFlrmfDpITAyqPwi4lX1Zuydzypg7xZcOOHNU3IygTSlVGvMRw=
=3q2l
-END PGP SIGNATURE-

packages that are touching /srv?

[Paul Wise]

Hi all,

In [1] there are several packages that reference /srv in their
maintainer scripts or debconf prompts. AFAICT from Debian's FHS
documentation, since /srv is laid out differently on different hosts
packages should not rely on a particular layout. My interpretation is
of this is that packages should never touch /srv unless directed to do
so by the sysadmin.

The packages seem to come in these categories:

Only referencing /srv in debconf messages.

FTP servers that default to using /srv/ftp to serve files.
TFTP servers that default to using /srv/tftp to serve files.
These also use those dirs as user home directories.

OBS uses /srv/obs for various things.

I wonder if any of these should be changed?

1. https://binarycontrol.debian.net/?q=%2Fsrv=
2. 
https://www.debian.org/doc/packaging-manuals/fhs/fhs-3.0.html#srvDataForServicesProvidedBySystem

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Re: Salsa CI news

[Russ Allbery]

Dmitry Smirnov  writes:
> On Thursday, 6 February 2020 10:22:24 AM AEDT Russ Allbery wrote:

>> I can't speak for Bernd, but I haven't seen any evidence in this thread
>> that the built binary is not DFSG-compliant.

> So now you are going to nitpick on my language with all your eloquence? :(

Accusing fellow project members of intentionally violating the DFSG is
serious.  If that isn't what you meant to do, and instead you only
intended to complain that the deployment wasn't to the quality
expectations of the archive, wasn't using packaged software, and that it
was inobvious how to find appropriate source, I think you chose your words
poorly in a way that goes substantially beyond nitpicking.

You also doubled down on accusing your fellow project members of
intentional wrong-doing:

On second thought, yes I would use "excuse" anyway precisely for its
moral implications and accusation of wrongdoing. In another community
it would not be obvious that DFSG compliance is a good thing. But here
in Debian where we all agree that DFSG is good, and compliance
concerns should be default, ideally. It should not be necessary to
call for DFSG compliance. It should be on abuser to explain that it
was not possible to build a service in a fully DFSG compliant manner
only from components provided by Debian.

This is a serious accusation of violation of the project principles to
which we've all agreed.  If that wasn't what you intended to do, I think
you should consider toning your language way down.

> Second, it that binary build, the way it is compiled upstream, would
> never be accepted by ftp-masters due to lack of some sources in Debian
> "main".  That's what I called problem with DFSG compliance.

Missing sources in main when those sources are reasonably believed to
covered under a DFSG-compatible license, just not uploaded to main, is not
what DFSG compliance normally means.  It is indeed a release-critical flaw
in packages uploaded to Debian main, but it's not the same thing as
running Debian services on non-free software, which is how I believe a
reasonable person would have interpreted your original message.

That said, thank you for clarifying, and I *do* appreciate you pointing
out lack of obviously available source for Debian project infrastructure,
since I think that's something we should be aware of and ideally fix.  I'm
just objecting to the moral accusation that you coupled with that bug
report.

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

Re: [please not now!] call for ftpmaster's transparency

[Sam Hartman]

Please! Not now!

I absolutely think that accountability and transparency for a couple of
delegated teams --and really for delegations in general--needs to be one
of the big issues for the next DPL.  I think that's true whether it is
me or someone else.

Our delegates put a lot of time and energy into the project.  We need to
find ways that the project can understand what is going on and give
feedback.  When the project needs things different than the delegates
are able to provide, we need a way to move forward--possibly changing
the delegation, possibly understanding why we won't be able to meet a
project need.  We need to do that all while respecting people, not micro
managing them, and while making taking on adelegated responsibility
something people want to do.


Right now, though, many of the people who could facilitate that
discussion are under incredible stress and are spending all the Debian
time they have and then some.

I know I don't have time to help with this.
I know at least one ftpmaster is fairly concerned about unrelated
issues.  Two others are quite busy with some of the stuff that is eating
my time.
The community team is busy.  While they wouldn't have a formal role, it
would be great to get people involved who could help us work together.

We're still recovering from the systemd vote.
And we haven't yet begun to make progress on the healing from conflict
issues I I brought up in the last two bits mails.

I appreciate the frustration; there was a fairly long project thread on
this too.
Deciding this needs to happen right now...well, it's going to be very
hard on people who are probably already under a lot of stress.

--Sam

Accepted debian-edu 2.11.10 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Feb 2020 01:42:54 +0100
Source: debian-edu
Architecture: source
Version: 2.11.10
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers 
Changed-By: Holger Levsen 
Changes:
 debian-edu (2.11.10) unstable; urgency=medium
 .
   [ Wolfgang Schweer ]
   * task-lxqt-desktop: Drop unused sddm-theme-elarun from Recommends.
   * debian/control: Update after running 'make dist'.
Checksums-Sha1:
 667bc9ca18fb7065acf474dc88edbf166e90c286 4762 debian-edu_2.11.10.dsc
 78a02422e1b907a9914b8f51418be66231475e02 119292 debian-edu_2.11.10.tar.xz
 9ce5792c0b0e09784a227269efa6f3381b4f7bd0 6943 
debian-edu_2.11.10_source.buildinfo
Checksums-Sha256:
 4c9982502819a2b98549b0391ce31774a56eba526535d451f35b2a1ea53d0c4a 4762 
debian-edu_2.11.10.dsc
 4f03851b4ff9fa40844d444a6cfd9b618cc5876026ef6b3cc7d988756f0fdd65 119292 
debian-edu_2.11.10.tar.xz
 b728079afaad227492b973a8b31f0023c0f307da63b19b80834d6caf2c64557e 6943 
debian-edu_2.11.10_source.buildinfo
Files:
 dfa1c8a32fe265ae13b16034a140b6b3 4762 metapackages optional 
debian-edu_2.11.10.dsc
 942fbe011c3075ade3a0a9eefca610ed 119292 metapackages optional 
debian-edu_2.11.10.tar.xz
 93f17df2cbea00a7962b19d6b83b6cec 6943 metapackages optional 
debian-edu_2.11.10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAl47YZUACgkQCRq4Vgaa
qhwjQw//X5pYqTOHnXPLFeayOiyyScM98k4gnKsk5dakDPGPTFbKRjOQ/aW0pSo8
Oq4KjHyPfLgqkABOsAePb4GM7h6bGiAGP69grECb2oxWjg2UJ1ITeF/Xgxz45dpr
62a3IheknA9W3MPiNYhthsBmDb/roUafI2s2LjvqnbuFdTbgVTkzp+EEmzBTWIfi
XBxRXvuJriUGbCWL4eZhtOC0wSqejN6gUzwZyt4WSMwAcGfUB8AmMdKPFU6FwzXE
C1yipxbOcaTsMgRwN3iTS3yrPfI1kZyAZpPQNTdHDuBhO9FCuyDI8DfB3Ggt/SMt
lLjf4BTCo2d6HqwkMEiZpkXY/BpO15cimQ4JWxsAI54pO4RAKbBSxPb8oJPmLmop
XDu1Ewx9rNzkKZo7E7/urxXLbLQtqyxgrs9NNkuZl4IWLoqnLHZ/AW5VmQxjiyer
v87BfK0Na1/RaFIL88LZ4ISbOufZeu1fGQ7pHIjMNDuzgb+FKNJhJcfmQdnFgYkF
iyYD4wLLHkz1B+WTcQD3BwMS0oPUtLxsDJLBoolyhAbj4+LyvG9KRz08GPJ32VMh
CA0MP/gC/TUnplWhv8jySHq/8EEIfBcmZZcwOTHx7an5121PecDJREIFdmkclESa
meK1nMPsTYvxxMmWm/Sf95CqRub/lzqeqHaeDRrszs9Z0EqDu1k=
=Esnc
-END PGP SIGNATURE-

Accepted gimplensfun 0.2.4-1.1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 23:52:20 +
Source: gimplensfun
Architecture: source
Version: 0.2.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Evgeni Golov 
Changed-By: Peter Michael Green 
Closes: 950172
Changes:
 gimplensfun (0.2.4-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add upstream patch to add a missing #include and hence
 fix build with new exiv2 (Closes: 950172).
Checksums-Sha1:
 a2ad5912f53dd1492be00883032abf8cfa3a983d 1974 gimplensfun_0.2.4-1.1.dsc
 8765ca1548754c9346db8f1141583a0c882bada9 2780 
gimplensfun_0.2.4-1.1.debian.tar.xz
 eb5db18eaa275de1a5d0a5980e867451890201c8 13190 
gimplensfun_0.2.4-1.1_source.buildinfo
Checksums-Sha256:
 a435742258050803f95acf82ae5ab48c6eca7d2b4c8e25daa5232c771508b081 1974 
gimplensfun_0.2.4-1.1.dsc
 c0c1aa6c8c19e3cc319ec9380243c2d6408e57a97966cd980540027f53b9 2780 
gimplensfun_0.2.4-1.1.debian.tar.xz
 4d0f10d12717153f35559655d72de8f32cf002a8a709c7d8d39080042bf086c2 13190 
gimplensfun_0.2.4-1.1_source.buildinfo
Files:
 2d4948d763769991399d6a158c0ce984 1974 graphics optional 
gimplensfun_0.2.4-1.1.dsc
 2b329e3e761e4350da4612c58445905e 2780 graphics optional 
gimplensfun_0.2.4-1.1.debian.tar.xz
 98f1d354a3a339435181091f27bff83a 13190 graphics optional 
gimplensfun_0.2.4-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAl47VoQUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsZkA//fFg+GSE29MGWpsr0ID95uqrw1VUj
5pLFXyxsFhGvyzyzONv93Y43p7fY9Vgto2pASqQxY1dsDXRpju1peddqGyflI6L2
AjXuHFzlQWhGIFDDQkHSkoYSYz7ewe59lQDq8HYRX5iMt0ytq69sjbbOhizCBeTo
2tN2bvHi1mmFjw3LujmHUhmWqR1kzoUQzi8IZdprFD5g9AJh321YisLZtkSatT0i
FTlcduBMKX6p4eAtmSLH2/57XvBYhO3rAqfEI8e34zOqmYRZUO41qNVybIyOkU2q
CtBF71sWzz7rKYvs99ETc9/Kcqjh5iOEHyta4YD/22rrT52CWwMUKPk47NWjuZ8o
z+0vd/9b+SMA0twHgS/Egs+XJcO4GN8RvxqIyz5vTYPgUA1wtqTrcBQmL4kfko1e
7eahS2Cboals8jYEny0SoOzqcdJODCMwx+BIMabKsDBuJCCSdggne0gxiaKfQ1Jr
7en+ju8aME8wGRtTYsb2F4Pyf8Vt8DoZBJAn1h61GX5HQJh0bYIJK5TJ8HiC7Uhb
zBqaiUvP4N2JL8ycasIZoY5AFsvVYTBD1t95MHHmr9hWzOcTf1sW2HnE7zdYjfEU
JwyKU5sLLccX2BNRM/YC1CMWDEPQgbTeo/+JxkiZIJO3t7McHIknL+S0Fudjdg3o
bZYoJr8QUye5YD0=
=4NHJ
-END PGP SIGNATURE-

Re: Salsa CI news

[Steffen Möller]

Hello,

I think your dispute goes down to the question if Debian's community
infrastructure should preferably using software packaged for Debian
(which salsa is doing) with the binaries Debian offers (which salsa is
not doing). I find this interesting. The two positions are

A) No idea why this should be of concern.

B) Using our own packages ensures that there is no diversion between
what Debian ships and what Debian uses, so it can be bootstrapped on an
island (which is the link to the DFSG) as a whole, not only the software
it distributes.

There is certainly more, like if B) was the case then the salsa
maintainers would find problems with the packages/updates of the same
and the Debian packages would be more likely be use by others when a big
installation like salsa uses them. And that would strengthen Debian as a
whole. However, this extra work /uncertainties may be something that
overloaded maintainers want to avoid.

I personally see the beauty of B. But if I cannot access the repository
because of some downtime -no good. So I am also a fan of A - it works.
The way to go may be to somehow convince the salsa maintainers that they
will save some work when they adopt the Debian packages. And that
whatever update they are doing is of no risk. No exact idea how to get
there. But the notion of interchangeable Docker images sounds very
reasonable ... and we work on exchanging them for singularity
(syslabs.io) images later.

Steffen

Re: Salsa CI news

[Dmitry Smirnov]

On Thursday, 6 February 2020 10:22:24 AM AEDT Russ Allbery wrote:
> I can't speak for Bernd, but I haven't seen any evidence in this thread
> that the built binary is not DFSG-compliant.

So now you are going to nitpick on my language with all your eloquence? :(

The first problem is that packaged gitlab-runner (where all the issues are 
addressed) is not used. I consider it to be a problem on its own.

Second, it that binary build, the way it is compiled upstream, would never be 
accepted by ftp-masters due to lack of some sources in Debian "main".
That's what I called problem with DFSG compliance.

On top of that there are minor things like sloppy upstream vendoring of many 
packaged components. That is over 90 libraries that may or may not contain 
some binary blobs, pre-generated files, or files licensed under non-DFSG 
compliant terms. Do you really want me to dig there to find you "proof" or 
did I say enough to demonstrate the problem?

User of upstream build (even self-compiled) can not be sure about DFSG 
compliance due to extensive vendoring - a something that took months to 
address in the package that was actually accepted into Debian.

-- 
Cheers,
 Dmitry Smirnov.

---

In theory, there is no difference between theory and practice. But, in
practice, there is.
-- Jan L. A. van de Snepscheut


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

Accepted toil 3.23.1-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 06 Feb 2020 00:15:16 +0100
Source: toil
Architecture: source
Version: 3.23.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Steffen Moeller 
Changes:
 toil (3.23.1-1) unstable; urgency=medium
 .
   * New upstream version
   * Standards-Version: 4.5.0 (routine-update)
   * Removed patch 'debian/patches/fix_tests' which was applied upstream
Checksums-Sha1:
 68cbceadde702ad7ad7ee530a238fcb7e24de3a2 2151 toil_3.23.1-1.dsc
 761afd26a3bced50aa98896d7fe20ffb533b5dcd 7046442 toil_3.23.1.orig.tar.gz
 efb869654a1cfb3c8f9770d2778555b4e047891e 10884 toil_3.23.1-1.debian.tar.xz
 973ba1fa997546d278812ad51554f3d774edd63b 9016 toil_3.23.1-1_source.buildinfo
Checksums-Sha256:
 e6127bdf0fcc60b8da4b81b6a5620f45b73679fbf2b6b48427212f56dbc3fb30 2151 
toil_3.23.1-1.dsc
 0e0cbceec03a910a4839b8f135e7e3c25e5e014d0d42442a251d792328c5a7c1 7046442 
toil_3.23.1.orig.tar.gz
 5abb73b340bd3c5d9292259e9d923a162e5b5ef2bf33c3e358bfda09ca60538e 10884 
toil_3.23.1-1.debian.tar.xz
 aa92d17315a7ea3a0d32b1aba8377a265398bf25cd25f92215e7cfe8db5a9f1c 9016 
toil_3.23.1-1_source.buildinfo
Files:
 a1659acbe67ff79abb1227252aaaf0cf 2151 net optional toil_3.23.1-1.dsc
 3916d5bafa9f47dad47a82bdfe9fa7f7 7046442 net optional toil_3.23.1.orig.tar.gz
 d7961b2ecc53db5b101821c7020c15c6 10884 net optional toil_3.23.1-1.debian.tar.xz
 10a4046ddc1ad4a6d298ae8258c04eaf 9016 net optional 
toil_3.23.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEhMGXeonn7+0+XKYuL9i+2sAg7tEFAl47T0wTHG1vZWxsZXJA
ZGViaWFuLm9yZwAKCRAv2L7awCDu0WXdD/0Rb81t0NStlgLrSwW+TJVxJ7g9mZHr
qVfE5kmlAh+WR5FmmCeajXcpq+1bhFG/cz5g0PdcC1KejMFIHuVtFj8NkHRuSk+a
L6cUY1quY6m//FzzVEQYYY9wy62BLNxLVG7d2Mmst9nsUGgCt0L7lZ1ofl2uTntt
Nly+n9GhWgEdmV4F+hvFBqKZ7FckWvisoLghpxnBl6bEWBBi3FsTECA8HoZfXMS7
caA9DutcmUSzcKJg7vlKAshgRCvUY5Xq9qtuEgOfU3dwI1nwEPhlYCmHocB0hLmE
PAzvHGJMxtoJMzlY4oW3hUFq+du5xSVxMXi9VcaNvjC8D6v54TUl7gR3sChNFybh
hreGwf4K+tdhimUJPd2vZPQSxkj6oQ0IINDZDfzwheGuyzwBhnjikauwp64SsDVm
HY8Iu4Xykjtc4G3zeUeBRtrwhsV0bEsEOghHEGeHpxMXCWH6+GiufRV6b+hCPqw4
qCBfD0IyVgHA6rKxKZ3HOuRM2zaeG2qSqtMrdz5vuthIvqDp5wOiZt1WkQ3P9xMf
y8QdmqFFv3W4lx+Qs2m7olHO1sLjYwrwj79mpe7bAuD4xAP3W5XiHLNwso/WC4Fi
R2v2/Sp/cLrWv0UqXjMAGr0FVg85gPsD1fvNwq/uePNnkYEIJn04P3B0Ef1hOKx0
d7mG3zDxMA/iOw==
=Mqfj
-END PGP SIGNATURE-

call for ftpmaster's transparency

[Dmitry Smirnov]

IMHO it is disturbing that one of the most essential processes in Debian
-- acceptance of new and modified packages -- operates almost in secrecy.

Unlike most Debian teams, ftp-masters communicate in private mail list.
I understand why security team might need to operate without full public
disclosure but I see no reason for ftp-masters to avoid transparency.
Wouldn't it be easier to understand what to expect if everyone could see
how team operates?

To make matters worse ftp-masters rarely leave their comments in ITP
issues. As I've recently learned that have profound effect on processing of
new packages.

One of my packages spent a year in the NEW queue at some point raising to
position number 4. Apparently before release of Buster (2019-07-06) member
of ftp-masters team left an internal (invisible to the public) comment on
my package that was not communicated to me until 7 months later when my
package was rejected based on that comment. The comment could have been
addressed without delay if it was left on the corresponding ITP issue where
it belong.

A precious time was lost but more importantly one can see that current
process requires an extra effort to communicate with maintainers -- a
something that would not be necessary if ftp-masters use the official
channel that exist specifically to discuss introduction of new packages --
ITP bug reports.

I'd like Debian project leader to engage in the matter of improving
transparency of ftp-masters team operations and procedures.

As very minimum I recommend to change current ftp-master procedures to use
ITP bugs instead of internal comments whenever possible, for the sake of
transparency and to optimise communication.

I want to encourage a public discussion regarding opening of the ftp-master
mail list to the public. Currently reasons for unjustified secrecy of ftp-
master processes is not explained...

  https://wiki.debian.org/Teams/FTPMaster
  https://wiki.debian.org/NewQueue

-- 
All the best,
 Dmitry Smirnov.

---

Honesty is a gift we can give to others. It is also a source of power and
an engine of simplicity. Knowing that we will attempt to tell the truth,
whatever the circumstances, leaves us with little to prepare for. We can
simply be ourselves.
-- Sam Harris


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

Re: Salsa CI news

[Inaki Malerba]

El 5/2/20 a las 21:25, Dmitry Smirnov escribió:
> On Tuesday, 26 February 2019 1:19:35 AM AEDT Inaki Malerba wrote:
>> [0] https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md
> 
> Thank you for providing this useful service.
> 
> My big concern though is that primary gitlab-runner 12.7.0 (HEAD)
> on salsa-runner.debian.net f0fdd533 is not DFSG compliant.
> 
> Frankly I don't understand why such issue is tolerated on official 
> infrastructure.
> 
> Please use properly packaged gitlab-(ci-multi-)runner package.
> 

Hi Dmitry,

Thanks for sharing your concern. We, the Salsa CI Team, have no control
over Salsa or the shared runners.

I'm sure there might be reasons why the setup is done in this way, but
we're not able to explain those.

I'd cc'ed the Salsa Admins which might miss the email otherwise.

Abrazos.

-- 
- ina



signature.asc
Description: OpenPGP digital signature

Re: Salsa CI news

[Bernd Zeimetz]

On 2/6/20 12:13 AM, Dmitry Smirnov wrote:
> On Thursday, 6 February 2020 9:52:47 AM AEDT Bernd Zeimetz wrote:
> 
>> Really don't care.
> 
> I see that... :(

See, I prefer to spend my time on doing open source software. I use
tools I can use and that are provided by others, even if the build was
done by other people on a different platform. Its still open source
software. The world would be much better if people would not discuss
about what is free or not, but just create free software. If there is
more free software, there is less need to use proprietary software. I'd
rather see that schools everywhere use linux instead fighting for a dfsg
free gitlab runner image.

>> You are free to setup and run your own runner.
> 
> Just because you did not setup yours properly?

Its not my runner, I'm just happy with what salsa provides, and I'm
using my own one gitlab instance and runners for projects like ceph
where salsa is just undersized for.

The salsa admins are overworked and busy, so I'm sure you have the
biggest chance if you provide something ready to run in k8s, replacing
the existing image should not be too hard if there is a working, tested
and maintained one. Just make sure the latest version is available asap
after a release.


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Re: Salsa CI news

[Russ Allbery]

Dmitry Smirnov  writes:

> Sources are somewhere, true. But build (binary) is not DFSG-compliant.

> I feel like you are making your point by pretending not to understand...
> Why all this denial?

I can't speak for Bernd, but I haven't seen any evidence in this thread
that the built binary is not DFSG-compliant.  You clearly believe this,
but you're not explaining why except for reasons that seem clearly
incorrect.

For example, Alpine Linux, assuming one does not enable the non-free
repository, and thus Docker containers created using it appear to be
DFSG-compliant.  They only claim OSI compliance, which is not precisely
the same thing, but there would need to be some indication that the Alpine
components used are in the very narrow set of OSI-approved but not
DFSG-compliant licenses.

Could you be (much) more specific about exactly what violations of the
DFSG you believe exist, rather than assuming everyone agrees with you and
then berating people for ignoring the DFSG?  It seems far more likely
that, rather than ignoring the DFSG, people simply don't believe you're
correct in asserting there is a problem.

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

Re: Salsa CI news

[Richard Laager]

On 2/5/20 5:05 PM, Dmitry Smirnov wrote:
> It should be on abuser

Saying "abuser" is inflammatory, especially as no abuse has been proven.
Please stop.

> to explain that it was not possible to build a
> service in a fully  DFSG compliant manner

Why is the current solution not DFSG compliant?

> only from components provided by Debian.

While I agree it would be better in Debian to use a Debian image instead
of an Alpine one and to use Debian packages, that is separate from DFSG
compliance and a much lower severity issue.

-- 
Richard



signature.asc
Description: OpenPGP digital signature

Accepted r-cran-qtl 1.45-11-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 23:56:55 +0100
Source: r-cran-qtl
Architecture: source
Version: 1.45-11-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Steffen Moeller 
Changes:
 r-cran-qtl (1.45-11-1) unstable; urgency=medium
 .
   * New upstream version
   * Standards-Version: 4.5.0 (routine-update)
   * debhelper-compat 12 (routine-update)
   * dh-update-R to update Build-Depends (routine-update)
   * autopkgtest: s/ADTTMP/AUTOPKGTEST_TMP/g (routine-update)
   * Trim trailing whitespace.
   * Set upstream metadata fields: Archive, Bug-Database, Bug-Submit,
 Repository, Repository-Browse.
   * Refer to specific version of license GPL-3+.
   * Fix day-of-week for changelog entries 0.98.57-2, 0.98.57-1, 0.97.22-
 1, 0.97.21-2, 0.97.21-1.
Checksums-Sha1:
 33600fd1d09e3cbec5f95f38c72556f413ceb811 2094 r-cran-qtl_1.45-11-1.dsc
 b6a5407128dd91e208e55207efc0b0683920e624 4380726 r-cran-qtl_1.45-11.orig.tar.gz
 8cbf9d8412fc42a8bbb613a970a5c22cef1fee0f 6796 
r-cran-qtl_1.45-11-1.debian.tar.xz
 117da1d46074c96bf0e461ce23f6033eda805217 9367 
r-cran-qtl_1.45-11-1_source.buildinfo
Checksums-Sha256:
 bd006140dcd61b9f7104b2017befc06b66c439f3d637a4fc48a3dc6fefe76da2 2094 
r-cran-qtl_1.45-11-1.dsc
 206128fa526c302fee486f5ce74ed92466a0588584ca3654fca63a018c7cd8b4 4380726 
r-cran-qtl_1.45-11.orig.tar.gz
 53995c230eff6616c0f841f564ab715539aa2f8c8e8ecb56022825433c620b53 6796 
r-cran-qtl_1.45-11-1.debian.tar.xz
 6323e7b39127131201166691c6119addbc83ea343fca7d1806fc614b75b581da 9367 
r-cran-qtl_1.45-11-1_source.buildinfo
Files:
 5147e75d901da78e336db54d4a44a7ad 2094 gnu-r optional r-cran-qtl_1.45-11-1.dsc
 55172fa7aa7b10e424e07342890d2228 4380726 gnu-r optional 
r-cran-qtl_1.45-11.orig.tar.gz
 9d2a1f258ba7bb5147c739e0f9ffd14d 6796 gnu-r optional 
r-cran-qtl_1.45-11-1.debian.tar.xz
 1fedaf3306cdcba0bc3a4577d4d309bb 9367 gnu-r optional 
r-cran-qtl_1.45-11-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEhMGXeonn7+0+XKYuL9i+2sAg7tEFAl47SOATHG1vZWxsZXJA
ZGViaWFuLm9yZwAKCRAv2L7awCDu0bw2D/4rnQrPjNmlujIyoWbEImw/KkIDJtox
cGvY9xsfV42ANgmHKzNlVsL+tEiboiyIk/NTMrx5HnF2ICSzOgK34lFnyGG3ituf
g/7eJ7IskskOoTkSZ6EsW3X3RqEh00JtBbYD1jAwRh3He93awPg+mlXygmT+6Tqt
1t5MD4XxSaZEuiq0HLpFBS1EiYlWe8qAZg3RBpmZl1/DlcsPd7qMES1tZPZYKYgk
tR76owZD/hWOmCJnpd/zhL3hnuMPg+y2wuFNVLa2+tnO0p7O3eXOf3CzCjXsfPC+
yr+Pzd3bUOcZ1DMdmEV0GA6fMh6FhkOJcJHZFOOuGWasOepZuMfNusAKMM0wqOTE
CGm/Qc4GDOf1w0y+MJZhIw4JtYzloPPe2PkXCLZaSC6Ee2CzWn8M/K76+EkXdQVX
RL5FylUJp8nfteqIBONYDiBt9g6+MgihKPNbNHpuGKXGctBypM3ktU6Hy9JdqOJA
b+dAD9ZkRpWs804Ts/YHGmrGd1Ytrpgs8RSTi5TUUYVl54p8p08IKo+RxI0AhQPE
jYrealJVxkN+5am3Mzpqw4mqXL1iIoaxA6U/uN9FtOp7xCpmHf8ofj5mI+CAoFyl
MAuUPOszjyqrZDiYk2ILNNbJUNUcKUfr9aaZvzvJn68J4vTLjViAp8PX28yJ0iJF
TAgsZrOHjzfmpw==
=Jhri
-END PGP SIGNATURE-

Accepted golang-1.14 1.14~rc1-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 23:54:28 +0100
Source: golang-1.14
Architecture: source
Version: 1.14~rc1-1
Distribution: unstable
Urgency: medium
Maintainer: Go Compiler Team 
Changed-By: Dr. Tobias Quathamer 
Closes: 950517
Changes:
 golang-1.14 (1.14~rc1-1) unstable; urgency=medium
 .
   * New upstream version 1.14~rc1
 - Fixes CVE-2020-7919
   * Add Breaks: dh-golang (<< 1.43~) to golang-go.
 Thanks to Pirate Praveen 
   * Update upstream's signing key
   * Add support for riscv64.
 Thanks to Aurelien Jarno  (Closes: #950517)
Checksums-Sha1:
 81477a26826544f2d82b72f48a014b59ce30d7be 2627 golang-1.14_1.14~rc1-1.dsc
 4c687eb5b2ab657fa97f0d7bd0c37a14bc777941 22331331 
golang-1.14_1.14~rc1.orig.tar.gz
 5d2d335fef4f8e33b31022eab1428217f0930a73 36076 
golang-1.14_1.14~rc1-1.debian.tar.xz
 312ca95bdebe3e15a91af316c55b58ca667575e6 6774 
golang-1.14_1.14~rc1-1_amd64.buildinfo
Checksums-Sha256:
 953ee9199b77adfdbb127dc4994b9cf288c583dcc7502e93b71dd3a6bf22c0fa 2627 
golang-1.14_1.14~rc1-1.dsc
 c520af88211d3174540fda77307bab94810d0b077a4e7871ea1d6846cb15e7da 22331331 
golang-1.14_1.14~rc1.orig.tar.gz
 3e41960e325150cff1db4551be559e1d76738ca42e90f3bf69c57b07c2e2ca82 36076 
golang-1.14_1.14~rc1-1.debian.tar.xz
 778f984b5926546493c9de8e65ec42903fc1f75efdc88e951e3b4e838af1cf37 6774 
golang-1.14_1.14~rc1-1_amd64.buildinfo
Files:
 f9a688455b6c7c0b9d56bb0b7fc4264e 2627 devel optional golang-1.14_1.14~rc1-1.dsc
 527b8485b467522c04254c7b7f1fd155 22331331 devel optional 
golang-1.14_1.14~rc1.orig.tar.gz
 ccb248f359c7c1a4f39cd3a184079ff8 36076 devel optional 
golang-1.14_1.14~rc1-1.debian.tar.xz
 75af8d915867e46889fb26ff16408e80 6774 devel optional 
golang-1.14_1.14~rc1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAl47SnQACgkQEwLx8Dbr
6xnS2g//Z0lMYEyPqHYMVT8OA9bnvOFr3mUj0s/niZDLg1jIumm0sBKrf1z2BX10
AfyN1Ab8GW5ekrGY6cMzxdoKTNuJswAFGQl7dzdx+hH7bVqL00VYlohFw6mYIgu3
V4el2gt6Xnp0INBlL4Sy/gh3WEF/yIO/Dj92fbdB41lZtxDDrCuWbw7itkyv/FI7
FxeeLIFgVQBEV5B3v+OauM6nFn96FiXStTSUoOZ5s6hBPs5+wIYeKlXEndcyixoh
rpTR0EExn6RStLoE/JpN/x0xcLRDbkJPoTY6DSeqaYMX+UbUfv9dHat8Jn9Y2zZk
0UkULf7V/PACNyT7/PMonQ8edFONBXFZYSbHrvVaPMQdDERMOHaNoxhigKlpYlo6
xuG/YYG0g9K4zwbz/VMmfBvHsmcPwa8dDffM7y11d/UUiRd9YwYEHomBpReg27Dp
eRxfzmI9KTERE4yfecaL4H/1iZr0xLfhYThWCC5qCbhPCVG/dzm/ZiVo205T09a3
OmEOUj/faipyc85hktlWIB9ytCvIEjsYUTyLtRqf3cG1PNj3KtRvgNVpsKvvVlyX
JK8qOKq7kddISmlI/TaE44X14Tz4uzi2qcLu4DOwO0IHci8iLOrhwiTwnaaxrXBW
vb0dAcQdKVxwCaBy3fTt67VLfrvwIfuByvsZ37NGOcRDqOxmk7k=
=bEvk
-END PGP SIGNATURE-

Re: Salsa CI news

[Dmitry Smirnov]

On Thursday, 6 February 2020 9:52:47 AM AEDT Bernd Zeimetz wrote:

> Really don't care.

I see that... :(


> You are free to setup and run your own runner.

Just because you did not setup yours properly?

I do maintain my own runner but it is not for everybody due to capacity 
constrains.

But let's not flip the discussion away from the problem with your runner.


> Its even possible to share them for everybody.

I would have done so if I had enough capacity.


> If you do, I'd suggest you add some appropriate tags so people can force
> their builds to run on a runner built from Debian source.

I'll consider that if/when I'll be able to scale-up the runner. Presently my 
VM struggles to build my own packages.

See, now I'm answering to you for doing nothing wrong... :(

I wish you could take the concern seriously.


> (there is not irony here, if you think that would improve Debian, just
> do it)

I'm trying to improve Debian by communicating a problem that you refuse to 
take seriously...

-- 
All the best,
 Dmitry Smirnov.

---

The more false we destroy the more room there will be for the true.
 -- Robert G. Ingersoll, 1902


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

Re: Bug#950760: RFS: libbpf/0.0.6-1 -- eBPF helper library (development files)

[Adam D. Barratt]

On Wed, 2020-02-05 at 22:42 +, Sudip Mukherjee wrote:
> On Wed, Feb 5, 2020 at 10:22 PM Christian Barcenas
>  wrote:
> > Because this changes the versioning scheme from kernel releases
> > (libbpf-dev and libbpf0 currently are at 5.4.13-1 in sid) to libbpf
> > version numbers (0.0.6-1), the epoch needs to be incremented to 1 I
> > believe.
> 
> I had this doubt but 5.4.13-1 is the linux source version, and
> libbpf0 has the version of 0.0.5. And since there is no separate
> source for libbpf so will this not be  considered as a new package
> rather than a version change?

No. There is currently a libbpf0 binary package. After the source
package split, there will still be a libbpf0 binary package. The
version of that binary package cannot go backwards.

(The source package will indeed be NEW, but that's not the issue under
discussion here.)

Regards,

Adam

Re: Salsa CI news

[Dmitry Smirnov]

On Thursday, 6 February 2020 9:53:09 AM AEDT Dmitry Smirnov wrote:
> On Thursday, 6 February 2020 9:25:29 AM AEDT intrigeri wrote:
> > I'd love if you would use wording less morally/emotionally loaded than
> > "excuse" here: for me at least, "excuse" is bound to the thought
> > framework of guilt, accusation, and absolute right vs. absolute wrong.
> > Framing the discussion this way can easily lead folks to react in
> > a defensive, non-constructive way.
> > 
> > Maybe, instead, you meant something like "what reason is there to do
> > X?", or "why do you think this trade-off is the current best
> > solution?" :)
> 
> Valid, thanks. Though you could have lectured us both on the tone we have
> used as I was merely responding to rather aggressive reply.

On second thought, yes I would use "excuse" anyway precisely for its moral 
implications and accusation of wrongdoing. In another community it would not 
be obvious that DFSG compliance is a good thing. But here in Debian where we 
all agree that DFSG is good, and compliance concerns should be default, 
ideally. It should not be necessary to call for DFSG compliance. It should be 
on abuser to explain that it was not possible to build a service in a fully 
DFSG compliant manner only from components provided by Debian. I'm not saying 
that DFSG compliance is optional (or that it doesn't matter) yet you are 
bothered with _my_ tone. I'm much more troubled by attitude of not caring for 
DFSG...

-- 
Best wishes,
 Dmitry Smirnov.

---

Human beings, who are almost unique in having the ability to learn from the
experience of others, are also remarkable for their apparent disinclination
to do so.
-- Mahatma Gandhi


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

Re: Salsa CI news

[Bernd Zeimetz]

On 2/5/20 11:52 PM, Bernd Zeimetz wrote:

> You are free to setup and run your own runner.
> Its even possible to share them for everybody.
> If you do, I'd suggest you add some appropriate tags so people can force
> their builds to run on a runner built from Debian source.
> (there is not irony here, if you think that would improve Debian, just
> do it)

If you want salsa to use a packaged gitlab runner, the first start would
be to create a docker image on salsa with it and maintain it. Then
people can use it easily.
But please note that you image will still run on proprietary hardware
and closed source software somewhere in gke (I think..).




-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Re: Heads up: persistent journal has been enabled in systemd

[Dmitry Smirnov]

On Thursday, 6 February 2020 9:04:33 AM AEDT Michael Stone wrote:
> Nobody said "exclusively" except you!

It was suggested that default will change and I'm concerned about that.


> Either option has benefits and
> disadvantages, but for some reason you're arguing as though 1) only your
> particular use cases matter

Nonsense. It is not "my case" but established default that remained stable 
for as long as I can remember. That would be for about a decade.


> and 2) continuing to use rsyslog isn't an option if the default changes.

No. I just don't want default to change. IMHO rationale for this is weak but 
everybody keeps arguing that it would not be a big deal. In time we will see 
how that goes (what could possibly go wrong?) but why do the change in first 
place?

I'm resting the case as I have nothing left to add...

-- 
Regards,
 Dmitry Smirnov.

---

A wise man proportions his belief to the evidence.
-- David Hume, "An Inquiry Concerning Human Understanding"


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

Re: Salsa CI news

[Dmitry Smirnov]

On Thursday, 6 February 2020 9:25:29 AM AEDT intrigeri wrote:
> I'd love if you would use wording less morally/emotionally loaded than
> "excuse" here: for me at least, "excuse" is bound to the thought
> framework of guilt, accusation, and absolute right vs. absolute wrong.
> Framing the discussion this way can easily lead folks to react in
> a defensive, non-constructive way.
> 
> Maybe, instead, you meant something like "what reason is there to do
> X?", or "why do you think this trade-off is the current best
> solution?" :)

Valid, thanks. Though you could have lectured us both on the tone we have 
used as I was merely responding to rather aggressive reply.

-- 
Best wishes,
 Dmitry Smirnov.

---

Truth never damages a cause that is just.
-- Mahatma Gandhi


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

Re: Salsa CI news

[Bernd Zeimetz]

On 2/5/20 11:42 PM, Dmitry Smirnov wrote:

> Sources are somewhere, true. But build (binary) is not DFSG-compliant.

Why? Because it was not built in Debian?

> Don't you think it would be _better_ to use (only) components from "main"?
> Certainly there will be more integrity if you can do that.

For something like producing build logs? Really don't care.

>> Where is the problem?
> 
> Lack of self-reliance? Using non-trusted vendor binaries (and/or container 
> image)? Using sloppy vendor build over proper one that we have in Debian? 
> Pick any.


You are free to setup and run your own runner.
Its even possible to share them for everybody.
If you do, I'd suggest you add some appropriate tags so people can force
their builds to run on a runner built from Debian source.
(there is not irony here, if you think that would improve Debian, just
do it)

-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Re: Heads up: persistent journal has been enabled in systemd

[Martin Steigerwald]

Andrey Rahmatullin - 05.02.20, 22:17:14 CET:
> On Thu, Feb 06, 2020 at 07:44:43AM +1100, Dmitry Smirnov wrote:
> > > We just had a GR where the project voted it was just fine to
> > > systemd all the things, so this sort of thing is to be expected.
> > 
> > Are you suggesting that voters fully understood the implications?
> > Is this OK now to replace everything with systemd counterparts?
> 
> Yes.
> 
> > I certainly voted with considerations for _init_ system.
> > 
> > If I recall correctly, no GR option suggested to "use as much
> > systemd
> > components as possible" or I think the outcome of GR could have been
> > different...
> 
> The winning option says "Packages may use any systemd facility at the
> package maintainer's discretion, provided that this is consistent with
> other Policy requirements and the normal expectation that packages
> shouldn't depend on experimental or unsupported (in Debian) features
> of other packages".
> You can read it at https://www.debian.org/vote/2019/vote_002#textb

Hmmm, for me this still reads different than: "Ok, let's change the 
default logging system."

Cause if I understood above wording correctly, then it means a package 
may use a Systemd feature. But this would only affect this one package. 
However here a system wide default of the system is changed.

Thanks,
-- 
Martin

Re: Bug#950760: RFS: libbpf/0.0.6-1 -- eBPF helper library (development files)

[Sudip Mukherjee]

On Wed, Feb 5, 2020 at 10:22 PM Christian Barcenas
 wrote:
>
> Because this changes the versioning scheme from kernel releases
> (libbpf-dev and libbpf0 currently are at 5.4.13-1 in sid) to libbpf
> version numbers (0.0.6-1), the epoch needs to be incremented to 1 I
> believe.

I had this doubt but 5.4.13-1 is the linux source version, and libbpf0 has the
version of 0.0.5. And since there is no separate source for libbpf so will this
not be  considered as a new package rather than a version change?


-- 
Regards
Sudip

Re: Salsa CI news

[Dmitry Smirnov]

On Thursday, 6 February 2020 9:11:07 AM AEDT Bernd Zeimetz wrote:
> They are not shipped in Debian, but they are free software,
> binaries with sources being available, as far as I can see all under a
> dfsg free license.

Sources are somewhere, true. But build (binary) is not DFSG-compliant.

I feel like you are making your point by pretending not to understand...
Why all this denial?

Saying "that's how Golang works" is enough to ignore DFSG compliance?

Don't you think it would be _better_ to use (only) components from "main"?
Certainly there will be more integrity if you can do that.


> Where is the problem?

Lack of self-reliance? Using non-trusted vendor binaries (and/or container 
image)? Using sloppy vendor build over proper one that we have in Debian? 
Pick any.

-- 
Cheers,
 Dmitry Smirnov.

---

Orthodoxy is the ability to say two and two make five when faith
requires it.
-- George Orwell, Nineteen Eighty-Four (1949).



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

Re: Bug#950760: RFS: libbpf/0.0.6-1 -- eBPF helper library (development files)

[Christian Barcenas]

Because this changes the versioning scheme from kernel releases
(libbpf-dev and libbpf0 currently are at 5.4.13-1 in sid) to libbpf
version numbers (0.0.6-1), the epoch needs to be incremented to 1 I
believe.

CC'ing debian-devel for discussion/consensus, per Debian Policy Manual 5.6.12.

Christian

On Wed, Feb 5, 2020 at 12:57 PM Sudip Mukherjee
 wrote:
>
> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for my package "libbpf"
>
>  * Package name: libbpf
>Version : 0.0.6-1
>Upstream Author : NA
>  * URL : https://github.com/libbpf/libbpf
>  * License : LGPL-2.1
>  * Vcs : https://github.com/sudipm-mukherjee/libbpf
>Section : libs
>
> It builds those binary packages:
>
>   libbpf-dev - eBPF helper library (development files)
>   libbpf0 - eBPF helper library (shared library)
>
> To access further information about this package, please visit the following 
> URL:
>
>   https://mentors.debian.net/package/libbpf
>
> Alternatively, one can download the package with dget using this command:
>
>   dget -x 
> https://mentors.debian.net/debian/pool/main/libb/libbpf/libbpf_0.0.6-1.dsc
>
> Changes since the last upload:
>
>* Package from github. (Closes: #948041)
>
> Note:
> I think this should be done after 
> https://salsa.debian.org/kernel-team/linux/merge_requests/207
> has been merged.
>
>
> --
> Regards
> Sudip
>

Accepted glibc 2.30-0experimental2 (source) into experimental

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 23:01:35 +0100
Source: glibc
Architecture: source
Version: 2.30-0experimental2
Distribution: experimental
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Changes:
 glibc (2.30-0experimental2) experimental; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch.
   * debian/patches/any/submitted-stt-gnu-ifunc-detection.patch: fix
 STT_GNU_IFUNC assembler and linker detection for toolchains defaulting to
 PIE.
   * debian/sysdeps/mips*.mk: drop -no-pie.
Checksums-Sha1:
 dff58f82f5b16718da10edb8301f6c12cc278f6e 8783 glibc_2.30-0experimental2.dsc
 414843cf6d345fd9f3a1f5867521533b3f614fb3 835128 
glibc_2.30-0experimental2.debian.tar.xz
 5279d510d59f8b62eb16f2cbe63da2d05c7e165d 7811 
glibc_2.30-0experimental2_source.buildinfo
Checksums-Sha256:
 69a26747927d76241ba8c4385caf280239e4605e9dd3dbab52589560acf844a3 8783 
glibc_2.30-0experimental2.dsc
 dfe2a86aa9896b96d7b0b7e748277ebc8836c385888729871b5a2bd92e559af6 835128 
glibc_2.30-0experimental2.debian.tar.xz
 639575316fe2d7516f4eb0210d3c6228484245ed51224dec42e6862441e0a713 7811 
glibc_2.30-0experimental2_source.buildinfo
Files:
 1d0eae49b4594bc53d77cfa6d5e11c3e 8783 libs required 
glibc_2.30-0experimental2.dsc
 ab02ced2bb4da67b19e4b82b21235b94 835128 libs required 
glibc_2.30-0experimental2.debian.tar.xz
 9e1a699ad0133f44149dab8a8833bc90 7811 libs required 
glibc_2.30-0experimental2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl47PUsACgkQE4jA+Jno
M2sYDw//Vl9bKqDEOAIHQR7K/pYmeuKYIWp3Gu8SXq2hvAiwnfLJRs7Ot7u01CYO
bVKPqQncMjoWD+c58Rm5YugaaO6PhahpW6moChcsF1ceB9OwuJGgQkmnXVUE6POF
MOtQwwfVlK7hoDYM27IR60z3ANDnczBzH5gCVITeTzsatcZAyvg9Koj22x0apbF3
HrbCXYQAj/icqd4LqF+BNe0wdluX8cbnXiQ7CF2mtRvWgTIs7uGQTmQk0Q6BsNSp
DhZ9hNOwGZySelhsPzszaDFFVf8AVEauPku2azhhW4r7ANkgA/Pb1QtjDPDU8L1c
6b3UC5k6xgB6I5aDhSf2RWt0l0hGI2CNnqNaEpOnc4jpijTf17sCtQGoLJve30NW
sb/0DqmgH6GfdLzv0up4o/hIuad2kfVP797JbVNnXnw/eujDa/bnrUcXHfaftMl5
TftdbKON+skS/FJFIaOGkOz8xe11jL7cA4r7rgzyoQdYPKuuoOLho3I3e+gncUfC
zDHyRbgjGlj+AwvpIgl5LvAcEZsz9uy6utahpV5VqRvseYfphfRt8NZ8ErBa9cdM
GysrNptUjDQtaILiMpE9PPxYbWqXHV0XFOoVzz9ztpHP7D35Yu4aGKX4yMUWXMZv
D1DB5HNTT85SzlH2C81H1TFbTHTO8iVaRNDwQbwX96TlLk237Iw=
=Y3Bv
-END PGP SIGNATURE-

Accepted fcitx5-gtk 0.0~git20191111.6f9ef64-2 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 16:54:09 -0500
Source: fcitx5-gtk
Architecture: source
Version: 0.0~git2019.6f9ef64-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Changes:
 fcitx5-gtk (0.0~git2019.6f9ef64-2) unstable; urgency=medium
 .
   * debian/control: Bump Standards-Version to 4.5.0.
   * Source-only upload to allow testing migration.
Checksums-Sha1:
 05296d8872e9e6bb863205f75cefc05e911a24b2 2605 
fcitx5-gtk_0.0~git2019.6f9ef64-2.dsc
 7cd9ca1e6ca1933e145038ee362da3953daa8d3e 2800 
fcitx5-gtk_0.0~git2019.6f9ef64-2.debian.tar.xz
 3bd75accf73034ef34a7dc2696a63b630c1eda29 17551 
fcitx5-gtk_0.0~git2019.6f9ef64-2_amd64.buildinfo
Checksums-Sha256:
 cd369087464668ddedf94635561e30526d6dea2f6f638c76c639c7d3921fd662 2605 
fcitx5-gtk_0.0~git2019.6f9ef64-2.dsc
 e52897f5a991dbc749dc810ad4abe6386d43a190eb32164059ee8cfa92afa4d7 2800 
fcitx5-gtk_0.0~git2019.6f9ef64-2.debian.tar.xz
 9bb7b4722be97f8645e6e76d36997d007b6061ee0f34ec19280a47575c77be1f 17551 
fcitx5-gtk_0.0~git2019.6f9ef64-2_amd64.buildinfo
Files:
 b3dfab9b51d141f046f00b9c4034785d 2605 utils optional 
fcitx5-gtk_0.0~git2019.6f9ef64-2.dsc
 151b7dc010cc1294d5cb9164c691c1f5 2800 utils optional 
fcitx5-gtk_0.0~git2019.6f9ef64-2.debian.tar.xz
 f95562f7c3cc05684b273a99fa582017 17551 utils optional 
fcitx5-gtk_0.0~git2019.6f9ef64-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl47P2cACgkQwpPntGGC
Ws7d0hAAoGJWPKcJ14eo+t/r25Vz/nMeAbqa84cGUeXmc3yACQwbaHrh7OLaJODw
ytFGkDDXyu1T4VRR5FgbahHdWGKQfK9aAbTigIEJfZJf4E38XUQafvLyEvry0GjT
Bje/Q4SBhOvIAIq40sH4NqG3JzFpfxaMPh3bliQn2Oso9c8Udk9YQS9W8LJkHcIR
4C6WcwNQzaAdQdFc3V44LqpM6MLzgu5MhIlDkloqpj5m27CqsIGcDC1Ss+ijf4bR
tKl9pgt26P2SwNtGeVX1tLwnbP3QPHXDB6uwjMJa99UQZRIqvJ/dI+f76mGuyfS+
tFS9x/z1bPXTS2E7awAcSlu7BKkPKJqDMh7Dgf51DrBg/jZUt7tPFqvEmlSkT11J
5T/Zx+9X5bU4k5V86401OFGOTjiNxFy9s9i4BUQDGSywnpZwEV6II3DrcftIfmj0
wX598VIsN4wYqvLiaR031VbnqIUJr9yyu5ygNLgmMFL3hTOrJqNIIg1qFax2tBN0
iBL9bBJBvaftfwykv7mjHyJ2b1dRq+6nLOK6mwpjjkvyFB2MPiupOvs7eNYCBNep
yISMiMujAV254VBCi1hnGLLif94CDAv2YBq5WnLLM0ABRjSyR+UU+gZUs9SI4zGR
rEZKxeSgHJEnlJL5maBnb1cepkCatr7O4e6HekKCh+6mlMigmwQ=
=irjQ
-END PGP SIGNATURE-

Re: Salsa CI news

[intrigeri]

Hi,

Dmitry Smirnov (2020-02-06):
> Now when we have a proper package for a while what excuse do you
> have to continue to use vendor binaries that could not be accepted
> to Debian?

I'd love if you would use wording less morally/emotionally loaded than
"excuse" here: for me at least, "excuse" is bound to the thought
framework of guilt, accusation, and absolute right vs. absolute wrong.
Framing the discussion this way can easily lead folks to react in
a defensive, non-constructive way.

Maybe, instead, you meant something like "what reason is there to do
X?", or "why do you think this trade-off is the current best
solution?" :)

Cheers!

Re: Heads up: persistent journal has been enabled in systemd

[Michael Stone]

On Thu, Feb 06, 2020 at 08:40:29AM +1100, Dmitry Smirnov wrote:

On Thursday, 6 February 2020 6:59:38 AM AEDT Nikolaus Rath wrote:

I would venture that for every user who is grateful that
/var/log/mail.log collects all the various mail-related logs, there is
another user that curses about non being able to separate (out of the
box) the logs from all the programs that consider themselves
mail-related, and another user who struggles to remember in which
logfile $DIFFICULT_TO_CLASSIFY_PROGRAM might be writing its logs.


There are log readers like "lnav" and "multitail" that will become useless
without traditional log files. "lnav" tails multiple logs by default and IMHO
provides a very useful interface.

Exclusively relying on systemd logging facilities limits ways in which we can
analyse logs.


Nobody said "exclusively" except you! Either option has benefits and 
disadvantages, but for some reason you're arguing as though 1) only your 
particular use cases matter and 2) continuing to use rsyslog isn't an 
option if the default changes.

Re: Heads up: persistent journal has been enabled in systemd

[Russ Allbery]

Dmitry Smirnov  writes:

> There are log readers like "lnav" and "multitail" that will become
> useless without traditional log files. "lnav" tails multiple logs by
> default and IMHO provides a very useful interface.

> Exclusively relying on systemd logging facilities limits ways in which
> we can analyse logs.

apt-get install rsyslog

Debian, of all projects, should be more relaxed about defaults, given that
we're the OS of choice for people who like to customize things.  I've been
using Debian for some 20 years and don't believe I have *ever* accepted
all of the defaults or left a system in a purely default mode for longer
than about five minutes.

No one is going to prevent you from using rsyslog everywhere that you want
to use rsyslog.

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

Accepted nvidia-settings-legacy-340xx 340.108-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 22:56:48 +0100
Source: nvidia-settings-legacy-340xx
Architecture: source
Version: 340.108-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Changes:
 nvidia-settings-legacy-340xx (340.108-1) unstable; urgency=medium
 .
   * New upstream release 340.108.
 - Fixed a bug that could prevent nvidia-xconfig from disabling the X
   Composite extension on version 1.20 of the X.org X server.  (390.116-1)
   * Bump Standards-Version to 4.5.0. No changes needed.
Checksums-Sha1:
 5f56547b115bb14f3a0224e90270ef3593dc2f17 2481 
nvidia-settings-legacy-340xx_340.108-1.dsc
 8857038e58cc3824e53266fa536087ac98d35f3e 1550018 
nvidia-settings-legacy-340xx_340.108.orig.tar.bz2
 b07d8ee10748c3b720ec7a2478ee9b3bc9341246 19364 
nvidia-settings-legacy-340xx_340.108-1.debian.tar.xz
 1498d1ff9df1ce8517aef219bea9be1d22b577f1 12251 
nvidia-settings-legacy-340xx_340.108-1_source.buildinfo
Checksums-Sha256:
 96e20162e1cbddd073232790440db8073a7af1c3a4894dbf58d8a733b0ab7d57 2481 
nvidia-settings-legacy-340xx_340.108-1.dsc
 d03c7f1d46be76191a2406ac347a5e309760b83b0302b3322126aed2e425e147 1550018 
nvidia-settings-legacy-340xx_340.108.orig.tar.bz2
 5bf0a6399ae716c19e7ddbc88e374e71f0cca4928240065aeefc990750fd11d4 19364 
nvidia-settings-legacy-340xx_340.108-1.debian.tar.xz
 d90fe7196a1b7498d8f73f1b3596f20d447b6788a1bdfb6ccbd2612d0041450c 12251 
nvidia-settings-legacy-340xx_340.108-1_source.buildinfo
Files:
 06dd4db710fa3394d515699cc2031174 2481 contrib/x11 optional 
nvidia-settings-legacy-340xx_340.108-1.dsc
 86944ff799d5798f407c5051282699b3 1550018 contrib/x11 optional 
nvidia-settings-legacy-340xx_340.108.orig.tar.bz2
 f11d673f346f98b9cbd56da5560a8bfb 19364 contrib/x11 optional 
nvidia-settings-legacy-340xx_340.108-1.debian.tar.xz
 96efc134b0b965f5973b8ee8d0f55b6c 12251 contrib/x11 optional 
nvidia-settings-legacy-340xx_340.108-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl47Ot8QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCNH7D/wOjSoDCqKFGZLBI16IiPaeWyOOjBiJ/8w1
RPIlBuNffkT0nw9K72avG9riuTNvLRkkYDwFZd2bvyBLIAKWijQzBZ91q0lb8EGs
TztRuV1iUdIaQWM3PvVvDPK/KdU4jX6tNNuUm2T5NbHajua8fSxkwU9uIaPPr/Dm
k9W8ewC7mEbBpZzDRs7HrrS5mooN7zZSe4mskax/vLnQ2MTZJeNyKk28ozK6KD+F
3Z/HDuSBY38UQp5KeXqxhw6KKzIlVqcVq3F20YpyDpqoxr9x9Z2BWDRQ4eVWnpy6
MB3i+oHYUvN29CiDrNVEIOLzTqrPTvN2ggieJVfInPG1NHetLf5llAD0SNuITqrD
PNMd4U33Q4WpzQ5oWDtYEyB0N+QEDjo6HfaUt97Zsl3NEkMzwelTJ+TT1Ii0wjLj
3NHUCn3KMgCym1PH63bmXSkOson60eBpKQgxuxYlWVpQMDuR5ikBbUjoPQeLg5+q
EJHl3oIOnC3chHuIFiAY6zHfuyPKOmKwA7PyY5bmdlaRMqc1dN/j9ObNtGCNiggL
gajqp50um4yUSAJkQv4d9oB6Tq1pjRtJa4rztA+75BNEFk8pjW/WD5t3UIgGaKmB
jZ9/dDMJ24IyaJCGflPzXUA2/635XnJ/EaV+bvEhBa6GTlErhJ6YFJauOJujGbbp
XF1mDDcBpw==
=nu2I
-END PGP SIGNATURE-

Accepted poco 1.10.0-2 (source) into experimental

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 22:56:56 +0100
Source: poco
Architecture: source
Version: 1.10.0-2
Distribution: experimental
Urgency: medium
Maintainer: Krzysztof Burghardt 
Changed-By: Jochen Sprickerhof 
Changes:
 poco (1.10.0-2) experimental; urgency=medium
 .
   * Add patches for broken builds
Checksums-Sha1:
 dfa373cd48eb4812b762fdc761ff3ba58f6cf6ea 3119 poco_1.10.0-2.dsc
 1d5892977ffaa5f8a432a3085d37399f750f2c8c 15404 poco_1.10.0-2.debian.tar.xz
 b813794ab0127f4256bd235b295e32a9e29dc800 8258 poco_1.10.0-2_source.buildinfo
Checksums-Sha256:
 e36e7e3064ba15ea56b9556db2c3fd6a46676db401172d34b6ce3d4e284f05fd 3119 
poco_1.10.0-2.dsc
 1ae9b784f9085b3ba6d5ee32ae4a0286fb2e8cce29b45aa54889ceab5c361301 15404 
poco_1.10.0-2.debian.tar.xz
 4d6151383eb471795d7285b3dcab295c5d833ba19962e8a71688ab86cd38cdb9 8258 
poco_1.10.0-2_source.buildinfo
Files:
 eafa79734fe99fa2c9a60f3226f49383 3119 libs optional poco_1.10.0-2.dsc
 b0878e0f0e9ee30c469249b5d34a3bb5 15404 libs optional 
poco_1.10.0-2.debian.tar.xz
 a995f1515dae06fd9ed0da66dfb40277 8258 libs optional 
poco_1.10.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl47OogACgkQW//cwljm
lDNIEQ//cf1yFvPna7/gp98ZnuwiLOhAinsOsDkL2I2ggArVq2GeUhRfkGu4Kxb7
NOI6X/cgL4cHtKJs1p7fxsgbPvQUccVZI97CpsmE5/po1M6JdjvuKOrjHo6/YCF5
wv+RlVpuJ0rZZ82jfGtqxI5wHvkziWKsMbkKhsCLorWE4vvX1QVpyl9d4bwhQ8Wr
EZN1XnQWw3P4k3TiveEVEQAkQQxGbKoJsWFOGBjkwDoj4L9IwgQN5TghOwRWiSk+
O7jy1FKJPHj9lN2+PrX0e2JWiP3zrckjqIXt+G7RNiTj4O8M2mUdMsONIVFuoZey
COQ+F53lzMBEMk2d9De7OKTx4AQSL/K40jl+yfCdOCu1J1+fQMAXjVNnvU815GW3
OlQoAywwa5Y/SQPQgyb/j8q80klD+J0uneN5duba4VTnLKB9+eK3gS4MqXNNIlfX
BL2v1DGVhq1gFqEKJ8hCq/CPsoNR0JBGU01kMXcBd/6gmXQhFwPvQiXgLO5E9qVx
IW/T7fHLn7BFOKiLrH/DgKI1AQBN8DFiym5klrUx1ZWTkb5y4Ndv/MXlNNyUl9KZ
a876+ByvDU2pOPE6sZH6B7YRApczDzGXHEYIUE6FQUadFawZbs6nRKXabDiVq+Ug
raZGWVCznUUSx4Bnb1Jc4TyQ3ktSmkn2kdNLtgUD5kO4ArNp0vk=
=oTam
-END PGP SIGNATURE-

Re: Salsa CI news

[Bernd Zeimetz]

On 2/5/20 10:33 PM, Dmitry Smirnov wrote:
> Upstream binaries are not DFSG compliant.

Why?

> Not only they use shitload of 
> vendored libraries

That is how go works. The exact version is available, the source code also.
The way how the docker image is being built is actually in the sources,
follow

https://gitlab.com/gitlab-org/gitlab-runner/-/blob/master/.gitlab-ci.yml

If you replace the used base image by debian:stable, and fix the way the
needed packages are installed, you could run this on salsa and have
Debian images out of it.

> but also bundle pre-built source-less Alpine-based helper 
> image 

Alpine linux, including the source to build their images is here:
https://github.com/alpinelinux
Afaik there is nothing in alpine linux that is non-free.

> fetched on build-time and incorporated into executable.

That is how go works.


> Instead of of telling me to go some place else consider that gitlab-runner 
> was rather difficult to introduce as an official package. Now when we have a 
> proper package for a while what excuse do you have to continue to use vendor 
> binaries that could not be accepted to Debian?

Still can't find a reason why the official and supported images are not
dfsg-free. They are not shipped in Debian, but they are free software,
binaries with sources being available, as far as I can see all under a
dfsg free license. Where is the problem?



Bernd


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Re: Adding security features

[Anthony DeRobertis]

On 2/5/20 2:52 PM, Nikolaus Rath wrote:


I think it's worth pointing out that this was an experimental feature
that users explicitly had to opt into. The original statement feels
misleading to me.



That's how it started, further looking (sorry, was replying from my 
phone before) give things like 
https://www.theandroidsoul.com/google-now-and-google-search-now-shows-your-recent-gmail-messages-when-you-search-my-inbox/ 
where various search terms show gmail messages. Which I just checked, 
searching "my inbox" still works here. I don't think that's anything 
special I've turned on, don't think "labs" even exists anymore in Gmail.

Accepted libime 0.0~git20191230.5b6e890+ds2-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 16:37:00 -0500
Source: libime
Architecture: source
Version: 0.0~git20191230.5b6e890+ds2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Changes:
 libime (0.0~git20191230.5b6e890+ds2-1) unstable; urgency=medium
 .
   * ds: Let src:libime to provide required dictionaries.
   * debian/control:
 - Drop build-dependency on fcitx5-data.
 + Bump Standards-Version to 4.5.0.
 + Mark architecture-dependent packages as linux-any.
Checksums-Sha1:
 4a93020da368d2862471fa55566cb80a4d4e2146 2669 
libime_0.0~git20191230.5b6e890+ds2-1.dsc
 5080eeafea0787c6cd4c8966aa0dc2477765958b 54681532 
libime_0.0~git20191230.5b6e890+ds2.orig.tar.gz
 34673dec5fea541b31f72e02ad42a96235f3f1af 6500 
libime_0.0~git20191230.5b6e890+ds2-1.debian.tar.xz
 8146a2e5879ab00d7c7662174ad45560e1a16b3f 11327 
libime_0.0~git20191230.5b6e890+ds2-1_amd64.buildinfo
Checksums-Sha256:
 652835ddfd0f0d688814fec9ec12ba3229bbe92ed0a5f4eaf847e5693fa85948 2669 
libime_0.0~git20191230.5b6e890+ds2-1.dsc
 8fe724bffc8de11aff5efee5f55ea53bdee2cd0f56a713410aed9a45149c7333 54681532 
libime_0.0~git20191230.5b6e890+ds2.orig.tar.gz
 8df7ffa3dd39d8581b7f17f8adc9eae915a11fe6085df58347992e0833ef06fb 6500 
libime_0.0~git20191230.5b6e890+ds2-1.debian.tar.xz
 089a02991a6d05c8ab460e084367902b623e12ca8a56d4e1b5fcdfaca9844da8 11327 
libime_0.0~git20191230.5b6e890+ds2-1_amd64.buildinfo
Files:
 2e068bf9ea58d8ab2336f172b8a1ce17 2669 libs optional 
libime_0.0~git20191230.5b6e890+ds2-1.dsc
 9ac6fb35289fca41380cb7bf8cd7b33e 54681532 libs optional 
libime_0.0~git20191230.5b6e890+ds2.orig.tar.gz
 bea36e5b4fd4d88654834ac880b12bad 6500 libs optional 
libime_0.0~git20191230.5b6e890+ds2-1.debian.tar.xz
 914ee4f8b28988c3833325f952f52274 11327 libs optional 
libime_0.0~git20191230.5b6e890+ds2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl47N+IACgkQwpPntGGC
Ws5qHw/8CA4+riU8jbuBfzpZIwI/CSykpm8nffLmk0vEarw7aEUftDUdTi9LV7vi
ECHVKtX6oSqhLWEpYWnEt34UnLQpUdem9MF2SNdH1vVVF0v5DpLKF7Ql7x1/5+hZ
mk8i5M7luWG6BroJ9Uab6RU0MnreUMLecGIZbaXtLKBt7AZQ/9lTjqqMmhMkay86
U7zgoYDSRYCXFCUZRZEwaAT8YkgqhmFpzsJq2asUvuhLatVx/kBIf38ElS6Oyub1
pDCM+HGop7IaMgHCtEB5GnqG+v5tvg8MTiSem9+u1ClH5xUvUpN//nWZECYc8FKK
/S+NegNqA1jcoNUEvXcapZAoMg9lPat1QeOtYgAIW5WluAhr+RiQjmxNu8SOl3WG
ZVRPzyg9imRboEc2RaBUAuJynIREoZTArGlaZPQJlQn95Pug9OmzU7Ag/lJ0c2lB
lPLbGbK5f2V3c2V5EKrLuvL8H8IwUGDN80FQMdjI3rKa6SBEBcxgsGLsVgBt987U
lo5crgePHkd7+Fc+nX4nNnNp65zOD0RujVO9o4At0MC4Cz+j8lVJRkWqJvTpYPFi
03e3KxngPGTAJn3g9MQVQ2NjPZPDXfSCI7XADe5+uZ88S1rRfXNwp5NwSt99cYYw
r3P4g0JTFsLiyBTAYQNif3IyEpvd/K0ak/xIlUQI6+GZnlbiJQ0=
=tSJN
-END PGP SIGNATURE-

Accepted gst-plugins-bad1.0 1.16.2-2.1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 22:46:23 +0100
Source: gst-plugins-bad1.0
Binary: gstreamer1.0-plugins-bad-doc gstreamer1.0-plugins-bad 
gstreamer1.0-opencv gstreamer1.0-plugins-bad-dbg libgstreamer-plugins-bad1.0-0 
libgstreamer-opencv1.0-0 libgstreamer-plugins-bad1.0-dev 
gir1.2-gst-plugins-bad-1.0
Architecture: source
Version: 1.16.2-2.1
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of GStreamer packages 

Changed-By: Gianfranco Costamagna 
Description:
 gir1.2-gst-plugins-bad-1.0 - GObject introspection data for the GStreamer 
libraries from the "
 gstreamer1.0-opencv - GStreamer OpenCV plugins
 gstreamer1.0-plugins-bad - GStreamer plugins from the "bad" set
 gstreamer1.0-plugins-bad-dbg - GStreamer plugins from the "bad" set (debug 
symbols)
 gstreamer1.0-plugins-bad-doc - GStreamer documentation for plugins from the 
"bad" set
 libgstreamer-opencv1.0-0 - GStreamer OpenCV libraries
 libgstreamer-plugins-bad1.0-0 - GStreamer libraries from the "bad" set
 libgstreamer-plugins-bad1.0-dev - GStreamer development files for libraries 
from the "bad" set
Closes: 922583
Changes:
 gst-plugins-bad1.0 (1.16.2-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Upload patch to fix build with newer opencv (Closes: #922583)
Checksums-Sha1:
 a64eb35741e9721b10b414422f8f1620af6021f9 4869 gst-plugins-bad1.0_1.16.2-2.1.dsc
 d8dfedae3b029b29ff08f843aeba7450510390b2 34636 
gst-plugins-bad1.0_1.16.2-2.1.debian.tar.xz
 c14af190aaee073b2a7b281476069075013aa794 19489 
gst-plugins-bad1.0_1.16.2-2.1_source.buildinfo
Checksums-Sha256:
 3c4408831f93b87e000d2f62b25c5a6ec8e4fed9f73b5cb600dadc4e35cb24d9 4869 
gst-plugins-bad1.0_1.16.2-2.1.dsc
 bc6ca1ca253feb1ca8a3dc6e5afb5dc6fd9df9c7b6dea0877ed8634e8b65d6c6 34636 
gst-plugins-bad1.0_1.16.2-2.1.debian.tar.xz
 cc6d8de856368607bae823d289ab90e4a00cd0ebc32bf46e2033688ffbdfdb03 19489 
gst-plugins-bad1.0_1.16.2-2.1_source.buildinfo
Files:
 c167c0a9711e278da3a2336e24db8e18 4869 libs extra 
gst-plugins-bad1.0_1.16.2-2.1.dsc
 fd49bda1adca94b88dc1a482309cca1c 34636 libs extra 
gst-plugins-bad1.0_1.16.2-2.1.debian.tar.xz
 2c5bf272dba10a10e5290df3f8f5a09f 19489 libs extra 
gst-plugins-bad1.0_1.16.2-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl47N84ACgkQ808JdE6f
XdnDnRAA0KEnVm9a592HiFd7EBKF6MoI9Y1n7Y86i5ZdAM9mPTDTOaHrk/OFMFzh
6sQILUb5Cp9fc+WceSpZYolNYOQhoVYtBCNs4T83q9IqdtNkf4bnagIc/0kEAa2u
TXtladBV5+zeRzjqkwXsTGcnGUvotDprewu9mA1pVkWgrKi/1FjyJS7Hy9sifLrq
Rs8dqNGko24weYWgxFrQOxLh5FZkcpTnmSAE6mIVn4UlXdJ+np55rpqu0Vl2Vd+H
IMhjt7DprI1KJcmuaq19umS1I6BmQbYeWS/DM5UPpDI25yTKIhfxORwHD4ZXOLuJ
4sgIAuPbqHZusYg9k/5tFtcZ5P5oq7APzGwVbdVMt3fWsNmDIAgURMAOck1b6trK
/hEiUzuV5Mt0nVRVjJ4KuNZU5iBAfKCnLNzPmtJkUiJztNJZdTzpfEYKOE/FIRXe
jjPL4VmenJtGNrkn9Cm2NT76iRo3KMd00HuQMKEpHNhKalsNuNjwlisfxsHeoWWw
B9YIg33roNP3Rjq4w7y/ujEpct0O9jJOcKx3RGQhyPMfjDDXnvgzaqxc5+8FrcTw
JQ9UiCRe4ny76Z73nwT8ry8pGN/Qc0z0ssjAeQC3JSEIUGbyyVk4YTHlHKxjFeJB
IRLF36SX4gAc7NzaoI6pHtWd1M+K0BcxI80CQH8+XYS4oFGFCaI=
=ymu4
-END PGP SIGNATURE-

Re: Heads up: persistent journal has been enabled in systemd

[Dmitry Smirnov]

On Thursday, 6 February 2020 6:59:38 AM AEDT Nikolaus Rath wrote:
> I would venture that for every user who is grateful that
> /var/log/mail.log collects all the various mail-related logs, there is
> another user that curses about non being able to separate (out of the
> box) the logs from all the programs that consider themselves
> mail-related, and another user who struggles to remember in which
> logfile $DIFFICULT_TO_CLASSIFY_PROGRAM might be writing its logs.

There are log readers like "lnav" and "multitail" that will become useless 
without traditional log files. "lnav" tails multiple logs by default and IMHO 
provides a very useful interface.

Exclusively relying on systemd logging facilities limits ways in which we can 
analyse logs.

-- 
All the best,
 Dmitry Smirnov.

---

That which has always been accepted by everyone, everywhere, is almost
certain to be false.
-- Paul Valery


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

Re: Heads up: persistent journal has been enabled in systemd

[Didier 'OdyX' Raboud]

Le mercredi, 5 février 2020, 21.44:43 h CET Dmitry Smirnov a écrit :
> On Wednesday, 5 February 2020 11:01:08 AM AEDT Scott Kitterman wrote:
> > We just had a GR where the project voted it was just fine to systemd all
> > the things, so this sort of thing is to be expected.
> 
> Are you suggesting that voters fully understood the implications?

Let me suggest (out of reading what they wrote in other parts of the thread), 
that I read Scott's message as a mix of despair and sarcasm.

> Is this OK now to replace everything with systemd counterparts?
> 
> I certainly voted with considerations for _init_ system.

The vote was named "init systems and systemd".

> If I recall correctly, no GR option suggested to "use as much systemd
> components as possible" or I think the outcome of GR could have been
> different...

This was option "Choice 1: F: Focus on systemd".

The option that won, "Choice 2: B: Systemd but we support exploring 
alternatives" [0] said:
> Packages may use any systemd facility at the package maintainer's
> discretion, provided that this is consistent with other Policy requirements
> and the normal expectation that packages shouldn't depend on experimental or
> unsupported (in Debian) features of other packages.

Of course, it's ironic to read that under this project's opinion; "src:systemd 
may use any systemd facility at systemd maintainer's discretion".

But, irony aside, we _did_ decide that we were to allow systemd facilities' 
usage, and moving ahead with journal's persistent storage seems to me very 
much inline with the project's latest GR-backed opinion.

I'm not saying the project decided "journald should replace rsyslog" though. 
I'm saying that activating the persistent storage in journald feels very much 
inline with the project's expressed opinion. Also, it is orthogonal to whether 
we should be demoting rsyslog, or to what would happen to it upon upgrade.

OdyX

[0] https://www.debian.org/vote/2019/vote_002#textb

Accepted ruby-friendly-id 5.3.0-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 22:15:51 +0100
Source: ruby-friendly-id
Architecture: source
Version: 5.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Changes:
 ruby-friendly-id (5.3.0-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Utkarsh Gupta ]
   * Add salsa-ci.yml
 .
   [ Cédric Boutillier ]
   * New upstream version 5.3.0
 + Add support for rails 6
   * Bump Standards-Version to 4.5.0 (no changes needed)
Checksums-Sha1:
 a4aad3a8a2cda6ec9a4502e1145ad953ae9e967c 1811 ruby-friendly-id_5.3.0-1.dsc
 a3dabcd7e6186d3ac55a3ff7e4ea95337ce52b34 46073 
ruby-friendly-id_5.3.0.orig.tar.gz
 e33cceac4cc53e288690a022d29168d47a3b0fca 2616 
ruby-friendly-id_5.3.0-1.debian.tar.xz
 8d5191d6b97c70887cc29f0767c0762f1bbcfd21 14803 
ruby-friendly-id_5.3.0-1_source.buildinfo
Checksums-Sha256:
 cd1ba0e16fb29c889f9875469287f78970e66f1f07819a4adf5d67cc3f2c1de3 1811 
ruby-friendly-id_5.3.0-1.dsc
 071114d995837437995b80e84a02b94082cea8e52237b52bc692c93b55cac37a 46073 
ruby-friendly-id_5.3.0.orig.tar.gz
 dc1b515f809e70a565bf0bcced83b56ab0236050a48af98ca4bb467c5b458b8c 2616 
ruby-friendly-id_5.3.0-1.debian.tar.xz
 d88ce15b9bda5be4a7b4c4a28a20047a705e31726eb3553d98c1027803260c39 14803 
ruby-friendly-id_5.3.0-1_source.buildinfo
Files:
 b5930f0a65e9e113ea6abd3e030488fa 1811 ruby optional 
ruby-friendly-id_5.3.0-1.dsc
 534e35ab1b732f042985dff433aff210 46073 ruby optional 
ruby-friendly-id_5.3.0.orig.tar.gz
 9d1fa6882bf55d414d3290460b9b49eb 2616 ruby optional 
ruby-friendly-id_5.3.0-1.debian.tar.xz
 96fec716ec19ecc87a078e0dd3eb06db 14803 ruby optional 
ruby-friendly-id_5.3.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAl47McEACgkQia+CtznN
IXqWoQf/XRTAL9F7a0yEqvdyBmFNPWIjBzGRQ20hVb7/+ElxHDyTY92PU1FJxmz5
GHQq8sh+mlXpzrRGtmYRRrFn0CNJmiNQZvRBqvuLStMXi3a8LlMLVx4ed38Ebnon
4kRX0MJ5evpNaEGgp7/6vILnLipFnBEPS3kxbd+XDwQfc2PUBS7tWtBSLnP2BP3g
qsLXocXCfxc/fWoTG0weMPqAQYkeQUnNotedTbQV3FnIOhNMgl02sAVPw/gK5AYr
aOs/gn2jt7oFBLGzdyl45UwwNZpaBTSk6y25DmdCvBvSOVwV/xsNqOzbGSfnzOBv
EQl8+gn9ktU5BHfx6b+Dnlq/i+5TZQ==
=LX9x
-END PGP SIGNATURE-

Accepted nvidia-settings-tesla-418 418.113-2 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 21:51:48 +0100
Source: nvidia-settings-tesla-418
Architecture: source
Version: 418.113-2
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Changes:
 nvidia-settings-tesla-418 (418.113-2) unstable; urgency=medium
 .
   * Upload to unstable.
Checksums-Sha1:
 ebfa42bacd25d1e67428c8b38195c55c200c72e1 2475 
nvidia-settings-tesla-418_418.113-2.dsc
 214f8d7fe5f05b36d31f914aa744162b1ef06187 21492 
nvidia-settings-tesla-418_418.113-2.debian.tar.xz
 b015e11c4cb7fe9a80629e15ffa174a196ba0928 14010 
nvidia-settings-tesla-418_418.113-2_source.buildinfo
Checksums-Sha256:
 9ac85c3d2b4f16550075c06f4245283b71e4aa1be19c433b849504d0626ad9ad 2475 
nvidia-settings-tesla-418_418.113-2.dsc
 e294a2b52bd0993df394671ec4d8b27efa83bd29dfb255629409025e800e1120 21492 
nvidia-settings-tesla-418_418.113-2.debian.tar.xz
 4b0720eb5221fb398625beace16cebdbdfcf31913416f3454ab4b79f5fb9f909 14010 
nvidia-settings-tesla-418_418.113-2_source.buildinfo
Files:
 f8092738ecc8d825b44958acf22c2cf1 2475 contrib/x11 optional 
nvidia-settings-tesla-418_418.113-2.dsc
 a72da48aaf85d94f439a5a2633ec8470 21492 contrib/x11 optional 
nvidia-settings-tesla-418_418.113-2.debian.tar.xz
 692f8f1e453cd73b932b849f4da44f5e 14010 contrib/x11 optional 
nvidia-settings-tesla-418_418.113-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl47MboQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCDTXEACwgP6bkneBzdFnDmrENZsPY92sfskUuCoC
m9RGvqvkeZvFqRaFoiHJumiiun+v/yTxQh+V/UC/r/zF4TPnMUVY85y05kMxcCbm
zpK2eLwI/x4D+x9zlWaf7FHyIUpao/A81DkLw9om2UGQUwY18yATFbd9Rm62DrG4
j79wayg9+7uPmqH8EQWwLjF5k/IjlbIf3Dw9xqOxjFMRgniBGEuelY58EbpDT09u
0M5pvS3/5ifKxvPveCPMHkQEYCoM00xAJQYAZ7ibbM5SY4ojt8PQ5AdQhsGOUEeE
qFCAuM5B5oEddkx6JL8N1A9217vSUBpjbMtVZdXmbjvOGnpJtMlzyG/A9XPhJpCy
diF11+SUbzTZ90fq35fFttYk97IpbrVfxZKisu4BJk8IJ1JRBFYF/eh9S9ZZYz8/
BFrIprqxnnw4Z5y8deg+2lfrGiqlC3S/hQgAsBJxbT3dO4Y+oFXw9t7b4jm7feCe
q7kn7UTd/bBdcQZ1Ktr4H+AjGrgAOqe+wUTTX5RiiZVl8rbUgDf7OvFrsE/MzeHm
VnzkvLrHglUnS/3BeyOdAitOA1Ll6TF24Aoq26frGvnVK7UhMSNJco5nc11xchwh
MO7vxGL0mAh5/YhXdkyNAV9G07Oy86mfKNREcTBTGaEI3tk65xMjvu/nvPlMu6v6
t1bLAPw12g==
=5aPG
-END PGP SIGNATURE-

Re: Salsa CI news

[Dmitry Smirnov]

On Thursday, 6 February 2020 8:10:17 AM AEDT Bernd Zeimetz wrote:
> You are free not to use salsa or not to use the gitlab runners.
> You are also free to rewrite the gitlab runner in a free version, if I
> remember right the api is published, so this should not be hard.

What warrants such a hostile reply?? Would you please care to read and 
understand the issue? There is no need to rewrite gitlab-runner, just to 
avoid vendor binaries.

Upstream binaries are not DFSG compliant. Not only they use shitload of 
vendored libraries but also bundle pre-built source-less Alpine-based helper 
image fetched on build-time and incorporated into executable.


> On the first look all used and vendored git modules are also under a
> free license, so you might want to provide some more details if you want
> people to take this serious.

Instead of of telling me to go some place else consider that gitlab-runner 
was rather difficult to introduce as an official package. Now when we have a 
proper package for a while what excuse do you have to continue to use vendor 
binaries that could not be accepted to Debian?

-- 
Best wishes,
 Dmitry Smirnov.

---

Truth — Something somehow discreditable to someone.
-- H. L. Mencken, 1949


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

Re: Heads up: persistent journal has been enabled in systemd

[Matt Zagrabelny]

On Wed, Feb 5, 2020 at 3:03 PM Dmitry Smirnov  wrote:

>
> Anyway the big disadvantage of changing default is that now random Debian
> systems will have no traditional logging interface (rsyslog) and we're all
> will be forced to adapt to the new interface in the absence of old one on
> some systems...
>

>From Michael's initial email:

"Depending on how it goes, I might ask the ftp-masters to lower the
priority of rsyslog from important to optional, so it would no longer be
installed by default on new bullseye installations."

As of right now, the only change is to enable persistent journal logs.

Text logs will still be there with the current systemd upload.

-m

Re: Heads up: persistent journal has been enabled in systemd

[Andrey Rahmatullin]

On Thu, Feb 06, 2020 at 07:44:43AM +1100, Dmitry Smirnov wrote:
> > We just had a GR where the project voted it was just fine to systemd all
> > the things, so this sort of thing is to be expected.
> 
> Are you suggesting that voters fully understood the implications?
> Is this OK now to replace everything with systemd counterparts?
Yes.

> I certainly voted with considerations for _init_ system.
> 
> If I recall correctly, no GR option suggested to "use as much systemd 
> components as possible" or I think the outcome of GR could have been 
> different...
The winning option says "Packages may use any systemd facility at the
package maintainer's discretion, provided that this is consistent with
other Policy requirements and the normal expectation that packages
shouldn't depend on experimental or unsupported (in Debian) features of
other packages".
You can read it at https://www.debian.org/vote/2019/vote_002#textb

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Accepted pycangjie 1.3-2 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 15:49:37 -0500
Source: pycangjie
Architecture: source
Version: 1.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Closes: 949971
Changes:
 pycangjie (1.3-2) unstable; urgency=medium
 .
   * Team upload.
   * debian/control:
 + Bump Standards-Version to 4.5.0.
 + Bump debhelper compat to v12.
 + Use Build-Dep: dh-sequence-python3. (Closes: #949971)
   * debian/README.source: Dropped, useless.
Checksums-Sha1:
 a695ecce549f22287150a56aae3dfb24e0bc990d 2058 pycangjie_1.3-2.dsc
 3104bf417cae69b149327a4d8d082f956751474a 3308 pycangjie_1.3-2.debian.tar.xz
 702a69634ee4173b8e7a32c26a9400d6aeac037b 6909 pycangjie_1.3-2_amd64.buildinfo
Checksums-Sha256:
 ab2b8530a73a8b394488d643bd54b227035867147100abffd15b37bed627b652 2058 
pycangjie_1.3-2.dsc
 3d76c0fad37097f3b4b49530b1faa6a64dc90936aa745a58ec14a3f267294569 3308 
pycangjie_1.3-2.debian.tar.xz
 bf80fa7f175cfad3ac28a17e08d6f9f00da5a60e591d2e833dc9276863382a6b 6909 
pycangjie_1.3-2_amd64.buildinfo
Files:
 f685a5acf0fe9d87199d780e557cf6f1 2058 python optional pycangjie_1.3-2.dsc
 0f70acc5912ed4064fc5a1a1ef1cb1a9 3308 python optional 
pycangjie_1.3-2.debian.tar.xz
 d80a33ab2a8a6149717f22b83896839e 6909 python optional 
pycangjie_1.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl47LK4ACgkQwpPntGGC
Ws4XLQ/+IZ3fmqmsWvrhxK+NBa190h/4deFeoZdM0GHOuweNCuxr8R6o4mTPd08J
F7EcfO0YyYlqXBK3xZ82AnMjkjca30yZGrSSBAGxYl93j1RtHJ4vG3O2k482iDRs
IR9hiPylmAwW9GXLAKIs3r1H0al88JKw4yT8f8ZRSBtW83KKid31iWFMIxFrWnBz
mvMiJ3JIaTO/gYrNkdXAb/B9f3cJds8F+OnktwUBm0YAXxANNd73Z6b88sJ7QQyO
3GGwh7/Tz+4Lv/XEkP0F2qVavcTqhectnnc32L8peKEvRTQSyX678pWgcRYon3gD
Hmq5zuSNDSLvBx3Vz//ItrY0nIjWshzogdvNCWeq83VwBylE0TdYoyQRo2n4eSmp
jyvbb4VCIoYTnbPbdLoVV/dFA7AnGKEqey61SqAeTTpj47dvNjqt7QGcWUxZe+of
oWSCrTa9MmWLsqicrbxd1uZpxYp5T4vqyA7z/q/GaAKLI+j6Ln4cOlSrK9WJ4lP4
J7D3B1SOzho8m3zZkyQNbN4D3R3yiSqu9+G3ZalQkyEPfPbCQQDUgZJcIX9I1qEK
CJG0QzihIxVZ2TMLkIEZPdXVsaQN9V8A+94Ddxnlnf75vWR03z81YxuflwLGXZoX
byLtRT7EEhvD5PIotMFcO6Z+Qfouke9WiLftPyt5hmAj2FcgckU=
=2D9L
-END PGP SIGNATURE-

Accepted lv2file 0.84-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 21:52:25 +0100
Source: lv2file
Architecture: source
Version: 0.84-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dennis Braun 
Closes: 776244 852439
Changes:
 lv2file (0.84-1) unstable; urgency=medium
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
 .
   [ Dennis Braun ]
   * New upstream release (Closes: #852439)
 + Allow piping raw FP audio from stdin to stdout (Closes: #776244)
   * d/control:
 + Use dh-compat instead of debian/compat
 + Bump dh-compat to 12
 + Bump Standards-Version to 4.5.0
 + Add me as uploader
 + Use https protocol for homepage
 + Set RRR: no
   * d/copyright:
 + Update source url
 + Update year
 + http > https
   * Add patch to fix the debug package
Checksums-Sha1:
 a45bbafe68363972ea52c674e8ca17e404d893ed 2037 lv2file_0.84-1.dsc
 8d92e246d73ace4c91fa423d624f5bff3565d450 7200 lv2file_0.84.orig.tar.gz
 f807fc788919e2e6f5b3eeb6bf40a485f751b537 4364 lv2file_0.84-1.debian.tar.xz
Checksums-Sha256:
 e43a10c188edfd7338181605a290a8c5557d8761f3b049c4b4a35ddd1937303a 2037 
lv2file_0.84-1.dsc
 2c63498a76c52f6712e5e5d0bce8686efd407364e1218cf0a698f1a7e52ad979 7200 
lv2file_0.84.orig.tar.gz
 0e7bcc5cc6d4f0d10242ed9e97fb19b9717905500bddaa0c7bb7b809dda005c6 4364 
lv2file_0.84-1.debian.tar.xz
Files:
 d4ef0e3fa9c24cf6958710fcb04c4b6c 2037 sound optional lv2file_0.84-1.dsc
 259719c6291d4b774db3e3a485e12d18 7200 sound optional lv2file_0.84.orig.tar.gz
 5708810c61a42d2184b812e4025f3f61 4364 sound optional 
lv2file_0.84-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl47K9UACgkQafL8UW6n
GZOqJQ//ZsKMEI9IRc2o49AYWFhOxR+TCA5Ea3VJqUrq4M77zTibjGbDT1H+JQl1
Q12Z4YIzQmMfSjYE3gOccxLCiaCpPiWfIXfKUDlP7/aefQ3hA+XoUqFxX588j/u2
2a4jyZRRGNMgB/HZiKOhArcqQZMavHjcaLf053cXfRT7IF7T+lCJM64TnfrWqrQJ
+3o0EFzluLqi+BDBOz/Q82SzCymSXjxtb1FKvINegBnZuyYwc286rL6PYYePrc+Z
Zbsc8rVypZO5i5DNJ/TYyudJhcio7aKTwBFz7lvUUZ49RfA/yRJcRgTTt4zazlmF
XP6HFDCch28XV74+2BbUz+pR6VlRwYxw22paKnrm8/NiQ/v+ahlwyocxuufsDIzp
Qa4NJzWxnHB+c+bHfXyFQ3f28Z3KqrBxOkjKrhWWAYdR5MBI+U1gyldtfjfNnUBJ
7iwX3grgUzsYNc6W08aWQcOt6iaYyEG0/rEHKqFD38hm1emGdDNJdP07wLUj1MMf
kdIJoAcYfsBKEzVV9A0FkixXa/UKSpJQ4QjEAcgw2PEM1iEJ2Wh3f5r5FKlBhfvu
PqMN4IE3XQ0QdsL35G6ceI7RjXJ47vj5Cu0RqaHaA7fAGomu/UWpAcHvv51DZnh3
R99hSKlZzW02ZIt5FNjvGlECNmHBMfAmxvMpTuyybRK2UfDDqko=
=Uc24
-END PGP SIGNATURE-

Accepted libcrcutil 1.0-5.1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 18:41:16 +0200
Source: libcrcutil
Architecture: source
Version: 1.0-5.1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Adrian Bunk 
Closes: 945546
Changes:
 libcrcutil (1.0-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Enable building on riscv64. (Closes: #945546)
Checksums-Sha1:
 fd1af5b87c39442ec24fef0b9ee355baba311f0b 2385 libcrcutil_1.0-5.1.dsc
 f3d4ec2924c564a3e0d701fe28c8330ba1bebb61 7996 libcrcutil_1.0-5.1.debian.tar.xz
Checksums-Sha256:
 7e04ce50bc38a5370227a20c1c7ddf726361436d2c7981e156bd1f60ccebd887 2385 
libcrcutil_1.0-5.1.dsc
 846030003fd818d5a25bc7b39d761617ca7062bcc270d853602bce35107b0c7e 7996 
libcrcutil_1.0-5.1.debian.tar.xz
Files:
 59e69f2351eb09107e68f0780a861080 2385 libs optional libcrcutil_1.0-5.1.dsc
 96a5bdc59e1af17d1f90084499b7caf0 7996 libs optional 
libcrcutil_1.0-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl469IsACgkQiNJCh6LY
mLEJ+w//eO5kE3e9iaYF0LNo3o75xa3zHsnlKULdTkt+q8ffDi0z4afEOrNGRtxK
/rWLVtX+Hc2r3KLUfQrWKo2kM/j8scUUWfk+nRim1iFaZVnc9UT0Fr7dUjHZ5m3B
GF/uHaSuTkBklfWPR1Gdk57tlWE7ieZ2ESi+N9NDoqpoJpRQoCIg6Xng9h9LhoAk
e8HHHmdLJ+NbniPTx/87upJ8Y4gfe7kwiBZsQipC171t6sVKv/nISDCHRK/SKr/H
GiMHcA8TgAFqeUUxO4EA2fRrJ9uEtCEFLWIwwM9Cekb3PeCtjMKSQkycsXooOqSR
hGbbLNIdvMDO/t1eJ2X6hDGw5kILh8Mju5sdFkPykkEtZYR5kWlm5IqTNOkCmwg8
fnuBdlK9iRUeQCFGHGWCWEpGKC5bB+3DznVA/Fv7ABEJ4o1awMARXYgae6T91sN0
35HhR9oy5vqiv+FXKpucs3rKr5EvzvmpUa/kV3arISHSqHT3+RqJBBAoN3nDyzw1
JMkJmvNTnQNFKzeSK/KfFDCseAvTsSS8AUgxJILV6QlCZXUZ+Mv04AJI9yR6hU/l
pkh74J5a9iVgYyeg6Y3btqq414FXJ+fF3F6U3exxphiIrpV6X0Xq6QQZClK/eEdN
j7bdeDh/AAEmMIiUC43GdXxXIjxAKVE69cG97b4X23JNVPJPSBg=
=+Bhc
-END PGP SIGNATURE-

Accepted deap 1.3.1-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 21:56:52 +0100
Source: deap
Architecture: source
Version: 1.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Miriam Ruiz 
Changed-By: Christian Kastner 
Changes:
 deap (1.3.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   * New upstream version 1.3.1
   * d/patches:
 - Drop 0002-fix-tests (fixed upstream)
 - Drop 0003-remove-pngmath (fixed upstream)
 - Refresh remaining patches
 - Add patch Use-system-MathJax-library.patch
 - Add patch Python3-syntax-fixes.patch
   * d/control:
 - Bump Standards-Version to 4.5.0
 - Set Rules-Requires-Root to no
 - Add python3-setuptools, python3-nose to Build-Depends
 - Switch binary package python3-deap from arch:all to arch:any
   The new upstream version compiles an extension
 - Add libjs-mathjax and fonts-mathjax to deap-doc Depends
 - Bump debhelper compatibility to 12
   * d/rules:
 - Move sphinx doc building from install target to build target
 - Add hardening=+all to DEB_BUILD_MAINT_OPTIONS
   * Add python3-nose to autopkgtest Depends
   * Update copyrights
Checksums-Sha1:
 4fe068fed26af6020590a1f8bde0d99bf2b3840b 2223 deap_1.3.1-1.dsc
 777dfcc0cac0353c22f42bfc0257011ce42011b2 1068273 deap_1.3.1.orig.tar.gz
 490fab5be289d20317e1b885165154b863c00c07 11600 deap_1.3.1-1.debian.tar.xz
 59b50eaa1275b4a0be272d11cda3b6d70d3de455 10119 deap_1.3.1-1_source.buildinfo
Checksums-Sha256:
 cc39868db9179d5223aa0634dbf9c31c89c4b6c719a9c171cd642b186941294b 2223 
deap_1.3.1-1.dsc
 11f54493ceb54aae10dde676577ef59fc52d52f82729d5a12c90b0813c857a2f 1068273 
deap_1.3.1.orig.tar.gz
 7966216834634eb9c352fe0680884c2fdc18439b1fe6b733ece98654f10efa4b 11600 
deap_1.3.1-1.debian.tar.xz
 bb3b4dedd8fb9c06ae1dccdd26e108751c6429cedea4b0997f8ec7dff082028f 10119 
deap_1.3.1-1_source.buildinfo
Files:
 5fda783d21f0f1c90773dfd92cada9be 2223 python optional deap_1.3.1-1.dsc
 ee30a9db17042ba15b7819d3d2713648 1068273 python optional deap_1.3.1.orig.tar.gz
 15b8eeded0a9fb1955fd79b599960e9f 11600 python optional 
deap_1.3.1-1.debian.tar.xz
 afe8d71908d10b02b755b8e6f3ae826b 10119 python optional 
deap_1.3.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEQZ9+mkfDq5UZ8bCjOZU6N95Os2sFAl47LG0PHGNra0BkZWJp
YW4ub3JnAAoJEDmVOjfeTrNrHKAP+gOtGzLP+G5ejhw5ljnVoUkpLq60ygpwWh40
3p1h7nYtzLucwyWr8UwvL/+Nlv22FbfqItIOyfgDOoPplGATl73SI7OB/19ARr02
qVkyBZtwzVsCUOteTl6pl5G+lew46rzSi4GOnzPB17XbqSq3W5rbQui/9ng5CDlW
Sy4pfFmjcI4PJE87+YPlD1bPnOh+78Du2RYZJwHWYaWrb0hTGAWhRivCvrAv7Yq4
p7t3T7nuQzRFUumy5BBy2HF7W6nstODF8IGzCW7LXWU8pd+Ow/YMr2cL8cjp62t4
oRVrGQv6nSX9q/DYFNcL5RHveChlCA75Vrb0PJdcrTJMp1rkczCep1Kry6k/ogrs
sbTeMpU/NH+3vTaUqeGxEf115K7vo61l0iJ6RmMugeUMC2k9F8AatOuo+Df9xsGb
UExjXlsalyPh7khNIzZ4K1gJwIg0f80BCLJuwFIO+WbM8zdL0KtsZl8SiUiM1R2F
wIJZnYV7D8h/2OaFo0l/YAhdJsUkNpbr6yxrFTe4iZy5wdSxmnhhL/VU6e1cElUT
KYb7O2864ARZ39dZhftl10FY1jwFVV/DAG+grvIpfwqzpovMN/qhTI6Vkx2HnOGP
G11CZK3D5OoIBYVF8gdVWY1D3/i9r/ZltlsXxRWNDNvdY9LA/9ooS/hnZAaebVBb
0SFwjAeE
=hLm/
-END PGP SIGNATURE-

Re: Salsa CI news

[Bernd Zeimetz]

On 2/5/20 9:25 PM, Dmitry Smirnov wrote:
> On Tuesday, 26 February 2019 1:19:35 AM AEDT Inaki Malerba wrote:
>> [0] https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md
> 
> Thank you for providing this useful service.
> 
> My big concern though is that primary gitlab-runner 12.7.0 (HEAD)
> on salsa-runner.debian.net f0fdd533 is not DFSG compliant.
> 
> Frankly I don't understand why such issue is tolerated on official 
> infrastructure.
> 
> Please use properly packaged gitlab-(ci-multi-)runner package.

You are free not to use salsa or not to use the gitlab runners.
You are also free to rewrite the gitlab runner in a free version, if I
remember right the api is published, so this should not be hard.

Also the gitlab runner is licensed under the MIT license, so if you did
find something that is not free enough for your needs, take the source
and replace what you do not like. Please send it as patch to gitlab then.
https://gitlab.com/gitlab-org/gitlab-runner/

On the first look all used and vendored git modules are also under a
free license, so you might want to provide some more details if you want
people to take this serious.



-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Accepted fcitx5 0.0~git20200128.9e3bc8d+ds1-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 14:19:46 -0500
Source: fcitx5
Architecture: source
Version: 0.0~git20200128.9e3bc8d+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Changes:
 fcitx5 (0.0~git20200128.9e3bc8d+ds1-1) unstable; urgency=medium
 .
   * debian/control:
 + Mark package fcitx5 to be suggesting the Qt/GTK frontend
   packages.
 + Convert package fcitx5-modules to be in metapackages section.
 + Bump Standards-Version to 4.5.0.
   * ds: No longer ships libime-related dictionaries in fcitx5-data
 package.
Checksums-Sha1:
 eab152c5e38ac4a611ebd74a226ee9810fdd555c 3730 
fcitx5_0.0~git20200128.9e3bc8d+ds1-1.dsc
 b1910dd6c03c7e08826e83b9ccb0929ad5f4e570 2965796 
fcitx5_0.0~git20200128.9e3bc8d+ds1.orig.tar.gz
 2278a8a5339968a9df335a6931ea33df7805e74b 5888 
fcitx5_0.0~git20200128.9e3bc8d+ds1-1.debian.tar.xz
 2df3ea8f7c12a3690b919a02994058d2c927c2f3 22841 
fcitx5_0.0~git20200128.9e3bc8d+ds1-1_amd64.buildinfo
Checksums-Sha256:
 2fc5e063fb162df6f65e689d03b4653f9d7318595bdeaceda92a15a5b9812ec6 3730 
fcitx5_0.0~git20200128.9e3bc8d+ds1-1.dsc
 2931f1bb834741f9b9d5be5ef5931c70ab06b3adb742f5615e14f5fe78afa7ee 2965796 
fcitx5_0.0~git20200128.9e3bc8d+ds1.orig.tar.gz
 857f53973ee71929505f80cff7a5cde6ccd4f01df62930e3369e6b3f5937fb9f 5888 
fcitx5_0.0~git20200128.9e3bc8d+ds1-1.debian.tar.xz
 bd4efffeca89e4bcb520f066e41949bedadb38bfd0dd67c67c8e5e6b3905160a 22841 
fcitx5_0.0~git20200128.9e3bc8d+ds1-1_amd64.buildinfo
Files:
 7c02fd97fcbe49723c2759a40b8d7769 3730 utils optional 
fcitx5_0.0~git20200128.9e3bc8d+ds1-1.dsc
 89b1a3702e08ffb162c9403e99ee673a 2965796 utils optional 
fcitx5_0.0~git20200128.9e3bc8d+ds1.orig.tar.gz
 68cd1ef180c46ac53411bd37785ca35c 5888 utils optional 
fcitx5_0.0~git20200128.9e3bc8d+ds1-1.debian.tar.xz
 a3cf555e81610a1acbb34f1f8110d91c 22841 utils optional 
fcitx5_0.0~git20200128.9e3bc8d+ds1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl47Jz4ACgkQwpPntGGC
Ws7g0A/9E/jXxKkMMJJiZGzGZDgA0fpu0bDYUCqtu6NZC061PEbdRgGOW80kJ0sB
oRjHiRicXqSrfiYMU1JAws/QYrNXlvz3zrtCEW2rR1GkxuLSorzJjPGMY9XUg572
AejF8tJslUCbaAozSWZVXyRAYqIvgX4FIF1ycqmCAw6TfmIXGdHoULO9Kve1jcvq
AOxMVkCkeo+eDzF8s8A4iLaPJ+vst9nnsej/fcNB9xIgvZnu+uTtwg2oJ41AityW
GXVD17mgbXnlwQACrQGB3hhahUPLwY/vjjxvAzWqzEh8h82GkTj5QtMiOGsM4JU4
1A86YbFvv/8uUksVJi4BI1KaEIRBk1hSiLcsekQtOrZ0a9EX6pS1Vapl78dsxmdr
jAz9v/VVMEEDdde4ekPnC3M+azTLrRrKhNirlegf3nvn8lQOIAELA0Aquy7ZfyTk
866OxmlM8Z8KY7QcAxnD7FryQ8POJRG29a2xFa/wB2uY4uW0TM/lt0EndWTEvE5R
LMBFEvVl1xPmj0lUMyYF7cU/+ZyV6QQkmLy8VKzW+At8qygs61VPA6IWjIRsiez3
tppW7ADyUqtcrD3k++6psfWpLzUdq1IQ/PEO61EwzSjfYkKezxH0vo8gfMK+xCwn
3czPTyK2UTX6qoklAYX77znUUxoGJUUi0/UV6uA/k5aA3bF0ubQ=
=cYwj
-END PGP SIGNATURE-

Re: Heads up: persistent journal has been enabled in systemd

[Dmitry Smirnov]

On Wednesday, 5 February 2020 11:01:08 AM AEDT Scott Kitterman wrote:
> We just had a GR where the project voted it was just fine to systemd all
> the things, so this sort of thing is to be expected.

Are you suggesting that voters fully understood the implications?
Is this OK now to replace everything with systemd counterparts?

I certainly voted with considerations for _init_ system.

If I recall correctly, no GR option suggested to "use as much systemd 
components as possible" or I think the outcome of GR could have been 
different...

Anyway the big disadvantage of changing default is that now random Debian 
systems will have no traditional logging interface (rsyslog) and we're all 
will be forced to adapt to the new interface in the absence of old one on 
some systems...

-- 
Cheers,
 Dmitry Smirnov.

---

Believing is easier than thinking. Hence so many more believers than
thinkers.
-- Bruce Calvert


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

Accepted pyfai 0.19.0+dfsg1-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Feb 2020 15:35:39 +0100
Source: pyfai
Architecture: source
Version: 0.19.0+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Changes:
 pyfai (0.19.0+dfsg1-1) unstable; urgency=medium
 .
   [ Steffen Möller ]
   * Add new file with ref to conda
 .
   [ Picca Frédéric-Emmanuel ]
   * New upstream version 0.19.0+dfsg1
   * d/control: Used dh-sequence-python3.
   * d/patches: Refreshed
Checksums-Sha1:
 2416c2408a9b4b7749b94fab5983d0f604b5bf9f 3020 pyfai_0.19.0+dfsg1-1.dsc
 3e0b7f9e7c2b4ed9dd2380c48376b63fb6fa3983 27099228 
pyfai_0.19.0+dfsg1.orig.tar.xz
 579c9db97320bff0e20ac0fd0052a9777e4743c7 17104 
pyfai_0.19.0+dfsg1-1.debian.tar.xz
Checksums-Sha256:
 556fc13492a4509c6c7477afb512d061792202a9492ab5e9b6dbca3865452cd8 3020 
pyfai_0.19.0+dfsg1-1.dsc
 cc70297aef3c73ca64eceaba0cd8a1e9c0e0a87a4531bfc2810cf3aaa756ceab 27099228 
pyfai_0.19.0+dfsg1.orig.tar.xz
 e3106460b21bcdbc976d107a4109a34e329a26a2ac0204ef131a1f4ca3d72140 17104 
pyfai_0.19.0+dfsg1-1.debian.tar.xz
Files:
 fddf9edccb0119b920fa15f2f81c27c8 3020 science optional pyfai_0.19.0+dfsg1-1.dsc
 8c1d553da8f02a1e9758d2a4c57da953 27099228 science optional 
pyfai_0.19.0+dfsg1.orig.tar.xz
 e270f296ec9a884920f2a7d048f826bb 17104 science optional 
pyfai_0.19.0+dfsg1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAl47H7IRHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALt/mRAAlQMsQcpWQ2PyOv0G0+swkGrCEws9zJru
NxBgOijfes1vTrVEnmUdFJ5NK0dlEzA9ZnO61qcWUn93koUqtYhpqlx9EsZnLBFN
/OOB+K8N0/tXDGO5CgFk2hNVful/h0uZPbizRyqZ0iyniKcoVdrkdTf090tkZxFU
dILsBN1bu/9fnpZBk369h0+OrZsR0LSZHNCt9RBksKSy+BuR3nxwdOS+UDdGG1rM
TSm+n2xr+vOOOyxll+VrSDutwt0YoQQ7ZGGJ1AgFXTvzfdhUcmLUxMfyc9nlYlMJ
ulhy5aN6teqknJk6kkL5UevGJJY+5GE8O8yNSSInND0su9kG0Su1u9aLrnX/IAwL
z/pzsXATMeV9GDJazsi2j0q18nPdJv7VBu6c5RMDP00H+9QYVvtKqyZjvEqotl0J
dmU2TaCo90kBu3cRwqtayq4GvitrzcBnIAmf+VLtZCNx7Dz+iksBLpqR/3I0G189
U/yl61w61CmhmyFMInP7qNW63sTX/FnbIzLBW7uEwfVDosNF8aX4mz9ljig9jWo2
AVDwB3c30Kas/IYA1R9G8DjnVjyY6H3ftH6MpwGNiCCCtK0xUa402/veR1HdZIal
gCKS15RZQNusxT2sG0y8q/iIaU9TzqNN2raAJo8e9QXCt+vzyDIdtxbp6LyEn8xO
ccBoNEuysI0=
=zAed
-END PGP SIGNATURE-

Accepted pocl 1.4-6 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 20:55:06 +0100
Source: pocl
Architecture: source
Version: 1.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL Maintainers 
Changed-By: Andreas Beckmann 
Changes:
 pocl (1.4-6) unstable; urgency=medium
 .
   * Update symbols files.
   * Upload to unstable.
Checksums-Sha1:
 29d046d864020765d2f7f5933d2b3786d617257a 2369 pocl_1.4-6.dsc
 8b4025f67e5afc50f8a0001a001298f82fe66909 23256 pocl_1.4-6.debian.tar.xz
 c3ea5ec8f333ed1472398c0228a313304c44c286 8137 pocl_1.4-6_source.buildinfo
Checksums-Sha256:
 edcb946e078b8e234c3f42176e0a8552487ba73711c1b313b20f00976cbac108 2369 
pocl_1.4-6.dsc
 f406a7308211121c27950aa3c8f69e268b63be5b64288c177d3e8aca7fbb0e97 23256 
pocl_1.4-6.debian.tar.xz
 ccc9ff9c81759447183a805e271c38a0130e08599e755af079fab3c9d5c26388 8137 
pocl_1.4-6_source.buildinfo
Files:
 d42b4dc2080a286b11b1a2c2313aa428 2369 libs optional pocl_1.4-6.dsc
 051880816227e360d081e4cd9e4d1909 23256 libs optional pocl_1.4-6.debian.tar.xz
 bc5dc3f9e8fe8f7bfacec715d9a7401c 8137 libs optional pocl_1.4-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl47IeMQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCKpGD/9EiLqafisXFkM8Q6sS8iBYbTUQJJwKrLBp
J/tS/gxOZwRuliGX8zr92SyMtnZzpI306ea9h2dqn0uZHtcnFtioDqq44kumW5jl
FtjZlMyLzblDhGNGANTXwYIUAMAJih1gK7uiWNYhgZkFZwJr2bpZyKJ8YtRMG+CW
pZ6F6/xffzfV3Up5OtAi5JzxCcFZ+HmLclnOVn2enb11vFWufaZsZusZMl9nyrlb
nGilaaLuI9W6B2nbEfhW3xUBV/eKKCaSivMtyWA/oV+VDeOvQN6kx/HKikA2wBIZ
wOUymkqjTwX/VMoMgR9ZJDkObLZz22DEEr1nB46+R2biJlU44O0PmJrOc2bJZYP6
zfIhT7vrEx2Z0WdWMkx3qM617PDBr24RYy/6NI8Y3yVfm1UQRYk1+VmaZiI81yRV
yUmZEcwY2M3m//xfuKaq2Kju1pfQ8hX/NtFcM9gV63A6ky0sHdHnDerz6ZZcqaYY
h+X/b7xptE1ffGWbw+nFxfY7lBCCymRb1U9XcDGJ3T75pByRy6iwMNb/NcXpbgYC
DfBbZcEIuNgfig3lb7Wr0CX4yNxM9fUhVbjuOpB+6YLYUx69Us0v1sMwwZ6qVGZ8
W/ZE5Mk3nnxd17michzesIcV+9KguNiPY44cmJyYndPVoAgRzWzeVLWbeznDgUkN
/FQCp1A3IA==
=59PZ
-END PGP SIGNATURE-

Accepted nvidia-settings 440.59-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 20:51:36 +0100
Source: nvidia-settings
Architecture: source
Version: 440.59-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Changes:
 nvidia-settings (440.59-1) unstable; urgency=medium
 .
   * New upstream release 440.59.
 - Added a default filename when saving the Display Configuration file
   in nvidia-settings if an existing configuration file is not detected.
Checksums-Sha1:
 560d72c4eb514d8f2414a8166a58a77a7245c951 2475 nvidia-settings_440.59-1.dsc
 8a7f62637c9ff1f6f963f4c049cc15d81bed57c5 1128810 
nvidia-settings_440.59.orig.tar.bz2
 f7a4cfed4340704c70cf49b558641f5148eecc37 22848 
nvidia-settings_440.59-1.debian.tar.xz
 cab0af86124d04b4eefa11c687f7b264f0f66cab 13972 
nvidia-settings_440.59-1_source.buildinfo
Checksums-Sha256:
 616019d7fb1b34a5e57df9231534be3a94fb85b52229988eff638b9fc82c2b16 2475 
nvidia-settings_440.59-1.dsc
 53c7e90b6c630dea667cc158805b57b6e22de61e34010de30713459ea1f40474 1128810 
nvidia-settings_440.59.orig.tar.bz2
 5b35cee579933b894666ae0602908f74ae8b3fcdfad290333ce670b6eb74d68a 22848 
nvidia-settings_440.59-1.debian.tar.xz
 70dd4c44eb93835a497527ec083ed9a48a1bba30f24c3626b351a509fe21e72a 13972 
nvidia-settings_440.59-1_source.buildinfo
Files:
 794261832c17bcea90163895ee27f662 2475 x11 optional nvidia-settings_440.59-1.dsc
 755393454e1c6de7ebbdb8626ce0e45f 1128810 x11 optional 
nvidia-settings_440.59.orig.tar.bz2
 d210ddb9e9f10cda36e6c4bdb9b88196 22848 x11 optional 
nvidia-settings_440.59-1.debian.tar.xz
 7b35ead76606d43b4342961d909a15ca 13972 x11 optional 
nvidia-settings_440.59-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl47InIQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCF+TEACFxFfCD54L8kg2jXI07XlCbHUvzdfJKued
J2FA2dpUna2FzrnwMnaHDW5StFAlazp60OFzQbxCGm+U9E9XIb67+NvnCRtyTRgw
zo2J9TupPE2hbU5Vwo83Etb7WStuTz0VrxWq4kcBnsRHsrh/iohBPUPoTkN6Xwwd
Bzp3hSRHl2wK8bT55qKW9gO5E2wTN9gsZkbcpMfKPqsmDpNSfh5vt0NYVOhGWWUu
hWtWU7THIun9ML3ps1K9d/zBe7fEw6Wdy8noLLdbPDQU1GAukq8Jcx+s0Q+3k5Ze
zMTCXw7/gT2TNr1GKj387lwkczo+EHFnXYQCk43Bj2ZHML7gAokMQR/B1udYWgmf
P8gU7V4O1rNdobrKMeIqd2I3ZrUEhpzzcnllzo4MxQeZN3Pa0Twj17eYR3xXPpP/
JMoIqLAo2kQ5YC/BHq1KrPw6zwoGtQLLI8qU8QT4CH5d/uhCpzwsLbR3rHgLfxY/
GCNqiwiA8YD+prqFOxQmRhLd2KBinzle25VX14JrsAyzOrcIvZOBt/79K0zagYqB
bQ9JSdKXauZPs/tiVUoG2cn8R49znsADSbtWud/pLG6w3Q5YOsbPzUDNEM/uJOYC
vlRwXHcr9LufcPjB5vVVioPmc98hiY8aPr3rQgUO04WjRz5m/5jBppbky8yS9e/q
TlfmqHiR7A==
=dwWv
-END PGP SIGNATURE-

Accepted mda-lv2 1.2.4-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 20:58:18 +0100
Source: mda-lv2
Architecture: source
Version: 1.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dennis Braun 
Closes: 936998
Changes:
 mda-lv2 (1.2.4-1) unstable; urgency=medium
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat
   * d/copyright: Use https protocol in Format field
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Olivier Humbert ]
   * d/control: Update description
   * d/copyright:
 + Update source url
 + Use https protocol
 .
   [ Dennis Braun ]
   * New upstream release
   * No need to repack anymore
   * d/control:
 + Bump dh-compat to 12
 + Bump Standards-Version to 4.5.0
 + Build with gtk3 and python3 (Closes: #936998)
 + Use https protocol for homepage
 + Set RRR: no
 + Add me as uploader
   * d/copyright: Update year and add myself
   * Remove unused debian files
   * d/rules: Fix WAF variable
Checksums-Sha1:
 715aa4e4f0c41429d7241aa10af0238b143cebf8 2065 mda-lv2_1.2.4-1.dsc
 b83c1a03b2c07b6c7b1a430f6a83935e726a2754 2362219 mda-lv2_1.2.4.orig.tar.bz2
 4ca657e90255fccdf717d714ade94324f381e1c3 4600 mda-lv2_1.2.4-1.debian.tar.xz
Checksums-Sha256:
 a71b803eda4161577cc26e1324490cc4cb9c9d9727fb45811d1f84bd8a320f81 2065 
mda-lv2_1.2.4-1.dsc
 a81a00e19594881174526cd6ee7a3e301236e0ca25191982f5c9af5eb8d96ca8 2362219 
mda-lv2_1.2.4.orig.tar.bz2
 d467da1293a3cdc9aaafccb0a1585caf3d2b3b7ade2b5579bc0f31a6f35abb52 4600 
mda-lv2_1.2.4-1.debian.tar.xz
Files:
 b85169eb8cb3ef33bc3b876b91233e83 2065 sound optional mda-lv2_1.2.4-1.dsc
 57feb6b58b195f87f8b3e436f3b56076 2362219 sound optional 
mda-lv2_1.2.4.orig.tar.bz2
 02ea45edaf5e362c180cf80290d65b38 4600 sound optional 
mda-lv2_1.2.4-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl47HusACgkQafL8UW6n
GZP3dw/+ILjQGk3dZLkCycMo/k0bJv6ZmY3hZYImggDOVw35gHgsYMicNmZ3V55r
snTwdHHSXwF9bdXi0Gtrrsl6CoPbpb3ECWywUJ1/yw8pdp/Z31FHYS2Rp1AI1NtZ
TJUJnMrO2mpojaruSY/Bl9xbDHV6eXj+eKkrrstZNBIP5vw6yzUEwmBVhyixOMdp
w5kP0+zu3cW0leES9U6Wi5wkScvHFbRr4oHA5U2nCdrXY1LOaLAklE7ap0QP3HtX
++OV+gCj8gOd/wxL4PgiM6KJa2vECBRodE1ylz6oN+cOCrGdG53537gnj79h9TcR
rby/MQFv/qaxqksa/lGI/DsOnTKGx8Dss0q3r7MHTNI6CulDCnoCNbUhgH8aTu6p
gO7NP0nxlAQLEj+9Jh9CbBahta6aYIGoNvnTyHrQKM7tBm3Xw4WTdJIoRVkEylHe
zYbDY/mGDwzgF5/lldImR8qFAPyApa5mdEp7z2ym/YwMmYKS0UZU4Q4CHLyek42i
9uu2GnCF6OREoO4YOXG5LekWREx5XFyhz3iIhb5Dh6g92sh2QMQBxmZZyXxO9lTr
b9uRO8KCrQSrrQPQDUc+XUglEs0XXZ79jJh6yukPv97elKLuMcRqECzaYu3R8JDM
pIRRf7KGRdB0eMdenUaIdZgmCgaxyVHteOnlls75hkeP9hIRUpY=
=1rtA
-END PGP SIGNATURE-

Accepted jaaa 0.9.2-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 21:01:12 +0100
Source: jaaa
Architecture: source
Version: 0.9.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dennis Braun 
Changes:
 jaaa (0.9.2-1) unstable; urgency=medium
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Ondřej Nový ]
   * Use dh-compat instead of debian/compat
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
 .
   [ Olivier Humbert ]
   * d/*.desktop: Add French names and comments
   * d/copyright: Update year, http > https and add myself
   * http > https in d/control and d/watch
 .
   [ Dennis Braun ]
   * New upstream release
   * d/control:
 + Bump dh-compat to 12
 + Bump Standards-Version to 4.5.0
 + Add libfreetype6-dev and pkg-config to B-D
 + Set RRR: no
 + Add me as uploader
   * d/copyright: Update year & add myself
   * d/docs: Fix path for installation
   * d/jaaa.manpages: Fix path for installation
   * d/patches: Refresh patches, add pkgconf fix
   * d/rules:
 + Add prefix and pkgconf export
 + Fix man installation
   * d/source/local-options: Drop, obsolete
Checksums-Sha1:
 06d16465aff96eb0572e8f18360d03b8f9bc6346 2155 jaaa_0.9.2-1.dsc
 65b8ddc177e6f1b57687e824d5c8f8123c12c0b9 23839 jaaa_0.9.2.orig.tar.bz2
 40a3b6ade2f9edd4a946fb2c9dd479863c780448 9632 jaaa_0.9.2-1.debian.tar.xz
Checksums-Sha256:
 9720363a5f3315b8f4aae04c350b108cffe3fc0c06ea87bf819216c4b1093740 2155 
jaaa_0.9.2-1.dsc
 6cf55a3924694179d83e9d49f557896fcebdc1a7f89477e601caa2277ad7f3b3 23839 
jaaa_0.9.2.orig.tar.bz2
 9485de09710edcd6939c1f21f54562d3cb8123cba40e279057ceefa9d0d2712d 9632 
jaaa_0.9.2-1.debian.tar.xz
Files:
 e950bafa05e26d623f9dea4de94ce815 2155 sound optional jaaa_0.9.2-1.dsc
 02ceeda017e57635c64302e6271ad094 23839 sound optional jaaa_0.9.2.orig.tar.bz2
 c277f033514487318013739db9750df4 9632 sound optional jaaa_0.9.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl47H2cACgkQafL8UW6n
GZN2Hw/+KUzaA6/KEFBazY3OmzuG8sS9qdZLewNC5zZJXYZMrPsTigtvOu85AMv8
9DWOwrVCU/1QrrvsQTOwk9IlX/5N/ZciunDtyqYHuu+Ci1+1obG1ca3HhQkJ4/4t
uhJE1t7hTqno8CAiy4PGAxwB/kWz5WNRixihiKwX702Lw7K47K7+tzR1yz+dFnLk
rD2uZci7GJuqoAxF607Uu1Rfg8XmftIL2//PvOUWDOzIEDOohz3UJ/xHIvRfSnfW
bUqp+6+wtL+GRm3nWuRi9+MVfV+g/nxLzuhdgh26zNK0gWYX2XPJ7DgukNHzF7Yk
nDI05IAHW5A7cmFli46RR/LGU5Lbbz7SEwismE91WKA18gLE/e5NtonRAF6KAk/1
tzgiOiAqy9lLqBEav9Ei57yUP1L2s6tvviSSGdV40GY0jj9Ks8uKlHSR3m/SNkv0
ZDQFDBpMMEZmE6Sf/z4JkRXZkdfyDNPsK2GiDHQZGL0K1c7jDA/uhSQs2VmMgtuw
UmzFVYhhcwU8vHt+aC5RLPjJEfGb4GEChGsYzWCMnnRx+kcXzpJqvh1mbbb/BZ5n
QrTKs5kXCd5EhxSu/WA4Vn+BAY2I1QaU/S9/DCsRX1WUIcITXaHW7px5oLz4L6/c
rRIQ40GCmPcYc+WoKqgnp3FGZIlKsP13BjkZQF7bieTrZ8qLfOg=
=h7z7
-END PGP SIGNATURE-

Accepted japa 0.9.2-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 20:46:45 +0100
Source: japa
Architecture: source
Version: 0.9.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dennis Braun 
Changes:
 japa (0.9.2-1) unstable; urgency=medium
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Ondřej Nový ]
   * Use dh-compat instead of debian/compat
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
 .
   [ Olivier Humbert ]
   * d/*.desktop: Add French names and comments
   * d/copyright: Update year, http > https and add myself
   * d/watch: http > https
 .
   [ Dennis Braun ]
   * New upstream release
   * d/control:
 + Bump dh-compat to 12
 + Bump Standards-Version to 4.5.0
 + Add libfreetype6-dev and pkg-config to B-D
 + Set RRR: no
 + Add me as uploader
   * d/copyright: Update year & add myself
   * d/japa.manpages: Fix path for installation
   * d/patches: Refresh patch, add pkgconf fix
   * d/rules: Add prefix and pkgconf export
   * d/source/local-options: Drop, obsolete
Checksums-Sha1:
 5714f967d75bab092e2144603cb8906e2e129509 2131 japa_0.9.2-1.dsc
 f6badcb18f234c1c998048f3de21244f24aa6ac7 24594 japa_0.9.2.orig.tar.bz2
 629bae4c3843f6e2e866589264da9d00913dc8c7 5840 japa_0.9.2-1.debian.tar.xz
Checksums-Sha256:
 884ac84f918268f7dd7b19ed52cbcb1ee26d9b33290807e05bbd7bdb570637d5 2131 
japa_0.9.2-1.dsc
 2721824768c7a8a2df5f19a7a01986312f26cec2c31b38def59ac3211e27b1fe 24594 
japa_0.9.2.orig.tar.bz2
 3ed3e25c1cef8a37c807d68cd3fa65495f046f8b9f77219480d8673f4400a6ca 5840 
japa_0.9.2-1.debian.tar.xz
Files:
 31d08b25c39cb8a59a4f4daae5963174 2131 sound optional japa_0.9.2-1.dsc
 43287acd2511c6f9aeff7951b6e07d79 24594 sound optional japa_0.9.2.orig.tar.bz2
 dd1f237238a7ce7e76883040f4296d2f 5840 sound optional japa_0.9.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl47G+UACgkQafL8UW6n
GZNJuhAAsTersAwfS05ouAga7V5BxdXx/wn94m4Jd22pdgDhcHh9sG2WJgdOH85k
GTzMYBSRR5fwaeNLPv/ATv0GAqqBYevYegXtyenrhfxj2wqjWhDD3XUwcQHLXHO3
Ky0HHvAcBFp9JdgVkPZJ1ANrthLwMER80SuA1qObeqXlHKAn6tq/sKh7NbSYw++S
HZwRnVH940uHpETf0VDHmjCJOSoF4wi3wMocoEsZ6AmKnGjJt5XVLlf74ALOcgkv
gppRSIoY5dnHJWvQE6sjVVFYXLgX2LJG92KeZ0qrwnEGYqYhwEBLC4Es2537NWgM
SSQcmPoTNML3Ib7RVav6u8j+2SHQuUHhx5IEp+Up6x366lKWs/YKXDV7nWL08I5i
GUcLN+haFoUnuASoJNz14x4N6fnnEVhRyuTnmzxoheEb/fBeqeQA6GTyNwB48CkL
+C3cHtRv3qbRBcMBGyHFlLRM7fjvp80KhXkkw5SlRLloNKoPcdnH/zcfeaPJvtnj
OSj9TCIfp1KKpdNw7YR+pUzS7PM4JKi/jg6uaq5Bjjg2yb12uuqgyuNvaXnp3sKj
Zlh1nH/1RWeisMpawHDA1RBkBXWBV7WiPLOo2FNyW6VQnVNYlZ9iMhG14IPfLFGy
ERYftmAYjhWnqNVuFJ3rSUFqbDFqkEA+Wd5dVKSgcOgEU/Ngyt8=
=x4ZO
-END PGP SIGNATURE-

Re: Heads up: persistent journal has been enabled in systemd

[Nikolaus Rath]

On Feb 05 2020, Scott Kitterman  wrote:
> On February 5, 2020 12:35:45 PM UTC, Ansgar  wrote:
>>On Wed, 2020-02-05 at 07:44 +, Scott Kitterman wrote:
>>> Do syslog facilities really have to be addressed by number rather
>>than name?  That seems like a horrible interface.
>>
>>Currently yes.  There is an upstream bug asking for a way to specify
>>them by name[1], but nobody implemented it yet.
>>
>>I think a `--facility` option should be fairly easy to implement.  Just
>>adapt some code from the existing `--identifier` and `--priority`
>>options, there is already a method to translate facility names to
>>numbers (see calls to `log_facility_unshifted_from_string`).
>>
>>Ansgar
>>
>>  [1]: https://github.com/systemd/systemd/issues/9716
>
> Thanks.  That seems like a pretty basic feature.
>
> My impression so far is that the journalctl interface is a regression from 
> what we have
> now in every way I care about.

I would venture that for every user who is grateful that
/var/log/mail.log collects all the various mail-related logs, there is
another user that curses about non being able to separate (out of the
box) the logs from all the programs that consider themselves
mail-related, and another user who struggles to remember in which
logfile $DIFFICULT_TO_CLASSIFY_PROGRAM might be writing its logs. The
former use-case is well served by having the current set of logfiles,
the latter will be much happier with being able to use journalctl.

So this doesn't strike me as a strong argument in either direction.

Best,
-Nikolaus

-- 
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

Re: Salsa CI news

[Dmitry Smirnov]

On Tuesday, 26 February 2019 1:19:35 AM AEDT Inaki Malerba wrote:
> [0] https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md

Thank you for providing this useful service.

My big concern though is that primary gitlab-runner 12.7.0 (HEAD)
on salsa-runner.debian.net f0fdd533 is not DFSG compliant.

Frankly I don't understand why such issue is tolerated on official 
infrastructure.

Please use properly packaged gitlab-(ci-multi-)runner package.

-- 
Cheers,
 Dmitry Smirnov.

---

One of the best ways to achieve justice is to expose injustice.
-- Julian Assange


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

Re: Adding security features

[Nikolaus Rath]

On Feb 05 2020, Anthony DeRobertis  wrote:
> On February 5, 2020 9:49:36 AM UTC, Nikolaus Rath  wrote:
>>On Feb 04 2020, Anthony DeRobertis  wrote:
>>> Google has at some point had results from
>>> Gmail in the web search results (no idea if they currently do).
>>
>>Would you have a reference for this please?
>
> Here is a news report from when they were testing it:
>  
> https://www.pcworld.com/article/260600/google_tries_showing_gmail_emails_in_search_results.html
>  
>
> Not sure what came of it.

I think it's worth pointing out that this was an experimental feature
that users explicitly had to opt into. The original statement feels
misleading to me.

Best
-Nikolaus

-- 
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

Accepted intel-media-driver 19.4.0r+dfsg1-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 20:07:57 +0100
Source: intel-media-driver
Architecture: source
Version: 19.4.0r+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Changes:
 intel-media-driver (19.4.0r+dfsg1-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/copyright:
 - Remove more kernels
 - Bump copyright years
   * debian/control:
 - Bump libva-dev B-D
 - Use dh-sequence-libva
 - Bump Standards-Version
   * debian/: Remove notes about setting LIBVA_DRIVER
 libva >= 2.6 knows how to handle the driver.
Checksums-Sha1:
 b9bde1648fc561cdd52717cf3a9addf21d2baa64 2384 
intel-media-driver_19.4.0r+dfsg1-1.dsc
 ea54850b35572e374d2c82c83896056d6a64448a 5931192 
intel-media-driver_19.4.0r+dfsg1.orig.tar.xz
 67995b3837b12a82a771af8322ef9485cf2c759d 5536 
intel-media-driver_19.4.0r+dfsg1-1.debian.tar.xz
Checksums-Sha256:
 e354ff1ff15d8efebb33f16f82abde66b843363d809f5395fb810a8b0e59f114 2384 
intel-media-driver_19.4.0r+dfsg1-1.dsc
 d8f9d91710af37225cc11e12cbbea74d34ba84531a373c566050de7ed37da015 5931192 
intel-media-driver_19.4.0r+dfsg1.orig.tar.xz
 1f0d6c05ff553a3155df2ee24cf314b8ca4346108ccf420c440a677f0a9e330f 5536 
intel-media-driver_19.4.0r+dfsg1-1.debian.tar.xz
Files:
 5c59333a08a8bbda5cbb01a5b6b5f82a 2384 video optional 
intel-media-driver_19.4.0r+dfsg1-1.dsc
 6abcd5c9675b3006844646d501486114 5931192 video optional 
intel-media-driver_19.4.0r+dfsg1.orig.tar.xz
 685f0a3163f0bc421ce2f5cd35eca781 5536 video optional 
intel-media-driver_19.4.0r+dfsg1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl47FukACgkQafL8UW6n
GZPklBAAj0llsLlqpTYYqRm/AafsaWiYHm2wMbVrhIMdqcylUpzPY4AkY9sP5RbW
cT9oVE7yWElYjbl0ooNW3hlTMolMtQjoWjehCJDsXTTbzILGo7eRdJ2dxXtdnrdM
p7bOeJMTYK/EMpwHyR0Arpx5JdTIIt7foeWGhzIjAxlU2GE9EtXszlYUI+5CmxHg
FsiDNVXQjAwDhDCXYu6C1Y4GSZJCBHwBnMvL7SDrLxpOTsfELjSfKxvO4bVVRgOT
PDMvb0f2le/VbV/e8VKsevK1fdSF1F/QY6cNUcwOMIUer9h5gh2MjUj/EmwjELBy
166H0dINA+pL9xMdSDv5KDOzTArMnOtWihCpF4f4tyr3nu8V8D8beTJ2yfKwG4gW
MbxPEfzw7iH4imhchOoHvd9ocOui/z1/sf83A+3wE30ESB+frHOEIVmSf+GPLK2A
6yD5mjffYLEUmeCD9N2yGVJ5qBQQ+OHi+T5tljlERRhi1Rc++YLQsHhK3YbP6310
97+or1PlKx3rY8zaIvJtUZv2BQpooESKCv71tAiw2ciHpMV0ViuamaHvlD825VNP
HoyBKs6GdC3XVNH/oOAcggctQ8qPxS0FtN23XCfCU0fluzPm73pqfgOr1641yHCF
HAlbxgqsfCx3l9Nq56RmpdNsZhd1YV1OxX+dLEyM9qBn2sKBf8Q=
=Sdcy
-END PGP SIGNATURE-

Accepted fomp 1.2.0-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 20:37:48 +0100
Source: fomp
Architecture: source
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dennis Braun 
Closes: 943062
Changes:
 fomp (1.2.0-1) unstable; urgency=medium
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat
   * d/copyright: Use https protocol in Format field
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Dennis Braun ]
   * New upstream release
   * d/control:
 + Bump dh-compat to 12
 + Bump Standards-Version to 4.5.0
 + Build with python3 (Closes: #943062)
 + Use https protocol for homepage
 + Set RRR: no
 + Add me as uploader
   * d/copyright: Update year, http > https and add myself
   * d/rules:
 + Fix WAF variable
 + Clean up, remove get-orig-source
   * d/watch: Remove opts
Checksums-Sha1:
 bfaf3c2115438edf841c91fb3d7d6f2a54e1ac5d 1951 fomp_1.2.0-1.dsc
 03e73cad2fbcbd3a8a5219f16f8b5c11012e92eb 328933 fomp_1.2.0.orig.tar.bz2
 d8b606568847a82ef4d34f76fdc2939024979023 3192 fomp_1.2.0-1.debian.tar.xz
Checksums-Sha256:
 57ace95d980ba94f46a8c23fa0c2b922c367195e064b2f2fa7143eecfe6ac888 1951 
fomp_1.2.0-1.dsc
 1ce3172224937139dd729754059b063b973c71e59522a6f83771669ca5378d06 328933 
fomp_1.2.0.orig.tar.bz2
 80118e3c6bfc0a9f33426baaf48664ce19bfe32a685cfac932be074e48423b0e 3192 
fomp_1.2.0-1.debian.tar.xz
Files:
 5c0f16565cb5f7161c1e985222d8728d 1951 sound optional fomp_1.2.0-1.dsc
 5f9c52c5b954ddf37c7af7f31adcc0ff 328933 sound optional fomp_1.2.0.orig.tar.bz2
 6ff372c32aac22bc7b621e61e8572493 3192 sound optional fomp_1.2.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl47Gf0ACgkQafL8UW6n
GZMEGBAAqgrFk0ncVCsmXG5tu4P/S0YNlH4/EG+qjj7S5gzvU3Z35km6ZH/eUo0L
62kim78ImQRQ0rC7xgQSIfBK+cpfv5p1xKV44vfJIVot8H6d4Q+3M+lYgodqBCYD
deZy/JSHPTr6GCf7CcPTbY4/k4vAr499nsU6i65ZPZxpHLMbSXQoMnrAfIHERWof
KL3T02AyJrEF9m4Pe4IEWyjboez0W3pGBnuEGYFePzJPlCaJ8pu1IwoKii75z3Dt
jQO1Sban2wRNQhNZhFIUoAu3nc0IU2INGrJWMn/4a9dtgSPi4B8o/zmbvtPX7dhU
QIw2cDMcOF3kLXmypihbbTy0FKDVuJdjJhAB3AcC+9PtYtqagU2V3J/p3/pHRIxQ
xvHSLEgf5hjmxbwO3ehoSeDHu42RHOG8LuyX6Px4s6An/uVwArHr9FzMgYnw59T7
HIsj4zJ8500RZ59tMMBlxcpAO2+2uaxL4gmzT3Eaf291kYg9lMpZ7woF29/HPRhj
kj2OKqRRXC3qGr2IMOeC+GWPjfDTV7mog681eDVdJNi1YupbdDS2u8WCfIcQ90rh
QKhpG5wQWxOZ3koEOTjFlfQcE6IikddiFjEfBVHAHYFpkucRX9dDicwiiam3G3VI
WkcLdwYOSqpGG8hPeaitdtR/nZparoTDtWeSrS4yLvVKc+boU6Y=
=pD51
-END PGP SIGNATURE-

Accepted ruby-gettext 3.3.3-2 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 13:27:01 -0500
Source: ruby-gettext
Architecture: source
Version: 3.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Utkarsh Gupta 
Changes:
 ruby-gettext (3.3.3-2) unstable; urgency=medium
 .
   * Re-upload to unstable
Checksums-Sha1:
 1f9e40cf542c891b33fbc62c3846b717572cd245 2152 ruby-gettext_3.3.3-2.dsc
 14511dead7cafce9e8d91e0ac81e941ae0dd24a1 11564 
ruby-gettext_3.3.3-2.debian.tar.xz
 99dad637363d188701ad6c7d0bb0fd966e019c80 9425 
ruby-gettext_3.3.3-2_amd64.buildinfo
Checksums-Sha256:
 30c259034ae6b808ec044daaa705c71fcb107b14f70772f06274f031ff4a21d5 2152 
ruby-gettext_3.3.3-2.dsc
 e63247ac1e228e74e705d49253c04d0a06b9a8ae1671c9c987a1385fdb11cafa 11564 
ruby-gettext_3.3.3-2.debian.tar.xz
 40df9a869718ef9bfe834ad963b46542d24b5c14727e6af05b97cda2e0fa4856 9425 
ruby-gettext_3.3.3-2_amd64.buildinfo
Files:
 ea0e215c1f731fc947647e2d21d5bf6e 2152 ruby optional ruby-gettext_3.3.3-2.dsc
 8b479b282093b6af4d56a444159f3d47 11564 ruby optional 
ruby-gettext_3.3.3-2.debian.tar.xz
 e68f7c71eec614dbccf76552c755fa54 9425 ruby optional 
ruby-gettext_3.3.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl47CbkTHHV0a2Fyc2hA
ZGViaWFuLm9yZwAKCRCCPpZ2BsNLlmGxD/48T66iKKkjXDAQTFJwJ3ppcn3qXNT5
ozPDAANmKUn0Lhpkmzs1YadVn3bW0vGblurDtkbOGs79uHHxQL7vFK5GbYLmXq3i
eOAwPgVcmqYeaGuu42y43n8Bn4MqfEDys+td+lwcNnfXVzjNediXW/m4hcI2OooA
u+/r/klzvhk7W42V/8Bihy6E8hCXFv3lrE9lqauaGrVBxxkl7UpkYz83sCraZVN6
X7EEDYrIWuTDphfHJz6BpnGE6yTbbZX1cbKs2iP9p8/zt1plunnL+4DTDys1ddbt
VCXLxhZsEipjp2Uzl7wfrVMCkvVmWpnYBJ3DZo1Ny4EE7oPizrNoxZj1PdBmeQta
TzSBJCZJu+BG0pn5y1+dLRWNY478PxhsSa2K4wcs6Nl6ek2WtZsyIzq05mIAxu2B
m8ETDvu+NkbdyqLMHyQeBhG9woJWXhMQ7PGFUasu2CA5PRnE7hCzlmLtZDAiRKTW
ujYeYJNPQgv+8/5Howc/jaKGBVtw6KacDMUPHuSQBEP8fnAlsgkBNYNntXKxUVvF
VUnvWadhbbCIZfFaeRIFdZPANepSDPPJuj+j+cCiXL0hWcy3TFy+EbuvMqXEEBlX
7ghz+rHDzMrB7RsBesvzEdH3AvVIJ/SLb041qIOEUahm/04RMbQXfPGJHuB6Uooi
YPKgVLSdAvIQ5w==
=QiQT
-END PGP SIGNATURE-

Accepted date 1.2.39-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 12:22:22 -0600
Source: date
Architecture: source
Version: 1.2.39-1
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Changes:
 date (1.2.39-1) unstable; urgency=medium
 .
   * New upstream release
 .
   * debian/control: Set Build-Depends: to current R version
   * debian/control: Set Build-Depends: to 'debhelper (>= 10)'
   * debian/control: Set Standards-Version: to current version
   * debian/control: Add Vcs-Browser: and Vcs-Git:
   * debian/control: Switch from cdbs to dh-r
   * debian/rules: Idem
   * debian/compat: Increate to 10
   * debian/source/format: Added
Checksums-Sha1:
 fb3dba01f473abfe17b29a14b6388431e1de88be 1793 date_1.2.39-1.dsc
 df50c1709f26f5dc2b1fc814883b0b030b41f3e8 10429 date_1.2.39.orig.tar.gz
 20366e32ee38158b2ab433d66b388c83ce41 2636 date_1.2.39-1.debian.tar.xz
 ce1af67b3e0e58bcc2c56d812ba3bfec6f533777 8747 date_1.2.39-1_amd64.buildinfo
Checksums-Sha256:
 aff24e5ded4a6217f7d9d8c43317fbee21a9ded7c8485f3fc39606b3f9508c30 1793 
date_1.2.39-1.dsc
 b5b1935638b73373809c009f94b77f993cd301744488d9bdf71ef79c82099757 10429 
date_1.2.39.orig.tar.gz
 c8f959689d4ce9d9e9e09968641de80a01b993004b438c4bac08bb0b81a7d6eb 2636 
date_1.2.39-1.debian.tar.xz
 a96c88f9b5a62b104eb4b21fd149c565e8183529d87086e88ac670bcd8eda571 8747 
date_1.2.39-1_amd64.buildinfo
Files:
 af5ce3d232e242c5ccb3b9275b034886 1793 gnu-r optional date_1.2.39-1.dsc
 b02db6bda9481b17900aad129c9e7863 10429 gnu-r optional date_1.2.39.orig.tar.gz
 d08e8672572cf859a0d623df48fc6899 2636 gnu-r optional 
date_1.2.39-1.debian.tar.xz
 342d0822714f29e8fcfdf9fcb5165305 8747 gnu-r optional 
date_1.2.39-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIVAwUBXjsIr6FIn+KrmaIaAQjjGRAAm3326NuGIW9NQQsirFcdfNlGlLUzb9AN
IpjN753ujXSx1pWYiA47qhFT0EVwDWGpKYXxYR2wl4KcB99V3C+dejFKQcYbW0aq
0qFYYmTk3nmIN9gTS09fIeOGxz/yxuy+s6MMMem01J8PmC9QchcrONOJkkUPSvTW
8hCnlis3I/8kcfkB+/q/wlVoyejHMwdjKoJ8OlmFuIx6sOjolgrWd6wxWYNkPWhR
GLBygQNSjixTrSOBPRrEke8FLBbW4e0AZgo+rMP8bAJUeb9vsiRStioo761L9GJl
NV2fFI5b6ZeFKExl1e9K/IyIMI1yIbyd7oR2IPRtFr9Gz4ZrTywt3cZoS33tBBow
9YCR3sIOngCNAY+QQMjJHQjINbh4NyPPgESUpyb3zva+wsRbXToDhELZj44Sat8D
0fltVF/pXamAMmaNXRwY2ZgSEoiT7gncx1ZeVy7velVVO9ShTEbk6+LTfOLU99Ht
UUBR+K4TKTyH/Xr/05P8dXsSVXDagWqJNTDIhkDUn4OvuyMOofHzLUQ9axL8rGw6
Wyx6dCELlfW1tN8XR7DJNdzYfOvBolQU3qzMl23V124CG+pjHA5zFMMAyEevC/3T
RyGdYsIViyb7UHRvTPgpS0ifAu0VX8jbxMBoIm/J5HWkubX7RmG/ZaIX5LxMohc4
IH5AAOb6LGw=
=SglQ
-END PGP SIGNATURE-

Accepted libsereal-perl 4.011-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 19:07:26 +0100
Source: libsereal-perl
Architecture: source
Version: 4.011-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Changes:
 libsereal-perl (4.011-1) unstable; urgency=medium
 .
   * Import upstream version 4.011.
   * Update versioned (build) dependencies on libsereal-{de,en}coder-perl.
   * Use substvars for runtime dependency versions.
   * Update years of packaging copyright.
   * Declare compliance with Debian Policy 4.5.0.
   * Annotate test-only build dependencies with .
   * debian/watch: use uscan version 4.
Checksums-Sha1:
 181a425c7a4050ad6d8c255e2703aaf4d09bc905 2542 libsereal-perl_4.011-1.dsc
 985df57bbf6c78d30d4a5cf3398f909b0bebc251 195514 
libsereal-perl_4.011.orig.tar.gz
 642cd6d4a3dc05182af521fe6427ecd3b5cc473e 2552 
libsereal-perl_4.011-1.debian.tar.xz
Checksums-Sha256:
 bfc9a0cf7228af646bae99d5d432c281ac0a32e55ccb0422f3fb2f432b08473c 2542 
libsereal-perl_4.011-1.dsc
 5bb8a1c43f03cf0024fb53d866fb3bcbd741544ff0cc3a65f91e0c174d43 195514 
libsereal-perl_4.011.orig.tar.gz
 f320b31335eb0a6c1255000f651706540bb639c9559cafa6b4334db13658 2552 
libsereal-perl_4.011-1.debian.tar.xz
Files:
 e920cd180131982791ad6ed0bebf4abd 2542 perl optional libsereal-perl_4.011-1.dsc
 b9f371bf214dbf4f6464645d4af28397 195514 perl optional 
libsereal-perl_4.011.orig.tar.gz
 520e4ad5d8f222a67186e91788e0951e 2552 perl optional 
libsereal-perl_4.011-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl47BkhfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbTuw//ZtbQpP4YfsAIEVTBmLhQgzN19wpLqa/doX4xWejNDX6cRx74d2S8q6tb
xAQOPtLbHH04WcHS1r4SbiNuYy4Pc+8XvIMypCK6e5/mcpwfBB/CLlyP+2qe73wK
e9jKxRqRBnOqbZAfkfQwrgGjEHYE6hwbAM01Saf8aq4CbuBQ8JzEsJJQO1JDkzcI
GMKb/pZSBcn0G97rZaBwZZ5DUYEKhoRBC5fxW7SvwSSKv6UwFccsY1DSwLKc2TlV
Sml7YXrA3vmiw0Zesu6PUSPWIiUBtcLbawzwCyiG+TzjSCqO+jtK+HBRduNpkaFO
ISGCdIMfCae6vXDI9hM1JsmklmO3fZ0z99jjJMucPyj5FwqUFcNqCWXFQ4m05YiS
ons8ypMaZWe5Th7MO2iUQ0OQIKPT20HbEX1QIPjskGonAnXg6JrKa2jjoQmFFRFV
z+kWzRPO+yMFn9lpwKwdNXvaiALpyUU0JdyPqaMsN9MSjSEkWst3PJ3tj2RQub9h
0dxVBEbhDpfXYo+DJhCnSdO0t+jBciSfnC/Ulw6w1/txVsnIY+AgI6NuAJGsGoGW
ixV7gqusSJzk0BJ01F26uny0z+hVp8jvLKsF+eTx6qkKI1OVgPT+H1WBF2VofyVR
Ojo35Am6MwMTEl4kzMhHSJzW1Be4fgp3jGxnUx+Rh/zDuthXCnY=
=sHpy
-END PGP SIGNATURE-

Accepted ruby-gettext-setup 0.34-2 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 17:47:13 +
Source: ruby-gettext-setup
Architecture: source
Version: 0.34-2
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 

Changed-By: Georg Faerber 
Changes:
 ruby-gettext-setup (0.34-2) unstable; urgency=medium
 .
   * debian/patches:
 - Make dependency on ruby-gettext less strict in gemspec. Upstream
   recently changed this to declare that only ruby-gettext << 3.3.0 is
   acceptable, as more modern versions lack support for Ruby << 2.5. That
   is not of concern to us at this point in time, as we are already
   transitioning to Ruby 2.7.
Checksums-Sha1:
 55c1de3468e833f1d4af958c11d5bd77b734e027 1714 ruby-gettext-setup_0.34-2.dsc
 2acdc8be9cdc6eee0c03bb8a56cfb3ccdb714a3d 4260 
ruby-gettext-setup_0.34-2.debian.tar.xz
 1f6602f08932ddcfff410d746a69f8b7bbf8df47 9269 
ruby-gettext-setup_0.34-2_amd64.buildinfo
Checksums-Sha256:
 1edcdf8798a9915de4b980bc689b778757ea141d269c612aae8f2fe27892a003 1714 
ruby-gettext-setup_0.34-2.dsc
 569ed0044e6a0ee710cd8e6507116c3efe83afca86c6b9bcb439b223b969361a 4260 
ruby-gettext-setup_0.34-2.debian.tar.xz
 d1df749fe469b85140b20641c9387b8388c7d8c02b5119c014c9351b68e869d2 9269 
ruby-gettext-setup_0.34-2_amd64.buildinfo
Files:
 29c8eb86d333bf5f61b6e06b7b204f5d 1714 ruby optional 
ruby-gettext-setup_0.34-2.dsc
 7c9497748c283782c7e9d91c5295eafe 4260 ruby optional 
ruby-gettext-setup_0.34-2.debian.tar.xz
 40f3475cf322cd3b140d68111ca62291 9269 ruby optional 
ruby-gettext-setup_0.34-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQTEfr/MTlfp/DLKNABGG+5dJAqekQUCXjsDtQAKCRBGG+5dJAqe
kZq4AP9o7+LUBxEXV0BsLlw0o1s1FBQ4Py4c+CFG4CM0J2LtzgD/eGCl6YANbYaG
p/AHjHyW7Snlj+K6/lWyCHfTRWEDOgc=
=RsSI
-END PGP SIGNATURE-

Accepted stk 4.6.1+dfsg-3 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 18:57:28 +0100
Source: stk
Architecture: source
Version: 4.6.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Changes:
 stk (4.6.1+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
   * Upload to unstable
Checksums-Sha1:
 8748db9dd58b806374722d187d3baf85ac118560 2364 stk_4.6.1+dfsg-3.dsc
 8dd7dd492e3483e411e5997b96dfad6c1f9e4926 12612 stk_4.6.1+dfsg-3.debian.tar.xz
Checksums-Sha256:
 4346ceb31a76542a7d132cdcb81c11f40db8e753e1c9ebf729ea62d9ac5cb200 2364 
stk_4.6.1+dfsg-3.dsc
 47d8b30da5fb44ea03ba3f64712315c671dcee5e3c8fe0222f095ae5b42a3664 12612 
stk_4.6.1+dfsg-3.debian.tar.xz
Files:
 01b8525537df72769ae64e82a9eca290 2364 sound optional stk_4.6.1+dfsg-3.dsc
 40c32c27980b9d57adca148993d346aa 12612 sound optional 
stk_4.6.1+dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl47Ao0ACgkQafL8UW6n
GZMOgQ//XwlfpoYNyhoJxSE7+Zht/F52HTY95ROLmmzfXt/ooKpPXROb3Uvf/puV
y8RRjv9mVxNq7rbnAybNDAlWMZAaSd9f2mDAI3NLP83h1QvV0STd5EJT6fUrPVUm
WrkP7Fo97b0KDh4c1dN0/B9ebWt4nyfFAWuQWXBe1YHArsFz5QooaDI7BmCVC50i
XOdw7ojIRGH4VmBqo5Fdc7a00DP2MsJNBhI90XK/+DZjlhe0h7FTzv2kc4qLSIAM
3yQgNxnjaiJJwZVps+ijAjd9W/Syt6XyvujND1G4Wz8y/CHnrfiAPO+ZG9j/N2L+
banEQlcCkA3rnbkOFAvSR0XfhYk8a6CuduLraebtzDEoNn5rvXn1CTN/8CCae6Dt
RfstJVQBfWzH0iGBn2NwWqz88YbonIq44dXOVZyFste+epOYw+Erx+ZP3WtJcGey
HAxBA+mvZQtQ+qqr/f+9ldQHPrhKbnmiwKbd6qB5sKK4xYiQu/UxCx2bSUIgFqAB
Lp9stkvfq8vlSNBn9/lQGCn3Oj83mvNZAglW+scrxZ2mXOjUjrU+q3ozMJ9ORiWp
b7NoA2AEK7sMUUHoZF60sNDfT3QVz8Y7myR58bZG7geEStv/NKfp4VVTqS04K6E3
1HUsSpxRUIKLEnFr/WOcPr4o4MvHRBDVKqG+ljzYzVMsuybvmUQ=
=+kI6
-END PGP SIGNATURE-

Accepted packit 1.7-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 14:40:04 -0300
Source: packit
Architecture: source
Version: 1.7-1
Distribution: unstable
Urgency: medium
Maintainer: Joao Eriberto Mota Filho 
Changed-By: Joao Eriberto Mota Filho 
Closes: 287666
Changes:
 packit (1.7-1) unstable; urgency=medium
 .
   * New upstream version 1.7. (Closes: #287666)
   * debian/control:
   - Added 'Rules-Requires-Root: no' to source stanza.
   - Bumped Standards-Version to 4.5.0.
   * debian/copyright:
   - Added new rights for upstream.
   - Updated packaging and upstream copyright years.
   * debian/salsa-ci.yml: added to provide CI tests for Salsa.
Checksums-Sha1:
 f53ba873edc68031f8178220054db08de912d39e 1915 packit_1.7-1.dsc
 876cc321a2beaed8da0226c980618bfab0eb5a58 53192 packit_1.7.orig.tar.gz
 7c5ab54d995644d2ff0a508bb2ac2771b7f71e03 5368 packit_1.7-1.debian.tar.xz
 11dfa283be16326ca94faf6eb5709a10be9925cf 5352 packit_1.7-1_source.buildinfo
Checksums-Sha256:
 bc33b6636f1ce7230170361d71fb4fe381c3515bdfc241c5c2f38aa94a5f1cef 1915 
packit_1.7-1.dsc
 b40540bed3b8a2bdfd63d750ff5989b66096c93d54ffec4c03f35812582ea4ad 53192 
packit_1.7.orig.tar.gz
 3d329eb2b0ed75a80d4a02f577d5d11bd0f59bb4e905145d3d874522b51ec701 5368 
packit_1.7-1.debian.tar.xz
 df15ee73e0a5461f94ea4da02bd74ca19e6664299d2947ed7102ab582eabfdc9 5352 
packit_1.7-1_source.buildinfo
Files:
 deb16124826e45089c1d852a64a27e60 1915 net optional packit_1.7-1.dsc
 939180fe056d392d7f1e6165c971123c 53192 net optional packit_1.7.orig.tar.gz
 829cc3596530c25a5a2f84bf5ee3c896 5368 net optional packit_1.7-1.debian.tar.xz
 f6327d115c718d9af0d201bd044b0ec8 5352 net optional 
packit_1.7-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl47AHAACgkQ3mO5xwTr
6e/vSA/7BFxuv3GsFuQxulaVx2DstCwjNv3plN1x1qKgg6dSIazgpKBCmvY4yTpm
mA9JUY5YYswu2iaplh3o8nQ6zm64odCydXLo8Q9wRrKQtY17LOmqsth1bCEu7WB+
uYb3dqXCwJDYUiXv6L0BJ5YdhCdrpRRh4J7mJ+wtoQIpL+fVckHJiGgUMdghE4RZ
Zj1UYOTeCaGMUSMAUp5aKyjwhly4NgVucYy5XjFIJtVnBgDwlleR9kflo6Eq9o4i
lC6Nz0PD8H2/klC+ecORnJ/UJTeXN18eQmRhGIotELUL1rGZHSk291B2G4GACCx5
ddMZPMJyHe1TLXqQ9vt7MZHoVZaDyOx4umL7V5/ixKQjWvJbeKm9qCstWRxRWRPI
UPamceXbnaBw+6XFxZo/tOw6LDbC0J8c6RxVxAeXgG339/kVThRf9DqBNyIVTj6G
1NbXUyBSpSs2jaXTi2tvX7VMX/f0iSpGCXThMOBNSU3MrPRPL7F5+mVEJViFNs4B
2/N54SulwCpC+TLKv7yqYhB4yD82j6QZpc8m1GSDxSz7Werh/RX5uhC+nNbeae0i
ni0qQISACa2dEQ5n2ZZF1zcinYuDnGMK9IyyJWCqLipoMqIBhw4oi/Bv7nAXnyb9
jkIqRq1NjNX5LHJwVy0p48HyD5sZD+lOccx1oaUWOwXNtV0R90s=
=O1uU
-END PGP SIGNATURE-

Accepted ruby-rbtrace 0.4.11-2 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 12:20:57 -0500
Source: ruby-rbtrace
Architecture: source
Version: 0.4.11-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Utkarsh Gupta 
Changes:
 ruby-rbtrace (0.4.11-2) unstable; urgency=medium
 .
   * Re-upload to unstable
Checksums-Sha1:
 290d5c7b453f119fb97bb1f3c5e4e2639f80678e 2150 ruby-rbtrace_0.4.11-2.dsc
 227e1f3ca8448039d35269107bb24d47d9bdc34b 2052 
ruby-rbtrace_0.4.11-2.debian.tar.xz
 968c9f6bb9700257a4349fc8f690ad80b0c5efae 9623 
ruby-rbtrace_0.4.11-2_amd64.buildinfo
Checksums-Sha256:
 7161a43f27e09f225db06a68234f91be0cd6d5b11b93a159360dc8e9381ff3a0 2150 
ruby-rbtrace_0.4.11-2.dsc
 f3ee9b06641f354bab5d69c537d95450495f17d6f91591607c3206996ec02a5e 2052 
ruby-rbtrace_0.4.11-2.debian.tar.xz
 77e4085a23212883e871b3beb4b558c9e098712c235290398b901fbe59eb79b0 9623 
ruby-rbtrace_0.4.11-2_amd64.buildinfo
Files:
 02427f77a921967044f61900c47f89dc 2150 ruby optional ruby-rbtrace_0.4.11-2.dsc
 baaf40306ce6d41e7605ce5ab6e5f6c0 2052 ruby optional 
ruby-rbtrace_0.4.11-2.debian.tar.xz
 71915c1a4d81874c58b80bab9956ce1b 9623 ruby optional 
ruby-rbtrace_0.4.11-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl46/TITHHV0a2Fyc2hA
ZGViaWFuLm9yZwAKCRCCPpZ2BsNLlkCBEAChOqYjH3PIC65btcimlBO/gnqaXYVM
29SZb1MMJlvKCAPR4P2fpGXGYReVbIhj7TVrijFmtzwOjzOsaXXljTjMNGlNiLwr
jPLuCFz7PV47zMM4oVdhne+CxIi+NXGobqUePxd20c81nMx/M3nDtYTifrZHOwP+
oCrI3K92F/mhUJP923fg171Pir5TXDazYzAM0G9Utt8x3TDpwagTlgEZHDWNHwLV
IOpAIMUVMGdbGw4nIoz0ddkCoB3AN+H96eoEcq5i77+WkAW/AusDcbKYSbK2P6oE
hfAOpsCAsQ95Q2XMZqNVCadEq82YSk3i325CaEbPbcW/Xhtz9s+uj0Tvlt6fvjnm
4lfAPvfstn+7uUkq7xZg98d5mm8s5w5NsVrEYcpXGE1EIs5+KQuI5v6erOBoIRyK
vBCwGZVdMawKGEdj5LV4f5CwjJModUA5hfmpKJY16UYQOFjM2e5g7LXUMnbgo+Cg
O5GGo6rfBiSzj3btyDya/bsjAzCKmI4GApmASnlmtp0AKZ2ptaZpHrW9UzcLVB1/
72aCWvPAehUc5stWWIKaVOhGAUOM9xZsAQ7//xZ4e1bYsXyIax7BBvza68vgPD6x
Q5EajwhcEQYEaoYkjRE2C2n6KY2Sewk1rbLl/H7I50HLJwlCCTLWWx1+krbbCkP8
GYyKG5J+pQ/11Q==
=AoAq
-END PGP SIGNATURE-

Accepted libclc 0.2.0+git20190827-4 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 18:58:46 +0200
Source: libclc
Architecture: source
Version: 0.2.0+git20190827-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL team 
Changed-By: Timo Aaltonen 
Closes: 950032
Changes:
 libclc (0.2.0+git20190827-4) unstable; urgency=medium
 .
   * use-python3.diff: Updated to fix new issues. (Closes: #950032)
Checksums-Sha1:
 4841c6939e124f58ae2bd05d5b84fdefa4501b72 2253 libclc_0.2.0+git20190827-4.dsc
 c7e3d2d89e3073376b10697d2cbfd8be7be48f17 4988 
libclc_0.2.0+git20190827-4.debian.tar.xz
 3bde7ef33f9c9861ff3533400ed9d0aed7114127 6893 
libclc_0.2.0+git20190827-4_source.buildinfo
Checksums-Sha256:
 76c4276ae1c5e1940cd8c2b7a17dcfa4bfdbc0fd78e8d955b6b9acb4f8b046ad 2253 
libclc_0.2.0+git20190827-4.dsc
 3769e70e9f931623046bf6d20c34ab9c056936986b309a712d7b9649f617ed65 4988 
libclc_0.2.0+git20190827-4.debian.tar.xz
 177ae6bff02ce5c76bcfbd5ef615a5f7b9253b5e4d017d1176e4aeb2a8c3f73d 6893 
libclc_0.2.0+git20190827-4_source.buildinfo
Files:
 e4ab729df465d2d44deccaed4257477f 2253 libs optional 
libclc_0.2.0+git20190827-4.dsc
 e3432511e96dfdcd4da5efa8c2501197 4988 libs optional 
libclc_0.2.0+git20190827-4.debian.tar.xz
 91a73055399c7b12e0b857a44ea99637 6893 libs optional 
libclc_0.2.0+git20190827-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl469FIACgkQy3AxZaiJ
hNzj6xAAoHpLRImGl+077DEL6ZpOHtBET55KUOkAGFsb5M1BrKp7LZxpswxVREiq
0Gtd7B/qasLjM7qxSBN0rYM/IpPcsaUtc4uG/v4jZK0UjVwv5967okvBhNgpC5Uz
jkmdIvHr4TLdKIio+RXZksN8B0aaJC4eDCInMJJ/4oHDWCqo5bzCxicbcJJzbmA4
u7/UNhw/G8dTZbvdCFZxC0+ypz27p+woG/D1E1jpTZSz7nK/Ahrgmty4qy1fV/iC
R5hVHjB/ehO3FW7IbOpHjrvJU5MXm2aTwIq6I4jToHhpzEBv/qYGppzHHdggVg4H
6QAmbDZlqF0CiPBG2Q8OuuxfoS8ibrJ4U7EUi+Bop/p7lBCu758xW/5GEhZnB012
+/HTTxTmlBCg9Qt/Dm7PfSXTqLF4RX4cQZWQEdNrzK4UjYDdaRkbWGsJYcgutwvj
iOGUciwh2+CSEI3qheC7dhYyEZMT50ekiIbrVZ5D5usdOTHUO7kaHd6Rt8k8F1/e
njKeZaL2CeuY+ekBzcWJBfQjXNl/oFwY+8da8JsVA8pbODZdkaPTAUcsolbuU/Iy
Bt5E/K3hcVsxxoHWPUE3tvCGhm1Ko1x3v2cOWxo/TPS4j+x9X9rPH6rDqiozI85k
ij86wCpks1ZFY1eEry6SDplIZkDMVqwO5SdviXRKjUzXMRw6bFM=
=68mi
-END PGP SIGNATURE-

Re: Adding security features

[Anthony DeRobertis]

On February 5, 2020 9:49:36 AM UTC, Nikolaus Rath  wrote:
>On Feb 04 2020, Anthony DeRobertis  wrote:
>> Google has at some point had results from
>> Gmail in the web search results (no idea if they currently do).
>
>Would you have a reference for this please?

Here is a news report from when they were testing it:
 
https://www.pcworld.com/article/260600/google_tries_showing_gmail_emails_in_search_results.html
 

Not sure what came of it.

Accepted puma 3.12.0-3 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 18:20:58 +0100
Source: puma
Architecture: source
Version: 3.12.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Daniel Leidert 
Changes:
 puma (3.12.0-3) unstable; urgency=medium
 .
   * Team upload.
   * d/compat: Remove obsolete file.
   * d/control: Add Rules-Requires-Root field.
 (Build-Depends): Use debhelper-compat.
 (Standards-Version): Bump to 4.5.0.
 (Depends): Drop ruby-interpreter.
   * d/copyright (Format): Fix insecure-copyright-format-uri and add myself.
   * d/puma.1, d/pumactl.1: Add manual pages.
   * d/puma.manpages: Install manual pages.
   * d/ruby-tests.rake: Set verbose mode.
   * d/patches/0010-fix-cluster-exit-for-ruby27.patch: Add patch.
 - Fix hang with Ruby >= 2.6 when shutting down workers.
   * d/patches/series: Enable new patch.
   * d/upstream/metadata: Add metadata.
Checksums-Sha1:
 55eb2659c2faf73f4bbc0ca68930bfbfe348b957 1960 puma_3.12.0-3.dsc
 06532783d5deab3ceab1947bfcd48c7ac7127b3e 10536 puma_3.12.0-3.debian.tar.xz
 e39fd11eaa2fc8c2720d7012e5e7038d0418c94b 8912 puma_3.12.0-3_amd64.buildinfo
Checksums-Sha256:
 d01c6b086897f8e095e1161f6221ca7df713bb42920df002328dcefb1cf0a2fa 1960 
puma_3.12.0-3.dsc
 f6b3e0f85b634f73c6aafd3c0bed80c4fbaaa17a66c3bd6b259bb5b3dc122642 10536 
puma_3.12.0-3.debian.tar.xz
 5d6db48962d6ea69cec3a6b1b466fbab195d1a89af0b941602f5a93c982f2fc2 8912 
puma_3.12.0-3_amd64.buildinfo
Files:
 9416973480ae94c20ba5b8436aafaa03 1960 ruby optional puma_3.12.0-3.dsc
 d7c0767af32d2c62ef654199bfc54c92 10536 ruby optional 
puma_3.12.0-3.debian.tar.xz
 62a34c694813f1a50ff080aab2a9a0b7 8912 ruby optional 
puma_3.12.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl46+rYACgkQS80FZ8KW
0F2Njg//RnNok+I6JX0zWqazK2xAocUUSO/n4qgt7KCZoux65ZLmq5ePkyUhEEh5
WehqchAaGhP0xRs4nf/eDYu6HLHsp7eD8Uuaz7aKEXO8f/YPVfDbsF6vVmuTBg+m
CSVdhs+LyVlkkmIbesl8SlHzYSVWCrypr1jEpoHrfqQtGTLXsY9S12yrWxibR6S/
Xo0hTxd/LQOutRsyeYDV+2mayapXx2uloW6Nn8czvtTR1Cye92w3jZlgHoki2KH8
TJo6G78R2Q9QPpL4j/JkuYUQRB4ksyqIzvRXwbJNMP8KKZbwVubeQj7KTShHPFqP
UJ39rQ5nC+9Vopv6kzK0ZlKk91xGxopnaXdtIKpP7f8FlIRgwTKJfAoh/99xSdJ+
OeoukGzDKAvUW4N4h1aAWa3b5VYdrFz6i9IZb524fX0lgcv+DbqJglUa61vZi1ZC
APE7QdzFUbTHkPc1j4AM4597u4XUrpheQSa8hvFhwTXnbxs/XHKowb0A699pRUeB
/Z5IXaai1oZVLpSqoq6FkZC2Zsosi2gx3vViRbWdW50zinLBzOmrODl9B3sSVV9M
PUssT25/NUEIO+ytnDfYY6TZ1bND1vLFnRMi0E0ewmRd851EucJQdsyR7a9UWzRs
bWoHspsZjXQy1LDCbJaZAKa4YwA0tfD9TTZez0aPxkGwr6OHdbg=
=tcBO
-END PGP SIGNATURE-

Accepted libxcb 1.13.1-4 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 19:27:55 +0200
Source: libxcb
Architecture: source
Version: 1.13.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 947499
Changes:
 libxcb (1.13.1-4) unstable; urgency=medium
 .
   * control: Add libxcb-xfixes0-dev to libxcb-xinput-dev Depends.
 (Closes: #947499)
Checksums-Sha1:
 b9c78bdbe09ccb2c268af98265cecaa4f834c256 5352 libxcb_1.13.1-4.dsc
 23b5df1eeb0b4d85762edd521bf41096c655a140 25493 libxcb_1.13.1-4.diff.gz
 0c23ca6525b63a14c232c3048c9c94101170c32b 7940 libxcb_1.13.1-4_source.buildinfo
Checksums-Sha256:
 f88afe42923180c505b410cea42ace6cf4b5a09023154934ee6fe3d62130b89e 5352 
libxcb_1.13.1-4.dsc
 15f018a872e5b557ecfac48e1fc8ea759051a7d11170a825d6e63d8bc17a5935 25493 
libxcb_1.13.1-4.diff.gz
 60cec765d1f9af877299459d705b94d6af9907bbf91e22f204e4d0fb827d14c2 7940 
libxcb_1.13.1-4_source.buildinfo
Files:
 11900b8f7b932af99595f0ce01130bb9 5352 libdevel optional libxcb_1.13.1-4.dsc
 61c4b37e98d8146beedb7495ee73d31f 25493 libdevel optional 
libxcb_1.13.1-4.diff.gz
 678c2c75f4461c64d8a4ee9274a2ee72 7940 libdevel optional 
libxcb_1.13.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl46/OoACgkQy3AxZaiJ
hNwOSA//d0TM3QodSkJvAwbJBln4b9r8BjunrGiEEDH2dK5YELoSjk3jDqiekbZM
IGSrRkBaLx8t86XseeqgG2CrdqQpAXnnD9T9zNV1+MpXg6hGOyPrh0l1HkXM6oYC
dizN2LoKA44LEIJ3GubFBQvEIROjpHohhzj/M1dRUGGBKSRroYO4NjIKpKXF4ChP
lJMcoYgF9CDJoYklyyBBJwSx4dCMBjJBuqmYex3p6rQ4MHf3EjOxEe5QnFt6DA2Y
hY6/oYQSYaUeQo0VGR+/+n4JS6l1Gqg8QkJgOwLva1Y57DmJJkEDhzMOG/yFusSz
qapJgB1TMmRr5fzG9/gB+U3N6BlyFDD6fz2wZyZBO9R23CMoaR8i8agxcrDsbIss
I3CzjCekykfBAPEw4aMiI6a1EJeUkBXi0uFTn1RuepcpwIaPqmMHzn8Xr3s34Gx+
67jMhX3kMMLTFJ7U1lgX81wi66InoCLfQogN6htLJKg3SuuN7LLidvOCC5fpKK5v
goI1ZG6TGgKW/qakoom5SgspCk7LUdqDorzYou60jm/ytlgnQynxuJeWaMRr4He5
2uDAiggE+P9I1PbSgFAcVzdjDLmXFSG+ELoscZLvlk/rVveA1M2/92SR+3HxYVJV
lMkI+jqzAYsM9lYQ1seEaV9gT458lU+wzejmH8SsCE5QBCXe5Ps=
=V59T
-END PGP SIGNATURE-

Accepted sbuild 0.79.0-1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 17:41:38 +0100
Source: sbuild
Architecture: source
Version: 0.79.0-1
Distribution: unstable
Urgency: medium
Maintainer: sbuild maintainers 
Changed-By: Ivo De Decker 
Closes: 774856 920335 921675 922148 928366 933723 934721
Changes:
 sbuild (0.79.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
   * remove debian/patches (have been applied upstream)
   * add buildd depends on devscripts and recommends on sudo (closes: #920335,
 #774856)
   * debian/tests/build-procenv: don't install packages from a different distro
 (closes: #928366)
   * pass the right .changes file to lintian (closes: #934721)
   * sbuild-createchroot: use umask 0022 (closes: #921675)
   * fix etc/sbuild-debian-developer-setup-update-all (closes: #922148)
   * add apt_keep_downloaded_packages option (closes: #933723)
   * add option --dpkg-file-suffix
Checksums-Sha1:
 8ecde2bfb970d193862d8bb7e286ea06ffa2e584 2488 sbuild_0.79.0-1.dsc
 481c408d6235aa24467b2ae4c7bca797b32c9896 201208 sbuild_0.79.0.orig.tar.xz
 e36d909fbf31f10630b6c6357bb222c2c3b56589 51200 sbuild_0.79.0-1.debian.tar.xz
 ab74276411bb1c431d5fd8acd15db0353df6d8df 5341 sbuild_0.79.0-1_source.buildinfo
Checksums-Sha256:
 c0aa47346ab6dd7890ddb316f3a6cde042605ee28c8d266d145a64b7f356dc26 2488 
sbuild_0.79.0-1.dsc
 f1cefc86954abd6f68ced1c20ec705fa84b8900f3cda8c28a5855914f8c1559c 201208 
sbuild_0.79.0.orig.tar.xz
 0dc4364fc0c5d0dfd076ea11a9832fa202019db02ab3ff41919884f6df915b3c 51200 
sbuild_0.79.0-1.debian.tar.xz
 36fba0fff201debdfb2240d0c3c2addfad465adbd70a7a6251a57b85959e2b33 5341 
sbuild_0.79.0-1_source.buildinfo
Files:
 ffc2bd97aeca45371855f981bc8e1fee 2488 devel optional sbuild_0.79.0-1.dsc
 e88bf68dc37637e77beb2f6ec1ecea3a 201208 devel optional 
sbuild_0.79.0.orig.tar.xz
 5616cbdedcac0d74168af295da440c29 51200 devel optional 
sbuild_0.79.0-1.debian.tar.xz
 c4b133a27363c253f7567e0d2d612e19 5341 devel optional 
sbuild_0.79.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEE9GM4QTXwpzdLbkGwrEC7WJcE6vwFAl4698cWHGl2by5kZWRl
Y2tlckB1Z2VudC5iZQAKCRCsQLtYlwTq/KakD/4z0Mh+0t+taNPoDpgNULrYFrbm
BCtqwDrsi/ddEYz+T/j9+pn9AkkkeQtdQlBxheAeeHoXwKFOInqQJAjI6ntpAB/H
oPhDh6pxfrwv8M/gjrMAf6cpgO3hGE5BaZzW7/Gd1QDC8Jz4toZ4fu+qmlLNeOND
Z0thmYNP1PGVUeamPI4buGy7WHumGPwr4tzeg513VK9diQ3Ge6Z2YFItamjb0nQS
DziMWpMruBpix40gWOHr9m8MbzG3vsF6c7kFTUea4dE1e8EdxAMY2o55X06NIXGf
sICOnADNKey6aTAKntWOCjZMiIJxRpvwc4AiDbR6eP4jq0TMF7AhIqK84lVX2PY3
s6zPLS8ORqUM6DPflwn8QO8YTrqviPgO6IY63QFgAqm4edagjLunyw7FfAUveyEP
+epdj2VPa3K089O7lEvtTgQczo7GBJkXwvJm27I3GzKG5R+Ob+mvHUiIM9Xuyx9m
cUswjFohGNB2ASDuTERmvlW7BoA3Cmj6o+s4rXjou6jPN+pp+c2TdNh6AmxuuJEN
FGSVcInDo5aNRKRnGrYnX8GNeZ24wxfDaDZrF6XVzvc+7tACiCHhjmLiFFYpiD7r
WuM++rB+Tns0mzNB6XWllYWKEU/8FqI6RrSHPYacSxFj3zFgiuLxQ2AFtKbsSTwC
bb6jNwDaU7q0c0UdXg==
=Jr9l
-END PGP SIGNATURE-

Re: Y2038 - best way forward in Debian?

[Guillem Jover]

On Wed, 2020-02-05 at 15:35:28 +0100, Ansgar wrote:
> On Wed, 2020-02-05 at 08:33 -0500, Sam Hartman wrote:
> > Steve, you're presuming that we would not create a new soname for
> > libc6 on architectures where we want a new time ABI.
> 
> Isn't the libc ABI for some reason part of Debian's architecture name? 
> uclibc-linux-amd64, musl-linux-i386, i386 are distict architectures
> after all.  So an incompatible newglibc-linux-i386 would be different
> from i386 as well?

Each libc needs its own architecture as that requires its own matching
C compiler, for the libc CRT, ld.so linker, some parts of the calling
convention, data types, or executable format ABI, etc. This is one
side of the architecture ABI, the other is coming from the CPU and
kernel ABIs, for example.

Given our current usage and definition of Debian architectures and
mapping to GNU triplets, the libc4 to libc5 (+ a.out to ELF migration),
or the libc5 to libc6 might have indeed demanded a new arch, as these
required new compilers (or a least different spec files) AFAIR and some
kind of hacked triplet-qualified hierarchies, but back then our
requirements for architecture definitions seems to have been more
primitive (first mostly mapping between CPU names, then CPU + kernel
names), we didn't have multiarch, and I guess a new arch (if it was even
considered, probably not) would have been deemed a cost too high, and
direct upgradability was probably way more important at the time.

Also the ABI tracked by the libc SONAME is a different part, and that
should not necessarily require a different compiler, otherwise you
could not build binaries against different SOVERSIONs for the same
libc.

I suppose the problem here is that the C compiler and C library are both
in charge of defining part of the architecture ABI, but at the same time
the C compiler and C library both also provide a set of shared libraries
with their own specific ABIs, so this all gets muddled into the same
basket.

Thanks,
Guillem

Accepted ruby-mobile-fu 1.4.0+github-3 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Feb 2020 11:45:40 -0500
Source: ruby-mobile-fu
Architecture: source
Version: 1.4.0+github-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Utkarsh Gupta 
Changes:
 ruby-mobile-fu (1.4.0+github-3) unstable; urgency=medium
 .
   * Fix package wrt cme
   * Bump debhelper-compat to 12
   * Bump Standards-Version to 4.5.0
   * Add salsa-ci.yml
   * Drop runtime dependency on ruby interpreter
   * Add myself as an uploader till the tests are working fine
   * Disable tests as they're badly broken because of minitest 5.11 -> 5.13
 - doesn't make sense for it to stop migration :)
Checksums-Sha1:
 ce58c694d4dc4df416e3700fd1ccea5e856b23be 2249 ruby-mobile-fu_1.4.0+github-3.dsc
 a55d0dcd239ad2547b6eacccde5ea9cb9e3dc5a3 3204 
ruby-mobile-fu_1.4.0+github-3.debian.tar.xz
 8c6d1c1782463a6e076da5e6cf41fea78c977316 11099 
ruby-mobile-fu_1.4.0+github-3_amd64.buildinfo
Checksums-Sha256:
 7b271c6348443a33c8d163acd1854231b74a8568c018d39965c0691e613ca3f6 2249 
ruby-mobile-fu_1.4.0+github-3.dsc
 fed017ef19b97eaba237b8b16618e41ad763fbc0838c5a9b3d5fffd1a83ca689 3204 
ruby-mobile-fu_1.4.0+github-3.debian.tar.xz
 fc606eb089e54f3667aae1024dc96a17579ed1548c089f2ea1eb8504293eb338 11099 
ruby-mobile-fu_1.4.0+github-3_amd64.buildinfo
Files:
 b6d313dfb83e1e129e436269be4a2363 2249 ruby optional 
ruby-mobile-fu_1.4.0+github-3.dsc
 35f16aeeb6676cad1055489c12ffb87e 3204 ruby optional 
ruby-mobile-fu_1.4.0+github-3.debian.tar.xz
 1cd6e85fb6790054faf4f381562e25d7 11099 ruby optional 
ruby-mobile-fu_1.4.0+github-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl468kkTHHV0a2Fyc2hA
ZGViaWFuLm9yZwAKCRCCPpZ2BsNLlhXbEAC0OXezs9onBRwXa7UqUWX3efpXF6GU
ax7Dc+1onTXGuVUy44sV5lu7ht78F8qTtSv+Nb9MbZg4a6OYNUVnYPmYzGI+u+JZ
zNUXSfY0CEVTf8mhCWjq5VSwaaPEJkltWZFAQ5dnpBlC4B5CyezrfdiNQ7p3uWkc
u6XVq0zwk8x/5jxPRPwslhnLioJX/5MesnHm+29+Sm93ne/KUUv9SZD8C3FVRo4H
yv7P3GWviot/cSA19/ldUQ2MJTD1RUre6M8MMMz/GZYRSUhjXXsuyHSlcdNJmzk8
ov0tA1LCFxNr7meaGaUu5g1/KROF/3cP53XToZseGKQ9EgxkqBtmp7mgv5rmJ8io
nCPaxqdrqUUC7059/oiPovclnkSNgoPc5rUfmdrQoVvg4TZITyxJ6OWH90+EVM7t
4YoNUA/qERcwmNsseEcgVjkzLJhWUkIY5PkiQ/j67TMkR1KyMNh1gdHZhCFfutDr
u9qwgZDDglQThZokWUHWK5LQR00f6CG2DwvU+BKqlGSwx4UjX34N7T/4MESe/xgP
qWddIcJDwnfcU3+RvTCviBU60HAm6UZePOtXa9LFb54GK7IoQ9QTnmx/HeyVoc0x
qKqkT/gW/8KaIJ8sc2uo+sUe5Eb6Qresn8X354i08fBPjqZVoLh+8uknswzIuPxe
NCmf06/zjUivOA==
=N8+0
-END PGP SIGNATURE-

Accepted mapnik-reference 8.10.0-2 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Feb 2020 17:38:53 +0100
Source: mapnik-reference
Architecture: source
Version: 8.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Changes:
 mapnik-reference (8.10.0-2) unstable; urgency=medium
 .
   * Team upload
 .
   [ Bas Couwenberg ]
   * Bump Standards-Version to 4.4.1, no changes.
 .
   [ Xavier Guimard ]
   * Bump debhelper compatibility level to 12
   * Declare compliance with policy 4.5.0
   * Add "Rules-Requires-Root: no"
   * Add upstream/metadata
   * Fix links
   * Add patch for semver ≥ 7 (fix debci)
   * Use pkg-js-tools auto install
   * Enable upstream test during autopkgtest
Checksums-Sha1: 
 abc31aede5b314ee09c3481f54521eec03615488 2128 mapnik-reference_8.10.0-2.dsc
 22d9f3b4578014afd442b2eb259e7779ebcdcb92 5844 
mapnik-reference_8.10.0-2.debian.tar.xz
Checksums-Sha256: 
 7303ea1b342883f721207d84e9aa5d23366e2ac4c7ecf94a4f57f7725b0e5058 2128 
mapnik-reference_8.10.0-2.dsc
 cbcfd8d798bebc2a966bf798b3d7f13e37bd77d4b95413a33bdf5174831fd8a6 5844 
mapnik-reference_8.10.0-2.debian.tar.xz
Files: 
 d73eaaada279b4865200e5e845651cdc 2128 doc optional 
mapnik-reference_8.10.0-2.dsc
 310025db6e5b9062533e94e6ff8841b5 5844 doc optional 
mapnik-reference_8.10.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl468IcACgkQ9tdMp8mZ
7ulOyw//bdIT8T6TPDY2BnWQsU7kWgCw8BGREFFH6ms0wLT0L5L23h4EhYLisemp
rlANU8CDU6/P33YTWS89pYCqfiGgQA8woiGS+WKgkgUIJbq3SGjc05jNVmkG8L/i
+ERkCrBbS3jkAjPBiRraS8S9BpvTCdpQn0X1YAieAPJA/k3WSlKj+Dz5jl6cQJl2
j+IcY07HlUXhyCgxwMlFwZIcz+NIll2Uz1bOcIZNN0FJrkcUAj8YMOXgcDetnx6j
MBUqEx6AgO2Jgeiwv4qBdICKqkoeGsNSxiCf5K9Va16zXaDI487Jut5eJg7lfVCD
qGVH9hdcbWADmrdaynuc1MzGoWdgC9rd0AE4XrTY44GfbxRPp+TG39E6IYzYHVnW
goZP5LRAxzlIF1fwb9BC8K/z5JgblVl1GJ3k24HcGzCowEd54C4kpfIMg3k6cojQ
GnW3vMVk9TM9wFgVHRrP+Umy1QQUu0g7YvcCRzj5ZOuH7AHJH0GRjWFHZllqFObi
bEnnc8KBlF1BYTBIupADAjN0ZGs6ApOe/7IsoiTj15NCgZtSNf5sFxxyIZPYBmMY
ZPVhlJaiXUGWMbZ9TwRmj0yUhUjKJTtRmtegV2fPrOmc2tzmv2MSZY8J7Gv1sLLM
+2ARlZDwt6FNeLbvzTvZ+mbS7OLsDb8f7Vu7JjndO/zVOWb5vxU=
=PXSo
-END PGP SIGNATURE-