Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #950430 > unrolled thread
| Started by | Lucas Nussbaum <lucas@debian.org> |
|---|---|
| First post | 2019-03-17 19:40 +0100 |
| Last post | 2019-03-22 16:30 +0100 |
| Articles | 8 — 4 participants |
Back to article view | Back to linux.debian.bugs.dist
Bug#924807: node-jschardet: FTBFS: build-dependency not installable: webpack Lucas Nussbaum <lucas@debian.org> - 2019-03-17 19:40 +0100
Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js Xavier <x.guimard@free.fr> - 2019-03-17 23:20 +0100
Bug#924807: [Pkg-javascript-devel] Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js Jonas Smedegaard <jonas@jones.dk> - 2019-03-18 00:00 +0100
Bug#924809: [Pkg-javascript-devel] Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js Jonas Smedegaard <jonas@jones.dk> - 2019-03-18 00:10 +0100
Bug#924807: [Pkg-javascript-devel] Bug#924807: Bug#924807: Bug#924807: Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js Jonas Smedegaard <jonas@jones.dk> - 2019-03-18 12:00 +0100
Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js Jonas Smedegaard <jonas@jones.dk> - 2019-03-18 12:30 +0100
Bug#925211: uglifyjs conflicts with webpack which can hinder JS maintainers work Jérémy Lal <kapouer@melix.org> - 2019-03-22 15:00 +0100
Bug#925211: [Pkg-javascript-devel] Bug#925211: uglifyjs conflicts with webpack which can hinder JS maintainers work Jérémy Lal <kapouer@melix.org> - 2019-03-22 16:30 +0100
| From | Lucas Nussbaum <lucas@debian.org> |
|---|---|
| Date | 2019-03-17 19:40 +0100 |
| Subject | Bug#924807: node-jschardet: FTBFS: build-dependency not installable: webpack |
| Message-ID | <xCIRw-7vR-65@gated-at.bofh.it> |
Source: node-jschardet Version: 1.6.0+dfsg-1 Severity: serious Tags: buster sid User: debian-qa@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > +------------------------------------------------------------------------------+ > | Install package build dependencies | > +------------------------------------------------------------------------------+ > > > Setup apt archive > ----------------- > > Merged Build-Depends: debhelper (>= 9), dh-buildinfo, nodejs, uglifyjs, webpack > Filtered Build-Depends: debhelper (>= 9), dh-buildinfo, nodejs, uglifyjs, webpack > dpkg-deb: building package 'sbuild-build-depends-node-jschardet-dummy' in '/<<BUILDDIR>>/resolver-wJ4w5E/apt_archive/sbuild-build-depends-node-jschardet-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy sbuild-build-depends-node-jschardet-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<<BUILDDIR>>/resolver-wJ4w5E/apt_archive ./ InRelease > Get:2 copy:/<<BUILDDIR>>/resolver-wJ4w5E/apt_archive ./ Release [963 B] > Ign:3 copy:/<<BUILDDIR>>/resolver-wJ4w5E/apt_archive ./ Release.gpg > Get:4 copy:/<<BUILDDIR>>/resolver-wJ4w5E/apt_archive ./ Sources [518 B] > Get:5 copy:/<<BUILDDIR>>/resolver-wJ4w5E/apt_archive ./ Packages [600 B] > Fetched 2081 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install node-jschardet build dependencies (apt-based resolver) > -------------------------------------------------------------- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-node-jschardet-dummy : Depends: webpack but it is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2019/03/15/node-jschardet_1.6.0+dfsg-1_testing.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
[toc] | [next] | [standalone]
| From | Xavier <x.guimard@free.fr> |
|---|---|
| Date | 2019-03-17 23:20 +0100 |
| Subject | Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js |
| Message-ID | <xCMil-1ys-5@gated-at.bofh.it> |
| In reply to | #950430 |
Control: reassign 924807 uglify-js Control: reassign 924809 uglify-js Control: merge 924807 924809 Bug seems to come from conflict between https://tracker.debian.org/pkg/uglify-js and https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed with uglifyjs Le 17/03/2019 à 19:05, Lucas Nussbaum a écrit : > Source: node-jschardet > Version: 1.6.0+dfsg-1 > Severity: serious > Tags: buster sid > User: debian-qa@lists.debian.org > Usertags: qa-ftbfs-20190315 qa-ftbfs > Justification: FTBFS in buster on amd64 > > Hi, > > During a rebuild of all packages in buster (in a buster chroot, not a > sid chroot), your package failed to build on amd64. > > Relevant part (hopefully): >> +------------------------------------------------------------------------------+ >> | Install package build dependencies | >> +------------------------------------------------------------------------------+ >> >> >> Setup apt archive >> ----------------- >> >> Merged Build-Depends: debhelper (>= 9), dh-buildinfo, nodejs, uglifyjs, webpack >> Filtered Build-Depends: debhelper (>= 9), dh-buildinfo, nodejs, uglifyjs, webpack >> dpkg-deb: building package 'sbuild-build-depends-node-jschardet-dummy' in '/<<BUILDDIR>>/resolver-wJ4w5E/apt_archive/sbuild-build-depends-node-jschardet-dummy.deb'. >> dpkg-scanpackages: warning: Packages in archive but missing from override file: >> dpkg-scanpackages: warning: sbuild-build-depends-core-dummy sbuild-build-depends-node-jschardet-dummy >> dpkg-scanpackages: info: Wrote 2 entries to output Packages file. >> Ign:1 copy:/<<BUILDDIR>>/resolver-wJ4w5E/apt_archive ./ InRelease >> Get:2 copy:/<<BUILDDIR>>/resolver-wJ4w5E/apt_archive ./ Release [963 B] >> Ign:3 copy:/<<BUILDDIR>>/resolver-wJ4w5E/apt_archive ./ Release.gpg >> Get:4 copy:/<<BUILDDIR>>/resolver-wJ4w5E/apt_archive ./ Sources [518 B] >> Get:5 copy:/<<BUILDDIR>>/resolver-wJ4w5E/apt_archive ./ Packages [600 B] >> Fetched 2081 B in 0s (0 B/s) >> Reading package lists... >> Reading package lists... >> >> Install node-jschardet build dependencies (apt-based resolver) >> -------------------------------------------------------------- >> >> Installing build dependencies >> Reading package lists... >> Building dependency tree... >> Reading state information... >> Some packages could not be installed. This may mean that you have >> requested an impossible situation or if you are using the unstable >> distribution that some required packages have not yet been created >> or been moved out of Incoming. >> The following information may help to resolve the situation: >> >> The following packages have unmet dependencies: >> sbuild-build-depends-node-jschardet-dummy : Depends: webpack but it is not going to be installed >> E: Unable to correct problems, you have held broken packages. >> apt-get failed. > > The full build log is available from: > http://aws-logs.debian.net/2019/03/15/node-jschardet_1.6.0+dfsg-1_testing.log > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > About the archive rebuild: The rebuild was done on EC2 VM instances from > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every > failed build was retried once to eliminate random failures. >
[toc] | [prev] | [next] | [standalone]
| From | Jonas Smedegaard <jonas@jones.dk> |
|---|---|
| Date | 2019-03-18 00:00 +0100 |
| Subject | Bug#924807: [Pkg-javascript-devel] Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js |
| Message-ID | <xCMV4-1Me-7@gated-at.bofh.it> |
| In reply to | #950491 |
[Multipart message — attachments visible in raw view] — view raw
Quoting Xavier (2019-03-17 23:12:51) > Control: reassign 924807 uglify-js > Control: reassign 924809 uglify-js > Control: merge 924807 924809 > > Bug seems to come from conflict between > https://tracker.debian.org/pkg/uglify-js and > https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed > with uglifyjs Problem is packages depending on uglifyjs and webpack together: webpack depends indirectly on node-uglify 2.x, whereas uglifyjs is either a virtual package provided by node-uglify 2.x or (since recently) a real package depending on node-uglyfy-js 3.x. Yes, the problem emerged when node-uglify was introduced as a real package, but the fix is for those packages depending on uglifyjs and webpack together to depend on node-uglify 2.x instead of the virtual package. Please revert these reassignments: This cannot be fixed in uglifyjs 3.x. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
[toc] | [prev] | [next] | [standalone]
| From | Jonas Smedegaard <jonas@jones.dk> |
|---|---|
| Date | 2019-03-18 00:10 +0100 |
| Subject | Bug#924809: [Pkg-javascript-devel] Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js |
| Message-ID | <xCN4J-25l-11@gated-at.bofh.it> |
| In reply to | #950502 |
[Multipart message — attachments visible in raw view] — view raw
Quoting Jonas Smedegaard (2019-03-17 23:48:57) > Quoting Xavier (2019-03-17 23:12:51) > > Control: reassign 924807 uglify-js > > Control: reassign 924809 uglify-js > > Control: merge 924807 924809 > > > > Bug seems to come from conflict between > > https://tracker.debian.org/pkg/uglify-js and > > https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed > > with uglifyjs > > Problem is packages depending on uglifyjs and webpack together: webpack > depends indirectly on node-uglify 2.x, whereas uglifyjs is either a > virtual package provided by node-uglify 2.x or (since recently) a real > package depending on node-uglyfy-js 3.x. > > Yes, the problem emerged when node-uglify was introduced as a real > package, but the fix is for those packages depending on uglifyjs and > webpack together to depend on node-uglify 2.x instead of the virtual > package. > > Please revert these reassignments: This cannot be fixed in uglifyjs 3.x. Put differently, the problem is packages depending both unversioned and transitively versioned on uglifyjs - that works only as long as the transitive dependency happens to be newest major release of uglifyjs. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
[toc] | [prev] | [next] | [standalone]
| From | Jonas Smedegaard <jonas@jones.dk> |
|---|---|
| Date | 2019-03-18 12:00 +0100 |
| Subject | Bug#924807: [Pkg-javascript-devel] Bug#924807: Bug#924807: Bug#924807: Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js |
| Message-ID | <xCY9Q-ra-3@gated-at.bofh.it> |
| In reply to | #950430 |
[Multipart message — attachments visible in raw view] — view raw
Quoting Xavier (2019-03-18 06:56:42) > Le 18/03/2019 à 06:19, Xavier a écrit : > > Le 18/03/2019 à 00:02, Jonas Smedegaard a écrit : > >> Quoting Jonas Smedegaard (2019-03-17 23:48:57) > >>> Quoting Xavier (2019-03-17 23:12:51) > >>>> Control: reassign 924807 uglify-js > >>>> Control: reassign 924809 uglify-js > >>>> Control: merge 924807 924809 > >>>> > >>>> Bug seems to come from conflict between > >>>> https://tracker.debian.org/pkg/uglify-js and > >>>> https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed > >>>> with uglifyjs > >>> > >>> Problem is packages depending on uglifyjs and webpack together: webpack > >>> depends indirectly on node-uglify 2.x, whereas uglifyjs is either a > >>> virtual package provided by node-uglify 2.x or (since recently) a real > >>> package depending on node-uglyfy-js 3.x. > >>> > >>> Yes, the problem emerged when node-uglify was introduced as a real > >>> package, but the fix is for those packages depending on uglifyjs and > >>> webpack together to depend on node-uglify 2.x instead of the virtual > >>> package. > >>> > >>> Please revert these reassignments: This cannot be fixed in uglifyjs 3.x. > >> > >> Put differently, the problem is packages depending both unversioned and > >> transitively versioned on uglifyjs - that works only as long as the > >> transitive dependency happens to be newest major release of uglifyjs. > >> > >> - Jonas > > > > List of packages that are affected by this change: Please clarify how you produced a list of packages which depend *both* unversioned and *also* transitively versioned on uglifyjs. ...or clarify what other list you produced and why you find such other list relevant here. > If I understand (but maybe I'm wrong), this means that in buster it is > not possible to have uglifyjs installed with one of these 14 packages > or their dependencies (`apt-cache rdepends --recurse node-uglify` > returns several thousands package names). Please elaborate why - either based on my explanation of the problem quoted above, or elaborate on which _different_ theory you have of what is the underlying problem you try to solve. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
[toc] | [prev] | [next] | [standalone]
| From | Jonas Smedegaard <jonas@jones.dk> |
|---|---|
| Date | 2019-03-18 12:30 +0100 |
| Subject | Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js |
| Message-ID | <xCYCS-R3-9@gated-at.bofh.it> |
| In reply to | #950430 |
[Multipart message — attachments visible in raw view] — view raw
Quoting Xavier (2019-03-18 12:01:52) > Le 18/03/2019 à 11:46, Jonas Smedegaard a écrit : > > Quoting Xavier (2019-03-18 06:56:42) > >> Le 18/03/2019 à 06:19, Xavier a écrit : > >>> Le 18/03/2019 à 00:02, Jonas Smedegaard a écrit : > >>>> Quoting Jonas Smedegaard (2019-03-17 23:48:57) > >>>>> Quoting Xavier (2019-03-17 23:12:51) > >>>>>> Control: reassign 924807 uglify-js > >>>>>> Control: reassign 924809 uglify-js > >>>>>> Control: merge 924807 924809 > >>>>>> > >>>>>> Bug seems to come from conflict between > >>>>>> https://tracker.debian.org/pkg/uglify-js and > >>>>>> https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed > >>>>>> with uglifyjs > >>>>> > >>>>> Problem is packages depending on uglifyjs and webpack together: webpack > >>>>> depends indirectly on node-uglify 2.x, whereas uglifyjs is either a > >>>>> virtual package provided by node-uglify 2.x or (since recently) a real > >>>>> package depending on node-uglyfy-js 3.x. > >>>>> > >>>>> Yes, the problem emerged when node-uglify was introduced as a real > >>>>> package, but the fix is for those packages depending on uglifyjs and > >>>>> webpack together to depend on node-uglify 2.x instead of the virtual > >>>>> package. > >>>>> > >>>>> Please revert these reassignments: This cannot be fixed in uglifyjs 3.x. > >>>> > >>>> Put differently, the problem is packages depending both unversioned and > >>>> transitively versioned on uglifyjs - that works only as long as the > >>>> transitive dependency happens to be newest major release of uglifyjs. > >>>> > >>>> - Jonas > >>> > >>> List of packages that are affected by this change: > > > > Please clarify how you produced a list of packages which depend *both* > > unversioned and *also* transitively versioned on uglifyjs. > > > > ...or clarify what other list you produced and why you find such other > > list relevant here. > > I pushed this list taken from UDD database (reverse build depends) + > "apt-cache rdepends", just to help to understand the impact of this bug. > If it is not useful, please ignore my message > > >> If I understand (but maybe I'm wrong), this means that in buster it is > >> not possible to have uglifyjs installed with one of these 14 packages > >> or their dependencies (`apt-cache rdepends --recurse node-uglify` > >> returns several thousands package names). > > > > Please elaborate why - either based on my explanation of the problem > > quoted above, or elaborate on which _different_ theory you have of what > > is the underlying problem you try to solve. > > I do not have a theory, just want to help (I'm not uploader of any > package concerned). So ignore my mail if it is not clear/useful. Ok: Since I don't recognize your list as matching the problem as I see it, I will ignore your provided list. Please note that I am _not_ saying that your list is wrong, nor that my view of the problem is correct. Only that I don't understand your info. > The fact is that today, it is not possible to have both webpack (or > some other packages) and uglifyjs on the same machine. Since you merged and reassigned bugs, packages will get kicked out of Buster because they cannot be fixed. I urge you to either stand by your change by engaging in discussions on theories as to what is the real problem here, or if you don't want to do that (or don't have the time, or don't understand the problem well enough) then I recommend that you consider reverting those changes done by you. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
[toc] | [prev] | [next] | [standalone]
| From | Jérémy Lal <kapouer@melix.org> |
|---|---|
| Date | 2019-03-22 15:00 +0100 |
| Subject | Bug#925211: uglifyjs conflicts with webpack which can hinder JS maintainers work |
| Message-ID | <xEsSe-82b-7@gated-at.bofh.it> |
| In reply to | #950430 |
[Multipart message — attachments visible in raw view] — view raw
Hi, it takes some time to understand what's happening here, and since fixing it properly will require quite some work on multiple packages, i add my notes to this bug report. Nota Bene: i use "webpack" here but the sake of the example. # Situation Because uglify version 2 compiles software that uglify version 3 does not compile correctly, and vice-versa, there are two versions in debian: * uglifyjs-2.8.29 builds node-uglify which provides uglifyjs * uglify-js-3.4.9 builds uglifyjs # Solutions (in my order of preference, to be adapted) 1. Packages not building with uglifyjs 2 should be fixed to build with uglifyjs 3. Not a trivial thing to do and it's deep freeze now. 2. Distribute /usr/bin/uglifyjsN and fix all packages calling /usr/bin/uglifyjs to call uglifyjsN, when they can't be fixed to use latest version of /usr/bin/uglifyjs. # Slight improvement that might be done for buster IF apt behaves like i think it will, to allow both /usr/bin/uglifyjs and node-uglify package to be installed: * uglify-js-3.4.9 builds node-uglify-js which provides uglifyjs and conflicts uglifyjs (<< 3.5.0-2), and remove uglifyjs binary package (to get it to be pure virtual package). However, if dependencies both try to install node-uglify and node-uglify-js it will still fail, but it's not as bad as a direct conflict with /usr/bin/uglifyjs. It could be misleading, though, to have an unexpected version, so maybe the best thing is to do nothing for Buster. Jérémy
[toc] | [prev] | [next] | [standalone]
| From | Jérémy Lal <kapouer@melix.org> |
|---|---|
| Date | 2019-03-22 16:30 +0100 |
| Subject | Bug#925211: [Pkg-javascript-devel] Bug#925211: uglifyjs conflicts with webpack which can hinder JS maintainers work |
| Message-ID | <xEuhk-z0-13@gated-at.bofh.it> |
| In reply to | #950430 |
[Multipart message — attachments visible in raw view] — view raw
Le ven. 22 mars 2019 à 15:51, Jonas Smedegaard <jonas@jones.dk> a écrit : > Quoting Jérémy Lal (2019-03-22 14:54:07) > > it takes some time to understand what's happening here, and since > > fixing it properly will require quite some work on multiple packages, > > i add my notes to this bug report. > > I fail to recognize your description below of the situation and how it > involves "quite some work" to solve. Did you see my description at https://bugs.debian.org/924807#28 ? > Yes, changing the dependency on uglifyjs to node-uglify of all concerned packages. Doing so without regressions will require quite some work. The other solution - migrate all packages to uglifyjs 3 - requires a lot more work. > # Situation > > Because uglify version 2 compiles software that uglify version 3 does > > not compile correctly, and vice-versa, > > No (unless I am missing out on some information), the difference is not > correctness of processing but difference in API (when linked with other > NodeJS libraries) and ABI (when using certain command-line options). > Indeed. > > there are two versions in debian: > > * uglifyjs-2.8.29 builds node-uglify which provides uglifyjs > > * uglify-js-3.4.9 builds uglifyjs > > Correct. > > > > # Solutions (in my order of preference, to be adapted) > > 1. Packages not building with uglifyjs 2 should be fixed to build with > > uglifyjs 3. > > Not a trivial thing to do and it's deep freeze now. > > [ assuming you mean "...now building..." ] > That is certainly the long-term plan, because only v3 is actively > maintained. > > Repackaging should however not be needed urgently, as v2 and v3 should > generally coexist fine. My turn to not understand: many packages not coinstallable due to a conflict is fine ? node-uglify conflicts with node-uglify-js. > Only cases where both ends up attempted used > together need urgent fixing. > Sure, that needs urgent fixing. However, debian users developing websites will typically want to use webpack and uglifyjs. And currently in Buster they won't be able to install both, and likewise with many other packages. > 2. Distribute /usr/bin/uglifyjsN and fix all packages calling > > /usr/bin/uglifyjs to call > > uglifyjsN, when they can't be fixed to use latest version of > > /usr/bin/uglifyjs. > > > > # Slight improvement that might be done for buster > > IF apt behaves like i think it will, to allow both /usr/bin/uglifyjs and > > node-uglify > > package to be installed: > > * uglify-js-3.4.9 builds node-uglify-js which provides uglifyjs and > > conflicts uglifyjs (<< 3.5.0-2), > > and remove uglifyjs binary package (to get it to be pure virtual > package). > > > > However, if dependencies both try to install node-uglify and > node-uglify-js > > it will still fail, > > but it's not as bad as a direct conflict with /usr/bin/uglifyjs. > > It could be misleading, though, to have an unexpected version, so maybe > the > > best thing > > is to do nothing for Buster. > > Sorry, I am lost on what you propose here - especially the short-term > part. Can you perhaps provide some concrete examples of packages that > are broken now and are solved by... what exact change, for Buster? > The proposed change is to switch back uglifyjs to a pure virtual package, as it was before, (if what i know about apt is right) that would solve the main example above: install webpack + uglifyjs. I do care to avoid further mess and i understand that no change shall be made on a hurry, it is just something i wanted to discuss. Jérémy
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web