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

Bug#1069633: marked as done (Time to remove yasm from Debian?)

Your message dated Wed, 29 Oct 2025 11:24:23 +0000
with message-id <E1vE4Hv-00HUgT-29@fasolo.debian.org>
and subject line Bug#1069633: fixed in gst-libav1.0 1.26.7-2
has caused the Debian Bug report #1069633,
regarding Time to remove yasm from Debian?
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.)


-- 
1069633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069633
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: yasm
Version: 1.3.0-4

In <URL: https://github.com/yasm/yasm/issues/164 >, the upstream
developer of yasm states "I'm still alive, but have moved on to other
projects. If someone else wants to take on maintainership, I'd be happy
to give them the access to this repo do so (presumably with some kind of
transitional period where I would review/approve PRs).".  The many open
security issues listed on
<URL: https://security-tracker.debian.org/tracker/source-package/yasm >
are all unsolved, and bsed on the statement above and the time duration
since it was expressed it seem unlikely that this will change any time
soon.

Perhaps it is time to remove yasm from Debian and move all reverse build
dependencies to use a different assembler?

-- 
Happy hacking
Petter Reinholdtsen

--- End Message ---
--- Begin Message --- 
Source: gst-libav1.0
Source-Version: 1.26.7-2
Done: Marc Leeman <marc.leeman@gmail.com>

We believe that the bug you reported is fixed in the latest version of
gst-libav1.0, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1069633@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marc Leeman <marc.leeman@gmail.com> (supplier of updated gst-libav1.0 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 29 Oct 2025 10:37:46 +0100
Source: gst-libav1.0
Architecture: source
Version: 1.26.7-2
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of GStreamer packages <gst-libav1.0@packages.debian.org>
Changed-By: Marc Leeman <marc.leeman@gmail.com>
Closes: 1069633
Changes:
 gst-libav1.0 (1.26.7-2) unstable; urgency=medium
 .
   * d/control: bump meson version to match meson.build
   * d/control: remove unused dependency on yasm (Closes: #1069633)
Checksums-Sha1:
 93f4bc50e1c78f0cbeec6dce1deb40293aa14f4a 2700 gst-libav1.0_1.26.7-2.dsc
 1d5534aa0793861600c4cf5ff42ee07b3ccadea0 17744 gst-libav1.0_1.26.7-2.debian.tar.xz
 7c37799ec67818ca708424acba5783135db05e73 17185 gst-libav1.0_1.26.7-2_source.buildinfo
Checksums-Sha256:
 39069331bf4a59f0d7babf2dd913e7b35fda451544d70b5cbefc33a702b994ad 2700 gst-libav1.0_1.26.7-2.dsc
 398cc76d01a585aa586aba80fa71db77862a2d711bd42c84451287f3b267f2d8 17744 gst-libav1.0_1.26.7-2.debian.tar.xz
 401572d5571beb0d47ef8b008ecf3e69bbf4c4de4288b5b5f6e9f926dea80246 17185 gst-libav1.0_1.26.7-2_source.buildinfo
Files:
 5972af4fc799faf5a884a5d1b82e01a7 2700 libs optional gst-libav1.0_1.26.7-2.dsc
 80bd6c2f8205005d0f73ab0df0d17d7c 17744 libs optional gst-libav1.0_1.26.7-2.debian.tar.xz
 16b7df5282ddde5bd06211b292ff522b 17185 libs optional gst-libav1.0_1.26.7-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJKBAEBCgA0FiEEgnz9dLpGgVKgQfOgempPF1mVplsFAmkB4HkWHG1hcmMubGVl
bWFuQGdtYWlsLmNvbQAKCRB6ak8XWZWmWy47D/44cKIZiyeI6xzCSl3RRNcJ/dxw
aoTDhN+K2sTXJ0OwXnDaJmdrlWGomYhYIYAgRdiAnpKFQ+P/jEy1aJGBRf1er4j7
X6tbktEdnGgIbFULNsL2rQOasfaMyBIEdxI5xYRVyno2jfyb3dRtr/KdY9GiDo+Z
Hy6W4Re2tzHcv7xbOMPJbnxnoWdgakXZqnf/lLAya35HdMoIAPRHNUhvFDncbkpB
d5Gy065EKHlincdg/eKmUU/nhf419RTczzH6wgfaadn2D9nr7c7cPz30e1kEcT5K
fP+llKEjk2zOmlFDGNzpdbuxRj35fylOvZDFo5I5AdGPTM5PMpG3dV0V2YFIH/h7
GAFho+DC/1xdk2hrbCptebSXbRkwR4VEsFFgTDzEHc8LpBKQ7BbsL5bjcTqCPGhu
c8jrsoMWKC/ljLkncFdiHAtOGQEyV0a+LFojeJGWDDRyKZw81fimiPKisw2Nv5xd
6L7plHBh2m+TdDB6qU2rou6QVdVwllkNUXCbFa5Q0J2btzu+KjE2KcYrGfCOrkLL
Fsib+Ha/9umGIRY0PlyoLOuRRfa/CrdPbCAs3fi9o69wbh5kC6FHiljBgB8c9tgF
SYWfRUEXnPnQfRLuVGdrDGj3/Dj8XOklzcB/puNXNubohdKDFDRv15cI6965Ydvb
vFh6BzMv5jjQ7EgABA==
=F/zC
-----END PGP SIGNATURE-----

Attachment: pgplSKR410x8i.pgp
Description: PGP signature


--- End Message ---
Reply to: