On Thu, May 31, 2018 at 09:04:25PM -0700, K. Macy wrote:
> This is where culling older bug reports comes in.
Well, even with doing that, the sheer number really doesn't help the
S/N that much. It may make someone a bit neurotic like me feel a bit
better, but that's all.
> However, when I've trie
On Fri, Jun 15, 2018 at 11:14:40AM +0200, Mikaël Urankar wrote:
> Last time I tried (2 weeks ago) qemu-ppc64-static was broken, not sure the
> situation has evolved since that.
I've been told by more than one person that it works, but the 2? 3? times
I've tried it it just hung.
I have real hardwa
On Sun, Jul 15, 2018 at 01:09:41PM -0600, Warner Losh wrote:
> I'm not saying that he has a lock. I'm saying he's are domain expert
> and many mistakes can be avoided by talking to him.
fwiw, substantially all the work done since at least 2013 is from kargl.
(I am eliding the licensing, Makefile,
On Tue, Jul 31, 2018 at 01:13:31PM +0200, Miroslav Lachman wrote:
> As Guido Falsi already said it is not guaranteed that you will not
> have ports with some X libs, because some ports does not have option
> to disable X11 dependencies.
IMHO those ports have bugs.
mcl
On Sat, Jan 25, 2020 at 03:59:06PM -0800, Cy Schubert wrote:
> A rule of thumb would probably be, have ~ 2 GB RAM for every core or
> thread when doing large parallel builds.
This is a rule of thumb that I have used for quite some time.
Perhaps less is necessary for certain tasks, but if you want
On Sun, May 03, 2020 at 10:04:04AM -0600, Ian Lepore wrote:
> That LOR site hasn't been updated in years. Many many years.
If someone wants to help me set up a page on the wiki, let me know.
(I have too much on my plate to do it myself.)
mcl
___
freebs
On Wed, Jul 15, 2020 at 11:56:43AM +0200, Willem Jan Withagen wrote:
> A bit of a pain, since pkg does not do it
because ...
> you need to manually fetch the tar from Broadcom first.
Finally:
> [pkg] also does not tell you why
Just ask it:
portsjail% cd sysutils/storcli
portsjail% make -V
The latest build of amd64-CURRENT ports has just completed:
http://beefy18.nyi.freebsd.org/build.html?mastername=head-amd64-default&build=p546132_s364744
The number of build failures is now 740. This is an slight drop from
the initial post-clang11 commit of 830. This is due to diligent work
I forgot to include the following statistic:
repojail% grep duplicate_symbol regresslogs.out.wanted | wc -l
613
mcl
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any m
On Wed, Sep 02, 2020 at 08:30:28AM +, Thomas Mueller wrote:
> NetBSD plans to switch from cvs to Mercurial.
So ... from square wheels, to triangular ones???
mcl
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/
On Wed, Sep 02, 2020 at 08:01:17AM +0200, Kurt Jaeger wrote:
> A short intro on git for svn users:
> https://hackmd.io/ML5TSl8mQ5-27B5eqDf7YA?view
For people like me that will not click on random URLs ...
... just feed "svn to git cheat-sheet" to your favorite search engine.
Disclaimer: my initi
On Thu, Sep 03, 2020 at 11:40:17AM -0700, Rodney W. Grimes wrote:
> To the contrary 5 years ago the project on @developers basically
> ran off one of the committers over the very idea of using git
> for the project. It was shortly after I returned, so I find it
> very ironic that now its all "git
On Sun, Sep 06, 2020 at 03:05:49PM -0400, Yoshihiro Ota wrote:
> Do you own pkg sites?
Only portmgr@ does that. So this matter can only be resolved by a
discussion between portmgr@ and clusteradm@.
mcl
___
freebsd-current@freebsd.org mailing list
https
On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote:
> We hope to have it finished in time for 13.0.
I also feel that it should be more a "requirement".
I don't see the rush in getting 13.0 out the door. There is a lot to
get working (especially in ports-land).
mcl
_
Folks, please change the Subject: line here. This has now become a
thread of only tangiental interest to a typical FreeBSD developer
(in this case, typified by me :-) )
mcl
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/l
On Wed, Jan 06, 2021 at 11:24:22AM +, tech-lists wrote:
> >Moreover mergemaster is still officially documented and recommend as
> >only right method in FreeBSD handbook. See
> >https://www.freebsd.org/doc/handbook/makeworld.html.
> >World is moving, we may have new tools but each deprecation sh
On Sun, Jan 24, 2021 at 07:45:08PM +0900, Yasuhiro Kimura wrote:
> By the way, when -CURRENT was bumped from 12 to 13, there were some
> ports that failed to be built on 13-CURRENT simply because they don't
> expect there is version 13.x of FreeBSD. And probably such ports fails
> to be built on 14
On Thu, Jan 28, 2021 at 02:20:40PM -0800, Steve Kargl wrote:
> This is all likely academic as I just saw John Baldwin's email
> that stated i386 support is being dropped in FreeBSD-current.
s/dropped/downgraded/
The only difference seems to be that security upgrades that _only_
affect i386 will n
On Mon, May 31, 2021 at 05:25:03AM +, Poul-Henning Kamp wrote:
> They are enthusiastic FreeBSD users and potential future committers,
> and should be treated as such!
The same goes for non-committers and phabricator, IMHO.
mcl
On Mon, Jun 07, 2021 at 01:58:01PM -0600, Ian Lepore wrote:
> Sometimes it's a real interesting exercise to figure out where a
> file on your runtime system comes from in the source world.
A tangential problem I trip over is "what is on this SD card?"
It generally takes me 5-10 minutes to remembe
Is this the same as:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256947
?
mcl
Anyone objecting to this, be careful, I might ship a pile of such
things to you from the depths of the closets :-)
mcl
101 - 122 of 122 matches
Mail list logo
