From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Feedback on CU175 Testing (Not Critical - For Info)
Date: Fri, 02 Jun 2023 21:51:37 +0200 [thread overview]
Message-ID: <793ccc76-e948-7bf6-9e3a-cc6a1e487855@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
Hi All,
On my vm testbed IPFire system I have samba and cups installed. Both running and also avahi installed due to cups dependency. It is also running.
After doing the upgrade from CU174 to CU175 Testing then the cups and avahi packages are no longer running.
Missed that the first few times I was running an update to CU175 Testing and it caused the reboot to pause saying that it could not stop avahi as it was not running. If this was caused by a bug report it or wait one minute or press any key.
In later updates to CU175 Testing I then remembered to go to the services page and turn avahi and cups back on before doing the reboot. Then no error messages.
I had a look at the update.sh script and I can't figure out why it would be stopping cups and avahi let alone failing to restart them.
Not critical, not blocking, just for information for future core updates.
Regards,
Adolf.
reply other threads:[~2023-06-02 19:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=793ccc76-e948-7bf6-9e3a-cc6a1e487855@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