Re: XFCE4 notes

[Paul Sutton]

On 20/07/2021 00:09, Wookey wrote:

On 2021-07-14 20:05 +0200, Michael Biebl wrote:

Am 14.07.21 um 19:54 schrieb Paul Sutton:

Hi All

Am I right in thinking that xfce4-notes has been removed?  I have
installed xfce4-goodies and it isn't installed.


 From unstable/testing that is correct.

See
https://tracker.debian.org/pkg/xfce4-notes-plugin
specifically
https://tracker.debian.org/news/1114283/removed-181-3-from-unstable/


Hmm. That's very annoying. I use it on a daily basis.

I see that the reason is given in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955349
'uses unmaintained libunique'.

Any further comments on what would be required to get this back?  Was
libunique actually broken/a problem, or merely unmaintained?

Is there something else one should use to do the same job, in which
case maybe the best thing is to update xfce-notes-plugin to use it?
Assuming that's not too difficult I don't mind doing some work to get
it back in a ship-able state.

Or it there something else that is still around that does the same job
as the notes plugin?  It's quite unusual in the way it works.

Wookey




Hi

gnotes was suggested, however I think the issue for users will be that 
while the files that store data are in plain text, if they are backed up 
before reinstalling debian,  they can just be dropped back in place and 
you can carry on with your notes.


For me xrce4-notes are stored in

~/.local/share/notes/Notes

Using a new program means work flow is impacted for people (I a thinking 
of others here)


I am happy to switch to gnotes, however would be good to have 
xfce4-notes working again.



Paul



--
Paul Sutton, Cert Cont Sci (Open)
https://personaljournal.ca/paulsutton/
Pronoun : him/his/he
OpenPGP : 4350 91C4 C8FB 681B 23A6 7944 8EA9 1B51 E27E 3D99

21st Debian Conference August 22 to August 29, 2021.
DebCamp from August 15 to August 21, 2021

https://debconf21.debconf.org/



OpenPGP_signature
Description: OpenPGP digital signature

Re: XFCE4 notes

[Wookey]

On 2021-07-14 20:05 +0200, Michael Biebl wrote:
> Am 14.07.21 um 19:54 schrieb Paul Sutton:
> > Hi All
> > 
> > Am I right in thinking that xfce4-notes has been removed?  I have
> > installed xfce4-goodies and it isn't installed.
> 
> From unstable/testing that is correct.
> 
> See
> https://tracker.debian.org/pkg/xfce4-notes-plugin
> specifically
> https://tracker.debian.org/news/1114283/removed-181-3-from-unstable/

Hmm. That's very annoying. I use it on a daily basis.

I see that the reason is given in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955349
'uses unmaintained libunique'.

Any further comments on what would be required to get this back?  Was
libunique actually broken/a problem, or merely unmaintained? 

Is there something else one should use to do the same job, in which
case maybe the best thing is to update xfce-notes-plugin to use it?
Assuming that's not too difficult I don't mind doing some work to get
it back in a ship-able state.

Or it there something else that is still around that does the same job
as the notes plugin?  It's quite unusual in the way it works.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Re: Steam Deck: good news for Linux gaming, bad news for Debian?

[Samuel Henrique]

Hello Simon,

That's an awesome reply, thank you very much for having the time to
write all of this and adding the links, I have found the Steam runtime
bit particularly interesting.

> (Disclosure: I work for Collabora, and I'm currently working on the
> Steam Runtime.)

If you're ever feeling like it, I would love to see a talk from you
about the inner workings of Steam on Linux/Debian.

> Anyway, enough email-writing, time to get back to Assassin's Creed
> Odyssey, under Proton, in a Debian-10-based Steam Runtime 2 container,
> on a Debian 11 machine :-)

Nice, I loved Odyssey and Origins, although I had a little bit of
issues on Odyssey because I didn't go for the hard difficulty when I
knew I was gonna try and do all the side quests... I ended up too
powerful at the end xD.

Cheers,

-- 
Samuel Henrique 

Re: Steam Deck: good news for Linux gaming, bad news for Debian?

[Simon McVittie]

(Disclosure: I work for Collabora, and I'm currently working on the
Steam Runtime.)

On Sat, 17 Jul 2021 at 13:48:32 +0100, Samuel Henrique wrote:
> As some of you already seem, we have very good news for the Linux
> gaming community, although somewhat bad for Debian:
...
> https://www.steamdeck.com/en/tech
> Operating System: SteamOS 3.0 (Arch-based)

I think this is still good for Debian, although arguably less good for
Debian than it might have been if it was directly based on Debian like
the earlier-generation Steam Machines were.

Rather than thinking "ugh, this isn't Debian", I'm thinking of this
as "good, this is modern Linux", and in particular not Windows!

SteamOS 2 is stuck on Debian 8, which is a long way out of support at
this point, so SteamOS needed a significant amount of work to catch up
with the last ~ 6 years of development somehow. You might notice from
https://repo.steampowered.com/steamos/dists/clockwerk/ that packaging
metadata for a Debian-9-based version appeared at one point, although
I don't think any packages appeared in that repository.

Obviously, as a Debian developer, the route I would have tried first for
that work would be to rebase onto a newer version of Debian - either
a stable release, or testing, or their own testing-like snapshots of
unstable like Ubuntu does - but Valve have chosen to rebase on Arch
instead. I am not the right person to say why, sorry.

Arch and Debian are not actually a million miles apart: they're both
package-based binary distributions in a nearly-FHS directory layout
(unlike for example NixOS), using glibc and GNU userspace (unlike for
example Alpine), booting with systemd by default (unlike for example
Devuan), community-maintained rather than driven by a single corporate
sponsor, with divergence from upstream generally being treated as a bug
but tolerated if there's a good enough reason why it's necessary.
(Of course, there are other distros that I could say similar things about,
Debian's threshold for what is a good enough reason for divergence from
upstream tends to be lower than Arch's, and we make different technical
decisions in various places.)

In terms of the upstream versions involved, Debian 11 is more like Arch
than it is like Debian 8 (although obviously the packaging and OS layout
are rather different!) so this still seems better for Debian in terms
of having the games that run successfully on the Steam Deck also run
successfully on Debian (and Ubuntu, and Fedora, and other modern
distributions).

I would hope that if Valve later decide that they need to be basing a
future SteamOS release on something that has periodic stable releases
and a security update story other than "upgrade everything", the obvious
choice would be Debian - but we'll have to see what happens.

> the gaming side of Linux still
> receives major improvements with new releases of things like Proton

You might have noticed that https://www.steamdeck.com/en/developers
emphasizes Proton over native Linux games at the moment, as a way
to get a broader range of games available, and the publicity videos
seem to be mostly (entirely?) things like Jedi: Fallen Order that are
Windows(-and-Proton)-only. Valve have said they're looking into getting
a solution for Windows "anticheat" mechanisms under Proton, which are
one of the biggest gaps in what Proton can do at the moment. Anything
they do to improve Proton is going to benefit Arch and Debian equally.

Current versions of Proton run in a container that is mostly Steam
Runtime 2 (+ graphics stack from the host system). Steam Runtime 2 is very
heavily based on Debian 10, with selected packages like SDL backported.
A Steam Runtime 3 prototype based on Debian 11 exists, although there's
no public release of it at the moment; if Proton starts requiring newer
versions of something, it would be natural to assume that the priority
of getting that prototype released will suddenly go up :-)

Similarly, it is possible to set native Linux games to be run in a
container via the "Steam Linux Runtime" compatibility tool, although
it isn't the default. Until recently, this was Steam Runtime 1 (based
on Ubuntu 12.04) plus the graphics stack from the host system. As of a
recent update, it's changed to Steam Runtime 2, with a few libraries taken
from Steam Runtime 1, and the host system's graphics stack as before -
so a combination of a Debian derivative, an old Ubuntu derivative and the
host system. I'm hoping that will result in better compatibility for games
that implicitly assumed they were actually running on something newer than
Steam Runtime 1.

These benefit ordinary Linux systems like Debian just as much as the
Steam Deck - perhaps more, because if the Steam Deck is running an
Arch derivative, it will always need to be up-to-date (because that's
the only way to get security updates in a rolling release), whereas
non-rolling-release systems can easily have libraries that are older than
those in a runtime container.

I'm also 

Accepted thunderbird 1:91.0~b1-1 (source) into experimental

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Jul 2021 22:04:15 +0200
Source: thunderbird
Architecture: source
Version: 1:91.0~b1-1
Distribution: experimental
Urgency: medium
Maintainer: Carsten Schoenert 
Changed-By: Carsten Schoenert 
Closes: 990631
Changes:
 thunderbird (1:91.0~b1-1) experimental; urgency=medium
 .
   * [78f0ddb] d/source.filter: some updates to filtering list
   * [3d29fcf] New upstream version 91.0~b1
 (Closes: #990631)
   * [daa7fab] d/control: Increase some Build-Depends
   * [f4bfd22] d/control: Remove libgtk2.0-dev from Build-Depends
   * [ad4e281] d/s/lintian-overrides: Adding one more file to ignore
Checksums-Sha1:
 3832ca52eb56aeb54583bafeac89a225627ada15 8075 thunderbird_91.0~b1-1.dsc
 1afda9e0037995fb1bc7f1a5fea16ff96a61e7b2 12174264 
thunderbird_91.0~b1.orig-thunderbird-l10n.tar.xz
 4d2af17373703b551ded60db4f12cfa3c0f807a3 427984840 
thunderbird_91.0~b1.orig.tar.xz
 3ccbc1b95e83b8af76a13cbc5f5b71a2ae823030 536640 
thunderbird_91.0~b1-1.debian.tar.xz
 a88c15fbd3f659500fe56fb1a4282ec06a38719c 35359 
thunderbird_91.0~b1-1_amd64.buildinfo
Checksums-Sha256:
 264328a365dd5406f56cdc199c1685a5f7fee97682ff71c6879d269e4ef27c85 8075 
thunderbird_91.0~b1-1.dsc
 cb1f665762bc4fe8fa246411a486f452513670dfe4168f99937df45e5cbdf60a 12174264 
thunderbird_91.0~b1.orig-thunderbird-l10n.tar.xz
 4caf2bbb77d73dcb12a40ecd4e15f2d4728c455e7e0ae29f3f976651e6933d61 427984840 
thunderbird_91.0~b1.orig.tar.xz
 9ac866ea5b7f67cc9bbf2524c5d7ec17b02e5dec7bed2ef8fcdbf858ea886ef8 536640 
thunderbird_91.0~b1-1.debian.tar.xz
 68f7d899e6252cf48e2e175da87194369d64f09c312a067f6498c92ec1246d85 35359 
thunderbird_91.0~b1-1_amd64.buildinfo
Files:
 9f3915bf0ea7ced22b7ccf5fec6675a8 8075 mail optional thunderbird_91.0~b1-1.dsc
 829dd2cb98b48f4baa7e0acc67694b07 12174264 mail optional 
thunderbird_91.0~b1.orig-thunderbird-l10n.tar.xz
 0f120bdd7f60489424616cf236718544 427984840 mail optional 
thunderbird_91.0~b1.orig.tar.xz
 0e7d2f07b3be76f8c4e78f820f0a5cfa 536640 mail optional 
thunderbird_91.0~b1-1.debian.tar.xz
 89e975aceb11f112237e657b28aea615 35359 mail optional 
thunderbird_91.0~b1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAmD14dEACgkQgwFgFCUd
HbBe9hAAhJli+fETcfa+qSCazmyFBDIOqWBgyyT+KOlruxmyTRN2NX814LxYn9l7
FViyspg3xKpINMRQspNj+/JGQukSt4rcieX1GzTYZTv4nuHGHZAMIsrsMxhfQeE4
wprN8Qt9lKM2L+/X1nAZfB3n6ufNf6GUwr007+Bcv4bqN0GNk0GHrNDf0+LOX79z
6eF4wegJx+4+W2tYJVHOJ9BxLE9yQ2/gqq3Ms1GS93USkI7kQF8sCzXD+hZAkli0
MDVL96gChdNLO6jdSzQQvdBHCu3L4wVlBwzSBkvBImvAlwzSEuXwdyIf4S9fXAVO
GaooHailstI2+X1uH9uPmDfal07BQSbYnuIVdJH6/OmUV/KNec4QVFXxt/nxx8CL
U1cn5WF05sQKNJHrpuXstlmS/MZq2pHLJ88pUmQknDxb8RE56tD8QjXJ45eCo8mz
zD6H53nkDKMZBPZl11jsHV09a7eLKO1HoGdp6vO/tdOZFzJnYngXM0NhmU078ch5
owVaR6QnCA/dQZ2xzwBQtuGHrD6JXPXsGWNIvWZDM5PsPGOxjlMDDxiCrzFgIUIn
PImZVmOjogNlHJhfgyWK2TriBRRgHkhgRupCRV8TPkhS2hr/XLgh17W2sUI1CzF4
iOIwfkgfgkrWmFx7aGCp7WZv0PL25ji+K6S9IH2nud4gdFBNUL8=
=T08G
-END PGP SIGNATURE-

Re: Need help with Multi-Arch in systemd

[Joerg Jaspert]

On 16194 March 1977, Simon McVittie wrote:


Would it be feasible for dak to have a list of binary package name
regexes mapped to a source package and a section/priority, and 
auto-accept

packages from the given source package that match the regex, assigning
the given section/priority, without manual action? That would let the
ftp team pre-approve src:systemd to ship /^libsystemd-shared-[0-9]+$/
in libs/optional, for example.


At some point somewhere I think it was already said, but in general: We 
love MRs, we are at https://salsa.debian.org/ftp-team/dak/ and something 
doing kind of auto-NEW processing is NOT out of the question.


Exact details have to be hashed out, but this is the wrong thread for 
that. While sometimes NEW can be annoying, it regularly catches bugs 
even if "only a small change in packaging" happened, so it does have 
some reason why its there. But yes, there are some candidates (hello 
kernel) that can make use of something with less humans involved.


Your example above doesn't sound too bad as a starter, though haven't 
put any further thought into it yet.


--
bye, Joerg

Re: Steam Deck: good news for Linux gaming, bad news for Debian :(

[Simon McVittie]

On Mon, 19 Jul 2021 at 02:25:16 +, Paul Wise wrote:
> BTW, the Valve Arch Linux overlay thing appears to be here:
> 
> https://repo.steampowered.com/arch/valveaur/

FYI, that's an overlay for "upstream" Arch, for Arch users who want to
try out Mesa and kernel patches that are not yet mainline - analogous
to the various PPAs provided by https://launchpad.net/~kisak. The name is
analogous to AUR, the repository for unofficial addon packages for Arch.

When SteamOS 3 becomes available to the public, I would expect it to be
more likely to appear in some other directory on repo.steampowered.com.

smcv

Accepted intake 0.6.1-2 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Jul 2021 22:19:14 +0200
Source: intake
Architecture: source
Version: 0.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 987486
Changes:
 intake (0.6.1-2) unstable; urgency=medium
 .
   * add fix-ftbfs-on-32bits.patch (Closes: #987486)
   * d/watch: fix broken link to github
   * d/control: add myself as uploader
Checksums-Sha1:
 7634da51422ad0899cafc3f5a8de66f6f25ee10f 2519 intake_0.6.1-2.dsc
 a74076a755a65cee3ed1eb1fac78c7ab44724816 10808 intake_0.6.1-2.debian.tar.xz
 70c39d26874bd89ad53600dbfb4f8d6fe34faa16 8896 intake_0.6.1-2_amd64.buildinfo
Checksums-Sha256:
 eee407d8118e4c20a7f24e149be3adafd50e34f61f2d2fbf4b3bf1535703b29d 2519 
intake_0.6.1-2.dsc
 6fe87124aa5af64d65bb066ffc532f76a441b5accc289be2b2db63e1e66b988a 10808 
intake_0.6.1-2.debian.tar.xz
 6c66f976ae53e921a8e31251b456d3e71202e4e0319bf1a01959248d3781f7c8 8896 
intake_0.6.1-2_amd64.buildinfo
Files:
 28d399c1829f996c49a08646dbb40835 2519 science optional intake_0.6.1-2.dsc
 d042e35cb05f0b8affa4fc6cc95e6859 10808 science optional 
intake_0.6.1-2.debian.tar.xz
 cbf98c70b1fabf57f3d653ba6ba2d3b2 8896 science optional 
intake_0.6.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmD1ycwUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdoEuA//cFjDXpbo2Du2mFg3JIA+uIi18OQB
RFRCiLG3v4ZZUZ3ks8M9ijVzwAQbZZnJeTz4/3Iy32inMLxl/NN0cUJG8B2oDE4W
0cK8aqAqJrOCv9Cc5SEuMyjZr1nGqskQV7pubU7yPY8YjbYEY0Ha+3n8LoX1oBnN
A2X3Y1MNdKugBDOLh1hKusOJeFcI//kDh0lR7l3Ri8MprOMM2peDZDqWZ1vjSZhD
VOW78Je1jrhdASZT5t08sk1ngqUEAtRMhy9/tc8/r4+3zPfj++qSRlxkip9SZeUn
980Kl+ff+j3OtUq2BGI55TE15QQhtG/wdzLacCRJHrt97vbFZWx92nPgF0gOuzb7
w8ITVcbBFDk3tuaxIOQglEyYEuvIw2CmQuNVTntz2WjzLlHL8dREFARigOLVOWe4
RuSuYj+2JTuutRWi9NNHvRQ4RtqsiQtIOS58Urvp/ShjfldtIlUlSiRgimXJvR9A
dq8/MoYxGhABM9wPndhluQQZ3L8g0V0solbPyI6FFq49cnij1fqp0iDUbF6qEJDc
9GYqwcw7dxMCF5BVpeTWThbgxJviuIqdIWpXxxY1BLlrz/r26W+CDwHJu4gy7Xml
b5Dt4AnyJoJiq73vJ5LPK8miNX3bAdxFvotA8pKIBjpVZTIUVgdSzo40I42CgWa3
hVxOGNrC4DtUkWg=
=k9/V
-END PGP SIGNATURE-

Accepted containerd 1.5.4~ds1-1 (source) into experimental

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Jul 2021 02:45:17 +0800
Source: containerd
Architecture: source
Version: 1.5.4~ds1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Shengjing Zhu 
Changes:
 containerd (1.5.4~ds1-1) experimental; urgency=medium
 .
   * New upstream version 1.5.4~ds1
 Fix CVE-2021-32760.
Checksums-Sha1:
 1c93fe11ec5ca93f52112f0fee7b6891f9ba7399 3824 containerd_1.5.4~ds1-1.dsc
 e6df1505a2c3d82f13ca50364e91e07f32f75728 1908848 
containerd_1.5.4~ds1.orig.tar.xz
 936605aa959dd1ee51d3143a299521afcc222e54 14948 
containerd_1.5.4~ds1-1.debian.tar.xz
 7e1b9994a2871fa1e90c21849429986f24398f5c 12557 
containerd_1.5.4~ds1-1_amd64.buildinfo
Checksums-Sha256:
 041b900c9cfe753791f66cd1e328524889a173505619963ebe3da014c3b38455 3824 
containerd_1.5.4~ds1-1.dsc
 9798136f10f51d4817e88ecbab28d12e31b4235c81bdb642ba2d8d2faea1e21b 1908848 
containerd_1.5.4~ds1.orig.tar.xz
 4a405e8b0008c844afd5af65ff5ce68289e4ce1a953a711dde52eeaf5875ef05 14948 
containerd_1.5.4~ds1-1.debian.tar.xz
 5159e3ff4ce27ac056f46cb23cdcb996616bf5fb7da1ebeecf9015d4cb844de0 12557 
containerd_1.5.4~ds1-1_amd64.buildinfo
Files:
 017811a81e46d505471c30e0af5d9147 3824 admin optional containerd_1.5.4~ds1-1.dsc
 1ba62afa70d0d652650076f5e6edc84d 1908848 admin optional 
containerd_1.5.4~ds1.orig.tar.xz
 01d6ee3544aef3a21584d478af07a6c9 14948 admin optional 
containerd_1.5.4~ds1-1.debian.tar.xz
 37b5468039f083fd48f87b7a3065cd6a 12557 admin optional 
containerd_1.5.4~ds1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iIYEARYIAC4WIQSRhdT1d2eu7mxV1B5/RPol6lUUywUCYPXJxBAcemhzakBkZWJp
YW4ub3JnAAoJEH9E+iXqVRTL4iEA/1X0nqsBZqGE3B5FtZJgzSyK2j9BMOShGXFC
HaO+Q9ysAQDDDEoIsyu5AxKBpe1yG/AtG7t4YJkAKX41CPOEBvJ1CQ==
=xNuZ
-END PGP SIGNATURE-

Accepted containerd 1.4.5~ds1-2 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Jul 2021 02:36:10 +0800
Source: containerd
Architecture: source
Version: 1.4.5~ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Shengjing Zhu 
Changes:
 containerd (1.4.5~ds1-2) unstable; urgency=medium
 .
   * Backport patches for CVE-2021-32760
Checksums-Sha1:
 59bcb5e3c342724a7659224c9bb2e57d4516bbc0 3857 containerd_1.4.5~ds1-2.dsc
 49caf517d607ae50a9c2bc60cefa1290030680d2 27108 
containerd_1.4.5~ds1-2.debian.tar.xz
 5d805b08aae541152bd8e1c3f2e0bc87f0c512fa 12429 
containerd_1.4.5~ds1-2_amd64.buildinfo
Checksums-Sha256:
 4e608dbfc209b490de88db19130c5cc04146174642daac68f07c61a9cbea4e9a 3857 
containerd_1.4.5~ds1-2.dsc
 c2d82aba0dab57a97960d11d17b8254fe26ea6c48a1fe94df4ee79d109afa559 27108 
containerd_1.4.5~ds1-2.debian.tar.xz
 da44f6154b8708c9382e6aa8ca4c1e446fa3f8e1485b09deddedac3eff28325b 12429 
containerd_1.4.5~ds1-2_amd64.buildinfo
Files:
 d566e2129220f4c3077199cbc5a859c6 3857 admin optional containerd_1.4.5~ds1-2.dsc
 921dfc1efb3061fdb308d58814ec1a7d 27108 admin optional 
containerd_1.4.5~ds1-2.debian.tar.xz
 11d4e375bf28deab8d77eee40df4e948 12429 admin optional 
containerd_1.4.5~ds1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iIYEARYIAC4WIQSRhdT1d2eu7mxV1B5/RPol6lUUywUCYPXHKBAcemhzakBkZWJp
YW4ub3JnAAoJEH9E+iXqVRTL0c4BAKNCoMfcG+i5vhk4/8SZys9qB++cqRo+NsOn
T2J2hn9QAQCGhQxRx2saR2e0Myb9uIOg/ha7C3GD2F6+ynEcBc3jCQ==
=FKmQ
-END PGP SIGNATURE-

Accepted runit 2.1.2-41exp1 (source) into experimental

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 16 Jul 2021 20:35:34 +0200
Source: runit
Architecture: source
Version: 2.1.2-41exp1
Distribution: experimental
Urgency: medium
Maintainer: Lorenzo Puliti 
Changed-By: Lorenzo Puliti 
Closes: 990774 991227
Changes:
 runit (2.1.2-41exp1) experimental; urgency=medium
 .
   * Set rules-requires-root to no
   * Runit-run: drop dependency on runit-systemd | sysvinit-core
   * Runit: get rid of ancient transition code in prerm
   * Add upstream metadata
   * Add support for policy-rc.d hack in invoke-run
   * Update invoke-run manpage for policy-rc.d
   * Update News files
   * Shutdown.c:
 - fix wrong command line parsing logic that always
   caused a No-Op when any option was given, breaking,
   among other things, the init switch from Sysvinit
   (Closes: #991227)
 - reboot the system with -r flag (Closes: #990774)
   * Update shutdown(8) manpage
   * Update license and copyright years
Checksums-Sha1:
 e52290feea0fe396ce74be74483de65d5d4542fc 2279 runit_2.1.2-41exp1.dsc
 e98459ac22e25c51be070f49db09169314815fb0 45748 runit_2.1.2-41exp1.debian.tar.xz
 d7f01009ae6cb47e70881c89c59ee03fca4ca1eb 5827 
runit_2.1.2-41exp1_source.buildinfo
Checksums-Sha256:
 bd40db2fa4a4c4f20305909d5b69885d4b105e532eb3e7a2c7dbbdbee8177a87 2279 
runit_2.1.2-41exp1.dsc
 44430dc69d5f5da1b6adb1074e5b7a5fda0c30bc252eb86ce18d1f5dca2d7a7a 45748 
runit_2.1.2-41exp1.debian.tar.xz
 dbd0ffe9fbcf96653dac228a388edde060a1feb79176b69512e0a6b35e7d5908 5827 
runit_2.1.2-41exp1_source.buildinfo
Files:
 5f2d5b2fa939229c5014ac0bdf843637 2279 admin optional runit_2.1.2-41exp1.dsc
 554abfa0fa7981113e75722c2be55664 45748 admin optional 
runit_2.1.2-41exp1.debian.tar.xz
 6f3a4dae82342f8a3c276fd7757f2f52 5827 admin optional 
runit_2.1.2-41exp1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmD1v5UACgkQweDZLphv
fH7nkBAAwOznMVXykm/k4p3w18VayMmbpH1u35YaBn2LYaeUscg08Xw2tGoGWVSf
XnnjqIUbMMwrzoUw76aHJaEtqqssmRvs12unHnb2BVEw0xHAIMVdnEVvdY+IJ4I7
11vLYNmKgZUx2Hz+78P8KHj3/o766lCJkXvV0ELCUT3GmVr37q2aaXrVk58NgWB5
Ik0eMaxPEkiV6bB63rufYPqkf3BD+kIPcGtRMwAZlYO+LoUnbenIfll+6Fv29WRa
f0eGV0Fu0UzFfUzbb2faqsV1aos+ekqn5n2LL6I7x+bZwnnaVa8ZSckQtV6s42wg
eHdyvJwiDql7eJ6GU/ew4T8iD/pI6SOcNs15m6KRlfVC9k7v5dX+z4OGKUCZKIb7
HemuSVeiAu+AkHmtjMyZe5EAix7/rahReMWmIuXsZqrr+UWwPabSsu9wkXBlBiW+
Otb7lueaOmsiXB07HNV1NAQ0nrY2B1zJ0lcrQzgJpgOfMnJbnXfe4dB4J+sw4SCJ
bBxWSc8yGHqPrq46cXeBdagCKapBXSHvLj3VS/zMuIpzdBWLOS0bULhb7o+2BuPa
P+/8gpdmKExj80k7C5lNAZDFtrA8A4sbYS1hIXuUBLdNwbc27fXzhAifCj8QxHpz
xCth3Bq10lnDjsIxlW1VzOeefNkxQpf9mQGd0RJuF3zGFOx9NJ8=
=lbGu
-END PGP SIGNATURE-

Re: merged /usr

[Simon McVittie]

On Mon, 19 Jul 2021 at 16:41:42 +0200, Johannes Schauer Marin Rodrigues wrote:
> Should I rather file bugs with patches against individual packages
> to move their files from /(sbin|bin|lib)/ to /usr/(sbin|bin|lib)/

As discussed in previous iterations of the ongoing merged-/usr megathread,
I don't think this can be the whole solution, because some packages have
paths outside /usr that are part of their Essential functionality.
Prominent examples include /bin/bash and /lib64/ld-linux-x86-64.so.2.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978636#118 for
full details.

smcv

Re: merged /usr considered harmful (was Re: Bits from the Technical Committee)

[Marc Haber]

On Mon, 19 Jul 2021 15:19:32 +0200, Michael Biebl 
wrote:
>Am 19.07.21 um 07:23 schrieb Marc Haber:
>> I am NOT looking forward having to manually convert legacy systems to
>> merged /usr and I do sincerely hope that Debian will choose a way to
>> get away without throwing away systems that have just a small /, still
>> supporting a dedicated /usr as long as it's mounted by initramfs. I am
>> not sure whether we ever issued a clear statement about that.
>
>I think this is a misunderstanding. Files from / would be moved to /usr. 
>So the only way this could fail is, if your /usr partition was too 
>small.That's still a possibility for existing systems, but a much 
>smaller one then moving files from /usr to /. Typically a separate /usr 
>partition is larger then /.

Right, that sounds much easier. It's still an Open Heart Operation,
especially for systems that I don't have out of band access for, which
is rather common for smaller installations.

>I assume you are referring to the sulogin issue here [1], i.e. whether 
>we require a root password on an emergency failure or not.

Yes. From my point of view, this is taking away a freedom from the
local admin.

In an ideal world, boot failure behavior would be locally
configurable.

A mis-booted sysv system, if I remember correctly (I have been a
mostly happy systemd user for already quite some time), could be told
to "just try to continue and show me how far you get", which in the
vast majority of cases led to a regular login prompt from which the
user-login-plus-sudo routine just worked. This didn't hand out any
more root shells than the current way of stopping dead and refusing to
do anything without the "real" root password, as far as I understand.
I probably don't have enough experience to have the final call on
that. But it's just a pet peeve of mine that I can easily live with.

>Fwiw, this is mostly me being paranoid and not handing out root shells.

It's good to be paranoid by default. It's bad to force that paranoia
on the local admin who might have a choice to move to a different
distribution. But alas, the others do it the same way. So it's just
freedom lost.

>This has nothing to do with merged-/usr.

I never said it has.

Greetings
Marc
-- 
-- !! No courtesy copies, please !! -
Marc Haber |   " Questions are the | Mailadresse im Header
Mannheim, Germany  | Beginning of Wisdom " | 
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834

Accepted smem 1.5-1.1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Jul 2021 22:47:50 +0300
Source: smem
Architecture: source
Version: 1.5-1.1
Distribution: unstable
Urgency: medium
Maintainer: Michal Čihař 
Changed-By: Adrian Bunk 
Closes: 958129
Changes:
 smem (1.5-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch from Marco Paganini for Python 3 incompatibility
 in "smem --bar". (Closes: #958129)
Checksums-Sha1:
 c779fcebb058ab586499074fa1054c77c7c471fa 1980 smem_1.5-1.1.dsc
 826e0bb68b0352759d5e9d7661ace308613f7f31 4280 smem_1.5-1.1.debian.tar.xz
Checksums-Sha256:
 a0830ffbe69baa35c5912425510185b93bca1fa4144a59abb9c322b62de906d6 1980 
smem_1.5-1.1.dsc
 626e992ce191e0a9cb9cbbbf4b8ac961fa47bd66469896a578eac2a64f7d9474 4280 
smem_1.5-1.1.debian.tar.xz
Files:
 90ed5797b38bd730b6b96de6a0d69695 1980 utils optional smem_1.5-1.1.dsc
 af747989462ae270f4e6a85a47cb0717 4280 utils optional smem_1.5-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmDzNGYACgkQiNJCh6LY
mLFSnA//Ru586fnmlW2cy8F/qIfUiQ7OHHnhalVqNDkrwSbwbcgpcnCfkOnSDb6k
9ioTnhFowXgCY6TuVjXnlqDyn8BAYe8xdX777ToLUocmQ6zNsrm7QG0bRrPlW4SH
rInT0TcBv+sgzDXMqiCxNKMeItAjql4s8DBg2lslVh1ZOz1a25UsWeVwjeo8eN7A
T7+cpACmklyUqWGF0IAqlGRBQvJ10hNNXaswFWQTOKsyXQM4zrlDLsZIxJJA8aWG
j/F37jK2QITjbZh87Vx70WhOXGPiHuXHfg5Jo4pyoezCaaMI9eOJ2CqEQmC2GQN7
1kFI2XAPVZQKAoL4SOB6unwrPfvmKS6tp1yy7WJHcal7g6ZEDpMO7AyIpBrow5pp
jxQu//MSh4cE3GbP1pJEv6PuDwdf0RQsXu2waN3DrnuqWNj7wBHX3XNTyfFVrQhr
6Uv3sGlGA6MVUorPF3DDp3J9Z2UYIMS7Ex7uu66p3GKwnQbyQCKjU2rXKVW/R69c
tSLD+wUvx/lyYJgcTk+DrIxepRq7IFUPyNBrrf3QoBqoMy0N5lTSJc1q1Uc5aIex
Hogf3z7myy6njVNxcghrHALIej3A/HpQl1Qk498D0gmy7fXQSlcU5W/15yWyy/t4
L6KDCLvnDL9NCtWjZ15ZRi8M1Tlb8bLT8tM9MpKoqFSdGUB//rU=
=ZyBf
-END PGP SIGNATURE-

Accepted scottfree 1.14-10.1 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Jul 2021 22:54:45 +0300
Source: scottfree
Architecture: source
Version: 1.14-10.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Adrian Bunk 
Closes: 968375
Changes:
 scottfree (1.14-10.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch from Bernhard Übelacker to fix crash when restoring
 from save-file. (Closes: #968375)
Checksums-Sha1:
 bc295e9d93d8c43d95751ae702c55949f189d875 1986 scottfree_1.14-10.1.dsc
 24ffe9f63e9fb5d9fc9eb2f0ed3b0b57c85908a0 5196 scottfree_1.14-10.1.debian.tar.xz
Checksums-Sha256:
 6d66ecf926305a460999fc212eca666333e3459a13025139ec2967e93e0d7002 1986 
scottfree_1.14-10.1.dsc
 50307fbc753861457586c135df16148cc6fc311a4512088a3337709b57a2292d 5196 
scottfree_1.14-10.1.debian.tar.xz
Files:
 6222b5ce5239ffe03f7e4c710f18286c 1986 games optional scottfree_1.14-10.1.dsc
 9a1523fd73de3cf106b4800b9870f808 5196 games optional 
scottfree_1.14-10.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmDzNiAACgkQiNJCh6LY
mLH7DhAAzuZY10ZDQ6rzSq7ohSz07a+An9tOXUTae+o0jQYfU8aVH1d2IUgxkJD7
tsqJFvMihuC7ekn2X9oTvH4U3TeXL8bgCJfaJk95lxhQTXk6gJPbgeAcR+maqwYq
uutkd0AUiHV5wyIxYzfPBflJc5KJcXTrpAWZAjoN3fkkwGITdJp+XNxoCACEHNBM
x4tOG4RccfnUD7erT2CepPdRCUbTxJk9jcRhAL1aQ2hkPoT701RGdrsIg+NCMGVZ
RCqPtMJq8geLfBXIDNikmWpFi2NBoxLJLoiy+hfyQnWfr5xiU0huWrOvcWSzpq0v
DRAx4/BBeTcsUflPQpcSqLrS0YYfLy3wrxdHv8h0YpRT7LfqTYjpRKndAAYdLQ1e
SjH4SnHYpdNF+ZeIMkGN+JuZMl6tAK2pJKZfhDeTGQpSWMqVyILf8kebDqFwqZEe
wyzfQG07NRvdapuZNIJ8WNNSFKVj7rJGC2WpT46C+Qd8088cEZTNM6VhAHEOYCTk
J8eYqoD4gu60cwwjp8qEAnFLDgi2LnHVJlYGfwz919CQz3jT0sQnwiaS5FcotFJB
F3BziYpsNLeWey2TYyfBSFK8i1UGVC3jliP0vyT/otN1+CxLGiw3MvBcfBA1CVso
p/ZDWFfekilwmj899Vj8qceZ7lfaiVuUWDuUxYa/kbuEcissvN8=
=0xgL
-END PGP SIGNATURE-

Accepted lshw 02.18.85-0.7 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Jul 2021 20:19:28 +0300
Source: lshw
Architecture: source
Version: 02.18.85-0.7
Distribution: unstable
Urgency: medium
Maintainer: Ghe Rivero 
Changed-By: Adrian Bunk 
Closes: 946940
Changes:
 lshw (02.18.85-0.7) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Backport upstream fix for floating point exception on invalid FAT,
 thanks to Dave Gomboc and Bernhard Übelacker. (Closes: #946940)
Checksums-Sha1:
 3a1813bf04108a640cf9a387e0af663e5b09ddea 1922 lshw_02.18.85-0.7.dsc
 43283da3a9c799339825f9307d8e8034c47ec369 17768 lshw_02.18.85-0.7.debian.tar.xz
Checksums-Sha256:
 b29c9a633ec37664a04fa8cf9d569b688b199cf53cf49b803c890a5f72edb568 1922 
lshw_02.18.85-0.7.dsc
 19d4aeb59fec21616592cc94a4ae30c019dc926cd107bb664073a94ee187 17768 
lshw_02.18.85-0.7.debian.tar.xz
Files:
 ad828478bbd5e81a809a41132fd1a28d 1922 utils optional lshw_02.18.85-0.7.dsc
 2d26ec0855543e2969772646b97ff305 17768 utils optional 
lshw_02.18.85-0.7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmDzI9MACgkQiNJCh6LY
mLH7mQ/8CVZ0BfXZLOBEzAApufvFimy1VptKDZKYlAgKCJ0KWDa5Un8fKwChSbA9
qOTqLS4gnN2wdFjlQ7Id428jtq/2ayagN99naE/XawgEiYu5cX2/cZrdwltLoTqe
HVOZe3Z30gYeQLollYfWylWeJxWM6b2cFcZbMSLRJKyjSF3VxlGsO7XRxRA8kZAw
Ymscirq/vGulAsIZyjUM9DM/d5VGabZ4S/iNxGva97ixynf8DvsjXbkq579g+5Bl
9woavK0SW9cuj5qTIm/DUnyRN2O4vleEQ00/l0LvkrK15rhbTJ3R5GtzKCO4DQVb
QfsxN0EC01rNP8ceRFKqXeaycZk7biaLkXfKb9O4201leC5VJeZuBF+D1lrLGbR/
f8WxBWDFRpJFioMimZm4dlVyfB31T1tHJk3eOuaJKdh21AcoLqY0qXopKswYpMvy
/E9Cs2skDZUPBI9WnPQXO1mN3BVkggSVnZPoQ3659QOSJgisb2zDHRXaR4w6B+Dn
YSOFWkAy0GMU/zUBG4FXiIM+SHtb1q8WU0DSFaJ4u2+WJ1dSuc0msYpN6PKF8PiW
KR3D6wCdt3uj6cmsUZ9cCUYBsXPcrr1R3iSKLxcNeu7K3G5sbL1/SirotZ2+qLlq
/jIFgoA3AhCiih28N3EptuexRMfHq87ESWldWO0yM6u16xQBjnY=
=3Mtf
-END PGP SIGNATURE-

Accepted eboard 1.1.3-0.4 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Jul 2021 21:48:28 +0300
Source: eboard
Architecture: source
Version: 1.1.3-0.4
Distribution: unstable
Urgency: medium
Maintainer: Vincent Legout 
Changed-By: Adrian Bunk 
Closes: 962627
Changes:
 eboard (1.1.3-0.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add upstream fix for segfault on engine selection,
 thanks to Eric Cooper and Bernhard Übelacker. (Closes: #962627)
Checksums-Sha1:
 03662a51f929fd247281fd8ff536eac7f8ab29b3 1739 eboard_1.1.3-0.4.dsc
 4a42325ea80222e7a7acb12b87ed7780ac639175 16756 eboard_1.1.3-0.4.debian.tar.xz
Checksums-Sha256:
 74b4b4c2b544123b94d1e2fb5daa711ef26744e589a3b3e01846f24b2d4391a8 1739 
eboard_1.1.3-0.4.dsc
 3c2f2e4e8bda0fedf9a05b1fbabbc7caca8af7ae09120bce2115426d652e70be 16756 
eboard_1.1.3-0.4.debian.tar.xz
Files:
 7787939d1c69e050744cc0ebcacd8b0b 1739 games optional eboard_1.1.3-0.4.dsc
 7d24b54f8ef2022b24e091f8315ba406 16756 games optional 
eboard_1.1.3-0.4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmDzKEAACgkQiNJCh6LY
mLGOGxAAtNKAGdbBrOqYue9sPHpz9opngJaLGD4PL9xtkt9THkNs0p3qsX0qxbID
QTRqeeQ0yhlcCubyHlTXdnaqi5vYhLC6AR6h8L5LYCNY/ZwmHN8WQPDVszbohQYK
hltOnt53vz8oruyfqZsIGZoXxDKzfbxDqNCMj9/lxr5VXf6HLwl1O9AE457liZ1v
iIluOnBmbiQnady38xlc6qa6ve1prpTAMJ9AuPpgHbJEt4phYbafVBKOhwYTV/Vg
rjvvIIgGNCzrGBA0acjcX/p/ESXbcFpZgblCo8NuRQN9duYISlPzToyT5gQtMf6e
hcEGW/rx8e/kySn6jN9aT/q2O9wponWNF6OU7UzymJqRdaF02sc9Lk/OIapWGZbG
bQrX73qTEbSB25f6EoOWAM8gFcZUplXrINBkTZN1ot06+LekPXU+8XiorEHGAOmB
POWU7LzNbyRG0ktObKf3A4yTv5kDM8VIvCLq1YP5OckG1aGt4ZEf1XXGg1AzvPuz
6lDZAq7xLx487aHTD4SAmuoWhG8XXca/JUB81yXqlkBT0XjtdYAgrvoZB6LyILRp
Vqj4xI0qTYAIHZW2LVBDsHG4XhJVV7CFYfky66lcAO33iRFlrtTN739IfFOq5vdp
xmgtU9+3VMFAlY5h93pYVmezraZBwF5krJlWntQ1iY14sF6b7Ns=
=bbyG
-END PGP SIGNATURE-

Accepted libcloudproviders 0.3.1-1 (source) into experimental

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Jul 2021 16:40:19 +0200
Source: libcloudproviders
Architecture: source
Version: 0.3.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Marco Trevisan (Treviño) 
Changes:
 libcloudproviders (0.3.1-1) experimental; urgency=medium
 .
   [ Marco Trevisan (Treviño) ]
   * New upstream release
   * debian/watch: Update to match new repository URI
   * debian/copyright: Update upstream URI
   * debian/patches: Drop, all applied upstream
   * debian: Use dh 13 features
   * debian/control: Add versioned provides for gir1.2-cloudproviders-0.3
Checksums-Sha1:
 337e7028579f44bada7fdb71d58caf828e978b6a 2359 libcloudproviders_0.3.1-1.dsc
 cb2747dfadee719372044fd007644b38d18557cb 22442 
libcloudproviders_0.3.1.orig.tar.bz2
 13426d2e409597c01a358db5c3652f98209154f9 3436 
libcloudproviders_0.3.1-1.debian.tar.xz
 6a1b2bed70db4e6dd7863d40e422cb026470448c 12953 
libcloudproviders_0.3.1-1_source.buildinfo
Checksums-Sha256:
 f1e2bacccdfdf149d95ef9177d5071bdbaad9909339b6be33214690ba4dbe976 2359 
libcloudproviders_0.3.1-1.dsc
 de4aa746c1695f30fcd3b52a4a6ee149ce567a2f7e185499bf2963f77dd1bad0 22442 
libcloudproviders_0.3.1.orig.tar.bz2
 4e9782be003f48510324d6c536c256f4c5d23da03d63d5a2afb48e61fd4d9a0a 3436 
libcloudproviders_0.3.1-1.debian.tar.xz
 a3f6e779dc8c3cdd5885015a9e9d55ff8c3ce25e2099b453370fc3e34794e35e 12953 
libcloudproviders_0.3.1-1_source.buildinfo
Files:
 002cf4d6eb3f79dba0c73f4039ab75d8 2359 libs optional 
libcloudproviders_0.3.1-1.dsc
 d037cc4124849c726b9237d2289a6123 22442 libs optional 
libcloudproviders_0.3.1.orig.tar.bz2
 8d95be889213a1292ff88118560d3fc1 3436 libs optional 
libcloudproviders_0.3.1-1.debian.tar.xz
 a5f33f8265f574a4c3fe36a05793d9c1 12953 libs optional 
libcloudproviders_0.3.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE1MUB2kjreXoIF1CTlEnC9QmWY18FAmD1juAACgkQlEnC9QmW
Y1/RFw//RDEKgAhhFqU4TvnXIo8DYL69E7GKvShgCFkEWKn7zqIQjk7mRmFgmvdh
8kuu17yUIIkX8JSD4vE1MfYMmERe2zMKltuiyVb3rH9yZmJPeZWleYh+g3hNQjY/
YO8lAe6Z/RPl+sLle2TrNPuhr95u2+e1n3g0kpqTXjDa+yypqP8JDTSb7ferXlL+
YIO/a3Jfwq5tL3t9ByPh1jwYSjU3u0H8Hq5UsPk7rFLCW8ayCG3S00HoVvLKROmW
RNk02bQfhVJmdTIQAyALoUKObtBPRyUGkwgvYczOtrb923yQaXFTO7V7Lcqnh7U5
jxGR6gNSwAJeeDwAKytEon7E5wnUlpU+lh+RDlX2RSsE3xzcMHdTwjQRVU7oaCgN
JsJfYo5AHxX3Ce0JLIdaKus2JyS/eu7rH37aSDbG2vwPreFPSGsrTD0ajdBMUE6v
H/LBReAjvWrhc9k9lHBc7QDDnHj9yy3yNPk8lsQYwNyvOFbFKc88mG0lMQpyOAKI
6uuFtGcRSDoDlHNMD0AuIWSmfBrN7AkThpXDB0UpKMzUrqZqTYdbiB0+v4KOFKGj
ATxVsUuSjW21/POcK1ty3Wi19m4UErFMSaSzwK8cD2UT8E2Y1LbquZGhseXkwfYu
eOSRdr8alOBYWPWMhhVvI3oftr2yDtjJki6cklPPf+PwHqKahaI=
=VVnt
-END PGP SIGNATURE-

Re: merged /usr considered harmful (was Re: Bits from the Technical Committee)

[Johannes Schauer Marin Rodrigues]

Quoting Michael Biebl (2021-07-19 15:10:42)
> Am 19.07.21 um 03:36 schrieb Guillem Jover:
> > What I've also said multiple times, is that
> > merged-usr-via-moves-and-symlink-farms could have been implemented in
> > a fully automated way, by debhelper, w/o requiring any maintainer scripts,
> > all with full cooperation and managed by dpkg, with .debs shipping
> > actual tracked pathnames
> I'm convinced this view is way too naive and not implementable in 
> practice (and yes, openSUSE is a data point that confirms that)
> 
> What you propose is, that each and every package does its /usr-merge 
> transition on its own. This only works, if packages are independent 
> (enough) so this actually works.
> Unfortunately this is not the case. Take PAM for example. You can't just 
> recompile src:pam and have debhelper automatically move all files to 
> /usr. This would break all packages that install a PAM plugin. You have 
> a transition here, involving many packages.
> Same is true for udev rules, systemd service files, basically every 
> package that provides interfaces/hooks to other packages is affected.
> So it's not that simple unfortunately. You can't fully automate that.
> 
> According to
> apt-file search -x '^/(lib|bin|sbin)'
> on my Debian sid/amd64 system, we have 1747 packages shipping 24583 
> files in those directories.

more precisely, on amd64 unstable:

/bin 247 files
/lib{32,64,x32} 83 files
/lib/firmware 2379 files
/lib/live 115 files
/lib/modules 17500 files
/lib/systemd 2221 files
/lib/udev 614 files
/lib/x86_64-linux-gnu 343 files
/lib/* 441 files
/sbin 547 files

So most files come from /lib/modules, where only 14 packages are involved,
/lib/systemd which will be fixed by an update to dh_installsystemd, and
/lib/firmware where only 36 packages are involved. The remainder then doesn't
sound so scary anymore as it only involves 656 unique packages and not 1747.
And again many of those remaining packages will be fixed by an update to
debhelper, correct? Given that 90% of source packages use dh, that would reduce
the number to a very manageable size.

> There are *many* such entangled transitions 
> hidden in there, so I fear this is not manageable.
> As Luca pointed out, even distros with a much stricter governance model 
> were not able to do that.
> 
> The /usr-merge transition as described and decided on in the TC bug, 
> seems to me is the only viable way forward.
> 
> Yes, it does break dpkg -S, but your idea of using a list of mapped 
> paths as in [1] seems like an entirely reasonable approach to solve this.
> 
> Once we have this global switch to merged-usr, packages can bit by bit, 
> completely independent, update their debian/rules to use --prefix=/usr 
> and after a few years, we don't have any packages anymore installing any 
> files in /. We could aid this process with a lintian check that flags
> packages that install files in /(sbin|bin|lib)/.

So what what is actually the roadmap after the bullseye release? What is the
way forward? Should I rather file bugs with patches against individual packages
to move their files from /(sbin|bin|lib)/ to /usr/(sbin|bin|lib)/ or do we
already have a debhelper patch to do that move for us?

This would mean that we only have to bear with the problems mentioned by
guillem until that move is complete, correct?

And another question: once there are no more files shipped by any package in
/(sbin|bin|lib)/ we can let base-file create the symlinks?

Thanks!

cheers, josch

signature.asc
Description: signature

Accepted r-cran-rcpparmadillo 0.10.6.0.0-1 (source) into experimental

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Jul 2021 08:19:48 -0500
Source: r-cran-rcpparmadillo
Architecture: source
Version: 0.10.6.0.0-1
Distribution: experimental
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Changes:
 r-cran-rcpparmadillo (0.10.6.0.0-1) experimental; urgency=medium
 .
   * New upstream release (to experimental during freeze)
Checksums-Sha1:
 b50176e02577df93f1cc4ea2a82340a426f1063b 2033 
r-cran-rcpparmadillo_0.10.6.0.0-1.dsc
 5e50dec265ab82611aaa8bcb3652e570ed05ae15 1673880 
r-cran-rcpparmadillo_0.10.6.0.0.orig.tar.gz
 b397f9cc0bfa5249729787701d45166ce29c66d9 4312 
r-cran-rcpparmadillo_0.10.6.0.0-1.debian.tar.xz
 ede79620cbdfac166238df3f30e7f6378f6feb6d 10519 
r-cran-rcpparmadillo_0.10.6.0.0-1_amd64.buildinfo
Checksums-Sha256:
 814a42adb72bc2a44133052a1fe3cca2f952dd7fd2c91658daf94e1aabc15d70 2033 
r-cran-rcpparmadillo_0.10.6.0.0-1.dsc
 9b80deebb91df0960a4881f96dfeac6aecd4e86ed60ccecce2b5165aa6439dad 1673880 
r-cran-rcpparmadillo_0.10.6.0.0.orig.tar.gz
 7694c5084a4939ec3eae97b9b2021a78c331726c7d44e073eed420ee776b697b 4312 
r-cran-rcpparmadillo_0.10.6.0.0-1.debian.tar.xz
 5dff1591fc5381329dfa45780a22210e88f7fac0cea095b7880fd0344d2e6930 10519 
r-cran-rcpparmadillo_0.10.6.0.0-1_amd64.buildinfo
Files:
 a2d7b025d6bce2edf4d2f5c4c8c4b466 2033 gnu-r optional 
r-cran-rcpparmadillo_0.10.6.0.0-1.dsc
 fa81a27f3f2d4608b120dc711fab31c1 1673880 gnu-r optional 
r-cran-rcpparmadillo_0.10.6.0.0.orig.tar.gz
 45c845bf717e2ee8ffb22b1b52d77b08 4312 gnu-r optional 
r-cran-rcpparmadillo_0.10.6.0.0-1.debian.tar.xz
 892fd4da0986c59279d3d08953d96672 10519 gnu-r optional 
r-cran-rcpparmadillo_0.10.6.0.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIVAwUBYPV8hqFIn+KrmaIaAQhtUA//TKVzca9X+y9eyR2W0rMLc6exBIUEywIH
ekqdCQEfkNFbv1UDhoMILNmPcLGKNO3Ak4AqvE+4bfLsXeJZ/+jqn9jlENb9Jg+C
ArEieKyvtpggIcH5gaaZHH9e5HnEyTZTQAqfx3uSHRMOHsFhmNSqEBje6/0LOZvz
UrioVoQtBhvB8qTA/y3Oq+DidERdmtEv0T8ygepZMKVJ9QYnNTupRYf7ALtRbvxd
IIecgnOvq3Vm2GK83VlcbxCbTmwEjiX+vUhVP8cULRiXsMR+1kSUUYrnKDxW4u9d
mOT2fgzbneUwgaHV5NzMFRRu6Uk407+b6vGwh6Q1mbD8mKQGenfuCdk3zSfasnvp
Oj8bSmvFCS7nJOWjg+EXI2I1SMms+8XWsSq+Y9mLvZNeDZK3nf9DKMF7p4oScGX/
EBNPL68WpHPe4V2i/pXLtxx4kjXJrjuAlja5z/UrruXRJ5jVAE9uHUL6AAHLw7RD
pYu2/5Ss3seCZGYioTL2ediccSc01S2KepjqVyFYn9kRNecnXItpxYBlLP8EJ0w/
E7Xi/wXc18tf2YtMg97/8hzc2DNTx5D7ZWeHggL1ZEkW3UPuOO+6HOxkPAe9imY2
miTcly+rtFFA+cO+l4uJ8/hwrHp+9OmKDmKoBKjTg4bmCifgBKcFT7hzaruB82X+
7S8HzxRg5Lc=
=/26e
-END PGP SIGNATURE-

Re: merged /usr considered harmful (was Re: Bits from the Technical Committee)

[Michael Biebl]

Am 19.07.21 um 07:23 schrieb Marc Haber:


I am NOT looking forward having to manually convert legacy systems to
merged /usr and I do sincerely hope that Debian will choose a way to
get away without throwing away systems that have just a small /, still
supporting a dedicated /usr as long as it's mounted by initramfs. I am
not sure whether we ever issued a clear statement about that.


I think this is a misunderstanding. Files from / would be moved to /usr. 
So the only way this could fail is, if your /usr partition was too 
small.That's still a possibility for existing systems, but a much 
smaller one then moving files from /usr to /. Typically a separate /usr 
partition is larger then /.



There are some technical reasons to separate /boot if you are using a file
system for other partitions that isn't suitable for early boot (or if
you're using cryptsetup or other file system layers).  /boot/efi is always
a separate partition because of how it works.  Apart from those two
special cases, the only reason to put something on a separate file system
is if you have a clear and compelling reason why you expect a given file
system to run out of space and you want to ensure that it cannot take
space from other parts of the system.


I also believe that smaller file systems are unlikely to break and
that a system that can boot up to a ssh-able state even with a broken
file system is way easier to fix. We have taken a huge step back in
that regard with systemd since the systemd rescue mode requiring the
"real" root password even for minor startup failures is way more
unfriendly than what we had before.


I assume you are referring to the sulogin issue here [1], i.e. whether 
we require a root password on an emergency failure or not.

Fwiw, this is mostly me being paranoid and not handing out root shells.
This has nothing to do with merged-/usr.


Michael


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802211



OpenPGP_signature
Description: OpenPGP digital signature

Re: merged /usr considered harmful (was Re: Bits from the Technical Committee)

[Michael Biebl]

Hi Guillem

Am 19.07.21 um 03:36 schrieb Guillem Jover:

What I've also said multiple times, is that
merged-usr-via-moves-and-symlink-farms could have been implemented in
a fully automated way, by debhelper, w/o requiring any maintainer scripts,
all with full cooperation and managed by dpkg, with .debs shipping
actual tracked pathnames
I'm convinced this view is way too naive and not implementable in 
practice (and yes, openSUSE is a data point that confirms that)


What you propose is, that each and every package does its /usr-merge 
transition on its own. This only works, if packages are independent 
(enough) so this actually works.
Unfortunately this is not the case. Take PAM for example. You can't just 
recompile src:pam and have debhelper automatically move all files to 
/usr. This would break all packages that install a PAM plugin. You have 
a transition here, involving many packages.
Same is true for udev rules, systemd service files, basically every 
package that provides interfaces/hooks to other packages is affected.

So it's not that simple unfortunately. You can't fully automate that.

According to
apt-file search -x '^/(lib|bin|sbin)'
on my Debian sid/amd64 system, we have 1747 packages shipping 24583 
files in those directories. There are *many* such entangled transitions 
hidden in there, so I fear this is not manageable.
As Luca pointed out, even distros with a much stricter governance model 
were not able to do that.


The /usr-merge transition as described and decided on in the TC bug, 
seems to me is the only viable way forward.


Yes, it does break dpkg -S, but your idea of using a list of mapped 
paths as in [1] seems like an entirely reasonable approach to solve this.


Once we have this global switch to merged-usr, packages can bit by bit, 
completely independent, update their debian/rules to use --prefix=/usr 
and after a few years, we don't have any packages anymore installing any 
files in /. We could aid this process with a lintian check that flags 
packages that install files in /(sbin|bin|lib)/.





Regards,
Michael


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858331#33




OpenPGP_signature
Description: OpenPGP digital signature

Accepted python-aiosqlite 0.16.1-3 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Jul 2021 19:19:19 +0200
Source: python-aiosqlite
Architecture: source
Version: 0.16.1-3
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Hof 
Changed-By: Marc Dequènes (Duck) 
Changes:
 python-aiosqlite (0.16.1-3) unstable; urgency=medium
 .
   * Introduce autopkgtest running the upstream test suite.
Checksums-Sha1:
 6be7c5c8a2070902d741ac37673fe46f00192135 2160 python-aiosqlite_0.16.1-3.dsc
 4d02bad007aa5c3e145f0eadc66fa30c6d4f71ef 4552 
python-aiosqlite_0.16.1-3.debian.tar.xz
 73b6cad3b34216bff0fd3a3990b6565db5f9edf4 7801 
python-aiosqlite_0.16.1-3_amd64.buildinfo
Checksums-Sha256:
 5baeca854931a2a3ba85fcd0ff5dd4bffee225501d974f36b83d31d43c2a 2160 
python-aiosqlite_0.16.1-3.dsc
 b55468368eb3b344dbfa7ff5791f191ec47f2fb58ed9034607e9920a2c7c 4552 
python-aiosqlite_0.16.1-3.debian.tar.xz
 ae4dc6ac9828c6907115325e0acae1f0b4121a333b36d2cee2859b5c8158541f 7801 
python-aiosqlite_0.16.1-3_amd64.buildinfo
Files:
 884924c92f5da1417ca6d8d7035a5918 2160 python optional 
python-aiosqlite_0.16.1-3.dsc
 eac1cec48239b14cc63443d8650f2cf9 4552 python optional 
python-aiosqlite_0.16.1-3.debian.tar.xz
 3ece59b320c62691cec50c5aa64c8db9 7801 python optional 
python-aiosqlite_0.16.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAmD1ceQACgkQVen596wc
RD/zxQ/9F6+UoFkGlzHXbsltKWnKstU7EUak2mNSgJL/a04PRjdpKfU68/lK3VK4
252ZXfroLVwk0scpX5/xsECrtTh7/FnjvuaGlrlep4Ij/fEndlMl1bBKq+x7vqEp
7tdWuhrMUkoLomEIqcRNb0kZTGxMKZs6WN8CB5LsvK+gB570ncPkbxkFyWkBVtoz
QuzEMo2qdjFtWZv4xGrkV98aH3AJL5EXVMNJkwSg9xhKDt1CAd1WY4N0y2Yy+iqk
PWw7gtByCa/h4Fr5hnlSWzFBAx4Qny+YipSwPdOGUgtPi/2pWbaWfp9IwWTxbwK6
p/y05tf+oF556hsCNZ23WyOzIhg+lQ/SQjEokmfoMe7tEsvktbz+wT4jq9hhkgJM
lheRwNNCOmw9myH1PHScJrumwmKrb+LrYo7iGlF44R09ML41BGVxE7JUECYs+Muz
LRcjj4VrXV/f5kW36YETSgB9m+jrlejrOHbsY87mlNQSqVkZ13Xq2WOJHdCxhKgk
6x2ess86w1xnVBV6OF9yy9y1hM4Z+qW9YQ0lx6HS5VQeK2Rx3OWDzYT2Ic22LP5v
eMK+sNx7xi84HvZ0gsRfbADsKk9+HwYjfTeFOQlxH4XUa4EnjUO/XbJifrEIjBDP
ur7hHV93SDKzMWbnz2UmYFaLv3aDrpV3KqHoAqgX7SVtnQGBnrE=
=OrZl
-END PGP SIGNATURE-

Accepted bible-kjv 4.34 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Jul 2021 12:36:43 +0100
Source: bible-kjv
Binary: bible-kjv bible-kjv-text
Architecture: source
Version: 4.34
Distribution: unstable
Urgency: medium
Maintainer: Matthew Vernon 
Changed-By: Matthew Vernon 
Description:
 bible-kjv  - King James Version of the Bible: user interface program.
 bible-kjv-text - King James Version of the Bible - text and concordance
Changes:
 bible-kjv (4.34) unstable; urgency=medium
 .
   * Check for error return value
Checksums-Sha1:
 1c614c76ef7d6623ce8fd1f457a70f8ba3a873d0 1619 bible-kjv_4.34.dsc
 0bc0a3b701290162ddf0316ff4c0222ee187e77d 1412589 bible-kjv_4.34.tar.gz
Checksums-Sha256:
 9222901337abf23d3a4f65e3744efc598b077ac7be52f866f487f0826ef96b09 1619 
bible-kjv_4.34.dsc
 c5892a874dd40c7d75fbf308b9f7d13b572800a640f51d6dc6c81a4c1c6181c4 1412589 
bible-kjv_4.34.tar.gz
Files:
 52f60a72cde821570f10fb62c41c319d 1619 doc optional bible-kjv_4.34.dsc
 2e3cc2c9a7a5203cd345aaceda65d08a 1412589 doc optional bible-kjv_4.34.tar.gz

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEuk75yE35bTfYoeLUEvTSHI9qY8gFAmD1ZEUTHG1hdHRoZXdA
ZGViaWFuLm9yZwAKCRAS9NIcj2pjyHRvD/wK3/PPn3tYE1SEacziH7bKh1iTwQfg
HzsaZ35pqGEO2idcDTohkYUuIUAGfhABHxs+ejMVdMvnZQEq/W1sS45cr7qPeoQR
8hiym3skUJsx+T3Qz4AsgIJR/oJCiIn1eJrMIJO3Oqhp9agyVbLUkUghd8owM0QB
A7JzxrU1RpH4uHWfbeXaZNskcCC7wDdNGU08pONa48KqH+kcnCehaG5gA9qxzZHe
uwWXQHe0MD5xxGcwl5jNKPtyk1yFa8PzLex0hgvrngzwjiI7I8nVl6nnum2QeluO
RjNM0bmHoavISzJJ9HnLkmLjJlCOYZ4VNVELcb2u9ywmqAB2mnmZyT8lmxwFmXo5
ChQCuXzsed0OPTAhOACJcjaJB9VQoUQP4+I+AiklcCcJlIJMnc8ucxVjgevEVTKJ
UsCeO+wdiYz//JvTqFgDhK7vPSniobQJCN6eoGod3OUnlvQYGN84yuhl110MXBF1
vsmbMWi4uAS10EvrbL0IYAX3RC1fIND0S4Al2bHnxUZJ7Wl0tnSAArTddKvhyBij
yfwNNnkJ9rZWRks5y+Z5lcJqrBgBJU0vW2JxUqLZ/5g7YFGuGWhf5PUUeQL8dNot
8foFX5NAICC8R2lVEaW+6TR03klk85y7HUdtSdSKhGf5DDSvH0lU8WPKOKxTPIgh
gFYn8VxABbvKsg==
=2MUi
-END PGP SIGNATURE-

Accepted gnome-remote-desktop 40.1-3 (source) into experimental

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Jul 2021 07:19:03 -0400
Source: gnome-remote-desktop
Built-For-Profiles: noudeb
Architecture: source
Version: 40.1-3
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Changes:
 gnome-remote-desktop (40.1-3) experimental; urgency=medium
 .
   * Drop direct dependency on libmutter
   * Build-Depend on dh-sequence-gnome instead of gnome-pkg-tools
Checksums-Sha1:
 90b0e814d45d3d9606e5bf10c65d1956a9b143d5 2368 gnome-remote-desktop_40.1-3.dsc
 c7855a6244dbfd44f23b6e84373db4b6ccf116c3 5312 
gnome-remote-desktop_40.1-3.debian.tar.xz
 69c859ac73dfef8d6c03e965f9aadd78d0bd57fd 10454 
gnome-remote-desktop_40.1-3_source.buildinfo
Checksums-Sha256:
 a1aa0b009478a43c2e6f720bc2032ce6539aac393d9d7aa06483f3c20e9047ea 2368 
gnome-remote-desktop_40.1-3.dsc
 2cac4bb553bba76069e6718566bb096687a12e62e68c83b03ba69b7a0a05cd33 5312 
gnome-remote-desktop_40.1-3.debian.tar.xz
 ffda531c44ff377e68724c68f2bbd1345eb99e7df32634882fb15a3fd420db71 10454 
gnome-remote-desktop_40.1-3_source.buildinfo
Files:
 05fa847d2d00aaf33c4a3b78c51e6bd5 2368 gnome optional 
gnome-remote-desktop_40.1-3.dsc
 e9c57db4dae49d0b03cb7f60827b9097 5312 gnome optional 
gnome-remote-desktop_40.1-3.debian.tar.xz
 8071ffafa41a32e7926f75c7212a795c 10454 gnome optional 
gnome-remote-desktop_40.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmD1YN8ACgkQ5mx3Wuv+
bH22cRAApllPeBaQlBLvR4GjPPovS6sPcMDu4weBtm8DAAec7tahF2+YZe8xHMDS
J0JX48vUox/C6YZLu3GnqOr6YSP5a8nMNFNwyeUQeYJ2KtT9gFLLDTzlBc2ddwhm
ldgC4Ww9XPpTkE03P9tLn00d00a/8nBT0EuUiNLyRR9krfjfY7Zif6L7dj3Mq/19
LHrF8/b0CG40Cq7qxSkSznDu5DNzHmzkZZhndzVv693zvYsKI4wc5yFOmavEf1oe
lHONAlUG3UtqSFhg1hhw9RZI+hioRvx5XSg4f+Jd5qKJDkYDUumYxNatyGHZTsSV
XNxbBv3QZvSSQic+EhDjkBCnwKgilPAtoXsEoOCSRKF3C/OwlpoVhJ0o04U07Yl8
6NtGZ6AcPfrkiubgDMmo/M3fPtu4/vzs8J6YhTep+PjRNiqbf2hN0pbFS3l+3M+N
pUmbxpxJtop+uiv9T2UBnT5Uz72MQ9+KScyDDOeanAaVj1vw93VRPFWM60dDPJzy
aty7AeoAilL/1c4wEQgTruNEkw71gvUdsjAsMuxA9PXSoTzA+e68QYDQeCNcvcy5
j+6A8BhWbFKfLKC8m1ihxbFCmrXlVxDvR+Sny+UVNi4yDNfWBnbDJJkgkFMzc6C1
cwYVA7PS/6r6Fuo2rNGB9YRU8PJSgZ3o/ZPiCA1mBQG/O2yx8NI=
=Hd6n
-END PGP SIGNATURE-

Accepted exim4 4.95~RC0-1 (source) into experimental

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Jul 2021 13:10:00 +0200
Source: exim4
Architecture: source
Version: 4.95~RC0-1
Distribution: experimental
Urgency: low
Maintainer: Exim4 Maintainers 
Changed-By: Andreas Metzler 
Closes: 528344 702358 985997
Changes:
 exim4 (4.95~RC0-1) experimental; urgency=low
 .
   * New upstream version.
 + Point watchfile to test subdirectory.
 + Drop superfluous patches.
 + Unfuzz 90_localscan_dlopen.dpatch
 + Unfuzz debian/EDITME.*
 + Fixup debian/minimaltest for new upstream.
 + New upstream default configuration does not abuse message_size_limit
   option to reject overlong lines, there is a new main configuration
   option - message_linelength_limit - which is set to 998 by default.
   Mirror this change, now the IGNORE_SMTP_LINE_LENGTH_LIMIT only affects
   the data ACL.
 + JH/48 Use a less bogus-looking filename for a temporary used for
   DH-parameters for GnuTLS.  Previously the name started "%s" which,
   while not a bug, looked as if it might be one.
   Closes: #985997
* Enable native SRS support. Closes: #702358
* Enable external SPF support in -heavy. Closes: #528344
* Cherrypick 75_04-Remove-the-must-helo-check-from-the-example-config.patch
  from upstream git master. Drops checking for EHLO/HELO-received in ACL
  since the new main config option hosts_require_helo defaults to '*'.
  Adapt Debian configuration to mirror this.
* Drop versioned Breaks added in 4.94.2-6, they are superfluous due to
  bumped upstream version.
* 77_01-Revert-GnuTLS-when-library-too-old-for-system-CA-bun.patch. Fix
  regression (tls_verify_certificates defaulting to unset instead of
  "system" for GnuTLS) by reverting respive upstream commit.
Checksums-Sha1: 
 d073af0956cf37b2554dddad36aaf148a3e42168 2928 exim4_4.95~RC0-1.dsc
 fd0d337b04e5eda78a2c95f28e611f5302cd26f5 1862392 exim4_4.95~RC0.orig.tar.xz
 0654e29780d479f286b9b0865404c592c327243d 488 exim4_4.95~RC0.orig.tar.xz.asc
 e7027d73e71106c1d3610668b967d109721c018c 466068 exim4_4.95~RC0-1.debian.tar.xz
Checksums-Sha256: 
 45e13401951e418d5f4f7e4ff062fffe3a25340865f30a6aa0f687e4c83849bd 2928 
exim4_4.95~RC0-1.dsc
 558ff4307eec3b2d259c5d29c3b6ae50f7939971ef7a50615147d9c560782867 1862392 
exim4_4.95~RC0.orig.tar.xz
 9b9edd4a755a471239297e14870d9d394be6ff16d3688d8150e0654a08b732be 488 
exim4_4.95~RC0.orig.tar.xz.asc
 ae886397ab9b3637b9cdb64c14f6ed358091a2f25915634055e2641fab09df33 466068 
exim4_4.95~RC0-1.debian.tar.xz
Files: 
 f5b53f8e32a34bdafdbfacd39f78e9b5 2928 mail standard exim4_4.95~RC0-1.dsc
 15290185ea7fa95714fe04a18ff3ccae 1862392 mail standard 
exim4_4.95~RC0.orig.tar.xz
 fb3ad14622a8a86cb1c17c7ee3b9d6d0 488 mail standard 
exim4_4.95~RC0.orig.tar.xz.asc
 451b5b13029ed22da721e268032384f2 466068 mail standard 
exim4_4.95~RC0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmD1X7gACgkQpU8BhUOC
FIQWYA//VGpKaQukkInEl+qTry8eMjR+zbGnItnyqqDevAV8rxlj0qjEcCiYfg+I
nu+5lqFqhW5f6L/7L14cbWZzvYFHRV1tpCPvYk17+xx9e6gTYIKVswaPMny1PtPX
rx0102Xr6NXF/XrJhcO0F7+V7PYpv6bnKddlXg1UK1IJUF55fJVafjpQkcjfYXBJ
Sq/NTRNRK7Cto4m+5I8wxzkpp9tvm0wVXHeMgAUjkWUbi2gM0CRoJwDUWt5CeQ+K
tZr8xEmycrRPAFd92hVQ7NXeDNG9kokFCXmW3vxwdAghoSi8gDz2fVEujZ/sRwxC
2JW/D6nLdcbNwdAZIQHVwUVhKVuCIivaqyk1MUnnR8ivQumwRn49KiQW6i3sPPWi
6hG4tSYYQ73oYGFKgpeRh7S8LQi0mnk0nv/jeA95ax3vUY84Gm3tS/0vWOJbOzBc
mKP0B2D6a1j3HKU3jZi9LbUKBd1MvWUkuRGijcETj41LT5F9dc21LA/+Vxrsf04j
90S9W7lPINOpNx4jLQwxPIvsQDdLPIC/HO6D+O06eYqQTw2rOVP4bS3yf24fdJDi
ult8G9jJH6Zpmz76mJbnpRk/ay/soFCkj2WPJUNf3KwKfYxyBTP8N2awYl70O8Px
NkJglH1Z+wABX4iPDaAlYQtqnytV5DxyydjdDDnWSNXd88HGjeQ=
=t8iF
-END PGP SIGNATURE-

Accepted bible-kjv 4.33 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Jul 2021 12:10:28 +0100
Source: bible-kjv
Binary: bible-kjv bible-kjv-text
Architecture: source
Version: 4.33
Distribution: unstable
Urgency: medium
Maintainer: Matthew Vernon 
Changed-By: Matthew Vernon 
Description:
 bible-kjv  - King James Version of the Bible: user interface program.
 bible-kjv-text - King James Version of the Bible - text and concordance
Closes: 991133
Changes:
 bible-kjv (4.33) unstable; urgency=medium
 .
   * Make the build not run in parallel
   * Use bible.rawtext to build concordance (Closes: #991133)
Checksums-Sha1:
 af0656aef837818583284e4acd0d7692947ff832 1619 bible-kjv_4.33.dsc
 c6ff5c0066e87b92bdbdc0d07f781a7719b0ad80 1412931 bible-kjv_4.33.tar.gz
Checksums-Sha256:
 29ecaec825d504b10c9a0bb3248463ee0762cbb346767398f39e3b4772a845e4 1619 
bible-kjv_4.33.dsc
 0adb4f0b4806356bd706684c708acdb2063c15157cbeff70b5f4cca82524764e 1412931 
bible-kjv_4.33.tar.gz
Files:
 9d3844276bf5c017b5a8b56a057ce660 1619 doc optional bible-kjv_4.33.dsc
 0f0a9ea80bbfa39410953ed54ef847d8 1412931 doc optional bible-kjv_4.33.tar.gz

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEuk75yE35bTfYoeLUEvTSHI9qY8gFAmD1XxYTHG1hdHRoZXdA
ZGViaWFuLm9yZwAKCRAS9NIcj2pjyMq+D/94Yu7UJl/owmVYR6xka1RrIogBWSxG
zySL3KpXZEBUrgDq9UX34m1o+MwpY9lckMX/r73rvz/EweCM4h+BjI4o9nDhXT3S
0Y8tCceEy4218A28CAVe+pL/YgirH5TpdcpmOWiRkYKl/ySUXyw2CgF1Qq7iZ9rC
Wo2+eG20Lci0YC1jGb5+L53zB8zFX+HAj/jZHHlA5JksP7I1gX+gqJ4c6zRZmtZj
Ad/WMx8xvYPr7yO3gvQMSwOPrSIiGR36huT7l1G7gXuThBWuPNy0B2GmV9afIUkH
6hGuch9dFqWRH2APi7GCvmyVit2t/k06AO7N/ERyVeKJeEnbNUh39hruRciJELyt
qLxo2wkD7LoYCdpGJHzOMQYTnSWOMkZ6zcT/iTbkac66t0efwWzV+HZqD3HaJTi4
EymAD9DZ9Hkc1j9Lir1wOx88le4KFBODTIWSslzrxdeSJcJkLeaB2/bLYlZq452M
ygAYNKzWbYaIXHv0Knn/dkhwzPBdoKRRoWfFdWkBk3e/r/9EAUa7cchc/SVNCQ1s
l/SN0lORd7pqdM7BAubZQ7tmVHzmlTHkjIDF94s0oiFWoA1Rb6TfXAr1RO1LMvSW
OgL9prg0x47WPk6Z67AofGVEjLDD32I4Aond2HS72swnAoVU4FZYVrCEOfqMGbr1
PztntXzcms4dxA==
=b5b9
-END PGP SIGNATURE-

Re: merged /usr

[Simon McVittie]

On Mon, 19 Jul 2021 at 11:33:49 +0200, Stephan Lachnit wrote:
> We could start with collecting the packages that install to /bin*
> instead of /usr/bin, and adjust the packaging so that they don't do
> that. [...] At this point, it shouldn't
> matter if you run a merged usr system or not, or am I forgetting
> something?

This would have part of the practical effect of merged-/usr, but not all
of it. It could still be a useful step forwards, but we should not view
it as being entirely equivalent to merged-/usr.

What we have now on unmerged-/usr systems, using /bin/bash and
/usr/bin/perl as examples of Essential programs that use the two paths:

 bashperl
/bin/foo   physical location   (does not exist)
/usr/bin/foo   (does not exist)physical location

What we would have on unmerged-/usr systems if we do as you suggest:

 bash perl
/bin/foo   exists via symlinks  (does not exist)
/usr/bin/foo   physical locationphysical location

Merged-/usr for comparison:

 bash perl
/bin/foo   exists via symlinks  exists via symlinks
/usr/bin/foo   physical locationphysical location

As you can see from those tables, a package that hard-codes /usr/bin/bash
is currently considered broken, but would work with either your proposal
or merged-/usr. Conversely, a package that hard-codes /bin/perl would
still be considered broken, would *not* work with your proposal, but
would work on merged-/usr systems.

(Obviously the same applies when considering hard-coded paths in /sbin,
/lib, etc. instead of /bin, in particular the ELF interpreters like
/lib64/ld-linux-x86-64.so.2 that are hard-coded into every
dynamically-linked executable)

Meanwhile, various shared libraries are also moving from /lib to
/usr/lib.  One potentially serious problem with that on non-merged-/usr
systems is that we still don't understand why the bugs discussed
in https://bugs.debian.org/911225 and https://bugs.debian.org/949395
happened, and a similar thing could potentially happen to /lib libraries
other than GLib. The script that GLib uses to work around this is generic,
and could be used in other affected packages if required, but it's larger
and more fragile than I'm really comfortable with.

(Merged-/usr systems cannot suffer from bugs like the ones discussed in
#911225, because the paths involved are the same directory.)

smcv

Accepted emscripten 2.0.16~dfsg-1 (source) into experimental

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Jul 2021 12:20:59 +0200
Source: emscripten
Architecture: source
Version: 2.0.16~dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Closes: 975069
Changes:
 emscripten (2.0.16~dfsg-1) experimental; urgency=medium
 .
   [ upstream ]
   * new release
 .
   [ Jonas Smedegaard ]
   * update and unfuzz patches
   * copyright info: update coverage
   * install new executables emdump emprofile
   * update source-only part of upstream source-map script
   * merge patch 2012 into patch 2004
   * update patch 2005 to use LLVM 12 (not 11);
 (build-)depend on versioned clang lld llvm;
 improve build-time tests: enable tests related to error handling;
 closes: bug#975069, thanks to Sebastien Jodogne
   * stop fix executable bits for JavaScript files
 no longer included upstream
Checksums-Sha1:
 e8703f6b4794212e8b0876d4a1a51a5fb81cbcbf 2534 emscripten_2.0.16~dfsg-1.dsc
 48ce4d62a8ecd8c08597a037cf39558cd897247e 17812504 
emscripten_2.0.16~dfsg.orig.tar.xz
 38ebd39718b680bf81eca93228bffb9d2fa8ef64 76472 
emscripten_2.0.16~dfsg-1.debian.tar.xz
 7ff162fc4e3e5465b347e65dd16642e760838aa2 14838 
emscripten_2.0.16~dfsg-1_amd64.buildinfo
Checksums-Sha256:
 35d5650e9aede0330d9e051685fba5699cb85984819167858c1411da035015ff 2534 
emscripten_2.0.16~dfsg-1.dsc
 a36c767d0e8b771db5a4b543eb649e3b33c12f56c406d5ba8eee7c7feb383282 17812504 
emscripten_2.0.16~dfsg.orig.tar.xz
 62a440c3e3a24341f1ebf2a86a777518eed6d5a778aff540eae431229ab075b2 76472 
emscripten_2.0.16~dfsg-1.debian.tar.xz
 977a28dc1c1f729da3997d5b16012c3f3773e5c76ab7d7a63e5a17721362765d 14838 
emscripten_2.0.16~dfsg-1_amd64.buildinfo
Files:
 cdb1404e7297b52e36fa8f3c51e0f1ed 2534 devel optional 
emscripten_2.0.16~dfsg-1.dsc
 d75c98e161f830c635e6e5595c6f1f45 17812504 devel optional 
emscripten_2.0.16~dfsg.orig.tar.xz
 620f0460df6c0b38344edccea5402c4d 76472 devel optional 
emscripten_2.0.16~dfsg-1.debian.tar.xz
 8001db6ac4cd0d02f99926453bc728c1 14838 devel optional 
emscripten_2.0.16~dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmD1VtcACgkQLHwxRsGg
ASHTrw//duIA9wntL/ONm7Y1eA5MyirmlLeUKoS7VmoynPGspKZgPm0fJfT4adz3
1JGG8GWYgtuafqZw0/OFd+Qad5DyT1TckMSWzOFYO3/2HyKFPDDJB7wj39DL5qYv
Law9Swzy0pJErvthTIsTOIRUsd2iUa9o5U9WEvA+riBKmHgZs4+mog24vf/+G2iO
pXedNf+qXBv49Yf6CZqG8jMEvWbghbky87cxXjB+aJjJGpzjnovthSY6w76mbgJv
cmziszTFUUCtYmILdXR0Z322liZEoTjfUycBIej/W0xGDZNwUdAYGMC5zI4sMJSg
Um+Qge1hWYfh7DOUVFyv0DFK3ApZWJpPanPppqaj2YQa562uUOw9eJfF8GqCS/C7
MZ9w3vT+NMy5nU84lWCl/H0YQndk+HEQKiPFoTjCD1muvM5ppCMbtXEmPhaOB3e7
D9V7KyMmOcKGesoPQ1caLzeQ0eUjkle/xrHcIShdT/HAW9Ai+PfmvxMeP0ghyDM+
D47aUpLimfDQCywwMA15LK+HfDal5/1jDxntWa9WNECSEolNqw24M5WNXCUSvf0z
owP1KXT1L8SHDJpLpbyGJVZ7xtYABtflZ31obsybsaKlqp4wBWVA9JbH7uLsU8AM
VXyi7K3O6ngPC1XJDNZksOAT54zopOgVJHX4mtASB407piZWquU=
=5MR1
-END PGP SIGNATURE-

Re: merged /usr considered harmful (was Re: Bits from the Technical Committee)

[Stephan Lachnit]

On Mon, Jul 19, 2021 at 3:37 AM Guillem Jover  wrote:
> What I've also said multiple times, is that
> merged-usr-via-moves-and-symlink-farms could have been implemented in
> a fully automated way, by debhelper, w/o requiring any maintainer scripts,
> all with full cooperation and managed by dpkg, with .debs shipping
> actual tracked pathnames, if it had not been for the mess required
> by merged-usr-via-aliased-dirs. :/

Maybe I get this wrong, but I don't think this conflicts with the
decision from the TC.

Until Debian 12 gets released, we have a lot of time for a transition.
Maybe we should start discussing the transition and less whether or
not we do it, as this has been decided now anyway.

We could start with collecting the packages that install to /bin*
instead of /usr/bin, and adjust the packaging so that they don't do
that. Of course, we would need to add a maintainer script that detects
un-merged usr and creates a symlink. Actually, I think it would be
enough to just let debhelper detect if a package installs to /bin, and
adjust the package automatically. For packages not using debhelper,
lintian can add a warning if the package installs to /bin. After all
packages that installed to /bin have been rebuilt, nothing would
install to /bin except for symlinks. At this point, it shouldn't
matter if you run a merged usr system or not, or am I forgetting
something? IMHO it would make way more sense to discuss how to merge
usr once the packages are fixed.

Anyway, I think the discussion made clear that we shouldn't
immediately start with merging usr once bullseye is released, and I
wouldn't interpret the TC decision as such.

Regards,
Stephan

* using /bin as an example, same goes for /lib etc

Re: merged /usr considered harmful (was Re: Bits from the Technical Committee)

[Marco d'Itri]

On Jul 19, Marc Haber  wrote:

> I am NOT looking forward having to manually convert legacy systems to
> merged /usr and I do sincerely hope that Debian will choose a way to
> get away without throwing away systems that have just a small /, still
> supporting a dedicated /usr as long as it's mounted by initramfs. I am
They cannot be supported without keeping a lot of unneeded complexity 
around, but there is no reason to reinstall them: you can move / inside 
/usr instead. You may use either sash or a live CD image.

> I also believe that smaller file systems are unlikely to break and
> that a system that can boot up to a ssh-able state even with a broken
> file system is way easier to fix. We have taken a huge step back in
And "apt install grml-rescueboot" is even better.
Also, with merged-/usr you may keep your *whole* OS in a read only file 
system.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Accepted emscripten 2.0.15~dfsg-1~rc1 (source) into experimental

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Jul 2021 01:26:05 +0200
Source: emscripten
Architecture: source
Version: 2.0.15~dfsg-1~rc1
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Changes:
 emscripten (2.0.15~dfsg-1~rc1) experimental; urgency=medium
 .
   [ upstream ]
   * new release
 .
   [ Jonas Smedegaard ]
   * unfuzz patches
   * update source-only part of upstream source-map script
   * extend patch 2005 to revert passing LLVM option legacy-pass-manager,
 not yet supported with LLVM 11
   * tighten (build-)dependency on binaryen
Checksums-Sha1:
 ae6f60eb16c6d308c4ab7107e892ceb628f838dc 2577 emscripten_2.0.15~dfsg-1~rc1.dsc
 3b5b09630d11278c042c66742cd62f9d132e3949 17847272 
emscripten_2.0.15~dfsg.orig.tar.xz
 aec717914cb682bc4db1b9fe0a658a0068d8ded5 76264 
emscripten_2.0.15~dfsg-1~rc1.debian.tar.xz
 0a3610dd6899bec9ab281bafb61335f248ba0a92 14944 
emscripten_2.0.15~dfsg-1~rc1_amd64.buildinfo
Checksums-Sha256:
 3994398d2f22595cbf17a3bc81f544bfa735d657f19993e60f60a72bb4134465 2577 
emscripten_2.0.15~dfsg-1~rc1.dsc
 982d4bdcfaa9a08193b8ad3bfe43493b968374a296a29fb45483d6067dbb5ee0 17847272 
emscripten_2.0.15~dfsg.orig.tar.xz
 3b76f246f0336e753b212d41a428615fd006006b5ff362fe4e8935c541e03e31 76264 
emscripten_2.0.15~dfsg-1~rc1.debian.tar.xz
 76170c35445eb86bd1b3b8cfbebd070755b3358a3eec79c12aff33bf43337cf8 14944 
emscripten_2.0.15~dfsg-1~rc1_amd64.buildinfo
Files:
 594db6139ece8de7ad4cf9cef8aa1482 2577 devel optional 
emscripten_2.0.15~dfsg-1~rc1.dsc
 926a4a8cae00645ea41ca5cf6bdf7230 17847272 devel optional 
emscripten_2.0.15~dfsg.orig.tar.xz
 f912087f0941c851ec2389afe1aa59af 76264 devel optional 
emscripten_2.0.15~dfsg-1~rc1.debian.tar.xz
 592b8b30e2a9274442e59f535a34eb2c 14944 devel optional 
emscripten_2.0.15~dfsg-1~rc1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmD1LscACgkQLHwxRsGg
ASGqOQ//VbL166ePuyfYJb+Y38GCxboiesjnfDgLcmENRLw+6fi9U31Kbo4G2y2u
A0DmOuFeAcAkPV525QSn1rt4/TdstTT8n9yoN0v2FpM4q74iq3VnyLK50OQtwPjV
9R0Th5peqyDc8ejTTC8HKrLsKVmfvtaPWDR01jSQr+bcvIpkOEV0AC9tNaPmpKGX
lMqWnq2kQw9fMcByy4cr74oJlyr5tbxxD0GhB3BR0eZiIKUt/iKABp31Nbk5Paqx
n/6uYjyoybelbtn7AkS8ASUELDsPMGvuQeR24D2zqJSFm17EAEduy/I3JV2m/NEg
VJ2otD3ItZbzOVLbyy+m700Sb4KVocRaM2W9juB7IGGbj7u3fgQMC1uRGCXyGp93
qS5VUyVXxUs8reIl0F5D3PexCDrdBco2yhUiI8Z7oRI2dNu0WXzcQ3C1wNB+bwOz
xuZDhkBbUXbHzdvWvDa+LBrfaKSNjGpEw/ys2k5urtIMM2sNmE8qcH1FP5fb0nh7
j2odme1M5059W5YZS2QvwUCiqLy0KTVaa7TYWVr71pFAuxjNBWQ5XUuWh1oY2qW7
T/Q0LRPTUf3bGAqgNLYbnJ5bOadunXstdEsHBmDjoz+8znCZLrYgtyf9u5eYlscN
F+Thq/G6vEcvrGB6WcrDS17XAgyyv3PVBWnb/dzFpmjhEuC7Bt4=
=9j02
-END PGP SIGNATURE-

Accepted virtualbox 6.1.22-dfsg-3 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Jul 2021 09:28:22 +0200
Source: virtualbox
Architecture: source
Version: 6.1.22-dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Virtualbox Team 
Changed-By: Gianfranco Costamagna 
Launchpad-Bugs-Fixed: 1933248
Changes:
 virtualbox (6.1.22-dfsg-3) unstable; urgency=medium
 .
   [ Dimitri John Ledkov ]
   * Drop virtualbox guest modules dkms and sources, as in Ubuntu and Debian,
 all kernel flavours provide those from the upstream kernel since at least
 focal 20.04 LTS.
 Thus these are not needed anymore. LP: #1933248
Checksums-Sha1:
 5c6a1dddfbacd0da09ae9a45b43c30582988d461 3438 virtualbox_6.1.22-dfsg-3.dsc
 0d9a0ef124e8e61761be548952a4d6ede8f67718 87700 
virtualbox_6.1.22-dfsg-3.debian.tar.xz
 52aa11b90e31800dffcf87fbe9fd618bdd1d66ab 23494 
virtualbox_6.1.22-dfsg-3_source.buildinfo
Checksums-Sha256:
 4f1eaa474272c7af5631000b62f21ec83c2f2b4fec663fa2948cd819e9696d9b 3438 
virtualbox_6.1.22-dfsg-3.dsc
 85ca3dac7ff26c17ffa57d06fef3b694b73dabbbcf637801ee547e90bfefb3ea 87700 
virtualbox_6.1.22-dfsg-3.debian.tar.xz
 69c0a60e77d23ba49f18074eae27a5c923577b80d5c25e7aa57cc0596d6d604f 23494 
virtualbox_6.1.22-dfsg-3_source.buildinfo
Files:
 c1792d0c983eadbd192a393c41f1e081 3438 contrib/misc optional 
virtualbox_6.1.22-dfsg-3.dsc
 c38578d647a0202cfd3471a97ef06200 87700 contrib/misc optional 
virtualbox_6.1.22-dfsg-3.debian.tar.xz
 e6bd17a3e9b7fff2c5cb88efc8bd6df7 23494 contrib/misc optional 
virtualbox_6.1.22-dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmD1KqIACgkQ808JdE6f
XdkMaBAArHuCRS+ltI8r/Wxkp7dADonw9Z2FSIWUAjLql3VCKcO1H60QFNltVxi3
6r+i6P0N8mwz9xLFFhSQb+NPTYxaawNQADUuzec9wg31eSxq9zhLUHVfQrcsoIcd
fU6MvfCx8WRBNw1UjjBLjd3AaGbinNit7PxfgvDhnzVSoumUG7P53P/brazW6m3w
YaQTgNi1iqTkIHAhyWBQrbe2Sv2j0TIi+PdZMel+ftGTC/ls4oJuT0AlFOKnaMst
8VBUSP/UOlNv482TKH2ufizHram9EQLFJpYg8fIyD+1iokgSmXq96IFkPU8KrXUj
dpQinrsXn3CYo59zbDsJshr2OX9HdNqizDC+epnsZJF+vCnlsPvhycrEo/fHCur4
2l1m05cdnADitmrc3/YgNfD2YJp4ys8zv7TtRBI+zRw7hCmlViSyc0eZbwBAQD2y
XfAjQT/QHWSyFyGT63ppA8+8JtS9oOHpB2j0hOiNoXVCINxDx8bxtg73braCi2x2
UpQj6LgeuFN6UVl4XegjYcUj9I0evmt4Vl8HqN3FPyI7MskhSzY9BDeEvvKmfdn+
yDQZLptvyHfsXEHP6kCwMPqgCddVww5aipqftl6T6L6nYvF0ZWkMMTAaH6mnUotU
NcaLHKpNaYOMCOL9ukqeT4FypofWixe9DYICnEdENLFZFLXH/KI=
=kVB5
-END PGP SIGNATURE-

Accepted poedit 3.0-6 (source) into unstable

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Jul 2021 09:13:46 +0200
Source: poedit
Architecture: source
Version: 3.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian l10n developers 
Changed-By: Gianfranco Costamagna 
Closes: 989949
Changes:
 poedit (3.0-6) unstable; urgency=medium
 .
   * Remove icon-theme.cache file from deb files (Closes: #989949)
Checksums-Sha1:
 40245cc8c6dc6333908af847b0550f2abb2cd1a7 2376 poedit_3.0-6.dsc
 b12ea724ffb157e96516920b55bd5302cdd45c4e 21968 poedit_3.0-6.debian.tar.xz
 6d1f01c4088bab8165bf0512359148678999541e 20586 poedit_3.0-6_source.buildinfo
Checksums-Sha256:
 ef7c32198ab0b4e28cce3e93f67d7b825ad2bd1d656786aa326611242bb8a045 2376 
poedit_3.0-6.dsc
 210dfeb1aeb4f1b2924e27b430ca81e4a9113b24c6bddb91beda348100603db2 21968 
poedit_3.0-6.debian.tar.xz
 881433067d2067e93ed44cce4b714cd9282a515577c3265524b07265e357fa4a 20586 
poedit_3.0-6_source.buildinfo
Files:
 e78dff027f8c1dec3d0830ff2a03909b 2376 text optional poedit_3.0-6.dsc
 d9ac89cfcaee1723ef6613673f1cb3be 21968 text optional poedit_3.0-6.debian.tar.xz
 46ad3ae3ab24506d090e9b709a8fa1c4 20586 text optional 
poedit_3.0-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmD1JkAACgkQ808JdE6f
XdkugA//YEBoccxlNAF2Uoa0Rxz2GUvhBVHaChFvbGBJOgm4lBhcCNGS/VOM1KJB
difl+XJFucFsbDV8xUfE4GrdCEC6USKw7uQhrsuoiSwfl2slqPUnpxh1Qhy/UYO6
NJ934bI71ykZ5pBSj94liVZSvIZ2EB3Y4UYPbAwCGgsOJ5O/wSnwaevXAaHl2yNf
SK4I4lyvUKNpNZJ2xgQWYHU1HCXLozeoZosa7zY1cVhgH2aeq5A+P9xlcAIn1tiN
mnC2xaBCTG8JRlws46TOXCj2e23mdFuF31yGpmeptRlUey+eWuC8d0sKbc5dEAtG
6JxD4KmSRLTy4wrSVQ8Dxk13XMqZ5Bh7YVpO0opH9/lVG/e77jhhTwV37A9o+5vX
S6oSzRU++rLgnaeVpP+9jGECfLrYr/FBOWaACpYJpgdytXyM3pItSqyfvqzixEY0
1W7LzmV4Gb/XxHKTURIbq9n+T2OTn6wtj5DWbSTFGC90XAY24/tlgd1OTOlMVz9z
fMvFiEyd/CAUofgE207z3qVVfSuW9x/gCNCPyUDReGVXNdS19AFt6dy+HEPvXYr9
YB4IP6R1/BB9Zoxt5koXi5wdrvamqDgEgDcl8lwCaY5r1IAyG8Hqf+inr8/YgojG
1RZG67W5ZJRkhWuE6XeAIyFeBQFzchabOkNLLiLTuiXiu8AN1gY=
=szAL
-END PGP SIGNATURE-

Re: merged /usr considered harmful (was Re: Bits from the Technical Committee)

[Gunnar Wolf]

As I said, on a separate mail...

Marc Haber dijo [Mon, Jul 19, 2021 at 07:12:24AM +0200]:
> In an ideal world, would the package manager not be a service utility
> to SUPPORT policy and adapt to changing environment contitions instead
> being a showstopper for innovation?
> 
> Who is the dpkg maintainer to challenge the decisions of the entire
> project? I fully understand that there is only ONE dpkg maintainer,
> but a utility THIS central to the entire ecosystem not being team
> maintained is a HUGE part of the problem.
> 
> And no, I cannot help and no, you wouldn't want me to write a single
> line of code in a package THIS central.
> (...)
> Would it not be dpkg's job to work around these flaws? It's not that
> every other component of a Debian system are perfect.

FWIW, I mostly agree with what you say here -- If the project decides
to a new standard (and, in this case, it has via the TC's decision --
which can of course be repealed by GR, if things come to that),
packages that behave differently... are buggy and should be fixed.

Of course, dpkg is a very special case for obvious reasons; I did try
to reach out to Guillem when we started discussing the bug at the TC,
and was disheartened by his harsh reply basically negating all
possibility of discussion because his non-belief in the TC itself.

There are technical issues that this migration will bring, and yes,
there is a nonzero chance some users will be bitten by the dissonance
between dpkg and reality. But after two TC bug resolutions (#914897
and #978636), and after lots of bytes have been spilled by various
people, I can only see work has to be put into making possibly
problematic cases less likely -- rebuilding and checking packages
don't ship files in the root directories will cover a great deal of
the distance. If aliasing the directories via symlinks is so messy,
well... we should focus on the root cause, and fix the rasons for it
to be broken as much as we can. The symlinks could probably be an
unconsequential footnote if this is done right.


signature.asc
Description: PGP signature

Re: merged /usr considered harmful (was Re: Bits from the Technical Committee)

[Gunnar Wolf]

Sorry to single you out here, Marc -- This goes to many people. This
goes, in fact, to the discussion itself.

Marc Haber dijo [Mon, Jul 19, 2021 at 07:12:24AM +0200]:
> In an ideal world, would the package manager not be a service utility
> to SUPPORT policy and adapt to changing environment contitions instead
> being a showstopper for innovation?
> 
> Who is the dpkg maintainer to challenge the decisions of the entire
> project? I fully understand that there is only ONE dpkg maintainer,
> but a utility THIS central to the entire ecosystem not being team
> maintained is a HUGE part of the problem.
> 
> And no, I cannot help and no, you wouldn't want me to write a single
> line of code in a package THIS central.
> (...)

While I agree with what you write here (will answer on a separate
mail), I'll ask you -and everybody- to please moderate the tone. It is
frustrating to speak in different wavelengths and not be able to hear
one another, but we are not going to get anywhere if we just SHOUT
LOUDER using our same wavelength. We must find some alternate
frequencies to get to a constructive situation.

Accepted binutils 2.37-1 (source) into experimental

[Debian FTP Masters]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Jul 2021 08:11:10 +0200
Source: binutils
Architecture: source
Version: 2.37-1
Distribution: experimental
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Changes:
 binutils (2.37-1) experimental; urgency=medium
 .
   * binutils 2.37 release.
Checksums-Sha1:
 b2b3311a1c567c1f35679f104a24dc0a378d9805 11273 binutils_2.37-1.dsc
 8515ac588ec51d2c9b505a4adbcc69a3fb965783 24345744 binutils_2.37.orig.tar.xz
 df7861b3220fc9840d311b454d1570416c4302f8 98824 binutils_2.37-1.debian.tar.xz
 b66b4447e21684cbf68cea726b9e54efeeb7bb7a 6324 binutils_2.37-1_source.buildinfo
Checksums-Sha256:
 df43be3bd5dfa33fa3af0a3853949ecdaf66c39c2e4ef6709721fa8fd1f5ff6e 11273 
binutils_2.37-1.dsc
 220124d1e23f360a3be80b2e2506b379164b0832cc6ff2767360e6a3a747b914 24345744 
binutils_2.37.orig.tar.xz
 d7c807d235726d92dca5bccc4924d2114690f1514f10602266ddefcac3faafa6 98824 
binutils_2.37-1.debian.tar.xz
 da7eb372d130d888f2a5b2e8d8c9dbf3a1b32794d2693e8961d30390ee6a8c7b 6324 
binutils_2.37-1_source.buildinfo
Files:
 a433104041002b310f73d4accefbb5ce 11273 devel optional binutils_2.37-1.dsc
 de8f34922e0731e1aed7cad767337f97 24345744 devel optional 
binutils_2.37.orig.tar.xz
 56f5f0ce6f6ff2eece8c92fec545bebd 98824 devel optional 
binutils_2.37-1.debian.tar.xz
 74265e7b43eb8d89bf70e0ddc6185b58 6324 devel optional 
binutils_2.37-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmD1GToQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9R1dEADbZjhjqFHESvdchLsLGhu0esOyaRCCdzjE
k0HTul2ga/A+u65iq4k6RV7sSD8G/vTvQgmIfy8aNKqQZHsOlaacwqDCqYmed6DM
/BRG9pLkiS6DFUz9R9OK4lfxoVjlnohgtUK0+YtXNhgVBy1uLrmvCIipj8CNEaUR
dEWY48ujfNTMmKZhRUk0PBHSbG4I1dd99+UkkoNnIemo28g+pvNsUubMr+6klfdS
B4Ag63kw0IfFKKgqOZk2H3mSX95MPWAvT1nsrqUMDuxWO0txpJ+D+5d3VqFfnSiJ
tC5XeimUKzwWAP+gpVgPhXudOgsl6/krbd8K5pTQDquEKLA5CikWfFtlr62pdBvA
iwS1IsYy7JU3vWOgZlgCF1gqXzsjFChk0hfEFOepUYM6ETF1n9olwbl8tUOvY9kz
zQaasQka8wnfN5QeI2xqhrPBY6njeOckieiZ8ZPPKc9a/U2IghZLFmxaNwR4ZBu0
m1KxskUMtcf7LZf8rLhzSQrFPy20Unp9IZ9+DF3hmz0p5QY4gDLQu3rkWhzZqZop
FAdyEPzDMaEoGPnPyv6jDNQzgCm6Il+OOynqVkZjToSBYLKAUFtCNFUevPXc6c3w
aCumUvMTWEFoJQpai3UsbodPkW2MewV/xMt0gRPj5zCK1vraZS7jliN7NFgUBp3h
hLlqH4hsbw==
=+qny
-END PGP SIGNATURE-