Re: evince build as prerequisite to Denemo compile

[David Richmond]

Just an update that I have now fixed this issue solely by updating the
MacPorts version of evince to a newer release from upstream; I submitted a
pull request on github to that effect.

Once I had evince, the latest Denemo (2.4.0) compiled and ran successfully
from their distributed source.

Provided that Denemo proves as useful as I hope, I plan to work on updating
that port, as well, now that I have learned a little bit about how MacPorts
works under the hood.

David

On Sat, May 16, 2020 at 5:53 PM David Richmond  wrote:

> Hi all,
>
> I am trying to compile Denemo [1] on MacOS 10.15.4. Denemo has not had an
> updated MacPort for several years. I got all the dependencies to build
> except for evince, which appears to be otherwise rarely used and has an
> open bug 60407 [2] to which I attached a full log showing the compile error:
>
> EvinceView-3.0.gir
> :info:build ev-document-model.h:57:
> :info:build ev-document-model.h:33: Fatal: EvinceView: Namespace conflict
> for 'document_model_get_type'
> :info:build ev-document-model.h:33: Fatal: EvinceView: Namespace conflict
> for 'document_model_get_type'
> :info:build make[3]: *** [EvinceView-3.0.gir] Error 1
>
> While I do not (yet) consider myself sufficiently knowledgable to act on
> the following information, it appears (via GNOME [3], Debian [4]) that
> version 3.30 or even 3.36 might be reasonable updates to the 3.28 that
> MacPorts is trying to compile. Might this fix the compile error without too
> much trouble?
>
> [1] http://denemo.org/hacking-sources/
> [2] https://trac.macports.org/ticket/60407
> [3] http://ftp.gnome.org/pub/GNOME/sources/evince/
> [4] https://packages.debian.org/search?keywords=evince
>
> Thanks for any help in advance!
>
> David
>

Re: cltversion error

[Christopher Jones]

Hi,

Apple have been (not so) slowly depreciating the CLT. I more expect to see it 
completely disappear in some future OS…

Chris

> On 12 Jun 2020, at 9:40 pm, Mircea Trandafir  wrote:
> 
> Hi again,
> 
> I actually went the other route, I removed Xcode and only installed the CLT. 
> I thought it would help with this issue, but it seems not. Hopefully they’ll 
> fix the bug soon.
> 
> Cheers,
> Mircea
> -- 
> Mircea Trandafir
> Associate professor
> Department of Business and Economics, 
> University of Southern Denmark
> Campusvej 55, 5230 Odense M
> Denmark
> Web: http://www.mirceatrandafir.com 
> 
>> On 12 Jun 2020, at 10.35 PM, Christopher Jones > > wrote:
>> 
>> Hi,
>> 
>> Glad I could help.
>> 
>> Don’t though bank on this not reoccurring…. Its been an issue through the 
>> lifetime of 10.15, and tends to reoccur on OS or Xcode upgrades. I believe 
>> there is a bug somewhere in that Apple removes the CLT package receipts but 
>> not the CLT itself.
>> 
>> One fix is to completely remove the CLT. Its actually not really needed 
>> anymore - Just having Xcode installed is enough.
>> 
>> cheers Chris
>> 
>>> On 12 Jun 2020, at 9:30 pm, Mircea Trandafir >> > wrote:
>>> 
>>> Thanks Chris for the quick reply. It is a bit weird, because:
>>> 
>>> > xcode-select -p
>>> /Library/Developer/CommandLineTools
>>> 
>>> But:
>>> 
>>> > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
>>> No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.
>>> 
>>> I manually removed the CLT folder and reinstalled with:
>>> 
>>> > sudo xcode-select --install
>>> 
>>> > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
>>> package-id: com.apple.pkg.CLTools_Executables
>>> version: 11.5.0.0.1.1588476445
>>> volume: /
>>> location: /
>>> install-time: 1591993420
>>> groups: com.apple.FindSystemFiles.pkg-group
>>> 
>>> But I have no idea why it didn’t work/see the CLTs in the first place… 
>>> Thanks again, hopefully this problem won’t pop back up.
>>> 
>>> Best,
>>> Mircea
>>> -- 
>>> Mircea Trandafir
>>> Associate professor
>>> Department of Business and Economics, 
>>> University of Southern Denmark
>>> Campusvej 55, 5230 Odense M
>>> Denmark
>>> Web: http://www.mirceatrandafir.com 
>>> 
 On 12 Jun 2020, at 10.06 PM, Christopher Jones >>> > wrote:
 
 Hi,
 
 Please run this, and check you get something similar
 
  > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
 package-id: com.apple.pkg.CLTools_Executables
 version: 11.5.0.0.1.1588476445
 volume: /
 location: /
 install-time: 1591989507
 groups: com.apple.FindSystemFiles.pkg-group 
 
 If you don’t, then you indeed have the issue the warning is referring to 
 and you need to force reinstall the CLT
 
 Chris
 
> On 12 Jun 2020, at 8:10 pm, Mircea Trandafir  > wrote:
> 
> Hi all,
> 
> This is the first time I’m writing to the list, so let me first thank the 
> developers for such a great piece of software! And also a everyone on the 
> list, I’ve been a consumer of information for the past few years and I 
> learned quite a bit about macports and MacOS.
> 
> The reason for my cry for help is the following: for the past couple of 
> months, I keep getting the following message whenever I run port, 
> particularly port reclaim during the “Building list of distfiles still in 
> use” step:
> 
> Warning: cltversion: For a possible fix, please see: 
> https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 
> 
> 
> I followed the instructions at the link, I also uninstalled and 
> reinstalled Xcode, it keeps popping back up. I have two MacBook Pros and 
> the same thing happens on both. Here is my setup:
> 
> MacPro 15,2
> MacOS 10.15.5
> MacPorts base version 2.6.2 (standard location, /opt/local)
> 
> I can confirm that the command line tools are installed in 
> /Library/Developer/CommandLineTools and that the 10.15 SDK is present in 
> SDKs. Is there any thing I could do to get rid of this message, which is 
> getting quite annoying? Any ideas why it might have started in the first 
> place?
> 
> Thanks,
> Mircea
> -- 
> Mircea Trandafir
> Associate professor
> Department of Business and Economics, 
> University of Southern Denmark
> Campusvej 55, 5230 Odense M
> Denmark
> Web: http://www.mirceatrandafir.com 
 
>>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: cltversion error

[Mircea Trandafir]

Hi again,

I actually went the other route, I removed Xcode and only installed the CLT. I 
thought it would help with this issue, but it seems not. Hopefully they’ll fix 
the bug soon.

Cheers,
Mircea
-- 
Mircea Trandafir
Associate professor
Department of Business and Economics, 
University of Southern Denmark
Campusvej 55, 5230 Odense M
Denmark
Web: http://www.mirceatrandafir.com

> On 12 Jun 2020, at 10.35 PM, Christopher Jones  
> wrote:
> 
> Hi,
> 
> Glad I could help.
> 
> Don’t though bank on this not reoccurring…. Its been an issue through the 
> lifetime of 10.15, and tends to reoccur on OS or Xcode upgrades. I believe 
> there is a bug somewhere in that Apple removes the CLT package receipts but 
> not the CLT itself.
> 
> One fix is to completely remove the CLT. Its actually not really needed 
> anymore - Just having Xcode installed is enough.
> 
> cheers Chris
> 
>> On 12 Jun 2020, at 9:30 pm, Mircea Trandafir > > wrote:
>> 
>> Thanks Chris for the quick reply. It is a bit weird, because:
>> 
>> > xcode-select -p
>> /Library/Developer/CommandLineTools
>> 
>> But:
>> 
>> > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
>> No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.
>> 
>> I manually removed the CLT folder and reinstalled with:
>> 
>> > sudo xcode-select --install
>> 
>> > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
>> package-id: com.apple.pkg.CLTools_Executables
>> version: 11.5.0.0.1.1588476445
>> volume: /
>> location: /
>> install-time: 1591993420
>> groups: com.apple.FindSystemFiles.pkg-group
>> 
>> But I have no idea why it didn’t work/see the CLTs in the first place… 
>> Thanks again, hopefully this problem won’t pop back up.
>> 
>> Best,
>> Mircea
>> -- 
>> Mircea Trandafir
>> Associate professor
>> Department of Business and Economics, 
>> University of Southern Denmark
>> Campusvej 55, 5230 Odense M
>> Denmark
>> Web: http://www.mirceatrandafir.com 
>> 
>>> On 12 Jun 2020, at 10.06 PM, Christopher Jones >> > wrote:
>>> 
>>> Hi,
>>> 
>>> Please run this, and check you get something similar
>>> 
>>>  > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
>>> package-id: com.apple.pkg.CLTools_Executables
>>> version: 11.5.0.0.1.1588476445
>>> volume: /
>>> location: /
>>> install-time: 1591989507
>>> groups: com.apple.FindSystemFiles.pkg-group 
>>> 
>>> If you don’t, then you indeed have the issue the warning is referring to 
>>> and you need to force reinstall the CLT
>>> 
>>> Chris
>>> 
 On 12 Jun 2020, at 8:10 pm, Mircea Trandafir >>> > wrote:
 
 Hi all,
 
 This is the first time I’m writing to the list, so let me first thank the 
 developers for such a great piece of software! And also a everyone on the 
 list, I’ve been a consumer of information for the past few years and I 
 learned quite a bit about macports and MacOS.
 
 The reason for my cry for help is the following: for the past couple of 
 months, I keep getting the following message whenever I run port, 
 particularly port reclaim during the “Building list of distfiles still in 
 use” step:
 
 Warning: cltversion: For a possible fix, please see: 
 https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 
 
 
 I followed the instructions at the link, I also uninstalled and 
 reinstalled Xcode, it keeps popping back up. I have two MacBook Pros and 
 the same thing happens on both. Here is my setup:
 
 MacPro 15,2
 MacOS 10.15.5
 MacPorts base version 2.6.2 (standard location, /opt/local)
 
 I can confirm that the command line tools are installed in 
 /Library/Developer/CommandLineTools and that the 10.15 SDK is present in 
 SDKs. Is there any thing I could do to get rid of this message, which is 
 getting quite annoying? Any ideas why it might have started in the first 
 place?
 
 Thanks,
 Mircea
 -- 
 Mircea Trandafir
 Associate professor
 Department of Business and Economics, 
 University of Southern Denmark
 Campusvej 55, 5230 Odense M
 Denmark
 Web: http://www.mirceatrandafir.com 
>>> 
>> 
> 

Re: cltversion error

[Christopher Jones]

Hi,

Glad I could help.

Don’t though bank on this not reoccurring…. Its been an issue through the 
lifetime of 10.15, and tends to reoccur on OS or Xcode upgrades. I believe 
there is a bug somewhere in that Apple removes the CLT package receipts but not 
the CLT itself.

One fix is to completely remove the CLT. Its actually not really needed anymore 
- Just having Xcode installed is enough.

cheers Chris

> On 12 Jun 2020, at 9:30 pm, Mircea Trandafir  wrote:
> 
> Thanks Chris for the quick reply. It is a bit weird, because:
> 
> > xcode-select -p
> /Library/Developer/CommandLineTools
> 
> But:
> 
> > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
> No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.
> 
> I manually removed the CLT folder and reinstalled with:
> 
> > sudo xcode-select --install
> 
> > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
> package-id: com.apple.pkg.CLTools_Executables
> version: 11.5.0.0.1.1588476445
> volume: /
> location: /
> install-time: 1591993420
> groups: com.apple.FindSystemFiles.pkg-group
> 
> But I have no idea why it didn’t work/see the CLTs in the first place… Thanks 
> again, hopefully this problem won’t pop back up.
> 
> Best,
> Mircea
> -- 
> Mircea Trandafir
> Associate professor
> Department of Business and Economics, 
> University of Southern Denmark
> Campusvej 55, 5230 Odense M
> Denmark
> Web: http://www.mirceatrandafir.com 
> 
>> On 12 Jun 2020, at 10.06 PM, Christopher Jones > > wrote:
>> 
>> Hi,
>> 
>> Please run this, and check you get something similar
>> 
>>  > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
>> package-id: com.apple.pkg.CLTools_Executables
>> version: 11.5.0.0.1.1588476445
>> volume: /
>> location: /
>> install-time: 1591989507
>> groups: com.apple.FindSystemFiles.pkg-group 
>> 
>> If you don’t, then you indeed have the issue the warning is referring to and 
>> you need to force reinstall the CLT
>> 
>> Chris
>> 
>>> On 12 Jun 2020, at 8:10 pm, Mircea Trandafir >> > wrote:
>>> 
>>> Hi all,
>>> 
>>> This is the first time I’m writing to the list, so let me first thank the 
>>> developers for such a great piece of software! And also a everyone on the 
>>> list, I’ve been a consumer of information for the past few years and I 
>>> learned quite a bit about macports and MacOS.
>>> 
>>> The reason for my cry for help is the following: for the past couple of 
>>> months, I keep getting the following message whenever I run port, 
>>> particularly port reclaim during the “Building list of distfiles still in 
>>> use” step:
>>> 
>>> Warning: cltversion: For a possible fix, please see: 
>>> https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 
>>> 
>>> 
>>> I followed the instructions at the link, I also uninstalled and reinstalled 
>>> Xcode, it keeps popping back up. I have two MacBook Pros and the same thing 
>>> happens on both. Here is my setup:
>>> 
>>> MacPro 15,2
>>> MacOS 10.15.5
>>> MacPorts base version 2.6.2 (standard location, /opt/local)
>>> 
>>> I can confirm that the command line tools are installed in 
>>> /Library/Developer/CommandLineTools and that the 10.15 SDK is present in 
>>> SDKs. Is there any thing I could do to get rid of this message, which is 
>>> getting quite annoying? Any ideas why it might have started in the first 
>>> place?
>>> 
>>> Thanks,
>>> Mircea
>>> -- 
>>> Mircea Trandafir
>>> Associate professor
>>> Department of Business and Economics, 
>>> University of Southern Denmark
>>> Campusvej 55, 5230 Odense M
>>> Denmark
>>> Web: http://www.mirceatrandafir.com 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: cltversion error

[Mircea Trandafir]

Thanks Chris for the quick reply. It is a bit weird, because:

> xcode-select -p
/Library/Developer/CommandLineTools

But:

> /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.

I manually removed the CLT folder and reinstalled with:

> sudo xcode-select --install

> /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
package-id: com.apple.pkg.CLTools_Executables
version: 11.5.0.0.1.1588476445
volume: /
location: /
install-time: 1591993420
groups: com.apple.FindSystemFiles.pkg-group

But I have no idea why it didn’t work/see the CLTs in the first place… Thanks 
again, hopefully this problem won’t pop back up.

Best,
Mircea
-- 
Mircea Trandafir
Associate professor
Department of Business and Economics, 
University of Southern Denmark
Campusvej 55, 5230 Odense M
Denmark
Web: http://www.mirceatrandafir.com

> On 12 Jun 2020, at 10.06 PM, Christopher Jones  
> wrote:
> 
> Hi,
> 
> Please run this, and check you get something similar
> 
>  > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
> package-id: com.apple.pkg.CLTools_Executables
> version: 11.5.0.0.1.1588476445
> volume: /
> location: /
> install-time: 1591989507
> groups: com.apple.FindSystemFiles.pkg-group 
> 
> If you don’t, then you indeed have the issue the warning is referring to and 
> you need to force reinstall the CLT
> 
> Chris
> 
>> On 12 Jun 2020, at 8:10 pm, Mircea Trandafir > > wrote:
>> 
>> Hi all,
>> 
>> This is the first time I’m writing to the list, so let me first thank the 
>> developers for such a great piece of software! And also a everyone on the 
>> list, I’ve been a consumer of information for the past few years and I 
>> learned quite a bit about macports and MacOS.
>> 
>> The reason for my cry for help is the following: for the past couple of 
>> months, I keep getting the following message whenever I run port, 
>> particularly port reclaim during the “Building list of distfiles still in 
>> use” step:
>> 
>> Warning: cltversion: For a possible fix, please see: 
>> https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 
>> 
>> 
>> I followed the instructions at the link, I also uninstalled and reinstalled 
>> Xcode, it keeps popping back up. I have two MacBook Pros and the same thing 
>> happens on both. Here is my setup:
>> 
>> MacPro 15,2
>> MacOS 10.15.5
>> MacPorts base version 2.6.2 (standard location, /opt/local)
>> 
>> I can confirm that the command line tools are installed in 
>> /Library/Developer/CommandLineTools and that the 10.15 SDK is present in 
>> SDKs. Is there any thing I could do to get rid of this message, which is 
>> getting quite annoying? Any ideas why it might have started in the first 
>> place?
>> 
>> Thanks,
>> Mircea
>> -- 
>> Mircea Trandafir
>> Associate professor
>> Department of Business and Economics, 
>> University of Southern Denmark
>> Campusvej 55, 5230 Odense M
>> Denmark
>> Web: http://www.mirceatrandafir.com 
> 

Re: cltversion error

[Christopher Jones]

Hi,

Please run this, and check you get something similar

 > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
package-id: com.apple.pkg.CLTools_Executables
version: 11.5.0.0.1.1588476445
volume: /
location: /
install-time: 1591989507
groups: com.apple.FindSystemFiles.pkg-group 

If you don’t, then you indeed have the issue the warning is referring to and 
you need to force reinstall the CLT

Chris

> On 12 Jun 2020, at 8:10 pm, Mircea Trandafir  wrote:
> 
> Hi all,
> 
> This is the first time I’m writing to the list, so let me first thank the 
> developers for such a great piece of software! And also a everyone on the 
> list, I’ve been a consumer of information for the past few years and I 
> learned quite a bit about macports and MacOS.
> 
> The reason for my cry for help is the following: for the past couple of 
> months, I keep getting the following message whenever I run port, 
> particularly port reclaim during the “Building list of distfiles still in 
> use” step:
> 
> Warning: cltversion: For a possible fix, please see: 
> https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 
> 
> 
> I followed the instructions at the link, I also uninstalled and reinstalled 
> Xcode, it keeps popping back up. I have two MacBook Pros and the same thing 
> happens on both. Here is my setup:
> 
> MacPro 15,2
> MacOS 10.15.5
> MacPorts base version 2.6.2 (standard location, /opt/local)
> 
> I can confirm that the command line tools are installed in 
> /Library/Developer/CommandLineTools and that the 10.15 SDK is present in 
> SDKs. Is there any thing I could do to get rid of this message, which is 
> getting quite annoying? Any ideas why it might have started in the first 
> place?
> 
> Thanks,
> Mircea
> -- 
> Mircea Trandafir
> Associate professor
> Department of Business and Economics, 
> University of Southern Denmark
> Campusvej 55, 5230 Odense M
> Denmark
> Web: http://www.mirceatrandafir.com 



smime.p7s
Description: S/MIME cryptographic signature

cltversion error

[Mircea Trandafir]

Hi all,

This is the first time I’m writing to the list, so let me first thank the 
developers for such a great piece of software! And also a everyone on the list, 
I’ve been a consumer of information for the past few years and I learned quite 
a bit about macports and MacOS.

The reason for my cry for help is the following: for the past couple of months, 
I keep getting the following message whenever I run port, particularly port 
reclaim during the “Building list of distfiles still in use” step:

Warning: cltversion: For a possible fix, please see: 
https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt

I followed the instructions at the link, I also uninstalled and reinstalled 
Xcode, it keeps popping back up. I have two MacBook Pros and the same thing 
happens on both. Here is my setup:

MacPro 15,2
MacOS 10.15.5
MacPorts base version 2.6.2 (standard location, /opt/local)

I can confirm that the command line tools are installed in 
/Library/Developer/CommandLineTools and that the 10.15 SDK is present in SDKs. 
Is there any thing I could do to get rid of this message, which is getting 
quite annoying? Any ideas why it might have started in the first place?

Thanks,
Mircea
-- 
Mircea Trandafir
Associate professor
Department of Business and Economics, 
University of Southern Denmark
Campusvej 55, 5230 Odense M
Denmark
Web: http://www.mirceatrandafir.com

Call for designers for our ports website

[Mojca Miklavec]

Dear MacPorters,

As part of a GSOC project Arjun has been working on great new features
for our web application with information about ports.

The application from last year has been deployed at
https://ports.macports.org/
while the new testing site is temporarily located at
http://macports.silentfox.tech/

The website already looks nice, but if we had some talented designers
among our users willing to help us go one step beyond what we have
right now, we would be extremely grateful for either just some advice
or potentially some more extensive help. There are a lot of minor
tweaks that could be done, but neither of us is a designer, and I'm
not able to give any competent advice about how to best improve the
layout.

Here are some concrete examples of subpages:
- http://macports.silentfox.tech/port/root6/
- http://macports.silentfox.tech/port/gnuplot/stats/?days=365_ago=0
- http://macports.silentfox.tech/search/?installed_file==root=on

Thank you very much in advance,
Mojca

Re: TenFourFox-Intel -- current browser for older systems

[Ken Cunningham]

> Unfortunately true "feature parity" turned out to be too 
> difficult to maintain for Cameron, so things like online banking by and 
> large don't work anymore.
He's pretty close. Security is right up to date, TLS 1.3, he is no more than a 
few weeks behind at most on security patches from the FireFox tree. Amazing, 
really.

There are some new web features that are apparently hard to implement...written 
in Rust, I think, which as you know is not so functional on 10.4. The bank I 
use works great with TFF, I guess it doesn't use those web features. And 
amazon, ebay, youtube, macports, wikipedia, etc, etc, etc, all work normally.

GitHub does use some of them, as of last year, so it has a hiccup.

Cameron said he watched the entire Democratic debate on a G5 running 
TenFourFox, all 2+hours of streaming video, without a hiccup.

The intel version works very well for me, almost never crashes. Perhaps 95% of 
websites work as expected.

Ken