Re: pkg_add not working
--vA66WO2vHvL/CRSR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Apr 17, 2013 at 08:59:25PM -0700, Mehmet Erol Sanliturk wrote:
> On Wed, Apr 17, 2013 at 8:49 PM, Neel Natu <neelnatu@gmail.com> wrote:
>=20
> > Hi,
> >
> > I am running HEAD and recently started getting errors on pkg_add.
> >
> > uname: 10.0-CURRENT FreeBSD 10.0-CURRENT #103 r249396M: Thu Apr 11 23:2=
5:06
> > PDT 2013
> >
> > > pkg_add -r sudo
> > Error: Unable to get
> >
> > ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-10-current/Lates=
t/sudo.tbz
> > :
> > File unavailable (e.g., file not found, no access)
> > pkg_add: unable to fetch '
> >
> > ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-10-current/Lates=
t/sudo.tbz
> > '
> > by URL
> >
> > This used to work pretty well until a few days ago. Any clues?
> >
> > best
> > Neel
> >
>=20
>=20
> The "packages-10-current<ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/pa=
ckages-10-current/Latest/sudo.tbz>"
> is deleted from
>=20
> ftp://ftp1.freebsd.org/pub/FreeBSD/ports/amd64/
>=20
>=20
> It seems that , it will be reconstructed from scratch .
>=20
>=20
There is high probabilty that it won't, pkg_add is deprecated, and current =
has
switch to pkgng by default for a while now. given we have to rebuild all the
packages from scratch, there is a very high level of chance only the one
respecting the default will be built now (meaning pkgng)
regards,
Bapt
--vA66WO2vHvL/CRSR
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
iEYEARECAAYFAlFvlNEACgkQ8kTtMUmk6Ezo7ACgvFt14dLTLLYdDdj2qAmcSUi7
im8AoLDPM+lR6pkjN/p6yDGFDcoEeBd0
=6vkB
-----END PGP SIGNATURE-----
--vA66WO2vHvL/CRSR--
討論串 (同標題文章)