debian-sid build for RISCV64 broken

debian-sid build for RISCV64 broken

[MOESSBAUER, Felix]

Dear devs,

we currently cannot build the riscv64 targets, as the sbuild chroot
packages have conflicting internal dependencies. This happens quite
frequently due to updates to the upstream sid repositories.

I'm wondering if we should pin riscv64 to snapshots.debian.org to avoid
these breaks. However, there we are rate-limited, making our builds
rather slow / unstable.

I'm open for other approaches, but would highly appreciate if we could
have a stable riscv64 build.

Best regards,
Felix

-- 
Siemens AG, Linux Expert Center
Otto-Hahn-Ring 6, 81739 München, Germany

Re: debian-sid build for RISCV64 broken

[Jan Kiszka]

On 10.11.23 09:13, 'MOESSBAUER, Felix' via isar-users wrote:
> Dear devs,
> 
> we currently cannot build the riscv64 targets, as the sbuild chroot
> packages have conflicting internal dependencies. This happens quite
> frequently due to updates to the upstream sid repositories.
> 
> I'm wondering if we should pin riscv64 to snapshots.debian.org to avoid
> these breaks. However, there we are rate-limited, making our builds
> rather slow / unstable.
> 
> I'm open for other approaches, but would highly appreciate if we could
> have a stable riscv64 build.
> 

RISC-V crossbuilding is broken, and is expected to remain broken for
some more month according to what I heard from Debian folks. Native
building against sid worked the last time I tried, but it's not
practical for anything that needs an own kernel etc.

Using snapshot means going back to early this year, using sid-ports
again - while it is also not working reliably due to server issues and
throttling of that service. That's what we are stuck with on
isar-cip-core side.

Jan

-- 
Siemens AG, Technology
Linux Expert Center

Re: debian-sid build for RISCV64 broken

[MOESSBAUER, Felix]

On Fri, 2023-11-10 at 09:22 +0100, Jan Kiszka wrote:
> On 10.11.23 09:13, 'MOESSBAUER, Felix' via isar-users wrote:
> > Dear devs,
> > 
> > we currently cannot build the riscv64 targets, as the sbuild chroot
> > packages have conflicting internal dependencies. This happens quite
> > frequently due to updates to the upstream sid repositories.
> > 
> > I'm wondering if we should pin riscv64 to snapshots.debian.org to
> > avoid
> > these breaks. However, there we are rate-limited, making our builds
> > rather slow / unstable.
> > 
> > I'm open for other approaches, but would highly appreciate if we
> > could
> > have a stable riscv64 build.
> > 
> 
> RISC-V crossbuilding is broken, and is expected to remain broken for
> some more month according to what I heard from Debian folks. Native
> building against sid worked the last time I tried, but it's not
> practical for anything that needs an own kernel etc.

Yes, for all practical use-cases we must have cross support.
Do we have any references that state this? Can we somehow get involved
to speedup fixing this?

> 
> Using snapshot means going back to early this year, using sid-ports
> again - while it is also not working reliably due to server issues
> and
> throttling of that service. That's what we are stuck with on
> isar-cip-core side.

This is more or less a showstopper for any work on porting things to
riscv64 in debian. We cannot even do prototypical porting of
applications anymore, as things simply don't build. What a bummer.

In the past it was at least somehow stable and could be used for
prototyping.

Felix

> 
> Jan
> 

Re: debian-sid build for RISCV64 broken

[Jan Kiszka]

On 10.11.23 09:37, MOESSBAUER, Felix (T CED INW-CN) wrote:
> On Fri, 2023-11-10 at 09:22 +0100, Jan Kiszka wrote:
>> On 10.11.23 09:13, 'MOESSBAUER, Felix' via isar-users wrote:
>>> Dear devs,
>>>
>>> we currently cannot build the riscv64 targets, as the sbuild chroot
>>> packages have conflicting internal dependencies. This happens quite
>>> frequently due to updates to the upstream sid repositories.
>>>
>>> I'm wondering if we should pin riscv64 to snapshots.debian.org to
>>> avoid
>>> these breaks. However, there we are rate-limited, making our builds
>>> rather slow / unstable.
>>>
>>> I'm open for other approaches, but would highly appreciate if we
>>> could
>>> have a stable riscv64 build.
>>>
>>
>> RISC-V crossbuilding is broken, and is expected to remain broken for
>> some more month according to what I heard from Debian folks. Native
>> building against sid worked the last time I tried, but it's not
>> practical for anything that needs an own kernel etc.
> 
> Yes, for all practical use-cases we must have cross support.
> Do we have any references that state this? Can we somehow get involved
> to speedup fixing this?

I exchange an email with Helmut Grohne back then, but he strongly
recommended going for debian-cross@lists.debian.org for any further
discussions.

> 
>>
>> Using snapshot means going back to early this year, using sid-ports
>> again - while it is also not working reliably due to server issues
>> and
>> throttling of that service. That's what we are stuck with on
>> isar-cip-core side.
> 
> This is more or less a showstopper for any work on porting things to
> riscv64 in debian. We cannot even do prototypical porting of
> applications anymore, as things simply don't build. What a bummer.
> 
> In the past it was at least somehow stable and could be used for
> prototyping.

I know. Another reason to shop for an update / plan on that debian list.

Jan

-- 
Siemens AG, Technology
Linux Expert Center