status of refpolicy package

https://qa.debian.org/developer.php?login=russell%40coker.com.au In the above page it has both versions 2:2.20210203-3 and 2:2.20210203-4 in the testing and unstable columns, what does that mean? Does the fact that it is (temporarily I hope) in AUTORM state mess it up? I've fixed the bug in po

Re: status of refpolicy package

On Saturday, 6 March 2021 15:25:48 AEDT Paul Wise wrote: > On Fri, Mar 5, 2021 at 11:12 AM Russell Coker wrote: > > https://qa.debian.org/developer.php?login=russell%40coker.com.au > > > > In the above page it has both versions 2:2.20210203-3 and 2:2.20210203-4 > > in &

Bug#1033060: qa.debian.org: wrong username and email for my DDPO page

Package: qa.debian.org Severity: normal https://qa.debian.org/developer.php?login=etbe%40debian.org https://qa.debian.org/developer.php?login=russell%40coker.com.au The above pages attribute my packages to Taihsiang Ho , apparently due to my last upload of the rasdaemon package.

Bug#97643: klisa isn't fixe

reopen 97643 quit Just tested this on version 4:2.2.1-1.4 and the bug is still there. Russell Coker

libsemanage testing migration

https://qa.debian.org/excuses.php?package=libsemanage It says that libsemanage is not migrating due to bug #1091109. That bug never affected version 3.8 as the issue was addressed upstream. I accidentally dropped the changelog entry (which I will restore next time I do an upload) and it doesn'