What software is missing in the Fedora repository?

[Rahul Sundaram]

Hi,

I am doing a quick survey for software that you use on a regular basis
that is not available via the Fedora repository. Software that you
suggest should be free and open source, free of patent and other legal
issues.

Tell me the home page of the software and give me a brief description on
what it does.  Bonus points if you can see in Google for "software-name
fedora package review" to figure it if it is already in the Fedora
package review queue. If you know of RPM packages in other distributions
for the software your are suggesting, that information is useful as well.

Rahul

[Gireesh Sreekantan]

I would love to see menumaker [1]. It hasn't been updated since Dec
13, 2005 but that version compiles and runs fine on F10. Not a deal
breaker but if you use fluxbox, icewm or openbox, it can save you
hours.

[1] http://sourceforge.net/projects/menumaker

[Rahul Sundaram]

On 05/08/2009 05:21 AM, Gireesh wrote:
> I would love to see menumaker [1]. It hasn't been updated since Dec
> 13, 2005 but that version compiles and runs fine on F10. Not a deal
> breaker but if you use fluxbox, icewm or openbox, it can save you
> hours.
>
> [1] http://sourceforge.net/projects/menumaker

To implement the second part of my sneaky plan, do you want to be a
package maintainer?  :-)  If you have interest, refer to

https://fedoraproject.org/wiki/Join_the_package_collection_maintainers

Feel free to ask questions, if you have any doubts.

Rahul

[Ankur Sinha]

On Fri, 2009-05-08 at 05:29 +0530, Rahul Sundaram wrote:
> On 05/08/2009 05:21 AM, Gireesh wrote:
> > I would love to see menumaker [1]. It hasn't been updated since Dec
> > 13, 2005 but that version compiles and runs fine on F10. Not a deal
> > breaker but if you use fluxbox, icewm or openbox, it can save you
> > hours.
> >
> > [1] http://sourceforge.net/projects/menumaker
>
> To implement the second part of my sneaky plan, do you want to be a
> package maintainer?  :-)  If you have interest, refer to
>
> https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
>
> Feel free to ask questions, if you have any doubts.
>
> Rahul
>
> Fedora-india mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-india

hi,

lol :D That was a really classy plan..

Anyway, I think I have learnt font packaging now (understood the spec
file etc.) and would like to "upgrade". Can you please suggest a really
really really simple package I could start with??

(I did go through the wishlist, Found all of them daunting :| )

regards,

Ankur

[Rahul Sundaram]

On 05/08/2009 08:10 AM, Ankur Sinha wrote:
> Anyway, I think I have learnt font packaging now (understood the spec
> file etc.) and would like to "upgrade". Can you please suggest a really
> really really simple package I could start with??
>
> (I did go through the wishlist, Found all of them daunting :| )

Software is always going to involve more work on packaging compared to
fonts. However, look at

http://sourceforge.net/projects/pdfchain

You can re-use

http://leigh123linux.fedorapeople.org/srpm/pdfchain-0.99-1.fc10.src.rpm

http://sourceforge.net/projects/pvqt/

A spec and rpm can be found at

http://hanzlici.cz/packages/fedora/panini/

There might be a few other simple ones at

http://forums.fedoraforum.org/showthread.php?p=1211201#post1211201

https://www.redhat.com/archives/fedora-list/2009-May/msg00440.html

courier-imap and courier-authlib was asked a few times. They are fairly
involved but you can be sure you will get many users.

A dead review of courier-authlib is at

https://bugzilla.redhat.com/show_bug.cgi?id=208064

Feel free to reuse the spec file.

Someone from Pune LUG suggested

http://www.novell.com/products/linuxpackages/enterpriseserver/i386/kinternet...

Seems to be a KDE applet that shows live transfer rates and graphs. You
should be able to find a SRPM somewhere. If you are a KDE user, take a
look at this and talk to the Fedora KDE SIG.

Rahul

[Ankur Sinha]

On Fri, 2009-05-08 at 16:01 +0530, Rahul Sundaram wrote:
> http://sourceforge.net/projects/pvqt/
>
> A spec and rpm can be found at
>
> http://hanzlici.cz/packages/fedora/panini/

hi,

Giving this one a try..

There is this macro that I don't know enough about.. I'm sure I'll have
more doubts as I package this, but this one's the only doubt currently.

In the spec file http://hanzlici.cz/packages/fedora/panini/panini.spec ,
the build section is like this :

%build
# --without debug hack:
CFLAGS="${CFLAGS:-%optflags}" ; export CFLAGS
%{?_without_debug:%define debug_package %{nil}}
%{?_without_debug:export RPM_OPT_FLAGS="${RPM_OPT_FLAGS//-g/}"}
%{?_without_debug:export CFLAGS="${CFLAGS//-g/}"}

This is what I got from the wiki on macros..
http://fedoraproject.org/wiki/Packaging/RPMMacros

%{_global_cflags}     -O2 -g -pipe
%{_optflags}          %{__global_cflags} -m32 -march=i386v
-mtune=pentium4

Didn't help much.. I'll go through the gcc docs for explanations on the
flags..

What I want to know is why these are needed? The build file in the
source specifies only "qmake-qt4 panini.pro" to build it from source..
Nothing about gcc flags there.. Can I leave these out?

A little insight to the "?_without_debug" thing would also be helpful.

regards,

Ankur

PS : Do i need to start a new topic for these queries?

[Rahul Sundaram]

On 05/09/2009 12:48 AM, Ankur Sinha wrote:
> There is this macro that I don't know enough about.. I'm sure I'll have
> more doubts as I package this, but this one's the only doubt currently.
>
> In the spec file http://hanzlici.cz/packages/fedora/panini/panini.spec ,
> the build section is like this :
>
> %build
> # --without debug hack:
> CFLAGS="${CFLAGS:-%optflags}" ; export CFLAGS

This one is a explicit override of the compiler flags for the package to
pick up the right compiler options. Not sure that is actually necessary
in this case. Refer to

http://fedoraproject.org/wiki/Packaging/cmake
> %{?_without_debug:%define debug_package %{nil}}
> %{?_without_debug:export RPM_OPT_FLAGS="${RPM_OPT_FLAGS//-g/}"}
> %{?_without_debug:export CFLAGS="${CFLAGS//-g/}"}

Remove these and check if the debuginfo packages are generated
correctly. If they are, there is no need for this.

desktop-file-install should have not use a vendor option. So remove that
as well.
> PS : Do i need to start a new topic for these queries?

Sure.

Rahul

[Ankur Sinha]

On Sat, 2009-05-09 at 06:15 +0530, Rahul Sundaram wrote:
> On 05/09/2009 12:48 AM, Ankur Sinha wrote:
> > There is this macro that I don't know enough about.. I'm sure I'll have
> > more doubts as I package this, but this one's the only doubt currently.
> >
> > In the spec file http://hanzlici.cz/packages/fedora/panini/panini.spec ,
> > the build section is like this :
> >
> > %build
> > # --without debug hack:
> > CFLAGS="${CFLAGS:-%optflags}" ; export CFLAGS
>
> This one is a explicit override of the compiler flags for the package to
> pick up the right compiler options. Not sure that is actually necessary
> in this case. Refer to
>
> http://fedoraproject.org/wiki/Packaging/cmake
> > %{?_without_debug:%define debug_package %{nil}}
> > %{?_without_debug:export RPM_OPT_FLAGS="${RPM_OPT_FLAGS//-g/}"}
> > %{?_without_debug:export CFLAGS="${CFLAGS//-g/}"}
>
> Remove these and check if the debuginfo packages are generated
> correctly. If they are, there is no need for this.
>
> desktop-file-install should have not use a vendor option. So remove that
> as well.
> > PS : Do i need to start a new topic for these queries?
>
> Sure.
>
> Rahul
>
> Fedora-india mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-india

hi,

I packaged it..Mock built it successfully too..It did give a few
warnings though.. In the src files.. Stuff like "unused parameters"
etc..

Here are all the files.. I haven't put it up for review yet.. I thought
I'd let you folks have a look at it first..

http://ankursinha.fedorapeople.org/panini/

Another query.. The source1 and source2 (the .desktop and .png files)
were not available in the source tar.. I used the ones at

http://hanzlici.cz/packages/fedora/panini/

If they weren't available what was I supposed to do? Am I supposed to
generate them??

regards,

Ankur

[Rahul Sundaram]

On 05/09/2009 11:56 PM, Ankur Sinha wrote:
> Here are all the files.. I haven't put it up for review yet.. I thought
> I'd let you folks have a look at it first..
>
> http://ankursinha.fedorapeople.org/panini/

[Not building it. Just a quick review]

Check if the license is GPLv3 or GPLv3+. If the source header has
something like (c) foo GPLv3 or later, then it is GPLv3+

Also don't rely on a single sf.net mirror, instead follow

