March 2006 - openSUSE Packaging - openSUSE Mailing Lists

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