search for: missing_fil

...readdir(PDIR); closedir(PDIR); foreach my $pf (@dents) { @@ -494,7 +494,6 @@ my $ver; my $oldpwd; - next if $pf =~ /^(\.|CVS$)/; if ($pf =~ /\.patch/) { # Patch file of a project: @@ -820,22 +819,22 @@ print "patch output was:\n$patch_output\n"; } if ($missing_files != 0) { - $self->{ERRMSG} .= "cannot apply ($missing_files missing files)\n"; + $self->{ERRMSG} .= "cannot apply $patchfile: ($missing_files missing files)\n"; return 0; # } elsif ($rejects*2 > $hunks) { } elsif ($rejects != 0) { - $self->{ERR...

Originally an attempt to fix: https://bugzilla.redhat.com/show_bug.cgi?id=1570407 However this isn't a complete fix. The OVA supplied doesn't even conform to VMware's own "specification" (I use the word loosely). The OVF inside the OVA references the disk.vmdk file, but the OVA doesn't contain that disk.vmdk file, only a snapshot called disk.vmdk.000000000. Therefore

https://bugzilla.mindrot.org/show_bug.cgi?id=2700 Bug ID: 2700 Summary: Missing PEM identity_file should be a fatal error Product: Portable OpenSSH Version: 7.2p2 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs

...ncy: php-pecl(Xdebug) is needed by package php-pear-PHPUnit2 Error: php-pecl-apc conflicts with php-mmcache Error: Missing Dependency: php = 4.3.9 is needed by package php-mmcache Error: php-eaccelerator conflicts with php-mmcache While dependency issues aren't too bad (e.g. "yum provides MISSING_FILE"), what is the best way to start going through and finding these conflicts? While this is just a test box, I'd like to get a handle on how to solve this sort of thing before I have the same problem on a production server. I see that CentOS plus in on here. Might that have to do with PHP...

...Error returns should describe all the information about an error that a client could reasonably use to recover from the error. This requirement goes beyond what a flat enum, or even an enum with a category (like std::error_code) is capable of expressing. For example, it is possible to express "missing_file" in an enum, but not "missing_file: /path/to/file". A library client could meaningfully respond to the latter by re-generating the file (if they knew how) and re-trying the operation. (3) There may be many levels of stack between the point where an error is raised, and the point wh...

https://bugzilla.redhat.com/show_bug.cgi?id=1570407 This turned into quite an in-depth refactoring of how we handle OVAs. It also fixes a potential security issue. Rich.

Hi Rafael, > What prevents you from using a diag handler in the jit server that > sends errors/warnings over the RPCChannel? What would you do with errors that can't reasonable be serialized when they reach the diagnostic handler? And what would you do with the serialized bytes on the client end? - Lang. Sent from my iPhone On Feb 10, 2016, at 10:31 AM, Rafael Espíndola