Search Results: "ag"

15 March 2007

Ross Burton: XICC in Mozilla

I just learnt via The Daily Chump that Firefox 3 should have support for ICC profile handling when displaying images. The initial patch was to use ColorSync which won't work on Linux, but the recent patches by Tim Rowley also use the _ICC_PROFILE from my ICC Profiles In X specification when running on Linux. Excellent news, I hope this gets integrated soon. Speaking of which, now that more applications are using this property, I should get around to extending the Screen Resolution setting in GNOME to include a colour profile selector... NP: Kaleidoscope, DJ Food

Stefano Zacchiroli: debian in gsoc

Google Summer of Code: Debian has been accepted Verbatim quote:
Congratulations!
Your organization "Debian" has been accepted in to the Google Summer of
Code(tm) 2007, and you have been marked as a potential Administrator. To
accept this request please visit
http://code.google.com/soc/mentor_step1.html and sign up using your Google
Account.
Thanks
- The Google Open Source Office

Keep on filling the proposal page! /me going to accept the above request ...

Martin Michlmayr: GNOME

GNOME provides a complete desktop environment that is easy to use. The project experienced major problems, such as delays, during its 1.x series and in particular during the preparation of its 2.0 release. GNOME introduced time based releases after its 2.0 release and has significantly improved release management. The project has published time based releases every six months for a number of years now and is considered as the reference model for a good implementation of time based release management. They have shown that it's possible to set and meet deadlines in volunteer projects and to release on time.
VersionDateMonths
1.01999-03-03
1.22000-05-2515
1.42001-04-0210
2.02002-06-2715
2.22003-02-067
2.42003-09-117
2.62004-03-317
2.82004-09-156
2.102005-03-096
2.122005-09-076
2.142006-03-156
2.162006-09-066
2.182007-03-146
Past problems Solutions Outstanding problems

Ingo Juergensmann: Debian

I've been using Debian for about 10 years now. Debian was my first Linux distribution. For about 7 years I've been running a Debian m68k buildd now. For some time now I've been worrying about Debian and its future.
IMHO, there are several reasons to worry about its future.
a) Release cycles.
Funny enough Martin Michlmayr wrote today about Gnome release cycles. Apparently Gnome suffered from similar problems in Gnome 1.x times as Debian still does today. The big difference between Gnome and Debian is: Gnome has actually learned from its mistakes and changed its release model to something better. Really. I don't use "better" very often in conjunction with "Gnome", but in this regard, the Gnome project did really something good.
Debian, on the other hand, suffers more and more from its "release everything for all when it's ready" syndrome. Releases are always delayed, it's a big chunk of work for everyone involved, Debian is losing users because of the delays and so on...
b) Debian as a base for other distributions.
Lately, several distributions announced, that they will use Ubuntu as a base for their own distribution and not Debian any longer.
c) Internal problems.
Debian has many internal problems. Many of them have to do with communication problems. Others with "you can't force anyone to do anything in Debian" ideology. Some with unresponsive persons in key positions. Some problems are a mixture of all the above. Altogether, these problems are causing that many developers are losing their fun in the long run.
d) Flame wars.
Well, actually this could be listed in b) Internel problems as well, but it's a massive problem of itself, so I think it deserves its own section. Flame wars are really time consuming and destructive. I know what I say. Been there, done that.
e) Getting new people in.
It is often said, that there are >1000 Debian Developers. The truth is that many of them are inactive or MIA. There was a proposal lately to find those inactive DDs and handle them accordingly. Given this fact of many, many inactive DDs means, that there is more work for those left. To solve this problem of overworked DDs (it's another truth, that some DDs are very active and have far too many jobs within Debian), Debian needs to attract more people and encourage people to contribute. Currently, it's not that easy for people to contribute, because of bureaucratic formalisms like sponsored uploads and such. Additionally, not everyone willing to help wants to do packaging or other tasks. There is a lot of other work to do like making graphics, organizing booths or other events, etc. Currently those tasks are mostly done by DDs that could better spent their time on developing Debian itself (packaging, porting, ...).

Ok, enough for now. But how can those problems be solved?
ad a)
Martin mentioned in his post about the Gnome Release management, that they changed from "release when it's ready" to time based releases and gained credibility because of this.
I think, Debian would benefit as well from this type of release management. Additionally, every Developer can react to this new method and make his packages fit for the release because he knows "Hey! Just 4 weeks until the release! Let's get my packages ready for it!"
Another problem, IMHO, is the "release all packages for all archs at one time" problem. This lead to the drop of m68k for etch (via some obscure circumstances like a very broken gcc 4.0 version and some strange release criteria, sometimes referenced as Vancouver Massacre).
Someone of the contestants for the new DPL job mentioned in his world domination plan to have a stable release of some basic components every year and having sub-releases for desktop environments (KDE, Gnome, XFCE...) every 6 months. Basically I believe that this is the way to go. You can discuss the time frames, of course. Release a stable base every year or every 2 years? But really, I think this would be the best way to deal with many problems Debian has.
If every 1-2 years a new stable base would be released, everyone could be happy: the admins with long release cycles for their servers, the users with faster releases for their desktops and (maybe) the porters who can (maybe) omit a subrelease of the desktop apps and concentrate on porting the base system if needed. Really. 15000 packages for (let's say) 15 archs is way too much work for everyone.

ad b)
With the above mentioned changes, Debian could re-gain some more market share and users from other distributions like Ubuntu - and be a base for distributions again. The reputation of Debian would rise again, because the releases wouldn't be delayed again.
I think it would be ok for smaller ports (like m68k) to release differently than the main archs (i386, amd64, ppc, arm): if every year a new stable base release would be done, it could be ok for them to skip a release, if necessary. Of course, details must be elaborated more in detail.

ad c)
There are many internal problems. The most urgent one is "bad communication". Needless to say that it's very important to communicate with your work mates to get your work done. If someone fails basic communication skills (answering questions about the stuff s/he is responsible for) in a reasonable time frame, s/he's simply the wrong person in that position and should be replaced. Of course this interfere with the current understanding of "not being able to be forced to do things" in Debian. People should change their mind about that.
Basically, it's similar to NMUs: if a package maintainer fails to fulfill his responsibilities (fixing bugs), he can either be enforced to fix the problem in that package by a bugreport or he can somewhat be replaced by doing a NMU when he's not fulfilling his duties. If he fails often to get his package into a good shape, he can be replaced permanently by hijacking the package.
Or to give a real world example: If you are holding a honorary post, let's say, you're doing the financial paper work for your soccer club, you can't say "Oh no... I don't have the time to do the tax declaration now or the next month...". That just doesn't work. Either you do your duties on time or you need to step down from that post. Otherwise you would do damage to your club. This is valid for other volunteer organisations as well, like Debian. Do your duties on time or step down from your post.

ad d)
Well, I'm not innocent when speaking about flame wars. Anyway, people can learn and change their mind. Flame wars are really bad in Debian, but it seems to be something like a sport to me sometimes. And usually it needs two parties for a flame war. That's the reason why I believe that expelling a fellow DD because they were involved in some major flame wars in the past is simply wrong. Either expel all parties or none.
A party is not only involved when answering to mails on mailing lists, but also when doing stuff that forces the other party to react - for example by starting a flame war on a mailing list. There's always action and always reaction. Therefore you can't disjoin both and just judge upon one party.
When a mediation is tempted, both parties are required to obey the mediators decision. Of course there should be a fair decision that honors both sides. Both sides have to give in for a successful mediation attempt. If that's not the case, the mediator failed. Not obeying to the mediators decision, because "no-one can be forced to do anything in Debian" (see above), is plainly wrong.
Anyway, most people should know of what I'm speaking here. I think it's plainly wrong to expel developers that have done really great work in the past due to some flame wars. Debian as a community has failed when it chooses this ultima ratio. Debian just proves that it is unable to establish a community where people can work together, when developers are going to get expelled because they thing that a mischief was done to him.
How would you feel and react when someone would play bad games on you? Wouldn't you yell loudly as well?
So, how can something like this be avoided? Maybe a Code of Conduct could help, maybe that CoC wouldn't be necessary when everyone would be nice to anyone and remember that there's a human being each mail with feelings and emotions?
Anyway, Debian needs to abandon flame wars in general.

ad e)
Well, I've already written a little bit about this problem above. There are many tasks in Debian that doesn't need technical excellence of packaging details - instead it needs excellence in social skills. Something that many technically focussed people are missing. Debian needs to become more attractive to those kind of people that are good at this non-technical issues and encourage them to join the project - and not to frighten them away by a very technical and bureaucratic procedure like the current NM process. Those kind of people won't wait some years to be actually being able to do work. They will just go on and find a place where their skills are better welcomed.


Ok, that's for now, I think... it's been a long post and therefore I've used folding for it.

Conclusion:
Well, not a nice one. Debian needs big changes in its structure and the candidates for the upcoming DPL elections identified some of them and put them on their agenda for their DPL period (if they win, of course). But the history showed that none of the past DPLs had really the power or the will to push big changes and made hard decisions. So, after all everything will stay as it is now. Nothing will change for the better, I fear. Users will leave Debian because of its stale release cycles, more and more Debian-based distributions will change their base to Ubuntu and Debian will become more and more irrelevant over time instead of being a strong participant in the free software world.

Tollef Fog Heen: Strength of asymmetric and symmetric encryption algorithms

Yves-Alexis Perez writes a bit about Debian and crypto-containers, comparing cryptsetup and encfs. The comparison is decent enough, except that it's fairly trivial to get cryptsetup to integrate into the whole gnome-volume-manager stack and have a dialogue pop up when you insert an encrypted USB stick or similar. Sure, it's mounted by a root process, but I wouldn't claim it's any kind of insecure because of that. What did really catch my eye was the line near the end:
[...] but this is a bruteforce attack against master password (1024 bits RSA key), not against 128bits aes key of the container.
Well, according to conventional research, a 1024 bit RSA key is about as strong as an 80 bit symmetric key. A semi-recent RSA paper confirms this too. And to the best of my knowledge, there has not been found weaknesses in AES which lower the effective key size.

Evan Prodromou: 24 Vent se CCXV

South-by-Southwest is well and truly over now. I had a really good time. I don't have quite as much fun at general-Web conferences as at wiki-specific conferences, but I think it's also healthy for me to look outside my own narrow niche every once in a while and see what other people are doing. I think overall the conference was pretty great, although I don't feel like the passion of 2006 was here in 2007. I will say that I find it disconcerting that there are so few wiki people at SxSW. I think there should be considerably more, and I'm going to urge some intelligent and thoughtful people to come to Austin next year and get on panels. Practically every aspect of blogging gets covered at SxSW, but mine was the only wiki-specific panel this year. We're taking a week on the coast near Galveston to recharge batteries and get our work lives back on track. Then it's off to Las Vegas for the IA Summit. Maj will be in the conference area -- I'll be baby-sitting at New York New York or something. tags:

Dear LazyWeb Two questions:
  • N800 movies. What ffmpeg or mencoder or transcode parameters should I use to convert video to run on the media player on my Nokia N800?
  • Zip code of Canada. In the US, when you try to charge a tank of gas using pay-at-the-pump, frequently you're asked for the ZIP code of the billing address of your credit card. But if your residential address is in Canada (or anywhere outside the US), you don't have a ZIP code attached to the card. I usually go inside to the cashier and pay there, but I wonder: is there a special code you could use (like "00000") that means "I don't have a US ZIP code"? If not, why not?
Thanks for any answers (see Contact for how to get them to me). tags:

Twittering again It seems like Twitter is waking up from its own SXSW07 hangover and sending out the thousands of backlogged twits that weren't delivered at the right time. I don't think in the age of EC2 any public Web site should go AWOL due to too much traffic. Twitter suffered just the kind of surge that EC2 (and S3) are there to solve. tags:

Erich Schubert: DBus Inspector

I've made a tiny update to DBus inspector, which works around the Tracker issue causing a segfault for many users (especially Ubuntu users, where Tracker seems to be part of a default install now?) Anyway, it should be working with the Python DBus bindings from GIT, but since they aren't released yet (or in Debian), I've added a workaround. If any service containes "Tracker" and your python dbus version is at most 0.80.2, it will just skip this service. I don't know if it's also Trackers fault that dbus-python segfaults. Download DBus Inspector Sorry, no homepage yet. Still waiting for repository and account creation on Gnome.org, which seems like a good home for it.

14 March 2007

Neil Williams: g++-3.4 and g++-4.1 cross-built side-by-side

edos-debcheck reports that the emdebian toolchain for alpha built from gcc-3.4 cannot be installed on i386 (and possibly amd64) when the repository also contains the toolchain for gcc-4.1:
libstdc++6-dev-alpha-cross (= 3.4.6-5): FAILED
The following constraints cannot be satisfied:
libstdc++6-dev-alpha-cross (= 3.4.6-5) depends on libstdc++6-alpha-cross (>= 3.4.6-5) libstdc++6-alpha-cross (= 4.1.1-21)

Yet there is no problem with these for arm or other architectures (except possibly s390). In the main Debian archive (native build), g++-3.4 depends on the gcc-4.1 version of libstdc++6. http://packages.debian.org/unstable/devel/g++-3.4.

$ edos-debcheck -explain -failures -check libstdc++6-dev-arm-cross combined

reports no errors.
('combined' here is a result of appending the Packages file from Debian to the Packages file from Emdebian although the Emdebian repository is slightly behind my own data. I'll sort out the update tomorrow.).

The repository can only contain one version of libstdc++6, just like any one system can only install one version (at least in /usr/lib):
$ reprepro list unstable libstdc++6-alpha-cross
unstable main i386: libstdc++6-alpha-cross 4.1.1-21
unstable main amd64: libstdc++6-alpha-cross 4.1.1-21
unstable main powerpc: libstdc++6-alpha-cross 4.1.1-21

By building separately, the emdebian cross-build has a dependency on 3.4.6-5 and despite the >=, edos-debcheck reports that the dependency cannot be satisfied.
$ dpkg -I /var/emdebian/debian/pool/main/g/gcc-3.4/libstdc++6-dev-alpha-cross_3.4.6-5_all.deb grep Depends
Depends: gcc-3.4-base (= 3.4.6-5), g++-3.4-alpha-linux-gnu (= 3.4.6-5), libstdc++6-alpha-cross (>= 3.4.6-5), libc6.1-dev-alpha-cross (>= 2.3.5-10)

The next cross-build of gcc-3.4 on i386 for alpha needs to use the version of libstdc++6 from the repository instead of making an older version via dpkg-cross. Not sure why this only affects alpha cross-builds.

Clint Adams: Beat your maintainers with a whisk, not a whip

Marco is remembering a time long ago, before people threw away their dictionaries so they wouldn't be able to look up what policy means, and before they started foaming at the mouth and mindlessly spouting metaphors with the word stick in them.

Maximilian Attems: ext[23] online resizing

The e2fsprogs package in Etch features the ext[23] resize2fs, see it in action on a mounted /usr partition:
nancy:/root# egrep usr /proc/mounts 
/dev/mapper/nancy_vg1-usr /usr ext3 rw,noatime,nodiratime,data=ordered 0 0
Now let's extend a bit that logical volume:
nancy:/root# lvextend -L+700M /dev/nancy_vg1/usr       
Extending logical volume usr to 4.68 GB
Logical volume usr successfully resized
Next easy step is to invoke resize2fs
nancy:/root# resize2fs /dev/nancy_vg1/usr 
resize2fs 1.40-WIP (14-Nov-2006)
Filesystem at /dev/nancy_vg1/usr is mounted on /usr; on-line resizing required
old desc_blocks = 1, new_desc_blocks = 1
Performing an on-line resize of /dev/nancy_vg1/usr to 1227776 (4k) blocks.
The filesystem on /dev/nancy_vg1/usr is now 1227776 blocks long.
Update: Mika of course already blogged about ext3 online resizing. Bug #400797 is a very good reason not to use ext2resize. I remember a post from Theodore Tso on it's bad code quality. Don't trust it.

Yves-Alexis Perez: Debian and crypto-containers

Theses days, I've been looking for a way to have crypto-containers in Debian. I wanted something easy to use, easy to move but still quite secure, which wouldn't require root access to the box, and as an option could use my gpg key.

I looked closely at two projects:

* cryptsetup/luks

The nice thing is that you only have one file containing all your crypted filesystem, it uses the Linux unified key management system (luks), and you are able to use a gpg key to crypt the data. I didn't tried it yet, because there are some drawbacks which I find really important. It uses multiple commands for every operations (creating the container, mounting and unmounting it).

For creating the crypto container you need to:
- create the file
- use it as a loop device (root access)
- initialize the container
- open the container
- create a filesystem on it
- mount it

Each time you want to mount it, you need to:
- create the loop device from the file
- open the container
- mount it

It surely can be wrapped, but that may be difficult to deploy. And you need root access for all operations (you can mount/umount without it using fstab, pmount or things like that, but still it's using privilegied access). And the major drawback, I think, is that the container size is fixed. You choose it when you create the initial file which you'll mount as a loop device. I don't know if there's a way to extend it after creating crypto-container, but anyway it'll need to be manual.

* encfs

encfs is fuse-based, so it doesn't require anything, beside fuse support in the kernel and your user belonging to fuse group. No need to root access nor anything. You create the container with only one command, then mount or umount it with only one command too. You can add and remove files from the container without asking yourself about disk usage or something, because the container is "expanded" (see after) when you add files, automatically.

There are two drawbacks in encfs, for me:
- crypto-container isn't a file, but a folder, with files and folders using crypted filenames but real size. (more or less, because you can use options to modify it but you won't hide a 20MB file for example). It's less secure than a one-file crypto-container where you can't determine how many files there are in it (and with crypsetup/luks, you won't be able to determine how much space is used in the container as the size is fixed anyway). It's less easy to move around, put on an usb key or transmit. You can tar it, yes, but you lose the comfort.
- you can't use a gpg key

In the end, I guess I'd like something like .dmg OSX Disk Images, which can be encrypted. They are really easy to use, as far as I could have seen. Maybe not so secure, but this is a bruteforce attack against master password (1024 bits RSA key), not against 128bits aes key of the container.

Anyway, I've setup an encfs folder here, but am still looking for something wich would improve the situation.

Marco d'Itri: Getting big changes in Debian

We used to be able to introduce new features distribution-wide. Many years ago the debian-policy mailing list was used to discuss new features, and every policy violation had to be fixed by maintainers. Nowadays the developers who can still be bothered to post to debian-policy can only fight about which current practices are uncontroversial enough that they can be documented. Does anybody remember the old times? When did the policy process change silently? How did it happen?

Norbert Tretkowski: Switched to GNOME

After the discussion about the upcoming non-free license change of the ion3 window manager, I decided to take a closer look at GNOME again. Last week I installed GNOME 2.14 from etch on my laptop, upgraded to 2.16 (which was a pain at that time), and found that I could actually make use of it. Meanwhile I also use GNOME 2.16 on my workstations at work and at home.

Alexander Wirt: Froscon2007 Call for Papers

Last year I was the organizer of the Debian booth at the FrOSCon in St.Augustin, Germany and I was so happy with the conference that I decided to take part in the second invocation of the conference. So I took over some tasks and here I am. The next FrOSCon takes place on August, 25th and 26th 2007 in St. Augustin, near Bonn, Germany. And will again be hosted by the faculty of computer science of the University of Applied Sciences Bonn-Rhein-Sieg in collaboration with the student body and the Linux/Unix User Group St. Augustin. Yesterday the Call for Papers started that will end on June 4th. Everybody is invited to take part and we are happy if we would get flooded by as many Papers as possible to make an even better FrOSCon as last year :).

Michael Prokop: Maintain /etc with mercurial on Debian

Based on Bart Trojanowski’s blog article “etc snapshots with git” I removed one further item from my todo list: maintain /etc with mercurial on my Debian systems. First step is creating the repository and securing access to the repository. As mercurial stores all its files within one single directory named .hg you won’t have any further directories within /etc besides /etc/.hg, rocking - right? ;-)
cd /etc
hg init
chmod og-rwx .hg
Ignore a few files:
cat > .hgignore << EOF
syntax: regexp
(^)*.dpkg-new
(^)*.dpkg-old
(^)blkid.tab( .old)
(^)mtab
# add other files if necessary, depends on your setup...
EOF
Now commit the current state:
hg add
hg ci -m "initial checkin"
We want to commit the changes automatically when using apt-get/aptitude so let’s write and include a wrapper for it:
cat > /etc/apt/hg-snapshot-script << EOF
#!/bin/sh
set -e
caller=$(ps axww   mawk '/aptitude apt-get/  for (i=5; i<=NF ; i++) printf ("%s ",$i); printf ("n")  '   head -1)
hg add 1>/dev/null
STATUS="$(hg st)"
if [ -n "$STATUS" ] ; then
   echo "hg-snapshot-script: found changed files:"
   hg st
   hg ci -m "snapshot from $LOGNAME after: $caller"
else
   echo "hg-snapshot-script: nothing to be done"
fi
EOF
chmod +x /etc/apt/hg-snapshot-script
cat >> /etc/apt/apt.conf << EOF
DPkg  
  Post-Invoke  "cd /etc ; ./apt/hg-snapshot-script"; ;
 
EOF
Finally track the two files too:
hg add
hg commit -m "apt will track /etc automagically using hg"
That’s it. :-) Oh BTW: users of subversion might want to point their browser to /etc under svk (by Enrico Zini).

Julien Valroff: Better follow bugs reported in Launchpad

In a previous entry, I explained how you can be assimilated to an Ubuntu developer without even being an official Debian developer, and of course without prior notice. I am now quite ashamed: I have just discovered that this was already discussed some time ago (read: months before my post), and led to the following results: However, packages where my name appears either in the Maintainer or in the XSBC-Original-Maintainer field still “belong” to me in Launchpad (see https://launchpad.net/~julienv/+packages for example).
However, I am not responsible for the bugs of these packages (see https://bugs.launchpad.net/~julienv/+assignedbugs) Now that my blog is syndicated on Planet Debian, I ask it again:
Am I supposed to look on Launchpad for bugs reported against the packages I maintain in Debian?
Obviously, if a bug wasn’t reported by a Debian user, it might mean nobody suffers from it, but fixing it could avoid future bug report anyway (except if this particular bug is very specific to Ubuntu). In order to improve the Debian maintainers’ work, I think it would be great that the PTS integrates the bugs in Launchpad in a simple way. This would allow us to easily subscribe to the bugs, and eventually get a notice if the bug is fixed, or at least allow us to be aware of the issue.

Phil Hands: Debian Tartan

The design is now agreed with the weavers, but unfortunately I misunderstood the price-list, so the prices I've been quoting for hand-sewn 8-yard kilts, and machined lady's 4-yard kilt-skirts were too low -- the correct prices for those and a couple of other things being:
Hand-sewn, 8 yard kilt: £420.00
Machined, 4-yard, skirt-kilt (lady's): £237.50
Machined, 6-yard kilt: £270.00
Waistcoat: £113.00
I'm sorry about quoting prices without making absolutely sure they were correct, the reason was that I was quoting the prices for standard weaves from stock, and it turns out that the custom weaves are more expensive. That said, note that the machined kilts are £80.00 cheaper than the previously quoted price (for hand-sewn), and that these are perhaps more appropriate to the use to which many of us will be putting the kilts anyway (hand-sewn are really an evening dress item, after all) Even so, I'll probably still fork out for the full 8-yards, on the basis that my dinner jacket is falling to bits after 20 years wear, so I need something new anyway. In case you're wondering what on earth I'm talking about, this has been discussed elsewhere. Just to make sure there are no other nasty surprises, if you are of a more rotund nature, you may find that it will take some extra material to encompass your circumference -- as an example, a 7 yard machined gents kilt will cost an extra fiver to stitch, and an extra £25.00 for the yard of cloth, so will come in at £300.00 rather than the usual £270.00 Confused? Well, so was I --- The designer's sending me a fuller price list, which I will ensure than anyone on the list of currently interested people is fully conversant with before we put the order in, so don't panic that I'll spend your money without giving you a final chance to come to your senses ;-) I hope that doesn't result in everyone changing their minds, but I'll understand completely if it does. Alternatively, you could decide that this is an opportunity to save yourself £80.00 by opting for a machined kilt (which AIUI are still made to measure, but just have proportionately less work and material in them) Anyway I'll post any further developments here so as not to continue spamming the lists. So, if you're interested in getting hold of any of the above despite the new prices, and have not yet told me you need to mail me now! -- the order will probably go in at the end of the week.

Eddy Petri&#537;or: ext2online is not always online

If you are running a system with ext3/ext2 on top of a LVM partition, or just when you made the partition bigger, you obviously want the file system to grow, too.

Easy, ext2online is the answer:

ext2online /dev/mapper/hdapool-homefilesystem

Unless you run into an error like:
ext2online v1.1.19 - 2001/03/18 for EXT2FS 0.5b
ext2online: group 0, block 2 not reserved

ext2online: unable to resize /dev/mapper/hdapool-homefilesystem

That's when you start googling and find that ext2online is not that online and needs the file system to be unmounted you need to run first:

ext2prepare
/dev/mapper/hdapool-homefilesystem 23G

Note that the size there is the desired new target for the filesystem.
So you log off, go to a console, umount the file system (unlucky you if is the root file system, in that case you'll need the rescue mode - does D-I have ext2prepare?), run the command.

Now fsck.ext3 the device, mount it and try again ext2online. Now it should work.

Francesco P. Lovergine: To package or not to package...

... this is the problem

I just casually saw Norbert post about the ion3 querelle. This a very unfortunate example of collapsing interactions among upstreams and maintainers. My general advice (but for suggesting to use wmii or dwm instead of ion3 :-)) is avoiding packaging of development branches, but this is a decision which sometimes is difficult to take: some programs seems in development for years and stable releases could result largerly unusable or limited. Surely our - and generally speaking any distribution - release cycle and maintainance are not adequate for many on-the-edge software out there.

When upstreams releases [a]periodical milestones, those could be packaged, but upstream will not support them: we have already our problems in supporting regular releases for security independently by upstream for mainstream programs, without adding pieces of casual crap around.

Packaging a casual snapshots is out of question IMHO, but for using it in sid/experimental, so I can understand the upstream opinion, because many users report problem to upstream instead of maintainers. I see definitively no silver bullet anyway, but for maintainers' capability of understanding what should be packaged or not and opening an unbreakable communication channel with upstreams to be up-to-date in respect with upstream roadmap.

Martin Michlmayr: GCC

The GNU Compiler Collection (GCC) is a compiler suite which supports a number of programming languages, such as C and C++. It is a very important development tool and is the standard compiler among free software projects. GCC was quite stagnant in the middle of the 1990s until the EGCS project formed. EGCS took over development of the official GCC in October 1998 and instituted rigorous processes, such as high levels of peer review, and created a steering committee which has the power to appoint maintainers and make important decisions. In theory, the project follows a time based release with an interval of six months. In practice, the project has released only one new version every year in recent times.
VersionDateMonths
3.02001-06-18
3.12002-05-1511
3.22002-08-143
3.32003-05-139
3.4.02004-04-1811
4.0.02005-04-2012
4.1.02006-02-2810
Past problems Solutions Outstanding problems

Next.

Previous.