Apt get update ошибка debian

# dpkg —print-architecture

amd64

# dpkg —print-foreign-architectures

в ответе ничего нет

# uname -a

Linux server1 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux

# ping mirror.mephi.ru -c 4
PING point.mephi.ru (85.143.112.112) 56(84) bytes of data.
64 bytes from 85.143.112.112: icmp_seq=1 ttl=51 time=74.3 ms
64 bytes from 85.143.112.112: icmp_seq=2 ttl=51 time=73.5 ms
64 bytes from 85.143.112.112: icmp_seq=4 ttl=51 time=73.9 ms

— point.mephi.ru ping statistics —
4 packets transmitted, 3 received, 25% packet loss, time 3008ms
rtt min/avg/max/mdev = 73.591/73.984/74.363/0.315 ms

# ping security.debian.org -c 4
PING security.debian.org (133.242.99.74) 56(84) bytes of data.
64 bytes from setoguchi.debian.org (133.242.99.74): icmp_seq=1 ttl=43 time=342 ms
64 bytes from setoguchi.debian.org (133.242.99.74): icmp_seq=2 ttl=43 time=341 ms
64 bytes from setoguchi.debian.org (133.242.99.74): icmp_seq=3 ttl=43 time=341 ms
64 bytes from setoguchi.debian.org (133.242.99.74): icmp_seq=4 ttl=43 time=341 ms

— security.debian.org ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 341.336/341.588/342.032/0.770 ms

[свернуть]

Источник

When using the desktop version of Ubuntu you’ll eventually get or probably have the problem that apt-get update throws a lot «Failed to fetch 404 Not Found» errors. Additionally, you may have the same problem when running apt-get install. Don’t worry, it will be fixed in a minute.

The Problem

You may see messages like the ones below when executing apt-get update or apt-get install. That is because Ubuntu releases are only supported for 9 months. LTS (Long Term Support) releases have support for 5 years. Once support is cut for the version you’re using, you’ll see those error messages. Ubuntu moves the repositories to another server and the defined URL to reach the sources are no longer available on default location http://archive.ubuntu.com/ubuntu/dist/.

$ sudo apt-get update
Ign http://de.archive.ubuntu.com raring Release.gpg  
Ign http://de.archive.ubuntu.com raring-updates Release.gpg  
Ign http://de.archive.ubuntu.com raring-backports Release.gpg  
Ign http://security.ubuntu.com raring-security Release.gpg  
Ign http://de.archive.ubuntu.com raring Release  
Ign http://de.archive.ubuntu.com raring-updates Release  
Ign http://de.archive.ubuntu.com raring-backports Release  
…
404  Not Found [IP: 91.189.92.201 80]  
Err http://security.ubuntu.com raring-security/restricted Sources  
404  Not Found [IP: 91.189.92.201 80]  
Err http://security.ubuntu.com raring-security/universe Sources  
404  Not Found [IP: 91.189.92.201 80]  
Err http://security.ubuntu.com raring-security/multiverse Sources  
404  Not Found [IP: 91.189.92.201 80]  
Ign http://de.archive.ubuntu.com raring-backports/main Translation-en  
Ign http://de.archive.ubuntu.com raring-backports/multiverse Translation-en  
Err http://security.ubuntu.com raring-security/main amd64 Packages  
…

W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/raring/restricted/source/Sources  404  Not Found [IP: 141.30.13.30 80]

W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/raring/universe/source/Sources  404  Not Found [IP: 141.30.13.30 80]

W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/main/source/Sources  404  Not Found [IP: 91.189.92.201 80]

W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/raring/multiverse/source/Sources  404  Not Found [IP: 141.30.13.30 80]

…

E: Some index files failed to download. They have been ignored, or old ones used instead.

How to Fix The Problem

There are two solutions to get your apt commands working again. First: upgrade the Ubuntu release. Second: update the sources url to the old package repositories. Both solutions are described below in more detail.

Distribution Upgrade

The most simple solution is to upgrade your Ubuntu instance to the newest release:

sudo apt-get dist-upgrade

If the distribution upgrade is not an option right now, you can update the sources url for the Ubuntu repositories to find the old packages.

Update Packages Url

You can use the sed command to update the sources in /etc/apt/sources.list file to the new location for old package repositories2.

Run the following command to update archive.ubuntu.com and security.ubuntu.com package repository4 URLs with old-releases.ubuntu.com. Since the normal Ubuntu releases link to the archive.… and security.… URLs, the support will be removed after their live cycle of 9 months and respective repositories3 moved to old-releases.….

sudo sed -i -e 's/archive.ubuntu.com|security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list

**Linux Mint additionally requires the execution of this command:**

sudo sed -i -e 's/archive.ubuntu.com|security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list.d/official-package-repositories.list

To check whether there are other files in /etc/apt/sources.list.d/ which need to be updated, use the following grep command.

grep -E 'archive.ubuntu.com|security.ubuntu.com' /etc/apt/sources.list.d/*

That’s it. Now you can update your sources again.

sudo apt-get update

Bazinga!

  • 1: Myles McNamara’s blog post saved me a lot of time to understand the problem and find a solution
  • 2: Ask Ubuntu: Install Software From Old Repositories (sed command)
  • 3: Ubuntu Old Releases
  • 4: Ubuntu Current Releases
Источник

cat /etc/apt/sources.list

deb http://deb.debian.org/debian jessie main
deb http://deb.debian.org/debian jessie-updates main
deb http://security.debian.org jessie/updates main

then apt-get update is failing.

If i remove the second line then above command is working fine.

I checked in the repositories. there is no folder with name jessie-updates.

We have many docker builds which requires apt-get update.

I can’t update all the docker files to remove that second line.

What is best approach to go ahead and also if they are removed permanently or a temporary glitch

Braiam's user avatar

Braiam

4,6893 gold badges25 silver badges57 bronze badges

asked Mar 26, 2019 at 7:54

3

According to the IRC channel for Debian, jessie-updates is now not supported:

Oldstable: Debian Jessie, jessie-updates and jessie-backports REMOVED 2019-03-24

Your solution is either to upgrade to Stretch, or update your /etc/apt/sources.list to the following:

deb http://archive.debian.org/debian/ jessie main
deb-src http://archive.debian.org/debian/ jessie main

deb http://security.debian.org jessie/updates main
deb-src http://security.debian.org jessie/updates main

jessie-updates has been removed and jessie-backports has been archived

Thanks to comments from Stephen Kitt & Daniel below.

answered Mar 26, 2019 at 9:44

Dan Clarke's user avatar

Dan ClarkeDan Clarke

5083 silver badges5 bronze badges

6

The debian Team did not move jessie-updates to the archive repository (yet). But they already removed it from the regular repositories. So you currently have no access to jessie-updates. Therefore you need to remove it from the sources.list.

My currently working sources.list:

deb http://deb.debian.org/debian jessie main
deb http://security.debian.org/debian-security jessie/updates main

answered Mar 26, 2019 at 14:22

A.K.'s user avatar

A.K.A.K.

1512 bronze badges

5

While the other answers with deb combinations from this thread and others of the stackexchange network, including very similar ones, did not fix it for me, this one does :

deb http://archive.debian.org/debian/ jessie main
deb-src http://archive.debian.org/debian/ jessie main

deb http://archive.debian.org/debian-security jessie/updates main
deb-src http://archive.debian.org/debian/ jessie main

in /etc/apt/sources.list.

It fixed both 404 and gpg key warnings, while the most upvoted does not today for me

answered May 17 at 15:00

NanoPish's user avatar

NanoPishNanoPish

8081 gold badge9 silver badges16 bronze badges

Jessie is no longer supported. They have taken it off the automatic updates for security reasons.

You need to do a full reinstall of bionic beaver.

At least that’s what I did.

answered Mar 27, 2019 at 4:44

AndiAna's user avatar

1

Источник

I’m having problems updating apt.

When run apt-get update

Ign http://dl.google.com stable InRelease
Hit http://ftp.bg.debian.org testing InRelease
Hit http://dl.google.com stable Release.gpg      
Hit http://dl.google.com stable Release          
Hit http://ftp.bg.debian.org testing/main Sources/DiffIndex 
Hit http://ftp.bg.debian.org testing/contrib Sources/DiffIndex
Hit http://ftp.bg.debian.org testing/non-free Sources/DiffIndex
Hit http://ftp.bg.debian.org testing/main armhf Packages/DiffIndex
Hit http://ftp.bg.debian.org testing/contrib armhf Packages/DiffIndex
Hit http://ftp.bg.debian.org testing/non-free armhf Packages/DiffIndex
Hit http://ftp.bg.debian.org testing/main i386 Packages/DiffIndex
Hit http://ftp.bg.debian.org testing/contrib i386 Packages/DiffIndex
Hit http://ftp.bg.debian.org testing/non-free i386 Packages/DiffIndex
Hit http://ftp.bg.debian.org testing/contrib Translation-en/DiffIndex
Hit http://ftp.bg.debian.org testing/main Translation-en/DiffIndex
Hit http://ftp.bg.debian.org testing/non-free Translation-en/DiffIndex
W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release       Unable to find expected entry 'main/binary-armhf/Packages' in Release file (Wrong     sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.

I have no idea where this dl.google.com comes from since my source.list is:

deb http://ftp.bg.debian.org/debian testing main contrib non-free
deb-src http://ftp.bg.debian.org/debian testing main contrib non-free

Thanks in advance.

oxfist's user avatar

oxfist

7176 silver badges21 bronze badges

asked May 13, 2014 at 12:47

selfbg's user avatar

5

I really think that the problem you are facing is caused from some wrong entries on the /etc/apt/sources.list.d/ folder. Check this folder and delete everything related with dl.google.com then retry, and everything should work properly. You probably have installed google-chrome via google’s .deb package and those entries where auto-added on that folder.

NOTE : After doing that your google-chrome will recieve no updates, so for a new version you will have to purge it with dpkg and then redownload and reinstall it yourself.

answered Mar 23, 2015 at 15:38

L0aD1nG's user avatar

L0aD1nGL0aD1nG

1111 silver badge10 bronze badges

Try these steps:

Go to Applications -> 'ubuntu software center'
Click on Edit -> Software Sources
Click on 'Other software' tab
Uncheck the line containing 'http://dl.google.com/linux'
Press Close
Exit 'ubuntu software center'
Retry apt-get update on command-line

answered Mar 4, 2016 at 0:27

user674669's user avatar

user674669user674669

10.4k15 gold badges72 silver badges103 bronze badges

Источник


0

2

Всем здравствуйте!

Debian 8 Netinstall, начал устанавливать поставил mc apache2 mysq-server mysql-client phpmyadmin

все ок, но через пару минут решил продолжить установку пакетов, и получил такую вот ошибку:

1. apt-get update

Игн http://mirror.mephi.ru jessie InRelease
Игн http://mirror.mephi.ru jessie-updates InRelease
Игн http://mirror.mephi.ru jessie Release.gpg
Игн http://mirror.mephi.ru jessie-updates Release.gpg
Игн http://mirror.mephi.ru jessie Release
Игн http://mirror.mephi.ru jessie-updates Release
Игн http://security.debian.org jessie/updates InRelease
Игн http://security.debian.org jessie/updates Release.gpg
Игн http://security.debian.org jessie/updates Release
Ош  http://security.debian.org jessie/updates/main Sources
  404  Not Found
Ош  http://security.debian.org jessie/updates/contrib Sources
  404  Not Found
Ош  http://security.debian.org jessie/updates/non-free Sources
  404  Not Found
Ош  http://security.debian.org jessie/updates/main amd64 Packages
  404  Not Found
Ош  http://security.debian.org jessie/updates/contrib amd64 Packages
  404  Not Found
Ош  http://security.debian.org jessie/updates/non-free amd64 Packages
  404  Not Found
Игн http://security.debian.org jessie/updates/contrib Translation-ru_RU
Игн http://security.debian.org jessie/updates/contrib Translation-ru
Игн http://security.debian.org jessie/updates/contrib Translation-en
Игн http://security.debian.org jessie/updates/main Translation-ru_RU
Игн http://security.debian.org jessie/updates/main Translation-ru
Игн http://security.debian.org jessie/updates/main Translation-en
Игн http://security.debian.org jessie/updates/non-free Translation-ru_RU
Игн http://security.debian.org jessie/updates/non-free Translation-ru
Игн http://security.debian.org jessie/updates/non-free Translation-en
Ош  http://mirror.mephi.ru jessie/main Sources
  404  Not Found
Ош  http://mirror.mephi.ru jessie/non-free Sources
  404  Not Found
Ош  http://mirror.mephi.ru jessie/contrib Sources
  404  Not Found
Ош  http://mirror.mephi.ru jessie/main amd64 Packages
  404  Not Found
Ош  http://mirror.mephi.ru jessie/non-free amd64 Packages
  404  Not Found
Ош  http://mirror.mephi.ru jessie/contrib amd64 Packages
  404  Not Found
Игн http://mirror.mephi.ru jessie/contrib Translation-ru_RU
Игн http://mirror.mephi.ru jessie/contrib Translation-ru
Игн http://mirror.mephi.ru jessie/contrib Translation-en
Игн http://mirror.mephi.ru jessie/main Translation-ru_RU
Игн http://mirror.mephi.ru jessie/main Translation-ru
Игн http://mirror.mephi.ru jessie/main Translation-en
Игн http://mirror.mephi.ru jessie/non-free Translation-ru_RU
Игн http://mirror.mephi.ru jessie/non-free Translation-ru
Игн http://mirror.mephi.ru jessie/non-free Translation-en
Ош  http://mirror.mephi.ru jessie-updates/main Sources
  404  Not Found
Ош  http://mirror.mephi.ru jessie-updates/contrib Sources
  404  Not Found
Ош  http://mirror.mephi.ru jessie-updates/non-free Sources
  404  Not Found
Ош  http://mirror.mephi.ru jessie-updates/main amd64 Packages
  404  Not Found
Ош  http://mirror.mephi.ru jessie-updates/contrib amd64 Packages
  404  Not Found
Ош  http://mirror.mephi.ru jessie-updates/non-free amd64 Packages
  404  Not Found
Игн http://mirror.mephi.ru jessie-updates/contrib Translation-ru_RU
Игн http://mirror.mephi.ru jessie-updates/contrib Translation-ru
Игн http://mirror.mephi.ru jessie-updates/contrib Translation-en
Игн http://mirror.mephi.ru jessie-updates/main Translation-ru_RU
Игн http://mirror.mephi.ru jessie-updates/main Translation-ru
Игн http://mirror.mephi.ru jessie-updates/main Translation-en
Игн http://mirror.mephi.ru jessie-updates/non-free Translation-ru_RU
Игн http://mirror.mephi.ru jessie-updates/non-free Translation-ru
Игн http://mirror.mephi.ru jessie-updates/non-free Translation-en
W: Не удалось получить http://mirror.mephi.ru/debian/dists/jessie/main/source/Sources  404  Not Found
W: Не удалось получить http://mirror.mephi.ru/debian/dists/jessie/non-free/source/Sources  404  Not Found
W: Не удалось получить http://mirror.mephi.ru/debian/dists/jessie/contrib/source/Sources  404  Not Found
W: Не удалось получить http://mirror.mephi.ru/debian/dists/jessie/main/binary-amd64/Packages  404  Not Found
W: Не удалось получить http://mirror.mephi.ru/debian/dists/jessie/non-free/binary-amd64/Packages  404  Not Found
W: Не удалось получить http://mirror.mephi.ru/debian/dists/jessie/contrib/binary-amd64/Packages  404  Not Found
W: Не удалось получить http://mirror.mephi.ru/debian/dists/jessie-updates/main/source/Sources  404  Not Found
W: Не удалось получить http://mirror.mephi.ru/debian/dists/jessie-updates/contrib/source/Sources  404  Not Found
W: Не удалось получить http://mirror.mephi.ru/debian/dists/jessie-updates/non-free/source/Sources  404  Not Found
W: Не удалось получить http://mirror.mephi.ru/debian/dists/jessie-updates/main/binary-amd64/Packages  404  Not Found
W: Не удалось получить http://mirror.mephi.ru/debian/dists/jessie-updates/contrib/binary-amd64/Packages  404  Not Found
W: Не удалось получить http://mirror.mephi.ru/debian/dists/jessie-updates/non-free/binary-amd64/Packages  404  Not Found
W: Не удалось получить http://security.debian.org/dists/jessie/updates/main/source/Sources  404  Not Found
W: Не удалось получить http://security.debian.org/dists/jessie/updates/contrib/source/Sources  404  Not Found
W: Не удалось получить http://security.debian.org/dists/jessie/updates/non-free/source/Sources  404  Not Found
W: Не удалось получить http://security.debian.org/dists/jessie/updates/main/binary-amd64/Packages  404  Not Found
W: Не удалось получить http://security.debian.org/dists/jessie/updates/contrib/binary-amd64/Packages  404  Not Found
W: Не удалось получить http://security.debian.org/dists/jessie/updates/non-free/binary-amd64/Packages  404  Not Found
E: Некоторые индексные файлы не скачались. Они были проигнорированы или вместо них были использованы старые версии.

2. вот мой /etc/apt/sources.list

 
#

# deb cdrom:[Debian GNU/Linux 8.7.1 _Jessie_ - Official amd64 NETINST Binary-1 20170116-10:57]/ jessie contrib main non-free

#deb cdrom:[Debian GNU/Linux 8.7.1 _Jessie_ - Official amd64 NETINST Binary-1 20170116-10:57]/ jessie contrib main non-free

deb http://mirror.mephi.ru/debian/ jessie main non-free contrib
deb-src http://mirror.mephi.ru/debian/ jessie main non-free contrib

deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free

# jessie-updates, previously known as 'volatile'
deb http://mirror.mephi.ru/debian/ jessie-updates main contrib non-free
deb-src http://mirror.mephi.ru/debian/ jessie-updates main contrib non-free

3. вот вывод некоторых команд:

# dpkg --print-architecture

amd64

# dpkg --print-foreign-architectures

в ответе ничего нет

# uname -a

Linux server1 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux

# ping mirror.mephi.ru -c 4
PING point.mephi.ru (85.143.112.112) 56(84) bytes of data.
64 bytes from 85.143.112.112: icmp_seq=1 ttl=51 time=74.3 ms
64 bytes from 85.143.112.112: icmp_seq=2 ttl=51 time=73.5 ms
64 bytes from 85.143.112.112: icmp_seq=4 ttl=51 time=73.9 ms

--- point.mephi.ru ping statistics ---
4 packets transmitted, 3 received, 25% packet loss, time 3008ms
rtt min/avg/max/mdev = 73.591/73.984/74.363/0.315 ms

# ping security.debian.org -c 4
PING security.debian.org (133.242.99.74) 56(84) bytes of data.
64 bytes from setoguchi.debian.org (133.242.99.74): icmp_seq=1 ttl=43 time=342 ms
64 bytes from setoguchi.debian.org (133.242.99.74): icmp_seq=2 ttl=43 time=341 ms
64 bytes from setoguchi.debian.org (133.242.99.74): icmp_seq=3 ttl=43 time=341 ms
64 bytes from setoguchi.debian.org (133.242.99.74): icmp_seq=4 ttl=43 time=341 ms

--- security.debian.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 341.336/341.588/342.032/0.770 ms

Заранее огромное спасибо всем кто откликнется!

Источник

Возможно, вам также будет интересно:

  • Aps 647 ошибка скания
  • Aps 647 scania ошибка
  • Aps 169 ошибка скания
  • Aps 169 scania ошибка
  • Appword as word application ошибка библиотеки

    • Понравилась статья? Поделить с друзьями:
    0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии