error running fedora-packager-setup
by Léon Keijser
Hi,
After reinstalling F12 (fresh install, no upgrade) i tried to run
'fedora-packager-setup' and got this error:
$ fedora-packager-setup
Setting up Fedora packager environment
Traceback (most recent call last):
File "/usr/bin/fedora-packager-setup", line 140, in <module>
main()
File "/usr/bin/fedora-packager-setup", line 114, in main
if certificate_expired():
NameError: global name 'certificate_expired' is not defined
I'm not sure why it's throwing this error.
Léon
13 years, 6 months
Update for the GCJ section of Java Guidelines
by Aleksandar Kurtakov
GCJ AOT bits are mandatory parts of any Java packages according to current
guidelines. There are at least 2 reasons to not require them:
1. GCJ has stagnated at Java 1.5 level and gcj bits require having GCJ
installed even in cases when the package requires Java >= 1.6. Resulting in an
installed but unusable for the given package JVM
2. GCJ AOT bits makes every package an arch specific one (when they are noarch
in general)- resulting in slower package build, slower install/uninstall,
bigger packages and etc.
There are other benefits like - much more readable RPM spec files, using less
resources on Fedora infrastructure. But the main benefit is for the users - we
do not have to force them to install something they will never use. E.g
installing eclipse-jdt drags gcj in but upstream is not supporting it and
there is even a warning added to indicate that you're running gcj and it may
not work as expected but gcj is still installed because of eclipse
dependencies that have the gcj bits.
This mail is by no means saying that there is no value in gcj. But gcj has a
different usecases and shouldn't be thrown at every user. GCJGuidelines should
be changed in such a way that they should indicate that you may add GCJ AOT
bits to your package but this should not result in mandatory installation of
GCJ (e.g. by making the gcj aot bits a separate subpackage auto-generated like
the debug packages, but this is up to the people interested in gcj to solve).
We simply don't have to force users to install a non-default and less feature
full JVM in order to use our packages with another JVM.
Regards,
Alexander Kurtakov
13 years, 7 months
[fedora-packaging] somebody who was sponsor , would u please help to review my package?
by Devil Wang
*HI all,*
*
*
*I have handle a package in Bugzilla as followed.*
*
Bug 580830
*
*https://bugzilla.redhat.com/show_bug.cgi?id=580830*
*Would some sponsor help to review my package.*
*
*
*I have modified for times , and i think , it might be in the proper status.
*
*
*
*Your help will be appreciated.*
--
Thanks & Regards
Linux Developer : Devil Wang
13 years, 7 months
What is "definitive" Fedora Java packaging guide
by Edmon Begoli
Could you please point me to "definitive" guide for creating Java RPMs.
I saw guides on using JPackage and some pretty good guides by
individuals outside of Fedora project,
but I would like to follow what is considered an official Fedora java
packaging guide or at least what is endorsed
by this group.
Thank you in advance,
Edmon
13 years, 7 months
Failed Dependencies while installing
by MGandra＠diskeeper.com
Hi
I have installed the complete SDK on the machine and trying to install our
product which uses the libraries. When I install our product rpm it says
error: Failed dependencies:
libvixAllProducts.so is needed
If I use -nodeps and install it will install and runs correctly.
What should I do to make sure that I don't get this error?
Madhukar
13 years, 7 months
user input while installing an RPM
by MGandra＠diskeeper.com
Hi
I have an RPM package which will install and I need to get the Username and
Password for root user and write it to a config file.
I can have another script file through which I can get user input and
install RPM and then write to the config file, but I want to get user input
and install rpm from one file.
I need one file that I can distribute it and does above things. How to do
that?
Madhukar
13 years, 7 months
Volonteering to own orphaned Java packages JLex and JDom
by Edmon Begoli
Hi,
Packages JLex and JDom have been recently orphaned and I am volunteering to
be a new owner of these.
I am a new as a packager, so I would need to be approved and sponsored
as a packager
and to be a new owner of these for Fedora 14+.
I am already Fedora contributor, and I am member of other projects and
CVS groups,
but I do not have CVS packaging privileges yet.
I am experienced software developer with 14 years in Java and 15 years
on RedHat Linux.
I am a member of the research staff at Oak Ridge National Lab
(http://computing.ornl.gov),
and PhD student in Computer Science at UTK (http://utk.edu).
My FAS account is: ebegoli I have account on fedorapeople and my keys
are up to date.
Please approve me, if that is appropriate, as the new owner of JLex
and JDom packages.
Thank you,
Edmon
13 years, 7 months
How much time wait to finish a review?
by Taylon
Hello guys,
I did a review request[1] for my first package some time ago, Michael
Schwendt started the review (thanks Michael), but he didn't finish that.
This package is under review for over two months, I would like to
package others softwares, but while my first package isn't revised I
cannot do this.
It's normal?
How much time until the package be revised?
I really should wait this revision to package another software?
1 - https://bugzilla.redhat.com/show_bug.cgi?id=555018
--
Blog - http://www.focolivre.org
13 years, 7 months
