Bug#979551: [Pkg-javascript-devel] Bug#979551: node-babel7: update-alternatives set up fails
Le 27/01/2021 à 22:20, Xavier a écrit : > Control: tags -1 + confirmed > > Hi, > > this can be fixed using `--slave` parameter of update-alternatives > instead of a main link for manpages However it seems not possible to decrease an alternative from "master" to "slave". For now I propose to remove alternatives for manpages, later I'll use "--slave" (with node-babel8 release)
Bug#979551: node-babel7: update-alternatives set up fails
Control: tags -1 + confirmed Hi, this can be fixed using `--slave` parameter of update-alternatives instead of a main link for manpages
Bug#979551: [Pkg-javascript-devel] Bug#979551: Bug#979551: node-babel7: update-alternatives set up fails
Quoting Pirate Praveen (2021-01-08 12:48:06) > > > On Fri, Jan 8, 2021 at 12:44 pm, Jonas Smedegaard > wrote: > > I don't understand - how is node-babel7 affected by how yarnpkg > > declares (build-)dependencies against it? > > > > node-babel7 will still be affected by the update-alternatives bug when > manpages missing. > > > What I suggest is to improve the package yarnpkg to replace any > > runtime and build-time package relations on node-babel7 to instead > > be on each actually needed node-$module package, virtual or not. > > > > (and yes, it should work fine for autopkgtest as well - a previous > > failure I caused was due to lack of appending (>= 7) for a virtual > > package also provided by older babel6 package). > > That is tangential to this particular bug. That is an improvement, > yes, but will not solve this bug without separate binary for > @babel/runtime module, as it will still pull in node-babel7 and > missing man pages will trigger this bug. Ahh. Yes, I agree that no changes to package yarnpkg can fix bugs in package node-babel7. And I agree that the issue on topic for this bugreport is a bug in node-babel7. That said, both you and I responsed to a _sidenote_ by Paolo: Quoting Jonas Smedegaard (2021-01-08 12:06:21) > Quoting Pirate Praveen (2021-01-08 11:55:14) > > On 2021, ജനുവരി 8 1:16:36 PM IST, Paolo Greppi > > wrote: > > >BTW, why is node-babel7 a run-time dependency of yarnpkg ? Should > > >it not just be a build-dep ? > > > > > > > It needs @babel/runtime which is currently part of node-babel7. I > > think yadd already uploaded a version of node-babel7 with separate > > node-babel7-runtime binary package. But it has not cleared NEW yet. > > You need not wait for NEW clearance to depend explicitly on required > packages - you need only have the required packages available as > virtual packages. My point above is that regardless of the topic of this bugreport, that other issue on topic for the sidenote need not wait for NEW processing, but can be addressed (or at least prepared) in parallel by changing to declare explicit package relations in package yarnpkg. - 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
Bug#979551: [Pkg-javascript-devel] Bug#979551: Bug#979551: node-babel7: update-alternatives set up fails
On Fri, Jan 8, 2021 at 12:44 pm, Jonas Smedegaard wrote: I don't understand - how is node-babel7 affected by how yarnpkg declares (build-)dependencies against it? node-babel7 will still be affected by the update-alternatives bug when manpages missing. What I suggest is to improve the package yarnpkg to replace any runtime and build-time package relations on node-babel7 to instead be on each actually needed node-$module package, virtual or not. (and yes, it should work fine for autopkgtest as well - a previous failure I caused was due to lack of appending (>= 7) for a virtual package also provided by older babel6 package). That is tangential to this particular bug. That is an improvement, yes, but will not solve this bug without separate binary for @babel/runtime module, as it will still pull in node-babel7 and missing man pages will trigger this bug.
Bug#979551: [Pkg-javascript-devel] Bug#979551: Bug#979551: node-babel7: update-alternatives set up fails
Quoting Pirate Praveen (2021-01-08 12:16:20) > > > On Fri, Jan 8, 2021 at 12:06 pm, Jonas Smedegaard > wrote: > > Quoting Pirate Praveen (2021-01-08 11:55:14) > >> > >> > >> On 2021, ജനുവരി 8 1:16:36 PM IST, Paolo Greppi > >> wrote: > >> >BTW, why is node-babel7 a run-time dependency of yarnpkg ? > >> >Should it not just be a build-dep ? > >> > > >> > >> It needs @babel/runtime which is currently part of node-babel7. I > >> think yadd already uploaded a version of node-babel7 with separate > >> node-babel7-runtime binary package. But it has not cleared NEW yet. > > > > You need not wait for NEW clearance to depend explicitly on required > > packages - you need only have the required packages available as > > virtual packages. > > > > Yes, but changing dependency alone will not solve this issue. When it > clears NEW and dependency is updated, this bug will be fixed for > yarnpkg, but node-babel7 will still be affected. I don't understand - how is node-babel7 affected by how yarnpkg declares (build-)dependencies against it? What I suggest is to improve the package yarnpkg to replace any runtime and build-time package relations on node-babel7 to instead be on each actually needed node-$module package, virtual or not. (and yes, it should work fine for autopkgtest as well - a previous failure I caused was due to lack of appending (>= 7) for a virtual package also provided by older babel6 package). - 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
Bug#979551: [Pkg-javascript-devel] Bug#979551: Bug#979551: node-babel7: update-alternatives set up fails
On Fri, Jan 8, 2021 at 12:06 pm, Jonas Smedegaard wrote: Quoting Pirate Praveen (2021-01-08 11:55:14) On 2021, ജനുവരി 8 1:16:36 PM IST, Paolo Greppi wrote: >BTW, why is node-babel7 a run-time dependency of yarnpkg ? >Should it not just be a build-dep ? > It needs @babel/runtime which is currently part of node-babel7. I think yadd already uploaded a version of node-babel7 with separate node-babel7-runtime binary package. But it has not cleared NEW yet. You need not wait for NEW clearance to depend explicitly on required packages - you need only have the required packages available as virtual packages. Yes, but changing dependency alone will not solve this issue. When it clears NEW and dependency is updated, this bug will be fixed for yarnpkg, but node-babel7 will still be affected.
Bug#979551: [Pkg-javascript-devel] Bug#979551: Bug#979551: node-babel7: update-alternatives set up fails
Quoting Pirate Praveen (2021-01-08 11:55:14) > > > On 2021, ജനുവരി 8 1:16:36 PM IST, Paolo Greppi wrote: > >BTW, why is node-babel7 a run-time dependency of yarnpkg ? > >Should it not just be a build-dep ? > > > > It needs @babel/runtime which is currently part of node-babel7. I think yadd > already uploaded a version of node-babel7 with separate node-babel7-runtime > binary package. But it has not cleared NEW yet. You need not wait for NEW clearance to depend explicitly on required packages - you need only have the required packages available as virtual packages. - 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
Bug#979551: [Pkg-javascript-devel] Bug#979551: node-babel7: update-alternatives set up fails
Quoting Paolo Greppi (2021-01-08 11:44:31) > Il 08/01/21 11:35, Jonas Smedegaard ha scritto: > > Quoting Paolo Greppi (2021-01-08 08:46:36) > >> I guess that's because the bullseye-slim image lacks the manpages. > > > > A Debian install with man pages excluded seems to be an unsupported > > system: Whatever hooks applied to do that trick should be extended to > > handle update-alternatives - not the packages providing alternatives nor > > the update-alternatives mechanism itself! > > > > If you disagree, then please try locate passages in Debian Policy to > > support your view. > > > > > > - Jonas > > > > Sorry I am not qualified to respond. Yes you are. My way of writing can be off-putting - it may sound like I know better than anyone, but I really don't know all - and even if my knowledge about Debian rules is "right", it is still relevant to get *opinions* to maybe *change* the rules. > Using Debian official images with docker/podman is a use case we > should support as it is one significant way for Debian to stay > relevant in this post-devops world. > > Also see: > - https://hub.docker.com/_/debian/#Image_Variants > - https://github.com/debuerreotype/debuerreotype/issues/10 I agree that Debian official material should work. Your 2 URLs point elsewhere than the official debian.org domain - could it be that the image you used is not "official Debian" mirrored at docker.com but maybe instead "official Docker" based on Debian? - 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
Bug#979551: [Pkg-javascript-devel] Bug#979551: node-babel7: update-alternatives set up fails
On 2021, ജനുവരി 8 1:16:36 PM IST, Paolo Greppi wrote: >BTW, why is node-babel7 a run-time dependency of yarnpkg ? >Should it not just be a build-dep ? > It needs @babel/runtime which is currently part of node-babel7. I think yadd already uploaded a version of node-babel7 with separate node-babel7-runtime binary package. But it has not cleared NEW yet. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#979551: [Pkg-javascript-devel] Bug#979551: node-babel7: update-alternatives set up fails
Il 08/01/21 11:35, Jonas Smedegaard ha scritto: Quoting Paolo Greppi (2021-01-08 08:46:36) I guess that's because the bullseye-slim image lacks the manpages. A Debian install with man pages excluded seems to be an unsupported system: Whatever hooks applied to do that trick should be extended to handle update-alternatives - not the packages providing alternatives nor the update-alternatives mechanism itself! If you disagree, then please try locate passages in Debian Policy to support your view. - Jonas Sorry I am not qualified to respond. Using Debian official images with docker/podman is a use case we should support as it is one significant way for Debian to stay relevant in this post-devops world. Also see: - https://hub.docker.com/_/debian/#Image_Variants - https://github.com/debuerreotype/debuerreotype/issues/10 Paolo
Bug#979551: [Pkg-javascript-devel] Bug#979551: node-babel7: update-alternatives set up fails
Quoting Paolo Greppi (2021-01-08 08:46:36) > I guess that's because the bullseye-slim image lacks the manpages. A Debian install with man pages excluded seems to be an unsupported system: Whatever hooks applied to do that trick should be extended to handle update-alternatives - not the packages providing alternatives nor the update-alternatives mechanism itself! If you disagree, then please try locate passages in Debian Policy to support your view. - 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
Bug#979551: node-babel7: update-alternatives set up fails
Package: node-babel7 Version: 7.12.11+~cs150.141.84-3 Severity: important Dear Maintainer, installing node-babel7 on official debian "bullseye-slim" docker image fails like this: docker pull debian:bullseye-slim docker run --rm -it debian:bullseye-slim apt update && apt install -y --no-install-recommends yarnpkg ... Setting up node-babel7 (7.12.11+~cs150.141.84-3) ... update-alternatives: using /usr/bin/babeljs-7 to provide /usr/bin/babeljs (babeljs) in auto mode update-alternatives: using /usr/bin/babeljs-7-external-helpers to provide /usr/bin/babeljs-external-helpers (babeljs-external-helpers) in auto mode update-alternatives: using /usr/bin/babeljs-7-node to provide /usr/bin/babeljs-node (babeljs-node) in auto mode update-alternatives: using /usr/bin/babeljs-7-parser to provide /usr/bin/babeljs-parser (babeljs-parser) in auto mode update-alternatives: error: alternative path /usr/share/man/man1/babeljs-7.1.gz doesn't exist dpkg: error processing package node-babel7 (--configure): installed node-babel7 package post-installation script subprocess returned error exit status 2 dpkg: dependency problems prevent configuration of yarnpkg: yarnpkg depends on node-babel7; however: Package node-babel7 is not configured yet. dpkg: error processing package yarnpkg (--configure): dependency problems - leaving unconfigured I guess that's because the bullseye-slim image lacks the manpages. BTW, why is node-babel7 a run-time dependency of yarnpkg ? Should it not just be a build-dep ? Paolo -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages node-babel7 depends on: ii node-browserslist 4.16.0+~cs5.4.69-1 ii node-chalk 4.1.0-1 ii node-commander 6.2.1-2 ii node-convert-source-map 1.7.0+~1.5.1-1 ii node-core-js3.8.1-1 ii node-debug 4.3.1+~cs4.1.5-1 ii node-esutils2.0.3-1 ii node-find-cache-dir 3.3.1-1 ii node-fs-readdir-recursive 1.1.0-1 ii node-glob 7.1.6+~7.1.3-1 ii node-globals13.5.0-1 ii node-js-tokens 6.0.0-1 ii node-jsesc 3.0.2-1 ii node-json5 2.1.3-2 ii node-lodash 4.17.20+dfsg+~cs8.31.170-1 ii node-make-dir 3.0.2-1 ii node-quick-lru 1.1.0-2 ii node-regenerator-runtime0.13.7-1 ii node-regenerator-transform 0.14.5-4 ii node-regexpu-core 4.7.1-1 ii node-resolve1.19.0+~cs5.20.8-2 ii node-semver 7.3.4-1 ii node-slash 3.0.0-1 ii node-source-map 0.7.0++dfsg2+really.0.6.1-4 ii node-source-map-support 0.5.19+ds+~0.5.3-1 ii node-to-fast-properties 3.0.1-1 ii node-v8flags3.2.0-1 ii nodejs 12.19.0~dfsg-1 node-babel7 recommends no packages. node-babel7 suggests no packages. -- no debconf information
