-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/18/2016 09:55 AM, Tom Hughes wrote: > On 18/01/16 14:45, Stephen Gallagher wrote: > >> Tom, sometime over the weekend you built nodejs-osenv in Rawhide >> rather than the f24-nodejs4 tag; this broke the ability to >> install the older npm package on Rawhide (and is breaking other >> projects' builds, such as Cockpit). > > It was already broken before that. The initial breakage was > sometime on Friday from your read-package-json update. > > I had previously built 2.0.2 in the side tag but when you updated > it to 2.0.3 you did it in the main tag. >
Crap, that was a mistake on my part. >> Can you look into whether npm can actually run with the new oserv >> and update the dep with %nodejs_fixdep if it can? Jared and I are >> going to continue working to finish the update to the new npm >> today, but if it continues to take extra time, we need to try to >> unbreak Rawhide concurrently. > > Well right now there is a vast list of dependency issues: > > npm-1.3.6-16.fc24.noarch requires npm(rimraf) < 0:2.3 > npm-1.3.6-16.fc24.noarch requires npm(retry) < 0:0.7 > npm-1.3.6-16.fc24.noarch requires npm(read-package-json) < 0:1.2 > npm-1.3.6-16.fc24.noarch requires npm(read-installed) < 0:0.3 > npm-1.3.6-16.fc24.noarch requires npm(opener) < 0:1.4 > npm-1.3.6-16.fc24.noarch requires npm(npm-user-validate) = 0:0.0.3 > npm-1.3.6-16.fc24.noarch requires npm(npm-registry-client) < 0:0.3 > npm-1.3.6-16.fc24.noarch requires npm(nopt) < 0:2.2 > npm-1.3.6-16.fc24.noarch requires npm(lockfile) < 0:0.5 > npm-1.3.6-16.fc24.noarch requires npm(init-package-json) = > 0:0.0.10 npm-1.3.6-16.fc24.noarch requires npm(ini) < 0:1.2 > npm-1.3.6-16.fc24.noarch requires npm(editor) = 0:0.0.4 > > Largely because, seeing that it had broken on Friday I was working > on the basis that we had decided to temporarily break it and > therefore didn't worry about things it was dependent on. > Yeah, sorry about that. Total screw-up on my part with read-package-json . > There are also a couple of issues lower down the stack where I > accidentally built something in f24 not realising that a dependency > was only in the side tag. > > I'll try fixdeping it and see what happens... > Probably not worth it in that case. I think we're only a couple packages away from being able to merge the side-tag in, so maybe we should just hold off and then do the frenzied fixup as soon as npm is done. Are you available to join Jared and I on IRC today? (What's your nick?) We're coordinating our efforts to get as much done as possible. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlac/a4ACgkQeiVVYja6o6OpdgCggVXKkFp29Tcpwd7WWjV9FxU3 QJgAoK3tj2NhJZvOgJrm9TJ7o2R1guME =njc4 -----END PGP SIGNATURE----- _______________________________________________ nodejs mailing list [email protected] http://lists.fedoraproject.org/admin/lists/[email protected]
