Summary: | app-backup/spideroak-bin-4.6.9945: bundles a lot of stuff | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Dennis Schridde <dschridde+gentoobugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | blueness, esigra, proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://tinderboxlogs.s3.amazonaws.com/tbamd64.excelsior.flameeyes.eu/app-backup%3Aspideroak-bin-4.6.9945%3A20120716-065635.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 251464 |
Description
Diego Elio Pettenò (RETIRED)
2012-07-16 08:12:24 UTC
Dupe of bug #398317 ? Did you try USE=system-libs? No the problem is that it bundles lots of stuff, it shouldn't have an USE for this kind of stuff if it works with system libs (and if it doesn't, why the $* have an USE for it?). So please just fix it _properly_. (In reply to comment #2) > No the problem is that it bundles lots of stuff, it shouldn't have an USE > for this kind of stuff if it works with system libs (and if it doesn't, why > the $* have an USE for it?). > > So please just fix it _properly_. The bundled stuff is not identical to our system libs, and it is precompiled, not source which we could deal with. They patch the libraries and they do not disclose what they do. Since upstream is a service (they provide encrypted cloud space) and they do not support "mangled" clients, I opted for this use flag to let the user decide. The conditional "if it works with system libs" is not definitely decideable. Recommendations? So the reason to use system libs is reliability and security — if you don't know that the system libs are reliable for their use, don't use them! Honestly, in these cases, I would like to see the package being p.masked, or at least never ever ever go stable. I'd say drop the USE flag, and keep this bug _open_ for reference. (In reply to comment #4) > So the reason to use system libs is reliability and security — if you don't > know that the system libs are reliable for their use, don't use them! That was my original gut reaction but after some discussion we went with the USE flag. > Honestly, in these cases, I would like to see the package being p.masked, or > at least never ever ever go stable. Never stable is fine here, in my opinion. We have tried to get upstream to open but they have not. > I'd say drop the USE flag, and keep this bug _open_ for reference. Let's see if there are any more points regarding this before we move in that direction. @Dennis any comment on this? I really don't want to act without your ACK. (In reply to comment #6) > @Dennis any comment on this? I really don't want to act without your ACK. I am still using spideroak with USE=system-libs and it works fine so far. I'd really like to unbundle even the rest of the included stuff (i.e. python packages), and hence press more on upstream to disclose what versions and patches to external libraries/packages were used. On the other hand I understand Diego's concerns from a packagers perspective that the bundled libs might be more stable in this case. Hence my vote: Mask the useflag for now and press on upstream again, while removing any stable keywords. Then remove the flag altogether, should we figure out that upstream is unwilling to move. How can we shutup the Tinderbox QA warning? I.e. tell the system that we are aware of the bundled libs? You really can't shut up that warning (it's an extra one) — just keep the bug open as a reference if you don't mind, and that will be enough (I won't open any other). The rest of the plan sounds good to me. In profiles/default/linux/package.use.mask: # Anthony G. Basile <blueness@gentoo.org> (23 Jul 2012) # USE=system-libs is potentially unreliable and insecure # Bug #426798 app-backup/spideroak-bin system-libs !!! existing preserved libs:
>>> package: net-libs/libssh2-1.4.2
* - /usr/lib64/libssh2.so.1
* - /usr/lib64/libssh2.so.1.0.1
* used by /opt/SpiderOak/libcurl.so.4 (app-backup/spideroak-bin-4.6.9945)
* used by /opt/SpiderOak/pycurl.so (app-backup/spideroak-bin-4.6.9945)
How do we fix this? libssh2.so.1 is present in /opt/SpiderOak - can we tell portage about that?
(In reply to comment #10) > !!! existing preserved libs: > >>> package: net-libs/libssh2-1.4.2 > * - /usr/lib64/libssh2.so.1 > * - /usr/lib64/libssh2.so.1.0.1 > * used by /opt/SpiderOak/libcurl.so.4 > (app-backup/spideroak-bin-4.6.9945) > * used by /opt/SpiderOak/pycurl.so (app-backup/spideroak-bin-4.6.9945) > > How do we fix this? libssh2.so.1 is present in /opt/SpiderOak - can we tell > portage about that? Oh, this is bug #402081 again. |