Re: GSoC Proposal: Rewrite key parts of MacPorts in Python
gt; that GSoC would be used as an opportunity for us to finally implement changes > that we have wanted to do for years but never got around to doing, rather > than to propose new projects whose ramifications have never been discussed > before. Thanks for your valuable insights and I really appreciate the detailed feedback. I didn't realize these things before and the efforts that went into creating and maintaining such a great project. I sincerely apologize to the community and also to the student for my ignorance and the fact that I didn't discuss this before in detail on the mailing list and understand the implications that it would make before putting anything on the ideas page. It was a pre-mature action from my side, and my intention was not to hurt anyone. This was also a learning for me personally to not put things in place without much thought, discussion and understanding. -- Jackson Isaac
Re: Update of port ehcache
On Mon, Mar 30, 2020 at 3:46 AM Ryan Schmidt wrote: > > > > On Mar 29, 2020, at 07:55, Jackson Isaac wrote: > > > If it were me, and I am interested to work on this, I would assign the > > ticket to me. > > To do so, you may > > - Login to trac using github > > - Under Modify ticket->reassign to 'Username' > > I believe only MacPorts team members are able to reassign tickets. > Didn't realize this. I notice that Saptarshi did try to assign the ticket to himself, but owner still reflected 'None'. I was able to assign it to Saptarshi. Is there a way non-members can assign themselves to a ticket ?
Re: Update of port ehcache
Hi Saptarshi, On Sun, Mar 29, 2020 at 2:25 PM SAPTARSHI MUKHERJEE wrote: > > Hi All, > > I just looked at the ticket https://trac.macports.org/ticket/60219 related to > updating of port ehcache. It involves a replacement of dependency and a few > replacements related to the website from where the file shall be fetched. > Following is the file I think is fine to be downloaded - > https://github.com/ehcache/ehcache3/releases/download/v3.8.1/ehcache-3.8.1.jar. > Kindly confirm the same. > The ticket is not assigned to anyone (meaning I don't think anyone is working to solve this, yet). If it were me, and I am interested to work on this, I would assign the ticket to me. To do so, you may - Login to trac using github - Under Modify ticket->reassign to 'Username' As for the Portfile itself, it indeed looks very outdated. I would suggest to use 'github' PortGroup to fetch the files. For ideas, you may look at existing ports using this. To make the search easy, I use 'the silver searcher' [1]. > I'd convey hereby that I'm interested to solve this issue, may kindly grant > me permission for the same. Any suggestions are always welcome. > If the portfile has 'nomaintainer' or 'openmaintainer', you are always welcome to create a pull request for it :). To understand these terms, you may look at the Note under maintainers at [2] In open source, I wouldn't expect you need to ask permission to work and improve the project, unless explicitly mentioned. [1] https://github.com/ggreer/the_silver_searcher#macos [2] https://guide.macports.org/#reference.keywords Stay safe, Jackson Isaac
[GSoC 2020] Student Application Deadline (Was: Application Template for aspiring students)
Dear Aspiring GSoC Students, Hope you all are doing well. This is a friendly reminder for the Student Application deadline i.e., 31st March 2020 1800 UTC. Make sure you submit your 'Final' proposal to the portal, in order to be eligible for GSoC, before the deadline. I hope you have been in contact with potential mentors and have already received feedback. Feel free to reach out to me if you need any guidance. On Fri, Mar 20, 2020 at 7:49 AM Jackson Isaac wrote: > > Dear Aspiring GSoC Students, > > The application period has begun on GSoC portal. There is less than 2 > weeks left for the student application deadline (31st March 2020). > > We recommend to add your draft proposals on the portal as early as > possible, so you can get feedback from potential mentors on questions > or suggestions to improve the proposal further. > > To help you get started, here[1] is a GSoC application template that > we have used in previous years as well, feel free to use it, add or > remove (sub-)sections. > > Also, a guideline on what we expect from a project application [2]. > > [1] https://trac.macports.org/wiki/SummerOfCodeApplicationTemplate > [2] > https://trac.macports.org/wiki/SummerOfCode#Whatweexpectfromstudentsfortheirapplications > > Hope this helps. Please feel free to contact us if you have any questions. > Stay safe, Jackson Isaac
Re: Port mechanism explanation needed
Hi Xim, On Tue, Mar 24, 2020 at 5:33 PM 陈国凯 wrote: > > I found no maintainers for port stlink and I wanted to take it if possible. > However, I am quite confused with the portfile mechanism of this port. > > After reading the wiki, I know that this portfile specifies a Github Repo > from which the port system obtains source code. While there are two problems > left for me. > > 1. I tried editing portfile locally, changing the version number but port > would only try fetching the source code from mirrors of MacPorts, rather than > fetching directly from Github upstream. Is there a way for me to test my > modifications locally? And how does the mirroring mechanism work? If one > changed the portfile configuration and merged changes into port tree, would > the mirrors be synced automatically? To fetch the source code/release tarball from upstream instead of mirrors, use the following command: sudo port -v fetch --no-mirror Once the Portfile is updated and merged into master, the mirrors start to pickup the latest Portfile (there might be delays involved before all mirrors are up to date). > 2. I cannot figure out to whom the checksums belongs. I downloaded all 1.6.0 > source code from Github release page while none of them matches the checksum > specified in the portfile. How can I obtain the file with the expected > checksum from Github (not from mirrors because I intend to make an upgrade > afterwhile so that I should find a way to configure checksum) The checksum you see on Github release page might have been computed using a different checksum algorithm. If you download and run the rmd160 and sha256 checksum on the package, then you should get the same checksum as mentioned in the portfile. To make this easy, when you update the Portfile you can run the following command sudo port -v checksum This will automatically calculate the correct checksum for the package downloaded from the upstream. Stay safe, Jackson Isaac
Re: QUERY FOR THE PROPOSAL
Hi Vibhansh, On Sun, Mar 22, 2020 at 11:14 PM Vibhansh Gupta wrote: > > Hi again, everyone ! > > I just wanted to ask a couple of quick questions before I hand in my draft > proposal. > > 1. Under the ‘Additional Questions’ in the GSoC Application Template on the > wiki, there’s a question asking : > > Link to any Past Open Source contributions (optional) > > I was wondering if this referred to contributions made to any open source > organisation or to MacPorts only? It is to any open source projects. > > 2. In preparing the week-by-week basis planned schedule for the project, I > was facing some difficulty to fill in upto 11 weeks. You can discuss with your (potential) mentor if the schedule looks feasible or not. Maybe they can help giving ideas to fill in the gaps > So I wanted to know : > > a) What happens if the work is completed early? What will then happen in the > remaining evaluation(s). You may consult your mentor if any pending tasks are left, if you finish early. For e.g., something from the future plans. Stay safe, Jackson Isaac
Re: Request for Information : GSoC 2020 Aspirant
On Fri, Mar 20, 2020 at 8:40 PM SAPTARSHI MUKHERJEE wrote: > > Hi Sir, > > Thanks a lot for the info provided. I've started working on the document. > Having developed some understanding and interest in the language TCL, I'm in > the process of figuring out ways of Improving the Command Line Tool UX, and > am enthusiastic to share the same by means of draft proposals. May kindly let > me know the best way to share the same; should I maintain a Google Doc > restricting the access to selected people and share over mail publicly, or > should I use a different platform for submission. > You may submit the draft on the GSoC portal. For more info check out [1] > Also if you would like me to try out some related issues and submit some pull > requests, may please let me know; I'll be glad in trying them out. > Take a look at our trac for open issues[2], you may start with easy tasks something like port update[3]. [1] https://lists.macports.org/pipermail/macports-dev/2020-March/041732.html [2] https://trac.macports.org/wiki/Tickets [3] https://trac.macports.org/query?status=!closed&type=update&component=ports&desc=1&order=time -- Jackson Isaac
[GSoC 2020] Application Template for aspiring students
Dear Aspiring GSoC Students, The application period has begun on GSoC portal. There is less than 2 weeks left for the student application deadline (31st March 2020). We recommend to add your draft proposals on the portal as early as possible, so you can get feedback from potential mentors on questions or suggestions to improve the proposal further. To help you get started, here[1] is a GSoC application template that we have used in previous years as well, feel free to use it, add or remove (sub-)sections. Also, a guideline on what we expect from a project application [2]. [1] https://trac.macports.org/wiki/SummerOfCodeApplicationTemplate [2] https://trac.macports.org/wiki/SummerOfCode#Whatweexpectfromstudentsfortheirapplications Hope this helps. Please feel free to contact us if you have any questions. Stay safe, Jackson Isaac
Re: GSoC 2020
Hi Samartha, On Thu, Mar 19, 2020 at 12:01 PM Samartha S M wrote: > > Hello Jackson Isaac > > I went through Buildbot project ideas for GSoC 2020 and this project idea > caught my attention 'Add support for running worker on non-python platforms'. > I have good experience with python and C++. Great! > I went through the project idea abstract, but still I would like to request > more resources. > Is the project about implementing only worker in C++ ? > What steps do I need to take further for a successful project proposal? > I would request the Buildbot mentors to respond to you on this :) In the meantime, you may also look at the macports-dev archive, you can find similar gsoc questions and answers [1]. [1] https://lists.macports.org/pipermail/macports-dev/2020-March/041711.html -- Jackson Isaac
Re: Saying Hello :)
Hi Mohammed Rabeeh, Welcome to The MacPorts Project! Apologies for the late response. On Fri, Feb 21, 2020 at 9:11 AM Mohammed Rabeeh wrote: > > Hello, > > My name is Mohammed Rabeeh. I'm a sophomore at the College of Engineering, > Trivandrum, India pursuing Computer Science & Engineering. I came across > MacPorts when I was going through the organization list and it caught my eye. > I have recently switched to Mac and my experience with it has been great. I > would love to contribute to MacPorts for GSoC '20. > > I have a lot of experience with web. I have been building web applications > for around 5 years now. I have good knowledge of Javascript, PHP, and Django. > I have built APIs in Django and attended a lot of hackathons were Django was > extensively used as the backend. > > I would like to work on mainly two projects, > > 1) The Django Web Application > 2) Improving MacPorts documentation, website and trac system > > I believe that my experience with web will make a really good candidate for > GSoC. I would also like details on these projects and would like to share my > thoughts and ideas with the mentor. Unfortunately, we don't have mentors available for the webapp project. Currently we have mentors that can assist you on: - Buildbot related project - Macports-base (potential mentors mcalhoun and satraul) Ideas List: https://trac.macports.org/wiki/SummerOfCode -- Jackson Isaac
Re: GSoC web-app query
Hi, Small correction below, On Thu, Mar 19, 2020 at 8:26 AM Jackson Isaac wrote: > > Hi Dandamudi, > > Welcome to The MacPorts Project! > > Apologies for the late reply. > > On Wed, Mar 18, 2020 at 1:18 PM DANDAMUDI ROHIT > wrote: > > > > Hello all, > > > > It seems the mentors alloted for web-app are busy, is there any other > > project idea I can take on? > > Unfortunately, our web-app mentors cannot continue due to the current > situation, and we support them in their decision. > > Currently we have mentors for the following projects (If I understand > correctly from Ideas list): > - Buildbot > - MacPorts base See ideas [1] where potential mentors are satraul or mcalhoun :) > > To get a better understanding of macports-base you may also see our > introductory video at [3]. > [1] https://trac.macports.org/wiki/SummerOfCode [3] https://www.youtube.com/watch?v=46qshiDskrM -- Jackson Isaac
Re: GSoC 2020
Hi Samartha. On Wed, Mar 18, 2020 at 8:19 AM Samartha S M wrote: > > I've not installed MacPorts yet. Is it compatible with Linux systems as I > have Linux based Ubuntu system? > It is possible to setup macports on linux, although it might not completely work correctly (had tried it long time ago, though). > Surely, I'll go through all resources which you have sent. > You may also look at the Buildbot project idea. -- Jackson Isaac
Re: GSoC web-app query
Hi Dandamudi, Welcome to The MacPorts Project! Apologies for the late reply. On Wed, Mar 18, 2020 at 1:18 PM DANDAMUDI ROHIT wrote: > > Hello all, > > It seems the mentors alloted for web-app are busy, is there any other > project idea I can take on? Unfortunately, our web-app mentors cannot continue due to the current situation, and we support them in their decision. Currently we have mentors for the following projects (If I understand correctly from Ideas list): - Buildbot - MacPorts base (Improving the Command Line Tool UX [1]) - MacPorts base (Update Orphaned Ports [2]) To get a better understanding of macports-base you may also see our introductory video at [3]. [1] https://trac.macports.org/wiki/SummerOfCode#color [2] https://trac.macports.org/wiki/SummerOfCode#orphanports [3] https://www.youtube.com/watch?v=46qshiDskrM -- Jackson Isaac
Re: Request for Information : GSoC 2020 Aspirant
Hi Saptarshi, On Wed, Mar 18, 2020 at 11:08 PM SAPTARSHI MUKHERJEE wrote: > > Dear Sir/Ma'am, > > I shortly started voyaging through the documentation on MacPorts, which > seemed quite interesting to me. I'm Saptarshi Mukherjee, a 3rd Year > Undergraduate at IIT Bhilai in Computer Science and Engineering, and an > enthusiast to contribute to MacPorts in GSoC 2020. Welcome to The MacPorts Project! > > In the first place, I'm absolutely new to tcl and am feeling a need to know > the language so as to have a clear understanding of the open-source codes. > Having confessed that, I'd however add that I've looked at some files, > acquired some overview, and then read some info about the issue concerning > "port reclaim". Having got some understanding of the current requirement in > that context, I hereby express my interest to contribute to that issue. I > could perceive the need to retain the build-related ports which are currently > being overlooked by the reclaim.tcl code, when checking for leaves. Apart > from that, the task of "Improving the Command Line UX" was also interesting > and seized my attention to try my hands on. You may also look at our introductory video on code base[1] for some more insights. > > Considering the fact that time is quite short with only 9-10 days remaining > for the application, I'd sincerely request for some directions on how I > should get going; whether I should read about tcl and revert with a concrete > understanding of the code, or I should try crafting and suggesting innovative > solutions (related to known data structures and relevant architectural > models) and pseudo-codes for implementations of the aforementioned tasks. Any > guidance would be highly appreciated. > If you already have a good understanding of the code and have ideas, feel free to already draft the application and submit in the portal, in this way you can get early feedback from the (potential) mentors. [1] https://www.youtube.com/watch?v=46qshiDskrM -- Jackson Isaac
Re: GSoC 2020
Hi Samartha, Welcome to The MacPorts Project! On Wed, Mar 18, 2020 at 6:20 AM Samartha S M wrote: > > Hello macports, > > I'm interested in contributing to your open source project under GSoC 2020. > I would like to learn more about the organization and projects so that I can > start preparing my proposals for the project ideas listed under GSoC 2020. > Do you already have MacPorts installed on your system ? You can find the guide at [1]. The Idea list can be found at [2]. You can either start with contributing to the core behind macports i.e., macports-base[3] or add/update existing portfiles (recipes to install packages) i.e., macports-ports[4]. To get started with contributing to macports-base, we have an introductory video[5] which will explain about the codebase very well. To jump into creating or working on existing portfile, our guide on portfile development[6] is a good starting point. You may also read existing portfile in our macports-ports repository[4]. Links: [1] https://guide.macports.org/ [2] https://trac.macports.org/wiki/SummerOfCode#Projects [3] https://github.com/macports/macports-base/ [4] https://github.com/macports/macports-ports/ [5] https://www.youtube.com/watch?v=46qshiDskrM [6] https://guide.macports.org/#development -- Jackson Isaac
[GSoC 2020] The MacPorts Project is Participating
Hi, I am happy to announce that The MacPorts Project has been accepted as an organization for Google Summer of Code 2020. Interested Mentors can reach out to mojca or ijackson (@macports.org), so that we send out the invites. Also, interested students can start working on idea proposals and interacting with potential mentors and the dev community for any help they might require. Ideas list: https://trac.macports.org/wiki/SummerOfCode#Projects P.S.: Start early, share early, ask for feedback :) -- Jackson Isaac
Fwd: [GSoC Mentors] GSoC 2020 Organization Applications are now open (and close on February 5th)
Hi, GSoC 2020 org applications are now open. Let's participate again this year, we have some ideas on wiki, maybe they need some refinement ? Also, buildbot mentors are happy to collaborate again this year with us. If any of the previous year students want to become the Org Admin/Mentor, let us know :) Regards, Jackson Isaac -- Forwarded message - From: 'sttaylor' via Google Summer of Code Mentors List < google-summer-of-code-mentors-l...@googlegroups.com> Date: Tue 14 Jan, 2020, 23:22 Subject: [GSoC Mentors] GSoC 2020 Organization Applications are now open (and close on February 5th) To: Google Summer of Code Mentors List < google-summer-of-code-mentors-l...@googlegroups.com> *Open Source Organizations* that wish to be mentoring orgs for GSoC 2020 can now apply. Orgs please remember the organization application period will close on Wednesday, February 5th. You can go to g.co/gsoc to complete your organization's application. *Students*- if you are interested in participating in GSoC 2020 *s**tudent applications open March 16-31*. The GSoC 2020 program announcement <https://opensource.googleblog.com/2019/12/announcing-google-summer-of-code-2020.html> , timeline <https://developers.google.com/open-source/gsoc/timeline>, marketing materials <https://developers.google.com/open-source/gsoc/resources/marketing> (slide deck, flyers), FAQs <https://developers.google.com/open-source/gsoc/faq>, and short videos <https://developers.google.com/open-source/gsoc/videos> about the program and tips for mentors and students are all available. Thinking about being a mentor for GSoC 2020? Reach out to the organization you'd like to work with in the next couple of months and let them know, I'm sure they'd be thrilled to have you as a mentor! We are looking forward to another exciting year of GSoC. For any questions about the programs please email us at gsoc-supp...@google.com Best, Stephanie Taylor -- You received this message because you are subscribed to the Google Groups "Google Summer of Code Mentors List" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-summer-of-code-mentors-list+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-summer-of-code-mentors-list/7ea5c97b-7467-4787-82af-5cb8c425f5d5%40googlegroups.com <https://groups.google.com/d/msgid/google-summer-of-code-mentors-list/7ea5c97b-7467-4787-82af-5cb8c425f5d5%40googlegroups.com?utm_medium=email&utm_source=footer> .
Re: AWS SAM CLI - Looking for help
Hi Björn, On Mon, Dec 16, 2019 at 2:51 PM Björn Raupach via macports-dev wrote: > > Hi there, > > would anyone mind helping me? I am not very experienced with Portfile > development and I know little about Python, which makes this all very > cumbersome (but fun). Welcome to The MacPorts Project! We are here to help :) > > I am trying to setup a Portfile for AWS SAM CLI: > https://github.com/awslabs/aws-sam-cli > > My problem is dealing with Python dependencies. I know Python people have > pip, conda and virtualenv - probably more. In MacPorts I can work with Port > dependencies: depends_build-append, depends_lib-append and so on. I just > don’t know how to put all of them together. > > There is a Port for the AWS CLI (py-awscli). I went ahead and did a lot of > copy & paste, trying to figure things out. > > I created 2 ports: py-aws-sam-cli and was-sam-cli_select. So far I managed to > download aws-sam-cli from https://pypi.org, but I end up with a runtime > exception. > > $ sam > Traceback (most recent call last): > File "/opt/local/bin/sam", line 6, in > from pkg_resources import load_entry_point > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pkg_resources/__init__.py", > line 3251, in > @_call_aside > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pkg_resources/__init__.py", > line 3235, in _call_aside > f(*args, **kwargs) > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pkg_resources/__init__.py", > line 3264, in _initialize_master_working_set > working_set = WorkingSet._build_master() > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pkg_resources/__init__.py", > line 583, in _build_master > ws.require(__requires__) > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pkg_resources/__init__.py", > line 900, in require > needed = self.resolve(parse_requirements(requirements)) > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pkg_resources/__init__.py", > line 786, in resolve > raise DistributionNotFound(req, requirers) > pkg_resources.DistributionNotFound: The 'tomlkit==0.5.8' distribution was not > found and is required by aws-sam-cli > > How to deal with missing dependencies in Python? Do I need py-tomlkit and > create a MacPorts dependency on that port? > Yes, you are indeed correct. You would need to create py-ports for any missing dependency packages e.g., tomlkit. You might have more dependencies further down. Happened when I was creating my first py-port as well :) Adding a dependency for py-port is something similar to what you have here [1]. I am not so experience with depends_build or depends_lib, but sometimes I follow trial and error, or look at other ports, how they use it. For more information on dependencies, you may look at the guide [2]. > My current work is here > https://github.com/raupachz/macports-ports/tree/aws-sam-cli > > And here is just the Portfile for py-aws-sam-cli: > https://github.com/raupachz/macports-ports/blob/aws-sam-cli/python/py-aws-sam-cli/Portfile > > > Thank you all for the time and effort that goes into MacPorts! > /Björn [1] https://github.com/raupachz/macports-ports/blob/aws-sam-cli/python/py-aws-sam-cli/Portfile#L33 [2] https://guide.macports.org/#reference.dependencies -- Jackson Isaac
Re: Developer mode
Hi Ryan, On Mon, Nov 18, 2019 at 8:57 PM Ryan Schmidt wrote: > > I wonder if we should add a "developer mode" to MacPorts -- something that > developers could enable in macports.conf. I like this idea. > > I feel that currently we print some information that is meant for developers > and is not helpful to regular users -- such as the "reinplace didn't change > anything" or "all compilers were blacklisted" warnings. > > And there is a lot more information that we could print that would be useful > to developers but that we don't print because it would be overwhelming to > regular users. We introduce new features, such as "compiler.cxx_standard > 2011", meant to replace old methods like "PortGroup cxx11 1.1", yet we have > no way of nudging developers to adopt these new features, short of the > laborious process of manually searching out the ports and filing tickets or > fixing it ourselves. If MacPorts could automatically nudge developers about > these issues as they're updating their own ports, that could be helpful. > > In "developer mode", "port lint" or other checks could be run as part of > every install. > > With this switch in place, over time, we could further streamline the regular > non-developer user experience further, such as by reducing amount of (to the > user probably irrelevant) output produced by installing or upgrading a port. > -- Jackson Isaac
Re: Interested in contributing to macports
Hi Gaurav, Welcome to The MacPorts Project! On Sun, Nov 10, 2019 at 10:01 AM Gaurav Punjabi wrote: > > Hey, I'm Gaurav Punjabi. I'm currently pursuing a Bachelors Degree in > Computer Science. I'm interested in contributing to MacPorts. But I'm a > little bit confused on where to start. Do you already have MacPorts installed on your computer? Also, do you have a MacOS system or Linux ? You can either start with contributing to the core behind macports i.e., macports-base[1] or add/update existing portfiles (recipes to install packages) i.e., macports-ports[2]. To get started with contributing to macports-base, we have an introductory video[3] which will explain about the codebase very well. To jump into creating or working on existing portfile, our guide on portfile development[4] is a good starting point. You may also read existing portfile in our macports-ports repository[2]. There are also web app[5] and buildbot[6] based projects you may look into. And if interested in something more, we have Universal Packaging Tool based project[7] Hope this gets you started and help in making your first contribution to MacPorts :) Links: [1] https://github.com/macports/macports-base/ [2] https://github.com/macports/macports-ports/ [3] https://www.youtube.com/watch?v=46qshiDskrM [4] https://guide.macports.org/#development [5] https://github.com/macports/macports-webapp [6] https://github.com/macports/mpbb [7] https://github.com/macports/upt-macports -- Jackson Isaac
Re: Wrapping up Xcode project
On Sat, Aug 10, 2019 at 7:21 AM Satryaji Aulia wrote: > > Hi all, > > I just finished building from source 348 ports without Xcode on my > 10.13 machine (only CommandLineTools). Only around 10 ports failed to > build and we know exactly why (mostly xcode 1.0 ports or dependency). > We recently discovered and/or fixed some bugs with ports like qt5, > devel, and marked ports that need xcodebuild but haven't yet like > SourceKitten. > > With the changes we made throughout the Xcode project, using MacPorts > without Xcode is now a much more pleasant experience, a major UX > improvement over the current release I just setup macports-base from master (on a fresh macOS) and I didn't notice any issues or didn't even realize that I required XCode (which I rarely use). A great UX improvement indeed. Kudos to the student and mentors working on this. > I'll be wrapping up the project with more quality assurance and > testing. It is appreciated if you guys can try out and test the latest > master (especially for old macOS versions) BTW, I tested this on latest Mojave. > > Thank you > > Sat -- Jackson Isaac
Re: New MacPorts ports database site
On Fri, Aug 23, 2019 at 8:16 AM Mojca Miklavec wrote: > > On Mon, 19 Aug 2019 at 06:17, Joshua Root wrote: > > > > MacPorts' new ports database is live at <https://ports.macports.org/>. > > I would like to ask for an opinion. > > Please compare > https://ports.macports.org/maintainer/github/ryandesign/ > and > https://ports.macports.org/ports/variant/universal > > In the first URL subports are grouped. Which one do you like better, > or do you have any ideas for further improvements? I liked the first one. I found it easy to see the subports and also to read the list of ports as compared to second one. Although I felt the spacing between rows were a bit further apart (in first one), and in second one there were back to back. Maybe spacing can be modified in somewhere between these two ? Not too far but not also back to back. I am not expert of pixel values but something like 2px might look better ? Also the first column is too wide, maybe a small dropdown arrow kind of symbol would be sufficient. > I initially asked for grouping of subports, but I cannot decide if it > actually looks better or not. > > I would prefer to have consistent output for all the queries rather > than use a different view for the maintainer. > > You can either answer here or "misuse" the following PR >https://github.com/macports/macports-webapp/pull/101 > > Thank you, > Mojca -- Jackson Isaac
[GSoC] Staying Connected on IRC - Workaround
Hi All, especially GSoC students and aspiring GSoCers, TLDR; Stay connected on IRC forever: https://vijaikumar.in/keeping-your-irccloud-client-always-connected-for-free-82db71b3cff3 As we all know that this is that time of year, when students and mentors work on GSoC projects, it is very important to have a proper channel for communication with the community. This year, we are evaluating different platforms like Zulip, Discord, Gitter, etc. so that students and mentors are able to see the chat history (unlike IRC, where only chats while connected are seen), github sync, and other cool features without premium memberships or shelling out $$$. At the same time, we don't want this to create communication gap, since not everyone are active and are on these new platforms. As a workaround, to stay connected, you may use IRCCloud, which keeps you connected for few hours after you disconnect. To stay connected forever, there is detailed steps at [1]. [1] https://vijaikumar.in/keeping-your-irccloud-client-always-connected-for-free-82db71b3cff3 -- Jackson Isaac
Re: Slack-like chat (also for GSOC)
On Sat, Jun 15, 2019 at 2:03 PM Rainer Müller wrote: > > On 14.06.19 13:01, Nils Breunese wrote: > > > > Chris jones wrote: > > > >> ( The main problem I have, is not something specific to Riot or whatever > >> forum we use, but more we need to perhaps give some thought to the > >> channels. Currently there is really only one, which gets (some) chat but > >> also messages for each and every commit. I don't think the average user > >> needs to see each and every commit. I think we probably need to split > >> these, for instance into Dev and User channels, to match the mailing lists > >> perhaps. ) > > > > I’d go even more granular: create a dedicated channel for commits and > > everyone can decide whether to follow that or not. > I am not sure how useful such a dedicated channel would be if only > automated messages will be posted and no discussion takes place. > Sometimes the mplog messages are even used during conversations, like > "see this commit, now it is fixed". > > For those that really do not want to see these messages, I would > recommend to add mplog to their your ignore list. That works in IRC > clients and also in Riot. > > The bot is operated by me, but if others also think that the bot is > annoying, I do not insist on keeping it running or moving it to another > channel. I like the mplog on #macports. If someone doesn't like it, I would say they put it in their ignore list. IIRC, we did try to create a separate channel for #macports-gsoc but then after some time we ended up in #macports, because there were more users out their who could and would like to share ideas. Splitting of channels, IMHO, might not be a good idea. It works fine as a separate Mailing list, but maybe not on IRC. I do agree, that one might get lost in all the chatter that might happen all at one place, but yeah that is same in most of the platforms, at least the ones that I have used. I do like the idea of threads (in slack), maybe we need to look if they are in some libre/open-source alternative ? -- Jackson Isaac
Re: Slack-like chat (also for GSOC)
On Thu, Jun 13, 2019 at 8:04 AM Mojca Miklavec wrote: > > Hi, > > As a quick feedback: Gitter doesn't seem to be mature enough, so that > those of us who kept testing it (for about three weeks) would want to > use it in the long run. > > * The Android app constantly keeps crashing. > * Even if it is not crashing, I wasn't able to configure it to get > notifications when a new message arrived that I would want to see it. > * Browser updates sometimes work, sometimes not. Very often one needs > to keep refreshing the browser and hope that something works > (sometimes the contents disappears completely). > * Channels are very tightly bound to git repositories, but unless you > sell your soul to the plugin, it seems hard to configure it properly, > and we never got it working once we migrated the github repository to > a different address (not that we tried that hard, but we did try). > * Functionality is very limited. > * No topics. > * I was subscribed to another channel with heavy traffic that I'm not > really interested in that much other than maybe checking it once per > week. Once I allowed notifications from the app (I did that under > Windows) to be able to respond to the student faster, I started being > bombarded with messaged from the other channel, and I was unable to > silence them until I completely removed the channel. And even then I > kept getting email two days later about the new posts in that channel. > * Receiving a bunch of emails reminding me of content that I have > already read two days ago. > > While it is very easy to initially set up, it is just not yet worth > considering as a serious platform to "replace" our official > communication channel. > > What should we try next? > Alternatives to IRC that I use (at work and tried at other projects) are Discord, Slack and MS Teams. Not too many options that I have explored, so did a quick google and found [1]. I would say we can try Riot (also mentioned earlier by Rainer), as I see lot of pros put up for it in [1]. We can also explore discord as an option. If none works, we can stick to IRC. [1] https://www.slant.co/options/4557/alternatives/~irc-alternatives -- Jackson Isaac
Re: Feedback request regarding speed optimisations in trace mode
Hi Mihir, On Thu, Jun 13, 2019 at 8:40 AM Mihir Luthra <1999mihir.lut...@gmail.com> wrote: > > Hi, > >> >> I would like to see the time for each run (if 10 runs, then 10 columns >> i.e., xx_run1, xx_run2, ...), rather than only average of them. >> >> Collect as much as insights we could, maybe we find some pattern or >> something that might help us (not sure what though). Since I have a >> feeling, we might get better performance in one run and not so good in >> another. > > > Thats true, that’s what troubling me the most. Before testing I read on stack > overflow that sys+user time is always correct, > but the most disturbing factor was that same port gives results significant > differences on multiple runs. Like in case of gettext + reps, sometimes I get > time as high as 13 mins and sometimes 11:30. Differences are also noticeable > in sys and user times. > Also I always made these tests on a completely new installation of the base. >> >> >> I notice that some ports take less time with modification and some >> ports take more time. Just want to make sure it happens in multiple >> runs. > > > I have made some more improvements since the last time, This time will make > tests on every port for 10 times and upload on spreadsheet. Not necessary to stick to 10 runs, just because I said so. It can be even 3 or 5 runs. Whichever you feel seem to be good enough to give some insights. E.g., you might feel that after 3 runs you are getting constant time and not much difference, in another case you might get all different values even on running it more than 3-5 times. >> >> >> In an ideal scenario, I would prefer a clean environment (can be a >> fresh install of OS, bare minimum apps running, reboot before each >> run, etc.) to run each test (containers maybe? or some CI like travis) >> which might not be affected by other processes running in background. >> > I didn’t reboot the system last time when I tested, but I had all my apps > closed and only 2 tabs open in terminal, 1 for modified base and 1 for > original. Also I didn’t make any runs simultaneously. This time I will reboot > after each run, but testing like that for sure Is gonna take some days for a > good number of ports. > Fresh install of OS probably would be hard for me, can’t it be like a guest > user. > These were just some random thoughts I had. Not necessary to stick to these or follow each and every one. Just try different ways. Guest user might be a good option (not sure though). I would say if these things (i.e., reboot/fresh install of OS) impact the timeline if you end up running tests for several days or weeks, I would say then just run acceptable number of tests and when you feel 'Ya, this is the sweet spot', you may skip extensive tests (like rebooting system for each and every port 10 times or so). Also, I would rather not do fresh install of OS on personal laptop each time I want to test a port. I was thinking more on terms of a Sandboxed environment or a VM(?) which has same setup and resources on each run, and which can be easily spinned up and deleted (in matter or minutes, in parallel, or whatever). Like a cloud platform as a service kind of thing, if it helps. It's easier if you can run these tests on Linux, since cloud has linux servers, but I don't believe major cloud providers provide MacOS VM's or anything of that sorts. -- Jackson Isaac
Re: Feedback request regarding speed optimisations in trace mode
On Sun, Jun 9, 2019 at 6:01 PM Mihir Luthra <1999mihir.lut...@gmail.com> wrote: > > Hi jan, > >> >> How exactly were these numbers obtained? Is it one run? >> An average of ten runs? All following a complete distclean? >> Is it the "real" time as reported by time(1) or somethin else? >> What are the other times reported by time(1), as in >> >> $ time sleep 5 >> 0m05.01s real 0m00.00s user 0m00.00s system > > > The time I sent that mail, I was mainly testing same ports repeatedly to rule > out the bugs. So I just took an average of them. I would like to see the time for each run (if 10 runs, then 10 columns i.e., xx_run1, xx_run2, ...), rather than only average of them. Collect as much as insights we could, maybe we find some pattern or something that might help us (not sure what though). Since I have a feeling, we might get better performance in one run and not so good in another. I notice that some ports take less time with modification and some ports take more time. Just want to make sure it happens in multiple runs. In an ideal scenario, I would prefer a clean environment (can be a fresh install of OS, bare minimum apps running, reboot before each run, etc.) to run each test (containers maybe? or some CI like travis) which might not be affected by other processes running in background. -- Jackson Isaac
Re: Enabled commenting on GSoC Proposal
On Tue 2 Apr, 2019, 21:07 Mihir Luthra, <1999mihir.lut...@gmail.com> wrote: > >> Mihir, >> >> The proposal is view-only. You might need to give comment-access for >> us to leave feedback on the draft. >> >> Done > Try to avoid creating multiple mail threads. Thanks >
Re: Request to help potential GSOC students
Hi Mojca, On Fri, Mar 29, 2019 at 3:55 AM Mojca Miklavec wrote: > > Dear MacPorts users & developers, > > You probably noticed a slightly increased traffic on this mailing list > recently. > Really appreciate your emails and response to the GSoC students :). > GSOC is an amazing opportunity for the students to learn something > new, and for the MacPorts community to greatly benefit from their > work. Last year we had almost no applications, while this year we seem > to be "bombarded" compared to the number of workforce available. > > I would be really grateful to get some helping hands reviewing student > proposals and answering their questions. While not everyone of us is > heavily skilled in every aspect of the code, some of the proposals are > pretty generic, easy to understand and could greatly benefit from your > feedback. I have added my feedback to the proposals which I had access to. > > The deadline for the final submission is the 9th of April. > > Proposals that we received so far: > > === MacPorts Base > > * Speed up trace mode by Mihir Luthra > https://docs.google.com/document/d/1qH5VMtrQ3tvd5gFPf51lmJtd6dYfUuEmO1AvXmU_4qM > Mihir, The proposal is view-only. You might need to give comment-access for us to leave feedback on the draft. > === Web / Buildbot projects > > * Custom Views Plugin for Buildbot by Rajdeep Bharati > https://docs.google.com/document/d/12wRjA8sOWNOuApHZ_fm0n1aIPLVPt9Xm2yGiMwiK3AI > > * Web app for port info, build and installation stats by Arjun Salyan > https://docs.google.com/document/d/198Ivygxb2NJQz_sqzDrbDPVEYZ5Ye5Yw0LV6Bt2QmG4 > -- Jackson Isaac
Re:
Hi Rishab, Welcome to The MacPorts Project! On Sat, Mar 16, 2019 at 3:13 PM rishab lamba wrote: > > Dear Sir/ Ma'am, > I am Rishab Lamba pursuing my B.Tech from BVCOE, Delhi. I got to know about > MacPorts from the GSoC program and wish to learn to contribute to its > platform. I have read the MacPorts Guide and have made myself comfortable > using the environment but am still a little ambiguous of how to contribute to > the source code. > So if you could help me how and where to start from, what is the knowledge > base or the prerequisites that would be required from me? I would really appreciate any help or guidance that I could get > Good to hear that you have gone through the macports guide and familiarised yourself. Have you installed macports on your machine ? Also, do you have a mac machine or linux machine? You can either start with contributing to the core behind macports i.e., macports-base[1] or add/update existing portfiles i.e., macports-ports[2]. To get started with contributing to macports-base, we have an introductory video[3] which will explain about the codebase very well. To jump into creating or working on existing portfile, our guide on portfile development[4] is a good starting point. You may also read existing portfile in our macports-ports repository[2]. Hope this gets you started and help in making your first contribution to MacPorts :) Links: [1] https://github.com/macports/macports-base/ [2] https://github.com/macports/macports-ports/ [3] https://www.youtube.com/watch?v=46qshiDskrM [4] https://guide.macports.org/#development -- Jackson Isaac
Re: Online meeting today at 15:00 UTC (in 4 hours)
On Sun 13 Jan, 2019, 15:59 Umesh Singla On Sun, Jan 13, 2019 at 3:21 PM Jackson Isaac > wrote: > >> On Sun 13 Jan, 2019, 14:52 Umesh Singla > >>> Thanks for the summary. >>> >>> Also, were we able to decide on the GSoC-admin? I have put the call for >>> mentors email for now to avoid further delays. But let's decide soon, so we >>> have someone actively looking into it. >>> >> >> Umesh, since you showed interest in being the admin again, I would say >> you can go ahead and be the org admin. Hope to get in responses soon from >> potential mentors. >> > > Okay, but I was really hoping you'd be willing to take this up, and if > possible, I'll start looking into base once in a while and help out the > newcomers get started on base or infra projects. Also, with the new job, I > delay considerably replying to the emails which could affect the > application process. > Sure. I'll take up the admin role then, in case we have sufficient mentors.
Re: Online meeting today at 15:00 UTC (in 4 hours)
On Sun 13 Jan, 2019, 14:52 Umesh Singla Thanks for the summary. > > Also, were we able to decide on the GSoC-admin? I have put the call for > mentors email for now to avoid further delays. But let's decide soon, so we > have someone actively looking into it. > > Umesh, since you showed interest in being the admin again, I would say you can go ahead and be the org admin. Hope to get in responses soon from potential mentors. > On Sun, Jan 13, 2019 at 12:56 AM Mojca Miklavec > wrote: > >> Hi, >> >> Here's the summary of today's meeting. >> >> === Next online meeting >> >> Scheduled two weeks from now (January 26th), with the stress on GSOC. >> We'll adjust the timing based on requests to join from USA or >> Australia, please raise your hands if you want to join. >> >> === MacPorts Meeting 2019 >> >> We shortlisted some dates (Saturday - Wednesday): >> - 6.-10. April >> - 11.-15. May >> - 8.-12. June >> Aljaž is suggesting June to hopefully get nicer weather, potentially >> the ability to go swimming etc. >> >> The idea is to organize the meeting in Trieste, Aljaž will try to find >> a suitable place to stay. If you would like to join, please cast the >> vote for your favourite date. If none of those dates suit you and you >> would like to join, please let us know. >> >> === Google Summer of Code >> >> * We are looking for volunteers to mentor the students. >> * We would probably not participate with more than one or two >> projects, but we will only apply if we get sufficient interest from >> potential mentors (ideally those who know the base). >> * Me and Umesh could guide a student working on buildbot or webapp, >> but that's not sufficient on itself to apply. >> * Jackson would require hardware to be able to help more :) >> * We need to attach "sample tasks" to all the ideas that we are >> suggesting to students (for screening the students for their fitness >> to work in GSOC). >> >> === Software Freedom Conservancy >> >> We discussed joining SFC. I sent an email to the PortMgr, but that >> list is slightly quiet :). >> We will repeat the initiative on this mailing list. It could be nice >> to try if we could get some co-funding for the meeting. >> >> === Travis >> >> * Zero recently made quite some improvements to our bot & Travis >> infrastructure. Thank you very much! >> * Private repositories for binary packages are now used. >> * Packages are always built from source. >> * Obsolete packages are no longer scheduled for build, just to fail >> anyway. >> * Some improvement in the bot. >> * He is looking for some further suggestions that could improve our >> experience. >> * (My not-too-serious suggestion was to ping participants after two >> weeks of no activity, to simplify Perry's life :) >> * Zero was thinking of starting to work on a script that could >> automatically update port version based on livecheck results and >> automatically create a pull request. This would be a very welcome >> addition. >> * My question was whether we could also automate revbumping >> dependent ports, but this is slightly more challenging. >> * Zero is looking into the other tickets (four tickets are currently >> open) and into automating releases. He asked if someone (Clemens?) >> could create an account on Bintray, but he'll send the details over >> the mailing list. >> * Zero asked if it was possible NOT to result in an error in "port >> test" when a port doesn't have any tests defined. At the moment he >> cannot enable running tests on Travis since that would almost always >> result in a failure when the port didn't implement that functionality, >> even if there was sufficient time left to run the tests. >> * Rainer promised to create ticket for base to support "port bintest" >> which could test something like "binaryname --version" or do some >> other simple test to check whether a port is working after it's being >> installed. This could also be a potential GSOC task, even though too >> small all by itself. >> >> === MacPorts base >> >> (Looking for volunteers to rewrite the base to python to gain more >> contributors :) :) :) >> Jackson will start drafting some introduction to programming MacPorts >> base. >> >> === Participants (in order of appearance) >> >> * umeshksingla (Umesh) >> * mojca (Mojca) >> * g5pw (Aljaž) >> * l2dy (Zero) >> * raimue (Rainer) >> * ijackson (Jackson) >> >> Thanks to everyone for participation, even if the schedule was a bit >> messy today, sorry for the confusion :) >> >> Mojca >> >> >> On Sat, 12 Jan 2019 at 12:01, Mojca Miklavec wrote: >> > >> > Hi, >> > >> > I think I first messed up the addition and subtraction in time zones >> > (last time it was apparently at 13:00 UTC), and then with sending out >> > the email yesterday under the wrong address. I wanted to ask if there >> > were any participants from the far east or west who wanted to >> > participate, in that case we could shift the hour, but since we only >> > had people from UTC+1 and UTC+5.5 who raised their
Re: Online MacPorts meeting? This Saturday?
Hi Mojca On Tue 8 Jan, 2019, 19:08 Mojca Miklavec Hi, > > This is slowly getting more and more urgent ... :) > > One week from now applications for GSOC start, and we still didn't > manage to call an online meeting. Any chance we do it this weekend? > > Topics: > - Google Summer of Code > - Meeting in 2019 > - Software Freedom Conservancy > - Review open pull requests and roadmap for base > - anything else: please propose > I am in for the call this Saturday. I would also like to discuss about Gsoc. Hope we can schedule something (even if we have interested admins and mentors would be enough) :) > >
Re: Online meeting next Saturday?
On Sat, Oct 27, 2018 at 1:42 AM Mojca Miklavec wrote: > > Hi, > > So: any interest for a meeting tomorrow, or a better suggestion for the date? > I am good with tomorrow. In November, I will not able to join the meeting. Let's see if we have other developers agree for tomorrow as well. The topics for discussion are interesting :) Thanks for taking the initiative. -- Jackson Isaac
Adding a Code of Conduct to MacPorts
Lately, I have seen open source projects have started adopting Code of Conduct. [1], [2] I think it is a great step to keep the open source community healthy and welcoming to everyone. I would like to know what other developers think about this. Also, who would be the decision makers (PortMgrs?) Reference: [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/code-of-conduct.rst [2] https://lwn.net/Articles/765332/ Kind Regards, Jackson Isaac
Re: How are other dev's filtering macports mail?
On Wed, Jun 6, 2018 at 1:23 AM, Daniel J. Luke wrote:
> This may be something that would be useful to put in the wiki, but I thought
> I'd ask on list how other committers deal with the large MacPorts email
> volume. The way I've been doing it for many years doesn't work anymore (I
> missed notification of a PR because it looks like github sends me one copy of
> a notification with List-Id set even though it shows me on the CC line).
>
> For the longest time, I've just done filtering on List-Id into list-specific
> mailboxes, so messages directly to me (or that CC me) end up in my inbox like
> normal [Note that this still works just fine for trac tickets]. I could do
> matching on list-id but add an exception for when I'm CC'd (which may work),
> but could also miss some mail.
>
In Gmail, I have added to the filter something like the following -
subject:(macports-tickets Digest)
list:"macports-tick...@lists.macports.org" -{ijack...@macports.org}
Even I used to not get PR replies, mentions, etc. in my Inbox unless I
click on the folder.
Then I added a "-{}" along with list-id and not if I am
mentioned or part of the
github PR conversation, I get the email in my mailbox rather than the folder.
--
Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
On Tue, May 8, 2018 at 10:47 AM, Mojca Miklavec wrote: > > 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 entered. > > > > Tried many ways.. > > > > If you have any suggestions do let me know. > We can even try firebase for the DB backend and host the frontend on heroku. Firebase free version gives 1GB of storage and 10GB of bandwidth per month. I guess for testing out the app on complete portindex we could give it a try. https://firebase.google.com/pricing/ Then again we would have some kind of limitations over here in long run. > > I was pretty sure that we would reach the database limit here. > > > This site > https://devcenter.heroku.com/articles/heroku-postgres-plans > says that the limit is 10k rows which is not anywhere near enough and > fully consistent with your observation. The plan that lets you have > 10M rows is 9 USD per month which I gladly pay if that would solve the > issues (I'm not sure if those are the only ones, we might not have > sufficient memory etc.) > 9USD is only for the DB though. We might need to pay for the compute separately. Looks like free VMs come with only 512MB RAM. > > (I also remembered that I might have access to create a clean virtual > machine, but I need a couple of days to physically reach a place where > I have the additional info. That would require setting up the whole > machine manually of course, but we need to do that for the final > deployment anyway.) > > > I think i have to break the data entry in separate chunks and do it. But not > > sure how to do that. > > In any case Heroku will apparently not let you import the full > database anyway until we switch to a payed account. If you still have > troubles with performance issues afterwards, this also won't help. > What you could do is temporarily copy or move a few folders (say, > math, science and python) and run portindex just on those. This will > give you a smaller number of ports to work with, but still sufficient > to figure out what other issues you'll need to deal with (port listing > will have to be paginated etc.) > > It's a good exercise to know what the limitations are. When you play > with new features and database design, it's always easier to play > with, say 10-100 ports than with full 15 MB portindex file. > This plan sounds good. +1 -- Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
Hi Vishnu, On Tue, May 8, 2018 at 12:01 AM, Vishnu wrote: > Hello > > Thanks for the repository link. > > so my current email should be added as the collaborator for me to > contribute right? > or should i use the new macports id. > I don't remember exactly but I guess yes, you would need to be added as a collaborator to start contributing to the repository. In the meantime, feel free to push your code to your local repository. in that case do i have to make a new account or what? > not clear about that.. > > No, you just add the macports email id to your existing github profile (See Links:[6] at the end). You would also want to update your git config (you could use --local to keep the config local to the directory that you are working on) to use your macports id though. See: https://trac.macports.org/wiki/WorkingWithGit#setup > Also writing down some points we discussed for the community to know : > > 1) make the repository- already done. > 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. > 3) Set milestones in github. > 4) Learn about unit tests > To know more about unit tests in brief I found a brief answer on SO [1]. You can find a detailed article on Tutorials point [4] and wikipedia [5]. > 5) Really try to implement API feature. > It would help to come up with a simple design on what the API would do. This would help you during the coding phase. We can always refine it as we progress. 7) Discuss about what commit needs to be shown on the port page. > As discussed, we could keep this topic for discussion at a later point of time. > 8) Add columns for port and intended OS , Port and build possible OS > Thanks for documenting the points discussed. I have added some of my thoughts inline. > > jackson i would require the milestones page you talked about. > > I was talking about something like [2]. To get more idea about milestones, you can refer [3]. Links: [1] https://stackoverflow.com/a/3258768/1970068 [2] https://github.com/pypa/warehouse/milestones [3] https://help.github.com/articles/about-milestones/ [4] https://www.tutorialspoint.com/software_testing_dictionary/ unit_testing.htm [5] https://en.wikipedia.org/wiki/Unit_testing [6] https://help.github.com/articles/adding-an-email-address-to- your-github-account/ -- Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
Hi Vishnu, On Mon, May 7, 2018 at 12:22 AM, Bradley Giesbrecht wrote: > > On Apr 30, 2018, at 10:34 AM, Joshua Root wrote: > > > > On 2018-5-1 02: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? > >>> > >>> > >> > >> I was thinking about macports-portstatistics or macports-portstats. > > > > This is going to cover more than just stats; it's intended to fill the > > role that was envisioned for MPWA, so I think it would be appropriate to > > use that name. > > macports-webapp? > > New repository for GSoC 2018 - macports-webapp is set up now. It is accessible at [1]. Let us know if you have any queries. You would also require @macports id. I'll send a follow up mail on the thread. Links: [1] https://github.com/macports/macports-webapp @neverpanic, thanks for the quick help :) Regards, Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
Hi Vishnu, On Sun, May 6, 2018 at 3:52 PM, Vishnu wrote: > Hello > > Sorry for being inactive. > Had back to back exams . > > Got free today. > > I implemented a new search feature in my app . > Pushed the changes to heroku too. > Please go through : > sleepy-wave-33400.herokuapp.com/port/ > > There you can search any port with its name. > Even just starting few characters would work. > > The search seems to be case-sensitive. For e.g., I entered 'app' but didn't get any matches whereas I had to enter 'App' to get some matches that too that begin with the entered text. It doesn't look for App in between the portname i.e., 'BGHUDAppKit' Also it would be great to populate the DB with the complete portindex. The installation statistics did you fetch from mpstats or manually entered some values ? Looks like they are from 2012. IIRC, your exam gets over tomorrow i.e., 7th May 2018 ? It would be great to setup an introduction meeting with mentors and student. I am okay with setting up a meeting any day after 1630 UTC (2200 IST). I would not be available the coming weekend i.e., from 10th May to 14th May. -- Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
On Mon, Apr 30, 2018 at 10:06 PM, Vishnu wrote: > Hey > > Repository names: > MacPorts-features? > Macportsinfo? > Or just simple > gsoc18? > > I was thinking about macports-portstatistics or macports-portstats. > > I will look into the feedback. > Also i am currently using create. > > And also in the long term. Parser would be run only once in forever or say a > year. If we run the parser once a year, wouldn't it be outdated pretty soon ? > And before running the original db must be cleared. > > And then obvious question arise. What if a new port is added in macports. > You are on a right path I would say. We would want it to update after every port is added/updated and built. > For that i would like to know the mechanics of new port addition. > > I think before the new port is added. It is obviously built before right? So > maybe we can add some code there to update the table with a row when new > port is added. When a port is submitted, it is built by Travis CI and also our buildbots, which builds the port for mac 10.6 to 10.13 versions and gives the build status. We would be more interested in the status provided by the buildbot. There could be a trigger or a listener which runs whenever a build job is initiated and then updates the DB on completion. I believe there would be some mechanism to know the status of each job. Maybe someone more familiar with buildbot could share some insights ? > > Just brainstorming. > > > Thanks > > On Mon, Apr 30, 2018, 2:23 PM Mojca Miklavec wrote: >> >> 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 repository and >> populate it, to simplify further work. >> >> > Here all the ports are listed: >> > sleepy-wave-33400.herokuapp.com/port/ >> > >> > When you'll open the page..probable the ports would not be there because >> > i >> > cleared the DB. >> > >> > To add the ports info into DB..we need to open this url: >> > sleepy-wave-33400.herokuapp.com/port/parser >> > >> > Parsing is done using the portindex.json i have. >> > For simplicity i have only 6 portfile data in it. >> > >> > Once you open sleepy-wave-33400.herokuapp.com/port/ >> > you can click on individual port to get further informant about that >> > port. >> > infact u can access this information using : >> >> Cool. Some feedback: >> - the css should go to a separate static file >> - allowing port id might be a bad idea because there might be a port >> called "123" >> - calling parser multiple times populates the database with multiple >> copies of the same port, you should use something like >> "create_or_update" >> - we need to figure out the best way to call the "parser" >> >> I might have a few other comments, but the initial purpose was to >> check if we have an easy way to deploy the development version and >> this has been achieved. >> >> Please come up with proposal(s) for project name, so that we can make >> an explicit request to the infrastructure team to create a new repo. >> >> Random brainstorming ideas: webapp, "port guardian" (in whatever >> spelling), ... >> >> Mojca -- Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
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 > repository and put all the documentation / plan / milestones / sample > page etc. to that repository. > This means: > - deciding for the name We can go with something like 'macports-buildstatistics' for repo name. If it would be a branch under /macports-base then 'gsoc18-buildstatistics'. Although having another repository under /macports makes more sense, since the project would be unrelated to what macports-base does. > - asking someone with permission to create a repository inside > macports org (and make sure that Vishnu has commit rights on that > repository) I believe the PortMgr would be able to create the repository for us ? I don't have the sufficient permission to create repo under /macports is what GitHub tells me. As for commit rights, I had sent out an email on 26 April for getting @macports id for Vishnu. Vishnu, Could you please search for 'Request for macports id for GSoC 2018 student' thread in your mailbox and reply with your preference for the username ? > - deciding how exactly this should be done > > I suggest to do most of development in a separate development branch > and make sure that whatever ends up in master gets a review. Or > something similar. We need a way to distinguish reviewed code from > playground. > Having separate branches for testing and playing around sounds good to me. We can then cherry pick the commits and have reviewed code on master. -- Jackson Isaac
Re: Strange behaviour of trace mode in MacPorts 2.4.3 / 10.13
On Sun, Apr 29, 2018 at 1:25 PM, Mojca Miklavec wrote: > 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 sometimes when my network was not good >> enough. > > We are in fact in the middle of nowhere with hardly-working internet > connection (and super happy if the GSM network works enough to make a > phone call, any data transfer is hopeless), but I don't understand how > that could have affected > dyld: warning: could not load inserted library > Missing something in depends_lib probably ? But I am not sure. Well looks like it is not provided by any port. I am guessing it is an internal library ? "$ port provides /opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib /opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib is not provided by a MacPorts port." While working on acl2, I was getting an error for library not found while running in trace-mode (didn't throw the error in non trace-mode). But this is something different and unrelated issue. I might not be able to give correct solutions. -- Jackson Isaac
Re: Strange behaviour of trace mode in MacPorts 2.4.3 / 10.13
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 sometimes when my network was not good enough. On Sun, Apr 29, 2018 at 1:04 PM, Mojca Miklavec wrote: > 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/macports/lib/darwintrace1.0/darwintrace.dylib' > into library validated process because no suitable image found. Did > find: > /opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib: code > signing blocked mmap() of > '/opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib' > /opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib: > stat() failed with errno=1 > dyld: warning: could not load inserted library > '/opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib' > into library validated process because no suitable image found. Did > find: > /opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib: code > signing blocked mmap() of > '/opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib' > /opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib: > stat() failed with errno=1 > Apymol > Apymol/data > Apymol/data/pmg_qt > Apymol/data/pmg_qt/icons > Apymol/data/pmg_qt/styles > Apymol/data/pymol > Apymol/data/pymol/icons > Apymol/data/pymol/matrices > Apymol/data/startup > Apymol/data/startup/lightingsettings_gui > Apymol/data/chempy > Apymol/data/chempy/sidechains > Apymol/data/chempy/tinker > Apymol/data/chempy/fragments > svn: E175002: REPORT request on '/p/pymol/code/!svn/me' failed > Command failed: 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 > Exit code: 1 > Error: Failed to fetch pymol: Subversion check out failed > Error: See > /opt/local/var/macports/logs/_path_to_macports-ports_science_pymol/pymol/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets to report a bug. > Error: Processing of port pymol failed > > Mojca -- Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
Hi Vishnu,
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/mpstats show
> Would submit the following data to
> http://stats.macports.neverpanic.de/submissions:
> {
> "id": "cc545acb-3f3b-4a93-afbd-8a72ef5e50b9",
> "os": {
> "macports_version": "2.4.99",
> "osx_version": "",
> "os_arch": "i386",
> "os_platform": "linux",
> "build_arch": "",
> "gcc_version": "5.4.0",
> "xcode_version": "none"
> },
> "active_ports": [
> {"name": "ncurses", "version": "6.1_0"},
> {"name": "libedit", "version": "20170329-3.1_2"},
> {"name": "mpstats", "version": "0.1.7_0", "requested": "true"}
> ],
> "inactive_ports": []
> }
> root@vishnupc:/# /opt/local/bin/port-tclsh /opt/local/libexec/mpstats submit
> Submitting data to http://stats.macports.neverpanic.de/submissions ...
> Success.
>
That's great :) But looks like the mpstats page [1] didn't add Linux
to the statistics.
This is most likely due to the reason that mpstats only checks for mac
OS version ?
Try to find a way to read Linux version if the installed os is not darwin based.
Though 'os_platform' does say 'linux'. Probably the statistics code
[2] doesn't recognize
linux as a platform ?
[1] http://stats.macports.neverpanic.de/os_statistics
[2] https://github.com/macports/macports-base/tree/gsoc11-statistics
--
Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
Hi Vishnu, 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 mpstats > Port mpstats contains: > /Library/LaunchDaemons/org.macports.mpstats.plist > > /opt/local/etc/LaunchDaemons/org.macports.mpstats/org.macports.mpstats.plist.default > /opt/local/etc/macports/stats.conf > /opt/local/libexec/mpstats > > Mojca you said there will be a change in os statistics > (http://stats.macports.neverpanic.de/os_statistics#os_platform) . > I couldn't see any change. > When you run 'port contents ' it lists you the files that are installed by that port. Here you would want to run '/opt/local/libexec/mpstats'. Basically it shows me two options. But I would like you to explore the command and let us know what you infer from them :) If I give out the exact command you might not be able to try out other commands available. -- Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
On Thu, Apr 26, 2018 at 1:02 AM, Vishnu wrote: > these are the errors. > > On 26 April 2018 at 00:59, Vishnu wrote: >> >> Yes I did add 'revupgrade_autorun no' line to >> /opt/local/etc/macports/macports.conf >> with sudo.. >> I cross checked it..it has been updated. >> It's been quite some time I have touched Ubuntu. From Joshua's mail and your logs I understand that macports user was not created. Could you try running $ sudo addgroup macports $ sudo adduser macports macports I am not exactly sure though if the group name is correct or not. Let us know if you still get the same errors after following these steps. -- Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
Hi Vishnu, On Thu, Apr 26, 2018 at 12:33 AM, Vishnu wrote: > anyone? > > On 25 April 2018 at 21:49, Vishnu wrote: >> >> Hi >> >> Still same error..Dont know what to do. >> Could you please paste the error that you are getting somewhere e.g., dpaste.de ? It would be really helpful if you join IRC channel #macports on freenode. I use IRCCloud to stay connected - https://www.irccloud.com/irc/freenode/channel/macports The link should help you get started. You would also need a @macports id. Do you have any preference for an username ? >> >> On 25 April 2018 at 21:24, 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 macports does not exist, will build as >>> > root >>> >>> Our build system only knows how to create users on macOS. You'll have to >>> create the macports user manually. >>> >>> > ---> Cleaning mpstats >>> > ---> Updating database of binaries >>> > Warning: Error determining file type of `/opt/local/bin/captoinfo': >>> > invalid command name "fileIsBinary" >>> > Warning: A file belonging to the `ncurses' port is missing or >>> > unreadable. Consider reinstalling it. >>> > Warning: Error determining file type of `/opt/local/bin/clear': invalid >>> > command name "fileIsBinary" >>> > Warning: A file belonging to the `ncurses' port is missing or >>> > unreadable. Consider reinstalling it. >>> > Warning: Error determining file type of `/opt/local/bin/infocmp': >>> > invalid command name "fileIsBinary" >>> > >>> > Didnt find a solution on the net either. >>> >>> That's rev-upgrade failing. It also only works on macOS. It's not >>> essential though, so you can set 'revupgrade_autorun no' in your >>> macports.conf. >>> >>> - Josh >> >> > -- Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
Hi Vishnu, On Wed, Apr 25, 2018 at 3:36 AM, Mojca Miklavec wrote: > 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. > For specific steps you could refer to step 3. at https://guide.macports.org/#installing.macports.git For building portindex you can do the following steps $ cd /opt/mports/macports-ports $ portindex It would take some time to create the whole portindex. P.S: git clone might also take a lot of time if you are on a slow internet. You could try a shallow clone [1] to make the checkout fast. You will have only the latest commit and not the complete changeset. Links: [1]: https://www.perforce.com/blog/git-beyond-basics-using-shallow-clones -- Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
On Tue, Apr 24, 2018 at 10:06 PM, Vishnu wrote: > I tried using these > > mkdir -p /opt/mports > $ cd /opt/mports > $ git clone https://github.com/macports/macports-base.git > $ git checkout v2.4.3 # skip this if you want to use the development > version > > Build and Install MacPorts > > MacPorts uses autoconf and makefiles for installation. These commands will > build and install MacPorts to /opt/local. You can add --prefix to > ./configure to relocate MacPorts to another directory if needed. > > $ cd /opt/mports/macports-base > $ ./configure --enable-readline > $ make > $ sudo make install > $ make distclean > > while trying to configure i am getting :configure: error: mtree not > found. > > How to proceed? > > I think i need to install additional files. > Can someone help? Looks like mtree[1] is not installed in your machine. Could you try running 'sudo apt-get install tree' before configure ? I also found one answer at [2]. Haven't checked though. [1] http://manpages.ubuntu.com/manpages/bionic/man8/fmtree.8.html [2] https://serverfault.com/a/690089 -- Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
Hi Vishnu, On Tue, Apr 24, 2018 at 9:58 PM, Vishnu wrote: > Hey > > I have been trying to install Macports on ubuntu. > And am unable to do so. > > Downloaded the tar. > Somehelp would be appreciated. > > Could you please try to build it from source [1] ? Are you getting some error related to XCode ? It would give some insights if you could paste[2] what kind of error you are getting. Reference: [1] https://guide.macports.org/#installing.macports.source [2] https://dpaste.de/ -- Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
Hi Vishnu, Welcome to The MacPorts Project! On Tue, Apr 24, 2018 at 4:15 AM, Vishnu wrote: > Hey, > > So first thing. > (a.1) I am planning to install ubuntu on my pc in a day. > I guess We can install Macports on that. That's great. Let us know if you face any issues and if we could be of any help. I was also thinking about cloud platform (specifically Google Cloud) which gives you around 300$ of credits for one year where you could spin up a VM and test the installation. Note: It might need a Credit Card for authentication. > (a.2 , a.3) Once macports is installed i'll install mpstats ,buildbot too. > > (b.1) I went and completed week 1.But i am unable to access week 3 , week > 4.Because the course starts on April 30 i guess. > I went through the topics. > Week 3 : Subqueries and Join > Week 4 : Modifying and Analyzing Data with SQL > I guess you can join the upcoming session and complete all the assignments and weeks before hand too (I was able to do so few weeks back). > So now would learn more about these topics through youtube, many other > resources. > > (b.2) Will look into them. > (b.3) Django hopefully wouldn't be a problem. > > (c.0) I would suggest that we create a new repository for your project > under > MacPorts, you fork it and use your own fork for endlessly playing with > it, testing etc > This sounds good. > I think i would be more comfortable with Github. > > (c.2) Can be done. > (c.3) You are talking about Build History data ..right? > There is already a JSON API for it as you said..so cant we use it? ( > https://build.macports.org/json/help ) > > (d.1 , d.2) Yes will do the research . > > > (e.1) I think when i will be changing Buildbot to update the database after > every build ..Then i would need Tcl. > Will learn them as i get time. > Speaking from experience, I would suggest go through the basics of Tcl and write some small sample programs to get the gist of Tcl. This would help you recall whatever you tried now at a later point of time when you actually touch macports-base. https://www.tcl.tk/man/tcl8.5/tutorial/Tcl0.html helped me a lot. I always keep this window open while developing base. > Will see Project Description. > > Also i have my Semester End exams from 27 April - 7 may. > So maybe i would not be able to reply on time. > No issues. Do well for the exams :) Keep us updated. Looking forward to a great summer this year :) -- Jackson Isaac
Regarding acl2 Port
Hi, I was working on updating the acl2 port version from 3.5 to 8.0 There has been lot of changes ever since to upstream. They moved to github and the stable versions are released under 'acl2-devel' username instead of acl2 (upstream). I was thinking to obsolete acl2 and move the new port to acl2-devel. Any thoughts or advice regarding this would be really helpful. Probably from experienced Port developers and/or PortMgr. I would also like to know how do I test all the variants and different phases that are mentioned in initial Portfile. There were lot of things that didn't work correctly with updated version but I was able to pin point to only errors that I encountered (by running just port -d build/destroot/install acl2) but there might be other changes too that may be required. Do we run each and every variant combination and test the portfile or is there any easy way to do so (maybe run a build bot job ?). -- Jackson Isaac
Re: Dealing with False Positive during Livecheck
On Wed, Apr 11, 2018 at 9:23 PM, Perry E. Metzger wrote: > On Wed, 11 Apr 2018 11:25:16 +0530 Jackson Isaac > wrote: >> 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 upstream seem to be inactive since the last changes >> were made >5 years ago. >> >> Few of the ports that I have noticed till now are: >> 1. aacgain >> 2. chemtool >> >> I will be updating the list and probably put it up on wiki, so that >> in future we don't spend time looking for the updated tarballs. > > Rather than putting this in the Wiki, is there a way to fix the > Portfile so that we don't get a false positive trigger? Then people > don't have to manually consider the problem. > One possible way as suggested on IRC is to add a comment in the Portfile as to why it cannot and/or won't be updated further (in case of inactive upstream) and removing the livecheck regex. -- Jackson Isaac
Dealing with False Positive during Livecheck
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 upstream seem to be inactive since the last changes were made >5 years ago. Few of the ports that I have noticed till now are: 1. aacgain 2. chemtool I will be updating the list and probably put it up on wiki, so that in future we don't spend time looking for the updated tarballs. Feel free to add ports which you might have also encountered. P.S: I didn't check the archives to see if this topic was discussed previously. -- Jackson Isaac
Re: [macports-ports] branch master updated: aacgain: Update dirname in post-extract phase
On Sun, Apr 8, 2018 at 3:33 PM, Jackson Isaac wrote:
> On Sun, Apr 8, 2018 at 3:05 PM, Ryan Schmidt wrote:
>>
>> On Apr 8, 2018, at 04:12, Jackson Isaac wrote:
>>
>>> Jackson Isaac (JacksonIsaac) pushed a commit to branch master
>>> in repository macports-ports.
>>>
>>>
>>> https://github.com/macports/macports-ports/commit/65defdc294622caa6e4c44d874286917a1d51ce1
>>>
>>> The following commit(s) were added to refs/heads/master by this push:
>>>
>>> new 65defdc aacgain: Update dirname in post-extract phase
>>>
>>> 65defdc is described below
>>>
>>>
>>> commit 65defdc294622caa6e4c44d874286917a1d51ce1
>>>
>>> Author: ijackson
>>> AuthorDate: Sun Apr 8 14:42:19 2018 +0530
>>>
>>>
>>> aacgain: Update dirname in post-extract phase
>>>
>>> Version and tarball name didn't match and
>>> hence there was an issue while applying patch.
>>>
>>> ---
>>> audio/aacgain/Portfile | 4
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/audio/aacgain/Portfile b/audio/aacgain/Portfile
>>> index 481b021..bda6c74 100644
>>> --- a/audio/aacgain/Portfile
>>> +++ b/audio/aacgain/Portfile
>>> @@ -21,6 +21,10 @@ use_bzip2 yes
>>> checksums sha256
>>> 2bb8e27aa8f8434a4861fdbc70adb9cb4b47e1dfe472910d62d6042cb80a2ee1 \
>>> rmd160 8f97121f3797cde45f71839dbe14251b74365ccd
>>>
>>> +post-extract {
>>> +file rename ${workpath}/${name}-1.8 ${workpath}/${name}-${version}
>>> +}
>>
>> Set worksrcdir instead of this.
>>
>> However, don't do that, because this update was completely wrong. No version
>> 1.9 exists at the download site. Take a look:
>>
>> http://aacgain.altosdesign.com/alvarez/
>>
>> There is only 1.8. Their web server is just configured in an improperly
>> helpful manner: If you request the file for the nonexistent 1.9, it silently
>> redirects you to the file for 1.8:
>>
>> $ curl -I http://aacgain.altosdesign.com/alvarez/aacgain-1.9.tar.bz2
>> HTTP/1.1 301 Moved Permanently
>> Content-Type: text/html; charset=iso-8859-1
>> Connection: keep-alive
>> Keep-Alive: timeout=15
>> Date: Sun, 08 Apr 2018 09:26:54 GMT
>> Server: Apache
>> Location: http://aacgain.altosdesign.com/alvarez/aacgain-1.8.tar.bz2
>>
>> What I did not see in your previous commit which updated the port to "1.9",
>> because you combined whitespace changes with functional ones, is that the
>> checksums did not change. So what you've called 1.9 here is definitely
>> unchanged from 1.8.
>>
>> The web site claims a version 1.9 exists, but I don't know where it is. If
>> it can't be found, the changes you made should be reverted to put the port
>> back at version 1.8. The epoch will have to be increased so that anybody who
>> did install 1.9 already will be downgraded back to 1.8.
>
> I did find one at "https://github.com/mecke/aacgain"; but I was not so
> sure if they both are by same author since 'alvarez' was mentioned at
> http://aacgain.altosdesign.com and on github it was 'mecke'. Also the
> commit log didn't help much either.
>
> Looking at the README, it looks like this might possibly be the 1.9 version.
>
> I would like to know what to do in such a scenario. Should I go
> forward with the github version ?
>
Github version is just code files and does not contain files for Unix
build which was part of the tarball created
by Alvarez.
Digging into the issue I came across a very old ticket for aacgain
reported by Ryan at https://trac.macports.org/ticket/25942.
Looks like someone had created the tarball for 1.9 and hosted it one
their own website since 'Alvarez' didn't create the
official 1.9 tarball yet. But the port was never updated.
--
Jackson Isaac
Re: [macports-ports] branch master updated: aacgain: Update dirname in post-extract phase
On Sun, Apr 8, 2018 at 3:05 PM, Ryan Schmidt wrote:
>
> On Apr 8, 2018, at 04:12, Jackson Isaac wrote:
>
>> Jackson Isaac (JacksonIsaac) pushed a commit to branch master
>> in repository macports-ports.
>>
>>
>> https://github.com/macports/macports-ports/commit/65defdc294622caa6e4c44d874286917a1d51ce1
>>
>> The following commit(s) were added to refs/heads/master by this push:
>>
>> new 65defdc aacgain: Update dirname in post-extract phase
>>
>> 65defdc is described below
>>
>>
>> commit 65defdc294622caa6e4c44d874286917a1d51ce1
>>
>> Author: ijackson
>> AuthorDate: Sun Apr 8 14:42:19 2018 +0530
>>
>>
>> aacgain: Update dirname in post-extract phase
>>
>> Version and tarball name didn't match and
>> hence there was an issue while applying patch.
>>
>> ---
>> audio/aacgain/Portfile | 4
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/audio/aacgain/Portfile b/audio/aacgain/Portfile
>> index 481b021..bda6c74 100644
>> --- a/audio/aacgain/Portfile
>> +++ b/audio/aacgain/Portfile
>> @@ -21,6 +21,10 @@ use_bzip2 yes
>> checksums sha256
>> 2bb8e27aa8f8434a4861fdbc70adb9cb4b47e1dfe472910d62d6042cb80a2ee1 \
>> rmd160 8f97121f3797cde45f71839dbe14251b74365ccd
>>
>> +post-extract {
>> +file rename ${workpath}/${name}-1.8 ${workpath}/${name}-${version}
>> +}
>
> Set worksrcdir instead of this.
>
> However, don't do that, because this update was completely wrong. No version
> 1.9 exists at the download site. Take a look:
>
> http://aacgain.altosdesign.com/alvarez/
>
> There is only 1.8. Their web server is just configured in an improperly
> helpful manner: If you request the file for the nonexistent 1.9, it silently
> redirects you to the file for 1.8:
>
> $ curl -I http://aacgain.altosdesign.com/alvarez/aacgain-1.9.tar.bz2
> HTTP/1.1 301 Moved Permanently
> Content-Type: text/html; charset=iso-8859-1
> Connection: keep-alive
> Keep-Alive: timeout=15
> Date: Sun, 08 Apr 2018 09:26:54 GMT
> Server: Apache
> Location: http://aacgain.altosdesign.com/alvarez/aacgain-1.8.tar.bz2
>
> What I did not see in your previous commit which updated the port to "1.9",
> because you combined whitespace changes with functional ones, is that the
> checksums did not change. So what you've called 1.9 here is definitely
> unchanged from 1.8.
>
> The web site claims a version 1.9 exists, but I don't know where it is. If it
> can't be found, the changes you made should be reverted to put the port back
> at version 1.8. The epoch will have to be increased so that anybody who did
> install 1.9 already will be downgraded back to 1.8.
I did find one at "https://github.com/mecke/aacgain"; but I was not so
sure if they both are by same author since 'alvarez' was mentioned at
http://aacgain.altosdesign.com and on github it was 'mecke'. Also the
commit log didn't help much either.
Looking at the README, it looks like this might possibly be the 1.9 version.
I would like to know what to do in such a scenario. Should I go
forward with the github version ?
>
> It seems that you didn't try to build this before committing it, or you would
> have at least seen the patch failure. Please always verify successful
> installation of a port on your own system before committing.
>
>
I did notice the patch failure and thought it might be because the
patch file was older and then I forgot to build it again with the new
patch file. It was a mistake from my side. Have got little rusty since
it has been quite some time updating ports.
--
Jackson Isaac
Re: [macports-ports] branch master updated: aacgain: Update to v1.9
Hi Ryan, On Sun, Apr 8, 2018 at 2:33 PM, Ryan Schmidt wrote: > > On Apr 8, 2018, at 03:46, Jackson Isaacwrote: > >> Jackson Isaac (JacksonIsaac) pushed a commit to branch master >> in repository macports-ports. >> >> >> https://github.com/macports/macports-ports/commit/30c9fad4f1d0e000525c5f2bb5119453f3e373fa >> >> The following commit(s) were added to refs/heads/master by this push: >> >> new 30c9fad aacgain: Update to v1.9 >> >> 30c9fad is described below >> >> >> commit 30c9fad4f1d0e000525c5f2bb5119453f3e373fa >> >> Author: Jackson Isaac > > Remember to set up your git clone (or your git defaults) so that your commits > are authored by your MacPorts project email address. > > https://trac.macports.org/wiki/WorkingWithGit#setup I was looking for this. For some reason my git checkout was not working like before. Thanks for the link :) > > >> AuthorDate: Sun Apr 8 14:16:50 2018 +0530 >> >> >> aacgain: Update to v1.9 >> >> Add modeline and fix mixed tabs and spaces. > > In the future, please make whitespace changes (along with adding the modeline > if needed) in a separate commit from functional changes, so that the > functional changes are easier to spot and review. > > Will keep this in mind. Actually, there was a bug in functional changes which I am fixing and will commit in few minutes. -- Jackson Isaac
Re: Gsoc 18 Project | Collect build statistics
Hi Vishnu,
On Fri 6 Apr, 2018, 22:19 Vishnu, wrote:
> Could i get a reply please.
>
Was there any question or query that I might have missed ?
On Thu, Apr 5, 2018, 11:23 PM Vishnu wrote:
>
>> Hello
>>
>> Here is the git repository i made and am working on for demo project.
>> https://github.com/VishnuM-sopho/demo-macports
>>
>> Thanks
>>
>> On 5 April 2018 at 21:31, Vishnu wrote:
>>
>>> Hello Jackson
>>>
>>>
>>> I am sorry .
>>> I was in a hurry to finish the demo as early as possible. So, I didnt yet
>>> make a git rep for this folder so you cant see any history.
>>> Right now we can only compare the files i sent earlier thrugh mails
>>> earlier to see changes.
>>>
>>> Thanks
>>>
>>> On 5 April 2018 at 19:53, Jackson Isaac wrote:
>>>
>>>> Hi,
>>>>
>>>> On Thu 5 Apr, 2018, 19:38 Vishnu, wrote:
>>>>
>>>>> Dear mentors,
>>>>>
>>>>> I further improved my demo project based on feedback.
>>>>>
>>>>> I am now able to parse the ports(stored in json locally) using the
>>>>> website itself(by accessing {url}/port/parser).
>>>>> This will read the json file and fill the port table using django
>>>>> models.
>>>>>
>>>>> also upon adding the ports to the table we get to see how many ports
>>>>> were added .
>>>>>
>>>>> Please go through the images attached in the link below in sequential
>>>>> order.
>>>>> And do provide some feedback.What else should i do?
>>>>>
>>>>>
>>>>> https://drive.google.com/open?id=1brwBCNoz9STWakvLZ7h-JNrnKFAdvMTS
>>>>>
>>>>
>>>> Could you please push the code on git so that we can track changes ?
>>>>
>>>
>>>
>>
Re: Gsoc 18 Project | Collect build statistics
Hi,
On Thu 5 Apr, 2018, 19:38 Vishnu, wrote:
> Dear mentors,
>
> I further improved my demo project based on feedback.
>
> I am now able to parse the ports(stored in json locally) using the website
> itself(by accessing {url}/port/parser).
> This will read the json file and fill the port table using django models.
>
> also upon adding the ports to the table we get to see how many ports were
> added .
>
> Please go through the images attached in the link below in sequential
> order.
> And do provide some feedback.What else should i do?
>
>
> https://drive.google.com/open?id=1brwBCNoz9STWakvLZ7h-JNrnKFAdvMTS
>
Could you please push the code on git so that we can track changes ?
Re: Gsoc 18 Project | Collect build statistics
Hi Vishnu, On Tue 3 Apr, 2018, 20:26 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 > Please go ahead and implement your idea :) > Would that act as a sample for my Coding skill? > Or should i do something else? > For me, it should be enough to get a gist of your skills and thought process. We can probably add some mini tasks on the fly, if required. Feel free to reach out to us in case you have any queries. -- Jackson Isaac
Re: Trac upgraded to 1.2
Hi, On Sun, Apr 1, 2018 at 1:05 PM, Ryan Schmidt wrote: > > On Mar 31, 2018, at 18:10, Clemens Lang wrote: > >> Our Trac installation at trac.macports.org was updated to the 1.2 series >> of Trac. Since this was a feature upgrade, new bugs may have sneaked in. >> If you see something that used to work before and no longer works now, >> please file a ticket with the trac component. >> >> See the Trac changelog at >> https://trac.edgewall.org/wiki/TracChangeLog#a1.2.2 >> for a list of changes. We upgraded from the 1.0 series of Trac. > > Thanks! > > So far, I dislike the "cosmetic improvements for ticket changelog". > > https://trac.edgewall.org/ticket/11835 > > I'm pretty sure I don't like the property changes floated to the right, and I > don't like that the box they're in is yellow. > > We already override the yellow color of the ticket description box, so maybe > we could at least override the yellow color of the property change box too. > > After Ryan's mail about the cosmetic changes, I was eager to check out the new Trac. For me in [1], the ticket results doesn't fit 100% in the browser tab i.e., there is a horizontal scroll (See [2]). IIRC, in the previous version it used to fit in the browser tab without any horizontal scroll. Is it just me or anyone else also had similar experience ? Also the transparent "Filters" box under Custom Query, looks a bit odd for me. I guess it is same for all drop down option buttons. Reference: [1] https://trac.macports.org/query?status=!closed&type=defect&component=ports&desc=1&order=time [2] https://imgur.com/a/MdhZX -- Jackson Isaac
Re: GSoC
Hi Abhishek, On Sat, Mar 17, 2018 at 11:07 PM, Abhishek Kashyap wrote: > hi > i want to know about the implementation of adding items to the port tree. > And procedure to install multiple plists. Please try to avoid creating multiple mail threads every time. Also it would be great if you could add more thoughts and content in the mail before you hit that Send button so that we also get some idea on what you want to know and what are you discussing about. It might not leave a good impression on the reader (it didn't at least for me). P.S: Take this in a constructive manner. Everyone has their first time :) -- Jackson Isaac
Re: Python default version
On Mon, Mar 12, 2018 at 8:16 PM, Ryan Schmidt wrote: > The python portgroup defaults to version 2.7, and in ports that have python > variants, I've used that version by default as well. > > I was reminded by the members of the MacPorts meeting that it has been > announced that python 2's end-of-life will be in 2020, which is coming up. > > Should we change the default python version to 3.6 now, or soon? > I agree to the decision to default to Python 3. I would say we should set a milestone for the default version. Probably in the next release cycle ? I have been using Python3 for my work most of the time. Haven't really touched Python2 much in a long time other than for some particular use case. -- Jackson Isaac
Re: Buildbot idea(s) for GSOC
Hi, On Thu, Mar 8, 2018 at 9:15 PM, Umesh Singla wrote: > Hi Mojca > > See inline. > > On Wed, Mar 7, 2018 at 3:22 AM, Mojca Miklavec wrote: >> >> Dear Umesh, >> >> In case we would get any good students in that area, I would be >> grateful if someone would work on improving buildbot core & front-end >> in close collaboration with mentors directly from buildbot. >> >> I added this one idea on the list, but it needs some polishing: >> https://trac.macports.org/wiki/SummerOfCode#Buildbotideas >> >> However, in order to attract potential students, we would likely need >> to add a few suitable keywords to our "description", like perhaps >> "frontend". But we would also need to make it easier for such students >> who end up on our site to actually spot such projects without browsing >> through the full list. > > > I can add some tags like frontend or javascript on GSoC website to include > MacPorts in the search results. Probably the tag "End User Applications" > doesn't help much. Feel free to add relevant tags. > > Maybe, we can divide the project list into 3 sections - infrastructure based > projects, macports-base and ports (or documentation-based as well?). Trac, Sounds great. It would be more organized and easy to search for the people visiting the site for the first time. Initially, even I had to read through a page few times to understand the things better. > as compared to other orgs' fancy websites these days, doesn't help much to > attract students (one simple reason could be very small fonts or not easily > searchable). I couldn't have chosen any project, if it wasn't for Jackson > who helped me out last year. Thanks! Such kind words keeps the community motivated :) Feel free to share a bier or two from the Meeting (qty. measured in dozen(s)) ;) > > The ideas which are not finalized or are still being discussed can be put on > to some other page or where mentors are not available for that year. > Something like general MacPorts projects and current year eligible-GSoC > projects. > >> >> Buildbot participated in GSOC before, but did not apply this year. >> They would be willing to mentor and we really need some features >> implemented if we want to go for buildbot 1.0 setup one day. (That >> said, I would find it ok even if some project from buildbot mentorship >> is not strictly macports-oriented.) > We can add them as secondary mentors advising on the project. Even for my project, we contributed to external project, namely libsolv. We kept a copy for ourselves to adapt to our needs and opened a PR on upstream. It was upto the external project on which parts they would want to merge into upstream (since we had macports specific code). The evaluation and organizational procedures would still be with us, AFAIK. > > I'll add someone's name from Buildbot to the project you added (I think > Pierre Tardy agreed to mentor?) along with "from Buildbot community" in the > description. But I'd say we should work on what exactly we mean by "make > Buildbot 1.0 a lot more useful for MacPorts". I haven't gone through the > threads about Buildbot on this list, maybe will do now. > That would be great. Probably we can get a confirmation from Buildbot team as to who would be interested and suitable mentor for the project. >> >> Another project we could put on the list would be figuring out how to >> start clean VMs for each build, but that might be tricky and the >> student would need to be able to figure that out on his own. >> Apparently buildbot supports that for Linux. > > > Not sure but can Jenkins help here? Usually you need a yaml file and a xml > file and provides quite a number of plugins to customize unlike Travis. It > would be a big shift though. > It's about time to get DevOps skills here ;) BTW, I hope everyone is ready for the MPM 2018. Hope to join remotely. Mojca, Any plans for remote session ? Would be great to have some details about it in advance, so interested people can plan accordingly. -- Jackson Isaac
Re: GSOC 2018
Hello Abhishek, On Sun, Feb 25, 2018 at 7:19 PM, Abhishek Kasyap wrote: > Hello i Abhishek,intrested in this project towards improvement of > startupitem code and many more.So guide where to start. > > Welcome to MacPorts Community! You can begin with going through Tcl tutorial at [1]. Our code can be found at [2]. For a code walkthrough you can refer to [3]. It would be great to hear more from you about what kind of projects have you already worked on, etc. Reference: [1] https://www.tcl.tk/man/tcl8.5/tutorial/tcltutorial.html [2] https://github.com/macports/macports-base/ [3] https://youtu.be/46qshiDskrM -- Jackson Isaac
Re: GSoC 2018: Interested in Improving startup item code
On Sun, Feb 18, 2018 at 12:07 AM, Abhishek Singh Bisht wrote: > Hi Jackson, > > Thanks for taking time, I appreciate it. Will proceed as you said. Also i > was thinking wether or not it’d be feasible to remove all dependencies on > Xcode? I mean shouldn’t the command line tools suffice? I read that some > ports mandatorily require Xcode, but is there any possibility? > Yes Xcode-clt should suffice for most of the ports. Some ports may depend on XCode itself though. I am not sure if any port can be built even without xcode itself. But anyways we would like to minimize the dependency on the XCode package as such which is 6-7GB for every update they release. Probably Clemens can share some insights ? -- Jackson Isaac
Re: GSoC 2018: Interested in Improving startup item code
Hi Abhishek, On Wed, Feb 14, 2018 at 6:12 PM, Abhishek Singh Bisht wrote: > Hello everyone, > > I am interested in contributing to your project, by helping improve the > startup item code. I have seen the project description and will definitely be > able to implement the required features probably a couple extra ones too by > the end of summer. > Welcome to the MacPorts community! > This mail is just to say hi and introduce myself, so I am Abhishek, a third > year B.E Computer Science and Engineering student from JSS Science & > Technology University(Formerly, SJCE Mysore). Thanks for your introduction. I am Jackson Isaac, one of the backup admin and mentor this year for The MacPorts Project. > > To be honest I am proficient in C, Python but do not have direct hands on > experience with TCL, only have seen a bit of it when dealing with TKinter in > Python. Having said that, I am pretty sure it wouldn’t require much time for > me to learn TCL. > To begin with, you can go through [1]. This will give you a gist of Tcl. Our code is at [2]. Clone, build and run - If you face issues or difficulties feel free to ask :). Try to understand the codebase and probably try to fix any open bugs [3]. You can even start with Portfile development. I would like you to open Pull Requests on github with your modifications. For a walk-through the code base, you can also refer [4]. I hope you are also following our discussions on -dev list regarding the projects (there is also a detailed discussion going on regarding the project that you showed interest in). Feel free to add anything that you would like to. We would love to hear your views and thoughts too. Reference: [1] https://www.tcl.tk/man/tcl8.5/tutorial/tcltutorial.html [2] https://github.com/macports/macports-base/ [3] https://trac.macports.org/wiki/Tickets [4] https://youtu.be/46qshiDskrM -- Jackson Isaac
Fwd: [GSoC Mentors] GSoC Org Ideas List should be solid by this Monday at 19:00 UTC for review
Hi Umesh, I hope you are receiving mails from GSoC Mentors list. We might need to revamp our Ideas page. Although there are tasks on Ideas list, we might have to work on verifying which tasks are doable and have potential mentors for, this year. Brainstorm any new ideas that we can add would also help. Devs, Please add detailed ideas to the list, if any. -- Forwarded message -- From: 'Stephanie Taylor' via Google Summer of Code Mentors List Date: Sun, Jan 28, 2018 at 1:35 PM Subject: [GSoC Mentors] GSoC Org Ideas List should be solid by this Monday at 19:00 UTC for review To: Google Summer of Code Mentors List Hi all, It seems quite a few veteran orgs have 0, or very few, projects listed on their Ideas List for their GSoC Org apps. Some have something like "coming soon" with no actual ideas on their page - this will result in an automatic rejection - please don't let that be you! Our team has been reviewing hundreds of applications this week and taking notes and we have noticed MANY orgs that have not completed their lists (have 1-2 ideas or ideas with 1 sentence describing the problem) or say 'coming in March', 'coming soon', etc. That's a 'Reject in our book. We will meet Monday, Jan 29 as a team to start our multi day meetings going through each and every org application together so you have until Monday at 19:00 UTC to get your ideas onto your list. You can always add more ideas later but if you are an Umbrella Org you should have plenty of ideas listed now - and if you are a smaller org you should have 4-5 well developed ideas minimum. And please don't just link to a bug tracker. If the bug tracker has extensive descriptions about the project/problem then that can sometimes be fine. But just saying here are 5 things we want worked on and a sentence about each isn't going to cut it. If you are an Org Admin I strongly encourage you to go back and look at your Ideas List before Monday at 19:00 UTC and make sure it is representative of what you want us to evaluate. Every year we have a few orgs who give us bad URLs or don't give us access permission to see their Project Ideas List. Again, please don't be that org... (your community will not be happy). Remember, the #1 thing our team considers when choosing which orgs to accept is the quality of the Project Ideas list. If you have nothing for us to look at we have to reject you. Please don't ask us to go and see if your application is okay. If you have a solid Project Ideas List and have read the Defining a Project Ideas list from the Mentor Guide and followed the advice your list is likely good to go. Best, Stephanie Stephanie Taylor Open Source Programs, Google sttay...@google.com -- You received this message because you are subscribed to the Google Groups "Google Summer of Code Mentors List" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-summer-of-code-mentors-list+unsubscr...@googlegroups.com. To post to this group, send email to google-summer-of-code-mentors-l...@googlegroups.com. Visit this group at https://groups.google.com/group/google-summer-of-code-mentors-list. To view this discussion on the web visit https://groups.google.com/d/msgid/google-summer-of-code-mentors-list/CAEp7XcT%2BacNEJP7E0ZYr742_xDFcJDQkB_DEB-gRwa9FKsOvEA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- Jackson Isaac
Re: GSoC 2018 Application
Hi Umesh, On Fri, Jan 12, 2018 at 4:21 PM, Umesh Singla wrote: > Hi, > > Following the conversation on the dev mailing list, I have assumed the role > of organization administrator and Jackson Isaac as backup administrator and > a potential mentor for now. > > I have registered MacPorts for participating in GSoC this year and submitted > the initial version of the application from MacPorts side on GSoC'18 [0] > website, in coordination with Jackson. > > The corresponding pages of our Trac have been updated. > > The application questionnaire [1] and the ideas page [2] have been modified > to include this year's dates and other relevant information. > > [0]: https://summerofcode.withgoogle.com/ > [1]: https://trac.macports.org/wiki/SummerOfCodeOrgApplication > [2]: https://trac.macports.org/wiki/SummerOfCode > Thanks for filling out the form. I had a quick glance. We still need to refine the answers, correct ? > @Jackson: I invited you to be a backup admin from GSoC's website. Please > check and approve. > Yup done :) Clemens, Mojca, Bradley, Are you in for mentoring this year again ? Also we need to decide what tasks need to be done this year as part of GSoC. -- Jackson Isaac
Re: GSOC 2018 org application period has begun
Hi Umesh, On Wed, Jan 10, 2018 at 7:52 AM, Umesh Singla wrote: > Hi Jackson, > > I am not at the stage to mentor but I think I can learn from the experience > of being an org admin (if we're participating). I couldn't find anything > more specific about the eligibility or role of an org-admin though, other > than managing the org's program and helping a smooth communication between > mentors and students. > That's great :) I'll help you out. Probably its time for me to become a Mentor now ;) > Let me know what you think and also, if any other criteria MacPorts has. I'd > be happy to volunteer. Could use someone as backup admin too. > I can be the backup admin. Clemens used to be the backup admin in the previous years. I'll wait for his reply before confirming. > Regards > > On Mon, Jan 8, 2018 at 9:57 PM, Jackson Isaac wrote: >> >> Hi, >> >> On Mon, Jan 8, 2018 at 1:13 PM, Mojca Miklavec wrote: >> > Hi, >> > >> > The GSOC 2018 application period for organisations is now open, >> > deadline for applying in January 23rd. >> > >> > I hope we are going to participate this year as well? >> > If so, it would be about time to come up with additional ideas and >> > clean up the ideas page. >> > >> >> Thanks Mojca for sending out a mail. I was about to mail tonight :) >> >> Let me know if anyone is interested to take up Org Admin/Mentor task, >> I'll be more than happy to guide them. >> >> If no one volunteers, I am open to become the Org Admin again this >> year. I'll wait until 10th January 2018 1600 UTC, after which >> I will be applying as Org Admin. I would also request other interested >> devs who would like to be mentors this year to send out a mail and >> also some ideas that they would have. >> >> P.S.: Will send out a separate mail once we know potential mentors, >> admins and backup mentors. >> > -- Jackson Isaac
Re: GSOC 2018 org application period has begun
Hi, On Mon, Jan 8, 2018 at 1:13 PM, Mojca Miklavec wrote: > Hi, > > The GSOC 2018 application period for organisations is now open, > deadline for applying in January 23rd. > > I hope we are going to participate this year as well? > If so, it would be about time to come up with additional ideas and > clean up the ideas page. > Thanks Mojca for sending out a mail. I was about to mail tonight :) Let me know if anyone is interested to take up Org Admin/Mentor task, I'll be more than happy to guide them. If no one volunteers, I am open to become the Org Admin again this year. I'll wait until 10th January 2018 1600 UTC, after which I will be applying as Org Admin. I would also request other interested devs who would like to be mentors this year to send out a mail and also some ideas that they would have. P.S.: Will send out a separate mail once we know potential mentors, admins and backup mentors. -- Jackson Isaac
Re: ui_options(questions_singlechoice)
Hi Umesh, On Fri, Oct 6, 2017 at 10:18 PM, Umesh Singla wrote: > Hi, devs > > I have to use $macports::ui_options(questions_singlechoice) for a project on > a list of some other registry data structure (snapshot) and not ports. It > gets displayed in the following manner on terminal: > > Select any one snapshot to restore: > > 1) ::registry::snapshot0 > > 2) ::registry::snapshot1 > > 3) ::registry::snapshot2 > > 4) ::registry::snapshot3 > > Enter a number to select an option: > > > I would like to know how to display useful information enough to identify > instead of "::registry::snapshot0" or "::registry::snapshot1". A > registry::snapshot has id, note, created_at fields. > IIRC, I had used something like this - $macports::ui_options(questions_singlechoice) "Select any one snapshot to restore:" "" [$reg_field_list] Hope this helps. Although, I couldn't find the exact location where ui_options are defined for the parameters that it would accept. Quite some time I touched base code. -- Jackson Isaac
Re: Fwd: Google Summer of Code 2018
Hi, On Tue, Sep 26, 2017 at 2:37 AM, Umesh Singla wrote: > > > On Sep 26, 2017 2:09 AM, "Mojca Miklavec" wrote: > > Forwarding a message from Google ... > .. > > Last week we also announced the Google Code-in 2017 (GCI) contest for 13-17 > year old students. GCI is open for past GSoC mentoring organizations to > apply to be a part of this exciting contest from October 9th - October 24th. > We are also giving GCI orgs over a month to enter their tasks into the > webapp, hopefully this will help them prepare for the busy winter contest. > GCI opens for student participants on November 28th! You can read more about > the program on our blog. > > > Have we ever participated in GCI before? > Not yet. But we are open to volunteers. Let me know if anyone is interested in mentoring. Also, we can start putting forward our ideas early on and listing potential mentors, so that it will help to decide if we should apply next year again or not. I am open to someone else taking up the org admin task too :). -- Jackson Isaac
Re: [GSoC] migration
Hi, On Sun, Aug 6, 2017 at 5:41 PM, Umesh Singla wrote: > On Sat, Jul 22, 2017 at 7:26 AM, Joshua Root wrote: >> >> >>> For now, I'd like to ask in what order does "registry::entry imaged" >>> returns the port list? Because I'm running the sorting function which the >>> restore_ports.tcl uses but it's giving me the ports in the same order as >>> result. >> >> >> Probably just ordered by rowid, i.e. might as well be random. Note that >> the sort_ports proc from restore_ports.tcl does not take a list of registry >> references like registry::entry returns, but a list of strings representing >> port names, versions and variants in the format generated by 'port >> installed'. > > > `port installed` returns the result of `registry::entry imaged` sorted in an > alphabetical order, first by name, then version etc. > > `registry::entry imaged` might be returning in a random order but sorting it > (with ports coming before their dependencies) doesn't change the result at > all. > [1] and [2] might be useful. The list of ports are passed to _mportexec after topologically sorting them for installing. This might also answer some of your previous queries regarding using [mportexec $workername $install_target] and sorting the dependencies at once. Variants is still pending. You could try to integrate sorting and installation of ports with libsolv and extend variant handling from your script. You might have to tweak the libsolv code if you pass the variants like foo+bar-baz. One idea could be to add 'bar' as dependency and 'baz' as conflict explicitly since it will only read the portindex for 'foo'. Libsolv proved to be faster than our traditional recursive dependency calculation engine even after reading through the complete portindex every time it was called. Let me know if you have any doubts regarding the libsolv code. The comments should be explanatory enough by itself but feel free if you want to understand what is actually happening behind the scenes by libsolv. If interested, you could check [3] for setting up libsolv branch and testing/reusing the code with yours. You could prepare one for yours too, since final evaluation and submission is coming up soon. [1] https://github.com/macports/macports-base/blob/gsoc15-dependency/src/macports1.0/macports_libsolv.tcl#L474 [2] https://github.com/macports/macports-base/blob/gsoc15-dependency/src/macports1.0/macports.tcl#L2035 [3] https://trac.macports.org/wiki/SummerOfCode2015Libsolv -- Jackson Isaac
[GSoC 2017] Final Evaluations + Preparation
Hi Summer Students and Mentors, Yet another summer is nearing its course. I hope you all might have received an email from Google probably with all the details regarding what things need to be done and submitted, required to pass the final evaluation. Please start preparing documentation, code cleanup, regression testing, unit tests, etc.. Also you would be required to submit a single URL with all your work. So consolidate all your work at one place and also document how we can run and test your code. Feel free to add any graphs, screenshots, results, anything you think would help others understand the project done by you. -- Jackson Isaac
[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 if there are any issues faced. Regards, Jackson Isaac
[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 a write-up about their work (code written) till now and further plans for 2nd phase. -- Jackson Isaac
Re: [GSoC 2017] Community Bonding
Hi, On Thu, May 18, 2017 at 11:37 PM, 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 help you > to get to know each other better, set up future plans and discuss any > changes/shortcomings. > > 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 hear from you how is community bonding is going > on till now. Let us know if you face any issues or need any help to > setup meetings. > > [1] https://www.youtube.com/watch?v=46qshiDskrM > We are fast approaching end of Community Bonding Period and coding starts immediately after that on 30th May 2017. Kindly send in your experience till now to -dev ML and what things are planned further. I hope you have connected at least once with your mentor till now and are clear about your goals to begin with. Let us know if you faced any issues till now e.g., setting up meeting, code base related, mentor/student availability, etc.. -- Jackson Isaac
Registering MacPorts as Not for Profit Organization
Hi all, Moving the discussion regarding registering MacPorts as an organization to set up bank account for receiving donations, GSoC stipends (mentor and travel stipends to be precise), etc.. The following two ways were discussed: 1. Register our own organization in a country where cost is minimal (for e.g., France as discussed by Mojca in the attached mail). Or in US or Germany (with strict rules, higher yearly costs, legal stuff, etc.). 2. Registering as a sub-organization under a bigger organization and using their account?. Please feel free to add your suggestions/opinions and views. Also which would be a fast and efficient way so that we can also complete the process before completion of GSoC in order to accept this year's mentor and travel stipends. On Fri, May 19, 2017 at 1:38 PM, Mojca Miklavec wrote: > > On 18 May 2017 at 20:21, Jackson Isaac wrote: > > > > Should we create a separate thread for discussing not-for profit > > organization registration to find out best and efficient way we could > > do so ? > > Yes, we may do so, but I would do it publicly (on the -dev list?). > > Just as one data point. We founded ConTeXt Group in 2011 according to > the French law from 1901 or so. Someone needs to write the bylaws and > send them + the list of board members to the French officials, but > none of that costs anything. *All* our expenses boil down to less than > 100 EUR per year for the bank account (monthly fee of 6 EUR + 10 EUR > per year for online banking). We don't have a tax number (which means > that most of the time I cannot even request an invoice on the name of > the group without a VAT number, so I usually collect just regular > invoices), we don't need to send any financial report to the > government and we don't pay any taxes. All we need is a volunteer > treasurer sending invoices for membership fee (not sure if that would > be relevant for MP), paying invoices for journal printing & expenses > related to years member meetings, and making financial reports for > internal use only, ... Plus a president and secretary taking care of > everything else. But we don't have any professional accountant or > anything. We do need a local French person to occasionally talk to the > officials or to go to the bank (once every few years) though. > > For MP it might make more sense to open one in Germany or USA, but > either of those will probably require following much stricter rules. > We tried to open a bank account for that (at that time already > existing) French organisation in Germany and Slovenia, but any of > those would require the president and treasurer to come to the bank > personally, to get a local VAT number and submit financial reports > also to the Slovenian government for example, plus following some > weird anti-money-laundering procedures or whatever. > -- Jackson Isaac
[GSoC 2017] Community Bonding
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 help you to get to know each other better, set up future plans and discuss any changes/shortcomings. 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 hear from you how is community bonding is going on till now. Let us know if you face any issues or need any help to setup meetings. [1] https://www.youtube.com/watch?v=46qshiDskrM Happy Summer Coding, Jackson Isaac
[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
Hi, On Fri, 31 Mar 2017 at 9:14 PM, Zero King 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.com/l2dy/420533b821570e26dc7374898c3264fb Any advice is welcome and since this is a new idea I'm seeking for potential mentors. -- Best regards, Zero King Please upload the draft on gsoc portal so that we can review and add comments if required. -- Jackson Isaac
[GSoC 2017] Final Call for Mentors
Hi all, As you might know summer is just around the corner and once again it's time for summer of code. MacPorts is participating this year in google summer of code. We have been getting proposal requests from interested students. I would like to request developers to reply to this mail if they are interested to mentor this year. I would send them mentor requests. This will also be required if you would like to help with proposal review process. P.S.: Only for those who are not participating in GSoC as students. -- Jackson Isaac
Re: GSoC'17: Add migrate action to port command Project
Hi Umesh, First of all, Welcome to The MacPorts Project. We are always happy to see new developers around. On Fri, Mar 24, 2017 at 4:30 AM, Umesh Singla wrote: > Hello, > > As we discussed on IRC, I've been looking into the project "Add migrate > action to port command" and hoping to submit a draft proposal very soon. > I'll need your help in putting up a nice proposal for sure. > Submitting a draft early is a good idea so that we could guide you well in time. We had submitted a template for proposal on the summerofcode.withgoogle.com page. Let me know if you are unable to access it. > I'm currently trying to acquaint myself with the MacPorts codebase and came > across the Macports guide [0]. Thanks for keeping such guides for newbies. > The project description points to a migration instruction guide [1], > automating which is more or less the goal of the project, am I right? > > Since final submission deadline is close, I'll be grateful if someone can > point me in the right direction for now and not waste time fiddling around. > > Also, @Jackson, I'm not able to find any discussion about this project on > mailing list threads. Can you link me to them? I think they'll help me in > understanding the need and expected outcomes by the community from this > project and might give a better insight into the project. > It was in macports-users (I thought it was posted on macports-dev, took me some time to search :P) https://lists.macports.org/pipermail/macports-users/2017-March/042837.html > @pixilla, if we need to discuss, what'd be the best time according to your > timezone? > Pixilla, Could you please guide the student on migration tool project. Let us know if you face any issue(s). -- Jackson Isaac
Re: [GSoC] Call for Mentors GSoC 2017
Hi all, This is a gentle reminder for GSoC 2017 Call for Mentors. If anyone else is interested in mentoring some awesome students this summer please let us know. I would also like to know if the mentors who have agreed to mentor this year have been contacted by any interested student until now and could you please share some experience/response from students? I noticed that there were few students around on IRC and mailing list. Would be great to hear about their interactions. On Tue, Feb 7, 2017 at 9:22 AM, Jackson Isaac wrote: > Hello everyone, > > As you all might be knowing GSoC season has started and they are > accepting organization applications until February 9, 2017, 17:00 > (UTC). > > I would like to invite you all and know who all would like to mentor > some awesome students this year to get on-board with MacPorts. > > I have already started the application process by coordinating with > Rainer. If we have sufficient mentors and a admin and backup admin(s), > we can move ahead with the application process. > > Please feel free to reply to this thread if you are interested in > participating as a mentor for GSoC 2017 with The MacPorts Project. > > Call out for mentors and admin from GSoC 2015: > Jeremy, Clemens, > > Would you like to be the admin/backup admin again this year ? > > Clemens, Lawrence, Michael, Rainer, > > There are some of your ideas in the ideas list, would you like to > mentor GSoC students this year ? > > Bradley has volunteered to mentor this year. > -- Jackson Isaac
Re: introduction for gsoc
Hi Mohit, On Sun, Mar 5, 2017 at 9:18 PM, mohit ahuja wrote: > Hi, > > I am Mohit Ahuja, a student at KTH, Sweden. I am planning to join > macports for this google summer of code(GSOC 2017), as suggested I am > introducing myself. > I have programming experience of a few years and have mostly worked on Python > and C, > and also I have learnt swift and javascript. >I love both open source and mac operating system and for me macports is one of >the most valuable Open Source project on a personal level. I would like to >contribute in terms of programming. Looking forward to working with you all. > Welcome to MacPorts project. We're always happy to see new GSoC students and their enthusiasm towards open source :) You might also want to take a look a Tcl, as most of our codebase is written in Tcl. You may go through http://www.tcl.tk/man/tcl8.5/tutorial/tcltutorial.html to get started. You've probably already seen our ideas page at https://trac.macports.org/wiki/SummerOfCode. Feel free to suggest your own ideas. We are open to hear ideas from our students too. If you don't have your own idea at the moment, just read through the ideas list and see if any of the tasks might suit you. Feel free to ask here on the list, in IRC, or email the potential maintainers directly for more information. Looking forward to a great summer! Jackson Isaac
Fwd: GSoC 2017: The MacPorts Project has been accepted as a mentor organization!
Hello everyone, Happy to announce that The MacPorts Project is participating for Google Summer of Code 2017. List of selected organizations: https://summerofcode.withgoogle.com/organizations/ Forwarding the email below. Also please forward it to your friends/family/students,etc.. Looking forward to meet and work with some awesome students on macports this year :) [image: Google Summer of Code] Congratulations! The MacPorts Project has been selected as a Google Summer of Code 2017 mentor organization. -- Jackson Isaac
Re: [GSoC] Call for Mentors GSoC 2017
On Wed, Feb 8, 2017 at 4:20 PM, Rainer Müller wrote: > > As in 2015, I am happy to help with the selection of students and with > whatever comes up during the mentoring process, especially with > developing on base. Sorry, I cannot take the commitment for a full > mentorship. I would rather like to spend my spare time on other areas, > like improving our infrastructure. > So as of now we have 2 mentors (Bradley and Michael). I guess I would be the org admin if I am applying on behalf of MacPorts for GSoC. Clemens have volunteered to be a backup admin, if no one else volunteers. I would like to wait until tomorrow afternoon if another mentor comes up. I am not so sure if we should move forward or wait ? Rainer/Clemens, Maybe you could suggest in this regard ? -- Jackson Isaac
Re: [GSoC] Call for Mentors GSoC 2017
On Tue, Feb 7, 2017 at 9:38 PM, Mojca Miklavec wrote: > On 7 February 2017 at 16:25, Michael Dickens wrote: >> I'm up for being a mentor again, for the correct student. >> >> Do we have a MP GSoC website up yet? The best I can find is < >> https://trac.macports.org/wiki/SummerOfCode >, which is for 2015. > > I guess the idea is to simply fix the contents of that page (fix dates etc.). > Yes. Also, feel free to update the wiki with any ideas that come up. > Many project ideas are still valid, but we should of course add new > ones (go through the tickets and figure out what ideas are both > feasible and of great importance to the community :) and potentially > change some of the old ones (or remove them if no longer relevant). I think some of the old ideas may not be feasible since with every new edition of OS, some new features are added and accordingly we might also have to update/remove those ideas since we might not be supporting the older versions of mac os. > Some things from the top of my head (without checking feasibility or > reasonability): > - collect statistics from the buildbot jobs, track outdated ports (via > livecheck), ... to become part of a potential new website > - come up with a solution to test basic functionality of submitted pull > requests > - create various buildbot jobs that we might need (like > "automatically" creating a new release etc.) Mojca, would you like to put these ideas on our Ideas page ? and also possibly be a mentor :). > - finish the SAT solver for dependency tracking (started during 2015, > not sure about the current status) I am trying to continue the work on it in my free time, need to update myself as lot of changes were made since I last worked on macports base. I had updated the branch with master few months back and now I am working on merging it with the latest change. Some work need to be done regarding the libsolv source to match with vendor tarball PR changes. Some of the work that were left during that time were uninstall ports, variants support and to add more fields to the portfile for better search options that are supported by libsolv. There might be more things that we could do with libsolv since there has been lot of additions to libsolv source too which I feel would be easy to integrate as we now have extracted directories and latest changes can be pushed without tarring the whole thing and pushing which was an expensive overhead before. -- Jackson Isaac
[GSoC] Call for Mentors GSoC 2017
Hello everyone, As you all might be knowing GSoC season has started and they are accepting organization applications until February 9, 2017, 17:00 (UTC). I would like to invite you all and know who all would like to mentor some awesome students this year to get on-board with MacPorts. I have already started the application process by coordinating with Rainer. If we have sufficient mentors and a admin and backup admin(s), we can move ahead with the application process. Please feel free to reply to this thread if you are interested in participating as a mentor for GSoC 2017 with The MacPorts Project. Call out for mentors and admin from GSoC 2015: Jeremy, Clemens, Would you like to be the admin/backup admin again this year ? Clemens, Lawrence, Michael, Rainer, There are some of your ideas in the ideas list, would you like to mentor GSoC students this year ? Bradley has volunteered to mentor this year. -- Jackson Isaac
Re: [GSoC] Announcing Google Summer of Code 2017 and Google Code-in 2016
On Thu, Feb 2, 2017 at 9:30 PM, Jeremy Lavergne wrote: >>> As there was no reaction yet, what is the feeling about returning this >>> year? Anyone up for being the organization contact handing in the >>> application, coordinating potential mentors, and collecting ideas? >>> >> I don't have experience for applying as an organization but would like >> to volunteer for helping. > > > A concern is number of available mentors. > Is there any mentor(s) interested. If we are planning to apply this year I would be more than happy to apply as organization on behalf of MacPorts. I would also like to know the status of 2015 project on "Portfile generation framework". On GSoC 2015 website I am able to see only 2 projects (https://www.google-melange.com/archive/gsoc/2015/orgs/macports). Bradley, Can you please share if the student passed or failed the final review since you were the mentor for Portfile generation project? Also, I can update the stats on our wiki at https://trac.macports.org/wiki/SummerOfCodeOrgApplication. -- Jackson Isaac
Re: [GSoC] Announcing Google Summer of Code 2017 and Google Code-in 2016
Hi, On Wed, Feb 1, 2017 at 7:08 PM, Rainer Müller wrote: > On 2017-01-23 07:03, Jackson Isaac wrote: >> Google is accepting applications from projects. Would like to know if >> MacPorts would be participating this year ? Looking forward for an >> awesome Summer. > > We skipped last year because we felt like we had too much stuff lying > around that was not integrated into base. That turned out well, as we > were also quite busy with the migration. > Being on Github now, I think there might be much more students showing interest for contributing to our project. > As there was no reaction yet, what is the feeling about returning this > year? Anyone up for being the organization contact handing in the > application, coordinating potential mentors, and collecting ideas? > I don't have experience for applying as an organization but would like to volunteer for helping. -- Jackson Isaac
Re: [GSoC] Announcing Google Summer of Code 2017 and Google Code-in 2016
Hi, On Tue, Oct 11, 2016 at 8:13 AM, Jeremy Lavergne wrote: > GSoC 2017 is announced! > > Please add or refines ideas on the MacPorts wiki; anyone interested in > mentoring is encouraged to contact those of us regularly involved with > the program (the likely administrators): > * s...@macports.org (myself) > * c...@macports.org (Clemens) > * rai...@macports.org (Rainer) > Google is accepting applications from projects. Would like to know if MacPorts would be participating this year ? Looking forward for an awesome Summer. P.S: Not a student anymore but would like to give a helping hand if required :) -- Jackson Isaac
