Control: severity 861180 normal
2017-05-04 16:30 GMT-03:00 Tong Sun :
> Hi Eriberto,
Hi,
> Do you still want to mark the Severity: as grave
> after Jörg Sommer has explained in
> https://github.com/neurobin/shc/issues/23#issuecomment-299035820
> that there is a workaround?
I tested this workaro
Processing control commands:
> severity 861180 normal
Bug #861180 [shc] shc: infinite loop makes the final executable not work
properly
Severity set to 'normal' from 'grave'
--
861180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861180
Debian Bug Tracking System
Contact ow...@bugs.debian.o
Hi Eriberto,
Do you *still* want to mark the Severity: as grave
after *Jörg Sommer *has explained in https://github.com/neurobin/
shc/issues/23#issuecomment-299035820
that there is a workaround?
Marking Severity: as grave will make
shc 3.8.9b-1 for* autoremoval from testing on **2017-05-24*
Wou
On Sat, Apr 29, 2017 at 7:45 PM, Eriberto wrote:
> I did some tests and I have news. I downloaded the versions 3.8.6 and
> 3.8.7 from upstream homepage and I did a 'make' inside a Sid jail.
> After this, I compiled a shell script. The script compiled by 3.8.6
> version worked fine, but the script
Hi,
2017-04-29 16:58 GMT-03:00 Eriberto :
> Hi,
>
> Searching inside Repology.org[1], I found a fork with a new upstream
> and new versions[2]. However, the newest version (3.9.3) has the same
> issue[3].
>
> Regards,
>
> Eriberto
>
> [1] https://repology.org/metapackage/shc/versions
> [2] https:/
Hi,
Searching inside Repology.org[1], I found a fork with a new upstream
and new versions[2]. However, the newest version (3.9.3) has the same
issue[3].
Regards,
Eriberto
[1] https://repology.org/metapackage/shc/versions
[2] https://github.com/neurobin/shc
[3] https://github.com/neurobin/shc/is
Thanks Eriberto for the offer.
I don't know how fast Francisco can response. Javier, could you see if you
can do anything? Thanks.
On Tue, Apr 25, 2017 at 12:24 PM, Eriberto wrote:
> 2017-04-25 13:09 GMT-03:00 Tong Sun :
> > Thanks for the detailed steps Eriberto, forwarding to the upstream
> au
2017-04-25 13:09 GMT-03:00 Tong Sun :
> Thanks for the detailed steps Eriberto, forwarding to the upstream author.
>
> Francisco, could you take a look at it please?
>
> Thanks
This bug could be solved soon to avoid shc be excluded from next
Debian Stable. I can sponsor the package if you want.
Thanks for the detailed steps Eriberto, forwarding to the upstream author.
Francisco, could you take a look at it please?
Thanks
On Tue, Apr 25, 2017 at 10:20 AM, Eriberto Mota wrote:
> 2017-04-25 10:42 GMT-03:00 Tong Sun :
> > Hi Eriberto,
> >
> > Is your infinite loop problem exactly as desc
2017-04-25 10:42 GMT-03:00 Tong Sun :
> Hi Eriberto,
>
> Is your infinite loop problem exactly as described in
> https://sfxpt.wordpress.com/2014/02/23/shc-3-8-9-is-not-usable/ ?
Hi Tong! Thanks for your quick reply.
No, not embedded here. See the following step-by-step:
1. The script test.sh:
Hi Eriberto,
Is your infinite loop problem exactly as described in
https://sfxpt.wordpress.com/2014/02/23/shc-3-8-9-is-not-usable/ ?
On Tue, Apr 25, 2017 at 9:24 AM, Joao Eriberto Mota Filho <
eribe...@debian.org> wrote:
> Package: shc
> Version: 3.8.9b-1+b1
> Severity: grave
> Tags: upstream
Package: shc
Version: 3.8.9b-1+b1
Severity: grave
Tags: upstream stretch
Justification: renders package unusable
Dear Maintainer,
The shc command is generating executables which can not be used over
Stretch and Sid. After generate the executable, when running, the
program.sh.x enter in an infinit
12 matches
Mail list logo
