Bug#575195: opal should build-depend on libsrtp-dev, and libopal-dev should depend on libsrtp0-dev
On Saturday 15 May 2010 07:22:55 Eugen Dedu wrote: I still do not understand, could you please elaborate? On the system where libopal is linked to srtp, libopal-dev too uses srtp. Opal .debs get built on a machine (user, binNMU, buildd) with srtp-dev installed. These .debs then get installed on a machine without srtp-dev. You would be surprised how often this can occur. No deps automatically pull in srtp libs. User then builds an application with opal, however as srpt is missing build fails, both headers and libs... Options: 1. Make explicit Build-Depends: libsrtp-dev, then it is expected that all .debs will include depends, and when the package above are installed they srtp deps will be pulled in. packages are working as expected... 2. Make explicit Build-Conflicts: libsrtp-dev, then it is expected that all .debs will not depend on srtp. If a user wants to include srtp support, then they need to change the package configuration and we can claim it is unsupported. Thus the recommend that we go for option 1. Mark signature.asc Description: This is a digitally signed message part.
Bug#575195: opal should build-depend on libsrtp-dev, and libopal-dev should depend on libsrtp0-dev
On Sat, May 15, 2010 at 08:03:25PM +1000, Mark Purcell wrote: On Saturday 15 May 2010 07:22:55 Eugen Dedu wrote: I still do not understand, could you please elaborate? On the system where libopal is linked to srtp, libopal-dev too uses srtp. Opal .debs get built on a machine (user, binNMU, buildd) with srtp-dev installed. These .debs then get installed on a machine without srtp-dev. You would be surprised how often this can occur. No deps automatically pull in srtp libs. User then builds an application with opal, however as srpt is missing build fails, both headers and libs... Options: 1. Make explicit Build-Depends: libsrtp-dev, then it is expected that all .debs will include depends, and when the package above are installed they srtp deps will be pulled in. packages are working as expected... 2. Make explicit Build-Conflicts: libsrtp-dev, then it is expected that all .debs will not depend on srtp. If a user wants to include srtp support, then they need to change the package configuration and we can claim it is unsupported. A slight clarification (or correct me if in fact you meant something else, Mark): Option 1: Have _source_ package build-depend on AND _binary_ *-dev package _depend_ on libsrtp-dev. And do this Option 2) Have _source_ package build-conflict with libsrtp-dev. Since libsrtp only builds on some architectures, option 1 really means add those package relations only on relevant archs. The safest is then to build-conflict on negated list of supported archs, but if that feels too complex to handle, I guess that part can be skipped. I recommend using d-shlibs to auto-resolve the binary relation! Thus the recommend that we go for option 1. I (obviously) agree, since that was the very point of packaging libsrtp :-) - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#575195: opal should build-depend on libsrtp-dev, and libopal-dev should depend on libsrtp0-dev
On 15/05/10 12:03, Mark Purcell wrote: On Saturday 15 May 2010 07:22:55 Eugen Dedu wrote: I still do not understand, could you please elaborate? On the system where libopal is linked to srtp, libopal-dev too uses srtp. Opal .debs get built on a machine (user, binNMU, buildd) with srtp-dev installed. Many people do this error, I do not understand why. Only source packages must be uploaded, not binary ones!! Moreover, the binary packages must be created in pbuilder, not in packager's or user's day-to-day partition!! About one year ago there was a post on debian lists giving this as a recommandation, I do not know how this was continued. This solves all the problems. These .debs then get installed on a machine without srtp-dev. You would be surprised how often this can occur. No deps automatically pull in srtp libs. User then builds an application with opal, however as srpt is missing build fails, both headers and libs... Libraries are automatically added in build-depends. Only the header might be missing. Options: 1. Make explicit Build-Depends: libsrtp-dev, then it is expected that all .debs will include depends, and when the package above are installed they srtp deps will be pulled in. packages are working as expected... 2. Make explicit Build-Conflicts: libsrtp-dev, then it is expected that all .debs will not depend on srtp. If a user wants to include srtp support, then they need to change the package configuration and we can claim it is unsupported. Thus the recommend that we go for option 1. Mark -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575195: opal should build-depend on libsrtp-dev, and libopal-dev should depend on libsrtp0-dev
On 05/04/10 23:30, Jonas Smedegaard wrote: On Wed, Mar 24, 2010 at 08:35:03AM +0100, Jonas Smedegaard wrote: As subject says, the source package opal should build-depend on virtual package libsrtp-dev, and the binary package libopal-dev should depend on the actual implementation of it, libopal0-dev. Above should be done only for archs for which srtp is actually packaged - on other archs it is recommended to instead conflict with the virtual libsrtp-dev, although this only is of severity minor (it gets severity normal if/when libsrtp gets support for those other archs at a later point in time). srtp is currently packaged on the following archs: alpha amd64 armel hppa i386 mips mipsel powerpc s390 The reason for this, and for this bugreport not being severity wishlist, is that opal automagically recognize an installed srtp so may accidentally link against it, rendering the libopal-dev package broken, as it then must depend on headers of the used library. If for some odd reason there is no interest in the use of srtp at all, then the opal build process might have an option no explicitly avoid it, which should then be used. I do not understand what is the problem when on someone's machine libsrtp-dev is installed. opal will compile with srtp support. Could you explain the problem? (opal does not have a flag to disable-srtp.) -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575195: opal should build-depend on libsrtp-dev, and libopal-dev should depend on libsrtp0-dev
On Tue, Apr 06, 2010 at 08:23:46AM +1000, Mark Purcell wrote: On Tuesday 06 April 2010 07:30:21 Jonas Smedegaard wrote: On Wed, Mar 24, 2010 at 08:35:03AM +0100, Jonas Smedegaard wrote: As subject says, the source package opal should build-depend on virtual package libsrtp-dev, and the binary package libopal-dev should depend on the actual implementation of it, libopal0-dev. Jonas, Thanks for the report. Will include with the next upload of opal. Excellent! :-) - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#575195: opal should build-depend on libsrtp-dev, and libopal-dev should depend on libsrtp0-dev
On Wed, Mar 24, 2010 at 08:35:03AM +0100, Jonas Smedegaard wrote: As subject says, the source package opal should build-depend on virtual package libsrtp-dev, and the binary package libopal-dev should depend on the actual implementation of it, libopal0-dev. Above should be done only for archs for which srtp is actually packaged - on other archs it is recommended to instead conflict with the virtual libsrtp-dev, although this only is of severity minor (it gets severity normal if/when libsrtp gets support for those other archs at a later point in time). srtp is currently packaged on the following archs: alpha amd64 armel hppa i386 mips mipsel powerpc s390 The reason for this, and for this bugreport not being severity wishlist, is that opal automagically recognize an installed srtp so may accidentally link against it, rendering the libopal-dev package broken, as it then must depend on headers of the used library. If for some odd reason there is no interest in the use of srtp at all, then the opal build process might have an option no explicitly avoid it, which should then be used. Ping -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#575195: opal should build-depend on libsrtp-dev, and libopal-dev should depend on libsrtp0-dev
On Tuesday 06 April 2010 07:30:21 Jonas Smedegaard wrote: On Wed, Mar 24, 2010 at 08:35:03AM +0100, Jonas Smedegaard wrote: As subject says, the source package opal should build-depend on virtual package libsrtp-dev, and the binary package libopal-dev should depend on the actual implementation of it, libopal0-dev. Jonas, Thanks for the report. Will include with the next upload of opal. Mark signature.asc Description: This is a digitally signed message part.
Bug#575195: opal should build-depend on libsrtp-dev, and libopal-dev should depend on libsrtp0-dev
Package: opal Version: 3.6.6~dfsg-4 Severity: normal Hi, As subject says, the source package opal should build-depend on virtual package libsrtp-dev, and the binary package libopal-dev should depend on the actual implementation of it, libopal0-dev. Above should be done only for archs for which srtp is actually packaged - on other archs it is recommended to instead conflict with the virtual libsrtp-dev, although this only is of severity minor (it gets severity normal if/when libsrtp gets support for those other archs at a later point in time). srtp is currently packaged on the following archs: alpha amd64 armel hppa i386 mips mipsel powerpc s390 The reason for this, and for this bugreport not being severity wishlist, is that opal automagically recognize an installed srtp so may accidentally link against it, rendering the libopal-dev package broken, as it then must depend on headers of the used library. If for some odd reason there is no interest in the use of srtp at all, then the opal build process might have an option no explicitly avoid it, which should then be used. Kind regards, - Jonas -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-12-generic (SMP w/2 CPU cores) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
