Including upstream requirements
Now that internal OSM software does not specify python modules in
setup.py, we need to include the requirements.txt from the module
in the requirements-dev.in to generate the full list properly.
Change-Id: Ieebd667829444217d1d38e05261d6f50b9f0d180
Signed-off-by: beierlm <mark.beierl@canonical.com>
diff --git a/requirements-dev.in b/requirements-dev.in
index 823c52c..ec714a2 100644
--- a/requirements-dev.in
+++ b/requirements-dev.in
@@ -13,5 +13,8 @@
# See the License for the specific language governing permissions and
# limitations under the License.
--e git+https://osm.etsi.org/gerrit/osm/common.git@master#egg=osm-common
--e git+https://osm.etsi.org/gerrit/osm/N2VC.git@master#egg=n2vc
+git+https://osm.etsi.org/gerrit/osm/common.git@master#egg=osm-common
+-r https://osm.etsi.org/gitweb/?p=osm/common.git;a=blob_plain;f=requirements.txt;hb=master
+
+git+https://osm.etsi.org/gerrit/osm/N2VC.git@master#egg=n2vc
+-r https://osm.etsi.org/gitweb/?p=osm/N2VC.git;a=blob_plain;f=requirements.txt;hb=master