January 2015 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] [RFC] Is there any plan to add ILP32 support for aarch64?
by Bamvor Jian Zhang 27 Jan '15

27 Jan '15

Hi, guys This is Bamvor Jian Zhang from Huawei OS team. Recently, I am working on enable the ILP32 support for arm64 based on the community work[kernel\_ilp32][glibc\_ilp32]. ILP32 is a method for running 32bit application on 64bit platform, such binary is elf32 with aarch64 assembly and is compiled by 64bit compiler. Refer the following table: \- | arm 32bit | arm64 ILP32 | arm64 LP64 ----------------|-------------|-------------|------------- instruction set | armv7-a | armv8-a | armv8-a int | 32bit | 32bit | 32bit long | 32bit | **32bit** | 64bit pointer | 32bit | **32bit** | 64bit x32 and n32 is the ILP32 ABI in x86\_64 and MIPS 64 respectively. Right now, more than 99% of LTP test cases is passed. And we get 2.6% to 7.9% performance improvement compare with aarch64 without any optimization or tuning. Base on these work, we are sure that ILP32 is worth to work on and we could feel more confident if more and more packages build and test. The obs seems the best way to build ilp32 packages, I wondering is there any document or guidance about how to add ILP32 to an architecture or how to add a new ABI to a new architecture? I got 4 commit about aarch64 in obs source code[openbuildservice] with "git log --grep aarch64": effc064 [backend] aarch64 workers can also build 32bit arm e0bd2e5 [api] add aarch64 to xml schema file b71ecfe [api] add aarch64 architecture 0c08cbe [backend] add aarch64 architecture But I still not puzzled about how to start. I also found some Linux32 definitions in obs source code[openbuildservice], does it mean the ilp32 is supported on the following architecture? src/backend/BSCando.pm: 'x86_64' => [ 'x86_64', 'i586:linux32', 'i686:linux32' ], src/backend/BSCando.pm: 'parisc64'=> [ 'hppa64', 'hppa:linux32' ], src/backend/BSCando.pm: 'ppc64' => [ 'ppc64le', 'ppc64', 'ppc:linux32' ], src/backend/BSCando.pm: 'ppc64p7' => [ 'ppc64le', 'ppc64p7', 'ppc:linux32' ], src/backend/BSCando.pm: 'ppc64le' => [ 'ppc64le', 'ppc64', 'ppc:linux32' ], src/backend/BSCando.pm: 's390x' => [ 's390x', 's390:linux32' ], src/backend/BSCando.pm: 'sparc64' => [ 'sparc64v', 'sparc64', 'sparcv9v', 'sparcv9', 'sparcv8:linux32', 'sparc:linux32' ], BTW: basically, add ilp32 support means that adding ilp32 support to kernel, gcc and glibc. And pass CC or CXX with additional -mabi=ilp32 to overwrite the default -mabi=lp64 when building the packages. regards bamvor [kernel\_ilp32] kernel ilp32 patch(v3): https://lkml.org/lkml/2014/9/3/704 [glibc\_ilp32] glibc ilp32 patch: https://sourceware.org/ml/libc-alpha/2014-10/msg00596.html [openbuildservice] https://github.com/openSUSE/open-build-service.git -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 14

[opensuse-buildservice] how to find my own requests
by Olaf Hering 27 Jan '15

27 Jan '15

I wonder how I would find requests created by myself? rq -h suggests that -M would do it, but appearently it does not. For example, how would I find 281054 or 281087? Right now one way would be "rq list -s accepted -t submit PRJ", which is way too verbose. And even wrong if the request is in a different state. Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 6

[opensuse-buildservice] checking whether a person is owner of a package
by Ludwig Nussel 26 Jan '15

26 Jan '15

Hi, To find out who are the owners of a package there's the /search/owner?binary=PKG call. Part of the result could be group though. If I wanted to know whether a specific user is owner of the given package, am I expected to retrieve the group information and check whether the user is member of each group? Is there maybe a better suited call that would do that for me on server side? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5; 90409 Nürnberg; Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 6

[opensuse-buildservice] OBS gateway hiccup?
by Ralf Lang 23 Jan '15

23 Jan '15

I get the following kind of error when accessing OBS for "osc build" or "osc ci". Building groupware-image-13.2.kiwi for images/x86_64 Getting buildinfo from server and store to /srv/obs/isv:B1-Systems:Horde5:opensuse-appliance/groupware-image/.osc/_buildinfo-images-x86_64.xml Server returned an error: HTTP Error 502: Bad Gateway However, osc up works. -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

4 16

[opensuse-buildservice] Fedora 21 and UCS 4.0 added
by Adrian Schröter 23 Jan '15

23 Jan '15

Hi, Fedora 21 and UCS 4.0 got added finally. You may have also noticed some friendly removal requests for repositories building against EOL distros. In case no "decline" action happens these requests will get accepted in about one month. Happy new year! adrian -- Adrian Schroeter email: adrian(a)suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] please replace/repair the packages made previously availble in patch openSUSE-2015-42
by grantksupport＠operamail.com 22 Jan '15

22 Jan '15

Could whoever/whatever broke, removed, or otherwise 'disappeared' the packages/versions previously made available in distro patch/update @ http://lists.opensuse.org/opensuse-updates/2015-01/msg00044.html please put them back? specifically, the libzypp versions >= 14.30. those had been introduced https://bugzilla.suse.com/show_bug.cgi?id=899510#c3 and enabled backward INCOMPATIBLE changes to repo files. with those versions removed, zypper up's forcing downgrades to libzypp <= 14.29 -- which will now cause zypper to break with those changes in place. the newer versions are no longer available in the repos, nor is the referenced patch, openSUSE-2015-42 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Can't get group information from LDAP
by Konstantin Rudenkov 22 Jan '15

22 Jan '15

Hi! I install standalone version OBS in corporate environment. We use OpenLDAP for identification. Users' authentication runs well, but webui does not even ask information about groups. I looked at tcpdump output, OpenLDAP log & production.log. What can be a problem? ( configuration connection with LDAP are shown below) ldap_mode: :on # LDAP Servers separated by ':'. # OVERRIDE with your company's ldap servers. Servers are picked randomly for # each connection to distribute load. ldap_servers: ldap.mysite.com # Max number of times to attempt to contact the LDAP servers ldap_max_attempts: 15 # The attribute the user memberof is stored in # ldap_user_memberof_attr: memberof # Perform the group_user search with the member attribute of group entry or memberof attribute of user entry # It depends on your ldap define # The attribute the group member is stored in ldap_group_member_attr: member # If you're using ldap_authenticate=:ldap then you should ensure that # ldaps is used to transfer the credentials over SSL or use the StartTLS extension ldap_ssl: :on # Use StartTLS extension of LDAP ldap_start_tls: :off # LDAP port defaults to 636 for ldaps and 389 for ldap and ldap with StartTLS #ldap_port: # Authentication with Windows 2003 AD requires ldap_referrals: :off # OVERRIDE with your company's ldap search base for the users who will use OBS ldap_search_base: ou=People, dc=mysite, dc=com # Sam Account Name is the login name for LDAP ldap_search_attr: uid # The attribute the users name is stored in ldap_name_attr: cn # The attribute the users email is stored in ldap_mail_attr: mail # Credentials to use to search ldap for the username ldap_search_user: "" ldap_search_auth: "" # By default any LDAP user can be used to authenticate to the OBS # In some deployments this may be too broad and certain criteria should # be met; eg group membership # # To allow only users in a specific group uncomment this line: ldap_user_filter: (mail=*(a)mysite.com) # # Note this is joined to the normal selection like so: # (&(#{dap_search_attr}=#{login})#{ldap_user_filter}) # giving an ldap search of: # (&(sAMAccountName=#{login})(memberof=CN=group,OU=Groups,DC=Domain Component)) # # Also note that openLDAP must be configured to use the memberOf overlay # ldap_authenticate says how the credentials are verified: # :ldap = attempt to bind to ldap as user using supplied credentials # :local = compare the credentials supplied with those in # LDAP using #{ldap_auth_attr} & #{ldap_auth_mech} # if :local is used then ldap_auth_mech can be # :md5 # :cleartext ldap_authenticate: :ldap ldap_auth_mech: :md5 # This is a string ldap_auth_attr: userPassword # Whether to update the user info to LDAP server, it does not take effect # when ldap_mode is not set. # Since adding new entry operation are more depend on your slapd db define, it might not # compatiable with all LDAP server settings, you can use other LDAP client tools for your specific usage ldap_update_support: :off # ObjectClass, used for adding new entry ldap_object_class: inetOrgPerson # Base dn for the new added entry ldap_entry_base: ou=OBSUSERS,dc=EXAMPLE,dc=COM # Does sn attribute required, it is a necessary attribute for most of people objectclass, # used for adding new entry ldap_sn_attr_required: :on # Whether to search group info from ldap, it does not take effect # when LDAP_GROUP_SUPPOR is not set. # Please also set below LDAP_GROUP_* configs correctly to ensure the operation works properly ldap_group_support: :on # OVERRIDE with your company's ldap search base for groups ldap_group_search_base: site=jenkins.mysite.com,ou=devops,ou=Technology,ou=MYSITE,ou=Projects # The attribute the group name is stored in ldap_group_title_attr: op # The value of the group objectclass attribute, leave it as "" if objectclass attr doesn't exist ldap_group_objectclass_attr: iponwebPermission-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Again: Correctly unpublishing packages
by Johannes Kastl 22 Jan '15

22 Jan '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, I just stumbled upon a problem that has been discussed before: How to correctly unpublish a package? I found this: > Wipe binaries and enable publishing with building disabled. Or use > `osc wipebinaries --all PROJECT [PACKAGE]`. "--all" is sufficient > as I know. > http://lists.opensuse.org/opensuse-buildservice/2013-06/msg00199.html I > found that the latter possibility is not working, i.e. just wiping the binaries does not delete them. At least after waiting for some hours. So does one really have to disable builds, enable publishing, and then wipebinaries? Or is there an easier solution? And, even if this could be a boomerang: Should stuff like this not be on the wiki somewhere? ;-) Regards, Johannes - -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. (Benjamin Franklin, 1759) -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlTA1IMACgkQzi3gQ/xETbKTtgCfcCLzpQdypU9MIeV42PpCz8RF E84AoI9vSecbfjM0/04q5KUaem4FERwI =FaZo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] Re: [opensuse] please replace/repair the packages made previously availble in patch openSUSE-2015-42
by grantksupport＠operamail.com 22 Jan '15

22 Jan '15

On Wed, Jan 21, 2015, at 05:47 PM, Patrick Shanahan wrote: > * grantksupport(a)operamail.com <grantksupport(a)operamail.com> [01-21-15 20:24]: > > On Wed, Jan 21, 2015, at 05:10 PM, Patrick Shanahan wrote: > > > an answer to this question/demand was posted to list in the last several > > > hours. The zypper package was "broken" and slipped bye. > > > > Thanks. > > > > For anyone interested, found it here: http://lists.opensuse.org/opensuse/2015-01/msg00612.html > > > > Imo, we have too many lists, &/or no clear guidance/policy where breakage like this is announced; you'd think that if a patch/update is announced on opensuse-updates, then any change/breakage/rollback to it should also be posted there. > > > > Also re-raises old questions of why/how it's allowed to push & publish updates before a stable, non-broken state is verified, AND that once done, there's no "current-1" snapshot, or other backup, to rollback to. Other topics ... > > You do realize that your post is private, not to the list, or both lists > against list netiquette. > > You do realize that your post is private, not to the list, or both lists > against list netiquette. Seriously? Well, gee-willikers -- my bad for just clicking "Reply to all ..." oh wait. Then again -- maybe you shouldn't have first responded to ME only "against list nettiquette": ------ Return-Path: <ptilopteri(a)gmail.com> ... Date: Wed, 21 Jan 2015 20:10:53 -0500 From: Patrick Shanahan <ptilopteri(a)gmail.com> To: grantksupport(a)operamail.com Subject: Re: [opensuse] please replace/repair the packages made previously availble in patch openSUSE-2015-42 Message-ID: <20150122011053.GC3960(a)wahoo.no-ip.org> Mail-Followup-To: grantksupport(a)operamail.com References: <1421886690.4030279.217141201.0F8A1C99(a)webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1421886690.4030279.217141201.0F8A1C99(a)webmail.messagingengine.com> X-Operating-System: Linux 3.11.10-25-desktop x86_64 openSUSE 13.1 Organization: Ptilopteri in Pandemonium User-Agent: Mutt/1.5.21 (2010-09-15) X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 ------ How's that? better ON the list? Wow ... -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] missing libgcc.a in cross-armv7hl-gcc49
by Rick Liu 20 Jan '15

20 Jan '15

Hi, I'm trying to use cross-armv7hl-gcc49 to do cross build for arm. After extract the RPM, the number of files is fewer than I expected. eg. Comparing with cross-gcc from other distro, such as Linaro or Mer, it's missing all the library files, like: $PREFIX/$TARGET/lib/libasan.a $PREFIX/$TARGET/lib/libasan.la $PREFIX/$TARGET/lib/libasan.so $PREFIX/$TARGET/lib/libasan.so.0 $PREFIX/$TARGET/lib/libasan.so.0.0.0 $PREFIX/$TARGET/lib/libasan_preinit.o $PREFIX/$TARGET/lib/libatomic.a $PREFIX/$TARGET/lib/libatomic.la $PREFIX/$TARGET/lib/libatomic.so $PREFIX/$TARGET/lib/libatomic.so.1 $PREFIX/$TARGET/lib/libatomic.so.1.0.0 $PREFIX/$TARGET/lib/libgcc_s.so $PREFIX/$TARGET/lib/libgcc_s.so.1 $PREFIX/$TARGET/lib/libgomp.a $PREFIX/$TARGET/lib/libgomp.la $PREFIX/$TARGET/lib/libgomp.so $PREFIX/$TARGET/lib/libgomp.so.1 $PREFIX/$TARGET/lib/libgomp.so.1.0.0 $PREFIX/$TARGET/lib/libgomp.spec $PREFIX/$TARGET/lib/libitm.a $PREFIX/$TARGET/lib/libitm.la $PREFIX/$TARGET/lib/libitm.so $PREFIX/$TARGET/lib/libitm.so.1 $PREFIX/$TARGET/lib/libitm.so.1.0.0 $PREFIX/$TARGET/lib/libitm.spec $PREFIX/$TARGET/lib/libmudflap.a $PREFIX/$TARGET/lib/libmudflap.la $PREFIX/$TARGET/lib/libmudflap.so $PREFIX/$TARGET/lib/libmudflap.so.0 $PREFIX/$TARGET/lib/libmudflap.so.0.0.0 $PREFIX/$TARGET/lib/libmudflapth.a $PREFIX/$TARGET/lib/libmudflapth.la $PREFIX/$TARGET/lib/libmudflapth.so $PREFIX/$TARGET/lib/libmudflapth.so.0 $PREFIX/$TARGET/lib/libmudflapth.so.0.0.0 $PREFIX/$TARGET/lib/libobjc.a $PREFIX/$TARGET/lib/libobjc.la $PREFIX/$TARGET/lib/libobjc.so $PREFIX/$TARGET/lib/libobjc.so.4 $PREFIX/$TARGET/lib/libobjc.so.4.0.0 $PREFIX/$TARGET/lib/libssp.a $PREFIX/$TARGET/lib/libssp.la $PREFIX/$TARGET/lib/libssp.so $PREFIX/$TARGET/lib/libssp.so.0 $PREFIX/$TARGET/lib/libssp.so.0.0.0 $PREFIX/$TARGET/lib/libssp_nonshared.a $PREFIX/$TARGET/lib/libssp_nonshared.la $PREFIX/$TARGET/lib/libstdc++.a $PREFIX/$TARGET/lib/libstdc++.la $PREFIX/$TARGET/lib/libstdc++.so $PREFIX/$TARGET/lib/libstdc++.so.6 $PREFIX/$TARGET/lib/libstdc++.so.6.0.19 $PREFIX/$TARGET/lib/libstdc++.so.6.0.19-gdb.py $PREFIX/$TARGET/lib/libsupc++.a $PREFIX/$TARGET/lib/libsupc++.la Where can I get these libraries? or how do I configure/rebuild cross-armv7hl-gcc49 package to build these libraries? Thanks, Rick -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0