From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Feedback on Core Update 157 testing Date: Tue, 25 May 2021 22:12:50 +0200 Message-ID: <1efd62d3-38e6-27b8-56bc-bd60faafcd1a@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8266534234012148477==" List-Id: --===============8266534234012148477== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 25/05/2021 13:49, Michael Tremer wrote: > Hi, >=20 > I had a little look and it seems that python3-inotify is missing in the upd= ater. >=20 > Apart from that, it should work on a fresh installation. I am not sure if your commit https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3Dc253116d250aedcb9e3= 40dc68cc52086700c698c 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 j= ust been too eager. >=20 > -Michael >=20 >> On 25 May 2021, at 12:42, Adolf Belka 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 Tes= ting and did the update. The error message came up when rebooting after the u= pgrade. >> >>> 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 "", line 1, in 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 >>>=20 Regards, Adolf. >> >> Regards, >> Adolf. >>> -Michael >>>> On 25 May 2021, at 12:33, Adolf Belka 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 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 >>>>>> 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 inte= resting as the ssh connection would not work until I had pressed Save in the = ssh WUI page >>>>>> >>>>>> Regards, >>>>>> >>>>>> Adolf. >>>>>> >>>>>> >=20 --===============8266534234012148477==--