Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Debian Feed - Package can only be downloaded by apt once
-
Hi @dan-brown_0128,
That is odd! We'll see if we can reproduce it and let you know what we find.
-Greg
-
Hi @dan-brown_0128,
I've tried to reproduce this both inside of Docker and on a clean bookworm vm, and haven't had any luck. It works for me whether the package has been pulled to ProGet or not, no matter how many times I try. Unfortunately I don't have any ideas what might be happening here.
-Greg
-
Hi @dan-brown_0128 , @gdivis ,
We received a support ticket that seems to be a similar topic...
I am using a ProGet Debian feed to mirror http://deb.debian.org/debian. I am using it on Debian containers running on my desktop. I have noticed that packages that I had installed already once are no longer available for a second installation. I have attached a screenshot that uses the command "apt update && apt install -y git" as example. According to the error message, the package "git" is unknown.
However when looking it up in the ProGet feed, it is listed as a cached package as it was installed in an earlier execution of the container. I have then set a retention rule on the feed to delete absolutely all packages and run the job manually to clean all packages cached on the feed. When re-executing the exact same command, the package git and its dependencies are found and installed.It appears that cached packages are no longer returned to the Linux instance when executing "apt update". I can force a complete cleanup of the ProGet feed prior to an installation as a workaround but this is a bit tedious.
So I wonder if this has something to do with how we're generating indexes, or something to that effect?
I also asked the other user for input - but we're currently stuck trying to reproduce this, so any other insight would be helpful.
Steve
-
Hi @dan-brown_0128 , @stevedennis
I had that thought too, and I made sure caching was enabled when I tried to reproduce this. I have some more ideas for trying to recreate this today - hopefully with more luck this time.
-
I'm starting to think this is related to package versions with a
+. We can keep going down the road ofunixodbc-common_2.3.11-2+deb12u1_all.debfor example.If I disable the cache and do not pull packages to proget, I can download/install just fine.
If I promote the package to another feed, I cannot install it. BUT if I try a package without a
+in the version/filename in that second feed, it does install or at least resolve (ex: bcal)There is one big difference in the index that might be the key... The original/upstream Debian index does not urlencode the
filenamebut it looks like ProGet isdebian upstream:
Filename: pool/main/u/unixodbc/unixodbc-common_2.3.11-2+deb12u1_all.deb
Proget:Filename: pool/bookworm/main/all/unixodbc-common/unixodbc-common_2.3.11-2%2Bdeb12u1_all.deb -
Oh and also to note: there is no network traffic (captured by our networking team) or from IIS logs when attempting to
apt installunixodbc-common from ProGet (pulled to feed). Maybe apt is thinking that filename is invalid and skips it -
Good find!
I did my testing against
unixodbc-common_2.3.11-2+deb12u1_all.deb, and oddly everything worked- I wonder if this behavior varies in different versions of apt?Anyway, we should change ProGet to match the Debian index behavior, so I will file this as a bug.
-
Hi @dan-brown_0128,
I've done some more research on this, and per the spec we definitely should not be url encoding anything in the Filename field: https://wiki.debian.org/DebianRepository/Format#Filename
I've filed this as PG-2591. It's an easy change, so we'll include it in this week's release on Friday. It still is strange that I couldn't reproduce this, but hopefully this will resolve the issue for you and anyone else that is seeing this.
-
Quick update -- Just installed 2023.30 in our test environment. At first I was still not able to download packages with
+in the version (despite the index being correct). After clearing the feed and re-promoting packages it does seem to work now! -
Great to hear! Thanks for the followup
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login