Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 576282 - sys-apps/portage-2.2.27: emerge --sync returns exit code 0 when repo arguments are given, and sync-type is unset
Summary: sys-apps/portage-2.2.27: emerge --sync returns exit code 0 when repo argument...
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: All All
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 240187 611328
  Show dependency tree
 
Reported: 2016-03-02 20:33 UTC by Zac Medico
Modified: 2017-05-20 18:02 UTC (History)
1 user (show)

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 Zac Medico gentoo-dev 2016-03-02 20:33:00 UTC 
When emerge --sync is given repo arguments, and sync-type is not set for any of those repos, then emerge returns exit code 0 though it doesn't sync anything:

https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/emaint/modules/sync/sync.py?h=v2.2.27#n178
Comment 1 Alexandru Elisei 2017-02-01 20:07:00 UTC 
What should be the behavior when doing emerge --sync (or emaint sync -a) and no auto-sync repos are defined (for whatever reason)? Exit with success or failure?
Comment 2 Zac Medico gentoo-dev 2017-02-01 20:12:25 UTC 
(In reply to Alexandru Elisei from comment #1)
> What should be the behavior when doing emerge --sync (or emaint sync -a) and
> no auto-sync repos are defined (for whatever reason)? Exit with success or
> failure?

Let's exit with success in that case.
Comment 3 Zac Medico gentoo-dev 2017-05-20 18:02:14 UTC 
Fixed in portage-2.3.4, and portage-2.3.5 is stable now.

https://gitweb.gentoo.org/proj/portage.git/commit/?id=79103f99799c9365389290e812213c46e006c019