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 comm
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 download
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 wh
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 t
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
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 pack
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 pack
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
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 t
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
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
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
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, e
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
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
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 g
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 dep
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
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
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
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-
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 w
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
>>> w
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 u
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.
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 tri
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 package
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
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 re
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/archiv
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
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
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 t
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
[
34 matches
Mail list logo
