Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

[Warner Losh]

I have this in my tree already...

Warner

On Mon, Jul 9, 2018, 10:28 AM Allan Jude  wrote:

> I will look at updating the rootgen.sh script this evening, to support
> creating more flexible ESP partitions, so we can drop the loader.efi
> into an msdosfs directly.
>
> On 07/08/2018 15:31, Ian Lepore wrote:
> > On Sun, 2018-07-08 at 21:08 +0200, Oliver Pinter wrote:
> >> Hi!
> >>
> >> Have you or Warner any update on this code?
> >>
> >> On Thursday, April 12, 2018, Eric McCorkle 
> >> wrote:
> >>
> >
> > Are you aware of https://reviews.freebsd.org/D15743 ?
> >
> > That's my changes to add geli support to loader(8) in an architecture-
> > agnostic way, so that "it just works" for all platforms and flavors of
> > loader. It has been succesfully tested on armv6/7 (ubldr) and on x86
> > using qemu.  The x86 tests cover ufs and zfs, legacy bios and uefi. The
> > only variations that aren't tested yet are the uefi flavors, because
> > the current rootgen.sh script for assembling test images is still using
> > boot1.efi and I don't know enough about efi myself to update the script
> > to make it assemble images the new way Warner envisions.
> >
> > -- Ian
> >
> >>>
> >>> I'm in the middle of moving to a new apartment right now.  It's
> >>> going to
> >>> be a bit before I can get to this.
> >>>
> >>> On 04/11/2018 20:31, Warner Losh wrote:
> 
>  OK. I've pushed in the main part of it. The additional work I
>  have
>  shouldn't affect any of this stuff.  I was going to look at what
>  part(s)
>  of your open reviewed needed to be redone tomorrow and send you
>  feedback, but if you wanted to get a start before then, I'm happy
>  to
>  answer questions. All the rest of my work is going to be
>  selecting the
>  root partition when we're told to us a specific partition, so
>  will be
>  very constrained.
> 
>  Warner
> 
>  On Wed, Apr 11, 2018 at 6:02 PM, Eric McCorkle   net
>  > wrote:
> 
>   I think the thing to do at this point is to wait for the
>  current
> >>> work on
> 
>   loader.efi to land, then adapt my patches to apply against
>  that work.
> 
>   On 04/11/2018 15:06, Warner Losh wrote:
>   > Still reviewing the code. I'm worried it's too i386
>  specific and it
>   > conflicts with some work I'm doing. I'll have a list of
>  actionable
>   > critiques this week.
>   >
>   > Warner
>   >
>   > On Wed, Apr 11, 2018 at 1:03 PM, Oliver Pinter
>   >    
>      >>
>   > wrote:
>   >
>   > Hi!
>   >
>   > Is there any update regarding the rebase or the
>  inclusion to
> >>> base
> 
>   > system?
>   > On 3/28/18, Eric McCorkle    >>> e...@metricspace.net>
> 
>   >   et>>>
> >>> wrote:
> 
>   > > I'll do another rebase from head just to be sure
>   > >
>   > > On March 28, 2018 3:23:23 PM EDT, Warner Losh <
> >>> i...@bsdimp.com 
> 
>   > >> wrote:
>   > >>It's on my list for nexr, finally. I have an
>  alternate patch
> >>> for
> 
>   > >>loader.efi
>   > >>from ESP, but i don't think it will affect the GELI
>  stuff. I
> >>> have some
> 
>   > >>time
>   > >>slotted for integration issues though.
>   > >>
>   > >>I am quite mindful of the freeze dates I  have
>  some uefi
> >>> boot
> 
>   > >>loader
>   > >>protocol changes that I need to get in.
>   > >>
>   > >>Warner
>   > >>
>   > >>On Feb 21, 2018 11:18 PM, "Tommi Pernila" <
> >>> tommi.pern...@iki.fi 
> 
>   >   fi>>>
> >>> wrote:
> 
>   > >>
>   > >>> Awesome, thanks for the update and the work that
>  you have
> >>> done!
> 
>   > >>>
>   > >>> Now we just need some more reviewers eyes on the
>  code :)
>   > >>>
>   > >>> Br,
>   > >>>
>   > >>> Tommi
>   > >>>
>   > >>> On Thu, 22 Feb 2018 at 2.03, Eric McCorkle <
> >>> e...@metricspace.net 
> 
>   >   et>>>
>   > >>wrote:
>   > >>>
>   >  FYI, I just IFC'ed everything, and the current
>  

Re: How to add su to /rescue ?

[Guy Helmer]

> On Jul 9, 2018, at 6:54 AM, Julian H. Stacey  wrote:
> 
> Hi current@
> I want to add su to /rescue, but got stuck on pam.
> Old unix su didn't suffer from pam.
> There's no #define in su to turn off pam.
> Man src.conf says WITHOUT_PAM is deprecated & does nothing.
> 
> Can someone please offer a solution ?
> Or better to include a simple BSD su pre pam ?
> I would happily develop a patch for that.


Hi,

Aside from not being able to use pam from a static executable, please don’t try 
to make the crunched hard-linked executable in /rescue setuid-root (su is 
useless without it). That would mean anyone running /rescue/sh gets a root 
shell :-)

Conceptually, a separate crunchgen binary could be made for setuid-root 
purposes, but having a setuid-root binary in /rescue (outside of the normal 
hierarchy) makes me nervous.

Regards,
Guy 

> 
> Notes to explain the need, & patches from my
> http://berklix.com/~jhs/src/bsd/fixes/freebsd/src/gen/rescue/
> -
> 
> Patch[es] below to solve this emailed scenario:
>> Please on prison-host cp /lib/libc.so.7 /tank/ezjail/my-domain/lib/libc.so.7
>> I am logged in on jail-host, but only as normal-user, not root, so I cannot 
>> run
>>  /rescue/cp /usr/obj/usr/src/lib/libc/libc.so.7 /lib/libc.so.7
>> 
>> a my make installworld on jail-host.my-domain previously failed with
>>  ===> lib/libc (install)
>>  install -C -o root -g wheel -m 444   libc.a /usr/lib
>>  install -C -o root -g wheel -m 444   libc_p.a /usr/lib
>>  install -s -o root -g wheel -m 444   -fschg -S  libc.so.7 /lib
>>  install: /lib/libc.so.7: chflags: Operation not permitted
>>  *** Error code 71
>> (might or not be an artifact of being in a jail)
>> 
>> unfortunately I had run the command as
>>  xs make installworld
>> (xs is my own little root wrapper)
>> so when it exited, I was just normal-user not root, & I had forgotten to
>> open another xterm & leave it logged in as root,
>> & I found no /rescue/su
> 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

[Allan Jude]

I will look at updating the rootgen.sh script this evening, to support 
creating more flexible ESP partitions, so we can drop the loader.efi 
into an msdosfs directly.


On 07/08/2018 15:31, Ian Lepore wrote:

On Sun, 2018-07-08 at 21:08 +0200, Oliver Pinter wrote:

Hi!

Have you or Warner any update on this code?

On Thursday, April 12, 2018, Eric McCorkle 
wrote:



Are you aware of https://reviews.freebsd.org/D15743 ?

That's my changes to add geli support to loader(8) in an architecture-
agnostic way, so that "it just works" for all platforms and flavors of
loader. It has been succesfully tested on armv6/7 (ubldr) and on x86
using qemu.  The x86 tests cover ufs and zfs, legacy bios and uefi. The
only variations that aren't tested yet are the uefi flavors, because
the current rootgen.sh script for assembling test images is still using
boot1.efi and I don't know enough about efi myself to update the script
to make it assemble images the new way Warner envisions.

-- Ian



I'm in the middle of moving to a new apartment right now.  It's
going to
be a bit before I can get to this.

On 04/11/2018 20:31, Warner Losh wrote:


OK. I've pushed in the main part of it. The additional work I
have
shouldn't affect any of this stuff.  I was going to look at what
part(s)
of your open reviewed needed to be redone tomorrow and send you
feedback, but if you wanted to get a start before then, I'm happy
to
answer questions. All the rest of my work is going to be
selecting the
root partition when we're told to us a specific partition, so
will be
very constrained.

Warner

On Wed, Apr 11, 2018 at 6:02 PM, Eric McCorkle mailto:e...@metricspace.net>> wrote:

 I think the thing to do at this point is to wait for the
current

work on


 loader.efi to land, then adapt my patches to apply against
that work.

 On 04/11/2018 15:06, Warner Losh wrote:
 > Still reviewing the code. I'm worried it's too i386
specific and it
 > conflicts with some work I'm doing. I'll have a list of
actionable
 > critiques this week.
 >
 > Warner
 >
 > On Wed, Apr 11, 2018 at 1:03 PM, Oliver Pinter
 > mailto:oliver.pin...@hardenedbsd.org>
 >>
 > wrote:
 >
 > Hi!
 >
 > Is there any update regarding the rebase or the
inclusion to

base


 > system?
 > On 3/28/18, Eric McCorkle 
e...@metricspace.net>


 > >>

wrote:


 > > I'll do another rebase from head just to be sure
 > >
 > > On March 28, 2018 3:23:23 PM EDT, Warner Losh <

i...@bsdimp.com 


 > >> wrote:
 > >>It's on my list for nexr, finally. I have an
alternate patch

for


 > >>loader.efi
 > >>from ESP, but i don't think it will affect the GELI
stuff. I

have some


 > >>time
 > >>slotted for integration issues though.
 > >>
 > >>I am quite mindful of the freeze dates I  have
some uefi

boot


 > >>loader
 > >>protocol changes that I need to get in.
 > >>
 > >>Warner
 > >>
 > >>On Feb 21, 2018 11:18 PM, "Tommi Pernila" <

tommi.pern...@iki.fi 


 > >>

wrote:


 > >>
 > >>> Awesome, thanks for the update and the work that
you have

done!


 > >>>
 > >>> Now we just need some more reviewers eyes on the
code :)
 > >>>
 > >>> Br,
 > >>>
 > >>> Tommi
 > >>>
 > >>> On Thu, 22 Feb 2018 at 2.03, Eric McCorkle <

e...@metricspace.net 


 > >>
 > >>wrote:
 > >>>
 >  FYI, I just IFC'ed everything, and the current
patches
 are still
 > >>fine.
 > 
 >  Also, the full GELI + standalone loader has been
deployed
 on one of
 > >>my
 >  laptops for some time now.
 > 
 >  On 02/21/2018 18:15, Eric McCorkle wrote:
 >  > The GELI work could be merged at this point,
though it
 won't be
 > >>usable
 >  > without an additional patch to enable loader-
only
 operation.  The
 >  > patches are currently up for review:
 >  >
 >  > This is the order in which they'd need to be
merged:
 >  >
 >  >
 >  > https://reviews.freebsd.org/D12732
 
 > >
 >  >
 >  > This one changes the efipart device.  Toomas
Soome
 identified
 > some
 > 

Re: sys/Makefile .if defined(MODULES_WITH_WORLD)

[Ian Lepore]

On Mon, 2018-07-09 at 11:50 +0200, Julian H. Stacey wrote:
> Hi current@
> src/sys/dev/amdsbwd/amdsbwd.c broke src/sys/modules
> 
> Is it immediately intuitive & well known to developers working in
> sys/dev
> to enable MODULES_WITH_WORLD before a test make all before a commit ?
> 
> Or what should we do to increase the liklehood of commiters catching
> modules/ errors before a commit ?
> 
> With src/
>   .ctm_status src-cur 13573
>   .svn_revision 335362
> sys/Makefile has
>   .if defined(MODULES_WITH_WORLD)
>   SUBDIR+=modules
> & nothing from cd /usr/src; find . -name \*src.conf\*
> & no default /etc/src.conf with no
>   MODULES_WITH_WORLD=YES
> so make all does not build /sys/modules/ 
> so this not seen from /sys/modules/
> ===> amdsbwd (all)
> cc  -O2 -pipe -DBERKLIX=YES  -fno-strict-aliasing -Werror -D_KERNEL
> -DKLD_MODULE -nostdinc   -I. -I/data/release/s1/usr/src/sys
> -I/data/release/s1/usr/src/sys/contrib/ck/include -fno-common  -fno-
> omit-frame-pointer -mno-omit-leaf-frame-pointer   -MD  -
> MF.depend.amdsbwd.o -MTamdsbwd.o -mcmodel=kernel -mno-red-zone -mno-
> mmx -mno-sse -msoft-float  -fno-asynchronous-unwind-tables
> -ffreestanding -fwrapv -fstack-protector -Wall -Wredundant-decls
> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-
> arith -Wcast-qual -Wundef -Wno-pointer-sign
> -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs
> -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-
> tautological-compare -Wno-error-empty-body -Wno-error-parentheses-
> equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-
> error-shift-negative-value -Wno-address-of-packed-member  -mno-aes
> -mno-avx  -std=iso9899:1999 -c
> /data/release/s1/usr/src/sys/dev/amdsbwd/amdsbwd.c -o amdsbwd.o
> /data/release/s1/usr/src/sys/dev/amdsbwd/amdsbwd.c:52:10: fatal
> error: 
>   'opt_amdsbwd.h' file not found
> #include "opt_amdsbwd.h"
> 
> 
> PS With 
>   .ctm_status src-cur 13601
>   .svn_revision   336117
> nothing from
>   find . -name opt_amdsbwd.h
> but this has
>   src/sys/dev/amdsbwd/amdsbwd.c
>   #include "opt_amdsbwd.h"
> I haven't yet upgraded my src/ yet to see if it still fails.
> 
> Cheers,
> Julian

Should be fixed in r336134.

-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: New conflict between the FreeBSD-libnv-development and FreeBSD-runtime-development packages

[Kyle Evans]

On Mon, Jul 9, 2018 at 4:58 AM, Tobias Kortkamp  wrote:
> Hi,
>
> there's a new conflict between the FreeBSD-{libnv,runtime}-development
> base packages.  This was for r336096 but the problem must have been
> introduced after r335966 as the packages from that revision were
> fine.
>
> Checking integrity...  done (1 conflicting)
>   - FreeBSD-libnv-development-12.0.s20180708222113 [base] conflicts
>   with FreeBSD-runtime-development-12.0.s20180708222113 [installed]
>   on /usr/include/sys/cnv.h
>

Hi,

Indeed- there's a patch in flight that will alleviate this that will
hopefully land later today.

Thanks,

Kyle Evans
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

How to add su to /rescue ?

[Julian H. Stacey]

Hi current@
I want to add su to /rescue, but got stuck on pam.
Old unix su didn't suffer from pam.
There's no #define in su to turn off pam.
Man src.conf says WITHOUT_PAM is deprecated & does nothing.

Can someone please offer a solution ?
Or better to include a simple BSD su pre pam ?
I would happily develop a patch for that.

Notes to explain the need, & patches from my
http://berklix.com/~jhs/src/bsd/fixes/freebsd/src/gen/rescue/
-

Patch[es] below to solve this emailed scenario:
> Please on prison-host cp /lib/libc.so.7 /tank/ezjail/my-domain/lib/libc.so.7
> I am logged in on jail-host, but only as normal-user, not root, so I cannot 
> run
>   /rescue/cp /usr/obj/usr/src/lib/libc/libc.so.7 /lib/libc.so.7
> 
> a my make installworld on jail-host.my-domain previously failed with
>   ===> lib/libc (install)
>   install -C -o root -g wheel -m 444   libc.a /usr/lib
>   install -C -o root -g wheel -m 444   libc_p.a /usr/lib
>   install -s -o root -g wheel -m 444   -fschg -S  libc.so.7 /lib
>   install: /lib/libc.so.7: chflags: Operation not permitted
>   *** Error code 71
> (might or not be an artifact of being in a jail)
> 
> unfortunately I had run the command as
>   xs make installworld
> (xs is my own little root wrapper)
> so when it exited, I was just normal-user not root, & I had forgotten to
> open another xterm & leave it logged in as root,
> & I found no /rescue/su

*** 12.0-CURRENT/usr/src/rescue/rescue/Makefile.origTue Jun 19 14:43:47 2018
--- new-generic/usr/src/rescue/rescue/Makefile  Mon Jul  9 12:21:47 2018
***
*** 188,193 
--- 188,195 
  CRUNCH_PROGS_usr.bin+= less
  CRUNCH_ALIAS_less= more
  
+ CRUNCH_PROGS_usr.bin+= su
+ 
  CRUNCH_PROGS_usr.bin+= xz
  CRUNCH_ALIAS_xz= unxz lzma unlzma xzcat lzcat
  
-
Patch above fails with:
  cc -O2 -pipe -DBERKLIX=YES   -std=gnu99-Qunused-arguments-static -o 
reue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo 
echo. ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo 
mv. pkill.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh.lo sleep.lo 
st.lo sync.lo test.lo csh.lo camcontrol.lo clri.lo devfs.lo dmesg.lo dump.lo 
dums.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo 
gbde.lo om.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo 
kldunload.lo ldcoig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo 
mount_cd9660.lo mount_msdos.lo mount_nfs.lo mount_nullfs.lo mount_udf.lo 
mount_unionfs.lo newfs.lo newfssdos.lo nos-tun.lo ping.lo reboot.lo restore.lo 
rcorder.lo route.lo savecore.lshutdown.lo spppcontrol.lo swapon.lo sysctl.lo 
tunefs.lo umount.lo ccdconfig.lping6.lo rtsol.lo ipf.lo routed.lo rtquery.lo 
zfs.lo zpool.lo bsdlabel.lo fdislo dhclient.lo head.lo mt.lo sed.lo tail.lo 
tee.lo !
 gzip.lo bzip2.lo less.lo suo xz.lo zstd.lo tar.lo nc.lo vi.lo id.lo 
iscsictl.lo zdb.lo chroot.lo chown.loscsid.lo 
/data/release/s1/usr/obj/data/release/s1/usr/src/amd64.amd64/rescue/rcue/../librescue/exec.o
 
/data/release/s1/usr/obj/data/release/s1/usr/src/amd64md64/rescue/rescue/../librescue/getusershell.o
 
/data/release/s1/usr/obj/data/rease/s1/usr/src/amd64.amd64/rescue/rescue/../librescue/login_class.o
 
/data/relse/s1/usr/obj/data/release/s1/usr/src/amd64.amd64/rescue/rescue/../librescue/pen.o
 
/data/release/s1/usr/obj/data/release/s1/usr/src/amd64.amd64/rescue/rescu../librescue/rcmdsh.o
 
/data/release/s1/usr/obj/data/release/s1/usr/src/amd64.a64/rescue/rescue/../librescue/sysctl.o
 
/data/release/s1/usr/obj/data/release/susr/src/amd64.amd64/rescue/rescue/../librescue/system.o
 -lcrypt -ledit -ljail kvm -lelf -ll -ltermcapw -lutil -lxo -l80211 -lalias 
-lcam -lncursesw -ldevsta-lipsec -llzma -lavl -lzpool -lzfs_core -lzfs -lnvpair 
-lpthread -luutil -lume-lgeom -lbsdxml -lkiconv !
 -lmt -lsbuf -lufs -lz -lbz2 -lprivatezstd -larchive -rypto -lmd -lm
  /usr/bin/ld: error: undefined symbol: pam_start
  >>> referenced by su.lo:(_$$hide$$ su.lo main)
  
  /usr/bin/ld: error: undefined symbol: pam_set_item
  >>> referenced by su.lo:(_$$hide$$ su.lo main)

Patch below does not solve problem above
*** 12.0-CURRENT/usr/src/rescue/librescue/Makefile.orig Mon Jul  9 13:02:43 2018
--- new-generic/usr/src/rescue/librescue/Makefile   Mon Jul  9 13:03:59 2018
***
*** 16,21 
--- 16,22 
  .PATH: ${SRCTOP}/lib/libc/gen \
 ${SRCTOP}/lib/libc/net \
 ${SRCTOP}/lib/libc/stdlib \
+${SRCTOP}/lib/libpam/libpam \
 ${SRCTOP}/lib/libutil 
  
  LIB=  rescue
---
changing libpam/libpam to libpam also fails.
---

Cheers,
Julian
-- 
Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich
 Brexit Referendum stole 3.7 million votes inc. from 700,000 British in EU.
 UK Goverment lies it's democratic in Article 50 paragraph 3 of letter to EU.
 http://berklix.eu/queen/  https://www.peoples-vote.uk   200,000 @ 9 Jul 2018

sys/Makefile .if defined(MODULES_WITH_WORLD)

[Julian H. Stacey]

Hi current@
src/sys/dev/amdsbwd/amdsbwd.c broke src/sys/modules

Is it immediately intuitive & well known to developers working in sys/dev
to enable MODULES_WITH_WORLD before a test make all before a commit ?

Or what should we do to increase the liklehood of commiters catching
modules/ errors before a commit ?

With src/
.ctm_status src-cur 13573
.svn_revision 335362
sys/Makefile has
.if defined(MODULES_WITH_WORLD)
SUBDIR+=modules
& nothing from cd /usr/src; find . -name \*src.conf\*
& no default /etc/src.conf with no
MODULES_WITH_WORLD=YES
so make all does not build /sys/modules/ 
so this not seen from /sys/modules/
===> amdsbwd (all)
cc  -O2 -pipe -DBERKLIX=YES  -fno-strict-aliasing -Werror -D_KERNEL 
-DKLD_MODULE -nostdinc   -I. -I/data/release/s1/usr/src/sys 
-I/data/release/s1/usr/src/sys/contrib/ck/include -fno-common  
-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer   -MD  
-MF.depend.amdsbwd.o -MTamdsbwd.o -mcmodel=kernel -mno-red-zone -mno-mmx 
-mno-sse -msoft-float  -fno-asynchronous-unwind-tables -ffreestanding -fwrapv 
-fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef -Wno-pointer-sign 
-D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs 
-fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare 
-Wno-error-empty-body -Wno-error-parentheses-equality 
-Wno-error-unused-function -Wno-error-pointer-sign 
-Wno-error-shift-negative-value -Wno-address-of-packed-member  -mno-aes 
-mno-avx  -std=iso9899:1999 -c 
/data/release/s1/usr/src/sys/dev/amdsbwd/amdsbwd.c -o amdsbwd.o
/data/release/s1/usr/src/sys/dev/amdsbwd/amdsbwd.c:52:10: fatal error: 
  'opt_amdsbwd.h' file not found
#include "opt_amdsbwd.h"


PS With 
.ctm_status src-cur 13601
.svn_revision   336117
nothing from
find . -name opt_amdsbwd.h
but this has
src/sys/dev/amdsbwd/amdsbwd.c
#include "opt_amdsbwd.h"
I haven't yet upgraded my src/ yet to see if it still fails.

Cheers,
Julian
-- 
Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich
 Brexit Referendum stole 3.7 million votes inc. from 700,000 British in EU.
 UK Goverment lies it's democratic in Article 50 paragraph 3 of letter to EU.
 http://berklix.eu/queen/  https://www.peoples-vote.uk   193,000 @ 8 Jul 2018
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

New conflict between the FreeBSD-libnv-development and FreeBSD-runtime-development packages

[Tobias Kortkamp]

Hi,

there's a new conflict between the FreeBSD-{libnv,runtime}-development
base packages.  This was for r336096 but the problem must have been
introduced after r335966 as the packages from that revision were
fine.

Checking integrity...  done (1 conflicting)
  - FreeBSD-libnv-development-12.0.s20180708222113 [base] conflicts
  with FreeBSD-runtime-development-12.0.s20180708222113 [installed]
  on /usr/include/sys/cnv.h

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"