Re: XZ Utils Compromised Releases

On 29/03/2024 18.52, Blair Zajac wrote: > In https://www.openwall.com/lists/oss-security/2024/03/29/4 >  it says > > == Bug reports == > > Given the apparent upstream involvement I have not reported an upstream > bug…. > > >

Re: XZ Utils Compromised Releases

On 29/03/2024 18.40, Fred Wright wrote: > > On Fri, 29 Mar 2024, Frank Dean wrote: > >> I received a security announcement on the Debian mailing list [1].  It >> appears versions 5.6.0 of XY Utils and later may be compromised.  I >> also found a discussion on Openwall [2]. >> >> >> [1]: >>

Re: Getting updated cargo.crates

On 30/11/2023 18.46, Austin Ziegler wrote: > I was opening a new PR to update a Rust dependency today and could not > figure out how to update the `cargo.crates` section. Digging through the > cargo-fetch portgroup pointed me > to  >

Re: Help with zef Portfile

On 25.11.23 16:07, Joshua Root wrote: The default destroot phase builds a string to pass to 'system' by combining destroot.cmd, destroot.args, etc. In this case, it might be easiest to use those for the rakudo command, and create the symlinks in a post-destroot block? Also note that all

Re: More classes of maintainer

[Resending, K-9 Mail from mobile sent it with an empty HTML version.] On 06/11/2023 12.49, Mark Anderson wrote: > The other thing that is different now is GitHub issues and projects have > come a long way in terms of features - we can probably implement > everything we do on Trac on Github as

Re: More classes of maintainer

On November 6, 2023 12:49:26 PM GMT+01:00, Mark Anderson wrote: >The other thing that is different now is GitHub issues and projects have >come a long way in terms of features - we can probably implement everything >we do on Trac on Github as well. Well, that is what I was asking... I am not

Re: More classes of maintainer

On 02/11/2023 21.19, Herby G wrote: > I actually do think moving tickets and issues from Trac to GitHub Issues > is a good idea, and would increase engagement for the project. We evaluated this option thoroughly back in 2016 when we moved the code repositories to GitHub. As far as I remember it

Re: `port archive` ?

On 20/10/2023 15.14, René J.V. Bertin wrote: > It happens that I'd like to "install" a variant of a self-built port without > actually activating it (e.g. when libraries are in use and I have no > immediate need to activate that different variant). > > Looking through the code I saw there must

Re: accessing $argv0 from Portfile?

On 15.08.23 15:01, René J.V. Bertin wrote: Is there a way to get the path to MacPort's tclsh interpreter from within a Portfile, other than by using a `glob` to find it in $prefix/libexec/macports/bin ? (not to do anything naughty, just to run a Tcl test/benchmark.) You can use

Re: Read environment variables from a file in launchd?

On 17/07/2023 20.58, Zhenfu Shi wrote: > I’m looking for a way to import environment variables for a process started > by launchd. systemd on Linux has EnvironmentFile key which allows env vars to > be read from a file, can launchd do something similar? > I’m asking this because my cloudflared

Re: iTerm2

On 23/06/2023 02.06, Mark Anderson wrote: > iTerm2 is getting increasingly hard to support building using macports > to where I'm not even using the build - I've just been trying to fix it. > The big issue is that building it on the latest box with the latest > Xcode works great, but the developer

Re: Xcode (14.0.1) is too old

On 01/11/2022 14.02, Chris Jones wrote: > Xcode 14.1 is indeed the recommended version for macOS13, as its the > only one containing the macOS13 SDK (AKAIK). However, Apple apparently > hit a few issues with it last minute and thus has not released a public > version of it yet, so for now you need

Re: revision control downloads

On 22/03/2022 22.23, Ryan Schmidt wrote: > On Mar 22, 2022, at 13:08, Daniel J. Luke wrote: > >> On Mar 21, 2022, at 9:20 PM, Ryan Schmidt wrote: >>> Ports that fetch their sources from a revision control system do not enjoy >>> the protection of checksums. Although ports that fetch source from

Re: code signing and the future of MacPorts

Hello, here is an older concept from 2016 I had written for gdb/lldb as Apple began to require code-signing for debuggers. This applies to more actions by now, but with the same requirements. The replies are also relevant and discuss alternatives.

New project member: judaew

Please join us in welcoming the following new MacPorts project member: - Vadim-Valdis Yudaev (judaew@, @judaew) We look forward to continued excellent contributions from these new team members. - Joshua, Ryan, and Rainer Do you want to join the MacPorts team? If you would like to be

PackagingCon 2021

Hello, on November 9 & 10 this year there will be the first PackagingCon, a virtual event to bring developers from different projects together. The organizers are still looking for submissions on packaging related topics in slots of 20-30 minutes. As it is a virtual event, all presentations will

Re: New ports.macports.org website

On July 20, 2021 1:15:50 AM GMT+02:00, Saagar Jha wrote: >This looks awesome! We had some discussion earlier of what kinds of >things we should be posting to social media, and I think major new >redesigns and efforts at modernization are a great thing to highlight. >I’d suggest posting this to

Re: delete in post-destroot is ineffective, how to make it effective?

On 12/07/2021 11.49, Jim DeLaHunt wrote: > I am breaking a single upstream codebase into subports. I want each > subport to contribute some of the overall complement of files. But the > "make install" of the codebase installs more files than I want. Thus I > think the right thing to do is to

Re: Segfaults on FreeBSD

On 24/06/2021 03.30, Marius Schamschula wrote: > I’m a gdb noob, particularly as it relates to Tcl scripts. Of course you could also achieve the same checks by adding some printf statements to the C source. :-) > When I load > > gdb /opt/local/libexec/macports/bin/tclsh8.5 ./tclsh8.5.core > >

Re: live check fetch failures

[resent because the list address in CC was wrong] On 19/06/2021 17.02, Ken Cunningham wrote: > I don't subscribe to any of MacPorts' email lists, or any others. > > So any comments come in new. Didn't realize that was troubling anyone, > but thank for letting me know it is. If you are not

Re: Segfaults on FreeBSD

On 19/06/2021 17.58, atmail.dreamhost.com wrote: > Every now and then I try to get MacPorts to build and run on FreeBSD. > > Getting it to build requires less than a handful of edits. > > However, when running portindex I get a Segfault with a Signal 11. > > Here’s what gdb says (after

Re: Old Macports Site

Please use Reply All to keep the discussion on the mailing list. On 06/06/2021 19.59, Jonathan Moore wrote: > where are the guides and category lists > > I can't find anything with the new search > > > Thank You, > > > Jonathan Moore Sorry, I still do not understand. Which search do you

Re: Old Macports Site

On 06/06/2021 02.38, Jonathan Moore via macports-dev wrote: > Would you please put the old MacPorts Site up with all of the detail so > people can continue reading the mac internals. Which site do you refer to? As far as I am aware, we did not remove anything. Rainer

Re: MacPorts Base: Support for a lower level of debug output, like ui_trace, or ui_debug2/ui_debug3?

On 24/05/2021 17.13, Christopher Nielsen wrote: > Has there been any thoughts/interest in implementing another level (or two) > of debug output, providing more detail than we get at Debug? That would allow > us to optionally output more diagnostic info in various areas, such as our >

Re: MacPorts 2.7.1 - Availability for GitHub CI Jobs, as well as Buildbots?

On 27/05/2021 20.10, Ryan Schmidt wrote: > On May 27, 2021, at 02:34, Joshua Root wrote: > >> On 2021-5-27 08:52 , Christopher Nielsen wrote: >>> While I realize MacPorts 2.7.1 was just released, is there an ETA on when >>> it will be available for both CI, as well as our buildbots? >>> There’s

Re: Freenode IRC

On 26/05/2021 11.19, Joshua Root wrote: > On 2021-5-26 14:39 , Thomas R. Murphy wrote: >> As continued malicious behavior continues on the current network for >> #macports, I'm quite interested in seeing a move for the project. I agree, it is about time now. > The channel is all set up on

Re: bash and bashdb ports

On 21/05/2021 14.48, Giuseppe 'ferdy' Miceli wrote: > could someone be so kind to enlighten me about the bash port? > > if i am not mistaken the bash50 sub-port is obsolete and could be removed. > > i stumbled on it while installing bashdb which depends on bash50 which > conflicts with bash. >

Re: Freenode IRC

On 19/05/2021 20.25, Andrew Janke wrote: > Have you considered using ZNC or another IRC "bouncer"? It'll retain and > replay history for you so you can get offline messages and have a > consistent message history between computers and devices. Pretty easy to > install if you have a Linux server

Re: Freenode IRC

On 19/05/2021 15.43, Marius Schamschula wrote: > It has come to my attention, on Twitter, that freenode.net > , were MacPorts hosts it’s IRC channels, is having > some serious issues [1]. The admins have resigned and control may now be > in questionable hands. Right, we need

Re: Publicizing MacPorts

On 20/04/2021 12.40, Steven Smith wrote: That’s begging the question of an effective communications strategy. A distributed model of random volunteers is perfect for aggregating git commits. It’s highly ineffective at communicating important news from that organization. If MacPorts wants to

Re: Publicizing MacPorts

On 19/04/2021 15.14, Steven Smith wrote: If you have contacts to tech reporters, please use them. I don't have any. If Ars Technica or any other news site wants to cover MacPorts, they can do that any time. This is the wrong attitude. MacPorts must tell them, not some random

Re: Publicizing MacPorts

On 19/04/2021 12.45, Steven Smith wrote: "Champion" how? "MacPorts should be making [the case]" how? The same way everyone else does: make noise, push news, promote, let the tech reporters know. Follow the Woody Allen rule for success. If a comparable announcement to this was made for

Re: port status process question

On 17/04/2021 14.59, tsteven4 wrote: What is the reason that the recent builds of gpsbabel_app from gpsbabel: update to 1.7.0 · macports/macports-ports@2c4528c · GitHub don't show up on Install

Re: map download link to distname

On 07/04/2021 08.04, Ryan Schmidt wrote: > On Apr 6, 2021, at 10:44, Rainer Müller wrote: > >> On 06/04/2021 01.39, Ryan Schmidt wrote: >>> Regarding the specific download link you mentioned, >>> https://gitlab.com/graphviz/graphviz/-/package_files/8183714/

Re: map download link to distname

On 06/04/2021 16.38, Jonathan Stickel wrote: > On 4/5/21 17:39, Ryan Schmidt wrote: >> master_siteshttps://gitlab.com/graphviz/graphviz/-/package_files/${package_id}/download?dummy= >> > > Thank you, this is the piece that I was missing. I was not familiar with URL > query strings. Maybe this is

Re: map download link to distname

On 06/04/2021 01.39, Ryan Schmidt wrote: > Regarding the specific download link you mentioned, > https://gitlab.com/graphviz/graphviz/-/package_files/8183714/download, I see > that link on the graphviz web site at > http://www.graphviz.org/download/source/ but I don't know where they got it. >

New project member: harens

Please join us in welcoming the following new MacPorts project member: - Haren Samarasinghe (harens@, @harens) We look forward to continued excellent contributions from these new team members. - Joshua, Ryan, and Rainer Do you want to join the MacPorts team? If you would like to be

Re: Looking to resolve Qemu on AppleSilicon build failure

On 18/02/2021 05.23, Joshua Root wrote: > On 2021-2-18 08:33 , Blake Garner wrote: >> I have been unsuccessfully trying to figure out how to resolve this issue >> with >> qemu builds on AppleSilicon hardware. >> >> https://trac.macports.org/ticket/62116 >>

Mails rejected today due to SpamCop blocklist

Hello, there was a problem with our mail server today. Any mail handled today may have been rejected in error due to a problem at the SpamCop blocklist. Their domain name expired, which had the effect that all sending IPs were blocked. For mailing list posts sent today, please look for any

Re: Desolate Condition

On 26/01/2021 16.12, Christopher Nielsen wrote: > One advantage that HomeBrew does have, though, is cachet: There are so many > times when articles - or even organizations, such as Google - simply recommend > using HomeBrew… with no mention of MacPorts. > > So, my feeling is that we need to up

Re: ACTION REQUIRED: Set your SMTP password

On 18/11/2020 19.14, Mojca Miklavec wrote: > I sent my previous email using the new SMTP settings from GMail, but I > didn't see any reply, so I went to check the mailing list archives to > see whether my email went through, to start with. > > Given that the email reached the mailing list,

Re: Scheduled downtime on Jun 11, 8 UTC

On 08/06/2020 20.03, Rainer Müller wrote: > it has been a while since we did a full operating system upgrade on our server > braeburn.macports.org, which provides most of our self-hosted services. We are > taking the opportunity to do so this Thursday. As the duration is hard to > pred

Scheduled downtime on Jun 11, 8 UTC

Hello, it has been a while since we did a full operating system upgrade on our server braeburn.macports.org, which provides most of our self-hosted services. We are taking the opportunity to do so this Thursday. As the duration is hard to predict, the end date is a conservative estimation.

Re: make xorg-server a dependency of x11 ports?

On 20/05/2020 15.30, Ken Cunningham wrote: > Should xorg-server should be made a dependency of some key x11 component, so > that when people install an x11 application, xorg-server installs and it > actually works for them “out-of-the-box”. I doubt even with the dependency it will not work "out

Re: Github macportsbot not running

On 29/04/2020 04.07, Chris Jones wrote: > Looks like the macportsbot has stopped running again , as The latest MRs are > no longer being labelled. Could someone kick it back into life ;) Thank you for the notification! I started it now. prbot had failed to start after a reboot of the host

Re: A currently unstable CI?

On 03/04/2020 11.20, Ryan Schmidt wrote: > True, but 10.15 is missing because we have failed to produce a 10.15 version > of MacPorts base for it to use. Short term, we should do that. Long term, we > should fix it so that the CI systems can use the standard version of MacPorts > base and don't

Re: Port mechanism explanation needed

On 24/03/2020 17.33, 陈国凯 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

Re: Migrating the guide to AsciiDoc

On 21.02.20 21:05, Rainer Müller wrote: > On 17.02.20 23:13, Mojca Miklavec wrote: >> I didn't yet check how the latest conversion looks like, so I cannot >> really make a good informed decision, but I would vote for proceeding >> with .adoc. > > For comparison, I

Re: Migrating the guide to AsciiDoc

On 17.02.20 23:13, Mojca Miklavec wrote: > I didn't yet check how the latest conversion looks like, so I cannot > really make a good informed decision, but I would vote for proceeding > with .adoc. For comparison, I just put the AsciiDoc based guide online here: https://guide-test.macports.org/

Re: Gitlab

On 16.02.20 17:02, Mark Brethen wrote: > How would you set up a portfile to fetch from gitlab? > Example: https://gitlab.com/DavidGriffith/frotz If you navigate to the release, you will find the associated assets. If the project does not provide a release tarball there, you can use an

Re: Migrating the guide to AsciiDoc

On 25.04.18 04:35, Rainer Müller wrote: > On 2018-04-22 09:29, Mojca Miklavec wrote: >> As requested during yesterday's meeting, here's the result of >> automatic conversion of our guide from xml (docbook) to asciidoc: >> >> https://github.com/macports/macports-g

New project member: ra1nb0w

Please join us in welcoming the following new MacPorts project member: - Davide Gerhard (ra1nb0w@, @ra1nb0w) We look forward to continued excellent contributions from these new team members. - Joshua, Ryan, and Rainer Do you want to join the MacPorts team? If you would like to be considered

Re: right way to add a library to src/

On 16/01/2020 13.20, Mihir Luthra wrote: > I was trying to add some code to a new directory in macports-base/src/ dir > such > that I can use it in both porttrace.tcl(as a tcl cmd) and darwintrace.c. > > Basically it is a library that needs to be dynamically generated(because it > uses >

Re: invalid certificate chain during port-fetch

On 29.12.19 10:50, René J.V. Bertin wrote: > On Saturday December 28 2019 21:51:07 Ryan Schmidt wrote: > >> If I understood the patch correctly, it adds a fallback so that if fetching >> via the curl library fails, then it tries fetching via the curl command line >> program. To my knowledge

Re: Developer mode

On 20/11/2019 01.21, Ralph Seichter wrote: > * Ryan Schmidt: > >> We might also add a way for a developer to indicate for which ports >> developer mode should be turned on. A developer might wish, for >> example, to be notified of issues relating to the ports they maintain >> but not the ports

Re: Outage of braeburn.macports.org

Hello, something similar as in August happened today and I issued another reset of the machine. I already started prbot manually, as it tried once again to start before postgres was running. I am only on my phone, so I could not fix it properly right away. Please check if any other service

Re: Github CI/CD

On 17/08/2019 21.33, Mark Anderson wrote: > So I got let into the beta and I messed around a bit. > > https://github.com/markemer/macports-cicd-test/commit/3afe383d66fc1c073bf33af821fc6701e4b9acc0/checks > > I was able to get macports-base to build. In 2 min. I'm going to give regular > Macports

Outage of braeburn.macports.org

Hello, according to monitoring, braeburn went down at 2019-08-17 06:10 UTC for an unknown reason. When I noticed the downtime, I was unable to find out any more clues and issued a hardware reset of the server some time at around 09:30. It booted normally and logs had no hint to what had happened.

Re: Setting up port builds on Azure using master branch of macports

On 2019-08-09 11:23, Ruben Di Battista wrote: What are the longest ports to build? In my experience paraview and mame, also probably the compilers. And they should fit the 360 minutes, right? I do not think any single port build will take that long. However, we first need to install all

Re: Setting up port builds on Azure using master branch of macports

On 04/08/2019 17.34, Ryan Schmidt wrote: > On Aug 1, 2019, at 10:50, Blair Zajac wrote: > >> Why Azure? > > We already use Azure to test pull requests, but we test against the released > version of MacPorts base, currently 2.5.4. I guess Mojca is suggesting we add > another builder that uses

Re: Request for enabling some web hooks for the new buildbot test setup

On 02/07/2019 09.41, Mojca Miklavec wrote: > 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 wrote: >> On Tue, Jul 2, 2019 at 11:21 AM Rajdeep Bharati wrote: >>> >>> Hi, >>> I had a query: are webhooks

Re: macOS 10.15 Read Only root

On 30/06/2019 04.15, Ryan Schmidt wrote: > On Jun 29, 2019, at 19:53, Mark Anderson wrote: > >> Do we have any plans with how to deal with 10.15 not allowing us to create >> /opt if it doesn’t exist? Or does /opt just come with the file system? I >> can’t remember. > > macOS does not come with

Re: Slack-like chat (also for GSOC)

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

Re: Slack-like chat (also for GSOC)

On 14.06.19 11:10, 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

Re: upt-macports project update and feedback request

On 06.06.19 04:36, Karan Sheth via macports-dev wrote: > Community feedback is requested on the following topics: > > 1. The naming convention of Python ports > For upt to be able to process dependencies correctly and add missing > packages recursively, it is important to have a consistent naming

Re: openssl source install with trace mode bugged

On 03.06.19 15:50, Mihir Luthra wrote: > I noticed that on a “new" MacPorts installation, if we try to install > openssl with flags   -st, it will fail. > > Problematic lines in main.log with debug on are :- > > :info:configure darwintrace[30583:0x10fc915c0]: >

Re: Mail delivery of macports-changes disabled for Gmail users

On 03.04.19 01:07, Ryan Schmidt wrote: > This happened again yesterday. And again today... :-/ Because I am clearly not making progress here, if anyone wants to help this would be the script that wraps git-multimail to handle the mails to macports-changes:

Re: Packaging buildbot-www

On 28.05.19 09:11, Rajdeep Bharati wrote: > I am packaging buildbot 2.x as a port. However, a key part of buildbot 2 > is the web interface, buildbot-www, which uses many javascript > dependencies (those aren't available as MacPorts packages yet). Please > find the attached image which shows the

Re: URGENT -- massive merge commit on macports/macports-ports

As a reference for everyone, we are talking about this commit in this thread: https://github.com/macports/macports-ports/commit/8636b39946229023fecc2c8c5d99be1b0a0bccd1 On 22.05.19 01:06, Christopher Jones wrote: > Its a merge commit, i.e. the committer at some point pulled in changes to a >

Re: PRs

On 19.05.19 20:40, Mark Anderson wrote: > Who is currently working on out CI/CD stuff like Travis, etc? And where > is it? There are some things I'd like to propose/do, like making the > maintainer timeout label automatic and making it possible to re-run CI > from GitHub commits. The bot is

Re: PRs

On 19.05.19 20:45, Christopher Chavez wrote: > On 5/19/2019 1:40 PM, Mark Anderson wrote: >> making it possible to re-run CI from GitHub commits. > > As a PR submitter, one workaround I'm aware of is rebasing the PR > commit(s). I'm not sure that's something members can/should try though, > so a

Re: Slack-like chat (also for GSOC)

On 18.05.19 00:04, Rainer Müller wrote: > On 17.05.19 23:54, Umesh Singla wrote: >> I tried setting one up. Well, it only takes one to sign up (email >> optional) and create rooms. Please give it >> a try: https://riot.im/app/#/room/#macports-public:matrix.org. This >> o

Re: Slack-like chat (also for GSOC)

On 2019-05-14 22:32, Mojca Miklavec wrote: On Tue, 14 May 2019 at 18:11, Rainer Müller wrote: >>> Would it be realistic to install such a service on breaburn if needed? >>> (Or is it too complex / too much work?) >> >> I'd prefer a SaaS offering her

Re: Slack-like chat (also for GSOC)

On 2019-05-14 18:11, Rainer Müller wrote: For the self-hosted options, Rocket Chat would be an option. However, when we used it at work, after a while I started to miss some kind of threading for longer conversations. Although we also usually do not have long conversations or that much

Re: Slack-like chat (also for GSOC)

On 12.05.19 21:49, Mojca Miklavec wrote: > 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

Re: New Portfiles

On 11.03.19 01:13, MacPorts wrote: > I don't remember why I ended up making a new port for html-tree. > > There seem to be two different modules at cpan that use the name > Web::Scraper. One uses Web::Scraper::LibXML. The port I created includes > the module that uses Web::Scraper::LibXML. It is

Re: Google Summer Of Code

On 28.02.19 10:35, Mojca Miklavec wrote: > Dear Ryan, > > On Thu, 28 Feb 2019 at 02:39, Ryan Schmidt wrote: >> On Feb 27, 2019, at 17:07, Mojca Miklavec wrote: >>> >>> Now it's really time to: >>> - Put a short news with a logotype on at least https://www.macports.org >>> (Ryan?) >> >> I don't

Re: Mail delivery of macports-changes disabled for Gmail users

On 26.02.19 02:55, Zero King wrote: > CCing the author would send the email to them, right? I don't want to > receive these emails, and PR authors could be confused when receiving > these emails. Yes, you are right. Thanks for pointing this out. Using CC is not a solution. The goal [1] was to

Mail delivery of macports-changes disabled for Gmail users

Hello, if you are using Gmail or a Google hosted mail service for your domain, your subscription to the macports-changes mailing list was likely disabled on 2019-02-22 by mailman due to "excessive or fatal bounces". If you still want to receive the mailing list, but are currently not getting the

Re: Universal packaging tool (for pypi, cpan, ruby, ...)

Hey, On 12.02.19 03:40, Cyril Roelandt wrote: > I'm the author of upt. Thanks for joining the discussion! > On 2019-02-10 21:24, Mojca Miklavec wrote: >> Hi, >> >> Last week I was sitting in cafeteria with the author of a new python >> package "upt" (Universal packaging tool) whose aim is to

Re: Tcl removes a level of backslashes when accessing a string as a list

On 02.02.19 02:52, Ryan Schmidt wrote: > You'd think I'd understand tcl's lists and strings by now. But no. A list is > a string and a string is a list. Or maybe it isn't. > > I'm having trouble with livecheck.regex. Since it's a regular expression, > it's pretty common for it to contain

Re: Q about a (new) portgroup file

On 27.01.19 14:33, Eric F (iEFdev) wrote: > > On 1/27/19 14:21 , Christopher Jones wrote: >> If you don’t think it is quite ready, but you want to start to get >> feedback, then that is exactly with WIP PRs are for. Just remember to >> start the title with ‘WIP” and also add the wip label to the

Re: depspec generator?

On 14.01.19 10:33, René J.V. Bertin wrote: > I think MacPort "base" already has most of the code required to generate a > depspec list from a new/upgraded port's destroot, as a means of verification > and convenience for port maintainers. (A bit like my own > port-check-conflicts.tcl >

Re: Online MacPorts meeting? This Saturday?

On January 10, 2019 10:00:54 PM GMT+01:00, Mojca Miklavec wrote: >Should we stick with 15:00 (3 p.m.) UTC for the meeting or does anyone >have any other requests? > >For those who can attend, please raise your hands (publicly or >privately). Works for me, I will attend. >We met via Google

New project member: mark

Please join us in welcoming the following new MacPorts project member: - Mark Anderson (mark@, @markemer) We look forward to continued excellent contributions from these new team members. - Joshua, Ryan, and Rainer Do you want to join the MacPorts team? If you would like to be considered for

Scheduled downtime on Dec 14

Hello, due to maintenance on the network in the data center where our server is hosted, there will be a 20-minute disconnection in the time frame given below. Start: 2018-12-14 03:00:00 UTC End:2018-12-14 05:00:00 UTC (expected) This will mostly affect the website, Trac, and the mailing

Re: macports rot

On 03.12.18 17:00, Jonathan Stickel wrote: > I would like to express some concerns about trends I've noticed in the > Macports community. I've been a Macports user and contributor for many > years. I understand the imperfect nature of open-source projects run by > volunteers. Interest and

Re: extract gzip files

On 30.11.18 18:09, Mark Brethen wrote: > This doesn’t work: > > extract.suffix= .gz > extract.cmd = gunzip > extract.pre_args = -c > extract.post_args = "> ${workpath}" This cannot work as ${workpath} is a directory and you cannot redirect output to a directory, you

Re: trying to understand the --no-exec activate option (on by default?)

On 29.11.18 22:59, René J.V. Bertin wrote: > That's what I understand from the embedded help but also what I'm trying to > confirm in the code. > As said, I'm not seeing output from post-activate phases when I reactivate a > port after having deactivated it. Have you tried unconditional output

Re: trying to understand the --no-exec activate option (on by default?)

On 29.11.18 23:25, Fred Wright wrote: > In the particular case of code signing, would it be possible to do that > in the post-destroot phase, so that the signature would remain across > activations and deactivations, or does the signature mechanism defend > against that (even though a verbatim

Re: trying to understand the --no-exec activate option (on by default?)

On 29.11.18 11:08, René J.V. Bertin wrote: > I'm trying to understand how/where the activate --no-exec option is set, I > have the impression it's on by default. To clarify the double negative here, the post-activate phase will be executed by default. Rainer

Re: Dealing with a click-through license

On 26.11.18 03:26, Randolph M. Fritz wrote: > No, you can download it. The license is an old BSD license, so it's > pretty good, but users are required to read and accept it. Is there any > way to accommodate this, or do I simply have to say that we can't > distribute a portfile for the system?

Re: convert a static library to a dynamic one?

On 18.11.18 20:36, Mark Brethen wrote: > The spooles src creates a static ‘spooles.a’ library. I want to get a dynamic > library out of it. In BSD, for a .so library you would use: > > ld -Bshareable -o libspooles.so.1 -x -soname libspooles.so.1 --whole-archive > spooles.a > > For macports I

Re: [GitHub] Subscribed to macports/macports-legacy-support notifications

On 07.11.18 22:31, Ryan Schmidt wrote: > > > On Nov 7, 2018, at 15:22, Rainer Müller wrote: > >> On 07.11.18 22:10, Rainer Müller wrote: >>> What is the plan? Should we also connect this new repository with Trac? >> >> Ah, just found the ticket: &g

Re: Macports-mgr

On 04.11.18 16:09, Mark Anderson wrote: > I sent a message to Macports-mgr in July and haven't heard back. I know > it can take a long time, but how long is a long time? It is already way too long. The goal is to answer within one week. PortMgr has failed way too often with this. In many cases it

Re: Fwd: [GitHub] Subscribed to macports/macports-legacy-support notifications

On 07.11.18 22:10, Rainer Müller wrote: > What is the plan? Should we also connect this new repository with Trac? Ah, just found the ticket: https://trac.macports.org/ticket/57537 Rainer

Fwd: [GitHub] Subscribed to macports/macports-legacy-support notifications

What is the plan? Should we also connect this new repository with Trac? Rainer Forwarded Message Subject: [GitHub] Subscribed to macports/macports-legacy-support notifications Date: Wed, 07 Nov 2018 12:47:03 -0800 From: GitHub To: rai...@macports.org Hey there, we’re just

Re: How to resolve a technical conflict

On 03.11.18 14:27, Perry E. Metzger wrote: > So an instance of something that hasn't happened much has appeared, > and I'd like some guidance both on the individual instance and on the > problem in general. [...] > 1. How does one adjudicate this particular dispute? > 2. How does one adjudicate

Re: How do base commits get released?

In addition to what Ryan already said, let me add a few more pointers. On 2018-11-02 03:41, George Plymale II wrote: > Furthermore, upon examining the commits between 2.5.3 and 2.5.4 it is > apparent that some commits on the master branch are missing: >

Re: loading checksums table from pre-checksum block?

On 2018-10-27 09:16, René J.V. Bertin wrote: > I have a port with lots of subports for which I keep the checksums in a > table-like structure in a dedicated file, so as to keep the Portfile a bit > more manageable (and to be able to generate said table with a script when > it's upgrade time). >

  1   2   3   4   5   >