On Sun, 22 Apr 2018 11:21:44 +0100 Peter Flynn <[email protected]> said:
> On 22/04/18 06:12, Carsten Haitzler (The Rasterman) wrote: > [...] > > 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. :) > Yep. I used to rely on it in the days when I recompiled from scratch for > each platform I used. > > But since Niko's .debs worked so well, I've been using them — until the > trouble with the most recent ones. But since you gave me the fix to > backtrack, I no longer need to compile anything, so I was just trying to > see if meson was as broken as it was when I last looked at it. > > > 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. > But nothing was installed the first time: the original command failed > for the reason given. Apt was doing its job correctly, just > badly-worded. The second time it worked perfectly. > > > 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. > No, absolutely not. I cannot understand why you still think this. > Everything is working fine. then explain the meson error you pasted. did meson install? can you install it? > > 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. > > No, it's fine. I simply typed an additional unnecessary package and apt > correctly refused to install it. > > > 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 was a result of my typing an additional unnecessary package name > the first time. The error message is bogus. Nothing was installed, > nothing was held. Apt merely thought there was because the command failed. it still doesn't change the fact that you have a meson package that is uninstallable for some reason related to the repo dataset you have. at least some of your dataset is broken. you can continue to pretend it's not even though you pasted the error yourself. i'm repeating myself. > > 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). > > No, there are no hold-backs, previous versions, or anything of the sort. then explain the error you yourself pasted. install meson. does it install? explain why dpkg itself says there are held packages? is it wrong? the dpkg maintainers would love to hear that bug report then... :) > > yes there is. see above. you yourself provided it. "unmet dependencies". > > No, that was just the result of my typing an additional unnecessary > package name. and that package is broken. it is not needed to run enlightenment, but if you ever need to compile it it will be needed. it doesn't change the fact that THAT package and/or its dependencies is broken within your repository dataset. that may imply more is broken. > > ninja-build WAS REQUESTED. > > Yes, wrongly. I should not have typed that name. > > > it was REQUESTED by the meson package. > > No, *I* requested it...wrongly. at no point am i saying that it is needed now for enlightenment to run. you keep thinking that because you made an error in trying to install meson when it was not needed that that changes the fact that meson is broken as i've indicated. i'm trying to help you by pointing out you have problems with your system there and this may lead to more issues in future. you seem to not want that help, even though your yourself saw the exact error and pasted it and now deny that any issues exist, so i may as well give up. > > I don't know what > > you've done, but a little bit of investigating like installing ninja-build > > But there is no package ninja-build in this distro. Just a package > ninja. I am assuming this package contained the functionality of > ninja-build, whatever that may be, because the ninja package satisfied > the requirements of meson. then THAT is the problem. meson depends on a non-existent package. i installed ubuntu in a vm a few weeks back to test efl stuff there and i installed meson and ninja-build because ninja-build *IS* ninja. the ninja pkg name was already taken in ubuntu at least for some other software that is not the ninja make/build tool. so i know at least on ubuntu ninja-build is the correct package dependency for meson. i am not sure about mint, but considering the closeness of their heritage i think that my assumption here would be right. if ninja-build is NOT available in mint then mint's packages are broken. they have a meson package depending on a ninja-build that they do not provide, thus the repo is broken. missing dependencies. this then would make me want to check out why and maybe report it or figure out why as it may be a signal of more problems. > > i'm trying to let you know you have a problem > > I appreciate that but I don't think that is the case. > > In any event it's moot. I am happy with the backtracking I did to > recover terminology, so I have no desire to recompile anything. > > I *will* need meson for a completely unrelated project I am > experimenting with, but that's a different question. and that is the ONLY thing i am talking about here. your meson package install failure. everything else you mention is not relevant. but i'm going to give up as you seem to think there is no problem at all, so up to you. > P > > ------------------------------------------------------------------------------ > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-users -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - [email protected] ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
