Re: Bug#960265: s390x install Debootstrap warning: Failure while configuring base packages. s390-tools depends on perl:any.
Hi
I'm new on that list and and notified (from another -email address -
that will be removed), about my desire to help and contribute that
port. Please don't remove it, Debian is only one of two free (not
charged) distributions.
The mainframe platform is evolving, now exist not only IBM Z servers
but also fully dedicated to Linux the LinuxONE servers. I know from
one case in Poland, taht it was very successful to supersede AIX
installation by LinuxOne installation with Oracle database as main
engine.
I also met the problem witch perl:any dependency (and a few others
during installation), but I resolved them using another installation
(trial RedHat) and debootstrap (with foreign option). The additional
difficulty was lack of Internet access (it is normal in some
environments), but I was determined.
In my opinion the big problem may be w ith access to the real platform
(currently I have access and possibilities but I don't know how long).
Of course we have emulators like hercules (which I use from very long
time) and know qemu s390 port (only with virtio, not tested by me),
but it is probably not enough in power (as long as yo don't have very
powerful emulation platform or use cross-compile). Anyway if Debian
maintainers have access to valid build environment, I think you should
not remove the architecture.
Kind Regards
Piotr (aka nome)
niedz., 14 cze 2020 o 17:20 Philipp Kern <pkern@debian.org> napisał(a):
>
> On 11.05.20 11:53, Winfried Münch wrote:
> > package: s390-tools
> >
> > Version: current Installer from 04.05.2020 21:14
> > http://ftp.halifax.rwth-aachen.de/debian/dists/buster/main/installer-s390x/current/images/generic/
> >
> >
> > When I install debian I run in this Problem (from console 4):
> >
> > May 11 09:43:43 debootstrap: Errors were encountered while processing:
> > May 11 09:43:43 debootstrap: s390-tools
> > May 11 09:43:44 debootstrap: dpkg: dependency problems prevent
> > configuration of s390-tools:
> > May 11 09:43:44 debootstrap: s390-tools depends on perl:any.
> > May 11 09:43:44 debootstrap:
> > May 11 09:43:44 debootstrap: dpkg: error processing package s390-tools
> > (--configure):
> > May 11 09:43:44 debootstrap: dependency problems - leaving unconfigured
> >
> > Installation failed in step install base system.
>
> perl:any is not part of the transitive closure that debootstrap
> calculates. To me it looks like a bug in debootstrap in that it does not
> find a deb to download because it does not drop the :any - either in
> pkgdetails or before.
>
> This was presumably broken by 2.3.0-1 which packaged ziomon and included
> a ${perl:Depends} on the main package as well - possibly because Lintian
> alerted about the missing dependency. That was technically correct, as
> it includes binaries that require modules from perl rather than
> perl-base. And it would presumably have worked if "perl:any" had instead
> been substituted as "perl".
>
> It's pretty telling how late this was discovered, sort of pointing out
> that Debian s390x has no users at all if that kind of bug slips into a
> stable release. Ubuntu forked the base tooling and thus was not
> affected. To be honest, that tells me that the port should be demoted
> and not be part of the next release. Especially given the lack of
> (motivated) porters.
>
> Furthermore it seems like the current debian-installer daily build does
> not boot and ends up in disabled PSW before printing even a single line
> of output.
>
> I never managed to get any kind of continuous integration going myself
> given how hard it is to integrate with existing Debian infrastructure to
> test it properly - unless you are an admin there already. Even a qemu
> setup would have spotted this particular bug. But without any users who
> care I also don't think it is worth spending much time on this.
>
> Kind regards and sorry
> Philipp Kern
>
Reply to: