Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 143272
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Default Assignee for Orphaned Packages <maintainer-needed@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Brad Allen <ULMO@SONIC.NET>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
sc-7.16-lexfix.patch Patch to fix ret initialisation patch Nick White 2007-11-19 00:28 0000 279 bytes Details | Diff
sc-7.16.ebuild Updated sc-7.16 ebuild text/plain Nick White 2007-11-19 00:30 0000 1.08 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 143272 depends on: Show dependency tree
Bug 143272 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-08-08 16:35 0000
syntax error: let A0<= = 10
syntax error: rightstring A0<= = "foo

app-office/sc-7.16 doesn't allow you to execute assignment commands from
anywhere, including saved files.  It does not work.  I tried with various
compiler flags, and it made no difference.

app-office/sc-7.12 does work.

To reproduce:

invoke sc (that's ESS CEE on the command line by itself)
type command >foo [RETURN] (that's GREATERTHAN EFF OH OH RETURN)
  syntax error: rightstring A0<= = "foo
or command =10 [RETURN] (that's EQUALS ONE ZERO RETURN)
  syntax error: let A0<= = 10

It gives error.  Try in sc-7.12, and notice it works right.

I put a mask in /etc/portage/package.mask for sc-7.16, and it works great.  I
recommend Gentoo put sc-7.16 into ~ or - (soft or hard mask?) so that 7.12 will
stick around long enough for the bug to be resolved.

------- Comment #1 From Jakub Moc (RETIRED) 2006-08-08 23:27:31 0000 -------
Last upstream release 4 years old; no maintainer. I'd rather see this thing go
to /dev/null.

------- Comment #2 From Brad Allen 2006-08-10 21:44:54 0000 -------
> Last upstream release 4 years old; no maintainer. I'd rather see this thing go
> to /dev/null.

2 things:

1.  How do we get stats on what packages people are using?  How many people use
sc?
2.  I'll consider becoming maintainer for sc.  So far, I copied some files into
ftp://ftp.sonic.net/pub/users/qm/sc/ and http://www.sonic.net/~qm/sc/ -- I'll
put this into slow burn until it works.  I have little time but if I do start
maint on this thing, it'll be to just keep it working.  Right now, of course,
the above bug still exists.  If I have to fix it, I'll do it some day but not
right away.

------- Comment #3 From Brad Allen 2006-08-10 22:08:43 0000 -------
> Last upstream release 4 years old; no maintainer. I'd rather see this thing go
> to /dev/null.

Ok, I read some Gentoo docs and can't find how to become maintainer of the
Gentoo sc package.  I want to do it.  Where's the link for docs for becoming
maintainer?  Do I just become a developer and then add myself to some XML list
someplace?  Or is there a more straightforward way?

------- Comment #4 From Jean-François Gagnon Laporte 2006-08-11 05:22:44 0000 -------
(In reply to comment #3)
>1.  How do we get stats on what packages people are using?  How many people >use sc?
> 
We currently do not have any stats available but there's a SoC project done by
genone for it.

> Ok, I read some Gentoo docs and can't find how to become maintainer of the
> Gentoo sc package.  I want to do it.  Where's the link for docs for becoming
> maintainer?  
> 
http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2

I think your best bet would be to find a developper to proxy maintain this
beast or let it drop from the main tree and get in contact with the sunrise
developpers to try your hand at maintaining it.

It won't be straightforward to become a dev since you have to be involved in
the project for a while, get noticed by current developpers, get a mentor etc
etc. All is explained in the link that I provided you.

------- Comment #5 From Alec Warner 2006-08-11 09:35:01 0000 -------
(In reply to comment #3)
> > Last upstream release 4 years old; no maintainer. I'd rather see this thing go
> > to /dev/null.
> 
> Ok, I read some Gentoo docs and can't find how to become maintainer of the
> Gentoo sc package.  I want to do it.  Where's the link for docs for becoming
> maintainer?  Do I just become a developer and then add myself to some XML list
> someplace?  Or is there a more straightforward way?
> 

Become a dev or put it in sunrise.

------- Comment #6 From Barral 2006-11-04 06:10:01 0000 -------
(In reply to comment #5)

any news about this?
(I would find it a pitty if this package would be removed)

------- Comment #7 From Charlie Shepherd (RETIRED) 2006-11-04 06:26:23 0000 -------
(In reply to comment #6)
> any news about this?
> (I would find it a pitty if this package would be removed)

It can only go in sunrise when its punted (see sunrise policy), so wait till
then, or find a dev to proxy for you.

------- Comment #8 From Charlie Shepherd (RETIRED) 2006-12-08 11:55:41 0000 -------
(In reply to comment #7)
> (In reply to comment #6)
> > any news about this?
> > (I would find it a pitty if this package would be removed)
> 
> It can only go in sunrise when its punted (see sunrise policy), so wait till
> then, or find a dev to proxy for you.

Seeing as I'm now a dev, I would be willing to proxy for you. Please mail me or
ping me on IRC (nick is masterdriverz).

------- Comment #9 From Charlie Shepherd (RETIRED) 2006-12-17 15:48:46 0000 -------
(In reply to comment #8)
> Seeing as I'm now a dev, I would be willing to proxy for you. Please mail me or
> ping me on IRC (nick is masterdriverz).

Just to update people, me and Kai are arranging proxy-maintaining this. 

------- Comment #10 From Carsten Luckmann 2007-01-24 11:19:14 0000 -------
Error occurs only when compiled with gcc-4(.1.1-r3).  Works fine if compiled
with gcc-3(.4.6-r1).

------- Comment #11 From Carsten Luckmann 2007-02-09 15:10:08 0000 -------
The bug lies somewhere in lex.c.  If you compile lex.c with either gcc-3 or
with gcc-4 -O0 (i.e. without optimization) it works.

(gcc-3.4.6-r1 and gcc-4.1.1-r3 used.)

------- Comment #12 From kAbaIaKH 2007-04-08 19:21:46 0000 -------
(In reply to comment #11)
> The bug lies somewhere in lex.c.  If you compile lex.c with either gcc-3 or
> with gcc-4 -O0 (i.e. without optimization) it works.
> 
> (gcc-3.4.6-r1 and gcc-4.1.1-r3 used.)
> 
It seems that the 'ret' variable within yylex() lacks its initialisation. From
Debian existing patch, adding '= 0' make everything work fine.

------- Comment #13 From Jakub Moc (RETIRED) 2007-11-17 20:23:13 0000 -------
Back to treecleaners...

------- Comment #14 From Nick White 2007-11-19 00:28:50 0000 -------
Created an attachment (id=136333) [details]
Patch to fix ret initialisation

 (In reply to comment #12)
> It seems that the 'ret' variable within yylex() lacks its initialisation. From
> Debian existing patch, adding '= 0' make everything work fine.

This patch applies the fix; seems to work cleanly. Ebuild incorporating this
follows.

------- Comment #15 From Nick White 2007-11-19 00:30:16 0000 -------
Created an attachment (id=136335) [details]
Updated sc-7.16 ebuild

Ebuild taking new patch into account

------- Comment #16 From Ryan Hill 2008-01-17 20:59:45 0000 -------
Fixed (along with a bunch of other stuff) in sc-7.16-r1.

------- Comment #17 From Malte Pe 2008-01-30 12:08:57 0000 -------
Thanks for keeping sc up to date! I actually use it, now that the 'syntax
error' bug has been fixed. Seeing as it's the only CLI spreadsheet editor in
portage (I may be wrong), it really would be a pitty if this thing would go
down /dev/null.

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug