From: Lars Schuhmacher <larsen007@web.de>
To: development@lists.ipfire.org
Subject: Comments regarding the upgrade process
Date: Tue, 22 Dec 2015 19:16:56 +0100 [thread overview]
Message-ID: <56799398.9020404@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2025 bytes --]
Hi,
today I updated from core 94 to 95. No problems so far, but I noticed some things that probably could be improved.
ipfire:~# pakfire upgrade
CORE UPGR: Upgrading from release 94 to 95
meta-core-upgrade... 100.00% |=============================>| 341.00 B
core-upgrade-2.17... 100.00% |=============================>| 38.04 MB
PAKFIRE UPGR: core-upgrade-95: Decrypting...
PAKFIRE UPGR: core-upgrade-95: Upgrading files and running post-upgrading scripts...
--> Would be nice to have a "--verbose" param to get
the output of "/var/log/pakfire/update-core-upgrade-95.log"
at this time. Otherwise there is not much output and
especially on slow machines the user gets nervous what is happening.
PAKFIRE UPGR: core-upgrade-95: Finished.
Core-Update 2.17
Release: 94 -> 95
Update: linux-pae
Version: 0 -> 3.14.57
Release: 0 -> 64
--> Should the previous version/release really be 0?
PAKFIRE RESV: linux-pae: Resolving dependencies...
PAKFIRE UPGR: We are going to install all packages listed above.
PAKFIRE INFO: Is this okay? [y/N]
--> Shouldn't the default be Yes?
y
linux-pae-3.14.57... 100.00% |=============================>| 25.39 MB
PAKFIRE UPGR: linux-pae: Decrypting...
PAKFIRE UPGR: linux-pae: Upgrading files and running post-upgrading scripts...
PAKFIRE UPGR: linux-pae: Finished.
--> Same as above with "--verbose", here for "/var/log/pakfire/update-linux-pae.log"
>From update-linux-pae.log:
*** Installing kernel module dependencies and firmware ***
*** Installing kernel module dependencies and firmware done ***
*** Resolving executable dependencies ***
*** Resolving executable dependencies done***
Could not find 'strip'. Not stripping the initramfs.
*** Store current command line parameters ***
*** Creating image file ***
*** Creating image file done ***
--> Should "strip" exist and is it needed?
Lars
next reply other threads:[~2015-12-22 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 18:16 Lars Schuhmacher [this message]
2015-12-22 22:36 ` Michael Tremer
2015-12-22 22:45 ` Larsen
2015-12-22 22:51 ` Michael Tremer
2015-12-22 23:25 ` Larsen
2015-12-23 0:35 ` R. W. Rodolico
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=56799398.9020404@web.de \
--to=larsen007@web.de \
--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