Gentoo Archives: gentoo-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] latest commits to dev-lang/go
Date: Wed, 16 May 2012 04:10:24
Message-Id: 4FB32861.6050001@gentoo.org
In Reply to: Re: [gentoo-dev] latest commits to dev-lang/go by William Hubbs
1 On 05/15/2012 08:54 PM, William Hubbs wrote:
2 > On Tue, May 15, 2012 at 10:15:28PM -0400, Matt Turner wrote:
3 >> On Tue, May 15, 2012 at 9:07 PM, William Hubbs <williamh@g.o> wrote:
4 >>> On Tue, May 15, 2012 at 06:37:39PM -0500, William Hubbs wrote:
5 >>>> All,
6 >>>>
7 >>>> I know my latest commits to dev-lang/go haven't updated the ChangeLog.
8 >>>>
9 >>>> I got into the habbit of using repoman commit -[Mm] to do that, but for
10 >>>> some reason that stopped working.
11 >>>>
12 >>>> I will use echangelog from this ponit until I hear that repoman commit
13 >>>> has been fixed.
14 >>>
15 >>> Thanks to Zac's quick assistance on irc, I found that this was an issue
16 >>> with my repository, not repoman.
17 >>>
18 >>> William
19 >>>
20 >>
21 >> So that others don't have the same problem -- what was the issue?
22 >
23 > it had to do with the timestamp of the ChangeLog file being wrong. I just
24 > fixed it by doing
25 >
26 > cvs up ChangeLog
27 >
28 > while I was in the dev-lang/go directory in my cvs checkout of the
29 > portage repo.
30 >
31 > William
32
33 To explain in some more depth:
34
35 If the ChangeLog timestamp differs from the one that's recorded in
36 CVS/Entries, then repoman thinks you've modified the ChangeLog manually
37 (or with echangelog), and it assumes that it shouldn't try to generate
38 an entry. You can use repoman --echangelog=force to force repoman to
39 generate a ChangeLog entry in this case.
40 --
41 Thanks,
42 Zac