On Fri, Sep 20, 2013 at 10:19 AM, Paul Tagliamonte <paul...@debian.org> wrote: > On Fri, Sep 20, 2013 at 10:18:18AM -0400, Dave Steele wrote: >> I'm not sure we are clear with terms here. The newbie is the upstream, >> and he has chosen to include the debian directory in his main >> repository. Should he choose to rev the packaging, upstream is >> coordinated, by definition. > > As such, a trivial debian package change would trigger a new upstream > release. If this is the intent, that's fineish in my view, but remember, > this screws up and chance of cross-distro work (since a change to RPM > local stuff, as example, would trigger a new upstream, and a no change > rebuild in Debian to match) > > I really discourage this usage a lot. Native packages must be for > packages local to Debian only. >
This raises an interesting question on this package. He is using github tags to identify releases. Currently, the tags page is providing native-friendly tars for each version. So how does he tag packaging-only updates - by tagging at the debian rev level, then adjusting watch to ignore the dash? I don't see how this provides less screwage to other distributions. In any case, it sounds like the guidance on this ticket is that either solution is fineish. -- "Le mieux est l'ennemi du bien" - Voltaire -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
