[Pkg-mc-devel] Midnight Comander 4.8.1 [RFS]
onlyjob at member.fsf.org
Sat Feb 25 03:49:03 UTC 2012
On Sat, 25 Feb 2012 10:07:40 Yury V. Zaytsev wrote:
> Dmitry, please do! Then I can commit my changes to your package there. I
> don't remember how to bootstrap a gbp-compatible repository and
> (unfortunately) don't have time to investigate.
Thank Yury, I imported repository to collab-maint and added my changes on top.
> Shall I apply for joining collab-maint in order to get commit access?
Yes, please apply.
> Test: yes, sponsor: no (not yet).
Hopefully your concerns have been addressed, please have a look at the updated
package and my other email.
Thank you very much for your help on patch 99.
It is now working as expected.
> I will try to re-write the Debian-specific patch that we discussed
> earlier today ASAP, to me this is a show-stopper.
Never mind, I already did it. Sorry for asking for help, it only appeared to
be difficult at 4am. :)
> Also maybe I will succeed in convincing Dmirty to not to rebuild the bs
> and we need to figure out the remaining bs awk-related patch. I secretly
> hope that there is no need for it anymore...
Certainly patch is not needed, but I can't tell is upstream still need this
workaround. However it should be safe so I just implemented it properly with
passing an argument to configure.
Thanks for all your help.
P.S. if you think 'mc' doesn't belong to collab-maint we can always move it
back. I think collab-maint is a great place for a package.
There are much more sophisticated packages hosted at collab-maint so perhaps
'mc' is not special enough to be maintained outside of collab-maint.
More information about the Pkg-mc-devel