Bug#747141: [debhelper-devel] Bug#747141: ping
Dima Kogan:
> Niels Thykier writes:
>
>> The issue in geda-gaf cannot be solved in debhelper correctly. Please
>> have a look at #766711 to understand the reasoning.
>>
>> Basically:
>> * We can only support two style of binNMUs: arch:all -> arch:all OR
>>arch:any -> arch: any. Anything else will break.
>> * Compat 10 and later will forbid possibly broken setups. We tried to
>>retro fit it into compat 9 and earlier, but it broke in unintended
>>ways (we could not reliably detect the issues).
>
> Hi. Thanks for the reply.
Hi,
You are welcome. :)
> Like you say, "at first glance" (pkg =
> ${source:Version}) would work for this specific case, and that's what
> the second patch here does.
>
FTR, the ${source:Version} is only true for arch:any -> arch:all; for
all "valid" cases, a ${binary:Version} solves it (${source:Version} does
not work for an arch:any -> arch:any). Finally, there is no solution
for arch:all -> arch:any.
> Clearly I haven't thought about this as much as you have, and if it
> really looks unfixable, it'd be great if
>
> - An attempt to make a broken binNMU would hard-fail instead of throwing
> an easily-missed warning
>
This is what we introduced in compat 10 and later.
> - The error message has a link to this and related bugs
>
I suppose this could be done as well.
> Currently dh_installdocs throws an error if compat != 9. Is it
> acceptable to make it fail even for compat == 9?
>
The release team rejected that on the grounds that too many packages
might start to FTBFS. I should mention last time this was considered was
during the jessie freeze, so it would have been rather unhelpful for
them at that time.
I attempted to support detection of the binNMU case and abort on only on
that (so we got a warning on a regular build and a FTBFS on binNMU
rather than a broken package). Unfortunately, it did not work so well.
In the end I settled with fixing it for compat 10.
Thanks,
~Niels
Processed: Re: Bug#857603: unblock: mpi4py/2.0.0-2.1
Processing commands for cont...@bugs.debian.org: > clone 856349 -1 Bug #856349 [src:mpi4py] mpi4py: FTBFS (Exception: MPI_ERR_WIN: invalid window) Bug 856349 cloned as bug 857604 > severity -1 serious Bug #857604 [src:mpi4py] mpi4py: FTBFS (Exception: MPI_ERR_WIN: invalid window) Severity set to 'serious' from 'important' > fixed -1 2.0.0-2.1 Bug #857604 [src:mpi4py] mpi4py: FTBFS (Exception: MPI_ERR_WIN: invalid window) Marked as fixed in versions mpi4py/2.0.0-2.1. > close -1 Bug #857604 [src:mpi4py] mpi4py: FTBFS (Exception: MPI_ERR_WIN: invalid window) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 856349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856349 857604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 857546 is forwarded to https://github.com/boothj5/profanity/issues/280
Processing commands for cont...@bugs.debian.org: > forwarded 857546 https://github.com/boothj5/profanity/issues/280 Bug #857546 [profanity] profanity: Server certificates are not verified Set Bug forwarded-to-address to 'https://github.com/boothj5/profanity/issues/280'. > thanks Stopping processing here. Please contact me if you need assistance. -- 857546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 857546 in 0.5.0-0.1, found 857546 in 0.4.7-1
Processing commands for cont...@bugs.debian.org: > found 857546 0.5.0-0.1 Bug #857546 [profanity] profanity: Server certificates are not verified Marked as found in versions profanity/0.5.0-0.1. > found 857546 0.4.7-1 Bug #857546 [profanity] profanity: Server certificates are not verified Marked as found in versions profanity/0.4.7-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 857546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#854130: libbson FTBFS on mips/mipsel: test-results.json aborted
Hi,
I have back-ported the patch that limits number of threads to 10 to current
debian version (1.5.4-1).
With these changes build pass successfully on my local mips and mipsel machines.
The patch is attached, if you want to go with this solution.
This change is already merged in 1.6.1 release.
Regards,
Radovan--- libbson-1.5.4.orig/tests/TestSuite.c
+++ libbson-1.5.4/tests/TestSuite.c
@@ -48,6 +48,8 @@
static int test_flags;
+const int MAX_THREADS = 10;
+
#define TEST_VERBOSE (1 << 0)
#define TEST_NOFORK(1 << 1)
@@ -629,6 +631,7 @@ typedef struct
{
TestSuite *suite;
Test *test;
+ int n_tests;
Mutex *mutex;
int *count;
} ParallelInfo;
@@ -638,18 +641,27 @@ static void *
TestSuite_ParallelWorker (void *data) /* IN */
{
ParallelInfo *info = (ParallelInfo *)data;
+ Test *test;
+ int i;
int status;
ASSERT (info);
- status = TestSuite_RunTest (info->suite, info->test, info->mutex, info->count);
-
- if (AtomicInt_DecrementAndTest (info->count)) {
- TestSuite_PrintJsonFooter (stdout);
- if (info->suite->outfile) {
- TestSuite_PrintJsonFooter (info->suite->outfile);
+ test = info->test;
+
+ /* there's MAX_THREADS threads, each runs n_tests tests */
+ for (i = 0; i < info->n_tests; i++) {
+ ASSERT (test);
+ status = TestSuite_RunTest (info->suite, test, info->mutex, info->count);
+ if (AtomicInt_DecrementAndTest (info->count)) {
+ TestSuite_PrintJsonFooter (stdout);
+ if (info->suite->outfile) {
+TestSuite_PrintJsonFooter (info->suite->outfile);
+ }
+ exit (status);
}
- exit (status);
+
+ test = test->next;
}
/* an info is allocated for each thread in TestSuite_RunParallel */
@@ -658,6 +670,9 @@ TestSuite_ParallelWorker (void *data) /*
return NULL;
}
+/* easier than having to link with math library */
+#define CEIL(d) ((int) (d) == d ? (int) (d) : (int) (d) + 1)
+
static void
TestSuite_RunParallel (TestSuite *suite) /* IN */
@@ -667,6 +682,8 @@ TestSuite_RunParallel (TestSuite *suite)
Mutex mutex;
Test *test;
int count = 0;
+ int starting_count;
+ int tests_per_thread;
int i;
ASSERT (suite);
@@ -677,19 +694,31 @@ TestSuite_RunParallel (TestSuite *suite)
count++;
}
- threads = (Thread *)calloc (count, sizeof *threads);
+ /* threads start decrementing count immediately, save a copy */
+ starting_count = count;
+ tests_per_thread = CEIL ((double) count / (double) MAX_THREADS);
+ threads = (Thread *) calloc (MAX_THREADS, sizeof *threads);
Memory_Barrier ();
+ /* "tests" is a linked list, a->b->c->d->..., iterate it and every
+* tests_per_thread start a new thread, point it at our position in the list,
+* and tell it to run the next tests_per_thread tests. */
+
for (test = suite->tests, i = 0; test; test = test->next, i++) {
- info = (ParallelInfo *)calloc (1, sizeof *info);
- info->suite = suite;
- info->test = test;
- info->count = &count;
- info->mutex = &mutex;
- Thread_Create (&threads [i], TestSuite_ParallelWorker, info);
+ if (!(i % tests_per_thread)) {
+ info = (ParallelInfo *) calloc (1, sizeof *info);
+ info->suite = suite;
+ info->test = test;
+ info->n_tests = BSON_MIN (tests_per_thread, starting_count - i);
+ info->count = &count;
+ info->mutex = &mutex;
+ Thread_Create (threads, TestSuite_ParallelWorker, info);
+ threads++;
+ }
}
+/* wait for the thread that runs the last test to call exit (0) */
#ifdef _WIN32
Sleep (3);
#else
Bug#856904: ksirk FTBFS on architectures where char is unsigned
Hi! On 03/06/2017 10:49 AM, John Paul Adrian Glaubitz wrote: > The attached debdiff contains a trivial patch which changes the declaration > of tbl[] from "char" to "signed char". With the patch applied, I verified > that the package builds successfully on armhf. Any progress on this? Shall I go ahead and perform an NMU? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#856936: quagga: libquagga0 contains libraries with different SOVERSIONS
Hi all, Thanks for the bug report and for the thoughful advice. On 2017-03-10.11:18, Vincent Bernat wrote: > ❦ 10 mars 2017 09:29 GMT, Simon McVittie : > > >> I suppose that's why I am in copy (the other actions are pretty obvious > >> and I suppose Scott will apply them soon; I can also do that if he's > >> unavailable). Yes, I will make the changes suggested by Simon. I won't be able to do this in the next few days, but will get it done within the next week after that. As the libraries are really intended to be private to the quagga "family" of daemons/utils, I plan to roll them into quagga-core (thanks for the explanation for how to do this correctly!). > > > > The other reason I wanted to Cc you is because as sponsor, you were > > responsible for checking that the package split proposed by the > > maintainer was Policy-compliant. I would have expected a sponsor to > > query the current library packaging and not upload without changes, > > because as it stands at the moment, it isn't correct for either > > private/internal libraries or public libraries; it's somewhere in > > between. > > > > (In particular, seeing the Lintian overrides in the diff should probably > > have been a warning sign.) > > > > During the first upload, the packaging was policy compliant as all > libraries were sharing the same version. There was no override. The > change in SO name for libzebra was done during a minor version > update. At this time, I suggested to solve the problem by ignoring > lintian instead of being overly complicated for a library without > reverse dependencies. My bad. > This was also due to me lacking the experience to solve this somewhat complicated packaging issue. My apologies too. FYI the version bump originated from this post to the upstream mailing list[0], which shows upstream's somewhat relaxed attitude to ABI stability. I guess this is understandable as the libraries are intended to be private. > >> - removing libquagga0 and libquagga-dev and put the libraries in > >>quagga-core and in /usr/lib/quagga. Not shipping the development > >>files. This is a change that would likely to be accepted by the > >>release team. > > > > I would recommend this route. As you say, splitting libquagga0 into > > 5 library packages seems like overkill if nobody is going to use it. Agreed. [0] https://lists.quagga.net/pipermail/quagga-dev/2016-December/033087.html -- Regards, Scott. signature.asc Description: PGP signature
Bug#854130: libbson FTBFS on mips/mipsel: test-results.json aborted
Thanks Radovan. I plan to upload 1.6.1 to Debian soon (via my sponsor Roberto Sanchez) so let's do that instead of backporting.
Processed: bibcursed: diff for NMU version 2.0.0-6.1
Processing control commands: > tags 631057 + pending Bug #631057 [bibcursed] bibcursed: FTBFS with --as-needed Added tag(s) pending. > tags 817375 + patch Bug #817375 [src:bibcursed] bibcursed: Removal of debhelper compat 4 Added tag(s) patch. > tags 817375 + pending Bug #817375 [src:bibcursed] bibcursed: Removal of debhelper compat 4 Added tag(s) pending. -- 631057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631057 817375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bibcursed: diff for NMU version 2.0.0-6.1
Processing control commands: > tags 631057 + pending Bug #631057 [bibcursed] bibcursed: FTBFS with --as-needed Ignoring request to alter tags of bug #631057 to the same tags previously set > tags 817375 + patch Bug #817375 [src:bibcursed] bibcursed: Removal of debhelper compat 4 Ignoring request to alter tags of bug #817375 to the same tags previously set > tags 817375 + pending Bug #817375 [src:bibcursed] bibcursed: Removal of debhelper compat 4 Ignoring request to alter tags of bug #817375 to the same tags previously set -- 631057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631057 817375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#817375: bibcursed: diff for NMU version 2.0.0-6.1
Control: tags 631057 + pending
Control: tags 817375 + patch
Control: tags 817375 + pending
Dear maintainer,
I've prepared an NMU for bibcursed (versioned as 2.0.0-6.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer.
Regards.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
diffstat for bibcursed-2.0.0 bibcursed-2.0.0
bibcursed.c|6 +-
debian/changelog | 15 +
debian/clean |1
debian/compat |2
debian/control |6 +-
debian/install |1
debian/manpages|1
debian/patches/fix-address-field.patch | 15 +
debian/patches/fix-bolding-behaviour.patch | 15 +
debian/patches/fix-manpage.patch | 15 +
debian/patches/ignore-case.patch | 15 +
debian/patches/series |4 +
debian/rules | 81 ++---
debian/source/format |1
14 files changed, 98 insertions(+), 80 deletions(-)
diff -Nru bibcursed-2.0.0/bibcursed.c bibcursed-2.0.0/bibcursed.c
--- bibcursed-2.0.0/bibcursed.c 2017-03-13 14:02:14.0 +0100
+++ bibcursed-2.0.0/bibcursed.c 2002-06-08 13:59:10.0 +0200
@@ -279,7 +279,7 @@
}
else
printw("%s","1. Address ");
- if (set_address == 1) addch('*');
+ if (set_author == 1) addch('*');
print_pos++;
}
if (use_annote != 0)
@@ -345,7 +345,7 @@
if (use_edition != 0)
{
move(print_pos,5);
- if (use_edition == 1)
+ if (use_edition != 1)
{
attron(A_BOLD);
printw("%s","7. Edition ");
@@ -526,7 +526,7 @@
}
/* Check to see if we have all the info we need */
- if (lch == 'z')
+ if (ch == 'z')
{
not_done =0;
if (use_address==1 && set_address == 0)
diff -Nru bibcursed-2.0.0/debian/changelog bibcursed-2.0.0/debian/changelog
--- bibcursed-2.0.0/debian/changelog 2017-03-13 14:02:14.0 +0100
+++ bibcursed-2.0.0/debian/changelog 2017-03-13 13:55:29.0 +0100
@@ -1,3 +1,18 @@
+bibcursed (2.0.0-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use source format 3.0 (quilt).
+ * Turn directly applied patches into single quilt patches in debian/patches.
+ * Fix syntax error in the manpage.
+ * Fix build with -Wl,--as-needed. Closes: #631057
+ * Rewrite debian/rules using the dh sequencer.
+ * Bump debhelper compat level to 10. Closes: #817375
+ * Bump Standards-Version to 3.9.8.
+ * Fix cross building.
+ * Do not start the synopsis with an article.
+
+ -- Mattia Rizzolo Mon, 13 Mar 2017 13:55:29 +0100
+
bibcursed (2.0.0-6) unstable; urgency=low
* debian/control:
diff -Nru bibcursed-2.0.0/debian/clean bibcursed-2.0.0/debian/clean
--- bibcursed-2.0.0/debian/clean 1970-01-01 01:00:00.0 +0100
+++ bibcursed-2.0.0/debian/clean 2017-03-13 11:37:21.0 +0100
@@ -0,0 +1 @@
+bibcursed
diff -Nru bibcursed-2.0.0/debian/compat bibcursed-2.0.0/debian/compat
--- bibcursed-2.0.0/debian/compat 2017-03-13 14:02:14.0 +0100
+++ bibcursed-2.0.0/debian/compat 2017-03-13 11:39:50.0 +0100
@@ -1 +1 @@
-4
+10
diff -Nru bibcursed-2.0.0/debian/control bibcursed-2.0.0/debian/control
--- bibcursed-2.0.0/debian/control 2017-03-13 14:02:14.0 +0100
+++ bibcursed-2.0.0/debian/control 2017-03-13 13:53:14.0 +0100
@@ -2,13 +2,13 @@
Section: tex
Priority: optional
Maintainer: John Wright
-Build-Depends: debhelper (>= 4), libncurses5-dev
-Standards-Version: 3.7.2
+Build-Depends: debhelper (>= 10), libncurses5-dev
+Standards-Version: 3.9.8
Package: bibcursed
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: An interactive program to edit BibTeX bibliographies
+Description: Interactive program to edit BibTeX bibliographies
Bibcursed is a simple program to make life a little easier when using
BibTeX bibliographies. It currently provides these main functions:
.
diff -Nru bibcursed-2.0.0/debian/install bibcursed-2.0.0/debian/install
--- bibcursed-2.0.0/debian/install 1970-01-01 01:00:00.0 +0100
+++ bibcursed-2.0.0/debian/install 2017-03-13 11:40:25.0 +0100
@@ -0,0 +1 @@
+bibcursed usr/bin
diff -Nru bibcursed-2.0.0/debian/manpages bibcursed-2.0.0/debian/manpages
--- bibcursed-2.0.0/debian/manpages 1970-01-01 01:00:00.0 +0100
+++ bibcursed-2.0.0/debian/manpages 2017-03-13 11:47:37.0 +0100
@@ -0,0 +1 @@
+b
Bug#846705: marked as done (cadvisor: FTBFS: dh_auto_build: go install -v -p 1 github.com/google/cadvisor github.com/google/cadvisor/api github.com/google/cadvisor/cache github.com/google/cadvisor/cac
Your message dated Mon, 13 Mar 2017 14:15:00 +0100 with message-id <20170313131457.gm2ms4r6jgbzp...@mapreri.org> and subject line Re: Bug#846705: cadvisor: FTBFS: dh_auto_build: go install -v -p 1 github.com/google/cadvisor github.com/google/cadvisor/api github.com/google/cadvisor/cache github.com/google/cadvisor/cache/memory github.com/google/cadvisor/client github.com/google/cadvisor/client/clientexample github.com/google/cadvisor/client/v2 github.com/google/cadvisor/collector github.com/google/cadvisor/container github.com/google/cadvisor/container/common github.com/google/cadvisor/container/docker github.com/google/cadvisor/container/libcontainer github.com/google/cadvisor/container/raw github.com/google/cadvisor/container/rkt github.com/google/cadvisor/container/systemd github.com/google/cadvisor/events github.com/google/cadvisor/fs github.com/google/cadvisor/healthz github.com/google/cadvisor/http github.com/google/cadvisor/http/mux github.com/google/cadvisor/info/v1 github.com/google/cadvisor/info/v1/test github.com/google/cadvisor/info/v2 github.com/google/cadvisor/integration/framework github.com/google/cadvisor/integration/runner github.com/google/cadvisor/integration/tests/api github.com/google/cadvisor/integration/tests/healthz github.com/google/cadvisor/manager github.com/google/cadvisor/metrics github.com/google/cadvisor/pages github.com/google/cadvisor/pages/static github.com/google/cadvisor/storage github.com/google/cadvisor/storage/bigquery github.com/google/cadvisor/storage/bigquery/client github.com/google/cadvisor/storage/bigquery/client/example github.com/google/cadvisor/storage/elasticsearch github.com/google/cadvisor/storage/influxdb github.com/google/cadvisor/storage/kafka github.com/google/cadvisor/storage/redis github.com/google/cadvisor/storage/statsd github.com/google/cadvisor/storage/statsd/client github.com/google/cadvisor/storage/stdout github.com/google/cadvisor/storage/test github.com/google/cadvisor/summary github.com/google/cadvisor/utils github.com/google/cadvisor/utils/cloudinfo github.com/google/cadvisor/utils/container github.com/google/cadvisor/utils/cpuload github.com/google/cadvisor/utils/cpuload/netlink github.com/google/cadvisor/utils/cpuload/netlink/example github.com/google/cadvisor/utils/machine github.com/google/cadvisor/utils/oomparser github.com/google/cadvisor/utils/oomparser/oomexample github.com/google/cadvisor/utils/procfs github.com/google/cadvisor/utils/sysfs github.com/google/cadvisor/utils/sysfs/fakesysfs github.com/google/cadvisor/utils/sysinfo github.com/google/cadvisor/validate github.com/google/cadvisor/version returned exit code 2 has caused the Debian Bug report #846705, regarding cadvisor: FTBFS: dh_auto_build: go install -v -p 1 github.com/google/cadvisor github.com/google/cadvisor/api github.com/google/cadvisor/cache github.com/google/cadvisor/cache/memory github.com/google/cadvisor/client github.com/google/cadvisor/client/clientexample github.com/google/cadvisor/client/v2 github.com/google/cadvisor/collector github.com/google/cadvisor/container github.com/google/cadvisor/container/common github.com/google/cadvisor/container/docker github.com/google/cadvisor/container/libcontainer github.com/google/cadvisor/container/raw github.com/google/cadvisor/container/rkt github.com/google/cadvisor/container/systemd github.com/google/cadvisor/events github.com/google/cadvisor/fs github.com/google/cadvisor/healthz github.com/google/cadvisor/http github.com/google/cadvisor/http/mux github.com/google/cadvisor/info/v1 github.com/google/cadvisor/info/v1/test github.com/google/cadvisor/info/v2 github.com/google/cadvisor/integration/framework github.com/google/cadvisor/integration/runner github.com/google/cadvisor/integration/tests/api github.com/google/cadvisor/integration/tests/healthz github.com/google/cadvisor/manager github.com/google/cadvisor/metrics github.com/google/cadvisor/pages github.com/google/cadvisor/pages/static github.com/google/cadvisor/storage github.com/google/cadvisor/storage/bigquery github.com/google/cadvisor/storage/bigquery/client github.com/google/cadvisor/storage/bigquery/client/example github.com/google/cadvisor/storage/elasticsearch github.com/google/cadvisor/storage/influxdb github.com/google/cadvisor/storage/kafka github.com/google/cadvisor/storage/redis github.com/google/cadvisor/storage/statsd github.com/google/cadvisor/storage/statsd/client github.com/google/cadvisor/storage/stdout github.com/google/cadvisor/storage/test github.com/google/cadvisor/summary github.com/google/cadvisor/utils github.com/google/cadvisor/utils/cloudinfo github.com/google/cadvisor/utils/container github.com/google/cadvisor/utils/cpuload github.com/google/cadvisor/utils/cpuload/netlink github.com/google/cadvisor/utils/cpuload/netlink/example github.com/google/cadvisor/utils/machine github.com/google/cadvisor/utils/oomparser github.com/google/cadvisor/utils/oomparser
Bug#856936: quagga: libquagga0 contains libraries with different SOVERSIONS
On Mon, 13 Mar 2017 at 23:43:52 +1100, Scott Leggett wrote: > FYI the version bump originated from this post to the upstream mailing > list[0], which shows upstream's somewhat relaxed attitude to ABI > stability. I guess this is understandable as the libraries are intended > to be private. This looks like good evidence for moving the libraries into quagga-core being the right way to resolve this bug. S
Bug#669541: marked as done (underscore.logger: FTBFS: SyntaxError: In src/underscore.logger.coffee, octal escape sequences "\033[#{color}m" are not allowed on line 53)
Your message dated Mon, 13 Mar 2017 15:07:19 +
with message-id
and subject line Bug#857565: Removed package(s) from unstable
has caused the Debian Bug report #669541,
regarding underscore.logger: FTBFS: SyntaxError: In
src/underscore.logger.coffee, octal escape sequences "\033[#{color}m" are not
allowed on line 53
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
669541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: underscore.logger
Version: 0.3.0~2014-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120419 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> debian/rules build
> test -x debian/rules
> mkdir -p "."
>
> Scanning upstream source for new/changed copyright notices...
>
> licensecheck -c '.*' -r --copyright -i
> '^debian/(changelog|copyright(|_hints|_newhints))' -l '9' * |
> /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
> 3 combinations of copyright and licensing found.
> WARNING: The following (and possibly more) new or changed notices discovered:
>
> Format: http://www.debian.org/doc/packaging-manuals/…
> License: GPL-2+
> HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER …
>
> To fix the situation please do the following:
> 1) Fully compare debian/copyright_hints with debian/copyright_newhints
> 2) Update debian/copyright as needed
> 3) Replace debian/copyright_hints with debian/copyright_newhints
> touch debian/stamp-copyright-check
> touch debian/stamp-upstream-cruft
> coffee -o build src/*.coffee
> SyntaxError: In src/underscore.logger.coffee, octal escape sequences
> "\033[#{color}m" are not allowed on line 53
> at SyntaxError (unknown source)
> at Lexer.error (/usr/lib/coffee-script/lib/coffee-script/lexer.js:686:13)
> at Lexer.stringToken
> (/usr/lib/coffee-script/lib/coffee-script/lexer.js:174:14)
> at Lexer.tokenize
> (/usr/lib/coffee-script/lib/coffee-script/lexer.js:35:137)
> at Object.compile
> (/usr/lib/coffee-script/lib/coffee-script/coffee-script.js:43:32)
> at /usr/lib/coffee-script/lib/coffee-script/command.js:182:33
> at /usr/lib/coffee-script/lib/coffee-script/command.js:152:18
> at [object Object]. (fs.js:115:5)
> at [object Object].emit (events.js:64:17)
> at afterRead (fs.js:1117:12)
> make: *** [build/node-underscore.logger] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/04/19/underscore.logger_0.3.0~2014-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--- End Message ---
--- Begin Message ---
Version: 0.3.0~2014-1+rm
Dear submitter,
as the package underscore.logger has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/857565
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#713494: marked as done (underscore.logger: FTBFS: new copyright notices found)
Your message dated Mon, 13 Mar 2017 15:07:19 +
with message-id
and subject line Bug#857565: Removed package(s) from unstable
has caused the Debian Bug report #669541,
regarding underscore.logger: FTBFS: new copyright notices found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
669541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: underscore.logger
Version: 0.3.0~2014-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> debian/rules build
> test -x debian/rules
> mkdir -p "."
>
> Scanning upstream source for new/changed copyright notices...
>
> licensecheck -c '.*' -r --copyright -i
> '^debian/(changelog|copyright(|_hints|_newhints))' -l '9' * |
> /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
> 3 combinations of copyright and licensing found.
> WARNING: The following (and possibly more) new or changed notices discovered:
>
> Format: http://www.debian.org/doc/packaging-manuals/…
> HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER …
> License: Expat
> FIXME
>
> Files: debian/rules
> Copyright: 2011, Jonas Smedegaard
> License: GPL-2+
>
> To fix the situation please do the following:
> 1) Fully compare debian/copyright_hints with debian/copyright_newhints
> 2) Update debian/copyright as needed
> 3) Replace debian/copyright_hints with debian/copyright_newhints
> touch debian/stamp-copyright-check
> touch debian/stamp-upstream-cruft
> coffee -o build src/*.coffee
> SyntaxError: In src/underscore.logger.coffee, octal escape sequences
> "\033[#{color}m" are not allowed on line 53
> at SyntaxError (unknown source)
> at Lexer.error (/usr/lib/coffee-script/lib/coffee-script/lexer.js:682:13)
> at Lexer.stringToken
> (/usr/lib/coffee-script/lib/coffee-script/lexer.js:170:14)
> at Lexer.tokenize
> (/usr/lib/coffee-script/lib/coffee-script/lexer.js:33:137)
> at Object.compile
> (/usr/lib/coffee-script/lib/coffee-script/coffee-script.js:47:32)
> at /usr/lib/coffee-script/lib/coffee-script/command.js:182:33
> at /usr/lib/coffee-script/lib/coffee-script/command.js:152:18
> at [object Object]. (fs.js:123:5)
> at [object Object].emit (events.js:64:17)
> at Object.oncomplete (fs.js:1190:12)
> make: *** [build/node-underscore.logger] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/underscore.logger_0.3.0~2014-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 0.3.0~2014-1+rm
Dear submitter,
as the package underscore.logger has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/857565
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#817397: marked as done (cl-postoffice: Removal of debhelper compat 4)
Your message dated Mon, 13 Mar 2017 15:08:41 + with message-id and subject line Bug#857570: Removed package(s) from unstable has caused the Debian Bug report #817397, regarding cl-postoffice: Removal of debhelper compat 4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 817397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cl-postoffice Severity: important Usertags: compat-4-removal Hi, The package cl-postoffice uses debhelper with a compat level of 4, which is deprecated and scheduled for removal. * Please bump the debhelper compat at your earliest convenience. on the 15th of June. - Compat 9 is recommended - Compat 5 is the bare minimum - If the package has been relying on dh_install being lenient about missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1]. * Compat level 4 will be removed on the first debhelper upload after the 15th of June. Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2015/09/msg00257.html --- End Message --- --- Begin Message --- Version: 1.8.2.3-4+rm Dear submitter, as the package cl-postoffice has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/857570 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#817400: marked as done (cl-salza: Removal of debhelper compat 4)
Your message dated Mon, 13 Mar 2017 15:09:17 + with message-id and subject line Bug#857571: Removed package(s) from unstable has caused the Debian Bug report #817400, regarding cl-salza: Removal of debhelper compat 4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 817400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cl-salza Severity: important Usertags: compat-4-removal Hi, The package cl-salza uses debhelper with a compat level of 4, which is deprecated and scheduled for removal. * Please bump the debhelper compat at your earliest convenience. on the 15th of June. - Compat 9 is recommended - Compat 5 is the bare minimum - If the package has been relying on dh_install being lenient about missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1]. * Compat level 4 will be removed on the first debhelper upload after the 15th of June. Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2015/09/msg00257.html --- End Message --- --- Begin Message --- Version: 0.7.4-1+rm Dear submitter, as the package cl-salza has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/857571 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#817366: marked as done (athcool: Removal of debhelper compat 4)
Your message dated Mon, 13 Mar 2017 15:09:56 + with message-id and subject line Bug#857572: Removed package(s) from unstable has caused the Debian Bug report #817366, regarding athcool: Removal of debhelper compat 4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 817366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: athcool Severity: important Usertags: compat-4-removal Hi, The package athcool uses debhelper with a compat level of 4, which is deprecated and scheduled for removal. * Please bump the debhelper compat at your earliest convenience. on the 15th of June. - Compat 9 is recommended - Compat 5 is the bare minimum - If the package has been relying on dh_install being lenient about missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1]. * Compat level 4 will be removed on the first debhelper upload after the 15th of June. Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2015/09/msg00257.html --- End Message --- --- Begin Message --- Version: 0.3.12-3+rm Dear submitter, as the package athcool has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/857572 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#817314: marked as done (bsign: Mandatory debian/compat for debhelper)
Your message dated Mon, 13 Mar 2017 15:10:45 + with message-id and subject line Bug#857626: Removed package(s) from unstable has caused the Debian Bug report #817314, regarding bsign: Mandatory debian/compat for debhelper to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 817314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bsign Severity: important Usertags: mandatory-debian-compat Hi, The package bsign uses debhelper but does not have a debian/compat file. * Please add a debian/compat file at your earliest convenience. * This will become mandatory in the first debhelper upload after 15th of April. If your package is *also* affected by any of the following debhelper related deprecations, please consider fixing them at the same time: * debhelper compat 4 is deprecated and is expected to be removed on the 15th of June. - Compat 9 is recommended - Compat 5 is the bare minimum - If the package has been relying on dh_install being lenient about missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1]. Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2015/09/msg00257.html --- End Message --- --- Begin Message --- Version: 0.4.5+rm Dear submitter, as the package bsign has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/857626 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#800288: marked as done (bsign: Please migrate a supported debhelper compat level)
Your message dated Mon, 13 Mar 2017 15:10:45 + with message-id and subject line Bug#857626: Removed package(s) from unstable has caused the Debian Bug report #800288, regarding bsign: Please migrate a supported debhelper compat level to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 800288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bsign Severity: important Usertags: deprecated-debhelper-compat-leq-3 Hi, The package bsign is using a debhelper compat level of 3 or less according to lintian. These compat levels have been deprecated for the past ~10 years and debhelper will remove support for them in the near future (as declared in [1]). * Please migrate the package to a supported debhelper compat level. - Compat 9 is recommended - Compat 5 is the bare minimum (compat 4 will be removed soon as well) * If your package uses any of the following tools, please remove them from the rules files. Neither of them does anything except warn about their deprecation. - dh_desktop - dh_scrollkeeper (deadline: January 1st 2016) - dh_suidregister - dh_undocumented * Please note that your package might have been flagged for using e.g. "DH_COMPAT=2 dh_foo ...". - This will still cause issues when the compat level is removed. * If the package has been relying on dh_install being lenient about missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1]. * Deadline: - compat 1+2: November 1st 2015 - compat 3: January 1st 2016 If you are using other deprecated debhelper features (such as omitting the debian/compat file), please consider fixing those while you are at it. Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2015/09/msg00257.html --- End Message --- --- Begin Message --- Version: 0.4.5+rm Dear submitter, as the package bsign has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/857626 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#850507: golang-github-tideland-golib: FTBFS randomly (failing tests)
found 850507 4.20.0-2 thanks Hello Jordi. As you have already noticed, this still fails in (most of the) reproducible builds autobuilers: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-tideland-golib.html To double-check, I've built this a lot of times in my own autobuilders. The result: Tried 200 times. Failed 98 times. I've put all (both failed and successful) my build logs here for you to see: https://people.debian.org/~sanvila/build-logs/golang-github-tideland-golib/ Note 1: It did never fail in two of my autobuilders, leaseweb1 and leaseweb2. Those happens to be the slowest machines I have currently (all the others are faster). Maybe this means something. Note 2: If it becomes non-trivial to fix the tests "the right way" I would suggest that they are just temporarily disabled for stretch. Thanks.
Processed: golang-github-tideland-golib: FTBFS randomly (failing tests)
Processing commands for cont...@bugs.debian.org:
> found 850507 4.20.0-2
Bug #850507 {Done: Jordi Mallach }
[src:golang-github-tideland-golib] golang-github-tideland-golib: FTBFS randomly
(failing tests)
Marked as found in versions golang-github-tideland-golib/4.20.0-2; no longer
marked as fixed in versions golang-github-tideland-golib/4.20.0-2 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
850507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#857642: putty: CVE-2017-6542: integer overflow permits memory overwrite by forwarded ssh-agent connections
Source: putty Version: 0.63-10 Severity: grave Tags: security upstream patch Justification: user security hole Hi, the following vulnerability was published for putty. CVE-2017-6542[0]: |integer overflow permits memory overwrite by forwarded ssh-agent |connections If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-6542 [1] http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/vuln-agent-fwd-overflow.html [2] https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=4ff22863d895cb7ebfced4cf923a012a614adaa8 Regards, Salvatore
Bug#856526: Problem with SAUCE in stretch
Thanks for this QA work. I am travelling right now and am not in a position to fix this now, but I will do so very soon. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
Processed: forcibly merging 850719 850863
Processing commands for cont...@bugs.debian.org: > forcemerge 850719 850863 Bug #850719 [src:node-rollup] FTBFS: uses npm to download from the network during the build Bug #850863 [src:node-rollup] node-rollup: FTBFS due to missing build-dependency on npm Severity set to 'normal' from 'serious' Bug #850719 [src:node-rollup] FTBFS: uses npm to download from the network during the build Marked as found in versions node-rollup/0.38.0-1. Merged 850719 850863 > thanks Stopping processing here. Please contact me if you need assistance. -- 850719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850719 850863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 850719 is serious
Processing commands for cont...@bugs.debian.org: > severity 850719 serious Bug #850719 [src:node-rollup] FTBFS: uses npm to download from the network during the build Bug #850863 [src:node-rollup] node-rollup: FTBFS due to missing build-dependency on npm Severity set to 'serious' from 'normal' Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 850719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850719 850863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#856904: ksirk FTBFS on architectures where char is unsigned
¡Hola John! El 2017-03-13 a las 12:40 +0100, John Paul Adrian Glaubitz escribió: Hi! On 03/06/2017 10:49 AM, John Paul Adrian Glaubitz wrote: The attached debdiff contains a trivial patch which changes the declaration of tbl[] from "char" to "signed char". With the patch applied, I verified that the package builds successfully on armhf. Any progress on this? Not really. Shall I go ahead and perform an NMU? Sure. Thanks a lot for working on this. Happy hacking, -- "C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do it blows your whole leg off." -- Bjarne Stroustrup Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature
Bug#855869: marked as done (dsniff: segfaults on portmapper messages)
Your message dated Mon, 13 Mar 2017 18:18:36 +
with message-id
and subject line Bug#855869: fixed in dsniff 2.4b1+debian-24
has caused the Debian Bug report #855869,
regarding dsniff: segfaults on portmapper messages
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
855869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dsniff
Version: 2.4b1+debian-23
Severity: important
Hi,
dsniff segfaults when receiving any RPC portmapper messages.
To generate such messages, I used:
rpcinfo -l 100021 4
But I expect any rpcinfo -l command will cause this to happen.
> Program received signal SIGSEGV, Segmentation fault.
> __memmove_sse2_unaligned_erms () at
> ../sysdeps/x86_64/multiarch/../multiarch/memmove-vec-unaligned-erms.S:294
> 294
> ../sysdeps/x86_64/multiarch/../multiarch/memmove-vec-unaligned-erms.S: No
> such file or directory.
> (gdb) bt full
> #0 __memmove_sse2_unaligned_erms () at
> ../sysdeps/x86_64/multiarch/../multiarch/memmove-vec-unaligned-erms.S:294
> No locals.
> #1 0x7655ce24 in _IO_new_file_xsputn (f=0x7fffe0f0,
> data=0x55797bd4, n=140737326206416) at fileops.c:1327
> s = 0x55797bd4 ""
> to_do = 140737326206416
> n = 140737326206416
> data = 0x55797bd4
> f = 0x7fffe0f0
> s = 0x55797bd4 ""
> to_do = 140737326206416
> #2 0x983e in rpc_decode (buf=buf@entry=0x55797bd0 "6]T\275",
> len=88, len@entry=92, msg=msg@entry=0x7fffe1c0) at ./rpc.c:129
> xdrs = {x_op = (unknown: 4136102144), x_ops = 0x7687f440
> <_IO_file_jumps>, x_public = 0x768835a3 <_IO_2_1_stderr_+131> "\n",
> x_private = 0x7655bb32
> "H\205\300H\211\305\017\267\273\200", x_base = 0x2525252525252525 Cannot access memory at address 0x2525252525252525>, x_handy = 1}
> fraghdr =
> p = 0x55797bd4 ""
> tmp =
> stat = 0
> tmplen =
> #3 0xec71 in decode_portmap (buf=0x55797bd0 "6]T\275",
> len=92, obuf=, olen=) at ./decode_portmap.c:35
> xdrs = {x_op = (unknown: 4294959712), x_ops = 0x7fffe1a0,
> x_public = 0x6f0063 ,
> x_private = 0x6f ,
> x_base = 0x555617df "portmap", x_handy = 1}
> msg = {rm_xid = 0, rm_direction = CALL, ru = {RM_cmb = {cb_rpcvers =
> 0, cb_prog = 0, cb_vers = 0, cb_proc = 0, cb_cred = {oa_flavor = 0, oa_base =
> 0x0, oa_length = 0}, cb_verf = {oa_flavor = 0,
> oa_base = 0x0, oa_length = 0}}, RM_rmb = {rp_stat =
> MSG_ACCEPTED, ru = {RP_ar = {ar_verf = {oa_flavor = 0, oa_base = 0x0,
> oa_length = 0}, ar_stat = SUCCESS, ru = {AR_versions = {low = 0,
> high = 0}, AR_results = {where = 0x0, proc = 0x0}}},
> RP_dr = {rj_stat = RPC_MISMATCH, ru = {RJ_versions = {low = 0, high = 0},
> RJ_why = AUTH_OK}}
> pm =
> pmap = {pm_prog = 93824994606032, pm_vers = 140737326678332, pm_prot
> = 64, pm_port = 206158430232}
> xm =
> hdrlen =
> #4 0xa524 in trigger_tcp_half (addr=addr@entry=0x77fa0010,
> hs=hs@entry=0x77fa0088, t=0x5577f470 ) at
> ./trigger.c:377
> buf = 0x55797bd0 "6]T\275"
> len = 92
> #5 0xafaa in trigger_tcp (ts=0x77fa0010,
> conn_save=) at ./trigger.c:430
> tr =
> #6 0x777a7f68 in process_tcp () from /usr/lib/libnids.so.1.21
> No symbol table info available.
> #7 0x777a5f35 in ?? () from /usr/lib/libnids.so.1.21
> No symbol table info available.
> #8 0x777a60ae in ?? () from /usr/lib/libnids.so.1.21
> No symbol table info available.
> #9 0x777a621b in nids_pcap_handler () from /usr/lib/libnids.so.1.21
> No symbol table info available.
> #10 0x77565646 in ?? () from /usr/lib/x86_64-linux-gnu/libpcap.so.0.8
> No symbol table info available.
> #11 0x775662d7 in ?? () from /usr/lib/x86_64-linux-gnu/libpcap.so.0.8
> No symbol table info available.
> #12 0x7756e26d in pcap_loop () from
> /usr/lib/x86_64-linux-gnu/libpcap.so.0.8
> No symbol table info available.
> #13 0x777a58f6 in nids_run () from /usr/lib/libnids.so.1.21
> No symbol table info available.
> #14 0x6dc3 in main (argc=, argv=)
> at ./dsniff.c:269
> services = 0x55561958 "/usr/share/dsniff/dsniff.services"
> savefile = 0x0
> triggers = 0x0
> c =
A few things I notice looking at rpc_decode...
> int
> rpc_decode(u_char *buf, int len, struct rpc_msg
Bug#857651: Multiple security issues
Source: audiofile Severity: grave Tags: security Hi, please see these security tracker entries for details, which have all the links to the reports, github issues and patches: https://security-tracker.debian.org/tracker/CVE-2017-6829 https://security-tracker.debian.org/tracker/CVE-2017-6831 https://security-tracker.debian.org/tracker/CVE-2017-6832 https://security-tracker.debian.org/tracker/CVE-2017-6833 https://security-tracker.debian.org/tracker/CVE-2017-6834 https://security-tracker.debian.org/tracker/CVE-2017-6835 https://security-tracker.debian.org/tracker/CVE-2017-6836 https://security-tracker.debian.org/tracker/CVE-2017-6837 https://security-tracker.debian.org/tracker/CVE-2017-6838 https://security-tracker.debian.org/tracker/CVE-2017-6839 Cheers, Moritz
Processed: found 857651 in 0.3.6-1
Processing commands for cont...@bugs.debian.org: > found 857651 0.3.6-1 Bug #857651 [src:audiofile] Multiple security issues Marked as found in versions audiofile/0.3.6-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 857651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#856869: clang-3.9: broken symlink: /usr/bin/scan-build-3.9-py -> ../share/clang/scan-build-3.9/bin/scan-build-py
Followup-For: Bug #856869 Hi Sylvestre, this issue also shows up in clang-4.0 and clang-5.0. Do you prefer separate bug reports for them or does the fix "automatically" flow to the newer versions? e.g. 0m46.8s ERROR: FAIL: Broken symlinks: /usr/bin/scan-build-5.0-py -> ../share/clang/scan-build-5.0/bin/scan-build-py Andreas
Bug#856489: NEWS.Debian.gz is your friend
I'm unable to reproduce the bug. Upon upgrade you should have seen the NEWS via apt-listchanges. You're right as far as README.Debian is concerned. IMO it might be adjusted like this: --- a/README.Debian 2017-01-07 17:36:04.0 +0100 +++ b/README.Debian 2017-03-13 20:14:53.818759251 +0100 @@ -33,7 +33,8 @@ Users may also need to move the socket into a directory accessible by the Postfix chroot; this can be accomplished by setting the SOCKET variable -in /etc/default/opendmarc. +in /etc/systemd/system/opendmarc.service.d/overrride.conf (if systemd is used) +or in /etc/default/opendmarc (if SysV is used). The default is to connect to the filter over TCP. The filter can be bound to localhost to prevent other hosts from accessing it. For example, to bind to Wolfgang signature.asc Description: PGP signature
Bug#857653: liblld-4.0: missing liblld-4.0.so.1
Package: liblld-4.0 Version: missing liblld-4.0.so.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m24.5s ERROR: FAIL: Broken symlinks: /usr/lib/llvm-4.0/lib/liblld.so.1 -> ../../x86_64-linux-gnu/liblld-4.0.so.1 /usr/lib/x86_64-linux-gnu/liblld-4.0.so -> liblld-4.0.so.1 /usr/lib/python2.7/dist-packages/lld-4.0/_lld.so -> ../../../x86_64-linux-gnu/liblld-4.0.so liblld-4.0.so.1 does not seem to exist anywhere, I could only find /usr/lib/llvm-4.0/lib/liblld.so.1 liblld-5.0 has the same problems. cheers, Andreas liblld-4.0_1:4.0-1.log.gz Description: application/gzip
Bug#857657: pybit-client: broken symlinks: /var/lib/pybit-client.d/*.py -> /usr/share/pyshared/pybitclient/*.py
Package: pybit-client Version: 1.0.0-2.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m36.3s ERROR: FAIL: Broken symlinks: /var/lib/pybit-client.d/git.py -> /usr/share/pyshared/pybitclient/git.py /var/lib/pybit-client.d/apt.py -> /usr/share/pyshared/pybitclient/apt.py /var/lib/pybit-client.d/subversion.py -> /usr/share/pyshared/pybitclient/subversion.py /var/lib/pybit-client.d/debianclient.py -> /usr/share/pyshared/pybitclient/debianclient.py These files are now found in /usr/lib/python2.7/dist-packages/pybitclient/ cheers, Andreas pybit-client_1.0.0-2.1.log.gz Description: application/gzip
Bug#844939: git-remote-hg: FTBFS: Test failures
Hi, On Wed, 11 Jan 2017 00:35:19 + Jonathan McCrohan wrote: Unfortunately upstream [1] [2] is not responsive at the moment. I have noticed another fork [3] which is in significantly better shape when using Mercurial 4.0 (only two tests failing), but this has diverged significantly from the original upstream. As a result, it is not possible to cherry-pick a patch or two which would resolve this issue. Assistance from someone with knowledge of both Git and Mercurial internals would be gratefully accepted. Regards, Jon [1] https://github.com/felipec/git-remote-hg/ [2] https://github.com/fingolfin/git-remote-hg/ [3] https://github.com/mnauw/git-remote-hg/ I am the maintainer/writer of the fork [3] mentioned above, which has indeed evolved quite somewhat from the original upstream to address quite some issues. More relevant here; I have re-run the tests (of [3]) against (local checkout of) Mercurial 4.0 and Mercurial 4.1 and all tests pass in my setup (not counting harmless known breakages) (?). So is there any more info on the failing ones that would allow resolving things to a clean test sheet? Also, the compatibility adjustment to Mercurial 4.0 is fairly minor (afaics only 1 commit involving a few lines), so if really desired/preferred that could probably be back-ported to the original upstream. Though again, as said, there are quite some limitations and issues in the original that have been handled in the fork (somewhat regrettably so that way given the circumstances). Regards, Mark
Bug#856869: clang-3.9: broken symlink: /usr/bin/scan-build-3.9-py -> ../share/clang/scan-build-3.9/bin/scan-build-py
Le 13/03/2017 à 20:22, Andreas Beckmann a écrit : > Followup-For: Bug #856869 > > Hi Sylvestre, > > this issue also shows up in clang-4.0 and clang-5.0. Do you prefer > separate bug reports for them or does the fix "automatically" flow to > the newer versions? > > e.g. > > 0m46.8s ERROR: FAIL: Broken symlinks: > /usr/bin/scan-build-5.0-py -> > ../share/clang/scan-build-5.0/bin/scan-build-py > This is already fixed in the svn, thanks for asking :)
Processed: Re: Bug#856805: gstreamer1.0-crystalhd: libgstbcmdec.so not found by gstreamer
Processing control commands: > severity -1 serious Bug #856805 [gstreamer1.0-crystalhd] gstreamer1.0-crystalhd: libgstbcmdec.so not found by gstreamer Severity set to 'serious' from 'important' -- 856805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#856805: marked as done (gstreamer1.0-crystalhd: libgstbcmdec.so not found by gstreamer)
Your message dated Mon, 13 Mar 2017 20:49:02 +
with message-id
and subject line Bug#856805: fixed in crystalhd 1:0.0~git20110715.fdd2f19-12
has caused the Debian Bug report #856805,
regarding gstreamer1.0-crystalhd: libgstbcmdec.so not found by gstreamer
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
856805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gstreamer1.0-crystalhd
Version: 1:0.0~git20110715.fdd2f19-11+b1
Severity: important
Dear Maintainer,
I installed package gstreamer1.0-crystalhd on debian testing, but gst-
inspect-1.0 revealed that the installed /usr/lib/gstreamer-1.0/libgstbcmdec.so
was not being found by gstreamer (and so playback was not using CrystalHD).
When I symlinked this file into directory /usr/lib/x86_64-linux-
gnu/gstreamer-1.0/ (where the other gstreamer plugins live) it started working
and I was able to play back videos using the CrystalHD decoder (as I had
already installed the kernel driver).
With regards,
Luke
-- System Information:
Debian Release: 9.0
APT prefers jessie
APT policy: (500, 'jessie'), (500, 'all'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gstreamer1.0-crystalhd depends on:
ii libc6 2.24-9
ii libcrystalhd3 1:0.0~git20110715.fdd2f19-11+b1
ii libglib2.0-02.50.3-1
ii libgstreamer-plugins-base1.0-0 1.10.3-1
ii libgstreamer1.0-0 1.10.3-1
gstreamer1.0-crystalhd recommends no packages.
gstreamer1.0-crystalhd suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: crystalhd
Source-Version: 1:0.0~git20110715.fdd2f19-12
We believe that the bug you reported is fixed in the latest version of
crystalhd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 856...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher (supplier of updated crystalhd
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 13 Mar 2017 21:33:53 +0100
Source: crystalhd
Binary: libcrystalhd-dev libcrystalhd3 gstreamer1.0-crystalhd
Architecture: source
Version: 1:0.0~git20110715.fdd2f19-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Sebastian Ramacher
Description:
gstreamer1.0-crystalhd - Crystal HD Video Decoder (GStreamer plugin)
libcrystalhd-dev - Crystal HD Video Decoder (development files)
libcrystalhd3 - Crystal HD Video Decoder (shared library)
Closes: 856805
Changes:
crystalhd (1:0.0~git20110715.fdd2f19-12) unstable; urgency=medium
.
* Team upload.
* debian/{rules,gstreamer1.0-crystalhd.install}: Move gstreamer plugin to
multiarch location (Closes: #856805)
Checksums-Sha1:
e5f6db170ed58ab381e6c03cbbd93beb46d83e1f 2356
crystalhd_0.0~git20110715.fdd2f19-12.dsc
ed1aadfc0e1625808adcfd6d5f216a4c60d37ba7 15260
crystalhd_0.0~git20110715.fdd2f19-12.debian.tar.xz
9384ba03c7e3a74dd56e354a0e78a8744d57c185 6973
crystalhd_0.0~git20110715.fdd2f19-12_amd64.buildinfo
Checksums-Sha256:
24d2413fe865d91f54366f906f04ebaa8cb9a2c28b3359a83f3754581474f621 2356
crystalhd_0.0~git20110715.fdd2f19-12.dsc
b634af1ff394c6e5e29e7e6b27648d35f58e475ed1749eeaf3dc80ca15a1 15260
crystalhd_0.0~git20110715.fdd2f19-12.debian.tar.xz
b069729687622e77f6ed8d74602556e0b2eb5e9e5d5bd28fd91de6155c4b0a92 6973
crystalhd_0.0~git20110715.fdd2f19-12_amd64.buildinfo
Files:
62e59ce848d37d74d6591af0212165ca 2356 libs optional
crystalhd_0.0~git20110715.fdd2f19-12.dsc
d9227e0bb3304b8d42650b76bb7f395c 15260 libs optional
crystalhd_0.0~git20110715.fdd2f19-12.debian.tar.xz
89980bf2a4592117a2cb479f3e357225 6973 libs optional
crystalhd_0.0~git20110715.fdd2f19-12_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAljHAuEACgkQafL8UW6n
GZPz0hAAwG/Js5Gn+KTr5/zWkxUdijPks4WVztcPh4WYoMaTxX
Bug#854000: marked as done (CVE-2017-5834 CVE-2017-5835 CVE-2017-5836)
Your message dated Mon, 13 Mar 2017 20:50:39 + with message-id and subject line Bug#854000: fixed in libplist 1.12+git+1+e37ca00-0.1 has caused the Debian Bug report #854000, regarding CVE-2017-5834 CVE-2017-5835 CVE-2017-5836 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 854000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libplist Severity: grave Tags: security CVE-2017-5834: heap-buffer-overflow in parse_dict_node https://github.com/libimobiledevice/libplist/issues/89 CVE-2017-5835: memory allocation error https://github.com/libimobiledevice/libplist/issues/88 CVE-2017-5836 issue in plist_free_data plist.c:185 https://github.com/libimobiledevice/libplist/issues/86 --- End Message --- --- Begin Message --- Source: libplist Source-Version: 1.12+git+1+e37ca00-0.1 We believe that the bug you reported is fixed in the latest version of libplist, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 854...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated libplist package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 26 Feb 2017 19:21:32 +0100 Source: libplist Binary: libplist3 libplist++3v5 libplist-dev libplist++-dev libplist-dbg python-plist libplist-utils libplist-doc Architecture: source Version: 1.12+git+1+e37ca00-0.1 Distribution: unstable Urgency: medium Maintainer: gtkpod Maintainers Changed-By: Hilko Bengen Description: libplist++-dev - Library for handling Apple binary and XML property lists libplist++3v5 - Library for handling Apple binary and XML property lists libplist-dbg - Library for handling Apple binary and XML property lists libplist-dev - Library for handling Apple binary and XML property lists libplist-doc - Library for handling Apple binary and XML property lists - docs libplist-utils - Apple property list converter libplist3 - Library for handling Apple binary and XML property lists python-plist - Library for handling Apple binary and XML property lists Closes: 851196 852385 854000 Changes: libplist (1.12+git+1+e37ca00-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream snapshot; tarball was generated from https://github.com/libimobiledevice/libplist/archive/e37ca0090343e0dae97e967d467bab56d502c37a.tar.gz - Fixes CVE-2017-5834, CVE-2017-5835, CVE-2017-5836 (Closes: #854000) - Fixes CVE-2017-5209 (Closes: #851196) - Fixes CVE-2017-5545 (Closes: #852385) * Update symbols file * Rebase patch * Add dh_python build-dependency Checksums-Sha1: cd9460ba56cce47f585819989f8af1e1d68ca63d 2582 libplist_1.12+git+1+e37ca00-0.1.dsc 479a1576ed9af72e8ed7e23959da866735caf0b2 160736 libplist_1.12+git+1+e37ca00.orig.tar.gz 9d15aa370ef1950183930131eca350b412f7a076 9540 libplist_1.12+git+1+e37ca00-0.1.debian.tar.xz 7af788c5ebd113b74c9ed65638922e786f8d5515 5041 libplist_1.12+git+1+e37ca00-0.1_source.buildinfo Checksums-Sha256: 2b08d2fb9d84b8b331ce86a557ece4d3cdf37f96d8831980b582e7efc4fa64cb 2582 libplist_1.12+git+1+e37ca00-0.1.dsc 676f970b325b6bee68648551c066260bed99aa510f620f9488dbe060d4244695 160736 libplist_1.12+git+1+e37ca00.orig.tar.gz c72458e91e68f4e6e1fc1b3914ec458b27be7be63f3e01200bb3037b9946ef9e 9540 libplist_1.12+git+1+e37ca00-0.1.debian.tar.xz aa657d0e31852664b49b8433d00420ccc5821ab396547ba8ba2eea2d4da69564 5041 libplist_1.12+git+1+e37ca00-0.1_source.buildinfo Files: 203022c0681f892b2a9c1a900d748add 2582 libs optional libplist_1.12+git+1+e37ca00-0.1.dsc 7715473abb463eba9687b0c024933df2 160736 libs optional libplist_1.12+git+1+e37ca00.orig.tar.gz 0f74556aeb109479135ca4947952cb53 9540 libs optional libplist_1.12+git+1+e37ca00-0.1.debian.tar.xz cdb47a514a5ca814e4bfd2e06dc4285b 5041 libs optional libplist_1.12+git+1+e37ca00-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlizKDUACgkQdbcQY1wh On7How//WRMwMFH9zTvpTatjiXAU444BPbHwWcSffVIX2ghGTjHIMkYI/zXCQl/5 aMzPgWrfVdbvzD0l9KFVWFelLR5lBHOz3DAZOExe6YtZzbiXNR3ju5545IpT+s8i HpBxO5lWv7ilIy8o3s/Zksq0eONzU
Bug#852385: marked as done (libplist: CVE-2017-5545)
Your message dated Mon, 13 Mar 2017 20:50:38 + with message-id and subject line Bug#852385: fixed in libplist 1.12+git+1+e37ca00-0.1 has caused the Debian Bug report #852385, regarding libplist: CVE-2017-5545 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 852385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libplist Version: 1.11-3 Severity: important Tags: upstream patch security fixed-upstream Forwarded: https://github.com/libimobiledevice/libplist/issues/87 Hi, the following vulnerability was published for libplist. CVE-2017-5545[0]: | The main function in plistutil.c in libimobiledevice libplist through | 1.12 allows attackers to obtain sensitive information from process | memory or cause a denial of service (buffer over-read) via Apple | Property List data that is too short. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-5545 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5545 [1] https://github.com/libimobiledevice/libplist/issues/87 Regards, Salvatore --- End Message --- --- Begin Message --- Source: libplist Source-Version: 1.12+git+1+e37ca00-0.1 We believe that the bug you reported is fixed in the latest version of libplist, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 852...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated libplist package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 26 Feb 2017 19:21:32 +0100 Source: libplist Binary: libplist3 libplist++3v5 libplist-dev libplist++-dev libplist-dbg python-plist libplist-utils libplist-doc Architecture: source Version: 1.12+git+1+e37ca00-0.1 Distribution: unstable Urgency: medium Maintainer: gtkpod Maintainers Changed-By: Hilko Bengen Description: libplist++-dev - Library for handling Apple binary and XML property lists libplist++3v5 - Library for handling Apple binary and XML property lists libplist-dbg - Library for handling Apple binary and XML property lists libplist-dev - Library for handling Apple binary and XML property lists libplist-doc - Library for handling Apple binary and XML property lists - docs libplist-utils - Apple property list converter libplist3 - Library for handling Apple binary and XML property lists python-plist - Library for handling Apple binary and XML property lists Closes: 851196 852385 854000 Changes: libplist (1.12+git+1+e37ca00-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream snapshot; tarball was generated from https://github.com/libimobiledevice/libplist/archive/e37ca0090343e0dae97e967d467bab56d502c37a.tar.gz - Fixes CVE-2017-5834, CVE-2017-5835, CVE-2017-5836 (Closes: #854000) - Fixes CVE-2017-5209 (Closes: #851196) - Fixes CVE-2017-5545 (Closes: #852385) * Update symbols file * Rebase patch * Add dh_python build-dependency Checksums-Sha1: cd9460ba56cce47f585819989f8af1e1d68ca63d 2582 libplist_1.12+git+1+e37ca00-0.1.dsc 479a1576ed9af72e8ed7e23959da866735caf0b2 160736 libplist_1.12+git+1+e37ca00.orig.tar.gz 9d15aa370ef1950183930131eca350b412f7a076 9540 libplist_1.12+git+1+e37ca00-0.1.debian.tar.xz 7af788c5ebd113b74c9ed65638922e786f8d5515 5041 libplist_1.12+git+1+e37ca00-0.1_source.buildinfo Checksums-Sha256: 2b08d2fb9d84b8b331ce86a557ece4d3cdf37f96d8831980b582e7efc4fa64cb 2582 libplist_1.12+git+1+e37ca00-0.1.dsc 676f970b325b6bee68648551c066260bed99aa510f620f9488dbe060d4244695 160736 libplist_1.12+git+1+e37ca00.orig.tar.gz c72458e91e68f4e6e1fc1b3914ec458b27be7be63f3e01200bb3037b9946ef9e 9540 libplist_1.12+git+1+e37ca00-0.1.debian.tar.xz aa657d0e31852664b49b8433d00420ccc5821ab396547ba8ba2eea2d4da69564 5041 libplist_1.12+git+1+e37ca00-0.1_source.buildinfo Files: 203022c0681f892b2a9c1a900d748add 2582 libs optional libplist_1.12+git+1+e37ca00-0.1.dsc 7715473abb463eba9687b0c024933df2 160736 libs optional libplist_1.1
Bug#851196: marked as done (libplist: CVE-2017-5209)
Your message dated Mon, 13 Mar 2017 20:50:38 + with message-id and subject line Bug#851196: fixed in libplist 1.12+git+1+e37ca00-0.1 has caused the Debian Bug report #851196, regarding libplist: CVE-2017-5209 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 851196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libplist Version: 1.12-3.1 Severity: important Tags: security upstream patch Forwarded: https://github.com/libimobiledevice/libplist/issues/84 Hi, the following vulnerability was published for libplist. CVE-2017-5209[0]: | The base64decode function in base64.c in libimobiledevice libplist | through 1.12 allows attackers to obtain sensitive information from | process memory or cause a denial of service (buffer over-read) via | split encoded Apple Property List data. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-5209 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5209 [1] https://github.com/libimobiledevice/libplist/issues/84 [2] https://github.com/libimobiledevice/libplist/commit/3a55ddd3c4c11ce75a86afbefd085d8d397ff957 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: libplist Source-Version: 1.12+git+1+e37ca00-0.1 We believe that the bug you reported is fixed in the latest version of libplist, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 851...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated libplist package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 26 Feb 2017 19:21:32 +0100 Source: libplist Binary: libplist3 libplist++3v5 libplist-dev libplist++-dev libplist-dbg python-plist libplist-utils libplist-doc Architecture: source Version: 1.12+git+1+e37ca00-0.1 Distribution: unstable Urgency: medium Maintainer: gtkpod Maintainers Changed-By: Hilko Bengen Description: libplist++-dev - Library for handling Apple binary and XML property lists libplist++3v5 - Library for handling Apple binary and XML property lists libplist-dbg - Library for handling Apple binary and XML property lists libplist-dev - Library for handling Apple binary and XML property lists libplist-doc - Library for handling Apple binary and XML property lists - docs libplist-utils - Apple property list converter libplist3 - Library for handling Apple binary and XML property lists python-plist - Library for handling Apple binary and XML property lists Closes: 851196 852385 854000 Changes: libplist (1.12+git+1+e37ca00-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream snapshot; tarball was generated from https://github.com/libimobiledevice/libplist/archive/e37ca0090343e0dae97e967d467bab56d502c37a.tar.gz - Fixes CVE-2017-5834, CVE-2017-5835, CVE-2017-5836 (Closes: #854000) - Fixes CVE-2017-5209 (Closes: #851196) - Fixes CVE-2017-5545 (Closes: #852385) * Update symbols file * Rebase patch * Add dh_python build-dependency Checksums-Sha1: cd9460ba56cce47f585819989f8af1e1d68ca63d 2582 libplist_1.12+git+1+e37ca00-0.1.dsc 479a1576ed9af72e8ed7e23959da866735caf0b2 160736 libplist_1.12+git+1+e37ca00.orig.tar.gz 9d15aa370ef1950183930131eca350b412f7a076 9540 libplist_1.12+git+1+e37ca00-0.1.debian.tar.xz 7af788c5ebd113b74c9ed65638922e786f8d5515 5041 libplist_1.12+git+1+e37ca00-0.1_source.buildinfo Checksums-Sha256: 2b08d2fb9d84b8b331ce86a557ece4d3cdf37f96d8831980b582e7efc4fa64cb 2582 libplist_1.12+git+1+e37ca00-0.1.dsc 676f970b325b6bee68648551c066260bed99aa510f620f9488dbe060d4244695 160736 libplist_1.12+git+1+e37ca00.orig.tar.gz c72458e91e68f4e6e1fc1b3914ec458b27be7be63f3e01200bb3037b9946ef9e 9540 libplist_1.12+git+1+e37ca00-0.1.debian.tar.xz aa657d0e31852664b49b8433d00420ccc5821ab396547ba8ba2eea2d4da69564 5041 libplist_1.12+git+1+e37ca00-0.1_source.buildinfo Files: 203022c0681f
Bug#857682: vlc-plugin-vlsub: unusable - needs to move to /usr/share/vlc/lua/extensions
Package: vlc-plugin-vlsub Version: 0.9.13-1 Severity: grave Justification: renders package unusable /usr/lib/vlc/lua/extensions is no longer on the Lua script search path, so the script included in vlc-plugin-vlsub will not be loaded. It should move to /usr/share/vlc/lua/extensions instead. Also, since vlc itself now included the vlsub plugin, maybe this package should simply be removed. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: Re: liblldb-3.8-dev: broken symlinks: /usr/lib/llvm-3.8/lib/liblldb*.so
Processing control commands:
> clone -1 -2
Bug #856864 {Done: Sylvestre Ledru } [liblldb-3.8-dev]
liblldb-3.8-dev: broken symlinks: /usr/lib/llvm-3.8/lib/liblldb*.so
Bug 856864 cloned as bug 857683
> reassign -2 liblldb-3.9-dev
Bug #857683 {Done: Sylvestre Ledru } [liblldb-3.8-dev]
liblldb-3.8-dev: broken symlinks: /usr/lib/llvm-3.8/lib/liblldb*.so
Bug reassigned from package 'liblldb-3.8-dev' to 'liblldb-3.9-dev'.
No longer marked as found in versions llvm-toolchain-3.8/1:3.8.1-17.
No longer marked as fixed in versions llvm-toolchain-3.8/1:3.8.1-18.
> found -2 1:3.9.1-4
Bug #857683 {Done: Sylvestre Ledru } [liblldb-3.9-dev]
liblldb-3.8-dev: broken symlinks: /usr/lib/llvm-3.8/lib/liblldb*.so
Marked as found in versions llvm-toolchain-3.9/1:3.9.1-4 and reopened.
> retitle -2 liblldb-3.9-dev: broken symlinks: /usr/lib/llvm-3.9/lib/liblldb*.so
Bug #857683 [liblldb-3.9-dev] liblldb-3.8-dev: broken symlinks:
/usr/lib/llvm-3.8/lib/liblldb*.so
Changed Bug title to 'liblldb-3.9-dev: broken symlinks:
/usr/lib/llvm-3.9/lib/liblldb*.so' from 'liblldb-3.8-dev: broken symlinks:
/usr/lib/llvm-3.8/lib/liblldb*.so'.
--
856864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856864
857683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#850464: nfs-blkmap.service fails to start at boot
On Sat, Mar 11, 2017 at 08:15:02PM +0100, Andreas Henriksson wrote: > Could you please test editing nfs-blkmap.service on your system > and replace: > PIDFile=/var/run/blkmapd.pid > with: > PIDFile=/run/blkmapd.pid > .. and report back if that solves the issue or not? Yes, this fixes the issue. BTW, I am not sure who else to ask about this, but https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539201 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738063 are somewhat related. There are a lot of problems with the systemd migration, and none of them are getting fixed. They're mostly related to nfs-common being disabled in systemd, and partly due to stuff missing in /etc/init.d/nfs-kernel-server If a user is expecting any of the following (due to their old configuration in /etc/default): enable nfs v2 disable nfs v3 disable nfs v4 statd idmapd blkmap etc. their system will be utterly broken, since each has to be manually enabled via systemctl enable, and/or both /etc/default/nfs-kernel-server and /etc/init.d/nfs-kernel-server have to be patched. In short, nfs-kernel-server is broken with systemd and nobody seems to be addressing any of the issues. I think there needs to a be a single unifying bug that summarizes all of the current systemd/nfs issues so they can be addressed in a coherent, multilateral manner. Thanks for your time and attention, hopefully someone can take over the mess... MRV Communications is a global supplier of packet and optical solutions that power the world’s largest networks. Our products combine innovative hardware with intelligent software to make networks smarter, faster and more efficient.
Bug#856864: liblldb-3.8-dev: broken symlinks: /usr/lib/llvm-3.8/lib/liblldb*.so
Followup-For: Bug #856864
Control: clone -1 -2
Control: reassign -2 liblldb-3.9-dev
Control: found -2 1:3.9.1-4
Control: retitle -2 liblldb-3.9-dev: broken symlinks:
/usr/lib/llvm-3.9/lib/liblldb*.so
Hi,
this issue also shows up in liblldb-{3.9,4.0,5.0}-dev. Sorry for missing
this earlier.
0m35.9s ERROR: FAIL: Broken symlinks:
/usr/lib/llvm-3.9/lib/liblldb.so -> liblldb-3.9.so
/usr/lib/llvm-3.9/lib/liblldb-3.9.so -> liblldb-3.9.so.1
/usr/lib/llvm-3.9/lib/liblldb-3.9.1.so -> liblldb-3.9.so
0m31.2s ERROR: FAIL: Broken symlinks:
/usr/lib/llvm-4.0/lib/liblldb.so -> liblldb-4.0.so
/usr/lib/llvm-4.0/lib/liblldb-4.0.so -> liblldb-4.0.so.1
/usr/lib/llvm-4.0/lib/liblldb-4.0.0.so -> liblldb-4.0.so
0m39.9s ERROR: FAIL: Broken symlinks:
/usr/lib/llvm-5.0/lib/liblldb.so -> liblldb-5.0.so
/usr/lib/llvm-5.0/lib/liblldb-5.0.so -> liblldb-5.0.so.1
/usr/lib/llvm-5.0/lib/liblldb-5.0.0.so -> liblldb-5.0.so
Andreas
liblldb-3.9-dev_1:3.9.1-5.log.gz
Description: application/gzip
Bug#856904: marked as done (ksirk FTBFS on architectures where char is unsigned)
Your message dated Mon, 13 Mar 2017 21:48:55 +
with message-id
and subject line Bug#856904: fixed in ksirk 4:16.04.0-1.1
has caused the Debian Bug report #856904,
regarding ksirk FTBFS on architectures where char is unsigned
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
856904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ksirk
Version: 4:16.04.0-1
Severity: serious
https://buildd.debian.org/status/package.php?p=ksirk&suite=sid
...
/«PKGBUILDDIR»/ksirk/iris/src/xmpp/base64/base64.cpp:65:2: error: narrowing
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
/«PKGBUILDDIR»/ksirk/iris/src/xmpp/base64/base64.cpp:65:2: error: narrowing
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
/«PKGBUILDDIR»/ksirk/iris/src/xmpp/base64/base64.cpp:65:2: error: narrowing
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
/«PKGBUILDDIR»/ksirk/iris/src/xmpp/base64/base64.cpp:65:2: error: narrowing
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
/«PKGBUILDDIR»/ksirk/iris/src/xmpp/base64/base64.cpp:65:2: error: narrowing
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
/«PKGBUILDDIR»/ksirk/iris/src/xmpp/base64/base64.cpp:65:2: error: narrowing
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
/«PKGBUILDDIR»/ksirk/iris/src/xmpp/base64/base64.cpp:65:2: error: narrowing
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
/«PKGBUILDDIR»/ksirk/iris/src/xmpp/base64/base64.cpp:65:2: error: narrowing
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
/«PKGBUILDDIR»/ksirk/iris/src/xmpp/base64/base64.cpp:65:2: error: narrowing
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
/«PKGBUILDDIR»/ksirk/iris/src/xmpp/base64/base64.cpp:65:2: error: narrowing
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
/«PKGBUILDDIR»/ksirk/iris/src/xmpp/base64/base64.cpp:65:2: error: narrowing
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
/«PKGBUILDDIR»/ksirk/iris/src/xmpp/base64/base64.cpp:65:2: error: narrowing
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
...
--- End Message ---
--- Begin Message ---
Source: ksirk
Source-Version: 4:16.04.0-1.1
We believe that the bug you reported is fixed in the latest version of
ksirk, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 856...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz (supplier of updated
ksirk package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 06 Mar 2017 10:44:11 +0100
Source: ksirk
Binary: ksirk
Architecture: source amd64
Version: 4:16.04.0-1.1
Distribution: sid
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers
Changed-By: John Paul Adrian Glaubitz
Description:
ksirk - Risk strategy game
Closes: 856904
Changes:
ksirk (4:16.04.0-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add patch: fix-signage-of-tbl-array.diff to fix FTBFS on
architectures where 'char' is unsigned. (Closes: #856904)
Checksums-Sha1:
2c98b6a2f18f692b2ef90e64627492cb21e37e2b 2338 ksirk_16.04.0-1.1.dsc
780c16cae5fcd0c2be66474bcf6ff9f843915b17 8696 ksirk_16.04.0-1.1.debian.tar.xz
793ec04f57491cbaee6c470776deb63055ae548e 13018756
ksirk-dbgsym_16.04.0-1.1_amd64.deb
dcf846e66bbe2715aa7e2b8dd684a90e4f13e0bc 11877
ksirk_16.04.0-1.1_amd64.buildinfo
797e93c84f16afd9c12342e06dc563f5eede4a43 3190498 ksirk_16.04.0-1.1_amd64.deb
Checksums-Sha256:
4a9be6ded2fc6175a432e9e41ea88aef444735ebce2c643b3f02bf7ef2ea18c7 2338
ksirk_16.04.0-1.1.dsc
5d71ed46c6d32522d3e0036d1cddf9e493b195e0f43f929381393e53e4d1ecac 8696
ksirk_16.04.0-1.1.debian.tar.xz
5782fe673bec7e3ae750aa86651a45f1a35920b13033df78efdc976b386d8d5d 13018756
ksirk-dbgsym_16.04.0-1.1_amd64.deb
8b286cf1f4196e0878b3f7b02fe000753d4dcc9e361c3bd312d112cb5ecc7627 11877
ksirk_16.04.0-1.1_amd64.buildinfo
1a659789f40c712cd484e4c99f2b5c31eb79e3e9d27c1b091396202d8465c08a 3190498
ksirk_16.04.0-1.1_amd64.deb
Files:
572a544935991db
Bug#788769: marked as done (entangle: FTBFS without networking: relax-ng: failed to load external entity [..] mallard-1.0.rng)
Hi Michael, On Fri, Mar 10, 2017 at 07:26:58PM +0100, Michael Biebl wrote: > On Sun, 26 Feb 2017 17:00:22 +0100 Florian Schlichting > > Given that it's too late now to get a mallard-rng package into Stretch, > > I suggest to ship the mallard-1.0.rng file as part of the yelp-tools > > package for now (e.g. as /usr/share/yelp-tools/mallard/mallard-1.0.rng) > > and simply use that as relaxng schema in yelp-check: > > Let's go with this approach for stretch and see if we can improve the > situation in buster. > > Florian, can you send us a complete debdiff, which includes the > installation of the mallard-rng schema, changelog entry etc. please find attached the source diff, with which I built the package for testing and from which I'd build the NMU. Feel free to massage the changelog to your liking, or any other part of the patch, really. Florian >From 68378f6d7a412db85e6e5839812301b3ba136c54 Mon Sep 17 00:00:00 2001 From: Florian Schlichting Date: Mon, 13 Mar 2017 22:27:33 +0100 Subject: [PATCH] Ship a copy of mallard-1.0.rng and use that in yelp-check instead of downloading the same file every time. Closes: #788769 --- debian/changelog |8 + debian/mallard-1.0.rng | 2158 debian/patches/local-mallard-rng.patch | 60 + debian/patches/series |1 + debian/yelp-tools.install |1 + 5 files changed, 2228 insertions(+) create mode 100644 debian/mallard-1.0.rng create mode 100644 debian/patches/local-mallard-rng.patch create mode 100644 debian/patches/series create mode 100644 debian/yelp-tools.install diff --git a/debian/changelog b/debian/changelog index 209a0c0..b348298 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +yelp-tools (3.18.0-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Ship a copy of mallard-1.0.rng and use that in yelp-check instead of +downloading the same file every time. Closes: #788769 + + -- Florian Schlichting Sun, 26 Feb 2017 16:30:17 +0100 + yelp-tools (3.18.0-2) unstable; urgency=medium * Convert from cdbs to dh. diff --git a/debian/mallard-1.0.rng b/debian/mallard-1.0.rng new file mode 100644 index 000..81a26c8 --- /dev/null +++ b/debian/mallard-1.0.rng @@ -0,0 +1,2158 @@ + +http://relaxng.org/ns/structure/1.0"; +xmlns:mal="http://projectmallard.org/1.0/"; +ns="http://projectmallard.org/1.0/";> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + http://www.w3.org/2001/XMLSchema-datatypes"/> + + + +http://www.w3.org/2001/XMLSchema-datatypes"/> + + + + +http://www.w3.org/2001/XMLSchema-datatypes"/> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + http://www.w3.org/2001/XMLSchema-datatypes"/> + + + +http://www.w3.org/2001/XMLSchema-datatypes"/> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +http://www.w3.org/2001/XMLSchema-datatypes"/> + + + + +http://www.w3.org/2001/XMLSchema-datatypes"/> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + http://www.w3.org/2001/XMLSchema-datatypes"/> + + + +http://www.w3.org/2001/XMLSchema-datatypes"/> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + http://www.w3.org/2001/XMLSchema-datatypes"/> + + + +http://www.w3.org/2001/XMLSchema-datatypes"/> + + + + +http://www.w3.org/2001/XMLSchema-datatypes"/> + + + + + + + + + + + + + + + + + + + + + + + + + +http://www.w3.org/2001/XMLSchema-datatypes"/> + + + + + + + + + + + + + + + + + + + + + + + + + + + + +http://www.w3.org/2001/XMLSchema-datatypes"/> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +http://www.w3.org/2001/XMLSchema-datatypes"/> + + + + + + + + + + + + + + + + + + +
Processed: 857604 notfound in mpi4py/2.0.0-2.1
Processing commands for cont...@bugs.debian.org:
> notfound 857604 mpi4py/2.0.0-2.1
Bug #857604 {Done: Niels Thykier } [src:mpi4py] mpi4py:
FTBFS (Exception: MPI_ERR_WIN: invalid window)
No longer marked as found in versions mpi4py/2.0.0-2.1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
857604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#857327: libapache2-authenntlm-perl: does not work with Apache 2.4
On 11/03/17 02:46, gregor herrmann wrote: From reading the above URLs, it seems that remote_addr -> client_addr remote_ip -> client_ip should do the trick. Could you maybe try this proposed fix? If it works, we can prepare an updated package for stretch. I tried that, and it's better - no problems on the Apache side at least. I think it's outdated on the NTLM side, as Edge on Windows 10 was not able to authenticate to it. But the basic authentication fallback works at least, as I was able to authenticate that way from cURL. Given that this package has been broken for years without anyone noticing perhaps it should be removed instead? thanks, Hamish
Bug#848220: gcc-5 should not ship in stretch
On Thu, Dec 15, 2016 at 10:35:16AM +0100, Matthias Klose wrote: > remaining issues: > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=gcc-5-legacy;users=debian-...@lists.debian.org All the actionable ones are done (apart from llvm-toolchain-snapshot, which doesn't seem to explictly be using any fixed version of gcc to me). > gcc-5-cross and gcc-5-cross-ports should be removed from testing at the same > time. llvm-toolchain-snapshot is only in unstable. #835940 is asking for gcc-5 > to stay in unstable, which should be fine. According to `dak rm -Rn gcc-5 gnat-5 gcc-5-cross gcc-5-cross-ports` nothing (build-)depends on them anymore¹. Do you think it can be removed from unstable too now, or does it have a particular purpose? ¹ except petsc on kfreebsd/hurd, which can be ignored if unfixed -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#843038: marked as done (FTBFS test failures on slow CPUs (test timeout))
Your message dated Tue, 14 Mar 2017 00:33:39 +
with message-id
and subject line Bug#843038: fixed in elki 0.7.1-3
has caused the Debian Bug report #843038,
regarding FTBFS test failures on slow CPUs (test timeout)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
843038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:elki
Version: 0.7.1-2
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
[...]
debian/rules build-indep
dh build-indep --buildsystem=maven
dh_testdir -i -O--buildsystem=maven
dh_update_autotools_config -i -O--buildsystem=maven
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
# Remove unneded executable bits:
find elki addons data -type f -executable -exec chmod -x {} \+
dh_auto_configure -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No
such file or directory
mh_patchpoms -pelki --debian-build --keep-pom-version
--maven-repo=/<>/debian/maven-repo
[... snipped ...]
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec - in
de.lmu.ifi.dbs.elki.evaluation.scores.ROCEvaluationTest
Running de.lmu.ifi.dbs.elki.evaluation.scores.AveragePrecisionEvaluationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in
de.lmu.ifi.dbs.elki.evaluation.scores.AveragePrecisionEvaluationTest
Running de.lmu.ifi.dbs.elki.evaluation.scores.MaximumF1EvaluationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in
de.lmu.ifi.dbs.elki.evaluation.scores.MaximumF1EvaluationTest
Running de.lmu.ifi.dbs.elki.evaluation.paircounting.ClusterContingencyTableTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec - in
de.lmu.ifi.dbs.elki.evaluation.paircounting.ClusterContingencyTableTest
Results :
Tests in error:
IntegerArrayQuickSortTest.testSorted:130 TestTimedOut test timed out after
500...
Tests run: 348, Failures: 0, Errors: 1, Skipped: 1
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] ELKI Data Mining Framework - Parent Project SUCCESS [ 0.389 s]
[INFO] ELKI Data Mining Framework . FAILURE [02:01 min]
[INFO] ELKI Data Mining Framework - Batik Visualization ... SKIPPED
[INFO] ELKI Data Mining Framework - Tutorial Algorithms ... SKIPPED
[INFO] ELKI Data Mining Framework - LibSVM based extensions SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 02:02 min
[INFO] Finished at: 2016-11-02T00:48:31+01:00
[INFO] Final Memory: 14M/36M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on
project elki: There are test failures.
[ERROR]
[ERROR] Please refer to /<>/elki/target/surefire-reports for the
individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :elki
dh_auto_test: /usr/lib/jvm/java-8-openjdk-amd64/bin/java -noverify -cp
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar
-Dmaven.home=/usr/share/maven
-Dmaven.multiModuleProjectDirectory=/<>
-Dclassworlds.conf=/etc/maven/m2-debian.conf
-Dproperties.file.manual=/<>/debian/maven.properties
org.codehaus.plexus.classworlds.launcher.Launcher
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1
deb
Bug#788769: marked as done (yelp-check validate fails without networking: relax-ng: failed to load external entity [..] mallard-1.0.rng)
Your message dated Tue, 14 Mar 2017 00:50:21 + with message-id and subject line Bug#788769: fixed in yelp-tools 3.18.0-3 has caused the Debian Bug report #788769, regarding yelp-check validate fails without networking: relax-ng: failed to load external entity [..] mallard-1.0.rng to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 788769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: entangle Version: 0.7.0-3 Severity: important Dear Maintainer, The package fails to build in a mean pbuilder that denies networking: yelp-check validate ./C error : connection refused warning: failed to load external entity "http://projectmallard.org/1.0/mallard-1.0.rng"; error : connection refused warning: failed to load external entity "http://projectmallard.org/1.0/mallard-1.0.rng"; Relax-NG parser error : grammar has no children Relax-NG parser error : Element has no Relax-NG schema /tmp/yelp-HSdh66vS/1.0.rng failed to compile [...] The full build log can be seen on the mean Reproducible Builds builder: https://reproducible.debian.net/rb-pkg/unstable/amd64/entangle.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-20-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: yelp-tools Source-Version: 3.18.0-3 We believe that the bug you reported is fixed in the latest version of yelp-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 788...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl (supplier of updated yelp-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 14 Mar 2017 01:25:55 +0100 Source: yelp-tools Binary: yelp-tools Architecture: source Version: 3.18.0-3 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Michael Biebl Description: yelp-tools - Yelp documentation tools Closes: 788769 Changes: yelp-tools (3.18.0-3) unstable; urgency=medium . [ Florian Schlichting ] * Ship a copy of mallard-1.0.rng and use that in yelp-check instead of downloading the same file every time. (Closes: #788769) Checksums-Sha1: 09e5482eb1dfcfaf409b74fa1b34127a45a5e95d 2146 yelp-tools_3.18.0-3.dsc fe04f85c11e30b28de672f0a573859fa8df9a7f6 6660 yelp-tools_3.18.0-3.debian.tar.xz 5773d842a1bd2a34d7a511eaa77def89dec83066 5738 yelp-tools_3.18.0-3_source.buildinfo Checksums-Sha256: 82e0c71dfb52be2dcd1d948f10056fdcf46ea911c1c947bf25aa251a6e5cd531 2146 yelp-tools_3.18.0-3.dsc 193b33f0105de986274c293a84ca1073a2618697017cd97e996f6ee2b1c10808 6660 yelp-tools_3.18.0-3.debian.tar.xz 5ec0c22afb93ea8e7ddc1b9f10950f7c50a94dbd15cca9d561a85db9e91cb5c2 5738 yelp-tools_3.18.0-3_source.buildinfo Files: 34957f58a29a09002f7555158554e35e 2146 gnome extra yelp-tools_3.18.0-3.dsc dfa76b55ea2eae9aaa94f7919a391e0e 6660 gnome extra yelp-tools_3.18.0-3.debian.tar.xz c12121e1dbb7e17432df7baa4d72d5fa 5738 gnome extra yelp-tools_3.18.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEECbOsLssWnJBDRcxUauHfDWCPItwFAljHOM4RHGJpZWJsQGRl Ymlhbi5vcmcACgkQauHfDWCPItzXOA/+LSwfQoJXE7SoI3JYh14ERja1qk9v7ImF TIdj3nM0h7lS4iy0+P65CDMqb4dypn85CPRND8ozGxULG2u5evo/Snd7VBCl6lvB XVYYh9GTFhLGGifGC0hgXmrQWbwjRhl9t+9BuTLtTjiSBlqMxS6taUVawVL2hNW0 TJOhaeiZbh/37xTiEYJQJjKTcA8gwYHjrCBEYHSE7rUmpJGrTeAecnQUX935UZH9 Npq8E1DwH0zHX0YPlMKx/csZ7jJBL+JPdzteUU6obPml1eKUuC8FbjzOSdrHb2v/ RRHh4N2zoM7B2Hx7W+jPViu87nOM9n84czpvaqf4dN/pFasFUc8+6/Prgztv2CeB m7Ipql0EyVPYMlPfNKn9Y+SVTEY6K/VSZl+g2WY4upFvj9A/0FBXJ0IPyT6SVm6/ 2NvA650BW+8oU5UVqkNO/3jYLvHygO91UXz0vSarxuEKa7LoS7ZOPRSUE+aq8QP+ pZ7I1D/PgqzrYexs3Nh/31wDY5VFghEf7B+FHaLcoKaSAK1NK4m0pYBDLoorohYe 3xJASn8LY/KlId+77JtPzh/IOtx9slqiJFPqZkKbo6LeZfp1lrIMJA1T0LzYbZt7 WC4bBGS0FEMRBPjQrVOj0L+BCchJq8GnGCdZ2qNt+ThXu6lgXGHWdL2p6J5vq/HL Vg3zEeLDPa0= =smuH -END PGP SIGNATURE E
Bug#856488: opendmarc: does not honor Socket config key anymore
On Wed, 01 Mar 2017 15:49:41 +0100 Dominik George wrote: > Package: opendmarc > Version: 1.3.2~Beta1-2 > Severity: grave > Justification: renders package unusable > > At some point, OpenDMARC stopped honouring the Socket option in its > config file. This results in 127.0.0.1:12302 never being bound with the > configuration file attached. It works for me if the interface is up and bound to the address. Scott K
Bug#857473: [Pkg-roundcube-maintainers] Bug#857473: roundcube: XSS issue in handling of a style tag inside of an svg element
Control: tag -1 pending Hi, On Sat, 11 Mar 2017 at 20:29:11 +0100, Salvatore Bonaccorso wrote: > 1.2.4 roundcube release fixed a XSS issue in handling of a style tag > inside of an svg element. Thanks for the ping and the pointers! I applied the fix to 1.2.3 (unstable) and 1.1.5 (jessie-backports). Could someone else in the team upload the two source packages? I don't have upload privileges :-P (Also I didn't tag the releases.) Cheers, -- Guilhem. signature.asc Description: PGP signature
Processed: Re: [Pkg-roundcube-maintainers] Bug#857473: roundcube: XSS issue in handling of a style tag inside of an svg element
Processing control commands: > tag -1 pending Bug #857473 [src:roundcube] roundcube: CVE-2017-6820: XSS issue in handling of a style tag inside of an svg element Added tag(s) pending. -- 857473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#857699: ioquake3 has a security vulnerability
Package: ioquake3 Version: 1.36 Severity: grave Hi, earlier today ioquake3 fixed a vulnerability that, as far as I understand, could let malicious multiplayer servers execute code on connecting clients. It affects all prior versions of ioquake3 (and I think also original Quake 3). Details: https://ioquake3.org/2017/03/13/important-security-update-please-update-ioquake3-immediately/ So you should probably update to latest ioq3 git or backport the fix. Cheers, Daniel
Processed: fixed 857426 in 8:6.8.9.9-5+deb8u8
Processing commands for cont...@bugs.debian.org:
> fixed 857426 8:6.8.9.9-5+deb8u8
Bug #857426 {Done: Bastien ROUCARIES }
[src:imagemagick] [Bug 1671630] Memory leak in IsOptionMember function
The source 'imagemagick' and version '8:6.8.9.9-5+deb8u8' do not appear to
match any binary packages
Marked as fixed in versions imagemagick/8:6.8.9.9-5+deb8u8.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
857426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: needrestart-session: doesn't show the same results as needrestart
Processing control commands: > severity -1 serious Bug #787291 [needrestart-session] needrestart-session: doesn't show the same results as needrestart Severity set to 'serious' from 'important' -- 787291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#857426: closed by Bastien ROUCARIES (does not affect sid,)
Hello Bastien, On Sat, Mar 11, 2017 at 03:18:04PM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the src:imagemagick package: > > #857426: [Bug 1671630] Memory leak in IsOptionMember function > > It has been closed by Bastien ROUCARIES . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Bastien ROUCARIES > by > replying to this email. > > > -- > 857426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857426 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > Date: Sat, 11 Mar 2017 16:15:15 +0100 > From: Bastien ROUCARIES > To: 857426-d...@bugs.debian.org > Subject: does not affect sid, > Message-ID: > > > version: 8:6.9.7.4+dfsg-2 Hmm, I do not see that change from 8:6.9.7.4+dfsg-1 to 8:6.9.7.4+dfsg-2. Are you sure that is the fixing version and not already done somewhere earlier? Regards, Salvatore
Processed: fixed 857426 in 8:6.9.2.10+dfsg-1
Processing commands for cont...@bugs.debian.org:
> fixed 857426 8:6.9.2.10+dfsg-1
Bug #857426 {Done: Bastien ROUCARIES }
[src:imagemagick] [Bug 1671630] Memory leak in IsOptionMember function
Marked as fixed in versions imagemagick/8:6.9.2.10+dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
857426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: fixed 857426 in 8:6.9.6.2+dfsg-2
Processing commands for cont...@bugs.debian.org:
> fixed 857426 8:6.9.6.2+dfsg-2
Bug #857426 {Done: Bastien ROUCARIES }
[src:imagemagick] [Bug 1671630] Memory leak in IsOptionMember function
Marked as fixed in versions imagemagick/8:6.9.6.2+dfsg-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
857426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#857426: closed by Bastien ROUCARIES (does not affect sid,)
Hi, On Tue, Mar 14, 2017 at 07:23:25AM +0100, Salvatore Bonaccorso wrote: > Hello Bastien, > > On Sat, Mar 11, 2017 at 03:18:04PM +, Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > > which was filed against the src:imagemagick package: > > > > #857426: [Bug 1671630] Memory leak in IsOptionMember function > > > > It has been closed by Bastien ROUCARIES . > > > > Their explanation is attached below along with your original report. > > If this explanation is unsatisfactory and you have not received a > > better one in a separate message then please contact Bastien ROUCARIES > > by > > replying to this email. > > > > > > -- > > 857426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857426 > > Debian Bug Tracking System > > Contact ow...@bugs.debian.org with problems > > > Date: Sat, 11 Mar 2017 16:15:15 +0100 > > From: Bastien ROUCARIES > > To: 857426-d...@bugs.debian.org > > Subject: does not affect sid, > > Message-ID: > > > > > > version: 8:6.9.7.4+dfsg-2 > > Hmm, I do not see that change from 8:6.9.7.4+dfsg-1 to > 8:6.9.7.4+dfsg-2. Are you sure that is the fixing version and not > already done somewhere earlier? Okay, the first version uploaded to unstable containing the fix is probably 8:6.9.6.2+dfsg-2. Regards, Salvatore
Bug#857473: [Pkg-roundcube-maintainers] Bug#857473: roundcube: XSS issue in handling of a style tag inside of an svg element
❦ 14 mars 2017 04:16 +0100, Guilhem Moulin : >> 1.2.4 roundcube release fixed a XSS issue in handling of a style tag >> inside of an svg element. > > Thanks for the ping and the pointers! I applied the fix to 1.2.3 > (unstable) and 1.1.5 (jessie-backports). > > Could someone else in the team upload the two source packages? I don't > have upload privileges :-P (Also I didn't tag the releases.) Both of them uploaded. -- Program defensively. - The Elements of Programming Style (Kernighan & Plauger) signature.asc Description: PGP signature
