Bug#1000101: eterm: depends on obsolete pcre3 library
Bastian Germann wrote: > Hi, > > I am uploading a NMU to fix this. The debdiff is attached. > > Sincerely, > Bastian Thank you so much for fixing this. I am planing to review build dependences to removed those no needed. Sincerely, Jose
Bug#1018023: Update on this bug?
Dear Matthew, I have just uploaded to mentors a new version of the package fixing this bug. I will made other improvements after Bookworm is released as we are very close to the full freeze. The new package can be found here: https://mentors.debian.net/package/eterm/ Thank you for your interest in Eterm, Jose Matthew Vernon wrote: > Hi, > > On 14/02/2023 18:36, Jose Antonio Jimenez Madrid wrote: > >> I will test this patch and let you to know whether the bug is fixed. > > Any joy? We're approaching the time that eterm is going to be > autoremoved from bookworm... > > Thanks, > > Matthew
Bug#1018023: Update on this bug?
Thanks Matthew for the links. I will test this patch and let you to know whether the bug is fixed. Sincerely, Jose Matthew Vernon wrote: > Hi, > > Do you have plans to fix this before the bookworm freeze, please? > > I think netbsd at least have patched eterm to work with the newer > imlib; at least per the comment here > https://github.com/mej/Eterm/issues/4 > > That linked to > http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/x11/eterm/patches/ > > Which has a couple of patches that seem like they'd do the trick... > > Thanks, > > Matthew
Bug#989041: eterm: CVE-2021-33477
Thank you so much Utkarsh for the patch, Please, upload it to unstable, as I have to upload it by Debian Mentors so it will reach testing faster if you upload it to fix this security bug. Also, you can upload it to buster-pu, the package version is the same than in Stretch, so it just to upload the same that you have already upload for Stretch. I will send the patch to upstream. There are several minor issues I have to coordinate with upstream that can be done later. Thank you so much for your great work. Jose
Bug#989041: eterm: CVE-2021-33477
Thank you Salvatore for submitting this important bug. I have sent this information to upstream and I have read the information you provided. It is the first time I have to deal with a security bug, so I do not know the right procedure to follow. I suppose there is a script or procedure to check whether the patch version has the problem fixed or not. I let you to know if upstream gives a patch. Sincerely, Jose P.S.: I have some knowledge of programming but I do not know whether I would be able to produce a patch on time for the upcoming bullseye release.
Bug#770369: Bug#737491: eterm: Occurs on upgrade to Jessie from Wheezy
Hi, Andy, I have tested a couple of solutions and I think the easiest way for you is just to download the Eterm package for Stretch (testing) and install it in your system manually with: dpkg -i eterm_0.9.6-4_amd64.deb I have just installed the Eterm version in testing and no new packages are needed, just this one and it is working in my system. (One can use pinning in apt to install packages for several distributions, but for just one package I think it is not necessary in this case). Please, let me know if this solution is not working for you to try a more elaborate fix until Stretch is released. Regards, Jose P.S.: Do not apologise for the "duplication" of bug numbers. It is not your fault, you used "reportbug" correctly. I draw the attention about the duplication of the bug to close both of them as one is already fixed in testing, just to document it and to not forget to close both. Andy Bennett wrote: 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
Bug#770369: Bug#737491: eterm: Occurs on upgrade to Jessie from Wheezy
(I am writing to bugs #737491 and #770369 as the fix is the same) Dear Andy, I think this bug is the same than bug #770369. 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. 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 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. Sincerely, Jose
