Why do you think it only supports 32bit? It's a noarch package, which means not dependant on architecture, which in turn usually implies it does not contain any binaries.
noarch packages are a little bit special, as they look like they are contained in i586 and x86_64 repos, or are sometimes installed from i586 repo on x86_64 system,
but they are hardlinked in the repos - it does not matter from which repo it is installed, it's the same package for both.
- Code: Select all
┌─[doktor5000@Mageia5]─[20:30:48]─[~]
└──╼ urpmq --sources task-kde4-devel
ftp://ftp.snt.utwente.nl/pub/os/linux/mageia/distrib/5/x86_64/media/core/release/task-kde4-devel-4.14.3-2.mga5.noarch.rpm
ftp://ftp.snt.utwente.nl/pub/os/linux/mageia/distrib/5/i586/media/core/release/task-kde4-devel-4.14.3-2.mga5.noarch.rpm
And yes it does not list any files because it's an empty package, it only consists of requires. They can be queried like all packages:
- Code: Select all
┌─[doktor5000@Mageia5]─[20:30:41]─[~]
└──╼ urpmq --requires task-kde4-devel
--requires behaviour changed, use --requires-recursive to get the old behaviour
kde-dev-scripts
kde4-config-file
kdebase4-devel[>= 1:4.14.3]
kdebase4-workspace-devel[>= 2:4.11.14]
kdelibs4-devel[>= 2:4.14.3]
kdepimlibs4-devel[>= 2:4.14.3]
task-c++-devel
task-kde4