Your message dated Wed, 4 Jan 2017 08:26:56 +0100
with message-id <23458e0e-312a-f6be-fcc3-480d99d1a...@debian.org>
and subject line Closing...
has caused the Debian Bug report #848771,
regarding numexpr: FTBFS: Test failures
to be marked as done.
This means that you claim that the problem has bee
On Monday, 2 January 2017 23:20:30 CET gregor herrmann wrote:
> I'm just reading
> http://blogs.perl.org/users/steve_mynott/2017/01/rakudo-star-past-present-an
> d-future.html which mentions that Rakudo Star is moving from panda to zef.
Thanks for the link. I'm currently trying to figure out what
On Wed, Jan 04, 2017 at 09:07:10AM +0200, Adrian Bunk wrote:
> On Wed, Jan 04, 2017 at 06:56:55AM +, Alastair McKinstry wrote:
>...
> > As pyro is a dependency of a package I maintain (cylc), I will step in
> > as maintainer.
>
> please retitle #530280 and set yourself as owner if you want to
On Wed, Jan 04, 2017 at 06:56:55AM +, Alastair McKinstry wrote:
> Hi,
Hi Alastair,
> As pyro is a dependency of a package I maintain (cylc), I will step in
> as maintainer.
please retitle #530280 and set yourself as owner if you want to
adopt pyro.
> I request that pyro(3) _not_ be removed
Hi,
As pyro is a dependency of a package I maintain (cylc), I will step in
as maintainer.
I request that pyro(3) _not_ be removed from stretch, as we are now
passing the Jan. 5 freeze;
were I to upload a new pyro4, it would not make stretch in time for the
freeze, and especially not with
testing
Your message dated Wed, 04 Jan 2017 06:48:58 +
with message-id
and subject line Bug#830147: fixed in ruby-jeweler 2.0.1-3
has caused the Debian Bug report #830147,
regarding Drop ruby-bluecloth dependency
to be marked as done.
This means that you claim that the problem has been dealt with.
If
2016-12-19 1:19 GMT+02:00 Dirk Eddelbuettel :
>
> On 19 December 2016 at 00:05, Andreas Beckmann wrote:
> | I just tried rmysql on the porterbox eller. B-D cannot be installed in
> | sid due to a dpkg-maintscript-helper bug, but stretch works fine.
> | I could build the package in stretch without i
Processing control commands:
> severity -1 serious
Bug #849041 [dgit] dgit: psuedomerge commits have no author.
Severity set to 'serious' from 'normal'
--
849041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
A stop gap measure, to prevent the segfaulting is to use the
'--no-osd-bar' option.
Your message dated Wed, 04 Jan 2017 01:34:10 +
with message-id
and subject line Bug#850079: fixed in vtwm 5.4.7-5
has caused the Debian Bug report #850079,
regarding vtwm runs all programs with all signals blocked
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 04 Jan 2017 01:03:35 +
with message-id
and subject line Bug#817406: fixed in compartment 1.1.0-5
has caused the Debian Bug report #817406,
regarding compartment: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Wed, 04 Jan 2017 01:03:35 +
with message-id
and subject line Bug#817318: fixed in compartment 1.1.0-5
has caused the Debian Bug report #817318,
regarding compartment: Mandatory debian/compat for debhelper
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> severity 846116 important
Bug #846116 [src:libhamcrest-java] libhamcrest-java: FTBFS randomly (error:
cannot access Description)
Severity set to 'important' from 'serious'
> severity 680038 important
Bug #680038 [src:kyotocabinet] kyotocabinet: F
severity 846116 important
severity 680038 important
severity 828929 important
severity 834686 important
severity 834962 important
severity 842836 important
severity 844083 important
severity 844088 important
severity 844571 important
severity 845164 important
severity 846021 important
severity 8461
Your message dated Wed, 04 Jan 2017 00:48:28 +
with message-id
and subject line Bug#844137: fixed in libgroove 4.3.0-3
has caused the Debian Bug report #844137,
regarding node-groove: FTBFS: Test failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On Mon, 02 Jan 2017 12:01:26 + Santiago Vila wrote:
> Package: src:jackson-module-afterburner
> Version: 2.7.1-1
> Severity: serious
pom.xml: The version is missing from the jackson-annotations artifact.
I've seen this kind of error quite a lot in the past. Removing the
--parent in *.poms do
tag 844137 pending
thanks
Hello,
Bug #844137 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/libgroove.git;a=commitdiff;h=bc80398
---
commit bc80398bb019ca483163ba67685e0
Processing commands for cont...@bugs.debian.org:
> tag 844137 pending
Bug #844137 [libgrooveplayer4] node-groove: FTBFS: Test failures
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
844137: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=84
Control: tags -1 confirmed
On Thu, 29 Dec 2016 16:45:01 + "Chris West (Faux)"
wrote:
> Source: java-gnome
> Version: 4.1.3-4
> Severity: serious
> Justification: fails to build from source
> Tags: sid stretch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC
Processing control commands:
> tags -1 confirmed
Bug #849669 [src:java-gnome] java-gnome: FTBFS on arm: dh_install:
libjava-gnome-java-doc missing files: doc/api/
Added tag(s) confirmed.
--
849669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849669
Debian Bug Tracking System
Contact ow...@
Hi there,
as the stretch freeze approaches, I'm getting concerned about the
status of logrotate, most notably #734688. The maintainer (CC'ed)
hasn't shown any sign of activity for a while, also no response to a
private message (I admit, it's been just a few days).
Since the fix includes switching
Your message dated Tue, 03 Jan 2017 23:18:39 +
with message-id
and subject line Bug#734688: fixed in logrotate 3.11.0-0.1~exp1
has caused the Debian Bug report #734688,
regarding Logs are not rotated for a month
to be marked as done.
This means that you claim that the problem has been dealt w
Hello,
On Tue, Jan 3, 2017 at 5:42 PM, Joachim Falk wrote:
> I have a fix for this and many other minor things. Can you test
> an RC for tigervnc 1.7.0+dfsg-2? Find the debs under
Looks ok for me.
(As a sidenote plain tigervncserver calls /etc/X11/Xvnc-session calls
Xsession which doesn't seem
Processing control commands:
> severity -1 serious
Bug #757083 [initscripts] initscripts: please treat /usr (if separate) the same
as /
Severity set to 'serious' from 'normal'
> tags -1 - patch
Bug #757083 [initscripts] initscripts: please treat /usr (if separate) the same
as /
Removed tag(s) pa
Correction is on its way.
// Ola
On 3 January 2017 at 16:45, Peter Gervai wrote:
> Package: tigervnc-standalone-server
> Version: 1.7.0+dfsg-1
> Severity: important
> File: /usr/bin/tigervncserver
> Tags: patch
>
> By the way it renders program unusable for me, but I am scared of grave bugs.
>
Niko Tyni:
>
> Seems to be https://github.com/sphinx-doc/sphinx/issues/3212
> which should be fixed in sphinx_1.4.9-2, migrated to testing today or so.
>
With that version of sphinx, dhcpcanon does not fail to build.
Thanks,
ju.
Your message dated Tue, 03 Jan 2017 22:04:56 +
with message-id
and subject line Bug#849650: fixed in debian-security-support 2017.01.03
has caused the Debian Bug report #849650,
regarding debian-security-support: FTBFS on 32-bit (??): /mawk: 186: [: -gt:
unexpected operator
to be marked as do
Processing control commands:
> affects -1 src:gyoto
Bug #849991 [doxygen] breathe: FTBFS with new doxygen?
Added indication that 849991 affects src:gyoto
> tags -1 patch
Bug #849991 [doxygen] breathe: FTBFS with new doxygen?
Added tag(s) patch.
--
849991: http://bugs.debian.org/cgi-bin/bugreport
Control: affects -1 src:gyoto
Control: tags -1 patch
I found a similar problem building the gyoto package.
Confirming that Albert's patch from the upstream bug report fixes
building breathe and gyoto.
--- a/src/xmlgen.cpp
+++ b/src/xmlgen.cpp
@@ -620,7 +620,7 @@
if (md->isInline()) t << "ye
On Tue, 3 Jan 2017 10:24:25 +0100 (CET) x.guerri...@tin.it wrote:
> Control: tags -1 patch
>
> I attach the patch making jack compatible with
> current eyed3 version.
> The patch can be applied at the end of the
> current debian patchset.
>
>
> This patch is distribuited under the same
> ter
On Mon, 26 Dec 2016 18:15:20 +0100 Daniel Pocock wrote:
[...]
> apcupsd[10324]: A copy of the daemon is still running. If you just
> stopped it,
> apcupsd[10324]: please wait about 5 seconds for it to shut down.
>
>
> Maybe the "stop" action should wait for it to really stop? Not
> stopping/re
Hmmm,
On 03-01-17 22:07, Paul Gevers wrote:
> On 03-01-17 21:21, PICCA Frederic-Emmanuel wrote:
>> I just try to use dbconfig-common like I did before,
>> (create the tango database, populate it with a few values and create some
>> procedures.)
>>
>> What is strange to me is that with dbconfig-c
Hello
> > > Version: 4.3.36-dfsg-1+deb8u1
> > > Severity: grave
> > > Justification: renders package unusable
>Every module source package gets broken by kernel API changes, so>logically we
>should do this for all of them rather than just
>virtualbox-dkms. But have you seen how many of them
Hi Frederic-Emmanuel,
On 03-01-17 21:21, PICCA Frederic-Emmanuel wrote:
> I just try to use dbconfig-common like I did before,
> (create the tango database, populate it with a few values and create some
> procedures.)
>
> What is strange to me is that with dbconfig-common (jessie version), I en
Your message dated Tue, 03 Jan 2017 21:03:59 +
with message-id
and subject line Bug#850029: fixed in bioperl-run 1.7.1-2
has caused the Debian Bug report #850029,
regarding libbio-perl-run-perl: fails to upgrade from 'jessie' - trying to
overwrite /usr/share/man/man3/Bio::Tools::Run::StandAlo
Your message dated Tue, 03 Jan 2017 21:05:03 +
with message-id
and subject line Bug#850058: fixed in libass 1:0.13.4-2
has caused the Debian Bug report #850058,
regarding mpv: [osd/libass] [0x55f686fa1bc0]: Warning: no style named 'Default'
found; Segmentation fault
to be marked as done.
Thi
Package: vtwm
Version: 5.4.7-4
Severity: serious
I have discovered that in my signal handling patch I forgot to reset
the signal mask before forking and execing.
Ouch!
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a pri
Your message dated Tue, 03 Jan 2017 21:05:03 +
with message-id
and subject line Bug#850058: fixed in libass 1:0.13.4-2
has caused the Debian Bug report #850058,
regarding libass5: 0.13.5 broke the ABI
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Package: duplicity
Version: 0.6.18-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Since yesterday's update, backup to a SSH target is broken and leads to this
stacktrace:
ssh: Unknown exception: CTR mode needs counter parameter, not IV
ssh: Traceback (most recent cal
> I am not sure that I follow what you are doing, but if you need the code
> to be run with the dbadmin privileges, you should put the code in:
>/usr/share/dbconfig-common/data/PACKAGE/upgrade-dbadmin/DBTYPE/VERSION
> instead of in:
>/usr/share/dbconfig-common/data/PACKAGE/upgrade/DBTYPE/VE
Processing commands for cont...@bugs.debian.org:
> tag 850058 pending
Bug #850058 [libass5] libass5: 0.13.5 broke the ABI
Bug #850067 [libass5] mpv: [osd/libass] [0x55f686fa1bc0]: Warning: no style
named 'Default' found; Segmentation fault
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stop
tag 850058 pending
thanks
Hello,
Bug #850058 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/libass.git;a=commitdiff;h=91aba54
---
commit 91aba5408ade4fb3f8bb408f11480940
Processing control commands:
> severity -1 grave
Bug #850058 [libass5] libass5: mpv often segfaults when displaying status info
Severity set to 'grave' from 'important'
> retitle -1 libass5: 0.13.5 broke the ABI
Bug #850058 [libass5] libass5: mpv often segfaults when displaying status info
Changed
Dear DDs,
the incompatibility problem with Docutils 0.13.1 is fixed in the Docutils
repository, we plan a bugfix release 0.13.2.
Dmitries patch is compatible to both versions but no longer required once
0.13.2 hits Debian.
regards,
Günter Milde
Control: severity -1 important
Control: tags -1 + moreinfo
On Mon, Dec 19, 2016 at 03:04:50AM +0100, Christian Hofstaedtler wrote:
> * Dominic Hargreaves [161219 02:04]:
> > Control: severity -1 important
> > Control tags -1 + unreproducible
> >
> > This package builds for me on a current sid ch
Processing control commands:
> severity -1 important
Bug #834420 [src:latex2html] latex2html: Relies on '.' being in perl's @INC
Severity set to 'important' from 'serious'
> tags -1 + moreinfo
Bug #834420 [src:latex2html] latex2html: Relies on '.' being in perl's @INC
Added tag(s) moreinfo.
--
8
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding pam-mysql: FTBFS: configure: error: Cannot find pam headers. Please
check if your system is ready for pam module developm
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding mediatomb: FTBFS: configure: error: unable to configure mysql support
to be marked as done.
This means that you claim tha
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding libapache-mod-musicindex: FTBFS: x86_64-linux-gnu-gcc: error: .specs:
No such file or directory
to be marked as done.
Th
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding libpreludedb: FTBFS: gcc: error: .specs: No such file or directory
to be marked as done.
This means that you claim that t
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding sphinxsearch: FTBFS: ./conftest.c:89: undefined reference to `_doprnt'
to be marked as done.
This means that you claim th
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding dballe: FTBFS: g++: error: .specs: No such file or directory
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding redland: FTBFS: gcc: error: .specs: No such file or directory
to be marked as done.
This means that you claim that the pr
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#847231: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #847231,
regarding mysql-server-core-5.7: fails to upgrade from 'jessie' - trying to
overwrite /usr/share/man/man1/innochecksum.1.gz
to be m
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding gnokii: FTBFS: gcc: error: .specs: No such file or directory
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding python-mysqldb: FTBFS: x86_64-linux-gnu-gcc: error: .specs: No such
file or directory
to be marked as done.
This means t
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding lua-sql: FTBFS: cc: error: .specs: No such file or directory
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding lua-dbi: FTBFS: cc: error: .specs: No such file or directory
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding ruby-mysql: FTBFS: cat: mkmf.log: No such file or directory
to be marked as done.
This means that you claim that the prob
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding mediatomb: FTBFS: g++: error: .specs: No such file or directory
to be marked as done.
This means that you claim that the
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding lua-sql: FTBFS: cc: error: .specs: No such file or directory
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding sphinxsearch: FTBFS: ./conftest.c:89: undefined reference to `_doprnt'
to be marked as done.
This means that you claim th
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding gmysqlcc: FTBFS: x86_64-linux-gnu-gcc: error: .specs: No such file or
directory
to be marked as done.
This means that yo
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding pmacct: FTBFS: gcc: error: .specs: No such file or directory
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding redland: FTBFS: gcc: error: .specs: No such file or directory
to be marked as done.
This means that you claim that the pr
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding apophenia: FTBFS: gcc: error: .specs: No such file or directory
to be marked as done.
This means that you claim that the
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding python-mysqldb: FTBFS: x86_64-linux-gnu-gcc: error: .specs: No such
file or directory
to be marked as done.
This means t
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding uselessly adds mysqls -fdebug-prefix-map= to mysql_config output,
breaking builds
to be marked as done.
This means that
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding libapache-mod-musicindex: FTBFS: x86_64-linux-gnu-gcc: error: .specs:
No such file or directory
to be marked as done.
Th
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#841592: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #841592,
regarding mysql-5.7: FTBFS: Tests failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 03 Jan 2017 19:34:56 +
with message-id
and subject line Bug#844275: fixed in mysql-5.7 5.7.16-2
has caused the Debian Bug report #844275,
regarding mysql_config injects build flags which breaks the build for other
packages
to be marked as done.
This means that you cla
Hi Frederic-Emmanuel,
On Tue, 3 Jan 2017 15:02:08 + PICCA Frederic-Emmanuel
wrote:
> 1) On Jessie
>
> with the tango account
>
> mysql> use tango;
> mysql> show create procedure class_att_prop\G
>
> I got "Create Procedure": NULL
>
> But If I use the root account (mysqladmin)
>
> CREAT
Your message dated Tue, 3 Jan 2017 11:04:42 -0800
with message-id <20170103190442.c4ewrrsbuyodv...@galago.mtmxr.com>
and subject line Re: Bug#821036: oath-toolkit: FTBFS: /usr/bin/gtkdoc-mkpdf:
/usr/bin/dblatex: not found
has caused the Debian Bug report #821036,
regarding oath-toolkit: FTBFS: /us
Your message dated Tue, 03 Jan 2017 19:04:47 +
with message-id
and subject line Bug#849953: fixed in quagga 1.1.0-3
has caused the Debian Bug report #849953,
regarding cannot restart service
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not t
Processing commands for cont...@bugs.debian.org:
> severity 848256 important
Bug #848256 [lastpass-cli] lastpass-cli: lpass segfaults attempting to log in
Severity set to 'important' from 'grave'
> tag 848256 +unreproducible +moreinfo
Bug #848256 [lastpass-cli] lastpass-cli: lpass segfaults attemp
severity 848256 important
tag 848256 +unreproducible +moreinfo
thanks
Hi Joachim,
thanks for your help, much appreciated - it works now for me too, yay ;)
Regards,
Daniel
Thanks Sebastian and Christian,
I'm packaging 2.4.18...
Regards,
Eva
On Fri, Dec 23, 2016 at 10:34 PM, Sebastian Andrzej Siewior
wrote:
> On 2016-12-23 09:42:22 [+0100], Christian Liesch wrote:
>> Hey all
>
> Hi,
>
>> Thanks for the patch, I build a new version => 2.4.18. Enjoy.
>
> Thank you Ch
Am 03.01.2017 um 19:04 schrieb Daniel Baumann:
> Hi,
>
> yes, that fixes the problem I mentioned, thanks.
>
> however, after doing this:
>
> ---snip---
> daniel@daniel:~$ tigervncserver
>
> New 'X-daniel' desktop at :1 on machine daniel
>
> Starting applications specified in /etc/X11/Xvnc-sess
On Thu, Dec 29, 2016 at 09:23:15PM +0100, Gaudenz Steinlin wrote:
>...
> The second problem is much tricker to solve. Rocksdb relies on
> std::future which does not work on armel due to a GCC bug:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727621
> https://gcc.gnu.org/bugzilla/show_bug.
Your message dated Tue, 03 Jan 2017 18:33:26 +
with message-id
and subject line Bug#849362: fixed in libstring-diff-perl 0.07-2
has caused the Debian Bug report #849362,
regarding libstring-diff-perl: FTBFS: test failures with new libyaml-perl
to be marked as done.
This means that you claim t
Processing control commands:
> reassign 849875 wpasupplicant
Bug #849875 [broadcom-sta-dkms] broadcom-sta-dkms: Wifi association took too
long, failing activation
Bug reassigned from package 'broadcom-sta-dkms' to 'wpasupplicant'.
No longer marked as found in versions broadcom-sta/6.30.223.271-5.
Processing commands for cont...@bugs.debian.org:
> tag 849362 + pending
Bug #849362 [libstring-diff-perl] libstring-diff-perl: FTBFS: test failures
with new libyaml-perl
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
849362: http://bugs.deb
tag 849362 + pending
thanks
Some bugs in the libstring-diff-perl package are closed in revision
dc7f6165be2a46cdde9c7d2d28156f0df8cbd793 in branch 'master' by gregor
herrmann
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libstring-diff-perl.git/commit/?id=dc7f616
Hi,
yes, that fixes the problem I mentioned, thanks.
however, after doing this:
---snip---
daniel@daniel:~$ tigervncserver
New 'X-daniel' desktop at :1 on machine daniel
Starting applications specified in /etc/X11/Xvnc-session
Log file is /home/daniel/.vnc/daniel:1.log
Use xtigervncviewer -S
Your message dated Tue, 03 Jan 2017 18:04:31 +
with message-id
and subject line Bug#834912: fixed in libfile-tee-perl 0.07-2
has caused the Debian Bug report #834912,
regarding libfile-tee-perl: FTBFS randomly (Failed 1/2 test programs)
to be marked as done.
This means that you claim that the
tag 834912 + pending
thanks
Some bugs in the libfile-tee-perl package are closed in revision
9b3aeb41a943ee9fefb3bbed7eac9e5b1c946143 in branch 'master' by gregor
herrmann
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libfile-tee-perl.git/commit/?id=9b3aeb4
Commi
Processing commands for cont...@bugs.debian.org:
> tag 834912 + pending
Bug #834912 [src:libfile-tee-perl] libfile-tee-perl: FTBFS randomly (Failed 1/2
test programs)
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
834912: http://bugs.debian
Hello, I will look into this the end of this week :)
Regards.
*Mouaad Aallam*
On Fri, Dec 30, 2016 at 9:16 PM, Hans-Christoph Steiner
wrote:
>
> It turns out that the approach in google-android-installers is not
> maintainable going forward, so we need to split out each source package
> from go
Great!
Sent from a phone
Den 3 jan 2017 15:27 skrev "Joachim Falk" :
> Hi Ola,
>
> Am 03.01.2017 um 13:04 schrieb Ola Lundqvist:
> > Hi
> >
> > Just want to check if your changes are ready for release? We have a new
> RC bug that I would like to fix asap.
> hopefully yes. It works on my system n
Dear Peter,
I have a fix for this and many other minor things. Can you test
an RC for tigervnc 1.7.0+dfsg-2? Find the debs under
http://xamane.jfalk.de/dists/homebrew-stretch/selfmade/binary-amd64
Regards,
Joachim Falk
signature.asc
Description: OpenPGP digital signature
Hi, the attached patch fixes *some* of the issues.
- sqlparse 0.2 changed is_whitespace into a property
- token_next now returns a (idx, token) tuple instead of just the token
However I am now getting these errors:
# journalctl _SYSTEMD_UNIT=calendarserver.service | tail
Jan 03 17:25:31 pdeb1 c
Processing commands for cont...@bugs.debian.org:
> merge #850054 #849996
Bug #850054 [tigervnc-standalone-server] /usr/bin/tigervncserver: label error
in sanity check
Bug #849996 [tigervnc-standalone-server] tigervncserver doesn't work
Marked as found in versions tigervnc/1.7.0+dfsg-1.
Added tag(
Processing commands for cont...@bugs.debian.org:
> severity #850054 serious
Bug #850054 [tigervnc-standalone-server] /usr/bin/tigervncserver: label error
in sanity check
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.
Please contact me if you need assistanc
Processing commands for cont...@bugs.debian.org:
> reassign #849996 tigervnc-standalone-server
Bug #849996 [tigervnc] tigervncserver doesn't work
Bug reassigned from package 'tigervnc' to 'tigervnc-standalone-server'.
No longer marked as found in versions 1.7.0+dfsg-1.
Ignoring request to alter fi
Processing commands for cont...@bugs.debian.org:
> fixed 849994 1.1.5+dfsg.1-1~bpo8+2
Bug #849994 {Done: Guilhem Moulin } [roundcube]
roundcube-core: install fails; Class 'Patchwork\Utf8\Bootup' not found
Marked as fixed in versions roundcube/1.1.5+dfsg.1-1~bpo8+2.
> thanks
Stopping processing he
Processing commands for cont...@bugs.debian.org:
> notfound 849994 1.1.5+dfsg.1-1~bpo8+2
Bug #849994 {Done: Guilhem Moulin } [roundcube]
roundcube-core: install fails; Class 'Patchwork\Utf8\Bootup' not found
No longer marked as found in versions roundcube/1.1.5+dfsg.1-1~bpo8+2.
> thanks
Stopping
Your message dated Tue, 03 Jan 2017 16:04:50 +
with message-id
and subject line Bug#848155: fixed in verilog-mode 20161124.fd230e6-2
has caused the Debian Bug report #848155,
regarding verilog-mode: FTBFS when built with dpkg-buildpackage -A (cp: cannot
stat 'verilog.info': No such file or di
Processing commands for cont...@bugs.debian.org:
> merge #849996 #850054
Bug #849996 [tigervnc] tigervncserver doesn't work
Unable to merge bugs because:
severity of #850054 is 'important' not 'serious'
package of #850054 is 'tigervnc-standalone-server' not 'tigervnc'
Failed to merge 849996: Did n
On 12/15/16 10:47, C. Morgan Hamill wrote:
Hello Morgan,
> Since upgrading to the version of lastpass-cli built against OpenSSL
> 1.1, Any attempt to use lpass has resulted in the error "Segmentation
> fault" followed by an immediate exit.
I'm unable to duplicate this behavior. I just build a cl
1 - 100 of 163 matches
Mail list logo
