@lpugoy I had the same problem as @cesarizu, followed your suggestion and removed /usr/lib/insync after uninstalling Insync.
Now, when I try to reinstall Insync I get:
cristiano@xmper8q3 [~]$ LANG=C sudo zypper in insync
Permission to access 'http://yum.insynchq.com/fedora/21/media.1/media' denied.
Abort, retry, ignore? [a/r/i/...? shows all options] (a):
ABORT request: Aborting requested by user
@Cris70: I tried on a Tumbleweed Docker image using the steps here to add the repo and running zypper ref and zypper in insync but wasn’t able to reproduce the issue. That path isn’t present even from the start so I’m not sure why your system is trying to access that. Have you run zypper ref before installing Insync?
@lpugoy I don’t know where that comes from, either. Here is my Insync.repo:
> cristiano@xmper8q3 [~]$ cat /etc/zypp/repos.d/Insync.repo
> [Insync]
> name=Insync
> enabled=1
> autorefresh=1
> baseurl=http://yum.insynchq.com/fedora/21/
> type=rpm-md
> keeppackages=0
BTW, I have the same problem on two different Tumbleweed boxes.
@lpugoy I’ve even tried removing and re-adding Insync’s repository, without success:
cristiano@xmper8q3 [~]$ sudo zypper rr 1
Rimozione del repository 'Insync' .....................................................................................................................................................[fine]
Il repository 'Insync' è stato rimosso.
cristiano@xmper8q3 [~]$ sudo zypper ar -r http://yum.insynchq.com/fedora/21/
Autorizzazione per accedere a 'http://yum.insynchq.com/fedora/21' rifiutata.
Annullare, riprovare, ignorare? [a/r/i/...? mostra tutte le opzioni] (a):
Si è verificato un problema durante il tentativo di lettura del file all'URI specificato:
ABORT request: Aborting requested by user
Sorry, forgot to add the LANG variable to oputput messages in english. However, the problem is the same as before: access denied.
@cesarizu: Do you mean that you are also encountering a message similar to:
Permission to access 'http://yum.insynchq.com/fedora/21/media.1/media' denied.
I’m also unable to reproduce this in Fedora 25 unfortunately. What are the contents of /etc/yum.repos.d/insync.repo?
@Cris70: The URL is not accessible because the repo is hosted in S3 and we didn’t enable browsing, but files under it should be accessible. For example http://yum.insynchq.com/fedora/21/repodata/repomd.xml. This probably caused the error you encountered with the command
sudo zypper ar -r http://yum.insynchq.com/fedora/21/
Please try recreating /etc/zypp/repos.d/Insync.repo manually instead then retry.
This may help you in debugging: on one of my Tumbleweed boxes - where I didn’t remove the old insync given the problem I had on the other - I noticed that with every zypper dup it tried to update insync, and it actually was able to download the new package. However, it would later fail with the dreaded lstat error.
So today, I tried to delete the contents of the /usr/lib/insync directory without first uninstalling insync. I did that while zypper was still downloading the new packages (the new insync had already been downloaded).
Well, this time it succeeded in installing the new insync!! (though it was a little upset due to the missing files )
However, although I now have an updated and working Insync, the repository still shows the usual access denied errors whatever I try to do with zypper.
See for example:
cris@PolariSuse [~]$ sudo zypper ref
[sudo] password for root:
Permission to access 'http://yum.insynchq.com/fedora/21/media.1/media' denied.
Abort, retry, ignore? [a/r/i/...? shows all options] (a):
ABORT request: Aborting requested by user
cris@PolariSuse [~]$ sudo zypper dup
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Permission to access 'http://yum.insynchq.com/fedora/21/media.1/media' denied.
Abort, retry, ignore? [a/r/i/...? shows all options] (a):
ABORT request: Aborting requested by user
I also am having the same problem as Cris70 and others on openSUSE tumbleweed. Why was browsing to this file disabled in the S3 repo? Wondering if this might be the issue.
@lpugoy maybe it would be a good idea for you to setup a build user at build.opensuse.org, that way you could build packages for different opensuse versions / architectures, and even for fedora and other distributions. You would also get for free some rpm checks and hosting.
@cseader@cesarizu: We don’t provide sources, only binaries. I took a look at the Build service before but it seemed complicated for me. Might take a look in the future.
@Cris70: Thanks for the link. That indicates that the /media.1/media folder is expected when using a YaST repo. That is not required for rpm-md repos, which is the type specified in the /etc/zypp/repos.d/Insync.repo file. So this looks more like a zypper bug to me. As a workaround I was able to make zypper ref succeed by adding the --force flag.
@lpugoy yes, using the --force flag allows to refresh the Insync repo. Even after that, however, I cannot install Insync on the PC where I removed it (usual access denied error).
It may actually be a bug in a recently published version of zypper, because the problem only started showing a few days ago.
I don’t know (didn’t check) if zypper has been recently updated, though, but maybe others in this forum will help.
If this is true, we could try filing a bug against openSUSE. But in the meantime, could you create the expected files/directories to see if the “access denied” error vanishes?
@lpugoy either you changed something in the repo in the last few minutes, or it was my change to the repo file (see below) that made it work, because I was finally able to (re)install Insync!!
I tested other rpm-md repositories to see if they contained the /media.1/media path, and saw that they did not contain it. But I noticed that all those repos had gpg-checking enabled.
So I modified the Insync repo this way:
i.e. I added the two gpg* lines.
Then tried again to install Insync and it worked!!
Hope this helps others too!
P.S. A few minutes later… the problem persists
It seems every time I change something in the repo file it can correctly complete the very first command I try and then… back to the usual behavior:
@Cris70: I think I know the cause now. The path http://yum.insynchq.com/fedora/21/media.1/media used to return an HTTP 403 which is used to specify that the access to the path is denied. If a path does not exist the code that should be returned is HTTP 404. I changed the settings of the S3 bucket to return a 404 instead. I still maintain though that for rpm-md repos zypper shouldn’t look for those paths.