Bug#686070: libpam-ssh/1.92-15
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Jerome,
- I would be much more comfortable if you asked the previous
maintainer for comments on the ITP (even if he never answers!)
- You could comment on #691988 explaining why you think the package
should be accepted for Wheezy:
+ insist that two users already requested reintroduction;
+ explain why you only took action after the freeze (perhaps you
used the squeeze version happily before that?);
+ explain that your RFS was filled in August and that you are not
responsible for the 2 month delay since then.
- That said, the package still contains non-minimalistic changes. You
need to produce a debdiff on the source package in squeeze and your
source package and comment on this debdiff. Every single change must
relate to fixing a RC bug or a release goal. For instance, I don't get
why you made those changes:
+ why introduce fix-debian-adhoc.patch, build-depend on
du-autoreconf etc? This seems to be replacing this:
$(MAKE) CFLAGS="$(cflags) -Wl,--version-script,debian/pam_ssh.version"
which I find simpler and more elegant.
Perhaps some of these changes are to fix a bug, please undo
whatever is unnecessary and explain (in this bug thread) what is
necessary.
+ Why remove the VCS control field? You should use the repository
instead.
+ the clean rule changes also seem unnecessary.
- Perhaps your package will not be unblocked for wheezy. In any case
you probably want to upload a new upstream soon enough. I would not
upload a new upstream to unstable at this point because it would
lower still the chances that the packages makes it into wheezy.
However, you can prepare the best possible package with new upstream
for experimental. In this package, you can do all the changes you
want.
I'm willing to sponsor your package (either 1.92 to unstable or 1.97 to
experimental, or both) but please try contacting the previous maintainer
for comments.
Note: I'm subscribed to the RFS, the ITP, and the release.d.o bugs. no
need to CC me.
Regards, Thibaut.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCAAGBQJQl4MmAAoJEJOUU0jg3ChAEaUP/iZhBeULC/yy5wGvyhTqZXn4
/YIhtTqTxOQA2rNwUMc2jyDYnAu6GpCrYjOz9wmWk2C356SehDkAAD/5rLoAbDKH
/DG/ZEUjgjfTcQA2IIu01jnGdSIM3p/D3laq6xaeFXBOYeTQ1DMlmhFVAm8mc74u
db+LE/teDlBJF8EQ1IBcOmOHq8xXQacLWngk08NhHwWdAPtMpoLhnuplDGEH3XFM
uLH4gJSpPNhk6Py7FOKT7v5VTg90QwNgilPnoBXdOWsQUZLAxWLLnLjNHDB2m6Ed
Y7CZfuL/TH3uqtWUR4jmECYbuiiNwtVoFgT537V/6fJD6DDj9K5pWxE3226vCjUL
N6Ye3U50lLIdtd8c9D/0SHbPDMR2sMpOsm4Gb/Ko49rqzU9wZHbkbgGtdjXLNg3D
A/f+j0cs2+Dj7uPXUXALhvhM92119ePTPPLDZ/Vnk5s3mva+pYEjgr6XT8TzLMUA
XQq8/WTqwgrpFQjqcoRFSo7MHtm3eD+ZWeK3GzkDanVoxafmMN5z0GMLtSjSiE8e
kjmdZkuqAf6p1Yp6gevtMx8MRUf2/IR/B1eyFdZI927O13MfdVbvZKotriy1KgR/
thVfNIlGMfw+6+tRRs5JyrGMK0grYVOPtW0++ZDiRid9mO0XreB78VU3DQVThOZh
uyfjVwH1lhkNiVy8IOle
=/ZWo
-----END PGP SIGNATURE-----
Reply to: