Search Results: "will"

10 May 2007

Roland Mas: Alioth going down, then up

Just a quick announcement for those of you who don't read debian-devel-announce: alioth.debian.org will be upgraded from Sarge to Etch this coming Sunday (2007-05-13). You may notice some downtime, although hopefully not too much.

Michal Čihař: Mailing lists for SVN commits

If you want to follow SVN commits on some of my SVN repositories, you can subscribe to appropriate maling list, which gets notification on each SVN commit. I hope I set up mailman correctly and everything will work as I expect :-). This list is also automatically forwared to packages.qa.debian.org, so you can also subscribe there for Debian package changes.

Martin Zobel-Helas: Packages considered for 4.0r1

As there are currently four persons working on the next stable release (Dann Frazier, Luk Claes, Julien Danjou and me), we decided to track all issues for the next stable release (4.0r1) also in the Debian BTS. So if you would like to look what we currently consider for 4.0r1, have a look here. Before adding a bug (eg. with the command bts user debian-release@lists.debian.org . usertag 420759 + SRM) please contact the stable release team first, or even better, let the stable release team add your bug there on their own. Also, not all uploaded packages to proposed-updates will automatically considered for the next stable release. Update: With “contact the stable release team first” i do mean, please send requests to debian-release@lists.d.o, not contacting release team members in private over IRC or direct eMail. And NO, h01ger, cellphone is also not an option!!!1!!!elf!!!!

Michal Čihař: Themes for 2.10.x releases

As phpMyAdmin themes for trunk are not compatible with 2.10.x releases, there was created 2.10 branch for themes compatible with those releases. Today I added 2.10 themes to demo server and they are also available as subversion snapshots. I hope this will help fixing possible issues with them.

Piotr Roszatycki: Test::Unit::Lite

I like very much a Test::Unit framework. I've found it as a very handy tool for organising the tests. I really don't like the standard Test::Simple and its deriveratives. I don't understand why I have to see the output for each failed test. I rather like the do-or-die tests grouped logically as test units. Somebody write me a note for Exception::Base module that it depends on non-core Perl modules. It is not for runtime but build dependency. Even that, it is true, because Test::Unit is a somewhat heavy module and it depends on i.e. Errors. I decided to reimplement Test::Unit. So it is available Test::Unit::Lite already! It is much lighter replacement for original Test::Unit. It should be compatible for existing test suites. The intention was possibility of bundling the Test::Unit::Lite with other module distributions:
$ perl -MTest::Unit::Lite -e bundle
It copies the Test::Unit::Lite module to the inc directory in the distribution source. The Test::Unit module isn't perfect. The most annoying behaviour is the random order for calling test cases. The Test::Unit::Lite sorts the function names and calls it always in the same order. There is not so many Perl modules distributions that use Test::Unit. I hope a little that my package could change this situation and the test units will be more popular and easier to use.

9 May 2007

Peter Van Eynde: to iceweasel or not?

At $employer I have to use meetingplace a lot, so it was rather irritating that it did not work.

After a bit of digging I hear that it works with firefox 2.0 and java 1.6. But only the original firefox, if you use iceweasel (or any renamed version I think) the 'browser test' works, but then it will tell you that you have no java installed. Clearly the application searches for firefox, does not find it and decides to give a bogus error message.

Now. Is this a iceweasel bug? I think not, but having browser detecting and adapting pages will always exist I fear so changing them all seems difficult. So let's call it a safety feature :-)

Simon Richter: Whee, it works.

The dirty work is done, and I have successfully built a busybox that links against uClibc. what is so special about that, you ask? Well, the toolchain I used is the emdebian ARM cross compiler, and the uClibc was built with dpkg-buildpackage, converted to a cross -dev package using dpkg-cross and then installed with dpkg. So the final step, providing a compiler alias, is a two line shell script away. You can use uClibc by either passing the -uclibc command line option to the compiler (in all stages), or by invoking the compiler using the arm-linux-uclibc-gcc alias. I am thinking about uClibc++ as well, however that will require additional tuning.

MJ Ray: Highway Code and Cycling

Steve Kinsella wrote:
"Your right to ride on the road is in jeopardy. The revised Highway Code says cyclists should "use cycle facilities where possible". [...] The implications of this are bad. First, we will suffer more abuse and intimidating driving. Secondly cyclists will be disobeying the Highway Code when they assess that a cycle lane or path is dangerous and act accordingly. Thirdly, if a cyclist is involved in an accident and tries to claim damages, the insurance companies are likely to argue that the rider contributed to the accident by not using the cycle facility. The Highway Code has been laid before parliament. It will automatically be approved possibly by 20 May unless it is referred to a House of Commons Committee which cannot amend it and can only recommend the whole document be rejected. [...] There is a petition on the government website. One can be sceptical about the value of these petitions but the publicity is valuable as can be seen from this Sunday Times article of 7 May. It is interesting to note that 35 MP's objected to the original revised wording. Unfortunately, the replacement wording is worse. 11,000 objections were received to the previous wording. There are 70, 000 in the CTC alone who should now be objecting. If this Highway Code is approved by government cyclists will effectively lose the right to ride on the road where there are alternative routes or adjacent facilities. Please register your name on the petition and persuade others to do the same."
(via nscycle )

MJ Ray: ADSL: Have you been TOS'd off?

One of my co-operatives, The Phone Co-op, has set clear monthly data allowances from 5GB to 20GB on its residential ADSL Max packages. If you exceed that, you get emailed (a bit before you hit the limit) and then billed GBP1.50 for each extra gig. When telling me about this, they wrote
"Unlike other ISPs, we will not impose any other restrictions to your service or how you use it"
which surprised me. Are heavy users still TOS'd off the network by other ISPs? They also announced a pound a month discount for combining ADSL and line rental, which suits me fine!

Anthony Towns: Torrenting the Debian Archive

Continuing the theme from my previous post – the first and fundamental thing any distro needs to have, and thus the first and fundamental thing to think about disintermediating, is some way of distributing software. That might be burning CDs and sending them out to resellers or OEMs, or having your stuff available for download, whether by putting it up on your own server, hosting it via a dedicated high-reliability provider like akamai, or maintaining a network of mirror sites and keeping them up to date. And, of course, anyone who wants to distribute their own software has to do the exact same thing – which either means doing it themselves, and not being able to take advantage of the scalability the distributor has already made work, or going through the distribution and dealing with the problems that entails, as well as the benefits. In this case, disintermediation and decentralisation are pretty much one and the same thing: and decentralising content distribution is already a well understood problem: that’s what peer-to-peer is all about, and peer-to-peer distribution of, well, distributions is already very successful – at least when it comes to CD (and DVD) images. Which means that just about anyone can create a CD image, and distribute it to the world in exactly the same way a major organisation like Debian or Red Hat would – upload a torrent file, run a seed, and let the magic of BitTorrent do its thing. Scalability is no longer something you need a distribution organisation to manage, instead it’s built directly into the technology itself. Unfortunately BitTorrent is designed for large static images – not something you update on a daily basis. And for better or worse, my preferred distribution (Debian testing, currently lenny) does update that frequently. Fortunately, though, BitTorrent’s an open protocol and has dozens of open source implementations – so last year I was able to propose it as part of the Google Summer of Code, and was lucky enough to get a few responses and a student to work on it. It didn’t get much further than that unfortunately – the student lost internet access not long into the programme (and for most of its duration), and that was pretty much that. So when this year’s SoC rolled around, I didn’t really expect much, and didn’t put the idea up for consideration again, but lo and behold someone came through and asked if it was still possible and if there was any more information, and when I forwarded on some of the mails from the previous year we ended up with a second chance at the project. So far it’s looking pretty good – we’ve had a lot more success at keeping in touch, and thanks to the extended schedule for the SoC this year we’ve been able to do a much better job of keeping on top of what’s going on. So much so, in fact, that there’s a first (alpha) release out before the SoC is officially due to start! Wonderful stuff! What it does at the moment is allow you to take a Packages file (the stuff “apt-get update” downloads, which includes descriptions of all the packages that are available, how they inter-depend, and so forth), and from that information create a usable torrent from which to obtain the packages themselves which can then be used to share and distribute the packages. There are two crucial steps in that: the first is allowing the torrent to work without requiring huge amounts of extra information to be distributed (which would introduce scalability problems of its own, instead of solving them), and the second is that the pieces that make up the torrent are selected in a way that matches the actual packages, so that when you upload a single new package, you are in fact only making a minor change to the torrent, rather than having it (on average) completely redefine half of the torrent (and again introduce scalability problems rather than solve them). There’s more information on the DebTorrent wiki page and Cameron’s blog if you’re interested. Anyway, it’s just an alpha release at the moment, which means while there’s code that does something, it’s not actually all that useful yet. The current plan is to next add some code to make it automatically prioritise packages based on what you’re actually using – so that rather than downloading all the debs it see, it’ll only download the ones you’ve got installed, or maybe only newer versions of the ones you’ve got installed, which should get us pretty close to the point where it’s actually useful for something. The end result, of course, is to build a tool that you can point at a Debian archive, run it on a machine connected to the Internet, and you won’t have to do anything more to have a reliable, scalable and reasonably efficient means of allowing your users to distribute and update their systems. In this case, scalable means that if you end up with as many users as Debian or Ubuntu, your users will have a comparable experience, as if you’d arranged for a similarly comprehensive mirror network, without actually having to do the leg work. And heck, presuming that works, it doesn’t even matter if no one else actually does that – it’s worth it even if it saves Debian or Ubuntu the effort of keeping track of a mirror network by hand. There are interesting possibilities at smaller scales too, of course. :)

Erich Schubert: Sch uble at LinuxTag 2007

Traditionally, the german ministry of the interior has been taking patronage for the LinuxTag. Which per-se is a good thing.However, the current minister of the interior has been publishing some "anti-terror proposals" that pretty much all opensource people see as a serious attack on their freedom, and that actually violate the constitution (or even the human rights, such as his statements towards torture).So this is a very odd situation: everybody would like to say "no" to him, but at the same time, welcome his ministry because of the good cooperation with opensource people the last years.IMHO, LinuxTag needs at least make a statement that while they welcome his efforts to establish the use of open source software in public administration, they can not agree with his political efforts with respect to the "war on terror", which pose a serious attack on the freedom of individuals.After all, there will be security experts at LinuxTag, and who if not they are capable of judging that e.g. the famous "federal trojan" won't be able to help much against organized crime (including terror organizations) because these can also organize computing safety (e.g. by not using Windows and not accepting executable data in email...). Or show up how much data abuse his proposals with respect to data gathering allow.

Erich Schubert: Munich Lindy Exchange

Munich Lindy Exchange 2007Registrations for the Munich Lindy Exchange (20. - 23. September 2007) are open.That will be a Lindy exchange to remember: this is the first Oktoberfest weekend, and of course the Lindy people will rock the Oktoberfest, too (apart from doing all kinds of other fun stuff, of course).(And yes, that means you should plan ahead - flights could become rather expensive during Oktoberfest. :-( )So if you are a Lindy Hop dancer, and want to meet some fun people, come to visit us. You won't be just a tourist, but you'll have "Munich natives" around you to show you all the cool places.Organized by Swing and the city (Christine von Scheidt).

Gustavo Franco: Re: Hypothesis about the number of Debian users, from apt-listbugs logs.

Interesting work Junichi, but I guess that you've missed some users. Your data:
I disagree with the number of users, because there's a important number missing: How many people said no to popcon. Even if your number is right or close, do you see the 1,000,000 - 48641 difference above?

The only thing I'm sure now is that we've much more than 1,000,000 users. With just the data above it isn't possible to reach the exact number. It was like ask just a few developers who will be his first option for DPL and give as a result the number of DDs and not a estimative on who's going to win.

Reference: http://www.netfort.gr.jp/~dancer/diary/daily/2007-May-9.html.en#2007-May-9-21:13:02

Michal Čihař: python-gammu has asynchronous wrapper

Yesterday I hacked asynchronous wrapper for python-gammu. It is start of progress to make Wammu behave better while talking to phone. My plan is that all operations will go through this asynchronous wrapper and will be completely non blocking to Wammu. This means no progress bar will pop up to front, but entries will appear in window as they are being read. Progress will be of course still shown, but only in status bar. The current code is only first step, next thing which has to be implemented in python-gammu are virtual commands. Those will be used for things like getting all calendar events from phone, so all you will have to do for getting all is enqueue GetAllCalendar event and worker will do all for you including progress reporting. If you want to write own application using this new wrapper, you can look at example which is in sources. It shows all current possibilities, but it will be enhanced in future.

Lars Wirzenius: Quote: Blinkenlites und cursorblinken

While cleaning up the infinite mess that is my home directory, I found the following:
ACHTUNG! ALLES LOOKENSPEEPERS! Das Internet is nicht fuer gefingerclicken und giffengrabben. Ist easy droppenpacket der routers und overloaden der backbone mit der spammen unt der me-tooen. Ist nicht fuer gewerken bei das dumpkopfen. Das musclicken sichtseeren keepen das bandwit-spewin hans in das pockets muss; relaxen und watchen das cursorblinken.
This is, obviously, a play on the old blinkenlite thing, which I also found:
A C H T U N G ! ! ! --Alles Touristen und Non Technischen Lookens Peepers-- Das maschine control is nicht fur Gefingerpoken und Mittengrabben. Oderwise is easy schnappen der Schpriggenwerk, Blownfuse, und Poppencorken mit Spitzensparken. Der Maschine is Diggen by Experten only. Is nicht fur Geverken by das Dummkopfen. Das Rubbernecken und Sightseeren keepen das Cottonpicken Hands in das Pockets. So Relaxen und Watsch das Blinkenlite.
If I ever have an actual machine room, these will go on the wall.

8 May 2007

Martin F. Krafft: Linux pains #517: unregistering network devices

Somehow my network device does not want to recognise that it actually has a carrier. This being Linux (and not Windows), I thus decide to reload the driver, after taking down the network interface:
lapse:~# ip l dev eth0
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:0a:e4:30:43:16 brd ff:ff:ff:ff:ff:ff
# notice: not UP
lapse:~# rmmod e1000
lapse kernel: unregister_netdevice: waiting for eth0 to become free.
  Usage count = 1
lapse kernel: unregister_netdevice: waiting for eth0 to become free.
  Usage count = 1
[...]
# goes on forever, uninterruptible; thus new shell:
lapse:~# ps u -C rmmod
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root      5624  0.0  0.0   1656   480 pts/2    D+   00:02   0:00 rmmod e1000
As we all well know, state 'D' uninterruptible sleep means: reboot. Especially since I cannot ssh into the box anymore (doh!), and su and sudo just end up in state 'D' as well, if I try them. So, on to reboot. Or wait, that doesn't work as the shutdown process will hang long before the filesystems get unmounted. Great. It's become impossible to argue that Linux is the more stable operating system Update: a few people responded with workarounds, ranging from use of watchdog to automate the reboot (this is my laptop, so it's not really necessary) to various combinations of flags to /sbin/shutdown or the use of sysrq to force the system to reboot without cleaning up or unmounting filesystems essentially the same as pressing the reset button. Ben Hutchings says:
I think this happens when the driver repeatedly attempts to fix an error condition and keeps scheduling future work (retaining a reference to the device) rather than giving up.
I thus ended up filing a bug against the kernel.

Daniel Stone: freedesktop.org downtime

It's just not our week, I guess. For the past couple of days, gabe.freedesktop.org (www.fd.o, ns1.fd.o, lists.fd.o) has been playing up: it will just mysteriously die with no explanation. It appears to still be alive, but we can't access it at all. Bringing it back up yields nothing suspicious before it dies, so we're suspecting some bad hardware. This wouldn't be too major a problem, bar the loss of the above-named services and dri.fd.o, openclipart.org, and a few other services, if it weren't for other things conspiring against us.

All revision control services (git/CVS/SVN committing and checkout, web access to same), Bugzilla, xorg.fd.o, people.fd.o and planet.fd.o, are on separate machines which are unaffected by this failure. But, unfortunately, we got less than 24 hours notice that our secondary DNS server at MIT was being moved, and would be offline for a while. Two DNS servers gone. Our third DNS server, hosted in the UK, is still servicing requests just fine, but apparently our registrar never noticed the update. So the third DNS server according to the glue records is home.keithp.com, which is also off the air right now for some reason.

So, ns0.bluelinux.co.uk is still serving names, and you can still access some services if you use that, but we're not sure how long until normal DNS is back up, let alone how long it will take us to get gabe fully fixed.

Sorry for the outage, please bear with us. If you think it's frustrating not being able to check www.fd.o, try checking the remote console and watching /proc/meminfo hopelessly spew into the serial console as you are unable to log in ...

MJ Ray: Boycott Novell

Boycott Novell republished my explanation of how boycotts work.
Boycotts are consumers doing judo on corporations:
  1. Most corporations aim to maximise their profit and their shareholders usually push them to do so.
  2. Boycotts are an overt way of linking lost sales to a particular issue.
  3. If it looks like it's costing more profit to suffer the boycott than to address the cause, the corporation is not maximising their profit.
  4. So, the executives should answer the boycott or the shareholders should replace them with some who will.
So, it is helpful to boycott harmful companies and it's more helpful to do so noisily.

Cameron Dale: May-08-2007

The first release is complete. You may now download debtorrent version 0.1.0 from the alioth project file list. Some notes: Here's the changelog:

Biella Coleman: San Francisco

I left there four years ago and I finally return tomorrow for a few weeks. It will be great to be back.

Next.

Previous.