Hi, 2011/10/12 Christian PERRIER <bubu...@debian.org>: > Answering in the list rather than BTS as this is more a discussion > than something related to that bug
I agree. > Quoting pytrainer (nore...@sourceforge.net): >> #148: Should not hardcode 1.3.5 version of GPSBabel in the import plugin >> -----------------------+---------------------------------------------------- >> Reporter: cperrier | Owner: >> Type: defect | Status: closed >> Priority: major | Milestone: Not scheduled >> Component: Core | Version: 1.8.0 >> Resolution: invalid | Keywords: >> -----------------------+---------------------------------------------------- >> Changes (by dgranda): >> >> * status: new => closed >> * resolution: => invalid >> >> >> Comment: >> >> Thanks Cristian for the follow up. >> >> Anyway this is not a bug (it works as expected) since gpsbabel changed >> some stuff from version 1.3.6 on, so pytrainer currently _only_ works with >> gpsbabel 1.3.5. Please see following messages for more information: >> >> http://sourceforge.net/mailarchive/message.php?msg_id=20818837 >> >> http://sourceforge.net/mailarchive/message.php?msg_id=23661969 >> >> I could see it as a request to support newer versions of gpsbabel (aka >> enhancement), but definitely not a defect. > > Ack. The original problem was indeed that Ubuntu/Debian packages were > depending on "gpsbabel (>=1.3.5)" > > Actually, I think they should more use "Suggests" and use a versioned > Suggests: > > Suggests: gpsbabel (<< 1.3.6) > > After all, the software still works if one doesn't have gpsbabel > installed, so the dependency was too hard. Yes, definitely 'suggestion' fits better here. It looks like a misunderstanding, hopefully now is clear for everyone. >> I close it as invalid. >> >> PS: I don't understand why we don't get notified (email to distribution >> list?) earlier when this information is published. Shouldn't they involve >> us somehow to provide quicker feedback? > > There is currently no way to automatically link upstream BTS (or > mailing lists) to distributions bugtrackers. It seems reasonable as too much automation between completely different applications and environments sounds infeasible, but I am confident there is a manual way to do it... > Here, the bug was reported in Ubuntu. A fix was proposed (the patch I > sent). As Debian maintainer, I receive Ubuntu bug reports for packages > I'm in charge of (this is an opt-in system between both bug > trackers). So, seeing that bug report, I fixed it in Debian (and thus > the change flows back to Ubuntu and they can drop the specific fix > they had there). And, then, as the Debian maintainer, one of my > "duties" is to notify upstream (aka you) about the "bug". Which I did. I really appreciate it, thanks very much. > I don't really see how this can be fully automated. Still, anyone can > subscribe to Debian bug reports for any packages (s)he wants. So you > actually can subscribe to bugs reporeted against pytrainer in > Debian. Even this list can be subscribed (there's a confirmation > system that can make it a little bit clumsy but that can be done). Subscribing sounds good. I will have a look on both bug reporting systems (Debian and Ubuntu) to see how can current list be subscribed to notifications regarding pytrainer package. If anyone has any idea on this topic, please shout! ;) David ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
