On Mon, Dec 11, 2017 at 11:10:42PM +0100, Salvatore Bonaccorso wrote:
> Hi Ben,
>
> On Mon, Dec 11, 2017 at 09:47:49PM +, Ben Hutchings wrote:
> > On Mon, 2017-12-11 at 21:29 +, Ben Hutchings wrote:
> > > There were several commits interspersed with sched/topology fixes
> > > upstream that
Tested on most important system (IBM BladeCenter HS22).
It boots OK, but infiniband don't work (interface is up, but rdma - no):
[ 147.690952] ko2iblnd: disagrees about version of symbol rdma_resolve_addr
[ 147.690956] ko2iblnd: Unknown symbol rdma_resolve_addr (err -22)
[ 147.691009] ko2iblnd:
On Tue, 12 Dec 2017 01:57:48 + Ben Hutchings wrote:
> [This message is bcc'd to all bug reporters.]
>
> Apologies for this regression. Salvatore Bonaccorso has tracked down
> which change in 3.16-stable triggers the crash, and I identified some
> related upstream changes which appear to fix i
Your message dated Tue, 12 Dec 2017 05:34:41 +
with message-id
and subject line Bug#872533: fixed in node-chai 4.1.2+dfsg-1
has caused the Debian Bug report #872533,
regarding node-chai FTBFS with nodejs 6.11.2
to be marked as done.
This means that you claim that the problem has been dealt wi
On 2017-12-11 7:42 AM, Michael Meskes wrote:
Anyone interested in citadel/webcit? If not I'm going to have it removed I
guess.
There used to be a team maintaining these packages, but I'm the only one who
worked on it in recent years. Not having used the software myself I don't
really intend t
Your message dated Tue, 12 Dec 2017 03:19:03 +
with message-id
and subject line Bug#883613: fixed in pocl 0.14-1
has caused the Debian Bug report #883613,
regarding pocl 0.14 test failures on i386
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
[This message is bcc'd to all bug reporters.]
Apologies for this regression. Salvatore Bonaccorso has tracked down
which change in 3.16-stable triggers the crash, and I identified some
related upstream changes which appear to fix it. An updated package is
available at:
https://people.debian.org
Source: linux
Version: 4.9.0-4
Followup-For: Bug #884116
I've got the same error after upgrading from 4.9.0-3 to the newer kernel.
I could provide information if required
-- System Information:
Debian Release: 9.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'
On 2017-12-11 21:34, Luca Boccassi wrote:
> BTW I've been running the packages built from 384-stretch-backports on
> my desktop and I haven't encountered issues.
Thanks for testing :-)
I think I'll wait until 384 is in testing for a good week and update
stretch-backports to 384 thereafter, unless
Processing commands for cont...@bugs.debian.org:
> reassign 884140 src:linux
Bug #884140 [linux-image] Kernel 3.16.51-2 general protection fault in
sched_init_smp()
Warning: Unknown package 'linux-image'
Bug reassigned from package 'linux-image' to 'src:linux'.
No longer marked as found in versio
Processing control commands:
> forcemerge 883938 -1
Bug #883938 [src:linux] linux-image-3.16.0-4-amd64: Kernel panic on boot after
upgrading to debian 8.10 kernel 3.16.51
Bug #884069 [src:linux] Kernel crash on boot on IBM BladeCenter HS22
Unable to merge bugs because:
package of #884140 is 'linu
On 2017-11-18, 24...@secmail.pro wrote:
CloudFlare's MITM activity is widely discussed in the Tor Project ticket.
This bug is mentioned on this webpage:
https://trac.torproject.org/projects/tor/ticket/24351
I am the reporter of that bug, titled "Block Global Active Adversary
Cloudflare". Thou
The provided work-around (setting numa=off) worked here.
Do you need further information about the system in use?
BTW: Thank you for the NUMA advice, it was about 21.00 CET when
I started a search engine and found the bug entry and the suggested
work-around, so, your advice came just in time.
On Sat, 09 Dec 2017 18:01:35 -0500 Joachim Breitner
wrote:
> Hi,
>
> rebuilding evolution fixes the problem for me.
>
> Maybe re-assign to evolution?
That's most likely a result of the uncoordinated libical3 transition /
NMU of evolution-data-server.
Jeremy did sourceful uploads of evo and ed
Hi Ben,
On Mon, Dec 11, 2017 at 09:47:49PM +, Ben Hutchings wrote:
> On Mon, 2017-12-11 at 21:29 +, Ben Hutchings wrote:
> > There were several commits interspersed with sched/topology fixes
> > upstream that I thought were cleanup and therefore didn't backport to
> > the 3.16 stable branc
On Mon, Dec 11, 2017 at 03:45:50PM +0100, Andreas Tille wrote:
> > Will let you know when I'm through with those and all is pushed to
> > alioth again.
The current master passes build in a cowbuilder that has access to
python3-ratelimiter, and lintian's only serious complaints are the
privacy viol
On Mon, 2017-12-11 at 21:29 +, Ben Hutchings wrote:
> There were several commits interspersed with sched/topology fixes
> upstream that I thought were cleanup and therefore didn't backport to
> the 3.16 stable branch. Now I suspect that at least some of them are
> needed.
>
> I'm attaching ba
Your message dated Mon, 11 Dec 2017 21:35:52 +
with message-id
and subject line Bug#884063: fixed in vlc 3.0.0~rc1-1
has caused the Debian Bug report #884063,
regarding vlc-plugin-base: fails to upgrade from 'sid' - trying to overwrite
/usr/lib/x86_64-linux-gnu/vlc/plugins/codec/libzvbi_plugi
There were several commits interspersed with sched/topology fixes
upstream that I thought were cleanup and therefore didn't backport to
the 3.16 stable branch. Now I suspect that at least some of them are
needed.
I'm attaching backports of 3 of the commits that I left out. Can you
test whether t
Your message dated Mon, 11 Dec 2017 21:17:21 +
with message-id
and subject line Bug#883937: fixed in gnome-todo 3.26.2-2
has caused the Debian Bug report #883937,
regarding fix the build with libical3
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Mon, 11 Dec 2017 21:19:13 +
with message-id
and subject line Bug#863612: fixed in opendmarc 1.3.2-3
has caused the Debian Bug report #863612,
regarding opendmarc: still ignore inet SOCKET configuration
to be marked as done.
This means that you claim that the problem has bee
Your message dated Mon, 11 Dec 2017 21:00:14 +
with message-id
and subject line Bug#875349: fixed in libp11 0.4.7-2
has caused the Debian Bug report #875349,
regarding libp11: Please migrate to openssl1.1 in Buster
to be marked as done.
This means that you claim that the problem has been deal
Hi
here the bisect log (unless overseen something with the last good commit):
git bisect start
# good: [3717265153a66c2ecbd745ea8eef213289b4a55e] Linux 3.16.48
git bisect good 3717265153a66c2ecbd745ea8eef213289b4a55e
# bad: [c45c05f42d5d3baf5d18e648c064788381fcfa1c] Linux 3.16.51
git bisect bad c
Processing commands for cont...@bugs.debian.org:
> severity 863612 serious
Bug #863612 [opendmarc] opendmarc: still ignore inet SOCKET configuration
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
863612: https://bugs.deb
On Wed, 2017-12-06 at 11:37 +0100, Andreas Beckmann wrote:
> On 2017-12-06 10:53, Julien Aubin wrote:
> > Okay I will try it. Could you please provide me the build guide and
> > install
> > guide ?
>
> From README.source:
>
> Building "bleeding edge" from SVN for users
>
> As new upstream ve
On 11 December 2017 at 19:37, Matthew Woodcraft wrote:
| Package: python-rpy
| Version: 1.0.3-30
| Severity: grave
|
| Installing and importing the stretch version of python-rpy fails with the
| stretch version of R:
|
| «
| apt install python-rpy
| python
| Python 2.7.13 (default, Nov 24 2017,
Your message dated Mon, 11 Dec 2017 21:04:51 +0100
with message-id <20171211200450.7wxkpgsigwuvq...@fliwatuet.svr02.mucip.net>
and subject line Re: Bug#828477: openvpn: FTBFS with openssl 1.1.0
has caused the Debian Bug report #828477,
regarding openvpn: FTBFS with openssl 1.1.0
to be marked as don
tag 883937 pending
thanks
Hello,
Bug #883937 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:
https://anonscm.debian.org/cgit/pkg-gnome/gnome-todo.git/commit/?id=04cc486
---
commit 04cc4863b70b96e64a426141435f7c
Processing commands for cont...@bugs.debian.org:
> tag 883937 pending
Bug #883937 [src:gnome-todo] fix the build with libical3
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
883937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883937
De
Processing commands for cont...@bugs.debian.org:
> summary 883938 Seems to affect machines with 2+-sockets/NUMA. Workaround: set
> numa=off on the kernel command and downgrade to 3.16.48-1 or earlier
Summary replaced with message bug 883938 message
Summary replaced with message bug 883938 messag
Processing commands for cont...@bugs.debian.org:
> summary 883938 Seems
Summary replaced with message bug 883938 message
Summary replaced with message bug 883938 message
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
883938: https://bugs.debian.org/cgi-bin/bugr
Package: python-rpy
Version: 1.0.3-30
Severity: grave
Installing and importing the stretch version of python-rpy fails with the
stretch version of R:
«
apt install python-rpy
python
Python 2.7.13 (default, Nov 24 2017, 17:33:09)
[GCC 6.3.0 20170516] on linux2
Type "help", "copyright", "credits" o
I'm thinking January, there's usually a new Parts Library at the end of the
year so I'm thinking about updating both at the same time.
Is there a way I can cross compile to test if the patch fixes this error?
On Sun, Dec 10, 2017 at 12:37 PM, Nicolas Guilbert wrote:
> Hi Leo,
>
> that sounds gr
Source: libical
Version: 2.0.0-1
Severity: serious
Hi,
We have src:libical3 now, so libical2 should be dropped before the
freeze. We shouldn't need to release buster with both libical 2 and 3.
Filing this bug so we don't forget about that.
Emilio
-- System Information:
Debian Release: buster/si
Bernhard Schmidt wrote:
Can you check whether numa=off on the kernel command line fixes this as well?
Indeed it does. Appending numa=off to the kernel command line fixes
the bug in my KVM virtual machines as well as my physical servers (at
least the ones I've tested so far).
So this might be a
Your message dated Mon, 11 Dec 2017 18:04:36 +
with message-id
and subject line Bug#884019: fixed in terminology 1.1.1-2
has caused the Debian Bug report #884019,
regarding terminology: FTBFS if $HOME is not writable
to be marked as done.
This means that you claim that the problem has been de
Your message dated Mon, 11 Dec 2017 18:01:21 +
with message-id
and subject line Bug#880592: Removed package(s) from unstable
has caused the Debian Bug report #843866,
regarding photofloat: FTBFS: Can't find bundle for base name
org.mozilla.javascript.resources.Messages, locale en_US
to be mar
Your message dated Mon, 11 Dec 2017 18:00:32 +
with message-id
and subject line Bug#858990: fixed in kvirc 4:4.9.2~git20171211+dfsg-1
has caused the Debian Bug report #858990,
regarding kvirc: Please migrate to openssl1.1 in buster
to be marked as done.
This means that you claim that the prob
Your message dated Mon, 11 Dec 2017 18:01:21 +
with message-id
and subject line Bug#880592: Removed package(s) from unstable
has caused the Debian Bug report #830750,
regarding photofloat: traceback on run
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Mon, 11 Dec 2017 18:01:21 +
with message-id
and subject line Bug#880592: Removed package(s) from unstable
has caused the Debian Bug report #844972,
regarding photofloat: FTBFS: Exception in thread "main"
java.lang.reflect.InvocationTargetException
to be marked as done.
Thi
On Fri, Dec 08, 2017 at 05:32:38PM -0600, Rob Browning wrote:
>Steve McIntyre writes:
>
>> Interestingly, in armhf mode the package builds just fine on the same
>> type of hardware (built ok on hoiby). Wondering what on earth is going
>> on...
>
>Agreed.
>
>For what it's worth, the only change bet
Your message dated Mon, 11 Dec 2017 17:56:21 +
with message-id
and subject line Bug#880101: Removed package(s) from unstable
has caused the Debian Bug report #824827,
regarding Error: Encryption failed!
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Hi Karsten,
Thanks for the test. Can you check whether numa=off on the kernel command line
fixes this as well?
Bernhard
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
Processing commands for cont...@bugs.debian.org:
> affects 873417 hashcat
Bug #873417 [src:pocl] pocl: Please update to llvm-toolchain 4.0 or, better, 5.0
Added indication that 873417 affects hashcat
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
873417:
Your message dated Mon, 11 Dec 2017 17:52:05 +
with message-id
and subject line Bug#880044: Removed package(s) from unstable
has caused the Debian Bug report #867501,
regarding python-jingo FTBFS: test failures
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Mon, 11 Dec 2017 17:48:34 +
with message-id
and subject line Bug#879463: Removed package(s) from unstable
has caused the Debian Bug report #811628,
regarding FTBFS with GCC 6: cannot convert x to y
to be marked as done.
This means that you claim that the problem has been de
Your message dated Mon, 11 Dec 2017 17:50:29 +
with message-id
and subject line Bug#879818: Removed package(s) from unstable
has caused the Debian Bug report #848187,
regarding xserver-xorg-video-freedreno: FTBFS with xserver 1.19
to be marked as done.
This means that you claim that the probl
Your message dated Mon, 11 Dec 2017 17:49:23 +
with message-id
and subject line Bug#879577: Removed package(s) from unstable
has caused the Debian Bug report #843382,
regarding imgtex: libapache-mod-fastcgi is gone
to be marked as done.
This means that you claim that the problem has been deal
I can reproduce the bug on multiple (physical) servers running in our
data center.
When booting my virtual servers with the new kernel, the issue did not
arise...
...until I enabled NUMA.
Booting a virtual machine with 2 sockets and 16 cores each works fine
when NUMA is disabled in KVM.
With N
Your message dated Mon, 11 Dec 2017 17:47:22 +
with message-id
and subject line Bug#879167: Removed package(s) from unstable
has caused the Debian Bug report #790220,
regarding webkit2pdf: depends on libwebkitgtk-1.0-0 which is deprecated
to be marked as done.
This means that you claim that t
Your message dated Mon, 11 Dec 2017 17:45:58 +
with message-id
and subject line Bug#879128: Removed package(s) from unstable
has caused the Debian Bug report #790219,
regarding webkit-image: depends on libwebkitgtk-1.0-0 which is deprecated
to be marked as done.
This means that you claim that
Your message dated Mon, 11 Dec 2017 17:45:58 +
with message-id
and subject line Bug#879128: Removed package(s) from unstable
has caused the Debian Bug report #784559,
regarding [webkit-image] Qt4's WebKit removal
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 11 Dec 2017 17:46:29 +
with message-id
and subject line Bug#879158: Removed package(s) from unstable
has caused the Debian Bug report #790203,
regarding gphpedit: depends on libwebkitgtk-1.0-0 which is deprecated
to be marked as done.
This means that you claim that the
Your message dated Mon, 11 Dec 2017 17:35:52 +
with message-id
and subject line Bug#878761: Removed package(s) from unstable
has caused the Debian Bug report #867052,
regarding libunique: Not suitable for release in buster
to be marked as done.
This means that you claim that the problem has b
Your message dated Mon, 11 Dec 2017 17:34:03 +
with message-id
and subject line Bug#878472: Removed package(s) from unstable
has caused the Debian Bug report #880289,
regarding jackson-datatype-guava: FTBFS: dh_auto_test:
/usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven/boot
Your message dated Mon, 11 Dec 2017 17:34:31 +
with message-id
and subject line Bug#878543: Removed package(s) from unstable
has caused the Debian Bug report #805297,
regarding python-ceres: FTBFS: ImportError: No module named mock
to be marked as done.
This means that you claim that the prob
Your message dated Mon, 11 Dec 2017 17:33:39 +
with message-id
and subject line Bug#878448: Removed package(s) from unstable
has caused the Debian Bug report #876427,
regarding cmigrep: FTBFS with ocaml 4.05.0
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Mon, 11 Dec 2017 17:35:26 +
with message-id
and subject line Bug#878756: Removed package(s) from unstable
has caused the Debian Bug report #824579,
regarding iok: Uses deprecated libunique3
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Mon, 11 Dec 2017 17:27:56 +
with message-id
and subject line Bug#878283: Removed package(s) from unstable
has caused the Debian Bug report #805158,
regarding gurgitate-mail: FTBFS: find: `debian/gurgitate-mail/usr/lib': No such
file or directory
to be marked as done.
This
Your message dated Mon, 11 Dec 2017 17:23:51 +
with message-id
and subject line Bug#877889: Removed package(s) from unstable
has caused the Debian Bug report #831737,
regarding pbnj: missing dependency on libshell-perl
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 11 Dec 2017 17:17:00 +
with message-id
and subject line Bug#877751: Removed package(s) from unstable
has caused the Debian Bug report #871829,
regarding blam: depends on libwebkit1.1-cil which is deprecated
to be marked as done.
This means that you claim that the probl
Your message dated Mon, 11 Dec 2017 17:17:30 +
with message-id
and subject line Bug#877786: Removed package(s) from unstable
has caused the Debian Bug report #790217,
regarding webkit-sharp: depends on libwebkitgtk-1.0-0 which is deprecated
to be marked as done.
This means that you claim that
Thanks Helmut and Paul for your messages. There are more information
about this issue in Debian Legal[1].
I tried to make a new configure.ac (or configure.in) but I had no
success. I will try again when I have more time (I hope it can be
soon).
[1] https://lists.debian.org/debian-legal/2017/11/ms
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:tiff
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.
Just as a note:
Upgrading to jessie-backports version 4.9.51-1~bpo8+1 is also an option,
which works.
Christoph
<>
signature.asc
Description: OpenPGP digital signature
Processing commands for cont...@bugs.debian.org:
> found 875688 1:6.0.0~beta2-1
Bug #875688 [libreoffice-report-builder] report builder inactive; only legacy
reports can be created and run
Marked as found in versions libreoffice/1:6.0.0~beta2-1.
> thanks
Stopping processing here.
Please contact
Processing commands for cont...@bugs.debian.org:
> notfound 875688 6.0.0~beta2-1
Bug #875688 [libreoffice-report-builder] report builder inactive; only legacy
reports can be created and run
There is no source info for the package 'libreoffice-report-builder' at version
'6.0.0~beta2-1' with archi
Same here with DELL R7910 and dual Xeon E5-2660v3. Downgrading the kernel
did help.
Hi
The issue is as well happening with 3.16.51 vanilla (and config
generated with localmodconfig, make deb-pkg built).
Trying to bisect now.
Regards,
Salvatore
Processing commands for cont...@bugs.debian.org:
> found 875688 6.0.0~beta2-1
Bug #875688 [libreoffice-report-builder] report builder inactive; only legacy
reports can be created and run
There is no source info for the package 'libreoffice-report-builder' at version
'6.0.0~beta2-1' with architec
Processing commands for cont...@bugs.debian.org:
> tags 875688 - moreinfo
Bug #875688 [libreoffice-report-builder] report builder inactive; only legacy
reports can be created and run
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
875688:
After some more searching I found that the screen artifacts start after
this message (from dmesg):
[drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Package: src:linux
Version: 4.9.65-3
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
I did an upgrade today and linux image was upgraded from 4.9.51-1 to 4.9.65-3.
* What was the outcome of this action?
Various screen artifacts appear un
Your message dated Mon, 11 Dec 2017 15:19:10 +
with message-id
and subject line Bug#872305: fixed in diaspora 0.6.0.1+debian-2
has caused the Debian Bug report #872305,
regarding diaspora: Package fails to install
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 11 Dec 2017 15:19:10 +
with message-id
and subject line Bug#866877: fixed in diaspora 0.6.0.1+debian-2
has caused the Debian Bug report #866877,
regarding diaspora: fails on being triggered
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> affects 876608 diaspora
Bug #876608 [ruby-compass] ruby-compass (build) depends on ruby-sass (< 3.5),
but 3.5.1-2 is in unstable
Added indication that 876608 affects diaspora
> thanks
Stopping processing here.
Please contact me if you need assis
Processing commands for cont...@bugs.debian.org:
> affects 875612 diaspora
Bug #875612 [ruby-compass-rails] ruby-compass-rails: ruby-compass obsolete and
now broken
Added indication that 875612 affects diaspora
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
8756
tag 872305 pending
thanks
Hello,
Bug #872305 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:
https://anonscm.debian.org/cgit/pkg-ruby-extras/diaspora.git/commit/?id=494820c
---
commit 494820c925706ed82b3948b2d
tag 866877 pending
thanks
Hello,
Bug #866877 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:
https://anonscm.debian.org/cgit/pkg-ruby-extras/diaspora.git/commit/?id=494820c
---
commit 494820c925706ed82b3948b2d
Processing commands for cont...@bugs.debian.org:
> tag 872305 pending
Bug #872305 [diaspora] diaspora: Package fails to install
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
872305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872305
D
Same here with Supermicro H8DGi-F (with only one cpu installed)
Same here, whole cluster of machines down here with this kernel. Same
panic message, so I won't repeat it here. These are Supermicro boxes
with Xeon CPUs:
$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 16
O
Processing commands for cont...@bugs.debian.org:
> tag 866877 pending
Bug #866877 [diaspora] diaspora: fails on being triggered
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
866877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866877
D
On 11.12.2017 13:42, Michael Meskes wrote:
> Anyone interested in citadel/webcit? If not I'm going to have it removed I
> guess.
>
> There used to be a team maintaining these packages, but I'm the only one who
> worked on it in recent years. Not having used the software myself I don't
> really in
Processing commands for cont...@bugs.debian.org:
> fixed #868773 1:0.9.6-2
Bug #868773 [src:khal] khal FTBFS: AssertionError: assert not OSError(6, 'No
such device or address')
Marked as fixed in versions khal/1:0.9.6-2.
>
End of message, stopping processing here.
Please contact me if you need a
Nicholas D Steeves writes ("Re: Bug#883731: audacious: Debian packaging has
incorrect license"):
> Will I also need to provide formal copies in debian/COPYING.emails or
> would a README.copyright or similar pointing to the bug report
> suffice? In particular I'm concerned about lines like this fr
Hi Rene and Lionel, we just tested version 6.0.0~beta2-1 and unfortunately we
find that Report Builder is inactive ...
Regards!
Guido
On Mon, Dec 11, 2017 at 03:35:53PM +0100, chrysn wrote:
> I've got them all down locally; it'll need some cleaning up (and
> possibly upstreaming) of patches, and I have yet to run it in a pbuilder
> to see which build dependencies popped up that are undeclared so far,
> but I don't expect any show
> The problem is that when trying to build this I get a lot of errors in
> the build time tests. Is there any volunteer to have a look?
I've got them all down locally; it'll need some cleaning up (and
possibly upstreaming) of patches, and I have yet to run it in a pbuilder
to see which build depe
Hi Drew!
> Looks like you're looking at the SRC dir after debian patches have been
> applied.
Indeed; thanks for pointing that out and for closing the bugs. :)
(FYI as Lintian will report a warning on this in recent versions, you may
need to specify an override with a suitable explanatory commen
Processing commands for cont...@bugs.debian.org:
> severity 589003 serious
Bug #589003 [cdrdao] cdrdao deletes cue file
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
589003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu
Processing control commands:
> tags 849604 + patch
Bug #849604 [src:geis] libgeis: please add dependency “Suggests: libgeis-doc”
Added tag(s) patch.
> tags 849604 + pending
Bug #849604 [src:geis] libgeis: please add dependency “Suggests: libgeis-doc”
Added tag(s) pending.
> tags 853415 + pending
B
Control: tags 849604 + patch
Control: tags 849604 + pending
Control: tags 853415 + pending
Dear maintainer,
I've prepared an NMU for geis (versioned as 2.2.17-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
regards,
Processing control commands:
> tags 849604 + patch
Bug #849604 [src:geis] libgeis: please add dependency “Suggests: libgeis-doc”
Ignoring request to alter tags of bug #849604 to the same tags previously set
> tags 849604 + pending
Bug #849604 [src:geis] libgeis: please add dependency “Suggests: li
Source: apscheduler
Version: 3.4.0-1
Severity: serious
Some recent change in unstable makes apscheduler FTBFS:
https://tests.reproducible-builds.org/debian/history/apscheduler.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apscheduler.html
...
debian/rules override_dh
Control: tags 880866 + patch
Control: tags 880866 + pending
Dear maintainer,
I've prepared an NMU for python-dotenv (versioned as 0.7.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
regards,
Mattia Rizzolo
GPG K
Processing control commands:
> tags 880866 + patch
Bug #880866 [src:python-dotenv] python-dotenv FTBFS with python 3.6 as only
supported version
Added tag(s) patch.
> tags 880866 + pending
Bug #880866 [src:python-dotenv] python-dotenv FTBFS with python 3.6 as only
supported version
Added tag(s)
Having the same issue, this causes a lot of IO due to writing logs and
gnome-shell constantly being near 100% cpu.
Is there any way to disable org.gnome.Shell.CalendarServer service, or to
prevent it from restarting ?
Thanks,
--
Vincent Alquier
vincent.alqu...@gmail.com
Source: yowsup
Version: 2.5.0~git20160904.d69c1ff-1
Severity: serious
Tags: buster sid
Some recent change in unstable makes yowsup FTBFS:
https://tests.reproducible-builds.org/debian/history/yowsup.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/yowsup.html
...
==
Anyone interested in citadel/webcit? If not I'm going to have it removed I
guess.
There used to be a team maintaining these packages, but I'm the only one who
worked on it in recent years. Not having used the software myself I don't
really intend to spend more time on it and both packages have an
1 - 100 of 143 matches
Mail list logo
