All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Martin Steigerwald <ms@teamix.de>
Cc: fio@vger.kernel.org,
	"Georg Schönberger" <gschoenberger@thomas-krenn.com>
Subject: Re: new fio release?
Date: Tue, 24 Sep 2013 08:41:51 -0600	[thread overview]
Message-ID: <5241A4AF.7030504@kernel.dk> (raw)
In-Reply-To: <1416283628.111018.1380009575092.JavaMail.zimbra@teamix.de>

On 09/24/2013 01:59 AM, Martin Steigerwald wrote:
> Hi Jens!
> 
> Georg is currently packaging fio 2.1.2 for Ubuntu Precise, while I did 2.1.1 for Debian a while ago.
> 
> I already started packaging 2.1.2 for Debian as well and I think I was almost finished with it but I had:
> 
> ms@mango:~/lokal/Debian/fio> lintian -IE fio_2.1.2-1_amd64.changes
> W: fio: script-with-language-extension usr/bin/fio2gnuplot.py
> W: fio: binary-without-manpage usr/bin/fio2gnuplot.py
> W: fio: binary-without-manpage usr/bin/genfio
> 
> which as I looked are all fixed upstream already.
> 
> Since it is difficult to rename a upstream file in debian packaging without repacking upstream tarball, I'd rather build next package from a fio release with these issues fixed.
> 
> 
> Can you do a fio 2.1.3 release?

Yeah, it's about that time anyway, and the short list of changes between
2.1.2 to now seems to indicate a decent point to do a new release.

-- 
Jens Axboe


  reply	other threads:[~2013-09-24 14:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <500349838.110961.1380009378087.JavaMail.zimbra@teamix.de>
2013-09-24  7:59 ` new fio release? Martin Steigerwald
2013-09-24 14:41   ` Jens Axboe [this message]
2013-10-09 11:02     ` Martin Steigerwald
2013-10-09 15:33       ` Jens Axboe
2013-10-10  5:23       ` Georg Schönberger
2013-10-10 12:52         ` Martin Steigerwald
2013-10-10 12:56           ` Martin Steigerwald

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=5241A4AF.7030504@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=gschoenberger@thomas-krenn.com \
    --cc=ms@teamix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.