Re: There should be a requirement to check if a port exists before committing something right into the master

On Fri, 31 May 2024 18:45:53 +0100, Herby G wrote: > > Is it a guarantee that the PortIndex is available to `port` everytime `port > lint` is run? If so, would it be possible for us to use the port index to > verify that one and only one port exists for the current port name? > Another option is

Re: Building MacPorts - why not activate Tcl 64bit support?

On Fri, 31 May 2024 18:06:33 +0100, "René J.V." Bertin wrote: > > Is that simply to keep support for building on 32bit systems simple or is > there another reason? I am not familiar enough with Tcl to know if there's > any advantage to activating 64bit support ... but that's what MS once though

Re: Git-devel has broken git-credential-osxkeychain.c for older systems

Hi, On Mon, 22 Apr 2024 08:44:09 +0200, Riccardo Mottola wrote: > > Hi! > > Kirill A. Korinsky wrote: > > Keep in mind that suggested method removes support osx keyring from that > > system. User still be able to use SSH-based auth or enter password by hand > > fo

Re: Git-devel has broken git-credential-osxkeychain.c for older systems

On Sun, 21 Apr 2024 10:51:24 +0200, Sergio Had wrote: > > I am pretty sure there are people outside of Macports, or at least not on > its developers list, who use < 10.7. > Some on MacRumors, for instance; quite likely that those who are on KDX and > Hotline also run those on 10.4–10.5, though I h

Re: Git-devel has broken git-credential-osxkeychain.c for older systems

Hi, On Sun, 21 Apr 2024 09:38:24 +0200, Rliccardo Mottola wrote: > > I care for 10.5 and 10.6, but I read this mailing list :) > Probably most people developing or using these systems is on this > mailing list. Others may be using them but with old software only, not > trying to run latest on it.

Re: Git-devel has broken git-credential-osxkeychain.c for older systems

On Sun, 21 Apr 2024 07:47:03 +0200, Sergio Had wrote: > > Given it is in contrib, presumably it got its own upstream? Nope, it is part of git. See it as optional part of git which aren't available on each supported system. -- wbr, Kirill

Re: Git-devel has broken git-credential-osxkeychain.c for older systems

On Sat, 20 Apr 2024 20:45:36 +0200, Sergio Had wrote: > > Is someone in touch with Git upstream? It should be pretty trivial to > retain the working code, they are perhaps simply assuming that nobody uses > it. Which is not the case, obviously. I really doubt that anyone care about of macOS 10.6

Re: Git-devel has broken git-credential-osxkeychain.c for older systems

On Sat, 20 Apr 2024 18:19:30 +0200, Saagar Jha wrote: > > Wait, I use osxkeychain. It’s basically a requirement if you’re pushing to > an authenticated server over HTTPS and don’t want to have to deal with > storing keys yourself. I suspect it is used a lot for this. > Do you use on 10.6? I mean

Re: Git-devel has broken git-credential-osxkeychain.c for older systems

On Sat, 20 Apr 2024 00:25:47 +0200, Sergio Had wrote: > > What do we do? :) To fix the build you have two options: 1. Revert that patch for system before 10.7 2. Remove folder contrib/credential/osxkeychain I suggest to follow (2) as simpler thay and the good news that osxkeychain is something

Re: livecheck and curl 8.7.1

On Fri, 19 Apr 2024 21:12:43 +0200, René J.V. Bertin wrote: > > On Friday April 19 2024 20:51:20 Kirill A. Korinsky wrote: > > >bootstrap MacPorts, that fixes all issues. > > I strongly doubt it would fix the issue I've encountered. I realise it > only happens wi

Re: livecheck and curl 8.7.1

On Fri, 19 Apr 2024 20:46:10 +0200, René J.V. Bertin wrote: > > For a few years now I've copied libcurl.4.dylib and dependencies into > $prefix/libexec/lib/pextlib1.0 and then use install_name_tool magic to ensure > Pextlib.so uses this copy. This solves the problems with livechecks or even > d

Re: libtool: can't vm_allocate() buffer for output file of size 1218661592 ((os/kern) no space available)

On Mon, 01 Apr 2024 14:35:21 +0200, Sergio Had wrote: > > Can something be done about this error or is it a hard constraint of 32-bit > arch? > Seems like a limit for VM size for 32bit application. A while ago, before 64 bit were usual, it was qutie tricky to work with large files. Each applica

Re: XZ Utils Compromised Releases

On Fri, 29 Mar 2024 18:50:35 +0100, Rainer Müller wrote: > > > In [1] they mention reverting to 5.4.5 to fix it.  It's not 100% clear > > from that whether 5.4.6 is affected, but it sounds like it's not.  Since > > MacPorts is currently at 5.4.6, the port is probably OK as long as it > > doesn't d

Re: The future of the Golang Portgroup ― what to do with offline builds?

On Fri, 16 Feb 2024 10:24:59 +0100, Nils Breunese wrote: > > Allowing ports to download dependencies at build time carries the risk of > those dependencies not being available at build time, which I guess is why > MacPorts is not a fan of this method. In a corporate setting this is typically > mit

Re: mailing list "dev" vs "user"

On Thu, 25 Jan 2024 10:54:23 +0100, wrote: > > Hi, > > up to now I didn't subscribe to "macports-dev" mailing list, even if I use and > collaborate in MacPorts for years! > > Questions about bugs (e.g. discussions similar to track) belong to which list > best? Is "dev" only for "macports" itsel

Re: Question on architechture

On Wed, 24 Jan 2024 01:59:54 +0100, Mark Anderson wrote: > > So the Io port won't build on arm64, it will build on x86_64 and even get > moving on arm64 in x86_64 mode, but memcached seems to fail in universal > mode. What's the best way to deal with this for now, a note? a warning? > Some wait to

Re: Support for ancient machines and operating systems

> On 8. Jan 2024, at 20:55, Joshua Root wrote: > > On 9/1/2024 01:53, Kirill A. Korinsky wrote: >> How do you see the way to backport changes from upstream MacPorts to legacy >> MacPorts? >> at some point automatical merge would be broken on conflicts, and I assume

Re: Support for ancient machines and operating systems

> On 8. Jan 2024, at 16:18, Perry E. Metzger wrote: > > On 1/8/24 10:12, Kirill A. Korinsky wrote: >>> I don't think there should be overly much in the way of trouble if legacy >>> reasonably disciplined about frequently applying commits from upstream to >

Re: Support for ancient machines and operating systems

> On 8. Jan 2024, at 16:08, Perry E. Metzger wrote: > > On 1/8/24 09:53, Kirill A. Korinsky wrote: >>> On 8. Jan 2024, at 15:50, Perry E. Metzger wrote: >>> >>> I'd like to float the idea that we create a fork of the MacPorts repository >>>

Re: Support for ancient machines and operating systems

Hi Perry, > On 8. Jan 2024, at 15:50, Perry E. Metzger wrote: > > I'd like to float the idea that we create a fork of the MacPorts repository > that is devoted to operating systems and hardware that is more than (say) a > decade old, and that we allow the people who are interested in maintaini

Re: MacPorts 2.9.0-beta1 now available for testing

Greeting, Any news / changes on Github PG / extract.rename = yes for multiple distfiles? See: - https://trac.macports.org/ticket/66993 - https://github.com/macports/macports-ports/blob/9110117598a7828780270c73402bf2bd434082f8/devel/retdec/Portfile#L142-L146 > On 30. Dec 2023, at 14:11, Joshua

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

Re: How to fix duplicate rpath in existing library files

this can be made default, so > that we do not need to visit every port that makes a library and uses the PG. > I do not know how widespread the LC_RPATH problem is. > > > On Mon, Dec 18, 2023 at 12:28 PM Kirill A. Korinsky <mailto:kir...@korins.ky>> wrote: > If your por

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, K

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: https://github.com/macports/macp

Re: Port Reclaim

y port it would have > marked those as requested. > > —Mark > ___ > Mark E. Anderson mailto:m...@macports.org>> > MacPorts Trac WikiPage <https://trac.macports.org/wiki/mark> > GitHub Profile <https://github.com/markemer> > > &g

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: Updating openjdk8 to 8u392

ObjC 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

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 > m

Re: Portfile for osxphotos

Here it is: https://github.com/macports/macports-ports/pull/20416 <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

Re: Portfile for osxphotos

Hello, I've used osxphotos once or twice and willing to make a port file and take care of it. PR will be made tonight. -- wbr, Kirill > On 7. Sep 2023, at 08:03, Nils Breunese wrote: > > Hello, > > I recently wanted to export some photos from Apple’s Photos application and > import them on

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 h

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&type=code -- wbr, Kirill > On 23. Aug 2023, at 20:1

Re: Build bot notifications

t; > Sign in, and 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:

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: 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 bui

Re: Problems fetching from GitHub on 10.8?

he interesting thing, > though, is that I have the MacPorts curl (and curl-ca-bundle) installed on > the 10.8 VM already. I would have thought that MacPorts base would look for > and use MacPorts curl and curl-ca-bundle if they're installed? > > -- > Jason Liu >

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 able

Re: Update ICU to 73.1

PR to update ICU is ready: https://github.com/macports/macports-ports/pull/18558 <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

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 give

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 port

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

Re: The State of Rust in MacPorts Today

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, > >

Re: The State of Rust in MacPorts Today

, at 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

eam. 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

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

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: - htt

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 sched

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: sc

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: h

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

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 - https://github.com/macpor

Re: Update ICU to 72

n 20. Oct 2022, at 15:02, Kirill A. Korinsky wrote: > > 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 > <https://github.com/macports/macports-ports/pull/16426>

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? https://github.com/macports/macports-ports/pull/1654

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} {

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 arc

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: Update ICU to 72

to confirm that all software can be used with new ICU, or some patch are required. Thanks. -- wbr, Kirill > On 27. Sep 2022, at 21:54, Kirill A. Korinsky wrote: > > Folks, > > I'd like to announce that ICU 72 is planned to be released in late of October. > > Dea

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 th

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 De

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 wit

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