[Pkg-javascript-devel] Bug#867298: Bug#867298: npm2deb: please bump debhelper and Standards-Version
Quoting Johannes Schauer (2017-07-05 21:16:38) > Quoting Jonas Smedegaard (2017-07-05 21:04:44) > > Quoting Johannes Schauer (2017-07-05 18:26:40) > > > Maybe I misunderstand but this bug report is not about "changing" > > > or "bumping" anything. > > > > > > Since npm2deb creates the *initial* Debian packaging, the > > > situation where we start with a lower Standards-Version and then > > > have to verify changes before we can "bump" the Standards-Version > > > doesn't arise. > > > > Right, this is not about single package bumping as I confusingly > > wrote, but instead about automated processing where it is even > > _more_ important to verify that the claimed Standards-Version is > > accurately applied, and even _more_ important to consider if newest > > shiny denhelper really is needed! > > Lets not conflate the two issues. I assume that it's uncontroversial > that the newest Standards-Version should be emitted because it doesn't > make sense to pick any old policy version and then require the > maintainer to bump the version bit by bit, right? If npm2deb maintainers has only verified that the tool comply with some older version of Debian Policy, then indeed the burden is on each maintainer using the tool to verify that the generated package comply with a different (newer) release of Debian Policy. I am not against this being addressed. My point is just that addressing it involves actually checking that newer release of Debian Policy and ensuring that the tool complies with it. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#867298: Bug#867298: npm2deb: please bump debhelper and Standards-Version
Quoting Jonas Smedegaard (2017-07-05 21:04:44) > Quoting Johannes Schauer (2017-07-05 18:26:40) > > Maybe I misunderstand but this bug report is not about "changing" or > > "bumping" anything. > > > > Since npm2deb creates the *initial* Debian packaging, the situation > > where we start with a lower Standards-Version and then have to verify > > changes before we can "bump" the Standards-Version doesn't arise. > > Right, this is not about single package bumping as I confusingly wrote, > but instead about automated processing where it is even _more_ important > to verify that the claimed Standards-Version is accurately applied, and > even _more_ important to consider if newest shiny denhelper really is > needed! Lets not conflate the two issues. I assume that it's uncontroversial that the newest Standards-Version should be emitted because it doesn't make sense to pick any old policy version and then require the maintainer to bump the version bit by bit, right? > > Furthermore, I'd argue that any tool which auto-generates Debian packaging > > data should use the current and/or recommended packaging practices. > > According to the debhelper man page, compatibility level 10 is the > > "recommended mode of operation". > I am aware that the developers of debhelper promote newest major version - > that does not change my plea about being more conservative: Use the debhelper > compatibility level supported in oldstable (currently 9), unless some feature > requiring a newer compatibility level is needed. I will leave the choice about the right debhelper version to the npm2deb maintainers. Thanks! cheers, josch signature.asc Description: signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#867298: Bug#867298: npm2deb: please bump debhelper and Standards-Version
Quoting Johannes Schauer (2017-07-05 18:26:40) > Quoting Jonas Smedegaard (2017-07-05 17:46:19) > > Quoting Johannes Schauer (2017-07-05 17:15:46) > > > Standards-Version 3.9.8 is outdated. npm2deb should generate version > > > 4.0.0 instead. > > Just to avoid misunderstanding: Standards-Version should *only* be > > changed as a *result* of verifying that said the package comply with > > said version of Debian Policy. > > > > > > > The current recommended compat level for debhelper is 10. npm2deb > > > should use that one instead of compat level 9. > > Please bump debhelper compatibility level only when really needed, > > to help ease backportability (to _any_ environment, not only > > backport.debian.org). > > Maybe I misunderstand but this bug report is not about "changing" or > "bumping" anything. > > Since npm2deb creates the *initial* Debian packaging, the situation > where we start with a lower Standards-Version and then have to verify > changes before we can "bump" the Standards-Version doesn't arise. Right, this is not about single package bumping as I confusingly wrote, but instead about automated processing where it is even _more_ important to verify that the claimed Standards-Version is accurately applied, and even _more_ important to consider if newest shiny denhelper really is needed! > Furthermore, I'd argue that any tool which auto-generates Debian > packaging data should use the current and/or recommended packaging > practices. According to the debhelper man page, compatibility level 10 > is the "recommended mode of operation". I am aware that the developers of debhelper promote newest major version - that does not change my plea about being more conservative: Use the debhelper compatibility level supported in oldstable (currently 9), unless some feature requiring a newer compatibility level is needed. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#867298: Bug#867298: npm2deb: please bump debhelper and Standards-Version
Quoting Jonas Smedegaard (2017-07-05 17:46:19) > Quoting Johannes Schauer (2017-07-05 17:15:46) > > Standards-Version 3.9.8 is outdated. npm2deb should generate version > > 4.0.0 instead. > Just to avoid misunderstanding: Standards-Version should *only* be changed as > a *result* of verifying that said the package comply with said version of > Debian Policy. > > > > The current recommended compat level for debhelper is 10. npm2deb > > should use that one instead of compat level 9. > Please bump debhelper compatibility level only when really needed, to help > ease backportability (to _any_ environment, not only backport.debian.org). Maybe I misunderstand but this bug report is not about "changing" or "bumping" anything. Since npm2deb creates the *initial* Debian packaging, the situation where we start with a lower Standards-Version and then have to verify changes before we can "bump" the Standards-Version doesn't arise. Furthermore, I'd argue that any tool which auto-generates Debian packaging data should use the current and/or recommended packaging practices. According to the debhelper man page, compatibility level 10 is the "recommended mode of operation". Thanks! cheers, josch signature.asc Description: signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#867298: Bug#867298: npm2deb: please bump debhelper and Standards-Version
Quoting Johannes Schauer (2017-07-05 17:15:46) > Standards-Version 3.9.8 is outdated. npm2deb should generate version > 4.0.0 instead. Just to avoid misunderstanding: Standards-Version should *only* be changed as a *result* of verifying that said the package comply with said version of Debian Policy. > The current recommended compat level for debhelper is 10. npm2deb > should use that one instead of compat level 9. Please bump debhelper compatibility level only when really needed, to help ease backportability (to _any_ environment, not only backport.debian.org). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
