On 2024-01-01, Ax0n wrote:
> On Fri, Dec 29, 2023 at 7:33 PM Stuart Henderson
> wrote:
>
>> Pity, without the deletes a transcript of a run of pkg_add -u -v
>> might have shown why the packages didn't get updated. They should have,
>> and in most cases they do.
>>
>
> Here's the pkg_add -uiv
On Fri, Dec 29, 2023 at 7:33 PM Stuart Henderson
wrote:
> Pity, without the deletes a transcript of a run of pkg_add -u -v
> might have shown why the packages didn't get updated. They should have,
> and in most cases they do.
>
Here's the pkg_add -uiv output that I saved while removing stuff
On 2023-12-29, Ax0n wrote:
> On Fri, Dec 29, 2023, 11:21 Theo de Raadt wrote:
>
>> Then your machine is not -current, not by a long shot.
>>
>> We moved to libc.so.98.0 on Dec 12.
>>
>> At least two rounds of new packages have shown up since then.
>>
>> I do believe there are circumstances where
On Fri, Dec 29, 2023, 11:21 Theo de Raadt wrote:
> Then your machine is not -current, not by a long shot.
>
> We moved to libc.so.98.0 on Dec 12.
>
> At least two rounds of new packages have shown up since then.
>
> I do believe there are circumstances where pkg_add fails to update
> library pack
Ax0n wrote:
> And yes, quite a lot of stuff referencing libc.so.97.1 in /usr/local - 223
> files in bin, 361 in lib, 0 in sbin.
Then your machine is not -current, not by a long shot.
We moved to libc.so.98.0 on Dec 12.
At least two rounds of new packages have shown up since then.
I do believ
On Thu, Dec 28, 2023, 11:00 Stuart Henderson
wrote:
Not sure how much core dumps will help, but if you can try running
the binaries with problems with LD_DEBUG set in the environment (to
anything) and capture output (e.g. using script(1) as it will likely be
copious) that might give clues.
I'll
Stuart Henderson wrote:
> On 2023-12-27, Ax0n wrote:
> > I had been running #1471 since December 5th without issue, and this week
> > upgraded to the latest snapshot (#1567) after which some apps such as
> > Firefox won't run. They display "msyscall a8000 error" followed by a
> > core dump. dme
On 2023-12-27, Ax0n wrote:
> I had been running #1471 since December 5th without issue, and this week
> upgraded to the latest snapshot (#1567) after which some apps such as
> Firefox won't run. They display "msyscall a8000 error" followed by a
> core dump. dmesg(1) shows a bogus syscall. I did e
b...@fea.st wrote:
> On Thu, Dec 28, 2023, at 00:41, Ax0n wrote:
> > I had been running #1471 since December 5th without issue, and this week
> > upgraded to the latest snapshot (#1567) after which some apps such as
> > Firefox won't run. They display "msyscall a8000 error" followed by a
> > core
On Thu, Dec 28, 2023, at 00:41, Ax0n wrote:
> I had been running #1471 since December 5th without issue, and this week
> upgraded to the latest snapshot (#1567) after which some apps such as
> Firefox won't run. They display "msyscall a8000 error" followed by a
> core dump. dmesg(1) shows a bogus
10 matches
Mail list logo
