[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1028142: marked as done (dlocate: cannot find recent files - obsolete database?)

Your message dated Sun, 08 Jan 2023 13:23:12 +0100
with message-id <87cz7pnrkf.fsf@turtle.gmx.de>
and subject line Re: Bug#1028142: dlocate: cannot find recent files - obsolete database?
has caused the Debian Bug report #1028142,
regarding dlocate: cannot find recent files - obsolete database?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1028142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028142
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: dlocate
Version: 1.12
Severity: grave
Justification: renders package unusable

dlocate cannot find recent files, so it is mostly useless.

I suspect that since the upgrade to dlocate 1.12 on 2022-11-25,
its database is no longer updated:

zira:~> ll /var/lib/dlocate
total 109172
-rw-r--r-- 1 root root 55750318 2022-11-25 00:27:44 dlocatedb
-rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old
-rw-r--r-- 1 root root   105318 2022-11-25 00:27:44 dlocatedb.stamps
-rw-r--r-- 1 root root   299199 2022-11-25 00:27:44 dpkg-list

The changelog doesn't mention any change:

dlocate (1.12) unstable; urgency=medium

  * QA upload.
  * Convert to 3.0 source format. Closes: #1007667

 -- Bastian Germann <bage@debian.org>  Thu, 24 Nov 2022 00:10:50 +0100

The cron file /etc/cron.daily/dlocate is there, though:

#!/bin/sh

# update databases for both files and packages.
if [ -x /usr/sbin/update-dlocatedb ] ; then
  /usr/sbin/update-dlocatedb -b
fi

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dlocate depends on:
ii  dctrl-tools [grep-dctrl]  2.24-3+b1
ii  dpkg                      1.21.17
ii  perl                      5.36.0-6

Versions of packages dlocate recommends:
ii  supercat  0.5.7-1

dlocate suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

--- End Message ---
--- Begin Message --- 
On 2023-01-08 12:18 +0100, Vincent Lefevre wrote:

> On 2023-01-08 08:54:35 +0100, Sven Joachim wrote:
>> That is your problem, you need to reenable and restart these units.
>>
>> # systemctl enable anacron.service anacron.timer
>> # systemctl start anacron.service anacron.timer
>>
>> See the d-d-a link I gave in my first reply,
>> https://lists.debian.org/debian-devel-announce/2022/11/msg00001.html.
>
> I confirm that this fixes the issue. IMHO, it should have been
> announced in the NEWS.Debian file.

I agree that the handling of #1019554 by the anacron maintainer was
anything but stellar.  If you think that they should do anything about
it now, it is probably best to open a new bug.

In any case, I am closing the current one since there is nothing wrong
with the dlocate cron script.

Cheers,
       Sven

--- End Message ---
Reply to: