Re: Algorithm for selecting between packages providing the same phpapi-20100525, change between squeeze - wheezy
On Tue, Jul 9, 2013 at 5:36 PM, Julien Cristau jcris...@debian.org wrote: On Tue, Jul 9, 2013 at 14:25:59 +0200, Ondřej Surý wrote: David, will this bug get fixed in wheezy? More people are starting to complain they get libapache2-mod-php5filter installed: #709027 I am still have no idea how to fix that in wheezy apart from fixing the selection algorithm in apt. I'm pretty sure what needs to happen here is to have exactly one package providing phpapi-20121212. You are quite right. I have prepared an php5 upload where only php5-common package provide phpapi-20121212 and the Provides: part have been dropped from various SAPIs. This will of course break all packages depending only on php5-module without declaring dependency on php5 (or specific php5 SAPI). After cleaning the list (grep-dctrl generated) by removing php libraries and various optional modules, where the php5 dependency is provided by main package (like fusionforge, mediawiki, nordugrid, horde), I have been left with this list: Package: bandwidthd-pgsql Depends: dbconfig-common, php5-gd, postgresql-client, ucf, debconf (= 0.5) | debconf-2.0, libc6 (= 2.14), libgd3 (= 2.1.0~alpha~), libpcap0.8 (= 0.9.8), libpng12-0 (= 1.2.13-4), libpq5 Package: davical Depends: debconf (= 1.0.32), php5-pgsql, postgresql-client (= 8.1), libawl-php (= 0.53-1~), libawl-php ( 0.54), libdbd-pg-perl, libyaml-perl On the other hand it will fix all packages declaring Depends: php5-module, php5 since the php5 SAPI dependency will be correctly resolved by dependency order in php5. We might be able to do the same for wheezy if we can push the fix for bandwidth-pgsql and davical to wheezy in the same run. That's probably up to release team to say if they would ack such action. O. -- Ondřej Surý ond...@sury.org
Re: Algorithm for selecting between packages providing the same phpapi-20100525, change between squeeze - wheezy
David, will this bug get fixed in wheezy? More people are starting to complain they get libapache2-mod-php5filter installed: #709027 I am still have no idea how to fix that in wheezy apart from fixing the selection algorithm in apt. Ondrej On Thu, May 23, 2013 at 8:57 PM, David Kalnischkies kalnischk...@gmail.comwrote: (funny, talk without end about init systems, but not a single response for a Debian native tool for a few days… and with funny, I meant sad) On Mon, May 20, 2013 at 3:16 PM, Ondřej Surý ond...@sury.org wrote: I am just curious about the selection mechanism in apt(itude), something has changed between squeeze and wheezy. apt and aptitude are not the same program and have very different behavior even through they share a 3 letter prefix and a library in various areas, so don't assume that what I am saying about the resolver in libapt which apt-get is using has anything to do with aptitude which has its own or the various other libapt front-ends which might or might not use the solver, or use it differently. (Ignoring that most of them could use an external solver) When I was noticed by a user that libapache2-mod-php5filter is installed by default when phpapi-20100525 (f.e. try installing php5-mysql in squeeze and wheezy). […] It seems that apt is ignoring Priority: (php5filter is extra) Actually, its not ignoring the Priority, in fact it sorts by Priority, just that the order changed recently (Nov 2011). A certain individual – who I am not going to call out in public to protect him from the lynch-mob – made the mistake of changing the code to sort lowest priority first … (fixed in his branch now added to the wheezy-maybe list) The solution would be to pick one default SAPI and do php5-SAPI | phpapi-20100525, but that would be hard to push into all r-depending PHP modules. This is indeed the recommend solution if you have a default as nowhere is defined which provider of a priority is chosen. While priority might be an obvious and easy choice for solvers working with a heuristic, I wouldn't be surprised if more deterministic solvers would go for the least 'changes' instead which might not be an optimal default choice. Maybe you want to try it with: apt-get install $whatever --solver $solver [where $solver is likely aspcud as we haven't that much more so far] Also: build-dependencies, but that is probably not an issue for PHP. Best regards David Kalnischkies -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caaz6_fdjfr7jvnx6b0wgttjpunbhhsmzuw48chmn2kmf-de...@mail.gmail.com -- Ondřej Surý ond...@sury.org
Re: Algorithm for selecting between packages providing the same phpapi-20100525, change between squeeze - wheezy
On Tue, Jul 9, 2013 at 2:25 PM, Ondřej Surý ond...@sury.org wrote: will this bug get fixed in wheezy? Just asked Michael about it again as we forgot about it for the last one, but as said, you are depending on an implementation detail of libapt, so this isn't going to fix your problem if another solver is used (e.g. aptitude [as it isn't using the relevant code] or an external solver). So just to repeat myself: Policy isn't defining which provider should be chosen, its assumed that the maintainer is expressing a preference or if not that ANY provider can be chosen based on whichever criteria the solver might want. (Still no checked what aptitude uses, but I bet its some sort of 'least disruptive changes' which is obviously better than priority alone, but not at all working in your favor of course) Best regards David Kalnischkies -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAAZ6_fBK2XYUEfVTmi1_Q6A0PT3UQ96esZOthjsOPgy=pee...@mail.gmail.com
Re: Algorithm for selecting between packages providing the same phpapi-20100525, change between squeeze - wheezy
On Tue, Jul 9, 2013 at 14:25:59 +0200, Ondřej Surý wrote: David, will this bug get fixed in wheezy? More people are starting to complain they get libapache2-mod-php5filter installed: #709027 I am still have no idea how to fix that in wheezy apart from fixing the selection algorithm in apt. I'm pretty sure what needs to happen here is to have exactly one package providing phpapi-20121212. Cheers, Julien signature.asc Description: Digital signature
Re: Algorithm for selecting between packages providing the same phpapi-20100525, change between squeeze - wheezy
(funny, talk without end about init systems, but not a single response for a Debian native tool for a few days… and with funny, I meant sad) On Mon, May 20, 2013 at 3:16 PM, Ondřej Surý ond...@sury.org wrote: I am just curious about the selection mechanism in apt(itude), something has changed between squeeze and wheezy. apt and aptitude are not the same program and have very different behavior even through they share a 3 letter prefix and a library in various areas, so don't assume that what I am saying about the resolver in libapt which apt-get is using has anything to do with aptitude which has its own or the various other libapt front-ends which might or might not use the solver, or use it differently. (Ignoring that most of them could use an external solver) When I was noticed by a user that libapache2-mod-php5filter is installed by default when phpapi-20100525 (f.e. try installing php5-mysql in squeeze and wheezy). […] It seems that apt is ignoring Priority: (php5filter is extra) Actually, its not ignoring the Priority, in fact it sorts by Priority, just that the order changed recently (Nov 2011). A certain individual – who I am not going to call out in public to protect him from the lynch-mob – made the mistake of changing the code to sort lowest priority first … (fixed in his branch now added to the wheezy-maybe list) The solution would be to pick one default SAPI and do php5-SAPI | phpapi-20100525, but that would be hard to push into all r-depending PHP modules. This is indeed the recommend solution if you have a default as nowhere is defined which provider of a priority is chosen. While priority might be an obvious and easy choice for solvers working with a heuristic, I wouldn't be surprised if more deterministic solvers would go for the least 'changes' instead which might not be an optimal default choice. Maybe you want to try it with: apt-get install $whatever --solver $solver [where $solver is likely aspcud as we haven't that much more so far] Also: build-dependencies, but that is probably not an issue for PHP. Best regards David Kalnischkies -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caaz6_fdjfr7jvnx6b0wgttjpunbhhsmzuw48chmn2kmf-de...@mail.gmail.com
Algorithm for selecting between packages providing the same phpapi-20100525, change between squeeze - wheezy
Hi, I am just curious about the selection mechanism in apt(itude), something has changed between squeeze and wheezy. When I was noticed by a user that libapache2-mod-php5filter is installed by default when phpapi-20100525 (f.e. try installing php5-mysql in squeeze and wheezy). squeeze: # apt-get install php5-mysql Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: apache2-mpm-prefork apache2-utils apache2.2-bin apache2.2-common libapache2-mod-php5 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap libcap2 libexpat1 libgcrypt11 libgnutls26 libgpg-error0 libgssapi-krb5-2 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libldap-2.4-2 libmysqlclient16 libonig2 libqdbm14 libsasl2-2 libtasn1-3 mime-support mysql-common php5-common procps ucf wheezy: # apt-get install php5-mysql Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: apache2-mpm-prefork apache2-utils apache2.2-bin apache2.2-common libapache2-mod-php5filter libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap libcap2 libexpat1 libgcrypt11 libgnutls26 libgpg-error0 libgssapi-krb5-2 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libldap-2.4-2 libmagic1 libmysqlclient18 libonig2 libp11-kit0 libpcre3 libprocps0 libqdbm14 libsasl2-2 libssl1.0.0 libtasn1-3 libxml2 mime-support mysql-common php5-common procps psmisc It seems that apt is ignoring Priority: (php5filter is extra) The solution would be to pick one default SAPI and do php5-SAPI | phpapi-20100525, but that would be hard to push into all r-depending PHP modules. Ondrej -- Ondřej Surý ond...@sury.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caljhhg-s6ikuntfd_dj35x3klscxixoj-qpyrtwa1vsvfmz...@mail.gmail.com
