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

On Wednesday 22 April 2015, 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.

I would push it from git daily when the build and test runs always 
stable. My major problem on OBS is that we don't always have the right 
kernel modules installed.

> There's also things like 
> Hydra (http://hydra.nixos.org/) ... but this only seems to
> cover i686 and x86_64.

Our drone.io and travis-ci.org setup for x86_64 is already not bad
but a bit poor ... old ubuntu, no loop devices, no systemd. If hydra has 
more features then we could also try this.

Another thing would be gcc build farm. I have ssh login there and there 
are some interesting archs. We could set up some build cronjobs. But we 
can't be root there.
https://gcc.gnu.org/wiki/CompileFarm

BTW I've heard that Debian has also some exotic developer machines where 
one could ask for login.

cu,
Rudi

      parent reply	other threads:[~2015-04-22 16:02 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
2015-04-22 16:10             ` Ruediger Meier
2015-04-22 16:02           ` Ruediger Meier [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=201504221802.05316.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=kzak@redhat.com \
    --cc=mail@bernhard-voelker.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