[Bug 208003] [lshell] connection closed after one command

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Mar 15 03:58:28 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208003

            Bug ID: 208003
           Summary: [lshell] connection closed after one command
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: mouzannar at gmail.com

Created attachment 168197
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=168197&action=edit
patch solving the connection closing

Hello,

Users running FreeBSD 10.{0,2}-RELEASE with the lshell-0.9.16 package have
reported a bug upstream that lshell exited after only one command. I have
successfully reproduced the bug on a vagrant FreeBSD 10.2-RELEASE box (thanks
for making the FreeBSD vagrant box available). Unfortunately, this makes the
lshell package unusable on FreeBSD. 

This issue can be easily fixed by applying the following (and attached) patch
or by upgrading the package to the latest version 0.9.18 [1].

--- shellcmd.py.bak     2016-03-15 03:35:36.718063000 +0000
+++ shellcmd.py 2016-03-15 03:36:06.377039000 +0000
@@ -134,7 +134,7 @@
                 self.g_arg = ' '.join(self.g_line.split()[1:])
                 self.cd()
             else:
-                os.system('set -m; %s' % self.g_line)
+                os.system('%s' % self.g_line)
         elif self.g_cmd not in ['', '?', 'help', None]: 
             self.log.warn('INFO: unknown syntax -> "%s"' %self.g_line)
             self.stderr.write('*** unknown syntax: %s\n' %self.g_cmd)


You will find more info on the bug in the upstream report:
https://github.com/ghantoos/lshell/issues/92

Cheers,
 Ignace M

[1] https://github.com/ghantoos/lshell/releases/tag/0.9.18

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list