On Tue, 23 Dec 2014 11:05:30 +0100, Baptiste Daroussin <bapt at freebsd.org> wrote:> On Tue, Dec 23, 2014 at 08:25:36AM +0100, sthaug at nethelp.no wrote: >> > > Proceed with this action? [y/N]: y >> > > Fetching bash-4.3.30_1.txz: 100% 1 MB 1.2M/s 00:01 >> > > Fetching gettext-runtime-0.19.3.txz: 100% 144 KB 147.2k/s 00:01 >> > > Checking integrity...Assertion failed: (pkgdb_ensure_loaded(j->db, >> p2, PKG_LOAD_FILES|PKG_LOAD_DIRS) == EPKG_OK), function >> pkg_conflicts_need_conflict, file pkg_jobs_conflicts.c, line 211. >> > > Child process pid=4851 terminated abnormally: Abort trap >> ... >> > According to the 20141130 entry in /usr/ports/UPDATING, the gettext >> > port was split into 2 ports. One containing the libraries, and the >> > other the developer tools. >> > >> > See /usr/ports/UPDATING on how to fix this issue. >> >> Thanks, that got the issue fixed. >> >> For Christmas I wish for a more descriptive error message from pkg :-) >> > it has been fixed :) (better than a more descriptive error message no?) > > Best regards > BaptBut to know things like this, I have to have an updated ports tree on your system, because "pkg updating" doesn't have it's own copy of UPDATING somewhere. ( I thought it had until know ) So before "pkg upgrade" I'd have to update my ports tree to check UPDATING? Michael
On Tue, Dec 23, 2014 at 12:37:54PM +0100, Michael Ross wrote:> On Tue, 23 Dec 2014 11:05:30 +0100, Baptiste Daroussin <bapt at freebsd.org> > wrote: > > > On Tue, Dec 23, 2014 at 08:25:36AM +0100, sthaug at nethelp.no wrote: > >> > > Proceed with this action? [y/N]: y > >> > > Fetching bash-4.3.30_1.txz: 100% 1 MB 1.2M/s 00:01 > >> > > Fetching gettext-runtime-0.19.3.txz: 100% 144 KB 147.2k/s 00:01 > >> > > Checking integrity...Assertion failed: (pkgdb_ensure_loaded(j->db, > >> p2, PKG_LOAD_FILES|PKG_LOAD_DIRS) == EPKG_OK), function > >> pkg_conflicts_need_conflict, file pkg_jobs_conflicts.c, line 211. > >> > > Child process pid=4851 terminated abnormally: Abort trap > >> ... > >> > According to the 20141130 entry in /usr/ports/UPDATING, the gettext > >> > port was split into 2 ports. One containing the libraries, and the > >> > other the developer tools. > >> > > >> > See /usr/ports/UPDATING on how to fix this issue. > >> > >> Thanks, that got the issue fixed. > >> > >> For Christmas I wish for a more descriptive error message from pkg :-) > >> > > it has been fixed :) (better than a more descriptive error message no?) > > > > Best regards > > Bapt > > But to know things like this, > I have to have an updated ports tree on your system, > because "pkg updating" doesn't have it's own copy of UPDATING somewhere. > ( I thought it had until know ) > > So before "pkg upgrade" I'd have to update my ports tree to check UPDATING? >Nope UPDATING is 90% of the time useless with pkg since 1.4.x for the last 10% we plan to add a pkg news. (Still nothing done in that area) Best 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-stable/attachments/20141223/6a565019/attachment.sig>
On Tue, Dec 23, 2014 at 5:37 AM, Michael Ross <gmx at ross.cx> wrote:> On Tue, 23 Dec 2014 11:05:30 +0100, Baptiste Daroussin <bapt at freebsd.org> > wrote: > >> On Tue, Dec 23, 2014 at 08:25:36AM +0100, sthaug at nethelp.no wrote: >>> >>> > > Proceed with this action? [y/N]: y >>> > > Fetching bash-4.3.30_1.txz: 100% 1 MB 1.2M/s 00:01 >>> > > Fetching gettext-runtime-0.19.3.txz: 100% 144 KB 147.2k/s 00:01 >>> > > Checking integrity...Assertion failed: (pkgdb_ensure_loaded(j->db, >>> > > p2, PKG_LOAD_FILES|PKG_LOAD_DIRS) == EPKG_OK), function >>> > > pkg_conflicts_need_conflict, file pkg_jobs_conflicts.c, line 211. >>> > > Child process pid=4851 terminated abnormally: Abort trap >>> ... >>> > According to the 20141130 entry in /usr/ports/UPDATING, the gettext >>> > port was split into 2 ports. One containing the libraries, and the >>> > other the developer tools. >>> > >>> > See /usr/ports/UPDATING on how to fix this issue. >>> >>> Thanks, that got the issue fixed. >>> >>> For Christmas I wish for a more descriptive error message from pkg :-) >>> >> it has been fixed :) (better than a more descriptive error message no?) >> >> Best regards >> Bapt > > > But to know things like this, > I have to have an updated ports tree on your system, > because "pkg updating" doesn't have it's own copy of UPDATING somewhere. > ( I thought it had until know ) > > So before "pkg upgrade" I'd have to update my ports tree to check UPDATING? >You don't need to update your ports tree, instead use: http://svnweb.freebsd.org/ports/head/UPDATING to read the latest copy of UPDATING. -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised.