Le 27/06/2013 17:08, Adrian Schröter a écrit :
Am Donnerstag, 27. Juni 2013, 17:05:40 schrieb Guillaume Gardet:
Le 27/06/2013 16:34, Adrian Schröter a écrit :
Am Donnerstag, 27. Juni 2013, 14:50:41 schrieb Guillaume Gardet:
Le 27/06/2013 14:46, Adrian Schröter a écrit :
Le 27/06/2013 14:02, Dirk Müller a écrit : > Hi Adrian, > >>> For reasons that I don't understand/remember, the OBS uses however >>> uname -m, so thats where the armv6l is coming from. >> it is not uname -m, it is manual setup decision. But it is the same >> as >> the kernel does it (it does not know armv7hl either). > Thats uname -m then. > >> for what? Just setting up a project link using >> openSUSE:Factory:ARM/standard (containing armv6l) would not work? I >> thought that is what you wanted the armv7 binaries inside for ? > We're not talking about factory but about 12.3. Maybe it needs too much work and we could just use a snapshot of Factory (once it will be ready)?
Am Donnerstag, 27. Juni 2013, 14:45:41 schrieb Guillaume Gardet: that one is there since yesterday, but a armv5 -> armv6 copy for 12.3 is running now as well. Ok, thanks. Any links, please? armv5 -> armv6 will be more usefull since I can get a working image on Raspberry Pi whereas armv7 stuff won't run. all armv5 rpms of devel:ARM:12.3:Contrib:RaspberryPi standard repo are copied to the armv6 one now. Would it be possible to create devel:ARM:12.3:Contrib:RaspberryPi/images armv6l? So that I can link to it? (because I have some problems to set up correctly my home images repo ATM). done.
Thanks. It seems OBS is quite slow ATM. armv6l does not show up yet: https://build.opensuse.org/project/show?project=devel%3AARM%3A12.3%3AContrib... whereas repo config show that armv6l is enabled for images. Or maybe there is a problem? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org