Hi Nguyen,
for me (note: I don't have any upload power, so my opinion counts less than 0
here) :)
--- ettercap-0.7.3/debian/changelog
+++ ettercap-0.7.3/debian/changelog
[snip]
fine for me, do not need to mention me at all :)
--- ettercap-0.7.3/debian/patches/series
+++ ettercap-0.7.3/debian/p
peter green wrote:
Matthias Klose wrote:
there exist several workarounds for it (lowering the
optimization, using gcc-4.8, ...).
Disabling stack protector also seems to result in a succesful compile
(reducing it from strong to regular does not).
And another workaround is to use -marm.
--
To
Matthias Klose wrote:
there exist several workarounds for it (lowering the
optimization, using gcc-4.8, ...).
Disabling stack protector also seems to result in a succesful compile
(reducing it from strong to regular does not).
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.o
Processing commands for cont...@bugs.debian.org:
> severity 762417 normal
Bug #762417 [gtk-vnc] vinagre: cannot connect - libgrypt error?
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
762417: http://bugs.debian.org/cgi-bin/b
On 2014-12-24 10:34, Michael Biebl wrote:
Am 23.12.2014 um 21:22 schrieb Hugh Davenport:
Package: systemd
Version: 215-7
Severity: normal
Dear Maintainer,
* What led up to the situation?
Recently updated, and now boot hangs on LSB job "raise network
interfaces". Waited several minutes and
Processing control commands:
> reassign -1 ifupdown
Bug #773832 [systemd] systemd: LSB job "raise network interfaces" hangs with
allow-hotplug and no cable
Bug reassigned from package 'systemd' to 'ifupdown'.
No longer marked as found in versions systemd/215-7.
Ignoring request to alter fixed ver
Your message dated Thu, 25 Dec 2014 22:04:05 +
with message-id
and subject line Bug#772831: fixed in squidguard 1.5-4
has caused the Debian Bug report #772831,
regarding squidguard: squid 2.7 redirector protocol used by squidguard is no
more supported with squid 3.4
to be marked as done.
Thi
Processing commands for cont...@bugs.debian.org:
> severity 675112 serious
Bug #675112 [directfb] directfb: FTBFS in experimental: C compiler cannot
create executables
Bug #708726 [directfb] FTBFS as typo of LDFLAGS
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
>
Processing commands for cont...@bugs.debian.org:
> forcemerge 708726 675112
Bug #708726 [directfb] FTBFS as typo of LDFLAGS
Bug #675112 [directfb] directfb: FTBFS in experimental: C compiler cannot
create executables
Severity set to 'normal' from 'serious'
Bug #708726 [directfb] FTBFS as typo of
After some tests I created this updated patch.
With it squidguard is running with squid3 version 3.4.8.
Ciao,
Joo
Package: squidguard
Subject: fix for working (only) with squid 3.4 and higher
Author: Joachim Wiedorn
Origin: other, http://bugs.squid-cache.org/show_bug.cgi?id=3978
Processing commands for cont...@bugs.debian.org:
> severity 772831 serious
Bug #772831 [squidguard] squidguard: squid 2.7 redirector protocol used by
squidguard is no more supported with squid 3.4
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if
Processing commands for cont...@bugs.debian.org:
> severity 760424 serious
Bug #760424 [netfilter-persistent] Subject: netfilter-persistent: Running
firewall before partitions mounted
Severity set to 'serious' from 'wishlist'
> tags 760424 patch
Bug #760424 [netfilter-persistent] Subject: netfilt
Your message dated Thu, 25 Dec 2014 18:33:34 +
with message-id
and subject line Bug#765319: fixed in pioneers 14.1-3
has caused the Debian Bug report #765319,
regarding missing license in debian/copyright
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> severity -1 grave
Bug #766700 [pidgin-encryption] pidgin-encryption: Please default to stronger
keys
Severity set to 'grave' from 'important'
> tags -1 patch pending
Bug #766700 [pidgin-encryption] pidgin-encryption: Please default to stronger
keys
Added tag(s) pen
Package: libical-dev
Version: 1.0-1.1
Severity: critical
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
Hi!
While working on the “reproducible builds” effort [1], we have noticed
that libical could not be built reproducibly:
https://jenkins.debian.net/userContent/dbd/libic
Your message dated Thu, 25 Dec 2014 15:34:39 +
with message-id
and subject line Bug#773836: fixed in glance 2014.2.1-2
has caused the Debian Bug report #773836,
regarding glance: unrestricted path traversal flaw
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Thu, 25 Dec 2014 15:32:06 +
with message-id
and subject line Bug#772971: fixed in nvidia-graphics-drivers 304.125-1
has caused the Debian Bug report #772971,
regarding src:nvidia-graphics-drivers*: CVE-2014-8298: GLX-INDIRECT (Including
CVE-2014-8093, CVE-2014-8098)
to be m
Package: lightdm
Version: 1.10.3-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I think it happened after an important upgrade related to systemd
a few mo
Control: tags -1 + help
this is not seen on the gcc-4.9 Linaro branch, so a ARM porter should identify
the relevant backport.
On 12/25/2014 06:12 AM, Matthias Klose wrote:
> the escalation is wrong. there exist several workarounds for it (lowering the
> optimization, using gcc-4.8, ...). I asked
Processing control commands:
> tags -1 + help
Bug #764732 [gcc-4.9] gcc-4.9: broken -O2 optimizations on armhf
Added tag(s) help.
--
764732: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email t
Your message dated Thu, 25 Dec 2014 10:19:14 +
with message-id
and subject line Bug#773836: fixed in glance 2014.1.3-6
has caused the Debian Bug report #773836,
regarding glance: unrestricted path traversal flaw
to be marked as done.
This means that you claim that the problem has been dealt w
Hi *,
nope, you seems to be modifying other patches rather than the strict necessary
to fix this bug.
Moreover the patch is lacking of a CVE description (actually the patch is
fixing two CVEs, and the
description mentions only one)
(there is also no need to mention me, I'm not the author of th
22 matches
Mail list logo