First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 181973
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Roy Marples (RETIRED) <uberlord@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Aaron Slunt <tonglebeak@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
remove_qt3_use.diff remove_qt3_use.diff patch Bernd Steinhauser 2007-06-18 09:09 0000 1.34 KB Details | Diff
rt2500-9999.ebuild rt2500-9999.ebuild text/plain Bernd Steinhauser 2007-06-18 18:31 0000 1.01 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 181973 depends on: Show dependency tree
Bug 181973 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-06-14 01:04 0000
The last version of the rt2500 driver listed in portage is feb 9th. It's been
over 3 months since an updated ebuild has been put into portage. I'm requesting
one of the following

1) An ebuild that downloads the snapshot from 6/13 (known to be working), or

2) A CVS ebuild that checks out the latest hourly cvs source and
compiles/installs (just like xxxx-9999 ebuilds out there).

Reproducible: Always

------- Comment #1 From Bernd Steinhauser 2007-06-17 13:20:26 0000 -------
An update would be good, since there have been some major changes (added SMP 
support, fixed a few major hang ups), but maybe this should depend on but
#174867
If you would like to upgrade yourself, create an overlay, put the ebuild named
"rt2500-1.1.0_pre2007020911" 
in it and rename it to
"rt2500-1.1.0_preDATE"
where you replace DATE with your version.
Then rename the tar.gz file that you downloaded to match that name. It should
work. 
You should ensure that you're not using the qt3 use flag, because that utility
has been removed from the rt2500 tree. It should be replaced by a gtk use flag,
but that would depend on bug #159900.

I'm working on a cvs ebuild, but I don't know when I've got the time to finish
it. ;)

------- Comment #2 From Aaron Slunt 2007-06-17 21:13:43 0000 -------
(In reply to comment #1)
> An update would be good, since there have been some major changes (added SMP 
> support, fixed a few major hang ups), but maybe this should depend on but
> #174867
> If you would like to upgrade yourself, create an overlay, put the ebuild named
> "rt2500-1.1.0_pre2007020911" 
> in it and rename it to
> "rt2500-1.1.0_preDATE"
> where you replace DATE with your version.
> Then rename the tar.gz file that you downloaded to match that name. It should
> work. 
> You should ensure that you're not using the qt3 use flag, because that utility
> has been removed from the rt2500 tree. It should be replaced by a gtk use flag,
> but that would depend on bug #159900.
> 
> I'm working on a cvs ebuild, but I don't know when I've got the time to finish
> it. ;)
> 

I've tried it, this is what I get. Any ideas?

>>> Emerging (7 of 11) net-wireless/rt2500-1.1.0_pre2007061716 to /
 * rt2500-1.1.0_pre2007061716.tar.gz MD5 ;-) ...                          [ ok
]
 * rt2500-1.1.0_pre2007061716.tar.gz RMD160 ;-) ...                       [ ok
]
 * rt2500-1.1.0_pre2007061716.tar.gz SHA1 ;-) ...                         [ ok
]
 * rt2500-1.1.0_pre2007061716.tar.gz SHA256 ;-) ...                       [ ok
]
 * rt2500-1.1.0_pre2007061716.tar.gz size ;-) ...                         [ ok
]
 * checking ebuild checksums ;-) ...                                      [ ok
]
 * checking auxfile checksums ;-) ...                                     [ ok
]
 * checking miscfile checksums ;-) ...                                    [ ok
]
 * checking rt2500-1.1.0_pre2007061716.tar.gz ;-) ...                     [ ok
]
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/2.6.21-gentoo-r2/build
 * Found sources for kernel version:
 *     2.6.21-gentoo-r2
 * Checking for suitable kernel configuration options...                  [ ok
]
>>> Unpacking source...
>>> Unpacking rt2500-1.1.0_pre2007061716.tar.gz to /var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007061716/work
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007061716 ...
/usr/portage/eclass/linux-mod.eclass: line 506: cd:
/var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007061716/work/rt2500-cvs-2007061716/Module:
No such file or directory
 * Preparing rt2500 module
make: Entering directory `/usr/src/linux-2.6.21-gentoo-r2'
scripts/Makefile.build:17:
/var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007061716/work/rt2500-cvs-2007061716/Module/Makefile:
No such file or directory
make[1]: *** No rule to make target
`/var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007061716/work/rt2500-cvs-2007061716/Module/Makefile'.
 Stop.
make: ***
[_module_/var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007061716/work/rt2500-cvs-2007061716/Module]
Error 2
make: Leaving directory `/usr/src/linux-2.6.21-gentoo-r2'

!!! ERROR: net-wireless/rt2500-1.1.0_pre2007061716 failed.
Call stack:
  ebuild.sh, line 1621:   Called dyn_compile
  ebuild.sh, line 973:   Called qa_call 'src_compile'
  ebuild.sh, line 44:   Called src_compile
  rt2500-1.1.0_pre2007061716.ebuild, line 38:   Called linux-mod_src_compile
  linux-mod.eclass, line 516:   Called die

!!! Unable to make  -C /usr/src/linux
M=/var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007061716/work/rt2500-cvs-2007061716/Module
modules.
!!! If you need support, post the topmost build error, and the call stack if
relevant.

------- Comment #3 From Bernd Steinhauser 2007-06-18 09:08:01 0000 -------
Are you sure, that you did take a current ebuild from the tree?
Did you check the tarball that it contains everything, that is needed?
It does happen sometimes, that they release corrupt tarballs.
Just try another one.

I've just checked it again, it does work for me, so shouldn't be a problem
considering the ebuild.

------- Comment #4 From Bernd Steinhauser 2007-06-18 09:09:16 0000 -------
Created an attachment (id=122396) [edit]
remove_qt3_use.diff

------- Comment #5 From Bernd Steinhauser 2007-06-18 18:31:15 0000 -------
Created an attachment (id=122431) [edit]
rt2500-9999.ebuild

rt2500 CVS ebuild.
Be aware, that this is a true CVS ebuild and not based on the hourly tarball.

------- Comment #6 From Aaron Slunt 2007-06-18 21:37:18 0000 -------
Just to let you know, I did screwup. I emerged 617 successfully yesterday and
have had no issues at all.

------- Comment #7 From Roy Marples (RETIRED) 2007-07-15 22:13:57 0000 -------
I've added a new CVS snapshot to fix this.
Sorry for the delay - the only machine I have left with an rt2500 card needed a
new PSU.

------- Comment #8 From Bernd Steinhauser 2007-07-16 11:08:25 0000 -------
(In reply to comment #7)
> I've added a new CVS snapshot to fix this.
> Sorry for the delay - the only machine I have left with an rt2500 card needed a
> new PSU.
> 

You forgot to remove the qt3 use flag. If you look into that tar file, you will
see, that they removed the Utility, so emerging it with qt3 enabled will fail.

------- Comment #9 From Roy Marples (RETIRED) 2007-07-16 11:23:53 0000 -------
(In reply to comment #8)
> You forgot to remove the qt3 use flag. If you look into that tar file, you will
> see, that they removed the Utility, so emerging it with qt3 enabled will fail.

Removed, thanks

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