Your message dated Thu, 30 Jul 2020 13:15:22 +0200
with message-id <20200730111521.3es5upqv2hu4b...@percival.namespace.at>
and subject line Re: Bug#867400: general: backports suite-names can't be
properly used in sources.list
has caused the Debian Bug report #867400,
regarding general: backports suite-names can't be properly used in sources.list
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 ow...@bugs.debian.org
immediately.)
--
867400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: normal
Hey.
Not sure where this should actually go to (apt? ftp-masters? backports?)...
please reassign as it fits :-)
It's seems to have never properly worked for me, to use the suite-names for
backports repos in sources list.
E.g. having:
deb http://foo/debian/ oldstable/updates main contrib non-free
instead of jessie/updates goes fine, but:
deb http://foo/debian/ oldstable-backports main contrib non-free
gives a warning:
W: Conflicting distribution: http://foo oldstable-backports InRelease
(expected oldstable-backports but got jessie-backports)
in aptitude and friends.
Looking at the Release files there seem to be some possibly wrong usage of the
fields?
jessie's security Release has:
Origin: Debian
Label: Debian-Security
Suite: oldstable
Codename: jessie
while that of the backports Release has:
Origin: Debian Backports
Label: Debian Backports
Suite: jessie-backports
Codename: jessie-backports
not using Suite: oldstable-backports for some reason.
Can this be fixed (for all backports suites)?
Cheers,
Chris.
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.11.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
* Christoph Anton Mitterer <cales...@scientia.net> [200730 11:13]:
> Package: general
>
> Not sure where this should actually go to (apt? ftp-masters? backports?)...
> please reassign as it fits :-)
>
> It's seems to have never properly worked for me, to use the suite-names for
> backports repos in sources list.
This looks like something the backports ftpmasters would need to
take care of. The best way of reaching them is probably via the
backports mailing list [1].
As this bug cannot be handled in the Debian BTS, I'm closing it
here.
Chris
[1] https://lists.debian.org/debian-backports/
--- End Message ---
