-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packages #20
Comments
Sebix, I would by all means support that. Do you know how to nominate packages for inclusion in the repositories? |
Attention @NullHypothesis |
A friendly Debian developer told me that you could create a package yourself and then find a Debian developer that has a look at it, and then uploads it for you. (That sounds easier than becoming a developer yourself, or convince another developer to do all the work for you.) |
Thanks @NullHypothesis, I will look into the package requirements then. |
Hi @sebix , I have researched the idea of getting the package into Debian repository (https://mentors.debian.net/intro-maintainers) a bit. On IRC I was told that the best sponsor is probably the Python team (https://wiki.debian.org/Teams/PythonModulesTeam). I will follow up on this and am supportive of the idea. The hold back at the moment, and what I intend to resolve first, is the possible licensing issue #25. BR Hadi |
Packages for OpenSUSE: https://build.opensuse.org/package/show/home:sebix/python3-pyasn Includes into official repos is pending, but I'm still unsure about the license. |
Builds succeed for Ubuntu 16.04. For Debian I need to change the version number (they have different policies), but it works too. Please test them (don't have an ubuntu at hand): Click on the distro's name in the right bar or "Download package" to get the .deb-file. |
Cool, thanks, will check. |
I have packages for CentOS, Debian, Fedora, OpenSUSE and Ubuntu: https://build.opensuse.org/package/show/home:sebix:intelmq/python3-pyasn Please test them. After #25 is resolved, we can get them upstream. |
And please think about reducing the amount of data shipped in the releases. Currently it's 70MB test data versus 0.5MB code and docs. |
Thank you! Will check both soon |
Thanks! |
Hi @sebix, did you eventually resolve the licensing issue in some manner? (I want to do a new minor release, and if you have any solution, I'd be happy to merge before I do, thanks!) |
See #25 |
Well, in #25 the conclusion was pytricia can be way forward, and I personally think the correct design is to have the back-end be a choice (either at compile time or at runtime)... But I unfortunately didn't get around to doing the work. That's why I was asking if you implemented any solution for yourself? Shall we close this thread and continue the discussion in #25? |
To deploy software more securely than via pip, we need packages for debian/ubuntu of used third-party libraries.
Would this be possible?
The text was updated successfully, but these errors were encountered: