Re: -current amd64 packages not updated? Impatient or broken?

2021-01-07 Thread Mike Larkin
On Thu, Jan 07, 2021 at 05:44:05PM -0700, Theo de Raadt wrote: > Chris Cappuccio wrote: > > > Mihai Popescu [mih...@gmail.com] wrote: > > > I was in the same situation, impatient to have a 2021 snapshot. > > > > > > Warning: I am not sure you will not finish with a Frankenstein system. I > > >

Re: -current amd64 packages not updated? Impatient or broken?

2021-01-07 Thread Theo de Raadt
Chris Cappuccio wrote: > Mihai Popescu [mih...@gmail.com] wrote: > > I was in the same situation, impatient to have a 2021 snapshot. > > > > Warning: I am not sure you will not finish with a Frankenstein system. I am > > not so good with compiler-linker stuff. > > For those trying to use the

Re: -current amd64 packages not updated? Impatient or broken?

2021-01-07 Thread Chris Cappuccio
Mihai Popescu [mih...@gmail.com] wrote: > I was in the same situation, impatient to have a 2021 snapshot. > > Warning: I am not sure you will not finish with a Frankenstein system. I am > not so good with compiler-linker stuff. For those trying to use the latest snap and the latest ports, try

Re: -current amd64 packages not updated? Impatient or broken?

2021-01-07 Thread Mihai Popescu
I was in the same situation, impatient to have a 2021 snapshot. Dirty hint: the .hk mirror still has the base part from 2020! But try it as a last option, the folks there are not so bandwidth fortunate. After installing the base, please switch /etc/installurl to something more suitable as

Re: help needed with httpd.conf and rewrite directive

2021-01-07 Thread John McGuigan
Yeah, or that... I realized that after but didn't want to double post. I emailed Kevin off-list to mention that the "/" character isn't special so it doesn't need to be escaped so Edgar's example can be modified to: location match "^/sendy/l/([%w/]+)$" { request rewrite

Re: help needed with httpd.conf and rewrite directive

2021-01-07 Thread Christian Weisgerber
On 2021-01-07, John McGuigan wrote: > httpd's regex is based on Lua's, the following site will help you figure it > out: Or, you know, the patterns(7) man page. -- Christian "naddy" Weisgerber na...@mips.inka.de

Re: -current amd64 packages not updated? Impatient or broken?

2021-01-07 Thread Steve Williams
On 07/01/2021 1:30 p.m., Christian Weisgerber wrote: Steve Williams: I hesitate to send this because perhaps I'm just too impatient, but then again, perhaps not.  This is not critical/time sensitive. I just thought I'd check if there a problem with the current packages folder from the

Re: -current amd64 packages not updated? Impatient or broken?

2021-01-07 Thread Christian Weisgerber
Steve Williams: > I hesitate to send this because perhaps I'm just too impatient, but then > again, perhaps not.  This is not critical/time sensitive. > > I just thought I'd check if there a problem with the current packages folder > from the mirrors? No, the amd64 package builds have been

Re: -current amd64 packages not updated? Impatient or broken?

2021-01-07 Thread Amit Kulkarni
Thanks for the correction! amit On Thu, Jan 7, 2021 at 11:59 AM Patrick Wildt wrote: > > No, that's not correct. The libc++ 11 (*not* LLVM 11) has not yet been > committed. This issue is because of libunwind 11. With libc++ 11 we > have made a separate ports build first, to check the

Re: -current amd64 packages not updated? Impatient or broken?

2021-01-07 Thread Steve Williams
Impatient it is :D Thanks for the update! Cheers, Steve W. On 07/01/2021 10:56 a.m., Patrick Wildt wrote: I committed an update to libunwind which made a major bump necessary. Maybe I should have asked ports to run with the build first, so that base and packages would be aligned. Too late

Re: msdos partition is too small in arm64/miniroot68.img

2021-01-07 Thread adr
On Thu, Jan 07, 2021 at 01:01:53PM +, tech-lists wrote: > On Wed, Jan 06, 2021 at 09:01:19PM +, a...@sdf.org wrote: > > [...method...] > > thanks for that, I'll let you know how I get on. I think your > problem with spontaneous crashes might be down to swapfile, > sdcard is unsuitable

Re: -current amd64 packages not updated? Impatient or broken?

2021-01-07 Thread Patrick Wildt
Oh, and another correction: it's libc++ 10.0.1, we're not going 11 yet. Am Thu, Jan 07, 2021 at 06:59:52PM +0100 schrieb Patrick Wildt: > No, that's not correct. The libc++ 11 (*not* LLVM 11) has not yet been > committed. This issue is because of libunwind 11. With libc++ 11 we > have made a

Re: -current amd64 packages not updated? Impatient or broken?

2021-01-07 Thread Patrick Wildt
No, that's not correct. The libc++ 11 (*not* LLVM 11) has not yet been committed. This issue is because of libunwind 11. With libc++ 11 we have made a separate ports build first, to check the fallout. Once the fallout is mostly fixed, we'll do the switch to libc++ 11. Until then snapshots are

Re: msdos partition is too small in arm64/miniroot68.img

2021-01-07 Thread Theo de Raadt
tech-lists wrote: > On Thu, Jan 07, 2021 at 09:55:28AM -0700, Theo de Raadt wrote: > >tech-lists wrote: > > > >> On Wed, Jan 06, 2021 at 09:25:01AM -0700, Theo de Raadt wrote: > >> >The miniroot is 33MB because it contains many install firmwares, and > >> >it is 97% full. > >> > > >> >I suggest

Re: -current amd64 packages not updated? Impatient or broken?

2021-01-07 Thread Amit Kulkarni
Like naddy@ mentioned on ports@ they are trying to figure out the fallout from the switch to LLVM 11 as system compiler. This is why the packages are being delayed. Please wait a while till it is sorted out. thanks On Thu, Jan 7, 2021 at 10:56 AM Steve Williams wrote: > > Hi, > > I hesitate to

Re: -current amd64 packages not updated? Impatient or broken?

2021-01-07 Thread Patrick Wildt
I committed an update to libunwind which made a major bump necessary. Maybe I should have asked ports to run with the build first, so that base and packages would be aligned. Too late for that now. Time will fix it though. Am Thu, Jan 07, 2021 at 09:54:39AM -0700 schrieb Steve Williams: > Hi, >

Re: msdos partition is too small in arm64/miniroot68.img

2021-01-07 Thread tech-lists
On Thu, Jan 07, 2021 at 09:55:28AM -0700, Theo de Raadt wrote: tech-lists wrote: On Wed, Jan 06, 2021 at 09:25:01AM -0700, Theo de Raadt wrote: >The miniroot is 33MB because it contains many install firmwares, and >it is 97% full. > >I suggest you find another way of installing. > Is there a

Re: msdos partition is too small in arm64/miniroot68.img

2021-01-07 Thread Theo de Raadt
tech-lists wrote: > On Wed, Jan 06, 2021 at 09:25:01AM -0700, Theo de Raadt wrote: > >The miniroot is 33MB because it contains many install firmwares, and > >it is 97% full. > > > >I suggest you find another way of installing. > > > > Is there a technical (or some other reason I'm not seeing)

-current amd64 packages not updated? Impatient or broken?

2021-01-07 Thread Steve Williams
Hi, I hesitate to send this because perhaps I'm just too impatient, but then again, perhaps not.  This is not critical/time sensitive. I just thought I'd check if there a problem with the current packages folder from the mirrors? I am trying to update my development system (to resume work

Re: msdos partition is too small in arm64/miniroot68.img

2021-01-07 Thread Theo de Raadt
Christer Solskogen wrote: > On Wed, Jan 6, 2021 at 5:39 PM Theo de Raadt wrote: > > The miniroot is 33MB because it contains many install firmwares, and > it is 97% full. > > True, but the miniroot has space available to expand the msdos partition. The miniroot has two filesystems. a is

Re: msdos partition is too small in arm64/miniroot68.img

2021-01-07 Thread tech-lists
On Thu, Jan 07, 2021 at 02:20:54PM +, a...@sdf.org wrote: On Thu, Jan 07, 2021 at 01:01:53PM +, tech-lists wrote: On Wed, Jan 06, 2021 at 09:01:19PM +, a...@sdf.org wrote: [...method...] thanks for that, I'll let you know how I get on. I think your problem with spontaneous crashes

Re: Bug in pkgtools version parsing logic?

2021-01-07 Thread Jeremy O'Brien
On Wed, Jan 6, 2021, at 17:16, Jeremy O'Brien wrote: > Hi there, > > I'm looking through the pkgtools code to determine how the version > comparison logic works, and I came across this block of code at > /usr/libdata/perl5/OpenBSD/PackageName.pm:385: > > sub from_string > { > my

Re: msdos partition is too small in arm64/miniroot68.img

2021-01-07 Thread tech-lists
On Wed, Jan 06, 2021 at 09:01:19PM +, a...@sdf.org wrote: [...method...] thanks for that, I'll let you know how I get on. I think your problem with spontaneous crashes might be down to swapfile, sdcard is unsuitable for this. I've had good results with arm64/freebsd-current/swapfile on

Re: msdos partition is too small in arm64/miniroot68.img

2021-01-07 Thread tech-lists
On Wed, Jan 06, 2021 at 09:25:01AM -0700, Theo de Raadt wrote: The miniroot is 33MB because it contains many install firmwares, and it is 97% full. I suggest you find another way of installing. Is there a technical (or some other reason I'm not seeing) why miniroot68.fs has been made as

Re: npppd - problem with simultaneous sessions

2021-01-07 Thread radek
Hi, > It seems that only last person can use the tunnel. This reminds me > problems through NAT. True. Can it be caused by wrong PF rules? > Both sessions seem to be connected from A.B.C.D. Are the clients > behind a NAT? Yes, both client are behind the same router/NAT. I have a 66/i386 box