Skip Menu |

This queue is for tickets about the PDF-Create CPAN distribution.

Report information
The Basics
Id: 45965
Status: resolved
Priority: 0/
Queue: PDF-Create

People
Owner: MARKUSB [...] cpan.org
Requestors: david [...] davidfavor.com
SREZIC [...] cpan.org
Cc:
AdminCc:

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



Subject: PDF::Create 1.03 VERSION munged & fix for it
Date: Tue, 24 Mar 2009 20:02:49 -0500
To: bug-PDF-Create [...] rt.cpan.org
From: David Favor <david [...] davidfavor.com>
PDF::Create 1.02 contains PDF::Image:GIF 1.02 PDF::Create 1.03 contains PDF::Image::GIF 1.00 So the most recent version of PDF::Create downlevels PDF::Image::GIF when it's installed, causing a circular upgrade nightmare in CPANPLUS. Please release PDF::Create 1.04 and bump PDF::Image::GIF to 1.04 too or something above 1.02 and this should fix itself. -- Love feeling your best ever, all day, every day? Click http://RadicalHealth.com/join for the easy way.
Subject: Version of PDF::Create::Page problematic
The $VERSION of PDF::Create::Page in the current distribution is 1.00. But the version of the last distribution was 1.02. So if I use the "upgrade" command in CPAN, alternately the old and the new distribution would be installed. This can easily be fixed by providing a new distribution with $PDF::Create::Page::VERSION set to at least 1.03. Regards, Slaven
On Mon May 11 12:37:51 2009, SREZIC wrote: Show quoted text
> The $VERSION of PDF::Create::Page in the current distribution is 1.00. > But the version of the last distribution was 1.02. So if I use the > "upgrade" command in CPAN, alternately the old and the new
distribution Show quoted text
> would be installed. > > This can easily be fixed by providing a new distribution with > $PDF::Create::Page::VERSION set to at least 1.03. > > Regards, > Slaven
The current namespace and versioning is a mess. I'm working on flattening the namespace, so I can work with a single version number. For now I'll have to make sure I don't forget to patch up the version numbers for each release.
Working on it, see also Bug #45965
Fixed in v1.05