On Mon, Jan 29, 2018 at 12:09:04PM +0000, Ian Jackson wrote: > Right. But if you're not doing a -1 upload the .orig is somewhere > else ?
In that case the .orig is simply discarded after doing the build instead
of being copied out of the chroot.
> Right, but is the normal workflow to have the .orig in .. when working
> in ../<packagename> ?
That's what I do at least.
mattia@warren ~/devel/debian/limnoria % tree -L 2
.
├── gpg
│ └── <stuff>
├── limnoria
│ ├── debian
│ ├── locales
│ ………… <i.e. the sources>
├── limnoria_2017.10.01-1.debian.tar.xz
├── limnoria_2017.10.01-1.dsc
├── limnoria_2017.10.01.orig.tar.gz
├── limnoria_2017.10.01.orig.tar.gz.asc
└── <more random files>
And when I try to build that .dsc I end up with:
mattia@warren ~/devel/debian/limnoria % DEB_BUILD_OPTIONS=nocheck
DEB_BUILD_PROFILES=nocheck pbuilder b limnoria_2017.10.01-1.dsc
…
mattia@warren ~/devel/debian/limnoria % ls ~/pbuilder/result/unstable/amd64/
limnoria_2017.10.01-1_all.deb limnoria_2017.10.01-1.dsc
limnoria_2017.10.01-1_amd64.buildinfo limnoria_2017.10.01-1_source.changes
limnoria_2017.10.01-1_amd64.changes limnoria_2017.10.01.orig.tar.gz
limnoria_2017.10.01-1.debian.tar.xz limnoria_2017.10.01.orig.tar.gz.asc
> Does that mean the origs end up in multiple places ?
Well, you've got one in .., as you said. Then pbuilder copies it into
the chroot for building. Some black boxes later the full build is done
and comes the time to export the build artifacts out of the chroot into
the original system, at this point:
* you are doing a -1 build, so it copied out into --buildresult
together with the .debs
* you are doing a -2 build, so it is not copied out
Here I'm writing 'a -1 build' and 'a -2 build', but clearly there are
several other cases that makes a .orig appear or not in a .changes file.
In the case of a -1 build (with the default configuration where
--buildresult is not ..!) you effectively end up with two copies of the
.orig: one in .. and one in --buildresult.
Anyway, isn't this discussion kind of moot? I understood that for
reasons you're thinking of specifying `--debbuiltopts -b`, so you'd get
a binary only build and that one would discard the .orig as well (as
with -b the source don't appear on the .changes at all). Obviously that
doesn't include people with SOURCE_ONLY_CHANGES=yes, as those when doing
a -b build would get a _amd64.changes with only .debs and a
_source.changes with only source.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
