[lsb-discuss] unoffficial LSB conference call minutes for 8 May 2013

R P Herrold herrold at owlriver.com
Wed May 8 20:50:46 UTC 2013

LSB teleconference

Wednesday,  8 May 2013 @11:00 to noon, US ET

Where:	(605) 715-4920 Access Code: 512468

Gobby:	gobby -j lsb-temp.pmman.net:6522 with passwd: LSB

IRC channels are:
 	#lsb-meeting at freenode.net during meetings
 	#lsb at freenode.net most other times

in the form : name (organization)  [irc_nick]
Jeff Licquia (LF) licquia
Russ Herrold (Owl River)  orc_emac
Rick Troth (Velocity Software) rickt
Robert Schweikert (SuSE)  robjo
Mats Wichmann (Intel)  mwichmann

Kay Tate (SuSE)  ktate

Posted Agenda:

  - LSB May updates: lots of bugs getting attention.

  - LSB 5.0 status (such as it is).

  - Infrastructure updates: reboot of bzr server, final 
shutdown of old POWER build server, wiki updates.

New business:

Meeting opens at 11:00 with:

Jeff: LSB 4 series May updates.  appchecker, and distchecker 
getting some love, but most updates will be more oriented to 
LSB 5 tests.  After bug triage last week, Jeff sent a mailing 
list piece, proposing to postpone the SDK update til the next 
update release.  Also interested users were invited to propose 
bugs for inclusion this round.  No objections during the call 
to so proceeding, either

No one came forward to this regard -- speak now, or wait three 
months, readers of these minutes.

PAM tests are reported by Corel, that Fedora 19 has some 
changes that are causing test failures.  The disk full 
notifications seem to be not reliable under some 
distributions.  Russ: Query: is this documented in the man 
pages in play?

Russ also observed mount option changes with a recent update 
to 'kpartx' under CentOS 6.4 updates, with a new options 
silently appearing to mandate blocking for a '-s' synchronous 
succeed or failure

Jeff: 5.0 stuff Other bugs have taken precedence.  Graphics 
libraries (PNG abi change) (JPEG soap opera covered in links 
in last week's minutes) are causing some heartburn.  Retaining 
PNG 1.2 may not play well with the 'ground truth' of current 
distribution practice (PNG 1.5)

In other news, Ubuntu (Raring Ringtail) and Debian each have 
had new releases -- Debian, a major one ('WHeezy, their v 7'), 
which Russ forced to be released through his actions.  Last 
prior release ('Squeeze' their v 6) was in 2011.  Ubuntu tests 
to trail Debian as to all not features that interest them, and 
so we can expect a flow through in Ubuntu's 13.10 release 
(code-name: Saucy Salamander)

Wheezy has both libpng devel headers and libraries in both 
relevant versions

The jpg situation: upstream has a new developer, who appears 
to not be getting along well with others.  The libjpeg-turbo 
project, which started out as a simple optimization project, 
has become a full-fledged fork.

We did have an issue with OpenSUSE only shipping the new jpeg 
libraries, but it turns out this may have been inadvertent, 
and the libjpeg-turbo libs may appear in a bug fix soon.  If 
this happens, every distro will support the LSB libjpeg62 
interface, which allows us to play "wait-and-see" for a while.

New infrastructure.  The new Power units are working out well, 
as they seem well connected and quite performant

The old Wiki (Mediawiki) updates became more urgent when SEO 
spammers discovered the venue.. MW 1.19 seems to be a long 
term support place to move to.  see:

add on matter:  some pre-conference discussion in IRC was 
discussing the fact that bugzilla has multiple products that 
may not play well, 'trans-product'.  A bug may be a 'blocker' 
and partially completed such that it is not 'really' a blocker 
any more.  'Bugzilla foo' thoughts from the list are 
solicited.  Removing a 'blocker' once it is laregely done is 
not compelling, because we lose the ability to look at it 
later to build Release Notes.  Red Hat's current 
implementation of bugzilla handles this well. (not solving our 
blocker issue). but adding Release Note generation better). 
Russ to find out more and advise the mailing list

Quick summary of what we do now: LSB being a large "software 
project", bugzilla is divided into several products.  We use 
release-rollup bugs on each product to track deliverables - 
you can look at the SDK blocker to decide if the next SDK is 
ready to release or not by whether there are open bugs 
blocking it. We also use those dependant bugs for release note 
information.  But by their nature, certain bugs span products. 
Example: "RFE: add pam_get_user".  Implementation would have a 
database component, an SDK component, an appchk/libchk 
component, a specification component, and would have to be 
covered somewhere in the compliance test suites.  Thus the bug 
would have to block multiple release rollups.

But when database/SDK/spec/checkers part of that process is 
done, that bug isn't really 'blocking' the rollups for those 
components any longer; it remains open because of missing test 
suite coverage but looks like it is open across the board. 
We don't want to remove it from the rollups it no longer 
blocks, because then we don't have the thread of what was 

Call ends at local Noon

Weekly Bug triage:
The bug tracker is at: https://bugs.linuxbase.org/
irc-only #lsb-meeting at freenode.net
Thurs at 10:00 Eastern
Bugzilla stats as of 08 May: 527 open (527 on 04/24), 523 
assigned, 4 new
New last 90 days: 51, last 30: 8; closed last 90: 50, last 30: 
Changed this week: 5, last week: 30
Bugs that are assigned but have no milestone: 212
Rollup bugs: 20

last week's bug triage minutes:
Minutes (text):


Next meeting:
15 May 2013 11:00 to noon, US ET

gobby unofficial minutes are open for edit for at least 15 min 
after each call, and then issued into the mailing list

This document: LSB_minutes_20130508.txt

More information about the lsb-discuss mailing list