Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-04 Thread Michael Gmelin


> On 4. Feb 2021, at 10:47, Yasuhiro Kimura  wrote:
> 
> It's a bit off topic from the first question, but please let me ask
> another one.
> 
> When everything is default, devel/git and textproc/docproj are
> installed in chroot environment after building userland and installing
> it to chroot has completed. While the former is installed by using
> official package, the latter is installed by using ports tree checked
> out in chroot.
> 
> Then is there any reason doing so? Why aren't both of them installed
> by using offical package nor by using ports tree?

I would assume that this is because

- textproc/docproj is the FreeBSD Documentation Project and therefore you 
always want to have the latest version, especially when working with CURRENT 
(so it’s part of our development effort).
- git is a third party tool maintained outside of the project (we won’t change 
it as part of developing FreeBSD)

Cheers,
Michael


> 
> ---
> Yasuhiro Kimura
> ___
> 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: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-04 Thread Yasuhiro Kimura
It's a bit off topic from the first question, but please let me ask
another one.

When everything is default, devel/git and textproc/docproj are
installed in chroot environment after building userland and installing
it to chroot has completed. While the former is installed by using
official package, the latter is installed by using ports tree checked
out in chroot.

Then is there any reason doing so? Why aren't both of them installed
by using offical package nor by using ports tree?

---
Yasuhiro Kimura
___
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: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-03 Thread Rodney W. Grimes
-- Start of PGP signed section.
> On Mon, Feb 01, 2021 at 05:13:42PM -0800, Rodney W. Grimes wrote:
> 
> >One could build your own local pkg repository that contained pkg
> >and what ever other pkg's are needed during a make release and
> >modify the /etc/pkg/FreeBSD.conf file to point at it as a way
> >to work around this .
> 
> Thanks for the suggestion, might try that. I guess here you're thinking
> poudriere?

I think it is just a small set of pkg's you need so, no not poudriere,
was just thinking cd /usr/src/.../pkg; make package; cp pkg*.tgz 
/place/for/packages

> -- 
> J.
-- End of PGP section, PGP failed!

-- 
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"


Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-03 Thread Yasuhiro Kimura
From: Glen Barber 
Subject: Re: Failure of release build with release.sh on 14-CURRENT amd64
Date: Mon, 1 Feb 2021 21:26:23 +

> Setting NODOC=1 should workaround the problem for now,

Thanks, Release build successfully completed with it.

> until the
> conversion from XML to ASCIIDoc/Hugo is 100% complete.  (It is
> effectively complete, but there are a few nits here and there that need
> to be resolved.)

I got it. Since textproj/docproj is meta port, it also need to be
updated to depend on new required tools.

---
Yasuhiro Kimura
___
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: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-03 Thread tech-lists

On Mon, Feb 01, 2021 at 05:13:42PM -0800, Rodney W. Grimes wrote:


One could build your own local pkg repository that contained pkg
and what ever other pkg's are needed during a make release and
modify the /etc/pkg/FreeBSD.conf file to point at it as a way
to work around this .


Thanks for the suggestion, might try that. I guess here you're thinking
poudriere?

--
J.


signature.asc
Description: PGP signature


Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-01 Thread Rodney W. Grimes
On some day Glen Barber wrote:
> On Mon, Feb 01, 2021 at 09:38:33PM +, tech-lists wrote:
> > On Mon, Feb 01, 2021 at 09:27:44PM +, Glen Barber wrote:
> > > On Sun, Jan 31, 2021 at 03:30:14PM +, tech-lists wrote:
> > > > Found
> > > > A pre-built version of pkg could not be found for your system.
> > > > Consider changing PACKAGESITE or installing it from ports:
> > > > 'ports-mgmt/pkg'.
> > > > 
> > > > root@generic:/usr/src/release # which pkg
> > > > /usr/sbin/pkg
> > > > 
> > > 
> > > This is because the 14.0-CURRENT packages for arm64 take a significant
> > > amount of more time to build than x86.
> > 
> > Hi,
> > 
> > Is there a way of making it use the pkg which is already installed on the 
> > system
> > running make release?
> > 
> 
> No.  /usr/sbin/pkg is the bootstrap tool to install /usr/local/sbin/pkg.
> It does not have the same functionality.

One could build your own local pkg repository that contained pkg
and what ever other pkg's are needed during a make release and
modify the /etc/pkg/FreeBSD.conf file to point at it as a way
to work around this .

> Glen

-- 
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"


Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-01 Thread Glen Barber
On Mon, Feb 01, 2021 at 09:38:33PM +, tech-lists wrote:
> On Mon, Feb 01, 2021 at 09:27:44PM +, Glen Barber wrote:
> > On Sun, Jan 31, 2021 at 03:30:14PM +, tech-lists wrote:
> > > Found
> > > A pre-built version of pkg could not be found for your system.
> > > Consider changing PACKAGESITE or installing it from ports:
> > > 'ports-mgmt/pkg'.
> > > 
> > > root@generic:/usr/src/release # which pkg
> > > /usr/sbin/pkg
> > > 
> > 
> > This is because the 14.0-CURRENT packages for arm64 take a significant
> > amount of more time to build than x86.
> 
> Hi,
> 
> Is there a way of making it use the pkg which is already installed on the 
> system
> running make release?
> 

No.  /usr/sbin/pkg is the bootstrap tool to install /usr/local/sbin/pkg.
It does not have the same functionality.

Glen



signature.asc
Description: PGP signature


Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-01 Thread tech-lists

On Mon, Feb 01, 2021 at 09:27:44PM +, Glen Barber wrote:

On Sun, Jan 31, 2021 at 03:30:14PM +, tech-lists wrote:

Found
A pre-built version of pkg could not be found for your system.
Consider changing PACKAGESITE or installing it from ports:
'ports-mgmt/pkg'.

root@generic:/usr/src/release # which pkg
/usr/sbin/pkg



This is because the 14.0-CURRENT packages for arm64 take a significant
amount of more time to build than x86.


Hi,

Is there a way of making it use the pkg which is already installed on the system
running make release?

thanks,
--
J.


signature.asc
Description: PGP signature


Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-01 Thread Glen Barber
On Sun, Jan 31, 2021 at 03:30:14PM +, tech-lists wrote:
> Hello,
> 
> I also tried to build a release and failed. My context is different to
> yours, though. The failure error is different. Just thought I'd mention
> it as "make release on -current is broken for me as well". In my
> context, it ignores the installed pkg and tries, and fails to get a
> -current pkg binary from the repos.
> 
> Context is raspberry pi4/8GB
> git version is src.git as of 30/01/21 evening UTC
> 
> command used was: root@generic:/usr/src/release # sh release.sh -c
> arm64/RPI.conf
> 
> error:
> --- installdirs-CONFSDIR ---
> installing DIRS CONFSDIR
> install -N /scratch/usr/src/etc  -d -m 0755 -o root  -g wheel
> /scratch/etc/pkg
> ELF ldconfig path: /lib /usr/lib /usr/lib/compat
> Bootstrapping pkg from
> pkg+http://pkg.FreeBSD.org/FreeBSD:14:aarch64/latest, please wait...
> pkg: Error fetching
> http://pkg.FreeBSD.org/FreeBSD:14:aarch64/latest/Latest/pkg.txz: Not
> Found
> A pre-built version of pkg could not be found for your system.
> Consider changing PACKAGESITE or installing it from ports:
> 'ports-mgmt/pkg'.
> 
> root@generic:/usr/src/release # which pkg
> /usr/sbin/pkg
> 

This is because the 14.0-CURRENT packages for arm64 take a significant
amount of more time to build than x86.

Glen



