Re: [MacPorts] #58848: Error: Failed to build rust: command execution failed

On Aug 18, 2019, at 03:56, Dmitri Zaitsev wrote: > 3. What kind of build error is that and how to deal with it? Rust does not build on an OS X version as old as you are using. Software developers frequently remove support for older operating systems from their projects, on the assumption

Re: Outage of braeburn.macports.org

Hi, On Sun, Aug 18, 2019 at 02:03:16PM +, Zero King wrote: > On Sun, Aug 18, 2019 at 01:58:36PM +, Zero King wrote: > > The prbot.service is down. Please try to start it. I restarted the service. -- Clemens

Re: pull request labels not being set

There was server outage. Mojca V ned., 18. avg. 2019 15:40 je oseba Christopher Jones < jon...@hep.phy.cam.ac.uk> napisala: > Hi All, > > Anyone know why GitHub no longer seems to be automatically setting labels > on new pull requests ? > > https://github.com/macports/macports-ports/pulls > >

Re: Outage of braeburn.macports.org

CC mailing lists. On Sun, Aug 18, 2019 at 01:58:36PM +, Zero King wrote: Hi Rainer, On Sat, Aug 17, 2019 at 11:45:06AM +0200, Rainer Müller wrote: Hello, according to monitoring, braeburn went down at 2019-08-17 06:10 UTC for an unknown reason. When I noticed the downtime, I was unable

pull request labels not being set

Hi All, Anyone know why GitHub no longer seems to be automatically setting labels on new pull requests ? https://github.com/macports/macports-ports/pulls ? Chris smime.p7s Description: S/MIME cryptographic signature

Re: [MacPorts] #58848: Error: Failed to build rust: command execution failed

Hi, > What I find puzzling: > > 1. As I did not change anything on my system, why did all the files download > correctly this time but not the last time? Any number of possible reasons. Transient network issues to some mirrors for instance. The mirrors used for downloads are not the same each

Re: "make[1]: execvp: printf: Argument list too long"

René J.V. Bertin wrote: > There's no `string hash` function as far as I've seen. There's this, but that doesn't really shorten the paths by all that much (just not even a factor 2): {{{ package require md5 ui_msg "${portpath}:\n[md5::md5 -hex ${portpath}]" }}}

Re: [MacPorts] #58848: Error: Failed to build rust: command execution failed

First of all, I appreciate any advice and apologies for any misunderstanding, I am still very new to MacPorts (after giving up on HB). I have now ran all of these: {{{ sudo port clean rust sudo port selfupdate sudo port upgrade outdated sudo port reclaim }}} The reclaim command suggested to

"make[1]: execvp: printf: Argument list too long"

Hi, I ran into another issue with the potentially inordinately long `portbuildpath` names, and started thinking of ways to avoid hitting a hard limit on the argument length list, using a unique shortened version of `portpath`: 1) if the traditional `portbuildpath` already exists, use that 2)