Mariadb-10.1 download gives error 404

[Horst Simon]

Hi,

When I tried to install mariadb-10.1 I get following error, is it removed? It 
work previously.

--->  Fetching archive for mariadb-10.1
--->  Attempting to fetch mariadb-10.1-10.1.24_0+openssl.darwin_16.x86_64.tbz2 
from 
http://nou.nc.packages.macports.org/pub/macports/packages.macports.org/mariadb-10.1
--->  Attempting to fetch mariadb-10.1-10.1.24_0+openssl.darwin_16.x86_64.tbz2 
from http://sea.us.packages.macports.org/macports/packages/mariadb-10.1
--->  Attempting to fetch mariadb-10.1-10.1.24_0+openssl.darwin_16.x86_64.tbz2 
from https://packages.macports.org/mariadb-10.1
--->  Fetching distfiles for mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://aarnet.au.distfiles.macports.org/pub/macports/distfiles/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://mirror.aarnet.edu.au/pub/MariaDB/mariadb-10.1.24/source/
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://sea.us.distfiles.macports.org/macports/distfiles/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://ftp.osuosl.org/pub/mariadb/mariadb-10.1.24/source/
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
https://distfiles.macports.org/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://ftp.yz.yamagata-u.ac.jp/pub/dbms/mariadb/mariadb-10.1.24/source/
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://kmq.jp.distfiles.macports.org/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://jog.id.distfiles.macports.org/macports/distfiles/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://mirrors.supportex.net/mariadb/mariadb-10.1.24/source/
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://lil.fr.distfiles.macports.org/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://ftp.heanet.ie/mirrors/mariadb/mariadb-10.1.24/source/
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://nue.de.distfiles.macports.org/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://mirror3.layerjet.com/mariadb/mariadb-10.1.24/source/
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://mirror2.hs-esslingen.de/mariadb/mariadb-10.1.24/source/
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
https://pek.cn.distfiles.macports.org/macports/distfiles/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://mirror.switch.ch/mirror/mariadb/mariadb-10.1.24/source/
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://osl.no.distfiles.macports.org/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://cjj.kr.distfiles.macports.org/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://mirrors.fe.up.pt/pub/mariadb/mariadb-10.1.24/source/
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://jnb.za.distfiles.macports.org/distfiles/mariadb-10.1
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://gd.tuwien.ac.at/db/mariadb/mariadb-10.1.24/source/
--->  Attempting to fetch mariadb-10.1.24.tar.gz from 
http://her.gr.distfiles.macports.org/mariadb-10.1
Error: Failed to fetch mariadb-10.1: The requested URL returned error: 404 Not 
Found
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mariadb-10.1/mariadb-10.1/main.log
 for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port mariadb-10.1 failed

Regards,
Horst Simon

Re: running macports along with homebrew

[Ryan Schmidt]

On Aug 31, 2017, at 10:53, Ken Cunningham wrote:

> I think homebrew gets attention for two reasons.
> 
> 
> 1. a one-line copy & paste install command that is pasted into the terminal  
> (macports could / should do that too, BTW).

While I agree our web site, including installation instructions, needs to be 
streamlined, it's not clear to me that offering a one-line install command is a 
good idea, to the extent that I'm not sure it's a good idea to blindly download 
and run a script you don't know. MacPorts has an installer package that's 
signed, which conveys a level of trust and security, and Mac users should not 
be unfamiliar with the notion of downloading and running an installer package. 
I dare say more Mac users would be familiar with that than pasting a command 
into the terminal.

But it should be possible to write a shell script that installs MacPorts by 
downloading and installing the right pkg, if someone is keen to work on that.


> 2. the fact that it symlinks it's stuff into /usr/local, making it easier to 
> use it's installed products for building other software for amateurs 
> (macports could do that too).

We won't put things in /usr/local. It's been discussed to death why that would 
be a very bad idea. See e.g.

https://trac.macports.org/wiki/FAQ#defaultprefix

and

https://trac.macports.org/wiki/FAQ#usrlocal


> 3. My impression is that it's not so difficult to get things accepted. If a 
> submission builds on Travis on 10.10 to 10.12, it's usually in homebrew 
> within a day or so, it seems.

I'd echo what's been said elsewhere: if a MacPorts ticket or PR isn't getting 
attention after a few days, you can remind the macports-dev mailing list about 
it and hopefully someone will get to it. If we don't have enough developers 
getting to such things, that may indicate that we need to approve additional 
developers for commit access. The process for requesting commit access is 
documented in the guide. Sometimes we managers need reminders about answering 
those requests too, but we really do want to grant commit access to good 
developers who want to help, and that especially means developers who won't 
confine themselves to just updating the few ports they personally care about, 
but rather those who will seek out and handle open tickets and PRs for other 
ports.

Re: running macports along with homebrew

[Daniel J. Luke]

On Aug 31, 2017, at 3:34 PM, Craig Treleaven  wrote:
> AIUI, casks are supposed to help in two ways:  binary (only) packages and 
> pre-compiled binaries.
> 
> MacPorts solved the second part several years ago.  As an aside, I think a 
> lot of people using Homebrew never got this message.

Indeed, a quick look at pacakges.macports.org indicates there are 22,957 binary 
archives available.

> Maybe I’m missing something important.

I get that feeling a lot when talking to people who really like homebrew.

-- 
Daniel J. Luke

Re: running macports along with homebrew

[Craig Treleaven]

> On Aug 31, 2017, at 9:46 AM, db  wrote:
> 
> On 31 Aug 2017, at 15:35, Craig Treleaven  wrote:
>> What is it that you want that MacPorts does not provide?
> 
> As I said in my OP, missing ports and updated versions, cask...

Gentle reminders, regularily applied, tend to cure the ‘missing ports and 
updated versions’ issue.

Homebrew Casks appear to confuse many people, me included:

https://apple.stackexchange.com/questions/125468/what-is-the-difference-between-brew-and-brew-cask

AIUI, casks are supposed to help in two ways:  binary (only) packages and 
pre-compiled binaries.

MacPorts solved the second part several years ago.  As an aside, I think a lot 
of people using Homebrew never got this message.

For Homebrew, the binary-only Cask packages seem to be aimed at things like 
Google Chrome and similar.  I understand the attraction to having a command 
line way to check for and update my major packaged applications.  But, AFAICT, 
it is never going to work for purchased applications (Carbon Copy Cloner, 
Parallels Desktop, etc).  Given that I’m going to have to keep an eye out for 
such updates, it is not solving the whole problem.  And creates an opportunity 
for malicious software to be substituted, even temporarily.

Maybe I’m missing something important.

Craig

Re: running macports along with homebrew

[db]

On 31 Aug 2017, at 17:53, Ken Cunningham  
wrote:
> I think homebrew gets attention for two reasons.
> 
> 
> 1. a one-line copy & paste install command that is pasted into the terminal  
> (macports could / should do that too, BTW).
> 
> 2. the fact that it symlinks it's stuff into /usr/local, making it easier to 
> use it's installed products for building other software for amateurs 
> (macports could do that too).
> 
> 3. My impression is that it's not so difficult to get things accepted. If a 
> submission builds on Travis on 10.10 to 10.12, it's usually in homebrew 
> within a day or so, it seems.
> 
> On the other hand:
> 
> 1. MacPorts, in general, pays more attention to the details. There is 
> significantly more OCD in the submission reviews, which is both very good and 
> sometimes deflating. But a port in macports is very trustworthy, and in the 
> end, that is the single most important thing.
> 
> 2. MacPorts has a couple of real superstars who can fix things it seems 
> nobody else can fix. So we have gcc6 working perfectly well all the way back 
> to Tiger, for example, and the latest-greatest clang / llvm features, etc.

The first three points are certainly not what appeals to me from homebrew. I do 
agree on the latter two though.

To give you a couple of examples: vagrant — there's a ticket but the dev seems 
to haven't finished it, and ipfs — I wrote the port and the ticket's now in the 
twilight zone, no feedback whatsoever (I have other portfiles that I don't even 
bother submitting). Both are in homebrew. And as I mentioned earlier, cask has 
already 3.7K binaries to manage, which is quite convenient.

I don't want to get rid of MacPorts, but complement it without breaking 
anything.

Re: running macports along with homebrew

[Ken Cunningham]

I think homebrew gets attention for two reasons.


1. a one-line copy & paste install command that is pasted into the terminal  
(macports could / should do that too, BTW).

2. the fact that it symlinks it's stuff into /usr/local, making it easier to 
use it's installed products for building other software for amateurs (macports 
could do that too).

3. My impression is that it's not so difficult to get things accepted. If a 
submission builds on Travis on 10.10 to 10.12, it's usually in homebrew within 
a day or so, it seems.

On the other hand:

1. MacPorts, in general, pays more attention to the details. There is 
significantly more OCD in the submission reviews, which is both very good and 
sometimes deflating. But a port in macports is very trustworthy, and in the 
end, that is the single most important thing.

2. MacPorts has a couple of real superstars who can fix things it seems nobody 
else can fix. So we have gcc6 working perfectly well all the way back to Tiger, 
for example, and the latest-greatest clang / llvm features, etc.


Ken

Re: running macports along with homebrew

[db]

On 31 Aug 2017, at 15:35, Craig Treleaven  wrote:
> What is it that you want that MacPorts does not provide?

As I said in my OP, missing ports and updated versions, cask...

Re: running macports along with homebrew

[Craig Treleaven]

> On Aug 31, 2017, at 9:32 AM, db  wrote:
> 
> On 30 Aug 2017, at 10:16, Richard L. Hamilton  wrote:
>> the newer, safer convention is distinct subdirectories of /opt, for each 
>> package or set of commonly managed packages; thus, MacPorts by default uses 
>> /opt/local, XQuartz uses /opt/X11 (for the stuff that's not elsewhere), etc.
> 
> Is it a tacit convention? I couldn't find a source myself.
> 
> 
> Thank you all for the useful information. It seems only Umesh is actually 
> using homebrew though.

What is it that you want that MacPorts does not provide?  

Craig

Re: running macports along with homebrew

[db]

On 30 Aug 2017, at 10:16, Richard L. Hamilton  wrote:
> the newer, safer convention is distinct subdirectories of /opt, for each 
> package or set of commonly managed packages; thus, MacPorts by default uses 
> /opt/local, XQuartz uses /opt/X11 (for the stuff that's not elsewhere), etc.

Is it a tacit convention? I couldn't find a source myself.


Thank you all for the useful information. It seems only Umesh is actually using 
homebrew though.