Public bug reported:
Hello, most of our Launchpad build logs for most packages are fairly
verbose, giving full command lines with all arguments for compilers,
which can help understand what exact inputs were used when building any
given package.
The Rust default cargo output is very terse and does not show this level
of detail. This is fine when it's run interactively at a terminal but
build logs should be more verbose to allow later investigations, problem
solving, etc.
For example, the Ubuntu security team was investigating the build logs
for the papers package to determine if some unmaintained crates were
used in our build, and found that the build logs were insufficient. The
output is along the lines of:
Compiling serde v1.0.217
Compiling equivalent v1.0.1
Compiling hashbrown v0.15.2
[...]
The logs we were consulting are at
https://launchpadlibrarian.net/777827190/buildlog_ubuntu-plucky-
amd64.papers_48~beta-3ubuntu2_BUILDING.txt.gz
I believe the implementation I would like is for cargo to emit verbose
build logs when stdout is connected to a file or socket, and the current
upstream minimalism when stdout is connected to a terminal. The end
result that I want is for our Launchpad build logs of our packages to be
verbose, and if this implementation suggestion doesn't work, then we
might need to get more creative.
Thanks
** Affects: rust-defaults (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100308
Title:
Please provide more verbose rust build logs in launchpad
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-defaults/+bug/2100308/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
