5:09 p.m.
Hi all!
More and more people talk to me and ask "when will RPM Fusion for
EL/EPEL 5 start". As a big junk of the livna import is now done I might
over the next few weeks slowly start to do the same work for EPEL. But I
need to know which of the package owners actually is willing to maintain
their packages in RPM Fusion's EL-branch.
So if you want to maintain all or some of you packages for EL drop me a
line please. Then I'll create branches for them sooner or later and help
with the initial build round just like I do for Fedora now.
You are a Fedora/EPEL packager and interested in RPM Fusion for EL/EPEL
as well but don't own packages in RPM Fusion (or dribble / frehsrpms /
livna) yet? Then drop me a line -- some of the current RPM Fusion
packagers won't be intersted in EPEL, so we need to find owners for
their packages in RPM Fusions EL-branch. There are likely some deps for
RPM Fusions packages that are still missing in EPEL -- so the more hands
that can help with that the better.
Cu
knurd
6:49 p.m.
Thorsten Leemhuis a écrit :
So if you want to maintain all or some of you packages for EL drop me
a
line please. Then I'll create branches for them sooner or later and help
with the initial build round just like I do for Fedora now.
Hi
Please create the EPEL branches for
- pdflib-lite
- php-pecl-pdflib
I will work on the build ASAP
Remi.
3:36 p.m.
On 13.08.2008 20:49, Remi Collet wrote:
Thorsten Leemhuis a écrit :
> So if you want to maintain all or some of you packages for EL drop me a
> line please. Then I'll create branches for them sooner or later and help
> with the initial build round just like I do for Fedora now.
Please create the EPEL branches for
- pdflib-lite
- php-pecl-pdflib
Done.
I will work on the build ASAP
While at it: the x86 builder is still down; hopefully he gets online
again tomorrow.
CU
knurd
4:56 p.m.
On Mon, 2008-08-11 at 19:09 +0200, Thorsten Leemhuis wrote:
Hi all!
More and more people talk to me and ask "when will RPM Fusion for
EL/EPEL 5 start". As a big junk of the livna import is now done I might
over the next few weeks slowly start to do the same work for EPEL. But I
need to know which of the package owners actually is willing to maintain
their packages in RPM Fusion's EL-branch.
I'll maintain my packages (as long as the dependencies are there) for
EPEL (-:
/David
8:25 p.m.
Thorsten Leemhuis píše v Po 11. 08. 2008 v 19:09 +0200:
Hi all!
More and more people talk to me and ask "when will RPM Fusion for
EL/EPEL 5 start". As a big junk of the livna import is now done I might
over the next few weeks slowly start to do the same work for EPEL. But I
need to know which of the package owners actually is willing to maintain
their packages in RPM Fusion's EL-branch.
So if you want to maintain all or some of you packages for EL drop me a
line please. Then I'll create branches for them sooner or later and help
with the initial build round just like I do for Fedora now.
I am ready push kino into the EL-branches (EL4 + EL5), prerequisites are
ffmpeg and libquicktime.
You are a Fedora/EPEL packager and interested in RPM Fusion for
EL/EPEL
as well but don't own packages in RPM Fusion (or dribble / frehsrpms /
livna) yet? Then drop me a line -- some of the current RPM Fusion
packagers won't be intersted in EPEL, so we need to find owners for
their packages in RPM Fusions EL-branch. There are likely some deps for
RPM Fusions packages that are still missing in EPEL -- so the more hands
that can help with that the better.
Dan
2:47 p.m.
On 11.08.2008 19:09, Thorsten Leemhuis wrote:
So if you want to maintain all or some of you packages for EL drop me
a
line please. Then I'll create branches for them sooner or later and help
with the initial build round just like I do for Fedora now.
Here is a list of packages I branched for EL-5 so far:
Free:
+Fedora EPEL|ffmpeg2theora|Convert any file that ffmpeg can decode to
theora|kwizart(a)gmail.com||
+Fedora EPEL|ffmpeg-compat|Libraries for ffmpeg-compat|kwizart(a)gmail.com||
+Fedora EPEL|gpac|MPEG-4 multimedia framework|kwizart(a)gmail.com||
+Fedora EPEL|kino|Kino is a non-linear DV editor for GNU/Linux|dan(a)danny.cz||
+Fedora EPEL|libdvbpsi|Library for MPEG TS and DVB PSI tables decoding and
generation|kwizart(a)gmail.com||
+Fedora EPEL|libmad|MPEG audio decoder library|david(a)juran.se||
+Fedora EPEL|libmpeg3|Decoder of various derivatives of MPEG
standards|kwizart(a)gmail.com||
+Fedora EPEL|libquicktime|A library for reading and writing Quicktime
files.|kwizart(a)gmail.com||
+Fedora EPEL|smpeg|MPEG library for SDL|kwizart(a)gmail.com||
+Fedora EPEL|transcode|Video stream processing tool|david(a)juran.se||
+Fedora EPEL|vcdimager|VideoCD mastering and ripping tool|kwizart(a)gmail.com||
+Fedora EPEL|vlc|Multi-platform MPEG, DVD, and DivX player|kwizart(a)gmail.com||
+Fedora EPEL|xv|Interactive image display program for X|somlo(a)cmu.edu||
Nonfree:
+Fedora EPEL|Cg|NVIDIA Cg Toolkit|kwizart(a)gmail.com||
+Fedora EPEL|pdflib-lite|Portable C library for dynamically generating PDF
files|Fedora(a)FamilleCollet.com||
+Fedora EPEL|php-pecl-pdflib|Package for generating PDF files|Fedora(a)FamilleCollet.com||
CU
knurd
11:41 p.m.
Thorsten Leemhuis :
So if you want to maintain all or some of you packages for EL drop me
a line please. Then I'll create branches for them sooner or later and
help with the initial build round just like I do for Fedora now.
Hello
My name is Nikolay Ulyanitsky.
I am the main developer of the "Red Hat Club Repository" project
(http://www.redhat-club.org/Repository -- site in Russian).
The main purpose of the project is build/rebuild extra packages for EPEL
and RPMFusion repositories for RHEL-based distributions following Fedora
Packaging Guidelines.
We rebuilded several packages from Livna 9 / Fedora 9 repositories with
small changes and added own packages.
kmod's is builded by RHEL technology: is not necessary to rebuild them
for every kernel update or build akmod's or dkms packages because RHEL
kernels have stable KABI (kmod builded for RHEL 5.0 will work on CentOS
5.2 and vise versa).
* Packages list
http://www.redhat-club.org/Repository/Packages
* SRPM repository
http://repo.redhat-club.org/redhat/5/SRPMS/
* SVN (only spec files, patches and spec.diff (diff between original
spec and modified))
http://svn.repo.redhat-club.org/
I want to help to maintain some packages for EL branch in RPMFusion that
don't have owners yet.
--
Nikolay Ulyanitsky <lystor(a)lystor.org.ua>
6:45 a.m.
Nikolay Ulyanitsky wrote:
Thorsten Leemhuis :
> So if you want to maintain all or some of you packages for EL drop me
> a line please. Then I'll create branches for them sooner or later and
> help with the initial build round just like I do for Fedora now.
Hello
My name is Nikolay Ulyanitsky.
I am the main developer of the "Red Hat Club Repository" project
(http://www.redhat-club.org/Repository -- site in Russian).
The main purpose of the project is build/rebuild extra packages for EPEL
and RPMFusion repositories for RHEL-based distributions following Fedora
Packaging Guidelines.
We rebuilded several packages from Livna 9 / Fedora 9 repositories with
small changes and added own packages.
kmod's is builded by RHEL technology: is not necessary to rebuild them
for every kernel update or build akmod's or dkms packages because RHEL
kernels have stable KABI (kmod builded for RHEL 5.0 will work on CentOS
5.2 and vise versa).
* Packages list
http://www.redhat-club.org/Repository/Packages
* SRPM repository
http://repo.redhat-club.org/redhat/5/SRPMS/
* SVN (only spec files, patches and spec.diff (diff between original
spec and modified))
http://svn.repo.redhat-club.org/
I want to help to maintain some packages for EL branch in RPMFusion that
don't have owners yet.
Hi Nikolay,
Welcome, glad to hear someone wants to help out with the EPEL part of rpmfusion.
Question, do you maintain any packages in Fedora / EPEL itself?
Regards,
Hans
10:45 a.m.
Hi Hans
Welcome, glad to hear someone wants to help out with the EPEL part of
rpmfusion.
Question, do you maintain any packages in Fedora / EPEL itself?
At this time I am not a Fedora/EPEL contributor because I
thought that EPEL contributors must support Fedora packages too but
I use RHEL everywhere and have no time to support Fedora.
--
Nikolay Ulyanitsky <lystor(a)lystor.org.ua>
12:47 p.m.
On 16.08.2008 12:45, Nikolay Ulyanitsky wrote:
> Welcome, glad to hear someone wants to help out with the EPEL
part of rpmfusion.
> Question, do you maintain any packages in Fedora / EPEL itself?
At this time I am not a Fedora/EPEL contributor because I
thought that EPEL contributors must support Fedora packages too but
I use RHEL everywhere and have no time to support Fedora.
I mentioned it to Nikolay in private already, but I just wanted to state
it here for the rest of the readers as well:
You can participate in EPEL without contributing to Fedora. Some Fedora
people don't like that concept to much, but it's imho a good thing and
definitely allowed (might be in the EPEL FAQ even, but that's 503 right
now, so I can't check) :-)
Cu
knurd
1:06 p.m.
On 16.08.2008 01:41, Nikolay Ulyanitsky wrote:
Thorsten Leemhuis :
> So if you want to maintain all or some of you packages for EL drop me
> a line please. Then I'll create branches for them sooner or later and
> help with the initial build round just like I do for Fedora now.
[...]
reply a bit out of order ;-)
I want to help to maintain some packages for EL branch in RPMFusion
that
don't have owners yet.
Welcome Nikolay! It's great to see people showing interest in the EL
stuff that RPM Fusion plans. I suppose we can need a few helping hands
there, as some of the RPM Fusion packagers likely have no interest in EL
stuff.
[...]
We rebuilded several packages from Livna 9 / Fedora 9 repositories with
small changes and added own packages.
* Packages list
http://www.redhat-club.org/Repository/Packages
* SRPM repository
http://repo.redhat-club.org/redhat/5/SRPMS/
* SVN (only spec files, patches and spec.diff (diff between original
spec and modified))
http://svn.repo.redhat-club.org/
Thx for the pointers. If there are patches in you packages that might be
of general interest then consider to send them to the RPM Fusion package
owners; you can find them in these files
http://cvs.rpmfusion.org/viewvc/free/owners/owners.list?view=markup
http://cvs.rpmfusion.org/viewvc/free/owners/owners.epel.list?view=markup
http://cvs.rpmfusion.org/viewvc/nonfree/owners/owners.list?view=markup
http://cvs.rpmfusion.org/viewvc/nonfree/owners/owners.epel.list?view=markup
At the same time it might be wise for the RPM Fusion packagers to look
for changes in SVN from the "Red Hat Club Repository" (see above for the
URL). That might makes things easier and avoid pitfalls/bugs --
especially when you try to build your packages for EL.
Note that lkundrak recently published a repo which holds some of the
Livna packages rebuild for EL as well; see
http://elvn.getrpm.net/
http://elvn.getrpm.net/svn/packages/
http://elvn.getrpm.net/rpm/el5/
for details and patches.
kmod's is builded by RHEL technology: is not necessary to
rebuild
them for every kernel update or build akmod's or dkms packages
because RHEL kernels have stable KABI (kmod builded for RHEL 5.0 will
work on CentOS 5.2 and vise versa).
I hope we can do the same for RPM Fusion -- but I have not looked into
that yet.
In fact we didn't even agree on what kernel module packaging standard to
use for RPM Fusion at all -- but your comment imho is yet another reason
to go the kmod route, as this afaics provides all that we need:
- pre compiled kmods (Fedora)
- pre compiled kmods that are not kernel specific (EL)
- dynamically builds kmods using akmods (mainly Fedora, but might be of
interest for some EL users as well)
Cu
knurd
10:11 a.m.
On 11.08.2008 19:09, Thorsten Leemhuis wrote:
More and more people talk to me and ask "when will RPM Fusion for
EL/EPEL 5 start". As a big junk of the livna import is now done I might
over the next few weeks slowly start to do the same work for EPEL. But I
need to know which of the package owners actually is willing to maintain
their packages in RPM Fusion's EL-branch.
So if you want to maintain all or some of you packages for EL drop me a
line please. Then I'll create branches for them sooner or later and help
with the initial build round just like I do for Fedora now.
If you are a RPM Fusion contributor but are *not* at all interested in
maintaining you packages for EL then please add you fas username and a
your email to
http://rpmfusion.org/PackagersNotInterestedInEL
That will help those interested in EL to identify packages that need new
owners for the EL branch.
tia
Cu
knurd
10:32 a.m.
2008/8/17 Thorsten Leemhuis <fedora(a)leemhuis.info>:
If you are a RPM Fusion contributor but are *not* at all interested
in
maintaining you packages for EL then please add you fas username and a your
email to
http://rpmfusion.org/PackagersNotInterestedInEL
That will help those interested in EL to identify packages that need new
owners for the EL branch.
I thought a lot about this and I don't think that having a wiki page
that lists packagers not interested in EL is the right way to proceed.
I think that having a wish list for EL packages like EPEL does works
better.
You may wonder why :) For example, I mostly maintain emulators in RPM
Fusion. I don't think that there is a need to have those compiler for
EL. Maybe for some emulators I maybe wrong and that's the purpose of
the wish list.
Your opinions are welcome.
Bye,
Andrea.
10:52 a.m.
On 19.08.2008 12:32, Andrea Musuruane wrote:
2008/8/17 Thorsten Leemhuis <fedora(a)leemhuis.info>:
> If you are a RPM Fusion contributor but are *not* at all interested in
> maintaining you packages for EL then please add you fas username and a your
> email to
> http://rpmfusion.org/PackagersNotInterestedInEL
> That will help those interested in EL to identify packages that need new
> owners for the EL branch.
I thought a lot about this and I don't think that having a wiki page
that lists packagers not interested in EL is the right way to proceed.
It IMHO definitely is -- EPEL has one as well and it helped a lot!
http://fedoraproject.org/wiki/EPEL/ContributorStatus
I think that having a wish list for EL packages like EPEL does works
better.
That can and should come later once we started.
[...]
CU
knurd
6:45 p.m.
Thorsten Leemhuis wrote:
On 11.08.2008 19:09, Thorsten Leemhuis wrote:
>
> More and more people talk to me and ask "when will RPM Fusion for
> EL/EPEL 5 start". As a big junk of the livna import is now done I
> might over the next few weeks slowly start to do the same work for
> EPEL. But I need to know which of the package owners actually is
> willing to maintain their packages in RPM Fusion's EL-branch.
>
> So if you want to maintain all or some of you packages for EL drop me
> a line please. Then I'll create branches for them sooner or later and
> help with the initial build round just like I do for Fedora now.
Branch for EL-5 please:
akode-extras
amarok-extras-freeworld
k3b-extras-freeworld
kdemultimedia-extras-freeworld
libtunepimp-extras-freeworld
xine-lib-extras-freeworld
(heck, feel free to add anything else that I maintain to that list too). :)
-- Rex
7:24 p.m.
On Fri, Aug 22, 2008 at 8:45 PM, Rex Dieter <rdieter(a)math.unl.edu> wrote:
Thorsten Leemhuis wrote:
> On 11.08.2008 19:09, Thorsten Leemhuis wrote:
> >
>
>> More and more people talk to me and ask "when will RPM Fusion for EL/EPEL
>> 5 start". As a big junk of the livna import is now done I might over the
>> next few weeks slowly start to do the same work for EPEL. But I need to know
>> which of the package owners actually is willing to maintain their packages
>> in RPM Fusion's EL-branch.
>>
>> So if you want to maintain all or some of you packages for EL drop me a
>> line please. Then I'll create branches for them sooner or later and help
>> with the initial build round just like I do for Fedora now.
>>
>
Branch for EL-5 please:
akode-extras
amarok-extras-freeworld
k3b-extras-freeworld
kdemultimedia-extras-freeworld
libtunepimp-extras-freeworld
xine-lib-extras-freeworld
(heck, feel free to add anything else that I maintain to that list too). :)
Done.
--
Xavier.t Lamien
--
http://fedoraproject.org/wiki/XavierLamien
GPG-Key ID: F3903DEB
Fingerprint: 0F2A 7A17 0F1B 82EE FCBF 1F51 76B7 A28D F390 3DEB
3:27 p.m.
Thorsten Leemhuis schrieb:
Hi all!
More and more people talk to me and ask "when will RPM Fusion for
EL/EPEL 5 start". As a big junk of the livna import is now done I might
over the next few weeks slowly start to do the same work for EPEL. But I
need to know which of the package owners actually is willing to maintain
their packages in RPM Fusion's EL-branch.
So if you want to maintain all or some of you packages for EL drop me a
line please. Then I'll create branches for them sooner or later and help
with the initial build round just like I do for Fedora now.
I assume that RPMfusion/EPEL is using the same guidelines for updating
packages as EPEL itself? [1]
If so I'm not sure I'll be able to contribute. In a worst case scenario
my package fails to build because a BR was updated for some reason (eg.
serious security hole) and I'm not able to fix this (no programming
skills here).
Or do I misunderstand the guidelines here?
Sebastian
[1]
https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Package_mainten...
10:28 p.m.
On Wed, Sep 10, 2008 at 5:27 PM, Sebastian Vahl <ml(a)deadbabylon.de> wrote:
Thorsten Leemhuis schrieb:
> Hi all!
>
> More and more people talk to me and ask "when will RPM Fusion for
> EL/EPEL 5 start". As a big junk of the livna import is now done I might
> over the next few weeks slowly start to do the same work for EPEL. But I
> need to know which of the package owners actually is willing to maintain
> their packages in RPM Fusion's EL-branch.
>
> So if you want to maintain all or some of you packages for EL drop me a
> line please. Then I'll create branches for them sooner or later and help
> with the initial build round just like I do for Fedora now.
I assume that RPMfusion/EPEL is using the same guidelines for updating
packages as EPEL itself? [1]
Actually, yes. Except for kmod availability.
If so I'm not sure I'll be able to contribute. In a worst
case scenario
my package fails to build because a BR was updated for some reason (eg.
serious security hole)
Update from where, Redhat Enterprise Linux base repository ?
and I'm not able to fix this (no programming
skills here).
Feel free to bug on bz.rf.o
Other folks could give you a hand on that.
--
Xavier.t Lamien
--
http://fedoraproject.org/wiki/XavierLamien
GPG-Key ID: F3903DEB
Fingerprint: 0F2A 7A17 0F1B 82EE FCBF 1F51 76B7 A28D F390 3DEB
4:03 p.m.
On 10.09.2008 17:27, Sebastian Vahl wrote:
Thorsten Leemhuis schrieb:
> More and more people talk to me and ask "when will RPM Fusion for
> EL/EPEL 5 start". As a big junk of the livna import is now done I might
> over the next few weeks slowly start to do the same work for EPEL. But I
> need to know which of the package owners actually is willing to maintain
> their packages in RPM Fusion's EL-branch.
>
> So if you want to maintain all or some of you packages for EL drop me a
> line please. Then I'll create branches for them sooner or later and help
> with the initial build round just like I do for Fedora now.
I assume that RPMfusion/EPEL is using the same guidelines for updating
packages as EPEL itself? [1]
I'd say so.
If so I'm not sure I'll be able to contribute. In a worst
case scenario
my package fails to build because a BR was updated for some reason (eg.
serious security hole) and I'm not able to fix this (no programming
skills here).
That of course can happen -- just like in can happen in Fedora as well.
Okay, to be fair, it likely happens a bit more often in the EL branch --
especially if brand new and old stuff gets mixed together (which
normally should not happen that often normally in the EL branch, as the
EPEL policy suggest to only update packages to new versions if there is
a really good reason).
In my experience the problem you outline happens quite seldom. And if it
happens, then most of the time it's easy to find a workaround or patch
to circumvent the problem. In the rare cases where programmings skills
really are needed it's often not that hard to get help from upstream or
other Fedora folks.
So the potential problem you outline is nothing I'd worry about.
CU
knurd
5704
days inactive
5735
days old
rpmfusion-developers@lists.rpmfusion.org
19 comments
11 participants
participants (11)
-
Andrea Musuruane -
Dan Horák -
David Juran -
Hans de Goede -
Nicolas Chauvet -
Nikolay Ulyanitsky -
Remi Collet -
Rex Dieter -
Sebastian Vahl -
Thorsten Leemhuis -
Xavier Lamien