Dear Dmitry, On Wed, Mar 08, 2017 at 08:46:37AM +0300, Dmitry Bogatov wrote: > > control: tag -1 -moreinfo > > [2017-03-06 20:54] Sean Whitton <spwhitton@spwhitton.name> > > Dear Dmitry, > > > > On Sat, Feb 18, 2017 at 10:23:46AM +0300, Dmitry Bogatov wrote: > > > Note, that this is not full-scale modernization of package. It is just > > > a NMU, required for libbg1 -> libbg2 transition. > > > > Could you explain the background, please? Stretch is frozen. Have the > > release team authorized this transition? > > No. It is upload into experimental > > > It's rarely appropriate for an NMU to update to a new upstream version. > > If you are just performing the transition in experimental, there is no > > justification for it. > > I believe I have justification for this. Previous version (cvm-0.96) is > source-incompatible with (bglibs >= 2.03). There *might* be NMU justification if you were uploading to unstable. There definitely isn't for uploading to experimental. It would need to be a QA upload. > > > Please note, that package is maintained with dgit(1) tool using > > > dgit-maint-merge(7) workflow. In particular, it means that quilt > > > patches are squashed in source package and are not intended for > > > review. For more information about how to sponsor this package, > > > see dgit-sponsorship(7). > > > > This is not appropriate for an NMU. Indeed, I see that you've changed > > the source format to 3.0 (quilt) -- also not appropriate for an NMU. > > Well, I can revert it, but truth is that this package is maintained by > Gerrit Pape, who is not active for some years. I took over some of his > packages, but I am not interested in `cvm'. I just need to transit > bglibs, since latest version of `bcron', in which I am interested, > requires latest bglibs. > > Probably this upload should be QA upload, not NMU for lack of actual > maintainer. It is any way to ask QA team to make this upload on their > behalf? Sure, I can adopt, upload and fill RFA at same time, but it > feels wrong. I am talking to the MIA team. You could e-mail them yourself, too. Please be patient! Since Debian's current focus is releasing stretch, there is no reason to bypass our usual conventions for work that cannot end up in stretch. Thanks again. -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature