Re: uploading to m68k
Sorry for taking a while to get back to you.
Anyway the script works fine on multiarchitecture uploads already. I'm
lazy though so haven't written the documentation YET!. It's extremely
easy though:
1. Rename your packages with dpkg-name.
2. Run dchanges to produce a changes file. You have to conform to
dchanges(5). A bit more info on this at the end of this email.
3. Upload the whole mess to Incoming.
4. Wait for email saying it's been rejected and installed.
5. If it's been rejected, you'll find what you've uploaded in
Incoming/REJECT. You won't have to upload it again if the reason was a
bad .changes file or only part of the upload was corrupted.
6. If it's been installed, go have a beer. :)
> - Michael Schmitz has a fairly good connection to master and has
> volunteered to clear our incomming. unfortunately he can do
> this job only until the end of the month.
I'll help Michael with this.
> - Frank Neumann and Sven Rudolph are moving the m68k area back to
> europe, so that the incoming processing is easier to maintain
> for us.
Don't do this yet. If Incoming gets processed every day or two, I
don't think this will be necessary.
> it seems that the script
> did already run on our incoming once?
Yeah, I tried to run the script, but your changes files were all very
old so didn't work. dinstall understands formats 1.4 and higher.
Be sure and read dchanges(5) as it documents the format. That's what I
went by when I wrote dinstall. dchanges itself is just an
implementation of dchanges(5). For example, I think it has a bug
producing binary only changes files, which is what you guys will
produce, but there's a patch in bug report 3104.
master is down right now (Argh! Why is it so flaky?) so I can't check
the exact reasons that your changes files were rejected. Here are some
I remember:
In the Architecture field, put m68k. Don't put source unless you're
uploading source. You shouldn't be.
In the Distribution field, put one of unstable, non-free, contib, or
experimental.
In the Binary field put the name of the package(s) you're uploading.
The Files section is most important.
For format 1.4 it's
<md5sum> <size> <section> <name>
For format 1.5 it's
<md5sum> <size> <section> <priority> <name>
It doesn't matter what you put in the section and priority fields as
I'll override them anyway. It's ok to just put `-' in both, and that's
what I suggest. One mistake I remember - only list the files you want
installed here. Some of you were listing source files here which of
course you weren't uploading.
For the Maintainer field, don't put the original maintainer; put
yourself. This field is used to figure out who get's the email.
Also, forget about the seperate m68k/Incoming. Put your uploads in the
main Incoming directory. But be extra careful to not overwrite
somebody else's files. So do 2 things:
1. Use dpkg-name to rename your deb files before uploading them.
2. Make sure your changes file has a unique name. Start it with m68k or
something else.
That's about it. I'll finish the documentation today and put it in
doc/package-developer today (I promise!).
Guy
Reply to: