|
|
|
||||||||||||||||||||||||||||||||||
| Sunday, 19 May 2013 | Dereel | |
| Top of page | ||
| next day | ||
| last day |
|
Another power failure
|
Topic: general | Link here |
Another power failure this morning at 2:03.
|
Laziness and new houses
|
Topic: general | Link here |
I've been relatively lazy lately, much to the disgust of Peter Jeremy, who complained today that there's not enough to read in my diary. And I always thought it was too verbose. Today I did little. Yvonne found a newly listed house for sale in Tantaus Road, interestingly almost adjoining the property in Snowgum Road that we looked at a month ago. It looked quite good, and since it's only 1.5 km away, we went over to take a look from the outside. To our surprise it belongs to the Leahys, from whom we bought various things last year. The photos are really good; it makes the place look much better. They were in the garden, and though you're not supposed to speak to the sellers directly without the estate agent being present, it seemed rude not to say hello. They're moving to Ballarat for age-related issues. I wonder when we'll end up having to do that.
|
Getting my head around Subversion
|
Topic: technology, opinion | Link here |
I've been using revision control systems, notably RCS, for over 20 years, and for all sorts of things, including this diary:
It's been 5 years since the FreeBSD project moved from CVS to subversion, but I haven't really done any merging until yesterday. That worked fine, but today's didn't. Followed the instructions and discovered that my source file (/usr/src/lib/libc/stdio/printf.3) didn't have any mergedata at all:
=== grog@eureka (/dev/pts/3) /src/FreeBSD/svn/head/lib/libc/stdio 5 -> svn propget svn:mergeinfo -R printf.3
=== grog@eureka (/dev/pts/3) /src/FreeBSD/svn/head/lib/libc/stdio 6 ->
Is this the first time that anything has been merged to this file? Tried the next step:
=== grog@eureka (/dev/pts/3) /src/FreeBSD/svn/head/lib/libc/stdio 6 -> svn merge -c r242738 svn+ssh://svn.freebsd.org/base/head/lib/libc/stdio/printf.3 printf.3
So far, so good. What does the mergeinfo look like now?
=== grog@eureka (/dev/pts/3) /src/FreeBSD/svn/head/lib/libc/stdio 7 -> svn propget svn:mergeinfo -R
That was more than I expected, to say the least. But svn diff shows exactly my change:
=== grog@eureka (/dev/pts/3) /src/FreeBSD/svn/head/lib/libc/stdio 8 -> svn diff printf.3
Where did the other mergeinfo come from? Sent a message to the committers list and got back a very nicely worded reply that basically amounted to RTFM. Further up in the instructions was the admonition:
Never merge directly to a file.
Never, ever merge directly to a file.
Never, ever, ever merge directly to a file.
And I had read that, and even thought the repetition a little silly. So why did I do it anyway? Because that's the way our grandfathers did it with RCS. RCS is file oriented. CVS is too, really. But Subversion is change set oriented, and the mergeinfo is associated with the changeset, not with the file.
|
Pkgng: first impressions
|
Topic: technology, opinion | Link here |
So now my ports are roughly up to date. Can I use Pkgng to keep them up to date? Read the instructions, which are still a little preliminary. The best entry point seems to be the Pkg Primer, though there's also a Handbook section. First you need to run pkg2ng, which takes quite a while, and produced about 4,500 lines of output, not all of it pleasant:
At the end it came up with:
OK, that's simple enough. Remove and reinstall:
=== root@stable-amd64 (/dev/pts/1) /usr/ports 4 -> pkg delete texinfo-5.1.20130419
=== root@stable-amd64 (/dev/pts/1) /usr/ports 5 -> pkg delete texinfo
=== root@stable-amd64 (/dev/pts/1) /usr/ports 6 -> pkg_delete texinfo-5.1.20130419
=== root@stable-amd64 (/dev/pts/1) /usr/ports 7 -> pkg install texinfo
=== root@stable-amd64 (/dev/pts/1) /usr/ports 8 -> pkg install texinfo-5
=== root@stable-amd64 (/dev/pts/1) /usr/ports 9 -> pkg_add -r texinfo
=== root@stable-amd64 (/dev/pts/1) /usr/ports 10 ->
The third line (prompt 6) is subtly different: instead of pkg (Pkgng) it uses pkg_delete (old packages). That might be because it failed to register, of course. But pkg also can't find the remote packages. In other words, pkg doesn't seem to do anything useful—yet. Maybe it's related to the repository, but I didn't find a description of that. This was all in a virtual machine, and I had taken a snapshot before running pkg2ng, so I just restored it. I'll try again some other time.
| Monday, 20 May 2013 | Dereel | |
| Top of page | ||
| previous day |
|
Computing for non-techies
|
Topic: technology, general, opinion | Link here |
Our neighbour Jenny Bartlett, whom I only met 9 days ago, has been on a shopping spree and bought herself a digital (“personal”) video recorder and a Samsung Galaxy tablet, which she calls an iPad, possibly because that's what the salesperson called it. And she had difficulty installing it, so Yvonne persuaded me (“No, I will not repair your computer”) to go along and help.
The thing's wireless, of course, so apart from the pad she also had a wireless router to connect to her existing installation (laptop connected to IPStar satellite), and her real issue was how to connect things up. That wasn't difficult, apart from the fact that the router required a login to connect. But what do you do with a tablet? This is the same question I asked myself a year ago, and in Jenny's case it's not clear what advantage the tablet would have over her laptop, which, she says, she doesn't use. In addition, I had great difficulty with the touchscreen, which seemed very unresponsive. Chris Bahlo has a Samsung; we should send her by and see what she thinks.
The main issue with the DVR was wiring again, not helped by the lack of an antenna cable. The display (via HDMI) was surprisingly unstable, but it got the EPG and we were able to set it up to record. But what terrible documentation! In general, it's amazing how bad the documentation for everything is. I think there must have been about 20 pages of badly reproduced black and white documentation for the tablet, router and DVR put together, and much of my interaction with the DVR was through trial and error. I wonder how much use Jenny will get out of the devices.
|
More subversion pain
|
Topic: technology, opinion | Link here |
OK, now I have learnt not to talk to files when using subversion—or so I thought. The list goes on (my interpretation of the last one):
Never merge directly to a file.
Never, ever merge directly to a file.
Never, ever, ever merge directly to a file.
...
OK, sometimes you can merge to a file.
Still, the “sometimes” didn't apply here, so I started my next merge as described in the instructions. Something went wrong and I got a conflict where no conflict should have been. Tried moving the directory, checking out again, confirming that the mergeinfo had been reset, and starting again. No changes to the files. Tried again, and this time the mergeinfo had changed. OK, not a problem: that's what propdel is for. But no, I can't do that:
=== grog@eureka (/dev/pts/3) /src/FreeBSD/svn/stable/9/usr.bin/locale 102 -> svn propdel --revprop -r242743 svn:mergeinfo .
So somehow, without trying, I've managed to corrupt the repository metadata, and I can't fix it. This whole setup is too fragile: it shouldn't be possible to make this kind of mistake. I seem to remember having similar problems in Rocksoft years ago, but I don't seem to have noted it in my diary. It looks as if I'll have to blow away the checkout and start again.
|
Watch calibration
|
Topic: general | Link here |
How accurate is my new watch? Hard to say. My old watch gained about 15 to 20 seconds a month. I thought I had set the new one to be 2 seconds behind the old one (because that one was currently about 2 seconds fast), but when I checked today the new one was 2 seconds faster than the old one. Is it gaining a lot, or did I just set it the wrong way round? Today at 15:00 odd I set it exactly to the time on eureka (NTP synchronized). Now I'll have to wait a few days and see how it drifts.
| This page contains (roughly) yesterday's and today's entries. I have a horror of reverse chronological documents, so all my diary entries are chronological. I try to leave the pages here for two days; you'll find them all in the archive, so if I fall behind a day or two, you may find more here. Note that I often update a diary entry a day or two after I write it. | Do you have a comment about something I have written? This is a diary, not a “blog”, and there is deliberately no provision for directly adding comments. But I welcome feedback and try to reply to all messages I receive. See the diary overview for more details. If you do send me a message relating to something I have written, please indicate whether you'd prefer me not to mention your name. Otherwise I'll assume that it's OK to do so. |
| Previous month | Greg's home page | This month | Greg's photos | Greg's links |
| RSS 2.0 |
|