Subject: A few questions from a newbie...

From: llucius <[email-masked]>
Date: Thu, 13 Jun 1996 22:58:05 -0500 (CDT)

Howdy,

I've just started getting involved with you folks and have read the guidelines
for preparing packages, but I'm still a bit confused on a few points.  Would
some kind sole set me straigt?

Let's suppose for an instant that I have about 75 .deb files compiled for us 
m68k users.  (I will be redoing some to add architecture to control files and
binary package names.)

1)  Should I upload these to master?
2)  What guidelines should be followed when doing this?
3)  Is a "changes" file required for such an upload since nothing really
    changed?
4)  If so, what should the "changes" file contain?

Thanks,

Leland Lucius

__ Y_ a_ m_ b_ o_ | The leanest, meanest, fightinest sweet tater on Earth!
   oo o  oo o  o  | 
    o       o   o | [email-masked]
 o oo    o     o  | 
-- -- -- -- -- -- | http://www.millcomm.com/~llucius       (maybe one day)

---

From: Juergen Menden <[email-masked]>
Date: Fri, 14 Jun 1996 10:01:22 +0200 (MET DST)

On Thu, 13 Jun 1996, llucius wrote:
> m68k users. 

fine. can you send me the package names?
i will include them in the list, so that we can stop 
working on these packages (at least up until the uploading
is reliable working ;-)

i resend the current list in my next mail.

> 1)  Should I upload these to master?

please stay tuned a little bit longer. Michael is currently
processing our upload queue (more then 50 .deb files!)
and i don't want to give him more work as long as the old one
isn't done.

FYI: Guy has written an upload processing script which 
should process our as well as the intel uploads automatically.
i've uploaded dpkg-1.2.3elf.m68k.deb to the intel upload
area to test this. unfortunately this file was received
on master just in time _after_ dinstall ran last time.
now i'm waiting for the next run (this weekend?) to see
if this really works.

sorry for all the delays, the intel 1.1 release is to be
going out on monday so they have some other things to do. ;-))

> 2)  What guidelines should be followed when doing this?

- rename the .deb file with dpkg-name
- use "dchanges -p *.m68k.deb" to create a changes file (format 1.[456])
- put your name and adress in the maintainer field
  (it is _only_ used to send you an ack or an error report
  for your upload. the real maintainer wouldn't like to 
  receive this ;-))
- rename the *.changes file to *.m68k.changes (for uniqueness)
- upload the .m68k.deb files together with the .changes file
  to master.

> 3)  Is a "changes" file required for such an upload since nothing really

yes. the changes section is not so important, but the rest of 
the file (length, md5-sum, ...) is used by dinstall for 
consistency checks and therefore _is_ important.

> 4)  If so, what should the "changes" file contain?

read dchanges(5). the programm 'dchanges' is only an 
implementation of dchanges(5).

> (I will be redoing some to add architecture to control files and
> binary package names.)

please send the changes you did as bug report to
   [email-masked]
1st lines of the _body_: 
   Package: <name>
   Version: 1.2.3-4

thanks
jjm

-- 
Juergen Menden                   | Disclaimer: The opinions expressed by me, 
tel:    +49 (89) 289 - 22387     +-----------+ are (usually) not the opinions 
e-mail: [email-masked]     | of anyone else on this planet.

Hi! I'm a .signature virus!  Add me to your .signature and join in the fun!