You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm packaging gitlab for debian and gollum lib is a dependency. We keep only one version of a gem in the archive and currently we have github-markup 1.4.0 and gollum-lib 4.1.0. Even though we have a newer minor release available in the archive, it is causing gitlab install to fail because the dependency is too strict. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821821
Can this be changed to ~> 1.3 (or ~> 1.4 for newer versions)? We could update to gollum-lib 4.2.0 right now, but the same problem will reappear when a newer github-markup minor release is uploaded.
The text was updated successfully, but these errors were encountered:
Yes. I would say it should also be possible to backport a more relaxed 1.3 dependency, but I need to look and see if there was a reason for the strict dependency in the first case.
I'm packaging gitlab for debian and gollum lib is a dependency. We keep only one version of a gem in the archive and currently we have github-markup 1.4.0 and gollum-lib 4.1.0. Even though we have a newer minor release available in the archive, it is causing gitlab install to fail because the dependency is too strict. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821821
Can this be changed to ~> 1.3 (or ~> 1.4 for newer versions)? We could update to gollum-lib 4.2.0 right now, but the same problem will reappear when a newer github-markup minor release is uploaded.
The text was updated successfully, but these errors were encountered: