I want consistency between the case where there is a binary build and
the case where there is a source build.
I want --source because I want the source package to be included in the
.changes.
I want to use one tool, (sbuildh) rather than having my scripts care
about how it is being called.
Hi,
Quoting Sam Hartman (2016-10-13 19:36:21)
> > "Johannes" == Johannes Schauer writes:
>
> Johannes> Do you know a situation when it would be beneficial to let
> Johannes> sbuild create the source package *again* after it has
> Johannes> already been produced
> "Johannes" == Johannes Schauer writes:
Johannes> Do you know a situation when it would be beneficial to let
Johannes> sbuild create the source package *again* after it has
Johannes> already been produced for sbuild?
Sbuild can take a directory as input.
I
Hi,
On Tue, 30 Aug 2016 20:56:30 -0400 Sam Hartman wrote:
> what happened:
> $ sbuild --source --no-arch-any --no-arch-all -c unstable -d
> sid-hadron-snapshot .
> dh clean
>dh_testdir
>dh_auto_clean
>dh_clean
> dpkg-source: info: using source format '3.0
package: sbuild
version: 0.70.0
severity: normal
what happened:
$ sbuild --source --no-arch-any --no-arch-all -c unstable -d
sid-hadron-snapshot .
dh clean
dh_testdir
dh_auto_clean
dh_clean
dpkg-source: info: using source format '3.0 (native)'
dpkg-source: info: building hadron-ci in
5 matches
Mail list logo