Reason: The symbol versioning "fix" breaks anything built with 3.0.0.
Masked by Sam James on 2024-06-25
Install this package:
emerge -a dev-libs/libassuan
If the package is masked, you can unmask it using the autounmask tool or standard emerge options:
autounmask dev-libs/libassuan
Or alternatively:
emerge --autounmask-write -a dev-libs/libassuan
| Version | EAPI | Keywords | Slot |
|---|---|---|---|
| 3.0.1-r1 | 8 | ~alpha ~amd64 ~arm ~arm64 ~hppa ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~arm64-macos ~x64-macos ~x64-solaris | 0/$(ver_cut 1-2) |
| 3.0.0-r1 | 8 | ~alpha amd64 arm arm64 ~hppa ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 ~sparc x86 ~arm64-macos ~x64-macos ~x64-solaris | 0/$(ver_cut 1-2) |
| 2.5.7 | 8 | ~alpha amd64 arm arm64 ~hppa ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 ~sparc x86 ~arm64-macos ~x64-macos ~x64-solaris | 0 |
<pkgmetadata> <maintainer type="project"> <email>base-system@gentoo.org</email> <name>Gentoo Base System</name> </maintainer> <longdescription> In an ideal world, Assuan is irrelevant. Assuan's primary use is to allow a client to interact with a non-persistent server. Using Assuan, this is accomplished by forking a subprocess and communicating with it via, for example, a pipe or unix domain socket. This method is neither elegant nor efficient especially when there is a lot of data spread across several transactions: not only is there a penalty for an increased number of context switches, but also a significant amount of data is MEMCPYed from the client to a file descriptor and from the file descriptor to the server. </longdescription> </pkgmetadata>
| Type | File | Size | Versions |
|---|---|---|---|
| DIST | libassuan-2.5.7.tar.bz2 | 605076 bytes | 2.5.7 |
| Type | File | Size |
|---|---|---|
| DIST | libassuan-2.5.7.tar.bz2.sig | 238 bytes |
| DIST | libassuan-3.0.0.tar.bz2 | 592353 bytes |
| DIST | libassuan-3.0.0.tar.bz2.sig | 119 bytes |
| DIST | libassuan-3.0.1.tar.bz2 | 592430 bytes |
| DIST | libassuan-3.0.1.tar.bz2.sig | 119 bytes |