Bug#1068068: Need rebootstrapping on armel and armhf

2024-03-30 Thread tony mancill
On Sat, Mar 30, 2024 at 01:29:42PM +0500, Andrey Rakhmatullin 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).

Thank you for the bug report.  Frank (the upstream author) is in the
process of updating icmake to no longer depend on bobcat, thus breaking
the cycle.


signature.asc
Description: PGP signature


Bug#1068068: Need rebootstrapping on armel and armhf

2024-03-30 Thread Andrey Rakhmatullin
On Sat, Mar 30, 2024 at 02:14:24PM +0100, Frank B. Brokken wrote:
> > 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. 
It looked to me that I need to make a chroot, run the bootstrap script to
build some kind of local bootstrap bobcat, build local icmake with that
bobcat, build local bobcat with that icmake, build the icmake .deb,
install it in a new chroot, build the bobcat .deb, then ideally build a
clean icmake .deb again; and do that twice as two architectures need
bootstrapping. This is much much much more than I'm going to do for random
packages so I decided against it.

> 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?
Not sure what did you want to say here, sorry? By not being
cross-buildable I mean they lack cross-building support, both at the
packaging level (no proper M-A headers, no B-D annotation) and at the
upstream level (the gcc running was not the cross one).

> 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).
icmake is indeed not available on armel and armhf until libbobcat6 is
rebuilt against libssl3t64.

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Bug#1068068: Need rebootstrapping on armel and armhf

2024-03-30 Thread Frank B. Brokken
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


Bug#1068068: Need rebootstrapping on armel and armhf

2024-03-30 Thread Andrey Rakhmatullin
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).


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled