git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [StGit] Debian packaging update

From
Yann Dirson <ydirson@altern.org>
Date
Aug 28, 2008, 19:24 UTC
Message-ID
<20080828192450.GH4985@nan92-1-81-57-214-146.fbx.proxad.net>
In-Reply-To
<20080828140929.GB3584@khazad-dum.debian.net>
On Thu, Aug 28, 2008 at 11:09:29AM -0300, Henrique de Moraes Holschuh wrote:
Show 23 quoted lines
> (Debian maintainer(s) for stgit added to CC through the generic package
> redirect address).
> 
> On Fri, 22 Aug 2008, Catalin Marinas wrote:
> > 2008/8/22 Daniel White <daniel@whitehouse.id.au>:
> > > Since it is now packaged by Debian is it still necessary to be
> > > maintaining Debian packaging?
> > 
> > This is mainly to make it easier for Debian maintainers. Someone might
> > also want to build a .deb package for a different version or flavour
> > of Debian.
> 
> Well, I happen to be a heavy STGIT user, and also a senior Debian
> developer (I have been a DD for over 10 years), so I am entitled to
> reply to this thread I suppose :-)
> 
> Whatever people told you guys, the sad truth is that for the
> overwhelming majority of packages, the mere presence of a debian/ dir
> upstream is taken as a warning sign by any seasoned Debian developer
> (i.e. it is so often a problem, we take it as a bad sign).  It almost
> never helps.  I have no idea where stgit is in that regard, though.  And
> I have NOT checked the "upstream version of the Debian packaging", so
> please don't take this personally.

In this case, they are mostly in sync, except that lately I have not been very active on the stgit front (and on the debian front as well BTW), so that I did not take the time to formalize a set of patches for integration of the latest changes into stgit.

And most of the problem then boils down to the current package diffs not being handled as a series of patches, which is quite a shame for stgit :). Indeed I had started trying to change that at the very beginning of my involvment in the package, but finally decided I had no time for that - and I'm also quite frustrated by the various ways I have tried to maintain debian packages as patch series, unfortunately (eg. see my experiment in debian/README.maint in the tau package). I still have to come with a decent way of doing that.

> Of course, this changes a lot when upstream is also a Debian developer
> and spends a few hours per week keeping up-to-date with Debian policy
> and toolset changes, etc.
Hey, that's not far of what used to happen :)

Another benefit to having uptodate packaging upstream would be to have deb snapshots regularly generated, alhough we don't take advantage of this for the moment.

> I think you guys should CC the Debian developer on any threads about the
> debian/ dir.

I'm on the ml too, but CC'ing never hurts, especially since other people can subscribe to the address via the Package Tracking System.

Previous: Yann DirsonNext: Yann Dirson
Message 13 of 18 in “[StGit] Debian packaging update”
  1. Daniel WhiteAug 18, 2008
  2. Catalin MarinasAug 21, 2008
  3. Daniel WhiteAug 22, 2008
  4. Daniel WhiteAug 22, 2008
  5. Catalin MarinasAug 22, 2008
  6. Catalin MarinasAug 22, 2008
  7. Daniel WhiteAug 23, 2008
  8. Sebastian HarlAug 28, 2008
  9. Henrique de Moraes HolschuhAug 28, 2008
  10. Karl HasselströmAug 28, 2008
  11. Henrique de Moraes HolschuhAug 28, 2008
  12. Yann DirsonAug 28, 2008
  13. Yann DirsonAug 28, 2008
  14. Yann DirsonAug 28, 2008
  15. Karl HasselströmAug 28, 2008
  16. Catalin MarinasAug 30, 2008
  17. Karl HasselströmAug 31, 2008
  18. Catalin MarinasAug 30, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.