On Fri, Jun 03, 2016 at 01:25:41AM +0200, Dominik George wrote:
> > Apart from that: Uploaded!!! As the package will go through the NEW
> > queue, let's see what the ftp-masters say.
>
> Thanks a lot for the help and the final upload!
Thanks to you both!
> Meanwhile, I have started work on
On Thu, Jun 02, 2016 at 11:02:09PM +0200, Dominik George wrote:
>
> There are some notes from Andreas and you in the changelog. I think they are
> irrelevant for the public. Can I drop them?
Drop whatever you think is irrelevant that I might have injected
Andreas.
--
http://fam-tille.de
Hi Mike,
> I made some cosmetic changes under debian/changelog and re-fixed the
> year-author-syntax in debian/copyright's Copyright: fields.
OK. I skipped that as DEP-5 says that the Copyright: fields may well be an
exact copy of the copyright notice in the source files.
> Apart from that:
Hi Nik,
On Do 02 Jun 2016 23:53:48 CEST, Dominik George wrote:
Hi,
Ack. Please give a short reason in debian/changelog for closing those
bugs, then: e.g.
- Using VNC as backend is discouraged nowadays and xrdpxorg (or
what's its name) supercedes that VNC backend. Thus closing bug
Hi,
> Ack. Please give a short reason in debian/changelog for closing those
> bugs, then: e.g.
>
>- Using VNC as backend is discouraged nowadays and xrdpxorg (or
> what's its name) supercedes that VNC backend. Thus closing bug related
> to VNC as xrdp backend. (Closes: #1, #2, #3, #4...).
I
Hi Nik,
On Do 02 Jun 2016 23:02:09 CEST, Dominik George wrote:
Hi,
Ack. Please give a short reason in debian/changelog for closing those
bugs, then: e.g.
- Using VNC as backend is discouraged nowadays and xrdpxorg (or
what's its name) supercedes that VNC backend. Thus closing bug
Hi,
> Ack. Please give a short reason in debian/changelog for closing those
> bugs, then: e.g.
>
>- Using VNC as backend is discouraged nowadays and xrdpxorg (or
> what's its name) supercedes that VNC backend. Thus closing bug related
> to VNC as xrdp backend. (Closes: #1, #2, #3, #4...).
Hi,
> As a training task, please do this:
>
>o remove the above quoted placeholder white-list block
>o run debuild -uc -us -S -Zxz and let lintian provide you
> with files not mentioned anymore in debian/copyright
>o go over the debian/copyright.in and merge information from
>
On Do 02 Jun 2016 21:13:14 CEST, Dominik George wrote:
Hi,
Are you sure that all those bugs can be closed? Have you tested your
version regarding all those reported issues you are closing? If yes.
Then...
Personally, I like to name what I close. I.e. give a short description
how an issue
Hi Nik,
On Do 02 Jun 2016 01:20:00 CEST, Andreas Tille wrote:
Hi Dominik,
On Thu, Jun 02, 2016 at 12:44:18AM +0200, Dominik George wrote:
newest version is in collab-maint, issues seem to be resolved.
Please test, and, if satisfied, feel free to upload ;).
Very good. Unfortunately I can
Hi,
> Are you sure that all those bugs can be closed? Have you tested your
> version regarding all those reported issues you are closing? If yes.
> Then...
>
> Personally, I like to name what I close. I.e. give a short description
> how an issue was fixed. If I don't know how it was fixed but
Hi Dominik,
On Do 02 Jun 2016 01:26:30 CEST, Dominik George wrote:
Hi,
one more question:
Is the „Closes:“ line in changelog syntactically correct to close
all the bugs?
-nik
Are you sure that all those bugs can be closed? Have you tested your
version regarding all those reported
On Thu, Jun 02, 2016 at 06:19:58AM +0200, Andreas Tille wrote:
> Without checking: After Building you get a *.changes file.
run lintian on it to check, lintian will complain if the syntax is
wrong…
lintian $changes_file
--
cheers,
Holger
signature.asc
Description: Digital signature
Without checking: After Building you get a *.changes file. Open this
and check whether it has a Closes: line featuring all the bugs you want
to close.
Sorry for my brewity
Andreas.
On Thu, Jun 02, 2016 at 01:26:30AM +0200, Dominik George wrote:
> Hi,
>
> one more question:
>
> Is the
Hi Dominik,
On Thu, Jun 02, 2016 at 12:44:18AM +0200, Dominik George wrote:
> newest version is in collab-maint, issues seem to be resolved.
>
> Please test, and, if satisfied, feel free to upload ;).
Very good. Unfortunately I can not test before next Monday. Mike
if you can run a test and
Hi,
one more question:
Is the „Closes:“ line in changelog syntactically correct to close all the bugs?
-nik
--
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
Dominik George · Mobil: +49-151-61623918
Teckids e.V. · FrOSCon e.V. · OpenRheinRuhr e.V.
Fellowship of the FSFE ·
Hi,
newest version is in collab-maint, issues seem to be resolved.
Please test, and, if satisfied, feel free to upload ;).
Cheers,
Nik
--
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
Dominik George · Mobil: +49-151-61623918
Teckids e.V. · FrOSCon e.V. · OpenRheinRuhr
Hi
On Wed Jun 1 20:23:15 2016 GMT+0200, Andreas Tille wrote:
> On Wed, Jun 01, 2016 at 08:16:20PM +0200, Dominik George wrote:
> > We tried to avoid updateing to a new upstream commit as the one in use was
> > well-tested, but looking through the changes, there has been a big diff,
> > but
> >
On Wed, Jun 01, 2016 at 08:16:20PM +0200, Dominik George wrote:
> We tried to avoid updateing to a new upstream commit as the one in use was
> well-tested, but looking through the changes, there has been a big diff, but
> almost all of it seems to be fixing warnings and code formatting.
>
> So
Hi,
> > While I do agree with you, please give us a few more days (three, let's
> > say) to find a workaround. I have something schemed, but need to find out
> > whether it is too ugly to share or not ;).
> >
Something new:
Upstream actually seems to have a patch that fixes this issue.
We
On Mi 01 Jun 2016 11:31:49 CEST, Dominik George wrote:
Hi,
GTK3 and Qt5 are tricky in remote environments, anyway. It is mostly
because of upstream devs not being aware enough of remote desktop
technologies.
Personally, I think, we should / you should upload xrdp as is now to
Debian
Hi,
> GTK3 and Qt5 are tricky in remote environments, anyway. It is mostly
> because of upstream devs not being aware enough of remote desktop
> technologies.
>
> Personally, I think, we should / you should upload xrdp as is now to
> Debian unstable (not experimental, really unstable) and open
Hi Dominik, Andreas,
On Mi 01 Jun 2016 11:15:36 CEST, Andreas Tille wrote:
On Wed, Jun 01, 2016 at 10:30:02AM +0200, Dominik George wrote:
We know that GTK3 and/or Qt5 components are somehow involved. They
seem to reset the layout in some way on startup. Why and how, I
don't know yet. I
On Wed, Jun 01, 2016 at 10:30:02AM +0200, Dominik George wrote:
>
> We know that GTK3 and/or Qt5 components are somehow involved. They seem to
> reset the layout in some way on startup. Why and how, I don't know yet. I
> also do not know yet whether this is a GTK/Qt bug or an x11rdp bug. We see
Hi,
>> I've scheduled a session for that at our organisation's meeting this
>weekend.
>
>Any outcome of this session?
Yes, to some extent.
We know that GTK3 and/or Qt5 components are somehow involved. They seem to
reset the layout in some way on startup. Why and how, I don't know yet. I also
On Wed, May 18, 2016 at 04:18:22PM +0200, Dominik George wrote:
> > > Well, at least I got hold of a client system fortesting by now.
> >
> > Fine. Just let me know if I should test in my system which actually has
> > shown the problem. I'd happily help out with testing.
>
> I've scheduled a
> > Well, at least I got hold of a client system fortesting by now.
>
> Fine. Just let me know if I should test in my system which actually has
> shown the problem. I'd happily help out with testing.
I've scheduled a session for that at our organisation's meeting this weekend.
-nik
--
On Wed, May 18, 2016 at 03:20:58PM +0200, Dominik George wrote:
> Hi,
>
> > Do you have any news for this last showstopper to upload the new version
> > (at least I'd upload once this is fixed).
>
> Well, at least I got hold of a client system fortesting by now.
Fine. Just let me know if I
Hi,
> Do you have any news for this last showstopper to upload the new version
> (at least I'd upload once this is fixed).
Well, at least I got hold of a client system fortesting by now.
Cheers,
Nik
--
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
Dominik George ·
Hi Dominik,
On Thu, Apr 28, 2016 at 07:21:24PM +0200, Andreas Tille wrote:
>
> > I think we will be able to fix this issue.
>
> Sound promissing after "setxkbmap de" seems to fix the issue.
Do you have any news for this last showstopper to upload the new version
(at least I'd upload once
On Thu, Apr 28, 2016 at 07:09:37PM +0200, Dominik George wrote:
> > I definitely needed to install xorgxrdp as well to get my normal desktop
> > as usual. While on normal apt-get installs Recommends are installed I
> > wonder what alternative could bring up a sensible desktop otherwise and
> >
Hi Dominik,
On Wed, Apr 27, 2016 at 10:00:32PM +0200, Dominik George wrote:
> Him
>
> > Seems like you forgot to add debian/startwm.sh to the repository.
>
> Oops, yes, it got lost somewhere.
>
> I added it now.
Thanks. I think we are quite there. I cleaned up the changelog from my
previous
Hi,
> My first attempt to connect from a windows machine to my test linux box
> just brings up a ligthblue empty space (same color as xrdp login screen)
> but no window manager or desktop environment (I'm using xfce by
> default).
>
> I definitely needed to install xorgxrdp as well to get my
Him
> Seems like you forgot to add debian/startwm.sh to the repository.
Oops, yes, it got lost somewhere.
I added it now.
-nik
--
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
Dominik George · Mobil: +49-151-61623918
Teckids e.V. · FrOSCon e.V. · OpenRheinRuhr e.V.
Hi Dominik,
On Tue, Apr 19, 2016 at 12:06:55PM +0200, Dominik George wrote:
> >How has got this knowledge and how.
>
> We have been running this commit in production for almost a year. We started
> with what used to be HEAD for a very long time. It was bleeding edge whem we
> started. The
Hi Mike,
On Tue, Apr 19, 2016 at 10:17:07AM +, Mike Gabriel wrote:
>
> Personally, I am not a great fan of gbp. It has caused me more trouble than
> served any good (and I really think that gbp is a great tool for Debian
> packaging, as I said, my personal workflow does not use it).
>
>
Hi Dominik,
On Tue, Apr 19, 2016 at 12:06:55PM +0200, Dominik George wrote:
>
> We have been running this commit in production for almost a year. We started
> with what used to be HEAD for a very long time. It was bleeding edge whem we
> started. The specific commit used now is that state that
Hi Andreas,
On Di 19 Apr 2016 12:00:39 CEST, Andreas Tille wrote:
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.
Hi Andreas,
>How has got this knowledge and how.
We have been running this commit in production for almost a year. We started
with what used to be HEAD for a very long time. It was bleeding edge whem we
started. The specific commit used now is that state that was „stable“ for the
repo for a
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,
Hi,
>> * 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'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
Hi Dominik,
thanks for working on xrdp and commiting to the repository.
On Mon, Apr 18, 2016 at 09:34:35PM +0200, Dominik George wrote:
> * It only contains debian/ now.
Do you have any reason for this?
> * get-orig-source fetches sources from GitHub, depending on package
>version and
HI Nik,
theres for giving your time to this.
On Mo 18 Apr 2016 21:34:35 CEST, Dominik George wrote:
Hi,
I updated the repo in collab-maint to the following state:
* It only contains debian/ now.
* get-orig-source fetches sources from GitHub, depending on package
version and two
Hi,
I updated the repo in collab-maint to the following state:
* It only contains debian/ now.
* get-orig-source fetches sources from GitHub, depending on package
version and two variables inrules to determine the versions of
librfxcodec and xorgxrdp. I decided to create a single
Hi Dominik,
On Fri, Apr 15, 2016 at 12:45:47PM +0200, Dominik George wrote:
> Also, I kindly ask you to co-maintain the package after I got it finalised on
> Monday.
Comaintenance is confirmed.
Thanks for the status upgrade
Andreas.
--
http://fam-tille.de
Hi Andreas,
> I'm afraid I'm getting on your nerves […]
No, you absolutely don't. You are actually right in every single point.
> Is it really that hard to take
> the repository where official xrdp was maintained and if nothing else
> helps
>
> rsync -a --delete -v
>
> commit all
Hi Dominik,
I'm afraid I'm getting on your nerves but we are chatting now way to
long how to to get xrdp finalised. I asked you several times how I
could help and there is no response. Is it really that hard to take
the repository where official xrdp was maintained and if nothing else
helps
On Fri, Apr 01, 2016 at 01:40:40PM +, Mike Gabriel wrote:
>
> I think that all previous uploads to Debian should be in the repo. Plus your
> changes.
+1
Kind regards
Andreas.
--
http://fam-tille.de
Hi Nik,
On Fr 01 Apr 2016 14:47:52 CEST, Dominik George wrote:
Hi,
> Yes, I know that. However, the only problem to be solved is merging the
> two repositories, and having some remotes dangling around doing so does
> not make it easier.
If you ask me you should not put too much effort into
Hi,
> > Yes, I know that. However, the only problem to be solved is merging the
> > two repositories, and having some remotes dangling around doing so does
> > not make it easier.
> If you ask me you should not put too much effort into this merge. The
> main thing is that it somehow can be
On Tue, Mar 15, 2016 at 10:03:13PM +0100, Dominik George wrote:
> Hi,
>
> >sorry for nagging constantly but you expected to be done until middle
> >of
> >last week.
>
> No. I said I'd be done until middle of *this* week, and I actually got
> publishing the stuff on my todo list for tomorrow.
Hi,
>sorry for nagging constantly but you expected to be done until middle
>of
>last week.
No. I said I'd be done until middle of *this* week, and I actually got
publishing the stuff on my todo list for tomorrow.
>Could you please, pretty please be more transparent by
>commiting your work to
Hi again Dominik,
sorry for nagging constantly but you expected to be done until middle of
last week. Could you please, pretty please be more transparent by
commiting your work to some public place. It does not help at all if
you silently work on problems others could help with.
Thanks
On Tue, Mar 08, 2016 at 11:21:32PM +0100, Dominik George wrote:
>
> In that case, please let us finalise the work ;). I expect it to be done
> until
> middle of the week.
Just for my understanding: To what repository are you pushing
intermediate changes to follow your steps?
Kind regards and
On Tue, Mar 08, 2016 at 11:21:32PM +0100, Dominik George wrote:
> In that case, please let us finalise the work ;). I expect it to be done
> until
> middle of the week.
Sounds good. My favourite way to do this would be to clone
https://anonscm.debian.org/git/collab-maint/xrdp.git
to the
Hi,
>
> On Tue, Mar 08, 2016 at 06:59:32PM +0100, Dominik George wrote:
> > most of your concerns are being addressed already (restoring history and
> > such).
> The current master branch of the repository you named[1] starts with
>
>
> xrdp (0.9.0~git20150318-1~alpha1) teckids; urgency=medium
Hi,
On Tue, Mar 08, 2016 at 06:59:32PM +0100, Dominik George wrote:
> most of your concerns are being addressed already (restoring history and
> such).
The current master branch of the repository you named[1] starts with
xrdp (0.9.0~git20150318-1~alpha1) teckids; urgency=medium
* New
Hi,
most of your concerns are being addressed already (restoring history and such).
Please do not make it more difficult, an experienced DD (Mike Gabriel) is
working with us.
> 3. Why do you plan
> a) a non-official (random?) Git commit rather than a release?
Because there is no current
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will
[Setting reply-to Debian-Edu]
On Tue, Mar 08, 2016 at 06:29:12PM +0100, Dominik George wrote:
> >If anybody of the people responding tp the ITA bug like to become the
> >main maintainer of the package I'd be more than happy to sponsor the
> >package. As far as the situation is now I'll upload my
60 matches
Mail list logo
