[SOLVED] mtimes differ

venom · Posted: Mon Mar 20, 2006 3:34 pm Post subject: [SOLVED] mtimes differ

Hi,
I did etc-update lately - it was something about 17 files to upgrade there. I remember, that I haven't modified files, which content I had ever changed (those, which contained settings only for my system). Now, when my system starting (and when i shutdown it), I get many errors like "Re-caching dependency info (mtimes differ)".

I was searching on Gentoo forums, and available solutions are:

1) re-emerging baselayout (I did it, but I still have this errors)
2) run depscan.sh (I did it too, but this script do nothing...)

masteroftheuniverse · Apprentice Joined: 20 Jan 2005 Posts: 259

is your system clock staying consistent?

venom · Posted: Tue Mar 21, 2006 11:08 am Post subject:

last time i was having a problem with bios- settings of my system clock was not saved (i don't know why - everything expect clock was ok). Now I`m using NTP to set my system time, so it must be consistent.

Autie · Posted: Tue Mar 21, 2006 10:21 pm Post subject:

Kinda same here:

Raenk · n00b Joined: 04 Mar 2004 Posts: 64

Exact same thing here, haven't try to solve it yet, but what causes this ?

WTFman · Apprentice Joined: 04 Apr 2005 Posts: 153

Hmm, I've gotten this too, I was sure it was after I tried fooling around w/ gcc 4.1 and glibc 2.4 but maybe something else causes this?
_________________
Occupation: Professional Slacker
Hobbies/Interests: Open Source Aficionado since 2005

Zyzzyva100 · Apprentice Joined: 08 Aug 2005 Posts: 193

This happened to me after emerge --update world, and I was updated to glibc 2.4 (which caused other problems), but this doesn't really seem to be a big problem. Its weird, but it doesn't show as an error per se. I just wish I knew what it was.

awx · n00b Joined: 26 Jan 2005 Posts: 51

Same here on my Mini-ITX system. I'm using ntp and have rc_synctohwclock="yes".

mudrii · l33t Joined: 26 Jun 2003 Posts: 789 Location: Singapore

Reemerge baselayout

venom · Posted: Thu Mar 23, 2006 4:48 pm Post subject:

as I said, i tried it firstly, before anything, but it doesn't repaired my system

I still have mtimes errors

venom · Posted: Thu Mar 23, 2006 5:41 pm Post subject:

wow, I've found a solution- you really need to re-emerge baselayout, but...

When I did it first time, I hadn't changed any USE FLAGS, and after reboot, I was still having errors.

Now, I compiled baselayout with all available flags:

toralf · Posted: Fri Mar 24, 2006 1:13 pm Post subject:

I filed a bug regarding this message: https://bugs.gentoo.org/show_bug.cgi?id=127419 re-emerging baselayout is really _not_ needed.

Southtown · n00b Joined: 30 Dec 2005 Posts: 8

Well, I emerged baselayout to be sure I wasn't just 'un-verbosing' the errors. The sendmail issue seemed to take care of one package, but my problems started after an emerge -e world. I was afraid the bugfix only applied to one package which had an error caused by deeper issues. Would each package contain these errors?!

Emerging baselayout did work, by the way. However I didn't reboot between the 'use emerge' and the 'un-use emerge' and I successfully avoided any major errors.

_________________
Spirit happens

Zyzzyva100 · Apprentice Joined: 08 Aug 2005 Posts: 193

So I see the topic says that this has been solved, but I have tried many of the listed "fixes", and still have the problem.

Re-emerging baselayout fixed some, but not all of the places that I see mtimes differ on startup or shutdown. I tried re-emerging glibc again (this only started after I did an update world, and glibc 2.4 had been released to stable). I also rebuilt my tool chain, and have done everything but emerge -e world.

Do I really need to re-emerge every package on my system to fix this? Right now it isn't causing any actual errors, but I have a bad feeling that eventually it will start to do so, and I would rather have it fixed before then.

toralf · Posted: Sun Mar 26, 2006 8:29 pm Post subject:

Bob P · Posted: Mon Mar 27, 2006 9:53 am Post subject:

toralf · Posted: Mon Mar 27, 2006 11:18 am Post subject:

reopened

Zyzzyva100 · Apprentice Joined: 08 Aug 2005 Posts: 193

bolshoi · n00b Joined: 29 Mar 2006 Posts: 1

Did you explicity put /sbin/depscan.sh --update?

toralf · Posted: Wed Mar 29, 2006 1:24 pm Post subject:

joaopft · Posted: Fri Mar 31, 2006 11:22 pm Post subject:

It is enough to do:

simu-san · n00b Joined: 29 Mar 2006 Posts: 2

for me

odessit · Posted: Mon Apr 10, 2006 2:46 pm Post subject:

touch /etc/init.d/*; /sbin/depscan.sh --update
worked for me too (radiusd problem)

richard.scott · Posted: Thu Apr 13, 2006 10:08 am Post subject:

On my system I removed /var/lib/init.d/deptree and /var/lib/init.d/depcache and then I ran depscan.sh to recreate those files.

That worked for me

luminoso · Posted: Mon May 15, 2006 8:19 pm Post subject: