Ubuntu
e2fsprogs package

Request Freeze Exception for E2fsprogs 1.40.1

Bug #124839 reported by Theodore Ts'o
4
Affects Status Importance Assigned to Milestone
e2fsprogs (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: e2fsprogs

E2fsprogs 1.40.1 has just been released into upstream, and into Debian unstable. It fixes a number of rather critical bugs that are found in the current version (1.39+1.40-WIP-2007.04.07+dfsg-2). There have been two releases since that last release, 1.40 and 1.40.1 and both have been bug-fix only releases.

Some of more notable bugs that have been fixed since then include:

* If there are corrupted inodes found in pass2, and the locale is set to Turkish, e2fsck will hang in an infinite loop due to a buggy Turkish translation which resulted in an @-expansion loop. E2fsck now has a recursive depth limit of 10 when doing @-expansions to avoid this problem.

* Partitions that previously contained an NTFS filesystem could be misidentified as NTFS instead of the ext2/3 filesystem, due to a bug in libblkid. This has bitten many Ubuntu users, who have filed a number of Launchpad bugs. Those have been largely consolidated into Launchpad #110138

* E2fsprogs 1.39 introduced a bug which caused e2fsck to not work on floppy drives. This was fixed in e2fsprogs 1.40

There are a number of other bugs that have been fixed, including Debian Bug #'s 401711, #407107, #416477, #432052, Sourceforge Bug# 1745818, and Gento Bug #146903, but the three above are the most serious.

E2fsck has also been enhanced so that if the journal is corrupted, it will remove the journal, and then automatically recreate it at the end of e2fsprogs run. In addition it is more paranoid about checking all blocks in the journal to make sure they are valid, and if uses the backup journal inode information in the superblock it will now write that information into the journal inode after the information has been checked out.

The previous version was uploaded into unstable a bit over a weak ago, and one bug was reported, which has been fixed in 1.40.1. I believe 1.40.1 to be stable, but if you want to wait 10 days until it migrates to testig, thta's also fine, but I wanted to get the request for a freeze exception in now. If there are any problems, I am monitoring the launchpad bug reports, and am prepared to fix any problems that shake out promptly.

Regards,

Ted

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

Please *dont* subscribe ubuntu-release to bugs.

Jim Qode (jimqode)
Changed in e2fsprogs:
status: New → Confirmed
Revision history for this message
Theodore Ts'o (tytso) wrote :

My apologies, but that *was* the procedure documented here:

https://wiki.ubuntu.com/FreezeExceptionProcess

If Ubuntu-release should not be subscribed to bugs requesting an exception to the Freeze Exception, please tell me what the correct procedure should be.

Revision history for this message
Theodore Ts'o (tytso) wrote : Re: [Bug 124839] Re: Request Freeze Exception for E2fsprogs 1.40.1

On Mon, Jul 09, 2007 at 07:02:02AM -0000, Sarah Hobbs wrote:
> Please *dont* subscribe ubuntu-release to bugs.

My apologies, but that *was* the procedure documented here:

https://wiki.ubuntu.com/FreezeExceptionProcess

If Ubuntu-release should not be subscribed to bugs requesting an
exception to the Freeze Exception, please tell me what the correct
procedure should be.

Thanks, regards,

      - Ted

Revision history for this message
Theodore Ts'o (tytso) wrote :

On Mon, Jul 09, 2007 at 09:43:37AM -0000, Jim Qode wrote:
> ** Changed in: e2fsprogs (Ubuntu)
> Status: New => Confirmed

Thanks,

I assume that this means the Freeze exception has been approved; can
you help walk me through the next step, if I need to do anything? I'm
a Debian developer and I'm not fully up on the Ubuntu procedures, so
it's not clear to me if I need to prepare a new set of binary packages
for Gutsy (I've built them on Feisty and Sid as part of my development
testing), or whether there is some automated process which takes the
sid upload and transmogrifies it into an Ubuntu package.

If it is the former, I assume there some kind of sponsored upload
process given that I don't have upload privileges for Ubuntu (at least
as far as I know!). Can you walk me through that?

Thanks, and thanks in advance for your accomodation of my relative
lack of inexperience in the Ubuntu processes!

                      - Ted

Revision history for this message
Daniel Hahler (blueyed) wrote :

I don't think a freeze exception is required.
According to https://wiki.ubuntu.com/GutsyReleaseSchedule we're in DebianImportFreeze, but this still allows to manually request a merge/sync.

I've taken a look at the merge (according to https://wiki.ubuntu.com/MOTU/School/Merging-and-Syncing) and filed a sync request (bug 125331).

Somebody should dupe them accordingly - I'm not sure how to proceed, too.

Revision history for this message
Theodore Ts'o (tytso) wrote :

I thought the explicit request from a developer defined in Debian Import Freeze required a Freeze Exception, but you probably know the process better than I.

Note that I am about to release 1.40.2, with two bug fixes including one reported to me today that will cause e2fsck to seg fault on a badly corrupted filesystem. Said bug
(see http://repo.or.cz/w/e2fsprogs.git?a=commit;h=5e9ba85c2694926eb784531d81ba107200cf1a51 for details) is in Feisty as well, BTW.

Revision history for this message
Daniel Hahler (blueyed) wrote :

I've marked this as a duplicate of bug 125331 and should a freeze exception be required, this would be it. And I'm also not very experienced with the process(es), but it should work out :)

Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.