[gentoo-user] emerge --unmerge fails

[gentoo-user] emerge --unmerge fails

[Hilco Wijbenga]

Hi all,

I'm trying to unmerge some packages. They all fail like this:

centaur ~ # emerge --unmerge arora
 * This action can remove important packages! In order to be safer, use
 * `emerge -pv --depclean <atom>` to check for reverse dependencies before
 * removing packages.

 www-client/arora
    selected: 0.11.0
   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 www-client/arora-0.11.0...
 * The 'prerm' phase of the 'www-client/arora-0.11.0' package has failed
 * with exit value -1.
 *
 * The problem occurred while executing the ebuild file named
 * 'arora-0.11.0.ebuild' located in the '/var/db/pkg/www-
 * client/arora-0.11.0' directory. If necessary, manually remove the
 * environment.bz2 file and/or the ebuild file located in that directory.
 *
 * Removal of the environment.bz2 file is preferred since it may allow the
 * removal phases to execute successfully. The ebuild will be sourced and
 * the eclasses from the current portage tree will be used when necessary.
 * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
 * removal phases to be skipped entirely.

 * Messages for package www-client/arora-0.11.0:

 * The 'prerm' phase of the 'www-client/arora-0.11.0' package has failed
 * with exit value -1.
 *
 * The problem occurred while executing the ebuild file named
 * 'arora-0.11.0.ebuild' located in the '/var/db/pkg/www-
 * client/arora-0.11.0' directory. If necessary, manually remove the
 * environment.bz2 file and/or the ebuild file located in that directory.
 *
 * Removal of the environment.bz2 file is preferred since it may allow the
 * removal phases to execute successfully. The ebuild will be sourced and
 * the eclasses from the current portage tree will be used when necessary.
 * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
 * removal phases to be skipped entirely.
Traceback (most recent call last):
  File "/usr/bin/emerge", line 42, in <module>
    retval = emerge_main()
  File "/usr/lib/portage/pym/_emerge/main.py", line 1492, in emerge_main
    myopts, myaction, myfiles, spinner)
  File "/usr/lib/portage/pym/_emerge/actions.py", line 2305, in action_uninstall
    valid_atoms, ldpath_mtimes, ordered=ordered)
  File "/usr/lib/portage/pym/_emerge/unmerge.py", line 507, in unmerge
    scheduler=scheduler)
  File "/usr/lib/portage/pym/portage/dbapi/vartree.py", line 4509, in unmerge
    ldpath_mtimes=ldpath_mtimes)
  File "/usr/lib/portage/pym/portage/dbapi/vartree.py", line 2160, in unmerge
    vartree=self.vartree)
  File "/usr/lib/portage/pym/portage/package/ebuild/doebuild.py", line
793, in doebuild
    fd_pipes=fd_pipes, returnpid=returnpid)
  File "/usr/lib/portage/pym/portage/package/ebuild/doebuild.py", line
1261, in spawn
    buf.fromfile(f, buffsize)
IOError: [Errno 5] Input/output error

centaur ~ # eix sys-apps/portage
[I] sys-apps/portage
     Available versions:  [P]2.1.6.7 2.1.6.13 2.1.7.17 2.1.8.3
(~)2.1.9 (~)2.1.9.1 (~)2.1.9.2 {M}(~)2.2_rc67 [M](~)2.2_rc77
[M](~)2.2_rc78 [M]**9999 {build doc epydoc linguas_pl python3 selinux}
     Installed versions:  2.2_rc67(10:58:51 07/14/10)(-build -doc
-epydoc -linguas_pl -python3 -selinux)
     Homepage:            http://www.gentoo.org/proj/en/portage/index.xml
     Description:         Portage is the package management and
distribution system for Gentoo

centaur ~ # eix dev-lang/python
[D] dev-lang/python
     Available versions:
        (2.4)   2.4.6
        (2.5)   2.5.4-r4
        (2.6)   2.6.4-r1 2.6.5-r2 2.6.5-r3{tbz2}
        (2.7)   [M](~)2.7
        (3.1)   3.1.2-r3 3.1.2-r4{tbz2}
        {-berkdb bootstrap build +cxx doc elibc_uclibc examples gdbm
ipv6 +ncurses +readline sqlite +ssl +threads tk +wide-unicode wininst
+xml}
     Installed versions:  2.6.6-r1(2.6){tbz2}(09:17:19 10/13/10)(gdbm
ncurses readline ssl threads wide-unicode xml -berkdb -build -doc
-elibc_uclibc -examples -ipv6 -sqlite -tk -wininst)
3.1.2-r4(3.1){tbz2}(12:04:46 09/07/10)(gdbm ncurses readline ssl
threads wide-unicode xml -build -doc -elibc_uclibc -examples -ipv6
-sqlite -tk -wininst)
     Homepage:            http://www.python.org/
     Description:         Python is an interpreted, interactive,
object-oriented programming language.

centaur ~ # eselect python list
Available Python interpreters:
  [1]   python2.6 *
  [2]   python3.1

Any ideas?

Cheers,
Hilco

Re: [gentoo-user] emerge --unmerge fails

[Paul Hartman]

On Wed, Oct 13, 2010 at 2:05 PM, Hilco Wijbenga
<hilco.wijbenga@gmail.com> wrote:
> Hi all,
>
> I'm trying to unmerge some packages. They all fail like this:


>  * The 'prerm' phase of the 'www-client/arora-0.11.0' package has failed
>  * with exit value -1.
>  *
>  * The problem occurred while executing the ebuild file named
>  * 'arora-0.11.0.ebuild' located in the '/var/db/pkg/www-
>  * client/arora-0.11.0' directory. If necessary, manually remove the
>  * environment.bz2 file and/or the ebuild file located in that directory.
>  *
>  * Removal of the environment.bz2 file is preferred since it may allow the
>  * removal phases to execute successfully. The ebuild will be sourced and
>  * the eclasses from the current portage tree will be used when necessary.

As the error suggests, remove that file
(/var/db/pkg/www-client/arora-0.11.0/environment.bz2) and then try
again, it should hopefully work then.

See this bug for more info:
https://bugs.gentoo.org/show_bug.cgi?id=211833

Re: [gentoo-user] emerge --unmerge fails

[Hilco Wijbenga]

On 13 October 2010 13:23, Paul Hartman <paul.hartman+gentoo@gmail.com> wrote:
> On Wed, Oct 13, 2010 at 2:05 PM, Hilco Wijbenga
> <hilco.wijbenga@gmail.com> wrote:
>> Hi all,
>>
>> I'm trying to unmerge some packages. They all fail like this:
>
>
>>  * The 'prerm' phase of the 'www-client/arora-0.11.0' package has failed
>>  * with exit value -1.
>>  *
>>  * The problem occurred while executing the ebuild file named
>>  * 'arora-0.11.0.ebuild' located in the '/var/db/pkg/www-
>>  * client/arora-0.11.0' directory. If necessary, manually remove the
>>  * environment.bz2 file and/or the ebuild file located in that directory.
>>  *
>>  * Removal of the environment.bz2 file is preferred since it may allow the
>>  * removal phases to execute successfully. The ebuild will be sourced and
>>  * the eclasses from the current portage tree will be used when necessary.
>
> As the error suggests, remove that file
> (/var/db/pkg/www-client/arora-0.11.0/environment.bz2) and then try
> again, it should hopefully work then.
>
> See this bug for more info:
> https://bugs.gentoo.org/show_bug.cgi?id=211833

Nope, removing environment.bz2 doesn't make any difference. Also, note
that it's not just this package. I have the same problem for at least
2 others. It seems a pandemic. :-)

Re: [gentoo-user] emerge --unmerge fails

[Dean Matzkov]

Have you tried upgrading to the latest version of Portage 2.2? The
newest version in the tree is currently portage-2.2_rc95, while you're
still using portage-2.2_rc67. Perhaps there's a bug causing this that
was fixed in subsequent release?

[gentoo-user] Re: emerge --unmerge fails

[walt]

On 10/13/2010 12:05 PM, Hilco Wijbenga wrote:
> Hi all,
>
> I'm trying to unmerge some packages. They all fail like this:
>
>>>> Unmerging www-client/arora-0.11.0...
>   * The 'prerm' phase of the 'www-client/arora-0.11.0' package has failed
>   * with exit value -1.

>
> centaur ~ # eix sys-apps/portage
>       Installed versions:  2.2_rc67(10:58:51 07/14/10)(-build -doc
>
> centaur ~ # eix dev-lang/python
>       Installed versions:  2.6.6-r1(2.6)

Hm, well I'm just now updating my ~amd64 machine and I see that both python
and portage are about to be updated.  I'm still with the 2.1.x portage, so
I can't comment on the version you're running.  Were your python and portage
just recently updated?

Did you run python-updater after the upgrade?  Perhaps the python ebuild does
that for you, I'm not sure.  Anyway I'd run it again just to make sure.

This could be a new bug in portage, too.  I'd suggest downgrading to your
previous portage version -- but I'm not sure how safe that is.  Anyone else
know?

Re: [gentoo-user] emerge --unmerge fails

[Willie Wong]

On Wed, Oct 13, 2010 at 12:05:40PM -0700, Hilco Wijbenga wrote:
>  * The 'prerm' phase of the 'www-client/arora-0.11.0' package has failed
>  * with exit value -1.
>  *
>  * The problem occurred while executing the ebuild file named
>  * 'arora-0.11.0.ebuild' located in the '/var/db/pkg/www-
>  * client/arora-0.11.0' directory. If necessary, manually remove the
>  * environment.bz2 file and/or the ebuild file located in that directory.
>  *
>  * Removal of the environment.bz2 file is preferred since it may allow the
>  * removal phases to execute successfully. The ebuild will be sourced and
>  * the eclasses from the current portage tree will be used when necessary.
>  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
>  * removal phases to be skipped entirely.
> 
>  * Messages for package www-client/arora-0.11.0:
> 
>  * The 'prerm' phase of the 'www-client/arora-0.11.0' package has failed
>  * with exit value -1.
>  *
>  * The problem occurred while executing the ebuild file named
>  * 'arora-0.11.0.ebuild' located in the '/var/db/pkg/www-
>  * client/arora-0.11.0' directory. If necessary, manually remove the
>  * environment.bz2 file and/or the ebuild file located in that directory.
>  *
>  * Removal of the environment.bz2 file is preferred since it may allow the
>  * removal phases to execute successfully. The ebuild will be sourced and
>  * the eclasses from the current portage tree will be used when necessary.
>  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
>  * removal phases to be skipped entirely.
> Traceback (most recent call last):
>   File "/usr/bin/emerge", line 42, in <module>
>     retval = emerge_main()
>   File "/usr/lib/portage/pym/_emerge/main.py", line 1492, in emerge_main
>     myopts, myaction, myfiles, spinner)
>   File "/usr/lib/portage/pym/_emerge/actions.py", line 2305, in action_uninstall
>     valid_atoms, ldpath_mtimes, ordered=ordered)
>   File "/usr/lib/portage/pym/_emerge/unmerge.py", line 507, in unmerge
>     scheduler=scheduler)
>   File "/usr/lib/portage/pym/portage/dbapi/vartree.py", line 4509, in unmerge
>     ldpath_mtimes=ldpath_mtimes)
>   File "/usr/lib/portage/pym/portage/dbapi/vartree.py", line 2160, in unmerge
>     vartree=self.vartree)
>   File "/usr/lib/portage/pym/portage/package/ebuild/doebuild.py", line
> 793, in doebuild
>     fd_pipes=fd_pipes, returnpid=returnpid)
>   File "/usr/lib/portage/pym/portage/package/ebuild/doebuild.py", line
> 1261, in spawn
>     buf.fromfile(f, buffsize)
> IOError: [Errno 5] Input/output error

Strange, an IO error? 
Which other packages do you have this problem with?


W
-- 
Willie W. Wong                                     wwong@math.princeton.edu
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire 
         et vice versa   ~~~  I. Newton

Re: [gentoo-user] emerge --unmerge fails

[Hilco Wijbenga]

On 13 October 2010 15:29, Dean Matzkov <bapabooiee@gmail.com> wrote:
> Have you tried upgrading to the latest version of Portage 2.2? The
> newest version in the tree is currently portage-2.2_rc95, while you're
> still using portage-2.2_rc67. Perhaps there's a bug causing this that
> was fixed in subsequent release?

I didn't really want to be running cutting edge portage but it did
solve my problem. I can unmerge again. :-)

Re: [gentoo-user] emerge --unmerge fails

[Dean Matzkov]

Well, if you were running portage-2-2_rc67, that's already pretty much
bleeding edge =P

But just out of curiosity, though, is there any particular reason
you're not running a more-stable version of Portage, such as v2.1.8.3
or v2.1.9.17? The 2.2 release-candidates are hard-masked for a reason
- which includes things randomly breaking, such as this unmerge issue
you experienced.

On Wed, Oct 13, 2010 at 7:52 PM, Hilco Wijbenga
<hilco.wijbenga@gmail.com> wrote:
> I didn't really want to be running cutting edge portage but it did
> solve my problem. I can unmerge again. :-)

Re: [gentoo-user] emerge --unmerge fails

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 651 bytes --]

On Wed, 13 Oct 2010 18:52:14 -0700, Hilco Wijbenga wrote:

> > Have you tried upgrading to the latest version of Portage 2.2? The
> > newest version in the tree is currently portage-2.2_rc95, while you're
> > still using portage-2.2_rc67. Perhaps there's a bug causing this that
> > was fixed in subsequent release?  
> 
> I didn't really want to be running cutting edge portage but it did
> solve my problem. I can unmerge again. :-)

2.2 is cutting edge, that's why it's masked. If you're going to run
cutting edge, you may as well use the sharpest version.


-- 
Neil Bothwick

Life Support System Failure - Reboot Patient (Y/n)?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] emerge --unmerge fails

[Hilco Wijbenga]

On 14 October 2010 00:38, Dean Matzkov <bapabooiee@gmail.com> wrote:
> Well, if you were running portage-2-2_rc67, that's already pretty much
> bleeding edge =P

Yeah, I was wondering if someone would notice that. :-)

> But just out of curiosity, though, is there any particular reason
> you're not running a more-stable version of Portage, such as v2.1.8.3
> or v2.1.9.17? The 2.2 release-candidates are hard-masked for a reason
> - which includes things randomly breaking, such as this unmerge issue
> you experienced.

I don't remember exactly but there was a feature I wanted that wasn't
in Portage 2.1. I think it was Sets. I believe I needed it (or thought
I needed it) to simplify installing KDE.

Re: [gentoo-user] emerge --unmerge fails

[Hilco Wijbenga]

On 14 October 2010 01:36, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Wed, 13 Oct 2010 18:52:14 -0700, Hilco Wijbenga wrote:
>> > Have you tried upgrading to the latest version of Portage 2.2? The
>> > newest version in the tree is currently portage-2.2_rc95, while you're
>> > still using portage-2.2_rc67. Perhaps there's a bug causing this that
>> > was fixed in subsequent release?
>>
>> I didn't really want to be running cutting edge portage but it did
>> solve my problem. I can unmerge again. :-)
>
> 2.2 is cutting edge, that's why it's masked. If you're going to run
> cutting edge, you may as well use the sharpest version.

True. Would it be safe to downgrade to the latest 2.1?

Re: [gentoo-user] emerge --unmerge fails

[Paul Hartman]

On Thu, Oct 14, 2010 at 2:38 AM, Dean Matzkov <bapabooiee@gmail.com> wrote:
> Well, if you were running portage-2-2_rc67, that's already pretty much
> bleeding edge =P

Except there have been about 30 update releases since that one. Only
the Changelog knows how many things have been fixed in that time. :)