Re: [Kolab-devel] Kolab Development packages now requiring a package for composer

2015-05-13 8:20 GMT+02:00 Timotheus Pokorra <[email protected]>:

> >> My guess is that dpkg-source is doing some kind of strange magic to
> ensure
> >> the "php textfile" is in the right format or ends with a newline
> whatever.
> >
> > There's also the [   59s] running debian transformer... step in
> >
> https://obs.kolabsys.com/package/live_build_log/home:timotheus:branches:Kolab:Development/composer/Debian_8.0/i586
> > build log . I think this is also where the newline might get added, but
> > perhaps you're right and OBS (ab?)use of dpkg-source is the reason.
> The source of debian_transformer is here:
> https://github.com/openSUSE/obs-build/blob/master/debtransform
> On first sight, I cannot see where the byte is added.
>

I ran debtransform locally and it seems to be the cuplrit:

~/composer$ md5sum debian/composer.phar
4678f9f648f2fb2348097ebf4bbde229  debian/composer.phar
~/composer$ ./debtransform . composer.dsc ../composer.new
debtransform: . composer.dsc ../composer.new
~/composer$ cd ../composer.new/
~/composer.new$ zcat composer_1.0.0-0.4.diff.gz | patch -p1
patching file debian/bzr-builder.manifest
[...]
patching file debian/composer.phar
[...]
~/composer.new$ md5sum debian/composer.phar
261fd5bf293a2e1ff1d7ba9db9dd388a  debian/composer.phar

I think patch command is responsible for the newline (well, it's a binary
file, not sure how Debian manages those inside a source package)

Regards,


Mateusz.

_______________________________________________
devel mailing list
[email protected]
https://lists.kolab.org/mailman/listinfo/devel