| 1 |
It looks like it is just the dev-python/Babel ebuild as far as I can see.
|
| 2 |
I used to be happy on a case insensitive file system myself but
|
| 3 |
I have the above as a dependency of something else and this is fun:
|
| 4 |
|
| 5 |
fbissey@Mirage ~/Gentoo $ emerge -puDNv dev-python/babel
|
| 6 |
|
| 7 |
These are the packages that would be merged, in order:
|
| 8 |
|
| 9 |
Calculating dependencies... done!
|
| 10 |
|
| 11 |
emerge: there are no ebuilds to satisfy "dev-python/babel".
|
| 12 |
|
| 13 |
emerge: searching for similar names...
|
| 14 |
emerge: Maybe you meant any of these: dev-python/Babel, dev-python/babelfish, dev-python/blz?
|
| 15 |
fbissey@Mirage ~/Gentoo $ emerge -puDNv dev-python/Babel
|
| 16 |
|
| 17 |
These are the packages that would be merged, in order:
|
| 18 |
|
| 19 |
Calculating dependencies... done!
|
| 20 |
|
| 21 |
emerge: there are no ebuilds to satisfy "dev-python/Babel".
|
| 22 |
|
| 23 |
emerge: searching for similar names...
|
| 24 |
emerge: Maybe you meant any of these: dev-python/babelfish, dev-python/blz, dev-python/tablib?
|
| 25 |
|
| 26 |
There is a loose policy, as far as I remember to avoid capital in
|
| 27 |
package names as much as possible (stuff like dev-lang/R being case
|
| 28 |
where you usually want capital). I am not entirely clear what it is in
|
| 29 |
Babel that breaks things though, there must be something more than
|
| 30 |
capitalisation.
|
| 31 |
|
| 32 |
François
|
| 33 |
|
| 34 |
> On 19/05/2015, at 12:03, Gibson, John <jgibson@×××××.org> wrote: |
| 35 |
> |
| 36 |
> On May 18, 2015, at 19:07, yegle <cnyegle@×××××.com> wrote: |
| 37 |
>> |
| 38 |
>> On Mon, May 18, 2015 at 2:13 AM, Konstantin Tokarev <annulen@××××××.ru> wrote: |
| 39 |
>>> You should create case-sensitive partition and move your prefix there. |
| 40 |
>> |
| 41 |
>> If this is a requirement of using Gentoo Prefix then yes I should |
| 42 |
>> start with a case-sensitive partition. But looks like this is not the |
| 43 |
>> case, at least I cannot find it in the bootstrap guide etc. |
| 44 |
>> |
| 45 |
>> I've been using Gentoo Prefix on a case-insensitive FS (blame Apple |
| 46 |
>> for the default) for 5 years without a problem, and the rsync problem |
| 47 |
>> appeared in recent weeks. |
| 48 |
>> |
| 49 |
>> So I'm looking for anyone who can confirm that there's a problem |
| 50 |
>> syncing and the problem tie to a case-insensitive FS. Then, either |
| 51 |
>> declare that Gentoo Prefix require a case-sensitive FS and everyone |
| 52 |
>> should migrate their existing prefix, or fix the problem by |
| 53 |
>> remove/rename the offending file in portage tree. |
| 54 |
>> |
| 55 |
>> -- |
| 56 |
>> yegle |
| 57 |
>> http://about.me/yegle |
| 58 |
>> |
| 59 |
> |
| 60 |
> I've been using Prefix since at least 2008 and it does require a case-sensitive file system, however as Fabian said way back then: |
| 61 |
>> I'm running on case-insensitive filesystem too, and the problems |
| 62 |
>> currently are very very very limited. So just go for it and forget |
| 63 |
>> about it, until you start to hit weird errors ;) |
| 64 |
>> |
| 65 |
> See this thread for details: |
| 66 |
> |
| 67 |
> https://www.mail-archive.com/gentoo-alt%40lists.gentoo.org/msg03694.html |
| 68 |
> |
| 69 |
> Changing the tree to support case-insensitve file systems may not be possible. AFAIK that the Prefix tree is really just the main Gentoo tree at this point, and because the main tree originated on Linux it assumes case sensitivity. |
| 70 |
> |
| 71 |
> I run my prefix out of a case-insensitive sparse bundle and haven't seen the problem. |
| 72 |
> |
| 73 |
> John |
| 74 |
> |
Archives