No pkginfo found, but it's in the catalog...

[yagmot]

The screenshot pretty much says it all. Munki throws up a warning saying "No pkginfo for yaddayadda found in catalogs testing, production" yet when I open the local cached copy of the testing catalog file, I see yaddayadda plain as day.

I'm encountering this problem with a number of pkginfos, and they all happen to be my BW printers. The color printer pkginfos give me no problems at all. The odd thing is that the files are practically identical. I tried making an exact duplicate and only changing the name, but it's still not working. I diffed the files and verified that those are the only differences. Any ideas? I'm pulling my hair out over this...

-Tom

[Nate Walck]

What is the name key for the Color printer that works? What is the version number key on the Color/B&W Pkginfo? You did makecatalogs between each change? (Have to ask!).

Nate

--
You received this message because you are subscribed to the Google Groups "munki-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
<Screen Shot 2013-08-26 at 10.22.18 AM.png>

[Gregory Neagle]

Pkginfo names that end with a hyphen and digits confuse Munki. 

Sent from my iPhone

--

You received this message because you are subscribed to the Google Groups "munki-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[yagmot]

Greg was right. I actually started to try exchanging the hyphens for underscores before I saw his post... Thanks guys!

[jeremy...@msad72.org]

This tidbit really should be noted somewhere on https://code.google.com/p/munki/wiki/PkginfoForAppleSoftwareUpdates, I've been struggling with this for days until I found this post.

[Gregory Neagle]

On Nov 13, 2013, at 2:05 PM, jeremy...@msad72.org wrote:

This tidbit really should be noted somewhere on https://code.google.com/p/munki/wiki/PkginfoForAppleSoftwareUpdates,

Why there, specifically?

https://code.google.com/p/munki/wiki/Manifests#item_names

If you understand how you can refer to items in manifests, you understand this is not something specific to PkginfoForAppleSoftwareUpdates.

If I can say 'install the item named "Firefox", version "3.0.9"' by adding "Firefox-3.0.9" to a manifest, it follows that it might be a bad idea to name something "Foo-1.0". Is that item "Foo", version "1.0", or Item "Foo-1.0", latest version?

-Greg

[jeremy...@msad72.org]

I have been getting the same "No pkginfo found" error noted above because when using "munkiimport --apple-update 041-6651 --catalog=testing" I named it with a hyphen instead of an underscore during the import process.  Now when I run managedsoftwareupdate I do not get the "No pkginfo found" error if I instead use an underscore.

Of course, your confusion may stem from the fact that I'm not sure I'm actually using the --apple-update tool correctly as my assumption was that I could simply tell Munki to pull only this specific update referenced by the Product Key from Apple and it would go out, put the pkg in my repo, and apply it to my fleet... which upon more careful reading it seems this tool is only for tweaking additional metadata if you are using munki to provide ALL Apple software updates, correct???  Is there another tool I'm missing that would do that, because that would be pretty awesome ;)

[Gregory Neagle]

On Nov 13, 2013, at 2:29 PM, jeremy...@msad72.org wrote:

I have been getting the same "No pkginfo found" error noted above because when using "munkiimport --apple-update 041-6651 --catalog=testing" I named it with a hyphen instead of an underscore during the import process.  Now when I run managedsoftwareupdate I do not get the "No pkginfo found" error if I instead use an underscore.

Of course, your confusion may stem from the fact that I'm not sure I'm actually using the --apple-update tool correctly as my assumption was that I could simply tell Munki to pull only this specific update referenced by the Product Key from Apple and it would go out, put the pkg in my repo, and apply it to my fleet... which upon more careful reading it seems this tool is only for tweaking additional metadata if you are using munki to provide ALL Apple software updates, correct???  

The additional metadata is used when Munki installs Apple software updates from an Apple software update server.

Is there another tool I'm missing that would do that, because that would be pretty awesome ;)

If you are downloading Apple updates and importing them into your Munki repo you treat them like any other package: Firefox or an Office 2011 update or a Wacom driver. (And you get to reimplement the logic that determines which machines get which updates.) What am I missing here?

-Greg

On Wednesday, November 13, 2013 5:12:04 PM UTC-5, gregn...@mac.com wrote:

On Nov 13, 2013, at 2:05 PM, jeremy...@msad72.org wrote:

This tidbit really should be noted somewhere on https://code.google.com/p/munki/wiki/PkginfoForAppleSoftwareUpdates,

Why there, specifically?

https://code.google.com/p/munki/wiki/Manifests#item_names

If you understand how you can refer to items in manifests, you understand this is not something specific to PkginfoForAppleSoftwareUpdates.

If I can say 'install the item named "Firefox", version "3.0.9"' by adding "Firefox-3.0.9" to a manifest, it follows that it might be a bad idea to name something "Foo-1.0". Is that item "Foo", version "1.0", or Item "Foo-1.0", latest version?

-Greg

I've been struggling with this for days until I found this post.

On Sunday, August 25, 2013 10:01:14 PM UTC-4, gregn...@mac.com wrote:

Pkginfo names that end with a hyphen and digits confuse Munki. 

[jeremy...@msad72.org]

The motivator for this was Safari 6.1 - the package for this update was far harder to obtain (at least for me) than any package has right to be and I suspect Apple is going to continue down this road so I doubt this is a unique case.  For me, Munki is about simplifying my workflow, as I learn more and more about it I keep marveling at the level of control I have.  

It seemed perfectly logical that I could simply read my com.apple.SoftwareUpdate plist to find a specific product key for a troublesome pkg and then entering that key into munkiimport --apple-update would automate grabbing and distributing that specific item for me without enabling all Apple software updates en masse.  That's exactly the kind of simplicity Munki is spoiling me with and honestly seems even easier than manually downloading packages from Apple to import as is SOP.  It is what the page I referenced implied to me when I read it, whether that was intended or not.  Were that accurate, your nugget about it not liking hyphens and numbers is incredibly important... the tool even suggests naming it "041-6651" by default when you run it so I never thought to second guess it.

If this was not your intent for the tool, please forgive my rambling, my post was simply to help point out a potential clarification for the wiki to help others avoid losing the time I lost figuring this out.  There's so much to sift through as it is, I just really appreciate the time you devote to this project.

[Gregory Neagle]

On Nov 13, 2013, at 8:16 PM, jeremy...@msad72.org wrote:

The motivator for this was Safari 6.1 - the package for this update was far harder to obtain (at least for me) than any package has right to be and I suspect Apple is going to continue down this road so I doubt this is a unique case.  

Right. Let Apple software update do its job (with or without Munki's help).

For me, Munki is about simplifying my workflow, as I learn more and more about it I keep marveling at the level of control I have.  

It seemed perfectly logical that I could simply read my com.apple.SoftwareUpdate plist to find a specific product key for a troublesome pkg and then entering that key into munkiimport --apple-update would automate grabbing and distributing that specific item for me without enabling all Apple software updates en masse.  

While that would be _possible_, it would not be a fair amount of work to implement. And it still would require you to reimplement all of the logic Apple Software Update uses to determine which updates are applicable for which machines. The better generic solution, of course, is to run your own Apple software update server, either using Apple's software, or reposado (https://github.com/wdas/reposado) and simply use Munki as a client (with or without additional metadata). You can run a reposado server on the same hardware as your Munki server if you'd like.

That's exactly the kind of simplicity Munki is spoiling me with and honestly seems even easier than manually downloading packages from Apple to import as is SOP.  

Even easier is to do none of these things and implement your own Apple software update server, or point Munki at Apple's!

It is what the page I referenced implied to me when I read it, whether that was intended or not.  Were that accurate, your nugget about it not liking hyphens and numbers is incredibly important... the tool even suggests naming it "041-6651"

That's not a _suggestion_. The apple_update_metadata item's name _must_ match the Apple update's ProductKey for this feature to _work_. That name is how Munki _finds_ an apple_update_metadata item that matches a given Apple update.

by default when you run it so I never thought to second guess it.

And a name of "041-6651" is acceptable for apple_update_metadata items. Such items are _never_ to be added to any manifest, and so the confusion between "foo-1.0" and "foo", version "1.0" doesn't apply here.

If this was not your intent for the tool, please forgive my rambling, my post was simply to help point out a potential clarification for the wiki to help others avoid losing the time I lost figuring this out.

I've updated the wiki document: https://code.google.com/p/munki/wiki/PkginfoForAppleSoftwareUpdates