search for: unfixed

A new version of pqR is now available at pqR-project.org, which fixes several bugs that are also present in the latest R Core patch release (r66002). A number of bugs found previously during pqR development are also unfixed in the latest R Core release. Here is the list of these bugs that are unfixed in r66002 (including documentation deficiencies), taken from the pqR bug fix and documentation update sections of the pqR NEWS file (pqR-project.org/NEWS.txt): o The documentation for c now says how the names for th...

Hello, Today I tried to upgrade from samba 4.0.0 to 4.0.3 on my test environment. I patched the source with the diffs patch-4.0.0-4.0.1.diffs, patch-4.0.1-4.0.2.diffs, patch-4.0.2-4.0.3.diffs , then make, make install. # samba-tool dbcheck Checking 807 objects Not fixing nTSecurityDescriptor on CN=Performance Monitor Users,CN=Builtin,DC=inview,DC=local <--- all errors were

Hi, about an year ago i was reporting a bug in mailbox aliases, which remains unfixed and unasnwered (probably totally ignored, don't understand why). I thought it was because the bug is old and already fixed but yesterday i upgraded to Dovecot 2.2.24 and problem persists. Here is the original report, everything, except the Dovecot version, is still correct: http://doveco...

...at 5:09 PM, Talin <viridia at gmail.com> wrote: > So this was working fine for me until a few days ago when I checked out the > most recent LLVM - the one with the new type system. Now I am getting the > same error that I was getting previously. > Is it possible that your fix got unfixed when they merged in the new branch? I wouldn't be surprised if something broke, but I would be surprised if it's exactly the same issue. It's crashing calling DIBuilder::createPointerType again? -Eli

Known issues: 1) Linux 'sleep 20' -- Unfixable before 2.5.0 (known work around) 2) HP/UX signal issue -- Patched and HP/UX 11 works in v2 3) SCO 2/ Native Compiler -- Unfixable before 2.5.0 (known work around) 4) NeXTStep -- Resynced, MAX_GROUPS vs NGROUPS unresolved (not major) 5) DG/UX regcomp/regexec -- Fixed. 6) Cray signal issues -- ??? 7) Solaris '$PATH' issue -- ??

...eaving that aside, sid doesn't seem to have all the security fixes which ought to be expected. * The BTS could do with a bit of gardening, perhaps. Please let me know what, if anything, you think you would like help with. FYI I also looked at security-tracker.debian.org pages for all the unfixed vulnerabilities in wheezy and jessie, and I think the decisions not to backport those fixes are reasonable in each case. Thanks, Ian.

...nsfer allows PV guest to elevate privileges [XSA-214]"): > Source: xen > Version: 4.4.1-9 > Severity: important > Tags: security upstream fixed-upstream > > See > https://xenbits.xen.org/xsa/advisory-214.html I have fixed these in stretch but the jessie package remains unfixed. I think I may be able to find some backports somewhere. Would that be useful ? Is anyone else working on this ? Ian.

...in <viridia at gmail.com> wrote: >> So this was working fine for me until a few days ago when I checked out the >> most recent LLVM - the one with the new type system. Now I am getting the >> same error that I was getting previously. >> Is it possible that your fix got unfixed when they merged in the new branch? > > I wouldn't be surprised if something broke, but I would be surprised > if it's exactly the same issue.  It's crashing calling > DIBuilder::createPointerType again? Did you ever make any progress narrowing this down? -Eli

...overwrite > core packages do so with little packages like sqlite (yum uses sqlite so > changing the version of it is not a Good Thing for system stabilty). > Other repos in that list have been effectively unmaintained for a number > of years so they contain packages that may have severe unfixed security > vulnerabilities. I suggest that we shouldn't use euphemisms when it's far more valuable to come out and say it. I would certainly appreciate if the centos docs explicitly tagged the other repos with these comments. Factual commentary about risks does not come anywhere close...

On Mon, 4 Nov 2019 at 14:07, David Newall <openssh at davidnewall.com> wrote: > [about scp] That's just awful, and I should have > thought it was not at all necessary. Am I missing something? > If you're saying that the scp protocol is an unfixable mess then the openssh team has been agreeing[0] with you for at least a decade and a half. We fix what we can, but some

Hi, I have three Iaxy devices (s101i) parts. Two of them seem to work fine. The third plays a loud repeating click sound when an analog phone is plugged in. I can provision all of them, and make calls to all of them. The clicking one will blink when a call is incoming, but no audio from the call can be heard on the handset, and the caller only hears silence. The same handset works on the

...m/np0s5hgM (you'll probably need to add quotes around the content) fromJSON returns the error glibc detected home/sguha/lib64/R/bin/exec/R: realloc(): invalid next size: 0x000000000209e210 *** Is there a fix coming soon? Maybe CRAN should also have an outstanding bug field - packages with unfixed bugs could be removed. Cheers Joy rjson- 0.2.3 and R.version _ platform x86_64-unknown-linux-gnu arch x86_64 os linux-gnu system x86_64, linux-gnu status major 2 minor 13.0 year 2011 month 04 day...

Looks to me like the first series of patches should be OK to post now. I propose that: 001-apply-to-page-range.patch 001a-reboot-use-struct.patch 002-sync-bitops.patch 003-remove-ring0-assumptions.patch 004-abstract-asm.patch 005-cpuid-cleanup.patch unfix-fixmap.patch fixmap-bootparam.patch remove-read-hazard-from-cow.patch pte-clear-not-present.patch

Full_Name: Tom Callaway Version: 2.7.2 OS: Fedora 10 (Linux/x86_64) Submission from: (NULL) (96.233.67.230) Recently, Debian identified a security issue with the javareconf script in R. I confirmed that this is still unfixed in R 2.7.2. The following patch resolves the issue: diff -up R-2.7.2/src/scripts/javareconf.BAD R-2.7.1/src/scripts/javareconf --- R-2.7.2/src/scripts/javareconf.BAD 2008-08-29 11:04:21.000000000 -0400 +++ R-2.7.2/src/scripts/javareconf 2008-08-29 11:05:34.000000000 -0400 @@ -125,16 +125,17 @@ f...

I'm using dsync to synchronize emails on a laptop where wifi connectivity sometimes fails in the middle of a sync. I have a shell script that runs dsync, and here is one line of it including the output of dsync: + dsync -f -m realmail mirror /home/paulproteus/projects/ssh-attach/run ssh rose.makesad.us dsync dsync-local(paulproteus): Error: dbox

With respect to random testing LLVM pre-2.4 is doing extremely well, we have no unreported bugs right now. John

On Oct 10, 2008, at 2:06 PM, John Regehr wrote: > With respect to random testing LLVM pre-2.4 is doing extremely well, > we > have no unreported bugs right now. That's great John! For my info, are there any reported bugs that are unfixed in 2.4? -Chris

> For my info, are there any reported bugs that are unfixed in 2.4? Looks like there is one outstanding correctness bug (2697) and three crash bugs (2735, 2775, 2797). I haven't reverified these lately, though. John

...isters so far. Anyway, I'm > looking forward to your fix! I've commited the first series of patches to ToT to unbreak win64, basically: 1. Honour register save area 2. Enable proper passing of __m128 and __m64 arguments 3. Minor cleanups here and there The callee-saved problem is still unfixed, I'm working on general solution. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Moritz Muehlenhoff writes ("Re: Xen package security updates for jessie 4.4, XSA-213, XSA-214"): > On Thu, May 04, 2017 at 05:59:18PM +0100, Ian Jackson wrote: > > Should I put jessie-security in the debian/changelog and dgit push it > > (ie, from many people's pov, dput it) ? > > Yes, the distribution line should be jessie-security, but please send > a