On Sat, 21 Apr 2018 22:09:35 +0100 Peter Flynn <pe...@silmaril.ie> said:
> On 21/04/18 06:37, Carsten Haitzler (The Rasterman) wrote: > > you didn't even have to install meson if it's already compiled > > binaries. meson is needed to compile terminology and enlightenment > > Right. I was installing meson because the web site said so. > > But it turned out (thanks to your help) that I don't need to compile > terminology and enlightenment because I was able to back-track over the > dud-package problem. well... that is the purpose of deb, rpm, etc. etc. - to provide already compiled ready-to-go software. our job is to provide the source code that gets compiled, so out instructions will be for that. :) the general instructions on our download page where the downloads are source at any rate. :) you need to keep this in mind and know the difference. it'll save you a lot of pain and agony. :) > > on the cmdline or not should make no difference. a package (meson) > > needs to be installed. ninja-build is a dependency of meson > > Right. But the web site said just "ninja" so I typed ninja. Not ninja-build. that doesn't matter. meson required ninja-build. you installed some unrelated ninja package that is going to consume some space but otherwise have no effect. the problem is meson + its dependencies in the package repos you use. that may mean mint is totally broken. it may mean repos you have added are broken as a result you end up with this. either way you have a broken package repo situation when it comes to meson. > > and it cannot install that/ something is seriously wrong with the > > package repository/ies you are using > No. I obviously haven't explained this clearly enough: > > 1. I read web site at https://www.enlightenment.org/docs/distros/start > > 2. It says I need basic tools: git. autoconf (2.59 or better), automake > (1.10 or better), autopoint, libtool, gettext, meson and ninja > > 3. I type (as in email of 18/04/18 20:58) > apt install git autoconf automake autopoint libtool gettext meson ninja > > 4. apt says The following packages have unmet dependencies: meson : > Depends: ninja-build (>= 1.6) but it is not going to be installed > > 5. Massimo said "there is no package named ninja, you should > remove it from the apt command line." > > 6. I type > apt install git autoconf automake autopoint libtool gettext meson > > 7. Works perfectly. It installs ninja-build as a dependency of meson. as above. ... the meson package in the distribution you use and/or its dependencies when taken as a whole in your distribution or your use of it including added or changed repository url's is broken. that package and/or its dependencies are broken. i am letting you know you are using a distro that has a problem and this essentially disallows you from building enlightenment unless you choose to start compiling meson and its dependencies yourself too. > Nothing is broken in any repo; just the instructions refer to ninja > instead of ninja-build (and it's not needed explicitly anyway because it > gets included as a dependency of meson). yes they are. you posted the error yourself: The following packages have unmet dependencies: meson : Depends: ninja-build (>= 1.6) but it is not going to be installed E: Unable to correct problems, you have held broken packages. that is an error for you. perhaps you have held back certain packages from updating that cause ninja-build not to update to a newer version etc. (as i said before that perhaps it's there but unable to install a new enough version). you have an issue there... *THIS* above. this meson + ninja-build issue is the thing i have been talking about. > > in that it is broken with a package (meson) that is uninstallable > > because a dependency of it is unable to be installed (doesn't exist > > or is too old a version as it wanted >= 1.6). your problem lies in > > your repositories and those packages. > > No. I don't understand why you think the repo is broken. There is no > evidence for this. yes there is. see above. you yourself provided it. "unmet dependencies". the repose are broken or your use of them is (added repose that altered available versions, but the simple thing that no ninja-build package of appropriate version can be found... that is a problem). > But apt needs much better error reporting, because it fails to identify > WHY the package could not be installed, and because it used the name of > a package which was not requested (ninja-build instead of ninja). But > perhaps it doesn't have that information. ninja-build WAS REQUESTED. it was REQUESTED by the meson package. it is a dependency of the meson package. dig in and find out. it clearly says there that the dependency "ninja-build of a version greater to or equal to 1.6 cannot be met". it then even says "you have held unbroken packages". i don't know what you've done, but a little bit of investigating like installing ninja-build or finding out what version it is or if it even exists would let you know a little more. then follow the breadcrumbs. if it's not available then there is a serious issue. if it is but the version is too old, then what is the version in the upstream repositories. if that's ok then you have something holding that package from being upgraded. you can hold packages in place to stop them from ever upgrading. perhaps you have packages that are help. but one way or another your "repos are broken". by that i mean the repository data set of packages that your packaging system can use is not consistent within itself. it's unable to install packages because links between them have been broken by something. i'm trying to let you know you have a problem and you should probably address it otherwise the problem is not likely going to go solve itself and it's going to probably lead to other problems in future. :) > ///Peter > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-users mailing list > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
