Bug 12888 - pngtopnm is misssing in the cauldron netpbm
Summary: pngtopnm is misssing in the cauldron netpbm
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-27 02:37 CET by Thomas Spuhler
Modified: 2014-03-06 02:41 CET (History)
1 user (show)

See Also:
Source RPM: netpbm
CVE:
Status comment:


Attachments

Description Thomas Spuhler 2014-02-27 02:37:44 CET
Description of problem:
pngtopnm is misssing in the cauldron netpbm
The should be an alias
The manual says:

DESCRIPTION
       This program is part of Netpbm(1)

       pngtopnm was obsoleted by pngtopam(1) , introduced with Netpbm 10.44 (September 2008).  pngtopam is backward compatible
       with pngtopnm, plus adds many additional functions, including the ability to produce a PAM image that includes an alpha
       (transparency) channel.

       Starting in Release 10.48, pngtopnm is just an alias for pngtopam.

       pngtopnm remained in the Netpbm package through Release 10.47 because it may have fewer bugs  than  pngtopam  in  those
       releases,  and  may be faster in some environments.  But pngtopnm's incompatibility with the most current PNG libraries
       makes it impractical to maintain along with pngtopam now.

This miss makes programs such as lilypond not to build.

Reproducible: 

Steps to Reproduce:
Comment 1 David Walser 2014-02-27 13:57:41 CET
netpbm hasn't been updated in 2 years, so there's no recent change in it that should have broken lilypond building.  The netpbm package is unmaintained, so you should feel free to try to update it :o)
Comment 2 David Walser 2014-02-27 14:12:30 CET
Unless tv's attempt to port it to libpng16 causes the pngtopnm binary to not be produced.

CC: (none) => thierry.vignaud

Comment 3 Thomas Spuhler 2014-02-27 16:29:56 CET
(In reply to David Walser from comment #2)
> Unless tv's attempt to port it to libpng16 causes the pngtopnm binary to not
> be produced.

OK, this may cause other packages not to build anymore.
Need to look at Netpbm
Comment 4 Thomas Spuhler 2014-03-05 23:24:34 CET
(In reply to David Walser from comment #2)
> Unless tv's attempt to port it to libpng16 causes the pngtopnm binary to not
> be produced.

Why not making a symlink to pngtopam since this replaces pngtopnm?

BTW, Fedora has ver. 10.61.2 in the repos. Is there a problem to upgrade?
Comment 5 David Walser 2014-03-06 02:32:35 CET
(In reply to Thomas Spuhler from comment #4)
> Why not making a symlink to pngtopam since this replaces pngtopnm?

I have no idea.  If it's a valid drop-in replacement, I guess you can.

> BTW, Fedora has ver. 10.61.2 in the repos. Is there a problem to upgrade?

Not a problem, it's just that nobody has taken an interest in this package in a long time.  I think the only times it was updated were during the Mageia 2 development cycle.  tv updated it a few times early on, Funda updated it once, and I updated it once shortly before Mageia 2 release IIRC, and nobody's updated it since.  My update of it was trivial as I was just syncing it with what was in Mandriva Cooker at the time.  It's a rather complicated package, so it appears to be non-trivial to update, but please don't hesistate to take a crack at it.
Comment 6 Thomas Spuhler 2014-03-06 02:41:07 CET
(In reply to David Walser from comment #5)
> (In reply to Thomas Spuhler from comment #4)
> > Why not making a symlink to pngtopam since this replaces pngtopnm?
> 
> I have no idea.  If it's a valid drop-in replacement, I guess you can.
not needed. Did it automagically after pngtopam built with libpng16
I am going to close this as resolved
> 
> > BTW, Fedora has ver. 10.61.2 in the repos. Is there a problem to upgrade?
> 
> Not a problem, it's just that nobody has taken an interest in this package
> in a long time.  I think the only times it was updated were during the
> Mageia 2 development cycle.  tv updated it a few times early on, Funda
> updated it once, and I updated it once shortly before Mageia 2 release IIRC,
> and nobody's updated it since.  My update of it was trivial as I was just
> syncing it with what was in Mandriva Cooker at the time.  It's a rather
> complicated package, so it appears to be non-trivial to update, but please
> don't hesistate to take a crack at it.
I will do it soon

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.