On Tue, May 29, 2012 at 10:48:43AM +0200, intrigeri wrote:
> Commit 85a9d87f makes debian/rules stop passing
> "DEB_BUILD_MAINT_OPTIONS = hardening=+all" to dpkg-buildflags.
I was doing testing with and without the revert, and the lintian
tests did not improve. I plan to do a few more tests though.
I'm curious why we would force all hardening options on when it is
not the default for Debian. I assume hardening defaults were chosen
for good reason. Doesn't this make it harder to adjust the whole
distro at once, if needed? This is not like -Wall where it only
affects compilation. It affects runtime as well, as I understand it.
> However, process-wise, it would make things much easier for me on the
> long run if you maintained this package using the "classic"
> git-buildpackage + pristine-tar workflow:
>
> - a branch dedicated to Debian packaging (usually called "master",
> but since your repo is the upstream one, I suggest calling it
> "debian-master" instead)
> - a branch dedicated at importing upstream tarballs using
> git-import-orig (called "upstream", by default)
> - git-import-orig takes care of maintaining the pristine-tar branch,
> merging the orig tarball into "upstream", merging "upstream" into
> "debian-master", and creating tags as needed, so this should not
> change your current workflow much: the main thing that changes is
> how you send me your work.
>
> This way, every time you ask me to upload a package, I can easily
> check the changes using Git, run git-buildpackage, inspect and push
> the result. Also, it will make maintaining official Debian backports
> much easier.
>
> What do you think?
Well, you asked. :-) I mean no offense by the following. It reflects my
perspective as an upstream focused programmer, at least so far.
First, some questions: are my source packages not the files that will be
uploaded? Do you need to recreate them for some reason? I had assumed
that uploading was easy if you had accurate, signed source packages
from me.
What changes do you check when you use git? Is it not suitable to do:
git log -p barry-0.18.2..barry-0.18.3 -- debian
to see what changed?
Also, the debian/ directory lives in master, and if I understand correctly,
you're asking for it to be moved. This makes no sense to me. I can see
creating new tags for Debian-only -1, -2, releases, but not splitting
debian/ into its own little world.
As for pristine-tar, my initial reaction is that I'm disappointed
that I can't get rid of it yet. I had hoped that by taking on the
role of maintainer, I could avoid that waste. I know downstream loves
pristine-tar, but upstream, it looks like a hack. :-) I admire Joey Hess,
but unfortunately pristine-tar rubs me the wrong way.
If I find a way to make git-buildpackage run for you as expected, without
pristine-tar, would that be satisfactory? Maybe that's impossible, but I'd
really like to get rid of that dependency.
If worse comes to worst, would it be possible to get a git repo somewhere
on debian.org that I could push pristine-tar stuff to? I'm sure I could
script something to do it automatically, but I don't want that waste in
upstream, and it seems rude to put it on repo.or.cz too.
Thanks,
- Chris
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
