[Pkg-kde-extras] Bug#562944: kmymoney depends on libkleo

[Lisandro Damián Nicanor Pérez Meyer]

On Tuesday 29 December 2009 15:54:08 Thomas McGuire wrote:
[snip]
 KMyMoney is our first external user, so the situation
  is not ideal anymore.

Actually, kopete-criptography suffers the same problem (except that has 
changed recently, last version I checked was 1.3.0), that's why it is not 
packaged in Debian.

Regards, Lisandro.

-- 
Quote me as saying I was mis-quoted.
 -- Groucho Marx

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/



___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#628736: Unreproducible

[Lisandro Damián Nicanor Pérez Meyer]

tag 628736 unreproducible moreinfo
thanks

Hi! I am running Sid in my boxes and I can't see the bug.

*Maybe* It's an old dbus installation, check the following line:

Connecting todeprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

Also, look at this:

kbuildsycoca4(7941) KConfigGroup::readXdgListEntry: List entry x-scheme-
handler/file in /home/alex/.local/share/applications/mimeapps.list is not
compliant with XDG standard (missing trailing semicolon).
  kbuildsycoca4(7941) KConfigGroup::readXdgListEntry: List entry x-scheme-
handler/Trash in /home/alex/.local/share/applications/mimeapps.list is not
compliant with XDG standard (missing trailing semicolon).

You can try renaming /home/alex/.local/share/applications/mimeapps.list 
(preferably without KDE started) and trying again. Or you acn fix the trailing 
semicolons :)

Regards, Lisandro.

-- 
Compartir las cosas buenas es una necesidad fácil de satisfacer. Compartir las
cosas malas es una necesidad mayor, pero mucho mas difícil de satisfacer. Sin
embargo, es el compartir las cosas malas lo que mas nos une como hermanos.
  Lisandro Damián Nicanor Pérez Meyer

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#597212: Moreinfo

[Lisandro Damián Nicanor Pérez Meyer]

tag 597212 moreinfo
thanks

Hi! Can you still reproduce the bug with the new version available in Sid?

Kinds regards, Lisandro.

-- 
La vida no se mide por la cantidad de veces que respiramos,
sino por la cantidad de momentos que nos quitan la respiración.
  Anónimo

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#574546: More info

[Lisandro Damián Nicanor Pérez Meyer]

tag 574546 moreinfo
thanks

Hi! I am currently using 4:4.6.1-1 and I can't reproduce this bug. Can you 
still reproduce it?

Kinds regards, Lisandro.

-- 
Bebe a bordo (pero con moderación)

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#563609: More info needed

[Lisandro Damián Nicanor Pérez Meyer]

tag 563609
thanks

Hi! The bug you reported seems already fixed. Can you please check it with the 
latest version?

Kinds regards, Lisandro.

-- 
 __
 ¿Nunca viste a una vaca hablar? 
 --
\   ^__^
 \  (oo)\___
(__)\   )\/\
||w |
|| ||

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#605134: More info needed

[Lisandro Damián Nicanor Pérez Meyer]

tag 605134 unreproducible
thanks

Hi! Can you still reproduce this bug with the current version in Sid?

Kinds regards, Lisandro.

-- 
El futuro es WIN95 A no ser que hagamos algo a tiempo.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#628736: More info.

[Lisandro Damián Nicanor Pérez Meyer]

tag 628736 moreinfo
thanks

Indeed, it's not kile's problem.

 the caps lock and scroll lock lights flash.

As Pino just pointed me out, this is a clear sign of a kernel panic.

Now, is acx built from the package acx100-source or are you using ndiswrapper 
against the windows drivers?

In the first case, this bug should be asigned to acx100-source, in the second 
case, this bug should be closed as invalid, as it's not Debian supported 
software.

Kinds regards, Lisandro.

-- 
9: Que es el Explorador de Windows
* El tipo que le roba las ideas a MacOs
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#658624: (no subject)

[Lisandro Damián Nicanor Pérez Meyer]

tag 658624 upstream
thanks

Hi! This is an upstream bug which I think the cause of the problem has been 
found.

I can't find the correct bug url now :-/

-- 
Esperando confirmación de ingredientes necesarios
que serán expuestos a la radiación...
  Manera geek de expresar que se espera la compra
  de carne para un típico asado argentino.
  Silvio Rikemberg.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#658624: forwarded upstream

[Lisandro Damián Nicanor Pérez Meyer]

forwarded 658624 https://bugs.kde.org/show_bug.cgi?id=268267
thanks

I'm not coupling this bug with #655332: Seems to export private symbols as 
some people reported [0] that regenerating digikam's config files they can get 
to retieve files from the camera again.

I have to do this in a few hours, so I'll take a look at it.

[0] https://bugs.kde.org/show_bug.cgi?id=268267#c96

Kinds regards, Lisandro.

-- 
Some consider UNIX to be the second most important invention to come out
of ATT Bell Labs after the transistor.
  Dennis Ritchie, creator of the C programming language and co-creator of UNIX
  http://www.linfo.org/q_unix.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#661419: Bug#661419: krusader: Crash at start with 'floating point exception' after update

[Lisandro Damián Nicanor Pérez Meyer]

tag 661419 unreproducible
thanks

On Dom 26 Feb 2012 22:51:17 George Shuklin escribió:
 Package: krusader
 Version: 1:2.4.0~beta1+git76+de1ea35-1
 Severity: grave
 Justification: renders package unusable
 
 After update krusader crash with 'floater pointer exception'.
 
 Data from crashlog:

Well, I can't reproduce this bug. I should ask you to install libqt4-dbg to 
get the debugging symbols for the backtrace... but bug #657637 is blocking me 
from doing this :-/

Maybe #657637 should block this bug, but i'll leave that to Mark or Fabo.

Kinds regards, Lisandro.

-- 
Confucius say: He who play in root, eventually kill tree.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#568714: Xine backend does not exists anymore.

[Lisandro Damián Nicanor Pérez Meyer]

phonon-xine-backend does not exists anymore in the archive, so I guess this 
bug can be closed.

Kinds regards, Lisandro.
-- 
The vast majority of Slashdot readers use Firefox. “We only have 20
percent of our population on Internet Explorer,” he says. “It's exactly
flipped from the Internet as a whole.”
  Rob Malda, on an interview by David Kushner for IEEE Spectrum.
  http://www.spectrum.ieee.org/nov07/5639/3

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#658624: More info needed

[Lisandro Damián Nicanor Pérez Meyer]

tag 626058 moreinfo
tag 663137 moreinfo
tag 658624 moreinfo
thanks

Hi! With the upload of libdc1394-22 2.2.0-1 this may have been fixed.
Could you please check that this is the case?

Kinds regards, Lisandro.

-- 
La política es una actividad noble. Hay que revalorizarla, ejerciéndola con
vocación y una dedicación que exige testimonio, martirio, o sea, morir
por el bien común.
  Padre Bergoglio - http://www.lanacion.com.ar/1153085

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#685411: unblock (pre-approval): k3b/2.0.2-6

[Lisandro Damián Nicanor Pérez Meyer]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi RT! I'm writing to ask for pre-approval of the inblock of k3b/2.0.2-6.
The changes are:

- Fix sox = 14.4.0 detection with fix-sox-detection-with-sox-14.4.0.patch,
 imported from upstream. This closes #675737
- Compress k3b-data and k3b-i18n with xz.
- Enable the lame-based MP3 encoding plugin:
- build depend on libmp3lame-dev
- install the new plugin (and its configuration) in libk3b6-extracodecs

I'm attaching the debdiff for this package.

Kinds regards, Lisandro.

unblock k3b/2.0.2-6

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru k3b-2.0.2/debian/changelog k3b-2.0.2/debian/changelog
--- k3b-2.0.2/debian/changelog	2012-06-01 07:30:15.0 -0300
+++ k3b-2.0.2/debian/changelog	2012-08-20 12:38:31.0 -0300
@@ -1,3 +1,17 @@
+k3b (2.0.2-6) unstable; urgency=low
+
+  * Team upload.
+
+  [ Pino Toscano ]
+  * Compress k3b-data and k3b-i18n as xz.
+  * Add fix-sox-detection-with-sox-14.4.0.patch (backported from upstream
+branch 2.0) to fix the detection of sox = 14.4. (Closes: #675737)
+  * Enable the lame-based MP3 encoding plugin:
+- build depend on libmp3lame-dev
+- install the new plugin (and its configuration) in libk3b6-extracodecs
+
+ -- Lisandro Damián Nicanor Pérez Meyer lisan...@debian.org  Mon, 20 Aug 2012 12:38:28 -0300
+
 k3b (2.0.2-5) unstable; urgency=low
 
   * Team upload.
diff -Nru k3b-2.0.2/debian/control k3b-2.0.2/debian/control
--- k3b-2.0.2/debian/control	2012-06-01 06:55:56.0 -0300
+++ k3b-2.0.2/debian/control	2012-08-20 11:54:27.0 -0300
@@ -7,7 +7,8 @@
  kdelibs5-dev (= 4:4.4.4), libavformat-dev, libdvdread-dev, libflac++-dev,
  libflac-dev, libkcddb-dev, libmad0-dev, libmpcdec-dev,
  libqtwebkit-dev, libsamplerate0-dev, libsndfile1-dev, libtag1-dev,
- shared-mime-info, libvorbis-dev, libcam-dev [kfreebsd-any]
+ shared-mime-info, libvorbis-dev, libcam-dev [kfreebsd-any],
+ libmp3lame-dev
 Standards-Version: 3.9.3
 Homepage: http://www.k3b.org
 Vcs-Svn: svn://svn.debian.org/pkg-kde/kde-extras/k3b/trunk/
diff -Nru k3b-2.0.2/debian/libk3b6-extracodecs.install k3b-2.0.2/debian/libk3b6-extracodecs.install
--- k3b-2.0.2/debian/libk3b6-extracodecs.install	2012-02-20 06:40:28.0 -0300
+++ k3b-2.0.2/debian/libk3b6-extracodecs.install	2012-08-20 11:54:27.0 -0300
@@ -1,3 +1,7 @@
 usr/lib/kde4/k3bffmpegdecoder.so
+usr/lib/kde4/k3blameencoder.so
 usr/lib/kde4/k3bmaddecoder.so
+usr/lib/kde4/kcm_k3blameencoder.so
 usr/lib/kde4/kio_videodvd.so
+usr/share/kde4/services/k3blameencoder.desktop
+usr/share/kde4/services/kcm_k3blameencoder.desktop
diff -Nru k3b-2.0.2/debian/patches/fix-sox-detection-with-sox-14.4.0.patch k3b-2.0.2/debian/patches/fix-sox-detection-with-sox-14.4.0.patch
--- k3b-2.0.2/debian/patches/fix-sox-detection-with-sox-14.4.0.patch	1969-12-31 21:00:00.0 -0300
+++ k3b-2.0.2/debian/patches/fix-sox-detection-with-sox-14.4.0.patch	2012-08-20 11:54:27.0 -0300
@@ -0,0 +1,32 @@
+From 2b672a2928d57b1132644ee4da1d6c664050bce1 Mon Sep 17 00:00:00 2001
+From: Pino Toscano p...@kde.org
+Date: Sun, 8 Jul 2012 22:20:15 +0200
+Subject: [PATCH] fix sox detection with sox = 14.4.0
+
+sox 1.14.0 changed the string that is printed out on --version, breaking the simply string matching done;
+add a new case to cover also this new version
+
+BUG: 301544
+
+(cherry picked from commit 79cd49cac3a6b7031556aae53ce3ecff8c360cb9)
+---
+ plugins/encoder/sox/k3bsoxencoder.cpp |3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/plugins/encoder/sox/k3bsoxencoder.cpp b/plugins/encoder/sox/k3bsoxencoder.cpp
+index 62d2bcd..72a3dc0 100644
+--- a/plugins/encoder/sox/k3bsoxencoder.cpp
 b/plugins/encoder/sox/k3bsoxencoder.cpp
+@@ -69,6 +69,9 @@ public:
+ if ( pos = 0 ) {
+ pos += 17;
+ }
++else if ( ( pos = out.indexOf( sox:  SoX v ) ) = 0 ) {
++pos += 15;
++}
+ else if ( ( pos = out.indexOf( sox: SoX v ) ) = 0 ) {
+ pos += 10;
+ }
+-- 
+1.7.10.4
+
diff -Nru k3b-2.0.2/debian/patches/series k3b-2.0.2/debian/patches/series
--- k3b-2.0.2/debian/patches/series	2012-02-20 08:19:33.0 -0300
+++ k3b-2.0.2/debian/patches/series	2012-08-20 11:54:27.0 -0300
@@ -8,3 +8,4 @@
 114_bug587996_bdr_capacity_fix.diff
 k3bscsicommand_bsd-Do-not-access-the-scsi_sense_data.patch
 k3bsetup-put-the-shebang-in-the-first-line.patch
+fix-sox-detection-with-sox-14.4.0.patch
diff -Nru k3b-2.0.2/debian/rules k3b-2.0.2/debian/rules
--- k3b-2.0.2/debian/rules	2012-06-01 07:24:41.0 -0300
+++ k3b-2.0.2

Re: [Pkg-kde-extras] too small an issue to open a ticker: typo in krecipes nutritional information

[Lisandro Damián Nicanor Pérez Meyer]

On Thu 18 Oct 2012 05:51:48 Lothar escribió:
 View recipe, look under properties:
 calcuim: 0.3mg
 Correct would be Calcium
 http://scarydevilmonastery.net/snap/1350549945749517025d.png

Even so it deserves a bug report upstream.

Kinds regards, Lisandro.

-- 
I still maintain the point that designing a monolithic kernel in 1991 is a
fundamental error.  Be thankful you are not my student.  You would not get a
high grade for such a design :-)
(Andrew Tanenbaum to Linus Torvalds)

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#705642: Bug#705642: k3b: Please say when there is not enough room on the disk

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 upstream
thanks

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following instructions
to report a new bug.

Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs and therefore it is unlikely that
your bug will be solved if you do not report it to KDE developers
directly (unless it is/has been reported by somebody else).

Whenever you open a bug report on the KDE bug tracking system, or 
you find that the bug has been already reported on it, you can couple 
both this Debian bug and the KDE bug together by sending a mail with 
the text below to cont...@bugs.debian.org (replace KDE-BUG-URL with 
the address of the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 705642 KDE-BUG-URL
  
thanks  

 
[ copy this ]   

 


 
Thank you,
-- 
LINUX KERNEL LIBERADO
DOS SECUESTRADORES MICROSOFTIANOS CAPTURADOS
OTRO SIGUE PROFUGO
*musiquita de cronica TV*

Ok, ok, ya me voy a hacer algo util, no me peguen :D

  Matias Angasule D'Ambrosio,
  sobre la liberación del kernel 2.6.23
  http://linux.org.ar/pipermail/bblug/2007-October/005405.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#713828: Bug#713828: basket: Basket crashes at the start

[Lisandro Damián Nicanor Pérez Meyer]

On Monday 24 June 2013 00:25:10 Luigi Toscano wrote:
 tags 713828 moreinfo
 
 thanks
 
 Prekates Alexandros wrote:
  After 'enter' the basket window will appear and then it crashes:
 I tried to install it on a:
 - wheezy/i386 system, upgraded from squeeze
 - wheezy/amd64 system
 both

I guess here is missing the final are working OK.

:)

-- 

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#713828:

[Lisandro Damián Nicanor Pérez Meyer]

tag 713828 moreinfo
thanks

On Saturday 29 June 2013 07:54:36 Πρεκατές Αλέξανδρος wrote:
 Basket starts with sudo! Also my system wheezy after a dist-upgrade in which
 i have many issues and aptitude remove many packages that i had to
 reinstall . Basket is one of them.
 No i wasnt able to start it even once (with the sudo exception that's
 working).
 Also i have very slow other KDE apps , like kmail, fileligth . (i mean a pop
 up dialog takes 1 minute to pop up!)

Hi! Please send us the output of running /sbin/ifconfig

I suspect you are missing the lo interface, and this bug is just a consequence 
of that.

Kinds regards, Lisandro.


-- 
The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself.  Therefore all
progress depends on the unreasonable man.
  George Bernard Shaw

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#716751: Bug#716751: telepathy-logger-qt: FTBFS on most arches due to broken symbols file

[Lisandro Damián Nicanor Pérez Meyer]

On Friday 12 July 2013 16:36:43 Roland Stigge wrote:
 On 07/12/2013 04:28 PM, Lisandro Damián Nicanor Pérez Meyer wrote:
  telepathy-logger-qt FTBFS on many arches, including armel, armhf,
  
  i386, kfreebsd-i386, mips, mipsel, powerpcand s390:
  Yes, those are symbols issues which we maintainers are aware. You
  have to live with that until we are able to get all the symbols,
  process them and re upload the package.
 
 OK!
 
 When you are doing it platform specific, can you please take into
 account powerpcspe at debian-ports.org also:
 
 http://buildd.debian-ports.org/status/package.php?p=telepathy-logger-qt

We do it by default.

Please don't use -quiet for packages maintained by this team, the rest of the 
team do not get a reply.

-- 

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

Re: [Pkg-kde-extras] Esperanto translations for KVIrc 4.2

[Lisandro Damián Nicanor Pérez Meyer]

On Thursday 29 August 2013 09:01:21 Sian Mountbatten wrote:
 Dear Team
 
 I have translated *all* the KVIrc messages into Esperanto. Where should
 I send them
 so that they can be incorporated in the next release of the program?

KVirc's upstream.

-- 
En los momentos de crisis, la imaginación es mas importante que el
conocimiento.
 Albert Einstein

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#725282: Bug#725282: kaffeine: DvbLinuxDevice::startDevice uses wrong device path

[Lisandro Damián Nicanor Pérez Meyer]

tag 725282 upstream
forwarded 725282 https://bugs.kde.org/show_bug.cgi?id=292138
thanks

On Thursday 03 October 2013 17:38:05 Alex Wilk wrote:
 Package: kaffeine
 Version: 1.2.2-2
 Severity: important
 
 Dear Maintainer,
 
 after an update kaffeine has the same problem as described at the following
 link: - https://bugs.kde.org/show_bug.cgi?id=292138
 
 % kaffeine
 kaffeine(15836) DvbLinuxDevice::startDevice: cannot open frontend
 dvb/adapter0/frontend0
 
 Also, the solution is the same as described (create a symbolic link from
 /dev/dvb in the current directory or change to the directory /dev).
 However, I do not know exactly what was updated in detail.

Then the problem is already reported upstream and must be solved there :)

Kinds regards, Lisandro.

-- 

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

Re: [Pkg-kde-extras] bespin package removed from testing: new upstream version (fix FTBFS #724180)

[Lisandro Damián Nicanor Pérez Meyer]

CCing Ritesh

On Saturday 02 November 2013 20:49:08 David Suárez wrote:
 Hi, I just updated the bespin package with the following changes:
 
 bespin (0.r1688-1) unstable; urgency=low
  .
* [Team upload]
  .
* New upstream release
* Switch to dpkg-source 3.0 (quilt) format (Closes: #724180)
* debian/rules: fix clean target
* debian/control:
   + update debhelper version
   + update standards version; no changes needed
   + use canonical URL for Vcs-Git field
* debian/copyright: fix license file
* Fix some spelling errors on upstream sources
* Use correct debian/install-* file for extras
* Do not install an additional copyright file
* Add debian/watch file
 
 May I simply ask for access on pkg-kde team and push to the git repository ?
 
 Or anyone will review the changes before pushing them ?

The maintainer of this package is Ritesh. He is the one who should review/ack  
this package.


-- 
firmaware: soft cuya licencia pagas enviando un autografo
  StucKman en #grulic, irc.freenode.net

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

Re: [Pkg-kde-extras] Bug#738712: Tracking source package renames

[Lisandro Damián Nicanor Pérez Meyer]

This should have gone to #738172 and not #738712 :)

/me wondered what pkg-kdeextras had to do with this :-P

On Wednesday 05 March 2014 17:07:31 Don Armstrong wrote:
 16:07:57 pabs dondelelcaro: does the BTS know about source package
 renaming? #738172 16:20:41 pabs ah, we discussed this before, I remember
 now
 16:29:49 dondelelcaro pabs: I've actually already got some code for it
 16:29:54 dondelelcaro pabs: but currently it doesn't
 16:32:00 dondelelcaro (it's actually not too terribly difficult; you just
 walk through the changelog) 16:51:55 pabs could you mail the bug about
 that?

-- 
7: Hay diferencia entre cortar un archivo y borrarlo o eliminarlo
* Depende cuando se cuelgue Windows
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#741361: Bug#741361: Please migrate to xine-lib-1.2

[Lisandro Damián Nicanor Pérez Meyer]

tag 741361 moreinfo
thanks

On Tuesday 11 March 2014 18:14:17 Moritz Muehlenhoff wrote:
 Source: kaffeine
 Severity: important
 
 Hi,
 xine-lib is scheduled for removal in jessie. Please build-depend on
 libxine2-dev instead of libxine-dev (a test compile worked fine for me)
 
 The severity will be bumped to RC status in a few weeks/months.

Hi Moritz! If libxine is going to be *removed*, can't you simply make libxine-
dev provide libxine2 stuff? In that way you will only need binNMUs for this 
packages. You normally add the soname to dev packages if you intend to provide 
more than one version at the time.

I'll wait for your reply before doing any change :)

Kinds regards, Lisandro.


-- 
I must confess, I was born at a very early age.
 -- Groucho Marx

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#741361: Bug#741361: Please migrate to xine-lib-1.2

[Lisandro Damián Nicanor Pérez Meyer]

tag 741361 moreinfo
thanks

On Tuesday 11 March 2014 18:14:17 Moritz Muehlenhoff wrote:
 Source: kaffeine
 Severity: important
 
 Hi,
 xine-lib is scheduled for removal in jessie. Please build-depend on
 libxine2-dev instead of libxine-dev (a test compile worked fine for me)
 
 The severity will be bumped to RC status in a few weeks/months.

Hi Moritz! If libxine is going to be *removed*, can't you simply make libxine-
dev provide libxine2 stuff? In that way you will only need binNMUs for this 
packages. You normally add the soname to dev packages if you intend to provide 
more than one version at the time.

I'll wait for your reply before doing any change :)

Kinds regards, Lisandro.


-- 
I must confess, I was born at a very early age.
 -- Groucho Marx

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#741361: Bug#741361: Bug#741361: Please migrate to xine-lib-1.2

[Lisandro Damián Nicanor Pérez Meyer]

On Wednesday 09 April 2014 23:05:16 Moritz Mühlenhoff wrote:
[snip]
 kaffeine is now the only package left (beside pyxine, which is filed for
 removal), so it would be nice if you could either fix this soon or give me
 the green light to fix it myself (this is indirectly holding the libav10
 transition)

Moritz: please go ahead :)

-- 
Passwords are like underwear. You shouldn’t leave them out where people can
see them. You should change them regularly. And you shouldn’t loan them out
to strangers.
  Anonymous

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#748603: Not serious

[Lisandro Damián Nicanor Pérez Meyer]

severity 748603 normal
thanks

Hi Franz! Thanks a lot for your feedback, but no, this is not a bug at all, 
it's just normal sid breakage when packages *got* uploaded but some of them 
need to pass trough the NEW queue [0] due to a binary changing it's name.

[0] http://ftp-master.debian.org/new.html

There is nothing here a maintainer can do to solve the situation but wait, as 
she has uploaded everything that's needed. So, no bug at all.

The package would be unsuitable for a release *if* the package is already in 
testing, but this is not the case.

I will keep the bug open just to mark this situation, but it should be closed 
with the same version it was opened with (or simply omitting the Version: 
pseudo-header), as this is just a normal situation.

Again, thanks a lot for you feedback non the less!

Kinds regards, Lisandro.

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#753591: FTBFS due to CMake error

[Lisandro Damián Nicanor Pérez Meyer]

Source: gammaray
Version: 2.0.2-1
Severity: serious

Gammaray is currently FTBFS due to #752847.

As a workaround you might want to add libegl1-mesa-dev as a build dependency.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#753591: Pending

[Lisandro Damián Nicanor Pérez Meyer]

tag 752847 pending
thanks

gammary and fcitx-qt5 maintainers: I'm about to upload the fix for your 
FTBFSs, I'll ask for a binNMu when ready.

-- 
2: Windows con las funciones que realiza se clasifica como:
* Un bug
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#754580: partitionmanager heads up

[Lisandro Damián Nicanor Pérez Meyer]

There seems to be some work done to push the new upstream release directly. A 
possible new maintainer is contacting Mark Purcell to get an ACK and upload 
it.

That's all I know :)

-- 
#exclude windows.h

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#763852: Preparing the upload that removes libqt4-private-dev

[Lisandro Damián Nicanor Pérez Meyer]

Hi! i would like to get this fixed in the next Qt4 upload which will surely 
happen next week.

I know the fix is already commited in the repo, is it possible to get this 
uploaded soon?

Thanks a lot!

Lisandro.


-- 
Lo que me sorprende de las mujeres es que se arrancan los pelos desde
la raíz con cera caliente y aún así le temen a las arañas.
  Jerry Seinfeld

lis: comentario sobre tu frase
yo soy mujer, yo me arranco los pelos y VOS le tenes miedo a las arañas
  María Luján Pérez Meyer (mi hermana)

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#786363: qapt: needs update for qt-gstreamer 1.2

[Lisandro Damián Nicanor Pérez Meyer]

unblock 760003 by 786363
severity 786363 normal
retitle 786363 Binaries should not be named after the gstreamer version
thanks

On Saturday 30 May 2015 12:10:14 Diane Trout wrote:
[snip]
 (I'm not sure if that means this bug should be closed and a new one opened,
 or this one should be downgraded and stop blocking 760003.)

Let's just remove the block and rename it accordingly.

qapt maintainers: the binary packages produced by qapt do not expose the 
gstreamer API, so they should not be marked with the gstreamer version they 
where linked against (except if you at some point want to make two available 
versions of the gstreamer backend, which I hardly doubt).

Moreover they are not public libraries but private ones, so they can be 
renamed accordingly (maybe even called plugin?)

Kinds regards, Lisandro.

-- 
UNIX is basically a simple operating system, but you have to be a
genius to understand the simplicity.
  Dennis Ritchie

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

Re: [Pkg-kde-extras] Bug#760003: transition: qt-gstreamer

[Lisandro Damián Nicanor Pérez Meyer]

On Thursday 28 May 2015 14:05:18 Lisandro Damián Nicanor Pérez Meyer wrote:
[snip]
  It won't hurt to upload the experimental version around the same time as
  kamoso though if you want to, since we'll have to wait for kamoso to age
  anyway.
 
 I'm afraid it's still not clear to me if you are referring to qapt (which
 seems to have built fine) or qtgstreamer :-/

I have just understood how the situation is. The bad news are that the 
experimental version can't be pushed to unstable until kf5 is in it, which 
means waiting for Qt 5.4.2... not a solution now.

**BUT** the good news are that qapt does not expose any gstreamer API, which 
means that even if the package names are deceptive they should just work as 
they already are. And that's why a simple binNMU just worked.

So I would just simply keep the version in sid as it is, we will push the 
newer version with proper naming with kf5.

Thanks a lot for your work!

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#763852: Raising severity

[Lisandro Damián Nicanor Pérez Meyer]

severity 763852 serious
thanks

Hi! The latest qt4 version has been released and I plan to push it to unstable 
quite soon.

I am raising the severity to serious directly from wishlist because we know 
the change is in pending state and I have also discussed the issue with Felix 
on IRC.

Thanks!

-- 
Theory and practice sometimes clash. And when that happens, theory loses.
Every single time.
  Linus Benedict Torvalds.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#793747: Please (after tomorrow 20150727) depend on konsole4-kpart instead of konsole.

[Lisandro Damián Nicanor Pérez Meyer]

Source: kile
Version: 4:2.1.3-2
Severity: important

Hi! As you might know KDE is switching to KF5/Qt5. Kile depends on konsole
in order to get it's kpart from it (in the KDE4 series they where in the
same package).

In the KF5 series konsole and it's kpart are spplitted, so we created a new
binary called konsole4-kpart to provide you with the aforementioned
dependency until kile itslef switches to KF5.

To avoid breaking stuff we made kf5's konsole to depend on both konsole4-kaprt
and konsole-kpart (kf5 based) until the rdeps fixes their dependencies.

I'm offering to do a team upload/NMU (as you prefer) in case you prefer me
doing the upload.

Thanks *a lot* for bringing us kile

-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

-- no debconf information

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#802949: FTBFS on mipsel during qtbase-5-5-1 transition

[Lisandro Damián Nicanor Pérez Meyer]

Source: gammaray
Version: gammaray
Severity: serious

Hi! While rebuilding gammaray fro the qtbase 5.5.1 private headers' transition
your package failed to build from source on mipsel.

The build was trying twice, both times failing during the tests.


Kinds regards, Lisandro.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'buildd-unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

-- no debconf information

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#784476: New upstream release available supporting Qt5

[Lisandro Damián Nicanor Pérez Meyer]

Hi! There is a new upstream release available which supports Qt5. I might do a 
team upload except you tell me otherwise. I will also probably push the 
packaging to git (again, if none of you maintainers tell me otherwise).

Kinds regards, Lisandro.



-- 
Los estadounidenses no tienen la culpa, la guerra tiene la culpa. La falta de
voluntad de la gente para comprender a aquellos que tienen valores diferentes,
eso es lo que tiene la culpa.
  Shinji Mikamo
  
<http://www.lanacion.com.ar/1716475-el-cataclismo-nuclear-de-hiroshima-narrado-por-un-superviviente>

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#799395: FTBFS: should depend on libsoprano-dev

[Lisandro Damián Nicanor Pérez Meyer]

Source: kile
Version: 4:2.1.3-2
Severity: serious
Tags: stretch sid
Justification: FTBFS due to missing dependency

Hi! kile currently FTBFS due to libsoprano-dev not being listed
in B-Ds.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'buildd-unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#784448: Bumping severity to normal

[Lisandro Damián Nicanor Pérez Meyer]

severity 784449 normal
severity 784448 normal
severity 784612 normal
severity 784450 normal
severity 784451 normal
severity 784452 normal
severity 784453 normal
severity 784454 normal
severity 784456 normal
severity 784455 normal
thanks

Hi! As we intend to go further with this removal we are bumping it's severity.
If you need help please do not hesitate in replying to the bug, I am 
subscribed to it.

-- 
Videogames do not influence kids. I mean, if Pac-Man influenced our
generation, we would all be jumping in dark rooms, chomping magic pills
and listening to electronic repeating music.
  Kristian Wilson, Nintendo Inc. 1989

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#784460: Bumping severity

[Lisandro Damián Nicanor Pérez Meyer]

severity 784457 normal
severity 784458 normal
severity 784459 normal
severity 784616 normal
severity 784460 normal
severity 784461 normal
severity 784462 normal
severity 784463 normal
severity 784464 normal
severity 784610 normal
thanks

Hi! As we intend to go further with this removal we are bumping it's severity.
If you need help please do not hesitate in replying to the bug, I am 
subscribed to it.


-- 
"So long, and thanks for all the fish!"
  The Hitchhickers guide to the Galaxy

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#784471: Bumping severities

[Lisandro Damián Nicanor Pérez Meyer]

severity 784468 normal
severity 784470 normal
severity 784471 normal
severity 784472 normal
severity 784473 normal
severity 784475 normal
severity 784476 normal
severity 784477 normal
severity 784479 normal
severity 784480 normal
thanks

Hi! As we intend to go further with this removal we are bumping it's severity.
If you need help please do not hesitate in replying to the bug, I am 
subscribed to it.

-- 
Alas, I am dying beyond my means.
  Oscar Wilde, as he sipped champagne on his deathbed

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#784490: Bumping severity

[Lisandro Damián Nicanor Pérez Meyer]

severity 784481 normal
severity 784483 normal
severity 784485 normal
severity 784484 normal
severity 784486 normal
severity 784487 normal
severity 784490 normal
severity 784491 normal
severity 784493 normal
severity 784496 normal
thanks

Hi! As we intend to go further with this removal we are bumping it's severity.
If you need help please do not hesitate in replying to the bug, I am 
subscribed to it.

-- 
For want of a nail, the shoe was lost;
For want of the shoe, the horse was lost;
For want of the horse, the rider was lost;
For want of the rider, the battle was lost;
For want of the battle, the kingdom was lost;
And all for the want of a horseshoe nail
  http://www.everything2.com/index.pl?node_id=1097943

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#784560: Bumping severities

[Lisandro Damián Nicanor Pérez Meyer]

severity 784510 normal
severity 784511 normal
severity 784512 normal
severity 784516 normal
severity 784518 normal
severity 784527 normal
severity 784529 normal
severity 784531 normal
severity 784559 normal
severity 784560 normal
thanks

Hi! As we intend to go further with this removal we are bumping it's severity.
If you need help please do not hesitate in replying to the bug, I am 
subscribed to it.

-- 
Wiki participants are, by nature, a pedantic, ornery, and unreasonable bunch.
So there's a camaraderie here we seldom see outside of our professional
contacts.
  http://www.c2.com/cgi/wiki?WhyWikiWorks

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#784524: Bumping severities

[Lisandro Damián Nicanor Pérez Meyer]

severity 784619 normal
severity 784513 normal
severity 784514 normal
severity 784522 normal
severity 784523 normal
severity 784524 normal
severity 784525 normal
severity 784613 normal
severity 784532 normal
severity 784618 normal
thanks

Hi! As we intend to go further with this removal we are bumping it's severity.
If you need help please do not hesitate in replying to the bug, I am 
subscribed to it.

-- 
This end should point toward the ground if you want to go to space.
If it starts pointing toward space you are having a bad problem
and you will not get to space today.
  http://xkcd.com/1133/

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#803456: Digikam 5.0.0 uploaded

[Lisandro Damián Nicanor Pérez Meyer]

On domingo, 10 de julio de 2016 2:01:04 P. M. ART Steve M. Robbins wrote:
> Hi,
> 
> I wanted to make people aware that I have uploaded Digikam 5.0.0 packages to
> Debian earlier today.

First of all: thanks a lot.
 
> I uploaded to experimental for staging for a few reasons:
> 
> 1. To work through the build issues on various architectures.
> 
> 2. The configuration files are in a new location, but digikam does no
> migration [1].  To the user, it appears you are starting from scratch and
> there is a risk of confusion -- the referenced bug is from someone who
> thought (mistakenly) that a migration procedure was required.  The bug also
> references possibly using a KF5 function KConfig::copyTo() to migrate the
> files, but then concludes that some digikam 4 settings cause digikam 5 to
> crash.  At this point, it seems that automatic migration is unsafe but that
> the initial configuration wizard should be augmented with text that
> describes the upgrade- from-4.x scenario better.  I'm seeking suggestions
> on what might be the best approach here.

I would for starters file an RC bug to the version in experimental so users 
know this before it gets installed (thanks to apt-listbugs). This would also 
make the bug more visible.

Then I guess it's either provide patches upstream or wait for a fix :-/

> 3. The showfoto internationalized docs are missing due to an upstream bug
> [2]. The bug is now patched upstream; however, the fix re-structures the
> source tarball so it is unclear whether this is easy to port into the
> current version; or better to wait for upstream 5.1.0 source tarball.

We still have time before the freeze, do you think a new upstream release will 
happen during this timeframe? Else it could be an upstream snapshot.

Thanks a lot Steve!


-- 
Those are my principles. If you don't like them I have others.
 -- Groucho Marx

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#842715: skrooge: FTBFS with Qt 5.7.1

[Lisandro Damián Nicanor Pérez Meyer]

I've noticed that even with that patch is not enough, so I'm trying to just 
use the latest release which Pino had almost ready. That version compiles 
fine, it just needs some package adjustments... hopefully :)

-- 
http://xkcd.com/150/
Personas como ésta no se encuentran todos los días. Y cuando uno las
encuentra, suelen no estar disponibles.
Si encontrás una, no la pierdas.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#842715: skrooge: FTBFS with Qt 5.7.1

[Lisandro Damián Nicanor Pérez Meyer]

Source: skrooge
Version: 2.4.0-2
Severity: important

Hi! Skrooge FTBFS with Qt 5.7.1. We are about to start the transition
to get 5.7.1 into testing.

The relevant build log part is:

/<>/skgbasemodeler/skgdocument.cpp: In member function 'virtual 
SKGDocument::SKGModelTemplateList SKGDocument::getDisplaySchemas(const 
QString&) const':
/<>/skgbasemodeler/skgdocument.cpp:2530:47: error: call of 
overloaded 'qAsConst(SKGStringListList&)' is ambiguous
 for (const auto& line : qAsConst(lines)) {
   ^
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:43:0,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:43,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qstringlist.h:41,
 from /<>/skgbasemodeler/skgdocument.h:24,
 from /<>/skgbasemodeler/skgdocument.cpp:22:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1130:58: note: candidate: 
constexpr typename QtPrivate::QAddConst::Type& qAsConst(T&) [with T = 
QList; typename QtPrivate::QAddConst::Type = const 
QList]
 Q_DECL_CONSTEXPR typename QtPrivate::QAddConst::Type (T ) 
Q_DECL_NOTHROW { return t; }
  ^~~~
In file included from /<>/skgbasemodeler/skgerror.h:28:0,
 from /<>/skgbasemodeler/skgservices.h:31,
 from /<>/skgbasemodeler/skgdocument.h:30,
 from /<>/skgbasemodeler/skgdocument.cpp:22:
/<>/skgbasemodeler/skgdefine.h:38:47: note: candidate: constexpr 
typename QAddConst::Type& qAsConst(T&) [with T = QList; 
typename QAddConst::Type = const QList]
 Q_DECL_CONSTEXPR typename QAddConst::Type& qAsConst(T& t) Q_DECL_NOTHROW { 
return t; }

It might be possible that this is not a Qt5-related bug, will try to rebuild 
against current 5.6 to check.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'buildd-unstable'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#842715: skrooge: FTBFS with Qt 5.7.1

[Lisandro Damián Nicanor Pérez Meyer]

tag 842715 confirmed patch
thanks

This patch solves the issue:

<https://quickgit.kde.org/?
p=skrooge.git=commit=1ac4c788019cb3eb6e8fbd2caccae881fe115e48>



-- 
This end should point toward the ground if you want to go to space.
If it starts pointing toward space you are having a bad problem
and you will not get to space today.
  http://xkcd.com/1133/

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

Re: [Pkg-kde-extras] [Pkg-xfce-devel] Bug#875029: [lightdm] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

On 15 September 2017 at 06:31, Ralf Jung <p...@ralfj.de> wrote:
> Hi,
[snip]
> lightdm-kde upstream seems entirely dead for 4 years now.  I won't do a
> port to Qt5.  So I guess what I should do is ask for lightm-kde to be
> removed from the repository.  Lisandro, can I wait with that until you
> really remove Qt4 or should I rather do this ASAP?

First of all, thanks you all for your replies.

Ideally they should get removed *before* qt4 itself, but there is no
need to rush. A good moment to consider asking for their removals is
whenever we set the bugs' severities to important, which won't happen
soon. On the other hand, knowing that you already stated that they can
be removed alongside Qt 4 itself I *will* ask for their removal citing
your replies whenever we get to remove Qt4. But again, the sooner the
better, as some other packages might be depending on yours (you won't
believe the amount of strange things you might find out when removing
packages...).

Thanks!

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874952: [keurocalc] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: keurocalc
Version: 1.2.3-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874993: [kraft] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kraft
Version: 0.59-1.1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874982: [krename] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: krename
Version: 4.0.9-4
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874978: [krecipes] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: krecipes
Version: 2.1.0-3
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874981: [komparator] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: komparator
Version: 4:1.0-3
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874962: [knights] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: knights
Version: 2.5.0-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874936: [kchmviewer] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kchmviewer
Version: 7.5-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874906: [hupnp] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: hupnp
Version: 1.0.0-1.1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874819: [audex] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: audex
Version: 0.79-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#875008: [libalkimia] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: libalkimia
Version: 5.0.0-3
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#875174: [robojournal] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: robojournal
Version: 0.5-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874825: [appmenu-qt] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: appmenu-qt
Version: 0.2.6-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874811: [amarok] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: amarok
Version: 2.8.0-8
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874977: [kradio4] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kradio4
Version: 4.0.8+git20170124-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874961: [kmymoney] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kmymoney
Version: 4.8.0-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#875035: [libqaccessibilityclient] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: libqaccessibilityclient
Version: 0.1.1-5
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#875030: [lightdm-kde] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: lightdm-kde
Version: 0.3.2.2-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874883: [gammaray] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: gammaray
Version: 2.0.2-1
2.3.0-3
2.6.0-1
2.7.0-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#875206: [telepathy-qt] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: telepathy-qt
Version: 0.9.6.1-6.1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#875208: [tora] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: tora
Version: 2.1.3-3
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#875239: [webkitkde] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: webkitkde
Version: 1.3.4-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874828: [bangarang] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: bangarang
Version: 2.1-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874988: [kscope] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kscope
Version: 1.9.4-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#875149: [qtcurve] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: qtcurve
Version: 1.8.18+git20160320-3d8622c-5
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#875147: [qt-gstreamer] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: qt-gstreamer
Version: 1.2.0-4
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#875003: [kvpnc] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kvpnc
Version: 0.9.6a-4
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874829: [basket] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: basket
Version: 2.10~beta+git20160425.b77687f-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874940: [kdesudo] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kdesudo
Version: 3.4.2.4-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874928: [kalternatives] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kalternatives
Version: 0.13-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874923: [k3b] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: k3b
Version: 2.0.3a-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874966: [kile] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kile
Version: 4:2.1.3-4
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874998: [kvirc] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kvirc
Version: 4:4.2.0-3
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874971: [kio-gopher] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kio-gopher
Version: 0.1.4-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#875187: [soundkonverter] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: soundkonverter
Version: 2.2.2-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#875315: QJson removal form Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: amarok
Version: 2.8.0-8
Severity: important
User: debian-qt-...@lists.debian.org
Usertags: qjson-removal

Hi! As you might know we the Qt/KDE team are preparing to remove Qt4.
This means that we need to remove QJson from the archive too.

In order to make this move, all packages directly or indirectly depending on
the QJson library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

Noreover porting from QJson to Qt5's QJson (part of the official API) tends to
be quite easy.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'buildd-unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages amarok-common depends on:
ii  perl  5.26.0-7

amarok-common recommends no packages.

Versions of packages amarok is related to:
ii  phonon-backend-gstreamer [phonon-backend]  4:4.9.0-1
ii  phonon-backend-vlc [phonon-backend]0.9.0-2

-- no debconf information

___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#874928: [kalternatives] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Hi! There seems to be work in progress, so please do no file the bug.

Thanks!

El 9 dic. 2017 12:51 a.m., "Boyuan Yang" <073p...@gmail.com> escribió:

> X-Debbugs-CC: p...@kde.org debian-qt-...@lists.debian.org
>
> 在 2017年11月28日星期二 CST 上午9:55:54，Boyuan Yang 写道：
> > X-Debbugs-CC: p...@kde.org debian-qt-...@lists.debian.org
> >
> > Hello all,
> >
> > I'm wondering about the future of package "kalternatives" in Debian. It
> has
> > not been updated for 7 years, now affected by Qt4 removal and I cannot
> find
> > the upstream VCS for it.
> >
> > Will there be any porting efforts? If yes, please let me know; if not, we
> > could consider submitting removal request to get this out of Debian
> > unstable.
> >
> > PS: I'm the current maintainer of package "galternatives" in Debian.
> >
> > Thanks,
> > Boyuan Yang
>
> Hello,
>
> Since there's no response, I'm going to file an RM bug for package
> kalternatives within one month.
>
> Please let me know if anyone is willing to work on it and port it to Qt5.
>
> Thanks,
> Boyuan Yang
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Action requested: migration of alioth list pkg-kde-extras

[Lisandro Damián Nicanor Pérez Meyer]

I'm hereby asking for pkg-kde-extras@l.a.d.o to be migrated.

As the current admin is not available and I don't seem able to add mmyself as 
an admin from the alioth web interface I'm CCing this mail to pkg-kde-
ext...@lists.alioth.debian.org to ensure transparency.

Thanks in advance, Lisandro.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

Re: [Pkg-kde-extras] Action requested: migration of alioth list pkg-kde-extras

[Lisandro Damián Nicanor Pérez Meyer]

El sábado, 24 de febrero de 2018 06:46:12 -03 Dominic Hargreaves escribió:
> On Tue, Feb 13, 2018 at 12:56:11PM -0300, Lisandro Damián Nicanor Pérez 
Meyer wrote:
> > I'm hereby asking for pkg-kde-extras@l.a.d.o to be migrated.
> > 
> > As the current admin is not available and I don't seem able to add mmyself
> > as an admin from the alioth web interface I'm CCing this mail to pkg-kde-
> > ext...@lists.alioth.debian.org to ensure transparency.
> 
> The list has now been marked to be migrated, and the new owner recorded
> in the absence of any objections.

**Thanks**


-- 
El futuro es WIN95 A no ser que hagamos algo a tiempo.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras