Bug#1070258: release-notes: Approach to managing other package managers when upgrading needs documentation

Manny wrote: > One of the ways I got burnt in the Bullseye → Bookworm full-upgrade is > documented here: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070203 > > There was no signal given before, during, or after the upgrade warning > that the non-debian python app “argostranslate”

Bug#1070314: cryptsetup: backward incompatible change for plain mode when relying on defaults

RL wrote (https://lists.debian.org/debian-doc/2024/05/msg3.html): > Guilhem Moulin writes: >> cryptsetup 2:2.7.0~rc0-1 has a backward incompatible change for plain >> mode when relying on defaults cipher and password hashing algorithm. >> >> The change affects users upgrading from bookworm to

Bug#1064617: Passwords should not be changed frequently

Philip Hands wrote: > IMO Having the 'password/passphrase' throughout makes it awkward to > read, and actually we've got one place where it still just says > password, and fixing that would make it slightly worse IMO. > > How about dropping the passphrase stuff? > > >

Bug#1064617: Passwords should not be changed frequently

Philip Hands wrote: >> Maybe instead of saying "use the system's initial user account to >> become root" it should say "allow the system's initial user account >> to gain administrative privileges"? I'm not sure. Oh, and we might >> even want to mention the word "superuser", or then again we

Bug#1064617: Passwords should not be changed frequently

Philip Hands wrote: >> https://salsa.debian.org/installer-team/user-setup/-/commit/77c1517fade367bc465da2a5908c5ac47dd8bba7 >> >> Template: passwd/root-password >> Type: password >> # :sl1: >> _Description: Root password/passphrase: >>One needs a password/passphrase that grants >>

Bug#1064617: Passwords should not be changed frequently

Philip Hands wrote: > Justin B Rye writes: >> Philip Hands wrote: >>> Justin B Rye writes:> ... >>> The reason behind that structure was supposed to be that one definitely >>> needs _a_ password, but not necessarily a root password, so the password >>

Bug#1064617: Passwords should not be changed frequently

Philip Hands wrote: > Justin B Rye writes: >> It needs a small amount of rephrasing, but the most important problem >> is that it starts by saying you need to set a password and then goes >> on to suggest that you might not need to set a password. Maybe that >> can be

Bug#1064617: Passwords should not be changed frequently

Holger Wansing wrote: > @d-l10n-english: hey guys, we would like to get a proposal reviewed, > which aims to improve the root/user password screens in the installer. > > Please find the related merge request at > It needs a

Bug#1064394: release-notes: English language output for the commands into script session

Franco Martelli wrote: >> The question is, will users realise that they're putting the files in >> *root's* home directory, and will they even know where that is? > > A minimal assumption of knowledge base of the FHS ¹ and tilde-expansion > should be take by Release Notes writers. I think we

Bug#1064394: release-notes: English language output for the commands into script session

I've just noticed that we're discussing this on debian-doc without always Ccing the bug - see https://lists.debian.org/debian-doc/2024/02/threads.html Franco Martelli wrote: >> immediately preceding line invoking screen with a 2>~/foo redirection* >> won't work on csh (tested with

Bug#1064394: release-notes: English language output for the commands into script session

Franco wrote: > Dear Debian Documentation Project staff, > > I want to suggest to add a sentence like the following to the §4.4.1 > "Recording the session" paragraph. ¹ Below the "script" command: > > --- BEGIN of the statement --- I like this idea; but it might work better if we turn things

Bug#1051314: fonts-recommended: recognise noto-core as alternative to dejavu-core

Package: fonts-recommended Version: 1 Severity: wishlist Tags: patch Various major desktops now default to fonts-noto-core instead of fonts-dejavu-core. During a conversation with a fontconfig-config maintainer on debian-l10n-english about the knock-on effects

Bug#1050833: release-notes: Bookworm renames network interfaces

Rainer Dorsch wrote: >> Are you saying that armhf machines still used one of the old interface >> naming schemes (https://wiki.debian.org/NetworkInterfaceNames) on >> bullseye, and hadn't yet switched over to "predictable" names? > > That is at least what I observed. I don't have insights, why

Bug#1050833: release-notes: Bookworm renames network interfaces

Rainer Dorsch wrote: > I did a test installation with a bullseye installer on a cubox-i > (armhf architecture) and then upgraded to bookworm. After the upgrade > the network was gone. Even booting with the previous kernel > 5.10.0-23-armmp does not bring the network back. > > After some more

Bug#684128: src:debian-installer: allow use of binary units in disk partitioner

Holger Wansing wrote: > Thorsten Glaser : >> Could this information (valid unit sufficēs) be added to the dialogue >> where the size is entered? Screen space should suffice. [...] > CC'ing debian-l10n-english for template review (three identical additions > in two packages). [...] > Hint: "max"

Bug#1041072: trixie: Explicitly flag that /usr-merge changes will break skip-upgrades

Matthew Vernon wrote: > We don't support skip-upgrades, but in practice they can often be made > to work by an experienced administrator. > > For trixie, though, packages are going to be allowed to assume > merged-/usr, and the ongoing work to resolve the outstanding problems > around merged-/usr

Bug#1037203: aide release notes to work around #1037171

Marc Haber wrote: > I am really sorry for this. #1037171 is an embarrassing one, sadly too > late for the release, but I'll try to do a fix via spu. I gather from the version data that when the bug submitter says buster that's a typo for bookworm? > Suggested wording for something along chapter

Bug#1037121: release-notes: Salt has been dropped

Elimar Riesebieter wrote: > Please mention that in Bookworm the salt-stack has been removed. Does this mean we need something in issues.dbk like this? salt stack dropped Due to several release-critical bugs and a short upstream support lifecycle, the salt

Bug#1036907: release-notes: dash in bookworm drops debconf selector for /bin/sh

Andrej Shadura wrote: > I think the release notes should probably mention that dash > 0.5.11+git20210903+057cd650a4ed-4 has dropped all debconf code to allow > using a different shell as /bin/sh. It's not clear from the above (or the changelog) what the change is, exactly. Okay, there's now no

Bug#1036776: release-notes: Release notes paragraph from Debian Med team

Andreas Tille wroteL > Please add the following patch from the Debian Med team to the release notes: Some English-usage suggestions: > > News from Debian Med Blend > > > As in every release new packages in the field of life sciences and > medicine > were added. "Have been"

Bug#1036358: release-notes: Debian 12 expected to be last release w/ installer for i386

Paul Gevers wrote: > On 20-05-2023 16:21, Justin B Rye wrote: > > When do we stop producing official Release Notes? > > You mean when do we stop accepting changes to the Release Notes and stop > building them? Once the release is EOL. However, I don't expect a lot of > p

Bug#995397: Dropped support for 32-bit Xen PV guests should be mentioned in i386 release notes

Richard Lewis wrote: > But the user could be reading the release notes form perspective of > the host, which could be running any arch, so i think safer to include > in every arch's release-notes > > > 32-bit Xen PV guests are not supported > >The Linux kernel (from version 5.9) not

Bug#1036358: release-notes: Debian 12 expected to be last release w/ installer for i386

RL wrote: > Ansgar writes: >> On Fri, 2023-05-19 at 15:03 +0100, Steve McIntyre wrote: >>> My plan is therefore to ship i386 installer images >>> for bookworm as normal (including bookworm point releases going >>> forwards), but to disable those builds for testing/trixie >>> ~immediately after

Bug#1035089: bookworm: gpgv must be installed for successful upgrades

Jonathan Wiltshire wrote: > Attached patch adds a section in the upgrade guide to ensure gpgv is > installed. Most users will have this if they have followed previous > upgrade guidance not to skip releases. However, without it they will not > be able to upgrade at all because the release signing

Bug#1030041: release-notes: offer deb22 format for apt sources

Package: release-notes Severity: minor The familiar "single-line" format for apt sources in .list files is, in theory, gradually being deprecated in favour of the deb822 format in .sources files[1]. We can expect the old format to be supported for a few releases yet - for a start as I understand

Bug#1030040: release-notes: usrmerge and dist-upgrade

Package: release-notes Severity: normal We've already given users notice in previous release-notes that the unmerged format won't be supported on bookworm; now, any users who haven't yet installed usrmerge will get it automatically pulled in during the dist-upgrade. The release-notes ought to

Bug#1023596: bookworm: document changes in default rsyslog configuration

Michael Biebl wrote: > Am 07.11.22 um 23:15 schrieb RL: >> Are both rsyslog and systemd's journal still both the default in bookworm? >> >> I see rsyslog is still priority: important - any plans to reduce that in >> future releases? > > That's actually good point: rsyslog in bookworm has been

Bug#1015892: binutils-common: empty man pages for gprofng and gp-*

Package: binutils-common Version: 2.38.90.20220713-2 Severity: minor I see post-stable versions of binutils include a new set of executables: gprofng, gp-archive, and so on. I can deduce a few things about them from their names, and a good bit more from the output of "gpprofng --help", which

Bug#1014089: run-parts omits some scripts in /etc/cron.daily

Package: debianutils Followup-For: Bug #1014089 I'm not the maintainer, or even a DD, but I happened to notice this bugreport... thanks for being interested in improving Debian, but I don't think it is a bug. > At least in verbose mode run-parts should list all scripts and > explain why some are

Bug#1009253: www.debian.org: remove debian-www list from the footer; direct people to the contact page instead

Paul Wise wrote: > Hi debian-l10n-english folks, > > I'm looking for advice on how to reword the footer on the Debian > website. I want to drop debian-www from the contact information in the > website footer, directing people to the contact page on the website > instead, which should empower them

Bug#992116: release-notes: Add breakage from merged-/usr-via-aliased-dirs

Paul Gevers wrote: > On 23-09-2021 21:25, Paul Gevers wrote: >> "The Debian project is still deciding how to do this and how to migrate >> existing systems as the proper solution isn't known yet." Yes, highly >> frustrating, but it is reality. >> >> For reference: >>

Bug#996472: nspark: Description doesn't say what it does

Simon McVittie wrote: > Package: nspark > Version: 1.7.8B2+git20210317.cb30779-1 > Severity: normal > X-Debbugs-Cc: debian-l10n-engl...@lists.debian.org Well, it reached me, but the BTS etc. don't seem to be sure whether the package exists... # A rewritten version of RISC OS !Spark for UNIX # #

Bug#992034: installation-guide: Include a note on how to change init system during install

Holger Wansing wrote: > Trying to integrate your suggestions, would then have Thanks for making sense of it... > + > + Customization > + > + Using the shell (see ), the installation process > + can be carefully customized, to fit exceptional use cases: > + > + > + Installing an

Bug#992034: installation-guide: Include a note on how to change init system during install

Justin B Rye wrote: > Hmm. That may have been boiled down *too* far, since there's no > hint that it works by going to a shell. So maybe that should have > been in the intro? (Sorry, can't remember the ulink syntax) > > As well as troubleshooting, the [[6.3.9.2|link]] al

Bug#993819: release-notes: Please document the removal of wicd

Hendrik Boom wrote: > Here is the text I have included in the current draft upgrade > instructions for Devuan: > > Warning: `wicd` will no longer be available after the upgrade, so if > you use it to connect to the internet through wifi, you will be cut > off. To prevent this, you should

Bug#992034: installation-guide: Include a note on how to change init system during install

Holger Wansing wrote: >> The more I look at the way the sections are organised the more I think >> that the real problem is that "6.3.9 Troubleshooting" is already a >> misfit. There needs to be some clearer mention in 6.1 of the fact >> that jumping to VT2 lets you issue commands behind d-i's

Bug#992034: installation-guide: Include a note on how to change init system during install

Holger Wansing wrote: >> @Justin? > > Hmm, debian-l10n-english has vanished from the loop somehow. > Therefore, I fear you lost track of this thread in the meantime ... Thanks for spotting that. > Maybe you could try to catch up starting from >

Bug#992185: release-notes: Confusion with "apt full-upgrade" and "apt-get dist-upgrade"

Hideki Yamane wrote: >> >>Dist-upgrade fails with Could not perform immediate >> configuration You're right, this got left behind. Patch attached. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package

Bug#992157: release-notes: warn about SSH at the start of the upgrade paragraph

Paul Gevers wrote: > Minimal system upgrade > + > + > + > +If you upgrade remotely, be aware of linkend="ssh-not-available"/>. > + > + Yes, this looks good. The link text appears as "Section x.y.z, *No new SSH connections possible during upgrade*", right?

Bug#992051: security archive layout change needs more configuration changes

Paul Gevers wrote: > Do you agree with the attached patch? Yes, looks good to me! -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package

Bug#992051: security archive layout change needs more configuration changes

Paul Gevers wrote: > The security line in your APT configuration may look like: > deb https://deb.debian.org/debian-security > bullseye-security main contrib > > + > + If APT is configured using APT pinning or > + APT::Default-Release, "Configured using" is a

Bug#992025: release-notes: Add section on switching init system

Matthew Vernon wrote: >> (We don't seem to be consistent about our em dashes.) > > Sorry, I'm not sure if you're saying you want an em-dash instead of a hyphen > here, or if you don't think it matters? It probably doesn't matter. >>> + identifying the packages to install later easier). Next,

Bug#992025: release-notes: Add section on switching init system

Holger Wansing wrote: >>> + If you encounter any issues specifically associated with using >>> + an alternative init system, there is a Debian init system >>> + diversity list (>> + >>> url="debian-init-divers...@chiark.greenend.org.uk">debian-init-divers...@chiark.greenend.org.uk) >>> +

Bug#992025: release-notes: Add section on switching init system

Matthew Vernon wrote: > + > + > + Switching Init System > + > + > + The default init system in Debian is systemd. In bullseye, a > + number of alternative init systems are supported (such as > + System-V-style init and OpenRC). Generally, to switch between > +

Bug#991969: D-I: news for Bullseye: help with firmware installation

Paul Gevers wrote: > Before pushing, I hope to see comments from Justin. > > Paul > +Help with installation of firmware > + > + More and more, peripheral devices require firmware to be loaded as > + part of the hardware initialization. To help deal with this problem, > + the installer has

Bug#991781: RFR: fail2ban can't send e-mail using mail from bsd-mailx

Paul Gevers wrote: > I have the attached patch ready to push. I'm wondering if we need more > detailed instructions. > > + > +fail2ban can't send e-mail using mail from bsd-mailx > + > + The fail2ban package can > + be configured to send out e-mail notifications. It does that

Bug#991721: release-notes: mention known RC bugs in bullseye

Paul Gevers wrote: > To give translators a chance, I have pushed this without review. The > attached text is what I pushed. Fixes still welcome of course. This and #988963 look okay to me anyway, except perhaps for a few of the bug titles, which are outside my jurisdiction. (I assume translators

Bug#991809: A brief note about NIS installation

Francesco Paolo Lovergine wrote: > Package: release-notes > Severity: normal > > NIS does not more use debconf for its initial installation. While existing > setups should smoothly upgrade to the new multi-package organization, > the recommended configuration way in bullseye is by following the

Bug#991688: mention improved/added man page translations

Joost van Baal-Ilić wrote > The manual pages for several projects such as systemd, util-linux, > OpenSSH, and Mutt in a number of languages, including French, Spanish, > and Macedonian, have been substantially improved. To benefit from > this, please install manpages-xx (where xx is the code

Bug#991688: mention improved/added man page translations

Helge Kreutzmann wrote: > The man pages for nonenglish speaking users have been substantially > improved and extended. Please add a text along the following lines: > Presumably as a subheading under 2.2 "What's new in the distribution?", though I think those items might work better if we moved

Bug#990940: release-notes: wpewebkit to be covered by security support in bullseye

Alberto Garcia wrote: > Debian provides security support for the WebKitGTK browser engine > (source package: webkit2gtk). For bullseye we also want to support > wpewebkit, which is developed by the same team, follows a very similar > release schedule and numbering system, shares most of the code

Bug#990462: Bug#990319: unblock: intel-microcode/3.20210608.2

Paul Gevers wrote: >> We could replace this with "See the instructions in the DSA (also in >> the intel-microcode README.Debian)". Mind you, it would be nice if >> that README started with "TLDR: boot with dis_ucode_ldr"! > > To get this straight, you only propose to replace the piece between >

Bug#990462: Bug#990319: unblock: intel-microcode/3.20210608.2

Sebastian Ramacher wrote: > What about the following text (adapted from the DSA)? > > The intel-firmware package contained in bullseye and released as part of It's "intel-microcode" (eventually: intel-microcode). > DSA-4934-1 is known to contain two significant bugs. For some CoffeeLake

Bug#963964: release-notes: document aufs removal for bullseye

Paul Gevers wrote: > > + > + > + The aufs-dkms > + package is not part of bullseye. Most + role="package">aufs-dkms users should be > + able to switch to kernel supported > + overlayfs to get similar I think at least

Bug#988472: install-mbr doesnt create a partition

Marc Haber wrote: > Package: release-notes > Severity: minor > > Hi, > > Chapter 4.3.3.1 of the release notes suggest using install-mbr /dev/sdX > followed by mkdosfs /dev/sdX1. On a really blank medium, this doesn't > work since install-mbr does NOT create a partition. You mean the

Bug#988078: release-notes: add information regarding exim4 and 'tainted data' issue

Andreas Metzler wrote: > The text has been slightly updated with one oof the latest uploads, it > now reads That's the last sentence changed. We also need a title text; maybe Exim 4.94 (The upstream "brand name" usually seems to be capitalised, whereas the Debian (meta)package name is

Bug#987777: Linux enabled user namespaces by default

Paul Gevers wrote: > Attached commit ready to push. Looks good to me. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package

Bug#987659: release-notes: redmine not available, please wait backports

Paul Gevers wrote: > Attached commit ready to push. This one needs a bit of work: > + > + > + redmine missing in bullseye > + > + redmine is > + unfortunately late migrating over to newer + role="package">rails version despite end of > + upstream support

Bug#987440: release-notes: Mention GnuPG no longer reads ~/.gnupg/options

Paul Gevers wrote: > No change commit ready to push. > > + > + > + gnupg2 options file > + > + Starting with version 2.2.27-1, per-user configuration of the > + GnuPG suite has completely moved to > + ~/.gnupg/gpg.conf, and > + ~/.gnupg/options is no longer

Bug#973987: Please mention fcitx5 is available in bullseye

Justin B Rye wrote: > > New Fcitx 5 Input method ^ Oh, except that should be "Input Method". -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package

Bug#973987: Please mention fcitx5 is available in bullseye

Shengjing Zhu wrote: > === > 2.2.x New Fcitx 5 Input method > > Fcitx 5 is an input method for Chinese, Japanese, Korean and many > other languages. It is the successor of the popular Fcitx 4 in > Buster. The new version supports Wayland and has better addon support. > More information including

Bug#980743: release-notes: bullseye is the final release to ship apt-key

Paul Gevers wrote: > + > + > + bullseye is the final Debian release to ship > + apt-key. Keys should be managed by > + dropping files into trusted.gpg.d instead, in binary format trusted.gpg.d or maybe /etc/apt/trusted.gpg.d? > + as created

Bug#986993: release-notes: Mention OpenJDK 17 status in bullseye

Paul Gevers wrote: > Attached patch ready to push. > + > +OpenJDK 17 > + > + Debian bullseye comes with an early access version of > + OpenJDK 17 (the next expected > + OpenJDK LTS version after OpenJDK > + 11), to avoid the rather tedious bootstrap > + process.

Bug#977358: release-notes: document how to make the rescue mode usable if no root password is set (buster)

Paul Gevers wrote: > How about (dropping the package specific section, and just merge it into > upgrade items): > 5.1. Upgrade specific items for bullseye > 5.2. Items not limited to the upgrade process > * Limitations in security support > * Gnome accessibility issue > *

Bug#987017: recommends 3 different ways to find obsolete packages, pick one

Antoine Beaupré wrote >>> aptitude search '~o' >> >> This is nice and simple, but frankly as an aptitude user I wouldn't >> bother. Instead I'd do what the text just above mentions - launch >> aptitude, notice that there was a category for "Obsolete and Locally >> Created Packages" (which

Bug#987017: recommends 3 different ways to find obsolete packages, pick one

Antoine Beaupre wrote: > The release notes, in sections 4.2.2 and 4.8, actually suggest *three* > *different* ways of finding what are essential orphaned packages: I don't think you mean "orphan" in either of the senses known to "https://wiki.debian.org/Glossary#orphan;. > aptitude search

Bug#987007: release-notes: Release notes for Bullseye by Debian Med team

Andreas Tille wrote: > the Debian Med team proposes the following text for the Bullseye release > notes: > > News from Debian Med Blend > > The Debian Med team was involved into the fight against COVID-19 I'd recommend The Debian Med team has been taking part in the fight against

Bug#986322: Bug#986129: unblock: sendmail/8.15.2-22

Paul Gevers wrote: >> In contrast to normal upgrades of sendmail, during the upgrade of buster >> to bullseye sendmail will be stopped, causing more downtime to the >> service than other sendmail upgrades. Please read [1] for generic advice >> on reducing downtime. >> [1] >>

Bug#977358: release-notes: document how to make the rescue mode usable if no root password is set (buster)

Paul Gevers wrote: > Hi Justin, Andrei, > > Thanks for the proposed text below. I struggle a bit with where to place > it. What do you suggest? It's not really an upgrading issue, is it? Maybe at the end of "issues", next to the similarly chronic issue of GNOME mouseless a11y? That's under

Bug#977358: release-notes: document how to make the rescue mode usable if no root password is set (buster)

Andrei POPESCU wrote: >> (Should there be some hint here at the fact that this has happened >> because we've switched to an implementation of sulogin without the >> slightly dodgy Debian-specific patches?) > > This is explained in the bug report for who cares to investigate, in my > opinion it's

Bug#977358: release-notes: document how to make the rescue mode usable if no root password is set (buster)

Andrei POPESCU wrote: > Ok, here is something, just to get the discussion started: Thanks! My suggestions below still need some work, but I'll call this my first pass: > The `rescue` boot option is unusable without a root password. > > If a password for the `root` account is not set the

Bug#950447: Document that persistent journal is now enabled in systemd

Andrei POPESCU wrote > On Mi, 31 mar 21, 17:33:47, Justin B Rye wrote: >> + >> + Persistent systemd journal >> + >> +Systemd in bullseye activates its persistent journal functionality >> +by default, storing its files in >> +/var/log/journal/

Bug#950447: Document that persistent journal is now enabled in systemd

Paul Gevers wrote: >> On 18-03-2021 11:41, Michael Biebl wrote: >>> Yes, the persistent journal is enabled on upgrades and new installations. >> >> Thanks. >> >>> I'm a bit uncertain, whether I should go into that much detail in the >>> release notes, especially wrt to rsyslog. But on the other

Bug#974728: vim-scripts: Document migration from vim-addon-manager handling to Vim's native "package" functionality

Paul Gevers wrote: > I have prepared the attached change to the release notes, ready to push. Only one niggle: > + The addons for vim > + historically provided by + role="package">vim-scripts are now managed by Vim's > + native package functionality rather than by > +

Bug#931785: release-notes: bullseye: security suite renamed to bullseye-security (from buster/updates)

Justin B Rye wrote: > It looks good, but I'd just made a note to myself that we might also > want to mention this in upgrading.dbk where it discusses editing APT > sources. Hoping to send in some patches tomorrow. Better late than never. -- JBR with qualifications in linguistics, e

Bug#985616: Document change to unbound ".d" config file fragment behavior

Paul Gevers wrote: >> >> Config file fragment handling in unbound >> >> The DNS resolver unbound >> has changed the way it handles configuration file fragments. If >> you are relying on an include: directive to >> merge several fragments into a valid

Bug#985616: Document change to unbound ".d" config file fragment behavior

Andrei POPESCU wrote: > The NEWS file is also available online: > > https://sources.debian.org/src/unbound/1.13.1-1/debian/NEWS/ That's a better idea than the alternative I was considering, which was to point at this bug report. So we could cut it all the way down to something like:

Bug#985616: Document change to unbound ".d" config file fragment behavior

Andrei POPESCU wrote: > On Du, 21 mar 21, 13:01:07, Justin B Rye wrote: >> Robert Edmonds wrote: >>> During the bullseye release cycle the default /etc/unbound/unbound.conf >>> file was changed to use the newly introduced "include-toplevel:" >>>

Bug#985616: Document change to unbound ".d" config file fragment behavior

Robert Edmonds wrote: > During the bullseye release cycle the default /etc/unbound/unbound.conf > file was changed to use the newly introduced "include-toplevel:" > directive rather than the "include:" directive. This should probably be > mentioned in the bullseye release notes because it will

Bug#966701: Driverless printing in buster via ipp-usb

Andrei POPESCU wrote: >>> +Both printing with CUPS and scanning with >>> +SANE are increasingly likely to be possible >>> +without the need for any (often non-free) driver specific > > For me this would sound better: > > ... without the need for any driver (often non-free)

Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier"

Miguel Figueiredo wrote: > Às 21:43 de 13/03/21, Paul Gevers escreveu: > [...] >> + The XFS file system has removed the barrier >> + and nobarrier mount options. > > How about: The mount options were removed from the XFS file system ? Oh, yes, it's true that it was the developers who

Bug#985502: release-notes: suggestions for usrmerge section

Paul Gevers wrote: >> I'd forgotten the *Buster* release notes *do* mention usrmerge: >> >> https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.html#merged-usr >> >> but we've taken that part out now. Could we perhaps recycle the >> phrase "the usrmerge package exists to do

Bug#985502: release-notes: suggestions for usrmerge section

Justin B Rye wrote: > Remember that at present not only do we fail to mention the word > "usrmerge" I'd forgotten the *Buster* release notes *do* mention usrmerge: https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.html#merged-usr but we've taken that part

Bug#985602: Document the new /usr/bin/open command

Charles Plessy wrote: > I would like to document the new `/usr/bin/open` command in the "what's > new" section of the release notes. Here is a description. > > A new `open` commmand is available as a convenience alias to `xdg-open` > (by default) or `run-mailcap`, managed by the

Bug#966701: Driverless printing in buster via ipp-usb

Brian Potkin wrote: [...] >> +Both printing with CUPS and scanning with >> +SANE are increasingly likely to be possible >> +without the need for any (often non-free) backend driver specific > > "backend" has different meaning in CUPS and SANE; I'd omit it. It > is also a possible

Bug#985502: release-notes: suggestions for usrmerge section

Paul Gevers wrote [...] >> Do we have a proposed mechanism for that? Is usrmerge going to be >> made Essential (but a no-op on already-merged systems), or what? > > I'm not aware of the ideas on this front [...] >> summary. Debian bullseye will be the last Debian >>

Bug#985502: release-notes: suggestions for usrmerge section

Paul Gevers wrote: >>> Historically there was a reason to split root level >>> bin, sbin and >>> lib directories into >> >> Nobody ever split /bin etc. "into" /usr; the historical standard was >> to have those directories to split things "out from" the equivalents >> under /usr.

Bug#966701: Driverless printing in buster via ipp-usb

Justin B Rye wrote: > Well, for a start, we don't want to make users read through two > separate competing explanations of what driverless operation is when > they only need to read one. We should try to pull out as much > repeated material as possible from the two sect

Bug#985502: release-notes: suggestions for usrmerge section

Package: release-notes Severity: wishlist Tags: patch Trying to make our coverage in issues.dbk more helpful. > Historically there was a reason to split root level > bin, sbin and > lib directories into Nobody ever split /bin etc. "into" /usr; the historical standard was

Bug#981693: Default Password hash Changes to Yescript for Bullseye

Paul Gevers wrote: > index fbe357b8..f3ff6d48 100644 > --- a/en/issues.dbk > +++ b/en/issues.dbk > @@ -82,6 +82,45 @@ information mentioned in . > > > > + > + > +Password hashing uses yescript by default > + > + The default password hash for local system accounts has

Bug#985438: release-notes: trivial formatting fixes

Package: release-notes Severity: wishlist Tags: patch There are a couple of lines using ASCII quotes when they should be using Docbook s - one in installing.dbk, one in upgrading.dbk. Patch attached. (Salsa's down for maintenance at the moment, so the diffs are slightly faked up. If they don't

Bug#931785: release-notes: bullseye: security suite renamed to bullseye-security (from buster/updates)

Paul Gevers wrote: > On Wed, 10 Jul 2019 13:16:27 +0200 Ansgar Burchardt > wrote: >> For bullseye, the security suite is now named bullseye-security >> instead of buster/updates and users should adapt their sources.list >> accordingly when upgrading. >> >> People should probably use something

Bug#966701: Driverless printing in buster via ipp-usb

Brian Potkin >>> Justin B Rye wrote: >>>> Hang on, is this to go in "What's New"? If so, it's competing with a >>>> version that was added a couple of days ago - >>>> >>>> >>>> https://salsa.debian.org/ddp-team/rele

Bug#966701: Driverless printing in buster via ipp-usb

Brian Potkin wrote: > Justin B Rye wrote: >> Hang on, is this to go in "What's New"? If so, it's competing with a >> version that was added a couple of days ago - >> >> >> https://salsa.debian.org/ddp-team/release-notes/-/commit/30e6ab258f8e98fe43

Bug#966701: Driverless printing in buster via ipp-usb

Hang on, is this to go in "What's New"? If so, it's competing with a version that was added a couple of days ago - https://salsa.debian.org/ddp-team/release-notes/-/commit/30e6ab258f8e98fe43ded83205b68645e74c5cef Have you seen that version? -- JBR with qualifications in linguistics,

Bug#966701: Driverless printing in buster via ipp-usb

Brian Potkin wrote: >> USB connected printers and driverless printing >> -- >> >> The Release Notes for Debian 10 briefly describe the driverless printing >> situation implemented via CUPS and cups-filters. [1] The changes apply to >> modern printers

Bug#971956: release-notes: SANE and driverless scanning

Brian Potkin wrote: > On Sun 14 Mar 2021 at 17:01:14 +0000, Justin B Rye wrote: >>>> Driverless scanning is the ability to scan without using a vendor >>>> backend driver, free or non-free. [...] >> >> It all looks okay. "Vendor backend driver" is

Bug#971956: release-notes: SANE and driverless scanning

Paul Gevers wrote: >> Driverless scanning is the ability to scan without using a vendor >> backend driver, free or non-free. [...] > > You didn't comment on this text, does it mean it passes your judgement? It all looks okay. "Vendor backend driver" is a strange expression, but it seems to be

Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier"

Paul Gevers wrote: > Control: tag -1 patch > > Hi, > > How's this? > > + > +The XFS file system no longer supports barrier/nobarrier > +option > + > + The XFS file system has removed the barrier > + and nobarrier mount options. It is > + recommended to check

Bug#980903: debhelper: doc-base doc-id deduplication does not work as documented with multiple "dh_installdocs -p" calls; causes /usr/share/doc-base/ to be installed multiple times

Axel Beckert wrote: > Justin B Rye wrote: >> Please be aware that this deduplication is currently done in memory >> only, so it requires B to be called no more than >> once during the package build. Calling BI >> in combination with using FIF<.doc

  1   2   3   4   5   6   7   8   9   10   >