On Tue, Jan 14, 2014 at 5:38 PM, Adam Williamson <awilliam@xxxxxxxxxx> wrote: > On Tue, 2014-01-14 at 10:32 -0700, Michal Jaegermann wrote: >> Adam Williamson wrote: >> >> >> obexftp contains the same Requires except for libpthread (obexfs >> >> depends on libphread). There's an empty /usr/share/doc/obexftp/html >> >> included. >> > >> > They're the same tools, the obefxs source was moved into the obexftp >> > source tree upstream. >> > >> > The thing I was unsure about was dealing with obsoleting an orphaned >> > package. Do I have to adopt the orphaned package first? Or can I just >> > file a request to kill that package? >> >> I think that if obexftp package will "provide" a high enough version of >> obexfs then an update will automatically replace it and you will end up >> with obexftp only. Also anything which has explicit dependencies on >> obexfs will not raise a fuss as after such replacement dependencies will >> be still satisfied. > > Yes, I know that too. Let me play that tune again, Sam: I'm principally > asking the question of how the obexfs package should get retired. I just use "fedpkg retire" which does most of the work and then just file a rel-eng trac ticket to block it which does the rest. You don't need to own it. Peter -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
