Bug 1420 - pdfedit, an editor for manipulating PDF documents
Summary: pdfedit, an editor for manipulating PDF documents
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Low enhancement
Target Milestone: ---
Assignee: Oliver Burger
QA Contact:
URL:
Whiteboard:
Keywords:
: 3152 23091 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-05-25 09:45 CEST by Manuel Hiebel
Modified: 2018-05-28 21:36 CEST (History)
5 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Manuel Hiebel 2011-05-25 09:45:41 CEST
Please add the package: pdfedit - Editor for manipulating PDF documents -

http://sourceforge.net/projects/pdfedit

Thanks.
Manuel Hiebel 2011-06-05 20:35:40 CEST

Summary: Add package: pdfedit => pdfedit, an editor for manipulating PDF documents
Severity: normal => enhancement

Comment 1 Oliver Burger 2011-07-15 21:55:31 CEST
Since pdfedit is depending on Qt3 it can't be built for Mageia

CC: (none) => oliver.bgr

Comment 2 Manuel Hiebel 2011-07-15 22:01:22 CEST
ahh, indeed :(

do you know a similar apps ?
Comment 3 Oliver Burger 2011-07-15 22:07:19 CEST
No, but I saw on the pdfedit project page, that a KDE4 version is being worked on. I don't know, how far that work is, but if you are lucky...
Comment 4 Oliver Burger 2011-07-17 23:41:14 CEST
Good news, according to the upstream developers, the first stable release of the qt4 port will be available in two to three weeks.

I will stay on it.

Status: NEW => ASSIGNED
Assignee: bugsquad => oliver.bgr

Comment 5 Marja Van Waes 2011-10-14 20:28:04 CEST
(In reply to comment #4)
> Good news, according to the upstream developers, the first stable release of
> the qt4 port will be available in two to three weeks.
> 
> I will stay on it.

Anny news?

CC: (none) => marja11

Comment 6 Oliver Burger 2011-10-14 20:58:56 CEST
No, I'm following the upstream mls and there isn't even an alpha version available :/
Comment 7 Marja Van Waes 2011-10-14 21:01:22 CEST
@ Oliver

:(

But thanks for replying :D
Comment 8 Manuel Hiebel 2011-10-23 20:13:00 CEST
*** Bug 3152 has been marked as a duplicate of this bug. ***

CC: (none) => globetrotterdk

Comment 9 Oliver Burger 2012-01-19 17:53:40 CET
no movement upstream

Priority: Normal => Low

Comment 10 Oliver Burger 2012-03-10 20:25:31 CET
Closing as upstream is not providing any updates on the qt4 port.
When upstream moves again, it can be reopened.

Status: ASSIGNED => RESOLVED
Resolution: (none) => WONTFIX

Comment 11 George Oprisko 2013-05-05 20:32:06 CEST
I went to 
http://pkgs.org

on the web and found the following packages:
lib64-png12_0-1.2.49-1.mga2.x86_64.rpm
lib64qt3-3.3.8b-30.mga2.x86_64.rpm
lib64tlib5-5.1.2-12.mga2.x86_64.rpm
qt3-common-3.3.8b-30.mga2.x86_64.rpm
t1lib-config-5.1.2-12.mga2.x86_64.rpm
pdfedit-0.4.5-1.el6.nux.x86_64.rpm

I did this because the default repositories delivered broken packages.

Specifically virtually all the lib64 packages were broken, and
qt3 was broken.

I istalled the above packages using urpmi, and pdfedit is working.

Btw, I have source for pdfedit-0.4.5-1, but hoped to find a suitably built
package, which I did.   The one I used was built for CentOs, Rhel6.

INDY

CC: (none) => goprisko
Resolution: WONTFIX => FIXED

Comment 12 Marja Van Waes 2018-05-28 21:34:14 CEST
@ George

It was nice that you added your comment about how you managed to get a working pdfedit, but you shouldn't have changed the resolution of this report from wontfix to fixed, because a package request is only fixed if the requested package is available from the official Mageia repositories ;-)



(In reply to Oliver Burger from comment #10)
> Closing as upstream is not providing any updates on the qt4 port.
> When upstream moves again, it can be reopened.

Nothing changed upstream, the project is dead and we'd probably need a qt5 port now.

Changing resolution back to WONTFIX.

Resolution: FIXED => WONTFIX

Comment 13 Marja Van Waes 2018-05-28 21:36:55 CEST
*** Bug 23091 has been marked as a duplicate of this bug. ***

CC: (none) => hamnisdude


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