Munki 2.0.0.2108 - Enhanced user information when item fails to install.

[GoogleCodeExporter]

(Using Firefox/Flash to see the issue)

Server
1. Import Flash as "Flash".
2. Import Firefox.
3. In Firefox's pkginfo, have it require "Adobe Flash" or something that 
doesn't currently exist.
4. Add Firefox to optional_install

Client
1. Attempt to download Firefox via MSC. It will mark the item as "Unavailable".

-------

If you go to the Firefox page, there will be an error.

Can't install X because could not resolve all dependencies.

The logs show what truly happened.

WARNING: Could not process item blahblahblah for install. No pkginfo found in 
catalogs: development, testing, production
WARNING: Didn't attempt to install X because could not resolve all dependencies.

-------

I think at the very least, we should show both sets of information to help the 
user understand what is happening, even if this is the fault of the admin. A 
user will not know what to report other than it not working.

What I would prefer is a pop-up/notification/whatever that informs the user of 
the issue. A typical user is not going to know that they need to go to the 
actual program page to see the generic error.

Original issue reported on code.google.com by eriknico...@gmail.com on 1 Aug 2014 at 12:52

[GoogleCodeExporter]

"I think at the very least, we should show both sets of information to help the 
user understand what is happening, even if this is the fault of the admin. A 
user will not know what to report other than it not working."

I don't. The user can't do much about the issue other than report it. I'm 
tempted to make the error even more generic: "Can't install X because of a 
server error. Contact your systems administrator."

Parsing the log to show only the relevant info is harder than it seems. I don't 
want to bother at this point since the end-user can't do anything about it.

"What I would prefer is a pop-up/notification/whatever that informs the user of 
the issue. A typical user is not going to know that they need to go to the 
actual program page to see the generic error."

What happens if they've logged out or quit MSC.app? It should launch (or set 
itself up to launch upon the next login (and keep track of which user initiated 
the install in case of multiple users of a machine) to inform them of an error 
they can do nothing about except report? Here's how I see it working in real 
life:

"I told MSC to install Foo.app. Later I looked for Foo.app to run it and it 
wasn't there. I opened MSC.app and now it says Foo.app is unavailable! What's 
going on?" Admin checks and fixes things.

or

"I told MSC to install Foo.app. Later I looked for Foo.app to run it and it 
wasn't there. I opened MSC.app and now it says Foo.app is unavailable! I 
clicked on it and now I see an error about 'Can't install Foo.app because could 
not resolve all dependencies.: What's going on?" Admin checks and fixes things.

Original comment by greg.nea...@disneyanimation.com on 1 Aug 2014 at 1:00

[GoogleCodeExporter]

Fair enough. At least fix the broken English. :)

Original comment by eriknico...@gmail.com on 1 Aug 2014 at 1:04

[GoogleCodeExporter]

Please be more specific in what you'd expect to see. Errors are often terse.

Would

"Can't install X because not all dependencies could be resolved."

be acceptable? (I don't think that phrase will make any more sense to normal 
users, but it is more like standard English)

Original comment by gregnea...@mac.com on 1 Aug 2014 at 1:10

[GoogleCodeExporter]

I'm giving you a hard time - in the end it's just semantics.

"Foo could not be installed due to a dependency issue. Please contact your 
system administrator."

Original comment by eriknico...@gmail.com on 1 Aug 2014 at 1:20