On Aug 30, 2024, at 4:02 PM, René J.V. Bertin wrote:
> On Friday August 30 2024 15:46:39 Daniel J. Luke wrote:
>> It's probably better to fix the build system.
>
> Undoubtedly. But the case I had that made me start this discussion was of the
> same sort as the problem
build phase instead of trying to
wrangle the macports machinery into doing what you're attempting.
(As a bonus, you don't have to implement your script in tcl if you don't want
to).
--
Daniel J. Luke
of MacPorts working where /opt/local was a symlink some time
ago (I had a local patch to fixup some of the problems, but I can't find it
now). IIRC setting prefix in macports.conf made things mostly work.
--
Daniel J. Luke
ns that are no longer supported
upstream.
--
Daniel J. Luke
s to run the test phase as
root (test.asroot yes should work here, but when I did a quick test it didn't
and I didn't have a chance to see why), or alter the openssh tests/build to not
need to be run as root.
--
Daniel J. Luke
To clarify - this was in the context of commits to base/
(That may or may not change your perception - but like I said, I didn’t measure
and this is totally measurable).
--
Daniel J. Luke
> On Nov 5, 2023, at 1:26 PM, Perry E. Metzger wrote:
>
>
>> On 11/4/23 02:42, Danie
On Nov 2, 2023, at 9:17 PM, Perry E. Metzger wrote:
> On 11/2/23 10:28, Daniel J. Luke wrote:
>> On Nov 1, 2023, at 9:32 PM, Perry E. Metzger wrote:
>>> As an aside, as it stands, the rules situation with closed maintainer /
>>> open maintainer is kind of unpleasan
re we moved to github there were many people saying we'd get lots more
commits by moving to it, but the volume doesn't seem much higher to me - of
course, I also didn't measure before/after so my perception could be incorrect).
--
Daniel J. Luke
ose name being on the port means you have to ritualistically wait three
> days for a reply you know will never come.
Maybe we need an update to the port abandoned process (or some sort of positive
checkin for maintainers to make sure they're still interested in maintaining a
port)?
--
Daniel J. Luke
etzger) pushed a commit to branch master
> in repository macports-ports.
--
Daniel J. Luke
re
> is seemingly showing issues with the ‘ld -ld_classic’ workaround we are using
> for the linker issues Xcode 15 has, which I don’t yet understand.
I built it today and it built fine (I didn't do any testing to make sure it
worked, though).
--
Daniel J. Luke
OS.
YMMV (especially since the set of ports you care about is probably not the same
as the set of ports I have installed), and I'm prepared to debug/fix any
problems I see, but I find it much easier than the other options.
--
Daniel J. Luke
ial) portindex with the
version of the port(s) you don't want to upgrade.
See also /opt/local/etc/macports/sources.conf
--
Daniel J. Luke
> only certain installed releases? Maybe it could be done by using a pre-build
> {} tcl block?
>
> Is there a global variable available that is set to the installed version
> number?
> And is there an easy way to tell if a port is already installed before
> upgrading?
>
> Rob
--
Daniel J. Luke
m explicitly passing -s to the port command—download from source:
>>
>> What’s the fix to this? (Simple revbump?) And why don’t I detect it but the
>> OP does?
--
Daniel J. Luke
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/16545
>
> I think that this CVE should be a reason to merge such PR ASAP without
> maintainers confirmation.
--
Daniel J. Luke
features on a given port.
--
Daniel J. Luke
port files would look cleaner (and we wouldn’t need variant-specific magic), so
complexity there seems worthwhile.
--
Daniel J. Luke
> On Oct 30, 2022, at 6:23 AM, Ryan Schmidt wrote:
>
> On Oct 28, 2022, at 21:33, Daniel J. Luke wrote:
>>
>> I don't think implem
okt. 2022 om 11:23 heeft Ryan Schmidt het volgende geschreven:On Oct 28, 2022, at 21:33, Daniel J. Luke wrote:I don't think implementation difficulty is the barrier here - but that all variants should just have the same behavior.In my mind, the real problem is the need for +test variants,
ile of a plan to rely on variant propagation (ie if you have the
> port installed already, it won’t be reinstalled with the “+debug” variant),
> that such rare users might best install each port they want to be installed
> as “debug” do that specifically. Certainly most of us don’t want clang-15
> installed with it’s debug variant when you’re trying to debug some little
> port.
--
Daniel J. Luke
On Jun 8, 2022, at 1:41 PM, Joshua Root wrote:
> On 2022-6-9 03:12 , Daniel J. Luke wrote:
>> is the origin server bandwidth constrained?
>
> The origin is nue.de.packages.macports.org, and fetching from there directly
> is considerably faster (~5 MB/s for me, vs 948 kB/s goin
tbz2
>
> Gives me 39.3MB/s on my work network, and 8.5MB/s on my home ISP.
>
> Chris - I suspect the issue is more your end, or your ISP, than the servers
> per se.
>
> cheers (another) Chris
--
Daniel J. Luke
omething. I'm just saying that software could be written to do the right thing
here and I would welcome the automation. Implementation would, of course, take
time and require consideration of all of the other pieces of MacPorts (and
infra) that it touches.
--
Daniel J. Luke
eally a proposal yet (I don't think anyone is working on code) -
but there are of course possibilities here. We could (ab)use epoch, just have
portindex increment the revision for the ports that request to be rebuilt when
a new version of something is added, add a new int that we auto-increment, hash
over the (portname, epoch, version, revision) of deps that a port says it cares
about [and countless others that would maybe take me more than 5 minutes to
come up with ;-)]
--
Daniel J. Luke
curl-ca-bundle
... there are probably other alternatives as well.
So far, when people encounter this problem, there hasn't been enough motivation
for anyone to build a MacPorts feature to support it (but I'd be happy to see
one).
--
Daniel J. Luke
the end user
behavior you want without having this port being a unique (and surprising)
thing.
--
Daniel J. Luke
our response that this isn’t how depends_lib works.
Nope, there's no way (currently) to have a port declare that it needs to be
rebuilt if a dependency is updated (it would be a really nice feature to add to
base, though).
--
Daniel J. Luke
iles from the checked out
source and puts it on our mirrors (builder could probably do this since it's
already going to check out the source), then have base look for the distfile on
our mirrors first (even if the portfile specifies to check out from a revision
control system)
--
Daniel J. Luke
long with an up-to-date
> curl-ca-bundle (that addresses the LetsEncrypt cert issue) fails with the
> same error:
>
>> pip-2.7 install --cert /opt/local/etc/openssl/cert.pem -I --user setuptools
IIRC pip will respect a CA bundle set in the REQUESTS_CA_BUNDLE environment
variable.
--
Daniel J. Luke
ned by someone who
doesn't want/need/use those patches.
--
Daniel J. Luke
ase? If at all
> possible, I'd like to avoid manually using curl through a `system` call, but
> I suppose it could work as a last resort.
Does this sourceforge example help?
https://trac.macports.org/wiki/howto/AvoidRedirects
--
Daniel J. Luke
base to make it
(eventually) possible to not need them.
For os.major stuff, I think there have been some proposals for range syntax,
just none have been implemented yet.
--
Daniel J. Luke
cted
> by this problem.
Specifically the version/revision being changed interacts poorly with 'port
outdated' (causing these ports to always appear as if they are outdated) -
other differences do not.
--
Daniel J. Luke
ools:
https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt
(this happened to me on upgrade to macOS 12 as well).
--
Daniel J. Luke
In any event - I thought I'd post, if for no other reason than to save someone
some time if they also see this behavior.
--
Daniel J. Luke
e thing later - so might
as well get it over with now. The sooner we get to a state where (mostly)
things all work with the latest openssl, the better.
--
Daniel J. Luke
; ui_error "'tests' variant must be activated to enable test support"
> error "Please enable the 'tests' variant and try again"
> }
> }
>
> --
> Jason Liu
>
>
> On Tue, Sep 28, 2021 at 11:13 AM Ken Cunningham
On Sep 20, 2021, at 10:20 AM, Daniel J. Luke wrote:
> On Sep 20, 2021, at 8:15 AM, Frank Dean wrote:
>> Daniel J. Luke writes:
>>> The newest version of clamav uses cmake for builds. In the 'configure'
>>> stage, I have it disabling tests because otherwise
On Sep 20, 2021, at 8:15 AM, Frank Dean wrote:
> Daniel J. Luke writes:
>> The newest version of clamav uses cmake for builds. In the 'configure'
>> stage, I have it disabling tests because otherwise it won't build without
>> the test dependencies install
see
an obvious hook for when someone is running `port test` to change
configure.args (I could, of course, add a post-extract/pre-configure and do
some non-declaritive test to see if `port test` is being run and use that to
branch - but that feels like a bad design choice).
--
Daniel J. Luke
ne).
I agree that the priority should be on just having one working version, though.
--
Daniel J. Luke
27;perl5' and have everything depend on
it (and revbump the world of perl when we upgrade it). It takes us too long to
migrate everything 'nicely'
I suspect we could do this for python as well, but I've not looked recently at
how disruptive newer python versions are.
... but I've said it before and people don't really like that idea, I guess :)
--
Daniel J. Luke
x27;s no
> getting around rev bumping all dependents.
This is something that would be nice to expand macports base to handle more
easily (although the details of the implementation might be annoying to deal
with) - but we've managed for a /long/ time with rev-bumping all dependent
ports.
--
Daniel J. Luke
On May 17, 2021, at 2:03 AM, Ryan Schmidt wrote:
> On May 16, 2021, at 17:57, Daniel J. Luke wrote:
>> On May 16, 2021, at 10:48 AM, Christopher Nielsen wrote:
>>> I’d bet the hypervisor is spending more time on scheduling and pre-emption,
>>> than actual proc
mine that a config change needs to happen,
we can use the actual measurements to help us optimize the configuration).
--
Daniel J. Luke
timeout/security update/mistake) is more likely to
be aware of this.
--
Daniel J. Luke
using the revupgrade_autorun switch.
--
Daniel J. Luke
required effort.
If you've got time+interest in making it work - please do so!
--
Daniel J. Luke
ble* to build from source, but not
> be *required* to do so.
How is it stingy? We have binary archives for everything that the buildbots can
build that the licenses allow us to distribute, right?
port, by default, will use the binary archives unless you tell it to build from
source instead.
--
Daniel J. Luke
On Jun 22, 2020, at 11:20 PM, Ryan Schmidt wrote:
> On Jun 22, 2020, at 14:34, Daniel J. Luke wrote:
>> We should just have one perl5 port that tracks the current release.
>
> You say this every year (or at least often).
I say this every time we run into the set of problems that
make it so the revbump is unnecessary.
We could keep the 'old' perl5s around - but I would suggest that it's not
worthwhile. People who really need multiple versions of perl are better served
by using perlbrew than any of the packagers.
--
Daniel J. Luke
group/perl5-1.0.tcl?rev=6127
>
> Toby, do you remember why it uses pure_install and not install?
presumably it was to avoid writing to perllocal.pod and then having to do
something (like remove it from the destroot) before installing where they may
already be a perllocal.pod file.
--
Daniel J. Luke
ying it.
>
> Again, I know MacPorts is not going to change that (no point now). But from a
> ‘business’ point of view, it was masterful.
--
Daniel J. Luke
On Oct 23, 2019, at 9:58 AM, Ryan Schmidt wrote:
> On Oct 23, 2019, at 08:56, Daniel J. Luke wrote:
>> On Oct 22, 2019, at 9:49 PM, Ryan Schmidt wrote:
>>> Or does the port use libxml2? If so, it may be using a bad method of
>>> finding libxml2. One bad method of f
hanges upstream) instead? http://www.xmlsoft.org/FAQ.html tells people to use
xml2-config (so I suspect other upstream projects will be reluctant to include
patches that switch from using xml2-config to pkg-config).
--
Daniel J. Luke
but if it allows it, we should
be providing install via port so that the normal dependency resolution stuff
can work.
--
Daniel J. Luke
no - and the number of ports we have is /much/
larger).
--
Daniel J. Luke
ine for trac tickets]. I could do
matching on list-id but add an exception for when I'm CC'd (which may work),
but could also miss some mail.
I'll plan on collecting responses and putting something up on the wiki if it
seems like it would be useful to others.
Thanks.
--
Daniel J. Luke
onsidered converting to Jira or BugZilla, but in the end,
we decided that staying with Trac is the best and least disruptive choice
for now. We will migrate the data from our Trac installation to a new
server, taking the opportunity to upgrade to the latest version of Trac and
make some other improvements."
--
Daniel J. Luke
On Mar 16, 2018, at 11:28 AM, db wrote:
> On 16 Mar 2018, at 16:03, "Daniel J. Luke" wrote:
>> portfiles could in theory attempt to connect to any port, so a comprehensive
>> list like you're asking for is probably not possible to create.
>
> But there c
look at switching our default port syncing to http
(or run our rsync server on tcp/80).
--
Daniel J. Luke
tk2, gtk3, ang gtk2-murrine all as lib deps,
> and install them all. Then nothing can go wrong.
That's one option.
Another would be to use variants for this (maybe a default gtk3 variant and an
optional gtk2 one?)
--
Daniel J. Luke
On Feb 15, 2018, at 1:04 PM, Bradley Giesbrecht wrote:
> And freshclam is not a service and only needs to run once a day
> (StartInterval).
it can run as a service, though (which defaults to checking 12 times a day for
updates).
--
Daniel J. Luke
ight also take quite long. I can
> imagine changing the GitHub PortGroup would lead to index update times
> of more than 10 minutes. :(
... although I don't think we'd be putting this sort of thing in the GitHub
PortGroup ...
--
Daniel J. Luke
out
something to handle the case where a port wanted to set a revision and then
later we wanted to update the revision in the portgroup).
IIRC Ryan /hated/ that idea.
Alternatively, we could add something to base to let us specify this kind of
dependency (which would be useful).
--
Daniel J. Luke
update any port that has a security update.
--
Daniel J. Luke
On Oct 9, 2017, at 8:11 AM, Rainer Müller wrote:
> I would just move 1.4 to gnupg1 and let gnupg provide version 2.2, as
> only few users will be looking for GnuPG 1.4.x these days. If there is
> enough interested, create gnupg-devel for the 2.3 development branch.
+1
--
Daniel J. Luke
g something - but I'm not sure what it is. Any thoughts?
--
Daniel J. Luke
n't choose to
'restore' the user?
Might be good to include instructions for both outcomes and/or include both in
any plans for how we make MacPorts deal with this automatically.
--
Daniel J. Luke
On Sep 8, 2017, at 1:26 PM, Ryan Schmidt wrote:
> On Sep 8, 2017, at 11:48, Daniel J. Luke wrote:
>> One solution might be to separate the build/distfile mirroring from the
>> portfile mirroring. You could probably even do that by running separate
>> rsync's for tho
On Sep 8, 2017, at 12:32 PM, Ryan Schmidt wrote:
> On Sep 8, 2017, at 11:08, Daniel J. Luke wrote:
>> On Sep 8, 2017, at 11:55 AM, Ryan Schmidt wrote:
>>> On Sep 8, 2017, at 10:51, Daniel J. Luke wrote:
>>>> On Sep 7, 2017, at 9:37 AM, Ryan Schmidt wrote:
>>
On Sep 8, 2017, at 11:55 AM, Ryan Schmidt wrote:
> On Sep 8, 2017, at 10:51, Daniel J. Luke wrote:
>> On Sep 7, 2017, at 9:37 AM, Ryan Schmidt wrote:
>>> That'll happen when a huge port gets built and the resulting packages must
>>> be transferred between my pri
be reasonable to move things around so we're not dependent on your
(presumably consumer-class) internet connection?
--
Daniel J. Luke
; point, is there a way I can get this to work… ?
I suspect the sandbox doesn't include access to /dev/random (Macports started
using sandbox-exec with version 2.2.0)
As a temporary workaround (or to test this theory) you can add "sandbox_enable
no" to your macports.conf
--
Daniel J. Luke
958&w=1
(add subport=foo to the end of your command to get subport foo).
I always forget this and end up needing to look it up - it should probably go
on our wiki or FAQ somewhere.
--
Daniel J. Luke
27; tree where someone has done a review and
merged from the auto-committed one. I don't know if a universe where that
exists is better, though (it would be pretty trivial to create a Portfile that
could pass automated checks but do something bad if run on an end-user's
machine).
--
Daniel J. Luke
On May 8, 2017, at 12:36 PM, m...@macports.org wrote:
> I think we should strive to support the latest versions of python 2 and 3
> only.
+1 (just like we should do with perl5).
--
Daniel J. Luke
inports days until now - it's probably overdue for
general macports.conf cleanup)
--
Daniel J. Luke
On Jan 27, 2017, at 3:58 PM, John Patrick wrote:
> how do I get the pkg installer from the website as all the links are
> for 2.3.5, or do i need to guess the url?
it's in the release announcement:
https://lists.macports.org/pipermail/macports-announce/2017-January/40.html
-
rts-dev/2017-January/035306.html
easy workaround is to use the pkg installer or download the source and build
(instead of using selfupdate).
note that the 'default' sources.conf configuration works fine.
--
Daniel J. Luke
ase/tarballs/base.tar worked fine
selfupdate with an install that pulls release/base fails with:
configure: === configuring in vendor/tcl/unix
(/opt/local/var/macports/sources/rsync.macports.org/release/base/vendor/tcl/unix)
configure: error: no configure script found in vendor/tcl/unix
--
Daniel J. Luke
clobbered it. I think you might not even be able to do it with SIP anymore
anyway.
> I still don't know how to workaround programs calling
> /usr/sbin/sendmail.
One option would be to configure the apple postfix to relay through the
macports-installed postfix.
--
Daniel J. Luke
On Jan 26, 2017, at 2:11 AM, Johannes Kastl wrote:
> On 25.01.17 22:28 Daniel J. Luke wrote:
>> What does `openssl s_client -connect 78.46.5.205:25 -starttls
>> smtp` > say?
>
> "verify return: 1" sounds like problems, but "Verify return code: 0
> (o
> /C=US/O=Equifax/OU=Equifax Secure Certificate Authority
>
> and later:
> ... status=deferred (Server certificate not trusted)
What does `openssl s_client -connect 78.46.5.205:25 -starttls smtp` say?
(using the MacPorts installed openssl)
--
Daniel J. Luke
ogging system.
see the 'log' manpage.
To replicate tail -f /var/log/mail.log you'd do something like:
log stream --style syslog --type log --predicate '(processImagePath contains
"postfix")'
--
Daniel J. Luke
y adds an
> Approved header with the corresponding list post password to the mail.
> This is apparently not enough to circumvent/pass the spam filter.
some whitelisting should be able to fix it.
--
Daniel J. Luke
On Jan 13, 2017, at 8:20 PM, Craig Treleaven wrote:
>> On Jan 13, 2017, at 4:06 PM, Joshua Root wrote:
>> On 2017-1-14 07:28 , Daniel J. Luke wrote:
>>> On Jan 13, 2017, at 3:01 PM, Craig Treleaven
>>> wrote:
>>>> Suppose I create an mpkg insta
th
the mariadb (client) port.
--
Daniel J. Luke
s to a
> procedure?
I don't know, why don't you build a simple benchmark, test it, and report back
with your results?
--
Daniel J. Luke
ubports index properly would be welcome, though.
--
Daniel J. Luke
ix for the missing \ in the description in the subport.
--
Daniel J. Luke
t in their myself.
That's not the default. If you can figure out where you may have read
instructions telling you to set that, it would be helpful (so we could create a
real fix for whatever people were trying to work-around and not have people
setting things that way).
--
Daniel J. Luke
tting a MacPorts
installed git?
--
Daniel J. Luke
on db46 because when oracle purchased, the db4 license changed - but I
think Oracle made another change that made it OK, I just haven't gone to look /
no one has offered to investigate or submitted a patch).
> b. Have a mariadb10 variant
As I don't use any of the mysql-descendent DBs, I rely on people who do to
submit patches for them :)
--
Daniel J. Luke
e masking of non-dep files from trace mode, that would work,
> too. (As the old versions would be inaccessible.)
As far as I'm aware, there is no way to do this.
The best thing would be if trace mode could be enhanced so that it could be
always on (or at least default to on).
--
Daniel J. Luke
95 matches
Mail list logo
