One bug report is probably sufficient. Thanks.
> On Sep 1, 2017, at 20:41, Horst Simon wrote:
>
> Thanks Ryan, it now downloads, but I am getting now build error with command
> execution fails, the same as with mariadb-10.0, should I open a bug report
> for both or only against mariadb-10.0
>
Thanks Ryan, it now downloads, but I am getting now build error with command
execution fails, the same as with mariadb-10.0, should I open a bug report for
both or only against mariadb-10.0
Regards,
Horst
> On 2 Sep 2017, at 9:04 am, Ryan Schmidt wrote:
>
>
> On Aug 31, 2017, at 23:57, Horst
> On Sep 1, 2017, at 03:22, db wrote:
>
> On 31 Aug 2017, at 21:34, Craig Treleaven wrote:
>> Gentle reminders, regularily applied, tend to cure the ‘missing ports and
>> updated versions’ issue.
>
> It shouldn't work like that. Actually, it didn't.
Ok. How would you like us to proceed?
On Aug 31, 2017, at 23:57, Horst Simon wrote:
> When I tried to install mariadb-10.1 I get following error, is it removed? It
> work previously.
Upstream developers must have moved or removed the file on their server. I've
added it to our mirror server. It should be available to you within a c
On 31 Aug 2017, at 21:34, Craig Treleaven wrote:
> Gentle reminders, regularily applied, tend to cure the ‘missing ports and
> updated versions’ issue.
It shouldn't work like that. Actually, it didn't.
> I understand the attraction to having a command line way to check for and
> update my majo
On 31 Aug 2017, at 21:46, Daniel J. Luke wrote:
> Indeed, a quick look at pacakges.macports.org indicates there are 22,957
> binary archives available.
As of now 19944 ports. No vagrant, no stem — yet.
