On 2021-02-23 19:30, Mark Millard via freebsd-stable wrote:
On 2021-Feb-23, at 18:08, Chris wrote:
On 2021-02-23 17:42, Mark Millard wrote:
(Warner is only CC'd here.)
Warner Losh imp at bsdimp.com wrote on
Wed Feb 24 01:04:13 UTC 2021 :
On Tue, Feb 23, 2021, 4:51 PM Chris wrote:
> Given
On 2021-Feb-23, at 18:08, Chris wrote:
> On 2021-02-23 17:42, Mark Millard wrote:
>> (Warner is only CC'd here.)
>> Warner Losh imp at bsdimp.com wrote on
>> Wed Feb 24 01:04:13 UTC 2021 :
>>> On Tue, Feb 23, 2021, 4:51 PM Chris wrote:
>>> > Given this is a pkg(8) error, I brought it up on
Ah didn't consider that this was an old enough ver of stable to cause this.
On Tue, Feb 23, 2021, 6:08 PM Chris wrote:
> On 2021-02-23 17:42, Mark Millard wrote:
> > (Warner is only CC'd here.)
> >
> > Warner Losh imp at bsdimp.com wrote on
> > Wed Feb 24 01:04:13 UTC 2021 :
> >
> >> On Tue,
On 2021-02-23 17:42, Mark Millard wrote:
(Warner is only CC'd here.)
Warner Losh imp at bsdimp.com wrote on
Wed Feb 24 01:04:13 UTC 2021 :
On Tue, Feb 23, 2021, 4:51 PM Chris wrote:
> Given this is a pkg(8) error, I brought it up on ports@
> but it was suggested I (also?) bring it up here
On 2021-02-23 17:07, Brian W. wrote:
12-stable is not what you're running if you got that error.
# uname -apKU
FreeBSD fbsd12dev 12.1-STABLE FreeBSD 12.1-STABLE r363918 GENERIC amd64
amd64 1201522 1201522
Looks pretty STABLE to me.
--Chris
Run freebsd-update with appropriate args to get to
(Warner is only CC'd here.)
Warner Losh imp at bsdimp.com wrote on
Wed Feb 24 01:04:13 UTC 2021 :
> On Tue, Feb 23, 2021, 4:51 PM Chris wrote:
>
> > Given this is a pkg(8) error, I brought it up on ports@
> > but it was suggested I (also?) bring it up here on stable@
> >
> > OK awhile back I
12-stable is not what you're running if you got that error. Run
freebsd-update with appropriate args to get to a later release is the
easiest option.
Brian
On Tue, Feb 23, 2021, 5:04 PM Warner Losh wrote:
> On Tue, Feb 23, 2021, 4:51 PM Chris wrote:
>
> > Given this is a pkg(8) error, I
On Tue, Feb 23, 2021, 4:51 PM Chris wrote:
> Given this is a pkg(8) error, I brought it up on ports@
> but it was suggested I (also?) bring it up here on stable@
>
> OK awhile back I installed a copy of 12 stable from the
> usb stick image. I tweaked it to my wishes then got called
> away and
Given this is a pkg(8) error, I brought it up on ports@
but it was suggested I (also?) bring it up here on stable@
OK awhile back I installed a copy of 12 stable from the
usb stick image. I tweaked it to my wishes then got called
away and haven't been able to get back to it until the other
day.
On 2021-Feb-23 11:30:58 -0600, Chris Anderson wrote:
>nope, it led a pretty boring life. that zfs filesystem was created on that
>server and has been on the same two mirrored disks for its lifetime.
Does the server have ECC RAM? Possibly it's a bitflip somewhere before
the data got to disk.
On 2021-02-23 3:33 pm, Mark Johnston wrote:
On Tue, Feb 23, 2021 at 02:36:04PM -0600, Dean E. Weimer via
freebsd-stable wrote:
I just built and installed FreeBSD 13.0 Beta 3 from source checked out
with last commit of 4b737a9c58cac69008f189cc44e7d1a81a0b601c after the
install I was installing a
On Tue, Feb 23, 2021 at 02:36:04PM -0600, Dean E. Weimer via freebsd-stable
wrote:
> I just built and installed FreeBSD 13.0 Beta 3 from source checked out
> with last commit of 4b737a9c58cac69008f189cc44e7d1a81a0b601c after the
> install I was installing a few ports, and perl5.32 failed to
I just built and installed FreeBSD 13.0 Beta 3 from source checked out
with last commit of 4b737a9c58cac69008f189cc44e7d1a81a0b601c after the
install I was installing a few ports, and perl5.32 failed to build
stating dtrace -h not available.
root@fbsd13-devel:/ # dtrace -h
dtrace: failed to
On 2021-02-22 9:34 pm, Dean E. Weimer wrote:
On 2021-02-22 8:55 pm, Dean E. Weimer via freebsd-stable wrote:
On 2021-02-22 5:52 pm, Warner Losh wrote:
What does this patch do for you?
diff --git a/stand/i386/loader/Makefile b/stand/i386/loader/Makefile
index ad95948ec50a..cbbe15bd1fc0 100644
The more I look at `make -dm` output, the less sense it makes. Your
patch is decidedly correct regardless of how this specific scenario is
playing out:
1.) As you noted, it's wrong to clean something that's built
elsewhere. You can reasonably expect `make clean all` to work pretty
much everywhere
I'm unsure of the mechanics as well. I do know that we shouldn't delete
stuff in OTHER directories, though. the btx stuff is trying to do a bit of
an end run around the link only with the installed stuff here and using
crt0.o as a library from the 'where it was built' directory which I think
On Tue, Feb 23, 2021 at 4:53 AM Andriy Gapon wrote:
> On 23/02/2021 05:25, Chris Anderson wrote:
> > so I can't ls -i the file since that triggers the no such file warning.
> if I run
> > zdb - on the inode of a directory which contains one of those
> missing files,
> > I can get the inode
Hi,
What I don't understand here is, why are these being considered
out-of-date? That seems like it is indicative of a larger problem that
we'd surely fall over elsewhere on if not for here, that the source
tree's timestamps are post-dated w.r.t. the objdir.
Thanks,
Kyle Evans
On Mon, Feb 22,
On Thu, 18 Feb 2021 at 15:29, Ed Maste wrote:
>
> The git-svn stable/12 mirror is currently stuck. It encountered an
> issue with the OpenSSL 1.1.1j import (e3a8c0df593b) and hasn't been
> able to make progress past it. It's under investigation and will
> hopefully be resolved soon.
This was
On 23/02/2021 05:25, Chris Anderson wrote:
> so I can't ls -i the file since that triggers the no such file warning. if I
> run
> zdb - on the inode of a directory which contains one of those missing
> files,
> I can get the inode of the file from that, but I don't get anything
>
20 matches
Mail list logo
