gcc10 ports

Hey, I just finished to heavy rework gcc10 port and introduced the brand new gcc10-bootstrap port. Both ports is near identical in term of applied patches (to make it easy to support) and used https://github.com/iains/gcc-10-branch as source of patch

Ref: portgroups: respect subport name, when it matches project name

Hi, I need help from someone who understand how github and similar port group like gitlab works to review https://github.com/macports/macports-ports/pull/13050 It works very well locally but it may introduce some unexpected side effects.

Re: Ref: github CI: run on forks

Hi, I'd love to point your attention on this PR: https://github.com/macports/macports-ports/pull/13049 I suggest to setup a deadline to merge 1st March. -- wbr, Kirill signature.asc Description: Message signed with OpenPGP

Re: Portfile for osxphotos

Here it is: https://github.com/macports/macports-ports/pull/20416 -- wbr, Kirill > On 8. Sep 2023, at 15:46, Nils Breunese wrote: > > Kirill A. Korinsky het volgende geschreven: > >> I've used osxphotos once or twice and willing to

Regarding github CI

Folks, As you may have noticed a few weeks ago, I opened a PR https://github.com/macports/macports-ports/pull/20092 in which I propose enabling the execution of port test as part of GitHub's CI. I understand that not all ports currently

ICU 74.1

Folks, As usual the first step to update ICU is update icu-deve`. In two weeks I'll open a PR to update ICU and revbump all dependencies without testing all of them. I kindly ask maintainers to install icu-devel to catch any future issue before end users. See:

Re: Port Reclaim

you may specificly mark your port to be requested via `port setrequested blabla` -- wbr, Kirill > On 6. Nov 2023, at 11:39, Mark Anderson wrote: > > I'm noticing that port reclaim routinely is asking to uninstall all my ports. > And this is not post migration. The rest of the command works as

Re: Port Reclaim

are you sure that you have migrated list of requested ports as well? As far as I recall the list of requested ports are migrated at separetly steps. Otherwise it should be expected and default behaviour to mark something as requested when you install it via `port install blabla` -- wbr, Kirill

Re: Updating openjdk8 to 8u392

I technically can do it, but not early than November. :( -- wbr, Kirill > On 22. Oct 2023, at 17:39, Nils Breunese wrote: > > Hello, > > The openjdk8 port in MacPorts is currently at 8u372, but two updates with > security fixes have been released since then: 8u382 in July and 8u392 this >

Re: Updating openjdk8 to 8u392

jC libs fail to build. > I fixed the build on PPC up to AWT libs, but those are hopeless, or I got no > idea what to do to fix them anyway. > If we get rid of those, perhaps we can have openjdk8 at least back to 10.5, > including PPC. > > On Mon, Oct 23, 2023 at 1:18 AM Kiril

Re: Quick favor for those with access to 10.12 machines

You may use github "mirror" of SDK for difference macOS, for example https://github.com/search?q=repo%3Aphracker%2FMacOSX-SDKs%20kCGImageByteOrder32Big=code -- wbr, Kirill > On 23. Aug 2023, at 20:14, Jason

Build bot notifications

Folks, Is it possible to have a email notification when build bot have failed to build a port where I'm a maintainer? -- wbr, Kirill signature.asc Description: Message signed with OpenPGP

Re: Build bot notifications

d then follow the link in your profile to the ports you maintain > > https://ports.macports.org/accounts/my_ports/github/ > > There you can get a summary of the latest builds, etc. > > Chris > > On 23/08/2023 1:25 pm, Kirill A. Korinsky via macports-dev wrote: >> Folks, &

Update ICU to 71.1

Hey, For last days I've had worked to update ICU to the last version. All my tests had passed and I'd like to point that my PR is ready to be merged: https://github.com/macports/macports-ports/pull/15987 -- wbr, Kirill signature.asc

Update ICU to 72

Folks, I'd like to announce that ICU 72 is planned to be released in late of October. Deadline for bug reports is 18th October 2022. A port icu-devel was switched to a release candidate and I suggest to test it with your ports because I'm planing to update icu port to the next release after

Re: Using platforms in 2.8.0

clear, thanks -- wbr, Kirill > On 22. Oct 2022, at 13:03, Joshua Root wrote: > > On 2022-10-22 21:56 , Kirill A. Korinsky wrote: >> I'm asking is there a way to support specified arch inside platform block's >> condition. Like: >> platform {aarch64} { >> ... >> } > > You can certainly do

Re: Using platforms in 2.8.0

Does it support somehow arch? -- wbr, Kirill > On 22. Oct 2022, at 10:50, Joshua Root wrote: > > MacPorts 2.8.0 lets you specify which OS versions your ports work on via the > platforms option. This indicates a port that works on darwin versions from > 10.x to 19.x inclusive: > > platforms

Re: Using platforms in 2.8.0

I'm asking is there a way to support specified arch inside platform block's condition. Like: platform {aarch64} { ... } -- wbr, Kirill > On 22. Oct 2022, at 12:55, Joshua Root wrote: > > On 2022-10-22 20:34 , Kirill A. Korinsky wrote: >> Does it support somehow arch? > > I'm not sure what

Re: Update ICU to 72

Folks, ICU 72.1 was released. To allow easy test it, I've updated only icu-devel port as https://github.com/macports/macports-ports/pull/16426 . The icu port will be updated in two weeks. I strongly suggest to try to install it to confirm

Review a fix for OpenSSL3 CVE

Folks, OpenSSL team released a fix for found CVE: https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/ May I ask someone to review a PR to fix this CVE?

Re: Update ICU to 72

Folks, The PR to update ICU and bump all ports are here: https://github.com/macports/macports-ports/pull/16552 I'd like to ask to review it and merge it because it may introduce many conflicts. Thanks! -- wbr, Kirill > On 20. Oct

Re: The State of Rust in MacPorts Today

18:16, Christopher Jones wrote: > > Hi, > >> On 13 Dec 2022, at 5:07 pm, Kirill A. Korinsky via macports-dev >> mailto:macports-dev@lists.macports.org>> >> wrote: >> >> David, >> >> the idea is creating a dependency chain: >>

Re: The State of Rust in MacPorts Today

MCL's bootstrap compilers are for older systems. > > To update rust, my understanding is that you have to do the usual work of > rebasing patches (my PR), but you also have to provide the binaries for older > systems which I could not provide. > > > On Tue, Dec 13, 2022, 11:07 AM

Re: The State of Rust in MacPorts Today

Folks, From the third hand we may build our own bootstrap chain of rust from scratch. Or almost. We have a https://ports.macports.org/port/mrustc/details/ which is able to bootstrap 1.54 rust on x86_64 and arm64. Unfortunately support of i386

Re: The State of Rust in MacPorts Today

gt; Is it possible to build recent versions directly with rust-1.54? For > example, mrustc -> rust 1.54 -> rust 1.65? > > > On Tue, Dec 13, 2022 at 12:07 PM Kirill A. Korinsky via macports-dev > mailto:macports-dev@lists.macports.org>> > wrote: > David, > >

Allow installing both port:tbb and port:onetbb

Folks, I'd like to announce the PR on which I've worked for last weeks. The goal is allow to install both `tbb` and `onetbb` port on the same machine, and it forces to add installing both `oce` and `opencascade`. It is based on serveral PRs which I've made and which's fixed broken ports: -

Request to re-run buildbots for a few ports

Folks, As Renee point it is much better to ask someone who had an access to buildbot to rescheduled a build on buildbots instead of bump a revision. The context: cmake's update broke cmake on old platform. It was fixed in few days. May I ask anyone with access to reschedule build for ports:

Request review for two PR which contains math related software

Foks, I'd like to ask a review of two PR which brings more than 10 new ports which contains different libraries and tools to math. The first on is bring Polymake which is one of the best software for research in polyhedral geometry: https://github.com/macports/macports-ports/pull/16675

Request of review / merge a few PRs

Folks, I'm asking anyone to review and probably merge three my PRs: 1. Which was approved by maintainer: https://github.com/macports/macports-ports/pull/16793 2. A small fix inside qt* ports that brokes a runtime dependency from clang:

Re: Request to re-run buildbots for a few ports

Thanks. Fixing OneTBB on 10.6 -- wbr, Kirill > On 1. Dec 2022, at 14:05, Ryan Schmidt wrote: > > On Nov 28, 2022, at 14:34, Kirill A. Korinsky wrote: > >> May I ask anyone with access to reschedule build for ports: scalapack and >> papilo? > > Jeremy scheduled a rebuild of scalapack on

Re: Merge pull request

Thanks Pieter for this follow up. Meanwhile, I'd like to point that I have a few more missed PRs which I'd like to ask someone with write access to merge: - https://github.com/macports/macports-ports/pull/16496 -

Re: Java portgroup default fallback?

Keep in mind that for M1 you probably need zulu JVM. -- wbr, Kirill > On 23. Feb 2023, at 21:48, Joshua Root wrote: > > Does anyone know why there is no default value for java.fallback? The > assumption appears to be that if a port is using this portgroup, it requires > Java, since it errors

Update ICU to 73.1

Hey folks, I plan to create a PR to update ICU to 73.1 in two weeks: 9th may. It will include revdump of all affected ports, but I won't plan to test that all of them is compiled, instead I'd like to ask you to install icu-devel port which allows to track mainstream version of icu for your

Re: Go Ports: Update PG to Ensure Ports Aren't Built if Version Required Not Available

I may try to make some magic and bring fresh go 﫣 -- wbr, Kirill > On 27. Jul 2023, at 18:39, Christopher Nielsen > wrote: > > At present, our Go port is pinned at an older version - 1.17.3 - for macOS > 10.12 and earlier. With the result being that many Go-based ports simply fail > to

Re: Problems fetching from GitHub on 10.8?

Well... you need to build a MacPorts against some fresh enough libcurl :) Old system hasn't got enough. I'm using bootstrap MacPorts with curl (and python) for old systems :) And it works very stable. Can you use normal MacPorts and link MacPorts against curl from MacPorts? Yes, you can. But

Re: Problems fetching from GitHub on 10.8?

See: https://trac.macports.org/ticket/51516 You may also enjoy my ansible playbook: https://github.com/catap/macos-ansible-playbooks -- wbr, Kirill > On 21. Jul 2023, at 19:45, Jason Liu wrote: > >  > On my Mountain Lion VM, a Portfile that I'm working on updating doesn't seem > to be

Re: path:-style depspec to libc++.dylib?

Hi, I just tried depends_lib path:lib/libc++.dylib:libcxx and it works as expected. May you share a line which triggers an error? -- wbr, Kirill > On 8. May 2023, at 00:17, René J.V. Bertin wrote: > > Hi, > > I tried to write a path:-style depspec to libc++.dylib, but that

Re: Update ICU to 73.1

PR to update ICU is ready: https://github.com/macports/macports-ports/pull/18558 -- wbr, Kirill > On 25. Apr 2023, at 15:24, Kirill A. Korinsky wrote: > > Hey folks, > > I plan to create a PR to update ICU to 73.1 in two weeks: 9th

Re: How to fix duplicate rpath in existing library files

Default means to revbump all ports which is affected. A lot of heavy ports. I really not sure how safe is it, so, I prefer to be on safe side. -- wbr, Kirill > On 18. Dec 2023, at 22:41, Dave Allured - NOAA Affiliate > wrote: > > Thanks, that seems to be working well. I hope this can be

Re: How to fix duplicate rpath in existing library files

If your port using compilers PG you may control it via compilers.add_gcc_rpath_support option. See: https://github.com/macports/macports-ports/commit/760f4f8df2b90a6e31bd960f9768bf086c35b19f -- wbr,

Reschedule builds of cl-* ports

Folks, How can I reschedule to build missed / failed cl-* ports on build bots? Can someone do it? -- wbr, Kirill signature.asc Description: Message signed with OpenPGP