Hi Dmitrijs, > First of all thank you for picking up the maintenance of this package. > It is non-trivial.
:) > > I'd like to thank you for your care for the 'autofs' package > > but please excuse me for expressing my non-appreciation of your NMU. > > I have cancelled it due to bug that Jakub Wilk expressed. Thank you for this. You can read more about conflict with autotools-dev in CAVEATS section of dh-autoreconf(7). > > Although perhaps not fast enough we're working on 'autofs' - we have a > > team of three and a different fix to the problem is already committed > > to repository. > > The changelog entry says: > " * declare myself as Maintainer (adopting package)" > > And the control says, that there is one maintainer & one uploader. > > Please, either change the maintainer to a team, or list all people on > the team. > > Please, set Vcs-* fields as per: > http://www.debian.org/doc/manuals/developers-reference/best-pkging-practic > es.html#bpp-vcs You're right. All the changes you're mentioned are pending. The team has formed after the package was sponsored so I was just trying to explain the current situation. Nevertheless for one or three maintainers NMU approach would still be invasive without first contacting the person(s) responsible. > If the fix has been committed to Vcs-*, you should set the 'pending' tag > on the bug. Normally I would agree but usually I'm trying to consider the fact that looking for sponsor may take weeks or even months in which case 'pending' may not be very useful. Sometimes I set 'pending' when package is ready and waiting for upload. Also one would expect that new 'serious' will hardly be unnoticed or ignored. If you have doubts, gentle reminder (accompanied with patch) will be always appreciated. :) > Correct Vcs-* headers, together with the pending tag would allowed me to > find the patches I was looking for. I'm with you, sorry for delay. Lesson learned. > > I do believe the pressure you impose with your NMU is unnecessary > > because simply asking or sharing your suggestions in email to any of > > us would be better. > > True. I'm sorry for putting you in the spotlight. We are days away from > the freeze, the package has RC bugs and did not transition to testing > yet. I do not want to release wheezy without autofs. There is pressure > from the release team. No worries, I understand this. I had very serious issue preventing me from working on package. :( > From the changelog, I understood that there was only one maintainer who > did ample of work to update the package. > > RC http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673796 has no > response from maintainer. Do you have a patch committed to some private > Vcs repository? Yes, we're using the following repository: http://anonscm.debian.org/gitweb/?p=collab-maint/autofs.git > > RC http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674391 has no > response from maintainer. And you say you do have a patch ready. Yes, see the above repository. > Who sponsored your upload? You can find out with 'who-uploads' from devscripts. ;) > Because bug #674391 is Fail To Build From > Source (in a sane manner) filed the day after the upload. Autoconf was > last updated on 2012-05-12. Did the package FTBFS (in a sane manner) on > the upload? Autoconf is unrelated to the issue. Yes package was building fine but I think the second build would be broken due to modification introduced by upstream patches to a generated file. I'm not sure what has changed (if any) to provoke FTBFS - perhaps something was built differently because problem was discovered during automatic rebuild. (Shortly after upload I noticed that it was impossible to un-apply patches after build.) But I knew how to avoid the issue. > > Also I'm sure you're aware that I'm not a DD, so to override your NMU > > I must complete changes for new release and find a sponsor within 5 > > days only. > > I am aware that you are not a DD. > To cancel an NMU you only need to get any DD to 'sponsor' this one line: > > "dcut ftp-eu cancel autofs_5.0.6-1.1_amd64.changes" Thank you. However when there is only little time left I need to ask more than one person in order to stop it for sure. > Nobody is forcing you to complete changes for a new release in an > unreasonable quick amount of time. > > I am sure anyone from #debian-mentors would have done it, if it was not > already done by me. True. > Do you have a DD in your team of three people to review and sponsor > packages? Fortunately. :) > > You're welcome to the team if you want to help but please consider > > first to communicate whatever improvements you might have and then > > perhaps sponsor the existing effort rather than override it with > > premature NMU. > > Yes, I do want to be part of the team. Thank you and welcome :) Feel free to add yourself to Uploaders. > Do you have a team setup on alioth with a Vcs repository and mailing > list? Or do you want help to set this up? Yes, see above. > Improvements I want to achieve: This package to migrate to testing. > This means: > * fix FTBFS in a sane way Done. > * fix FTBFS with gold / ld --as-needed Could you please provide more details on this? We'll do our best but I believe to Debian side this is not a priority, as we can always fix it after freeze. At the moment let's focus on coordinated upload. > * fix conf file upgrade handling Done as well. > > > Meanwhile I'll do my best to address the problem ASAP. > > Great. > * Please comment on the bugs that are being worked on. If appropriate. > * Please tag pending, if a solution for the bug is found and it will be > part of the next upload. OK. > Above action, would have prevented spending me time doing duplicate work > in a different time zone. Apologies for that, and please excuse me once again for stressing the importance of communication which could save you time as well. > Thank you for you contributions to debian. I hope you will keep up the > excellent work you are doing with this package. But please do fix the > issues with the package I have outlined above. Thank you too. I'm sure everything will be OK as we're learning to work better together. :) Cheers, Dmitry. http://anonscm.debian.org/gitweb/?p=collab-maint/autofs.git -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
