Re: GSOC

(Resending the email since I initially posted from the wrong email address) Dear Abhishek, On 26 March 2018 at 08:00, Abhishek Kashyap wrote: > Yes,I can totally ageee with you.But i focus more attention towards the goal > of the project almost from GSOC period.I am not doing for money instead i

Re: Gsoc 18 Project | Collect build statistics

Dear Vishnu, First some general remarks, then the answers to your questions below. - One of the most important things that we should discuss and improve is the timeline. This is very little work, but it requires some coordination to make sure that they are defined in the most sensible way. One op

Re: Gsoc 18 Project | Collect build statistics

On 26 March 2018 at 11:54, Vishnu wrote: > Also i wanted to know.Like if a new port is created .Buildbot is > compulsorily run right? > and if it is deleted.There is no need for buildbot to run.So buildbot wont > send updates to the log that port has been deleted. I was already thinking about that

Re: Gsoc 18 Project | Collect build statistics

On 26 March 2018 at 14:47, Vishnu wrote: > Ok . > I will be writing Milestones seperately very soon. > What is your irc id? and on what channel are you available.i use freenode. You can join #macports > Also rather than irc could we use comments in docs.google to interact.And > simultaneously you

Re: Blacklisting gcc

On 27 March 2018 at 08:31, Ryan Schmidt wrote: > > > On Mar 26, 2018, at 01:25, Mojca Miklavec wrote: > >> On 26 March 2018 at 02:49, Ryan Schmidt wrote: > >>> On Mar 25, 2018, at 14:37, David B. Evans wrote: > >>> > >>>> +# blacklist c

Mirror size & completeness of binaries

Hi, I don't know about the best way to do it, but I would like to suggest to provide macports mirorring in two different sizes: a small one and a complete one. While I'm a heavy supporter of providing support for legacy systems, I see no reason to mirror files for them on all of our mirrors and c

Re: Mirror size & completeness of binaries

On 28 March 2018 at 13:58, Rainer Müller wrote: > On 2018-03-27 13:56, Mojca Miklavec wrote: >> I don't know about the best way to do it, but I would like to suggest to >> provide macports mirorring in two different sizes: a small one and a >> complete one. >> &

Re: Mirror size & completeness of binaries

On 29 March 2018 at 16:19, Ryan Schmidt wrote: > On Mar 27, 2018, at 06:56, Mojca Miklavec wrote: > >> I don't know about the best way to do it, but I would like to suggest to >> provide macports mirorring in two different sizes: a small one and a >> complete

Re: Mirror size & completeness of binaries

On 29 March 2018 at 18:21, Rainer Müller wrote: > On 2018-03-29 16:19, Ryan Schmidt wrote: >> At the same time, we need to consider how MacPorts base will respond to the >> situation. Currently, it assumes all packages are available on all mirrors. >> Therefore, it tries to find a package on thre

Re: Port trees for specific versions of MacOS

Dear Ken, On 28 March 2018 at 18:01, Ken Cunningham wrote: > In Rene mentions the idea > of generating port tree overlays for specific versions of MacOS, to preserve > compatible versions of ports which have moved beyond the capabilities of tha

Re: Compiling against libc++ on 10.6 and using the binary on 10.7

On 24 March 2018 at 12:40, Ryan Schmidt wrote: > On Mar 24, 2018, at 01:33, Mojca Miklavec wrote: >> On 24 March 2018 at 02:57, Ryan Schmidt wrote: >>> On Mar 23, 2018, at 05:35, Mojca Miklavec wrote: >>> >>>> I'm compiling some command-line tools and

Re: Port trees for specific versions of MacOS

On 31 March 2018 at 19:31, Ken Cunningham wrote: > > For example, cmake pegged @ 3.9 will work for many years on Tiger to build > any software that needs cmake, and at present, you can get nothing usable > from the main MacPorts repo. CMake is in fact one exception where I would be in favour of

Re: app PortGroup enhancements, and request for someone to test with +quartz variant for a few gtk apps

On 30 March 2018 at 20:17, Kenneth F. Cunningham wrote: > On 2018-03-22, at 8:24 AM, Kenneth F. Cunningham wrote: > >> 2. an option to hide the sometimes forever bouncing dock icon >> >> options app.hide_dock_icon >> default app.hide_dock_icon no >> >> For the +x11 versions, you would want both of

Re: Python ports: should we use wheel files?

On 31 March 2018 at 12:11, Enrico Maria Crisostomo wrote: > Hi all, > > While updating the py-tensorflow port to 1.6.0 I started to think about this > question: we shortly discussed about it on the corresponding PR > (https://github.com/macports/macports-ports/pull/1499) and decided to bring > i

Re: Gsoc 18 Project | Collect build statistics

On 2 April 2018 at 18:50, Vishnu wrote: > Hi > > Here is the basic structure i prepared. > > https://jsfiddle.net/3r4vL4L3/5/ > > And i wanted to know what all am i supposed to show in installation > statistics mandatorily? > > Top port Versions of a month? > Top os of that port? > Number of instal

Re: CI system for PR builds

I fail to find any info about available runners for hosted CI infrastructure. Mojca V pon., 2. apr. 2018 20:43 je oseba db napisala: > GitLab 10.6 released with CI/CD for GitHub > > > https://about.gitlab.com/2018/03/22/gitlab-10-6-released/#open-source-projects

Re: Gsoc 18 Project | Collect build statistics

V pon., 2. apr. 2018 19:49 je oseba Vishnu napisala: > In the database. > Because then it would be very easy to count the number of os for that port. > I'll explain tomorrow why this is suboptimal. (But there's no need to further optimise the database design right now.) Just plan the final resul

Re: CI system for PR builds

On 3 April 2018 at 13:09, Rainer Müller wrote: > On 2018-04-03 12:31, db wrote: >> On 3 Apr 2018, at 02:20, Rainer Müller wrote: >>> Then please explain what this would offer us at all? >> >> I'll try. GitLab let's you have external runners >> (https://docs.gitlab.com/ee/ci/runners/README.html), w

Re: Gsoc 18 Project | Collect build statistics

t there's no point in asking you to spend a week making this document ten times longer and fixing tiny unimportant details that don't really demonstrate the skillset :) On 2 April 2018 at 23:32, Mojca Miklavec wrote: > V pon., 2. apr. 2018 19:49 je oseba Vishnu napisala: >> >&g

Re: Gsoc 18 Project | Collect build statistics

Dear Vishnu, On 3 April 2018 at 16:56, Vishnu wrote: > Regarding mini django project. What would you suggest i do? > > I was thinking on code to populate the port table from portindex.json > > Would that act as a sample for my Coding skill? > Or should i do something else? That sounds ok and is i

Re: CI system for PR builds

On 3 April 2018 at 14:43, db wrote: > On 3 Apr 2018, at 13:09, Rainer Müller wrote: >> But what exactly do you think would be the benefit from such a complicated >> setup (GitHub -> GitLab -> External Runner)? > > Testing? But hey, I only know MP's infrastructure from what I read in the > list,

Re: jmol haspatch maintainer - please commit #56106

Dear Peter, On 3 April 2018 at 18:23, Peter Brommer wrote: > Hi, > > I recently submitted a patch for jmol (as maintainer). Could somebody with > commit privileges please take a look at > https://trac.macports.org/ticket/56106 before it becomes outdated again… Just a suggestion (without taking

Re: Gsoc 18 Project | Collect build statistics

Dear Vishnu, On 3 April 2018 at 20:10, Vishnu wrote: > > Hello > > Yes portindex.json is very useful. > > I tried my hands with python and sql. > And am successfully able to parse the json and store the data into the table . Thank you very much. The initial steps look promising. Now, try to inte

Re: port policy questions for munin

On 4 April 2018 at 02:23, Rainer Müller wrote: > On 2018-04-04 01:38, macpo...@parvis.nl wrote: >> Questions about policy: >> - how to submit Portfile (unified diff against the previous version?) > > If your new Portfile is significantly different from the previous > version, a unified diff would n

Re: Gsoc 18 Project | Collect build statistics

will explain : >>>> >>>> >>>> >>>> Databse : >>>> >>>> >>>> >>>> Is my progress fine? >>>> >>>> I think this would be enough as my proof of skill. >>>> >&g

Re: Port and patch submissions via ticket vs. via PR.

On 4 April 2018 at 13:15, Ryan Schmidt wrote: > On Apr 1, 2018, at 11:02, Perry E. Metzger wrote: > >> As some of you have noticed, I've been trying to keep the PR queue >> relatively clear. > > Thanks very much for that! Indeed. What you are doing is simply amazing. >> Also, Mojca brought the qu

Re: Build Failure on ports-10.6_x86_64_legacy: libpsl, mosquitto

On 4 April 2018 at 17:19, Rainer Müller wrote: > On 2018-04-04 16:36, Andrew Moore wrote: >> If I’m reading correctly the attached report from buildbot >> port net/mosquitto fails for OS X <= >> 10.6 due to indirect dependency: libpsl. If so, this is presumably a >> known issue, since many ports d

Re: Port and patch submissions via ticket vs. via PR.

(I noticed that my previous email was flying to some strange address. I'm sorry if this is the second post, I cannot see the other one in mail archive, so I'm not sure if it went through.) On 4 April 2018 at 16:28, Jonathan Stickel wrote: > > Some instructions about > recommended procedures for pu

Re: Build Failure on ports-10.6_x86_64_legacy: libpsl, mosquitto

On 5 April 2018 at 04:25, Andrew Moore wrote: > > Not being familiar with buildbot, I’m curious if there’s an easy way to > confirm a successful build? If I go to, for instance, > https://build.macports.org/console, the format looks promising, but the > content is limited. Google doesn’t seem

Re: Mirror size & completeness of binaries

On 2 April 2018 at 17:15, Ryan Schmidt wrote: > On Apr 2, 2018, at 08:11, Arno Hautala wrote: >> On Fri, Mar 30, 2018 at 5:20 PM, Rainer Müller wrote: >>> >>> For example, in a future archive_sites.conf: >>> >>> name macports >>> platform darwin 18 >>> urls https://packages.macports.o

Re: Gsoc 18 Project | Collect build statistics

Dear Vishnu, To address some of your earlier non-technical questions with respect to GSOC, here's what our admin wrote: As per GSOC policy, we cannot comment on selection process before April 23rd. We are evaluating all the proposals and might ask some clarifications if required. There are no set

Re: CI system for PR builds

On 3 April 2018 at 19:26, Rainer Müller wrote: > On 2018-04-03 13:37, Mojca Miklavec wrote: >>> We can already trigger our Buildbot directly from GitHub and could spawn >>> a VM from a snapshot using libvirt. >> >> My (potentially wrong) impression was that libvi

Re: CI system for PR builds

On 3 April 2018 at 21:45, db wrote: > On 3 Apr 2018, at 18:04, Mojca Miklavec wrote: >> Travis has lots of limitations, but it offers both (a) and (b) for free. > > Couldn't (b) be the current infrastructure? No, because that would make the infrastructure that distributes

Online MacPorts Meeting on 21st April at 13:00 UTC

Hi, I would like to announce the first online MacPorts meeting happening two weeks from now, on April 21st at 13:00 - 14:00 UTC (if it takes much longer than one hour, we are probably doing something wrong). Many people wanted to join us at the face-to-face meeting last month, but could not make

Re: Releasing 2.4.3

On 10 April 2018 at 00:15, Rainer Müller wrote: > > If nobody objects, I am going to tag a new release on Tuesday and > prepare tarballs. In case you didn't do the tagging yet, I would suggest cherry-picking also the commit which adds "size ..." to checksums. While this is not strictly a bugfix, i

Re: CI system for PR builds

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 i

"Accidentally" added 35 and 36 subports to "backport" python modules

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 fu

Re: CI system for PR builds

On 11 April 2018 at 15:47, G A wrote: > Can these 400 new or pending ports on Trac be rolled over into the repo as > PRs? Yes, that would be ideal, and any help doing that would be greatly appreciated. It would probably make sense to make a mass-edit on Trac to invite authors to submit PRs, but b

Re: CI system for PR builds

On 11 April 2018 at 16:18, Joshua Root wrote: > > Certainly let's encourage contributors who have something to submit to > use PRs. But I don't know that simply moving existing tickets over to > PRs without the involvement of the original contributor will be useful. In any case I don't think that

Re: Gsoc

Dear Abhishek, On 11 April 2018 at 19:06, Abhishek Kashyap wrote: > On Tue, 10 Apr 2018 at 3:56 PM, Abhishek Kashyap wrote: >> >> Is there any notification about my proposals.Whats going on. >> I am enclosing my proposals with this mail. > > What happened there is no reply from anyone.Please reply

Re: New guide section on Git and GitHub

On 12 April 2018 at 04:39, Mark Anderson wrote: > Have we thought about moving entirely to github. Using issues and projects? > I remember there being a reason we didn't, but I don't remember what it was. Yes, we did. Ryan even had all trac tickets imported into GitHub and some redirection from ol

Re: [macports-ports] branch master updated: py-*: add missing subports for python 3.5 and 3.6

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

Support for python 2.6, 3.3 and 3.4

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

Re: How to submit changes with a GitHub Pull Request (was Re: CI system for PR builds)

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

Re: CI system for PR builds

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

Re: Online MacPorts Meeting on 21st April at 13:00 UTC - suggestion

On 11 April 2018 at 17:47, Perry E. Metzger wrote: > On Sun, 8 Apr 2018 19:42:24 +0200 Rainer Müller > wrote: >> However, meetings on IRC are slow, as you have to wait for others to >> type, you have no notifications whether others still have something >> to say, etc. >> >> For such a scheduled m

Re: Is it possible to specify variant as part of depends_lib?

On 19 April 2018 at 10:24, Chris Jones wrote: > On 18/04/18 18:39, Edward Maros wrote: >> >> I have a package (gds) that has a build requirement on port root5 with >> the variant +python27. >> >> Currently the buildbot system will not build the gds package because it >> installs the root5 package

Re: Online MacPorts Meeting on 21st April at 13:00 UTC

Hi, Quick reminder, the meeting starts in 10 minutes: https://trac.macports.org/wiki/Meetings/2018-04-21 Mojca On 7 April 2018 at 10:31, Mojca Miklavec wrote: > Hi, > > I would like to announce the first online MacPorts meeting happening > two weeks from now, on April 21st at 1

Wrong time on Travis with macOS 10.13?

Hi, In one of my PRs all the builds fail (only on xcode9.3) due to time synchronisation issues: Portfile is from the future - check date and time of your system https://travis-ci.org/macports/macports-ports/builds/369674495 Does anyone know how to check if this is indeed the case and report it

Migrating the guide to AsciiDoc

Hi, As requested during yesterday's meeting, here's the result of automatic conversion of our guide from xml (docbook) to asciidoc: https://github.com/macports/macports-guide/tree/master/guide/adoc This was initially explored by Aljaž and gives quite nice results out-of-the-box, but there ar

Re: Online MacPorts Meeting on 21st April at 13:00 UTC

On 21 April 2018 at 17:34, Rainer Müller wrote: > On 2018-04-07 10:31, Mojca Miklavec wrote: >> I would like to announce the first online MacPorts meeting happening >> two weeks from now, on April 21st at 13:00 - 14:00 UTC (if it takes >> much longer than one hour, we are pro

Re: Migrating the guide to AsciiDoc

On 23 April 2018 at 09:42, Jan Stary wrote: > On Apr 22 09:29:53, mo...@macports.org wrote: >> As requested during yesterday's meeting, here's the result of >> automatic conversion of our guide from xml (docbook) to asciidoc: >> >> https://github.com/macports/macports-guide/tree/master/guide/a

Re: GSOC

On 23 April 2018 at 19:23, Abhishek Kashyap wrote: > Why my proposals was rejected.What is the reason behind it? > I have tried my best.I have given my precious time to create my > proposals.Reply soon as possible. Dear Abhishek, I hope we'll have an opportunity to send a longer response, but in

Re: Gsoc 18 Project | Collect build statistics

Dear Vishnu, Let me congratulate you for being accepted to the GSOC program with MacPorts. Since your project is of vital importance for MacPorts, we will require pretty high coding standards, including good documentation and test cases, and strive towards early deployment, leaving sufficient roo

Re: Gsoc 18 Project | Collect build statistics

Dear Vishnu, I have a bunch of suggestions written below. Community bonding should usually be used to getting familiar with our codebase, our tools, our communication channels, getting to know people, ... Since you are creating a standalone product, this community bonding could be slightly differ

Re: Installing nokogiri with --use-system-libraries (was: Re: Migrating the guide to AsciiDoc)

Hi, On 23 April 2018 at 17:42, Rainer Müller wrote: > > Ruby and gems are really strange... > > Apparently, installing nokogiri with bundle fails Wasn't it you who said that we don't need a port for it as it's just a one-time conversion? :) (I'm honestly not sure who said that.) Looking at how e

Re: Gsoc 18 Project | Collect build statistics

Dear Vishnu, On 24 April 2018 at 00:45, Vishnu wrote: > >> (c.3) Plan the API to get the data from the database in JSON format >> (so that someone else could write an independent app with the same >> display functionality). >> More in a separate email, I guess. > > (c.3) You are talking about Buil

Re: Gsoc 18 Project | Collect build statistics

See last email from Ryan. Can you try to clone macports-ports and run portindex there? (Sorry, typing on my phone.) You can also go to our IRC channel for more real-time help. Mojca V tor., 24. apr. 2018 23:37 je oseba Vishnu napisala: > Hi all > > was succesfully able to install macports using

Re: Gsoc 18 Project | Collect build statistics

On 25 April 2018 at 14:45, Vishnu wrote: > Hello > > Succesfully ran the portindex2json. > and saved it ino a json. > > So what next? Wonderful, that's very good news, that will make it much easier to proceed with the rest of the tasks. Now: - play a bit with "port search python", "port info pyth

Re: Agility

Hi, I just want to say that I find it magnificent what you achieved with PRs. At the moment there is no single PR older than 4 days and if I ignore the "add GitHub handle" ones, there are only 9 PRs left (older than one hour). Yes, sure, mistakes happen all the time, but they happened just as we

Some minor issues on Linux (was: Gsoc 18 Project | Collect build statistics)

On 25 April 2018 at 17:54, Joshua Root wrote: > On 2018-4-26 01:39 , Vishnu wrote: >> Hi >> >> I think its best if you can create a repository under Macports. >> I'll be coding there. >> >> Also while trying to install mpstats . >> I am getting these error >> >> Warning: configured user/group macpo

Re: Agility

On 25 April 2018 at 18:23, Chris Jones wrote: > >> I have one request though. You are sometimes asking people to close >> the PRs because you don't want unfinished PRs in the queue. I would >> like to suggest adding a special label to such PRs before closing >> them, saying something like "workneed

Re: What "openmaintainer" means

Hi, I've been wanting to ask for a long time already: wouldn't it be about time to start switching to an explicit "closed maintainer" policy instead? That is: having to explicitly declare ports to be under a closed maintainer policy, while keeping openmaintainer as default otherwise. Of course th

Re: Gsoc 18 Project | Collect build statistics

Dear Vishnu, On 26 April 2018 at 06:44, Jackson Isaac wrote: > On Thu, Apr 26, 2018 at 3:42 AM, Vishnu wrote: >> Finally was able to install it. >> And successfully run mpstats. > > Great to hear that! You are making a good progress. Keep it up. > >> root@vishnupc:~# /opt/local/bin/port content m

Re: Binary packages not rebuilding against updated libraries

On 26 April 2018 at 00:34, Ryan Schmidt wrote: > On Apr 25, 2018, at 17:14, Jan Stary wrote: >> >> Keep a record of what depends on what (as packaging managers do). >> If A depends on B, and B has been rebuilt, reduild A too. >> No "revision bump"; port A as such has not changed. > > MacPorts does

Re: Agility

On 26 April 2018 at 08:21, Jan Stary wrote: > > What are the top three Trac features > that Github issues don't have? This is my personal list, others might have something different on their priority list: 1.) Add labels for ports. This is a feature that GitHub issues have in principle, but we co

Re: Python port best-practice?

On 26 April 2018 at 18:07, Renee Otten wrote: > > Wouldn’t it make sense to have a policy so that Python ports (if working > correctly) have the same subports - that would avoid breaking one port when > (subjectively?) removing a subport from another. Just quickly looking at the > current subpor

Strange behaviour of trace mode in MacPorts 2.4.3 / 10.13

Hi, This looks pretty strange to me: ---> Fetching distfiles for pymol Executing: cd "/path/to/pymol/work" && /usr/bin/svn --non-interactive --trust-server-cert export http://svn.code.sf.net/p/pymol/code/trunk/pymol@4187 2>&1 dyld: warning: could not load inserted library '/opt/local/libexec/ma

Re: Gsoc 18 Project | Collect build statistics

On 29 April 2018 at 08:29, Jackson Isaac wrote: > On Sun, Apr 29, 2018 at 7:36 AM, Vishnu wrote: >> Hey >> >> Thanks a lot. >> Now it works. >> I dont know why it was not working earlier. >> >> And jackson . I ran both the commands. >> root@vishnupc:/# /opt/local/bin/port-tclsh /opt/local/libexec/m

Re: Strange behaviour of trace mode in MacPorts 2.4.3 / 10.13

On 29 April 2018 at 09:43, Jackson Isaac wrote: > Hi Mojca, > > I am running 2.4.99 on 10.13.4. For me the fetch worked without any errors > > Logs: https://paste.macports.org/2998aff5e709 > > Did you try running the fetch again ? Probably a network issue. I have > faced similar svn checkout errors

Re: Releasing 2.4.4

Hi, Are there any news or progress about the 2.4.4 release? Mojca On 21 April 2018 at 17:27, Rainer Müller wrote: > Hello, > > as discussed in today's online meeting [1], there is nothing left to be > fixed or backported to the release-2.4 branch for MacPorts 2.4.4. > > The ChangeLog shows the c

Re: Gsoc 18 Project | Collect build statistics

On 29 April 2018 at 10:17, Jackson Isaac wrote: > On Sun, Apr 29, 2018 at 1:21 PM, Mojca Miklavec wrote: >> >> >> I would say that the next most reasonable step (apart from any other >> thing from the list I sent in the beginning) would be to create a >> reposit

Re: Gsoc 18 Project | Collect build statistics

Dear Vishnu, On 29 April 2018 at 16:45, Vishnu wrote: > Hi > > Jackson i have already replied to the mail regarding username. > > Mojca, I was able to edit the file and entered values manually in the code > of mpstats. > > vishnu@vishnupc:~$ /opt/local/bin/port-tclsh /opt/local/libexec/mpstats sho

Re: Gsoc 18 Project | Collect build statistics

On 29 April 2018 at 19:34, Vishnu wrote: > Hey > > I wanted to work on finalising the database. What all final columns in each > table. This is a creative process that should in the first place be carefully crafted by you - of course with sufficient input and feedback from our side. > Take your f

Re: Gsoc 18 Project | Collect build statistics

On 30 April 2018 at 02:22, Vishnu wrote: > Hi > > After hours of fixing error in heroku and my ubuntu . > Finally got to run the so far app. Yay! That's great since it will be much easier for the whole community to test the app much more quickly. Now, it would be great to pick some name for the r

Re: Strange behaviour of trace mode in MacPorts 2.4.3 / 10.13

Dear Clemens, On 29 April 2018 at 18:00, Clemens Lang wrote: > On Sun, Apr 29, 2018 at 09:34:10AM +0200, Mojca Miklavec wrote: >> Hi, >> >> This looks pretty strange to me: >> >> ---> Fetching distfiles for pymol >> Executing: cd "/path/t

Re: Gsoc 18 Project | Collect build statistics

On 30 April 2018 at 18:47, Jackson Isaac wrote: > On Mon, Apr 30, 2018 at 10:06 PM, Vishnu wrote: >> Hey >> >> Repository names: >> MacPorts-features? >> Macportsinfo? >> Or just simple >> gsoc18? No, gsoc18 is a bad name since the idea is to use the project afterwards as well and I don't like to

Re: Request for discussion: lowering the backlog of old Trac tickets.

Dear Perry, On 30 April 2018 at 18:16, Perry E. Metzger wrote: > So I started looking over the Trac tickets a few days ago. Thanks a lot for taking the initiative for this. Below are some of my thoughts. One thing I really dislike about many projects is that one sometimes spends quite a while t

Re: Request for discussion: lowering the backlog of old Trac tickets.

On 1 May 2018 at 02:35, Jeremy Lavergne wrote: > On 04/30/2018 07:01 PM, Mojca Miklavec wrote: >> tickets that we cannot address, but don't explicitly close either. >> Something like a "stale" state? > > "wontfix" ? "Won't fix" sound

Instructions for creating patches (Re: trac rrdtool)

On 1 May 2018 at 16:11, Rainer Müller wrote: > > The guide uses "Portfile-rrdtool.diff" as an example filename [1]. Some > users seem to take that literally and submit patches with that name. > > [1] https://guide.macports.org/#development.patches.portfile Looking at this part of the guide, I woul

Re: Remove all remnants of python <2.7

On 4 May 2018 at 15:05, Perry E. Metzger wrote: > Yesterday, Ryan pointed out in the course of a pull request that the > port in question still had support for python 2.5(!). > > I'd like to propose that we should systematically remove all > references in Portfiles to any version of Python before 2

Re: Gsoc 18 Project | Collect build statistics

On 6 May 2018 at 20:52, Bradley Giesbrecht wrote: > > macports-webapp? Let's go with that one then. Joshua, or anyone else from portmgr, can you please create a new repository inside macports org? In case anyone else wants to join, we'll have an audio meeting tonight at 17:00 UTC (probably on g

Re: Gsoc 18 Project | Collect build statistics

Dear Vishu, On 7 May 2018 at 20:52, Jackson Isaac wrote: > On Tue, May 8, 2018 at 12:01 AM, Vishnu wrote: >> >> 2) Upload a file with DB schema . > > There should be some way that you can create tables/schema > using markdown. But feel free to use whatever works better for you. Probably a regul

Re: Gsoc 18 Project | Collect build statistics

On 8 May 2018 at 01:12, Vishnu wrote: > Hi > > I will work on all the points mentioned today.. > > But i have been trying many different ways. > To get 20k ports onto the database.. The site is crashing.. Timeout error. > Or the site cant be reached. > Maximum i got till 9k ports successfully enter

Re: kmymoney4 not working!

Dear Ben, On 9 May 2018 at 23:15, Ben W wrote: > > Hello Mojca, > > Sorry if e-mailing directly is not proper bug reporting etiquette, but I'm > not familiar with how or where to do that, There are three major ways: - ask on IRC channel #macports on Freenode - ask on the macports[-devel] mailing

Re: Gsoc 18 Project | Collect build statistics

On 11 May 2018 at 04:00, Vishnu wrote: > Hi > > Also i wanted to know > For this link > https://www.macports.org/ports.php?by=name&substr=python27 > > There is already existing database with loads of information. > Is it not updated? > is it static ? It is not static, the database is updated via

Re: Gsoc 18 Project | Collect build statistics

On 12 May 2018 at 14:17, Rainer Müller wrote: > On 2018-05-12 10:34, Vishnu wrote: >> I am not saying that my db and the exiting Db would be interdependent. >> Rather i am saying just once in forever I can copy the content to my >> database. >> Then do the code to keep on updating it whenever somet

Re: Gsoc 18 Project | Collect build statistics

Dear Vishnu, Sorry for being slightly out-of-sync (sending emails I wrote quite a while ago and in the meantime no longer being up-to-date with other responses). On 12 May 2018 at 17:26, Vishnu wrote: > Hi > > "The PortIndex file itself is generated with the 'portindex' command, > which only upda

Re: Question about MacPorts project membership application

Dear Chih-Hsuan Yen, On 13 May 2018 at 16:37, Chih-Hsuan Yen wrote: > Hello everyone, > > Perry Metzger suggests me to apply for MacPorts project membership on two of > my pull requests [1][2], so I wrote a letter "Commit access: Chih-Hsuan Yen" > to macports-...@lists.macports.org 5 days ago, fol

Re: [macports-mgr] Question about MacPorts project membership application

On 13 May 2018 at 21:32, Rainer Müller wrote: > On 2018-05-13 18:30, Mojca Miklavec wrote: >> The portmgr team might need some time to check the contributions and >> verify candidate's suitability for commit rights, but maybe they >> forgot to send you a preliminary conf

Re: Gsoc 18 Project | Collect build statistics

Dear Vishnu, On 13 May 2018 at 09:37, Vishnu wrote: > Hey > > Mojca you said once that you have lot to comment on the current database. > So it would be great if you could do that. I left a comment on https://github.com/macports/macports-webapp/issues/2 and made a bunch of changes and suggest

Re: Gsoc 18 Project | Collect build statistics

On 15 May 2018 at 05:46, Vishnu wrote: > Hi > > Yes I was laos thinking about it for some time. > > Please someone from infra team create another repository. This would also remove all the tickets etc., so I don't think it is a super good idea. Git is flexible enough to allow force pushing to a b

Re: [macports-mgr] Question about MacPorts project membership application

On 16 May 2018 at 16:42, Chih-Hsuan Yen wrote: > > Here I have an idea: how about making application letters public? If so > applicants can check if their letters are received or not easily. The problem is that this also publically exposes candidates whose application has been rejected (even if on

Re: Pull Request Etiquette

V ned., 20. maj 2018 00:06 je oseba Marcus Calhoun-Lopez napisala: > There is a pull request to update Octave to 4.4.0. > A significant amount of work has been put in to it. > While attempting to address some of the outstanding issues, my version had > diverged in some significant ways. > > Does a

(Not) deprecating py35 subports

Hi, Recently a PR has been merged which put a py35 subport into a graveyard. I just wanted to say that we should first focus our efforts into: * Getting entirely rid of python 2.6 and python3.3 and lower, starting with regular ports like vim which still ships with python26 and python33 variants (

Request for help with DYLD_LIBRARY_PATH-related bug in perl5.28 build

Hi, Is there any volunteer to help with rewriting/fixing part of the perl build system*** (which sets DYLD_LIBRARY_PATH to current build path for the sake of finding the library, just to be later shadowed by the OS, probably for security reasons)? The bug first appeared in running the test suite:

Re: Request for help with DYLD_LIBRARY_PATH-related bug in perl5.28 build

On 17 August 2018 at 02:42, Tony Cook wrote: > On Thu, Aug 16, 2018 at 12:28:32PM +0200, Mojca Miklavec wrote: >> Hi, >> >> Is there any volunteer to help with rewriting/fixing part of the perl >> build system*** (which sets DYLD_LIBRARY_PATH to current build path >

Re: squash and merge, license documentation, "size" documentation

Hi, On 18 August 2018 at 12:47, Perry E. Metzger wrote: > On Fri, 17 Aug 2018 22:15:38 -0700 Eitan Adler wrote: >> On Fri, 17 Aug 2018 at 06:44, Perry E. Metzger wrote: >> > >> > As many of you are aware, I merge a significant fraction of the >> > pull requests these days. A few requests to make

ranlib: malformed objects on 10.6

Hi, After upgrading ports on 10.6 (I probably didn't touch the machine since about May this year) I ran into issue compiling software with clang-5.0 against libc++: /usr/bin/ranlib: object: .libs/libfoo.a(libfoo_la-bar-file.o) malformed object (unknown load command 2) ar: internal ranlib command

Re: ranlib: malformed objects on 10.6

hours to wait for the build to finish to confirm that). Thanks again, Mojca > > On 3 Sep 2018, at 8:40 pm, Mojca Miklavec wrote: > > > > Hi, > > > > After upgrading ports on 10.6 (I probably didn't touch the machine > > since about May this year) I ran

  1   2   3   4   5   6   7   8   >