Package Details: sc-im 0.8.2-1

Git Clone URL: https://aur.archlinux.org/sc-im.git (read-only, click to copy)
Package Base: sc-im
Description: A spreadsheet program based on SC
Upstream URL: https://github.com/andmarti1424/sc-im
Licenses: BSD
Conflicts: sc-im-git, scim-spreadsheet
Submitter: Rhinoceros
Maintainer: Rhinoceros (andmarti1424)
Last Packager: Rhinoceros
Votes: 43
Popularity: 2.58
First Submitted: 2015-09-05 01:44
Last Updated: 2021-05-18 22:32

Dependencies (4)

Required by (0)

Sources (2)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Rhinoceros commented on 2021-04-19 11:10

@GregTheMadMonk No worries at all. Easy error to make, and you aren't the first person to get confused by this. And I appreciate you posting here and attempting to improve the package too!

GregTheMadMonk commented on 2021-04-19 11:07

@Rhinoceros, oh, I see... My bad, sorry...

Rhinoceros commented on 2021-04-19 10:05

@GregTheMadMonk base-devel, which includes bison, is assumed to be installed when building packages. As per the wiki, this should not be in the makedepends array.

GregTheMadMonk commented on 2021-04-19 09:49

You should probably add bison to make dependencies. yacc (which is provided by bison package) seems to be required during build (or, at least, it didn't build for me unless I've installed bison)

luukvbaal commented on 2021-03-19 15:56

Right you are, my bad.

Rhinoceros commented on 2021-03-19 08:21

@luukvbaal Works for me in a clean directory. Upstream changed their versioning, but I reflected the change in the new checksum. You probably have the old one cached by your AUR helper.

luukvbaal commented on 2021-03-19 08:03

Getting sc-im-0.8.0.tar.gz ... FAILED arch.0.8.0.patch ... Passed ==> ERROR: One or more files did not pass the validity check! please check.

Rhinoceros commented on 2021-02-26 04:08

@crossgear Sorry, I didn't mean the Markdown, but thanks for fixing up the formatting anyway. I actually meant the Warning: sc-im is only available from AUR parts, etc., which I didn't recognise. The "basic" way to install is manually doing makepkg -s, which excludes all the additional things that can go wrong when using an AUR helper to install packages. It's a good fallback test when things go wrong.

Having said that, I don't know anything about Manjaro really, so the issues might be related to different version or defaults of patch? Or more likely the paths where it builds packages? If you can't get it to build, it might be more helpful to ask at a Manjaro forum.

crossgear commented on 2021-02-26 03:45

@Rhinoceros No, I've just never used Markdown before. I was redirected from Github to comment here. Never tried makepkg -s, but I can try. Maybe worth noting that I'm running Manjaro.

Rhinoceros commented on 2021-02-26 03:33

@crossgear I just tried again and it works for me. What is all that extra text you posted? Are you using some AUR helper? Can you test with just a manual makepkg -s?