Re: Stable Release Updates types proposal
On Sat, Mar 13, 2010 at 07:58:03AM +, Terry Barnaby wrote:
> Last night I was helping some school kids with a powerpoint presentation
> they had written. They had, not un-reasoanbly, used FontWork titles.
> Under F12 with OpenOffice 3.1 it took 3 minutes to load the 10 slide file
> and about 1 minute between slides. Editing was basically impossible.
> I had to go back to a F8 system OpenOffice 2.x system to edit the FontWork
> out. How on earth did this "release" get out (Fedora/OpenOffice ??) ??
> This is just one of many basic issues I and others have had with Fedora
> recently.
And where is your bug report? Anyway, there is no justification for you
having used the wording that you used ('How on earth did this "release"
get out (Fedora/OpenOffice ??) ?? This is just one of many basic issues
I and others have had with Fedora recently.'), because:
1. Fontwork objects are 3-D objects, therefore the performance depends
on graphic driver, card and so on. I just checked it and it works
reasonably well on my machine (6-slide presentation with a fontwork
on each slide was loaded in 10 seconds and transition between slides
took a second at worst). That means there are users for whom it
works without problems.
2. This upstream bug: http://www.openoffice.org/issues/show_bug.cgi?id=58291
says someone had similar performance problems with fontwork in OO.o 2.0.
That means it's nothing new in 3.1 (and I personally doubt there
was much change in this area between 2.3 and 3.1).
3. Fontwork is just a very small piece of OO.o. Even if it had as poor
performance as you describe on _every_ system, it would hardly be a
blocker for release of OO.o and it's absolutely unimaginable it would be
a blocker for release of Fedora. That means it can hardly be described
as basic issue.
D.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re:saa716x module and unknown symbols
Try: cp saa716x*.ko /lib/modules/`uname -r`/extra/ demod 在2010-03-18 14:10:12，"Rodd Clarkson" 写道： >On Thu, 2010-03-18 at 12:32 +0800, Chen Lei wrote: > >> 在2010-03-18 10:18:06，"Rodd Clarkson" 写道： >> >I'm trying to test a v4l driver for an AverMedia Express Card. >> > >> >when I try and load the module dmesg reports: >> > >> >saa716x_core: Unknown symbol spi_alloc_master >> >saa716x_core: Unknown symbol spi_unregister_master >> >saa716x_core: Unknown symbol spi_register_master >> > >> >There seems to be hints that this should be in: >> > >> >/usr/include/linux/spi/spi.h >> > >> >but I can only find >> > >> >/usr/include/linux/spi/spidev.h >> > >> >Also, I see references to this in >> > >> >/usr/src/kernels/2.6.31.12-174.2.22.fc12.x86_64/include/linux/spi/spi.h >> > >> >which is part of kernel-devel. >> > >> >How do I get these symbols on my system? > >> You should compile saa716x module manually. >> See http://saa716x.sourceforge.net/ > >I've bumped into the site you mention in my searching, but there's isn't >really anything there. There's no files to download, not documentation >and no discussion. > >I've compile the saa716x modules manually from: >http://jusst.de/hg/saa716x/summary > >Having built these modules, I'm now getting the message about in dmesg >when I try to modprobe the modules. It appears that the Fedora kernel >isn't supplying the symbols above, but I don't know why not, or how to >add them to the mix. > > >Rodd > >-- >devel mailing list >devel@lists.fedoraproject.org >https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Re:saa716x module and unknown symbols
On Thu, 2010-03-18 at 12:32 +0800, Chen Lei wrote: > 在2010-03-18 10:18:06，"Rodd Clarkson" 写道： > >I'm trying to test a v4l driver for an AverMedia Express Card. > > > >when I try and load the module dmesg reports: > > > >saa716x_core: Unknown symbol spi_alloc_master > >saa716x_core: Unknown symbol spi_unregister_master > >saa716x_core: Unknown symbol spi_register_master > > > >There seems to be hints that this should be in: > > > >/usr/include/linux/spi/spi.h > > > >but I can only find > > > >/usr/include/linux/spi/spidev.h > > > >Also, I see references to this in > > > >/usr/src/kernels/2.6.31.12-174.2.22.fc12.x86_64/include/linux/spi/spi.h > > > >which is part of kernel-devel. > > > >How do I get these symbols on my system? > You should compile saa716x module manually. > See http://saa716x.sourceforge.net/ I've bumped into the site you mention in my searching, but there's isn't really anything there. There's no files to download, not documentation and no discussion. I've compile the saa716x modules manually from: http://jusst.de/hg/saa716x/summary Having built these modules, I'm now getting the message about in dmesg when I try to modprobe the modules. It appears that the Fedora kernel isn't supplying the symbols above, but I don't know why not, or how to add them to the mix. Rodd -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-13 Branched report: 20100317 changes
Chris Adams wrote: > It shouldn't be based on the sum, as that would mean positives for one > release could override negatives for another. That's kinda the whole point. "Kinda" because of course negatives should not be ignored, but that's always true, even if the positives are for the same release! They need to be checked for validity (e.g. longstanding breakage which is not a regression nor the one bug supposed to be fixed is not a valid reason to reject the update, but I've seen even more blatantly invalid complaints), and fixed if valid, not outvoted. (This just shows again how numeric karma is flawed. It's really stupid to rely on that number for anything serious.) But my point is that lack of positives for some release should indeed be ignored if there's enough positive feedback for the exact same update on some other release. > If you want to require simultaneous pushes, they should only be after > testing for each release is known good. First of all, I don't want to REQUIRE anything, but RECOMMEND things. We already have enough rules we're required to follow, and unfortunately more (and completely unnecessary ones at that) are coming soon. :-( And secondly, my suggestion is to assume that positive feedback on release n + no complaints on release m = the package is fine on release m as well (which has a probability very close to 1 in practice, especially if it's built from the same specfile in both cases). > Just because something works on F12 doesn't mean it doesn't break things > on F11. Theoretically yes, but in practice it's extremely unlikely. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning Packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maxim Burgerhout wrote: > I wouldn't mind doing dash, but as I am a relatively new packager and > this is a critical path package, (more experienced) co-maintainers > would be very welcome. > > I would like to co-maintain dash as well, as if that is ok. > Maxim Burgerhout > ma...@wzzrd.com > > GPG Fingerprint > EB11 5E56 E648 9D99 E8EF 05FB C513 6FD4 1302 B48A > > > > On Wed, Mar 17, 2010 at 21:35, Rahul Sundaram wrote: >> On 03/18/2010 02:01 AM, Jon Ciesla wrote: >>> Warren Togami wrote: >>> I am orphaning the following packages. Two look pretty important for someone else to save. NEWLY ORPHANED PACKAGES = dash (critical path, used by dracut) scponly (pretty important!) >>> Trying to take scponly, I keep getting Request Failed. >>> >> Same here. >> >> Rahul >> -- >> devel mailing list >> devel@lists.fedoraproject.org >> https://admin.fedoraproject.org/mailman/listinfo/devel >> - -- Regards, Huzaifa Sidhpurwala, RHCE, CCNA (IRC: huzaifas) IT Desktop R&D Lead. Global Help Desk, Pune (India) Phone: +91 20 4005 7322 (UTC +5.5) GnuPG Fingerprint: 3A0F DAFB 9279 02ED 273B FFE9 CC70 DCF2 DA5B DAE5 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org/ iD8DBQFLobPHzHDc8tpb2uURAjE/AJ9ifYCwhiXAt1KYrvW1oZiuMYaM7QCfdc4I CmlWVEaD7SavIeGNZ3gBDhM= =JNYA -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re:saa716x module and unknown symbols
You should compile saa716x module manually. See http://saa716x.sourceforge.net/ 在2010-03-18 10:18:06，"Rodd Clarkson" 写道： >I'm trying to test a v4l driver for an AverMedia Express Card. > >when I try and load the module dmesg reports: > >saa716x_core: Unknown symbol spi_alloc_master >saa716x_core: Unknown symbol spi_unregister_master >saa716x_core: Unknown symbol spi_register_master > >There seems to be hints that this should be in: > >/usr/include/linux/spi/spi.h > >but I can only find > >/usr/include/linux/spi/spidev.h > >Also, I see references to this in > >/usr/src/kernels/2.6.31.12-174.2.22.fc12.x86_64/include/linux/spi/spi.h > >which is part of kernel-devel. > >How do I get these symbols on my system? > > >R. > >PS. I hope this is the right place to ask, but if it isn't, then I'll >ask elsewhere. I'm asking here, because it appears that many distros >supply the symbols by default but fedora (which I use) doesn't. > > > >-- >devel mailing list >devel@lists.fedoraproject.org >https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-13 Branched report: 20100317 changes
Once upon a time, Kevin Kofler said: > PS: The main cause for this kind of problems is people insisting on separate > testing per release. IMHO updates should go out to all releases at the same > time, based on the sum of the testing done for all of them, then we won't > have such upgrade path problems, ever. It shouldn't be based on the sum, as that would mean positives for one release could override negatives for another. If you want to require simultaneous pushes, they should only be after testing for each release is known good. Just because something works on F12 doesn't mean it doesn't break things on F11. -- Chris Adams Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
saa716x module and unknown symbols
I'm trying to test a v4l driver for an AverMedia Express Card. when I try and load the module dmesg reports: saa716x_core: Unknown symbol spi_alloc_master saa716x_core: Unknown symbol spi_unregister_master saa716x_core: Unknown symbol spi_register_master There seems to be hints that this should be in: /usr/include/linux/spi/spi.h but I can only find /usr/include/linux/spi/spidev.h Also, I see references to this in /usr/src/kernels/2.6.31.12-174.2.22.fc12.x86_64/include/linux/spi/spi.h which is part of kernel-devel. How do I get these symbols on my system? R. PS. I hope this is the right place to ask, but if it isn't, then I'll ask elsewhere. I'm asking here, because it appears that many distros supply the symbols by default but fedora (which I use) doesn't. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-13 Branched report: 20100317 changes
I wrote: > Both fedora-easy-karma and fedora-packager are breaking upgrade paths, > this inheritance problem is just another side effect of that. The packages > have to be pushed to stable either simultaneously or in decreasing release > order. Both the fedora-packager maintainer and you: please queue your F13 > updates to stable ASAP to fix the upgrade path (which will also fix this > inheritance glitch). (And yes, fedora-packager needs to be pushed first, > that's the first offender here.) And next time please don't push out a F12 > update without pushing out the equivalent update for F13 first or at the > same time. PS: The main cause for this kind of problems is people insisting on separate testing per release. IMHO updates should go out to all releases at the same time, based on the sum of the testing done for all of them, then we won't have such upgrade path problems, ever. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: hal-storage-addon is now a separate package
On Wed, 2010-03-17 at 14:08 +, Matthew Garrett wrote: > On Wed, Mar 17, 2010 at 06:08:57AM -0400, Jon Masters wrote: > > > Thanks! I reported elsewhere to some virt. folks that it is also a CPU > > hog (in terms of waking up guests every two seconds to poll a virtual CD > > device that may almost never have "media"). They are going to look at > > fixing the qemu emulation so that virtualized drives can report media > > status without being polled. But this now yields two interim solutions, > > including either explicitly telling hal not to poll (I typically do this > > on all new installs under virt) or removing this package in the future. > > You'll still have issues with udisks polling if the session requests it, > so the qemu fix is still a good one. As long as they indicate that they > support async notification, everything should just work. Right, indeed and indeed. So it's on their radar. Jon. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-13 Branched report: 20100317 changes
Till Maas wrote: > On Wed, Mar 17, 2010 at 06:49:41PM +, Branched Report wrote: > >> fedora-easy-karma-0-0.3.20100306git00fc20aa.fc12.noarch requires >> fedora-packager >= 0:0.4.0 > > This is unexpected behaviour of Fedora for me. Why is the package from > F12 automatically added to the F13 repo? The current situation is, that > I did not push fedora-easy-karma from testing to stable in F13, because > fedora-packager >= 0.4.0 is still in testing there, but it is in stable > in F12, which is why I only pushed it to stable for F12 now. Both fedora-easy-karma and fedora-packager are breaking upgrade paths, this inheritance problem is just another side effect of that. The packages have to be pushed to stable either simultaneously or in decreasing release order. Both the fedora-packager maintainer and you: please queue your F13 updates to stable ASAP to fix the upgrade path (which will also fix this inheritance glitch). (And yes, fedora-packager needs to be pushed first, that's the first offender here.) And next time please don't push out a F12 update without pushing out the equivalent update for F13 first or at the same time. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning kadu
W dniu 18.03.2010 00:23, Dominik 'Rathann' Mierzejewski pisze: > On Thursday, 18 March 2010 at 00:15, Julian Sikorski wrote: > [...] >> I was thinking about taking this, but since I'm primarily a >> Gnome/empathy user I guess I'm not the most optimal choice. On the other >> hand, I could update kadu to the latest version in the meantime. This >> would mean updating libgadu as well, though. > > There have been complaints on forum.fedora.pl already, so if you think > it's a non-disruptive update then go ahead. libgadu has been updated > already. It's in updates-testing at the moment, but if you give it a +1 > karma, then it'll get pushed to stable. Otherwise I will push it in a day > or two. > > Regards, > R. > I'll try to get it done tomorrow, last time I looked the kadu spec looked very convoluted. Julian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning kadu
On Thursday, 18 March 2010 at 00:15, Julian Sikorski wrote: [...] > I was thinking about taking this, but since I'm primarily a > Gnome/empathy user I guess I'm not the most optimal choice. On the other > hand, I could update kadu to the latest version in the meantime. This > would mean updating libgadu as well, though. There have been complaints on forum.fedora.pl already, so if you think it's a non-disruptive update then go ahead. libgadu has been updated already. It's in updates-testing at the moment, but if you give it a +1 karma, then it'll get pushed to stable. Otherwise I will push it in a day or two. Regards, R. -- Fedora http://fedoraproject.org/wiki/User:Rathann RPMFusion http://rpmfusion.org | MPlayer http://mplayerhq.hu "Faith manages." -- Delenn to Lennier in Babylon 5:"Confessions and Lamentations" -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Feature Owners: Beta Freeze is 2010-03-23 :: Features must be at 100% complete
Hello Feature People, According to our schedule, six days from today is Beta Freeze for Fedora 13. https://fedoraproject.org/wiki/Releases/13/Schedule https://fedoraproject.org/wiki/Beta_Freeze_Policy At Beta Freeze it is expected that all features are 100% complete. Features that are not at 100% complete at Beta Freeze will be sent to FESCo for further review. Please take time now to update your feature page to reflect all of the work completed for Fedora 13. Unfinished items can be rolled forward to a new page for Fedora 14. A friendly reminder that the feature pages list below are not at 100% complete: https://fedoraproject.org/wiki/Anaconda/Features/StorageFiltering https://fedoraproject.org/wiki/Features/BetterWebcamSupportF13 https://fedoraproject.org/wiki/Features/boot.fedoraproject.org https://fedoraproject.org/wiki/Features/ColorManagement https://fedoraproject.org/wiki/Features/Gnome2.30 https://fedoraproject.org/wiki/Features/IntelliJ_IDEA https://fedoraproject.org/wiki/Features/Moblin-2.2 https://fedoraproject.org/wiki/Features/ModprobeWhitelist https://fedoraproject.org/wiki/Features/MultipathInstall https://fedoraproject.org/wiki/Features/Python3F13 https://fedoraproject.org/wiki/Features/SystemRollbackWithBtrfs https://fedoraproject.org/wiki/Features/SystemtapStaticProbes https://fedoraproject.org/wiki/Features/Sugar_0.88 https://fedoraproject.org/wiki/Features/Upstart0.6.0 https://fedoraproject.org/wiki/Features/UserAccountDialog https://fedoraproject.org/wiki/Features/Virtx2apic https://fedoraproject.org/wiki/Features/YumLangpackPlugin https://fedoraproject.org/wiki/Features/Zarafa ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning kadu
W dniu 17.03.2010 18:13, Dominik 'Rathann' Mierzejewski pisze: > On Wednesday, 17 March 2010 at 10:54, Dawid Gajownik wrote: >> Hi, >> >> after changing job and place of living I have no more time to maintain >> kadu, sorry. That's the main reason why I have decided to orphan this >> package. > > I have a potential maintainer for this package, but he's not sponsored > yet. I'm willing to sponsor him after he gets acquainted with our packaging > guidelines, however, so if anyone wants to step up as maintainer now, > be aware that there's a willing (co-)maintainer in making. :) > > Regards, > R. > I was thinking about taking this, but since I'm primarily a Gnome/empathy user I guess I'm not the most optimal choice. On the other hand, I could update kadu to the latest version in the meantime. This would mean updating libgadu as well, though. Julian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: your favourite method of dealing with ssh brute force attacks
On Wed, 2010-03-17 at 22:55 +0100, Michał Piotrowski wrote: > I recetly had 30 hours of ssh brute force attack on my system. I'm > using strong passwords, but still can be geneated from /dev/random, so > I switched to rsa authentication. What's your favourite way to deal > with such attacks? Please describe pros and cons. off-topic, but here's a few: run ssh on a high, non-standard port, implement a portknocker, only work with certificates (not passwords), set PermitRootLogin to no in your sshd config, obfuscate your username(s), etc. Léon -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: libssh2 F11 update breaks Fedora 12 DVD update
Bruno Wolff III wrote: > Are you sure about that? I am pretty sure that adding custom repositories > has been available for a few releases. Only for installs, not for upgrades. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: your favourite method of dealing with ssh brute force attacks
2010/3/17 Eric Sandeen : > Michał Piotrowski wrote: >> Hi, >> >> I recetly had 30 hours of ssh brute force attack on my system. I'm >> using strong passwords, but still can be geneated from /dev/random, so >> I switched to rsa authentication. What's your favourite way to deal >> with such attacks? Please describe pros and cons. >> >> Regards, >> Michal > > Aside from not allowing password logins, I throttle them, they usually > get tired and go away to an easier target. > > -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -m limit > --limit 1/minute --limit-burst 2 -j ACCEPT If I understand correctly - this limits ssh connections to two connections per minute. I tried it before on my devel server without success. I tried it now with your configuration also without success. I used -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -m limit --limit 2/minute --limit-burst 2 -j ACCEPT and I still can connect to ssh as many times as I want. > > > -Eric Regards, Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: main problems of fedora?
Gergely Buday wrote: > is there a list of known deficiencies of fedora - I mean those which > can be cured by developing new software, rather than fixing bugs? Or, > if such list does not exist, can you name a few missing item from > fedora? Think of relatively small would-be software, without a GUI. There's always that big security hole in the installer – more of an RFE than a bug, and over eleven years old now. Anaconda can download and install packages from the network, but it doesn't check whether they have been tampered with. This hits upgrading particularly hard, because upgrading from a DVD is broken without updates and insecure if updates are included, and Preupgrade will also remain insecure until this gets addressed. https://bugzilla.redhat.com/show_bug.cgi?id=998 Björn Persson signature.asc Description: This is a digitally signed message part. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [389-devel] DN normalisation design document
On 03/17/2010 01:13 PM, Andrey Ivanov wrote: In order to support "Old DN format including DN in the double quotes" another cn=config switch may be necessary. It seems there was recently a new switch introduced to make the dn syntax validation a little more "relaxed" - nsslapd-dn-validate-strict. Maybe this one could be used to allow for DNs with double-quoted values? Actually, the way how we are going to handle the old style 'dn: ="",' is converting the old style to a new style in the normalization when the server receives DNs from clients and the converted new style DN is used in the rest of the process. The nsslapd-dn-validate-strict value is examined in the DN syntax validation code for now. Unless we change it, the DN syntax validation code always receives the new DN style. Ok. What i wanted to say is that we should avoid any new config parameters in cn=config. The way you propose to handle the problem is the best one - it is completely transparent to the user, the server back-end "sees" only the normalised DNs so it does not complain and no additional configuration parameters are necessary. That being said, are you suggesting if nsslapd-dn-validate-strict is on, we should not convert an old style DN to a new style? That'd be really strict. I'm leaning toward to the other side accepting the both old and new style with no restriction. Do you see any disadvantages in allowing the old style? No, absolutely not, i agree completely with your reasoning. The code should be strict but not completely rigid :) Taking care of the "legacy" presentation in a transparent manner is the ideal solution. Thanks so much for the confirmation, Andrey. I'm working on the issue based on the design... --noriko smime.p7s Description: S/MIME Cryptographic Signature -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: your favourite method of dealing with ssh brute force attacks
Michał Piotrowski wrote: > Hi, > > I recetly had 30 hours of ssh brute force attack on my system. I'm > using strong passwords, but still can be geneated from /dev/random, so > I switched to rsa authentication. What's your favourite way to deal > with such attacks? Please describe pros and cons. > > Regards, > Michal Aside from not allowing password logins, I throttle them, they usually get tired and go away to an easier target. -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -m limit --limit 1/minute --limit-burst 2 -j ACCEPT -Eric -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: your favourite method of dealing with ssh brute force attacks
On Wed, Mar 17, 2010 at 11:06 PM, Orion Poplawski wrote: > On 03/17/2010 03:55 PM, Michał Piotrowski wrote: >> Hi, >> >> I recetly had 30 hours of ssh brute force attack on my system. I'm >> using strong passwords, but still can be geneated from /dev/random, so >> I switched to rsa authentication. What's your favourite way to deal >> with such attacks? Please describe pros and cons. > > This really is off-topic here. > > -- > Orion Poplawski > Technical Manager 303-415-9701 x222 > NWRA/CoRA Division FAX: 303-415-9702 > 3380 Mitchell Lane or...@cora.nwra.com > Boulder, CO 80301 http://www.cora.nwra.com > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel I agree -- Athmane Madjoudj -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: your favourite method of dealing with ssh brute force attacks
2010/3/17 Athmane Madjoudj : > 2010/3/17 Michał Piotrowski : >> Hi, >> >> I recetly had 30 hours of ssh brute force attack on my system. I'm >> using strong passwords, but still can be geneated from /dev/random, so >> I switched to rsa authentication. What's your favourite way to deal >> with such attacks? Please describe pros and cons. >> >> Regards, >> Michal >> -- >> devel mailing list >> devel@lists.fedoraproject.org >> https://admin.fedoraproject.org/mailman/listinfo/devel >> > > 1. Change SSH port I don't have a remote access to my cisco router, so I can't change port forwarding - sigh. > 2. Disable access to root via SSH Actually I need this to deploy my project. I'll change this someday, but it will take some time to tweak configuration. > 3. Install HIDS eg: fail2ban is included in fedora OR BFD > (http://www.rfxn.com/projects/brute-force-detection/) I'm not sure if I want to blindly ban networks. > > > -- > Athmane Madjoudj > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel Regards, Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: your favourite method of dealing with ssh brute force attacks
On Wed, 17 Mar 2010 22:55:48 +0100 Michał Piotrowski wrote: > Hi, > > I recetly had 30 hours of ssh brute force attack on my system. I'm > using strong passwords, but still can be geneated from /dev/random, so > I switched to rsa authentication. What's your favourite way to deal > with such attacks? Please describe pros and cons. > > Regards, > Michal 'denyhosts' is in Fedora as well and works great. Use AllowUser lines in your global ssh configuration and only allow known good users / source addresses (if that's possible in your setup). Regards, -- Conrad Meyer -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: your favourite method of dealing with ssh brute force attacks
On 03/17/2010 03:55 PM, Michał Piotrowski wrote: > Hi, > > I recetly had 30 hours of ssh brute force attack on my system. I'm > using strong passwords, but still can be geneated from /dev/random, so > I switched to rsa authentication. What's your favourite way to deal > with such attacks? Please describe pros and cons. This really is off-topic here. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: your favourite method of dealing with ssh brute force attacks
2010/3/17 Michał Piotrowski : > Hi, > > I recetly had 30 hours of ssh brute force attack on my system. I'm > using strong passwords, but still can be geneated from /dev/random, so > I switched to rsa authentication. What's your favourite way to deal > with such attacks? Please describe pros and cons. > > Regards, > Michal > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > 1. Change SSH port 2. Disable access to root via SSH 3. Install HIDS eg: fail2ban is included in fedora OR BFD (http://www.rfxn.com/projects/brute-force-detection/) -- Athmane Madjoudj -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
your favourite method of dealing with ssh brute force attacks
Hi, I recetly had 30 hours of ssh brute force attack on my system. I'm using strong passwords, but still can be geneated from /dev/random, so I switched to rsa authentication. What's your favourite way to deal with such attacks? Please describe pros and cons. Regards, Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[389-devel] Please review: Bug 573375 - MODRDN operation not logged
Hi, Please review the patch for this bug: https://bugzilla.redhat.com/show_bug.cgi?id=573375 Patch: https://bugzilla.redhat.com/attachment.cgi?id=400890&action=edit https://bugzilla.redhat.com/attachment.cgi?id=400890&action=diff Fix description: The slapi_log_access() should be invoked using LDAP_DEBUG_STATS, LDAP_DEBUG_STATS2, or LDAP_DEBUG_ARGS level. Thanks. -- Endi S. Dewata -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: F-13 Branched report: 20100317 changes
>> hornsey-1.5.2-0.1.fc13.i686 requires libclutter-gst-0.10.so.0 This is a known issue and should be resolved shortly. Its part of 'Moblin' and well the whole state is in 'flux'. watch this (well maybe not this one) space basically more will be known soon! >> pyclutter-gst-0.9.2-1.fc12.i686 requires >> libclutter-gst-0.10.so.0 I'll look at this one as well if no one else does. > Is anybody working on these, or should releng be taking a crack at it? Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning Packages
I wouldn't mind doing dash, but as I am a relatively new packager and this is a critical path package, (more experienced) co-maintainers would be very welcome. Maxim Burgerhout ma...@wzzrd.com GPG Fingerprint EB11 5E56 E648 9D99 E8EF 05FB C513 6FD4 1302 B48A On Wed, Mar 17, 2010 at 21:35, Rahul Sundaram wrote: > On 03/18/2010 02:01 AM, Jon Ciesla wrote: >> Warren Togami wrote: >> >>> I am orphaning the following packages. Two look pretty important for >>> someone else to save. >>> >>> NEWLY ORPHANED PACKAGES >>> = >>> dash (critical path, used by dracut) >>> scponly (pretty important!) >>> >>> >> Trying to take scponly, I keep getting Request Failed. >> > Same here. > > Rahul > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-13 Branched report: 20100317 changes
On Wed, 2010-03-17 at 17:01 -0400, Bill Nottingham wrote: > Bruno Wolff III (br...@wolff.to) said: > > > > fedora-easy-karma-0-0.3.20100306git00fc20aa.fc12.noarch > > > > requires fedora-packager >= 0:0.4.0 > > > > > > This is unexpected behaviour of Fedora for me. Why is the package from > > > F12 automatically added to the F13 repo? The current situation is, that > > > I did not push fedora-easy-karma from testing to stable in F13, because > > > fedora-packager >= 0.4.0 is still in testing there, but it is in stable > > > in F12, which is why I only pushed it to stable for F12 now. > > > > dist-f13 inherits from dist-f12-updates so once something makes it to > > F12 stable it will start showing up in F13. > > ... although we may be changing this behavior shortly. Jesse? > > Bill ngggh. I killed the inheritance for all the existing packages, but new packages can still sneak through, as there is nothing already tagged in dist-f13. This is something of a difficult problem. We want the packages and ownership and other info to be inherited forward, just not the build tags. I'm going to have to think on this for a bit. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: main problems of fedora?
On Wed, Mar 17, 2010 at 21:48:40 +0100, Gergely Buday wrote: > I'm a notorius functional programmer and look for a task that > certainly has users. Then engineering services is a good area to look. The autoQA project probably could use assistance. Infrastructure and release engineering are other places to look for projects to do for Fedora that might have that kind of task on their wish lists. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-13 Branched report: 20100317 changes
Bruno Wolff III (br...@wolff.to) said: > > > fedora-easy-karma-0-0.3.20100306git00fc20aa.fc12.noarch requires > > > fedora-packager >= 0:0.4.0 > > > > This is unexpected behaviour of Fedora for me. Why is the package from > > F12 automatically added to the F13 repo? The current situation is, that > > I did not push fedora-easy-karma from testing to stable in F13, because > > fedora-packager >= 0.4.0 is still in testing there, but it is in stable > > in F12, which is why I only pushed it to stable for F12 now. > > dist-f13 inherits from dist-f12-updates so once something makes it to > F12 stable it will start showing up in F13. ... although we may be changing this behavior shortly. Jesse? Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: main problems of fedora?
I'm a notorius functional programmer and look for a task that certainly has users. - Gergely 2010/3/17, Bruno Wolff III : > On Wed, Mar 17, 2010 at 19:32:06 +0100, > Gergely Buday wrote: >> Hi there, >> >> is there a list of known deficiencies of fedora - I mean those which >> can be cured by developing new software, rather than fixing bugs? Or, >> if such list does not exist, can you name a few missing item from >> fedora? Think of relatively small would-be software, without a GUI. > > I don't think there is any global list of such things. Various SIGs may have > wish lists. > > Can you explain more about why you want such a list? > -- Mobilkészülékről küldve -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning Packages
On 03/18/2010 02:01 AM, Jon Ciesla wrote: > Warren Togami wrote: > >> I am orphaning the following packages. Two look pretty important for >> someone else to save. >> >> NEWLY ORPHANED PACKAGES >> = >> dash (critical path, used by dracut) >> scponly (pretty important!) >> >> > Trying to take scponly, I keep getting Request Failed. > Same here. Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-13 Branched report: 20100317 changes
On Wed, Mar 17, 2010 at 21:12:33 +0100, Till Maas wrote: > On Wed, Mar 17, 2010 at 06:49:41PM +, Branched Report wrote: > > > fedora-easy-karma-0-0.3.20100306git00fc20aa.fc12.noarch requires > > fedora-packager >= 0:0.4.0 > > This is unexpected behaviour of Fedora for me. Why is the package from > F12 automatically added to the F13 repo? The current situation is, that > I did not push fedora-easy-karma from testing to stable in F13, because > fedora-packager >= 0.4.0 is still in testing there, but it is in stable > in F12, which is why I only pushed it to stable for F12 now. dist-f13 inherits from dist-f12-updates so once something makes it to F12 stable it will start showing up in F13. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning Packages
Warren Togami wrote: > I am orphaning the following packages. Two look pretty important for > someone else to save. > > NEWLY ORPHANED PACKAGES > = > dash (critical path, used by dracut) > scponly (pretty important!) > Trying to take scponly, I keep getting Request Failed. I'll try again later, but only if Toshio doesn't want it, who's already co-maintainer. > lrzip > perl-Finance-YahooQuote > > Warren > -- in your fear, seek only peace in your fear, seek only love -d. bowie -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: main problems of fedora?
On Wed, Mar 17, 2010 at 07:32:06PM +0100, Gergely Buday wrote: > is there a list of known deficiencies of fedora - I mean those which > can be cured by developing new software, rather than fixing bugs? Or, > if such list does not exist, can you name a few missing item from > fedora? Think of relatively small would-be software, without a GUI. Maybe there is something for you on the Fedora wishlist: https://fedoraproject.org/wiki/WishList Regards Till pgpexEyWzo3Z8.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [389-devel] DN normalisation design document
> > In order to support "Old DN format including DN in the double quotes" > another cn=config switch may be necessary. It seems there was recently a new > switch introduced to make the dn syntax validation a little more "relaxed" - > nsslapd-dn-validate-strict. Maybe this one could be used to allow for DNs > with double-quoted values? > > Actually, the way how we are going to handle the old style 'dn: > ="",' is converting the old style to a new style > in the normalization when the server receives DNs from clients and the > converted new style DN is used in the rest of the process. The > nsslapd-dn-validate-strict value is examined in the DN syntax validation > code for now. Unless we change it, the DN syntax validation code always > receives the new DN style. > > Ok. What i wanted to say is that we should avoid any new config parameters in cn=config. The way you propose to handle the problem is the best one - it is completely transparent to the user, the server back-end "sees" only the normalised DNs so it does not complain and no additional configuration parameters are necessary. That being said, are you suggesting if nsslapd-dn-validate-strict is on, we > should not convert an old style DN to a new style? That'd be really > strict. I'm leaning toward to the other side accepting the both old and new > style with no restriction. Do you see any disadvantages in allowing the old > style? > No, absolutely not, i agree completely with your reasoning. The code should be strict but not completely rigid :) Taking care of the "legacy" presentation in a transparent manner is the ideal solution. -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: libssh2 F11 update breaks Fedora 12 DVD update
On 3/17/10 3:40 PM, Rahul Sundaram wrote: > On 03/18/2010 12:45 AM, Kevin Kofler wrote: >> >> DVD upgrades are just broken by design and will stay broken until they start >> pulling in the updates repository. Right now, they don't even offer the >> option. >> > > They do. I was given no such option when performing an upgrade using the F13 Alpha DVD. This option only appeared for the full install. I seem to recall the same behavior for the F12 DVD. -- Braden McDaniel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-13 Branched report: 20100317 changes
On Wed, Mar 17, 2010 at 06:49:41PM +, Branched Report wrote: > fedora-easy-karma-0-0.3.20100306git00fc20aa.fc12.noarch requires > fedora-packager >= 0:0.4.0 This is unexpected behaviour of Fedora for me. Why is the package from F12 automatically added to the F13 repo? The current situation is, that I did not push fedora-easy-karma from testing to stable in F13, because fedora-packager >= 0.4.0 is still in testing there, but it is in stable in F12, which is why I only pushed it to stable for F12 now. Regards Till pgplAZv3UKeSt.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-13 Branched report: 20100317 changes
On Wed, 2010-03-17 at 18:49 +, Branched Report wrote: > doodle-0.6.7-5.fc12.i686 requires libextractor.so.1 > easystroke-0.5.2-1.fc13.i686 requires > libboost_serialization-mt.so.5 > fedora-easy-karma-0-0.3.20100306git00fc20aa.fc12.noarch > requires fedora-packager >= 0:0.4.0 > hornsey-1.5.2-0.1.fc13.i686 requires libclutter-gst-0.10.so.0 > linphone-2.1.1-4.fc12.i686 requires libortp.so.7 > pyclutter-gst-0.9.2-1.fc12.i686 requires > libclutter-gst-0.10.so.0 > zikula-module-menutree-2.2-1.fc13.noarch requires zikula >= > 0:1.2 > > Is anybody working on these, or should releng be taking a crack at it? -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: libssh2 F11 update breaks Fedora 12 DVD update
On 03/18/2010 12:45 AM, Kevin Kofler wrote: > > DVD upgrades are just broken by design and will stay broken until they start > pulling in the updates repository. Right now, they don't even offer the > option. > They do. Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: libssh2 F11 update breaks Fedora 12 DVD update
On Wed, Mar 17, 2010 at 20:15:36 +0100, Kevin Kofler wrote: > > DVD upgrades are just broken by design and will stay broken until they start > pulling in the updates repository. Right now, they don't even offer the > option. Are you sure about that? I am pretty sure that adding custom repositories has been available for a few releases. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rpms/perl-Expect/EL-5 .cvsignore, 1.6, 1.7 perl-Expect.spec, 1.6, 1.7 sources, 1.6, 1.7
Author: tremble
Update of /cvs/pkgs/rpms/perl-Expect/EL-5
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv31586
Modified Files:
.cvsignore perl-Expect.spec sources
Log Message:
Update to match F-13
Index: .cvsignore
===
RCS file: /cvs/pkgs/rpms/perl-Expect/EL-5/.cvsignore,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -p -r1.6 -r1.7
--- .cvsignore 21 Jul 2006 14:50:48 - 1.6
+++ .cvsignore 17 Mar 2010 19:39:14 - 1.7
@@ -1 +1 @@
-Expect-1.20.tar.gz
+Expect-1.21.tar.gz
Index: perl-Expect.spec
===
RCS file: /cvs/pkgs/rpms/perl-Expect/EL-5/perl-Expect.spec,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -p -r1.6 -r1.7
--- perl-Expect.spec15 Oct 2007 20:04:00 - 1.6
+++ perl-Expect.spec17 Mar 2010 19:39:14 - 1.7
@@ -1,6 +1,6 @@
Name: perl-Expect
-Version:1.20
-Release:1%{?dist}
+Version:1.21
+Release:4%{?dist}
Summary:Expect for Perl
Group: Development/Libraries
@@ -12,6 +12,7 @@ BuildRoot: %{_tmppath}/%{name}-%{ve
BuildArch: noarch
BuildRequires: perl(IO::Pty) >= 1.03
BuildRequires: perl(IO::Tty) >= 1.03
+BuildRequires: perl(ExtUtils::MakeMaker)
Requires: perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo
$version))
%description
@@ -55,6 +56,25 @@ rm -rf $RPM_BUILD_ROOT
%changelog
+* Mon Dec 7 2009 Stepan Kasal - 1.21-4
+- rebuild against perl 5.10.1
+
+* Sat Jul 25 2009 Fedora Release Engineering
- 1.21-3
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild
+
+* Thu Feb 26 2009 Fedora Release Engineering
- 1.21-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild
+
+* Wed Mar 05 2008 Tom "spot" Callaway - 1.21-1
+- update to 1.21
+
+* Wed Mar 05 2008 Tom "spot" Callaway - 1.20-2
+- rebuild for new perl
+
+* Mon Oct 15 2007 Tom "spot" Callaway - 1.20-1.1
+- correct license tag
+- add BR: perl(ExtUtils::MakeMaker)
+
* Fri Jul 21 2006 Jose Pedro Oliveira - 1.20-1
- Update to 1.20.
Index: sources
===
RCS file: /cvs/pkgs/rpms/perl-Expect/EL-5/sources,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -p -r1.6 -r1.7
--- sources 21 Jul 2006 14:50:48 - 1.6
+++ sources 17 Mar 2010 19:39:14 - 1.7
@@ -1 +1 @@
-9134ae3778285bcf8c3ffdba1a177886 Expect-1.20.tar.gz
+a151b0dc4d1a35c73941c65b7c26da5b Expect-1.21.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Python SIG
I noticed that there's an effort to better organize the various Special Interest Groups in Fedora: https://fedorahosted.org/fedora-engineering-services/ticket/2 I noticed that although https://fedoraproject.org/wiki/SIGs/Python had "[[Category:Language-specific SIGs]]" we didn't have: "[[Category:SIGs]]" and so we weren't showing anywhere on that page. I've fixed this, and the page is now at least showing on the list at the bottom of: https://fedoraproject.org/wiki/Category:SIGs However, we're not in the hand-written list on that page, and I feel that we should be (hey, Ruby gets a mention, why can't we :) ) Any ideas what the summary info for the SIG should be? At the risk of plagiarism, Ruby's says: "A SIG for people who are interested in improving the state of Ruby in Fedora. This includes packaging Ruby libraries and applications, setting and improving standards for packaging them as RPM's and maintaining Ruby packages for Fedora." and that might be a good first start, but I'd also include the runtime as well as libraries and applications - I don't want people to feel that the runtime is somehow sacrosanct (just more care required!). How about this: "A SIG for people who are interested in Python on Fedora. This includes packaging and optimizing the various Python 2 and Python 3 runtimes (CPython, Jython), packaging libraries and applications, setting and improving standards for packaging them as RPM's and maintaining Python packages for Fedora." (somewhat copied from Ruby) I think the various questions on the F-E-S ticket are good ones. I'm willing to do some work towards some of that ticket, but any help would be welcome. Thoughts? Dave ___ python-devel mailing list python-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/python-devel
Orphaning Packages
I am orphaning the following packages. Two look pretty important for someone else to save. NEWLY ORPHANED PACKAGES = dash (critical path, used by dracut) scponly (pretty important!) lrzip perl-Finance-YahooQuote Warren -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: libssh2 F11 update breaks Fedora 12 DVD update
Harald Hoyer wrote: > On the F12 install DVD we have libssh2-1.2-2.fc12. > > A fully updated F11 will have libssh2 with a higher version. Apparently > anaconda force updates some packages, if you update with the F12 DVD, but > not the libssh2 package, which will lead to a broken yum, because > python-curl needs libcurl, which needs libssh2. > > But the libssh2 from F11 needs libssl.so.8 which is not available anymore > on the system (anaconda force update of openssl??). So yum does not run > anymore. The non-technical user ends up with a broken system. > > Solution? DVD upgrades are just broken by design and will stay broken until they start pulling in the updates repository. Right now, they don't even offer the option. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: libssh2 F11 update breaks Fedora 12 DVD update
Conrad Meyer wrote:
> F-{N} GA DVD will never intentionally work as an update against F-{N-1} +
> Updates, unless you enable F-{N} Updates also (and then it should work).
Except the DVD does not support that for upgrades, making DVD upgrades
entirely useless as long as this is not fixed.
Kevin Kofler
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
[pkgdb] perl-Finance-YahooQuote ownership changed
Package perl-Finance-YahooQuote in Fedora 6 was orphaned by wtogami To make changes to this package see: https://admin.fedoraproject.org/pkgdb/packages/name/perl-Finance-YahooQuote -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-Finance-YahooQuote ownership changed
Package perl-Finance-YahooQuote in Fedora 7 was orphaned by wtogami To make changes to this package see: https://admin.fedoraproject.org/pkgdb/packages/name/perl-Finance-YahooQuote -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-Finance-YahooQuote ownership changed
Package perl-Finance-YahooQuote in Fedora 9 was orphaned by wtogami To make changes to this package see: https://admin.fedoraproject.org/pkgdb/packages/name/perl-Finance-YahooQuote -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-Finance-YahooQuote ownership changed
Package perl-Finance-YahooQuote in Fedora 8 was orphaned by wtogami To make changes to this package see: https://admin.fedoraproject.org/pkgdb/packages/name/perl-Finance-YahooQuote -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-Finance-YahooQuote ownership changed
Package perl-Finance-YahooQuote in Fedora 10 was orphaned by wtogami To make changes to this package see: https://admin.fedoraproject.org/pkgdb/packages/name/perl-Finance-YahooQuote -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-Finance-YahooQuote ownership changed
Package perl-Finance-YahooQuote in Fedora 12 was orphaned by wtogami To make changes to this package see: https://admin.fedoraproject.org/pkgdb/packages/name/perl-Finance-YahooQuote -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-Finance-YahooQuote ownership changed
Package perl-Finance-YahooQuote in Fedora devel was orphaned by wtogami To make changes to this package see: https://admin.fedoraproject.org/pkgdb/packages/name/perl-Finance-YahooQuote -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-Finance-YahooQuote ownership changed
Package perl-Finance-YahooQuote in Fedora 11 was orphaned by wtogami To make changes to this package see: https://admin.fedoraproject.org/pkgdb/packages/name/perl-Finance-YahooQuote -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-Finance-YahooQuote ownership changed
Package perl-Finance-YahooQuote in Fedora 13 was orphaned by wtogami To make changes to this package see: https://admin.fedoraproject.org/pkgdb/packages/name/perl-Finance-YahooQuote -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: What is the future of logwatch?
On Wed, 17 Mar 2010 19:02:26 + Paul Howarth wrote: > On Wed, 17 Mar 2010 17:50:58 + > Frank Murphy wrote: > > > On 17/03/10 17:22, Karel Klic wrote: > > > > --snipped-- > > > > > Is it "logwatch" really enabled by default on Fedora? > > > > Currently you have to "yum install logwatch" with @live CD's install > > not sure about the DVD. > > The default install from the DVD installed it prior to F-12 but not in > F-12. Indeed, I gad to go and search for it explicitly when I realized I stopped seeing the reports in my inbox after the upgrade ... Simo. -- Simo Sorce * Red Hat, Inc * New York -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: What is the future of logwatch?
On Wed, 17 Mar 2010 17:50:58 + Frank Murphy wrote: > On 17/03/10 17:22, Karel Klic wrote: > > --snipped-- > > > Is it "logwatch" really enabled by default on Fedora? > > Currently you have to "yum install logwatch" with @live CD's install > not sure about the DVD. The default install from the DVD installed it prior to F-12 but not in F-12. Paul. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F-13 Branched report: 20100317 changes
Compose started at Wed Mar 17 09:15:24 UTC 2010 Broken deps for i386 -- doodle-0.6.7-5.fc12.i686 requires libextractor.so.1 easystroke-0.5.2-1.fc13.i686 requires libboost_serialization-mt.so.5 fedora-easy-karma-0-0.3.20100306git00fc20aa.fc12.noarch requires fedora-packager >= 0:0.4.0 hornsey-1.5.2-0.1.fc13.i686 requires libclutter-gst-0.10.so.0 linphone-2.1.1-4.fc12.i686 requires libortp.so.7 pyclutter-gst-0.9.2-1.fc12.i686 requires libclutter-gst-0.10.so.0 zikula-module-menutree-2.2-1.fc13.noarch requires zikula >= 0:1.2 Broken deps for x86_64 -- doodle-0.6.7-5.fc12.i686 requires libextractor.so.1 doodle-0.6.7-5.fc12.x86_64 requires libextractor.so.1()(64bit) easystroke-0.5.2-1.fc13.x86_64 requires libboost_serialization-mt.so.5()(64bit) fedora-easy-karma-0-0.3.20100306git00fc20aa.fc12.noarch requires fedora-packager >= 0:0.4.0 hornsey-1.5.2-0.1.fc13.x86_64 requires libclutter-gst-0.10.so.0()(64bit) linphone-2.1.1-4.fc12.i686 requires libortp.so.7 linphone-2.1.1-4.fc12.x86_64 requires libortp.so.7()(64bit) pyclutter-gst-0.9.2-1.fc12.x86_64 requires libclutter-gst-0.10.so.0()(64bit) zikula-module-menutree-2.2-1.fc13.noarch requires zikula >= 0:1.2 New package fedora-easy-karma Fedora update feedback made easy New package lldpad Intel LLDP Agent New package perl-CatalystX-LeakChecker Debug memory leaks in Catalyst applications New package perl-Context-Preserve Run code after a subroutine call, preserving context New package rubygem-maruku Maruku is a Markdown-superset interpreter written in Ruby New package scantailor An interactive post-processing tool for scanned pages Updated Packages: anjal-0.3.2-1.fc13 -- * Fri Mar 05 2010 Peter Robinson 0.3.2-1 - Official upstream 0.3.2 release tarball - Add patch to fix explicit dso linking. Fixes 564934 audacious-plugins-2.2-25.fc13 - * Thu Mar 04 2010 Michael Schwendt - 2.2-25 - Update icon popup patch for new playlist API to also fix a double-free (which made the popup crash with streaming audio). * Tue Mar 02 2010 Michael Schwendt - 2.2-24 - Patch notification area status icon (fix popup and title changes). clutter-gst-1.0.0-1.fc13 * Fri Mar 05 2010 Peter Robinson 1.0.0-1 - New upstream 1.0.0 stable release - Enable introspection support eclipse-rse-3.1.1-3.fc13 * Thu Feb 25 2010 Jeff Johnston 3.1.1-3 - Resolves: #567874 - Remove oro requirement as it is not needed. embryo-0.9.9.050-3.fc12 --- ibus-anthy-1.2.0.20100313-1.fc13 * Fri Mar 12 2010 Takao Fujiwara - 1.2.0.20100313-1 - Update to 1.2.0.20100313 - Update fr.po * Fri Mar 12 2010 Takao Fujiwara - 1.2.0.20100312.1-1 - Update to 1.2.0.20100312.1 - Minor fix for a translation * Fri Mar 12 2010 Takao Fujiwara - 1.2.0.20100312-1 - Update to 1.2.0.20100312 - Fix bug 564268 - Crash with enabled global input method ibus-table-1.2.0.20100111-7.fc13 * Wed Mar 10 2010 Caius 'kaio' Chance - 1.2.0.20100111-7 - Add template.txt in files. * Wed Mar 10 2010 Caius 'kaio' Chance - 1.2.0.20100111-6 - Disable -additional. * Wed Mar 10 2010 Caius 'kaio' Chance - 1.2.0.20100111-5 - Remove -additional for obsoletion by ibus-table-latin and ibus-table-code. pgadmin3-1.10.2-1.fc13 -- * Mon Mar 15 2010 Devrim GUNDUZ 1.10.2-1 - Update to 1.10.2 pgbouncer-1.3.2-1.fc13 -- * Tue Mar 16 2010 Devrim GÜNDÜZ - 1.3.2-1 - Update to 1.3.2, per changes described in: - http://pgfoundry.org/frs/shownotes.php?release_id=1605 python-4Suite-XML-1.0.2-9.fc13 -- * Fri Feb 26 2010 Miloslav Trmač - 1.0.2-9 - Don't use "as" identifier in the test suite Resolves: #564872 - Point URL: to something that doesn't fail with 503 - Update source URL qemu-0.12.3-6.fc13 -- * Mon Mar 15 2010 Justin M. Forbes - 2:0.12.3-6 - Detect cdrom via ioctl (#473154) - re add increased buffer for USB control requests (#546483) rabbitmq-server-1.7.2-1.fc13 * Mon Feb 15 2010 Matthew Sackman 1.7.2-1 - New Upstream Release * Fri Jan 22 2010 Matthew Sackman 1.7.1-1 - New Upstream Release shapelib-1.2.10-2.20100216cvs.fc13 -- * Fri Feb 19 2010 Lucian Langa - 1.2.10-2.20100216cvs - update patch0-3 fix undefined symbols system-config-printer-1.1.93-6.fc13 --- * Mon Mar 08 2010 Jiri Popelka 1.1.93-6 - Fixed pycups to be more cautious when removing the Connection object from the list (bug #567386). * Wed Mar 03 2010 Tim Waugh - 1.1.93-5 - Added comments for all sources and patches. -
Re: main problems of fedora?
On Wed, 17 Mar 2010, Gergely Buday wrote: > Hi there, > > is there a list of known deficiencies of fedora - I mean those which > can be cured by developing new software, rather than fixing bugs? Or, > if such list does not exist, can you name a few missing item from > fedora? Think of relatively small would-be software, without a GUI. > One of the new initatives in Fedora is called Fedora Engineering Services - http://fedoraproject.org/wiki/Fedora_Engineering_Services If you're a fast learner who just wants to work on various technical and other issues but don't care what, sign up. We can always use more help. -Mike -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: main problems of fedora?
On Wed, Mar 17, 2010 at 19:32:06 +0100, Gergely Buday wrote: > Hi there, > > is there a list of known deficiencies of fedora - I mean those which > can be cured by developing new software, rather than fixing bugs? Or, > if such list does not exist, can you name a few missing item from > fedora? Think of relatively small would-be software, without a GUI. I don't think there is any global list of such things. Various SIGs may have wish lists. Can you explain more about why you want such a list? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
main problems of fedora?
Hi there, is there a list of known deficiencies of fedora - I mean those which can be cured by developing new software, rather than fixing bugs? Or, if such list does not exist, can you name a few missing item from fedora? Think of relatively small would-be software, without a GUI. - Gergely -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: What is the future of logwatch?
On 17/03/10 17:22, Karel Klic wrote: --snipped-- > Is it "logwatch" really enabled by default on Fedora? Currently you have to "yum install logwatch" with @live CD's install not sure about the DVD. --snipped-- -- Regards, Frank Murphy UTF_8 Encoded, Fedora 12, 13, Rawhide: x86_64 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: What is the future of logwatch?
Hi Yaakov, please see below. On 03/16/2010 10:31 PM, Yaakov Nemoy wrote: > Hey List, > > In the org that i work for, we use logwatch for log monitoring. Since > puppet is too new to have a module in logwatch, i've had the 'joy' > recently of attempting to write a functional module. In doing so, i > have a number of issues i would like to bring up about logwatch in > Fedora (and RHEL/CentOS). > > To begin with, like a good netizen, i sent a message to the mailing > list upstream. So far i've heard no reply. There's the chance that it > got caught in my spam filter, but i've gotten one message from the ML > already. It feels like upstream is dead. There has also been no > release since 2007. Since it still 'just works' i won't bring out the > fire and brimstone and demand it be removed, but i would like to know, > how are we going to support this? Yes, the upstream is almost dead. Nevertheless I believe if someone (anyone) starts to be active on their mailing list, it will make things move again in a good direction. If it does not, it makes sense to do a fork, because a _lot_ of people use the package, send patches, and improve logwatch in a long run. I have had this in my todo list since 5 months or so, even promising it to a colleague of mine that time. Unfortunately there are still things with higher priority to be done. If you can help and devote some time to logwatch, then we should cooperate. > This question is important in the context of the issues i had > programming for logwatch. A well programmed tool maintains orthogonal > features in an orthogonal way. I ran into some serious bugs while > trying to develop a robust module. Logwatch has two modes, one for a > machine with a single set of logs, and one for generating reports for > a machine with multiple logs, namely your centralised logging box. The > snippets of code that filter the logs you want to analyse allow you to > control for the date range and the machine the logged event was > generated on. When trying to code for the puppet logs, my code > ultimately only worked on the single nodes, but crapped out on our > logging box. After debugging the issue, it's obvious that it's doing > some prefiltering per host that is occluding all the puppet logs, when > the 'splithosts' feature is enabled. Extending and maintaining this > package is going to be difficult without a willing maintainer. If this > is just something that needs a bug report, i would appreciate if the > package maintainer, according to zodbot Karel Klíč, could speak up on > this. Extending and maintaining a package are two different things. I believe that discussing some programming issues and source code design is out of scope for Fedora maintainer role. It would be too much work to do it for every package. > If no one is willing to maintain logwatch, i would like to ask why is > it enabled by default? For most environments, logwatch is > ignored/disabled in lieu of other solutions.People who use logwatch > seriously are already aware of its presence and will enable it when > disabled. They are also generaly experts, and from my experience been > around the sysadmin block quite a few times. For the non-expert user, > discussions of target audience aside, either they know about logwatch, > and perhaps keep an eye on it, or will never find it. I refer to the > fact that the only way to know about logwatch on a running system is > that innocous "you've got mail in /var/spool/mail/root' message. Then > you have to know to open up your mbox, which in my case means > installing mutt which is not installed by default, and read it, and > then know it's logwatch, and realize what it's there for. There are > 'expert tips' i've seen that remind newbs to check logwatch on their > own machines, but if this is something important, it should be more > obvious, and if it's not so important, why is it enabled by default? Is it really enabled by default on Fedora? It should not be enabled in a desktop spin, and Fedora currently has no server spin. If logwatch is installed and enabled on some spin one day, this should be documented in the deployment guide, so inexperienced users can read about the presence of logwatch, and how to use it. I am willing to write something if others feel it's necessary. > I'm not going to bike shed, so i'm not going to ask for any particular > action. We don't have the time in our organisation to take up > maintenance of logwatch, so we clearly are going to look for another > solution. Still, i would like to ask the persons who made the decision > to enable this by default, is it still relevant? Or is it something > that's in danger of becoming cruft? Am i missing a certain perspective > on why it's enabled by default? > > -Yaakov Best regards, Karel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning kadu
On Wednesday, 17 March 2010 at 10:54, Dawid Gajownik wrote: > Hi, > > after changing job and place of living I have no more time to maintain > kadu, sorry. That's the main reason why I have decided to orphan this > package. I have a potential maintainer for this package, but he's not sponsored yet. I'm willing to sponsor him after he gets acquainted with our packaging guidelines, however, so if anyone wants to step up as maintainer now, be aware that there's a willing (co-)maintainer in making. :) Regards, R. -- Fedora http://fedoraproject.org/wiki/User:Rathann RPMFusion http://rpmfusion.org | MPlayer http://mplayerhq.hu "Faith manages." -- Delenn to Lennier in Babylon 5:"Confessions and Lamentations" -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 477426] [monafont] Please convert to new font packaging guidelines
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=477426 Mamoru Tasaka changed: What|Removed |Added Status|MODIFIED|CLOSED Resolution||CURRENTRELEASE --- Comment #9 from Mamoru Tasaka 2010-03-17 12:43:16 EDT --- Once closing. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
rpms/perl-IO-Socket-SSL/F-13 .cvsignore, 1.22, 1.23 perl-IO-Socket-SSL.spec, 1.27, 1.28 sources, 1.22, 1.23
Author: pghmcfc
Update of /cvs/pkgs/rpms/perl-IO-Socket-SSL/F-13
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv21889
Modified Files:
.cvsignore perl-IO-Socket-SSL.spec sources
Log Message:
Update to 1.33
Index: .cvsignore
===
RCS file: /cvs/pkgs/rpms/perl-IO-Socket-SSL/F-13/.cvsignore,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -p -r1.22 -r1.23
--- .cvsignore 27 Sep 2009 21:01:01 - 1.22
+++ .cvsignore 17 Mar 2010 16:43:49 - 1.23
@@ -1 +1 @@
-IO-Socket-SSL-1.31.tar.gz
+IO-Socket-SSL-1.33.tar.gz
Index: perl-IO-Socket-SSL.spec
===
RCS file: /cvs/pkgs/rpms/perl-IO-Socket-SSL/F-13/perl-IO-Socket-SSL.spec,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -p -r1.27 -r1.28
--- perl-IO-Socket-SSL.spec 7 Dec 2009 10:54:01 - 1.27
+++ perl-IO-Socket-SSL.spec 17 Mar 2010 16:43:49 - 1.28
@@ -4,8 +4,8 @@
#
Name: perl-IO-Socket-SSL
-Version: 1.31
-Release: 2%{?dist}
+Version: 1.33
+Release: 1%{?dist}
Summary: Perl library for transparent SSL
Group: Development/Libraries
License: GPL+ or Artistic
@@ -42,8 +42,8 @@ done
%{__rm} -rf %{buildroot}
%{__make} pure_install PERL_INSTALL_ROOT=%{buildroot}
/usr/bin/find %{buildroot} -type f -name .packlist -exec %{__rm} -f {} ';'
-/usr/bin/find %{buildroot} -depth -type d -exec /bin/rmdir {} 2>/dev/null ';'
-%{__chmod} -R u+w %{buildroot}/*
+/usr/bin/find %{buildroot} -depth -type d -exec /bin/rmdir {} ';' 2>/dev/null
+%{_fixperms} %{buildroot}
%check
# Avoid running the session tests (spawns servers, requires 3 free ports
@@ -61,8 +61,17 @@ done
%{_mandir}/man3/IO::Socket::SSL.3pm*
%changelog
+* Wed Mar 17 2010 Paul Howarth - 1.33-1
+- Update to 1.33
+ - attempt to make t/memleak_bad_handshake.t more stable
+ - fix hostname checking: only check an IP against subjectAltName GEN_IPADD
+
+* Tue Feb 23 2010 Paul Howarth - 1.32-1
+- Update to 1.32 (die in Makefile.PL if Scalar::Util has no dualvar support)
+- Use %%{_fixperms} macro instead of our own %%{__chmod} incantation
+
* Mon Dec 7 2009 Stepan Kasal - 1.31-2
-- rebuild against perl 5.10.1
+- Rebuild against perl 5.10.1
* Sun Sep 27 2009 Paul Howarth - 1.31-1
- Update to 1.31 (see Changes for details)
Index: sources
===
RCS file: /cvs/pkgs/rpms/perl-IO-Socket-SSL/F-13/sources,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -p -r1.22 -r1.23
--- sources 27 Sep 2009 21:01:01 - 1.22
+++ sources 17 Mar 2010 16:43:49 - 1.23
@@ -1 +1 @@
-3a51c3f603ee242d5869e8ffd51b989b IO-Socket-SSL-1.31.tar.gz
+e288b5cda3de1f4cbf15e2eb709e9d7c IO-Socket-SSL-1.33.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
rpms/perl-DBIx-Class/devel perl-DBIx-Class.spec,1.25,1.26
Author: cweyl
Update of /cvs/extras/rpms/perl-DBIx-Class/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv18603
Modified Files:
perl-DBIx-Class.spec
Log Message:
* Wed Mar 17 2010 Chris Weyl 0.08120-2
- update F::A::MT so bits marked as "no_index" are filtered both for provides
_and_ requires
- update by Fedora::App::MaintainerTools 0.006
- additional deps script run; 27 deps found
Index: perl-DBIx-Class.spec
===
RCS file: /cvs/extras/rpms/perl-DBIx-Class/devel/perl-DBIx-Class.spec,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -p -r1.25 -r1.26
--- perl-DBIx-Class.spec17 Mar 2010 16:32:28 - 1.25
+++ perl-DBIx-Class.spec17 Mar 2010 16:34:21 - 1.26
@@ -94,9 +94,9 @@ BuildRequires: perl(namespace::clean) >=
%filter_provides_in %{perl_vendorlib}/DBIx/Class/SQLAHacks
%filter_requires_in %{perl_vendorlib}/DBIx/Class/SQLAHacks
%filter_from_provides /^perl(DBIx::Class::SQLAHacks)/d
-%filter_From_requires /^perl(DBIx::Class::SQLAHacks)/d
+%filter_from_requires /^perl(DBIx::Class::SQLAHacks)/d
%filter_from_provides /^perl(DBIx::Class::Storage::DBIHacks)/d
-%filter_From_requires /^perl(DBIx::Class::Storage::DBIHacks)/d
+%filter_from_requires /^perl(DBIx::Class::Storage::DBIHacks)/d
%perl_default_filter
}
%{?perl_default_subpackage_tests}
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
rpms/perl-DBIx-Class/devel auto.ini, 1.2, 1.3 perl-DBIx-Class.spec, 1.24, 1.25
Author: cweyl
Update of /cvs/extras/rpms/perl-DBIx-Class/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv17696
Modified Files:
auto.ini perl-DBIx-Class.spec
Log Message:
* Wed Mar 17 2010 Chris Weyl 0.08120-2
- update F::A::MT so bits marked as "no_index" are filtered both for provides
_and_ requires
- update by Fedora::App::MaintainerTools 0.006
- additional deps script run; 27 deps found
Index: auto.ini
===
RCS file: /cvs/extras/rpms/perl-DBIx-Class/devel/auto.ini,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- auto.ini4 Mar 2010 08:14:06 - 1.2
+++ auto.ini17 Mar 2010 16:32:28 - 1.3
@@ -1,33 +1,11 @@
[add_build_requires]
-; FIXME -- these all need to be rechecked to ensure that we're not just
-; duplicating the find_optional_requires script
-;
; optional tests
-perl(DateTime::Format::MySQL)=0
perl(Text::CSV_XS)=0
-perl(Test::Memory::Cycle)=0
-perl(Test::Pod)=0
-perl(Test::Pod::Coverage)=0
-perl(SQL::Translator)=0
-perl(DateTime)=0
-perl(DateTime::Format::Oracle)=0
-perl(DBIx::ContextualFetch)=0
-; optional tests as of 0.08102
-perl(Clone)=0
-perl(Time::Piece)=0
-perl(Time::Piece::MySQL)=0
-; .. the following are also needed as a requires for replicated dbd support
-perl(MooseX::AttributeHelpers)=0.12
-perl(Class::MOP)=0.63
-perl(Moose)=0.54
-perl(Moose::Util::TypeConstraints)=0.54
-; CDBI-compat tests...
-perl(Class::Data::Inheritable)=0
perl(Class::Inspector)=1.24
-perl(Class::Trigger)=0
;
perl(Test::Moose)=0
[metadata_filtering]
-; this wouldn't be an issue if we'd filter dupes in perl_default_filter
+; Note that maintainertool automatically generates filter macro statements for
+; packages/directories marked as "no_index" in META.yml.
filter_from_requires=/^perl(DBD::Pg)$/d
Index: perl-DBIx-Class.spec
===
RCS file: /cvs/extras/rpms/perl-DBIx-Class/devel/perl-DBIx-Class.spec,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -p -r1.24 -r1.25
--- perl-DBIx-Class.spec17 Mar 2010 01:09:33 - 1.24
+++ perl-DBIx-Class.spec17 Mar 2010 16:32:28 - 1.25
@@ -1,7 +1,7 @@
Name: perl-DBIx-Class
Summary:Extensible and flexible object <-> relational mapper
Version:0.08120
-Release:1%{?dist}
+Release:2%{?dist}
License:GPL+ or Artistic
Group: Development/Libraries
Source0:
http://search.cpan.org/CPAN/authors/id/R/RI/RIBASUSHI/DBIx-Class-%{version}.tar.gz
@@ -14,45 +14,28 @@ BuildRequires: perl >= 1:5.6.1
BuildRequires: perl(Carp::Clan) >= 6.0
BuildRequires: perl(Class::Accessor::Grouped) >= 0.09002
BuildRequires: perl(Class::C3::Componentised) >= 1.0005
-BuildRequires: perl(Class::Data::Inheritable)
BuildRequires: perl(Class::Inspector) >= 1.24
-BuildRequires: perl(Class::MOP) >= 0.63
-BuildRequires: perl(Class::Trigger)
-BuildRequires: perl(Clone)
BuildRequires: perl(Context::Preserve) >= 0.01
BuildRequires: perl(CPAN)
BuildRequires: perl(Data::Dumper::Concise) >= 1.000
BuildRequires: perl(Data::Page) >= 2.00
-BuildRequires: perl(DateTime)
-BuildRequires: perl(DateTime::Format::MySQL)
-BuildRequires: perl(DateTime::Format::Oracle)
BuildRequires: perl(DBD::SQLite) >= 1.25
BuildRequires: perl(DBI) >= 1.609
-BuildRequires: perl(DBIx::ContextualFetch)
BuildRequires: perl(ExtUtils::MakeMaker) >= 6.42
BuildRequires: perl(File::Temp) >= 0.22
BuildRequires: perl(Module::Find) >= 0.06
-BuildRequires: perl(Moose) >= 0.98
-BuildRequires: perl(Moose::Util::TypeConstraints) >= 0.54
-BuildRequires: perl(MooseX::AttributeHelpers) >= 0.12
BuildRequires: perl(MRO::Compat) >= 0.09
BuildRequires: perl(Path::Class) >= 0.18
BuildRequires: perl(Scope::Guard) >= 0.03
BuildRequires: perl(SQL::Abstract) >= 1.61
BuildRequires: perl(SQL::Abstract::Limit) >= 0.13
-BuildRequires: perl(SQL::Translator) >= 0.11002
BuildRequires: perl(Sub::Name) >= 0.04
BuildRequires: perl(Test::Builder) >= 0.33
BuildRequires: perl(Test::Exception)
-BuildRequires: perl(Test::Memory::Cycle)
BuildRequires: perl(Test::Moose)
BuildRequires: perl(Test::More) >= 0.92
-BuildRequires: perl(Test::Pod)
-BuildRequires: perl(Test::Pod::Coverage)
BuildRequires: perl(Test::Warn) >= 0.21
BuildRequires: perl(Text::CSV_XS)
-BuildRequires: perl(Time::Piece)
-BuildRequires: perl(Time::Piece::MySQL)
Requires: perl(Carp::Clan) >= 6.0
Requires: perl(Class::Accessor::Grouped) >= 0.09002
@@ -103,11 +86,17 @@ BuildRequires: perl(namespace::clean) >=
%{?filter_from_requires: %filter_from_requires /^perl(DBD::Pg)$/d }
%{?perl_default_filter:
%filter_provides_in %{perl_vendorlib}/DBIx/Class/Admin
+%filter_requires_in %{perl_vendorlib}/DBIx/Class/Admin
%filter_provides_in %{perl_vendorlib}/DBIx/Class/CDBICompat
+%filter_requires_in %{perl_vendorlib}/DBIx/Class/CDBICompat
%
rpms/perl-IO-Socket-SSL/devel .cvsignore, 1.23, 1.24 perl-IO-Socket-SSL.spec, 1.28, 1.29 sources, 1.23, 1.24
Author: pghmcfc
Update of /cvs/pkgs/rpms/perl-IO-Socket-SSL/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv14983
Modified Files:
.cvsignore perl-IO-Socket-SSL.spec sources
Log Message:
Update to 1.33
Index: .cvsignore
===
RCS file: /cvs/pkgs/rpms/perl-IO-Socket-SSL/devel/.cvsignore,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -p -r1.23 -r1.24
--- .cvsignore 23 Feb 2010 13:58:55 - 1.23
+++ .cvsignore 17 Mar 2010 16:23:38 - 1.24
@@ -1 +1 @@
-IO-Socket-SSL-1.32.tar.gz
+IO-Socket-SSL-1.33.tar.gz
Index: perl-IO-Socket-SSL.spec
===
RCS file: /cvs/pkgs/rpms/perl-IO-Socket-SSL/devel/perl-IO-Socket-SSL.spec,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -p -r1.28 -r1.29
--- perl-IO-Socket-SSL.spec 23 Feb 2010 13:58:55 - 1.28
+++ perl-IO-Socket-SSL.spec 17 Mar 2010 16:23:39 - 1.29
@@ -4,7 +4,7 @@
#
Name: perl-IO-Socket-SSL
-Version: 1.32
+Version: 1.33
Release: 1%{?dist}
Summary: Perl library for transparent SSL
Group: Development/Libraries
@@ -61,6 +61,11 @@ done
%{_mandir}/man3/IO::Socket::SSL.3pm*
%changelog
+* Wed Mar 17 2010 Paul Howarth - 1.33-1
+- Update to 1.33
+ - attempt to make t/memleak_bad_handshake.t more stable
+ - fix hostname checking: only check an IP against subjectAltName GEN_IPADD
+
* Tue Feb 23 2010 Paul Howarth - 1.32-1
- Update to 1.32 (die in Makefile.PL if Scalar::Util has no dualvar support)
- Use %%{_fixperms} macro instead of our own %%{__chmod} incantation
Index: sources
===
RCS file: /cvs/pkgs/rpms/perl-IO-Socket-SSL/devel/sources,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -p -r1.23 -r1.24
--- sources 23 Feb 2010 13:58:55 - 1.23
+++ sources 17 Mar 2010 16:23:40 - 1.24
@@ -1 +1 @@
-324ec02c26ecb41c481d0586c4174a56 IO-Socket-SSL-1.32.tar.gz
+e288b5cda3de1f4cbf15e2eb709e9d7c IO-Socket-SSL-1.33.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File IO-Socket-SSL-1.33.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-IO-Socket-SSL: e288b5cda3de1f4cbf15e2eb709e9d7c IO-Socket-SSL-1.33.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: F-13 Branched report: 20100316 changes
On Wed, 2010-03-17 at 11:00 +, Quentin Armitage wrote: > I have added a spec file and patches to > https://bugzilla.redhat.com/show_bug.cgi?id=10 which allow linphone > to build on F-13. > > The version has had to be updated to linphone-3.2.1 because ortp, on > which it depends, has been updated to 0.16.1. > > Can someone apply the updates and build it? I don't think I can take it > any further. I've got the patches applied and a build going, looks like the same thing has to be done for devel. Perhaps you should apply for co-maintainership Quentin? -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[389-devel] DN normalisation design document
Hi Noriko, i've read the design document http://directory.fedoraproject.org/wiki/Upgrade_to_New_DN_Format In order to support "Old DN format including DN in the double quotes" another cn=config switch may be necessary. It seems there was recently a new switch introduced to make the dn syntax validation a little more "relaxed" - nsslapd-dn-validate-strict. Maybe this one could be used to allow for DNs with double-quoted values? Here is the commit comment for that parameter : commit 0410819d48795fca4faf986cf8658c34c4d929e3 Author: Nathan Kinder Date: Wed May 13 11:12:11 2009 -0700 Add strict DN syntax enforcement option. The DN syntax has become more restrictive over time, and the current rules are quite strict. Strict adherence to the rules defined in RFC 4514, section 3, would likely cause some pain to client applications. Things such as spaces between the RDN components are not allowed, yet many people use them still since they were allowed in the previous specification outlined in RFC 1779. To deal with the special circumstances around validation of the DN syntax, a configuration attribute is provided named nsslapd-dn-validate-strict. This configuration attribute will ensure that the value strictly adheres to the rules defined in RFC 4514, section 3 if it is set to on. If it is set to off, the server will normalize the value before checking it for syntax violations. Our current normalization function was designed to handle DN values adhering to RFC 1779 or RFC 2253 Concerning the logic of escaping/unescaping/normalisation we could test how openldap behaves in each case (as you've made it in "DN HEX HEX" bug). For upgrades/migrations and double quotes in DNs: the two values may be left during the upgrade (just in case someone uses them as-is) and then an optional validation/cleaning script could be provided separately? The sensitive part here is the whole o-NetscapeRoot tree: console using and writing this type of values, replication agreement/management etc As for the "related bugs" section i think another bug should be added ( https://bugzilla.redhat.com/show_bug.cgi?id=199923), it concernes the same RFC4514 compliance. -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
rawhide report: 20100317 changes
Compose started at Wed Mar 17 08:15:19 UTC 2010 Broken deps for i386 -- easystroke-0.5.2-1.fc13.i686 requires libboost_serialization-mt.so.5 edje-0.9.93.063-1.fc14.i686 requires libembryo-ver-svn-05.so.0 emotion-0.1.0.042-5.fc12.i686 requires libecore_job.so.0 emotion-0.1.0.042-5.fc12.i686 requires libevas.so.0 emotion-0.1.0.042-5.fc12.i686 requires libecore.so.0 emotion-0.1.0.042-5.fc12.i686 requires libecore_fb.so.0 emotion-0.1.0.042-5.fc12.i686 requires libecore_x.so.0 emotion-0.1.0.042-5.fc12.i686 requires libecore_evas.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libecore_txt.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libecore_job.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libevas.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libecore.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libecore_fb.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libecore_imf_evas.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libefreet.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libecore_file.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libefreet_mime.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libecore_imf.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libecore_con.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libecore_ipc.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libedbus.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libehal.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libecore_x.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libedje.so.0 enlightenment-0.16.999.050-5.fc12.i686 requires libecore_evas.so.0 epsilon-0.3.0.012-9.fc12.i686 requires libecore_ipc.so.0 epsilon-0.3.0.012-9.fc12.i686 requires libevas.so.0 epsilon-0.3.0.012-9.fc12.i686 requires libecore.so.0 epsilon-0.3.0.012-9.fc12.i686 requires libecore_fb.so.0 epsilon-0.3.0.012-9.fc12.i686 requires libecore_file.so.0 epsilon-0.3.0.012-9.fc12.i686 requires libecore_con.so.0 epsilon-0.3.0.012-9.fc12.i686 requires libecore_x.so.0 epsilon-0.3.0.012-9.fc12.i686 requires libedje.so.0 epsilon-0.3.0.012-9.fc12.i686 requires libecore_evas.so.0 epsilon-xine-0.3.0.012-9.fc12.i686 requires libecore_ipc.so.0 epsilon-xine-0.3.0.012-9.fc12.i686 requires libevas.so.0 epsilon-xine-0.3.0.012-9.fc12.i686 requires libecore.so.0 epsilon-xine-0.3.0.012-9.fc12.i686 requires libecore_fb.so.0 epsilon-xine-0.3.0.012-9.fc12.i686 requires libecore_file.so.0 epsilon-xine-0.3.0.012-9.fc12.i686 requires libecore_con.so.0 epsilon-xine-0.3.0.012-9.fc12.i686 requires libecore_x.so.0 epsilon-xine-0.3.0.012-9.fc12.i686 requires libecore_evas.so.0 evolution-couchdb-0.3.2-2.fc13.i686 requires libcouchdb-glib-1.0.so.1 ewl-0.5.2.042-12.fc12.i686 requires libecore_txt.so.0 ewl-0.5.2.042-12.fc12.i686 requires libevas.so.0 ewl-0.5.2.042-12.fc12.i686 requires libecore.so.0 ewl-0.5.2.042-12.fc12.i686 requires libefreet.so.0 ewl-0.5.2.042-12.fc12.i686 requires libecore_file.so.0 ewl-0.5.2.042-12.fc12.i686 requires libefreet_mime.so.0 ewl-0.5.2.042-12.fc12.i686 requires libedje.so.0 ewl-devel-0.5.2.042-12.fc12.i686 requires libecore_txt.so.0 ewl-devel-0.5.2.042-12.fc12.i686 requires libevas.so.0 ewl-devel-0.5.2.042-12.fc12.i686 requires libecore.so.0 ewl-devel-0.5.2.042-12.fc12.i686 requires libecore_file.so.0 ewl-devel-0.5.2.042-12.fc12.i686 requires libedje.so.0 ewl-devel-0.5.2.042-12.fc12.i686 requires libecore_evas.so.0 hornsey-1.5.2-0.1.fc13.i686 requires libclutter-gst-0.10.so.0 inkscape-0.47-6.fc13.i686 requires libMagickCore.so.2 inkscape-0.47-6.fc13.i686 requires libMagick++.so.2 inkscape-view-0.47-6.fc13.i686 requires libMagick++.so.2 inkscape-view-0.47-6.fc13.i686 requires libMagickCore.so.2 linphone-2.1.1-4.fc12.i686 requires libortp.so.7 murmur-1.1.8-15.fc12.i686 requires libIce.so.33 murmur-1.1.8-15.fc12.i686 requires libIceUtil.so.33 openvas-libnasl-2.0.2-3.fc13.i686 requires libopenvas_hg.so.2 openvas-libnasl-2.0.2-3.fc13.i686 requires libopenvas.so.2 paperbox-0.4.4-2.fc12.i686 requires libtrackerclient.so.0 perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::Admin::Usage) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::Storage::DBI::Replicated::Types) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::ClassResolver::PassThrough) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::CDBICompat::Relation
How do i decrease the time mock takes?
hey, How would I decrease the time mock takes to rebuild my srpm? I read up this page[1] "The cached buildroots trick above is much faster than using squid alone, but you can also use squid in addition to the cached buildroots, particularly if you are at the slow end of an Internet connection." However, mock still takes a lot of time to update the cache here. How can i further speed it up? - Is there a reason why presto is disabled for mock? Can I use drpms (if they exist) to make mock faster? -- regards, Ankur - FAS : ankursinha ; franciscod @ Freenode - gpg --keyserver pgp.mit.edu --recv-keys 5E9BF638 signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Broken dependencies: perl-DBIx-Class
perl-DBIx-Class has broken dependencies in the rawhide tree: On x86_64: perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::Admin::Usage) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::Storage::DBI::Replicated::Types) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::ClassResolver::PassThrough) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::CDBICompat::Relationship) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::Admin::Types) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::Admin) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::Admin::Descriptive) On i386: perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::Admin::Usage) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::Storage::DBI::Replicated::Types) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::ClassResolver::PassThrough) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::CDBICompat::Relationship) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::Admin::Types) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::Admin) perl-DBIx-Class-0.08120-1.fc14.noarch requires perl(DBIx::Class::Admin::Descriptive) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: hal-storage-addon is now a separate package
On Wed, Mar 17, 2010 at 06:08:57AM -0400, Jon Masters wrote: > Thanks! I reported elsewhere to some virt. folks that it is also a CPU > hog (in terms of waking up guests every two seconds to poll a virtual CD > device that may almost never have "media"). They are going to look at > fixing the qemu emulation so that virtualized drives can report media > status without being polled. But this now yields two interim solutions, > including either explicitly telling hal not to poll (I typically do this > on all new installs under virt) or removing this package in the future. You'll still have issues with udisks polling if the session requests it, so the qemu fix is still a good one. As long as they indicate that they support async notification, everything should just work. -- Matthew Garrett | mj...@srcf.ucam.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: kernel bug or coincidence
On 03/15/2010 05:50 PM, Muayyad AlSadi wrote: > hello, > > I have experienced a failure like this twice on same day and once in another > day > > Call Trace: > ... > [] kernel_thread_helper+0x7 ... > > I have scrolled up and found that there is some sata errors > > ata1: limiting speed to > ata1.00: SATA link up ... > ... > this happened twice and it happened only with the updated kernel > > my yum logs shows > > Feb 15 00:35:35 Installed: kernel-PAE-2.6.30.10-105.2.23.fc11.i686 > > I'm now using the previous kernel for days and I've not encountered that error > and DeviceKit does not report any problem > > my current kernel is > uname -r > 2.6.30.10-105.2.16.fc11.i686.PAE > > here are images of the problem > > http://uppix.net/d/d/a/c4f09aa4209ac30230080fa5aa52d.jpg > > http://uppix.net/b/8/1/e1a430ab2a3e0bb7478feed74eb53.jpg > > http://uppix.net/0/0/c/667ca14c8b0da542cd92986de1cf7.jpg > Upgrade to Fedora 12 would be my first advice. And a dmesg would be useful too. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 574431] New: perl-Sys-SigAction - request for EL-5 branch
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: perl-Sys-SigAction - request for EL-5 branch https://bugzilla.redhat.com/show_bug.cgi?id=574431 Summary: perl-Sys-SigAction - request for EL-5 branch Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: perl-Sys-SigAction AssignedTo: andr...@bawue.net ReportedBy: trem...@tremble.org.uk QAContact: extras...@fedoraproject.org CC: andr...@bawue.net, fedora-perl-devel-l...@redhat.com Classification: Fedora I (tremble) am currently trying to get the various packages we use at work into EPEL, perl-Sys-SigAction is one of these packages. Would you be willing to add an EL branch for perl-Sys-SigAction, or alternatively I can maintain the EL branch. I am also willing to co-maintain the EL branch (and Fedora branches) if you would like. If you have no desire to maintain EL packages you may wish to add yourself to the http://fedoraproject.org/wiki/EPEL/ContributorStatusNo page so that we can simply make the CVS request in future. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: libssh2 F11 update breaks Fedora 12 DVD update
On Wednesday 17 March 2010 01:10:31 am Harald Hoyer wrote:
> On the F12 install DVD we have libssh2-1.2-2.fc12.
>
> A fully updated F11 will have libssh2 with a higher version. Apparently
> anaconda force updates some packages, if you update with the F12 DVD, but
> not the libssh2 package, which will lead to a broken yum, because
> python-curl needs libcurl, which needs libssh2.
>
> But the libssh2 from F11 needs libssl.so.8 which is not available anymore
> on the system (anaconda force update of openssl??). So yum does not run
> anymore. The non-technical user ends up with a broken system.
>
> Solution?
F-{N} GA DVD will never intentionally work as an update against F-{N-1} +
Updates, unless you enable F-{N} Updates also (and then it should work).
Regards,
--
Conrad Meyer
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 574409] New: request for perl-Net-SSH EPEL build
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: request for perl-Net-SSH EPEL build https://bugzilla.redhat.com/show_bug.cgi?id=574409 Summary: request for perl-Net-SSH EPEL build Product: Fedora EPEL Version: el5 Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: perl-Net-SSH AssignedTo: st...@silug.org ReportedBy: trem...@tremble.org.uk QAContact: extras...@fedoraproject.org CC: st...@silug.org, fedora-perl-devel-l...@redhat.com Classification: Fedora perl-Net-SSH seems to have an EPEL branch, but no builds Please could one be built and pushed, I'm willing to help co-maintain if this would be of use. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Problems in packaging kicad
On 03/17/2010 12:56 AM, Kevin Kofler wrote: > Tom "spot" Callaway wrote: >> - link fixes. Really, these libraries should be linked properly so they >> don't need the executable linking calls to be explicitly correct, but >> cmake gives me a headache. > > You can use target_link_libraries on a shared library just as well as on an > executable. Yeah, I tried that first, but cmake ignored it, and I have better things to do with my day than try to figure out someone's half-thought out make replacement. ~spot -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Problems in packaging kicad
Le Mercredi 17 Mars 2010 10:19:52, Terry Barnaby a écrit : > Another little change that is needed is that the package source file > "kicad-ld.conf" has the contents "/usr/lib64/kicad". It should be > "/usr/lib/kicad", otherwise it does not work correctly on 32bit > i686 platforms. > > The kicad.spec file edits this to "/usr/lib64/kicad" if for an x86_64 > platform. I don't know what I did to get the edited file instead of the source file in the sources... Thanks for pointing. Regards, Alain -- La version française des pages de manuel Linux http://manpagesfr.free.fr -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning DR17 and EFL
On Wed, Mar 17, 2010 at 01:30:01PM +0100, Christoph Wickert wrote: > It's ok if you are not willing to explain something to me, but you also > refused to explain it to your co-maintainer and others. Please explain > it at least to the readers of this list, so they can get picture of > what's going on. Please don not explain anymore here on this list. It is now obvious that there have been misunderstandings and if you want to resolve your conflict, please do this in private or ask for a mediator if you would like to have one. I could do this, but I believe you can do this yourself, after you have calmed down and maybe got some distance. Regards Till pgpdEi6glyilv.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Problems in packaging kicad
Le Mardi 16 Mars 2010 21:19:44, Tom "spot" Callaway a écrit : > On 03/16/2010 08:27 AM, Alain Portal wrote: > > Hi, > > > > I get some problem in packaging kicad. > > Linking fails, and I don't know how to solve. > > There is no problem if I compile without packaging. > > Well, I doubt that seriously. This code is a bit of a mess (but still > not as painful as chromium). > > Attached is a new spec file, and two patches that fix the problems which > were preventing it from building. Great job ;-) Thanks for your help! Regards, Alain -- La version française des pages de manuel Linux http://manpagesfr.free.fr -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning DR17 and EFL
Thomas, I don't want to go into details because I don't want a flame war, but the IRC backlogs prove you wrong in different ways. And still I wouldn't dare calling you a liar. Am Mittwoch, den 17.03.2010, 09:13 +0100 schrieb Thomas Janssen: > I'm sorry. but you *are* a liar. You proved it again that you don't > understand it like several times before. A lack of understanding is something completely different than a lie. If you accuse me of lying then you should at least prove this accusation, but again, you are not providing any details. Ether retract the "liar" or prove it. It's ok if you are not willing to explain something to me, but you also refused to explain it to your co-maintainer and others. Please explain it at least to the readers of this list, so they can get picture of what's going on. Regards, Christoph -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: rpms/remmina/F-13 import.log,1.1,1.2 remmina.spec,1.4,1.5
Am Mittwoch, den 17.03.2010, 12:47 +0100 schrieb Nicolas Mailhot: > > Le Mar 16 mars 2010 19:09, Christoph Wickert a écrit : > > > > Am Dienstag, den 16.03.2010, 19:08 +0100 schrieb Christoph Wickert: > >> With cvs-import you have no option to change the changes. > > > > s/change/check > > Of course you have it shows a diff with previous files and asks confirmation Thanks for that info, I didn't know that as I don't use cvs-import for updates. If it really shows a diff, I wonder why people repeatedly revert changes with cvs-import.sh. Regards, Christoph -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
KDE-SIG meeting report (11/2010)
This is a report of the weekly KDE-SIG-Meeting with a summary of the topics that were discussed. If you want to add a comment please reply to this email or add it to the related meeting page. -- = Weekly KDE Summary = Week: 11/2010 Time: 2010-03-16 14:00 UTC Meeting page: https://fedoraproject.org/wiki/SIGs/KDE/Meetings/2010-03-16 Meeting minutes: http://meetbot.fedoraproject.org/fedora-meeting/2010-03-16/kde- sig.2010-03-16-13.58.html Meeting log: http://meetbot.fedoraproject.org/fedora-meeting/2010-03-16/kde- sig.2010-03-16-13.58.log.html -- = Participants = * JaroslavReznik * KevinKofler * LukasTinkl * RexDieter * StevenParrish * ThanNgo * Ryan Rix * Eike Hein * ThomasJanssen -- = Agenda = * topics to discuss: o rrix blah'ing about dvd/liveimage kde-integration o qt-4.7.0-tp ready for devel/ import o kde-4.4.1 status o Triaging trips/tricks for commonly reported abrt bugs? o Target audience = Summary = rrix blah'ing about dvd/liveimage kde-integration * Fedora isn't seen as KDE distro, we need to improve it * Colin Walters is improving DVD experience o KDE comps o Some package splits o Firstboot dragging too much of Gnome * Ryan Rix to check current status, meaning of this effort qt-4.7.0-tp ready for devel/ import * qt-assistant-adp compat package imported * Issues o PyQt4/PyKDE4 broken * Rex Dieter to commit/build qt-4.7.0-tp1 in devel/ kde-4.4.1 status * Agreed: kde-4.4.1 is ready for stable updates Triaging trips/tricks for commonly reported abrt bugs? * Kevin Kofler is closing duplicates o Mostly KPixmapCache issue * We need better duplicates checks - Karel Klic is working on it Target audience [1] * KDE SIG meeting proposal to be discussed on mailing list -- = Next Meeting = http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2010-03-23 -- = Links = [1] https://fedoraproject.org/wiki/SIGs/KDE/KDE_Target_Audience -- Jaroslav Řezník Software Engineer - Base Operating Systems Brno Office: +420 532 294 275 Mobile: +420 731 455 332 Red Hat, Inc. http://cz.redhat.com/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: rpms/remmina/F-13 import.log,1.1,1.2 remmina.spec,1.4,1.5
Le Mar 16 mars 2010 19:09, Christoph Wickert a écrit : > > Am Dienstag, den 16.03.2010, 19:08 +0100 schrieb Christoph Wickert: >> With cvs-import you have no option to change the changes. > > s/change/check Of course you have it shows a diff with previous files and asks confirmation -- Nicolas Mailhot -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: libssh2 F11 update breaks Fedora 12 DVD update
On Wed, Mar 17, 2010 at 09:10:31AM +0100, Harald Hoyer wrote: >On the F12 install DVD we have libssh2-1.2-2.fc12. > >A fully updated F11 will have libssh2 with a higher version. Apparently >anaconda >force updates some packages, if you update with the F12 DVD, but not the >libssh2 >package, which will lead to a broken yum, because python-curl needs libcurl, >which needs libssh2. > >But the libssh2 from F11 needs libssl.so.8 which is not available anymore on >the >system (anaconda force update of openssl??). So yum does not run anymore. The >non-technical user ends up with a broken system. > >Solution? Do a network-enabled install with the updates repositories included. That should bring in the libssh2 from F-12 updates. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-13 Branched report: 20100316 changes
I have added a spec file and patches to https://bugzilla.redhat.com/show_bug.cgi?id=10 which allow linphone to build on F-13. The version has had to be updated to linphone-3.2.1 because ortp, on which it depends, has been updated to 0.16.1. Can someone apply the updates and build it? I don't think I can take it any further. Quentin Armitage On Tue, 2010-03-16 at 18:35 +, Branched Report wrote: > Compose started at Tue Mar 16 09:15:16 UTC 2010 > > Broken deps for i386 > -- > linphone-2.1.1-4.fc12.i686 requires libortp.so.7 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Conflicts in latest update
On Tue, 2010-03-16 at 13:44 +0100, Ralf Corsepius wrote: > On 03/16/2010 01:37 PM, Matěj Cepl wrote: > > Dne 16.3.2010 13:04, Jon Masters napsal(a): > >> I'd just add those gstreamer packages to my exclude config in yum for > >> the moment, if you don't want to deal with the breakage each time. Then > >> you can remove those excludes when the repos catch up with each other. > >> > >> /etc/yum.conf: > >> > >> exclude=gstreamer-plugins-bad-free gstreamer-plugins-good > > > > It's safer to use --skip-broken parameter of yum for awhile. > > Doesn't work in this particular case, because yum doesn't catch the file > conflicts this update causes. Right, that would be why I suggested the exclude and not skip-broken. I didn't file a bug because I thought this naming issue/conflict was well known by now. I've seen similar in the past, apologies for assuming. Jon. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: hal-storage-addon is now a separate package
On Tue, 2010-03-16 at 15:19 +, Matthew Garrett wrote: > Right now, installing hal will result in hald-addon-storage polling > removable devices from boot - even if nothing's paying attention. This > is a surprisingly large power consumption hit on modern systems. udisks > starts the polling on-demand, which is preferable, but some legacy > applications still require hal. > > I've just split hald-addon-storage out into its own package in rawhide. > If you need the hald-addon-storage functionality (ie, you rely on hal > for media change events) then please add an explicit depends on > hal-storage-addon. Thanks! I reported elsewhere to some virt. folks that it is also a CPU hog (in terms of waking up guests every two seconds to poll a virtual CD device that may almost never have "media"). They are going to look at fixing the qemu emulation so that virtualized drives can report media status without being polled. But this now yields two interim solutions, including either explicitly telling hal not to poll (I typically do this on all new installs under virt) or removing this package in the future. Jon. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Orphaning kadu
Hi, after changing job and place of living I have no more time to maintain kadu, sorry. That's the main reason why I have decided to orphan this package. Regards, Dawid -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Conflicts in latest update
On Wed, 17 Mar 2010 09:32:19 +0530, Ankur wrote: > On Tue, 2010-03-16 at 21:46 +0100, Michael Schwendt wrote: > > On Tue, 16 Mar 2010 15:46:16 -0400, James wrote: > > > > > Rpmfusion can run auto QA like tests on rpmfusion and Fedora (I don't > > > think we can legally do the same ... but I'm not sure). Finding the file > > > conflicts automatically is harder (you need to download all the rpms), > > > and it's not fast, but it's possible (Seth has a script, IIRC). > > > > I've created and published a proof-of-concept script a couple of times > > before. It's the one I've used to file all those bugs about conflicts > > in Rawhide. > > http://mschwendt.fedorapeople.org/confcheck-remote-split2.py > > (that's a more experimental version that tries to work with just 1GB of RAM) > > It does not download all packages, but just the headers. For packages > > stored in a local mirror, the speed isn't too bad. It ran approx. 11 minutes > > with remote Rawhide, though, on an average dual core machine. > > > > Will Woods/autoqa features a conflicts checker, too, > > https://fedorahosted.org/pipermail/autoqa-results/2010-March/date.html > > which is why I haven't continued with filing further tickets or with > > enhancing my script. > > > hi, > > Is there a wiki page with more info on this script please? How it's to > be used etc.? My one reads the system's Yum repo configuration by default (and it only has a few options explained by --help, such as restricting the check to packages matching a regexp - and a multilib option could be added but it's not really tested with x86_64 and multiarch repos). Probably the first thing I'd change if I continued to work on it is to merge the file mode conflicts with the file checksum conflicts for better readability. As an example, with Fedora 12 i686 you currently would get: $ ./confcheck-remote-split2.py Target distribution: fedora rpmfusion-free rpmfusion-free-updates rpmfusion-free-updates-testing updates updates-testing Reading repository metadata... Pass 1: Potential duplicate files in metadata... Sorting... Pruning... Pass 2: Examining duplicates closer... WARNING: file mode conflict => /usr/share/java/maven2/poms => dumbster-1.6-9.fc12.noarch maven2-2.0.8-3.fc12.noarch WARNING: file mode conflict => /usr/share/java/maven2/poms => maven2-2.0.8-3.fc12.noarch dumbster-1.6-9.fc12.noarch WARNING: file mode conflict => /usr/lib/libpfm.so.3 => libpfm-3.5-4.fc12.i686 papi-4.0.0-2.fc12.i686 WARNING: file mode conflict => /usr/lib/libpfm.so.3 => papi-4.0.0-2.fc12.i686 libpfm-3.5-4.fc12.i686 WARNING: file mode conflict => /etc/redhat-release => fedora-release-12-2.noarch ovirt-node-1.9.0-0.fc12.i686 WARNING: file mode conflict => /etc/system-release => fedora-release-12-2.noarch ovirt-node-1.9.0-0.fc12.i686 WARNING: file mode conflict => /etc/redhat-release => generic-release-12-1.noarch ovirt-node-1.9.0-0.fc12.i686 WARNING: file mode conflict => /etc/system-release => generic-release-12-1.noarch ovirt-node-1.9.0-0.fc12.i686 WARNING: file mode conflict => /etc/redhat-release => ovirt-node-1.9.0-0.fc12.i686 fedora-release-12-2.noarch WARNING: file mode conflict => /etc/redhat-release => ovirt-node-1.9.0-0.fc12.i686 generic-release-12-1.noarch WARNING: file mode conflict => /etc/system-release => ovirt-node-1.9.0-0.fc12.i686 fedora-release-12-2.noarch WARNING: file mode conflict => /etc/system-release => ovirt-node-1.9.0-0.fc12.i686 generic-release-12-1.noarch => plt-scheme-4.1.2-3.fc12.src.rpm => 1:plt-scheme-4.1.2-3.fc12.i686 in fedora File conflict with: batik-slideshow-1.7-6.fc12.noarch /usr/bin/slideshow => EMBOSS-6.1.0-6.fc12.src.rpm => EMBOSS-6.1.0-6.fc12.i686 in updates File conflict with: pscan-1.3-4.fc12.i686 /usr/bin/pscan File conflict with: wcstools-3.8.1-1.fc12.i686 /usr/bin/remap => amule-2.2.6-1.fc12.src.rpm => amule-2.2.6-1.fc12.i686 in rpmfusion-free File conflict with: cas-0.15-1.fc12.1.noarch /usr/bin/cas /usr/share/man/man1/cas.1.gz => anaconda-12.46-2.fc12.src.rpm => anaconda-12.46-2.fc12.i686 in fedora File conflict with: ovirt-node-1.9.0-0.fc12.i686 /usr/sbin/gptsync /usr/sbin/showpart => asterisk-1.6.1.17-1.fc12.src.rpm => asterisk-1.6.1.17-1.fc12.i686 in updates-testing File conflict with: callweaver-1.2.1-2.fc12.i686 /usr/sbin/smsq /usr/sbin/streamplayer => batik-1.7-6.fc12.src.rpm => batik-slideshow-1.7-6.fc12.noarch in fedora File conflict with: 1:plt-scheme-4.1.2-3.fc12.i686 /usr/bin/slideshow => callweaver-1.2.1-2.fc12.src.rpm => callweaver-1.2.1-2.fc12.i686 in fedora File conflict with: asterisk-1.6.1.17-1.fc12.i686 /usr/sbin/smsq /usr/sbin/streamplayer => cas-0.15-1.fc12.1.src.rpm => cas-0.15-1.fc12.1.noarch in updates File conflict with: amule-2.2.6-1.fc12.i686 /usr/bin/cas /usr/share/man/man1/cas.1.gz => dcbd-0.9.15-7.fc12.src.rpm
Re: Problems in packaging kicad
On 03/16/2010 08:19 PM, Tom "spot" Callaway wrote: > On 03/16/2010 08:27 AM, Alain Portal wrote: >> Hi, >> >> I get some problem in packaging kicad. >> Linking fails, and I don't know how to solve. >> There is no problem if I compile without packaging. > > Well, I doubt that seriously. This code is a bit of a mess (but still > not as painful as chromium). > > Attached is a new spec file, and two patches that fix the problems which > were preventing it from building. > > ~spot, who feels dirty after spending so much time hacking around cmake > Another little change that is needed is that the package source file "kicad-ld.conf" has the contents "/usr/lib64/kicad". It should be "/usr/lib/kicad", otherwise it does not work correctly on 32bit i686 platforms. The kicad.spec file edits this to "/usr/lib64/kicad" if for an x86_64 platform. Terry -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning DR17 and EFL
On Wed, Mar 17, 2010 at 2:02 AM, Christoph Wickert wrote: > Am Dienstag, den 16.03.2010, 22:11 +0100 schrieb Thomas Janssen: > >> The real reason to get the packages orphaned is the continued >> annoyance of cwickert on IRC (#fedora-de), trying to force me into the >> role of the bad guy there, since he did not understand the problem, >> even not in the FESCo Meeting from today. See the FESCo ticket to get >> a hint of what was going on in #fedora-de. >> https://fedorahosted.org/fesco/ticket/355 >> Trying to force anybody into pushing an untested release into F-13. >> You can see that even in the Meeting log. Instead of let me do my job >> as package maintainer. So i'm really sick and tired and give it away. >> >> Coming back to that social problem mentioned. The rel-eng ticket was >> clearly mentioned in #fedora-de and even to cassmodiah (if i have to >> upload backlogs, cassmodiah == boelkmoeller3), not just by me, but as >> well by cwickert. Everything was talked about, as well what i want to >> do. >> The only social problem here was an arrogant and stubborn cwickert. >> Sorry, but i can't stand a liar. > > Please don't call me a liar if you are not even telling half the truth: > * Several people - me included - repeatedly offered to their help > to fix the breakage that your co-maintainer caused. In order to > help you, they need details like build logs etc, but you even > refused to tell which packages are causing problems. We asked > you several times, but got no reply. Did i ask for help? No. I asked upstream, that might be something new to you that one can ask upstream as well. And i give a lot more of what they tell me than what *you* tell me. And there's a reason for it. > * You claim that two packages are broken, but according to Rudolf > everything does build fine and it's just a "trivial update". I dunno how often i have to write it until you understand it. Seems to me you're not reading at all. > * You claimed that you wanted to brief your co-maintainer and > explain him everything in detail. This never happened. The mail > you sent him is full of accusations, but no technical details. Everything was explained in IRC, the same channel he's in, #fedora-de. Please.. Though i wrote him the email and told him again what i wanted to do. I hope you recall that i sent the mail and i still have it around. Liar. > * You claimed that in order to update you needed new packages that > will not be ready in time for F13, while others confirmed the > stack does build with the packages that are currently in Fedora. You want to read, what you quoted out, again. Since that is what i claimed all day long. > * You had several weeks for testing, updates or submitting > reviews. None of this happened. As i said. I was the packager. *You* don't have to tell me what to do. And you never understood what i told you. > * In the trac ticket you claim that the update path was broken > through the embryo update. This is not true. There have been > broken deps for weeks, but not a broken upgrade path. ... > * Several neutral observers of the conversation in fedora-de# > today said you were argued illogical, e.g. > * You said you needed testers, but you refused to build the > packages at least in rawhide. Without packages there will be no > testers, simple as that. No. I never said i need testers. I said *I* want to test it before i offer it. Kinda different isn't it. If you dont like how i handle my packages, that i first test stuff built locally and then push it to repos, feel free to try to remove my packager status. > * You repeatedly insulted people (not only me) on IRC. I insulted only *you*. Yes, yesterday i was giving you everything back from the last weeks. I had to join #fedora-de again for it, but it was worth it. Especially after this last post in the FESCo ticket and the again started accusation in #fedora-de. > If you refuse to answer a simple yes/no question and wont let people > help you, then I really think there is a social problem. Answer *you* a question i answered already about 10 times. But you haven't understand yet, why would you in the future. So i refused to answer the question again *but* pointed you to your backlogs where the answer is multiple times. Oh, i forgot, you wanted already an answer (especially yesterday in #fedora-de for the rhetoric question if i sent a srpm and a buildlog to che. I never asked him for help, i never needed the help from him or you there, so why would i do that? Because you wanted so, because you think you're the big boss there. Not for me :) I'm sorry. but you *are* a liar. You proved it again that you don't understand it like several times before. I really wonder how someone like you made it into FESCo. I already left #fedora-de because i can't stand your continued annoyance started with the updat
libssh2 F11 update breaks Fedora 12 DVD update
On the F12 install DVD we have libssh2-1.2-2.fc12. A fully updated F11 will have libssh2 with a higher version. Apparently anaconda force updates some packages, if you update with the F12 DVD, but not the libssh2 package, which will lead to a broken yum, because python-curl needs libcurl, which needs libssh2. But the libssh2 from F11 needs libssl.so.8 which is not available anymore on the system (anaconda force update of openssl??). So yum does not run anymore. The non-technical user ends up with a broken system. Solution? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