http://fedoraproject.org/wiki/Packaging/SourceURL#Sourceforge.net

The end version number 0.62.83-1 should be in the end of the email address.

run rpmlint on the spec file, SRPM and binary RPM for checking

install the debuginfo RPM package and verify that it is not empty.

Run the program and check if it actually functioning.
> Another query.. The source1 and source2 (the .desktop and .png files)
> were not available in the source tar.. I used the ones at
>
> http://hanzlici.cz/packages/fedora/panini/
>
> If they weren't available what was I supposed to do? Am I supposed to
> generate them??

Yes and don't provide the path (unless it is the upstream project path)
at source1 and source2 since you can't rely on it but just the filename.
As long as you include them directly in the SRPM, it would be buildable.

Rahul

[Ankur Sinha]

On Sun, 2009-05-10 at 18:53 +0530, Rahul Sundaram wrote:
> Check if the license is GPLv3 or GPLv3+. If the source header has
> something like (c) foo GPLv3 or later, then it is GPLv3+

This is what the "usage" file states..

You can redistribute and/or modify it under the terms of the GNU General
Public License as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later version.

So I'm guessing the license is GPLv2+, the src zip has a copy of the
GPLv3 in it..
> Also don't rely on a single sf.net mirror, instead follow
>
> http://fedoraproject.org/wiki/Packaging/SourceURL#Sourceforge.net

Done..
> run rpmlint on the spec file, SRPM and binary RPM for checking

Done. No errors/warnings..

I'll install the debuginfo and the package to see if its working..

Thanks,

regards,

Ankur

[Rahul Sundaram]

On 05/10/2009 07:16 PM, Ankur Sinha wrote:
> On Sun, 2009-05-10 at 18:53 +0530, Rahul Sundaram wrote:
> > Check if the license is GPLv3 or GPLv3+. If the source header has
> > something like (c) foo GPLv3 or later, then it is GPLv3+
>
> This is what the "usage" file states..
>
> You can redistribute and/or modify it under the terms of the GNU General
> Public License as published by the Free Software Foundation; either
> version 2 of the License, or (at your option) any later version.
>
> So I'm guessing the license is GPLv2+, the src zip has a copy of the
> GPLv3 in it..

GPLv2+, yes.

Don't rely on the copy of the license. There is no difference between
GPLv2 or GPLv2+ within the license itself. What really matters is how
the license is applied to the source code.

Read the copyright headers in the individual source files (every single
one of them) and any explicit mentions of the license in the README or
website. If it is ambiguous or contradictory, communicate with the
upstream developers and explicitly verify and include a copy of that
communication (preferably a email) in the SRPM.

Rahul

[Ankur Sinha]

On Sun, 2009-05-10 at 19:25 +0530, Rahul Sundaram wrote:
> GPLv2+, yes.
>
> Don't rely on the copy of the license. There is no difference between
> GPLv2 or GPLv2+ within the license itself. What really matters is how
> the license is applied to the source code.
>
> Read the copyright headers in the individual source files (every
> single
> one of them) and any explicit mentions of the license in the README or
> website. If it is ambiguous or contradictory, communicate with the
> upstream developers and explicitly verify and include a copy of that
> communication (preferably a email) in the SRPM.

Okay.. I'll do that..

In the meantime..

