Neil Williams: cross-building, multiarch and binutils
At the Emdebian ARM sprint, cross-building experiments on a Multi-Arch base are going fairly well. It is looking like the hacks in dpkg-cross may finally be avoidable, possibly before Wheezy gets released. Elsewhere, debhelper has been updated to allow dh_strip and other tools to work directly with the binutils package from the cross-building toolchain and not to need binutils-multiarch any more. dpkg-cross has been updated to only Suggest binutils-multiarch, which makes room for more architectures to be covered by binutils-multiarch (which, therefore, will be getting quite a lot bigger quite soon).Cross-building in Debian is therefore entering a period of transition and the old ways of dpkg-cross - and the tools it has spawned like apt-cross, xapt, pdebuild-cross and others - will be gradually side-lined and finally rendered obsolete. Like all transitions, there will be breakage, there will be pain, there will be things which don't cross-build now and which have no prospect of being fixed until the transition is deeply entrenched. There are packages which used to cross-build and which will stop cross-building and, again, won't be fixable for months. Sadly, Squeeze released with cross-building breakage too, due to changes within apt during the release freeze. A Lenny chroot is possibly the best place to do cross-building for now.
This is a major transition. It WILL break things. Badly and often.
What's more, just because we decide to implement stuff using one method now does not mean that the same method will even exist in a month or two.
In other words, if you've got a working cross-build chroot or installation currently and you absolutely need it to continue working leave it alone.
Don't go changing real packages to use the changes we're trying out!
If you enjoy fixing stuff, don't mind pain and fancy risking your system as I've been doing (unlinking /etc/, deleting /lib64 on amd64 or forcing package installation such that no shared libraries are accessible any longer) then you are:
- insane
- welcome to join the work
Check out the current state of things via the #emdebian channel on oftc.net and the very risky Emdebian multiarch SVN experiments along with the even more risky Emdebian Multiarch Mirror, courtesy of Steve McIntyre and Phil Hands.
The README in SVN is very clear - DON'T INSTALL THESE OUTSIDE A CHROOT and even if you do, don't come crying to me when it breaks your entire system (even when used inside a chroot).
No warranty, no guarantees, no promises, none of this is fit for any purpose whatsoever and we'll say when we finally have something which might actually be useful.
I've been very quiet on here for a few months, and the reason is (of course) because I've been doing other things. No surprise there, I guess!
What I've been doing, first of all, is writing
The interview at Munich seemed to go well. Well, at least, I had fun. We'll see how that turns out.
Thanks to those nice people at Novell and
Collabora,
Another week is over and it's time to look again at state of
I've noticed that the name I chose for my Python B-tree library,
btree, isn't particularly unique. There's at least two other
libraries with the same name. I need to rename nime.
I'm not able to come up with a new name, though. Do you, dear
reader, have a suggestion?
I'd like a name that is short, and is either descriptive
or invokes mental impressions of trees or forests.
Edit: Should also be relatively unique (low hit count on
Google), and not a name already used by an existing Python
project, or preferably any free software project.
We have many orphaned packages in Debian. Those are packages that no longer have a maintainer willing to care for them. They are a problem for several reasons. Often, there have better alternatives (that s often why the maintainer gave up maintenance), but users keep installing them because they show up in apt-cache search. Or, they might be broken, without anybody noticing because they only have a few users. Also, developers need to take them into account. They might slow down transitions, have RC bugs that need fixing, etc.
So, there are good reasons to remove some of the orphaned packages from the Debian archive. Not all of them. But those that have been orphaned for a long time without anybody stepping up to take over the maintenance, have very few users according to popcon, etc. Removing some of them also makes it easier to expose the ones that should really find an adopter.
Also, that removal is not final. The good reason to do this now is that we are at the beginning of a release cycle, and that it will be easy to reintroduce packages that are really needed during the next two years. Also, packages (both source and binaries) are still available on
Packaging updates
Debian patch tracker
Finally got around to fixing a couple post-release (and older) issues
in the
Enough news to release another Debian XSF News issue, after less
than a week.
squeeze is released but this doesn't mean the end of the ordinary RC bug;
old ones are still around, & new ones keep floating in.
People are using computers, everywhere, really! ;)
(Non-Debian readers can stop reading now, I'm talking about so-called
"orphaned packages" and not anything of real-world importance.)
In 2008 I stopped maintaining non-native packages in Debian. At the time
I maintained a fair amount of stuff. It's interesting to see what happened
to it after I gave it up, partly because some of the results seem so
random and partly because some of what has happened seems to point
at weaknesses in Debian.
First, the success stories. More than half of my packages are now being
maintained by others: xaos, longrun, fbreader, liblinebreak,
analog, xgalaga, znc, sysnews, metastore, bsdgames, uqm, oneko, kobodeluxe,
archivemail, unclutter I still use much of this stuff, some only
occasionally, and other daily, and am glad it's being kept alive.
(It's surprising that someone still care about longrun.)
I was unhappy to have to NMU procmeter3 just before the release
of Debian 6.0 to fix a trivial to debug RC bug that almost got it removed
from the release. I hope that was just a bump in its road.
Also, splitvt is now maintained again after being orphaned a long
time. I'm not sure if it makes sense to keep it in Debian, since screen can
do the same thing, and it has a security history, but someone wants
to, so that's fine.
Two packages are left on life support. I'm surprised nobody wants
to maintain grepmail, unless we're all using notmuch or mairix
now? And dgen is the best Sega emulator I know of.
Several games were not picked up by the games team, despite
them showing some interest originally, and were removed: xtris, xjewel,
xemeraldia, xbl Of those, xemeraldia in particular is a lot of fun,
I'm surprised nobody cared to keep it. Also, the nestra Nintendo
emulator was shipped with squeeze, but now is removed as it never got
a maintainer. I don't know if there is a better NES emulator in Debian.
The intercal programming language was removed. Surprising. Debian
does at least still have clc-intercal for all our pressing Intercal
needs.
Finally, sparkline-php was removed today despite never having
had any bugs, needing no maintenance, and being a suggests of ikiwiki,
which is now more buggy (broken relationships, outdated docs) and
less featureful in Debian.
There are many ways to run some commands simultaneously on multiple
hosts like
Thank you