slackware.uk (aka slackware.org.uk) not updating?
 

It looks like ftp://slackware.uk/slackware/ and http://slackware.uk/slackware/ are not updating.
Using ftp://slackware.no/slackware/ now ...
I also tried http://bear.alienbase.nl/mirrors/slackware/, but for reasons not researched compat32pkg cannot access e.g. its slackware-current release: "(ERROR) [--mirror] The host 'bear.alienbase.nl' is unknown or unreachable", whereas with e.g. Firefox I can access that release without problems.
:D

Edit Apr 6, 2016: I replaced the above phrase about compat32pkg -- it originally read "but compat32pkg seems to require ftp and bear does not provide that".

I suggest that you directly contact Darren to give him this information (see http://slackware.uk/ for contact information) preferably giving examples of what is not updated, as I am not sure that he visits this forum frequently.

Works fine for my MLED repo.

http://slackware.uk/microlinux/

Eh? I never used compat32pkg but it would seem strange that a tool these days requires ftp and can not work with http.
Bear server will never provide ftp, just like its predecessor 'taper' never provided ftp access.

{ftp,http}://slackware.uk/slackware/ have been updated now.
:D

Hello,

compat32pkg does not require ftp.

In your case, compat32pkg fails because http://bear.alienbase.nl/mirrors/slackware is not the url of a slackware tree as opposed to http://bear.alienbase.nl/mirrors/sla...lackware-14.1/ or http://bear.alienbase.nl/mirrors/sla...kware-current/ for instance.

--
SeB

@phenixia2003: In my Apr 5, 2016 11:04 AM post I spoke of the complete Slackware repositories. Of course I used a specific release -- i.c. slackware-current -- for compat32pkg.
When testing compat32pkg I get for http what to me looks like inconsistent results, whereas for ftp this is not the case. I do not want to debug this right now *) and amended the Apr 5, 2016 11:04 AM post therefore.
:D

*) I added debugging this to my todo list.