Bug#856603: RFS: arc-theme/20170302-1
On Thu, Mar 02, 2017 at 09:11:32PM +0000, David Mohammed wrote:
> I am looking for a sponsor for my package "arc-theme"
>
> * Package name : arc-theme
> Version : 20170302-1
> Changes since the last upload:
>
> * New upstream release
> - Cinnamon 3.2 fixes
> - Fix frame borders with GTK+3.22.9
> - Small bugfixes
> * Packaging Changes
> - update copyright year from 2016 to 2016-2017
These changes are in no way fit for a freeze exception.
> Notes:
> I see that sid contains GTK+3.22.9 whereas stretch (testing) is
> currently carrying GTK+3.22.8
>
> I presume that stretch will update to upstream's recommended
> GTK+3.22.9 version shortly (Ubuntu 17.04 is similarly making this move
> shortly) - as such, as soon as Debian Stretch does, arc-theme will
> then be visually broken due to this issue:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=779005
>
> 'After upgrading to GTK 3.22.9 frame border style should be applied to
> frame.flat > border instead of frame > border.flat.' The Adwaita theme
> was updated for these requirements too:
>
> https://git.gnome.org/browse/gtk%2B/commit/?id=0c20604932f
>
> I can confirm that this release of arc-theme works with GTK+3.22.8 as
> well as GTK+3.22.9
On the other hand, gtk+3.0 has, likewise, changes that don't look
appropriate for a freeze exception either. It's a mess, actually:
testing has 3.22.8-1.
3.22.9-1 is a whole new upstream release, with changes that actively break
unrelated packages. As you just mentioned, it does at least require themes
to be updated, and, as usual for GTK 3 new releases, probably a bunch of
gtk-3 using programs as well.
Then there's 3.22.9-2 which is a targetted RC bug fix... atop of bad
3.22.9-1 rather than testing's 3.22.8-1. Ie, exactly the reason why
uploading random changes to unstable during freeze is a bad idea.
I see that gtk+3.0's maintainers will need to make a separate upload to
testing-proposed-updates with a 3.22.8-2.
However, the migration status at the PTS vs tracker.d.o looks wrong: the
former mentions an unblock request while the latter says it's (as expected)
frozen. As there's no unblock bug on release.debian.org, I assume the PTS
once again shows stale data.
CC-ing debian-release -- could you guys please clarify what's amiss?
--
⢀⣴⠾⠻⢶⣦⠀ Meow!
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second
⠈⠳⣄⠀⠀⠀⠀ preimage for double rot13!
Reply to: