Re: Re: dpkg-scanpackages problem

> You should delete the old .debs and only leave the most > current versions > in the archive, if I recall correctly. OK, i can do that, but the strange thing is that dpkg-scanpackage was generating the Packages.gz with the newest version, with more than one version of the debs. Hereward

Re: dpkg-scanpackages problem

You should delete the old .debs and only leave the most current versions in the archive, if I recall correctly. On Mon, Aug 27, 2001 at 07:26:51PM +, Hereward Cooper wrote: > Hi, > > I'm managed to generate a Packages.gz file for my two packages, > but recentlly (last couple of hours) when I

Re: Re: dpkg-scanpackages problem

> You should delete the old .debs and only leave the most > current versions > in the archive, if I recall correctly. OK, i can do that, but the strange thing is that dpkg-scanpackage was generating the Packages.gz with the newest version, with more than one version of the debs. Hereward -- T

Re: dpkg-scanpackages problem

You should delete the old .debs and only leave the most current versions in the archive, if I recall correctly. On Mon, Aug 27, 2001 at 07:26:51PM +, Hereward Cooper wrote: > Hi, > > I'm managed to generate a Packages.gz file for my two packages, > but recentlly (last couple of hours) when I

dpkg-scanpackages problem

Hi, I'm managed to generate a Packages.gz file for my two packages, but recentlly (last couple of hours) when I updated the package version to 1.0.4-4 inorder to fix some bugs I get the problem that the generated Packages.gz doesn't contain the newest version, instead the oldest (1.0.4-1). #

dpkg-scanpackages problem

Hi, I'm managed to generate a Packages.gz file for my two packages, but recentlly (last couple of hours) when I updated the package version to 1.0.4-4 inorder to fix some bugs I get the problem that the generated Packages.gz doesn't contain the newest version, instead the oldest (1.0.4-1). #