On Tue, 27 Jun 2023 07:22:36 +0100
Stuart Henderson wrote:
> On 2023/06/26 07:10, Edward Ahlsen-Girard wrote:
> [...]
>
> pkg_check isn't meant to take a partial package name as argument, it
> checks all installed packages. Just run "pkg_check".
>
Running with no arguments doesn't return
On 2023/06/26 07:10, Edward Ahlsen-Girard wrote:
> ed@pav(~)$pkg_check keepassxc
pkg_check isn't meant to take a partial package name as argument, it
checks all installed packages. Just run "pkg_check".
Begin forwarded message:
Date: Mon, 26 Jun 2023 07:04:36 -0500
From: Edward Ahlsen-Girard
To: Solène Rapenne
Subject: Re: keepassxc in Jun 20 snap is sad
On Mon, 26 Jun 2023 09:19:54 +0200
Solène Rapenne wrote:
[...]
A fresh clean user receives the same error.
pkg_check surprised me
On 2023/06/23 10:01, Ashlen wrote:
> 4) `pkg_info -mz > file`, `pkg_delete -X`, `pkg_add -l file`.
if someone has a suspected problem with updates not working correctly
and does this, they will destroy any information that might have helped
debug it.
that said, this doesn't look like a problem
On Fri, 23 Jun 2023 10:01:48 -0600
Ashlen wrote:
> Same for me, I can't reproduce the issue either (I just upgraded).
> Edward, what are the contents of /etc/installurl for you? If you're
> using a CDN or a mirror with issues, that's probably your problem
> right there. My advice is the
Same for me, I can't reproduce the issue either (I just upgraded).
Edward, what are the contents of /etc/installurl for you? If you're
using a CDN or a mirror with issues, that's probably your problem right
there. My advice is the following, in this order:
1) `pkg_add -u` if you haven't already.
On Thu, 22 Jun 2023 14:48:15 +0200
Solene Rapenne wrote:
> Le Thu, 22 Jun 2023 05:53:55 -0500,
> Edward Ahlsen-Girard a écrit :
>
> [...]
> > > 1) Port-related mails should go to ports@, so I'm CC'ing ports@
> > > and dropping misc@. If it becomes clear it's an issue with the
> > > port
On 06/22/2023 7:48 AM CDT Solene Rapenne wrote: Le
Thu, 22 Jun 2023 05:53:55 -0500, Edward Ahlsen-Girard
a écrit :
On Wed, 21 Jun 2023 10:32:52 -0600 Ashlen wrote:
1) Port-related mails should go to ports@, so I'm CC'ing
ports@ and dropping misc@. If it becomes clear
Le Thu, 22 Jun 2023 05:53:55 -0500,
Edward Ahlsen-Girard a écrit :
> On Wed, 21 Jun 2023 10:32:52 -0600
> Ashlen wrote:
>
> > 1) Port-related mails should go to ports@, so I'm CC'ing ports@ and
> > dropping misc@. If it becomes clear it's an issue with the port
> > itself (but I don't think it
On Wed, 21 Jun 2023 10:32:52 -0600
Ashlen wrote:
> 1) Port-related mails should go to ports@, so I'm CC'ing ports@ and
> dropping misc@. If it becomes clear it's an issue with the port
> itself (but I don't think it is), we can CC the maintainer later.
>
> 2) Can you please open that core file
On Wed, 21 Jun 2023 10:32:52 -0600
Ashlen wrote:
> 1) Port-related mails should go to ports@, so I'm CC'ing ports@ and
> dropping misc@. If it becomes clear it's an issue with the port
> itself (but I don't think it is), we can CC the maintainer later.
>
> 2) Can you please open that core file
1) Port-related mails should go to ports@, so I'm CC'ing ports@ and
dropping misc@. If it becomes clear it's an issue with the port
itself (but I don't think it is), we can CC the maintainer later.
2) Can you please open that core file with gdb and provide the
backtrace? Should be as simple as:
12 matches
Mail list logo
