crashed during bulk build
The build got up to octave [4002/12503] and the computer crashed and dumped core. I think it's because I was trying to kill a process, of which there should be at most one because it's a cron job, of which there were eleven, and then ran pidof to see if any new ones had popped up. I will, as I said, try to figure out how to resume the build. The disk fullness of that partition is 66%. The disk usage shouldn't be anywhere near that, but it might be. There was an orphaned process called lt-autogen, left over from one of the previously built packages, that was hogging the CPU. Once I figured out that its working directory was inside the build, but its parent was init, I killed it. It may have been writing a huge file, which I'll have to find and delete before trying to copy the entire build directory. The next quarter starts in two weeks, so there isn't much point in me actually finishing this build. But I will make it possible for Justin, John, or anyone else to resume a build if the computer crashes for reasons unrelated to the build. Pierre -- li fi'u vu'u fi'u fi'u du li pa
Re: bulk build
On Tuesday 05 June 2012 19:47:07 Justin Sherrill wrote: Your computer crashed during the build too, possibly from the same issue. I don't think you are going to get any farther than I did. I'm up to 2776, and 2485 was SDL_gfx as before, so I got farther than I did, and the crash was not caused by anything in the package being built. If it crashes again, I'll copy the build directory and try to figure out how to resume. Pierre -- lo ponse be lo mruli po'o cu ga'ezga roda lo ka dinko
Re: bulk build was: computer hung
On Tuesday 05 June 2012 09:26:34 Justin Sherrill wrote: If you're having problems with a couple packages not rebuilding, the fix is not going to be building 12500 additional packages. If there's specific packages you can't get to upgrade, looking at the errors for those exact items will do you a lot more good. I've always upgraded with binary packages, except this once and while I was using Source Mage Linux several years ago. Binaries are built from the bottom up; pkg_rolling-replace can run into trouble when a package whose name has changed, and which it therefore doesn't know how to replace, depends on a package that conflicts with a new package that it's building. I had such trouble with the Python packages. The default python in 2012Q1 is 2.7; previously it was 2.6, and I had lots of build failures because of it. pkgin handles this pretty well, but pkg_rolling-replace doesn't. If I run clean.sh -q, will that continue where it left off instead of rebuilding most of the already built packages? Hopefully I'll have learned how to finish a bulk build by the time 2012Q2 is out. Pierre -- li fi'u vu'u fi'u fi'u du li pa
Re: bulk build was: computer hung
On Tue, Jun 5, 2012 at 2:43 PM, Pierre Abbat p...@phma.optus.nu wrote: On Tuesday 05 June 2012 09:26:34 Justin Sherrill wrote: If you're having problems with a couple packages not rebuilding, the fix is not going to be building 12500 additional packages. If there's specific packages you can't get to upgrade, looking at the errors for those exact items will do you a lot more good. I've always upgraded with binary packages, except this once and while I was using Source Mage Linux several years ago. Binaries are built from the bottom up; pkg_rolling-replace can run into trouble when a package whose name has changed, and which it therefore doesn't know how to replace, depends on a package that conflicts with a new package that it's building. I had such trouble with the Python packages. The default python in 2012Q1 is 2.7; previously it was 2.6, and I had lots of build failures because of it. pkgin handles this pretty well, but pkg_rolling-replace doesn't. If I run clean.sh -q, will that continue where it left off instead of rebuilding most of the already built packages? Hopefully I'll have learned how to finish a bulk build by the time 2012Q2 is out. You're still going to end up building 12,500 packages. The -q option just doesn't update the pkgsrc files, which makes the startup time a bit shorter. You are going down the wrong path for what you want to do. If you want to rebuild your python packages, write down the ones you have installed, remove the ones you have now, and reinstall. You may be able to to do this with a few commands with pkg_chk.
Re: bulk build was: computer hung
On Tuesday 05 June 2012 16:15:15 Justin Sherrill wrote: You're still going to end up building 12,500 packages. The -q option just doesn't update the pkgsrc files, which makes the startup time a bit shorter. You are going down the wrong path for what you want to do. No I'm not. What I want to do is build all the packages, so that anyone who wants to upgrade can do so easily. What is the correct way to restart a bulk build where it left off? Who's going to build the packages for 2012Q2, since your computer has crashed? If you want to rebuild your python packages, write down the ones you have installed, remove the ones you have now, and reinstall. You may be able to to do this with a few commands with pkg_chk. I have no idea what they do; they must have been installed as dependencies of something else. I don't know why the default was switched to 2.7. I do know that upgrading with pkgin is easy and takes a few hours, while upgrading with pkg_rolling-replace takes weeks and is prone to failure, and the system is hosed, as far as running some programs is concerned, while it's upgrading. Pierre -- li ze te'a ci vu'u ci bi'e te'a mu du li ci su'i ze te'a mu bi'e vu'u ci
Re: bulk build
On Tuesday 05 June 2012 16:59:53 Pierre Abbat wrote: What is the correct way to restart a bulk build where it left off? I found this in the man page of pbulk-build: It then writes suc- cessful builds to success and failing builds to error. If either success or error exists at start-up, they are read and the build continues where they left off. These files are in /olv/pbulk/bulklog/meta/. When I started the build, after a while it said something that it would wait five seconds and then delete something. Pierre -- Don't buy a French car in Holland. It may be a citroen.
Re: bulk build was: computer hung
On Jun 5, 2012 5:03 PM, Pierre Abbat p...@phma.optus.nu wrote: No I'm not. What I want to do is build all the packages, so that anyone who wants to upgrade can do so easily. What is the correct way to restart a bulk build where it left off? Who's going to build the packages for 2012Q2, since your computer has crashed? Your computer crashed during the build too, possibly from the same issue. I don't think you are going to get any farther than I did.
Re: bulk build was: computer hung
On Tuesday, June 05, 2012 07:47:07 PM Justin Sherrill wrote: Your computer crashed during the build too, possibly from the same issue. I don't think you are going to get any farther than I did. Ah. I understood that you had a failure such as a head crash or a burned-out motherboard that made it unusable. If it crashed from a random event, not from a bug in the compiler triggered by a particular package, it should be possible to restart the build. There is a way to restart pbulk-build and have it continue where it left off; it shouldn't be too hard to implement it in simplepbulk. Pierre -- li fi'u vu'u fi'u fi'u du li pa
the partition I'm doing the bulk build on
# du -s * 7 COPYRIGHT 0 IN_CHROOT 10037 bin 839 boot 1 build.sh 51972 bulklog 0 compat 0 dev 2782472 distfiles 9477etc 0 home 0 media 0 mnt 2059650 packages 0 proc 1 root 35711 sbin 3 settings.conf 0 sys 0 tmp du: usr/pkg/libexec: No such file or directory du: usr/pkg/sbin: No such file or directory du: usr/pkg/lib: No such file or directory du: usr/pkg/bin: No such file or directory du: usr/pkg/etc: No such file or directory du: usr/pkg/info: No such file or directory du: usr/pkg/man: No such file or directory du: usr/pkg/share: No such file or directory du: usr/pkg/include: No such file or directory du: usr/pkg: No such file or directory 711245 usr 26198 var 167870 wrkobjdir # df . Filesystem1K-blocks Used Avail Capacity Mounted on /crypt/pfs/@@-1:1 453435392 117572512 33586288026%/olv /olv has no snapshots. Why is so much more space used than in files? Pierre -- The Black Garden on the Mountain is not on the Black Mountain.
Re: the partition I'm doing the bulk build on
On Fri, 01 Jun 2012 14:13:48 +0200, Pierre Abbat p...@phma.optus.nu wrote: # du -s * 7 COPYRIGHT 0 IN_CHROOT 10037 bin 839 boot 1 build.sh 51972 bulklog 0 compat 0 dev 2782472 distfiles 9477etc 0 home 0 media 0 mnt 2059650 packages 0 proc 1 root 35711 sbin 3 settings.conf 0 sys 0 tmp du: usr/pkg/libexec: No such file or directory du: usr/pkg/sbin: No such file or directory du: usr/pkg/lib: No such file or directory du: usr/pkg/bin: No such file or directory du: usr/pkg/etc: No such file or directory du: usr/pkg/info: No such file or directory du: usr/pkg/man: No such file or directory du: usr/pkg/share: No such file or directory du: usr/pkg/include: No such file or directory du: usr/pkg: No such file or directory 711245 usr 26198 var 167870 wrkobjdir # df . Filesystem1K-blocks Used Avail Capacity Mounted on /crypt/pfs/@@-1:1 453435392 117572512 33586288026%/olv /olv has no snapshots. Why is so much more space used than in files? What did you do to have no snapshots on /olv? If you turned off the nightly cleanup then it has probably accumulated fine grained history. Sascha
Re: the partition I'm doing the bulk build on
On Friday 01 June 2012 15:08:51 Sascha Wildner wrote: What did you do to have no snapshots on /olv? If you turned off the nightly cleanup then it has probably accumulated fine grained history. -bash-4.2$ hammer config /olv snapshots 0d 0d prune 1d 5m rebalance 1d 5m dedup 1d 5m reblock 1d 5m recopy29d 10m Before I started the bulk build, it finished hammer in less than an hour. It now takes half a day or more. I just ran ps and got this: -bash-4.2$ ps waux|grep hammer phma71667 40.0 0.1 4144 1224 0 DLM+5:02PM 0:00.05 grep hammer root -1 0.0 0.0 0 0 ?? BLMFri09PM 1:19.40 (hammer-S0) root -1 0.0 0.0 0 0 ?? BLMFri09PM 1:17.04 (hammer-S2) root -1 0.0 0.0 0 0 ?? BLMFri09PM 15:10.97 (hammer-S0) root -1 0.0 0.0 0 0 ?? BLMFri09PM 15:13.26 (hammer-S2) root -1 0.0 0.0 0 0 ?? BLMFri09PM 2:42.42 (hammer-M) root -1 0.0 0.0 0 0 ?? BLMFri09PM 2:09.76 (hammer-S1) root -1 0.0 0.0 0 0 ?? BLMFri09PM 2:09.95 (hammer-S3) root -1 0.0 0.0 0 0 ?? BLMFri09PM 37:42.95 (hammer-M) root -1 0.0 0.0 0 0 ?? BLMFri09PM 16:38.14 (hammer-S1) root -1 0.0 0.0 0 0 ?? BLMFri09PM 16:51.96 (hammer-S3) root38834 0.0 0.0 2252124 ?? ILM 1:02AM 0:00.01 /bin/sh /etc/periodic/daily/160.clean-hammer root38836 0.0 0.0 1160 20 ?? ILM 1:02AM 0:00.55 hammer cleanup root79725 0.0 7.9 190584 81384 ?? DLM 1:45AM 11:17.88 hammer -t 300 dedup /olv Pierre -- The Black Garden on the Mountain is not on the Black Mountain.
Re: computer got hung while doing bulk build
On Thursday 24 May 2012 14:58:32 Justin Sherrill wrote: If you're using my simplepbulk script, run clean.sh again without the -a qualifier, and it'll rescan and restart with only unbuilt packages. Also, this will possibly happen again. I've had trouble getting builds to finish due to bug 2296, I think it is. It resumed, but not where it left off: .. 10500/10590 .. 10550/10590 10590/10590 Resolving... Global dependency resolution failed, check /bulklog/meta/presolve-err.log for details Building... Initialisation complete. [436/12503] Starting build of digest-2004 [436/12503] Successfully built digest-2004 [437/12503] Starting build of f2c-20100903 [437/12503] Successfully built f2c-20100903 Pierre -- sei do'anai mi'a djuno puze'e noroi nalselganse srera
computer got hung while doing bulk build
I brought up Firefox (I had been doing it on the laptop, but I took it out last night and will take it out tonight) and Gimp on darner. Also hammer has been running over 13 hours, which is highly unusual; usually it takes 20 or 40 minutes. I have over 70 GB on the disk that holds the bulk build. The computer hung. On the window that's showing the bulk build, I see this: [1736/12501] Starting build of tex-pst-3dplot-1.94 [1736/12501] Failed to buildtex-pst-3dplot-1.94 [1752/12501] Starting build of farsight2-0.0.26nb6 Read from remote host darner: Connection reset by peer Connection to darner closed. I have to reboot darner. How do I resume the bulk build? Pierre -- When a barnacle settles down, its brain disintegrates. Já não percebe nada, já não percebe nada.
Re: computer got hung while doing bulk build
On Thu, May 24, 2012 at 2:38 PM, Pierre Abbat p...@phma.optus.nu wrote: I brought up Firefox (I had been doing it on the laptop, but I took it out last night and will take it out tonight) and Gimp on darner. Also hammer has been running over 13 hours, which is highly unusual; usually it takes 20 or 40 minutes. I have over 70 GB on the disk that holds the bulk build. The computer hung. On the window that's showing the bulk build, I see this: [1736/12501] Starting build of tex-pst-3dplot-1.94 [1736/12501] Failed to build tex-pst-3dplot-1.94 [1752/12501] Starting build of farsight2-0.0.26nb6 Read from remote host darner: Connection reset by peer Connection to darner closed. I have to reboot darner. How do I resume the bulk build? If you're using my simplepbulk script, run clean.sh again without the -a qualifier, and it'll rescan and restart with only unbuilt packages. Also, this will possibly happen again. I've had trouble getting builds to finish due to bug 2296, I think it is.
bulk build for 2010Q4 progress
Here's the state of the bulk build for pkgsrc-2010Q4: DragonFly 2.8/i386: 5864 packages built so far DragonFly 2.8/x86_64: 10304 packages built so far DragonFly 2.9/i386: 3144 packages built so far DragonFly 2.9/x86_64: All 10483 packages done - uploading now. The report from the 2.9/x86_64 build is below, for the curious. -- pkgsrc bulk build report DragonFly 2.9/x86_64 Compiler: gcc Build start: 2011-01-20 02:49 Build end: 2011-01-20 15:37 Full report: http://avalon.dragonflybsd.org/reports/x86_64/2.9/20110120.0249/meta/report.html Machine readable version: http://avalon.dragonflybsd.org/reports/x86_64/2.9/20110120.0249/meta/report.bz2 Total number of packages: 10381 Successfully built: 8555 Failed to build: 379 Depending on failed package: 813 Explicitly broken or masked: 559 Depending on masked package:75 Packages breaking the most other packages Package Breaks Maintainer - lang/ruby19-base 325 t...@netbsd.org security/heimdal 233 pkgsrc-us...@netbsd.org multimedia/xine-lib 59 pkgsrc-us...@netbsd.org lang/ocaml35 a...@netbsd.org lang/mono 29 kef...@netbsd.org multimedia/py-gstreamer0.10 22 pkgsrc-us...@netbsd.org net/gupnp-igd 19 pkgsrc-us...@netbsd.org textproc/xerces-c 18 pkgsrc-us...@netbsd.org graphics/gimp 15 a...@netbsd.org graphics/sane-backends13 pkgsrc-us...@netbsd.org Build failures Package Breaks Maintainer - archivers/star uebay...@netbsd.org audio/akode-plugins-mpc ha...@netbsd.org audio/buzztard 1 pkgsrc-us...@netbsd.org audio/daapd nath...@netbsd.org audio/liblastfm1 pkgsrc-us...@netbsd.org audio/maplay pkgsrc-us...@netbsd.org audio/ncmpc pkgsrc-us...@netbsd.org audio/sox 11 pkgsrc-us...@netbsd.org audio/taglib-extras1 pkgsrc-us...@netbsd.org benchmarks/iozonepkgsrc-us...@netbsd.org benchmarks/libmicro pkgsrc-us...@netbsd.org benchmarks/netperf pkgsrc-us...@netbsd.org benchmarks/randread pkgsrc-us...@netbsd.org biology/gromacs pkgsrc-us...@netbsd.org biology/rasmol pkgsrc-us...@netbsd.org cad/magicpkgsrc-us...@netbsd.org cad/tnt-mmtl dmcmah...@netbsd.org chat/ejabberdpkgsrc-us...@netbsd.org chat/galepkgsrc-us...@netbsd.org chat/silc-client 1 s...@netbsd.org chat/silc-server s...@netbsd.org chat/tircpkgsrc-us...@netbsd.org chat/unrealircd pkgsrc-us...@netbsd.org comms/asterisk16 jnem...@netbsd.org comms/libopensync-plugin-syncml di...@netbsd.org comms/mgetty+sendfax pkgsrc-us...@netbsd.org comms/modemd tsa...@netbsd.org comms/tn3270 pkgsrc-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-msdosdjgpppkgsrc-us...@netbsd.org databases/clisp-gdbm a...@inbox.ru databases/couchdbfi...@joyent.com databases/rrdtool 11 pkgsrc-us...@netbsd.org databases/sqlite3-tclpkgsrc-us...@netbsd.org devel/avltreewrstu...@netbsd.org devel/binutils pkgsrc-us...@netbsd.org devel/clisp-pcre a...@inbox.ru devel/clisp-syscalls a...@inbox.ru devel/clisp-zlib a...@inbox.ru devel/electric-fence pkgsrc-us...@netbsd.org devel/elfsh pkgsrc-us...@netbsd.org devel/ethos pkgsrc-us...@netbsd.org devel/gsoap chrisware...@chriswareham.demon.co.uk devel/gtl
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
pkgsrc bulk build question
Hi, is anyone using the bulk build script mk/bulk/build successfully on DragonFly? After setting up a chroot environment and bootstrapping I can manually build packages, but sh mk/bulk/build gives me (after a while): Complete dependency database left in /usr/pkgsrc/.bulk_db Appending to database in /usr/pkgsrc/.bulk_db bmake: don't know how to make print-summary-data. Stop *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc mk/bulk/build: error: Could not create the bulk build cache. Any ideas? Regards, Johannes PS: Are there any prebuilt Q12009 packages available?
Re: pkgsrc bulk build question
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
pkgsrc bulk build results
hey, i finally finished the pkgsrc bulk build for 1.10 and these are the results: http://chlamydia.fs.ei.tum.de/~corecode/unsorted/bulkbuild/20070726.2220/meta/report.html There is quite some breakage, please go down the list and check if you can fix an issue for the package you'd like to be available as binary package. The fixes can be on the DragonFly side (broken interface, bad declaration, whatever) or on the pkgsrc side. However please do not contact me for pkgsrc patches, I don't have time and I can't commit them. I'll upload the packages soon. Thanks for your attention. simon -- Serve - BSD +++ RENT this banner advert +++ASCII Ribbon /\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
pkgsrc bulk build results
I completed two pkgsrc bulk builds. The following is from the report it generated. (The first bulk build reporting didn't work.) The actual count of packages I see on the system is 2851 packages. Some significant packages that were packaged: apache 1 perl xorg-server thttpd stunnel-4 ORBit2 Mesa SDL (and many SDL-*) afterstep aspell bash (23) bluefish cdparanoia cdrecord (needs to be renamed to cdrtools) curl cvs daemontools db4 djbdns docbook (and docbook-*) elinks enlightenment evince exim fontconfig gaim gawk ggv ghostscript-afpl ghostscript-gnu gimp gmake many gnome packages icewm ircII ispell-base joe jed jove kdelibs libglade2 libgnome lua lynx lyx-qt mhonarc mplayer mutt mysql-client nautilus nedit nessus-core openbox openldap openmotif many perl modules many python modules python 1.5 python 2.3 python 2.4 qt3-libs qt3-tools rox rsync rxvt samba 3 screen scribus sodipodi solid-pop3d spamassassin speex sqlite3 squirrelmail swig teTeX 2 teTeX-bin-3 ted tuxpaint unzip vim vim-gtk vncviewer webalizer wget windowmaker xfce4 xorg xpdf xterm zip (Reminder to me: fix blackbox :) I know for sure that many other packages will successfully package, but since running as non-root different, non-DragonFly, issues come up. (Soon I will start a build as root.) This includes a few uncommitted patches. Summary: Build started: Mon Aug 29 19:45:33 2005 GMT Build ended:Wed Aug 31 03:36:14 2005 GMT Successfully packaged: 2902 Packages really broken: 1037 Pkgs broken due to them:1270 Total broken: 2307 Not packaged: 314 Total: 2621 ... Top Ten Offenders PackageBreaks Maintainer -- lang/tcl 139 [EMAIL PROTECTED] graphics/netpbm103 [EMAIL PROTECTED] lang/ruby18-base 75 [EMAIL PROTECTED] x11/kdebase3 75 [EMAIL PROTECTED] graphics/gdk-pixbuf56 [EMAIL PROTECTED] www/apache 56 [EMAIL PROTECTED] audio/xmms 48 [EMAIL PROTECTED] lang/python21 46 [EMAIL PROTECTED] converters/wv2 44 [EMAIL PROTECTED] textproc/libxml44 [EMAIL PROTECTED] Jeremy C. Reed BSD News, BSD tutorials, BSD links http://www.bsdnewsletter.com/
Re: pkgsrc bulk build results
This is great! Keep up the good work! -- - Liam J. Foy [EMAIL PROTECTED] http://www.bsd-systems.co.uk
Re: pkgsrc bulk build results
Jeremy C. Reed wrote: I completed two pkgsrc bulk builds. The following is from the report it generated. (The first bulk build reporting didn't work.) hey this looks really great! is this the standard output of a pkgsrc bulk run? Or did you do some serious scripting yourself? cheers simon -- Serve - BSD +++ RENT this banner advert +++ASCII Ribbon /\ Work - Mac +++ space for low $$$ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Re: pkgsrc bulk build results
On Wed, 31 Aug 2005, Simon 'corecode' Schubert wrote: I completed two pkgsrc bulk builds. The following is from the report it generated. (The first bulk build reporting didn't work.) hey this looks really great! is this the standard output of a pkgsrc bulk run? Or did you do some serious scripting yourself? Have a look at http://mail-index.netbsd.org/pkgsrc-bulk/ to see real examples of the reports. I didn't link to my report for a few reasons: it was not archived yet, didn't want people to assume they shoujld use my /home/reed-hardcoded packages, and I didn't want people to needlessly suck up bandwidth from leaf as I read it has limited bandwidth. Jeremy C. Reed BSD News, BSD tutorials, BSD links http://www.bsdnewsletter.com/
Re: pkgsrc bulk build results
On Wed, Aug 31, 2005 at 12:00:17AM -0700, Jeremy C. Reed wrote: PackageBreaks Maintainer -- lang/tcl 139 [EMAIL PROTECTED] What's broken with this? I thought I had the necessary patches in my patch set. graphics/netpbm103 [EMAIL PROTECTED] Hm. What is broken here? lang/ruby18-base 75 [EMAIL PROTECTED] Patched in my patchset, not upstream. x11/kdebase3 75 [EMAIL PROTECTED] Same. graphics/gdk-pixbuf56 [EMAIL PROTECTED] I thought I had a patch for that once in the past. How does it break? www/apache 56 [EMAIL PROTECTED] Is that apache 1.3 or 2.0? 2.0 should work. audio/xmms 48 [EMAIL PROTECTED] I know that it did work before, but I don't have the results of my last run. lang/python21 46 [EMAIL PROTECTED] Should be as simple as applying the same patches as for the python2.3. converters/wv2 44 [EMAIL PROTECTED] No idea at the moment, not sure whether I had it working before. textproc/libxml44 [EMAIL PROTECTED] Don't know about this either. Joerg
Re: pkgsrc bulk build results
: :On Wed, 31 Aug 2005, Simon 'corecode' Schubert wrote: : : I completed two pkgsrc bulk builds. The following is from the report it : generated. (The first bulk build reporting didn't work.) : : hey this looks really great! : : is this the standard output of a pkgsrc bulk run? Or did you do some serious : scripting yourself? : :Have a look at http://mail-index.netbsd.org/pkgsrc-bulk/ to see real :examples of the reports. : :I didn't link to my report for a few reasons: it was not archived yet, :didn't want people to assume they shoujld use my /home/reed-hardcoded :packages, and I didn't want people to needlessly suck up bandwidth from :leaf as I read it has limited bandwidth. : : Jeremy C. Reed : :BSD News, BSD tutorials, BSD links :http://www.bsdnewsletter.com/ The report shouldn't eat up all that much bandwidth (at least not compared to e.g. downloading the package sources), so I wouldn't worry about it. -Matt Matthew Dillon [EMAIL PROTECTED]
Re: pkgsrc bulk build results
On Wed, 31 Aug 2005, Matthew Dillon wrote: The report shouldn't eat up all that much bandwidth (at least not compared to e.g. downloading the package sources), so I wouldn't worry about it. The report links to the build logs which are many megabytes in size, totalling: 573M/unused3/reed/pkgsrc/DragonFly/pkgstat/20050829.0729 646M/unused3/reed/pkgsrc/DragonFly/pkgstat/20050830.2036 I will be removing old logs, but they are useful to show pkgsrc developers where it last failed. Jeremy C. Reed BSD News, BSD tutorials, BSD links http://www.bsdnewsletter.com/
Re: pkgsrc bulk build results
On 31 Aug 2005, Joerg Sonnenberger wrote: PackageBreaks Maintainer -- lang/tcl 139 [EMAIL PROTECTED] What's broken with this? I thought I had the necessary patches in my patch set. I haven't used all of your patches yet. And this bulk build was started before some patches were put in place. graphics/netpbm103 [EMAIL PROTECTED] Hm. What is broken here? error: invalid lvalue in assignment Due to newer gcc I think. I already found and tested fix. Will commit soon. ... graphics/gdk-pixbuf56 [EMAIL PROTECTED] I thought I had a patch for that once in the past. How does it break? I tested your patch and will commit. www/apache 56 [EMAIL PROTECTED] Is that apache 1.3 or 2.0? 2.0 should work. This is 1. This failed due to vulnerabilty check. We need to find if there is a security issue and fix. converters/wv2 44 [EMAIL PROTECTED] No idea at the moment, not sure whether I had it working before. configure isnan detection problem. I don't know but I reported to wv2 bugzilla. Workaround is: CONFIGURE_ENV+=ac_cv_lib_m_isnan=yes textproc/libxml44 [EMAIL PROTECTED] Don't know about this either. I used distfile already on machine which was wrong size (partial download I assume). This is working now. As I find issues, I look in your pkgsrc.diff. It is much appreciated! Jeremy C. Reed technical support remote administration http://www.pugetsoundtechnology.com/
