Bug 280182 - Wrong dbus-mingw4 path in python file dbus-1.4.10.py
Summary: Wrong dbus-mingw4 path in python file dbus-1.4.10.py
Status: RESOLVED DUPLICATE of bug 280187
Alias: None
Product: kde-windows
Classification: Unmaintained
Component: buildsystem (show other bugs)
Version: unspecified
Platform: Microsoft Windows Microsoft Windows
: NOR minor
Target Milestone: ---
Assignee: KDE-Windows
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-16 11:25 UTC by benu.e
Modified: 2012-02-22 22:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
This is the file that I quickfixed by adding -x86 to the path. I think this is NOT the right fix. (1.35 KB, text/plain)
2011-08-16 11:25 UTC, benu.e
Details

Note You need to log in before you can comment on or make changes to this bug.
Description benu.e 2011-08-16 11:25:46 UTC
Created attachment 62869 [details]
This is the file that I quickfixed by adding -x86 to the path. I think this is NOT the right fix.

Version:           unspecified (using Devel) 
OS:                MS Windows

The path for dbus at sourceforge has probably changed and the script tries to download
http://downloads.sourceforge.net/kde-windows/dbus-mingw4-1.4.10-bin.tar.bz2
causing a 404 error.
Looking up the path here
http://ftp.heanet.ie/mirrors/sourceforge/k/project/kd/kde-windows/dbus/1.4.10/
made me realize that the path should be
http://downloads.sourceforge.net/kde-windows/dbus-x86-mingw4-1.4.10-bin.tar.bz2

I could quickfix this for me but my fix does not work if it wants to download a dbus-mingw version prior to 1.4.10.

Reproducible: Always

Steps to Reproduce:
Create a new kde root folder and add your kdeenv variables.
Do emerge qt.

Actual Results:  
Error 404 Not found for dbus-mingw4 and the script crashes.

Expected Results:  
Correct download path should be in script.

I added my quickfix to this budreport. This worked for me as I wanted to continue installing.
Comment 1 Patrick Spendrin 2012-02-22 22:31:08 UTC

*** This bug has been marked as a duplicate of bug 280187 ***