Re: Lilypond-devel & Big Sur?

[Stan Sanderson]

> On Apr 5, 2022, at 5:27 PM, Ryan Schmidt  wrote:
> 
> On Apr 5, 2022, at 13:04, Stanton Sanderson wrote:
> 
>> Wondering if anyone else has found problems with the latest update of 
>> Lilypond-devel (to v 2.23.7) on Big Sur (11.6.5) and Frescobaldi (3.1.3)… 
>> Had to revert to Lilypond-devel 2.23.6.
> 
> Would you care to specify what those problems were?

This all too obvious question was expected. I have been reluctant to 
reinstall/reactivate lilypond-devel 2.23.7 since I’ve been using Lilypond 
extensively. 

So I reinstalled on one machine, and did the deactivate (2.23.6) and activate 
(2.23.7) on the other. Compiled updated files on both machines with no errors 
reported. The obvious answer is operator error, too little faith in Macports 
and worry about the time involved in further testing.

What I think I saw before might have been a gs error; all is good now.

Sorry for the noise, thanks for the query, and much gratitude for your work.

-Stan

Re: "list-unsubscribe" mail header & no footer

[André-John Mas]

My entry was:

"L:macports-users.lists.macports.org" => {
  "updatedAt" => 667601013
  "value" => "accepted"
}

but trying to remove it makes no difference. I tried that while the mail client 
was quit. It reappears, but the
unsubscribe button doesn't appear for this list.

Using Apple Mail 16.0 and receiving on via gmail. Only seems to impact this 
mailing list. Will need to dig more.

The main reason for bringing this up is that I have seen lists getting marked 
as spam when enough
people can't work out how to unsubscribe.

> On 5 Apr, 2022, at 15:38, Mike Cappella  wrote:
> 
> 
> 
>> On Apr 5, 2022, at 11:12 AM, André-John Mas > > wrote:
>> 
>> I just noticed that the emails for "macports users" aren't showing the 
>> "unsubscribe" button in
>> Apple Mail and they don't have a footer to link to unsubscribe instructions, 
>> as I am used to
>> seeing in other list server based messages.
>> 
>> Which is the right channel to bring up this issue?
> 
> You've likely hit the X to clear the Unsubscribe button, and this gets stored 
> as a property:
> 
> ~/Library/Mail/V9/MailData/
> 
> $ plutil -p 
> EMUbiquitouslyPersistedDictionary-com.apple.mail.listUnsubscribeInfo.plist
> {
>   "data" => {
> ...
> "L:macports-users.lists.macports.org 
> " => {
>   "updatedAt" => 670876830
>   "value" => "ignored"
> }
>   }
>   "version" => 1
> }
> 
> Note the value "ignored" above, which I believe prevents showing the 
> Unsubscribe button.
> 
> They will also be in the sandboxed area:
> 
> ~/Library/Containers/com.apple.Mail/Data/Library/Mail/V9/MailData/
> 
> I'm not sure what path to provide to clear the property.

Re: Lilypond-devel & Big Sur?

[Ryan Schmidt]

On Apr 5, 2022, at 13:04, Stanton Sanderson wrote:

> Wondering if anyone else has found problems with the latest update of 
> Lilypond-devel (to v 2.23.7) on Big Sur (11.6.5) and Frescobaldi (3.1.3)… Had 
> to revert to Lilypond-devel 2.23.6.

Would you care to specify what those problems were?

Re: libusb-devel port

[Chris Jones]

> On 5 Apr 2022, at 3:08 pm, Christoph Kukulies  wrote:
> 
> Thanks. Assumed I have downloaded a binary release from libusb’s github 
> Releases and it looks like that in the tree:
> 
> $ find macos_11.6
> macos_11.6
> macos_11.6/.DS_Store
> macos_11.6/bin
> macos_11.6/bin/dpfp
> macos_11.6/bin/listdevs
> macos_11.6/bin/sam3u_benchmark
> macos_11.6/bin/fxload
> macos_11.6/bin/xusb
> macos_11.6/bin/testlibusb
> macos_11.6/bin/hotplugtest
> macos_11.6/bin/stress
> macos_11.6/include
> macos_11.6/include/.DS_Store
> macos_11.6/include/libusb-1.0
> macos_11.6/include/libusb-1.0/libusb.h
> macos_11.6/lib
> macos_11.6/lib/pkgconfig
> macos_11.6/lib/pkgconfig/libusb-1.0.pc
> macos_11.6/lib/libusb-1.0.dylib
> macos_11.6/lib/libusb-1.0.0.dylib
> macos_11.6/lib/libusb-1.0.a
> macos_11.6/lib/libusb-1.0.la
> 
> How can I make these active in libusb-devel or otherwise available?

You cannot. Macports strongly prefers to build ports from source itself, and 
only redistributes rebuilt binaries in extreme circumstances.

You need to update the port file to fetch and then build a newer github 
revision for the devel subport. See

https://github.com/macports/macports-ports/blob/584723a8c2a65990bd0566b226f8c31b7f30fce5/devel/libusb/Portfile

See line 60 onwards.

That said, the devel port currently builds a revision that appears to be from 
the 3rd of April this year, so is pretty recent. Is this not new enough ?

Chris


> 
> Do the pkgconfig .pc files play a role in the installation mechanism?
> 
> —
> Christoph
> 
>> Am 05.04.2022 um 15:36 schrieb Chris Jones :
>> 
>> 
>>> On 05/04/2022 1:54 pm, Christoph Kukulies wrote:
>>> Thanks. Nonetheless I don‘t get how I can aim at a specific version or 
>>> 1.0.26-rc1 „HEAD“
>> 
>> you cannot. You still get whatever version libusb-devel is current set to 
>> provide. The idea of a X-devel port though is these can be updated and 
>> tested without affecting the default X port.
>> 
>> If you want a different version than libusb-devel currently provides, then 
>> you need to update the port to provide this.
>> 
>>> Btw, what is the correspondent to
>>> ldd
>>> under macOS?
>> 
>> otool -L
>> 
>>> —
>>> Christoph
 Am 05.04.2022 um 12:56 schrieb Chris Jones :
 
 
 
> On 05/04/2022 11:50 am, Christoph Kukulies wrote:
> $ sudo port deactivate libusb @1.0.25_0
> Password:
> Note: It is not recommended to uninstall/deactivate a port that has 
> dependents as it breaks the dependents.
> The following ports will break:
>  libusb-compat @0.1.7_0
>  openocd @0.11.0_0
>  usbutils @007_1
>  libftdi1 @1.5_1
>  qemu @6.2.0_0
>  stlink @1.7.0_1
> Continue? [y/N]:
> 
> OK to continue?
 
 yes.
 
 ports that depend on libusb should use a path style dependency, to allow 
 libusb or libusb-devel to satisfy it
 
 path:lib/pkgconfig/libusb-1.0.pc:libusb
 
 so assuming you are about to install libusb-devel its fine.
> 

Re: "list-unsubscribe" mail header & no footer

[Mike Cappella]

> On Apr 5, 2022, at 11:12 AM, André-John Mas  wrote:
> 
> I just noticed that the emails for "macports users" aren't showing the 
> "unsubscribe" button in
> Apple Mail and they don't have a footer to link to unsubscribe instructions, 
> as I am used to
> seeing in other list server based messages.
> 
> Which is the right channel to bring up this issue?

You've likely hit the X to clear the Unsubscribe button, and this gets stored 
as a property:

~/Library/Mail/V9/MailData/

$ plutil -p 
EMUbiquitouslyPersistedDictionary-com.apple.mail.listUnsubscribeInfo.plist
{
  "data" => {
...
"L:macports-users.lists.macports.org" => {
  "updatedAt" => 670876830
  "value" => "ignored"
}
  }
  "version" => 1
}

Note the value "ignored" above, which I believe prevents showing the 
Unsubscribe button.

They will also be in the sandboxed area:

~/Library/Containers/com.apple.Mail/Data/Library/Mail/V9/MailData/

I'm not sure what path to provide to clear the property.

Re: "list-unsubscribe" mail header & no footer

[Sriranga Veeraraghavan]

Hi Andre-John,

I agree with Ralph, it might be something on your computer.  

On BigSur (11.6.5) Mail.app (Apple Mail) shows me an unsubscribe option right 
below the headers for messages from the macports mailing lists.  On iOS 15.4.1, 
I get a big unsubscribe option above the headers for macports mailing lists. 

Best,

-ranga


> On Apr 5, 2022, at 11:50, Ralph Seichter via macports-users 
>  wrote:
> 
> * André-John Mas:
> 
>> Maybe this is impacting me only?
> 
> Looks like that might be the case: https://imgur.com/a/0KtaLZM
> 
> The screenshot I took shows that Apple Mail displays an "unsubscribe"
> action buttion for me. I am running macOS Monterey (version 12.3.1).
> 
> -Ralph

Re: "list-unsubscribe" mail header & no footer

[Ralph Seichter via macports-users]

* André-John Mas:

> Maybe this is impacting me only?

Looks like that might be the case: https://imgur.com/a/0KtaLZM

The screenshot I took shows that Apple Mail displays an "unsubscribe"
action buttion for me. I am running macOS Monterey (version 12.3.1).

-Ralph

Re: "list-unsubscribe" mail header & no footer

[André-John Mas]

Fair enough for the footer, but not sure why Apple Mail is not recognising the 
headers
here for unsubscribe. I do see them there, but something is not behaving the 
same
as on other mailing lists.

Maybe this is impacting me only?

> On 5 Apr, 2022, at 14:30, Ralph Seichter via macports-users 
>  wrote:
> 
> * André-John Mas:
> 
>> I just noticed that the emails for "macports users" aren't showing the
>> "unsubscribe" button in Apple Mail and they don't have a footer to
>> link to unsubscribe instructions, as I am used to seeing in other list
>> server based messages.
> 
> All messages from this mailing list have a "List-Unsubscribe" and
> various other List-* headers. That's all a decent MUA requires. Message
> footers and subject prefixes break DKIM signatures and are therefore to
> be avoided.
> 
> -Ralph

Re: "list-unsubscribe" mail header & no footer

[Ralph Seichter via macports-users]

* André-John Mas:

> I just noticed that the emails for "macports users" aren't showing the
> "unsubscribe" button in Apple Mail and they don't have a footer to
> link to unsubscribe instructions, as I am used to seeing in other list
> server based messages.

All messages from this mailing list have a "List-Unsubscribe" and
various other List-* headers. That's all a decent MUA requires. Message
footers and subject prefixes break DKIM signatures and are therefore to
be avoided.

-Ralph

"list-unsubscribe" mail header & no footer

[André-John Mas]

Hi,

I just noticed that the emails for "macports users" aren't showing the 
"unsubscribe" button in
Apple Mail and they don't have a footer to link to unsubscribe instructions, as 
I am used to
seeing in other list server based messages.

Which is the right channel to bring up this issue?

Thanks

Andre

Lilypond-devel & Big Sur?

[Stanton Sanderson]

Wondering if anyone else has found problems with the latest update of 
Lilypond-devel (to v 2.23.7) on Big Sur (11.6.5) and Frescobaldi (3.1.3)… Had 
to revert to Lilypond-devel 2.23.6.

Thanks, Stan

Re: libusb-devel port

[Ryan Schmidt]

On Apr 5, 2022, at 09:08, Christoph Kukulies wrote:

> Thanks. Assumed I have downloaded a binary release from libusb’s github 
> Releases and it looks like that in the tree:
> 
> $ find macos_11.6
> macos_11.6
> macos_11.6/.DS_Store
> macos_11.6/bin
> macos_11.6/bin/dpfp
> macos_11.6/bin/listdevs
> macos_11.6/bin/sam3u_benchmark
> macos_11.6/bin/fxload
> macos_11.6/bin/xusb
> macos_11.6/bin/testlibusb
> macos_11.6/bin/hotplugtest
> macos_11.6/bin/stress
> macos_11.6/include
> macos_11.6/include/.DS_Store
> macos_11.6/include/libusb-1.0
> macos_11.6/include/libusb-1.0/libusb.h
> macos_11.6/lib
> macos_11.6/lib/pkgconfig
> macos_11.6/lib/pkgconfig/libusb-1.0.pc
> macos_11.6/lib/libusb-1.0.dylib
> macos_11.6/lib/libusb-1.0.0.dylib
> macos_11.6/lib/libusb-1.0.a
> macos_11.6/lib/libusb-1.0.la
> 
> How can I make these active in libusb-devel or otherwise available?

I don't understand the question. MacPorts doesn't generally use binaries 
provided by upstream developers. Instead, MacPorts builds projects from source. 
Depending on various factors, you might receive a binary that we compiled on 
our servers, or MacPorts may build it from source on your system. The 
libusb-devel port currently installs version @20220403-bfbef179. If you wish 
for it to install a different version, you can edit the libusb-devel Portfile 
(the file identified by the command `port file libusb-devel`.) You can see what 
files the port installed by running `port contents libusb-devel` after 
installing it.

> Do the pkgconfig .pc files play a role in the installation mechanism?

The libusb-1.0.pc file tells other programs how to find libusb at build time.

Re: libusb-devel port

[Christoph Kukulies]

Thanks. Assumed I have downloaded a binary release from libusb’s github 
Releases and it looks like that in the tree:

$ find macos_11.6
macos_11.6
macos_11.6/.DS_Store
macos_11.6/bin
macos_11.6/bin/dpfp
macos_11.6/bin/listdevs
macos_11.6/bin/sam3u_benchmark
macos_11.6/bin/fxload
macos_11.6/bin/xusb
macos_11.6/bin/testlibusb
macos_11.6/bin/hotplugtest
macos_11.6/bin/stress
macos_11.6/include
macos_11.6/include/.DS_Store
macos_11.6/include/libusb-1.0
macos_11.6/include/libusb-1.0/libusb.h
macos_11.6/lib
macos_11.6/lib/pkgconfig
macos_11.6/lib/pkgconfig/libusb-1.0.pc
macos_11.6/lib/libusb-1.0.dylib
macos_11.6/lib/libusb-1.0.0.dylib
macos_11.6/lib/libusb-1.0.a
macos_11.6/lib/libusb-1.0.la

How can I make these active in libusb-devel or otherwise available?

Do the pkgconfig .pc files play a role in the installation mechanism?

—
Christoph

> Am 05.04.2022 um 15:36 schrieb Chris Jones :
> 
> 
> On 05/04/2022 1:54 pm, Christoph Kukulies wrote:
>> Thanks. Nonetheless I don‘t get how I can aim at a specific version or 
>> 1.0.26-rc1 „HEAD“
> 
> you cannot. You still get whatever version libusb-devel is current set to 
> provide. The idea of a X-devel port though is these can be updated and tested 
> without affecting the default X port.
> 
> If you want a different version than libusb-devel currently provides, then 
> you need to update the port to provide this.
> 
>> Btw, what is the correspondent to
>> ldd
>> under macOS?
> 
> otool -L
> 
>> —
>> Christoph
>>> Am 05.04.2022 um 12:56 schrieb Chris Jones :
>>> 
>>> 
>>> 
 On 05/04/2022 11:50 am, Christoph Kukulies wrote:
 $ sudo port deactivate libusb @1.0.25_0
 Password:
 Note: It is not recommended to uninstall/deactivate a port that has 
 dependents as it breaks the dependents.
 The following ports will break:
  libusb-compat @0.1.7_0
  openocd @0.11.0_0
  usbutils @007_1
  libftdi1 @1.5_1
  qemu @6.2.0_0
  stlink @1.7.0_1
 Continue? [y/N]:
 
 OK to continue?
>>> 
>>> yes.
>>> 
>>> ports that depend on libusb should use a path style dependency, to allow 
>>> libusb or libusb-devel to satisfy it
>>> 
>>> path:lib/pkgconfig/libusb-1.0.pc:libusb
>>> 
>>> so assuming you are about to install libusb-devel its fine.



smime.p7s
Description: S/MIME cryptographic signature

Re: libusb-devel port

[Chris Jones]

On 05/04/2022 1:54 pm, Christoph Kukulies wrote:

Thanks. Nonetheless I don‘t get how I can aim at a specific version or 
1.0.26-rc1 „HEAD“


you cannot. You still get whatever version libusb-devel is current set 
to provide. The idea of a X-devel port though is these can be updated 
and tested without affecting the default X port.


If you want a different version than libusb-devel currently provides, 
then you need to update the port to provide this.




Btw, what is the correspondent to

ldd

under macOS?


otool -L



—
Christoph


Am 05.04.2022 um 12:56 schrieb Chris Jones :




On 05/04/2022 11:50 am, Christoph Kukulies wrote:
$ sudo port deactivate libusb @1.0.25_0
Password:
Note: It is not recommended to uninstall/deactivate a port that has dependents 
as it breaks the dependents.
The following ports will break:
  libusb-compat @0.1.7_0
  openocd @0.11.0_0
  usbutils @007_1
  libftdi1 @1.5_1
  qemu @6.2.0_0
  stlink @1.7.0_1
Continue? [y/N]:

OK to continue?


yes.

ports that depend on libusb should use a path style dependency, to allow libusb 
or libusb-devel to satisfy it

path:lib/pkgconfig/libusb-1.0.pc:libusb

so assuming you are about to install libusb-devel its fine.

Re: libusb-devel port

[Christoph Kukulies]

Thanks. Nonetheless I don‘t get how I can aim at a specific version or 
1.0.26-rc1 „HEAD“

Btw, what is the correspondent to

ldd

under macOS?

—
Christoph 

> Am 05.04.2022 um 12:56 schrieb Chris Jones :
> 
> 
> 
>> On 05/04/2022 11:50 am, Christoph Kukulies wrote:
>> $ sudo port deactivate libusb @1.0.25_0
>> Password:
>> Note: It is not recommended to uninstall/deactivate a port that has 
>> dependents as it breaks the dependents.
>> The following ports will break:
>>  libusb-compat @0.1.7_0
>>  openocd @0.11.0_0
>>  usbutils @007_1
>>  libftdi1 @1.5_1
>>  qemu @6.2.0_0
>>  stlink @1.7.0_1
>> Continue? [y/N]:
> >
> > OK to continue?
> 
> yes.
> 
> ports that depend on libusb should use a path style dependency, to allow 
> libusb or libusb-devel to satisfy it
> 
> path:lib/pkgconfig/libusb-1.0.pc:libusb
> 
> so assuming you are about to install libusb-devel its fine.

Re: libusb-devel port

[Chris Jones]

On 05/04/2022 11:50 am, Christoph Kukulies wrote:

$ sudo port deactivate libusb @1.0.25_0
Password:
Note: It is not recommended to uninstall/deactivate a port that has 
dependents as it breaks the dependents.

The following ports will break:
  libusb-compat @0.1.7_0
  openocd @0.11.0_0
  usbutils @007_1
  libftdi1 @1.5_1
  qemu @6.2.0_0
  stlink @1.7.0_1
Continue? [y/N]:

>
> OK to continue?

yes.

ports that depend on libusb should use a path style dependency, to allow 
libusb or libusb-devel to satisfy it


path:lib/pkgconfig/libusb-1.0.pc:libusb

so assuming you are about to install libusb-devel its fine.

Re: libusb-devel port

[Christoph Kukulies]

$ sudo port deactivate libusb @1.0.25_0
Password:
Note: It is not recommended to uninstall/deactivate a port that has dependents 
as it breaks the dependents.
The following ports will break:
 libusb-compat @0.1.7_0
 openocd @0.11.0_0
 usbutils @007_1
 libftdi1 @1.5_1
 qemu @6.2.0_0
 stlink @1.7.0_1
Continue? [y/N]: 





OK to continue?

—
Christoph 


> Am 05.04.2022 um 12:40 schrieb Chris Jones :
> 
> 
> 
> On 05/04/2022 11:33 am, Christoph Kukulies wrote:
>> I’m in the need of testing a libusb issue with an intermediate build of 
>> libusb (1.0.26-rc1, that is)
>> Since I’m always reluctant of mixing brew and macports - is that actually 
>> „dangerous“ or impossible at all, should that be avoided or can it be done -
>> One of the developers of libusb told me that the libusb-devel port is 
>> broken. I’d prefer using macports. Trying it, I got:
>> $ sudo port install libusb-devel
>> Password:
>> Error: Can't install libusb-devel because conflicting ports are active: 
>> libusb
>> Error: Follow https://guide.macports.org/#project.tickets 
>>  if you believe there is a bug.
>> Error: Processing of port libusb-devel failed
>> $
>> Any advice?
> 
> you need to deacivate libusb first
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: libusb-devel port

[Chris Jones]

On 05/04/2022 11:33 am, Christoph Kukulies wrote:
I’m in the need of testing a libusb issue with an intermediate build of 
libusb (1.0.26-rc1, that is)


Since I’m always reluctant of mixing brew and macports - is that 
actually „dangerous“ or impossible at all, should that be avoided or can 
it be done -


One of the developers of libusb told me that the libusb-devel port is 
broken. I’d prefer using macports. Trying it, I got:


$ sudo port install libusb-devel
Password:

Error: Can't install libusb-devel because conflicting ports are active: 
libusb
Error: Follow https://guide.macports.org/#project.tickets 
 if you believe there is a bug.

Error: Processing of port libusb-devel failed
$

Any advice?


you need to deacivate libusb first

libusb-devel port

[Christoph Kukulies]

I’m in the need of testing a libusb issue with an intermediate build of libusb 
(1.0.26-rc1, that is)

Since I’m always reluctant of mixing brew and macports - is that actually 
„dangerous“ or impossible at all, should that be avoided or can it be done -

One of the developers of libusb told me that the libusb-devel port is broken. 
I’d prefer using macports. Trying it, I got:

$ sudo port install libusb-devel
Password:

Error: Can't install libusb-devel because conflicting ports are active: libusb
Error: Follow https://guide.macports.org/#project.tickets if you believe there 
is a bug.
Error: Processing of port libusb-devel failed
$ 

Any advice?

—
Christoph




smime.p7s
Description: S/MIME cryptographic signature