La Salle Debain

Sun Mon Tue Wed Thu Fri Sat
26 27 28 29 30    

Open Source @ Consolidated Braincells Inc.

About La Salle Debain

This is a weblog I'm keeping about my work on Debian and any other useful Debian related info I come across. It is not meant to compete with other news sources like Debian Weekly News or Debian Planet. Mostly it is just a way for me to classify and remember all the random bits of information that I have floating around me. I thought maybe by using a blog it could be of some use to others too. Btw. "I" refers to Jaldhar H. Vyas, Debian developer for over 5 years. If you want to know more about me, my home page is here.

The name? Debain is a very common misspelling of Debian and la salle de bains means bathroom in French.

If you have a comment to make on something you read here, feel free to write to me at

You can get an rss 0.91 feed of any page in the blog by appending ?flav=rss to the end of the URL.

Thu, 17 Jul 2003

Charting Debian

Bram Stolk has created a 'self organizing map' visualisation of the dependencies in Debian packages.

It depicts all packages from testing/main with 5 or more dependencies. Instead of visualizing the dependencies directly, a classification has been made.

In the chart, all packages that have highly similar dependencies are grouped close together. Alternatively, packages placed on opposite sides of the map truly have wildly different dependencies. Clustering is present at all scales. Unfortunately, some clusters are too dense to read.

posted at: 20:19 | #

Thu, 03 Jul 2003

Guide to Gnu/Linux desktop survival

This is an introductory book with a Debian focus and lots of useful information for desktop users.

posted at: 21:07 | #

Wed, 02 Jul 2003

Status of sarge release.

<p>[Posted to debian-devel by Drew Scott Daniels.]</p> <p><a href=""></a> is the best place to discuss this. I'm going to start posting this unofficial status report there like I did for my freeze date estimate last month in <a href=""></a><br /> Again, I'm having trouble keeping this up to date and accurate, but here it is as I'll likely be busy for the next few weeks. I'll try to post another message updating this stuff again next month, but next time it'll be to debian-release.<br /> Note I don't think I've updated the menu and translation items yet.<br /> </p> <p> I may not be pointing to the canonical locations. My guesses about priorities (1-3) of things to be done before Sarge is released is below with status information. I'm unsure as to where to get status information about some things in the second paragraph below (which is mainly about packages).<br /> </p> <ul> <li>2 Installer TODO: <a href=";content-type=text/vnd.viewcvs-markup">;content-type=text/vnd.viewcvs-markup</a> you can follow my experiences in my &quot;installation-report&quot; at <a href=""></a></li> <li>1 Debian installer Ports(and architectures?) status: <a href=""></a> <a href=""></a> says all ports not likely for sarge. <a href=""></a> talks about the hurd status. <a href=""></a> seems to show that the super H (sh) is almost ready (all base compiled). Note <a href=""></a> says: &quot;If you don't have a functioning installer by release, then sure, you'll release, but you won't be installable when you do.&quot;</li> <li>2 i386 libc support? (The large thread starting with <a href=""></a> and going into the May archive talks about this). Do we have to wait for upstream to fix this? We want to stay compatible with other distributions which broke support for i386 in libc. <a href=""></a> describes the current situation.</li> <li>1 gcc 3.3 (and g++ abi change?) transition status (versions with c102 suffix): <a href=""></a> a search reveils: <a href=";num=100&amp;hl=en&amp;ie=UTF-8&amp;oe=UTF-8&amp;btnG=Google+Search&amp;as_epq=&amp;as_oq=&amp;as_eq=&amp;lr=&amp;as_ft=i&amp;as_filetype=&amp;as_qdr=all&amp;as_occt=any&amp;as_dt=i&amp;;safe=images">;num=100&amp;hl=en&amp;ie=UTF-8&amp;oe=UTF-8&amp;btnG=Google+Search&amp;as_epq=&amp;as_oq=&amp;as_eq=&amp;lr=&amp;as_ft=i&amp;as_filetype=&amp;as_qdr=all&amp;as_occt=any&amp;as_dt=i&amp;;safe=images</a> but this search is inaccurate. It only tells about the last crawled i386 package pages and includes packages that depend/recomend/suggest these i386 c102 packages. g++&ndash;3.2 and 3.3 have the same ABI. Transition should now be done to 3.3, but I beleive this means packages already compiled with 3.2 should still work.</li> <li>2 Release Critical Bugs status: <a href=""></a></li> <li>1 Problems in testing: <a href=""></a></li> <li>2 IPV6 status &amp; status guesses: <a href=""></a> and ipv6 tagged bugs: <a href=""></a> Note some 3rd party 2005 and october deadlines for IPV6 stuff in <a href=""></a></li> <li>3 Debian Description Translation Projects (DDTP?) status: <a href=""></a> with an anoucement ( <a href=""></a> ) of an APT with translation support. Also: <a href=""></a> has status and ranked information about l10n and i18n in package Descriptions and templates. <a href=""></a> (in development) talks about howto do l10n, i18n, and m17n. <a href=""></a> discusses 4 basic goals.</li> <li>2 UTF-8 or UTF8? <a href=""></a> suggests a status site. <a href=""></a> talks about the current list of programs with i18n support disabled.</li> <li>3 Package attributes: (Is done by &quot;tags&quot; and/or keywords. I'd like to include upstream trove information): <a href=""></a> has details of the tag Package browser, debtags package information and links to other package tag discussions/information.</li> <li>3 Menu system update to conform to <a href=""></a> (as suggested in <a href=""></a> ) The old update was abandonded but contributes to the new standard.</li> <li>3 AMD x86-64 port? Several threads have been on debian-devel about this. i386 packages will aparently work for this arch. (Note: According to <a href=""></a> AMD prefers the port to be called AMD64 and not x86-64 or alike) &quot;gcc-3.3 is a prerequisite&quot; says <a href=""></a> There is also a mailing list at <a href=""></a> to replace the old alioth mailing list. <a href=";bug=197117">;bug=197117</a> and <a href=""></a> may also be of interest</li> <li>3 lfs (large file size) bugs: <a href=""></a></li> </ul> <ul> <li>2 flex transition: Silently a major revision of flex came into unstable and broke parts of, postgresql and many others. flex-old is now available so a slower transition can be allowed while not delaying sarge.</li> <li>1 XFree86 status (sarge'll have 4.3.0, 4.2.1 was abandonded due to gcc compilation issues, but is back): <a href=""></a> <a href=""></a> gives some status and information about how to help. <a href=""></a> asks for help to port 4.3.0 to the AMD64 (aka x86-64). <a href=""></a> apears to be the 4.3.0 release plan. <a href=""></a> shows 4.2.1-9 is in unstable (and I'm expecting will be in testing in 2 days).</li> <li>1 Linux Kernel: The thread starting at <a href=""></a> discusses how the kernel source, images, patches and related packages need to be handled differnely, especialy for security update reasons.</li> <li>3 Linux kernel 2.6: <a href=""></a> there were some potential Debian Installer (d-i) issues listed in the same thread. In <a href=""></a> aj says not to wait for 2.6. 2.5 was feture frozen October 31, 2002 ? The thread at <a href=""></a> discusses how 2.5 can work. m68k still uses 2.2 and it's hoped that 2.2 won't be in sarge+1. Rummors of a release this summer are discussed, but it's also predicted to be &quot;unstable&quot; for a while after it goes to 2.6.</li> <li>1 KDE (3.1?)? 3.1.1 is in unstable. <a href=""></a> suggests tracking the kdebase package. The thread at <a href=""></a> talks about the current transition status.</li> <li>1 libpng transition: versioned symbols are now available. debian-devel has some discussion about this archived for Jan and Jul 2002. <a href=""></a> is quite interesting. <a href=""></a> lists some more info. <a href=""></a> described a past situation, <a href=""></a> describes the current situation.</li> <li>3 QT transition (Qt2&ndash;&gt;Qt3)? Mentioned in thread <a href=""></a></li> <li>3 MySQL 4: <a href=""></a> (note there was a libmysqlclient12 bug, it isn't lgpl and there's openssl vs gpl and gpl vs lgpl licence issues) <a href=""></a> discusses the current situation.</li> <li>1 Gnome2: <a href=""></a> (is the imlib png library compatiblility issue involve here?) In <a href=""></a> I give some status information. Some of Gnome2 is in testing.</li> <li>2 Java (some packages were in contrib/non-free because they wouldn't work with free Java implementations (ie kaffe). kaffe is free but marked [REMOVE], (Sun's jre isn't?), gjc and gij need some work acording to <a href=""></a> An old, but still relevant java faq is at <a href=""></a> I'm unsure what's holding up an upload of Kaffe (I haven't asked).</li> <li>3 guile 1.4 -&gt; 1.6 transition? <a href=""></a> Josselin Mouette says in <a href=""></a> that 1.6 is broken. It seems we'll be sticking with 1.4 for a while. <a href=""></a> and bugs.d.o seems to indicate that only build issues are holding back guile 1.6, and there are now proposed patches.</li> <li>1 Apache2, Apache and php4: <a href=""></a> Also <a href=""></a> says gdbm needs a new apache2 which has a new RC bug, waits for openldap2, and libapr0-dev in testing depends on libgdbmg1-dev which is gone. Apache2 has a version in testing.</li> <li>3 ocaml status? <a href=""></a> says there's a new target of getting 3.07 in.</li> <li>1 openldap2: <a href=""></a> openldap2 is blocking quite a few things and it looks like it'll all be fixed &quot;soon&quot; (10 days+NEW queue?)</li> </ul> <p> Some other notes:<br /> </p> <ul> <li>&quot;reasons sarge is going to blow you away&quot;: <a href=""></a></li> <li>Boot-floppies status (very likely has to be replaced with the debian-installer): <a href=""></a></li> </ul> <ul> <li>Packages not in testing reasons and prioraty lists: <a href=""></a></li> <li>Testing information: <a href=""></a></li> <li>Update excuses: <a href=""></a></li> <li>Update output: <a href=""></a></li> <li>Archives of the mailing list for &quot;Coordinating Debian releases&quot; (includes assignments and reports on assignments): <a href=""></a></li> </ul> <ul> <li>QA information (links to info on RC bugs and alike): <a href=""></a></li> </ul> <ul> <li>A Woody+1 (aka sarge) release goal wishlist: <a href=""></a></li> <li>Discussion about Woody+1 (goals) at: <a href=""></a></li> <li>Older (hamm, slink) release goals: <a href=""></a></li> </ul> <ul> <li>Info about release(d) revisions of Stable: <a href=""></a></li> <li>Website translation status: <a href=""></a></li> <li>Debian keys trust metrics: <a href=""></a> (It'd be nice to see a higher trust metric.)</li> <li>Package Popularity (popularity-contest): <a href=""></a> replaces the now broken <a href=""></a></li> </ul> <ul> <li>Devel todo list: <a href=""></a></li> </ul> <ul> <li>General information about sarge: <a href=""></a></li> <li>Package diff bethween Debian testing and unstable: <a href=""></a></li> <li><a href=""></a> talks about some dependancy loop packages and says they &quot;could have hints applied in;.</li> </ul> <p> Old items that I haven't updated because I consider them to be resolved for now:<br /> </p> <ul> <li>3 gzip rsync patch (patch will be removed or fixed for alphas): <a href=""></a> this was fixed, but there's still a bug set to hold the rsync patch out of testing.</li> <li>3 fhs status: <a href=""></a> Done, see the bugs.</li> <li>3 Postgresql (uprade bug fixed, but flex bug is kludged, help needed)</li> <li>3 Ooo ( 1.0.3?): More info at least on the debian ooo mailing list. <a href=""></a> shows some info</li> <li>2 Perl transition (5.6-5.8): The debian-perl list might have an up to date status. Perl 5.8.0-17 is in testing now.</li> <li>2 Postgresql 7.3.2r1-5 is in testing</li> <li>2 Python transition: 2.2.2-6 is in testing. <a href=""></a> shows part of how it finnished.</li> </ul>

posted at: 06:15 | #