[Solved] megasync update

Message
Author
User avatar
mithrandir
Posts: 26
Joined: Mon Apr 09, 2018 7:51 am

Re: megasync update

#11 Post by mithrandir »

I have fixed by manual installation, but I'd like to know what is the real problem in updating with apt...

User avatar
Eadwine Rose
Administrator
Posts: 11968
Joined: Wed Jul 12, 2006 2:10 am

Re: megasync update

#12 Post by Eadwine Rose »

mithrandir wrote: Wed May 30, 2018 4:26 pm
Eadwine Rose wrote: Wed May 30, 2018 4:23 pm Could someone give me what was in the synaptic repo fields again originally?

I mean.. I just removed the ./ bit, hit reload and now it's gone *snort*


Oh duh.. scroll up lady.... found it.
Have you fixed the problem?
No, since we don't know what the error is. I just put the old original back in.
MX-23.2_x64 July 31 2023 * 6.1.0-20-amd64 ext4 Xfce 4.18.1 * 8core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 525.147.05 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 860EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
mithrandir
Posts: 26
Joined: Mon Apr 09, 2018 7:51 am

Re: megasync update

#13 Post by mithrandir »

Eadwine Rose wrote: Wed May 30, 2018 4:42 pm

No, since we don't know what the error is. I just put the old original back in.
ok... I agree, perhaps there is no solution

User avatar
Richard
Posts: 1577
Joined: Fri Dec 12, 2008 10:31 am

Re: [Solved] megasync update

#14 Post by Richard »

Maybe MEGAsync changed the config of their server?
Advise them of your problem, so the update might work in the future?
or
NOTE: Maybe not. See below. :}
Last edited by Richard on Wed May 30, 2018 5:37 pm, edited 1 time in total.
Thinkpad T430 & Dell Latitude E7450, both with MX-21.3.1
kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.

User avatar
timkb4cq
Developer
Posts: 3206
Joined: Wed Jul 12, 2006 4:05 pm

Re: [Solved] megasync update

#15 Post by timkb4cq »

OK, this appears to be an error in the package that contains all the scripts for the MX Package Installer (mx-packageinstaller-pkglist).
I'll notify the developer.
HP Pavillion TP01, AMD Ryzen 3 5300G (quad core), Crucial 500GB SSD, Toshiba 6TB 7200rpm
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB

User avatar
dolphin_oracle
Developer
Posts: 20024
Joined: Sun Dec 16, 2007 1:17 pm

Re: [Solved] megasync update

#16 Post by dolphin_oracle »

well, if someone can find a new working megasync repo, I'll update it.

this is what megasync puts in the sources when you install manually.

Code: Select all

deb https://mega.nz/linux/MEGAsync/Debian_9.0/ ./
so I think their repo isn't quite right at the moment.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
fehlix
Developer
Posts: 10383
Joined: Wed Apr 11, 2018 5:09 pm

Re: [Solved] megasync update

#17 Post by fehlix »

There is a "bug" whtin the mx-packageinstaller-pkglist as shown here:

Code: Select all

grep -E 'wget.*-o' mx-packageinstaller-pkglist/megasync.pm
wget https://mega.nz/linux/MEGAsync/Debian_9.0/Release.key -o /tmp/megarelease.key
Find the bug!
Hint: s/-o/-O/
Which makes apt complaining about not able to verify the package, as the key is downloaded
but saved under it original name!

Similar "bugs" here:

Code: Select all

$ grep -lE 'wget.* -o' mx-packageinstaller-pkglist/*.pm 
mx-packageinstaller-pkglist/megasync.pm
mx-packageinstaller-pkglist/spotify_32.pm
mx-packageinstaller-pkglist/spotify_64.pm
EDIT: just verfied! -o is not correct, wget needs -O outputfile, with capital "-O"

Code: Select all

LANG=C wget --help | grep -E --  ' -o| -O'
  -o,  --output-file=FILE          log messages to FILE
  -O,  --output-document=FILE      write documents to FILE
f
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
dolphin_oracle
Developer
Posts: 20024
Joined: Sun Dec 16, 2007 1:17 pm

Re: [Solved] megasync update

#18 Post by dolphin_oracle »

maybe, but the install now goes through. I think they fixed their repo.

I'll correct the -O/-o.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
fehlix
Developer
Posts: 10383
Joined: Wed Apr 11, 2018 5:09 pm

Re: [Solved] megasync update

#19 Post by fehlix »

dolphin_oracle wrote: Wed May 30, 2018 7:05 pm maybe, but the install now goes through. I think they fixed their repo.

I'll correct the -O/-o.
Sure, if the Realease.key is already in the keyring.
Otherwise "apt-key add /tmp/megarelease.key" will never work!

If you going to fix mx-packageinstaller-pkglist you might consider to fix this one also:

Code: Select all

-rw-r--r-- 1 fehlix fehlix  0 Jan 13 19:17 Chinese_fonts .pm
the lenght of zero byte.
This is within the just download deb-file mx-packageinstaller-pkglist_18.05.01_all.deb.
If you fetch from git the file 'Chinese_fonts .pm" is not empty.
I assume the reason of the empty file in the deb is because of the "space"
within the filename made a zero-length during packaging.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
dolphin_oracle
Developer
Posts: 20024
Joined: Sun Dec 16, 2007 1:17 pm

Re: [Solved] megasync update

#20 Post by dolphin_oracle »

fehlix wrote: Wed May 30, 2018 7:25 pm
dolphin_oracle wrote: Wed May 30, 2018 7:05 pm maybe, but the install now goes through. I think they fixed their repo.

I'll correct the -O/-o.
Sure, if the Realease.key is already in the keyring.
Otherwise "apt-key add /tmp/megarelease.key" will never work!

If you going to fix mx-packageinstaller-pkglist you might consider to fix this one also:

Code: Select all

-rw-r--r-- 1 fehlix fehlix  0 Jan 13 19:17 Chinese_fonts .pm
the lenght of zero byte.
This is within the just download deb-file mx-packageinstaller-pkglist_18.05.01_all.deb.
If you fetch from git the file 'Chinese_fonts .pm" is not empty.
I assume the reason of the empty file in the deb is because of the "space"
within the filename made a zero-length during packaging.
done and done. no clue on the file name, but anything is possible. it didn't give any errors during packaging, but its fixed now!
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

Post Reply

Return to “Software / Configuration”