Bug 233948

Summary: sysutils/iocage: No package for 12.0-RELEASE (quarterly)
Product: Ports & Packages Reporter: Jason Tubnor <jason>
Component: Individual Port(s)Assignee: Marcelo Araujo <araujo>
Status: Closed FIXED    
Severity: Affects Many People CC: antoine, java4dev, python
Priority: --- Keywords: needs-qa
Version: LatestFlags: bugzilla: maintainer-feedback? (araujo)
antoine: merge-quarterly-
Hardware: amd64   
OS: Any   

Description Jason Tubnor 2018-12-11 22:53:45 UTC
After running through the standard upgrade procedure, iocage stopped working with the following output:

# iocage list
Traceback (most recent call last):
  File "/usr/local/bin/iocage", line 6, in <module>
    from iocage.main import cli
  File "/usr/local/lib/python3.6/site-packages/iocage/main.py", line 37, in <module>
    import iocage.lib.ioc_check as ioc_check
  File "/usr/local/lib/python3.6/site-packages/iocage/lib/ioc_check.py", line 28, in <module>
    import libzfs
ImportError: Shared object "libzfs.so.2" not found, required by "libzfs.so"

It appears that it hasn't been adjusted for the new shared object libzfs.so.3

To workaround create a symlink from .3 to .2

# cd /lib
# ln -s libzfs.so.3 libzfs.so.2

But after further investigation (pkg info py36-iocage) I found that it didn't upgrade as part of the pkg update/upgrade process when moving to 12.0.  Looking through the package repo, it isn't even available as a package.  Can this be addressed
Comment 1 Jason Tubnor 2018-12-12 02:00:01 UTC
Further clarification - py36-iocage is located in the 'latest' branch but does not exist in 'quarterly'.
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2018-12-14 06:17:19 UTC
iocage appears in SKIPPED due to "Reason: py36-libzfs-1.0.20171215", which was IGNORED due to "requires kernel source files in /usr/src". [1]

There was also ports r481901 (cc tobik) which wasn't MFH'd, which may be related/implicated.

[1] beefy2 - 120amd64-quarterly
Comment 3 java4dev 2019-01-26 18:56:37 UTC
Hello

Any news on this issue?
I have also uppgrated from FreeBSD 11 to FreeBSD 12 and can no longer access any of the jails.

Best Regards
Nikolas
Comment 4 Antoine Brodin freebsd_committer freebsd_triage 2019-01-26 19:36:14 UTC
I can't reproduce.
Comment 5 Jason Tubnor 2019-01-28 03:52:05 UTC
I can confirm that it now exists in the quarterly repo.  Ok to stay closed.  Thanks
Comment 6 java4dev 2019-01-28 09:22:55 UTC
Thank you Jason
does this means that we will get teh fix via the freebsd-update?
Best