Repo Issue
-
I was running an update yesterday via the terminal and when it finished I got this message All packages are up to date.
"Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://repo.vivaldi.com/stable/deb stable InRelease' doesn't support architecture 'i386'" I am running a 64 bit OS and have the 64 bit version of the latest stable version of Vivaldi. I was wondering if anyone might know what is going on and how to maybe fix this issue.
Thank you -
Hi, I update Vivaldi just past afternoon without any repo issues. I'm on Linux Mint 20.1 (Cinnamon).
I dont know why you get this error but you should write what distro you use and also hardware specs, just to help investigate the probelm -
Edit your repository source like this: deb [arch=amd64] https://repo.vivaldi.com/archive/deb/ stable main
then run update command.
Hope that can help you. -
Bug was reported & confirmed some days ago. Vivaldi Linux dev will have a look for repo data.
-
I'm facing the same issue. Every
apt[-get] update
ends up with the warning about »main/binary-i386/Packagesâ could not be downloaded (not sure about the correct translation).I presume the Vivaldi repository used to have both of the subfolders »main/binary-i386/â and »main/binary-amd64/â. But for the latest stable update (4.3.2439.65-1) it seems Vivaldi dropped or forgot to build the *-i386 subfolder. It's just not online.
Actually this package is not needed on amd64 archs as the 64-bit edition is installed by default. But on systems with the i386 subset installed (or 32-bit only)
apt
is trying to locate both amd64 and i386 packages by default. In this case it ends up with this error.The best fix here is the injection of "[arch=amd64]" in »sources.listâ and also in »sources.list.d/vivaldi.listâ (if exists) as @harold_crane mentioned above.
Once edited it won't bother you again no matter what the Vivaldi pros are going to fix (or not) on this.But please correct me if I misinterpreted something.
-
It is not an error or even a warning. It is a "notice", which is why it starts with "N:". Nonetheless, I will look at the option to see if we can easily hide it for you.
But in any case, it can be safely ignored (notices are two levels down from errors).
-
@i-m-jens said in Repo Issue:
But for the latest stable update (4.3.2439.65-1) it seems Vivaldi dropped or forgot to build the *-i386 subfolder.
We have not provided updates to i386 since Vivaldi 3.7, thus it was removed from the repository.
-
@ruarĂ said in Repo Issue:
It is not an error or even a warning. It is a "notice", which is why it starts with "N:".
That seems to depend on the distro and/or version.
(I had both "W:" and "E:" messages on my cosy Ubuntu ESM.)Nevertheless, it is confusing.
Anyway, a subsequent
apt[-get] upgrade
ran seemlessly.@ruarĂ said in Repo Issue:
We have not provided updates to i386 since Vivaldi 3.7 [âŠ]
Ah, interesting. My first install was 3.8.
@ruarĂ said in Repo Issue:
[âŠ] thus it was removed from the repository.
Do you mean recently, before the mentioned update?
If not so, it must be a different reason.Sorry for tittle-tattle. I like fiddly thingys.
P.S.: BTW, thanks for your great work!
-
@i-m-jens said in Repo Issue:
(I had both "W:" and "E:" messages on my cosy Ubuntu ESM.)
Not for this issue you have not. Perhaps for something else. This will only cause a notice.
Also neither a N: nor a W: will prevent updates. Only an E: will do that.
@i-m-jens said in Repo Issue:
Do you mean recently,
Yes it was very recently removed from the repo. On the last minor update.
-
I also get the same message everytime I run "sudo apt update"
I'm at Pop_OS 21.04 btw -
Since people coming here do not like to see notices, warnings or errors on their systems, can this notice (N) be avoided one way or another? Like completely not appearing?
-
I get such repo message on Ubuntu 20 LTS now.
-
@mrsyria Edit your Vivaldi repo config file to:
deb [arch=amd64] https://repo.vivaldi.com/archive/deb/ stable main
-
@doctorg Thanks.
-
@ruarĂ said in Repo Issue:
Not for this issue you have not. Perhaps for something else. This will only cause a notice.
Also neither a N: nor a W: will prevent updates. Only an E: will do that.
Well it's still occurring what actually cannot occur:
Anyway I could manage to find a re-translation of my "messages" on invoking
apt[-get] update
:W: Failed to fetch http://repo.vivaldi.com/stable/deb/dists/stable/Release Unable to find expected entry »main/binary-i386/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.
Both
apt
andapt-get
exit with the error code 100.This "error" still persists due to I missed to also adjust
/etc/apt/*/*.list.save
files accordingly (which revert the*.list
files back again).So this should be regarded on adjusting the
/etc/apt/*/*.list
files.Yes it was very recently removed from the repo. On the last minor update.
So THAT is the "error" â which actually is a "note".
Anyway, meanwhile I noticed that Vivaldi is recommend for usage on Ubuntu 18++. But let me report it works absolute seamlessly on Ubuntu 14.
Nice!The only problem now is the deletion of the old 'main/binary-i386/Release' file (maybe also the 'Package*' files) â which however was just needed for compatibility reasons with an installed 32bit subsystem.
Maybe you simply need to adjust the DEB package (â control.tar.xz/postinst). On fly by it looks like it is even made compatible for Ubuntu 12 and any other architecture (i386/arm64/mipsel/mips64el) that are not included in the repository any more!
-
A fix is in progress for internal 4.4 version. Stay tuned for a next Snapshot.
-
@i-m-jens 14 is not supported by Ubuntu and thus should not be run as a desktop because you are not receiving fully security updates. Is that where you are seeing this as an error? Because if that is where then I can't say I really care much (though as @DoctorG points out I have fixed it internally) and hence a fix will roll out anyway.
-
@i-m-jens said in Repo Issue:
W: Failed to fetch http://repo.vivaldi.com/stable/deb/dists/stable/Release Unable to find expected entry »main/binary-i386/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.
It is not clear that the E: is related to the W: above. More likely the failed to download indexes are because you tested this on a distro where the main repos themselves have expired, i.e. the error is related to the other repos, NOT Vivaldi
-
@ruarĂ said in Repo Issue:
It is not clear that the E: is related to the W: above. More likely the failed to download indexes are because you tested this on a distro where the main repos themselves have expired, i.e. the error is related to the other repos, NOT Vivaldi
Sorry, but no. This is definitely caused by the changes in the Vivaldi repo:
apt
failed to download simply because you deleted this i386 package from your repo.And it's not an issue of the main repos of my distro. In this case the installation of Vivaldi v3.8 should have failed right from the beginning as well as all succeeding updates.
Furthermore after I patched all mentioned
sources.list
files correctly those messages didn't occur again.
Quite contrary the update runs without any errors, warnings or notes. In fact I never had any problems since I installed Vivaldi.(BTW, take it as a compliment.)
It seems you kept Vivaldi downwards compatible with Debian 7 (or at least v8) and THAT makes Vivaldi a very good product.
And don't worry me using an ESM distro â I got better reasons for that than just »It's old, so it's bad!«.
I just wanted to give a helping hand ...Have a nice day!
-
@I-M-Jens the install for
Vivaldi 3.8
and any version since succeeded for the primaryamd64
architecture while ignoring the mismatching/outdated foreign arch package.The repo change was a necessary cleanup to drop the unsupported
i386
release.
So no one installs this old version »because it's old and has security vulnarabilities!«.Chrome
went through similar pains 5 years ago.
APT
issues a warning when a repository does not provide binaries for all configured architectures.