public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Feedback on Core Update 155 Testing
Date: Wed, 17 Mar 2021 11:51:45 +0100	[thread overview]
Message-ID: <fb322a5d-c2de-4be2-80c6-088255efbbb7@ipfire.org> (raw)
In-Reply-To: <4d4c90ac-087e-1e65-f34e-ae7d512e1469@ipfire.org>

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

Hi Everyone,

On 17/03/2021 10:35, Adolf Belka wrote:
> Dear all,
>
> There is feedback on the forum about IPFire not rebooting after update 
> and needing a soft reset. After that it boots again. I also found the 
> same effect on my VM testbed system for testing.
>
> https://community.ipfire.org/t/feedback-core-update-155-testing/4896
>
> That symptom triggered my memory (a bit late) and I found the 
> discussion about my sysvinit patch.
>
> https://lists.ipfire.org/pipermail/development/2021-February/009403.html
>
> So the fix never got created and it did not revert from the update.
>
> Sorry for this mess. I will do a new patch to hopefully solve that 
> problem for adding to Core Update 155, or you can revert sysvinit and 
> I will make the update for the following Core Update.
>
Thinking about this while out walking the dog, I realised if the 
decision is to leave the updated package in Core Update 155 then I need 
to just create a patch for whatever fix is required to make it work 
properly on first boot. If the decision is to revert then I will need to 
create a patch for the full update again. I will work on creating a 
patch to just fix what is now in CU155 unless I hear differently from 
anyone.

Regards,

Adolf.

>
> I also found the same problem with ssh not working after the update as 
> mentioned in the forum post.
>
> Rebooting gave the following error message in the log.
>
> /usr/sbin/sshd: /lib/libcrypt.so.1: version `XCRYPT_2.0' not found 
> (required by /usr/sbin/sshd) [FAIL]
>
>
> People on the forum had deleted the /lib/libcrypt.so.1 link, which was 
> made to /lib/libcrypt-2.32.so and remade it to /usr/lib/libcrypt.so.1 
> and they have reported that ssh then works. I have not tried that fix 
> yet.
>
> I checked the OpenSSH update patch I created and I didn't find 
> anything related to libcrypt or a change of libcrypt location from 
> /lib to /usr/lib
>
>
> Regards,
>
> Adolf
>
-- 
Sent from my laptop


  reply	other threads:[~2021-03-17 10:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  9:35 Adolf Belka
2021-03-17 10:51 ` Adolf Belka [this message]
2021-03-17 12:40   ` Adolf Belka
2021-03-17 15:54     ` Michael Tremer
2021-03-17 15:52 ` Michael Tremer
2021-03-17 17:11 Fwd: " Adolf Belka
2021-03-18 11:31 ` Michael Tremer
2021-03-18 18:31   ` Adolf Belka

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=fb322a5d-c2de-4be2-80c6-088255efbbb7@ipfire.org \
    --to=adolf.belka@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