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

Bug#1119975: marked as done (libogg: provide a .cmake file)

Your message dated Fri, 21 Nov 2025 08:48:56 +0000
with message-id <E1vMMp6-005ePe-16@fasolo.debian.org>
and subject line Bug#1119975: fixed in libogg 1.3.6-2
has caused the Debian Bug report #1119975,
regarding libogg: provide a .cmake file
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.)


-- 
1119975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119975
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libogg
Version: 1.3.6-1
Severity: wishlist

Dear Maintainer,

Following #1118470, would it be possible to package .cmake file?

Best regards,
Patrice


-- System Information:
Debian Release: forky/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.16.12+deb14+1-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
Source: libogg
Source-Version: 1.3.6-2
Done: Fabian Greffrath <fabian@debian.org>

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

Debian distribution maintenance software
pp.
Fabian Greffrath <fabian@debian.org> (supplier of updated libogg 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: Fri, 21 Nov 2025 09:25:36 +0100
Source: libogg
Architecture: source
Version: 1.3.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Fabian Greffrath <fabian@debian.org>
Closes: 1119743 1119975
Changes:
 libogg (1.3.6-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Patrice Duroux ]
   * build using cmake (Closes: #1119975, #1119743)
   * d/control: remove RRR: no.
 .
   [ Fabian Greffrath ]
   * Add obj-*/ to debian/clean
Checksums-Sha1:
 738a21709e8dfa32e63c7c9d39c394d93e668c14 2094 libogg_1.3.6-2.dsc
 cedaf05cd98016bffb2ee2e1ec87ed4252a42d0e 18384 libogg_1.3.6-2.debian.tar.xz
 85956ac556442a0a4258e307e19dcf05b7fd2ff9 7302 libogg_1.3.6-2_amd64.buildinfo
Checksums-Sha256:
 967855d2d86d13e63a5f20f48176afedbf33ed12aeecae64b10526835e2865ea 2094 libogg_1.3.6-2.dsc
 8a7a4b0468e29485df82b9109d1dfa8ba6b97649e3ebc1a08afa23b29d85fd4e 18384 libogg_1.3.6-2.debian.tar.xz
 19e4f0f75d47e89448b84524ffd043d9a76780f1f4dee533b0a9e12e1056f90d 7302 libogg_1.3.6-2_amd64.buildinfo
Files:
 057fe563aca5f0ff02d0ccb933b05f47 2094 libs optional libogg_1.3.6-2.dsc
 7b10a24cf4078eb344aff9f0d180f7dc 18384 libs optional libogg_1.3.6-2.debian.tar.xz
 fb760191636fb642b09562d04250f67b 7302 libs optional libogg_1.3.6-2_amd64.buildinfo

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

iQJGBAEBCgAwFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAmkgIkISHGZhYmlhbkBk
ZWJpYW4ub3JnAAoJEMvqjpcMzVnfSaMP/iVW8jC2WVzvxDF6xUaM0CKxej0Uao1q
XlsNxr/IJv4rwgCDb7pQ2eqP0CSh8pqnfsOnR07poPYZYocfv+JwsaTxp8gd4TB6
TcLhcgIj/kaJ63Zs3UY7vlUsxpa2IPmsHPUTFx5q8b0zxX7qOuyULpv3+iU0+eCs
KzUB+/jL5+GpUkL0rppr7X1yAVt/O4SC9w1BxXcjaoXW72en+GwYD9NlBYvpjtLc
Ajy2169DsCXTkYz62BWemEyuaf0O2pKJEhWAdtUhKGjVmQ1dylVWV1hE2O3CUPvz
4uwvV8LEJDcC1vC+KGqBNFlQAf0Q2sYYwIMrYJlOyIRmkWnIQ4CQHh3GlXO6tV8D
tB57mPeuwoGLflgfjo8hg7ca38Ihz0RCGnE6dAbgO6HLVaHc1VBPeFDgdWyeWdOQ
cUBrf9VmQy1i4qN7d4CvB0xVbHQkWvK7fJulefyMn4MIQEbxWYez/6eSBZT8rJm0
ls5WeZQHpD8H4tWdjTg9WTUqFGXgi2xgMkQMKScMV5RhsMIqACE7pIjCchIY5vut
dA3D3TEMDrM1337afjyAIW1zv3O2pIlUeEK5HWVqRo3co9E7yD/XrKEra8CIjQEn
NiSNRbup3mcEYekPMoe2JOY7g4Mr4kPOoB9C54AoRtB+zKOfqGIfzOMnVR/EKj3Q
viHTnRSQjr62
=2qCt
-----END PGP SIGNATURE-----

Attachment: pgpP5mBCppMr9.pgp
Description: PGP signature


--- End Message ---
Reply to: