[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#853809: marked as done (unblock: e2fsprogs/1.43.4-2)



Your message dated Fri, 10 Feb 2017 10:45:37 +0100
with message-id <65e3b28f-a134-d115-6395-47ee995b2c3b@debian.org>
and subject line Re: Bug#853809: unblock: e2fsprogs/1.43.4-2
has caused the Debian Bug report #853809,
regarding unblock: e2fsprogs/1.43.4-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
853809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853809
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package e2fsprogs

1.43.4 is the new upstream version of e2fsprogs which fixes a RC bug
(#840733: e2fsprogs contains non-free file).  n.b., the non-free file is
only used in a regression test and isn't actually included in any
binary.  There are also a number of important bug fixes that I'd really
like to get into stretch.  See the debian changelog or [1] for more
details.

[1] http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.43.4

Note: there is a udeb involved since this will also require a d-i
release manager unblock.  I'm unclear whether there is a separate
process for requesting that particlar unblock.  Please advise.

I just uploaded 1.43.4-2 to sid today, so it will be five days old when
the Stretch Freeze hits.  So I'm filing this bug now as a heads up,
since unless the release schedule slips, this isn't going to meet the
mandatory 10 day delay which was announced in December.


Files in second .deb but not in first
-------------------------------------
-rw-r--r--  root/root   /usr/share/locale/fi/LC_MESSAGES/e2fsprogs.mo
-rw-r--r--  root/root   /usr/share/locale/ms/LC_MESSAGES/e2fsprogs.mo

Files in first .deb but not in second
-------------------------------------
lrwxrwxrwx  root/root   /sbin/fsck.ext4dev -> e2fsck
lrwxrwxrwx  root/root   /sbin/mkfs.ext4dev -> mke2fs
lrwxrwxrwx  root/root   /usr/share/man/man8/fsck.ext4dev.8.gz -> e2fsck.8.gz
lrwxrwxrwx  root/root   /usr/share/man/man8/mkfs.ext4dev.8.gz -> mke2fs.8.gz

Control files: lines which differ (wdiff format)
------------------------------------------------
Installed-Size: [-3851-] {+4022+}
Pre-Depends: e2fslibs (= [-1.43.3-1),-] {+1.43.4-2),+} libblkid1 (>= 2.17.2), libc6 (>= 2.14), libcomerr2 (>= 1.42~WIP-2011-10-05-1), libss2 (>= 1.34-1), libuuid1 (>= 2.16), util-linux (>= 2.15~rc1-1)
Version: [-1.43.3-1-] {+1.43.4-2+}

unblock e2fsprogs/1.43.4-2

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable-debug'), (600, 'unstable'), (500, 'testing-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-00090-g3a45c5c (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message ---
On 08/02/17 17:44, Theodore Ts'o wrote:
> On Fri, Feb 03, 2017 at 10:34:09PM +0100, Emilio Pozuelo Monfort wrote:
>>
>> This seems fine to me, unblocked. Cc'ing debian-boot@/Cyril for the udeb unblock.
>>
> 
> Hi, I've since found a regression that I would like to fix via a
> cherry pick from upstream.  The e2fsprogs/1.43.4-2 package hasn't
> transitioned into testing yet (it will in 3 more days).
> 
> Enclosed please find the source debdiff.  Would you prefer that I wait
> for 1.43.4-2 to transition into testing, and then upload 1.43.4-3 and
> then file a new unblock request?

It's 9/10 days now and would migrate tonight, so I've aged it so it migrates in
~30 mins. Please wait for that and upload your additional fixes afterwards - you
can check if it migrated with rmadison.

Cheers,
Emilio

--- End Message ---

Reply to: