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 157 testing
Date: Tue, 25 May 2021 22:12:50 +0200	[thread overview]
Message-ID: <1efd62d3-38e6-27b8-56bc-bd60faafcd1a@ipfire.org> (raw)
In-Reply-To: <EFD7A473-D2A0-46BB-A96F-20855EF80810@ipfire.org>

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

Hi Michael,

On 25/05/2021 13:49, Michael Tremer wrote:
> Hi,
> 
> I had a little look and it seems that python3-inotify is missing in the updater.
> 
> Apart from that, it should work on a fresh installation.
I am not sure if your commit
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=c253116d250aedcb9e340dc68cc52086700c698c
is in the Testing build now or not yet. I just tried a fresh clone of 156 and upgraded to 157 and the same thing still happened. I am not sure if I have just been too eager.
> 
> -Michael
> 
>> On 25 May 2021, at 12:42, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Michael,
>>
>> On 25/05/2021 13:35, Michael Tremer wrote:
>>> Okay, thank you for double-checking.
>>> I assume this is a fresh installation?
>> No, this was a working Core Update 156 vm that I cloned and changed to Testing and did the update. The error message came up when rebooting after the upgrade.
>>
>>> Can you try loading the inotify Python module on a Python 3 shell?
>> I will give that a try and come back with what I find.
I tried importing inotify into python3 and got the following message
Python 3.8.7 (default, Mar 26 2021, 14:28:13)
[GCC 10.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import inotify
Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'inotify'

I then tried the same with python2 and got
Python 2.7.18 (default, Mar 26 2021, 14:26:55)
[GCC 10.2.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import inotify
>>> 

Regards,
Adolf.
>>
>> Regards,
>> Adolf.
>>> -Michael
>>>> On 25 May 2021, at 12:33, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>
>>>> Hi Michael,
>>>>
>>>> On 25/05/2021 12:18, Michael Tremer wrote:
>>>>> Hello,
>>>>> Is this problem still happening with the recent builds?
>>>> I just tried it now, 13:30 in Netherlands, and got the same result.
>>>>
>>>> This is on my VirtualBox vm testbed.
>>>>
>>>> Regards,
>>>> Adolf.
>>>>> Best,
>>>>> -Michael
>>>>>> On 21 May 2021, at 14:26, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> After updating and doing the reboot I got the following message on the boot screen.
>>>>>>
>>>>>> Starting Unbound DHCP Leases Bridge...
>>>>>> Traceback (most recent call last):
>>>>>> File "/usr/sbin/unbound-dhcp-leases-bridge", line 35, in <module>
>>>>>> import inotify.adapters
>>>>>> ModuleNotFoundError: No module named 'inotify'                          [FAIL]
>>>>>>
>>>>>> The prior message was Starting DHCP Server...    [OK]
>>>>>>
>>>>>> The following message was Starting SSH Server...    [OK] which is interesting as the ssh connection would not work until I had pressed Save in the ssh WUI page
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Adolf.
>>>>>>
>>>>>>
> 

  reply	other threads:[~2021-05-25 20:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 12:14 ummeegge
2021-05-21 12:29 ` Tom Rymes
2021-05-21 13:08 ` Michael Tremer
2021-05-21 13:19   ` Adolf Belka
2021-05-21 13:21   ` Peter Müller
2021-05-21 16:57   ` ummeegge
2021-05-25 11:17     ` Michael Tremer
2021-05-21 13:26 ` Adolf Belka
2021-05-25 10:18   ` Michael Tremer
2021-05-25 11:33     ` Adolf Belka
2021-05-25 11:35       ` Michael Tremer
2021-05-25 11:42         ` Adolf Belka
2021-05-25 11:49           ` Michael Tremer
2021-05-25 20:12             ` Adolf Belka [this message]
2021-05-23 16:15 ` Core Update 157 (testing) report Peter Müller
2021-05-25 10: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=1efd62d3-38e6-27b8-56bc-bd60faafcd1a@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