On Sat, 23 Mar 2019 at 17:49, Craig Treleaven wrote:
>
> I see no reason to report inactive ports.
Neither do I. I would remove those as I already mentioned in an earlier email.
> The “OS” section for my system is:
>
> "os": {
> "macports_version": "2.5.4",
> "osx_version": "10.10",
>
On Sun, 24 Mar 2019 at 01:06, Craig Treleaven wrote:
>
> please note that we can’t expect all ports to build successfully on the
> buildbots.
Nobody said that, but we cannot blame the student collecting the data
from buildbot for macports internal deficiencies :)
> There are a number of ports th
Dear Ravi,
On Sun, 24 Mar 2019 at 13:13, Ravi Rathee wrote:
>
> Is it possible to make an android application similar to a web application
> with all the ports information and all the details. Similar to last years
> GSoC project but on Android.
While it is definitely possible to make one, its
On Sun, 24 Mar 2019 at 19:55, Craig Treleaven wrote:
> > On Mar 24, 2019, at 1:09 PM, Mojca Miklavec wrote:
> > On Sun, 24 Mar 2019 at 01:06, Craig Treleaven wrote:
>>>
>>> There are a number of ports that require a dependency to be installed with
>>>
Dear Craig,
> As you said, people have looked at this problem and not found a workable
> solution.
Personally I never did spend any effort into fixing this, partially
probably also because it doesn't affect any ports that I use or
maintain.
> It may be a _long_ time before a “proper” solution i
Dear Fred,
(Resending due to the initial post from the wrong email account; sorry
for the duplicate.)
On Sun, 24 Mar 2019 at 22:57, Fred Wright wrote:
> On Sun, 24 Mar 2019, Mojca Miklavec wrote:
> > On Sat, 23 Mar 2019 at 17:49, Craig Treleaven wrote:
> >>
> >>
Dear Karan,
Warmly welcome to the MacPorts community!
On Mon, 25 Mar 2019 at 20:36, KARAN SHETH via macports-dev wrote:
> Hey there,
> I would like to start by saying this is not GSoC Proposal as the
> subject says but I had no idea what else to call it. This is just to make
> contact with y
On Mon, 25 Mar 2019 at 01:28, Christopher Chavez wrote:
>
> Hi Mihir, I am a MacPorts user and port maintainer. I have a suggestion, but
> am not a member, so do not take my advice as canon.
>
> > On Mar 23, 2019, at 1:52 PM, Mihir Luthra wrote:
> >
> > I was thinking to add an 8th section which g
On Sun, 24 Mar 2019 at 13:06, Pierre Tardy wrote:
>
> Right.
> I would advise to start from a fresh config with a git poller a simple build
> recipe to train yourself at buildbot.
Fully agreed. For the task at hand (for the whole summer, not just for
the demo) you would only ever need portwatcher
On Tue, 26 Mar 2019 at 10:48, Rajdeep Bharati wrote:
>
> Would rewriting the waterfall view (with custom features) using Vue be one of
> the goals/stretch goals?
> And I presume that the plugin will become a part of buildbot core?
I leave that up to Pierre to answer.
My personal wish (but I lac
Dear Rajdeep,
On Sun, 24 Mar 2019 at 13:06, Pierre Tardy wrote:
>
> I would advise to start from a fresh config with a git poller a simple build
> recipe to train yourself at buildbot.
Just as a random idea (feel free to judge for yourself if this
simplification makes sense or not, you could sti
On Tue, 26 Mar 2019 at 16:07, Rajdeep Bharati wrote:
>
> In an earlier email (GSoC Tips), you told me that a basic functioning product
> (with the major features, tests & documentation) must be deployed before the
> first evaluation. Is the first evaluation the one from June 24-28?
Yes.
Having
Dear Arjunt
On Tue, 26 Mar 2019 at 07:34, Arjun Salyan wrote:
>
> Dear all,
>
> Using the valuable information and suggestions by all of you here at
> MacPorts, especially the potential mentors, I have come up with the first
> draft of my proposal for GSoC 2019.
> Link to Google Doc:
> https://
Dear Rajdeep,
On Tue, 26 Mar 2019 at 19:51, Rajdeep Bharati wrote:
>
> I have submitted a draft proposal:
> https://docs.google.com/document/d/12wRjA8sOWNOuApHZ_fm0n1aIPLVPt9Xm2yGiMwiK3AI/edit.
> Could you please provide some feedback?
Cool, thank you very much, it looks nice, please give us a
Dear Karan,
I'm just answering a small part of your question here, a bit more about upt
while CC-ing its author & potential mentor:
On Tue, 26 Mar 2019 at 18:15, KARAN SHETH wrote:
>
>
>> (Another option for a project in Python would be bringing universal
>> packaging tool [1] to MacPorts.)
>>
27;change_source'].append(GitHubPullrequestPoller(
> owner = 'halide',
> repo = 'Halide',
> token = token,
> pullrequest_filter = pr_filter,
> pollInterval = 60*5, # Check Halide PRs every five minutes
> pollAtLaunch = True))
> Rajdeep
>
> On We
Dear Mihir,
On Wed, 27 Mar 2019 at 17:25, Mihir Luthra wrote:
>
> Hi,
>
> I have shared my draft application from the GSoC dashboard.
> Please provide me with feedbacks. :)
Please note again that I'm not familiar with the contents at all, so
I'm providing just some general feedback.
What I miss
On Thu, 28 Mar 2019 at 05:12, Joshua Root wrote:
> On 2019-3-28 10:17 , Renee Otten wrote:
> > I am looking for some advice on how to deal with a port that will only
> > download a large data set (~5GB),
> > see https://github.com/macports/macports-ports/pull/3904. I assume we do
> > not necessaril
On Wed, 27 Mar 2019 at 17:13, Arjun Salyan wrote:
>>
>> - A more elaborate plan about how you plan to handle updates / keep
>> the database up-to-date. Sure, we can trigger certain actions from the
>> buildbot, but those various "actions" need to be implemented. Keeping
>> the app up to date in a s
Dear Karan,
On Thu, 28 Mar 2019 at 07:52, KARAN SHETH wrote:
> Resending the mail cause, previous mail was not sent to mailing list.
> On Wed, Mar 27, 2019 at 2:10 PM Mojca Miklavec wrote:
>
>> Dear Karan,
>>
>> I'm just answering a small part of your questi
On Thu, 28 Mar 2019 at 19:28, KARAN SHETH wrote:
> Hey,
>
> [image: Sent from Mailspring]
> On Thu, Mar 28, 2019 at 8:48 PM Mojca Miklavec wrote:
>
>
> We are looking forward. I hope that Cyril will also help with the process
> (my encounter with UPM so far was for
Dear MacPorts users & developers,
You probably noticed a slightly increased traffic on this mailing list recently.
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, wh
On Fri, 29 Mar 2019 at 09:18, Pierre Tardy wrote:
>
> My fear is that this is part of the many stretch goals, and this is beginning
> to be very optimistic schedule.
> I think it is best to make a great finished GSoC rather than lots of very
> cool but unfinished mini projects.
I would say that
On Sat, 30 Mar 2019 at 12:54, Arjun Salyan wrote:
>
> Hi,
> I have installed an ajax based search box in the demo app:
> https://frozen-falls-98471.herokuapp.com
Cool, I like it, thanks!
The next "feature request" would probably be to allow search through
descriptions as well :)
Anyway, I'm just
Dear Satryaji,
On Fri, 29 Mar 2019 at 09:35, Satryaji Aulia wrote:
>
> Hi Marcus, I’m a final-year student from University of Indonesia interested
> in contributing to MacPort, and I’m working on my proposal right now.
>
> I’d like to ask about the Phase out dependency on Xcode project idea on t
On Sat, 30 Mar 2019 at 21:59, Arjun Salyan
wrote:
>
> Thanks Mojca, I will update the Demo App with the suggested changes very
> shortly.
>
> On Sat, Mar 30, 2019 at 8:30 PM Mojca Miklavec wrote:
>>
>> Anyway, I'm just curious: what's the current situ
On Mon, 1 Apr 2019 at 06:34, Ken Cunningham wrote:
>
> I doubt this is possible, but it strikes me that a number of big ports, like
> clang-8.0, are actually forced in the portfile to build against libc++.
>
> And my 10.6.8 system is configured to use stdlib=libc++.
>
> But base can't rationalize
Dear Karan,
Just a few quick notes (for others as well).
On Sun, 31 Mar 2019 at 22:00, KARAN SHETH via macports-dev wrote:
>
> I have uploaded the project.
> Macports-Backend : https://github.com/Korusuke/upt-macports
> NPM-Frontend : https://github.com/Korusuke/upt-npm
Awesome, thank you very
Dear Satryaji,
On Sun, 31 Mar 2019 at 21:37, Satryaji Aulia wrote:
>
> - Xcode detection
>
> The detailed explanation is helpful and it clarifies a lot. So to me it seems
> like the core solution of the problem is simple but the extended
> functionality (trace mode) is a bit more complex. I'll r
On Mon, 1 Apr 2019 at 16:38, Renee Otten wrote:
>
> there is a figure showing a WebUI that is not described (personally I am not
> sure if that would be needed anyway).
My assumption was that Karan planned to submit "an alternative"
proposal for another project (web app), but I might be wrong.
M
Dear Pierre,
On Mon, 1 Apr 2019 at 17:06, Pierre Tardy wrote:
> In buildbot, there is no difference between author and commiter, we only
> keep the author.
> Do you think committer info is really needed?
>
This has nothing to do with the project proposal at hand, but yes, this
would be super use
On Mon, 1 Apr 2019 at 16:37, Rajdeep Bharati wrote:
>
> I have set up a simple datepicker widget with view #1. See the demo in the
> video below.
Awesome, thank you!
This would probably be something very useful for any project using
buildbot, not just for us.
> Screen Recording 2019-04-01 at 8.
Dear Rajdeep,
On Mon, 1 Apr 2019 at 17:47, Rajdeep Bharati wrote:
>
> Yes, I think so. But I have done `buildbot restart master` several times
> after that.
Did you also delete the database?
Merely restarting the configuration should not delete old build results.
Mojca
Dear Satryaji,
On Mon, 1 Apr 2019 at 21:29, Satryaji Aulia wrote:
>
> Hi again Mojca and Marcus.
>
> >> I notice how useful a "port bump" command would be if it existed.
> >
> > Yes, it would be.
>
> I've started my implementation, under macports-base/src/port1.0/portbump.tcl.
Cool!
> Besides th
On Mon, 1 Apr 2019 at 18:52, Rajdeep Bharati wrote:
>
> When I would be configuring the real (production) macports buildmaster, then
> would the old database be used?
Not if you deploy it on a fresh server, unless you explicitly put the
database there (import it from elsewhere).
(I don't know ho
Dear Arjun,
On Mon, 1 Apr 2019 at 18:38, Arjun Salyan
wrote:
>
> Hi,
> I was working on keeping the PortIndex updated, and was able to achieve this:
>
> Sync Portindex from
> 'rsync://rsync.macports.org/macports//trunk/dports/PortIndex_darwin_16_i386/PortIndex'
> Update or Add ports that were re
On Tue, 2 Apr 2019 at 01:33, KARAN SHETH wrote:
>
> Is it possible to rename the existing Python ports as per PYPI so that
> issues of duplicates ports can be avoided?
>
Yes, I would be in favour of coming up with an "algorithm" for naming all
python ports and then stick to it. Ports which don't
On Tue, 2 Apr 2019 at 16:01, Pierre Tardy wrote:
>
> Not sure if this is applicable, but there is no import method from
> buildbot 0.8.x to buildbot 0.9+
I don't believe we really need that.
It would be nice to "export" all the relevant (summary) data once
before decommissioning the old master (o
Dear Karan,
you may put such statistics and suggestions for action plans in the
proposal (or appendix to proposal).
What about pypackage -> py-pypackage? (I miss such entries on the list,
unless those are the ones you intentionally didn't count.)
Did you ignore capitalisation of names?
Mojca
On
Dear Karan,
On Fri, 5 Apr 2019 at 08:25, KARAN SHETH wrote:
>
> Hey,
>
> So I tried porting upt and in the process had to port spdx-lookup and spdx.
> These are the portfiles for the same [1],[2],[3].
>
> When I try to install upt there is no error message but while trying
> to run upt via a term
On Fri, 5 Apr 2019 at 09:16, KARAN SHETH wrote:
> On Fri, Apr 5, 2019 at 11:59 AM Mojca Miklavec wrote:
> >
> > Dear Karan,
> >
> > No time to test now, but what does "port contents py37-upt" say? It
> > could be called upt-py37 or something. That'
On Sat, 6 Apr 2019 at 04:06, Cyril Roelandt wrote:
>
> Upt gives you three kinds of dependencies: build, runtime and test. This
> should be done in the backend.
MacPorts also splits "runtime" dependencies into two types. One are
proper runtime dependencies (not needed for building the package
itse
Dear Rajdeep,
On Sat, 6 Apr 2019 at 13:33, Rajdeep Bharati wrote:
>
> I was wondering what kind of features you would like to have in the new
> waterfall view?
I don't remember whether I ever explicitly said I wanted some new
features there :)
Probably the only thing I really miss is the portna
On Sat, 6 Apr 2019 at 13:54, KARAN SHETH wrote:
>
> I would also like to ask if anything else needs to be added or updated
> in the proposal as the deadline is nearing.
There's nothing specific that I would want to comment on.
Well, to me it's not entirely clear how the automatic updates would be
Dear Davide,
On Sun, 7 Apr 2019 at 09:40, Davide Gerhard wrote:
>
> Seems that macports-dev@ has not received my proposal (sent yesterday);
> moreover, mailman does not answer to my command or only after some hour.
This is strange and might need to be put to attention of our
infrastructure team.
Dear Amir,
Nice to see you at MacPorts!
You should send your email to the macports development mailing list
and you would get the answer there. (I'm forwarding it to the mailing
list now, but you should subscribe for the future.)
On Sat, 6 Apr 2019 at 20:14, AmirAli Mashayekhi wrote:
>
> Dear Ma
Dear Davide,
On Sun, 7 Apr 2019 at 12:55, Davide Gerhard wrote:
> On Sunday, 07/04/2019 11:55 CEST, Mojca Miklavec wrote:
> > On Sun, 7 Apr 2019 at 09:40, Davide Gerhard wrote:
> >>
> >> Sorry, I am late but I saw only the other day that MacPorts
> >> part
On Sun, 7 Apr 2019 at 20:25, Christopher Chavez wrote:
>
> Currently, comments in Portfiles containing dates, such as for when remove
> something in the future, are specified in whichever scheme preferred by the
> port maintainer or whoever inserted the date. Some of these schemes are
> region-
On Mon, 8 Apr 2019 at 07:35, Joshua Root wrote:
>
> ISO 8601 is a great compliant solution to recommend.
>
> Changing ambiguous dates to something unambiguous is a reasonable thing
> to submit PRs for if you so desire.
Ambiguous dates can be verified with "git log".
But I would do a PR for everyt
ar,
but properly doing this one task would also take a while and could be
a separate task.
(You don't have much time left until the proposal deadline though.)
Mojca
> My proposal link :
> https://docs.google.com/document/d/1RUmFN7PSPqbGzH4h8Hqq-qkTFgS3XJ_bIrsq7GhikYE/edit?usp=sharing
On Sun, 7 Apr 2019 at 16:36, Satryaji Aulia wrote:
>
> Hi Marcus and Mojca.
>
> I’ve fleshed out my proposal (also my understanding of MacOS compilers)
> again. To disallow Xcode compilers, I added my idea to use a compiler
> blacklist which implementation already exists. I’ve also worked a lot on
Dear Rajdeep,
On Sun, 7 Apr 2019 at 19:41, Rajdeep Bharati wrote:
>
> I found something which might help us: https://bors.tech/homu-io/
> https://github.com/barosl/homu.
> I will try it set it up on my local system and get back to you.
> Mojca
This sounds nice, but I wonder if it would actually
Dear Arjun,
On Mon, 8 Apr 2019 at 20:31, Arjun Salyan wrote:
>
> Dear MacPorts Community,
>
> I have submitted my Final Proposal. I do understand that during these last
> hours it might not be possible to give feedback on the proposals. But if I am
> lucky enough to get more of them, I will try
Dear Rajdeep,
On Tue, 9 Apr 2019 at 17:27, Rajdeep Bharati wrote:
>
> Here's a poc of buildbot workers running on mac VM using libvirt (thought I'm
> not sure whether this is the kind of thing we need):
> https://github.com/nextgis/buildbot
Cool, nice find! I don't know how hard it would be to
Dear Shreyas,
Your references definitely sound compelling and I firmly believe that
you could make a wonderful project, but the two hours left before the
deadline are not anywhere near enough to prepare a solid proposal.
Proposal is not just about writing two paragraphs about yourself, you
need to
Dear Rajdeep,
On Thu, 11 Apr 2019 at 14:02, Rajdeep Bharati wrote:
>
> I had a doubt regarding the creation of buildbot 2.x Portfile: Would writing
> a Portfile be sufficient or would there need to be other changes to the ports
> tree as well?
We would presumably move the contents of the existi
Dear Arjun,
Thanks a lot for the update.
On Thu, 11 Apr 2019 at 16:15, Arjun Salyan wrote:
>
> I have added maintainer views and tables to the demo app.
>
> List of maintainers is clickable on the port-detail page.
> A maintainer-detail view that display info and list of maintained ports
Awesome
Hi,
On Sat, 13 Apr 2019 at 08:47, Joshua Root wrote:
> On 2019-4-13 07:57 , Jack Howarth wrote:
> > What will be the situation with 10.14.5 and its enforcement of
> > notarization for Applications and kernel extensions for MacPorts? In
> > particular, will the new notarization requirement li
Dear Arjun,
I'll answer individual questions & provide further suggestion separately.
Given the current state of the app with sufficient complexity, I
believe that it would be wise to introduce some unit tests to be able
to extensively test what happens with data you import, and to prevent
/ dete
On Tue, 16 Apr 2019 at 09:12, Rajdeep Bharati wrote:
>
> Hello,
> For testing a new Portfile in my local repository, the Macports guide says
> that I need to edit the sources.conf file. However, this file is locked and
> I'm not able to unlock it.
Did you try with root privileges?
I don't know
On Fri, 12 Apr 2019 at 19:50, Arjun Salyan wrote:
> On Fri, Apr 12, 2019 at 3:03 AM Mojca Miklavec wrote:
>
>> One thing that "urgently" needs to be done is to obfuscate the email
>>
>> (if written at all). I'm not even sure whether we actually want the
>
On Tue, 16 Apr 2019 at 12:38, Rajdeep Bharati wrote:
>
> I think one more port needs to be created: autobahn.
> (https://docs.buildbot.net/current/manual/installation/requirements.html)
If it's not in the ports tree yet, I believe I have this port on my
computer already. (I can check when I come
Dear Rajdeep,
On Tue, 16 Apr 2019 at 12:38, Rajdeep Bharati wrote:
>
> About the npm dependencies: Can't it be taken care of by using buildbot-www
> from pypi?
While I'm not yet sure about the npm packages situation, I looked a
bit around and bumped into
https://www.freshports.org/devel/py-b
Hi,
When we switched to GitHub Ryan made a test conversion of Trac tickets
to GitHub issues, but there were several problems with that approach,
the biggest one being inability to easily filter by ports, and
generally the GitHub's issues were less powerful than what Trac is
offering, so it made se
Dear Karan,
On Fri, 3 May 2019 at 23:27, Karan Sheth wrote:
>
> If PEAR ports are useful to the community then I would like to take
> this as stretch goals / after GSoC goal.
For anyone putting the GSOC mails to "ignore mode" due to heavy
traffic ... maybe leave the comment inside
https://git
Hi,
I lost the original thread about libgcc revbumps and good measures for
revbumping ... but it seems that all cross-compilers are now broken
and need a revbump.
Maybe we should put some comments on top of isl. From what I remember
in the past isl would also often just work with newer gcc and fo
Dear Horst,
On Sun, 5 May 2019 at 16:15, Horst Gutmann wrote:
>
> I noticed that the main website today (or yesterday) got a little
> refresh with the bright blue tone being more prominent. Is someone
> already working on updating the guide's stylesheet to also reflect that
> change?
Se the answe
Xcode.
2.) Arjun Salyan: Web App (with API) to Collect PortIndex, Build
History and Installation Statistics
Mentored by: Mojca Miklavec, Umesh Singla
A standalone Django app telling you everything about individual ports.
3.) Karan Sheth: Automating Packaging for Macports
Mentored by: Cyril Roe
Hi,
I know that our official channels only include mailing lists, IRC and
PR/ticket discussion so far, but I'm curious about your stand with
respect to setting up a service like Zulip Chat / Rocket Chat / ...
for aiding the GSOC communication when higher frequency of potentially
simple questions w
:)
I assume that we'll also want to add other items for the rest of the
summer to that list?
> @Mojca Miklavec Yesterday you mentioned:
>>
>> 16:33:15 regarding the features of the default waterfall view,
>> another problem I saw was that unless one of the builds was
On Sun, 12 May 2019 at 21:15, Clemens Lang wrote:
> On Thu, May 09, 2019 at 11:38:16PM +0200, Mojca Miklavec wrote:
> > I know that our official channels only include mailing lists, IRC and
> > PR/ticket discussion so far, but I'm curious about your stand with
> > respe
On Tue, 14 May 2019 at 19:15, Nils Breunese wrote:
>
> Slack provides shareable invite links, but they expire. This blog post lists
> some other options:
>
> https://intoli.com/blog/make-a-public-slack-community/
>
> Looks like it requires some work, but it’s possible to setup.
> Note that I don’t
On Tue, 14 May 2019 at 18:11, Rainer Müller wrote:
>
> I think Slack workspaces are also always invite only, but please correct
> me if I am wrong (maybe only for paid plans?). Assuming we might want to
> replace IRC one day as the official development and support chat, that
> would not work well.
Dear Arjun,
I'm CC-ing the list as that's potentially interesting to others as well.
On Tue, 14 May 2019 at 19:45, Arjun Salyan wrote:
> Summary of today's discussion:
>
> 1. *Repository: *The existing repository for the web app would be moved
> from the staging area to the official MacPorts org
On Thu, 16 May 2019 at 13:31, Ruben Di Battista wrote:
>
> I would like to stress once again about Matrix.
>
> If we setup Matrix, we can bridge the channels with whatever service you
> might need. First of all IRC, so people that like to keep hanging out there
> can still do it with the addition
On Thu, 16 May 2019 at 19:47, Rainer Müller wrote:
>
> I am really confused what you want to set up for Matrix?
If you are asking me ...
I don't know, I never used it and I never took a closer look, so I'm
not sure how it works.
I assumed that someone needs to configure something somewhere to
pro
On Mon, 20 May 2019 at 00:05, Mark Anderson wrote:
>
> Yeah. I don’t like that really. I’ll live with it. I think I can trigger from
> Travis, if I want to.
>
> Are we looking to move over to azure pipelines permanently or do we want to
> try and see what can be done on the Travis side.
Personal
Dear Students, Mentors & others,
We are all enthusiastic about the most productive part of the GSOC
that's officially about to start tomorrow.
We have so many projects this year that it became non-trivial to keep
all the relevant URLs in the memory. Please check if I got all the
details right:
Dear Rajdeep,
[Removing the -users mailing list as regular users should not be
concerned with ugly implementation details of MacPorts :), and CC-ing
Karan, Renee & Cyril.]
On Tue, 28 May 2019 at 08:56, Rajdeep Bharati wrote:
>
> Dear developers,
>
> I am packaging buildbot 2.x as a port. However,
On Tue, 28 May 2019 at 14:38, Ryan Schmidt wrote:
> On May 28, 2019, at 02:11, Rajdeep Bharati wrote:
>
> > I am packaging buildbot 2.x as a port.
>
> That's great, thanks. I would suggest updating (and where applicable
> renaming) the existing buildbot ports. I would not make new "buildbot2"
> p
(CC-ing Arjun as parts of this might be of interest for the app as well,
and the general mailing list as they might provide further feedback.)
On Wed, 29 May 2019 at 08:57, Rajdeep Bharati
wrote:
> Hi,
> I wanted to be sure about one thing:
> In view #2
> Screenshot 2019-05-29 at 12.21.13 PM.pn
On Thu, 30 May 2019 at 16:43, Rajdeep Bharati wrote:
>
> How do we decide which ports are supposed to be built? Is it only the ports
> (files) that are affected by a particular `change`?
We fetch a list of modified directories.
Then a bash script from mpbb runs though all of the ports in those
di
Hi,
In this case I have a feature request for Karan ...
On Sun, 2 Jun 2019 at 18:46, Ryan Schmidt wrote:
> On Jun 2, 2019, at 11:30, Rajdeep Bharati wrote:
>
> > One thing is that when I install the new py37-buildbot, the command that I
> > get to use is `buildbot-3.7`.
> > What changes do I nee
On Sun, 2 Jun 2019 at 18:30, Rajdeep Bharati wrote:
> On Sun, Jun 2, 2019 at 9:45 PM Ryan Schmidt wrote:
>
> Got it, thanks for your help. One thing is that when I install the new
> py37-buildbot, the command that I get to use is `buildbot-3.7`.
> What changes do I need to make in the port to us
Hi,
Below is a quote from
https://developer.apple.com/documentation/macos_release_notes/macos_10_15_beta_release_notes
Scripting Language Runtimes
Deprecations
Scripting language runtimes such as Python, Ruby, and Perl are
included in macOS for compatibility with legacy software. Future
versio
Dear Arjun,
Thanks a lot for sending out the report.
Dear MacPorts users,
I would warmly welcome everyone to check what has been done so far,
provide feedback, but in particular volunteer to run
sudo port install mpstats-gsoc
to help us get more statistics ready by the time Arjun starts work
Hi,
On Fri, 7 Jun 2019 at 01:49, Ryan Schmidt wrote:
>
> Originally, all-lowercase port names were encouraged, because users often
> specify port names in all lowercase and there were a few bugs in MacPorts
> when the capitalization specified did not match the capitalization used in
> the port.
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 whe
Hi,
I would like to suggest creating a super simple repository with
bootstrapping tools required to allow other project to test their
software on Travis, Azure etc. *using* MacPorts.
I imagine that it should be possible for the .travis.yml file to simply:
- copy a single file (or clone repository
be shown soon (ideally in about two weeks).
Thank you very much,
Mojca
(And of course feel free to provide feedback about the rest of the site.)
On Sat, 8 Jun 2019 at 14:52, Mojca Miklavec wrote:
>
> Dear MacPorts users,
>
> I would warmly welcome everyone to check what has been
Hi,
I wonder if the owner of macports.zulip.org is on this mailing list.
Thank you,
Mojca
Hi,
I would like to suggest providing simplification for the following four lines:
namepy-foo
version 1.2.3
master_sitespypi:[string index ${python.rootname} 0]/${python.rootname}
distname${python.rootname}-${version}
which could read like the foll
On Sun, 23 Jun 2019 at 10:43, Joshua Root wrote:
> On 2019-6-23 17:52 , Mojca Miklavec wrote:
> > Hi,
> >
> > I would like to suggest providing simplification for the following four
> > lines:
> >
> > namepy-foo
> > version
Dear Karan,
On Fri, 21 Jun 2019 at 22:56, Karan Sheth wrote:
>
>> (My next question would be if we could simply create a Docker image
>> with Ubuntu with macports "preinstalled", but that's for later.)
>
> As i wanted to try/learn docker, and this seemed like a good opportunity.
> I did this first
On Wed, 26 Jun 2019 at 16:00, Karan Sheth wrote:
> Hey,
>
> My suggestion would be: could you perhaps share the sources
>> (Dockerfile I guess; together with some basic usage instructions)? We
>> could probably add a repository under github/macports-gsoc or so. Then
>> I could at least build an im
On Wed, 26 Jun 2019 at 18:30, Karan Sheth wrote:
>
> Failed to parse file foo/bar/Portfile: MacPorts does not support qt4 on
>> platforms other than darwin
>> Failed to parse file lang/chicken/Portfile: can't read "archs()": no such
>> element in array
>>
>
> Yes it fails for around 361 ports.
>
>
Hi,
We are approaching the release of 10.15.
What are the chances to get the "port migrate" code merged before the
end of this summer and before the release of 10.15?
If we wait too long, the OS might change sufficiently that the code
will stop working one day.
Thank you,
Mojca
Dear Rainer,
(or anyone else from the infra team; I'm forwarding this to the
development mailing list as there's some more background info, I hope
that's ok)
Would it be acceptable to enable some web hooks in the base & ports
repository for testing?
On Tue, 2 Jul 2019 at 08:41, Rajdeep Bharati w
On Sun, 30 Jun 2019 at 14:00, Clemens Lang wrote:
>
> On Sat, Jun 29, 2019 at 11:58:04PM +0200, Mojca Miklavec wrote:
> > We are approaching the release of 10.15.
> >
> > What are the chances to get the "port migrate" code merged before the
> > end of thi
Dear Karan,
On Wed, 26 Jun 2019 at 16:00, Karan Sheth wrote:
>
>> My suggestion would be: could you perhaps share the sources
>> (Dockerfile I guess; together with some basic usage instructions)? We
>> could probably add a repository under github/macports-gsoc or so. Then
>> I could at least build
201 - 300 of 730 matches
Mail list logo
