Aigars Mahinovs: Debian development basic links
For a Debian package creation seminar:
For a Debian package creation seminar:
Ubuntu's live CD installer, Ubiquity, needs to suppress desktop
automounting while it's doing partitioning and generally messing about with
mount points, otherwise its temporary mount points end up busy on unmount
due to some smart-arse desktop component that decides to open a window for
it.
To date, it employs the following methods, each of which was sufficient
at the time:
/desktop/gnome/volume_manager/automount_drives and
/desktop/gnome/volume_manager/automount_media gconf keys to
false.
kded to unload its medianotifier module,
and load it again just before the installer exits.
/apps/nautilus/desktop/volumes_visible gconf key to
false.
AutomountDrives and AutomountMedia keys
in $HOME/.config/Thunar/volmanrc to FALSE.
/apps/nautilus/preferences/media_automount and
/apps/nautilus/preferences/media_automount_open gconf keys to
false.
hal-lock --interface
org.freedesktop.Hal.Device.Storage --exclusive.
/apps/nautilus/preferences/media_autorun_never gconf
key to true
(experimental,
but apparently now required since nautilus uses the gio volume
monitor).
hal-lock mechanism; it was simple and
involved minimal fuss. I had hoped that it might end up as a standard, but I
guess that would be too easy.
There's a 10 Downing Street e-petition asking for the National Archive to use ODF and not Microsoft's OOXML as planned. Not sure if we can really stop gov.uk selling our heritage to Microsoft now, but it seems worth the effort to sign it.

It's been a long time since I've written on my blog; longer than I'd like. I really want to get back in the swing of it, if only to keep this entire site from bitrotting interminably. My Alexa ranking has dropped to like >1M, which in my Web-addled state means that my personal worth has dropped, too. I know, I know.
tags: blog me alexa


Quite some time back, I
wrote
about my disappointment that
Ampad
had ceased manufacturing their Quad Ruled Steno Books,
which I use to make notes to myself on just about everything.
Several of my friends in Europe responded that similar pads in A5 size were
commonly available in retail stores, and I quite happily bought a few on a
trip to Germany. Then, one of my colleagues at work had some nice notebooks
made up for a customer event with grid paper and suitable logos on the cover
that I grabbed a few of and have used quite happily.
Sometime in the intervening years, Ampad started producing these pads again,
but with a different product number, 42036. I stumbled over some at a local
office supply store and bought a big pile... others have noticed too, and sent
me email about it, which is why I'm taking the time to write this...
Yes, I'm much happier now!
archivesCreate the key and the 512 MB loopback partition:
dev=/home/username/.archives
dir=/home/username/archives
fstype=ext3 fsoptions=defaults cipher=aes
keyfile=/home/username/.archives.key
keyhash=sha1 keycipher=des3
sudo cryptmount --generate-key 32 archivesFix the permissions so that you can write to this partition with your normal user account:
dd if=/dev/zero of=.archives bs=1M count=512
mkdir archives
sudo cryptmount --prepare archives
sudo mkfs.ext3 -m 0 /dev/mapper/archives
sudo cryptmount --release archives
cryptmount archivesThen you can mount and umount that partition using:
cd archives
sudo chown username:username .
cryptmount -u archives
cryptmount archivesand
cryptmount -u archives
Limited Liability Partnerships are a
relatively new company form here, but it
has some
interesting opportunities for cooperatives.
I work for one
(TTLLP)
so I've gathered some useful links:-
uniteddiversity LLP (some of those behind The Open Coop)
Limited Liability Partnerships @ Co-opNet
Chris Cook's web site
appears to include contributions from 2amase's
Bev Meldrum. At least I think it's Chris Cook's web site...
2amase LLP's web site forwards to
http://www.thetoolfactory.com/Contact.htm
which says they have a Plymouth office, but says nothing about
their current status. They're
listed on uk.coop
and
again
Sticking LLP into the uk.coop search is amusing.
Companies House - Formation and Names - GBLLP1
and
Administration and Management - GBLLP2
The governing laws are
Limited Liability Partnerships Act 2000
and
BIM72505 - Partnership Act 1890
Any feedback you have on the above would be helpful.
Anyway, hope that helps. Let me know how you get on with a comment, please,
or if the new LLP needs a web site or hosting... ;-)
This year I have not given any vote recommendation because all candidates would be (IMO) good DPL. The participation stats are a bit strange however: when I got the second call for vote I noticed 176 votes in the first week compared to 135 last year. So I thought “good, participation is on the rise”. But then I got reminded that we have shortened the voting period of the DPL election to two weeks. So the comparison doesn’t hold.
The vote close in two days and we have so far only 283 votes, and last year we got 482 in the end. So we’re likely to have much less participation this year… even if you add a percentage for the people who wish to vote but cannot for various reasons (which proves once more how important it is that the next DPL be determined to fix those recurring problems), you won’t get the same numbers.
So my question is: do we have lower participation because all candidates are good and people do not care who gets elected? or do we have so many DD that follow Debian only every 2.5 weeks?
And if you haven’t voted yet, it’s time to do it.
I'm currently part way through testing Chronicle and I'm probably going to change the address of my blog (with Redirects) as part of that. I don't much like having blog in the address and some research seems to agree with me. I've lived with this mistake for four years now, through various software upgrades, so I'll take the chance to change. But what should I change the path to? /writing/reflections/ /news/ /notes/ /articles/ or something else? Vote now by leaving a comment! Oh and about the debian project leader vote: reluctant candidates are good, teams are good, people who already have had high office are less good. Go vote on that too if you can.
Qt 4.4.0 rc1 was uploaded yesterday to unstable. It was previously available in experimental.
A rework of the packages was done :
The lenny l10n NMU campaign is now running for about two months now.
The objectives of this campaign are tackling pending po-debconf l10n bugs.
The process is the following:
A few days ago, I just screwed the samba packages maintenance.
It's been quite some time since we were preparing Samba 3.2.0 packages. Upstream has not published a release version, only pre-releases. The release was planned for next week but will not happen as some last minutes issues have been found in pre-releases.
Anyway, we had ready packages for 3.2.0 pre-release 2....which were planed to go to experimental.
However, these packages were under preparation for quite a while, so when I finally agreed with Steve Langasek that it's OK to upload, I built and uploaded the packages. Then got a good laugh when discovering that I forgot "UNRELEASED" as target in debian.changelog.
It was late, I then "s/UNRELEASED/unstable" as I often do in such case....then uploaded...then forgot about the issue and went to something else.
The package went through NEW (it has a new binary package) and 1 or 2 days later quietly entered unstable.
...which I discovered only the next day, when it was way too late to remove from unstable something that was meant for experimental.
All this explains why samba packages now use an epoch...:-)
Things are back to normal now. Unstable has 1:3.0.28a-2 and experimental will hopefully have 3.2.0~pre2 soon.
Next week I go to the Samba annual conference. I'll probably spend some time hunting down some bugs in the package and discuss with upstream about some of the issues we have (old bugs, FHS patch, upstream's .deb packages). And maybe also get better ideas about Samba 3.2.x schedule, to be able to decide with Steve and Noel which release is the target for lenny: 3.0.28* or 3.2.x.
Where, oh, where do I start with this one??$ parsechangelog wc
97 644 4793
dpkg-buildpackage -a actually works. It means that work can really proceed on autobuilders for toolchains (glibc and uClibc) and for cross built target packages for embedded devices. I'll be watching the dpkg migration closely and if 1.14.18 is not migrated for some reason, I will have revert the changes for this element to restore the old workarounds.apt-cache policy which is actually quite unreliable with respect to CD/DVD sources and some unofficial sources or mixed testing/unstable configurations.Next.