Harry Schmalzbauer
2014-Dec-18 18:44 UTC
pkg-1.4-0 signal-4-exit with core-avx-i; FreeBSD:10:i386 vs. FreeBSD:10:32?
Hello, surprisingly my deployment process fails with: pkg: file:///media/OAK_PKG_CD/packages/FreeBSD:10:i386/meta.txz: No such file or directory I never had any problems with my scripts with pkg-1.3.8. It looks that FreeBSD:10:32 was renamed to FreeBSD:10:i386, right? Now pkg-1.4.0 is mandatory. Not mentioned in UPDATING, no help how to define previous version ? :-( pkg-1.4.0 core dumps when compiled with CPUTYPE=core-avx-i on an Ivy-Bridge host and run on a Haswell system (both ESXi-guest and both stable/10, r275903) :-( This is not very helpful, I know, sorry, but I don't have time to investigate ? I was about to do some quick updates? I strongly vote for pkg integration into base with the usual maintenance quality. The current circular dependency caused too much problems since pkg_legacy was abandoned. A planned one-hour-task again takes me 10 hours because of fundamental changes I cannot easily revert or were announced/tested. Thanks, -Harry
Harry Schmalzbauer
2014-Dec-19 15:44 UTC
New in pkg-1.4-0 pkg: unlinkat(usr/local/): Read-only file system [Was: pkg-1.4-0 signal-4-exit with core-avx-i; FreeBSD:10:i386 vs. FreeBSD:10:32?]
Bez?glich Harry Schmalzbauer's Nachricht vom 18.12.2014 19:44 (localtime):> Hello, > > surprisingly my deployment process fails with: > pkg: file:///media/OAK_PKG_CD/packages/FreeBSD:10:i386/meta.txz: No such > file or directory > > I never had any problems with my scripts with pkg-1.3.8. It looks that > FreeBSD:10:32 was renamed to FreeBSD:10:i386, right?After adjusting my scripts to handle the new ABI, I now see the another pkg(8) surprise: 'pkg delete -f pkg' [1/1] Deinstalling pkg-1.4.0... [1/1] Deleting files for pkg-1.4.0: 100% pkg: unlinkat(usr/local/): Read-only file system pkg: unlinkat(usr/): Read-only file system pkg: unlinkat(usr/local/): Read-only file system pkg: unlinkat(usr/): Read-only file system ? (repeted) It's true that "/" is read-only, but "/usr/local" is rw of course. pkg(8) mustn't touch anything on "/" for most packages, which is true for "pkg" itself. Can somebody explain the cause of these error messages with pkg-1.4.0? Thanks, -Harry