Skip Menu |
 

This queue is for tickets about the Module-Signature CPAN distribution.

Report information
The Basics
Id: 33109
Status: open
Priority: 0/
Queue: Module-Signature

People
Owner: Nobody in particular
Requestors: grousse [...] cpan.org
Cc:
AdminCc:

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



Subject: Troubles with rpm packaging
Download (untitled) / with headers
text/plain 797b
If automatic debug symbol extraction is activated, rpm automatically creates two files in source directory when building a package: debugfiles.list and debugsources.list. In the case of noarch packages, those files are absolutly useless, and empty, but they still exist. As a consequence, all perl module tests based on Module::Signature fail, with following error message: Not in MANIFEST: debugfiles.list Not in MANIFEST: debugsources.list The only current exception mechanism for Module::Signature is the use of MANIFEST.SKIP. However, modificating this file for adding new exceptions also cause signature test to fail, as MANIFEST.SKIP signature is modified. So, what would be useful would be some way to dynamically add exceptions to Module::Signature, through env variables for instance.
How about you simple generate those files somewhere else?
From: paul [...] city-fan.org
Download (untitled) / with headers
text/plain 1.2k
On Mon Feb 11 03:57:14 2008, GROUSSE wrote: Show quoted text
> If automatic debug symbol extraction is activated, rpm automatically > creates two files in source directory when building a package: > debugfiles.list and debugsources.list. In the case of noarch packages, > those files are absolutly useless, and empty, but they still exist. > As a consequence, all perl module tests based on Module::Signature fail, > with following error message: > Not in MANIFEST: debugfiles.list > Not in MANIFEST: debugsources.list > > The only current exception mechanism for Module::Signature is the use of > MANIFEST.SKIP. However, modificating this file for adding new exceptions > also cause signature test to fail, as MANIFEST.SKIP signature is modified. > > So, what would be useful would be some way to dynamically add exceptions > to Module::Signature, through env variables for instance.
It's easy enough to work around this problem by creating a subdirectory and unpacking the module tarball into that, so that debug data gets created in a directory above where MANIFEST is associated with and hence doesn't cause a problem. For example, here's my RPM spec for Module::Signature itself: http://cvs.fedoraproject.org/viewvc/rpms/perl-Module-Signature/EL-6/perl-Module-Signature.spec?revision=1.14&view=markup
Subject: Re: [rt.cpan.org #33109] Troubles with rpm packaging
Date: Tue, 11 May 2010 13:03:36 +0200
To: "paul [...] city-fan.org via RT" <bug-Module-Signature [...] rt.cpan.org>
From: Florian Ragwitz <rafl [...] debian.org>
Download (untitled) / with headers
text/plain 625b
On Tue, May 11, 2010 at 06:58:08AM -0400, paul@city-fan.org via RT wrote: Show quoted text
> It's easy enough to work around this problem by creating a subdirectory > and unpacking the module tarball into that, so that debug data gets > created in a directory above where MANIFEST is associated with and hence > doesn't cause a problem. For example, here's my RPM spec for > Module::Signature itself: > > http://cvs.fedoraproject.org/viewvc/rpms/perl-Module-Signature/EL-6/perl-Module-Signature.spec?revision=1.14&view=markup
So would you agree that this ticket could be rejected? -- BOFH excuse #352: The cables are not the same length.
Download signature.asc
application/pgp-signature 189b

Message body not shown because it is not plain text.



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.