Bug 679040

Summary:	sys-apps/portage: Update git remote according to repos.conf
Product:	Portage Development	Reporter:	Nils Freydank <holgersson>
Component:	Enhancement/Feature Requests	Assignee:	Portage team <dev-portage>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	darkdexter, peter
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Nils Freydank 2019-02-28 10:31:39 UTC

Hi,

portage currently just calls git the first time it syncs. If you need to change the git remote URI afterwards you need to manually adjust it in $(portageq get_repo_path / gentoo
)/.git/config.

Instead the corresponding entry should be updated on every call of emerge --sync , maybe on other occasions I miss here aswell.


Reproducible: Always

Comment 1 Anthony Mendez 2023-11-01 03:14:03 UTC

Bumping this because I ran into the same issue.

The librewolf overlay changed hosts and I updated my repos.conf and moved on. I didn't realize this wouldn't also change the local repo so I went for 3 months without upgrading librewolf.

Due to the implications of not keeping critical programs like web browsers up to date I think this issue has some security implications.

Comment 2 John Helmert III archtester

2023-11-04 23:17:46 UTC

> Due to the implications of not keeping critical programs like web browsers up to date I think this issue has some security implications.

I agree that for this reason this issue is of some importance, but by this logic any dependency resolution issue should be treated as a security bug because someone somewhere could concievably not update something.

*** This bug has been marked as a duplicate of bug 905869 ***