[SOLVED] A question about linux mint 18.3 repositories

[darkwolf]

Hello everyone i'm new here. about one month ago i have installed Linux Mint 18.3 64 bit on my pc, everything seems to work fine and i'm liking it so far, but lately i have notice something strange, whenever i check for updates it says:

Code: Select all

failed  0b   InRelease    http://packages.linuxmint.com sylvia InRelease

and when i try

Code: Select all

sudo apt update

or

Code: Select all

sudo apt-get update

in terminal it says:

Code: Select all

Ign:5 http://packages.linuxmint.com sylvia InRelease

Is this normal? If not how can i fix it?

[kc1di]

Hello darkwolf and Welcome to Linux Mint,

Please go to a terminal and issue this command and copy and past it back here (using the Code tag) Thanks.

Code: Select all

inxi -Sr

[darkwolf]

Here is the result:

Code: Select all

System:    Host: .....-PC Kernel: 4.13.0-32-generic x86_64 (64 bit)
           Desktop: Cinnamon 3.6.7  Distro: Linux Mint 18.3 Sylvia
Repos:     Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
           deb http://packages.linuxmint.com sylvia main upstream import backport
           deb http://archive.ubuntu.com/ubuntu xenial main restricted universe multiverse
           deb http://archive.ubuntu.com/ubuntu xenial-updates main restricted universe multiverse
           deb http://archive.ubuntu.com/ubuntu xenial-backports main restricted universe multiverse
           deb http://security.ubuntu.com/ubuntu/ xenial-security main restricted universe multiverse
           deb http://archive.canonical.com/ubuntu/ xenial partner

[Sir Charles]

This is what I found:

When you use apt-get update it verifies if the same update indexes need downloading, if not it does not download the same updated indexes again.

Hit means apt checked the timestamps on package list, those match and there are no changes.

Ign means there are no changes in the pdiff index file, it wont bother downloading it again.

Nothing to be scared of, it just means there is no need to download updated indexes again, the ones you have are current.

here: https://askubuntu.com/questions/294525/ ... 532#294532

Not sure if it is the right explanation, but I mean, in the meantime...

[darkwolf]

So in the end there is nothing to worry about? to tell you the truth, i knew what Ign means but what confused me was this: failed 0b InRelease http://packages.linuxmint.com sylvia InRelease whenever i click refresh in update manager.

[Sir Charles]

failed 0b InRelease whenever i click refresh in update manager.

I am not sure what that means, but have you tried to clean up the downloaded archive files and unused packages before you run sudo apt update ?

[darkwolf]

failed 0b InRelease whenever i click refresh in update manager.

I am not sure what that means, but have you tried to clean up the downloaded archive files and unused packages before you run sudo apt update ?

I'm not sure, do you mean apt autoclean? Yes i do it almost everytime after i install any package or update.

[Sir Charles]

Yes, plus maybesudo apt clean andsudo apt auto remove to erase what remains of downoaded archive fies and all unused packages. Then what doesfailed 0b InRelease mean

[darkwolf]

Yes, plus maybesudo apt clean andsudo apt auto remove to erase what remains of downoaded archive fies and all unused packages. Then what doesfailed 0b InRelease mean

Some detailed info: I get failed 0b InRelease http://packages.linuxmint.com sylvia InRelease when i open update manager, click refresh then click show individual files option, after this finishes there is no error or anything like that, that's why i'm a bit confused.

Sorry for constant editing but what do you think? is this a problem or not? should i just ignore it?

[Sir Charles]

I am not sure, I mean if it otherwise is not causing other issues for updating or installing packages then probably it is not that serious a problem. Couldn't that be due to a temporary down server? Hope someone with more insight into this come along and shed some light.

[minitux]

for me, if update it's ok , and it seems , its a little problem on update manager.

for me the important thing it's update from terminal and i think you don't have any problem on your system.

[ralplpcr]

FWIW: There have been several different attacks on routers in recent months. Sometimes, this can cause problems - especially with the default IPV6 that many of these repositories use. I've had similar issues where 1 or more repositories seem to hang, or are unable to connect at times.

I've had good luck using the following method to bypass it: sudo apt-get -o Acquire::ForceIPv4=true update

This forces an IPV4 update instead of IPV6. So far, it's never failed me when I encounter a stubborn repository that won't connect via IPV6?

[darkwolf]

Thanks all. I think i will ignore this little weird issue, based on what you all said, it is not that important problem i think, i'm going to set this topic as solved.

[Moem]

i'm going to set this topic as solved.

That's always appreciated; please do it in the subject (title) of the first posting, so it can be seen from the forum overview page.

[Sir Charles]

I've had similar issues where 1 or more repositories seem to hang, or are unable to connect at times. I've had good luck using the following method to bypass it: sudo apt-get -o Acquire::ForceIPv4=true update
This forces an IPV4 update instead of IPV6. So far, it's never failed me when I encounter a stubborn repository that won't connect via IPV6?

I will remember this when/if I run into similar issue.
Thanks!