On 5/23/15 1:32 PM, David Evans wrote:
I'm not sure how long this has been going on but this buildbot is
silently failing in the compile phase with the following stdout
Warning: not using chroot
File 'portlist' not found
Usage: ./mpab [help | mount | umount | shell | buildmp [RELEASE_FILE] |
On 23.05.2015 11:56 PM, David Evans wrote:
Apparently a corrupted database issue. Output from the write portlist phase
shows
Also see thread Snow Leopard builder failing on SQLite database corruption
Mihai
signature.asc
Description: OpenPGP digital signature
On 5/23/15 3:00 PM, Mihai Moldovan wrote:
On 23.05.2015 11:56 PM, David Evans wrote:
Apparently a corrupted database issue. Output from the write portlist phase
shows
Also see thread Snow Leopard builder failing on SQLite database corruption
Mihai
Thanks, Mihai. I was out of town and
On May 23, 2015, at 5:11 PM, David Evans wrote:
On 5/23/15 3:00 PM, Mihai Moldovan wrote:
On 23.05.2015 11:56 PM, David Evans wrote:
Apparently a corrupted database issue. Output from the write portlist
phase shows
Also see thread Snow Leopard builder failing on SQLite database corruption
On May 22, 2015, at 9:46 PM, lar...@macports.org wrote:
Revision
136599
Author
lar...@macports.org
Date
2015-05-22 19:46:13 -0700 (Fri, 22 May 2015)
Log Message
libjpeg-turbo: Respect configure.build_arch
After r136597, the conditional is always false (because
Mark,
Just add their e-mail address to yours in the Portfile (separated by a space).
On May 23, 2015, at 12:13 PM, Mark Brethen mark.bret...@gmail.com wrote:
I would like to add another maintainer to the FreeCAD port that I maintain.
How do I get someone added as a maintainer for this port?
I'm not sure how long this has been going on but this buildbot is
silently failing in the compile phase with the following stdout
Warning: not using chroot
File 'portlist' not found
Usage: ./mpab [help | mount | umount | shell | buildmp [RELEASE_FILE] |
rebuildmp [RELEASE_FILE] |
Hi Ryan,
I see we currently have 3 variants of libssh: libssh (the one from
libssh.org), libssh01 (a *very*, *very*, *very* old version of the one from
libssh.org) and libssh2 (completely unrelated software from libssh2.org.)
libssh01 has no dependents. Can I deprecate it?
Mihai
On 2015-5-24 02:25 , David Evans wrote:
On 5/19/15 10:31 PM, Joshua Root wrote:
On 2015-5-20 13:24 , Joshua Root wrote:
Revision: 136259
https://trac.macports.org/changeset/136259
Author: devans at macports.org
Date: 2015-05-13 12:49:19 -0700 (Wed, 13 May 2015)
Log Message:
On May 22, 2015, at 3:57 AM, René J.V. Bertin wrote:
In that light, it might also be a good idea to follow the Debian/Ubuntu lead
on versioning, and prepend the major compatibility version to the port
version so it becomes easier to compare them. Supposing MacPorts supports a
colon in the
On 2015-5-24 00:21 , Rainer Müller wrote:
On 2015-05-22 13:31, René J.V. Bertin wrote:
Is there a reason why the parser doesn't bark when one declares a
variant with a name that starts with a +? It took me a while to find
that as the reason for a variant that seemingly didn't want to get
set
On 24.05.2015 03:23 AM, Ryan Schmidt wrote:
So yes, feel free to kill libssh01 immediately.
Without replacing it with libssh first or revbumping and erroring out in
pre-configure?
Okay.
Mihai
signature.asc
Description: OpenPGP digital signature
On May 23, 2015, at 9:57 AM, Rainer Müller rai...@macports.org wrote:
The second approach with multiple versions per port would allow to add
new versions without forcing everyone to upgrade immediately. This opens
the possibility to test new versions with a few brave testers without
the need
On 2015-05-22 15:17, René J.V. Bertin wrote:
On Friday May 22 2015 14:36:49 Rainer Müller wrote:
What if a port flagged stable depends on an unstable port?
That'd be an anomaly and in order for anything like this to function
with MacPorts, base would have to support the notion of depending
On 2015-05-22 13:31, René J.V. Bertin wrote:
Is there a reason why the parser doesn't bark when one declares a
variant with a name that starts with a +? It took me a while to find
that as the reason for a variant that seemingly didn't want to get
set while `port info` showed it as a default
On 5/19/15 10:31 PM, Joshua Root wrote:
On 2015-5-20 13:24 , Joshua Root wrote:
Revision: 136259
https://trac.macports.org/changeset/136259
Author: devans at macports.org
Date: 2015-05-13 12:49:19 -0700 (Wed, 13 May 2015)
Log Message:
---
gnome-keyring: blacklist
On Saturday May 23 2015 15:57:22 Rainer Müller wrote:
So you assume we provide multiple versions of the same port?
I know you don't, and that a port is always taken from the highest-priority
repo in sources.conf .
I also know I added the word wishful or wishfully before or after the word
I would like to add another maintainer to the FreeCAD port that I maintain. How
do I get someone added as a maintainer for this port?
Mark
___
macports-dev mailing list
macports-dev@lists.macosforge.org
On Saturday May 23 2015 16:21:27 Rainer Müller wrote:
'port lint' already reports such a variant. However, it seems reasonable
to reject such a name completely.
Exactly my point (I'd have resorted to port lint if I hadn't caught the error
in my eyelashes before, it always takes me a while to
19 matches
Mail list logo
