pbuilder , is there a way to generate and keep log files with human-readable time-stamps
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
This is what my existing ~/.pbuilderrc
is which is symlinked to ~/root/.pbuilderrc
$ cat ~/.pbuilderrc
BASEPATH="/var/cache/pbuilder/sid-amd64/base.cow"
DISTRIBUTION="sid"
MIRRORSITE="http://deb.debian.org/debian/"
# Enable build log
PKGNAME_LOGFILE="yes"
while I am understanding how cowbuilder and pbuilder works, is it possible to have a log file which shows how the build happened even after the build is successfully created.
Update - I am using cowbuilder and don't see any way to have detailed logs to keep after a run happens.
debian pbuilder cowbuilder
add a comment |Â
up vote
1
down vote
favorite
This is what my existing ~/.pbuilderrc
is which is symlinked to ~/root/.pbuilderrc
$ cat ~/.pbuilderrc
BASEPATH="/var/cache/pbuilder/sid-amd64/base.cow"
DISTRIBUTION="sid"
MIRRORSITE="http://deb.debian.org/debian/"
# Enable build log
PKGNAME_LOGFILE="yes"
while I am understanding how cowbuilder and pbuilder works, is it possible to have a log file which shows how the build happened even after the build is successfully created.
Update - I am using cowbuilder and don't see any way to have detailed logs to keep after a run happens.
debian pbuilder cowbuilder
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
This is what my existing ~/.pbuilderrc
is which is symlinked to ~/root/.pbuilderrc
$ cat ~/.pbuilderrc
BASEPATH="/var/cache/pbuilder/sid-amd64/base.cow"
DISTRIBUTION="sid"
MIRRORSITE="http://deb.debian.org/debian/"
# Enable build log
PKGNAME_LOGFILE="yes"
while I am understanding how cowbuilder and pbuilder works, is it possible to have a log file which shows how the build happened even after the build is successfully created.
Update - I am using cowbuilder and don't see any way to have detailed logs to keep after a run happens.
debian pbuilder cowbuilder
This is what my existing ~/.pbuilderrc
is which is symlinked to ~/root/.pbuilderrc
$ cat ~/.pbuilderrc
BASEPATH="/var/cache/pbuilder/sid-amd64/base.cow"
DISTRIBUTION="sid"
MIRRORSITE="http://deb.debian.org/debian/"
# Enable build log
PKGNAME_LOGFILE="yes"
while I am understanding how cowbuilder and pbuilder works, is it possible to have a log file which shows how the build happened even after the build is successfully created.
Update - I am using cowbuilder and don't see any way to have detailed logs to keep after a run happens.
debian pbuilder cowbuilder
debian pbuilder cowbuilder
edited Sep 1 at 8:08
asked Aug 31 at 18:21
shirish
3,31942474
3,31942474
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
If you run pbuilder
manually, you can use the --logfile
and --loglevel
options to specify where and what to log.
Generally speaking though youâÂÂll use pbuilder
via another tool, which will take care of logs for you. For example, pdebuild
will leave a log file ending in .build
, with start and end timestamps, containing the build logs, alongside the packages it gets from pbuilder
.
The same applies to cowbuilder
: pdebuild --pbuilder cowbuilder
will build a package using cowbuilder
and leave a log file names after the package, ending in .build
, alongside the resulting packages (typically in the parent directory).
I updated my query and now have cowbuilder in the mix.
â shirish
Sep 1 at 8:08
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
If you run pbuilder
manually, you can use the --logfile
and --loglevel
options to specify where and what to log.
Generally speaking though youâÂÂll use pbuilder
via another tool, which will take care of logs for you. For example, pdebuild
will leave a log file ending in .build
, with start and end timestamps, containing the build logs, alongside the packages it gets from pbuilder
.
The same applies to cowbuilder
: pdebuild --pbuilder cowbuilder
will build a package using cowbuilder
and leave a log file names after the package, ending in .build
, alongside the resulting packages (typically in the parent directory).
I updated my query and now have cowbuilder in the mix.
â shirish
Sep 1 at 8:08
add a comment |Â
up vote
2
down vote
If you run pbuilder
manually, you can use the --logfile
and --loglevel
options to specify where and what to log.
Generally speaking though youâÂÂll use pbuilder
via another tool, which will take care of logs for you. For example, pdebuild
will leave a log file ending in .build
, with start and end timestamps, containing the build logs, alongside the packages it gets from pbuilder
.
The same applies to cowbuilder
: pdebuild --pbuilder cowbuilder
will build a package using cowbuilder
and leave a log file names after the package, ending in .build
, alongside the resulting packages (typically in the parent directory).
I updated my query and now have cowbuilder in the mix.
â shirish
Sep 1 at 8:08
add a comment |Â
up vote
2
down vote
up vote
2
down vote
If you run pbuilder
manually, you can use the --logfile
and --loglevel
options to specify where and what to log.
Generally speaking though youâÂÂll use pbuilder
via another tool, which will take care of logs for you. For example, pdebuild
will leave a log file ending in .build
, with start and end timestamps, containing the build logs, alongside the packages it gets from pbuilder
.
The same applies to cowbuilder
: pdebuild --pbuilder cowbuilder
will build a package using cowbuilder
and leave a log file names after the package, ending in .build
, alongside the resulting packages (typically in the parent directory).
If you run pbuilder
manually, you can use the --logfile
and --loglevel
options to specify where and what to log.
Generally speaking though youâÂÂll use pbuilder
via another tool, which will take care of logs for you. For example, pdebuild
will leave a log file ending in .build
, with start and end timestamps, containing the build logs, alongside the packages it gets from pbuilder
.
The same applies to cowbuilder
: pdebuild --pbuilder cowbuilder
will build a package using cowbuilder
and leave a log file names after the package, ending in .build
, alongside the resulting packages (typically in the parent directory).
edited Sep 1 at 9:54
answered Aug 31 at 21:01
Stephen Kitt
147k22321388
147k22321388
I updated my query and now have cowbuilder in the mix.
â shirish
Sep 1 at 8:08
add a comment |Â
I updated my query and now have cowbuilder in the mix.
â shirish
Sep 1 at 8:08
I updated my query and now have cowbuilder in the mix.
â shirish
Sep 1 at 8:08
I updated my query and now have cowbuilder in the mix.
â shirish
Sep 1 at 8:08
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f466096%2fpbuilder-is-there-a-way-to-generate-and-keep-log-files-with-human-readable-tim%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password