Pkg xen devel - Dec 2024 - Your xen stable upload

On Sun, 2024-08-25 at 15:59 +0200, Hans van Kranenburg
wrote:
> Hi Adam,
> 
> On 8/25/24 15:26, Adam D. Barratt wrote:
> > 
> > I noticed that there's a xen upload in the stable-new queue, which
> > claims to have been uploaded by you.
> > 
> > I'm afraid that we can't accept it currently, because it is a
newer
> > version than is currently in unstable and testing:
[...]
> Fair enough. I just read this after finishing the accompanying bts
> bug report, which also mentions that.
> 
> We're running into problems with 4.17.5-1 for unstable, which is most
> likely related to compatibility issues with newer ocaml in unstable.
We now have 4.19.1 in unstable, and after DSA 5836-1, both 4.17.5-
1~deb12u1 and 4.17.5+23-ga4e5191dc0-1 in stable-new. Should the former
be rejected in favour of the version from the DSA?

I'm tempted to leave the packages in stable-new in any case until the
new version manages to migrate to testing, just to avoid any potential
version skew issues as we're not far off the next point release.

Regards,

Adam

Hi,

On 28/12/2024 22:43, Adam D. Barratt wrote:
> On Sun, 2024-08-25 at 15:59 +0200, Hans van Kranenburg wrote:
>> Hi Adam,
>>
>> On 8/25/24 15:26, Adam D. Barratt wrote:
>>>
>>> I noticed that there's a xen upload in the stable-new queue,
which
>>> claims to have been uploaded by you.
>>>
>>> I'm afraid that we can't accept it currently, because it is
a newer
>>> version than is currently in unstable and testing:
> [...]
>> Fair enough. I just read this after finishing the accompanying bts
>> bug report, which also mentions that.
>>
>> We're running into problems with 4.17.5-1 for unstable, which is
most
>> likely related to compatibility issues with newer ocaml in unstable.
> 
> We now have 4.19.1 in unstable, and after DSA 5836-1, both 4.17.5-
> 1~deb12u1 and 4.17.5+23-ga4e5191dc0-1 in stable-new. Should the former
> be rejected in favour of the version from the DSA?
> 
> I'm tempted to leave the packages in stable-new in any case until the
> new version manages to migrate to testing, just to avoid any potential
Sorry for the confusion.

Some people in the team had some struggles last year (*cough*).

We have 4.19.1-1 right now in sid, yay.

You can totally disregard and/or delete the 4.17.5-1~deb12u1 thing.

The 4.17.5+23-ga4e5191dc0-1 security update is the newer thing we want
instead.

Hans