From: Paul Colquhoun <paulcol@andor.dropbear.id.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] MEGA sync problems
Date: Sat, 09 Oct 2021 10:34:30 +1100 [thread overview]
Message-ID: <7295958.EvYhyI6sBW@bluering> (raw)
In-Reply-To: <3e1f020e-82fa-b185-d3ef-c82e2848d826@204EastSouth.com>
[-- Attachment #1: Type: text/plain, Size: 2364 bytes --]
On Saturday, October 9, 2021 7:33:04 A.M. AEDT Skippy wrote:
> Greetings.
>
> I have been using Megasync with Gentoo for many moons. Now I'm having an
> assortment of problems.
>
> Mega is not in the official Gentoo. I've been getting my ebuilds from here:
>
> http://gpo.zugaina.org/net-misc/megasync
>
> I currently have 4.4.0 installed. This was working fine until about 2-3
> weeks ago. Now I get this error message when I attempt to start it.
>
> --------------------
> ------------------------------------------
>
> There are newer versions available so I figured this was a good
> indicator I should just update Megasync.
>
> Well the universe hates me and every version of Megasync newer than
> 4.4.0 fails. In fact if I attempt to re-emerge my existing 4.4.0 that
> fails as well.
>
> Here is the full emerge log for version 4.5.3.
>
> https://zerobin.net/?e8b7f31b1ce11c23#4wTnxsnZ+v31rS8PLplBxM+//23zC5b0rMXSAT
> uoYDQ=
>
> I've been informed that 4.5.3 is failing because it needs <=ffmpeg-3.4.
>
> That brings me to how to install such a version of ffmpeg. My limited
> understanding of slots tells me this should be possible, but I've yet to
> find anything explaining how to install the older ffmpeg without
> disturbing the newer version.
>
> Any help with this would be greatly appreciate. Much thanks.
>
> Skippy
> -----------------------------------------
>
> root # emerge -pqv '=net-misc/megasync-4.5.3::Skippy'
> [ebuild U ] net-misc/megasync-4.5.3 [4.4.0] USE="cryptopp curl
> readline sqlite thunar zlib -dolphin -examples -freeimage -gnome -java
> -nautilus -php -python -threads (-qt5%*)" ABI_X86="32 (64) (-x32)"
>
> ------------------------------------
It looks like you are downloading the ebuild by hand from their web site.
I just installed Megesync 4.5.3 on my system, which has ffmpeg-4.4
The commands I used were:
layman -a 4nykey
to add the 4nykey overlay, which contains megasync, then
emerge -a megasync
just like other portage programs.
If you still get any crypto-related errors, have a look for the recent news item
"*2021-07-23-libxcrypt-migration*"
eselect news list
will get you a list.
--
Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/
Asking for technical help in newsgroups? Read this first:
http://catb.org/~esr/faqs/smart-questions.html#intro
[-- Attachment #2: Type: text/html, Size: 7473 bytes --]
prev parent reply other threads:[~2021-10-08 23:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 20:33 [gentoo-user] MEGA sync problems Skippy
2021-10-08 20:43 ` Michael Orlitzky
2021-10-08 23:34 ` Paul Colquhoun [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7295958.EvYhyI6sBW@bluering \
--to=paulcol@andor.dropbear.id.au \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox