Am 22. Juni 2025 11:34:09 MESZ schrieb Holger Wansing :
>Hi,
>
>Holger Wansing wrote (Fri, 20 Jun 2025 16:29:28 +0200):
>
>As you may have noticed, the release-notes don't get updated on the website
>currently.
>The version at the website is stuck at the state from 2025-06-19.
>Since it's not c
Hi,
Holger Wansing wrote (Fri, 20 Jun 2025 16:29:28 +0200):
> Paul Gevers wrote (Mon, 16 Jun 2025 21:04:35 +0200):
> >
> > On 15-06-2025 23:41, Holger Wansing wrote:
> > > Would it be ok, to drop the build for at least the very outdated
> > > languages?
> > > Most content will be in English an
Hi,
Paul Gevers wrote (Mon, 16 Jun 2025 21:04:35 +0200):
> Hi,
>
> On 15-06-2025 23:41, Holger Wansing wrote:
> > Would it be ok, to drop the build for at least the very outdated languages?
> > Most content will be in English anyway now...
>
>
> I think that's a reasonable thing to do.
Done.
Hi,
On 15-06-2025 23:41, Holger Wansing wrote:
Would it be ok, to drop the build for at least the very outdated languages?
Most content will be in English anyway now...
I think that's a reasonable thing to do.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
Processing control commands:
> forwarded -1
> https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/215
Bug #1094000 [release-notes] release-notes: fails to build on trixie (sphinx >=
6.0) due to 'extlinks' config
Set Bug forwarded-to-address to
'https://salsa.debian.org/ddp-team/rel
On Mon, 23 Dec 2024 at 16:18, Holger Wansing wrote:
> Am 23. Dezember 2024 15:40:59 MEZ schrieb Richard Lewis:
> >Unfortunately https://www.debian.org/releases/trixie/amd64/release-notes/ is
> >a 404, i wonder if
> >someone could make those pages redirect to the correct trixie pages?
>
> See abo
Hi,
Am 23. Dezember 2024 15:40:59 MEZ schrieb Richard Lewis:
>I worked it out:
>
>bookworm (docbook) is
>https://www.debian.org/releases/bookworm/amd64/release-notes/
>trixie (rst) is
>https://www.debian.org/releases/trixie/release-notes/index.en.html
This link is correct for trixie.
>
Richard Lewis writes:
> Paul Gevers writes:
>
>> Hi,
>>
>> On 22-12-2024 19:08, Richard Lewis wrote:
>>> Currently the page has several that relate to bookworm (and some
>>> before): should anything relating to bookworm or earlier be closed? is
>>> it still desirable/possible to amend the bookwo
Paul Gevers writes:
> Hi,
>
> On 22-12-2024 19:08, Richard Lewis wrote:
>> Currently the page has several that relate to bookworm (and some
>> before): should anything relating to bookworm or earlier be closed? is
>> it still desirable/possible to amend the bookworm release-notes?
>
> bookworm re
Hi,
Am 22. Dezember 2024 21:20:56 MEZ schrieb Paul Gevers :
>On 22-12-2024 19:08, Richard Lewis wrote:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927679
>> - is about docbook syntax. release-notes now use markdown. close?
>
>Absolutely. Except if the markdown setup also has something lik
Hi,
On 22-12-2024 19:08, Richard Lewis wrote:
Currently the page has several that relate to bookworm (and some
before): should anything relating to bookworm or earlier be closed? is
it still desirable/possible to amend the bookworm release-notes?
bookworm release-notes can be updated until boo
Hi,
On 07-06-2023 13:40, Martin Bagge / brother wrote:
Noticed that &newreleasename; was added in the upgrading section of the
release notes (looks to be introduced via #1035089) and I can parse that
(or can I?) but make validate does not pass clean with it.
Thanks, I thought I fixed that...
Hi Kernel team,
Last release I sent out the message below and in the end we included
something [1] in the Release Notes mentioning dropped support. Is there
something like that worth mentioning this time around?
Paul
[1]
https://www.debian.org/releases/bullseye/armel/release-notes/ch-inform
Processing commands for cont...@bugs.debian.org:
> unarchive 977358
Bug #977358 {Done: Paul Gevers } [release-notes]
release-notes: document how to make the rescue mode usable if no root password
is set (buster)
Unarchived Bug 977358
> reopen 977358
Bug #977358 {Done: Paul Gevers } [release-note
Processing control commands:
> tags -1 + patch
Bug #1034412 [release-notes] release-notes: Information about manpages-l10n for
bookworm release notes
Added tag(s) patch.
--
1034412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034412
Debian Bug Tracking System
Contact ow...@bugs.debian.or
Processing control commands:
> tags -1 + patch
Bug #1034248 [release-notes] release-notes: Document that GTK4 apps are not
accessible with screen reader
Added tag(s) patch.
--
1034248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034248
Debian Bug Tracking System
Contact ow...@bugs.debian
Processing commands for cont...@bugs.debian.org:
> severity 1033065 normal
Bug #1033065 [release-notes] release-notes: i386 notes should specify minimum
CPU requirements
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
10330
Processing control commands:
> severity -1 serious
Bug #1033065 [release-notes] release-notes: i386 notes should specify minimum
CPU requirements
Severity set to 'serious' from 'important'
--
1033065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033065
Debian Bug Tracking System
Contact o
Processing control commands:
> affects 1005863 net-tools
Bug #1005863 [gcc-11] gcc-11: invalid opcode for Geode LX on i386
Added indication that 1005863 affects net-tools
> tags -1 moreinfo
Bug #1033065 [release-notes] release-notes: i386 notes should specify minimum
CPU requirements
Added tag(s)
Hallo Andy,
On Thu, Dec 30, 2021 at 12:42:21AM +0100, andy wrote to
debian-doc@lists.debian.org:
>
> Systemctl suspend funktioniert nicht richtig, wenn ich
>
> systemctl suspend
>
> im Terminal eingebe fährt der Rechner herunter aber beim Neustart bleibt
> der Bildschirm schwarz was kann ich ma
Hi,
andy wrote (Thu, 30 Dec 2021 00:42:21 +0100):
>
> Systemctl suspend funktioniert nicht richtig, wenn ich
>
> systemctl suspend
>
> im Terminal eingebe fährt der Rechner herunter aber beim Neustart bleibt
> der Bildschirm schwarz was kann ich machen um den Fehler zu entfernen?
Solche sollt
Hi Martin,
On 13-08-2021 23:53, Martin Bagge / brother wrote:
> While translating the issues file I noticed that three occurences of
> fail2ban uses as tag instead of the more common role="package">. Looks like only these three lines in the entire repo
> does it like this. Might be an oversight.
Hi Justin, all,
On 06-08-2021 19:23, Justin B Rye wrote:
> Thinking about the overall structure, it might work better to move the
> "good news" part to the start...
>
>
>No new SSH connections possible during upgrade
>
> Although existing Secure Shell (SSH) connecti
Paul Gevers wrote:
> Please find attached my proposal for the release notes to cover bug #990069.
>
> Disclaimer: I (or somebody else) still have (has) to verify that the
> procedure works as intended. One can clearly start a very limited
> upgrade with only openssh-server, but what needs checking
Processing commands for cont...@bugs.debian.org:
> # grr
> reassign 988963 release-notes
Bug #988963 [libgc1c2] libgc1c2: please drop obsolete Conflicts on libgc1
Bug #988003 [libgc1c2] libgc1c2: please drop obsolete Conflicts on libgc1
Bug reassigned from package 'libgc1c2' to 'release-notes'.
Bu
Hi,
On 16-06-2021 02:31, Ben Hutchings wrote:
>>> +
>>> +Package: linux-image-marvell
>>> +Pin: release a=buster
>>> +Pin-Priority: 900
>>> +
My system is upgrading as I write this, at least one bug found. The pin
line should read:
Pin: release n=buster
Paul
OpenPGP_signature
Descriptio
wOn Mon, 2021-06-14 at 06:25 +0100, Justin B Rye wrote:
> Paul Gevers wrote:
> > +
> > + Hardware that's no longer supported
>
> The contraction "that's" seems out of place in a title - probably we
> should just use:
>
> No longer supported hardware
>
That would correctly be s
Paul Gevers wrote:
> +
> + Hardware that's no longer supported
The contraction "that's" seems out of place in a title - probably we
should just use:
No longer supported hardware
> +
> + Due to hardware limitations, it's no longer viable for Debian
> + to build the
Hi all,
Proposed text for the release notes attached.
On 11-06-2021 21:47, Ben Hutchings wrote:
> On Sat, 2021-06-12 at 03:01 +0900, Roger Shimizu wrote:
>> On Fri, Jun 11, 2021 at 1:22 PM Salvatore Bonaccorso
>> wrote:
>>> On Thu, Jun 10, 2021 at 11:32:23AM +0200, Paul Gevers wrote:
On 24
On Sat, 2021-06-12 at 03:01 +0900, Roger Shimizu wrote:
> On Fri, Jun 11, 2021 at 1:22 PM Salvatore Bonaccorso
> wrote:
> >
> > Hi,
> >
> > On Thu, Jun 10, 2021 at 11:32:23AM +0200, Paul Gevers wrote:
> > > Hi Kernel team,
> > >
> > > I know everybody is busy, but friendly ping.
> > >
> > > O
Hi Roger,
Thanks for the reply,
On 11-06-2021 20:01, Roger Shimizu wrote:
> On Fri, Jun 11, 2021 at 1:22 PM Salvatore Bonaccorso
> wrote:
>>> On 24-05-2021 06:55, Paul Gevers wrote:
I happen to own a QNAP (armel) and I spotted in the changelog that it's
not going to be supported in bu
On Fri, Jun 11, 2021 at 1:22 PM Salvatore Bonaccorso wrote:
>
> Hi,
>
> On Thu, Jun 10, 2021 at 11:32:23AM +0200, Paul Gevers wrote:
> > Hi Kernel team,
> >
> > I know everybody is busy, but friendly ping.
> >
> > On 24-05-2021 06:55, Paul Gevers wrote:
> > > I happen to own a QNAP (armel) and I s
Hi,
On Thu, Jun 10, 2021 at 11:32:23AM +0200, Paul Gevers wrote:
> Hi Kernel team,
>
> I know everybody is busy, but friendly ping.
>
> On 24-05-2021 06:55, Paul Gevers wrote:
> > I happen to own a QNAP (armel) and I spotted in the changelog that it's
> > not going to be supported in bullseye. I
Hi Kernel team,
I know everybody is busy, but friendly ping.
On 24-05-2021 06:55, Paul Gevers wrote:
> I happen to own a QNAP (armel) and I spotted in the changelog that it's
> not going to be supported in bullseye. I was wondering, is that
> something that should be mentioned in the release note
Processing control commands:
> tags -1 moreinfo
Bug #977358 [release-notes] release-notes: document how to make the rescue mode
usable if no root password is set (buster)
Added tag(s) moreinfo.
--
977358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977358
Debian Bug Tracking System
Contac
Processing control commands:
> tags -1 pending patch
Bug #976238 [release-notes] release-notes: Please mention that NSS NIS/NIS+
support has been moved to separate packages
Added tag(s) pending and patch.
--
976238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976238
Debian Bug Tracking Sy
Processing control commands:
> tags -1 patch pending
Bug #947860 [release-notes] release-notes: Sec 4.3 preparing sources.list omits
explicit statement of key change
Added tag(s) pending and patch.
--
947860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947860
Debian Bug Tracking System
Co
Processing control commands:
> tags -1 patch
Bug #945568 [release-notes] release-notes: Mention isdn4linux removal
Added tag(s) patch.
--
945568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 patch
Bug #931785 [release-notes] release-notes: bullseye: security suite renamed to
bullseye-security (from buster/updates)
Added tag(s) patch.
--
931785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931785
Debian Bug Tracking System
Contact ow...@bu
Processing control commands:
> tags -1 moreinfo
Bug #977477 [release-notes] release-notes: Update apt upgrade guidance
Added tag(s) moreinfo.
--
977477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi,
It was just a stupid mistake during update, I've fixed and pushed it.
Thanks!
--
Hideki Yamane / Debian Developer
2019年7月22日(月) 4:12 Javier Fernandez-Sanguino :
>
> Dear Hideki Yamane,
>
> Based on the build logs below it looks like the Japanese translation of the
> release notes does no
Paul Gevers wrote:
> On 11-07-2019 16:01, Justin B Rye wrote:
>> [...] But that's getting too contorted. Maybe it would be better
>> to simplify down to this:
>>
>> On systems with simple network hardware (e.g. only an
>> eth0
>> and no eth1) the net.ifnames=0
>> kernel
>> commandl
Hi,
On 11-07-2019 16:01, Justin B Rye wrote:
> Another way of phrasing it would be to say something like "only one
> network interface recognised as belonging to a given type (e.g.
> ethX)". But that's getting too contorted. Maybe it would be better
> to simplify down to this:
>
> On system
Andrei POPESCU wrote:
>> Would it help if instead of saying "only one network interface (of a
>> given type)" it said something like "only one network interface in a
>> given type namespace (e.g. ethX)"?
>
> From my translator's point of view, please avoid the jargon
> ("namespace"), though I can
On Mi, 10 iul 19, 22:21:59, Justin B Rye wrote:
> Andrei POPESCU wrote:
>
> > To be on the safe side the entry could be adjusted as per this patch
> > (also attached for convenience):
>
> I'm not sure what you're trying to achieve with this change, since all
> it seems to do is assert more spec
Andrei POPESCU wrote:
> On Mi, 03 iul 19, 18:22:30, Michael Biebl wrote:
>> Usually ethernet interfaces are name eth* and wifi interfaces are named
>> wlan*, so yeah, if you have a single ethernet interface which is named
>> eth0 and a single wifi interface that is named wlan0, then you are safe
>>
On Mi, 03 iul 19, 18:22:30, Michael Biebl wrote:
>
> Usually ethernet interfaces are name eth* and wifi interfaces are named
> wlan*, so yeah, if you have a single ethernet interface which is named
> eth0 and a single wifi interface that is named wlan0, then you are safe
> as well. I do vaguely re
Hi,
On 03-07-2019 18:52, andreimpope...@gmail.com wrote:
> My new patch tries to address this.
Pushed this version already.
Paul
signature.asc
Description: OpenPGP digital signature
On Mi, 03 iul 19, 19:07:40, Michael Biebl wrote:
> >
> > As per the e-mail thread that started this, users will find out it does
> > work. If the Release Notes entry contradicts their experience they will
> > dismiss the advice as outdated/incorrect/etc.
>
> Being a supported configuration and
Am 03.07.19 um 18:48 schrieb Justin B Rye:
>> As said, net.ifnames=0 does not enforce the old naming scheme, it means
>> use the kernel provided names.
> I don't follow. Surely the old naming scheme *is* to use the
> kernel-provided names? Where did names like "eth0" come from if not
> the kernel
Am 03.07.19 um 18:52 schrieb andreimpope...@gmail.com:
> On Mi, 03 iul 19, 18:22:30, Michael Biebl wrote:
>> Am 03.07.19 um 17:53 schrieb andreimpope...@gmail.com:
>>>
>>> diff --git a/en/issues.dbk b/en/issues.dbk
>>> index 4769f9d6..c7634151 100644
>>> --- a/en/issues.dbk
>>> +++ b/en/issues.dbk
On Mi, 03 iul 19, 18:22:30, Michael Biebl wrote:
> Am 03.07.19 um 17:53 schrieb andreimpope...@gmail.com:
> >
> > diff --git a/en/issues.dbk b/en/issues.dbk
> > index 4769f9d6..c7634151 100644
> > --- a/en/issues.dbk
> > +++ b/en/issues.dbk
> > @@ -136,7 +136,7 @@ information mentioned in .
> >
(Thanks to Andrei for coming up with a better revision than the draft
I was too slow with!)
Michael Biebl wrote:
> Am 03.07.19 um 17:53 schrieb andreimpope...@gmail.com:
>> Based on your comments I prepared the patch below (also attached for
>> convenience), that I could push anytime.
>>
>> diff
Am 03.07.19 um 17:53 schrieb andreimpope...@gmail.com:
> On Mi, 03 iul 19, 16:47:36, Michael Biebl wrote:
>> Am 03.07.19 um 16:12 schrieb Michael Biebl:
>>> Am 03.07.19 um 15:50 schrieb andreimpope...@gmail.com:
Please kindly confirm this Release Notes entry is needed/correct/etc.
https:/
On Mi, 03 iul 19, 16:47:36, Michael Biebl wrote:
> Am 03.07.19 um 16:12 schrieb Michael Biebl:
> > Am 03.07.19 um 15:50 schrieb andreimpope...@gmail.com:
> >> Please kindly confirm this Release Notes entry is needed/correct/etc.
> >> https://www.debian.org/releases/buster/amd64/release-notes/ch-inf
Am 03.07.19 um 16:12 schrieb Michael Biebl:
> Am 03.07.19 um 15:50 schrieb andreimpope...@gmail.com:
>> Please kindly confirm this Release Notes entry is needed/correct/etc.
>> https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#migrate-interface-names
>>
>> #919390 ap
Am 03.07.19 um 16:12 schrieb Michael Biebl:
> Am 03.07.19 um 15:50 schrieb andreimpope...@gmail.com:
>> Please kindly confirm this Release Notes entry is needed/correct/etc.
>> https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#migrate-interface-names
>>
>> #919390 ap
Am 03.07.19 um 15:50 schrieb andreimpope...@gmail.com:
> Please kindly confirm this Release Notes entry is needed/correct/etc.
> https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#migrate-interface-names
>
> #919390 appears to contradict /usr/share/doc/udev/README.De
Processing control commands:
> tags -1 patch
Bug #928026 [release-notes] release-notes: document the state of security
support for golang packages in Buster
Added tag(s) patch.
--
928026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928026
Debian Bug Tracking System
Contact ow...@bugs.debi
Dear kernel team,
I hope I didn't miss your response, but AFAICT the request below is
still open. A reply like "no, there is no need for any specifics" is
also very welcome.
On 06-04-2019 21:50, Paul Gevers wrote:
> Dear kernel team,
>
> I am reaching out to you as I help to coordinate this rele
On Du, 14 apr 19, 21:03:59, Justin B Rye wrote:
> Andrei POPESCU wrote:
> > Of course it helps if I actually attache the patch :)
>
> They look good to me, but I also see one other change to add:
>
> > @@ -390,7 +390,7 @@ code.
> > &debian; &releasename; has AppArmor enabled per
> > def
Andrei POPESCU wrote:
> Of course it helps if I actually attache the patch :)
They look good to me, but I also see one other change to add:
> @@ -390,7 +390,7 @@ code.
> &debian; &releasename; has AppArmor enabled per
> default. AppArmor is a mandatory access control
> framework th
Hi Andrei,
On 14-04-2019 20:55, Andrei POPESCU wrote:
> While reviewing the Romanian translation I found some typos in the
> English version. There is also one small rewording included so CCing
> -l10n-english.
>
> Please find attached a patch generated with 'git diff >'.
You seem to have forg
On Du, 14 apr 19, 21:55:48, Andrei POPESCU wrote:
> Hello,
>
> While reviewing the Romanian translation I found some typos in the
> English version. There is also one small rewording included so CCing
> -l10n-english.
>
> Please find attached a patch generated with 'git diff >'.
Of course it h
Processing control commands:
> tags -1 moreinfo
Bug #880638 [release-notes] release-notes: Document apt sandbox support [buster]
Added tag(s) moreinfo.
--
880638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 patch
Bug #864017 [release-notes] release-notes: Assumes /etc/apt/sources.list is
used (and not /etc/apt/sources.list.d/*.list or deb822) [general]
Added tag(s) patch.
--
864017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864017
Debian Bug Tracking
Processing control commands:
> tags -1 moreinfo
Bug #881771 [release-notes] release-notes: No mention of "predictable network
interface names" in Debian 10
Added tag(s) moreinfo.
--
881771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881771
Debian Bug Tracking System
Contact ow...@bugs.de
Processing control commands:
> tags -1 moreinfo
Bug #883715 [release-notes] release-notes: please document unattended-upgrades
Added tag(s) moreinfo.
--
883715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 patch moreinfo
Bug #865215 [release-notes] release-notes: Perform upgrades with apt(8) instead
of apt-get(8)
Added tag(s) patch and moreinfo.
--
865215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865215
Debian Bug Tracking System
Contact ow...@bugs.
On 2019-03-04 13:51, Debian Bug Tracking System wrote:
> Hi Aurelien,
>
> On Sun, 18 Feb 2018 21:52:07 +0100 Aurelien Jarno
> wrote:> The s390x baseline ISA has been raised to z196 in buster [1]. This
> > should be mentioned in the release notes.
> >
> > I'll try to work on a patch in the next d
Baptiste Jammet:
> Hi,
> Le 05/06/2017 09:23, Niels Thykier a écrit :
>
>> Probably done:
>> ==
>> * chapter 3 (?)
> See #864231
>
>> * chapter 4
> See #864227
>
Thanks, I have merged them now. Apologies for the delay.
With this, I have closed the release-notes for content upda
Hi,
Le 05/06/2017 09:23, Niels Thykier a écrit :
Probably done:
==
* chapter 3 (?)
See #864231
* chapter 4
See #864227
Let me know if you disagree with any of these.
English review done:
[...]
Timeline:
=
[...]
Thank you for handling this
Dear Niels,
El 5 jun. 2017 9:23 a. m., "Niels Thykier" escribió:
I admit it is not a lot of time to finish. But it should get us a lot
of the way while hopefully leaving enough time for everyone to do their
part.
Thank you for providing a plan for both proofreading, reviews and
translations
Hi,
Niels Thykier wrote:
> Holger Wansing:
> > Hi,
> >
> > In chapter about ftp services, there is a link to the announcement
> > on the debian-announce mailinglist.
> > Maybe we could use the link to the news on debian.org
> > https://www.debian.org/News/2017/20170425
> > instead, to benefit f
Holger Wansing:
> Hi,
>
> In chapter about ftp services, there is a link to the announcement
> on the debian-announce mailinglist.
> Maybe we could use the link to the news on debian.org
> https://www.debian.org/News/2017/20170425
> instead, to benefit from existing translations?
>
>
>
> Holge
Processing control commands:
> tags -1 moreinfo
Bug #805493 [release-notes] release-notes: Document how to migrate SELinux
policies from the old store to the new one
Added tag(s) moreinfo.
--
805493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805493
Debian Bug Tracking System
Contact ow..
Processing control commands:
> tags -1 moreinfo
Bug #850442 [release-notes] release-notes: Section about new remote desktop
software in Debian
Added tag(s) moreinfo.
--
850442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> retitle -1 release-notes: recommend installing usrmerge on upgrade to buster
Bug #841666 [release-notes] release-notes: recommend installing usrmerge on
upgrade to stretch
Changed Bug title to 'release-notes: recommend installing usrmerge on upgrade
to buster' from
Processing control commands:
> tag 789604 patch
Bug #789604 [release-notes] release-notes: 'halt' behaviour changed without
notice
Added tag(s) patch.
--
789604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
T
Processing control commands:
> tags -1 pending
Bug #712737 [release-notes] release-notes: Ambiguity in section 4.6 regarding
whether installer installs kernel-metapackage
Added tag(s) pending.
--
712737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712737
Debian Bug Tracking System
Contact
On 2015-02-04 20:45, Martin Zobel-Helas wrote:
> Can we change that rebuild to once or twice a week, please? Changes to
> the release-notes are not that often.
Just curious: Is the rebuild done, when there are no changes?
--
To UNSUBSCRIBE, email to debian-doc-requ...@lists.debian.org
with a su
Processing control commands:
> tags -1 pending
Bug #760897 [release-notes] release-notes: systemd switch: customised init
scripts
Added tag(s) pending.
--
760897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
Processing control commands:
> tags -1 moreinfo unreproduciable
Unknown tag/s: unreproduciable.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid
help security upstream pending sarge sarge-ignore experimental d-i confirmed
ipv6 lfs fixed-in-experimental fixed-upstream
Processing control commands:
> tags -1 moreinfo
Bug #712804 [release-notes] release-notes: Chapter 4.5.1 Change "Configure=0"
to Configure=1"
Added tag(s) moreinfo.
--
712804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with p
Processing control commands:
> tags -1 pending
Bug #533267 [release-notes] release-notes: Purging uninstalled packages
Bug #611317 [release-notes] release-notes: suggest running "apt-get clean" just
before dist-upgrade
Bug #617981 [release-notes] release-notes: Leftover configured packages take u
Processing control commands:
> tags -1 patch
Bug #533267 [release-notes] release-notes: Purging uninstalled packages
Bug #611317 [release-notes] release-notes: suggest running "apt-get clean" just
before dist-upgrade
Bug #617981 [release-notes] release-notes: Leftover configured packages take up
On Mon, Apr 29, 2013 at 23:54:32 +0200, Martin Bagge / brother wrote:
> in whats-new.po I saw that LXDE is noted as having a version number
> (0.5.0). This seems odd when LXDE is made out of individual
> components with different version numbers. I should know this as I
> am the upstream release m
On Mon, Apr 29, 2013 at 23:54:32 +0200, Martin Bagge / brother wrote:
> in whats-new.po I saw that LXDE is noted as having a version number
> (0.5.0). This seems odd when LXDE is made out of individual
> components with different version numbers. I should know this as I
> am the upstream release m
On Vi, 12 apr 13, 08:39:03, Justin B Rye wrote:
> >
> > This distinction has nothing to do with visual mode of aptitude, the
> > command line interface provides similar levels of interaction.
>
> You really think so? I'm surprised, because my experience is entirely
> different: I find using apti
TL;DR: revised patch removes this paragraph.
Daniel Hartwig wrote:
Justin B Rye wrote:
>>> The preferred program for interactive package management from a
>>> terminal is _aptitude_. For a non-interactive command line interface
>>> for package management, it is recommended to use _apt-get_.
Daniel Hartwig wrote:
> Neither is this something new, so why not
> just remove this old notice?
I recommended that in http://bugs.debian.org/704286 and have been
waiting for the suggestion to be reviewed and committed.
Thanks,
Jonathan
--
To UNSUBSCRIBE, email to de
On 9 April 2013 17:11, Justin B Rye wrote:
> Justin B Rye wrote:
>> This patch also tweaks section 2.1.3:
>>
>> The preferred program for interactive package management from a
>> terminal is _aptitude_. For a non-interactive command line interface
>> for package management, it is recommended
Justin B Rye wrote:
> This patch also tweaks section 2.1.3:
>
> The preferred program for interactive package management from a
> terminal is _aptitude_. For a non-interactive command line interface
> for package management, it is recommended to use _apt-get_. [...]
>
> Obviously, if I say
Daniel Hartwig wrote:
Justin B Rye wrote:
>> Daniel Hartwig wrote:
>>>
>>> Right, and I do not see how ‘visual mode’ is misleading?
>>
>> I've explained it already, but the reason it's not obvious to you is
>> that you're not some
>>
>> slow-witted, ignorant newbie,
>>
>> and therefore don't have
On 30 March 2013 17:10, Justin B Rye wrote:
> Daniel Hartwig wrote:
>>
>> Right, and I do not see how ‘visual mode’ is misleading?
>
> I've explained it already, but the reason it's not obvious to you is
> that you're not some
> slow-witted, ignorant newbie,
> and therefore don't
> have much pra
Daniel Hartwig wrote:
>>> I'm standardising on "full-console mode", given that nobody has
>>> suggested anything better.
>>
>> The reason no one has suggested anything better is that 'visual mode' is the
>> *canonical name* for running aptitude in this mode. Please don't have a
>> proxy battle wit
Steve Langasek wrote:
>> Going back to the aptitude non-olfactory mode nonsense, here's a patch
>> for that.
>
>> I'm standardising on "full-console mode", given that nobody has
>> suggested anything better.
>
> The reason no one has suggested anything better is that 'visual mode' is the
> *canon
On 30 March 2013 07:35, Steve Langasek wrote:
> On Fri, Mar 29, 2013 at 09:37:12PM +, Justin B Rye wrote:
>> Justin B Rye wrote:
>> > Still it seems nobody's interested. Would it help if I was more
>> > specific? The chapter on upgrading has:
>> [...]
>> > Patch attached.
>
>> Going back to
On 30 March 2013 05:37, Justin B Rye wrote:
> (I am of course taking it for granted we still trust apt-get more than
> aptitude for dist-upgrades.)
Yes.
--
To UNSUBSCRIBE, email to debian-doc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Fri, Mar 29, 2013 at 09:37:12PM +, Justin B Rye wrote:
> Justin B Rye wrote:
> > Still it seems nobody's interested. Would it help if I was more
> > specific? The chapter on upgrading has:
> [...]
> > Patch attached.
> Going back to the aptitude non-olfactory mode nonsense, here's a patch
1 - 100 of 417 matches
Mail list logo
