Re: missing package texlive-basic-44435-run.tar.xz

[Jean de Largentaye]

Thanks! I hadn't found that ticket.

On Tue, Nov 14, 2017 at 5:13 PM Ryan Schmidt 
wrote:

> On Nov 14, 2017, at 14:42, Jean de Largentaye wrote:
>
>
> I'm on macOS 10.13.1, running MacPorts 2.4.2, just recently sync'd. I'm
> trying to install the port texlive variant -doc, but the package
> texlive-basic-44435-run.tar.xz does not exist on any mirrors, see attached
> main.log.
>
> I have also manually verified on a few selected servers (such as
> distfiles.macports.org), and confirmed the absence of this particular
> file, whereas older versions exist.
>
> I'm especially confused because the Portfile that refers to this version
> appears to exist since June 20th?
>
>
> https://github.com/macports/macports-ports/blob/master/tex/texlive-basic/Portfile
>
> Have others encountered the issues? What are your suggestions to fix or
> work around it?
>
>
> See https://trac.macports.org/ticket/55319
>

Re: missing package texlive-basic-44435-run.tar.xz

[Ryan Schmidt]

On Nov 14, 2017, at 14:42, Jean de Largentaye wrote:
> 
> I'm on macOS 10.13.1, running MacPorts 2.4.2, just recently sync'd. I'm 
> trying to install the port texlive variant -doc, but the package 
> texlive-basic-44435-run.tar.xz does not exist on any mirrors, see attached 
> main.log.
> 
> I have also manually verified on a few selected servers (such as 
> distfiles.macports.org), and confirmed the absence of this particular file, 
> whereas older versions exist.
> 
> I'm especially confused because the Portfile that refers to this version 
> appears to exist since June 20th?
> 
> https://github.com/macports/macports-ports/blob/master/tex/texlive-basic/Portfile
> 
> Have others encountered the issues? What are your suggestions to fix or work 
> around it?

See https://trac.macports.org/ticket/55319

Re: MacPorts related questions

[Ken Cunningham]

I find systems painfully, almost unusably, slow without an SSD. I have retrofit 
them into almost every system I have (including a Beige G3 tower running MacOS 
9.2.2).

K

> On Nov 14, 2017, at 6:24 AM, William H. Magill  wrote:
> 
> 
> 
>> On Nov 14, 2017, at 8:31 AM, pagani laurent via macports-users 
>>  wrote:
>> 
>> Maybe I am misled by a hidden problem but when I moved from Lion to Sierra 
>> for similar reasons (browsers not maintained anymore for 10.7, etc.) I 
>> experienced a strong slow down of my machine (MBP, 8 Gb Ram, hard drive). I 
>> recovered speed when it died and I moved to a more recent machine with 16Gb 
>> and a SSD. So I would cautiously upgrade to Mavericks or Yosemite and stop 
>> there if enough in your case.
>> 
>> LP
> 
> There is a massive amount of conversion work done in the background when you 
> first upgrade to Sierra or High Sierra.
> Allowing the system to chug along for about 24 hours (depending on your disk 
> size) gets rid of the sluggishness.
> 
> There is a “notification” which pops up warning you of this when you first 
> login after the upgrade, but it is quickly dismissed and forgotten about. :)
> 
> 
> T.T.F.N.
> William H. Magill
> # iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.13.1
> # Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.13.1
> # MacPro5,1 Quad-Core Intel Xeon [2.8 GHz - 16 GB 1066 MHz] OSX 10.13.1
> mag...@icloud.com
> mag...@mac.com
> whmag...@gmail.com
> 
> 
> 
> 
> 
> 
> 
> 

Re: MacPorts related questions

[pagani laurent via macports-users]

I am not talking about the migration period but the weeks after. The machine 
was always very slow and never recovered. The HD was 500 Gb (filled up to 90%…)


> Le 14 nov. 2017 à 15:24, William H. Magill  a écrit :
> 
> 
> 
>> On Nov 14, 2017, at 8:31 AM, pagani laurent via macports-users 
>>  wrote:
>> 
>> Maybe I am misled by a hidden problem but when I moved from Lion to Sierra 
>> for similar reasons (browsers not maintained anymore for 10.7, etc.) I 
>> experienced a strong slow down of my machine (MBP, 8 Gb Ram, hard drive). I 
>> recovered speed when it died and I moved to a more recent machine with 16Gb 
>> and a SSD. So I would cautiously upgrade to Mavericks or Yosemite and stop 
>> there if enough in your case.
>> 
>> LP
> 
> There is a massive amount of conversion work done in the background when you 
> first upgrade to Sierra or High Sierra.
> Allowing the system to chug along for about 24 hours (depending on your disk 
> size) gets rid of the sluggishness.
> 
> There is a “notification” which pops up warning you of this when you first 
> login after the upgrade, but it is quickly dismissed and forgotten about. :)
> 
> 
> T.T.F.N.
> William H. Magill
> # iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.13.1
> # Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.13.1
> # MacPro5,1 Quad-Core Intel Xeon [2.8 GHz - 16 GB 1066 MHz] OSX 10.13.1
> mag...@icloud.com
> mag...@mac.com
> whmag...@gmail.com
> 
> 
> 
> 
> 
> 
> 
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: MacPorts related questions

[William H. Magill]

> On Nov 14, 2017, at 8:31 AM, pagani laurent via macports-users 
>  wrote:
> 
> Maybe I am misled by a hidden problem but when I moved from Lion to Sierra 
> for similar reasons (browsers not maintained anymore for 10.7, etc.) I 
> experienced a strong slow down of my machine (MBP, 8 Gb Ram, hard drive). I 
> recovered speed when it died and I moved to a more recent machine with 16Gb 
> and a SSD. So I would cautiously upgrade to Mavericks or Yosemite and stop 
> there if enough in your case.
> 
> LP

There is a massive amount of conversion work done in the background when you 
first upgrade to Sierra or High Sierra.
Allowing the system to chug along for about 24 hours (depending on your disk 
size) gets rid of the sluggishness.

There is a “notification” which pops up warning you of this when you first 
login after the upgrade, but it is quickly dismissed and forgotten about. :)


T.T.F.N.
William H. Magill
# iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.13.1
# Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.13.1
# MacPro5,1 Quad-Core Intel Xeon [2.8 GHz - 16 GB 1066 MHz] OSX 10.13.1
mag...@icloud.com
mag...@mac.com
whmag...@gmail.com

Re: MacPorts related questions

[pagani laurent via macports-users]

Maybe I am misled by a hidden problem but when I moved from Lion to Sierra for 
similar reasons (browsers not maintained anymore for 10.7, etc.) I experienced 
a strong slow down of my machine (MBP, 8 Gb Ram, hard drive). I recovered speed 
when it died and I moved to a more recent machine with 16Gb and a SSD. So I 
would cautiously upgrade to Mavericks or Yosemite and stop there if enough in 
your case.

LP

> 
> 
> On Nov 14, 2017, at 03:39, iEFdev wrote:
> 
>>> Lion is old. If possible on your Mac, please consider upgrading to a newer 
>>> version of macOS.
>> 
>> Yes, I'll maybe go to ML. I stopped at Lion and didn't think ML brought much 
>> more to it, but it seems to be the bottom low version today. On my way to 
>> migrate my Mac Pro -> mini and the run it off-line. Perhaps I should do a 
>> clean install of ML then.
> 
> Mountain Lion is not much better, from our perspective, because Mountain Lion 
> and earlier use libstdc++, which doesn't support C++11, which many ports are 
> requiring. Mavericks and later use libc++ which supports C++11. If your Mac 
> can upgrade to Mountain Lion, it can upgrade to at least El Capitan, possibly 
> even High Sierra. I'd recommend you upgrade to the newest version you can.
> 
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: MacPorts related questions

[Ryan Schmidt]

On Nov 14, 2017, at 03:39, iEFdev wrote:

>> Lion is old. If possible on your Mac, please consider upgrading to a newer 
>> version of macOS.
> 
> Yes, I'll maybe go to ML. I stopped at Lion and didn't think ML brought much 
> more to it, but it seems to be the bottom low version today. On my way to 
> migrate my Mac Pro -> mini and the run it off-line. Perhaps I should do a 
> clean install of ML then.

Mountain Lion is not much better, from our perspective, because Mountain Lion 
and earlier use libstdc++, which doesn't support C++11, which many ports are 
requiring. Mavericks and later use libc++ which supports C++11. If your Mac can 
upgrade to Mountain Lion, it can upgrade to at least El Capitan, possibly even 
High Sierra. I'd recommend you upgrade to the newest version you can.