Control: severity -1 wishlist
Control: retitle -1 `debci setup` options not documented

On Mon, Oct 30, 2017 at 02:22:52PM +0000, Андрей Родионов wrote:
> Hi Antonio,
> 
> 
> > On Oct 30, 2017, at 1:49 PM, Antonio Terceiro <[email protected]> wrote:
> > 
> > Control: tag -1 moreinfo
> > 
> > Hello, thanks for your bug report
> > 
> > On Mon, Oct 30, 2017 at 11:09:49AM +0000, Андрей Родионов wrote:
> >> Package: debci
> >> Version: 1.5.1
> >> Severity: normal
> >> 
> >> Dear Maintainer,
> >> 
> >> I'm trying to run debci setup on stretch and seeing the following in the 
> >> logs:
> >> 
> >> lxc-create: lxccontainer.c: lxc_container_new: 4151 Error: 
> >> adt-sid-armhf.new creation was not completed
> >>  Volume group "lxc" not found
> >>  Cannot process volume group lxc
> >> lxc-create: bdev/lxclvm.c: lvm_create: 414 Error creating new lvm blockdev 
> >> /dev/lxc/adt-sid-armhf.new size 1073741824 bytes
> >> 
> >> I don't have any custom configs, just ran "apt install debci". According 
> >> to the ./lib/environment.sh it will pick up "unstable" which will be 
> >> converted to "sid". I'm running on stretch (stable).
> > 
> > I can't understand what is relationship between the error message you
> > pasted above and the choice of default suite. Can you elaborate? if you
> > specify a suite, e.g. `debci setup -s stretch`, doesn't it fail in the
> > same way?
> 
> The error is not related to the bug. I don’t have working debci to put
> proper logs here. Parameter “-s” nowhere mentioned in documentation,
> so I haven’t tried it first… After I changed debci_suite in
> /etc/debci/conf.d/local.conf to stretch, I was able to continue with
> the build.

Yes, it's not documented yet. OTOH it is in the output of `debci setup
--help`.

Anyway I am turning this bug into a wishlist to document that.

> >> I was wondering if default debci_suite value could be taken from the 
> >> "lsb_release -a" output.
> > 
> > not really. just because the host system is stable does not mean that
> > the most common case is testing on stable.
> 
> Got it. Looks like codename on unstable is “n/a”, which is not really useful. 
> I’m trying to setup custom debian package on stable version. 

what exactly do you mean by codename here?

$ grep Codename /var/lib/apt/lists/*_unstable_InRelease
Codename: sid

Attachment: signature.asc
Description: PGP signature

Reply via email to