On Sat, Mar 31, 2018 at 7:25 AM, David Wolfskill <da...@catwhisker.org> wrote:
> While the actual change to the Perl version works fine for me, I > find that invoking "pkg updating" fails to display the 20180330 > ports/UPDATING entry. I got lucky, because I found out about the > change a different way. > > I maintain /usr/ports as an SVN working copy, using a local private > mirror (updated nightly): > > g1-215(11.1-S)[1] svn info /usr/ports/ > Path: /usr/ports > Working Copy Root Path: /usr/ports > URL: file:///svn/freebsd/ports/head > Relative URL: ^/head > Repository Root: file:///svn/freebsd/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 466037 > Node Kind: directory > Schedule: normal > Last Changed Author: mandree > Last Changed Rev: 466037 > Last Changed Date: 2018-03-31 03:08:17 -0700 (Sat, 31 Mar 2018) > > g1-215(11.1-S)[2] > > > The 20180330 entry does exist in /usr/ports/UPDATIMG: > > g1-215(11.1-S)[2] grep -i -B 2 -A 2 perl /usr/ports/UPDATING | head > > 20180330: > AFFECTS: users of lang/perl5* > AUTHOR: m...@freebsd.org > > The default Perl version has been switched to Perl 5.26. If you are > using > binary packages to upgrade your system, you do not have anything to do, > pkg > upgrade will do the right thing. For the other people, follow the > -- > > g1-215(11.1-S)[3] > > > I have Perl installed: > > g1-215(11.1-S)[3] pkg info -o perl5\* > perl5-5.26.1 lang/perl5.26 > g1-215(11.1-S)[4] > > > But "pkg updating -i" fails to display the 20180330 entry for me; > it does show entries for some(?) other ports I have installed: > > g1-215(11.1-S)[4] pkg updating -i | head > 20180319: > AFFECTS: users of dns/dnsmasq > AUTHOR: mand...@freebsd.org > > Note that with dnsmasq 2.79, some parts of the interface have changed in > an > incompatible way versus previous versions. This comprises changed > recursion > behaviour, signature support, a change for SIGINT (vs. SIGHUP) behaviour. > > Note especially that dnsmasq will no longer answer non-recursive queries > unless it is marked authoritative! Be sure to see the manual page for > the > g1-215(11.1-S)[5] > > > Is the above a demostration of a problem with "pkg updating"? > Something else? > > Thanks! > > Peace, > david > -- > David H. Wolfskill da...@catwhisker.org > An investigator who doesn't make a perp nervous isn't doing his job. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. > I also don't see the perl message. The newest entry I see is: 20180214: AFFECTS: users of lang/ruby23 I have no installed ports with newer update messages installed. I suspect thre issue is the handing of the wildcard (lang/perl5*). Either it's a bug or wildcards should not be allowed in UPDATING. There are LOTS of entries with asterisks, though, ome rather more complex such as: 20180308: AFFECTS: */php* */pecl* */pear* BTW, that one should show up in "pkg updating -i" and does not, either. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 _______________________________________________ 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"