Bug#408769: php5-sqlite3: package is completay unusable out of the box
so, the solution is: 1) add configuration for sqlite3 2) blame php dudz? I am not sure that they will like this, specially since there is no real policy, but a draft. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#408769: php5-sqlite3: package is completay unusable out of the box
At 1169998948 time_t, Diego Iastrubni wrote: > sed -i 's!...!/usr/share/php5!' /etc/php5/php.ini ...? Touching other packages configuration files = death penalty. > That's ugly, but it's an option. I assume this bug should be passed to the > php5 package maintainer. I agree. > The real question is, do we really need php4-sqlite3 and php5-sqlite3? Is it > possible to merge those 2 into one big happy package? What am *I* missing > now? The fact is that for now, it seems that all packages are splitted like that in order to not install useless modules, which makes sense. -- Julien Danjou .''`. Debian Developer : :' : http://julien.danjou.info `. `' http://people.debian.org/~acid `- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD signature.asc Description: Digital signature
Bug#408769: php5-sqlite3: package is completay unusable out of the box
sed -i 's!...!/usr/share/php5!' /etc/php5/php.ini ...? That's ugly, but it's an option. I assume this bug should be passed to the php5 package maintainer. The real question is, do we really need php4-sqlite3 and php5-sqlite3? Is it possible to merge those 2 into one big happy package? What am *I* missing now? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#408769: php5-sqlite3: package is completay unusable out of the box
At 1169993410 time_t, Diego Iastrubni wrote: > I am trying to build a package which depends on sqlite3. This breaks my > package in funny ways. This still does not justify critical severity. > You are talking about php5-sqlite3 and php4-sqlite3? Yes. > I am probably not following, but I think in both packages you are installing > the same php "include" file, so this can be worked around in some way. Yes, it's the same. > If splitting this package is a problem (or just using the same package for > PHP4 and PHP5), IMHO the best solution should be to modify the default > configuration of php4 and php5 to include /usr/share/php$PHPVERSION/, as > dictated by the php policy Draft, section 2.2.2. > http://webapps-common.alioth.debian.org/draft-php/html/ch-php-int.html#s-php-interpreter-fs Thanks for the pointer. It seems that: "The default PHP include path is: .:/etc/php:/usr/local/share/php/5.0:/usr/share/php5:/usr/share/php/5.0:/usr/share/php:/usr/local/share/php" So why including DB/sqlite3.php does not work for you if /usr/share/php5 is in default include path? Do I miss something? > > Sure that's doing some configuration by yourself is fucking critical. > No, read my comment in the original post: it leaves a modified configuration > file. This situation must be avoided, if we want to reduce race between > the "packager" version and "my version". I agree, however this is not a huge problem. > Is it that hard to include a file with this content? No, that's just NOT critical. But I'll add a default configuration. Cheers, -- Julien Danjou .''`. Debian Developer : :' : http://julien.danjou.info `. `' http://people.debian.org/~acid `- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD signature.asc Description: Digital signature
Bug#408769: php5-sqlite3: package is completay unusable out of the box
At 1169997889 time_t, Diego Iastrubni wrote: > Yes, that policy is not enforced by default at the moment. Should I understand that I am in advance with the policy? Because in this case I don't see what I can easily do to fix that point. (chicken/egg... :) Cheers, -- Julien Danjou .''`. Debian Developer : :' : http://julien.danjou.info `. `' http://people.debian.org/~acid `- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD signature.asc Description: Digital signature
Bug#408769: php5-sqlite3: package is completay unusable out of the box
On Sunday 28 January 2007 16:45, Julien Danjou wrote: > At 1169993410 time_t, Diego Iastrubni wrote: > > I am trying to build a package which depends on sqlite3. This breaks my > > package in funny ways. > This still does not justify critical severity. ok. Thanks for the other fix in this bug. > "The default PHP include path is: > > .:/etc/php:/usr/local/share/php/5.0:/usr/share/php5:/usr/share/php/5.0:/usr >/share/php:/usr/local/share/php" > > So why including DB/sqlite3.php does not work for you if /usr/share/php5 > is in default include path? Do I miss something? Yes, that policy is not enforced by default at the moment. If you do not specify any include_path, it's set to ".:/usr/share/php". The directory /usr/share/php5 is not included at all. The default configuration is available at /usr/share/php5/php.ini-dist (look at the post-inst of php-cgi for example). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#408769: php5-sqlite3: package is completay unusable out of the box
On Sunday 28 January 2007 14:51, Julien Danjou wrote: > AHAH. > Are you sure that can't create data loss too? I am trying to build a package which depends on sqlite3. This breaks my package in funny ways. > > The package installs the include file in the path: > > /usr/share/php5/DB/sqlite3.php > > > > This path is not included by default. From what I see in php-db, that > > file belongs in /usr/share/php/DB/sqlite3.php. > > Right. > However I don't know yet how I can grab this files in two packages > without being in conflict with the other one. You are talking about php5-sqlite3 and php4-sqlite3? I am probably not following, but I think in both packages you are installing the same php "include" file, so this can be worked around in some way. If splitting this package is a problem (or just using the same package for PHP4 and PHP5), IMHO the best solution should be to modify the default configuration of php4 and php5 to include /usr/share/php$PHPVERSION/, as dictated by the php policy Draft, section 2.2.2. http://webapps-common.alioth.debian.org/draft-php/html/ch-php-int.html#s-php-interpreter-fs > Sure that's doing some configuration by yourself is fucking critical. No, read my comment in the original post: it leaves a modified configuration file. This situation must be avoided, if we want to reduce race between the "packager" version and "my version". Is it that hard to include a file with this content? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#408769: php5-sqlite3: package is completay unusable out of the box
severity 408769 serious thanks I consider this as serious since the sqlite3.php is not in its right place. At 1169986166 time_t, Diego Iastrubni wrote: > Justification: breaks unrelated software AHAH. Are you sure that can't create data loss too? > The package installs the include file in the path: > /usr/share/php5/DB/sqlite3.php > > This path is not included by default. From what I see in php-db, that > file belongs in /usr/share/php/DB/sqlite3.php. Right. However I don't know yet how I can grab this files in two packages without being in conflict with the other one. > Now, even after I add that path to the include_path (changing default > configuration is bad, as it marks config files as dirty), applications > using sqlite3 (and pear...) still do not work. > > The reason, is that the sqlite3.so module is not loaded by php. From > what I see in php5-sqlite, this file is missing: > /etc/php5/conf.d/sqlite3.ini > > The contents may be something like this: > turing:/etc/php5/apache2/conf.d# cat /etc/php5/conf.d/sqlite3.ini > # configuration for php SQLite3 module > extension=sqlite3.so Sure that's doing some configuration by yourself is fucking critical. Cheers, -- Julien Danjou .''`. Debian Developer : :' : http://julien.danjou.info `. `' http://people.debian.org/~acid `- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD signature.asc Description: Digital signature
Processed: Re: Bug#408769: php5-sqlite3: package is completay unusable out of the box
Processing commands for [EMAIL PROTECTED]: > severity 408769 serious Bug#408769: php5-sqlite3: package is completay unusable out of the box Severity set to `serious' from `critical' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#408769: php5-sqlite3: package is completay unusable out of the box
Package: php5-sqlite3 Version: 0.4-2 Severity: critical Justification: breaks unrelated software The package installs the include file in the path: /usr/share/php5/DB/sqlite3.php This path is not included by default. From what I see in php-db, that file belongs in /usr/share/php/DB/sqlite3.php. Now, even after I add that path to the include_path (changing default configuration is bad, as it marks config files as dirty), applications using sqlite3 (and pear...) still do not work. The reason, is that the sqlite3.so module is not loaded by php. From what I see in php5-sqlite, this file is missing: /etc/php5/conf.d/sqlite3.ini The contents may be something like this: turing:/etc/php5/apache2/conf.d# cat /etc/php5/conf.d/sqlite3.ini # configuration for php SQLite3 module extension=sqlite3.so 2 huge problems on a single package. great :) -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages php5-sqlite3 depends on: ii libapache2-mod-php5 [phpapi- 5.2.0-8 server-side, HTML-embedded scripti ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii libsqlite3-0 3.3.8-1 SQLite 3 shared library ii php5-cli [phpapi-20060613+lf 5.2.0-8 command-line interpreter for the p php5-sqlite3 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
