661538 – sys-apps/portage

Bug 661538 - sys-apps/portage

Summary: sys-apps/portage

Status:	RESOLVED INVALID

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2018-07-18 16:54 UTC by Rick Farina (Zero_Chaos)
Modified:	2018-07-18 17:38 UTC (History)
CC List:	0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Rick Farina (Zero_Chaos) gentoo-dev

2018-07-18 16:54:35 UTC

items defined in /etc/portage/repos.conf/ are not attempted to be synced unless the gentoo repo is synced.  if /usr/portage/metadata/timestamp.chk is in sync for gentoo, then everything else in repos.conf is ignored.

at *least* for git repos they should be checked in the same manner as smart-live-rebuild, or just attempt to update all repos no matter what

Comment 1 Rick Farina (Zero_Chaos) gentoo-dev

2018-07-18 17:38:08 UTC

this bug is invalid, caused by me having the same repo defined multiple times and the winner had sync set to no