On 12/01/16 22:24, Troy Dawson wrote:
Here's the problem, and I think many of us nodejs packages have
hit it.
You update a package, every test you try works, great. You push it to
stable, and the next morning you get a pile of emails stating that you
broke all sorts of dependencies. Not that your new package can't
install, but other packages that depended on your package can no
longer install.
How can I check for dependent issues before I push to stable?
The best way I know is to check what requires the package:
dnf repoquery --whatrequires 'npm(ws)'
In this case the answer appears to be (in F23) nothing!
But if something does require it then check exactly what version it
requires with:
dnf repoquery --requires <requiring-package>
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/