similar to: Updateinfo file is not valid XML

Displaying 20 results from an estimated 1000 matches similar to: "Updateinfo file is not valid XML"

2019 May 30
2
epel repository broken
Hello, I have now over two Days this errors on all my systems ? Updateinfo file is not valid XML: <open file '/var/cache/yum/x86_64/7/epel/ 92f2e15cad66d79ea1ad327e2af7af89d98e4d153d7a3e27ff41946f476af5b4- updateinfo.xml.zck', mode 'rt' at 0x7f464cf24420> a "yum clean all" dont't change the Problem! -- mit freundliche Gr??en / best regards, G?nther J.
2006 May 07
0
updateinfo and stale data
Hi, FreeBSD 5.4, NUT from ports (2.0.3), serial on /dev/cuaa1, Ellipse 1200 USBS. I set the ups.conf up as : [ellipse] driver=mge-utalk port=/dev/cuaa1 desc="Ellipse" When I go to start it I get : Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3) Could not get multiplier table: using raw
2017 Jan 13
1
yum --security check-update
Hi all, Does anyone know why when I run the following command, I get thousands of packages in the output, saying they've been excluded? [root at server yum.repos.d]# yum --security check-update | less Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.removed.com * epel: mirror.removed.com * extras: mirror.removed.com * updates: mirror.removed.com
2020 Jun 29
3
R 4.0.0 rebuild status
On Mon, 29 Jun 2020 at 14:25, Jos? Ab?lio Matos <jamatos at fc.up.pt> wrote: > > Again you guessed right, that was the main idea. :-) > As I told above and to reiterate it, the idea of this work is to make it easier to automate the > process. Similarly to how we do the mass builds for all the packages. But the mass rebuild process is very different, because releng doesn't
2005 Aug 19
0
updateinfo: cannot update system status
Dear all, I am trying to figure out the meaning of the following message: [root@hat ups]# /usr/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.85 (2.0.2) .Detected Evolution 2200 on /dev/ttyS0 updateinfo: Cannot update system status ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is an MGE pulsar evolution on ttyS0. Cheers,
2005 Nov 21
1
★男性は完全無料登録をして待つだ
$B!zCK@-$O40A4L5NAEPO?$r$7$FBT$D$@$1$G$9!#(B $B>/$74i$bA*$s$@J}$,$$$$$+$b!)!)$=$l$O$*G$$;$7$^$9!#(B http://www.00-love5.com/serebu/s.html $B!V(BYAHOO!$B!W!V(BGoogle$B!W$N8!:w7k2L$O$=$N%5%$%H$N?M5$!"(B $B?.MjEY!J%f!<%6!<$K$h$kEjI<!K$G=g0L$,7hDj$7$^$9!#(B $BEv%5%$%H$O8!:w%+%F%4%j(B $B!TAG?M%[%9%H!U$K$F%H%C%W%Z!<%8$G>R2p$5$l$F$$$^$9!#(B
2017 Jun 21
2
Problems with EPEL
I didn't want to join yet another mailing list.... Is anyone/everyone having issues? Our hourly cron job checking update is failing on EPEL: Updateinfo file is not valid XML: <open file '/var/cache/yum/x86_64/7/epel/gen/updateinfo.xml', mode 'rt' at 0x1dd46f0> When I try to look at it, it appears to have binary data in it. mark
2017 Nov 06
2
yum update info output
Hi all, when I check for updates with yum, it gives me a list of packages, with some additional info, e.g. --> systemd-sysv-219-42.el7_4.1.x86_64 from @updates removed (updateinfo) --> systemd-sysv-219-42.el7_4.4.x86_64 from updates removed (updateinfo) yum info will tell me that I have 4.1 of this package installed, and that 4.4 is available - from the repo updates. What is the
2015 Jan 06
2
When will CentOS Publish Errata?
> 1. Blatant screen scraping is a violation of the terms of service for RHN .. > so where is a SOURCE of information for something like this: > > https://rhn.redhat.com/errata/RHSA-2014-2024.html > > If you read this: > https://access.redhat.com/help/terms/ > > then, one can not just grab all the info on that errata page and distribute it .. > which is why we LINK
2015 Jan 06
2
When will CentOS Publish Errata?
On 01/06/2015 04:25 AM, Liam O'Toole wrote: > On 2015-01-06, Somers-Harris, David | David | OPS > <david.somers-harris at mail.rakuten.com> wrote: >>> 1. Blatant screen scraping is a violation of the terms of service >>> for RHN .. so where is a SOURCE of information for something like >>> this: >>> >>>
2015 Apr 08
4
Update only of security vulnerabilities?
Hi All :) What is the best way to get a list of available security updates? I found several commands for that: 1) yum updateinfo list updates -q --security 2) yum list-security --security -q 3) yum --security check-update -q Based on the sample output below I think I can use any of the three with some awk to get a list of packages. yum updateinfo list updates -q --security FEDORA-EPEL-2014-0525
2018 May 11
1
Centos7 update: epel no route to host
Hello All, I' have a laptop who's not booting to graphical screen today. Actualy I had several the last few days, related to cr repo. This one won't update, EM: updates | 3.4 kB 00:00:00 epel/x86_64/updateinfo FAILED https://mirror.ynet.sk/epel/7/x86_64/repodata/3ada5bcbccaa9772074a773b15bd01dd48e753a184ebecfed590de6c389ada03-updateinfo.xml.bz2: [Errno 14] curl#7 -
2006 Jul 24
1
Problems with MGE ESV 8+ and NUT 2.0.3
Hello, I recently had a failure with my old MGE ESV8 ups, it just died on me so I had to get a new one. I found a MGE ESV8+ cheap and everything seems to work fine with it except the communication with the computer. The old ESV8 (non +) worked fine with NUT after applying some patches I got from the mailing list, but I think they are in the source tree now. I'm using the same cable that
2017 Oct 10
1
yum security update issue
Hi all, I have used http://cefs.steve-meier.de/ plus https://github.com/vmfarms/generate_updateinfo to insert some security-information into my os-updates - mirror. This seems to work, but only partially. On my 7.4 test server, > yum --security -v check-update gives me dnsmasq, nss, nss-sysinit and nss-tools as the packages to install. The nss-packages are all of "severity =
2015 Jan 05
4
When will CentOS Publish Errata?
> However, luckily, Gmane archives everything just fine. > http://thread.gmane.org/gmane.linux.centos.devel/12370/focus=12375 Thanks Steven for bringing this thread to my attention. So it looks like there was already a discussion about this in September, and it ended with two action items. 1. Write code to automatically put the following into updateinfo.xml a. Link to RH web site b.
2015 Jan 06
1
When will CentOS Publish Errata?
On 2015-01-06, Somers-Harris, David | David | OPS <david.somers-harris at mail.rakuten.com> wrote: >> 1. Blatant screen scraping is a violation of the terms of service >> for RHN .. so where is a SOURCE of information for something like >> this: >> >> https://rhn.redhat.com/errata/RHSA-2014-2024.html >> >> If you read this:
2007 Apr 15
3
Fwd: Response from Canon - MultiPASS (KMM7153196V60774L0KM)
My apologies for this because it is, technically, OT, but it is a classic example of what rotten support Linux (and CentOS) get in the US from equipment manufacturers. The whole email is a lie because they DO have the drivers on their asia site, they just don't want us 'Murkins to get our hands on them. Or maybe it's part of some clever little nuance of their agreement with Micro$oft
2007 Aug 19
2
[LLVMdev] c const
Hi Christopher, On Friday 17 August 2007 19:42:31 Christopher Lamb wrote: > On Aug 16, 2007, at 9:09 AM, Chris Lattner wrote: > > On Thu, 16 Aug 2007, Holger Schurig wrote: > >>> if the programmer is going to tell you that the memory pointed > >>> to by a pointer argument is never written. > > If you use a const * __restrict pointer then you should get the
2006 Mar 28
2
Skewed t distribution
Dear All, I am working with skewed-t copula in my research recently, so I needed to write an mle procedure instead of using a standard fit one; I stick to the sn package. On subsamples of the entire population that I deal with, everything is fine. However, on the total sample (difference in cross-sectional dimension: 30 vs 240) things go wrong - the objective function diverges to infinity. I
2015 Jun 20
2
Finished a prototype of GSoC project: Implement a new doc toolchain
Hi, Kunaal and I have completed a prototype of the first part of our GSoC project (implement a new doc toolchain). Our goal is to implement a doc toolchain for short how-to docs and lower the barrier for new comers to contribute. This is the workflow of the prototype: 1. Contributor creates a new pull request on GitHub 2. A corresponding issue is automatically created on Pagure 3. Staff and