[pkg-x2go-devel] Fixing of x2goclient in Debian wheezy

[Mike Gabriel]

Hi X2Go Packagers, hi Lisandro (Mike's sponsor),

first I want to introduce Lisandro Perez Meyer as my pseudo-permanent   
sponsor to the X2Go Packaging Team (for those who do not know him). I   
will include him in all communications that are relevant for Mike   
packaging stuff for Debian. Lisandro say that sponsorship is   
pseudo-permanent, as his intention is to get rid of me once I know all  
  the stuff he thinks I need to know ;-).

Then a request for feedback to the X2Go pkg team on x2goclient for wheezy:

I--in the role of upstream--am thinking about releasing x2goclient   
3.99.2.2 during the next week (in coordination with Alex). The new   
upstream releases fixes two DebBTS issues currently open:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682839
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682852

Upstream commit for BTS issue #682839:
http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=5e5eb0cfffc514ee419a116a78f25ff98728c746

Upstream commit for BTS issue #682852:
http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=3335fca16afaa0792207228115e31630894dee71

Most of the other commits two upstream are acceptances of current   
Debian patches against x2goclient 3.99.2.1:
http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=647ab75f420637994b0cc400590adedd106e0c28
http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=c688541a6ef4477d3eb9eb28ca71e13a781cc69f
http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=67c1fa932ae66dcf288d99c12dcd57ea57779906
http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=9667c4ffcf9c906a230991682a0f1a5d35a9c794

There is only one commit that is not documented by a Debian bug   
(reason is that I do not know what Alex has been fixed with that   
commit):
http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=d4d0fe38610d3e514dc2e4e259ce8f103e4ac535

My questions:

1. Alex, can you explain what you exactly fixed with commit d4d0fe38?
2. Alex, can you send this explanation to submit at bugs.debian.org? Or   
otherwise, provide me with a bug description so that I can send it?
3. For acceptance of a new x2goclient upload to Debian would it make   
more sense patching in even more patches against 3.99.2.1 or do people  
  think we should upload 3.99.2.2, reduce the patch stack in the  
package  and convince the Debian release team that the upstream  
release is  better then dumping more patches into 3.99.2.1?

Wondering about the best strategy?
Mike (who has been trying to get past the release team several times   
during the last weeks)

-- 

DAS-NETZWERKTEAM
mike gabriel, rothenstein 5, 24214 neudorf-bornstein
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel at das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.alioth.debian.org/pipermail/pkg-x2go-devel/attachments/20120728/486e5bf2/attachment.pgp>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.alioth.debian.org/pipermail/pkg-x2go-devel/attachments/20120728/486e5bf2/attachment-0001.pgp>