Re: Might an UPDATING entry be appropriate for a MINIMAL_PKG_VERSION bump?

2020-10-05 Thread Tatsuki Makino
David Wolfskill wrote on 2020/10/06 08:45:

> 
> But in order for them to be built, you need to have updated
> ports-mgmt/pkg ahead of time, or this kind of thing happens:
> 
> | ...

> | ===>  Cleaning for nvidia-driver-440.100_1
> | ===>  nvidia-driver-440.100_1 pkg(8) must be version 1.15.9 or greater, but
> | you have 1.15.8. You must upgrade the ports-mgmt/pkg port first.
> | *** Error code 1
> | 
> | Stop.
> 

Hmmm.
I've never bothered with that because I'm following the steps below :)

svnlite cleanup /usr/src
svnlite update /usr/src
rm -r -f /usr/obj/{*,.[^.]*,..?*}
svnlite revert -R /usr/src
patch -d /usr/src < mypatch
portsnap fetch update
portmaster -x \*-kmod-\[0-9gv\] -a
make -C /usr/src buildworld
make -C /usr/src buildkernel
mergemaster -p
make -C /usr/src installkernel
make -C /usr/src installworld
make -C /usr/src delete-old delete-old-libs
mergemaster
shutdown -r +1

> 
> Hence my query: Is an UPDATING entry warranted when MINIMAL_PKG_VERSION is
> bumped?
>

Normally, when pkg appears in pkg version -L =, it is replaced
immediately because something of a bug in it has been fixed.
Rarely, though, there are more bugs :)

Best regards.

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


Re: Might an UPDATING entry be appropriate for a MINIMAL_PKG_VERSION bump?

2020-10-05 Thread David Wolfskill
On Tue, Oct 06, 2020 at 08:31:05AM +0900, Tatsuki Makino wrote:
> Hello.
> 
> In my case,
> -x \*-kmod-\[0-9gv\] is added to portmaster because all packages that
> install kernel modules contain -kmod in their names. This excludes *-kmod.
> And when they are upgraded, I won't be installing them right away.
> 
> Then to install them I write PORTS_MODULES in src.conf.
> PORTS_MODULES=\
> graphics/drm-fbsd12.0-kmod\
> graphics/gpu-firmware-kmod
> 
> They are created at the same time as the kernel.
> 

But in order for them to be built, you need to have updated
ports-mgmt/pkg ahead of time, or this kind of thing happens:

| ...
| --- kernel.full ---
| linking kernel.full
| ctfmerge -L VERSION -g -o kernel.full ...
|   text  data   bssdec hex   filename
|   22900304   1840729   3667344   28408377   0x1b17a39   kernel.full
| Building /common/S1/obj/usr/src/amd64.amd64/sys/CANARY/kernel.debug
| Building /common/S1/obj/usr/src/amd64.amd64/sys/CANARY/kernel
| --- all ---
| ===> Ports module x11/nvidia-driver (all)
| cd ${PORTSDIR:-/usr/ports}/x11/nvidia-driver; env  -u CC  -u CXX  -u CPP  -u 
MAKESYSPATH  -u MK_AUTO_OBJ  -u MAKEOBJDIR  MAKEFLAGS="-j 16 -J 15,16 -j 16 -J 
15,16 -D NO_MODULES_OBJ .MAKE.LEVEL.ENV=MAKELEVEL KERNEL=kernel TARGET=amd64 
TARGET_ARCH=amd64"  SYSDIR=/usr/src/sys  
PATH=/common/S1/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/common/S1/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/common/S1/obj/usr/src/amd64.amd64/tmp/legacy/bin:/common/S1/obj/usr/src/amd64.amd64/tmp/usr/sbin:/common/S1/obj/usr/src/amd64.amd64/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin
  SRC_BASE=/usr/src  OSVERSION=1202502  
WRKDIRPREFIX=/common/S1/obj/usr/src/amd64.amd64/sys/CANARY make -B clean build
| ===>  Cleaning for nvidia-driver-440.100_1
| ===>  nvidia-driver-440.100_1 pkg(8) must be version 1.15.9 or greater, but
| you have 1.15.8. You must upgrade the ports-mgmt/pkg port first.
| *** Error code 1
| 
| Stop.


Hence my query: Is an UPDATING entry warranted when MINIMAL_PKG_VERSION is
bumped?

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
"the end of the pandemic is in sight" -- Donald Trump (while infected
with SARS-COV-2)

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


signature.asc
Description: PGP signature


Re: Might an UPDATING entry be appropriate for a MINIMAL_PKG_VERSION bump?

2020-10-05 Thread Tatsuki Makino
Hello.

In my case,
-x \*-kmod-\[0-9gv\] is added to portmaster because all packages that
install kernel modules contain -kmod in their names. This excludes *-kmod.
And when they are upgraded, I won't be installing them right away.

Then to install them I write PORTS_MODULES in src.conf.
PORTS_MODULES=\
graphics/drm-fbsd12.0-kmod\
graphics/gpu-firmware-kmod

They are created at the same time as the kernel.

Best regards.


David Wolfskill wrote on 2020/10/05 21:54:
> When I rebuild FreeBSD (stable/12) on my laptop, I also rebuild a ports
> module (x11/nvidia-driver), since the laptop has an Nvidia graphics
> card.
> 
> However, a couple of times within the last few days, the kernel build
> has failed because I normally wait to update ports until after I have
> built and rebooted the newly-built base OS... and "?ports" includes
> ports-mgmt/pkg.
> 
> In each case (so far), I have then updated ports-mgmt/pkg, then
> re-started the base OS build/install.
> 
> I believe that it would be helpful to have an UPDATING entry reflect
> that "evasive action" is required when MINIMAL_PKG_VERSION is bumped.
> 
> Or, perhaps, I'm going about this all wrong...?  If so, please let me
> know a better way.
> 
> Thanks.
> 
> Peace,
> david
> 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"