[ Request ] Missing bootchart2, please sync it from Debian Sid

[dino99]

Quantal archive has bootchart package; but installing the new insserv package, i've seen this comment:

insserv (1.14.0-3)
 * Suggest the actively maintained bootchart2 instead of the doormant bootchart package. (Closes: #599012)

So it should be a good idea to drop that actual bootchart 0.90 from Quantal archive, and replace it by bootchart2 0.14.4-1 from Debian Sid archive

http://packages.debian.org/fr/sid/bootchart2

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: bootchart (not installed)
Uname: Linux 3.6.0-999-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
Date: Fri Aug 10 18:27:14 2012
SourcePackage: bootchart
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bryan Quigley (bryanquigley)]

bootchart "1" doesn't work with systemd, while bootchart2 ships in debian with systemd jobs[1]
[1] https://packages.debian.org/wheezy/amd64/bootchart2/filelist

[Bryan Quigley (bryanquigley)]

So I was just informed that the bootchart package in Ubuntu is being maintained separately: (ubuntu-devel)
gQuigs: I was wondering why bootchart2 hasn't been automatically synced from debian?
cjwatson: gQuigs: overwrites binaries from bootchart; when I last checked I heard there wasn't much point as our bootchart had most of the relevant stuff anyway
cjwatson: Actually binaries from pybootchartgui
cjwatson: anyway it's in the sync blacklist
cjwatson: bootchart # keybuk, entirely separate packaging
cjwatson: bootchart2 # cjwatson, ditto; our bootchart source has many of the improvements here, and the pybootchartgui binary clashes
cjohnston cjwatson
cjwatson: oh.. in that case should I guess I should file a separate request to pull the systemd units out of boothchart2?
...
xnox: gQuigs: the problem with bootchart2 was that it was systemd only and doesn't support upstart boot. Kind of worthless for comparing bootspeed on ubuntu then, isn't it

I'll open a new bug for the systemd support to bootchart.

[dino99 (9d9)]

Seems like bootchart2 is required now by systemd-boot system:

https://bugs.launchpad.net/ubuntu/+source/bootchart/+bug/1353587

the ubuntu-devel option looks strange: why maintaining a fork based on an old package, instead of forking the new one (if necessary) ?

[Daniel Hollocher (chogydan)]

upstart has bootchart, and systemd has systemd-analyze plot > plot.svg

I think you need to sell your case for bootchart2 better, so setting to incomplete. Feel free to unset!

[Daniel Hollocher (chogydan)]

for more info regarding systemd: http://0pointer.de/blog/projects/blame-game.html

[dino99 (9d9)]

hi Daniel,

time have elapsed since that report have been sent, and i have to answer:
- why bootchart is still into the more recent archives( utopic/vivid) as its a non maintained and oldish package ? That's the first reason for moving to something maintained & far better.

..... from the github project :

      Why bootchart2 ?
      ------------------

 There are a number of interesting additional features:

 * higher resolution - the taskstat interface gives nanosecond
   timing information, where /proc/*/stat information is far,
   far less reliable and useful.

 * higher performance - the C re-write allows us to collect more
   data, more quickly - sampling at ~50+Hz.

 * using PROC_EVENTS we can determine accurate process parentage
   without needing to use a (poorly maintained) 'acct' binary

 * no Java dependency - with the visualisation in easy-to-hack
   python, development is quicker, and dependencies more commonly
   found.

 * simpler wrappers - by using ptrace to connect to and extract
   data from the collector, we no longer require a consistently
   visible set of logs accessible via a shared file-system.

 * built-in visualisation - allowing some level of interaction,
   zoom and so on.

 * better rendering - render to png, or svg, with added event
   annotation support, and 'show more' functionality.

 * cumulative, and total CPU time graphing in the boot-chart.

 * and no doubt more by the time this is actually read.

That is: if bootchart is considered as a future no-go, then purge it from Ubuntu archive; but Debian still has it (bootchart2) even if systemd is/will be used (but not only). So to me, the most logical is to switch to bootchart2.