pkg_delete failed

Hi Trying to update packages I got the following output dfly-bkpsrv# pkg_chk -g dfly-bkpsrv# pkg_chk -r pkgtools/pkg_install - pkg_install-20090610 pkg_install-20090724 13:42 /usr/pkg/sbin/pkg_delete -K /var/db/pkg -r pkg_install-20090610 pkg_delete: The following packages are marked as not for

Re: pkg_delete failed

On Mon, August 17, 2009 4:15 am, Siju George wrote: What should I do to update pkg_install? I've wondered about this too; the last time this bit me when updating a bulk build, I ended up using pkg_delete -ff to get rid of _everything_ and rebuilding from pkgsrc/pkgtools/bootstrap. This may be

Re: pkg_delete failed

Siju George wrote: What should I do to update pkg_install? Starting from 2009Q1 (AFAIR) pkg_add updates packages inplace. This with combination of DESTDIR support makes this procedure possible: cd /usr/src/pkgtools/pkg_install/ bmake USE_DESTDIR=yes package pkg_add -u

Hammer question about pruning

Hi all, Im thinking about deploying DragonFly as a storage server. Company I work for needs fine snapshot/versioning granularity and I think Hammer would be good for that. The situation is like this: they want daily snapshots, but they want to keep every modification of files/databases since the

Re: Hammer question about pruning

:Hi all, : :Im thinking about deploying DragonFly as a storage server. Company I work :for needs fine snapshot/versioning granularity and I think Hammer would be :good for that. The situation is like this: they want daily snapshots, but :they want to keep every modification of files/databases

pkgsrc-HEAD DragonFly 2.3.2/i386 2009-08-12 22:01

pkgsrc bulk build report DragonFly 2.3.2/i386 Compiler: gcc Build start: 2009-08-12 22:01 Build end: 2009-08-17 15:48 Full report: http://leaf.dragonflybsd.org/~hasso/pbulk-logs/20090812.2201/meta/report.html Machine readable version:

Re: pkgsrc-HEAD DragonFly 2.3.2/i386 2009-08-12 22:01

-Build start: 2009-07-30 16:12 +Build start: 2009-08-12 22:01 -audio/albumplayerpkgstc-us...@netbsd.org -audio/csound5pkgsrc-us...@netbsd.org +audio/cdparanoia 13 k...@tac.nyc.ny.us -audio/mp3_check

Re: Hammer question about pruning

Thanks Matt, So if I set the prune-min to 3 days, and use even the default PFS config (1 day snapshot, 1 day prune, 1 day reblock) it will just work? Excellent! Petr

Re: Hammer question about pruning

:In regards to existing hammer instalations that run the initial HAMMER :release, do I have to upgrade to HAMMER WIP? : :Petr It isn't necessary for the pruning feature. If it is still calling it WIP then you have either an old kernel or an old hammer binary. Do not upgrade to the

Re: Hammer question about pruning

Sorry for the confusion, IM running a recent kernel + userland, but the file system was created about 9 months ago, this is what I have: min=1 wip=3 max=2 current=1 description=2.0 - First HAMMER release available versions: 1 NORM2.0 - First HAMMER release 2 NORM2.3 - New

Re: Hammer question about pruning

: :Sorry for the confusion, IM running a recent kernel + userland, but the file :system was created about 9 months ago, this is what I have: : :min=1 wip=3 max=2 current=1 description=2.0 - First HAMMER release :available versions: :1 NORM2.0 - First HAMMER release :2 NORM2.3