[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#819800: marked as done (sources.list(5): contradictory about when to use deb822 format)

Your message dated Mon, 4 Apr 2016 13:46:14 +0200
with message-id <20160404114614.GA3986@crossbow>
and subject line Re: Bug#819800: sources.list(5): contradictory about when to use deb822 format
has caused the Debian Bug report #819800,
regarding sources.list(5): contradictory about when to use deb822 format
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 owner@bugs.debian.org
immediately.)


-- 
819800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819800
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 1.2.9
Severity: normal

Dear deity,  ;)

i am currently looking at transition to deb822 style sources list.
Doing so i encountered a contradiction in sources.list(5).

First it says deb822 is avail since apt 1.1, then it goes on with given
examples all about jessie archive entries.
jessie only has apt 1.0.9, so i guess from reading above mentioned hint,
that deb822 style won't work in jessie.

The manpage should be updated to be unambiguous:
:%s/\<jessie\>/stretch/g

Thanks.



kind regards,

     Thilo



-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apt depends on:
ii  adduser                 3.114
ii  debian-archive-keyring  2014.3
ii  gnupg                   1.4.20-4
ii  gnupg2                  2.1.11-6
ii  gpgv                    1.4.20-4
ii  libapt-pkg5.0           1.2.9
ii  libc6                   2.22-4
ii  libgcc1                 1:5.3.1-13
ii  libstdc++6              5.3.1-13

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc     <none>
ii  aptitude    0.7.5-3
ii  dpkg-dev    1.18.4
ii  python-apt  1.1.0~beta2
ii  synaptic    0.83+b1

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sat, Apr 02, 2016 at 01:11:07PM +0200, Thilo Six wrote:
> Dear deity,  ;)

Dear worshipper, :)


> i am currently looking at transition to deb822 style sources list.

("transition" is a strong word here: We aren't pushing for it yet given
that a bunch of tools do not support it [guesstimate, we haven't even
started tracking it])


> Doing so i encountered a contradiction in sources.list(5).
> 
> First it says deb822 is avail since apt 1.1, then it goes on with given
> examples all about jessie archive entries.
> jessie only has apt 1.0.9, so i guess from reading above mentioned hint,
> that deb822 style won't work in jessie.

Yes, apt/jessie does not support deb822 (at least not by default and not
in the way as documented by the manpage… so for simplicity lets just
pretend it doesn't support it at all).


> The manpage should be updated to be unambiguous:
> :%s/\<jessie\>/stretch/g

That is a good find and I would agree, but we don't use a literal
'jessie' in the documentation but the placeholder entity
debian-stable-codename, which at the moment is set to 'jessie',
but will change before freeze to 'stretch'.

We don't want to change that now as that would mean we refer to
a release (and we use it in various places) which isn't released yet
and will not be released as stable for (more than) a year still as that
would probably confuse readers more than using it as a valid, but
perhaps slightly strange, example.

[The indirection runs actually a bit further as the vendor (= the
distribution building and shipping apt) controls this example, so we
would fix that for Debian, the manpage would still have the same problem
for the others…]

So, for simplicity reasons we aren't going to fix this as this will fix
itself in a while, so I am closing as future done.


A more anecdotal reason might be that manpages generally document the
current state of things more than history, so it isn't unlikely to find
advice in them which doesn't apply to older versions.


Best regards

David Kalnischkies

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: