Ten years ago, pretty much to the day, I was installing my first Debian system, a frozen Potato, using a release-candidate version of the boot-floppies. A few days later, I was reading the Policy, New Maintainer’s Guide and Developer’s Reference while building my first package.
It’s been a fun ten years, with ups and downs, and I’m looking forward to what’s coming next.
I’ve spent the last week packaging VMware Workstation 7.0.0 at work. Looking around on the net, I’ve been unable to find anything helpful about packaging this new version, so it seems nobody’s got around to packaging it yet.
I’ve asked our customer for its approval for releasing our packaging scripts to the community and got it, so here are our packaging scripts for this version, courtesy of EDF. See the instructions in debian/README.source for what has to be done to turn it into a full source package.
The packaging is based on our previous 6.5.2 packaging, which was itself based (partially, at least) upon the Gento 6.5.2 ebuild. It uses a tweaked vmware-installer to install the products to debian/tmp, then makes use of the vmware-installer database to populate the packages.
I think this method should work with any VMware product using vmware-installer 1.1.
Packages have been built and tested on Etch and Lenny.
Hope it helps! Bugs, comments, questions to the email address listed as Maintainer in debian/control, please :-)
… 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.
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.
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.
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.
Don’t like HAL? X.org now forces it upon you via xserver-xorg.
#515214, currently wishlist/wontfix.
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.
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.
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”.