Closed koppor closed 12 months ago
Hi @koppor, the reason it doesn't give an informative message is because this is an unexpected scenario. Normally that message is when the user has put in empty packages as an arg.
I believe this bug was introduced in PR 104 and v1.3.0 will not contain this error. I have some time today and am going to try and get it all resolved since it is fairly outstanding.
From the output you posted it looks like it couldn't grab any of the package info.
+++ apt-cache --quiet=0 --no-all-versions show libfile-copy-recursive-perl
+++ grep -E '^(Package|Version|N):'
++ data=
Although a local run of the function get_normalized_package_list libfile-copy-recursive-perl
produces
+++ apt-cache --quiet=0 --no-all-versions show libfile-copy-recursive-perl
+++ grep -E '^(Package|Version|N):'
++ data='Package: libfile-copy-recursive-perl
Version: 0.45-1'
I am curious to see what apt-cache --quiet=0 --no-all-versions show libfile-copy-recursive-perl
produces on your runner. Can you link to your action file that you are using?
Thank you for the quick reply @awalsh128.
It is a no-issue, because the workflow does not run on Ubuntu. I am very sorry for the noise!
Deep link to the usage of a docker image: https://github.com/gi-ev/biblatex-lni/blob/59ca278df4b2d489d33f0723eab81d129fc168bf/.github/workflows/check.yml#L33
I ran following
I get following output
Why does it say
But fails with
On a random Ubuntu machine, the output of apt-cache show is as follows
The requested package exists: https://packages.debian.org/buster/libfile-copy-recursive-perl
PR is https://github.com/gi-ev/biblatex-lni/pull/22
There should be at least some hint in the README.md what to do if "Packages argument cannot be empty." is shown.