Dear Andrey Rakhmatullin, you wrote: > > Package: icmake,libbobcat6 > Severity: serious > Tags: ftbfs > > As src:icmake B-D:libbobcat-dev, src:bobcat B-D:icmake, there seems to be zero > packaging-level support for bootstrapping, the packages are not > cross-buildable > and the upstream bootstrapping instructions are too tedious, I'm filing this > for visibility (as there are ~14 packages B-D:libbobcat-dev).
Thanks for your bug report. You write: > there seems to be zero packaging-level support for bootstrapping, the > packages are not cross-buildable and the upstream bootstrapping instructions > are too tedious, So far no issues were encountered when the bootstrapping procedure as described in the README.bobatbootstrap file in icmake's src distribution is followed. If you could be a bit more specific about what you mean by 'bootstrapping instructions are too tedious' then I'm sure those instructions can be changed so that they're less tedious. Wrt the package not being cross-buildable: The https://packages.debian.org/sid/libbobcat-dev shows the following lines for armel and armhf: armel 6.04.00-1 1,604.2 kB 8,598.0 kB [list of files] armhf 6.04.00-1 1,608.4 kB 8,126.0 kB [list of files] although I also see packages for which version 6.04.00-1+b2 or 6.04.00-1+b4 is listed. So maybe for unstable some issues recently appeared? Also, the bootstrapping procedure is only required when icmake isn't avaialble yet. For the construction of the bobcat library icmake 11.01.02-1 is required, and icmake.01.02-1 needs libbobcat-dev >= 5.07.00, which is available since bullseye (oldstable). So maybe you can also provide some info about why the bootstrapping procedure is needed/used? In any case: the dependence on icmake when constructing the full bobcat library could be avoided, but I'd rather not do that once icmake *is* available. So please advise. -- Frank B. Brokken (+31) 6 5353 2509 PGP Key Fingerprint: DF32 13DE B156 7732 E65E 3B4D 7DB2 A8BE EAE4 D8AA
signature.asc
Description: PGP signature
