Hi Mojca!
> Am 12.02.2021 um 02:37 schrieb Mojca Miklavec :
>
> On Thu, 11 Feb 2021 at 22:34, Henning Hraban Ramm wrote:
>>
>> Hi, is there a possibility to update the MacPorts version of TeX Live 2020?
>
> It depends on whether you are willing to wait for TeX Live 2021, or
> willing to volunte
On Thu, Feb 11, 2021 at 08:32:19PM -0500, "wowfunha...@gmail.com"
wrote:
> Hello all!
>
> The recently discovered vulnerability in sudo is making me nervous
> about my old systems. This may be unreasonable, as these systems have
> plenty of other vulnerabilities and I behave accordingly. Howeve
It finally finished. The lines scroll by so fast it was hard to see what it
was doing, but it is completed successfully.
> On Feb 11, 2021, at 7:57 PM, Ryan Schmidt wrote:
>
>
>
> On Feb 11, 2021, at 19:27, Tom Gederberg wrote:
>
>> I just upgraded from Big Sur 11.1 to 11.2.1 and then did a
>
>
> On Feb 11, 2021, at 19:32, Todd Doucet wrote:
>
> > So I guess there is still a bit of a mystery. If I get some time I will
> > try to build the new MacPorts from source and see if there is still a
> > warning. (I presently do not rely on MacPorts for mainline code and it is
> > ver
On Feb 11, 2021, at 17:32, wowfunha...@gmail.com wrote:
> Hello all!
>
> The recently discovered vulnerability in sudo is making me nervous about my
> old systems. This may be unreasonable, as these systems have plenty of other
> vulnerabilities and I behave accordingly. However, sudo just seem
On Feb 11, 2021, at 19:27, Tom Gederberg wrote:
> I just upgraded from Big Sur 11.1 to 11.2.1 and then did a
>
> sudo port -v selfupdate
> sudo port -v upgrade outdated
>
> It is taking hours and seems to be compiling everything from scratch. It
> have Neve taken this log before and I usual
On Feb 11, 2021, at 19:32, Todd Doucet wrote:
> So I guess there is still a bit of a mystery. If I get some time I will try
> to build the new MacPorts from source and see if there is still a warning.
> (I presently do not rely on MacPorts for mainline code and it is very easy
> for me to
On Thu, 11 Feb 2021 at 22:34, Henning Hraban Ramm wrote:
>
> Hi, is there a possibility to update the MacPorts version of TeX Live 2020?
It depends on whether you are willing to wait for TeX Live 2021, or
willing to volunteer to create devel subports yourself. See:
https://github.com/macports/
> On Feb 11, 2021, at 18:47, Todd Doucet wrote:
>
> > You can see that there are two SDKs here, including the one that you
> > expect, and the name MacOSX.sdk links to it too:
> >
> > % ls -l /Library/Developer/CommandLineTools/SDKs
> >
> > lrwxr-xr-x 1 root wheel 14 Feb 6 16:23 MacOSX.s
Hello all!
The recently discovered vulnerability in sudo is making me nervous about my old
systems. This may be unreasonable, as these systems have plenty of other
vulnerabilities and I behave accordingly. However, sudo just seems like such a
vital component, and this exploit particularly bad.
I just upgraded from Big Sur 11.1 to 11.2.1 and then did a
sudo port -v selfupdate
sudo port -v upgrade outdated
It is taking hours and seems to be compiling everything from scratch. It have
Neve taken this log before and I usually update my ports every week.
Is anyone else experiencing this?
On Feb 11, 2021, at 18:47, Todd Doucet wrote:
> You can see that there are two SDKs here, including the one that you expect,
> and the name MacOSX.sdk links to it too:
>
> % ls -l /Library/Developer/CommandLineTools/SDKs
>
> lrwxr-xr-x 1 root wheel 14 Feb 6 16:23 MacOSX.sdk -> MacOSX11.1.s
It is a little odd that one of the package receipts is not named
com.apple.pkg.CLTools_SDK_macOS111
but instead is named
com.apple.pkg.CLTools_SDK_macOS110
>
>> MacPorts 2.6.4 was released before Apple released macOS 11.1. We did not yet
>> know how the version numbers of macOS and th
> MacPorts 2.6.4 was released before Apple released macOS 11.1. We did not yet
> know how the version numbers of macOS and the macOS SDK would progress under
> macOS 11. We made a guess based on what had happened in macOS 10.15 and
> earlier, and we guessed wrong. We have corrected the code alr
On Feb 11, 2021, at 15:34, Henning Hraban Ramm wrote:
> Hi, is there a possibility to update the MacPorts version of TeX Live 2020?
MacPorts texlive was apparently updated to version 2020 in July of 2020:
https://github.com/macports/macports-ports/commit/73396594cf737f853b78c1c64c410a47450dfb
On Wed, Feb 10, 2021 at 08:17:42PM -0600, Ryan Schmidt
wrote:
> On Feb 9, 2021, at 21:26, Eric Gallager wrote:
>
> > With git at least, there's a built-in command (`git bisect`) to assist
> > with cases like this; would it be possible to add a similar feature to
> > the restore_ports.tcl script
On Feb 11, 2021, at 14:50, Todd Doucet wrote:
> I have read everything I can about this warning, but none of it corresponds
> to exactly my situation, hence this report.
>
> I have a brand new Mac Mini M1, and a fresh MacPorts installation. This is
> not an upgrade--I have never had MacPort
I'd add that AS LONG AS you have a separate admin and user account, you can do
anything you please to your user account; but best to leave settings for the
admin account as close to system default as possible; that way you minimize the
risk of locking yourself out in the event that an OS update
Hi, is there a possibility to update the MacPorts version of TeX Live 2020?
Usually you would use "tlmgr update --self --all".
There are fixes for several packages, and even the LuaTeX binary got a fix, I
was told.
(I’m debugging at a customer’s LaTeX project, colleagues and build server have
I have read everything I can about this warning, but none of it corresponds to
exactly my situation, hence this report.
I have a brand new Mac Mini M1, and a fresh MacPorts installation. This is not
an upgrade--I have never had MacPorts on this machine, ever.
I definitely have both Xcode 12.4
I'd recommend the following which is part of my standard config:
cd /private/etc
cp paths paths.d/999-macOS
mv paths paths.orig
echo "/opt/local/bin" > paths
echo "/opt/local/sbin" >> paths
echo "/opt/local/bin/bash" >> shells
echo "/opt/local/bin/zsh" >> shells
you can now do "chsh -s
On 11 Feb2021, at 2:57 AM, Ryan Schmidt wrote:
>
>
>
> On Feb 10, 2021, at 14:59, Murray Eisenberg wrote:
>
>> Is there any hope of soon getting ftgl and gl2ps to build (under Big Sur
>> 11.1 with MacPorts — I’m using 2.6.99 — and Xcode CLT 12.5)?
>>
>> I need the former to get gnuplot and
Thanks Rainer, that was exactly the case.
On Thu, Feb 11, 2021 at 7:02 AM Rainer Müller wrote:
> On 10/02/2021 22.35, Mike Summers via macports-users wrote:
> > I'm not able to get MacPorts bash working in Terminal as the default
> shell.
> >
> > This is fresh install of Big Sur 11.2 on a new ma
Thanks Peter, your note put me on the right track.
What I should have done was set my default shell (with chsh or Users &
Groups) to /bin/bash before installing MacPorts bash. Then the PATH tweaks
from the MacPorts bash installer fix-up the PATH and the MacPorts bash is
always invoked.
--Mike
On
On 10/02/2021 22.35, Mike Summers via macports-users wrote:
> I'm not able to get MacPorts bash working in Terminal as the default shell.
>
> This is fresh install of Big Sur 11.2 on a new machine, fresh install of
> MacPorts. Only bash and bash-autocomplete are installed
>
> Setting the shell in
Am 11.02.2021 um 03:12 schrieb Ryan Schmidt :
>
> On Feb 10, 2021, at 11:14, Rainer Müller wrote:
>
>> Your suspicion is correct, all buildbots run on case-sensitive filesystems.
>> Direct access is not possible and it is wiped directly after the build as
>> disk
>> space is a rare resource for
26 matches
Mail list logo
