Bug#838440: [Pkg-javascript-devel] Bug#838440: Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries
On 10/10/16 14:01, Sebastiaan Couwenberg wrote: > On 10/09/2016 11:02 PM, Sebastiaan Couwenberg wrote: >> On 10/09/2016 10:25 PM, Jérémy Lal wrote: >>> Now the same is going to happen with "powerpc" arch: libv8 is actually not >>> compatible with all processors supported by debian (ppc64xx are ok, though). >>> >>> Sebastiaan, i feel bad asking for your help again, but since you already >>> filled all the RM bugs once, i suppose you're in the best position to do it >>> again >>> for powerpc. >> >> Sure, the list of immediately affected packages is limited. > > There has been some progress getting the RM bugs processed. Several of > for armel are still outstanding, which may be due to the dependency > problems reported by dak for reverse dependencies. > > I thought that arch:all reverse dependencies didn't need to be removed > too, but I may be mistaken in that although dak has the option > --no-arch-all-rdeps for apparently that reason. > > I'll follow up on the outstanding bugreports to mention that only > arch:all rdeps are reported by dak in the dependency problems. Indeed, arch:all packages don't need to be removed. If dak complains about them, point it out they are arch:all and it's OK to break them. Cheers, and thanks for looking at this. Emilio
Bug#838440: [Pkg-javascript-devel] Bug#838440: Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries
On 10/09/2016 11:02 PM, Sebastiaan Couwenberg wrote: > On 10/09/2016 10:25 PM, Jérémy Lal wrote: >> Now the same is going to happen with "powerpc" arch: libv8 is actually not >> compatible with all processors supported by debian (ppc64xx are ok, though). >> >> Sebastiaan, i feel bad asking for your help again, but since you already >> filled all the RM bugs once, i suppose you're in the best position to do it >> again >> for powerpc. > > Sure, the list of immediately affected packages is limited. There has been some progress getting the RM bugs processed. Several of for armel are still outstanding, which may be due to the dependency problems reported by dak for reverse dependencies. I thought that arch:all reverse dependencies didn't need to be removed too, but I may be mistaken in that although dak has the option --no-arch-all-rdeps for apparently that reason. I'll follow up on the outstanding bugreports to mention that only arch:all rdeps are reported by dak in the dependency problems. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#838440: [Pkg-javascript-devel] Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries
On 10/09/2016 10:25 PM, Jérémy Lal wrote: > Now the same is going to happen with "powerpc" arch: libv8 is actually not > compatible with all processors supported by debian (ppc64xx are ok, though). > > Sebastiaan, i feel bad asking for your help again, but since you already > filled all the RM bugs once, i suppose you're in the best position to do it > again > for powerpc. Sure, the list of immediately affected packages is limited. Is there a bugreport or other reference for the powerpc issue I can include for more information in the RM bugs? Currently nodejs still built successfully on powerpc, so filing the RM bugs is a bit premature. The affected packages were retrieved from UDD as follows: udd=>SELECT DISTINCT source udd-> FROM packages udd-> WHERE distribution = 'debian' udd-> AND release = 'sid' udd-> AND architecture = 'powerpc' udd-> AND source != 'nodejs' udd-> AND (dependsLIKE '%nodejs%' OR udd(>recommends LIKE '%nodejs%') udd-> ORDER BY source udd-> ; source - almond codelite node-bones node-expat node-groove node-iconv node-leveldown node-mapnik node-sqlite3 node-srs node-stringprep node-topcube node-websocket node-ws node-xmlhttprequest node-zmq (16 rows) Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#838440: [Pkg-javascript-devel] Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries
2016-10-06 12:24 GMT+02:00 Sebastiaan Couwenberg : > On 10/06/2016 12:21 PM, Jérémy Lal wrote: > > 2016-09-21 11:53 GMT+02:00 Sebastiaan Couwenberg : > > > >> On 09/21/2016 11:34 AM, Jérémy Lal wrote: > >>> 2016-09-21 10:24 GMT+02:00 Emilio Pozuelo Monfort : > I see you dropped support for armel in #818552 and requested the > removal > of the outdated armel binaries. That's fine. However, nodejs doesn't > migrate to testing because the lack of armel binaries breaks a number > of packages that depend on nodejs on armel: > > trying: nodejs > skipped: nodejs (15, 0, 81) > got: 68+546: a-3:i-18:a-0:a-11:a-0:m-0:m-0:p-35:p-0:s-1:m-546 > * armel: node-almond, node-groove, node-iconv, node-leveldown, > node-node-expat, node-sqlite3, node-topcube, node-websocket, node-ws, > node-xmlhttprequest, qtwebchannel5-examples > > Those need to get their armel binaries removed as well. > > >>> > >>> Thank you for your help, at some point i believed the request for > removal > >>> implied removal of dependencies as well. > >>> Should i make another removal request ? Would you like to do it ? I'm > >>> super-busy right now. > >> > >> I've filed the RM bugs for the affected packages, some more may be > >> required for their reverse dependencies. > > > > Thank you. Can we close this bug now ? > > No, ftp-master has not removed all the rdeps yet, so there are still RM > bugs blocking this issue. Now the same is going to happen with "powerpc" arch: libv8 is actually not compatible with all processors supported by debian (ppc64xx are ok, though). Sebastiaan, i feel bad asking for your help again, but since you already filled all the RM bugs once, i suppose you're in the best position to do it again for powerpc. Jérémy.
Bug#838440: [Pkg-javascript-devel] Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries
On 10/06/2016 12:21 PM, Jérémy Lal wrote: > 2016-09-21 11:53 GMT+02:00 Sebastiaan Couwenberg : > >> On 09/21/2016 11:34 AM, Jérémy Lal wrote: >>> 2016-09-21 10:24 GMT+02:00 Emilio Pozuelo Monfort : I see you dropped support for armel in #818552 and requested the removal of the outdated armel binaries. That's fine. However, nodejs doesn't migrate to testing because the lack of armel binaries breaks a number of packages that depend on nodejs on armel: trying: nodejs skipped: nodejs (15, 0, 81) got: 68+546: a-3:i-18:a-0:a-11:a-0:m-0:m-0:p-35:p-0:s-1:m-546 * armel: node-almond, node-groove, node-iconv, node-leveldown, node-node-expat, node-sqlite3, node-topcube, node-websocket, node-ws, node-xmlhttprequest, qtwebchannel5-examples Those need to get their armel binaries removed as well. >>> >>> Thank you for your help, at some point i believed the request for removal >>> implied removal of dependencies as well. >>> Should i make another removal request ? Would you like to do it ? I'm >>> super-busy right now. >> >> I've filed the RM bugs for the affected packages, some more may be >> required for their reverse dependencies. > > Thank you. Can we close this bug now ? No, ftp-master has not removed all the rdeps yet, so there are still RM bugs blocking this issue. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#838440: [Pkg-javascript-devel] Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries
2016-09-21 11:53 GMT+02:00 Sebastiaan Couwenberg : > On 09/21/2016 11:34 AM, Jérémy Lal wrote: > > 2016-09-21 10:24 GMT+02:00 Emilio Pozuelo Monfort : > >> I see you dropped support for armel in #818552 and requested the removal > >> of the outdated armel binaries. That's fine. However, nodejs doesn't > >> migrate to testing because the lack of armel binaries breaks a number > >> of packages that depend on nodejs on armel: > >> > >> trying: nodejs > >> skipped: nodejs (15, 0, 81) > >> got: 68+546: a-3:i-18:a-0:a-11:a-0:m-0:m-0:p-35:p-0:s-1:m-546 > >> * armel: node-almond, node-groove, node-iconv, node-leveldown, > >> node-node-expat, node-sqlite3, node-topcube, node-websocket, node-ws, > >> node-xmlhttprequest, qtwebchannel5-examples > >> > >> Those need to get their armel binaries removed as well. > >> > > > > Thank you for your help, at some point i believed the request for removal > > implied removal of dependencies as well. > > Should i make another removal request ? Would you like to do it ? I'm > > super-busy right now. > > I've filed the RM bugs for the affected packages, some more may be > required for their reverse dependencies. > > Thank you. Can we close this bug now ? Jérémy
Bug#838440: [Pkg-javascript-devel] Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries
On 09/21/2016 11:34 AM, Jérémy Lal wrote: > 2016-09-21 10:24 GMT+02:00 Emilio Pozuelo Monfort : >> I see you dropped support for armel in #818552 and requested the removal >> of the outdated armel binaries. That's fine. However, nodejs doesn't >> migrate to testing because the lack of armel binaries breaks a number >> of packages that depend on nodejs on armel: >> >> trying: nodejs >> skipped: nodejs (15, 0, 81) >> got: 68+546: a-3:i-18:a-0:a-11:a-0:m-0:m-0:p-35:p-0:s-1:m-546 >> * armel: node-almond, node-groove, node-iconv, node-leveldown, >> node-node-expat, node-sqlite3, node-topcube, node-websocket, node-ws, >> node-xmlhttprequest, qtwebchannel5-examples >> >> Those need to get their armel binaries removed as well. >> > > Thank you for your help, at some point i believed the request for removal > implied removal of dependencies as well. > Should i make another removal request ? Would you like to do it ? I'm > super-busy right now. I've filed the RM bugs for the affected packages, some more may be required for their reverse dependencies. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries
2016-09-21 10:24 GMT+02:00 Emilio Pozuelo Monfort : > Source: nodejs > Version: 4.4.7~dfsg-2 > Severity: serious > > Hi, > > I see you dropped support for armel in #818552 and requested the removal > of the outdated armel binaries. That's fine. However, nodejs doesn't > migrate to testing because the lack of armel binaries breaks a number > of packages that depend on nodejs on armel: > > trying: nodejs > skipped: nodejs (15, 0, 81) > got: 68+546: a-3:i-18:a-0:a-11:a-0:m-0:m-0:p-35:p-0:s-1:m-546 > * armel: node-almond, node-groove, node-iconv, node-leveldown, > node-node-expat, node-sqlite3, node-topcube, node-websocket, node-ws, > node-xmlhttprequest, qtwebchannel5-examples > > Those need to get their armel binaries removed as well. > Thank you for your help, at some point i believed the request for removal implied removal of dependencies as well. Should i make another removal request ? Would you like to do it ? I'm super-busy right now. > Or perhaps, if the version in experimental works on armel (it still has > armel binaries) you could try to get that uploaded to sid? > It's just that nodejs actually builds fine on the buildd machines for armel, because those machines have better cpu than the lowest supported armel cpu. Jérémy
Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries
Source: nodejs Version: 4.4.7~dfsg-2 Severity: serious Hi, I see you dropped support for armel in #818552 and requested the removal of the outdated armel binaries. That's fine. However, nodejs doesn't migrate to testing because the lack of armel binaries breaks a number of packages that depend on nodejs on armel: trying: nodejs skipped: nodejs (15, 0, 81) got: 68+546: a-3:i-18:a-0:a-11:a-0:m-0:m-0:p-35:p-0:s-1:m-546 * armel: node-almond, node-groove, node-iconv, node-leveldown, node-node-expat, node-sqlite3, node-topcube, node-websocket, node-ws, node-xmlhttprequest, qtwebchannel5-examples Those need to get their armel binaries removed as well. Or perhaps, if the version in experimental works on armel (it still has armel binaries) you could try to get that uploaded to sid? Cheers, Emilio -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
