Bug#1028420: /usr/bin/dpkg-buildpackage: Feature Request: custom version flag support.

2023-01-10 Thread Garrett Kajmowicz
Package: dpkg-dev Version: 1.21.1 Severity: wishlist File: /usr/bin/dpkg-buildpackage Dear Maintainer, I'm requesting a flag or environment variable for dpkg-buildpackage and related tools which will allow overriding the version value of the package being produced. Supporting either a build

Bug#1026230: debhelper: Unable to successfully build in read-only source directory.

2022-12-23 Thread Garrett Kajmowicz
> Right, and while I'm happy to entertain the possibility to support something > like this, it seems a bit like one of those gargantuan projects we might end > up > with. So, I guess I'd also like to understand the motivations, and perhaps > whether other alternatives are not fulfilling? :)

Bug#1026230: debhelper: Unable to successfully build in read-only source directory.

2022-12-20 Thread Garrett Kajmowicz
> I have CC'ed Guillem Jover because *if* this is a change to be supported, > then it would need dpkg and debhelper to support it. Great! I look forward to hearing his response as well. > For this to be possible, it would require two "independent" features in the > Debian build stack: > > C1)

Bug#1026230: debhelper: Unable to successfully build in read-only source directory.

2022-12-16 Thread Garrett Kajmowicz
Package: debhelper Version: 13.6ubuntu1 Severity: wishlist Dear Maintainer, I'm working on a use-case which can be generalized as wanting to be able to perform a build with debhelper in a read-only source directory. Not simply that the files themselves are read-only, but that the full

Bug#833625: Request for fixing

2016-09-03 Thread Garrett Kajmowicz
Can we get some traction on this issue. I'm having the exact same problem. However, I don't want to delete my SQLITE databases because they contain any additional annotations and tags that I've added. I would expect a software version upgrade to handle this transparently. - Garrett