[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#918372: unblock: med-fichier/4.0.0+repack-6



Hi Adrian, Niels,

On 06-01-2019 20:01, Adrian Bunk wrote:
>> That is because gmsh from testing links to libmed1v5. Adding this
>> *versioned* breaks to libmed11 (albeit being a bit ridiculous from the
>> archive point of view) would do the right thing AFAICT.
>> ...
> 
> despite libmed11 not being installed at all in the debci test?

britney reads this to determine which packages (based on SRC) need to
come from unstable for testing in testing.

> You are saying that the (test) dependencies of gmsh/unstable matter when
> testing gmsh/testing with med-fichier/unstable?

Yes, because they are processed by britney. So if gmsh/testing and
med-fichier/unstable aren't a good match based on information that
britney has available, it will request the test with both from unstable.
britney looks at the regular Depends/Breaks/Conflicts fields as well as
the test dependencies.

> That's unexpected compared to the normal dependency semantics.

I agree, but this is how it is done now until we change it. We're open
for suggestions and I assume the release team is open for patches as well.

>>> The root problem is that debci installs cruft packages from unstable.
>>
>> Care to elaborate what you mean here? debci doesn't install anything.
>> It's apt that installs stuff. Based on a slightly odd configuration put
>> in place by autopkgtest on request of debci which got its trigger from
>> britney.
> 
> Britney says for med-fichier:
> old binaries left on amd64: libmed1v5, libmedc1v5 (from 4.0.0+repack-1) (but ignoring cruft, so nevermind)
> 
> Installing one of these cruft packages that cannot ever migrate to 
> testing is the problem.

Sure, but the root cause is that the combination to test isn't properly
determined by britney. britney just doesn't know.

> Correct would be that this debci test does not pull in a single package
> from unstable, since no non-cruft package depended on from gmsh/testing 
> is being provided by med-fichier/unstable.

I don't agree. What we want to test is what happens if med-fichier has
performed the transition from libmed5v1 to libmed11 and we try to move
the set to testing.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: