Bug#827348: marked as done (qtscript-opensource-src FTBFS on Alpha; double value incorrect in last bit in test suite)

2017-02-25 Thread Debian Bug Tracking System
Your message dated Sun, 26 Feb 2017 13:19:32 +1300
with message-id <20170226001932.547252n7ktyrjylu@tower>
and subject line qtscript-opensource-src now builds on Alpha
has caused the Debian Bug report #827348,
regarding qtscript-opensource-src FTBFS on Alpha; double value incorrect in 
last bit in test suite
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
827348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtscript-opensource-src
Version: 5.6.1+dfsg-2
Severity: important
Justification: fails to build from source but built in past
Tags: patch
User: debian-al...@lists.debian.org
Usertags: alpha

qtscript-opensource-src FTBFS on Alpha due to a test suite failure [1]:

FAIL!  : tst_QScriptJsTestSuite::ecma_2/RegExp(/\B/.lastIndex) Compared values 
are not the same
   Actual   (actual): "1.7976931348623155e+308"
   Expected (expect): "1.7976931348623157e+308"
   Loc: [ecma_2/RegExp/properties-002.js(583)]

This is the result of a double precision calculation that has rounded
the last bit of the calculation in the wrong direction.  That does not
seem sufficient reason to completely fail the build so I attach a
patch that disables this test and hope you would consider including
it in the next upload of qtscript-opensource-src.

Cheers
Michael.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=qtscript-opensource-src&arch=alpha&ver=5.6.1%2Bdfsg-2&stamp=1465838369
Index: qtscript-opensource-src-5.6.1+dfsg/tests/auto/qscriptjstestsuite/skip.txt
===
--- qtscript-opensource-src-5.6.1+dfsg.orig/tests/auto/qscriptjstestsuite/skip.txt
+++ qtscript-opensource-src-5.6.1+dfsg/tests/auto/qscriptjstestsuite/skip.txt
@@ -7,6 +7,7 @@ regress-322135-03.js | takes forever
 regress-322135-04.js | takes forever
 ecma/Expressions/11.4.7-02.js | Fails on some architectures
 ecma/TypeConversion/9.3.1-3.js | Fails on some architectures
+ecma_2/RegExp/properties-002.js | Fails on Alpha
 ecma_3/Array/regress-387501.js | Produces wrong error message
 ecma_3/RegExp/regress-375715-04.js | bug
 ecma_3/RegExp/regress-289669.js | Can fail due to relying on wall-clock time
--- End Message ---
--- Begin Message ---
qtscript-opensource-src has been building on Alpha since version
5.6.1+dfsg-2.  I suspect the bug was actually a bug in glibc which
has been fixed in the meantime.  Closing this bug report.

Cheers
Michael.--- End Message ---


Re: Bug#856004: khtml: please build-depen on libssl1.0-dev for Stretch

2017-02-25 Thread John Paul Adrian Glaubitz
On 02/25/2017 09:39 PM, Sebastian Andrzej Siewior wrote:
> No. I assume that it might use QT's internal networking which is 1.0 and if
> they mix then bad things will happen.
> 
> The two functions marked * have no error handling if the function is missing.
> Not using SSLv23_client_method() means that the the user of this class has to
> try again with TLSv1_client_method() member which will only allow a TLS1.0
> handshake. This is not what you want because TLS1.0 itself is deprecated and
> the v23 method would allow the maximum possible TLS level (which is currently
> 1.2).

But the question is whether SSL support is actually relevant in khtml at all.

As you can see from the list of reverse dependencies, there's actually not
much that is using khtml and the very few packages that use it are offline
only like SystemSettings or Kiten. So, I don't think any SSL code is actually
ever used.

I mean, if you really insist to rebuild khtml with libssl1.0-dev, then please
just let's go ahead in order to get the number of RC bugs for Stretch down.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Re: Bug#856004: khtml: please build-depen on libssl1.0-dev for Stretch

2017-02-25 Thread Sebastian Andrzej Siewior
On 2017-02-25 12:29:31 [-0300], Lisandro Damián Nicanor Pérez Meyer wrote:
> I think the issue here is if it will work or not at runtime. 

