![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png){kind=small}
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
Entry tags:
hg update -C tip
So, a while ago, we closed the 'production' branch in Mercurial. Since then, i've been merrily going along with my 'hack, updating my code regularly, yadda, except for some reason I kept having problems applying patches from the review queue...
...many of you can probably figure out where this is going. So, tonight I was having some trouble with S2 changes in dw-nonfree making my update script error out and die, and Afuna and I realized, finally, that it was because I was still set to the 'production' branch in Mercurial. So, if you're like me and keep having problems applying patches, try this:
hg id
If it says 'production', do this:
hg update -C tip
(When I did that, I got "427 files updated, 0 files merged, 28 files removed, 0 files unresolved". Yowch.)
...many of you can probably figure out where this is going. So, tonight I was having some trouble with S2 changes in dw-nonfree making my update script error out and die, and Afuna and I realized, finally, that it was because I was still set to the 'production' branch in Mercurial. So, if you're like me and keep having problems applying patches, try this:
hg id
If it says 'production', do this:
hg update -C tip
(When I did that, I got "427 files updated, 0 files merged, 28 files removed, 0 files unresolved". Yowch.)
no subject
no subject
no subject
no subject
I'm not sure of this, though. And unfortunately, because of the way Ubuntu's packaging system works, to go any higher using the official Ubuntu package I'd need to upgrade the whole system to a later distro - which I should probably do anyway, since Hardy Heron is kind of dated by now - it was released in April 2008.
The issue is that I tend to find that dist-upgrades can cause all sorts of issues if you're not careful, and would probably involve longer-than-usual downtime. (I wouldn't want people to be able to connect to the box while the dist-upgrade was going on, for example, and afterwards you'd need to check configs to make sure everything was still okay, which could be a problem if new configuration options were added.
I keep backups of the essential bits that make the Dreamhack system work (although I don't keep backups of user data), so technically it would be possible to reinstall the whole thing, although I'd need to create all the user accounts again, which would involve running the install script for each user. It only takes 5 minutes, but we currently have 212 Dreamhack users, which would mean it would take about 18 *hours* to do the whole thing. And that doesn't include installing all the base packages needed in Ubuntu, plus it would lose any user data. On the upside, no issues with configuration.
A variant of the above could be if we didn't recreate users, and instead have people reapply. That'd have the effect of also meaning that those who didn't use it wouldn't have their accounts recreated.
(of course, if we did do any of these, I'd make sure to warn everybody via email ahead of time - probably like a month ahead or something.)
[edit: there is a solution to the Mercurial thing which I didn't mention; I could uninstall the official Ubuntu version and compile the latest one directly. That would give us the latest version of Mercurial, but it won't help with the rest of the system being dated.]
no subject
*contemplates creating DW-Nix* Nah.. bad idea...
no subject
no subject
no subject
no subject
no subject