On Tue, Jun 28, 2016 at 04:44:33AM -0700, David Wolfskill wrote: > As part of my daily update of FreeBSD on my laptop, on the first reboot > after installing the freshly-built kernel & world, I use portmaster to > update any installed ports that have been updated since I last updated. > > This morning, for the first time in ... months, I think, the "pkg > updating -d ..." command I run to start the process actually generated > some output -- quite a bit of it. > > But I'm at a loss to understand why it did: only one of the ports it > mentioned is installed, and that one didn't get updated by "portmaster > -ad"; the others aren't installed at all. > > My ports working copy is ports/head, at r417708. > > I'm running: > FreeBSD g1-252.catwhisker.org 10.3-STABLE FreeBSD 10.3-STABLE #406 > r302244M/302246:1003505: Tue Jun 28 04:11:52 PDT 2016 > r...@g1-252.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY amd64 > > now; when I ran "pkg updating -d ...", I was running: > FreeBSD g1-252.catwhisker.org 10.3-STABLE FreeBSD 10.3-STABLE #405 > r302220M/302222:1003504: Mon Jun 27 04:03:47 PDT 2016 > r...@g1-252.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY amd64 > > and pkg reports: > g1-252(10.3-S)[2] pkg --version > 1.8.6 > > The "pkg updating" command I issued was: pkg updating -d 20160626
Hello David, I did replicate this and it seemed related to a handful of recent UDPATING entries that were made without a trailing colon after the date. I normalized all the entries for consistency and am seeing `pkg updating -d 20160626` return the expected output for me. Please see if that resolved the issue for you as well. Jason _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
