On Mon, Jun 4, 2012 at 2:05 AM, Cyril Brulebois <k...@debian.org> wrote: > Johannes Ring <joha...@simula.no> (31/05/2012): >> python-ufc needs to be rebuilt against the latest swig (2.0.7). Please >> binNMU it. >> >> nmu python-ufc_2.0.5-2 . ALL . -m 'Rebuild against swig 2.0.7, see >> #675207.' > > if this package has such strict dependencies on swig, why aren't they > exposed through strict package dependencies?
You mean by adding something like "swig2.0 (>= 2.0.7)" in Build-Depends? The thing is that UFC only depends on SWIG >= 2.0.0, however, it will always need to be rebuilt whenever a new SWIG release enters the archive. Can this be automated or will I need to request a binNMU each time? Thanks, Johannes -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caljqy_gxk3rlkg09sb6kjxhq+ywbrjq-hsj-d5nnjtg1txv...@mail.gmail.com
