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: Comments regarding the upgrade process
Date: Tue, 22 Dec 2015 22:36:35 +0000	[thread overview]
Message-ID: <1450823795.2928.14.camel@ipfire.org> (raw)
In-Reply-To: <56799398.9020404@web.de>

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

Hi,

I am afraid that I must disappoint you on some of these points. pakfire
in IPFire 2 is legacy code and I do not have the time to add new
features. It is just maintained as it is and bugs are fixed.

We have a rewrite of this in IPFire 3 already.

On Tue, 2015-12-22 at 19:16 +0100, Lars Schuhmacher wrote:
> 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?

Why?

> 
> 
>     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?

All binaries and kernel modules are already stripped, so stripping them
again is unnecessary.

> 
> 
> 
> Lars

-Michael

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-12-22 22:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 18:16 Lars Schuhmacher
2015-12-22 22:36 ` Michael Tremer [this message]
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=1450823795.2928.14.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