Maybe we could backport these changings to bullseye manual too?
There is no "bookworm-only" material until now, and we have no bullseye branch for the manual currently, probably it's a good time for that now?
Accepted:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 29 Jan 2022 23:37:50 +0100
Source: installation-guide
Architecture: source
Version: 20220129
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team <debian-boot@lists.debian.org> Changed-By: Samuel Thibault <sthibault@debian.org>
Closes: 408643 603444 604839 838948 988472 992034 992183 993475
Changes:
installation-guide (20220129) unstable; urgency=medium
.
[ Holger Wansing ]
* Update supported devices in Bullseye for armel.
* Include a note on how to change init system during install. Closes: #992034
* Add missing preseed line for apt-setup in example-preseed template.
Closes: 992183
* Don't call 'Linux' an operating system, use 'GNU/Linux' instead.
Closes: 993475
* Some clarifications on preseeding. Closes: #603444
* Preseeding: add a comment about automatic network configuration being the
default method. Closes: #838948
* Document the new 'avoid the tasksel prompt' preseeding feature, introduced
in pkgsel 0.69.
* Overhaul of chapter 'Preparing Files for USB Memory Stick Booting'.
Closes: #604839, #988472, #408643.
* Some corrections/optimizations in doc structure related to graphical
installer.
* Consistently use 'text-based' for the text installer (newt frontend)
instead of 'character-based' or 'textual installer'.
* Improve description of popcon functionality.
* Remove mark for Spanish being an unsupported/outdated translation, thanks
to eulalio.
* Document how to preseed disabling of 'cdrom' sources.list entries for
DVD/BD installation images.
.
[ Samuel Thibault ]
* Provide more details on the textual front-end keyboard shortcuts.
* Fix partman-partitioning/choose_label type to select.
.
[ Stéphane Blondon ]
* Update CSS for notes, warnings and code block
.
[ Updated translations ]
* Catalan by d
* Chinese (simplified) by 吕文彬 and Boyuan Yang
* Dutch by Frans Spiesschaert
* German by Holger Wansing
* Italian by Luca Monducci
* Japanese by Hideki Yamane
* Portuguese by Miguel Figueiredo
* Romanian by ionut eugen
* Spanish by eulalio
* Swedish by Luna Jernberg
Checksums-Sha1:
fc116e52e53bd2f85b7039464c5dda2707df7c2a 2843 installation-guide_20220129.dsc
b2ad855aaadf77d80f8b167f33221a50ada4e139 3781500 installation-guide_20220129.tar.xz
2175b110c8b2beb771ef79dcecc72e2554e220f6 14807 installation-guide_20220129_amd64.buildinfo
Checksums-Sha256:
d43727fca414b433e969b65d35b2082ce6fff4266f52e3d3dd9b6268746b3e47 2843 installation-guide_20220129.dsc
ddb01f4057a7cf93f2dd19a77893e9135adf0a20043dc99029cfde3e1b43566b 3781500 installation-guide_20220129.tar.xz
edb2281b9f06fe4ad6c73085e2a8c9161dece309ce5754c5907e2d6a5e151243 14807 installation-guide_20220129_amd64.buildinfo
Files:
895181f326d8155e39340d4be2a60ffd 2843 doc optional installation-guide_20220129.dsc
828e7f886b9ec59eb92d8be23aa98667 3781500 doc optional installation-guide_20220129.tar.xz
f8b124059c5580ed9424388ebf058240 14807 doc optional installation-guide_20220129_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEi6MnFvk67auaclLJ5pG0tXV4H2IFAmH1zfQACgkQ5pG0tXV4 H2Lv0RAAjH8GbtSJAAAJ71P4NrIkcmfKseGgY531onJBrZl79VHTTXMEi7q7NGgT cuTc5GF6fgUCIkBrpm/uJ4KhIgG4/0hAzB96nz+Y7v+idSjae0ugvYHQAOT+QNhQ 117EuwUhgpixNLNCDNurvrgjSCM4xpQVoSSRYp4rrMBOBIewRcLyTb1KtWifDN/s /yGjCMCAvMPi5KRld96cNxTXKFa66isI954sAugpt6o+goCL86iOFCd663dsldrY QZHCOm9jT13L02HvGhH5rsOWusr3s1RYPu5tOlYh3oHpSyYV3rmDpNB+WzajSWHb 11xSyGUsI5MT76iEu/xGDDiZe9LPISO8cLnwiafYyBtVVWs+wZaSpDRKswSZ0hpp atGNVAZUJ8bLG1yCPc3rKyOPoVJCnNTgiOPrVPClsWiGa8+pzY3H58gdN93w/R1R 0qbFa0MmwzmRV0j82tXgmDQmwCM2PXa8Ams06KY/Xtetk51cV6vs3yRchTwAyhME OJHqeQspBS7X80lq04rtqPizZ1qmTFf8Z1jU32cDAJtoVSvtpWSSgKgkGqln52bD 7yZRyDkYF+HENqS/Higm2f0PDo027/+vRhQqS1BwW4AyQqejDgDU1LNFzPuWnNVj jU4raBtgK7aAsnrmOEgHdfLooRjKAIxEbcNvpuWZgCjezQrAPUM=
=r2jO
-----END PGP SIGNATURE-----
Thank you for your contribution to Debian.
What's needs to happen now?
I cannot do that for installation-guide anyway, but just for learning:
- Upload
- Uploading to which distribution is controlled by the entry in the
first line of debian/changelog, right?
What needs to be used there? "bullseye" - "stable" - ... - ?
- Anything else needed?
- Are there any restrictions for such procedere, like: only DDs with full
upload rights can do that?
Or could I do that for tasksel for example? Remember, I'm only DM, with
upload rights for some selected packages (d-i related).
Holger Wansing, le dim. 30 janv. 2022 11:13:03 +0100, a ecrit:
Maybe we could backport these changings to bullseye manual too?
There is no "bookworm-only" material until now, and we have no bullseye branch for the manual currently, probably it's a good time for that now?
We can do that indeed.
Holger Wansing, le dim. 30 janv. 2022 11:59:18 +0100, a ecrit:
What's needs to happen now?
I cannot do that for installation-guide anyway, but just for learning:
- Upload
- Uploading to which distribution is controlled by the entry in the
first line of debian/changelog, right?
What needs to be used there? "bullseye" - "stable" - ... - ?
IIRC it's a normal stable-proposed-update, so that'd be bullseye.
- Anything else needed?
I guess the scripts for the website will automatically get the version
from bullseye, but TBH I don't remember :)
- Are there any restrictions for such procedere, like: only DDs with full
upload rights can do that?
Or could I do that for tasksel for example? Remember, I'm only DM, with
upload rights for some selected packages (d-i related).
IIRC DM can upload proposed-updates for their packages too.
- Are there any restrictions for such procedere, like: only DDs with full
upload rights can do that?
Or could I do that for tasksel for example? Remember, I'm only DM, with
upload rights for some selected packages (d-i related).
IIRC DM can upload proposed-updates for their packages too.
Ok, I will give it a try for tasksel then ;-)
Holger Wansing <hwansing@mailbox.org> wrote (Sun, 30 Jan 2022 12:38:37 +0100):
- Are there any restrictions for such procedere, like: only DDs with full
upload rights can do that?
Or could I do that for tasksel for example? Remember, I'm only DM, with
upload rights for some selected packages (d-i related).
IIRC DM can upload proposed-updates for their packages too.
Ok, I will give it a try for tasksel then ;-)
I have prepared tasksel in git for such upload (created a bullseye branch
+ adapted the changelog entry with the needed version/upload-target).
Could you take a look, if all is fine?
Hello,
Holger Wansing, le dim. 30 janv. 2022 13:19:26 +0100, a ecrit:
Holger Wansing <hwansing@mailbox.org> wrote (Sun, 30 Jan 2022 12:38:37 +0100):
- Are there any restrictions for such procedere, like: only DDs with full
upload rights can do that?
Or could I do that for tasksel for example? Remember, I'm only DM, with
upload rights for some selected packages (d-i related).
IIRC DM can upload proposed-updates for their packages too.
Ok, I will give it a try for tasksel then ;-)
I have prepared tasksel in git for such upload (created a bullseye branch
+ adapted the changelog entry with the needed version/upload-target).
Could you take a look, if all is fine?
debian-release wants proposals for stable to be already in testing, so notably the CUPS change has to get tested there first.
In general 3.69 -> 3.68+deb11u1 update looks wrong, it has to be
increasing :)
Samuel Thibault <sthibault@debian.org> wrote (Sun, 30 Jan 2022 13:23:25 +0100):
In general 3.69 -> 3.68+deb11u1 update looks wrong, it has to be
increasing :)
Hmm, increasing is of course right.
However, I guessed this goes per distribution, so:
current version in stable is 3.68, that's why I chose 3.68deb11u1.
Looking at the version history in stable, that would be indeed an increase.
?
So, if I understand that correctly:
- I do an upload to unstable now, which is then 3.69
- Then I can upload to stable, which then gets 3.69deb11u1
Would that be correct?
Holger Wansing, le dim. 30 janv. 2022 13:42:10 +0100, a ecrit:
Samuel Thibault <sthibault@debian.org> wrote (Sun, 30 Jan 2022 13:23:25 +0100):
In general 3.69 -> 3.68+deb11u1 update looks wrong, it has to be increasing :)
Mmm, sorry, even if that's what caught my eye, this isn't an absolute
rule.
Hmm, increasing is of course right.
However, I guessed this goes per distribution, so:
current version in stable is 3.68, that's why I chose 3.68deb11u1.
Looking at the version history in stable, that would be indeed an increase. ?
Yes, and that's usually what happens: we upload to stable some patched versions of what is already in stable.
So, if I understand that correctly:
- I do an upload to unstable now, which is then 3.69
Yes.
- Then I can upload to stable, which then gets 3.69deb11u1
Would that be correct?
It would have to be less that 3.69 actually, so that on upgrading to
bookworm the package gets "upgraded" to 3.69.
I guess best would be 3.69~deb11u1, to say that it's essentially 3.69,
but before 3.69 from bookworm.
I guess best would be 3.69~deb11u1, to say that it's essentially 3.69,
but before 3.69 from bookworm.
Hmm, my intention was to only bring one of the latest changings into stable (the "install CUPS on desktop systems" part), not everything.
Samuel Thibault <sthibault@debian.org> wrote (Sun, 30 Jan 2022 14:26:52 +0100):
Holger Wansing, le dim. 30 janv. 2022 13:42:10 +0100, a ecrit:
So, if I understand that correctly:
- I do an upload to unstable now, which is then 3.69
Yes.
I have prepared this upload in git now.
During this, however, I noticed that I cannot do this upload myself,
because it adds new packages to the archive (only task-* pseudo-packages,
but new packages anyway), and so that requires an binary upload, which I
am lacking permissions for.
Therefore, could someone upload tasksel 3.69 for me, please?
Holger Wansing, le dim. 30 janv. 2022 14:44:18 +0100, a ecrit:
Samuel Thibault <sthibault@debian.org> wrote (Sun, 30 Jan 2022 14:26:52 +0100):
Holger Wansing, le dim. 30 janv. 2022 13:42:10 +0100, a ecrit:
So, if I understand that correctly:
- I do an upload to unstable now, which is then 3.69
Yes.
I have prepared this upload in git now.
During this, however, I noticed that I cannot do this upload myself, because it adds new packages to the archive (only task-* pseudo-packages, but new packages anyway), and so that requires an binary upload, which I
am lacking permissions for.
Therefore, could someone upload tasksel 3.69 for me, please?
I have uploaded it.
I have uploaded it.
It's in!
Now we have to wait for it to reach testing before submitting the
changes for stable.
Now we have to wait for it to reach testing before submitting the
changes for stable.
If I remember correctly, there's a source-only upload needed for
tasksel to migrate to testing after the binary upload.
I have uploaded it.
It's in!
Now we have to wait for it to reach testing before submitting the
changes for stable.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 299 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 75:56:32 |
| Calls: | 6,695 |
| Calls today: | 5 |
| Files: | 12,228 |
| Messages: | 5,347,209 |
| Posted today: | 2 |