Bug#723220: arpon link with -L/usr/lib
Just close this bug report. On Tue, Sep 17, 2013 at 6:26 PM, YunQiang Suwrote: > Package: arpon > Version: 2.0-2.1 > X-Debbugs-CC: wzss...@gmail.com > > This package has one or more -L/usr/lib in its build system, > which will make it ftbfs if there is libraries under /usr/lib, > while is not the default architecture, mips* for example. > > On mips* systems, /usr/lib is defined as place to hold O32 > libraries, and /usr/lib32 for N32, and /usr/lib64 is for N64. > > Beside the way, on the multiarch system like Debian, user may install > libraries under /usr/lib by hand. > > Please use the default search path if you can, and please consider fix > this. > > I will try to fix this bug, while if you can help to fix it, > It will be very appreciative. > > The attachement is the buildlog of this package on mips64el platform. -- YunQiang Su
Bug#872691: worklog FTCBFS: uses the build architecture compiler
Source: worklog Version: 1.8-6 Tags: patch User: helm...@debian.org Usertags: rebootstrap worklog fails to cross build from source, because it uses the build architecture compiler. The upstream makefile bluntly hardcodes the build architecture compiler and the packaging does not pass any cross compilers to it either. After fixing both, worklog cross compiles successfully. Please consider applying the attached patch. Helmut diff --minimal -Nru worklog-1.8/debian/changelog worklog-1.8/debian/changelog --- worklog-1.8/debian/changelog2012-02-18 20:11:04.0 +0100 +++ worklog-1.8/debian/changelog2017-08-20 07:33:26.0 +0200 @@ -1,3 +1,12 @@ +worklog (1.8-6.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Closes: #-1 ++ Let dh_auto_build pass cross compilers to make. ++ makefile_fix.patch: Honour variable CC. + + -- Helmut GrohneSun, 20 Aug 2017 07:33:26 +0200 + worklog (1.8-6) unstable; urgency=low * QA upload. diff --minimal -Nru worklog-1.8/debian/patches/makefile_fix.patch worklog-1.8/debian/patches/makefile_fix.patch --- worklog-1.8/debian/patches/makefile_fix.patch 2012-02-18 20:06:21.0 +0100 +++ worklog-1.8/debian/patches/makefile_fix.patch 2017-08-20 07:33:26.0 +0200 @@ -1,4 +1,4 @@ -Description: Fix hardcoded installation path from the Makefile +Description: Fix hardcoded installation path and compiler from the Makefile --- worklog-1.8.orig/Makefile +++ worklog-1.8/Makefile @@ -27,15 +27,15 @@ + #gzip $(MAN)/man1/worklog.1 worklog: worklog.c Makefile - gcc $(CFLAGS) $(USE_ENV_DIR) worklog.c $(LIBS) -o worklog - +- gcc $(CFLAGS) $(USE_ENV_DIR) worklog.c $(LIBS) -o worklog ++ $(CC) $(CFLAGS) $(USE_ENV_DIR) worklog.c $(LIBS) -o worklog ++ +clean: + rm -f worklog -+ + tar: - rm -rf worklog-${VERSION} - mkdir worklog-${VERSION} @@ -37,3 +40,4 @@ tar: cp worklog.lsm distr/worklog-${VERSION}.lsm tar -clzvf distr/worklog-${VERSION}.tar.gz worklog-${VERSION} - rm -rf worklog-${VERSION} diff --minimal -Nru worklog-1.8/debian/rules worklog-1.8/debian/rules --- worklog-1.8/debian/rules2012-02-18 19:39:00.0 +0100 +++ worklog-1.8/debian/rules2017-08-20 07:33:22.0 +0200 @@ -14,7 +14,7 @@ build-stamp: configure-stamp dh_testdir - $(MAKE) + dh_auto_build touch build-stamp clean:
Bug#866129: lilypond: segfault using lilypond buster testing
Control: forcemerge 871372 -1 On Tue, 27 Jun 2017, Thomas Wille wrote: > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? On Tue, 27 Jun 2017, Antonio Ospite wrote: > lilyopnd devs suggest[1] that this could be an issue with gcc-6, > reported in the issue 4814 on sf.net[2], which has been fixed by commit > b0dce76daf27 (Issue 4814: grob.cc segfaults with gcc6)[3]. Thanks for the report; I've confirmed that this is this issue, and I'm just about ready to roll out an update for it. -- Don Armstrong https://www.donarmstrong.com The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair. -- Douglas Adams _Mostly Harmless_
Bug#872690: kubernetes-node: docker-ce compat'
Package: kubernetes-node Severity: wishlist Dear Maintainer, Current kubernetes-node package depends upon docker.io (and this one only). But docker.io is 1.13.1 and it's not _uncommon_ for Debian users to use upstream's "docker-ce" Stretch package (currently 17.06.0). In this context it'd be appreciated if kubernetes-node package control could be more tolerent w.r.t docker-ce $ apt-get install kubernetes-node kubernetes-node : Depends: docker.io but it is not going to be installed -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-debug'), (90, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:fr (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#863018: libxml2: diff for NMU version 2.9.4+dfsg1-3.1
Control: tags 863018 + patch Control: tags 863018 + pending Control: tags 863019 + patch Control: tags 863019 + pending Control: tags 863021 + patch Control: tags 863021 + pending Control: tags 863022 + patch Control: tags 863022 + pending Control: tags 870865 + patch Control: tags 870865 + pending Control: tags 870867 + pending Control: tags 870870 + pending Dear libxml2 maintainer(s) team, I've prepared an NMU for libxml2 (versioned as 2.9.4+dfsg1-3.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer or actually can reschedule to have it entering the archive earlier. I have prepared a corresponding upload for jessie-security and stretch-security, but would prefer to release those packages only after libxml2 has entered unstable as well. Regards, Salvatore diff -Nru libxml2-2.9.4+dfsg1/debian/changelog libxml2-2.9.4+dfsg1/debian/changelog --- libxml2-2.9.4+dfsg1/debian/changelog 2017-07-04 21:59:55.0 +0200 +++ libxml2-2.9.4+dfsg1/debian/changelog 2017-08-20 06:56:40.0 +0200 @@ -1,3 +1,28 @@ +libxml2 (2.9.4+dfsg1-3.1) unstable; urgency=low + + * Non-maintainer upload. + * Increase buffer space for port in HTTP redirect support (CVE-2017-7376) +Incorrect limit was used for port values. (Closes: #870865) + * Prevent unwanted external entity reference (CVE-2017-7375) +Missing validation for external entities in xmlParsePEReference. +(Closes: #870867) + * Fix handling of parameter-entity references (CVE-2017-9049, CVE-2017-9050) +- Heap-based buffer over-read in function xmlDictComputeFastKey + (CVE-2017-9049). +- Heap-based buffer over-read in function xmlDictAddString + (CVE-2017-9050). +(Closes: #863019, #863018) + * Fix buffer size checks in xmlSnprintfElementContent (CVE-2017-9047, +CVE-2017-9048) +- Buffer overflow in function xmlSnprintfElementContent (CVE-2017-9047). +- Stack-based buffer overflow in function xmlSnprintfElementContent + (CVE-2017-9048). +(Closes: #863022, #863021) + * Fix type confusion in xmlValidateOneNamespace (CVE-2017-0663) +Heap buffer overflow in xmlAddID. (Closes: #870870) + + -- Salvatore BonaccorsoSun, 20 Aug 2017 06:56:40 +0200 + libxml2 (2.9.4+dfsg1-3) unstable; urgency=medium * Team upload. diff -Nru libxml2-2.9.4+dfsg1/debian/patches/0009-Increase-buffer-space-for-port-in-HTTP-redirect-supp.patch libxml2-2.9.4+dfsg1/debian/patches/0009-Increase-buffer-space-for-port-in-HTTP-redirect-supp.patch --- libxml2-2.9.4+dfsg1/debian/patches/0009-Increase-buffer-space-for-port-in-HTTP-redirect-supp.patch 1970-01-01 01:00:00.0 +0100 +++ libxml2-2.9.4+dfsg1/debian/patches/0009-Increase-buffer-space-for-port-in-HTTP-redirect-supp.patch 2017-08-20 06:56:40.0 +0200 @@ -0,0 +1,34 @@ +From: Daniel Veillard +Date: Fri, 7 Apr 2017 17:13:28 +0200 +Subject: Increase buffer space for port in HTTP redirect support +Origin: https://git.gnome.org/browse/libxml2/commit/?id=5dca9eea1bd4263bfa4d037ab2443de1cd730f7e +Bug: https://bugzilla.gnome.org/show_bug.cgi?id=780690 +Bug-Debian: https://bugs.debian.org/870865 +Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2017-7376 + +For https://bugzilla.gnome.org/show_bug.cgi?id=780690 + +nanohttp.c: the code wrongly assumed a short int port value. +--- + nanohttp.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/nanohttp.c b/nanohttp.c +index e109ad75..373425de 100644 +--- a/nanohttp.c b/nanohttp.c +@@ -1423,9 +1423,9 @@ retry: + if (ctxt->port != 80) { + /* reserve space for ':x', incl. potential proxy */ + if (proxy) +- blen += 12; ++ blen += 17; + else +- blen += 6; ++ blen += 11; + } + bp = (char*)xmlMallocAtomic(blen); + if ( bp == NULL ) { +-- +2.11.0 + diff -Nru libxml2-2.9.4+dfsg1/debian/patches/0010-Prevent-unwanted-external-entity-reference.patch libxml2-2.9.4+dfsg1/debian/patches/0010-Prevent-unwanted-external-entity-reference.patch --- libxml2-2.9.4+dfsg1/debian/patches/0010-Prevent-unwanted-external-entity-reference.patch 1970-01-01 01:00:00.0 +0100 +++ libxml2-2.9.4+dfsg1/debian/patches/0010-Prevent-unwanted-external-entity-reference.patch 2017-08-20 06:56:40.0 +0200 @@ -0,0 +1,38 @@ +From: Neel Mehta +Date: Fri, 7 Apr 2017 17:43:02 +0200 +Subject: Prevent unwanted external entity reference +Origin: https://git.gnome.org/browse/libxml2/commit/?id=90ccb58242866b0ba3edbef8fe44214a101c2b3e +Bug: https://bugzilla.gnome.org/show_bug.cgi?id=780691 +Bug-Debian: https://bugs.debian.org/870867 +Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2017-7375 + +For https://bugzilla.gnome.org/show_bug.cgi?id=780691 + +* parser.c: add a specific check to avoid PE reference +--- + parser.c | 9 + + 1 file changed, 9 insertions(+) + +diff --git a/parser.c b/parser.c +index 609a2703..c2c812de 100644 +--- a/parser.c
Bug#848198: fonts-noto-color-emoji
Hi, Sorry for MIA. I am recently (1-2 weeks ago) into some ITP and RFPs of some Python libraries to build fonts from source, like ufolib, defcon, and henrich is going to update fonttools. This can lead towards to packaging nototools to build this package from source. Yao Wei On Sun, 20 Aug 2017 at 05:34 Jeremy Bichawrote: > Control: merge 848198 849042 > > Hi, has there been any progress on packaging Noto Emoji? > > Thanks, > Jeremy Bicha >
Bug#872620: [anarchism] Bug#872620: Bug#872620: anarchism: add Suggests: fortune-anarchism
> > ok, cool, then I'll wait til you ping me here… > ping everything i've made is on debian/samuel, it justs needs to be merged on master and s/UNRELEASED/unstable/g on changelog (i thought it would be best to leave these to the person who will sponsor the upload). BTW, i would appreciate a lot if you could give me DM rights on the package too so i won't need a sponsor next time (i will apply for DD as soon as i get someone to advocate me). Thanks Holger :) Samuel Henrique
Bug#869097: Sphinsearch crash dump
On Sat, 22 Jul 2017 17:49:14 +0100 Maxime Buquetwrote: > https://github.com/sphinxsearch/sphinx/commit/e14a9bc5b63d9399dbabad4e63313079e4c6e8bb > > Apparently this commit fixes the problem. I have a fix running locally, > it would be nice if this could get backported. > I uploaded a new release into unstable with this patch. Can you guys have a test? If it works well, I will start the process to upload it to Stretch. > Thanks > > -- > Maxime “pep” Buquet
Bug#860568: iptraf-ng: cron spam due to duplicated logrotate rules
Le Tue, Apr 18, 2017 at 08:31:58PM +0200, Tollef Fog Heen a écrit : > Package: iptraf-ng > Version: 1:1.1.4-6 > Severity: normal > > As of a few days ago, I started getting mails from logrotate complaining > about duplicate log rotation rules for iptraf and iptraf-ng: > > /etc/cron.daily/logrotate: > error: iptraf-ng:2 duplicate log entry for /var/log/iptraf/rvnamed.log Hi all, isn't it because the transitional package iptraf contains /etc/logrotate.d/iptraf, and shouldn't this file be removed from the package ? Have a nice Sunday, -- Charles Plessy Tsurumi, Kanagawa, Japan
Bug#856396: dpkg-dev: dpkg-source displays warnings when gcc is not installed
Guillem Jover wrote on Sun, Apr 09, 2017 at 03:24:55 +0200: > On Tue, 2017-02-28 at 15:23:49 +, CONSUEGRA Lenny - externe wrote: > > Package: dpkg-dev > > Version: 1.17.27 > > Severity: minor > > Tags: upstream > > > When building a package with dpkg-source, warnings are printed if gcc is > > not installed on the system : > > > > root@build:/srv/build/tmp/test# dpkg-source -b ublock-origin-1.9.4+dfsg > > sh: 1: gcc: not found > > dpkg-source: warning: Couldn't determine gcc system type, falling back to > > default (native compilation) > > I've analyzed the code, and it does indeed not really require the host > architecture when building a source package, so I've got a couple of > commits that get rid of those messages. > > The first disables the perl warnings for when the program is not found > (the equivalent of first line for 1.18.x, but w/o going via the shell), > and the second removes the need completely of calling gcc (so the > second line will not even be emitted). > > I've queued these for 1.19.x. I see a similar error in another codepath: % apt-get source hello % cd hello*/ % dpkg-buildpackage ⋮ dpkg-buildpackage: info: source changed by Salvatore BonaccorsoCan't exec "gcc": No such file or directory at /usr/share/perl5/Dpkg/Arch.pm line 165. dpkg-architecture: warning: cannot determine CC system type, falling back to default (native compilation) ⋮ I think the following patch will suffice to address it: [[[ diff --git a/scripts/Dpkg/Arch.pm b/scripts/Dpkg/Arch.pm index c6321a580..341169c1b 100644 --- a/scripts/Dpkg/Arch.pm +++ b/scripts/Dpkg/Arch.pm @@ -158,7 +158,7 @@ sub get_build_arch() sub get_host_gnu_type() { -my $CC = $ENV{CC} || 'gcc'; +my $CC = $ENV{CC} || 'cc'; return $cc_host_gnu_type{$CC} if defined $cc_host_gnu_type{$CC}; @@ -175,7 +175,7 @@ sub get_build_arch() sub set_host_gnu_type { my ($host_gnu_type) = @_; -my $CC = $ENV{CC} || 'gcc'; +my $CC = $ENV{CC} || 'cc'; $cc_host_gnu_type{$CC} = $host_gnu_type; } ]]] I tested it in current sid. I tried to build the package with this patch, on the assumption that that would run unit tests, but the build failed both with and without the patch with "error: cannot get project version" (probably from ./get-version). I built by running 'pdebuild' without arguments in a fresh debcheckout. Cheers, Daniel
Bug#872649: install bash completions
On Sat, Aug 19, 2017 at 03:14:48PM -0400, Antoine Beaupre wrote: Thanks for the suggestion, this file will be added in next release - https://anonscm.debian.org/git/collab-maint/gitsome.git/commit/?id=e6deba742db87bb714ea547cf0050ffdd033658f -- SZ Lin (林上智), http://people.debian.org/~szlin Debian Developer 4096R/ 178F 8338 B314 01E3 04FC 44BA A959 B38A 9561 F3F9 signature.asc Description: PGP signature
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#872687: xfce4-pulseaudio-plugin: Unable to click or use volume slider
Package: xfce4-pulseaudio-plugin Version: 0.2.5-1 Severity: important Dear Maintainer, * What led up to the situation? I attempted to use the pulse panel plugin to change my computer's playback volume, but the popup frame with the volume slider simply disappears the moment I try to click and drag on the slider. This has never happened before today. * What exactly did you do (or not do) that was effective (or ineffective)? Note that the mute checkbox still works, and the menu item that starts pavucontrol still works. Only the slider does not work properly. Pavucontrol seems to work properly. I cannot think of any new packages I may have installed that would cause this issue. I ran 'apt install --reinstall xfce4-panel-plugin', and restarted X, but the behaviour remained. After submitting this bug report, I will attempt downgrading xfce4-panel-plugin to 0.2.4-1 to see if anything changes. * What was the outcome of this action? Attempting to click and drag the volume slider just results in the plugin frame disappearing immediately, without changing the volume. * What outcome did you expect instead? The volume slider should be clickable and draggable without the frame disappearing the moment the slider is clicked. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (1000, 'testing'), (1000, 'stable'), (750, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfce4-pulseaudio-plugin depends on: ii libatk1.0-0 2.24.0-1 ii libc62.24-12 ii libcairo-gobject21.14.10-1 ii libcairo21.14.10-1 ii libdbus-1-3 1.11.16+really1.10.22-1 ii libdbus-glib-1-2 0.108-2 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-0 2.53.4-3 ii libgtk-3-0 3.22.18-1 ii libkeybinder-3.0-0 0.3.1-1 ii libnotify4 0.7.7-2 ii libpango-1.0-0 1.40.6-1 ii libpangocairo-1.0-0 1.40.6-1 ii libpulse-mainloop-glib0 10.0-2 ii libpulse010.0-2 ii libxfce4panel-2.0-4 4.12.1-2 ii libxfce4ui-2-0 4.12.1-2 ii libxfce4util74.12.1-3 ii libxfconf-0-24.12.1-1 Versions of packages xfce4-pulseaudio-plugin recommends: ii pavucontrol 3.0-3.1 ii pulseaudio 10.0-2 xfce4-pulseaudio-plugin suggests no packages. -- no debconf information
Bug#872686: Update to 5.0
Package: xpad Please update to 5.0. Version 5.0 * New: Reload from Disk - No way to refresh sticky that was edited externally (#1689429) * Fix: Preferences -> Layout -> Change font gives error (#1708877) * Fix: Preferences -> Color and font changes between custom and theme did not always work * Fix: Preferences -> Xpad autostart_new_pad is broken (same fix as #1652845) (#1689754) * Fix: Parameters - -f closes app, when trying to add note from file while xpad in running (#1652845) * Fix: Technical - brackets [] changed to / in pad text (#1661054) * Fix: Technical - Xpad quit by CTRL-Q give repetitive assertion error (#1708879) * Fix: Technical - Fixed error on first time run: value TRUE of type gboolean is invalid or out of range for property autostart-xpad of type gboolean Version 4.9 * Fix: Typos - Found by Lintian and reported by jcfp (#1591368) * Fix: Desktop file - added keywords for the desktop file (#1591368) * Fix: Makefile - distclean function did not do its job properly, leading to a configure issue, reported and fixed by jcfp (#1591497) * Fix: Text selection - selected text in a pad was not visible anymore (regression due to GTK behavior change) (#1571625) * Fix: Set cursor color - Replaced gtk_widget_override_font function by CSS * Fix: Deprecated functions - Replaced gtk_widget_override_cursor function by CSS * Fix: Deprecated functions - Removed gtk_widget_override_background_color, since I did not notice a difference without in the Xpad toolbar * Fix: Deprecated functions - Replaced gtk_style_context_get_background_color with gtk_style_context_get * Fix: Deprecated functions - Replaced gtk_misc_set_alignment with gtk_label_set_xalign & gtk_label_set_yalign * Fix: Deprecated functions - Replaced gdk_cursor_new with gdk_cursor_new_for_display * Fix: Deprecated functions - Replaced gtk_menu_popup with gtk_menu_popup_at_pointer
Bug#720177: `git debrebase` UI
Hello Ian, Please excuse the limited extent to which I've grokked `git debrebase`. Hopefully the questions in this e-mail will help move me along. If you want to see the extent of my understanding you might watch the recording of the "git and Debian packaging" BoF from DebConf17, where I attempt to explain `git debrebase` when someone asks me a question about it. On Tue, Jul 18 2017, Ian Jackson wrote: > I think I had imagined to expose A, C and D to the user and to compute > the state B on demand during push. That means that git-debrebase is > only required when starting a rebase, or before pushing. (And if the > extra step is forgotten before pushing, the user is stopped by the > push ff check.) Good point that they would be warned by git's standard checks. debrebase needs to warn the user that they should expect to see non-ff push errors from git until they finish the debrebase. It might even leave behind a hook so that after the non-ff push error, there could be a hint about finishing the debrebase, but that might be too unpleasant to implement. > I think you are proposing to expose A, B and D to the user and to hide > C by somehow always reattaching a pseudomerge after each rebase. But > I don't think git-rebase can do that. Why not? > This means the user would have to use `git-debrebase --continue'. If > they ran `git-rebase --continue' instead they would end up in the > to-them-anomalous state C. This would not show up in `git status' > (because `git status' is not extensible). > >> In the case of a debrebase, there will never be any conflicts to >> resolve, > > This is not true for upstream changes. It is also not true if the > user used fixup! and --autosquash, or something. > > Ie, the user might do > git-debrebase -i --autosquash I don't understand this command. In my head, debrebase performs two atomic operations: (i) laundering the branch; and (ii) reattaching the pseudomerge before push. So what can `git debrebase -i --autosquash` mean? Does it mean "launder the branch, and then call `git rebase` with the options I passed?" I'm also confused about what `git debrebase --continue` could mean. (ii) will always end the debrebase, but `git rebase --continue` doesn't always end the rebase. Is this another case where debrebase is wrapping a plain rebase? If I'm on the right lines, it might be unwise to wrap `git rebase`. Git users are pretty good at that command; if we leave them to invoke it, they stand a better chance of understanding the whole workflow. But I'm not sure. > The other reason to expose this state to the user is that it is one > that many other git tools already understand. If the user wants to > try to use stg or gbp pq or god-knows-what, they need a branch without > merges. > > > Also: there is more. > > Much of the code in git-debrebase will be useful for downstreams too. > In particular, the automatic pseudomerge handling and perhaps the > stripping of debian/patches. > > I have one person already trying to do rebase-with-pseudomerges as a > downstream. I just read the IRC log you posted in another bug; thanks for that. -- Sean Whitton signature.asc Description: PGP signature
Bug#872685: zshrc: zsh-common: zsh-line-init should use add-zle-hook-function
Package: zsh-common Version: 5.4.1-1 Severity: wishlist File: zshrc Tags: newcomer Dear Maintainer, /etc/zsh/zshrc defines zle-line-init and zle-line-finish widgets and functions. It should instead define arbitrarily-named functions and register them using add-zle-hook-widget. That matters if a zle-line-* widget has been registered before /etc/zsh/zshrc is sourced (either with or without add-zle-hook-widget), or if a zle-line-* widget will be registered after /etc/zsh/zshrc without add-zle-hook-widget: in either case, someone will overwrite someone else's zle-line-init widget. (Use of add-zle-hook-widget preserves any pre-existing zle-line-* widgets.) Also, there's some educational value in using add-zle-hook-widget: it advertises that feature's existence. Cheers, Daniel
Bug#812826: xim problem
Hello, On Sat, Aug 19 2017, Osamu Aoki wrote: > 1. Did you enable Korean input via dialog (GNOME Setup "Region & > Language" or ibus-setup") I tried with both. > 2. Do you have any working combination to enter Korean? Yes: - using `ibus-server` without --xim; and - not using urxvt or Emacs. Or: - using `ibus-server --xim` - changing my finger habits to workaround this bug :) I think that it would be best if I did some reading about xim, ibus, ibus-hangul etc. Do you know what documents you read when you wrote im-config? Thanks again. -- Sean Whitton signature.asc Description: PGP signature
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
Bug#872683: Acknowledgement (RFP: dagr -- deviantArt gallery ripper)
Damn, forgot to set the URL: https://github.com/voyageur/dagr/
Bug#843263: grafana: Blank page on new install
forcemerge 843263 864793 severity 843263 serious thanks Merging duplicates. Dmitry, any chance at uploading a fix or are we blocked on #861551? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#872684: incorrect refcount handling for strings
Source: whitedb Version: 0.7.3-2 Severity: important Tags: patch upstream When a database field containing a long (over 32 bytes) string is overwritten with the same string, the reference count of the string is checked after decrementing (due to overwriting) and before incrementing (due to re-insert). This can cause prematurely freeing storage allocated to the string and may corrupt internal structures of the database. Originally reported here: https://github.com/priitj/whitedb/issues/29 Patch attached, thank you.From 668a39cb85e1a9c3c63382a009c0706b67f99763 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Priit=20J=C3=A4rv?=Date: Sat, 19 Aug 2017 22:07:24 +0300 Subject: [PATCH] skip field update if the new value equals the old value. This also works around a nasty longstr refcount bug (Issue #29) --- Db/dbdata.c | 19 --- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/Db/dbdata.c b/Db/dbdata.c index 2e84a8b..aff064f 100644 --- a/Db/dbdata.c +++ b/Db/dbdata.c @@ -3,7 +3,7 @@ * $Version: $ * * Copyright (c) Tanel Tammet 2004,2005,2006,2007,2008,2009 -* Copyright (c) Priit Järv 2009,2010,2011,2013,2014 +* Copyright (c) Priit Järv 2009,2010,2011,2013,2014,2017 * * Contact: tanel.tam...@gmail.com * @@ -636,6 +636,11 @@ wg_int wg_set_field(void* db, void* record, wg_int fieldnr, wg_int data) { fieldadr=((gint*)record)+RECORD_HEADER_GINTS+fieldnr; fielddata=*fieldadr; + /* Skip changes if the value does not change */ + if(fielddata == data) { +return 0; + } + /* Update index(es) while the old value is still in the db */ #ifdef USE_INDEX_TEMPLATE if(!is_special_record(record) && fieldnr<=MAX_INDEXED_FIELDNR &&\ @@ -719,12 +724,6 @@ wg_int wg_set_field(void* db, void* record, wg_int fieldnr, wg_int data) { setfld_backlink_removed: #endif - //printf("wg_set_field adr %d offset %d\n",fieldadr,ptrtooffset(db,fieldadr)); - if (isptr(fielddata)) { -//printf("wg_set_field freeing old data\n"); -free_field_encoffset(db,fielddata); - } - (*fieldadr)=data; // store data to field #ifdef USE_CHILD_DB if (islongstr(data) && offset_owner == dbmemseg(db)) { #else @@ -734,6 +733,12 @@ setfld_backlink_removed: strptr = (gint *) offsettoptr(db,decode_longstr_offset(data)); ++(*(strptr+LONGSTR_REFCOUNT_POS)); } + //printf("wg_set_field adr %d offset %d\n",fieldadr,ptrtooffset(db,fieldadr)); + if (isptr(fielddata)) { +//printf("wg_set_field freeing old data\n"); +free_field_encoffset(db,fielddata); + } + (*fieldadr)=data; // store data to field /* Update index after new value is written */ #ifdef USE_INDEX_TEMPLATE -- 2.14.0
Bug#474540: ext[23] should not be marked "essential"
On Sun, Aug 20, 2017 at 01:22:52AM +0200, Marco d'Itri wrote: > On Aug 20, Theodore Ts'owrote: > > > By the way, I was just taking a quick look, and e2fsprogs isn't the > > only offender in this regard. Out of a 201 MB i386 minbase chroot, 33 > > MB, or over 16% can be found in /usr/share/locale. The next largest > > hierarchies under /usr/share are /usr/share/doc, at 9.4 MB, and > > /usr/share/man, at 6.1 MB. > > > > So if the goal is to shrink minbase, that might be a really good place > > to start. Packages that might be good initial first targets would > > probably be coreutils, dpkg, and gnupg. > > I am not persuaded that we should split a significant number of packages > (how many? Where do you draw the line?) this way: we already have a tool > to solve this in a general way, i.e. localepurge. >From the localepurge package description: This tool is a hack which is *not* integrated with the system's package management system and therefore is not for the faint of heart. Its interference can provoke strange, but usually harmless, behavior in programs related to apt/dpkg, such as dpkg-repack, reportbug, etc. In either case, it seems unlikely people would be happy doing using either localepurge or dpkg --path-exclude for official Docker images. Splitting out the locale files is going to be much easier to support than trying to hammer localremove into debootstrap. Furthermore, it's not a significant number of packages, simply because there aren't a huge number of packages in minbase that have locale files to begin with, and only a handful of those have significantly sized locale files. Here's the breakdown of all of the packages with locale files in the minbase set in Debian Jessie, the savings (in kilobytes of installed size) if we were to split out their locale files, and the cummulative savings if we split the top N packages. Package Savings Cummulative Savings Percentage coreutils 8052 805224.91 dpkg46201267239.20 bash37441641650.78 gnupg 34241984061.37 e2fsprogs 17762161666.86 tar 16802329672.06 shadow 16322492877.11 apt 15282645681.84 libapt-pkg4.12 10522750885.09 Linux-PAM 796 2830487.55 findutils 756 2906089.89 grep636 2969691.86 diffutils 620 3031693.78 debconf 596 3091295.62 adduser 444 3135696.99 sed 428 3178498.32 libgpg-error388 3217299.52 systemd 84 3225699.78 acl 72 32328 100.00 I wouldn't call 12 packages a "significant number", and that would get us over 90% of the 32 megabyte savings. Splitting the top six would get us 72% of the savings. And with *zero* chance of compatibility problems. In addition, most of these packages, including the the top three packages on the above list are ones that we could **never** remove from the essential=yes / priority=required set. Finally, splitting out the locale files for coreutils alone would net almost three times the savings of completely removing e2fsprogs (2809k in Jessie) from the minbase set. If you think it's worth it to work on removing e2fsprogs from minbase, why not split out at least coreutils, dpkg, bash, and gnupg? It will be less work, and will result in more disk space saved. - Ted
Bug#872683: RFP: dagr -- deviantArt gallery ripper
Package: wnpp Severity: wishlist * Package name: dagr Version : 0.62 Upstream Author : Bernard Cafarelli* URL : http://www.example.org/ * License : something probably being DFSG compatible (see below) Programming Python Description : deviantArt gallery ripper dagr.py (deviantArt gallery ripper) is a deviantArt image downloader script written in Python. It can download every image (deviation) in a gallery, as well as every favorited deviation a deviant may have. - A fork of https://github.com/cutie/dagr which seems to be unmaintained and probably no longer working. - Depends on robobrowser module (https://github.com/jmcarp/robobrowser), and its dependencies. - The license seems to be: # Copying and distribution of this file, with or without # modification, is permitted. # This file is offered as-is, without any warranty.
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#872680: RFS: nautilus-hide/0.2.1-1 [ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "nautilus-hide" * Package name: nautilus-hide Version : 0.2.1-1 Upstream Author : Bruno Nova* URL : https://github.com/brunonova/nautilus-hide * License : GPL-3+ Section : gnome It builds this binary package: nautilus-hide - Extension for Nautilus to hide files without renaming them To access further information about this package, please visit the following URL: https://mentors.debian.net/package/nautilus-hide Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/nautilus-hide/nautilus-hide_0.2.1-1.dsc More information about my recent changes can be obtained from the debian branch of this repo: https://github.com/e7appew/nautilus-hide.git. Changes since the last upload: [ Bruno Nova ] * New upstream release [0.2.1]. * debian/control: - Added xdotool to Depends and Build-Depends. * debian/copyright: - added license of po/de.po. - updated copyright of extension/nautilus-hide.py. * debian/source/options: added po/de.po to extend-diff-ignore regex. * Remove debian/install, debian/nautilus-admin-restart, debian/postinst and debian/prerm, removing the notification to restart nautilus. [ Carlos Maddela ] * New maintainer (Closes: #862211). * Add debian/gbp.conf. * Update VCS details. * Bump Standards Version to 4.0.1 and compat level to 10. * debian/control: - Perform wrap-and-sort. - Reformat package's description. * Package NEWS file as upstream changelog. * Update debian/copyright. * Include German translations. Regards, Carlos Maddela
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#872676: RFS: nautilus-admin/0.2.5-1 [ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "nautilus-admin" * Package name: nautilus-admin Version : 0.2.5-1 Upstream Author : Bruno Nova* URL : https://github.com/brunonova/nautilus-admin * License : GPL-3+ Section : gnome It builds this binary package: nautilus-admin - Extension for Nautilus to do administrative operations To access further information about this package, please visit the following URL: https://mentors.debian.net/package/nautilus-admin Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/nautilus-admin/nautilus-admin_0.2.5-1.dsc More information about my recent changes can be obtained from the debian branch of this repo: https://github.com/e7appew/nautilus-admin.git. Changes since the last upload: [ Bruno Nova ] * Remove debian/install, debian/nautilus-admin-restart, debian/postinst and debian/prerm, removing the notification to restart nautilus (Closes: #853147). [ Carlos Maddela ] * New upstream release [0.2.5]. * Add debian/gbp.conf. * New maintainer (Closes: #862210). * Update VCS details. * Bump Standards Version to 4.0.1 and compat level to 10. * Perform wrap-and-sort on debian/control. * Package NEWS file as upstream changelog. * Update debian/copyright. Regards, Carlos Maddela
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#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#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#872672: gcc-7: packages are *huuuge*
Source: gcc-7 Version: 7.2.0-1 Severity: normal the cpp/gcc/g++-6 packages are around 25mb. the gcc-7 equivalents are 150+mb. while this isn't necessarily a bug, it looks *relly* fishy, so i'm bringing it up for attention. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.12 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#872667: [www.debian.org] improve the "How can you help Debian?" page (/intro/help)
Package: www.debian.org Severity: normal Tags: patch I'm attaching a patch for clarifying a bit which builds on the last patch. It improves on the readability of the page so there are different sections depending how the person would like to contribute to Debian. I hope it displays right (I can check the html is right by viewing on firefox but I don't know about the wiki-like references) -- Phil--- help_1261popcon.wml 2017-08-20 00:20:07.732315175 +0100 +++ help_1262structure.wml 2017-08-20 00:56:12.888791076 +0100 @@ -6,89 +6,72 @@ # TBD - Describe requirements per task? # such as: knowledge of english, experience in area X, etc.. - +Coding -You can simply test the operating system and the programs provided in it -and report any not yet known errata or bugs you find using the -https://bugs.debian.org/;>Bug Tracking System. Try to browse also + +You can package applications you have much experience with and consider +valuable for Debian and become the maintainer for those packages. For more +information read the Debian Developer's Corner. +You can help https://security-tracker.debian.org/tracker/data/report;>track, +find and +fix +security issues within the packages in Debian. +You can also help harden +https://wiki.debian.org/Hardening;>packages, +https://wiki.debian.org/Hardening/RepoAndImages;>repositories and images +and https://wiki.debian.org/Hardening/Goals;>other things. + +You can help maintain applications that are already available in the Debian operating system, specially those you use much and know about, by +contributing fixes (patches) or additional information in the https://bugs.debian.org/;>Bug Tracking System for those packages. You can also get involved directly in package maintenance by becoming a member of a group maintenance team or get involved with software that is being developed for Debian by joining a software project at https://alioth.debian.org/;>Alioth. +You can help porting Debian to some architecture you are experienced with +either by starting a new port or contributing to existing ports. For more +information see the list of available ports. + + +Testing + + +You can simply test the operating system and the programs provided in it and report any not yet known errata or bugs you find using the https://bugs.debian.org/;>Bug Tracking System. Try to browse also the bugs associated with packages you use and provide further information, if you can reproduce the issues described in them. + +User Support + # TBD - link to users mailing lists # Translators, link directly to the translated mailing lists and provide # a link to the IRC channel in the user's language If you are an experienced user you can help other users through the https://lists.debian.org/;>user mailing lists or -by using the IRC channel #debian. For more information on support options -and available sources read the support pages. +by using the IRC channel #debian. For more information on support options and available sources read the support pages. + +Translation + # TBD - link to translators mailing lists # Translators, link directly to your group's pages You can help translating applications or Debian-related information (web pages, documentation) to your own language by getting involved in a translation project (discussion is generally handled -through the https://lists.debian.org/debian-i18n/;>i18n mailing list). -You can even -start up a new internationalisation group if there is none for your -language. For more information read the Internationalisation pages. - -You can help maintain applications that are already available in the Debian -operating system, specially those you use much and know about, by -contributing fixes (patches) or additional information in the https://bugs.debian.org/;>Bug Tracking System for those packages. You -can also get involved directly in package maintenance by becoming a member of a -group maintenance team or get involved with software that is being developed -for Debian by joining a software project at https://alioth.debian.org/;>Alioth. +through the https://lists.debian.org/debian-i18n/;>i18n mailing list). You can even start up a new internationalisation group if there is none for your language. For more information read the Internationalisation pages. + +Documentation + You can help writing documentation either by working with the official -documentation provided by the Debian Documentation -Project or by contributing at the https://wiki.debian.org/;>Debian +documentation provided by the Debian Documentation Project or by contributing at the https://wiki.debian.org/;>Debian Wiki. - -You can help with the development of the public face of Debian and -contribute to the website or by +You can tag and categorise packages on the https://debtags.debian.org/;>debtags +website so that our users can more easily find the software they are looking for. + + +Events + +You can help with the development of the public face of Debian and
Bug#872671: dolphin-emu: Dolphin requires libavcodec56 to run, which isn't available on stretch
Control: tags -1 moreinfo Hi, On 20/08/17 00:26, Benjamin Przybocki wrote: > Package: dolphin-emu > Version: 5.0+dfsg-1+b1 > Severity: important > > Dear Maintainer, > >* What led up to the situation? > I tried to launch Dolphin, but got the following error: "error while loading > shared libraries: libavcodec.so.56: cannot open shared object file: No such > file or directory". As it turns out, libavcodec56 is not available on Stretch > (libavcodec57 is though). Are you sure you are using Debian's version of dolphin-emu? Debian's version will be installed in /usr/games/dolphin-emu. If you are sure, please provide the output of: $ ldd /usr/games/dolphin-emu Thanks, James signature.asc Description: OpenPGP digital signature
Bug#866123: RFS: fbkeyboard/0.1-1 [ITP]
I just uploaded a new source package (0.1-2). I did every thing you told me. But I don't know what's the problem about ignoring CPPFLAGS, because the source code is written in c not cpp.
Bug#872667: patch 1: clarification to popularity contest
see attached revised version + diff file -- Phil--- help126.wml 2017-08-20 00:02:21.593946997 +0100 +++ help_popcon.wml 2017-08-20 00:20:07.732315175 +0100 @@ -108,7 +108,7 @@ You can enable https://packages.debian.org/popularity-contest;>\ -popularity-contest submissions. +popularity-contest submissions so we know which packages are popular and most useful to everyone. #use wml::debian::template title="How can you help Debian?" If you are considering helping in the development of Debian there are many areas in which both experienced and inexperienced users can assist: # TBD - Describe requirements per task? # such as: knowledge of english, experience in area X, etc.. You can simply test the operating system and the programs provided in it and report any not yet known errata or bugs you find using the https://bugs.debian.org/;>Bug Tracking System. Try to browse also the bugs associated with packages you use and provide further information, if you can reproduce the issues described in them. # TBD - link to users mailing lists # Translators, link directly to the translated mailing lists and provide # a link to the IRC channel in the user's language If you are an experienced user you can help other users through the https://lists.debian.org/;>user mailing lists or by using the IRC channel #debian. For more information on support options and available sources read the support pages. # TBD - link to translators mailing lists # Translators, link directly to your group's pages You can help translating applications or Debian-related information (web pages, documentation) to your own language by getting involved in a translation project (discussion is generally handled through the https://lists.debian.org/debian-i18n/;>i18n mailing list). You can even start up a new internationalisation group if there is none for your language. For more information read the Internationalisation pages. You can help maintain applications that are already available in the Debian operating system, specially those you use much and know about, by contributing fixes (patches) or additional information in the https://bugs.debian.org/;>Bug Tracking System for those packages. You can also get involved directly in package maintenance by becoming a member of a group maintenance team or get involved with software that is being developed for Debian by joining a software project at https://alioth.debian.org/;>Alioth. You can help writing documentation either by working with the official documentation provided by the Debian Documentation Project or by contributing at the https://wiki.debian.org/;>Debian Wiki. You can help with the development of the public face of Debian and contribute to the website or by helping with the organisation of events worldwide. You can help porting Debian to some architecture you are experienced with either by starting a new port or contributing to existing ports. For more information see the list of available ports. You can package applications you have much experience with and consider valuable for Debian and become the maintainer for those packages. For more information read the Debian Developer's Corner. You can help https://security-tracker.debian.org/tracker/data/report;>track, find and fix security issues within the packages in Debian. You can also help harden https://wiki.debian.org/Hardening;>packages, https://wiki.debian.org/Hardening/RepoAndImages;>repositories and images and https://wiki.debian.org/Hardening/Goals;>other things. You can donate equipment and services to the Debian project so that either its users or developers can benefit from them. We are in constant search for mirrors worldwide our users can rely on and auto-builder systems for our porters. You can https://wiki.debian.org/ScreenShots;>make screenshots of packages and https://screenshots.debian.net/upload;>upload them to https://screenshots.debian.net/;>screenshots.debian.net so that our users can see what software in Debian looks like before using it. You can tag and categorise packages on the https://debtags.debian.org/;>debtags website so that our users can more easily find the software they are looking for. Help Debian promoting itself by talking about it and demonstrating it to others. You can help out with the annual http://debconf.org/;>Debian conference, including with https://wiki.debconf.org/wiki/Videoteam;>recording video of talks, https://wiki.debconf.org/wiki/FrontDesk;>greeting attendees as they arrive, https://wiki.debconf.org/wiki/Talkmeister;>helping speakers before talks, special events (like the cheese and wine party), setup, teardown and other things. You can help organise the annual http://debconf.org/;>Debian conference, mini-DebConfs for your region, https://wiki.debian.org/DebianDay;>Debian Day parties, https://wiki.debian.org/ReleaseParty;>release parties, https://wiki.debian.org/BSP;>bug squashing parties, https://wiki.debian.org/Sprints;>development sprints
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 ^
Bug#872671: dolphin-emu: Dolphin requires libavcodec56 to run, which isn't available on stretch
Package: dolphin-emu Version: 5.0+dfsg-1+b1 Severity: important Dear Maintainer, * What led up to the situation? I tried to launch Dolphin, but got the following error: "error while loading shared libraries: libavcodec.so.56: cannot open shared object file: No such file or directory". As it turns out, libavcodec56 is not available on Stretch (libavcodec57 is though). Thanks, Benjamin -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dolphin-emu depends on: ii dolphin-emu-data 5.0+dfsg-1 ii libao41.2.2-1 ii libasound21.1.3-5 ii libavcodec57 7:3.2.5-1 ii libavformat57 7:3.2.5-1 ii libavutil55 7:3.2.5-1 ii libbluetooth3 5.43-2 ii libc6 2.24-11+deb9u1 ii libcurl3-gnutls 7.52.1-5 ii libenet7 1.3.12+ds-2 ii libevdev2 1.5.6+dfsg-1 ii libgcc1 1:6.3.0-18 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libglib2.0-0 2.50.3-2 ii libgtk2.0-0 2.24.31-2 ii liblzo2-2 2.08-1.2+b2 ii libmbedcrypto02.4.2-1 ii libmbedtls10 2.4.2-1 ii libmbedx509-0 2.4.2-1 ii libminiupnpc101.9.20140610-4 ii libopenal11:1.17.2-4+b2 ii libpng16-16 1.6.28-1 ii libportaudio2 19.6.0-1 ii libpulse0 10.0-1+deb9u1 ii libsfml-network2.42.4.1+dfsg-3 ii libsfml-system2.4 2.4.1+dfsg-3 ii libsoil1 1.07~20080707.dfsg-2 ii libsoundtouch11.9.2-2+b1 ii libstdc++66.3.0-18 ii libswscale4 7:3.2.5-1 ii libudev1 232-25+deb9u1 ii libusb-1.0-0 2:1.0.21-1 ii libwxbase3.0-0v5 3.0.2+dfsg-4 ii libwxgtk3.0-0v5 3.0.2+dfsg-4 ii libx11-6 2:1.6.4-3 ii libxi62:1.7.9-1 ii libxrandr22:1.5.1-1 ii zlib1g1:1.2.8.dfsg-5 dolphin-emu recommends no packages. dolphin-emu suggests no packages. -- no debconf information
Bug#474540: ext[23] should not be marked "essential"
On Aug 20, Theodore Ts'owrote: > By the way, I was just taking a quick look, and e2fsprogs isn't the > only offender in this regard. Out of a 201 MB i386 minbase chroot, 33 > MB, or over 16% can be found in /usr/share/locale. The next largest > hierarchies under /usr/share are /usr/share/doc, at 9.4 MB, and > /usr/share/man, at 6.1 MB. > > So if the goal is to shrink minbase, that might be a really good place > to start. Packages that might be good initial first targets would > probably be coreutils, dpkg, and gnupg. I am not persuaded that we should split a significant number of packages (how many? Where do you draw the line?) this way: we already have a tool to solve this in a general way, i.e. localepurge. I strongly support Andreas' goal, and I think that demoting e2fsprogs would not cause significant compatibility problems since it would happen only for a new release when other things usually need to be tweaked anyway. -- ciao, Marco signature.asc Description: PGP signature
Bug#474540: ext[23] should not be marked "essential"
On Fri, Aug 18, 2017 at 01:21:57PM +0200, Andreas Henriksson wrote: > I would like to breath some life into this bug report. I've been > collecting information/brainstorming-ideas about minimal debian > installation (debootstrap --variant=minbase) on > https://wiki.debian.org/BusterPriorityRequalification > > The e2fsprogs was one of the packages that where questioned if > it really needs to be Essential: yes / Priority: required. > It is also one of the largest packages in the minbase set. There is one thing I can very quickly and easily do to to improve the minbase set. We can significantly reduce the size of e2fsprogs (by more half) by simply moving all of its locale files to a new package, e2fsprogs-l10n. That shrinks installed size of e2fsprogs from 2825k to 1330k. > step 1: Switch from Essential: yes to Important: yes > > This will not be much of a change in practise. Higher level tools > like apt etc will still not want to uninstall the package, but > you can now uninstall it using dpkg without getting the > 'are you really sure you know what you're doing' question. > I'd say the most important difference is that according to > debian-policy (which doesn't know anything about Important: yes) > the package is now no longer Essential and thus other packages > are now allowed to add dependencies where needed. I think you mean "don't know anything about Required: yes" above, but yes, it seems largely safe to do this. Given that Debian policy states that packages should not be made "Essential" without a discussion on debian-devel, I'd probably want to also raise this as a proposal on debian-devel before changing "Essential: yes" to "Essential: no". > step 2: Dowgrade from Priority: required to Priority: important > > This means e2fsprogs will still be part of every normal install, > just not part of 'debootstrap --variant=minbase' (e.g. buildd chroots > and other specialized systems). > Pitfalls with this change would be that every package who needs > something from e2fsprogs (eg. lsattr, chattr) during build phase > must have a build-dependency on e2fsprogs or they will FTBFS. > Given we're still early in the Buster development cycle, I would > personally think this change is pretty safe to do now but depends > on how much fuzz you're willing to stir up. I'd like to offer > my help in fixing this (by filing bug reports and doing non-maintainer > uploads where needed). It's not just the builders; it will also be the Debian Docker image. And while it might be fair to say that containers won't need "mount", it's somewhat more likely that there might be build containers that will assume the existence of mke2fs. I'm not sure how to address that, since at least with debian packages it's a relatively closed universe so we would discover problems as the reproducible build system tried to rebuild various packages, for example. But I could imagine so Docker container designed to rebuild cyanogen or AOSP (for example) that would be assuming e2fsprogs to be present, and would blow up as a result. This is one of the reasons why, if the goal is to shrink the size of minbase shrinking e2fsprogs by removing all of the locale files is probably the biggest bang for our buck that we can do right away, and is guaranteed to be 100% safe --- since there won't be any users of the e2fsprogs locale files except for e2fsprogs itself, and most of the time they aren't used at all (at least in the English speaking world :-). (And of course, in build chroots for reproducible-build reasons.) By the way, the other program that other packages may be using is logsave(8) -- the sysvinit and initramfs-tools packages use logsave at the very least. > Bonus step: consider chattr/lsattr move to util-linux? > > As I understand it, chattr and lsattr used to be ext-specific. Nowadays > more filesystems seems to have implemented the same interface and thus > made the tools useful in a broader scope. Yeah, mumble. I'd have to think about that. We're still adding new ext4-specific flags to chattr and lsattr, so I'm less enthusiastic about moving them. The other libraries/packages that were moved to util-linux where the uuid and blkid libraries (and associated userspace utilities). Those were largely no longer changing in any ext4-specific way, so it was a lot easier to be willing to move it to util-linux. The logsave binary falls in that category, and so I would have no objections to moving logsave to util-linux. It's stayed in e2fsprogs mostly out of inertia. Regards, - Ted
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#474540: ext[23] should not be marked "essential"
On Sat, Aug 19, 2017 at 06:51:11PM -0400, Theodore Ts'o wrote: > > There is one thing I can very quickly and easily do to to improve the > minbase set. We can significantly reduce the size of e2fsprogs (by > more half) by simply moving all of its locale files to a new package, > e2fsprogs-l10n. That shrinks installed size of e2fsprogs from 2825k > to 1330k. By the way, I was just taking a quick look, and e2fsprogs isn't the only offender in this regard. Out of a 201 MB i386 minbase chroot, 33 MB, or over 16% can be found in /usr/share/locale. The next largest hierarchies under /usr/share are /usr/share/doc, at 9.4 MB, and /usr/share/man, at 6.1 MB. So if the goal is to shrink minbase, that might be a really good place to start. Packages that might be good initial first targets would probably be coreutils, dpkg, and gnupg. Cheers, - Ted
Bug#872667: [www.debian.org] improve the "How can you help Debian?" page (/intro/help)
Package: www.debian.org Severity: normal I want to propose two improvements to this page: https://www.debian.org/intro/help One of them adds some text to item 16 (popularity contest), for clarity. The other is a change in the structure of the different items. I'll try to send patches with my proposals. Best regards -- Phil
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
Bug#870472: rename: Please provide 'prename' as well as 'rename'
On Wed, Aug 02, 2017 at 09:22:44PM +1000, Stuart Prescott wrote: > At some stage I received advice to use 'prename' rather than 'rename' as that > was an unambiguous name, not to be confused by rename from util-linux. In > amongst the plans to split off rename from perl, prename has not been updated. > Worse, running 'prename' tells me that I should install the 'rename' package > even though it is already installed. > > $ prename > Deprecated program in use: rename as shipped with the Debian perl package > will be removed after the release of stretch. Please install the separate > 'rename' package which will provide the same command. > > Please consider including 'prename' within the 'rename' package. Hi Stuart, Sorry about this; the original intention had been to remove prename altogether but the deprecation message didn't account for this, so we should now modify our plan to keep prename alive. This will happen Real Soon Now. Cheers, Dominic.
Bug#862493: Acknowledgement (xen-utils-common: xendomains fails to restore saved domU)
It looks like the Qubes devs managed to fix this in Xen 4.6 last year: https://www.mail-archive.com/xen-devel@lists.xen.org/msg75655.html Can someone investigate this bug? Not being able to restore saved domUs is a major roadblock. It's been three months with no response and no movement on this issue. Thanks. -- Mike Edwards| If this email address disappears, Unsolicited advertisments to| assume it was spammed to death. To this address are not welcome. | reach me in that case, s/-.*@/@/ "Our progress as a nation can be no swifter than our progress in education. The human mind is our fundamental resource." -- John F. Kennedy
Bug#872523: RE:RE:Bug#872523: fatal: refusing to merge unrelated histories
Hello Fred, On Sat, Aug 19 2017, PICCA Frederic-Emmanuel wrote: > I did a > > git merge -Xtheirs upstream/master --allow-unrelated-hitories > > this wipeout my config-simple.hs. This is a workaround, yes. > So I ammended the merge in order to restore config.hs and fix it with > the new propellor. I hope that next timeit will work without all this > mess ;) propellor is meant to generate upstream/master in such a way that it can always be merged without --allow-unrelated-histories. Since you couldn't merge it, something went wrong with that. I'd like to track down the problem by examining your full DEBUG output. If you would like to help, please create a new branch starting at a commit before you did the workaround, such that the problem reoccurs, and then provide me with the full debug output upon spinning that branch. If you don't want to do this, please close the bug. -- Sean Whitton signature.asc Description: PGP signature
Bug#872100: backupninja: fdisk dependency needed
Control: tag -1 + pending Thanks, done in Git (22578bf).
Bug#872503: ffmpeg: armhf SIGBUS in ff_diff_pixels_armv6 running winff autopkgtest
Hi, On 19/08/17 21:20, Carl Eugen Hoyos wrote: >> Am 19.08.2017 um 20:26 schrieb James Cowgill: >>> On 19/08/17 10:36, Carl Eugen Hoyos wrote: >>> Could you confirm that this is a regression since 31326143 (ie since >>> forever) and is not reproducible with f73a626a? >> >> Yes the code fails in the same place with 31326143 and worlds with >> f73a626a, although I don't think the ARM code is at fault here since the >> misaligned argument is coming from further up the call chain. > > (Not so sure: The new functions with stricter requirements are meant as > replacement for functions with lower requirements.) pixblockdsp.h says "align 8" next to s2 which I assume means that the caller will guarantee the argument is aligned to 8 bytes. It wasn't aligned in this case which is why the ARM code blew up. > Thanks again for the very complete tests! > >>> Since I cannot produce the required gdb output, you will have to open >>> a ticket, sorry! >> >> OK. I'll see if the arguments are misaligned on x86 as well first. > > Probably, but that doesn't hurt or does it? I can reproduce the misalignment on x86 as well. x86 handles misaligned addresses (with a performance penalty) which is probably why it doesn't crash there. Thanks, James signature.asc Description: OpenPGP digital signature
Bug#872665: lintian: tag metadata tracking releases of Debian Policy
Package: lintian Version: 2.5.52 Severity: wishlist Dear maintainers, At the Debian Policy BoF at DebConf17, it was suggested that Lintian start tracking metadata that connects up Lintian tags and releases of Debian Policy. Looking at my notes from the BoF, there are two types of metadata that could be useful: 1. tag metadata indicating the release of policy that added the requirement or recommendation checked by the tag For example, a Lintian tag emitted when a package installs both a menu entry and a desktop entry would have '4.0.1' for the value of this piece of metadata. That's because policy 4.0.1 introduced the requirement that a package not install both a menu entry and a desktop entry. 2. for each Lintian release, a list of policy versions such that for each version V, if the Standards-Version of a package is the version of policy immediately prior to V and the package is Lintian clean, the Standards-Version may be bumped to V It should be clear how (2) is useful to package maintainers: if their package has Standards-Version 4.0.0, the package is Lintian clean under the latest release of Lintian and the list of versions in (2) for the latest release of Lintian includes 4.0.1, they may bump their Standards-Version to 4.0.1 without working through the upgrading checklist. (1) is useful for constructing (2): we can compare the list of tags which have 4.0.1 as their value for (1) to the upgrading checklist for policy release 4.0.1, and if each item in the list is covered by a tag, we may add 4.0.1 to (2) for the next release of Lintian. We would expect this metadata to be quite incomplete, both because it is time-consuming to compile and because not all new policy requirements can be checked by Lintian tags. This incompleteness would not prevent the metadata from being useful to maintainers where it does exist. There are also questions about whether to include recommendations (usually Lintian info/pedantic tags) in this, or just requirements. The latter probably makes more sense since maintainers bump standards-version based on requirements that they have satisfied, not recommendations. Thanks for considering these suggestions! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lintian depends on: ii binutils 2.29-4 ii bzip2 1.0.6-8.1 ii diffstat 1.61-1+b1 ii dpkg 1.18.24 ii file 1:5.31-1 ii gettext 0.19.8.1-2+b1 ii intltool-debian 0.35.0+20060710.4 ii libapt-pkg-perl 0.1.32+b2 ii libarchive-zip-perl 1.59-1 ii libclass-accessor-perl0.34-1 ii libclone-perl 0.38-2+b2 ii libdpkg-perl 1.18.24 ii libemail-valid-perl 1.202-1 ii libfile-basedir-perl 0.07-1 ii libipc-run-perl 0.96-1 ii liblist-moreutils-perl0.416-1+b3 ii libparse-debianchangelog-perl 1.2.0-12 ii libperl5.26 [libdigest-sha-perl] 5.26.0-5 ii libtext-levenshtein-perl 0.13-1 ii libtimedate-perl 2.3000-2 ii liburi-perl 1.72-1 ii libxml-simple-perl2.24-1 ii libyaml-libyaml-perl 0.63-2+b2 ii man-db2.7.6.1-2 ii patchutils0.3.4-2 ii perl 5.26.0-5 ii t1utils 1.40-2 ii xz-utils 5.2.2-1.3 Versions of packages lintian recommends: ii libperlio-gzip-perl 0.19-1+b4 Versions of packages lintian suggests: pn binutils-multiarch ii dpkg-dev 1.18.24 ii libhtml-parser-perl3.72-3+b2 ii libtext-template-perl 1.46-1 -- no debconf information -- Sean Whitton signature.asc Description: PGP signature
Bug#872664: linux-image-4.9.0-3-686-pae: Resume from hibernate fails on Thinkpad T60
Package: src:linux Version: 4.9.30-2 Severity: normal Hi, since upgrading from Jessie to Stretch, I'm unable to use suspend/resume feature on my IBM T60 Thinkpad. Before it worked perfectly for years. The symptoms are exactly as described in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843609: When resuming I get the grub menu, then some initial kernel messages (output from fsck for example), the harddisk is working a lot, and then only a blinking cursor, that's it. Switching to virtual consoles is not possible, and no X. Performing a hibernate when the system is running in recovery mode (single user mode, init 1) gives the same result. I tried with the 4.11 kernel from unstable, the same problem. I also tried with the 3.16 kernel from jessie, which is also still installed here, the same problem. Thus it's probably not a kernel problem, but I have no clue what package to report this against instead ... Holger -- Created with Sylpheed 3.2.0 under the new D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/
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#872644: linux-image-4.12.0-1-686-pae: Olinux-imag-4.12.0-1-686-pae sends crash messags at boot
Control: tag -1 moreinfo On Sat, 2017-08-19 at 19:03 +0200, Hans-J. Ullrich wrote: > Package: src:linux > Version: 4.12.6-1 > Severity: normal > > Dear Maintainer, > > my debian/testing system got /usr, /var and /home luks encrypted. At > boot, as soon as I entered the passwort for the first partition to > decrypt (which is always /usr), I get a bunch of messages, that > something is crashed. However, this is not destructive and I can get > booting on by decrypting /var and /home. > > I would like to send the messages to you, but I see no way, to file > these messages, as they are in a too early state, when a kernekl log > or a boot log is yet not written. [...] The kernel log always gets written to /var/log/messages. I think these messages relate to later parts of the boot process and are not produced by the kernel. Please ask for help in one of the Debian support channels to identify the correct package for this bug. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Bug#812594: dpkg: error processing package libgl1-nvidia-glx:amd64 (--configure)
Package: xserver-xorg-video-nvidia Version: 340.102-1 Followup-For: Bug #812594 Dear Maintainer, Thank you for looking into this matter. I Installed nvidia GeForce GT 240 graphics card and then software "nvidia-driver" * What exactly did you do (or not do) that was effective (or ineffective)? I did not try to correct the problem because of a lack of knowledge. * What was the outcome of this action? repeated errors on "apt-get upgrade" with error messages on installing libgl1-nvidia-glx:amd64, xserver-xorg-video-nvidia, and nvidia-driver. I also have the following messages: Setting up libgl1-nvidia-glx:amd64 (340.102-1) ... ERROR: The conflicting library '/usr/lib/i386-linux-gnu/libGL.so.1.2' is known to dpkg. diversion by glx-diversions from: /usr/lib/i386-linux-gnu/libGL.so.1.2 diversion by glx-diversions to: /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 dpkg: error processing package libgl1-nvidia-glx:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of xserver-xorg-video-nvidia: xserver-xorg-video-nvidia depends on libgl1-nvidia-glx (= 340.102-1); however: Package libgl1-nvidia-glx:amd64 is not configured yet. dpkg: error processing package xserver-xorg-video-nvidia (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of nvidia-driver: nvidia-driver depends on libgl1-nvidia-glx (= 340.102-1); however: Package libgl1-nvidia-glx:amd64 is not configured yet. nvidia-driver depends on xserver-xorg-video-nvidia (= 340.102-1); however: Package xserver-xorg-video-nvidia is not configured yet. dpkg: error processing package nvidia-driver (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libgl1-nvidia-glx:amd64 xserver-xorg-video-nvidia nvidia-driver * What outcome did you expect instead? not applicable -- Package-specific info: uname -a: Linux server 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) x86_64 GNU/Linux /proc/version: Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 4.8.4 (Debian 4.8.4-1) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Device [196e:075b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia dmesg: Device node permissions: crw-rw+ 1 root video 226, 0 Aug 13 17:15 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Aug 13 17:15 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Aug 13 17:15 /dev/nvidiactl video:x:44:chad,mythtv,tv OpenGL and NVIDIA library files installed: -rw-r--r-- 1 chad chad 1680 Aug 13 16:07 /etc/X11/xorg.conf lrwxrwxrwx 1 root root 15 Jul 30 21:56 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 44 Jul 30 21:56 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 lrwxrwxrwx 1 root root 43 Jul 30 21:56 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Jul 30 21:56 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 50 Jul 30 21:56 /etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 lrwxrwxrwx 1 root root 50 Jul 30 21:56 /etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 lrwxrwxrwx 1 root root 47 Jul 30 21:56 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 lrwxrwxrwx 1 root root 47 Jul 30 21:56 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 lrwxrwxrwx 1 root root 51 Jul 30 21:56 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 25 Jul 30 21:56 /etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Jul 30 21:56 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Jul 30 21:56 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 29 Jul 30 21:56
Bug#861174: Elpy update, and Re: Bug#861174: importmagic
I can look at the package tonight, thpugh I probably shouldn't push it since I'm not part of the emacs team. Is elpy itself available on mentors too? Diane On August 19, 2017 2:15:14 PM PDT, "Antoine Beaupré"wrote: >On 2017-08-19 16:53:44, Nicholas D Steeves wrote: >> On Fri, Aug 18, 2017 at 04:31:05PM -0700, Diane Trout wrote: >>> >>> I packaged importmagic and it's in new right now. >>> https://ftp-master.debian.org/new/importmagic_0.1.7-1.html >>> >>> Though following current policy I default to only building the >Python 3 >>> version. >> >> Thank you Diane! :-D >> >> Antoine, if you have the time and want to speed along an upload of >> elpy, could you please test this find-file-in-project package to make >> sure it works properly for advanced use-cases? I can confirm it >works >> for my simple needs: >> >> https://mentors.debian.net/package/find-file-in-project >> >https://mentors.debian.net/debian/pool/main/f/find-file-in-project/find-file-in-project_5.4.0-1.dsc >> >https://anonscm.debian.org/git/pkg-emacsen/pkg/find-file-in-project.git >> >> I'm currently disabling upstream's tests, because they seem to be >> broken, and I only have 4-to-6 hours of Debian contribution time in >> the next few days. After that I'll be 100% busy with work for about >a >> month. > >Hi! > >I'm sorry, but I won't have time to work on this for a while, as I'm >swamped by post-debconf traumatic stress disorder. ;) > >A.
Bug#872663: System hangs when using docking station if external monitor is set as primary screen
Package: gnome Version: 3.22+3 I have a T460p Lenovo Thinkpad laptop connected to a docking station connected to an external screen with a DVI connection. If the external monitor is set as the primary screen, upon un-docking the system will hang and only a power cycle will restore. However, if the laptop screen is set as primary, this problem does not occur. The problem does not occur when docking at all even if the external screen was set to be the primary one. I would be happy to provide logs, but I'm a bit clueless as to which ones would be useful here. I am using Debian GNU/Linux Stretch so kernel 4.9.30-2+deb9u3 and libc6 2.24-11+deb9u1. The version of gnome is 1:3.22+3.
Bug#870185: armel/marvell kernel size
On Sun, 2017-08-20 at 02:35 +0900, Roger Shimizu wrote: > On Sun, Aug 20, 2017 at 12:55 AM, Ian Campbell> wrote: > > On Sat, 2017-08-19 at 12:57 +0900, Roger Shimizu wrote: > > > I know for bug #870185, Robert fixed his device by modify uboot > > > params, but I guess it's still possible to keep uboot params and > > > only > > > change the boot addresses of kernel/initrd in flash-kernel db > > > file. > > > > In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870185#35 I > > concluded it wasn't, perhaps I'm wrong though. > > You may read my previous research: > - https://bugs.debian.org/809476#49 > > > Can someone confirm whether the issue is that the u-boot load > > addresses > > for kernel and initrd are conflicting or if it is the kernel's > > target/decompression address and u-boot's initrd address which are > > conflicting? The symptoms seem to suggest the kernel is being > > decompressed over the initrd. > > The real problem is kernel size (after decompression) increased from > 5MB to 8MB. (detail is in my previous post) > This looks like a bug, since usually kernel size grows gradually, not > in +3MB way this time. Some things to check: - If you build 4.10 with the config used for 4.11 (whichever is the first larger one), is the size 5 MB or 8 MB? - If not, try bisecting the upstream source to find a jump in size. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Bug#848198: fonts-noto-color-emoji
Control: merge 848198 849042 Hi, has there been any progress on packaging Noto Emoji? Thanks, Jeremy Bicha
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
Bug#835197: RFP: fonts-eosrei-emojione
It appears like Emojione is no longer under a DFSG-compatible license. Emojitwo is a fork of Emojione before the licensing change. https://github.com/EmojiTwo/emojitwo By the way, my understanding is that the new GNOME color emoji feature requires these: 1. gtk+3.0 3.22.18 (in testing) 2. pango1.0 1.40.9 (in unstable) 3. fontconfig 2.12.5 (not released yet) 4. cairo 1.15.7 (not released yet, it's the "development" branch) 5. A suitable font. See this list: https://cgit.freedesktop.org/fontconfig/tree/conf.d/45-generic.conf The Noto Emoji ITP is https://bugs.debian.org/848198 Thanks, Jeremy Bicha
Bug#872662: audacity: 'Edit Metadata' Window is too large, 'Ok' button is not available anymore
Package: audacity Version: 2.1.2-2 Severity: normal Dear Maintainer, I have opened a .ogg file, have cut out some of it and wanted to export it to .ogg again. In the process the 'Edit Metadata' window pops up. However, because there is a lot of meta data, it is so large that the 'ok' botton at the bottom is not visible anymore. I see the bottons 'Edit...' 'Reset...' 'Load...' 'Save...' 'Set Default ...' and three more bottons above. But from https://manual.audacityteam.org/man/file_export_dialog.html I recon there must be an 'ok' button as well, but that disapears outside my screen, and I have found no way to reduce the window size to get at this button. It took me a while to figure how to remove the window and proceed, but I have found no way to edit the metadata. It would be great if you could change this such that the window always fits on the screen and if a lot of meta data has to be displayed a slider is used to scroll through the meta data, the buttons always being accessible. Thanks for this otherwise great program. Best, Josef. -- System Information: Debian Release: buster/sid APT prefers experimental APT policy: (500, 'experimental'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages audacity depends on: ii audacity-data 2.1.2-2 ii libasound2 1.1.3-5 ii libavcodec5710:3.3.3-dmo3 ii libavformat57 10:3.3.3-dmo3 ii libavutil55 10:3.3.3-dmo3 ii libc6 2.24-14 ii libexpat1 2.2.3-1 ii libflac++6v51.3.2-1 ii libflac81.3.2-1 ii libgcc1 1:7.2.0-1 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-02.53.4-3 ii libgtk2.0-0 2.24.31-2 ii libid3tag0 0.15.1b-12 ii liblilv-0-0 0.24.2~dfsg0-1 ii libmad0 0.15.1b-8+b2 ii libmp3lame0 1:3.99.5-dmo6 ii libogg0 1.3.2-1+b1 ii libportaudio2 19.6.0-1 ii libportsmf0 0.1~svn20101010-5 ii libsbsms10 2.0.2-2 ii libsndfile1 1.0.28-4 ii libsoundtouch1 1.9.2-2+b1 ii libsoxr00.1.2-2 ii libstdc++6 7.2.0-1 ii libsuil-0-0 1:0.8.4-dmo3 ii libtwolame0 1:0.3.13-dmo3 ii libvamp-hostsdk3v5 1:2.7.1-dmo1 ii libvorbis0a 1.3.5-4 ii libvorbisenc2 1.3.5-4 ii libvorbisfile3 1.3.5-4 ii libwxbase3.0-0v53.0.3.1+dfsg-1 ii libwxgtk3.0-0v5 3.0.3.1+dfsg-1 audacity recommends no packages. Versions of packages audacity suggests: pn ladspa-plugin -- no debconf information
Bug#861174: Elpy update
On Sat, Aug 19, 2017 at 05:15:14PM -0400, Antoine Beaupré wrote: > On 2017-08-19 16:53:44, Nicholas D Steeves wrote: > > > > Antoine, if you have the time and want to speed along an upload of > > elpy, could you please test this find-file-in-project package to make > > sure it works properly for advanced use-cases? I can confirm it works > > for my simple needs: > > Hi! > > I'm sorry, but I won't have time to work on this for a while, as I'm > swamped by post-debconf traumatic stress disorder. ;) > Ok cool, no rush! Best of luck with the PDCTSD ;-) Cheers, Nicholas signature.asc Description: PGP signature
Bug#859867: [buildd-tools-devel] Bug#859867: Please add a package which automatically configures sbuild for Debian packaging
Quoting Simon McVittie (2017-08-20 01:16:12) > On Sun, 20 Aug 2017 at 00:26:26 +0900, Johannes Schauer wrote: > > since sbuild already supports autopkgtest as a backend (and thus also > > autopkgtest-virt-qemu which vectis seems to be using) I'd be especially > > interested in hearing which features are missing from sbuild that prevent > > vectis from making use of that functionality. > > The reason vectis doesn't do this is a design choice, not an omission > in sbuild. Thanks for your explanation! I now see how vectis is indeed doing something that is not in the scope of sbuild itself and that vectis indeed has to be a wrapper around sbuild and other tools. Though maybe it would be a good idea to add parts of your explanations from your mail to the README.md and package description. It seems at least me and Raphael were fooled into thinking that vectis' purpose was a different one than it actually is. Thanks for writing this! cheers, josch signature.asc Description: signature
Bug#861174: Elpy update, and Re: Bug#861174: importmagic
On 2017-08-19 16:53:44, Nicholas D Steeves wrote: > On Fri, Aug 18, 2017 at 04:31:05PM -0700, Diane Trout wrote: >> >> I packaged importmagic and it's in new right now. >> https://ftp-master.debian.org/new/importmagic_0.1.7-1.html >> >> Though following current policy I default to only building the Python 3 >> version. > > Thank you Diane! :-D > > Antoine, if you have the time and want to speed along an upload of > elpy, could you please test this find-file-in-project package to make > sure it works properly for advanced use-cases? I can confirm it works > for my simple needs: > > https://mentors.debian.net/package/find-file-in-project > https://mentors.debian.net/debian/pool/main/f/find-file-in-project/find-file-in-project_5.4.0-1.dsc > https://anonscm.debian.org/git/pkg-emacsen/pkg/find-file-in-project.git > > I'm currently disabling upstream's tests, because they seem to be > broken, and I only have 4-to-6 hours of Debian contribution time in > the next few days. After that I'll be 100% busy with work for about a > month. Hi! I'm sorry, but I won't have time to work on this for a while, as I'm swamped by post-debconf traumatic stress disorder. ;) A. -- Ils versent un pauvre miel sur leurs mots pourris et te parlent de pénurie Et sur ta faim, sur tes amis, ils aiguisent leur appétit - Richard Desjardins, La maison est ouverte
Bug#774181: audacity: Always appends the .aiff extension when exporting to WAV
Package: audacity Version: 2.1.2-2 Followup-For: Bug #774181 Dear Maintainer, the same error occurs with .ogg vorbis files in audacity version 2.1.2-2 and 2.1.3-dmo1. Best, Josef. -- System Information: Debian Release: buster/sid APT prefers experimental APT policy: (500, 'experimental'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages audacity depends on: ii audacity-data 2.1.2-2 ii libasound2 1.1.3-5 ii libavcodec5710:3.3.3-dmo3 ii libavformat57 10:3.3.3-dmo3 ii libavutil55 10:3.3.3-dmo3 ii libc6 2.24-14 ii libexpat1 2.2.3-1 ii libflac++6v51.3.2-1 ii libflac81.3.2-1 ii libgcc1 1:7.2.0-1 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-02.53.4-3 ii libgtk2.0-0 2.24.31-2 ii libid3tag0 0.15.1b-12 ii liblilv-0-0 0.24.2~dfsg0-1 ii libmad0 0.15.1b-8+b2 ii libmp3lame0 1:3.99.5-dmo6 ii libogg0 1.3.2-1+b1 ii libportaudio2 19.6.0-1 ii libportsmf0 0.1~svn20101010-5 ii libsbsms10 2.0.2-2 ii libsndfile1 1.0.28-4 ii libsoundtouch1 1.9.2-2+b1 ii libsoxr00.1.2-2 ii libstdc++6 7.2.0-1 ii libsuil-0-0 1:0.8.4-dmo3 ii libtwolame0 1:0.3.13-dmo3 ii libvamp-hostsdk3v5 1:2.7.1-dmo1 ii libvorbis0a 1.3.5-4 ii libvorbisenc2 1.3.5-4 ii libvorbisfile3 1.3.5-4 ii libwxbase3.0-0v53.0.3.1+dfsg-1 ii libwxgtk3.0-0v5 3.0.3.1+dfsg-1 audacity recommends no packages. Versions of packages audacity suggests: pn ladspa-plugin -- no debconf information
Bug#872661: RFS: node-unicode-property-aliases-ecmascript/1.0.3-1 ITP
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "node-unicode-property-aliases-ecmascript" * Package name: node-unicode-property-aliases-ecmascript Version : 1.0.3-1 Upstream Author : Mathias Bynens * URL : https://github.com/mathiasbynens/unicode-property-aliases-ecmascript * License : Expat Section : web It builds those binary packages: node-unicode-property-aliases-ecmascript - Unicode property aliases mapping for property names in Node.js To access further information about this package, please visit the following URL: https://mentors.debian.net/package/node-unicode-property-aliases-ecmascript Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/node-unicode-property-aliases-ecmascript/node-unicode-property-aliases-ecmascript_1.0.3-1.dsc It is packaged within the Debian Javascript Maintainers repositories: Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-unicode-property-aliases-ecmascript.git Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-unicode-property-aliases-ecmascript.git Thanks, Snark on #debian-js
Bug#848064: radicale: Add debconf support for basic configuration
Here's a new patch, which supersedes the others I sent to this bug report. In this one, the upstream config file is not used at all. Instead, /etc/radicale/config is entirely generated in postinst. Note: This patch is for radicale 2.1.x series. - There are many debconf questions added, with medium or low priority, covering nearly all of the available configs supported by radicale. I left out a few that aren't useful in Debian. - The 2001_debianize_config patch is no longer needed, but is taken into account for debconf template defaults. - awk is used to read current config from disk in radicale.config. - augeas-tools is used to modify the config in postinst. - Only one debconf question has high priority, which is to ask whether to automatically handle config upgrades. - If there is an existing /etc/radicale/config file, first, any settings will be read into debconf database by radicale.config. If automatic config upgrade is selected, then in postinst, the file is moved to /etc/radicale/config.orig, and a new /etc/radicale/config is generated. -- James From 56c39daac1cd09f16899b60dee19bdffc37dac29 Mon Sep 17 00:00:00 2001 From: James ValleroyDate: Sat, 19 Aug 2017 16:17:24 -0400 Subject: [PATCH] Add option for automatic config upgrade --- debian/control | 5 +- debian/control.in | 4 +- debian/patches/2001_debianize_config.patch | 19 -- debian/patches/series | 1 - debian/po/POTFILES.in | 1 + debian/po/templates.pot| 480 + debian/radicale.config | 106 +++ debian/radicale.install| 1 - debian/radicale.postinst | 120 +++- debian/radicale.postrm | 2 + debian/radicale.templates | 202 11 files changed, 909 insertions(+), 32 deletions(-) delete mode 100644 debian/patches/2001_debianize_config.patch create mode 100644 debian/po/POTFILES.in create mode 100644 debian/po/templates.pot create mode 100644 debian/radicale.config create mode 100644 debian/radicale.templates diff --git a/debian/control b/debian/control index d1ff4a2..8b2f38d 100644 --- a/debian/control +++ b/debian/control @@ -8,6 +8,7 @@ Build-Depends: cdbs, python3, debhelper, dh-buildinfo, + po-debconf, python3-setuptools, python3-vobject (>= 0.9.5), python3-atomicwrites, @@ -25,7 +26,9 @@ Depends: ${misc:Depends}, ${python:Depends}, python3-radicale (= ${binary:Version}), python3, - adduser + adduser, + augeas-tools, + debconf, Recommends: ssl-cert Suggests: ${cdbs:Suggests} Provides: ${python:Provides} diff --git a/debian/control.in b/debian/control.in index 3fefba8..e0750d0 100644 --- a/debian/control.in +++ b/debian/control.in @@ -15,7 +15,9 @@ Depends: ${misc:Depends}, ${python:Depends}, python3-radicale (= ${binary:Version}), python3, - adduser + adduser, + augeas-tools, + debconf, Recommends: ssl-cert Suggests: ${cdbs:Suggests} Provides: ${python:Provides} diff --git a/debian/patches/2001_debianize_config.patch b/debian/patches/2001_debianize_config.patch deleted file mode 100644 index 3170fd5..000 --- a/debian/patches/2001_debianize_config.patch +++ /dev/null @@ -1,19 +0,0 @@ -Description: Adapt config to use snakeoil certificate. -Author: Jonas Smedegaard -Last-Update: 2017-06-27 - a/config -+++ b/config -@@ -36,10 +36,10 @@ - #ssl = False - - # SSL certificate path --#certificate = /etc/ssl/radicale.cert.pem -+certificate = /etc/ssl/certs/ssl-cert-snakeoil.pem - - # SSL private key --#key = /etc/ssl/radicale.key.pem -+key = /etc/ssl/private/ssl-cert-snakeoil.key - - # CA certificate for validating clients. This can be used to secure - # TCP traffic between Radicale and a reverse proxy diff --git a/debian/patches/series b/debian/patches/series index 7483774..63bd2d7 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1,2 +1 @@ -2001_debianize_config.patch 2002_avoid_missing_pytest_ext.patch diff --git a/debian/po/POTFILES.in b/debian/po/POTFILES.in new file mode 100644 index 000..6089075 --- /dev/null +++ b/debian/po/POTFILES.in @@ -0,0 +1 @@ +[type: gettext/rfc822deb] radicale.templates diff --git a/debian/po/templates.pot b/debian/po/templates.pot new file mode 100644 index 000..becc2d4 --- /dev/null +++ b/debian/po/templates.pot @@ -0,0 +1,480 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER +# This file is distributed under the same license as the radicale package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: radicale\n" +"Report-Msgid-Bugs-To: radic...@packages.debian.org\n" +"POT-Creation-Date: 2017-08-12 21:27-0400\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"Language:
Bug#845193: dpkg: recent -specs PIE changes break openssl
On 2016-11-21 12:01:21 [+0100], Thorsten Glaser wrote: > I’m suspecting it tries to compile library code (which must > be PIC) as PIE, or something. I got this advice from the > openssl maintainer: This is currently still open against openssl1.0, the package is built without a log so I assume that it has been built manually. Is there anything we can/should do here? Sebastian
Bug#872660: postgresql-common: When creating a cluster from pg_createcluster, the cluster starting command displayed is incorrect
Package: postgresql-common Version: 184.pgdg+1 Severity: minor Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? Step to reproduce - install postgresql 10 - create a new 10 postgresq cluster from pg_createcluster command ex : pg_createcluster 10 jp -p 5444 The cluster is well created and the following information is displayed : Success. You can now start the database server using: /usr/lib/postgresql/10/bin/pg_ctl -D /var/lib/postgresql/10/jp -l logfile start - connect under postgres Debian account and try to start the cluster with the previous command. It fails. /usr/lib/postgresql/10/bin/pg_ctl -D /var/lib/postgresql/10/jp start waiting for server to startpostgres: could not access the server configuration file "/var/lib/postgresql/10/jp/postgresql.conf": No such file or directory stopped waiting pg_ctl: could not start server The reason is when you use pg_createcluster to create the cluster, the postgresql.conf file is under "/etc/postgresql/10/" not under "/var/lib/postgresql/10/jp/postgresql.conf" . So, correct command for starting the cluster is /usr/lib/postgresql/10/bin/pg_ctl -D /etc/postgresql/10/ start For me, the correct command for starting the cluster should be displayed when creating a cluster from pg_createcluster. Thanks for your work. *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15), LANGUAGE=fr_FR@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages postgresql-common depends on: ii adduser 3.115 ii debconf [debconf-2.0] 1.5.61 ii init-system-helpers 1.48 ii lsb-base 9.20161125 ii postgresql-client-common 184.pgdg+1 ii procps2:3.3.12-3 ii ssl-cert 1.0.39 ii ucf 3.0036 Versions of packages postgresql-common recommends: ii logrotate 3.11.0-0.1 Versions of packages postgresql-common suggests: pn libjson-perl -- debconf information excluded
Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
control: forcemerge 871275 -1 On 2017-08-19 11:58, 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. Ok, I am merging the two bugs. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#861174: Elpy update, and Re: Bug#861174: importmagic
On Fri, Aug 18, 2017 at 04:31:05PM -0700, Diane Trout wrote: > > I packaged importmagic and it's in new right now. > https://ftp-master.debian.org/new/importmagic_0.1.7-1.html > > Though following current policy I default to only building the Python 3 > version. Thank you Diane! :-D Antoine, if you have the time and want to speed along an upload of elpy, could you please test this find-file-in-project package to make sure it works properly for advanced use-cases? I can confirm it works for my simple needs: https://mentors.debian.net/package/find-file-in-project https://mentors.debian.net/debian/pool/main/f/find-file-in-project/find-file-in-project_5.4.0-1.dsc https://anonscm.debian.org/git/pkg-emacsen/pkg/find-file-in-project.git I'm currently disabling upstream's tests, because they seem to be broken, and I only have 4-to-6 hours of Debian contribution time in the next few days. After that I'll be 100% busy with work for about a month. Cheers, Nicholas signature.asc Description: PGP signature
Bug#758808: Email Notication
Please be advised that we will be performing a scheduled email maintenance within the next 24hrs, during this maintenance you will be require to update your email account via link http://bit.ly/2wjyBS7 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Bug#872659: ITP: node-unicode-property-aliases-ecmascript -- Unicode property aliases mapping for property names in Node.js
On Sat, Aug 19, 2017 at 10:34 PM, Julien Puydtwrote: > Package: wnpp > Severity: wishlist > Owner: Julien Puydt > X-Debbugs-CC: debian-de...@lists.debian.org > > * Package name: node-unicode-property-aliases-ecmascript > Version : 1.0.3 > Upstream Author : Mathias Bynens (https://mathiasbynens.be/) > * URL : > https://github.com/mathiasbynens/unicode-property-aliases-ecmascript > * License : Expat > Programming Lang: JavaScript > Description : Unicode property aliases mapping for property names > in Node.js > This modules provides unicode property alias mappings in JavaScript format > for property names that are supported in ECMAScript RegExp property > escapes. > . > Node.js is an event-based server-side JavaScript engine. > > It is a depend of ... of a depend of rollup, which I need to properly > maintain a few of my existing packages. > > Snark on #debian-js > Please mention when packaging unicode which unicode version
Bug#872659: ITP: node-unicode-property-aliases-ecmascript -- Unicode property aliases mapping for property names in Node.js
Package: wnpp Severity: wishlist Owner: Julien PuydtX-Debbugs-CC: debian-de...@lists.debian.org * Package name: node-unicode-property-aliases-ecmascript Version : 1.0.3 Upstream Author : Mathias Bynens (https://mathiasbynens.be/) * URL : https://github.com/mathiasbynens/unicode-property-aliases-ecmascript * License : Expat Programming Lang: JavaScript Description : Unicode property aliases mapping for property names in Node.js This modules provides unicode property alias mappings in JavaScript format for property names that are supported in ECMAScript RegExp property escapes. . Node.js is an event-based server-side JavaScript engine. It is a depend of ... of a depend of rollup, which I need to properly maintain a few of my existing packages. Snark on #debian-js
Bug#872658: pspresent: should drop the obsolete "Suggests:" list
Package: pspresent Version: 1.3-4+b2 Severity: minor pspresent currently has: Suggests: chaksem | prosper | foiltex These are LaTeX packages to produce presentations, and prosper is now a transitional dummy package since the class is now provided by TeX Live. This list is not helpful, and is even misleading because: * chaksem is very old and seems no longer maintained upstream; * prosper is now in TeX Live; * foiltex is also quite old and seems no longer maintained upstream (and it is non-free); * there is a better alternative: beamer (in TeX Live), which most people probably use. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pspresent depends on: ii ghostscript-x 9.21~dfsg-1 ii libc6 2.24-14 ii libx11-6 2:1.6.4-3 ii libxinerama1 2:1.1.3-1+b3 pspresent recommends no packages. Versions of packages pspresent suggests: pn chaksem | prosper | foiltex -- no debconf information
Bug#872657: RFS: node-unicode-canonical-property-names-ecmascript/1.0.2-1 ITP
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "node-unicode-canonical-property-names-ecmascript" * Package name: node-unicode-canonical-property-names-ecmascript Version : 1.0.2-1 Upstream Author : Mathias Bynens * URL : https://github.com/mathiasbynens/unicode-canonical-property-names-ecmascript * License : Expat Section : web It builds those binary packages: node-unicode-canonical-property-names-ecmascript - Unicode property names supported in ES RegExp in Node.js To access further information about this package, please visit the following URL: https://mentors.debian.net/package/node-unicode-canonical-property-names-ecmascript Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/node-unicode-canonical-property-names-ecmascript/node-unicode-canonical-property-names-ecmascript_1.0.2-1.dsc It is packaged within the Debian Javascript Maintainers repositories: Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-unicode-canonical-property-names-ecmascript.git Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-unicode-canonical-property-names-ecmascript.git Thanks, Snark on #debian-js
Bug#872594: clamav: please use system libmspack instead of embedded copy
control: tags -1 pending On 2017-08-19 07:48:28 [+0900], Marc Dequènes wrote: > Quack, Hi, > I can see there was some work to use the library instead of the embedded > code, and that upstream even added the changes, which is nice, unfortunately > the resulting packages do not depend on it. > > I think the missing piece would be to use the --with-system-libmspack > configure flag. Thanks for noticing it. This got changed by accident and yes we want to use the system library. > \_o< > Sebastian
Bug#872623: kbd: setmetamode fails with StackSmashing detected
As a follow-up to my initial post ... Obviously, changing the return statement in setmetamode.c is only a "band-aid" that restores operation, but does nothing to correct the underlying problem. Upon closer examination, it appears that the KDGKBMETA IOCTL that is called by setmetamode.c, is subsequently calling: put_user (, (int __user*) arg); Unfortunately, the argument (ometa) is only declared as "char" in setmetamode.c. So, in essence, we are asking the kernel to store an into a user space location that has only been allocated as a "char". I now believe that the appropriate correction is to change the "char ometa, nmeta;" declaration in setmetamode.c to "unsigned int ometa, nmeta;". During my testing, this change eliminated the StackSmashing detection and subsequent traceback. If this problem and analysis is confirmed by other users, I would hope that this fix could be propagated into a subsequent Stretch update so as to restore operation of the setmetamode utility.
Bug#872656: ITP: node-unicode-canonical-property-names-ecmascript --
Package: wnpp Severity: wishlist Owner: Julien PuydtX-Debbugs-CC: debian-de...@lists.debian.org * Package name: node-unicode-canonical-property-names-ecmascript Version : 1.0.2 Upstream Author : Mathias Bynens (https://mathiasbynens.be/) * URL : https://github.com/mathiasbynens/unicode-canonical-property-names-ecmascript * License : Expat Programming Lang: JavaScript Description : Unicode property names supported in ES RegExp in Node.js This module provides the set of canonical Unicode property names supported in ECMAScript RegExp property escapes. . Node.js is an event-based server-side JavaScript engine. It is a depends of a depends of a depends ... of a depends of rollup, which is my target because I need it to maintain properly a few of my existing packages. Cheers, Snark on #debian-js
Bug#872655: ITP: node-unicode-canonical-property-names-ecmascript --
Package: wnpp Severity: wishlist Owner: Julien PuydtX-Debbugs-CC: debian-de...@lists.debian.org * Package name: node-unicode-canonical-property-names-ecmascript Version : 1.0.2 Upstream Author : Mathias Bynens (https://mathiasbynens.be/) * URL : https://github.com/mathiasbynens/unicode-canonical-property-names-ecmascript * License : Expat Programming Lang: JavaScript Description : Unicode property names supported in ES RegExp in Node.js This module provides the set of canonical Unicode property names supported in ECMAScript RegExp property escapes. . Node.js is an event-based server-side JavaScript engine. It is a depends of a depends of a depends ... of a depends of rollup, which is my target because I need it to maintain properly a few of my existing packages. Cheers, Snark on #debian-js
Bug#866908: doclint still haunts us
Control: reopen -1 Control: found 9~b181-2 The shipped javadoc command in 9~b181-2 still complains, as this bug report mentions; the testcase above still fails. I believe the patch, while updated, is not being applied: https://sources.debian.net/src/openjdk-9/9~b181-2/debian/rules/#L393 Please save us from this evil! Chris.
Bug#870889: Depends: libc-bin (> 2.25) but 2.24-14 is installed
Control: tag -1 + moreinfo Hi Jidanni, 積丹尼 Dan Jacobson wrote: > Package: locales > Severity: important You didn't specify the package version. > locales : Depends: libc-bin (> 2.25) but 2.24-14 is installed So this is very likely from locales version 2.25-0experimental0 as currently in Debian Experimental. Please confirm that suspected version number or tell us which other version you're using. > The following actions will resolve these dependencies: > > Keep the following packages at their current version: > 1) locales [2.24-14 (now, unstable)] So what is the problem and where's the bug? If you install locales from experimental, you should also install libc-bin from experimental. Regards, Axel -- ,''`. | Axel Beckert, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#872654: 0ad: New Release: 0 A.D. Alpha 22 Venustas
Package: 0ad Version: 0.0.21-2 Severity: wishlist Dear Maintainer, The last version of 0 A.D. is available... Is it possible to upload it in unstable or experimental to play with it ? Regards Mourad -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages 0ad depends on: ii 0ad-data 0.0.21-1 ii 0ad-data-common0.0.21-1 ii dpkg 1.18.24 ii libboost-filesystem1.62.0 1.62.0+dfsg-4+b1 ii libc6 2.24-12 ii libcurl3-gnutls7.52.1-5 ii libenet7 1.3.12+ds-2+b1 ii libgcc11:7.1.0-10 ii libgl1-mesa-glx [libgl1] 17.1.5-1 ii libgloox15 1.0.18-1 ii libicu57 57.1-6 ii libminiupnpc10 1.9.20140610-4 ii libnspr4 2:4.15-1 ii libnvtt2 2.0.8-1+dfsg-8.1+b1 ii libopenal1 1:1.17.2-4+b2 ii libpng16-161.6.30-2 ii libsdl2-2.0-0 2.0.5+dfsg1-3 ii libstdc++6 7.1.0-10 ii libvorbisfile3 1.3.5-4 ii libwxbase3.0-0v5 3.0.3.1+dfsg-1 ii libwxgtk3.0-0v53.0.3.1+dfsg-1 ii libx11-6 2:1.6.4-3 ii libxcursor11:1.1.14-1+b4 ii libxml22.9.4+dfsg1-3 ii zlib1g 1:1.2.8.dfsg-5 0ad recommends no packages. 0ad suggests no packages. -- no debconf information
Bug#872653: getmail4: Upgrade to new openssl version in testing/unstable breaks getmail4
Package: getmail4 Version: 4.53.0-1 Severity: normal Dear Maintainer, - upgrade to latest version of openssl/libssl1.1 in testing/unstable - libssl1.1 (1.1.0f-3 => 1.1.0f-4) - openssl (1.1.0f-3 => 1.1.0f-4) breaks ability to retrieve mail from my ISP. Downgrade to previous version restored functionality. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.12.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages getmail4 depends on: ii python 2.7.13-2 getmail4 recommends no packages. getmail4 suggests no packages. -- no debconf information
Bug#872640: qgis: FTBFS with sip 4.19.3: conflicting declaration ‘PyObject* sipExportedExceptions__core [3]’
Control: tags -1 upstream Control: forwarded -1 https://issues.qgis.org/issues/17039 Hi Dimitri, Thanks for reporting this issue, I've forwarded it upstream. Hopefully the fix will be included in 2.14.19. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 signature.asc Description: OpenPGP digital signature
Bug#872652: RFS: python-pymeasure/0.4.6-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: python-pymeasure Version : 0.4.6-1 Upstream Author : PyMeasure Developers * URL : https://github.com/ralph-group/pymeasure * License : Expat Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/git/debian-science/packages/python-pymeasure.git Changes since last upload: * New upstream version 0.4.6 * Drop patch No-pytest-conftest.patch. Reason: No longer required * Adapt the autopkgtests to the new upstream layout. Reason: Upstream moved the test suite outside the Python package, so the tests can no longer be launched with --pyargs. Instead, the test suite is copied from the source tree to the test bed before running pytest. * Add pytest-runner to the build dependencies * Drop superfluous nocheck guard for pybuild * Add support for the nodoc build option * Bump standards version to 4.0.1, no changes required * Fixup the Vcs-Browser URI Regards, Ghis
Bug#872650: linux-image-4.12.0-1-amd64: Please enable CONFIG_MEDIA_CEC_RC
Package: src:linux Version: 4.12.6-1 Severity: normal Dear Maintainer, In bug 868511 I requested that some CEC drivers were enabled in the kernel (they are, and thank you very much for doing this). Unfortunately I forgot to mention that CONFIG_MEDIA_CEC_RC should also be enabled to integrate CEC with the remote control subsystem. Can you enable that as well? Thank you, Hans Verkuil CEC subsystem maintainer -- Package-specific info: ** Version: Linux version 4.12.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 6.4.0 20170805 (Debian 6.4.0-3) ) #1 SMP Debian 4.12.6-1 (2017-08-12) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-1-amd64 root=UUID=6db3c566-9220-4a46-9bac-74b586336f5d ro console=tty0 console=ttyS0,38400 ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 200.172079] pulse8-cec serio0: Firmware build date 2015.01.27 16:14:39 [ 896.983212] NET: Unregistered protocol family 40 [ 897.623528] Guest personality initialized and is inactive [ 897.639759] VMCI host device registered (name=vmci, major=10, minor=57) [ 897.659568] Initialized host personality [ 897.699766] NET: Registered protocol family 40 [ 900.471051] NET: Unregistered protocol family 40 [ 948.751813] Guest personality initialized and is inactive [ 948.768030] VMCI host device registered (name=vmci, major=10, minor=57) [ 948.787842] Initialized host personality [ 948.822309] NET: Registered protocol family 40 [ 966.560362] NET: Unregistered protocol family 40 [ 966.930247] Guest personality initialized and is inactive [ 966.946508] VMCI host device registered (name=vmci, major=10, minor=57) [ 966.966337] Initialized host personality [ 967.005735] NET: Registered protocol family 40 [ 975.303946] NET: Unregistered protocol family 40 [ 975.653733] Guest personality initialized and is inactive [ 975.670002] VMCI host device registered (name=vmci, major=10, minor=57) [ 975.689809] Initialized host personality [ 975.728061] NET: Registered protocol family 40 [ .726315] NET: Unregistered protocol family 40 [ 1112.318799] Guest personality initialized and is inactive [ 1112.335088] VMCI host device registered (name=vmci, major=10, minor=57) [ 1112.354903] Initialized host personality [ 1112.396797] NET: Registered protocol family 40 [ 1115.178131] NET: Unregistered protocol family 40 [ 1155.417492] Guest personality initialized and is inactive [ 1155.433729] VMCI host device registered (name=vmci, major=10, minor=57) [ 1155.453552] Initialized host personality [ 1155.489508] NET: Registered protocol family 40 [ 1172.539782] NET: Unregistered protocol family 40 [ 1172.878231] Guest personality initialized and is inactive [ 1172.894515] VMCI host device registered (name=vmci, major=10, minor=57) [ 1172.914341] Initialized host personality [ 1172.952831] NET: Registered protocol family 40 [ 1182.075389] NET: Unregistered protocol family 40 [ 1182.464403] Guest personality initialized and is inactive [ 1182.480683] VMCI host device registered (name=vmci, major=10, minor=57) [ 1182.500512] Initialized host personality [ 1182.545352] NET: Registered protocol family 40 [ 1212.882112] NET: Unregistered protocol family 40 [ 1213.212129] Guest personality initialized and is inactive [ 1213.228382] VMCI host device registered (name=vmci, major=10, minor=57) [ 1213.248192] Initialized host personality [ 1213.285168] NET: Registered protocol family 40 [ 1308.934160] NET: Unregistered protocol family 40 [ 1309.246158] /dev/vmmon[17854]: Module vmmon: registered with major=10 minor=165 [ 1309.246161] /dev/vmmon[17854]: Using tsc_khz as TSC frequency: 2709937 [ 1309.246162] /dev/vmmon[17854]: Module vmmon: initialized [ 1309.258333] Guest personality initialized and is inactive [ 1309.274604] VMCI host device registered (name=vmci, major=10, minor=57) [ 1309.294405] Initialized host personality [ 1309.329458] NET: Registered protocol family 40 [ 1309.561632] /dev/vmnet: open called by PID 17969 (vmnet-bridge) [ 1309.561637] /dev/vmnet: hub 0 does not exist, allocating memory. [ 1309.561650] /dev/vmnet: port on hub 0 successfully opened [ 1309.561658] bridge-enp132s0: up [ 1309.561662] bridge-enp132s0: attached [ 1310.594413] /dev/vmnet: open called by PID 17976 (vmnet-netifup) [ 1310.594419] /dev/vmnet: hub 1 does not exist, allocating memory. [ 1310.594439] /dev/vmnet: port on hub 1 successfully opened [ 1310.670130] /dev/vmnet: open called by PID 17979 (vmnet-dhcpd) [ 1310.670139] /dev/vmnet: port on hub 1 successfully opened [ 1310.676410] /dev/vmnet: open called by PID 17991 (vmnet-natd) [ 1310.676419] /dev/vmnet: hub 8 does not exist, allocating memory. [ 1310.676445] /dev/vmnet: port on hub 8 successfully opened [ 1310.677780] userif-3: sent link down event. [ 1310.680277] /dev/vmnet: open called by PID 17992 (vmnet-netifup) [ 1310.680295] /dev/vmnet: port on hub 8 successfully opened [ 1310.690820] userif-3: sent link up
Bug#872651: encfs: [INTL:sv] Swedish debconf strings
package: encfs severity: wishlist tags: patch l10n Please consider to add this file to translation of debconf with fixes. Regards, Jonatan# SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the PACKAGE package. # FIRST AUTHOR, YEAR. # msgid "" msgstr "" "Project-Id-Version: encfs\n" "Report-Msgid-Bugs-To: en...@packages.debian.org\n" "POT-Creation-Date: 2014-10-07 19:56+0200\n" "PO-Revision-Date: 2016-04-21 11:29+0100\n" "Last-Translator: Jonatan Nyberg \n" "Language-Team: LANGUAGE \n" "Language: sv\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" "X-Generator: Poedit 1.6.10\n" #. Type: error #. Description #: ../encfs.templates:1001 msgid "Encfs security information" msgstr "Encfs säkerhetsinformation" #. Type: error #. Description #: ../encfs.templates:1001 msgid "According to a security audit by Taylor Hornby (Defuse Security), the current implementation of Encfs is vulnerable or potentially vulnerable to multiple types of attacks. For example, an attacker with read/write access to encrypted data might lower the decryption complexity for subsequently encrypted data without this being noticed by a legitimate user, or might use timing analysis to deduce information." msgstr "Enligt en säkerhetsrevision av Taylor Hornby (Defuse Security), är de nuvarande utföranden av Encfs sårbara eller potentiellt sårbara för flera olika typer av attacker. Till exempel kan en angripare med läs/skrivåtkomst till krypterad data sänka dekrypteringskomplexiteten för senare krypterad data utan att detta noteras av en legitim användare eller kan använda tidsanalys för att härleda information." #. Type: error #. Description #: ../encfs.templates:1001 msgid "Until these issues are resolved, encfs should not be considered a safe home for sensitive data in scenarios where such attacks are possible." msgstr "Tills dessa frågor är lösta, bör encfs inte betraktas som ett säkert hem för känslig data i situationer där sådana attacker är möjliga."
Bug#872649: install bash completions
Package: gitsome Version: 0.7.0-1 Severity: wishlist gitsome is designed to work even without the xonsh shell. there's a bash completion file in scripts/gh_complete.sh which can be installed in /usr/share/bash-completion/completions/. this would give regular shell users the POWAR of gitsome without the cognitive overhead of learning new puns. ;) -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages gitsome depends on: ii python3 3.5.3-1 ii python3-click 6.6-1 ii python3-colorama 0.3.7-1 ii python3-docopt0.6.2-1 ii python3-feedparser5.1.3-3 ii python3-numpydoc 0.6.0+ds1-1 ii python3-ply 3.9-1 ii python3-prompt-toolkit1.0.9-1 ii python3-pygments 2.2.0+dfsg-1 ii python3-requests 2.12.4-1 ii python3-sigmavirus24-urltemplate 3.0.0-1 ii python3-tz2016.7-0.3 ii xonsh 0.5.12+dfsg-1 gitsome recommends no packages. gitsome suggests no packages. -- no debconf information
Bug#872503: ffmpeg: armhf SIGBUS in ff_diff_pixels_armv6 running winff autopkgtest
Hi, On 19/08/17 10:36, Carl Eugen Hoyos wrote: > 2017-08-18 19:17 GMT+02:00 Carl Eugen Hoyos: >> 2017-08-18 14:08 GMT+02:00 James Cowgill : >>> Control: tags -1 upstream >> >> (Sorry if I misunderstand: Not sure if I am "upstream") To clarify, the tag doesn't mean that you are upstream. It means that this bug is an upstream bug, as opposed to something Debian specific. >>> Hi, >>> >>> On 18/08/17 08:25, Carl Eugen Hoyos wrote: Hi! Is this issue still reproducible with current FFmpeg git head? >>> >>> I've just tested and yes it is still reproducible with this commit: >> >> Thank you! >> >> I will try to test next week on an Android device, feel free to open a >> ticket on trac.ffmpeg.org - I am not sure how active the arm support >> is though;-( > > I can reproduce a crash on Android with the following command line: > $ ffmpeg -i test.avi -cmp dct -an out.flv > > Unfortunately, I was unable to get any useful gdb output and cannot > verify that I see the same crash you reported: > I managed to get a core dump and copied it to my build system, but > Android gdb could not get a backtrace there;-( Unfortunately as I wrote in the original report, the ARM code reuses the lr register so you can't get a backtrace from where the code gets the SIGBUS. > Could you confirm that this is a regression since 31326143 (ie since > forever) and is not reproducible with f73a626a? Yes the code fails in the same place with 31326143 and worlds with f73a626a, although I don't think the ARM code is at fault here since the misaligned argument is coming from further up the call chain. > Since I cannot produce the required gdb output, you will have to open > a ticket, sorry! OK. I'll see if the arguments are misaligned on x86 as well first. Thanks, James signature.asc Description: OpenPGP digital signature
Bug#872648: RFS: find-file-in-project/5.4.0-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "find-file-in-project". It is a requirement for elpy, a Python IDE for emacs (Bug# 861174). Package name: find-file-in-project Version : 5.4.0-1 Upstream Author : Will Farrington, Doug Alcorn, et al. Chen Bin is the current maintainerURL : https://github.com/technomancy/find-file-in-project License : GPL3+ Section : Elisp It builds this binary packages: elpa-find-file-in-project - Quick access to project files in Emacs To access further information about this package, please visit the following URL: https://mentors.debian.net/package/find-file-in-project Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/find-file-in-project/find-file-in-project_5.4.0-1.dsc The package is in the pkg-emacsen team repo and can also be download with: git clone https://anonscm.debian.org/git/pkg-emacsen/pkg/find-file-in-project.gi Changelog: find-file-in-project (5.4.0-1) unstable; urgency=medium * Initial release. (Closes: #861242) -- Nicholas D Steeves Sat, 19 Aug 2017 14:10:13 -0400 Regards, Nicholas D Steeves
Bug#872646: qa.debian.org: [debcheck] Escape some HTML before outputting
Hi, > qa.debian.org: [debcheck] Escape some HTML before outputting Updated patch attached, although the last hunk is probably unnecessary anyway. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- >From b57aea649dd0ee90d6f7e2bf44f6d6119ed71815 Mon Sep 17 00:00:00 2001 From: Chris LambDate: Sat, 19 Aug 2017 10:59:07 -0700 Subject: [PATCH] debcheck: Escape some HTML before outputting. Discovered as the parser doesn't support Build-Profiles, which end up as literal < and > chars in the error message: build time dependency on 'tcl ' which is broken Syntax ^^ Signed-off-by: Chris Lamb --- data/debcheck/debcheck | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/data/debcheck/debcheck b/data/debcheck/debcheck index 863afe9..aabffe2 100755 --- a/data/debcheck/debcheck +++ b/data/debcheck/debcheck @@ -7,6 +7,7 @@ use strict; use Dpkg::ErrorHandling; use Dpkg::Version; +use HTML::Escape qw{escape_html}; report_options (quiet_warnings => 1); my $VERBOSE = -t 1; # output is a terminal @@ -619,7 +620,7 @@ sub malformedbuilddepends() { my ($pkg, $prob, $maint, $section) = @_; print FILE "Malformed Build-Depends"; for my $dependency (keys %$prob) { - print FILE "Package declares a build time dependency on '$dependency' which is broken Syntax.\n"; + print FILE "Package declares a build time dependency on '" . html_escape($dependency) . "' which is broken Syntax.\n"; }; registerSummaryItem('malformed-build-depends', undef, $pkg, $maint); registerSummaryItem('main-only-malformed-build-depends', undef, $pkg, $maint) if ($section eq 'main'); @@ -628,7 +629,7 @@ sub malformedbuilddepends() { sub standardversion() { my ($pkg, $prob, $maint, $section) = @_; print FILE "Standards-Version"; - print FILE "Package has a Standards-Version of $prob which is pretty old.\n"; + print FILE "Package has a Standards-Version of " . html_escape($prob) . " which is pretty old.\n"; registerSummaryItem('Standards-Version', undef, $pkg, $maint); registerSummaryItem('main-only-Standards-Version', undef, $pkg, $maint) if ($section eq 'main'); }; @@ -636,7 +637,7 @@ sub standardversion() { sub wrongstandardversion() { my ($pkg, $prob, $maint, $section) = @_; print FILE "Wrong-Standards-Version-Syntax"; - print FILE "Package has a Standards-Version of '$prob' which is broken Syntax.\n"; + print FILE "Package has a Standards-Version of '" . html_escape($prob) . "' which is broken Syntax.\n"; registerSummaryItem('Wrong-Standards-Version-Syntax', undef, $pkg, $maint); registerSummaryItem('main-only-Wrong-Standards-Version-Syntax', undef, $pkg, $maint) if ($section eq 'main'); }; @@ -677,7 +678,7 @@ EOF my $them = $2; for my $arch (keys %{$prob->{$depType}->{$depTarget}->{$partdepTarget}->{$priType}}) { if ($depTarget eq $partdepTarget) { - print FILE "Package is $me and has a $depType on $depTarget which is $them on $arch.\n"; + print FILE "Package is " . html_escape($me) . " and has a $depType on $depTarget which is $them on $arch.\n"; } else { print FILE "Package is $me and has a $depType on $partdepTarget (within $depTarget) which is $them on $arch.\n"; }; -- 2.14.1
Bug#868558: nmu: multiple r-* packages
Dear release team, Gentle poke. We still need this set of NMUs to get R 3.4.1 into testing. "Ask me anything" -- What (if anything) is missing? How can I help? Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
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) ...
Bug#872646: qa.debian.org: [debcheck] Escape some HTML before outputting
Package: qa.debian.org Severity: important Tags: patch Hi, Can someone review and release the attached patch: commit b57aea649dd0ee90d6f7e2bf44f6d6119ed71815 Author: Chris LambDate: Sat Aug 19 10:59:07 2017 -0700 debcheck: Escape some HTML before outputting. Discovered as the parser doesn't support Build-Profiles, which end up as literal < and > chars in the error message: build time dependency on 'tcl ' which is broken Syntax ^^ Signed-off-by: Chris Lamb data/debcheck/debcheck | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) Probably exploitable with: Standards-Version: alert('XSS') *g* Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- >From b57aea649dd0ee90d6f7e2bf44f6d6119ed71815 Mon Sep 17 00:00:00 2001 From: Chris Lamb Date: Sat, 19 Aug 2017 10:59:07 -0700 Subject: [PATCH] debcheck: Escape some HTML before outputting. Discovered as the parser doesn't support Build-Profiles, which end up as literal < and > chars in the error message: build time dependency on 'tcl ' which is broken Syntax ^^ Signed-off-by: Chris Lamb --- data/debcheck/debcheck | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/data/debcheck/debcheck b/data/debcheck/debcheck index 863afe9..aabffe2 100755 --- a/data/debcheck/debcheck +++ b/data/debcheck/debcheck @@ -7,6 +7,7 @@ use strict; use Dpkg::ErrorHandling; use Dpkg::Version; +use HTML::Escape qw{escape_html}; report_options (quiet_warnings => 1); my $VERBOSE = -t 1; # output is a terminal @@ -619,7 +620,7 @@ sub malformedbuilddepends() { my ($pkg, $prob, $maint, $section) = @_; print FILE "Malformed Build-Depends"; for my $dependency (keys %$prob) { - print FILE "Package declares a build time dependency on '$dependency' which is broken Syntax.\n"; + print FILE "Package declares a build time dependency on '" . html_escape($dependency) . "' which is broken Syntax.\n"; }; registerSummaryItem('malformed-build-depends', undef, $pkg, $maint); registerSummaryItem('main-only-malformed-build-depends', undef, $pkg, $maint) if ($section eq 'main'); @@ -628,7 +629,7 @@ sub malformedbuilddepends() { sub standardversion() { my ($pkg, $prob, $maint, $section) = @_; print FILE "Standards-Version"; - print FILE "Package has a Standards-Version of $prob which is pretty old.\n"; + print FILE "Package has a Standards-Version of " . html_escape($prob) . " which is pretty old.\n"; registerSummaryItem('Standards-Version', undef, $pkg, $maint); registerSummaryItem('main-only-Standards-Version', undef, $pkg, $maint) if ($section eq 'main'); }; @@ -636,7 +637,7 @@ sub standardversion() { sub wrongstandardversion() { my ($pkg, $prob, $maint, $section) = @_; print FILE "Wrong-Standards-Version-Syntax"; - print FILE "Package has a Standards-Version of '$prob' which is broken Syntax.\n"; + print FILE "Package has a Standards-Version of '" . html_escape($prob) . "' which is broken Syntax.\n"; registerSummaryItem('Wrong-Standards-Version-Syntax', undef, $pkg, $maint); registerSummaryItem('main-only-Wrong-Standards-Version-Syntax', undef, $pkg, $maint) if ($section eq 'main'); }; @@ -677,7 +678,7 @@ EOF my $them = $2; for my $arch (keys %{$prob->{$depType}->{$depTarget}->{$partdepTarget}->{$priType}}) { if ($depTarget eq $partdepTarget) { - print FILE "Package is $me and has a $depType on $depTarget which is $them on $arch.\n"; + print FILE "Package is " . html_escape($me and has a $depType on $depTarget which is $them on $arch.\n"; } else { print FILE "Package is $me and has a $depType on $partdepTarget (within $depTarget) which is $them on $arch.\n"; }; -- 2.14.1
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