Anyone willing to maintain the RPMs?


#1

Hey folks,

As many of you have probably noticed the Jitsi RPM packages are
currently having a few issues. Pavel Tankov, who created our RPM builder
and packages and who maintained them for quite a while is having less
time to contribute these days, so we were wondering if anyway was
willing to continue the effort.

Maintaining the packages would require the maintainer to:

* maintain a build machine where the build would take place

* setup the build scripts (we will provide those that we currently use)

* allow the Jitsi build machine to connect over ssh and trigger builds
when necessary

* have sufficient bandwidth to allow for regular build uploads to our
download repository (up to about 5 times a day).

* regularly use Jitsi from within the rpm so that problems would become
obviously rapidly.

Any takers?

Emil

P.S. bcc-ed users list. please respond on dev.


#2

I'm not volunteering :slight_smile: BUT...

Just wanted to introduce myself. I'm a Fedora and RPM Fusion package
maintainer and was looking at trying to build RPM packages for Fedora,
however, when I tried setting up the spec file I ran into a few
issues, some of which I can't remember as it was several weeks ago,
but one major issue was the the RPM jitsi provides has quite a few
files that are not in the source tarball.

I think another was bundled libraries which is forbidden in Fedora and
frowned upon but tolerated in RPM Fusion. The most frequent offender
being ffmpeg.

We also use a program called rpmlint which checks for the most common
problems with RPM packages and I remember it finding quite a few with
the provided RPM package.

So while I don't think I can volunteer to take it over, I would like
to collaborate with whoever does.

Thanks,
Richard M. Shaw

···

2011/6/16 Emil Ivov <emcho@jitsi.org>:

Hey folks,

As many of you have probably noticed the Jitsi RPM packages are
currently having a few issues. Pavel Tankov, who created our RPM builder
and packages and who maintained them for quite a while is having less
time to contribute these days, so we were wondering if anyway was
willing to continue the effort.

Maintaining the packages would require the maintainer to:

* maintain a build machine where the build would take place

* setup the build scripts (we will provide those that we currently use)

* allow the Jitsi build machine to connect over ssh and trigger builds
when necessary

* have sufficient bandwidth to allow for regular build uploads to our
download repository (up to about 5 times a day).

* regularly use Jitsi from within the rpm so that problems would become
obviously rapidly.

Any takers?


#3

Hi,

I can provide and maintain RPM build machine. What Linux distribution
would be most suitable?

Regards,
Chris

···

2011/6/16 Emil Ivov <emcho@jitsi.org>:

Hey folks,

As many of you have probably noticed the Jitsi RPM packages are
currently having a few issues. Pavel Tankov, who created our RPM builder
and packages and who maintained them for quite a while is having less
time to contribute these days, so we were wondering if anyway was
willing to continue the effort.

Maintaining the packages would require the maintainer to:

* maintain a build machine where the build would take place

* setup the build scripts (we will provide those that we currently use)

* allow the Jitsi build machine to connect over ssh and trigger builds
when necessary

* have sufficient bandwidth to allow for regular build uploads to our
download repository (up to about 5 times a day).

* regularly use Jitsi from within the rpm so that problems would become
obviously rapidly.

Any takers?

Emil

P.S. bcc-ed users list. please respond on dev.


#4

I take the opportunity to mention this OpenSUSE issue which could be
resolved in a better way:

Unable to install "java >= 1:1.5.0"
http://java.net/jira/browse/JITSI-836

I do not use OpenSUSE and can not offer to help but there is this:

OpenSUSE Build Service
https://build.opensuse.org/

Cheers,
Andreas

···

---

Am 16.06.2011 16:18, schrieb Emil Ivov:

Hey folks,

As many of you have probably noticed the Jitsi RPM packages are
currently having a few issues. Pavel Tankov, who created our RPM builder
and packages and who maintained them for quite a while is having less
time to contribute these days, so we were wondering if anyway was
willing to continue the effort.

Maintaining the packages would require the maintainer to:

* maintain a build machine where the build would take place

* setup the build scripts (we will provide those that we currently use)

* allow the Jitsi build machine to connect over ssh and trigger builds
when necessary

* have sufficient bandwidth to allow for regular build uploads to our
download repository (up to about 5 times a day).

* regularly use Jitsi from within the rpm so that problems would become
obviously rapidly.

Any takers?

Emil

P.S. bcc-ed users list. please respond on dev.


#5

I'm experimenting with the openSUSE Build Service (now "Open Build Service"), and
I think it's a good tool to build packages. It allows to build specific packages for other distributions, too.
The main page at the openSUSE Buid Service for the Jitsi package I created is
https://build.opensuse.org/package/show?package=jitsi&project=home%3ADaniLeo%3AVoIP
while the repository for the latest version of openSUSE is at
http://download.opensuse.org/repositories/home:/DaniLeo:/VoIP/openSUSE_11.4/
Have a look at it and tell what you think.
The sources are not the very latest, because I have to trigger the rebuild manually.
It could be tiggered also using a tool (called osc), so it could be possible to trigger the rebuild when necessary
by the server that schedules all the builds.

Cheers!
Daniel

···

I take the opportunity to mention this OpenSUSE issue which could be
resolved in a better way:

Unable to install "java >= 1:1.5.0"
http://java.net/jira/browse/JITSI-836

I do not use OpenSUSE and can not offer to help but there is this:

OpenSUSE Build Service
https://build.opensuse.org/

Cheers,
Andreas
---

Am 16.06.2011 16:18, schrieb Emil Ivov:

Hey folks,

As many of you have probably noticed the Jitsi RPM packages are
currently having a few issues. Pavel Tankov, who created our RPM builder
and packages and who maintained them for quite a while is having less
time to contribute these days, so we were wondering if anyway was
willing to continue the effort.

Maintaining the packages would require the maintainer to:

* maintain a build machine where the build would take place

* setup the build scripts (we will provide those that we currently use)

* allow the Jitsi build machine to connect over ssh and trigger builds
when necessary

* have sufficient bandwidth to allow for regular build uploads to our
download repository (up to about 5 times a day).

* regularly use Jitsi from within the rpm so that problems would become
obviously rapidly.

Any takers?

Emil

P.S. bcc-ed users list. please respond on dev.


#6

Hello,

I'm a packager mantainer for Mandriva, I want to package this project
for our repository too.

I couldnt assume full responsibility for the RPM builds but we can work
together in an cross compatible SPEC file, so minimal changes will take
place to package to others RPM distros, and this SPEC could live on the
trunk of the project, so anyone could reach it easily.

My main concern, after taking a look at the src.rpm provided in the
OpenSuse build services is the size of the tarball.

Is there any "clean" tarball generator in place? We need a script to
clean up the trunk code (removing no linux related and every 3d party
libs, and all the svn hooks too)

If anyone has interest please drop an email, I'll be working on this
during this week I hope.

Regards

Guilherme Moro


#7

hello,

I wish to unsubscribe the current work email and subscribe the new one. I can't figure out how to unsubscribe. Can someone help me out?

Renato


#8

Let me know if there's anything I can do to help. I'd like the same
thing for Fedora and we appear to have the same issues (such as 3rd
party libs).

Thanks,
Richard

···

On Sun, Jun 19, 2011 at 1:19 PM, <guilherme.moro@gmail.com> wrote:

Hello,

I'm a packager mantainer for Mandriva, I want to package this project
for our repository too.

I couldnt assume full responsibility for the RPM builds but we can work
together in an cross compatible SPEC file, so minimal changes will take
place to package to others RPM distros, and this SPEC could live on the
trunk of the project, so anyone could reach it easily.

My main concern, after taking a look at the src.rpm provided in the
OpenSuse build services is the size of the tarball.

Is there any "clean" tarball generator in place? We need a script to
clean up the trunk code (removing no linux related and every 3d party
libs, and all the svn hooks too)

If anyone has interest please drop an email, I'll be working on this
during this week I hope.


#9

http://java.net/projects/jitsi/lists

log in, and this page should show you an unsubscribe button.

···

On Sun, Jun 19, 2011 at 8:00 PM, Renato Rodrigues <renato@passolivre.org>wrote:

hello,

I wish to unsubscribe the current work email and subscribe the new one. I
can't figure out how to unsubscribe. Can someone help me out?

Renato


#10

BTW: The 3rd pary libraries would also have to be packaged separately
for an inclusion in Debian. There are tools to help with this.

Two links for those who might be interested:
http://wiki.debian.org/Java/Packaging
http://www.debian.org/doc/manuals/debian-java-faq/ch4.html

Cheers,
Andreas

···

Am 20.06.2011 15:50, schrieb Richard Shaw:

Let me know if there's anything I can do to help. I'd like the same
thing for Fedora and we appear to have the same issues (such as 3rd
party libs).

Thanks,
Richard


#11

Hey Renato,

I am not sure that the java.net page would allow you to unsubscribe if
you subscribed without a java.net account in the first place. If this is
the case, you should use our primary Mailing Lists page here:

http://jitsi.org/mailinglists

You'll find unsubscription instructions there.

Hope this helps,
Emil

На 20.06.11 01:22, Guilherme Moro написа:

···

http://java.net/projects/jitsi/lists

log in, and this page should show you an unsubscribe button.

On Sun, Jun 19, 2011 at 8:00 PM, Renato Rodrigues <renato@passolivre.org > <mailto:renato@passolivre.org>> wrote:

    hello,

    I wish to unsubscribe the current work email and subscribe the new
    one. I can't figure out how to unsubscribe. Can someone help me out?

    Renato

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#12

Yup, the same is required for Fedora.

http://fedoraproject.org/wiki/Packaging:Java

I do, however, have a working package based on someone else's spec
file from back in 2010 (man it feels weird saying that! :).

I know the debian build process is very different but you may be able
to translate my spec into something usable for Debian. Pull the spec
and patches from:

http://hobbes1069.fedorapeople.org/jitsi/

Richard

···

On Mon, Jun 20, 2011 at 12:14 PM, Andreas Kuckartz <A.Kuckartz@ping.de> wrote:

BTW: The 3rd pary libraries would also have to be packaged separately
for an inclusion in Debian. There are tools to help with this.

Two links for those who might be interested:
http://wiki.debian.org/Java/Packaging
http://www.debian.org/doc/manuals/debian-java-faq/ch4.html


#13

Could not create framework :java.lang.NoClassDefFoundError:org/osgi/framework/launch/Framework ?

how to resolve this problem ?


#14

На 23.10.11 23:00, Richard Shaw написа:

···

On Mon, Jun 20, 2011 at 12:14 PM, Andreas Kuckartz <A.Kuckartz@ping.de> wrote:

BTW: The 3rd pary libraries would also have to be packaged separately
for an inclusion in Debian. There are tools to help with this.

Two links for those who might be interested:
http://wiki.debian.org/Java/Packaging
http://www.debian.org/doc/manuals/debian-java-faq/ch4.html

Yup, the same is required for Fedora.

http://fedoraproject.org/wiki/Packaging:Java

I do, however, have a working package based on someone else's spec
file from back in 2010 (man it feels weird saying that! :).

I know the debian build process is very different but you may be able
to translate my spec into something usable for Debian. Pull the spec
and patches from:

http://hobbes1069.fedorapeople.org/jitsi/

FYI, the debian packaging files are already part of the Jitsi source and
a Debian package can be easily built by executing "ant deb"

I am also very much OK to also have our RPM build scripts published so
if any one of the maintainers has the time to do so, please go ahead!

Cheers,
Emil