Justin B Rye writes:
> sebul wrote:
>> https://www.debian.org/doc/manuals/debian-faq/customizing.en.html#consolefont
>> says /etc/kbd/config file
>> But, I cannot find /etc/kbd/config on my Debian.
>> How can I solve it?
>
> /etc/kbd/config is deprecated in favour of /etc/default/console-setup
>
Joost van Baal-Ilić writes:
>> Source: debian-faq
> But how about the doc-debian package? That one now installs :
>
> /usr/share/doc/debian/bug-log-access.txt
> /usr/share/doc/debian/bug-*.txt.gz
> /usr/share/doc/debian/bug-reporting.txt.gz
> /usr/share/doc/debian/constitution.*txt.gz
> /usr/sha
Daniel Lewart writes:
> Package: release-notes
> Severity: wishlist
>
> Debian Documention Team,
just a user here, but since no-one replied i thought id give my view
> Chapter 4. "Upgrades from Debian 10 (buster)" has commands spread out
> over 20 pages. I think many (most?) admins would enjoy
Some thoughts on clarity - from a user pov, given that people reading
release-notes will not be familiar with details:
Luca Boccassi writes:
> systemd-resolved has been split into a separate package.
> This new systemd-resolved package will not be installed automatically
s/This/The
> on upgrad
Michael Biebl writes:
> The rsyslog configuration changed significantly in bookworm.
Hi, I'd potentially be happy to contribute some text for release-notes
on rsyslog. Some questions based on what i'd want to know as an
interested user:
Are both rsyslog and systemd's journal still both the defa
James Addison writes:
> (someone who knows more may correct me, but I think it would be great to have
> the package available for install using apt in addition to the website)
Interesting idea, but who would use it - won't a release-notes package
always be a whole release out of date?
(and the
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 the release.
>
> I
Hendrik Boom writes:
> On Sat, May 20, 2023 at 01:06:12PM +0100, RL wrote:
>> James Addison writes:
>>
>> > (someone who knows more may correct me, but I think it would be great to
>> > have
>> > the package available for install using apt in additi
Holger Wansing writes:
>> > as far as I know, sphinx/reStructuredText is still lacking some
>> > functionality,
>> > which is heavily used in the release-notes.
>> > That is the use of substitutions within URLs.
>>
>> You could always keep the entities and do a 'sed
>> s/&oldrelease;/bookworm/g
Zebediah Beck writes:
> I'm subscribed to different mailing lists of the community in connection
> with my message here is my proposal or suggestion.
>
> Good day sir/madam
>
> I'm a long time debian user but am a first time user of the mailing list
> and bug report systems, I would like that con
Zebediah Beck writes:
> Wonderful thanks that is well and good with me, please explain why
> libbitcoin was removed from Debian in 2018?
Here's how you can find this:
find the package on https://tracker.debian.org/ (search for libbitcoin)
follow links to https://bugs.debian.org/906801 which say
Franco writes:
> " If you are comfortable with English language it's strongly
> recommended that you run the following command as soon as you start
> the 'script' session:
>
> # LC_ALL=C.UTF-8; LANGUAGE=; export LC_ALL LANGUAGE
>
> This will allow you to get command output messages in English
Bronsen Steele writes:
> I hope you are well. I would like to know if you can please send the
> Debian manifesto.
typing debian manifesto into google suggests the following link:
https://www.debian.org/doc/manuals/project-history/manifesto.en.html
> I would like to read more about the project.
Holger Wansing writes:
>> When following that link, the article says to do an “apt update” then
>> neglects to tell users to perform the upgrade.
>
> Moreover, we have "This should only be necessary in specific situations." in
> this chapter appendix A [1], while we recommend to upgrade to the
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 trixie. Plain mode
> is generally advised against but it still makes sense
15 matches
Mail list logo
