openSUSE Packaging June 2006

packaging@lists.opensuse.org

24 participants
14 discussions

by Quentin Denis

hello! does anyone have an idea what is wrong with that? got serveral complaints but on my system it works fine: %post export GCONF_CONFIG_SOURCE="$(%{_bindir}/gconftool-2 --get-default-source)" %{_bindir}/gconftool-2 --makefile-install-rule \ "%{_sysconfdir}/gconf/schemas/%{name}.schemas" &>/dev/null || : /usr/bin/update-mime-database "%{_datadir}/mime" &>/dev/null || : %{_bindir}/update-desktop-database &>/dev/null || : /usr/bin/scrollkeeper-update -q &>/dev/null || : %preun export GCONF_CONFIG_SOURCE="$(%{_bindir}/gconftool-2 --get-default-source)" %{_bindir}/gconftool-2 --makefile-uninstall-rule \ "%{_sysconfdir}/gconf/schemas/%{name}.schemas" &>/dev/null || : %postun /usr/bin/update-mime-database "%{_datadir}/mime" &>/dev/null || : %{_bindir}/update-desktop-database &>/dev/null || : /usr/bin/scrollkeeper-update -q &>/dev/null || : regards, Quentin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging-help(a)opensuse.org

14 years, 8 months

[opensuse-packaging] problem to download many rpm from builservice source

by Marc Collin

hi i try to download a rpm and i get the url was not found..... i tried many rpm from kde and other project...... game same result for all rpm i tried at: http://software.opensuse.org/download/KDE:/KDE3/SUSE_Linux_10.1/x86_64/ i seem to be redirected to a bad server 90% of the time... any way to resolve that? thanks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging-help(a)opensuse.org

14 years, 8 months

[opensuse-packaging] Versioned provides ??

by Volker Kuhlmann

Ok so we have a bunch of packages which require X, but X is already on the system, albeit without a Provide. That sounds like an obvious workaround of compiling Name: rpmlib-missingdep Version: suse10.1 Release: 1 BuildArchitectures: noarch Provides: rpmlib(PatchRPMs) = 3.0.6-1 Summary: Provides missing dependency for SUSE 10.1 rpm 4.4.2-40 into a package and installing that. # rpm -q --provides rpmlib-missingdep rpmlib(PatchRPMs) = 3.0.6-1 rpmlib-missingdep = suse10.1-1 But it doesn't work: # rpm -UvhF x86_64/fontconfig-2.3.94-18.4.x86_64.patch.rpm --test error: Failed dependencies: rpmlib(PatchRPMs) <= 3.0.6-1 is needed by fontconfig-2.3.94-18.4.x86_64 Exit 1 Nevertheless all hell breaks lose when trying to remove it: # rpm -e rpmlib-missingdep What's the trick here? Thanks, Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging-help(a)opensuse.org

14 years, 8 months

[opensuse-packaging] Automatically installing "plugins" via dependencies

by Michal Marek

Hi, does anyone an idea how to solve situations like this in a "right way"? There is an application A and a library L and libL-plugin for app A. The user installs A and L and wants to use L features from A. Another user installs just A and is not interrested in L. Now if A would require or recommend libL-plugin, then installing A would automatically pull the (possibly big and unwanted) library L. Requiring or recommending libL-plugin in L would have the same problem. To give a real example: A = unixODBC L = mysql-shared (or postgresql-libs) libL-plugin = MyODBC-unixODBC (or psqlODBC) Both unixODBC and mysql-shared can be used without each other, but the user somehow expects, that if he or she installs unixODBC and mysql-shared, it will simply work with each other. See this bug: https://bugzilla.novell.com/show_bug.cgi?id=144602 Other example is php5 and it's extensions (databases again for example), some multimedia players and codec libraries probably have a similar problem. Any ideas? -- Michal Marek SuSE CR --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging-help(a)opensuse.org

14 years, 8 months

[opensuse-packaging] Re: About Gnome packaging

by James Ogley

On Tue, 2006-06-13 at 14:21 -0400, Jonh Arson wrote: > Alright then, i started to move my stuff over to 2.15 yesterday and did > a bit this morning too, working on the platform ATM updated glib, cairo, > glitz, gnome-keyring, poppler, and some more stuff to get the 2.9 branch > of gtk to work still clashing on pango need to contact gcj team and make > it so swing doesn't get pull as a dep of gettext. > > Should i move all my stuff to /usr already ? i prefer to not screw with > that now personally. Taking this to opensuse-packaging, Stanislav do you have a view on this? -- James Ogley james(a)usr-local-bin.org http://usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Help end poverty: http://oxfam.org.uk/imin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging-help(a)opensuse.org

14 years, 8 months

[opensuse-packaging] TaskJuggler should be a default install for SUSE 10.2

by Mat Gray

Dear Sir, I was very disappointed to find that TaskJuggler was not a default install on SUSE 10.1. For very large projects, that are heavily interlinked, and change drastically on a week by week basis a GUI driven Project Management tool is simply unusable. The text driven interface of TJ allows me to rapidly make vast changes to my project plan, repeatedly, something that would take 10x as long using a GUI such as happens in Mr Project. I can understand a desire to rationalise overlapping tools, such as having 5 different types of word processors, but i want you to understand that TJ is complimentary to Mr Project, and that together along with Mind-Mapping and Flow-Charting tools they provide a comprehensive Project Management suite. I would like this to be considered as strong representation from a SUSE business user that future SUSE releases should include TaskJuggler as a default installed application. Kind regards. Matthew Gray (OD) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging-help(a)opensuse.org

14 years, 8 months

[opensuse-packaging] help getting started

by fblaise＠madpenguin.org

Hi all New to the packaging world. Would like to build a few packages, such as gnomebaker (yes, one exists, but what the hell :>), LAT and firestarter. I read the tutorial on the opensuse wiki, but am wondering what url to put in these url_* lines. Can someone help me determine what I need to build my environment. I am looking for logic so that I can reproduce it without bothering people :) Thanks fred --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging-help(a)opensuse.org

14 years, 8 months

[opensuse-packaging] The return of usr-local-bin

by James Ogley

Hi guys, As people will have noticed I've been the epitome of inactivity on the packaging front for the last couple of months since my build machine suffered a catastrophic hardware failure. The good news is that next week I should commission a replacement machine and be back in business. Expect the usual bleeding-edge versions of GNOME apps, including some of the smaller bits & bobs that just make the desktop a friendlier place to be (mail-notification anyone?). The great news of course is that with each successive version of SUSE this is a smaller and smaller job for me as the GNOME setup keeps getting better and better. One thing I can't promise though is a full GNOME 2.14 (or even 2.15) build - don't know if I'll have the time. That said, the last time I did a complete set of desktop packages it only took two days so you never know... James -- James Ogley james(a)usr-local-bin.org http://usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Help end poverty: http://oxfam.org.uk/imin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging-help(a)opensuse.org

14 years, 8 months

Secure/signed installation sources woes

by Pascal Bleser

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Trying to add signatures to my (yast2) RPM repository for 10.1. http://en.opensuse.org/Secure_Installation_Sources A couple of unclear things in there I'd like to poke on. ========= "When YaST detects an installation source it checks if the file "products" is there, and then checks if it is signed with a known key. If it is not signed at all or with an unknown key, or if the key is on the media, but not trusted (yet), the user will be asked what to do." "The key is usually also on the installation media as /gpg-pubkey-9c800aca-40d8063e.asc" What it doesn't say clearly is where/how YaST2 will try to fetch the armored/exported key in order to propose importing it. I assume it uses whatever is defined in "content" using the "KEY" tag (see below). Correct ? ========= "The "content" file is signed in the same manner as the "products" file, so there is a "content.key" (usually, but not necessarily the same as "products.key")." Those "content.key"/"products.key" files are not mentioned anywhere else. Are those copies of the ASCII-armored, exported GPG key ? ========= "META keys are added for all files in the directory named in the key DESCRDIR" So in "content" I should have something like: ... DESCRDIR setup/descr KEY SHA1 33ad20fe228350dc4e0f0cd7967460c31266af36 gpg-pubkey-guru.asc META SHA1 4baafd9998ea4e20245f82e507c6db6b723f4597 packages META SHA1 965ba5faeea815d41ba308ffd193b78505b26c1c directory.yast META SHA1 4565f769ae573f89dddbf2eef1357b59a88ad1df packages.DU META SHA1 c53400cdb9e16ac0d9add587585fc77c86f132c5 packages.en Correct ? ========= "Before YaST uses any file from DESCRDIR it will look up the entry in "content". This entry is currently a SHA1 checksum followed by the package name. This may change to a SHA256 checksum." A "package" name ? I suppose what is meant here is "file" name. Is it ? ========= "The next step in the chain is the file "packages" in DESCRDIR. If you are familiar with its syntax you will see that we added a new tag there, too, right after the "Pgk:" tag. Here is an example of the first two lines of the entry for the default kernel: =Pkg: kernel-default 2.6.16 13 i586 =Cks: SHA1 8c8eb2b605e1d626c22bea8dd0c3b05885432b16 Again we have a SHA1 checksum." Maybe it should be mentioned that one must use create_package_descr from 10.1 or Factory (I only checked the one from autoyast2-2.13.59.tar.bz2) What about older versions ? If I use create_package_descr from 10.1/Factory, that adds those =Cks: tags into the "packages" file, can I also use it to generate "packages" for, say, 10.0/9.3/9.2/9.1 ? Or will YaST2 on 10.0 and older bark, saying that it does not know anything about the "=Cks:" tag ? cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser(a)skynet.be> <guru(a)unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEdcqur3NMWliFcXcRAipAAJ9zpDlujVLHfvUyGqzVevt23Y3fUgCfcBvf /6CbxUT9RXz8ZjXc+Kor0/Q= =nzgd -----END PGP SIGNATURE-----

14 years, 8 months

[opensuse-packaging] Unoffical OpenOffice RPMs

by Pascal Bleser

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi I was just wondering about the latest (and unofficial+unsupported) OpenOffice.org builds, that are available here: http://ftp.suse.com/pub/projects/OpenOffice.org/ The maintainer seems to be Petr Mladek <pmladek(a)suse.cz> (Petr, that's why I've taken you in CC: ;)) - if not, please let me know. Are those going to be moved to the Build Service ? If not, would it be possible to generate RPM-MD metadata in that directory ? Currently, the only option to have a repository that holds those packages is to use the APT-RPM repositories at gwdg.de That's fine, but suse.com/projects is mirrored on a lot more servers, so I would prefer to use and reference an RPM-MD repository that's created right there. Thanks :) cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser(a)skynet.be> <guru(a)unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEhhEPr3NMWliFcXcRAhhZAKCLlp0UVTBBGjj8VNxjNttsDZ4KHwCgh2BF FU1CN+Ahs53sdZoSO3934Jc= =yedi -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging-help(a)opensuse.org

14 years, 8 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging June 2006