[BUG] Inconsistent integrity checksums for Github repositories when switching between machines about pacote HOT 2 CLOSED

If you are installing with npm 6, then yes, the tarballs will be different across different operating systems, because of the OS flag included in all gzip files by zlib. That's fixed in npm v7.

I'm getting the same results in OS X and Ubuntu using npm 7 and pacote 11. I also get the same result creating a tarball from a checkout of the same repo locally:

$ npx pacote tarball ./test-pacote-data yy.tar.gz
{
  integrity: 'sha512-PjIPQu6kTUJLRLaAqb9XRWjt32RMjUCBFe92IpOKRQBlK6ACqnI4mUFmFxC8NuZo67KXbX9MLTebE9xMKIqECQ==',
  resolved: '/home/isaacs/test-pacote/test-pacote-data',
  from: 'file:test-pacote-data'
}

$ npx pacote tarball "github:skress/test-pacote-data" xx.tar.gz
{
  integrity: 'sha512-PjIPQu6kTUJLRLaAqb9XRWjt32RMjUCBFe92IpOKRQBlK6ACqnI4mUFmFxC8NuZo67KXbX9MLTebE9xMKIqECQ==',
  resolved: 'git+ssh://[email protected]/skress/test-pacote-data.git#9b7d86d0ad05e737a54c5f887e732bbd3b1471d8',
  from: 'github:skress/test-pacote-data'
}

I don't have an apple silicon-based mac to test with, but I can try to track down someone who does.

from pacote.

Thanks for looking at my problem ... so, I just retried it on all systems and I don't know what has happened since my bug report but it seems to be working without problems on all systems now. I had upgraded nodejs/npm to the latest versions already, but on macOS I had already been on npm v7 when reporting the problem (and you wrote that npm v7 fixed it). So that should not explain it. I have upgraded macOS to 11.2 and then 11.2.1 in the last couple of days. Don't know if that might explain anything.

Whatever problem it was, I can't reproduce it anymore. So sorry for the false report (although I am sure that it did not work at that time ...)

Thanks, again ... closing it now

from pacote.