Conversation

@micahflee What do "apt show $PKG" and "apt policy $PKG" say? If they also don't show anything about the package, then something is weird, and I've never seen that situation.

1
0
0

@liw @micahflee i’m using too

apt policy $pkgname

see also debug options in apt.conf man page

apt -o Debug::something policy $pkgname

0
0
1

@micahflee does apt even know about the packages available in that specific repo? Look in /var/lib/apt/lists similar to this: https://superuser.com/questions/1073336/list-all-packages-from-a-repository

0
0
0

@micahflee

Are you sure that it is not Packages.gz? Or doesn't that matter?

I checked with an ancient script that is running a local Debian repository, it uses dpkg-scanpackages and dpkg-scansources to create Packages.gz and Sources.gz files, then writes a Release file and signs it.

1
0
0

@repa @micahflee in repo file usually has whatever is there (with hash). you dont have to have the .gz one

0
0
0

Fixed! The problem was that my repo had Packages.gz files, but not uncompressed Packages files. When I added those, apt is now recognizing my packages

0
0
0