> George Danchev writes:
> > dh sequencer also calls dh_installdebconf earlier in the call sequence
> > (which Frank's rules was actually missing), which takes care to create
> > debian/pkg/DEBIAN/ directory. So, when dh_makeshlibs and dh_shlibdeps
> > enter the scene, we have valid package direct
George Danchev writes:
> dh sequencer also calls dh_installdebconf earlier in the call sequence
> (which Frank's rules was actually missing), which takes care to create
> debian/pkg/DEBIAN/ directory. So, when dh_makeshlibs and dh_shlibdeps
> enter the scene, we have valid package directories, as
> Frank Küster writes:
> > Maybe some other tool "usually" also creates DEBIAN, but not in my case?
>
> I'm really confused by this too, since the calling sequence for a binary
> build also runs dh_makeshlibs before running dh_installdeb,
> dh_makeshlibs seems to assume that the DEBIAN directory a
Frank Küster writes:
> Maybe some other tool "usually" also creates DEBIAN, but not in my case?
I'm really confused by this too, since the calling sequence for a binary
build also runs dh_makeshlibs before running dh_installdeb,
dh_makeshlibs seems to assume that the DEBIAN directory already exi
Russ Allbery wrote:
> Frank Küster writes:
>
>> No, I've found out now (Use the source, conveniently dpkg-shlibdeps is
>> a Perl script): I was the DEBIAN directory in the package directory
>> which was missing, and which made dpkg-shlibdeps _think_ that it
>> wasn't a package directory.
>>
>> S
Frank Küster writes:
> No, I've found out now (Use the source, conveniently dpkg-shlibdeps is
> a Perl script): I was the DEBIAN directory in the package directory
> which was missing, and which made dpkg-shlibdeps _think_ that it
> wasn't a package directory.
>
> Simply calling dh_installdeb bef
George Danchev wrote:
>> However, the files are already installed where they should be
>> IMO. Running dh_shlibdeps with -v gives
>>
[...]
> Are you sure that these binaries are already installed in debian// and
> that dpkg-shlibdeps gets called after that, i.e. not before they are in
> place.
> Hi,
Hi,
> in a new upstream version which I'm working on, I get warnings from
> dpkg-shlibdeps which I don't understand. And I can't find a way to find
> out, so I'm asking here.
>
> The warnings are multiple occurrences of
>
> dpkg-shlibdeps: warning: binaries to analyze should already be inst
Hi,
in a new upstream version which I'm working on, I get warnings from
dpkg-shlibdeps which I don't understand. And I can't find a way to find
out, so I'm asking here.
The warnings are multiple occurrences of
dpkg-shlibdeps: warning: binaries to analyze should already be installed in
their pa
9 matches
Mail list logo
