From: Hoyt, D. <ho...@ll...> - 2011-11-08 19:08:29
|
Hi there, Here's a command I issued and the resulting error message: $ mingw-get --all-related source msys-vim mingw-get.exe: *** WARNING *** http://prdownloads.sourceforge.net/mingw/msysCORE-1.0.17-1-msys-1.0.17-src.tar?download: opened with unexpected status: code = 404 mingw-get.exe: *** WARNING *** please report this to the mingw-get maintainer mingw-get.exe: *** ERROR *** Get package: http://prdownloads.sourceforge.net/mingw/msysCORE-1.0.17-1-msys-1.0.17-src.tar?download: download failed http://prdownloads.sourceforge.net/mingw/libiconv-1.14-1-msys-1.0.17-src.tar.lzma?download 4.20 MB / 4.20 MB |================================================| 100% http://prdownloads.sourceforge.net/mingw/termcap-0.20050421_1-2-msys-1.0.13-src.tar.lzma?download 67.83 kB / 67.83 kB |================================================| 100% http://prdownloads.sourceforge.net/mingw/gettext-0.18.1.1-1-msys-1.0.17-src.tar.lzma?download 14.41 MB / 14.41 MB |================================================| 100% http://prdownloads.sourceforge.net/mingw/vim-7.3-2-msys-1.0.16-src.tar.lzma?download 6.68 MB / 6.68 MB |================================================| 100% As you can see, other package sources download fine, but msys core seems to be having problems. I issued the command again just to be sure that there wasn't some CDN issue - but it failed with the same error. Just wanted to bring this to your attention. |
From: Charles W. <cwi...@us...> - 2011-11-08 19:40:21
|
On 11/8/2011 2:08 PM, Hoyt, David wrote: > Here’s a command I issued and the resulting error message: > > $ mingw-get --all-related source msys-vim > > mingw-get.exe: *** WARNING *** > http://prdownloads.sourceforge.net/mingw/msysCORE-1.0.17-1-msys-1.0.17-src.tar?download: > opened with unexpected status: code = 404 > > mingw-get.exe: *** WARNING *** please report this to the mingw-get > maintainer > > mingw-get.exe: *** ERROR *** Get package: > http://prdownloads.sourceforge.net/mingw/msysCORE-1.0.17-1-msys-1.0.17-src.tar?download: > download failed This looks like another bug in the manifest. msys-core.xml SHOULD say this: <source tarname="msysCORE-%-msys-%-src.tar.%" /> <licence tarname="msysCORE-%-msys-%-lic.tar.%" /> (note the trailing .%) -- but instead it says this: <source tarname="msysCORE-%-msys-%-src.tar" /> <licence tarname="msysCORE-%-msys-%-lic.tar" /> this was a recent mingw-get requirement change, and I thought we updated all the affected manifests but looks like we missed a few: msys-core -- Cesar msys-bash -- me msys-mintty -- Andy Thanks for the report. -- Chuck |
From: Earnie <ea...@us...> - 2011-11-08 20:11:02
|
Charles Wilson wrote: > On 11/8/2011 2:08 PM, Hoyt, David wrote: >> Here’s a command I issued and the resulting error message: >> >> $ mingw-get --all-related source msys-vim >> >> mingw-get.exe: *** WARNING *** >> http://prdownloads.sourceforge.net/mingw/msysCORE-1.0.17-1-msys-1.0.17-src.tar?download: >> opened with unexpected status: code = 404 >> >> mingw-get.exe: *** WARNING *** please report this to the mingw-get >> maintainer >> >> mingw-get.exe: *** ERROR *** Get package: >> http://prdownloads.sourceforge.net/mingw/msysCORE-1.0.17-1-msys-1.0.17-src.tar?download: >> download failed > > This looks like another bug in the manifest. msys-core.xml SHOULD say this: > > <source tarname="msysCORE-%-msys-%-src.tar.%" /> > <licence tarname="msysCORE-%-msys-%-lic.tar.%" /> > It does in CVS; maybe it didn't make the FRS release. -- Earnie -- http://www.for-my-kids.com |
From: Keith M. <kei...@us...> - 2011-11-08 20:17:59
|
On 08/11/11 19:40, Charles Wilson wrote: > this was a recent mingw-get requirement change, and I thought we updated > all the affected manifests but looks like we missed a few: Well, I just blitzed the entire corpus with a sed regex substitution... > msys-core -- Cesar > msys-bash -- me > msys-mintty -- Andy ...so I guess these three didn't match for some reason, and I failed to notice. Or, the wild card sftp upload I followed up with choked on these three, and I failed to notice that. Apologies. > Thanks for the report. Seconded. -- Regards, Keith. |
From: Keith M. <kei...@us...> - 2011-11-08 20:26:01
|
On 08/11/11 20:10, Earnie wrote: >> This looks like another bug in the manifest. msys-core.xml SHOULD say this: >> >> <source tarname="msysCORE-%-msys-%-src.tar.%" /> >> <licence tarname="msysCORE-%-msys-%-lic.tar.%" /> > > It does in CVS; maybe it didn't make the FRS release. Which suggests that my sed regex worked, and it was the bulk sftp upload which choked. -- Regards, Keith. |
From: Keith M. <kei...@us...> - 2011-11-08 21:43:58
|
On 08/11/11 20:25, Keith Marshall wrote: > On 08/11/11 20:10, Earnie wrote: >>> This looks like another bug in the manifest. msys-core.xml SHOULD say this: >>> >>> <source tarname="msysCORE-%-msys-%-src.tar.%" /> >>> <licence tarname="msysCORE-%-msys-%-lic.tar.%" /> >> >> It does in CVS; maybe it didn't make the FRS release. > > Which suggests that my sed regex worked, and it was the bulk sftp upload > which choked. In fact, my own sandbox copies show that the sed substitution had been correctly applied in each of these three cases: >>> msys-core -- Cesar >>> msys-bash -- me >>> msys-mintty -- Andy I've pushed them to FRS again. -- Regards, Keith. |
From: Hoyt, D. <ho...@ll...> - 2011-11-08 21:49:09
|
> This looks like another bug in the manifest. These things happen to everyone. Thanks for looking into it so quickly -- it's much appreciated. Have the catalogs been updated then? > Thanks for the report. Happy to help in what little way I can. Everyone's hard work and long hours on the project is much appreciated -- please remember that and don't forget that your community supports all that you do! Cheers, - David |
From: Charles W. <cwi...@us...> - 2011-11-09 03:31:30
|
On 11/8/2011 4:49 PM, Hoyt, David wrote: > Have the catalogs been updated then? The three msys-* manifests with the "missing source" problem have been updated correctly, and have now had enough time to propagate to the various mirrors. I just now updated the mingw32-gettext.xml manifest to correct the missing dependencies on libstdc++ and libgomp. However, it may take some time for the updated version to propagate to the mirrors. Minutes to hours. -- Chuck |
From: Hoyt, D. <ho...@ll...> - 2011-11-09 17:14:40
|
> The three msys-* manifests with the "missing source" problem have been updated correctly ... Thank you very much for resolving that so quickly. Cheers, - David |
From: Keith M. <kei...@us...> - 2011-11-09 19:37:34
|
On 09/11/11 17:14, Hoyt, David wrote: >> The three msys-* manifests with the "missing source" problem have >> been updated correctly ... > > Thank you very much for resolving that so quickly. You're welcome. Having established that the three offending files were actually correct in my build sandbox, uploading them again was all that was required. -- Regards, Keith. |
From: Hoyt, D. <ho...@ll...> - 2011-11-10 02:02:51
|
> Having established that the three offending files were > actually correct in my build sandbox, uploading them again was all that > was required. I'm unsure if it's the mirror I've been assigned to or what -- but I haven't seen the update yet. I've updated my catalogs and re-run "mingw-get --all-related source msys-bash" but continue to get 404s. It says it's trying to download http://prdownloads.sourceforge.net/mingw/msysCORE-1.0.17-1-msys-1.0.17-src.tar?download and fails, but when I try "wget http://prdownloads.sourceforge.net/mingw/msysCORE-1.0.17-1-msys-1.0.17-src.tar.lzma?download" it works and downloads the file just fine. Any thoughts on what could be going on? Thanks, - David |
From: Charles W. <cwi...@us...> - 2011-11-10 03:50:01
|
On 11/9/2011 9:02 PM, Hoyt, David wrote: > I'm unsure if it's the mirror I've been assigned to or what -- but I > haven't seen the update yet. I've updated my catalogs and re-run > "mingw-get --all-related source msys-bash" but continue to get 404s. It > says it's trying to download > http://prdownloads.sourceforge.net/mingw/msysCORE-1.0.17-1-msys-1.0.17-src.tar?download > and fails, but when I try "wget > http://prdownloads.sourceforge.net/mingw/msysCORE-1.0.17-1-msys-1.0.17-src.tar.lzma?download" > it works and downloads the file just fine. Any thoughts on what could be > going on? Uhm, you didn't mention whether you did this or not, first: mingw-get update That (re)downloads the latest copy of the manifest files. THEN you can do mingw-get upgrade ... or whatever. -- Chuck |
From: Keith M. <kei...@us...> - 2011-11-10 18:29:26
|
On 10/11/11 03:49, Charles Wilson wrote: > On 11/9/2011 9:02 PM, Hoyt, David wrote: >> I'm unsure if it's the mirror I've been assigned to or what -- but >> I haven't seen the update yet. I've updated my catalogs >From this, I deduce that David most likely did do... >> and re-run "mingw-get --all-related source msys-bash" but continue >> to get 404s. > > Uhm, you didn't mention whether you did this or not, first: > > mingw-get update ...this. I guess I wasn't paying enough attention, when I repeated my upload attempt; I'm not allowed to do it! Neither is Chuck. Cesar (Strauss) and Chris (Sutcliffe), are you following this? We need YOU to fix these: - msys-bash.xml.lzma and msys-core.xml.lzma are mode 644, and owned by cstrauss; Cesar, will you please chmod them to 664. - msys-mintty.xml.lzma is mode 644, and owned by ir0nh34d; Chris, will you please perform similar honours for it. After doing this, please then update your own mingw-dist sandboxes, and upload fresh copies of your respective catalogues named above. -- Regards, Keith. |
From: Chris S. <ir0...@gm...> - 2011-11-10 21:30:56
|
On 10 November 2011 13:29, Keith Marshall wrote: > Cesar (Strauss) and Chris (Sutcliffe), are you following this? We need > YOU to fix these: > > - msys-mintty.xml.lzma is mode 644, and owned by ir0nh34d; Chris, > will you please perform similar honours for it. I'll take care of this tonight. I would also suggest validating the group as well. I've noticed weird and wonderful things if you upload directly (via sftp) vs. their web based UI. Cheers, Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d |
From: Chris S. <ir0...@gm...> - 2011-11-10 23:46:29
|
On 10 November 2011 16:30, Chris Sutcliffe wrote: > On 10 November 2011 13:29, Keith Marshall wrote: >> Cesar (Strauss) and Chris (Sutcliffe), are you following this? We need >> YOU to fix these: >> >> - msys-mintty.xml.lzma is mode 644, and owned by ir0nh34d; Chris, >> will you please perform similar honours for it. > > I'll take care of this tonight. I would also suggest validating the > group as well. I've noticed weird and wonderful things if you upload > directly (via sftp) vs. their web based UI. Fixed in FRS now. Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d |
From: Keith M. <kei...@us...> - 2011-11-15 20:04:28
|
On 10/11/11 23:46, Chris Sutcliffe wrote: > On 10 November 2011 16:30, Chris Sutcliffe wrote: >> On 10 November 2011 13:29, Keith Marshall wrote: >>> Cesar (Strauss) and Chris (Sutcliffe), are you following this? We need >>> YOU to fix these: >>> >>> - msys-mintty.xml.lzma is mode 644, and owned by ir0nh34d; Chris, >>> will you please perform similar honours for it. >> >> I'll take care of this tonight. I would also suggest validating the >> group as well. I've noticed weird and wonderful things if you upload >> directly (via sftp) vs. their web based UI. > > Fixed in FRS now. I guess you mean you adjusted the permissions, but neglected to replace the obsolete file in FRS -- we're still serving the incorrect version from 2011-07-31. -- Regards, Keith. |
From: Charles W. <cwi...@us...> - 2011-11-15 22:05:12
|
On 11/15/2011 4:07 PM, Keith Marshall wrote: > I've since found that the web interface allows me to steal ownership of > the file. Ah, that's good to know. I wonder how long that will last. -- Chuck |
From: Earnie <ea...@us...> - 2011-11-15 23:50:51
|
Charles Wilson wrote: > On 11/15/2011 4:07 PM, Keith Marshall wrote: >> I've since found that the web interface allows me to steal ownership of >> the file. > > Ah, that's good to know. I wonder how long that will last. They're now using Python services. They're slowly moving everyone to the new interface but some of the services such as the FRS are already using the new allura based SF. That being said allura is in beta status so changes are occurring weekly so who knows when it'll break. https://sourceforge.net/projects/allura/ -- Earnie -- https://sites.google.com/site/earnieboyd/ |
From: Hoyt, D. <ho...@ll...> - 2011-11-10 21:35:06
|
> From this, I deduce that David most likely did do... You're exactly right -- I certainly did a mingw-get update first. Thanks for taking such a close look at the issue and being so willing to resolve it. Cheers, - David |
From: Cesar S. <ces...@gm...> - 2011-11-11 02:27:59
|
On 11/10/2011 04:29 PM, Keith Marshall wrote: > - msys-bash.xml.lzma and msys-core.xml.lzma are mode 644, and owned > by cstrauss; Cesar, will you please chmod them to 664. Done. > After doing this, please then update your own mingw-dist sandboxes, and > upload fresh copies of your respective catalogues named above. Also done. Regards, Cesar |
From: Hoyt, D. <ho...@ll...> - 2011-11-14 22:10:54
|
> msys-mintty.xml.lzma is mode 644, and owned by ir0nh34d; Chris, > will you please perform similar honours for it. For anyone who cares, just thought I'd report that msys-mintty doesn't seem to be updated yet. msys-core and msys-bash are both working fine on my end (just updated each: mingw-get update && mingw-get --all-related source msys-core). Output: $ mingw-get --all-related source msys-mintty mingw-get.exe: *** WARNING *** http://prdownloads.sourceforge.net/mingw/mintty-1.0.1-1-msys-1.0.16-src.tar?download: opened with unexpected status: code = 404 mingw-get.exe: *** WARNING *** please report this to the mingw-get maintainer mingw-get.exe: *** ERROR *** Get package: http://prdownloads.sourceforge.net/mingw/mintty-1.0.1-1-msys-1.0.16-src.tar?download: download failed $ mingw-get --all-related licence msys-mintty mingw-get.exe: *** WARNING *** http://prdownloads.sourceforge.net/mingw/mintty-1.0.1-1-msys-1.0.16-lic.tar?download: opened with unexpected status: code = 404 mingw-get.exe: *** WARNING *** please report this to the mingw-get maintainer mingw-get.exe: *** ERROR *** Get package: http://prdownloads.sourceforge.net/mingw/mintty-1.0.1-1-msys-1.0.16-lic.tar?download: download failed Thanks, - David |
From: Hoyt, D. <ho...@ll...> - 2011-11-14 23:29:34
|
> ... msys-core and msys-bash are both working fine ... After creating a completely fresh env, it seems that bash still isn't working: mingw-get.exe: *** WARNING *** http://prdownloads.sourceforge.net/mingw/bash-3.1.17-4-msys-1.0.16-src.tar?download: opened with unexpected status: code = 404 mingw-get.exe: *** WARNING *** please report this to the mingw-get maintainer mingw-get.exe: *** ERROR *** Get package: http://prdownloads.sourceforge.net/mingw/bash-3.1.17-4-msys-1.0.16-src.tar?download: download failed mintty is still not working as per my previous post. gdb license is also having issues it seems: mingw-get.exe: *** WARNING *** http://prdownloads.sourceforge.net/mingw/gdb-7.3.1-1-mingw32-lic.tar.lzma?download: opened with unexpected status: code = 404 mingw-get.exe: *** WARNING *** please report this to the mingw-get maintainer mingw-get.exe: *** ERROR *** Get package: http://prdownloads.sourceforge.net/mingw/gdb-7.3.1-1-mingw32-lic.tar.lzma?download: download failed Everything else is fine. |
From: Keith M. <kei...@us...> - 2011-11-15 20:04:12
|
On 14/11/11 23:29, Hoyt, David wrote: > gdb license is also having issues it seems: > > mingw-get.exe: *** WARNING *** http://prdownloads.sourceforge.net/mingw/gdb-7.3.1-1-mingw32-lic.tar.lzma?download: opened with unexpected status: code = 404 > mingw-get.exe: *** WARNING *** please report this to the mingw-get maintainer > mingw-get.exe: *** ERROR *** Get package: http://prdownloads.sourceforge.net/mingw/gdb-7.3.1-1-mingw32-lic.tar.lzma?download: download failed You didn't show the command you issued, but I'm guessing: $ mingw-get licence --all-related gdb Without the "all-related" option, I can't reproduce this; gdb doesn't provide a -lic package, and the catalogue directs mingw-get to retrieve licence information from the -doc package instead: $ mingw-get licence gdb fixme:wininet:InternetAttemptConnect Stub mingw-get.exe: *** ERROR *** http://prdownloads.sourceforge.net/mingw/gdb-7.3.1-1-mingw32-doc.tar.lzma?download:cannot open URL mingw-get.exe: *** ERROR *** Get package: http://prdownloads.sourceforge.net/mingw/gdb-7.3.1-1-mingw32-doc.tar.lzma?download: download failed Yes, the download fails, but that's because I'm running without an internet connection; the host file has been correctly identified as gdb-7.3.1-1-mingw32-doc.tar.lzma, NOT gdb-7.3.1-1-mingw32-lic.tar.lzma as in your case. Notice: $ mingw-get licence --print-uris gdb http://prdownloads.sourceforge.net/mingw/gdb-7.3.1-1-mingw32-doc.tar.lzma?download is correct, but: $ mingw-get licence --print-uris --all-related gdb http://prdownloads.sourceforge.net/mingw/libiconv-1.14-2-mingw32-lic.tar.lzma?download http://prdownloads.sourceforge.net/mingw/gcc-4.6.1-2-mingw32-lic.tar.lzma?download http://prdownloads.sourceforge.net/mingw/gettext-0.18.1.1-2-mingw32-lic.tar.lzma?download http://prdownloads.sourceforge.net/mingw/expat-2.0.1-1-mingw32-lic.tar.gz?download http://prdownloads.sourceforge.net/mingw/gdb-7.3.1-1-mingw32-doc.tar.lzma?download http://prdownloads.sourceforge.net/mingw/gdb-7.3.1-1-mingw32-lic.tar.lzma?download adds the incorrect -lic association, while still correctly identifying the -doc association, and also adding the correct dependency references. So, what's going on here? 'mingw-get licence gdb' says "resolve the licence associations, for EVERY component of the gdb package"; that includes gdb-bin AND gdb-doc, (the only two components specified by the package maintainer, in this case). Now, gdb-bin has EXPLICIT per release licence associations, which resolve to the -doc component package; hence the correct licence association is identified. However, gdb-doc has no licence association at all, not even a generic per PACKAGE fallback; thus mingw-get generates an IMPLIED association, substituting -lic for the component field (-doc), resulting in the incorrect association in this case. This is NOT, as Chuck may have suggested, a bug in mingw-get: > That appears to be a bug in mingw-get. It seems to assume that all > licence elements will have the component value "-lic", but gdb doesn't. > It actually has per-release <licence/> and <source/> elements, and the > <licence/> element is actually the -doc component. No, mingw-get is behaving as intended. The bug is in mingw32-gdb.xml, which specifies NO licence association AT ALL for the gdb-doc component; this IMPLIES a STANDARD association to 'gdb-%-mingw32-%-lic.tar.%', but gdb does not conform to this standard; thus mingw32-gdb.xml needs to add an explicit (non-standard) licence association for its orphaned -doc component. I'll fix that later tonight. -- Regards, Keith. |
From: Keith M. <kei...@us...> - 2011-11-15 08:24:20
|
On 14/11/11 23:29, Hoyt, David wrote: >> ... msys-core and msys-bash are both working fine ... > After creating a completely fresh env, it seems that bash still isn't working: WJFFM. Did you remember to 'mingw-get update' first? $ rm -f $MINGW_ROOT/var/cache/mingw-get/source/* $ rm -f $MINGW_ROOT/var/lib/mingw-get/data/msys*.xml $ mingw-get update ... $ mingw-get source --down --all msys-bash fixme:wininet:InternetAttemptConnect Stub http://prdownloads.sourceforge.net/mingw/msysCORE-1.0.17-1-msys-1.0.17-src.tar.lzma?download 2.39 MB / 2.39 MB |================================================| 100% http://prdownloads.sourceforge.net/mingw/libiconv-1.14-1-msys-1.0.17-src.tar.lzma?download 4.20 MB / 4.20 MB |================================================| 100% http://prdownloads.sourceforge.net/mingw/gettext-0.18.1.1-1-msys-1.0.17-src.tar.lzma?download 14.41 MB / 14.41 MB |================================================| 100% http://prdownloads.sourceforge.net/mingw/coreutils-5.97-3-msys-1.0.13-src.tar.lzma?download 4.88 MB / 4.88 MB |================================================| 100% http://prdownloads.sourceforge.net/mingw/termcap-0.20050421_1-2-msys-1.0.13-src.tar.lzma?download 67.83 kB / 67.83 kB |================================================| 100% http://prdownloads.sourceforge.net/mingw/regex-1.20090805-2-msys-1.0.13-src.tar.lzma?download 337.37 kB / 337.37 kB |================================================| 100% http://prdownloads.sourceforge.net/mingw/bash-3.1.17-4-msys-1.0.16-src.tar.lzma?download 2.46 MB / 2.46 MB |================================================| 100% (The "fixme" is just noise from wine's wininet implementation). > mintty is still not working as per my previous post. Ack. > gdb license is also having issues it seems: I'll take a look. Thanks for the heads-up. -- Regards, Keith. |
From: Keith M. <kei...@us...> - 2011-11-15 21:12:39
|
On 15/11/11 08:24, Keith Marshall wrote: > On 14/11/11 23:29, Hoyt, David wrote: >> mintty is still not working as per my previous post. > > Ack. > >> gdb license is also having issues it seems: > > I'll take a look. Thanks for the heads-up. I've now uploaded corrections for both; should work properly after they've percolated to the mirrors. -- Regards, Keith. |