Bug#821802: [lokalize/Applications/16.04] cmake: support hunspell 1.4 in cmake

2016-04-25 Thread Rene Engelhard
Hi,

On Mon, Apr 25, 2016 at 12:42:48AM +, Nick Shaforostoff wrote:
> Git commit 7aa9dafeb457ca3bc48a61c5dfa2e69b0ecdad6c by Nick Shaforostoff.
> Committed on 25/04/2016 at 00:42.
> Pushed by shaforo into branch 'Applications/16.04'.
> 
> support hunspell 1.4 in cmake
> 
> CCMAIL: 821...@bugs.debian.org
> 
> M  +1-1cmake/FindHUNSPELL.cmake
> 
> http://commits.kde.org/lokalize/7aa9dafeb457ca3bc48a61c5dfa2e69b0ecdad6c
> 
> diff --git a/cmake/FindHUNSPELL.cmake b/cmake/FindHUNSPELL.cmake
> index 26942b5..eca3cc1 100644
> --- a/cmake/FindHUNSPELL.cmake
> +++ b/cmake/FindHUNSPELL.cmake
> @@ -14,7 +14,7 @@ ENDIF (HUNSPELL_INCLUDE_DIR AND HUNSPELL_LIBRARIES)
>  
>  FIND_PATH(HUNSPELL_INCLUDE_DIR hunspell/hunspell.hxx )
>  
> -FIND_LIBRARY(HUNSPELL_LIBRARIES NAMES hunspell-1.3 hunspell-1.2)
> +FIND_LIBRARY(HUNSPELL_LIBRARIES NAMES hunspell-2.0 hunspell-1.5 hunspell-1.4 
> hunspell-1.3 hunspell-1.2)
^^

Where do you invent these? :)

(And as I said in the bug: why is it not using pkg-config (hunspell.pc) which
is version-agnostic and doesn't break if the SONAME is bumped without
API breakage?)

Regards,

Rene



Bug#821802: [lokalize/Applications/16.04] cmake: support hunspell 1.4 in cmake

2016-04-25 Thread Rene Engelhard
Hi,

On Mon, Apr 25, 2016 at 10:59:58AM +0200, Rene Engelhard wrote:
> On Mon, Apr 25, 2016 at 12:42:48AM +, Nick Shaforostoff wrote:
> > Git commit 7aa9dafeb457ca3bc48a61c5dfa2e69b0ecdad6c by Nick Shaforostoff.
> > Committed on 25/04/2016 at 00:42.
> > Pushed by shaforo into branch 'Applications/16.04'.
> > 
> > support hunspell 1.4 in cmake
> > 
> > CCMAIL: 821...@bugs.debian.org
> > 
> > M  +1-1cmake/FindHUNSPELL.cmake
> > 
> > http://commits.kde.org/lokalize/7aa9dafeb457ca3bc48a61c5dfa2e69b0ecdad6c
> > 
> > diff --git a/cmake/FindHUNSPELL.cmake b/cmake/FindHUNSPELL.cmake
> > index 26942b5..eca3cc1 100644
> > --- a/cmake/FindHUNSPELL.cmake
> > +++ b/cmake/FindHUNSPELL.cmake
> > @@ -14,7 +14,7 @@ ENDIF (HUNSPELL_INCLUDE_DIR AND HUNSPELL_LIBRARIES)
> >  
> >  FIND_PATH(HUNSPELL_INCLUDE_DIR hunspell/hunspell.hxx )
> >  
> > -FIND_LIBRARY(HUNSPELL_LIBRARIES NAMES hunspell-1.3 hunspell-1.2)
> > +FIND_LIBRARY(HUNSPELL_LIBRARIES NAMES hunspell-2.0 hunspell-1.5 
> > hunspell-1.4 hunspell-1.3 hunspell-1.2)
> ^^
> 
> Where do you invent these? :)

Ah, I see 
https://github.com/hunspell/hunspell/commit/ad5c19e3bab27167e9f7ecb0c05f61678e7e4930#diff-eb785e299ea6147029b02572abefea1d.

That still doesn't explain hunspell-2.0, though :)

Regards,

Rene



Processed: retitle 821802 to FTBFS with hunspell 1.4+

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 821802 FTBFS with hunspell 1.4+
Bug #821802 [lokalize] lokalize: FTBFS with (upcoming) hunspell 1.4
Changed Bug title to 'FTBFS with hunspell 1.4+' from 'lokalize: FTBFS with 
(upcoming) hunspell 1.4'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
821802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: tagging 821802, tagging 821802

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 821802 + upstream
Bug #821802 [lokalize] FTBFS with hunspell 1.4+
Added tag(s) upstream.
> tags 821802 + fixed-upstream
Bug #821802 [lokalize] FTBFS with hunspell 1.4+
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
821802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#821800: Removed package(s) from unstable

2016-04-25 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  gwenview | 4:4.14.2-1 | hurd-i386
gwenview-dbg | 4:4.14.2-1 | hurd-i386

--- Reason ---
RoQA; new build-dependency not available on hurd-i386
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 821...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/821800

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)



Bug#822243: Removed package(s) from unstable

2016-04-25 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 braindump | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
  calligra | 1:2.8.5+dfsg-1.2 | all
calligra-data | 1:2.8.5+dfsg-1.2 | all
calligra-dbg | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
calligra-libs | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
calligra-reports-map-element | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, 
i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
calligra-reports-web-element | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, 
i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
calligra-semanticitems | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
calligraactive | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
calligraauthor | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
calligraflow | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
calligraflow-data | 1:2.8.5+dfsg-1.2 | all
calligraplan | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
calligrasheets | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
calligrastage | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
calligrastage-data | 1:2.8.5+dfsg-1.2 | all
calligrawords | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
calligrawords-data | 1:2.8.5+dfsg-1.2 | all
karbon | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
  kexi | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
kexi-calligrasheets-driver | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, 
i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
 kexi-data | 1:2.8.5+dfsg-1.2 | all
kexi-map-form-widget | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
kexi-mysql-driver | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
kexi-postgresql-driver | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
kexi-sybase-driver | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
kexi-web-form-widget | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
kexi-xbase-driver | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
 krita | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
krita-data | 1:2.8.5+dfsg-1.2 | all
krita-gemini | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
krita-sketch | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
okular-backend-odp | 1:2.8.5+dfsg-1.2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x

--- Reason ---
ROM; RC-buggy; FTBFS; block NBS removals
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs 

Bug#822623: sddm session script should load ~/.Xmodmap if present

2016-04-25 Thread Stephen Crowley
Package: sddm
Version: 0.13.0-1
Severity: important

Just add this line to

/usr/share/sddm/scripts/Xsession

before the session is started

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

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

Versions of packages sddm depends on:
ii  adduser 3.114
ii  debconf [debconf-2.0]   1.5.59
ii  libc6   2.22-6
ii  libgcc1 1:5.3.1-14
ii  libpam0g1.1.8-3.2
ii  libqt5core5a5.5.1+dfsg-16+b1
ii  libqt5dbus5 5.5.1+dfsg-16+b1
ii  libqt5gui5  5.5.1+dfsg-16+b1
ii  libqt5network5  5.5.1+dfsg-16+b1
ii  libqt5qml5  5.5.1-3
ii  libqt5quick55.5.1-3
ii  libstdc++6  5.3.1-14
ii  libsystemd0 229-4
ii  libxcb-xkb1 1.11.1-1
ii  libxcb1 1.11.1-1
ii  qml-module-qtquick2 5.5.1-3
ii  sddm-theme-breeze [sddm-theme]  4:5.4.3-2

Versions of packages sddm recommends:
ii  libpam-systemd  229-4

Versions of packages sddm suggests:
ii  libpam-kwallet5  5.4.3-1

-- debconf information:
* shared/default-x-display-manager: sddm
  sddm/daemon_name: /usr/bin/sddm

--
This message is intended only for the use of the individual or entity to which 
it is addressed and may contain information which is privileged, confidential 
or subject to copyright. Internet communications cannot be guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
arrive late or contain viruses. The information contained in this e-mail is 
drawn from sources believed to be reliable, but the accuracy and completeness 
of the information is not guaranteed, nor in providing it does Canaccord 
Genuity Corp. or its subsidiaries, or affiliated companies, "The Firm" assume 
any liability. 

Canaccord Genuity Corp., its subsidiaries or affiliated companies, disclaims 
all responsibility and accepts no liability (including negligence) for the 
consequences for any person acting, or refraining from acting, on such 
information. Unless otherwise stated, this transmission is neither an offer nor 
the solicitation of an offer to sell or purchase any investment. As a 
solicitation, this e-mail was intended for distribution in those jurisdictions 
where The Firm is registered as advisors or dealers in securities. Any 
unauthorized use, disclosure, distribution or copying of this communication by 
anyone other than the intended recipient is strictly prohibited. 

When addressed to our clients, any opinions or advice contained in this email 
are subject to the terms and conditions expressed in the governing Canaccord 
Genuity Corp., its subsidiaries or affiliated companies' client agreements.  If 
you have received this message in error, please notify us immediately by return 
email and destroy and delete the message from your computer.  (Disclaimer)
--- /usr/share/sddm/scripts/Xsession~	2015-11-04 14:41:36.0 -0600
+++ /usr/share/sddm/scripts/Xsession	2016-04-25 13:48:31.272552070 -0500
@@ -84,6 +84,7 @@
   xrdb -merge /etc/X11/Xresources
 fi
 [ -f $HOME/.Xresources ] && xrdb -merge $HOME/.Xresources
+[ -f $HOME/.Xmodmap ] && xmodmap ~/.Xmodmap
 
 case $session in
   "")


Bug#822429: Acknowledgement (plasma-nm: Upstream Bug 362141: Connection editor fails with "connection.gateway-ping-timeout: can not set property: value")

2016-04-25 Thread J Mo
Note that a workaround is to use the ncurses "nmtui" command line tool, 
or the Gnome Network Connections tool (apt-get install 
network-manager-gnome).
It may be necessary to manually restart network manager after using 
these tools (sudo systemctl restart NetworkManager.service), as I found 
they saved the configuration changes but did not implement them.


I have found the KDE Connection Editor in it's current state to be 
completely unusable.