On Fri, 5 Jul 2019 at 01:03, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:

Hello!

I just uploaded updated installation images 2019-07-04 for the
following Debian Ports architectures:

* alpha
* hppa
* ia64
* m68k
* powerpc
* ppc64
* sh4
* sparc64

I uploaded both CD images [1] as well as netboot images [2].

Please test those images and report back over the mailing list for
the corresponding architecture.

Thank you for producing these! I'm new today to hardware ports (though
I have been a debian hurd-i386 user for many years). I have
successfully used this ia64 image to install to my stylish combination slim-line space heater and secure ambient noise generator.

It's an HP Integrity rx2620 with iLO MP and a single mckinley at 1.4
GHz and 6 GiB of RAM.

I had the same issue that Frank Scheiner had regarding vim-tiny on the
rx2660 (thank you Frank for the detailed explanation of your
experience). This one was supremely frustrating as editing bootstrap-base.postinst after the first install attempt and retrying
the install leads to failing to extract a .tar (file exists!) wheras
performing the partitioning step again would lead to the cdrom
becoming unmounted; and d-i would not give me the option to remount
the cdrom before continuing onto the next step until I restarted the
install in expert mode. Editing the file before detecting disks
seemed to work however.

I have not tested running without the radeon module blacklisted; I
will do once I have the machine configured for use.

--
William Leslie

Notice:
Likely much of this email is, by the nature of copyright, covered
under copyright law. You absolutely MAY reproduce any part of it in
accordance with the copyright law of the nation you are reading this
in. Any attempt to DENY YOU THOSE RIGHTS would be illegal without
prior contractual agreement.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 7/6/19 10:39 PM, William ML Leslie wrote:

I had the same issue that Frank Scheiner had regarding vim-tiny on the
rx2660 (thank you Frank for the detailed explanation of your
experience).

The problem is the vim package which failed to build from source on ia64
again [1]. If I build installation images after the vim package has failed
to build, the issue you are describing occurs. The explanation why a vim package that fails to build blocks the installation is explained in [2].

I will build the vim package manually now with the testsuite disabled but someone needs to have a look at vim on alpha and ia64 and fix the package.

Adrian

[1] https://buildd.debian.org/status/package.php?p=vim&suite=unstable
[2] https://lists.debian.org/debian-sparc/2017/12/msg00060.html

--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi!

On 7/7/19 12:07 AM, John Paul Adrian Glaubitz wrote:

The problem is the vim package which failed to build from source on ia64 again [1]. If I build installation images after the vim package has failed
to build, the issue you are describing occurs. The explanation why a vim package that fails to build blocks the installation is explained in [2].

I will build the vim package manually now with the testsuite disabled but someone needs to have a look at vim on alpha and ia64 and fix the package.

This issue should be fixed in today's images now [1].

Thanks,
Adrian

[1] https://cdimage.debian.org/cdimage/ports/2019-07-07/

--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)