Package Details: yandex-disk 0.1.6.1080-1

Git Clone URL: https://aur.archlinux.org/yandex-disk.git (read-only, click to copy)
Package Base: yandex-disk
Description: Yandex.Disk keeps your files with you at all times.
Upstream URL: http://disk.yandex.ru/
Licenses: custom
Submitter: ziggi
Maintainer: Stezko (Felixoid)
Last Packager: Felixoid
Votes: 131
Popularity: 0.57
First Submitted: 2013-08-27 11:59 (UTC)
Last Updated: 2022-05-28 22:10 (UTC)

Latest Comments

RBuster commented on 2022-06-15 02:33 (UTC)

Puted two lines to /etc/locale-gen and run "locale-gen".

en_US.UTF-8 UTF-8

ru_RU.UTF-8 UTF-8

Error: Invalid or unsupported charset:utf-8.utf-8 or UTF-8

The problem is only with the yandex-disk package. Maybe the package refers to other locales? Or an incorrect error - the problem is completely different

Stezko commented on 2022-06-14 09:16 (UTC)

Я думаю решать проблему локали недопустима в комментариях к пакету.

dchusovitin commented on 2022-06-14 09:12 (UTC) (edited on 2022-06-14 09:12 (UTC) by dchusovitin)

@RBuster where did you find "ru_RU.UTF-8.UTF-8" locale? It's a wrong locale. A message "Invalid or unsupported charset:utf-8.utf-8 or UTF-8" says about that.

Put two lines to /etc/locale-gen and run "locale-gen".

en_US.UTF-8 UTF-8

ru_RU.UTF-8 UTF-8

RBuster commented on 2022-06-14 07:14 (UTC)

The following lines are uncommented in the /etc/locale.gen file:

en_US.UTF-8 UTF-8 ru_RU.UTF-8.UTF-8 UTF-8

But still Error: Invalid or unsupported charset:utf-8.utf-8 or UTF-8

Stezko commented on 2022-06-13 17:00 (UTC)

@RBuster may be en_US.utf-8?

RBuster commented on 2022-06-13 16:16 (UTC)

  1. Installed archlinux using archinstall (utf-8 is enabled)
  2. Installed yay
  3. Installed yandex-disk using yay
  4. Entered the command yandex-disk setup

Error: Invalid or unsupported charset:utf-8.utf-8 or UTF-8

Felixoid commented on 2022-05-28 18:57 (UTC)

Add me to comaintainers, please

Stezko commented on 2022-05-28 06:54 (UTC)

I'll get to the computer, update it

Felixoid commented on 2022-04-28 09:52 (UTC) (edited on 2022-04-28 09:52 (UTC) by Felixoid)

The client is broken currently, please, consider updating ASAP

diff --git a/.SRCINFO b/.SRCINFO
index f7dc2c1..a028a82 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,6 +1,6 @@
 pkgbase = yandex-disk
        pkgdesc = Yandex.Disk keeps your files with you at all times.
-       pkgver = 0.1.6.1074
+       pkgver = 0.1.6.1080
        pkgrel = 1
        url = http://disk.yandex.ru/
        install = yandex-disk.install
@@ -10,10 +10,10 @@ pkgbase = yandex-disk
        depends = gcc
        depends = gcc-libs
        depends = zlib
-       source = https://repo.yandex.ru/yandex-disk/deb/pool/main/y/yandex-disk/yandex-disk_0.1.6.1074_amd64.deb
+       source = https://repo.yandex.ru/yandex-disk/deb/pool/main/y/yandex-disk/yandex-disk_0.1.6.1080_amd64.deb
        source = yandex-disk.install
        source = yandex-disk.service
-       md5sums = 5f3263652239be600bc8c35e3e3f7e2b
+       md5sums = 19446922ba1713183476953663a2b1cb
        md5sums = 5ad775bd895526c6b1f335c6d71dbdfa
        md5sums = 3d0370f3dfadf9da294b91441c226547

diff --git a/PKGBUILD b/PKGBUILD
index 5c0740b..d5d60c2 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,7 +3,7 @@
 # Contributor: Dmitry Chusovitin <dchusovitin@gmail.com>

 pkgname='yandex-disk'
-pkgver=0.1.6.1074
+pkgver=0.1.6.1080
 pkgrel=1
 pkgdesc='Yandex.Disk keeps your files with you at all times.'
 arch=('x86_64')
@@ -14,9 +14,9 @@ install=yandex-disk.install
 source=("https://repo.yandex.ru/yandex-disk/deb/pool/main/y/yandex-disk/yandex-disk_${pkgver}_amd64.deb"
         "yandex-disk.install"
         "yandex-disk.service")
-md5sums=('5f3263652239be600bc8c35e3e3f7e2b'
+md5sums=('19446922ba1713183476953663a2b1cb'
         '5ad775bd895526c6b1f335c6d71dbdfa'
-        '3d0370f3dfadf9da294b91441c226547')   
+        '3d0370f3dfadf9da294b91441c226547')

 package() {
     cd $srcdir

sistematico commented on 2021-06-10 22:09 (UTC)

@flow206 thank you very much! Version bumped.

flow206 commented on 2021-05-24 17:30 (UTC)

The build is broken. Failed to download the old version yandex_disk_0.1.5.1039_amd64.deb

Could you update the link to the new version: https://repo.yandex.ru/yandex-disk/deb/pool/main/y/yandex-disk/yandex-disk_0.1.6.1074_amd64.deb

And thank you for providing this package!

lybin commented on 2020-01-29 20:47 (UTC)

@timhs, the problem on your side.

timhs commented on 2020-01-29 20:28 (UTC) (edited on 2020-01-29 20:29 (UTC) by timhs)

can't update 

curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
==> ERROR: Fehler beim Download von https://repo.yandex.ru/yandex-disk/deb/pool/main/y/yandex-disk/yandex-disk_0.1.5.1039_amd64.deb

I took a look at repo.yandex.ru and it looks like there is only the old yandex-disk_0.1.5.1039_amd64.deb there.

lybin commented on 2020-01-29 10:45 (UTC)

Thank you, also can transfer to a prepare section some commands, Arch unpacks deb already: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=upwork

sistematico commented on 2020-01-29 10:28 (UTC)

@lybin changed.

$ yandex-disk --version Yandex.Disk 0.1.5.1039 © 2019 YANDEX

lybin commented on 2020-01-22 11:11 (UTC) (edited on 2020-01-22 11:12 (UTC) by lybin)

@sistematico, pls change source url to https:// may be we will solve problem, I think hard cache somewhere...

sistematico commented on 2019-12-23 23:28 (UTC)

yandex-disk_0.1.5.1039_amd64.deb

Latest for me..

sergeimipt commented on 2019-12-18 14:28 (UTC)

it is again 0.1.5.1010 for me. There must be a problem on the Yandex server end. https://repo.yandex.ru/yandex-disk/deb/pool/main/y/yandex-disk

zkiroel commented on 2019-12-18 11:42 (UTC)

well thanks for the repo had to edit pkgbuild for 0.1.5.1010 version, maybe I had to install latest but nwm and change md5, and works like a sharm

sergeimipt commented on 2019-12-15 14:20 (UTC)

@lybin Just in case, the issue with the old version of yandex-disk does no longer exist (at least for me). When the page (https://repo.yandex.ru/yandex-disk/deb/pool/main/y/yandex-disk) is accessed from my machine, I see 0.1.5.1039 (as it should be).

PS: planned to write a message to Yandex but it is OK already.

sergeimipt commented on 2019-12-01 19:01 (UTC) (edited on 2019-12-01 19:03 (UTC) by sergeimipt)

@lybin thanks for a prompt response. I have no idea why it is happening to me, and isn't to you. I tried from my home computer and from my mobile phone, two different network providers, both showing 1010, not 1039. I am based in Moscow, maybe it is somehow related to a user location.

Temporary fix: checkout to the previous commit 068ccdd9c232 (or HEAD~). Worked like a charm for me!

$ sudo pacman -S --needed base-devel $ mkdir ~/git $ cd ~/git $ git clone https://aur.archlinux.org/yandex-disk.git $ git checkout 068ccdd9c232 # go one commit back $ cd yandex-disk $ makepkg -si

lybin commented on 2019-12-01 18:11 (UTC)

I checked again xD 0.1.5.1039 Guys, write to Yandex or your provider about this problem. May be you both have same provider and he has some cache, I don't know.. I see one moment, in package schema http not https, it will be better to change.

sergeimipt commented on 2019-12-01 16:43 (UTC)

Hello, now is 1st December 2019, 8 pm UTC+3. I confirm that that the current version of yandex disk is 0.1.5.1010 ( https://repo.yandex.ru/yandex-disk/deb/pool/main/y/yandex-disk/), not 0.1.5.1039. Please, update the pkgver variable and checksums.

PS: I updated the PKGBUILD manually ($ sed -i "s/pkgver=.*/pkgver=0.1.5.1010/" PKGBUILD), but it still doesn't work due to wrong checksums.

The log:

$ makepkg -si ==> Making package: yandex-disk 0.1.5.1039-1 (Sun 01 Dec 2019 07:15:30 PM MSK) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading yandex-disk_0.1.5.1039_amd64.deb... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading http://repo.yandex.ru/yandex-disk/deb/pool/main/y/yandex-disk/yandex-disk_0.1.5.1039_amd64.deb Aborting...

Stane1983 commented on 2019-11-03 08:12 (UTC)

@lybin then it must have been some glitch or maintenance on their side because when I tried to install it there was only 1010 version available. Bad luck I guess :)

lybin commented on 2019-11-02 16:33 (UTC) (edited on 2019-11-02 16:34 (UTC) by lybin)

@Stane1983, the latest version on http://repo.yandex.ru/yandex-disk/deb/pool/main/y/yandex-disk/ is 0.1.5.1039 ... Package installing successfully, I checked it just now.

Stane1983 commented on 2019-11-02 13:14 (UTC)

Latest version on http://repo.yandex.ru/yandex-disk/deb/pool/main/y/yandex-disk/ is 0.1.5.1010 and this package fails to install unless PKGBUILD is edited to change version and md5sum of .deb file.

vp1981 commented on 2017-05-18 06:03 (UTC)

ziggi, yes, of course.

ziggi commented on 2017-05-12 16:11 (UTC)

vp1981, can I add your service file to the package?

vp1981 commented on 2017-05-10 11:33 (UTC)

For those who uses several Yandex accounts and wants to use 'yandex-disk' may use following service file: [Unit] Description=Yandex-Disk service for %i After=local-fs.target network.target ConditionPathExists=%h/.config/yandex-disk/%i.cfg [Service] Type=forking ExecStart=/usr/bin/yandex-disk start -c %h/.config/yandex-disk/%i.cfg ExecStop=/usr/bin/yandex-disk stop -c %h/.config/yandex-disk/%i.cfg [Install] WantedBy=default.target (link to the service https://bitbucket.org/vp1981/pkgbuild/src/7090062b17dd082adb205c6a8a33569199ff520c/yandex-disk/yandex-disk@.service?at=master&fileviewer=file-view-default). To use the service one has to setup configuration for every Yandex account, give them appropriate names, change settings in configuration as well. Then enable service as systemctl --user enable yandex-disk@ACCOUNT.service systemctl --user start yandex-disk@ACCOUNT.service

ziggi commented on 2017-05-03 20:55 (UTC)

> In the systemd service file I've found the following line: > ExecReload=/usr/bin/killall -qw yandex-disk > > I really appreciate your work and I beg your pardon, ziggi, but are > you kidding me? :) Why bother implementing a "reload" command if it > merely kills ALL the processes that have "yandex-disk" in their names? > > There is a wonderful systemctl command named 'reload-or-restart' that > restarts a service if it doesn't have the "reload" command > implemented, so what you have done is certainly a misuse of the > ExecReload parameter. If you can prove me wrong please let me know. I kill the process and him will be started automatically soon. > Also in the docs they mention that the daemon has to be stopped with > the command "yandex-disk stop": https://yandex.com/support/disk/cli- > clients.html#cli-daemon__cli-commands . There is the "ExecStop" > parameter (man 5 systemd.service) which one can utilize to achieve the > desired behaviour. Well I guess nothing bad will happen if the daemon > is stopped with the SIGTERM signal, but nevertheless. "yandex-disk stop" doesn't kill the systemd daemon. > And I can't keep myself from mentioning the "RestartSec" parameter > which is set to 60. Do you have any special reason to override the > default systemd behaviour? I mean, is anything bad going to happen if > it is restarted with, let's say, a second timeout? Yes, without some delay daemon won't start. And I don't know exactly how much him need. > The last but not the least. You have that weird shell script that > apparently parses the configuration file and appends the parsed values > to the yandex-disk command line. Well, to begin with, it happily > parses all the commented lines producing stuff like `--#proxy=socks4`. > And why did you even bother with that? The daemon reads that file by > default (unless you specify the "-c"/"--config" option). Because "-c" option is not supported with "--no-daemon" mode. But I found the way how it can be fixed. P.S. This service works good but if you want to suggest any changes - just show me your service configuration file. Because any program has specific behavior and any decision has specific causes. Anyway, thanks for reporting.

mexus commented on 2017-05-03 19:17 (UTC)

Hi ziggi! In the systemd service file I've found the following line: ExecReload=/usr/bin/killall -qw yandex-disk I really appreciate your work and I beg your pardon, ziggi, but are you kidding me? :) Why bother implementing a "reload" command if it merely kills ALL the processes that have "yandex-disk" in their names? There is a wonderful systemctl command named 'reload-or-restart' that restarts a service if it doesn't have the "reload" command implemented, so what you have done is certainly a misuse of the ExecReload parameter. If you can prove me wrong please let me know. Also in the docs they mention that the daemon has to be stopped with the command "yandex-disk stop": https://yandex.com/support/disk/cli-clients.html#cli-daemon__cli-commands . There is the "ExecStop" parameter (man 5 systemd.service) which one can utilize to achieve the desired behaviour. Well I guess nothing bad will happen if the daemon is stopped with the SIGTERM signal, but nevertheless. And I can't keep myself from mentioning the "RestartSec" parameter which is set to 60. Do you have any special reason to override the default systemd behaviour? I mean, is anything bad going to happen if it is restarted with, let's say, a second timeout? The last but not the least. You have that weird shell script that apparently parses the configuration file and appends the parsed values to the yandex-disk command line. Well, to begin with, it happily parses all the commented lines producing stuff like `--#proxy=socks4`. And why did you even bother with that? The daemon reads that file by default (unless you specify the "-c"/"--config" option). Thanks for your attention.

mamantoha commented on 2016-07-27 22:54 (UTC)

ziggi, I just checked sha512sum of yandex-disk.install. And it`s correct. Probably something wrong with my system.

ziggi commented on 2016-07-27 22:45 (UTC)

mamantoha, everything works, I have tested it.

mamantoha commented on 2016-07-27 22:09 (UTC)

Can't install the latest version: ==> Validating source files with sha512sums... yandex-disk_0.1.5.948_amd64.deb ... Passed yandex-disk.install ... FAILED yandex-disk.service ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build yandex-disk. ==> Restart building yandex-disk ? [y/N] ==> ------------------------------------

mdeni commented on 2016-01-15 21:16 (UTC)

kfr2359, thank you for this information. I will wait for new kernel in stable repo. So I hope this update will solve this issue on my system too.

kfr2359 commented on 2016-01-15 13:23 (UTC)

Installing 4.4.0-2 kernel (available on testing repository) fixes the problem mdeni and I have faced.

kfr2359 commented on 2016-01-05 15:41 (UTC)

Have got exactly the same problem mdeni had described. Maybe it's somehow connected to the recent kernel update?

mdeni commented on 2016-01-02 20:44 (UTC)

I've got a bug. I start the daemon and it works fine about 1 minute then there becomes a lot of processes and two of them using 100% cpu each. And nothing works as log doesn't change. Also I cannot kill or stop processes and then reboot system. Only hard reboot with power button pressed helps. Could you help me to solve this problem or at least investigate and report a bug to devs (I'm newbie to Arch). Thank you.

salikovpro commented on 2015-10-11 09:10 (UTC)

Please. in PkBuild: update: pkgver=0.1.5.940 //not 905 md5sums = ('f4f3b9093ff30faa16a9df1504025947')

wilful commented on 2015-08-25 12:17 (UTC)

После очередного апдейта системы (при попытке запуска setup): Assertion 'clock_gettime(clock_id, &ts) == 0' failed at src/basic/time-util.c:34, function now(). Aborting. Got signal 6 0.1.5.905 x64 [bt] Execution path: [bt] /usr/lib/libc.so.6(gsignal+0x38) [0x7f04842ce5f8] [bt] /usr/lib/libc.so.6(gsignal+0x38) [0x7f04842ce5f8] [bt] /usr/lib/libc.so.6(abort+0x16a) [0x7f04842cfa7a] [bt] /usr/lib/libnss_resolve.so.2(+0x2c8c5) [0x7f04858a38c5] [bt] /usr/lib/libnss_resolve.so.2(+0x214af) [0x7f04858984af] [bt] /usr/lib/libnss_resolve.so.2(+0x28c88) [0x7f048589fc88] [bt] /usr/lib/libnss_resolve.so.2(+0xb403) [0x7f0485882403] [bt] /usr/lib/libnss_resolve.so.2(+0x2ec1d) [0x7f04858a5c1d] [bt] /usr/lib/libnss_resolve.so.2(_nss_resolve_gethostbyname4_r+0xc1) [0x7f048589a5e1] [bt] /usr/lib/libc.so.6(+0xd3ff1) [0x7f048436eff1] [bt] /usr/lib/libc.so.6(getaddrinfo+0xee) [0x7f0484370f9e] [bt] yandex-disk() [0x5fd727] [bt] yandex-disk() [0x430859] [bt] yandex-disk() [0x5f60ec] [bt] yandex-disk() [0x5ea5de] [bt] /usr/lib/libpthread.so.0(+0x74a4) [0x7f0484edc4a4] [bt] /usr/lib/libc.so.6(clone+0x6d) [0x7f048438412d]

ziggi commented on 2014-08-06 20:09 (UTC)

updated

lev.bezborodov commented on 2014-08-06 20:00 (UTC)

Please change to actual version of the debian package: yandex-disk_0.1.5.758_amd64.deb

tchgefest commented on 2014-05-06 08:34 (UTC)

Сегодня заметил yandex-disk sync Ошибка: Прокси-сервер недоступен yandex-disk -v Яндекс.Диск 0.1.4.504 © 2013 ООО «ЯНДЕКС» yandex-disk start Ошибка: Прокси-сервер недоступен в конфиге proxy="no" Я не использую прокси.

ziggi commented on 2014-03-10 19:43 (UTC)

dchusovitin, thanks. Package updated. Use 'yandex-disk setup' for initial configure Use 'systemctl --user enable yandex-disk.service' for load with system start

dchusovitin commented on 2014-03-10 18:03 (UTC)

ziggi, oh, sorry, bug in service file. I updated a package, maybe it's useful to you.

ziggi commented on 2014-03-10 17:39 (UTC)

to ForeverYoung: Thanks. to dchusovitin: I try you solution, but yandex-disk.service is inactive after reboot.

dchusovitin commented on 2014-03-10 17:19 (UTC)

http://lists.freedesktop.org/archives/systemd-devel/2014-February/017146.html * %h, %s, %U specifier support is not available anymore when used in unit files for PID 1. This is because NSS calls are not safe from PID 1. They stay available for --user instances of systemd, and as special case for the root user. New package - https://gist.github.com/dchusovitin/9469152 Install and run 'systemctl --user enable yandex-disk'

ForeverYoung commented on 2014-03-10 11:38 (UTC)

I think service file now should be as follows: [Unit] Description=Yandex-Disk service for %I After=local-fs.target network.target [Service] Type=forking User=%I ExecStart=/usr/bin/yandex-disk start RestartSec=60 Restart=always [Install] WantedBy=multi-user.target

lumberjack commented on 2014-03-10 10:22 (UTC)

не стартует... мар 10 16:11:09 arch systemd[1]: Starting Yandex-Disk service for myuser... мар 10 16:11:09 arch systemd[1]: yandex-disk@myuser.service failed to run 'start' task: Operation not supported мар 10 16:11:09 arch systemd[1]: Failed to start Yandex-Disk service for myuser. мар 10 16:11:09 arch systemd[1]: Unit yandex-disk@myuser.service entered failed state.

ziggi commented on 2014-02-15 13:51 (UTC)

to tchgefest: Я проверил, у меня похожая проблема, но при использовании yandex-disk unpublish само действие происходит корректно, но в ответ выдаётся "Доступ закрыт".

tchgefest commented on 2014-02-11 08:21 (UTC)

Почему так происходит.Делаю так: yandex-disk publish Yandex.Disk/fail.tar.gz [14:09~] http://yadi.sk/d/ssdfWQd -ссылка есть,но потом делаю так: yandex-disk unpublish Yandex.Disk/fail.tar.gz выдается ошибка [b]неизвестная ошибка при попытке закрыть доступ[/b] Хотя видно [b]yandex-disk status Статус ядра синхронизации: ожидание команды[/b]

elifarley commented on 2014-02-06 23:45 (UTC)

I was able to run it a first time (version 0.1.4.504-2). Then, after rebooting, I'm unable to start it up again. Log messages below: Feb 06 21:43:02 ideapad systemd[1]: Starting Yandex-Disk service for myuser... Feb 06 21:43:02 ideapad systemd[1]: yandex-disk@myuser.service failed to run 'start' task: No such process Feb 06 21:43:02 ideapad systemd[1]: Failed to start Yandex-Disk service for myuser.

ziggi commented on 2013-12-10 14:15 (UTC)

Updated. Use 'yandex-disk setup' for initial configure. Use 'systemctl enable yandex-disk@<username>.service' for load with system start.

serghei commented on 2013-12-09 23:46 (UTC)

Please change PKGBUILD arch='i386' [ "$CARCH" = "x86_64" ] && _arch='amd64' source=("http://repo.yandex.ru/yandex-disk/yandex-disk_latest_${_arch}.deb") md5sums=('b342b34b5503213944c8223e10ebb7ec') [ "$CARCH" = "x86_64" ] && md5sums=('2e89d48eb804f1f83b4f06fb235d19bd') Best regards

geomaster commented on 2013-11-27 09:42 (UTC)

After update process 'yandex-disk' used over 100% (70-80%% per core) CPU

ForeverYoung commented on 2013-10-31 07:51 (UTC)

And some message during installation, that "you need to configure yandex-disk service before first run by this and that..."

ForeverYoung commented on 2013-10-31 07:49 (UTC)

Suggested systemd file: [Unit] Description=Yandex-Disk service for %i After=network.target [Service] User=%i ExecStart=/bin/sh -c "/usr/bin/yandex-disk --no-daemon `cat ~/.config/yandex-disk/config.cfg | grep '=' | xargs -l1 -I0 echo -n '--0 '`" Restart=on-abort [Install] WantedBy=multi-user.target

Ashen91 commented on 2013-09-29 13:49 (UTC)

Hey guys, what about writing a taskbar menu for it? Any ideas how we can do it?

rukolonist commented on 2013-08-27 17:18 (UTC)

It would be better if you will use links to the latest versions: http://repo.yandex.ru/yandex-disk/yandex-disk_latest_amd64.deb and http://repo.yandex.ru/yandex-disk/yandex-disk_latest_i386.deb Of course you still need to update md5 sums.

rukolonist commented on 2013-08-27 17:08 (UTC)

Current version is 0.1.1.281, please update it.