I just checked sbuild-launchpad-chroot and those messages aren't errors,
they are merely normal schroot log messages.
When a chroot file isn't found, we print the "doesn't exist" message to
stdout and exit 0 which seems absolutely appropriate behavior.
** Changed in: sbuild-launchpad-chroot (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637898
Title:
sbuild-launchpad-chroot shouldn't emit errors when non-LP chroots are
used
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1637898/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
