Hi all,
I just made an update (unrelated to fetching) to blitz-devel, a
nomaintainer port, and got this error below from each buildbot, even though
it worked fine on my machine. Anyone know what this is about?
Thanks,
David
DEBUG: Executing org.macports.fetch (blitz-devel)
DEBUG: Executing:
Hi,
On Tue, Jan 05, 2016 at 12:44:49PM -0600, Ryan Schmidt wrote:
>
> I'm not comfortable with installing unchecked files on user systems.
> The whole point of the checksum system is to verify that the files
> that are installed on user systems are the same files that were tested
> by the
On Jan 5, 2016, at 12:11 PM, David Strubbe wrote:
> I just made an update (unrelated to fetching) to blitz-devel, a nomaintainer
> port, and got this error below from each buildbot, even though it worked fine
> on my machine. Anyone know what this is about?
>
> Thanks,
> David
>
> DEBUG:
On Jan 5, 2016, at 7:32 AM, Rainer Müller wrote:
> On 2016-01-04 07:45, Mojca Miklavec wrote:
>> I agree with Ryan here. But then again the port depends on poppler
>> which would probably be built with libstdc++ by default unless the
>> whole MacPorts is configured to use libc++. I'm not sure
On Jan 5, 2016, at 5:52 AM, Carlo Tambuatco wrote:
> Will this work with perl_select…? My installation of perl_select has been a
> bit flaky.
As far as I know, MacPorts does not contain anything called "perl_select".
We have "port select", but it does not handle perl; adding this feature is
> On Jan 5, 2016, at 12:43 PM, ebori...@macports.org wrote:
>
> Revision
> 144262
> Author
> ebori...@macports.org
> Date
> 2016-01-05 10:43:29 -0800 (Tue, 05 Jan 2016)
> Log Message
>
> py-htmldocs: 34 and 35 tarballs appear to be updated nightly; skip checksums.
> (At least we don't install
On Jan 5, 2016, at 1:27 PM, Brandon Allbery wrote:
> On Tue, Jan 5, 2016 at 2:24 PM, Ryan Schmidt wrote:
>> As far as I know, MacPorts does not contain anything called "perl_select".
>
> There is, actually, but it's a stub that doesn't do anything as yet (or
> probably ever since it was
On 2016-01-02 06:43, Ryan Schmidt wrote:
> Using a Subversion working copy and "svn commit"?
For ports, I am exclusively using this approach.
> Using a Git clone and git-svn?
For base I am experimenting with git-svn, but I also keep a normal svn
working copy.
> Do you have any complaints about
On 2016-01-04 07:45, Mojca Miklavec wrote:
> I agree with Ryan here. But then again the port depends on poppler
> which would probably be built with libstdc++ by default unless the
> whole MacPorts is configured to use libc++. I'm not sure what strategy
> could be used in these cases.
I would
Hi all,
I propose to make the port pymol-devel obsolete. There is a pymol port,
which is a newer version of the same software. It is not clear what, if
any, purpose pymol-devel serves, though years ago it was a newer version
than the pymol port (no clear reason was stated at the time for why this
On 5 January 2016 at 12:52, Carlo Tambuatco wrote:
> Will this work with perl_select…?
No. Or at least not yet.
Perl 6 is not even remotely compatible with Perl 5, so there is no way
to switch between the two versions of Perl to run the same script.
In the future it might be possible to provide
11 matches
Mail list logo
