On Wednesday 31 August 2016 09:51 PM, Antonio Terceiro wrote:
> On Wed, Aug 31, 2016 at 07:36:56PM +0530, Pirate Praveen wrote:
>> Do we really need to generate keys for sbuild?
>>
>> sudo sbuild-update --keygen
>
> with the newest sbuild, probably not. not sure about sbuild from stable.
>
ok.
On Wed, Aug 31, 2016 at 07:36:56PM +0530, Pirate Praveen wrote:
> Do we really need to generate keys for sbuild?
>
> sudo sbuild-update --keygen
with the newest sbuild, probably not. not sure about sbuild from stable.
signature.asc
Description: PGP signature
Do we really need to generate keys for sbuild?
sudo sbuild-update --keygen
signature.asc
Description: OpenPGP digital signature
On Saturday 27 August 2016 07:02 PM, Antonio Terceiro wrote:
> I would like to not special case any suite here. you just need an
> experimental chroot, named experimental-${arch}-sbuild, and it just
> works. just like if you were building for e.g. jessie.
>
> if you don't want to have a separate c
On Sat, Aug 27, 2016 at 12:34:52AM +0530, Pirate Praveen wrote:
> Hi,
>
> Is this change ok? It will not work when build dependencies from
> experimental are required
for that to work you just need to have experimental in the sources.list
> but will work in the simple case of just
> stashing pac
Hi,
Is this change ok? It will not work when build dependencies from
experimental are required but will work in the simple case of just
stashing packages in experimental to not break dependencies in unstable.
diff --git a/build-and-upload b/build-and-upload
index 1a41c68..66fd4d1 100755
--- a/bui
6 matches
Mail list logo
