fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
fche has joined #systemtap
higgins has quit [Quit: Leaving]
higgins has joined #systemtap
fche has quit [Ping timeout: 268 seconds]
fche has joined #systemtap
fche has quit [Read error: Connection reset by peer]
orivej has quit [Ping timeout: 245 seconds]
fche has joined #systemtap
_whitelogger has joined #systemtap
orivej has joined #systemtap
orivej has quit [Ping timeout: 258 seconds]
_whitelogger has joined #systemtap
khaled has joined #systemtap
orivej has joined #systemtap
<ema>
fche: hey, I'm trying to build systemtap 4.1 and it fails building the docs because of an empty <tbody> in tapsets.xml
<ema>
the commit removing tbody's contents seems to be eddee1202a1ed99c7a6e78976ee2c2d4bfc6e308
<ema>
the file in question is doc/SystemTap_Tapset_Reference/syscalls.xmlpart
<ema>
but then I see that tbody content was re-added again in da2a89dcf54af8ce7eebe7575b04ed7f48314e0a, mmh
<fche>
ema, yeah there was a doc generation misstep
<fche>
sorry about that
<fche>
we're thinking about getting away from relatively complicated xml/etc. and doing something simpler
<fche>
not sure what though
<ema>
oh ok, so the xmlto issue will be fixed eventually in 4.2?
<fche>
oh sure; in the mean time you can configure --without-docs, or apply that fix commit to your local checkout
<ema>
I'm preparing an updated package for Debian, so yeah I'll add the fix as a patch
<ema>
thanks!
<fche>
very good!
<fche>
did you take over debian packaging from, oh dear, not sure who did it last?
<ema>
then I've worked on 4.0 for the Debian Buster release (didn't want us to release with a broken systemtap!)
<ema>
and now I'm gonna take care of 4.1 as it looks like an interesting release :)
<fche>
thanks a lot
<fche>
do you think we need a more formal communication channel with you folks to keep you abreast of updates?
<ema>
no need, I read the mailing list
<fche>
I'm embarrassed to admit that our non-fedora testing is very limited (I think we have a modern ubuntu VM but that's about it). Should we coordinate for some prerelease testing?
<ema>
ah yes that would be great!
<fche>
ok. our rough timeline for 4.2 would be something like five months from now, so we have some time. Do you have any idea about the debian/stap userbase? How many folks are we collectively serving with this stuff?
<ema>
that's a tricky question. There's popcon (popularity contest, opt-in at distro installation time) data which can answer it to a very limited extent