corresponding binary package to source package missing

Bug #191988 reported by StefanPotyra
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Undecided
Unassigned

Bug Description

Hi,

I just wanted to find out the exact version of the binary package nvidia-glx/nvidia-glx-new, that is a byproduct of linux-restricted-modules-someversion of the latest upload. Since I'm lazy (my mirror is behind a day or so, and doesn't know anything about -8.20 yet), I looked at this page:

https://launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/2.6.24.9-8.20

where nvidia-glx, nvidia-glx-new (probably more), are missing, while apt-cache showsrc nvidia-glx tells me that l-r-m is indeed the corresponding source package.

Oh, and there must be some black magic going on in the l-r-m source package to produce these binaries (of which after looking 10 minutes at it, I still only have a vague assumption of what's going on there).

Cheers,
      Stefan.

Tags: lp-soyuz
Revision history for this message
William Grant (wgrant) wrote :

That page is correct. Only sparc, lpia, powerpc and ia64 built and were accepted; i386 failed, and amd64 is in NEW.

Changed in soyuz:
status: New → Invalid
Revision history for this message
StefanPotyra (sistpoty) wrote :

indeed, now the page has filled (probably because amd64 left new).. thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.