Olivier Berger:
> > I'm surprised that it would have been to be removed, instead of upgraded
> > by the new phpgroupware package (yes, the transition one).
> > Maybe you chose to remove it instead of upgrading it ?

aptitude chose to remove it (instead of upgrading), presumably because 
otherwise some packages would have been broken. I then selected the calendar 
and manual modules only, missing the core package. As it is with the testing 
release, the initial breakage may have been caused by who knows what.

> Anyway, all this rant may not have been the cause for the rights problem
> with the sessions directory...
>
> I was just puzzled by the status of the package in your report.
>
> I'll try and investigate the rights problem and see what's the real
> cause.

Thanks! Also thanks for your previous email, explaining things. I dug around 
in my system and found an aptitude log:

Aptitude 0.4.10: log report
Mon, Apr 14 2008 10:18:30 +0200

IMPORTANT: this log only lists intended actions; actions which fail due to
dpkg problems may not be completed.

Will install 163 packages, and remove 17 packages.
7057kB of disk space will be freed
===============================================================================
[REMOVE, NOT USED] lapack3
[REMOVE, NOT USED] libc-client2007
[REMOVE, NOT USED] libneon27-gnutls
[REMOVE, NOT USED] libsndfile1
[REMOVE, NOT USED] libsuitesparse
[REMOVE, NOT USED] mlock
[REMOVE, NOT USED] openoffice.org-style-hicontrast
[REMOVE, NOT USED] openoffice.org-style-industrial
[REMOVE, NOT USED] php5-imap
[REMOVE, NOT USED] phpgroupware
[INSTALL, DEPENDENCIES] libblas3gf
[INSTALL, DEPENDENCIES] libcurl3
[INSTALL, DEPENDENCIES] libgfortran3
[INSTALL, DEPENDENCIES] liblapack3gf
[INSTALL, DEPENDENCIES] libssh2-1
[INSTALL, DEPENDENCIES] libstlport4.6ldbl
[INSTALL, DEPENDENCIES] libsuitesparse-3.1.0
[INSTALL, DEPENDENCIES] libtotem-plparser10
[INSTALL, DEPENDENCIES] openoffice.org-writer2latex
[INSTALL, DEPENDENCIES] phpgroupware-0.9.16-admin
[INSTALL, DEPENDENCIES] phpgroupware-0.9.16-core-base
[INSTALL, DEPENDENCIES] phpgroupware-0.9.16-phpgwapi
[INSTALL, DEPENDENCIES] phpgroupware-0.9.16-preferences
[INSTALL, DEPENDENCIES] phpgroupware-0.9.16-setup
[REMOVE, DEPENDENCIES] libstlport4.6c2
[REMOVE, DEPENDENCIES] phpgroupware-admin
[REMOVE, DEPENDENCIES] phpgroupware-calendar
[REMOVE, DEPENDENCIES] phpgroupware-manual
[REMOVE, DEPENDENCIES] phpgroupware-phpgwapi
[REMOVE, DEPENDENCIES] phpgroupware-preferences
[REMOVE, DEPENDENCIES] phpgroupware-setup
[INSTALL] phpgroupware-0.9.16-calendar
[INSTALL] phpgroupware-0.9.16-doc
[INSTALL] phpgroupware-0.9.16-manual
[UPGRADE] aspell 0.60.5-2 -> 0.60.5-2.1
<... snip lotsa unrelated upgrades ...>
[UPGRADE] wwwconfig-common 0.0.48 -> 0.1.0
===============================================================================

Log complete.

I'm not entirely fluent with aptitude's dependency stuff, but what might have 
happened is this:

1. Once upon a time, I decided to install phpgroupware-calendar (among some 
other modules, but for simplicity let's pretend it's only the calendar).
2. aptitude resolved the dependencies and selected the phpgroupware package 
for installation, marking it "automatic."
3. Then April 14th came: I pressed "u", then "U" for complete system upgrade 
and a lot of phpgroupware dependencies were broken, so aptitude decided to 
select calendar for removal in order to preserve an unbroken system state.
4. Seeing that all installed packages which depend on phpgroupware were 
selected for removal, aptitude also selected phpgroupware for removal because 
it was marked "automatic".
5. Me, seeing phpgroupware is about to be removed, selects 
phpgroupware-0.9.16-calendar. However, phpgroupware-0.9.16 is not selected, 
as it's not in the dependency list (this is what's not intended in this 
situation, but difficult to fix, right?).

How, in this situation, it came to be that the permissions were broken, I 
cannot tell. I hope this info helps you a little anyway.


Best regards,
Alexander



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to