[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: debian gnustep-base backport !
From: |
eric |
Subject: |
Re: debian gnustep-base backport ! |
Date: |
Wed, 23 Apr 2008 12:27:09 +0200 |
User-agent: |
Mozilla-Thunderbird 2.0.0.9 (X11/20080110) |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hubert Chathi a écrit :
> On Sun, 20 Apr 2008 21:45:39 +0200 eric <eric@collectifs.net> wrote:
>
>> I would like to backport 'gnustep-base-1.14.1-5' form debian/testing
>> to debian/etch but i have some trouble !
>
> [...]
>
>> < Build-Depends: debhelper (>= 5), gobjc, gnustep-make (>= 2.0.0),
>> libffcall1-dev [alpha amd64 hppa hurd-i386 i386 ia64 kfreebsd-amd64
>> kfreebsd-i386 knetbsd-i386 m68k mips mipsel powerpc ppc64 s390 sparc],
>> libffi4-dev [alpha amd64 arm armel armeb hppa hurd-i386 i386 ia64
>> kfreebsd-amd64 kfreebsd-i386 knetbsd-i386 m68k mips mipsel powerpc
>> ppc64 s390 sparc], libxml2-dev, libxslt1-dev, libssl-dev, zlib1g-dev,
>> m4, libkvm-dev [kfreebsd-i386 kfreebsd-amd64 knetbsd-i386]
>> - ---
>>> Build-Depends: debhelper (>= 5), gobjc (>= 4:4.1), gnustep-make (>=
>> 2.0.0), libffcall1-dev [alpha amd64 hppa hurd-i386 i386 ia64
>> kfreebsd-amd64 kfreebsd-i386 knetbsd-i386 m68k mips mipsel powerpc
>> ppc64 s390 sparc], libffi4-dev [alpha amd64 arm armel armeb hppa
>> hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 knetbsd-i386 m68k
>> mips mipsel powerpc ppc64 s390 sparc], libxml2-dev, libxslt1-dev,
>> libssl-dev, zlib1g-dev, m4, libkvm-dev [kfreebsd-i386 kfreebsd-amd64
>> knetbsd-i386] 80c80
>> < Depends: libgnustep-base1.14 (= ${binary:Version}),
>> gnustep-base-common, gnustep-base-runtime (>= ${source:Version}),
>> gnustep-make (>= 2.0.0), gobjc, ${shlibs:Depends}, ${misc:Depends}
>> - ---
>>> Depends: libgnustep-base1.14 (= ${binary:Version}),
>> gnustep-base-common, gnustep-base-runtime (>= ${source:Version}),
>> gnustep-make (>= 2.0.0), gobjc (>= 4:4.1), ${shlibs:Depends},
>> ${misc:Depends}
>> make: *** [test-control] Erreur 1
>
> The debian/control file is built from debian/control.m4, so any changes
> to dependencies, etc. should be made in debian/control.m4 (or to the
> variables in debian/rules). You then regenerate debian/control by
> running "debian/rules debian/control".
I'm not familiar with m4, but it works !
thanks
eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIDw795OIxjq5GfYERAs+oAJ9u7hEB9UngBbBsHzT2Xj5srirTRgCgmLYF
8xE5cdAg+nT2mFAPLY7R0gc=
=mFAw
-----END PGP SIGNATURE-----