Changes between Initial Version and Version 1 of Ticket #53334, comment 4


Ignore:
Timestamp:
Jan 17, 2017, 7:07:12 PM (7 years ago)
Author:
dbevans (David B. Evans)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #53334, comment 4

    initial v1  
    77The problem is not that the compatibility version has regressed but that it was accidentally advanced.  All versions of 2.36 are actually ABI compatible (other than the compatibility version).
    88
    9 The problem was introduced in gdk-pixbuf2 2.36.2 and fixed as you say in 2.36.3+ so only ports that linked against 2.36.2 when last installed/updated are effected.   So  everything that links with gdk-pixbuf2 is overkill.  And restoring the error seems to be counter productive.
     9The problem was introduced in gdk-pixbuf2 2.36.1 and fixed as you say in 2.36.3+ so only ports that linked against 2.36.1 or 2.36.2 when last installed/updated are effected.   So  everything that links with gdk-pixbuf2 is overkill.  And restoring the error seems to be counter productive.
    1010
    11 I've already revbumped the problem ports that I've run across so far, particular those that have binary archives linked against 2.36.2 and will do so with others as they become apparent.  Making a list now of any ports that may remain.  That is, those that were updated when 2.36.2 was active and have not yet been revbumped.  I think hat should be sufficient.
     11I've already revbumped the problem ports that I've run across so far, particular those that have binary archives linked against 2.36.1 or 2.36.2 and will do so with others as they become apparent.  Making a list now of any ports that may remain.  That is, those that were updated after 2.36.1 was committed and before  2.36.3 and have been revbumped thereafter.  I think hat should be sufficient.
    1212
    1313Let me know if you have any further suggestions or candidates.