Bug#538067: status of the OpenCPN package?
On Thu, Aug 14, 2014 at 06:44:55PM +1200, Hamish wrote: > Andreas wrote: > > So you are free to commit there (or even move this to Git > > As long as I am the acting lead/co-author and maintainer of the I understood your "no time" flag as rather non-acting. > packaging effort I would dearly prefer to keep it in svn, Fine for me, sorry if I suggested something you did not liked. > and moreover > have people coordinate with Anton and myself before applying their own > patches, thankyouverymuch. What about "our" (in terms of a team) patches? I wonder why you come up with the idea of applying "own" patches. I have addressed some issues[1] in the packaging which are not addressed since >1 year as far as I can see and without testing the package should generate several lintian warnings. This is plain Debian packaging stuff and IMHO it would be rather sensible if people who are admitting to have no time would give people free hands to work on such open issues. If something might happen against your intention (you have proven an impressively quick response time with your current answer) it is quite simple to revert. > The most important part of working together in a team is communication and > mutual respect, not "the last person to commit wins". I understand working in a team that anybody can bring things forward. I consider it bad leading if you stop people from working in advance instead of inspecting their commits and tweak (rewert?) if needed. Your lose / win terminology implies a conflict / fight which I fail to see and my experience has shown that it brings things forward if you encourage people to do something. Kind regards Andreas. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538067#159 -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#538067: status of the OpenCPN package?
Andreas wrote: > So you are free to commit there (or even move this to Git As long as I am the acting lead/co-author and maintainer of the packaging effort I would dearly prefer to keep it in svn, and moreover have people coordinate with Anton and myself before applying their own patches, thankyouverymuch. The most important part of working together in a team is communication and mutual respect, not "the last person to commit wins". The OSGeo Live DVD ships in the very near future, if anyone wants to help free my time to work on other things, helping to test that would be greatly appreciated. http://aiolos.survey.ntua.gr/gisvm/dev/ patches welcome, Hamish -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#538067: status of the OpenCPN package?
Hi, On Wed, Aug 13, 2014 at 07:21:08PM -0400, Antoine Beaupré wrote: > ... > of course. keep in mind that the jessie freeze is only a few months > ahead (3, i think?) so if you want OpenCPN to be "in debian" in the next > few years, we should get this show on the road! The packaging attempt is a group effort and available in http://svn.debian.org/viewsvn/pkg-grass/packages/opencpn/trunk/ So you are free to commit there (or even move this to Git which is as far as I know a migration path Debian GIS has agreed upon). The offer for sponsering the package from my side stays valid for any team member. Some hintes what I consider worth changing to the packaging are in the log of the bug report. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#538067: status of the OpenCPN package?
On 2014-06-24 06:22:53, Hamish wrote: > Antoine Beaupré wrote: > >>> I am writing to you because you have participated in the review of the >>> new OpenCPN debian package as part of bug #538067. >>> >>> I would be ready to sponsor the package if people are okay with its >>> current state. It would be a shame to have the package stalled in that >>> bug report forever like this. :) >>> >>> Note that upstream is now at version 3.2.2 as well, so there may be some >>> work required to get it up to the latest release. Yet i believe that >>> uploading 2.5 would be better than nothing. >>> >>> What's blocking this? do you need an uploader? > > Francesco: >> I think Hamish_B who worked in the past on this is currently busy, as >> happens frequently with Real Life. I'm not sure if anyone is able >> to work on that starting from current status. > > Hi, > > indeed I am super busy with other responsibilites right now, but I haven't > given up on this package! There is very little blocking it now, I don't > even remeber what if anything, need to check the last post to the ITP and > the ftp-master's previous rejection comment. :) AFAIR it wasn't anything > major. Alright, I fully understand that. Sharing those comments here would be quite useful if someone else wants to pursue your work in case you become too busy in the future. :) > I was hesitating to update the packaging in debiangis svn for two reasons, > one was that the 2.5.0 package was 99% ready to go, and a 3.2.2 would > require resetting the QA-clock to zero. So my plan there was to get 2.5.0 > into sid immediately then work on 3.2.2 after. The second reason was that > opencpn 3 replaced the graphics canvas with OpenGL, and for Debian/Ubuntu > combined with a Intel GPU it caused a rendering bug for many people. (one > of the main use cases for opencpn is on laptops where intel GPUs are very > common). It's been a while since I checked on the status of the bug, but > I'm thinking that it is still present in 3.2.2? (don't quote me on that :) This seems perfectly reasonable - 3.2.2 can be uploaded to experimental once 2.5 passes NEW. > Also since for me at least 2.5.0 is basically feature-complete and a very > rock-solid release, I wasn't in a rush for the new nice extra features > like improved AIS and radar overlay. Nice, but not critical to the primary > purpose of the program. Indeed. > Probably todo is to check if the build is still ok with the latest sid, > since perhaps some package names could need updating in the control file. > But otherwise I am quite confident in the state of the current packaging > and very supportive of one final review before upload. A huge amount of > work went into it, so it would be a real shame to throw it out and start > again, even if a lot of our review is now merged upstream! of course. keep in mind that the jessie freeze is only a few months ahead (3, i think?) so if you want OpenCPN to be "in debian" in the next few years, we should get this show on the road! thanks for working on this. a. -- Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir - Lofofora pgpx7d3t4DK_i.pgp Description: PGP signature
Bug#538067: status of the OpenCPN package?
Antoine Beaupré wrote: >> I am writing to you because you have participated in the review of the >> new OpenCPN debian package as part of bug #538067. >> >> I would be ready to sponsor the package if people are okay with its >> current state. It would be a shame to have the package stalled in that >> bug report forever like this. :) >> >> Note that upstream is now at version 3.2.2 as well, so there may be some >> work required to get it up to the latest release. Yet i believe that >> uploading 2.5 would be better than nothing. >> >> What's blocking this? do you need an uploader? Francesco: > I think Hamish_B who worked in the past on this is currently busy, as > happens frequently with Real Life. I'm not sure if anyone is able > to work on that starting from current status. Hi, indeed I am super busy with other responsibilites right now, but I haven't given up on this package! There is very little blocking it now, I don't even remeber what if anything, need to check the last post to the ITP and the ftp-master's previous rejection comment. :) AFAIR it wasn't anything major. I was hesitating to update the packaging in debiangis svn for two reasons, one was that the 2.5.0 package was 99% ready to go, and a 3.2.2 would require resetting the QA-clock to zero. So my plan there was to get 2.5.0 into sid immediately then work on 3.2.2 after. The second reason was that opencpn 3 replaced the graphics canvas with OpenGL, and for Debian/Ubuntu combined with a Intel GPU it caused a rendering bug for many people. (one of the main use cases for opencpn is on laptops where intel GPUs are very common). It's been a while since I checked on the status of the bug, but I'm thinking that it is still present in 3.2.2? (don't quote me on that :) Also since for me at least 2.5.0 is basically feature-complete and a very rock-solid release, I wasn't in a rush for the new nice extra features like improved AIS and radar overlay. Nice, but not critical to the primary purpose of the program. Probably todo is to check if the build is still ok with the latest sid, since perhaps some package names could need updating in the control file. But otherwise I am quite confident in the state of the current packaging and very supportive of one final review before upload. A huge amount of work went into it, so it would be a real shame to throw it out and start again, even if a lot of our review is now merged upstream! thanks for your interest, Hamish ps- MB-System is also very close to being ready for final review, the final 3rd party murky license trouble is now happily resolved with LGPL since a couple weeks ago. (packaging code for this also in alioth debiangis svn) pps- updated gpsdrive too! although I've been maintaining that in the upstream debian/ dir and need to merge that with alioth, and make one final mapnik2 api change commit before I tag a new release. RC version can be tested with ubu 14.04 at dev side of http://live.osgeo.org. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#538067: status of the OpenCPN package?
On Sun, Jun 01, 2014 at 09:05:36PM -0400, Antoine Beaupré wrote: > Hi, > > I am writing to you because you have participated in the review of the > new OpenCPN debian package as part of bug #538067. > > I would be ready to sponsor the package if people are okay with its > current state. It would be a shame to have the package stalled in that > bug report forever like this. :) > > Note that upstream is now at version 3.2.2 as well, so there may be some > work required to get it up to the latest release. Yet i believe that > uploading 2.5 would be better than nothing. > > What's blocking this? do you need an uploader? > > A. > I think Hamish_B who worked in the past on this is currently busy, as happens frequently with Real Life. I'm not sure if anyone is able to work on that starting from current status. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#538067: status of the OpenCPN package?
Hi, I am writing to you because you have participated in the review of the new OpenCPN debian package as part of bug #538067. I would be ready to sponsor the package if people are okay with its current state. It would be a shame to have the package stalled in that bug report forever like this. :) Note that upstream is now at version 3.2.2 as well, so there may be some work required to get it up to the latest release. Yet i believe that uploading 2.5 would be better than nothing. What's blocking this? do you need an uploader? A. -- Il faut tout un village pour élever un enfant. - Proverbe africain pgpCg5R7fU_3e.pgp Description: PGP signature
