[pkg-php-pear] composer and debian

Mathieu Parent math.parent at gmail.com
Thu Jun 27 10:12:47 UTC 2013

2013/6/26 andrea rota <a at xelera.eu>:
> gitweb is complaining about missing tree
> (http://anonscm.debian.org/gitweb/?p=pkg-php/php-symfony-process.git;a=tree):
> do i need to create a master branch, or do i set the default tree
> somewhere else?

echo 'ref: refs/heads/debian-sid' > /git/pkg-php/php-symfony-process.git/HEAD

> the other lintian warning i see now is wrong-name-for-upstream-changelog
> (usr/share/doc/php-symfony-process/CHANGELOG.md): i understand the issue
> but i'm not sure how to best deal with this without having to rename the
> file to changelog every time i pull a new release tag from upstream: as
> far as i understand, debian/<package>.docs does not support 'renaming'
> files - is the only manageable option renaming the upstream CHANGELOG.md
> file? i imagine that creating a symlink to it in the debian-sid branch
> won't work (i.e. dh_installdocs will copy a (broken) symlink to
> /usr/share/doc/<package>)?

use dh_installchangelogs instead (with an override).

> that's correct, however i think there is some confusion upstream: they
> use symfony/<component> on github and this is what is used as component
> name in composer, whereas the current PEAR channel for Symfony2
> (http://pear.symfony.com/) uses symfony2/<component> for the PEAR modules.

THe pear repo is outdated. Just ignore it.

> not an issue per se, but i wonder if this might generate confusion in
> Debian if packages end up being named according to the naming scheme of
> the upstream source (composer or PEAR).

Yes. PEAR and Composer naming is full of heuristics, so we'll see (if
there is something not correctly translated, fill a but to

> Were it not for the fact that there are a couple of older symfony
> v1-related packages in the Debian archives, i would think that perhaps
> agreeing on either of the naming schemes for the Debian package names,
> using the other one in a Provides: field could help, but i haven't got a
> deep understanding of the Provides: field scenarios :)

Ask pkg-php-tools:
$ /usr/share/pkg-php-tools/scripts/phppkginfo debian_pkgname
pear.symfony.com Symfony_Yaml

You can also add provides, but provides are not versionned
(http://bugs.debian.org/7330). You can also add a meta package.
> anyways, i'm going to proceed with the other four dependencies for
> composer and then to composer itself - any feedback is very welcome,
> including on any issues with my git workflow/branches etc. (i have tried
> to follow http://wiki.debian.org/PHP/GitUsage but i may have missed
> something).

Your worklow is good.


More information about the pkg-php-pear mailing list