Your message dated Sat, 12 Jan 2019 10:04:04 +
with message-id
and subject line Bug#918442: fixed in dh-perl6 0.2
has caused the Debian Bug report #918442,
regarding perl6-readline: FTBFS (Operation "cmp": no method found)
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 12 Jan 2019 10:04:28 +
with message-id
and subject line Bug#916160: fixed in lsof 4.91+dfsg-1
has caused the Debian Bug report #916160,
regarding lsof FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 12 Jan 2019 10:44:29 +0100
with message-id <20190112094429.ga2...@semistable.com>
and subject line fixed in 2018.12
has caused the Debian Bug report #915561,
regarding moarvm 2018.11 appears to be broken
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> affects -1 src:glibc
Bug #919049 [src:linux] posix-cpu-timers: Unbreak timer rearming (regression)
Added indication that 919049 affects src:glibc
> found -1 4.20-1~exp1
Bug #919049 [src:linux] posix-cpu-timers: Unbreak timer rearming (regression)
Marked as found in
Processing commands for cont...@bugs.debian.org:
> reassign 918442 dh-perl6
Bug #918442 [src:perl6-readline] perl6-readline: FTBFS (Operation "cmp": no
method found)
Bug reassigned from package 'src:perl6-readline' to 'dh-perl6'.
No longer marked as found in versions perl6-readline/0.1.4-3.
Source: linux
Version: 4.19.13-1
Severity: serious
Tags: upstream patch
Justification: Regression / Causes FTBFS on glibc (testfailures)
Control: affects -1 src:glibc
Control: found -1 4.20-1~exp1
Control: forwarded -1 https://lkml.org/lkml/2018/12/30/169
Upstream fix 0e334db6bb4b ("posix-timers:
Your message dated Sat, 12 Jan 2019 09:49:29 +
with message-id
and subject line Bug#915112: fixed in glew 2.1.0-4
has caused the Debian Bug report #915112,
regarding glew: incompatible with glext.h from current mesa
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 12 Jan 2019 09:49:29 +
with message-id
and subject line Bug#916710: fixed in glew 2.1.0-4
has caused the Debian Bug report #916710,
regarding info-beamer FTBFS with glew 2.1.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On 1/10/19, Eric Wong wrote:
>> +- s.version = (ENV['VERSION'] || '5.4.1').dup
>> ++ s.version = '5.4.1'
>
> Why is ignoring ENV['VERSION'] necessary for the Debian build?
> I can probably remove that check if desired from the upstream
> package before the 5.5.0 release.
I've checked debian's
Package: ruby-haml-rails
Version: 0.9.0-4
Severity: serious
The following packages have unmet dependencies:
ruby-haml-rails : Depends: ruby-haml (< 5.0) but 5.0.4-1 is to be installed
Your message dated Sat, 12 Jan 2019 11:36:48 +0200
with message-id <20190112093648.GJ17164@localhost>
and subject line node-temp is back in buster
has caused the Debian Bug report #918292,
regarding node-sshpk build depends on node-temp that is currently not in buster
to be marked as done.
This
This is a critical issue. Would you recognize the need of a citation notice if
developers publish a list of donors?
Sincerely yours
Control: notfound -1 1.21.0-3
On Thu, Jan 10, 2019 at 09:13:00PM +0100, Andreas Henriksson wrote:
> On Thu, Jan 03, 2019 at 09:03:20PM +0200, Adrian Bunk wrote:
> > found 918012 1.21.0-3
> > thanks
>
> https://packages.debian.org/unstable/docker-compose says:
>
> dep: python3-docker (>=
Processing control commands:
> notfound -1 1.21.0-3
Bug #918012 [docker-compose] docker-compose: invalid version of python3-docker
dependency
No longer marked as found in versions docker-compose/1.21.0-3.
--
918012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918012
Debian Bug Tracking
Processing commands for cont...@bugs.debian.org:
> severity 913044 important
Bug #913044 [src:hy] hy fails its tests with Python3.7
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
913044:
Processing control commands:
> severity -1 serious
Bug #919000 [spyder3] Missing distribution 'keyring'
Severity set to 'serious' from 'normal'
--
919000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> close 896581
Bug #896581 [src:guile-2.0] guile-2.0 FTBFS with glibc 2.27
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
896581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896581
Debian
Processing control commands:
> tag -1 moreinfo unreproducible
Bug #911507 [offlineimap] offlineimap: fails to load imaplib2
Added tag(s) unreproducible and moreinfo.
--
911507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 moreinfo unreproducible
On Tue, 8 Jan 2019 17:42:38 +0200 Ilias Tsitsimpis
wrote:
> Hi,
>
> On Sun, Oct 21, 2018 at 08:50AM, Hans-Joachim wrote:
> > Dear Maintainer,
> >
> > calling offlineimap stops reporting
> >
> > Error while trying to import system imaplib2: name
I pinged you on github
I am pretty sure it's due to vtk/mayavi. I would suggest to package
without the hard dependency on mayavi.
if mayavi is not installed tests will be skipped and it should pass.
hope this helps
Alex
Control: found -1 5.8.0+ds-1
Control: found -1 5.8.0+ds6-3
On Sun, 30 Dec 2018 18:57:42 +0100 Ralf Jung wrote:
> In any case it seems like npm updates don't properly upgrade/remove the file
> in
> /etc, because I had an up-to-date npm and still had those lines in there (and
> I
> never locally
Processing control commands:
> found -1 5.8.0+ds-1
Bug #917217 {Done: Pirate Praveen } [npm] npm breaks
other packages' bash-completion
Marked as found in versions npm/5.8.0+ds-1; no longer marked as fixed in
versions npm/5.8.0+ds-1 and reopened.
> found -1 5.8.0+ds6-3
Bug #917217 [npm] npm
201 - 222 of 222 matches
Mail list logo
