Hi,

might I suggest keeping the old and new xrdp packages in parallel for a
while? Maybe call the latter xrdp-git, then fold it into xrdp once there is
a release? It sounds to me like there were quite a lot of (upstream)
changes between the two and I'm not sure how clean the upgrade path is,
teething problems etc.

Cheers,
Christian

2016-04-19 12:00 GMT+02:00 Andreas Tille <andr...@an3as.eu>:

> Hi Dominik,
>
> On Tue, Apr 19, 2016 at 11:49:38AM +0200, Dominik George wrote:
> > >>  * It only contains debian/ now.
> > >
> > >Do you have any reason for this?
> >
> > Yes, because that's what Mike originally asked for, unless I got him
> wrong.
>
> I do not see any good reason for this kind of advise.  Mike, could you
> please confirm that you are against keeping the upstream source inside
> the archive.  IMHO this is against a very common gbp workflow and in
> this specific case I think its definitely needed.
>
> > >I'm missing the background knowledge to decide this so I'll leave this
> > >to you.  I have no idea about the motivation to pick a specific commit
> > >and not any other - it would be soooo helpful if upstream would tag
> > >releases.
> >
> > The only reason for the specific commit is that it is known to work. No
> more, no less.
>
> How has got this knowledge and how.
>
> > I talked with upstream about making a release, and we will do so
> together, but this will take some more weeks. There is quite some activity
> upstream right now. I understand you cannot wait any longer, so we will
> need to work without a release for now.
>
> Fully ACK.  Good to know that upstream is somehow convinced.
>
> Thanks for your work on this
>
>      Andreas.
>
> --
> http://fam-tille.de
>
> --
> To unsubscribe, send mail to 719624-unsubscr...@bugs.debian.org.
>

Reply via email to