FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 03-14-2009, 08:52 AM
Jean-Yves Avenard
 
Default Forcing version on dependency, how?

Hi.

I'm trying to build a package so it depends on a specific version of a library.

I carefully read http://www.debian.org/doc/maint-guide/index.en.html

but didn't get the answer I was looking for.

In my debian/control file I have for a given package:
Depends: ${misc-depends}

Which will install all the dependencies as required ; however it
creates a dependency on a newer library I previously installed which
doesn't ship with the system. I know that my package will work with
the standard library.

Is there a way to force which version of the dependency is going to be
installed?
Like right now, my package automatically add a dependency to version
1.0.19 of the library, I want that dependency to be on version 1.0.17

The only way I've found so far is to remove ${misc-depends} and set
manually all the dependencies..
But obviously this isn't an ideal solution, as I could very easily
forget about a dependency in the future.

What I tried to do is in the debian/rules add:
dh_makeshlibs -a -V 'libname (>= 1.0.17)'

but this still generate a dependency as:
shlibs-depends=libartsc0 (>= 1.5.9), libname (>= 1.0.17), libname (>> 1.0.19)

Which I don't know how it will behave...

Is there a way to get the dependency to be automatically generated ;
as well as specifying a given version of a dependency?

Any help or recommendations would be greatly appreciated.

Thank you
Jean-Yves


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-14-2009, 08:57 AM
Adeodato Simó
 
Default Forcing version on dependency, how?

Hello, Jean-Yves.

Please mail your questions about packaging to debian-mentors@lists.debian.org.

--
- Are you sure we're good?
- Always.
-- Rory and Lorelai


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-14-2009, 09:11 AM
Jean-Yves Avenard
 
Default Forcing version on dependency, how?

2009/3/14 Adeodato Simó <dato@net.com.org.es>

Hello, Jean-Yves.



Please mail your questions about packaging to debian-mentors@lists.debian.org.



--

- Are you sure we're good?

- Always.

* * * *-- Rory and Lorelai




I'm not sure I like to classify as "newbie"
 
Old 03-14-2009, 09:31 AM
Vincent Danjean
 
Default Forcing version on dependency, how?

Jean-Yves Avenard wrote:
> 2009/3/14 Adeodato Simó <dato@net.com.org.es>
>
>> Hello, Jean-Yves.
>>
>> Please mail your questions about packaging to
>> debian-mentors@lists.debian.org.
>>
>> --
>> - Are you sure we're good?
>> - Always.
>> -- Rory and Lorelai
>>
>>
> I'm not sure I like to classify as "newbie"

I do not think that only "newbie" are on debian-mentors...

Read the docs about shlibs files and/or symbols files (for the library
package, not yours in your case)
Nevertheless, manually downgrading version in library dependencies must
only be done for private packages, not packages uploaded to debian.

Regards,
Vincent


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-15-2009, 07:28 AM
Raphael Hertzog
 
Default Forcing version on dependency, how?

Hello Jean-Yves,

On Sat, 14 Mar 2009, Jean-Yves Avenard wrote:
> 2009/3/14 Adeodato Simó <dato@net.com.org.es>
>
> > Hello, Jean-Yves.
> >
> > Please mail your questions about packaging to
> > debian-mentors@lists.debian.org.
>
> I'm not sure I like to classify as "newbie"

Everybody has stuff to learn but your mail made it clear that you had a
lot to learn yet about libraries and automatic dependencies:
- it's not ${miscepends} but ${shlibsepends}
- those are generated by dpkg-shlipdeps and its manual pages should give
you enough information to understand how they are generated
- automatic dependencies are handled by the libraries that provide them
and it's not a good idea to try to override them

The packaging manual is an entry point, it doesn't contain all the infos
that one should know.

Cheers,
--
Raphaėl Hertzog

Contribuez ą Debian et gagnez un cahier de l'admin Debian Lenny :
http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-15-2009, 08:22 AM
Jean-Yves Avenard
 
Default Forcing version on dependency, how?

Hi


2009/3/15 Raphael Hertzog <hertzog@debian.org>



Everybody has stuff to learn but your mail made it clear that you had a

lot to learn yet about libraries and automatic dependencies:
Thanks for letting me know. It would have been even better if you had provided an answer that actually help resolving my problem.

Luckily someone did, and recommended the use of pbuilder to build the packages so it doesn't rely on packages I installed locally.




- it's not ${miscepends} but ${shlibsepends}
I know it is. However, my packages are made using original ubuntu packages as a basis.

It is in those packages that they are using miscepends instead. Like the mythtv packages:

Example in debian/control

Package: mythtv-common
Architecture: allPre-Depends: pwgen
Depends: adduser, mysql-client, ttf-freefont, ${miscepends}
Suggests: mythtv-doc (= ${source:Version})

Which is why I copied this into my original mail.




The packaging manual is an entry point, it doesn't contain all the infos

that one should know.


Could you recommend a manual that do contain the required information?

Thank you
Jean-Yves
 
Old 03-15-2009, 02:20 PM
Raphael Hertzog
 
Default Forcing version on dependency, how?

Hi,

On Sun, 15 Mar 2009, Jean-Yves Avenard wrote:
> Thanks for letting me know. It would have been even better if you had
> provided an answer that actually help resolving my problem.

I did, I pointed you to dpkg-shlibdeps(1).

> Luckily someone did, and recommended the use of pbuilder to build the
> packages so it doesn't rely on packages I installed locally.

Well, that certainly doesn't answer your question about forcing
dependency.

BTW, in the dpkg-shlibdeps manual page, there are explanation about
debian/shlibs.local which lets you override the library dependency.
(This doesn't change anything about the fact that it is generally wrong to
do it though)

> > - it's not ${miscepends} but ${shlibsepends}
>
> I know it is. However, my packages are made using original ubuntu packages
> as a basis.

That doesn't change the problem at all. ${miscepends} is used by
various dh_* commands for example to add debconf dependencies but it
doesn't cover the library dependencies.

> It is in those packages that they are using miscepends instead. Like the
> mythtv packages:
> Example in debian/control
>
> Package: mythtv-common
> Architecture: allPre-Depends: pwgen
> Depends: adduser, mysql-client, ttf-freefont, ${miscepends}
> Suggests: mythtv-doc (= ${source:Version})

Surely an arch: all package doesn't end contain ELF binaries that could
depend on libraries ?

> > The packaging manual is an entry point, it doesn't contain all the infos
> > that one should know.
>
> Could you recommend a manual that do contain the required information?

There's no documentation that covers it all. The best is to read the
manual pages of all tools/commands that are used (directly or indirectly)
in the build process. At least you know what's happening and it's no more
a magical incantation.

Cheers,
--
Raphaėl Hertzog

Contribuez ą Debian et gagnez un cahier de l'admin Debian Lenny :
http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-18-2009, 12:00 AM
Gunnar Wolf
 
Default Forcing version on dependency, how?

Jean-Yves Avenard dijo [Sat, Mar 14, 2009 at 09:11:05PM +1100]:
> > Please mail your questions about packaging to
> > debian-mentors@lists.debian.org.
>
> I'm not sure I like to classify as "newbie"

It is not about classification - it is about the right place to ask
things, as otherwise we drown in cross-list or cross-topic
traffic. -mentors is the place to ask, even if you are the author of
dpkg.

Greetings,

--
Gunnar Wolf - gwolf@gwolf.org - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 02:42 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org