Search Results: "ag"

13 March 2008

Chris Lamb: AptFs - FUSE filesystem for APT source repositories

(This was one of those pesky “oh, it’ll only take an hour” ideas.) AptFs is a FUSE-based filesystem that provides a view to unpacked and patched Debian source packages as regular folders on a filesystem. Binary packages are modelled as symbolic links pointing to their respective source package. This arrangement allows one to: The program maintains a sliding window of unpacked packages to perform automatic cleanup of unpacked packages — it would not be very helpful if commands such as
% find /path/to/aptfs
…unpacked the entire archive into your temporary directory. Source (GPLv3) is available in Git:
% git-clone git://git.chris-lamb.co.uk/aptfs  # or
% git-clone http://git.chris-lamb.co.uk/repo/aptfs.git
Patches always welcome, and shout if you like it; I’ll file an ITP and try and upload it.

Steve Kemp: Do you have monkeys in Scotland?

I've uploaded a new make package to fix the memory corruption bug which I recently tracked down, with kind permission from the maintainer. I've also been working on a Debian Planet filtering/exclusion system. I've put together a (working) online demo, and I think I could probably inject it via greasemonkey without too many problems. (I'm a little reluctant to install that addon, because I suspect the security implications are severe). Still it was a nice hack, and actually reminds me that I like javascript these days. The demo will probably disappear in a week or two, but otherwise works as expected - just a couple of GUI issues to solve. (As with the Debian Planet search this isn't tied to our install, and could work on any PlanetPlanet installation.) Maybe it isn't the friendliest of ideas, but I think it is a good one regardless. ObQuote: Last King of Scotland

Andrew Pollock: [life] Disrupted

So my flight from SFO to AKL was nice and uneventful. I even managed to sleep for about 6 hours. The flight landed about 30 minutes early in Auckland, but alas, the connecting flight had some sort of "engineering" problems, and was delayed from a 6:30am departure, past 7:30am, and then the next thing I knew they were handing out bits of paper saying the flight wouldn't be departing until 10pm and we were all getting shuttled off to a hotel for the day. So I don't really know what happened to the flight, but the same flight number is now departing this evening. Fortunately I didn't have a huge amount to do today in Brisbane (but I have no idea what Nick had intended to do today). I currently estimate I'll get into Brisbane at around 11:30pm tonight. I've got plenty of reading I was planning on doing on the flight, which I didn't do any of, so I can keep myself occupied. I'm also going to try and catch up with Rowan and Kelly. Oh, and it was good to be able to have a shower. It sure beats sitting around in Auckland International all day. I think this is the first time I've had a delay like this. The moral of the story? Direct flights, hang the expense!

Jonathan McDowell: This week I have mostly been listening to...

Last.fm tag:cover I blame Flash but it's actually not been bad; the odd terrible choice, a few excellent versions (some of which were new to me) and mostly just acceptable covers that give me a reasonable range of stuff to listen to at work.

Romain Francoise: Emacs in bzr: initial impressions

So, since Emacs is apparently switching to bzr, I thought I'd try it out. The first thing I noticed is that cloning the repository is very slow. So slow that I killed it, thinking that it was stuck, but it wasn't. It turns out that the official page recommends downloading a tarball instead, so I did that.

Once I had my local Emacs branch, I tried a simple bzr log to see how recent the repository was. It sat there for a whole minute before even starting to show something. Apparently, all the history commands are slow... This is with a hot cache:
$ time bzr log >/dev/null
bzr log > /dev/null 44.89s user 0.58s system 99% cpu 45.563 total
$ time bzr version-info
revision-id: cvs-1:monnier-20080313012033-9ewl8gg4q3bw01z3
date: 2008-03-13 01:20:33 +0000
build-date: 2008-03-13 20:14:17 +0100
revno: 87445
branch-nick: sandbox
bzr version-info 6.41s user 0.14s system 99% cpu 6.549 total
$
Six seconds just to show me the current revision?!

Compare with my favorite scm, in a repository that contains the same history, also converted with cvsps:
$ time git log >/dev/null
git log > /dev/null 1.81s user 0.05s system 99% cpu 1.862 total
$ time git show >/dev/null
git show > /dev/null 0.02s user 0.00s system 85% cpu 0.023 total
$
Fortunately, other bzr commands such as status, diff, commit are pretty fast so this might be a problem with the conversion process, or something. At least I hope so, because as is it's completely unusable!

Christian Perrier: Squashing badly encoded changelog files - task completed

Back in February, I worked on packages providing badly encoded changelog files. With the removal of gmanedit from testing and unstable (Gnome 1.x removal process) and the ack that perl wrongly changelog encoding is mostly upstream's changelog (which will be hopefully fixed), I think its OK, now, to announce that this lenny release goal is achieved. Thanks to Bas Zoetekouw who did the mass bug filing which helped a lot tracking this down. We could now imagine tracking down badly encoded debian/copyright files... PS: above, "badly" means "using national encoding"...which is generally ISO-stoneage^W8859-1.

Mike Hommey: Recovering files from ext3

Carlo Wood wrote a nice piece of documentation about how to recover files from ext3, based on his experience after deleting 3GB. This actually happened to me 5 years ago, now, and is how ext3rminator came to exist. I’ve been meaning to update it for a while (and journal parsing has been on the top of the TODO list for a while), but package maintenance is unfortunately time consuming. And I have a big tendancy to do something else, too (like coding on git).

Mike Hommey: Xulrunner 1.9beta4 approaching experimental

It’s been a while I’ve not talked about my packages. I’ve been preparing a xulrunner trunk upload for a while now, and I must say that while I’m not totally happy with evolutions in Mozilla codebase, I do appreciate that a significant amount of the patches we were applying have been applied upstream. And even more will be applied when Firefox 3.0beta5 is released. I even got patches that were *not* in Debian to be applied. Thanks have to go to Reed Loden for all this. Another nice thing on Mozilla trunk is that they finally stopped patching sqlite, which means we can now have Mozilla linked against the system one. It is even more important now that libnss uses sqlite, too. And now that we have libcairo 1.5 in experimental, and recent enough nss and nspr in unstable (uploaded a few days ago, creating some mess with iceweasel, iceape and xulrunner), we have all the necessary bits to have (most of) the bundled libraries replaced by system ones. The sad thing is they did implement APNG (animated png) in their bundled libpng, so, to have APNG support, we need to either patch libpng or use the bundled one. I’ll see if I can just disable APNG for the moment. I hope to be able to upload the package to experimental on saturday or sunday, based on the firefox 3.0pre4 codebase. Iceweasel should follow a few days later.

MJ Ray: SPI: Forgive me world, for I have sinned

Before I start on this, note that SPI's next board meeting is next Wednesday at 1900 UTC on irc.oftc.net #spi and logs should appear here and on spi-general less than a day after. I expect the agenda will appear here. Last Tuesday morning, someone asked about SPI holding copyrights. On Tuesday afternoon, I answered with the policy and the only practice example I found. SPI's policy is fine. SPI's practice seemed unclear. On Wednesday morning, I clarified that reply to one board member and made a suggestion to one who seemed to want to ask a lawyer. On Sunday afternoon, after a staggering number of posts which weren't really getting anywhere, I tried to drag it back to the practice example a bit rudely, but that's the level the discussion had fallen to by then. It didn't go down well. It seems rude is fine from other people, but not me. Damn baggage. There was a sequence of posts telling me that SPI members weren't even allowed to ask about this task. I replied to one on Tuesday morning and took the useful bits off to debian vote. Yesterday, I lost my cool, really, and posted too much, replying to all the stupid posts suggesting that you can only ask if you wear the right hat, and one or two particularly ugly personal attacks. Sorry about that. Meanwhile, over on IRC, a draft solution to the problem has been developed/found. So all's well in the end. I give big thanks to Jimmy, Sam and Lucas in particular and a big apology for responding to the mailing list abuse.

Lars Wirzenius: Libc is broken. What now?

Today I woke up and read the news that the Ubuntu hardy C library (libc6) had been broken. The bug is so bad that the system no longer boots. Tempers are running high. What to do? There is a discussion thread on the ubuntu-devel mailing list, where someone flames the person who did the broken upload, and someone else flames the first flamer, and then other people flame the second flamer. It's a regular flamefest. It's not the most constructive reaction from any of the involved people (which is why I'm not linking to it). This is not Ubuntu specific in any way. Any system that is being developed is going to have bugs of various sorts, some really bad like this. When that happens, people are going to be annoyed. I'd like to offer the following as lessons to be learned from these kinds of episodes:
  • Developers must have the freedom to make mistakes without retaliation. Flaming counts as retaliation. Fear makes people less productive.
  • People who suffer from the bug need to vent. Preferably they will do this in private rather than in public, and without aiming it at specific people, but the need is real, and suppressing it won't improve things. Back in the old days, alt.flame worked pretty well for Usenet, perhaps that's a model that could still apply.
  • Many problems can be found via automatic testing. Perhaps testing all uploads with, say, piuparts, before they are installed into the package archive could catch some future problems. (Disclaimer: piuparts can't currently test libc or other essential packages.)
  • Even with rigorous testing, there will be catastrophic bugs. Linux could benefit from a way to recover from them that is easier than fiddling with installation media and tweaking stuff manually. There's various approaches that could apply, perhaps we should pick one and push it. "We" being not just Ubuntu, but also Debian and other distributions.

Bastian Venthur: The Eagle has Landed

Yesterday, I submitted my diploma thesis (one day before the deadline — yay!), so I will hopefully have much more time to work on my Debian packages again.

12 March 2008

Russell Coker: Not Visiting the US

I won’t be visiting the US in the forseeable future. For some time I have been concerned about the malfunctioning legal process and other related issues that arose from the so-called “War On Terror“. But the most recent news is that the TSA may just copy all the contents of your laptop or even steal it [1]. Law enforcement agents can search property if they see evidence of a crime in progress or if they have a search warrant. They can seize property as evidence in a trial, but if the property in question is not illegal then it will be returned afterwards. The TSA take property from travellers without any reason for doing so and do not return it. This is not law enforcement, it is banditry. It’s bad enough catching a late train while carrying a laptop and risking a junkie trying to steal it. When bandits have police protection (as the TSA do) then it becomes an unacceptable risk. The TSA have recently apologised for making people remove iPods and other devices from their luggage [2]. Strangely this has been interpreted by some people to mean that the TSA won’t be stealing data and hardware from travellers. I’m sure that if the TSA was going to stop searching laptop hard drives and confiscating laptops then they would have announced it. From now on I will avoid entering US territory (even for connecting flights), except in the unlikely event that someone pays me an unreasonably large amount of money such that I am prepared to travel without electronic gear. I know that some people in the US won’t like this (some people flip out when anything resembling a Boycott is mentioned). I am not Boycotting the US, merely avoiding bandits. If the fear of bandits hurts your business then you need to get a law enforcement system that can deal with the problem. On a related note, check out the TSA Gangstaz [3] video, funny.

Neil Williams: Open vs archived bugs in Debian

Bubulle asked about whether anyone has computed the number of bugs open (and by inference close) and I've just found a link from the DD statistics pages:
Debian Bug Tracking System News - These are the bugs touched during the last four hours. The data will be updated in 40 minutes.
Active Bugs 110443 (+9) 9230042 kb
Archived Bugs 366389 (+0) 24156850 kb
Debian NEW closable bugs 41
Source packages in incoming.debian.org 19
Package movement for testing +17 -2
Orphaned packages 360
Popularity contest Debian 76404 (+0) Ubuntu 448702 (+0)
Total registered dpkg/apt Users 525106

There's an RSS feed too.

Gintautas Miliauskas: Launchpad translation synchronization

Ubuntu package translation storage in Launchpad used to annoy me, primarily because the synchronization workflow between Launchpad and upstream was unclear. My questions have been partly answered on Launchpad Answers. Others working with translations in Launchpad might be interested in this information. Here's another tip for translation coordinators. I used to worry about translation pollution in Launchpad, until I found that you can clean up efficiently by sorting packages by the number of translations changed locally in Launchpad (to try it out, you can go here and click twice on the "Changed" column). Click on the number of changed translations in a given package and you will be presented with a list of the changed translations, which you can reset to upstream versions one by one by choosing "packaged" versions. It seems to be a good idea to perform such a cleanup once in a while, to keep the amount of cruft to a minimum.

Neil Williams: Serial over USB, broken laptops and screen

Well, after many failed attempts, here I am on my problematic HP laptop with a USB key mounted, a balloon3 board booted under an Emdebian root filesystem and visible over USB-to-serial using /dev/ttyUSB0 via screen.
Thanks to Daniel's tip about screen /dev/ttyUSB0 115200, my USB to Serial converter (Maplins with a Prolific PL2303 chipset) is working on my problematic HP laptop.
The proviso is that I have to reboot to enable all this stuff - allow the laptop to hibernate and all this USB stuff just disappears. :-(
The only remaining problem is the wireless - I haven't decided yet whether to patch the current stock Debian kernel (I've had enough problems without getting into more kernel issues) - I may simply buy a replacement external wireless unit or just not use wireless until the b43 driver is capable of working with the Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 02).
The magic runes for enabling USB are to add some more options to the grub boot list (on the 'kernel' line):

noapic nolapic noirqfixup

minicom still doesn't like serial over USB (on this laptop, it adds an extra line feed and then refuses to pass on any keyboard entry to the device in a similar manner to the powerpc laptop) but screen works nicely. Thanks Daniel.
With noirqfixup added, I can also plug in other USB things like a USB mouse and actually see them work. This is all good news because apart from adding these mysterious runes to Grub, this is a completely standard Debian box running Sid and with no particular configuration changes or tweaks in the system setup.
This means that I can now get on with uploading the emdebian-tools package split to Debian unstable, adapting the Emdebian root filesystem for balloon3 to support USB networking by default and suggesting screen as an alternative to minicom in the control information for the new emdebian-rootfs package. (The package split is now in Emdebian SVN - main trunk - if you are interested.) I'm also downgrading my old G4 iBook to running Lenny instead of sid and it will now stay running Lenny as Debian stable when Lenny is released. It just makes it easier to not have to keep downloading massive updates on the brief occasions that I now use the iBook.
Now if I can just work out why hibernation forgets 'noirqfixup', I'll have a usable HP laptop....
Not bad for a machine that I once considered as a complete non-starter.

David Pashley: User friendly names in warnquota

By default, warnquota sends out emails with the device name in the message, which probably doesn't make much sense to most non-technical users.
Hi,
We noticed that you are in violation with the quotasystem
used on this system. We have found the following violations:
/dev/mapper/Ubuntu-home
                        Block limits               File limits
Filesystem           used    soft    hard  grace    used  soft  hard  grace
/dev/mapper/Ubuntu-home
               +- 1044404 1000000 1200000  6days    1781     0     0
You can improve this by using /etc/quotatab to assign a more meaningful name to the partition:
/dev/mapper/Ubuntu-home:user directory
/dev/mapper/Ubuntu-shared:shared area
Read Comments (1)

Sylvain Le Gall: Linux 2.6.24 and Debian Etch on a Thinkpad x60s

I just installed a new kernel on my thinkpad. The migration was done from a 2.6.23 kernel and brings a new 80211g driver: iwl3945. This new driver is fully included in the kernel and only need an additional firmware, which can be found in firmware-iwlwifi Debian package. It works pretty well, seems to connect faster, but the blinking WIFI antenna on my laptop doesn't work anymore. It replaces ipw3945 with a daemon in user space. The installation was not straightforward, since ipw3945 and udev persistent net rules prevent it. The solution is to remove lines concerning the net interface using ipw3945 (the line "# PCI device 0x8086:0x4227 (ipw3945)" and the line after) in the file /etc/udev/rules.d/z25_persistent-net.rules. After this, you must do:
modprobe -r iwl3945
modprobe iwl3945
The file /etc/udev/rules.d/z25_persistent-net.rules now contains a line for the iwl3945 driver. Installing the driver for etch requires to update the package wireless-tools using its backport to etch and downloading/installing the package firmware-iwlwifi from unstable.

Filip Van Raemdonck: Debian firewire support

Christian, you forgot to mention the Linux kernel, where a member of the kernel team deliberately broke hardware support.
Thanks to Holger for these links, he has listed several more. I disagree with the suggestion that shipping the old firewire stack in the linux-extra-modules package is sufficient workaround; unless this is not prohibiting it from being included in the installer to support ethernet over firewire? (though in such case it will certainly have implications due to the fact that this package should be pulled in when the installer used eth1394)

So Adrian, you too may want to reconsider if Debian really does have less compatibility regressions than other distributions.

Filip Van Raemdonck: Debian firewire support

Christian, you forgot to mention the Linux kernel, where a member of the kernel team deliberately broke hardware support.
Thanks to Holger for these links, he has listed several more. I disagree with the suggestion that shipping the old firewire stack in the linux-extra-modules package is sufficient workaround; unless this is not prohibiting it from being included in the installer to support ethernet over firewire? (though in such case it will certainly have implications due to the fact that this package should be pulled in when the installer used eth1394)

So Adrian, you too may want to reconsider if Debian really does have less compatibility regressions than other distributions.

11 March 2008

Martin F. Krafft: vcs-pkg meeting in Extremadura?

If you are interested in using version control for distro packaging, you If you read the mailing list, you know about the upcoming Extremadura meeting 2-6 April 2008. If this is news to you, well, it isn t anymore. If you think you should be in Extremadura when this party takes place, don t hesitate and reply. The message ID is 20080311193428.GA25745@piper.oerlikon.madduck.net.

Next.

Previous.