that is what I assume, correct.

> Sebastian: have you seen it crash due to this?

No. I assume that it might use QT's internal networking which is 1.0 and if
they mix then bad things will happen.
I sure that the following symbols are missing:
 RAND_egd
 NETSCAPE_X509_it
 X509_STORE_CTX_set_chain*
 sk_free*
 sk_num
 sk_pop
 sk_value
 sk_new
 sk_push
 sk_dup
 SSLv23_client_method

The two functions marked * have no error handling if the function is missing.
Not using SSLv23_client_method() means that the the user of this class has to
try again with TLSv1_client_method() member which will only allow a TLS1.0
handshake. This is not what you want because TLS1.0 itself is deprecated and
the v23 method would allow the maximum possible TLS level (which is currently
1.2).
For those reasons I think it is wise to migrate to libssl1.0-dev.

Sebastian



Re: Bug#856004: khtml: please build-depen on libssl1.0-dev for Stretch

2017-02-25 Thread Lisandro Damián Nicanor Pérez Meyer
On sábado, 25 de febrero de 2017 10:56:59 ART Scott Kitterman wrote:
> On Saturday, February 25, 2017 12:29:31 PM Lisandro Damián Nicanor Pérez
> Meyer
> wrote:
> > On sábado, 25 de febrero de 2017 14:03:31 ART John Paul Adrian Glaubitz
> 
> wrote:
> > > Hi Sebastian!
> > > 
> > > I just gave it a try and khtml builds fine as is.
> > > 
> > > Are there any additional tests you'd suggest for testing whether khtml
> > > works fine with libssl1.1? Attached is the build log of a successful
> > > test build of the current khtml package.
> > 
> > I think the issue here is if it will work or not at runtime.
> > 
> > Sebastian: have you seen it crash due to this?
> 
> Kf5 (including khtml) need to use the same version of openssl as Qt5, which
> is 1.0 for this cycle.  Whether crashes have been seen or not, trying to
> mix openssl 1.0 and 1.1 in the same stack seems foolhardy.

I agree with that.

-- 
Un viejo proverbio de El.Machi dice que la memoria es como
las papas fritas... ¡nunca sobran!

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.


Re: Bug#856004: khtml: please build-depen on libssl1.0-dev for Stretch

2017-02-25 Thread John Paul Adrian Glaubitz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

On 02/25/2017 04:29 PM, Lisandro Damián Nicanor Pérez Meyer wrote:
> I think the issue here is if it will work or not at runtime.
> 
> Sebastian: have you seen it crash due to this?

So, looking at the reverse dependencies of khtml (libkf5khtml5), the
packages affected by such a crash would be:

 * khelpcenter
 * kio-extras
 * kiten
 * systemsettings

I have just rebuilt khtml against libssl1.1 and installed the package
on my laptop running Debian unstable. I'm an active KDE user and tried
to run the Help Center, Kiten and System Settings. I have not seen any
crashes so far.

So, I think we should downgrade the severity of the bug for the time
being and wait for more info from the original bug reporter.

Adrian

- -- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAlixrtAACgkQdCY7N/W1
+RN/wRAAlnnNe3uRmdunihGmRvZxUyIAMKd2gQfbtfjwKQldKYnpiAtoky/ioYfF
5r+yQ4p4vstLMPoKsCXtbY4eNN+KLbcfASzPnPrcu8noHs5BWOwa1VpSlL9Cpvlq
lRDjzhKyLjSN/z8NULZ++8Wj5R3hZjox8r6b7tGJRy7XXAbbNMSx9G2JqZdvTRgW
yjWdbnbgGJE+1aFHqkymdSM/Mfl0mGO1wH8pMcHPTu2yYmVMhJWhgstzmcAisolN
5hKmifv6M4Ok9qYsC7z5J52LT0m8zccUxwKcOg5n/ABMDo2axAI1dFMyTksrYxOv
w9s7YkpWJycbLRiuYJha5pARRcEwjjIJRFc3geutZS/SSefZ4oAunm2tYnGpkTg3
s9p7E9fp1LneGPaS1ADE1yb2bdqtMAVoCBkPMPGuM0Z/DMztoD6gYkPJPA5qF3wS
5wEgwk/mG+2Ws7oA+W99gZmkmnI+SDq+wCrO0+lCv9JGgZaWc2MxoqfEGUFjcVTF
B/f/p2SmgKSrIUCRkSUT4AMda9oE8Zh+Xeq0MEGma7baU4wwqVH854EsJyfbanAk
+kci2xFZ/u5kE5HVDiS34QQ4UqXRukMosO1aqiJmqNuY506cIVEClLrlHzvrLtXE
paFMTrqXkm2uyS/RPglP1cFTY7rEKAQsQ1R6tO+GnQ0+8C55vWs=
=yK96
-END PGP SIGNATURE-



Bug#856004: khtml: please build-depen on libssl1.0-dev for Stretch

2017-02-25 Thread Scott Kitterman
On Saturday, February 25, 2017 12:29:31 PM Lisandro Damián Nicanor Pérez Meyer 
wrote:
> On sábado, 25 de febrero de 2017 14:03:31 ART John Paul Adrian Glaubitz 
wrote:
> > Hi Sebastian!
> > 
> > I just gave it a try and khtml builds fine as is.
> > 
> > Are there any additional tests you'd suggest for testing whether khtml
> > works fine with libssl1.1? Attached is the build log of a successful
> > test build of the current khtml package.
> 
> I think the issue here is if it will work or not at runtime.
> 
> Sebastian: have you seen it crash due to this?

Kf5 (including khtml) need to use the same version of openssl as Qt5, which is 
1.0 for this cycle.  Whether crashes have been seen or not, trying to mix 
openssl 1.0 and 1.1 in the same stack seems foolhardy.

Scott K

signature.asc
Description: This is a digitally signed message part.


Re: Bug#856004: khtml: please build-depen on libssl1.0-dev for Stretch

2017-02-25 Thread Lisandro Damián Nicanor Pérez Meyer
On sábado, 25 de febrero de 2017 14:03:31 ART John Paul Adrian Glaubitz wrote:
> Hi Sebastian!
> 
> I just gave it a try and khtml builds fine as is.
> 
> Are there any additional tests you'd suggest for testing whether khtml
> works fine with libssl1.1? Attached is the build log of a successful
> test build of the current khtml package.

I think the issue here is if it will work or not at runtime. 

Sebastian: have you seen it crash due to this?

-- 
Programming today is a race between software engineers striving to build
bigger and better idiot-proof programs, and the Universe trying to produce
bigger and better idiots. So far, the Universe is winning.
  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.


Bug#856004: khtml: please build-depen on libssl1.0-dev for Stretch

2017-02-25 Thread John Paul Adrian Glaubitz
Hi Sebastian!

I just gave it a try and khtml builds fine as is.

Are there any additional tests you'd suggest for testing whether khtml
works fine with libssl1.1? Attached is the build log of a successful
test build of the current khtml package.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


khtml_5.28.0-1_amd64.build.gz
Description: application/gzip


Bug#848936: marked as done (sddm: purging leaves leaves dangling /etc/systemd/system/display-manager.service symlink)

2017-02-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 Feb 2017 10:05:31 +
with message-id 
and subject line Bug#848936: fixed in sddm 0.14.0-2
has caused the Debian Bug report #848936,
regarding sddm: purging leaves leaves dangling 
/etc/systemd/system/display-manager.service symlink
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
848936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: init-system-helpers
Version: 1.22
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + gdm3 lightdm sddm xdm
Control: found -1 sddm/0.13.0-1
Control: found -1 xdm/1:1.1.11-3

Hi,

during tests with piuparts I noticed the same behavior in 4 packages
providing a display-manager service: a dangling symlink is left after
purge. Some have individual bugs filed (lightdm: #775385, gdm3:
#771085), but this is more likely a bug somewhere in the helpers being
used. Notice, that after purge no other package providing a
display-manager service was installed any more.


1m16.3s ERROR: FAIL: Package purging left files on system:
  /etc/systemd/system/display-manager.service -> 
/lib/systemd/system/xdm.service not owned

3m8.3s ERROR: FAIL: Package purging left files on system:
  /etc/systemd/system/display-manager.service -> 
/lib/systemd/system/sddm.servicenot owned

2m46.0s ERROR: FAIL: Package purging left files on system:
  /etc/systemd/system/display-manager.service -> 
/lib/systemd/system/gdm3.servicenot owned

1m23.3s ERROR: FAIL: Package purging left files on system:
  /etc/systemd/system/display-manager.service -> 
/lib/systemd/system/lightdm.service not owned


Andreas


xdm_1:1.1.11-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sddm
Source-Version: 0.14.0-2

We believe that the bug you reported is fixed in the latest version of
sddm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 848...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated sddm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Feb 2017 19:09:24 +0100
Source: sddm
Binary: sddm sddm-theme-maui sddm-theme-debian-maui sddm-theme-elarun 
sddm-theme-debian-elarun sddm-theme-maldives
Architecture: source
Version: 0.14.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 sddm   - modern display manager for X11
 sddm-theme-debian-elarun - 'Debian Elarun' Theme for SDDM X11 display manager
 sddm-theme-debian-maui - 'Debian Maui' theme for SDDM X11 display manager
 sddm-theme-elarun - 'Elarun' Theme for SDDM X11 display manager
 sddm-theme-maldives - 'Maldives' theme for SDDM X11 display manager
 sddm-theme-maui - 'Maui' theme for SDDM X11 display manager
Closes: 848936 853844 854260
Changes:
 sddm (0.14.0-2) unstable; urgency=medium
 .
   * Avoid killing plymouth from the sddm system unit (Closes: 854260)
   * Purge dangling symlink.
 Thanks to Andreas Beckmann for following this issue (Closes: 848936)
   * Install the generated configuration file as an example
   * Workaround debconf's db_purge stdout parsing (#855912)
 Thanks to Laurent Bonnaud for reporting (Closes: 853844)
Checksums-Sha1:
 e8c5b546b980273d03b247ad3c876d7e32ed2ffc 2615 sddm_0.14.0-2.dsc
 40a456dfe6ddadb76d7cdbe18879dd3bde8cbd3d 44584 sddm_0.14.0-2.debian.tar.xz
 231c831173e0a3eba7a2fb2abbd26380f180d781 11401 sddm_0.14.0-2_source.buildinfo
Checksums-Sha256:
 bafaabf50f8e1eadc9b3a3492f656deb0826216f8c0d9f18ab39c28a6e1357b7 2615 
sddm_0.14.0-2.dsc
 cb030eff205c2b6220235afdf9acb81aabb3a02bfb9829d8636a30b0804202c9 44584 
sddm_0.14.0-2.debian.tar.xz
 33e974c69d8fb56f32e3b170f2f34c3c4341a38cb78b66f8d3c6f232d753be50 11401 
sddm_0.14.0-2_source.buildinfo
Files:
 c2da863112024e0f4be2c890e794a43d 2615 kde optional sddm_0.14.0-2.dsc
 66c4f44dba04d54b96ea79ba4ca07671 44584 kde optional sddm_0.14.0-2.debian.tar.xz
 e7f9210fe70b5a65eba5b132fa4c9bec 11401 kde optional 
sddm_0.14.0-2_source.buildinfo

-BEGIN PGP SIGN

sddm_0.14.0-2_source.changes ACCEPTED into unstable

2017-02-25 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Feb 2017 19:09:24 +0100
Source: sddm
Binary: sddm sddm-theme-maui sddm-theme-debian-maui sddm-theme-elarun 
sddm-theme-debian-elarun sddm-theme-maldives
Architecture: source
Version: 0.14.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 sddm   - modern display manager for X11
 sddm-theme-debian-elarun - 'Debian Elarun' Theme for SDDM X11 display manager
 sddm-theme-debian-maui - 'Debian Maui' theme for SDDM X11 display manager
 sddm-theme-elarun - 'Elarun' Theme for SDDM X11 display manager
 sddm-theme-maldives - 'Maldives' theme for SDDM X11 display manager
 sddm-theme-maui - 'Maui' theme for SDDM X11 display manager
Closes: 848936 853844 854260
Changes:
 sddm (0.14.0-2) unstable; urgency=medium
 .
   * Avoid killing plymouth from the sddm system unit (Closes: 854260)
   * Purge dangling symlink.
 Thanks to Andreas Beckmann for following this issue (Closes: 848936)
   * Install the generated configuration file as an example
   * Workaround debconf's db_purge stdout parsing (#855912)
 Thanks to Laurent Bonnaud for reporting (Closes: 853844)
Checksums-Sha1:
 e8c5b546b980273d03b247ad3c876d7e32ed2ffc 2615 sddm_0.14.0-2.dsc
 40a456dfe6ddadb76d7cdbe18879dd3bde8cbd3d 44584 sddm_0.14.0-2.debian.tar.xz
 231c831173e0a3eba7a2fb2abbd26380f180d781 11401 sddm_0.14.0-2_source.buildinfo
Checksums-Sha256:
 bafaabf50f8e1eadc9b3a3492f656deb0826216f8c0d9f18ab39c28a6e1357b7 2615 
sddm_0.14.0-2.dsc
 cb030eff205c2b6220235afdf9acb81aabb3a02bfb9829d8636a30b0804202c9 44584 
sddm_0.14.0-2.debian.tar.xz
 33e974c69d8fb56f32e3b170f2f34c3c4341a38cb78b66f8d3c6f232d753be50 11401 
sddm_0.14.0-2_source.buildinfo
Files:
 c2da863112024e0f4be2c890e794a43d 2615 kde optional sddm_0.14.0-2.dsc
 66c4f44dba04d54b96ea79ba4ca07671 44584 kde optional sddm_0.14.0-2.debian.tar.xz
 e7f9210fe70b5a65eba5b132fa4c9bec 11401 kde optional 
sddm_0.14.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE+JIdOnQEyG4RNSIVxxl2mbKbIyoFAlixU4kACgkQxxl2mbKb
IyrVYQ//RLM3kNIABH5lJ5uHHiRcpKBA677+ZNPDihF9DCnR2JGhGk5YodjdWt7l
YW//Iua7+jfzZ881H8zxEf/mcRS7Wyg1oywShwv4unbkwkWWBpZ5+PliGw2Hk/Pg
E52j94u5m6u2w7g94eOZ9puD4Dk28rE1NB4lca3aws94W2P4Xrk65cKae2V+A59e
GgLOKHsnw+pP19rBO+tA5gXSOf3oMD3S1TbMSw67pajxATEz5xbdSFIoZ9I1+pb+
LZsZ/nzVR1tz5hC/KN16B7L2XaJB9sC2OULIF4XyxwF6vDdAEHWIW9/mDxdM5xz6
h6Hh80atNqGfbuiIUVOaI1kVCZq3qMt2gtTtxPlF+iapscGC61WNlc3EChUN5CQf
e3NT2RkoXTM/4w8mTTeY4SVuEMAFMhjwX+BGm395BmKidjqLzedTWgHWsFRCDsTK
vemqkhYTWhuE/BeLsHnrrAoqEHPwXwhdDG2WH+n5ZAy/EUsBwdUmeV+bYHmUZR8r
vTcIEMXlMCmAXMe1Uo+Xd5WY1tTu9w3KV2ScRpzU4Q9tdEAkTbIdHl3V+Y5hAX+a
IHIeQUy6hqcJfxxz3wwkEo0W9Vi4UUjom1ALfE5X4XgFmf+qf4bzhUMdBWOa+jjC
jqy0XvwXfvqXG5yuD9A/9j//zByjL13YWLCjLt7wjwBlWQtAGoc=
=BvMP
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Processing of sddm_0.14.0-2_source.changes

2017-02-25 Thread Debian FTP Masters
sddm_0.14.0-2_source.changes uploaded successfully to localhost
along with the files:
  sddm_0.14.0-2.dsc
  sddm_0.14.0-2.debian.tar.xz
  sddm_0.14.0-2_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



Bug#853844: marked as done (sddm: purging fails because of deluser/userdel (sddm is currently used by a process))

2017-02-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 Feb 2017 10:05:32 +
with message-id 
and subject line Bug#853844: fixed in sddm 0.14.0-2
has caused the Debian Bug report #853844,
regarding sddm: purging fails because of deluser/userdel (sddm is currently 
used by a process)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
853844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sddm
Version: 0.14.0-1
Severity: serious


Dear Maintainer,

here is the problem:

# apt purge sddm   sddm-theme-breeze
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  sddm* sddm-theme-breeze*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 2 595 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 261837 files and directories currently installed.)
Removing sddm (0.14.0-1) 
.]
Please be sure to run "dpkg-reconfigure gdm3".
Removing sddm-theme-breeze (4:5.8.5-1) ...
Processing triggers for man-db (2.7.6.1-2) ...
(Reading database ... 261663 files and directories currently installed.)
Purging configuration files for sddm (0.14.0-1) ...
Removing user `sddm' ...
Warning: group `sddm' has no more members.
userdel: user sddm is currently used by process 658
/usr/sbin/deluser: `/usr/sbin/userdel sddm' returned error code 8. Exiting.
Could not remove sddm user.
/usr/sbin/delgroup: `sddm' still has `sddm' as their primary group!
Could not remove sddm group.
userdel: user sddm is currently used by process 658
/usr/sbin/deluser: `/usr/sbin/userdel sddm' returned error code 8. Exiting.
/usr/sbin/delgroup: `sddm' still has `sddm' as their primary group!
dpkg: error processing package sddm (--purge):
 subprocess installed post-removal script returned error exit status 128
Errors were encountered while processing:
 sddm
E: Sub-process /usr/bin/dpkg returned an error code (1)


Stopping the service before the purge fixes the problem.


-- 
Laurent.
--- End Message ---
--- Begin Message ---
Source: sddm
Source-Version: 0.14.0-2

We believe that the bug you reported is fixed in the latest version of
sddm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 853...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated sddm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Feb 2017 19:09:24 +0100
Source: sddm
Binary: sddm sddm-theme-maui sddm-theme-debian-maui sddm-theme-elarun 
sddm-theme-debian-elarun sddm-theme-maldives
Architecture: source
Version: 0.14.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 sddm   - modern display manager for X11
 sddm-theme-debian-elarun - 'Debian Elarun' Theme for SDDM X11 display manager
 sddm-theme-debian-maui - 'Debian Maui' theme for SDDM X11 display manager
 sddm-theme-elarun - 'Elarun' Theme for SDDM X11 display manager
 sddm-theme-maldives - 'Maldives' theme for SDDM X11 display manager
 sddm-theme-maui - 'Maui' theme for SDDM X11 display manager
Closes: 848936 853844 854260
Changes:
 sddm (0.14.0-2) unstable; urgency=medium
 .
   * Avoid killing plymouth from the sddm system unit (Closes: 854260)
   * Purge dangling symlink.
 Thanks to Andreas Beckmann for following this issue (Closes: 848936)
   * Install the generated configuration file as an example
   * Workaround debconf's db_purge stdout parsing (#855912)
 Thanks to Laurent Bonnaud for reporting (Closes: 853844)
Checksums-Sha1:
 e8c5b546b980273d03b247ad3c876d7e32ed2ffc 2615 sddm_0.14.0-2.dsc
 40a456dfe6ddadb76d7cdbe18879dd3bde8cbd3d 44584 sddm_0.14.0-2.debian.tar.xz
 231c831173e0a3eba7a2fb2abbd26380f180d781 11401 sddm_0.14.0-2_source.buildinfo
Checksums-Sha256:
 bafaabf50f8e1eadc9b3a3492f656deb0826216f8c0d9f18ab39c28a6e1357b7 2615 
sddm_0.14.0-2.dsc
 cb030eff205c2b6220235afdf9acb81aabb3a02bfb9829d8636a30b0804202c9 44584 

Bug#854260: marked as done (sddm: Please remove Conflicts= and OnFailure= from sddm.service file)

2017-02-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 Feb 2017 10:05:32 +
with message-id 
and subject line Bug#854260: fixed in sddm 0.14.0-2
has caused the Debian Bug report #854260,
regarding sddm: Please remove Conflicts= and OnFailure= from sddm.service file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
854260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sddm
Version: 0.13.0-1
Severity: normal

Hi,

The debian/sddm.service file contains the following lines:

Conflicts=plymouth-quit-wait.service
After=systemd-user-sessions.service plymouth-start.service 
plymouth-quit-wait.service
OnFailure=plymouth-quit.service

For me the Conflicts= (and the OnFailure=) doesn't make any sense. The
gdm.service file contains these line too but only because GDM takes care
himself of stopping plymouth. sddm should just wait that plymouth
is stopped here and nothing else.

The OnFailure= is also redundant here if the Conflicts= is removed as
the plymouth-quit.service will be executed anyway.

Upstream ships a file in services/sddm.service.in, with
After=plymouth-quit.service (like GDM), any reason you have modified
this?

Regards,

Laurent Bigonville

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: sddm
Source-Version: 0.14.0-2

We believe that the bug you reported is fixed in the latest version of
sddm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 854...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated sddm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Feb 2017 19:09:24 +0100
Source: sddm
Binary: sddm sddm-theme-maui sddm-theme-debian-maui sddm-theme-elarun 
sddm-theme-debian-elarun sddm-theme-maldives
Architecture: source
Version: 0.14.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 sddm   - modern display manager for X11
 sddm-theme-debian-elarun - 'Debian Elarun' Theme for SDDM X11 display manager
 sddm-theme-debian-maui - 'Debian Maui' theme for SDDM X11 display manager
 sddm-theme-elarun - 'Elarun' Theme for SDDM X11 display manager
 sddm-theme-maldives - 'Maldives' theme for SDDM X11 display manager
 sddm-theme-maui - 'Maui' theme for SDDM X11 display manager
Closes: 848936 853844 854260
Changes:
 sddm (0.14.0-2) unstable; urgency=medium
 .
   * Avoid killing plymouth from the sddm system unit (Closes: 854260)
   * Purge dangling symlink.
 Thanks to Andreas Beckmann for following this issue (Closes: 848936)
   * Install the generated configuration file as an example
   * Workaround debconf's db_purge stdout parsing (#855912)
 Thanks to Laurent Bonnaud for reporting (Closes: 853844)
Checksums-Sha1:
 e8c5b546b980273d03b247ad3c876d7e32ed2ffc 2615 sddm_0.14.0-2.dsc
 40a456dfe6ddadb76d7cdbe18879dd3bde8cbd3d 44584 sddm_0.14.0-2.debian.tar.xz
 231c831173e0a3eba7a2fb2abbd26380f180d781 11401 sddm_0.14.0-2_source.buildinfo
Checksums-Sha256:
 bafaabf50f8e1eadc9b3a3492f656deb0826216f8c0d9f18ab39c28a6e1357b7 2615 
sddm_0.14.0-2.dsc
 cb030eff205c2b6220235afdf9acb81aabb3a02bfb9829d8636a30b0804202c9 44584 
sddm_0.14.0-2.debian.tar.xz
 33e974c69d8fb56f32e3b170f2f34c3c4341a38cb78b66f8d3c6f232d753be50 11401 
sddm_0.14.0-2_source.buildinfo
Files:
 c2da863112024e0f4be2c890e794a43d 2615 kde optional sddm_0.14.0-2.dsc
 66c4f44dba04d54b96ea79ba4ca07671 44584 kde optional sddm_0.14.0-2.debian.tar.xz
 e7f9210fe70b5a65eba5b132fa4c9bec 11401 kde optional 
sddm_0.14.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE+JIdOnQEyG4RNSIVxxl2mbKbIyoFAlixU4kACgkQxxl2mbKb
IyrVYQ//RLM3kNIABH5lJ5uHHiRcpKBA67