First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 186181
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Java team <java@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Charly <gentoo@blueSpirit.la>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 186181 depends on: Show dependency tree
Bug 186181 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-07-22 07:27 0000
It's a really easy problem: Emerge tries to download JDom-b9 from
http://www.jdom.org/dist/source/jdom-b9.tar.gz. The correct URL is instead
http://www.jdom.org/dist/source/archive/jdom-b9.tar.gz.

Reason: The Jdom-team moves "old" version in the archive folder. So if you
write an ebuild for the current version, the URL
http://www.jdom.org/dist/source/jdom-XXX.tar.gz is correct - as long as there
is no better version available. In my opinion this will occur to the working
eBuild "dev-java/jdom-1.0-r2" in the near future too!

Reproducible: Always

Steps to Reproduce:
In my case

"emerge xdoclet"

but also 

"emerge -pv "=dev-java/jdom-1.0_beta9-r2""

Actual Results:  
>>> Emerging (1 of 6) dev-java/jdom-1.0_beta9-r2 to /
>>> Downloading 'http://pandemonium.tiscali.de/pub/gentoo/distfiles/jdom-b9.tar.gz'
--09:18:00--  http://pandemonium.tiscali.de/pub/gentoo/distfiles/jdom-b9.tar.gz
           => `/usr/portage/distfiles/jdom-b9.tar.gz'
Resolving pandemonium.tiscali.de... 195.52.219.14
Connecting to pandemonium.tiscali.de|195.52.219.14|:80... failed: Connection
refused.
>>> Downloading 'http://www.jdom.org/dist/source/jdom-b9.tar.gz'
--09:18:01--  http://www.jdom.org/dist/source/jdom-b9.tar.gz
           => `/usr/portage/distfiles/jdom-b9.tar.gz'
Resolving www.jdom.org... 65.212.180.182
Connecting to www.jdom.org|65.212.180.182|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
09:18:01 ERROR 404: Not Found.

!!! Couldn't download 'jdom-b9.tar.gz'. Aborting.

Expected Results:  
:-)

------- Comment #1 From Petteri Räty 2007-07-22 09:18:02 0000 -------
Well you should be able to fetch this stuff from the mirrors just fine.

pena jdom # devebuild jdom-1.0_beta9-r2.ebuild clean unpack
depend:  /usr/portage/dev-java/jdom/jdom-1.0_beta9-r2.ebuild
>>> Downloading 'http://trumpetti.atm.tut.fi/gentoo/distfiles/jdom-b9.tar.gz'
--12:17:11--  http://trumpetti.atm.tut.fi/gentoo/distfiles/jdom-b9.tar.gz
           => `/var/distfiles/jdom-b9.tar.gz'
Resolving trumpetti.atm.tut.fi... 130.230.54.100
Connecting to trumpetti.atm.tut.fi|130.230.54.100|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3,417,274 (3.3M) [application/x-tar]

100%[============================================================================================================================================================>]
3,417,274      9.24M/s

12:17:12 (9.24 MB/s) - `/var/distfiles/jdom-b9.tar.gz' saved [3417274/3417274]

But of course it is preferred to keep the urls up2date.

------- Comment #2 From Petteri Räty 2007-07-22 09:21:25 0000 -------
It would be better for upstream to put the files into archive from day 1 so
that we wouldn't have to update SRC_URI. It would be great if you would take
the time to report this upstream. In the meanwhile I update SRC_URI for beta9
and beta10.

First Last Prev Next    No search results available      Search page      Enter new bug