On Sat, Aug 22, 2015 at 02:53:09PM +0100, Adam D. Barratt wrote: > Hi, > > On Sat, 2015-08-22 at 11:59 +0200, Guido Günther wrote: > > Hi, > > On Sat, Aug 22, 2015 at 04:39:05AM +0000, Debian testing autoremoval watch > > wrote: > > > virt-manager 1:1.0.1-5 is marked for autoremoval from testing on > > > 2015-09-09 > > > > > > It is affected by these RC bugs: > > > 793601: virt-manager: purging virt-manager deletes files owned by > > > virtinst: /usr/share/virt-manager/**/*.py > > > > This is fixed in experimental, is it o.k. to upload to sid without > > interfering with the gcc transition? The package is python only. > > Similarly to libvirt, as long as there's no C++ code in virt-manager and > it does not expose any C++ artefacts in its public ABI, uploading it to > unstable now should be fine. "Python only" shouldn't be an issue.
It's python only - thanks for the clarification! Cheers, -- Guido
