Overview
Request History
fstrba created request
This package depends on gcj able to build java code into native elf binary. Gcj is going and with it this capacity.
factory-auto added pdftk as a reviewer
Submission for pdftk by someone who is not maintainer in the devel project (Publishing). Please review
factory-auto added repo-checker as a reviewer
Is this delete request safe?
factory-auto accepted review
ok
licensedigger accepted review
ok
dimstar_suse set openSUSE:Factory:Staging:H as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:H"
dimstar_suse accepted review
Picked openSUSE:Factory:Staging:H
repo-checker accepted review
Manual override
dimstar_suse accepted review
GCC6 is not longer maintainable, and pdftk without gcc6 is apparently a no-go
dimstar_suse accepted review
ready to accept
dimstar_suse approved review
ready to accept
dimstar_suse added factory-maintainers as a reviewer
Request accepted. Cleanup in progress - DO NOT REVOKE!
dimstar_suse accepted review
Virtually accepted delete pdftk
dimstar_suse approved review
Virtually accepted delete pdftk
dimstar_suse accepted request
Accept to openSUSE:Factory
is there another, older compatibility-required compiler that will still be in SLES15? then we could use that to build pdftk...
Actually, there is a way to build this in a project for openSUSE:Factory, but in SLE15, the gcc6 (last that has gcj) will not be.
but will there be an older one? For compatibility reasons? pdftk built without changes since gcc-4.x
No, no GCJ will be in SLE15. If it was otherwise, I would not bother to remove the gcj dependency in everything where it was humanly possible :( Pdftk is a special beast. OTOH, for the reasons of being able to bootstrap java myself, I have a repository Java:bootstrap that I will maintain buildable for quite a time, so it can live there and one can get it from there, but that is the most one can do at this point. The other solution would be to port those C++ files to Java and use pdftk as a pure Java application.
Let's just drop it. My "customers" can just use the package from Leap 42.3 for the next 20 years ;-)
I don't understand why there won't be a compatible version of gcc available at all. gcc just released updates to gcc 5 just the day before yesterday, let alone gcc6.
-quote-
News
GCC 5.5 released [2017-10-10]
GCC 7.2 released [2017-08-14]
GCC 6.4 released [2017-07-04]
-quote-