Archive for the 'Debian' Category

Page 2 of 8

Why oh why…

… did FAI switch to that stinking pile of shit known as live-initramfs?

Things that were possible before aren’t possible anymore due to the extreme brokenness of live-initramfs. Nothing that can’t be fixed by some heavy-handed patching here and there, but what a waste of time.

Not happy. Hammer time.

How to not use lintian overrides

Look what just got added to all the packages maintained by the Debian Forensics team:

--- md5deep-3.4.orig/debian/source.lintian-overrides
+++ md5deep-3.4/debian/source.lintian-overrides
@@ -0,0 +1,3 @@
+# Avoid warnings if non-uploaders to uploads.
+md5deep source: changelog-should-mention-nmu
+md5deep source: source-nmu-has-incorrect-version-number

You’re doing it wrong.

Digi AccelePort drivers updated to 1.3-15; now for Lenny

This is yet another “beta” release from Digi from a few months ago.

I had to patch the driver to build with a 2.6.26 kernel, as neither versions of the code would build against that version. Lenny ships with 2.6.26, so that would have meant no dgap drivers on Lenny. I’ve tested the patched driver and haven’t noticed anything obvious while doing so.

The drivers are now built for Lenny; if you need them on Etch, a simple rebuild from source will do. Previous versions are still available in the pool, under the old/ directory.

APT source line, now changed:

deb http://debian.technologeek.org/ lenny non-free

Feedback at the usual address.

No patch is better than useless patch

Joerg,

The patch you submitted has 0 chance of getting applied, and you know it. It’s nothing more than a bad joke.

The best solution for this issue is most probably to provide a xserver-xorg-nohal package that is a duplicate of xserver-xorg minus the HAL dependency.

HAL-haters heads up: #515214

Don’t like HAL? X.org now forces it upon you via xserver-xorg.

#515214, currently wishlist/wontfix.

d-i SCM FAIL

From the Bits from the Debian Installer team mail to d-d-a:

It has been decided that, in order to not slow down the development processes, D-I SVN should be branched when the work on preparing a release starts. Even if SVN doesn’t make the process very easy, changing the VCS we use is currently not an option we prefer.

SVN, branching, d-i. There’s no word to describe how painful it is to work on d-i using SVN. d-i is big, SVN is slow in about everything it does. Now add branches to the mix.

That mail left me very disappointed; first because I thought switching to git was sort-of planned for after the release of Lenny, and now it’s off the table, second because some things in this mail are just wrong.

Oh well. No d-i for me, I guess, then.

mt-daapd EPIC WIN

I’ve been doing some code lately, fixing things here and there, and over the last few days gave mt-daapd some attention.

First, I was reported a segfault of mt-daapd when reloading web pages too fast. Surprisingly, it turned out to be a stupid omission in a simple routine and it is hard to hit without disabling the cache in the browser.

Now, I just fixed something that’s been bugging me for a while: mt-daapd did not handle Avahi daemon restarts, leading to mt-daapd becoming invisible to clients relying on mDNS until you restarted it.

And, wow, that went a bit further than expected. As I expected, the simple piece of code needed to handle that wasn’t there. But still it did not work, as it turns out the event loop for the Avahi polling wasn’t being run. Replace stupid code reinventing the wheel by the Avahi-provided wheel and there, it works. But not when run as a daemon (aka foreground only). Well yes, starting the thread before daemonizing isn’t going to work well, so fix that. EPIC WIN \o/

As mt-daapd’s upstream is not active anymore I’m accumulating fixes for mt-daapd in the Debian package, to the point I’m starting to consider setting up a git repository somewhere with those fixes and possibly some more code rework if I feel like it.

This project should remain open and openminded

David,

I’m not saying it lightly: the end goal is censorship, no matter how nicely you try to put it.

The goal is to discourage people from posting. They call it “peer pressure”, which is nothing else but the politically correct equivalent expression for “intimidation”. The end result is censorship.

The idea of censoring the mailing lists has actually been mentioned very clearly in the recent discussions on -devel, and I never thought it would go past that, but it’s actually happening. By the way, this could actually morph into a shitty karma system that wouldn’t let you post past your monthly allowance and “credit” “earned”. How’s that for you?

You refer to those +1/-1 mails; I find them silly, annoying, useless and a waste of bandwidth and CPU time. That used to be called a “me too” and generally despised and frowned upon.

If you actually want to score posts or posters, get a decent MUA and set up its scoring system the way you like. But keep that to yourself.

As Aigars told, there are mail to web forum “gateways” (more like rendering engines for a mail archive, actually) that will present mails to a list in a crappy web forum of some sort that will come with all kind of crap like scoring, karma and whatever.

There’s an essential difference between web forums and our mailing lists, though: forums of this kind use nicknames all over the place, our mailing lists use real names. There are privacy issues involved, and I’m not giving up on that, either.

You want to stop flamewars? Stop replying, especially to tell how intolerable it is and other shit. Just let the damn thing die already. Funny how the well-meaning people are feeling “harassed” on the mailing lists when they, themselves, are harassing people they disagree with.

We don’t all have the same views, culture etc. We’re not all friends, and we probably never will be. Guess what? It’s OK! Get over it and work with each other, because that is what we are here for. If you (general) can’t get over it, I’m afraid this Project is not the appropriate place for you.

Imposing a monoculture of politically correct crap is not an answer to the perceived “problems”.

Free software yes, free speech no thanks.

This proposal leaves me speechless. The replies even more. The sole fact that there are positive replies kills me.

I’m really starting to think that this Project could do a lot better without some people. Now if you’ll excuse me for a sec, I have a urgent need to vomit.

Reality check, people. Get back on the ground.

On the firmwares/Lenny vote

Christian notes, and rightly so, how much this vote sucks, for various reasons.

There are too many viable options (as far as releasing Lenny is concerned) and that makes it tricky to vote in a useful way. And Christian got bitten by it: do not vote by ranking all options 1 to 7, or this vote will end up being our most EPIC FAIL to date. With that many options, the votes will end up diluted and who knows what the result will be.

For this vote to succeed and be meaningful, it’s pretty much required to rank several options equally. That is, and provided it matches your views, ranking the “Let’s release Lenny and give the finger to the zealots” options at the same level.

Be careful when voting on this one. IT’S A TRAP.