Please sync with Debian

[Raphaël Hertzog]

While trying to package something that requires zend framework and wanting this package to work both for Debian and Ubuntu I noticed that Debian has "zendframework" and Ubuntu has "zend-framework".

This divergence probably happened because Frank Habermann was not aware of the Ubuntu package when he created the package for Debian.

That said this is not a good reason to keep divergent and conflicting packages in Debian and Ubuntu. I hereby ask you to consider merging your efforts on the Debian side. I'm going to subscribe Frank Habermann to this bug.

[Stephan Rügamer (sruegamer)]

I would like to see that,
but as long the Debian package doesn't ship the ZendX library addons,
this won't happen.
People already depending on this.

You can, of course, depend on zendframework|zend-framework to make it work.

More Informations about this:

Sadly, when I was packaging zend-framework in the past, there was no work done inside Debian, but it was widely spread that Ubuntu has Zend Framework in the Repos (ref: http://andigutmans.blogspot.de/2008/02/zend-framework-to-be-part-of-ubuntu.html)

When I first encountered the debian package I requested a blacklisting for syncing this package from Debian.
1. the naming of the Debian package was wrong, libphp-zend-framework is more the usual naming convention.
2. Missing features.

Furthermore, nobody was getting in touch with Ubuntu Universe Developers or directly with me, to make this happen in the past. SInce 2008 the package is available, while work on the Debian side was starting only in 2009.

Frank can update his package easily and take over responsibility...I'm am not bound to it.
Some conflicts and replaces headers in debian/control can help here.

The general issue itself, can be easily resolved with zend framework 2.0 for debian and the next Ubuntu release in 13.04

Regards,

\sh

[Raphaël Hertzog (hertzog)]

For reference this is the bug that required the Debian package to be blacklisted: https://bugs.launchpad.net/ubuntu/+source/zendframework/+bug/580507

I would hope that Stephan could instead contribute the "goodies" to the Debian package so that everybody benefits from it. I'm not sure if this is still relevant nowadays though.

[Raphaël Hertzog (hertzog)]

Hi Stefan, thank you for your quick answer.

I'm not familiar with all this, but why were those "ZendX addons" not packaged separately if they are addons and not provided in the main zendframework tarball?

Also why are you suggesting to wait for zend framework 2.0 to resolve this issue? Is there anything special in that version? Does it integrate or obsolete the above addons?

[Raphaël Hertzog (hertzog)]

I'm taking the liberty to move the status to triaged because opinion is a sort of soft wontfix.

Would you be willing to maintain a Debian package for those addons so that Ubuntu can then use the official Debian packages with just an added dependency to ease the transition? I'll open a separate bug on the Debian side to get the naming fixed and to track this on the Debian side too.

[lordlamer (lordlamer)]

Hi,

> I'm not familiar with all this, but why were those "ZendX addons" not
> packaged separately if they are addons and not provided in the main
> zendframework tarball?
I would add ZendX after debian wheezy is released. I could create also
an package for experimental first.

> Also why are you suggesting to wait for zend framework 2.0 to resolve
> this issue? Is there anything special in that version? Does it integrate
> or obsolete the above addons?
ZendFramework 2 should be a seperate package.

regards,
Frank

[lordlamer (lordlamer)]

Hi,

> Would you be willing to maintain a Debian package for those addons so
> that Ubuntu can then use the official Debian packages with just an added
> dependency to ease the transition? I'll open a separate bug on the
> Debian side to get the naming fixed and to track this on the Debian side
> too.
The upstream package is called "zendframework" not "zend-framework".

regards,
Frank

[Raphaël Hertzog (hertzog)]

> 1. the naming of the Debian package was wrong, libphp-zend-framework is more the usual naming convention.

Note that you have libzend-framework-php in Ubuntu and not libphp-zend-framework. Also upstream does not put a dash between zend and framework, although they use upper case letters to distinguish both words...

[Stephan Rügamer (sruegamer)]

Raphael:

Question 1:
ZendX is distributed inside the source package from upstream.
Those 'addons' are experimental or not ready for production. but people already using them to be up2date with all upcoming features.

Question 2:

I had the idea to package zend framework 2 as separate package, with a different name (libphp-zend-framework-2 or something like this) for ubuntu. But this would lead to the same mess as we have now.
So, for the version 2.x we should merge our efforts (as said, I am happy to leave it to the Frank, because my time doing a lot of distro work is counted, because of more real life work stuff).

Anyways what I don't know if ZF 2.x will replace ZF1.x completly or if ZF1.x will stay for a longer time to ease migrations of other reverse-depending packages.

@Frank:
Regarding the version 1 package, when Frank can adjust the package for 13.04 in debian, we can remove the blacklist entry and sync it from debian directly and getting rid of the ubuntu package.

@All:
TL;DR: I would leave it to Frank as Maintainer in Debian to decide.

Regards,

\sh

[Quinn Balazs (qbalazs)]

Is there a current framework to change depends/recommends from zendframework to zend-framework, or is this up to individual package maintainers?

[Daniel James (daniel-64studio)]

Hi, in my opinion this bug should not have been marked as 'Fix Released'. The Ubuntu package of zend has fallen three years behind Debian's version and has not had a bugfix upload in more than a year.

The version in Ubuntu vivid is 1.11.11 which was released by upstream in September 2011.

Debian jessie and sid have 1.12.9 which was released by upstream in September 2014.

Debian experimental has 1.12.11 which was released by upstream in February 2015.

The case in https://bugs.launchpad.net/ubuntu/+source/zendframework/+bug/580507 for a separate package may have been valid in 2010 but is not so apparent now.

I would suggest that Ubuntu follows the Debian package, and if any users depend on experimental features not included in the Debian package, file a bug. If an addon feature hasn't been merged into the main zend release after three years, it is unlikely to be supported upstream.

[Nish Aravamudan (nacc)]

Note that I'm working on solving things along the lines of c#10 in LP: #1593024.

[Quinn Balazs (qbalazs)]

I'd agree that this shouldn't be marked "Fix Released" upstream when no merge happened and we're lagging years behind the versions supported in Debian.

[Quinn Balazs (qbalazs)]

Invalidating without explanation is frowned upon, I've linked this bug to #1593024 as a duplicate as both tackle syncing zend-framework from Debian.