08-05-2013
Have you tried to install now that the dependency has been met?
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
I have a problem when i grep for a particular field among all fhe files in the directory.
if i do an ls -l field *
i can find it.
however at the moment the number of files in the directory are close to 28000 and it returns an
ksh: /usr/bin/grep: arg list too long
Assuming i... (2 Replies)
Discussion started by: manualvin
2 Replies
2. UNIX for Dummies Questions & Answers
I have 2 physical interfaces (bnx0 and bnx1) aggregated into aggr1. I need to assign second IP, and normally I know how to do it to physical interface (i.e. bnx0:1) however same trick (aggr1:1) is not working. Is there any way to do it? (0 Replies)
Discussion started by: bratan
0 Replies
3. Solaris
Hi all,
we are starting to build some basic infrastructure for using solaris 11.
I have built an IPS of solaris packages from the DVD images.
what I want to do next is create a repository of custom packages.
so in that case I want a publisher of "my-company-name" and not solaris.
can... (1 Reply)
Discussion started by: robsonde
1 Replies
4. Solaris
hi am trying to get some knowledge on Solaris common trouble shooting problems..
can some one help me in getting most common issues..
and how to solve those issues.
thanks in advance (4 Replies)
Discussion started by: aravindreddy
4 Replies
5. Solaris
I need some help getting a IPS repo setup for custom internal packages.
we already have an IPS for the oracle solaris package.
what I want is a repo called BOB that can be used for packages internal to company BOB.
I think I have created a repo called BOB, but it's not setup in the network... (1 Reply)
Discussion started by: robsonde
1 Replies
6. Solaris
Hi experts,
I have an X86 as my IPS server running ( uname -a SunOS 5.11 11.1 i86pc i386 i86pc). the IPS has the following package version:
prdb01b:~# pkg list -fa entire
NAME (PUBLISHER) VERSION IFO
entire ... (0 Replies)
Discussion started by: afadaghi
0 Replies
7. Solaris
What do people think of this tool? pkgtree - for displaying a visual representation of Solaris IPS package dependencies. (0 Replies)
Discussion started by: cambridge
0 Replies
8. Solaris
Hi guys,
I've got a local IPS repository on server 1 (local server in the basement) and a second one on server 2 in another data center. Both servers act as repository servers for their locations.
The publisher list is like this
pkg publisher
PUBLISHER TYPE STATUS... (4 Replies)
Discussion started by: dheitepriem
4 Replies
9. UNIX for Beginners Questions & Answers
i have problems with using solaries 8 . code and commands for extracting files from CD ? especially extracting file.jar from package and batch (1 Reply)
Discussion started by: moh_abaloo
1 Replies
LEARN ABOUT PLAN9
deb-symbols
deb-symbols(5) dpkg suite deb-symbols(5)
NAME
deb-symbols - Debian's extended shared library information file
SYNOPSIS
symbols
DESCRIPTION
The symbol files are shipped in Debian binary packages, and its format is a subset of the template symbol files used by dpkg-gensymbols(1)
in Debian source packages.
The format for an extended shared library dependency information entry in these files is:
library-soname main-dependency-template
[| alternative-dependency-template]
[...]
[* field-name: field-value]
[...]
symbol minimal-version [id-of-dependency-template]
The library-soname is exactly the value of the SONAME field as exported by objdump(1). A dependency-template is a dependency where #MINVER#
is dynamically replaced either by a version check like "(>= minimal-version)" or by nothing (if an unversioned dependency is deemed
sufficient).
Each exported symbol (listed as name@version, with version being "Base" if the library is not versioned) is associated to a minimal-version
of its dependency template (the main dependency template is always used and will end up being combined with the dependency template
referenced by id-of-dependency-template if present). The first alternative dependency template is numbered 1, the second one 2, etc.
Each entry for a library can also have some fields of meta-information. Those fields are stored on lines starting with an asterisk.
Currently, the only valid fields are:
Build-Depends-Package
It indicates the name of the "-dev" package associated to the library and is used by dpkg-shlibdeps to make sure that the dependency
generated is at least as strict as the corresponding build dependency (since dpkg 1.14.13).
Ignore-Blacklist-Groups
It indicates what blacklist groups should be ignored, as a whitespace separated list, so that the symbols contained in those groups
get included in the output file (since dpkg 1.17.6). This should only be necessary for toolchain packages providing those
blacklisted symbols. The available groups are system dependent, for ELF and GNU-based systems these are aeabi and gomp.
EXAMPLES
Simple symbols file
libftp.so.3 libftp3 #MINVER#
DefaultNetbuf@Base 3.1-1-6
FtpAccess@Base 3.1-1-6
[...]
Advanced symbols file
libGL.so.1 libgl1
| libgl1-mesa-glx #MINVER#
* Build-Depends-Package: libgl1-mesa-dev
publicGlSymbol@Base 6.3-1
[...]
implementationSpecificSymbol@Base 6.5.2-7 1
[...]
SEE ALSO
https://wiki.debian.org/Projects/ImprovedDpkgShlibdeps
dpkg-shlibdeps(1), dpkg-gensymbols(1).
1.19.0.5 2018-04-16 deb-symbols(5)