On Thu, Jun 14, 2018 at 10:58:47AM +0200, Paul Gevers wrote: > On 14-06-18 10:08, Sébastien Villemot wrote: > >> I saw an upload of dynare 4.5.5-2, which apparently tried to fix part of > >> this, but now the test for dynare migration¹ fails with a segfault of > >> octave. Looking at the list of installed packages and their versions, I > >> suspect dynare is missing a *versioned* dependency on the latest octave. > >> What do you think? > > I guess what's happening here is that the test bed contains dynare 4.5.5-2, > > liboctave5 and octave 4.2.2-3 (and not 4.4), which is a combination which is > > technically possible but indeed broken. > > So let's make sure the archive knows that. > > In any case, even though the dependency relationships are not perfect, nothing > > is actually broken, and the problem will disappear after the transition is complete. > I think the versioned Depends solution is correct. The reason why I > think we (as maintainers) should start caring more is that we need > autopkgtest to be able to figure this out by itself and for that it > needs to be fed with the right relations. This *is* making the > transition more difficult because the RT now has to judge if you made > the right assessment. It's so much easier if the test just passes. I have just uploaded dynare 4.5.5-3 which has a versioned dependency on octave 4.4. Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
Attachment:
signature.asc
Description: PGP signature