You are not logged in.
Pages: 1
If there is not already a bug report please submit one at bugs.devuan.org
I edited the other thread and the above post to reflect the situation.
after mucking around a bit I just realized the contents of those Packages.xz (package info) is not the same as Contents.gz (hostfs => pkgfs)
EDIT: in fact after a quick check it turns out @golinux is right, there is no issue with the original script IF your repo points to deb.devuan.org
there is now a 100% solution, no patch needed the Devuan Jessie repos
EDIT: in fact after a quick check it turns out @golinux is right, there is no issue with the original script IF your repo points to deb.devuan.org:
https://dev1galaxy.org/viewtopic.php?pid=11397#p11397
Count_Cucaracha wrote:GNUser wrote:Here's a robust workaround for the time being
Its robustness was short-lived as that option to apt-file no longer exists.
More information as to why not would be helpful. Perhaps it was PEBKAC . . .
that "workaround" wont help, because it searches the contents of the copied apt-file caches and uses the Debian repos, NOT the Devuan repos and caches created from them.
https://dev1galaxy.org/viewtopic.php?id=2291
looks for "dir/Content-_arch_.gz" instead of "dir/binary-_arch_/Packages.gz"
Cheers
Paul
Not the Devuan team. https://pkginfo.devuan.org/cgi-bin/d1pk … elease=any Talk to Debian. We have not touched that package.
In Devuan ASCII the problem went away.
can a Devuan patch be applied to the Jessie repos to fix this, from a diff between Dev1 Jessie & Dev1 Ascii then?
"apt-file" perl script is bugged in Devuan 1 (jessie-stable-old?)
looks for "dir/Content-_arch_.gz" instead of "dir/binary-_arch_/Packages.gz"
use "apt-file -v update" to reproduce debug confirmation of issue.
Why was this package allowed thru? Does the same bug appear in Devuan 2? Someone is letting the team down ...
Update
it appears the solution is simply to change repos to point to deb.devuan.org.
Pages: 1