Re: [wpkg-users] Removing a dependency, removes all packages in the dependency chain
Rainer Meier r.me...@wpkg.org writes: Hi Stefan, Hello, [...] I will have a look at the logs you sent to me (I received them, thank you). I am going to handle this with medium priority as it seems not to be reproducible at the moment. Please inform me if you have a clear test case where this happens or if it happens again to you. I have the same problem here, with GTK2 and pidgin-2.6.6-no-gtk. I had: host: \- pidgin \- GTK2 With pidgin 2.7.0, there is no no-gtk version any more, so I remove the dependency in pidgin.xml and I have the following: --8---cut here---start-8--- ERROR : Command '%SOFTWARE%\pidgin\2.6.6\remove.cmd was unsuccessful.|Le chemin d'accE8s spE9cifiE9 est introuvable.| ERROR : Exit code returned non-successful value: -1|Package: Pidgin.|Command:|%SOFTWARE%\pidgin\2.6.6\remove.cmd ERROR : Could not process (remove) Pidgin.|Package still installed. ERROR : Removal of depending packages for 'GNOME Tool Kit' (gtk2) failed. Removal of depending package 'Pidgin' (pidgin) failed ERROR : Failed to remove package which depends on 'GNOME Tool Kit (gtk2), skipping removal.|You might use the /force flag to force removal but remember that the package depending on this on ERROR : Could not process (remove) GNOME Tool Kit.|Package still installed. --8---cut here---end---8--- My problem is that pidgin 2.6.6 is not available anymore since I distribute 2.7.0. Regards. -- Daniel Dehennin RAIP de l'Orne pgpgM0dInYlHb.pgp Description: PGP signature - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Removing a dependency, removes all packages in the dependency chain
Daniel Dehennin daniel.dehen...@ac-caen.fr writes: [...] I have the same problem here, with GTK2 and pidgin-2.6.6-no-gtk. I had: host: \- pidgin \- GTK2 With pidgin 2.7.0, there is no no-gtk version any more, so I remove the dependency in pidgin.xml and I have the following: [...] My problem is that pidgin 2.6.6 is not available anymore since I distribute 2.7.0. To be really clear, if a dependency is removed, it's normal to remove the depending package (it's not supposed to work without it's dependency), but it may not do so if this one is in upgrade (which may remove the dependency) ? Regards. -- Daniel Dehennin RAIP de l'Orne pgpyCEpunl0E8.pgp Description: PGP signature - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Removing a dependency, removes all packages in the dependency chain
Rainer Meier r.me...@wpkg.org writes: Hi Daniel, Hello, You are right. This might be the actual reason for the confusion. [...] I am sorry about this longish and probably chaotic message. I was thinking about possible ways to improve the situation for about an hour and continuously updated, dadded and deleted the message while I was trying to think about the whole impact of such a change. Unfortunately my conclusion finally was the statement above; I think the way WPKG is handling it currently might be unexpected but it makes sure the system state is consistently maintained at any point in time. Rainer, Being the initial poster, I am at a point, where I prefer the clean remove and reinstall, even, if all my clients have experienced this behavior. Delaying the removal instead of being the first action will cause more trouble, than reinstalling things. --- Stefan - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Removing a dependency, removes all packages in the dependency chain
Hi Daniel, On 08.06.2010 12:02, Daniel Dehennin wrote: I first test on my lab virtual machine, things happend like this: First run: - GTK2 could not uninstall pidgin 2.6.6, so GTK2 was not uninstalled - Pidgin was updated to 2.7.0 and does not depends on GTK2 any more. Second run: - GTK2 has no reverse dependency any more, so GTK2 was removed. Oh, right, so it's healing itself on second run. In case GTK could not be removed either since you removed GTK from the server too it should work as well. The reason is that WPKG would try to remove GTK and after failing it would recognize it as a zombie package and remove it from the package database anyway. Sure then GTK itself would remain on the machine but WPKG would not care about it any more. This was a near useless thread as the computers were not rebooted, so only one run of WPKG client was done :-/, so everything is working as expected in fact. Hmm, not really useless; it could have pointed to a real problem. So it's better to sort things out. I was really happy about your simple summary about Pidgin/GTK problem because it was very easy to trace what really happens. One good point about my noise is that now, we can cutpast you post, put it on the wiki and nobody will ask anymore ;-) Oh, probably not my chaotic message ;-) But feel free to add some wiki information. br, Rainer - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Removing a dependency, removes all packages in the dependency chain
Is this behavior by design or is there a way to skip removing, if the packages are still valid for the host? Well, WPKG is supposed to first create a complete list of packages assigned to the host (flat list). Then it does an upgrade to the latest package version on all these packages. Are you able to provide a sample of the three packages before the change and after the change - probably along with a full debug log? Hi Rainer, I have reapplied the dependency today and resynchronized my test machine, so that the JRE5 Remove package was installed. I have then reverted the dependency and synchronized once more, but this time removing the package did not result in any other package being removed too. How should we proceed, since this happened to all my testing machines? I do have a log file from yesterday, which does include the remove and reinstall. I will send it directly to you. --- Stefan - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Removing a dependency, removes all packages in the dependency chain
Hi Stefan, On 07.04.2010 17:48, Pendl Stefan wrote: I have reapplied the dependency today and resynchronized my test machine, so that the JRE5 Remove package was installed. I have then reverted the dependency and synchronized once more, but this time removing the package did not result in any other package being removed too. How should we proceed, since this happened to all my testing machines? I do have a log file from yesterday, which does include the remove and reinstall. I will send it directly to you. OK, something seems to be strange. I will have a look at the logs. Maybe something was mixed up in the local wpkg.xml of the hosts. Unfortunetely if there is no clear way to reproduce it it's hard to identify potential problems. I will have a look at the logs you sent to me (I received them, thank you). I am going to handle this with medium priority as it seems not to be reproducible at the moment. Please inform me if you have a clear test case where this happens or if it happens again to you. Thanks for the report anyway. Rainer - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Removing a dependency, removes all packages in the dependency chain
Hi Stefan, On 06.04.2010 17:27, Pendl Stefan wrote: I have just encountered a strange thing. Let's see how strange it is I have package3 depending on package2 and package2 depends on package1. OK, so you just assign package3 to the host? Which makes a chain then: host \- package3 \- package2 \- package1 Now I have considered package1 to be obsolete and removed the dependency between package2 and package1. This results in package2 and package3 being removed and reinstalled. So your dependency tree looks as follows: host \- package3 \- package2 In this case the packages WPKG evaluates which are assigned to the host should be the same except that package1 is not part of the list. WPKG works with a flat list of packages assigned to the host. I currently don't see any reason why package2 and pacakge3 should be removed by WPKG unless your dependency tree you outlined is reversed... like host \- package1 \- package2 \- package3 In this case removing the dependency between package1 - package2 would lead in removal of package2 and package3 since they do not apply to the host any more. However you say it's re-installed. I will have to create a testcase for this and try to reproduce this use-case. Should not be too difficult. Is this behavior by design or is there a way to skip removing, if the packages are still valid for the host? Well, WPKG is supposed to first create a complete list of packages assigned to the host (flat list). Then it does an upgrade to the latest package version on all these packages. Are you able to provide a sample of the three packages before the change and after the change - probably along with a full debug log? br, Rainer - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
