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

Bug#1053179: marked as done (libavif: drop doc generation on arches without pandoc)

Your message dated Wed, 11 Oct 2023 23:49:10 +0000
with message-id <E1qqiww-001EFK-PO@fasolo.debian.org>
and subject line Bug#1053179: fixed in libavif 1.0.1-2
has caused the Debian Bug report #1053179,
regarding libavif: drop doc generation on arches without pandoc
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.)


-- 
1053179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053179
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libavif
Version: 0.11.1-3
Severity: normal

The libavif build attempts to build docs (the man page) using pandoc
for each architecture. This is a problem since pandoc is not available
on several architectures.

debian/rules for libavif contains doc logic, defining MAN_PAGES_FLAG.
Currently it is only switched off if nodoc is used.

It would be helpful for the arches which don't have pandoc to switch
off the MAN_PAGES_FLAG for these selected architectures, similar to
the architecture-specific configuration already used to set SVT_FLAG.

The affected architectures are summarised on the build page
https://buildd.debian.org/status/package.php?p=libavif :

hppa
hurd-i386
loong64
sparc64

pandoc is only used to generate the man page.  I guess it does not
significantly differ between architectures.  Perhaps a copy of the
amd64 man page could be stored in the debian dir and used for these
architectures that can't generate their own man page.

--- End Message ---
--- Begin Message --- 
Source: libavif
Source-Version: 1.0.1-2
Done: Boyuan Yang <byang@debian.org>

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

Debian distribution maintenance software
pp.
Boyuan Yang <byang@debian.org> (supplier of updated libavif 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, 11 Oct 2023 19:30:04 -0400
Source: libavif
Architecture: source
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Boyuan Yang <byang@debian.org>
Closes: 1053179
Changes:
 libavif (1.0.1-2) unstable; urgency=medium
 .
   * debian/control,debian/rules: Adjust build-dep architecture requirement:
     + Add loong64 for libgav1-dev.
     + Add riscv64 loong64 for librav1e-dev.
     + Add loong64 for librav1e-dev.
     + Disable hppa hurd-i386 loong64 sparc64 for pandoc.
   * debian/rules: Use prebuilt man pages when pandoc is disabled.
     If pandoc is disabled in debian/control, use prebuilt copied
     located at debian/avifenc.1 and debian/avifdec.1.
     (Closes: #1053179)
Checksums-Sha1:
 f883500b697c91400c888518c588fab0c5ec29ce 2715 libavif_1.0.1-2.dsc
 780e8ba3824deccdb08401a5e2b16ca974b948f4 10569767 libavif_1.0.1.orig.tar.gz
 b63854e58068107dcf551c6718f8d15a07d8e3b7 9976 libavif_1.0.1-2.debian.tar.xz
 2a157ad9384b6bf05522d1a11de341c29a9287ff 10932 libavif_1.0.1-2_amd64.buildinfo
Checksums-Sha256:
 eb90f8cf34c32e3b1c5506b1b71eb05e945a7f7b41e24497803ed89f103762f2 2715 libavif_1.0.1-2.dsc
 398fe7039ce35db80fe7da8d116035924f2c02ea4a4aa9f4903df6699287599c 10569767 libavif_1.0.1.orig.tar.gz
 f6c8cecbee9d134b897471d37ea96698377b9426245bc542816424e0bd7dfc74 9976 libavif_1.0.1-2.debian.tar.xz
 11c82838f45b47ba8ff148ae93c82a72ba035ec196c604de8e066f290a227320 10932 libavif_1.0.1-2_amd64.buildinfo
Files:
 cd287bf07111c5be4f31a6043f0f6333 2715 libs optional libavif_1.0.1-2.dsc
 d7b2a7da1fb652b40936b09ffb006b24 10569767 libs optional libavif_1.0.1.orig.tar.gz
 7fc1e03b89f181acaa7e8965d56de6e3 9976 libs optional libavif_1.0.1-2.debian.tar.xz
 0765722cd8d95a053462f1a2afebeb47 10932 libs optional libavif_1.0.1-2_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmUnMO8ACgkQwpPntGGC
Ws62QBAAgGTiW+BSJaPgjayE7vcwsfXzh96zkEDcGvSMrF2BL7THBEHviJz6Ffrk
uvuFCaNa6AQo50uwZFMykAbGR9gu2VAXR+wBUoTfgY+EPbnlKTaBUiNTkuTEXxG1
Hpw9OHuUcaE0XflNwmH8rfqJCAHM0X//kc3Bw6Ss339D8p73F+a1CovFl/LwjZda
5ILO3BpmSbA+/4JcAy+b+HhQVOJ4FDc8OxGZfKlRnP4feEmJfSDCiN1nQ6St7uGj
O9TbwAKbbPs2FaH1CkW8fus5S9Uz+gUfbSdV0BkLFsJxdkMX/mhT7Vn2inBZudma
Ly+sBZ9PjhrEl7gCRa/gBshYRKpB7mxaVLtSwEYyDftVabjgvbnI1/4F+vEqfl/G
Vkqltov93adue0XKxel9kF/snL9C6lejZEu6NhnYYSHfwmdopReY/l557fKN8ujV
l62Sx1CH+U94CsopbNgitnXqRm7J9k2Clrmd6R38RjhN4IFgQYcLlrJKzH7WSCaN
s06w0NuSfRCzZKrxJIWob4CCDm9ybmjSvKWKerCsAcSVhsKblWClVp241Mh7QUpT
5CWvwv0AN5DJcaCzKG2N0ZPJpHZx0uur8VW2uRJI7fPqwxAGZDqao4CYUMvGfP+D
/jeplYg9f6Oq1Us4UOeaXjxI3mujT9EARb3vobHuDi7kCWnxNu0=
=7GrY
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: