On Fri, Sep 2, 2016 at 11:51 AM, Andrew Stitcher <[email protected]>
wrote:

> On Thu, 2016-09-01 at 22:14 -0400, Matt Broadstone wrote:
> > Hey all,
> >
> > Would it be possible to fix up the .gitattributes for the qpid-cpp
> > git
> > repository? I'm having an incredibly hard time updating the sources
> > for the
> > debian packaging because there are many mixed in CRLF files
> > throughout the
> > repository
>
> Can you explain exactly what the problem you are seeing actually is?
>
>
Sure.

The problem comes down to debian's sanity checks to ensure that files have
not been modified locally before building and packaging the resultant deb
file.

When you guys make a new release, I import those tarballs using
`git-buildpackage` to a new `upstream/<rel>` tag, which is to be used later
to generate the `orig` (pristine) tarball for the sanity check.  What seems
to be the problem (though I'm really guessing at best here, since I'm not a
debian packager by trade) is that line endings have been changed on a few
files between the releases, and so we now have differences in newly
imported files - as well as line ending changes - the latter of which are
not just "handled" for me during the merge. What happens then is that
debian's sanity checks when recreating the `orig` tarball indicate that
I've made a bunch of changes and need to resolve that.

Generally speaking though, I think this is a problem you'll want to solve
anyway given that you have mixed OS developers accessing the code on a
somewhat regular basis.  If anyone here is far stronger in
debian-packaging-foo than I, please let me know - I'm sure I could use help
;)

Matt

I have had no problem checking out the code from the repo on both Linux
> and Windows and building there.
>
> What is different about creating debian packages?
>
> Andrew
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to