Processing commands for cont...@bugs.debian.org:
> tags 835278 + fixed-in-experimental
Bug #835278 {Done: Dmitry Bogatov } [runit] [runit] fails to
upgrade cleanly
Bug #835903 {Done: Dmitry Bogatov } [runit] runit: upgrade
failed
Added tag(s) fixed-in-experimental.
Added tag(s) fixed-in-experime
Package: release.debian.org
Severity: critical
Tags: patch
User: release.debian@packages.debian.org
Usertags: pu
The attached patch fixes bug #817231 in the rabbitvcs package. This is
classified as a critical bug on the grounds that it can cause serious data loss
(e.g. loss of entire home fo
❦ 3 septembre 2016 23:37 CEST, Chris Lamb :
>> If your bug was wishlist, I would just ignore it. It is severity serious
>> and I have to handle it. Maybe it is legitimate. Maybe not.
>
> Oh! I thought we were discussing whether it was a bug at all — hence the
> time you spent addressing whether
❦ 4 septembre 2016 01:03 CEST, Santiago Vila :
>> [...] information leak [...]
>
> This is not just a privacy issue but also a reproducibility issue.
>
> It is bad that a package leaks information to the external world,
> but it is even worse, I would say, that information from the outside
> wo
Just found out about Krita, and thinking about giving it a try...
Does the fact that the latest stable version of Krita upstream (3.x) has now
split from Calligra have any bearing
on this bug?
I.e. instead of trying to fix these issues, we should just start from a clean
slate with Calligra?
B
Can we get some traction on this issue. I'm having the exact same problem.
However, I don't want to delete my SQLITE databases because they contain
any additional annotations and tags that I've added. I would expect a
software version upgrade to handle this transparently.
- Garrett
On Sat, 3 Sep 2016, Vincent Bernat wrote:
> [...] information leak [...]
This is not just a privacy issue but also a reproducibility issue.
It is bad that a package leaks information to the external world,
but it is even worse, I would say, that information from the outside
world is being used i
Your message dated Sun, 04 Sep 2016 01:00:49 +0200
with message-id <147294364988.953.6502748623064315...@auryn.jones.dk>
and subject line Re: Bug#835667: d-shlibs: FTBFS in testing (broken by new
shellcheck)
has caused the Debian Bug report #835667,
regarding d-shlibs: FTBFS in testing (broken by
Processing control commands:
> tags 835612 + fixed-upstream pending
Bug #835612 [src:ikiwiki] ikiwiki: FTBFS in testing (broken by new git)
Added tag(s) fixed-upstream and pending.
--
835612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835612
Debian Bug Tracking System
Contact ow...@bugs.de
Control: tags 835612 + fixed-upstream pending
On Sat, 27 Aug 2016 at 15:34:30 +, Santiago Vila wrote:
> This used to build ok, so this failure seems related to git 2.9.3,
> which is in testing since a few days.
This is reproducible in an upstream build on current unstable, and should
now be f
Your message dated Sun, 04 Sep 2016 00:53:45 +0200
with message-id <147294322588.953.869991314541340...@auryn.jones.dk>
and subject line Re: [Pkg-javascript-devel] Bug#719382: node-stringprep: FTBFS:
/bin/sh: 1: node-waf: not found
has caused the Debian Bug report #719382,
regarding node-stringpre
Package: gnupg
Version: 2.1.15-2
Severity: grave
A simple verification of a inlined signed file leaves the agent running.
This makes it impossible to clean up the system properly. This is for
example used by cdebootstrap.
As it is inline signed, it is not possible to use gpgv, which can't
decode
Your message dated Sat, 03 Sep 2016 22:31:17 +
with message-id
and subject line Bug#835278: fixed in runit 2.1.2-7
has caused the Debian Bug report #835278,
regarding [runit] fails to upgrade cleanly
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 03 Sep 2016 22:32:10 +
with message-id
and subject line Bug#817038: fixed in transifex-client 0.11.1+git15~g655c5e9-1.1
has caused the Debian Bug report #817038,
regarding transifex-client: Use python-six instead of the embedded version of
python-urllib3
to be marked a
Your message dated Sat, 03 Sep 2016 22:31:17 +
with message-id
and subject line Bug#835278: fixed in runit 2.1.2-7
has caused the Debian Bug report #835278,
regarding runit: upgrade failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Sat, 03 Sep 2016 22:29:51 +
with message-id
and subject line Bug#835413: fixed in pygobject 3.21.91-2
has caused the Debian Bug report #835413,
regarding pygobject: wrong enum to hash conversion on 64-bit big endian
to be marked as done.
This means that you claim that the p
On 03/09/16 14:15, Graham Inggs wrote:
A wild stab in the dark: don't we need to binNMU lazarus before we can
build packages with it?
I'd say yes, in that build log it looks like it's lazbuild which is
crashing. So yes a binnmu of lazarus seems the next step.
Then, don't we need to binNMU e
Your message dated Sat, 03 Sep 2016 22:27:59 +
with message-id
and subject line Bug#828715: fixed in graphite-api 1.1.3-2
has caused the Debian Bug report #828715,
regarding graphite-api: FTBFS: ImportError: No module named 'sphinx_rtd_theme'
to be marked as done.
This means that you claim th
Your message dated Sat, 03 Sep 2016 22:25:02 +
with message-id
and subject line Bug#835411: fixed in eigen3 3.3~beta2-2
has caused the Debian Bug report #835411,
regarding eigen3: causes FTBFS in other packages
to be marked as done.
This means that you claim that the problem has been dealt wi
> If your bug was wishlist, I would just ignore it. It is severity serious
> and I have to handle it. Maybe it is legitimate. Maybe not.
Oh! I thought we were discussing whether it was a bug at all — hence the
time you spent addressing whether privacy leaking is valuable — not the
severity of the
❦ 3 septembre 2016 21:22 CEST, Chris Lamb :
>> The policy says "may not". I am not a native speaker, but for me, this
>> is not like "must not". Since you are a native speaker, I think you know
>> better: is it optional or not?
>
> May I suggest an alternative approach…? We have two cases here:
Hi all,
it looks like this test failure is the random case. I was not
able to reproduce it building it 2 times on barriere.debian.org.
I propose to reduce the bug severity to "normal".
Thanks
Anton
On September 3, 2016 4:01:16 PM EDT, Santiago Vila wrote:
>Package: src:nipy
>Version: 0.4.0+git26-gf8d3149-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 fai
Package: src:nipy
Version: 0.4.0+git26-gf8d3149-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:
--
Source: snd
Version: 16.7-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,
snd fails to build from source in unstable/amd64:
[..]
make: [
Package: src:ruby-concurrent
Version: 1.0.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:
--
Hi Vincent,
> The policy says "may not". I am not a native speaker, but for me, this
> is not like "must not". Since you are a native speaker, I think you know
> better: is it optional or not?
May I suggest an alternative approach…? We have two cases here:
a) Debian Policy states it is a bug i
Processing commands for cont...@bugs.debian.org:
> tags 833905 +fixed-upstream
Bug #833905 [src:dimbl] dimbl: FTBFS: include/dimbl/DimProcs.h:37:29: error:
expected ')' before '&' token
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
tags 833905 +fixed-upstream
thanks
On Wed, Aug 10, 2016 at 08:45:57AM +0100, Chris Lamb wrote:
>...
> make[3]: Entering directory
> '/home/lamby/temp/cdt.20160810084053.cX2EXg73ka.dimbl/dimbl-0.12/src'
> g++ -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2
> -g -O2
>
On Mon, Aug 08, 2016 at 03:41:19PM +, Mattia Rizzolo wrote:
> source: undertaker
> version: 1.6.1-2
> severity: serious
>
> Dear maintainer,
>
> your package failed to build during the rebuilds for the boost1.61
> transition, using gcc-6 as a compiler.
> you can see the failed build logs at:
Processing commands for cont...@bugs.debian.org:
> severity 834688 normal
Bug #834688 [java-package] java-package: Fails to create package for JDK 8u102
Severity set to 'normal' from 'grave'
> tags 834688 + moreinfo
Bug #834688 [java-package] java-package: Fails to create package for JDK 8u102
Add
Your message dated Sat, 03 Sep 2016 18:21:54 +
with message-id
and subject line Bug#831914: fixed in gui-apt-key 0.4-2.2
has caused the Debian Bug report #831914,
regarding gui-apt-key: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error:
binary build with no binary artifacts found; canno
Your message dated Sat, 03 Sep 2016 18:17:11 +
with message-id
and subject line Bug#831813: fixed in nullmailer 1:1.13-1+deb8u1
has caused the Debian Bug report #831813,
regarding nullmailer leaks sensitive data through debconf
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 03 Sep 2016 18:17:12 +
with message-id
and subject line Bug#827411: fixed in piuparts 0.62+deb8u1
has caused the Debian Bug report #827411,
regarding piuparts: FTBFS on jessie: 'wheezy' != 'squeeze'
to be marked as done.
This means that you claim that the problem has b
Control: found -1 4.2.13-1
> request-tracker4 (4.2.13-1) unstable; urgency=medium
>* Fix FTBFS with gpg 2.1 by no longer explicitly configuring the
> path to gpg (Closes: #835536)
This doesn't seem to have worked: 4.2.13-1 failed on the 'all' buildd
with lots of
# Tests were run but n
Processing control commands:
> found -1 4.2.13-1
Bug #835536 {Done: Dominic Hargreaves } [src:request-tracker4]
request-tracker4: FTBFS with gnupg 2.1
The source 'request-tracker4' and version '4.2.13-1' do not appear to match any
binary packages
Marked as found in versions request-tracker4/4.2.
Processing commands for cont...@bugs.debian.org:
> fixed 836377 0.10.2
Bug #836377 {Done: Ben Finney } [dput] build system
terminal locale not inherited by build programs
Marked as fixed in versions dput/0.10.2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
836
On 2016-09-03 11:07, Rob Browning wrote:
> Aurelien Jarno writes:
>
> > glibc 2.24 is now in unstable, so I am upgrading the severity of this
> > bug to serious. If you don't have time to fix this bug, I can do a
> > non-maintainer upload with the patch which is in the bug log.
>
> I've been wor
Your message dated Sat, 03 Sep 2016 16:32:11 +
with message-id
and subject line Bug#831399: fixed in python-pyotp 2.1.1-2
has caused the Debian Bug report #831399,
regarding FTBFS on armel and i386: Test values out of range for platform time_t
on various architectures
to be marked as done.
T
Your message dated Sat, 03 Sep 2016 16:26:57 +
with message-id
and subject line Bug#835894: fixed in gnustep-gui 0.25.0-4
has caused the Debian Bug report #835894,
regarding missing dependency on gnustep-back
to be marked as done.
This means that you claim that the problem has been dealt with
Aurelien Jarno writes:
> glibc 2.24 is now in unstable, so I am upgrading the severity of this
> bug to serious. If you don't have time to fix this bug, I can do a
> non-maintainer upload with the patch which is in the bug log.
I've been working on a release, and I think I should have time to fi
Hey.
Not really sure whether these changes here makes things so much better:
1) It's still al just Wants, no Requires... i.e. if netfilter rules
loading fails for whichever reason, the boot process will continue just
normally, with networking and any daemons, that possibly require
netfilter for t
tags 830088 + pending
tags 830099 + pending
owner 830099 !
owner 830088 !
thanks
Hi,
Back in the game! \o/
Thanks for this bugreport, I take a look on this one.
Cheers,
signature.asc
Description: PGP signature
Processing commands for cont...@bugs.debian.org:
> tags 830088 + pending
Bug #830088 [ruby-em-socksify] Could not find 'em-socksify' (>= 0.3)
Added tag(s) pending.
> tags 830099 + pending
Bug #830099 [ruby-em-http-request] Could not find 'em-socksify' (>= 0.3)
Added tag(s) pending.
> owner 830099
Your message dated Sat, 03 Sep 2016 15:36:16 +
with message-id
and subject line Bug#835236: Removed package(s) from unstable
has caused the Debian Bug report #828927,
regarding strigi: FTBFS with gcc-6 and glibc 2.23
to be marked as done.
This means that you claim that the problem has been de
Your message dated Sat, 03 Sep 2016 15:35:40 +
with message-id
and subject line Bug#836085: Removed package(s) from unstable
has caused the Debian Bug report #724520,
regarding gnupg-doc ftbfs in unstable
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 03 Sep 2016 15:35:18 +
with message-id
and subject line Bug#836161: Removed package(s) from unstable
has caused the Debian Bug report #818124,
regarding easymp3gain: FTBFS: Could not check LCL version
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 03 Sep 2016 15:35:03 +
with message-id
and subject line Bug#836178: Removed package(s) from unstable
has caused the Debian Bug report #832300,
regarding pyoperators: Non-deterministically FTBFS to unreliable timing in tests
to be marked as done.
This means that you cla
❦ 3 septembre 2016 15:46 CEST, Chris Lamb :
>> Was this MBF discussed somewhere?
>
> I don't consider it to be a MBF — I haven't been systematically working
> my way through the archive and I've really only filed a handful of bugs;
> mostly quasi-duplicates due to Sphinx stuff (which is arguabl
Package: src:quilt
Version: 0.63-3
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:
-
Package: src:barbican
Version: 1:2.0.0-5
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:
---
Package: src:glance
Version: 2:12.0.0-4
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:
Source: elog
Version: 2.9.2+2014.05.11git44800a7-2
Severity: grave
Tags: security upstream patch
Hi,
the following vulnerability was published for elog.
CVE-2016-6342[0]:
posting entry as arbitrary username by improper authentication
If you fix the vulnerability please also make sure to include
Hi Graham,
On 03-09-16 15:15, Graham Inggs wrote:
> Of course you mean s/doublecmd/ddrescueview/ there.
Indeed, duh...
> A wild stab in the dark: don't we need to binNMU lazarus before we can
> build packages with it?
Hmm, forgot about that. You are probably right.
> Then, don't we need to bin
Hi Vincent,
> Was this MBF discussed somewhere?
I don't consider it to be a MBF — I haven't been systematically working
my way through the archive and I've really only filed a handful of bugs;
mostly quasi-duplicates due to Sphinx stuff (which is arguably more a
QA thing than to do with violation
Hi Manuel,
I am the maintainer of freqtweak in Debian,
Sorry for the late response as I was busy all these days
I am taking a look at all bugs now and will come up with an upload soon.
On Thu, May 10, 2012 at 11:24 PM, Manuel A. Fernandez Montecelo
wrote:
> Source: freqtweak
> Version: 0.7.2-4
On 3 September 2016 at 13:47, Paul Gevers wrote:
> Unfortunately it doesn't seem to solve all issues. At least doublecmd
> now only FTBFS on powerpc (yes, fpc installed fine):
>
> An unhandled exception occurred at $0FE281F0:
> EAccessViolation:
> $0FE281F0
> $0FE36604
> $0FDED188
> $0FDED
forwarded 797998
https://github.com/unknown-horizons/unknown-horizons/issues/2295
thanks
Apparently unknown horizon is incompatible with Swig >= 3 and both the fife
engine and the game
itself have to be updated to the current Git master version.
I requested a new release at
https://github.com/
Processing commands for cont...@bugs.debian.org:
> forwarded 797998
> https://github.com/unknown-horizons/unknown-horizons/issues/2295
Bug #797998 [unknown-horizons] unknown-horizons: Crash shortly after start of
single player game
Set Bug forwarded-to-address to
'https://github.com/unknown-hor
Your message dated Sat, 03 Sep 2016 12:22:39 +
with message-id
and subject line Bug#836456: fixed in dput 0.10.3
has caused the Debian Bug report #836456,
regarding AttributeError: 'file' object has no attribute 'readable'
to be marked as done.
This means that you claim that the problem has b
On 03-Sep-2016, gregor herrmann wrote:
> I consider the following as RC as well:
That's quite different behaviour, so should be in a separate bug
report.
Fortunately bug#836456 already addresses that separate issue, so I'll
respond to it there.
--
\ “I was sleeping the other nig
Your message dated Sat, 3 Sep 2016 21:57:25 +1000
with message-id <20160903115724.p2jlyhvwbjrjw...@benfinney.id.au>
and subject line Re: Bug#836377: build system terminal locale not inherited by
build programs
has caused the Debian Bug report #836377,
regarding build system terminal locale not inh
Hi
Unfortunately it doesn't seem to solve all issues. At least doublecmd
now only FTBFS on powerpc (yes, fpc installed fine):
An unhandled exception occurred at $0FE281F0:
EAccessViolation:
$0FE281F0
$0FE36604
$0FDED188
$0FDED25C
See
https://buildd.debian.org/status/fetch.php?pkg=ddrescu
Package: dput
Version: 0.10.2
Severity: grave
Justification: renders package unusable
Hello,
every time I try to upload something I get the following:
> % dput local-desktop_0.83_amd64.changes
> Trying to upload package to ghedini.me
> Checking signature on .changes
> Traceback (most recent cal
❦ 9 juillet 2016 15:26 CEST, Chris Lamb :
> Source: python-asyncssh
> Version: 1.5.6-1
> Severity: serious
> Justification: Policy 4.9
> User: la...@debian.org
> Usertags: network-access
>
> Dear Maintainer,
>
> Whilst python-asyncssh builds successfully on unstable/amd64, according to
> Debian
Processing commands for cont...@bugs.debian.org:
> severity 835497 important
Bug #835497 [src:xemacs21-packages] xemacs21-packages: FTBFS with '.' removed
from perl's @INC
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.
Please contact me if you need assista
Package: src:givaro
Version: 4.0.2-2
Severity: serious
Tags: patch
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:
---
This requires a rebuild of gadap, which I've just uploaded. A fixed grads
should follow tonight.
On 1 September 2016 21:48:06 GMT+01:00, Bas Couwenberg
wrote:
>Source: grads
>Version: 2:2.1.a3-3
>Severity: serious
>Tags: upstream
>Justification: make the package in question unusable or mostly
Your message dated Sat, 03 Sep 2016 10:55:45 +
with message-id
and subject line Bug#835491: fixed in slack 1:0.15.2-9
has caused the Debian Bug report #835491,
regarding slack: FTBFS with '.' removed from perl's @INC
to be marked as done.
This means that you claim that the problem has been de
Processing commands for cont...@bugs.debian.org:
> forwarded 835241 https://github.com/pytest-dev/pytest-mock/issues/61
Bug #835241 [src:pytest-mock] pytest-mock: FTBFS against pytest 3.0.0
Set Bug forwarded-to-address to
'https://github.com/pytest-dev/pytest-mock/issues/61'.
> thanks
Stopping pr
Your message dated Sat, 03 Sep 2016 10:41:08 +
with message-id
and subject line Bug#826300: fixed in fpc 3.0.0+dfsg-8
has caused the Debian Bug report #826300,
regarding fpc: fp-compiler not installable on powerpc since glibc 2.23
to be marked as done.
This means that you claim that the probl
Package: tome
Version: 2.4~0.git.2015.12.29-1
Severity: serious
Hi,
tome needs to be rebuilt against boost 1.61. It can't be binNMUed as it's
in non-free, so please do a maintainer upload.
Thanks,
Emilio
Source: vowpal-wabbit
Version: 8.1.1-1
Severity: serious
Your package failed to build everywhere:
https://buildd.debian.org/status/package.php?p=vowpal-wabbit&suite=unstable
Emilio
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (800, 'unstable'), (700, '
Source: fcl
Version: 0.5.0-2
Severity: serious
Your package no longer builds on armel/armhf because it build-depends
on liboctomap-dev, which is unavailable there. You should either get
it built there somehow (e.g. by disabling that b-d there if possible)
or by getting your package removed from th
Hi Antonio,
Antonio Terceiro wrote:
> On Tue, Aug 18, 2015 at 06:26:06PM +0200, Christian Hofstaedtler wrote:
> > We're not going to have ruby-hpricot in stretch.
>
> ruby-hpricot has now only 2 reverse dependencies: ruby-ronn and
> ruby-fast-fs. However, the number of packages build-depending on
Hi
Yesterday, I was providing an new tarball 0.7.63 making the tests
pass. ags_functional_audio_test.c needs your soundcard
but shouldn't crash if it's not available. Further there was an issue
with $(HOME)/.gsequencer/ags.conf having jack=enabled.
Since jack support is a work in progress it is no
Hi
Yesterday, I was providing a new tarball 0.7.63 fixing the unit tests.
They should all pass for now.
Bests,
Joël
On Thu, Sep 1, 2016 at 7:10 PM, Aaron M. Ucko wrote:
> Source: gsequencer
> Version: 0.7.62-1
> Severity: serious
> Justification: fails to build from source (but built successful
On 03/09/16 03:36, peter green wrote:
On 02/09/16 23:05, Abou Al Montacir wrote:
Upstream suggests the following patch which may be temporary:
diff --git a/rtl/linux/powerpc/cprt0.as b/rtl/linux/powerpc/cprt0.as
index e237d8d..a5672e3 100644
--- a/rtl/linux/powerpc/cprt0.as
+++ b/rtl/linux/power
Processing commands for cont...@bugs.debian.org:
> block 836444 by 835411
Bug #836444 [src:shogun] shogun: FTBFS with eigen3 3.3~beta2-1
836444 was not blocked by any bugs.
836444 was not blocking any bugs.
Added blocking bug(s) of 836444: 835411
> thanks
Stopping processing here.
Please contact
Source: shogun
Version: 3.2.0-7.3
Severity: serious
Along with ceres-solver and opensurgsim, shogun FTBFS with eigen3
3.3~beta2-1, however they all build fine with 3.3~beta1-2.
Shogun also builds fine with eigen3 3.3~beta2-1 including the patch
mentioned by Philipp [1].
In both of the above cas
Hi Otto,
On Sat, Sep 03, 2016 at 09:51:02AM +0300, Otto Kekäläinen wrote:
> The MariaDB 10.0.26 PowerPC build failure regression was identified
> and fixed in commit
> https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=de356c12d3ff73a20e65d1cd7756f3370208ccb2
>
> This has been
With eigen3 including upstream's patch mentioned by Philipp [1],
opensurgsim now builds and passes all 12 tests on ppc64el, but fails 1
test on amd64 and 3 tests on arm64. I don't know if more work is
needed in the eigen3 patch or in opensurgsim.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi
On Fri, 02 Sep 2016 10:49:23 -0400, Daniel Kahn Gillmor wrote:
Thanks for the patch!
I can confirm that it works but I still have some issues:
1) After the build finishes there are 6 instances of gpg-agent
running. In my cowbuilder setup this doesn't cause any issues and
they time out after
Your message dated Sat, 03 Sep 2016 07:48:44 +
with message-id
and subject line Bug#835730: fixed in mercurial 3.9.1-1
has caused the Debian Bug report #835730,
regarding mercurial: FTBFS: Tests failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 03 Sep 2016 07:19:00 +
with message-id
and subject line Bug#835250: fixed in sqlobject 3.1.0+dfsg-1
has caused the Debian Bug report #835250,
regarding FTBFS against pytest 3.0.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Control: usertags -1 fixed-upstream
Hey,
Fix is upstream:
kdepim [Applications/16.08 f68b21d] Akregator keep crashing at exit
akregator [master 36c7fe5] Akregator keep crashing at exit
(upstream had switched repos, so stable and master needs to be applied two
times)
Regards,
sandro
--
Am Fr
86 matches
Mail list logo
