Re: [e-users] Terminology deleted by update

[Peter Flynn]

On 22/04/18 14:26, Carsten Haitzler (The Rasterman) wrote:
[...]

Everything is working fine.


then explain the meson error you pasted. 


I already have, about three times. It was because I typed the wrong 
package name.



id meson install? can you install it?


Yes, once I retyped the apt command it insatlled perfectly.


it still doesn't change the fact that you have a meson package that is
uninstallable


No, it's installed.


for some reason related to the repo dataset you have.


No, nothing to do with it.


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.


I think we'd better stop this; I'm wasting your time.


then explain the error you yourself pasted. install meson. does it install?


I have explained this already several times. Possibly not clearly.

explain why dpkg itself says there are held packages? is it wrong? 


It was only wrong for that command. I think it may be a very trivial bug 
in apt or dpkg.



and that package is broken. it is not needed to run enlightenment, but if you
ever need to compile it it will be needed. 


We shall see. I wanted to do this just to see if meson worked (given 
that I had terrible problems with it a few years ago on another project).


I had good success with compiling eft/enlightenment/terminology in a 
previous version that compiled perfectly on several platforms a couple 
of years ago; that used normal ./configure;make;make install so I am 
interested to see if meson offers anything better.


at no point am i saying that it is needed now for enlightenment to run. 


No, that was never a question.


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 appreciate your concern and help. I just think you have misunderstood 
the position, possibly through my poor explanations. I'm happy to be 
proved wrong, though.



then THAT is the problem. meson depends on a non-existent package.


IFF that is the problem, then it's a problem for the Mint packagers. I'm 
not seriously concerned because I'm only doing this out of interest, 
having had problems with meson some years ago.



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. 


Aha. NOW some new information. I was unaware of that. Perhaps the Mint 
packagers mistook one for the other. Strange that there is no report of 
it, especially as Mint uses meson for their own builds, apparently.



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.


Yes, that makes perfect sense. I did not have this extra information.


and that is the ONLY thing i am talking about here. your meson package install
failure. everything else you mention is not relevant.


I never raised anything except the meson/ninja problem. I think some 
others did contribute other information though.


Let's leave it rest until I am ready to experiment.

///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

Re: [e-users] Terminology deleted by update

[The Rasterman]

On Sun, 22 Apr 2018 11:21:44 +0100 Peter Flynn  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 

Re: [e-users] Terminology deleted by update

[Peter Flynn]

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.


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.



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.

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.


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.


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.



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.


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
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] Terminology deleted by update

[The Rasterman]

On Sat, 21 Apr 2018 22:09:35 +0100 Peter Flynn  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 

Re: [e-users] Terminology deleted by update

[Peter Flynn]

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.


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.


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.

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).


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.


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.


///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

Re: [e-users] Terminology deleted by update

[The Rasterman]

On Fri, 20 Apr 2018 21:51:04 +0100 Peter Flynn  said:

> On 20/04/18 07:00, Carsten Haitzler (The Rasterman) wrote:
> [...]
> > umm but:
> > 
> >   meson : Depends: ninja-build (>= 1.6) but it is not going to be installed
> > 
> > that says that there should be a ninja-build package. the meson package you
> > are installing depends on it... where is that meson package coming from?
> > from mint? or is it the extra repo (niko's) you added above?
> 
> No, that just has efl, enlightenment, and terminology. Maybe Mint's
> meson did call it ninja-build, it has long scrolled off the console.

well you asked to install meson on the cmdline (which is only needed for
compilation) and that meson pkg needs ninja-build. ninja is obviously some
different thing on debian based distros. ninja-build cannot be installed.

> The point was, I didn't have to mention it; installing meson included it
> automatically as a dependency, whereas mentioning it explicitly caused
> an error, which I though was weird.

you didn't even have to install meson if it's already compiled binaries. meson
is needed to compile terminology and enlightenment these days (in git master).
terminology has required meson now in releases too.

> > well niko's repo is that.. a non-distro repo custom filled with specific
> > pkgs that dont come from the distro. :)
> 
> Yes, that's why I mentioned it.
> 
> > well either way the output you had above with meson and ninja-build errors
> > says that some meson package somewhere apt is trying to install requires
> > ninja-build and its having trouble getting ninja-build installed.
> 
> No, exactly the opposite. Installing meson automatically included ninja
> (-build or not, I can't remember now) as a dependency. It only gave an
> error if I tried to include the package name on the command line.

on the cmdline or not should make no difference. a package (meson) needs to be
installed. ninja-build is a dependency of meson and it cannot install that/
something is serioously wrong with the package repository/ies you are using 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. they seem to be broken somehow and you'd need to investigate exactly
why and report to the package maintainers.

> ///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

Re: [e-users] Terminology deleted by update

[Peter Flynn]

On 20/04/18 07:00, Carsten Haitzler (The Rasterman) wrote:
[...]
> umm but:
> 
>   meson : Depends: ninja-build (>= 1.6) but it is not going to be installed
> 
> that says that there should be a ninja-build package. the meson package you 
> are
> installing depends on it... where is that meson package coming from? from 
> mint?
> or is it the extra repo (niko's) you added above?

No, that just has efl, enlightenment, and terminology. Maybe Mint's
meson did call it ninja-build, it has long scrolled off the console.
The point was, I didn't have to mention it; installing meson included it
automatically as a dependency, whereas mentioning it explicitly caused
an error, which I though was weird.

> well niko's repo is that.. a non-distro repo custom filled with specific pkgs
> that dont come from the distro. :)

Yes, that's why I mentioned it.

> well either way the output you had above with meson and ninja-build errors 
> says
> that some meson package somewhere apt is trying to install requires
> ninja-build and its having trouble getting ninja-build installed.

No, exactly the opposite. Installing meson automatically included ninja
(-build or not, I can't remember now) as a dependency. It only gave an
error if I tried to include the package name on the command line.

///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

Re: [e-users] Terminology deleted by update

[The Rasterman]

On Thu, 19 Apr 2018 03:07:41 + Stephen Houston  said:

> Also, the comment that was made about Ubuntu and Fedora not updating meson
> (or any other apps as was stated) is very misleading. Both Fedora and
> Ubuntu stay well up to date and keep their packages very up to date.  The
> meson version included in both distros stable repos work just fine to build
> e, efl, and e apps using meson. No need to force the rolling release point
> of view there. Yes debian is usually way behind, and yes way behind ubuntu
> and fedora too, so not surprised there.

if you install ubuntu 16.04 then 16.04 will not update meson. if you do
apt-get update/upgrades it won't. it'll get bugfixes and security fixes. you
need to actually go alter your package repo url's to upgrade. that is what i
mean. you can upgrade to 17.04, then 18.04 etc.. but it requires explicitly
changing repositories to upgrade, unlike a rolling distro where you don't change
your repos and doing an update+upgrade just upgrades everything that has been
updated in the repo since you last did this.

> On Wed, Apr 18, 2018, 9:52 PM Dave  wrote:
> 
> >  In the year 2018, of the month of April, on the 19th day, Carsten
> > Haitzler wrote:
> > > >
> > > > Is Meson that neglected in some places? I had sort of assumed it would
> > > > be under heavy support as it's become so popular.
> > >
> > > no - it's that meson has been changing a lot of late i'd say as it gets
> > more
> > > adoption and more projects find bugs and shortcomings in it and meson
> > adds
> > > features to match thus needing a very up to date version. if you use
> > debian
> > > (stable), ubuntu, fedora etc. you will not find them UPGRADING meson or
> > really
> > > any package. only providing bugfix/security fix packages (a new revision
> > of the
> > > same version of the older pkg with the security or bug fix). they
> > probably
> > > focus most on security fixes and only the big bug fixes may get a fix.
> > if the
> > > fix is to upgrade the pkg they probably wont do it.
> > >
> > > that's why a rolling release distro (arch, gentoo, suse tumbleweed,
> > debian
> > > SID/testing etc.) will stay up to date as it's always ipdating and
> > upgrading
> > > all packages based on when upsterams release them.
> >
> >  Just a note that Debian also has a "backports" repo, which contains some
> > updated binaries for the stable release.  Meson is one such package.  The
> > backported version is a little behind testing/unstable, but is still much
> > more recent than stable.
> >
> >  https://packages.debian.org/stretch-backports/meson
> >
> >  I use testing (buster) myself, and it compiles terminology 1.2 fine.
> >
> >  Cheers,
> >  dave.k
> >
> >
> >
> > --
> > 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
> >
> --
> 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

Re: [e-users] Terminology deleted by update

[The Rasterman]

On Thu, 19 Apr 2018 22:45:55 +0100 Peter Flynn  said:

> On 19/04/18 03:37, Carsten Haitzler (The Rasterman) wrote:
> [...]
> > anyone can get write access. sign up an account there. it's a wiki.
> 
> I'm not a developer, just an end user, so I don't think I would be in
> any remote way qualified to add anything myself.

if you find packages  update or change names - a user can modify those things.
developers are not people who compile things. they are people who work on the
code itself. users may or may not compile things. in the process of compiling
you will maybe figure out dependencies change.

> > but please note that that page is GENERIC. it doesn't cover any special
> > distro.
> 
> My error: I assumed that most distros would use the same names.

absolutely not. there's 1000+ linux distros. there's the bsd's too ... and not
to mention windows and osx where there are also various ways of getting
dependencies. :)

> > we cant have one generic page magically just work on every distro.
> 
> No indeed, not as things stand. One page each for the distros I test
> might be achievable.
> 
> > if you looked top-right there is a list of distro specific install pages
> > with more specialist instructions per distro. again - a wiki. can be
> > updated by users of that distro as it changes over time.
> 
> Right. I missed that completely

that'll be the "per distro" pages. and that is really where users come in -
when the compile and test and when distros add, remove or rename packages you
can't expect developers to keep every distro around in some vm or chroot and
keep up with all of them in addition to working on the code. :)

> > did you try install ninja-build on its own and see what version it was?
> 
> No, I just omitted it from the list, and it got included as a dependency
> on meson, so it all installed. Haven't had time to do anything with it
> yet though.
> 
> > perhaps its too old? did you customize the pkg repo urls 
> 
> No, everything is stock. The only addition was Niko's repo for E and
> Terminology, now removed.
> 
> > perhaps mint is just broken if it can't install
> > its own pkgs dependencies if everything you have is stock... 
> 
> No, just the naming. Mint has no such animal as ninja-build, apparently,
> just plain ninja, and it gets installed along with meson.

umm but:

  meson : Depends: ninja-build (>= 1.6) but it is not going to be installed

that says that there should be a ninja-build package. the meson package you are
installing depends on it... where is that meson package coming from? from mint?
or is it the extra repo (niko's) you added above?

> > but that'd be a
> > pretty horrible break there, so my suspects are custom pkg repos of your own
> > breaking up dependencies somehow...
> 
> It would be pretty bad, but I don't do custom pkg repos, fortunately.

well niko's repo is that.. a non-distro repo custom filled with specific pkgs
that dont come from the distro. :)

> If what I need can't be provided from stock, I switch Linux distro to
> one that can (why I ditched Xubuntu for Mint). Like I said: I'm an end
> user — I don't have the freedom to experiment at the moment; the best I
> can do right now is to donate to the support of a distro. When I retire
> things will be different, I hope — time to experiment and contribute :-)

well either way the output you had above with meson and ninja-build errors says
that some meson package somewhere apt is trying to install requires
ninja-build and its having trouble getting ninja-build installed. too old a
version or doesn't exist. so either that meson package is broken in that
environment with the ninja-build pkgs available :)

> ///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

Re: [e-users] Terminology deleted by update

[Peter Flynn]

On 19/04/18 10:40, maderios wrote:
> On 04/18/2018 09:32 PM, Peter Flynn wrote:
>> Sounds good. I've avoided Arch because last time I tried it, it broke
>> Emacs, and was several versions behind on a few key (for me) packages.
>> But if that's changed I should look at it again.
>>
> Hi
> 'Last time' you used Arch.  When, how many years ago? I use Arch and
> Emacs every day, it works fine. 

This was a specific instance: trying to install Linux on a Dell XPS-15,
and everything except Mint screwed up what I now believe to be the
hardware recognition, resulting in Emacs violently complaining about
blink-cursor-start and mouse-button-5 clicks even though my fingers were
off the machine. blogs.silmaril.ie passim if you're feeling bored.

///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

Re: [e-users] Terminology deleted by update

[Peter Flynn]

On 19/04/18 03:37, Carsten Haitzler (The Rasterman) wrote:
[...]
> anyone can get write access. sign up an account there. it's a wiki.

I'm not a developer, just an end user, so I don't think I would be in
any remote way qualified to add anything myself.

> but please note that that page is GENERIC. it doesn't cover any special 
> distro.

My error: I assumed that most distros would use the same names.

> we cant have one generic page magically just work on every distro.

No indeed, not as things stand. One page each for the distros I test
might be achievable.

> if you looked top-right there is a list of distro specific install pages with
> more specialist instructions per distro. again - a wiki. can be updated by
> users of that distro as it changes over time.

Right. I missed that completely

> did you try install ninja-build on its own and see what version it was?

No, I just omitted it from the list, and it got included as a dependency
on meson, so it all installed. Haven't had time to do anything with it
yet though.

> perhaps its too old? did you customize the pkg repo urls 

No, everything is stock. The only addition was Niko's repo for E and
Terminology, now removed.

> perhaps mint is just broken if it can't install
> its own pkgs dependencies if everything you have is stock... 

No, just the naming. Mint has no such animal as ninja-build, apparently,
just plain ninja, and it gets installed along with meson.

> but that'd be a
> pretty horrible break there, so my suspects are custom pkg repos of your own
> breaking up dependencies somehow...

It would be pretty bad, but I don't do custom pkg repos, fortunately.
If what I need can't be provided from stock, I switch Linux distro to
one that can (why I ditched Xubuntu for Mint). Like I said: I'm an end
user — I don't have the freedom to experiment at the moment; the best I
can do right now is to donate to the support of a distro. When I retire
things will be different, I hope — time to experiment and contribute :-)

///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

Re: [e-users] Terminology deleted by update

[maderios]

On 04/18/2018 09:32 PM, Peter Flynn wrote:

at last arch has been smooth sailing on this, but it's a rolling
distro so it stays relatively up to date :)

Sounds good. I've avoided Arch because last time I tried it, it broke
Emacs, and was several versions behind on a few key (for me) packages.
But if that's changed I should look at it again.


Hi
'Last time' you used Arch.  When, how many years ago? I use Arch and 
Emacs every day, it works fine. On the safe side, I installed lts arch 
kernel.

To install easily fresh E (Thanks Carsten :)
https://aur.archlinux.org/packages/efl-git/
https://aur.archlinux.org/packages/enlightenment-git/
https://aur.archlinux.org/packages/terminology-git/
--
Maderios

--
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

Re: [e-users] Terminology deleted by update

[Stephen Houston]

Also, the comment that was made about Ubuntu and Fedora not updating meson
(or any other apps as was stated) is very misleading. Both Fedora and
Ubuntu stay well up to date and keep their packages very up to date.  The
meson version included in both distros stable repos work just fine to build
e, efl, and e apps using meson. No need to force the rolling release point
of view there. Yes debian is usually way behind, and yes way behind ubuntu
and fedora too, so not surprised there.

On Wed, Apr 18, 2018, 9:52 PM Dave  wrote:

>  In the year 2018, of the month of April, on the 19th day, Carsten
> Haitzler wrote:
> > >
> > > Is Meson that neglected in some places? I had sort of assumed it would
> > > be under heavy support as it's become so popular.
> >
> > no - it's that meson has been changing a lot of late i'd say as it gets
> more
> > adoption and more projects find bugs and shortcomings in it and meson
> adds
> > features to match thus needing a very up to date version. if you use
> debian
> > (stable), ubuntu, fedora etc. you will not find them UPGRADING meson or
> really
> > any package. only providing bugfix/security fix packages (a new revision
> of the
> > same version of the older pkg with the security or bug fix). they
> probably
> > focus most on security fixes and only the big bug fixes may get a fix.
> if the
> > fix is to upgrade the pkg they probably wont do it.
> >
> > that's why a rolling release distro (arch, gentoo, suse tumbleweed,
> debian
> > SID/testing etc.) will stay up to date as it's always ipdating and
> upgrading
> > all packages based on when upsterams release them.
>
>  Just a note that Debian also has a "backports" repo, which contains some
> updated binaries for the stable release.  Meson is one such package.  The
> backported version is a little behind testing/unstable, but is still much
> more recent than stable.
>
>  https://packages.debian.org/stretch-backports/meson
>
>  I use testing (buster) myself, and it compiles terminology 1.2 fine.
>
>  Cheers,
>  dave.k
>
>
>
> --
> 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
>
--
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

Re: [e-users] Terminology deleted by update

[Dave]

 In the year 2018, of the month of April, on the 19th day, Carsten Haitzler 
wrote:
> > 
> > Is Meson that neglected in some places? I had sort of assumed it would
> > be under heavy support as it's become so popular.
> 
> no - it's that meson has been changing a lot of late i'd say as it gets more
> adoption and more projects find bugs and shortcomings in it and meson adds
> features to match thus needing a very up to date version. if you use debian
> (stable), ubuntu, fedora etc. you will not find them UPGRADING meson or really
> any package. only providing bugfix/security fix packages (a new revision of 
> the
> same version of the older pkg with the security or bug fix). they probably
> focus most on security fixes and only the big bug fixes may get a fix. if the
> fix is to upgrade the pkg they probably wont do it.
> 
> that's why a rolling release distro (arch, gentoo, suse tumbleweed, debian
> SID/testing etc.) will stay up to date as it's always ipdating and upgrading
> all packages based on when upsterams release them.

 Just a note that Debian also has a "backports" repo, which contains some
updated binaries for the stable release.  Meson is one such package.  The
backported version is a little behind testing/unstable, but is still much
more recent than stable.

 https://packages.debian.org/stretch-backports/meson

 I use testing (buster) myself, and it compiles terminology 1.2 fine.

 Cheers,
 dave.k


--
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

Re: [e-users] Terminology deleted by update

[The Rasterman]

On Wed, 18 Apr 2018 20:32:49 +0100 Peter Flynn  said:

> On 18/04/18 09:56, Carsten Haitzler (The Rasterman) wrote:
> > On Wed, 18 Apr 2018 09:11:33 +0100 Peter Flynn  said:
> >> I know meson is terribly fashionable these days, but I have tried
> >> to get it to work on at least five Linux distros and it's never
> >> worked properly -- always been missing some unfindable component.
> > 
> > ummm maybe its just the distros you tried that don't stay up to date
> > that easily?
> 
> Is Meson that neglected in some places? I had sort of assumed it would
> be under heavy support as it's become so popular.

no - it's that meson has been changing a lot of late i'd say as it gets more
adoption and more projects find bugs and shortcomings in it and meson adds
features to match thus needing a very up to date version. if you use debian
(stable), ubuntu, fedora etc. you will not find them UPGRADING meson or really
any package. only providing bugfix/security fix packages (a new revision of the
same version of the older pkg with the security or bug fix). they probably
focus most on security fixes and only the big bug fixes may get a fix. if the
fix is to upgrade the pkg they probably wont do it.

that's why a rolling release distro (arch, gentoo, suse tumbleweed, debian
SID/testing etc.) will stay up to date as it's always ipdating and upgrading
all packages based on when upsterams release them.

> So far I have tried Ubuntu, RedHat, CentOS, Bodhi, and raw Debian. All

all non-rolling and if they are older versions... not great. :(

> failed because some specific library was not available in the version
> required (different library for each distro), or because build
> instructions for the project I was working on expected an environment
> that didn't exist (presumably the original developer's environment).

i've build efl and e on a range of distros and also on fbsd too and
cross-compiled for windows as well over the years and i invariably can get it
to build by hunting down the dependency. i rarely have much trouble other than
just figuring out what the local distros package name is for that thing. i will
also try and use their absolute latest release each time.

> > at last arch has been smooth sailing on this, but it's a rolling
> > distro so it stays relatively up to date :)
> Sounds good. I've avoided Arch because last time I tried it, it broke
> Emacs, and was several versions behind on a few key (for me) packages.
> But if that's changed I should look at it again.
> 
> Thanks for the tips.
> 
> ///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

Re: [e-users] Terminology deleted by update

[The Rasterman]

On Wed, 18 Apr 2018 20:58:30 +0100 Peter Flynn  said:

> On 18/04/18 20:32, Peter Flynn wrote:
> > On 18/04/18 09:56, Carsten Haitzler (The Rasterman) wrote:
> >> On Wed, 18 Apr 2018 09:11:33 +0100 Peter Flynn  said:
> >>> I know meson is terribly fashionable these days, but I have tried
> >>> to get it to work on at least five Linux distros and it's never
> >>> worked properly -- always been missing some unfindable component.
> >>
> >> ummm maybe its just the distros you tried that don't stay up to date
> >> that easily?
> > 
> > Is Meson that neglected in some places? I had sort of assumed it would
> > be under heavy support as it's become so popular.
> > 
> > So far I have tried Ubuntu, RedHat, CentOS, Bodhi, and raw Debian. 
> 
> Just tried Mint:
> 
> > pentacle ~ # apt install git autoconf automake autopoint libtool gettext
> > meson ninja Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > autoconf is already the newest version (2.69-9).
> > automake is already the newest version (1:1.15-4ubuntu1).
> > autopoint is already the newest version (0.19.7-2ubuntu3).
> > gettext is already the newest version (0.19.7-2ubuntu3).
> > libtool is already the newest version (2.4.6-0.1).
> > git is already the newest version (1:2.7.4-0ubuntu1.3).
> > Some packages could not be installed. This may mean that you have
> > requested an impossible situation or if you are using the unstable
> > distribution that some required packages have not yet been created
> > or been moved out of Incoming.
> > The following information may help to resolve the situation:
> > 
> > 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.
> > pentacle ~ # 
> 
> Unfortunately, apt doesn't say *why* it won't install ninja-build, so I
> have no way of knowing how the problem can be fixed.

did you try install ninja-build on its own and see what version it was?
perhaps its too old? did you customize the pkg repo urls to have extra ones
there that are not standard? perhaps mint is just broken if it can't install
its own pkgs dependencies if everything you have is stock... but that'd be a
pretty horrible break there, so my suspects are custom pkg repos of your own
breaking up dependencies somehow...

> ///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

Re: [e-users] Terminology deleted by update

[The Rasterman]

On Wed, 18 Apr 2018 21:47:01 +0100 Peter Flynn  said:

> On 18/04/18 21:19, Massimo Maiurana wrote:
> [...]
> > On debian buster (testing) there is no package named ninja, you should
> > remove it from the apt command line. Meson should carry out ninja-build
> > automatically as it's one of its dependencies.
> 
> Interesting, so it does.
> 
> Perhaps someone with write-access to
> https://www.enlightenment.org/docs/distros/start could note "meson
> (includes ninja)" instead of "meson and ninja".

anyone can get write access. sign up an account there. it's a wiki.

but please note that that page is GENERIC. it doesnt cover any special distro.
it's a list of dependencies, not PACKAGE NAMES. it's youer job to figure out
what the pkg name is on your distro. every distro is difference. on arch ninja
is "ninja" and on debian distros it seems to be "ninja-build". they are just
names for you to then go research on what package provides those. you will on
debian and rh distros have to install the libxxx-dev or libxxx-devel pkgs too
for headers. again - your job to figure out. we cant have one generic page
magically just work on every distro.

if you looked top-right there is a list of distro specific install pages with
more specialist instructions per distro. again - a wiki. can be updated by
users of that distro as it changes over time.

> However, attempting to install the dependencies mentioned lower down
> that page hits a snag:
> 
> # apt install gcc make check libpam freetype libpng libjpeg zlib libdbus
> luajit libx11 libxcursor libxrender libxrandr libxfixes libxdamage
> libxcomposite libxss libxp libxext libxinerama libxkbfile libxtst libxcb
> libxcb-shape libxcb-keysyms1 libpulse libsndfile libudev libblkid
> libmount libgstreamer vlc libtiff giflib curl openssl opengl libspectre
> poppler librsvg libraw libxine bullet
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Unable to locate package libpam
> E: Unable to locate package freetype
> E: Unable to locate package libpng
> E: Unable to locate package libjpeg
> E: Unable to locate package zlib
> E: Unable to locate package libdbus
> E: Unable to locate package libx11
> E: Unable to locate package libxcursor
> E: Unable to locate package libxrender
> E: Unable to locate package libxrandr
> E: Unable to locate package libxfixes
> E: Unable to locate package libxdamage
> E: Unable to locate package libxcomposite
> E: Unable to locate package libxss
> E: Unable to locate package libxp
> E: Unable to locate package libxext
> E: Unable to locate package libxinerama
> E: Unable to locate package libxkbfile
> E: Unable to locate package libxtst
> E: Unable to locate package libxcb
> E: Unable to locate package libxcb-shape
> E: Unable to locate package libpulse
> E: Unable to locate package libsndfile
> E: Unable to locate package libudev
> E: Unable to locate package libblkid
> E: Unable to locate package libmount
> E: Unable to locate package libgstreamer
> E: Unable to locate package libtiff
> E: Unable to locate package giflib
> E: Unable to locate package opengl
> E: Unable to locate package libspectre
> E: Unable to locate package poppler
> E: Unable to locate package librsvg
> E: Unable to locate package libraw
> E: Unable to locate package libxine
> E: Unable to locate package bullet
> #
> 
> This is Mint...something wrong somewhere.
> 
> ///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

Re: [e-users] Terminology deleted by update

[The Rasterman]

On Wed, 18 Apr 2018 17:45:19 -0400 mh  said:

> 
> On 4/18/18 4:56 AM, Carsten Haitzler (The Rasterman) wrote:
> > On Wed, 18 Apr 2018 09:11:33 +0100 Peter Flynn  said:
> >
> >> Yes, it looks like a build fail.
> >>
> >> Thanks, Carsten, for suggesting dpkg --purge. I had used apt --purge 
> >> but it
> >> seems that doesn't actually purge everything.
> >>
> >> Then reinstalling it worked (with a waning) so now it's back and on hold.
> >>
> >> I know meson is terrribly fashionable these days, but I have tried to get
> >> it to work on at least five Linux distros and it's never worked 
> >> properly --
> >> always been missing some unfindable component.
> > ummm maybe its just the distros you tried that don't stay up to date that
> > easily? at last arch has been smooth sailing on this, but it's a 
> > rolling distro
> > so it stays relatively up to date :)
> 
> 
> I'm running Debian sid and have no problems building with meson. just 

sid is rolling so that should make it good in terms of being up to date

> recompiled new two days ago. unstable and testing are using meson 
> version 0.45.1-2 right now, stable is at 0.37.1-1 . Arch is at version 
> 0.45.1-1 ;)
> 
> 
> >
> >> ///Peter
> >>
> >> On 18 April 2018 03:27:53 Dave  wrote:
> >>
> >> Weird. I've downloaded and unpacked that deb file. It just contains the
> >> /usr/share/doc/terminology data. No binaries. I'm guessing whoever 
> >> created
> >> it has an automated system for building packages, and it's failing on 
> >> binary
> >> compilation.
> >>
> >> Your old deb files are located in /var/cache/apt/archives . You can 
> >> install
> >> the previous terminology version from there via dpkg, or download the old
> >> version from the repository. Then you can put the package on "hold" by
> >> running "echo terminology hold | dpkg --set-selections". That'll 
> >> prevent it
> >> from being automatically upgraded.
> >>
> >> Otherwise, you could always compile the latest terminology yourself. It's
> >> not too hard. Though there is an annoying focus bug present in the latest
> >> version, which you may want to avoid until a point release is done.
> >>
> >> Cheers,
> >> dave.k
> >>
> >>
> >> In the year 2018, of the month of April, on the 17th day, Peter Flynn 
> >> wrote:
> >> Sorry, this failed to send earlier.
> >>
> >> On 17/04/18 12:12, Peter Flynn wrote:
> >> [...]> 1 not fully installed or removed.
> >> After this operation, 0 B of additional disk space will be used.
> >> E: Internal Error, No file name for terminology:amd64
> >>
> >> Does anyone know where I can get it in a .deb form that won't vanish
> >> at an update
> >>
> >> I did some digging into
> >> http://ppa.launchpad.net/niko2040/e19/ubuntu/pool/main/t/terminology/
> >> and found that the two most recent .debs are only 11Kb, which must
> >> surely be an error.
> >>
> >> terminology_1.2.0-0artful0_amd64.deb 2018-04-15 19:20 5.7M
> >> terminology_1.2.0-0bionic0_amd64.deb 2018-04-15 19:52 5.7M
> >> terminology_1.2.0-0trusty4_amd64.deb 2018-04-15 20:06 11K
> >> terminology_1.2.0-0xenial3_amd64.deb 2018-04-15 20:06 11K
> >>
> >> I've sent Niko an email via launchpad, but does anyone else have a 
> >> solution?
> >>
> >> 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
> >> enlightenment-users@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
> >>
> >> --
> >> 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
> >>
> >>
> >>
> >>
> >> --
> >> 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
> >>
> >
> 
> --
> 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
> 


-- 

Re: [e-users] Terminology deleted by update

[mh]

On 4/18/18 4:56 AM, Carsten Haitzler (The Rasterman) wrote:

On Wed, 18 Apr 2018 09:11:33 +0100 Peter Flynn  said:


Yes, it looks like a build fail.

Thanks, Carsten, for suggesting dpkg --purge. I had used apt --purge 
but it

seems that doesn't actually purge everything.

Then reinstalling it worked (with a waning) so now it's back and on hold.

I know meson is terrribly fashionable these days, but I have tried to get
it to work on at least five Linux distros and it's never worked 
properly --

always been missing some unfindable component.

ummm maybe its just the distros you tried that don't stay up to date that
easily? at last arch has been smooth sailing on this, but it's a 
rolling distro

so it stays relatively up to date :)



I'm running Debian sid and have no problems building with meson. just 
recompiled new two days ago. unstable and testing are using meson 
version 0.45.1-2 right now, stable is at 0.37.1-1 . Arch is at version 
0.45.1-1 ;)






///Peter

On 18 April 2018 03:27:53 Dave  wrote:

Weird. I've downloaded and unpacked that deb file. It just contains the
/usr/share/doc/terminology data. No binaries. I'm guessing whoever 
created
it has an automated system for building packages, and it's failing on 
binary

compilation.

Your old deb files are located in /var/cache/apt/archives . You can 
install

the previous terminology version from there via dpkg, or download the old
version from the repository. Then you can put the package on "hold" by
running "echo terminology hold | dpkg --set-selections". That'll 
prevent it

from being automatically upgraded.

Otherwise, you could always compile the latest terminology yourself. It's
not too hard. Though there is an annoying focus bug present in the latest
version, which you may want to avoid until a point release is done.

Cheers,
dave.k


In the year 2018, of the month of April, on the 17th day, Peter Flynn 
wrote:

Sorry, this failed to send earlier.

On 17/04/18 12:12, Peter Flynn wrote:
[...]> 1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for terminology:amd64

Does anyone know where I can get it in a .deb form that won't vanish
at an update

I did some digging into
http://ppa.launchpad.net/niko2040/e19/ubuntu/pool/main/t/terminology/
and found that the two most recent .debs are only 11Kb, which must
surely be an error.

terminology_1.2.0-0artful0_amd64.deb 2018-04-15 19:20 5.7M
terminology_1.2.0-0bionic0_amd64.deb 2018-04-15 19:52 5.7M
terminology_1.2.0-0trusty4_amd64.deb 2018-04-15 20:06 11K
terminology_1.2.0-0xenial3_amd64.deb 2018-04-15 20:06 11K

I've sent Niko an email via launchpad, but does anyone else have a 
solution?


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
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

--
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




--
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





--
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

Re: [e-users] Terminology deleted by update

[Massimo Maiurana]

Peter Flynn ha scritto il 18/04/2018 alle 22:47:
> On 18/04/18 21:19, Massimo Maiurana wrote:
> [...]
>> On debian buster (testing) there is no package named ninja, you should
>> remove it from the apt command line. Meson should carry out ninja-build
>> automatically as it's one of its dependencies.
> 
> Interesting, so it does.
> 
> Perhaps someone with write-access to
> https://www.enlightenment.org/docs/distros/start could note "meson
> (includes ninja)" instead of "meson and ninja".
> 
> However, attempting to install the dependencies mentioned lower down
> that page hits a snag:
> 
> # apt install gcc make check libpam freetype libpng libjpeg zlib libdbus
> luajit libx11 libxcursor libxrender libxrandr libxfixes libxdamage
> libxcomposite libxss libxp libxext libxinerama libxkbfile libxtst libxcb
> libxcb-shape libxcb-keysyms1 libpulse libsndfile libudev libblkid
> libmount libgstreamer vlc libtiff giflib curl openssl opengl libspectre
> poppler librsvg libraw libxine bullet
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Unable to locate package libpam
> E: Unable to locate package freetype
> E: Unable to locate package libpng
> E: Unable to locate package libjpeg
> E: Unable to locate package zlib
> E: Unable to locate package libdbus
> E: Unable to locate package libx11
> E: Unable to locate package libxcursor
> E: Unable to locate package libxrender
> E: Unable to locate package libxrandr
> E: Unable to locate package libxfixes
> E: Unable to locate package libxdamage
> E: Unable to locate package libxcomposite
> E: Unable to locate package libxss
> E: Unable to locate package libxp
> E: Unable to locate package libxext
> E: Unable to locate package libxinerama
> E: Unable to locate package libxkbfile
> E: Unable to locate package libxtst
> E: Unable to locate package libxcb
> E: Unable to locate package libxcb-shape
> E: Unable to locate package libpulse
> E: Unable to locate package libsndfile
> E: Unable to locate package libudev
> E: Unable to locate package libblkid
> E: Unable to locate package libmount
> E: Unable to locate package libgstreamer
> E: Unable to locate package libtiff
> E: Unable to locate package giflib
> E: Unable to locate package opengl
> E: Unable to locate package libspectre
> E: Unable to locate package poppler
> E: Unable to locate package librsvg
> E: Unable to locate package libraw
> E: Unable to locate package libxine
> E: Unable to locate package bullet
> #
> 
> This is Mint...something wrong somewhere.

Consider that package names are different from one distro to another.
E.g. on buster there is no freetype but instead libfreetype6, libxrandr
is actually libxrandr2 and so on.

-- 
Massimo Maiurana
Ragusa (RG)

--
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

Re: [e-users] Terminology deleted by update

[Peter Flynn]

On 18/04/18 21:19, Massimo Maiurana wrote:
[...]
> On debian buster (testing) there is no package named ninja, you should
> remove it from the apt command line. Meson should carry out ninja-build
> automatically as it's one of its dependencies.

Interesting, so it does.

Perhaps someone with write-access to
https://www.enlightenment.org/docs/distros/start could note "meson
(includes ninja)" instead of "meson and ninja".

However, attempting to install the dependencies mentioned lower down
that page hits a snag:

# apt install gcc make check libpam freetype libpng libjpeg zlib libdbus
luajit libx11 libxcursor libxrender libxrandr libxfixes libxdamage
libxcomposite libxss libxp libxext libxinerama libxkbfile libxtst libxcb
libxcb-shape libxcb-keysyms1 libpulse libsndfile libudev libblkid
libmount libgstreamer vlc libtiff giflib curl openssl opengl libspectre
poppler librsvg libraw libxine bullet
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libpam
E: Unable to locate package freetype
E: Unable to locate package libpng
E: Unable to locate package libjpeg
E: Unable to locate package zlib
E: Unable to locate package libdbus
E: Unable to locate package libx11
E: Unable to locate package libxcursor
E: Unable to locate package libxrender
E: Unable to locate package libxrandr
E: Unable to locate package libxfixes
E: Unable to locate package libxdamage
E: Unable to locate package libxcomposite
E: Unable to locate package libxss
E: Unable to locate package libxp
E: Unable to locate package libxext
E: Unable to locate package libxinerama
E: Unable to locate package libxkbfile
E: Unable to locate package libxtst
E: Unable to locate package libxcb
E: Unable to locate package libxcb-shape
E: Unable to locate package libpulse
E: Unable to locate package libsndfile
E: Unable to locate package libudev
E: Unable to locate package libblkid
E: Unable to locate package libmount
E: Unable to locate package libgstreamer
E: Unable to locate package libtiff
E: Unable to locate package giflib
E: Unable to locate package opengl
E: Unable to locate package libspectre
E: Unable to locate package poppler
E: Unable to locate package librsvg
E: Unable to locate package libraw
E: Unable to locate package libxine
E: Unable to locate package bullet
#

This is Mint...something wrong somewhere.

///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

Re: [e-users] Terminology deleted by update

[Massimo Maiurana]

Peter Flynn ha scritto il 18/04/2018 alle 21:58:
> On 18/04/18 20:32, Peter Flynn wrote:
>> On 18/04/18 09:56, Carsten Haitzler (The Rasterman) wrote:
>>> On Wed, 18 Apr 2018 09:11:33 +0100 Peter Flynn  said:
 I know meson is terribly fashionable these days, but I have tried
 to get it to work on at least five Linux distros and it's never
 worked properly -- always been missing some unfindable component.
>>>
>>> ummm maybe its just the distros you tried that don't stay up to date
>>> that easily?
>>
>> Is Meson that neglected in some places? I had sort of assumed it would
>> be under heavy support as it's become so popular.
>>
>> So far I have tried Ubuntu, RedHat, CentOS, Bodhi, and raw Debian. 
> 
> Just tried Mint:
> 
>> pentacle ~ # apt install git autoconf automake autopoint libtool gettext 
>> meson ninja

On debian buster (testing) there is no package named ninja, you should
remove it from the apt command line. Meson should carry out ninja-build
automatically as it's one of its dependencies.

>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> autoconf is already the newest version (2.69-9).
>> automake is already the newest version (1:1.15-4ubuntu1).
>> autopoint is already the newest version (0.19.7-2ubuntu3).
>> gettext is already the newest version (0.19.7-2ubuntu3).
>> libtool is already the newest version (2.4.6-0.1).
>> git is already the newest version (1:2.7.4-0ubuntu1.3).
>> Some packages could not be installed. This may mean that you have
>> requested an impossible situation or if you are using the unstable
>> distribution that some required packages have not yet been created
>> or been moved out of Incoming.
>> The following information may help to resolve the situation:
>>
>> 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.
>> pentacle ~ # 
> 
> Unfortunately, apt doesn't say *why* it won't install ninja-build, so I
> have no way of knowing how the problem can be fixed.
> 
> ///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
> 


-- 
Massimo Maiurana
Ragusa (RG)

--
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

Re: [e-users] Terminology deleted by update

[Peter Flynn]

On 18/04/18 20:32, Peter Flynn wrote:
> On 18/04/18 09:56, Carsten Haitzler (The Rasterman) wrote:
>> On Wed, 18 Apr 2018 09:11:33 +0100 Peter Flynn  said:
>>> I know meson is terribly fashionable these days, but I have tried
>>> to get it to work on at least five Linux distros and it's never
>>> worked properly -- always been missing some unfindable component.
>>
>> ummm maybe its just the distros you tried that don't stay up to date
>> that easily?
> 
> Is Meson that neglected in some places? I had sort of assumed it would
> be under heavy support as it's become so popular.
> 
> So far I have tried Ubuntu, RedHat, CentOS, Bodhi, and raw Debian. 

Just tried Mint:

> pentacle ~ # apt install git autoconf automake autopoint libtool gettext 
> meson ninja
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> autoconf is already the newest version (2.69-9).
> automake is already the newest version (1:1.15-4ubuntu1).
> autopoint is already the newest version (0.19.7-2ubuntu3).
> gettext is already the newest version (0.19.7-2ubuntu3).
> libtool is already the newest version (2.4.6-0.1).
> git is already the newest version (1:2.7.4-0ubuntu1.3).
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> 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.
> pentacle ~ # 

Unfortunately, apt doesn't say *why* it won't install ninja-build, so I
have no way of knowing how the problem can be fixed.

///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

Re: [e-users] Terminology deleted by update

[Peter Flynn]

