LinuxForum.Fans
Тема

mate и libnotify

Автор: zenon 5 сообщений 4034 просмотров
#275816

Как разрулить не пойму, mate стоит из одноименного оверлея.
При обновлении мира требует libnotify, но из mate стоит x11-libs/libmatenotify
И получаем вот такое:

text
[ebuild  N     ] x11-libs/libnotify-0.7.5  USE="introspection (symlink) -doc {-test}" 0 kB

Total: 1 package (1 new), Size of downloads: 0 kB

Would you like to merge these packages? [Yes/No]

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) x11-libs/libnotify-0.7.5 * libnotify-0.7.5.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * introspection-20110205.m4.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking libnotify-0.7.5.tar.xz to /var/tmp/portage/x11-libs/libnotify-0.7.5/work >>> Unpacking introspection-20110205.m4.tar.bz2 to /var/tmp/portage/x11-libs/libnotify-0.7.5/work >>> Source unpacked in /var/tmp/portage/x11-libs/libnotify-0.7.5/work >>> Preparing source in /var/tmp/portage/x11-libs/libnotify-0.7.5/work/libnotify-0.7.5 ... * Running eautoreconf in '/var/tmp/portage/x11-libs/libnotify-0.7.5/work/libnotify-0.7.5' ... * Running gtkdocize --copy ... [ ok ] * Running libtoolize --install --copy --force --automake ... [ ok ] * Running aclocal -I m4 ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy ... [ ok ] * Running elibtoolize in: libnotify-0.7.5/build-aux/ * Applying portage/1.2.0 patch ... * Applying sed/1.5.6 patch ... * Applying as-needed/2.4.2 patch ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/x11-libs/libnotify-0.7.5/work/libnotify-0.7.5 ... * econf: updating libnotify-0.7.5/build-aux/config.guess with /usr/share/gnuconfig/config.guess * econf: updating libnotify-0.7.5/build-aux/config.sub with /usr/share/gnuconfig/config.sub ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-dependency-tracking --disable-static --enable-introspection checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for x86_64-pc-linux-gnu-gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... none checking how to run the C preprocessor... gcc -E checking whether make sets $(MAKE)... (cached) yes checking whether ln -s works... yes checking for an ANSI C-conforming const... yes checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for size_t... yes checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking how to print strings... printf checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/x86_64-pc-linux-gnu/bin/ld checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r checking for x86_64-pc-linux-gnu-objdump... x86_64-pc-linux-gnu-objdump checking how to recognize dependent libraries... pass_all checking for x86_64-pc-linux-gnu-dlltool... no checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar checking for archiver @FILE support... @ checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for x86_64-pc-linux-gnu-mt... no checking for mt... no checking if : is a manifest tool... no checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for x86_64-pc-linux-gnu-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for PACKAGE... yes checking for gobject-introspection... yes checking for gtkdoc-check... /usr/bin/gtkdoc-check checking for gtkdoc-rebase... /usr/bin/gtkdoc-rebase checking for gtkdoc-mkpdf... /usr/bin/gtkdoc-mkpdf checking whether to build gtk-doc documentation... no checking for xmlto... no checking whether to build DocBook documentation... yes checking for more warnings... no checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating docs/Makefile config.status: creating docs/reference/Makefile config.status: creating libnotify.pc config.status: creating libnotify/Makefile config.status: creating libnotify/notify-features.h config.status: creating tests/Makefile config.status: creating tools/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands

libnotify 0.7.5 ========================

prefix: /usr exec_prefix: ${prefix} bindir: ${exec_prefix}/bin datadir: /usr/share source code location: . cflags: -march=native -mtune=native -O2 -pipe -g0 -Wno-all -fomit-frame-pointer

Build docs: no

>>> Source configured. >>> Compiling source in /var/tmp/portage/x11-libs/libnotify-0.7.5/work/libnotify-0.7.5 ... make -j5 -l5 -s config.status: creating config.h config.status: config.h is unchanged Making all in libnotify GEN s-enum-types-h GEN s-enum-types-c CC notify.lo CC notification.lo CC notify-marshal.lo CC notify-enum-types.lo CCLD libnotify.la GISCAN Notify-0.7.gir GICOMP Notify-0.7.gir Making all in docs Making all in reference Making all in tools CC notify-send.o CCLD notify-send Making all in tests >>> Source compiled. >>> Test phase [not enabled]: x11-libs/libnotify-0.7.5

>>> Install libnotify-0.7.5 into /var/tmp/portage/x11-libs/libnotify-0.7.5/image/ category x11-libs make -j5 -l5 -s DESTDIR=/var/tmp/portage/x11-libs/libnotify-0.7.5/image/ install Making install in libnotify /bin/mkdir -p '/var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/lib64' /bin/mkdir -p '/var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/share/gir-1.0' /bin/mkdir -p '/var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/include/libnotify' /bin/sh ../libtool --mode=install /usr/bin/install -c libnotify.la '/var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/lib64' /bin/mkdir -p '/var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/lib64/girepository-1.0' /usr/bin/install -c -m 644 notify.h notify-features.h notification.h notify-enum-types.h '/var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/include/libnotify' /usr/bin/install -c -m 644 Notify-0.7.gir '/var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/share/gir-1.0' /usr/bin/install -c -m 644 Notify-0.7.typelib '/var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/lib64/girepository-1.0' libtool: install: /usr/bin/install -c .libs/libnotify.so.4.0.0 /var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/lib64/libnotify.so.4.0.0 libtool: install: (cd /var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/lib64 && { ln -s -f libnotify.so.4.0.0 libnotify.so.4 || { rm -f libnotify.so.4 && ln -s libnotify.so.4.0.0 libnotify.so.4; }; }) libtool: install: (cd /var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/lib64 && { ln -s -f libnotify.so.4.0.0 libnotify.so || { rm -f libnotify.so && ln -s libnotify.so.4.0.0 libnotify.so; }; }) libtool: install: /usr/bin/install -c .libs/libnotify.lai /var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/lib64/libnotify.la libtool: install: warning: remember to run `libtool --finish /usr/lib64' Making install in docs Making install in reference /usr/bin/install -c -m 644 ./html/annotation-glossary.html /usr/bin/install -c -m 644 ./html/api-index-deprecated.html /usr/bin/install -c -m 644 ./html/api-index-full.html /usr/bin/install -c -m 644 ./html/ch01.html /usr/bin/install -c -m 644 ./html/home.png /usr/bin/install -c -m 644 ./html/index.html /usr/bin/install -c -m 644 ./html/index.sgml /usr/bin/install -c -m 644 ./html/left.png /usr/bin/install -c -m 644 ./html/libnotify.devhelp2 /usr/bin/install -c -m 644 ./html/libnotify-notify.html /usr/bin/install -c -m 644 ./html/NotifyNotification.html /usr/bin/install -c -m 644 ./html/right.png /usr/bin/install -c -m 644 ./html/style.css /usr/bin/install -c -m 644 ./html/up.png http://library.gnome.org/devel/gdk-pixbuf/unstable/ -> /usr/share/gtk-doc/html/gdk-pixbuf/ (6) http://library.gnome.org/devel/glib/unstable/ -> /usr/share/gtk-doc/html/glib/ (77) http://library.gnome.org/devel/gobject/unstable/ -> /usr/share/gtk-doc/html/gobject/ (4) Making install in tools /bin/mkdir -p '/var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/bin' /bin/sh ../libtool --mode=install /usr/bin/install -c notify-send '/var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/bin' libtool: install: warning: `../libnotify/libnotify.la' has not been installed in `/usr/lib64' libtool: install: /usr/bin/install -c .libs/notify-send /var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/bin/notify-send Making install in tests /bin/mkdir -p '/var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/lib64/pkgconfig' /usr/bin/install -c -m 644 libnotify.pc '/var/tmp/portage/x11-libs/libnotify-0.7.5/image//usr/lib64/pkgconfig' «/var/tmp/portage/x11-libs/libnotify-0.7.5/image/usr/bin/notify-send» -> «/var/tmp/portage/x11-libs/libnotify-0.7.5/image/usr/bin/libnotify-notify-send» >>> Completed installing libnotify-0.7.5 into /var/tmp/portage/x11-libs/libnotify-0.7.5/image/

strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment -R .GCC.command.line usr/bin/libnotify-notify-send usr/lib64/libnotify.so.4.0.0 ecompressdir: bzip2 -9 /usr/share/doc

>>> Installing (1 of 1) x11-libs/libnotify-0.7.5 * checking 29 files for package collisions * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * Detected file collision(s): * * /usr/bin/notify-send * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * x11-libs/libmatenotify-1.4.1 * /usr/bin/notify-send * * Package 'x11-libs/libnotify-0.7.5' NOT merged due to file collisions. * If necessary, refer to your elog messages for the whole content of the * above message.

>>> Failed to install x11-libs/libnotify-0.7.5, Log file:

>>> '/var/tmp/portage/x11-libs/libnotify-0.7.5/temp/build.log'

* Messages for package x11-libs/libnotify-0.7.5:

* This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * Detected file collision(s): * * /usr/bin/notify-send * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * x11-libs/libmatenotify-1.4.1 * /usr/bin/notify-send * * Package 'x11-libs/libnotify-0.7.5' NOT merged due to file collisions. * If necessary, refer to your elog messages for the whole content of the * above message. * * The following package has failed to build or install: * * (x11-libs/libnotify-0.7.5::gentoo, ebuild scheduled for merge), Log file: * '/var/tmp/portage/x11-libs/libnotify-0.7.5/temp/build.log' *

* GNU info directory index is up-to-date.

ы. Профиль - desktop, флагов gnome/kde в make.conf нет

#275817

Можно сделать «неправильно»

text

mv /usr/bin/notify-send /usr/bin/notify-send.bak

...либо написать разработчику оверлея о замеченном «баге».

#275818

Можно попробовать так:

text

quickpkg --include-config=y x11-libs/libmatenotify
emerge -C  x11-libs/libmatenotify
emerge -1 x11-libs/libnotify

Затем проверить, будут ли коллизии

text

emerge -puDNv --with-bdeps=y world 

...и ошибки

text

revdep-rebuild
#275823

Удалил /usr/bin/notify-send, и собрал (дважды)

text
# emerge -pv libnotify libmatenotify

These are the packages that would be merged, in order:

Calculating dependencies... done! [ebuild R ] x11-libs/libnotify-0.7.5 USE="introspection (symlink) -doc {-test}" 0 kB [ebuild R ] x11-libs/libmatenotify-1.4.1::mate-overlay USE="symlink -doc {-test}" 0 kB

Total: 2 packages (2 reinstalls), Size of downloads: 0 kB

Больше коллизий нет. Не понял даже почему.

#275824
"newzenon" написал:
Больше коллизий нет. Не понял даже почему.

Видимо, порядок установки важен — один ebuild правильный, а второй — «кривой».

Войдите или зарегистрируйтесь, чтобы ответить.