Date: Fri, 29 Nov 2013 07:45:29 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-current@freebsd.org Subject: Re: problems with pkg2ng Message-ID: <52984619.6080302@infracaninophile.co.uk> In-Reply-To: <20131129015446.M75652@i805.com.br> References: <20131129015446.M75652@i805.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xiukXLIGScAVdXoeSjeg8qWqI0dKJ9d18 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 29/11/2013 02:02, Nilton Jose Rizzo wrote: > in the near past, when I update ports repository via svn, I always= use > pkg2ng to upgrade (or update?) the database, but today I can not do it= =2E Uh? pkg2ng is a one time thing. Its only use is when converting a system that had previously used pkg_tools to pkg(8). That happens once, and after that, you never need it again. > The command pkg2ng show this error message: >=20 > root@valfenda:/home2/rizzo # pkg2ng > pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository > configuration file > Converting packages from /var/db/pkg > pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository > configuration file > pkg: fstat() failed for(/usr/local/etc/cups/cupsd.conf.N): No such file= or > directory This is not pkg2ng specific, but comes from the underlying calls to various pkg(8) actions. As it says, the format of pkg.conf has changed with this update, and it is instructing you on how to modify your pkg.conf so it conforms to the new norms. See pkg.conf(5) for details on creating a repository configuration file. The fstat() message is a different thing again -- looks like one of the files owned by the cups port has been deleted. You can fix that by forcing a reinstall of that package, but it's pretty innocuous really. > but when I search in /usr/ports/UPDATING I can not found anything about= this > and no man pages about pkg2ng=20 A lot of people seem confused and/or alarmed by this update. Yes, there have been a number of problems reported, which are being dealt with. Whether this warrants an entry in UPDATING I don't know, but the general tenor of any such entry would be "modify your configuration files as shown in the output of pkg(8)." No, there isn't a man page for pkg2ng. It was never thought necessary. However, if anyone wants to contribute a page for pkg2ng I'm sure it would be gratefully received. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matthew@infracaninophile.co.uk --xiukXLIGScAVdXoeSjeg8qWqI0dKJ9d18 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQJ8BAEBCgBmBQJSmEYgXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATKPUP/R1DccACHc9WthNveeJG/cg2 r6VoLDuPnUSMxScuCtGdM6IaRXQ4kFy1WpLF2thZ5Bj74YyvFOfp5WHu1nfPk1Wg 8ESPx6WPscP8Li+deG7x/9N3A1mCsgW8GdCGYYVmAPezGL8+IlcrCpNZPvMt+vVg GiioGSApDIl+HEctZ6NgzAvjZkyI/jmVbQwI4cJ+TbJBf3113PwGnglXWMy7dm91 LCCxEPu+LAUrpPuEGeLmqpzudcmjDi6sMWnxnOJO4tLHto2HljJdERFbPUPyGcHf utH006skgfc8IMXSiEz4vF7TjFSXpvWBMoXXffZGIIschpvA6Vu7o2JwkYzSi7bj FzN4on9y4U7QvMZNpidm0JAAUMP7YHLCxYivQ+0pfn0drk/ycYXMzHC+Cuyg8bbb j/TqoKsdcDfjXM2aZLVo1rt3wXw/uLtxPBhJcybFodpRJpNS0XKTA+5E+zlPZHEf p60EakYtybQzLq4EeRWB0n8+sqVG3XgqvB2bsD+Ljeav4hCYZhSTSkIlyjQxOSXD F4Zx1Oskj77FhDwFBnGHQQsGoLoKWojkd0aajGcmZLpG/nvaJbAWYPQnTnSHNriS 6xRCH2+rHcd0HxqprtZgj8X2RFYIXD61HoVX2oEf64Xw5eZ0IwScSPQFrto5wBCE swzV+Xc1+A3CLaeZBOUq =ukE+ -----END PGP SIGNATURE----- --xiukXLIGScAVdXoeSjeg8qWqI0dKJ9d18--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52984619.6080302>