public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/2] vm_smoke_test: Drop wheezy from test
Date: Mon, 14 May 2018 18:01:12 +0200	[thread overview]
Message-ID: <20180514180112.6c0e3658@md1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <6dfb2e88-58c1-f9bd-4dac-ff13cdc26c42@ilbers.de>

Am Mon, 14 May 2018 16:49:14 +0300
schrieb Alexander Smirnov <asmirnov@ilbers.de>:

> On 05/11/2018 08:54 PM, Alexander Smirnov wrote:
> > Wheezy requires old e2fsprogs (1.42-) installed on the host,
> > otherwise wheezy kernel won't be able to mount root partition.
> > After each build host upgrade this becomes more complicated to
> > maintain outdated tool. So it's time for wheezy to slightly go...
> >   
> 
> If there are no objections, I'd like to apply this to have CI build 
> green. Then I'll be able to eventually release master :-)

I have no objections to dropping wheezy support. But if doing so the
real change is not removing it from the CI scripts and keeping it
around.
There are configs that need to be removed, docs that need to be updated.
Just "git grep wheezy" and you will find many more referrence than just
CI. We do not have a support matrix, but as long as we have code
hanging around, that suggests that a certain distro is supported ... it
should be working.

Dropping wheezy is a topic that probably deserves its own thread.

Henning

> Alex
> 


  reply	other threads:[~2018-05-14 16:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 17:54 Alexander Smirnov
2018-05-11 17:54 ` [PATCH 2/2] vm_smoke_test: Add parameters Alexander Smirnov
2018-05-14 13:49 ` [PATCH 1/2] vm_smoke_test: Drop wheezy from test Alexander Smirnov
2018-05-14 16:01   ` Henning Schild [this message]
2018-05-14 16:15     ` Alexander Smirnov
2018-05-15 16:37       ` Henning Schild

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=20180514180112.6c0e3658@md1pvb1c.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=asmirnov@ilbers.de \
    --cc=isar-users@googlegroups.com \
    /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