On 27 Jun 2017, at 9:47 PM, Ian Campbell wrote:
> On Tue, 2017-06-27 at 07:21 -0400, Antoine Beaupré wrote:
>> On 2017-06-27 08:11:03, Ian Campbell wrote:
>>> If you want to be pointlessly pedantic about it then your bug is that
>>> your maintainer script in debian/ calls a program which sleeps,
On 30 Mar 2017, at 3:54 AM, Michael Stapelberg wrote:
>
> Hi Tim,
>
> "Potter, Tim" writes:
>> Hi Ricardo. Thanks for the bug report. I messed up by uploading some of
>> the Docker 1.13
>> dependencies to unstable instead of experimental - my apologi
On 16 Mar 2017, at 2:07 AM, Sjoerd Simons wrote:
>
> Source: etcd
> Version: 3.1.2+dfsg
> Severity: serious
> Justification: fails to build from source
>
> Hey,
>
> When trying to build etcd i get:
[...]
> debian/rules:9: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [overri
Hi Roland. I messed up by uploading containerd (as well as runc and
libnetwork) to unstable
while uploading the matching Docker package to experimental.
If you downgrade to the original containerd, runc and libnetwork you should see
the
problem disappear. I've done a new upload adding Break li
On 24 Feb 2017, at 12:25 AM, Ricardo Sateler wrote:
>
> Package: containerd
> Version: 0.2.3~git20161117.78.03e5862~ds1-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> After upgrading containerd from 0.2.1~ds1-3 to
> 0.2.3~git20161117.78.03e5862~ds1-1, doc
On 18 Feb 2017, at 5:33 AM, Evgeni Golov wrote:
>
> Hi Tim,
>
> On Wed, Feb 15, 2017 at 10:52:22PM +0000, Potter, Tim wrote:
>>> I can reproduce this. Downgrading to 0.1.1+dfsg1-2 fixed this for me.
>>
>> Hi everyone. This upload is part of updated build d
On 16 Feb 2017, at 9:56 AM, Chris Lamb wrote:
>
> Potter, Tim wrote:
>
>> On 16 Feb 2017, at 9:06 AM, Chris Lamb wrote:
>
>> Hi everyone. This upload is part of updated build dependencies for Docker
>> 1.13.0.
>> Currently the pipeline is stalled whi
On 16 Feb 2017, at 9:06 AM, Chris Lamb wrote:
>
> Felipe Sateler wrote:
>
>> Cannot start service web: rpc error: code = 2 desc
>> = "oci runtime error: flag provided but not defined: -bundle"
>
> I can reproduce this. Downgrading to 0.1.1+dfsg1-2 fixed this for me.
Hi everyone. This upload i
> On 14 Dec 2016, at 4:38 AM, Hilko Bengen wrote:
>
> Hi Tim,
>
>> I think I'll probably ask the FTP Masters very nicely to remove the
>> new package rather than mess with the reverse dependencies.
>
> Keep in mind that golang-go-flags-dev was released with jessie. I am not
> entirely sure if A
Hi Hilko. Hey thanks for the bug report. Looks like it's totally my fault for
not double checking that this package was not already in Debian under an old
name.
I think I'll probably ask the FTP Masters very nicely to remove the new package
rather than mess with the reverse dependencies.
Re
On 29 Aug 2016, at 8:59 PM, Luca BRUNO wrote:
>
> 1.13.0+dfsg-1 has been built without issues on i386:
> https://buildd.debian.org/status/fetch.php?pkg=rkt&arch=i386&ver=1.13.0%2Bdfsg-1&stamp=1472188080
>
> ppc64 and s390x are in progress upstream and should hopefully
> be back in the next relea
This was fixed by a recent upload of version 0.0~git20160816.0.d69c40b-1 but
this bug
wasn't closed in d/changelog.
Tim.
On 28 Aug 2016, at 8:24 PM, Lucas Nussbaum wrote:
>
> Source: golang-x-text
> Version: 0.0~git20160606.0.a4d77b4-1
> Severity: serious
> Tags: stretch sid
> User: debian...
On 2 Aug 2016, at 4:22 AM, Tianon Gravi wrote:
>
> On 31 July 2016 at 20:20, Potter, Tim (HPE Linux Support)
> wrote:
>> Patch attached to fix this, but it's a bit icky (and has been replaced by a
>> shell out to call
>> getent in a later version.
>
> V
On 20 Jul 2016, at 6:35 PM, Chris Lamb wrote:
>
>> My _hunch_ is that whatever you're using to build (pbuilder perhaps?)
>> is running as your user ("lamby") but not including "/etc/passwd" from
>> your host
>
> It is running as my user and /etc/passwd includes:
>
> lamby:x:1000:1000:,,,:/home
Rebuilds cleanly now so closing this bug.
Tim.
signature.asc
Description: Message signed with OpenPGP using GPGMail
I've just pushed a patch for this to the package repository on alioth.
Tim.
signature.asc
Description: Message signed with OpenPGP using GPGMail
This FTBFS should be fixed by the upload of the newer version in #812838.
Tim.
signature.asc
Description: Message signed with OpenPGP using GPGMail
On 6 Apr 2016, at 4:07 PM, Potter, Tim (HPE Linux Support)
wrote:
>
> On 31 Mar 2016, at 11:14 PM, Chris Lamb wrote:
>
> [...]
>
>>dh_auto_test -O--buildsystem=golang
>> go test -v github.com/armon/gomdb
>> === RUN TestEnvOpen
>> -
On 31 Mar 2016, at 11:14 PM, Chris Lamb wrote:
[...]
> dh_auto_test -O--buildsystem=golang
> go test -v github.com/armon/gomdb
> === RUN TestEnvOpen
> --- PASS: TestEnvOpen (0.00s)
> === RUN TestEnvCopy
> --- PASS: TestEnvCopy (0.00s)
> env_test.go:67: Env path: /tmp/mdb_
I’m trying to rebuild this package from source and it’s also failing, but I get
a
different set of errors. Perhaps this will shed some light on what’s happening
to someone:
Running tests for ruby2.2 using debian/ruby-tests.rake ...
RUBYLIB=/Source/pkg-ruby/ruby-patron/debian/ruby-patron/usr/lib/
On 30 Jul 2015, at 5:08 pm, Michael Stapelberg wrote:
> On Thu, Jul 30, 2015 at 6:05 AM, Potter, Tim (Cloud Services)
> wrote:
> On 28 Jul 2015, at 5:14 pm, Michael Stapelberg wrote:
> >
> > So, yes, if you could work with upstream on a proper solution and then we
>
On 28 Jul 2015, at 5:14 pm, Michael Stapelberg wrote:
>
> So, yes, if you could work with upstream on a proper solution and then we
> could just package a new upstream snapshot, that’d be great.
I’ve just posted two pull requests on the upstream project. One to fix the
occasional test failure
upstream on a proper solution and then we
> could just package a new upstream snapshot, that’d be great.
OK - I’ll work on that then.
Tim.
>
> On Tue, Jul 28, 2015 at 3:02 AM, Potter, Tim (Cloud Services)
> wrote:
> On 28 Jul 2015, at 6:35 am, solo-debianb...@goeswhere.com wrot
On 28 Jul 2015, at 6:35 am, solo-debianb...@goeswhere.com wrote:
>
> On Mon, Jul 27, 2015 at 07:26:10PM +0200, Michael Stapelberg wrote:
>> control: tags -1 + unreproducible
>>
>> Chris, was this an issue on your end? Or am I misinterpreting something?
>>
>
> The problem seems to have gone away
On 26 Jul 2015, at 12:39 am, Philipp Marek wrote:
>
> Hello Tim,
>
> I'm sorry about the delay,
>
>> Hi Phillip. I noticed that you committed this fix to the
>> branches/fsvs-1.2.x but haven’t released a new version of fsvs
>> containing it.
>> Would you be interested in cutting a 1.2.6 releas
On Thu, 12 Feb 2015 12:05:00 +0100 Philipp Marek wrote:
> (errors) fixed in r2472, builds with GCC 5.
Hi Phillip. I noticed that you committed this fix to the branches/fsvs-1.2.x
but haven’t released a new version of fsvs containing it.
Would you be interested in cutting a 1.2.6 release conta
Hi Steve. Looks like this bug is no longer reproducible in one of the previous
two uploads that Keith made.
I wasn’t able to reproduce on my gcc5 test system so was wondering if you could
close out this bug.
Regards,
Tim.
smime.p7s
Description: S/MIME cryptographic signature
tags 777917 + patch
thanks
Hi there. Here’s a small patch to fix the FTBS with gcc5. It simply adds
-std=gnu89 to CFLAGS in debian/rules which is picked up by autoconf.
Regards,
Tim.
777917-gcc5-fixes.patch
Description: Binary data
smime.p7s
Description: S/MIME cryptographic signature
tags 777916 + patch
thanks
Hi there. Here’s a quick patch to fix the gcc5 build failures for the ioapps
package. Since upstream appears to be unmaintained and doesn’t use autoconf
I’m proposing a patch to modify the Makefile directly.
Patch is attached which appends “-std=gnu89” flag to the C
tags 488159 + patch
thanks
Ironically, the code that checks for the C99 “restrict” keyword does not
compile because “restrict” cannot be used as a variable name. Attached is a
patch that fixes this by renaming the local variable in this case.
The maintainer has signed up for LowThresholdNMU so
As mentioned by Matthias think error above is fixed by recompiling leveldb. I
added a block on 791086 to reflect this.
My build procedure is:
- install boost packages from experimental
$ apt-get install -t experimental libboost-dev libboost-program-options-dev
libboost-system-dev libboost-thr
Control: notfound -1 0.94.2-1
Control: tags -1 + patch
this works with ceph from experimental. The link failure goes away once leveldb
is rebuilt using GCC 5.
smime.p7s
Description: S/MIME cryptographic signature
I don’t understand the original failure, but I just rebuilt the package using
an up-to-date version of unstable the latest version of boost installed from
experimental as it has been rebuilt with gcc5.
The next error I get is during running the unit tests:
g++ -DHAVE_CONFIG_H -I. -D__CEPH__ -D
tags 778164 + patch
thanks
Hi there. Attached is a small patch to fix the build under gcc5. The
visibility of one of the functions in the yacc grammar is increased so the
program links without error now.
Regards,
Tim.
778164-gcc5-fixes.patch
Description: Binary data
smime.p7s
Descriptio
Hi - sorry I think I got a bit carried away and closed this bug. Apologies if
I overstepped.
Regards,
Tim.
smime.p7s
Description: S/MIME cryptographic signature
close 87 5.1.1-1
thanks
Tried to reproduce with the latest version and it builds fine under gcc5 now.
smime.p7s
Description: S/MIME cryptographic signature
tags 777849 + patch
thanks
Hi there. I’ve made a small patch to debian/rules for the fhist package to
build correctly using gcc5. I’ve also tested with gcc 4.9.2 and there are no
adverse effects.
Regards,
Tim.
777849-gcc5-ftbfs.patch
Description: Binary data
smime.p7s
Description: S/MI
tags 777819 + patch
thanks
Hi there. I’ve made a partial fix for building clementine under GCC5. The
patch is attached and it’s a simple rearrangement of operands to prevent an
error/bug due to operator precedence. The fix has already made it into the
master branch of upstream.
This doesn’t
tags 778024 + patch
thanks
Hi there. Here’s a quick patch to fix the build under g++-5. Not sure whether
this should be an upstream patch or one in debian/patches.
Regards,
Tim.
778024-gcc5.patch
Description: Binary data
smime.p7s
Description: S/MIME cryptographic signature
On Fri, 09 Jan 2015 12:09:46 -0800 Matt Taggart wrote:
> Most of the links on
> https://security-tracker.debian.org/tracker/CVE-2014-2330
> https://security-tracker.debian.org/tracker/CVE-2014-2331
>
> don't give any info, the RedHat link is for the full set of things and
> it's not clear to me
On 6/03/15 6:37 AM, "Andreas Beckmann" wrote:
>On 2015-03-05 04:21, Debian Bug Tracking System wrote:
>>* Change dependency on libconstantine-java to Conflicts, from
>> Breaks. (Closes: #779112).
>
>No. Breaks should have been sufficient, but you are still missing a
>Replaces.
>
> Selec
Hi everyone. Can this bug be closed out? I don't think marking it as
pending is good enough to fix auto-removed build-dependencies on
ruby-faraday.
I've checked the dependent bug mentioned, 770728, and the two packages
mentioned (ruby-em-hiredis and ruby-em-synchrony) transitioned to testing
in
Hi everyone. I'm nervously following along with this bug since its
presence is threatening the removal of a couple of dozen other packages as
you can all probably see from the QA page.
In the spirit of not hassling anyone (-: I was curious whether there was a
plan to close this out? It sounds li
On 2/09/14 2:19 AM, "tony mancill" wrote:
>>> CVE-2014-3120[0]:
>>> | The default configuration in Elasticsearch before 1.2 enables dynamic
>>> | scripting, which allows remote attackers to execute arbitrary MVEL
>>> | expressions and Java code via the source parameter to _search. NOTE:
>>> | th
On 30/08/14 5:37 AM, "Salvatore Bonaccorso" wrote:
>Source: elasticsearch
>Severity: grave
>Tags: security upstream fixed-upstream
>
>Hi Hilko,
>
>I see elasticsearch entered unstable now. Some time ago the following
>vulnerability was published for elasticsearch.
>
>CVE-2014-3120[0]:
>| The defa
45 matches
Mail list logo