February 2009 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] sane-frontends needs new maintainer
by Johannes Meixner 12 Feb '09

12 Feb '09

Hello, I can no longer maintain the package sane-frontends sane-frontends contains the scanner user frontend programs xscanimage, xcam, and scanadf from the SANE project http://www.sane-project.org/ "whatdependson -R sane-frontends" results nothing "whatdependson sane-frontends" results only - beagle-index (gnome-maintainers(a)suse.de) but as far as I know this is no hard build dependency. FYI: "whatdependson" is an internal Suse/Novell tool "whatdependson package" shows build dependencies i.e. for which other packages is the package needed to build the other packages. "whatdependson -R package" shows run-time dependencies i.e. which other packages require the package to be installed so that the other packages work o.k. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] kde4-skrooge
by Sascha 'saigkill' Manns 12 Feb '09

12 Feb '09

Package: kde4-skrooge Project: home:saigkill Hello Mates, the last build was suceeded, but now i'm see an expansions Error. Has anyone an idea, how to fix it? -- Sincereley yours Sascha Manns openSUSE Marketing Team (Weekly News) openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://lizards.opensuse.org/author/saigkill -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] pstoedit needs new maintainer
by Johannes Meixner 10 Feb '09

10 Feb '09

Hello, I can no longer maintain the package pstoedit. Perhaps one of kde-maintainers(a)suse.de gnome-maintainers(a)suse.de or sbrabec(a)novell.com could maintain it because they need it: $ whatdependson pstoedit - autotrace (sbrabec(a)novell.com) - koffice2 (kde-maintainers(a)suse.de) $ whatdependson -R pstoedit - inkscape [pstoedit=3.45-1.6] $ maintainer inkscape gnome-maintainers(a)suse.de Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Re: [opensuse-gnome] G:F status after packaging day
by Suman Manjunath 09 Feb '09

09 Feb '09

On Fri, 2009-02-06 at 02:17 +0100, Vincent Untz wrote: > Also, I had to disable most (all?) of the sharepoint related patches in > evolution since they break the build. I suspect I broke a patch at some > point -- when the build service ate the evolution package: > https://bugzilla.novell.com/show_bug.cgi?id=472867 > If evo people could look at the patches and either fix them (based on > the old patches), upstream them or kill them, that'd be great. I posted a comment on the bug. Here's a gist anyway ;-) It was not a problem with the evo package. It is a problem the way linkpac works. I made the submission to G:F so I know for sure that all was well in my repo before the submission ;-) All patches were clean. Since both projects (i.e. evo in G:F and evo in my repo) had "project.diff", something broke when I submitted and you accepted. I've changed the product and component of that bug so we can track it there. -Suman -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] Different build behaviour in Factory
by Adrian Schröter 06 Feb '09

06 Feb '09

Hello, A significant change, how we build openSUSE:Factory and all repos building against it have just made effective. This change has the effect that we will not publish packages anymore when they have effective not changed. So it should be way more comfortable to follow up Factory. The same message, a bit more verbose can be found here: http://news.opensuse.org/2009/02/05/more-efficient-factory-development/ However, this is new stuff, so we might have introduced new problems, even though we hope to have implemented this on the save side. But early in the Alpha phase of 11.2 is a good point of time to test this :) We may activate this compare check also in 11.1 and before builds later, but lets first look how good it works for factory :) bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

Re: [opensuse-packaging] Question for packaging python apps
by Jan Matejek 05 Feb '09

05 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin Vidner napsal(a): > On Thu, Feb 05, 2009 at 12:24:26PM +0100, Vincent Untz wrote: >> Hi, >> >> I have a python app that installs all its .py files in >> ${_datadir}/%{name}, and upstream thinks it's right. I thought it made >> sense to put the files in %{py_sitedir}/%{name}, so I originally had a >> patch to do this, but if upstream doesn't want it, I'm not really keen >> on keeping it. >> >> Is there any policy for this? > > If those files are private to the app, as opposed to usable by > others as a library, then ${_datadir}/%{name} is a reasonable > private storage and I see no reason to diverge from upstream. Actually it's a little more difficult than that - what you (and upstream) are doing is directly against FHS, which states that program files aren't supposed to go anywhere near ${_datadir}. General recommendation is to put everything in %{py_sitedir}. But it's not a policy (yet), because this approach also has some drawbacks... And python upstream doesn't have a strong opinion on this either, that's the worst part. so, simple answer is, keep the files where upstream wants them, until somebody comes up with a better way. (and when that somebody does, i'll keep you posted) regards m. - -- (if you have any comments, please CC me in the reply, otherwise my replies will break threads. that is a bug in my way of using the mailinglist, which is not yet fixed) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmLLVYACgkQjBrWA+AvBr951gCfdN9uI1h7hiw7NCLDB0aZnwZA TqUAnR0+OA+zPObVa4uxt9Tz6rbxq0jK =22z4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] Question for packaging python apps
by Vincent Untz 05 Feb '09

05 Feb '09

Hi, I have a python app that installs all its .py files in ${_datadir}/%{name}, and upstream thinks it's right. I thought it made sense to put the files in %{py_sitedir}/%{name}, so I originally had a patch to do this, but if upstream doesn't want it, I'm not really keen on keeping it. Is there any policy for this? Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] kde4-skrooge
by Sascha 'saigkill' Manns 04 Feb '09

04 Feb '09

Hello Friends, ================== Packet: kde4-skrooge Project: home:saigkill ================== in this Package i've got any REPMLint Errors. The no-binary is fixed. Can anyone help me? -- Sincereley yours Sascha Manns openSUSE Marketing Team (Weekly News) openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://lizards.opensuse.org/author/saigkill -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] GCC 4.4 hints for packagers
by Cristian Rodríguez 03 Feb '09

03 Feb '09

Hi: GCC 4.4 will appear sooner or later on factory, and some of your packages may fail to build. To resolve the errors you may see, read the following article http://www.cyrius.com/journal/gcc/gcc-4.4-include or see if your package is on this list http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-gcc-4.4;users=debian… You will probably find a patch attached in the report to fix the issue. Thanks for flying with openSUSE. -- "We have art in order not to die of the truth" - Friedrich Nietzsche Cristian Rodríguez R. Software Developer Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/

2 3

[opensuse-packaging] OBS Scheduler = Dead
by Magnus Boman 03 Feb '09

03 Feb '09

Hey, Are there any plans to have someone monitor (and fix issues) in OBS 24x7? Atm, the scheduler is dead and everyone is a sleep, which is quiet annoying as it's daytime where I am. Actually, feel free to add me to the payroll and give me access and I'll help out while you guys are a sleep :-) Cheers, Magnus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 4