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 deletion: pkg_install-20090610 ** '/usr/pkg/sbin/pkg_delete -K /var/db/pkg -r pkg_install-20090610' failed [ Rechecking packages after deletions ] dfly-bkpsrv# pkg_chk -a pkgtools/pkg_install - pkg_install-20090610 pkg_install-20090724 dfly-bkpsrv# pkg_chk -as pkgtools/pkg_install - pkg_install-20090610 pkg_install-20090724 dfly-bkpsrv# pkg_chk -as pkgtools/pkg_install - pkg_install-20090610 pkg_install-20090724 What should I do to update pkg_install? Thanks --Siju
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 more catastrophic than you want. The best thing may be to ask on the pkgsrc-us...@netbsd.org mailing list. I'd like to know the best answer too.
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 /usr/src/packages/pkg_install-[DATE].tgz The same procedure works with bootstrap-mk-files and bmake packages. And one more small related hint ... Note, that pkg_add rejects update attempt to the same version already installed. I often screw up some of my packages during development and would like to reinstall it from known good package. Then this procedure works: pkg_delete -f package pkg_add package.tgz pkg_admin rebuild-tree -- Hasso Tepper
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 last snapshot for at least 3 days. Is this as easy as configuring the pruning in hammer cleanup to 3d? Should reblocking still be done daily or also every 3 days? Thanks, Petr
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 since the last :snapshot for at least 3 days. Is this as easy as configuring the pruning :in hammer cleanup to 3d? Should reblocking still be done daily or also :every 3 days? : :Thanks, : :Petr The pruning system currently throws away fine-grained history beyond the first snapshot. BUT, I actually reserved a field in the PFS structure to set the minimum fine-grained history retention. I just haven't added any code to use the field. I think what you are requesting is desireable, and it will not take much time for me to code it up. I will implement the feature today. As with other hammer features, the idea is to be able to run a prune, rebalance, or reblocking operation at any time. The timing of when you run these operations is not supposed to effect the retention policy. That will still be the case. -Matt Matthew Dillon dil...@backplane.com
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: http://leaf.dragonflybsd.org/~hasso/pbulk-logs/20090812.2201/meta/report.bz2 Total number of packages: 9039 Successfully built: 8245 Failed to build: 328 Depending on failed package: 127 Explicitly broken or masked: 270 Depending on masked package:69 Packages breaking the most other packages Package Breaks Maintainer - x11/libgnomekbd 16 pkgsrc-us...@netbsd.org ham/gnuradio-core 15 w...@netbsd.org graphics/py-cairo 14 le...@trash.net audio/cdparanoia 13 k...@tac.nyc.ny.us lang/sun-jre15 8 pkgsrc-us...@netbsd.org lang/sun-jre14 8 pkgsrc-us...@netbsd.org comms/openobex 5 pkgsrc-us...@netbsd.org security/openvas-libraries 4 pkgsrc-us...@netbsd.org security/nessus-libraries 4 pkgsrc-us...@netbsd.org graphics/libv4l4 tech-multime...@netbsd.org Build failures Package Breaks Maintainer - archivers/jamjar sk...@netbsd.org archivers/sapcar pkgsrc-us...@netbsd.org audio/ario pkgsrc-us...@netbsd.org audio/bmp-macpkgsrc-us...@netbsd.org audio/cdparanoia 13 k...@tac.nyc.ny.us audio/gogo pkgsrc-us...@netbsd.org audio/libvisual0.2-plugins pkgsrc-us...@netbsd.org benchmarks/iozonepkgsrc-us...@netbsd.org benchmarks/randread gr...@netbsd.org biology/py-mol pkgsrc-us...@netbsd.org py26-mol-0.98nb4 pkgsrc-us...@netbsd.org biology/rasmol pkgsrc-us...@netbsd.org cad/boolean pkgsrc-us...@netbsd.org cad/eagler...@netbsd.org chat/jabberd2 1 pkgsrc-us...@netbsd.org chat/tircpkgsrc-us...@netbsd.org chat/zircon pkgsrc-us...@netbsd.org comms/asterisk16 jnem...@netbsd.org comms/modemd tsa...@netbsd.org comms/openobex 5 pkgsrc-us...@netbsd.org comms/plptools pkgsrc-us...@netbsd.org cross/avr-gcc 2 pkgsrc-us...@netbsd.org cross/avrdudepkgsrc-us...@netbsd.org cross/h8300-hms-gcc pkgsrc-us...@netbsd.org cross/i386-cygwin32 pkgsrc-us...@netbsd.org cross/i386-linux pkgsrc-us...@netbsd.org cross/i386-mingw32 pkgsrc-us...@netbsd.org cross/i386-msdosdjgpppkgsrc-us...@netbsd.org cross/mipsEEel-netbsdpkgsrc-us...@netbsd.org databases/openldap-smbk5pwd g...@netbsd.org databases/php-mssql1 jdole...@netbsd.org php4-mssql-4.4.9 1 jdole...@netbsd.org devel/cfitsiopkgsrc-us...@netbsd.org devel/diffusepkgsrc-us...@netbsd.org devel/electricfence pkgsrc-us...@netbsd.org devel/elfsh pkgsrc-us...@netbsd.org devel/gobo-eiffelpkgsrc-us...@netbsd.org devel/gtlpkgsrc-us...@netbsd.org devel/java-subversiong...@netbsd.org devel/libFoundation2 pkgsrc-us...@netbsd.org devel/libscsi 2 pkgsrc-us...@netbsd.org devel/libstatgrab 1 pkgsrc-us...@netbsd.org devel/mico tonne...@netbsd.org devel/ogre pkgsrc-us...@netbsd.org devel/p5-Devel-Checklib pkgsrc-us...@netbsd.org devel/p5-VCP 1 pkgsrc-us...@netbsd.org devel/papaya 1 pkgsrc-us...@netbsd.org devel/py-readlinetsa...@netbsd.org py23-readline-0nb4 tsa...@netbsd.org devel/py-subversion g...@netbsd.org py23-subversion-1.6.4nb1 g...@netbsd.org
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 pkgsrc-us...@netbsd.org -audio/xmms-faad pkgsrc-us...@netbsd.org -chat/silc-client-icb s...@netbsd.org +comms/openobex 5 pkgsrc-us...@netbsd.org -comms/xtel bou...@netbsd.org -cross/dasm xmo...@users.sourceforge.net -devel/anjuta 1 pkgsrc-us...@netbsd.org +devel/diffusepkgsrc-us...@netbsd.org -devel/flim 6 tech-pkg...@jp.netbsd.org +devel/rapidsvn pkgsrc-us...@netbsd.org -devel/semantic 2 pkgsrc-us...@netbsd.org +devel/valide ah...@netbsd.org +editors/Sigilpkgsrc-us...@netbsd.org -emulators/dega panc...@phreaker.net -emulators/raine pkgsrc-us...@netbsd.org -games/nethackpo...@netbsd.org -geography/garmin-utils g...@netbsd.org +graphics/cinepaint a...@netbsd.org -graphics/geeqie pkgsrc-us...@netbsd.org +graphics/ivtools ma...@netbsd.org -graphics/ruby-clutter-gtk 1 oba...@netbsd.org -graphics/xfigpkgsrc-us...@netbsd.org +ham/gnuradio-core 15 w...@netbsd.org +ham/xdx w...@netbsd.org -inputmethod/skk1 uebay...@netbsd.org -lang/cparser pkgsrc-us...@netbsd.org -lang/pcc r...@reedmedia.net +lang/see 1 ah...@netbsd.org -mail/mutt-devel to...@netbsd.org +mail/wl tech-pkg...@jp.netbsd.org -math/calcpkgsrc-us...@netbsd.org -math/xlispstat 1 pkgsrc-us...@netbsd.org -misc/lookup uebay...@netbsd.org +multimedia/dvdstyler pkgsrc-us...@netbsd.org -multimedia/pspvc pkgsrc-us...@netbsd.org +net/gupnp 2 pkgsrc-us...@netbsd.org -print/tex-dhucs1 mins...@netbsd.org +print/tex-memhangul-ucs mins...@netbsd.org +security/pkgsrc-us...@netbsd.org +sysutils/coreutils 2 pkgsrc-us...@netbsd.org -sysutils/gnome-commander pkg...@blackmouse.biz -sysutils/treec...@netbsd.org +wm/wmii g...@netbsd.org -www/browser-bookmarks-menu pkgsrc-us...@netbsd.org -x11/qgtkstylepkgsrc-us...@netbsd.org +x11/libgnomekbd 16 pkgsrc-us...@netbsd.org +x11/py-wxWidgets pkgsrc-us...@netbsd.org +py23-wxWidgets-2.8.10.1 pkgsrc-us...@netbsd.org
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 WIP version, it will break the filesystem (that's why there are so many warnings if you try to do it). With a recent kernel version 2 will be marked as 'NORM'. It is a different implementation then what was in WIP. If version is is marked as normal then it is safe to upgrade to it and the utility won't spew dire warnings at you when you do. But note that older kernels will not be able to read that filesystem. The upgrade will apply only to newly created directories. -Matt
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 directory entry layout Should I switch to version 2 anyhow? Petr
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 directory entry layout : :Should I switch to version 2 anyhow? : :Petr Yah, you can switch to v2. It will improve the directory layout for new directory topologies created after the upgrade. Though it still takes a reblocking pass or two to get it there (which will happen automatically by the hammer cleanup crons over the course of time). -Matt Matthew Dillon dil...@backplane.com
