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

Accepted lyx 2.4.1-2 (source) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 12 Jul 2024 21:32:07 +0200
Source: lyx
Architecture: source
Version: 2.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Dr. Tobias Quathamer <toddy@debian.org>
Changed-By: Dr. Tobias Quathamer <toddy@debian.org>
Changes:
 lyx (2.4.1-2) unstable; urgency=medium
 .
   [ Sven Hoexter ]
   * Drop mailcap mimetype file.
     While re-reading Debian Policy section 9.7 I understood that if you
     ship a .desktop file you can drop the mailcap mimetype definition.
     The system /etc/mailcap file will be updated automagically based
     on the information shipped in the .desktop file.
   * Provide a lyx mimetype icon for the hicolor default theme.
     At least file manager which use the hicolor theme will be
     able to find the LyX icon associated with the application/x-lyx
     mime type via the .desktop file.
Checksums-Sha1:
 a2491954d3ca6a5a0b0ee493d0494ee5698fff04 2414 lyx_2.4.1-2.dsc
 9d45d5be6015356ef3c5ec744ad0309d6160da46 31788 lyx_2.4.1-2.debian.tar.xz
 7a525162e59104c596bb213f539f35474645b03f 12635 lyx_2.4.1-2_amd64.buildinfo
Checksums-Sha256:
 57a00593260bb84e23c8d489ab6504f244c83556426fbff8f65a5db92b27212f 2414 lyx_2.4.1-2.dsc
 f8368919b33e96c430ff5675913ec746956c8f75dfb4841bbbb969c051627fb8 31788 lyx_2.4.1-2.debian.tar.xz
 a441fa11c752b9e7daea928a3f1cabb79fd8aedc78e2eb1e60f427e19375c6ff 12635 lyx_2.4.1-2_amd64.buildinfo
Files:
 1cb44b0378fff2977d629ca035172a7f 2414 editors optional lyx_2.4.1-2.dsc
 645762f67be53a4005235b52c132895c 31788 editors optional lyx_2.4.1-2.debian.tar.xz
 43c72d89d020553cfae1120c03308709 12635 editors optional lyx_2.4.1-2_amd64.buildinfo

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

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAmaRh3AACgkQEwLx8Dbr
6xmdmQ/6A2+Yv5HpUC/S6cUlydsGLvuJV8vYGq/3Y47ZvfrKKTwlqS6qwbrH0qZ/
1PlIvcWSz8lBZyyQNIiDDAS5qTmSLT7HuNEZMozkdqbAFlE7oCaQKZmpe0s1W1nq
1alwyrO8UYriY+llQfQKpCF1i5rDmpGdtg8HpWmphN5NYau5ze8ulOnPiyQH4CVK
DiClZcfoAxlGVLhToy3ed6SE0UOEVLZfR+ioABdtzbNNSdXsDVzPpC4piPrCb5RO
9wYTiYwvbdq7TKq1bmyu+MWFjDgdy+cBwv6UlgRvX3X2IkbMpticzAmUggIicWUz
SNgLMB4gdlft06qQ88Us6JU0FOOeTY1m9QMXHcJJKYBEox/ymjsAnYrMyaOp+nzG
yq6aytrm4A2bbza9ayi6RKWhk54fYsJ1EAQzw9mGpeZKzj1znMgGQI+z5dU/UwWG
A/JGPZM94nftnuDf85eNjjtYfRiraHnavYDd0p2S64xtTIXP/24qiSsCy7wVYDuf
tPYdF2fphjL3J5y8iMi+UIADdz7SB5mx0tJWSo8zrHwHbcefM4MSMJtoxT5OLJ0p
Mlfe0/C1Zl2b9VONxXz3VLwEnuu3z8qaCUIolvntTDB0/YIjbTDXdX02uihYj4wz
fNjkYTwdKIc7cDqASR3quAgOsA9BMncydIev9Se11KeZiuO0gek=
=kKfM
-----END PGP SIGNATURE-----

Attachment: pgp6WVkZ5LRSR.pgp
Description: PGP signature


Reply to: