Fix the port on systems where libusb does not come with the basesystem.
No portrevision bump, no change for the packages where this was building
successfully on pointyhat.
A familiar procedure in any open source project: irritation causes improvement. In this case, the Forth-based boot loader irritated Matthew Dillon into writing a new replacement C-based one. (See the commit too, and it may slightly affect the upgrade process for 2.7 users.)
All these recent locking changes seem to be adding up to a much moreresponsive system, incidentally.
There’s a whole lot of options for bmake, used in pkgsrc, and they aren’t immediately obvious. I’ve linked to a reference before, but it’s no longer at that location. However, I found a new link!
I missed this before, but Gerard van Essen linked to it: there’s a BSD Show! episode from 2010-06-22 with James T. Nixon from PC-BSD, in addition to the other episodes I linked recently.
(I was recorded for the show tonight – it was fun!)
The Professional Certification requirements are now published. (via) The tests happen at various conventions around the world, so plan ahead and you should be able to find one near you.
As I found out directly, upgrading from pkgsrc version 2010Q1 to 2010Q2 has a minor quirk: binary packages for 2010Q2 will refuse to install with an older version of pkg_install. Rebuild pkgtools/pkg_install to the 2010Q2 version and the problem will go away.
Full buildworlds again, as there’s more commits that make it necessary. If you’re running 2.7, you should probably just plan on using buildworld, and not quickworld for rebuilding.
On August 31st, Stuart Henderson (sthen@) announced that the default Python version has changed from 2.5 to 2.6. This was following a commit by Federico G. Schwindt (fgsch@) in the ports tree. Please read on for Federico's full commit message and Stuart's announce:
System data structures have changed again, so make sure your next rebuild is a full buildworld/buildkernel if you’re running 2.7. There’s been a lot of changes to pull more and more out from under the Giant Lock.
happened to notice that recent libkinfo changes broke sysutils/estd. It’s fixed by rebuilding the program, though this may affect a few other packages. This only affects people running bleeding-edge DragonFly 2.7.
All three of the Google Summer of Code Projects for DragonFly are complete and passed! The code for each will show up at the Google-hosted project page in the next week or so. The original proposals for Alex Hornung’s device mapper/LVM, Samuel Greear’s kevent/select/pool work, and David Shao’s GEM/KMS porting are still there on the Google project page for DragonFly.
If you are running DragonFly 2.7, Matthew Dillon has made some kernel changes, so updating your 2.7 machine will require a full buildworld cycle, not quickworld.
The binary packages for 2.6 and 2.7 have been updated to pkgsrc-2010Q2. This means that pkg_radd will automatically pull down newer packages, and you should make sure your /usr/pkgsrc is using the pkgsrc-2010Q2 release if you want to be sure there’s no version mismatches.
I know it's a bit late in the month but Augusts London *BSD meeting will be held at the Cleveland Arms pub in Bayswater on Thursday the 26th, 7pm
If you use upcoming, you can find the meeting details here
Theo de Raadt (deraadt@) has tagged 4.8-current. This means that we are one step closer to the upcoming OpenBSD 4.8 release. Keep an eye out for pre-orders! Read below for the full commit message:
When I think about the names of people on mailing lists who have helped
me solve difficult problems or learn something new, often I have no face
to go with the name. In my day to day life I may have walked right past
them without knowing, or saying hello, or more appropriately, asking to
buy them a beer or lunch as a way to say thanks for the help they've
given me. If you've been communicating with someone for years via email
or even phone, and you finally get the chance to meet them in person, it
is always an strange combination of both fun and unusual, or more
accurately, both familiar and unfamiliar. It's the contradiction that
seems a bit troublesome at first, but it fades quickly. There's a lot of
this for people attending their first hackathon, but even those who have
attended many hackathons probably experience a little of it due to the
new people they're going to meet for the first time.
Wondering "Who are these people?" is only natural but keeping
the event organized really does help. A great deal of thought and
effort goes into planing and organizing each hackathon. One of the smart
things done is keeping a master list of arrival and departure flights so
people can coordinate meeting, sharing rides and similar. From the
master list, I knew I would be on the same flight from SFO
as Chris Kuethe (ckuethe@), so we traded emails to confirm and just
assumed we'd figure it out at the airport gate.
Knowing one of the developers would be on the same flight was
reassuring. I almost never travel and this was the first time in almost
a decade where I was traveling alone without the assistance of a family
member or friend. As a novice traveler and first time hackathon
attendee, I made plenty of poor decisions in picking out what to bring
and I seriously over-packed for the trip. Showing you how stupid I was
may save you from making similar mistakes.
