debian Gnu/Linux is supposed to mount HFS+ automatically, and 'just work'--it even has all the packages pre-installed typically. You may need to install hfsprogs and any other "hfsp..." packages you are missing. I've seen disks like yours plug-n-play into Debian.
The support for hfs+ has reportedly (I will post a link, can't find it at the moment) been troublesome, in the most recent kernels, since around Linux 2.7 times, so the workaround is to use the -t hfsplus and -o [all options needed] for mount. Your kernel is probably already telling you to possibly use the force option, and is explaining that this is risky.
There is a really great explanation of how to do this, in this post, and of course more information is on on the man pages for mount and hfsplus.
This greatly assumes that your disk is not messed up, for example containing data from old installations or being otherwise corrupted.
Since you created the disk on a Mac, be sure also the table is actually GPT, and not an apple partition map or even some type of other table or hybrid-table; user sourcejedi recently pointed this out to me.
If you'd like to post an update, I will gladly follow-up on this answer and/or provide more research if you can post the output of viewing the disk in gparted (or gdisk as mgorven suggested above), as well also post information from dmesg from just after all of the above commands and trying to mount the specific partition /dev/sda1 using the correct offset and sizelimit, as I mentioned.
The partition unique GUID is generated at the time that the partition is created. It uniquely identifies the partition at least inside the disk and probably among all the disks you own (because it's unbelievably rare for GUIDs to collide).
A partition GUID code (by which I believe you mean a partition type GUID), on the other hand, is a known, fixed GUID. It identifies the type of data inside that partition. For example, if you had a partition that contained an ordinary GNU/Linux filesystem, you would assign it a partition type GUID of 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (defined as "GNU/Linux filesystem data"). If that partition was used as your /home, you would give it a GUID of 933AC7E1-2EB4-4F13-B844-0E14E2AEF915 (defined as "GNU/Linux /home"). If that partition was encrypted with, say, LUKS, you would give it a GUID of CA7D7CCB-63ED-4C53-861C-1742536059CC (defined as "LUKS partition"). And so on and so forth.
tl;dr: the partition unique GUID identifies that exact partition. The partition GUID code identifies the type of data inside that particular partition.
Best Answer
That link you posted looks like a very ugly hack type solution.
However, according to the man page,
gdisk, which is used to convert MBR -> GPT, also has an option in the "recovery & transformation" menu (pressrto get that) to convert GPT -> MBR; thegkey will:I'd try that first.