Several of the utilities in devscripts recognise when they are being run from a package's source tree, and automatically find the built files based on that. It would be convenient for dput to be able to do the same, so if there's a debian/changelog use it to get the package name and version and look for ../package_version_*.changes
Hi Joey, thanks a lot for your suggestion. Joey Hess wrote: Well, basically I've refrained from similar efforts to make uploading easier with the rationale that uploading to Debian was grave enough to make sure that everything is correct. For example all my uploads to ftp-master sit in my private repo or the pbuilder result directory. With the rise of non-official repositories, that rationale might no longer apply, though. If implemented, do you think _source.changes should be excluded or included? (Debian doesn't allow them, AFAIU they're a must for Ubuntu?) Kind regards T.
Thomas Viehmann wrote: I don't know; I have used a dput wrapper for some time that does this guessing for most of my uploads for debian, and I've not had any problems. Well at the worst an incorrect _source.changes would be rejected by ftp-master, I think.
Thomas Viehmann wrote: I don't know; I have used a dput wrapper for some time that does this guessing for most of my uploads for debian, and I've not had any problems. Well at the worst an incorrect _source.changes would be rejected by ftp-master, I think.
package dput retitle 348908 dput: guess location of package ‘*.changes’ file thanks The file needs to be located, more generally, wherever the package build process puts it. It is common for VCS-helper build tools such as ‘bzr-buildpackage’ or ‘svn-buildpackage’ etc. to have a configured source package destination which is often not the parent directory. For example, ‘svn-buildpackage(1)’ specifies the “buildArea” property; the ‘bzr-buildpackage’ tool uses the “build-dir” option. Other VCS-helper build tools may have corresponding configuration settings to specify the package build destiantion, and hence the location of the ‘*.changes’ file.
Greetings. I'm writing to you because I have a humanitarian request that I believe could be incredibly impactful. I'm reaching out about the recent devastating storm that tragically claimed many lives and affected numerous individuals in Libya, including one of my clients. I would like to discuss a proposal with you that could enable us to extend a helping hand to these victims. Looking forward to discussing this further with you. Warm regards, Mrs. Nathalie Herolds
Greetings. I'm writing to you because I have a humanitarian request that I believe could be incredibly impactful. I'm reaching out about the recent devastating storm that tragically claimed many lives and affected numerous individuals in Libya, including one of my clients. I would like to discuss a proposal with you that could enable us to extend a helping hand to these victims. Looking forward to discussing this further with you. Warm regards, Mrs. Nathalie Herolds
Greetings. I'm writing to you because I have a humanitarian request that I believe could be incredibly impactful. I'm reaching out about the recent devastating storm that tragically claimed many lives and affected numerous individuals in Libya, including one of my clients. I would like to discuss a proposal with you that could enable us to extend a helping hand to these victims. Looking forward to discussing this further with you. Warm regards, Mrs. Nathalie Herolds