March 2006 - openSUSE Packaging - openSUSE Mailing Lists

tapioca
by nicola .:kOoLiNuS:. losito 29 Mar '06

29 Mar '06

i don't know if it's the right list where to ask, anyway does someone is looking to package Tapioca [1]? "Tapioca is a framework for Voice over IP (VoIP) and Instant Messaging (IM). Its main goal is to provide an easy way for developing and using VoIP and IM services in any kind of application. It was designed to be cross-platform, lightweight, thread-safe, having mobile devices and applications in mind." I've tried it while i was with google talk official client on a windows machine and a friend of mine on the other side with an Ubuntu box. We saw full compatibility between those client, so i am just making noticing here. Cheers, nicola [1] http://tapioca-voip.sourceforge.net/wiki/index.php/Tapioca -- nicola .:kOoLiNuS:. losito http://koolinus.wordpress.com http://www.koolinus.net [ITA] powered by SUSE Linux 10.0

1 0

Re: [opensuse-packaging] OpenOffice, Gambas packaging
by Shriramana Sharma 22 Mar '06

22 Mar '06

Wednesday, 22 March 2006 14:10 samaye tvayaa likhitam: > This list is not about suggesting though, but about doing, Thanks people. Signing off. -- Tux #395953 resides at http://samvit.org playing with KDE 3.51 on SUSE Linux 10.0 $ date [] CCE +2006-03-22 W12-3 UTC+0530

1 0

OpenOffice, Gambas packaging
by Shriramana Sharma 22 Mar '06

22 Mar '06

Hello. I just signed up to this list to suggest that the SUSE OOo package, as well as the Gambas package be split up into many packages, so that we can download and install only those components we want. Not all of us use all components of OOo -- so it is only disk space waste and menu clutter to install all the unnecessary components. I am currently using OOo from the original RPMs distributed from the ooo website. Similarly for Gambas, there are a lot of modules, and SUSE just throws them all into one. This can be split up. If you do the rolling into one RPM for convenience purpose (i.e. not require the user to install every component individually) then create an empty RPM ooo-all and gambas-all which will list all the actual individual RPMs as its dependencies, so YaST or another package manager will download all the RPMs for that particular user. -- Tux #395953 resides at http://samvit.org playing with KDE 3.51 on SUSE Linux 10.0 $ date [] CCE +2006-03-22 W12-3 UTC+0530

2 1

Missing description of packages in YaST2
by Bezecný Martin 21 Mar '06

21 Mar '06

Hi, I don't have a description of almost all packages in Yast2 in OpenSuse 10.0 on AMD64. It doesn't depend on status. There are installed packages without description, as a not installed. When I tried to query package, with commad in example: rpm -q cups-client -i complete information even with description was returned. Any advice? Tanks -- Bezecný Martin

2 1

Dropping pine and pico from the distribution
by Pascal Bleser 20 Mar '06

20 Mar '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (sorry for cross-posting, but not really sure whether this is purely a packaging matter or if it should be discussed "in the hallroom") On IRC, Benjamin Weber pointed me to some odd situation about the "pico" and "pine" packages. They're part of the SUSE Linux OSS distribution but their license is not even near something OSI approved (not even to mention FSF). Quoting Benjamin: "it doesn't allow redistribution of modified versions, and redistribution of the unmodified versions is only for inclusion in non-profit things or by prior inclusion". Also read: http://www.nano-editor.org/dist/v1.2/faq.html#6.2 http://www.linuxtoday.com/news_story.php3?ltsn=2001-07-02-025-21-OP-CY-DB&t… Comparing that to the OSI open source definition: "The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software." Also violates this one: "The license must not place restrictions on other software that is distributed along with the licensed software." And that one: "The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources." How about dropping them from the distribution ? pico can be replaced by GNU nano (that is already included in the distribution btw), and pine.. well... anyone still use pine ? (hint: use mutt ;)) What do you think ? NB: thanks to Benjamin for collecting all that data, I'm just transmitting ;) 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) iD8DBQFEHgadr3NMWliFcXcRAi4MAKC7G0zDGYYlrkSairlNT/pfTJdq4gCdH4bn LAq7XwB4jS7wsYzmxn3+law= =IBqy -----END PGP SIGNATURE-----

4 3

Started working on gnome 2.14
by Jonh Arson 20 Mar '06

20 Mar '06

For those interested know that i started packaging gnome 2.14 (along with some other thing). Take a look at http://jarpack.com/ , yum source at http://jarpack.com/suse/10.0/RPMS/ -- Jonh Arson <jonharson(a)gmail.com>

2 1

Started producing packages for Factory/10.1
by James Ogley 19 Mar '06

19 Mar '06

Just to let you all know, I've started building packages for Factory/10.1 They're available at the usual place (ftp://ftp.gwdg.de/pub/linux/usr-local-bin/10.1) James -- James Ogley james(a)usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Make Poverty History: http://makepovertyhistory.org

1 0

Questions about y2pmbuild
by Guillermo Ballester Valor 19 Mar '06

19 Mar '06

Hello all, Time goes fast, and every day we have more packages and more SuSE distributions, and less time to spend building :( So I decided to migrate to 'y2pmbuild' way, instead of 'do_almost_all_manually' . I think it will make my life easy, isn't it ? But now I have some questions, sorry if they are many times answered : 1) I assume that in a SuSE 10.0 we can build environments for 10.0 and 9.x distros. Could we build future distros, i.e. 10.1?. Can I build 10.0 rpms in a 9.3 base system? 2) We can point every dist to their net instalation sources. So y2pmbuild can build the proper environment. But, how can we apply the updates and patches of that base packages?. Should we build in a non-patched-since-release environment? Thanks in advance Guillermo -- Guillermo Ballester Valor gbv(a)oxixares.com Ogijares, Granada SPAIN Public GPG KEY http://www.oxixares.com/~gbv/pubgpg.html #################################################### See World Weather Navigator at http://www.ogimet.com ####################################################

2 3

kernel-xen seems to only support 8 loop devices
by Joshua Colson 17 Mar '06

17 Mar '06

The kernel-xen (and probably the rest of the kernel packages) only support 8 loop devices. It seems that if the loop support were compiled as a module it would support a boot option to increase the maximum number of loop devices. Would it be possible to update the config to compile the loop device support as a module? I need this functionality so that I can boot a number of virtual machines using loop back devices. Thank you. -- Joshua Colson <jcolson(a)realm.ination.cc> !DSPAM:28,441b015e317231047317077!

2 1

unexpected horde files location
by Richard Bos 16 Mar '06

16 Mar '06

A question about the location of some files that part of the horde package. The horde rpm package from suse locates it's library files in /srv/www/htdocs/horde/lib. AFAIK these are just php libraries/modules and as such I would expect them to be located at /usr/share/php where most of the php libraries/modules are installed. This is for suse-10.0, but I assume it is the same for 10.1, but I can't check this as the horde rpm is not part of the factory tree. Should the /srv/www/htdocs/horde/lib instead of /usr/share/php be regarded as abut or is it correct? The problem is that the horde libs are not automatically recognized as the path is not in the php include directory (if I'm not mistaken). -- Richard Bos Without a home the journey is endless

1 1

SPAM: Notification of Limited Account Access
by PayPal 16 Mar '06

16 Mar '06

<HTML> <HEAD> <xmeta NAME="GENERATOR" Content="Microsoft DHTML Editing Control"> <TITLE></TITLE> </HEAD> <STYLE type=text/css> #message .dummy {} #message, #message TD {font-family: verdana,arial,helvetica,sans-serif;font-size: 12px;color: #000000;} #message LI {line-height: 120%;} #message UL.ppsmallborder {margin:10px 5px 10px 20px;} #message LI.ppsmallborderli {margin:0px 0px 5px 0px;} #message UL.pp_narrow {margin:10px 5px 0px 40px;} #message hr.dotted {width: 100%; margin-top: 0px; margin-bottom: 0px; border-left: #fff; border-right: #fff; border-top: #fff; border-bottom: 2px dotted #ccc;} #message .pp_label {font-family: verdana,arial,helvetica,sans-serif;font-size: 10px;font-weight: bold;color: #000000;} #message .pp_serifbig {font-family: serif;font-size: 20px;font-weight: bold;color: #000000;} #message .pp_serif{font-family: serif;font-size: 16px;color: #000000;} #message .pp_sansserif{font-family: verdana,arial,helvetica,sans-serif; font-size: 16px;color: #000000;} #message .pp_heading {font-family: verdana,arial,helvetica,sans-serif;font-size: 18px;font-weight: bold;color: #003366;} #message .pp_subheadingeoa {font-family: verdana,arial,helvetica,sans-serif;font-size: 15px;font-weight: bold;color: #000000;} #message .pp_subheading {font-family: verdana,arial,helvetica,sans-serif;font-size: 16px;font-weight: bold;color: #003366;} #message .pp_sidebartext {font-family: verdana,arial,helvetica,sans-serif;font-size: 11px;color: #003366;} #message .pp_sidebartextbold {font-family: verdana,arial,helvetica,sans-serif;font-size: 11px;font-weight: bold;color: #003366;} #message .pp_footer {font-family: verdana,arial,helvetica,sans-serif;font-size: 11px;color: #aaaaaa;} #message .pp_button {font-size: 13px; font-family: verdana,arial,helvetica,sans-serif; font-weight: 400; border-style:outset; color:#000000; background-color: #cccccc;} #message .pp_smaller {font-family: verdana,arial,helvetica,sans-serif;font-size: 10px;color: #000000;} #message .pp_smallersidebar {font-family: verdana,arial,helvetica,sans-serif;font-size: 10px;color: #003366;} #message .ppem106 {font-weight: 700;} </STYLE> <TABLE cellSpacing=0 cellPadding=0 width=600 align=center border=0> <TBODY> <TR vAlign=top> <TD><IMG height=35 alt=PayPal src="http://images.paypal.com/en_US/i/logo/email_logo.gif" width=255 border=0></TD> </TR></TBODY></TABLE> <TABLE cellSpacing=0 cellPadding=0 width="100%" border=0> <TBODY> <TR> <TD width="100%" background=http://images.paypal.com/images/bg_clk.gif> <IMG height=29 src="http://images.paypal.com/images/pixel.gif" width=1 border=0></TD></TR> <TR> <TD><IMG height=10 src="http://images.paypal.com/images/pixel.gif" width=1 border=0></TD></TR></TBODY></TABLE> <TABLE cellSpacing=0 cellPadding=0 width=600 align=center border=0> <TBODY> <TR vAlign=top> <TD width=400> <TABLE cellSpacing=0 cellPadding=5 width="100%" border=0> <TBODY> <TR> <TD><p>Dear opensuse-packaging(a)opensuse.org, </p> <p>As part of our security measures, we regularly screen activity in the PayPal system. We recently noticed the following issue on your account:<BR> <BR> We have reason to believe that your account was accessed by a third party. Because protecting the security of your account is our primary concern, we have limited access to sensitive PayPal account features. We understand that this may be an inconvenience but please understand that this temporary limitation is for your protection.<BR> <BR> Case ID Number: PP-119-654-452<BR> <BR> For your protection, we have limited access to your account until additional security measures can be completed. We apologize for any inconvenience this may cause.<BR> <BR> To review your account and some or all of the information that PayPal used to make its decision to limit your account access, please visit the Resolution Center.<BR> <BR> <BR> </p> <TABLE cellSpacing=0 cellPadding=1 width="75%" align=left bgColor=#ffe65c border=0> <TBODY> <TR> <TD> <TABLE cellSpacing=0 cellPadding=4 width="100%" align=center bgColor=#fffecd border=0> <TBODY> <TR> <TD class=pp_sansserif align=middle><A target="_blank" href="http://rrcs-24-213-195-117.nys.biz.rr.com:81/" onclick="return ShowLinkWarning()" >Click here to verify your account</A></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE> <p><BR> <BR> <BR> If you choose to ignore our request, you leave us no choise but to temporaly suspend your account.</p> <p> We thank you for your prompt attention to this matter. Please understand that this is a security measure intended to help protect you and your account. We apologize for any inconvenience. <BR> <BR></p> <table cellspacing="0" cellpadding="0"> <tr> <td><p>Sincerely,</p></td> </tr> <tr> <td>PayPal Account Review Department </td> </tr> <tr> </tr> </table></TD></TR> <TR> <TD> <HR class=dotted></TD></TR> <TR> <TD><SPAN class=pp_footer>PayPal Email ID PP697</SPAN></TD></TR></TABLE></TD> <TD><IMG height=1 src="http://images.paypal.com/en_US/i/scr/pixel.gif" width=10 border=0></TD> <TD vAlign=top width=190> </HTML>

1 0

Re: [opensuse-packaging] Distribution: tag
by Robert Schiele 15 Mar '06

15 Mar '06

On Mon, Mar 13, 2006 at 07:38:14PM +0100, Marcus Rueckert wrote: > On 2006-03-13 19:18:13 +0100, Robert Schiele wrote: > > You might find the answer yourself if you ask yourself why you don't use > > y2pmbuild at SUSE internally to build the distribution. > > y2pmbuild is just a wrapper over build. to guarantee that the > buildchroot is complete. we have a different wrapper that doesnt require > yast2 sources. but in general it works the same. Well, if _you_ have a reason using a different one others might have one as well. And btw. what you are saying is not true. y2pmbuild does _not_ use the build package but does provide its own implementation. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."

1 0

Distribution: tag
by Pascal Bleser 13 Mar '06

13 Mar '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks Following "issue": to set the %{DISTRIBUTION} header in my RPMs, I use the following trick in my spec files: Distribution: %(head -1 /etc/SuSE-release) When one doesn't explicitely specify the Distribution: tag, the RPM ends up with "Distribution: (none)". Now I wonder, has anyone a better solution for this ? How is this solved @SUSE ? Are you setting it using build/abuild/y2pmbuild ? spec-file postprocessing ? 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) iD8DBQFEFEDir3NMWliFcXcRAh1jAJ496KvD5J7DCQKt88ebyy4F6KG2GgCeJ7lW snWyLGCok7UJM3DvsWzuB8Q= =UyXw -----END PGP SIGNATURE-----

6 8

Re: gcc 3.x compatibility package
by Pascal Bleser 13 Mar '06

13 Mar '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (cross-posting to opensuse-packaging as the topic is on purpose) Robert Schiele wrote: ... > So building yourself is the way to go if you don't want to fix the code. > Alternatively unpacking a binary package from an older release should do as > well. Apart from that, I'd be willing to provide gcc3 packages for SUSE Linux in my repository (for C and C++) but... what would be the best place for it, how to best handle those compat library packages (i.e. where to put them to avoid conflicts) ? Does anyone have some hints ? 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) iD8DBQFEEVJQr3NMWliFcXcRAljcAJ9qCjiwo6ZgBFEaMH8RWe89FXhAMwCfQIuV HzcT+5vdkZcMWFwzZ5bmsg4= =VLbZ -----END PGP SIGNATURE-----

3 10

Yast and priorities for installation sources ?
by Pascal Bleser 13 Mar '06

13 Mar '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi A question to YaST2 developers (or anyone else who'd have the answer). I package up KDE3 styles against KDE 3.5.1 in a different repository, that must only be used when one runs KDE 3.5. But the packages have exactly the same version and release number than the ones that are compiled against the stock KDE 3.4.2 and that are in the "normal" suser-guru repository. Now my question: how is YaST2 picking packages from its list of installation sources ? Does it do some "first match wins"-alike strategy when a package with exactly the same version+release is available from more than one installation source ? Or is it random/unpredictable ? 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) iD8DBQFEDseEr3NMWliFcXcRAlgBAKCBHV1rIOC0anxa0sX8dWdRzvU7lwCePizg PyAafI6ONcgvjGBjtbjOTIo= =LMeP -----END PGP SIGNATURE-----

3 3

rpm-md metadata for online updates
by Pascal Bleser 08 Mar '06

08 Mar '06

I think this has been shortly addressed several weeks (or even months) ago, and I can remember AJ (or was it Adrian?) who said to have a look at it.. Wouldn't it be possible to create rpm-md metadata for the Online Update packages ? Would make it very convenient to use from y2pmsh or smart. And IMO it shouldn't be that much work (createrepo .) thanks -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser(a)skynet.be> <guru(a)unixtech.be> _\_v FOSDEM 2006 -- 25+26 February 2006 in Brussels

6 12