On 18/04/18 09:56, Carsten Haitzler (The Rasterman) wrote:
> On Wed, 18 Apr 2018 09:11:33 +0100 Peter Flynn  said:
>> I know meson is terribly fashionable these days, but I have tried
>> to get it to work on at least five Linux distros and it's never
>> worked properly -- always been missing some unfindable component.
> 
> ummm maybe its just the distros you tried that don't stay up to date
> that easily?

Is Meson that neglected in some places? I had sort of assumed it would
be under heavy support as it's become so popular.

So far I have tried Ubuntu, RedHat, CentOS, Bodhi, and raw Debian. All
failed because some specific library was not available in the version
required (different library for each distro), or because build
instructions for the project I was working on expected an environment
that didn't exist (presumably the original developer's environment).

> at last arch has been smooth sailing on this, but it's a rolling
> distro so it stays relatively up to date :)
Sounds good. I've avoided Arch because last time I tried it, it broke
Emacs, and was several versions behind on a few key (for me) packages.
But if that's changed I should look at it again.

Thanks for the tips.

///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

Re: [e-users] Terminology deleted by update

[The Rasterman]

On Wed, 18 Apr 2018 09:11:33 +0100 Peter Flynn  said:

> Yes, it looks like a build fail.
> 
> Thanks, Carsten, for suggesting dpkg --purge. I had used apt --purge but it 
> seems that doesn't actually purge everything.
> 
> Then reinstalling it worked (with a waning) so now it's back and on hold.
> 
> I know meson is terrribly fashionable these days, but I have tried to get 
> it to work on at least five Linux distros and it's never worked properly -- 
> always been missing some unfindable component.

ummm maybe its just the distros you tried that don't stay up to date that
easily? at last arch has been smooth sailing on this, but it's a rolling distro
so it stays relatively up to date :)

> ///Peter
> 
> On 18 April 2018 03:27:53 Dave  wrote:
> 
> Weird.  I've downloaded and unpacked that deb file.  It just contains the
> /usr/share/doc/terminology data.  No binaries.  I'm guessing whoever created
> it has an automated system for building packages, and it's failing on binary
> compilation.
> 
> Your old deb files are located in /var/cache/apt/archives .  You can install
> the previous terminology version from there via dpkg, or download the old
> version from the repository.  Then you can put the package on "hold" by
> running "echo terminology hold | dpkg --set-selections".  That'll prevent it
> from being automatically upgraded.
> 
> Otherwise, you could always compile the latest terminology yourself.  It's
> not too hard.  Though there is an annoying focus bug present in the latest
> version, which you may want to avoid until a point release is done.
> 
> Cheers,
> dave.k
> 
> 
> In the year 2018, of the month of April, on the 17th day, Peter Flynn wrote:
> Sorry, this failed to send earlier.
> 
> On 17/04/18 12:12, Peter Flynn wrote:
> [...]> 1 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> E: Internal Error, No file name for terminology:amd64
> 
> Does anyone know where I can get it in a .deb form that won't vanish
> at an update
> 
> I did some digging into
> http://ppa.launchpad.net/niko2040/e19/ubuntu/pool/main/t/terminology/
> and found that the two most recent .debs are only 11Kb, which must
> surely be an error.
> 
> terminology_1.2.0-0artful0_amd64.deb  2018-04-15 19:205.7M
> terminology_1.2.0-0bionic0_amd64.deb  2018-04-15 19:525.7M
> terminology_1.2.0-0trusty4_amd64.deb  2018-04-15 20:0611K
> terminology_1.2.0-0xenial3_amd64.deb  2018-04-15 20:0611K
> 
> I've sent Niko an email via launchpad, but does anyone else have a solution?
> 
> 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
> enlightenment-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
> 
> --
> 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
> 
> 
> 
> 
> --
> 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

Re: [e-users] Terminology deleted by update

[Peter Flynn]

Yes, it looks like a build fail.

Thanks, Carsten, for suggesting dpkg --purge. I had used apt --purge but it 
seems that doesn't actually purge everything.


Then reinstalling it worked (with a waning) so now it's back and on hold.

I know meson is terrribly fashionable these days, but I have tried to get 
it to work on at least five Linux distros and it's never worked properly -- 
always been missing some unfindable component.


///Peter

On 18 April 2018 03:27:53 Dave  wrote:

Weird.  I've downloaded and unpacked that deb file.  It just contains the
/usr/share/doc/terminology data.  No binaries.  I'm guessing whoever created
it has an automated system for building packages, and it's failing on binary
compilation.

Your old deb files are located in /var/cache/apt/archives .  You can install
the previous terminology version from there via dpkg, or download the old
version from the repository.  Then you can put the package on "hold" by
running "echo terminology hold | dpkg --set-selections".  That'll prevent it
from being automatically upgraded.

Otherwise, you could always compile the latest terminology yourself.  It's
not too hard.  Though there is an annoying focus bug present in the latest
version, which you may want to avoid until a point release is done.

Cheers,
dave.k


In the year 2018, of the month of April, on the 17th day, Peter Flynn wrote:
Sorry, this failed to send earlier.

On 17/04/18 12:12, Peter Flynn wrote:
[...]> 1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for terminology:amd64

Does anyone know where I can get it in a .deb form that won't vanish
at an update

I did some digging into
http://ppa.launchpad.net/niko2040/e19/ubuntu/pool/main/t/terminology/
and found that the two most recent .debs are only 11Kb, which must
surely be an error.

terminology_1.2.0-0artful0_amd64.deb2018-04-15 19:205.7M
terminology_1.2.0-0bionic0_amd64.deb2018-04-15 19:525.7M
terminology_1.2.0-0trusty4_amd64.deb2018-04-15 20:0611K
terminology_1.2.0-0xenial3_amd64.deb2018-04-15 20:0611K

I've sent Niko an email via launchpad, but does anyone else have a solution?

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
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

--
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




--
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

Re: [e-users] Terminology deleted by update

[The Rasterman]

On Wed, 18 Apr 2018 09:52:49 +0200 Boris Faure  said:

> On 18-04-18 12:08, Dave wrote:
> >  Weird.  I've downloaded and unpacked that deb file.  It just contains the
> > /usr/share/doc/terminology data.  No binaries.  I'm guessing whoever created
> > it has an automated system for building packages, and it's failing on binary
> > compilation.
> 
> With Terminology 1.2.0, the build system has changed. I've written about
> it in my release notes. That's the likely reason the 1.2.0 package is
> broken.

indeed the older ubuntus might not have a recent enough meson to work right...


-- 
- 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

Re: [e-users] Terminology deleted by update

[Boris Faure]

On 18-04-18 12:08, Dave wrote:
>  Weird.  I've downloaded and unpacked that deb file.  It just contains the
> /usr/share/doc/terminology data.  No binaries.  I'm guessing whoever created
> it has an automated system for building packages, and it's failing on binary
> compilation.

With Terminology 1.2.0, the build system has changed. I've written about
it in my release notes. That's the likely reason the 1.2.0 package is
broken.

Best Regards
-- 
Boris Faure
Pointer Arithmetician
--
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

Re: [e-users] Terminology deleted by update

[The Rasterman]

On Tue, 17 Apr 2018 22:07:41 +0100 Peter Flynn  said:

> On 17/04/18 14:59, Carsten Haitzler (The Rasterman) wrote:
> > On Tue, 17 Apr 2018 12:12:24 +0100 Peter Flynn  said:
> > 
> [...]
> >> Does anyone know where I can get it in a .deb form that won't vanish at
> >> an update?
> > 
> > perhaps remove the pkgs fully (dpkg --purge it) before re-installing?
> 
> Good point, but as I added, the repo seems to have bogus .debs (only 11Kb).

that sounds wrong... indeed. i can't help there. you'll have to contract the
maintainers. :)

> On another machine running Mint 18 I have
> terminology_1.1.1-0xenial1_amd64.deb so I have copied that to a safe
> place where I can try again tomorrow.
> 
> ///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

Re: [e-users] Terminology deleted by update

[Dave]

 Weird.  I've downloaded and unpacked that deb file.  It just contains the
/usr/share/doc/terminology data.  No binaries.  I'm guessing whoever created
it has an automated system for building packages, and it's failing on binary
compilation.

 Your old deb files are located in /var/cache/apt/archives .  You can install
the previous terminology version from there via dpkg, or download the old
version from the repository.  Then you can put the package on "hold" by
running "echo terminology hold | dpkg --set-selections".  That'll prevent it
from being automatically upgraded.

 Otherwise, you could always compile the latest terminology yourself.  It's
not too hard.  Though there is an annoying focus bug present in the latest
version, which you may want to avoid until a point release is done.

 Cheers,
 dave.k


 In the year 2018, of the month of April, on the 17th day, Peter Flynn wrote:
> Sorry, this failed to send earlier.
> 
> On 17/04/18 12:12, Peter Flynn wrote:
> [...]> 1 not fully installed or removed.
> > After this operation, 0 B of additional disk space will be used.
> > E: Internal Error, No file name for terminology:amd64
> >
> > Does anyone know where I can get it in a .deb form that won't vanish
> > at an update
> 
> I did some digging into
> http://ppa.launchpad.net/niko2040/e19/ubuntu/pool/main/t/terminology/
> and found that the two most recent .debs are only 11Kb, which must
> surely be an error.
> 
> terminology_1.2.0-0artful0_amd64.deb  2018-04-15 19:205.7M
> terminology_1.2.0-0bionic0_amd64.deb  2018-04-15 19:525.7M
> terminology_1.2.0-0trusty4_amd64.deb  2018-04-15 20:0611K 
> terminology_1.2.0-0xenial3_amd64.deb  2018-04-15 20:0611K 
> 
> I've sent Niko an email via launchpad, but does anyone else have a solution?
> 
> 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
> enlightenment-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-users

--
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

Re: [e-users] Terminology deleted by update

[Peter Flynn]

Sorry, this failed to send earlier.

On 17/04/18 12:12, Peter Flynn wrote:
[...]> 1 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> E: Internal Error, No file name for terminology:amd64
>
> Does anyone know where I can get it in a .deb form that won't vanish
> at an update

I did some digging into
http://ppa.launchpad.net/niko2040/e19/ubuntu/pool/main/t/terminology/
and found that the two most recent .debs are only 11Kb, which must
surely be an error.

terminology_1.2.0-0artful0_amd64.deb2018-04-15 19:205.7M
terminology_1.2.0-0bionic0_amd64.deb2018-04-15 19:525.7M
terminology_1.2.0-0trusty4_amd64.deb2018-04-15 20:0611K 
terminology_1.2.0-0xenial3_amd64.deb2018-04-15 20:0611K 

I've sent Niko an email via launchpad, but does anyone else have a solution?

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
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] Terminology deleted by update

[Peter Flynn]

On 17/04/18 14:59, Carsten Haitzler (The Rasterman) wrote:
> On Tue, 17 Apr 2018 12:12:24 +0100 Peter Flynn  said:
> 
[...]
>> Does anyone know where I can get it in a .deb form that won't vanish at
>> an update?
> 
> perhaps remove the pkgs fully (dpkg --purge it) before re-installing?

Good point, but as I added, the repo seems to have bogus .debs (only 11Kb).

On another machine running Mint 18 I have
terminology_1.1.1-0xenial1_amd64.deb so I have copied that to a safe
place where I can try again tomorrow.

///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

Re: [e-users] Terminology deleted by update

[The Rasterman]

On Tue, 17 Apr 2018 12:12:24 +0100 Peter Flynn  said:

> I recently installed Mint 18 on a desktop system, and added e and
> terminology like this:
> 
> sudo add-apt-repository -y ppa:niko2040/e19
> sudo apt-get update
> sudo apt-get install enlightenment terminology
> 
> All working nicely. Then this morning I ran my weekly update:
> 
> peter@oimelc:~/$ sudo apt update
> [sudo] password for peter:
> Hit:1 http://ppa.launchpad.net/gezakovacs/ppa/ubuntu xenial InRelease
> Hit:2 http://archive.canonical.com/ubuntu xenial InRelease
> Hit:3 http://archive.ubuntu.com/ubuntu xenial InRelease
> Get:4 http://ppa.launchpad.net/niko2040/e19/ubuntu xenial InRelease
> ...all normal.
> 
> peter@oimelc:~/$ sudo apt upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following NEW packages will be installed:
>   libdrm-common libllvm5.0 libqmi-glib5
> The following packages will be upgraded:
>   apparmor apport apt apt-transport-https apt-utils apt-xapian-index
> [snip lots and lots of packages]
>   systemd-sysv terminology timeshift transmission-common
> After this operation, 87.4 MB of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Get:1 http://ppa.launchpad.net/niko2040/e19/ubuntu xenial/main amd64
> terminology amd64 1.2.0-0xenial3 [11.0 kB]
> Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64
> bsdutils amd64 1:2.27.1-6ubuntu3.4 [51.5 kB]
> [...]
> 
> So off it went and updated everything just fine...EXCEPT at the end:
> 
> dpkg: error processing package terminology (--configure):
>  subprocess installed post-installation script returned error exit status 2
> 
> Errors were encountered while processing:
>  terminology
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Terminology has disappeared from my menus and from /usr/bin so it has
> vanished.
> 
> I tried to get it back with:
> 
> $ sudo apt-get --reinstall install terminology
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not
> upgraded.
> 1 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> E: Internal Error, No file name for terminology:amd64
> 
> Does anyone know where I can get it in a .deb form that won't vanish at
> an update?

perhaps remove the pkgs fully (dpkg --purge it) before re-installing?

-- 
- 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