You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
whether things work with old pkg and the new pkgng toolstacks.
For the last point (pkg vs. pkgng), we need to make working beaker with FreeBSD 9.2 (and 9.3 (done)). There are four main issues:
on freebsd-9 beaker insists on using pkg_add -r for installing rsync, update: fixed in portsng 0.2.0 via monkey patch,
on any version, including freebsd-9.2, beaker uses pkg info to check if curlis installed, update*: fixed in portsng 0.2.0 via monkey patch,
also, beaker is unable of making correct choice between pkg_add and pkg install when installing packages (including puppet), update: fixed in portsng 0.2.0 via monkey patch,
finally, install_puppet_on tries to install sysutils/puppet, but we have in repository sysutils/puppet37, sysutils/puppet38 and sysutils/puppet4update: workarounded in portsng 0.2.0, we use install_package instead.
The text was updated successfully, but these errors were encountered:
Patched beaker, such that it's able to install all prerequisites also when there is no pkgng. Now the problem is, that portupgrade insists on switching to pkgng on FreeBSD 9.2. No idea why...
Need more to check with acceptance testing:
install_options
work,uninstall_options
work,package_settings
work,pkg
and the newpkgng
toolstacks.For the last point (pkg vs. pkgng), we need to make working beaker with FreeBSD 9.2 (and 9.3 (done)). There are four main issues:
pkg_add -r
for installingrsync
, update: fixed in portsng 0.2.0 via monkey patch,pkg info
to check ifcurl
is installed, update*: fixed in portsng 0.2.0 via monkey patch,pkg_add
andpkg install
when installing packages (including puppet), update: fixed in portsng 0.2.0 via monkey patch,install_puppet_on
tries to installsysutils/puppet
, but we have in repositorysysutils/puppet37
,sysutils/puppet38
andsysutils/puppet4
update: workarounded in portsng 0.2.0, we useinstall_package
instead.The text was updated successfully, but these errors were encountered: