search

horjulf / docker-rutorrent-autodl

21 stars 12 forks source link

autodl-irssi update errors #15

Closed kvn1351 closed 4 years ago

kvn1351 commented 4 years ago

This happens on a fresh docker :/

Any ideas?

image

The only thing I could find online was this: https://github.com/autodl-community/autodl-irssi/issues/185 https://plaza.quickbox.io/t/update-autodl-irssi/8469

MGoPhishin commented 4 years ago

Encountering this same issue described above since a few days ago on 2.6.2. In addition, if my IRC trackers attempt to pick something up, I get 2020-03-17 10_18_17-ruTorrent v3 9 a similar error stating "Could not parse HTTP Response"

lun4r commented 4 years ago

I've got same issue. autodl-irssi v.2.6.2 /autodl-trackers v282

akzkak commented 4 years ago

Fixed by reverting back to previous version in "/rutorrent/.irssi/scripts/AutodlIrssi" directory.

Stop container and paste v.2.6.1 into the dir above.

horjulf commented 4 years ago

Seems to be related to SSL changes in autodl-irssi upstream, updated the base image to alpine 3.11, can you confirm its fixed in the develop build ?

Tag: horjulf/rutorrent-autodl:develop

kvn1351 commented 4 years ago

Seems to be related to SSL changes in autodl-irssi upstream, updated the base image to alpine 3.11, can you confirm its fixed in the develop build ?

Tag: horjulf/rutorrent-autodl:develop

image

Thanks!

EsEnZeT commented 4 years ago

@horjulf

Isn't this more problem, how update of autodl is handled?

[cont-init.d] 30-getautodl: executing...
Cloning into '/app/rutorrent/plugins/autodl-irssi'...
Already up to date.
Updating a94f348..b534cbe
error: Your local changes to the following files would be overwritten by merge:
    AutodlIrssi/SslSocket.pm
    AutodlIrssi/Startup.pm
    AutodlIrssi/Updater.pm
Please commit your changes or stash them before you merge.
Aborting

for now wiping 'AutodlIrssi' folder and then updating fixes problem.

horjulf commented 4 years ago

That means the contents were modified outside of the container, those files are git cloned and updated when the container starts, if you resolved the conflict, it shouldn't be an issue anymore.