Romain Francoise: An update on md5sums, and Debian's growth
Back in August 2007 I looked at the state of embedded md5sums in Debian
packages and found that approximately 3% of the files in the
archive didn't have checksums. Three years later, things have improved:
only 0.76% of the archive is now missing checksums (sid,
main/contrib/non-free). (See this lintian report for the list of
affected packages.)
Since then there's also been various discussions on this subject and
there is now a policy bug open to make md5sums a requirement (at
the "should" level). There is also a wishlist bug against debhelper
to turn
dh_md5sums into dh_checksums with a stronger hash algorithm,
but MD5 still being good enough for simple integrity checking, it seems
rather pointless to upgrade the algorithm without a trust path in the
form of in-package signatures ala RPM...
Anyway, what's perhaps more surprising is the growth of the distribution
in only three years: sid has gone from 20774 to 30314 packages, a 45%
increase. Similarly, the number of regular files has gone from
approximately 2 million to just above 2.9 million.
Indeed, looking at our last five releases, the distribution's growth is
impressive:
- woody (2002): 8273 packages
- sarge (2005): 15195 packages (+83.7%)
- etch (2007): 18043 packages (+18.7%)
- lenny (2009): 22277 packages (+23.5%)
- squeeze (2010?): 28870 packages (+29.6%)
select p.package, version, insts from packages p, popcon where (p.architecture = 'i386' or p.architecture = 'all') and p.release = 'squeeze' and p.package = popcon.package and popcon.insts < 500 order by insts;.)
This release fixes an important ipconfig regression from Lenny due to a badly tested monster patch 4efbcf90f60. ipconfig should now perform better then ever, thanks to the inflow of fixes since Lenny release. This RC fixes are scheduled for Squeeze and it already landed in Sid.
1.5.19 had no release announcement, but fixed compilation on x86_32, the syscall handling on sh4 (initramfs-tools is said to boot fine with it), valgrind ipconfig warnings and added getrusage() for the mksh port.
Thanks to hpa for giving me the official
I ve been wondering if the following kind of testing management software exists (preferably free software, of course).
It would allow one to specify a number of test cases. For each, one should be able to describe preconditions, testing instructions and expected outcome. Also, file attachments should be supported in case a test case needs a particular data set.
It would publish a web site describing each test case.
A tester (who in the free software world could be anyone) would take a test case, follow the instructions given and observe whatever outcome occurs. The tester would then file a test report with this software, either a terse success report or a more verbose failure report.
The software should maintain testing statistics so that testers could easily choose test cases that have a dearth of reports.
As a bonus, it would be nice if the software could submit a failure report as a bug report .
(Note that this would be useful for handling the sort of tests that cannot be automated. There are many good ways already to run automated test suites.)
It looks a lot as if Facebook is closing up on third party developers. Seems
like they've cherry picked the features they want to copy, and now are no
longer interested in third parties anymore:
If you find that running Windows makes a GRUB 2-based system unbootable (
The
OCaml compiles native executables in static mode. It allows to have a minimal set of dependencies when delivering an executable. It has also disadvantages like the size of the executable and problems arising when considering libraries update -- but this is another topic. There is still one strong dependency that you should not forget when you want to deliver a product for most of the Linux distributions: dependency on the glibc version.
Trying to run OASIS compiled with Debian Lenny, on CentOS 5.5:
Due to a variety of people and places we want to see, 
The 
It consists of a set of shell scripts, which use zenity to give a nice GUI
over
Future improvements might include providing a Qt alternative (and the "g"
in the name might just mean "GUI" instead of "GTK" then), and whatever users
need. It might also become something more serious, written in a more complex
language, who knows 



