From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Feedback on CU188 update peculiarity
Date: Tue, 27 Aug 2024 11:18:35 +0100 [thread overview]
Message-ID: <3D9027B2-2016-43EA-83F1-FB658278356E@ipfire.org> (raw)
In-Reply-To: <ef1696f3-08d7-4e11-a580-3ef5d5019d34@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
Hello,
This is from this and should be fixed now:
https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=6fc9957e62b4f5fe9b47e9d340480b9bc33788cd
Pakfire considered “core-update” to be a regular package because it has not been filtered out of the list of available package. It kind of is a package as in that it installs some files and runs a script to apply changes, but obviously should not be uninstalled, etc.
Therefore this used to be filtered out which did not happen in earlier builds.
This should be solved by now. If you see this again, please let me know.
-Michael
> On 26 Aug 2024, at 17:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi Michael,
>
> Something I noticed when I did the CU188 update. After finishing the update the Available Updates box says that Version: 2.27 -> 2.29 -- Release: 182 is available.
>
> If I then press the update button it repeats doing the CU188 update and at the end it again shows the same message about CU182 being available.
>
> Doing a reboot doesn't change it. The same message is there and if I press the button it repeats the CU188 update and then the same message again.
>
> Regards,
>
> Adolf.
>
>
next prev parent reply other threads:[~2024-08-27 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 16:58 Adolf Belka
2024-08-27 10:18 ` Michael Tremer [this message]
2024-08-27 16:27 ` Adolf Belka
2024-08-29 9:25 ` 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=3D9027B2-2016-43EA-83F1-FB658278356E@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