From: Lukas Czerner <lczerner@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: Theodore Ts'o <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] e2fsprogs: Fix autoheader failure
Date: Mon, 1 Apr 2019 17:13:35 +0200 [thread overview]
Message-ID: <20190401151335.fce73kluttm4vcpc@work> (raw)
In-Reply-To: <20190401143859.GA17530@quack2.suse.cz>
On Mon, Apr 01, 2019 at 04:38:59PM +0200, Jan Kara wrote:
> On Mon 01-04-19 09:24:12, Theodore Ts'o wrote:
> > On Mon, Apr 01, 2019 at 10:05:48AM +0200, Jan Kara wrote:
> > >
> > > No problem :). I was just packaging latest e2fsprogs release and stumbled
> > > upon this...
> >
> > If you are packaging the e2fsprogs v1.45, I suggest you either (a)
> > hold back on packaging e2scrub, or (b) wait for 1.45.1, which I hope
> > to get out fairly soon, since by packaing 1.45 for Debian unstable,
> > we've gotten many useful bug reports and as you can see, there are a
> > lot of e2scrub fixes that are queued up for the next release.
>
> Thanks for info! I did package e2scrub but so far disabled installing any
> of crond files, systemd files, or udev rules so it should be harmless
> unless someone manually runs it...
I did pretty much the same thing for rawhide and I do plan to enable the
whole thing with the next update.
Thanks!
-Lukas
>
> Honza
>
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
prev parent reply other threads:[~2019-04-01 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 16:58 [PATCH] e2fsprogs: Fix autoheader failure Jan Kara
2019-03-30 1:48 ` Theodore Ts'o
2019-04-01 8:05 ` Jan Kara
2019-04-01 13:24 ` Theodore Ts'o
2019-04-01 14:38 ` Jan Kara
2019-04-01 15:13 ` Lukas Czerner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190401151335.fce73kluttm4vcpc@work \
--to=lczerner@redhat.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox