1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.KDE

  • Re: CAUTION: QT-5 version 5.15.15 + 5.15.17 upgrade in Debian/unstable

    From Andrey Rakhmatullin@21:1/5 to Sedat Dilek on Sun Oct 27 19:50:01 2024
    On Sun, Oct 27, 2024 at 07:37:25PM +0100, Sedat Dilek wrote:
    just as a warning to be careful and check APT suggestions.

    Here 80+ packages will be removed.

    Here I am on Debian/unstable AMD64.

    Thanks.

    Best regards,
    -Sedat-


    To be more precise:

    This happens if you use KDE/Plasma and other KDE stuff from D/exp.

    No, this happens on pure sid, because the Qt transition is underway.


    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmceiX8tFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh YnEP/2+DClkVHaF1AJDHqDw2HGYoQQjXeLwxwKhxhSDWYH1yiDLMSQY4YklPyX+2 84+AvODYjRT/VTqeoA+A5FsCphyfp47ZIs35aoQ09EnOsD0jGfa4kJaoxIWqfS+2 7fBXRO9+2VKHoDAd0O/ehiQK8QPR2Q9bq2qLz8vxHhKtphTGXORp2KHIuwwZWVgf 6vbWHh+lCYcEedVX+aAFjdAmuoIE8ndKj28XFU3bRFtN56OXn6nA/pmo7XYnZhzC 3LnNWiXWseIsijj5x3s30hXkCI4sf1/X+vO7i4cYCJ9bjf1knloeejNINrxSVaYM YY9CgU1RK+IkmRM/r9wKFU6iX7k96mrkw31uHeZwiEmT6C6RhqnDXW0b6kpFUP8x pg8LOECP52IfyperNfEEf4lXIGflZ+B3xcO99PBrB9XK1qpG3eckGk06a7rxBbMt 0SZG42pFl60/qCN+LdGoe+BCCQvktI/7tf2dsgb5iCFQEcnqr3BtbA35P6EOfjg2 wCMAHIyxa8NeqJBbMcB674lD37M3RtOlSzwzpAHDNGSF6WrjQnxmVktvr6ikmIey XRJYWkAWZirsdCJ5kFY5adxDzkGNRGxrus8A6X3AS/CNKwmvwsvTjvsGBMo5zzQ4 ytvhp7RDUs/T6FjXx8Bg78mGFwkwX52eV/kh3KpnNyVjff7i
    =UZAc
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rakhmatullin@21:1/5 to Sedat Dilek on Wed Oct 30 11:40:01 2024
    On Wed, Oct 30, 2024 at 11:26:39AM +0100, Sedat Dilek wrote:
    The transition is still on-going ...

    Looks like it's almost finished, a couple of FTBFS packages need removal from testing and a couple of failing autopkgtests need investigation, but in sid it should already be fine.


    Not sure what means "transition is done" - for me it means when all
    software depending on it is rebuilt against -dev packages, too.

    What is not rebuilt yet?

    Just a question about quassel status:

    armhf + arm64 have NEW packages in D/sid.

    Not sure what do you mean ("NEW" has a special meaning in Debian and it doesn't look like you meant it).
    If you mean it had more binNMUs on those two arches then it's pretty
    common and also unrelated.


    NEW (armhf + arm64) = 1:0.14.0-2+b3 (see b3 - amd64 has still b2).

    This is never important (as I mentioned).
    And, as I mentioned, "NEW" in Debian means https://ftp-master.debian.org/new.html

    Is there sth. BROKEN with the AMD64 packages?

    No?


    The build of AMD64 needs a manual trigger or what does the process look like?

    The process follows the transition tracker that you linked.
    Why do you think anything is needed?

    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmciC2ItFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh 0QwP/ji9dNtZ9igmC4jTULsuEjbYlIUxc/V2ZOlOxHkTe7u+2mgKWtcjjHML8HKf al65DpzmHoHogBqAmIkFj3uK3WVyW25N9n8W2HyhbFGnDluSKXOTZdA7DrKG4+sF fMeou2DYQNkzJqaIZMV5ciTFGZN7pBdrWu39imFhBBkmU7AxJnyov+OHfYuH0pl2 O1RU8zILQ8HY5g0wrsY1lKLFLXeW42uqEPXu9WWjFuQBmAVqZmfgwAD93GmZAByf K2DtYCJvS/yzW0eA5cNBspyCyYolTLDVj3TtjRwX8AThG2cbyHTfGznjNkoRd7Tq 0YiVX6E+sbw5Yz+MSuGnqZ5+SLYDsfAlz78Av4FZ2Ll4bujp1zhNMUGVMMWqBI3v OmtnU5UnVZIIowoXLaZKLQl/hazezDhQMaY0pWwYG8esHyt3/cDPCiEULm5CsspY xbyVTvt22xCJ1ukCdW0Z8yM5WBLx9XQfJ9J77pxNw2Ki2XCYI6/HXy43kLiP7ZX8 UdGSzVz1bw+I/IbxEUkkSXawRT8FFvWqWMckhVKOQzfay1GpNaJJsU7nYwQCtcmT UKRUvnK52AkBDCqdrBxmLUI36biyN6wWqbJFxOm2DGO40E0cDZj+RPbW998Rurvm 1RnhBRr0O2SjT8c3Z421Mi+zPcyrzE1y+1/o0t5XhD6PPkHY
    =YuAu
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rakhmatullin@21:1/5 to Sedat Dilek on Wed Oct 30 11:20:01 2024
    On Wed, Oct 30, 2024 at 10:19:52AM +0100, Sedat Dilek wrote:
    The transition is still on-going ...

    Looks like it's almost finished, a couple of FTBFS packages need removal
    from testing and a couple of failing autopkgtests need investigation, but
    in sid it should already be fine.

    Just a question about quassel status:

    armhf + arm64 have NEW packages in D/sid.

    Not sure what do you mean ("NEW" has a special meaning in Debian and it
    doesn't look like you meant it).
    If you mean it had more binNMUs on those two arches then it's pretty
    common and also unrelated.

    Is there sth. BROKEN with the AMD64 packages?

    No?

    Where can I see the status or a build-log?

    You can see both statuses and build logs on https://buildd.debian.org/status/package.php?p=quassel


    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmciB0ktFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh A6oP/RSBo30etiZ3WlBUcxaBOgl97xBt+MAbUXABRoKo9nxKsNR5Y7yRppDQ7oZU QIrmjoK1zrNxKaDzQW1E+GeeQZ/47fqgMR0zug95oXOH2l/MfLDhEseOShw2upw5 h7Pgyg7okJXtVLhHsIUsWmmw0EKsKoUYFw3dWMIe/xbz8rbSymcVzXEmlrv+pBRT 90WHcTCzEsWjGheo+zGFJKpp3SLxb77hVfQxMQojZhPyyriif2k4v7XhdESnJiNn PzxWkWYBRzHmMhI/bKZYE0+ixCMWishX35erXqDVjHGcknteD9vWZOGW9Q5bLLmo 88z5TTGsRrxC/GI7Y+ik8yklekqeOPSIaySXJb6U8s9yYw+MvDU0HVuLkr3ZyUz4 AtEyR/bc7nympCJV2aJn2UYVC16KxeOoULAewlqi9DsAVzrrR6RP40173kk8FHOX dzVTEFCHbaK/PxwgHoi70+T3vt9VnylV2ggL9eLRF1hi5Q97poQizWUw0gIWTOeG 9EoSvjGS/qaBIOkTzIbYm+X7Pibb1XFYuDI3GQ0sF1Z4xAFIaqiHZ6vHmOrilhLM 3x7QqCrQ2w8bMtGgPPw3pw0MAIn9GBLUIYw435oRxBKc9RrgBFOOJOHHtOM1vAVL KkYzwy3Bc/BB/ATdWa8Oi7YaGNVxmrgYJBbsXcDeCXxhURJm
    =aEZH
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rakhmatullin@21:1/5 to Sedat Dilek on Wed Oct 30 12:30:09 2024
    On Wed, Oct 30, 2024 at 12:19:08PM +0100, Sedat Dilek wrote:
    The transition is still on-going ...

    Looks like it's almost finished, a couple of FTBFS packages need removal
    from testing and a couple of failing autopkgtests need investigation, but
    in sid it should already be fine.


    Not sure what means "transition is done" - for me it means when all software depending on it is rebuilt against -dev packages, too.

    What is not rebuilt yet?


    Simple question:
    Does quassel need a rebuild against all QT-5.15.15 -dev packages it
    depends on: Yes or No?

    It doesn't depend on qtbase-abi* so it doesn't. You don't see it on the transition tracker page either.

    Just a question about quassel status:

    armhf + arm64 have NEW packages in D/sid.

    Not sure what do you mean ("NEW" has a special meaning in Debian and it doesn't look like you meant it).
    If you mean it had more binNMUs on those two arches then it's pretty common and also unrelated.


    NEW (armhf + arm64) = 1:0.14.0-2+b3 (see b3 - amd64 has still b2).


    ^^ quassel version 1:0.14.0-2+b3 on arm* architecture is a rebuild
    against QT-5.15.15 -dev packages?

    No, quassel version 1:0.14.0-2+b3 on armhf was a rebuild for time64 7
    months ago, on arm64 it's a rebuild for PAC/BTI support which is an
    ongoing rebuild right now.

    This is never important (as I mentioned).
    And, as I mentioned, "NEW" in Debian means https://ftp-master.debian.org/new.html


    OK.
    I watch "NEW" packages uploaded to incoming.d.o

    Sure, you just need to know that using the word "NEW" for stuff that is
    not NEW or related to the NEW queue in any way will cause confusion.

    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmciF7ctFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh MzUP/jJ4nB7O+P6fBWw7wnyIiGuNhvwd5f8e2bRN8hb2d/Q4w8rj8xQ05IacSiQJ QD0lVbTWMfJ0CX4NxsewckqUpv5yzzyrq9sQUVF+J6dnwfMg7A3TJU2/qw5hv15R WQzjwDXcajqic3ewQX2kwmTUOwjrDZLuFigGi8+njgYnwidUbLRW8KV76wduNeWV ivdBa/G0zEUt2a7eVLcPfNg1LNG7U352gM2ViKjP8iQHtISPFNRD5eygwbDhp08F 9pCBFQShTj0T7AJhvEInle0hHzuCk/Zy5dHvLVTAki+yVE9yhvNuxD6WN3UiYEHF n8amFJmMqf9O1m4NSt0tCrlahOWYlWiXCxDIDP+0vyj65oezC6wNegOWDcRSo3/F xpet7uuL211gajfAYOnQmFVMpJP2TASaaE4xyPQi5rHLVZ0MC28UgCp0Zhkqjjha wQSCtzJb/oVXPPHiGlnKcx3ZLypPa/PwZASkMeqn2asAV9j6uEX7A1yNvBp6u3m3 X7OMe3nzNJ0D1QTlTTZdkTy1hJjJ3SiXfsujxfBsGyJoQDH1oTvEcbyh5bDBZw/C 2xAW7+rAjOktVmPM2vMOlmiGoROs8nZbhBL2MWkgp3yPhGWCd1UTefSNH05E1hcq 36OkNYfiq3XKDihTpWOp/SHhPyB+Y42ZOUPpWOF8HI8B/39S
    =hDg7
    -----END PGP SIGNATURE-----

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