On (04/05/16 11:05), Alexander Bokovoy wrote:
>On Tue, 03 May 2016, Robbie Harwood wrote:
>> Lukas Slebodnik <lsleb...@redhat.com> writes:
>> > On (03/05/16 12:29), Robbie Harwood wrote:
>> > > David Kupka <dku...@redhat.com> writes:
>> > > 
>> > > > --8<------------- trac-ticket-template-proposal ------------------->8--
>> > > > Related SW versions:
>> > > > On server:
>> > > > {{{
>> > > > $ rpm -q freeipa-server pki-base 389-ds-base bind samba krb5-server
>> > > 
>> > > I think this is a good idea.  However, we are on Debian/family as
>> > > well now, and I think we want to accept bugs that come from these
>> > > users as well.
>> > 
>> > FreeIPA is heavily patched on debian and has quite old version there
>> > 4.0.5.
>> > 
>> > The better would be recommend to reproduce with upstream version
>> > (fedora/CentOS).
>> (FreeIPA 4.1.4 is available on Debian, but your point still stands.)
>> In summary: I don't like that upstream is conflated with fedora/CentOS.
>> Of course I understand that this was done to ease development and not
>> out of malice.  But longer term I would like Debian/Ubuntu FreeIPA to be
>> less of an afterthought because I believe we can attract users to our
>> product.  I believe this to be especially true with working
>> freeipa-client on those distros, which we now have and I am very happy
>> about.
>I think you miss context here. There was huge amount of work done in
>last couple months to get FreeIPA 4.3 running on Ubuntu and Debian. It
>made to Ubuntu 16.04. It didn't make to Debian proper yet for a single
>reason: FreeIPA tarball ships with a minified JS code for parts of the
>web UI framework which is against some of Debian policies and therefore
>FreeIPA is blocked from entering Debian.
I think you misses context here.

The porpose of reporting bugs to upstream is to file bugs to upstream version.
If the downstream version is patched with non-upstream patches
then you need to find out wheter bug is in upstream or downstream
caused by non-upstream patches. And it should be task of reporter
to ensure that bug is in upstream.

ATM the easiest way is to test with fedora.

>There are people like Timo Aaltonen who work on the Debian/Ubuntu
>support but they cannot do everything on their own. JS code issue is
>unique to Debian so ideally someone would need to contribute fixes that
>are right from Debian point of view but nobody did it so far. You are
I contributed in past :-)
but into C related code.

As I mentioned in previous mail.
If freeipa get to the state that debian has pure upstream version
then we can recommend to report bugs + exact version with dpkg-query

The purpose of David's mail was to simplify job for developers
and developers life will not be easier if developer need to
find out wheter bug is in upstream or it's caused by downstream patches.


Manage your subscription for the Freeipa-devel mailing list:
Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code

Reply via email to