Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 679040 - sys-apps/portage: Update git remote according to repos.conf
Summary: sys-apps/portage: Update git remote according to repos.conf
Status: RESOLVED DUPLICATE of bug 905869
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: Normal normal with 1 vote (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-28 10:31 UTC by Nils Freydank
Modified: 2023-11-04 23:17 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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 Gentoo Infrastructure gentoo-dev Security 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 ***