On Apr 10, 2018, at 12:44, Rainer Müller wrote:
> Building package installers is the most time-consuming operation in our
> release process. Therefore I was asking whether it is actually worth to
> wait for them to appear before releasing to selfupdate.
I am rebuilding our installer creation
On 7 April 2018 at 15:45, db wrote:
> On 7 Apr 2018, at 14:37, Ryan Schmidt wrote:
>
> Is buildbot running on your basement???
Yes (not mine).
> Streamlining this process could have been something for GSoC.
Until the autumn of 2016 we had no concept of pull requests at all and
we had nearly no
On Apr 9, 2018, at 17:15, Rainer Müller wrote:
> If nobody objects, I am going to tag a new release on Tuesday and
> prepare tarballs.
Please merge my other two commits from this ticket:
https://trac.macports.org/ticket/55492
My first commit, which you merged, was buggy and needed fixing.
>
On Apr 9, 2018, at 22:43, Eric A. Borisch wrote:
> I'd still like to see the opportunistic (via libarchive / bsdtar) compression
> (pull request #45) integrated at some point; with modern machines and their
> soldered-down storage, it's all the more useful.
Sure, but this thread is about
On Apr 10, 2018, at 12:07, Ryan Schmidt wrote:
> On Apr 9, 2018, at 17:15, Rainer Müller wrote:
>
>> If nobody objects, I am going to tag a new release on Tuesday and
>> prepare tarballs.
>
> Please merge my other two commits from this ticket:
>
> https://trac.macports.org/ticket/55492
>
>
On 2018-04-10 19:07, Ryan Schmidt wrote:
>
> On Apr 9, 2018, at 17:15, Rainer Müller wrote:
>
>> If nobody objects, I am going to tag a new release on Tuesday and
>> prepare tarballs.
>
> Please merge my other two commits from this ticket:
>
> https://trac.macports.org/ticket/55492
>
> My
I am not comfortable releasing a version of MacPorts that includes a MacPorts
gcc in the default compiler list (which 2.4.3 now does) without having answered
the new-vs-old ABI question satisfactorily. I believe releasing that will lead
to the libstdc++ mismatch crashes that were the reason why
On 2018-04-10 19:39, Ryan Schmidt wrote:
>
> On Apr 10, 2018, at 12:07, Ryan Schmidt wrote:
>
>> On Apr 9, 2018, at 17:15, Rainer Müller wrote:
>>
>>> If nobody objects, I am going to tag a new release on Tuesday and
>>> prepare tarballs.
>>
>> Please merge my other two commits from this ticket:
On Apr 10, 2018, at 13:55, Ken Cunningham wrote:
> On 2018-04-10, at 11:47 AM, Rainer Müller wrote:
>>>
>>> I don't want to release 2.4.3 with the libstdc++ ABI issue unanswered. I
>>> believe it will cause problems.
>>
>> Then we should revert this change for 2.4.3 and we have one more
On Apr 10, 2018, at 12:54, Rainer Müller wrote:
>
> On 2018-04-10 19:39, Ryan Schmidt wrote:
>>
>> On Apr 10, 2018, at 12:07, Ryan Schmidt wrote:
>>
>>> On Apr 9, 2018, at 17:15, Rainer Müller wrote:
>>>
If nobody objects, I am going to tag a new release on Tuesday and
prepare
On Apr 10, 2018, at 13:47, Rainer Müller wrote:
> On 2018-04-10 20:26, Ryan Schmidt wrote:
>>
>> On Apr 10, 2018, at 12:54, Rainer Müller wrote:
>>>
>>> At some point we should make a cut and not add many changes in the last
>>> minute...
>>
>> Well I can't force you to merge them.
>
> I
On 2018-04-10, at 12:02 PM, Ryan Schmidt wrote:
>
> On Apr 10, 2018, at 13:55, Ken Cunningham wrote:
> Mixing libc++ and libstdc++ results in a link failure. Mixing old libstdc++
> and new libstdc++ did not previously result in a link failure; it resulted in
> a runtime crash which was
On 2018-04-10 21:06, Ryan Schmidt wrote:
> I'm not going to merge them, because I don't know how, and don't have the
> energy to attempt to learn how to do so, given the zillion other things I'm
> trying to do right now.
This is even documented:
On 2018-04-10 19:39, Ryan Schmidt wrote:
> Do you want to merge this performance enhancement too:
[...]
> And these bugfixes:
I assigned this to the MacPorts 2.4.4 milestone, so we do not forget
about them:
https://trac.macports.org/ticket/56267
Rainer
On 2018-04-10 20:26, Ryan Schmidt wrote:
>
> On Apr 10, 2018, at 12:54, Rainer Müller wrote:
>>
>> At some point we should make a cut and not add many changes in the last
>> minute...
>
> Well I can't force you to merge them.
I cannot stop you either... I am just afraid that by merging changes
Hi,
I though it would be about time to add 35 and 36 to all python submodules.
https://github.com/macports/macports-ports/pull/1561
I kept in mind that some might not work immediately, but I forgot that
some are simply not designed to be used with python 3.6, like many
modules for backporting
Hi,
Recently I took upon a journey to try to update ports
which are tagged as 'nomaintainer' and noticed that
some of the ports give out false positives during livecheck.
This is due to the reason that upstream decided to tag a
newer version without actually updating the code / tarball.
Also the
17 matches
Mail list logo
