Presently, libproxy bundles libmodman and includes it in the package. Upstream split libmodman into a separate tarball, and then set up libproxy to build off of a system version of libmodman if it exists (otherwise it uses the version that is bundled with it). Review request for the new libmodman package: https://bugzilla.redhat.com/show_bug.cgi?id=603514 The packager will be sponsored by me, but I'm waiting for this package to go through. He also submitted this bug against libproxy: https://bugzilla.redhat.com/show_bug.cgi?id=603517 Which asks the maintainer to upgrade to the version that can optionally use the system version of libmodman. And, of course, libmodman conflicts with all previous versions of libproxy, because there are file conflicts. Since both of these items basically depend on each other, where should we go next? -- Ian Weller <ian@xxxxxxxxxxxxx> () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
Attachment:
pgpS0ETFeWX0Y.pgp
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
