[Pkg-e-devel] SOLVED: Re: [e-users] doing an upgrade just trashed e

[Albin Tonnerre]

> Reverse Depends:
>   e17:i386,e17
>   e17-dev,e17 0.17.3-3
>   e17-dbg,e17 0.17.3-3
>   e17-data,e17
> Dependencies:
> 0.17.3-3 - libasound2 (2 1.0.16) libc6 (2 2.14) libdbus-1-3 (2 1.0.2)
> libecore-con1 (2 1.7.7) libecore-evas1 (2 1.7.7) libecore-file1 (2
> 1.7.7) libecore-imf1 (2 1.7.7) libecore-input1 (2 1.7.7) libecore-ipc1
> (2 1.7.7) libecore-x1 (2 1.7.7) libecore1 (2 1.7.7) libedbus1 (2 1.7.7)
> libedje1 (2 1.7.4) libeet1 (2 1.6.0) libefreet1 (2 1.7.7) libeina1 (2
> 1.7.4) libeio1 (2 1.7.4) libevas1 (2 1.7.7) libpam0g (2 0.99.7.1)
> libxcb-keysyms1 (2 0.3.9) libxcb-shape0 (0 (null)) libxcb1 (0 (null))
> e17-data (5 0.17.3-3) libevas1-engine-software-x11 (0 (null))
> libedje-bin (0 (null)) dbus-x11 (0 (null)) pm-utils (0 (null))
> enlightenment (0 (null)) enlightenment:i386 (0 (null)) e17:i386 (0
> (null)) Provides: 0.17.3-3 - x-window-manager Reverse Provides:
>
> The first to report '(0 (null))' was libevas1-engine-software-x11,
> which looked related to my error, so I tried to manually install it:
>
> # apt-get install libevas1-engine-software-x11
>
> which in fact needed to be installed, and that pulled in a bunch of
> other stuff as well.
>
> Then I re-ran apt-cache, but it looked the same. So I stepped through
> the rest of the packages that also had '(0 (null))' in the version.
>
> # apt-get install libedje-bin
>
> which also needed to be upgraded, and it pulled in some stuff too.
>
> The rest of the '(0 (null))' pkgs were okay.
>
> I flipped back to vt7, and tried logging in and it worked.
> Whoo-Friggin-Hoo!!!
>
> THAT was stressful - I have work to do! :)
>
> NO IDEA why the package did not pull that stuff in right. I added the e
> packages maintainers to this email so they can have a look.

That's weird. I can't really see why something like that would happen.
You shouldn't have been able to keep the e17 package if one the
dependencies was missing...
-- 
Albin