Today (Friday) is the last day people can commit to the 2.0 branch.
I would appreciate it if a couple of people could do basic testing of
release builds for 2.0 today (cd /usr/src/nrelease; make installer release).I will be building and testing the final release ISOs Saturday morning
and letting them propagate to our mirrors overnight.The release will be officially announced on Sunday!
-Matt
Matthew Dillon
<dillon@backplane.com>
I think we should hold off the release until packages are built and have
propagated to all mirrors. This might take several days, though.
Packages are large and connectivity is low.cheers
simon
Only two of the package mirrors have even started to update, so it's going
to be a few days until the new build updates, and then more days until all
the files are copied out.pkgbox has a full set of packages - a good chunk of them are built on
1.13, so there will be a warning at install, but that's it. Building from
source (which I think is somewhat more common with pkgsrc) is already an
option in any case. I don't think there's a need to wait.
Ok what am I doing wrong.. I just sync'ed with 2_0 and rebuilt, now
trying to test the release builds.
# uname -a
DragonFly dfly_vm1.ocnetworking.com 2.0.0-RELEASE DragonFly
2.0.0-RELEASE #0: Fri Jul 18 22:56:51 PDT 2008
dylan@dfly_vm1.ocnetworking.com:/usr/obj/usr/src/sys/DFLY1 i386# cd /usr/src/nrelease
{dfly_vm1}
/usr/src/nrelease
# make installer release
Unable to find cdrtools-ossdvd-2.01.1.36nb2.tgz, use the following
command to fetch required packages:
make [installer] fetch
*** Error code 1Stop in /usr/src/nrelease.
{dfly_vm1} /usr/src/nreleasepkg_radd cdrtools-ossdvd-2.01.1.36nb2.tgz
pkg_add: Warning: package
`http://pkgbox.dragonflybsd.org//All/cdrtools-ossdvd-2.01.1.36nb2.tgz'
was built for a different version of the OS:
pkg_add: DragonFly/i386 1.10.1 (pkg) vs. DragonFly/i386 2.0.0 (this host)
pkg_add: package `cdrtools-ossdvd-2.01.1.36nb2' already recorded as
installedDylan
This message tells you that the required package could not be found in
/usr/release/packages, and not that it is not installed.Do make installer fetch.
Sascha
Thanks for reading my error messages for me. I totally misread it...
Its running now....
Dylan
And if you're booting a 2.0 system, please test pkg_radd, too.
Hmm, will you change http://pkgbox.dragonflybsd.org/All/ to point to the
2.0 packages?I wonder, how can we make the All/ redirect handle users of previous
DragonFly releases needing older packages?Sascha
Oh, yeah. Changed now. If someone could test, that would be helpful, as
Well, we could change pkg_radd to build a path using the output of uname,
and then analyze the incoming request path on pkgbox, and then redirect
those requests to the appropriate folder based on that. I'm not going to
get that working in the next 24 hours, though.
Perhaps the version should be part of the path:
http://pkgbox.dragonflybsd.org/2.0/All/
--
Erik Wikström
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
git: | |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
