2 ms·

It would be nice if unsloth published GGUFs would use a version number or something, because now I have multiple different files on local storage that otherwise

It would be nice if unsloth published GGUFs would use a version number or something, because now I have multiple different files on local storage that otherwise have exactly the same name. "Qwen3.8-27B-UD-Q8_K_XL.gguf" for instance. The one downloaded at least 4 days ago is a different thing and is NOT the "Dynamic 3.0" GGUF which I am now downloading, which I presume will have a different sha256 checksum? The unsloth page says dynamic 3.0 is released "today", but I have an older copy of qwen3.8 27B Q8 which I downloaded, if I remember right, at least 4-5 days ago... https://huggingface.co/unsloth/Qwen3.8-27B-GGUF https://huggingface.co/unsloth/Qwen3.8-27B-GGUF

jlbprof 2mo ago
How can I tell which one I have? I dl'd mine a few days ago.
- walrus01 2mo ago
  I have just run a sha256 checksum on both copies now, the one I downloaded 4-5 days ago, and the one that's on the unsloth huggingface page released today, and will see if they're the same or different. (downloaded in the last few hours after the announcement of dynamic 3.0) Qwen3.8-27B-UD-Q8_K_XL-unsloth-dynamic3.0$ openssl dgst -sha256 *.gguf SHA2-256(Qwen3.8-27B-UD-Q8_K_XL.gguf)= af36ecb6b5db1407953345b746c14ac93f0657dda413910b4348683a2d990377 =====separator========= downloaded at least 4 days ago: Qwen3.8-27B-UD-Q8_K_XL-unsloth-original$ openssl dgst -sha256 Qwen3.8-27B-UD-Q8_K_XL.gguf SHA2-256(Qwen3.8-27B-UD-Q8_K_XL.gguf)= af36ecb6b5db1407953345b746c14ac93f0657dda413910b4348683a2d990377 So they're actually the same thing, but the announcement says released today... Please let's not confuse the end users any more than they already are.
  - CMay 2mo ago
    I think they said they were keeping the old UD 2.0 quant for the larger sizes? So maybe they kept those the same and simply reuploaded them. They said the newer UD 3.0 quant performed worse on some things for the higher quants. So now it's a mix of UD 3.0 and UD 2.0.
m463 2mo ago
I wonder if there should be some kind of header sort of like a README inside mixed with something like EXIF information that camera images embed.
- walrus01 2mo ago
  there's metadata in a GGUF (as can be seen when loading one into llama-server with verbose level 4) but it doesn't appear to show what the expected sha256 of the file is.
  - gunalx 2mo ago
    Well that would not work as the metadata is also part of the sha, and if you have a sha predictably contain or hash to itself you have a bad hashing algorithm. (Unless of course you mean sha of the weigths and not the gguf itself)
    - nagaiaida 2mo ago
      you can just hash the metadata masking out the hash as all zeroes or anything similar to get around that, like header checksums that ostensibly include themselves
  - close04 2mo ago
    With large downloads ideally they'd provide all the info upfront. Even some unique code in the name that you can look up in a readme on the site.
prima-facie 2mo ago
You can manage these easily with the huggingface python app. hf download hf://unsloth/Qwen3.8-27B-GGUF \ Qwen3.8-27B-UD-Q4_K_XL.gguf and then see them with `hf cache ls`. Prune old versions with `hf cache prune`.
- hedora 2mo ago
  That's terrible. My computer shipped with a filesystem and curl.
  - mycall 2mo ago
    There is always SHA256 as the alternative.
  - cicko 2mo ago
    You can't run models with filesystem and curl.
    - embedding-shape 2mo ago
      To be fair, you can't run models with "hf download" either...
      - catchnear4321 2mo ago
        To be fair, the point was more that cURL isn’t a local hf cache manager, much like it isn’t an inference backend, pointing out that avoiding additional dependencies manages risk at the cost of functionality and/or maintenance overhead…
