George Danchev <danchev@spnet.net> (13/05/2012): > Just to add few more hopefully helpful bits. > > 1) the changelog of not yet uploaded package to sid, waiting for > your green light: Thanks, that's appreciated. > bobcat (3.00.02-1) unstable; urgency=low > > * New upstream release (bumps the soname version). > + Arg, ArgConfig and ConfigFile use the bridge design pattern. > + Programs depending on the Bobcat library must be recompiled. > * Rename the library package libbobcat2 to libbobcat3 to reflect > the soname bump (no further relationships are needed, since > libbobcat2 and libbobcat3 do not ship common files). > * Drop unneeded and errant relationships of > Provides|Conflicts|Replaces: > libbobcat1 previosly added to the library package section (post > lenny). > * Likewise, drop Provides|Conflicts|Replaces: libbobcat1-dev > relationships from the -dev package section (libbobcat1-dev is > a non-virtual package in lenny, which has been subsequently renamed > to libbobcat-dev in squeeze). > > > 2) the ben file: > > title = "bobcat"; > is_affected = .build-depends ~ /libbobcat-dev/; > is_bad = .depends ~ /libbobcat2/; > is_good = .depends ~ /libbobcat3/; Tracker is up at: http://release.debian.org/transitions/html/bobcat.html In your first mail: > All of these built successfully against the new bobcat library, even > though ccbuild required a minor tweak [1] to succeed due to unrelated > FTBFS with newer GCC, reported as #667132. I think it would be nice if this could be fixed ASAP, so that it's ready to be binNMU'd when the time comes, and so that we discover new failures early, if any. This looks like quite self-contained, so I might get back to you soon to get this transition started. Ping me back by wednesday if you didn't hear from me by then. Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature