Bug#994839: ch-upgrading.en.html#sufficient-space: a suggestion.

[Brian Potkin]

Package: release-notes
Severity: normal
Tags: patch



At

https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#sufficient-space

steps 1, 2 and 3 for using a temporary /var/cache/apt/archives work
fine for me. At step 4 I do 'mount' and get

/dev/sdc1 on /media/usbkeys type ext4 (rw,relatime)
/dev/sdc1 on /var/cache/apt/archives type ext4 (rw,relatime)

It would seem to me that step 4 should be advising

umount /var/cache/apt/archives

Cheers,

Brian.

[Andrei POPESCU]

Post by Brian Potkin
At
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#sufficient-space
steps 1, 2 and 3 for using a temporary /var/cache/apt/archives work
fine for me. At step 4 I do 'mount' and get
/dev/sdc1 on /media/usbkeys type ext4 (rw,relatime)
/dev/sdc1 on /var/cache/apt/archives type ext4 (rw,relatime)
It would seem to me that step 4 should be advising
umount /var/cache/apt/archives

Yes, this would be the correct command.

Kind regards,
Andrei

[Debian Bug Tracking System]

Your message dated Thu, 23 Sep 2021 15:49:19 +0200
with message-id <aaf1edf8-1cc0-14f8-6d64-***@debian.org>
and subject line Re: Bug#994839: ch-upgrading.en.html#sufficient-space: a suggestion.
has caused the Debian Bug report #994839,
regarding ch-upgrading.en.html#sufficient-space: a suggestion.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)

[Andrei POPESCU]

Date: Thu, 23 Sep 2021 15:49:19 +0200
From: Paul Gevers

Post by Andrei POPESCU

Post by Brian Potkin
It would seem to me that step 4 should be advising
umount /var/cache/apt/archives

Yes, this would be the correct command.

Ack. Committed locally and about to push.

Hi Paul,

Would you mind if I commit such trivial-but-obvious fixes directly?

Is there something else to consider (besides fixing existing
translations)?

Kind regards,
Andrei

[Paul Gevers]

Hi Andrei,

Post by Andrei POPESCU
Would you mind if I commit such trivial-but-obvious fixes directly?

If you're really sure, yes, go ahead. Making sure somebody from the
release team (me) is aware would be *really* appreciated.

Post by Andrei POPESCU
Is there something else to consider (besides fixing existing
translations)?

Around the release (i.e. half a year before and until we branched off) I
try to be nice to translators and leave mistakes in the original in to
avoid creating too much fuzzy translations, unless I can fix the
original in the translations too (like I did this time).

Paul

[Andrei POPESCU]

Post by Paul Gevers
Hi Andrei,

Post by Andrei POPESCU
Would you mind if I commit such trivial-but-obvious fixes directly?

If you're really sure, yes, go ahead. Making sure somebody from the
release team (me) is aware would be *really* appreciated.

Should that (B)Cc: -release or do you prefer direct message instead?

Post by Paul Gevers

Post by Andrei POPESCU
Is there something else to consider (besides fixing existing
translations)?

Around the release (i.e. half a year before and until we branched off) I
try to be nice to translators and leave mistakes in the original in to
avoid creating too much fuzzy translations, unless I can fix the
original in the translations too (like I did this time).

As a (too busy for this release) translator myself, this is very much
appreciated.

Kind regards,
Andrei

[Paul Gevers]

Hi

Post by Andrei POPESCU

Post by Paul Gevers
If you're really sure, yes, go ahead. Making sure somebody from the
release team (me) is aware would be *really* appreciated.

Should that (B)Cc: -release or do you prefer direct message instead?

I think the best thing is to make sure that debian-doc is CC'd. Somebody
(currently me) from the release team should really be watching that list.

Paul

[Andrei POPESCU]

Post by Paul Gevers
Hi

Post by Andrei POPESCU

Post by Paul Gevers
If you're really sure, yes, go ahead. Making sure somebody from the
release team (me) is aware would be *really* appreciated.

Should that (B)Cc: -release or do you prefer direct message instead?

I think the best thing is to make sure that debian-doc is CC'd. Somebody
(currently me) from the release team should really be watching that list.

Ok, Cc: -doc or the bug where applicable (and with the same end effect)
was implied ;)

Kind regards,
Andrei