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
Currently the Manifest file can't be built because the med-3.3.1 source tarball has been removed by the providing website.
I feel like I searched half the internet for the git repository of this library, or at least a reupload of the old 3.3.1 version, and I just can't find it. Can anyone explain to me what open source library just provides periodical source tarballs and no git repository? Or did I miss anything?
Generally I think this Manifest should use fewer source tarballs. They just encourage these problems and they are generally less trustworthy (just look at the recent XZ backdoor).
The text was updated successfully, but these errors were encountered:
Generally I think this Manifest should use fewer source tarballs. They just encourage these problems and they are generally less trustworthy (just look at the recent XZ backdoor).
Generally I think this Manifest should use fewer source tarballs. They just encourage these problems and they are generally less trustworthy (just look at the recent XZ backdoor).
this is irrelevant.
I agree that this is not relevant for this issue. But it is certainly relevant for the project in general. I can create a separate issue for that if you want.
Currently the Manifest file can't be built because the
med-3.3.1
source tarball has been removed by the providing website.I feel like I searched half the internet for the git repository of this library, or at least a reupload of the old 3.3.1 version, and I just can't find it. Can anyone explain to me what open source library just provides periodical source tarballs and no git repository? Or did I miss anything?
Generally I think this Manifest should use fewer source tarballs. They just encourage these problems and they are generally less trustworthy (just look at the recent XZ backdoor).
The text was updated successfully, but these errors were encountered: