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

Bug#1012524: marked as done (libass: PGP signature and i386 assembly)

Your message dated Thu, 01 Dec 2022 09:35:38 +0000
with message-id <E1p0fyk-00HAnn-OS@fasolo.debian.org>
and subject line Bug#1012524: fixed in libass 1:0.17.0-1
has caused the Debian Bug report #1012524,
regarding libass: PGP signature and i386 assembly
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.)


-- 
1012524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012524
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libass
Version: 1:0.16.0-1
Severity: minor

Hi!

I noticed 7a4ee5d47246b80de8bb16ee75faf65bd9cd91b5 recently added the PGP 
key used to sign the last release for future verification. However, as the
0.16.0 release notes and the MAINTAINERS file note, future releases may
also be signed with a few other keys listed in the MAINTAINERS file.

To my understanding something like the following will allow uscan to match 
with any of the authorised keys (alternatively fetch from a keyserver by 
IDs as found in MAINTAINERS):

  alias gpg_t='gpg --no-default-keyring --keyring /tmp/tmp.keys'
  curl https://github.com/astiob.gpg | gpg_t --import -
  curl https://github.com/TheOneric.gpg | gpg_t --import -
  curl https://github.com/rcombs.gpg | gpg_t --import -
  gpg_t --export --export-options export-minimal --armor > debian/upstream/signing-key.asc
  # To verify which keys are included
  gpg --list-packets debian/upstream/signing-key.asc


While updating to 0.16.0 --with-pic was also added for i386 assembly.
However, it appears the nasm dependency is still limited to any-amd64,
after it was in the past[1] removed from i386 due to being not PIC.
The build log[2] confirms that no assembly is built on i386.
Can this be reenabled now that PIC assembly is supported?

Something to take note of is that previously assembly was enabled also for
kfreebsd-i386. Since then, we changed[3] the 32bit assembly configuration 
for BSD systems upstream to fix an issue with regular FreeBSD.
If it truly worked before on kfreebsd-i386 (other than non-PIC being at
odds with the guidelines), then this change may inadvertently have broken 
kfreebsd-i386.
I tried to test it, but the old kfreebsd-i386 installer I found always 
crashes or gets stuck early on in my VM and I wasn't able to set up a 
chroot or multiarch from a kfreebsd-amd64 host either. I can however 
confirm that on kfreebsd-64 the assembly works as intended.


Cheers

Oneric


[1]: https://salsa.debian.org/multimedia-team/libass/-/commit/d9eae1f0aefacf9b8c838cb5108dcc100f336e0b
[2]: https://buildd.debian.org/status/fetch.php?pkg=libass&arch=i386&ver=1%3A0.16.0-1&stamp=1652520467&raw=0
[3]: https://github.com/libass/libass/commit/3855299b0721acfeb5391a140cd6df65ce2b73d2

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Source: libass
Source-Version: 1:0.17.0-1
Done: Sebastian Ramacher <sramacher@debian.org>

We believe that the bug you reported is fixed in the latest version of
libass, 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 1012524@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher <sramacher@debian.org> (supplier of updated libass 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: Thu, 01 Dec 2022 10:12:09 +0100
Source: libass
Architecture: source
Version: 1:0.17.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Sebastian Ramacher <sramacher@debian.org>
Closes: 1012524
Changes:
 libass (1:0.17.0-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Opportunistically check upstream PGP signatures.
 .
   [ Sebastian Ramacher ]
   * New upstream version 0.17.0
   * debian/control:
     - Also BD on nasm on any-i386 (Closes: #1012524)
     - Change to libfontconfig-dev
     - Add libunibreak-dev to Buuild-Depends
   * debian/watch: Use api.github.com
   * debian/upstream: Update upstream signing keys
Checksums-Sha1:
 d979e5df59a8c10a30c30e349f6468bac842566a 2370 libass_0.17.0-1.dsc
 a97f8d62c7802ae90d77aa3ffae6050e39491e51 403780 libass_0.17.0.orig.tar.xz
 00e4dc8b8e4df3804936c9e0e0e326cc1826e39e 833 libass_0.17.0.orig.tar.xz.asc
 5f577a5eb72929f844b608293da0795751eedb82 15576 libass_0.17.0-1.debian.tar.xz
Checksums-Sha256:
 506ae9a58e34936dd5c89278ae3666a6b721ab7225164e5e369849d5c8d1320b 2370 libass_0.17.0-1.dsc
 971e2e1db59d440f88516dcd1187108419a370e64863f70687da599fdf66cc1a 403780 libass_0.17.0.orig.tar.xz
 38cfbb8c5dbc158d3be6582bf9123c46c5f2618d918407d1c6748213630cf6a3 833 libass_0.17.0.orig.tar.xz.asc
 9f1600e2570ea0d06bd312897e81a6d4631657196d3fa6a952661407a1e3a659 15576 libass_0.17.0-1.debian.tar.xz
Files:
 3e4fff9ee2befc4001fbb0fe990a0749 2370 libs optional libass_0.17.0-1.dsc
 25f7435779aa28eb7dbd3f76f4d17d15 403780 libs optional libass_0.17.0.orig.tar.xz
 e5514e60f6d466e314df92d16978de35 833 libs optional libass_0.17.0.orig.tar.xz.asc
 1b18d06b51148cc27d9d027d4a27f604 15576 libs optional libass_0.17.0-1.debian.tar.xz

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

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmOIcj4ACgkQafL8UW6n
GZOyaw//Zyp8VWhIpvC8RgddPrn6YSHGMMa/oSQj11PuHlst8IJnFi972bQh6vfn
HInZuL25thYz2R36tgPJR0XOoNX1Rf7v4EOXVz4T85qNxCVSj4VgU9hEN7CJ7r3h
o9HDaomaVEOBoVRBaAF8s4ZmA8P77ABD0oXJPdhknogyYyKhhkYIjvzLenlIvL8B
mZ7+CV412vnD/Tz9k+d45wb8Y6JEEaJWpaEXRbellvhXu8SvTC3le44d858jhY0T
cyBn6toGAQZBNmK1Y+W9td3MnuqpJqe6t32ek9JZoJ+pqgyhpow8hlKeBOI7mmLX
rh4PdgaoI7PgGNPvt4U+ucVCYoJkq/Q5XBcZdNyWYJ6UQdJpnywS97TDQszmhJg3
3A0nQ0Mr3qP774PIh7TgURexeqq6SrVjc/75a06hBEsz+bVuH+IhhqF5bY6hneZD
v9avdIoq6kZyTHZPBaPqimAmKJ72MdmRk0ZLmIQiH2FGC5xSDZog15PqORdptRfA
/izXnjEpFO6u2Ch9TyCbTOTRW90N1RWd5eq68KUZyscLw/AQsx83FBNhH+VYu3qm
IsoJNRgqa3vMUcA4HLHPuPWKrUuZQxj0NbH9VeJMhrib0T+stmz6Hvsi9NOEuYNO
khwkYzn+J9CYyuuC+/Yxj29I4SDtK8srrA/NUtW02rk1uYxWVHA=
=4x0I
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: