pkgsrc-HEAD DragonFly 2.3/i386 2009-05-15 05:10
pkgsrc bulk build report DragonFly 2.3/i386 Compiler: gcc Build start: 2009-05-15 05:10 Build end: 2009-05-20 06:53 Full report: http://leaf.dragonflybsd.org/~hasso/pbulk-logs/20090515.0510/meta/report.html Machine readable version: http://leaf.dragonflybsd.org/~hasso/pbulk-logs/20090515.0510/meta/report.bz2 Total number of packages: 8774 Successfully built: 7902 Failed to build: 403 Depending on failed package: 143 Explicitly broken or masked: 264 Depending on masked package:62 Packages breaking the most other packages Package Breaks Maintainer - sysutils/libgtop 17 pkgsrc-us...@netbsd.org print/cups13 j...@pkgsrc.org lang/sun-jre15 8 pkgsrc-us...@netbsd.org lang/sun-jre14 8 pkgsrc-us...@netbsd.org textproc/py-xml7 droch...@netbsd.org sysutils/wbm-useradmin 6 pkgsrc-us...@netbsd.org security/libpreludedb 5 shanno...@netbsd.org graphics/GeometryKit 5 pkgsrc-us...@netbsd.org security/openvas-libraries 4 adri...@netbsd.org security/nessus-libraries 4 pkgsrc-us...@netbsd.org Build failures Package Breaks Maintainer - archivers/jamjar sk...@netbsd.org archivers/sapcar pkgsrc-us...@netbsd.org audio/bmp-macpkgsrc-us...@netbsd.org audio/csound5pkgsrc-us...@netbsd.org audio/gogo pkgsrc-us...@netbsd.org audio/gtkpod s...@netbsd.org audio/libao-nas pkgsrc-us...@netbsd.org audio/libvisual0.2-plugins pkgsrc-us...@netbsd.org audio/moc-devel peter.schul...@infidyne.com audio/sndpkgsrc-us...@netbsd.org benchmarks/iozonepkgsrc-us...@netbsd.org benchmarks/lmbench pkgsrc-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/i2cbjw...@netbsd.org chat/irchat-pj 1 tech-pkg...@jp.netbsd.org chat/silc-client-icb s...@netbsd.org chat/tircpkgsrc-us...@netbsd.org chat/zircon pkgsrc-us...@netbsd.org comms/modemd tsa...@netbsd.org comms/plptools pkgsrc-us...@netbsd.org comms/xtel bou...@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/bdb-xml 4 mins...@netbsd.org databases/openldap-smbk5pwd g...@netbsd.org databases/php-mssql1 jdole...@netbsd.org php4-mssql-4.4.9 1 jdole...@netbsd.org devel/anjuta 1 pkgsrc-us...@netbsd.org devel/cfitsiopkgsrc-us...@netbsd.org devel/electricfence pkgsrc-us...@netbsd.org devel/elfsh pkgsrc-us...@netbsd.org devel/gdbpkgsrc-us...@netbsd.org devel/gdb6 shanno...@netbsd.org devel/gdbada j...@johnrshannon.com 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
Re: pkgsrc bulk build question
Jordan Gordeev jgord...@dir.bg wrote: Johannes Hofmann wrote: Hi, is anyone using the bulk build script mk/bulk/build successfully on DragonFly? [...] Any ideas? I suggest you use the new method of doing bulk builds - pbulk. It's a package available at /usr/pkgsrc/pkgtools/pbulk. Some documentation on how to use: 1. http://www.dragonflybsd.org/docs/developer/PbulkBuilding/ 2. /usr/pkgsrc/doc/HOWTO-pbulk 3. http://wiki.netbsd.se/pbulk-HOWTO Thanks for pointing me at pbulk. It is a bit complex at first especially if you don't need all the parallel stuff, but it seems to be working now, [14/354] :-) Regards, Johannes
Re: amd64 ISO ?
Hi Saifi, As far as I know DFBSD does not provide AMD64 ISOs yet as it is still development. If you are interested, you can try amd64 on qemu by using DFBSD's amd64 testing framework located in test/amd64. For this, you'll need of course a DFBSD installation and the source tree. Regards, Antonio Huete 2009/5/20 Saifi Khan saifi.k...@twincling.org: Hi all: i'd like to download and try the native AMD64 build ISO image of DragonFlyBSD 2.2.x . The 2.2.1 download ISO at http://www.dragonflybsd.org/download/ seems to be for i386. Can somebody please point me to the download URL ? thanks Saifi.
Re: amd64 ISO ?
On Wed, 20 May 2009, Antonio Huete Jimenez wrote: Hi Saifi, As far as I know DFBSD does not provide AMD64 ISOs yet as it is still development. If you are interested, you can try amd64 on qemu by using DFBSD's amd64 testing framework located in test/amd64. For this, you'll need of course a DFBSD installation and the source tree. Regards, Antonio Huete Hi Antonio: Thank you for your reply. In that case, as per my understanding: . download dfly 2.2.1 dvd iso for intel . install dfly 2.2.1 on a i386/intel box . login as root . update BINPKG_SITES in /etc/settings.conf . pkg_add -v scmgit . cd /usr . make git-clone . cd /usr/pkgsrc/emulators/qemu . make install clean . cd /usr/src/test/amd64 . http://gitweb.dragonflybsd.org/dragonfly.git/blob/HEAD:/test/amd64/Makefile there is just a Makefile # make all . qemu-system-x86_64 -m 900m root.img Does this look ok to you ? Additionally, i've the following queries: . what do i specify for BINPKG_SITES . do i need to create a hdd image using qemu-img to be used as hard disk ? . dfly 2.2.1 liveCD on startx just seems to hang, so is it a better approach to install it first to the disk ? . what do i need to do to get the network 'bridge' work ? Appreciate your replies and suggestions. thanks Saifi.
Re: amd64 ISO ?
Saifi Khan schrieb: [...] . update BINPKG_SITES in /etc/settings.conf . pkg_add -v scmgit git is already on the LiveCD and will be automatically on the installed system as well. Sascha -- http://yoyodyne.ath.cx
Re: amd64 ISO ?
On Wed, 20 May 2009, Sascha Wildner wrote: Saifi Khan schrieb: [...] . update BINPKG_SITES in /etc/settings.conf . pkg_add -v scmgit git is already on the LiveCD and will be automatically on the installed system as well. Sascha Thanks Sascha. i'm just learning the ropes right now as far as DragonFlyBSD is concerned. Appreciate you maintaining the manual sets on your home page. thanks Saifi.
Re: Hammer error?
I will check with the debugger later, but i can tell in advance that i found the trigger, i could reproduce the error :-) Machine0 has standard out of the box hammerFS from installer, used for 2-3 months, now 30GB in /home, it's a server, it has a public static IP for his own. Machine1 fresh install same structure, running in a VM in my home behind a router, behind a ADSL (Dynamic-ip) I forwaded the ADSL port 22 to the Machine1, checked my ip address at the moment and ran: Machine0# hammer pfs-status /home //to get shared-uuid Machine1# hammer pfs-slave /pfs/machine0.home shared-uuid=** Machine0# hammer mirror-copy /home r...@machine1ipaddress:/pfs/machine0.home It took a couple of hours (30GB) and sometime in the run the public address of my ADSL modem changed (not the internat, im still 192.168) Then i got a hammer.core in my root's home. I think there is nothing to do about this just do the copy in small chunks, right? Sdav On Tue, May 19, 2009 at 22:49, Matthew Dillon dil...@apollo.backplane.com wrote: :Hello, :I was doing some backup from Machine0 to Machine1 using hammer :mirror-copy and got a suppicious new file called hammer.core. :Looking around the files it looks like a success copy but i still :curious about this new 720kb file. :Someone can tell me if i need to worry about it and where can i start :checking for errors in case there was one? :Machine0 has DFBSD2.2.0-release, Machine1 has DFBSD2.2.1-release, :could it be the problem? should i just upgrade both? :Sdav A hammer.core could only come from the hammer utility core dumping. This wouldn't be a filesystem error but it certainly indicates a bug somewhere in the hammer utility. If you haven't updated the sources relative to when the core was generated you can recompile the hammer utility with DEBUG_FLAGS=-g and then gdb the binary and core file and get a backtrace to see where it died. If you have updated the sources since then you'd have to wait for a new core file to be generated for a newly debug-compiled hammer utility to match the core file. cd /usr/src/sbin/hammer make clean make obj make DEBUG_FLAGS=-g all install ... gdb /sbin/hammer hammer.core ... gdb back -Matt Matthew Dillon dil...@backplane.com -- Sdävtaker prays to Rikku goddess for a good treasure.
Re: cd9660: /dev/cd0c: Invalid argument
Saifi, Can you please boot with verbose and post here your dmesg? Thanks Antonio Hi: Env: AMD64X2 4400+ processor ASUS M2NMX-SE motherboard 2GB DDR2 RAM 320GB Seagate SATA II NCQ HDD nVidia graphics card nVidia SATA controller nVidia neForce Gigabit ethernet On running the dfly 2.2.1 DVD, the following lines are seen after the boot loader options Mounting root from cd9660: cd0c cd0: invalid primary paritition table: no magic iso_mountroot(): using session at block 0 cd0: invalid primary paritition table: no magic cd9660: Rockridget extension start_init: tryign /sbin/init Loading configuration files. . kern.seedenable: 0 - 1 kern.seedenable: 1 - 0 Starting file system checks: cd9660: /dev/cd0c: Invalid argument In fact the DVD boot process waits here long enough that i'm able to type the above lines by looking at the string :) Any idea what could be reason for this ? thanks Saifi.
cd9660: /dev/cd0c: Invalid argument
Hi: Env: AMD64X2 4400+ processor ASUS M2NMX-SE motherboard 2GB DDR2 RAM 320GB Seagate SATA II NCQ HDD nVidia graphics card nVidia SATA controller nVidia neForce Gigabit ethernet On running the dfly 2.2.1 DVD, the following lines are seen after the boot loader options Mounting root from cd9660: cd0c cd0: invalid primary paritition table: no magic iso_mountroot(): using session at block 0 cd0: invalid primary paritition table: no magic cd9660: Rockridget extension start_init: tryign /sbin/init Loading configuration files. . kern.seedenable: 0 - 1 kern.seedenable: 1 - 0 Starting file system checks: cd9660: /dev/cd0c: Invalid argument In fact the DVD boot process waits here long enough that i'm able to type the above lines by looking at the string :) Any idea what could be reason for this ? thanks Saifi.
pkg_radd PKG_PATH
Hi all: pkg_radd PKG_PATH by default tries to look for http://pkgbox.dragonflybsd.org/DragonFly-2.2.1/All Which is the recommended PKG_PATH URL to use? http://mirror.evilprojects.net/pub/DragonFlyBSD/packages/DragonFly-2.2.0/ or http://mirror.evilprojects.net/pub/DragonFlyBSD/packages/DragonFly-2.3.0/ thanks Saifi.
Re: pkg_radd PKG_PATH
On Wed, 20 May 2009, Antonio Huete Jimenez wrote: Hi Saifi, It is pointing to 2.2.1 because you are using 2.2.1. You should use the packages compiled for the release you are using. You might want to give it a try to pkgin. You can find some instructions for setting it up here: http://leaf.dragonflybsd.org/mailarchive/users/2009-05/msg00064.html Regards, Antonio Hi all: pkg_radd PKG_PATH by default tries to look for http://pkgbox.dragonflybsd.org/DragonFly-2.2.1/All Which is the recommended PKG_PATH URL to use? http://mirror.evilprojects.net/pub/DragonFlyBSD/packages/DragonFly-2.2.0/ or http://mirror.evilprojects.net/pub/DragonFlyBSD/packages/DragonFly-2.3.0/ thanks Saifi. Hi Antonio: The page http://mirror.evilprojects.net/pub/DragonFlyBSD/packages/ does not list the package directory for 2.2.1 Is 'pkgin' supposed to be an alternative/workaround for releases where package directory is not available ? thanks Saifi.
Re: pkg_radd PKG_PATH
Hi Saifi, It is pointing to 2.2.1 because you are using 2.2.1. You should use the packages compiled for the release you are using. You might want to give it a try to pkgin. You can find some instructions for setting it up here: http://leaf.dragonflybsd.org/mailarchive/users/2009-05/msg00064.html Regards, Antonio Hi all: pkg_radd PKG_PATH by default tries to look for http://pkgbox.dragonflybsd.org/DragonFly-2.2.1/All Which is the recommended PKG_PATH URL to use? http://mirror.evilprojects.net/pub/DragonFlyBSD/packages/DragonFly-2.2.0/ or http://mirror.evilprojects.net/pub/DragonFlyBSD/packages/DragonFly-2.3.0/ thanks Saifi.
Re: pkg_radd PKG_PATH
On Wed, 20 May 2009, Antonio Huete Jimenez wrote:
Hi Saifi,
It is pointing to 2.2.1 because you are using 2.2.1. You should use the
packages compiled for the release you are using.
You might want to give it a try to pkgin. You can find some instructions for
setting it up here:
http://leaf.dragonflybsd.org/mailarchive/users/2009-05/msg00064.html
Regards,
Antonio
i could checkout the WIP (work in progress), but on attempting
to build the /usr/pkgsrc/pkgin i get the following error:
amd64# make
Makefile, line 32: Could not find ../../mk/bsd.prefs.mk
Makefile, line 36: Malformed conditional (${OPSYS} != NetBSD
|| (${OPSYS} == NetBSD !empty(OS_VERSION:M[0-4].*)))
Makefile, line 37: Could not find
../../net/libfetch/buildlink3.mk
Makefile, line 38: if-less endif
Makefile, line 40: Could not find
../../archivers/libarchive/buildlink3.mk
Makefile, line 41: Could not find
../../databases/sqlite3/buildlink3.mk
Makefile, line 42: Could not find ../../mk/bsd.pkg.mk
make: fatal errors encountered -- cannot continue
amd64# pwd
/usr/pkgsrc/wip/pkgin
amd64#
This clearly points to the missing .mk files and expeced to be
in '/usr/pkgsrc/mk' directory.
However, i noted that '/usr/share/mk' diretory has the required
.mk files.
My question is - what is the correct way to install the mk
scripts ? Can i just copy the mk/ directory to /usr/pkgsrc/
directory ?
thanks
Saifi.
Re: pkg_radd PKG_PATH
amd64# make Please try bmake
Re: pkg_radd PKG_PATH
On Wed, 20 May 2009, Jeremy C. Reed wrote:
amd64# make
Please try bmake
the same error is seen.
amd64# o
/usr/pkgsrc/wip/pkgin
amd64# bmake
bmake: /usr/pkgsrc/wip/pkgin/Makefile line 32: Could not find
../../mk/bsd.prefs.mk
bmake: /usr/pkgsrc/wip/pkgin/Makefile line 36: Malformed
conditional (${OPSYS} != NetBSD || (${OPSYS} == NetBSD
!empty(OS_VERSION:M[0-4].*)))
bmake: /usr/pkgsrc/wip/pkgin/Makefile line 37: Could not find
../../net/libfetch/buildlink3.mk
bmake: /usr/pkgsrc/wip/pkgin/Makefile line 40: Could not find
../../archivers/libarchive/buildlink3.mk
bmake: /usr/pkgsrc/wip/pkgin/Makefile line 41: Could not find
../../databases/sqlite3/buildlink3.mk
bmake: /usr/pkgsrc/wip/pkgin/Makefile line 42: Could not find
../../mk/bsd.pkg.mk
bmake: Fatal errors encountered -- cannot continue
bmake: stopped in /usr/pkgsrc/wip/pkgin
amd64#
thanks
Saifi.
Re: pkg_radd PKG_PATH
However, i noted that '/usr/share/mk' diretory has the required .mk files. My question is - what is the correct way to install the mk scripts ? Can i just copy the mk/ directory to /usr/pkgsrc/ directory ? No. You have a broken or incomplete pkgsrc installation if you don't have pkgsrc/mk/bsd.prefs.mk
Re: cd9660: /dev/cd0c: Invalid argument
: Mounting root from cd9660: cd0c : cd0: invalid primary paritition table: no magic : iso_mountroot(): using session at block 0 : cd0: invalid primary paritition table: no magic : cd9660: Rockridget extension : start_init: tryign /sbin/init : Loading configuration files. : . : kern.seedenable: 0 - 1 : kern.seedenable: 1 - 0 : Starting file system checks: : cd9660: /dev/cd0c: Invalid argument It's working ok. It's trying to run fsck on the CD, which clearly will not work. That is a known bug but it is harmless. It is not stuck on that step but probably instead working on some later step in the boot process. -Matt
Re: Hammer error?
:Oh, after retry with the new IP it started in :transactionid=3D0002 again, is it ok? shouldnt it start where it :crashed? :Sdav This isn't a bug but it is a missing feature. What is happening is that the mirror stream is trying to eat too large a chunk (the entire difference between the slave and the master) in one go, and will not update the transaction id until the entire chunk is finished. Because transaction id's do not represent timestamps we need to add a heuristic to at least the mirror-stream implementation to not try to do the entire block at once. We also need to make a slight modificatin to the wire protocol to allow save points to be sent in the middle of the stream. Right now only the mirror-stream protocol can do save-points, since it is a continuous 2-way connection. mirror-copy cannot. -Matt
Re: pkg_radd PKG_PATH
: :Matthew Dillon wrote: : Not all of our mirrors have all of our top-level softlinks. : corecode? Chlamydia is missing a bunch of softlinks. :=20 : Nearly all the softlinks point to the 2008Q4 package set. : :I'll add the links. We really need to get pkgbox going so that chlamydia= :=20 :can mirror off it. Is that still happening? : :cheers : simon Yes, that's the plan. We aren't going to do anything drastic on Avalon until Robin's crypto cycle test finishes (The test takes 2 cpu-weeks to run). Peter is out of the country as well. I'm not sure what Justin's schedule is like. So it could be a few weeks before Avalon gets reconfigured. -Matt
Re: pkg_radd PKG_PATH
On Wed, 20 May 2009, Jeremy C. Reed wrote: However, i noted that '/usr/share/mk' diretory has the required .mk files. My question is - what is the correct way to install the mk scripts ? Can i just copy the mk/ directory to /usr/pkgsrc/ directory ? No. You have a broken or incomplete pkgsrc installation if you don't have pkgsrc/mk/bsd.prefs.mk What is the way out of this ? Post dfly 2.2.x installation, there was just a 'pkg_summary' file in /usr/pkgsrc. Should that be considered broken ? With Antonio's suggestion, http://leaf.dragonflybsd.org/mailarchive/users/2009-05/msg00064.html the following steps were taken: # cd /usr # make pkgsrc-wip-checkout # cd pkgsrc/wip/pkgin # bmake What did i miss here ? thanks Saifi.
Re: cd9660: /dev/cd0c: Invalid argument
On Wed, 20 May 2009, Antonio Huete Jimenez wrote: Saifi, Can you please boot with verbose and post here your dmesg? Thanks Antonio Hi: Env: AMD64X2 4400+ processor ASUS M2NMX-SE motherboard 2GB DDR2 RAM 320GB Seagate SATA II NCQ HDD nVidia graphics card nVidia SATA controller nVidia neForce Gigabit ethernet On running the dfly 2.2.1 DVD, the following lines are seen after the boot loader options Mounting root from cd9660: cd0c cd0: invalid primary paritition table: no magic iso_mountroot(): using session at block 0 cd0: invalid primary paritition table: no magic cd9660: Rockridget extension start_init: tryign /sbin/init Loading configuration files. . kern.seedenable: 0 - 1 kern.seedenable: 1 - 0 Starting file system checks: cd9660: /dev/cd0c: Invalid argument In fact the DVD boot process waits here long enough that i'm able to type the above lines by looking at the string :) Any idea what could be reason for this ? The only time these set of lines are seen is when booting with dfly-2.2.1 DVD. thanks Saifi.
Re: cd9660: /dev/cd0c: Invalid argument
On Wed, 20 May 2009, Matthew Dillon wrote: : Mounting root from cd9660: cd0c : cd0: invalid primary paritition table: no magic : iso_mountroot(): using session at block 0 : cd0: invalid primary paritition table: no magic : cd9660: Rockridget extension : start_init: tryign /sbin/init : Loading configuration files. : . : kern.seedenable: 0 - 1 : kern.seedenable: 1 - 0 : Starting file system checks: : cd9660: /dev/cd0c: Invalid argument It's working ok. It's trying to run fsck on the CD, which clearly will not work. That is a known bug but it is harmless. It is not stuck on that step but probably instead working on some later step in the boot process. -Matt Yes, while booting with dfly 2.2.1 DVD, i realized that this is harmless as i could proceed with the installation. However, post installation, on selecting [reboot computer] option from the installer, a bunch of errors keep scrolling on the screen endlessly (some stuff related to cd). The only way to exit that state is to 'hard reset' the box. thanks Saifi.
Re: pkg_radd PKG_PATH
On Wed, 20 May 2009, Matthew Dillon wrote: Not all of our mirrors have all of our top-level softlinks. corecode? Chlamydia is missing a bunch of softlinks. Nearly all the softlinks point to the 2008Q4 package set. -- The issue with 2.3.x (head development) verses 2.2.x (release) is mainly the fact that libc's version got bumped, which creates problems if mixing packages built using 2.2.x with packages built using 2.3.x. -Matt 1. which mirror should i use ? 2. for dfly 2.2.1, there doesnot seem to by any entry at http://mirror.evilprojects.net/pub/DragonFlyBSD/packages/ So far the only packages that have been installed are those from the dfly-2.2.1 DVD from which site can i install 2.2.1 packages ? thanks Saifi.
Re: nb suffix to package names
On Thu, May 21, 2009 at 5:26 PM, Saifi Khan saifi.k...@twincling.org wrote: Hi: Noticed that some of the packages installed from the dfly 2.2.1 DVD have 'nb' suffixes, for example: xconsole-1.0.3nb1 shared-mime-info-0.51nb2 rxvt-unicode-8.3nb4 Two questions here: . what does the 'nb' suffix mean ? . what is the interpretation of the number after 'nb' ? thanks Saifi. Hi Saifi, I think this 'nb' is a NetBSD convention to their software packages - pkgsrc which is what DragonFly is using. Thanks, Archimedes
