Util-Linux package development
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Bernhard Voelker <mail@bernhard-voelker.de>
Cc: Ruediger Meier <sweet_f_a@gmx.de>, util-linux@vger.kernel.org
Subject: Re: sfdisk, latest fixes break ppc64
Date: Wed, 22 Apr 2015 17:46:56 +0200	[thread overview]
Message-ID: <20150422154656.GG27969@ws.net.home> (raw)
In-Reply-To: <5537B53F.2070805@bernhard-voelker.de>

On Wed, Apr 22, 2015 at 04:50:39PM +0200, Bernhard Voelker wrote:
> On 04/22/2015 04:20 PM, Ruediger Meier wrote:
> >On Wednesday 22 April 2015, Karel Zak wrote:
> >>  I hope so:-) Next time it would be nice to detect and fix such bugs
> >>  in major release or in .1  ... we need a way how to motivate users
> >>to use -rc releases (t-shits, beers? ;-)
> >
> >Hehe, maybe the only way is like we have it right now. 2.xx and 2.xx.1
> >are the real rc1 and rc2. The distributors have to learn to use 2.xx.2
> >only ;)
> 
> Isn't there a cross-platform CI system somewhere?
> ... okay, http://build.opensuse.org/ is one, but it usually
> doesn't track upstream changes.  There's also things like
> Hydra (http://hydra.nixos.org/) ... but this only seems to
> cover i686 and x86_64.

We already use 

    https://drone.io/github.com/karelzak/util-linux

and

    https://travis-ci.org/karelzak/util-linux

both connected to github, but for ppc64 and s390 I use machines in Red
Hat labs and during -rc1 I usually use Coverity analyzer.

It's also possible to use Fedora/Suse build farms, but we don't
execute all the tests (especially tests where is necessary root perms)
by default. 

Anyway, this is no problem, the problem is real life testing.
Fortunately, I can push unstable stuff to Fedora Rawhide :)

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2015-04-22 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 10:34 sfdisk, latest fixes break ppc64 Ruediger Meier
2015-04-22 10:13 ` Karel Zak
2015-04-22 10:42   ` Ruediger Meier
2015-04-22 13:28     ` Karel Zak
2015-04-22 14:20       ` Ruediger Meier
2015-04-22 14:50         ` Bernhard Voelker
2015-04-22 15:46           ` Karel Zak [this message]
2015-04-22 16:10             ` Ruediger Meier
2015-04-22 16:02           ` Ruediger Meier

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=20150422154656.GG27969@ws.net.home \
    --to=kzak@redhat.com \
    --cc=mail@bernhard-voelker.de \
    --cc=sweet_f_a@gmx.de \
    --cc=util-linux@vger.kernel.org \
    /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