public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: PFire 2.21
Date: Thu, 28 Jun 2018 11:41:14 +0100	[thread overview]
Message-ID: <8987a19707614c9fd4c4a0c88beb176d60c2d7c0.camel@ipfire.org> (raw)
In-Reply-To: <b19d92af-cf23-2508-4a5f-c9785dfc6891@link38.eu>

[-- Attachment #1: Type: text/plain, Size: 4159 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello,

On Wed, 2018-06-27 at 23:07 +0200, Peter Müller wrote:
> Hello Paul,
> 
> this is the right place. Testing reports are always welcome. :-)
> 
> A crashing grub does not sound so good - especially if a firewall
> machine is physical unreachable and no remote KVM console or similar
> is available.
> 
> The 2.12 release was split up in two parts (one includes the new
> kernel, firmware files are in the second) and as far as I am aware,
> both should installed before rebooting.

Yes, you should install both in one go and then reboot. Pakfire should not
really allow you to only install one.

> > This may be my machine as I had used a live parted in the past to make a
> > properly useful size var partition.
> 
> I did not get this.

Changing the partition layout should not create any problems, because...

> @Core developers: Are we changing partition layout on existing
> installations (enlarge /boot, drop /var)?

... once the system is installed we never change any partition layout and
basically don't about it.

@Paul: Do you have any log files or so that can be useful to find out what went
wrong here?

> Yes, restoring too old backup files causes trouble. IPFire creates
> a new backup before running a core upgrade, but if this fails, it
> is hard to recover it. So better create a fresh backup before updating
> to 2.21. Should we include this in the release notes?

Pakfire automatically creates one. But people of course have to download that
from the system.

> Any observations after running on 2.21 (faster/slower/unstable/...)?

Best,
- -Michael

> 
> Thanks, and best regards,
> Peter Müller
> 
> 
> > Dear all,
> > 
> >  
> > 
> > Hopefully I am in the right place to report on 2.21
> > 
> > Just in case not - a quick summary
> > 
> > Moved to testing from stable 120.
> > 
> > Pakfire upgraded first to 121 - no reboot suggested.
> > 
> > Pakfire upgraded next to 2.21 - This time reboot required.
> > 
> >  
> > 
> > Reboot failed with a broken grub.  I could not fix this with the manual grub
> > commands to get ipfire running at all so could not rewrite grub from a
> > running system.  
> > 
> > This may be my machine as I had used a live parted in the past to make a
> > properly useful size var partition.
> > 
> >  
> > 
> > Bit the bullet and downloaded nightly build of 2.21 and reinstalled a clean
> > ipfire.
> > 
> > So far so good.
> > 
> >  
> > 
> > Only one comment about restoring previous settings from a backup.
> > 
> > My backup was old  and from a time when php was supported.  After restoring
> > the backup a surprise was in store the next time apache web interface was
> > restarted.  Apache failed as there is a reference in the conf files from
> > backup to load php so extension. 
> > 
> > Commenting out the line fixes it of course.  Just thought I would mention
> > that restoring backups from a version prior to the latest may have issues as
> > features start to get expired.
> > 
> >  
> > 
> > By the way I really admire the stuff you do and a donation is en-route. 
> > 
> >  
> > 
> > Regards,
> > 
> > Paul
> > 
> >  
> > 
> >  
> > 
> > 
> > 
> >  
> > 
> > 
> 
> 
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAls0u0oACgkQgHnw/2+Q
CQea5RAAlwmc2rNnuAO5vjeKkQRpRy2HqPrP3awFP/aCXMEiKHL5sSHCbMiuR/nF
tPaINsZPOCtTX4amaKCdy+5/XU0mtahnFcP1DtHvCDhByEQ6o/xSCVuMmGOx5gZQ
8n/IUHGgL9z4WTAM2pDUdIoOQlOIlXAU+4DZyPAaXoccAF5nHRRX7CSm7QfymcW9
Kes/Gm8QuJzW5oAj4TsPW1UUN9QF3qd3LzsINdyfCDKDZTLfwlgpoEZSWe36LzQp
jTVVVBZJpzJxs2O5hZ34hZXXl8GzkaL+oOpeuwFgAneydPhT9Qe4HjjTzNT2dAC1
GsjBRGXPwSC7s4qqTmiEwPRVopEAarEZBPEYU6KwW1Mhh72xAxi+lPqmges5S6M8
9V7zwUqkgOTsItJLqiRvW+pLj2cgSJ3lKvP2hTyS+YWaTm01xJ9Y/PleqXsK4r+T
B7U04EwRULiTkSVJqI4metGVKLHdee3zAvBRFtkyNITzIT+FGBiF5xEArh5JQPiq
W/pgGKRJ2pJylzTL9jU8eJ26go53RB8i9VVac6hDPl3N6n0/tXNkAWJrToCJHibW
FMPXBngRofWpTcfumphYKCmu1RyruMO76qgUKq1deHAJkER9jULs3OnkWd2K3r+A
0H2JUp2COUH188FMfEo7kyYodZ9ZO3cYaNVe5n1vehJe/ubnVGQ=
=PYHD
-----END PGP SIGNATURE-----


  reply	other threads:[~2018-06-28 10:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <012c01d40e59$94d51de0$be7f59a0$@ministc.com>
2018-06-27 21:07 ` Peter Müller
2018-06-28 10:41   ` Michael Tremer [this message]
2018-06-28 20:51     ` Paul Titjen
2018-06-29 17:26       ` IPFire 2.21 test report Peter Müller
2018-06-29 20:55         ` Peter Müller

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=8987a19707614c9fd4c4a0c88beb176d60c2d7c0.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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