Date: Sat, 11 Oct 2014 15:54:52 +0200 From: Michelle Sullivan <michelle@sorbs.net> To: freebsd-ports@dan.me.uk Cc: freebsd-ports@freebsd.org Subject: Re: PKG not quite ready for prime time Message-ID: <543936AC.7030102@sorbs.net> In-Reply-To: <54393381.1000204@dan.me.uk> References: <sl4g3adpms8lkd2rr38n3666et8eptsp9i@4ax.com> <543817AA.8080305@gmx.de> <he6g3apojoln19fd9d8gr2rs0koq3a6940@4ax.com> <54381E16.9070609@FreeBSD.org> <1a8g3athvnun67c4kljhjtsjjlc30116j1@4ax.com> <543837CF.9070607@FreeBSD.org> <e79i3ale313b5iqvuql3ns08m86hmtonoa@4ax.com> <543931DB.7070205@sorbs.net> <54393381.1000204@dan.me.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel Austin via freebsd-ports wrote: > Hi, > > On 11/10/2014 14:34, Michelle Sullivan wrote: >> scratch65535@att.net wrote: >>>> You are missing this: >>>> https://www.freebsd.org/security/advisories/FreeBSD-EN-14:03.pkg.asc >>>> >>>> freebsd-update can provide it. >>>> >>> >>> Thank you for the pointer. >>> >>> What puzzles me is why the problem wasn't fixed for o/s versions >>> prior to 10.0 since it was being made mandatory for those >>> versions. That doesn't seem like good practice. >>> >> We have a winner! <3\ > > I've upgraded countless machines from 9.x to 10.x using freebsd-update > and have never come across this issue. (have done a few 8.x to 10.x > via 9.x and been fine too - but not many of these) > > What upgrade path did you use, what version did you come from, and > what version did you go to? Not talking about changing versions - talking about machines that are forced to use pkg that are not 10.x and the freebsd-update tool was used to patch the box at the same major version. Michelle -- Michelle Sullivan http://www.mhix.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?543936AC.7030102>