Bug#770369: Bug#737491: eterm: Occurs on upgrade to Jessie from Wheezy
Hi,
Thanks for your help!
I think this bug is the same than bug #770369.
I tried to file this as a followup to the existing bug but must have messed
up with my usage of `reportbug`; sorry!
This bug is close in stretch (testing). As it is expected the
release stretch occurs soon, the easiest way is:
1. To wait for the release of stretch to get this problem fixed
when you upgrade from Wheezy to Stretch.
2. Downgrade the Eterm package to the version in Jessie so you
can use it until the upgrade to Stretch.
Do you mean wheezy? Do you have a command to hand that can do that for me
or is it best to fetch the .deb out of the appropriate package pool?
I am trying to maintain Eterm package, but my process of
learning to do it properly is getting a little long so
I have not prepared a new Eterm package.
I have checked the fix proposed and my local Eterm package is
working in Jessie-amd64 (thanks to Charles Gorand and Arnaud
Ceyroll for the fix).
Andy, if you want I can send you my local package to your
e-mail, so you can use it.
For Santiago Vila (or other developers) I have modified the
source package in Jessie by performing the fix suggested by
Arnaud and Charles to the command.c file, just
recompiled in my Jessie system and the new Eterm package is
working again.
Maybe I can try to build my own local package? Are you able to send me the
patch for the Jessie package?
Maybe it is worth to propose an update for Jessie
so the package will be usable again
for all the users. I will have some spare time after the middle
of June, so I would be able to apply the fix in the correct way
(I have just edited the source to test it, I have to read deeper
the maint-guide to
do it in the right way).
After the release of Stretch I will try to fix the UTF8 problem
in Eterm to finally maintain this package.
Thanks for your help and for giving the time.
Regards,
@ndy
--
andyjpb@ashurst.eu.org
http://www.ashurst.eu.org/
0x7EBA75FF
Reply to: