xterm: Не могу ничего сделать с этим пакетом (он поврежден!)
sspphheerraa 24 марта, 2010 - 23:15
Сабж. С пакетом x11-terms/xterm что-то случилось, и теперь его не получается ни удалить, ни обновить, ни откатить.
Компилируется нормально, а вот уже в конце на стадии инсталляции выпадает следующее (во всех случаях одно и то же):
installing /temp/var/portage/x11-terms/xterm-250/image//usr/share/X11/app-defaults/XTerm-color installing /temp/var/portage/x11-terms/xterm-250/image//usr/share/X11/app-defaults/UXTerm installing /temp/var/portage/x11-terms/xterm-250/image//usr/share/X11/app-defaults/KOI8RXTerm ... installed app-defaults ... installed icons Completed installation of executables and documentation. Use "make install-ti" to install terminfo description. >>> Completed installing xterm-250 into /temp/var/portage/x11-terms/xterm-250/image/ strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment usr/bin/xterm usr/bin/resize ecompressdir: bzip2 -9 /usr/share/man >>> Installing (1 of 1) x11-terms/xterm-250 !!! Parse error in '/var/db/pkg/x11-terms/xterm-250/CONTENTS' !!! line 1: Unrecognized CONTENTS entry !!! line 2: Null byte found in CONTENTS entry portage: COUNTER for x11-terms/xterm-250 was corrupted; resetting to value of 0 * 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/xterm * /usr/bin/resize * /usr/bin/uxterm * /usr/bin/koi8rxterm * /usr/share/X11/app-defaults/XTerm * /usr/share/X11/app-defaults/UXTerm * /usr/share/X11/app-defaults/KOI8RXTerm * /usr/share/X11/app-defaults/XTerm-color * /usr/share/doc/xterm-250/ctlseqs.txt.bz2 * /usr/share/doc/xterm-250/README.bz2 * /usr/share/doc/xterm-250/README.i18n.bz2 * /usr/share/doc/xterm-250/html/xterm.log.html * /usr/share/man/man1/resize.1.bz2 * /usr/share/man/man1/xterm.1.bz2 * /usr/share/man/man1/uxterm.1.bz2 * /usr/share/man/man1/koi8rxterm.1.bz2 * /usr/share/pixmaps/xterm-color_32x32.xpm * /usr/share/pixmaps/xterm_48x48.xpm * /usr/share/pixmaps/xterm-color_48x48.xpm * /usr/share/pixmaps/xterm_32x32.xpm * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'x11-terms/xterm-250' merged despite file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. !!! Parse error in '/var/db/pkg/x11-terms/xterm-250/CONTENTS' !!! line 1: Unrecognized CONTENTS entry !!! line 2: Null byte found in CONTENTS entry !!! FAILED prerm: /var/db/pkg/x11-terms/xterm-250/EAPI * Messages for package x11-terms/xterm-250: * 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/xterm * /usr/bin/resize * /usr/bin/uxterm * /usr/bin/koi8rxterm * /usr/share/X11/app-defaults/XTerm * /usr/share/X11/app-defaults/UXTerm * /usr/share/X11/app-defaults/KOI8RXTerm * /usr/share/X11/app-defaults/XTerm-color * /usr/share/doc/xterm-250/ctlseqs.txt.bz2 * /usr/share/doc/xterm-250/README.bz2 * /usr/share/doc/xterm-250/README.i18n.bz2 * /usr/share/doc/xterm-250/html/xterm.log.html * /usr/share/man/man1/resize.1.bz2 * /usr/share/man/man1/xterm.1.bz2 * /usr/share/man/man1/uxterm.1.bz2 * /usr/share/man/man1/koi8rxterm.1.bz2 * /usr/share/pixmaps/xterm-color_32x32.xpm * /usr/share/pixmaps/xterm_48x48.xpm * /usr/share/pixmaps/xterm-color_48x48.xpm * /usr/share/pixmaps/xterm_32x32.xpm * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'x11-terms/xterm-250' merged despite file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. Traceback (most recent call last): File "/usr/bin/emerge", line 42, in <module> retval = emerge_main() File "/usr/lib64/portage/pym/_emerge/main.py", line 1393, in emerge_main myopts, myaction, myfiles, spinner) File "/usr/lib64/portage/pym/_emerge/actions.py", line 428, in action_build retval = mergetask.merge() File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 840, in merge rval = self._merge() File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 1148, in _merge self._main_loop() File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 1295, in _main_loop self._poll_loop() File "/usr/lib64/portage/pym/_emerge/PollScheduler.py", line 134, in _poll_loop handler(f, event) File "/usr/lib64/portage/pym/_emerge/SpawnProcess.py", line 198, in _output_handler self._unregister_if_appropriate(event) File "/usr/lib64/portage/pym/_emerge/AbstractPollTask.py", line 27, in _unregister_if_appropriate self.wait() File "/usr/lib64/portage/pym/_emerge/AsynchronousTask.py", line 42, in wait self._wait_hook() File "/usr/lib64/portage/pym/_emerge/AsynchronousTask.py", line 115, in _wait_hook self._exit_listener_stack.pop()(self) File "/usr/lib64/portage/pym/_emerge/EbuildPhase.py", line 93, in _post_phase_exit self.wait() File "/usr/lib64/portage/pym/_emerge/AsynchronousTask.py", line 42, in wait self._wait_hook() File "/usr/lib64/portage/pym/_emerge/AsynchronousTask.py", line 115, in _wait_hook self._exit_listener_stack.pop()(self) File "/usr/lib64/portage/pym/_emerge/TaskSequence.py", line 44, in _task_exit_handler self.wait() File "/usr/lib64/portage/pym/_emerge/AsynchronousTask.py", line 42, in wait self._wait_hook() File "/usr/lib64/portage/pym/_emerge/AsynchronousTask.py", line 115, in _wait_hook self._exit_listener_stack.pop()(self) File "/usr/lib64/portage/pym/_emerge/CompositeTask.py", line 106, in _default_final_exit return self.wait() File "/usr/lib64/portage/pym/_emerge/AsynchronousTask.py", line 42, in wait self._wait_hook() File "/usr/lib64/portage/pym/_emerge/AsynchronousTask.py", line 115, in _wait_hook self._exit_listener_stack.pop()(self) File "/usr/lib64/portage/pym/_emerge/EbuildBuild.py", line 181, in _build_exit self.wait() File "/usr/lib64/portage/pym/_emerge/AsynchronousTask.py", line 42, in wait self._wait_hook() File "/usr/lib64/portage/pym/_emerge/AsynchronousTask.py", line 115, in _wait_hook self._exit_listener_stack.pop()(self) File "/usr/lib64/portage/pym/_emerge/CompositeTask.py", line 106, in _default_final_exit return self.wait() File "/usr/lib64/portage/pym/_emerge/AsynchronousTask.py", line 42, in wait self._wait_hook() File "/usr/lib64/portage/pym/_emerge/AsynchronousTask.py", line 115, in _wait_hook self._exit_listener_stack.pop()(self) File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 1127, in _build_exit self._schedule() File "/usr/lib64/portage/pym/_emerge/PollScheduler.py", line 43, in _schedule return self._schedule_tasks() File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 1317, in _schedule_tasks if q.schedule(): File "/usr/lib64/portage/pym/_emerge/SequentialTaskQueue.py", line 56, in schedule task.start() File "/usr/lib64/portage/pym/_emerge/AsynchronousTask.py", line 24, in start self._start() File "/usr/lib64/portage/pym/_emerge/PackageMerge.py", line 44, in _start self.returncode = self.merge.merge() File "/usr/lib64/portage/pym/_emerge/MergeListItem.py", line 148, in merge retval = self._install_task.install() File "/usr/lib64/portage/pym/_emerge/EbuildBuild.py", line 283, in install rval = merge.execute() File "/usr/lib64/portage/pym/_emerge/EbuildMerge.py", line 27, in execute blockers=self.find_blockers) File "/usr/lib64/portage/pym/portage/__init__.py", line 7701, in merge mydbapi=mydbapi, prev_mtimes=prev_mtimes) File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 3240, in merge mydbapi=mydbapi, prev_mtimes=prev_mtimes) File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 3249, in _merge cleanup=cleanup, mydbapi=mydbapi, prev_mtimes=prev_mtimes) File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 2798, in treewalk ldpath_mtimes=prev_mtimes, others_in_slot=others_in_slot) File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 1442, in unmerge writemsg("%s\n" % str(e), noiselevel=-1) File "/usr/lib64/portage/pym/portage/exception.py", line 111, in __str__ {"cpv": self.cpv, "eapi": str(self.eapi).lstrip("-")} UnicodeEncodeError: 'ascii' codec can't encode character u'\ufffd' in position 0: ordinal not in range(128) localhost #
Что делать?
»
- Для комментирования войдите или зарегистрируйтесь
А что говорит emerge -C
А что говорит
SysA написал(а): А что
говорит следующее
# emerge -C xterm x11-terms/xterm selected: 250 protected: none omitted: none >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging x11-terms/xterm-250... !!! Parse error in '/var/db/pkg/x11-terms/xterm-250/CONTENTS' !!! line 1: Unrecognized CONTENTS entry !!! line 2: Null byte found in CONTENTS entry !!! FAILED prerm: /var/db/pkg/x11-terms/xterm-250/EAPI Traceback (most recent call last): File "/usr/bin/emerge", line 42, in <module> retval = emerge_main() File "/usr/lib64/portage/pym/_emerge/main.py", line 1330, in emerge_main myopts, myaction, myfiles, spinner) File "/usr/lib64/portage/pym/_emerge/actions.py", line 2112, in action_uninstall valid_atoms, ldpath_mtimes, ordered=ordered) File "/usr/lib64/portage/pym/_emerge/unmerge.py", line 421, in unmerge scheduler=scheduler) File "/usr/lib64/portage/pym/portage/__init__.py", line 7712, in unmerge ldpath_mtimes=ldpath_mtimes) File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 1442, in unmerge writemsg("%s\n" % str(e), noiselevel=-1) File "/usr/lib64/portage/pym/portage/exception.py", line 111, in __str__ {"cpv": self.cpv, "eapi": str(self.eapi).lstrip("-")} UnicodeEncodeError: 'ascii' codec can't encode character u'\ufffd' in position 0: ordinal not in range(128) localhost #_внезапно_
...и cлучилось это само собой и внезапно
//K.O.
sed -i 's/collision-protect//' /etc/make.conf && emerge xterm// не?taaroa написал(а): //
нет, - тоже самое что и в первом посте :(
Установку в xterm из xterm
Установку в xterm из xterm делаешь?
попробуй загрузиться без иксов ...
Gentoo - Symphony of Creations
Удалить (для параноиков
Удалить (для параноиков переместить куда-либо) файлы, вызывающие коллизию, т. е. :
Я ♥ Gentoo & Funtoo
* above message.
Должно бы сильно насторожить
Compute:
Bosch M2.8.1 -> custom Bosch M2.8.3 clone from Russia.
Speed about 260 km,Ram 2 pers.,HDD - 70 kg,210 FLOPS ;)
DolphinSoft
без иксов тоже самое
коллизии это похоже следствие, а не причина
Вот-вот... что там могло произойти? что значит "Null byte found..."
/
rm -rf /var/db/pkg/x11-terms/xterm-250/ & emerge -C xterm// не?taaroa написал(а): rm -rf
А мусора в системе после этого не останется? все-таки информация о файлах пакета
sspphheerraa
если удалить из базы запись о пакете, то ка потом будет работать emerge -C xterm - тайна великая сие есть =)
Compute:
Bosch M2.8.1 -> custom Bosch M2.8.3 clone from Russia.
Speed about 260 km,Ram 2 pers.,HDD - 70 kg,210 FLOPS ;)
/
Тайны в общем то никакой нет, удаление работать не будет, если снести всю базу, кому было действительно нужно, тот уже заюзал поиск и нашел решение подобных проблем (на том же forums.gentoo.org, например). Установка работать будет, с жалобами на коллизии.
//За два дня можно было уже не только найти решение проблемы, но и завершить
emerge -bekv system && emerge -bekv worldtaaroa написал(а): //За два
emerge -e это не решение проблемы, все тоже самое
?
Вы мое сообщение точно прочитали или "пробежались по диагонали"?
Еще раз:
0. за два дня можно было уже не только найти решение проблемы, но и завершить emerge -bekv system && emerge -bekv world (это к тому, что решения своей проблемы вы не искали) //K.O.
1. prerm не отрабатывает на каких то файлах, вероятное решение - прочекать fs, проверить пермишенсы (permissions) на эти файлы, просто удалить эти файлы, вы это пробовали сделать?