April 2013 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Authentication failed When attempting to login with Admin/opensuse
by cheyw 11 Apr '13

11 Apr '13

Hi,All I'm setting up a obs service on an opensuse 12.1(i386) system and the setup's gone off without issue ，step by step with "/usr/share/doc/packages/obs-server/README.SETUP" until I attempt to log into the web interface. When attempting to login with Admin/opensuse I get Authentication failed. Sign up a new user would have the same error. But I'm able to log into the API using osc, I can see the default project “deleted” by "osc ls " command . How can I resolve the problem ? ----------------- OpenSUSE 12.1 (i386) OBS :Server:2.4.repo -->http://download.opensuse.org/repositories/OBS:/Server:/2.4/openSUSE_12.1/OB… ----------------- -- Best regards cheyw -- View this message in context: http://opensuse.14.x6.nabble.com/Authentication-failed-When-attempting-to-l… Sent from the opensuse-buildservice mailing list archive at Nabble.com. -- 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] Subprojects, Organization and Inheritance
by Matthew Drobnak 10 Apr '13

10 Apr '13

Hello again everyone. I've run into a bit of a dilemma - The way I currently have things set up is three main projects, one called "common" and two others for two different products, which both inherit from common. Here's the issue. We have a lot of language-related packages - like Python 2.7 for example, and will be getting a lot of Node.JS related packages. I don't want "common" to end up being a complete mess and turning into what one of our current yum repos for one of the two products is - 3000 packages with no idea what's still in use, where they came from, etc... So, I'd ideally like to add in some more organization, but am afraid of messing up the repo setup for the two products. What would be the recommended way to handle this? Thanks. -Matt -- 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] Is publishing days behind?
by Greg Freemyer 10 Apr '13

10 Apr '13

I have a package that built Friday and still hasn't published for 12.3 Is it just slow, or do I need to kick something? https://build.opensuse.org/package/show?package=libprelude&project=home%3Ag… Thanks Greg -- 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] Managing SUSE translations in unified way
by Tomáš Chvátal 09 Apr '13

09 Apr '13

Hello guys, Let me tell you a "shorty" bit about my hackweek project. Currently our translation repositories are stored in internal svn and split by branches per release. I want to tackle the issue where translations are inconsistent among supported releases and also somehow consolide all the stuff we are providing to have only one input channel with less space for contributor confusion. As I described this in my previous mail [1] I want to fire up the weblate instance with help from Michal Cihar. But as people complained against web translations only we will simply list the git repositories with access to allow them merge requests on github or use the weblate only as interface to obtain the .po files. Items currently stored in svn [2]: yast - obvious, in github webyast - obvious, in github lcn - merged repository for various tools zypper/bootloader/... packages - repository for cd descs/etc... Some of the packages do not have suse upstream (eg special kde translations and so on). These will be migrated in the end to new github project (eg. openSUSE/translations-3rdparty.git; if you have cooler name we will use it :P). Also I bet we already have some projects that should be translated and are not. If you happen to be aware of such project we can also add it to the toolkit, just reply to this mail with its name and git repo. List of tasks to get this working ------------------------------------------- Infrastructure side: Deprecate translations mailinglists to keep only the opensuse-translation where everyone should discuss, with per language lists the problem is if the team goes inactive nobody notices, and we can have more active list where we ingore threads that do not bother us. Eg we can have them prefixed by lang if they matter only for those ([ru] Unable to translate foo due to xyz). [[Who can actually sent deprecation mails and mark them read only?]] Create new documentation on i18n which will contain the weblate instance and provide links to git repositories and pull requests description for contributors not wanting to use the weblate. Suspending the translation repositories to read-only until migration is complete. Note for translators, you can translate your stuff even in read-only mode. Merging then will be possible in weblate or by hand into the new location which will be described in the new repository listing. IMPORTANT: this must be done ASAP, because without the disabled write access we shouldn't start moving the files around. Upstream/developers side: Take the translations from the svn repository and create po/ folder in your project root. Structure looks like this (some projects already have po folder but the translations are in tarball, just throw away the tarball and unpack it): <snip> yast2-network/po/cs.po yast2-network/po/de.po yast2-network/po/yast2-network.pot </snip> Modify spec-file of the package to count with the translations from here (I am well aware it will create collisions in the start with the generic l10n packages we will remove later on, so we should obsolete them and make the lang pkg recommended). Create new hook that updates the .pot file with each commit and regenerates the .po files. I bet Michal already have some nice hook at phpmyadmin and he can provide it so we don't need to write one stock each time. Remove hooks that push into svn if there are some and it is not cron-based server side. [[Anyone knows how this is done?]] Update buildscripts to generate .mo files and to install them into right place. Easy in distutils, for autotools you need gettext Makefile.in.in, I will provide help and do the work where needed. After we fire up testing weblate we will also need to add weblate key to be able push to the repository. [[Michal could you please elaborate here how this taks need to be done?]] Of course you are not the ones who have to do the work, I will do the task if asked/allowed to touch your repos (scarabeusiv account at github). I am just pretty sure I will not be able to migrate all 205 repos in one week without screwing up somewhere, so any help will be highly appreciated, specially when you guys know your project much more than I do :-) Packaging side: We need to update the .spec files of the various translation modules like yast2-translations to be split into specified packages (yast2-network-lang,...) Packages that will be obsoleted and split are: yast2-translations [[I suck at searching in obs so if you see more of those that should be adjusted please reply here and I will do whats needed]] Possible future task that would make people happy: Allow translations of wiki pages instead of having separate wiki instances for each language. This stuff is messy and using weblate here would be so awesome. Cheers Tom PS: keep reply-to on opensuse-translation so we don't clutter the discussion on multiple places. PPS: this is quite lengthy mail so if I forgot to mention something just slap me and ask for more informations. [1] http://lists.opensuse.org/opensuse-translation/2013-04/msg00000.html [2] http://svn.opensuse.org/svn/opensuse-i18n/

4 6

[opensuse-buildservice] how to avoid a file in the binary package
by Martin Koller 07 Apr '13

07 Apr '13

Hi all, building my app "showimage" on OBS, I get the following warning: showimage.i586: W: install-file-in-docs /usr/share/doc/packages/showimage/INSTALL [ 79s] A file whose name suggests that it contains installation instructions is [ 79s] included in the package. Such instructions are often not relevant for already [ 79s] installed packages; if this is the case for this file and it does not contain [ 79s] any information that is of interest after the package has been built and [ 79s] installed, do not include the file in the binary package. How can I define that the INSTALL file is only part of the .src package ? https://build.opensuse.org/package/view_file?expand=1&file=showimage.spec&p… -- Best regards/Schöne Grüße Martin A: Because it breaks the logical sequence of discussion Q: Why is top posting bad? () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments Geschenkideen, Accessoires, Seifen, Kulinarisches: www.bibibest.at -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] building with gcc48
by scalpel4k 06 Apr '13

06 Apr '13

Hi OBS experts, I have a little problem with one package that needs to be built with gcc48. However, when I specify that requirement in the spec file I end up with a conflict, because allegedly another version of libgcc_sl1 is already installed (from gcc47). Does anybody know how I can get around this conflict? thanks for your help Michi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] [GSoC2013][BitBake Integration]Call for mentors
by 赵旭 06 Apr '13

06 Apr '13

Hello, I am a student interested in the idea of integrating BitBake with OBS and hope I can work on it in GSoC 2013. Unfortunately Michal is busy this year and wont be able to help most probably. However I myself think it is a great idea and want to make it. So I come to this mailist for help (following Manu's advice) and hopefully there will someone willing to be my mentor on this project and let's make it together:) -- --------------------------------- Xu Zhao Department of Computer Science&Technology Tsinghua University Beijing P.R.China Mobile: +86-152-1058-8604 nuklly(a)gmail.com -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Application:Geo OBS priority
by Angelos Tzotsos 06 Apr '13

06 Apr '13

Hi all, The geospatial repository seems to be building only 1-2 projects at a time for the last 3 days. Since we are upgrading some major applications, we need to build the whole repository and this delay is causing trouble to the users (postgis is still not released for 12.3). I believe that this repository should have a priority raise in OBS (I don't know the current priority or if there is a problem in OBS currently). Best, Angelos -- Angelos Tzotsos Remote Sensing Laboratory National Technical University of Athens http://users.ntua.gr/tzotsos -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] does anyone ever clean up / verify users?
by Mathias Homann 06 Apr '13

06 Apr '13

Hi, there are a few weird kinks on OBS right now... ...for example: - several packages / build jobs that by now have been running for several WEEKS, while a local build of those packages usually takes minutes - at least one account who does not use OBS anymore, or at least does not read emails sent to the address configured on the account, but branched several packages and therefor blocks others from cleaning up their homes. who can deal with that? cheers, MH -- gpg key fingerprint: 5F64 4C92 9B77 DE37 D184 C5F9 B013 44E7 27BD 763C () ascii ribbon campaign against HTML e-mail /\ www.asciiribbon.org -- 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] Open Build Service (OBS) 2.4.0 RC 2 released
by Adrian Schröter 05 Apr '13

05 Apr '13

We released OBS 2.4.0 RC 2 (tagged as 2.3.96) today. This update contains fixes for user handling in webui and a number of other smaller bug fixes. LDAP is still in unclear state, but the general loading of ldap modules have been fixed. While there is a group working on improving it, the current code is completely untested by SUSE. It would be great if someone could test it before release. The release rpms and appliances can be found in OBS:Server:2.4 project: http://en.opensuse.org/openSUSE:Build_Service_Appliance Repositories: http://download.opensuse.org/repositories/OBS:/Server:/2.4/ Release Notes are currently the same as for RC 1. Skipping them here. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0