On 07.04.2016 15:50, James Hogarth wrote: > > > On 7 April 2016 at 14:26, Tomas Hozza <thozza@xxxxxxxxxx <mailto:thozza@xxxxxxxxxx>> wrote: > > Hi all. > > We pushed an update for log4cplus in F24+ [1]. It is a rebase and one of the dependent packages is "pion-net". The problem is that pion-net does not build on F24+, which stops us from pushing update on F24 which would not break dependencies. There is an older build of pion-net in F24 from times when it was building just fine. > > What should be the process here? Should we untag the package from F24 or should I ignore the broken dependency? I don't see any good solutions to this problem other than fixing the FTBFS in pion-net. > > Also note that pion-net is orphaned. > > > > Well if you need it leaving it orphaned isn't going to help you (plus when it gets retired your package will no longer meet its dependency requirements so will need to be retired without the dep picked up). > > So as I see it options are: > 1) Pick up pion-net yourself > 2) Convince someone else to pick up pion-net > > Either way the FTBFS will need to be fixed ... unless you retire log4cplus from F24+ ... although I'm guessing you don't want to do that. > > > > > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx > Actually it is the other way around. The orphaned package pion-net depends on log4cplus. I'm not interested in taking ownership of the pion-net and actually retiring if from F24 works for me. log4cplus works as expected and is not broken, nor any of its dependencies. Only the one package which depends ON log4cplus. Regards, -- Tomas Hozza Senior Software Engineer - EMEA ENG Developer Experience PGP: 1D9F3C2D UTC+1 (CET) Red Hat Inc. http://cz.redhat.com -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
