January 2014 - openSUSE Packaging - openSUSE Mailing Lists

Re: [opensuse-packaging] Re: Proper version scheme for packages from git, hg, svn, ...
by Jan Engelhardt 11 Jan '14

11 Jan '14

On Saturday 2014-01-11 09:29, Matwey V. Kornilov wrote: >Ok. And what version scheme should I follow? If you have not already made up your mind as to what you want (or "need"), then I would say go with the guidelines. They are there to guide. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] Best practices for a library with backends?
by Martin Vidner 09 Jan '14

09 Jan '14

Hi, I am getting involved with https://github.com/libyui , the UI library powering YaST. The basic design is a core library, libyui, which provides the API but has no actual UI. One of the 3 backends, libyui-{ncurses,gtk,qt}, is needed. I am looking for examples of best practices of versioning the shared libraries and setting up the dependencies among the parts of the framework. Current problems of libyui in this area: - not being careful about the so-versioning. That is a solved problem for a single(!) library, see https://github.com/openSUSE/libzypp/blob/a01b41c7dfe42a1fae9d9431fbad61997f… - the user-facing ABI of libyui and the backend-facing ABI are not well separated. Is there any project which has figured this out? - expressing the dependency "the core lib needs at least one backend with a matching ABI" is done via the yui_backend symbol but that breaks bootstrapping the build (See Fedora 19 on https://build.opensuse.org/project/monitor/devel:libraries:libyui ) Can you point me to any projects that handle this situation (common api + backends), however well? -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

2 1

[opensuse-packaging] Stack protector isues?
by Ilya Chernykh 09 Jan '14

09 Jan '14

What causes this package to fail for 32-bit but build for 64-bit in Factory? https://build.opensuse.org/package/show/KDE:KDE3/kdelibs3 I receive the following error message: [ 666s] /usr/lib/libc_nonshared.a(stack_chk_fail_local.oS): In function `__stack_chk_fail_local': [ 666s] /home/abuild/rpmbuild/BUILD/glibc-2.18.90/debug/stack_chk_fail_local.c:45: undefined reference to `__stack_chk_fail' [ 666s] collect2: error: ld returned 1 exit status [ 666s] Error creating ./kdeprint/management/libkdeinit_kaddprinterwizard.la. Exit status 1. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 12

[opensuse-packaging] openocd looks for home
by Matwey V. Kornilov 07 Jan '14

07 Jan '14

Hi, We have different forks of openocd package. Even I have my own with CMSIS support. But we don't have devel project for it. openocd is open on-chip debugger. It is a tool to communicate with embedded ARM-based hardware, to upload microcode and to provide interface for gdb for online debugging. I think, It is necessary to have openocd in Factory, but in any case we need devel project. I have not found appropriate project. Any ideas? Who will take care? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Unite package 'R-base' with 'R-base-devel'
by guenter 04 Jan '14

04 Jan '14

Please transfer the files from R-base-devel in the package R-base. Why?: When you have installed R and use it, it's _most likely_ that you need an additional R-package. If you then invoke e.g. 'install.packages("maps")' you will get an error which essentially says "R.h not found" (R-packages are built from source for install). But this takes a while to find out what the problem is (google for '"R.h" fatal error opensuse'). R-base-devel is small (400K after installation; R-base has 48,6M); the additional disk space is worth the convenience of a normal R user, I feel. It avoids a lot of frustration. Or make R-base-devel a dependency for R-base. Happy New Year! guenter -- openSuse 12.3; R-base[-devel] 2.15.2-2.4.1.x86_64 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] openSUSE ARMм7 BeagleBone Black experience
by Matwey V. Kornilov 02 Jan '14

02 Jan '14

Hi Marcus and all, I was trying to set this up and now I am in stuck. I have a piece of this hardware and want to run openSUSE 13.1 on it. I've collected needed packages (with u-boot-am335xevm 2013.04) in home:matwey:beaglebone,. I took openSUSE:13.1:Ports/JeOS as a base. Fortunately, there even was JeOS-beaglebone.kiwi, but it was not built and published. I've found two thing regarding to u-boot setup (quite strange): 1. u-boot looks for dtb in /boot/, when dtb-s are installed into /boot/dtb (is it a bug?) 2. mmcboot command tries to boot the kernel with bootm command: mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${kloadaddr} - ${fdtaddr} when compressed zImage is installed and have to be booted with bootz command. After this issues had been fixed manually from u-boot console, I was able to boot the linux. Here is available full booting log: http://paste.opensuse.org/18807914 Booting is stuck on root partition waiting, easily something wrong with mmc card device driver, but I can not figure out what exactly. dtb-file seems to be correct, u-boot finds that it has to be am335x-boneblack.dtb Will appreciate any help. -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 11

[opensuse-packaging] Re: [opensuse-arm] Booted openSUSE 13.1 on Beagle Bone Black
by Matwey V. Kornilov 02 Jan '14

02 Jan '14

2014/1/2 Alexjan Carraturo <axjslack(a)gmail.com>: > Hi Matwey > > I'm really curious to try the image for BeagleBone black. > > There is a link to download a tar.gz of this release (or loop)? http://download.opensuse.org/repositories/home:/matwey:/beaglebone/images_a… Remember, that you have to copy all files and dirs at first partition to /boot before booting (don't know where it should be fixed ;) ). You have to keep S2 switched during power-on to boot from external memory card. You need serial debug port, because there is YaST2 firstboot requiring interactive (setting time and passwords...). > I have already tried other file systems, one of which cross-compiled by me, > but I'd be happy to find some version that already has basic support for all > devices (in particular graphics acceleration and video decoder) do you know > if in the image openSUSE it's already all supported? Don't know yet, but would be nice if you could check. -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] Booted openSUSE 13.1 on Beagle Bone Black
by Matwey V. Kornilov 02 Jan '14

02 Jan '14

Hi, I have just successfully booted openSUSE 13.1 JeOS on my beagle bone black instance (see /var/log/messages at [1]). I am not sure that all peripherals are working, but I am able to communicate by Ethernet. Sure, I will check what is not working later. My working project is located at [2]. 1) u-boot-am335xevm I had to add patch to u-boot to make am335 to read bootscript. I sent SR to Base:System (and It is already accepted). I can easily sent this SR to 13.1:Ports. 2) dtb-am335x I had to patch existing dtb-source 3.12.5 to kernel master. So, no further patches are required for Factory, provided we will have kernel 3.13+ for 13.2. I can also SR to 13.1:Ports. 3) kernel This boots with kernel-default-3.11, but I had to apply 9 patches to make it work (look at kernel-source is at [3]): 2 of them are to fix ethernet module 7 of them are to fix DMA All of this patches are back-ports from upstream kernel. Provided we have kernel 3.13+ for 13.2, no patches are required for Factory. It is quite unlikely that our kernel teem will agree to apply 9 patches to openSUSE 13.1 kernel branch. 4) kiwi I have strange issue with kiwi, because I have to open my first partition and copy files from / to /boot directory manually before booting. Kiwi moves u-boot.bin and others from /boot to /, but u-boot looks for /boot/u-boot.bin [1] http://paste.opensuse.org/45517667 [2] https://build.opensuse.org/project/show/home:matwey:beaglebone [3] https://github.com/matwey/kernel-source -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0