Bug#971807: buster-pu: package webext-tbsync
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
> > retitle 971807 buster-pu: package webext-tbsync
> > user release.debian.org@packages.debian.org
> > usertags 971807 + pu
> > thanks
> >
> > On Wed, 2020-10-07 at 20:39 +0200, Mechtilde Stehmann wrote:
> > > Package: release.debian.org
> > > Version:
> > > Severity: grave
> >
> > Absolutely not. A stable update is generally - and at most - normal
> > severity.
>
> I choose 'grave' because the bugs about the incompatibility are set
> to grave like #968102.
The package might well have an RC bug. The release process does not. :-
)
[...]
> > You want 2.16.1-0+deb10u1 or 2.16.1-1~deb10u1, with an appropriate
> > changelog stanza on top of either the current stable package or the
> > unstable upload, depending on which way you go.
>
> yes I will take the right versioning 2.16.1~deb10u1-1.
You have the components out of order - it's 2.16.1-1~deb10u1, not
2.16.1~deb10u1-1. It's effectively a backport of 2.16.1-1.
> It is needed to be uploaded to stable-update because of the
> > > update
> > > thunderbird 68 to 78.
> >
> > Is the new package compatible with Thunderbird 68 as well?
>
> The new package isn't compatible with Thunderbird 68 but only with 78
> as described in d/control. That's why it is useful to update to
> stable-update and not to proposed-update.
One *can't* "update [in] stable-updates and not proposed-updates". An
update to stable is *always* made via proposed-updates. The Release
Team may then choose to copy the package to stable-updates as well, but
the upload is no different from any other.
> 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... :-)
Regards,
Adam
Reply to: