Bug#692353: ITP: php-wpcli -- PHP PEAR module for a WordPress CLI interface
What is the current status of this? I'm more then happy to help to finally make this happen. Best, Marko Heijnen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692353: ITP: php-wpcli -- PHP PEAR module for a WordPress CLI interface
Package: wnpp Severity: wishlist Owner: andrea rota a...@xelera.eu * Package name: php-wpcli Version : 0.6.0 Upstream Author : scribu m...@scribu.net, Andreas Creten andr...@madewithlove.be * URL : http://wp-cli.org/ * License : MIT Programming Lang: PHP Description : PHP PEAR module for a WordPress CLI interface wp-cli is a set of command-line tools for managing WordPress installations. You can update plugins, set up multisite installs, manage users, interact with the database, manage themes, create posts and much more. It can be extented through plugins to let administrators manage even more aspects of a WordPress installation. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692353: ITP: php-wpcli -- PHP PEAR module for a WordPress CLI interface
On 11/05/2012 06:28 PM, andrea rota wrote: Package: wnpp Severity: wishlist Owner: andrea rota a...@xelera.eu * Package name: php-wpcli Version : 0.6.0 Upstream Author : scribu m...@scribu.net, Andreas Creten andr...@madewithlove.be * URL : http://wp-cli.org/ * License : MIT Programming Lang: PHP Description : PHP PEAR module for a WordPress CLI interface wp-cli is a set of command-line tools for managing WordPress installations. You can update plugins, set up multisite installs, manage users, interact with the database, manage themes, create posts and much more. It can be extented through plugins to let administrators manage even more aspects of a WordPress installation. Hi, It'd be great if you could have this package made using pkg-php-tools, and make sure you work together with the PKG PHP PEAR team (and have the package team maintained). If you never tried it, please try debpear, which will create a working package quickly! I'd be happy to review / sponsor such package if you need. Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692353: ITP: php-wpcli -- PHP PEAR module for a WordPress CLI interface
hi Thomas, On Mon, Nov 05, 2012 at 09:33:44PM +0800, Thomas Goirand wrote: [...] It'd be great if you could have this package made using pkg-php-tools, and make sure you work together with the PKG PHP PEAR team (and have the package team maintained). If you never tried it, please try debpear, which will create a working package quickly! I'd be happy to review / sponsor such package if you need. thanks - i have prepared an initial package which works ok on a couple of production nodes: what would be the best way to make the code available for review? the upstream git repo (https://github.com/wp-cli/wp-cli) is not in the layout used by debpear once it extracts the pear package tgz (this is not in the pear.php.net channel so i fed the tarball downloaded via pear download wp-cli.github.com/pear/wpcl to debpear for the initial debian/ folder setup) so i can't simply fork it and add the work-in-progress debian/ folder to my fork - shall i just create a git repo with the full tree - unpacked upstream tgz and debian folder - i have on my working dir now? thank you, andrea -- andrea rota Xelera - IT infrastructures http://xelera.eu/contact-us/ signature.asc Description: Digital signature
Bug#692353: ITP: php-wpcli -- PHP PEAR module for a WordPress CLI interface
On 11/06/2012 12:28 AM, andrea rota wrote: thanks - i have prepared an initial package which works ok on a couple of production nodes: what would be the best way to make the code available for review? Upload the package somewhere (it doesn't have to be mentors.debian.net, as long as download is fast enough), and give the link to the .dsc file (that file is the result of a dpkg-buildpackage, and it links to the .orig.tar.gz and debian.tar.gz files, which will be downloaded automatically by dget). the upstream git repo (https://github.com/wp-cli/wp-cli) is not in the layout used by debpear once it extracts the pear package tgz (this is not in the pear.php.net channel so i fed the tarball downloaded via pear download wp-cli.github.com/pear/wpcl to debpear for the initial debian/ folder setup) so i can't simply fork it and add the work-in-progress debian/ folder to my fork - shall i just create a git repo with the full tree - unpacked upstream tgz and debian folder - i have on my working dir now? I would advise you to read this: http://pkg-php.alioth.debian.org/ and do what is advised there. I wrote that page, feel free to be critic about it, and ask me to rewrite parts of it if you don't understand some of it. Extracting the upstream tar.gz in the upstream-sid branch is what I would do, another way is to do like here (I'm also in the Openstack packaging team in Debian), which is a very good workflow as well: http://openstack.alioth.debian.org/ what's cool is that it uses upstream git tags. I hope that helps, Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692353: ITP: php-wpcli -- PHP PEAR module for a WordPress CLI interface
hi Thomas, On Tue, Nov 06, 2012 at 03:24:17AM +0800, Thomas Goirand wrote: On 11/06/2012 12:28 AM, andrea rota wrote: thanks - i have prepared an initial package which works ok on a couple of production nodes: what would be the best way to make the code available for review? Upload the package somewhere (it doesn't have to be mentors.debian.net, as long as download is fast enough), and give the link to the .dsc file (that file is the result of a dpkg-buildpackage, and it links to the .orig.tar.gz and debian.tar.gz files, which will be downloaded automatically by dget). ok - my first attempt is now on mentors.debian.net (http://mentors.debian.net/package/php-wpcli) and i can already see some obvious issues that had escaped my attention when looking at lintian's output in the terminal - including the fact that it seems that a git submodule of the upstream repo (src/php/php-cli-tools) should probably be packaged separately :S the upstream git repo (https://github.com/wp-cli/wp-cli) is not in the layout used by debpear once it extracts the pear package tgz (this is not in the pear.php.net channel so i fed the tarball downloaded via pear download wp-cli.github.com/pear/wpcl to debpear for the initial debian/ folder setup) so i can't simply fork it and add the work-in-progress debian/ folder to my fork - shall i just create a git repo with the full tree - unpacked upstream tgz and debian folder - i have on my working dir now? I would advise you to read this: http://pkg-php.alioth.debian.org/ and do what is advised there. I wrote that page, feel free to be critic about it, and ask me to rewrite parts of it if you don't understand some of it. Extracting the upstream tar.gz in the upstream-sid branch is what I would do, another way is to do like here (I'm also in the Openstack packaging team in Debian), which is a very good workflow as well: http://openstack.alioth.debian.org/ what's cool is that it uses upstream git tags. ok, that's great. i love git awesomeness. my first packaging attempt did not use any of this - i'll give it another go tomorrow. thanks again for your help! best andrea -- andrea rota Xelera - IT infrastructures http://xelera.eu/contact-us/ signature.asc Description: Digital signature
Bug#692353: ITP: php-wpcli -- PHP PEAR module for a WordPress CLI interface
On 11/06/2012 05:54 AM, andrea rota wrote: hi Thomas, On Tue, Nov 06, 2012 at 03:24:17AM +0800, Thomas Goirand wrote: On 11/06/2012 12:28 AM, andrea rota wrote: thanks - i have prepared an initial package which works ok on a couple of production nodes: what would be the best way to make the code available for review? Upload the package somewhere (it doesn't have to be mentors.debian.net, as long as download is fast enough), and give the link to the .dsc file (that file is the result of a dpkg-buildpackage, and it links to the .orig.tar.gz and debian.tar.gz files, which will be downloaded automatically by dget). ok - my first attempt is now on mentors.debian.net (http://mentors.debian.net/package/php-wpcli) and i can already see some obvious issues that had escaped my attention when looking at lintian's output in the terminal - including the fact that it seems that a git submodule of the upstream repo (src/php/php-cli-tools) should probably be packaged separately :S It doesn't build on my SID box: dh binary --buildsystem=phppear --with phppear dh_testroot -O--buildsystem=phppear dh_prep -O--buildsystem=phppear dh_installdirs -O--buildsystem=phppear dh_auto_install -O--buildsystem=phppear Unknown channel wp-cli.github.com/pear Parsing of package.xml from file ./wpcli-0.6.0/package.xml failed Cannot download non-local package ./wpcli-0.6.0/package.xml install failed dh_auto_install: /usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin -d php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d doc_dir=/usr/share/doc/php-wpcli -d test_dir=/usr/share/php/tests install --offline --nodeps -P /home/zigo/sources/pkg-php-pear/php-wpcli/php-wpcli-0.6.0/debian/php-wpcli ./wpcli-0.6.0/package.xml returned exit code 1 make: *** [binary] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 As for the Git packaging, if you haven't done so, please join the PKG-PHP group on alioth.debian.org, and I'll add you the PKG PEAR maintainer rights once you're in. Then please upload the git repo on Alioth. Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
