On 12 April 2018 at 04:23, Ryan Schmidt wrote:
> On Apr 11, 2018, at 21:22, Joshua Root wrote:
>> On 2018-4-12 11:49 , Ryan Schmidt wrote:
>>>
>>> These performance problems predate the existence of our
>>> getNextBuildOnPortBuilder function.
>>>
>>> It smells to me like a missing database index p
> On 12 Apr 2018, at 02:30, Ryan Schmidt wrote:
>
>
> On Apr 11, 2018, at 08:48, Enrico Maria Crisostomo wrote:
>
>> Well, I replicated it:
>>
>> * Clean the repo (e.g.: git clean -xfd)
>> * git checkout v2.4.2
>> * build and install 2.4.2:
>>
>> $ export PATH=/bin:/sbin:/usr/bin:/usr/s
Hi,
There are still some python modules that provide support for python
2.6 and 3.3. Is it ok to put all of them to py-graveyard?
There are a number of broken py34-* ports due to missing dependencies
(notably py34-matplotlib).
Do we want to:
(a) Temporarily add those missing dependencies until t
On 11 Apr 2018, at 19:24, Perry E. Metzger wrote:
> The main steps are:
> […]
> [By the way, if someone wants to turn this email into a document, I
> was pretty careful writing what's above so that would be easy.]
Thanks for the write-up. Although I probably rather prefer the PR way, it's
gettin
On 8 Apr 2018, at 02:04, Rainer Müller wrote:
> So here is the full plan in detail:
Side note: Wouldn't it be feasible to adjust portfiles based on CI's feedback?
Let's say, you have something build on 10.6-10.13, but for whatever reason it
fails on 10.9, so that could be reflected in the portf
On 12 April 2018 at 13:59, db wrote:
> On 11 Apr 2018, at 19:24, Perry E. Metzger wrote:
>> The main steps are:
>> […]
>> [By the way, if someone wants to turn this email into a document, I
>> was pretty careful writing what's above so that would be easy.]
>
> Thanks for the write-up. Although I pr
On 12 April 2018 at 13:59, db wrote:
>
> Side note: Wouldn't it be feasible to adjust portfiles based on CI's
> feedback? Let's say, you have something build on 10.6-10.13, but for whatever
> reason it fails on 10.9, so that could be reflected in the portfile in order
> to avoid having users bui
On Wed, 11 Apr 2018 19:30:56 -0400 Andrew Moore
wrote:
> As someone who only reads the manual as last resort, I think
> Section 7 of the MacPorts Guide could be retitled from “MacPorts
> Project” to “Contributing to MacPorts”. And then steps for
> creating pull requests via GitHub spelled out tut
On Thu, 12 Apr 2018 11:59:17 +0200 Mojca Miklavec
wrote:
> Hi,
>
> There are still some python modules that provide support for python
> 2.6 and 3.3. Is it ok to put all of them to py-graveyard?
As a data point, Python 2.6 and Python 3.3 are both past End of
Life and are no longer supported by t
On Apr 12, 2018, at 03:39, Enrico Maria Crisostomo wrote:
> On 12 Apr 2018, at 02:30, Ryan Schmidt wrote:
>
>> On Apr 11, 2018, at 08:48, Enrico Maria Crisostomo wrote:
>>
>>> Well, I replicated it:
>>>
>>> * Clean the repo (e.g.: git clean -xfd)
>>> * git checkout v2.4.2
>>> * build and insta
On Apr 12, 2018, at 06:59, db wrote:
> On 8 Apr 2018, at 02:04, Rainer Müller wrote:
>> So here is the full plan in detail:
>
> Side note: Wouldn't it be feasible to adjust portfiles based on CI's
> feedback? Let's say, you have something build on 10.6-10.13, but for whatever
> reason it fails
On 12 Apr 2018, at 14:27, Mojca Miklavec wrote:
> What nobody mentioned so far is that one can also simply click "Edit" on the
> existing Portfile on GitHub interface and that will also open a pull request.
Interesting. It seems that 'Create new file' would have a similar effect.
'Upload files'
> On Apr 12, 2018, at 1:35 PM, db wrote:
>
> On 12 Apr 2018, at 14:27, Mojca Miklavec wrote:
>> What nobody mentioned so far is that one can also simply click "Edit" on the
>> existing Portfile on GitHub interface and that will also open a pull request.
>
> Interesting. It seems that 'Create n
On 12 Apr 2018, at 18:52, Ryan Schmidt wrote:
> 1. MacPorts does not have a method of declaring that a port does not build on
> a version of macOS. Such a feature is being discussed:
> https://trac.macports.org/ticket/15712
> In the absence of this feature, we write pre-fetch blocks that manually
On Apr 12, 2018, at 13:14, db wrote:
> On 12 Apr 2018, at 18:52, Ryan Schmidt wrote:
>> 1. MacPorts does not have a method of declaring that a port does not build
>> on a version of macOS. Such a feature is being discussed:
>> https://trac.macports.org/ticket/15712
>> In the absence of this feat
On Apr 12, 2018, at 02:53, Mojca Miklavec wrote:
> On 12 April 2018 at 04:23, Ryan Schmidt wrote:
>> On Apr 11, 2018, at 21:22, Joshua Root wrote:
>>> On 2018-4-12 11:49 , Ryan Schmidt wrote:
These performance problems predate the existence of our
getNextBuildOnPortBuilder functi
On 12 Apr 2018, at 19:52, Craig Treleaven wrote:
> Is there a playground somewhere to try out such features? For those of us
> that are somewhat git- and github-challenged.
Not that I'm aware of. Just fork some repo or create a new one and make it your
playground.
On 12 Apr 2018, at 20:16, Ryan Schmidt wrote:
> You may have noticed that discussion about the issue resumed 4 weeks ago, and
> a milestone was assigned.
I didn't notice the milestone. Is 2.6 next year's?
On Apr 12, 2018, at 13:38, db wrote:
> On 12 Apr 2018, at 20:16, Ryan Schmidt wrote:
>> You may have noticed that discussion about the issue resumed 4 weeks ago,
>> and a milestone was assigned.
>
> I didn't notice the milestone. Is 2.6 next year's?
Milestones don't have specific dates. We wan
On Apr 12, 2018, at 13:35, Jackson Isaac wrote:
> Jackson Isaac (JacksonIsaac) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/5ed97fc2b4fe6ecb8953371fdeefa3bc8da73ea9
>
> The following commit(s) were added to refs/heads/
On 2018-04-12 20:14, db wrote:
> On 12 Apr 2018, at 18:52, Ryan Schmidt wrote:
>> 1. MacPorts does not have a method of declaring that a port does not build
>> on a version of macOS. Such a feature is being discussed:
>> https://trac.macports.org/ticket/15712
>> In the absence of this feature, we
> On Apr 12, 2018, at 5:09 PM, MacPorts wrote:
>
> #15712: Add versions to platforms
> --+
> Reporter: raimue | Owner: larryv
> Type: enhancement | Status: assigned
> Priority: Normal | Milestone: MacPorts 2.6
This issue might also be impacting the High Sierra macports 2.4.3 installer
image as well. After installing it on a machine with no /opt/local, I get
the following from 'sudo port self update'...
---> Updating MacPorts base sources using rsync
MacPorts base version 2.4.3 installed,
MacPorts bas
On Apr 12, 2018, at 17:42, Jack Howarth wrote:
> This issue
"This issue" isn't an issue, it's just a misunderstanding of how the shell
caches information.
> might also be impacting the High Sierra macports 2.4.3 installer image as
> well. After installing it on a machine with no /opt/local, I
On 2018-04-13 00:42, Jack Howarth wrote:
> This issue might also be impacting the High Sierra macports 2.4.3
> installer image as well. After installing it on a machine with no
> /opt/local, I get the following from 'sudo port self update'...
>
> ---> Updating MacPorts base sources using rsync
>
On Thu, Apr 12, 2018 at 6:47 PM, Rainer Müller wrote:
> On 2018-04-13 00:42, Jack Howarth wrote:
> > This issue might also be impacting the High Sierra macports 2.4.3
> > installer image as well. After installing it on a machine with no
> > /opt/local, I get the following from 'sudo port self upd
On Apr 12, 2018, at 17:54, Jack Howarth wrote:
> On Thu, Apr 12, 2018 at 6:47 PM, Rainer Müller wrote:
>> It is actually an unrelated problem. The new version is not yet
>> available over selfupdate. The script that is supposed to update the
>> rsync server is failing.
>>
>> Check this and follo
Joshua Root wrote:
> On 2018-4-6 06:15 , Bjarne D Mathiesen wrote:
>> 2) filing a bug
>
> Yes. Against py-nuitka in our trac, and probably against setuptools
> upstream.
https://trac.macports.org/ticket/56279
--
Bjarne D Mathiesen
Korsør ; Danmark ; Europa
--
https://github.com/macports/macports-base/pull/76
During the extract-from-package step, if bsdtar exists **and** supports
--hfsCompression, use the flag during the extraction.
To test:
* make sure libarchive is installed
* check disk usage
* deactivate & re-activate a large port (llvm / gcc /
On Apr 12, 2018, at 18:02, Jack Howarth wrote:
> Okay. I was confused as to whether the installer contained the complete ports
> repo or if it had to download that from the servers. I'm used to fink where
> the installer only provides a core set of the base package files and the rest
> have to
Is anyone on 10.13 able to start polari such that a window appears? It
seems to cause the xors-server app to launch but only produces the
following output in the terminal without opening the Polari window...
$ polari
(.:18119): Gjs-*WARNING* **: 20:07:49.426: Some code accessed the property
'Dro
On Apr 12, 2018, at 04:59, Mojca Miklavec wrote:
> There are still some python modules that provide support for python
> 2.6 and 3.3. Is it ok to put all of them to py-graveyard?
>
> There are a number of broken py34-* ports due to missing dependencies
> (notably py34-matplotlib).
>
> Do we wan
> On Apr 12, 2018, at 8:42 PM, Ryan Schmidt wrote:
>
>
> On Apr 12, 2018, at 04:59, Mojca Miklavec wrote:
>
>> There are still some python modules that provide support for python
>> 2.6 and 3.3. Is it ok to put all of them to py-graveyard?
>>
>> There are a number of broken py34-* ports due to
33 matches
Mail list logo
