Bug#605009: serious performance regression with ext4

2010-11-27 Thread Jonathan Nieder
Hi Ted, Ted Ts'o wrote: 1) Suppose package contains files a, b, and c. Which are you doing? a) extract a.dpkg-new ; fsync(a.dpkg-new); rename(a.dpkg-new, a); extract b.dpkg-new ; fsync(b.dpkg-new); rename(b.dpkg-new, b); extract c.dpkg-new ; fsync(c.dpkg-new); rename(c.dpkg-new,

Bug#605009: serious performance regression with ext4

2010-11-27 Thread Mathias Behrle
* Betr.: Re: Bug#605009: serious performance regression with ext4 (Fri, 26 Nov 2010 16:33:06 +0100): On Fri, 26 Nov 2010, Mathias Behrle wrote: * Betr.: Re: Bug#605009: serious performance regression with ext4 (Fri, 26 Nov 2010 15:53:27 +0100): That was ok everywhere except on

Bug#605009: serious performance regression with ext4

2010-11-27 Thread Raphael Hertzog
On Sat, 27 Nov 2010, Jonathan Nieder wrote: c) extract(a.dpkg-new); extract(b.dpkg-new); extract(c.dpkg-new); fsync(a.dpkg-new); fsync(b.dpkg-new); fsync(c.dpkg-new); rename(a.dpkg-new, a); rename(b.dpkg-new, b); rename(c.dpkg-new, c); (c)

Bug#605009: serious performance regression with ext4

2010-11-27 Thread Guillem Jover
Hi! On Fri, 2010-11-26 at 16:52:54 -0500, Ted Ts'o wrote: On Fri, Nov 26, 2010 at 03:53:27PM +0100, Raphael Hertzog wrote: Just to sum up what dpkg --unpack does in 1.15.8.6: 1/ set the package status as half-installed/reinst-required 2/ extract all the new files as *.dpkg-new 3/ for all

Bug#605009: serious performance regression with ext4

2010-11-27 Thread Mathias Behrle
* Betr.: Fw: Bug#605009: serious performance regression with ext4 (Fri, 26 Nov 2010 22:15:06 +0100): * Betr.: Re: Bug#605009: serious performance regression with ext4 (Fri, 26 Nov 2010 16:33:06 +0100): On Fri, 26 Nov 2010, Mathias Behrle wrote: * Betr.: Re: Bug#605009: serious

Bug#605009: serious performance regression with ext4

2010-11-27 Thread Olaf van der Spek
On Fri, Nov 26, 2010 at 10:52 PM, Ted Ts'o ty...@mit.edu wrote: I am guessing you are doing (a) today --- am I right?  (c) or (d) would be best. Are there any plans to provide an API for atomic (non-durable) file updates, not involving fsync? Would be simpler (for apps), faster and more general

Processed: Bug#605099 marked as pending

2010-11-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: tag 605099 pending Bug #605099 [dpkg] [l10n] Updated Czech dpkg translation Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 605099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605099

Bug#605099: marked as pending

2010-11-27 Thread Christian PERRIER
tag 605099 pending thanks Hello, Bug #605099 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=b3d0622 --- commit b3d062225c0144d28747a48bd82a5108ada1439a

Bug#604914: dpkg: Suggesting minor i18n changes

2010-11-27 Thread Guillem Jover
Hi! On Thu, 2010-11-25 at 13:14:53 +0200, Andrei POPESCU wrote: Package: dpkg Version: 1.15.8.6 Severity: wishlist Tags: l10n While translating dpkg to Romanian I stumbled across a few things that you might want to consider: Please keep submitting any other such strings that seem

Bug#604914: dpkg: Suggesting minor i18n changes

2010-11-27 Thread Christian PERRIER
Quoting Guillem Jover (guil...@debian.org): #: lib/dpkg/ehandle.c:107 msgid out of memory pushing error handler: What is this? Could you please add a note/explanation for translators or rephrase? Changed to out of memory for new error context, hope it's slightly better? I guess