1 |
On Sat, 5 Sep 2015 12:50:22 -0700 |
2 |
Zac Medico <zmedico@g.o> wrote: |
3 |
|
4 |
> On 09/05/2015 09:18 AM, Zac Medico wrote: |
5 |
> > On 09/05/2015 09:16 AM, Brian Dolbec wrote: |
6 |
> >> On Sat, 5 Sep 2015 07:31:27 -0700 |
7 |
> >> Zac Medico <zmedico@g.o> wrote: |
8 |
> >> |
9 |
> >>> Unadded files that are excluded from the Manifest are safe to |
10 |
> >>> ignore. |
11 |
> >>> |
12 |
> >>> X-Gentoo-Bug: 559636 |
13 |
> >>> X-Gentoo-Bug-url: https://bugs.gentoo.org/show_bug.cgi?id=559636 |
14 |
> >>> --- |
15 |
> >>> [PATCH v2] fixes it to properly check the find_invalid_path_char |
16 |
> >>> return value bin/repoman | 6 +++++- |
17 |
> >>> 1 file changed, 5 insertions(+), 1 deletion(-) |
18 |
> >>> |
19 |
> >>> diff --git a/bin/repoman b/bin/repoman |
20 |
> >>> index 1ba7841..2c42c2d 100755 |
21 |
> >>> --- a/bin/repoman |
22 |
> >>> +++ b/bin/repoman |
23 |
> >>> @@ -2570,7 +2570,11 @@ else: |
24 |
> >>> if myunadded: |
25 |
> >>> for x in range(len(myunadded)-1, -1, -1): |
26 |
> >>> xs = myunadded[x].split("/") |
27 |
> >>> - if xs[-1] == "files": |
28 |
> >>> + if |
29 |
> >>> repo_config.find_invalid_path_char(myunadded[x]) != -1: |
30 |
> >>> + # The Manifest excludes this |
31 |
> >>> file, |
32 |
> >>> + # so it's safe to ignore. |
33 |
> >>> + del myunadded[x] |
34 |
> >>> + elif xs[-1] == "files": |
35 |
> >>> print("!!! files dir is not |
36 |
> >>> added! Please correct this.") sys.exit(-1) |
37 |
> >>> elif xs[-1] == "Manifest": |
38 |
> >> |
39 |
> >> uhg :( not another patch to "old" repoman code. |
40 |
> >> |
41 |
> >> I really want to get the rewrite code into portage master BEFORE |
42 |
> >> any more patches, or changes are applied. There has been enough |
43 |
> >> changes, that even the simplest small change can make it a rebase |
44 |
> >> nightmare. |
45 |
> >> |
46 |
> >> At this point, I will only accept patches on the rewrite |
47 |
> >> |
48 |
> > |
49 |
> > Fair enough. I'll just rebase the patch after the rewrite is merged. |
50 |
> > |
51 |
> |
52 |
> We could just keep all of the repoman patches in a special branch. |
53 |
> Then for each release, just do a 'git rebase master' in that branch, |
54 |
> and then tag the resulting branch head as a release. After the |
55 |
> rewrite is merged, I'll manually rebase them all on the rewrite. |
56 |
|
57 |
I doubt you will be able to do a git rebase of old code patches onto |
58 |
the new code. It is just way too different. most of the tests have |
59 |
been removed from the main file and put into individual files. |
60 |
|
61 |
You'll likely have to hand apply them and adapt to the new code at the |
62 |
same time. |
63 |
|
64 |
|
65 |
|
66 |
-- |
67 |
Brian Dolbec <dolsen> |