Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
2016SuiteSKUless Revert "Revert "support new URL for post-2016 O365 versions"" Sep 13, 2018
Atlassian Fixing HipChat.munki Aug 1, 2016
CelestialTeapotSoftware
CharlesProxy
ClipMenu
Google PythonAppEngineSDK
IrradiatedSoftware
Isolator
Limechat
MSLync
MSMAU
MSOffice2016
MSOutlook
MacID
Mactracker Switch to HTTPS Sparkle feed Oct 14, 2016
OnCue
Pacifist
PeterBorgApps
Puppetlabs
QuickRadar
RedSweater
Reflector
SharedProcessors
Sonos
Synergy
WWDC
Workshare
iTeleport
santa
santaRecipes
.gitignore
README.md

README.md

arubdesu-recipes

Recipes for http://autopkg.github.io/autopkg/

FAQ

Why does Microsoft have an update available, but your recipe (doesn't see it yet|fails)?

Sorry, but Microsoft is often faster to provide direct download links than to fix or update the products feed(s). So far, we've had

  1. improperly signed packages,
  2. no signature at all,
  3. broken xml in the feed,
  4. xml that points to a valid URL... which 404's,
  5. days which turn into weeks which turn into months where they don't update the feed at all.

We usually just have to wait. You can help confirm this symptom by doing the following:

  1. Visiting the update feed URL (it's in the URLProvider processor, e.g. for Lync)
  2. If it's still showing the old URL, we just have to wait, but you can continue...

If you're going above and beyond -

  1. Download the new version and install (or unpack the payload from the pkg if you're savvy)
  2. Run 'Check for Updates' from the Help menu while doing a packet capture with a tool like CharlesProxy
  3. If there's a new update feed, then yes, my recipe is indeed behind the times and needs updating.
  • If not... let's enjoy the wait together!