[gobolinux-users] Freshen 2.2.4

[Isaac Dupree]

Michael Homer wrote:
> I'm not on Gobo at the moment, so I can't test this out. However, it
> looks like one of two things: one, there's a bug in the version
> comparisons that makes 2.12q-r1<2.12r, or two, something requires
> <2.12r and the fact that it's displaying HAL is a bug (it's actually
> expected behaviour in that case, since it only shows exactly one
> program that's pulling something into the tree, and which it is
> doesn't matter).

Freshen does claim it's a downgrade, so unless Freshen contains multiple 
inconsistent version-comparison algorithms....

Anyway, if (for example) one package depended on Readline >= 4.0 < 5 and 
another on Readline >= 5.0, shouldn't Freshen install both versions? 
(and symlink both... I suppose resolving any symlink conflicts in favor 
of the newer version)


> It could be a package dependency file. They're in either
> /tmp/dependencies-* or /tmp/Freshen/dependencies-*, depending on how
> you have it set up. It's still odd behaviour all the same. If you
> delete all of them and run it again, do you get the same behaviour?

Only /tmp/dependencies-* existed, which were all empty, but I deleted 
them anyway.

Then it was somewhat painful.  Freshen seemed to hang with no CPU usage 
at lots of "Attempting to fetch package dependencies for ...", including 
installed packages for which there exists no corresponding recipe, as 
well as installed LocalRecipes. The first:

Freshen: Attempting to fetch recipe dependencies for LibIDL 0.8.8-r3
GetRecipe: Recipe for LibIDL 0.8.8-r3 not found
Freshen: Attempting to fetch package dependencies for LibIDL 0.8.8-r3

I pressed Ctrl-C for all these (I think no other times), and got the 
same bogus Util-Linux results.



>> P.S. sometimes Freshen's output glitches and repeats itself a bit such
>> as the following (not an exact quote, since I can't seem to reproduce it
>> right now. maybe a nasty multithreading/SMP problem(race condition?)?:
>>
>> Freshen: ;Freshen: Updating settingsUpdating settings...
> Freshen is single-threaded, so it at least shouldn't be a problem. I
> don't know where the semicolon could possibly come from, though.

I remember the semicolon is definitely there - I'll try to get a real 
example when I see one. Really wild guesses: Maybe it's the fault of 
some library Freshen uses, or something to do with shell scripts? Both 
Python and Ruby (at least) seem to be involved


Isaac