Thanks for adding squirrelmail to Mageia! That said, I just tried an install of squirrelmail on Mga2 on another system that does not have Apache/PHP on it yet. This message is the result: # urpmi squirrelmail A requested package cannot be installed: squirrelmail-1.4.22-4.mga2.noarch (due to unsatisfied /usr/bin/php) Continue installation anyway? (Y/n) n A urpmf for /usr/bin/php returns several results with this being the most likely candidate - php-cli:/usr/bin/php. It seems to me that dependencies should be installed automatically instead of failing with an error. Not so?
How strange! urpmi should be able to resolve that. Are you sure your urpmi configuration and repository setup is OK?
Assignee: bugsquad => luigiwalser
Well, I used these commands in order: urpmi.update -av (all appears good from here) urpmi squirrelmail (with the result shown above) urpmf /usr/bin/php (which did return a lot of results, including the one I picked to install to get past the squirrelmail error) The repository setup on the server in question is using the kernel.org repository and that all appears to be "okay" as well. Is there something specific you want me to check?
Oh, during the install, after I installed php-cli, squirrelmail wanted apache-mpm-prefork-2.2.22-12 but did not want apache-2.2.22-12, which I had to install later to actually have a running web server. There was no service in systemctl or under /etc/rc.d/init.d for httpd before I added that.
Reproduced. Pushed new release [1] to core/updates_testing, which should fix it. Please test. BTW, in Cauldron resolving file deps works like it should so I guess we have a regression in urpmi/rpm in mga2. [1] squirrelmail-1.4.22-4.1.mga2
CC: (none) => jani.valimaa
Hmm, can't reproduce this anymore. Managed to reproduce this only once in just created chroot. Dunno what happened or what really was needed to fix this.
Yes, that wasn't a correct change to make. The file dependency is autogenerated by the autodeps scripts that run during package build, so if it isn't working correctly, we have bigger problems. Also, it would be a Requires and not a BuildRequires.
Actually BR is correct, if pkg containing the needed file is installed during the build the file dep is converted to pkg require.
(In reply to comment #7) > Actually BR is correct, if pkg containing the needed file is installed during > the build the file dep is converted to pkg require. If that's true, I suppose the BR would effective, but it doesn't make it correct. As far as it not pulling in apache, I think the proper fix for that would be for apache-mod_php to require apache instead of apache-mpm. I guess that's just fallout of the way we reorganized the requires within the apache packages. I can fix that when we do the next PHP security update.
Ah, yes. I was only fixing the "bug" mentioned in the first post and didn't touch the apache one..
(In reply to comment #8) > As far as it not pulling in apache, I think the proper fix for that would be > for apache-mod_php to require apache instead of apache-mpm. I guess that's > just fallout of the way we reorganized the requires within the apache packages. > I can fix that when we do the next PHP security update. This is fixed now in updates_testing. Once this is pushed to updates we can check to see if we can reproduce the other problem.
CC: jani.valimaa => (none)
Depends on: (none) => 7618
the update of php was pushed today an should come soon on yours mirrors, can you tell us if this bug is resolved when you get the update ? thanks
Keywords: (none) => NEEDINFO
Fixed now in Cauldron as well (php-5.4.8-7.mga3).
Status: NEW => RESOLVEDResolution: (none) => FIXED