Hello Vagrant,
On 03/02/2023 03:45, Vagrant Cascadian wrote:
There were definitely cases of packages that had alternate dependencies
that will never be satisfyable (e.g. from contrib or non-free when
building only from main, or even ubuntu), so failing to resolve all
dependencies is not technically an error.
But sure, issuing a warning that reprepro_retries was reached and
suggesting to bump the value if later steps fail due to missing
dependencies seems reasonable...
The mirroring here is definitely a best-effort shotgun approach,
grabbing all the dependencies/recommends of any package you actually
expressed interest in (by putting in a .packages or .downloads file in
one of the profiles), and *trying* to pull in anything mentioned in any
Depends or Recommends or Provides field, recursively... and comparing
the previous run to the current run if anything changed.
If it does not pull in enough, I think debian-cd still
fails... maybe... I guess... hope? :)
In some cases, adding more packages to one of the .downloads files is
the appropriate workaround.
Thanks for the detailed explanations, much appreciated!
Sounds like the default should at least be bumped to a larger value,
then.
That has been the value since at least 2006, picked by finding the right
value at the time for the biggest profile I ever tested and doubling
it... there have been quite a few packages added to Debian since then,
so it is no surprise that it would need to be updated!
Feel free to propose a higher value grounded in a current real world
use-case, and double it. :)
I opened a merge request on Salsa:
https://salsa.debian.org/debian/simple-cdd/-/merge_requests/10
I just doubled the value and made it 40.
From the Kali Linux build logs I can see, the number of attempts goes
from 11 to 20. Unfortunately we don't keep daily build logs, only those
that fail, so I can't really tell what's the average number of attempts,
for example. I just know that "sometimes" we reach 20.
Thanks for looking into it!
Help is definitely appreciated! I have not really looked at simple-cdd
much since the previous release, and simple-cdd surely needs some help
now that we are into the early phases of a freeze cycle!
And thanks for the quick feedback!
By the way, as I see that simple-cdd is in Salsa's debian group: are you
Ok if we (Kali Linux developers, that would be Raphael Hertzog or me)
release the package from time to time, or do you prefer to be taking
care of that?
Cheers,
--
Arnaud Rebillout / Offensive Security / Kali Linux Developer
