Posts made by kvasudevan_8753

This will be useful for us too. An exporter will need to be written. An introduction to writing exporter can be found here: https://prometheus.io/docs/instrumenting/writing_exporters/

Thanks.

@atripp said in Debian Feed problem:

There hasn't been any activity or other reports of this problem since I asked the earlier questions.... it's obviously nothing we can reproduce.

If you can help by answering those questions then we can start to investigate. Thanks :)

@atripp said in Debian Feed problem:

How did you create the package? Please share the commands you used, etc.

Can you share this package? Please attach it or upload it

How did you push this package? Please share commands you used to do it

Thanks @atripp for having a look at this issue.

The debian package (rtpengine) was created using the instructions here: https://nickvsnetworking.com/rtpengine-installation-configuration/

We used docker to build our debian package, so summary of steps:

• install the dependencies and run the following in a container

ENV BCG_VER=${BCG_VER}
RUN curl https://codeload.github.com/BelledonneCommunications/bcg729/tar.gz/${BCG_VER} --output bcg729_${BCG_VER}.orig.tar.gz && tar zxf bcg729_${BCG_VER}.orig.tar.gz
RUN git clone https://github.com/ossobv/bcg729-deb.git bcg729-${BCG_VER}/debian
RUN cd bcg729-${BCG_VER} && dpkg-buildpackage -us -uc -sa
RUN dpkg -i libbcg729-*.deb
ENV RTP_VER=${RTP_VER}
RUN git clone https://github.com/sipwise/rtpengine.git
RUN cd rtpengine && git checkout ${RTP_VER} && dpkg-checkbuilddeps && dpkg-buildpackage

Yes, I have the package, happy to upload it to your file share site if you have one (Alternatively, it's available here: https://filebin.net/tq2ebua1o38z5w5l)

The package was pushed using curl:

curl https://proget.XXXX/debian-packages/upload/bionic-uw/main/ngcp-rtpengine_7.5.4.1+0~mr7.5.4.1_all.deb --user 'debupload:XXXXX' --upload-file ngcp-rtpengine_7.5.4.1+0~mr7.5.4.1_all.deb

On the backend proget server, I can see the file has been uploaded and it's definitely not 0 bytes

-Krish

Has there been a workaround/resolution to this issue? I seem to have the same problem with the debian feed. The upload is fine, as I can confirm on the proget backend, the file is uploaded fine. However when we download the package via apt-get or via UI, the package is zero bytes. We are on proget 5.2.30 and we are running proget docker container.

Thanks

Thanks for the update.

Hello,

When pushing to proget to a nuget feed with an incorrect API key, proget responds with the following error message:

choco push hello.6.0.399.nupkg -s https://proget.dev.xx.yy/testfeed -k <key>
Attempting to push hello.6.0.399.nupkg to https://proget.xx.yy/testfeed
Cannot access a disposed object.
Object name: 'System.Net.Sockets.NetworkStream'.

Giving the correct api key, works as expected. It would be help if the error was a 401). I am using [1] for choco client.

-Thanks.

[1] https://github.com/Linuturk/mono-choco

5.2.30 works for me. I see the files restored. Thanks inedo!

Thank you. I will test this later this afternoon and update.

To delete a package using curl:

curl -kL -v -X DELETE -u Admin:<pass> http://<api endpoint url>/package/<package_name>/<package_version>

you can get the api endpoint url from the feed settings. top right hand corner.

Hello,

Running the latest proget docker for linux, seems to indicate the bmdbupdate.exe is missing. Here is the message:

ProGet version is 5.2.30.4.
Attempting to use shared configuration for ProGet.
Shared configuration file loaded from /usr/share/Inedo/SharedConfig/ProGet.config.
No encryption key is configured. Credentials will be stored in plain text.
Current DB schema version is 5.2.29.8.
Cannot open assembly '/usr/local/proget/db/bmdbupdate.exe': No such file or directory.

What has changed?

Thanks
Krish