Re: Latest sparc64 installer ISO - no kernel modules were found

2018-03-20 Thread John Conner
Hi,

Thread from Feb: did the ISO image get rebuilt at all?  I've got the same
problem...

Thanks!

John


Re: Latest sparc64 installer ISO - no kernel modules were found

2018-02-09 Thread Frank Scheiner

On 02/08/2018 10:24 PM, John Paul Adrian Glaubitz wrote:

On 02/08/2018 10:22 PM, Frank Scheiner wrote:

Thanks, I tried this one this evening, but although the kernel modules are 
there now, the base installation fails due to a dependency problem of the 
vim-tiny
editor:
(...)> What can we do about that?


You can fix src:vim on hppa and sparc64:


https://buildd.debian.org/status/package.php?p=vim&suite=sid


Well, it looks like it got fixed by a rebuild with an updated toolchain 
or/and updated packages (compare [1] and [2] after:

```
+--+
| Build environment 
  |

+--+
```
).

[1]: 
https://buildd.debian.org/status/fetch.php?pkg=vim&arch=sparc64&ver=2%3A8.0.1453-1&stamp=1518005728&raw=0


[2]: 
https://buildd.debian.org/status/fetch.php?pkg=vim&arch=sparc64&ver=2%3A8.0.1453-1&stamp=1518126708&raw=0


I assume a rebuild of the ISO is still required, because the packages 
for the base install are included on the ISO, right?




For hppa I don't know if changing `bwipe` to `bwipe!` (on [3]) would 
make the failing test "Test_terminal_special_chars" ("Caught exception 
in Test_terminal_special_chars(): Vim(bwipeout):E89: No write since last 
change for buffer 44 (add ! to override) @ function 
RunTheTest[38]..Test_terminal_special_chars, line 13" from [4]) succeed. 
At least the test before it ends with `bwipe!`. But on the other hand if 
it succeeds as is on most other arches, why should we change it on hppa?


[3]: 
https://github.com/vim/vim/blob/218101442e8775bd1f05d1dda18d3946ee032dd1/src/testdir/test_terminal.vim#L620


[4]: 
https://buildd.debian.org/status/fetch.php?pkg=vim&arch=hppa&ver=2%3A8.0.1453-1&stamp=1518031946&raw=0




Re: Latest sparc64 installer ISO - no kernel modules were found

2018-02-08 Thread John Paul Adrian Glaubitz
On 02/08/2018 10:22 PM, Frank Scheiner wrote:
> Thanks, I tried this one this evening, but although the kernel modules are 
> there now, the base installation fails due to a dependency problem of the 
> vim-tiny
> editor:
> (...)> What can we do about that?

You can fix src:vim on hppa and sparc64:

> https://buildd.debian.org/status/package.php?p=vim&suite=sid

Adrian

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



Re: Latest sparc64 installer ISO - no kernel modules were found

2018-02-08 Thread Frank Scheiner

On 02/07/2018 08:38 PM, John Paul Adrian Glaubitz wrote:

On 02/07/2018 11:47 AM, John Paul Adrian Glaubitz wrote:

Yes, I forgot to bump the kernel version inside debian-installer. This is an 
easy fix.

I will do that later today and then rebuild the installer images.


New images are up - untested, of course.


Thanks, I tried this one this evening, but although the kernel modules 
are there now, the base installation fails due to a dependency problem 
of the vim-tiny editor:


```
[...]
Feb  8 20:52:56 debootstrap: Errors were encountered while processing: 

Feb  8 20:52:56 debootstrap:  vim-tiny 

Feb  8 20:52:57 debootstrap: dpkg: dependency problems prevent 
configuration of vim-tiny:
Feb  8 20:52:57 debootstrap:  vim-tiny depends on vim-common (= 
2:8.0.1401-2); h


   however:
Feb  8 20:52:57 debootstrap:   Version of vim-common on system is 
2:8.0.1453-1.
Feb  8 20:52:57 debootstrap: 

Feb  8 20:52:57 debootstrap: dpkg: error processing package vim-tiny 
(--configur


   re):
Feb  8 20:52:57 debootstrap:  dependency problems - leaving unconfigured

Feb  8 20:55:03 base-installer: error: exiting on error 
base-installer/debootstrap-failed
Feb  8 20:55:05 main-menu[208]: WARNING **: Configuring 'bootstrap-base' 
failed


with error code 1
Feb  8 20:55:05 main-menu[208]: WARNING **: Menu item 'bootstrap-base' 
failed.
Feb  8 20:55:09 main-menu[208]: INFO: Modifying debconf priority limit 
from 'hig


   gh' to 'medium'
Feb  8 20:55:09 debconf: Setting debconf/priority to medium 

Feb  8 20:55:12 main-menu[208]: INFO: Falling back to the package 
description fo


   or brltty-udeb
```

What can we do about that?

Cheers,
Frank



Re: Latest sparc64 installer ISO - no kernel modules were found

2018-02-07 Thread John Paul Adrian Glaubitz
On 02/07/2018 11:47 AM, John Paul Adrian Glaubitz wrote:
> Yes, I forgot to bump the kernel version inside debian-installer. This is an 
> easy fix.
> 
> I will do that later today and then rebuild the installer images.

New images are up - untested, of course.

Adrian

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



Re: Latest sparc64 installer ISO - no kernel modules were found

2018-02-07 Thread John Paul Adrian Glaubitz
Hi!

Yes, I forgot to bump the kernel version inside debian-installer. This is an 
easy fix.

I will do that later today and then rebuild the installer images.

Adrian

> On Feb 7, 2018, at 9:16 AM, Frank Scheiner  wrote:
> 
> Dear Adrian,
> 
> I just tried the latest sparc64 installer ISO from 2018-02-06 19:28h (from 
> [1]) on my T5220 and shortly after starting the "normal" installation mode I 
> get the following message:
> 
> ```
> No kernel modules were found. This probably is due to a mismatch
> between the kernel used by this version of the installer and the
> kernel version available in the archive.
> [...]
> ```
> 
> ...titled "[!!] Load installer components from CD".
> 
> [1]: https://cdimage.debian.org/cdimage/ports/
> 
> The used kernel version string is:
> 
> ```
> Linux version 4.14.0-1-sparc64 (debian-ker...@lists.debian.org) (gcc version 
> 7.2.0 (Debian 7.2.0-16)) #1 Debian 4.14.2-1 (2017-11-30)
> ```
> 
> I assume it's useless to continue at this point but better wait for a new 
> installer ISO, right?
> 
> Cheers,
> Frank