latest freebsd:11:x86:64 repo and ruby 1.9 -> 2.0

Baptiste Daroussin bapt at FreeBSD.org
Mon Oct 20 06:59:06 UTC 2014


On Mon, Oct 20, 2014 at 09:29:23AM +0300, Andriy Gapon wrote:
> On 20/10/2014 01:08, Baptiste Daroussin wrote:
> > On Sat, Oct 18, 2014 at 12:29:27PM +0300, Andriy Gapon wrote:
> >>> $ pkg upgrade Updating FreeBSD repository catalogue... FreeBSD
> >>> repository is up-to-date. Updating poudriere repository catalogue... 
> >>> poudriere repository is up-to-date. All repositories are up-to-date. 
> >>> Checking for upgrades (24 candidates): 100% Checking integrity... done
> >>> (1 conflicting) Checking integrity... done (0 conflicting) The
> >>> following 24 packages will be affected (of 0 checked):
> >> 
> >> First, a minor nit: of 0 checked?
> >> 
> >>> Installed packages to be REMOVED: ruby-1.9.3.547_3,1 porttools-1.02 
> >>> newfile-1.0.14_4 hub-1.12.2 libchk-1.10.3 zfs-snapshot-mgmt-20090201_2
> >> 
> >> Then the real problem, I do not want these packages to be removed except
> >> for ruby-1.9.3.547_3,1.  In other words, I want to keep using
> >> zfs-snapshot-mgmt, libchk, hub and porttools.  What should I do?
> > 
> > Just accept the upgrade and reinstall them they are there. we need to
> > improve the solver to prevent that.
> 
> OK.  This should work for me this time, but in general we can see how annoying
> this could be if dozens of packages would be affected.

Yes the problem is we have no way yet to know ruby-2.0 is an upgrade of ruby-1.9

pkg 1.4 will know that.
So it will be fixed automagically by pkg 1.4

regards,
Bapt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20141020/120faa1d/attachment.sig>


More information about the freebsd-ports mailing list