signature.asc
Description: PGP signature


Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-01 Thread Glen Barber
On Sun, Jan 31, 2021 at 04:29:09PM +0900, Yasuhiro Kimura wrote:
> Hello,
> 
> I tried release build with /usr/src/release/release.sh on 14-CURRENT
> amd64 under followin conditions.
> 
> * 14-CURRENT amd64
> * f17fc5439f5 + revert of 84eaf2ccc6a (Workaroud of the problem
>   reported as bug 253087 on Bugzilla)
> * No release.conf, everithing is default
> * /scratch is empty when build starts
> * /scratch/usr/doc is ba0831043d of main
> * /scratch/usr/ports is r563439 of head
> * /scratch/usr/src is 151ec796a23 of main
> * devel/git is installed but devel/subversion isn't
> 
> And the result is failure with following error messages.
> 
> --
> cd /usr/doc/en_US.ISO8859-1/htdocs/releases/14.0R &&  env 
> MAN4DIR=/usr/src/release/../share/man/man4  _BRANCH=CURRENT  make all install 
> clean "FORMATS=html txt"  INSTALL_COMPRESSED='' URLS_ABSOLUTE=YES 
> DOCDIR=/usr/obj/usr/src/amd64.amd64/
> release/rdoc  WEBDIR=/usr/doc 
> DESTDIR=/usr/obj/usr/src/amd64.amd64/release/rdoc
> cd: /usr/doc/en_US.ISO8859-1/htdocs/releases/14.0R: No such file or directory
> *** Error code 2
> 
> Stop.
> make[1]: stopped in /usr/src/release
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/src/release
> --
> 
> Full buld log is
> 
> https://www.utahime.org/FreeBSD/release.sh.2021-01-31-09-10-35.log
> 
> (Caution: Size of the file is about 75MB)
> 
> Does this mean that release.sh is simply broken right now or I did
> something wrong?
> 

Setting NODOC=1 should workaround the problem for now, until the
conversion from XML to ASCIIDoc/Hugo is 100% complete.  (It is
effectively complete, but there are a few nits here and there that need
to be resolved.)

Glen



signature.asc
Description: PGP signature


Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-01-31 Thread tech-lists

Hello,

I also tried to build a release and failed. My context is different to
yours, though. The failure error is different. Just thought I'd mention
it as "make release on -current is broken for me as well". In my
context, it ignores the installed pkg and tries, and fails to get a
-current pkg binary from the repos.

Context is raspberry pi4/8GB
git version is src.git as of 30/01/21 evening UTC

command used was: 
root@generic:/usr/src/release # sh release.sh -c arm64/RPI.conf


error:
--- installdirs-CONFSDIR ---
installing DIRS CONFSDIR
install -N /scratch/usr/src/etc  -d -m 0755 -o root  -g wheel
/scratch/etc/pkg
ELF ldconfig path: /lib /usr/lib /usr/lib/compat
Bootstrapping pkg from
pkg+http://pkg.FreeBSD.org/FreeBSD:14:aarch64/latest, please wait...
pkg: Error fetching
http://pkg.FreeBSD.org/FreeBSD:14:aarch64/latest/Latest/pkg.txz: Not
Found
A pre-built version of pkg could not be found for your system.
Consider changing PACKAGESITE or installing it from ports:
'ports-mgmt/pkg'.

root@generic:/usr/src/release # which pkg
/usr/sbin/pkg

--
J.


signature.asc
Description: PGP signature


Failure of release build with release.sh on 14-CURRENT amd64

2021-01-30 Thread Yasuhiro Kimura
Hello,

I tried release build with /usr/src/release/release.sh on 14-CURRENT
amd64 under followin conditions.

* 14-CURRENT amd64
* f17fc5439f5 + revert of 84eaf2ccc6a (Workaroud of the problem
  reported as bug 253087 on Bugzilla)
* No release.conf, everithing is default
* /scratch is empty when build starts
* /scratch/usr/doc is ba0831043d of main
* /scratch/usr/ports is r563439 of head
* /scratch/usr/src is 151ec796a23 of main
* devel/git is installed but devel/subversion isn't

And the result is failure with following error messages.

--
cd /usr/doc/en_US.ISO8859-1/htdocs/releases/14.0R &&  env 
MAN4DIR=/usr/src/release/../share/man/man4  _BRANCH=CURRENT  make all install 
clean "FORMATS=html txt"  INSTALL_COMPRESSED='' URLS_ABSOLUTE=YES 
DOCDIR=/usr/obj/usr/src/amd64.amd64/
release/rdoc  WEBDIR=/usr/doc DESTDIR=/usr/obj/usr/src/amd64.amd64/release/rdoc
cd: /usr/doc/en_US.ISO8859-1/htdocs/releases/14.0R: No such file or directory
*** Error code 2

Stop.
make[1]: stopped in /usr/src/release
*** Error code 1

Stop.
make: stopped in /usr/src/release
--

Full buld log is

https://www.utahime.org/FreeBSD/release.sh.2021-01-31-09-10-35.log

(Caution: Size of the file is about 75MB)

Does this mean that release.sh is simply broken right now or I did
something wrong?

Best Regards.

---
Yasuhiro Kimura
___
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"