Skip Menu |
 

This queue is for tickets about the Config-IniFiles CPAN distribution.

Report information
The Basics
Id: 46549
Status: resolved
Priority: 0/
Queue: Config-IniFiles

People
Owner: Nobody in particular
Requestors: salvatore.bonaccorso [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



MIME-Version: 1.0
X-Spam-Status: No, hits=0.0 required=8.0 tests=DK_SIGNED,SPF_PASS
Content-Disposition: inline
X-Virus-Checked: Checked by ClamAV on 16.mx.develooper.com
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bCsyhTFzCvuiizWE"
Message-ID: <20090531113327.GA20990 [...] faerie>
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by diesel.bestpractical.com (Postfix) with SMTP id 116304D8178 for <bug-Config-IniFiles [...] rt.cpan.org>; Sun, 31 May 2009 07:33:40 -0400 (EDT)
Received: (qmail 28021 invoked by uid 103); 31 May 2009 11:33:38 -0000
Received: from x16.dev (10.0.100.26) by x1.dev with QMQP; 31 May 2009 11:33:38 -0000
Received: from mail-ew0-f164.google.com (HELO mail-ew0-f164.google.com) (209.85.219.164) by 16.mx.develooper.com (qpsmtpd/0.80) with ESMTP; Sun, 31 May 2009 04:33:31 -0700
Received: by ewy8 with SMTP id 8so4217218ewy.45 for <bug-Config-IniFiles [...] rt.cpan.org>; Sun, 31 May 2009 04:33:27 -0700 (PDT)
Received: by 10.211.168.5 with SMTP id v5mr2571404ebo.88.1243769607531; Sun, 31 May 2009 04:33:27 -0700 (PDT)
Received: from faerie (77-58-207-27.dclient.hispeed.ch [77.58.207.27]) by mx.google.com with ESMTPS id 28sm5687462eye.46.2009.05.31.04.33.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 31 May 2009 04:33:27 -0700 (PDT)
Received: from salvi by faerie with local (Exim 4.69) (envelope-from <salvatore.bonaccorso [...] gmail.com>) id 1MAjI7-0005Sz-3q for bug-Config-IniFiles [...] rt.cpan.org; Sun, 31 May 2009 13:33:27 +0200
Delivered-To: cpan-bug+Config-IniFiles [...] diesel.bestpractical.com
User-Agent: Mutt/1.5.19 (2009-01-05)
Subject: [Config::IniFiles] =cut found outside a pod block
Return-Path: <salvatore.bonaccorso [...] gmail.com>
Domainkey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; b=C4vdS9NcNjGvOKSAHzmxtTAeKS4LVt8gSRtldG8HkgD1vOwO2YE20S/teIFVGFVQEs PXexLJHe77xvDvGdBjE6ICFtV7NGqc+5EbTcCLlWrhFtsBYE4ulO3v9itC3YD4axhFjJ lx2Eqb+f7EpvdoyOQUl5y7Q3c4FxrMegxkApI=
X-Original-To: bug-Config-IniFiles [...] rt.cpan.org
X-Spam-Check-BY: 16.mx.develooper.com
Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:subject :message-id:mime-version:content-type:content-disposition:user-agent; bh=/tkglNBJXT6V7vSBIQPWsIxXN1EHlCQD9a7Wh1mlwvc=; b=RsgIWj3Xjk7sDxWx8lKiySo+HhOBpgvw0fKfgz3mEmVnPtsyRgChQ+oVXoii3MmF7Q mJr/9UKKwSzgvblW07eVzLVMt/FYi8D/5xDYdplChitPGLaREUQyKHQBPJCC8D9U7YgR VpBCcPPVburn6gqHqjZC+zIoi/786f/iE94xw=
Date: Sun, 31 May 2009 13:33:27 +0200
X-Spam-Level: *
To: bug-Config-IniFiles [...] rt.cpan.org
From: Salvatore Bonaccorso <salvatore.bonaccorso [...] gmail.com>
Content-Length: 0
Content-Description: Digital signature
content-type: application/pgp-signature; name="signature.asc"
Content-Disposition: inline
Content-Length: 835
Download signature.asc
application/pgp-signature 835b

Message body not shown because it is not plain text.

Content-Type: multipart/mixed; boundary="liOOAslEiF7prFVr"
Content-Disposition: inline
Content-Length: 0
content-type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: us-ascii
Content-Length: 364
Download (untitled) / with headers
text/plain 364b
Hi Building the new upstream release of Config::IniFiles we noticed that there is a error when creating the manpage via pod2man [1]. [1] http://lists.debian.org/debian-perl/2009/05/msg00154.html There is a =cut closing a nonexistend POD block? If this is correct the following patch would fix that. Could you integrate this upstream? Kind regards Salvatore
Content-Type: text/x-diff; charset=us-ascii
content-disposition: attachment; filename="1001-fix-POD-Config-IniFiles.patch"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: us-ascii
Content-Length: 598

Message body is not shown because sender requested not to inline it.

MIME-Version: 1.0
In-Reply-To: <20090531113327.GA20990 [...] faerie>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <20090531113327.GA20990 [...] faerie>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-17651-1243771229-249.46549-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 736
Download (untitled) / with headers
text/plain 736b
On Sun May 31 07:35:09 2009, salvatore.bonaccorso@gmail.com wrote: Show quoted text
> Hi > > Building the new upstream release of Config::IniFiles we noticed that > there is a error when creating the manpage via pod2man [1]. > > [1] http://lists.debian.org/debian-perl/2009/05/msg00154.html > > There is a =cut closing a nonexistend POD block? If this is correct > the following patch would fix that. Could you integrate this upstream? > > Kind regards > Salvatore
Hi! This was fixed in Config-IniFiles-2.50 (coming to a CPAN mirror near you). I noticed that the distribution did not have t/pod.t and t/pod-coverage.t so I added them and fixed the problems they reported - among them this one. Thanks for the report. Regards, -- Shlomi Fish
MIME-Version: 1.0
In-Reply-To: <20090531113327.GA20990 [...] faerie>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <20090531113327.GA20990 [...] faerie>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-15493-1243771262-383.46549-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 71
Resolving per the upload of Config-IniFiles-2.50 that fixes this issue.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.