Re: [Slackbuilds-users] screenfetch could not build
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've never implied anything like that. I'm just asking for admin to leave trace in tte changelog if it exists embedded in the SlackBuild itself. If someone can fix the version in the script I guess he can, at the same expense, write 4 or 5 words which state that he changed it. That takes several seconds. While i do agree that documentation is important, unfortunately in this case, i can't promise anything. One of the reason why we use GIT is because it can track all the changes of the code from initial submission to the latest version. Visit http://slackbuilds.org/cgit/slackbuilds and enter your package name and you can see the history. Writing 4-5 words might be a simple thing, but that only applies to one package, while we have to deal with like +/- 70-100 submissions / week. We do this work on our free time, so our main focus is to make sure the scripts work. If the maintainer wishes to make a self-documentation, that's fine. I have seen some other maintainer do the same thing and it's a nice thing to see, but that's just not our main priority. This is my personal opinion though. Other admins might have different opinion about this. - -- Willy Sudiarto Raharjo -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlTOcOgACgkQiHuDdNczM4F8VACbBBjJwnQujMPpnQP5LXEJlYdM uS0An0KaFg1VRrJVfes2dcOgXieyEDxz =oaW0 -END PGP SIGNATURE- ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
I don't agree. When SBo admins make changes whithout informing the maintainer, it's often not really obvious that changes are made to the code. Even if you notice, you can't be sure of a kind of changes that were made without looking at the log. And why would you look at the log if you are sure that no changes are made by the information you currently have. It's much easier to state the changes somewhere obvious then searching through the logs after every SBo update. I ask for them to document it when they change things whithout my knowledge (or as it happened several times before whithout asking) so I am aware of that when making future changes to the scripts. That's not much. And it's polite thing to do. Bojan. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
On Sat, Jan 31, 2015 at 08:38:41PM +0100, Bojan Popovic wrote: It's much easier to state the changes somewhere obvious then searching through the logs after every SBo update. I ask for them to document it when they change things whithout my knowledge (or as it happened several times before whithout asking) so I am aware of that when making future changes to the scripts. That's not much. And it's polite thing to do. I think the burden on admins is high enough and Willy has been doing an amazing job at keeping the pending queue empty. Contacting a maintainer after modifying anything would take too much effort and documenting any changes in the script inflates it for no reason (the git log already does this quite well). I personally maintain a local git repo for any SlackBuilds I maintain, and before making any changes for future submission I just download the SlackBuild's tarball from SBo and diff the files to see upstream changes. This takes under a minute for the maintainer and lets the admins continue on as they have been without any additional effort. I really don't see a problem with things as they are... ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
Ok, thanx. But I need to ask you a tiny favor. I try to keep a small changelog on the top of the script. Could you add the line about the change. And increase the version in the comments to 1.5. This is the current log: # ChangeLog # 1.0 23-DEC-2012 Added # 1.1 08-JUL-2013 Updated to a new upstream ver. 3.0.5. Fixes Slack64 # detection. # 1.2 06-DEC-2013 Updated to a new upstream ver. 3.2.2. # 1.3 24-JUL-2014 Updated to a new upstream ver. 3.5.0. # 1.4 07-DEC-2014 Updated to a new upstream ver. 3.6.5 Just add the following line: # 1.5 31-JAN-2015 Added a source alternative (willysr) Bojan. On Sat, 31 Jan 2015 08:05:59 +0700 Willy Sudiarto Raharjo will...@slackbuilds.org wrote: ah you are right i already have the other source inside the slackbuilds directory i have pushed a fix for this in my branch Thanks ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 But I need to ask you a tiny favor. I try to keep a small changelog on the top of the script. Could you add the line about the change. And increase the version in the comments to 1.5. This is the current log: # ChangeLog # 1.023-DEC-2012 Added # 1.1 08-JUL-2013 Updated to a new upstream ver. 3.0.5. Fixes Slack64 # detection. # 1.2 06-DEC-2013 Updated to a new upstream ver. 3.2.2. # 1.3 24-JUL-2014 Updated to a new upstream ver. 3.5.0. # 1.4 07-DEC-2014 Updated to a new upstream ver. 3.6.5 Just add the following line: # 1.5 31-JAN-2015 Added a source alternative (willysr) It's kinda too late for that as i have pushed public update this morning you might want to add that in your next update in the future - -- Willy Sudiarto Raharjo -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlTMy5QACgkQiHuDdNczM4Fn2gCfUNnt8DhaIGYOk7aPkcoM/q0Q bt4AnA1mmr6KifNEE+pqnjXb/uWPAULf =FCzL -END PGP SIGNATURE- ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
I don't think it's really late. I can make the change too, but I'll have to go through the upload form on the site. As the end result is the same, might be better if you do it. :) If you're hesistant, never mind. I'll just make the change myself and upload it later today. Just seems like extra work both me and you (someone needs to check the contents of the uploaded tarball). Bojan. On Sat, 31 Jan 2015 19:33:24 +0700 Willy Sudiarto Raharjo will...@slackbuilds.org wrote: It's kinda too late for that as i have pushed public update this morning you might want to add that in your next update in the future ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
OK, I found the reason. I set wget to have --content-disposition on by default, which causing downloaded file to be named as screenFetch-3.6.5.tar.gz with the download link in the info file. On Fri, Jan 30, 2015 at 11:09 AM, Bojan Popovic bo...@mycity.rs wrote: Hi. Did you change the script by hand? The archive name is different from the one in the current SBo script: Found screenFetch-3.6.5.tar.gz in /var/cache/sbopkg. This also looks suspicious: The reason is that the archive file name is screenFetch-3.6.5.tar.gz, but script is looking for screenfetch-3.6.5.tar.gz and failed. If you did, 3.6.5 is already available on SBo. Just update your local SBo repo (sbopkg -r). Anyway, I did a quick build test. Better sure than sorry. Everything is ok on my end. Bojan (the maintainer). ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ -- Qun-Ying ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
Interesting. I will look at that the next upload. I have never used that option before. I will need to RTFM on it. Thanx for reporting. Bojan. On Fri, 30 Jan 2015 12:56:25 -0800 Qun-Ying zhu.quny...@gmail.com wrote: OK, I found the reason. I set wget to have --content-disposition on by default, which causing downloaded file to be named as screenFetch-3.6.5.tar.gz with the download link in the info file. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] screenfetch could not build
The latest screenfetch could not build. Found screenFetch-3.6.5.tar.gz in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for screenFetch-3.6.5.tar.gz ... OK Building package for screenfetch... tar: /var/lib/sbopkg/SBo/14.1/desktop/screenfetch/screenfetch-3.6.5.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: /var/lib/sbopkg/SBo/14.1/desktop/screenfetch/v3.6.5.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now The reason is that the archive file name is screenFetch-3.6.5.tar.gz, but script is looking for screenfetch-3.6.5.tar.gz and failed. -- Qun-Ying ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
Hi. Did you change the script by hand? The archive name is different from the one in the current SBo script: Found screenFetch-3.6.5.tar.gz in /var/cache/sbopkg. This also looks suspicious: The reason is that the archive file name is screenFetch-3.6.5.tar.gz, but script is looking for screenfetch-3.6.5.tar.gz and failed. If you did, 3.6.5 is already available on SBo. Just update your local SBo repo (sbopkg -r). Anyway, I did a quick build test. Better sure than sorry. Everything is ok on my end. Bojan (the maintainer). ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It is a mysteryy why it works on your box, as you also got the error: root@SBo64:/home/willysr/ slackbuilds/desktop/screenfetch$ sh screenfetch.SlackBuild tar: /home/willysr/slackbuilds/desktop/screenfetch/screenfetch-3.6.5.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now ah you are right i already have the other source inside the slackbuilds directory i have pushed a fix for this in my branch Thanks - -- Willy Sudiarto Raharjo -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlTMKncACgkQiHuDdNczM4GOUgCgmL99aKs9c+fjHS1vN7qVPRSA gJAAn0SHd9Rywy/1rfj5TcHWy/tqH5oJ =2Awi -END PGP SIGNATURE- ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
Well, it should match. Github tarballs have a form of the second one. The first one is the old source tarball name format. So, in any case, problem seem to be on your end. Bojan. On Fri, 30 Jan 2015 16:52:38 -0800 Qun-Ying zhu.quny...@gmail.com wrote: Please take a look at the script: http://slackbuilds.org/cgit/slackbuilds/tree/desktop/screenfetch/screenfetch.SlackBuild?h=willysr At line 53: tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf $CWD/v$VERSION.tar.gz It will not match the download filename, and hence the script should exit. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
Anyway if you don't solve the problem, there is an easy manual solution. Screenfetch is simply a shell script. Just download it, make it executable and put in your path. You can get the latest git version here: http://git.silverirc.com/cgit.cgi/screenfetch.git/plain/screenfetch-dev Cheers, Bojan. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
Thanks, I already have it built by modifying the build script. My point was to bring attention to you and get the script updated, so that other people have that wget option set will not encounter the same error as me. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OK, I found the reason. I set wget to have --content-disposition on by default, which causing downloaded file to be named as screenFetch-3.6.5.tar.gz with the download link in the info file. I tried to recreate your situation with --content-disposition and it still works willysr@SBo64:~/slackbuilds/desktop/screenfetch$ wget - --content-disposition $DOWNLOAD - --2015-01-31 07:09:37-- https://github.com/KittyKatt/screenFetch/archive/v3.6.5.tar.gz Resolving github.com (github.com)... 192.30.252.129 Connecting to github.com (github.com)|192.30.252.129|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://codeload.github.com/KittyKatt/screenFetch/tar.gz/v3.6.5 [following] - --2015-01-31 07:09:38-- https://codeload.github.com/KittyKatt/screenFetch/tar.gz/v3.6.5 Resolving codeload.github.com (codeload.github.com)... 192.30.252.145 Connecting to codeload.github.com (codeload.github.com)|192.30.252.145|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 54153 (53K) [application/x-gzip] Saving to: ‘screenFetch-3.6.5.tar.gz’ 100%[===] 54,153 84.8KB/s in 0.6s 2015-01-31 07:09:40 (84.8 KB/s) - ‘screenFetch-3.6.5.tar.gz’ saved [54153/54153] willysr@SBo64:~/slackbuilds/desktop/screenfetch$ su Password: root@SBo64:/home/willysr/slackbuilds/desktop/screenfetch$ sh screenfetch.SlackBuild tar: /home/willysr/slackbuilds/desktop/screenfetch/screenfetch-3.6.5.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now screenFetch-3.6.5/ screenFetch-3.6.5/CHANGELOG screenFetch-3.6.5/COPYING screenFetch-3.6.5/README.mkdn screenFetch-3.6.5/TODO screenFetch-3.6.5/screenfetch-dev screenFetch-3.6.5/screenfetch.1 Slackware package maker, version 3.14159. Searching for symbolic links: No symbolic links were found, so we won't make an installation script. You can make your own later in ./install/doinst.sh and rebuild the package if you like. This next step is optional - you can set the directories in your package to some sane permissions. If any of the directories in your package have special permissions, then DO NOT reset them here! Would you like to reset all directory permissions to 755 (drwxr-xr-x) and directory ownerships to root.root ([y]es, [n]o)? n Creating Slackware package: /tmp/screenfetch-3.6.5-noarch-1_SBo.tgz ./ install/ install/slack-desc usr/ usr/bin/ usr/bin/screenfetch usr/doc/ usr/doc/screenfetch-3.6.5/ usr/doc/screenfetch-3.6.5/TODO usr/doc/screenfetch-3.6.5/CHANGELOG usr/doc/screenfetch-3.6.5/README.mkdn usr/doc/screenfetch-3.6.5/COPYING Slackware package /tmp/screenfetch-3.6.5-noarch-1_SBo.tgz created. - -- Willy Sudiarto Raharjo -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlTMHdEACgkQiHuDdNczM4EGewCfURlcFqXRB5Bwf2wcoBj523d1 c/IAoJW1HHyohQZ5fWq7GjOuNkYTqEnN =BT3z -END PGP SIGNATURE- ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
It is a mysteryy why it works on your box, as you also got the error: root@SBo64:/home/willysr/ slackbuilds/desktop/screenfetch$ sh screenfetch.SlackBuild tar: /home/willysr/slackbuilds/desktop/screenfetch/screenfetch-3.6.5.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now On Fri, Jan 30, 2015 at 4:12 PM, Willy Sudiarto Raharjo will...@slackbuilds.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OK, I found the reason. I set wget to have --content-disposition on by default, which causing downloaded file to be named as screenFetch-3.6.5.tar.gz with the download link in the info file. I tried to recreate your situation with --content-disposition and it still works willysr@SBo64:~/slackbuilds/desktop/screenfetch$ wget - --content-disposition $DOWNLOAD - --2015-01-31 07:09:37-- https://github.com/KittyKatt/screenFetch/archive/v3.6.5.tar.gz Resolving github.com (github.com)... 192.30.252.129 Connecting to github.com (github.com)|192.30.252.129|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://codeload.github.com/KittyKatt/screenFetch/tar.gz/v3.6.5 [following] - --2015-01-31 07:09:38-- https://codeload.github.com/KittyKatt/screenFetch/tar.gz/v3.6.5 Resolving codeload.github.com (codeload.github.com)... 192.30.252.145 Connecting to codeload.github.com (codeload.github.com)|192.30.252.145|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 54153 (53K) [application/x-gzip] Saving to: ‘screenFetch-3.6.5.tar.gz’ 100%[===] 54,153 84.8KB/s in 0.6s 2015-01-31 07:09:40 (84.8 KB/s) - ‘screenFetch-3.6.5.tar.gz’ saved [54153/54153] willysr@SBo64:~/slackbuilds/desktop/screenfetch$ su Password: root@SBo64:/home/willysr/slackbuilds/desktop/screenfetch$ sh screenfetch.SlackBuild tar: /home/willysr/slackbuilds/desktop/screenfetch/screenfetch-3.6.5.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now screenFetch-3.6.5/ screenFetch-3.6.5/CHANGELOG screenFetch-3.6.5/COPYING screenFetch-3.6.5/README.mkdn screenFetch-3.6.5/TODO screenFetch-3.6.5/screenfetch-dev screenFetch-3.6.5/screenfetch.1 Slackware package maker, version 3.14159. Searching for symbolic links: No symbolic links were found, so we won't make an installation script. You can make your own later in ./install/doinst.sh and rebuild the package if you like. This next step is optional - you can set the directories in your package to some sane permissions. If any of the directories in your package have special permissions, then DO NOT reset them here! Would you like to reset all directory permissions to 755 (drwxr-xr-x) and directory ownerships to root.root ([y]es, [n]o)? n Creating Slackware package: /tmp/screenfetch-3.6.5-noarch-1_SBo.tgz ./ install/ install/slack-desc usr/ usr/bin/ usr/bin/screenfetch usr/doc/ usr/doc/screenfetch-3.6.5/ usr/doc/screenfetch-3.6.5/TODO usr/doc/screenfetch-3.6.5/CHANGELOG usr/doc/screenfetch-3.6.5/README.mkdn usr/doc/screenfetch-3.6.5/COPYING Slackware package /tmp/screenfetch-3.6.5-noarch-1_SBo.tgz created. - -- Willy Sudiarto Raharjo -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlTMHdEACgkQiHuDdNczM4EGewCfURlcFqXRB5Bwf2wcoBj523d1 c/IAoJW1HHyohQZ5fWq7GjOuNkYTqEnN =BT3z -END PGP SIGNATURE- ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ -- Qun-Ying ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
Please take a look at the script: http://slackbuilds.org/cgit/slackbuilds/tree/desktop/screenfetch/screenfetch.SlackBuild?h=willysr At line 53: tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf $CWD/v$VERSION.tar.gz It will not match the download filename, and hence the script should exit. -- Qun-Ying ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
When using the --content-disposition with wget, it will be the same effect as you download the file from a browser. When you download it from a browser, it will save the file as screenFetch-3.6.5.tar.gz, that is how GitHub setup its download link. Wget by default only use the last part of the url as save filename, it maynot be the intended file name by web server. On Fri, Jan 30, 2015 at 4:46 PM, Bojan Popovic bo...@mycity.rs wrote: Well, it should match. Github tarballs have a form of the second one. The first one is the old source tarball name format. So, in any case, problem seem to be on your end. Bojan. -- Qun-Ying ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] screenfetch could not build
You can safely ignore that. The script containts something like: tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf $CWD/v$VERSION.tar.gz This is to allow packaging from both classical tarballs (screenfetch-3.6.5.tar.gz) and github tarballs (v3.6.5.tar.gz). This can be redirected to /dev/null. There might be reason why I didn't but can't remember right now as that error message is harmless. Or maybe it was just an ommision. I will fix that in the next update. If Willy didn't have any problems, I guess the problem is on your end. Bojan. On Fri, 30 Jan 2015 16:45:30 -0800 Qun-Ying zhu.quny...@gmail.com wrote: It is a mysteryy why it works on your box, as you also got the error: root@SBo64:/home/willysr/ slackbuilds/desktop/screenfetch$ sh screenfetch.SlackBuild tar: /home/willysr/slackbuilds/desktop/screenfetch/screenfetch-3.6.5.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
