Processed: Re: Bug#866129: lilypond: segfault using lilypond buster testing
Processing control commands: > forcemerge 871372 -1 Bug #871372 [src:lilypond] lilypond: FTBFS: command failed: /<>/out/bin/lilypond -I . -dbackend=eps --formats=ps,png,pdf -djob-count=16 -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr --header=doctitlehu --header=doctitleit --header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde --header=texidoces --header=texidocfr --header=texidochu --header=texidocit --header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types -ddump-signatures -danti-alias-factor=2 -I "/<>/out/lybook-db" -I "." -I ".." -I "/<>/input/regression" -I "." --formats=eps -deps-box-padding=3.00 -dread-file-list -dno-strip-output-dir "/<>/out/lybook-db/snippet-names-7631296499380870844.ly" Bug #871372 [src:lilypond] lilypond: FTBFS: command failed: /<>/out/bin/lilypond -I . -dbackend=eps --formats=ps,png,pdf -djob-count=16 -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr --header=doctitlehu --header=doctitleit --header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde --header=texidoces --header=texidocfr --header=texidochu --header=texidocit --header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types -ddump-signatures -danti-alias-factor=2 -I "/<>/out/lybook-db" -I "." -I ".." -I "/<>/input/regression" -I "." --formats=eps -deps-box-padding=3.00 -dread-file-list -dno-strip-output-dir "/<>/out/lybook-db/snippet-names-7631296499380870844.ly" Marked as found in versions lilypond/2.18.2-7. Bug #866129 [src:lilypond] lilypond: segfault using lilypond buster testing Severity set to 'serious' from 'important' Marked as found in versions lilypond/2.18.2-8. Added tag(s) buster and sid. Merged 866129 871372 -- 866129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866129 871372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#869594: marked as done (grok FTBFS: We require gperf version >= 3.0.3)
Your message dated Sun, 20 Aug 2017 03:49:17 + with message-idand subject line Bug#869594: fixed in grok 1.20110708.1-4.2 has caused the Debian Bug report #869594, regarding grok FTBFS: We require gperf version >= 3.0.3 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.) -- 869594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grok Version: 1.20110708.1-4.1 Severity: serious User: helm...@debian.org Usertags: rebootstrap grok fails to build from source in unstable amd64 (presumably due to the gperf 3.1 upload): | cc -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pipe -fPIC -I. -O2 -I/usr/local/include -DPLATFORM_GNULinux libc_helper.c -o libc_helper.o | GNU gperf 3.1 | We require gperf version >= 3.0.3 | Makefile:226: recipe for target 'grok_matchconf_macro.c' failed | make[1]: *** [grok_matchconf_macro.c] Error 1 | make[1]: Leaving directory '/<>' | dh_auto_build: make -j1 returned exit code 2 | debian/rules:18: recipe for target 'build-arch' failed | make: *** [build-arch] Error 2 | dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Helmut --- End Message --- --- Begin Message --- Source: grok Source-Version: 1.20110708.1-4.2 We believe that the bug you reported is fixed in the latest version of grok, 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 869...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. SZALAY Attila (supplier of updated grok 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: SHA256 Format: 1.8 Date: Wed, 09 Aug 2017 16:36:26 -0400 Source: grok Binary: grok libgrok1 libgrok-dev grok-dbg Architecture: source amd64 Version: 1.20110708.1-4.2 Distribution: unstable Urgency: medium Maintainer: Stig Sandbeck Mathisen Changed-By: SZALAY Attila Description: grok - powerful pattern-matching and reacting tool grok-dbg - debugging symbols for grok libgrok-dev - development files for grok libgrok1 - shared libraries for grok Closes: 841668 869594 Changes: grok (1.20110708.1-4.2) unstable; urgency=medium . * Non-maintainer upload. * Apply Steve Langasek's fix for wrong pointer alias bug (Closes: #841668) * Apply patches to allow build grok with gperf >= 3.1 (Closes: #869594) Checksums-Sha1: 9529aafeae71bf294f11a81105e773b4f55e 2138 grok_1.20110708.1-4.2.dsc c5e858b5cfb35d88f2606dad56e56a7e5e75774d 6440 grok_1.20110708.1-4.2.debian.tar.xz 0ed128114e76bdb6ee0f53547e23683b61cd 240286 grok-dbg_1.20110708.1-4.2_amd64.deb 5cd505df46e4dc929af94f380529c5702c42192a 6728 grok_1.20110708.1-4.2_amd64.buildinfo 4e00b07790c4f34cc8addbb96f3b6f8422e310e1 58062 grok_1.20110708.1-4.2_amd64.deb 8e18fbb8fa56a5abbfe93bb285c3d7688177b321 8856 libgrok-dev_1.20110708.1-4.2_amd64.deb 460440c2e460db6a6fc830e818331cfd912d667d 31966 libgrok1_1.20110708.1-4.2_amd64.deb Checksums-Sha256: 5c1dca113403a9fcd32209e29ff3230d3d95c2b66676dbcf114f01b6ea28f173 2138 grok_1.20110708.1-4.2.dsc 3dbd704158d5de207715e84ec7b5a47e4e2d3d32ededddc03288915487d1a275 6440 grok_1.20110708.1-4.2.debian.tar.xz 10e9b47e2504121dc6ef33e0f031a2a8017ceb4ec5854a988e426f1c9ab8e340 240286 grok-dbg_1.20110708.1-4.2_amd64.deb 41bf1ada47440a76e3cf9bc4433df6544916ad07b77541a208214ae565a5ae3e 6728 grok_1.20110708.1-4.2_amd64.buildinfo c7fa2e66bcd63ae4d5c81efc7aa5a1e9d60ff5e142f998690d8f1180dd0860cd 58062 grok_1.20110708.1-4.2_amd64.deb 4219426c8aba178dae17ea8c8849d7f4063db1eda72fe7e55901288174ba 8856 libgrok-dev_1.20110708.1-4.2_amd64.deb 45398609822d7d0d36d5df397313f3c6fccef01a058129ac1b40d44028f07a4f 31966 libgrok1_1.20110708.1-4.2_amd64.deb Files: 67012a8074d220fff6573d104588b8ff 2138 misc extra grok_1.20110708.1-4.2.dsc 92a7165a242a374349efd6806223 6440 misc extra grok_1.20110708.1-4.2.debian.tar.xz 785d15a77338ce8c149d5a47df31405b 240286 debug extra grok-dbg_1.20110708.1-4.2_amd64.deb 975e9d0ae1e5770757c7df5cd602b70a 6728 misc extra
Bug#861551: Patch for grafana FTBFS
Hi, This seems to be due to an API change in the go-xorm library. Luckily, the change is simple enough, and the attached patch fixes it. Sadly, then other problems show with javascript, and I am not sure about this... ## Build CSS: http://lesscss.org/usage/index.html mkdir -p public/css cd public/css \ && lessc --include-path=../less --include-path=../vendor/bootstrap/less ../less/bootstrap.dark.less grafana.dark.min.css.tmp \ && cat grafana.dark.min.css.tmp /usr/share/fonts-font-awesome/css/font-awesome.css > grafana.dark.min.css \ && lessc --include-path=../less --include-path=../vendor/bootstrap/less ../less/bootstrap.light.less grafana.light.min.css.tmp \ && cat grafana.light.min.css.tmp /usr/share/fonts-font-awesome/css/font-awesome.css > grafana.light.min.css \ ; tsc --module amd public/app/features/dashboard/timepicker/timepicker.ts public/app/features/panel/panel_meta.ts public/app/core/core_module.ts public/app/core/directives/give_focus.ts public/app/core/directives/array_join.ts public/app/core/filters/filters.ts public/app/core/core.ts public/app/core/table_model.ts public/app/core/time_series.ts public/app/core/controllers/signup_ctrl.ts public/app/core/routes/bundle_loader.ts public/app/core/utils/flatten.ts public/app/core/utils/datemath.ts public/app/core/utils/rangeutil.ts public/app/headers/lodash/lodash.d.ts public/app/headers/angularjs/angularjs.d.ts public/app/headers/common.d.ts public/app/headers/moment/moment.d.ts public/app/headers/moment/moment-node.d.ts public/app/headers/require/require.d.ts public/app/headers/jquery/jquery.d.ts public/app/plugins/datasource/influxdb_08/specs/query_builder_specs.ts public/app/plugins/datasource/influxdb_08/specs/datasource-specs.ts public/app/plugins/datasource/influxdb_08/specs/influx_series_specs.ts public/app/plugins/datasource/graphite/specs/query_ctrl_specs.ts public/app/plugins/datasource/graphite/specs/gfunc_specs.ts public/app/plugins/datasource/graphite/specs/datasource_specs.ts public/app/plugins/datasource/prometheus/specs/datasource_specs.ts public/app/plugins/datasource/elasticsearch/specs/query_ctrl_specs.ts public/app/plugins/datasource/elasticsearch/specs/query_builder_specs.ts public/app/plugins/datasource/elasticsearch/specs/index_pattern_specs.ts public/app/plugins/datasource/elasticsearch/specs/elastic_response_specs.ts public/app/plugins/datasource/elasticsearch/specs/datasource_specs.ts public/app/plugins/datasource/elasticsearch/specs/query_def_specs.ts public/app/plugins/datasource/influxdb/specs/query_ctrl_specs.ts public/app/plugins/datasource/influxdb/specs/query_builder_specs.ts public/app/plugins/datasource/influxdb/specs/influx_query_specs.ts public/app/plugins/datasource/influxdb/specs/query_part_specs.ts public/app/plugins/datasource/influxdb/specs/influx_series_specs.ts public/app/plugins/datasource/influxdb/query_part.ts public/app/plugins/datasource/influxdb/influx_query.ts public/app/plugins/datasource/cloudwatch/specs/datasource_specs.ts public/app/panels/table/transformers.ts public/app/panels/table/module.ts public/app/panels/table/specs/table_model_specs.ts public/app/panels/table/specs/renderer_specs.ts public/app/panels/table/specs/transformers_specs.ts public/app/panels/table/editor.ts public/app/panels/table/controller.ts public/app/panels/table/renderer.ts public/test/core/table_model_specs.ts public/test/core/utils/rangeutil_specs.ts public/test/core/utils/datemath_specs.ts public/test/core/utils/flatten_specs.ts public/test/lib/common.ts public/app/headers/angularjs/angularjs.d.ts(1422,15): error TS2430: Interface 'IHttpPromise' incorrectly extends interface 'IPromise'. Types of property 'then' are incompatible. Type '(successCallback: (response: IHttpPromiseCallbackArg) => TResult | IPromise,...' is not assignable to type '(successCallback: (promiseValue: IHttpPromiseCallbackArg) => IPromise | TResult...'. Types of parameters 'successCallback' and 'successCallback' are incompatible. Type 'IPromise | TResult | IHttpPromise | IPromise' is not assignable to type 'void | TResult | IHttpPromiseCallbackArg | IPromise' is not assignable to type 'void | TResult | IHttpPromiseCallbackArg | IPromise' is not assignable to type 'IPromise>'. Types of property 'then' are incompatible. Type '(successCallback: (response: IHttpPromiseCallbackArg) => TResult | IPromise I...'. Types of parameters 'successCallback' and 'successCallback' are incompatible. Type 'IPromise | TResult | IHttpPromise | IPromise' is not assignable to type 'void | TResult | IHttpPromiseCallbackArg | IPromise' is not assignable to type 'void | TResult | IHttpPromiseCallbackArg | IPromise' is not assignable to type 'IPromise>'. Types of property 'then'
Bug#872688: galpy, hardcoded dependency on obsolete package libgsl2
Package: galpy Version: 1.2-1 Severity: serious After rebuilding for the libgsl transition python-galpy and python3-galpy now depend on both libgsl2 and libgsl23 due to a hardcoded dependency. Removing the hardcoded dependency from the packaging is trivial and a quick grep of the source didn't show up any hardcoded references in the source tree itself but it would be good if someone who actually uses the package could check things out.
Bug#861551: grafana: FTBFS with latest golang-go.crypto
Dear Maintainer, Here's the failing part if it helps: […] github.com/grafana/grafana/pkg/services/sqlstore/sqlutil github.com/grafana/grafana/pkg/services/sqlstore/migrator github.com/grafana/grafana/pkg/services/sqlstore/migrations github.com/grafana/grafana/pkg/services/sqlstore # github.com/grafana/grafana/pkg/services/sqlstore src/github.com/grafana/grafana/pkg/services/sqlstore/sqlstore.go:96: cannot assign to x.Logger src/github.com/grafana/grafana/pkg/services/sqlstore/sqlstore.go:96: cannot use xorm.NewSimpleLogger(f) (type *xorm.SimpleLogger) as type func() core.ILogger in assignment src/github.com/grafana/grafana/pkg/services/sqlstore/sqlstore.go:99: cannot assign to x.ShowSQL src/github.com/grafana/grafana/pkg/services/sqlstore/sqlstore.go:99: cannot use false (type bool) as type func(...bool) in assignment src/github.com/grafana/grafana/pkg/services/sqlstore/sqlstore.go:100: x.ShowInfo undefined (type *xorm.Engine has no field or method ShowInfo) src/github.com/grafana/grafana/pkg/services/sqlstore/sqlstore.go:101: x.ShowDebug undefined (type *xorm.Engine has no field or method ShowDebug) src/github.com/grafana/grafana/pkg/services/sqlstore/sqlstore.go:102: x.ShowErr undefined (type *xorm.Engine has no field or method ShowErr) src/github.com/grafana/grafana/pkg/services/sqlstore/sqlstore.go:103: x.ShowWarn undefined (type *xorm.Engine has no field or method ShowWarn) github.com/grafana/grafana/pkg/api/cloudwatch github.com/grafana/grafana/pkg/api github.com/grafana/grafana/pkg/cmd dh_auto_build: go install -gcflags=\"-trimpath=/home/lamby/temp/cdt.20170819183554.HipoxvWaoS.db.grafana/grafana-2.6.0\+dfsg/_build/src\" -asmflags=\"-trimpath=/home/lamby/temp/cdt.20170819183554.HipoxvWaoS.db.grafana/grafana-2.6.0\+dfsg/_build/src\" -v -p 9 github.com/grafana/grafana github.com/grafana/grafana/pkg/api github.com/grafana/grafana/pkg/api/cloudwatch github.com/grafana/grafana/pkg/api/dtos github.com/grafana/grafana/pkg/api/static github.com/grafana/grafana/pkg/bus github.com/grafana/grafana/pkg/cmd github.com/grafana/grafana/pkg/components/apikeygen github.com/grafana/grafana/pkg/components/renderer github.com/grafana/grafana/pkg/events github.com/grafana/grafana/pkg/log github.com/grafana/grafana/pkg/login github.com/grafana/grafana/pkg/metrics github.com/grafana/grafana/pkg/middleware github.com/grafana/grafana/pkg/models github.com/grafana/grafana/pkg/plugins github.com/grafana/grafana/pkg/services/eventpublisher github.com/grafana/grafana/pkg/services/notifications github.com/grafana/grafana/pkg/services/search github.com/grafana/grafana/pkg/services/sqlstore github.com/grafana/grafana/pkg/services/sqlstore/migrations github.com/grafana/grafana/pkg/services/sqlstore/migrator github.com/grafana/grafana/pkg/services/sqlstore/sqlutil github.com/grafana/grafana/pkg/setting github.com/grafana/grafana/pkg/social github.com/grafana/grafana/pkg/util returned exit code 2 debian/rules:15: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 […] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- grafana.2.6.0+dfsg-3.unstable.amd64.log.txt.gz Description: Binary data
Processed: Re: grafana: FTBFS with latest golang-go.crypto
Processing commands for cont...@bugs.debian.org: > block 864793 by 861551 Bug #864793 [grafana] crashes with JavaScript errors Bug #843263 [grafana] grafana: Blank page on new install 864793 was not blocked by any bugs. 864793 was not blocking any bugs. Added blocking bug(s) of 864793: 861551 843263 was not blocked by any bugs. 843263 was not blocking any bugs. Added blocking bug(s) of 843263: 861551 > thanks Stopping processing here. Please contact me if you need assistance. -- 843263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843263 864793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: grafana: Blank page on new install
Processing commands for cont...@bugs.debian.org: > forcemerge 843263 864793 Bug #843263 [grafana] grafana: Blank page on new install Bug #864793 [grafana] crashes with JavaScript errors Severity set to 'important' from 'grave' Merged 843263 864793 > severity 843263 serious Bug #843263 [grafana] grafana: Blank page on new install Bug #864793 [grafana] crashes with JavaScript errors Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 843263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843263 864793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872681: pd-libdir FTBFS with puredata 0.48.0-1
Source: pd-libdir Version: 1.10-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pd-libdir.html ... libdir.c: In function 'libdir_add_to_path': libdir.c:61:9: error: 'sys_searchpath' undeclared (first use in this function); did you mean 'sys_usestdpath'? sys_searchpath = namelist_append(sys_searchpath, dirbuf, 0); ^~
Bug#872682: pd-vbap FTBFS with puredata 0.48.0-1
Source: pd-vbap Version: 1.0.3.2-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pd-vbap.html ... In file included from vbap.c:14:0: s_stuff.h:48:12: error: conflicting types for 'sys_hostfontsize' EXTERN int sys_hostfontsize(int fontsize); ^~~~ In file included from vbap.h:5:0, from vbap.c:13: /usr/include/pd/m_pd.h:436:12: note: previous declaration of 'sys_hostfontsize' was here EXTERN int sys_hostfontsize(int fontsize, int zoom); ^~~~
Bug#872678: gem FTBFS with puredata 0.48.0-1
Source: gem Version: 1:0.93.3-10 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gem.html ... Setup.cpp: In function 'void Gem_addownpath(const char*)': Setup.cpp:96:5: error: 'sys_searchpath' was not declared in this scope sys_searchpath = namelist_append(sys_searchpath, mypath, 0); ^~ Setup.cpp:96:5: note: suggested alternative: 'sys_usestdpath' sys_searchpath = namelist_append(sys_searchpath, mypath, 0); ^~ sys_usestdpath Makefile:804: recipe for target 'libGem_la-Setup.lo' failed make[4]: *** [libGem_la-Setup.lo] Error 1
Bug#872677: pd-pdogg FTBFS with puredata 0.48.0-1
Source: pd-pdogg Version: 0.25.1-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pd-pdogg.html ... In file included from oggread~.c:29:0: s_stuff.h:48:12: error: conflicting types for 'sys_hostfontsize' EXTERN int sys_hostfontsize(int fontsize); ^~~~ In file included from oggread~.c:28:0: /usr/include/pd/m_pd.h:436:12: note: previous declaration of 'sys_hostfontsize' was here EXTERN int sys_hostfontsize(int fontsize, int zoom); ^~~~
Bug#872679: pd-hcs FTBFS with puredata 0.48.0-1
Source: pd-hcs Version: 0.1-3 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pd-hcs.html ... classpath.c: In function 'classpath_rewind': classpath.c:90:22: error: 'sys_searchpath' undeclared (first use in this function); did you mean 'sys_usestdpath'? x->x_top->nl_next = sys_searchpath; ^~ sys_usestdpath classpath.c:90:22: note: each undeclared identifier is reported only once for each function it appears in Makefile:166: recipe for target 'classpath.o' failed make[2]: *** [classpath.o] Error 1
Bug#872673: pd-creb FTBFS with puredata 0.48.0-1
Source: pd-creb Version: 0.9.2+darcs20151027-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pd-creb.html ... setup.c: In function 'creb_class_setup': setup.c:84:5: error: 'sys_searchpath' undeclared (first use in this function); did you mean 'sys_usestdpath'? sys_searchpath = namelist_append(sys_searchpath, libpath, 0); ^~ sys_usestdpath setup.c:84:5: note: each undeclared identifier is reported only once for each function it appears in ../Makefile.config:15: recipe for target 'setup.o' failed make[2]: *** [setup.o] Error 1
Bug#872675: pdp FTBFS with puredata 0.48.0-1
Source: pdp Version: 1:0.14.1-3 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pdp.html ... pdp.c: In function 'pdp_class_setup': pdp.c:143:5: error: 'sys_searchpath' undeclared (first use in this function); did you mean 'sys_usestdpath'? sys_searchpath = namelist_append(sys_searchpath, libpath, 0); ^~ sys_usestdpath pdp.c:143:5: note: each undeclared identifier is reported only once for each function it appears in ../Makefile.config:60: recipe for target 'pdp.o' failed make[3]: *** [pdp.o] Error 1
Bug#872674: puredata-import FTBFS with puredata 0.48.0-1
Source: puredata-import Version: 1.3-3 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/puredata-import.html ... make -j1 make[1]: Entering directory '/build/1st/puredata-import-1.3' cc -I"/usr/include/pd" -Wall -W -g -DPD -DVERSION='"1.3"' -fPIC -O6 -funroll-loops -fomit-frame-pointer -o "import.o" -c "import.c" In file included from import.c:2:0: s_stuff.h:48:12: error: conflicting types for 'sys_hostfontsize' EXTERN int sys_hostfontsize(int fontsize); ^~~~ In file included from import.c:1:0: /usr/include/pd/m_pd.h:436:12: note: previous declaration of 'sys_hostfontsize' was here EXTERN int sys_hostfontsize(int fontsize, int zoom); ^~~~ import.c: In function 'import_new': import.c:112:12: warning: unused variable 'currentdir' [-Wunused-variable] t_symbol *currentdir; ^~ import.c:109:35: warning: unused parameter 's' [-Wunused-parameter] static void *import_new(t_symbol *s, int argc, t_atom *argv) ^ import.c: In function 'import_free': import.c:138:35: warning: unused parameter 'x' [-Wunused-parameter] static void import_free(t_import *x) ^ Makefile:191: recipe for target 'import.o' failed make[1]: *** [import.o] Error 1
Bug#869953: marked as done (budgie-core: Adapt to gnome-settings-daemon 3.24)
Your message dated Sat, 19 Aug 2017 23:34:10 + with message-idand subject line Bug#869953: fixed in budgie-desktop 10.3.1-5 has caused the Debian Bug report #869953, regarding budgie-core: Adapt to gnome-settings-daemon 3.24 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.) -- 869953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: budgie-core Version: 10.2.9-3 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gsd324 Tags: buster budgie-core includes a gnome-session file to allow users to easily log in to Budgie. gnome-settings-daemon 3.24 has split itself into separate binaries and the gnome-session file will no longer work. The new version of gnome-settings-daemon is available for testing in Debian experimental. We intend to upload gnome-settings-daemon 3.24 to Debian unstable about 10 days from now on Sunday, August 6. I suggest uploading the fix to the DELAYED queue for that date so that this transition will be easy and smooth. I also suggest adding an explicit dependency on gnome-settings-daemon 3.24 so that budgie-desktop won't migrate to testing before gnome-settings-daemon 3.24 does. On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Source: budgie-desktop Source-Version: 10.3.1-5 We believe that the bug you reported is fixed in the latest version of budgie-desktop, 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 869...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Mohammed (supplier of updated budgie-desktop 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: Fri, 18 Aug 2017 00:37:52 +0100 Source: budgie-desktop Binary: budgie-core budgie-core-dev budgie-desktop budgie-desktop-doc gir1.2-budgie-desktop-1.0 libbudgie-plugin0 libbudgietheme0 libraven0 Architecture: source Version: 10.3.1-5 Distribution: unstable Urgency: high Maintainer: David Mohammed Changed-By: David Mohammed Description: budgie-core - Core package for Budgie-Desktop budgie-core-dev - Development package for budgie-desktop budgie-desktop - Desktop package for budgie-desktop budgie-desktop-doc - documentation files for the budgie-desktop gir1.2-budgie-desktop-1.0 - GNOME introspection library for budgie-desktop libbudgie-plugin0 - Plugin library for budgie-desktop libbudgietheme0 - Theme library for budgie-desktop libraven0 - Raven library for budgie-desktop Closes: 869953 Changes: budgie-desktop (10.3.1-5) unstable; urgency=high . * Bug fix release - add patch gsd.patch (Closes: #869953) Where gnome-settings-daemon version is greater than libmutter, the build of budgie-desktop results in an invalid gnome-session file. The patch ensures a valid file is created by checking the version of gnome-settings-daemon instead of mutter during the build. * Packaging Changes: - debian/control: Add build dependency for gnome-settings-daemon-dev to ensure the patch can determine the version correctly - debian/control: Fix the Vcs-Git location typo bugie --> budgie Checksums-Sha1: 27e24f29c17e30df69b9c9ce31324f235d32051b 2918 budgie-desktop_10.3.1-5.dsc 7cf37b18efc1a948dba00f316549aa45e3b286af 42204 budgie-desktop_10.3.1-5.debian.tar.xz 9d5800cedeb079e270348b622c7421d7f83d91ba 6813 budgie-desktop_10.3.1-5_source.buildinfo Checksums-Sha256: c5e0b91b0abaa15977f6e1163fc30aa4fa39ffec4608cc8b9b90f9cf1e7f1d8a 2918 budgie-desktop_10.3.1-5.dsc 0d345f1f5df00c1877d212726f6061ad25bdf05c9e77a07706a7baa4f1b5963c 42204 budgie-desktop_10.3.1-5.debian.tar.xz 5400df07934f7145ad314534db57b6d833649dc0332b5a37ca1842692fbbeeb0 6813 budgie-desktop_10.3.1-5_source.buildinfo Files: 9bad81122b9d6e9a07a2bad12461fd28 2918 x11 optional budgie-desktop_10.3.1-5.dsc 4961cdcfe2079ee3f2bb73d4699855d6 42204 x11 optional budgie-desktop_10.3.1-5.debian.tar.xz 7bc02cd522b15b774a2c2fe9425bbac2 6813 x11 optional
Processed: libgmm++-dev requires header that is shipped in libgetfem++-dev
Processing control commands: > affects -1 src:csound Bug #872670 [libgmm++-dev] libgmm++-dev requires header that is shipped in libgetfem++-dev Added indication that 872670 affects src:csound -- 872670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872670: libgmm++-dev requires header that is shipped in libgetfem++-dev
Package: libgmm++-dev Version: 5.2+dfsg1-4 Severity: serious Control: affects -1 src:csound https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/csound.html ... -- Looking for C++ include gmm/gmm.h -- Looking for C++ include gmm/gmm.h - not found ... CMake Error at CMakeLists.txt:108 (message): BUILD_LINEAR_ALGEBRA_OPCODES is enabled, but GMM_HEADER="" ... In file included from /usr/include/gmm/gmm_except.h:42:0, from /usr/include/gmm/gmm_ref.h:46, from /usr/include/gmm/gmm_def.h:40, from /usr/include/gmm/gmm_kernel.h:41, from /usr/include/gmm/gmm.h:40, from /build/1st/csound-6.09.1~dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckIncludeFile.cxx:1: /usr/include/gmm/gmm_std.h:41:10: fatal error: getfem/getfem_arch_config.h: No such file or directory #include ^
Processed: fakechroot FTBFS: t/jemalloc.t hangs with libjemalloc1 3.6.0-10
Processing control commands: > affects -1 src:fakechroot Bug #872669 [libjemalloc1] fakechroot FTBFS: t/jemalloc.t hangs with libjemalloc1 3.6.0-10 Added indication that 872669 affects src:fakechroot -- 872669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872669: fakechroot FTBFS: t/jemalloc.t hangs with libjemalloc1 3.6.0-10
Package: libjemalloc1 Version: 3.6.0-10 Severity: serious Control: affects -1 src:fakechroot https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fakechroot.html ... srcdir=. SEQ= prove -j16 --failures --exec /bin/sh ./t t/host.t ok t/dedotdot.t ok t/00echo.t .. ok t/ftw.t . ok t/java.t ok t/cp.t .. ok t/execlp.t .. ok t/execve-elfloader.t ok t/clearenv.t ok t/execve-null-envp.t ok t/chdir.t ... ok t/mkstemps.t ok t/canonicalize_file_name.t .. ok t/cmd-subst.t ... ok t/popen.t ... ok t/posix_spawn.t . ok t/escape-nested-chroot.t ok t/opendir.t . ok t/posix_spawnp.t ok t/zzarchlinux.t . skipped: TEST_ARCHLINUX is false t/zzdebootstrap.t ... skipped: TEST_DEBOOTSTRAP is false t/fts.t . ok t/statfs.t .. ok t/chroot.t .. ok t/statvfs.t . ok t/mktemp.t .. ok t/pwd.t . ok t/symlink.t . ok t/realpath.t ok t/touch.t ... ok t/system.t .. ok t/test-r.t .. ok t/socket-af_unix.t .. ok t/readlink.t ok Fri Sep 21 21:29:19 UTC 2018 - pbuilder was killed by timeout after 18h. Sat Aug 19 15:06:26 UTC 2017 - total duration: 18h 0m 31s. Reproduced with libjemalloc1 3.6.0-10, no problem with 3.6.0-9.1
Bug#872668: aspcud FTBFS on arm64/armhf with gcc 7
Source: aspcud Version: 1:1.9.1-2 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/buster/arm64/aspcud.html ... cd /build/aspcud-1.9.1/obj-aarch64-linux-gnu/libcudf && /usr/bin/c++ -I/build/aspcud-1.9.1/libcudf/src -I/build/aspcud-1.9.1/libcudf/. -I/build/aspcud-1.9.1/obj-aarch64-linux-gnu/libcudf/src -g -O2 -fdebug-prefix-map=/build/aspcud-1.9.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/cudf-lib.dir/src/critparser_impl.cpp.o -c /build/aspcud-1.9.1/obj-aarch64-linux-gnu/libcudf/src/critparser_impl.cpp critparser_impl.y: In function 'void yy_reduce(yyParser*, int)': critparser_impl.y:59:95: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:60:99: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:60:122: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:67:94: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:79:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:80:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:81:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:82:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:83:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:84:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:85:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:86:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:87:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:88:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:89:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:90:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:91:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:92:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? critparser_impl.y:93:15: error: 'union YYMINORTYPE' has no member named 'yy'; did you mean 'yy0'? libcudf/CMakeFiles/cudf-lib.dir/build.make:198: recipe for target 'libcudf/CMakeFiles/cudf-lib.dir/src/critparser_impl.cpp.o' failed make[3]: *** [libcudf/CMakeFiles/cudf-lib.dir/src/critparser_impl.cpp.o] Error 1 Even though it isn't a segfaultm #872535 has some similarities (lemon + arm* + gcc-7).
Bug#871217: marked as done (openzwave-controlpanel: FTBFS with GCC-7: error: -Wformat-security ignored without -Wformat)
Your message dated Sat, 19 Aug 2017 23:05:03 + with message-idand subject line Bug#871217: fixed in openzwave-controlpanel 0.2a+git20161006.a390f35-2 has caused the Debian Bug report #871217, regarding openzwave-controlpanel: FTBFS with GCC-7: error: -Wformat-security ignored without -Wformat 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.) -- 871217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openzwave-controlpanel Version: 0.2a+git20161006.a390f35-1 Severity: serious Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-7 openzwave-controlpanel FTBFS since GCC-7 was made the default compiler: g++ -g -O2 -fdebug-prefix-map=/build/openzwave-controlpanel-0.2a+git20161006.a390f35=. -fstack-protector-strong -Wformat -Werror=format-security -c -Wall -Wno-unknown-pragmas -Wno-format -I /usr/include/openzwave -I /usr/include/openzwave/command_classes -I /usr/include/openzwave/value_classes -I /usr/include/openzwave/platform -I /usr/include/openzwave/platform/unix -I /usr/include/openzwave/tinyxml -o ozwcp.o ozwcp.cpp cc1plus: error: -Wformat-security ignored without -Wformat [-Werror=format-security] cc1plus: some warnings being treated as errors Makefile:43: recipe for target 'ozwcp.o' failed make[1]: *** [ozwcp.o] Error 1 Note the command has these conflicting flags: -Wformat -Werror=format-security -Wno-format Andreas openzwave-controlpanel_0.2a+git20161006.a390f35-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: openzwave-controlpanel Source-Version: 0.2a+git20161006.a390f35-2 We believe that the bug you reported is fixed in the latest version of openzwave-controlpanel, 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 871...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dara Adib (supplier of updated openzwave-controlpanel 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: Sat, 19 Aug 2017 18:32:25 -0400 Source: openzwave-controlpanel Binary: openzwave-controlpanel Architecture: source amd64 Version: 0.2a+git20161006.a390f35-2 Distribution: unstable Urgency: medium Maintainer: Debian IoT Maintainers Changed-By: Dara Adib Description: openzwave-controlpanel - OpenZWave Control Panel Closes: 871217 Changes: openzwave-controlpanel (0.2a+git20161006.a390f35-2) unstable; urgency=medium . * Append CPPFLAGS to CFLAGS to enable FORTIFY hardening. * Add debian/watch file in case upstream starts releasing. * Override lintian informational tags about spelling. * Update debian/copyright URL to use https. * Add -Wno-format-security flag. (Closes: #871217) * Bump Standards-Version to 4.0.1. Checksums-Sha1: d39b0f50dce719faf9f5f2a27ebf9abf2d66af8b 2314 openzwave-controlpanel_0.2a+git20161006.a390f35-2.dsc 8c6ab64a71cd55d005169197dcb417bfdf057021 5744 openzwave-controlpanel_0.2a+git20161006.a390f35-2.debian.tar.xz 193585884a96c0ac836ce886762640d05a868e0f 235088 openzwave-controlpanel-dbgsym_0.2a+git20161006.a390f35-2_amd64.deb c789173afd2b757db9f70d9fa147fee1ec00fac9 6644 openzwave-controlpanel_0.2a+git20161006.a390f35-2_amd64.buildinfo b2e3b2447fa68e7208af159aba8ef05eacfca52c 54762 openzwave-controlpanel_0.2a+git20161006.a390f35-2_amd64.deb Checksums-Sha256: a12cb31bcf67fdb40ca5ad932401ebeda1d03a911720d1e66c427b6b2571258f 2314 openzwave-controlpanel_0.2a+git20161006.a390f35-2.dsc cea8617b19d1f83a5f982b6354e9aed587e4d75bf34edf0c27fb6750c30c6457 5744 openzwave-controlpanel_0.2a+git20161006.a390f35-2.debian.tar.xz 44ce936d01315bc97df64c6779a5a41e3e635cc024da1d3ec7e04f24b579fd2f 235088 openzwave-controlpanel-dbgsym_0.2a+git20161006.a390f35-2_amd64.deb 087bfb911c81b396cb59636f8c70bb05ad8eb072f547582177a6f8f2e88da1de 6644 openzwave-controlpanel_0.2a+git20161006.a390f35-2_amd64.buildinfo bb1ffc6e0b246bd6b5062971e2730d6c72d19a207ab4addf19dde2b3a44a9ff0 54762
Processed: bump severity of #869953 and add tags
Processing commands for cont...@bugs.debian.org: > severity 869953 grave Bug #869953 [budgie-core] budgie-core: Adapt to gnome-settings-daemon 3.24 Severity set to 'grave' from 'important' > tags 869953 patch sid Bug #869953 [budgie-core] budgie-core: Adapt to gnome-settings-daemon 3.24 Added tag(s) patch and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 869953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872666: [kde-baseapps] KDE packages are broken in Debian sid/buster
Package: kde-baseapps Version: 4:16.08.3-1 Severity: critical Hi, Few days ago I did an upgrade to a VM Debian Sid system and all packages from KDE were uninstalled. My Laptop is running also same Debian but I didn't do a such upgrade because apt dist-upgrade is asking me to uninstall whole KDE. Here is the output of apt dist-upgrade command: root@Adi-Laptop:/home/adrian# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: accountsservice analitza-common apper-data baloo-kf5 breeze-cursor-theme coinor-libcbc3 coinor-libcgl1 coinor-libclp1 coinor-libcoinmp1v5 coinor-libcoinutils3v5 coinor-libosi1v5 cracklib-runtime debconf-kde-data debconf-kde-helper fonts-dustin fonts-hack-ttf fonts-linuxlibertine fonts-open-sans fonts-oxygen fonts-sil-gentium fonts-sil-gentium-basic frameworkintegration gir1.2-atspi-2.0 gir1.2-wnck-3.0 gnome-orca gtk3-engines-breeze hyphen-en-us ieee-data kate5-data kde-cli-tools-data kde-config-gtk-style kde-config-sddm kde-style-breeze kde-style-breeze-qt4 kde-style-qtcurve-qt4 kded5 kdegames-card-data-kf5 kdegames-mahjongg-data-kf5 kdepasswd kf5-kdepim-apps-libs-data kf5-messagelib-data khotkeys khotkeys-data kmenuedit ksysguard ksysguard-data ksysguardd ktnef kwayland-integration kwin-data kwin-decoration-oxygen kwin-style-breeze kwrite kwrited libaccounts-glib0 libaccounts-qt5-1 libaccountsservice0 libanalitza7 libanalitzagui7 libanalitzaplot7 libanalitzawidgets7 libappstreamqt2 libatk-adaptor libbrlapi0.6 libbsh-java libcrack2 libdebconf-kde1 libdirectfb-1.2-9 libdolphinvcs5 libfakekey0 libfreehand-0.1-1 libkaccounts1 libkasten3controllers3 libkasten3core3 libkasten3gui3 libkasten3okteta1core1 libkasten3okteta1gui1 libkdecorations2-5v5 libkdecorations2private5v5 libkf5activitiesstats1 libkf5akonadisearch-bin libkf5akonadisearch-data libkf5akonadisearch-plugins libkf5akonadisearchcore5 libkf5akonadisearchdebug5 libkf5akonadisearchpim5 libkf5akonadisearchxapian5 libkf5baloowidgets-bin libkf5baloowidgets5 libkf5blog5 libkf5bluezqt-data libkf5bluezqt6 libkf5calendarevents5 libkf5calendarsupport-data libkf5declarative-data libkf5eventviews-data libkf5followupreminder5 libkf5gapiblogger5 libkf5gpgmepp-pthread5 libkf5grantleetheme-plugins libkf5grantleetheme5 libkf5idletime5 libkf5jsembed-data libkf5jsembed5 libkf5kcmutils-data libkf5kdepimdbusinterfaces5 libkf5kdgantt2-5 libkf5kiogui5 libkf5kmahjongglib5 libkf5kmanagesieve5 libkf5kontactinterface-data libkf5kontactinterface5 libkf5ksieve-data libkf5ksieve5 libkf5libkdepim-data libkf5libkleo5 libkf5messagecore5 libkf5modemmanagerqt6 libkf5networkmanagerqt6 libkf5people-data libkf5people5 libkf5peoplebackend5 libkf5peoplewidgets5 libkf5qgpgme5 libkf5screen-bin libkf5screen7 libkf5sendlater5 libkf5style5 libkf5syndication5 libkf5sysguard-bin libkf5sysguard-data libkf5tnef5 libkf5waylandclient5 libkf5waylandserver5 libkf5webkit5 libkf5xmlrpcclient-data libkf5xmlrpcclient5 libkfontinst5 libkfontinstui5 libksgrd7 libksignalplotter7 libkwin4-effect-builtins1 libkwineffects9 libkwinglutils9 libkwinxrenderutils9 libkworkspace5-5 liblimba0 libmspub-0.1-1 libokteta2core2 libokteta2gui2 libopenconnect5 liboxygenstyle5-5 liboxygenstyleconfig5-5 libpagemaker-0.0-0 libplasma-geolocation-interface5 libpowerdevilcore2 libpowerdevilui5 libprocesscore7 libprocessui7 libpwquality-common libpwquality1 libqca-qt5-2 libqca-qt5-2-plugins libqgsttools-p1 libqt5clucene5 libqt5concurrent5 libqt5designer5 libqt5designercomponents5 libqt5help5 libqt5multimedia5-plugins libqt5multimediaquick-p5 libqt5multimediawidgets5 libqt5quickwidgets5 libqtcurve-utils2 libreoffice libreoffice-avmedia-backend-gstreamer libreoffice-calc libreoffice-draw libreoffice-help-en-us libreoffice-impress libreoffice-librelogo libreoffice-nlpsolver libreoffice-ogltrans libreoffice-script-provider-bsh libreoffice-script-provider-js libreoffice-script-provider-python libreoffice-wiki-publisher libsane-perl libscim8v5 libsignon-plugins-common1 libsignon-qt5-1 libstoken1 libtaskmanager6 libtomcrypt0 libuv1 libweather-ion7 libwireshark8 libwiretap6 libwnck-3-0 libwnck-3-common libwsutil7 libx265-116 libxcb-cursor0 libxcb-damage0 libxcb-dpms0 libxcb-record0 libzmf-0.0-0 linux-headers-4.11.0-1-amd64 linux-headers-4.11.0-1-common linux-image-4.11.0-1-amd64 lp-solve mythes-en-us nodejs oxygen-sounds parley-data plasma-desktop-data plasma-discover-common polkit-kde-1 powerdevil powerdevil-data pulseaudio-module-gconf python-debianbts python-httplib2 python-pycurl python-pysimplesoap python3-brlapi python3-louis python3-pyatspi python3-software-properties python3-speechd python3-xdg qdbus-qt5 qml-module-org-kde-activities qml-module-org-kde-bluezqt qml-module-org-kde-extensionplugin qml-module-org-kde-kholidays qml-module-org-kde-solid qml-module-qt-labs-folderlistmodel
Processed: found 871514 in 7.1.0-13
Processing commands for cont...@bugs.debian.org: > # > https://buildd.debian.org/status/fetch.php?pkg=aptitude=mips64el=0.8.9-1=1503173356=0 > found 871514 7.1.0-13 Bug #871514 [gcc-7] clamav: FTBFS on mips64el Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks that 1 > 1) Marked as found in versions gcc-7/7.1.0-13. Marked as found in versions gcc-7/7.1.0-13. > thanks Stopping processing here. Please contact me if you need assistance. -- 871514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871514 871538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 871514
Processing commands for cont...@bugs.debian.org: > affects 871514 + src:aptitude Bug #871514 [gcc-7] clamav: FTBFS on mips64el Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks that 1 > 1) Added indication that 871514 affects src:aptitude Added indication that 871538 affects src:aptitude > thanks Stopping processing here. Please contact me if you need assistance. -- 871514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871514 871538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872029: cinnamon-settings-daemon: does not remain running
I fixed this on my cinnamon-only system by removing the gnome-settings-daemon package. The gnome-settings-daemon package kept starting a process that took over xsettings (the process' name ended in gsd-xsettings).
Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
On Sat, Aug 19, 2017 at 11:58:09AM +0200, Andreas Beckmann wrote: > > terminate called after throwing an instance of 'std::logic_error' > > what(): basic_string::_M_construct null not valid > > Could this be related to #871275 "libapt-pkg5.0: requires rebuild > against GCC 7 and symbols/shlibs bump" which was fixed recently in apt? > IIRC this started after making gcc-7 the default ... I'll look if there > are new occurrences of this bug. Unlikely that it is related to this symbol change as it is a single symbol related to URIs, which apt uses while acquiring files, but at the stage packages are installed nothing worries about URIs anymore… A core dump would really be handy. It could still be a problem with gcc or perhaps dpkg changed slightly a log message and apt stumbles over parsing it correctly (althrough, dpkg wasn't uploaded in a while)… or… construction of a std::string's is done all over the place, implicit and explicit, so without details we can't even guess sensibly. Can't really suggest debugging options either, as most of them include the construction of std::string's which could easily hide the problem – and the debug usually involves stuff happening before/after dpkg is called, usually not while it's running, but oh well, we could try -o Debug::pkgDPkgProgressReporting=1 perhaps – that is heavy on string operations through, so that could turn out to be more confusing than helping… (and as said, dpkg hasn't changed in a while). Best regards David Kalnischkies signature.asc Description: PGP signature
Processed: forcibly merging 871275 872201
Processing commands for cont...@bugs.debian.org: > forcemerge 871275 872201 Bug #871275 {Done: Julian Andres Klode} [libapt-pkg5.0] libapt-pkg5.0: requires rebuild against GCC 7 and symbols/shlibs bump Bug #872201 [libapt-pkg5.0] libc-bin: sometimes throws std::logic_error while processing triggers Severity set to 'serious' from 'important' Marked Bug as done Removed indication that 872201 affects piuparts.debian.org Marked as fixed in versions apt/1.5~beta2. Marked as found in versions apt/1.5~beta1. Added tag(s) buster and sid. Bug #871275 {Done: Julian Andres Klode } [libapt-pkg5.0] libapt-pkg5.0: requires rebuild against GCC 7 and symbols/shlibs bump Added tag(s) help and moreinfo. Merged 871275 872201 > thanks Stopping processing here. Please contact me if you need assistance. -- 871275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871275 872201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
Processing control commands: > forcemerge 871275 -1 Bug #871275 {Done: Julian Andres Klode} [libapt-pkg5.0] libapt-pkg5.0: requires rebuild against GCC 7 and symbols/shlibs bump Unable to merge bugs because: package of #872201 is 'libc-bin' not 'libapt-pkg5.0' Failed to forcibly merge 871275: Did not alter merged bugs. -- 871275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871275 872201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#853316: marked as done (aptitude: ftbfs with GCC-7)
Your message dated Sat, 19 Aug 2017 18:19:31 + with message-idand subject line Bug#853316: fixed in aptitude 0.8.9-1 has caused the Debian Bug report #853316, regarding aptitude: 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.) -- 853316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:aptitude Version: 0.8.5-1 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/aptitude_0.8.5-1_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 [...] g++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I../../src -I.. -I.. -I../../src -I../.. -I../../src -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -DHELPDIR=\"/usr/share/aptitude\" -DPKGDATADIR=\"/usr/share/aptitude\" -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/lib/x86_64-linux-gnu/cwidget -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -Wall -c -o download_list.o ../../src/download_list.cc g++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I../../src -I.. -I.. -I../../src -I../.. -I../../src -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -DHELPDIR=\"/usr/share/aptitude\" -DPKGDATADIR=\"/usr/share/aptitude\" -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/lib/x86_64-linux-gnu/cwidget -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -Wall -c -o download_thread.o ../../src/download_thread.cc g++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I../../src -I.. -I.. -I../../src -I../.. -I../../src -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -DHELPDIR=\"/usr/share/aptitude\" -DPKGDATADIR=\"/usr/share/aptitude\" -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/lib/x86_64-linux-gnu/cwidget -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -Wall -c -o load_config.o ../../src/load_config.cc g++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I../../src -I.. -I.. -I../../src -I../.. -I../../src -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -DHELPDIR=\"/usr/share/aptitude\" -DPKGDATADIR=\"/usr/share/aptitude\" -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/lib/x86_64-linux-gnu/cwidget -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -Wall -c -o load_grouppolicy.o ../../src/load_grouppolicy.cc g++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I../../src -I.. -I.. -I../../src -I../.. -I../../src -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -DHELPDIR=\"/usr/share/aptitude\" -DPKGDATADIR=\"/usr/share/aptitude\" -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/lib/x86_64-linux-gnu/cwidget -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security
Bug#872647: ruby-puppet-forge FTBFS: Could not find 'faraday_middleware' (< 0.11.0, >= 0.9.0) - did find: [faraday_middleware-0.12.2]
Source: ruby-puppet-forge Version: 2.2.7-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-puppet-forge.html ... /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 'faraday_middleware' (< 0.11.0, >= 0.9.0) - did find: [faraday_middleware-0.12.2] (Gem::LoadError) ...
Processed: Fix for the conky FTBFS with gcc 7
Processing control commands: > tags -1 patch Bug #853353 [src:conky] conky: ftbfs with GCC-7 Added tag(s) patch. -- 853353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#853353: Fix for the conky FTBFS with gcc 7
Control: tags -1 patch A fix for the conky FTBFS with gcc 7 is attached. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed Description: src/luamm.hh: #include Required for building with gcc 7. Author: Adrian BunkBug-Debian: https://bugs.debian.org/853353 --- conky-1.10.6.orig/src/luamm.hh +++ conky-1.10.6/src/luamm.hh @@ -26,6 +26,7 @@ #include #include #include +#include #include #include
Processed: Already fixed upstream
Processing commands for cont...@bugs.debian.org: > tags 853614 fixed-upstream Bug #853614 [src:pingus] pingus: ftbfs with GCC-7 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 853614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#853397: marked as done (fcgiwrap: ftbfs with GCC-7)
Your message dated Sat, 19 Aug 2017 16:04:09 + with message-idand subject line Bug#853397: fixed in ucommon 7.0.0-10 has caused the Debian Bug report #853397, regarding fcgiwrap: 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.) -- 853397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fcgiwrap Version: 1.1.0-9 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/fcgiwrap_1.1.0-9_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 [...] checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for unistd.h... (cached) yes checking for stdbool.h that conforms to C99... yes checking for _Bool... yes checking for pid_t... yes checking for size_t... yes checking for ssize_t... yes checking vfork.h usability... no checking vfork.h presence... no checking for vfork.h... no checking for fork... yes checking for vfork... yes checking for working fork... yes checking for working vfork... (cached) yes checking whether lstat correctly handles trailing slash... yes checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... yes checking for strchr... yes checking for strdup... yes checking for strrchr... yes checking for dup2... yes checking for putenv... yes checking for select... yes checking for setenv... yes checking for strerror... yes configure: creating ./config.status config.status: creating Makefile config.status: creating config.h configure: WARNING: unrecognized options: --disable-silent-rules, --disable-maintainer-mode, --disable-dependency-tracking make[1]: Leaving directory '/<>' dh_auto_build make -j1 make[1]: Entering directory '/<>' cc -std=gnu99 -Wall -Wextra -Werror -pedantic -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now fcgiwrap.c -lfcgi -lsystemd -o fcgiwrap fcgiwrap.c: In function 'handle_fcgi_request': fcgiwrap.c:573:4: error: this statement may fall through [-Werror=implicit-fallthrough=] cgi_error("502 Bad Gateway", "Cannot execute script", filename); ^~~ fcgiwrap.c:575:3: note: here default: /* parent */ ^~~ cc1: all warnings being treated as errors : recipe for target 'fcgiwrap' failed make[1]: *** [fcgiwrap] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 debian/rules:6: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 --- End Message --- --- Begin Message --- Source: ucommon Source-Version: 7.0.0-10 We believe that the bug you reported is fixed in the latest version of ucommon, 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. Peter Colberg (supplier of updated ucommon 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
Bug#853548: Patch
Control: tag -1 patch Hi, just making the inline functions static inline gets rid of the warnings 'A' is static but used in inline function 'B' which is not static and fixes the build. Patch attached. Cheers, -Hilko >From 7251d5b20ea2c0e8245556d4eb3b3327c26fcfd7 Mon Sep 17 00:00:00 2001 From: Hilko BengenDate: Sat, 19 Aug 2017 17:03:16 +0200 Subject: [PATCH] make some functions static --- g3/g3cat.c | 3 +++ g3/pbm2g3.c | 6 +++--- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/g3/g3cat.c b/g3/g3cat.c index 8a4b708..4205d33 100644 --- a/g3/g3cat.c +++ b/g3/g3cat.c @@ -67,6 +67,7 @@ void putcode _P2( (code, len), int code, int len ) } #ifdef __GNUC__ +static inline #endif void putwhitespan _P1( (l), int l ) @@ -98,6 +99,7 @@ void putwhitespan _P1( (l), int l ) } #ifdef __GNUC__ +static inline #endif void putblackspan _P1( (l), int l ) @@ -129,6 +131,7 @@ void putblackspan _P1( (l), int l ) } #ifdef __GNUC__ +static inline #endif void puteol _P0( void ) /* write byte-aligned EOL */ diff --git a/g3/pbm2g3.c b/g3/pbm2g3.c index 283a728..1641782 100644 --- a/g3/pbm2g3.c +++ b/g3/pbm2g3.c @@ -40,6 +40,7 @@ static unsigned int out_hibit = 0; static int out_byte_tab[ 256 ]; /* for g3 byte reversal */ #ifdef __GNUC__ +static inline #endif void putcode _P2( (code, len), int code, int len ) @@ -60,6 +61,7 @@ void putcode _P2( (code, len), int code, int len ) } #ifdef __GNUC__ +static inline #endif void puteol _P0( void ) /* write byte-aligned EOL */ @@ -69,6 +71,7 @@ void puteol _P0( void ) /* write byte-aligned EOL */ } #ifdef __GNUC__ +static inline #endif void putwhitespan _P1( (l), int l ) @@ -99,9 +102,6 @@ void putwhitespan _P1( (l), int l ) putcode( t_white[l].bit_code, t_white[l].bit_length ); } -#ifdef __GNUC__ -inline -#endif void putblackspan _P1( (l), int l ) { if ( l >= 64 ) -- 2.14.1
Processed: Patch
Processing control commands: > tag -1 patch Bug #853548 [src:mgetty] mgetty: ftbfs with GCC-7 Added tag(s) patch. -- 853548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872635: util-linux: FTBFS on armel: test failure
Source: util-linux Version: 2.29.2-4 Severity: serious Justification: FTBFS Hi, Your package FTBFS on armel, hopefully I've managed to pick the right part: | ~~~ dns long ~~~ | ~~~ dns host last ~~~ | FAILED (utmp/last-dns) | = script: /<>/tests/ts/utmp/last = | = OUTPUT = | 1~~~ dns short ~~~ | 2IPv4 root dns-server Wed Aug 28 13:00 - 14:00 (01:00) | 3 | 4wtmp-a begins Wed Aug 28 03:00:00 2013 | 5~~~ dns long ~~~ | 6IPv4 root dns-server Wed Aug 28 13:00 - 14:00 (01:00) | 7 | 8wtmp-a begins Wed Aug 28 03:00:00 2013 | 9~~~ dns host last ~~~ | 10IPv4 root Wed Aug 28 13:00 - 14:00 (01:00) dns-server | 11 | 12wtmp-a begins Wed Aug 28 03:00:00 2013 | = EXPECTED === | 1~~~ dns short ~~~ | 2IPv4 root a.root-servers.n Wed Aug 28 13:00 - 14:00 (01:00) | 3 | 4wtmp-a begins Wed Aug 28 03:00:00 2013 | 5~~~ dns long ~~~ | 6IPv4 root a.root-servers.net Wed Aug 28 13:00 - 14:00 (01:00) | 7 | 8wtmp-a begins Wed Aug 28 03:00:00 2013 | 9~~~ dns host last ~~~ | 10IPv4 root Wed Aug 28 13:00 - 14:00 (01:00) a.root-servers.net | 11 | 12wtmp-a begins Wed Aug 28 03:00:00 2013 | = O/E diff === | --- /<>/tests/output/utmp/last-dns 2017-08-17 13:37:15.211650587 + | +++ /<>/tests/expected/utmp/last-dns 2016-11-02 12:03:35.569215943 + | @@ -1,12 +1,12 @@ | ~~~ dns short ~~~ | -IPv4 root dns-server Wed Aug 28 13:00 - 14:00 (01:00) | +IPv4 root a.root-servers.n Wed Aug 28 13:00 - 14:00 (01:00) | | wtmp-a begins Wed Aug 28 03:00:00 2013 | ~~~ dns long ~~~ | -IPv4 root dns-server Wed Aug 28 13:00 - 14:00 (01:00) | +IPv4 root a.root-servers.net Wed Aug 28 13:00 - 14:00 (01:00) | | wtmp-a begins Wed Aug 28 03:00:00 2013 | ~~~ dns host last ~~~ | -IPv4 root Wed Aug 28 13:00 - 14:00 (01:00) dns-server | +IPv4 root Wed Aug 28 13:00 - 14:00 (01:00) a.root-servers.net | | wtmp-a begins Wed Aug 28 03:00:00 2013 | == | : nodns ...~~~ basic output ~~~ | ~~~ include system ~~~ | ~~~ show ip ~~~ | ~~~ no host ~~~ | ~~~ full times shortopt ~~~ | ~~~ full times longopt ~~~ | ~~~ no time ~~~ | ~~~ iso-8601 time ~~~ | ~~~ since and until ~~~ | ~~~ present ~~~ | OK |... FAILED (1 from 2 sub-tests) | = script: /<>/tests/ts/utmp/last = | = OUTPUT = | = EXPECTED === | = O/E diff === | == | | script: /<>/tests/ts/utmp/last-ipv6 | sub dir: /<>/tests/ts/utmp | top dir: /<>/tests |self: /<>/tests/ts/utmp | test name: last-ipv6 | test desc: last ipv6 | component: utmp | namespace: utmp/last-ipv6 | verbose: yes | output: /<>/tests/output/utmp/last-ipv6 |valgrind: /<>/tests/output/utmp/last-ipv6.vgdump |expected: /<>/tests/expected/utmp/last-ipv6 | mountpoint: /<>/tests/output/utmp/last-ipv6-mnt | | utmp: last ipv6 ... | : dns ...~~~ dns short ~~~ | ~~~ dns long ~~~ […] | - | 1 tests of 186 FAILED | - | Makefile:12092: recipe for target 'check-local-tests' failed | make[5]: *** [check-local-tests] Error 1 | make[5]: Leaving directory '/<>' | Makefile:11734: recipe for target 'check-am' failed | make[4]: *** [check-am] Error 2 | make[4]: Leaving directory '/<>' | Makefile:11445: recipe for target 'check-recursive' failed | make[3]: *** [check-recursive] Error 1 | make[3]: Leaving directory '/<>' | Makefile:11738: recipe for target 'check' failed | make[2]: *** [check] Error 2 | make[2]: Leaving directory '/<>' | dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2 | debian/rules:159: recipe for target 'override_dh_auto_test' failed | make[1]: *** [override_dh_auto_test] Error 2 | make[1]: Leaving directory '/<>' | debian/rules:47: recipe for target 'build-arch' failed | make: *** [build-arch] Error 2 | dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Full build log: https://buildd.debian.org/status/fetch.php?pkg=util-linux=armel=2.29.2-4=1502977052=0 KiBi.
Bug#853339: Upstream fix for the bwm-ng FTBFS with gcc 7
Thanks to everyone involved, i will do an upload today, after i get home, i'm currently at a Debian Day party :) Oh, and sorry for taking so long to reply :(, although i was aware of this bug as soon as it was reported, i didn't took the time to deal with this, so again thanks a lot for the help. Samuel Henrique
Bug#872598: udev-udeb: no input in graphical installer
On Sat, Aug 19, 2017 at 9:38 AM, Cyril Bruleboiswrote: > Control: tag -1 patch > > Hi, > > (Again, please keep debian-boot@ in copy.) > > Raphael Hertzog (2017-08-19): >> > I've only quickly glanced at the contents of both packages, and >> > debdiff mentions no obvious issues (file lists are the same). >> >> I believe this is precisely the problem. The new udev-udeb should >> include a new file: >> diff --git a/debian/udev-udeb.install b/debian/udev-udeb.install >> index 6a8e2108f..6758fef06 100644 >> --- a/debian/udev-udeb.install >> +++ b/debian/udev-udeb.install >> @@ -5,6 +5,7 @@ lib/udev/ata_id >> lib/udev/scsi_id >> lib/udev/cdrom_id >> lib/udev/rules.d/50-udev-default.rules >> +lib/udev/rules.d/60-input-id.rules >> lib/udev/rules.d/60-cdrom_id.rules >> lib/udev/rules.d/60-persistent-input.rules >> lib/udev/rules.d/60-persistent-storage.rules >> >> I won't have the time to test this now but I believe it's the problem. > > That's absolutely correct. I've started by copying the file manually into > the netboot-gtk mini.iso, and confirmed the fix. To be extra sure, I've > rebuilt a systemd package with your change, and used the new udev udebs > for a clean build, and that works as well. > > A timely fix would be appreciated, the breakage(s) in the graphical > installer prevented us from releasing debian-installer over the past few > weeks, and it would be great not to wait too long before we're able to do > so, esp. with linux 4.12.6-1 having reached testing lately. > > Thinking about this, I'll check with debian-release@ and I might just > freeze all udeb-producing packages right away. Winter has come. > > >> It would be nice to have a fixed udev soon. Thank you Cyril for the >> investigation! >> >> I wonder if it would be possible to have autopkgtest tests covering >> udev-udeb... > > I'm still new to the whole autopkgtest thing, but from where I stand, the > fact d-i is broken has been known for quite a while; the core issue is > that nobody investigated this before I found some time. An easy way to be > more proactive on the systemd side would be to make sure that new (and/or > deleted) files in the udev and libudev1 binaries are detected by > maintainers (esp. since udev.install uses wildcards for rules files, while > udev-udeb.rules uses a static list), so that the update can be propagated > to the udebs if relevant. --fail-missing is broken on the udeb builds at the moment, so it is not enabled. I'll try to fix this and enable it. This should help catch these sort of issues in the future. -- Saludos, Felipe Sateler
Bug#853639: Fix for the regina-normal FTBFS with gcc 7
On Sat, Aug 19, 2017 at 02:20:35AM +, Benjamin Burton wrote: > Hi Adrian, Hi Ben, > > A fix for the regina-normal FTBFS with gcc 7 is attached. > > Having just uploaded the fix that has been sitting on my hard drive while I > was on holiday all week, I realised that you had also sent in a patch for > this (which of course is the same one-liner as mine). > > Apologies for the duplicated effort, and thanks for looking into this. no problem, the fix is now in unstable so everything is fine. > - Ben. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Re: Bug#872532: w3m bricked: symbol lookup error: w3m: undefined symbol: Gpm_Wgetch
Processing control commands: > severity -1 important Bug #872532 [w3m] w3m bricked: symbol lookup error: w3m: undefined symbol: Gpm_Wgetch Severity set to 'important' from 'grave' -- 872532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872532: w3m bricked: symbol lookup error: w3m: undefined symbol: Gpm_Wgetch
Control: severity -1 important On August 18, 2017 at 3:50PM +0800, jidanni (at jidanni.org) wrote: > w3m: symbol lookup error: w3m: undefined symbol: Gpm_Wgetch > APT prefers experimental > APT policy: (990, 'experimental'), (500, 'unstable') > ii libgpm21.20.7-1 This problem seems to be caused with the experimental version of libgpm2. The current sid looks OK. Thanks, -- Tatsuya Kinoshita pgpFy0zxs7GWK.pgp Description: PGP signature
Processed: closing 871362
Processing commands for cont...@bugs.debian.org: > close 871362 Bug #871362 [src:spatial4j] spatial4j: FTBFS: [[1;31mERROR[m] Failed to execute goal [32morg.apache.maven.plugins:maven-jar-plugin:3.0.2:jar[m [1m(attach-sources)[m on project [36mspatial4j[m: [1;31mYou have to use a classifier to attach supplemental artifacts to the project instead of replacing them.[m -> [1m[Help 1][m Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 871362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872378: fenrir.deb: No speech after enabling fenrir to start inconcial.
matthew dyer, on sam. 19 août 2017 09:01:15 -0400, wrote: > This was a fresh install of Fenrir from the deian uunstable repo. I simply > disabled espeakup from starting and enabled Fenrir to start and rebooted the > system and got no speech in the conciel. HTH. Could you try to downgrade to version 1.05-1 so as to check whether it's only version 1.06-1 which has the issue? Samuel
Bug#872598: udev-udeb: no input in graphical installer
Am 19.08.2017 um 14:38 schrieb Cyril Brulebois: > A timely fix would be appreciated, the breakage(s) in the graphical > installer prevented us from releasing debian-installer over the past few > weeks, and it would be great not to wait too long before we're able to do > so, esp. with linux 4.12.6-1 having reached testing lately. I might have time for that mid next week. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#872378: fenrir.deb: No speech after enabling fenrir to start inconcial.
Hi, Sent from Mail for Windows 10 From: Samuel Thibault Sent: Saturday, August 19, 2017 2:39 AM To: Matthew Dyer; 872...@bugs.debian.org Subject: Bug#872378: fenrir.deb: No speech after enabling fenrir to start inconcial. Hello, Matthew Dyer, on mer. 16 août 2017 18:49:38 -0400, wrote: >* What led up to the situation? > I disabled espeakup.service then enabled fenrir.service >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? > Fenrir did not speak after rebooting the system. >* What outcome did you expect instead? > Fenrir should have spoken after logining to my consel2 Is this only with version 1.06-1 of fenrir, or does it happen also with version 1.05-1? This was a fresh install of Fenrir from the deian uunstable repo. I simply disabled espeakup from starting and enabled Fenrir to start and rebooted the system and got no speech in the conciel. HTH. Matthew Samuel ___ Pkg-a11y-devel mailing list pkg-a11y-de...@lists.alioth.debian.org https://lists.alioth.debian.org/mailman/listinfo/pkg-a11y-devel
Bug#872598: udev-udeb: no input in graphical installer
Control: tag -1 patch Hi, (Again, please keep debian-boot@ in copy.) Raphael Hertzog(2017-08-19): > > I've only quickly glanced at the contents of both packages, and > > debdiff mentions no obvious issues (file lists are the same). > > I believe this is precisely the problem. The new udev-udeb should > include a new file: > diff --git a/debian/udev-udeb.install b/debian/udev-udeb.install > index 6a8e2108f..6758fef06 100644 > --- a/debian/udev-udeb.install > +++ b/debian/udev-udeb.install > @@ -5,6 +5,7 @@ lib/udev/ata_id > lib/udev/scsi_id > lib/udev/cdrom_id > lib/udev/rules.d/50-udev-default.rules > +lib/udev/rules.d/60-input-id.rules > lib/udev/rules.d/60-cdrom_id.rules > lib/udev/rules.d/60-persistent-input.rules > lib/udev/rules.d/60-persistent-storage.rules > > I won't have the time to test this now but I believe it's the problem. That's absolutely correct. I've started by copying the file manually into the netboot-gtk mini.iso, and confirmed the fix. To be extra sure, I've rebuilt a systemd package with your change, and used the new udev udebs for a clean build, and that works as well. A timely fix would be appreciated, the breakage(s) in the graphical installer prevented us from releasing debian-installer over the past few weeks, and it would be great not to wait too long before we're able to do so, esp. with linux 4.12.6-1 having reached testing lately. Thinking about this, I'll check with debian-release@ and I might just freeze all udeb-producing packages right away. Winter has come. > It would be nice to have a fixed udev soon. Thank you Cyril for the > investigation! > > I wonder if it would be possible to have autopkgtest tests covering > udev-udeb... I'm still new to the whole autopkgtest thing, but from where I stand, the fact d-i is broken has been known for quite a while; the core issue is that nobody investigated this before I found some time. An easy way to be more proactive on the systemd side would be to make sure that new (and/or deleted) files in the udev and libudev1 binaries are detected by maintainers (esp. since udev.install uses wildcards for rules files, while udev-udeb.rules uses a static list), so that the update can be propagated to the udebs if relevant. I'm fine with setting up a check through a cron job on d-i.debian.org so as to avoid putting the burden on systemd maintainers. The feedback loop might take a few hours/days after an upload with such a change, but that would make it obvious that something “important” changed, and would speed up understanding such regressions. KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#872598: udev-udeb: no input in graphical installer
Processing control commands: > tag -1 patch Bug #872598 [udev-udeb] udev-udeb: no input in graphical installer Added tag(s) patch. -- 872598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872613: [Pkg-javascript-devel] Bug#872613: node-mocha FTBFS with nodejs 6.11.2: test failures
Hi, Le 19/08/2017 à 13:10, Adrian Bunk a écrit : > Source: node-mocha > Version: 1.20.1-7 > Severity: serious > Tags: buster sid > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-mocha.html > > ... > [31m 4 failing[0m > > [0m 1) Suite .beforeAll() wraps the passed in function in a Hook adds it to > _beforeAll: > > [31mAssertionError: expected '"before all" hook: fn' to be '"before > all" hook'[0m Those aren't difficult issues : the new nodejs gives a more precise answer, so the tests just have to be adapted to that. Perhaps updating to a newer mocha will also help (bug #868318). Snark on #debian-js
Bug#872565: marked as done (encfs: FTBFS on mips, mipsel: undefined reference to `__atomic_store_8')
Your message dated Sat, 19 Aug 2017 11:19:10 + with message-idand subject line Bug#872565: fixed in encfs 1.9.2-2 has caused the Debian Bug report #872565, regarding encfs: FTBFS on mips, mipsel: undefined reference to `__atomic_store_8' 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.) -- 872565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: encfs Version: 1.9.2-1 Severity: serious Tags: sid buster Hi, ensfc FTBFS on mips, mipsel and various ports architectures with the error: > libencfs.so.1.9.2: undefined reference to `__atomic_store_8' > libencfs.so.1.9.2: undefined reference to `__atomic_fetch_add_8' > collect2: error: ld returned 1 exit status This happens because those architectures do not have native 64-bit atomic instructions and instead call out to libatomic to provide emulations of them. To allow linking on these architecture you must link against libatomic. One option is to add the -latomic to LDFLAGS in the Debian package, or I could probably come up with a patch to be applied upstream which will link only on the architectures it's needed. Note there is an upstream GCC bug about doing all this in the toolchain, but for the moment it has to be done per package: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358 Thanks, James signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: encfs Source-Version: 1.9.2-2 We believe that the bug you reported is fixed in the latest version of encfs, 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 872...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Eduard Bloch (supplier of updated encfs 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: SHA256 Format: 1.8 Date: Sat, 19 Aug 2017 12:39:00 +0200 Source: encfs Binary: encfs Architecture: source Version: 1.9.2-2 Distribution: unstable Urgency: low Maintainer: Eduard Bloch Changed-By: Eduard Bloch Description: encfs - encrypted virtual filesystem Closes: 855365 871270 872332 872565 Changes: encfs (1.9.2-2) unstable; urgency=low . * Move encfs library to a custom folder (closes: #871270) * linkatomic.patch: attempt to link with libatomic where available but reducing linker references where possible (closes: #872565) * Swedish translation update by Jonatan Nyberg (closes: #855365) * Fixed references to deprecated fuse-utils package (closes: #872332) Checksums-Sha1: 24b9e0a0bdaf5b4680ff3f1eb245b74c560202f5 1953 encfs_1.9.2-2.dsc b86d4e36482f059964af0ed5b5bfae3f1d00bef8 12988 encfs_1.9.2-2.debian.tar.xz 550e9f0c98133b06bf96e02ad2a76eefe2e839cf 7885 encfs_1.9.2-2_source.buildinfo Checksums-Sha256: fdfcf33f3f381a16f904771cc8d679844331dafe228dea75b1df0fb7f591e3f6 1953 encfs_1.9.2-2.dsc 01d372c9d18dc70db5f5b19ea95cb44fd90cf8bb530c72ad747aa4c0a35e77cd 12988 encfs_1.9.2-2.debian.tar.xz 3ee3f39013fbef4b394c959f57457f17b98f45344c76c1c2da6e3bfadc7ac766 7885 encfs_1.9.2-2_source.buildinfo Files: bbf46549e5881538d8f442a1465ccfc3 1953 utils optional encfs_1.9.2-2.dsc 0737f20961590861d4ff18844236f3af 12988 utils optional encfs_1.9.2-2.debian.tar.xz f7f5410509640f067cd38abfeaa0c44e 7885 utils optional encfs_1.9.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEZI3Zj0vEgpAXyw40aXQOXLNf7DwFAlmYF94ACgkQaXQOXLNf 7DzrshAAm3vYA/6k3Wfl/Ll1w2rwpupZ/Jkffyu8FneGvkTzPGduEWT6Ia6QTJ4H eRGD+2ged/rg9L8aURDulL5uFWPaMZvV6m/fM21+C1M7yZxpG3bWzIQR3EB+Brbt +ucqmUNzUXod2kxqt6JRiD+UT2arxGKN+6XjaILBEGhJjp6HywJ9S2Qic5rd/fL/ xuX01S5d8gWywrnrpTUdpnOH6AipFDVD7h2wJlmeJORE08m5c45dD6CoRyM4gplX i2+844avTdsTHtYKPoaO+H3oqoY9R5ZUKIeNADmzfCz37rxj2FhOZNIXfBffBKap 3wFpbDIFx4YcjsK483ZBHjqbQORdIxE8hXpIb45YWq2vqPD0WuWv5oVNuOVuxaV6 mryvBQqzHrZ/fytxlBLyWXc7m2Vm0vaC9U3C+WEXCWhcKGF93nVzBXcF9cwxJPd5 4ryK2YKnPEpa205dl6BpI2gNPbEATCCF+VFumwufP9kgAcOE13AgVix2uizEpPAn qxyni7nOhp0GTCGvCmfSTphXsuLN8LFCUexEcV8Vai5ZJB1onxburFTccl5X0sfc /7zJrx9Xr8FH61s598DnuH+VjIQ/CCCgmUr67S9tpOL6QFIJllez2nxEuEI6m8T2
Bug#871270: marked as done (encfs: installs private library in public directory)
Your message dated Sat, 19 Aug 2017 11:19:10 + with message-idand subject line Bug#871270: fixed in encfs 1.9.2-2 has caused the Debian Bug report #871270, regarding encfs: installs private library in public directory 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.) -- 871270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: encfs Version: 1.9.2-1 Severity: serious Tags: sid buster User: debian-...@lists.debian.org Usertags: gcc-7-op-mangling Hi, It appears that your package provides an external symbol that is affected by the recent name mangling changes in GCC 7. See: https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling In GCC 7, the name mangling for C++ conversion operators which return a type using the abi_tag attribute (most commonly std::string) has changed. When your library is compiled with GCC 7, it will now emit two symbols for the conversion operator using the new and old naming. Executables compiled with GCC 7 will always use the new symbol, while old executables compiled using <= GCC 6 will use the old symbol. For new executables to build without undefined references, your library will need rebuilding with GCC 7. To ensure that new executables will pull in the newer version of the library built with GCC 7: - Your library package should Build-Depend on g++ (>= 4:7). - If your package provides a symbols file, ensure that the new conversion operator symbols have a version matching the version this bug is fixed in (including the Debian revision and tilde if necessary). Using apt as an example (debian/libapt-pkg5.0.symbols): (c++)"URI::operator std::__cxx11::basic_string [abi:cxx11]()@APTPKG_5.0" 0.8.0 + (c++)"URI::operator std::__cxx11::basic_string ()@APTPKG_5.0" 1.5~beta2~ Where "1.5~beta2" is the version this bug was fixed in. - If your package does not provide a symbols file, add a dh_makeshlibs override so that tight enough dependencies are generated. Using libebml as an example (debian/rules): + override_dh_makeshlibs: + # For new symbols when compiled with GCC 7 + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)' Where "1.3.4-2" is the version this bug was fixed in. - If your package is about to be renamed due to an upstream SONAME bump, you do not need to add any special symbols handling. If you would like to know the exact name of the new symbols, using "abipkgdiff" from abigail-tools might be able to help. Thanks, James --- End Message --- --- Begin Message --- Source: encfs Source-Version: 1.9.2-2 We believe that the bug you reported is fixed in the latest version of encfs, 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 871...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Eduard Bloch (supplier of updated encfs 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: SHA256 Format: 1.8 Date: Sat, 19 Aug 2017 12:39:00 +0200 Source: encfs Binary: encfs Architecture: source Version: 1.9.2-2 Distribution: unstable Urgency: low Maintainer: Eduard Bloch Changed-By: Eduard Bloch Description: encfs - encrypted virtual filesystem Closes: 855365 871270 872332 872565 Changes: encfs (1.9.2-2) unstable; urgency=low . * Move encfs library to a custom folder (closes: #871270) * linkatomic.patch: attempt to link with libatomic where available but reducing linker references where possible (closes: #872565) * Swedish translation update by Jonatan Nyberg (closes: #855365) * Fixed references to deprecated fuse-utils package (closes: #872332) Checksums-Sha1: 24b9e0a0bdaf5b4680ff3f1eb245b74c560202f5 1953 encfs_1.9.2-2.dsc b86d4e36482f059964af0ed5b5bfae3f1d00bef8 12988 encfs_1.9.2-2.debian.tar.xz 550e9f0c98133b06bf96e02ad2a76eefe2e839cf 7885 encfs_1.9.2-2_source.buildinfo Checksums-Sha256: fdfcf33f3f381a16f904771cc8d679844331dafe228dea75b1df0fb7f591e3f6 1953 encfs_1.9.2-2.dsc
Bug#872613: node-mocha FTBFS with nodejs 6.11.2: test failures
Source: node-mocha Version: 1.20.1-7 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-mocha.html ... [31m 4 failing[0m [0m 1) Suite .beforeAll() wraps the passed in function in a Hook adds it to _beforeAll: [31mAssertionError: expected '"before all" hook: fn' to be '"before all" hook'[0m [42m+ expected[0m [41m- actual[0m [41m-"\"before all\" hook: fn"[0m [42m+"\"before all\" hook"[0m [0m[90m at Assertion.fail (/usr/lib/nodejs/should/lib/assertion.js:92:17) at Assertion.value (/usr/lib/nodejs/should/lib/assertion.js:164:19) at Context. (/build/1st/node-mocha-1.20.1/test/suite.js:140:36) at callFn (/build/1st/node-mocha-1.20.1/lib/runnable.js:223:21) at Test.Runnable.run (/build/1st/node-mocha-1.20.1/lib/runnable.js:216:7) at Runner.runTest (/build/1st/node-mocha-1.20.1/lib/runner.js:373:10) at /build/1st/node-mocha-1.20.1/lib/runner.js:451:12 at next (/build/1st/node-mocha-1.20.1/lib/runner.js:298:14) at /build/1st/node-mocha-1.20.1/lib/runner.js:308:7 at next (/build/1st/node-mocha-1.20.1/lib/runner.js:246:23) at Immediate. (/build/1st/node-mocha-1.20.1/lib/runner.js:275:5) at runCallback (timers.js:672:20) at tryOnImmediate (timers.js:645:5) at processImmediate [as _immediateCallback] (timers.js:617:5) [0m [0m 2) Suite .afterAll() wraps the passed in function in a Hook adds it to _afterAll: [31mAssertionError: expected '"after all" hook: fn' to be '"after all" hook'[0m [42m+ expected[0m [41m- actual[0m [41m-"\"after all\" hook: fn"[0m [42m+"\"after all\" hook"[0m [0m[90m at Assertion.fail (/usr/lib/nodejs/should/lib/assertion.js:92:17) at Assertion.value (/usr/lib/nodejs/should/lib/assertion.js:164:19) at Context. (/build/1st/node-mocha-1.20.1/test/suite.js:175:35) at callFn (/build/1st/node-mocha-1.20.1/lib/runnable.js:223:21) at Test.Runnable.run (/build/1st/node-mocha-1.20.1/lib/runnable.js:216:7) at Runner.runTest (/build/1st/node-mocha-1.20.1/lib/runner.js:373:10) at /build/1st/node-mocha-1.20.1/lib/runner.js:451:12 at next (/build/1st/node-mocha-1.20.1/lib/runner.js:298:14) at /build/1st/node-mocha-1.20.1/lib/runner.js:308:7 at next (/build/1st/node-mocha-1.20.1/lib/runner.js:246:23) at Immediate. (/build/1st/node-mocha-1.20.1/lib/runner.js:275:5) at runCallback (timers.js:672:20) at tryOnImmediate (timers.js:645:5) at processImmediate [as _immediateCallback] (timers.js:617:5) [0m [0m 3) Suite .beforeEach() wraps the passed in function in a Hook adds it to _beforeEach: [31mAssertionError: expected '"before each" hook: fn' to be '"before each" hook'[0m [42m+ expected[0m [41m- actual[0m [41m-"\"before each\" hook: fn"[0m [42m+"\"before each\" hook"[0m [0m[90m at Assertion.fail (/usr/lib/nodejs/should/lib/assertion.js:92:17) at Assertion.value (/usr/lib/nodejs/should/lib/assertion.js:164:19) at Context. (/build/1st/node-mocha-1.20.1/test/suite.js:209:37) at callFn (/build/1st/node-mocha-1.20.1/lib/runnable.js:223:21) at Test.Runnable.run (/build/1st/node-mocha-1.20.1/lib/runnable.js:216:7) at Runner.runTest (/build/1st/node-mocha-1.20.1/lib/runner.js:373:10) at /build/1st/node-mocha-1.20.1/lib/runner.js:451:12 at next (/build/1st/node-mocha-1.20.1/lib/runner.js:298:14) at /build/1st/node-mocha-1.20.1/lib/runner.js:308:7 at next (/build/1st/node-mocha-1.20.1/lib/runner.js:246:23) at Immediate. (/build/1st/node-mocha-1.20.1/lib/runner.js:275:5) at runCallback (timers.js:672:20) at tryOnImmediate (timers.js:645:5) at processImmediate [as _immediateCallback] (timers.js:617:5) [0m [0m 4) Suite .afterEach() wraps the passed in function in a Hook adds it to _afterEach: [31mAssertionError: expected '"after each" hook: fn' to be '"after each" hook'[0m [42m+ expected[0m [41m- actual[0m [41m-"\"after each\" hook: fn"[0m [42m+"\"after each\" hook"[0m [0m[90m at Assertion.fail (/usr/lib/nodejs/should/lib/assertion.js:92:17) at Assertion.value (/usr/lib/nodejs/should/lib/assertion.js:164:19) at Context. (/build/1st/node-mocha-1.20.1/test/suite.js:244:36) at callFn (/build/1st/node-mocha-1.20.1/lib/runnable.js:223:21) at Test.Runnable.run (/build/1st/node-mocha-1.20.1/lib/runnable.js:216:7) at Runner.runTest (/build/1st/node-mocha-1.20.1/lib/runner.js:373:10) at /build/1st/node-mocha-1.20.1/lib/runner.js:451:12 at next (/build/1st/node-mocha-1.20.1/lib/runner.js:298:14) at /build/1st/node-mocha-1.20.1/lib/runner.js:308:7 at next (/build/1st/node-mocha-1.20.1/lib/runner.js:246:23) at Immediate. (/build/1st/node-mocha-1.20.1/lib/runner.js:275:5) at runCallback (timers.js:672:20) at tryOnImmediate (timers.js:645:5) at processImmediate
Bug#866634: marked as done (cairo-dock-plug-ins: depends on libwebkitgtk-3.0-0 which is deprecated)
Your message dated Sat, 19 Aug 2017 10:49:10 + with message-idand subject line Bug#866634: fixed in cairo-dock-plug-ins 3.4.1-1.1 has caused the Debian Bug report #866634, regarding cairo-dock-plug-ins: depends on libwebkitgtk-3.0-0 which is deprecated 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.) -- 866634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cairo-dock-plug-ins Severity: serious Tags: sid buster User: pkg-webkit-maintain...@lists.alioth.debian.org Usertags: oldlibs libwebkitgtk-3.0-0 webkit1 Hi, cairo-dock-plug-ins depends on libwebkitgtk-3.0-0, which is deprecated in favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk). cairo-dock-plug-ins should be ported to the new webkitgtk version so we can remove the old, unmaintained one. Please try to do soon as we're going to try to remove the old webkitgtk soon. I am filing this bug as "serious" since the old webkitgtk will not be available in the next major stable release of Debian (codenamed "buster"). If you have any question don't hesitate to ask. On behalf of the Debian WebKit Maintainers, Jeremy Bicha --- End Message --- --- Begin Message --- Source: cairo-dock-plug-ins Source-Version: 3.4.1-1.1 We believe that the bug you reported is fixed in the latest version of cairo-dock-plug-ins, 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 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated cairo-dock-plug-ins 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: Wed, 09 Aug 2017 12:19:29 +0300 Source: cairo-dock-plug-ins Binary: cairo-dock-plug-ins cairo-dock-plug-in-data cairo-dock-alsamixer-plug-in cairo-dock-animated-icons-plug-in cairo-dock-cairo-penguin-plug-in cairo-dock-clipper-plug-in cairo-dock-clock-plug-in cairo-dock-dbus-plug-in cairo-dock-dbus-plug-in-interface-python cairo-dock-dbus-plug-in-interface-ruby cairo-dock-dbus-plug-in-interface-mono cairo-dock-dbus-plug-in-interface-vala cairo-dock-desklet-rendering-plug-in cairo-dock-dialog-rendering-plug-in cairo-dock-drop-indicator-plug-in cairo-dock-dustbin-plug-in cairo-dock-icon-effect-plug-in cairo-dock-illusion-plug-in cairo-dock-logout-plug-in cairo-dock-motion-blur-plug-in cairo-dock-netspeed-plug-in cairo-dock-powermanager-plug-in cairo-dock-quick-browser-plug-in cairo-dock-rendering-plug-in cairo-dock-shortcuts-plug-in cairo-dock-showdesktop-plug-in cairo-dock-showmouse-plug-in cairo-dock-slider-plug-in cairo-dock-stack-plug-in cairo-dock-switcher-plug-in cairo-dock-systray-plug-in cairo-dock-tomboy-plug-in cairo-dock-toons-plug-in cairo-dock-weather-plug-in cairo-dock-wifi-plug-in cairo-dock-xgamma-plug-in cairo-dock-gmenu-plug-in cairo-dock-keyboard-indicator-plug-in cairo-dock-terminal-plug-in cairo-dock-mail-plug-in cairo-dock-rssreader-plug-in cairo-dock-system-monitor-plug-in cairo-dock-dnd2share-plug-in cairo-dock-musicplayer-plug-in cairo-dock-gnome-integration-plug-in cairo-dock-kde-integration-plug-in cairo-dock-xfce-integration-plug-in cairo-dock-folders-plug-in cairo-dock-impulse-plug-in cairo-dock-messaging-menu-plug-in cairo-dock-recent-events-plug-in cairo-dock-remote-control-plug-in Architecture: source Version: 3.4.1-1.1 Distribution: unstable Urgency: low Maintainer: Debian Cairo-dock Maintainers Changed-By: Adrian Bunk Description: cairo-dock-alsamixer-plug-in - Alsamixer plug-in for Cairo-dock cairo-dock-animated-icons-plug-in - Animated icons plug-in Cairo-dock cairo-dock-cairo-penguin-plug-in - Cairo-Penguin plug-in for Cairo-dock cairo-dock-clipper-plug-in - Clipper plug-in for Cairo-dock cairo-dock-clock-plug-in - Clock plug-in for Cairo-dock cairo-dock-dbus-plug-in - Dbus plug-in for Cairo-dock cairo-dock-dbus-plug-in-interface-mono - library of D-Bus interface for mono of Cairo-dock cairo-dock-dbus-plug-in-interface-python - library of D-Bus interface for Python of
Bug#872598: udev-udeb: no input in graphical installer
Am 19.08.2017 um 10:14 schrieb Raphael Hertzog: > I wonder if it would be possible to have autopkgtest tests covering > udev-udeb... We'd be happy to ship such an autopkgtest. Help in that regard would be much appreciated. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#872603: marked as done (statsmodels binary-all FTBFS: ImportError: No module named _tkinter, please install the python-tk package)
Your message dated Sat, 19 Aug 2017 10:19:47 + with message-idand subject line Bug#872603: fixed in statsmodels 0.8.0-3 has caused the Debian Bug report #872603, regarding statsmodels binary-all FTBFS: ImportError: No module named _tkinter, please install the python-tk package 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.) -- 872603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: statsmodels Version: 0.8.0-2 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=statsmodels=all=0.8.0-2=1503095627=0 ... == ERROR: statsmodels.tsa.vector_ar.tests.test_var.TestVARResults.test_fevd_plot -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/tests/test_var.py", line 235, in test_fevd_plot self.fevd.plot() File "/<>/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/var_model.py", line 1594, in plot import matplotlib.pyplot as plt File "/usr/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 115, in _backend_mod, new_figure_manager, draw_if_interactive, _show = pylab_setup() File "/usr/lib/python2.7/dist-packages/matplotlib/backends/__init__.py", line 32, in pylab_setup globals(),locals(),[backend_name],0) File "/usr/lib/python2.7/dist-packages/matplotlib/backends/backend_tkagg.py", line 6, in from six.moves import tkinter as Tk File "/usr/lib/python2.7/dist-packages/six.py", line 203, in load_module mod = mod._resolve() File "/usr/lib/python2.7/dist-packages/six.py", line 115, in _resolve return _import_module(self.mod) File "/usr/lib/python2.7/dist-packages/six.py", line 82, in _import_module __import__(name) File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 42, in raise ImportError, str(msg) + ', please install the python-tk package' ImportError: No module named _tkinter, please install the python-tk package == ERROR: statsmodels.tsa.vector_ar.tests.test_var.TestVARResults.test_plot -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/tests/test_var.py", line 421, in test_plot self.res.plot() File "/<>/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/var_model.py", line 856, in plot plotting.plot_mts(self.y, names=self.names, index=self.dates) File "/<>/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/plotting.py", line 31, in plot_mts import matplotlib.pyplot as plt File "/usr/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 115, in _backend_mod, new_figure_manager, draw_if_interactive, _show = pylab_setup() File "/usr/lib/python2.7/dist-packages/matplotlib/backends/__init__.py", line 32, in pylab_setup globals(),locals(),[backend_name],0) File "/usr/lib/python2.7/dist-packages/matplotlib/backends/backend_tkagg.py", line 6, in from six.moves import tkinter as Tk File "/usr/lib/python2.7/dist-packages/six.py", line 203, in load_module mod = mod._resolve() File "/usr/lib/python2.7/dist-packages/six.py", line 115, in _resolve return _import_module(self.mod) File "/usr/lib/python2.7/dist-packages/six.py", line 82, in _import_module __import__(name) File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 42, in raise ImportError, str(msg) + ', please install the python-tk package' ImportError: No module named _tkinter, please install the python-tk package == ERROR: statsmodels.tsa.vector_ar.tests.test_var.TestVARResults.test_plot_acorr -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File
Bug#872598: udev-udeb: no input in graphical installer
Am 19.08.2017 um 10:19 schrieb Michael Biebl: > Am 19.08.2017 um 04:59 schrieb Cyril Brulebois: >> >> I haven't looked into the changelog and actual changes (yet), but I'd be >> happy to get some input (no pun intended) from systemd maintainers. >> > > Maybe this is related: > https://github.com/systemd/systemd/commit/43af16c99c800afdfc4b6913ea7596aaddd0395d > > I.e., could you apply this upstream patch, make sure the udev rule is in > the udeb and try again? Urgh, I missed that this patch is already part of v234, sorry for the confusion. So all that's missing seems to be the installation in the udev-udeb. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
Control: severity -1 important On 2017-08-19 10:29, Aurelien Jarno wrote: > Any news about this? This bug now blocks the migration of glibc to > testing. Downgrading. Andreas
Processed: Re: Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
Processing control commands: > severity -1 important Bug #872201 [libc-bin] libc-bin: sometimes throws std::logic_error while processing triggers Severity set to 'important' from 'serious' -- 872201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#871182: marked as done (kdb: FTBFS: dh_makeshlibs: failing due to earlier errors)
Your message dated Sat, 19 Aug 2017 09:04:10 + with message-idand subject line Bug#871182: fixed in kdb 3.0.2-1 has caused the Debian Bug report #871182, regarding kdb: FTBFS: dh_makeshlibs: failing due to earlier errors 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.) -- 871182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kdb Version: 3.0.1.1-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170805 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install --fail-missing > dh_install: Please use dh_missing --list-missing/--fail-missing instead > dh_install: This feature will be removed in compat 11. > make[1]: Leaving directory '/<>' >dh_movelibkdeinit -O--parallel >dh_installdocs -O--parallel >dh_installchangelogs -O--parallel >dh_perl -O--parallel >dh_link -O--parallel >dh_strip_nondeterminism -O--parallel >dh_compress -X.dcl -X.docbook -X-license -X.tag -X.sty -X.el -O--parallel >dh_fixperms -O--parallel >dh_missing -O--parallel >dh_strip -O--parallel >dh_makeshlibs -Xusr/lib/libkdeinit5_\* -O--parallel > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libkdb3-3/DEBIAN/symbols doesn't match > completely debian/libkdb3-3.symbols > --- debian/libkdb3-3.symbols (libkdb3-3_3.0.1.1-1_amd64) > +++ dpkg-gensymbolsf0wPIX 2017-08-06 20:37:52.617425735 + > @@ -1368,8 +1368,8 @@ > _ZN9KDbResultD0Ev@Base 3.0.0 > _ZN9KDbResultD1Ev@Base 3.0.0 > _ZN9KDbResultD2Ev@Base 3.0.0 > - (optional=gccinternal)_ZN9QBitArray6setBitEi@Base 3.0.0 > - _ZN9QBitArray8clearBitEi@Base 3.0.0 > +#MISSING: 3.0.1.1-1# (optional=gccinternal)_ZN9QBitArray6setBitEi@Base 3.0.0 > +#MISSING: 3.0.1.1-1# _ZN9QBitArray8clearBitEi@Base 3.0.0 > _ZNK12KDbFieldList10fieldCountEv@Base 3.0.0 > > _ZNK12KDbFieldList13sqlFieldsListEP13KDbConnectionRK7QStringS4_N3KDb22IdentifierEscapingTypeE@Base > 3.0.0 > _ZNK12KDbFieldList14fieldsIteratorEv@Base 3.0.0 > @@ -1736,7 +1736,8 @@ > _ZNK9KDbParser9statementEv@Base 3.0.0 > _ZNK9KDbResult7isErrorEv@Base 3.0.0 > > (optional=templinst)_ZNSt6vectorIPPiSaIS1_EE12emplace_backIJS1_EEEvDpOT_@Base > 3.0.0 > - > (optional=templinst)_ZNSt6vectorIPPiSaIS1_EE19_M_emplace_back_auxIJS1_EEEvDpOT_@Base > 3.0.0 > + > _ZNSt6vectorIPPiSaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base > 3.0.1.1-1 > +#MISSING: 3.0.1.1-1# > (optional=templinst)_ZNSt6vectorIPPiSaIS1_EE19_M_emplace_back_auxIJS1_EEEvDpOT_@Base > 3.0.0 > _ZTI11KDbSqlField@Base 3.0.0 > _ZTI11QSharedData@Base 3.0.0 > _ZTI12KDbFieldList@Base 3.0.0 > dh_makeshlibs: failing due to earlier errors > debian/rules:6: recipe for target 'binary' failed > make: *** [binary] Error 2 The full build log is available from: http://aws-logs.debian.net/2017/08/05/kdb_3.0.1.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: kdb Source-Version: 3.0.2-1 We believe that the bug you reported is fixed in the latest version of kdb, 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 871...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated kdb 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: SHA256 Format: 1.8 Date: Sat, 19 Aug 2017 10:51:33 +0200 Source: kdb Binary: libkdb3-3 libkdb-data
Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
On 2017-08-16 11:54, Aurelien Jarno wrote: > On 2017-08-16 02:41, Andreas Beckmann wrote: > > [ adding apt@, therefore quoting fully ] > > > > On 2017-08-15 22:56, Aurelien Jarno wrote: > > > control: tag - 1 + help > > > control: tag - 1 + moreinfo > > > > > > On 2017-08-15 09:58, Andreas Beckmann wrote: > > >> Package: libc-bin > > >> Version: 2.24-14 > > >> Severity: serious > > >> User: debian...@lists.debian.org > > >> Usertags: piuparts > > >> > > >> Hi, > > >> > > >> during several tests with piuparts in sid I noticed spurious and > > >> unreproducible errors while processing libc-bin triggers. > > >> Often apt-get just exits with an error code (but no error message > > >> at all) after processing the triggers. > > >> A few times I also get an error message about an uncaught exception. > > >> These failures usually go away after rerunning the test. > > >> > > >> >From the attached log (scroll to the bottom...): > > >> > > >> Processing triggers for libc-bin (2.24-14) ... > > >> terminate called after throwing an instance of 'std::logic_error' > > >> what(): basic_string::_M_construct null not valid > > > > > > What make you think it's an issue in libc-bin? The trigger processing > > > code just does: > > > > > > if [ "$1" = "triggered" ] || [ "$1" = "configure" ]; then > > > ldconfig || ldconfig --verbose > > > exit 0 > > > fi > > > > > > And there is no C++ code in ldconfig. Moreover even if ldconfig fails > > > the error is ignored and the install should not stop. > > > > OK, that probably leaves dpkg (no C++ either) and apt-get as the call > > chain to the trigger processing ... adding apt@ to the loop. > > #871275 could be a candidate, i.e. a g++7 rebuild might fix it. > > > > I reran the test where I attached the logfile yesterday repeatedly for > > 100 times with no failure. But I could probably dig out a dozen of > > similar failures from other piuparts tests. (These failures will be > > retried frequently, so will eventually succeed.) > > > > If there is some way to get more debug output for this problem, I could > > enable that globally in my piuparts instance. > > I guess you can try to get a core dump. Just make sure that you run > "ulimit -c unlimited" before running the command. The core dump will > tell you which binary actually has the issue and should provide more > info about the issue. Any news about this? This bug now blocks the migration of glibc to testing. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#872598: udev-udeb: no input in graphical installer
Am 19.08.2017 um 04:59 schrieb Cyril Brulebois: > > I haven't looked into the changelog and actual changes (yet), but I'd be > happy to get some input (no pun intended) from systemd maintainers. > Maybe this is related: https://github.com/systemd/systemd/commit/43af16c99c800afdfc4b6913ea7596aaddd0395d I.e., could you apply this upstream patch, make sure the udev rule is in the udeb and try again? If that doesn't help, we will need log files to debug this further. A Xorg log from a working/non-working installer would be a start. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#872598: udev-udeb: no input in graphical installer
Hello, On Sat, 19 Aug 2017, Cyril Brulebois wrote: > I've only quickly glanced at the contents of both packages, and debdiff > mentions no obvious issues (file lists are the same). I believe this is precisely the problem. The new udev-udeb should include a new file: diff --git a/debian/udev-udeb.install b/debian/udev-udeb.install index 6a8e2108f..6758fef06 100644 --- a/debian/udev-udeb.install +++ b/debian/udev-udeb.install @@ -5,6 +5,7 @@ lib/udev/ata_id lib/udev/scsi_id lib/udev/cdrom_id lib/udev/rules.d/50-udev-default.rules +lib/udev/rules.d/60-input-id.rules lib/udev/rules.d/60-cdrom_id.rules lib/udev/rules.d/60-persistent-input.rules lib/udev/rules.d/60-persistent-storage.rules I won't have the time to test this now but I believe it's the problem. I see this in the upstream change between both versions: --- a/rules/50-udev-default.rules +++ b/rules/50-udev-default.rules.in @@ -11,7 +11,6 @@ SUBSYSTEM=="rtc", ATTR{hctosys}=="1", SYMLINK+="rtc" SUBSYSTEM=="rtc", KERNEL=="rtc0", SYMLINK+="rtc", OPTIONS+="link_priority=-100" SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", IMPORT{builtin}="usb_id", IMPORT{builtin}="hwdb --subsyste m=usb" -SUBSYSTEM=="input", ENV{ID_INPUT}=="", IMPORT{builtin}="input_id" ENV{MODALIAS}!="", IMPORT{builtin}="hwdb --subsystem=$env{SUBSYSTEM}" ACTION!="add", GOTO="default_end" [...] --- /dev/null +++ b/rules/60-input-id.rules @@ -0,0 +1,7 @@ +# do not edit this file, it will be overwritten on update + +ACTION=="remove", GOTO="id_input_end" + +SUBSYSTEM=="input", ENV{ID_INPUT}=="", IMPORT{builtin}="input_id" + +LABEL="id_input_end" It would be nice to have a fixed udev soon. Thank you Cyril for the investigation! I wonder if it would be possible to have autopkgtest tests covering udev-udeb... Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
Processed: tagging 871182
Processing commands for cont...@bugs.debian.org: > tags 871182 + pending Bug #871182 [src:kdb] kdb: FTBFS: dh_makeshlibs: failing due to earlier errors Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 871182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Also affects ruby-diaspora-federation-rails
Processing commands for cont...@bugs.debian.org: > affects 872606 src:ruby-diaspora-federation-rails Bug #872606 [src:ruby-diaspora-federation] ruby-diaspora-federation build-depends on ruby-faraday-middleware (< 0.11~) but 0.12.2-1 is to be installed Added indication that 872606 affects src:ruby-diaspora-federation-rails > thanks Stopping processing here. Please contact me if you need assistance. -- 872606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872606: ruby-diaspora-federation build-depends on ruby-faraday-middleware (< 0.11~) but 0.12.2-1 is to be installed
Source: ruby-diaspora-federation Version: 0.1.4-2 Severity: serious Tags: buster sid The following packages have unmet dependencies: builddeps:ruby-diaspora-federation : Depends: ruby-faraday-middleware (< 0.11~) but 0.12.2-1 is to be installed
Bug#872604: csmith FTBFS on s390x: platform.cpp:82: Error: Unrecognized opcode: `stckf'
Source: csmith Version: 2.3.0-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=csmith=s390x=2.3.0-1=1503091499=0 ... g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o platform.o platform.cpp platform.cpp: Assembler messages: platform.cpp:82: Error: Unrecognized opcode: `stckf' Makefile:717: recipe for target 'platform.o' failed make[3]: *** [platform.o] Error 1
Bug#872603: statsmodels binary-all FTBFS: ImportError: No module named _tkinter, please install the python-tk package
Source: statsmodels Version: 0.8.0-2 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=statsmodels=all=0.8.0-2=1503095627=0 ... == ERROR: statsmodels.tsa.vector_ar.tests.test_var.TestVARResults.test_fevd_plot -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/tests/test_var.py", line 235, in test_fevd_plot self.fevd.plot() File "/<>/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/var_model.py", line 1594, in plot import matplotlib.pyplot as plt File "/usr/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 115, in _backend_mod, new_figure_manager, draw_if_interactive, _show = pylab_setup() File "/usr/lib/python2.7/dist-packages/matplotlib/backends/__init__.py", line 32, in pylab_setup globals(),locals(),[backend_name],0) File "/usr/lib/python2.7/dist-packages/matplotlib/backends/backend_tkagg.py", line 6, in from six.moves import tkinter as Tk File "/usr/lib/python2.7/dist-packages/six.py", line 203, in load_module mod = mod._resolve() File "/usr/lib/python2.7/dist-packages/six.py", line 115, in _resolve return _import_module(self.mod) File "/usr/lib/python2.7/dist-packages/six.py", line 82, in _import_module __import__(name) File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 42, in raise ImportError, str(msg) + ', please install the python-tk package' ImportError: No module named _tkinter, please install the python-tk package == ERROR: statsmodels.tsa.vector_ar.tests.test_var.TestVARResults.test_plot -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/tests/test_var.py", line 421, in test_plot self.res.plot() File "/<>/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/var_model.py", line 856, in plot plotting.plot_mts(self.y, names=self.names, index=self.dates) File "/<>/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/plotting.py", line 31, in plot_mts import matplotlib.pyplot as plt File "/usr/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 115, in _backend_mod, new_figure_manager, draw_if_interactive, _show = pylab_setup() File "/usr/lib/python2.7/dist-packages/matplotlib/backends/__init__.py", line 32, in pylab_setup globals(),locals(),[backend_name],0) File "/usr/lib/python2.7/dist-packages/matplotlib/backends/backend_tkagg.py", line 6, in from six.moves import tkinter as Tk File "/usr/lib/python2.7/dist-packages/six.py", line 203, in load_module mod = mod._resolve() File "/usr/lib/python2.7/dist-packages/six.py", line 115, in _resolve return _import_module(self.mod) File "/usr/lib/python2.7/dist-packages/six.py", line 82, in _import_module __import__(name) File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 42, in raise ImportError, str(msg) + ', please install the python-tk package' ImportError: No module named _tkinter, please install the python-tk package == ERROR: statsmodels.tsa.vector_ar.tests.test_var.TestVARResults.test_plot_acorr -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/tests/test_var.py", line 428, in test_plot_acorr self.res.plot_acorr() File "/<>/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/var_model.py", line 660, in plot_acorr plotting.plot_full_acorr(self.acorr(nlags=nlags), linewidth=linewidth) File "/<>/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/plotting.py", line 120, in plot_full_acorr import matplotlib.pyplot as plt File "/usr/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 115, in _backend_mod, new_figure_manager, draw_if_interactive, _show = pylab_setup() File "/usr/lib/python2.7/dist-packages/matplotlib/backends/__init__.py", line 32, in pylab_setup globals(),locals(),[backend_name],0) File "/usr/lib/python2.7/dist-packages/matplotlib/backends/backend_tkagg.py", line 6, in from six.moves import tkinter as Tk File
Bug#872378: fenrir.deb: No speech after enabling fenrir to start in concial.
Hello, Matthew Dyer, on mer. 16 août 2017 18:49:38 -0400, wrote: >* What led up to the situation? > I disabled espeakup.service then enabled fenrir.service >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? > Fenrir did not speak after rebooting the system. >* What outcome did you expect instead? > Fenrir should have spoken after logining to my consel2 Is this only with version 1.06-1 of fenrir, or does it happen also with version 1.05-1? Samuel
Processed: Move to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 872263 src:linux 4.11.6-1 Bug #872263 [linux-image-4.11.0-1-amd64-dbg] linux-image-4.11.0-1-amd64-dbg: file overwrite error upgrading from stretch-backports Warning: Unknown package 'linux-image-4.11.0-1-amd64-dbg' Bug reassigned from package 'linux-image-4.11.0-1-amd64-dbg' to 'src:linux'. No longer marked as found in versions linux/4.11.6-1. Ignoring request to alter fixed versions of bug #872263 to the same values previously set Bug #872263 [src:linux] linux-image-4.11.0-1-amd64-dbg: file overwrite error upgrading from stretch-backports Marked as found in versions linux/4.11.6-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 872263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Version tracking fix
Processing commands for cont...@bugs.debian.org: > found 872595 2.5.0+dfsg-1 Bug #872595 [src:calibre] calibre: please use system libmspack instead of embedded copy Marked as found in versions calibre/2.5.0+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 872595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 872378 is serious
Processing commands for cont...@bugs.debian.org: > severity 872378 serious Bug #872378 [fenrir] fenrir.deb: No speech after enabling fenrir to start in concial. Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 872378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems