Bug#828299: fetchmail: FTBFS with openssl 1.1.0
Hello Kurt Roeckx. On Sun, Jun 26, 2016 at 12:21:39PM +0200, Kurt Roeckx wrote: > Source: fetchmail > Version: 6.3.26-2 > Severity: important > Control: block 827061 by -1 > > Hi, > > OpenSSL 1.1.0 is about to released. [...] > https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/fetchmail_6.3.26-2_amd64-20160529-1418 [...] The failure in this build log didn't look like it was really openssl related. I've tried rebuilding the package which succeded for me. Could you please double-check here and possibly close this bug report if there's no issue? Regards, Andreas Henriksson
Processed: tagging 842811, tagging 842812, tagging 842814
Processing commands for cont...@bugs.debian.org: > tags 842811 + pending Bug #842811 [src:memcached] memcached: CVE-2016-8704 Added tag(s) pending. > tags 842812 + pending Bug #842812 [src:memcached] memcached: CVE-2016-8705 Added tag(s) pending. > tags 842814 + pending Bug #842814 [src:memcached] memcached: CVE-2016-8706 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 842811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842811 842812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842812 842814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843012: libcsp: CVE-2016-8596 CVE-2016-8597 CVE-2016-8598
Source: libcsp Version: 1.4+fdd49b7+dfsg-3 Severity: grave Tags: security upstream patch Hi, the following vulnerabilities were published for libcsp. CVE-2016-8596[0]: | Buffer overflow in the csp_can_process_frame in csp_if_can.c in the | libcsp library v1.4 and earlier allows hostile components connected to | the canbus to execute arbitrary code via a long csp packet. CVE-2016-8597[1]: | Buffer overflow in the csp_sfp_recv_fp in csp_sfp.c in the libcsp | library v1.4 and earlier allows hostile components with network access | to the SFP underlying network layers to execute arbitrary code via | specially crafted SFP packets. CVE-2016-8598[2]: | Buffer overflow in the zmq interface in csp_if_zmqhub.c in the libcsp | library v1.4 and earlier allows hostile computers connected via a zmq | interface to execute arbitrary code via a long packet. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2016-8596 [1] https://security-tracker.debian.org/tracker/CVE-2016-8597 [2] https://security-tracker.debian.org/tracker/CVE-2016-8598 Regards, Salvatore
Bug#842939: WOT found guilty to sell user data
I've had a look at the source and I can confirm the tracking code is present in
debian.
Please read this blog post first:
https://www.kuketz-blog.de/wot-addon-wie-ein-browser-addon-seine-nutzer-ausspaeht/
(German)
https://translate.google.com/translate?hl=en&sl=auto&tl=en&u=https%3A%2F%2Fwww.kuketz-blog.de%2Fwot-addon-wie-ein-browser-addon-seine-nutzer-ausspaeht%2F
(English)
It's worth a read, the tl;dr is: the author discovered the addon is
sending your browser history together with a unique identifier to mywot
servers. The author then setup a virtual machine with linux, firefox and
no addons besides WOT. Later, the canary dataset was found inside the
data dump that was acquired by the NDR.
This is the version >= stretch:
There's an event handler for `onLocationChange` that is passing the tab
location to `wot_stats.loc`:
```
if (tabUrl && wot_stats.isWebURL(tabUrl)) {
var ref = browser.contentDocument.referrer;
if (request && request.referrer &&
typeof(request.referrer) != undefined) {
ref = request.referrer.asciiSpec;
}
wot_stats.loc(tabUrl, ref);
}
```
https://sources.debian.net/src/wot/20151208-2/content/core.js/#L81
`wot_stats.loc` is then calling `wot_stats.query`, which is sending the
data to a server (https://secure.mywot.com at the point of writing. The
endpoint is remotely configurable, I'll cover that later). I've marked
the comments that are added by myself.
```
data = {
"s":WOT_STATS.SID,
"md":21,
"pid":wot_stats.getUserId(),
"sess":wot_stats.getSession()['id'],
"q":encodeURIComponent(url), //(kpcyrd): this is the current url
"prev":encodeURIComponent(wot_stats.last_prev), //(kpcyrd): this is
the previously seen url
"link":0,
"sub": "ff",
"tmv": WOT_STATS.VER,
"hreferer" : encodeURIComponent(ref), //(kpcyrd): this seems to be
a referer, but I didn't investigate further
"ts" : wot_stats.utils.getCurrentTime()
};
var requestDataInfo = this.utils.serialize(data);
var requestData = requestDataInfo.data;
var requestLength = requestDataInfo.length;
var encoded = btoa(btoa(requestData)); //(kpcyrd): base64 encode twice
if (encoded != "") {
var data = "e=" + encodeURIComponent(encoded);
var statsUrl = settings[this.urlKey] + "/valid"; //(kpcyrd): get
the endpoint from the config
this.utils.postRequest(statsUrl, data, requestLength); //(kpcyrd):
send data to the server, there's a unique identifier in the cookies
}
this.last_prev = url; //(kpcyrd): set the current url as previous url
for the next request
```
https://sources.debian.net/src/wot/20151208-2/content/stats.js/#L280
After decoding the base64, the resulting request looks like this:
https://media.kuketz.de/blog/artikel/2016/wot-addon/unmaskiert2.jpg
As far as I can tell, this is happening for every page load.
The endpoint for that data is dynamic, it's fetched from
https://secure.mywot.com/config when you provide the correct parameters:
```
$ curl 'https://secure.mywot.com/config?s=241&ins=1478145149&ver=1.0'
{"ok":1,"url":"https://secure.mywot.com"}
```
Not sure why it's working like this, I assume it's to obfuscate the
endpoint they're sending data to. The code between this fetch and the
usage quoted above is unnecessary complicated. It could also be used to
bypass firewalls trying to block this.
The data that is sent with this tracking script has huge implications on
privacy, but since these are full urls (hostname, path, querystring,
anchor/fragment) this causes significant implications on security,
especially for applications that store sensitive information in query
strings.
I've also had a quick look at the version in jessie and it looks like
it's "only" operating on hostnames, but when you actually look into some
of the util functions, this doesn't seem to be the case.
```
onLocationChange: function(progress, request, location)
{
if (progress.DOMWindow != this.browser.contentWindow) {
return;
}
if (location) {
wot_core.block(this, request, location.spec);
//(kpcyrd): this sends data to the server
}
wot_core.update();
},
```
https://sources.debian.net/src/wot/20131118-1/chrome/wot.jar%21/content/core.js/#L62
```
block: function(pl, request, url)
{
try {
if (!wot_util.isenabled() || !pl || !pl.browser ||
!url) {
return;
}
if (!wot_warning.isblocking())
Bug#828309: getdns: FTBFS with openssl 1.1.0
On Sun, 26 Jun 2016 12:21:45 +0200 Kurt Roeckx wrote: > Source: getdns > Version: 0.9.0-1 > Severity: important > Control: block 827061 by -1 > > Hi, > > OpenSSL 1.1.0 is about to released. During a rebuild of all packages using > OpenSSL this package fail to build. A log of that build can be found at: > https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/getdns_0.9.0-1_amd64-20160530-2108 > > On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the > reasons why it might fail. There are also updated man pages at > https://www.openssl.org/docs/manmaster/ that should contain useful information. > > There is a libssl-dev package available in experimental that contains a recent > snapshot, I suggest you try building against that to see if everything works. > > If you have problems making things work, feel free to contact us. getdns v1.1.0-a2, which was released two weeks ago supports openssl 1.1.0. I haven't tested it yet. Scott K
Bug#842814: memcached: CVE-2016-8706
Hi Guillaume, On Thu, Nov 03, 2016 at 03:17:27AM +0100, Guillaume Delacour wrote: > Please see attached the debdiff. > Also, please note that i can't upload myself to security-master as i'm > not a DD nor DM. I actually did already earlier this week, but I have not released yet the DSA text. Sorry for not notifying the bug. Are you working on an unstable upload? Regards, Salvatore
Processed: Re: xul-ext-wot: WOT find guilty to sell user data
Processing control commands: > severity -1 serious Bug #842939 [xul-ext-wot] xul-ext-wot: WOT find guilty to sell user data Severity set to 'serious' from 'important' -- 842939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843003: fritzing: fails to build on all architectures except i386 and amd64
Package: fritzing Version: 0.9.3b+dfsg-1 Severity: serious debian/patches/system-libgit2.patch is written so that only amd64 and i386 will build. https://buildd.debian.org/status/package.php?p=fritzing libgit2 is available though on every Linux architecture: https://buildd.debian.org/status/package.php?p=libgit2 Thanks, Jeremy Bicha
Processed: block 842812 with 842814
Processing commands for cont...@bugs.debian.org: > block 842812 with 842814 Bug #842812 [src:memcached] memcached: CVE-2016-8705 842812 was not blocked by any bugs. 842812 was not blocking any bugs. Added blocking bug(s) of 842812: 842814 > thanks Stopping processing here. Please contact me if you need assistance. -- 842812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 842811 with 842814
Processing commands for cont...@bugs.debian.org: > block 842811 with 842814 Bug #842811 [src:memcached] memcached: CVE-2016-8704 842811 was not blocked by any bugs. 842811 was not blocking any bugs. Added blocking bug(s) of 842811: 842814 > thanks Stopping processing here. Please contact me if you need assistance. -- 842811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#842811: memcached: CVE-2016-8704
Fix is the same as for #842814. On Tue, 01 Nov 2016 14:00:07 +0100 Salvatore Bonaccorso wrote: > Source: memcached > Version: 1.4.31-1 > Severity: important > Tags: security upstream > > Hi, > > the following vulnerability was published for memcached. > > CVE-2016-8704[0]: > Memcached Server Append/Prepend Remote Code Execution Vulnerability > > 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-2016-8704 > [1] http://www.talosintelligence.com/reports/TALOS-2016-0219/ > > Please adjust the affected versions in the BTS as needed. > > Regards, > Salvatore > > -- Guillaume Delacour signature.asc Description: OpenPGP digital signature
Bug#842812: memcached: CVE-2016-8705
Fix is the same as #842814. On Tue, 01 Nov 2016 14:05:19 +0100 Salvatore Bonaccorso wrote: > Source: memcached > Version: 1.4.31-1 > Severity: important > Tags: security upstream > > Hi, > > the following vulnerability was published for memcached. > > CVE-2016-8705[0]: > Memcached Server Update Remote Code Execution Vulnerability > > It is reproducible with the (fixed) reproducer on the TALOS site, when > running under valgrind easily. > > 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-2016-8705 > [1] http://www.talosintelligence.com/reports/TALOS-2016-0220/ > > Please adjust the affected versions in the BTS as needed. > > Regards, > Salvatore > > -- Guillaume Delacour signature.asc Description: OpenPGP digital signature
Bug#842814: memcached: CVE-2016-8706
Please see attached the debdiff.
Also, please note that i can't upload myself to security-master as i'm
not a DD nor DM.
On Tue, 01 Nov 2016 14:08:44 +0100 Salvatore Bonaccorso
wrote:
> Source: memcached
> Version: 1.4.31-1
> Severity: important
> Tags: security upstream
>
> Hi,
>
> the following vulnerability was published for memcached.
>
> CVE-2016-8706[0]:
> |Memcached Server SASL Autentication Remote Code Execution
> |Vulnerability
>
> It is easily reproducible with the TALOS reproducer when memcached
> enabled SASL authentication and running under valgrind to see the
> crash.
>
> 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-2016-8706
> [1] http://www.talosintelligence.com/reports/TALOS-2016-0221/
>
> Please adjust the affected versions in the BTS as needed.
>
> Regards,
> Salvatore
>
>
--
Guillaume Delacour
diff -Nru memcached-1.4.21/debian/changelog memcached-1.4.21/debian/changelog
--- memcached-1.4.21/debian/changelog 2015-03-07 13:01:25.0 +
+++ memcached-1.4.21/debian/changelog 2016-11-03 02:14:20.0 +
@@ -1,3 +1,12 @@
+memcached (1.4.21-1.1+deb8u1) jessie-security; urgency=high
+
+ * CVE-2016-8704: Fix Append/Prepend Remote Code Execution (Closes: #842811)
+ * CVE-2016-8705: Fix Update Remote Code Execution (Closes: #842812)
+ * CVE-2016-8706: Fix SASL Authentication Remote Code Execution
+(Closes: #842814)
+
+ -- Guillaume Delacour Thu, 03 Nov 2016 02:26:55 +0100
+
memcached (1.4.21-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru memcached-1.4.21/debian/patches/08_CVE-2016-8704_8705_8706.patch
memcached-1.4.21/debian/patches/08_CVE-2016-8704_8705_8706.patch
--- memcached-1.4.21/debian/patches/08_CVE-2016-8704_8705_8706.patch
1970-01-01 00:00:00.0 +
+++ memcached-1.4.21/debian/patches/08_CVE-2016-8704_8705_8706.patch
2016-11-03 01:31:47.0 +
@@ -0,0 +1,50 @@
+From bd578fc34b96abe0f8d99c1409814a09f51ee71c Mon Sep 17 00:00:00 2001
+From: dormando
+Date: Wed, 12 Oct 2016 13:50:47 -0700
+Subject: [PATCH] CVE reported by cisco talos
+Origin: upstream,
+https://github.com/memcached/memcached/commit/bd578fc34b96abe0f8d99c1409814a09f51ee71c
+Last-Update: 2016-11-03
+
+---
+ items.c | 3 +++
+ memcached.c | 10 --
+ 2 files changed, 11 insertions(+), 2 deletions(-)
+
+diff --git a/items.c b/items.c
+index 9e6d921..a1cca4a 100644
+--- a/items.c
b/items.c
+@@ -148,6 +148,9 @@ item *do_item_alloc(char *key, const size_t nkey, const
unsigned int flags,
+ uint8_t nsuffix;
+ item *it = NULL;
+ char suffix[40];
++if (nbytes < 2 || nkey < 0)
++return 0;
++
+ size_t ntotal = item_make_header(nkey + 1, flags, nbytes, suffix,
&nsuffix);
+ if (settings.use_cas) {
+ ntotal += sizeof(uint64_t);
+diff --git a/memcached.c b/memcached.c
+index dc1f636..ad423a0 100644
+--- a/memcached.c
b/memcached.c
+@@ -1997,10 +1997,16 @@ static bool authenticated(conn *c) {
+ static void dispatch_bin_command(conn *c) {
+ int protocol_error = 0;
+
+-int extlen = c->binary_header.request.extlen;
+-int keylen = c->binary_header.request.keylen;
++uint8_t extlen = c->binary_header.request.extlen;
++uint16_t keylen = c->binary_header.request.keylen;
+ uint32_t bodylen = c->binary_header.request.bodylen;
+
++if (keylen > bodylen || keylen + extlen > bodylen) {
++write_bin_error(c, PROTOCOL_BINARY_RESPONSE_UNKNOWN_COMMAND, NULL, 0);
++c->write_and_go = conn_closing;
++return;
++}
++
+ if (settings.sasl && !authenticated(c)) {
+ write_bin_error(c, PROTOCOL_BINARY_RESPONSE_AUTH_ERROR, NULL, 0);
+ c->write_and_go = conn_closing;
diff -Nru memcached-1.4.21/debian/patches/series
memcached-1.4.21/debian/patches/series
--- memcached-1.4.21/debian/patches/series 2015-03-07 13:01:25.0
+
+++ memcached-1.4.21/debian/patches/series 2016-11-03 01:32:38.0
+
@@ -4,3 +4,4 @@
04_add_init_retry.patch
06_eol_comment_handling.patch
07_disable_tests.patch
+08_CVE-2016-8704_8705_8706.patch
signature.asc
Description: OpenPGP digital signature
Bug#828549: SLURM OpenSSL 1.1 issue - Patch to disable OpenSSL support until upstream fixes
Hi Mehdi, That’s awesome! Changing the code is definitely preferable, as long as the code works with older versions of MySQL. To check this, I tried building SLURM in a Jessie COWbuilder installation. In order to test, one dependency had to be changed in the control file: Change “default-libmysqlclient-dev” to “libmysqlclient-dev”. The test took place with OpenSSL 1.0.1 (specifically, OpenSSL source package version 1.0.1t-1+deb8u3). I also tried building for Ubuntu Xenial (again using COWbuilder), which has OpenSSL package version 1.0.2g-1ubuntu4.5. This also required changing the control file, as with Jessie. I did not test in Wheezy, because there are other dependency issues (like a minimum debhelper version) that would need to be changed. I also did not test on Ubuntu Trusty. Both builds were able to complete. You can download the results here: Debian Jessie (16.05.6-2~sbp81+1, for jessie-backports): https://stanford.box.com/s/tehux7vh57w75k9sfjjpt0s0sjiugor1 Ubuntu Xenial (16.05.6-2~sbp16.04+1, for xenial-backports: https://stanford.box.com/s/opnjc8ab5dqzrwwp3qi2rutvfa1mu51l (I’ll keep each links working until the bug is fixed upstream) “sbp” stands for “Stanford Backport”, since this isn’t an official backport. Each .tar.gz has all of the stuff you would need to upload to a repository of your own, so you can either install the .deb files manually, or you could use the .changes file to upload to a repository of your own. The versions are numbered so that when Gennaro releases 16.05.6-2 (or something later), that will take precedence over the ones I built. Unfortunately, I don’t think your patch would be able to work directly, because the quilt build process requires that the original code be untouched; all of the changes to source have to be Quilt patches. So, I’ve taken your patch and converted it into a quilt patch! I’m attaching to this email a Git commit patch that creates the quilt patch, and updates the patch series list. So, here are the next steps that I would suggest: * Mehdi, you should go to https://bugs.schedmd.com, create an account, open bug 3226, and attach your patch (the original one you sent me). I’m asking you to do it because you are the author, so you should get the credit for it. * Anyone who wants to test on Jessie or Xenial can use one of the builds that I made. * In the meantime, if Gennaro decides to go forward with your code, he could use the quilt patch I’ve attached here. Thanks much for the patch! ~ Karl 0001-Add-support-for-OpenSSL-1.1.patch Description: 0001-Add-support-for-OpenSSL-1.1.patch
Bug#828462: marked as done (ocaml-ssl: FTBFS with openssl 1.1.0)
Your message dated Thu, 03 Nov 2016 00:18:57 + with message-id and subject line Bug#828462: fixed in ocaml-ssl 0.5.2-2 has caused the Debian Bug report #828462, regarding ocaml-ssl: FTBFS with openssl 1.1.0 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.) -- 828462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocaml-ssl Version: 0.5.2-1 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/ocaml-ssl_0.5.2-1_amd64-20160529-1458 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- Source: ocaml-ssl Source-Version: 0.5.2-2 We believe that the bug you reported is fixed in the latest version of ocaml-ssl, 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 828...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mehdi Dogguy (supplier of updated ocaml-ssl 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: Thu, 03 Nov 2016 00:49:11 +0100 Source: ocaml-ssl Binary: libssl-ocaml libssl-ocaml-dev Architecture: source amd64 Version: 0.5.2-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Mehdi Dogguy Description: libssl-ocaml - OCaml bindings for OpenSSL (runtime) libssl-ocaml-dev - OCaml bindings for OpenSSL Closes: 828462 Changes: ocaml-ssl (0.5.2-2) unstable; urgency=medium . * Team upload. * Use accessor functions for X509_STORE_CTX (Closes: #828462). - add 0001-Use-accessor-functions-for-X509_STORE_CTX.patch * Bump Standards-Version to 3.9.8, no changes required. * Update Homepage field. * Update Vcs-* fields to use secure and canonical URIs. Checksums-Sha1: 219bb6aff7207bc64b9ec0aea73e89da40e110f0 2142 ocaml-ssl_0.5.2-2.dsc c1349c770ac2674b0c34d458b85c044ab77d02d8 4560 ocaml-ssl_0.5.2-2.debian.tar.xz 058617bcb23610b1aed5ac70adf3e018486a09eb 21680 libssl-ocaml-dbgsym_0.5.2-2_amd64.deb 37de2ccf05c10aafce48d492d58a12b5a29703e3 75982 libssl-ocaml-dev_0.5.2-2_amd64.deb 8bebad854f7c66400fcbb0d42b4e2e9ad84ed76a 15058 libssl-ocaml_0.5.2-2_amd64.deb Checksums-Sha256: 199fde656dbe9871a99d9df1f8c973d56e4dad43bf351c33048d463b153ae4ca 2142 ocaml-ssl_0.5.2-2.dsc d9848f4f698e935e9dea3481cce50431eb9b7076e64d71b68a4f8468e864ebf2 4560 ocaml-ssl_0.5.2-2.debian.tar.xz 90a1d9e5342330b1a0ba387acbdad89388c872ab4ea65b9266d264bf7655c9da 21680 libssl-ocaml-dbgsym_0.5.2-2_amd64.deb 91e15af4d7758fd4fb4e21a6656028b2ba5ce6ea3c30f2086c587d086b77531e 75982 libssl-ocaml-dev_0.5.2-2_amd64.deb 6cecf2be93b5965f758622cdc8fc667014a842c604dc36a11cbf02119b91e4e9 15058 libssl-ocaml_0.5.2-2_amd64.deb Files: 57f73d0e4fcb5e3c1c279222b194f283 2142 ocaml optional ocaml-ssl_0.5.2-2.dsc 68b9e4cba4ea54aabd49fc1cdf0296b4 4560 ocaml optional ocaml-ssl_0.5.2-2.debian.tar.xz 45fb159a5949a10545e24c14a26d11a4 21680 debug extra libssl-ocaml-dbgsym_0.5.2-2_amd64.deb 1239efb59c4a4cf9969bfdb8315e2c4e 75982 ocaml optional libssl-ocaml-dev_0.5.2-2_amd64.deb c006e2a15e3f411dbf2ba75c2423cb22 15058 ocaml optional libssl-ocaml_0.5.2-2_amd64.deb -BEGIN PGP SIGNATURE- iQIuBAEBCAAYBQJYGnwtERxtZWhkaUBkZWJpYW4ub3JnAAoJEDO+GgqMLtj/QW8P /iDuAcCz34sYcxmDzm2MSJKrWWVH6J/XPR6e8br4bUVcElhf/P2mKloeH5w0PUmo FjEZ89nCsZeJLR4xFf7LRVDf2yHeUfrvY2iR8xWQq2Vhvsd5t5zReVtmTM8quHOH 7VkhMFYhJ9xFTDs/3PtL8aKpLqfqZbkzNBICDTsjTMZec50+l1EbrobIK2OxNEsW gNuHBjOdKNsTF+cNQ0aHkq3IbgbXArmne0VTwipttvS8e8ySe6zL3g54govF10sn a2f//Bd9VNEB7ym4w6Yy7ky9cKAWmUASl6RZusGbHCgZ0eKteszFKLyhzlTP47/z 0ZE3m
Bug#837674: parmap: FTBFS with bindnow and PIE enabled
Hi, On 13/09/2016 14:12, Balint Reczey wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64 with patched GCC and dpkg. > > The rebuild tested if packages are ready for a transition > enabling PIE and bindnow for amd64. > FWIW, I've tried to rebuild parmap in a clean Sid chroot and I am unable to reproduce the build failure. You can find attached my build log. Does it still fail for you? Regards, -- Mehdi dpkg-buildpackage: info: source package parmap dpkg-buildpackage: info: source version 1.0~rc7-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Mehdi Dogguy dpkg-source --before-build parmap dpkg-source: info: applying 0001-Update-version-number-in-various-places.patch fakeroot debian/rules clean dh --with ocaml clean dh: Compatibility levels before 9 are deprecated (level 7 in use) dh_testdir dh_auto_clean dh_auto_clean: Compatibility levels before 9 are deprecated (level 7 in use) dh_ocamlclean dh_clean dh_clean: Compatibility levels before 9 are deprecated (level 7 in use) dpkg-source -b parmap dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building parmap using existing ./parmap_1.0~rc7.orig.tar.gz dpkg-source: info: building parmap in parmap_1.0~rc7-1.debian.tar.xz dpkg-source: info: building parmap in parmap_1.0~rc7-1.dsc dpkg-genchanges --build=source >../parmap_1.0~rc7-1_source.changes dpkg-genchanges: info: including full source code in upload dpkg-source --after-build parmap dpkg-source: info: unapplying 0001-Update-version-number-in-various-places.patch dpkg-buildpackage: info: full upload (original source is included) [0mI: Copying COW directory[0m [0mI: forking: rm -rf /var/cache/pbuilder/build/cow.3985[0m [0mI: forking: cp -al /var/cache/pbuilder/cows/unstable-amd64/ /var/cache/pbuilder/build/cow.3985[0m [0mI: unlink for ilistfile /var/cache/pbuilder/build/cow.3985/.ilist failed, it didn't exist?[0m [0mI: forking: chroot /var/cache/pbuilder/build/cow.3985 cowdancer-ilistcreate /.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i ''[0m [0mI: Invoking pbuilder[0m [0mI: forking: pbuilder build --debbuildopts --debbuildopts --buildplace /var/cache/pbuilder/build/cow.3985 --buildresult /var/cache/pbuilder/result/unstable-amd64 --no-targz --internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.3985 cow-shell' /home/mehdi/Debian/pkg-ocaml-maint/parmap_1.0~rc7-1.dsc[0m [0mI: Running in no-targz mode[0m [0mI: using fakeroot in build.[0m [0mI: pbuilder: network access will be disabled during build[0m [0mI: Current time: Thu Nov 3 01:03:38 CET 2016[0m [0mI: pbuilder-time-stamp: 1478131418[0m [0mI: copying local configuration[0m [0mI: mounting /proc filesystem[0m [0mI: mounting /sys filesystem[0m [0mI: mounting /run/shm filesystem[0m [0mI: mounting /dev/pts filesystem[0m [0mI: Mounting /var/cache/pbuilder/result/[0m [0mI: policy-rc.d already exists[0m [0mI: Obtaining the cached apt archive contents[0m [0mI: Installing the build-deps[0m [1;33mW: execute priv not set on file D09custompool, not executing.[0m [0mI: user script /var/cache/pbuilder/build/cow.3985/tmp/hooks/D10aptupdate starting[0m Hit:1 http://debian.univ-lorraine.fr/debian unstable InRelease Reading package lists... [0mI: user script /var/cache/pbuilder/build/cow.3985/tmp/hooks/D10aptupdate finished[0m [0mI: user script /var/cache/pbuilder/build/cow.3985/tmp/hooks/D11unsafeio starting[0m Setting force-unsafe-io for dpkg [0mI: user script /var/cache/pbuilder/build/cow.3985/tmp/hooks/D11unsafeio finished[0m [1;33mW: execute priv not set on file D12aptupgrade, not executing.[0m -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder Team Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: debhelper (>= 7.0.50~), ocaml-nox (>= 3.12.0~), dh-ocaml (>= 0.9~), ocaml-findlib, autoconf dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 11646 files and directories currently installed.) Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ... Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ... dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested: pbuilder-satisfydepends-dummy depends on debhelper (>= 7.0.50~); however: Package debhelper is not installed. pbuilder-satisfydepends-dummy depends on ocaml-nox (>= 3.12.0~); however: Pa
Bug#827541: marked as done (automake-1.15: FTBFS: Test failures in t/check12.sh and t/check12-w.sh)
Your message dated Thu, 03 Nov 2016 00:03:48 + with message-id and subject line Bug#827541: fixed in automake-1.15 1:1.15-5 has caused the Debian Bug report #827541, regarding automake-1.15: FTBFS: Test failures in t/check12.sh and t/check12-w.sh 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.) -- 827541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: automake-1.15 Version: 1:1.15-4 Severity: serious >From my pbuilder build log: ... PASS: t/check-tests-in-builddir.sh PASS: t/colneq.sh PASS: t/check-concurrency-bug9245.sh FAIL: t/check12.sh PASS: t/colon4.sh PASS: t/colneq2.sh PASS: t/colneq3.sh ... PASS: t/missing3-w.sh PASS: t/mkinst3-w.sh PASS: t/check7-w.sh FAIL: t/check12-w.sh PASS: t/missing-version-mismatch-w.sh PASS: t/exeext4-w.sh PASS: t/color-tests2-w.sh ... Testsuite summary for GNU Automake 1.15 # TOTAL: 2953 # PASS: 2880 # SKIP: 28 # XFAIL: 43 # FAIL: 2 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to bug-autom...@gnu.org Makefile:3026: recipe for target 'test-suite.log' failed make[3]: *** [test-suite.log] Error 1 make[3]: Leaving directory '/build/automake-1.15-1.15' Makefile:3132: recipe for target 'check-TESTS' failed make[2]: *** [check-TESTS] Error 2 make[2]: Leaving directory '/build/automake-1.15-1.15' Makefile:3366: recipe for target 'check-am' failed make[1]: *** [check-am] Error 2 make[1]: Leaving directory '/build/automake-1.15-1.15' dh_auto_test: make -j8 check VERBOSE=1 returned exit code 2 debian/rules:8: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 (reproducible.debian.net is also seeing the same failure - see https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/automake-1.15_1.15-4.rbuild.log .) -- Daniel Schepler --- End Message --- --- Begin Message --- Source: automake-1.15 Source-Version: 1:1.15-5 We believe that the bug you reported is fixed in the latest version of automake-1.15, 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 827...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Eric Dorland (supplier of updated automake-1.15 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, 01 Nov 2016 19:33:03 -0400 Source: automake-1.15 Binary: automake Architecture: source all Version: 1:1.15-5 Distribution: unstable Urgency: medium Maintainer: Eric Dorland Changed-By: Eric Dorland Description: automake - Tool for generating GNU Standards-compliant Makefiles Closes: 827541 Changes: automake-1.15 (1:1.15-5) unstable; urgency=medium . * debian/patches/0005-Use-system-help2man-if-it-is-available.patch: Add patch to use system help2man for reproducibility. * debian/control, debian/rules: Use dh-autoreconf. * debian/patches/0006-Disable-t-check12.sh-and-t-check12-w.sh.patch: Disable t/check12.sh and t/check12-w.sh. (Closes: #827541) * debian/control: Standards-Version to 3.9.8. Checksums-Sha1: e2cfd5b1507e0b99c4ce91b936c830da97236501 2232 automake-1.15_1.15-5.dsc 4abf264ec47faa76427a5bf4b4f207b18dd49e98 12924 automake-1.15_1.15-5.debian.tar.xz d7e0a20925543a508b077149e01198f881878068 732706 automake_1.15-5_all.deb Checksums-Sha256: 82af7bc3721c6eddf38b9e822e0bc3a4e4484579004b4b35e67749fc021dcb63 2232 automake-1.15_1.15-5.dsc c9095f84e486aaf70ea19baddae58eaad39f54a52b9528d20cc4f35cb2de19c5 12924 automake-1.15_1.15-5.debian.tar.xz 8cd4dfd30513e6b94b2ed523cd3987ff5c1d0afd6991f46fa25ced571c9a20c5 732706 automake_1.15-5_all.deb Files: 4f7482a83051bce1faad6480790b976e 2232 devel optional automake-1.15_1.15-5.dsc 3386964e3a893327be4f14c6d69ca17f 12924 devel optional automake-1.15_1.15-5.debian.tar.xz 97af4001686ef971dbb16c397518b90a 732706 devel option
Bug#822337: upgrade from libfreeradius-client to radcli
Am 02.11.16 um 23:38 schrieb Jan Wagner: > it's my understanding that it's a drop in for freeradius-client > and radiusclient-ng. So simply adding 'libradcli-dev' as the first build > dependency alternaive should do the trick? monitoring-plugins configure tries to detect the radius library which can't be detected, with libradcli-dev (and libradcli4) installed: configure: WARNING: Skipping radius plugin configure: WARNING: install radius libs to compile this plugin (see REQUIREMENTS). With kind regards, Jan. -- Never write mail to , you have been warned! -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M+ V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y --END GEEK CODE BLOCK-- signature.asc Description: OpenPGP digital signature
Bug#828589: uw-imap: FTBFS with openssl 1.1.0
On 2016-09-12 17:00:28 [+0200], Kurt Roeckx wrote:
> > But this problem existed before 1.1.0 support (this patch).
> > What do you recommend here? The builtin usage
> > (X509_VERIFY_PARAM_set_hostflags()) looks simple. The alternative
> > X509_check_host() is 1.0.2+ and since it can not be applied to stable I
> > don't see the point. I would add this for 1.1.0 and keep the current
> > validation for < 1.1.0.
>
> We don't want to upload this to Debian stable in any case. But if
> it's only doing the right thing with 1.1.0 that works for me.
So I've been looking at this again. The patch attached should do what
you asked for. It is so untested that EA is already using it…
Ehm. One thing: The callback that uw-imap invokes
scq(err_str_cpy, "hostname", cert_subj)
expects to pass the hostname of the connection. I have no idea how to
obtain it at that point. I could also drop that callback, set
SSL_VERIFY_NONE instead and then check the connection after the
handshake via SSL_get_verify_result(). It is enough exercise I think.
And I haven't got any response from upstream. So I leave it to someone
that can test it and is using it. So far it seems only alpine does [0].
[0]
http://sources.debian.net/src/alpine/2.20%2Bdfsg1-2/web/src/alpined.d/alpined.c/?hl=10831#L10831
> Kurt
Sebastian
>From b45c2495fffd431a4eee359c24a0b292c87bc33c Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior
Date: Wed, 2 Nov 2016 22:21:42 +
Subject: [PATCH] uw-imap: use openssl host validation
Signed-off-by: Sebastian Andrzej Siewior
---
src/osdep/unix/ssl_unix.c | 54 +++
1 file changed, 54 insertions(+)
diff --git a/src/osdep/unix/ssl_unix.c b/src/osdep/unix/ssl_unix.c
index 836e9fa..eddf420 100644
--- a/src/osdep/unix/ssl_unix.c
+++ b/src/osdep/unix/ssl_unix.c
@@ -205,6 +205,40 @@ static SSLSTREAM *ssl_start (TCPSTREAM *tstream,char *host,unsigned long flags)
static char *ssl_last_error = NIL;
static char *ssl_last_host = NIL;
+#if OPENSSL_VERSION_NUMBER >= 0x1010
+
+static int cert_verify(int preverify, X509_STORE_CTX* x509_ctx)
+{
+ sslcertificatequery_t scq;
+ X509* cert;
+ char cert_subj[250];
+ int err;
+ char err_str_cpy[50];
+ const char *err_str;
+
+ if (preverify == 1)
+return 1;
+
+ scq = mail_parameters(NIL, GET_SSLCERTIFICATEQUERY, NIL);
+ if (!scq)
+ return 0;
+
+ cert = X509_STORE_CTX_get_current_cert(x509_ctx);
+ if (!cert)
+ return 0;
+ err = X509_STORE_CTX_get_error(x509_ctx);
+ err_str = X509_verify_cert_error_string(err);
+ err_str_cpy[sizeof(err_str_cpy) - 1] = '\0';
+ strncpy(err_str_cpy, err_str, sizeof(err_str_cpy) - 1);
+
+ X509_NAME_oneline(X509_get_subject_name(cert), cert_subj, sizeof(cert_subj));
+
+ if (scq(err_str_cpy, "hostname", cert_subj) == 0)
+ return 0;
+ return 1;
+}
+#endif
+
static char *ssl_start_work (SSLSTREAM *stream,char *host,unsigned long flags)
{
BIO *bio;
@@ -226,10 +260,12 @@ static char *ssl_start_work (SSLSTREAM *stream,char *host,unsigned long flags)
return "SSL context failed";
SSL_CTX_set_options (stream->context,0);
/* disable certificate validation? */
+#if OPENSSL_VERSION_NUMBER < 0x1010
if (flags & NET_NOVALIDATECERT)
SSL_CTX_set_verify (stream->context,SSL_VERIFY_NONE,NIL);
else SSL_CTX_set_verify (stream->context,SSL_VERIFY_PEER,ssl_open_verify);
/* set default paths to CAs... */
+#endif
SSL_CTX_set_default_verify_paths (stream->context);
/* ...unless a non-standard path desired */
if (s = (char *) mail_parameters (NIL,GET_SSLCAPATH,NIL))
@@ -259,6 +295,20 @@ static char *ssl_start_work (SSLSTREAM *stream,char *host,unsigned long flags)
/* create connection */
if (!(stream->con = (SSL *) SSL_new (stream->context)))
return "SSL connection failed";
+#if OPENSSL_VERSION_NUMBER >= 0x1010
+ SSL_set_tlsext_host_name(stream->con, host);
+ if (!(flags & NET_NOVALIDATECERT)) {
+ X509_VERIFY_PARAM *param;
+
+ param = SSL_get0_param(stream->con);
+ X509_VERIFY_PARAM_set_hostflags(param, X509_CHECK_FLAG_NO_PARTIAL_WILDCARDS);
+ X509_VERIFY_PARAM_set1_host(param, host, 0);
+
+ SSL_set_verify(stream->con, SSL_VERIFY_PEER, cert_verify);
+ } else {
+ SSL_set_verify(stream->con, SSL_VERIFY_NONE, 0);
+ }
+#endif
bio = BIO_new_socket (stream->tcpstream->tcpsi,BIO_NOCLOSE);
SSL_set_bio (stream->con,bio,bio);
SSL_set_connect_state (stream->con);
@@ -267,6 +317,7 @@ static char *ssl_start_work (SSLSTREAM *stream,char *host,unsigned long flags)
if (SSL_write (stream->con,"",0) < 0)
return ssl_last_error ? ssl_last_error : "SSL negotiation failed";
/* need to validate host names? */
+#if OPENSSL_VERSION_NUMBER < 0x1010
if (!(flags & NET_NOVALIDATECERT)) {
cert_subj[0] = '\0';
@@ -281,6 +332,7 @@ static char *ssl_start_work (SSLSTREAM *stream,char *host,unsigned long flags)
sprintf (tmp,"*%.128s: %.255s",err,cert ? cert_subj : "???");
return ssl_last_error = cpystr (tmp);
}
+#endif
retur
Processed: affects 842998 + erlang
Processing commands for cont...@bugs.debian.org: > affects 842998 + erlang Bug #842998 [erlang-base-hipe] erlang-base-hipe: OTP / HiPE broken with GCC 6.2 Added indication that 842998 affects erlang > thanks Stopping processing here. Please contact me if you need assistance. -- 842998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#830178: Possible fix
thanks a lot Piotr! these days i'm going thru the list of packages we care at work for stretch so a mail-ping was super effective :) On Wed, Nov 2, 2016 at 6:39 PM, Piotr Ożarowski wrote: > [Sandro Tosi, 2016-11-02] >> thanks! i pinged that bug to see if upstream will release a new >> version soo, if not we could just pick up that patch > > I uploaded -2, thanks for the reminder and sorry for the delay (RL, I > will try to keep up a bit with Debian this weekend...) -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#842998: erlang-base-hipe: OTP / HiPE broken with GCC 6.2
Package: erlang-base-hipe Version: 1:19.1.5+dfsg-1 Severity: grave Tags: upstream Justification: renders package unusable HiPE in the OTP 19.1.5 Debian package is broken (at least on amd64), because it was built with GCC 6.2. See also upstream report: http://erlang.org/pipermail/erlang-questions/2016-November/090753.html -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages erlang-base-hipe depends on: ii adduser 3.115 ii init-system-helpers 1.45 ii libc62.24-5 ii libsctp1 1.0.17+dfsg-1 ii libsystemd0 231-9 ii libtinfo56.0+20160917-1 ii procps 2:3.3.12-2 ii zlib1g 1:1.2.8.dfsg-2+b3 Versions of packages erlang-base-hipe recommends: ii erlang-crypto1:19.1.5+dfsg-1 ii erlang-syntax-tools 1:19.1.5+dfsg-1 ii libsctp1 1.0.17+dfsg-1 Versions of packages erlang-base-hipe suggests: ii erlang 1:19.1.5+dfsg-1 ii erlang-doc 1:19.1.5+dfsg-1 ii erlang-manpages 1:19.1.5+dfsg-1 ii erlang-tools 1:19.1.5+dfsg-1 -- no debconf information
Bug#837001: marked as done (naspro-core: FTBFS: fs.c:106:3: error: 'readdir_r' is deprecated [-Werror=deprecated-declarations])
Your message dated Wed, 02 Nov 2016 23:04:46 + with message-id and subject line Bug#837001: fixed in naspro-core 0.5.1-3 has caused the Debian Bug report #837001, regarding naspro-core: FTBFS: fs.c:106:3: error: 'readdir_r' is deprecated [-Werror=deprecated-declarations] 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.) -- 837001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: naspro-core Version: 0.5.1-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160906 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../.. -I../../include -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 > -pedantic -Wall -Werror -pthread -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o fs.lo fs.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include > -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -pedantic -Wall -Werror -pthread > -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -c fs.c -fPIC -DPIC -o .libs/fs.o > fs.c: In function 'nacore_fs_dir_get_next_entry': > fs.c:106:3: error: 'readdir_r' is deprecated [-Werror=deprecated-declarations] >readdir_r(dir->dir, (struct dirent *)ret, &entry); >^ > In file included from fs.c:27:0: > /usr/include/dirent.h:183:12: note: declared here > extern int readdir_r (DIR *__restrict __dirp, > ^ > cc1: all warnings being treated as errors > Makefile:398: recipe for target 'fs.lo' failed > make[5]: *** [fs.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2016/09/06/naspro-core_0.5.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: naspro-core Source-Version: 0.5.1-3 We believe that the bug you reported is fixed in the latest version of naspro-core, 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 837...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James Cowgill (supplier of updated naspro-core package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 02 Nov 2016 22:37:44 + Source: naspro-core Binary: libnacore5 libnacore-dev libnacore-doc Architecture: source Version: 0.5.1-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: James Cowgill Description: libnacore-dev - NASPRO core library (development files) libnacore-doc - NASPRO core library (documentation) libnacore5 - NASPRO core library Closes: 837001 Changes: naspro-core (0.5.1-3) unstable; urgency=medium . * QA upload. * Disable -Werror to fix FTBFS with glibc 2.24. (Closes: #837001) Checksums-Sha1: 3cd7b3c7ce76fbb9029f920a98f29b32a4e47b9b 1896 naspro-core_0.5.1-3.dsc 1e804a60df7c5433b670715c31e5d7271884728a 4608 naspro-core_0.5.1-3.debian.tar.xz Checksums-Sha256: 0ff7a159540545864bca50cab218f1186837017380f80504b821df92ad3957da 1896 naspro-core_0.5.1-3.dsc e14f617880f5b613e0baa38aa5f69e20da7fa46ac1ed73b8d4977a40600996e8 4608 naspro-core_0.5.1-3.debian.tar.xz Files: 2ee8dc8826b783673c1bea470aabeb29 1896 libs optional naspro-core_0.5.1-3.dsc 3ec56354a042768e8de0c206ff1b4102 4608 libs optional naspro-core_0.5.1-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYGmr/AAoJEMfxZ23qLQHvIrsQAKlwA7XXWwjgLm/pmp5Quh3w iMWMHwbe0mmp3E6lkf3SvARJeVg2U0aeV3nMeyrNT5Ft74Qs0CfVYzFmfhabyLK3 Qvk9jBlsCBYT1AObYfTZYfsQ+4YIyeEf06oAOejLX/T61SV1CGUviwXwshBhs0gF /tkn5icc1+ETJ5wlVpjEIjFraodeLt8ZE9zK+SW67HBMUCNzuqJzdtyQOJM5zchf Nq3GBo/9YLGMXW43RPqFqwFIP0Oz
Processed: Downgrading due to switch to libssl1.0-dev
Processing control commands: > severity -1 important Bug #828523 [src:qtbase-opensource-src] qtbase-opensource-src: FTBFS with openssl 1.1.0 Severity set to 'important' from 'serious' -- 828523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#830178: marked as done (mako: FTBFS: ValueError: too many values to unpack)
Your message dated Wed, 02 Nov 2016 23:04:40 + with message-id and subject line Bug#830178: fixed in mako 1.0.4+ds1-2 has caused the Debian Bug report #830178, regarding mako: FTBFS: ValueError: too many values to unpack 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.) -- 830178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mako Version: 1.0.4+ds1-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, mako fails to build from source in unstable/amd64: [..] copying build/lib.linux-x86_64-2.7/mako/template.py -> /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako creating /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/ext copying build/lib.linux-x86_64-2.7/mako/ext/__init__.py -> /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/ext copying build/lib.linux-x86_64-2.7/mako/ext/preprocessors.py -> /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/ext copying build/lib.linux-x86_64-2.7/mako/ext/babelplugin.py -> /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/ext copying build/lib.linux-x86_64-2.7/mako/ext/pygmentplugin.py -> /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/ext copying build/lib.linux-x86_64-2.7/mako/ext/extract.py -> /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/ext copying build/lib.linux-x86_64-2.7/mako/ext/turbogears.py -> /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/ext copying build/lib.linux-x86_64-2.7/mako/ext/linguaplugin.py -> /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/ext copying build/lib.linux-x86_64-2.7/mako/ext/beaker_cache.py -> /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/ext copying build/lib.linux-x86_64-2.7/mako/ext/autohandler.py -> /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/ext copying build/lib.linux-x86_64-2.7/mako/exceptions.py -> /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako copying build/lib.linux-x86_64-2.7/mako/util.py -> /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako byte-compiling /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/_ast_util.py to _ast_util.pyc byte-compiling /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/pygen.py to pygen.pyc byte-compiling /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/ast.py to ast.pyc byte-compiling /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/compat.py to compat.pyc byte-compiling /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/filters.py to filters.pyc byte-compiling /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/__init__.py to __init__.pyc byte-compiling /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/cache.py to cache.pyc byte-compiling /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/pyparser.py to pyparser.pyc byte-compiling /home/lamby/temp/cdt.20160707080835.RGttmOyLYo.mako/mako-1.0.4+ds1/debian/python-mako/usr/lib/python2.7/dist-packages/mako/lookup
Bug#828523: Downgrading due to switch to libssl1.0-dev
Control: severity -1 important We switched our build dependnecy on libssl-dev to libssl1.0-dev so I'm downgrading this bug. Of course I'm keeping this open because we need to switch to 1.1 as soons as upstream allows us. -- I wish to be cremated. One tenth of my ashes shall be given to my agent, as written in our contract. -- Groucho Marx Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#842776: marked as done (libdose3-ocaml-dev is uninstallable)
Your message dated Wed, 2 Nov 2016 23:51:47 +0100 with message-id and subject line Re: Bug#842776: libdose3-ocaml-dev is uninstallable has caused the Debian Bug report #842776, regarding libdose3-ocaml-dev is uninstallable 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.) -- 842776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libdose3-ocaml-dev Version: 5.0.1-6 Severity: grave Justification: renders package unusable Hi, libdose3-ocaml-dev in unstable depends on libocamlgraph-ocaml-dev-i0qi0:amd64. This is provided by libocamlgraph-ocaml-dev 1.8.6-1+b1 but a recent binNMU introduced libocamlgraph-ocaml-dev 1.8.6-1+b2. Thus, dose3 needs a rebuild with the new ocamlgraph version to fix this problem. Thanks! cheers, josch --- End Message --- --- Begin Message --- On 02/11/2016 23:48, Johannes Schauer wrote: > Quoting Mehdi Dogguy (2016-11-02 23:46:15) >> I may have missed something... but why not requesting a rebuild of the >> package >> instead of opening this bug? Is there anything else to do besides doing the >> binNMU? > > probably not. It was just a long time since I last filed a request for a > binNMU > and at the time I reported this I was pressed for time but didn't want to > forget about this, so I just quickly filed this bug against src:dose3. > Ok, thanks for the confirmation! I've now scheduled the binNMU and will close this bugreport. Regards, -- Mehdi signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#842776: libdose3-ocaml-dev is uninstallable
Hi Johannes, On 01/11/2016 08:04, Johannes Schauer wrote: > Package: libdose3-ocaml-dev > Version: 5.0.1-6 > Severity: grave > Justification: renders package unusable > > Hi, > > libdose3-ocaml-dev in unstable depends on > libocamlgraph-ocaml-dev-i0qi0:amd64. This is provided by > libocamlgraph-ocaml-dev 1.8.6-1+b1 but a recent binNMU introduced > libocamlgraph-ocaml-dev 1.8.6-1+b2. Thus, dose3 needs a rebuild with the > new ocamlgraph version to fix this problem. > Thanks for detecting this issue and filing the bug! I may have missed something... but why not requesting a rebuild of the package instead of opening this bug? Is there anything else to do besides doing the binNMU? -- Mehdi
Processed: tagging 828404
Processing commands for cont...@bugs.debian.org: > tags 828404 + fixed-upstream Bug #828404 [src:libpam-mount] libpam-mount: FTBFS with openssl 1.1.0 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 828404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#842776: libdose3-ocaml-dev is uninstallable
Hi, Quoting Mehdi Dogguy (2016-11-02 23:46:15) > I may have missed something... but why not requesting a rebuild of the package > instead of opening this bug? Is there anything else to do besides doing the > binNMU? probably not. It was just a long time since I last filed a request for a binNMU and at the time I reported this I was pressed for time but didn't want to forget about this, so I just quickly filed this bug against src:dose3. Thanks! cheers, josch signature.asc Description: signature
Bug#828404: libpam-mount: FTBFS with openssl 1.1.0
Hi, according to the upstream changelog, this is fixed in the latest release (2.16). Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#822337: [Pkg-nagios-devel] Bug#822337: upgrade from libfreeradius-client to radcli
Hi Daniel, Am 23.04.16 um 17:43 schrieb Daniel Pocock: > Please check the preinst for radcli to see if you are satisfied with it, > it has to copy /etc/radiusclient/* to /etc/radcli sorry, but the migration of configurations done by users or radiusclient/radcli maintainers is nothing we will deal in monitoring-plugins. With kind regards, Jan. -- Never write mail to , you have been warned! -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M+ V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y --END GEEK CODE BLOCK-- signature.asc Description: OpenPGP digital signature
Processed: Bug#837001 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 837001 pending Bug #837001 [src:naspro-core] naspro-core: FTBFS: fs.c:106:3: error: 'readdir_r' is deprecated [-Werror=deprecated-declarations] Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 837001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837001: marked as pending
tag 837001 pending thanks Hello, Bug #837001 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=pkg-multimedia/naspro-core.git;a=commitdiff;h=0298efa --- commit 0298efa47da4cacf22d75340b6c395e1c0f1712a Author: James Cowgill Date: Wed Nov 2 22:39:17 2016 + Upload to unstable diff --git a/debian/changelog b/debian/changelog index 2b9c2b1..e965508 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,9 @@ -naspro-core (0.5.1-3) UNRELEASED; urgency=medium +naspro-core (0.5.1-3) unstable; urgency=medium * QA upload. + * Disable -Werror to fix FTBFS with glibc 2.24. (Closes: #837001) - -- James Cowgill Wed, 02 Nov 2016 21:31:24 + + -- James Cowgill Wed, 02 Nov 2016 22:37:44 + naspro-core (0.5.1-2) unstable; urgency=medium
Processed: tagging 828451
Processing commands for cont...@bugs.debian.org: > tags 828451 + help Bug #828451 [src:netty-tcnative] netty-tcnative: FTBFS with openssl 1.1.0 Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 828451: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#830178: Possible fix
[Sandro Tosi, 2016-11-02] > thanks! i pinged that bug to see if upstream will release a new > version soo, if not we could just pick up that patch I uploaded -2, thanks for the reminder and sorry for the delay (RL, I will try to keep up a bit with Debian this weekend...)
Bug#822337: upgrade from libfreeradius-client to radcli
Hi Sandro, Am 02.11.16 um 23:16 schrieb Sandro Tosi: > On Sat, 23 Apr 2016 17:43:05 +0200 Daniel Pocock wrote: >> > monitoring-plugins-standard depends on libfreeradius-client >> > >> > libfreeradius-client has been deprecated in favor of radcli[1] >> > >> > Please update the build dependency to use radcli. The API is fully >> > compatible, radcli is a fork of the previous library, it is actively >> > maintained and includes many bug fixes. >> > >> > radcli is available in sid and jessie-backports >> > >> > Please check the preinst for radcli to see if you are satisfied with it, >> > it has to copy /etc/radiusclient/* to /etc/radcli > do you plan to make this change or do you see any issue with it? can i > help somehow? not being very familiar with all those radius stuff tooking into https:github.com/radcli/radcli#1-introduction (based originally on freeradius-client and radiusclient-ng and is source compatible with them) it's my understanding that it's a drop in for freeradius-client and radiusclient-ng. So simply adding 'libradcli-dev' as the first build dependency alternaive should do the trick? Cheers, Jan. -- Never write mail to , you have been warned! -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M+ V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y --END GEEK CODE BLOCK-- signature.asc Description: OpenPGP digital signature
Bug#840690: marked as done (ruby-foreman: FTBFS: Failed examples: rspec ./spec/foreman/export/inittab_spec.rb:17 # Foreman::Export::Inittab exports to the filesystem)
Your message dated Wed, 02 Nov 2016 22:20:29 +
with message-id
and subject line Bug#840690: fixed in ruby-foreman 0.82.0-2
has caused the Debian Bug report #840690,
regarding ruby-foreman: FTBFS: Failed examples: rspec
./spec/foreman/export/inittab_spec.rb:17 # Foreman::Export::Inittab exports to
the filesystem
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.)
--
840690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-foreman
Version: 0.82.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
ruby-foreman fails to build from source in unstable/amd64:
[..]
NoMethodError:
undefined method `stub' for
#
# /usr/lib/ruby/vendor_ruby/rspec/matchers.rb:967:in `method_missing'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:747:in
`method_missing'
# ./spec/foreman/export/upstart_spec.rb:14:in `block (2 levels) in '
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:443:in `instance_exec'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:443:in `instance_exec'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:350:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:507:in `block in
run_owned_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:506:in `each'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:506:in
`run_owned_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:593:in `block in
run_example_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:592:in `reverse_each'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:592:in
`run_example_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:462:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:490:in
`run_before_example'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:253:in `block in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:496:in `block in
with_around_and_singleton_context_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:453:in `block in
with_around_example_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `block in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:602:in
`run_around_example_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:453:in
`with_around_example_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:496:in
`with_around_and_singleton_context_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:251:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:627:in `block
in run_examples'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:623:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:623:in
`run_examples'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:589:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `block
in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block (3
levels) in run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block (2
levels) in run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1835:in
`with_suite_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:112:in `block in
run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:77:in `report'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:111:in `run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:87:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
# /usr/bin/rspec:4:in `'
37) Foreman::Export::Upstart with a formation exports to the filesystem
with concurrency
Failure/Error: before(:each) { stub(upstart).say }
NoMethodError:
undefined method `stub' for
#
# /usr/lib/ruby/vendor_ruby/rspec/matchers.rb:967:in `method_missing'
# /usr/lib/ruby/vendor_ruby/rspec/
Bug#828549: SLURM OpenSSL 1.1 issue - Patch to disable OpenSSL support until upstream fixes
Hi,
On 02/11/2016 20:06, Karl Kornel wrote:
> forwarded 828549 https://bugs.schedmd.com/show_bug.cgi?id=3226 tags 828549 +
> patch thanks
>
> Hello!
>
> It looks like even the latest SLURM Debian package, 16.05.6-1, still has this
> issue. I tested with OpenSSL package version 1.1.0b-2, building on a sid
> COWbuilder.
>
> The issue is being tracked upstream at this URL:
>
> https://bugs.schedmd.com/show_bug.cgi?id=3226
>
Thanks for the reference!
> The bug was filed on Oct. 31, and acknowledged on Nov. 1.
>
> SLURM only uses OpenSSL in one place: To create “job step credentials”.
> However, this is not the default: the default is to have MUNGE create those
> credentials.
>
> Since OpenSSL is only used in one place, and that’s not even as the default,
> I have created a Quilt patch which removes OpenSSL from the build entirely.
> Unfortunately, it’s not enough to change how we run ./configure; if the
> configure script sees an OpenSSL installation, it will use it, so I have to
> completely remove the test for OpenSSL, as well as the Makefile.am file that
> would trigger the compilation of OpenSSL-using code.
>
I think it is easier to port Slurm to use OpenSSL 1.1. Attached is a tentative
patch that makes Slurm compile against OpenSSL 1.1. I haven't tested it
thoroughly and I would appreciate some help. In short, EVP_MD_CTX became opaque
in OpenSSL 1.1 and we cannot use it directly anymore. Similar fixes have been
applied to other softs.
Another way to avoid the bug in Debian is to use OpenSSL 1.0 by choosing
libssl1.0-dev in the Build-Depends line. It doesn't fix the issue but prevents
the system from removing it from testing.
Regards,
--
Mehdi
From: Mehdi Dogguy
Date: Wed, 2 Nov 2016 22:54:38 +0100
Subject: Port to OpenSSL 1.1
---
src/plugins/crypto/openssl/crypto_openssl.c | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/src/plugins/crypto/openssl/crypto_openssl.c b/src/plugins/crypto/openssl/crypto_openssl.c
index 2fa9767..87c0b55 100644
--- a/src/plugins/crypto/openssl/crypto_openssl.c
+++ b/src/plugins/crypto/openssl/crypto_openssl.c
@@ -179,7 +179,7 @@ extern int
crypto_sign(void * key, char *buffer, int buf_size, char **sig_pp,
unsigned int *sig_size_p)
{
- EVP_MD_CTXectx;
+ EVP_MD_CTX*ectx;
int rc= SLURM_SUCCESS;
int ksize = EVP_PKEY_size((EVP_PKEY *) key);
@@ -188,17 +188,18 @@ crypto_sign(void * key, char *buffer, int buf_size, char **sig_pp,
*/
*sig_pp = xmalloc(ksize * sizeof(unsigned char));
- EVP_SignInit(&ectx, EVP_sha1());
- EVP_SignUpdate(&ectx, buffer, buf_size);
+ ectx = EVP_MD_CTX_create();
+ EVP_SignInit(ectx, EVP_sha1());
+ EVP_SignUpdate(ectx, buffer, buf_size);
- if (!(EVP_SignFinal(&ectx, (unsigned char *)*sig_pp, sig_size_p,
+ if (!(EVP_SignFinal(ectx, (unsigned char *)*sig_pp, sig_size_p,
(EVP_PKEY *) key))) {
rc = SLURM_ERROR;
}
#ifdef HAVE_EVP_MD_CTX_CLEANUP
/* Note: Likely memory leak if this function is absent */
- EVP_MD_CTX_cleanup(&ectx);
+ EVP_MD_CTX_destroy(ectx);
#endif
return rc;
@@ -208,13 +209,14 @@ extern int
crypto_verify_sign(void * key, char *buffer, unsigned int buf_size,
char *signature, unsigned int sig_size)
{
- EVP_MD_CTX ectx;
+ EVP_MD_CTX *ectx;
intrc;
- EVP_VerifyInit(&ectx, EVP_sha1());
- EVP_VerifyUpdate(&ectx, buffer, buf_size);
+ ectx = EVP_MD_CTX_create();
+ EVP_VerifyInit(ectx, EVP_sha1());
+ EVP_VerifyUpdate(ectx, buffer, buf_size);
- rc = EVP_VerifyFinal(&ectx, (unsigned char *) signature,
+ rc = EVP_VerifyFinal(ectx, (unsigned char *) signature,
sig_size, (EVP_PKEY *) key);
if (rc <= 0)
rc = SLURM_ERROR;
@@ -223,7 +225,7 @@ crypto_verify_sign(void * key, char *buffer, unsigned int buf_size,
#ifdef HAVE_EVP_MD_CTX_CLEANUP
/* Note: Likely memory leak if this function is absent */
- EVP_MD_CTX_cleanup(&ectx);
+ EVP_MD_CTX_destroy(ectx);
#endif
return rc;
Bug#828513: proftpd-dfsg: FTBFS with openssl 1.1.0
On 02.11.2016 10:49, Hilmar Preuße wrote: Hi Kurt, > According to [2] one could use libssl1.0-dev as BD instead. > Unfortunately this removes libpq-dev, which is needed by our package > too. Not sure if the Postgres people will change here so we can use > the work around for stretch. > OK, they did. I fixed the BD in our git. As soon as our fixed packages has been uploaded I'll lower this bug to non-rc. Hilmar -- http://www.hilmar-preusse.de.vu/ #206401 http://counter.li.org
Bug#822337: upgrade from libfreeradius-client to radcli
Hello monitoring-plugin maintainers! On Sat, 23 Apr 2016 17:43:05 +0200 Daniel Pocock wrote: > monitoring-plugins-standard depends on libfreeradius-client > > libfreeradius-client has been deprecated in favor of radcli[1] > > Please update the build dependency to use radcli. The API is fully > compatible, radcli is a fork of the previous library, it is actively > maintained and includes many bug fixes. > > radcli is available in sid and jessie-backports > > Please check the preinst for radcli to see if you are satisfied with it, > it has to copy /etc/radiusclient/* to /etc/radcli do you plan to make this change or do you see any issue with it? can i help somehow?
Bug#842677: Fixed #842677
On Wed, Nov 02, 2016 at 11:01:26PM +0100, Ruben Undheim wrote: > Hi Santiago! > > Thanks for reporting the bug. > > I've uploaded the fix, but I completely forgot to add your name to the > changelog! Oh, don't worry about that. You fixed the bug very quickly, which is already a form of appreciation. Thanks a lot.
Bug#841883: linux-image-4.7.0-1-686: cannot boot with 4.7.8-1, stuck at loading initrd
On Tue, 01 Nov 2016 10:28:40 -0600 Ben Hutchings wrote: > On Tue, 2016-11-01 at 11:31 +0100, Francesco Poli wrote: > [...] > > I expected to find a linux-image-4.8.0-1-686 package in unstable, but > > it seems to be only present as a virtual package, provided by > > linux-image-4.8.0-1-686-unsigned: > > Correct - the code-signed packages can't be uploaded until all the > unsigned packages are built, and the ARM builds took a long time. Thanks for the explanation, now everything is way clearer! :-) > They will be available soon. And indeed they became available, while I was striving to find the time to test version 4.8.5-1: here's the outcome, I installed the new linux image from unstable (aptitude -t unstable install linux-image-686) and rebooted. I can confirm that version 4.8.5-1 works correctly. So, as far as I am *personally* concerned, this bug may be closed as fixed in version 4.8.5-1 and/or forcemerged with #841850. Thanks a lot for your assistance and helpfulness! Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpeQtUhRBx5x.pgp Description: PGP signature
Bug#830178: Possible fix
thanks! i pinged that bug to see if upstream will release a new version soo, if not we could just pick up that patch On Wed, Nov 2, 2016 at 6:05 PM, Nish Aravamudan wrote: > On Wed, Nov 2, 2016 at 3:00 PM, Sandro Tosi wrote: >> On Mon, 26 Sep 2016 17:34:47 -0700 Nish Aravamudan >> wrote: >>> So I am tracking the same issue seen on Ubuntu 16.10 and I found: >>> >>> https://github.com/sphinx-doc/sphinx/pull/2396 >>> >>> I tested the following patch to the sourc3, and it does seem to build, >>> although I'm not sure I fully understand why yet (I'm completely new to >>> sphinx, just trying to help fix these bugs :) But I think it's because >>> upstream sphinx has changed an underlying data structure (index)? >>> >>> -Nish >>> >>> --- a/doc/build/templates/genindex.mako >>> +++ b/doc/build/templates/genindex.mako >>> @@ -21,7 +21,7 @@ >>> numcols = 1 >>> numitems = 0 >>> %> >>> -% for entryname, (links, subitems) in entries: >>> +% for entryname, (links, subitems, dummy) in entries: >>> >>> >>> % if links: >>> >> >> hey Piotr, did you have a chance to look at this patch? do you think >> it's ok to apply to the debian package or would you rather forward it >> upstream and ask what they thnk about it? > > Sorry, I should have updated this bug: upstream mako has picked this > up already: https://github.com/zzzeek/mako/pull/20 > > -Nish -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#830178: Possible fix
On Wed, Nov 2, 2016 at 3:00 PM, Sandro Tosi wrote: > On Mon, 26 Sep 2016 17:34:47 -0700 Nish Aravamudan > wrote: >> So I am tracking the same issue seen on Ubuntu 16.10 and I found: >> >> https://github.com/sphinx-doc/sphinx/pull/2396 >> >> I tested the following patch to the sourc3, and it does seem to build, >> although I'm not sure I fully understand why yet (I'm completely new to >> sphinx, just trying to help fix these bugs :) But I think it's because >> upstream sphinx has changed an underlying data structure (index)? >> >> -Nish >> >> --- a/doc/build/templates/genindex.mako >> +++ b/doc/build/templates/genindex.mako >> @@ -21,7 +21,7 @@ >> numcols = 1 >> numitems = 0 >> %> >> -% for entryname, (links, subitems) in entries: >> +% for entryname, (links, subitems, dummy) in entries: >> >> >> % if links: >> > > hey Piotr, did you have a chance to look at this patch? do you think > it's ok to apply to the debian package or would you rather forward it > upstream and ask what they thnk about it? Sorry, I should have updated this bug: upstream mako has picked this up already: https://github.com/zzzeek/mako/pull/20 -Nish
Bug#841662: libserver-starter-perl: test suite sometimes times out
On Tue, Nov 01, 2016 at 09:24:06PM +0100, gregor herrmann wrote: > On Sun, 30 Oct 2016 20:03:49 +0200, Niko Tyni wrote: > > > Given it fails somewhat regularly on both ci.debian.net and > > tests.reproducible-builds.org, possibly a faster machine would improve > > the chances of reproducing it. Just getting the log of 'strace -f > > -olog prove -l t/01-starter.t' when it locks up would help tremendously, > > but I ran it for two hours or so like that without a single lockup. > > I failed as well on Sunday but today I succeeded. > Attached is the output of > > while :; do strace -f -olog prove -l t/04-starter-dir.t t/05-killolddelay.t > t/06-autorestart.t || break ; done Oh awesome, thanks! Note to self: next time ask for time stamps too (strace -ttt or so). But this will do quite fine :) The problem (at least the one visible in this trace) seems to be related to Test::TCP. The test_tcp() call in t/06-autorestart.t finds an empty port with Net::EmptyPort, then passes it to both the client and the server code. The server starts up in a child process in Test::TCP::start(), but gets EADDRINUSE when binding the listener socket for some reason. The parent process in Test::TCP::start() then hangs in Net::Empty::wait_port(), waiting for the port to become available before calling the client code but always getting ECONNREFUSED. The Server::Starter tests should probably specify a max_wait parameter to test_tcp(). That should fix at least these hangs, probably in exchange for test failures. However, I'm not sure what causes the EADDRINUSE value. Either the kernel keeps the port reserved even after it got closed (Net::EmptyPort finds a port by binding to one and then closing it immediately), or some unrelated process steals the port in between, possibly for a non-listener socket (hence ECONNREFUSED). The latter explanation feels somewhat more plausible, particularly as the hangs seem to happen more on busy hosts. This should be easy-ish to demonstrate but I'm out of time for tonight. I'm not totally convinced this is the same hang I was seeing in my earlier investigations fwiw, but it's at least a step forward :) -- Niko
Bug#830178: Possible fix
On Mon, 26 Sep 2016 17:34:47 -0700 Nish Aravamudan wrote: > So I am tracking the same issue seen on Ubuntu 16.10 and I found: > > https://github.com/sphinx-doc/sphinx/pull/2396 > > I tested the following patch to the sourc3, and it does seem to build, > although I'm not sure I fully understand why yet (I'm completely new to > sphinx, just trying to help fix these bugs :) But I think it's because > upstream sphinx has changed an underlying data structure (index)? > > -Nish > > --- a/doc/build/templates/genindex.mako > +++ b/doc/build/templates/genindex.mako > @@ -21,7 +21,7 @@ > numcols = 1 > numitems = 0 > %> > -% for entryname, (links, subitems) in entries: > +% for entryname, (links, subitems, dummy) in entries: > > > % if links: > hey Piotr, did you have a chance to look at this patch? do you think it's ok to apply to the debian package or would you rather forward it upstream and ask what they thnk about it? thanks!!
Bug#842677: Fixed #842677
Hi Santiago! Thanks for reporting the bug. I've uploaded the fix, but I completely forgot to add your name to the changelog! I'm sorry about that. Cheers, Ruben
Processed: Changes for 828549
Processing commands for cont...@bugs.debian.org: > forwarded 828549 https://bugs.schedmd.com/show_bug.cgi?id=3226 Bug #828549 [src:slurm-llnl] slurm-llnl: FTBFS with openssl 1.1.0 Set Bug forwarded-to-address to 'https://bugs.schedmd.com/show_bug.cgi?id=3226'. > tags 828549 + patch Bug #828549 [src:slurm-llnl] slurm-llnl: FTBFS with openssl 1.1.0 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 828549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forwarded 842019 https://sourceforge.net/p/makedumpfile/feature-requests/5/
Processing commands for cont...@bugs.debian.org: > forwarded 842019 https://sourceforge.net/p/makedumpfile/feature-requests/5/ Bug #842019 [makedumpfile] makedumpfile issues many readpage_elf: Attempt to read non-existent page Set Bug forwarded-to-address to 'https://sourceforge.net/p/makedumpfile/feature-requests/5/'. > thanks Stopping processing here. Please contact me if you need assistance. -- 842019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841705: [lshw] lshw 02.18-0.1 hangs Stretch
Hello Derek, On Sat, 22 Oct 2016 14:56:22 +0100 Derek wrote: > Just executing lshw as root causes the monitor to go blank, after a few > seconds the desktop reappears but it's unresponsive. The desktop > disappearing and reappearing repeats for a minute or two before > rebooting. > > The Magic Sys Rq key combination allows me to reboot the PC. > > There's nothing in /var/log/* that relates to the hang. > > Please ask if there's anything I can do to provide more information. i tried on my system and on a virtual machine and they both work fine, so it's possible it's something specific to your machine that makes lshw unhappy. have you tried multiple times and the all end up in your machine being unresponsive? did you dist-upgraded your machine recently? if not, could you try to upgrade it and retry? thanks
Bug#828371: lastpass-cli openssl 1.1.0 now has PR upstream
Control: forwarded -1 https://github.com/lastpass/lastpass-cli/pull/215 Control: tags -1 + upstream patch Hello! I've sent a PR to upstream that fixes building against OpenSSL 1.1.0. Same patch should apply cleanly to the packaged version. Regards, Andreas Henriksson
Processed: lastpass-cli openssl 1.1.0 now has PR upstream
Processing control commands: > forwarded -1 https://github.com/lastpass/lastpass-cli/pull/215 Bug #828371 [src:lastpass-cli] lastpass-cli: FTBFS with openssl 1.1.0 Set Bug forwarded-to-address to 'https://github.com/lastpass/lastpass-cli/pull/215'. > tags -1 + upstream patch Bug #828371 [src:lastpass-cli] lastpass-cli: FTBFS with openssl 1.1.0 Added tag(s) patch and upstream. -- 828371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 830369 to fabric, fixed 830369 in fabric/1.10.2-1.1
Processing commands for cont...@bugs.debian.org: > reassign 830369 fabric Bug #830369 [src:ipython] ipython: FTBFS: ImportError: No module named Crypto Bug reassigned from package 'src:ipython' to 'fabric'. No longer marked as found in versions ipython/2.4.1-1. Ignoring request to alter fixed versions of bug #830369 to the same values previously set > fixed 830369 fabric/1.10.2-1.1 Bug #830369 [fabric] ipython: FTBFS: ImportError: No module named Crypto Marked as fixed in versions fabric/1.10.2-1.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 830369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841247: [Calendarserver-maintainers] Bug#841247: calypso: UnicodeDecodeError when importing an .ics
Hi Mathias, On Wed, Nov 02, 2016 at 01:14:02PM +0100, Mathias Behrle wrote: > control: affects -1 + tryton-modules-calendar > tryton-modules-calendar-classification tryton-modules-calendar-scheduling > tryton-modules-calendar-todo tryton-modules-party-vcarddav tryton-meta > > > From: Guido Günther > > To: Jens Reyer , 841...@bugs.debian.org > > Subject: Re: Bug#841247: calypso: UnicodeDecodeError when importing an .ics > > Date: Sun, 23 Oct 2016 12:28:37 +0200 > > > Hi Guido, > > > The unicode handling for python 2.7 got broken in upstream commit > > > > > > https://github.com/eventable/vobject/commit/b3f9bbcf4cf222f0dda3ac29f96364c5d7ab5f16 > > > > Let's see if upstream cares at all. If not we should rather drop the > > python2.7 version for stretch. > > There are currently 6 Tryton modules affected as rdepends of python-vobject. > There are still some bits in the Tryton framework lacking Python3 support, so > it is currently not possible to switch the whole Tryton stuff to Python3 (and > I > suppose this won't be the case for stretch). Dropping the Python2 version of > python-vobject would seriously hurt those Tryton modules. So please let's find > a way to keep the Python2 version in the archive (for stretch). It breaks calyso as well which I'd rather see in the archive than removed. The bug is fixable. Someone needs to sit down and cook a patch. I have it on the TODO list but work is piling up at the moment - but I hope to get it done til the end of the year. Somebody uploading 0.8.x for python2 would be another option. Cheers, -- Guido
Bug#840516: doesn't work with django 1.10
On Wed, 12 Oct 2016 13:35:14 +0200 Daniel Baumann wrote: > Package: graphite-web > Version: 0.9.15+debian-2 > Severity: serious > > Hi Jonas, > > graphite-web doesn't work with django 1.10 anymore, can you please upgrade? Hello Daniel, can you provide a bit more content, like for example what error you get? Upstream latest release is what is packaged in debian so there is nothing to upgrade to. from the looks at https://github.com/graphite-project/graphite-web/commit/5d139bd878afad4e63be4f50e909aff9b27c7327 it looks like graphite-web only wants to support 1.9.*
Bug#828443: mosquitto-auth-plugin debdiff
Control: tags -1 + upstream patch Hello! I've submitted a PR upstream. Attaching a debdiff for your convenience that adds the patch to the packaging as it applies without modifications to the packaged version. Regards, Andreas Henriksson
Processed: mosquitto-auth-plugin debdiff
Processing control commands: > tags -1 + upstream patch Bug #828443 [src:mosquitto-auth-plugin] mosquitto-auth-plugin: FTBFS with openssl 1.1.0 Added tag(s) patch and upstream. -- 828443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#828287: dsniff: FTBFS with openssl 1.1.0
Hello Dug, in Debian we started the transition to OpenSSL 1.1.0: do you have any plan to port dsniff to that version? thanks! On Sun, 26 Jun 2016 12:21:31 +0200 Kurt Roeckx wrote: > Source: dsniff > Version: 2.4b1+debian-22.1 > Severity: important > Control: block 827061 by -1 > > Hi, > > OpenSSL 1.1.0 is about to released. During a rebuild of all packages using > OpenSSL this package fail to build. A log of that build can be found at: > https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/dsniff_2.4b1+debian-22.1_amd64-20160529-1415 > > On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of > the > reasons why it might fail. There are also updated man pages at > https://www.openssl.org/docs/manmaster/ that should contain useful > information. > > There is a libssl-dev package available in experimental that contains a recent > snapshot, I suggest you try building against that to see if everything works. > > If you have problems making things work, feel free to contact us.
Processed: stretch, not jessie
Processing commands for cont...@bugs.debian.org: > retitle 842972 openxenmanager: shouldn't be part of stretch Bug #842972 [openxenmanager] openxenmanager: shouldn't be part of Jessie Changed Bug title to 'openxenmanager: shouldn't be part of stretch' from 'openxenmanager: shouldn't be part of Jessie'. > tags 842972 sid stretch Bug #842972 [openxenmanager] openxenmanager: shouldn't be part of stretch Added tag(s) sid and stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 842972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841596: marked as pending
tag 841596 pending thanks Hello, Bug #841596 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/sqlobject.git;a=commitdiff;h=78e7ea0 --- commit 78e7ea0770a792b768e2b45a76df6b6d60985168 Author: Neil Muller Date: Wed Nov 2 18:34:30 2016 +0200 Add changelog entry diff --git a/debian/changelog b/debian/changelog index b1b5936..f4718f0 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +sqlobject (3.1.0+dfsg-2) UNRELEASED; urgency=low + + * Fix build failure with sqlite 3.15: new patch fix_sqlite_vacuum_cmd +backported from upstream. (Closes: #841596) + + -- Neil Muller Wed, 02 Nov 2016 18:32:58 +0200 + sqlobject (3.1.0+dfsg-1) unstable; urgency=low * Updated to latest upstream release.
Processed: Bug#841596 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 841596 pending Bug #841596 [src:sqlobject] sqlobject: FTBFS: tests failed Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 841596: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#828549: SLURM OpenSSL 1.1 issue - Patch to disable OpenSSL support until upstream fixes
forwarded 828549 https://bugs.schedmd.com/show_bug.cgi?id=3226 tags 828549 + patch thanks Hello! It looks like even the latest SLURM Debian package, 16.05.6-1, still has this issue. I tested with OpenSSL package version 1.1.0b-2, building on a sid COWbuilder. The issue is being tracked upstream at this URL: https://bugs.schedmd.com/show_bug.cgi?id=3226 The bug was filed on Oct. 31, and acknowledged on Nov. 1. SLURM only uses OpenSSL in one place: To create “job step credentials”. However, this is not the default: the default is to have MUNGE create those credentials. Since OpenSSL is only used in one place, and that’s not even as the default, I have created a Quilt patch which removes OpenSSL from the build entirely. Unfortunately, it’s not enough to change how we run ./configure; if the configure script sees an OpenSSL installation, it will use it, so I have to completely remove the test for OpenSSL, as well as the Makefile.am file that would trigger the compilation of OpenSSL-using code. The same Quilt patch also updates the configuration builder HTML, to remove the OpenSSL option. Finally, I update the the control file, README files, and the init scripts (removing the OpenSSL-related checks). All of these changes are in a series of two Git patch files, which are attached. -- A. Karl Kornel | System Administrator Research Computing | Stanford University +1 (650) 736-9327 0002-Update-Debian-files-for-OpenSSL-removal.patch Description: 0002-Update-Debian-files-for-OpenSSL-removal.patch 0001-Add-quilt-patch-to-disable-OpenSSL.patch Description: 0001-Add-quilt-patch-to-disable-OpenSSL.patch
Processed: forwarded
Processing commands for cont...@bugs.debian.org: > forwarded 828443 https://github.com/jpmens/mosquitto-auth-plug/issues/142 Bug #828443 [src:mosquitto-auth-plugin] mosquitto-auth-plugin: FTBFS with openssl 1.1.0 Set Bug forwarded-to-address to 'https://github.com/jpmens/mosquitto-auth-plug/issues/142'. > thanks Stopping processing here. Please contact me if you need assistance. -- 828443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#842982: lua-sec update prevents ssl connections with prosody
Package: lua-sec Version: 0.6-1 Severity: serious thanks Hi Enrico, after an "apt-get dist-upgrade" today on a Stretch system, which among others installed lua-sec 0.6-1, prosody was no longer able to accept ssl connections. All connections came from (unknown)@(unknown) and were rejected. After installing 0.5-1 everything was fine again. Can you please have a look? Thanks! Thorsten
Bug#780323: coreutils RC bugs not properly closed
Hello Michael, the bugs in the recipients list are not properly closed (according to their version graph in the BTS) and so they still appear unresolved - could you please fix their found/fixed versions? thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#842752: marked as done (postgresql-9.6: FTBFS: test failures on i386/armel/armhf)
Your message dated Wed, 02 Nov 2016 18:49:01 + with message-id and subject line Bug#842752: fixed in postgresql-9.6 9.6.1-2 has caused the Debian Bug report #842752, regarding postgresql-9.6: FTBFS: test failures on i386/armel/armhf 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.) -- 842752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: postgresql-9.6 Version: 9.6.1-1 Severity: serious Your package failed to build on i386, armel and armhf with test errors. See the logs at https://buildd.debian.org/status/package.php?p=postgresql-9.6 Emilio -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: postgresql-9.6 Source-Version: 9.6.1-2 We believe that the bug you reported is fixed in the latest version of postgresql-9.6, 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 842...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg (supplier of updated postgresql-9.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 02 Nov 2016 11:04:52 +0100 Source: postgresql-9.6 Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 postgresql-9.6 postgresql-9.6-dbg postgresql-client-9.6 postgresql-server-dev-9.6 postgresql-doc-9.6 postgresql-contrib-9.6 postgresql-plperl-9.6 postgresql-plpython-9.6 postgresql-plpython3-9.6 postgresql-pltcl-9.6 Architecture: source Version: 9.6.1-2 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers Changed-By: Christoph Berg Description: libecpg-compat3 - older version of run-time library for ECPG programs libecpg-dev - development files for ECPG (Embedded PostgreSQL for C) libecpg6 - run-time library for ECPG programs libpgtypes3 - shared library libpgtypes for PostgreSQL 9.6 libpq-dev - header files for libpq5 (PostgreSQL library) libpq5 - PostgreSQL C client library postgresql-9.6 - object-relational SQL database, version 9.6 server postgresql-9.6-dbg - debug symbols for postgresql-9.6 postgresql-client-9.6 - front-end programs for PostgreSQL 9.6 postgresql-contrib-9.6 - additional facilities for PostgreSQL postgresql-doc-9.6 - documentation for the PostgreSQL database management system postgresql-plperl-9.6 - PL/Perl procedural language for PostgreSQL 9.6 postgresql-plpython-9.6 - PL/Python procedural language for PostgreSQL 9.6 postgresql-plpython3-9.6 - PL/Python 3 procedural language for PostgreSQL 9.6 postgresql-pltcl-9.6 - PL/Tcl procedural language for PostgreSQL 9.6 postgresql-server-dev-9.6 - development files for PostgreSQL 9.6 server-side programming Closes: 842752 Changes: postgresql-9.6 (9.6.1-2) unstable; urgency=medium . * Team upload. . [ Martin Pitt ] * Add missing perl test dependency (for Test::More). . [ Christoph Berg ] * Explicitly disable PIE on 32 architectures. Previously we were just not enabling it, but it's on by default now in unstable. Closes: #842752. * libpq-dev: Remove dependency on libssl-dev (and comerr-dev and krb5-multidev) to unbreak co-installation with libssl1.0-dev. Checksums-Sha1: 17add7e63d07daba043e7726426bad0e5b770cb6 3634 postgresql-9.6_9.6.1-2.dsc 837d70a77ed46b2d75ede311a277a121cbaaf39e 20376 postgresql-9.6_9.6.1-2.debian.tar.xz Checksums-Sha256: 2fad895302ea58d1db661a25bbca9cef228535c957e3d918250c537a227723d4 3634 postgresql-9.6_9.6.1-2.dsc cda7c8c40942e7382ce63a6ef6a9ba26d80b132100fba2c4815aeb5a8a4a6905 20376 postgresql-9.6_9.6.1-2.debian.tar.xz Files: e8546840040c16f56daaef24515a3ca6 3634 database optional postgresql-9.6_9.6.1-2.dsc 1d7167f3558e67163e0f2bf024cf6447 20376 database optional postgresql-9.6_9.6.1-2.d
Bug#842324: console-setup: During apt-get dist-upgrade stage, console-setup did not finish cleanly under ja_JP.UTF-8 locale.
'critical' severity seems way exaggerated, and in particular if the error in is `iconv` that program is part of libc-bin so this bug should be reassigned to that pkg. I'll let the console-setup maint decide what to do of course, just posting my quick check on this RC bug. please CC me on replies -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#842979: Missing dependency on python-jtextfsm
Package: python-napalm-base Version: 0.18.0-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I have missed this dependency (which replaces gtextfsm). Will package it shortly. - -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (101, 'experimental-debug'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-napalm-base depends on: ii python-jinja2 2.8-1 ii python-netaddr 0.7.18-2 pn python:any python-napalm-base recommends no packages. python-napalm-base suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIvBAEBCAAZBQJYGi+6EhxiZXJuYXRAZGViaWFuLm9yZwAKCRCVpC/oNTUl+b1w EACT/8g5O7xshyAXy4k17IgXUo465S1McyOci2AXn3LbjRst5iYYz+Cb+SDhRmyB dpz62Qfy3iENfp/amjcvuY0UbqWoAhnfVamjh1RRaHR37MFAA6cWzeplZPg+0Etg YhdFMjHgSfXbRKQG1wLqYlFUNHBt0B63KSYZwX3F2SL129pZStpFEMM26xk8IzVE Sqc0fIbDgdODFI5X/3n9xq9ns/FAJ9mrEKT2KefjKQCsXA7KjSW9MvWhQ4QYqMxa n93bea6kwjKpMJm428TasksZggwoNhi8LComIQ2xljoT0Ur2rCHOUgIN9M2AeE++ 17GdEIucjl9aohA6waodJ724CxjXEVVJnpJhmsoKQOMp1xl/x1XwiqWgMa5xLqz5 eXWdeVpejAlmP4sE+ZH5dfdqZ9hh8AE/MIdBMlnTsFg6XOI8wMM6KM9/qUUoezsx ou3kwHyXwe+6NIn+vGgegjRu4NHvGxfgobFVbt8LIn0Gr3IbL9f97BIs9tfvt2Df sgd0wnXFA4cvW+wKXjICVXgarKpW7fVgkoXhunH1bL6svbS1Gy2ovVcesvhv/B+j BP/m9YuHBfrB7euBBY9XsPDQRLwIvMT6GkVlEBLh4ff5BuNlMl6mvo1x9HGFaYxc 0LlGtimwIUWy8fCsFtDbNOfZB7oSAFy0Y+EnnjCrUgCYmg== =Gy9A -END PGP SIGNATURE-
Bug#837629: OpenRD* with debian's u-boot 2016.09
On Nov 2, 2016, at 10:38 AM, Vagrant Cascadian wrote: > I've uploaded u-boot 2016.11~rc3 to the cascadia.debian.net > repository. I won’t hold my breath, but give it a try... I will. No promises on the target date, but “soon”! (-; > Another option which might help debug the issue is to build u-boot > mainline from source with an older GCC, such as what's shipped in > jessie. You could then build the individual targets rather than the > whole package, and it shouldn't take too long. Could also insert some > printf statements in the early boot, maybe to figure out exactly where > it is failing... I’ve never done anything like that. (Though I’m familiar with the usual UNIX software development tools, such as gnu-autoconf, gcc and make, etc. And I’d be glad to learn what I don’t know.) Would you be willing to walk me through the steps? Thanks! Rick
Bug#842972: openxenmanager: shouldn't be part of Jessie
Package: openxenmanager Version: 0.r80+dfsg-4 Severity: grave Justification: renders package unusable The current version of openxenmanager is severely outdated and is known to have too many issues. I orphaned it because I do not have any nearterm interest in Xen Management Suite. Since then the Xen Management is known to have a change in its management interface. So, it is very like to not work. This bug is filed to ensure that OXM, in its current buggy form, does not become part of Debian Stable. Thanks, Ritesh -- System Information: Debian Release: stretch/sid APT prefers testing-debug APT policy: (990, 'testing-debug'), (990, 'unstable'), (990, 'testing'), (500, 'unstable-debug'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.6brk0+ (SMP w/4 CPU cores) Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#837629: OpenRD* with debian's u-boot 2016.09
On 2016-10-27, Rick Thomas wrote: > On Oct 5, 2016, at 1:26 PM, Vagrant Cascadian wrote: >> On 2016-10-03, Rick Thomas wrote: deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main The repository should be signed by my key, available in the debian-keyring package in the archive (F0ADA5240891831165DF98EA7CFCD8CD257721E9). ... > Unfortunately testing u-boot on OpenRD fell by the wayside. > I gather that the current u-boot in experimental has OpenRD support removed? Both in experimental and unstable. > But… as of now, all the “interesting” bits are temporarily under control. > Would you like me to test something? I've uploaded u-boot 2016.11~rc3 to the cascadia.debian.net repository. I won't hold my breath, but give it a try... Another option which might help debug the issue is to build u-boot mainline from source with an older GCC, such as what's shipped in jessie. You could then build the individual targets rather than the whole package, and it shouldn't take too long. Could also insert some printf statements in the early boot, maybe to figure out exactly where it is failing... live well, vagrant signature.asc Description: PGP signature
Bug#818513: Fix for the gtk2-engines-wonderland FTBFS
Control: tags -1 patch A fix for the gtk2-engines-wonderland FTBFS is attached. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed Description: Fix the build by using AM_INIT_AUTOMAKE Author: Adrian Bunk Bug-Debian: https://bugs.debian.org/818513 --- gtk2-engines-wonderland-1.0.orig/configure.in +++ gtk2-engines-wonderland-1.0/configure.in @@ -1,8 +1,5 @@ -AC_INIT(Theme) - -# For automake. -VERSION=2.0.0 -PACKAGE=gtk2-bluecurve-engine +AC_INIT([gtk2-engines-wonderland], [1.0]) +AM_INIT_AUTOMAKE # Honor aclocal flags ACLOCAL="$ACLOCAL $ACLOCAL_FLAGS"
Processed: Fix for the gtk2-engines-wonderland FTBFS
Processing control commands: > tags -1 patch Bug #818513 [gtk2-engines-wonderland] FTBFS: ./missing: Command not found Added tag(s) patch. -- 818513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#828453: nginx: FTBFS with openssl 1.1.0
On Wed, Nov 02, 2016 at 05:22:21PM +0100, Kurt Roeckx wrote: > On Wed, Nov 02, 2016 at 10:39:29AM +0100, Moritz Muehlenhoff wrote: > > > > The issue hasn't been diagnosed upstream, but this will likely also affect > > nginx > > once rebuilt against openssl 1.1. > > It seems it was fixed in OpenSSL in the mean time. Ack, fixed with https://github.com/openssl/openssl/commit/a7faa6da317887e14e8e28254a83555983ed6ca7 Cheers, Moritz
Bug#826884: marked as done (snapd: /usr/bin/snap already used by the snap package)
Your message dated Wed, 02 Nov 2016 16:35:31 + with message-id and subject line Bug#826884: fixed in snapd 2.16-1 has caused the Debian Bug report #826884, regarding snapd: /usr/bin/snap already used by the snap package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 826884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: snapd Version: 2.0.5+1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 snap Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package snapd. Preparing to unpack .../snapd_2.0.5+1_amd64.deb ... Unpacking snapd (2.0.5+1) ... dpkg: error processing archive /var/cache/apt/archives/snapd_2.0.5+1_amd64.deb (--unpack): trying to overwrite '/usr/bin/snap', which is also in package snap 2013-11-29-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for libc-bin (2.22-11) ... Errors were encountered while processing: /var/cache/apt/archives/snapd_2.0.5+1_amd64.deb cheers, Andreas snap=2013-11-29-2_snapd=2.0.5+1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: snapd Source-Version: 2.16-1 We believe that the bug you reported is fixed in the latest version of snapd, 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 826...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek (supplier of updated snapd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 02 Nov 2016 12:14:52 + Source: snapd Binary: golang-github-ubuntu-core-snappy-dev golang-github-snapcore-snapd-dev snapd Architecture: source all amd64 Version: 2.16-1 Distribution: unstable Urgency: medium Maintainer: Steve Langasek Changed-By: Steve Langasek Description: golang-github-snapcore-snapd-dev - snappy development go packages. golang-github-ubuntu-core-snappy-dev - transitional dummy package snapd - Tool to interact with Ubuntu Core Snappy. Closes: 826884 Changes: snapd (2.16-1) unstable; urgency=medium . [ Michael Hudson-Doyle ] * New upstream release. * Import gopkg.in/cheggaaa/pb.v1 rather than github.com/cheggaaa/pb. * Switch to unconditional conflict against `snap` (Closes: #826884) * Update Vcs-Git and Vcs-Browser to point to alioth. . [ Steve Langasek ] * Remove govendor from gbp.conf, and import Ubuntu tarball as our orig.tar.gz (switching our packaging to non-native). * Add Uploaders. * Drop lintian overrides not used in Debian because we dynamically link against golang-yaml.v2. * Bump standards-version, no changes required. * Add/fix various lintian overrides. Checksums-Sha1: 2a23254af33ef4c370cae9cb39faa5be0cb2c01f 2816 snapd_2.16-1.dsc 1b5c458f1f5cf9b4db4b1877f30584b2de0fe12b 902480 snapd_2.16.orig.tar.xz e5d24f277e8b0c30283d57e5ebc9fe38112e2d94 28496 snapd_2.16-1.debian.tar.xz 12baea5986e085d0e556d2fe2a238a7973fc772c 462636 golang-github-snapcore-snapd-dev_2.16-1_all.deb 013deb8d3f55adb86cdab68cbd41e630623a92ce 26064 golang-github-ubuntu-core-snappy-dev_2.16-1_all.deb 997dcc010cdb57aeb46db8867e7ad269a2c5129a 2839338 snapd-dbgsym_2.16-1_amd64.deb 281b116536adf5a23d2f4f4b7465ba8bfd2ced2f 5523276 snapd_2.16-1_amd64.deb Checksums-Sha256: 02e96f123f1bf85005916565d713a03c7ffa6ea53f7df8cb606901685a100126 2816 snapd_2.16-1.dsc 895d46f5d85f393904e15b6326e4803b8cdea7c444b84a00c5971f4927acf66b 902480 snapd_2.16.orig.tar.xz 1800994d41b14b70618e54c926275b273bfcf41e797ae1001ebba11660323f28 28496 snapd_2.16-1.debian.tar.xz c689872ff4b88531ed90ffba9563a9e090b1da9c9d7f6739f28437f92f32c989 462636 golang-github-snapcore-snapd-dev_2.16-1_all.deb 87a409eda0309e843205969d59f916b05b263ca9945bdd78e3af82427ec462f9 26064 golang-github-ubuntu-core
Bug#811737: marked as done (nam: FTBFS with GCC 6: narrowing conversion)
Your message dated Wed, 02 Nov 2016 16:33:48 +
with message-id
and subject line Bug#811737: fixed in nam 1.15-4
has caused the Debian Bug report #811737,
regarding nam: FTBFS with GCC 6: narrowing conversion
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.)
--
811737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nam
Version: 1.15-3
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing
This package fails to build with GCC 6. GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.
Note that only the first error is reported; there might be more. You
can find a snapshot of GCC 6 in experimental. To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.
You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html
> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
>
> In file included from /<>/main.cc:109:0:
> /<>/bitmap/play.xbm: At global scope:
> /<>/bitmap/play.xbm:7:20: error: narrowing conversion of '240'
> from 'int' to 'char' inside { } [-Wnarrowing]
> 0x00, 0x00, 0x00};
> ^
>
> /<>/bitmap/play.xbm:7:20: error: narrowing conversion of '240'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/play.xbm:7:20: error: narrowing conversion of '240'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/play.xbm:7:20: error: narrowing conversion of '240'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/play.xbm:7:20: error: narrowing conversion of '240'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/play.xbm:7:20: error: narrowing conversion of '255'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/play.xbm:7:20: error: narrowing conversion of '240'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/play.xbm:7:20: error: narrowing conversion of '240'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/play.xbm:7:20: error: narrowing conversion of '240'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/play.xbm:7:20: error: narrowing conversion of '240'
> from 'int' to 'char' inside { } [-Wnarrowing]
> In file included from /<>/main.cc:110:0:
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '192'
> from 'int' to 'char' inside { } [-Wnarrowing]
> 0x00, 0x00, 0x00};
> ^
>
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '240'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '252'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '255'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '192'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '255'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '240'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '255'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '192'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '255'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '255'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '252'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '240'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/back.xbm:7:20: error: narrowing conversion of '192'
> from 'int' to 'char' inside { } [-Wnarrowing]
> In file included from /<>/main.cc:111:0:
> /<>/bitmap/stop.xbm:7:20: error: narrowing conversion of '224'
> from 'int' to 'char' inside { } [-Wnarrowing]
> 0x00, 0x00, 0x00};
> ^
>
> /<>/bitmap/stop.xbm:7:20: error: narrowing conversion of '224'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/stop.xbm:7:20: error: narrowing conversion of '224'
> from 'int' to 'char' inside { } [-Wnarrowing]
> /<>/bitmap/stop.xbm:7:20: error: narrowing conversion of '224'
> from 'int' to 'char' inside { } [-Wnarrowing]
...
--
Martin Michlmayr
Linux for HPE Helion, Hewlett P
Bug#828277: marked as done (dacs: FTBFS with openssl 1.1.0)
Your message dated Wed, 02 Nov 2016 16:33:33 + with message-id and subject line Bug#828277: fixed in dacs 1.4.38-1 has caused the Debian Bug report #828277, regarding dacs: FTBFS with openssl 1.1.0 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.) -- 828277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dacs Version: 1.4.28b-3 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/dacs_1.4.28b-3_amd64-20160529-1413 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- Source: dacs Source-Version: 1.4.38-1 We believe that the bug you reported is fixed in the latest version of dacs, 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 828...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg (supplier of updated dacs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 02 Nov 2016 17:21:22 +0100 Source: dacs Binary: dacs libapache2-mod-dacs libdacs1 libdacs-dev dacs-examples Architecture: source Version: 1.4.38-1 Distribution: unstable Urgency: medium Maintainer: Christoph Berg Changed-By: Christoph Berg Description: dacs - Distributed Access Control System (DACS) dacs-examples - Distributed Access Control System (DACS) - example web root libapache2-mod-dacs - Distributed Access Control System (DACS) - Apache Module libdacs-dev - Distributed Access Control System (DACS) - development files libdacs1 - Distributed Access Control System (DACS) - shared library Closes: 729470 729475 737641 810537 828277 835673 Changes: dacs (1.4.38-1) unstable; urgency=medium . * New upstream version. + Works with OpenSSL 1.1. (Closes: #828277) + Uses newer config.guess/sub. (Closes: #737641) + Installs dacsinit. (Closes: #729475) * Rewrite rules to use dh. * Disable infocard auth, broken in 1.4.38. * Drop debian/patches/ssl_hook_Fixup. * Update libdacs1.symbols. * Update watch file to also look for .txz files. * Fix libdacs-dev short description, thanks Daniele Forsi. (Closes: #810537) * Remove redundant "dacs" subdir from examples package. (Closes: #729470) * Add patch by Chris Lamb to make build reproducible, thanks! (Closes: #835673) * Support DEB_BUILD_OPTIONS=nodoc. Checksums-Sha1: 1f9e2ab26b38fb2f3856262d00cadd3f9064d07f 2240 dacs_1.4.38-1.dsc ba5c9515b9bd3447fb9d65df8325bd21ead56c69 2381540 dacs_1.4.38.orig.tar.xz 6ab1f84c052e0ffc4747acf120de39102d1074b6 18168 dacs_1.4.38-1.debian.tar.xz Checksums-Sha256: 857deb21d5366dae2abf512421d1adc737a04e9ee16c14712de042d7ce2bceaf 2240 dacs_1.4.38-1.dsc b7c23a806f3aa5c4a2619aa8c4df969cce206ab875a493fa0b9f1afe1f6c7ccc 2381540 dacs_1.4.38.orig.tar.xz 7c5dbc26841f59251dac71d54d54ab92a05906b2cbb72374d37c3b61318b0059 18168 dacs_1.4.38-1.debian.tar.xz Files: f386194f1f3694f5dfa5cbb2982af7bb 2240 web optional dacs_1.4.38-1.dsc 79b3d1d0601f839780eeef669b0b5fc9 2381540 web optional dacs_1.4.38.orig.tar.xz 78267c830fa408bd8271ba3633caa301 18168 web optional dacs_1.4.38-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYGhK1AAoJEExaa6sS0qeua3MP+wQADRxJLmFNTKERau/UGFVV Omr82yhNjIYoQ4CCLtRsH+3fXQfhyWTyDqm+RDW8XISURU7QqhTdegX6BxoTT5xw RsZ6P8mYFwXaIdHKb+Orbzz3AEad9+jygcqgbdXRK9BPsvEaxKloNQGe1BgCYYjV hhuxzH/Cnn5KJVXb/U1ko0fQGyUpiSQM8+ktL6sJ0xqjNDEHvZCXMiQn9+ftxP/W j+BRq3Y53C9qVrCOhCIInSK7vhQsH/rwahjQBDRBffgL6QhEh4hwaY03MCgNh8n6 G4o33c9IavSQh1FtKNR1F1IHPnJu++gKxvEtHTrmZWR
Bug#821500: Fix from Ubuntu for the glpi FTBFS
Control: tags -1 patch The fix I found in Ubuntu for this bug is attached, cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed diff -pruN 0.84.8+dfsg.1-1/debian/control 0.84.8+dfsg.1-1ubuntu1/debian/control --- 0.84.8+dfsg.1-1/debian/control 2014-10-18 09:28:23.0 + +++ 0.84.8+dfsg.1-1ubuntu1/debian/control 2016-03-24 07:31:31.0 + @@ -9,9 +10,9 @@ Standards-Version: 3.9.6 Package: glpi Architecture: all Depends: apache2 | apache | apache-ssl | apache-perl | httpd, -php5 | php5-cgi | libapache2-mod-php5, -php5-cli, -php5-mysql | php5-mysqlnd, +php | php-cgi | libapache2-mod-php, +php-cli, +php-mysql | php-mysqlnd, debconf (>= 0.2.26) | debconf-2.0, dbconfig-common, fonts-freefont-ttf, diff -pruN 0.84.8+dfsg.1-1/debian/glpi.cron.d 0.84.8+dfsg.1-1ubuntu1/debian/glpi.cron.d --- 0.84.8+dfsg.1-1/debian/glpi.cron.d 2014-10-18 09:24:01.0 + +++ 0.84.8+dfsg.1-1ubuntu1/debian/glpi.cron.d 2016-03-24 07:31:31.0 + @@ -1 +1 @@ -*/1 * * * * www-data /usr/bin/php5 /usr/share/glpi/front/cron.php +*/1 * * * * www-data /usr/bin/php /usr/share/glpi/front/cron.php
Processed: Fix from Ubuntu for the glpi FTBFS
Processing control commands: > tags -1 patch Bug #821500 [glpi] glpi: PHP 7.0 Transition Added tag(s) patch. -- 821500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#835581: marked as done (node-es6-promise: FTBFS in testing (compile-modules shows usage help))
Your message dated Wed, 2 Nov 2016 17:28:03 +0100 with message-id and subject line Better than fixed : closed has caused the Debian Bug report #835581, regarding node-es6-promise: FTBFS in testing (compile-modules shows usage help) 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.) -- 835581: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-es6-promise Version: 3.2.2+ds-1 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 dh_testdir -i dh_update_autotools_config -i dh_auto_configure -i debian/rules override_dh_auto_build make[1]: Entering directory '/<>/node-es6-promise-3.2.2+ds' mkdir dist compile-modules convert -f bundle -o dist/es6-promise.js lib/es6-promise.umd.js compile-modules [--help] [--version] [] Commands convert Converts modules from `import`/`export` to an ES5 equivalent. help Display help for a given command. debian/rules:10: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>/node-es6-promise-3.2.2+ds' debian/rules:7: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2 Sorry, I have no idea why it fails, but the failure is reproducible easily. Once you fix this, I would recommend that you try uploading this in source-only form, then we will get pretty official build logs in buildd.debian.org. Thanks. --- End Message --- --- Begin Message --- Hi, I meant to close the bug, not just mark it fixed. Snark on #debian-js--- End Message ---
Bug#828453: nginx: FTBFS with openssl 1.1.0
On Wed, Nov 02, 2016 at 10:39:29AM +0100, Moritz Muehlenhoff wrote: > > The issue hasn't been diagnosed upstream, but this will likely also affect > nginx > once rebuilt against openssl 1.1. It seems it was fixed in OpenSSL in the mean time. Kurt
Bug#812058: Fix for the gargoyle-free FTBFS
Control: tags -1 patch What broke the build is that gcc 6 changed the default C++ standard from C++98 to C++14. Not all valid C++98 code is also valid C++11 and C++14 code. Note that this just changed the default, when told to process C++98 code gcc 6 does not differ in any significant way from gcc 5. Making the code compatible with C++14 would be the best possible solution, but as a workaround it is possible to fix the build with this change to tell gcc that this is C++98 code. I am aware that this change results in a (harmless) compiler warning on every compiled C file. The build system of the package uses the same CFLAGS for both C and C++ code. --- debian/rules.old2016-11-02 15:42:31.0 + +++ debian/rules2016-11-02 15:44:50.0 + @@ -15,6 +15,7 @@ # This has to be exported to make some magic below work. export DH_OPTIONS +export DEB_CFLAGS_MAINT_APPEND = -std=gnu++98 # Tell 'jam' to statically link private libraries; the convenience # library is pretty small and it's much simpler in jam than trying to cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Fix for the gargoyle-free FTBFS
Processing control commands: > tags -1 patch Bug #812058 [gargoyle-free] gargoyle-free: FTBFS with GCC 6: error: exception cleanup for this Added tag(s) patch. -- 812058: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812058 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#799843: marked as done (googleearth-package: geerated package depends on lsb-core which is not available on sid)
Your message dated Wed, 2 Nov 2016 18:14:12 +0200 with message-id and subject line Re: Bug#799843: googleearth-package: generated package depends on lsb-core which is not available on sid has caused the Debian Bug report #799843, regarding googleearth-package: geerated package depends on lsb-core which is not available on sid 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.) -- 799843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: googleearth-package Version: 1.2.2 Severity: grave Justification: renders package unusable Dear Maintainer, it looks like that recently lsb-core disappeared from sid but the package generated by googleearth-package depends on it. This makes googleearth uninstallable. Alberto -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages googleearth-package depends on: ii bzip2 1.0.6-8 ii dpkg-dev1.18.3 ii fakeroot1.20.2-1 ii file1:5.25-2 ii wget1.16.3-3 ii x11-common 1:7.7+9 ii x11-utils 7.7+3 Versions of packages googleearth-package recommends: pn libdb5.3:i386 pn libgnutls26:i386 pn libldap-2.4-2:i386 pn libsasl2-2:i386 pn libsasl2-modules-db:i386 pn libsasl2-modules:i386 googleearth-package suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- On 2 November 2016 at 17:35, Frédéric Brière wrote: > On Mon, Oct 17, 2016 at 12:24:16PM +0200, Graham Inggs wrote: >> Please confirm if this was fixed by the upload of lsb 9.20161016. > > lsb-compat does indeed do the trick. Thanks! Thanks for confirming. Closing now.--- End Message ---
Bug#822852: gedit-latex-plugin also works for me
Control: severity -1 important gedit-latex-plugin also works for me, lowering the severity accordingly. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: gedit-latex-plugin also works for me
Processing control commands: > severity -1 important Bug #822852 [gedit-latex-plugin] gedit-latex-plugin: Activation of the plugin makes gedit segfault on startup Severity set to 'important' from 'critical' -- 822852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#799843: googleearth-package: generated package depends on lsb-core which is not available on sid
On Mon, Oct 17, 2016 at 12:24:16PM +0200, Graham Inggs wrote: > Please confirm if this was fixed by the upload of lsb 9.20161016. lsb-compat does indeed do the trick. Thanks!
Bug#841698: marked as done (node-lodash: FTBFS with bash as /bin/sh)
Your message dated Wed, 02 Nov 2016 15:33:45 + with message-id and subject line Bug#841698: fixed in node-lodash 2.4.1+dfsg-4 has caused the Debian Bug report #841698, regarding node-lodash: FTBFS with bash as /bin/sh 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.) -- 841698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-lodash Version: 2.4.1+dfsg-3 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, node-lodash fails to build from source in unstable/amd64 when /bin/sh is set to bash: […] debian/rules override_dh_auto_build make[1]: Entering directory '/home/lamby/temp/cdt.20161022151027.jj3SRN2eOz.db.node-lodash/node-lodash-2.4.1+dfsg' dh_auto_build if [ ! -d debian/build ]; \ then mkdir debian/build; \ fi; \ do \ cp lodash.js debian/build/; \ uglifyjs -o debian/build/$(basename lodash .js).min.js lodash.js; \ done /bin/sh: -c: line 3: syntax error near unexpected token `do' /bin/sh: -c: line 3: `do \' debian/rules:16: recipe for target 'override_dh_auto_build' failed […] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- node-lodash.2.4.1+dfsg-3.unstable.amd64.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Source: node-lodash Source-Version: 2.4.1+dfsg-4 We believe that the bug you reported is fixed in the latest version of node-lodash, 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 841...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paolo Greppi (supplier of updated node-lodash package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 02 Nov 2016 11:17:34 +0100 Source: node-lodash Binary: node-lodash libjs-lodash Architecture: source all Version: 2.4.1+dfsg-4 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers Changed-By: Paolo Greppi Description: libjs-lodash - Lo-dash is a Javascript utility library node-lodash - Lo-dash is a Node.js utility library Closes: 841698 Changes: node-lodash (2.4.1+dfsg-4) unstable; urgency=low . * Team upload. . * Fix build when /bin/sh is set to bash (Closes: #841698) Checksums-Sha1: 6c1a4986f43337bcdd5007458122b13288972598 2111 node-lodash_2.4.1+dfsg-4.dsc b3a1db53cc801c1d3af60a027c68ba3247069373 6420 node-lodash_2.4.1+dfsg-4.debian.tar.xz 7a751941bce48b6442ff7e3b4ad3af6fb9351615 56906 libjs-lodash_2.4.1+dfsg-4_all.deb daa38d76da0efaae4f1f913024ca759c6007d481 49074 node-lodash_2.4.1+dfsg-4_all.deb Checksums-Sha256: beb697c37515f47920d05262fc21cf17e3dc860279288fb214c0293fd012a0e5 2111 node-lodash_2.4.1+dfsg-4.dsc e6239bfc821d77da18378ad1742e97562cbe9e1d99e555fb91e130398c732002 6420 node-lodash_2.4.1+dfsg-4.debian.tar.xz f056ee98feee6b8662f79e94115460258ce605b0a8813915be5ee2bd99cedcee 56906 libjs-lodash_2.4.1+dfsg-4_all.deb 0b108c0b0c3b1655e0b9ef8b803543af8541ad2bc1a82ffbd1e07ac8d384ed72 49074 node-lodash_2.4.1+dfsg-4_all.deb Files: a88369c0458d92b5c90287cf037fef8b 2111 web optional node-lodash_2.4.1+dfsg-4.dsc a1a8da11b5827d4456c8e2dc5371a6cd 6420 web optional node-lodash_2.4.1+dfsg-4.debian.tar.xz 840532284740ab6f53d58060b043fb95 56906 web optional libjs-lodash_2.4.1+dfsg-4_all.deb e18ae875c05720d1a302cd5f9f0e3774 49074 web optional node-lodash_2.4.1+dfsg-4_all.deb -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYGgQwAAoJEM4fnGdFEsIqWecQAJGixgWrRA7UOxQPyBq9A37J D85IVWFV5oy2l4Te7PHlHjR9p425HNIzW2rwQ3h5UPFQb4pn2eoYlDWIt2s+nLLC PFuGK/8e8WG8Jqn5vDruaGoOoeVTjfVNT0e3Ma0jHvesuVIwLRinRlScNdphITDm FrA9Zgn/QxuuMSEFwed22uYs9jMeqJfhyCv3oXYFLLqgrjE1l69+mqx5KoEakjkg Ojd2v9p9ferEtAkTzV9C0A3k59V4hIYQKQKcz5Mh/rVGyaQZ6SOLWRkkGbiXKFRD bFjMKId9E7D5ETYxN+qIbLuUziNVMLFW+fpO+eYRwlmct4Q7ZhQ1KJp39fQCmtnv qyejADDevIkl3z9PEdlkOZFQqmtRgKlHzrQ5RoRowoi2ZCVmJXKkgJqtoz+LVb5g 9ZT+7SAl2cq+V8+CMxuKa52CYiCiCPbRWHEmIUxWdlh9+HYiPIJZq/
Bug#837359: ocaml: FTBFS on -fPIE binNMU on armhf - test failure
On Wed, Nov 02, 2016 at 02:22:00AM +, Ximin Luo wrote:
>...
Thanks a lot for debugging this.
> let emit_load_symbol_addr dst s =
> if !Clflags.pic_code then begin
> [..]
> end else if !arch > ARMv6 && not !Clflags.dlcode && !fastcode_flag then
> begin
> ` movw{emit_reg dst}, #:lower16:{emit_symbol s}\n`;
> ` movt{emit_reg dst}, #:upper16:{emit_symbol s}\n`;
> 2
>
> Note that !arch in ocaml means "get the current value of the mutable
> reference 'arch'".
The armel port has a lower baseline than armhf, this would explain the
difference between these ports.
> It looks like they already wrote the working code, it's just not being
> emitted here. So I just need to figure out how to make Cflags.pic_code true,
> which shouldn't be too hard. I will try this tomorrow when I'm less tired.
asmcomp/amd64/arch.ml:let pic_code = ref true
asmcomp/arm/arch.ml:let pic_code = ref false
cu
Adrian
[1] https://patches.ubuntu.com/o/ocaml/ocaml_4.02.3-6ubuntu2.patch
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Bug#842639: marked as done (libhmsbeagle1v5: unsatisfiable Depends: beignet-opencl-icd | mesa-opencl-icd | opencl-icd)
Your message dated Wed, 02 Nov 2016 15:06:01 +
with message-id
and subject line Bug#842639: fixed in libhmsbeagle 2.1.2+20160831-5
has caused the Debian Bug report #842639,
regarding libhmsbeagle1v5: unsatisfiable Depends: beignet-opencl-icd |
mesa-opencl-icd | opencl-icd
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.)
--
842639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhmsbeagle1v5
Version: 2.1.2+20160831-4
Severity: serious
emilio@tatooine:~$ grep-excuses libhmsbeagle
libhmsbeagle (2.1.2+20150609-1.1 to 2.1.2+20160831-4)
Maintainer: Debian Med Packaging Team
14 days old (needed 5 days)
libhmsbeagle1v5/armel unsatisfiable Depends: beignet-opencl-icd |
mesa-opencl-icd | opencl-icd
libhmsbeagle1v5/mips unsatisfiable Depends: beignet-opencl-icd |
mesa-opencl-icd | opencl-icd
libhmsbeagle1v5/mips64el unsatisfiable Depends: beignet-opencl-icd |
mesa-opencl-icd | opencl-icd
libhmsbeagle1v5/mipsel unsatisfiable Depends: beignet-opencl-icd |
mesa-opencl-icd | opencl-icd
libhmsbeagle1v5/powerpc unsatisfiable Depends: beignet-opencl-icd |
mesa-opencl-icd | opencl-icd
libhmsbeagle1v5/ppc64el unsatisfiable Depends: beignet-opencl-icd |
mesa-opencl-icd | opencl-icd
libhmsbeagle1v5/s390x unsatisfiable Depends: beignet-opencl-icd |
mesa-opencl-icd | opencl-icd
Valid candidate
beignet-opencl-icd is only available on any-{amd64,i386}, so that dependency
should be restricted to those architectures, or your package should be
removed from !any-{amd64,i386}.
Cheers,
Emilio
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500,
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: libhmsbeagle
Source-Version: 2.1.2+20160831-5
We believe that the bug you reported is fixed in the latest version of
libhmsbeagle, 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 842...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated libhmsbeagle package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 02 Nov 2016 15:12:30 +0100
Source: libhmsbeagle
Binary: libhmsbeagle-dev libhmsbeagle1v5 libhmsbeagle-java
Architecture: source amd64
Version: 2.1.2+20160831-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Andreas Tille
Description:
libhmsbeagle-dev - High-performance lib for Bayesian and Maximum Likelihood
phylogen
libhmsbeagle-java - High-performance lib for Bayesian and Maximum Likelihood
phylogen
libhmsbeagle1v5 - High-performance lib for Bayesian and Maximum Likelihood
phylogen
Closes: 842639
Changes:
libhmsbeagle (2.1.2+20160831-5) unstable; urgency=medium
.
* Restrict Architecture to those where beignet-opencl-icd|mesa-opencl-icd
is available (mesa-opencl-icd exists for 4 architectures)
Closes: #842639
Checksums-Sha1:
0421a5232093b23278663242880eccfccdd78ba3 2455 libhmsbeagle_2.1.2+20160831-5.dsc
0eb91ed706ce74a67f9a2413833928d75c568fce 36196
libhmsbeagle_2.1.2+20160831-5.debian.tar.xz
6e25f9aad274ae5bed61f7be3d50e4e403627d7d 166470
libhmsbeagle-dev_2.1.2+20160831-5_amd64.deb
e22a420edc85c9e0b380be201cd618635e8a2805 24156
libhmsbeagle-java_2.1.2+20160831-5_amd64.deb
29b19e5a47194f18015039b903547383dc139bdc 690734
libhmsbeagle1v5-dbgsym_2.1.2+20160831-5_amd64.deb
5db773e1dfe9638aa00635c50f433274fe1f0b6f 116274
libhmsbeagle1v5_2.1.2+20160831-5_amd64.deb
Checksums-Sha256:
4e90613b3bdaf07cbaa174b3de569531a5bf084a1da3a3c2d28f0a006ca98bf4 2455
libhmsbeagle_2.1.2+20160831-5.dsc
0fa4e81a41cf12e6e959fbcf715216df29339094c9933e410f6a15e41334dc78 36196
libhmsbeagle_2.1.2+20160831-5.debian.tar.xz
b87e495488f6f6a0174f422f0d2b200bd464d497cd4cb773a6f8
Bug#828505: pjproject: FTBFS with openssl 1.1.0
Control: severity -1 important 2.5.5~dfsg-2 in unstable now builds against libssl1.0-dev. Unless upstream releases a fixed version in time for stretch we will keep it that way. Downgrading severity in accordance with the release team. signature.asc Description: Digital signature
Processed: Re: Bug#828505: pjproject: FTBFS with openssl 1.1.0
Processing control commands: > severity -1 important Bug #828505 [src:pjproject] pjproject: FTBFS with openssl 1.1.0 Severity set to 'important' from 'serious' -- 828505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841763: unattended-upgrades: Breaks hard when apt is upgraded
Hi, On Sun, 23 Oct 2016, Alexandre Detiste wrote: > I think that adding this snippet to apt's debian/rules would fix this problem, > not tested tough. > > > > override_dh_systemd_start: > dh_systemd_start apt-daily.timer > Not restarting it would be one way to fix it. I don't know if apt-daily does other things that need a restart when upgrading. A different idea may be to use systemd-run to start apt (or the whole unattended-upgrades script) as a transient scope unit. AIUI, this should prevent systemd from killing apt, even if the parent process is terminated. Cheers, Stefan
Processed: FTBFS with openssl 1.1 set back to serious
Processing commands for cont...@bugs.debian.org: > severity 828521 serious Bug #828521 [src:qpid-proton] qpid-proton: FTBFS with openssl 1.1.0 Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 828521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#842914: marked as done (r-bioc-cummerbund: FTBFS (no package called 'foreign'))
Your message dated Wed, 02 Nov 2016 13:49:01 + with message-id and subject line Bug#842914: fixed in r-bioc-cummerbund 2.16.0-2 has caused the Debian Bug report #842914, regarding r-bioc-cummerbund: FTBFS (no package called 'foreign') 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.) -- 842914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:r-bioc-cummerbund Version: 2.16.0-1 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 R dh_testdir -i -O--buildsystem=R dh_update_autotools_config -i -O--buildsystem=R dh_auto_configure -i -O--buildsystem=R dh_auto_build -i -O--buildsystem=R dh_auto_test -i -O--buildsystem=R fakeroot debian/rules binary-indep dh binary-indep --buildsystem R dh_testroot -i -O--buildsystem=R dh_prep -i -O--buildsystem=R dh_installdirs -i -O--buildsystem=R dh_auto_install -i -O--buildsystem=R I: R Package: cummeRbund Version: 2.16.0 I: Building using R version 3.3.1.20161024-1 I: R API version: r-api-3 I: Using built-time from d/changelog: Thu, 27 Oct 2016 15:53:32 +0200 mkdir -p /<>/debian/r-bioc-cummerbund/usr/lib/R/site-library R CMD INSTALL -l /<>/debian/r-bioc-cummerbund/usr/lib/R/site-library --clean . "--built-timestamp='Thu, 27 Oct 2016 15:53:32 +0200'" * installing *source* package 'cummeRbund' ... ** R ** data ** inst ** preparing package for lazy loading Error in loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = vI[[j]]) : there is no package called 'foreign' Error : package 'Gviz' could not be loaded ERROR: lazy loading failed for package 'cummeRbund' * removing '/<>/debian/r-bioc-cummerbund/usr/lib/R/site-library/cummeRbund' dh_auto_install: R CMD INSTALL -l /<>/debian/r-bioc-cummerbund/usr/lib/R/site-library --clean . --built-timestamp='Thu, 27 Oct 2016 15:53:32 +0200' returned exit code 1 debian/rules:4: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 25 dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit status 2 Seems like a missing build-depends. Thanks. --- End Message --- --- Begin Message --- Source: r-bioc-cummerbund Source-Version: 2.16.0-2 We believe that the bug you reported is fixed in the latest version of r-bioc-cummerbund, 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 842...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-bioc-cummerbund package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 02 Nov 2016 14:09:24 +0100 Source: r-bioc-cummerbund Binary: r-bioc-cummerbund Architecture: source all Version: 2.16.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: r-bioc-cummerbund - tool for analysis of Cufflinks RNA-Seq output Closes: 842914 Changes: r-bioc-cummerbund (2.16.0-2) unstable; urgency=medium . * Build-Depends: r-cran-foreign, r-cran-nnet Closes: #842914 Checksums-Sha1: 9f9c9dc0f787c92c65ddf5614537bb06d4b267ac 2202 r-bioc-cummerbund_2.16.0-2.dsc 23a5d054b7f7cd81a92ac84c7d87e3d44ef7460c 3712 r-bioc-cummerbund_2.16.0-2.debian.tar.xz 20829885ffda686031680c81be57e07a03bb5e25 2127148 r-bioc-cummerbund_2.16.0-2_all.deb Checksums-Sha256: 316f80649a56c4dd96e6aa44c91bf0a17de3ba6d531a1dca002ca4ea2c92d209 2202 r-bioc-cummerbund_2.16.0-2.dsc 2a49f83da72e1daf665ecd924873d6efc307022585c3809c0030b6585df00b74 3712 r-bioc-cummerbund_2.16.0-2.debian.tar.xz d6693482f72d80a1b13bd3be74b6ecc6dd36e84f76ae56f0675befb0726b4fcd 2127148 r-bioc-cummerbund_2.16.0-2_all.deb Files: 2ccbfbe3cfcebb88704e47394a4b8845 2202 gnu-r optional r-bioc-cummerbund_2.16.0-2.dsc 0ff30b5c42fc432f2b51b5aebf122a3e
Bug#842915: marked as done (r-bioc-gviz: FTBFS (no package called 'foreign'))
Your message dated Wed, 02 Nov 2016 13:04:58 + with message-id and subject line Bug#842915: fixed in r-bioc-gviz 1.18.0-2 has caused the Debian Bug report #842915, regarding r-bioc-gviz: FTBFS (no package called 'foreign') 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.) -- 842915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:r-bioc-gviz Version: 1.18.0-1 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 R dh_testdir -i -O--buildsystem=R dh_update_autotools_config -i -O--buildsystem=R dh_auto_configure -i -O--buildsystem=R dh_auto_build -i -O--buildsystem=R dh_auto_test -i -O--buildsystem=R fakeroot debian/rules binary-indep dh binary-indep --buildsystem R dh_testroot -i -O--buildsystem=R dh_prep -i -O--buildsystem=R dh_installdirs -i -O--buildsystem=R dh_auto_install -i -O--buildsystem=R I: R Package: Gviz Version: 1.18.0 I: Building using R version 3.3.1.20161024-1 I: R API version: r-api-3 I: Using built-time from d/changelog: Thu, 27 Oct 2016 15:44:42 +0200 mkdir -p /<>/debian/r-bioc-gviz/usr/lib/R/site-library R CMD INSTALL -l /<>/debian/r-bioc-gviz/usr/lib/R/site-library --clean . "--built-timestamp='Thu, 27 Oct 2016 15:44:42 +0200'" * installing *source* package 'Gviz' ... ** R ** data ** inst ** preparing package for lazy loading Error in loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = vI[[j]]) : there is no package called 'foreign' ERROR: lazy loading failed for package 'Gviz' * removing '/<>/debian/r-bioc-gviz/usr/lib/R/site-library/Gviz' dh_auto_install: R CMD INSTALL -l /<>/debian/r-bioc-gviz/usr/lib/R/site-library --clean . --built-timestamp='Thu, 27 Oct 2016 15:44:42 +0200' returned exit code 1 debian/rules:4: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 25 dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit status 2 Seems like a missing build-depends. Thanks. --- End Message --- --- Begin Message --- Source: r-bioc-gviz Source-Version: 1.18.0-2 We believe that the bug you reported is fixed in the latest version of r-bioc-gviz, 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 842...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-bioc-gviz package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 02 Nov 2016 12:10:06 +0100 Source: r-bioc-gviz Binary: r-bioc-gviz Architecture: source all Version: 1.18.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: r-bioc-gviz - Plotting data and annotation information along genomic coordinate Closes: 842915 Changes: r-bioc-gviz (1.18.0-2) unstable; urgency=medium . * Build-Depends: r-cran-foreign, r-cran-nnet Closes: #842915 Checksums-Sha1: 127972b6d483c1a9aa7d97d97df9ac2edec45f31 2149 r-bioc-gviz_1.18.0-2.dsc 4bc84869f3eb883882b2514e41375db0b0e415dd 6024 r-bioc-gviz_1.18.0-2.debian.tar.xz 5d25c4f2657e0cd8af515866688e894a5bc41fce 4294240 r-bioc-gviz_1.18.0-2_all.deb Checksums-Sha256: 2569e21f61ee8130c654224f707201f5e65f25ef0a47e578e654571e93160f87 2149 r-bioc-gviz_1.18.0-2.dsc 2e48c9b948abef69540cde337caf45b32bb5bd71be2eb3437e4a455b69e853aa 6024 r-bioc-gviz_1.18.0-2.debian.tar.xz b3331858eae79ab8ac328264026d1b5afabba424f0e8c5d71ca9fa6364f5bafe 4294240 r-bioc-gviz_1.18.0-2_all.deb Files: c46929ff05ca5c517661676c56dc3c52 2149 gnu-r optional r-bioc-gviz_1.18.0-2.dsc ab501ccb2e390d3147854d57deb081b4 6024 gnu-r optional r-bioc-gviz_1.18.0-2.debian.tar.xz 9cb7d9317c2dada5c5eb81e215337c98 4294240 gnu-r optional r-bioc-gviz_1.18.0-2_all.deb -BEGIN PGP SIGNATURE- Ve
Bug#842713: marked as done (ocamlbuild: FTBFS: E: Error: unit Ocamlbuild exported in ocamlbuild but already exported by ocaml-nox/ocaml-base-nox v4.02.3-7+b1)
Your message dated Wed, 02 Nov 2016 12:48:55 + with message-id and subject line Bug#842713: fixed in ocamlbuild 0.9.3-3 has caused the Debian Bug report #842713, regarding ocamlbuild: FTBFS: E: Error: unit Ocamlbuild exported in ocamlbuild but already exported by ocaml-nox/ocaml-base-nox v4.02.3-7+b1 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.) -- 842713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocamlbuild Version: 0.9.3-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, ocamlbuild fails to build from source in experimental/amd64: […] dh_strip dh_makeshlibs dh_shlibdeps dh_installdeb dh_ocaml E: Error: unit Ocamlbuild exported in ocamlbuild but already exported by ocaml-nox/ocaml-base-nox v4.02.3-7+b1 E: Error running /usr/bin/ocaml-md5sums --package ocamlbuild dep < debian/ocamlbuild.olist.debhelper at /usr/bin/dh_ocaml line 487. debian/rules:8: recipe for target 'binary' failed make: *** [binary] Error 255 […] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ocamlbuild.0.9.3-2.experimental.amd64.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Source: ocamlbuild Source-Version: 0.9.3-3 We believe that the bug you reported is fixed in the latest version of ocamlbuild, 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 842...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ximin Luo (supplier of updated ocamlbuild package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 02 Nov 2016 13:28:14 +0100 Source: ocamlbuild Binary: ocamlbuild Architecture: source Version: 0.9.3-3 Distribution: experimental Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Ximin Luo Description: ocamlbuild - Build tool for building OCaml library and programs Closes: 842713 Changes: ocamlbuild (0.9.3-3) experimental; urgency=medium . * Force a rebuild against OCaml 4.03.0 on all architectures. (Closes: #842713) Checksums-Sha1: 3bd7dab674847910f311b9c6dc9ccc3c77efac3f 2009 ocamlbuild_0.9.3-3.dsc e3cd612f28d8593f07233f383470fc9a1672af90 3016 ocamlbuild_0.9.3-3.debian.tar.xz Checksums-Sha256: 2e296adf849711bf901a4c53304ed3803cc2eb15e86a6a2ecb81a0c667112b51 2009 ocamlbuild_0.9.3-3.dsc c5083522a0ad2829899b2aebe2e60b366e1abbdf6bc99657734f8e0a971b89ca 3016 ocamlbuild_0.9.3-3.debian.tar.xz Files: 2c54d493ee1a3cf272bea4f601eeb907 2009 ocaml optional ocamlbuild_0.9.3-3.dsc 6b9a103be6c328252cc9a3d5cca42609 3016 ocaml optional ocamlbuild_0.9.3-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIyBAEBCgAcBQJYGdwkFRxpbmZpbml0eTBAZGViaWFuLm9yZwAKCRCGDe87j2UL eTuKD/9X2Cxx7BNTAAQpGIYWo3Xh68B7rjnX343SaX2ypkIWeL6JN+dh/Ecfuf2F Lh9PVnXtBR13ZcJe7sex5Ko9F4haxXL21IyRllY2IDklF6ISvZkj2/7pUaSHykT9 1FFobzhrzAxe3oQI7X1iL1vKM5FgpTCVc3uxB+WmnEXLINW+pJ4zbr8FfiUYhkKa lzrkC8P7Cf1k0Gl9ZISxiSLRqGzFIYusQf31P3AStBrVqbZ39IGgFSRFAucrHuSV QDaCom8WqMoLAWsrBfL1SJyMveEnhHWt8+ZqhzHEHwzWCNyxUZ+C4CwD0Q6AsMa1 PQTR2bV7Unm0580+sfn+UT71MIzDTpzz1t1d8EhUZnrH7AHvgoKB9gPrdN9sovPT cB1cuIyr1By6eRqooWi0+V4F9vbt+INH+x0F0LqgzjKBmDQB4HcDbR39yntCED56 +cUDWH914X2DkbFMWYlykhLqX/QCYNeEvTzgy90vgv1fhXdtZzXqmkWKcAX9burg h4iewnjeelOasQwnqKVZ4ZTGmvsoJxtqauMQRdNG/F/hE6wzpZHfagTKT1+eVbg0 Rf2+iVXtFxdp2Uu0qdIeBZzNtRzfagwDbik3oil5FeglJpYTPqHY18iTvfv4w13/ 8Ft1+RDiVV+CP/rymx6sU7s4Xefj7ktZwTgaRFh3g4/qdaBIvA== =yIgI -END PGP SIGNATURE End Message ---
Bug#831833: Tagged as fixed-upstream - do you intend to upload?
Hi Charles, On Wed, Nov 02, 2016 at 09:03:45PM +0900, Charles Plessy wrote: > > you have set #831833 as fixed-upstream at 20 Jul 2016. Do you intend to > > upload the fix to the Debian archive? > > I was hoping that Upstream would make a new release with the fix :( > > So one would need to check if the following commit would be enough as a > patch... > > https://github.com/arq5x/bedtools2/commit/be2633d4951328264611e4cabc65e12fa8fef1cd > > I am not sure if I can do it in the short term... Everybody is welcome to be > faster than me :) Since I feel not able to do the proper tests I'd prefer if you could do this yourself. I do not think that it needs to be fixed in the next couple of days fixing this in November would be a good idea to have sufficient testing before the freeze. Kind regards Andreas. -- http://fam-tille.de
Bug#842751: marked as done (fim: FTBFS on several architectures)
Your message dated Wed, 02 Nov 2016 12:33:36 + with message-id and subject line Bug#842751: fixed in fim 0.5~rc2-3 has caused the Debian Bug report #842751, regarding fim: FTBFS on several architectures 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.) -- 842751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fim Version: 0.5~rc2-2 Severity: serious Your package still fails to build on several architectures. See the logs at https://buildd.debian.org/status/package.php?p=fim Emilio -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: fim Source-Version: 0.5~rc2-3 We believe that the bug you reported is fixed in the latest version of fim, 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 842...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rafael Laboissiere (supplier of updated fim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 02 Nov 2016 09:48:49 -0200 Source: fim Binary: fim Architecture: source amd64 Version: 0.5~rc2-3 Distribution: unstable Urgency: medium Maintainer: Michele Martone Changed-By: Rafael Laboissiere Description: fim- scriptable frame buffer and ascii art image viewer Closes: 842751 Changes: fim (0.5~rc2-3) unstable; urgency=medium . * d/p/allow-concurrent-bison.patch: New patch (Closes: 842751) Checksums-Sha1: 922b51729f78a128afbe6decc41517689297611d 2008 fim_0.5~rc2-3.dsc 5bc838afdde7677c6798a58f17ae83b75cb83db5 7176 fim_0.5~rc2-3.debian.tar.xz 8b667926f727b444e0b6a5318a6a317b694582c6 2787024 fim-dbgsym_0.5~rc2-3_amd64.deb 1b58dcc7d2ad3c402b1c5a48b91a4fc02cc3f2c0 394798 fim_0.5~rc2-3_amd64.deb Checksums-Sha256: cd77b4e65790dbdd9d1e5bcf6d5909dfa202c0c13b8b591a7d8f1f852648b09c 2008 fim_0.5~rc2-3.dsc cf402acdfb7fa38366dda91a729afa8a3845f579ecfa766b5bd3c29703145935 7176 fim_0.5~rc2-3.debian.tar.xz 141493576ad066f8b129ecd056c76c13b569e0b6bce6251b2de95c305976e7bb 2787024 fim-dbgsym_0.5~rc2-3_amd64.deb 38c459dad6a47189f01f634b82d1179ac7931dab50a99e5d4be471219cff75f8 394798 fim_0.5~rc2-3_amd64.deb Files: 695a201acb6a78b50f5786e7e1f261c2 2008 graphics extra fim_0.5~rc2-3.dsc cf4c0d714c914f3e0849365b34252e16 7176 graphics extra fim_0.5~rc2-3.debian.tar.xz f9c4c1680097c9431d9cf315e13d4983 2787024 debug extra fim-dbgsym_0.5~rc2-3_amd64.deb 7ebce6820292a9038357ce43c288ac4d 394798 graphics extra fim_0.5~rc2-3_amd64.deb -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYGddpAAoJECEkqhmDeFyQFLwP/j1wgzwZAgoH7d/Jp++DEjlI i2n0+7EBhekm08PoZCzVteUzYl5o36dvJYfNxYskeyqLKvlm+zC1rHIC3HMKmRbZ 6x/jnV7J12Hy3yaKzuV+1vFEck20zDM0pS2v2sY3803r+WtLB+7mGRash6y+lywg 1hiNQF8Hr2//8gr8MIETba90pjVwhujunYAPUeHB99tED2b882LQeCgIzRnd7YDJ SDuvnso4c0oM0ts5TABQcaJv2Wi+ZrLbHSNcAWb3Vd5cNal1Bh9vo31IhIBjSfSS +6jZlqUUCYDeS+YIB5DuxwlkUo+GL78dJlLO6mXAX7POnfCjRYdsl+AUm2xUTKrY eDrgXyQU0BwGy6oBPP6ZXfvnyT1o+HdwgiP8kf6DrIFmQz5tynv5lO52lxTVsrj2 v3RwvRuBJEgNTZV6BFq4iinUxDbiYe9DOtpeD6MQE0kglSen56ybgYtGkVic4c3H NobGqwq2m2L25Fircf93efppL9vKdJcXpH4BpjcX+WNVgPrGvaqR8aZV8NngUs8Y 7FbSMyjzmw77DIGh9s3CDx/TRwjJE3+DOWJ++0ZvbDPFiulb3plnMPo3V4157TmU xWY0Ud+2wka0hlrXgJUQGiBQ2ERv0IgRqD2j3MS6KIC1WQ6Ih7yA0hNMOEuW5Nh/ oy58rv5yV7HQTcpMGPIc =MzrQ -END PGP SIGNATURE End Message ---
