> 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
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
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?
> 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
>
> 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
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
* 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
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
>
* 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
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
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
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
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
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
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
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
$ 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
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
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
19 matches
Mail list logo
