[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: gtkpod - build issue



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 22/04/2011 14:39, Etienne Millon wrote:
> Hello,
> 
> I offered my help so here it is :)

Thanks a lot! ;-)

>> Who is interested in helping, can find my build files at [1].
>> I started from scratch, meaning that I downloaded the source package
>> from sourceforge.net and merged it with the config files from "debian"
>> directory I got from the debian source package that djpig (Frank)
>> prepared for version 0.99.14, changing the things that needed to be updated.
> 
> This is a correct way to do it. However, be sure to check the
> differences between the two upstream versions. For example, if
> upstream ships new examples you should install them.

OK, I'll check.

> Also, if this is your first package, it may be a good idea to fix bugs
> in the current package (ie prepare 0.99.14-4), rather than preparing a
> new upstream version.

Should I? :-P I'm not so sure I could help solving bugs... but I've
never tried ;-)

>> Obviously, I decided to use quilt to patch the original source code and
>> modified the files in "debian" dir for that.
>> Build Dependencies have been tested in cowbuilder/pbuilder environment
>> and they're ok (or think so).
> 
> As you use the "3.0 (quilt)" format, you don't need to include quilt
> in your build-deps. This was needed before 3.0, when packages used
> quilt explicitly. In debian/rules, you should get rid of --with quilt
> too.

Before writing my "call for help", I tried to omit the quilt dependency
and the "--with quilt" option for debhelper but debuild didn't work in
the pbuilder environment, asking for it. And it seems the way to have
the source back unpatched, once I want to clean it (insted of doing it
manually via "quilt (or dquilt) pop -a".

Tried now... it works even without ;-) That's weird! :-(

>> Now, I'm having an issue with the final process, while dh_shlibdeps runs
>> (you can see it from the .build file attached). It says that it can't
>> find a library (libgtkpod) that is compiled during the build process.
>> The library is present where it's supposed to but no way to get
>> dh_shlibdeps understand it ;-)
>> I've tried many different solutions, but no one worked.
>>
>> If anyone could give me some helpful hints, it would be appreciated.
>> Any suggestion or advice on the package is really welcome.
>>
>> Thank you in advance.
> 
> I had a quick look at debian/control and have a few remarks :
> 
>   - the Vcs-* fields should point to where the packaging is done, not
>     to the upstream VCS.

OK, so I should wait to see the buildd environment, I guess... or am I
wrong?

>   - adding libgpod as an explicit dependency to gtkpod is not needed
>     as normally shlib:Depends should include it

Done.

>   - gtkpod-data should not depend on shlib:Depends (it contains only
>     images and stuff like that, nothing executable). I don't think
>     that python:Depends is necessary (the only python script is an
>     example).

Done.

> 
> As for the dh_shlibdeps problem : it complains about a missing
> libgtkpod (note : different from libgpod). I believe that it is
> because you don't install it (you took gtkpod.install directly from
> gtkpod_0.99.14).

I was wondering if it'd have a sense to split the libgtkpod from the
gtkpod package. Could that help?

> Hope that helps !

It did! But I (we) have to work a lot on this messy package ;-)

Hope to hear from you soon.

mfv
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)

iEYEARECAAYFAk22vIUACgkQ1t4DH5kfnS2mYgCcDUQA1ib/p+aH/F0nFmX2Oopf
M94AoKGWUJuRVj3xC+bAKqinfyec+0NV
=V30h
-----END PGP SIGNATURE-----

-- 
Il messaggio e' stato analizzato alla ricerca di virus o
contenuti pericolosi da MailScanner, ed e'
risultato non infetto.


Reply to: