FTBFS: depends on php4-dev, which has been removed

[Daniel Hahler]

php-interbase build-depends on php4-dev for building php4-interbase.

php4-interbase is obsolete and should get removed.

I think the fix is to provide a debdiff for php-interbase to not build php4-interbase anymore.

Is there any other action required to remove php4-interbase from the archives?

[Daniel Hahler (blueyed)]

Actually, it seems like php5-interbase gets provided by the php5 source package now.

Therefor this bug seems invalid and I'll file a request to remove php-interbase instead.

[Daniel Hahler (blueyed)]

Re-opening, because of comment from Luca in bug 135716.

php-interbase seems to still be needed for Gutsy.

[Daniel Hahler (blueyed)]

debdiff to remove php4-interbase package from php-interbase:
  * Do not build php4-interbase anymore (LP: #135695)
  * debian/control: Removed php4-interbase
  * debian/control: Changed DebianMaintainerField
  * debian/po/POTFILES.in: removed php4-interbase.templates
  * debian/control: removed Build-Depends on php4-dev
  * debian/control: Build-Depend on firebird2.0-dev instead
    of firebird2-dev, because it FTBFS with the latter
  * debian/control: Standards-Version 3.7.2
  * Removed debian/php4-*
  * Executed debconf-updatepo (according to lintian)

I'm especially unsure about using firebird2.0-dev instead of firebird2-dev! (but I could not get it to build using firebird2-dev).

Please note, that this is untested, because I'm not using firebird/interbase.

[Daniel Hahler (blueyed)]

Please note: once this bug is fixed, the remaining php4-interbase package should get removed from the archives.

[Luca Falavigna (dktrkranz)]

Daniel, there are still some unmetdeps troubles: depends on phpapi-20060613+lfs, which is not installable.

[Daniel Hahler (blueyed)]

Luca, I cannot confirm.

phpapi-20060613+lfs gets provided by libapache2-mod-php5, php5-cgi and php5-cli:
$ aptitude search '~Pphpapi-20060613\+lfs' | awk '{print $2}'
libapache2-mod-php5
php5-cgi
php5-cli

[Luca Falavigna (dktrkranz)]

Please, forget about my previous comment. It works correctly for me.

[Daniel Hahler (blueyed)]

Subscribing ubuntu-universe-sponsors again.

[Scott Kitterman (kitterman)]

Patch doesn't apply here:

patching file php-interbase-5.1.2/debian/php4-interbase.preinst
patching file php-interbase-5.1.2/debian/php4-interbase.postinst
patching file php-interbase-5.1.2/debian/rules
patching file php-interbase-5.1.2/debian/php4-interbase.config
patching file php-interbase-5.1.2/debian/changelog
patching file php-interbase-5.1.2/debian/php4-interbase.templates
patching file php-interbase-5.1.2/debian/control
patching file php-interbase-5.1.2/debian/po/ja.po
Hunk #2 FAILED at 25.
Hunk #3 FAILED at 43.
2 out of 4 hunks FAILED -- saving rejects to file php-interbase-5.1.2/debian/po/ja.po.rej
patching file php-interbase-5.1.2/debian/po/sv.po
Hunk #1 FAILED at 16.
1 out of 1 hunk FAILED -- saving rejects to file php-interbase-5.1.2/debian/po/sv.po.rej
patching file php-interbase-5.1.2/debian/po/de.po
patching file php-interbase-5.1.2/debian/po/ru.po
patching file php-interbase-5.1.2/debian/po/tr.po
patching file php-interbase-5.1.2/debian/po/da.po
Hunk #2 FAILED at 27.
1 out of 4 hunks FAILED -- saving rejects to file php-interbase-5.1.2/debian/po/da.po.rej
patching file php-interbase-5.1.2/debian/po/ca.po
patching file php-interbase-5.1.2/debian/po/pt.po
patching file php-interbase-5.1.2/debian/po/templates.pot
patching file php-interbase-5.1.2/debian/po/vi.po
patching file php-interbase-5.1.2/debian/po/POTFILES.in
patching file php-interbase-5.1.2/debian/po/nl.po
patching file php-interbase-5.1.2/debian/po/es.po
Hunk #1 succeeded at 21 with fuzz 2.
Hunk #2 FAILED at 33.
Hunk #3 FAILED at 51.
2 out of 4 hunks FAILED -- saving rejects to file php-interbase-5.1.2/debian/po/es.po.rej
patching file php-interbase-5.1.2/debian/po/fr.po
Hunk #2 FAILED at 23.
Hunk #3 FAILED at 41.
2 out of 4 hunks FAILED -- saving rejects to file php-interbase-5.1.2/debian/po/fr.po.rej
patching file php-interbase-5.1.2/debian/po/pt_BR.po
Hunk #1 succeeded at 14 with fuzz 2.
Hunk #2 FAILED at 25.
1 out of 4 hunks FAILED -- saving rejects to file php-interbase-5.1.2/debian/po/pt_BR.po.rej
patching file php-interbase-5.1.2/debian/po/cs.po
Hunk #2 FAILED at 25.
Hunk #3 FAILED at 42.
2 out of 4 hunks FAILED -- saving rejects to file php-interbase-5.1.2/debian/po/cs.po.rej

Please fix and resubmit.

[Emmet Hikory (persia)]

Patch applies cleanly for me, although I've not looked at the contents.

[Daniel Hahler (blueyed)]

The patch applies cleanly for me. I've also asked on IRC and persia confirmed it, too.
Resubscribing u-u-s.

[Scott Kitterman (kitterman)]

At this point it'll need to be retargeted for hardy and gutsy-proposed.

[Scott Kitterman (kitterman)]

Ack for upload to gutsy-proposed from motu-uvf. Please remember to upload to Hardy when it opens.

[Soren Hansen (soren)]

I would really prefer it if you could redo the patch to include the interbase code from the php5 tarball rather than sticking with the stuff from php 5.1.2.

[Scott Kitterman (kitterman)]

OK. Nack then until Soren's happy.

[Matthew Firth (launchpad-matthew)]

I have also patched it in a similar way to dAniel's above, but have also updated the sources to be those from PHP 5.2.3. Built and tested on Gutsy, and "pbuild" also gives it a clean bill of health.

GIven that it's basically a new release of "upstream" as well as patches to the packaging scripts/controls (to get rid of the 'php4' stuff), I was going to attach the following to this bug:

 * A new ".orig.tar.gz".
 * A complete ".diff.gz" for the package.
 * A new ".dsc".

I was also going to use a version of "5.2.3-0ubuntu1" to reflect that it's not actually a Debian package (following the naming in "php-imap").

Is this the correct way to procede?

[Emmet Hikory (persia)]

I've unsubscribed ubuntu-universe-sponsors pending the presentation of a solution that addresses Soren's comments above. Please resubscribe if sponsorship is required for such a solution.

[Daniel Hahler (blueyed)]

Matthew, yes that would work, as far as I know - however, https://wiki.ubuntu.com/MOTU/Contributing#head-b205c74e27fe15e79e10c9e7f14d3cdfb359d81d says that an interdiff should get used.
Please just step into #ubuntu-motu on IRC, if you have any questions.

As far as I can see you need the version for hardy first and then for gutsy-proposed (see https://wiki.ubuntu.com/SRU).

[Daniel Hahler (blueyed)]

Uploaded an updated version for Hardy yesterday, still waiting in NEW.

[Launchpad Janitor (janitor)]

This bug was fixed in the package php-interbase - 5.2.5-0ubuntu1

---------------
php-interbase (5.2.5-0ubuntu1) hardy; urgency=low

  * New upstream release
  * Do not build php4-interbase anymore (LP: #135695)
  * debian/control:
    - Remove package php4-interbase
    - removed Build-Depends on php4-dev
    - Build-Depend on firebird2.0-dev instead of firebird2-dev,
      because it FTBFS with the latter
    - Standards-Version 3.7.3
    - Add Homepage field
    - DebianMaintainerField
  * debian/po/POTFILES.in: removed php4-interbase.templates
  * Removed debian/php4-*
  * Executed debconf-updatepo (according to lintian)

 -- Daniel Hahler <email address hidden> Thu, 14 Feb 2008 01:11:10 +0100

[Popa Adrian Marius (mapopa)]

thank you for the new php-interbase package , now i have installed on my hardy , I will test it to see if is ok
(with ibwebadmin)

[Popa Adrian Marius (mapopa)]

debdiff for gutsy-proposed should be added to the php5-interbase package and the bug fixed by the motu

[Popa Adrian Marius (mapopa)]

latest debdiff for gutsy-proposed should be added to the php5-interbase package and the bug fixed by the Ubuntu Sponsors for universe

[Daniel Hahler (blueyed)]

Setting back to "Fix Released".
Mariuz: For Gutsy, a StableReleaseUpdate (http://wiki.ubuntu.com/SRU) would be required, which does not really fit here.
Either wait for Hardy or build the package from source.

[Popa Adrian Marius (mapopa)]

i have build-ed with your patch and worked https://launchpad.net/~mapopa/+archive/+build/540982

, the problem is that new users will get the php-api error
so i will try to use the Stable Release Update guide
and an new bug will be submitted i guess