Bug#488934: [SRM] stable upload for licq?

2008-07-15 Thread Philipp Kern
On Mon, Jul 14, 2008 at 11:44:33PM +0200, Frank Lichtenheld wrote:
 licq in stable is currently unusable due to server-side changes (see bug
 #488934). The patch is trivial and I have confirmed that it applies to
 the stable version and works.
 
 The question now is where to upload to?
 Is this ok for a stable point release? Or should this go into volatile
 instead?

I don't think licq is that volatile, at least judging from history.  But
currently the version in stable is broken, and thus warrants an upload
to stable-proposed-updates.  So please go ahead and upload to
ftp-master.

Kind regards,
Philipp Kern
-- 
 .''`.  Philipp Kern Debian Developer
: :' :  http://philkern.de   Debian Release Assistant
`. `'   xmpp:[EMAIL PROTECTED]
  `-finger pkern/[EMAIL PROTECTED]


signature.asc
Description: Digital signature


Bug#488934: [SRM] stable upload for licq?

2008-07-15 Thread Frank Lichtenheld
On Tue, Jul 15, 2008 at 12:23:50PM +0200, Philipp Kern wrote:
 On Mon, Jul 14, 2008 at 11:44:33PM +0200, Frank Lichtenheld wrote:
  licq in stable is currently unusable due to server-side changes (see bug
  #488934). The patch is trivial and I have confirmed that it applies to
  the stable version and works.
  
  The question now is where to upload to?
  Is this ok for a stable point release? Or should this go into volatile
  instead?
 
 I don't think licq is that volatile, at least judging from history.  But
 currently the version in stable is broken, and thus warrants an upload
 to stable-proposed-updates.  So please go ahead and upload to
 ftp-master.

Done

Gruesse,
-- 
Frank Lichtenheld [EMAIL PROTECTED]
www: http://www.djpig.de/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#488934: [SRM] stable upload for licq?

2008-07-14 Thread Frank Lichtenheld
licq in stable is currently unusable due to server-side changes (see bug
#488934). The patch is trivial and I have confirmed that it applies to
the stable version and works.

The question now is where to upload to?
Is this ok for a stable point release? Or should this go into volatile
instead?

For reference the debdiff I tested with:
diff -u licq-1.3.4/debian/control licq-1.3.4/debian/control
--- licq-1.3.4/debian/control
+++ licq-1.3.4/debian/control
@@ -2,7 +2,7 @@
 Build-Depends: cdbs (= 0.4.37), debhelper (= 5), imagemagick, kdebase-data, 
kdelibs4-dev, libcdk5-dev, libgpgme11-dev (= 0.4.2), libncurses5-dev, 
libqt3-mt-dev, libssl-dev, libxosd-dev (= 2.1.0), libxss-dev
 Section: net
 Priority: optional
-Maintainer: Peter Eisentraut [EMAIL PROTECTED]
+Maintainer: Debian QA Group [EMAIL PROTECTED]
 Standards-Version: 3.7.2
 
 Package: licq
diff -u licq-1.3.4/debian/changelog licq-1.3.4/debian/changelog
--- licq-1.3.4/debian/changelog
+++ licq-1.3.4/debian/changelog
@@ -1,3 +1,11 @@
+licq (1.3.4-2etch1) stable; urgency=low
+
+  * QA upload
++ change maintainer to QA group
+  * Fixing ICQ version too old problem (Closes: #47, #488934)
+
+ -- Frank Lichtenheld [EMAIL PROTECTED]  Mon, 14 Jul 2008 14:34:05 +0200
+
 licq (1.3.4-2) unstable; urgency=low
 
   * licq-plugin-qt replaces a file from the old licq package
only in patch2:
unchanged:
--- licq-1.3.4.orig/debian/patches/40_ICQ_version_too_old.patch
+++ licq-1.3.4/debian/patches/40_ICQ_version_too_old.patch
@@ -0,0 +1,12 @@
+diff -urNad licq-1.3.5~/src/icqpacket.cpp licq-1.3.5/src/icqpacket.cpp
+--- licq-1.3.5~/src/icqpacket.cpp  2007-09-28 22:11:35.0 +0200
 licq-1.3.5/src/icqpacket.cpp   2008-07-02 09:47:49.0 +0200
+@@ -821,7 +821,7 @@
+ 
+   // Static versioning
+   buffer-PackUnsignedLongBE(0x00160002);
+-  buffer-PackUnsignedShortBE(0x010A);
++  buffer-PackUnsignedShortBE(0x010B);
+   // Client version major (4 == ICQ2000, 5 == ICQ2001)
+   buffer-PackUnsignedLongBE(0x00170002);
+   buffer-PackUnsignedShortBE(0x0014);


Gruesse,
-- 
Frank Lichtenheld [EMAIL PROTECTED]
www: http://www.djpig.de/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]