|
| Greg's diary |
| recent entries |
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Monday, 18 January 2021 | Dereel | Images for 18 January 2021 |
| Top of page | ||
| next day | ||
| last day |
|
The revenge of Microsoft
|
Topic: technology, opinion | Link here |
Yvonne in to my office with a problem: distress, the Microsoft “Windows” 10 box, wouldn't talk to her, something to do with all slots being full. Sure enough, it was repeatable.
Bloody Microsoft! Does this have something to do with the unsolicited upgrade last week? Probably. In to my office to check. Worked fine for me. Simulate Yvonne's environment and try again. Long delay while it logged her in and did whatever else Microsoft does when it starts up. But it worked. Back to her office. Worked.
So what went wrong? She had to log in, but the first couple of times around we didn't get that far. But it seems to be related to logging in, which only happens once per reboot. I should at least have kept track of the exact message.
| Tuesday, 19 January 2021 | Dereel | Images for 19 January 2021 |
| Top of page | ||
| previous day |
|
Next system upgrade attempt
|
Topic: technology, opinion | Link here |
As part of my migration attempts for eureso, brought dereel up to date: new kernel, new userland, update ports.
It almost worked:
[43/194] Installing librsvg2-rust-2.50.2...
pkg: librsvg2-rust-2.50.2 conflicts with librsvg2-2.40.21 (installs files into the same place). Problematic file: /usr/local/bin/rsvg-convert
There's too much of that kind of thing. OK, it looks like librsvg2-rust-2.50.2 should win, so let's remove the other:
=== root@dereel (/dev/pts/0) /home/grog 2 -> Log pkg delete librsvg2-2.40.21
===== Tue 19 Jan 2021 12:37:08 AEDT on dereel: pkg delete librsvg2-2.40.21
Installed packages to be REMOVED:
ImageMagick7: 7.0.10.24
audacity: 2.4.2_2
chromium: 84.0.4147.135
darktable: 3.2.1_3
emacs: 27.1_1,3
firefox: 84.0.1,2
gimp: 2.10.20_1,2
gtk3: 3.24.23_1
gtkmm30: 3.24.2
handbrake: 1.3.3_1
hugin: 2020.0
Number of packages to be removed: 23
Those were only the ones that I recognized, and it includes about every port I use on the machine. No way I'm going to do that. So I just restarted the pkg upgrade, and how about that: it worked!
But then I discovered that the source tree hadn't been updated in weeks. It's easy enough to guess why: the FreeBSD project is moving from subversion to Git.
|
Making friends^W acquaintance with git
|
Topic: technology, opinion | Link here |
So I have to finally use Git to update my software. I really wish they hadn't done it, but I'm going to have to come to terms with it.
OK, where's the docco? I had saved some mail messages on the subject for later perusal. Now's the time. 529 messages! There must be a simpler way. Peter Jeremy has been there before me (and grumbled mightily). Ask on IRC.
No Peter, but Andy Snow came up with this summary, which refers to Warner Losh's git primer, the one that he had sent to me some months ago.
OK, follow that:
cd /usr/src
REPO=https://github.com/freebsd/freebsd.git
git clone $REPO -b stable/12
Nothing happened. Oh, yes, I was just looking in the wrong place. Lots of network traffic, and after 25 minutes I had a tree /usr/src/freebsd, 3.3 GB in size.
But no history! What use is that? Daniel O'Connor came up with an alternative way, described in this document. It's also by Warner Losh, but completely different, and refers to different repositories.
But wait, there's more. Callum Gibson came up with this page, from which I derived the invocation:
REPO=ssh://git@gitrepo.FreeBSD.org/src.git
git clone $REPO
That's the main FreeBSD source repository, for registered developers only. And it said something as it worked:
Warning: Permanently added 'gitrepo.freebsd.org' (ECDSA) to the list of known hosts.
remote: Enumerating objects: 433625, done.
remote: Counting objects: 100% (433625/433625), done.
It also checked out into a directory src/, more like I would have expected, and there seems to be some kind of history involved. So: all OK? Not quite.
First, how do I find the version number? Looking at bin/ls/ls.c, the last svn version has:
__FBSDID("$FreeBSD: head/bin/ls/ls.c 368467 2020-12-08 23:38:26Z bdrewery $");
And the git version?
__FBSDID("$FreeBSD$");
So we've lost a lot of information. Ah, says Jamie Fraser, that's an old, worn-out way of looking at things. Just
