Closed TheChymera closed 6 years ago
@TheChymera Thank you very much for your issue. I will update the requirements and will have a new release running by the end of the day.
@TheChymera I updated the requirements.txt
. The functions that Arcas uses for all the above packages have not changed so you shouldn't have an issue.
The hard coded version where just the versions that I was running with when creating Arcas, no any other reason.
I tried it locally and it works for me. Please let know if you have problems.
Hey there @Nikoleta-v3 ! Thanks very much for patching this up.
Could you perhaps publish your 0.0.4
release as a static archive? The repository has a dedicated section for that.
Currently it appears that you are tracking releases as branches - this makes distribution difficult because:
9999
, and it tracks the master branch.I could track the master branch of your package as a live version - but it seems that your master branch does not include your newest fixes (e.g. the version requirements).
Thank you once again @TheChymera for your issue and ideas.
I put together a new release on Github (https://github.com/ArcasProject/Arcas/releases)
and now the master
branch is also in line with the latest version.
I am trying to package your software for Gentoo Linux, but the test suite will not pass, apparently because arcas requires an old version of
requests-mock
:Version
1.1.0
is not available in the Gentoo main tree anymore, as we have moved on to1.2.0
. Could you adapt yourrequirements.txt
to a more up to date version ofrequests-mock
?In the mean time, are there any Arcas features that would actually fail with
=requests-mock-1.2.0
?Apparently you also require an older ratelimit (currently Gentoo only provides
=ratelimit-1.4.1
), and a very specificrequests
version,2.12.1
(here, Gentoo provides more and even older versions2.8.1
,2.11.1
,2.12.5
,(~)2.13.0
,(~)2.14.2
,(~)2.18.1
,(~)2.18.2-r1
,(~)2.18.4
- yet not that very specific one).Again, could you relax these very strict constraints, and for the time being, could you detail what exactly would break if the package was used with newer dependency versions?