Date: Sat, 08 Jul 2023 00:12:33 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: maintainer-feedback requested: [Bug 272420] ports-mgmt/pkg: pkg-1.20.1_1 ssh:// repos no longer working Message-ID: <bug-272420-32340-Uy3ny8mxhm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-272420-32340@https.bugs.freebsd.org/bugzilla/> References: <bug-272420-32340@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-pkg (Nobody) <pkg@FreeBSD.org> for maintainer-feedback: Bug 272420: ports-mgmt/pkg: pkg-1.20.1_1 ssh:// repos no longer working https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272420 --- Description --- After updating pkg, ssh:// repositories stopped working. Typical output (username, host and path removed for privacy reasons) doas pkg upgrade Updating custom repository catalogue... pkg: Invalid url: 'ssh://user@host/path/to/packages/meta.conf' pkg: Invalid url: 'ssh://user@host/path/to/packages/meta.txz' repository custom has no meta file, using default settings pkg: Invalid url: 'ssh://user@host/path/to/packages/packagesite.pkg' pkg: Invalid url: 'ssh://user@host/path/to/packages/packagesite.txz' Unable to update repository custom Error updating repositories! Error messages are incorrect because I was able to update seconds before. Has ssh:// been silently depreciated? I ask this because I recall some simi= lar behaviour when another url scheme was depreciated without any end user notifications.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272420-32340-Uy3ny8mxhm>