Re: Name of a binary package according to sonames
On Sun, Dec 17, 2006 at 06:07:18PM -0400, Jose Luis Rivas Contreras wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm maintaining libtorrent package, this source builds 2 binaries, libtorrent-rakshasa (is libtorrent9 last version in debian archive) and libtorrent-rakshasa-dev (is libtorrent9 last version in debian archive), I get this warning from lintian when I build the package. Now running lintian... W: libtorrent-rakshasa: package-name-doesnt-match-sonames libtorrent10 Finished running lintian. The version I'm building is libtorrent-0.11.0 so I don't think I should call the binary libtorrent10. Please check the real soname with objdump -p libtorrent-0.11.0 |grep SONAME Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kurt Roeckx escribió: On Sun, Dec 17, 2006 at 06:07:18PM -0400, Jose Luis Rivas Contreras wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm maintaining libtorrent package, this source builds 2 binaries, libtorrent-rakshasa (is libtorrent9 last version in debian archive) and libtorrent-rakshasa-dev (is libtorrent9 last version in debian archive), I get this warning from lintian when I build the package. Now running lintian... W: libtorrent-rakshasa: package-name-doesnt-match-sonames libtorrent10 Finished running lintian. The version I'm building is libtorrent-0.11.0 so I don't think I should call the binary libtorrent10. Please check the real soname with objdump -p libtorrent-0.11.0 |grep SONAME The real soname is libtorrent.so.10 So, should I name it libtorrent10? - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFhrBZOKCtW8rKsRgRAneOAJ94txj+uSnxu4NWWF+nB3+ZzHT4ZQCfQnM4 8WYy9Hb8+jyzwpbjzIo09qw= =zZr/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
On Mon, Dec 18, 2006 at 11:14:33AM -0400, Jose Luis Rivas Contreras wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Dec 17, 2006 at 06:07:18PM -0400, Jose Luis Rivas Contreras wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm maintaining libtorrent package, this source builds 2 binaries, libtorrent-rakshasa (is libtorrent9 last version in debian archive) and libtorrent-rakshasa-dev (is libtorrent9 last version in debian archive), I get this warning from lintian when I build the package. Now running lintian... W: libtorrent-rakshasa: package-name-doesnt-match-sonames libtorrent10 Finished running lintian. The version I'm building is libtorrent-0.11.0 so I don't think I should call the binary libtorrent10. Please check the real soname with objdump -p libtorrent-0.11.0 |grep SONAME The real soname is libtorrent.so.10 So, should I name it libtorrent10? Either the soname should be libtorrent.so.11, or you might want to rename libtorrent-0.11.0 to libtorrent-0.10.0 or something. If the soname really is and should be libtorrent.so.10, you want to name it libtorrent-rakshasa10 or something. But it should have the 10 in it. From what I understand there are 2 incompatible libtorrent packages, so you want to reflect that in the name of the package. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kurt Roeckx escribió: On Mon, Dec 18, 2006 at 11:14:33AM -0400, Jose Luis Rivas Contreras wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Dec 17, 2006 at 06:07:18PM -0400, Jose Luis Rivas Contreras wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm maintaining libtorrent package, this source builds 2 binaries, libtorrent-rakshasa (is libtorrent9 last version in debian archive) and libtorrent-rakshasa-dev (is libtorrent9 last version in debian archive), I get this warning from lintian when I build the package. Now running lintian... W: libtorrent-rakshasa: package-name-doesnt-match-sonames libtorrent10 Finished running lintian. The version I'm building is libtorrent-0.11.0 so I don't think I should call the binary libtorrent10. Please check the real soname with objdump -p libtorrent-0.11.0 |grep SONAME The real soname is libtorrent.so.10 So, should I name it libtorrent10? Either the soname should be libtorrent.so.11, or you might want to rename libtorrent-0.11.0 to libtorrent-0.10.0 or something. I can't that version already pass... If the soname really is and should be libtorrent.so.10, you want to name it libtorrent-rakshasa10 or something. But it should have the 10 in it. Ok, so I'm renaming the package to libtorrent10-rakshasa and -dev. From what I understand there are 2 incompatible libtorrent packages, so you want to reflect that in the name of the package. Yes, there's libtorrent-rasterbar (in a RFP, but I want to avoid problems in a near future), my packages were libtorrent9 and libtorrent9-dev, so I add to the name of the libraries -rakshasa to reflect that in the name. Thanks and Cheers!! - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFhr0pOKCtW8rKsRgRAr5zAJ4qLKHfOrr9fe3C2lcJpU4F62KkTgCg0eMF UGHUzA0TBliBAp4kbZTrj+0= =ZJAe -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
On Mon, Dec 18, 2006 at 12:09:13PM -0400, Jose Luis Rivas Contreras wrote: The version I'm building is libtorrent-0.11.0 so I don't think I should call the binary libtorrent10. Please check the real soname with objdump -p libtorrent-0.11.0 |grep SONAME The real soname is libtorrent.so.10 So, should I name it libtorrent10? Either the soname should be libtorrent.so.11, or you might want to rename libtorrent-0.11.0 to libtorrent-0.10.0 or something. I can't that version already pass... If the soname is set to libtorrent.so.10, it means applications will start to look for a file called /usr/lib/libtorrent.so.10. That will probably be a symlink in your case to libtorrent-0.11.0, which looks rather confusing to me. In libtorrent9 you have a file called /usr/lib/libtorrent.so.9. But there doesn't seem to be a file named libtorrent-0.9.0.so or something, so I'm a little confused what changed. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kurt Roeckx escribió: On Mon, Dec 18, 2006 at 12:09:13PM -0400, Jose Luis Rivas Contreras wrote: The version I'm building is libtorrent-0.11.0 so I don't think I should call the binary libtorrent10. Please check the real soname with objdump -p libtorrent-0.11.0 |grep SONAME The real soname is libtorrent.so.10 So, should I name it libtorrent10? Either the soname should be libtorrent.so.11, or you might want to rename libtorrent-0.11.0 to libtorrent-0.10.0 or something. I can't that version already pass... If the soname is set to libtorrent.so.10, it means applications will start to look for a file called /usr/lib/libtorrent.so.10. That will probably be a symlink in your case to libtorrent-0.11.0, which looks rather confusing to me. In libtorrent9 you have a file called /usr/lib/libtorrent.so.9. But there doesn't seem to be a file named libtorrent-0.9.0.so or something, so I'm a little confused what changed. No, there's only libtorrent.so.10 libtorrent.so.10.0.0 in my build (libtorrent-0.11.0) I'm more confused since I renamed the package to libtorrent10-rakshasa and libtorrent-rakshasa10 and lintian keeps giving me the warning... Jose - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFhsdYOKCtW8rKsRgRAg2iAKCqVE6x7lYUQoSKGvBsUrA4q4kdwgCfVRZ/ SRiDJbmdP0TU7pDbvE1Tbkc= =oOay -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
Jose Luis Rivas Contreras wrote: I'm more confused since I renamed the package to libtorrent10-rakshasa and libtorrent-rakshasa10 and lintian keeps giving me the warning... I am giving a try at the rasterbar's library, and ran into the same issue. I asked on #debian-mentors and they told me that a lintian override was needed in that case. -- Felipe Sateler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
On Mon, Dec 18, 2006 at 12:52:40PM -0400, Jose Luis Rivas Contreras wrote: If the soname is set to libtorrent.so.10, it means applications will start to look for a file called /usr/lib/libtorrent.so.10. That will probably be a symlink in your case to libtorrent-0.11.0, which looks rather confusing to me. In libtorrent9 you have a file called /usr/lib/libtorrent.so.9. But there doesn't seem to be a file named libtorrent-0.9.0.so or something, so I'm a little confused what changed. No, there's only libtorrent.so.10 libtorrent.so.10.0.0 in my build (libtorrent-0.11.0) So, your source package is libtorrent version is 0.11.0, which has a binary package libtorrent10-rakshasa with a library called libtorrent.so.10, and also has that soname. That all looks good. I'm more confused since I renamed the package to libtorrent10-rakshasa and libtorrent-rakshasa10 and lintian keeps giving me the warning... I think in this case you can probably ignore the warning. Do you conflict with the -dev package of the other libtorrent package? You'll both want to have a /usr/lib/libtorrent.so, so you should conflict. You probably now don't have a conflict with other library package now, but at some point this might happen. And I think this should be avoided. I think either one or both should really change the name of the library itself, to avoid all confusion, and also make them not conflict. For instance, you could name it librakshasatorrent (or librtorrent). The ideal solution would be that there really was only 1 libtorrent package, and that both current of them worked on 1 library. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kurt Roeckx escribió: On Mon, Dec 18, 2006 at 12:52:40PM -0400, Jose Luis Rivas Contreras wrote: If the soname is set to libtorrent.so.10, it means applications will start to look for a file called /usr/lib/libtorrent.so.10. That will probably be a symlink in your case to libtorrent-0.11.0, which looks rather confusing to me. In libtorrent9 you have a file called /usr/lib/libtorrent.so.9. But there doesn't seem to be a file named libtorrent-0.9.0.so or something, so I'm a little confused what changed. No, there's only libtorrent.so.10 libtorrent.so.10.0.0 in my build (libtorrent-0.11.0) So, your source package is libtorrent version is 0.11.0, which has a binary package libtorrent10-rakshasa with a library called libtorrent.so.10, and also has that soname. Yes That all looks good. I'm more confused since I renamed the package to libtorrent10-rakshasa and libtorrent-rakshasa10 and lintian keeps giving me the warning... I think in this case you can probably ignore the warning. Do you conflict with the -dev package of the other libtorrent package? You'll both want to have a /usr/lib/libtorrent.so, so you should conflict. - -dev is used just for building rtorrent and -dev needs libtorrent-rakshasa so if I conflict them -dev can't build. You probably now don't have a conflict with other library package now, but at some point this might happen. And I think this should be avoided. I think either one or both should really change the name of the library itself, to avoid all confusion, and also make them not conflict. For instance, you could name it librakshasatorrent (or librtorrent). Well, the one with rasterbar will name it libtorrent-rasterbar and I will name the library libtorrent-rakshasa, so, I think there's no conflict. The ideal solution would be that there really was only 1 libtorrent package, and that both current of them worked on 1 library. Well, rakshasa is used by rtorrent, and rasterbar is used by another bittorrent clients. Kurt Thanks!! Jose - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFh1C2OKCtW8rKsRgRAkYVAJ4rDfVvgxvmuaJ6ueZ12nj2KtRHIACg0l+l dEBZkTiLNTrVxh5fJ6ywrZ4= =eh+/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Felipe Sateler escribió: Jose Luis Rivas Contreras wrote: I'm more confused since I renamed the package to libtorrent10-rakshasa and libtorrent-rakshasa10 and lintian keeps giving me the warning... I am giving a try at the rasterbar's library, and ran into the same issue. I asked on #debian-mentors and they told me that a lintian override was needed in that case. Yes, that's what I will do, that's the only solution. :/ Thanks!! Jose - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFh1DsOKCtW8rKsRgRAhc2AKCDCWD4D6e10hakmlcMIZKjwP9J8ACgluAq n0s71KCyvGLfYb8BSlEmFcY= =cUuJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
On Sun, Dec 17, 2006 at 06:07:18PM -0400, Jose Luis Rivas Contreras wrote: The version I'm building is libtorrent-0.11.0 so I don't think I should call the binary libtorrent10. Why not? The version of a library and its soname have seldomly anything to do with each other (and if so, it may be a sign that upstream doesn't understand the meaning of a soname). Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
