Hi,

I'd like to update hyprutils in sid to 0.14.0 and aquamarine in sid to
0.13.0-1 which are their latest upstream releases. Both packages have
been uploaded to experimental, and most of their reverse dependencies as
listed in [1][2] build fine without any sourceful changes.

The ones that don't, have pending upstream releases that have been
packaged in salsa already. I'll upload them as their dependencies turn
green in the ben tracker.

To save us some rebuilds, I would like to handle both hyprutils and
aquamarine transitions together.

The auto-generated ben trackers are at [1].

[1] https://release.debian.org/transitions/html/auto-hyprutils.html
[2] https://release.debian.org/transitions/html/auto-aquamarine.html


Ben file:

title = "hyprutils";
is_affected = .depends ~ "libhyprutils12" | .depends ~ "libhyprutils13";
is_good = .depends ~ "libhyprutils13";
is_bad = .depends ~ "libhyprutils12";

Heya,

aquamarine 0.14.0 just got released, changing the soname to
libaquamarine13. I have uploaded it to experimental.

This means the ben file for aquamarine should now look like:

  title = "aquamarine";
  is_affected = .depends ~ "libaquamarine11" | .depends ~ "libaquamarine12" | .depends  ~ "libaquamarine13";
  is_good = .depends ~ "libaquamarine13";
  is_bad = .depends ~ "libaquamarine11" | .depends ~ "libaquamarine12";

Also, since it's taking a while to start the transition, and also since
there are pending updates that don't require a newer version of
hyprutils and aquamarine, I have updated all of them in unstable, so a
simple binNMU of everything should do the trick.

There is a pending upload of hyprland 0.56.1, but that actually requires
hyprutils 0.14.0 so I'll wait until all its build-deps have
transitioned before uploading it.

Control: tags -1 confirmed

Go ahead.

Cheers,
Emilio