From c.e.tower at gmail.com Fri Feb 7 18:04:42 2014 From: c.e.tower at gmail.com (Chick Tower) Date: Fri, 07 Feb 2014 13:04:42 -0500 Subject: [sbopkg-users] Faulty Source Downloads In-Reply-To: <8f1ad082f9357af9ead31f58df4a29bb@eumx.net> References: <8f1ad082f9357af9ead31f58df4a29bb@eumx.net> Message-ID: <52F5203A.8060109@gmail.com> On a few occasions, I've run sbopkg and found out that what it downloaded as the source file is actually some kind of HTML file, compressed. The compilation fails on the MD% sum check, of course. The links on slackbuilds.org seem fine. This seemed to have begun when I upgraded to version 0.37.0. Has anyone else run into this problem? -- Chick From chess at chessgriffin.com Fri Feb 7 18:31:56 2014 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 07 Feb 2014 13:31:56 -0500 Subject: [sbopkg-users] Faulty Source Downloads In-Reply-To: <52F5203A.8060109@gmail.com> References: <8f1ad082f9357af9ead31f58df4a29bb@eumx.net> <52F5203A.8060109@gmail.com> Message-ID: On 07.02.2014 13:04, Chick Tower wrote: > On a few occasions, I've run sbopkg and found out that what it > downloaded as the source file is actually some kind of HTML file, > compressed. The compilation fails on the MD% sum check, of course. > The links on slackbuilds.org seem fine. This seemed to have begun > when I upgraded to version 0.37.0. Has anyone else run into this > problem? I have not seen this recently, but in the past some of source downloads have had issues because of wonky redirects, or spaces in filenames, or stupid things like that. Can you provide one or two examples of ones that have not worked for you? Thanks! -- Chess Griffin From c.e.tower at gmail.com Fri Feb 7 18:50:04 2014 From: c.e.tower at gmail.com (Chick Tower) Date: Fri, 07 Feb 2014 13:50:04 -0500 Subject: [sbopkg-users] Faulty Source Downloads In-Reply-To: References: <8f1ad082f9357af9ead31f58df4a29bb@eumx.net> <52F5203A.8060109@gmail.com> Message-ID: <52F52ADC.1000500@gmail.com> On 02/07/2014 01:31 PM, Chess Griffin wrote: > On 07.02.2014 13:04, Chick Tower wrote: >> On a few occasions, I've run sbopkg and found out that what it >> downloaded as the source file is actually some kind of HTML file, >> compressed. The compilation fails on the MD% sum check, of course. >> The links on slackbuilds.org seem fine. This seemed to have begun >> when I upgraded to version 0.37.0. Has anyone else run into this >> problem? > > I have not seen this recently, but in the past some of source downloads > have had issues because of wonky redirects, or spaces in filenames, or > stupid things like that. > > Can you provide one or two examples of ones that have not worked for you? > > Thanks! > I think there have been others, but I don't recall them now. I know my downloads of pygame and libofx are the wrong files. They both have dates of 13Jan2014 in /var/cache/sbopkg. If you like, I can attach them to an e-mail to you. I just now downloaded libofx by clicking on the link on its slackbuilds.org page. I haven't tried compiling it again, but it's 1.5MB in size now, rather than the 6+KB it was. Thanks for the quick response! -- Chick From c.e.tower at gmail.com Sat Feb 8 02:39:05 2014 From: c.e.tower at gmail.com (Chick Tower) Date: Fri, 07 Feb 2014 21:39:05 -0500 Subject: [sbopkg-users] Faulty Source Downloads In-Reply-To: References: <8f1ad082f9357af9ead31f58df4a29bb@eumx.net> <52F5203A.8060109@gmail.com> Message-ID: <52F598C9.9090701@gmail.com> On 02/07/2014 01:31 PM, Chess Griffin wrote: > I have not seen this recently, but in the past some of source downloads > have had issues because of wonky redirects, or spaces in filenames, or > stupid things like that. > > Can you provide one or two examples of ones that have not worked for you? > > Thanks! > I think I see what happened. The file that is named for the pygame source file is actually a "welcome" screen from one of the libraries I frequent, spelling out its rules for use of its wireless services. It usually appears the first time I try to use a web browser to visit a site. Does sbopkg use HTTP to download files? It appears so, and that it accepts the library's initial page as the file it requested. I suppose most of you use sbopkg from home and don't run into this. As a workaround, I'll try to remember to use a web browser before running sbopkg, thereby loading the initial library page in the web browser rather than letting sbopkg read it. -- Chick