fixed 820794 2:4.2.14+dfsg-0+deb8u2
thanks
I confirm that 4.2.14+dfsg-0+deb8u2 finally actually fixes.
4.2.14+dfsg-0+deb8u2 has reached stable-security.
Thank you very much Mathieu.
Philippe Cloutier
Développement des systèmes d'information
Groupe Voyages Québec
* 1 [418] 525
Merci d'avance Mathieu.
Note that the link to git.debian.org is broken (404).
> -Message d'origine-
> De : Mathieu Parent [mailto:math.par...@gmail.com]
> Envoyé : 7 décembre 2016 15:46
> À : 820794-submit...@bugs.debian.org
> Objet : Bug#820794: marked as pending
>
> tag 820794 pending
>
2013/4/2 Thorsten Glaser
> On Thu, 28 Mar 2013, Filipus Klutiero wrote:
>
> > There's a very simple solution to that which would solve even more
> > problems. Unfortunately, it requires a larger change.
>
> Well, let’s just not do that right now.
>
> The upgrade to 1.19 was on very short notice a
Package: sun-java6
Version: 6-00-2
Severity: critical
Tags: security, upstream
The sun-java6 version in testing is vulnerable to CVE-2007-5689 :
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5689
From http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-5689 :
Overview
The Java Virtual Machin
Are you able to reproduce this without using aptitude? Or at least, without
using its TUI?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Le February 1, 2008 12:42:49 am Lee Aylward, vous avez écrit :
> On Fri, Feb 01, 2008 at 12:28:15AM -0500, Philippe Cloutier wrote:
> > > On Thu, Jan 31, 2008 at 09:00:29PM -0800, Randall Donald wrote:
> > > > > libgl1-mesa-swx11 conflicts with nvidia-glx
> > >
> On Thu, Jan 31, 2008 at 09:00:29PM -0800, Randall Donald wrote:
> > > libgl1-mesa-swx11 conflicts with nvidia-glx
> >
> > That isn't my problem or bug.
> > libgl1-mesa-swx11 in fact conflicts with all other opengl
> > implementations i.e.
> > Conflicts: libgl1, libgl1-mesa-swrast, mesag3, mesag3
severity 463467 important
thanks
Le February 1, 2008 12:05:01 am Lee Aylward, vous avez écrit :
> On Thu, Jan 31, 2008 at 07:30:52PM -0500, Philippe Cloutier wrote:
> > How does this conflict make nvidia-glx unusable?
>
> Because I can't install it?
I don't even have an
Package: sun-java5
Version: 1.5.0-10-3
Severity: critical
Tags: security, fixed-upstream
1.5.0-10 is vulnerable to CVE-2007-5689 :
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5689
From http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-5689 :
Overview
The Java Virtual Machine (JVM) in Sun
How does this conflict make nvidia-glx unusable?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Which version of nvidia-glx do you use?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Did 3.5.7 work?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Did you already use nvidia-installer on that system?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Le October 23, 2007 02:14:36 pm Bastian Kleineidam, vous avez écrit :
> Hi,
>
> I just hit bug #435386, attached is a build log. As stated in my previous
> message, removing $(ROOT_CMD) from debian/rules fixes the nested fakeroot
> error.
>
> Regards,
> Bastian
Which command triggers this problem
Package: nvidia-graphics-legacy-71xx-modules-amd64
Version: 1.0.7185+1
Severity: grave
2.6.18-4 is obsolete, replaced by 2.6.21-2 in testing and 2.6.22-2 in
unstable. These packages are no more usable in testing and unstable, if they
ever have been. They should be updated or removed.
--
To U
Package: nvidia-graphics-legacy-71xx-modules-i386
Version: 1.0.7185+1
Severity: grave
2.6.18-4 is obsolete, replaced by 2.6.21-2 in testing and 2.6.22-2 in
unstable. These packages are no more usable in testing and unstable, if they
ever have been. They should be updated or removed.
--
To UN
Package: gcc-4.2
Version: 4.2.1-4
Severity: serious
gcc-4.2 includes gcc-4.2's manpage, which is a non-free document under the
GFDL with invariant sections. gcov's manpage has the same issue.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAI
The system seems to have not only sid sources, but also experimental
sources (in addition to stable and testing). Please provide sources.list.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Please explain how this is a grave bug.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
maximilian attems a écrit :
On Tue, Mar 20, 2007 at 04:36:55PM +, Filipus Klutiero wrote:
Humk but if you don't know what the bug is, why did you upgrade the report's
severity to serious?
would be cool if you guys actually read the bug report :)
readjusting subject..
so the repor
Stefano, now that we have BTS version tracking, bugs in a source package which
are fixed this way should not be closed until the obsolete source package is
removed from the archive.
Rethinking about it...please ignore that part.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Maximilian, what's the bug? yaird can't be used with lilo with latest
kernel?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
unmerge 413469 415287
#Reports about different issues
close 413469 20070203-1
severity 413469 wishlist
#Same as previously
thanks
Steve Langasek a écrit :
On Fri, Mar 16, 2007 at 12:53:46AM -0400, Philippe Cloutier wrote:
Steve, why did you reopen this bug?
Because the package is
Steve Langasek a écrit :
severity 413469 serious
reopen 413469
thanks
[...]
After discussing on IRC with Joey and other ion users, it seems that there
isn't really much demand for ion3 in a stable release after all; those I've
talked to who use ion3 all say they run testing or unstable on the
Jose, please open a bug report against ftp.debian.org requesting the
removal of list.
Thanks for having maintained this package.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
What evidence do you have that the package is unusable?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
reopen 410948
severity 410948 minor
thanks
Steve Langasek a écrit :
On Fri, Feb 16, 2007 at 04:05:17AM -0500, Filipus Klutiero wrote:
[...]
Again, this is an effort to keep the government from claiming *more* rights
over the software than what's permitted by the usual license, not to
Steve Langasek a écrit :
On Thu, Feb 15, 2007 at 03:19:42PM -0500, Filipus Klutiero wrote:
utils/base64/base64.tcl's copyright notice contains
# See the file "license.terms" for information on usage and
# redistribution
# of this file, and for a DISCLAIMER OF ALL WARRANTIES.
Steve Langasek a écrit :
On Wed, Feb 14, 2007 at 03:55:53PM -0500, Filipus Klutiero wrote:
Package: amsn
Version: 0.95+dfsg2-0.2
Severity: serious
des.tcl contains the following paragraph at the end of its license
terms:
GOVERNMENT USE: If you are acquiring this softwar
Hi,
I'm just trying to evaluate the severity, but does this happen for all
users on your system? For example, if you create a new user?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
severity 409841 important
thanks
Downgrading while waiting for evidence of grave severity from submitter.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Justification: causes non-serious data loss
Which data loss does this cause?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
severity 374355 normal
thanks
Aurélien, you hit #408249.
Aside from supporting Kurt's request for a status update, I would like
Guillem to take note that vlc maintainers should be informed if you
don't expect to be able to fix this bug in time for Etch, due to
vlc-plugin-glide.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
severity 357439 important
thanks
I am vaguely following this bug, so I may be doing something wrong. It
appears that the severity justification for this report is that the
package is unusable. However, this was referring to amaya, and
libwxgtk2.6-0 is not unusable, so I'm downgrading to import
Justification: renders package unusable
What evidence do you have that the package is unusable?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
the sole thing that I upgraded since is the xorg server
From what?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
reassign 397685 nvidia-graphics-legacy-modules-i386
thanks
I suppose what you describe is a linux-2.6 bug fixed in -4. Let's keep
this report anyway as a reminder that
nvidia-graphics-legacy-modules-i386 and its 3 friends are now also
unusable in sid.
--
To UNSUBSCRIBE, email to [EMAIL PROT
Andrew Vaughan a écrit :
Hi Randall, Hi Phillipe
Both nvidia-graphics-drivers and nvidia-graphics-drivers-legacy are
currently free of RC bugs, and old enough.
Is there any reason not ask on -release for them to be pushed into testing?
I was personally waiting for an up-to-date Etch box w
severity 397027 important #submitter doesn't support severity justification
thanks
Johannes Bittner a écrit :
Philippe Cloutier wrote:
Justification: renders package unusable
What evidence do you have that nvidia-glx is unusable?
Before we get into this, explain what you
Justification: renders package unusable
What evidence do you have that xserver-xorg is unusable?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Justification: renders package unusable
What evidence do you have that nvidia-glx is unusable?
Before we get into this, explain what you're doing with such an
x11-common version.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECT
Randall Donald a écrit :
On Mon, 2006-10-30 at 16:19 -0500, Philippe Cloutier wrote:
Sure.
This bug should normally be closed, as nvidia-graphics-modules-i386 is
no longer in testing and therefore nvidia-graphics-modules-i386 can't
FTBFS in testing anymore. However, when nvidia-k
Randall Donald a écrit :
On Thu, 2006-10-19 at 15:52 -0400, Philippe Cloutier wrote:
Note that this bug no longer applies, but is kept open as a dummy
britney-helping bug to avoid the package to reenter testing once
linux-2.6 is updated, in case nvidia-graphics-drivers is not in testing
notfound 394661 10.063
severity 394679 grave
merge 394679 394661
found 394661 10.062
thanks
Actually it wasn't happening with a homemade kernel, but upgrading the normal
linux-image-2.6.18 package.
The stock linux-2.6 images weren't yet recompiled with k-p 10.063.
I have the impression this
Is it possible to try any other driver on this system? Perhaps vesa?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Justification: renders package unusable
What evidence do you have that kdeprint is unusable?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Note that this bug no longer applies, but is kept open as a dummy
britney-helping bug to avoid the package to reenter testing once
linux-2.6 is updated, in case nvidia-graphics-drivers is not in testing
then.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troub
What evidence do you have that 1.0-7174 is vulnerable?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Please mention which version you were upgrading from.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
reassign 382956 ftp.debian.org
thanks
Mozilla is a major package with over 35% installed base in
popcon. It shouldn't just be removed and leaving users without an
upgrade path.
This may be the case for Debian stable, but it's definitely not the case
for unstable. It's sad to leave users withou
Please provide a severity justification.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Does this bug reproduce for more than one user on that system?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Are you able to reproduce this bug in a current Debian release?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Please specify which binary package(s) is rendered unusable by this bug.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi,
I'm unable to reproduce this in testing. If this is the result of an
upgrade, please try to identify which package upgrade triggered the bug.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
As this prevents bug #372252 from
being fixed in testing, this will most probably result in nvidia-glx-legacy
being dropped from etch if new binary packages aren't made available soon.
This bug does not prevent #372252 from being fixed in testing. britney
is simply unhappy about introducing a
57 matches
Mail list logo
