Re: Lying to dpkg?

[cjw44@cam.ac.uk (Colin Watson)]

d4jonas@dtek.chalmers.se (Jonas Steverud) wrote:
>cjw44@cam.ac.uk (Colin Watson) writes:
>
>> d4jonas@dtek.chalmers.se (Jonas Steverud) wrote:
>[...]
>> >The only problem with this is dselect will tell you the packages made
>> >by equivs are obsolete - but I maybe did some wrong when I deleted the
>> >.debs? Anyone who knows?
>> 
>> Obsolete/local, strictly: it's the "local" bit that's relevant to you.
>> You can safely ignore this, but if you recreate the .debs and run 'dpkg
>> -A package.deb' then I believe they'll be recorded in the available file
>> and therefore not listed as local.
>
>But it will still list the package as obsolete, right?

"not listed as obsolete/local", I should have said. But ...

>I mean, the ftpserver will not list it as available and if I'm not
>misstaken dselect then thinks it's obsolete.
>
>The issue isn't that very great, it's just a minor source for
>irritation - and only sometimes - and I was mostly curious wheather
>there was something I've overlooked.

Ah ... indeed, you're right; now that I've tried it, it works right up
to an update. In that case you might want to investigate setting up your
own private repository of packages using dpkg-scanpackages; it's not too
difficult to do with a bit of trial and error. I'm happy to help you
with this if you have problems.

-- 
Colin Watson                                           [cjw44@cam.ac.uk]