After talking to development team, they decided is best to have another package called "mstflint4" in universe repository for trusty (than going on with a sync/merge like this SRU was proposing). For that to happen I'll now prepare a source package and make it available for it to be uploaded to -universe. Then I'll ask for sponsorship again.
From #ubuntu-devel:
10:37 <inaddy> slangasek: you mentioned that instead of merging/sync mstflint for trusty we should create a mstflint4 package (probably universe). what is the best procedure for this ? to follow the request for inclusion (as described in [MIR] procedure) ? creating a PPA with full source + bzr branch ?
10:45 <rbasak> inaddy: an uploader will be able to upload any source package. I suggest you follow normal SRU procedure and link to a source package upload from the bug somehow. A PPA would be fine.
10:45 <rbasak> (and detail the exception in the bug)
Thank you Talat.
After talking to development team, they decided is best to have another package called "mstflint4" in universe repository for trusty (than going on with a sync/merge like this SRU was proposing). For that to happen I'll now prepare a source package and make it available for it to be uploaded to -universe. Then I'll ask for sponsorship again.
From #ubuntu-devel:
10:37 <inaddy> slangasek: you mentioned that instead of merging/sync mstflint for trusty we should create a mstflint4 package (probably universe). what is the best procedure for this ? to follow the request for inclusion (as described in [MIR] procedure) ? creating a PPA with full source + bzr branch ?
10:45 <rbasak> inaddy: an uploader will be able to upload any source package. I suggest you follow normal SRU procedure and link to a source package upload from the bug somehow. A PPA would be fine.
10:45 <rbasak> (and detail the exception in the bug)