Search Results: "ag"

13 March 2007

Erich Schubert: Debian contribution portal

In a short mail exchange with Kevin Mark, he coined the term "contribute.debian.net" (or .org). I really like this name, and the idea behind it: Similar to packages.qa.debian.org/packagename, we create a platform trying to encourage people to contribute to Debian. Stuff that should be listed here includes: Other views include the canonical translation views (DDTP/DDTSS) or the current TODO page (which is not very widely known, I think, and probably not updated very often either) and such tools, of course. Again, similar to packages.qa.debian.org, but with a focus on non-DD-contributors.

Erich Schubert: -3 unread messages

Screenshot from liferea (experimental): -3 unread blog posts This is a search folder, searching for "erich" and removing a few common false positives (mostly "Bericht" = "report" and "Gericht" = "court"). So how did I über-read these three messages? :-)

Sven Mueller: Wishlist for lenny or why debian packaging is considered hard

Eddy, while I agree that ebuilds look a lot cleaner, shorter or easier than typical debian/rules + debian/control, you should consider a few things: So all in all, I’m quite certain that the amount of learning needed to create a correct ebuild is lower than that needed to create a Debian source package, but I don’t think that packaging for Debian is hard either. And finally, Erich is quite right that a central repository for all Debian packaging scripts would be a nice thing. However it would be quite hard to determine the right VCS to use for that. Most de-central VCSes I glanced over need manual intervention on the “server” side to include patches from local developer branches. And of course there is the problem of several packages having a non-clean upstream tarball they need to repack for each release as well as several packages having a tarball which includes more than one single upstream tarball. You would need to find a way to handle those as well.

MJ Ray: OpenWRT: Belkin, I hate you so much right now

So, as mentioned, I had a go at installing OpenWRT on my router. It's pretty definitely broadcom-based, but it's a Belkin F5D7630uk4A, which is listed as Untested at the OpenWRT site. Reading up on the similar 7230 made it seem like it shouldn't be too hard, although the web interface won't take the firmware image, but I'm damned if I can persuade it to take a tftp upload of anything. I can see it bring the link up and down while rebooting. Anyone know how to get OpenWRT on one of these? While messing about, I uploaded the latest Belkin firmware and that's improved network stability, but added a new problem. After the router has been up a few hours, I see a problem similar to this ipw bug and this madwifi bug but I'm using a bcm43xx (terrible card, by the way). The only way out seems to be reboot the router, rinse and repeat. As I've noted before, I'm never buying Belkin again unless something changes. I've filed a technical support query - let's see if they can save themselves. Or can anyone help me get OpenWRT on it? See also: OpenWRT Forum post.

Wouter Verhelst: Iniscripts

Been trying out upstart today. It's a nice piece of code, but unfortunately it's totally useless today. Not because its concepts suck; rather, because Debian packages today ship with SysV-style initscripts, and those do not integrate well with upstart: most of the features that make upstart so interesting require you to create an event.d script, which has a totally different syntax. The Debian Developer inside me couldn't help but start to think about a way to fix this, but that seems harder than what it initially would sound like to the uninitiated. My first idea was to add some /sbin executable to upstart or one of its supporting packages, so that a SysV-style initscript could exit if that binary told it that upstart was running, before doing anything. That way, a package could ship both upstart event.d files and SysV-style initscripts during a migration period, and we could get rid of the SysV-style initscripts when and if Debian eventually decides to migrate to upstar. But when I sent that past #debian-devel, someone mentioned initng, which is yet a different init implementation. If this would work for upstart, it could also work for initng, and I don't think many packages would want to ship initscripts for three different init implementations. So scratch that. My next idea was to generate initscripts, rather than have packages ship them. The amount of common code in our initscripts is huge, anyway, and it's not as if it's all that hard to write an initscript. The things an initscript needs to do are limited, anyway: start a daemon when requested, stop it, restart it, perhaps send it a SIGHUP if or when configuration updates have been performed, and provide some useful output on all that. In most cases, that's about it. So, I thought, why not create an RFC822-style file (analogously to other files in the debian/ directory of a debian source package) containing all the metadata on an initscript, and generate the correct style of initscript out of that? That should work, I thought. So I started writing a specification, and had a look at the initscript of one of my own packages, nbd-server. Which does this at some point (nonrelevant content cut out):
i=0
while [ ! -z $ NBD_FILE[$i]  ]
do
  start-stop-daemon --start --quiet --exec /bin/nbd-server (...)
  echo -n " $ NBD_FILE[$i]  ]
  i=$(( $i + 1 ))
done
There's no way you'll be able to express that type of flexibility with an RFC822-style file containing all the metadata. So, scratch that too. I still do think generating initscripts is the right thing to do, however; the question that remains is "how". One idea I had was to use m4 in an autoconf kind of way, since autoconf allows one to mix autoconf macros with "regular" shell snippets, which would be exactly the kind of flexibility that one would need. However, that totally ignores the fact that autoconf is only able to pull this off because its output is shellscript in every case. An m4 macro that has to produce output which are not, in fact, shellscripts (such as would be the case for this project) could not do that. I think I'm kinda stuck now...

MJ Ray: Debian: DPL Debate (3)

I hopped onto IRC and put most of the debate questions to Gustavo Franco (stratus). You can read it next to the others - SynrG and pusling tried to help recreate the cage fight, but I think we're just too tame. There's also this linux.com article where Steve McIntyre and Anthony Towns don't answer questions and it seems the reporters didn't notice Sven Luther's withdrawal.

Julien Danjou: DeFuBu contest #8

Bug Welcome to this 8th issue of the DeFuBu contest, the almost monthly championship of the funniest bug reported to the Debian BTS. The challengers How the vote has been done Four Debian related people voted, Raphael Hertzog, Jeroen van Wolffelaar, Ana Guerrero and Margarita Manterola. Full ranking Bugs Challengers The winners Notes To participate, simply drop me an email with a bug number or a request to vote, or anything that may help. About DeFuBu

Simon Richter: Why Debian packaging is easy

Eddy, the problem with packaging software is that it is not a once-off thing, but the package needs constant maintenance, and for that, I need to be able to understand how the build process works (on a large scale). While at first the rules file generated by dh_make seems huge, it is actually quite easy to understand if you have the output of "apropos dh_" printed out and are not afraid to look at the occasional manpage.

Ingo Juergensmann: Need a job? We're hiring...

My employer is hiring and is looking for a system administrator for the office in Rostock, Germany.
The requirements are:

For more details take a look at the full job description on the debian-jobs list. We are using Debian (of course). Please note that the job description is in German.

Meike Reichle: More on pneumatics

Maks: You're welcome! This is not actually my current playlist or top 10 (or top 11) though. It's really just the songs that put most strain on said pneumatic thingy by having a rhythm that is on the one hand catchy enough to make me bounce along and on the other hand slow enough to be "doinged" with an office chair. (NOFX's Don't call me white is a good example for a totally undoingable song. The classic punk rhythm generally is just way too fast to be rendered on an office chair without stopping to type. Thinking about it, I guess Ska sucks by Propaghandi roughly marks the line between doingability and undoingability) The word creations in this post are especially dedicated to Clint. A surreal salute!

12 March 2007

Gunnar Wolf: Alive again

Due to the extreme stupidity of the bank that holds my money whenever I have some, we were unable to pay my main domain name (gwolf.org) together with two others - I mean, the fscking bank mixed up the secret questions/answers, and we were unable to confirm our identity in order to pay to my favorite registrar (do you know they sponsor Debconf? I've been their customer for at least five years, and they rock).
As of this Sunday, gwolf.org went off the net. Of course, being it a sunday, it was impossible to get a human in the right area of the bank.
I must really thank Nadezhda: Despite being quite busy today, and after spending a couple of frustrating hours Sunday night trying to reach somebody, she managed to take the needed steps. Our domains are back to life.
If you sent me a mail during this weekend, please send it again.

Roland Mas: Alioth goes Mercurial

For those who don't read debian-devel-announce: the Alioth team, with help from John Goerzen, has set up an infrastruct^W^Wa couple of scripts on Alioth, so that it's now hosting Mercurial repositories on hg.debian.org. Please read the AliothHg page on the Debian wiki for details, but don't expect many surprises: it'll work mostly the same way as the other VCSes hosted on Alioth.

Meike Reichle: What kills my office chair's pneumatic thingy

*doing* *doing* *doing* *doing*

Wouter Verhelst: The DPL race

The previous DPL races which I actively followed consisted of hectic discussions on the debian-vote mailinglist, multiple parallel long threads full of questions and answers. Given that there were 9 candidates this year (of which only 8 are left now, after Sven Luther left the race, I expected to have to write an insane amount of time-sucking emails to that list, and had somewhat prepared for that eventuality. Strangely enough, though, that hasn't happened. Since the campaigning period will come to an end this sunday, that'll mean that either most developers are waiting 'till the last minute, or that there simply aren't that many questions this year. I'm really hoping for the latter... then again, I would prefer that people actually do ask questions -- the DPL is an important position in Debian, and people really should be informing themselves before voting.

Erich Schubert: What made Debian cool

Debian used to be the cool kid among Linux distributions. Because our stuff worked much better, was easy to install and especially to upgrade. Dependencies would be automatically resolved while others were fighting dependency chaos, and our menus would have all the apps in it, where others had to fill their menus on their own. And at the same time, Debian was very flexible and could be customized to become e.g. Knoppix. Our bugtracking was great and we were openly discussing bugs and all this stuff. Many of these Debian achievements are now common among distributions. Especially among Debian-derived distributions. Debian however has become a reliable 'stable' distribution often even called 'stale', while others stand in the spotlight of innovation. Other distributions have come up with maybe more advanced bugtrackers (I'm not talking bugzilla, which IMHO is overengineered) and other tools. Technically, this isn't completely true. There are still many fields where Debian is technically leading. But our focus has recently been a lot about individual packages or components (e.g. the installer). Maybe we should try focusing more on infrastructure again. In fact, Debian still has some very good infrastructure components others might be lacking. Our QA tools (including bug counters, tracking which versions are affected by which bugs, all kinds of graphs, wotomae) are great. All our update-* commands are missing in many other distributions, also things like invoke-rc.d. We have a solid Python policy to support multiple Python versions and precompilation (judging from the SELinux policy, none of the other distributions has that yet). We're able to use dash as a minimal shell instead of bash in most places (which does make a speed and memory difference). We have Debtags. But these projects don't play a key role in Debian anymore AFAICT. Trying to start a major infrastructure thing requires a LOT of engagement, maybe too much. I'd love to see better SELinux support in Debian, but I can't do it on my own, it's just too much. And I find it very hard to find people to help me with that effort. If Enrico hadn't been pushing Debtags again and again (and with a lot of code), it would also have gone stale. Despite being IMHO something that can take Debian on top again (making it a lot easier to find appropriate software). One of the reasons why Debian is still living pretty much outside is that it would be a huge effort to get maintainers to add the corresponding Tag information to their packages and so on. I've always balked at even trying that, fortunately Enrico got some tag information added via overrides to the Packages file already. Another thing that should have been happening within Debian (but happened at Ubuntu) is 'upstart'. There have been a couple of packages dealing with new init systems, but none ever managed to get support into other packages (nor is there any package in Debian with upstart support that I'm aware of). Getting SELinux strict support into init ramdisks is another big thing I'm too scared of to even attempt... i.e. I doubt that I'll be able to do that on my own, yet even to get it into the actual packages... DPL candidates: any ideas on how to be come more agile in such points (e.g. adding support to sysvinit+upstart+initng+runit to all packages with init scripts)? It took us already ages to get LSB headers added to many init scripts. Or on any of the other transitions we should do (SELinux support, Debtags, ...), or even why we've lost this flexibility? The one idea I have for that is to try to do some hackfests. Like an init transition day, where a group of people tries to NMU most of the packages that have init scripts. Or adds "Homepage:" to most packages, which some important package metadata we only have on some packages. Or adding 'watch' files. Some of these would be easier if we had a common way of packaging and a central SVN repository. That would make it both easier to prepare the transition (e.g. committing init scripts beforehand) or especially for adding Homepage metadata and watch files without actually interfering with the maintainers work by not doing an upload immedeately, but just adding them to SVN so the maintainer includes them on his next upload. (Sorry, no comments enabled in my blog.) P.S. another thing I'd really love to see is a (semantic) PackageWiki for Debian, that has a Wiki-like structure with a page for each (Source-) package. Including things like e.g. Screenshots, Homepage link, Link to the Freshmeat page of the package, support lists/groups ... Kind of like the QA pages, but for the actual users, and editable by visitors.

Erich Schubert: The NMU that won't die.

With the help of the great qa.debian.org developer overview pages (great tool, thank you Igor and all others who contributed. It keeps on getting better!), I found out that a NMU I did during a Munich BSP for sarge still lives (it was a simple 'recommends' removal NMU): html2wml was not changed since then. Popcon lists a few installations for this, there are no bugs open, but I wonder if the package is actually still working or useful. Or if we should keep it in the repository (it has not been orphaned; but it doesn't look like the maintainer has been active since 2003, I didn't check the MIA tools though).

Erich Schubert: Debian wish for lenny

I have a Debian wish for lenny: Why do we really have to make a distinction between NMUs and maintainer uploads? I agree that we need to have someone (which can be a group) be responsible for packages and need to keep track of that to detect unmaintained packages (as well as to have someone track bug reports). With this central repository, we could have NMUs committed to the packages directly, and make contribution easier in general. For example, right now transations are usually added to a package via a bug report. The maintainer then needs to go through these bug reports (and some packages have so many open bugs I doubt the maintainer has a real overview over them; so he might easily miss some easy to fix ones), extract the patch and apply it to his package after review. With this central patch tracking system, the translators could just commit the translation change to the package directly, and it will end up in the next upload automatically. (Note that I'm not trying to force all packages to be maintained this way. I agree that for some packages it's not really appropriate. In general it should be left to the maintainers discretion. However I guess many team-maintained packages are handled in a similar way already, and I'd like to use that for my packages as well, even when not having Co-Maintainers. I'm also aware that when fixing security issues, you might not want to make your changes world visible immediately. This can however be done using SVK if we end up using SVN, for example.) Some rationale for this suggestion: In fact I think that other distributions (e.g. *BSD ports, Gentoo?) are ahead of us in this respect, having a standard way of packaging and building things and keeping track of changes. Anyway, just my € 0.02 [Yes, I'm aware that this was covered in the DPL debate, but IMHO the point of different packaging preferences falls a bit short, and probably needs to be addressed first, before being able to have a central VCS for all packages. Also I think we should be able to find a common VCS we can all live with, or at least 90% of packages.] [And yes, I'm aware that this is a controversial topic that can easily start yet another flameware. But we need to find a way of keeping flamewars down anyway...]

Erich Schubert: Swingin' M nchen

München (Munich!) has a great swing scene - alive and kicking. Lindy Hop [wikipedia], Balboa [wikipedia], Boogie Woogie [wikipedia] (~ East Coast Swing) and Rock'n'Roll [wikipedia] (the acrobatic version) all over the place. Since starting dancing (RnR some years ago, Lindy a year ago, all just socially until about half a year where I took on the others as well and started going to some real trainings), they've become an essential part of my life that I wouldn't want to miss. If you happen to come to Munich, here are some links for you: P.S. My personal favourites / recommendations: Go to Cord or Salon Erna to see how much fun the community is, then take classes with Swing and the City or Keep on Swinging.

Adam Rosi-Kessel: Rachele on Salute

Rachele is developing a restaurant critic section of her nascent blog. The latest victim: Salute.
Tonight we couldn t have been more disappointed. The bread was cold, the pizza crust was now a soft, perfectly round, plate size pizza with American style sauce and cheese. (We could have done better at Romano s down the street). And the lasagne, despite our previous server s promise, was not the same one. It was an American style lasagne that anyone could have made at home. (I would have made sure it was cooked all the way through as well.)
On the other hand, I thought my pumpkin ravioli was decent.

MJ Ray: Debian: DPL Debate (2)

Wouter Verhelst wrote:
"That line 754 came across pretty horrible, TBH. I didn't have much time to think my reply through, and it shows. What I wanted to say is that for the bits the NMs are actually involved in (ID check, T&S, P&P, etc), P&P is what takes up the most time. Waiting for an AM, waiting for the FD to check the report, and waiting for the DAM to figure it out and say "okay" all does, indeed, take much longer than that, on average."
I still don't understand how this matches the NM statistics that show the AM processing step (which includes ID check, T&S and P&P IIRC) has a shorter median than waiting for DAM. Waiting for DAM is what often takes up most time. During the audience discussion, I was told by a 2007 DD that they spent a year waiting for DAM, just like I did back in 2002. (I also was re-tested about free software while seeing NMs with very questionable philosophies get fast-tracked past me - I don't know if those still happen.) NM is still broken, but it's somehow not a campaign topic in this year's DPL election AFAICS. Elsewhere, gustavo posted that his no-show was because he was in a car crash - I think that's a fair reason for missing the debate. I'll hop on IRC after 1400 and see if I can record his answers.

Next.

Previous.