:: [DNG] Devuan 1.0 Installation Prob…
Top Page
Delete this message
Reply to this message
Author: Alessandro Selli
Date:  
To: dng
Subject: [DNG] Devuan 1.0 Installation Problem
On 25/08/2018 at 03:27, Alessandro Selli wrote:
> On 25/08/2018 at 02:45, Alessandro Selli wrote:
>> On 24/08/2018 at 21:27, Jaromil wrote:
>>> dear Arnt,
>>>
>>> On Fri, 24 Aug 2018, Arnt Karlsen wrote:
>>>
>>>> ..why Devuan 1.0 when you can have Devuan ASCII 2.0.0 stable release?
>>>> https://devuan.org/os/debian-fork/ascii-stable-announce-060818
>>>> which _may_ solve your problem.
>>> I doubt we can say "just use ASCII" as an answer to this problem,
>>> since we have declared Jessie an "LTS" release, we should have this
>>> sorted and stick to our menu. True is that ASCII just works very well,
>>> but then we cannot just leave people who want to use Jessie
>>> behind.
>>>
>>> I hope we can figure out, I haven't yet looked at the screenshots sent
>>> by Gaston
>>   He started the graphical install, selects the English language, then
>> the United States as the timezone location, then the United States as
>> the location of the Devuan mirror.
>>
>>   Next he chose us.mirror.devuan.org as the package manager mirror (the
>> other choice being auto.mirror.devuan.org) and the error windows shows
>> up with:
>>
>> ##########################################################
>> # Bad archive mirror
>> # An error has been detected while trying to use the specified Devuan
>> archive mirror.
>> #
>> # Possible reasons for the error are: incorrect mirror specification;
>> mirror is not available
>> # (possibily due to an unreliable network connection); mirror is broken
>> (for example
>> # because an invalid Release file was found); mirror doe not support the
>> correct Devuan
>> # version.
>> #
>> # Additional details may be available in /var/log/syslog or virtual
>> console 4.
>> #
>> # Please check the specified mirror or try a different one.
>> ##########################################################
>>
>>
>>   I'd suggest Gaston to do check is some error message in
>> /var/log/syslog could help pinpointing the source of the error and to do
>> try selecting another repository server.  And of course to check if the
>> network is configured correctly, if he can resolve and ping
>> us.mirror.devuan.org.
>   Sorry, I did not check all the screenshots: he did.
>
>   I'll try to send the console output, if I can OCR the screenshots quickly.
>
> Alessandro


  First console output:

Aug 24 01:54:27 apt-setup: Please insert a Disc in the driue and press enter
Aug 24 01:54:27 apt-setup:
Aug 24 01:54:27 apt-setup: Mounting CD-ROM...
Aug 24 01:54:27 kernel: [  286.415632] ISO 9660 Extensions: Microsoft
Joliet Level 3
Aug 24 01:54:27 apt-setup: Identifying...
Aug 24 01:54:27 kernel: [  286.416545] ISO 9660 Extensions: RRIP_1991A
Aug 24 01:54:27 apt-setup: [c3f880d2662c18295a70f972e6dfb52a-2]
Aug 24 01:54:27 apt-setup: Scanning disc for index files.
Aug 24 01:54:28 apt-setup: Found 2 package indexes, 0 source indexes, 0
translation indexes and 0 signatures
Aug 24 01:54:28 apt-setup: This disc is called:
Aug 24 01:54:28 apt-setup: 'Debian GNU/Linux 1.0-final _Jessie_ -
Official amd64 NETINST Binary-1 20170522-03:42'
Aug 24 01:54:28 apt-setup: Copying package lists.
Aug 24 01:54:28 apt-setup: _ Reading Package Indexes.   0 i M
Aug 24 01:54:28 apt-setup: _ Reading Package Indexes.   1 i M
Aug 24 01:54:28 apt-setup: _ Reading Package Indexes.   Don ê M
Aug 24 01:54:28 apt-setup:
Aug 24 01:54:28 apt-setup: Writing new source list
Aug 24 01:54:28 apt-setup: Source list entries for this disc are:
Aug 24 01:54:28 apt-setup: deb cdrom:[Debian GNU/Linux 1.0-final
_Jessie_ - Official amd64 NETINST Binary-1 20170522-03:42]/ jessie main
non-free
Aug 24 01:54:28 apt-setup: Unmounting CD-ROM..
Aug 24 01:54:28 apt-setup: Repeat this process for the rest of the CDs
in your set.
Aug 24 01:54:28 kernel: [  286.704605] ISO 9660 Extensions: Microsoft
Joliet Leuel 3
Aug 24 01:54:28 kernel: [  286.705412] ISO 9660 Extensions: RRIP_1991A
Aug 24 01:54:28 kernel: [  286.748938] ISO 9660 Extensions: Microsoft
Joliet Leuel 3
Aug 24 01:54:28 kernel: [  286.749739] ISO 9660 Extensions: RRIP_1991A
Aug 24 01:54:55 choose-mirror[31759]: DEBUG: command: wget -q
http://us.mirror.devuan.org/merged/dists/jessie/Release -O - | grep -E
'^(Suite|Codename|Architectures):'
Aug 24 01:54:57 choose-mirror[31759]: DEBUG: command: wget -q
http://us.mirror.devuan.org/merged/dists/stable/Release -O - | grep -E
'^(Suite|Codename|Architectures):'
Aug 24 01:54:58 choose-mirror[31759]: WARNING _: broken mirror: invalid
Suite or Codename in Release file for stable
Aug 24 01:54:58 choose-mirror[31759]: WARNING _: broken mirror: invalid
Suite in Release file for jessie


  Errors documented by the console log from the other attempts have the
same error message:


Aug 24 01:54:57 choose-mirror[31759]: DEBUG: command: wget -q
http://us.mirror.devuan.org/merged/dists/stable/Release -O - | grep -E
'^(Suite|Codename|Architectures):'
Aug 24 01:54:58 choose-mirror[31759]: WARNING _: broken mirror: invalid
Suite or Codename in Release file for stable

  The command does work for me:

wget -q http://us.mirror.devuan.org/merged/dists/stable/Release -O - |
grep -E '^(Suite|Codename|Architectures):'
Suite: testing
Codename: ascii
Architectures: alpha amd64 arm64 armel armhf hppa i386 ia64 mips mipsel
powerpc ppc64el s390x sparc


  Why is Jessie stable/Release labeled a "testing" suite?


Alessandro




--
Alessandro Selli <alessandroselli@???>
Tel. 3701355486
VOIP SIP: dhatarattha@???
Chiave firma e cifratura PGP/GPG signing and encoding key:
BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE