multi-version nodejs-colors for nodejs-cli-table
by Piotr Popieluch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm reviewing Ralph's nodejs-cli-table [1]. The module depends on
nodejs-colors 1.0.3. Fixdep doesn't work as the module uses new features
introduced in 1.0.0. Updrading colors 0.6.2 to 1.0.3 will break all the
depending packages, see below.
What would be wise to do? Update all dependents or multiversion
nodejs-colors. What needs to be done to have colors multiversioned?
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1191212
for line in $(repoquery --whatrequires 'npm(colors)'); do
echo ${line}:
repoquery -R ${line} | grep colors;
echo
done
nodejs-dtree-0:0.0.7-1.fc21.noarch:
npm(colors) < 0.7
npm(colors) >= 0.6.2
nodejs-grunt-0:0.4.4-4.fc21.noarch:
npm(colors) < 1
npm(colors) >= 0.6
nodejs-grunt-html-validation-0:0.1.18-2.fc21.noarch:
npm(colors)
npm(colors) < 0.7
npm(colors) >= 0.6.0
nodejs-grunt-init-0:0.3.1-2.fc21.noarch:
npm(colors) < 1
npm(colors) >= 0.6
nodejs-grunt-saucelabs-0:8.3.3-1.fc21.noarch:
npm(colors) < 0.7
npm(colors) >= 0.6.2
nodejs-node-static-0:0.7.3-2.fc21.noarch:
npm(colors) >= 0.6.0
nodejs-replace-0:0.3.0-2.fc21.noarch:
npm(colors)
nodejs-winston-0:0.7.3-2.fc21.noarch:
npm(colors) < 0.7
npm(colors) >= 0.6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJU51TKAAoJEPHEApzE46n59cUP/35/IT0D4WcGKcOatyXmdqaV
UCDOk3E6+D0+3rmeVVwnFQpxWUzmMfriSvkxI/vLzuciMYyz1SBrK/D8tGZwMx0J
HwR00npkhzI7vi0COeOvKHvgXJfO4jk85q5sMkTfRRjk0HquRddy1FShK67jRTzb
Li20g0OtNRYqwsaMczcJF6RyP8txhfsFZsyop8xxF0EmmniPD3wWV01AZAgzBJcc
nnjtA09ehuq3RQXdkNLKyvSMBVfEfcJS8+oXIPwzvMnOCFatOrorelZHB61lqPXw
Bb6BV9TriZmMlXeMTUNqcntNSML7fJt7oAqXDqOH+ifsjsqmgNZbQDPQ/m+81hIM
MmQLeG+f+4XOqapi3FsLAwFIrHp16ZRHWng+ZOy0B0IBg2BXo7JK5nQDYAElqcpm
fOVKjaeEsjt0Gil8B1FjZkhuTcOKu7IqomtZGzzgUiZrmO99MAXn1mGYHDHA6T2g
eZoWEwVkJDe5mE+HKMN74TsXJxRb23a78Nb5gwTJYsDIMrTPLVSj64egl9/i3o+0
dHFzT6uL13Ri8LxaPwHE/tFWwCQONLK3jxQuwj0++DzikN9weCen4CfgLbKEN30J
gnpOEm0UpbhASAt9sGCwpmZM3wfV8RSxiURjd1ijwcGiWERfIEPn6qnBSHGBv7dz
oTqh28SZGhMBehA375yI
=OJEw
-----END PGP SIGNATURE-----
8 years, 9 months
nodejs-ws - should I change it to a noarch
by Troy Dawson
Hi All,
I was going through, updating my nodejs package for rawhide (f22) when I
found the nodejs-ws went from binary to pure javascript with version 0.7.1.
So, my question is this. Do I continue to leave it as an arch, so I
don't break thing, so should I go to noarch.
Switching from an arch to a noarch has bitten me in the past when people
do updates. I don't know if that is still the case.
What are people's thoughts. Should I switch it to a noarch?
I'm not planning on backporting this to older distributions if that
matters in the decision.
Thanks
Troy Dawson
p.s. Side note - This update also requires nodejs-ultron, if anyone
wants to do a review request.
https://bugzilla.redhat.com/show_bug.cgi?id=1188763
p.p.s. If there is already a fedora page explaining arch to noarch
policies, that would be great. Feel free to point me to it.
8 years, 9 months