Re: Uploaded glibc-pre2.1 2.0.106-0.2 (hurd-i386) to master
On Tue, Dec 22, 1998 at 12:09:29PM -0600, Gordon Matzigkeit wrote:
>
> JK> Normally it would be, I think Christian's objection is mainly
> JK> that the sources for the current sparc libc6 binary packages
> JK> (almost) got stepped on again.
>
> How can I upload things so that nothing ``gets stepped on''? Which
> parts do I need to upload again, or should I just do another dupload
> from scratch?
Yes, Porters should in general only upload binary packages for their
architecture. This requires invoking dpkg-buildpackage with the
-B option (or is it -b? Dunno the difference. Try -B).
Then all will be build but the sources and architecture all packages.
Certainly, this does only work good if you didn't need to do any
changes to the package. If you had to do so, you should forward them to
the package maintainer for incorporation.
>
> The entire process of how a file gets from
> /home/Debian/ftp/private/project/Incoming into the ftp archive is a
> mystery to me, and so I was unaware that there was potential for
> clobbering another person's work.
It is all done by a programm called "dinstall". There are several
things that help you in the process:
Install "lintian", a Debian package checker. It will check your
packages for policy compliance and consistency.
You can try to run "dinstall -n changes-file" on master (you need to
find a dinstall, try "locate dinstall"). This will try a dry run.
Note that there is only one source file for each package and all
architectures.
Marcus
Reply to: