Hi,
Dmitry Smirnov only...@member.fsf.org writes:
Can someone check the solution please? Right now I have limited to to
do that...
http://xpra.org/trac/ticket/349#comment:2
Upstream is waiting for feedback before backporting to 0.9.x.
how do you build xpra from svn nowadays? Last time
On Wed, 5 Jun 2013 16:06:08 Timo Juhani Lindfors wrote:
how do you build xpra from svn nowadays? Last time I had to chown
/etc/xpra for my own user to be able to test it as normal user iirc.
Sorry I don't understand the question and the problem. We moved away
from SVN some time ago. Workflow
Hi,
Dmitry Smirnov only...@member.fsf.org writes:
Sorry I don't understand the question and the problem. We moved away
from SVN some time ago. Workflow is usual and simple:
extract upstream source,
I use git-svn to track upstream so I first tried
git archive --prefix=xpra-0.9.4+svn3586/ -o
Building Xpra from its SVN checkout is easy. Just add our debian/* to
his src directory or copy copy his debian/* to src before running
`debuild`.
Maybe I need to somehow port old-libav.patch to the new xpra svn trunk?
It patches x264lib.c which does not exist anymore in upstream source
tree
Dmitry Smirnov only...@member.fsf.org writes:
You might need to apply old-libav.patch if you using libav from
unstable. Our Debian package takes care of it automatically.
I think I now managed to forward-port old-libav.patch. Next failure is
creating
Timo Juhani Lindfors timo.lindf...@iki.fi writes:
I guess I'll just remove all entries from wimpiggy.install for now since
I'm only interested in xpra.
Next failure :)
dh_installdocs
cp: cannot stat 'xpra.README': No such file or directory
Then
dh_installdocs
cp: cannot stat
Can someone check the solution please? Right now I have limited to to
do that...
http://xpra.org/trac/ticket/349#comment:2
Upstream is waiting for feedback before backporting to 0.9.x.
Cheers,
Dmitry Smirnov
GPG key : 4096R/53968D1B
--
To UNSUBSCRIBE, email to
Package: xpra
Version: 0.9.4+dfsg-1
Severity: normal
Steps to reproduce:
1) xpra attach ssh:server.example.com:7
2) change resolution of the client machine to 640x480 temporarily
(e.g. in gnome System-Preferences-Monitors)
3) change the resolution back to normal
Expected results:
3) all parts
8 matches
Mail list logo
