vcswatch reports that
this package seems to have a new changelog entry (version
51+3, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit 471f86c7d0ba84e75e2c77fe264879d7015f08d5
Author: Jeremy Bícha <jbicha@ubuntu.com>
Date: Tue Oct 20 12:29:28 2026 +0200
Update debian/changelog
to avoid the change I reverted from showing up there
commit 810dd20312ad3cc73e1fd8365e569c71bd013038
Author: Jeremy Bícha <jbicha@ubuntu.com>
Date: Tue Oct 20 12:29:02 2026 +0200
gnome-core: Update minimum gnome-shell to 50
commit cede513c25520a9fddb52bc9137a5444831c7f86
Author: Jeremy Bícha <jbicha@ubuntu.com>
Date: Mon Oct 19 14:36:06 2026 +0200
Remove LICENSE file
This was added temporarily to get GitLab to recognize
the correct LICENSE for this project since it appears
that GitLab does not recognize license in subfolders.
It appears like GitLab remembers the LICENSE even after
the license file is removed. I don't know if this state
is temporary.
Unfortunately, there are some 3.0 (quilt) packages that
cannot edit outside debian/ so this seems like a workaround
that was worth trying.
meta-gnome is technically 3.0 (native) so isn't necessarily
affected by that limitation
commit 1cec3ed2e2d2fa8fae139e4aabebb42dca5b8952
Author: Jeremy Bícha <jbicha@debian.org>
Date: Mon Oct 19 08:35:42 2026 -0400
Add LICENSE
commit 1943abe1eb31737cde8e856dacf10e8a9a471e1e
Author: Jeremy Bícha <jbicha@ubuntu.com>
Date: Fri Oct 16 04:35:52 2026 +0200
Opt into Salsa CI
mainly for piuparts to ensure installability
Adding an autopkgtest to check installability wouldn't work
because we may want to have dependencies that aren't yet in Testing
but are expected to migrate to Testing before meta-gnome would.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/m/meta-gnome.png){kind=link}