Package Details: google-musicmanager 1.0.243.1116_r0-1

Git Clone URL: https://aur.archlinux.org/google-musicmanager.git (read-only)
Package Base: google-musicmanager
Description: A simple application for adding the music files on your computer to your Google Music library
Upstream URL: http://music.google.com
Licenses: custom:musicmanager
Submitter: jumpcannon
Maintainer: vlad
Last Packager: vlad
Votes: 359
Popularity: 2.836971
First Submitted: 2011-07-22 04:41
Last Updated: 2015-12-08 17:33

Latest Comments

rgavs commented on 2015-12-19 18:07

I have the same issue as Binero below

Binero commented on 2015-12-17 19:44

I can't seem to open the options menu once I'm logged in.

nwcatalyst commented on 2015-10-05 19:01

Can anyone verify if this would work on an ARMv5 system?

sl1pkn07 commented on 2015-07-18 18:27

google-musicmanager E: Dependency libid3tag detected and not included (libraries ['usr/lib/libid3tag.so'] needed in files ['opt/google/musicmanager/MusicManager'])
google-musicmanager W: Dependency fontconfig included but already satisfied
google-musicmanager W: Dependency libogg included but already satisfied
google-musicmanager W: Dependency freetype2 included but already satisfied
google-musicmanager W: Dependency xdg-utils included but already satisfied
google-musicmanager W: Dependency libidn included but already satisfied

google-musicmanager E: Insecure RPATH '.' in file ('opt/google/musicmanager/MusicManager')

you can remove this with chrpath [community]

johnnybash commented on 2015-07-12 18:32

Line 30 has to be:

ar -xv ${pkgname}-beta_${pkgver/_/-}_*.deb

without the quotation marks, doesn´t build otherwise

czert commented on 2015-06-11 07:33

amd64 has a new checksum, too: 03987c7a6b53dee9d75fe15dd9aed0f9

mt12345 commented on 2015-04-17 18:39

==> Validating source files with md5sums...
google-musicmanager-beta-amd64-1.0.129.6633_r0.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build google-musicmanager.

terminalmage commented on 2015-04-17 05:54

i686 MD5 is incorrect

MarcObvious commented on 2014-09-29 15:34

New MD5 for AMD64 57aadd30e0a051ee892039bdd573f397

corruptmemory commented on 2014-09-24 16:00

Getting:

==> Building and installing package
==> Making package: google-musicmanager 1.0.117.4968_r0-1 (Wed Sep 24 11:59:25 EDT 2014)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading google-musicmanager-beta-amd64-1.0.117.4968_r0.deb...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 3945k 100 3945k 0 0 2528k 0 0:00:01 0:00:01 --:--:-- 2529k
==> Validating source files with md5sums...
google-musicmanager-beta-amd64-1.0.117.4968_r0.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build google-musicmanager.

chetwisniewski commented on 2014-05-26 01:51

Now the MD5 is 62a310f50ae4416eb351c0b34ff4803a

davidrusu commented on 2014-05-06 18:03

MD5 for AMD64 has changed again it's bb6deb7de4e76d45329fb61c3a02372e

okto commented on 2014-04-05 17:16

Augh, why does it need Qt? I switched to Arch from Ubuntu so I wouldn't have to deal with that!

sjvega commented on 2014-03-14 00:33

I need the new i686 MD5, some one has it? Thanks

Heratiki commented on 2014-03-13 01:58

MD5 has changed for AMD64 yet again. Now it is currently af4fd07b72a8b2ae9456968c5c71b9ef

benjica commented on 2014-03-06 00:30

It appears the md5 for the amd_64 has changed to 7fbfedf8a8189ff0157a2ca590d9402d.

AlD commented on 2014-02-16 17:53

Accidentally marked as outdated, please disregard.

jumpcannon commented on 2013-12-07 21:35

Thanks ares81, updated to reflect the new version.

ares81 commented on 2013-12-06 13:18

For the amd64 version the md5sum is e97bdbad4f907e5d11d985da503e1fe8 .
Please check the PKGBUILD! Thanx!

ares81 commented on 2013-12-06 13:12

Error in the md5sum check!

marzipankaiser commented on 2013-11-01 13:46

@rjrjr:
Had the same problem. Found a workaround here:
http://askubuntu.com/questions/222609/why-does-google-music-manager-refuse-to-open-in-12-04
http://ubuntuforums.org/showthread.php?t=2087385&page=2

Delete ~/.config/google-musicmanager and reinstall.
Then, choose Upload when installing and an empty folder, later you can choose download in the options.

bluefalcon commented on 2013-10-18 15:52

I am getting the following error when I rum makepkg -i on this package:

error: missing package metadata in google-musicmanager-1.0.84.1107_r0-1-x86_64.pkg.tar.xz
error: 'google-musicmanager-1.0.84.1107_r0-1-x86_64.pkg.tar.xz': invalid or corrupted package

Is this happening to anyone else?

rjrjr commented on 2013-10-15 23:23

I'm having some trouble with music manager on 64 bit Openbox running kernel 3.11. The package installed fine, and allowed me to log in, but now I am unable to open the main window. The icon appears in my dock, and I can right click on it to open the menu, but am unable to open the 'Options' window. Double clicking the icon also does nothing.

Kiichiro commented on 2013-10-02 07:43

Here is new md5sums on 2013-10-02:
93dbd28c89a75525841fd64c12ec4df8 - x86_64
7af1a9f89b5ddc2732d848e60c3a502b - i686

supergiox commented on 2013-10-01 18:22

@sh4wn Same problem for me!

sh4wn commented on 2013-10-01 08:10

The MD5 sum of the file doesn't match:

==> Retrieving sources...
-> Found google-musicmanager-beta-amd64-1.0.71.8015_r0.deb
==> Validating source files with md5sums...
google-musicmanager-beta-amd64-1.0.71.8015_r0.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!

mattalexx commented on 2013-09-22 20:30

For some reason, I can't get the window to open when I double click the task bar icon.

supernatendo commented on 2013-07-24 17:28

I have bitcoin-qt running just fine.

jumpcannon commented on 2013-07-23 05:44

@supernatendo Strange. Does that happen with other QT apps?

supernatendo commented on 2013-07-22 02:37

For some reason I get a empty window when I run google-musicmanager. I am running spectrwm with xorg and proprietary nvidia drivers.

tom5760 commented on 2013-07-03 19:05

It seems the package from Google has been updated to 1.0.71.8015_r0. Bumping the pkgver seems to be enough to fix it.

jumpcannon commented on 2013-05-19 20:06

@mattalexx I'll continue updating the package to whatever Google puts out. As of right now, the new Google Play Music thing only changes the website and the Android app, the musicmanager is the same as the old one.

mattalexx commented on 2013-05-19 01:07

Is this going to be updated to the recently updated manager?

gridcol commented on 2013-05-03 06:01

Good news here.
After the package update (or whatever happend.. there was a new PKGBUILD in the AUR) google-musicmanager runs smoothly. No error message after a few seconds, I could upload all my songs at once.

jumpcannon commented on 2013-05-02 22:48

The package needs qt4 but qtwebkit pulls that in so it doesn't need to be listed explicitly at all. Long story short, I accidentally used an old template for the PKGBUILD which is what caused qt to get listed again, but the condition that lead to that happening has been fixed. Sorry for any inconvenience!

jumpcannon commented on 2013-05-02 22:47

Yeah, the package needs qt4 but qtwebkit pulls that in so it doesn't need to be listed explicitly at all. Long story short, I accidentally used an old template for the PKGBUILD which is what caused the error, but the condition that lead to that happening has been fixed. Sorry for any inconvenience!

jumpcannon commented on 2013-05-02 22:46

Yeah, the qt dependency shouldn't be there at all (qtwebkit pulls in qt4).

ender4 commented on 2013-05-02 02:34

The qt dependency doesn't work since it is a meta package, and therefore not provided by any one package.

luolimao commented on 2013-05-01 16:04

sed -i "/^depends=/ s|'qt'|'qt4'|" PKGBUILD
:)

vendion commented on 2013-05-01 12:07

The dependency probably should be qt4 instead of qt which is a metapackage for qt5.

Driadan commented on 2013-05-01 11:28

had to drop the 'qt' dependency as it was complaining of not having it despite I did have it.
After that, it builded ok.

Not sure if the dependency is incorrectly named or it's a bug of either yaourt or pacman

dapilori commented on 2013-04-29 20:07

@tiberiousr

Thank you very much, I solved by reverting to the old naming scheme of network interfaces with:
ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules

tiberiousr commented on 2013-04-29 19:47

@dapilori : This is a known issue due to Arch not using the old ethN/wlanN network device naming scheme.

See this thread for a work-around, I believe it's around 1/2 way down the page: https://bbs.archlinux.org/viewtopic.php?id=130688

tiberiousr commented on 2013-04-29 19:44

@dapilori : This is a known issue due to Arch not using the old ethN/wlanN network device naming scheme.

See this thread for a work-around, I believe it's around 1/2 way down the page: https://bbs.archlinux.org/viewtopic.php?id=130688

dapilori commented on 2013-04-29 19:29

I get this error:
Login failed. Could not identify your computer

Any ideas?

gridcol commented on 2013-04-18 18:33

Thanks for the link pajmullaney.

I posted the issue on the arch linux forums:
https://bbs.archlinux.org/viewtopic.php?id=161731

gridcol commented on 2013-04-18 18:14

Thanks for the link pajmullaney.

I posted the issue on the arch linux forums:
https://bbs.archlinux.org/viewtopic.php?id=161731

jumpcannon commented on 2013-04-18 14:50

Thanks gridcol, unfortunately that sounds like an upstream bug. The following thread may be of interest to you:

http://productforums.google.com/forum/#!msg/apps/pP7G8IosLVc/ixxQ5Qd6GKkJ

You should also feel free to make a post on the archlinux forum to see if anyone there has encountered the problem and figured out a way to solve it.

gridcol commented on 2013-04-18 09:24

Thanks for your reply pajmullaney.

As I said, google-musicmanager worked fine a few weeks. I had the system tray and could work with it, all fine so far.
What I was doing is this:
I added folders to google-musicmanager incrementally:
../music/bandA
../music/bandB
../music/bandC

Then I wanted google-musicmanager to recognize new music in my ../music/ folder. I removed all the folders and just added ../music/. Silly google-musicmanager wanted to upload all my files again, so I closed google-musicmanager, removed my whole library on Google Music, waited one day to do it properly, started google-musicmanager again and gave it a run.
After having google-musicmanager started a few seconds, it terminates with the following message:
"Successfully sent the minidump file."

google-musicmanager.log says (replaced user with $user):
2013-04-17 15:17:51,391 +0200 INFO TId 0x7f006bfff700 Calling ParseMp3 </home/$user/music/The Baseballs/Strings 'n' Stripes/17 Torn (live).mp3> [FileScanner.cpp:60 FileScanner::addFileTypeInformation()]
2013-04-17 15:17:51,429 +0200 INFO TId 0x7f00697fa700 Child Exited 0 [exception_handler_linux.cpp:78 ::LinuxCrashCallback()]

There's nothing wrong with the files. I had all of them already up on Google Music and didn't touch them since then. Does this information help in any way?

jumpcannon commented on 2013-04-18 07:19

gridcol, tyr0: As I've stated previously, the correct behavior for the program is to fork off into the background when started (thus if you start it from the command line it appears to have exited). The icon should appear in your system tray, if you have one - I do not recommend using it without a tray because then you will have no way to interact with the GUI. If your desktop environment or window manager does not provide a system tray, you can use e.g. stalonetray (which is in community).

Please note that this behavior is not in any way connected to the logging system - if you do not have log4cxx installed google-musicmanager will print the messages telling you so, but will still work normally (without logging, of course). If you want to get rid of those error messages or have access to the program's logs, please install log4cxx from the AUR. It is listed as an optional dependency because the core functionality of google-musicmanager does not depend on log4cxx being installed.

If you can confirm that the program actually crashes, you're going to need to do a bit of digging and provide some additional information. I have just tested the program on a fresh install and it continues to work as expected both with and without log4cxx installed.

gridcol commented on 2013-04-17 16:44

musicmanager worked fine here until I removed my folders and tried to re-upload all my stuff. Now musicmanager quits the way tyr0 explained.

I don't get it... looking forward for a genius solution.

gridcol commented on 2013-04-17 16:43

musicmanager worked fine here until I removed my folders and tried to re-upload all my stuff. Now musicmanager quits the way tyr0 explained.

I don't get it... looking forward for a genius solution.

tyr0 commented on 2013-04-11 18:53

I do have the same problem as mentioned by several other users:
log4cxx: No appender could be found for logger (root).
log4cxx: Please initialize the log4cxx system properly.

Afterwards I get the message "Successfully sent the minidump file." and google-musicmanager quits. Has anyone found a solution for this strange behavior?

oneeyed commented on 2013-03-28 19:45

==> Validating source files with md5sums...
google-musicmanager-beta-amd64-1.0.55.7425_r0.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!

jumpcannon commented on 2013-03-01 23:31

That should be already been taken care of, jyc. Are you still having problems?

jyc commented on 2013-03-01 23:29

Needs to be updated for the qt -> extra/qt4 rename.

https://www.archlinux.org/news/qt4-replaces-qt/

jumpcannon commented on 2013-02-27 20:56

ascarpino, thanks for the heads-up.

jumpcannon commented on 2013-02-27 20:55

ascarpino, thanks for the heads-up.

jumpcannon commented on 2013-02-27 20:52

ascarpino, thanks for the heads-up.

ilpianista commented on 2013-02-27 14:54

Please drop qt from the depends array as qt is already required by qtwebkit.

Otherwise people that use [testing] will get:
:: spotify: requires qt>=4.5.0

There's no more a 'qt' package in [testing] (and in the next days in [extra])

duffydack commented on 2013-02-15 17:44

I can confirm that reverting my interface naming back to eth0 has fixed my authentication issue.

Anonymous comment on 2013-02-14 18:45

I was able to get past this goofy nonsense by doing the following:

tunctl -t wlan0 -u myusername
ip link set up address 00:04:5a:xx:xx:xx
ip addr add 10.0.0.1/24 dev wlan0

I do not pretend to know if it needed a valid mac (which I didn't have, I use a private number scheme). It wasn't able to identify my computer until I added the ip address with the link up. So, does it use interface names inappropriately, the mac? the IP? it didn't work for me until it had all three to this pretend interface. Now I'm logged in. ymmv.

alucryd commented on 2013-02-12 11:07

Apparently I'm not the only one affected, see here:
http://productforums.google.com/forum/#!msg/apps/PjN5g6Mujuw/p1H8Rm0Uvc4J
http://ubuntuforums.org/showthread.php?t=2087385

There are some temporary workarounds...

alucryd commented on 2013-02-11 15:04

I'm getting the same log4cxx error as everyone, but MusicManager runs almost fine afterwards. I'm saying almost cause I can successfully log in, and choose to download my library in my music folder. However as soon as I click "start" (or whatever that button is called) the window disappears. It seems the downloading is taking place since my music is regularly appearing and the MusicManager process is active, but is the window supposed to disappear?

jumpcannon commented on 2013-02-10 19:38

systemd isn't the problem, I'm using systemd and it works just fine.

Do let me know if the RPM version works for you, I can switch the package over to that version if it helps, but since the DEB version is working for me I can't really test it myself.

Anonymous comment on 2013-02-10 19:32

I am also getting the error message "Login Failed: Could not identify your computer".
I am using systemd and I don't see why it should not work with it.

@dblue
I tried you approach, unfortunatly with no success.

How does the authentification work on other platforms? I think Fedora is using systemd since version 15 or 16.

Maybe you should use the RPM instead of the DEB. I think I give it a try tomorrow and let you know...

Anonymous comment on 2013-02-08 19:05

After I updated my system to use systemd, I started getting the login failed error too. It was fixed for me by reverting back to the eth0 style names using:

ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules

I only tried it with my wi-fi adapter, changing back to wlan0 from wlXXX0, but I guess it'd work for ethN as well as wlanN devices.

Anonymous comment on 2013-02-05 18:06

I am getting the same error message "Login Failed: Could not identify your computer" I am not using a virtual machine

laydros commented on 2013-02-04 16:04

I'm getting the error "Login Failed: Could not identify your computer" Are those of you having success using the kernel switch to enable eth0 style interface names, or am do I have another problem?

jumpcannon commented on 2013-02-03 15:10

duffydack, logging in and uploading music continues to work on my machine - unfortunately that sounds like an upstream bug, which I won't be able to help you with :/

KerrickStaley, does it actually exit, or just fork and return to the console? The expected behavior is that the app forks on launch. Check your system tray, there should be an icon there you can interact with if you need to change your settings or anything.

I also get the log4cxx error, but logging isn't actually necessary for the app to work (which is why I've listed it as an optional dependency). I suspect that the upstream devs are doing something wrong with the logging system. I don't run an Ubuntu system, but I'd be curious to see if logging even works there.

duffydack commented on 2013-01-31 17:55

Just updated (google-musicmanager-1.0.55.7425_r0-1) and still get same error as KerrickStaley and the app itself won't recognise 'me' when I try log in.

KerrickStaley commented on 2013-01-30 08:30

When run, google-musicmanager prints

log4cxx: No appender could be found for logger (root).
log4cxx: Please initialize the log4cxx system properly.

and exits with code 0. Any guesses as to why? log4cxx is installed (although log4cxx might not be related to the issue at all).

KerrickStaley commented on 2013-01-30 07:42

The MD5 checksum for
google-musicmanager-beta-amd64-1.0.54.4672_r0.deb
needs to be changed to
6fcc9c3477d34041134fd77648d961de

Anonymous comment on 2012-12-13 07:48

MD5 update for i386

ce8f23d422aac8ad33b78ba25ec75ebd

Anonymous comment on 2012-12-13 01:56

md5 update for google-musicmanager-beta-amd64-1.0.51.1573_r0.deb:

83881ad51c559f98cf0a1f0d09277cd2 should be 67b3edcf1f68ef53a22c99a7dff87022



--- PKGBUILD 2012-11-01 20:17:08.000000000 +1100
+++ PKGBUILD.new 2012-12-13 11:44:32.642394774 +1100
@@ -15,7 +15,7 @@

if [ "$CARCH" = "x86_64" ]; then
_arch='amd64'
- md5sums=('83881ad51c559f98cf0a1f0d09277cd2')
+ md5sums=( '67b3edcf1f68ef53a22c99a7dff87022')
elif [ "$CARCH" = "i686" ]; then
_arch='i386'
md5sums=('7c5e224bbac5d0d0c925fa817c5e8282')

Anonymous comment on 2012-12-11 16:40

pajmullaney, I thought that was the issue but I haven't experienced this issue before. Thanks for the suggestion, I didn't think that changing that setting would make a difference. It did. :)

jumpcannon commented on 2012-12-09 23:42

TheCuban, you're saturating your connection. If you plan to use a web browser while uploading music, you need to set the musicmanager's throttle appropriately.

Anonymous comment on 2012-12-09 21:50

I've noticed an issue with Google Music Manager. My internet starts acting extremely wonky. Anybody else notice a similar issue? Where browsing web pages or downloads start working intermittently?

Anonymous comment on 2012-12-02 07:51

I reinstalled it and works, thanks :D

jumpcannon commented on 2012-12-01 20:03

Jaxmetalmax, are you on the latest version? Everything works correctly on my machine, and teratomata said that it works correctly on theirs also.

Anonymous comment on 2012-12-01 04:43

It works, but as "teratoma" said, the Option thing is not responsive, it's not working for me, do you know any solution?

dmikalova commented on 2012-11-26 21:31

Hmm, it works now, the Options thing was not being responsive previously. Still getting a log4cxx problem but it doesn't seem to matter.

jumpcannon commented on 2012-11-20 23:19

Hey, maybe this is a silly question, but have you guys tried right-clicking on the tray icon and selecting "Options"? Unlike older versions of the client (iirc), it doesn't automatically open the options window on launch. Or are you talking about a different GUI?

jumpcannon commented on 2012-11-20 18:39

@teratomata is the current version not working for you? It installs and works correctly on my system.

dmikalova commented on 2012-11-20 15:48

Not a fix to the log4cxx problem, but I was able to install a working version using the 1.0.35.1577 version from http://google-music-manager.en.uptodown.com/ubuntu/old changing the MD5sum in the PKGBUILD, and installing lib32-libdidn and lib32-qt.

Anonymous comment on 2012-11-04 05:08

Anyone figured out a way to fix the log4cxx issues? The service starts, but the UI never shows after logging in for me. I assume it's related to the log4cxx errors since I never had this problem before the November update.

log4cxx: No appender could be found for logger (root).
log4cxx: Please initialize the log4cxx system properly.

Only errors that show so I don't really have much to go on.

jumpcannon commented on 2012-08-27 07:59

@uberbrodt To answer your rhetorical question, I had the cronjob set to run weekly. That was probably a dumb default. It'll now run daily, and it'll also proactively check for updates rather than waiting for someone to flag the package out-of-date.

Anonymous comment on 2012-08-25 00:50

How long does it take for your script to run? MD5 sums have changed again...

jumpcannon commented on 2012-06-12 00:49

@PotHix It's fixed.

If you guys catch the md5 thing before I do in the future, just flag the package out-of-date, that'll trigger a script I use to build and re-upload automatically. Thanks ;)

PotHix commented on 2012-06-11 23:30

md5 has changed again a528855ac7e944c920612fca8a73fa6d

ctarwater commented on 2012-05-26 14:47

Here's the correct md5sum for the current google-musicmanager-beta_current_amd64.deb: 374dda21c0be17e9290fc30798fa2d07

allen875 commented on 2012-05-25 07:46

google seems to have changed there package name format to (google-musicmanager-beta_current_amd64.deb) so the pkgbuild is throwing a validity check error.

jumpcannon commented on 2012-05-12 13:39

@dxxvi Thanks for the heads-up, fixed.

dxxvi commented on 2012-05-12 09:56

google-musicmanager seems to need libQtWebKit.so.4, which is in qtwebkit, to run.

jmrenner commented on 2012-03-12 03:18

I'm getting a can't connect to server error. Yes my internet is up and running. And I can connect to play.google.com but for some reason it doesn't want to connect to upload anything... (updated package on March 11,2012 )

jmrenner commented on 2012-03-12 03:17

I'm getting a can't connect to server error. Yes my internet is up and running. And I can connect to play.google.com but for some reason it doesn't want to connect to upload anything... (updated package on March 11,2012 )

jmrenner commented on 2012-03-12 01:40

I'm getting a can't connect to server error. Yes my internet is up and running. And I can connect to play.google.com but for some reason it doesn't want to connect to upload anything... (updated package on March 11,2012 )

Anonymous comment on 2012-03-10 04:45

@jackgu1988: Yes, it could be a security issue. But if you turn on Google's 2-step verification, then you don't have to worry about a thing.

Another thing: The package failed the md5sum check. I calculated the sum, and edited the PKGBUILD file with the new value, and it built. So far I haven't noticed any problems.

jackgu1988 commented on 2012-01-30 12:09

If you want your password to be saved, you have to edit /opt/google/musicmanager/google-musicmanager.desktop and add -p <and your password here> in the end of the Exec line. This brings up some security issues though, as someone can cat this file and see it. It's up to you.

techlive commented on 2012-01-30 10:30

One last thing you guys should known is that this PKGBUILD is using an auto fetch tweak to get the neweast version number of the pkgver.That means at the end of makepkging you always get the latest version of the google musicmanager pkg tarball despite which version of the PKGBUILD you are using.

Because of the following code, it extarct the exact version string from the deb control file and will not mess up the AUR.

:;pkgver=`grep "Version" control | cut -d: -f2 | sed 's/^ *//g' | sed 's/ *$//g' | sed 's/-/_/g'`

So, if there is a new version appeared, what you need to do is remakepkg the PKGBULD, and the remind here to update of the PKGBUILD.

techlive commented on 2012-01-30 10:16

The PKGBUILD has been updated, sorry for the delay, I am on a Chinese lunar new year vacation for the past seven days, and Happy Chinese Dragon Year!

@acfrazier, thanks for the reminding, @FredBezies, thanks for prividing the updated PKGBUILD.

There is one thing I have to explain is that the pacakage name is google-musicmanager-beta_current_$arch.deb while downloading, but has been renamed to google-musicmanager-beta-${_arch}-${pkgver}.deb to avoid conflicting with the last download source,because the name of the source tarball are always the google-musicmanager-beta_current_$arch.deb.

Otherwise if one last version google-musicmanager-beta_current_$arch.deb existed in the makepkg source dir, the makepkg won't download the new one, and this will cause md5sum checking fails.

FredBezies commented on 2012-01-27 16:53

Updated PKGBUILD : http://pastebin.com/ZwtzMNFP

acfrazier commented on 2012-01-25 20:26

Flagging this out of date, PKGBUILD needs updated, current version is 1.0.24.7712. The deb is now called google-musicmanager-beta_current-$arch.deb

md5 for x64 is 21f981fda89e10791d06fc9c6ac73e67
md5 for x86 is 9918c083e638a00ab506e55ae80c58a3

Anonymous comment on 2011-12-22 21:32

My bad, I didn't realize that package exists. I'll try to contact the maintainer of the [google-musicmanager] package, to update the description, so the package can be found when searching for "google music".

techlive commented on 2011-12-22 21:26

This package is duplicated with [google-musicmanager]:https://aur.archlinux.org/packages.php?ID=50891

Google only provide one downloadable version of google-musicmanager,sometimes is a release version and sometimes is a beta verion,there is no difference between stable version PKGBUILD ond beta version PKGBUILD like other package,so there is no need to create a beta version PKGBUILD alone.

I will ask the AUR mailing list to delete this package.

techlive commented on 2011-12-22 19:29

There are two ways that will cause an md5sum check error:

1. A previous downdload deb file already existed in your sources directory (In most case,it is your current directory where your PKGBUILD existed,unless you edited /etc/makepkg.conf or ~/.makepkg.conf and changed the $SRCDEST variable) which will cause the makepkg not download the new deb file if they have the same name.This is accturally what Google doing by update their deb file without changing the name of the file.In this case,either your manually delete the existed deb file or, the best to modify the PKGBUILD, change as the following.

form

source=("http://dl.google.com/linux/direct/google-musicmanager-beta_current_${_arch}.deb")

to

source=("google-musicmanager-beta-${_arch}-${pkgver}.deb::http://dl.google.com/linux/direct/google-musicmanager-beta_current_${_arch}.deb")

and using google-musicmanager-beta-${_arch}-${pkgver}.deb later to extract.

2. The other way is that this PKGBUILD is outdated because Google has updated an new def file without changing its name.WTF!In this case,either you modify the PKGBIULD yourself or just flag the PKGBULD outdated and wait the maintainer to update it sometime.

techlive commented on 2011-12-22 19:28

There are two ways that will cause an md5sum check error:

1. A previous downdload deb file already existed in your sources directory (In most case,it is your current directory where your PKGBUILD existed,unless you edited /etc/makepkg.conf or ~/.makepkg.conf and changed the $SRCDEST variable) which will cause the makepkg not download the new deb file if they have the same name.This is accturally what Google doing by update their deb file without changing the name of the file.In this case,either your manually delete the existed deb file or, the best to modify the PKGBUILD, change as the following.

form

source=("http://dl.google.com/linux/direct/google-musicmanager-beta_current_${_arch}.deb")

to

source=("google-musicmanager-beta-${_arch}-${pkgver}.deb::http://dl.google.com/linux/direct/google-musicmanager-beta_current_${_arch
}.deb")

and using google-musicmanager-beta-${_arch}-${pkgver}.deb later to extract.

2. The other way is that this PKGBUILD is outdated because Google has updated an new def file without changing its name.WTF!In this case,either you modify the PKGBIULD yourself or just flag the PKGBULD outdated and wait the maintainer to update it sometime.

techlive commented on 2011-12-22 18:33

New version came out:

pkgver=1.0.23.1334.r0

if [ "$CARCH" = "i686" ]; then
_arch='i386'
md5sums=('6388d3f89a5f04c7aec991228a90030f')
elif [ "$CARCH" = "x86_64" ]; then
_arch='amd64'
md5sums=('f98a581295d9c338e754422ea279f337')
fi

Anonymous comment on 2011-12-22 14:17

FYI this build does not have the Download option if you have purchased music through the Market.

rjrjr commented on 2011-12-19 00:51

I also got the error described by drdrewdown:

==> Validating source files with md5sums...
google-musicmanager-beta_current_amd64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
The build failed.

My current directory should be home, but I don't see a .deb, just 2 empty files, one is named "ERROR:" and the other is "Validating".

Any thoughts?

techlive commented on 2011-11-29 05:10

I think that the filename of the downloaded deb file should be appended with the version number in case of checksum error for the next makepkging.

techlive commented on 2011-11-29 05:07

@drdrewdown You need to manually delete the existed google-musicmanager-beta_current_amd64.deb file in your source files directory (in most cases,it is your current directory unless you have changed it in makepkg.conf) and re-makepkg it.

drdrewdown commented on 2011-11-29 05:02

is it just me?

==> Validating source files with md5sums...
google-musicmanager-beta_current_amd64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!

Anonymous comment on 2011-11-22 16:20

That works perfect for me now thanks ....

Anonymous comment on 2011-11-22 07:50

Changes in 1.0.22.3409.r0-1:
* Updated to 1.0.22.3409-r0
* Fixed building on both i686 and x86_64
* Temporarily added "options=(!strip)" until I can figure out what's causing strip to fail on minidump_upload

jumpcannon commented on 2011-11-22 03:06

@DruKe: This package is sourced from Google's official repository, so it will always contain the most up-to-date version. Interestingly, they didn't actually update the client when they pulled Music out of Beta; the change was entirely a marketing gimmick.

Anonymous comment on 2011-11-22 03:01

It looks like they've released a new version today 1.0.22.3409-r0. That explains while the md5sum was different. Will look into the other ERROR you get once I'm home.

Anonymous comment on 2011-11-22 02:40

ok well yes i change PKGBUILD with i386 in work but after recopile here is another error ..


==> Tidying install...
-> Purging other files...
-> Compressing man and info pages...
-> Stripping unneeded symbols from binaries and libraries...
/usr/bin/strip:./opt/google/musicmanager/minidump_upload: File format not recognized
==> ERROR: Makepkg was unable to build google-musicmanager-beta.

another thing the md5sum for i386 is this 09ff61f45410b52aa10b60f13d0daa55 , well this work for me ... i hope you can help me with this

Anonymous comment on 2011-11-22 00:59

Thanks a lot for catching this, I'll upload a fixed version tonight, meanwhile if you want you can just edit the PKGBUILD yourself, change the line:
ar xv google-musicmanager-beta_current_amd64.deb || return 1
to
ar xv google-musicmanager-beta_current_$ARCH.deb || return 1

Anonymous comment on 2011-11-22 00:49

Starting build()...
ar: google-musicmanager-beta_current_amd64.deb: No such file or directory
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build google-musicmanager-beta.

i get this error i try to build in i386 ...

Anonymous comment on 2011-11-21 18:52

Yup it's working properly. Didn't know if there were any new features we may be missing out on however.

Anonymous comment on 2011-11-21 06:30

Changes in 1.0.18.6104.r0-2:
* Removed deb specific cron job
* Moved *.desktop file from /opt to /usr/share/applications so DEs can find it and at to application menu automatically.
* Moved the icons from /opt to /usr/share/icons/hicolor/*x*/apps so DEs can find them

Anonymous comment on 2011-11-20 07:01

I would really appreciate it if someone could test this on i686.

jumpcannon commented on 2011-11-17 21:21

@DruKe: Did the package not build correctly for you? I just tested it and it still works for me; even though it's officially out of beta they still use the same URLs for the musicmanager packages.

Anonymous comment on 2011-11-17 14:15

Bump - Google took the product out of beta.

Nebulosa commented on 2011-09-27 14:02

It's already 1.0.18.6104.

jackgu1988 commented on 2011-09-26 14:04

I got version 1.0.18 on my debian today. Please update :)

techlive commented on 2011-09-23 07:11

@ladr0n,that's all right,for now,it seems all work fine after changing the install path.

jumpcannon commented on 2011-09-22 17:13

@loganfynne: What does it use log4cxx for? I do not have log4cxx installed and the musicmanager seems to work correctly for me without it; furthermore, log4cxx isn't in the main repositories and I'm hesitant to add something from AUR as a dependency if it isn't actually required to use the program. I'll add it as an optdepends at least, just in case people want it.

@techlive: The AUR package for Google Chrome is also installed into /opt/google, so I followed that precedent. You are correct that the arch packaging guidelines do suggest putting packages in /opt/{pkg} rather than /opt/{vendor}/{pkg}; my only concern is that some Google programs might (stupidly) assume that other Google programs are installed in /opt/google. I'll move it for now as you suggest but if it turns out that some other Google program wants google-musicmanager to be in /opt/google later on, I'll have to move it back. Thanks for the updated PKGBUILD

jumpcannon commented on 2011-09-22 17:11

@loganfynne: What does it use log4cxx for? I do not have log4cxx installed and the musicmanager seems to work correctly for me without it; furthermore, log4cxx isn't in the main repositories and I'm hesitant to add something from AUR as a dependency if it isn't actually required to use the program. I'll add it as an optdepends at least, just in case people want it.

@techlive: The AUR package for Google Chrome is also installed into /opt/google, so I followed that precedent. You are correct that the arch packaging guidelines do suggest putting packages in /opt/{pkg} rather than /opt/{vendor}/{pkg}; my only concern is that some Google programs might (stupidly) assume that other Google programs are installed in /opt/google. I'll move it for now as you suggest but if it turns out that some other Google program wants google-musicmanager to be in /opt/google later on, I'll have to move it back. Thanks for the updated PKGBUILD

techlive commented on 2011-09-22 16:35

Please install this package into /opt/google-musicmanager instead of the /opt/google/musicmanager which is not an arch way of packaging and installing,here is an updated and improved PKGBUILD,it is very appreciate if you use it. http://pastebin.com/6vVy2k0L

Anonymous comment on 2011-09-18 17:40

This requires the log4cxx package. Could you please add that as a dependency?

Anonymous comment on 2011-09-04 21:16

Current version is 1.0.16.6403

rafaelff commented on 2011-08-26 02:07

Looks like this custom license is missing in this package. This might be a problem, considering that this software is only available for USA. See my access to their site: http://img268.imageshack.us/img268/3978/googlemusic.png

Cheers

jumpcannon commented on 2011-08-26 02:06

@josephgbr: As others have mentioned, you can sign up for the service by using a U.S. proxy. Once you've signed up, they do not check your IP address for use with the client. This probably technically violates the T.O.S., so use at your own discretion.

jumpcannon commented on 2011-08-26 01:52

@josephgbr: As others have mentioned, you can sign up for the service by using a U.S. proxy. Once you've signed up, they do not check your IP address for use with the client. This probably technically violates the T.O.S., so use at your own discretion.

rafaelff commented on 2011-08-26 01:47

Looks like this custom license is missing in this package. This might be a problem, considering that this software is only available for USA. See my access to their site: http://img268.imageshack.us/img268/3978/googlemusic.png

Cheers

MatejLach commented on 2011-08-25 23:48

For anyone who wants an updated and functional PKGBUILD:
http://pastebin.com/im8GAa4n
[I HOPE NO ONE WILL BE CLAIMING THAT I DID NOT EDITED ANYTHING]

Anonymous comment on 2011-08-01 20:26

Great!

Anonymous comment on 2011-07-22 16:25

It runs (i686) and is about to realize i already had uploaded my music with the wine version :) Thank you all very much, i will add comments if anything goes wrong so you will know. Will try to notify in the forum too: https://bbs.archlinux.org/viewtopic.php?id=122983
If the topic changes it may be nice to point it out here.

mtorromeo commented on 2011-07-22 16:20

I'm not sure, I only have x86_64 systems.
Maybe someone else will be able to answer this question.

jumpcannon commented on 2011-07-22 16:16

@mtorromeo: "With options=(!strip)" on i686 will the program actually run, or just not fail to build?

Anyway, added those changes, thanks for the feedback!

mtorromeo commented on 2011-07-22 15:55

A couple of suggestions, since I was also preparing a PKGBUILD:

The provides and conflicts lines are unecessary.
If you add "options=(!strip)" the package will build on i686.
The current version is 1.0.13.9715 (shown in the about tab).
As jck already said, libidn is a dependency.




jck commented on 2011-07-22 10:13

libidn should also be a dependency

jumpcannon commented on 2011-07-22 08:04

As it happens, Google put a 64-bit binary in their 32-bit package, so this won't work on i686 until they fix that. I've filed a bug report (I think, it's not entirely clear how to file a bug report for Google Music).

jumpcannon commented on 2011-07-22 07:59

As it happens, Google put a 64-bit binary in their 32-bit package, so this won't work on i686 until they fix that. I've filed a bug report (I think, it's not entirely clear how to file a bug report for Google Music).