Gentoo Archives: gentoo-portage-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] [PATCH v2] repoman: ignore unadded files when possible (bug 559636)
Date: Sat, 05 Sep 2015 19:50:30
Message-Id: 55EB477E.6090804@gentoo.org
In Reply to: Re: [gentoo-portage-dev] [PATCH v2] repoman: ignore unadded files when possible (bug 559636) by Zac Medico
1 On 09/05/2015 09:18 AM, Zac Medico wrote:
2 > On 09/05/2015 09:16 AM, Brian Dolbec wrote:
3 >> On Sat, 5 Sep 2015 07:31:27 -0700
4 >> Zac Medico <zmedico@g.o> wrote:
5 >>
6 >>> Unadded files that are excluded from the Manifest are safe to ignore.
7 >>>
8 >>> X-Gentoo-Bug: 559636
9 >>> X-Gentoo-Bug-url: https://bugs.gentoo.org/show_bug.cgi?id=559636
10 >>> ---
11 >>> [PATCH v2] fixes it to properly check the find_invalid_path_char
12 >>> return value bin/repoman | 6 +++++-
13 >>> 1 file changed, 5 insertions(+), 1 deletion(-)
14 >>>
15 >>> diff --git a/bin/repoman b/bin/repoman
16 >>> index 1ba7841..2c42c2d 100755
17 >>> --- a/bin/repoman
18 >>> +++ b/bin/repoman
19 >>> @@ -2570,7 +2570,11 @@ else:
20 >>> if myunadded:
21 >>> for x in range(len(myunadded)-1, -1, -1):
22 >>> xs = myunadded[x].split("/")
23 >>> - if xs[-1] == "files":
24 >>> + if
25 >>> repo_config.find_invalid_path_char(myunadded[x]) != -1:
26 >>> + # The Manifest excludes this file,
27 >>> + # so it's safe to ignore.
28 >>> + del myunadded[x]
29 >>> + elif xs[-1] == "files":
30 >>> print("!!! files dir is not added!
31 >>> Please correct this.") sys.exit(-1)
32 >>> elif xs[-1] == "Manifest":
33 >>
34 >> uhg :( not another patch to "old" repoman code.
35 >>
36 >> I really want to get the rewrite code into portage master BEFORE any
37 >> more patches, or changes are applied. There has been enough changes,
38 >> that even the simplest small change can make it a rebase nightmare.
39 >>
40 >> At this point, I will only accept patches on the rewrite
41 >>
42 >
43 > Fair enough. I'll just rebase the patch after the rewrite is merged.
44 >
45
46 We could just keep all of the repoman patches in a special branch. Then
47 for each release, just do a 'git rebase master' in that branch, and then
48 tag the resulting branch head as a release. After the rewrite is merged,
49 I'll manually rebase them all on the rewrite.
50 --
51 Thanks,
52 Zac

Replies