On Fri, Feb 29, 2008 at 11:50:19AM +0100, Hilmar Preusse wrote:
> dlocate actually depends on findutils (<< 4.2.31-2).

no, it depends on 'locate | findutils (<< 4.2.31-2)'

> [...]
> Depends: dctrl-tools | grep-dctrl (>= 0.11), dpkg (>= 1.8.0), locate | 
> findutils (<< 4.2.31-2), perl
> [...]
> 
> The version in unstable/testing however is 4.2.33-1 resp. 4.2.32-1, which
> makes your package uninstallable. No, findutils can't be removed, as it is
> essential.

could you show an example?

dlocate depends on either 'locate' or 'findutils (<< 4.2.31-2)'. that
was changed recently (Dec 2007) because locate & frcode were split out
from the findutils package into a separate package called 'locate'.

to put it another way: dlocate actually depends on the frcode program.
frcode used to be in findutils package (<< 4.2.31-2), but is now in the
locate package.


so, either the 'locate' package or 'findutils <<4.2.31-2' will satisfy
the dependancy.

see Bug #453952 for more details.


btw, what are you using? apt-get? aptitude? if you're describing an
actual event rather than just theory, try with the other one. if that
works, then i'd suspect that there might be a bug in the dependancy
resolution of the other.




BTW, in case you're worried about incompatibility with mlocate, that
package does not conflict with the locate package....although you do
have to take steps to stop both locate and mlocate from indexing the
filesystems. see Bug #454471 for more details. see also Bug #454106, one
of the messages contains a useful method for generating the locate db
from the mlocate db.




> P.S.: there are a lot of bugs on your package having the tag "fixed", but
> were never closed.

hmmm. i guess i've just assumed all along that Fixed is equivalent to
Closed, and they don't actually need to be closed. i've adopted all the
NMU changes, so i'll just close all the Fixed bugs next time i upload an
update.


craig

-- 
craig sanders <[EMAIL PROTECTED]>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to