On 2020/04/20 10:37, f.holop wrote: > Stuart Henderson - Mon, 20 April 2020 at 00:28:29 > > It's trying to continue fetching (ftp -C) but the range request is > > rejected because it's trying to fetch starting at the end of the file. > > You'll see the same if you try to fetch it twice manually with ftp -C. > > I guess it didn't get renamed from cfg-if-0.1.9.tar.gz.dist to > > cfg-if-0.1.9.tar.gz maybe due to some permissions problem. > > > > ls -l distfiles/cargo/cfg-if-0.1.9.tar.gz* - anything look different > > than other files? > > there are no permission problems as far as i see. but the filename is > not good: > > $ ls -l distfiles/cargo/cfg-if-0.1.9.tar.gz* > -rw-r--r-- 1 g wheel 7353 Apr 19 23:56 > distfiles/cargo/cfg-if-0.1.9.tar.gz.part
So for some reason this file was fetched completely (this is the normal name used when fetching until it's known that the file was fetched) but wasn't renamed, and the left-over file is getting in the way. > > > > some other questions: > > > > > > where did this list of MODCARGO_CRATES come from? > > > it's not the dep list in the toml file, so it's not > > > like RUN_DEPENDS in python... is it _all_ the crates > > > from the lock file? am i supposed to fill in the licenses > > > for all of them manually? > > > > Remove the old MODCARGO_CRATES entries, run "make modcargo-gen-crates" > > and include the newly generated list in the port Makefile. > > > > Then "make modcargo-gen-crates-licenses" and replace the list in the > > Makefile with the new output which includes license information. > > > > If it now uses a new version of rust-libc newer than 0.2.63 that's ok, > > if not then put MODCARGO_CRATES_UPDATE and MODCARGO_CRATES += libc 0.2.63 > > back. > > thank you. is there documentation that i have missed, or is everyone > simply expected to read the Makefile sources? It's in port-modules(5) but it's more of a reference and expects some existing knowledge really. > would be an idea to lower the barrier to entry by creating a couple of > language specific makefile templates having workflow information > and best practices? This would probably fit better in the ports faq than manpages. > i have python porting experience but big changes are coming/keep > happening and keeping tabs on all these is unrealistic for me, hunting > for drops of wisdom like this in mailing list archives... > > -f > -- > monotheism is a gift from the gods. >
