/srv/www.debian.org/release-notes/build.log-xsltproc --nonet --novalid
--xinclude --stringparam draft.mode maybe --stringparam profile.arch
"amd64;not-arm64;not-armel;not-armhf;not-i386;not-mips64el;not-mipsel;not-ppc64el;not-s390x;linux"
\
/srv/www.debian.org/release-notes/build.log-
/srv/www.debian.org/release-notes/build.log-xsltproc --nonet --novalid
--xinclude --stringparam draft.mode maybe --stringparam profile.arch
"amd64;not-arm64;not-armel;not-armhf;not-i386;not-mips64el;not-mipsel;not-ppc64el;not-s390x;linux"
\
/srv/www.debian.org/release-notes/build.log-
Package: release-notes
Severity: important
The release notes has a section about the issues with openstack, but
there are also problems with lxc. I'm not sure what the proper
workaround is, but setting `lxc.mount.auto = cgroup:mixed:force` fixed
it for me.
Mike
Package: release-notes
Severity: normal
Re: 5.1.2 "which takes advantage of the undocumented feature of APT that it
supports regular expressions (inside /)."
Why are we encouraging people to use undocumented features ?
It surely just sets you up for a future fail when people try to use the
Package: release-notes
Severity: normal
The project really needs to make its mind up which way it is going in terms of
managing repo keys.
The bullseye release notes, e.g. 5.3.2. Deprecated components for bullseye make
reference to "Keys should be managed by dropping files into
On Sun 15 Aug 2021 at 20:24:54 +0100, Brian Potkin wrote:
> On Sun 15 Aug 2021 at 20:40:36 +0200, Bruno Zuber wrote:
>
> > It seems to be "http" by default (at least it's ony my newly installed
> > system). I've switched to https and everything still works.
>
> Works for me too. But that
On Sun 15 Aug 2021 at 20:40:36 +0200, Bruno Zuber wrote:
> It seems to be "http" by default (at least it's ony my newly installed
> system). I've switched to https and everything still works.
Works for me too. But that wasn't what I was puzzled about.
> "https" prevents someone from tempering
It seems to be "http" by default (at least it's ony my newly installed
system). I've switched to https and everything still works.
"https" prevents someone from tempering with the users connection (e.g.
man in the middle attack). However as the packages are singed anyway so
https is "just" an
§ 5.1.3 in the Release Notes has
deb https://deb.debian.org/debian-security bullseye-security main contrib
Is the https (rather than http) seen as being better? I've always
used http.
Cheers,
Brian.
Hi,
On 14/08/2021 08:42, Paul Gevers wrote:
On 09-08-2021 22:53, Matthew Vernon wrote:
Not currently (I imagine something like it will end up there
eventually); I think it warrants being in the release notes because it's
quite a significant change from Buster (where non-systemd inits were
On Sb, 14 aug 21, 21:10:44, Paul Gevers wrote:
> Hi,
>
> On 14-08-2021 20:41, Marco Möller wrote:
> > What's about this version:
> >
> >
> > For the Debian release "bullseye", the repository providing security
> > updates is now addressed as bullseye-security
> > The format which was used in
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
Package: release-notes
Severity: minor
X-Debbugs-Cc: henr...@debian.org
Hi,
In en/upgrading.dbk, one of its section title says about "Dist-upgrade",
so it's about "apt-get dist-upgrade"
>
>Dist-upgrade fails with Could not perform immediate
> configuration
However, paragraphs continue
13 matches
Mail list logo
