'npackdcl.exe info' no longer shows all available versions

[GoogleCodeExporter]

Hi, I'm the author of the puppet module for npackd. In version 1.17.9, the 
command 'npackd info -p {somepackage}' returned a Versions field containing all 
available versions. E.g. for Putty:

Icon: 
https://lh6.googleusercontent.com/-E0wnbZL31b8/T2h0OY68qKI/AAAAAAAAAaQ/E0IIgHmr_
NM/s800/uk.org.greenend.chiark.sgtatham.Putty.png
Title: Putty
Description: SSH client
License: org.opensource.MITLicense
Package home page: 
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
Versions: 0.62, 0.63

In 1.18.7, the same command returns info only about installed package versions:

Title: Putty
Description: [Npackd list of installed packages] Putty
License:
Internal package name: uk.org.greenend.chiark.sgtatham.Putty
Package home page:
Categories:
Icon:
Versions: 0.62
1 versions are installed:
    0.62 in C:\Program Files (x86)\Putty-0.62_2

The puppet provider was making use of this version list to determine whether 
packages are up to date. I can't seem to find the new way to get this list of 
versions; has this functionality been removed? If yes, might you recommend a 
new way to determine if packages are up to date?

Thanks

Original issue reported on code.google.com by badgeri...@gmail.com on 20 May 2014 at 11:45

[GoogleCodeExporter]

I should amend this a little: the question the puppet provider needs an answer 
to is "What is the latest version for package X?"

Original comment by badgeri...@gmail.com on 21 May 2014 at 2:58

[GoogleCodeExporter]

This is the only way to find out the latest available version for a package 
right now.

I cannot reproduce this. Could the reversed version number order be a problem? 
This is what I get with 1.18.7.

>%npackd_cl%\npackdcl info -p Putty
Title: Putty
Description: SSH client
License: org.opensource.MITLicense
Internal package name: uk.org.greenend.chiark.sgtatham.Putty
Package home page: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.ht
ml
Categories: Tools
Icon: https://lh6.googleusercontent.com/-E0wnbZL31b8/T2h0OY68qKI/AAAAAAAAAaQ/E0I
IgHmr_NM/s800/uk.org.greenend.chiark.sgtatham.Putty.png
Versions: 0.63, 0.62
No versions are installed

Original comment by tim.lebe...@gmail.com on 22 May 2014 at 4:06

[GoogleCodeExporter]

Hrm, I think there may be a caching issue here:

PS > npackdcl.exe list-repos
0 repositories are defined

PS > npackdcl.exe info -p Putty
Title: Putty
Description: [Npackd list of installed packages] Putty
License:
Internal package name: uk.org.greenend.chiark.sgtatham.Putty
Package home page:
Categories:
Icon:
Versions: 0.62
No versions are installed

I thought I knew how to clear it (internet options) but that didn't change 
anything. I'm still poking around, but thought I'd put this out here since it 
may be meaningful to you. 

Original comment by badgeri...@gmail.com on 22 May 2014 at 4:54

[GoogleCodeExporter]

since 1.18 "npackdcl.exe add/remove" do not reload the repositories from the 
Internet. Maybe this is the problem. Please try "npackdcl detect"!

Original comment by tim.lebe...@gmail.com on 22 May 2014 at 5:06

[GoogleCodeExporter]

Ah ha, yes, now I get the same output as you. Normally the cached data will 
time out at some point right? Or is it necessary to manually kick it with 
'detect' to get it to reload?

Original comment by badgeri...@gmail.com on 23 May 2014 at 2:14

[GoogleCodeExporter]

no, only "npackdcl detect" re-builds the local package database. Yes, it is 
necessary to kick it with 'detect' to get it to reload.

Original comment by tim.lebe...@gmail.com on 23 May 2014 at 5:35

[GoogleCodeExporter]

Ok, thanks. I've got the needed changes into the puppet provider.  

Original comment by badgeri...@gmail.com on 27 May 2014 at 3:32

[GoogleCodeExporter]

I wonder how apt-get for example deals with this problem.

Original comment by tim.lebe...@gmail.com on 30 May 2014 at 11:00

[GoogleCodeExporter]

I think apt-get and the like operate pretty much the same. Within the puppet 
community, for example, I've seen various patterns for doing apt (periodic 
'apt-get update', always run 'apt-get update' before attempting to install any 
package, etc.). 

Original comment by badgeri...@gmail.com on 3 Jun 2014 at 2:18

[GoogleCodeExporter]

Original comment by tim.lebe...@gmail.com on 29 Jun 2014 at 2:01

• Changed state: Thinking