Re: Meaning of "Checking build-dependency (indep) on amd64" excuse

2019-01-17 Thread Paul Gevers
Hi Feri,

Please CC me on reply.

>> I think I understand the rest, although I don't know whether the
>> autopkgtest regression blocks migration indefinitely.  That would be
>> unfortunate, because unstable pcs needs unstable pacemaker, so they
>> deadlock...
>
> I think you will need to ask the release team to hint them in
> together.

Yes, they will block unless overridden by the release team, or better,
when you change your package relations such that the migration software
figures out that they need to be tested together. (The release team and
I can do the latter manually, but that is not really sustainable.)

With the current code your options are:
- *versioned* depends on one of the binary packages from the source you
want from unstable in any of the binary packages that is going to be
taken from unstable already
- *versioned* breaks or conflicts on the binary packages from the source
you want from unstable in any of the binary packages that is going to be
taken from unstable
- *versioned* test dependency in the package that is used for
autopkgtest (only helps if the version that is tested is already taken
from unstable). The version of the test dependency will NOT be added to
the triggers, but if the version of the autopktest is going to be taken
from unstable already due to other considerations, with the current
settings of ci.d.n and autopkgtest the required version will be installed.

Mind you, if the migration software asks for a test with multiple
packages from unstable (visible in the triggers string) a PASS will be
used for all those packages, so you only need to "fix" this in one package.

Paul



signature.asc
Description: OpenPGP digital signature


Re: Meaning of "Checking build-dependency (indep) on amd64" excuse

2019-01-16 Thread Paul Wise
On Wed, Jan 16, 2019 at 12:07 AM Ferenc Wágner wrote:

> Thanks, Paul, it makes sense indeed and I agree it's reasonable to do,
> but how/why is this an excuse?  Is there any problem with that?

No idea, you would have to ask the release team about this.

> That gives 404 to me.

https://salsa.debian.org/release-team/britney2/blob/master/britney2/policies/policy.py#L916

-- 
bye,
pabs

https://wiki.debian.org/PaulWise
http://bonedaddy.net/pabs3/



Re: Meaning of "Checking build-dependency (indep) on amd64" excuse

2019-01-15 Thread Ferenc Wágner
Paul Wise  writes:

> On Tue, Jan 15, 2019 at 7:06 PM  wrote:
>
>> Could somebody please explain me the meaning of the "Checking
>> build-dependency (indep) on amd64" migration excuse as seen on
>> https://qa.debian.org/excuses.php?package=pacemaker?
>
> Looking at the code, I think it means that the migration scripts are
> verifying the Build-Depends-Indep packages are installable on amd64
> and probably ignoring installability on other arches. This is
> reasonable since all of Debian's arch:all buildds use amd64 right now.

Thanks, Paul, it makes sense indeed and I agree it's reasonable to do,
but how/why is this an excuse?  Is there any problem with that?

> https://salsa.debian.org/release-team/britney2/blob/britney2/policies/policy.py#L916

That gives 404 to me.

>> I think I understand the rest, although I don't know whether the
>> autopkgtest regression blocks migration indefinitely.  That would be
>> unfortunate, because unstable pcs needs unstable pacemaker, so they
>> deadlock...
>
> I think you will need to ask the release team to hint them in together.

OK, will do.
-- 
Regards,
Feri



Re: Meaning of "Checking build-dependency (indep) on amd64" excuse

2019-01-15 Thread Paul Wise
On Tue, Jan 15, 2019 at 7:06 PM  wrote:

> Could somebody please explain me the meaning of the "Checking
> build-dependency (indep) on amd64" migration excuse as seen on
> https://qa.debian.org/excuses.php?package=pacemaker?

Looking at the code, I think it means that the migration scripts are
verifying the Build-Depends-Indep packages are installable on amd64
and probably ignoring installability on other arches. This is
reasonable since all of Debian's arch:all buildds use amd64 right now.

https://salsa.debian.org/release-team/britney2/blob/britney2/policies/policy.py#L916

> I think I understand the rest, although I don't know whether the
> autopkgtest regression blocks migration indefinitely.  That would be
> unfortunate, because unstable pcs needs unstable pacemaker, so they
> deadlock...

I think you will need to ask the release team to hint them in together.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise