Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

16.1.5: Could not find package: ngattach #25

Closed
oparoz opened this issue Mar 3, 2016 · 9 comments
Closed

16.1.5: Could not find package: ngattach #25

oparoz opened this issue Mar 3, 2016 · 9 comments

Comments

@oparoz
Copy link

oparoz commented Mar 3, 2016

Following the process defined earlier in the 16.1 cycle, I now get

# make core-16.1.5
.MAKE.LEVEL.ENV=MAKELEVEL
ARCH=amd64
BLOCKSIZE=K
CCACHE_DIR=/var/db/ccache
CCACHE_LOGFILE=/var/log/ccache.log
CCACHE_PATH=/usr/bin:/usr/local/bin
CLICOLOR=YES
CONFIGDIR=/usr/tools/config/16.1
CONFIG_PKG=/usr/local/etc/pkg/repos/origin.conf
CONFIG_XML=/usr/local/etc/config.xml
COREDIR=/usr/core

...
# Rules section
# uPnPd rule anchor
anchor "miniupnpd"
Installing mpd4-4.4.1_2...
`-- Installing libpdel-0.5.3_6...
`-- Extracting libpdel-0.5.3_6: 100%
Extracting mpd4-4.4.1_2: 100%
Installing mpd5-5.8...
Extracting mpd5-5.8: 100%
Could not find package: ngattach
*** Error code 1

Stop.
make: stopped in /usr/tools

I can install mpd5 just fine from ports, so there seems to be some package issue.

@fichtner
Copy link
Member

fichtner commented Mar 3, 2016

ngattach is a new port, you need to rebuild (or force rebuild) ports in order to pick it up:

# make ports-ngattach
# make core-16.1.5

@fichtner fichtner closed this as completed Mar 3, 2016
@oparoz
Copy link
Author

oparoz commented Mar 3, 2016

Thanks, but shouldn't make prefetch-packages VERSION=16.1 download all the required packages without having to manually compile them?

Also, make ports-ngattach fails

>>> Building net/isc-dhcp43-client... ===>  Cleaning for isc-dhcp43-client-4.3.3P1_1

===>  isc-dhcp43-client-4.3.3P1_1 conflicts with installed package(s):
      isc-dhcp42-client-4.2.8

      They install files into the same place.
      You may want to stop build with Ctrl + C.
===>  License ISCL accepted by the user
===>   isc-dhcp43-client-4.3.3P1_1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by isc-dhcp43-client-4.3.3P1_1 for building

===>  isc-dhcp43-client-4.3.3P1_1 conflicts with installed package(s):
      isc-dhcp42-client-4.2.8

      They will not build together.
      Please remove them first with pkg delete.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/net/isc-dhcp43-client

@fichtner
Copy link
Member

fichtner commented Mar 3, 2016

You cannot magically turn a 16.1(.0) packages set into a 16.1.x set, it will fail at some point because ports need to be switched, updated and removed. Plus you're updating the GUI, but not the vulnerable packages that way...

My advice is to recompile the ports completely. It's what we do for every release or deal with the aftermath yourself:

# make ports-isc-dhcp42-client,isc-dhcp42-server,isc-dhcp42-relay

@fichtner
Copy link
Member

fichtner commented Mar 3, 2016

Also, you're trying to build 16.1.5 from a tools.git perspective past 16.1.5, because dhcp 4.3 isn't used there.

# cd /usr/tools
# git checkout 16.1.5

This will avoid the next clash when core.git will want DHCP 4.2, not 4.3...

@oparoz
Copy link
Author

oparoz commented Mar 3, 2016

You cannot magically turn a 16.1(.0) packages set into a 16.1.x set

I think I understand. You only make the dot zero release available as a download, because people may not necessarily want to install the latest version and there will be problems if packages are newer than core.

Plus you're updating the GUI, but not the vulnerable packages that way...

Since I have a local ports tree, I don't care about updating packages to generate core. The only think I'm after is the GUI.

My advice is to recompile the ports completely

They are all compiled from source, just not when building the packages "image" from which I extract the GUI.

Also, you're trying to build 16.1.5 from a tools.git perspective past 16.1.5, because dhcp 4.3 isn't used there.

But then I would be stuck on an old branch which only gets the latest updates from upstream once a week.
I guess that's still the right thing to do as the GUI may not be designed for some of the newer packages.
Thanks for the advice. I'll update the How-to.

I stumbled upon another problem which makes it impossible to compile ports

+ rm -rf /usr/obj/usr/tools/config/16.1/OpenSSL
*** Error code 1

Stop.
make: stopped in /usr/tools

When manually running the command, I can see why:

# rm -rf /usr/obj/usr/tools/config/16.1/OpenSSL
rm: /usr/obj/usr/tools/config/16.1/OpenSSL/dev/fd: Operation not supported
rm: /usr/obj/usr/tools/config/16.1/OpenSSL/dev/usb: Operation not supported
rm: /usr/obj/usr/tools/config/16.1/OpenSSL/dev/pts: Operation not supported
rm: /usr/obj/usr/tools/config/16.1/OpenSSL/dev: Device busy
rm: /usr/obj/usr/tools/config/16.1/OpenSSL: Directory not empty

@fichtner
Copy link
Member

fichtner commented Mar 3, 2016

# make clean-stage

Fixes this, devfs is mounted inside the jail.

@oparoz
Copy link
Author

oparoz commented Mar 3, 2016

Nope, same problem

+ :
+
+ setup_stage /usr/obj/usr/tools/config/16.1/OpenSSL
+ echo '>>> Setting up stage in /usr/obj/usr/tools/config/16.1/OpenSSL'
>>> Setting up stage in /usr/obj/usr/tools/config/16.1/OpenSSL
+ local 'MOUNTDIRS=/dev /usr/src /usr/ports /usr/core /usr/plugins'
+ [ -d /usr/obj/usr/tools/config/16.1/OpenSSL/dev ]
+ umount /usr/obj/usr/tools/config/16.1/OpenSSL/dev
+ true
+ [ -d /usr/obj/usr/tools/config/16.1/OpenSSL/usr/src ]
+ [ -d /usr/obj/usr/tools/config/16.1/OpenSSL/usr/ports ]
+ [ -d /usr/obj/usr/tools/config/16.1/OpenSSL/usr/core ]
+ [ -d /usr/obj/usr/tools/config/16.1/OpenSSL/usr/plugins ]
+ rm -rf /usr/obj/usr/tools/config/16.1/OpenSSL
+ chflags -R noschg /usr/obj/usr/tools/config/16.1/OpenSSL
+ rm -rf /usr/obj/usr/tools/config/16.1/OpenSSL
*** Error code 1

Stop.
make: stopped in /usr/tools

@fichtner
Copy link
Member

fichtner commented Mar 3, 2016

A runaway process is stuck in the jail, that's likely why devfs won't unmount.

@oparoz
Copy link
Author

oparoz commented Mar 3, 2016

Thanks, it was configd.

All good after that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants