Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #181093

Re: Error on install: Repository "couldn't be accessed"

From Liam O'Toole <liam.p.otoole@gmail.com>
Newsgroups linux.debian.user
Subject Re: Error on install: Repository "couldn't be accessed"
Date 2017-05-18 15:10 +0200
Message-ID <tItlM-2Zs-15@gated-at.bofh.it> (permalink)
References <tIaj8-5vV-13@gated-at.bofh.it> <tIasO-5zp-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 2017-05-17, RavenLX <ravenlx@sitesplace.net> wrote:
>
>
> On 05/17/2017 12:20 PM, Robert Hardy (r.hardy) wrote:
>> Hi,
>> 
>> I received this message when installing from the Debian 8.8 netinstall 
>> ISO (debian-8.8.0-amd64-netinst.iso)
>> 
>> Initial error was for ftp.uk.debian.org <ftp://ftp.uk.debian.org>. I 
>> tried several others (including ftp.fr.debian.org 
>> <ftp://ftp.fr.debian.org> and  mirror.bytemark.co.uk) with similar errors.
>> 
>> Continued with the install, which appeared to go OK otherwise. Found 
>> that two lines were commented out in sources.list, post install:
>> 
>> # jessie-updates, previously known as 'volatile'
>> 
>> # Line commented out by installer because it failed to verify:
>> 
>> #deb http://ftp.uk.debian.org/debian/ jessie-updates main
>> 
>> # Line commented out by installer because it failed to verify:
>> 
>> #deb-src http://ftp.uk.debian.org/debian/ jessie-updates main
>> 
>> Uncommented these, and received the following errors on running apt-get 
>> update:
>> 
>> Hit http://ftp.uk.debian.org jessie/main Translation-en
>> 
>> Err http://ftp.uk.debian.org jessie-updates/main Translation-en
>> 
>> Err http://ftp.uk.debian.org jessie-updates/main Translation-en
>> 
>> Err http://ftp.uk.debian.org jessie-updates/main Translation-en
>> 
>>    404  Not Found [IP: 78.129.164.123 80]
>> 
>> Fetched 168 kB in 6min 3s (463 B/s)
>> 
>> W: Failed to fetch 
>> http://ftp.uk.debian.org/debian/dists/jessie-updates/main/i18n/Translation-en  
>> 404  Not Found [IP: 78.129.164.123 80]
>> 
>> E: Some index files failed to download. They have been ignored, or old 
>> ones used instead.
>> 
>>   * Is this a known issue?
>>   * Should I have any concerns about stability / missing files follow this?
>> 
>> Thanks,
>> 
>> Rob
>
> I had that happened. I then changed all the http://ftp.* to 
> http://httpredir.debian.org. I learned of this here:
>
> https://wiki.debian.org/SourcesList#Example_sources.list
>
> Then I apt-get update and it worked fine from there.

Just a FYI: the recommended redirector is now http://deb.debian.org/.

-- 

Liam

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Error on install: Repository "couldn't be accessed" "Robert Hardy (r.hardy)" <r.hardy@yorksj.ac.uk> - 2017-05-17 18:50 +0200
  Re: Error on install: Repository "couldn't be accessed" RavenLX <ravenlx@sitesplace.net> - 2017-05-17 19:00 +0200
    Re: Error on install: Repository "couldn't be accessed" Liam O'Toole <liam.p.otoole@gmail.com> - 2017-05-18 15:10 +0200
      Re: Error on install: Repository "couldn't be accessed" RavenLX <ravenlx@sitesplace.net> - 2017-05-21 14:40 +0200
        Re: Error on install: Repository "couldn't be accessed" Matthew McKinnon <comprofix@list.comprofix.com> - 2017-05-22 01:10 +0200
          Re: Error on install: Repository "couldn't be accessed" Brian <ad44@cityscape.co.uk> - 2017-05-22 01:20 +0200
            Re: Error on install: Repository "couldn't be accessed" Matthew McKinnon <comprofix@list.comprofix.com> - 2017-05-22 02:00 +0200
              Re: Error on install: Repository "couldn't be accessed" Brian <ad44@cityscape.co.uk> - 2017-05-22 02:20 +0200
                Re: Error on install: Repository "couldn't be accessed" Matthew McKinnon <comprofix@list.comprofix.com> - 2017-05-22 05:50 +0200
                Re: Error on install: Repository "couldn't be accessed" Brian <ad44@cityscape.co.uk> - 2017-05-22 12:20 +0200
                Re: Error on install: Repository "couldn't be accessed" RavenLX <ravenlx@sitesplace.net> - 2017-05-25 13:50 +0200
                Re: Error on install: Repository "couldn't be accessed" Darac Marjal <mailinglist@darac.org.uk> - 2017-05-26 10:20 +0200
                Re: Error on install: Repository "couldn't be accessed" Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-05-27 10:20 +0200
      RE: Error on install: Repository "couldn't be accessed" "Robert Hardy (r.hardy)" <r.hardy@yorksj.ac.uk> - 2017-05-23 16:10 +0200
        Re: Error on install: Repository "couldn't be accessed" Liam O'Toole <liam.p.otoole@gmail.com> - 2017-05-24 13:10 +0200
        Re: Error on install: Repository "couldn't be accessed" RavenLX <ravenlx@sitesplace.net> - 2017-05-25 13:50 +0200
          Re: Error on install: Repository "couldn't be accessed" Mark Fletcher <mark27q1@gmail.com> - 2017-05-26 10:10 +0200
            Re: Error on install: Repository "couldn't be accessed" Liam O'Toole <liam.p.otoole@gmail.com> - 2017-05-26 11:10 +0200
              Re: Error on install: Repository "couldn't be accessed" Mark Fletcher <mark27q1@gmail.com> - 2017-05-27 07:20 +0200
            Re: Error on install: Repository "couldn't be accessed" RavenLX <ravenlx@sitesplace.net> - 2017-05-27 13:40 +0200

csiph-web