What is the policy for handling a forked upstream project where the
fork seems much more alive then the original?
I'm the (mostly idle) maintainer of the Azureus/Vuze bittorrent
client. The original Azureus/Vuze project has gone mostly idle without
any new releases in more then a year. The code however has been forked,
by the original lead developers, as BiglyBT. And this fork seem to
be live and under active development.
So now my question is, what is the procedure for switching the code
base for the Fedora package from Vuze to BiglyBT?
Do I just switch the tar-ball in the azureus package repo and add an
"obsoletes" statement in the spec-file?
Can I change the name of the source rpm?
Can the name of the entire package (including the package git repo and
bugzilla entry) be changed?
Advice are welcome!
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2019-01-03 17:00 UTC in #fedora-meeting-1 on irc.freenode.net.
Local time information (via. uitime):
================= Day: Thursday ==================
2019-01-03 09:00 PST US/Pacific
2019-01-03 12:00 EST --> US/Eastern <--
2019-01-03 17:00 GMT Europe/London
2019-01-03 17:00 UTC UTC
2019-01-03 18:00 CET Europe/Berlin
2019-01-03 18:00 CET Europe/Paris
2019-01-03 22:30 IST Asia/Calcutta
---------------- New Day: Friday -----------------
2019-01-04 01:00 HKT Asia/Hong_Kong
2019-01-04 01:00 +08 Asia/Singapore
2019-01-04 02:00 JST Asia/Tokyo
2019-01-04 03:00 AEST Australia/Brisbane
Links to all tickets below can be found at:
= Followups =
#topic #719 Simplify packaging of forge-hosted projects
= New business =
#topic #841 Change or remove "Want to help" footer
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at:
If you would like to add something to this agenda, you can:
* Reply to this e-mail
* File a new ticket at: https://pagure.io/packaging-committee
* E-mail me directly
* Bring it up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.