Date: Sat, 08 Jul 2023 00:12:33 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 272420] ports-mgmt/pkg: pkg-1.20.1_1 ssh:// repos no longer working Message-ID: <bug-272420-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272420 Bug ID: 272420 Summary: ports-mgmt/pkg: pkg-1.20.1_1 ssh:// repos no longer working Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: pkg@FreeBSD.org Reporter: freebsd-bugs@micallef.io Assignee: pkg@FreeBSD.org Flags: maintainer-feedback?(pkg@FreeBSD.org) 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. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272420-7788>