On Thu, Jan 3, 2013 at 5:23 AM, Zac Medico zmed...@gentoo.org wrote:
The CVS keyword expansion causes the ebuild digest to mutate during the
commit. If we repoman could predict correctly emulate the CVS keywords
expansion on the client side, then it could generate a correct Manifest
in
On 01/08/2013 11:24 PM, Douglas Freed wrote:
On Thu, Jan 3, 2013 at 5:23 AM, Zac Medico zmed...@gentoo.org wrote:
The CVS keyword expansion causes the ebuild digest to mutate during the
commit. If we repoman could predict correctly emulate the CVS keywords
expansion on the client side, then it
On 01/08/2013 11:36 PM, Zac Medico wrote:
On 01/08/2013 11:24 PM, Douglas Freed wrote:
On Thu, Jan 3, 2013 at 5:23 AM, Zac Medico zmed...@gentoo.org wrote:
The CVS keyword expansion causes the ebuild digest to mutate during the
commit. If we repoman could predict correctly emulate the CVS
In latest portage tree snapshot:
* Digest verification failed:
*
/usr/portage/dev-libs/gobject-introspection/gobject-introspection-1.34.2-r1.ebuild
* Reason: Filesize does not match recorded size
* Got: 2598
* Expected: 2582
The problem is that the directory was apparently included into
On Thu, Jan 3, 2013 at 10:46 AM, Maxim Kammerer m...@dee.su wrote:
The problem is that the directory was apparently included into daily
snapshot between 00:31:07 UTC (ebuild commit) and 00:31:13 UTC
(Manifest commit). For those that don't remember, CVS does not have
atomic commits, so it's not
On 01/03/2013 02:09 AM, Dirkjan Ochtman wrote:
In any case, we probably shouldn't spend a whole lot of effort on this
given the somewhat-impending git migration, which neatly solves this
problem. Maybe there's some low-hanging fruit in the commit ordering,
though? I was thinking it might be
