Bug 14923 - No pfstools in Mageia repositories
Summary: No pfstools in Mageia repositories
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: David GEIGER
QA Contact:
URL: http://pfstools.sourceforge.net/index...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-31 10:40 CET by Husi Susi
Modified: 2015-02-01 12:22 CET (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Husi Susi 2014-12-31 10:40:40 CET 
Hello Mageia Team,

it would be nice to have pfstools in your repositories.
It is very useful to have such a powerful tool like pfstool and it is free (GPL 2.1).

Best regards

HS



Reproducible: 

Steps to Reproduce:
David GEIGER 2015-01-27 15:12:09 CET

CC: (none) => geiger.david68210
Assignee: bugsquad => geiger.david68210

Comment 1 David GEIGER 2015-01-27 16:38:00 CET 
Hi Husi Susi,

pfstools is now imported and submitted on Cauldron.

http://svnweb.mageia.org/packages/cauldron/pfstools/

associated packages:
====================
x86_64:
lib64pfstools-devel-1.8.5-1.mga5.x86_64
lib64pfstools1.2_0-1.8.5-1.mga5.x86_64
pfstools-1.8.5-1.mga5.x86_64
pfstools-exr-1.8.5-1.mga5.x86_64
pfstools-gdal-1.8.5-1.mga5.x86_64
pfstools-glview-1.8.5-1.mga5.x86_64
pfstools-imgmagick-1.8.5-1.mga5.x86_64
pfstools-octave-1.8.5-1.mga5.x86_64
pfstools-qt-1.8.5-1.mga5.x86_64

i586:
libpfstools-devel-1.8.5-1.mga5.i586
libpfstools1.2_0-1.8.5-1.mga5.i586
pfstools-1.8.5-1.mga5.i586
pfstools-exr-1.8.5-1.mga5.i586
pfstools-gdal-1.8.5-1.mga5.i586
pfstools-glview-1.8.5-1.mga5.i586
pfstools-imgmagick-1.8.5-1.mga5.i586
pfstools-octave-1.8.5-1.mga5.i586
pfstools-qt-1.8.5-1.mga5.i586

Best regards daviddavid.
Comment 2 David GEIGER 2015-02-01 12:22:31 CET 
Closing of this bug as it is now imported.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.