Le Thu, Jul 22, 2010 at 10:13:40AM +0200, Mike Hommey a écrit :
>
> Build-Depends-Indep are used to build arch: all stuff only and are not
> installed on buildds, but in your case, the jdk is necessary to build
> arch: any stuff.
>
> Now, you obviously have another bug, that is that --with-java i
techroot’, but it failed on all buildds when running
> >> dh_makeshlibs.
> >>
> >> dh_makeshlibs: dpkg-gensymbols -plibajax6 -Idebian/libajax6.symbols
> >> -Pdebian/libajax6 returned exit code 1
> >>
> >> See for instance:
> >> https://
Le Thu, Jul 22, 2010 at 02:10:53AM +0200, Jakub Wilk a écrit :
> * Charles Plessy , 2010-07-22, 08:41:
>> I uploaded a package that built fine in a chroot made by the helper
>> tool ‘sbuild-createchroot’, but it failed on all buildds when running
>> dh_makeshlibs.
>
* Charles Plessy , 2010-07-22, 08:41:
I uploaded a package that built fine in a chroot made by the helper
tool ‘sbuild-createchroot’, but it failed on all buildds when running
dh_makeshlibs.
dh_makeshlibs: dpkg-gensymbols -plibajax6 -Idebian/libajax6.symbols
-Pdebian/libajax6 returned exit
Dear all,
I uploaded a package that built fine in a chroot made by the helper tool
‘sbuild-createchroot’, but it failed on all buildds when running dh_makeshlibs.
dh_makeshlibs: dpkg-gensymbols -plibajax6 -Idebian/libajax6.symbols
-Pdebian/libajax6 returned exit code 1
See for instance:
https
On Fri, Jul 02, 2004 at 09:47:26PM -0700, Matt Zimmerman wrote:
> dh_shlibdeps (via dpkg-shlibdeps) uses information that the library
> maintainer provided (the shlibs file) to determine the appropriate
> dependency. This mechanism is documented in the policy manual.
Good answer. Got it. (What
On Fri, Jul 02, 2004 at 08:48:39PM -0700, William Ballard wrote:
> On Fri, Jul 02, 2004 at 03:25:06PM -0700, Matt Zimmerman wrote:
> > On Fri, Jul 02, 2004 at 11:57:38AM -0700, William Ballard wrote:
> >
> > > Notice libfam0c102 isn't coming in with a version dependency. Is there
> > > to make
On Fri, Jul 02, 2004 at 03:25:06PM -0700, Matt Zimmerman wrote:
> On Fri, Jul 02, 2004 at 11:57:38AM -0700, William Ballard wrote:
>
> > Notice libfam0c102 isn't coming in with a version dependency. Is there
> > to make dh_shlibdeps add that in?
>
> No. Why do you believe that you need to?
I
On Fri, Jul 02, 2004 at 09:47:26PM -0700, Matt Zimmerman wrote:
> dh_shlibdeps (via dpkg-shlibdeps) uses information that the library
> maintainer provided (the shlibs file) to determine the appropriate
> dependency. This mechanism is documented in the policy manual.
Good answer. Got it. (What
On Fri, Jul 02, 2004 at 08:48:39PM -0700, William Ballard wrote:
> On Fri, Jul 02, 2004 at 03:25:06PM -0700, Matt Zimmerman wrote:
> > On Fri, Jul 02, 2004 at 11:57:38AM -0700, William Ballard wrote:
> >
> > > Notice libfam0c102 isn't coming in with a version dependency. Is there
> > > to make
On Fri, Jul 02, 2004 at 03:25:06PM -0700, Matt Zimmerman wrote:
> On Fri, Jul 02, 2004 at 11:57:38AM -0700, William Ballard wrote:
>
> > Notice libfam0c102 isn't coming in with a version dependency. Is there
> > to make dh_shlibdeps add that in?
>
> No. Why do you believe that you need to?
I
On Fri, Jul 02, 2004 at 11:57:38AM -0700, William Ballard wrote:
> Notice libfam0c102 isn't coming in with a version dependency. Is there
> to make dh_shlibdeps add that in?
No. Why do you believe that you need to?
--
- mdz
On Fri, Jul 02, 2004 at 11:57:38AM -0700, William Ballard wrote:
> Notice libfam0c102 isn't coming in with a version dependency. Is there
> to make dh_shlibdeps add that in?
No. Why do you believe that you need to?
--
- mdz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Fam isn't configurable via pkg-config, but I put it in configure.ac
via a call to AC_CHECK_LIB(fam,main) [1].
In debian/rules I call dh_shlibdeps but not dh_makeshlibs, and I end up
with these substvars:
shlibs:Depends=libart-2.0-2 (>= 2.3.16), libatk1.0-0 (>= 1.6.0), libc6
(>
Fam isn't configurable via pkg-config, but I put it in configure.ac
via a call to AC_CHECK_LIB(fam,main) [1].
In debian/rules I call dh_shlibdeps but not dh_makeshlibs, and I end up
with these substvars:
shlibs:Depends=libart-2.0-2 (>= 2.3.16), libatk1.0-0 (>= 1.6.0), libc6
(>
matze <[EMAIL PROTECTED]> writes:
> the package (kbiff - biff clone for kde) contains a
> shared library named kbiff.so which is installed in /usr/lib. dh_makeshlibs
> doesn't create the shlibs file and so i patched dh_makeshlibs to know why. it
> seems, that the scri
matze <[EMAIL PROTECTED]> writes:
> the package (kbiff - biff clone for kde) contains a
> shared library named kbiff.so which is installed in /usr/lib. dh_makeshlibs
> doesn't create the shlibs file and so i patched dh_makeshlibs to know why. it
> seems, that the scri
hi,
i'm trying to create my first package and like the most beginners i'm
encountering problems. the package (kbiff - biff clone for kde) contains a
shared library named kbiff.so which is installed in /usr/lib. dh_makeshlibs
doesn't create the shlibs file and so i patched dh_mak
hi,
i'm trying to create my first package and like the most beginners i'm
encountering problems. the package (kbiff - biff clone for kde) contains a
shared library named kbiff.so which is installed in /usr/lib. dh_makeshlibs
doesn't create the shlibs file and so i patched d
Viral <[EMAIL PROTECTED]> wrote:
>dh_makeshlibs puts ldconfig in postinst and postrm.
>However, lintian complains about ldconfig being run from postrm, and refers
>to ch. 9 of the policy.
>
>What am I missing here, or is it only applicable to a specific case ?
You're m
Viral <[EMAIL PROTECTED]> wrote:
>dh_makeshlibs puts ldconfig in postinst and postrm.
>However, lintian complains about ldconfig being run from postrm, and refers
>to ch. 9 of the policy.
>
>What am I missing here, or is it only applicable to a specific case ?
You're m
Hi,
dh_makeshlibs puts ldconfig in postinst and postrm.
However, lintian complains about ldconfig being run from postrm, and refers
to ch. 9 of the policy.
What am I missing here, or is it only applicable to a specific case ?
Thanks,
viral
--
Every year is getting shorter, never seem to find
Hi,
dh_makeshlibs puts ldconfig in postinst and postrm.
However, lintian complains about ldconfig being run from postrm, and refers
to ch. 9 of the policy.
What am I missing here, or is it only applicable to a specific case ?
Thanks,
viral
--
Every year is getting shorter, never seem to
23 matches
Mail list logo
