[gobolinux-users] Freshen couldn't better prepare update?

Daniele Maccari gobo.users at gmail.com
Mon Jul 16 09:20:53 UTC 2007


Michael Homer ha scritto:
> On 7/16/07, Daniele Maccari <gobo.users at gmail.com> wrote:
>   
>> Michael Homer ha scritto:
>>     
>>> On 7/15/07, rubisher <rubisher at scarlet.be> wrote:
>>>
>>>       
>>>> Michael Homer wrote:
>>>>
>>>>         
>>>>> On 7/15/07, rubisher <rubisher at scarlet.be> wrote:
>>>>>
>>>>>           
>>>>>> Hello Michael,
>>>>>>
>>>>>> 2 or 3 weeks ago I launch the upgrade of kde with:
>>>>>>
>>>>>> # Freshen -U KDE-Utils KDE-Libs KDE-PIM KDE-Graphics KDE-Multimedia
>>>>>>
>>>>>> (Freshen release 2.2.2-r1)
>>>>>>
>>>>>> Among dependencies there was new Xorg which is also a dependency of other kde's dependencies, I so stopped to count the
>>>>>> number of time Freshen asked me if I want to upgrade Xorg even thought I already accepted at the first time.
>>>>>>
>>>>>>             
>>>>> Freshen never asks you at all. Compile might, but it shouldn't if that
>>>>> version of X has already been installed. Which should have happened at
>>>>> the beginning of the Freshen run if it wasn't already met. If X failed
>>>>> to install at that point, that's the problem, and you should stop and
>>>>> see why.
>>>>>
>>>>>           
>>>> mmm, may be did I tell to skip it the first time Freshen put the question (I don't remember)?
>>>>
>>>>         
>>> It doesn't put the question. Compile might, but only if it isn't
>>> satisfied at that point, which it definitely should be.
>>>
>>>       
>>>>> What does just `Freshen  KDE-Utils KDE-Libs KDE-PIM
>>>>> KDE-Graphics KDE-Multimedia` give you?
>>>>>
>>>>>           
>>>> Well as far as kde 3.5.6 seems to be broken to me, I can revert this update and retry the operation.
>>>> I will come back as soon as I can with logs.
>>>>
>>>>         
>>> You don't need to compile, just give the output of that command.
>>> Freshen --debug might help too.
>>>
>>>       
>>>>> `ls -l /Programs/Xorg`?
>>>>>
>>>>>           
>>>> No pb:
>>>> # ls -l /Programs/Xorg/
>>>> total 12
>>>> drwxr-xr-x 9 Brother Brother 4096 2007-06-03 11:23 7.1
>>>> drwxrwxr-x 9 Brother Brother 4096 2007-04-07 20:31 7.2
>>>> lrwxrwxrwx 1 Brother Brother    3 2007-06-30 19:10 Current -> 7.2
>>>> drwxr-xr-x 3 Brother Brother 4096 2007-06-03 11:23 Settings
>>>> lrwxrwxrwx 1 Brother Brother   16 2007-06-03 14:51 Variable -> /System/Variable
>>>>
>>>>         
>>> So Xorg 7.2 is installed and symlinked properly... Freshen definitely
>>> won't try to install it, and Compile/InstallPackage shouldn't be
>>> trying either (plus, they're called with --no-dependencies, they
>>> shouldn't even be looking). That's puzzling. I think we'll need some
>>> more logs of what actually goes on to solve this.
>>> -Michael
>>> _______________________________________________
>>> gobolinux-users mailing list
>>> gobolinux-users at lists.gobolinux.org
>>> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
>>>
>>>
>>>       
>> I think there's a misunderstanding. What we (or at least I am) are
>> saying is that when updating a package and a dependecy update is needed
>> by more than one package (so the dependecy is not installed yet, that's
>> the point), every and each package which depends on it will ask for the
>> installation of the update, even if we already answer yes the first
>> time. For example:
>> xxx require xorg as a dependency: compile? yes
>> ...
>> ...
>> ...
>> yyy (which is a dependecy of xxx) require xorg as a dependency: compile? no
>>     
> Dependencies should be resolved before that point, and Compile's
> dependency-handling shouldn't ever be being used. That's why I want
> the output of plain `Freshen` to see how it's ordering things. Xorg
> should be listed ahead of everything that depends on it, or not at all
> if it's already up-to-date. If it's already up-to-date at the point
> something that requires it is Compiled, Compile should see that it's
> met and not try to install it again.
>
> Regardless of how they're ordered, Compile is explicitly instructed
> not to resolve dependencies, so it shouldn't be prompting you for it
> at all (it's both in --batch mode and with --no-dependencies). There
> may be a Compile bug making it ignore those flags, although I wasn't
> able to trigger it when I did a couple of experiments.
> -Michael
> _______________________________________________
> gobolinux-users mailing list
> gobolinux-users at lists.gobolinux.org
> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
>
>   
Well, I'll try a few experiments then. Hope this could help.

Bye.


More information about the gobolinux-users mailing list