November 2011 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] split of ncurses library
by Stephan Kulow 25 Nov '11

25 Nov '11

Hi, Werner split libltinfo from libncurses and so we see a lot of build failures due to programs linking -lncurses and expecting functions there that are now in -lltinfo and as library dependencies are not longer taken into account, there is a huge fallout. The right fix is to use ncurses-config --libs - note that Fedora and debian have the same split, so packages failing have a high chance of having a patch floating around in the internet :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

11 22

[opensuse-packaging] skrooge update failed (obs doesn't find files in packagelist)
by Sascha Manns 25 Nov '11

25 Nov '11

Hello mates, today i've tried to build skrooge 1.1.0. But sadly the present build in KDE:Extra failed. The buildlog can found there: https://build.opensuse.org/package/rawlog?arch=i586&package=skrooge&project… It looks like he doesn't find my *.po files and other stuff. But it is placed in my %files section. In the past i also ignored debug files. Must i place these packages in the %files section or can i ignore it? Have a nice evening Sascha -- Sincerly yours Sascha Manns Community &Support Agent open-slx GmbH http://www.open-slx.de This mail is written with Balsam Professional 12.1

2 2

[opensuse-packaging] Chromium package in openSUSE releases
by Raymond Wooninck 25 Nov '11

25 Nov '11

With openSUSE 12.1 the Chromium browser became part of the openSUSE release, after spending quite some time in the openSUSE:<release>:Contrib repositories. Unfortunately a bug report was created (bnc#731832), where an user complains that openSUSE is releasing an alpha version of the Chromium browser and that this should be a stable version. It seems that the reporter bases his statement on the fact how Ubuntu, Archlinux and Debian are handling the Chromium browser. This seems to be complete based on the Chrome browser. I did some digging of my own and I found the following webpage that explains the release management behind Chrome and Chromium (http://ftagada.wordpress.com/2011/01/19/chromium-release-management- explained/) Half way the page is the following indicated: "I (the author, an Ubuntu packager) said in the introduction that there is no such thing upstream. They have enough in their plate with just Chrome. So it is up to each downstream distribution to decide what is best for its users." So officially there are no alpha, beta or stable versions of Chromium and it is up to each dsitribution to decide what they want to ship. For openSUSE 12.1 it is too late to change anything here as that this would mean that existing users might experience loss-of-data as that their profiles are not compatible with lower versions of Chromium. However for the upcoming 12.2 release there is still time to decide which way openSUSE wants to go. At this moment I see three possibilities: 1) Keep things the way they are. Chromium will be updated regularly to the latest available version. No change from the current procedure 2) openSUSE will use the Chrome release management and the Chromium package will be frozen until the Stable version has reached the current version of Chromium. Then this is the package that will be maintained from that moment onwards. 3) We have a mixture of the above. In the Chromium devel-project (network:chromium), two packages are maintained. The first package chromium will follow the stable releases and a second package chromium-unstable will follow the current procedure and gets a weekly update. However the chromium- unstable package will never be submitted to Factory. Before making m choice in what to provide, I would like to have your feedback on how to continue this. Honestly speaking I do not like option 3 as that this would mean double the work for me, but it is a possibility. Thanks Regards Raymond (tittiatcoke) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 10

Re: [opensuse-project] Re: [opensuse-packaging] Chromium package in openSUSE releases
by Sankar P 24 Nov '11

24 Nov '11

> > > > Right now, > > > > -> openSUSE community is spending effort to give chromium for openSUSE > > "openSUSE community" == Raymond (??) > > Is this correct? I mean, what's raymond stance towards this? This > seems a huge falacy. Might work from the 'engineering' point of view, > but from a motivational perspective, I have some doubts. > Yes, Raymond and everyone else who works on bringing chromium to openSUSE. > > -> Chrome community is spending effort to give Chrome for openSUSE > > That's maybe a project management requirement from Chrome (to give a > offer for most popular Linux platforms)... But, they never really > cared/fixed the libpng12 issue, which somehow challenges your > statement. If they were really spending efforts into openSUSE, they > would have a Requires on the rpm for libpng12. > > Furthermore, do you believe it's fair to compare a product from Google > (which has a whole team and project management behind) with a > volunteer contribution like Raymond's? > The objective is common for both. To bring Chrom[e/ium] to openSUSE. Some work on personal time and some are paid to do that. > I think we're running into way too much falacies. > > > > > -> There are no patches added by openSUSE to customize chromium > > -> Chrome development is going on at a rapid pace > > Sure there's no patches, but there's probably hundreds of hours of > work on it from contributors. Let's just trash them because we find > out that Chrome is a better option ? > Nope. I merely recommended to redirect those hundreds-of-hours in a different place, but still relevant to openSUSE. > > > > So, instead of working on two different places to make Chrome available for > *openSUSE* users, we should focus on just one place so that it will be more > efficient. Much like, two people digging a water-well in one place instead of > two different places. > > Chrome != Chromium ? > > Now why should you or anyone else impose to a volunteer contributor > what or what they should or shouldn't do with their contributions? Now > we have everyone enforcing project management decisions ? Are we > community Linux or corporate linux? > Who enforced any decision ? If I have said, "Hey Raymond, now go and work with the Chrome community and get openSUSE rpms from there", it will be enforcing my decision. I merely suggested, [with a "out-of-the-box thinking" label], if we should just get packages from Chrome upstream, instead of building them ourselves. I have suggested the same earlier for Eclipse too when Stephen Shaw tried to get them built on OBS for openSUSE. Also, my decisions are not as respectful as a project manager decision :-) I am a mere humble contributor working in freetime, just like you. > Please enlighten me... You are a part of the Marketing team, so you > know the answers better than I do. > I am not officially part of the Marketing team. I have not even sent any mail to the marketing team (except for 12.1 release notes as part of the GNOME team). I do not represent them in any form. I just distribute DVDs which I used to do even before a marketing team was formed. > > > Also, I do not intend to block Raymond. I am merely recommending him to > work with the Chrome community who is already giving RPMs for openSUSE. It is > just a proposal and he can happily reject it as he wish. > > You use Chrome or Chromium? Sounds fishy... to me it looks like you > are trying to get in openSUSE the stuff you use in disfavor of a > competitor product that you don't use but that others might use... What competitor product ? Chrome and Chromium ? They are from the same project. Chromium is the name of the project. Chrome is the name of the release which is done by Google. A particular build configuration of Chromium sources + some codecs is called the Chrome browser release. They are not competing products. > > Are the Chrome/Chromium Licenses the same? Which one should we favor? > > Sankar, you are a member of the Marketing Team, I expect you or any > other marketing contributor to be aware of the motivational factors > and their impact in present or future volunteer contributor... > Marketing isn't about posting news or making buzzes throught the > world... it goes far beyond it, it would be interesting that people > actually consider what they are supposed to consider and not only > follow a narrow perspective and claim they are marketeers... How would > I know that ? > Please the next answer :-) > > PS: we're just discussing hopefully in a constructive way and > confronting ideas, this is not a personal attack, I hope that is > clear. > I did not take any offence. I rarely feel offended ;-) But I've something to share. If I see things with pre-conceived negative notions, I will always find fault and will complain, even if the cause was good. I will see ghosts when there are none. In a similar way, my suggestion to work with the chromium project instead of building chromium ourselves is just a suggestion from a community member (me) to Raymond. The marketing team or project management has nothing to do with it. Even if they want to say something, it will be represented by them in a more formal way than via me. But because of your unplesant memories about marketing team or some openSUSE project decisions, you are assuming that I am trying to stop Raymond (or others) from working for openSUSE. I can assure you, it is not. This mail thread has crossed levels of sanity and before http://psankar.blogspot.com/2009/08/most-wanted-feature.html blocks it, we should stop. The conclusion is: 1) Sankar made a suggestion. Raymond will reject or accept it, IOW, will do what Raymond feels best. 2) Nelson was unhappy about the suggestion. Sankar tried to convince him that the reasons are nothing political. 3) Everyone decided to respect the decision of Raymond and get back to spending their evenings doing constructive things :) Thanks. Sorry to everyone else who had to hear the noise. This will be the last mail from me in this thread. Sankar > > > > > I understand that you may be unhappy with the board/foundation related > happenings in openSUSE, but trust me, my mail has nothing related to any of > it. Read through my previous mails once again with an clear mindset and see > if you find anything other than trying to get best Chrome experience on > openSUSE. > > This is not related to you, it meant in a general perspective... > People want to do a lot of stuff but in the end nothing happens > (happened to me also with GNOME:Ayatana). > > > > > Have Fun :-) > > > > Sankar > > > > P.S: I have been using Chrome from Google during 11.4 and even now on my > 12.1 box without any issues. So I am not really sure what the problem you > referred to was. Even if there was a problem, I am sure the chromium > community will be happy to fix it, for the benefit of the openSUSE users. > > > > > > > > -- > Nelson Marques > > /* http://www.marques.so > nmo.marques(a)gmail.com */ > > -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

Re: [opensuse-project] Re: [opensuse-packaging] Chromium package in openSUSE releases
by Sankar P 24 Nov '11

24 Nov '11

>> Chrome project already gives 32-bit and 64-bit dev and beta builds for > openSUSE (and fedora). We can just work with those chrome packagers instead > of building it ourselves. I see no benefit in building chrome by ourselves. > If we are paranoid about chrome recording few things that we do, we should > ideally use a different browser, like Firefox > > I hope I never see you in the future trying to promote people to get > enrolled with openSUSE or crying about the lack of it... Because such > attitudes just make contributors run away... Raymond (and many others) > work and efforts should be rewarded, and situations like the one you > suggest doesn't sound like a reward. > > I've been noticing openSUSE is closing all the channels for free > contributors... If you SUSE/Novell/Attachmate or whoever is pushing > the hidden agenda's want to block contributors, then just state what > you are trying to accomplish, because most of what I ear is play > bullshit and everyone is loosing credibility (one example: the current > board and the Foundation to be done during this year). Take a deep breath :-) Right now, -> openSUSE community is spending effort to give chromium for openSUSE -> Chrome community is spending effort to give Chrome for openSUSE -> There are no patches added by openSUSE to customize chromium -> Chrome development is going on at a rapid pace So, instead of working on two different places to make Chrome available for *openSUSE* users, we should focus on just one place so that it will be more efficient. Much like, two people digging a water-well in one place instead of two different places. Also, I do not intend to block Raymond. I am merely recommending him to work with the Chrome community who is already giving RPMs for openSUSE. It is just a proposal and he can happily reject it as he wish. I understand that you may be unhappy with the board/foundation related happenings in openSUSE, but trust me, my mail has nothing related to any of it. Read through my previous mails once again with an clear mindset and see if you find anything other than trying to get best Chrome experience on openSUSE. Have Fun :-) Sankar P.S: I have been using Chrome from Google during 11.4 and even now on my 12.1 box without any issues. So I am not really sure what the problem you referred to was. Even if there was a problem, I am sure the chromium community will be happy to fix it, for the benefit of the openSUSE users. -- 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] ANNOUNCE: stricter tests done by factory-auto
by Stephan Kulow 23 Nov '11

23 Nov '11

Hi, I've spent the day implementing a long overdue TODO: adding more checks to the script behind factory-auto. I check now the source_validator output, the download_files (if the Source* urls are valid) and various other things. Among them: openSUSE:Factory/FooBar needs to have FooBar.spec, FooBar.changes and Name: FooBar in FooBar.spec (there might be additional spec files) Factory packages shall not have a Vendor tag, but need to contain a copyright and license (for those I added some heuristics that I hope work for most cases). We need to have a %changelog line in the spec file and of course the package needs to have succeeded. Please watch factory-auto declines (for now they will be under user coolo, but I plan to create an extra user for that soon) and notify me if you think the decline is wrong. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 1

[opensuse-packaging] My first factory package update. Help please.
by Greg Freemyer 22 Nov '11

22 Nov '11

I'm attempting my first package update and it got rejected. I don't understand some of Coolo's statements, so I'm hoping for clarification from the experts here. See interspersed: ---------- Forwarded message ---------- >> From: <coolo(a)suse.com> >> Date: Fri, Nov 18, 2011 at 3:23 AM >> Subject: [obs submit-request 92004] openSUSE:Factory/perl-Image-ExifTool: declined by coolo >> To: Greg.Freemyer(a)gmail.com >> >> >> >> State of submit-request #92004 was changed by coolo: >> >> review -> declined >> >> Comment: >> do not require package names, but require perl(IO::Compress) - and wait for it to land in Factory (I just submitted it). I understand that part. >> And add provides/obsoletes for exiftool in there - and add a deleterequest for it. We don't need the tool twice in factory This has me lost. perl-Image-ExifTool v8.40 is already in factory. I'm just upgrading it to 8.65. Admittedly there is a new executable (/usr/bin/exiftool) that was not there before. I can add a provides statement easily enough, but why do I need a obsoletes and why do I need a deleterequest. I'm just trying to update an existing perl package (devel:languages:perl / perl-Image-ExifTool). >> https://build.opensuse.org/request/diff/92004 >> >> Source >> project: devel:languages:perl >> package: perl-Image-ExifTool >> revision: 5 >> >> Target: >> project: openSUSE:Factory >> package: perl-Image-ExifTool Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 4

[opensuse-packaging] Getting rid of /etc/tmpdirs.d
by Andreas Jaeger 22 Nov '11

22 Nov '11

We currently use both /etc/tmpdirs.d and /usr/lib/tmpfiles.d - the first for SysVinit, the second for systemd. I suggest to drop /etc/tmpdirs.d completely (after taking care that the files are listed in tmpfiles.d The question is how to create the directories when booting with SysVinit. We have two options: 1) Run /bin/systemd-tmpfiles from systemd to create these 2) Add some shell magic that reads and parses the tmpfiles.d and creates those. Since I see that systemd is already - even if not used by default - required by a couple of packages, I'm going with the first option. This was triggered by a bug in screen where screen did not create the needed directories at install time, they were created only at boot time. I'll fix now all packages - and take care of the %post section as well. Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 10

[opensuse-packaging] How to link to EPEL
by Schlomo Schapiro 22 Nov '11

22 Nov '11

Hi, I need to build a couple of RHEL packages, how could I link in the EPEL repositories so that I don't have to add all the EPEL packages that are needed? Regards, Schlomo -- 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] Desktop-related macros for scriptlets
by Vincent Untz 20 Nov '11

20 Nov '11

Hi, Something I probably failed to document properly in 11.4 is the new macros that got introduced for desktop-related things (some of them being, arguably, GTK+-only). They were introduced to fix various issues, and move away from the SuSEconfig scripts. With rpm 4.9, we might be able to use another solution. In that case, the macros listed below will just expand to an empty string and do nothing. So it won't harm to use them either. Desktop-related macros ====================== a) Package installs a .desktop file in /usr/share/applications Macros: %desktop_database_post/%desktop_database_postun What it does: calls update-desktop-database to update a cache mapping MIME types to apps handling them. This is needed to make the desktops aware that an app can handle a MIME type. b) Package installs a MIME definition (in /usr/share/mime): Macros: %mime_database_post/%mime_database_postun What it does: calls update-mime-database to update the database containing information about all MIME definitions. c) Package installs an icon in hicolor (/usr/share/icons/hicolor): Macros: %icon_theme_cache_post/%icon_theme_cache_postun What it does: calls gtk-update-icon-cache (if existing) to update the GTK+ icon cache for hicolor, as specified by the spec. This is needed to make the icon visible to GTK+ apps. d) Package installs an icon in another icon theme (let's say "geeko" theme, /usr/share/icons/geeko) Macros: %icon_theme_cache_post geeko / %icon_theme_cache_postun geeko What it does: calls gtk-update-icon-cache (if existing) to update the GTK+ icon cache for geeko. This is needed to make the icon visible to GTK+ apps. e) Package installs a GSettings schema (in /usr/share/glib-2.0/schemas): Macros: %glib2_gsettings_schema_post/%glib2_gsettings_schema_postun %glib2_gsettings_schema_requires (similar to %py_requires) What it does: calls glib-compile-schemas to build the blob containing the data for all schemas. This is needed to have your app not crash :-) f) Package installs a gio module (in /usr/lib/gio/modules): Macros: %glib2_gio_module_post/%glib2_gio_module_postun %glib2_gio_module_requires (similar to %py_requires) What it does: calls gio-querymodules to update a cache listing all gio modules and the extension points they are using. This is needed to make the gio module known to gio. g) Package installs a gdk-pixbuf loader (in /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders): Macros: %gdk_pixbuf_loader_post/%gdk_pixbuf_loader_postun %gdk_pixbuf_loader_requires (similar to %py_requires) What it does: calls gdk-pixbuf-query-loaders to update a cache listing all gdk-pixbuf loaders and their abilities. This is needed to make the gdk-pixbuf loader known to gdk-pixbuf. h) Package installs a GTK+ (2 or 3) IM module (in /usr/lib/gtk-2.0/2.10.0/immodules or /usr/lib/gtk-3.0/3.0.0/immodules): Macros: %gtk2_immodule_post/%gtk2_immodule_postun %gtk2_immodule_requires %gtk3_immodule_post/%gtk3_immodule_postun %gtk3_immodule_requires What it does: calls gtk-query-immodules-2.0/gtk-query-immodules-3.0 to build a cache listing all IM modules and the locale/language they apply to. You obviously need to only call the gtk2/gtk3 version, depending on which version of GTK+ you target. This is needed to make the IM module known to GTK+. i) Package installs a pango module (in /usr/lib/pango/1.6.0/modules): Macros: %pango_module_post/%pango_module_postun %pango_module_requires (similar to %py_requires) What it does: calls pango-querymodules to update a cache listing all pango modules and information about what they handle. This is needed to make the module known to pango. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- 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

5 10