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

From	RavenLX <ravenlx@sitesplace.net>
Newsgroups	linux.debian.user
Subject	Re: Error on install: Repository "couldn't be accessed"
Date	2017-05-27 13:40 +0200
Message-ID	<tLIeB-2RJ-5@gated-at.bofh.it> (permalink)
References	(1 earlier) <tIasO-5zp-13@gated-at.bofh.it> <tItlM-2Zs-15@gated-at.bofh.it> <tKiFA-4he-13@gated-at.bofh.it> <tKZrd-7Fs-49@gated-at.bofh.it> <tLitP-3mP-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 05/26/2017 04:02 AM, Mark Fletcher wrote:
> On Thu, May 25, 2017 at 07:36:08AM -0400, RavenLX wrote:
>> On 05/23/2017 10:07 AM, Robert Hardy (r.hardy) wrote:
>>> Err http://deb.debian.org jessie-updates/main Translation-en
>>
>> In my setup it's:
>>
>> http://deb.debian.org jessie/updates main contrib non-free
>>
>> Note that it's jessie/updates not jessie-updates. Replace the hyphen with a
>> dash in your sources.list and update again. See if that works?
>>
> Why would it be jessie/updates? Looking at deb.debian.org/debian/dists
> with a web browser, there is no updates/ folder under jessie/ but there
> is a jessie-updates/ folder...

You're right. My bad. I was reading security.debian.org line and not 
paying attention. Sorry about that. Mr. Hardy has the correct URL.

Another thing he can try is to move the affected lists from:

/var/lib/apt/lists
/var/lib/apt/lists/partial

Do another apt-get update and see if that helps. If not, you can always 
put the lists back, if you need to. Generally doing apt-get update after 
moving the lists out of those directories will refresh those lists.

That works for bad checksums when checking for updates, but not sure if 
that will help in Mr. Hardy's situation. Worth a try, maybe?

Back to linux.debian.user | Previous | Next — Previous 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