[Pkg-crosswire-devel] question about dput and distribution

Matthew Talbert ransom1982 at gmail.com
Mon Jul 20 23:42:21 BST 2009

Thanks for your reply.

> Generally you should change the last changelog entry with unique
> version number and correct target release.

So essentially I need to create separate source packages for each
release I want to build for?

> What tool did you use to set-up the repository? ftp-archive
> dinstall-mini reprepro?


> Generally All debs are stored in the same folder and then package.gz
> and source.gz files are generated to create something apt can read
> (and store in apt-cache) and optionally Release & Release.gpg files if
> you want an authenticated repository.
> Now guess what happens if you uploaded to repository
> xiphos_3.1-1_amd64.deb rebuild for another distribution with same
> version number and upload again? Well it fails cause
> xiphos_3.1-1_amd64.deb already exists but has a different checksum!
> Change last changelog entry to something like xiphos (3.1-1~jaunty1)
> jaunty and everything should be fly.

So essentially, I just need to add a new changelog entry. What about
doing something like xiphos (3.1-1~SVN_REV) ?

OK, I think I'm understanding this now. If I change the changelog
entry before making the source package, then everything will just

> And dput.cf does some sanity checks and doesn't usually allow
> uploading bogus distributions see man dput.cf :
>       distributions
>              This defines a comma-separated list of distributions  that  this
>              host  accepts,  used to guess the host to use when none is given
>              on the command line.
>       allowed_distributions
>              A regular expression (of Python re module syntax) that the  dis‐
>              tribution field must match or dput will refuse the upload.
> Hope this helps =)

Yes, it does. Thank you.


More information about the Pkg-crosswire-devel mailing list