If you’re like me, you’ve been using XMMS for music playback since just about forever. It’s ancient, though. It uses GTK1, and since Thomas Klausner is trying to get GTK1 dependencies out of pkgsrc, he listed a roundup of alternatives on the pkgsrc-users mailing list, most/all of which are in pkgsrc. Pouya Tafti added some more.
Thomas Klausner is planning to get rid of the last bits of GTK1 in pkgsrc, which means some old/non-updated software has to go too. Speak up on the firstname.lastname@example.org mailing list if you need some of that listed software, or (better yet) provide patches to move it to GTK2.
So, I felt lucky recently. I updated shiningsilence.com from DragonFly 2.6 to DragonFly 2.8, and wanted to upgrade my pkgsrc packages from pkgsrc-2010Q3 to pkgsrc-2010Q4.
You can do this with pkg_rolling-replace, or various other tools, but I wanted to see if I could do it completely with binary packages. I used pkg_radd -uv <pkgname> for each of the major packages I had installed.
Surprisingly, it worked, for every package. I had to force-install some Perl modules because I was moving from 5.10 to 5.12, but I think I may have been able to use an additional -u switch to get by that problem. I did use pkg_leaves to identify packages I didn’t need, and removed them to reduce the number of items to upload.
It was exactly what I wanted. Previous pkgsrc upgrades had taken most of a day, as I had to build from source and figure out what went where. We’ve had a better success rate in bulk builds recently, and this paid off in an upgrade process that only took perhaps an hour.
If you’ve ever installed pkgsrc packages from source, you probably typed ‘bmake install’. There’s a ‘bin-install’ target that will use binary packages if they are available, but you have to set the appropriate environment variables to do so.
It’s now much easier, on DragonFly. If you have pkgsrc-current as of yesterday or later, or pkgsrc-2011Q1 when it arrives, you can type ‘bmake bin-install’ for a pkgsrc application and it will download the binary package automatically, if it’s available, and build from source if it’s not.
This is a setup I’ve wanted for a while – the speed of a binary install, plus a fallback if the binary isn’t available.
They’re finally uploaded! See my rather lengthy post about it on users@ for all the details.
The pkgsrc-2010Q4 branch is now available in DragonFly’s git repo, via ‘git checkout pkgsrc-2010Q4′ in /usr/pkgsrc. Enjoy!
Here’s where the binary build is: summarized in a post to users@. So far so good…
avalon.dragonflybsd.org, also known as mirror-master.dragonflybsd.org, is back up at a new location, with new disks and new connectivity. pkg_radd should work by default again, as should git.dragonflybsd.org.
Here’s the state of my build of pkgsrc-2010Q4 packages:
- DragonFly 2.8/i386 – in progress
- DragonFly 2.8/x86_64 – in progress
- DragonFly 2.9/i386 – just started (happens on Avalon)
- DragonFly 2.9/x86_64 – in progress
So it will be some days yet… building over 4000 packages total is never quick.
Normally I hold this for Sunday, but I’ve got a good batch of links already. Something here for everyone, this week.
- A git cheatsheet, and another git cheatsheet. I may have linked to the latter one before, as it looks vaguely familiar. Anyway, bookmark. (Thanks, luxh on EFNet #dragonflybsd)
- What should you do about bad blocks on a disk? Get a new disk.
- If you ever wanted to port software, there’s a pkgsrc developer’s guide (thanks Francois Tigeot) that shows you how.
- It’s NOT LINUX, for the billionth time. It’s BSD UNIX (certified, even) under there!
- “Children of the Cron“. An entertaining pun. (via)
- Nothing to do with BSD, or even computers, really: Gary Gorton, interviewed about the recent financial crisis, at a Fed bank website (!?). Interesting because I like economic matters, and because it’s the first web page where I’ve ever seen pop-up links added usefully, as a sort of footnote that you don’t have to scroll. (via)
- Michael Lucas recently had a machine broken into. Since everything on the machine is suspect, he’s using Netflow data to figure out when it happened, and how, which is not surprising given his most recent book. He has two posts describing how he backtracks his way to the probable source.
If you run pkgsrc-current, not the quarterly releases, the png library has just been updated to 1.5. This may break a few applications for now, and require a lot of rebuilding on your next update, since many packages depend on this.
If you are running a quarterly release of pkgsrc, you are unaffected.
Aleksey Cheusov is putting together a package manager for pkgsrc, called nih. (For “Not Invented Here”). It’s binary-only at this point, so you’d need to run distbb or pbulk to generate packages, or download from avalon.dragonflybsd.org.
The planned freeze is underway; so pkgsrc-2010Q4 should arrive soon. How soon? January 1st, if it’s by the traditional schedule.
I never really noticed this before, but it’s possible to include your own patchsets into pkgsrc and have them picked up as part of the build process, using $LOCALPATCHES.
Somehow I ended up with a zillion links for this week’s Lazy Reading. I hope you’ve got some spare time for this… Let’s get right into it:
- Michael Lucas, BSD book author (see links on site), has started Twittering. He’s also found the Wikileaks/NetBSD association that I didn’t know about, as Julian Assange even shows up in the NetBSD fortunes file. Also, while linking to his blog, I’ll point at his post on “Write what you don’t know“. Think of that article next time you feel you don’t know enough to contribute to something – especially open source.
- There’s a lengthy dialog on the email@example.com mailing list about pkgsrc, and “Making it easier to get and use pkgsrc“. You can follow the whole thread on the listing page. I am all for the idea. Everybody and their brother has an App Store these days. Ports/pkgsrc are perhaps the original app store ideas, and I’d like to see them brought to the same level as these commercial entitites. This is important: pkgsrc is perhaps the only app store equivalent in existence that is not tied to a platform; that exists only to get you software rather than to provide a way to tie a platform into its developers profits.
- Hey, a roguelike zombie apocalypse game! Aw, it’s Windows-only.
- Mikel King has an editorial that sums up the many places BSD serves as an underpinning to products – a good checklist, if you don’t know of them. He’s also written an instructional article on passwordless/SSH setup.
- Along the same lines, Promote Perl by Building Great Things. This applies to BSD products too; telling people it’s great doesn’t work as well as making something great and showing that a BSD system is part of what makes it so.
- Did you know there are even BSD Certification classes in Iran? I really need to do that… though probably not at that location.
- Yacc is not dead. (via) I link to this because I had a moment of nerd excitement realizing that blog’s title is intended to look like a bang path.
- Database design ideas. There’s been a good series of posts there lately, good for anyone wanting to move beyond the basic CRUD details.
The utility pkg_add has a -u option that tells it to upgrade any existing matched package with a given binary package. Since pkg_radd passes options on to the underlying use of pkg_add, after automatically setting a remote repository for binary files, pkg_radd -u <packagename> tells pkg_add to automatically find and upgrade a package.
I never thought this would work. However, I’m building a package on a system that has pkgsrc-2010Q1 packages installed, but a pkgsrc-2010Q3 /usr/pkgsrc. Every time I’ve encountered an error because installed software was too low a version, pkg_radd -uv <package_name> has resulted in a quick upgrade.
I’m not recommending this as a new upgrade method; I’m noting how unexpectedly well this experiment is going. It may be just blind luck, but this sure would be nice if it ‘just worked’.
A number of people have encountered this: while installing some larger pkgsrc package, the process stops on a strange DocBook error. Alex Hornung has a fix: symlink /usr/pkg/etc/xml/catalog to /usr/pkg/share/xml/catalog.
Alex Hornung has some patches that allow KDE4 to build on DragonFly. They aren’t in pkgsrc and not all in KDE yet, so try them out directly if you want KDE4, for now.
Update: based on something Alex said on IRC… they’re in KDE4 now.
Chris Turner wrote some notes about building pkgsrc packages in a chroot, including the handy tip of using
to run and display a GUI-using app under the chroot.
Our mirror of the never-quite-official git repository for pkgsrc is being rebuilt, so it will be temporarily inaccessible. Matthew Dillon is working on building a new one directly from pkgsrc CVS, which will have a different link.
Update: It’s finished. Matthew Dillon’s posted a summary of the changes and what you need to update in order to use it.
I’ve drastically revamped the pkgsrc howto on the dragonflybsd.org website. It’s also linked in that site’s menu, too. Comments please!
A bump in shared library version for libssl/libcrypto means that any programs dependent on it will require a rebuild – including any pkgsrc programs.
This only affects you if you are running 2.7, for now. It means that on upgrading from 2.6 to 2.8, any libssl-using programs will need to be updated. This may not be a big thing, since pkgsrc-2010Q3 will also be out and people will want to upgrade anyway.
A small crop for Lazy Reading this week – oh well.
- Bad things about SVN. I’ve always thought git is more interesting, but subversion is easier. Oh well. The article is also fun for the unfiltered Windows-hate.
- At least this hasn’t happened yet with pkgsrc.
- What happens if you put your hand in the way of the Large Hadron Collider beam? (via)
I’ve noticed that if you have older pkgsrc packages installed, and install binary packages for pkgsrc-2010Q2, those packages will refuse to install if pkg_install is an older version than what they were built with.
I ended up force-deleting pkg_install and bmake, and reinstalling by running pkgtools/bootstrap/bootstrap. There may be better solutions; I’m mentioning it now since it’s a known problem.
Update: “bmake replace USE_DESTDIR=yes” was suggested by Joerg Sonnenberger. “pkg_add -u /path/to/newer/pkg_install” should also work (untested).
This will probably apply to the upcoming pkgsrc-2010Q3, too. Building from source is a workaround for now.
Starting September 23rd, pkgsrc will freeze (i.e. bugfixes only) in preparation for the 2010Q3 release, which is planned for one week later, instead of the usual 2 weeks. This release will include some very new software like Postgres 9, too.
Some time ago, there was an application called pkgmanager, available in pkgsrc-wip. It worked by tracking ‘wanted’ packages in pkgsrc, and upgrading based on that list. It hasn’t been updated in some time, however, and may not even build.
‘Rumko’ has written a replacement, called rpkgmanager. The Gitorious page linked in the previous sentence includes the URL to download the code via Git, so it’s available to try now even though it’s not yet in pkgsrc.
I totally meant to post this yesterday. Oops!
- We’re using toeplitz. I just like the name; I don’t understand how it works.
- The idea of software forks has been around since, oh, BSD and System V Unix diverged, if not earlier. Here’s an article that talks about forking in general, rather breathlessly. After reading that, read this perhaps more accurate fork parody. (via)
- You know what we could use for pkgsrc, and all the other port/package collections? Explanation. They face the same problem phone application stores face: too many programs to easily select what you need. You could certainly build a whole site just around package reviews; it’s even possible to argue that Ubuntu or PC-BSD are built around just making some 3rd-party-app choices ahead of time on an existing operating system. Anyway, here’s an article talking about that idea specifically around the Apple App Store. Please won’t somebody who is not me do something like that for pkgsrc?
- This writeup of one man’s experience with Forth gives a good feel for the language, or at least as good a feel as I can understand. Posted in memoriam for our recently departed Forth bootloader. (via) There’s other enjoyable articles on that blog, too.
- This describes about two years of my life, except it was mostly Zangband.
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.
- 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 recently sent out a description of what built for pkgsrc-2010Q2 , though the section on not changing the stable link is no longer true.
Binary packages built for pkgsrc-2010Q2 are available now via pkg_radd or directly. Make sure to read my lengthy post for exact details.
I haven’t seen an announcement at all, but I’m inferring that it’s out. I’ll be changing the DragonFly build machines momentarily.
There’s an online hackathon (the 14th!) planned for July 30th through August 2nd for pkgsrc (and probably some NetBSD material too) at FreeNode/#netbsd-code on IRC. Aleksej Saushev’s post has more details. At least it’s cheap to attend!
Matthew Dillon set up a git copy of the pkgsrc repository some time ago. However, it’s had syncing problems, and there’s an ‘official’ pkgsrc git repository now which does not have the problems. You can still pull from the same place, but it’s the ‘master’ branch now. His heads-up message describes how to switch.
It’s been 0.25 years since the last, so pkgsrc is due for another quarterly release. The usually-two-week freeze before release starts tonight. The release should happen at the end of the month.
- IBM’s developerWorks has an article up about GNU screen. It’s not BSD-specific, but the tips in using screen are useful. (Before someone brings it up: yes, tmux too.)
- Another article talks about inspecting network traffic using various tools including tcpdump and wireshark. It is a tremendous advantage to see what happens on a network at the most basic level, so this is a good skill to pick up.
- Oh, and “Setting up UNIX file systems” and “10 steps to Unix nirvana“.
- FreeBSD now ships with clang. (via) I know DragonFly (mostly?) works with clang… Could we switch?
- “hwstat” will gain DragonFly support soon.
- Firmware for ral(4) has been added by Joe Talbott.
- Thomas Klausner has a writeup of some project ideas or goals taken from the recent pkgsrcCon. A followup has me thinking: if the -uu option updates dependent packages with pkg_add, does that mean ‘pkg_radd -uu packagename” will do all updating possible based on available binary packages? Worth trying.
I’ve put a few of the reports from pkgsrc builds on DragonFly out. They’re all using pkgsrc-2010Q1, on i386/DragonFly 2.6, i386/DragonFly 2.7, and x86_64/DragonFly 2.7. The links in the reports go to the errors that caused each package to not build. If you happen to see something that has an easy fix, or that you really need to have working, please submit a fix.
Binary packages built for DragonFly 2.6 and 2.7 from the most recent pkgsrc quarterly release, 2010Q1, are now available. The utility pkg_radd will access them, or you can download directly.
From my email to users@:
- I almost have pkgsrc-2010Q1 builds done for every architecture, so I’ll point the default load location for pkg_radd to them within the next 24 hours.
- Are you still using a DragonFly system older than 2.4 and downloading binaries? If so, tell me.
- A project: enhancing pkg_search and pkg_radd to be able to tell when a package is missing because of license restrictions. Anyone want to try it?
If you use Apache, as many people do, some of the default building choices have changed in pkgsrc. Read Matthias Scheler’s post for details.
I’ve made reference to DESTDIR for pkgsrc several times, with only an informal understanding of what it means. From what I’ve learned, and what Joerg Sonnenberger’s told me, DESTDIR support means that packages can be built from pkgsrc without needing to be root. This means local packages can be built on an ordinary user account using pkgsrc.
This also means that pkgsrc can build packages before each upgrade, and only upgrade if a binary package can be built for each item involved. This means minimal downtime and no failures during upgrades, the biggest bugaboo for using pkgsrc that I’ve encountered.
I posted a note about where the 2010Q1 builds are for pkgsrc; if you’re on i386/2.6 right now, you can try it out.
The newest branch of pkgsrc for 2010 is officially out – read the release announcement for details on what’s updated. Among other things, DESTDIR support is almost complete, and a shift to default KDE4 is underway.
I’m working on bulk builds already, so hopefully soon you’ll be able to pkg_radd 2010Q1 packages…
pkgsrcCon is happening May 28th-30th in Basel, Switzerland. The event web page has note on location and hotel information. (thanks, S.P.Zeidler)
Based on a comment from John Merino on this very Digest, I managed to assemble some statistics on binary pkgsrc package use. See my full post for the details, including some analysis.
In an effort to catch up…
- Matthew Dillon made a change to how material in memory is paged out; it may improve things depending on how much paging your system already does.
- The AsiaBSDCon OpenBSD papers are online, with mention of video of the presentations.
- Use keys for your SSH login, cause this will only get worse.
- Ten Shell One-liners. The first one, using your favorite editor on the command line, is one of those things I knew about, but didn’t know to do. (caveat: some Linuxisms)
- Want to test a big xorg update for pkgsrc? Of course you do.
Every time a bulk build of pkgsrc packages is completed, a report is uploaded listing what built and what didn’t. Since there’s so many reports from the now-automated build, I’ve sorted it by architecture and release, to make lookups faster.
This is handy if you’re looking to fix pkgsrc apps on DragonFly, and you need a target. It’s also a good way to see if a desired module exists as a binary.