On Tuesday 10 April 2001 00:38, Rick Macdonald wrote:
> On Mon, 9 Apr 2001, Chris Gray wrote:
> > On Mon, 09 Apr 2001, Colin Watson wrote:
> > > Mario Vukelic <[EMAIL PROTECTED]> wrote:
> > >>My locally generated debs, e.g. from kernel compiles, show up
> > >> as obsolete in dselect. Is there an ea
On Mon, Apr 09, 2001, Chris Gray wrote:
> On Mon, 09 Apr 2001, Colin Watson wrote:
> > Mario Vukelic <[EMAIL PROTECTED]> wrote:
> >>My locally generated debs, e.g. from kernel compiles, show up as
> >>obsolete in dselect. Is there an easy way to tell their locations to
> >>the package manager or do
> My locally generated debs, e.g. from kernel compiles, show up as
> obsolete in dselect. Is there an easy way to tell their locations to the
> package manager or do I have to mess with Packages.gz files and the
Generate local Packages.gz of your debs, eg, in my mirror I use:
dpkg-scanpackages di
On 09 Apr 2001 10:38:36 -0600, Rick Macdonald wrote:
> Then I would add this to sources.list:
>
> deb file:/usr/local/src/debian-local local/
It works now, except that the line needs to be
deb file:/usr/local/src/debian-local local local
with the given directory setup. Thanks again and sorry f
On 09 Apr 2001 20:08:26 +0200, Mario Vukelic wrote:
> Uuhm, I did this now and it generates a nice Packages.gz, but the debs
> still show up as obsolete ? (Yes, I did update)
I'm a moron, the deb line in sources.list was commented out. Sorry
--
I did not vote for the Austrian government
On 09 Apr 2001 10:38:36 -0600, Rick Macdonald wrote:
(...)
> Then I would add this to sources.list:
>
> deb file:/usr/local/src/debian-local local/
Uuhm, I did this now and it generates a nice Packages.gz, but the debs
still show up as obsolete ? (Yes, I did update)
--
I did not vote for the
On 09 Apr 2001 10:38:36 -0600, Rick Macdonald wrote:
> I used to put my local debs (kernels etc) into a directory
> (/usr/local/src/debian-local/dists/local/local/binary-i386)
> and then run this script:
>
> #!/bin/sh
> cd /usr/local/src/debian-local
> dpkg-scanpackages dists/local/local/binary-
Chris Gray <[EMAIL PROTECTED]> wrote:
>On Mon, 09 Apr 2001, Colin Watson wrote:
>> Mario Vukelic <[EMAIL PROTECTED]> wrote:
>>>My locally generated debs, e.g. from kernel compiles, show up as
>>>obsolete in dselect. Is there an easy way to tell their locations to
>>>the package manager or do I have
On Mon, 9 Apr 2001, Chris Gray wrote:
> On Mon, 09 Apr 2001, Colin Watson wrote:
> > Mario Vukelic <[EMAIL PROTECTED]> wrote:
> >>My locally generated debs, e.g. from kernel compiles, show up as
> >>obsolete in dselect. Is there an easy way to tell their locations to
> >>the package manager or do
On 09 Apr 2001 12:17:09 -0400, Chris Gray wrote:
> If I understand the question correctly, it seems the canonical answer
> is to raise the version number of the locally created package. This
> should keep dselect or apt from thinking that the local package is
> obsolete. You can change the versi
On Mon, 09 Apr 2001, Colin Watson wrote:
> Mario Vukelic <[EMAIL PROTECTED]> wrote:
>>My locally generated debs, e.g. from kernel compiles, show up as
>>obsolete in dselect. Is there an easy way to tell their locations to
>>the package manager or do I have to mess with Packages.gz files and
>>the l
Mario Vukelic <[EMAIL PROTECTED]> wrote:
>My locally generated debs, e.g. from kernel compiles, show up as
>obsolete in dselect. Is there an easy way to tell their locations to the
>package manager or do I have to mess with Packages.gz files and the
>like?
You pretty much have to mess with Package
Hi,
My locally generated debs, e.g. from kernel compiles, show up as
obsolete in dselect. Is there an easy way to tell their locations to the
package manager or do I have to mess with Packages.gz files and the
like?
Thanks for comments, M.
--
I did not vote for the Austrian government
13 matches
Mail list logo
