[wpkg-users] Negative Dependency
Hi there Is there a way to specify a negative dependency in the package definition i want to say: if package XY is found (installed), then do not even try to install this package, just wait to wpkg to remove the other package, try again on next reboot can we do something like that? Best Regards - 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] Negative Dependency
El vie, 26-10-2012 a las 20:56 +0200, Stefan Pendl escribió: Am 26.10.2012 20:43, schrieb Geoff Brown: Reposted from Stefan (as an example): '---code start (watch for line wraps) package id=Java name=Java revision=2011.10.22 reboot=false priority=10 execute=once include package-id=JRE6 os=5\.0\.\d{4}/ include package-id=JRE7 condition check type=logical condition=not check type=host condition=os value=5\.0\.\d{4}/ /check /condition /include /package '---code end You may want to use a uninstall check for applications. '---code start (watch for line wraps) depends package-id=LibreOffice condition check type=logical condition=not check type=uninstall condition=exists path=Microsoft Office .* / /check /condition /depends '---code end -- Thank you guys but it's not exactly what i mean... As i can see you are saying: 'this package depends on libreoffice unless msoffice is installed' to be fair, i'm a Debian user since 1998, even before to start administering windows networks, so i'm taking this dependencies schema with the schema of Debian's package dependencies on my mind, and to have all of those dependencies resolved, i think we need more types of package dependencies; i cannot find the functionality i'm looking for. See http://wpkg.org/Package_dependencies We can define only three relationships between packages: * depend - depends the current package to another specified package. * chain - chains another specified package to this package. * include - includes another specified package in the overall WPKG process. And now see: http://www.debian.org/doc/debian-policy/ch-relationships.html There we have: * Depends (include in wpkg) * Pre-Depends (depends in wpkg) I can live without * Recommends, Suggests, Enhances can be obviated in wpkg logic * Breaks: Packages which break other packages But i miss, or it would be great to have: * Conflicts: Conflicting binary packages (libreoffice conflicts Apache openoffice) * Provides: Virtual packages (example: libreoffice and msoffice provides 'office_suite', any package depending on 'office_suite' have it's dependencies ok if they have any of those suites installed) * Replaces: Overwriting files and replacing packages (libreoffice replaces msoffice (and provides it too)) What i was asking for in my first email was something like 'conflicts', but Provides and Replaces can be very usefull too... I cannot find this functionality in wpkg.js is it there and i'm just missing how to get it? Best Regards - 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] Negative Dependency
El vie, 26-10-2012 a las 21:37 +0200, Stefan Pendl escribió: Am 26.10.2012 21:26, schrieb Carlos R. Pasqualini: Thank you guys but it's not exactly what i mean... As i can see you are saying: 'this package depends on libreoffice unless msoffice is installed' If MS Office is removed, then Libre Office is installed, that was what you asked. yes, but you put it on another package's dependencies... i want a way to say 'libreoffice conflicts with msoffice' in the libreoffice package definition, and 'msoffice conflicts with libreoffice' on the msoffice definition. I don't think we need to make things more complicated, I have always succeeded using the current available dependencies. I agree with you on simple and clean dependencies schema, but at least to me, not every time i can express the dependencies as i think them. Remove the package from the profile of the host and it gets removed, any other package being blocked by that package will be installed afterwards. I don't think one should create complex dependency constructs for software deployment. what if i make a mistake when i'm selecting packages in the profile and selecting two conflicting packages? (very possible when we have profiles dependencies specified on different files). Having a conflict statement on the package definition level will reduce having troubles on user's machines. Assign what is needed to the host and allow installation of additional required software through dependencies, that is simple and supported. I think i'll need re-think all this issue again... may be it's just a debianism in my head limiting my think capacity Best Regards - 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] Notifications of Flash and Java updates
El mié, 24-10-2012 a las 17:27 +0100, Pete Boyd escribió: NEW=`wget -q $URL -O - | grep 'Flash Player' |grep -m 1 '/h3'|awk '{gsub(/h3,,$0);print $3}'` Y'all don't read FilleHippo then? I didn't know about that site, it seems good How do you use filehippo.com to get updates on your mail about the packages you are interested in?? Thanks - 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] Notifications of Flash and Java updates
El mar, 23-10-2012 a las 13:19 -0800, Lonney escribió: Hi, Does anyone know of a service or system that will send an email to notify of when new versions of Flash and Java available ? I'm using linux on my network whenever i can, so I’ve made a script that i run with a cronjob: flash.sh: - #!/bin/bash LASTF='/path/to/check_wpkg/flash.last' LAST=`cat $LASTF` URL='http://www.adobe.com/products/flashplayer/distribution3.html' NEW=`wget -q $URL -O - | grep 'Flash Player' |grep -m 1 '/h3'|awk '{gsub(/h3,,$0);print $3}'` if [[ $NEW != $LAST ]]; then echo -e difd\nNew: $NEW Vs. $LAST\n URL: $URL|\ mail -s [WPKG] New Flash Player $NEW \ user@email echo -n $NEW $LASTF fi - the filter line is what i change for every package (there are some spanish, because i live in Argentina, you should adapt them to your Language): 7zip.sh:NEW=`wget -q $URL -O - |grep Download 7-Zip|grep for Windows|awk '{gsub(PBDownload 7-Zip ,,$0);gsub( for Windows/B:/P,$0); print $1}'` avg.sh:NEW=`wget -q $URL -O - | grep 'http://download.avgfree.com/filedir/inst/avg_free_x64_all_'|awk -F 'http://download.avgfree.com/filedir/inst/avg_free_x64_all_' '{print $2}'|awk -F '.exe' '{print $1}' ` firefox.sh:NEW=`wget -q $URL -O - | grep -m 1 curVersion |awk '{gsub(td class=\curVersion\ ,,$0);gsub(/td,,$0); print $1}'` flash.sh:NEW=`wget -q $URL -O - | grep 'Flash Player' |grep -m 1 '/h3'|awk '{gsub(/h3,,$0);print $3}'` java6.sh:NEW=`wget -q http://www.java.com/es/download/manual.jsp -O - | grep Recomendado |awk '{gsub(strongRecomendado Version ,, $0);gsub(/strong,,$0);gsub( Update ,u,$0);print $1}'` libo.sh:NEW=`wget -q $URL -O - | grep -m 1 'lia href=/download/' | awk -F '' '{gsub(/a,,$0);print $3}'` vlc.sh:NEW=`wget -q $URL -O - |grep 'Download latest VLC -'| awk '{gsub(h1Download latest VLC - ,,$0);gsub(/h2,,$0);print $1}'` Maybe it's not the very best solution, but it works great for my needs Best Regards Charly - 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] Why VNC and not remote desktop? (was: Advice on remote assistance program to deploy)
El mar, 02-10-2012 a las 18:29 +0200, heiko.hel...@horiba.com escribió: i would like to know why you install another program on windows if you have RemoteDesktop on windows and an excelente client on linux? I've made a special CD for installing XP, and it set's by default the remote access option. I combine it plus Wake on Lan capabilities and works great here... * For you to login to XP via RDP it requires the user in front of the PC to log out. * During your session the user will only see the login screen. This means - you can't troubleshoot a user problem with the user showing you what went wrong - you dismiss possible error screens that you were supposed to look at (not every user is able to mail you a screenshot - especially if mail isn't working ) I know there's remote assistance available via the windows help menu - we tried that (because it's free!) but though it works pretty well once established, most times establishing the connection fails. And for non-expert users, it's still a bit complicated. We used UltraVNCs QuickSupport tool for quite a while, but that needs a ton of bandwidth and crashes a lot. Now we're a happy TeamViewer customer. It just works, that's really really cool. I'm on an University, so Teamviewer is not an option (i can't rely on such a service by security policy). The way to support the user when they are actually using their desktops it's a very good argument i would like to test. As i can see, if we choose to not use RDP nor Teamviewer/Logmein/etc. we have left only VNC. ¿which one do you recommends to do this job? ¿is there a way to authenticate with DSA/RSA or the like? Thanks! - 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] Why VNC and not remote desktop? (was: Advice on remote assistance program to deploy)
El lun, 01-10-2012 a las 10:52 +0200, Marco Cunico escribió: Hi guys i would like to know why you install another program on windows if you have RemoteDesktop on windows and an excelente client on linux? I've made a special CD for installing XP, and it set's by default the remote access option. I combine it plus Wake on Lan capabilities and works great here... may be you have a different use case and can share with us your experience. Thanks! - 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] Office 2010 Windows XP...
El mar, 18-09-2012 a las 15:11 +1000, Jon Rhoades escribió: Hi, We've been happily installing Office 2010 on Windows 7 for some time now. Unfortunately against my better judgment we need to install it on 30 or so Windows XP machines. I'm using the same package file, but with a new customised msp adminfile however the %comspec% /C start /WAIT fails to halt the progression of WPKG so the Office installer runs in parallel with other installs and obviously fails to install. When I run WPKG manually from the command line I can see that the Office splash screen is spawned and the silent (ha!) installation occurs. My solution has been to set it as priority=0 so that it installs last without the possibility of interference. IS this a Windows XP issues that it doesn't honor the start /wait option? Cheers Jon xpOffice2010.xml: ?xml version=1.0 encoding=UTF-8? packages package id=xpOffice2010 name=OBI Microsoft Office 2010 revision=1 reboot=false priority=0 check type=uninstall condition=exists path=Microsoft Office Standard 2010 / install cmd='%comspec% /C start /WAIT %SOFTWARE%\office \Office2010-MAK-SP1\setup.exe /adminfile %SOFTWARE%\office\obi.MSP' exit code=1641 / exit code=3010 / /install install cmd='%SYSTEMROOT%\system32\cscript C:\Program Files\Microsoft Office\Office14\OSPP.VBS /act'/ upgrade include=install / /package /packages Hi, i'm not installing (yet) msoffice 2010, but i'm installing Office2007 and visio2010 on XP systems and not using start /wait: Visio: install cmd='%PKG_DIR%\SETUP.EXE /adminfile %PKG_DIR% \visio2010.msp /config %PKG_DIR%\conf-fcal.xml' / Office2007: install cmd='%PKG_SETUP% /config %SOFTWARE%\Microsoft\Office\2007 \config_fcal.xml' exit code=1641 reboot=delayed/ /install It works great on win XP trough 7 (even on 7-64bits) on the other side: are you sure you are using the right command? i don't understand why: install cmd='%comspec% /C start /WAIT %SOFTWARE%\office Office2010-MAK-SP1\setup.exe /adminfile %SOFTWARE%\office\obi.MSP' and not: install cmd='%comspec% /C start /WAIT %SOFTWARE%\office Office2010-MAK-SP1\setup.exe /adminfile %SOFTWARE%\office\obi.MSP' (why after /start ?) may be i'm wrong on this last suggestion Best Regards - 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] packages not installing/upgrading
El jue, 13-09-2012 a las 07:42 +0200, Stefan Pendl escribió: Am 12.09.2012 22:07, schrieb Carlos R. Pasqualini: What does the number after the hyphen mean in your version number? x.y.z-a ... what means a? i reserve the last value for reviews of the .xml file with the same version of the installer. suppose i have a 1.2.3 version of the package, i'll create a 1.2.3-0 revision of the xml, and if i found something wrong in the XML file, i can create 1.2.3-1 ... 1.2.3-9 without having trouble with the possibly upcoming version 1.2.4 of the package. It's just used by me. ¿do you think it's bad to do that? I have done so in the past too, but am now adding the additional version part with a dot, since the hyphen gave me some unexpected results. OK! i will take your advice right now! In general this should be solvable by using: downgrade include=remove/ downgrade include=install/ i this particular case, i do not need to execute remove before install, because i'am not really downgrading, i'm upgrading but WPKG thinks i'm downgrading, apparently there was an error in a previous version of the xml file (i'm trying to understand what have happened). Can you post the package as it is contained in the file %SystemRoot%\System32\wpkg.xml on the failing system and how it is now defined on the server? If we compare those two we can better see what is going on, since that is the thing WPKG.js compares too. This is the portion on Libreoffice in the file %SYSTEM32%\wpkg.xml of one of the affected machines (before the downgrade definition): package id=libreoffice name=LibreOffice revision=%PKG_VERSION% reboot=false priority=10 variable name=PKG_VERSION value=%shortversion%-0/ variable name=shortversion value=3.5.4/ variable name=PKG_SOURCE value=%SOFTWARE%\libreoffice\3.5/ depends package-id=java7/ check type=uninstall condition=versiongreaterorequal path=LibreOffice .+ value=%shortversion%/ install cmd=msiexec /qn /i quot;%PKG_SOURCE%\LibO_%shortversion% _Win_x86_install_multi.msiquot; ALLUSERS=1 CREATEDESKTOPLINK=1 REGISTER_ALL_MSO_TYPES=0 ISCHECKFORPRODUCTUPDATE=0 REGISTER_NO_MSO_TYPES=1/ upgrade include=install/ remove cmd=msiexec /qn /x quot;%PKG_SOURCE%\LibO_%shortversion% _Win_x86_install_multi.msiquot; / /package After obtaining this copy, i have updated the package definition with: downgrade include=install / and now i have 3.6.1 on the affected machines that i have tested (around half of the total i know had this issue). I'll assume (by now) that this issue is fixed. By the way, i have no way to know all the remove commands for every package's version; as i understand, i cannot use the remove command of other version of the XML package because it will call the remove section of the current version of the XML package, not the remove section of the installed version of the package; to call the remove section of the installed package, i need to remove the package from the profile. Generally I use the MSI file for remove too, since I really don't like and need to bother with the application IDs. I don't know why users spend so much time on finding out the application IDs, when there is a simpler solution. Nowadays MSI files are able to remove older versions of the software too. ohh... i didn't know about that, i will test it! Thanks 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] packages not installing/upgrading
El jue, 13-09-2012 a las 23:07 +0200, Stefan Pendl escribió: Am 13.09.2012 21:19, schrieb Carlos R. Pasqualini: package id=libreoffice name=LibreOffice revision=% PKG_VERSION% reboot=false priority=10 variable name=PKG_VERSION value=%shortversion%-0/ variable name=shortversion value=3.5.4/ May be the problem was caused by the double variable expansion, which is only supported with wpkg.js 1.3.0 and higher. Not in this case, because i'm using 1.3.0 from the first day (i'm almost new on wpkg as you can see): var WPKG_VERSION = 1.3.0; - 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] packages not installing/upgrading
El mar, 11-09-2012 a las 11:09 +0200, Rainer Meier escribió: Hi Carlos, I might shed some light on this topic. Although I currently don't have time for in-dept explanation/analysis. On 06.09.2012 20:08, Carlos R. Pasqualini wrote: 2012-09-06 14:43:53, INFO: Installing 'LibreOffice' (libreoffice)... So WPKG is going to verify (check, upgrade/downgrade) LibreOffice. Fine. 2012-09-06 14:43:53, DEBUG : Reading variables from hosts[s] 2012-09-06 14:43:53, DEBUG : Reading variables from profile[s] 2012-09-06 14:43:53, DEBUG : Reading variables from package 'LibreOffice'. 2012-09-06 14:43:53, DEBUG : Got variable 'shortversion' of value '3.6.1' 2012-09-06 14:43:53, DEBUG : Got variable 'PKG_VERSION' of value '% shortversion%-0' 2012-09-06 14:43:53, DEBUG : Got variable 'PKG_SOURCE' of value '% SOFTWARE%\libreoffice\3.6' 2012-09-06 14:43:53, DEBUG : Setting variable: 'SOFTWARE=\\capibara \repositorio\software'. 2012-09-06 14:43:53, DEBUG : Setting variable: 'SOFTWARE=\\capibara \repositorio\software'. 2012-09-06 14:43:53, DEBUG : Setting variable: 'shortversion=3.6.1'. 2012-09-06 14:43:53, DEBUG : Setting variable: 'PKG_VERSION=% shortversion%-0'. 2012-09-06 14:43:53, DEBUG : Setting variable: 'PKG_SOURCE=%SOFTWARE% \libreoffice\3.6'. Variables set. 2012-09-06 14:43:53, DEBUG : Install type: downgrade 2012-09-06 14:43:53, DEBUG : Fetched 0 downgrade command(s). Here's your issue (very likely). WPKG performs a DOWNgrade, not an upgrade as you might have expected. Please note that the decision to do upgrade or downgrade is not depending on the checks. I think you got that point as I have seen you replying exactly this to another mail in the topic. The checks are entirely there to verify whether the software is installed properly. The decision whether upgrade or downgrade is performed depends on the values of the 'revision' attribute of a package. So if WPKG now claims it's going to perform a downgrade, then this is because the machine your package is applied to seems to have already a LibreOffice package installed which seems to have a newer version (in terms of revision='...' attribute). So please verify that your hosts local wpkg.xml in system32 folder does not contain an entry with LibreOffice where the revision is higher than your package to be synchronized. Such things often happen if package manipulations in productive repository happen while clients do run WPKG or the numbering scheme changes. For example early versions of WPKG only supported digits in the revision attribute. So I was used to enter something like 361 in the revision field. Then when changing to a different format like 3.6.1 it means a downgrade for WPKG since 3.6.1 is supposed to be lower version than 361.0.0 (or 350.0.0 previously installed). So please compare the revision locally on the host with the one on the server and you will likely find the cause why WPKG performs a downgrade instead of an upgrade. Moreover you will see here that WPKG fetched 0 (in words: zero) downgrade commands. Likely you did not specify any downgrade commands. You might also just replicate the upgrade commands as downgrade commands so WPKG would actually perform the same commands during suspected downgrade. So WPKG would think it's doing a downgrade while performing upgrade commands. The result will also be that the checks succeed and finally you are running LibreOffice 3.6.1 on your machine. Please also note that there were some issues regarding complex variable definitions recently. I recommend to use latest WPKG version from SVN: http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/stable/src/main/resources/wpkg/ 2012-09-06 14:43:53, ERROR : Could not process (downgrade) Finally the checks fail since no changes were performed to the system (performed downgrade, no commands, no system change, checks fail). HTH, Rainer Hi Rainer Your explanation makes a lot of sense to me, Thanks! Actually, in the first e-mail, i was asking for how to get even more info than 0xFF, because i was not understanding why i was having a 'downgrade'. Here is my libreoffice.xml file: -- ?xml version=1.0 encoding=UTF-8? packages xmlns:xsi=http://www.wpkg.org/packages; xsi:noNamespaceSchemaLocation=../xsd/packages.xsd package id=libreoffice name=LibreOffice revision=%PKG_VERSION% reboot=false priority=10 variable name=shortversion value=3.6.1 / variable name=PKG_VERSION value=%shortversion %-0 / variable name=PKG_SOURCE value=%SOFTWARE% \libreoffice\3.6 / depends package-id=java7 / check type=uninstall condition=versiongreaterorequal path=LibreOffice .+ value=%shortversion% / install
Re: [wpkg-users] packages not installing/upgrading
El mar, 11-09-2012 a las 12:28 +1000, Patrick CAHILL escribió: Carlos, yes but you have to remember that the Check has what is currently installed on the Client on the Left of the GreaterThanorEqual and whats packaged on the Server on the Right. If [Currently_Installed_on_Client] Is [GreaterThanOrEqual] To [Package_on_Server] Then [Upgrade] If [3.5.1] is GreaterThanOrEqual To [3.6.1] Then [Upgrade] So 3.5.1 has to be Larger or Equal to 3.6.1 for the Upgrade to occur, this will never happen, 3.5 is never bigger than 3.6 (which you will note is why the check system never checks the final .1 in your log, it stops after .5 = .6) As far as I can tell, GreaterThanOrEqual should be used to Upgrade to a lower version, a Downgrade if you will. Imagine if you have 3.6.1 installed but it has some bad problem on your systems, you could create a package with the check... If [3.6.1] is GreaterThanOrEqual To [3.5.1] Then [Upgrade] This will Upgrade to the lower version. Typically you want to upgrade to a higher version, so you should use LessThan or LessThanOrEqual If [Currently_Installed_on_Client] Is [LessThan] [Package_on_Server] Then [Upgrade] If [3.5.1] is LessThan [3.6.1] Then [Upgrade] I hope this helps (and that it is correct) ;) -Pat Cahill On 11/09/12, Carlos R. Pasqualini pasquali...@fcal.uner.edu.ar wrote: El mar, 11-09-2012 a las 09:32 +1000, Patrick CAHILL escribió: Carlos, can you try something for me? In your LibreOffice Upgrade definition, replace 'versiongreaterorequal' with 'versionsmallerthan' The way I read the documentation is... IF [the_version_installed] IS [condition] [the_version_packaged] THEN install/upgrade So your error is actually logically correct. If [3.5] is [Greater Than or Equal To] [3.6] then Upgrade Your return code is -1 which in a tri-state (less, equal, greater) like this is usually lessthan, which is correct. (A less than B = -1, A equal B = 0, A greater than B = 1) The reason I say use ''versionsmallerthan' rather than 'versionlessorequal' is that I think you only want to upgrade if the version installed is smaller, if its the same as is in the package then you dont want to install again. Even if I am wrong, its only a quick one word change. I will give it a try tomorrow, but that doesn't have any sense; we are talking about the 'check' condition, it is supposed to check if the package is already installed/upgraded and not if WPKG needs to do some work... See http://wpkg.org/Packages.xml#Check_conditions_.2F_check_type says: --- Of course it would be unwise to launch the installer if the software is already installed. That's why there are check conditions. The check conditions are also used after the installer has finished to verify that the software has actually been successfully installed. --- so i'm making the check condition against the new version of the package, not the older one; i want to have installed in this system this version or any greater version (if it was installed manually) Best Regards Dear Pat i really thank you for taking time to answer other user's questions, but i think you are really wrong. I will insist, the check is to see if the installed version complies with the package's requirements. As I understand the check / does not have any inference in the decision of upgrading or downgrading a package. I would like to have some other users to give her thoughts on this. Best Regards - 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] packages not installing/upgrading
El mié, 12-09-2012 a las 20:39 +0200, Stefan Pendl escribió: Am 12.09.2012 19:43, schrieb Carlos R. Pasqualini: As I understand the check / does not have any inference in the decision of upgrading or downgrading a package. The checks are defined to make sure the version to be installed with the current package is installed correctly. In general this means different things in different situations. 1) initial install (no entry in local wpkg.xml file): check if software is already installed to prevent double installation 2) upgrade and downgrade (previous entry in local wpkg.xml file): check if up-/downgrade really succeeded this can be changed with some package attributes to check before up-/downgrading 3) remove (package is no longer applied through a profile): make sure the package is installed before it will be removed That is what i have been understanding, so it seems Pat has the wrong view of what check / does. isn't it? What does the number after the hyphen mean in your version number? x.y.z-a ... what means a? i reserve the last value for reviews of the .xml file with the same version of the installer. suppose i have a 1.2.3 version of the package, i'll create a 1.2.3-0 revision of the xml, and if i found something wrong in the XML file, i can create 1.2.3-1 ... 1.2.3-9 without having trouble with the possibly upcoming version 1.2.4 of the package. It's just used by me. ¿do you think it's bad to do that? In general this should be solvable by using: downgrade include=remove/ downgrade include=install/ i this particular case, i do not need to execute remove before install, because i'am not really downgrading, i'm upgrading but WPKG thinks i'm downgrading, apparently there was an error in a previous version of the xml file (i'm trying to understand what have happened). By the way, i have no way to know all the remove commands for every package's version; as i understand, i cannot use the remove command of other version of the XML package because it will call the remove section of the current version of the XML package, not the remove section of the installed version of the package; to call the remove section of the installed package, i need to remove the package from the profile. Best Regards - 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] WPKG on Windows 7
El mar, 11-09-2012 a las 16:04 +0200, Marco Gaiarin escribió: + WPKG-GP have notification messages, but only on startup (and my experience say me that doing installation on startup is a pain). i have not found any other way to reliably install software on Win7 without WPKG-GP (yes, on startup...) can we talk of WPKG-GP specific problems in this list? I'm having some trouble with WPKG-GP + Win7 because it tries to start before the computer have access to the network. best regards - 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] packages not installing/upgrading
El vie, 31-08-2012 a las 23:53 +0200, Stefan Pendl escribió: Am 31.08.2012 23:45, schrieb Carlos R. Pasqualini: Today i found an error on a package description, i suspect that type of errors are the source of troubles, but i need to debug and find others, and the output of /debug apparently is not showing all the info i need to understand the trouble. It is all about reading the log file, you just need to make sure the log level is set to 0xFF. You could post the offending portion of the log too. Here is another log, again with Libre Office What do you think? where should i search for an error? it does not even try to execute the install command, it has no sense to me. Thanks for your time! 2012-09-10 18:56:00, DEBUG : Reading variables from hosts[s] 2012-09-10 18:56:00, DEBUG : Reading variables from profile[s] 2012-09-10 18:56:00, DEBUG : Reading variables from package 'LibreOffice'. 2012-09-10 18:56:00, DEBUG : Got variable 'shortversion' of value '3.6.1' 2012-09-10 18:56:00, DEBUG : Got variable 'PKG_VERSION' of value '% shortversion%-0' 2012-09-10 18:56:00, DEBUG : Got variable 'PKG_SOURCE' of value '% SOFTWARE%\libreoffice\3.6' 2012-09-10 18:56:00, DEBUG : Setting variable: 'SOFTWARE=\\capibara \repositorio\software'. 2012-09-10 18:56:00, DEBUG : Setting variable: 'SOFTWARE=\\capibara \repositorio\software'. 2012-09-10 18:56:00, DEBUG : Setting variable: 'shortversion=3.6.1'. 2012-09-10 18:56:00, DEBUG : Setting variable: 'PKG_VERSION=% shortversion%-0'. 2012-09-10 18:56:00, DEBUG : Setting variable: 'PKG_SOURCE=%SOFTWARE% \libreoffice\3.6'. 2012-09-10 18:56:00, DEBUG : Install type: downgrade 2012-09-10 18:56:00, DEBUG : Fetched 0 downgrade command(s). 2012-09-10 18:56:00, DEBUG : Checking existence of package: LibreOffice 2012-09-10 18:56:00, DEBUG : Reading variables from hosts[s] 2012-09-10 18:56:00, DEBUG : Reading variables from profile[s] 2012-09-10 18:56:00, DEBUG : Reading variables from package 'LibreOffice'. 2012-09-10 18:56:00, DEBUG : Got variable 'shortversion' of value '3.6.1' 2012-09-10 18:56:00, DEBUG : Got variable 'PKG_VERSION' of value '% shortversion%-0' 2012-09-10 18:56:00, DEBUG : Got variable 'PKG_SOURCE' of value '% SOFTWARE%\libreoffice\3.6' 2012-09-10 18:56:00, DEBUG : Setting variable: 'SOFTWARE=\\capibara \repositorio\software'. 2012-09-10 18:56:00, DEBUG : Setting variable: 'SOFTWARE=\\capibara \repositorio\software'. 2012-09-10 18:56:00, DEBUG : Setting variable: 'shortversion=3.6.1'. 2012-09-10 18:56:00, DEBUG : Setting variable: 'PKG_VERSION=% shortversion%-0'. 2012-09-10 18:56:00, DEBUG : Setting variable: 'PKG_SOURCE=%SOFTWARE% \libreoffice\3.6'. 2012-09-10 18:56:01, DEBUG : Uninstall entry 'LibreOffice 3.5' matches expression 'LibreOffice .+'. 2012-09-10 18:56:01, DEBUG : Found version of 'LibreOffice .+' at HKLM \SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall \{EF790F1C-CB0C-4B95-8C54-60783F3B6661}: 3.5.4.2|Comparing to expected version: %shortversion%. 2012-09-10 18:56:01, DEBUG : Comparing version: '3.5.4.2' = '3.6.1'. 2012-09-10 18:56:01, DEBUG : Comparing version fragments: '3' = '3' 2012-09-10 18:56:01, DEBUG : Comparing version fragments: '5' = '6' 2012-09-10 18:56:01, DEBUG : Comparing uninstall version '3.5.4.2' to expected version '3.6.1' using condition 'versiongreaterorequal' returned -1. 2012-09-10 18:56:01, DEBUG : Uninstall version check for package 'LibreOffice .+' returned false for operation type versiongreaterorequal. 2012-09-10 18:56:01, DEBUG : Searching for previously executed checks with attributes type='uninstall', condition='versiongreaterorequal', path='LibreOffice .+', value='%shortversion%' 2012-09-10 18:56:01, DEBUG : Unable to find any previously executed checks with these attributes. 2012-09-10 18:56:01, DEBUG : Saving unsorted settings to 'C:\WINDOWS \system32\wpkg.xml'.false 2012-09-10 18:56:01, DEBUG : Saving XML : C:\WINDOWS\system32\wpkg.xml 2012-09-10 18:56:01, ERROR : Could not process (downgrade) LibreOffice.|Failed checking after installation. 2012-09-10 18:56:01, DEBUG : Cleaning up temporary downloaded files 2012-09-10 18:56:01, DEBUG : Restoring previous environment. 2012-09-10 18:56:01, DEBUG : Reading variables from hosts[s] - 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] packages not installing/upgrading
El lun, 10-09-2012 a las 19:50 -0300, Carlos R. Pasqualini escribió: El vie, 31-08-2012 a las 23:53 +0200, Stefan Pendl escribió: Am 31.08.2012 23:45, schrieb Carlos R. Pasqualini: Today i found an error on a package description, i suspect that type of errors are the source of troubles, but i need to debug and find others, and the output of /debug apparently is not showing all the info i need to understand the trouble. It is all about reading the log file, you just need to make sure the log level is set to 0xFF. You could post the offending portion of the log too. Here is another log, again with Libre Office What do you think? where should i search for an error? it does not even try to execute the install command, it has no sense to me. Thanks for your time! Here is the libreoffice's package XML ?xml version=1.0 encoding=UTF-8? packages xmlns:xsi=http://www.wpkg.org/packages; xsi:noNamespaceSchemaLocation=../xsd/packages.xsd package id=libreoffice name=LibreOffice revision=%PKG_VERSION% reboot=false priority=10 variable name=shortversion value=3.6.1 / variable name=PKG_VERSION value=%shortversion %-0 / variable name=PKG_SOURCE value=%SOFTWARE% \libreoffice\3.6 / depends package-id=java7 / check type=uninstall condition=versiongreaterorequal path=LibreOffice .+ value=%shortversion% / install cmd='msiexec /qn /i %PKG_SOURCE%\LibO_%shortversion% _Win_x86_install_multi.msi ALLUSERS=1 CREATEDESKTOPLINK=1 REGISTER_ALL_MSO_TYPES=0 ISCHECKFORPRODUCTUPDATE=0 REGISTER_NO_MSO_TYPES=1' / upgrade include=install / remove cmd='msiexec /qn /x %PKG_SOURCE%\LibO_%shortversion% _Win_x86_install_multi.msi ' / /package /packages - 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] packages not installing/upgrading
El mar, 11-09-2012 a las 09:32 +1000, Patrick CAHILL escribió: Carlos, can you try something for me? In your LibreOffice Upgrade definition, replace 'versiongreaterorequal' with 'versionsmallerthan' The way I read the documentation is... IF [the_version_installed] IS [condition] [the_version_packaged] THEN install/upgrade So your error is actually logically correct. If [3.5] is [Greater Than or Equal To] [3.6] then Upgrade Your return code is -1 which in a tri-state (less, equal, greater) like this is usually lessthan, which is correct. (A less than B = -1, A equal B = 0, A greater than B = 1) The reason I say use ''versionsmallerthan' rather than 'versionlessorequal' is that I think you only want to upgrade if the version installed is smaller, if its the same as is in the package then you dont want to install again. Even if I am wrong, its only a quick one word change. I will give it a try tomorrow, but that doesn't have any sense; we are talking about the 'check' condition, it is supposed to check if the package is already installed/upgraded and not if WPKG needs to do some work... See http://wpkg.org/Packages.xml#Check_conditions_.2F_check_type says: --- Of course it would be unwise to launch the installer if the software is already installed. That's why there are check conditions. The check conditions are also used after the installer has finished to verify that the software has actually been successfully installed. --- so i'm making the check condition against the new version of the package, not the older one; i want to have installed in this system this version or any greater version (if it was installed manually) Best Regards - 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] packages not installing/upgrading
El vie, 31-08-2012 a las 23:53 +0200, Stefan Pendl escribió: Am 31.08.2012 23:45, schrieb Carlos R. Pasqualini: Today i found an error on a package description, i suspect that type of errors are the source of troubles, but i need to debug and find others, and the output of /debug apparently is not showing all the info i need to understand the trouble. It is all about reading the log file, you just need to make sure the log level is set to 0xFF. You could post the offending portion of the log too. here it is one case that makes me nuts: 2012-09-06 14:43:53, DEBUG : Installation of references (dependencies) for 'LibreOffice' (libreoffice) successfully finished. 2012-09-06 14:43:53, INFO: Installing 'LibreOffice' (libreoffice)... 2012-09-06 14:43:53, DEBUG : Reading variables from hosts[s] 2012-09-06 14:43:53, DEBUG : Reading variables from profile[s] 2012-09-06 14:43:53, DEBUG : Reading variables from package 'LibreOffice'. 2012-09-06 14:43:53, DEBUG : Got variable 'shortversion' of value '3.6.1' 2012-09-06 14:43:53, DEBUG : Got variable 'PKG_VERSION' of value '% shortversion%-0' 2012-09-06 14:43:53, DEBUG : Got variable 'PKG_SOURCE' of value '% SOFTWARE%\libreoffice\3.6' 2012-09-06 14:43:53, DEBUG : Setting variable: 'SOFTWARE=\\capibara \repositorio\software'. 2012-09-06 14:43:53, DEBUG : Setting variable: 'SOFTWARE=\\capibara \repositorio\software'. 2012-09-06 14:43:53, DEBUG : Setting variable: 'shortversion=3.6.1'. 2012-09-06 14:43:53, DEBUG : Setting variable: 'PKG_VERSION=% shortversion%-0'. 2012-09-06 14:43:53, DEBUG : Setting variable: 'PKG_SOURCE=%SOFTWARE% \libreoffice\3.6'. 2012-09-06 14:43:53, DEBUG : Install type: downgrade 2012-09-06 14:43:53, DEBUG : Fetched 0 downgrade command(s). 2012-09-06 14:43:53, DEBUG : Checking existence of package: LibreOffice 2012-09-06 14:43:53, DEBUG : Reading variables from hosts[s] 2012-09-06 14:43:53, DEBUG : Reading variables from profile[s] 2012-09-06 14:43:53, DEBUG : Reading variables from package 'LibreOffice'. 2012-09-06 14:43:53, DEBUG : Got variable 'shortversion' of value '3.6.1' 2012-09-06 14:43:53, DEBUG : Got variable 'PKG_VERSION' of value '% shortversion%-0' 2012-09-06 14:43:53, DEBUG : Got variable 'PKG_SOURCE' of value '% SOFTWARE%\libreoffice\3.6' 2012-09-06 14:43:53, DEBUG : Setting variable: 'SOFTWARE=\\capibara \repositorio\software'. 2012-09-06 14:43:53, DEBUG : Setting variable: 'SOFTWARE=\\capibara \repositorio\software'. 2012-09-06 14:43:53, DEBUG : Setting variable: 'shortversion=3.6.1'. 2012-09-06 14:43:53, DEBUG : Setting variable: 'PKG_VERSION=% shortversion%-0'. 2012-09-06 14:43:53, DEBUG : Setting variable: 'PKG_SOURCE=%SOFTWARE% \libreoffice\3.6'. 2012-09-06 14:43:53, DEBUG : Uninstall entry 'LibreOffice 3.5' matches expression 'LibreOffice .+'. 2012-09-06 14:43:53, DEBUG : Found version of 'LibreOffice .+' at HKLM \SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall \{EF790F1C-CB0C-4B95-8C54-60783F3B6661}: 3.5.4.2|Comparing to expected version: %shortversion%. 2012-09-06 14:43:53, DEBUG : Comparing version: '3.5.4.2' = '3.6.1'. 2012-09-06 14:43:53, DEBUG : Comparing version fragments: '3' = '3' 2012-09-06 14:43:53, DEBUG : Comparing version fragments: '5' = '6' 2012-09-06 14:43:53, DEBUG : Comparing uninstall version '3.5.4.2' to expected version '3.6.1' using condition 'versiongreaterorequal' returned -1. 2012-09-06 14:43:53, DEBUG : Uninstall version check for package 'LibreOffice .+' returned false for operation type versiongreaterorequal. 2012-09-06 14:43:53, DEBUG : Searching for previously executed checks with attributes type='uninstall', condition='versiongreaterorequal', path='LibreOffice .+', value='%shortversion%' 2012-09-06 14:43:53, DEBUG : Unable to find any previously executed checks with these attributes. 2012-09-06 14:43:53, DEBUG : Saving unsorted settings to 'C:\WINDOWS \system32\wpkg.xml'.false 2012-09-06 14:43:53, DEBUG : Saving XML : C:\WINDOWS\system32\wpkg.xml 2012-09-06 14:43:53, ERROR : Could not process (downgrade) LibreOffice.|Failed checking after installation. 2012-09-06 14:43:53, DEBUG : Cleaning up temporary downloaded files Lots of other Machines have upgraded to LibO 3.6.1 without troubles... No visible error in debug file unless this one: Could not process (downgrade) LibreOffice.|Failed checking after installation. downgrade? error without even try to execute the upgrade command in the libreoffice.xml package? I find this debug output insufficient to understand what's happening Best Regards Charly - 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
[wpkg-users] packages not installing/upgrading
Hi people! i'm having trouble with upgradings trough wpkg and cannot find any way to debug it ¿is there a debug howto or something? i couldn't find any info about it. best regards Charly - 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