- 14u2c 2mo ago
  Using git is another option, you'll get the actual commits/history to reference: GIT_LFS_SKIP_SMUDGE=1 git clone https://huggingface.co/unsloth/Qwen3.8-27B-GGUF https://huggingface.co/unsloth/Qwen3.8-27B-GGUF cd Qwen3.8-27B-GGUF git lfs pull --include="Qwen3.8-27B-UD-Q8_K_XL.gguf" --exclude=""

jlbprof 2mo ago

How can I tell which one I have? I dl'd mine a few days ago.

walrus01 2mo ago
I have just run a sha256 checksum on both copies now, the one I downloaded 4-5 days ago, and the one that's on the unsloth huggingface page released today, and will see if they're the same or different. (downloaded in the last few hours after the announcement of dynamic 3.0) Qwen3.8-27B-UD-Q8_K_XL-unsloth-dynamic3.0$ openssl dgst -sha256 *.gguf SHA2-256(Qwen3.8-27B-UD-Q8_K_XL.gguf)= af36ecb6b5db1407953345b746c14ac93f0657dda413910b4348683a2d990377 =====separator========= downloaded at least 4 days ago: Qwen3.8-27B-UD-Q8_K_XL-unsloth-original$ openssl dgst -sha256 Qwen3.8-27B-UD-Q8_K_XL.gguf SHA2-256(Qwen3.8-27B-UD-Q8_K_XL.gguf)= af36ecb6b5db1407953345b746c14ac93f0657dda413910b4348683a2d990377 So they're actually the same thing, but the announcement says released today... Please let's not confuse the end users any more than they already are.
- CMay 2mo ago
  I think they said they were keeping the old UD 2.0 quant for the larger sizes? So maybe they kept those the same and simply reuploaded them. They said the newer UD 3.0 quant performed worse on some things for the higher quants. So now it's a mix of UD 3.0 and UD 2.0.

m463 2mo ago

I wonder if there should be some kind of header sort of like a README inside mixed with something like EXIF information that camera images embed.

walrus01 2mo ago
there's metadata in a GGUF (as can be seen when loading one into llama-server with verbose level 4) but it doesn't appear to show what the expected sha256 of the file is.
- gunalx 2mo ago
  Well that would not work as the metadata is also part of the sha, and if you have a sha predictably contain or hash to itself you have a bad hashing algorithm. (Unless of course you mean sha of the weigths and not the gguf itself)
  - nagaiaida 2mo ago
    you can just hash the metadata masking out the hash as all zeroes or anything similar to get around that, like header checksums that ostensibly include themselves
- close04 2mo ago
  With large downloads ideally they'd provide all the info upfront. Even some unique code in the name that you can look up in a readme on the site.

prima-facie 2mo ago

You can manage these easily with the huggingface python app. hf download hf://unsloth/Qwen3.8-27B-GGUF \ Qwen3.8-27B-UD-Q4_K_XL.gguf and then see them with `hf cache ls`. Prune old versions with `hf cache prune`.

hedora 2mo ago
That's terrible. My computer shipped with a filesystem and curl.
- mycall 2mo ago
  There is always SHA256 as the alternative.
- cicko 2mo ago
  You can't run models with filesystem and curl.
  - embedding-shape 2mo ago
    To be fair, you can't run models with "hf download" either...
    - catchnear4321 2mo ago
      To be fair, the point was more that cURL isn’t a local hf cache manager, much like it isn’t an inference backend, pointing out that avoiding additional dependencies manages risk at the cost of functionality and/or maintenance overhead…
14u2c 2mo ago
Using git is another option, you'll get the actual commits/history to reference: GIT_LFS_SKIP_SMUDGE=1 git clone https://huggingface.co/unsloth/Qwen3.8-27B-GGUF https://huggingface.co/unsloth/Qwen3.8-27B-GGUF cd Qwen3.8-27B-GGUF git lfs pull --include="Qwen3.8-27B-UD-Q8_K_XL.gguf" --exclude=""