https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192069

Gyrd Thane Lange <gyrd...@thanelange.no> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gyrd...@thanelange.no

--- Comment #3 from Gyrd Thane Lange <gyrd...@thanelange.no> ---
I have just experienced the same. Using portupgrade to upgrade pkg from 1.2 to
1.3 nulled all the timestamps in the package database.

Jul 25 00:54:33 onyx pkg: pkg-1.2.7_2 deinstalled
Jul 25 00:54:35 onyx pkg-static: pkg-1.3.0 installed

root@onyx:/usr/ports # pkg query "%t %o" | grep -v ^0
1406242475 ports-mgmt/pkg
root@onyx:/usr/ports # pkg query "%t %o" | wc -l
     791
root@onyx:/usr/ports # pkg info | grep portupgrade
portupgrade-devel-20131212,3

11.0-CURRENT #2 r269075M: Thu Jul 24 22:35:47 CEST 2014 amd64

It appears the date resets happens the moment ports-mgmt/pkg itself is
upgraded. Subsequent installs of any port seemingly records the correct time. A
brute force fix is therefore to reinstall *all* the packages on the system, but
since I happen to have a backup copy of the local.sqlite package db I can use
SQL to restore the timestamps. Nothing else seems to be missing.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Reply via email to