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 policycoreutils (which incidentally is also listed as having 2 versions in both testing and unstable) which caused AUTORM so will this clear up by itself?

https://release.debian.org/bullseye/freeze_policy.html

Also this page is unclear to me. Will the refpolicy package I just uploaded
go into testing in 10 days time or will that be 20 days?

--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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 the testing and unstable columns, what does that mean?

I see 2:2.20210203-3 in the testing column and 2:2.20210203-4 in the
unstable column.

Will the refpolicy package I just uploaded
go into testing in 10 days time or will that be 20 days?

Normally, what you see on the excuses page would apply.

https://qa.debian.org/excuses.php?package=refpolicy

However, I think that the hard freeze will happen before the package
migrates, so I suggest that you file an unblock request (reportbug release.debian.org) asking the release team to accept the changes.

https://release.debian.org/#release-dates

--
bye,
pabs

https://wiki.debian.org/PaulWise

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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
the testing and unstable columns, what does that mean?

I see 2:2.20210203-3 in the testing column and 2:2.20210203-4 in the
unstable column.

I just refreshed that page and now I see them in different columns. Strange.

Will the refpolicy package I just uploaded
go into testing in 10 days time or will that be 20 days?

Normally, what you see on the excuses page would apply.

https://qa.debian.org/excuses.php?package=refpolicy

However, I think that the hard freeze will happen before the package migrates, so I suggest that you file an unblock request (reportbug release.debian.org) asking the release team to accept the changes.

https://release.debian.org/#release-dates

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984642

Thanks, I've filed an unblock request.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984645

I've also filed an unblock request for refpolicy.

--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)