待辦事項 #38940

MinGW update errors report

啟用日期: 2019-02-07 08:50 最後更新: 2019-03-31 07:00

回報者:
負責人:
(無)
類型:
狀態:
開啟
元件:
里程碑:
(無)
優先權:
5 - 中
嚴重程度:
5 - 中
處理結果:
檔案:
Vote
Score: 0
No votes
0.0% (0/0)
0.0% (0/0)

細節

I am having issues updating to v8.2 for some packages some missing packages...

here is the update report for missing or issues..


upgrade: gcc-core-4.8.2-2-mingw32-dev.tar.lzma
 removing release gcc-core-4.8.2-mingw32-dev.tar.meta
mingw-get-gui: *** ERROR *** gcc-core-4.8.2-mingw32-dev.tar.meta: invalid manifest; no references
 installing gcc-core-4.8.2-2-mingw32-dev.tar.lzma
upgrade: gcc-c++-4.8.2-2-mingw32-dev.tar.meta
 removing release gcc-c++-4.8.2-mingw32-dev.tar.meta
mingw-get-gui: *** ERROR *** gcc-c++-4.8.2-mingw32-dev.tar.meta: invalid manifest; no references
 installing gcc-c++-4.8.2-2-mingw32-dev.tar.meta
upgrade: gcc-c++-4.8.1-5-mingw32-doc.tar.lzma
mingw-get-gui: *** WARNING *** not removing installed release
mingw-get-gui: *** WARNING *** gcc-c++-4.8.1-4-mingw32-doc.tar.lzma is still installed
mingw-get-gui: *** ERROR *** required package file is not available
mingw-get-gui: *** ERROR *** cannot upgrade to gcc-c++-4.8.1-5-mingw32-doc.tar.lzma
mingw-get-gui: *** ERROR *** due to previous download failure

plus the zlib libz dev package had a overwrite error.. and wouldn't force an overwrite... had to do it manually...

there were other error popups when I used "Mark all upgrades" option...

here is a link to screenshot(s) in a zip archive https://www.dropbox.com/s/716k9oq82n6nfcc/MinGW_screenshots.zip?dl=0

Ticket History (3/12 Histories)

2019-02-07 08:50 Updated by: melchiorgaspar
  • New Ticket "MinGW update errors report" created
2019-02-07 08:52 Updated by: melchiorgaspar
  • Details Updated
2019-02-08 07:19 Updated by: keith
  • 負責人 Update from (無) to keith
  • 元件 Update from OTHER to INSTALLER
評語

Reply To melchiorgaspar

I am having issues updating to v8.2 for some packages some missing packages...

To help me to help you, you need to be much more forthcoming about the details of your system/problem; (screenshots posted on dropbox do not suffice; you must include all necessary information right here):

  • What version of Windows are you running?
  • What version of mingw-get?
  • Where does your repository uri (specified in $MINGW_ROOT/var/lib/mingw-get/data/profile.xml) point?
2019-02-08 07:25 Updated by: melchiorgaspar
評語

I'm running Windows 7 ULTIMATE x64 mingw-get version 0.6.3-pre-20170905-1 <repository uri="http://osdn.net/dl/mingw/%F.xml.lzma">

my system specs, CPUz report: https://valid.x86.fr/qv6an5

2019-02-08 08:07 Updated by: keith
  • 負責人 Update from keith to (無)
評語

Reply To melchiorgaspar

upgrade: gcc-c++-4.8.1-5-mingw32-doc.tar.lzma
mingw-get-gui: *** WARNING *** not removing installed release
mingw-get-gui: *** WARNING *** gcc-c++-4.8.1-4-mingw32-doc.tar.lzma is still installed
mingw-get-gui: *** ERROR *** required package file is not available
mingw-get-gui: *** ERROR *** cannot upgrade to gcc-c++-4.8.1-5-mingw32-doc.tar.lzma
mingw-get-gui: *** ERROR *** due to previous download failure

Thanks. I can reproduce this; it's caused by a missing <download tarname="none" /> attribute, on the gcc-c++-4.8.1-5-doc component package spec. Now fixed, (but leave about an hour, for propagation to the OSDN mirrors).

2019-02-08 18:35 Updated by: keith
  • Details Updated
評語

Reply To melchiorgaspar

I'm running Windows 7 ULTIMATE x64
mingw-get version 0.6.3-pre-20170905-1
<repository uri="http://osdn.net/dl/mingw/%F.xml.lzma">

That looks okay; I assume that you know that MinGW is 32-bit, in spite of your 64-bit host.

my system specs, CPUz report: https://valid.x86.fr/qv6an5

And again, here you are pointing me to off-site information, which may not be persistent. If you think it may be important, you need to attach it to the ticket; I am not going to chase off-site links.

2019-02-08 19:36 Updated by: keith
評語

Reply To melchiorgaspar

upgrade: gcc-core-4.8.2-2-mingw32-dev.tar.lzma
 removing release gcc-core-4.8.2-mingw32-dev.tar.meta
mingw-get-gui: *** ERROR *** gcc-core-4.8.2-mingw32-dev.tar.meta: invalid manifest; no references
 installing gcc-core-4.8.2-2-mingw32-dev.tar.lzma
upgrade: gcc-c++-4.8.2-2-mingw32-dev.tar.meta
 removing release gcc-c++-4.8.2-mingw32-dev.tar.meta
mingw-get-gui: *** ERROR *** gcc-c++-4.8.2-mingw32-dev.tar.meta: invalid manifest; no references
 installing gcc-c++-4.8.2-2-mingw32-dev.tar.meta
Seriously? You still have remnants of this dysfunctional relic installed?

I am unable to reproduce this, but then, I expunged all traces of GCC-4.8.2, (and, in particular, gcc-4.8.2-dev — the dysfunctional component), years ago. I don't know why this is failing — perhaps you really do have corrupt manifests, but without seeing them, I cannot say for sure. Furthermore, since I cannot reproduce the problem, I cannot investigate possible causes.

I do observe that installation of the upgraded packages appeared to complete, without error. Can you now remove them? (You really don't want to keep them around any longer). If you can remove them, do they leave any artefacts which interfere with installation of the GCC-8.2.0 package set? (The dev components were an aberration, introduced with GCC-4.8.1 — we want to get rid of all references to them, ASAP).

2019-02-08 19:43 Updated by: melchiorgaspar
評語

Reply To keith

Reply To melchiorgaspar

I'm running Windows 7 ULTIMATE x64
mingw-get version 0.6.3-pre-20170905-1
<repository uri="http://osdn.net/dl/mingw/%F.xml.lzma">

That looks okay; I assume that you know that MinGW is 32-bit, in spite of your 64-bit host.

my system specs, CPUz report: https://valid.x86.fr/qv6an5

And again, here you are pointing me to off-site information, which may not be persistent. If you think it may be important, you need to attach it to the ticket; I am not going to chase off-site links.

yes I know I MinGW is 32bit.... CPUz reports remain up forever... as far as I know... and it was easier they trying to copy and paste all my system specs here..

2019-02-08 19:44 Updated by: melchiorgaspar
評語

"dysfunctional relic" I will see what I can do about it... I haven't kept up to date much with MinGW... I don't compile much these days

Its not showing me anything newer then v4.8.2-x

mingw32-gcc-dev 4.8.2-2 installed and repo same for g++-dev

(Edited, 2019-02-08 19:53 Updated by: melchiorgaspar)
2019-02-09 03:54 Updated by: keith
評語

Reply To melchiorgaspar

plus the zlib libz dev package had a overwrite error.. and wouldn't force an overwrite... had to do it manually...

If you installed any associated files "behind mingw-get's back", then this is expected, and by design. The rationale is that mingw-get has no way of knowing whence an existing file, which it wants to install but doesn't own, may have come. It doesn't want to blindly overwrite something which may be important to you, and may differ in functionality from the version it provides. On the horns of this dilemma, it does the only sane thing it can — it tells you there is a potential conflict, and leaves it to you to decide how it should be resolved. If you do want mingw-get to take ownership, then you must manually delete the conflicting files, and then "mingw-get install --reinstall ..." the owning package.

2019-02-09 04:21 Updated by: melchiorgaspar
評語

I manually took care of zlib...

2019-03-31 07:00 Updated by: keith
評語

Reply To melchiorgaspar

Its not showing me anything newer then v4.8.2-x: mingw32-gcc-dev 4.8.2-2 installed and repo; same for g++-dev

Are you referring just to the "dev" component, here? If that's the case, then it is correct — there is no "dev" component for any GCC release after 4.8.2. Even for GCC-4.8.2, each of those "dev" components is nothing more than an empty meta-package — they serve no purpose, other than to clear out any residual garbage, which may have been inherited from a prior GCC-4.8.1 release, and which may interfere with an upgrade to a future release, (including GCC-4.8.2). IIRC, if you had bothered to read the package description, it tells you this; it also states that you may safely remove this useless meta-package, after it is installed as an upgrade dependency — you should heed this advice.

Attachment File List

No attachments

編輯

Please login to add comment to this ticket » 登入