On Wed, 10 Jul 2019 at 03:31, Chris Morley
wrote:
>
> Vte could be rmoved, other then it could break any custom screens in the
> wild.
>
>
What is -vte used for?
https://packages.debian.org/search?keywords=python-vte
Suggests that is it still there in Sid.
--
atp
"A motorcycle is a bicycle wi
How do you forward port?
JT
On 7/9/2019 9:29 PM, Chris Morley wrote:
Removing python-sourceview2 will break all gscreen skins - including custom
skins in the wild, gmoccapy and anything else that displays gcode with GladeVCP.
Vte could be rmoved, other then it could break any custom screens i
Let's see if I push the right reply button this time and reply to the
list...
Trying to install dev and yapps2 is not available so one more for the
list. I've not looked to see where it is used yet.
JT
On 7/10/2019 5:53 AM, andy pugh wrote:
On Wed, 10 Jul 2019 at 03:31, Chris Morley
wrote:
What is -vte used for?
https://packages.debian.org/search?keywords=python-vte
Suggests that is it still there in Sid.
Hi Andy
virtual terminal emulation
Buster is full of holes currently, where packages in sid have not been
back-ported.
You should find that the kernel, gcc libc etc. ve
So much for memory, can't even walk from the beer cave to the machine
shop without forgetting something.
It's yapps2-runtime that's not in Debian 10. The only place I see it is
in debian/control.top.in in the dev section.
JT
On 7/10/2019 5:53 AM, andy pugh wrote:
On Wed, 10 Jul 2019 at 03:3
On Wed, 10 Jul 2019 at 11:53, andy pugh wrote:
>
> https://packages.debian.org/search?keywords=python-vte
>
> Suggests that is it still there in Sid.
>
https://wiki.debian.org/SimpleBackportCreation
Might contain the answer for packaging.
--
atp
"A motorcycle is a bicycle with a pandemonium a
AFAIK backporting is getting a package from a newer version of Debian
into an older version. We have the opposite problem.
JT
On 7/10/2019 7:40 AM, andy pugh wrote:
On Wed, 10 Jul 2019 at 11:53, andy pugh wrote:
https://packages.debian.org/search?keywords=python-vte
Suggests that is it sti
Hi,
For python-vte, it's labelled "debports'" not "backports" but either way, they
don't make the package available through synaptic. Maybe need to modify
sources.list or do it through the command line (like apt-get install -t
debports python-vte) I haven't looked into this much, but I haven't
On 7/10/19 12:20 PM, Alec Ari via Emc-developers wrote:
For python-vte, it's labelled "debports'" not "backports" but either
way, they don't make the package available through synaptic. Maybe
need to modify sources.list or do it through the command line (like
apt-get install -t debports python-vt
On 7/10/19 12:20 PM, Alec Ari via Emc-developers wrote:
For python-vte, it's labelled "debports'" not "backports" but either
way, they don't make the package available through synaptic. Maybe
need to modify sources.list or do it through the command line (like
apt-get install -t debports python-vt
Thanks for sluthing that out Seb, someone one on the forum also said
that gmoccapy imports vte but does not use it.
JT
On 7/10/2019 2:18 PM, Sebastian Kuzminsky wrote:
On 7/10/19 12:20 PM, Alec Ari via Emc-developers wrote:
For python-vte, it's labelled "debports'" not "backports" but either
I deleted yapps2-runtime from debian/control.top.in in the dev section
as that is the only place grep can find yapps2-runtime and rebuilt. Now
dev installs without complaining. I tested halcompile and it runs, is
there anything else in dev besides halcompile?
JT
On 7/10/19 2:59 PM, John Thornton wrote:
I deleted yapps2-runtime from debian/control.top.in in the dev section
as that is the only place grep can find yapps2-runtime and rebuilt. Now
dev installs without complaining. I tested halcompile and it runs, is
there anything else in dev besides halcom
Hi Seb,
It never hurts to double tag team when wrestling a problem out.
I think your correct that having yapps2-runtime | python-yapps for dev
is a correct solution and I can test that on a fresh install in the morning.
JT
On 7/10/19 4:35 PM, Sebastian Kuzminsky wrote:
On 7/10/19 2:59 PM, J
Vte can be removed without hurting the core functionality.
It was a convenience for debugging.
It could break custom screens that people might have out in the wild.
I'm thinking on how to trap the error and let custom users know...
There was talk of sourceview2 not being available - that is much
Hallo,
I just pushed a bugfix for gmoccapy, removing the unused import
statements vte and pango. So from my side, there is no need any more to
depent on vte.
sourceview2 will be a more complex matter.
Norbert
Am 10.07.19 um 04:29 schrieb Chris Morley:
Removing python-sourceview2 will break al
16 matches
Mail list logo