[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1108439: marked as done (unblock: gst-plugins-ugly1.0/1.26.3-4)

Your message dated Sat, 5 Jul 2025 16:33:36 +0200
with message-id <0346e302-b4cf-431f-9ef6-8007f8f9105c@debian.org>
and subject line Re: Bug#1108439: unblock: gst-plugins-ugly1.0/1.26.3-4
has caused the Debian Bug report #1108439,
regarding unblock: gst-plugins-ugly1.0/1.26.3-4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1108439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108439
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: gst-plugins-ugly1.0@packages.debian.org
Control: affects -1 src:gst-plugins-ugly1.0

Please unblock package gst-plugins-ugly1.0

[ Reason ]
gst-plugins-ugly1.0 1.26.3-1 was accidentally uploaded to unstable
instead of experimental. My understanding is that we generally do not
want things to be stuck in unstable.

Occasionally, gst-plugins-ugly1.0 gets security updates and it's
generally preferred to upload security updates to unstable for
migration to testing.

https://security-tracker.debian.org/tracker/source-package/gst-plugins-ugly1.0

[ Impact ]
There aren't any upstream code changes; just a version bump.

[ Tests ]
There are minimal upstream build tests. In this upload, I also made a
change to ensure that dh_auto_test failures will fail the build;
previously, this was only done for amd64 and arm64.

[ Risks ]
Key package for probably every Debian desktop (recommended by libreoffice-core)

[ Other Info ]
In general, I think that we are not intending to push gstreamer 1.26.3
to trixie, but we may try to do a Stable Update for trixie later to
update to a newer 1.26.x version.

[ Checklist ]
  [✔️] all changes are documented in the d/changelog
  [✔️] I reviewed all changes and I approve them
  [✔️] attach debdiff against the package in testing

unblock gst-plugins-ugly1.0/1.26.3-4

Thank you,
Jeremy Bícha

Attachment: gst-plugins-ugly1.0_1.26.3-4.debdiff
Description: Binary data


--- End Message ---
--- Begin Message --- 
Hi

On 28-06-2025 19:00, Jeremy Bícha wrote:

gst-plugins-ugly1.0 1.26.3-1 was accidentally uploaded to unstable
instead of experimental.



Ugg..


My understanding is that we generally do not
want things to be stuck in unstable.



Yes, but in the current phase it's a more delicate trade off.


Occasionally, gst-plugins-ugly1.0 gets security updates and it's
generally preferred to upload security updates to unstable for
migration to testing.
Ack, although in this case the accidental upload could go with the next upload if the security issue materialized.... 


There are minimal upstream build tests. In this upload, I also made a
change to ensure that dh_auto_test failures will fail the build;
previously, this was only done for amd64 and arm64.



... but I'll pick it because of this test coverage improvement.

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: