Hello Gerard!

EOL procedure on the wiki explicitly names this as first step: Make sure the package is properly Obsoleted/Provided by something if it is being replaced, see Renaming/Replacing Guidelines (on wiki).

Since you have pkgfoo-split1 and pkgfoo-split2 and you probably want to merge them into pkgfoo, i'd suggest to have Obsolete/Provides like this inside the merged pkg:

Obsoletes: pkgfoo-split1 <= $LAST_VER_IN_F18 Obsoletes: pkgfoo-split2 <= $LAST_VER_IN_F18 Provides: pkgfoo-split1 = %{version} Provides: pkgfoo-split2 = %{version}

If you have pkgfoo and pkgfoo-split and you probably want to merge them into pkgfoo, i'd suggest to have Obsolete/Provides like this inside the merged pkg:

Obsoletes: pkgfoo <= $LAST_VER_IN_F18 Obsoletes: pkgfoo-split <= $LAST_VER_IN_F18 Provides: pkgfoo-split = %{version}

Just my two cents.

BR, Björn

Am Sonntag, den 12.05.2013, 04:08 -0500 schrieb Jon Ciesla:

Sorry for top post, mobile. I think given the lack of builds toy can skip Obsoletes and Provides, and can just follow the EOL procedure on the wiki.

On May 11, 2013 6:01 PM, "Gerard Ryan" galileo@fedoraproject.org wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

    Hi packaging,

    I've got two packages which should be one. The reason they
    were two
    before was because of some strange circular dependencies,
    iirc. This
    doesn't apply anymore since the upstream project have moved
    from CVS
    to Git, and seem to have moved some things between some of
    their
    subproject repositories to fix the circular dependency
    problem.

    So, the package that I want to drop hasn't been built for
    Rawhide or
    F19 yet, and I don't think it should be. I haven't updated the
    main
    package to merge in the split one yet (it's ready, just
    waiting for
    broken deps). My questions are mainly about what steps do I
    need to do
    to do this as cleanly as possible:

    - - Do I need to manually put in any 'Obsoletes' or 'Provides'
    or
    anything like that? Nothing else uses the split package apart
    from a
    couple of my other packages, which I will remove
    (Build)Requires from.

    - - Since it hasn't been built in F19 yet, is there anything I
    need to
    do to other than retire it in pkgdb? I've never dropped or
    retired any
    packages so I'm not sure of the steps that need to be done.

    Thanks in advance for any help you can provide,
    Gerard.
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.13 (GNU/Linux)
    Comment: Using GnuPG with Thunderbird -
    http://www.enigmail.net/

    iQIcBAEBCAAGBQJRjs3dAAoJEG7cfkpivEoVCUkQAIwAeayZh3VRoHaJ08Tq/FAb
    58Jx+1WE85RKR7qVUWGOleBoQ/upKc921tBtHz+ewX6F
    +Bs7PIKcQ/ljambhj2p1
    R5yN8Oit2LdkJ9qGDa758vUubK+UfVuKUTPKVK+yOetr2
    +i/29VCRvUVEnMOFoM0
    GOuPh5wagjEY+Wd1P+cTtwMMJxnx67/UMqnlNthRffUFKvHKYD6uoI8m
    +WQNhQWH
    PjDw2pdt/DkouznOSz64Wb2R3uUzfeI5
    +gHGADOxxkWdek9NCC1GVL23jA587EIc
    IL6T2vOtr6bParcic7exWgjkxlYd7Z4YZsvmPYrp0IszGQh3weO3dowTsXZtBFTB
    XfBhC7nGby1JG+L5VwLDpPEI4OVaecxyeRNhFly0bspX0UI
    +bI6jqJKX2188WDYW
    HZPfE6BOdwlbKVpEoxW0+NAPesjSqkA0
    +3JwW3aENb1Uv9fDkv8RUlpWao5hwCar
    CNwQtwantBEdE2EpvgrWrPnqkazd
    +VZJMkeXx403zYo0hRHwNQydrvb5pxZKznSC
    atAUyImUhLOqpfUwKB5o0jhZbeOC9ClhkMTeq47mSphbACng6GhTis2ShqCtMvom
    6G9nfa3029F
    +L88SgwHQLHSn42aZwVSPfZzpgM2ZW59joTpMZmpnJONaH/9LKALV
    mEYM/kd70ZtE9iK+TAQV
    =G5qS
    -----END PGP SIGNATURE-----
    --
    packaging mailing list
    packaging@lists.fedoraproject.org
    https://admin.fedoraproject.org/mailman/listinfo/packaging

-- packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging

You're welcome.

Putting in Obsoletes/Provides should be the "regular fashion" when merging or EOL'ing pkgs. It makes things really easier to maintain when you have to do an in-release update, e.g.: needing to fix security issues or serious bugs. YUM will purge the merged-in pkg itself and user's system keeps no leaves and there will be no possible broken deps on upgrading to the new in-release-version.

The other way round it makes maintaining dependend pkgs even easier, because things won't break caused by missing deps and having to look how to get them resolved properly again.

I'm not sure how FEDUP handles such cases on release updates, but I'm sure Obsoletes/Provides will make things smother in such senarios, too. At least it will help to cleanup otherwise kept leave-pkgs.

And don't forget to put in proper O/P into possible -devel-pkgs, too.

Cheers, Björn

Am Sonntag, den 12.05.2013, 13:29 +0100 schrieb Gerard Ryan:

...<snip>

Thanks for the replies guys. It's the second scenario in what you've mentioned Björn, there's pkgfoo and pkgfoo-split. The reason I was asking was because I was thinking along the lines of what Jon says -- that maybe obsoletes/provides can be skipped. I guess since it's my first time EOL'ing a package, there's no harm in me explicitly putting them in, just to make sure.

Thanks again, Gerard. -- packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging