Hello,
I maintain in private a port (in fact, it is Espressif ESP-IDF for ESP chips).
The port itself is hosted via GITHUB. Download and installing of the sources
has been
performed successfuly.
The port has several Python based scripts which start accessing the internet
reeling in
several add
Hello Mikael,
First of all, I would like to thank you for your work on Signal Desktop,
even though I know that you have dropped the maintainership. I really
appreciate it!
I see that there is now a version 7.5 in the ports tree from you, but
according to Freshports there is no binary package fo
From: Yasuhiro Kimura
Subject: Re: `pkg autoremove` uninstalls pkg itself
Date: Fri, 19 Apr 2024 21:43:07 +0900 (JST)
> My question is, then, why what didn't happen before has happend?
>
> A. Something (ports-mgmt/pkg or ports framework) has changed
>resently so `pkg` is marked as automatica
From: Yasuhiro Kimura
Subject: Re: `pkg autoremove` uninstalls pkg itself
Date: Sun, 21 Apr 2024 22:30:26 +0900 (JST)
> Just from curiosity I checked out following commit and tested if the
> issue also happens (I selected the commit just because it was
> committed on the release date of 14.0-RELE
On Sunday, April 21, 2024 12:01:30 PM CEST Miroslav Lachman wrote:
> Hello Mikael,
> First of all, I would like to thank you for your work on Signal Desktop,
> even though I know that you have dropped the maintainership. I really
> appreciate it!
> I see that there is now a version 7.5 in the ports
For example, I've got a fallout message for 133amd64 for misc/py-mmcv,
but https://portsfallout.com/ shows zero fallout for this port, when
searched by port origin.
Thanks,
Yuri
Hi,
On Fri, 19 Apr 2024, at 18:34, TIM KELLERS wrote:
> I managed to get desktop-signal 7.5.0 built from source on a 3 day old
> Current. It took quit a while to gt all of the dependcies rebuilt from
> a fresh install, but I do have it running under KDE6
> uname is below, but you can see its o
Good morning.
I think the reason why the automatic flag in pkg is not up is because there is
an .undef here.
https: //cgit.freebsd.org /ports/tree/ports-mgmt/pkg/Makefile#n72
The package pkg is guessed to have been installed by a manual operation by the
bootstrap pkg. (This has not been confirm
On 21/04/2024 22:09, Stefan Ehmann wrote:
On Sunday, April 21, 2024 12:01:30 PM CEST Miroslav Lachman wrote:
Hello Mikael,
First of all, I would like to thank you for your work on Signal Desktop,
even though I know that you have dropped the maintainership. I really
appreciate it!
I see that ther
Yuri wrote on
Date: Sun, 21 Apr 2024 21:16:48 UTC :
> For example, I've got a fallout message for 133amd64 for misc/py-mmcv,
> but https://portsfallout.com/ shows zero fallout for this port, when
> searched by port origin.
The search field at https://pkg-status.freebsd.org/?all=1&type=packag
Dear port maintainers,
The portscout new distfile checker has detected that one or more
unmaintained ports appears to be out of date. Please take the opportunity
to check each of the ports listed below, and if possible and appropriate,
submit/commit an update. Please consider also adopting this po
From: Tatsuki Makino
Subject: Re: `pkg autoremove` uninstalls pkg itself
Date: Mon, 22 Apr 2024 07:35:13 +0900
> Good morning.
>
> I think the reason why the automatic flag in pkg is not up is because there
> is an .undef here.
> https: //cgit.freebsd.org /ports/tree/ports-mgmt/pkg/Makefile#n72
12 matches
Mail list logo
