hmm, on Thu, Oct 14, 2010 at 12:53:27PM +0200, Jan Stary said that > On Oct 14 10:10:22, frantisek holop wrote: > > hmm, on Wed, Oct 13, 2010 at 04:40:23PM +0000, Christian Weisgerber said > > that > > > frantisek holop <[email protected]> wrote: > > > > > > > for the last week or so, snapshot packages > > > > have "strange" dates alternating with a one day difference: > > > > > > > ftp://ftp.fr.openbsd.org/pub/OpenBSD/snapshots/packages/i386/ > > > > > > I now use "scp -p" instead of plain "scp" to upload the packages. > > > This gives you an idea when the build was actually started (timestamp > > > of the oldest package) as opposed to when I started the upload. It > > > doesn't really matter either way. > > > > ah, right. (my) problem with this is, that the upload dates > > were the only indication basically if a mirror was finished > > copying all the files.. (as unfinished mirrors were another > > source of confusing update errors) > > So, until now, you have always checked the 5000+ datetime strings > before an update, to be safe, right?
no, i simply looked at aa* and zz*. it happened many times that i caught the mirror mid-copying the new files, so i just waited until it finished them all. the mirror scripts work(ed) in alphabetical order. if you look in the archives this is a well known problem and as far as i know there is still no way for pkg_add to know that all packeges coming from PKG_PATH were compiled with the same libs. so i check manually. all i am saying is that before: all packages same date, slightly different times; now: times and dates vary by days. although i just did it again: ftp> ls aa* 150 Opening ASCII mode data connection for '/bin/ls'. -rw-r--r-- 1 1001 0 134940 Oct 12 10:22 aalib-1.4p2-no_x11.tgz -rw-r--r-- 1 1001 0 149809 Oct 12 02:51 aalib-1.4p2.tgz -rw-r--r-- 1 1001 0 30898 Oct 12 11:21 aamath-0.3p0.tgz 226 Transfer complete. ftp> ls zz* 150 Opening ASCII mode data connection for '/bin/ls'. -rw-r--r-- 1 1001 0 106917 Oct 12 09:14 zziplib-0.13.59.tgz -rw-r--r-- 1 1001 0 105184 Oct 12 03:12 zzuf-0.12.tgz 226 Transfer complete. this time times have bigger differences, but the date is now the same. > Snapshots and snapshot packages move forward all the time, unlike > your installed system. If you have a system that provides > libcurses.so.10.0, and (a new version of) a package comes out that > requires libcurses.so.11.0, there is simply no way to upgrade the > package, because your system does not meet the package's requirements. > That's exactly what pkg_add is telling you. at the time of writing i was using the latest OS snapshot.. as far as i know snapshot packages are compiled on snapshot systems. i am curious how can i get bad major errors from packages on the latest snapshot. i simply expected the oct 9/10 snapshot packages to match with the oct 6 system snapshot. -f -- no sense being pessimistic. it wouldn't work anyway.
