public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Daniel Weismüller" <daniel.weismueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.25 core141 build and put into new 2.25 pakfire trees
Date: Wed, 05 Feb 2020 13:26:33 +0100	[thread overview]
Message-ID: <a3d26adf-331c-60eb-28e6-6181aec9fbaa@ipfire.org> (raw)
In-Reply-To: <65a5b7c3ee8d6fd012ac748901b5074d39757090.camel@ipfire.org>

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

Hi

I've tried to upgrade to core 141 but I got an error.

[root(a)ipfire ~]# pakfire upgrade
CORE UPGR: Upgrading from release 139 to 141
meta-core-upgrade... 100.00% |=============================>| 994.00 B
core-upgrade-2.25... 100.00% |=============================>|    3.48 KB
meta-core-upgrade... 100.00% |=============================>| 997.00 B
core-upgrade-2.25... 100.00% |=============================>| 35.42 MB
PAKFIRE UPGR: core-upgrade-140: Decrypting...
PAKFIRE UPGR: core-upgrade-140: Upgrading files and running 
post-upgrading scripts...
PAKFIRE UPGR: core-upgrade-140: Finished.

PAKFIRE UPGR: core-upgrade-141: Decrypting...
PAKFIRE UPGR: core-upgrade-141: Upgrading files and running 
post-upgrading scripts...

Message from syslogd(a)ipfire at Wed Feb  5 11:16:00 2020 ...
ipfire ipfire: core-update-141: ERROR cannot update because not enough 
free space on root.
PAKFIRE ERROR: Returncode: 2. Sorry. Please search our forum to find a 
solution for this problem.
[root(a)ipfire ~]# df
Filesystem     1K-blocks      Used Available Use% Mounted on
devtmpfs         4010228         4   4010224   1% /dev
shm               262144        12    262132   1% /dev/shm
tmpfs            4053012       736   4052276   1% /run
/dev/sda3        1998672   1759992    117440  94% /
/dev/sda1          60400     29232     26584  53% /boot
/dev/sda4      381285708 190566412 171328012  53% /var
/var/lock           8192        12      8180   1% /var/lock
none             4053012        32   4052980   1% /var/log/vnstat
none             4053012     48768   4004244   2% /var/log/rrd
[root(a)ipfire ~]#


At first thanks for the implementation of the of the check if there is 
enough disc space before upgrading!

But what should I do now?

-

Daniel

Am 04.02.20 um 19:15 schrieb Stefan Schantl:
> Hello Arne,
>
> thanks for your hint. I've reinstalled core 141 for the latest changes
> on my dad's IPFire with PPPoE dialin and so far everything runs smooth.
>
> No problems during reboot or any kind of DNS issue.
>
> Best regards,
>
> -Stefan
>> Hi
>>
>> i have build IPFire core141 after some late changes and put the
>> images
>> in my people folder and
>> the updates to pakfire 2.25 trees for testing.
>> Because the critical dns changes i have not put into the 2.23.1
>> testing
>> trees yet. I hope i can do this
>> after some feedback. So please help testing.
>>
>> Make sure your installations are on core139 before change the tree
>> from
>> 2.23(.1) to 2.25 for updater testing!
>>
>> Arne
>>
>>

  parent reply	other threads:[~2020-02-05 12:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 18:05 Arne Fitzenreiter
2020-02-04 18:15 ` Stefan Schantl
2020-02-05 10:18   ` Michael Tremer
2020-02-05 12:26   ` Daniel Weismüller [this message]
2020-02-05 13:50     ` Michael Tremer
2020-02-06 11:23       ` Daniel Weismüller
2020-02-06 11:25         ` Michael Tremer
     [not found] <e23b18138732dc26f1ffe3239e9a3451@ipfire.org>
2020-02-06 10:47 ` Michael Tremer
     [not found] <f3c7ad86-ac3f-f1d7-369b-b0f7675589bd@ipfire.org>
2020-02-06 13:30 ` Arne Fitzenreiter
2020-02-07 14:37   ` Michael Tremer
2020-02-07 15:18     ` Tom Rymes
2020-02-07 15:36       ` Michael Tremer

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=a3d26adf-331c-60eb-28e6-6181aec9fbaa@ipfire.org \
    --to=daniel.weismueller@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