486824 – =sys-apps/portage-2.2.7 : repoman commit does not work properly

Bug 486824 - =sys-apps/portage-2.2.7 : repoman commit does not work properly

Summary: =sys-apps/portage-2.2.7 : repoman commit does not work properly

Status:	RESOLVED OBSOLETE

Alias:	None

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

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2013-10-02 19:08 UTC by Agostino Sarubbo
Modified:	2017-03-15 23:12 UTC (History)
CC List:	2 users (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 Agostino Sarubbo gentoo-dev

2013-10-02 19:08:58 UTC

It happened at least 2 times. I commit with repoman but the the result is digest verification failed.

It happened today with dev-php/smarty, as you can see here:
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-php/smarty/Manifest?view=log


Stable for x86, wrt bug #435618

(Portage version: 2.2.7/cvs/Linux x86_64, RepoMan options: --include-arches="x86", signed Manifest commit with key 7194459F)

So the error was not caused by cvs commit.

I see this problem since the last portage update.

Comment 1 Brian Dolbec (RETIRED) gentoo-dev

2017-03-15 22:52:51 UTC

I trust this bug is now obsolete or has been fixed?

Was this a CVS specific problem?

Comment 2 Zac Medico gentoo-dev

2017-03-15 23:12:40 UTC

Anything involving Manifest generation for CVS has to be obsolete now.