Update to the Addon Packages naming guidelines for Python 3 Modules
by Michael Schwendt
Two issues with the Addon Packages naming guidlines for Python 3:
On May 27th, 2013, the following exception has been removed from the
naming guidelines for Python Module packages:
| There is an exception to this rule. If the upstream source has "py" (or
| "Py") in its name, you can use that name for the package. So, for
| example, pygtk is acceptable.
The Python3 Module package naming guidelines still refer to that exception:
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Addon_Packages_...
That part should be removed as not to cause confusion.
[...]
As a second matter, the examples at the bottom of that section mention
"pygtk2", which does not adhere to the current naming guidelines anymore.
What's the status there? Is this just a compromise because such older
packages won't be renamed? Or would it be better to replace that example
with one of the many python-py* packages? ( yum list python-py\* )
10 years, 6 months
packing a theme for fedora
by Rudra Banerjee
Hi,
I am trying to make a(nother) Dark version of Adwaita. I am trying to keep changes at minimal so that the gtk-2 packages look in harmony with gtk-3 packages, and not altering gtk-3 at all.
Now, I want to package it for fedora. The dilemma I am facing is that adwaita package as it is installed in fedora does not say anything about license (I mean there is no license file and none of the file contains the license in it).
Is that accepted? Since I have just edited gtk-2.0/* do I need to add any license file or license statement at the top of each file?
10 years, 6 months
svn build issue
by Martin Gansser
Hi,
hi I'm working on the packet guayadeque, when creating the rpm package
on Fedora 20 you get the following error message:
bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=853553
There is a problem during the fedora 19+ package building related to svn:
-- Found Subversion: /usr/bin/svn (found version "1.8.3")
CMake Error at /usr/share/cmake/Modules/FindSubversion.cmake:83 (message):
Command "/usr/bin/svn info /builddir/build/BUILD/guayadeque-svn1885" failed
with output:
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: The working copy at
'/builddir/build/BUILD/guayadeque-svn1885'
is too old (format 29) to work with client version '1.8.3 (r1516576)'
(expects format 31). You need to upgrade the working copy first.
You need to upgrade the working copy with a 'svn upgrade' command in the %prep section if you build the package in fedora >= 20, otherwise building fails.
I don't know if this issue can be fixed only inside the RPM building or can be done even outside.
have somebody a idea to resolve this problem ?
regards
Martin
10 years, 6 months
Zoneminder packagers - Self Introduction for sponsership
by Timothy Ward
Hi All,
A lot of work has been done upstream on Zoneminder package Version 1.26
to lower the work load on the present packagers as they have been
keeping this package alive in Fedora for quite a while now. The present
package ver 1.25 does have problems and most have been addressed upline
in the new version. As the present packagers have either not responded
or indicated that they have little time to do this, I wish to be
sponsered as a package maintainer to be able to help out with this
package and any others packages that require package maintenance.
I have tried to contact the present packagers for this package but the
emails are either not responded too or returned as incorrect address.
Cheers
10 years, 6 months
