On 2023-12-12 6:16, Piotr Smyrak wrote:
On Tue, 12 Dec 2023 04:01:23 -0800
list_free...@bluerosetech.com wrote:
On 2023-10-24 15:12, Dan Mahoney (Ports) wrote:
Yes, I know that I should be ready to upgrade to 15 at some point,
on whatever quarterly port boundary it's decided, "I guess that's
w
On Tue, 12 Dec 2023 15:16:37 +0100
Piotr Smyrak wrote:
> On Tue, 12 Dec 2023 04:01:23 -0800
> list_free...@bluerosetech.com wrote:
>
> > On 2023-10-24 15:12, Dan Mahoney (Ports) wrote:
> > > Yes, I know that I should be ready to upgrade to 15 at some point,
> > > on whatever quarterly port bou
On Tue, Dec 12, 2023 at 04:01:23AM -0800, list_free...@bluerosetech.com wrote:
>
> On 2023-10-24 15:12, Dan Mahoney (Ports) wrote:
> > Yes, I know that I should be ready to upgrade to 15 at some point, on
> > whatever quarterly port boundary it's decided, "I guess that's when",
> > with no advanc
On 2023-10-24 15:12, Dan Mahoney (Ports) wrote:
Yes, I know that I should be ready to upgrade to 15 at some point, on
whatever quarterly port boundary it's decided, "I guess that's when",
with no advance notice, via the full stupid dump-and-restore
process.
I know it's too late now, but run pos
On Tue, 24 Oct 2023, Dan Mahoney (Ports) wrote:
All,
I’ve lost another morning to a bad choice made by ports/pkg.
Maybe this is a dumb question/rant, but recently, a routine pkg upgrade
of the dayjob’s RT VM (which included an upgrade to perl) decided to
leave me with no ability to connect.
All,
I’ve lost another morning to a bad choice made by ports/pkg.
Maybe this is a dumb question/rant, but recently, a routine pkg upgrade of the
dayjob’s RT VM (which included an upgrade to perl) decided to leave me with no
ability to connect. After following the rabbit hole, I hit a database
