• Bug#1067175: exaile: hard-coded dependency on libgtk-3-0 will become un

    From Simon McVittie@21:1/5 to All on Tue Mar 19 18:20:01 2024
    Package: exaile
    Version: 4.1.3+dfsg-2
    Severity: serious
    Justification: blocker for 64-bit time_t transition
    User: debian-arm@lists.debian.org
    Usertags: time-t
    Control: block 1036884 by -1

    exaile is an Architecture: all package, but has a direct dependency on libgtk-3-0, as well as an indirect dependency on libgtk-3-0t64 via gir1.2-gtk-3.0.

    On the architectures affected by the 64-bit time_t transition (notably
    armel and armhf), this is an impossible dependency, because libgtk-3-0 and libgtk-3-0t64 conflict.

    Please remove the explicit dependency on libgtk-3-0. For Python code
    that uses GTK via GObject-Introspection, it is sufficient to depend
    on gir1.2-gtk-3.0.

    More information about this transition is available on <https://wiki.debian.org/ReleaseGoals/64bit-time>.

    Thanks,
    smcv

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sat Mar 23 20:40:01 2024
    Processing control commands:

    tags -1 patch
    Bug #1067175 [exaile] exaile: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf
    Added tag(s) patch.

    --
    1067175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067175
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sun Mar 24 18:00:01 2024
    This is a multi-part message in MIME format...

    Your message dated Sun, 24 Mar 2024 16:49:59 +0000
    with message-id <E1roR2l-00958L-QO@fasolo.debian.org>
    and subject line Bug#1067175: fixed in exaile 4.1.3+dfsg-3
    has caused the Debian Bug report #1067175,
    regarding exaile: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
    immediately.)


    --
    1067175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067175
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 19 Mar 2024 17:14:34 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-113.6 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,HAS_PACKAGE,SPF_HELO_NONE,
    SPF_NONE,T_SCC_BODY_TEXT_LINE,UNPARSEABLE_RELAY,
    USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST autolearn=ham
    autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 6; hammy, 150; neutral, 24; spammy, 0.
    spammytokens: hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
    0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
    0.000-+--H*RT:311, 0.000-+--H*RT:108
    Return-path: <smcv@debian.org>
    Received: from str