Re: [GSoC 2017] Second Evaluation

Thanks, I completed the mentor evaluation for the Migration project. Regards, Bradley Giesbrecht (pixilla) > On Jul 24, 2017, at 9:10 AM, Jackson Isaac <ijack...@macports.org> wrote: > > Hi GSoC Students and Mentors, > > Phase 2 evaluations has begun. Deadline for fi

Re: [GSoC 2017] Second Evaluation

for this period too as I did for the last one, as >> soon as possible. >> >> Regards, >> Umesh >> >> Umesh Singla >> >> On Mon, Jul 24, 2017 at 9:40 PM, Jackson Isaac <ijack...@macports.org> >> wrote: >> >>> Hi GSoC Students and

Re: [GSoC 2017] Second Evaluation

luation from my side on the portal. I'll try to > come up with a write-up for this period too as I did for the last one, as > soon as possible. > > Regards, > Umesh > > Umesh Singla > > On Mon, Jul 24, 2017 at 9:40 PM, Jackson Isaac <ijack...@macports.org> > wrot

[GSoC 2017] Second Evaluation

Hi GSoC Students and Mentors, Phase 2 evaluations has begun. Deadline for filling the evaluations is July 28, 2017 16:00 UTC. The procedure remains the same as previous. Also please summarize the work done until now, challenges faced and how did you manage to overcome them. Please let us know

Re: [GSoC] migration

On 22 Jul 2017, at 03:01, Umesh Singla wrote: > I don't know, in the above example, what do you mean when you say "..you > realize that from its deps..", like, realize how? I am just asking this if > there's some other way to get info on the latest modifications that

Re: [GSoC] migration

On 2017-7-22 11:01 , Umesh Singla wrote: Another thing that comes to my mind now is if, suppose, updated version of ncurses was actually required for some another port and reverting it to the older state could possibly result in breaking of that port. May be, we could get all the ports which

Re: [GSoC] migration

Hi On Fri, Jul 21, 2017 at 5:39 PM, db wrote: > On 21 Jul 2017, at 13:02, Umesh Singla wrote: > > Unless we have a snapshot of the previous state, that is, before it got > hampered. > > But then again, we reinstall all the ports presently. At this

Fwd: [GSoC] migration

Forwarding this to macports-dev. -- Forwarded message -- From: Umesh Singla <umeshksin...@gmail.com> Date: Fri, Jul 21, 2017 at 4:32 PM Subject: Re: [GSoC] migration To: db <iams...@gmail.com> Hi > > Snapshot and restore should be able to be executed with

Re: [GSoC] migration

On 21 Jul 2017, at 13:02, Umesh Singla wrote: > Unless we have a snapshot of the previous state, that is, before it got > hampered. > But then again, we reinstall all the ports presently. At this time, it could > be hard for me to detect what went wrong while sync or

Re: [GSoC] migration

Hi Brad, Clemens, Josh Please see inline. > GSoC Week #7 (13 Jul - 19 Jul) > > > > I moved the things to migrate action instead of 'restore' since > 'restore' looks a subset of 'migrate', so can be dealt easily once migrate > is over. > > I’m not sure I understand and

Re: [GSoC] migration

On 20 Jul 2017, at 06:04, Bradley Giesbrecht <pixi...@macports.org> wrote: > Snapshot and restore should be able to be executed without migrate. I have a question and I haven't been following in detail this GSoC, so bear with me. Could snapshot and restore be used to rollback to a

Re: [GSoC] migration

> On Jul 19, 2017, at 3:43 PM, Umesh Singla <umeshksin...@macports.org> wrote: > > Hi Brad, > > With another week over, I have the following updates to share. > > > GSoC Week #7 (13 Jul - 19 Jul) > > I moved the things to migrate action instead of 'restor

Re: [GSoC] migration

Hi Brad, With another week over, I have the following updates to share. *GSoC Week #7 (13 Jul - 19 Jul)* I moved the things to migrate action instead of 'restore' since 'restore' looks a subset of 'migrate', so can be dealt easily once migrate is over. Agenda for last week: The migrate

[GSoC] Progress Report

Hi, In the last two weeks, I deployed pastebin upload from Travis and we now have full build logs available on https://paste.macports.org and linked in Travis logs. In some builds the pastebin link was lost, I fixed this bug and a typo that caused failed builds reported as successful (Oops!). I

Re: [GSoC] migration

On 2017-7-14 01:42 , Arno Hautala wrote: On Thu, Jul 13, 2017 at 11:34 AM, Joshua Root wrote: Depending on a variant is currently impossible. ... You do have to install the ports in dependency order to get it right, and that is what restore_ports does. There may be cases

Re: [GSoC] migration

On Thu, Jul 13, 2017 at 11:34 AM, Joshua Root wrote: > > Depending on a variant is currently impossible. > > ... > > You do have to install the ports in dependency order to get it right, and > that is what restore_ports does. There may be cases where previously > inactive ports

Re: [GSoC] migration

On 2017-7-13 22:49 , Arno Hautala wrote: On Wed, Jul 12, 2017 at 8:07 PM, Joshua Root wrote: On 2017-7-13 08:10 , Umesh Singla wrote: 3. ensuring that active versions are installed after the inactive versions The install action of port(1) does execute the activate

Re: [GSoC] migration

On Wed, Jul 12, 2017 at 8:07 PM, Joshua Root wrote: > On 2017-7-13 08:10 , Umesh Singla wrote: >> >> 3. ensuring that active versions are installed after the inactive >> versions > > The install action of port(1) does execute the activate target, however your > code could

Re: [GSoC] migration

On 2017-7-13 08:10 , Umesh Singla wrote: 3. ensuring that active versions are installed after the inactive versions since the output after running `port install vim -huge +tiny`: —— Computing dependencies for vim .. --->Staging vim into destroot *--->Installing vim @8.0.0596_0+tiny*

Re: [GSoC] migration

Hi > • A snapshot would be a list of install commands that created the > current installed state. > > • Restoring a snapshot would deactivate the active ports and > reproduce the install commands for the selected snapshot. > > • Migrate would amount to creating a new snapshot,

Re: [GSoC] migration

> On Jul 12, 2017, at 3:10 PM, Umesh Singla wrote: > > Hi Brad, > > With another week over, I have the following updates to share. These are > actually the points from my Notes as I keep going on, so the email might not > be well crafted. Thought, would share with

Re: [GSoC] migration

Hi Brad, With another week over, I have the following updates to share. These are actually the points from my Notes as I keep going on, so the email might not be well crafted. Thought, would share with you without any delay. *Week #5-6 (28 Jun - 12 Jul)* Golden lines for the project: 1. A

Re: [GSoC] migration

Josh, thank you for responding. Regards, Bradley Giesbrecht (pixilla) > On Jul 11, 2017, at 11:58 AM, Joshua Root wrote: > > On 2017-7-12 04:43 , Umesh Singla wrote: >> Hi Brad, >> While I was writing for restoring of ports, it seems that I need to include >> another field

Re: [GSoC] migration

On 2017-7-12 04:43 , Umesh Singla wrote: Hi Brad, While I was writing for restoring of ports, it seems that I need to include another field 'active' along with ports while taking snapshot. This might sound obvious now but it wasn't to me before I looked at what is going on, closely. While

Re: [GSoC] migration

Hi Brad, While I was writing for restoring of ports, it seems that I need to include another field 'active' along with ports while taking snapshot. This might sound obvious now but it wasn't to me before I looked at what is going on, closely. While there is something like 'active' port but

[GSoC] Progress Report

Hi, In the last two weeks, I fixed a few bugs in the Travis integration. * Fixed `git checkout` when `TRAVIS_COMMIT` is not HEAD * Fixed port listing, use `git diff` with three dots * Fixed typo, use subport name in MIME field name * Fixed lint error when no Portfile changed * Fixed detection

Re: [GSoC 2017] First Evaluation

Hello all, I have prepared a small informal write up about the work and challenges faced till now and posted on my blog [1]. Also, I have already completed my side of evaluation and submitted on GSoC website. Looking forward to community reviews. Regards, Umesh Singla [1]: https

[GSoC 2017] First Evaluation

Hi GSoC Students and Mentors, Phase 1 evaluation has started as of now until 16:00 UTC June 30, 2017. Please make sure that students fill out the mentor evaluations and at least one mentor evaluate the student performance before the deadline. It would be also good if the students can prepare

Re: Fwd: [GSoC] migration

On 2017-6-25 08:24 , Umesh Singla wrote: Anyway I tried consulting the existing migration guide. Why does it save the list of all installed ports and then sets the requested flags? Only installing the requested and let the dependencies figure out themselves - is it an improvement we're making

Re: [GSoC] migration

On 2017-6-25 06:29 , Bradley Giesbrecht wrote: On Jun 22, 2017, at 8:15 PM, Joshua Root wrote: On 2017-6-23 11:29 , Bradley Giesbrecht wrote: For the migration functionality wouldn’t we only install “requested” ports? Dependencies could be different with a platform change.

Fwd: [GSoC] migration

; Date: Fri, Jun 23, 2017 at 7:39 AM Subject: Re: [GSoC] migration To: Bradley Giesbrecht <pixi...@macports.org> Hi Brad I assumed we would allow multiple snapshots and be able to chose from a > list of snapshots by date-sequence. > Yes, and I think, adopting the files strategy

Re: [GSoC] migration

Hi Bradley, On Sun, Jun 25, 2017 at 1:59 AM, Bradley Giesbrecht wrote: > > >> For the migration functionality wouldn’t we only install “requested” > ports? Dependencies could be different with a platform change. > >> Also, if the installed variants for a given port are the

Re: [GSoC] migration

On 2017-6-23 11:29 , Bradley Giesbrecht wrote: On Jun 21, 2017, at 7:25 PM, Umesh Singla wrote: Hi Taking a step back for a moment, why is an SQL database the best way to store this data? What sorts of queries are you going to want to run on it? Would

Re: [GSoC] migration

Hi Taking a step back for a moment, why is an SQL database the best way >> to store this data? What sorts of queries are you going to want to >> run on it? Would a text (Tcl array) representation similar to the >> PortIndex be a better fit? >> >> >> We need to store all the

Re: [GSoC] migration

On 2017-6-22 02:09 , Umesh Singla wrote: Hi Josh, Taking a step back for a moment, why is an SQL database the best way to store this data? What sorts of queries are you going to want to run on it? Would a text (Tcl array) representation similar to the PortIndex be a better fit?

Re: [GSoC] migration

Hi Josh, Taking a step back for a moment, why is an SQL database the best way to > store this data? What sorts of queries are you going to want to run on it? > Would a text (Tcl array) representation similar to the PortIndex be a > better fit? > We need to store all the information about the

Re: [GSoC] migration

On 2017-6-20 03:58 , Umesh Singla wrote: Hi Bradley, I'm having a bit difficulty in implementing the body of snapshot procedure. Basically what I need to do now is (as I have written in my notes, so you can tell me if I'm on right track in my thoughts as well): "get the list of installed

Re: [GSoC] migration

Hi Bradley, I'm having a bit difficulty in implementing the body of snapshot procedure. Basically what I need to do now is (as I have written in my notes, so you can tell me if I'm on right track in my thoughts as well): "get the list of installed ports, their-installed-variants and

[GSoC] Progress Report

Hi, I've finished the Travis integration to test PRs sent to macports-staging/macports-ports. Code is currently at https://github.com/macports-staging/mpbot-github. I will deploy it to our repositories next week but please don't rely on it just yet. Travis has a 4 MiB log output per build

Re: [GSoC] migration

> On Jun 13, 2017, at 8:47 PM, Umesh Singla wrote: > > I suggest IRC #macports on Wednesdays at 2:00 PM UTC. If this time does not > work for anyone who would like to be included suggest an alternative or > additional day and time. > > So, today! I hung out by

Re: [GSoC] migration

On 2017-06-14 05:48, Umesh Singla wrote: > Thanks Rainer for this. This is really useful. I had doubts on how often > cregistry/sql.c file gets updated or whether this is the one. The name > sql.c seems to be so OS core file. So, I can just add the new tables here? > > Also, new tables means

Re: [GSoC] migration

On 2017-06-14 05:47, Umesh Singla wrote: > > 4. Another thing that ran my mind while pondering that there are 2 > options for sqlite database as well: make the tables in the very > beginning (while initial installation) or while running the snapshot > for the first time. I suggest

Re: [GSoC] migration

Hi For testing it should be enough to just modify the registry.db locally > as you need it. Once you reach a stable schema, you will have to add > modifications to the registry schema at two places. > > 1) The initial database schema for new installations is defined here: > >

Re: [GSoC] migration

Hi > I have not followed Rainer's strategy for having `port snapshot --create` > and `port snapshot --restore` as discussed in the previous thread, instead > have 3 separate actions... > > If I am following this correctly I think isolating the functionality into > actions makes sense. If we want

Re: [GSoC] migration

On 2017-06-11 19:07, Bradley Giesbrecht wrote: >> 4. Another thing that ran my mind while pondering that there are 2 options >> for sqlite database as well: make the tables in the very beginning (while >> initial installation) or while running the snapshot for the first time. I >> suggest to go

Re: [GSoC] migration

Hi Umesh, Thanks to Rainer for his comments on 2 and 5. My comments and questions inline. On Jun 8, 2017, at 3:12 PM, Umesh Singla wrote: > > 1. The agenda as per the proposal timeline [1] for the period from May 30 to > Jun 10 is to finalize the different cases

Re: [GSoC] migration

Hi Rainer, I have already created a new branch gsoc17-migrate in macports-base after discussing with Jackson on IRC and just now, pushed some initial code to https://github.com/macports/macports-base/tree/gsoc17-migrate, to begin with. For the copyright part, I'll just ignore it, for now, it

[GSoC] migrate action

Umesh: Coding officially began on May 30th, please reply with an update on the progress and current status of the development process and any questions we may be able to help with. Regards, Bradley Giesbrecht (pixilla)

Re: [GSoC] Progress Report

On 6 June 2017 at 04:15, Zero King wrote: > On Mon, Jun 05, 2017 at 02:08:20PM +0200, Rainer Müller wrote: >> >> How is getopt relevant for the timing? If the dependency on getopt is a >> problem, let's find a portable solution for mpbb. Duplicating the exact >> same functionality we already have

Re: [GSoC] Progress Report

On 2017-06-06 04:15, Zero King wrote: > On Mon, Jun 05, 2017 at 02:08:20PM +0200, Rainer Müller wrote: >> On 2017-06-05 03:17, Zero King wrote: >>> All information CI bot have access to is public, so I'm worried that >>> someone would send PR bot data without submitting a PR at all. >> >> Make the

Re: [GSoC] Progress Report

On Mon, Jun 05, 2017 at 02:08:20PM +0200, Rainer Müller wrote: On 2017-06-05 03:17, Zero King wrote: All information CI bot have access to is public, so I'm worried that someone would send PR bot data without submitting a PR at all. Make the PR bot pull data from Travis. The CI bot then only

Re: [GSoC] Progress Report

On 2017-06-05 03:17, Zero King wrote: > All information CI bot have access to is public, so I'm worried that > someone would send PR bot data without submitting a PR at all. Make the PR bot pull data from Travis. The CI bot then only triggers the PR bot, which then checks for new unprocessed

Re: [GSoC] Progress Report

On Sun, Jun 04, 2017 at 11:13:54PM +0200, Rainer Müller wrote: As far as I understand it, the CI "bot" are just scripts to be executed on Travis CI, but the PR bot will be a daemon process running on our own infrastructure? Yes, except that the CI bot is not just scripts. The CI bot is written

Re: [GSoC] Progress Report

On Sun, Jun 04, 2017 at 10:23:52PM +0200, Mojca Miklavec wrote: Dear Zero King, Thank you very much for the update. There's one thing I didn't fully understand: https://github.com/l2dy/mpbot-design/blob/master/cibot.md#interaction-with-ci-bot "This design is aimed for traceability, we can

Re: [GSoC] Progress Report

On 2017-06-04 14:49, Zero King wrote: > GSoC coding phrase has begun and I'm implementing a CI bot that runs on > Travis CI and tests pull requests. > > My project includes two bots, the CI bot testing pull requests and the > PR bot assigning labels to PRs and notify maintainer

Re: [GSoC] Progress Report

Dear Zero King, On 4 June 2017 at 14:49, Zero King wrote: > Hi, > > GSoC coding phrase has begun and I'm implementing a CI bot that runs on > Travis CI and tests pull requests. > > My project includes two bots, the CI bot testing pull requests and the > PR bot assigning lab

[GSoC] Progress Report

Hi, GSoC coding phrase has begun and I'm implementing a CI bot that runs on Travis CI and tests pull requests. My project includes two bots, the CI bot testing pull requests and the PR bot assigning labels to PRs and notify maintainers. The design docs are available at https://github.com/l2dy

Re: [GSoC 2017] Community Bonding

Hi, On Fri, May 26, 2017 at 12:57:11AM +0530, Umesh Singla wrote: > Since we are planning on 3 different actions which can also be used > independently like snapshot and migrate, having 2 scripts in the > macports1.0 directory directly or keeping these 2 commands in a single > script doesn't seem

Re: [GSoC 2017] Community Bonding

Hi, On Thu, May 18, 2017 at 11:37 PM, Jackson Isaac <ijack...@macports.org> wrote: > Hi GSoC Students and Mentors, > > I hope you are utilizing the community bonding period well and had > some kind of introductory get to know interaction between > student-mentor(s) already.

Re: [GSoC 2017] Community Bonding

On 05/25/2017 09:27 PM, Umesh Singla wrote: > > About the project, so the `restore`, `snapshot` and `migrate` actions > > are going to the action_array list [1]. While the flow was made clear > > in the proposal, I think the first step should be to decide on an > > exhaustive list

Re: [GSoC 2017] Community Bonding

Hi > > About the project, so the `restore`, `snapshot` and `migrate` actions > > are going to the action_array list [1]. While the flow was made clear > > in the proposal, I think the first step should be to decide on an > > exhaustive list of arguments/flags these 3 actions can possibly take.

Re: [GSoC 2017] Community Bonding

I've got it. It's umeshksin...@macports.org and the GitHub account I'll be using is github.com/umeshksingla. Thanks On May 23, 2017 3:39 AM, "Bradley Giesbrecht" wrote: > On May 22, 2017, at 12:22 PM, Umesh Singla wrote: > > I have written two

Re: [GSoC 2017] Community Bonding

> On May 22, 2017, at 12:22 PM, Umesh Singla wrote: > > I have written two introductory posts on my blog [0] on Blogger. > > [0]: http://umeshsingla.blogspot.in/ Umesh, thanks for sharing this link. In your second blog post you mention that by now you should have

Re: [GSoC 2017] Community Bonding

Hi, On Tue, May 23, 2017 at 12:52:55AM +0530, Umesh Singla wrote: > I have written two introductory posts on my blog [0] on Blogger. I > thought I shared the link to it in the proposal but no, I didn't. The > one is just when the results got announced and other about my take on > the

Re: [GSoC 2017] Community Bonding

Hi I have written two introductory posts on my blog [0] on Blogger. I thought I shared the link to it in the proposal but no, I didn't. The one is just when the results got announced and other about my take on the macports-base video. About the project, so the `restore`, `snapshot` and `migrate`

Re: [GSoC 2017] Community Bonding

> On May 18, 2017, at 11:07 AM, Jackson Isaac wrote: > > neverpanic's session[1] during MacPorts Meeting should help you get > started with macports-base and give you a good overview of macports > internals. Please go through it if not yet done. > > It would be great to

Re: [GSoC 2017] Community Bonding

Hi, On 18 May 2017 at 20:07, Jackson Isaac wrote: > Hi GSoC Students and Mentors, > > I hope you are utilizing the community bonding period well and had > some kind of introductory get to know interaction between > student-mentor(s) already. If not yet, please do so, it would he

Re: alternative/leaner installer creation algorithm: GSoC idea?

On Saturday May 13 2017 16:03:59 Craig Treleaven wrote: >> That is also inherent to the fact that Qt4 is installed as a monolithic >> port, not split in the different Qt components as port:qt5 is. >> >That horse is long gone from the barn. Anyway, my MythTV packages didn’t get >much smaller

Re: alternative/leaner installer creation algorithm: GSoC idea?

> On May 13, 2017, at 1:11 PM, René J.V. Bertin wrote: > > On Saturday May 13 2017 11:06:37 Craig Treleaven wrote: > >> Indeed. I presume it is the expanded installer payload that is 2 GB. For >> me, a 330 MB installer expands to just over 1 GB on a destination system. >

Re: alternative/leaner installer creation algorithm: GSoC idea?

doubt I'm the 1st to give these issues some thought but here's a brief >> outline of what I think might be possible as an alternative algorithm - and >> a nice GSoC or similar project. It's inspired by the rev-upgrade feature and >> should be able to use the information and func

Re: alternative/leaner installer creation algorithm: GSoC idea?

On Saturday May 13 2017 15:41:30 Rainer Müller wrote: Hi, > Hm, but everyone will get this many dependencies when they do the > regular 'sudo port install rkward'. Why would this only be a specific > problem for .pkg distribution? It's my understanding that .pkg installers are meant for

Re: Congratulations to all the selected GSOC students and projects

On 2017-5-12 06:45 , Clemens Lang wrote: Hey, On Tue, May 09, 2017 at 12:47:15PM +1000, Joshua Root wrote: On 2017-5-9 12:11 , Zero King wrote: Does anyone have a list of packages to install on Ubuntu Trusty to run MacPorts? This would save some test builds for Travis. The "Other Platforms"

Re: Congratulations to all the selected GSOC students and projects

Hey, On Tue, May 09, 2017 at 12:47:15PM +1000, Joshua Root wrote: > On 2017-5-9 12:11 , Zero King wrote: > > Does anyone have a list of packages to install on Ubuntu Trusty to > > run MacPorts? This would save some test builds for Travis. > > The "Other Platforms" section of

Re: Congratulations to all the selected GSOC students and projects

tion with my mentors. > > Thanks again, and you'll be hearing from me soon. > Have a nice weekend everyone! :) > > Regards > > On Fri, May 5, 2017 at 12:19 AM, Mojca Miklavec <mo...@macports.org> wrote: > Dear students and developers, > > Google just announced

Re: Congratulations to all the selected GSOC students and projects

On 2017-5-9 12:11 , Zero King wrote: Does anyone have a list of packages to install on Ubuntu Trusty to run MacPorts? This would save some test builds for Travis. The "Other Platforms" section of should cover it. So tcl, freebsd-buildutils (provides

Re: Congratulations to all the selected GSOC students and projects

On Mon, May 08, 2017 at 10:56:40PM +0200, Rainer Müller wrote: On 2017-05-08 21:57, Clemens Lang wrote: I'm trying to install MacPorts on Travis VMs. I want to avoid syncing the ports tree to save more time for actual testing. Since the .pkg installer would automatically call `port -v

Re: Congratulations to all the selected GSOC students and projects

On 2017-5-9 02:02 , Zero King wrote: I'm trying to install MacPorts on Travis VMs. I want to avoid syncing the ports tree to save more time for actual testing. You could prevent this by creating a sources.conf pointing to your prefabricated ports tree, tagged with [default,nosync], before

Re: Congratulations to all the selected GSOC students and projects

> On May 4, 2017, at 11:49 AM, Mojca Miklavec <mo...@macports.org> wrote: > > Dear students and developers, > > Google just announced 1,318 projects selected for the GSOC 2017. > > I'm happy to share with you that MacPorts got two slots for the > following

Re: Congratulations to all the selected GSOC students and projects

Hi, On Sun, May 07, 2017 at 11:12:04PM +0200, Clemens Lang wrote: You have been accepted into Google Summer of Code 2017 and will work for MacPorts over the summer. Congratulations, we are happy to have you! Thanks for picking my project and mentoring. Please read our guidelines we put

Re: Congratulations to all the selected GSOC students and projects

Hi Umesh and Zero, and welcome to MacPorts! You have been accepted into Google Summer of Code 2017 and will work for MacPorts over the summer. Congratulations, we are happy to have you! First of all let me welcome you to our organization. I am looking forward to a good summer with an interesting

Re: Congratulations to all the selected GSOC students and projects

announced 1,318 projects selected for the GSOC 2017. > > I'm happy to share with you that MacPorts got two slots for the > following projects: > > - Umesh Singla: > Adding migrate action to port command > mentor: Bradley Giesbrecht (pixilla) > > - "Zero King"

Congratulations to all the selected GSOC students and projects

Dear students and developers, Google just announced 1,318 projects selected for the GSOC 2017. I'm happy to share with you that MacPorts got two slots for the following projects: - Umesh Singla: Adding migrate action to port command mentor: Bradley Giesbrecht (pixilla) - "Zero King&q

Re: GSoC Proposal

spend their time where it matters most. > - Some glue code that knows how to communicate between GitHub and > BuildBot: which jobs to submit, how to report success etc. > > The glue code might need some time to be implemented, but it sounds > like something in the same direction

Re: GSoC Proposal

(and then that pull request would get a green icon of course once the build is complete). When a pull request gets updated/modified, the build could be tested again, but it would have to be triggered manually again. I had this idea in mind but chose the one in the proposal because I'd like to finis

Re: GSoC Proposal

Hi, Just to clarify one thing (also to any other GSOC applicant): this discussion does not provide any indication about the ranking of the submitted proposal or whether this or any other proposal might be or not be accepted. There might be better or worse applications where less clarification

Re: GSoC Proposal

On 4/2/17 6:03 AM, Mojca Miklavec wrote: Thank you. Please include that into the proposal as well. It wasn't clear to me whether your project would be a full "replacement" compared to the current functionality of the buildbot or just covering some small load cycle (like doing very very basic

Re: GSoC Proposal

macOS VMs on Travis would do `port lint | tee lint.txt; if grep "^Error: " lint.txt ; then ...` and `port install ...` (`port test ...` if test exists) and if one of them failed Travis will report that back to GitHub. Also Travis will keep logs so lint results will be available there. On

Re: GSoC Proposal

Have you seen how homebrew does this? I imagine he means something like that: Every submission has to be submitted to the 10.10 - 10.12 bots first, to see if it builds. Every submission is suggested / required to have at least a minimal test `myport --version` to make sure something actually

Re: GSoC Proposal

Can you please elaborate a bit more on Travis CI will do lint and install tests on macOS 10.10-12 for PRs and commits. What does "install tests" refer to exactly? Mojca

[GSoC 2017] Student Application deadline for GSoC 2017 is near!

Hi, This is a gentle reminder for GSoC 2017. Student applications close on 3rd April 2017 at 1600 UTC. Remember to upload your final proposal as PDF on the GSoC portal in order to be considered for GSoC 2017. -- Jackson Isaac

Re: GSoC Proposal

On 3/31/17 6:23 PM, Rainer Müller wrote: First of all, great to see a proposal coming from you as a project member! Thanks. We do not have anything else in Go yet, so this would be new to our infrastructure. I am a bit hesitant with that, because even after this GSoC, we will need someone

Re: GSoC Proposal

Hello, On 2017-03-31 17:43, Zero King wrote: > I'd like to implement a bot in Go dealing with pull requests for > macports-ports on GitHub and utilize Travis CI to test PRs and commits > in GSoC 2017. > > More details in my draft: > https://gist.github.com/l2dy/420533b821570e

Re: GSoC Proposal

Hi, On Fri, 31 Mar 2017 at 9:14 PM, Zero King <l...@icloud.com> wrote: Hi, I'd like to implement a bot in Go dealing with pull requests for macports-ports on GitHub and utilize Travis CI to test PRs and commits in GSoC 2017. More details in my draft: https://gist.github.co

Re: GSOC Application

On 03/31/2017 12:08 AM, Bradley Giesbrecht wrote: > Would the buildbots upload the tarballs to the MacPorts mirrors? Yes, that is the idea. It will not even require anything special on the buildbots, as just running the usual 'sudo port fetch' will generate this tarball after fetching from VCS.

Re: GSoC'17: Add migrate action to port command Project

> On Mar 30, 2017, at 12:13 PM, Clemens Lang wrote: > > Hey everybody, > > On Tue, Mar 28, 2017 at 01:37:55PM -0700, Bradley Giesbrecht wrote: >>> On Mar 28, 2017, at 11:55 AM, Umesh Singla wrote: >> >> Does the migrate and snapshot actions help you

Re: GSOC Application

am >> new to MacPorts. I can code in C and Python and am going through the Tcl >> tutorial on the GSOC wiki. >> I have installed MacPorts and am reading the documentation provided. > > Thank you for your interest in MacPorts! That already seems like a good start. > >&

Re: GSoC'17: Add migrate action to port command Project

Hi cal, ijackson Thanks for reviewing my proposal and providing a great feedback. I've replied to most of your comments in the proposal. This surely helps. Please let me know if I have made some false assumption about anything, the timeline/ project plan needs to be modified a great bit or I

Re: GSOC Application

Hello, On 03/30/2017 04:04 PM, Chinmaya Bhat wrote: > I am Chinmaya, a third-year Computer Science student at BMSIT, Bangalore. I am > new to MacPorts. I can code in C and Python and am going through the Tcl > tutorial on the GSOC wiki. > I have installed MacPorts an

Re: GSoC'17: Add migrate action to port command Project

Hey everybody, On Tue, Mar 28, 2017 at 01:37:55PM -0700, Bradley Giesbrecht wrote: > > On Mar 28, 2017, at 11:55 AM, Umesh Singla wrote: > > Does the migrate and snapshot actions help you divide the work? The > snapshot action is basically an inventory of what is

Re: GSoC'17: Add migrate action to port command Project

Hi, I'm not too familiar with the project, but just some of my thoughts. One of the biggest pains at the moment is the fact that we don't record requested variants anywhere. We do record requested ports, but not the variants. It may easily happen that "port install foo" would install variant A

<    3   4   5   6   7   8   9   >