Your message dated Mon, 22 Jun 2020 07:18:38 +0000
with message-id <e1jngj0-000hkl...@fasolo.debian.org>
and subject line Bug#959593: fixed in pacemaker 2.0.4-1
has caused the Debian Bug report #959593,
regarding pacemaker: FTBFS: (process:8138): WARNING **: 04:11:35.695: Unable to 
create profile directory (Permission denied) (13)
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 ow...@bugs.debian.org
immediately.)


-- 
959593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pacemaker
Version: 2.0.3-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<<PKGBUILDDIR>>/doc'
> /usr/bin/asciidoc --unsafe --backend=xhtml11 --attribute footer-style=none 
> --out-file=acls.html acls.txt 
> /usr/bin/asciidoc --unsafe --backend=xhtml11 --attribute footer-style=none 
> --out-file=crm_fencing.html crm_fencing.txt 
> /usr/bin/inkscape --file=shared/en-US/images/pcmk-active-passive.svg 
> --export-dpi=45 -C 
> --export-png=shared/en-US/images/pcmk-active-passive-small.png 
> 
> ** (process:8138): WARNING **: 04:11:35.695: Unable to create profile 
> directory (Permission denied) (13)
> Unable to init server: Could not connect: Connection refused
> Unknown option --file=shared/en-US/images/pcmk-active-passive.svg
> make[2]: *** [Makefile:949: 
> shared/en-US/images/pcmk-active-passive-small.png] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/pacemaker_2.0.3-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
Source: pacemaker
Source-Version: 2.0.4-1
Done: =?utf-8?q?Ferenc_W=C3=A1gner?= <wf...@debian.org>

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

Debian distribution maintenance software
pp.
Ferenc Wágner <wf...@debian.org> (supplier of updated pacemaker 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 ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Sun, 21 Jun 2020 20:32:05 +0200
Source: pacemaker
Architecture: source
Version: 2.0.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 
<debian-ha-maintain...@alioth-lists.debian.net>
Changed-By: Ferenc Wágner <wf...@debian.org>
Closes: 959593
Changes:
 pacemaker (2.0.4-1) unstable; urgency=medium
 .
   [ Rafael David Tinoco ]
   * [30838df] Omit pacemaker-resource-agents on Ubuntu/i386
 .
   [ Ferenc Wágner ]
   * [bc43eed] New upstream release (2.0.4) (Closes: #959593)
   * [a4e8629] Drop upstreamed patch, refresh the rest
   * [42ee58f] Enable CIB secrets and ship the cibsecret tool
   * [13be83d] Update Standards-Version to 4.5.0 (no changes required)
   * [90d9610] New patch: libpacemaker calls into libstonithd directly
   * [61500a3] The obsolete ACL document was removed altogether.
     In upstream commit d796f1e, because it was superseded by a new chapter
     of Pacemaker Explained.
   * [dce33c1] Drop dummy packages which were already transitional in buster
   * [3f7de34] Update symbols files.
     The newly disappeared symbols weren't present in the headers shipped in
     pacemaker-dev, except for three functions in attrd.h.  However, those
     weren't documented either and the header was renamed to attrd_internal.h
     to show its internal status (see upstream commit 16c7d122e).
   * [4bbb828] Update packaging list email address
   * [7c12194] New patch: Fix typo: evalute => evaluate
   * [8d9cbd4] The bullseye toolchain defaults to linking with --as-needed
Checksums-Sha1:
 e0f76c988f97706b24fce497c337ef202477752a 3415 pacemaker_2.0.4-1.dsc
 a065fd74d65d60212618701ea45f8f2add9dbfd3 5134516 pacemaker_2.0.4.orig.tar.gz
 38f54634968cc3bd94eb3cfb15280cc707ef5f13 45872 pacemaker_2.0.4-1.debian.tar.xz
 96af15fa6d5ca7fafeb9904413260e629dda5db1 26861 
pacemaker_2.0.4-1_amd64.buildinfo
Checksums-Sha256:
 084b2c6888d30913864af1d3f3c20d48822ae5055e628b4d969867f5e876e2cc 3415 
pacemaker_2.0.4-1.dsc
 dccc37190230e1ee645966d279f90ea989f44f4c619274684bef4ccb6de6f371 5134516 
pacemaker_2.0.4.orig.tar.gz
 80ef80d8195e7ba1ffa18123678f7445e87439f63dd8f6deed1ce1d315bf433e 45872 
pacemaker_2.0.4-1.debian.tar.xz
 cdbcf8ae9c5c4c69eaf60fe075634e18e0d81a400c6919d2613dbfcf6ec2cc42 26861 
pacemaker_2.0.4-1_amd64.buildinfo
Files:
 69de496023a60e23e52264330f05a973 3415 admin optional pacemaker_2.0.4-1.dsc
 ed31f72fd9ce2982eb392698979c7e36 5134516 admin optional 
pacemaker_2.0.4.orig.tar.gz
 e07f9e17acb127e7de8966e5c3fc736a 45872 admin optional 
pacemaker_2.0.4-1.debian.tar.xz
 dac8f7cdaf3aa7fef9b4b3c4ca3fffbe 26861 admin optional 
pacemaker_2.0.4-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEEwddEx0RNIUL7eugtOsj3Fkd+2yMFAl7wVVcACgkQOsj3Fkd+
2yN3OhAAj24R5OZs7moQ00ztuXXLXzGHsQY0q4ObIwLV1M3VjuX9kjHnb/Ekn4j8
shbycx2bqh1RHdgDNsStctul12jjYWtNl5GrBo/v+zA4ZeY9kauaOu1arleVdGV4
FnK6YYQAu7XBRT3ptDKyO8rykm5L+RSzlozFPhHAtC5eBkjozgzqPsxWVWqws3YW
FVj3t1fQ9DmREIX0AUbel+D8EYzD0yDXH2SSz0YPZiYEJD9X9YYjpaZzxZMOqXMK
t7vC1Zf1JCJGVVyY/tPBITb1ROUFGIhm4pfyyyXFpTJPBbQtS9lDf/BIwEyWX0YK
SclvhCSqkXn4BvnRp4+r6TdLP77ctDxn1sTDbGtajGTnQQg5S9VP/M+s1gzCc3zp
DJAimHGIbazQBT+q86VmoR/8IzpPER0dxppgwq6zxu83BEnwFkDKv2P54YWvAYwa
Ny0+eK3cVfWjdy5V1ZvMkdYlmwM1enZUYOkf153FS3zqcCzR7/Qn6kVCwuCQPaM/
3LCMRhTUtbKLUbBJQ5iSciHRpRv40ePvfKYMRf3oWDS2pOnAj2kXWZ3Wws23LPCe
KIRepnJigs0fAiTHge5TPXaUNdExQD4919lbKQHcxWaJ29nyuKhInKpT3Wiixpky
wDhYQFgYIbxCK86arVIxdvC+oHU2BgVGgicc1g7Z52n4PRxjXd8=
=LdXq
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to