Your message dated Sat, 10 Sep 2016 13:04:02 +0000
with message-id <[email protected]>
and subject line Bug#837249: fixed in libconfig-record-perl 1.1.2-2
has caused the Debian Bug report #837249,
regarding libconfig-record-perl: FTBFS: lib/Config/Record.pm: No such file or 
directory at Config-Record.spec.PL line 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 [email protected]
immediately.)


-- 
837249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837249
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libconfig-record-perl
Version: 1.1.2-1
Severity: serious
Tags: stretch sid
User: [email protected]
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> cp lib/Config/Record.pod blib/lib/Config/Record.pod
> cp lib/Config/Record.pm blib/lib/Config/Record.pm
> Manifying 1 pod document
> "/usr/bin/perl" "-Iblib/arch" "-Iblib/lib" Config-Record.spec.PL 
> Config-Record.spec
> lib/Config/Record.pm: No such file or directory at Config-Record.spec.PL line 
> 13.
> Makefile:438: recipe for target 'Config-Record.spec' failed
> make[1]: *** [Config-Record.spec] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/2016/09/10/libconfig-record-perl_1.1.2-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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: libconfig-record-perl
Source-Version: 1.1.2-2

We believe that the bug you reported is fixed in the latest version of
libconfig-record-perl, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann <[email protected]> (supplier of updated libconfig-record-perl 
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 [email protected])


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

Format: 1.8
Date: Sat, 10 Sep 2016 14:54:41 +0200
Source: libconfig-record-perl
Binary: libconfig-record-perl
Architecture: source
Version: 1.1.2-2
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group <[email protected]>
Changed-By: gregor herrmann <[email protected]>
Closes: 837249
Description: 
 libconfig-record-perl - Perl module for configuration file access
Changes:
 libconfig-record-perl (1.1.2-2) unstable; urgency=low
 .
   * Team upload.
 .
   [ Salvatore Bonaccorso ]
   * Change Vcs-Git to canonical URI (git://anonscm.debian.org)
   * Change search.cpan.org based URIs to metacpan.org based URIs
 .
   [ Axel Beckert ]
   * debian/copyright: migrate pre-1.0 format to 1.0 using "cme fix dpkg-
     copyright"
 .
   [ gregor herrmann ]
   * Strip trailing slash from metacpan URLs.
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-Browser URL to cgit web frontend
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * debian/rules: move {Config-Record.spec,META.yml}.PL away.
     They fail to find the module but we don't need to re-create
     Config-Record.spec and META.yml anyway during our build.
     (Closes: #837249)
   * Add more fixes to fix-spelling-error-in-manpage.patch.
     Thanks to lintian.
   * Mark package as autopkgtest-able.
   * Bump debhelper compatibility level to 9.
   * Declare compliance with Debian Policy 3.9.8.
Checksums-Sha1: 
 61fcf1efd7360d2553c7cfb2dfce8e78d815aed3 2285 libconfig-record-perl_1.1.2-2.dsc
 d1f127c83cf202b2fdbb69fcdc8cd604a531df15 2612 
libconfig-record-perl_1.1.2-2.debian.tar.xz
Checksums-Sha256: 
 3fdb30aa06de5e24cd98f4ee7129d2b201bf9b1d265d77debaa1e59bb4950440 2285 
libconfig-record-perl_1.1.2-2.dsc
 aece57df5da623e6df096eb543251d44826e4aabe60ac5151eec3a2ae9ddd255 2612 
libconfig-record-perl_1.1.2-2.debian.tar.xz
Files: 
 ebf33d2693026d8d298ea4c89a4c4c1d 2285 perl optional 
libconfig-record-perl_1.1.2-2.dsc
 dbbd220cbef89acaa10b802d275aca29 2612 perl optional 
libconfig-record-perl_1.1.2-2.debian.tar.xz

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

iQJ8BAEBCgBmBQJX1ALTXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGvugP/AnEPIkVYJPeWTtjI9WPz7rv
E0uEY5TMBpdTqehYrroWHVDt6f4BFczga1l07ZDXWVDnBSPYiQOOai+hv5Vo7Inn
Vq2BMLzc3bS0J5vJ358agzgra0xd9kxUZL/ie5G3OOZ8NihB0Yo2DPn6Q8KmHO4c
cnZaeneXPe19qSp9+tI8KH9O2L1VFRuYvNsL5I0oYF6/ykm5Ayw8gKwSDvhKCa2w
b01IlnDyuhdALjnDapMd6nY6nFZi+Lj+Ktjcv2VDk4Hqo/kPIvQ6N6P9jWc8YAks
n379Of2EZ2FNxnsI1USqDOXajASYULW3nnRGikvExNK7jPyXiueRjeFMZIaeSwEw
0X5LwMzrE60Emof6FF3O0aTxTikQFRrK1vEKnfJNJI7zke5/TTazsJHPYgShFaVC
MMLy+9ChCJ87oRYL2zKnqVH31gM15Wql6/BcnqXviDza+TzfFAeAbF+NWjB4rLqT
FgH23jEDw2vtaAkTk0g0E3PwBL2ObfBLwlN4CWzorbXzWVWZlWf671BrnwYHQWKH
42NuFD7Pfxp4ju+2wQjDgXhvSaGXdT98Dzr4j6aM8spJjpEg8/TAmC4d+3NmL63R
pVZ5zo5d0RXWwwLzdK68vMb/O4RbNXWRZHAH5EwTrux/lhAEOP05DdF4RHANq8n3
zCv05BToxA7sGkdmfBoY
=Oi2I
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to