Re: Upgrading to a new upstream maintainer version

On Tue, 22.06.99 13:55 +0200, Sami Dalouche wrote: I've already packaged a deb of epkg but there's a new upstream maintainer version. Must I remake entirely the package or I have just to do anything that will keep the changelog... ? * unpack the new upstream version * then copy the debian

Re: Becoming a new developper

On Wed, 23 Jun 1999, Steve Haslam wrote: On Wed, Jun 23, 1999 at 05:04:02PM +0300, Antti-Juhani Kaijanaho wrote: On Wed, Jun 23, 1999 at 11:30:02AM +0200, Peter Makholm wrote: I assume that you allow gcc, but I will use ar, tar and gzip for the packaging. ar can't create .debs

Re: Becoming a new developper

On Wed, Jun 23, 1999 at 04:14:55PM +0100, Steve Haslam wrote: ar can't create .debs Er, why not? deb(5): Note that many modern versions of ar create archives with different magic numbers. Archives created in this way will not be recognised by dpkg-deb, though these

Re: Upgrading to a new upstream maintainer version

On Wed, Jun 23, 1999 at 12:53:30AM +0200, Christian Hammers wrote: On Tue, 22.06.99 13:55 +0200, Sami Dalouche wrote: I've already packaged a deb of epkg but there's a new upstream maintainer version. Must I remake entirely the package or I have just to do anything that will keep the

dpkg acts strange

Hi ! I like to use a coppled Replace: + Conflict: to replace a package with a another one with a different name. This works well - but only with ONE package. The second packet will not be considered to be removed by dpkg. Why ?! read you, -christian- -- Linux - the choice of the GNU

Re: dpkg acts strange

Christian Hammers [EMAIL PROTECTED] writes: I like to use a coppled Replace: + Conflict: to replace a package with a another one with a different name. This works well - but only with ONE package. The second packet will not be considered to be removed by dpkg. Why ?! Limitation of dpkg. --