Summary: | net-analyzer/gsa-21.4.4 - Error: error:0308010C:digital envelope routines::unsupported | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | jonas.licht |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | jonas.licht, juippis, proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
emerge-history.txt environment etc.clang.tar.bz2 etc.portage.tar.bz2 logs.tar.bz2 net-analyzer:gsa-21.4.4:20221119-182855.log temp.tar.bz2 |
Description
Toralf Förster
![]() Created attachment 833821 [details]
emerge-info.txt
Created attachment 833823 [details]
emerge-history.txt
Created attachment 833825 [details]
environment
Created attachment 833827 [details]
etc.clang.tar.bz2
Created attachment 833829 [details]
etc.portage.tar.bz2
Created attachment 833831 [details]
logs.tar.bz2
Created attachment 833833 [details]
net-analyzer:gsa-21.4.4:20221119-182855.log
Created attachment 833835 [details]
temp.tar.bz2
@Toralf Förster I'm the old maintainer of whole gvm set in main gentoo tree. I was able to convince greenbone (upstream) to release tarball with pre-generated npm stuff. https://github.com/greenbone/gsa/issues/1261 It seems they stopped providing tar-balls. https://github.com/greenbone/gsa/issues/3188#issuecomment-941961494 It is very problematic to maintain this set in main gentoo tree. You need to ask a dev space for manually generating and uploading tar-ball or best shot is moving whole project to guru. Tell the story them and use trusted outside URI for pre-generated npm tarball. Good luck! https://bugs.gentoo.org/882031 https://bugs.gentoo.org/843419 You can generate the dep tarball and host it on your own Github space for example. It's true there'll be an "auditing issue" compared to upstreams release and it'd be best if upstream were to provide those tarballs again. But if this package doesn't have an active maintainer and it doesn't compile anymore, we're not going to keep it around either. @Jonas Licht, I worked hard with @Joonas Niilola to integrate the whole gvm set to main gentoo tree. Also this set have a great wiki that I write for gentoo. https://wiki.gentoo.org/wiki/Greenbone_Vulnerability_Management It is sad to see this set in last rites list. I cannot help you in main tree because I have issues with proxy-maint algorithm. But If you decide to move it to guru project I'm pleased to help you in our own space. (In reply to Hasan Calisir from comment #11) > @Jonas Licht, I worked hard with @Joonas Niilola to integrate the whole gvm > set to main gentoo tree. > > Also this set have a great wiki that I write for gentoo. > https://wiki.gentoo.org/wiki/Greenbone_Vulnerability_Management > > It is sad to see this set in last rites list. I cannot help you in main tree > because I have issues with proxy-maint algorithm. ? (In reply to Sam James from comment #12) > (In reply to Hasan Calisir from comment #11) > > @Jonas Licht, I worked hard with @Joonas Niilola to integrate the whole gvm > > set to main gentoo tree. > > > > Also this set have a great wiki that I write for gentoo. > > https://wiki.gentoo.org/wiki/Greenbone_Vulnerability_Management > > > > It is sad to see this set in last rites list. I cannot help you in main tree > > because I have issues with proxy-maint algorithm. > > ? I remembered you Sam, first, try to use sentences not single characters If you want to say something to me, be respectful. Second, this is not your business as you see I'm talking with the current maintainer of package about the issue. |