Maya

Bug #1074530
Comment #9

Comment 9 for bug 1074530

Revision history for this message

AJNpa80 (ajnelis1) wrote on 2012-11-04:

Didn't work for me, might be me and my system or something, waiting to see results of build bot - if program compiles and package builds with newer dependencies.

I guess the most help I can give is to clarify the problem I had in package manager. I figured out it is maya r317 that synaptic sees, the recent failed build was r372 (which is the one I'm waiting 2 see, same one being rebuilt soon) so it was an older build I've been trying to install.

This time I'll write the actual package names and version #s to remove any confusion. r317 wants libecal-1.2-11 and libedataserver-1.2-16 both (>=3.6) . I have the available versions installed, which are named libecal-1.2-15 and libedataserver-1.2-17, (note the last digit in the names) both of version 3.6.0ubuntu3. Its having a package name that includes a version # in it that breaks the install.

I just wanted to make that much clear because when I origionaly posted it was because the package would not install for that reason. I then saw a correlation in the most recent failed build log while looking for a built deb file to download and edit from the ppa on the launchpad website (in the package details dropdown). Because the website only showed the failed build in that view and I didn't know where else to look, it took me awhile to notice the version number synaptic was seeing. Because the package build failed when working on those libs I guessed it might have to do with each version of those libs having a new package name.

Looks like the new bot build just failed too.

So in the end r317 won't install because the names of them libs change when updated because of their package naming scheme, and r372 won't build the package for whatever reason. I think the first part of the build where it compiled the binary might have worked but I know it didn't build the deb. Might be worth looking at where external dependencies are declared.

I wonder which versions of libecal-1.2-xx and libedataserver-1.2-xx precise has in its repo. I'm guessing 11 and 16 respectively.

Didn't work for me, might be me and my system or something, waiting to see results of build bot - if program compiles and package builds with newer dependencies.

I guess the most help I can give is to clarify the problem I had in package manager. I figured out it is maya r317 that synaptic sees, the recent failed build was r372   (which is the one I'm waiting 2 see, same one being rebuilt soon) so it was an older build I've been trying to install.

This time I'll write the actual package names and version #s to remove any confusion.  r317 wants libecal-1.2-11 and libedataserver-1.2-16 both (>=3.6) .   I have the available versions installed, which are named libecal-1.2-15 and libedataserver-1.2-17, (note the last digit in the names) both of version 3.6.0ubuntu3.  Its having a package name that includes a version # in it that breaks the install.

I just wanted to make that much clear because when I origionaly posted it was because the package would not install for that reason.  I then saw a correlation in the most recent failed build log while looking for a built deb file to download and edit from the ppa  on the launchpad website (in the package details dropdown).  Because the website only showed the failed build in that view and I didn't know where else to look, it took me awhile to notice the version number synaptic was seeing. Because the package build failed when working on those libs I guessed it might have to do with each version of those libs having a new package name.

Looks like the new bot build just failed too. 
 
  So in the end r317 won't install because the names of them libs change when updated because of their package naming scheme, and r372 won't build the package for whatever reason. I think the first part of the build where it compiled the binary might have worked but I know it didn't build the deb. Might be worth looking at where external dependencies are declared.

I wonder  which versions of libecal-1.2-xx and libedataserver-1.2-xx precise has in its repo. I'm guessing 11 and 16 respectively.