February 2012 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Failing patch (only) for SLE_10
by Christian Boltz 09 Feb '12

09 Feb '12

Hello, I have a very interesting problem - a patch that works for most build targets fails for SLE_10. Does someone have an idea what could cause this (IMHO strange) behaviour? I've seen this in server:php:applications / postfixadmin https://build.opensuse.org/package/show?package=postfixadmin&project=server… Regards, Christian Boltz -- > Ist doch laut Deinen Schilderungen von den Hardwareanforderungen her > eine perfekte Konkurrenz zu Vista *renn* ;-) Da hast du recht ! Aber warum rennen :-) es wird dir kaum jemand hinterherlaufen weil alle vor der Kiste sitzen um auf die Katalogupdates zu warten ... [> Benjamin Zeller und Helmut Zengerling in suse-linux] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 5

[opensuse-packaging] Patching for new GCC
by Ilya Chernykh 09 Feb '12

09 Feb '12

In an old code I have encountered the following error: map.cpp:195:1: error: 'Map::Map' names the constructor, not the type The code is as follows: Map::Map & Map::operator = (Map const & map) { delete[] m_pieces; init(map); return *this; } I tried to remove the "::Map" but this did not help. Any ideas what should I do? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 8

[opensuse-packaging] non-executable-script warning
by Luiz Fernando Ranghetti 09 Feb '12

09 Feb '12

Hi guys, I have in one package I intend to submitt to Factory, tons of this warning: non-executable-script: https://build.opensuse.org/package/rawlog?arch=i586&package=translate-toolk… You'll see the incorrect-fsf-address warning too but these I correct with the guys upstream. I'm asking here whats the best way to correct this, because I want to raise this 'problem' upstream, and possibly offer a solution to them. Regards, Luiz -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] RFC: reminder mails for factory work
by Stephan Kulow 09 Feb '12

09 Feb '12

Hi, During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages. Too many people complain to me that they have no idea that their packages fail in factory or that they haven't seen the mail about the request X being declined, etc. So I collect the infos for each individual and send out reminders - my current idea is to send it out e.g every tuesday, but I can send it more often or less often as people say so. As an example I attach the mail as I would send it right now to Richard (because it has all interesting things and still isn't too long and I know he reads this list :) I would like to hear from you suggestions if this is useful to you and/or if you would like to see changes to make it more useful. I only send mail to the package maintainer as defined by the OBS flags and only if there is no maintainer set, I send mail to the project maintainers. This leads to the rather sad state, that a lot of people will get mail about packages they have no relation to. This is not a problem of the script, but a problem of some of the devel projects ;( So one thing to make this more useful (or the whole reporting) would be to set all people that have touched a specific package in the past also as package maintainers and either leave or cleanup the project maintainers. But that's a general topic that we should discuss instead of people starting to filter these mails. That's basically my main concern: I only want to send out mails that are interesting to the people reading it - even if it's auto generated content. So if the content is too long or too uninteresting, we need to change it. More examples of reminder mails you can find at http://stephan.kulow.org/reminders/ Greetings, Stephan

19 33

[opensuse-packaging] New review process for requests to G:F
by Vincent Untz 09 Feb '12

09 Feb '12

Hi all, The GNOME team has decided to adopt a process similar to the review process from Factory: all submit requests to GNOME:Factory now are set to be reviewed by the gnome-maintainers group by default. This shouldn't change anything for most contributors: we were already carefully reviewing the requests before; the main change is that it'll make it easier for us to control when changes enter G:F (and therefore, control rebuilds in that project). If this works fine for G:F, we might adopt the same process for G:A later on, and some packages maintained by the GNOME team in other projects (python-gobject in d:l:p, for instance). Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- 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] OBS is almost down in far east.
by Marguerite Su 08 Feb '12

08 Feb '12

Since OBS's last downtime, we packagers in China can hardly visit it. we have to keep waiting for longer than 2 minutes until OBS website refreshes. yes, every page. and have to wait even longer to the case of osc. we almost everytime will fail to send as small file as spec. tried using a Japan VPN and a US VPN, all failure, especially today. server maintainers please help. Marguerite -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

[opensuse-packaging] BuildRequires for 32-bit Java?
by Greg Freemyer 08 Feb '12

08 Feb '12

All, I'm trying to package a app that says it needs 32-bit Java. How do I say that in the spec file. Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 6

[opensuse-packaging] multimedia (and subrepos) project config
by Mariusz Fik 07 Feb '12

07 Feb '12

Hi, packages in multimedia:apps are built against libGLEW1_7 but this one it's not available in this repo - ie. clementine player. We need some multimedia:apps project config fix because we have now: unresolvable: have choice for libsndfile.so.1 needed by libpulse0: libsndfile1 libsndfile, have choice for libsndfile.so.1(libsndfile.so.1.0) needed by libpulse0: libsndfile1 libsndfile (at least for openSUSE12.1), something like: | Prefer: libsndfile1 to build against newer library version. Also we need to ship runtime dependecies for apps in multimedia:app, because using this repo without multimedia:libs is not possible now. -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D

8 9

[opensuse-packaging] right name for distorm / distorm3
by Greg Freemyer 07 Feb '12

07 Feb '12

All, I want to package distorm (distorm3) from http://code.google.com/p/distorm/ The name is distorm, but the source is distributed is distorm3-1.0.zip And the zip file expands to distorm3-1.0. I've got a very preliminary specfile at: https://build.opensuse.org/package/files?package=distorm&project=home%3Agre… Since '-' is illegal in the version number, it seems easiest to package this as distorm3. Further, this is an application, not a library, but since its written python, should it be python-distorm? Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 6

[opensuse-packaging] Automatic submission of changes to Factory
by Vincent Untz 02 Feb '12

02 Feb '12

Hi all, For a while, we've had the issue of packages with changes in devel projects not always being submitted to Factory. At the last openSUSE Conference, it appeared that not everyone was aware that this had to be manually done, and one solution that was discussed involved automatic submission. After some push from coolo, I finished a script I started working on a while ago, and we now have obs-autosubmit: https://gitorious.org/opensuse/obs-autosubmit To put it simply, it submits unsubmitted changes to Factory. It tries hard to be clever, for instance: - it only submits changes if the .changes entry is different - it doesn't submit a change that is already submitted - it doesn't submit a change that was declined/superseded Coupled with the factory-auto checks, this means that changed packages that don't build won't get through. (This has one issue, though: if a package failed to build because of another package being broken and got automatically submitted, it won't be automatically submitted again when the other package gets fixed) However, automatic submission is something that some people might not want. For instance, in GNOME:Factory, that'd be insane as we generally need to push several packages together and we do this after testing G:F. Therefore, there's a way to disable this automatic submission for either a whole project, or specific packages. Right now, this way is a hardcoded list, but we'll likely use attributes in the future. If you want to *not* have automatic submission for your project or your package, please tell me! For reference, a test run on Friday gave this result: - 375 packages to be automatically submitted. - 179 packages with changes, but no difference in .changes. - 73 packages with changes, already submitted in the past but declined/superseded/etc. - 78 packages with changes, already submitted. - 5 packages with changes, but autosubmit disabled. Cheers, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

11 39