upvote

points

by walrus0112 hours ago |
comments
upvoteby prima-facie11 hours ago|
next
[-]
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`.

reply
upvoteby 14u2c8 hours ago|
parent|
next
[-]
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

cd Qwen3.8-27B-GGUF

git lfs pull --include="Qwen3.8-27B-UD-Q8_K_XL.gguf" --exclude=""

reply
upvoteby hedora9 hours ago|
parent|
prev|
[-]
That's terrible. My computer shipped with a filesystem and curl.
reply
upvoteby cicko5 hours ago|
parent|
next
[-]
You can't run models with filesystem and curl.
reply
upvoteby embedding-shape2 hours ago|
parent|
[-]
To be fair, you can't run models with "hf download" either...
reply
upvoteby mycall9 hours ago|
parent|
prev|
[-]
There is always SHA256 as the alternative.
reply
upvoteby jlbprof11 hours ago|
prev|
next
[-]
How can I tell which one I have? I dl'd mine a few days ago.
reply
upvoteby walrus0111 hours ago|
parent|
[-]
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.

reply
upvoteby CMay11 hours ago|
parent|
[-]
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.
reply
upvoteby m46311 hours ago|
prev|
[-]
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.
reply
upvoteby walrus0111 hours ago|
parent|
[-]
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.
reply
upvoteby gunalx11 hours ago|
parent|
[-]
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)
reply
upvoteby nagaiaida9 hours ago|
parent|
[-]
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
reply