Maya 12.10 broken unresolved deps.

[AJNpa80]

I was wondering if libecal and libedataserver dep.s for maya still specificly need those versions ( if they had broken compat.in the new versions) or if not could the pkg be switched to require greater than (>=)the listed version. In quantal repos those evolution support libs are at 1.3xxetc. where maya wants 1.2xxyada-yada. I'm gonna spend a few minutes to download manualy and try to alter the pkg. deps I guess but figured I'd post because I couldn't find an obvious answer quickly. Might be a minor bug, I saw the most recent build for quantal failed, might be why.

in summary, now requires both packages example: libdadada 1.2boohoo
quantal repos have lets say: libdadada 1.3poopypoo
can we change to libdadada >=1.2skidooo

[AJNpa80 (ajnelis1)]

 I just realized i posted this in elementary in general having just found the maya project, my apologies in advance if needed. If it's any consolation I came here first because I install from from the elem.os daily ppa. I had started out posting in questions & answers and realized they don't get much traffic there and the bug reports get used for everything from want-ads to human interest stories so I put it here. This is one of the first bug reports I've filed because I always doubt if things qualify or are in the right place and the wall of etiquette can seem daunting. Thanks.

[Cody Garver (codygarver)]

Were you able to compile on your version of Ubuntu without modifying the CMakeLists.xt?

[Niels Avonds (niels-avonds)]

Cody: from what I read, the user is installing from the repository and modifying the .deb file instead of checking out the repository (is this correct?).
Please do let us know if it runs with these dependencies, since I currently don't have a Quantal machine to test on.
Thanks for the report :)

[AJNpa80 (ajnelis1)]

Ok folks sorry I dissappeared my dog of 12 years died and I just buried him. I'll clarify what I meant by taking you through my thought process step by step. I upgraded to quantal awhile ago and was just getting around to reinstalling elem on top of it using synaptic. The default rule is to favor quantal pkgs so in synaptic I only see pkgs in ppa listed for it. I selected pantheons meta and elemos desktop meta. I selected other elem progs that weren't selected. I noticed maya wasn't selected but was listed in ppa so when I clicked on it it listed as broken with libedataserver and libecal deps. unsatisfiable. It requests specific version, and the versions of those libs available for quantal are 1.3xxx as opposed to 1.2xxx so from there I was wondering if the developers requested that version intentionally, and in the meantime I thought I'd just go to the ppa, download the amd64 deb file, open it and edit the meta data to require the listed version or higher and see if it worked. I only got that far now because of my dog. Upon further inspection I see maya has failed to build for quantal, (I had thought it was only the most recent one) so I read the build log, and it complains that those two libs should be added to the build directory for quantal directly which might be the way to go if you are depending on that version explicitly because of broken compat. upstream or something similar. That should get it to build but the package manager still wants it installed, so it will come up broken unless quantal users manually download the old version or the dependency is removed after the library is embedded.. If you don't absolutely need that version, editing the metadata so it requires 1.2 as the minimum version should let the build bot and peoples package managers find the required libraries (which are already installed on my computer). I know how to edit .deb files dependencies to install them, but because there wasn't one available I haven't had time to try to checkout a branch and try to build and install it on mine. I hope this helps clarify.
 So from here the question is whether that version is needed explicitly, keep in mind if maya precise also requests a static version it will be in the same boat in the event of an update or backport to 1.3 in precises repos.

[Cody Garver (codygarver)]

I checked out the build recipe for our PPA and noticed it was only set to build for Precise, I have enabled and requested Quantal builds.

If you see this before I can see if/why the build fails, try this to see if it compiles for Quantal since I don't have a machine with that:

sudo apt-get -y build-dep maya; sudo apt-get -y install bzr; bzr branch lp:maya; cd maya; mkdir build; cd build; cmake .. -DCMAKE_INSTALL_PREFIX=/usr; sudo make install

[AJNpa80 (ajnelis1)]

heres my output, I think its those 2 libs versions

ajnpa80@HP-G60-Laptop:~$ sudo apt-get -y build-dep maya; sudo apt-get -y install bzr; bzr branch lp:maya ~/Projects/lp/maya ; cd ~/Projects/lp/maya; mkdir build; cd build; cmake .. -DCMAKE_INSTALL_PREFIX=/usr; sudo make install
[sudo] password for ajnpa80:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
bzr is already the newest version.
The following package was automatically installed and is no longer required:
  libx264-120
Use 'apt-get autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Branched 372 revisions.
-- The C compiler identification is GNU 4.7.2
-- The CXX compiler identification is GNU 4.7.2
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Found Gettext: /usr/bin/msgmerge (found version "0.18.1")
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.26")
-- checking for modules 'libecal-1.2>=3.2.0;gobject-2.0;glib-2.0;gio-2.0;gtk+-3.0;gthread-2.0;granite;libical;gee-1.0'
-- found libecal-1.2, version 3.6.0
-- found gobject-2.0, version 2.34.0
-- found glib-2.0, version 2.34.0
-- found gio-2.0, version 2.34.0
-- found gtk+-3.0, version 3.6.0
-- found gthread-2.0, version 2.34.0
-- found granite, version 0.1.1
-- found libical, version 0.48
-- found gee-1.0, version 0.6.4
-- Found Vala: /usr/bin/valac
-- checking for a minimum Vala version of 0.15.1
-- found Vala, version 0.16.1
-- GSettings schemas will be installed locally.
-- GSettings shemas will be compiled.
-- GSettings schemas will be installed into /usr/share/glib-2.0/schemas/
-- Configuring done
-- Generating done
-- Build files have been written to: /home/ajnpa80/Projects/lp/maya/build
[ 1%] Generating Maya/Application.c, Maya/Model/CalendarModel.c, Maya/Model/SourceManager.c, Maya/Services/Contractor.c, Maya/Services/Dexter.c, Maya/Settings/MayaSettings.c, Maya/Settings/SavedState.c, Maya/Settings/LanguagesFormat.c, Maya/Utils.c, Maya/View/Sidebar/AgendaView.c, Maya/View/Sidebar/Sidebar.c, Maya/View/Sidebar/SourceWidget.c, Maya/View/Sidebar/EventWidget.c, Maya/View/Grid/CalendarView.c, Maya/View/Grid/GridDay.c, Maya/View/Grid/Grid.c, Maya/View/Grid/EventButton/EventButton.c, Maya/View/Grid/EventButton/MultiDayEventButton.c, Maya/View/Grid/EventButton/SingleDayEventButton.c, Maya/View/Grid/WeekLabels.c, Maya/View/Grid/Header.c, Maya/View/Grid/VAutoHider.c, Maya/View/EventDialog.c, Maya/View/MayaMenu.c, Maya/View/MayaToolbar.c, Maya/View/SourceSelector.c, Maya/View/Widgets/ContractorButtonWithMenu.c, Maya/View/Widgets/DateSwitcher.c, Maya/View/Widgets/DateTimePicker.c, Maya/View/Widgets/Postl...

[AJNpa80 (ajnelis1)]

when i did it in comment 6 i had deleted my first try because i hadn't given bzr launchpad-login my launchpad id yet, thought i did, but bzr or cmake followed the move into trash, picked uip on it after posting so i redid it, thats why i posted output twice.

[AJNpa80 (ajnelis1)]

  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.

[Danielle Foré (danrabbit)]

removing this from the beta2 milestone since this is about Ubuntu, not elementary