[users] libupnp

["Germán Andrés Pulido F."]

Hi!

libupnp has been on version 1.6.6 so long, and the current version is
the 1.6.13. I downloaded the spec file from
https://raw.github.com/repoforge/rpms/master/specs/libupnp/libupnp.spec,
changed the version (from 1.6.6 to 1.6.13) and rebuilt the package
successfully on Centos 6.0 both 32 and 64 bits. Can this package be
rebuilt using the latest 1.6.13 version?

Thanks!

[Dag Wieers]

Post by "Germán Andrés Pulido F."
libupnp has been on version 1.6.6 so long, and the current version is
the 1.6.13. I downloaded the spec file from
https://raw.github.com/repoforge/rpms/master/specs/libupnp/libupnp.spec,
changed the version (from 1.6.6 to 1.6.13) and rebuilt the package
successfully on Centos 6.0 both 32 and 64 bits. Can this package be
rebuilt using the latest 1.6.13 version?

Yes, that's possible. However, you can do this yourself by modifying the
SPEC file in Github and providing a pull-request.

More information is available from:

http://github.com/repoforge

Thanks for the feedback !

[Yury V. Zaytsev]

Post by Dag Wieers

Post by "Germán Andrés Pulido F."
libupnp has been on version 1.6.6 so long, and the current version is
the 1.6.13. I downloaded the spec file from
https://raw.github.com/repoforge/rpms/master/specs/libupnp/libupnp.spec,
changed the version (from 1.6.6 to 1.6.13) and rebuilt the package
successfully on Centos 6.0 both 32 and 64 bits. Can this package be
rebuilt using the latest 1.6.13 version?

Yes, that's possible. However, you can do this yourself by modifying the
SPEC file in Github and providing a pull-request.

+1

Pull requests are highly appreciated. I know we are far behind
processing them, but the day will come... :-/

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Dag Wieers

Post by "Germán Andrés Pulido F."
libupnp has been on version 1.6.6 so long, and the current version is
the 1.6.13. I downloaded the spec file from
https://raw.github.com/repoforge/rpms/master/specs/libupnp/libupnp.spec,
changed the version (from 1.6.6 to 1.6.13) and rebuilt the package
successfully on Centos 6.0 both 32 and 64 bits. Can this package be
rebuilt using the latest 1.6.13 version?

Yes, that's possible. However, you can do this yourself by modifying the
SPEC file in Github and providing a pull-request.

+1
Pull requests are highly appreciated. I know we are far behind
processing them, but the day will come... :-/

And then we get to the point that libupnp is very hard to upgrade on eg.
RHEL5 and RHEL4 (even though it compiles fine) because it breaks ABI.
Older videolan, mplayer and others do not compile against newer libupnp...

On RHEL6, the newer vlc does compile with the newer libupnp, haven't
tested mplayer yet. But again something fairly simple quickly becomes a
nightmare. Which is why I only touch the whole multimedia set once every
year :-(

What is de advantage of the newer libupnp ?

[German Pulido]

Thanks for your pointers Dag

The only advantages I have found so far are:

1. I create my own RPMs for a P2P software named aMule, which uses libupnp. With current 1.6.6, aMule produces lots of warnings during compilation, with 1.6.13 no warnings at all.

2. libupnp 1.6.13 works with my router, 1.6.6 does not.

On a separate note, I currently have a little repository for RPM packages not present on repoforge (some game emulators and utilities). What is the process to make these part of repoforge?

Best regards,

Germ?n.

Post by Yury V. Zaytsev

Post by "Germán Andrés Pulido F."
libupnp has been on version 1.6.6 so long, and the current version is
the 1.6.13. I downloaded the spec file from
https://raw.github.com/repoforge/rpms/master/specs/libupnp/libupnp.spec,
changed the version (from 1.6.6 to 1.6.13) and rebuilt the package
successfully on Centos 6.0 both 32 and 64 bits. Can this package be
rebuilt using the latest 1.6.13 version?

Yes, that's possible. However, you can do this yourself by modifying the SPEC file in Github and providing a pull-request.

+1
Pull requests are highly appreciated. I know we are far behind
processing them, but the day will come... :-/

And then we get to the point that libupnp is very hard to upgrade on eg. RHEL5 and RHEL4 (even though it compiles fine) because it breaks ABI. Older videolan, mplayer and others do not compile against newer libupnp...
On RHEL6, the newer vlc does compile with the newer libupnp, haven't tested mplayer yet. But again something fairly simple quickly becomes a nightmare. Which is why I only touch the whole multimedia set once every year :-(
What is de advantage of the newer libupnp ?
--
-- dag wieers, dag at wieers.com, http://dag.wieers.com/
-- dagit linux solutions, info at dagit.net, http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]_______________________________________________
users mailing list
users at lists.repoforge.org
http://lists.repoforge.org/mailman/listinfo/users

[Yury V. Zaytsev]

Post by German Pulido
On a separate note, I currently have a little repository for RPM
packages not present on repoforge (some game emulators and utilities).
What is the process to make these part of repoforge?

1. Clone our repository on GitHub
2. Create your own branch
3. Make sure your specs follow our style
4. Create one directory per spec and commit
5. Push your clone to GitHub
6. Submit a pull request, explaining the changes
7. Wait for a long time for it to be processed

*3) Unfortunately there is no formal definition of 'style'. Just look at
the templates and some 'nice' SPECs when in doubt.

I personally like filezilla, Dag can for sure think of more, but I
didn't have time to work on the SPECs in the last couple of months so
I've lost the orientation a little bit.

*4) Make sure you build-test your specs on at least on
RHEL{5,6}{i386,x86_64}. Most of the time I spend on processing pull
requests is taken by rebuilding the SPECs and fixing arch/dist specific
issues properly.

[German Pulido]

Hi

Thanks for the instructions. I am not really familiar with github or what I need to clone it (should I have a web server published on the Internet or something?). I can learn by myself, just need a link to read :)

BTW: FileZilla is one of the RPMs I create :)

Regards.

Post by Yury V. Zaytsev

Post by German Pulido
On a separate note, I currently have a little repository for RPM
packages not present on repoforge (some game emulators and utilities).
What is the process to make these part of repoforge?

1. Clone our repository on GitHub
2. Create your own branch
3. Make sure your specs follow our style
4. Create one directory per spec and commit
5. Push your clone to GitHub
6. Submit a pull request, explaining the changes
7. Wait for a long time for it to be processed
*3) Unfortunately there is no formal definition of 'style'. Just look at
the templates and some 'nice' SPECs when in doubt.
I personally like filezilla, Dag can for sure think of more, but I
didn't have time to work on the SPECs in the last couple of months so
I've lost the orientation a little bit.
*4) Make sure you build-test your specs on at least on
RHEL{5,6}{i386,x86_64}. Most of the time I spend on processing pull
requests is taken by rebuilding the SPECs and fixing arch/dist specific
issues properly.
--
Sincerely yours,
Yury V. Zaytsev
_______________________________________________
users mailing list
users at lists.repoforge.org
http://lists.repoforge.org/mailman/listinfo/users

[Yury V. Zaytsev]

Post by German Pulido
Thanks for the instructions. I am not really familiar with github or
what I need to clone it (should I have a web server published on the
Internet or something?). I can learn by myself, just need a link to
read :)

No, you don't have to have a web server or anything like that. Just
register with github and use the big "Fork" button to fork the
repository into your account.

They also have nice help pages for you to read...

Post by German Pulido
BTW: FileZilla is one of the RPMs I create :)

Hmmm, in the git log it's attributed to Steve though... ;-)

[Yury V. Zaytsev]

Post by German Pulido
Thanks for the instructions. I am not really familiar with github or
what I need to clone it (should I have a web server published on the
Internet or something?). I can learn by myself, just need a link to
read :)

No, you don't have to have a web server or anything like that. Just
register with github and use the big "Fork" button to fork the
repository into your account.

They also have nice help pages for you to read...

Post by German Pulido
BTW: FileZilla is one of the RPMs I create :)

Hmmm, in the git log it's attributed to Steve though... ;-)

[German Pulido]

Hi

Thanks for the instructions. I am not really familiar with github or what I need to clone it (should I have a web server published on the Internet or something?). I can learn by myself, just need a link to read :)

BTW: FileZilla is one of the RPMs I create :)

Regards.

Post by Yury V. Zaytsev

Post by German Pulido
On a separate note, I currently have a little repository for RPM
packages not present on repoforge (some game emulators and utilities).
What is the process to make these part of repoforge?

1. Clone our repository on GitHub
2. Create your own branch
3. Make sure your specs follow our style
4. Create one directory per spec and commit
5. Push your clone to GitHub
6. Submit a pull request, explaining the changes
7. Wait for a long time for it to be processed
*3) Unfortunately there is no formal definition of 'style'. Just look at
the templates and some 'nice' SPECs when in doubt.
I personally like filezilla, Dag can for sure think of more, but I
didn't have time to work on the SPECs in the last couple of months so
I've lost the orientation a little bit.
*4) Make sure you build-test your specs on at least on
RHEL{5,6}{i386,x86_64}. Most of the time I spend on processing pull
requests is taken by rebuilding the SPECs and fixing arch/dist specific
issues properly.
--
Sincerely yours,
Yury V. Zaytsev
_______________________________________________
users mailing list
users at lists.repoforge.org
http://lists.repoforge.org/mailman/listinfo/users

[Yury V. Zaytsev]

Post by German Pulido
On a separate note, I currently have a little repository for RPM
packages not present on repoforge (some game emulators and utilities).
What is the process to make these part of repoforge?

1. Clone our repository on GitHub
2. Create your own branch
3. Make sure your specs follow our style
4. Create one directory per spec and commit
5. Push your clone to GitHub
6. Submit a pull request, explaining the changes
7. Wait for a long time for it to be processed

*3) Unfortunately there is no formal definition of 'style'. Just look at
the templates and some 'nice' SPECs when in doubt.

I personally like filezilla, Dag can for sure think of more, but I
didn't have time to work on the SPECs in the last couple of months so
I've lost the orientation a little bit.

*4) Make sure you build-test your specs on at least on
RHEL{5,6}{i386,x86_64}. Most of the time I spend on processing pull
requests is taken by rebuilding the SPECs and fixing arch/dist specific
issues properly.

[German Pulido]

Thanks for your pointers Dag

The only advantages I have found so far are:

1. I create my own RPMs for a P2P software named aMule, which uses libupnp. With current 1.6.6, aMule produces lots of warnings during compilation, with 1.6.13 no warnings at all.

2. libupnp 1.6.13 works with my router, 1.6.6 does not.

On a separate note, I currently have a little repository for RPM packages not present on repoforge (some game emulators and utilities). What is the process to make these part of repoforge?

Best regards,

Germ?n.

Post by Yury V. Zaytsev

Post by "Germán Andrés Pulido F."
libupnp has been on version 1.6.6 so long, and the current version is
the 1.6.13. I downloaded the spec file from
https://raw.github.com/repoforge/rpms/master/specs/libupnp/libupnp.spec,
changed the version (from 1.6.6 to 1.6.13) and rebuilt the package
successfully on Centos 6.0 both 32 and 64 bits. Can this package be
rebuilt using the latest 1.6.13 version?

Yes, that's possible. However, you can do this yourself by modifying the SPEC file in Github and providing a pull-request.

+1
Pull requests are highly appreciated. I know we are far behind
processing them, but the day will come... :-/

And then we get to the point that libupnp is very hard to upgrade on eg. RHEL5 and RHEL4 (even though it compiles fine) because it breaks ABI. Older videolan, mplayer and others do not compile against newer libupnp...
On RHEL6, the newer vlc does compile with the newer libupnp, haven't tested mplayer yet. But again something fairly simple quickly becomes a nightmare. Which is why I only touch the whole multimedia set once every year :-(
What is de advantage of the newer libupnp ?
--
-- dag wieers, dag at wieers.com, http://dag.wieers.com/
-- dagit linux solutions, info at dagit.net, http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]_______________________________________________
users mailing list
users at lists.repoforge.org
http://lists.repoforge.org/mailman/listinfo/users

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Dag Wieers

Post by "Germán Andrés Pulido F."
libupnp has been on version 1.6.6 so long, and the current version is
the 1.6.13. I downloaded the spec file from
https://raw.github.com/repoforge/rpms/master/specs/libupnp/libupnp.spec,
changed the version (from 1.6.6 to 1.6.13) and rebuilt the package
successfully on Centos 6.0 both 32 and 64 bits. Can this package be
rebuilt using the latest 1.6.13 version?

Yes, that's possible. However, you can do this yourself by modifying the
SPEC file in Github and providing a pull-request.

+1
Pull requests are highly appreciated. I know we are far behind
processing them, but the day will come... :-/

And then we get to the point that libupnp is very hard to upgrade on eg.
RHEL5 and RHEL4 (even though it compiles fine) because it breaks ABI.
Older videolan, mplayer and others do not compile against newer libupnp...

On RHEL6, the newer vlc does compile with the newer libupnp, haven't
tested mplayer yet. But again something fairly simple quickly becomes a
nightmare. Which is why I only touch the whole multimedia set once every
year :-(

What is de advantage of the newer libupnp ?

[Yury V. Zaytsev]

Post by Dag Wieers

Post by "Germán Andrés Pulido F."
libupnp has been on version 1.6.6 so long, and the current version is
the 1.6.13. I downloaded the spec file from
https://raw.github.com/repoforge/rpms/master/specs/libupnp/libupnp.spec,
changed the version (from 1.6.6 to 1.6.13) and rebuilt the package
successfully on Centos 6.0 both 32 and 64 bits. Can this package be
rebuilt using the latest 1.6.13 version?

Yes, that's possible. However, you can do this yourself by modifying the
SPEC file in Github and providing a pull-request.

+1

Pull requests are highly appreciated. I know we are far behind
processing them, but the day will come... :-/

["Germán Andrés Pulido F."]

Hi!

libupnp has been on version 1.6.6 so long, and the current version is
the 1.6.13. I downloaded the spec file from
https://raw.github.com/repoforge/rpms/master/specs/libupnp/libupnp.spec,
changed the version (from 1.6.6 to 1.6.13) and rebuilt the package
successfully on Centos 6.0 both 32 and 64 bits. Can this package be
rebuilt using the latest 1.6.13 version?

Thanks!

[Dag Wieers]

Post by "Germán Andrés Pulido F."
libupnp has been on version 1.6.6 so long, and the current version is
the 1.6.13. I downloaded the spec file from
https://raw.github.com/repoforge/rpms/master/specs/libupnp/libupnp.spec,
changed the version (from 1.6.6 to 1.6.13) and rebuilt the package
successfully on Centos 6.0 both 32 and 64 bits. Can this package be
rebuilt using the latest 1.6.13 version?

Yes, that's possible. However, you can do this yourself by modifying the
SPEC file in Github and providing a pull-request.

More information is available from:

http://github.com/repoforge

Thanks for the feedback !