[pkg-fso-maint] libfsoframework 0.12.0-8 MIGRATED to testing
FYI: The status of the libfsoframework source package in Debian's testing distribution has changed. Previous version: 0.12.0-7 Current version: 0.12.0-8 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ pkg-fso-maint mailing list pkg-fso-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fso-maint
[pkg-fso-maint] Bug#870965: marked as done (phoneui-apps: should phoneui-apps be removed from unstable?)
Your message dated Thu, 7 Sep 2017 15:22:48 +0200 with message-id <20170907132248.pkadmbdni6cpmc3o@earth> and subject line Closing Bugs, for packages removed from Debian has caused the Debian Bug report #870965, regarding phoneui-apps: should phoneui-apps be removed from unstable? 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.) -- 870965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phoneui-apps User: debian...@lists.debian.org Usertags: qa-removals-post-stretch Hi, Following a discussion[1] on the debian-qa@ mailing list on packages that missed both jessie and stretch, I am proposing the removal of this package from unstable, because: it was in unstable at the time of the stretch freeze but wasn't part of stretch AND it was in unstable at the time of the jessie freeze but it wasn't part of jessie AND it is still not in testing AND it was not uploaded since the beginning of 2017. If you disagree and think that this package should remain in unstable, feel free to just close this bug. If this bug is still open one month from now (on 2017-09-06), it will be turned into a removal request, using: reassign -1 ftp.debian.org retitle -1 RM: phoneui-apps -- RoQA; missed both jessie and stretch thanks - Lucas, for the QA team. [1] https://lists.debian.org/debian-qa/2017/07/msg00021.html --- End Message --- --- Begin Message --- Hi, Close open bugs in FSO related packages, that have been removed from Debian as part of removal request #873766. -- Sebastian signature.asc Description: PGP signature --- End Message --- ___ pkg-fso-maint mailing list pkg-fso-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fso-maint
[pkg-fso-maint] Bug#871119: marked as done (fso-gsmd: FTBFS with vala 0.36)
Your message dated Thu, 7 Sep 2017 15:22:48 +0200 with message-id <20170907132248.pkadmbdni6cpmc3o@earth> and subject line Closing Bugs, for packages removed from Debian has caused the Debian Bug report #871119, regarding fso-gsmd: FTBFS with vala 0.36 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.) -- 871119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fso-gsmd Version: 0.12.0-5 Severity: important User: pkg-vala-maintain...@lists.alioth.debian.org Usertags: vala-0.36 Tags: buster sid fso-gsmd fails to build from source with vala 0.36 which is currently in experimental and will be uploaded to unstable soon. You can find a build log from Ubuntu 17.10 Alpha at https://launchpad.net/~jbicha/+archive/ubuntu/vala36/+build/12762433 On behalf of the Debian Vala maintainers, Jeremy Bicha --- End Message --- --- Begin Message --- Hi, Close open bugs in FSO related packages, that have been removed from Debian as part of removal request #873766. -- Sebastian signature.asc Description: PGP signature --- End Message --- ___ pkg-fso-maint mailing list pkg-fso-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fso-maint
[pkg-fso-maint] Bug#868522: marked as done (openbmap-logger: The name org.freesmartphone.ogpsd was not provided by any .service files)
Your message dated Thu, 7 Sep 2017 15:22:48 +0200 with message-id <20170907132248.pkadmbdni6cpmc3o@earth> and subject line Closing Bugs, for packages removed from Debian has caused the Debian Bug report #868522, regarding openbmap-logger: The name org.freesmartphone.ogpsd was not provided by any .service files 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.) -- 868522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openbmap-logger Version: 0.4.0-7 Severity: grave Justification: renders package unusable Dear Maintainer, I cannot start openBmap as it fails with the following error: $ openBmapGTK Try loading /usr/share/openBmap/Main.glade glade file. Traceback (most recent call last): File "/usr/bin/openBmapGTK", line 356, in hwg = openBmapGTK() File "/usr/bin/openBmapGTK", line 130, in __init__ self._obmlogger = openbmap.logger.ObmLogger() File "/usr/lib/python2.7/dist-packages/openbmap/logger.py", line 826, in __init__ self._gps = Gps() File "/usr/lib/python2.7/dist-packages/openbmap/logger.py", line 763, in __init__ self._dbusobj = dbus.SystemBus().get_object('org.freesmartphone.ogpsd', '/org/freedesktop/Gypsy') File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in __init__ self._named_service = conn.activate_name_owner(bus_name) File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in activate_name_owner self.start_service_by_name(bus_name) File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in start_service_by_name 'su', (bus_name, flags))) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freesmartphone.ogpsd was not provided by any .service files -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openbmap-logger depends on: ii fso-frameworkd 0.10.1-3 ii python 2.7.13-2 ii python-glade2 2.24.0-5.1 ii python-gtk2 2.24.0-5.1 openbmap-logger recommends no packages. openbmap-logger suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Hi, Close open bugs in FSO related packages, that have been removed from Debian as part of removal request #873766. -- Sebastian signature.asc Description: PGP signature --- End Message --- ___ pkg-fso-maint mailing list pkg-fso-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fso-maint
[pkg-fso-maint] Bug#853504: marked as done (libphone-ui-shr: ftbfs with GCC-7)
Your message dated Thu, 7 Sep 2017 15:22:48 +0200 with message-id <20170907132248.pkadmbdni6cpmc3o@earth> and subject line Closing Bugs, for packages removed from Debian has caused the Debian Bug report #853504, regarding libphone-ui-shr: ftbfs with GCC-7 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.) -- 853504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853504 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libphone-ui-shr Version: 0.1+git20130901-3 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-7 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The severity of this report may be raised before the buster release. There is no need to fix this issue in time for the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc7-20170126/libphone-ui-shr_0.1+git20130901-3_unstable_gcc7.log The last lines of the build log are at the end of this report. To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-7/porting_to.html [...] /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../src/util -I../src/widget -I../src/view -DDATADIR=\"/usr/share\" -DPKGDATADIR=\"/usr/share/libphone-ui-shr\" -DPACKAGE=\"libphone-ui-shr\" -DLOCALEDIR=\"/usr/share/locale\" -DG_LOG_DOMAIN=\"libphone-ui-shr\" -pthread -I/usr/include/elementary-1 -I/usr/include/efl-1 -I/usr/include/ecore-fb-1 -I/usr/include/efl-1 -I/usr/include/ecore-x-1 -I/usr/include/efl-1 -I/usr/include/ethumb-client-1 -I/usr/include/efl-1 -I/usr/include/ethumb-1 -I/usr/include/efl-1 -I/usr/include/edje-1 -I/usr/include/lua5.1 -I/usr/include/efl-1 -I/usr/include/embryo-1 -I/usr/include/efl-1 -I/usr/include/ecore-imf-evas-1 -I/usr/include/efl-1 -I/usr/include/ecore-evas-1 -I/usr/include/efl-1 -I/usr/include/ecore-input-evas-1 -I/usr/include/efl-1 -I/usr/include/emotion-1 -I/usr/include/efl-1 -I/usr/include/eeze-1 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/uuid -I/usr/include/efl-1 -I/usr /include/evas-1 -I/usr/include/libpng16 -I/usr/include/fribidi -I/usr/include/freetype2 -I/usr/include/efl-1 -I/usr/include/ecore-imf-1 -I/usr/include/efl-1 -I/usr/include/ecore-input-1 -I/usr/include/efl-1 -I/usr/include/eio-1 -I/usr/include/efl-1 -I/usr/include/efreet-1 -I/usr/include/efl-1 -I/usr/include/efreet-1 -I/usr/include/efl-1 -I/usr/include/efreet-1 -I/usr/include/efl-1 -I/usr/include/eldbus-1 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/efl-1 -I/usr/include/ecore-file-1 -I/usr/include/efl-1 -I/usr/include/ecore-con-1 -I/usr/include/efl-1 -I/usr/include/ecore-1 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/efl-1 -I/usr/include/eo-1 -I/usr/include/efl-1 -I/usr/include/eet-1 -I/usr/include/efl-1 -I/usr/include/eina-1 -I/usr/include/eina-1/eina -I/usr/include/p11-kit-1 -pthread -I/usr/include/phoneui -I/usr/include/fso-glib -I/usr/include/fsoframework-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-li nux-gnu/glib-2.0/include -I/usr/include/libnl3 -I/usr/include/fso-glib -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/fsoframework-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libnl3 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/phone-utils -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g3 -Wall -Wextra -Werror -g -O2 -fdebug-prefix-map=/<>/libphone-ui-shr-0.1+git20130901=. -fstack-protector-strong -Wformat -Werror=format-security -c -o message-new-view.lo `test -f 'view/message-new-view.c' || echo './'`view/message-new-view.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../src/util
[pkg-fso-maint] Bug#871058: marked as done (fso-deviced: FTBFS with vala 0.36)
Your message dated Thu, 7 Sep 2017 15:22:48 +0200 with message-id <20170907132248.pkadmbdni6cpmc3o@earth> and subject line Closing Bugs, for packages removed from Debian has caused the Debian Bug report #871058, regarding fso-deviced: FTBFS with vala 0.36 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.) -- 871058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871058 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fso-deviced Version: 0.12.0-7 Severity: important User: pkg-vala-maintain...@lists.alioth.debian.org Usertags: vala-0.36 Tags: buster sid fso-deviced fails to build from source with vala 0.36 which is currently in experimental and will be uploaded to unstable soon. You can find a build log from Ubuntu 17.10 Alpha at https://launchpad.net/~jbicha/+archive/ubuntu/vala36/+build/12762432 On behalf of the Debian Vala maintainers, Jeremy Bicha --- End Message --- --- Begin Message --- Hi, Close open bugs in FSO related packages, that have been removed from Debian as part of removal request #873766. -- Sebastian signature.asc Description: PGP signature --- End Message --- ___ pkg-fso-maint mailing list pkg-fso-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fso-maint
[pkg-fso-maint] Bug#870943: marked as done (phoneuid: should phoneuid be removed from unstable?)
Your message dated Thu, 7 Sep 2017 15:22:48 +0200 with message-id <20170907132248.pkadmbdni6cpmc3o@earth> and subject line Closing Bugs, for packages removed from Debian has caused the Debian Bug report #870943, regarding phoneuid: should phoneuid be removed from unstable? 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.) -- 870943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phoneuid User: debian...@lists.debian.org Usertags: qa-removals-post-stretch Hi, Following a discussion[1] on the debian-qa@ mailing list on packages that missed both jessie and stretch, I am proposing the removal of this package from unstable, because: it was in unstable at the time of the stretch freeze but wasn't part of stretch AND it was in unstable at the time of the jessie freeze but it wasn't part of jessie AND it is still not in testing AND it was not uploaded since the beginning of 2017. If you disagree and think that this package should remain in unstable, feel free to just close this bug. If this bug is still open one month from now (on 2017-09-06), it will be turned into a removal request, using: reassign -1 ftp.debian.org retitle -1 RM: phoneuid -- RoQA; missed both jessie and stretch thanks - Lucas, for the QA team. [1] https://lists.debian.org/debian-qa/2017/07/msg00021.html --- End Message --- --- Begin Message --- Hi, Close open bugs in FSO related packages, that have been removed from Debian as part of removal request #873766. -- Sebastian signature.asc Description: PGP signature --- End Message --- ___ pkg-fso-maint mailing list pkg-fso-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fso-maint
[pkg-fso-maint] Bug#773586: marked as done (phoneuid: doesn't start or crashes during startup - probably due to problem in phonefsod)
Your message dated Thu, 7 Sep 2017 15:22:48 +0200 with message-id <20170907132248.pkadmbdni6cpmc3o@earth> and subject line Closing Bugs, for packages removed from Debian has caused the Debian Bug report #773586, regarding phoneuid: doesn't start or crashes during startup - probably due to problem in phonefsod 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.) -- 773586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: phoneuid Version: 0.1+git20130505-1 Severity: grave Justification: renders package unusable Dear Maintainer, This is sort of a continuation of #766114 which to me seems rightfully closed. There are four things to note in advance please: 1. I'm not sure whether phoneuid is the correct package to file this report against. It could be anywhere in this chain: fso-deviced - phonefsod - phoneuid - phoneui-apps 2. apt doesn't install recommends or suggests on this system by default: # cat /etc/apt/apt.conf APT::Install-Recommends "0"; APT::Install-Suggests "0"; 3. The automatic screen-blanking that's done by (I think) phonefsod works fine, however the lock screen with the slider (by phoneui-apps) doesn't come up. 4. I tested this first with sysvinit, then with systemd as the init system, but didn't see any differences. All of the following outputs are with systemd. After installing phoneui-apps and trying to start any of the apps (e.g. phoneui-quick-settings), no app window comes up. There's an strace output further down. The problem seems to be that phoneuid is either not starting or dying in the process: # cat phonefsod.log 2014.12.20 11:50:38.551544 [phonefsod] MESSAGE: phonefsod-0.1.0 is in startup mode as user(root) 2014.12.20 11:50:38.765655 [phonefsod] MESSAGE: Inhibiting suspend during startup phase (max 360s) 2014.12.20 11:51:03.876434 [phonefsod] WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out 2014.12.20 11:51:28.909052 [phonefsod] WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out 2014.12.20 11:51:53.955090 [phonefsod] WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: Timeout was reached 2014.12.20 11:52:18.983082 [phonefsod] WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out 2014.12.20 11:52:44.015819 [phonefsod] WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out 2014.12.20 11:52:44.091402 [phonefsod] MESSAGE: !!! ouch, phoneuid is gone - telephony won't work anymore !!! /var/log/phoneuid.log was not created when the process was started during boot. This is from a manual start as root after killing the original process: # cat phoneuid.log 2014.12.20 13:22:42.087796 [phoneuid] MESSAGE: Using log level 'INFO' 2014.12.20 13:22:42.088528 [libphone-ui]MESSAGE: Loading phoneuid 2014.12.20 13:22:42.423247 [libphone-ui]CRITICAL: No such file or directory 2014.12.20 13:23:07.495138 [libphone-ui]WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out 2014.12.20 13:23:32.524630 [libphone-ui]WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out 2014.12.20 13:23:57.563633 [libphone-ui]WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out for reference: # dpkg --get-selections | grep n900 fso-deviced-n900install fso-gsmd-n900