Possible regression in dependency tracking when update is run

[atelszewski]

Hi,

There is something bad (TM) happening ;-) [i.e. I don't think that's the behavior we expect]

I run:
slackrepo --preview update

and I get (among the others):

================================================================================
academic/pulseview                                                      12:57:25
================================================================================

Calculating dependencies ... 
Hints for libraries/libsigrok:
  ADDREQUIRES="libftdi1 librevisa libserialport"
Hints for libraries/qt5:
  OPTIONS="DOCS=yes EXAMPLES=yes PROPRIETARY_CODECS=yes"
  ADDREQUIRES="freetds OpenAL libwebp opus snappy"
Dependency tree:
academic/pulseview (ok)
  libraries/qt5 (rebuild for updated deps)
    libraries/libxkbcommon (ok)
    libraries/libwebp (updated)
    libraries/libinput (ok)
      libraries/libwacom (ok)
    libraries/OpenAL (ok)
    development/snappy (ok)
    development/freetds (ok)
    audio/opus (ok)
  libraries/libsigrokdecode (ok)
    python/python3 (ok)
  libraries/libsigrok (ok)
    libraries/libserialport (ok)
    libraries/librevisa (ok)
    libraries/libftdi1 (ok)
      libraries/confuse (ok)

academic/pulseview is up-to-date (version 0.4.0).

That is, academic/pulseview won't be rebuild, although its dependency libraries/qt5 is going to be rebuilt.

And there's yet another problem:

I run:
slackrepo update PaleMoon qt-creator

and although libraries/qt5 failed to build, slackrepo continues and rebuilds qt-creator (which depends on qt5).

I'm testing against 65b100d.

I hope I keep you busy coding ;-)

--
Best regards,
Andrzej Telszewski

[atelszewski]

Hi,

I think this is confirmed.

I downgraded spice and spice-gtk was rebuilt, but virt-manager wasn't (which depends on spice-gtk).

--
Best regards,
Andrzej Telszewski