[opensuse-kde] opensuse 11.2: KDE3 repository, kmail
Hi, I know that the kde3 repo is not officially maintained anymore. Nevertheless I hope someone could repair kdepim3-3.5.10-67.3.src.rpm where kmail crashs reproducible every time when sending an email. I think the included kdepim3-gcc4.4.patch is buggy because Ive got kmail working again recompiling it without that patch and explicitly using gcc-4.3. So maybe it would be an easy task for someone to remove that patch and add gcc-43 to the build requirements on opensuse 11.2. (gcc-43 is shipped with the default installation source) cu, Rudi -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Hi, as you seem fit for such things why not use the opensuse build service? Create a _link to kdepim3, make your modifications, test the result and when it works make a submitrequest. Most direct user contributions are handled that way (or should be) Cya, Karsten Am Montag, 7. Dezember 2009 15:52:36 schrieb Rüdiger Meier:
Hi,
I know that the kde3 repo is not officially maintained anymore. Nevertheless I hope someone could repair kdepim3-3.5.10-67.3.src.rpm where kmail crashs reproducible every time when sending an email.
I think the included kdepim3-gcc4.4.patch is buggy because Ive got kmail working again recompiling it without that patch and explicitly using gcc-4.3. So maybe it would be an easy task for someone to remove that patch and add gcc-43 to the build requirements on opensuse 11.2. (gcc-43 is shipped with the default installation source)
cu, Rudi
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Hi, On Monday 07 December 2009, Karsten König wrote:
as you seem fit for such things why not use the opensuse build service? Create a _link to kdepim3, make your modifications, test the result and when it works make a submitrequest. Most direct user contributions are handled that way (or should be)
Ok, I will try that. I just thought I'm not the right packager for such kde stuff because I'm not much using kde at all. cu, Rudi -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Hi, On Monday 07 December 2009, Karsten König wrote:
as you seem fit for such things why not use the opensuse build service? Create a _link to kdepim3, make your modifications, test the result and when it works make a submitrequest
So I've made my first steps with opensuse build service but have some dumb questions. 1. Using the web interface I created a link to kdepim3 of KDE:KDE3 and triggered a rebuild for openSUSE_11.[0-2]. The build for openSUSE_11.0 failed: /usr/src/packages/BUILD/kdepim-3.5.10/kaddressbook/thumbnailcreator/ldifvcardcreator.cpp:88: error: 'class KABC::VCardConverter' has no member named 'parseVCardsRaw' I'm not curious about that specific error, just wonder why KDE:KDE3/kdepim3 compiles but my link does not? 2. Using "osc build" on a local machine it asks me for root password after downloading all build requirements. Is this just needed for doing "chroot"? Is it possible to build without being root somehow? 3. Is there a simple command to build an osc checkout against my local installation without using a chroot dir? cu, Rudi -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday 09 December 2009 12:09:16 Rüdiger Meier wrote:
So I've made my first steps with opensuse build service but have some dumb questions.
1. Using the web interface I created a link to kdepim3 of KDE:KDE3 and triggered a rebuild for openSUSE_11.[0-2]. The build for openSUSE_11.0 failed: /usr/src/packages/BUILD/kdepim-3.5.10/kaddressbook/thumbnailcreator/ldifvca rdcreator.cpp:88: error: 'class KABC::VCardConverter' has no member named 'parseVCardsRaw'
I'm not curious about that specific error, just wonder why KDE:KDE3/kdepim3 compiles but my link does not?
This is because the repository you registered in your project for openSUSE_11.0 is the vanilla released openSUSE 11.0, so your kdepim3 is building against 11.0's kdepim3 and not the kdepim3 from KDE:KDE3, which adds the method parseVCardsRaw. Remove (at least) the openSUSE_11.0 repo from your project and add KDE:KDE3/openSUSE_11.0 instead so you build your link against the KDE it originates from.
2. Using "osc build" on a local machine it asks me for root password after downloading all build requirements. Is this just needed for doing "chroot"? Is it possible to build without being root somehow?
I don't know, you could check with opensuse-buildservice@opensuse.org if this is at all possible with osc build, but I doubt it since the ability to have multiple build roots is a central feature of osc.
3. Is there a simple command to build an osc checkout against my local installation without using a chroot dir?
You could use plain old rpmbuild if your local installation offers all the prerequisites for your kdepim3 build. HTH Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday 09 December 2009, Will Stephenson wrote:
On Wednesday 09 December 2009 12:09:16 Rüdiger Meier wrote:
I'm not curious about that specific error, just wonder why KDE:KDE3/kdepim3 compiles but my link does not?
This is because the repository you registered in your project for openSUSE_11.0 is the vanilla released openSUSE 11.0, so your kdepim3 is building against 11.0's kdepim3 and not the kdepim3 from KDE:KDE3,
Ah ok, thx. cu, Rudi -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday 09 December 2009, 12:09:16 Rüdiger Meier wrote:
2. Using "osc build" on a local machine it asks me for root password after downloading all build requirements. Is this just needed for doing "chroot"? Is it possible to build without being root somehow?
http://en.opensuse.org/Build_Service/Tutorial#Build_your_package_locally
3. Is there a simple command to build an osc checkout against my local installation without using a chroot dir?
No simple command, but you may be able to build a matching RRM build environment around this dir with mkdir and symlinks, or copy it over to /usr/src/packages/{SOURCES,SPECS} and build there. But all these methods aren't fully deterministic dependency wise, hence these methods are strongly deprecated for generating rpms targeted to other systems (as long as they're not exact clones of your's). Cheers, Pete -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday 09 December 2009, Hans-Peter Jansen wrote:
On Wednesday 09 December 2009, 12:09:16 Rüdiger Meier wrote:
2. Using "osc build" on a local machine [...] Is it possible to build without being root somehow?
http://en.opensuse.org/Build_Service/Tutorial#Build_your_package_loca lly
The main problem is that I'm not root or rather don't want to do that as root on our production systems.
3. Is there a simple command to build an osc checkout against my local installation without using a chroot dir?
No simple command, but you may be able to build a matching RRM build environment around this dir with mkdir and symlinks, or copy it over to /usr/src/packages/{SOURCES,SPECS} and build there.
Jup this is no prob, I thought there is already something like osc build --no_chroot
But all these methods aren't fully deterministic dependency wise, hence these methods are strongly deprecated for generating rpms targeted to other systems (as long as they're not exact clones of your's).
I see that this is very important and the main reason to use osc at all. Nevertheless a quick build against / should be good enough for first tests. cu, Rudi -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday 09 December 2009, 19:17:44 Rüdiger Meier wrote:
On Wednesday 09 December 2009, Hans-Peter Jansen wrote:
On Wednesday 09 December 2009, 12:09:16 Rüdiger Meier wrote:
2. Using "osc build" on a local machine [...] Is it possible to build without being root somehow?
http://en.opensuse.org/Build_Service/Tutorial#Build_your_package_loca lly
The main problem is that I'm not root or rather don't want to do that as root on our production systems.
Did you noticed this paragraph: <cite> If you start the build as normal user (good idea!), you will be asked for the root password of your local machine. You can avoid that if you add your user to /etc/sudoers and edit your ~/.oscrc : su-wrapper = sudo and with visudo add the line (as root): <your login name> ALL = NOPASSWD: /usr/bin/build to the sudo configuration (of course without '<' and '>') </cite> Is it a problem to ask your admin for these simple mods? How do you manage to install the built rpms? Pete -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday 09 December 2009 21:31:33 Hans-Peter Jansen wrote:
On Wednesday 09 December 2009, 19:17:44 Rüdiger Meier wrote:
The main problem is that I'm not root or rather don't want to do that as root on our production systems.
Did you noticed this paragraph:
<cite> If you start the build as normal user (good idea!), you will be asked for the root password of your local machine. You can avoid that if you add your user to /etc/sudoers and edit your ~/.oscrc : su-wrapper = sudo
and with visudo add the line (as root): <your login name> ALL = NOPASSWD: /usr/bin/build </cite>
Jup, but I watched the script "/usr/bin/build" and think I should not run it as root on a machine which is productively used for something important. There is IMO a risk (which I can't yet clearly see) that some Makefile or whatever could run amok somehow. This is probably no risk unless I would set BUILD_ROOT="/". But moreover I see "/usr/bin/build" is using most commands without absolute paths which is dangerous. If "/usr/bin/build" would be safe to give that sudo permissions to an evil user when I would use it too without doubt. But no prob - I will use rpmbuild for local testing (like I did before knowing that nice osc) and opensuse build farm (or a dedicated build machine) for deterministic chrooted builds.
Is it a problem to ask your admin for these simple mods? I'm the admin :)
How do you manage to install the built rpms? Good point, of course I do with root permissions. Before installing non-official-packages I view at least the filelist and pre/post install scripts which usually does not take much time (in contrast to %build and %install section).
cu, Rudi -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (4)
-
Hans-Peter Jansen -
Karsten König -
Rüdiger Meier -
Will Stephenson