[Ankur@Ankur twitter_tui]$ rpm -ql panini-debuginfo
/usr/lib/debug
/usr/lib/debug/.build-id
/usr/lib/debug/.build-id/df
/usr/lib/debug/.build-id/df/60e6e9dd27bbd736a6ef0f9a8a2aac80e9891b
/usr/lib/debug/.build-id/df/60e6e9dd27bbd736a6ef0f9a8a2aac80e9891b.debug
/usr/lib/debug/usr
/usr/lib/debug/usr/bin
/usr/lib/debug/usr/bin/panini.debug
/usr/src/debug/panini-0.62
/usr/src/debug/panini-0.62/build
/usr/src/debug/panini-0.62/build/moc_About.cpp
/usr/src/debug/panini-0.62/build/moc_GLwindow.cpp
/usr/src/debug/panini-0.62/build/moc_MainWindow.cpp
/usr/src/debug/panini-0.62/build/moc_TurnDialog.cpp
/usr/src/debug/panini-0.62/build/moc_picTypeDialog.cpp
/usr/src/debug/panini-0.62/build/moc_pvQtMouseModes.cpp
/usr/src/debug/panini-0.62/build/moc_pvQtPic.cpp
/usr/src/debug/panini-0.62/build/moc_pvQtView.cpp
/usr/src/debug/panini-0.62/build/pvQtVersion.h
/usr/src/debug/panini-0.62/build/ui_About.h
/usr/src/debug/panini-0.62/build/ui_ShowText.h
/usr/src/debug/panini-0.62/build/ui_TurnDialog.h
/usr/src/debug/panini-0.62/build/ui_mainwindow.h
/usr/src/debug/panini-0.62/build/ui_picTypeDialog.h
/usr/src/debug/panini-0.62/release
/usr/src/debug/panini-0.62/release/qrc_PaniniIcon.cpp
/usr/src/debug/panini-0.62/src
/usr/src/debug/panini-0.62/src/About.cpp
/usr/src/debug/panini-0.62/src/About.h
/usr/src/debug/panini-0.62/src/GLwindow.cpp
/usr/src/debug/panini-0.62/src/GLwindow.h
/usr/src/debug/panini-0.62/src/MainWindow.cpp
/usr/src/debug/panini-0.62/src/MainWindow.h
/usr/src/debug/panini-0.62/src/TurnDialog.cpp
/usr/src/debug/panini-0.62/src/TurnDialog.h
/usr/src/debug/panini-0.62/src/main.cpp
/usr/src/debug/panini-0.62/src/panocylinder.cpp
/usr/src/debug/panini-0.62/src/panocylinder.h
/usr/src/debug/panini-0.62/src/panosphere.cpp
/usr/src/debug/panini-0.62/src/panosphere.h
/usr/src/debug/panini-0.62/src/panosurface.cpp
/usr/src/debug/panini-0.62/src/panosurface.h
/usr/src/debug/panini-0.62/src/picTypeDialog.cpp
/usr/src/debug/panini-0.62/src/picTypeDialog.h
/usr/src/debug/panini-0.62/src/pictureTypes.cpp
/usr/src/debug/panini-0.62/src/pvQtMouseModes.h
/usr/src/debug/panini-0.62/src/pvQtPic.cpp
/usr/src/debug/panini-0.62/src/pvQtPic.h
/usr/src/debug/panini-0.62/src/pvQtView.cpp
/usr/src/debug/panini-0.62/src/pvQtView.h
/usr/src/debug/panini-0.62/src/pvQt_QTVR.cpp
/usr/src/debug/panini-0.62/src/pvQt_QTVR.h
[Ankur@Ankur twitter_tui]$

so it's not empty..

The app isn't running though.. This is what I got..

[Ankur@Ankur twitter_tui]$ panini
QGtkStyle cannot be used together with the GTK_Qt engine.
Locking assertion failure.  Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0x3f9767]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0x3f990e]
#2 /usr/lib/libX11.so.6 [0x2400e9]
#3 /usr/lib/libX11.so.6(XCreateSimpleWindow+0x26) [0x215db6]
#4 /usr/lib/libQtGui.so.4 [0x72c3c85]
#5 /usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate10create_sysEmbb+0x1828)
[0x72c25d8]
#6 /usr/lib/libQtGui.so.4(_ZN7QWidget6createEmbb+0x16c) [0x7284c1c]
#7 /usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate11createWinIdEm+0x1e3)
[0x727ff43]
#8 /usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate21setWindowTitle_helperERK7QString+0x9b) [0x72845bb]
#9 /usr/lib/libQtGui.so.4(_ZN7QWidget14setWindowTitleERK7QString+0xa2)
[0x7284a12]
#10 /usr/lib/libQtGui.so.4(_ZN11QMessageBox14setWindowTitleERK7QString
+0x24) [0x7766554]
#11 /usr/lib/libQtGui.so.4 [0x7768237]
#12 /usr/lib/libQtGui.so.4(_ZN11QMessageBoxC1ENS_4IconERK7QStringS3_6QFlagsINS_14StandardButtonEEP7QWidgetS4_IN2Qt10WindowTypeEE+0x1f0) [0x77685b0]
#13 /usr/lib/libQtGui.so.4 [0x776885b]
#14 /usr/lib/libQtGui.so.4(_ZN11QMessageBox7warningEP7QWidgetRK7QStringS4_6QFlagsINS_14StandardButtonEES6_+0x36) [0x7768a76]
#15 panini [0x8057ca3]
#16 /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x35)
[0x6f0d095]
#17 /usr/lib/libQtCore.so.4(_Z8qWarningPKcz+0x71) [0x6f0d431]
#18 /usr/lib/libQtGui.so.4 [0x7290268]
#19 /usr/lib/libX11.so.6(_XError+0x109) [0x238aa9]

and it hangs until I kill it. I don't know what the above errors mean..
I'm not sure I have all the packages required to run the app.. And I
don't know how to determine them. (I've skipped the "requires" field in
the Spec). I understand how to determine build-requires. How do you
determine the requires??

regards,

Ankur

[Rahul Sundaram]

On 05/10/2009 07:34 PM, Ankur Sinha wrote:
> [Ankur@Ankur twitter_tui]$ panini
> QGtkStyle cannot be used together with the GTK_Qt engine.

This one is explained in

http://www.virtualbox.org/ticket/2702

(first hit in google while searching for that message)
> Locking assertion failure.  Backtrace:

No idea about this one. Ask in #fedora-kde channel or in fedora-kde
mailing list. They probably have a better idea.

Probably useful to create another user, run this program and check if it
is due to a local configuration change.
> and it hangs until I kill it. I don't know what the above errors mean..
> I'm not sure I have all the packages required to run the app.. And I
> don't know how to determine them. (I've skipped the "requires" field in
> the Spec). I understand how to determine build-requires. How do you
> determine the requires??

In general, RPM is capable of figuring it out automatically.

http://fedoraproject.org/wiki/Packaging:Guidelines#Requires

Otherwise, there a few different ways including running the program
using the mock --shell argument or running ldd against the binary.

Rahul

[Ankur Sinha]

On Sun, 2009-05-10 at 19:52 +0530, Rahul Sundaram wrote:
> On 05/10/2009 07:34 PM, Ankur Sinha wrote:
> > [Ankur@Ankur twitter_tui]$ panini
> > QGtkStyle cannot be used together with the GTK_Qt engine.
>
> This one is explained in
>
> http://www.virtualbox.org/ticket/2702
>
> (first hit in google while searching for that message)
> > Locking assertion failure.  Backtrace:
>
> No idea about this one. Ask in #fedora-kde channel or in fedora-kde
> mailing list. They probably have a better idea.
>
> Probably useful to create another user, run this program and check if it
> is due to a local configuration change.
> > and it hangs until I kill it. I don't know what the above errors mean..
> > I'm not sure I have all the packages required to run the app.. And I
> > don't know how to determine them. (I've skipped the "requires" field in
> > the Spec). I understand how to determine build-requires. How do you
> > determine the requires??
>
> In general, RPM is capable of figuring it out automatically.
>
> http://fedoraproject.org/wiki/Packaging:Guidelines#Requires
>
> Otherwise, there a few different ways including running the program
> using the mock --shell argument or running ldd against the binary.
>
> Rahul
>
> Fedora-india mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-india

hi,

Okay.. I think I get it.. This looks like the tougher part, as compared
to just building the package.. I'll work on it.

@Rahul Thanks for your help.

regards,

Ankur

[Rahul Sundaram]

On 05/10/2009 08:01 PM, Ankur Sinha wrote:
> Okay.. I think I get it.. This looks like the tougher part, as compared
> to just building the package.. I'll work on it.
>
> @Rahul Thanks for your help.

No problem.

Building a package is a relatively small portion of maintaining the
software in the repository. The majority of time for any actively used
software would be in handling bug reports. patches related to that,
handling updates etc. We do have a lack of documented guidelines that
convey the whole picture. I am working on that but my plate is full at
the moment.

Rahul

[Rahul Sundaram]

On 05/10/2009 08:01 PM, Ankur Sinha wrote:
> Okay.. I think I get it.. This looks like the tougher part, as compared
> to just building the package.. I'll work on it.
>
> @Rahul Thanks for your help.

Ankur,

Are you posting this package up for review?

Rahul

[Ankur Sinha]

On Wed, 2009-07-01 at 12:48 +0530, Rahul Sundaram wrote:
> On 05/10/2009 08:01 PM, Ankur Sinha wrote:
> > Okay.. I think I get it.. This looks like the tougher part, as compared
> > to just building the package.. I'll work on it.
> >
> > @Rahul Thanks for your help.
>
> Ankur,
>
> Are you posting this package up for review?
>
> Rahul

hi,

I think this is what you're asking about :

https://bugzilla.redhat.com/show_bug.cgi?id=507052

[Rakesh Pandit]

2009/5/8 Rahul Sundaram wrote:
> On 05/08/2009 08:10 AM, Ankur Sinha wrote:

[..]
> http://sourceforge.net/projects/pdfchain

Taken care.

--
Regards,
Rakesh Pandit