Re: [Cooker] Uploading question

2003-07-08 Thread Abel Cheung
On 2003-07-07(Mon) 22:17:35 -0400, Levi Ramsey wrote:
  If I'm submitting a change to an existing package, and the packager is 
  Mandrake Linux Team http://www.mandrakeexpert.com (e.g., libsigc++1.2), 
  what do I do with the specfile? Mail it to the last name on the changelog? 
 
 I would suggest looking at the last 3 real changelog entries (by real, I
 mean non-automatic rebuild for new rpm or whatnot, and not lib64-type
 stuff), and send it to the address that appears twice in those three.

Yes, more usual than not, you'll get attention this way; while mailing
to official maintainers is equivalent to mailing to /dev/null.

Abel


-- 
Abel Cheung
Linux counter #256983   | http://counter.li.org
GPG Key: (0xC67186FF)   | http://deaddog.org/gpg.asc
Key fingerprint: 671C C7AE EFB5 110C D6D1  41EE 4152 E1F1 C671 86FF


pgp0.pgp
Description: PGP signature


Re: [Cooker] Uploading question

2003-07-08 Thread Michael Scherer

 If I'm submitting a change to an existing package, and the packager
 is Mandrake Linux Team http://www.mandrakeexpert.com (e.g.,
 libsigc++1.2), what do I do with the specfile? Mail it to the last
 name on the changelog? Upload it to incoming? Both?

use the force, or rpmmon.

There is a rpm for the secund.

[EMAIL PROTECTED] misc]$ rpmmon -p libsigc++1.2
[EMAIL PROTECTED]


-- 

Michaël Scherer




Re: [Cooker] Uploading question

2003-07-08 Thread Ben Reser
On Tue, Jul 08, 2003 at 08:13:40AM +0200, Michael Scherer wrote:
 
  If I'm submitting a change to an existing package, and the packager
  is Mandrake Linux Team http://www.mandrakeexpert.com (e.g.,
  libsigc++1.2), what do I do with the specfile? Mail it to the last
  name on the changelog? Upload it to incoming? Both?
 
 use the force, or rpmmon.
 
 There is a rpm for the secund.
 
 [EMAIL PROTECTED] misc]$ rpmmon -p libsigc++1.2
 [EMAIL PROTECTED]

Or even easier for those that have no reason to bother to install
rpmmon:
http://ben.reser.org/mandrake/rpmmon/

-- 
Ben Reser [EMAIL PROTECTED]
http://ben.reser.org

What upsets me is not that you lied to me, but that from now on I can
no longer believe you. -- Nietzsche



Re: [Cooker] Uploading question

2003-07-08 Thread Lyvim Xaphir
On Tue, 2003-07-08 at 03:56, Ben Reser wrote:
 On Tue, Jul 08, 2003 at 08:13:40AM +0200, Michael Scherer wrote:
  
   If I'm submitting a change to an existing package, and the packager
   is Mandrake Linux Team http://www.mandrakeexpert.com (e.g.,
   libsigc++1.2), what do I do with the specfile? Mail it to the last
   name on the changelog? Upload it to incoming? Both?
  
  use the force, or rpmmon.
  
  There is a rpm for the secund.
  
  [EMAIL PROTECTED] misc]$ rpmmon -p libsigc++1.2
  [EMAIL PROTECTED]
 
 Or even easier for those that have no reason to bother to install
 rpmmon:
 http://ben.reser.org/mandrake/rpmmon/


 What upsets me is not that you lied to me, but that from now on I
  can no longer believe you. -- Nietzsche

That's one hell of a sig, Ben Reser.  Can I use it sometime.


--LX
-- 
°°°
Linux Mandrake 9.1  Kernel 2.4.21-0.13mdk
*Catch Star Trek Enterprise, Wednesdays on UPN*





[Cooker] Uploading question

2003-07-07 Thread Andi Payn
OK, let me make sure I have the procedure straight:

If I'm submitting a new contribution, I upload the SRPM to incoming, and send 
an email to [EMAIL PROTECTED] and [EMAIL PROTECTED]

If I'm submitting a change to an existing package, I email the specfile to the 
packager, and send an email to cooker. (So the new gimp specs go to Thierry 
Vignaud.)

If I'm submitting a change to an existing package, and the packager is 
Mandrake Linux Team http://www.mandrakeexpert.com (e.g., libsigc++1.2), 
what do I do with the specfile? Mail it to the last name on the changelog? 
Upload it to incoming? Both?




Re: [Cooker] Uploading question

2003-07-07 Thread Austin
On 2003.07.07 18:42, Andi Payn wrote:
If I'm submitting a change to an existing package, and the packager is
Mandrake Linux Team http://www.mandrakeexpert.com (e.g., libsigc++1.2),
what do I do with the specfile? Mail it to the last name on the changelog?
Upload it to incoming? Both?
/incoming is Lenny, essentially.  He's a busy guy, and he hesitates to mess 
with important packages like the gimp.  You can send whatever you want to /
incoming, but IF it gets updated, it will likely take a while.

I'd suggest this:
If it's a main package, send it to the maintainer (usually the last or most 
frequent changelog entry).
If it's a contrib package, send it to me.

Cool?

Austin

--
Austin Acton Hon.B.Sc.
 Synthetic Organic Chemist, Teaching Assistant
   Department of Chemistry, York University, Toronto
 MandrakeClub Volunteer (www.mandrakeclub.com)
 homepage: www.groundstate.ca


Re: [Cooker] Uploading question

2003-07-07 Thread Austin
Shit, that was supposed to be to andi, not cooker.
I'm an ass.
Austin

--
Austin Acton Hon.B.Sc.
 Synthetic Organic Chemist, Teaching Assistant
   Department of Chemistry, York University, Toronto
 MandrakeClub Volunteer (www.mandrakeclub.com)
 homepage: www.groundstate.ca


Re: [Cooker] Uploading question

2003-07-07 Thread Levi Ramsey
On Mon Jul 07 15:42 -0700, Andi Payn wrote:
 If I'm submitting a change to an existing package, and the packager is 
 Mandrake Linux Team http://www.mandrakeexpert.com (e.g., libsigc++1.2), 
 what do I do with the specfile? Mail it to the last name on the changelog? 

I would suggest looking at the last 3 real changelog entries (by real, I
mean non-automatic rebuild for new rpm or whatnot, and not lib64-type
stuff), and send it to the address that appears twice in those three.

-- 
Levi Ramsey
[EMAIL PROTECTED]   [EMAIL PROTECTED]

Take due notice and govern yourselves accordingly.
Currently playing: Corrosion of Conformity - Wiseblood - Long Whip - B
Linux 2.4.21-0.15mdk
 22:15:00 up 2 days,  9:51,  6 users,  load average: 0.11, 0.20, 0.14