Processing commands for cont...@bugs.debian.org:
> clone 851412 -1
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Bug #851642 [src:systemd] perl:
clone 851412 -1
reassign -1 binutils
forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=21054
retitle -1 Forced local symbol rearranging messes up GOT
Hi James
Am 17.01.2017 um 12:18 schrieb James Cowgill:
> On 17/01/17 09:10, Michael Biebl wrote:
>> Am 17.01.2017 um 10:02 schrieb Micha
CVE List for 5.7:
CVE-2016-8318
CVE-2016-8327
CVE-2017-3238
CVE-2017-3244
CVE-2017-3251
CVE-2017-3256
CVE-2017-3257
CVE-2017-3258
CVE-2017-3265
CVE-2017-3273
CVE-2017-3291
CVE-2017-3312
CVE-2017-3313
CVE-2017-3317
CVE-2017-3318
CVE-2017-3319
CVE-2017-3320
--
Lars
On 01/17/2017 09:48 PM, Lars Tan
CVE List for 5.6:
CVE-2016-8318
CVE-2016-8327
CVE-2017-3238
CVE-2017-3244
CVE-2017-3257
CVE-2017-3258
CVE-2017-3265
CVE-2017-3273
CVE-2017-3291
CVE-2017-3312
CVE-2017-3313
CVE-2017-3317
CVE-2017-3318
--
Lars
On 01/17/2017 09:48 PM, Lars Tangvald wrote:
I've built and tested the update, and will
CVE List for 5.5:
CVE-2017-3238
CVE-2017-3243
CVE-2017-3244
CVE-2017-3258
CVE-2017-3265
CVE-2017-3291
CVE-2017-3312
CVE-2017-3313
CVE-2017-3317
CVE-2017-3318
--
Lars
On 01/13/2017 09:19 AM, Norvald H. Ryeng wrote:
Source: mysql-5.5
Version: 5.5.53-0+deb8u1
Severity: grave
Tags: security upstrea
I can confirm this bug and both workaround: add double-quote to line 21
and launch with --enable-remote-extensions. That solves the problem.
Processing commands for cont...@bugs.debian.org:
> tags 851412 + pending
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Bug #851642 [src:systemd]
On Sun, Jan 15, 2017 at 1:15 AM, Michael Biebl wrote:
> Am 14.01.2017 um 18:02 schrieb Michael Biebl:
>
>> binutils_2.27.90.20170114-1. Building in stretch chroot though was
>> successful. So my observation is:
>>
>> binutils_2.27.90.20170114-1: fails
>> binutils_2.27.90.20170113-1: fails
>> binut
On Sun, Jan 15, 2017 at 1:15 AM, Michael Biebl wrote:
> Am 14.01.2017 um 18:02 schrieb Michael Biebl:
>
>> binutils_2.27.90.20170114-1. Building in stretch chroot though was
>> successful. So my observation is:
>>
>> binutils_2.27.90.20170114-1: fails
>> binutils_2.27.90.20170113-1: fails
>> binut
Hello.
Applying the patch from https://github.com/SSSD/sssd/pull/67 onto sssd
1.14.2-1 in stretch, will make both ldaps:// and ldap://+starttls work
again. Applies cleanly, no regression found so far.
It would be quite unfortunate to have stretch without this fix, as I
believe ldap(s) support is
Processing commands for cont...@bugs.debian.org:
> tag 851010 pending
Bug #851010 [src:txfixtures] txfixtures: FTBFS: dh_auto_test: pybuild --test -i
python{version} -p 2.7 returned exit code 13
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
tag 851010 pending
thanks
Hello,
Bug #851010 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=python-modules/packages/txfixtures.git;a=commitdiff;h=49557f3
---
commit 49557f332e060faf08
Your message dated Wed, 18 Jan 2017 09:35:58 +
with message-id
and subject line Bug#851115: fixed in pcs 0.9.155+dfsg-1
has caused the Debian Bug report #851115,
regarding pcs: violates font license
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Package: python-jinja2
Version: 2.9.4-1
Severity: serious
Affects: ansible
The new version of jinja2 breaks several templates used by ansible.
Please see https://github.com/ansible/ansible/issues/20063
I stumbled across this when using debops:
https://github.com/debops/ansible-postfix/issues/84
Your message dated Wed, 18 Jan 2017 11:04:11 +
with message-id
and subject line Bug#851010: fixed in txfixtures 0.2.6-1
has caused the Debian Bug report #851010,
regarding txfixtures: FTBFS: dh_auto_test: pybuild --test -i python{version} -p
2.7 returned exit code 13
to be marked as done.
Th
Hi Ian
On Tue, 17 Jan 2017 13:35:14 + Ian Jackson
wrote:
> Martín Ferrari writes ("Re: "not authorised" doing various desktoppy things
> [and 1 more messages]"):
> > This seems to solve the problem for me, thank you very much! (And I hope
> > you can get this in for stretch!)
>
> Thanks to
Michael Biebl writes ("Re: "not authorised" doing various desktoppy things [and
1 more messages] [and 1 more messages]"):
> We are currently preparing an upload for systemd. It contains a
> workaround for #851412 so we plan to upload today as we don't want to
> block other packages unnecessarily.
Hi Jeremy,
[Jeremy Bicha, 2017-01-18]
> The new version of jinja2 breaks several templates used by ansible.
>
> Please see https://github.com/ansible/ansible/issues/20063
>
> I stumbled across this when using debops:
> https://github.com/debops/ansible-postfix/issues/84
could you check if this
Hi Lars,
On Wed, Jan 18, 2017 at 10:33:30AM +0100, Lars Tangvald wrote:
> Hi,
>
> The update builds and passes testing.
> I've attached debdiff output for Wheezy and Jessie for this update. Aside
> from the changelog, the only change to packaging is a patch for a test
> (main.events_2) that was f
Hi,
Unfortunately I can't reproduce the testing failures, and the build got all
the way to the signature generation, at which point it aborted because I do
not have the proper gpg signing key.
Bear with me, because I am new at this. Here is what I did:
1. git clone https://anonscm.debian.org/
Hi,
On 01/18/2017 12:39 PM, Salvatore Bonaccorso wrote:
Hi Lars,
On Wed, Jan 18, 2017 at 10:33:30AM +0100, Lars Tangvald wrote:
Hi,
The update builds and passes testing.
I've attached debdiff output for Wheezy and Jessie for this update. Aside
from the changelog, the only change to packaging
Ok, here is the last key piece of information. Replacing source-built
Bioperl with the debian bioperl-1.7.1-1 package from
https://packages.debian.org/sid/bioperl reproduced Gregor's test errors
exactly.
I also tried swapping in libbio-graphics-perl 2.40-1 from the same
repository (with both versi
Ok, and here is a little command-line test that takes the problem a bit
deeper. I'm sending this out because I have to go to work now and can't get
back to this again today:
perl -MBio::Perl -MBio::Graphics -MBio::Graphics::Glyph::span
Can't locate Bio/Coordinate/Pair.pm in @INC (you may need to
Package: diamond
Version: 4.0.515-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
I'm attempting to build diamond from source, however the build fails at lintian
check time:
"diamond: init.d-script-needs-depends-on-lsb-base etc/
Hi,
the uploader of this package Daniele E. Domenichelli confirmed that he
is not using this package any more and I personally do not consider my
time well spent to save a package which I never used. From my point of
view the package should be orphaned and possibly even removed from
Debian.
Kind
Your message dated Wed, 18 Jan 2017 12:19:22 +
with message-id
and subject line Bug#844785: fixed in systemd-shim 10-3
has caused the Debian Bug report #844785,
regarding policykit-1-gnome: Fails to start with warning: "Unable to determine
the session we are in: No session for pid"
to be mark
Your message dated Wed, 18 Jan 2017 12:19:22 +
with message-id
and subject line Bug#844785: fixed in systemd-shim 10-3
has caused the Debian Bug report #844785,
regarding systemd-shim not fully compatible with systemd 232
to be marked as done.
This means that you claim that the problem has be
Package: kpatch
Version: 0.3.2-3
Severity: serious
Justification: fails to build from source
Hi,
kpatch cannot build the kernel module for the current kernel in sid:
DKMS make.log for kpatch-0.3.2 for kernel 4.9.0-1-amd64 (x86_64)
Wed Jan 18 12:55:36 UTC 2017
make: Entering directory '/var/lib/d
Package: diamond
Version: 4.0.515-2
Followup-For: Bug #851745
Dear Maintainer,
Below, I've provided a patch that fixes this issue (#851745) but also #851198:
--
diff -Nru diamond-4.0.515/debian/changelog diamond-4.0.515/debian/changelog
--- diamond-4.0.515/debian/changelog2017-01-05 18:0
Your message dated Wed, 18 Jan 2017 13:04:52 +
with message-id
and subject line Bug#851302: Removed package(s) from unstable
has caused the Debian Bug report #811593,
regarding FTBFS with GCC 6: statement indented as if it were guarded by
to be marked as done.
This means that you claim that t
Package: sysdig-dkms
Version: 0.13.0-1
Severity: serious
Justification: fails to build from source
Control: found -1 0.9.0-1
Hi,
sysdig-dkms cannot build the kernel module for the current kernel in sid:
DKMS make.log for sysdig-0.13.0 for kernel 4.9.0-1-amd64 (x86_64)
Wed Jan 18 12:58:21 UTC 201
Processing control commands:
> severity -1 minor
Bug #851745 [diamond] diamond: lintian error:
init.d-script-needs-depends-on-lsb-base etc/init.d/diamond
Severity set to 'minor' from 'serious'
--
851745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851745
Debian Bug Tracking System
Contact
Processing control commands:
> found -1 0.9.0-1
Bug #851752 [sysdig-dkms] sysdig-dkms: module FTBFS for Linux 4.9
Marked as found in versions sysdig/0.9.0-1.
--
851752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
control: severity -1 minor
On Wed, Jan 18, 2017 at 7:13 AM, David Stapleton
wrote:
> Package: diamond
> Version: 4.0.515-2
> Severity: serious
this is NOT a serious issue, lintian is not part of the official build
process and if the tool you use add lintian at the end and mark the
build as faile
Processing commands for cont...@bugs.debian.org:
> tags 851752 + pending
Bug #851752 [sysdig-dkms] sysdig-dkms: module FTBFS for Linux 4.9
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
851752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bu
Processing commands for cont...@bugs.debian.org:
> forwarded 851752 https://github.com/draios/sysdig/issues/710
Bug #851752 [sysdig-dkms] sysdig-dkms: module FTBFS for Linux 4.9
Set Bug forwarded-to-address to 'https://github.com/draios/sysdig/issues/710'.
> thanks
Stopping processing here.
Pleas
Your message dated Wed, 18 Jan 2017 13:20:18 +
with message-id
and subject line Bug#851412: fixed in systemd 232-11
has caused the Debian Bug report #851412,
regarding Xvfb segfaults on mips64el
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated Wed, 18 Jan 2017 13:20:18 +
with message-id
and subject line Bug#851412: fixed in systemd 232-11
has caused the Debian Bug report #851412,
regarding FTBFS on mips*, tests fail with SIGSEGV
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Wed, 18 Jan 2017 13:20:18 +
with message-id
and subject line Bug#851412: fixed in systemd 232-11
has caused the Debian Bug report #851412,
regarding perl: FTBFS on mips64el: dist/threads/t/join.t failure
to be marked as done.
This means that you claim that the problem has b
Your message dated Wed, 18 Jan 2017 13:20:18 +
with message-id
and subject line Bug#851412: fixed in systemd 232-11
has caused the Debian Bug report #851412,
regarding dbus: Segmentation fault in dbus.postinst on mips64el
to be marked as done.
This means that you claim that the problem has be
Hi Lincoln,
On Wed, Jan 18, 2017 at 07:07:55AM -0500, Lincoln Stein wrote:
>
> There appears to be a new dependency on libbio-coordinate. Probably best to
> add a "use Bio::Coordinate" and the dependency to Bio::Graphics. Then the
> problem will disappear.
Cool. In Debian terminology this means
Hi Lars,
On Wed, Jan 18, 2017 at 12:45:45PM +0100, Lars Tangvald wrote:
> Hi,
>
> On 01/18/2017 12:39 PM, Salvatore Bonaccorso wrote:
> >Hi Lars,
> >
> >On Wed, Jan 18, 2017 at 10:33:30AM +0100, Lars Tangvald wrote:
> >>Hi,
> >>
> >>The update builds and passes testing.
> >>I've attached debdiff
Source: mariadb-10.0
Version: 10.0.16-1
Severity: grave
Tags: security upstream
Hi
The following CVE's were addressed in 10.0.29 upstream, whereas
CVE-2016-6664 has already a seprate bug in the BTS:
CVE-2016-6664
CVE-2017-3238
CVE-2017-3243
CVE-2017-3244
CVE-2017-3257
CVE
Processing commands for cont...@bugs.debian.org:
> tags 851755 + fixed-upstream
Bug #851755 [src:mariadb-10.0] mariadb-10.0: CVE-2017-3238 CVE-2017-3243
CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291
CVE-2017-3312 CVE-2017-3317 CVE-2017-3318
Added tag(s) fixed-upstream.
>
Source: mariadb-10.1
Version: 10.1.20-3
Severity: grave
Tags: upstream security fixed-upstream
Justification: user security hole
Hi
The following CVEs were fixed with a new upstream version 10.1.21,
whereas CVE-2016-6664 has already a separate bug in the BTS:
CVE-2016-6664
CVE-2017-3238
Followup-For: Bug #841583
Control: block -1 with 851131
The --force problem is specific to mysql, it does not happen with
mariadb. But it fails differently on mariadb:
[...]
2017-01-18 13:52:53 140102037378944 [Note] /usr/sbin/mysqld (mysqld
10.1.20-MariaDB-3) starting as process 3768 ...
2017-0
Processing control commands:
> block -1 with 851131
Bug #841583 [src:ruby-dataobjects-mysql] ruby-dataobjects-mysql: FTBFS:
mysql_install_db: [ERROR] unknown option '--force'
841583 was not blocked by any bugs.
841583 was not blocking any bugs.
Added blocking bug(s) of 841583: 851131
--
841583:
Glad to be of help. No source changes to bio::graphics needed then?
At some point in near future I will be making changes to the exception
reporting in bio::graphics so that the error messages are more informative.
Lincoln
On Wed, Jan 18, 2017 at 8:30 AM Andreas Tille wrote:
> Hi Lincoln,
>
>
Processing commands for cont...@bugs.debian.org:
> # including CVE-2016-6664 as well in list
> retitle 851755 mariadb-10.0: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243
> CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291
> CVE-2017-3312 CVE-2017-3317 CVE-2017-3318
Bug #851755 [s
Processing control commands:
> tag -1 pending
Bug #845829 [cfengine3] cfengine3: switch to build depend on the metapackage
default-libmysqlclient-dev
Added tag(s) pending.
--
845829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845829
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: tag -1 pending
On 2017-01-17 02:21, Andreas Beckmann wrote:
> attached is a patch to fix this (and another) issue.
> If you need help, I could also upload this as a NMU.
I now uploaded this as a NMU to DELAYED/2 since cfengine3 is the last
(fixable) package in stretch blocking the mariad
On Wed, 18 Jan 2017 14:00:47 +, Lincoln Stein wrote:
> Glad to be of help. No source changes to bio::graphics needed then?
Probably that too :)
I'll take a look later today.
Thanks for your efforts and your enormous help!
Cheers,
gregor
--
.''`. https://info.comodo.priv.at/ - Debian D
- car...@debian.org wrote:
> > >With that fixed, and build with -sa (to include the orig tarball)
> > >please do upload to security-master.
> > Do we have access to upload here? I think the security team have
> handled the
> > upload in the past.
>
> yes it nees to be a key in the DD keyrin
Your message dated Wed, 18 Jan 2017 15:08:39 +
with message-id
and subject line Bug#851293: fixed in puppet-module-swift 9.4.4-1
has caused the Debian Bug report #851293,
regarding CVE-2016-9590
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated Wed, 18 Jan 2017 15:08:44 +
with message-id
and subject line Bug#845899: fixed in python-mysqldb 1.3.7-1.1
has caused the Debian Bug report #845899,
regarding python-mysqldb: switch to build depend on the metapackage
default-libmysqlclient-dev
to be marked as done.
This me
Hi Lars,
On Wed, Jan 18, 2017 at 06:41:40AM -0800, Lars Tangvald wrote:
>
> - car...@debian.org wrote:
>
>
> > > >With that fixed, and build with -sa (to include the orig tarball)
> > > >please do upload to security-master.
> > > Do we have access to upload here? I think the security team h
Your message dated Wed, 18 Jan 2017 15:33:49 +
with message-id
and subject line Bug#851714: fixed in gitlab 8.13.11+dfsg-1
has caused the Debian Bug report #851714,
regarding gitlab: Cannot push to gitlab repositories with git >= 2.11.0
to be marked as done.
This means that you claim that the
Package: chromium
Version: 55.0.2883.75-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I upgraded package chromium to 55.0.2883-75.4. After that, the Chromium browser
would not run.
I browsed the starting script /usr/bin/chromium and noticed that the string in
line 2
Le 17/01/2017 à 14:01, Felipe Sateler a écrit :
Hi Yann,
On 17 January 2017 at 06:54, Yann Richard wrote:
Hi,
We have made a package from fcoe-utils source version 1.0.31 which fix init bug
:
https://github.com/DSI-Universite-Rennes2/fcoe-utils
Tested on HP 465c G8 on Ethernet controller:
- car...@debian.org wrote:
> Hi Lars,
>
> On Wed, Jan 18, 2017 at 06:41:40AM -0800, Lars Tangvald wrote:
> >
> > - car...@debian.org wrote:
> >
> >
> > > > >With that fixed, and build with -sa (to include the orig
> tarball)
> > > > >please do upload to security-master.
> > > > Do we
Your message dated Wed, 18 Jan 2017 16:06:02 +
with message-id
and subject line Bug#737167: fixed in xfonts-wqy 1.0.0~rc1-3
has caused the Debian Bug report #737167,
regarding xfonts-wqy: prompting due to modified conffiles which were not
modified by the user
to be marked as done.
This means
thx for the update. I try to handle it asap. I'm only short of time at
the moment.
Regards
Sascha
Am 17.01.2017 um 01:50 schrieb Santiago Vila:
> retitle 835189 python-pyrax: FTBFS (failing tests)
> thanks
>
> Hi.
>
> After building this package many times today, it always fail
> and not just s
Source: 389-ds-base
Version: 1.3.5.15-1
Severity: grave
Tags: security upstream patch
Justification: user security hole
Hi,
the following vulnerability was published for 389-ds-base. Choosed
severity > important, since possibly as well triggerable by
unauthenticated attackers, but I'm not too fam
Processing commands for cont...@bugs.debian.org:
> forcemerge 648208 794849
Bug #648208 [os-prober] os-prober: blockdev --setro affects running kvm
instances
Bug #788062 [os-prober] os-prober corrupts LVs/partitions while being mounted
inside a VM
Bug #806273 [os-prober] os-prober: remove or dis
Source: php-gettext
Version: 1.0.11-1
Severity: grave
Tags: security upstream
Hi,
the following vulnerability was published for php-gettext.
CVE-2015-8980[0]:
|Arbitrary code execution in select_string, ngettext and npgettext
|count parameter
If you fix the vulnerability please also make sure t
Source: php-gettext
Version: 1.0.11-1
Severity: grave
Tags: security upstream
Forwarded: https://bugs.launchpad.net/php-gettext/+bug/1606184
Hi,
the following vulnerability was published for php-gettext.
CVE-2016-6175[0]:
Use of eval too unrestrictive
If you fix the vulnerability please also m
[droping debian-perl list from CC]
On Wed, Jan 18, 2017 at 02:30:32PM +0100, Andreas Tille wrote:
> Hi Lincoln,
>
> On Wed, Jan 18, 2017 at 07:07:55AM -0500, Lincoln Stein wrote:
> >
> > There appears to be a new dependency on libbio-coordinate. Probably best to
> > add a "use Bio::Coordinate" a
Your message dated Wed, 18 Jan 2017 16:34:04 +
with message-id
and subject line Bug#848236: fixed in gbrowse 2.56+dfsg-1
has caused the Debian Bug report #848236,
regarding src:gbrowse: Fails to build from source since bioperl upgrade has
broken libbio-graphics-perl
to be marked as done.
Thi
On Wed, 18 Jan 2017 17:27:21 +0100, Andreas Tille wrote:
> > Cool. In Debian terminology this means a new "Build-Depends" and after
> > adding
> > libbio-coordinate-perl package to this the tests succeeded. Thanks a lot
> > for
> > your help and patience!
> >
> > I now need to sort out some o
Your message dated Wed, 18 Jan 2017 16:48:31 +
with message-id
and subject line Bug#847577: fixed in integrit 4.1-1.1
has caused the Debian Bug report #847577,
regarding Embeds dietlibc (GPL) but does not have a Built-Using field
to be marked as done.
This means that you claim that the proble
Package: libgcj-bc
Version: 6.2.1-1
Severity: grave
Control: affects -1 libecj-java-gcj ecj1 ecj-gcj ant-gcj ant-optional-gcj
$ cat /var/lib/dpkg/info/libgcj-bc\:amd64.shlibs
libgcj_bc 1 libgcj-bc (>= 6.2.1-3~)
$
That seems to be the reason why several packages can currently
not be installed i
Processing control commands:
> affects -1 libecj-java-gcj ecj1 ecj-gcj ant-gcj ant-optional-gcj
Bug #851775 [libgcj-bc] libgcj-bc shlibs creates dependency that cannot be
fulfilled in unstable
Added indication that 851775 affects libecj-java-gcj, ecj1, ecj-gcj, ant-gcj,
and ant-optional-gcj
--
On Wed, Jan 18, 2017 at 05:39:05PM +0100, gregor herrmann wrote:
> >
> >
> > https://anonscm.debian.org/cgit/debian-med/gbrowse.git/tree/debian/patches
>
> Oh, cool, adding the (build)-dep is really enough, no patching
> required. Nice.
Yes, we needed this for another package ...
> For st
On 18 January 2017 at 06:29, Piotr Ożarowski wrote:
> could you check if this commit fixes it for you?
> https://github.com/pallets/jinja/commit/c6ddeb7d5f64789ed0bbc1ffef8596a79bc06fd9
Thanks for the quick response.
I'm still getting the KeyError: undefined variable after I built
jinja2 with th
Your message dated Wed, 18 Jan 2017 17:20:28 +
with message-id
and subject line Bug#223915: fixed in tk-brief 5.10-0.1
has caused the Debian Bug report #223915,
regarding tk-brief: Please don't package it as a native package
to be marked as done.
This means that you claim that the problem has
Package: chromium
Version: 55.0.2883.75-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Since last recent release, chromium does not start anymore.
Wen typing the command in a shell, I get the following message:
---
chromium
/usr/bin/chromium: 122: /usr/bin/chromium
Your message dated Wed, 18 Jan 2017 17:20:28 +
with message-id
and subject line Bug#223915: fixed in tk-brief 5.10-0.1
has caused the Debian Bug report #223915,
regarding tk-brief: FTBFS: dpkg-source: error: can't build with source format
'3.0 (native)': native package version may not have a
Hi,
I wonder if the following solution would be accepted (see the two patches
attached) : let the source package ship the two binaries (bootlx and
net_aboot.nh). One can build aboot-base on amd64 then.
The two binaries are generated from source if the source package is
built on alpha.
(The inspi
Your message dated Wed, 18 Jan 2017 17:33:27 +
with message-id
and subject line Bug#832656: fixed in bcron 0.10-4
has caused the Debian Bug report #832656,
regarding runit: breaks users of runit: ln: failed to create symbolic link
'/etc/service/bcron-sched': No such file or directory
to be ma
Control: tags 789407 unreproducible
Control: severity 789407 normal
Lowering severity as this problem was not reproducible, and the original
submitter did not provide additional information upon request.
Christoph
signature.asc
Description: Digital signature
Processing control commands:
> tags 789407 unreproducible
Bug #789407 [pidgin-openpgp] unable to send openpgp messages
Added tag(s) unreproducible.
> severity 789407 normal
Bug #789407 [pidgin-openpgp] unable to send openpgp messages
Severity set to 'normal' from 'grave'
--
789407: http://bugs.d
On Wed, Jan 18, 2017 at 06:38:44PM +0100, jhcha54008 wrote:
> I wonder if the following solution would be accepted (see the two patches
> attached) : let the source package ship the two binaries (bootlx and
> net_aboot.nh). [...]
Hmm, but this is like removing a hack and creating another one in
Your message dated Wed, 18 Jan 2017 19:57:32 +0200
with message-id <20170118175732.nwmnfecckaxvyibo@localhost>
and subject line Re: Bug#749661: ifuse: Segfault
has caused the Debian Bug report #749661,
regarding ifuse: Segfault
to be marked as done.
This means that you claim that the problem has b
Your message dated Wed, 18 Jan 2017 20:14:12 +0200
with message-id <20170118181412.xh64oottft7jewcr@localhost>
and subject line Fixed in 2.10.11-3
has caused the Debian Bug report #811945,
regarding ucimf-openvanilla: FTBFS with GCC 6: unable to find string literal
operator
to be marked as done.
On Mon, Sep 26, 2016 at 02:16:45PM +0200, Sebastian Humenda wrote:
> Hi
Hi Sebastian,
> I'll provide a patch to upstream shortly and attach it here as well, so that
> it
> is fixed both upstream and downstream.
any news regarding that?
> Sebastian
Thanks
Adrian
--
"Is there not prom
Package: installation-reports
Severity: grave
Tags: d-i
Justification: renders package unusable
Dear Maintainer,
The current installer, with the new 4.9 kernel, is unable to resolve
domains, so is quite seriously broken.
This was noted during install on an arm64 gigabyte MP30-AR1
desktop/server,
On martes, 17 de enero de 2017 22:21:51 ART Rebecca N. Palmer wrote:
[snip]
> This suggests the fix (warning: untested and not my area of expertise -
> and if it is using that line, why is there no -Wl,--no-whole-archive in
> the build log?):
This part I don't know.
> --- a/tools/llvm-shlib/CMak
Your message dated Wed, 18 Jan 2017 19:03:59 +
with message-id
and subject line Bug#851579: fixed in lcdproc 0.5.8~rc2-1
has caused the Debian Bug report #851579,
regarding lcdproc: fails to install: post-installation script returned error
exit status 10
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> tags 851039 + help
Bug #851039 [src:python-apt] python-apt: FTBFS: Test failures
Added tag(s) help.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
851039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851039
D
Yes, I'll remove it immediately and apply the patches to bio::graphics as
well.
Lincoln
On Wed, Jan 18, 2017 at 11:58 AM, Andreas Tille wrote:
> On Wed, Jan 18, 2017 at 05:39:05PM +0100, gregor herrmann wrote:
> > >
> > >https://anonscm.debian.org/cgit/debian-med/gbrowse.git/
> tree/debian/
On Wed, Jan 18, 2017 at 06:43:33PM +, Wookey wrote:
>Package: installation-reports
>Severity: grave
>Tags: d-i
>Justification: renders package unusable
>
>Dear Maintainer,
>
>The current installer, with the new 4.9 kernel, is unable to resolve
>domains, so is quite seriously broken.
hosts, not
On Wed, Jan 18, 2017 at 06:54:10PM +0100, Santiago Vila wrote:
> On Wed, Jan 18, 2017 at 06:38:44PM +0100, jhcha54008 wrote:
>
> > I wonder if the following solution would be accepted (see the two patches
> > attached) : let the source package ship the two binaries (bootlx and
> > net_aboot.nh).
Package: palo
Version: 1.95
Severity: serious
>From debian/rules:
@if [ `dpkg --print-architecture` = hppa ]; \
then \
echo "Regenerating iplboot."; \
$(MAKE) realclean; \
$(MAKE) iplboot; \
else \
echo "Lea
Your message dated Wed, 18 Jan 2017 20:53:05 +
with message-id
and subject line Bug#828468: fixed in openhpi 3.6.1-2.1
has caused the Debian Bug report #828468,
regarding openhpi: FTBFS with openssl 1.1.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> tags 762400 stretch sid
Bug #762400 {Done: Michael Biebl } [src:gtk+3.0] gtk+3.0 has
a direct Build-Depends on itself
Bug #824982 {Done: Michael Biebl } [src:gtk+3.0] src:gtk+3.0:
unsatisfiable dependency on libgtk-3-common
Bug #824999 {Done: Mi
Processing control commands:
> severity -1 important
Bug #839443 [src:bcron] bcron: FTBFS: tests failures
Severity set to 'important' from 'serious'
--
839443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> unarchive 783615
Bug #783615 {Done: Michael Shuler } [ca-certificates]
"update-ca-certificates --fresh" doesn't correctly re-add certificates in
/usr/local/share/ca-certificates
Unarchived Bug 783615
> severity 783615 serious
Bug #783615 {Done:
control: severity -1 important
Hi, I'm downgrading this one, to make the current bcron have chances to
migrated.
I think tests should be fixed, but disabling a couple of them "fixed" the
build, and
will probably make it go in Stretch
G.
signature.asc
Description: OpenPGP digital signature
Processing control commands:
> block 849845 with -1
Bug #849845 [dirmngr] dirmngr: Can't resolve keyserver hostname anymore
Bug #850606 [dirmngr] dirmngr: can't resolve ipv6 addresses when use-tor is
enabled
849845 was not blocked by any bugs.
849845 was not blocking any bugs.
Added blocking bug(
Your message dated Wed, 18 Jan 2017 21:19:01 +
with message-id
and subject line Bug#850885: fixed in dwww 1.13.3
has caused the Debian Bug report #850885,
regarding apache2: Using dwww, fails with internal server error when trying to
access /usr/share/doc
to be marked as done.
This means tha
1 - 100 of 139 matches
Mail list logo
