Build numbering changed, or digit missing in latest release? about munki HOT 7 CLOSED

The receipts look correct in the package itself and the package name looks right in the release page. Where do you see the build number as 482?

from munki.

I'm assuming this is the carry over from googlecode/svn's incrementing, but... dunno how it would break

from munki.

In munki/code/tools/make_munki_mpkg.sh, MAGICNUMBER=482, and it used to match the build number before? This is also reflected the the .pkg filename produced by the latest release.

from munki.

That number never matched the build number since this moved to git. Check the git history for the history on that file specifically.

It's the offset from when we switched from SVN to git so the build numbers in git would be at the correct number.

from munki.

In the source tarball release for 6.3.1, MAGICNUMBER=4581, and in the source tarball for 6.3.2, MAGICNUMBER=482.
When I run make_munki_mpkg.sh for both these releases, it gives me the file names munkitools-6.3.1.4581.pkg and munkitools-6.3.2.482.pkg

Ultimately, I suppose it doesn't really matter. I just thought it might have been a typo so I thought I'd raise the issue.

from munki.

Are you doing a shallow git clone or no git clone and just downloading the zip file? In either case the "calculated" build number will be wrong.

https://github.com/munki/munki/wiki/Building-Munki-packages#procedure

Since you mention "In the source tarball release for 6.3.1" I'm guessing you aren't using a full git clone. Thus your odd/wrong build number.

from munki.

No response, but I think my guess is right, so closing this.

from munki.