Bug#971807: buster-pu: package webext-tbsync
On Sat, 2020-10-10 at 11:16 +0200, Mechtilde Stehmann wrote:
> Hello Adam,
Hi,
I've replied to the bug, as that's where you raised the questions, but
as this is trending towards general discussion we should possibly move
it to the debian-release list instead.
> Am 07.10.20 um 21:45 schrieb Adam D. Barratt:
> > On Wed, 2020-10-07 at 21:24 +0200, Mechtilde Stehmann wrote:
> > > Hello Adam,
> > >
> > > On Wed, 07 Oct 2020 19:54:41 +0100 "Adam D. Barratt"
> > > <adam@adam-barratt.org.uk> wrote:> severity 971807 normal
>
> ...
>
> > > Since RT updated Thunderbird in buster from version 68.x to 78.x
> > > this causes the incompatibility from webext-tbsync with the
> > > recent Thunderbird version in Buster.
> >
> > For the record, the Release Team have done no such thing. The
> > Security Team have released 78.x, which is not yet even in stable-
> > new, yet alone buster (although it likely will be in buster after
> > the next point release).
> >
> > I realise this might seem picky, but if you're going to say we
> > caused it... :-)
>
> Ok, I want to understand it and to document it properly.
>
> The secutity-team does the the update of thunderbird from 68.x to
> 78.x in buster.
>
> As I did an apt update && apt list --upgradable it already shows
> thunderbird 1:78.x in buster. So for me thunderbird 78.x is already
> released.
Where / how does it show that the package is "in buster"? Your
sources.list contains an entry for the security archive, which will be
"(security|deb).debian.org/debian-security buster/updates main" or
similar. As such the package is "in buster/updates" or "in buster-
security", but not "in buster".
The package _has been_ released, and will be available to any user of
stable who has the security archive in their APT sources (which
*should* be all of them). That is not in dispute. It is just not yet
part of the stable distribution in the main archive, "only" in the
security archive. This is a detail of the process that I expect and
appreciate that most users will never care about or possibly even be
particularly aware of.
Note that this does not in general mean that an update required to
stable by another update in the security archive cannot be made. I
would not have mentioned it at all, if you had not yourself said that
the Release Team had made the update to thunderbird. I was not honestly
expecting that comment to generate this much process discussion. :-)
> How can I follow up which package is in stable-new and not already in
> stable?
As a starting point, if the DSA was released since the most recent
point release, then the package cannot be in stable yet, as stable only
changes with point releases, which happen roughly every couple of
months.
APT will also show the difference:
$ apt-cache policy thunderbird
thunderbird:
Installed: (none)
Candidate: 1:78.3.1-2~deb10u2
Version table:
1:78.3.1-2~deb10u2 500
500 http://security.debian.org/debian-security buster/updates/main amd64 Packages
1:68.12.0-1~deb10u1 500
500 http://deb.debian.org/debian buster/main amd64 Packages
and for a package that has already been included in a point release:
$ apt-cache policy ark
ark:
Installed: (none)
Candidate: 4:18.08.3-1+deb10u2
Version table:
4:18.08.3-1+deb10u2 500
500 http://deb.debian.org/debian buster/main amd64 Packages
500 http://security.debian.org/debian-security buster/updates/main amd64 Packages
The current status of packages being potentially included in the next
point release (either via p-u, or imported from the security archive)
can be seen at https://release.debian.org/proposed-updates/stable.html
, with the top table corresponding to stable-new.
As stable-new is "just" another suite (well, it's a policy queue, but
for users that's again mostly an archive implementation detail), you
can also see the status of the package using rmadison, or dak on a
couple of DD-accessible hosts:
$ rmadison thunderbird -s stable,stable-new
thunderbird | 1:60.9.0-1~deb10u1 | stable | source, armel, armhf
thunderbird | 1:68.12.0-1~deb10u1 | stable | source, amd64, arm64, i386, mips64el, ppc64el, s390x
thunderbird | 1:78.3.1-2~deb10u1 | stable-new | source, amd64, arm64, mips64el, ppc64el
thunderbird | 1:78.3.1-2~deb10u2 | stable-new | source, amd64, arm64, i386, mips64el, ppc64el
I hope that helps resolve any queries you had regarding the process and
my earlier comment.
Regards,
Adam
Reply to: