Re: pkg: Cannot open /dev/null:No such file or directory

2019-06-03 Thread Baptiste Daroussin
On Tue, Jun 04, 2019 at 07:32:16AM +0200, O. Hartmann wrote:
> Hello List,
> 
> lately I ran into a serious problem installing packages in a nanoBSD
> environment, in which the package repository server is "remotely" on site. The
> issue as documented below occurs on both 12-STABLE r348529 and CURRENT r348600
> and must have been introduced shortly, since the last known good installation
> with the environment of ours was on 21st May 2019.
> 
> As far as I know,, the package installation is performed via "chroot'ed"
> environment and somehow /dev/null is out of a sudden not accessible anymore
> while pkg tries to delegate some output to /dev/null.
> 
> What happened here?
> 
> Kind regards and thanks in advance,
> 
> oh
> 
> [...]
> All repositories are up to date.
> The following 10 package(s) will be affected (of 0 checked):
> 
> New packages to be INSTALLED:
> python3: 3_3 [zeit4]
> sudo: 1.8.27_1 [zeit4]
> devcpu-data: 1.22 [zeit4]
> python36: 3.6.8_2 [zeit4]
> readline: 8.0.0 [zeit4]
> indexinfo: 0.3.1 [zeit4]
> libffi: 3.2.1_3 [zeit4]
> gettext-runtime: 0.19.8.1_2 [zeit4]
> openldap-sasl-client: 2.4.47 [zeit4]
> cyrus-sasl: 2.1.27 [zeit4]
> 
> Number of packages to be installed: 10
> 
What is new is that pkg is using /dev/null as input when running script? this is
new since pkg 1.11 . Somehow this does not seems to be avaalaible in your
environement.

Best regards,
Bapt


signature.asc
Description: PGP signature


pkg: Cannot open /dev/null:No such file or directory

2019-06-03 Thread O. Hartmann
Hello List,

lately I ran into a serious problem installing packages in a nanoBSD
environment, in which the package repository server is "remotely" on site. The
issue as documented below occurs on both 12-STABLE r348529 and CURRENT r348600
and must have been introduced shortly, since the last known good installation
with the environment of ours was on 21st May 2019.

As far as I know,, the package installation is performed via "chroot'ed"
environment and somehow /dev/null is out of a sudden not accessible anymore
while pkg tries to delegate some output to /dev/null.

What happened here?

Kind regards and thanks in advance,

oh

[...]
All repositories are up to date.
The following 10 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
python3: 3_3 [zeit4]
sudo: 1.8.27_1 [zeit4]
devcpu-data: 1.22 [zeit4]
python36: 3.6.8_2 [zeit4]
readline: 8.0.0 [zeit4]
indexinfo: 0.3.1 [zeit4]
libffi: 3.2.1_3 [zeit4]
gettext-runtime: 0.19.8.1_2 [zeit4]
openldap-sasl-client: 2.4.47 [zeit4]
cyrus-sasl: 2.1.27 [zeit4]

Number of packages to be installed: 10

The process will require 129 MiB more space.
20 MiB to be downloaded.
[1/10] Fetching python3-3_3.txz: . done
[2/10] Fetching sudo-1.8.27_1.txz: .. done
[3/10] Fetching devcpu-data-1.22.txz: .. done
[4/10] Fetching python36-3.6.8_2.txz: .. done
[5/10] Fetching readline-8.0.0.txz: .. done
[6/10] Fetching indexinfo-0.3.1.txz: . done
[7/10] Fetching libffi-3.2.1_3.txz: . done
[8/10] Fetching gettext-runtime-0.19.8.1_2.txz: .. done
[9/10] Fetching openldap-sasl-client-2.4.47.txz: .. done
[10/10] Fetching cyrus-sasl-2.1.27.txz: .. done
Checking integrity... done (0 conflicting)
[1/10] Installing indexinfo-0.3.1...
[1/10] Extracting indexinfo-0.3.1:  done
[2/10] Installing readline-8.0.0...
[2/10] Extracting readline-8.0.0: .. done
pkg: Cannot open /dev/null:No such file or directory
[3/10] Installing libffi-3.2.1_3...
[3/10] Extracting libffi-3.2.1_3: .. done
pkg: Cannot open /dev/null:No such file or directory
[4/10] Installing gettext-runtime-0.19.8.1_2...
[4/10] Extracting gettext-runtime-0.19.8.1_2: .. done
pkg: Cannot open /dev/null:No such file or directory
[5/10] Installing cyrus-sasl-2.1.27...
pkg: Cannot open /dev/null:No such file or directory
___
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: UEFI boot broken in 13?

2019-06-03 Thread Johannes Lundberg


On 6/3/19 7:25 PM, Rodney W. Grimes wrote:
>> Hi
>>
>> I'm using poudriere-image to create usb memstick images. The images are
>> identical except OS version. They are tested on a laptop with 13-CURRENT
>> installed as only OS, having UEFI boot and root on zfs.
>>
>> 12-STABLE memstick boots fine with in UEFI mode.
> Does it actually boot via a UEFI, or did UEFI fall back to CSM
> and do a legacy boot?
>
> What does "sysctl machdep.bootmethod" say?
> machdep.bootmethod: BIOS

It says UEFI (it is also easy to see the difference between legacy and
uefi boot on the font / font size used so I didn't doubt this).

>> With 13-CURRENT memstick it boots the installed FreeBSD from the SSD
>> instead (I choose USB UEFI OS in boot menu but it silently boots from
>> the SSD instead). If I switch to legacy boot, the memstick image boots fine.
>>
>> Any ideas?
> The .iso building was updated to create hybrid boot images some
> time back, these .iso images should be usable as boot .iso on a
> cd/dvd and as memstick images.  I would encourage there use over
> the memstick images, as there is a plan to remove them once we
> get better experience with the hybrid .iso.

I don't think that would affect things built with poudriere image.
(poudriere image -t usb )

The jails used are download via ftp for both 12 and 13 (created by
poudriere as well).


>
> It is also possible that something has munged the boot in head.
> Have you tried a downloaed ^/head snapshot from the last week,
> as it could also be your build system that is not producing
> a proper boot image?

My 13-CURRENT jail is always latest snapshot.

poudriere image does the same regardless of release: download tarballs,
extract to dir, makefs, mkimg. I don't see why it would work for 12 but
not 13. I can try a newer snapshot later.

>
>> /Johannes
___
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: UEFI boot broken in 13?

2019-06-03 Thread Rodney W. Grimes
> Hi
> 
> I'm using poudriere-image to create usb memstick images. The images are
> identical except OS version. They are tested on a laptop with 13-CURRENT
> installed as only OS, having UEFI boot and root on zfs.
> 
> 12-STABLE memstick boots fine with in UEFI mode.
Does it actually boot via a UEFI, or did UEFI fall back to CSM
and do a legacy boot?

What does "sysctl machdep.bootmethod" say?
machdep.bootmethod: BIOS

> 
> With 13-CURRENT memstick it boots the installed FreeBSD from the SSD
> instead (I choose USB UEFI OS in boot menu but it silently boots from
> the SSD instead). If I switch to legacy boot, the memstick image boots fine.
> 
> Any ideas?

The .iso building was updated to create hybrid boot images some
time back, these .iso images should be usable as boot .iso on a
cd/dvd and as memstick images.  I would encourage there use over
the memstick images, as there is a plan to remove them once we
get better experience with the hybrid .iso.

It is also possible that something has munged the boot in head.
Have you tried a downloaed ^/head snapshot from the last week,
as it could also be your build system that is not producing
a proper boot image?

> /Johannes
-- 
Rod Grimes rgri...@freebsd.org
___
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"


UEFI boot broken in 13?

2019-06-03 Thread Johannes Lundberg
Hi

I'm using poudriere-image to create usb memstick images. The images are
identical except OS version. They are tested on a laptop with 13-CURRENT
installed as only OS, having UEFI boot and root on zfs.

12-STABLE memstick boots fine with in UEFI mode.

With 13-CURRENT memstick it boots the installed FreeBSD from the SSD
instead (I choose USB UEFI OS in boot menu but it silently boots from
the SSD instead). If I switch to legacy boot, the memstick image boots fine.

Any ideas?

/Johannes


___
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: One True Awk upgrade

2019-06-03 Thread Jamie Landeg-Jones
Warner Losh  wrote:

> OK. I've resolved all the diffs between the git-tree I had and what made it
> into the tree. the upgrade is now complete, and I've pushed my notion of
> what awk should be to the bsd-ota branch in
> https://github.com/bsdimp/awk.git I'll work on folding them into upstream,
> although some of them are quite old and I'm unsure if they are appropriate
> for upstream...

Great! Thanks Warner.
___
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: Enabling synaptics and elantech touchpads by default

2019-06-03 Thread Greg V
On June 3, 2019 11:31:21 PM GMT+03:00, Niclas Zeising  
wrote:
>Hi!
>I've created a reveiew, https://reviews.freebsd.org/D20507, to enable 
>synaptics and elantech touchpads by default.
>
>Today, these tunables needs to be set on boot for users to get full use
>
>of their touchpads, even when using X.  By enabling this, things like 
>two finger scroll will work in X by default, meaning we get a more user
>
>friendly appearance.
>
>Is there any reason not to do this?

Probably buggy hardware, as usual?

But the ONLY system I ever saw a problem on is the ASUS Eee PC 900 (where 
elantech support breaks all mouse movement). Which is an extremely irrelevant 
joke of a machine. I only booted it for the nostalgia/laughs/dmesgd.nycbug 
posts.

Definitely +1 to enabling by default. Reducing the amount of tunables required 
for modern desktop use is very good.
___
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"


Enabling synaptics and elantech touchpads by default

2019-06-03 Thread Niclas Zeising

Hi!
I've created a reveiew, https://reviews.freebsd.org/D20507, to enable 
synaptics and elantech touchpads by default.


Today, these tunables needs to be set on boot for users to get full use 
of their touchpads, even when using X.  By enabling this, things like 
two finger scroll will work in X by default, meaning we get a more user 
friendly appearance.


Is there any reason not to do this?
Regards
--
Niclas Zeising
___
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: installworld breakage r348516 -> r348572

2019-06-03 Thread Andreas Nilsson
On Mon, Jun 3, 2019 at 9:35 PM O. Hartmann  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Make installworld after a successful build of r348572 fails due to:
>
> >>> Making hierarchy
> - --
> cd /usr/src; make -f Makefile.inc1  LOCAL_MTREE= hierarchy
> - --- hierarchy ---
> cd /usr/src/etc;
>
> PATH=/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/tmp/install.onYM9YQc
> make LOCAL_MTREE= distrib-dirs --- distrib-cleanup --- for file
> in /usr/share/doc/usd/10.exref /usr/share/doc/usd/11.edit
> /usr/share/doc/usd/12.vi /usr/share/doc/usd/13.viref;
> do  if [ -f /${file} ]; then  rm -f /${file};  fi;  done --- distrib-dirs
> --- -deU -i
> - -f /usr/src/etc/mtree/BSD.root.dist -p / sh: -deU: not found
> *** [distrib-dirs] Error code 127
>
> Greetings,
>
> oh
>
> - --
> O. Hartmann
>
> Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
> Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
> -BEGIN PGP SIGNATURE-
>
> iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXPV2AQAKCRA4N1ZZPba5
> Ry+RAP9inu4/g3bqyHRVSKOv82Gxpk8LUK/YToKzj56DtiCcIgEA31WCq5F5ja3t
> /EtvVa7hk5yAezafBEim/SRsNGjG/wM=
> =cgUI
> -END PGP SIGNATURE-
> ___
> 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"
>

See other mails from today:
"make packages broken"
"Post-installworld mergemaster breakage r348504 -> r348529"
which has info. A fix is supposed to have been commited.

Best regards
Andreas
___
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"


installworld breakage r348516 -> r348572

2019-06-03 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Make installworld after a successful build of r348572 fails due to:

>>> Making hierarchy
- --
cd /usr/src; make -f Makefile.inc1  LOCAL_MTREE= hierarchy
- --- hierarchy ---
cd /usr/src/etc;
PATH=/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/tmp/install.onYM9YQc
make LOCAL_MTREE= distrib-dirs --- distrib-cleanup --- for file
in /usr/share/doc/usd/10.exref /usr/share/doc/usd/11.edit 
/usr/share/doc/usd/12.vi /usr/share/doc/usd/13.viref;
do  if [ -f /${file} ]; then  rm -f /${file};  fi;  done --- distrib-dirs --- 
-deU -i
- -f /usr/src/etc/mtree/BSD.root.dist -p / sh: -deU: not found
*** [distrib-dirs] Error code 127

Greetings,

oh

- -- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXPV2AQAKCRA4N1ZZPba5
Ry+RAP9inu4/g3bqyHRVSKOv82Gxpk8LUK/YToKzj56DtiCcIgEA31WCq5F5ja3t
/EtvVa7hk5yAezafBEim/SRsNGjG/wM=
=cgUI
-END PGP SIGNATURE-
___
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: Post-installworld mergemaster breakage r348504 -> r348529?

2019-06-03 Thread David Wolfskill
On Mon, Jun 03, 2019 at 08:15:18AM -0600, Warner Losh wrote:
> I just committed this as a stop-gap fix.
> 
> Warner
> 

Cool.  I encountered the issue on my build box -- laptop was still busy
with other stuff.  Later, when the laptop was ready for the same update
to head, I applied the change proactively, and things Just Worked. :-)

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
"One of the things I learned is it’s not about the political view, it’s about 
the kind of person they are.” -- political reporter Dave Bryan (retired)

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature


Re: Post-installworld mergemaster breakage r348504 -> r348529?

2019-06-03 Thread Warner Losh
I just committed this as a stop-gap fix.

Warner

On Mon, Jun 3, 2019 at 5:33 AM Andreas Nilsson  wrote:

> On Mon, Jun 3, 2019 at 1:27 PM David Wolfskill 
> wrote:
>
> > On Mon, Jun 03, 2019 at 01:17:44PM +0200, Andreas Nilsson wrote:
> > > ...
> > > > Any hints?
> > > 
> >
> > > Might this be the same I noticed with "make packages", ie:
> > > diff --git a/Makefile.inc1 b/Makefile.inc1
> > > index 6c77c8abdb8..60ac6493c95 100644
> > > --- a/Makefile.inc1
> > > +++ b/Makefile.inc1
> > > @@ -888,7 +888,7 @@ INSTALLFLAGS+=  -h sha256
> > >  .endif
> > >  .if defined(DB_FROM_SRC) || defined(NO_ROOT)
> > >  IMAKE_INSTALL= INSTALL="${INSTALL} ${INSTALLFLAGS}"
> > > -IMAKE_MTREE=   MTREE_CMD="${MTREE_CMD} ${MTREEFLAGS}"
> > > +IMAKE_MTREE=   MTREE_CMD="${MTREE} ${MTREEFLAGS}"
> > >  .endif
> > >
> > >  DESTDIR_MTREEFLAGS=-deU
> > >
> > > Best regards
> > > Andreas
> > > 
> >
> > Thank you!  Yes; that fixes it.
> >
> > (Sorry for failing to recognize that the git hash you cited was related
> > to the r348504 - r348529 range)
> >
> > Peace,
> > david
> > --
> > David H. Wolfskill  da...@catwhisker.org
> > "One of the things I learned is it’s not about the political view, it’s
> > about
> > the kind of person they are.” -- political reporter Dave Bryan (retired)
> >
> > See http://www.catwhisker.org/~david/publickey.gpg for my public key.
> >
>
>
> Great :)
>
> I just want to point out that I'm not certain my "fix" does the right
> thing; it works for me for building packages for amd64 on amd64, I'm not
> sure it correctly handles crossbuilding, so I would wait for an upstream
> fix for any production workloads.
>
> Best regards
> Andreas
> ___
> 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"
>
___
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: Post-installworld mergemaster breakage r348504 -> r348529?

2019-06-03 Thread Andreas Nilsson
On Mon, Jun 3, 2019 at 1:27 PM David Wolfskill  wrote:

> On Mon, Jun 03, 2019 at 01:17:44PM +0200, Andreas Nilsson wrote:
> > ...
> > > Any hints?
> > 
>
> > Might this be the same I noticed with "make packages", ie:
> > diff --git a/Makefile.inc1 b/Makefile.inc1
> > index 6c77c8abdb8..60ac6493c95 100644
> > --- a/Makefile.inc1
> > +++ b/Makefile.inc1
> > @@ -888,7 +888,7 @@ INSTALLFLAGS+=  -h sha256
> >  .endif
> >  .if defined(DB_FROM_SRC) || defined(NO_ROOT)
> >  IMAKE_INSTALL= INSTALL="${INSTALL} ${INSTALLFLAGS}"
> > -IMAKE_MTREE=   MTREE_CMD="${MTREE_CMD} ${MTREEFLAGS}"
> > +IMAKE_MTREE=   MTREE_CMD="${MTREE} ${MTREEFLAGS}"
> >  .endif
> >
> >  DESTDIR_MTREEFLAGS=-deU
> >
> > Best regards
> > Andreas
> > 
>
> Thank you!  Yes; that fixes it.
>
> (Sorry for failing to recognize that the git hash you cited was related
> to the r348504 - r348529 range)
>
> Peace,
> david
> --
> David H. Wolfskill  da...@catwhisker.org
> "One of the things I learned is it’s not about the political view, it’s
> about
> the kind of person they are.” -- political reporter Dave Bryan (retired)
>
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.
>


Great :)

I just want to point out that I'm not certain my "fix" does the right
thing; it works for me for building packages for amd64 on amd64, I'm not
sure it correctly handles crossbuilding, so I would wait for an upstream
fix for any production workloads.

Best regards
Andreas
___
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: Post-installworld mergemaster breakage r348504 -> r348529?

2019-06-03 Thread David Wolfskill
On Mon, Jun 03, 2019 at 01:17:44PM +0200, Andreas Nilsson wrote:
> ...
> > Any hints?
>  

> Might this be the same I noticed with "make packages", ie:
> diff --git a/Makefile.inc1 b/Makefile.inc1
> index 6c77c8abdb8..60ac6493c95 100644
> --- a/Makefile.inc1
> +++ b/Makefile.inc1
> @@ -888,7 +888,7 @@ INSTALLFLAGS+=  -h sha256
>  .endif
>  .if defined(DB_FROM_SRC) || defined(NO_ROOT)
>  IMAKE_INSTALL= INSTALL="${INSTALL} ${INSTALLFLAGS}"
> -IMAKE_MTREE=   MTREE_CMD="${MTREE_CMD} ${MTREEFLAGS}"
> +IMAKE_MTREE=   MTREE_CMD="${MTREE} ${MTREEFLAGS}"
>  .endif
> 
>  DESTDIR_MTREEFLAGS=-deU
> 
> Best regards
> Andreas
> 

Thank you!  Yes; that fixes it.

(Sorry for failing to recognize that the git hash you cited was related
to the r348504 - r348529 range)

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
"One of the things I learned is it’s not about the political view, it’s about 
the kind of person they are.” -- political reporter Dave Bryan (retired)

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature


Re: Post-installworld mergemaster breakage r348504 -> r348529?

2019-06-03 Thread Andreas Nilsson
On Mon, Jun 3, 2019 at 1:06 PM David Wolfskill  wrote:

> I see:
>
> ...
> --
> >>> Installing everything completed on Mon Jun  3 03:48:55 PDT 2019
> --
> Mon Jun  3 03:48:55 PDT 2019
>
> *** Creating the temporary root environment in /var/tmp/temproot
>  *** /var/tmp/temproot ready for use
>  *** Creating and populating directory structure in /var/tmp/temproot
>
> /bin/sh: -N: not found
>
>   *** FATAL ERROR: Cannot 'cd' to /usr/src and install files to
>   the temproot environment
>
>
>
> (using my usual set of csh aliases, so trying again "manually"):
>
> freebeast(13.0-C)[1] cd /usr/src
> freebeast(13.0-C)[2] mergemaster -F -U -u 0022 -i
>
> *** The directory specified for the temporary root environment,
> /var/tmp/temproot, exists.  This can be a security risk if untrusted
> users have access to the system.
>
>   Use 'd' to delete the old /var/tmp/temproot and continue
>   Use 't' to select a new temporary root directory
>   Use 'e' to exit mergemaster
>
>   Default is to use /var/tmp/temproot as is
>
> How should I deal with this? [Use the existing /var/tmp/temproot] d
>
>*** Deleting the old /var/tmp/temproot
>
> *** Creating the temporary root environment in /var/tmp/temproot
>  *** /var/tmp/temproot ready for use
>  *** Creating and populating directory structure in /var/tmp/temproot
>
> /bin/sh: -N: not found
>
>   *** FATAL ERROR: Cannot 'cd' to /usr/src and install files to
>   the temproot environment
>
> freebeast(13.0-C)[3]
>
>
> As for the environment:
>
> FreeBSD freebeast.catwhisker.org 13.0-CURRENT FreeBSD 13.0-CURRENT #573
> r348504M/348508: Sun Jun  2 09:00:52 PDT 2019
> r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC
> amd64
>
> freebeast(13.0-C)[16] grep -v '^#' /etc/make.conf
> SENDMAIL_MC=/etc/mail/client.mc
> freebeast(13.0-C)[17]
>
> freebeast(13.0-C)[17] grep -v '^#' /etc/src.conf
>
> WITHOUT_DEBUG_FILES=1
> WITH_ELFCOPY_AS_OBJCOPY=1
> freebeast(13.0-C)[18]
>
> freebeast(13.0-C)[19] grep -v '^#' /etc/src-env.conf
> WITH_META_MODE=yes
> freebeast(13.0-C)[20]
>
> I find "-N ..." in /usr/src/Makefile.inc1 (for INSTALLFLAGS and
> MTREEFLAGS, but I don't see how that would cause this.  And I've
> been doing this (tracking head daily) for ... "a while" (usually
> without incident).
>
> Any hints?
>
> Thanks!
>
> Peace,
> david
> --
> David H. Wolfskill  da...@catwhisker.org
> "One of the things I learned is it’s not about the political view, it’s
> about
> the kind of person they are.” -- political reporter Dave Bryan (retired)
>
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.
>


Might this be the same I noticed with "make packages", ie:
diff --git a/Makefile.inc1 b/Makefile.inc1
index 6c77c8abdb8..60ac6493c95 100644
--- a/Makefile.inc1
+++ b/Makefile.inc1
@@ -888,7 +888,7 @@ INSTALLFLAGS+=  -h sha256
 .endif
 .if defined(DB_FROM_SRC) || defined(NO_ROOT)
 IMAKE_INSTALL= INSTALL="${INSTALL} ${INSTALLFLAGS}"
-IMAKE_MTREE=   MTREE_CMD="${MTREE_CMD} ${MTREEFLAGS}"
+IMAKE_MTREE=   MTREE_CMD="${MTREE} ${MTREEFLAGS}"
 .endif

 DESTDIR_MTREEFLAGS=-deU

Best regards
Andreas
___
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"


Post-installworld mergemaster breakage r348504 -> r348529?

2019-06-03 Thread David Wolfskill
I see:

...
--
>>> Installing everything completed on Mon Jun  3 03:48:55 PDT 2019
--
Mon Jun  3 03:48:55 PDT 2019

*** Creating the temporary root environment in /var/tmp/temproot
 *** /var/tmp/temproot ready for use
 *** Creating and populating directory structure in /var/tmp/temproot

/bin/sh: -N: not found

  *** FATAL ERROR: Cannot 'cd' to /usr/src and install files to
  the temproot environment



(using my usual set of csh aliases, so trying again "manually"):

freebeast(13.0-C)[1] cd /usr/src
freebeast(13.0-C)[2] mergemaster -F -U -u 0022 -i

*** The directory specified for the temporary root environment,
/var/tmp/temproot, exists.  This can be a security risk if untrusted
users have access to the system.

  Use 'd' to delete the old /var/tmp/temproot and continue
  Use 't' to select a new temporary root directory
  Use 'e' to exit mergemaster

  Default is to use /var/tmp/temproot as is

How should I deal with this? [Use the existing /var/tmp/temproot] d

   *** Deleting the old /var/tmp/temproot

*** Creating the temporary root environment in /var/tmp/temproot
 *** /var/tmp/temproot ready for use
 *** Creating and populating directory structure in /var/tmp/temproot

/bin/sh: -N: not found

  *** FATAL ERROR: Cannot 'cd' to /usr/src and install files to
  the temproot environment

freebeast(13.0-C)[3] 


As for the environment:

FreeBSD freebeast.catwhisker.org 13.0-CURRENT FreeBSD 13.0-CURRENT #573 
r348504M/348508: Sun Jun  2 09:00:52 PDT 2019 
r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC  
amd64

freebeast(13.0-C)[16] grep -v '^#' /etc/make.conf
SENDMAIL_MC=/etc/mail/client.mc
freebeast(13.0-C)[17] 

freebeast(13.0-C)[17] grep -v '^#' /etc/src.conf   
WITHOUT_DEBUG_FILES=1
WITH_ELFCOPY_AS_OBJCOPY=1
freebeast(13.0-C)[18] 

freebeast(13.0-C)[19] grep -v '^#' /etc/src-env.conf 
WITH_META_MODE=yes
freebeast(13.0-C)[20] 

I find "-N ..." in /usr/src/Makefile.inc1 (for INSTALLFLAGS and
MTREEFLAGS, but I don't see how that would cause this.  And I've
been doing this (tracking head daily) for ... "a while" (usually
without incident).

Any hints?

Thanks!

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
"One of the things I learned is it’s not about the political view, it’s about 
the kind of person they are.” -- political reporter Dave Bryan (retired)

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature


Re: make packages broken

2019-06-03 Thread Andreas Nilsson
On Mon, Jun 3, 2019 at 10:40 AM Andreas Nilsson  wrote:

> Hello all,
>
> It was time for the weekly update so git gave
> me: c7cdb4a80779a0451dc2c04c3d6b30769049d402 .
>
> It compiled fined, but when I tried to build packages I get:
> make -C /usr/src PKG_VERSION=13.0.s20190603083918 real-packages
> make[5]: "/usr/obj/usr/src/amd64.amd64/toolchain-metadata.mk" line 1:
> Using cached toolchain metadata from build at charlotte.resilans.se on
> Mon Jun  3 10:12:27 CEST 2019
> --
> >>> Install check world
> --
> mkdir -p /tmp/install.M2Q9GbT8
> progs=$(for prog in [ awk cap_mkdb cat chflags chmod chown cmp cp  date
> echo egrep find grep id install   ln make mkdir mtree mv pwd_mkdb  rm sed
> services_mkdb sh sort strip sysctl test true uname wc zic tzsetup
> makewhatis; do  if progpath=`which $prog`; then  echo $progpath;  else
>  echo "Required tool $prog not found in PATH." >&2;  exit 1;  fi;  done);
>  libs=$(ldd -f "%o %p\n" -f "%o %p\n" $progs 2>/dev/null | sort -u |  while
> read line; do  set -- $line;  if [ "$2 $3" != "not found" ]; then  echo $2;
>  else  echo "Required library $1 not found." >&2;  exit 1;  fi;  done);  cp
> $libs $progs /tmp/install.M2Q9GbT8
> cp -R ${PATH_LOCALE:-"/usr/share/locale"} /tmp/install.M2Q9GbT8/locale
> mkdir -p /usr/obj/usr/src/amd64.amd64/worldstage/
> echo "#mtree 2.0" > /usr/obj/usr/src/amd64.amd64/worldstage//METALOG
> cd /usr/src; MACHINE_ARCH=amd64  MACHINE=amd64  CPUTYPE=skylake CC="cc
> -target x86_64-unknown-freebsd13.0
> --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
> -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin" CXX="c++  -target
> x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
> -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin"  CPP="cpp -target
> x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
> -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin"  AS="as" AR="ar" LD="ld"
> LLVM_LINK=""  NM=nm OBJCOPY="objcopy"  RANLIB=ranlib STRINGS=  SIZE="size"
> PATH=/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/tmp/install.M2Q9GbT8
>  LD_LIBRARY_PATH=/tmp/install.M2Q9GbT8
>  PATH_LOCALE=/tmp/install.M2Q9GbT8/locale make -f Makefile.inc1
>  INSTALL="install -U -M /usr/obj/usr/src/amd64.amd64/worldstage//METALOG -D
> /usr/obj/usr/src/amd64.amd64/worldstage" MTREE_CMD=" -W"
> __MAKE_SHELL=/tmp/install.M2Q9GbT8/sh -DNO_ROOT
> METALOG=/usr/obj/usr/src/amd64.amd64/worldstage//METALOG restage;
>  MACHINE_ARCH=amd64  MACHINE=amd64  CPUTYPE=skylake CC="cc -target
> x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
> -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin" CXX="c++  -target
> x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
> -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin"  CPP="cpp -target
> x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
> -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin"  AS="as" AR="ar" LD="ld"
> LLVM_LINK=""  NM=nm OBJCOPY="objcopy"  RANLIB=ranlib STRINGS=  SIZE="size"
> PATH=/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/tmp/install.M2Q9GbT8
>  LD_LIBRARY_PATH=/tmp/install.M2Q9GbT8
>  PATH_LOCALE=/tmp/install.M2Q9GbT8/locale rm -rf /tmp/install.M2Q9GbT8
> --
> >>> Making hierarchy
> --
> cd /usr/src; make -f Makefile.inc1  LOCAL_MTREE= hierarchy
> cd /usr/src/etc;
> PATH=/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/tmp/install.M2Q9GbT8
> make LOCAL_MTREE=
> PATH=/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/tmp/install.M2Q9GbT8
> METALOG=/usr/obj/usr/src/amd64.amd64/worldstage//METALOG -DNO_ROOT
> distrib-dirs
> for file in /usr/share/doc/usd/10.exref /usr/share/doc/usd/11.edit
> 

make packages broken

2019-06-03 Thread Andreas Nilsson
Hello all,

It was time for the weekly update so git gave
me: c7cdb4a80779a0451dc2c04c3d6b30769049d402 .

It compiled fined, but when I tried to build packages I get:
make -C /usr/src PKG_VERSION=13.0.s20190603083918 real-packages
make[5]: "/usr/obj/usr/src/amd64.amd64/toolchain-metadata.mk" line 1: Using
cached toolchain metadata from build at charlotte.resilans.se on Mon Jun  3
10:12:27 CEST 2019
--
>>> Install check world
--
mkdir -p /tmp/install.M2Q9GbT8
progs=$(for prog in [ awk cap_mkdb cat chflags chmod chown cmp cp  date
echo egrep find grep id install   ln make mkdir mtree mv pwd_mkdb  rm sed
services_mkdb sh sort strip sysctl test true uname wc zic tzsetup
makewhatis; do  if progpath=`which $prog`; then  echo $progpath;  else
 echo "Required tool $prog not found in PATH." >&2;  exit 1;  fi;  done);
 libs=$(ldd -f "%o %p\n" -f "%o %p\n" $progs 2>/dev/null | sort -u |  while
read line; do  set -- $line;  if [ "$2 $3" != "not found" ]; then  echo $2;
 else  echo "Required library $1 not found." >&2;  exit 1;  fi;  done);  cp
$libs $progs /tmp/install.M2Q9GbT8
cp -R ${PATH_LOCALE:-"/usr/share/locale"} /tmp/install.M2Q9GbT8/locale
mkdir -p /usr/obj/usr/src/amd64.amd64/worldstage/
echo "#mtree 2.0" > /usr/obj/usr/src/amd64.amd64/worldstage//METALOG
cd /usr/src; MACHINE_ARCH=amd64  MACHINE=amd64  CPUTYPE=skylake CC="cc
-target x86_64-unknown-freebsd13.0
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin" CXX="c++  -target
x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin"  CPP="cpp -target
x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin"  AS="as" AR="ar" LD="ld"
LLVM_LINK=""  NM=nm OBJCOPY="objcopy"  RANLIB=ranlib STRINGS=  SIZE="size"
PATH=/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/tmp/install.M2Q9GbT8
 LD_LIBRARY_PATH=/tmp/install.M2Q9GbT8
 PATH_LOCALE=/tmp/install.M2Q9GbT8/locale make -f Makefile.inc1
 INSTALL="install -U -M /usr/obj/usr/src/amd64.amd64/worldstage//METALOG -D
/usr/obj/usr/src/amd64.amd64/worldstage" MTREE_CMD=" -W"
__MAKE_SHELL=/tmp/install.M2Q9GbT8/sh -DNO_ROOT
METALOG=/usr/obj/usr/src/amd64.amd64/worldstage//METALOG restage;
 MACHINE_ARCH=amd64  MACHINE=amd64  CPUTYPE=skylake CC="cc -target
x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin" CXX="c++  -target
x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin"  CPP="cpp -target
x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin"  AS="as" AR="ar" LD="ld"
LLVM_LINK=""  NM=nm OBJCOPY="objcopy"  RANLIB=ranlib STRINGS=  SIZE="size"
PATH=/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/tmp/install.M2Q9GbT8
 LD_LIBRARY_PATH=/tmp/install.M2Q9GbT8
 PATH_LOCALE=/tmp/install.M2Q9GbT8/locale rm -rf /tmp/install.M2Q9GbT8
--
>>> Making hierarchy
--
cd /usr/src; make -f Makefile.inc1  LOCAL_MTREE= hierarchy
cd /usr/src/etc;
PATH=/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/tmp/install.M2Q9GbT8
make LOCAL_MTREE=
PATH=/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin::/tmp/install.M2Q9GbT8
METALOG=/usr/obj/usr/src/amd64.amd64/worldstage//METALOG -DNO_ROOT
distrib-dirs
for file in /usr/share/doc/usd/10.exref /usr/share/doc/usd/11.edit
/usr/share/doc/usd/12.vi /usr/share/doc/usd/13.viref; do  if [ -f
/usr/obj/usr/src/amd64.amd64/worldstage/${file} ]; then  rm -f
/usr/obj/usr/src/amd64.amd64/worldstage/${file};  fi;  done
-W -deU