v0.5.9.5-ls37 fails to start about docker-mylar3 HOT 14 CLOSED

Yes, I can reproduce it. It looks like the only change between this and the previous working image is tzdata package from the repo (likely not related) and perhaps some python modules. Looking into it.

from docker-mylar3.

@evilhero bingo. I removed pathlib.py in the latest image and it works.

Also building the nightly fresh works fine with jaraco.text 3.6.0 so that pretty much confirms it

from docker-mylar3.

FYI: v0.6.0 of Mylar3 is now up which has the pathlib file removed.

Thanks for helping @aptalca !

from docker-mylar3.

other info: this was working yesterday and the "nightly" build from 9 days ago works fine too.

from docker-mylar3.

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

from docker-mylar3.

Here are the changes to pip list between the two builds:

--- old 2021-11-02 10:14:16.382033400 -0400
+++ new 2021-11-02 10:13:25.162033400 -0400
@@ -15,10 +15,11 @@
 feedparser            6.0.8
 html5lib              1.1
 idna                  3.1
+importlib-resources   5.4.0
 jaraco.classes        3.2.1
 jaraco.collections    3.4.0
-jaraco.functools      3.3.0
-jaraco.text           3.5.1
+jaraco.functools      3.4.0
+jaraco.text           3.6.0
 lockfile              0.12.2
 Mako                  1.1.5
 MarkupSafe            2.0.1
@@ -48,7 +49,8 @@
 tempora               4.1.2
 toml                  0.10.2
 tzdata                2021.5
-tzlocal               4.0.1
+tzlocal               4.1
 urllib3               1.26.2
 webencodings          0.5.1
 zc.lockfile           2.0
+zipp                  3.6.0

from docker-mylar3.

based on that error I'd guess that it was jaraco.text but 🤷

from docker-mylar3.

Same error here

from docker-mylar3.

Reported upstream: jaraco/jaraco.text#8

from docker-mylar3.

@aptalca , I'm wondering if this might be related to the stray pathlib.py module we have in our lib subdirectory - it was removed in the python3-dev branch, but it's still in the master branch.

from docker-mylar3.

Yeah figured as such when I saw that error ( I couldn't figure out how to test the removal of it from the image ).

I was going to hold out from merging up due to some other changes, but since this is a breaker - I'll merge up py3-dev into master in a little bit which should stop any future reports to you.

from docker-mylar3.

I just put in a quick patch to remove pathlib.py from the image. Would that suffice in the meantime? Or would it cause other issues down the line?

from docker-mylar3.

Well we've removed it entirely (it shouldn't have been there) - but I'm not sure how that would affect your image pulls going forward.

I'm guessing if that if it tries to remove the file and it doesn't exist it just ignores it - in which case when the merge goes up it should be fine on your side ?

from docker-mylar3.

I'm guessing if that if it tries to remove the file and it doesn't exist it just ignores it - in which case when the merge goes up it should be fine on your side ?

Yup, it will try to remove if it exists, but will ignore if not there

from docker-mylar3.