Osmium Git moved from pkg-osm to pkg-grass - how to proceed now (Was: Moving JOSM from pkg-osm git to pkg-grass git)
Hi, On Tue, Dec 17, 2013 at 03:39:06PM +0100, Francesco P. Lovergine wrote: That should also be intended for osmium, whose only uploader is David Paleino currently. It is also included in the list of the b-rdeps for GDAL, so it needs immediate care due to current lack of feedback by David. I moved the repository do pkg-grass and make Debian GIS maintainer of the package. I also updated the packaging to recently suggested policy. So the packaging is now at git://anonscm.debian.org/pkg-grass/osmium.git while I dropped some README.status inside the old repository. Since I have no idea about gdal somebody needs to check everything (probably also for updates by upstream - from my point of view it would really help to convince upstream to use release tags and drop the debian/ dir. Please let me know in how far I could be helpful to finalise the migration. Sponsoring is no problem at all as I have shown in the past. Kind regards Andreas. -- http://fam-tille.de ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Re: Osmium Git moved from pkg-osm to pkg-grass - how to proceed now (Was: Moving JOSM from pkg-osm git to pkg-grass git)
Hi Francesco. On Tue, Dec 17, 2013 at 08:23:49PM +0100, Francesco P. Lovergine wrote: Eh, this is a problem often present also in other software, but it depends definitively on upstream dev team ideas. Grass developers had no time/interest in supporting packaging and indeed have dropped the debian/ dir for years. The same did not happen in the qgis world, because their release cycle is too fast for Debian. I found practical cloning and merging via git their tree adding minimal changes when required: something a bit more complicated than the usual upstream+debian git branch, but it works. Well, if you think it is not worth contacting them that's perfectly fine for me. I did some further changes to the packaging including closing #732389 which was probably your request regarding gdal. If somebody would update to latest upstream to close #700614 I thinks the package is ready for uploading. I personally would hesitate to do this Git magic since it would be the first time for me to use this workflow without upstream tarball. BTW, the most important argument I have against this method is that we are not able to write a proper watch file. So if somebody volunteers to upgrade to latest upstream and upload or ask me for sponsering this task should be done. Kind regards Andreas. -- http://fam-tille.de ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Re: Osmium Git moved from pkg-osm to pkg-grass - how to proceed now (Was: Moving JOSM from pkg-osm git to pkg-grass git)
On Tue, Dec 17, 2013 at 06:25:04PM +0100, Andreas Tille wrote: while I dropped some README.status inside the old repository. Since I have no idea about gdal somebody needs to check everything (probably also for updates by upstream - from my point of view it would really help to convince upstream to use release tags and drop the debian/ dir. Eh, this is a problem often present also in other software, but it depends definitively on upstream dev team ideas. Grass developers had no time/interest in supporting packaging and indeed have dropped the debian/ dir for years. The same did not happen in the qgis world, because their release cycle is too fast for Debian. I found practical cloning and merging via git their tree adding minimal changes when required: something a bit more complicated than the usual upstream+debian git branch, but it works. -- Francesco P. Lovergine ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
