Re: hmisc and r-cran-rms testing migration blocked
Hi, On Tue, Jan 24, 2017 at 10:53:43AM -0600, Dirk Eddelbuettel wrote: > > | > which should be writable to any DD and do a Team upload / NMU at your > | > preference or send me a patch you consider the best solution. > | > | > https://anonscm.debian.org/git/debian-science/packages/r-cran-knitr.git/commit/?id=5e342fd1f88595b3779ef1fe6dbce768508b8e4b > | > | It seems wrong that these JS packages are *build* dependencies, > | there are not used during the build. > | > | They should instead be Suggests or Recommends, and that would also make > | r-cran-knitr available on armel again. > > Seconded. But it's not my package so ... Well, we have seen in the past that we have diverging opinions about "ownership" of packages. I can't repeat less that if you do a dch --team it is perfectly fine. Its actually the point of team maintenance that more than one person can (and should) fix issues. Back to the topic: I uploaded after moving the Build-Depends to Depends - I admit that Build-Depends was by accident and should have been Depends. However, this will not solve the original problem on armel. The JS package dependencies are required to enable the privacy means[1] and are not optional but required since it is not only documentation but also in parts of the code (for instance R/utils-rd2html.R). So this will shift the armel problem from not buildable to not installable. Its a usual trick to add those packages that are in the list of Depends to the Build-Depends to make sure that a package is only available on a certain architecture if it will be installable. This is more flexible than excluding specific architectures inside the Architecture field since once the dependency will be available again there is no need to change the package. Considering this I'm tempted to add the dependency which does not exist on armel back to the Build-Depends and ask ftpmaster for removal of r-cran-knitr for this architecture. What do you think about this approach? Kind regards Andreas. [1] https://anonscm.debian.org/cgit/debian-science/packages/r-cran-knitr.git/tree/debian/patches/privacy_breach_fix.patch -- http://fam-tille.de -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Re: hmisc and r-cran-rms testing migration blocked
On 24 January 2017 at 15:19, Adrian Bunk wrote: | On Mon, Jan 23, 2017 at 08:09:11PM +0100, Andreas Tille wrote: | > Hi, | > | > On Mon, Jan 23, 2017 at 11:37:00AM -0600, Dirk Eddelbuettel wrote: | > > | | > > | Therefore nodejs is no longer available on armel. | > > | | > > | And therefore the node-highlight.js package that does depend on nodejs | > > | is no longer installable on armel. | > > | | > > | If you need/want r-cran-knitr on armel, you should discuss with | > > | Andreas Tille whether there are possibilities remove or !armel | > > | the build dependency of r-cran-knitr on node-highlight.js | > > | > > Right. CCing Andreas -- knitr is by now real R infrastructure as the caller | > > of pandoc. It could quite possibly work meaningfully even without the | > > highlight.js. I am generally against "forking friom upstream", but this may | > > be worthy a making a different choice. But I leave the decision to the | > > maintainer. | > | > ... so you should have CCed the maintainer and not a "random" uploader. :-) | > As you might know I'm not in favour of private discussion. | > | > I admit that I'm quite uneducated about r-cran-knitr and worked on the | > package only as part of a chain of dependencies for my final target | > (r-cran-treescape). I'd follow any proposal of more educated people | > which will be considered more sensible than just excluding the package | > from armel (which is not relevant for the said package above. Feel | > free to commit to | > | >https://anonscm.debian.org/git/debian-science/packages/r-cran-knitr.git | > | > which should be writable to any DD and do a Team upload / NMU at your | > preference or send me a patch you consider the best solution. | | https://anonscm.debian.org/git/debian-science/packages/r-cran-knitr.git/commit/?id=5e342fd1f88595b3779ef1fe6dbce768508b8e4b | | It seems wrong that these JS packages are *build* dependencies, | there are not used during the build. | | They should instead be Suggests or Recommends, and that would also make | r-cran-knitr available on armel again. Seconded. But it's not my package so ... Dirk | > Kind regards | > | >Andreas. | | cu | Adrian | | -- | |"Is there not promise of rain?" Ling Tan asked suddenly out | of the darkness. There had been need of rain for many days. |"Only a promise," Lao Er said. |Pearl S. Buck - Dragon Seed | -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Re: hmisc and r-cran-rms testing migration blocked
On Mon, Jan 23, 2017 at 08:09:11PM +0100, Andreas Tille wrote: > Hi, > > On Mon, Jan 23, 2017 at 11:37:00AM -0600, Dirk Eddelbuettel wrote: > > | > > | Therefore nodejs is no longer available on armel. > > | > > | And therefore the node-highlight.js package that does depend on nodejs > > | is no longer installable on armel. > > | > > | If you need/want r-cran-knitr on armel, you should discuss with > > | Andreas Tille whether there are possibilities remove or !armel > > | the build dependency of r-cran-knitr on node-highlight.js > > > > Right. CCing Andreas -- knitr is by now real R infrastructure as the caller > > of pandoc. It could quite possibly work meaningfully even without the > > highlight.js. I am generally against "forking friom upstream", but this may > > be worthy a making a different choice. But I leave the decision to the > > maintainer. > > ... so you should have CCed the maintainer and not a "random" uploader. :-) > As you might know I'm not in favour of private discussion. > > I admit that I'm quite uneducated about r-cran-knitr and worked on the > package only as part of a chain of dependencies for my final target > (r-cran-treescape). I'd follow any proposal of more educated people > which will be considered more sensible than just excluding the package > from armel (which is not relevant for the said package above. Feel > free to commit to > >https://anonscm.debian.org/git/debian-science/packages/r-cran-knitr.git > > which should be writable to any DD and do a Team upload / NMU at your > preference or send me a patch you consider the best solution. https://anonscm.debian.org/git/debian-science/packages/r-cran-knitr.git/commit/?id=5e342fd1f88595b3779ef1fe6dbce768508b8e4b It seems wrong that these JS packages are *build* dependencies, there are not used during the build. They should instead be Suggests or Recommends, and that would also make r-cran-knitr available on armel again. > Kind regards > >Andreas. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Re: hmisc and r-cran-rms testing migration blocked
Hi, On Mon, Jan 23, 2017 at 11:37:00AM -0600, Dirk Eddelbuettel wrote: > | > | Therefore nodejs is no longer available on armel. > | > | And therefore the node-highlight.js package that does depend on nodejs > | is no longer installable on armel. > | > | If you need/want r-cran-knitr on armel, you should discuss with > | Andreas Tille whether there are possibilities remove or !armel > | the build dependency of r-cran-knitr on node-highlight.js > > Right. CCing Andreas -- knitr is by now real R infrastructure as the caller > of pandoc. It could quite possibly work meaningfully even without the > highlight.js. I am generally against "forking friom upstream", but this may > be worthy a making a different choice. But I leave the decision to the > maintainer. ... so you should have CCed the maintainer and not a "random" uploader. :-) As you might know I'm not in favour of private discussion. I admit that I'm quite uneducated about r-cran-knitr and worked on the package only as part of a chain of dependencies for my final target (r-cran-treescape). I'd follow any proposal of more educated people which will be considered more sensible than just excluding the package from armel (which is not relevant for the said package above. Feel free to commit to https://anonscm.debian.org/git/debian-science/packages/r-cran-knitr.git which should be writable to any DD and do a Team upload / NMU at your preference or send me a patch you consider the best solution. Kind regards Andreas. -- http://fam-tille.de -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
