tags 616026 + patch
tags 616026 + pending
thanks

Dear maintainer,

I've prepared an NMU for quassel (versioned as 0.7.1-1.1) and
uploaded it to DELAYED/1.

Regards.
diff -Nru quassel-0.7.1/debian/changelog quassel-0.7.1/debian/changelog
--- quassel-0.7.1/debian/changelog      2010-09-21 23:24:55.000000000 +0300
+++ quassel-0.7.1/debian/changelog      2011-03-30 19:05:13.000000000 +0300
@@ -1,3 +1,12 @@
+quassel (0.7.1-1.1) unstable; urgency=low
+
+  * Non-maintainer upload with maintainer permission.
+  * Do not hardcode kdelibs5 and kdebase-runtime in quassel-client-kde4 and
+    quassel-kde4 Depends (Closes: #616026). kdelibs5 has been deprecated and
+    will be removed soon while kdebase-runtime is added via shlibs as needed.
+
+ -- Modestas Vainius <[email protected]>  Wed, 30 Mar 2011 18:59:12 +0300
+
 quassel (0.7.1-1) unstable; urgency=low
 
   * New upstream release
diff -Nru quassel-0.7.1/debian/control quassel-0.7.1/debian/control
--- quassel-0.7.1/debian/control        2010-09-21 22:13:47.000000000 +0300
+++ quassel-0.7.1/debian/control        2011-03-30 18:56:49.000000000 +0300
@@ -62,7 +62,7 @@
 
 Package: quassel-client-kde4
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, quassel-data-kde4 
(=${source:Version}), dbus-x11, kdebase-runtime, kdelibs5, gawk
+Depends: ${shlibs:Depends}, ${misc:Depends}, quassel-data-kde4 
(=${source:Version}), dbus-x11, gawk
 Conflicts: quassel-client
 Recommends: quassel-core
 Description: distributed IRC client - KDE-based client
@@ -75,7 +75,7 @@
 
 Package: quassel-kde4
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, libqt4-sql-sqlite, 
quassel-data-kde4 (= ${source:Version}), dbus-x11, kdebase-runtime, kdelibs5, 
gawk
+Depends: ${shlibs:Depends}, ${misc:Depends}, libqt4-sql-sqlite, 
quassel-data-kde4 (= ${source:Version}), dbus-x11, gawk
 Conflicts: quassel
 Description: distributed IRC client - KDE-based monolithic core+client
  Quassel is a modern, cross-platform, distributed IRC client, meaning that



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

Reply via email to