From michael at knox.net.nz Tue Aug 1 02:51:55 2006 From: michael at knox.net.nz (Michael J. Knox) Date: Tue, 01 Aug 2006 14:51:55 +1200 Subject: On leave. Message-ID: <44CEC1CB.5020708@knox.net.nz> Just a heads up. I will be relocating to Auckland this coming weekend. So as of AUgust the 4th, I will be offically on leave/holiday/whatever you want to call it. I hope not to be with out a DSL connection for too long, but at this stage about 10 - 14 days is to be expected. Thanks! Michael From cweyl at alumni.drew.edu Tue Aug 1 04:24:58 2006 From: cweyl at alumni.drew.edu (Chris Weyl) Date: Mon, 31 Jul 2006 21:24:58 -0700 Subject: Stalled review policy proposal In-Reply-To: References: Message-ID: <7dd7ab490607312124s459a8dc2t8d12ada2020cccb5@mail.gmail.com> On 7/29/06, Jason L Tibbitts III wrote: > As discussed at the recent FESCo meeting, I've drawn up a quick policy > for dealing with stalled reviews. It's not intended to be > comprehensive; the idea is to address two main issues that have been > causing problems in the review process: unresponsive reviewers and > unresponsive package submitters. I like. +1 > The intent is to close the bug so that it can be submitted by someone > else in a separate bug. If the bug is resubmitted by someone else, it > is also reasonable to change the resolution on the closed bug to > DUPLICATE and mark it as a duplicate of the new bug so that reviewers > of the new ticket can easily find the work that was done on the old > one. Would it be possible to, say, close it with a keyword, or have it blocking something like "FE-DEADREVIEW"? That way it'd be much easier to find if someone wants to give the package another shot. (Or if people want to generate statistics, etc, etc...) -Chris -- Chris Weyl Ex astris, scientia From dennis at ausil.us Tue Aug 1 05:38:02 2006 From: dennis at ausil.us (Dennis Gilmore) Date: Tue, 1 Aug 2006 00:38:02 -0500 Subject: Extras Buildsys Update Message-ID: <200608010038.03674.dennis@ausil.us> Hey Guys, all of the builders are now updated. They all now implement the minimal buildroot as approved by FESCO. So for those maintainers out there that have done nothing about the broken builds by Matt Domsch. You need to fix your packages before we ask everyone to rebuild for FC6 very soon now. -- Dennis Gilmore, RHCE Proud Australian From j.w.r.degoede at hhs.nl Tue Aug 1 04:07:00 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Tue, 01 Aug 2006 06:07:00 +0200 Subject: Stalled review policy proposal In-Reply-To: References: Message-ID: <44CED364.9000305@hhs.nl> Jason L Tibbitts III wrote: > As discussed at the recent FESCo meeting, I've drawn up a quick policy > for dealing with stalled reviews. It's not intended to be > comprehensive; the idea is to address two main issues that have been > causing problems in the review process: unresponsive reviewers and > unresponsive package submitters. > > The draft is at > http://fedoraproject.org/wiki/JasonTibbitts/StalledReviewPolicy; I > will include a copy below and keep the draft updated with comments I > receive. > I finally got around to reading this. Looks good. The terms look good too. I also agree with the other poster that a tracker bug for reviews which have been closed as not a bug because of lack of submitter response would be a good idea. Regards, Hans From thias at spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net Tue Aug 1 09:13:38 2006 From: thias at spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net (Matthias Saou) Date: Tue, 1 Aug 2006 11:13:38 +0200 Subject: When should the mass FE6 rebuild begin? Message-ID: <20060801111338.08c68175@python2> Hi, When should the mass FE6 rebuild begin? I'm asking, because I'll be leaving on holidays for a couple of weeks at the end of this week... so if it's this Friday at the latest, that's fine, but if it's later, I'll have to find someone to deal with the packages I maintain. Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Fedora Core release 5.91 (FC6 Test2) - Linux kernel 2.6.17-1.2462.fc6 Load : 0.36 0.42 0.42 From bugs.michael at gmx.net Tue Aug 1 09:23:12 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Tue, 1 Aug 2006 11:23:12 +0200 Subject: Update of the fish package In-Reply-To: <7dad0d770607311659m5c1e5100o3bb06927535f53d1@mail.gmail.com> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <44CE2B5F.6010405@city-fan.org> <20060731184123.21c5a5d3.bugs.michael@gmx.net> <7dad0d770607311243n7f0b6cedr54febe4c6af3f28e@mail.gmail.com> <20060801002819.2e53a49d.bugs.michael@gmx.net> <7dad0d770607311659m5c1e5100o3bb06927535f53d1@mail.gmail.com> Message-ID: <20060801112312.a08a5541.bugs.michael@gmx.net> On Tue, 1 Aug 2006 01:59:04 +0200, Axel Liljencrantz wrote: > Thank you. So the following > > %{!?fedora: %define fedora 6} > %if "%fedora" >= "5" > BuildRequires: xorg-x11-proto-devel libX11-devel libXt-devel > %else > BuildRequires: xorg-x11-devel > %endif > > would be considered nicer than the original spec? I guess I'd agree. > The main downside is that it will not work on non-fedora systems which > do not use the same package names as fedora 5, which should be all pre > X.org-7.0 systems. Well, you could craft proper if-conditions for all supported releases of %fedora and cover old systems via %else. Alternatively, you can leave %fedora undefined whenever it is and in that case check whether it's undefined: %if 0%{?fedora} # a non-Fedora system %endif Here, %{?fedora} only expands to something if defined, and because of the prefix 0 the value becomes 0 (=false) if %fedora is undefined. From bugzilla at redhat.com Tue Aug 1 10:50:40 2006 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 1 Aug 2006 06:50:40 -0400 Subject: [Bug 179852] FC4 buildsys fails - FC4 mock succeeds - wine-docs package In-Reply-To: Message-ID: <200608011050.k71AoesT007413@bugzilla.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: FC4 buildsys fails - FC4 mock succeeds - wine-docs package https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179852 ------- Additional Comments From bugs.michael at gmx.net 2006-08-01 06:41 EST ------- Still happens on the upgraded builders: http://buildsys.fedoraproject.org/build-status/job.psp?uid=13494 -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. From kyrian at ore.org Tue Aug 1 10:50:49 2006 From: kyrian at ore.org (Kyrian) Date: Tue, 01 Aug 2006 11:50:49 +0100 Subject: FC5 tripwire RPM & possible maintainer available. In-Reply-To: <20060731212945.83AC273298@hormel.redhat.com> References: <20060731212945.83AC273298@hormel.redhat.com> Message-ID: <44CF3209.8060303@ore.org> Hi Folks, The FC5 tripwire RPM seems to be in an 'orphaned' or unknown state at the moment, as I'm sure you're all aware. Anyways, I've built an FC5 tripwire RPM, although at this stage only using the backward-compatible gcc 3.2.x RPMS supplied with FC5 to build it, and requiring the backward compatible accompanying libraries, which I can contribute back somehow to FC5 extras or whatever if anyone wants. I'm aware that in the longer term it needs some GCC4 patches applying to the source tree to make it compile and run under native GCC4, which I can probably do (never done exactly that before though), and probably needs a version update too if "Tripwire Software" have provided one under the GPL or other appropriate license. I use tripwire among other stuff regularly on a number of servers, so it's in my best interests that it remains maintained, and since I already do a fair bit of opensource stuff variously detailed here: http://www.orenet.co.uk/opensource/ I guess i'm fairly well placed to become its maintainer, if there's a vacancy, etc. Yours, Kev, oRe Net. From liljencrantz at gmail.com Tue Aug 1 11:07:10 2006 From: liljencrantz at gmail.com (Axel Liljencrantz) Date: Tue, 1 Aug 2006 13:07:10 +0200 Subject: Update of the fish package In-Reply-To: <20060801112312.a08a5541.bugs.michael@gmx.net> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <44CE2B5F.6010405@city-fan.org> <20060731184123.21c5a5d3.bugs.michael@gmx.net> <7dad0d770607311243n7f0b6cedr54febe4c6af3f28e@mail.gmail.com> <20060801002819.2e53a49d.bugs.michael@gmx.net> <7dad0d770607311659m5c1e5100o3bb06927535f53d1@mail.gmail.com> <20060801112312.a08a5541.bugs.michael@gmx.net> Message-ID: <7dad0d770608010407u395feb8cw54346141788fd6d2@mail.gmail.com> Thank you for sponsoring me. I am testing the fedora development tools and reading the development wiki, and hope to upload a new package in a day or two. There seems to be a lot to learn. On 8/1/06, Michael Schwendt wrote: > On Tue, 1 Aug 2006 01:59:04 +0200, Axel Liljencrantz wrote: > > > Thank you. So the following > > > > %{!?fedora: %define fedora 6} > > %if "%fedora" >= "5" > > BuildRequires: xorg-x11-proto-devel libX11-devel libXt-devel > > %else > > BuildRequires: xorg-x11-devel > > %endif > > > > would be considered nicer than the original spec? I guess I'd agree. > > The main downside is that it will not work on non-fedora systems which > > do not use the same package names as fedora 5, which should be all pre > > X.org-7.0 systems. > > Well, you could craft proper if-conditions for all supported releases of > %fedora and cover old systems via %else. > > Alternatively, you can leave %fedora undefined whenever it is and > in that case check whether it's undefined: > > %if 0%{?fedora} > # a non-Fedora system > %endif > > Here, %{?fedora} only expands to something if defined, and because of the > prefix 0 the value becomes 0 (=false) if %fedora is undefined. Thanks for the tip, that makes a lot of sense. I provide you with a revised, unified monster. It is hardcoded to handle all known fedora versions correctly, and in case of a non-fedora system, it falls back to checking the layout of the filesystem and performing an educated guess as to the correct dependencies. I indented it using a single tab per block level, since it was unreadable without indentation and the packaging guidelines do not mention any indentation style recomendation. If there is an informal common indentation style, please let me know. # Locate correct build-dependencies for providing X headers %if "%fedora" >= "5" #Modern Fedora version, has modular X.org BuildRequires: xorg-x11-proto-devel libX11-devel libXt-devel %else %if "%fedora" >= "3" #Semi-old Fedora version, has non-modular X.org BuildRequires: xorg-x11-devel %else %if 0%{?fedora} #This is not a Fedora system, try guessing BuildRequires by looking at the directory structure %define xinclude %( if test -d /usr/X11R6/include; then echo /usr/X11R6/include; else echo /usr/include; fi ) BuildRequires: %{xinclude}/X11/StringDefs.h, %{xinclude}/X11/Xlib.h BuildRequires: %{xinclude}/X11/Intrinsic.h, %{xinclude}/X11/Xatom.h %else #Ancient Fedora version, has XFree86 BuildRequires: XFree86-devel %endif %endif %endif Does this look ok? -- Axel From jonathan.underwood at gmail.com Tue Aug 1 11:29:09 2006 From: jonathan.underwood at gmail.com (Jonathan Underwood) Date: Tue, 1 Aug 2006 12:29:09 +0100 Subject: Update of the fish package In-Reply-To: <7dad0d770608010407u395feb8cw54346141788fd6d2@mail.gmail.com> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <44CE2B5F.6010405@city-fan.org> <20060731184123.21c5a5d3.bugs.michael@gmx.net> <7dad0d770607311243n7f0b6cedr54febe4c6af3f28e@mail.gmail.com> <20060801002819.2e53a49d.bugs.michael@gmx.net> <7dad0d770607311659m5c1e5100o3bb06927535f53d1@mail.gmail.com> <20060801112312.a08a5541.bugs.michael@gmx.net> <7dad0d770608010407u395feb8cw54346141788fd6d2@mail.gmail.com> Message-ID: <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> On 01/08/06, Axel Liljencrantz wrote: > Thanks for the tip, that makes a lot of sense. I provide you with a > revised, unified monster. It is hardcoded to handle all known fedora > versions correctly, and in case of a non-fedora system, it falls back > to checking the layout of the filesystem and performing an educated > guess as to the correct dependencies. > It is my understanding that including cruft in the spec file to allow it to build on non fedora distributions is strongly discouraged in extras - the spec files in fedora extras are for fedora. So I would suggest removing the %if 0%{?fedora} parts. That said, I don't see any directives in the packaging guidelines about this - perhaps we need clarification on this matter. Jonathan From liljencrantz at gmail.com Tue Aug 1 11:37:27 2006 From: liljencrantz at gmail.com (Axel Liljencrantz) Date: Tue, 1 Aug 2006 13:37:27 +0200 Subject: Update of the fish package In-Reply-To: <7dad0d770608010407u395feb8cw54346141788fd6d2@mail.gmail.com> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <44CE2B5F.6010405@city-fan.org> <20060731184123.21c5a5d3.bugs.michael@gmx.net> <7dad0d770607311243n7f0b6cedr54febe4c6af3f28e@mail.gmail.com> <20060801002819.2e53a49d.bugs.michael@gmx.net> <7dad0d770607311659m5c1e5100o3bb06927535f53d1@mail.gmail.com> <20060801112312.a08a5541.bugs.michael@gmx.net> <7dad0d770608010407u395feb8cw54346141788fd6d2@mail.gmail.com> Message-ID: <7dad0d770608010437taa0e181o6957d556557727f9@mail.gmail.com> On 8/1/06, Axel Liljencrantz wrote: > I indented it using a single tab per block level, since it was > unreadable without indentation and the packaging guidelines do not > mention any indentation style recomendation. If there is an informal > common indentation style, please let me know. Oops, just noticed that rpm silently ignores %if et. al. if they are indented. So I had to drop the indentation. Too bad. -- Axel From liljencrantz at gmail.com Tue Aug 1 11:42:15 2006 From: liljencrantz at gmail.com (Axel Liljencrantz) Date: Tue, 1 Aug 2006 13:42:15 +0200 Subject: Update of the fish package In-Reply-To: <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <44CE2B5F.6010405@city-fan.org> <20060731184123.21c5a5d3.bugs.michael@gmx.net> <7dad0d770607311243n7f0b6cedr54febe4c6af3f28e@mail.gmail.com> <20060801002819.2e53a49d.bugs.michael@gmx.net> <7dad0d770607311659m5c1e5100o3bb06927535f53d1@mail.gmail.com> <20060801112312.a08a5541.bugs.michael@gmx.net> <7dad0d770608010407u395feb8cw54346141788fd6d2@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> Message-ID: <7dad0d770608010442l298eb186la2e3d3922eff6764@mail.gmail.com> On 8/1/06, Jonathan Underwood wrote: > On 01/08/06, Axel Liljencrantz wrote: > > Thanks for the tip, that makes a lot of sense. I provide you with a > > revised, unified monster. It is hardcoded to handle all known fedora > > versions correctly, and in case of a non-fedora system, it falls back > > to checking the layout of the filesystem and performing an educated > > guess as to the correct dependencies. > > > > It is my understanding that including cruft in the spec file to allow > it to build on non fedora distributions is strongly discouraged in > extras - the spec files in fedora extras are for fedora. So I would > suggest removing the %if 0%{?fedora} parts. > > That said, I don't see any directives in the packaging guidelines > about this - perhaps we need clarification on this matter. As I said in one of my earlier mails, for me there is a benefit in maintaining only one spec file instead of many. I will of course respect fedora guidelines, but if it would be acceptable to have this rather small amount of non-fedora cruft in the spec it would make life a bit easier for me. There is also a small potential for confusion if the spec file that ships in the fish tarball is different from the one Fedora uses, not a big deal, but a small source of possible bugs and confusion. > Jonathan -- Axel From laurent.rineau__fedora_extras at normalesup.org Tue Aug 1 11:43:38 2006 From: laurent.rineau__fedora_extras at normalesup.org (Laurent Rineau) Date: Tue, 1 Aug 2006 13:43:38 +0200 Subject: Update of the fish package In-Reply-To: <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <7dad0d770608010407u395feb8cw54346141788fd6d2@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> Message-ID: <200608011343.39141@rineau.schtroumpfette> On Tuesday 01 August 2006 13:29, Jonathan Underwood wrote: > On 01/08/06, Axel Liljencrantz wrote: > > Thanks for the tip, that makes a lot of sense. I provide you with a > > revised, unified monster. It is hardcoded to handle all known fedora > > versions correctly, and in case of a non-fedora system, it falls back > > to checking the layout of the filesystem and performing an educated > > guess as to the correct dependencies. > > It is my understanding that including cruft in the spec file to allow > it to build on non fedora distributions is strongly discouraged in > extras - the spec files in fedora extras are for fedora. So I would > suggest removing the %if 0%{?fedora} parts. I don't understand the point. As an upstream developper of CGAL?, for example, I would prefere that the spec file for Fedora is the same as the one we use internally to generate development snapshots. Yes the resulting spec file is quite an advanced one, because of that. But if I can prove that I have written it, and can maintain it, what is the problem, from the FE point of view? The resulting RPMs are not bloated because of the complexity of the src.rpm file. ?)?https://bugzilla.redhat.com/199168 From jonathan.underwood at gmail.com Tue Aug 1 11:54:39 2006 From: jonathan.underwood at gmail.com (Jonathan Underwood) Date: Tue, 1 Aug 2006 12:54:39 +0100 Subject: Update of the fish package In-Reply-To: <200608011343.39141@rineau.schtroumpfette> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <7dad0d770608010407u395feb8cw54346141788fd6d2@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> Message-ID: <645d17210608010454k19f16a37p998a04f3e97274a1@mail.gmail.com> On 01/08/06, Laurent Rineau wrote: > > It is my understanding that including cruft in the spec file to allow > > it to build on non fedora distributions is strongly discouraged in > > extras - the spec files in fedora extras are for fedora. So I would > > suggest removing the %if 0%{?fedora} parts. > > I don't understand the point. As an upstream developper of CGAL?, for example, > I would prefere that the spec file for Fedora is the same as the one we use > internally to generate development snapshots. Yes the resulting spec file is > quite an advanced one, because of that. But if I can prove that I have > written it, and can maintain it, what is the problem, from the FE point of > view? The resulting RPMs are not bloated because of the complexity of the > src.rpm file. Well, as I said - it's my understanding, and my understanding is often a misunderstanding :). Anyway - it was really based on a recollection of the courier-mta packaging thread, see eg. http://www.redhat.com/archives/fedora-extras-list/2006-June/msg00415.html I guess we need some clarification here - is other distro stuff in the spec file OK or not from a FE packaging perspective? FESCO? Jonathan. From Axel.Thimm at ATrpms.net Tue Aug 1 12:15:53 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Tue, 1 Aug 2006 14:15:53 +0200 Subject: FC5 tripwire RPM & possible maintainer available. In-Reply-To: <44CF3209.8060303@ore.org> References: <20060731212945.83AC273298@hormel.redhat.com> <44CF3209.8060303@ore.org> Message-ID: <20060801121553.GC6313@neu.nirvana> On Tue, Aug 01, 2006 at 11:50:49AM +0100, Kyrian wrote: > I guess i'm fairly well placed to become its maintainer, if there's a > vacancy, etc. There is a vacancy, you can see that when checking who is owning the package in the owners.list in CVS. Currently it says extras-orphan at fedoraproject.org, which means it's free to grab. But I'm not sure how it works if you are no contributor yet and need to work on an existing package. Theoretically you need to submit a new package first, but these guidelines are being reworked. So perhaps ask on fesco irc meetings on Thursdays or maybe someone will already answer on list. (Check the wiki on details of irc meeting, orphan package management, sponsoring of new contributors, cvs etc). -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From andreas.bierfert at lowlatency.de Tue Aug 1 12:35:31 2006 From: andreas.bierfert at lowlatency.de (Andreas Bierfert) Date: Tue, 1 Aug 2006 14:35:31 +0200 Subject: Extras Buildsys Update In-Reply-To: <200608010038.03674.dennis@ausil.us> References: <200608010038.03674.dennis@ausil.us> Message-ID: <20060801143531.7e086331@alkaid.a.lan> On Tue, 1 Aug 2006 00:38:02 -0500 Dennis Gilmore wrote: > Hey Guys, > > all of the builders are now updated. They all now implement the minimal > buildroot as approved by FESCO. So for those maintainers out there that > have done nothing about the broken builds by Matt Domsch. You need to fix > your packages before we ask everyone to rebuild for FC6 very soon now. > Is it possible that there still is something borked about the builders. I get failed builds on FC5 with core repo missing like 13442. - Andreas -- Andreas Bierfert | http://awbsworld.de | GPG: C58CF1CB andreas.bierfert at lowlatency.de | http://lowlatency.de | signed/encrypted phone: +49 2402 102373 | cell: +49 173 5803043 | mail preferred -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From j.w.r.degoede at hhs.nl Tue Aug 1 12:52:46 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Tue, 01 Aug 2006 14:52:46 +0200 Subject: New ogre version (soname change) heads-up Message-ID: <44CF4E9E.6030901@hhs.nl> Hi all, I've just commited a new version of ogre to CVS and its building as I type this. Unfortunatly even though this is a bugfix release this release is not ABI compatible with the previous release, and upstream "forgot" to change the soname version. I've discussed this with upstream and they basicly give no ABI guarantees not even between bugfix releases. They do try to bump the soname, but forget that sometimes. So I've removed the -version-info argument to libtool when linking and added -release @PACKAGE_VERSION@ causing %{version} to be embedded into the soname. This will break the rpm deps of current ogre users (soname change), but that is way better then the silent ABI breakage which we would have had without this change. Thus I'm only making this change for devel and any ogre using packages must be recompiled. The new release is supposed to be 100% API compatible, so rebuilding should not be a problem. Regards, Hans From dennis at ausil.us Tue Aug 1 13:02:12 2006 From: dennis at ausil.us (Dennis Gilmore) Date: Tue, 1 Aug 2006 08:02:12 -0500 Subject: Extras Buildsys Update In-Reply-To: <20060801143531.7e086331@alkaid.a.lan> References: <200608010038.03674.dennis@ausil.us> <20060801143531.7e086331@alkaid.a.lan> Message-ID: <200608010802.12716.dennis@ausil.us> On Tuesday 01 August 2006 07:35, Andreas Bierfert wrote: > On Tue, 1 Aug 2006 00:38:02 -0500 > > Dennis Gilmore wrote: > > Hey Guys, > > > > all of the builders are now updated. They all now implement the minimal > > buildroot as approved by FESCO. So for those maintainers out there > > that have done nothing about the broken builds by Matt Domsch. You need > > to fix your packages before we ask everyone to rebuild for FC6 very > > soon now. > > Is it possible that there still is something borked about the builders. I > get failed builds on FC5 with core repo missing like 13442. > > - Andreas Requeue your job it should eb ok now. the nfs share wasnt mounted :( Dennis From bugs.michael at gmx.net Tue Aug 1 13:50:45 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Tue, 1 Aug 2006 15:50:45 +0200 Subject: Update of the fish package In-Reply-To: <645d17210608010454k19f16a37p998a04f3e97274a1@mail.gmail.com> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <7dad0d770608010407u395feb8cw54346141788fd6d2@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> <645d17210608010454k19f16a37p998a04f3e97274a1@mail.gmail.com> Message-ID: <20060801155045.4776f7da.bugs.michael@gmx.net> On Tue, 1 Aug 2006 12:54:39 +0100, Jonathan Underwood wrote: > I guess we need some clarification here - is other distro stuff in the > spec file OK or not from a FE packaging perspective? FESCO? It boils down to a matter of perspective. If you confront a reviewer with an overloaded spec file, which fails to build _and_ contains several obvious mistakes, several pitfalls and questionable sections, it becomes obvious that the spec file complexity is the cause of maintenance difficulties and decreased readability. In such a scenario I also strongly encourage the packager to create a clean and easy-to-maintain spec file instead of trying to hit many nails at once with a single hammer. Often, such pseudo distribution-independent spec files become a mess and work for only a few of the target distributions, because some distribution-specific bugs and build problems remain and depend on contributed fixes. In particular, when the packager does not have access to all the supported dists. Spec files for multiple distribution also result in superfluous changes (= the packager trying to sync spec files without reason), which bear the risk of breaking things by accident. The more you think about it and the more you practise it, the more you will like distribution-specific spec files. A single spec file for each distribution. Incremental changes, small changes. And for many version upgrades, you only need to touch Source, %version, %release and nothing else. From andreas.bierfert at lowlatency.de Tue Aug 1 13:51:26 2006 From: andreas.bierfert at lowlatency.de (Andreas Bierfert) Date: Tue, 1 Aug 2006 15:51:26 +0200 Subject: Extras Buildsys Update In-Reply-To: <200608010802.12716.dennis@ausil.us> References: <200608010038.03674.dennis@ausil.us> <20060801143531.7e086331@alkaid.a.lan> <200608010802.12716.dennis@ausil.us> Message-ID: <20060801155126.4dc4fbc2@alkaid.a.lan> On Tue, 1 Aug 2006 08:02:12 -0500 Dennis Gilmore wrote: > Requeue your job it should eb ok now. the nfs share wasnt mounted :( Hm, both my FC6 builds worked but on this FC5 build I get a strange error in root.log... make mockbuild worked fine here: http://buildsys.fedoraproject.org/logs/fedora-5-extras/13442-sylpheed-claws-2.4.0-1.fc5/i386/root.log - Andreas -- Andreas Bierfert | http://awbsworld.de | GPG: C58CF1CB andreas.bierfert at lowlatency.de | http://lowlatency.de | signed/encrypted phone: +49 2402 102373 | cell: +49 173 5803043 | mail preferred -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From andreas.bierfert at lowlatency.de Tue Aug 1 14:14:07 2006 From: andreas.bierfert at lowlatency.de (Andreas Bierfert) Date: Tue, 1 Aug 2006 16:14:07 +0200 Subject: When should the mass FE6 rebuild begin? In-Reply-To: <20060801111338.08c68175@python2> References: <20060801111338.08c68175@python2> Message-ID: <20060801161407.45ccd234@alkaid.a.lan> On Tue, 1 Aug 2006 11:13:38 +0200 Matthias Saou wrote: > Hi, > > When should the mass FE6 rebuild begin? > > I'm asking, because I'll be leaving on holidays for a couple of weeks > at the end of this week... so if it's this Friday at the latest, that's > fine, but if it's later, I'll have to find someone to deal with the > packages I maintain. > > Matthias > Hm, I suppose if the packages are in shape, kicking a build should not be to hard. So if you are gone before the rebuild let me know and I will jump in no problem. - Andreas -- Andreas Bierfert | http://awbsworld.de | GPG: C58CF1CB andreas.bierfert at lowlatency.de | http://lowlatency.de | signed/encrypted phone: +49 2402 102373 | cell: +49 173 5803043 | mail preferred -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From liljencrantz at gmail.com Tue Aug 1 14:14:10 2006 From: liljencrantz at gmail.com (Axel Liljencrantz) Date: Tue, 1 Aug 2006 16:14:10 +0200 Subject: Update of the fish package In-Reply-To: <20060801155045.4776f7da.bugs.michael@gmx.net> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <7dad0d770608010407u395feb8cw54346141788fd6d2@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> <645d17210608010454k19f16a37p998a04f3e97274a1@mail.gmail.com> <20060801155045.4776f7da.bugs.michael@gmx.net> Message-ID: <7dad0d770608010714u643814n6c7be78fcc47d736@mail.gmail.com> On 8/1/06, Michael Schwendt wrote: > On Tue, 1 Aug 2006 12:54:39 +0100, Jonathan Underwood wrote: > > > I guess we need some clarification here - is other distro stuff in the > > spec file OK or not from a FE packaging perspective? FESCO? > > It boils down to a matter of perspective. If you confront a reviewer with > an overloaded spec file, which fails to build _and_ contains several > obvious mistakes, several pitfalls and questionable sections, it becomes > obvious that the spec file complexity is the cause of maintenance > difficulties and decreased readability. In such a scenario I also strongly > encourage the packager to create a clean and easy-to-maintain spec file > instead of trying to hit many nails at once with a single hammer. > > Often, such pseudo distribution-independent spec files become a mess and > work for only a few of the target distributions, because some > distribution-specific bugs and build problems remain and depend on > contributed fixes. In particular, when the packager does not have access > to all the supported dists. > > Spec files for multiple distribution also result in superfluous changes (= > the packager trying to sync spec files without reason), which bear the risk > of breaking things by accident. > > The more you think about it and the more you practise it, the more you > will like distribution-specific spec files. A single spec file for each > distribution. Incremental changes, small changes. And for many version > upgrades, you only need to touch Source, %version, %release and nothing > else. All the things you say are probably true and valid counterpoints to the arguments made by myself and others advocating a single spec-file. But I don't think your points always apply. If you look at e.g. the spec file of fish, it is rather short and simple, even with the recent additions: http://roo.no-ip.org/fish/darcs/fish.spec The only part of the spec that is distribution specific is the BuildRequires to bring in the X headers. I would say that in such simple cases, the advantages of a single spec file are larger than the advantage of a slightly simpler file. But e.g. the spec file for the Courier package discussed in the thread referenced in one of the previous posts is a lot more complicated, and I wouldn't presume to know if writing a fedora-specific spec-file would be better. To me, it seems that advocating always using the same approach to writing spec-files ignores the fact that some packages are a great deal more complicated than others. I would think trusting the common sense of the maintainers to make the right choice in individual cases instead of imposing a one size fits all solution makes the most sense. -- Axel From dennis at ausil.us Tue Aug 1 15:16:06 2006 From: dennis at ausil.us (Dennis Gilmore) Date: Tue, 1 Aug 2006 10:16:06 -0500 Subject: Extras Buildsys Update In-Reply-To: <20060801155126.4dc4fbc2@alkaid.a.lan> References: <200608010038.03674.dennis@ausil.us> <200608010802.12716.dennis@ausil.us> <20060801155126.4dc4fbc2@alkaid.a.lan> Message-ID: <200608011016.07140.dennis@ausil.us> On Tuesday 01 August 2006 08:51, Andreas Bierfert wrote: > On Tue, 1 Aug 2006 08:02:12 -0500 > > Dennis Gilmore wrote: > > Requeue your job it should eb ok now. the nfs share wasnt mounted :( > > Hm, both my FC6 builds worked but on this FC5 build I get a strange error > in root.log... make mockbuild worked fine here: > http://buildsys.fedoraproject.org/logs/fedora-5-extras/13442-sylpheed-claws >-2.4.0-1.fc5/i386/root.log > > - Andreas Can you please try again, I made a change to the mock configs to exclude *.x86_64 it looks like its trying to bring in 64 bit stuff to the i386 build root. the only place it can get 64 bit packages is the repo of not yet pushed packages. Thanks for your patience Dennis From jkeating at redhat.com Tue Aug 1 15:39:52 2006 From: jkeating at redhat.com (Jesse Keating) Date: Tue, 1 Aug 2006 11:39:52 -0400 Subject: Update of the fish package In-Reply-To: <200608011343.39141@rineau.schtroumpfette> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> Message-ID: <200608011139.53076.jkeating@redhat.com> On Tuesday 01 August 2006 07:43, Laurent Rineau wrote: > I don't understand the point. As an upstream developper of CGAL?, for > example, I would prefere that the spec file for Fedora is the same as the > one we use internally to generate development snapshots. Yes the resulting > spec file is quite an advanced one, because of that. But if I can prove > that I have written it, and can maintain it, what is the problem, from the > FE point of view? The resulting RPMs are not bloated because of the > complexity of the src.rpm file. Because when a security flaw comes around and you're not there to fix it, somebody else has to be able to understand your spec and be able to massage a patch into it. Ditto for a forced rebuild, or for any number of things. This is a community project, you have to think in terms of somebody else being able to maintain your spec file, so you'll want to make it as easy as possible for somebody to do this, and that means clean as possible specs and as less complicated as possible. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bugs.michael at gmx.net Tue Aug 1 15:52:49 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Tue, 1 Aug 2006 17:52:49 +0200 Subject: Update of the fish package In-Reply-To: <7dad0d770608010714u643814n6c7be78fcc47d736@mail.gmail.com> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <7dad0d770608010407u395feb8cw54346141788fd6d2@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> <645d17210608010454k19f16a37p998a04f3e97274a1@mail.gmail.com> <20060801155045.4776f7da.bugs.michael@gmx.net> <7dad0d770608010714u643814n6c7be78fcc47d736@mail.gmail.com> Message-ID: <20060801175249.feb0114e.bugs.michael@gmx.net> On Tue, 1 Aug 2006 16:14:10 +0200, Axel Liljencrantz wrote: > To me, it seems that advocating always using the same approach to > writing spec-files ignores the fact that some packages are a great > deal more complicated than others. I would think trusting the common > sense of the maintainers to make the right choice in individual cases > instead of imposing a one size fits all solution makes the most sense. Right. With the exception that packages, which are "more complicated than others" very often become even more complicated when lots of conditional code is added to the spec. Conditional sections introduce multiple paths of execution. Fun starts with lots of %define's, a new conditional code block at every third line, and ends with disabling or overriding global rpm macros, sometimes even in ways that are clearly wrong for Fedora. Further, common sense regularly finds its limits when during the Review Process, the packager meets other packagers and possibly receives the first comments on his package ever. Then, when apparently the packager struggles to make the package build, and when it fails and fails and fails and contains problems at install-time and run-time, and perhaps a reviewer suggests fixes, then it can be a good idea to rethink the packaging techniques and e.g. cut down a spec from 32KiB to less than a quarter of that size (which has happened before). Anyway, let's not generalise. ;) From jonathan.underwood at gmail.com Tue Aug 1 15:48:43 2006 From: jonathan.underwood at gmail.com (Jonathan Underwood) Date: Tue, 1 Aug 2006 16:48:43 +0100 Subject: Update of the fish package In-Reply-To: <200608011139.53076.jkeating@redhat.com> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> <200608011139.53076.jkeating@redhat.com> Message-ID: <645d17210608010848k3d9d1ane9674cc63c5394b4@mail.gmail.com> On 01/08/06, Jesse Keating wrote: > On Tuesday 01 August 2006 07:43, Laurent Rineau wrote: > > I don't understand the point. As an upstream developper of CGAL?, for > > example, I would prefere that the spec file for Fedora is the same as the > > one we use internally to generate development snapshots. Yes the resulting > > spec file is quite an advanced one, because of that. But if I can prove > > that I have written it, and can maintain it, what is the problem, from the > > FE point of view? The resulting RPMs are not bloated because of the > > complexity of the src.rpm file. > > Because when a security flaw comes around and you're not there to fix it, > somebody else has to be able to understand your spec and be able to massage a > patch into it. > > Ditto for a forced rebuild, or for any number of things. This is a community > project, you have to think in terms of somebody else being able to maintain > your spec file, so you'll want to make it as easy as possible for somebody to > do this, and that means clean as possible specs and as less complicated as > possible. This is of course a very strong argument that is hard to disagree with. The fact we're having this discussion though reflects a lack of a firm decision on the matter and a solid packaging guideline reflecting the outcome of that decision. I would take this to the FESCO meeting, but I am never able to have IRC connection during FESCO meeting times (work restrictions). Hopefully someone else will bring it up. Jonathan. From jwboyer at jdub.homelinux.org Tue Aug 1 16:05:34 2006 From: jwboyer at jdub.homelinux.org (Josh Boyer) Date: Tue, 01 Aug 2006 11:05:34 -0500 Subject: Update of the fish package In-Reply-To: <645d17210608010848k3d9d1ane9674cc63c5394b4@mail.gmail.com> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> <200608011139.53076.jkeating@redhat.com> <645d17210608010848k3d9d1ane9674cc63c5394b4@mail.gmail.com> Message-ID: <1154448334.29112.5.camel@weaponx.rchland.ibm.com> On Tue, 2006-08-01 at 16:48 +0100, Jonathan Underwood wrote: > On 01/08/06, Jesse Keating wrote: > > On Tuesday 01 August 2006 07:43, Laurent Rineau wrote: > > > I don't understand the point. As an upstream developper of CGAL?, for > > > example, I would prefere that the spec file for Fedora is the same as the > > > one we use internally to generate development snapshots. Yes the resulting > > > spec file is quite an advanced one, because of that. But if I can prove > > > that I have written it, and can maintain it, what is the problem, from the > > > FE point of view? The resulting RPMs are not bloated because of the > > > complexity of the src.rpm file. > > > > Because when a security flaw comes around and you're not there to fix it, > > somebody else has to be able to understand your spec and be able to massage a > > patch into it. > > > > Ditto for a forced rebuild, or for any number of things. This is a community > > project, you have to think in terms of somebody else being able to maintain > > your spec file, so you'll want to make it as easy as possible for somebody to > > do this, and that means clean as possible specs and as less complicated as > > possible. > > This is of course a very strong argument that is hard to disagree > with. The fact we're having this discussion though reflects a lack of > a firm decision on the matter and a solid packaging guideline > reflecting the outcome of that decision. I would take this to the > FESCO meeting, but I am never able to have IRC connection during FESCO > meeting times (work restrictions). Hopefully someone else will bring > it up. It should be discussed by the packaging committee. They are responsible for the packaging guidelines. FESCO will certainly weigh in as well. josh From rdieter at math.unl.edu Tue Aug 1 16:19:15 2006 From: rdieter at math.unl.edu (Rex Dieter) Date: Tue, 01 Aug 2006 11:19:15 -0500 Subject: interest in qt-4.2.0(tp1)? In-Reply-To: References: Message-ID: <44CF7F03.3060009@math.unl.edu> Rex Dieter wrote on fedora-extras-list: > For Extras/devel, is there any interest in upgrading qt4-4.1 to qt-4.2.0-tp1 > (tech preview 1)? According to > http://www.trolltech.com/company/newsroom/announcements/press.2006-06-26.0683224314/ > (and qt4-4.2.0-tp1's README), > "We plan to enter the beta phase in Q3, 2006 and release the final Qt 4.2 in > early Q4, 2006." > > The final release matches *pretty* close to fc6 final release date of Early > October (according to http://fedoraproject.org/wiki/Core/Schedule ) > > Opinions? > > AFAIC, I'm leaning toward doing it especially since qt4-4.2 includes some > new/nice features including dbus bindings. FYI, the deed is done. qt4-4.2.0-tp1 has been imported into FE/devel. -- Rex From liljencrantz at gmail.com Tue Aug 1 16:19:56 2006 From: liljencrantz at gmail.com (Axel Liljencrantz) Date: Tue, 1 Aug 2006 18:19:56 +0200 Subject: Update of the fish package In-Reply-To: <200608011139.53076.jkeating@redhat.com> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> <200608011139.53076.jkeating@redhat.com> Message-ID: <7dad0d770608010919j4e839126u45cca5d0bb99e5c7@mail.gmail.com> On 8/1/06, Jesse Keating wrote: > On Tuesday 01 August 2006 07:43, Laurent Rineau wrote: > > I don't understand the point. As an upstream developper of CGAL?, for > > example, I would prefere that the spec file for Fedora is the same as the > > one we use internally to generate development snapshots. Yes the resulting > > spec file is quite an advanced one, because of that. But if I can prove > > that I have written it, and can maintain it, what is the problem, from the > > FE point of view? The resulting RPMs are not bloated because of the > > complexity of the src.rpm file. > > Because when a security flaw comes around and you're not there to fix it, > somebody else has to be able to understand your spec and be able to massage a > patch into it. > > Ditto for a forced rebuild, or for any number of things. This is a community > project, you have to think in terms of somebody else being able to maintain > your spec file, so you'll want to make it as easy as possible for somebody to > do this, and that means clean as possible specs and as less complicated as > possible. Look at e.g. http://roo.no-ip.org/fish/darcs/fish.spec can you honestly say that 'nobody could understand the spec'? Also, keep in mind that by using one spec file in stead of many, you only need to fix e.g. a security problem once in stead of once per major version of every supported operating system. My point is that in stead of saying 'never use generic .spec files' or 'never include anything not fedora-related in a .spec file', a more forgiving guideline like 'do not include anything not fedora-related in an already complex .spec file, and whenever possible, keep .spec files simple' is preferable. While the former is much easier to enforce, I feel that using such broad strokes in the guidelines will create a lot of extra work for people with simple packages, e.g. me. > > -- > Jesse Keating > Release Engineer: Fedora -- Axel From j.w.r.degoede at hhs.nl Tue Aug 1 16:56:31 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Tue, 01 Aug 2006 18:56:31 +0200 Subject: Update of the fish package In-Reply-To: <7dad0d770608010919j4e839126u45cca5d0bb99e5c7@mail.gmail.com> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> <200608011139.53076.jkeating@redhat.com> <7dad0d770608010919j4e839126u45cca5d0bb99e5c7@mail.gmail.com> Message-ID: <44CF87BF.5070806@hhs.nl> Axel Liljencrantz wrote: > On 8/1/06, Jesse Keating wrote: >> On Tuesday 01 August 2006 07:43, Laurent Rineau wrote: >> > I don't understand the point. As an upstream developper of CGAL?, for >> > example, I would prefere that the spec file for Fedora is the same >> as the >> > one we use internally to generate development snapshots. Yes the >> resulting >> > spec file is quite an advanced one, because of that. But if I can prove >> > that I have written it, and can maintain it, what is the problem, >> from the >> > FE point of view? The resulting RPMs are not bloated because of the >> > complexity of the src.rpm file. >> >> Because when a security flaw comes around and you're not there to fix it, >> somebody else has to be able to understand your spec and be able to >> massage a >> patch into it. >> >> Ditto for a forced rebuild, or for any number of things. This is a >> community >> project, you have to think in terms of somebody else being able to >> maintain >> your spec file, so you'll want to make it as easy as possible for >> somebody to >> do this, and that means clean as possible specs and as less >> complicated as >> possible. > > Look at e.g. > > http://roo.no-ip.org/fish/darcs/fish.spec > > can you honestly say that 'nobody could understand the spec'? I understand it, but I concider myself not the average packagers and even for me it hurts my eyes. I know the only conditional stuff in there are the X-requires but thats a 3 times nested if. Now as a C-programmer I generally try to avoid nested conditional statements more then 2 levels deep, for a spec file 3 levels of nesting is just wrong. So I think your example actually makes a strong point for those objecting to one spec for all. Regards, Hans From ville.skytta at iki.fi Tue Aug 1 17:07:02 2006 From: ville.skytta at iki.fi (Ville =?ISO-8859-1?Q?Skytt=E4?=) Date: Tue, 01 Aug 2006 20:07:02 +0300 Subject: When should the mass FE6 rebuild begin? In-Reply-To: <20060801111338.08c68175@python2> References: <20060801111338.08c68175@python2> Message-ID: <1154452022.2748.138.camel@localhost.localdomain> On Tue, 2006-08-01 at 11:13 +0200, Matthias Saou wrote: > When should the mass FE6 rebuild begin? The current plan is at FC6 test3 time (Aug 30 according to the preliminary schedule in Wiki). > I'm asking, because I'll be leaving on holidays for a couple of weeks > at the end of this week... so if it's this Friday at the latest, that's > fine, but if it's later, I'll have to find someone to deal with the > packages I maintain. In case you're not available, I'm sure it will be taken care of. Extra points for posting a list of packages you maintain that do *not* need to be rebuilt for some reason (and stating that reason). From seg at haxxed.com Tue Aug 1 17:45:24 2006 From: seg at haxxed.com (Callum Lerwick) Date: Tue, 01 Aug 2006 12:45:24 -0500 Subject: desktop icons In-Reply-To: <44CDA403.8010107@hhs.nl> References: <44CD9FED.1050903@kobold.org> <44CDA403.8010107@hhs.nl> Message-ID: <1154454326.17862.28.camel@localhost> On Mon, 2006-07-31 at 08:32 +0200, Hans de Goede wrote: > According to the freedesktop.org icon standard it is > %{_datadir}/icons/hicolor/, this is where all my packages put them > and I've even blocked reviews on poluting /usr/share/pixmaps with icons > (which will work too to support legacy apps). One thing I don't get is what if the icon is not one of the standard sizes? Like, say, 256x256? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From rdieter at math.unl.edu Tue Aug 1 17:51:38 2006 From: rdieter at math.unl.edu (Rex Dieter) Date: Tue, 01 Aug 2006 12:51:38 -0500 Subject: desktop icons References: <44CD9FED.1050903@kobold.org> <44CDA403.8010107@hhs.nl> <1154454326.17862.28.camel@localhost> Message-ID: Callum Lerwick wrote: > On Mon, 2006-07-31 at 08:32 +0200, Hans de Goede wrote: >> According to the freedesktop.org icon standard it is >> %{_datadir}/icons/hicolor/, this is where all my packages put them >> and I've even blocked reviews on poluting /usr/share/pixmaps with icons >> (which will work too to support legacy apps). > > One thing I don't get is what if the icon is not one of the standard > sizes? Like, say, 256x256? shrink it to fit. (: If it's not in one of the (pre)existing sizes referenced in the icons' index.theme file, it won't be used. -- Rex From liljencrantz at gmail.com Tue Aug 1 17:55:56 2006 From: liljencrantz at gmail.com (Axel Liljencrantz) Date: Tue, 1 Aug 2006 19:55:56 +0200 Subject: Update of the fish package In-Reply-To: <44CF87BF.5070806@hhs.nl> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> <200608011139.53076.jkeating@redhat.com> <7dad0d770608010919j4e839126u45cca5d0bb99e5c7@mail.gmail.com> <44CF87BF.5070806@hhs.nl> Message-ID: <7dad0d770608011055i7ff73454xff495a8a17b0b450@mail.gmail.com> On 8/1/06, Hans de Goede wrote: > > > Axel Liljencrantz wrote: > > On 8/1/06, Jesse Keating wrote: > >> On Tuesday 01 August 2006 07:43, Laurent Rineau wrote: > >> > I don't understand the point. As an upstream developper of CGAL?, for > >> > example, I would prefere that the spec file for Fedora is the same > >> as the > >> > one we use internally to generate development snapshots. Yes the > >> resulting > >> > spec file is quite an advanced one, because of that. But if I can prove > >> > that I have written it, and can maintain it, what is the problem, > >> from the > >> > FE point of view? The resulting RPMs are not bloated because of the > >> > complexity of the src.rpm file. > >> > >> Because when a security flaw comes around and you're not there to fix it, > >> somebody else has to be able to understand your spec and be able to > >> massage a > >> patch into it. > >> > >> Ditto for a forced rebuild, or for any number of things. This is a > >> community > >> project, you have to think in terms of somebody else being able to > >> maintain > >> your spec file, so you'll want to make it as easy as possible for > >> somebody to > >> do this, and that means clean as possible specs and as less > >> complicated as > >> possible. > > > > Look at e.g. > > > > http://roo.no-ip.org/fish/darcs/fish.spec > > > > can you honestly say that 'nobody could understand the spec'? > > I understand it, but I concider myself not the average packagers and > even for me it hurts my eyes. I know the only conditional stuff in there > are the X-requires but thats a 3 times nested if. Now as a C-programmer > I generally try to avoid nested conditional statements more then 2 > levels deep, for a spec file 3 levels of nesting is just wrong. > > So I think your example actually makes a strong point for those > objecting to one spec for all. Then we must simply agree to disagree. Strongly. As a C programmer, I try to avoid tripple-nested if-statements, but duplicating 200 lines of code N times (where N is currently 4, but can potentially be a large number) simply because 1-2 lines differ between versions is an order of magnitude worse. > > Regards, > > Hans -- Axel From buildsys at fedoraproject.org Tue Aug 1 18:32:02 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Tue, 1 Aug 2006 14:32:02 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-01 Message-ID: <20060801183202.E802C152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 24 ClanLib06-0.6.5-6.fc5 abcMIDI-20060730-1.fc5 amavisd-new-2.4.2-1.fc5 clips-6.24-19.fc5 cmake-2.4.2-1.fc5 compface-1.4-7.fc5 ctapi-common-1.0-3.fc5 cvsgraph-1.6.1-2.fc5 glpk-4.11-1.fc5 gtksourceview-sharp-2.0-14.fc5 hercules-3.04.1-3.fc5 jack-audio-connection-kit-0.101.1-12.fc5 kdetoys-3.5.3-3.fc5 makebootfat-1.4-4.fc5 moin-1.5.4-2.fc5 octave-2.9.7-1.fc5 octave-forge-2006.07.09-3.fc5 pam_usb-0.3.3-5.fc5 pdftk-1.12-7.fc5 pdsh-2.11-1.fc5 python-setuptools-0.6c1-2.fc5 rss-glx-0.8.1.p-5.fc5 sturmbahnfahrer-1.2-1.fc5 sysconftool-0.15-2.fc5 Packages built and released for Fedora Extras 4: 14 abcMIDI-20060730-1.fc4 amavisd-new-2.4.2-1.fc4 clips-6.24-16.fc4 cmake-2.4.2-1.fc4 ctapi-common-1.0-3.fc4 cvsgraph-1.5.2-3.fc4 glpk-4.11-1.fc4 jack-audio-connection-kit-0.101.1-12.fc4 kdetoys-3.5.3-3.fc4 makebootfat-1.4-3.fc4 pdsh-2.11-1.fc4 python-setuptools-0.6c1-2.fc4 sylpheed-claws-2.4.0-1.fc4 sysconftool-0.15-2.fc4 Packages built and released for Fedora Extras 3: 2 amavisd-new-2.4.2-1.fc3 makebootfat-1.4-3.fc3 Packages built and released for Fedora Extras development: 36 ClanLib06-0.6.5-6.fc6 abcMIDI-20060730-1.fc6 amavisd-new-2.4.2-1.fc6 auriferous-1.0.1-2.fc6 clips-6.24-19.fc6 cmake-2.4.2-3.fc6 compface-1.4-7.fc6 ctapi-common-1.0-3.fc6 cvsgraph-1.6.1-2.fc6 geomview-1.8.2-0.14.rc7.fc6 gtksourceview-sharp-2.0-14.fc6 hercules-3.04.1-3.fc6 inotify-tools-2.2-3.fc6 jack-audio-connection-kit-0.101.1-12.fc6 javasvn-1.1.0-0.beta4.fc6 kawa-1.8-8.fc6 kdetoys-3.5.4-2.fc6 ksynaptics-0.3.1-2.fc6 libsynaptics-0.14.6b-2.fc6 makebootfat-1.4-4.fc6 moin-1.5.4-2.fc6 ncmpc-0.11.1-6.fc6 ogre-1.2.2-1.p1.fc6 openal-0.0.9-0.6.20060204cvs.fc6 openvpn-2.1-0.11.beta14.fc6 pam_usb-0.3.3-5.fc6 pdftk-1.12-7.fc6 perl-DateTime-0.32-1.fc6 perl-Gtk2-Sexy-0.02-4.fc6 python-setuptools-0.6c1-2.fc6 qstat-2.10-4.fc6 qt4-4.2.0-0.4.tp1.fc6 rss-glx-0.8.1.p-5.fc6 rssowl-1.2.1-3.fc6 sturmbahnfahrer-1.2-1.fc6 sylpheed-claws-2.4.0-1.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From jonathan.underwood at gmail.com Tue Aug 1 18:36:12 2006 From: jonathan.underwood at gmail.com (Jonathan Underwood) Date: Tue, 1 Aug 2006 19:36:12 +0100 Subject: Update of the fish package In-Reply-To: <7dad0d770608011055i7ff73454xff495a8a17b0b450@mail.gmail.com> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> <200608011139.53076.jkeating@redhat.com> <7dad0d770608010919j4e839126u45cca5d0bb99e5c7@mail.gmail.com> <44CF87BF.5070806@hhs.nl> <7dad0d770608011055i7ff73454xff495a8a17b0b450@mail.gmail.com> Message-ID: <645d17210608011136n5501bf84ib50a22d9039b5b55@mail.gmail.com> On 01/08/06, Axel Liljencrantz wrote: > Then we must simply agree to disagree. Strongly. > > As a C programmer, I try to avoid tripple-nested if-statements, but > duplicating 200 lines of code N times (where N is currently 4, but can > potentially be a large number) simply because 1-2 lines differ between > versions is an order of magnitude worse. I think there two issues are getting munged/confused here. One issue is using the same spec file to cover all releases (which I don't personally see as too problematic if it's simple), and the other issue is including cruft for non-fedora distributions. The latter,I personally feel has no place in FE spec files. But that's my opinion, and I think a decision is required by the packaging committee/FESCO. Jonathan. From j.w.r.degoede at hhs.nl Tue Aug 1 19:29:28 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Tue, 01 Aug 2006 21:29:28 +0200 Subject: desktop icons In-Reply-To: <1154454326.17862.28.camel@localhost> References: <44CD9FED.1050903@kobold.org> <44CDA403.8010107@hhs.nl> <1154454326.17862.28.camel@localhost> Message-ID: <44CFAB98.30407@hhs.nl> Callum Lerwick wrote: > On Mon, 2006-07-31 at 08:32 +0200, Hans de Goede wrote: >> According to the freedesktop.org icon standard it is >> %{_datadir}/icons/hicolor/, this is where all my packages put them >> and I've even blocked reviews on poluting /usr/share/pixmaps with icons >> (which will work too to support legacy apps). > > One thing I don't get is what if the icon is not one of the standard > sizes? Like, say, 256x256? > In my experience, just putting it in the closest matching dir does the trick. The whole idea behind having multiple dirs for different sizes is that you can have hand pixilated versions for each common used size (or machine pixilated when the original is vector based), this gives better results then software scaling. However if you only install say a 48x48 icon, it will still show up fine in menus using 20x20 but it will get scaled. So if you drop a 52x50 icon into 48x48 it will get scaled a bit even when used in a menu wanting 48x48 icons. Regards, Hans From pertusus at free.fr Tue Aug 1 19:42:02 2006 From: pertusus at free.fr (Patrice Dumas) Date: Tue, 1 Aug 2006 21:42:02 +0200 Subject: questions about comps files In-Reply-To: <1154355884.20753.5.camel@orodruin.boston.redhat.com> References: <20060729093041.GA2701@free.fr> <1154355884.20753.5.camel@orodruin.boston.redhat.com> Message-ID: <20060801194201.GA2525@free.fr> On Mon, Jul 31, 2006 at 10:24:44AM -0400, Jeremy Katz wrote: > On Sat, 2006-07-29 at 11:41 +0200, Patrice Dumas wrote: > LaTeX things have traditionally been in the Authoring and Publishing > group as well. If there's a desire to get the description changed, > propose something and I'm more than willing to make it more generic :) What about These tools allow you to create documents in authoring formats and convert them to HTML, PDF, Postscript, and text. > > * where should wxWidgets based applications go (I maintain xchm). > > Look more at what the application does as opposed to what widget set it > uses. But there are the gnome-desktop, and kde-desktop... Anyway I guess xchm belongs to office. > The problem with doing so is that it can lead to a confusing UI in some > cases. We've tried (hard) to get to where packages are only listed for > one component. I'd like to try to stay there. Ok. I think this should be said somewhere... > There's the mail-server group :) Why not, but then the description could look like: These packages allow you to configure an IMAP, SMTP mail server or MTA. -- Pat From bugs.michael at gmx.net Tue Aug 1 19:49:23 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Tue, 1 Aug 2006 21:49:23 +0200 Subject: Update of the fish package In-Reply-To: <7dad0d770608011055i7ff73454xff495a8a17b0b450@mail.gmail.com> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> <200608011139.53076.jkeating@redhat.com> <7dad0d770608010919j4e839126u45cca5d0bb99e5c7@mail.gmail.com> <44CF87BF.5070806@hhs.nl> <7dad0d770608011055i7ff73454xff495a8a17b0b450@mail.gmail.com> Message-ID: <20060801214923.e1c28708.bugs.michael@gmx.net> On Tue, 1 Aug 2006 19:55:56 +0200, Axel Liljencrantz wrote: > On 8/1/06, Hans de Goede wrote: > > > > > > > > Look at e.g. > > > > > > http://roo.no-ip.org/fish/darcs/fish.spec > > > > > > can you honestly say that 'nobody could understand the spec'? > > > > I understand it, but I concider myself not the average packagers and > > even for me it hurts my eyes. I know the only conditional stuff in there > > are the X-requires but thats a 3 times nested if. Now as a C-programmer > > I generally try to avoid nested conditional statements more then 2 > > levels deep, for a spec file 3 levels of nesting is just wrong. > > > > So I think your example actually makes a strong point for those > > objecting to one spec for all. > > Then we must simply agree to disagree. Strongly. > > As a C programmer, I try to avoid tripple-nested if-statements, but > duplicating 200 lines of code N times (where N is currently 4, but can > potentially be a large number) simply because 1-2 lines differ between > versions is an order of magnitude worse. Much nicer to the eyes: # Locate correct build time-dependencies for providing X headers %if "%fedora" >= "5" # Modern Fedora version, has modular X.org BuildRequires: xorg-x11-proto-devel libX11-devel libXt-devel %endif %if "%fedora" < "5" %if "%fedora" >= "3" # Semi-old Fedora version, has non-modular X.org BuildRequires: xorg-x11-devel %endif %endif %if "%fedora" < "3" # Ancient Fedora version, has XFree86 BuildRequires: XFree86-devel %endif %if 0%{!?fedora} # This is not a Fedora system, try guessing BuildRequires by # looking at the directory structure %define xinclude /usr%(if [ -d /usr/X11R6/include ]; then echo /X11R6; fi)/inclu de BuildRequires: %{xinclude}/X11/StringDefs.h, %{xinclude}/X11/Xlib.h BuildRequires: %{xinclude}/X11/Intrinsic.h, %{xinclude}/X11/Xatom.h %endif From pertusus at free.fr Tue Aug 1 19:44:35 2006 From: pertusus at free.fr (Patrice Dumas) Date: Tue, 1 Aug 2006 21:44:35 +0200 Subject: questions about comps files In-Reply-To: <20060731142859.GA8610@jadzia.bu.edu> References: <20060729093041.GA2701@free.fr> <1154355884.20753.5.camel@orodruin.boston.redhat.com> <20060731142859.GA8610@jadzia.bu.edu> Message-ID: <20060801194435.GB2525@free.fr> On Mon, Jul 31, 2006 at 10:28:59AM -0400, Matthew Miller wrote: > On Mon, Jul 31, 2006 at 10:24:44AM -0400, Jeremy Katz wrote: > > "Text Processing?" I dunno. 'Authoring and Publishing' seems right to me, I was unhappy with 'These tools allow you to create documentation in the DocBook format and convert them to HTML, PDF, Postscript, and text.' > > > -- > Matthew Miller mattdm at mattdm.org > Boston University Linux ------> > > -- > fedora-extras-list mailing list > fedora-extras-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-extras-list From mattdm at mattdm.org Tue Aug 1 19:50:46 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Tue, 1 Aug 2006 15:50:46 -0400 Subject: questions about comps files In-Reply-To: <20060801194201.GA2525@free.fr> References: <20060729093041.GA2701@free.fr> <1154355884.20753.5.camel@orodruin.boston.redhat.com> <20060801194201.GA2525@free.fr> Message-ID: <20060801195046.GA13181@jadzia.bu.edu> On Tue, Aug 01, 2006 at 09:42:02PM +0200, Patrice Dumas wrote: > > Look more at what the application does as opposed to what widget set it > > uses. > But there are the gnome-desktop, and kde-desktop... Those do what they say -- they give you that desktop environment. There's no such thing as a wxWidgets desktop environment -- well, not yet at least. :) -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From bugs.michael at gmx.net Tue Aug 1 20:14:29 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Tue, 1 Aug 2006 22:14:29 +0200 Subject: Update of the fish package In-Reply-To: <20060801214923.e1c28708.bugs.michael@gmx.net> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> <200608011139.53076.jkeating@redhat.com> <7dad0d770608010919j4e839126u45cca5d0bb99e5c7@mail.gmail.com> <44CF87BF.5070806@hhs.nl> <7dad0d770608011055i7ff73454xff495a8a17b0b450@mail.gmail.com> <20060801214923.e1c28708.bugs.michael@gmx.net> Message-ID: <20060801221429.5e6a7569.bugs.michael@gmx.net> On Tue, 1 Aug 2006 21:49:23 +0200, Michael Schwendt wrote: > %if "%fedora" < "5" > %if "%fedora" >= "3" Too much of it introduces pitfalls, though. Such as: "" is less than "5" "%fedora" expands to "%fedora", if %fedora is undefined using %{?fedora} everywhere would be better :-D From buildsys at fedoraproject.org Tue Aug 1 20:29:15 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Tue, 1 Aug 2006 16:29:15 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-01 Message-ID: <20060801202915.B009F152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 2 cmake-2.4.3-1.fc5 freeciv-2.0.8-4.fc5 Packages built and released for Fedora Extras 4: 2 cmake-2.4.3-1.fc4 freeciv-2.0.8-3.fc4 Packages built and released for Fedora Extras 3: 1 freeciv-2.0.8-2.fc3 Packages built and released for Fedora Extras development: 2 cmake-2.4.3-1.fc6 freeciv-2.0.8-5.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Tue Aug 1 20:29:35 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Tue, 1 Aug 2006 16:29:35 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-01 Message-ID: <20060801202935.7608A152169@buildsys.fedoraproject.org> azureus: green AT redhat.com 5: 0:2.4.0.3-0.20060529cvs_1.fc5 (FE5) 6: 0:2.4.0.3-0.20060328cvs_5.fc6 (FE6) banshee: caillon AT redhat.com 5: 0:0.10.9-1..fc5 (FE5) 6: 0:0.10.8-1 (FE6) camE: matthias AT rpmforge.net 5: 0:1.9-6.fc5 (FE5) 6: 0:1.9-5.fc5 (FE6) camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: oliver AT linux-kernel.at 4: 0:1.14.0-1.fc4 (FE4) 5: 0:1.12.0-1.fc5 (FE5) 6: 0:1.12.0-1.fc5 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gaim-gaym: cweyl AT alumni.drew.edu 5: 0:0.96-3.fc5 (FE5) 6: 0:0.96-2.fc6 (FE6) gauche-gl: gemi AT bluewin.ch 5: 0:0.4.1-5.fc5 (FE5) 6: 0:0.4.1-4.fc6 (FE6) gcdmaster: denis AT poolshark.org 4: 0:1.2.1-5.fc4 (FE4) 5: 0:1.2.1-4.fc5 (FE5) 6: 0:1.2.1-4.fc5 (FE6) gdesklets: luya256 AT yahoo.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) git: chrisw AT redhat.com 3: 0:1.4.1-1.fc3 (FE3) 4: 0:1.4.0-1.fc4 (FE4) 5: 0:1.4.0-1.fc5 (FE5) 6: 0:1.4.1-1.fc6 (FE6) icon-naming-utils: 5: 0:0.7.3-1.fc5 (FC5-updates) 6: 0:0.7.3-1 (FC6) inkscape: denis AT poolshark.org 4: 0:0.44-3.fc4 (FE4) 5: 0:0.44-2.fc5 (FE5) 6: 0:0.44-2.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) libnasl: andreas.bierfert AT lowlatency.de 5: 0:2.2.8-1.fc5 (FE5) 6: 0:2.2.7-1.fc6 (FE6) libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) lvm2: 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-2 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-14.fc6 (FC6) mozilla: 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) nfs-utils: 5: 1:1.0.8-2.fc5 (FC5-updates) 6: 0:1.0.9-2.fc6 (FC6) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) pdsh: woodard AT redhat.com 5: 0:2.11-1.fc5 (FE5) 6: 0:2.10-4.fc6 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-1.FC6.1 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.1-2.fc5 (FE5) 6: 0:1.0.1-1.fc5 (FE6) quagga: 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-anthy: tagoh AT redhat.com 4: 0:1.2.0-1.fc4 (FE4) 5: 0:1.0.0-1.fc5.1 (FC5-updates) 6: 0:1.0.0-4.fc6 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5 (FE5) 6: 0:0.2.0-4.fc6 (FE6) scons: gemi AT bluewin.ch 5: 0:0.96.1-2.fc5 (FE5) 6: 0:0.96.1-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) smart: Axel.Thimm AT ATrpms.net 5: 0:0.42-34.fc5 (FE5) 6: 0:0.41-31.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) sylpheed-claws: andreas.bierfert AT lowlatency.de 4: 0:2.4.0-1.fc4 (FE4) 5: 0:2.3.1-1.fc5 (FE5) 6: 0:2.4.0-1.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.4-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) wine-docs: andreas.bierfert AT lowlatency.de 3: 0:0.9.17-1.fc3 (FE3) 4: 0:0.9.17-0.1.fc4 (FE4) 5: 0:0.9.17-1.fc5 (FE5) 6: 0:0.9.17-1.fc6 (FE6) xorg-x11-drv-nv: 5: 0:1.2.0-3.fc5 (FC5-updates) 6: 0:1.2.0-2.fc6 (FC6) From buildsys at fedoraproject.org Tue Aug 1 20:52:53 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Tue, 01 Aug 2006 20:52:53 -0000 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-01 Message-ID: <20060801205253.8045.65136@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (117 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (117 days) wine-core - 0.9.17-1.fc6.i386 (6 days) byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (13 days) gaim-guifications - 2.12-3.fc5.ppc (13 days) gaim-guifications - 2.12-3.fc5.x86_64 (13 days) caillon AT redhat.com banshee - 0.10.8-1.i386 (13 days) banshee - 0.10.8-1.ppc (13 days) banshee - 0.10.8-1.x86_64 (13 days) libipoddevice - 0.4.5-1.fc6.i386 (12 days) libipoddevice - 0.4.5-1.fc6.ppc (12 days) libipoddevice - 0.4.5-1.fc6.x86_64 (12 days) cweyl AT alumni.drew.edu gaim-gaym - 0.96-2.fc6.i386 (13 days) gaim-gaym - 0.96-2.fc6.ppc (13 days) gaim-gaym - 0.96-2.fc6.x86_64 (13 days) denis AT poolshark.org galeon - 2.0.1-4.fc6.i386 galeon - 2.0.1-4.fc6.ppc galeon - 2.0.1-4.fc6.x86_64 dennis AT ausil.us knetworkmanager - 0.1-0.3.svn20060625.fc6.i386 (12 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.ppc (12 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.x86_64 (12 days) fedora AT leemhuis.info gsynaptics - 0.9.8-1.fc6.ppc (13 days) frank-buettner AT gmx.net qt4-qsa - 1.2.1-13.fc6.i386 qt4-qsa - 1.2.1-13.fc6.ppc qt4-qsa - 1.2.1-13.fc6.x86_64 gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (5 days) amarok - 1.4.1-3.fc6.ppc (5 days) green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.i386 (6 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (6 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.x86_64 (6 days) jogl - 1.1.1-14.fc5.ppc (9 days) ivazquez AT ivazquez.net gnome-applet-music - 0.9.0-1.fc6.i386 (13 days) gnome-applet-music - 0.9.0-1.fc6.ppc (13 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (13 days) nautilus-search-tool - 0.2-1.fc5.i386 (13 days) nautilus-search-tool - 0.2-1.fc5.ppc (13 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (13 days) j.w.r.degoede AT hhs.nl chess - 1.0-1.fc6.i386 chess - 1.0-1.fc6.ppc chess - 1.0-1.fc6.x86_64 lmacken AT redhat.com python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.i386 (17 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.ppc (17 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.x86_64 (17 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.i386 (17 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.ppc (17 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.x86_64 (17 days) matthias AT rpmforge.net diradmin - 1.7.1-4.fc5.i386 (13 days) diradmin - 1.7.1-4.fc5.ppc (13 days) diradmin - 1.7.1-4.fc5.x86_64 (13 days) gtktalog - 1.0.4-7.fc5.i386 (13 days) gtktalog - 1.0.4-7.fc5.ppc (13 days) gtktalog - 1.0.4-7.fc5.x86_64 (13 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (13 days) gfontview - 0.5.0-5.fc5.ppc (13 days) gfontview - 0.5.0-5.fc5.x86_64 (13 days) gtkhtml36 - 3.6.2-5.fc6.i386 (13 days) gtkhtml36 - 3.6.2-5.fc6.ppc (13 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (13 days) libvisual-plugins - 0.2.0-3.fc5.i386 (13 days) libvisual-plugins - 0.2.0-3.fc5.i386 (13 days) libvisual-plugins - 0.2.0-3.fc5.ppc (13 days) libvisual-plugins - 0.2.0-3.fc5.ppc (13 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (13 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (13 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (13 days) syck-php - 0.55-7.fc5.i386 (13 days) syck-php - 0.55-7.fc5.ppc (13 days) syck-php - 0.55-7.fc5.ppc (13 days) syck-php - 0.55-7.fc5.x86_64 (13 days) syck-php - 0.55-7.fc5.x86_64 (13 days) pertusus AT free.fr cernlib - 2005-21.fc6.ppc (13 days) cernlib-packlib - 2005-21.fc6.ppc (13 days) dap-hdf4_handler - 3.6.0-3.fc5.i386 (9 days) dap-hdf4_handler - 3.6.0-3.fc5.ppc (9 days) dap-hdf4_handler - 3.6.0-3.fc5.x86_64 (9 days) patchy - 2005-21.fc6.ppc (13 days) paw - 2005-21.fc6.ppc (13 days) petersen AT redhat.com ghc642-gtk2hs-mozembed - 0.9.10-1.fc6.i386 ghc642-gtk2hs-mozembed - 0.9.10-1.fc6.ppc ghc642-gtk2hs-mozembed - 0.9.10-1.fc6.x86_64 rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (13 days) libibverbs - 1.0.3-1.fc6.ppc (13 days) libibverbs - 1.0.3-1.fc6.x86_64 (13 days) libibverbs-utils - 1.0.3-1.fc6.i386 (13 days) libibverbs-utils - 1.0.3-1.fc6.ppc (13 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (13 days) thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (13 days) directfb - 0.9.24-5.fc5.ppc (13 days) directfb - 0.9.24-5.fc5.x86_64 (13 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.i386 requires python-protocols >= 0:1.0 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) python-ruledispatch-0.5a0-0.1.svnr2115.fc5.x86_64 requires python-protocols >= 0:1.0 syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.ppc requires python-protocols >= 0:1.0 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.i386 requires python-protocols >= 0:1.0 Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.x86_64 requires python-protocols >= 0:1.0 Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.ppc requires python-protocols >= 0:1.0 Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.i386 requires libgcj.so.7 banshee-0.10.8-1.i386 requires libnautilus-burn.so.3 banshee-0.10.8-1.i386 requires libdbus-1.so.2 chess-1.0-1.fc6.i386 requires libCEGUIOgreRenderer.so.0 chess-1.0-1.fc6.i386 requires libOgreMain.so.11 dap-hdf4_handler-3.6.0-3.fc5.i386 requires libdap.so.4 diradmin-1.7.1-4.fc5.i386 requires libgnomesupport.so.0 diradmin-1.7.1-4.fc5.i386 requires libart_lgpl.so.2 diradmin-1.7.1-4.fc5.i386 requires libgnome.so.32 diradmin-1.7.1-4.fc5.i386 requires libgnomeui.so.32 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.i386 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 galeon-2.0.1-4.fc6.i386 requires mozilla = 37:1.7.13 gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-1.fc6.i386 requires mozilla-devel = 37:1.7.13 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 gtktalog-1.0.4-7.fc5.i386 requires libart_lgpl.so.2 gtktalog-1.0.4-7.fc5.i386 requires gnome-libs >= 0:1.2 gtktalog-1.0.4-7.fc5.i386 requires libgnomesupport.so.0 gtktalog-1.0.4-7.fc5.i386 requires libgnome.so.32 gtktalog-1.0.4-7.fc5.i386 requires libgnomeui.so.32 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-qt-1.so.1 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libipoddevice-0.4.5-1.fc6.i386 requires libdbus-1.so.2 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 qt4-qsa-1.2.1-13.fc6.i386 requires qt4 < 0:4.2 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- azureus-2.4.0.3-0.20060328cvs_5.fc6.x86_64 requires libgcj.so.7()(64bit) banshee-0.10.8-1.x86_64 requires libnautilus-burn.so.3()(64bit) banshee-0.10.8-1.x86_64 requires libdbus-1.so.2()(64bit) chess-1.0-1.fc6.x86_64 requires libCEGUIOgreRenderer.so.0()(64bit) chess-1.0-1.fc6.x86_64 requires libOgreMain.so.11()(64bit) dap-hdf4_handler-3.6.0-3.fc5.x86_64 requires libdap.so.4()(64bit) diradmin-1.7.1-4.fc5.x86_64 requires libgnomesupport.so.0()(64bit) diradmin-1.7.1-4.fc5.x86_64 requires libart_lgpl.so.2()(64bit) diradmin-1.7.1-4.fc5.x86_64 requires libgnome.so.32()(64bit) diradmin-1.7.1-4.fc5.x86_64 requires libgnomeui.so.32()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-gaym-0.96-2.fc6.x86_64 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 galeon-2.0.1-4.fc6.x86_64 requires mozilla = 37:1.7.13 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) ghc642-gtk2hs-mozembed-0.9.10-1.fc6.x86_64 requires mozilla-devel = 37:1.7.13 gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) gtktalog-1.0.4-7.fc5.x86_64 requires libgnomesupport.so.0()(64bit) gtktalog-1.0.4-7.fc5.x86_64 requires gnome-libs >= 0:1.2 gtktalog-1.0.4-7.fc5.x86_64 requires libart_lgpl.so.2()(64bit) gtktalog-1.0.4-7.fc5.x86_64 requires libgnome.so.32()(64bit) gtktalog-1.0.4-7.fc5.x86_64 requires libgnomeui.so.32()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-qt-1.so.1()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-1.so.2()(64bit) libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libipoddevice-0.4.5-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) qt4-qsa-1.2.1-13.fc6.x86_64 requires qt4 < 0:4.2 syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.17-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 banshee-0.10.8-1.ppc requires libnautilus-burn.so.3 banshee-0.10.8-1.ppc requires libdbus-1.so.2 cernlib-2005-21.fc6.ppc requires libg2c.so.0 cernlib-packlib-2005-21.fc6.ppc requires libg2c.so.0 chess-1.0-1.fc6.ppc requires libCEGUIOgreRenderer.so.0 chess-1.0-1.fc6.ppc requires libOgreMain.so.11 dap-hdf4_handler-3.6.0-3.fc5.ppc requires libdap.so.4 diradmin-1.7.1-4.fc5.ppc requires libgnomesupport.so.0 diradmin-1.7.1-4.fc5.ppc requires libart_lgpl.so.2 diradmin-1.7.1-4.fc5.ppc requires libgnome.so.32 diradmin-1.7.1-4.fc5.ppc requires libgnomeui.so.32 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.ppc requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 galeon-2.0.1-4.fc6.ppc requires mozilla = 37:1.7.13 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-1.fc6.ppc requires mozilla-devel = 37:1.7.13 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gsynaptics-0.9.8-1.fc6.ppc requires synaptics gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 gtktalog-1.0.4-7.fc5.ppc requires libart_lgpl.so.2 gtktalog-1.0.4-7.fc5.ppc requires gnome-libs >= 0:1.2 gtktalog-1.0.4-7.fc5.ppc requires libgnomesupport.so.0 gtktalog-1.0.4-7.fc5.ppc requires libgnome.so.32 gtktalog-1.0.4-7.fc5.ppc requires libgnomeui.so.32 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-qt-1.so.1 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libipoddevice-0.4.5-1.fc6.ppc requires libdbus-1.so.2 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 patchy-2005-21.fc6.ppc requires libg2c.so.0 paw-2005-21.fc6.ppc requires libg2c.so.0 qt4-qsa-1.2.1-13.fc6.ppc requires qt4 < 0:4.2 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 ====================================================================== New report for: frank-buettner AT gmx.net package: qt4-qsa - 1.2.1-13.fc6.i386 from fedora-extras-development-i386 unresolved deps: qt4 < 0:4.2 package: qt4-qsa - 1.2.1-13.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: qt4 < 0:4.2 package: qt4-qsa - 1.2.1-13.fc6.ppc from fedora-extras-development-ppc unresolved deps: qt4 < 0:4.2 ====================================================================== New report for: j.w.r.degoede AT hhs.nl package: chess - 1.0-1.fc6.i386 from fedora-extras-development-i386 unresolved deps: libCEGUIOgreRenderer.so.0 libOgreMain.so.11 package: chess - 1.0-1.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libCEGUIOgreRenderer.so.0()(64bit) libOgreMain.so.11()(64bit) package: chess - 1.0-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: libCEGUIOgreRenderer.so.0 libOgreMain.so.11 ====================================================================== New report for: petersen AT redhat.com package: ghc642-gtk2hs-mozembed - 0.9.10-1.fc6.i386 from fedora-extras-development-i386 unresolved deps: mozilla-devel = 37:1.7.13 package: ghc642-gtk2hs-mozembed - 0.9.10-1.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: mozilla-devel = 37:1.7.13 package: ghc642-gtk2hs-mozembed - 0.9.10-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: mozilla-devel = 37:1.7.13 ====================================================================== New report for: denis AT poolshark.org package: galeon - 2.0.1-4.fc6.i386 from fedora-extras-development-i386 unresolved deps: mozilla = 37:1.7.13 package: galeon - 2.0.1-4.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: mozilla = 37:1.7.13 package: galeon - 2.0.1-4.fc6.ppc from fedora-extras-development-ppc unresolved deps: mozilla = 37:1.7.13 From j.w.r.degoede at hhs.nl Tue Aug 1 21:08:33 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Tue, 01 Aug 2006 23:08:33 +0200 Subject: crack attack trademark issues / ok for Fe? Message-ID: <44CFC2D1.4030509@hhs.nl> Hi, I was wondering why the game crack-attack was in that other repo instead of in FE. So I asked the other repo, I got a reply pointing to this post: https://www.redhat.com/archives/fedora-extras-list/2005-April/msg00727.html Which talks about the Tetris trademark. I however do not see how thats an issue as the name crack attack does not seem to use the word Tetris. Now the game play / mechanics may be copied from Tetris Attack, but that is not a problem (IANAL). game play / mechanics cannot be trademarked or copyrighted *. What could be a problem is if the game had copied more then only game mechanics, for example have very similar graphics, identical levels (not relevant here as the levels are not mazes or something similar), etc. Thus I've comapred some screen shots. Here are screenshots from the Trademarked Nintendo original: http://en.wikipedia.org/wiki/Image:Tetris_Attack_box_art.jpg http://en.wikipedia.org/wiki/Image:Lakitu_Tetris_Attack.png And here are those from crack-attack: http://www.nongnu.org/crack-attack/screenshots.html http://www.aluminumangel.org/attack/index.html#screen%20shots Now that seems like original graphics to me. So I would like to reopen the discussion about including crack-attack into FE. I assume there will be objections, if so with arguments please. If there are no objections I'll coordinate moving it to FE with that other repo and submit it for review. Regards, Hans * For more on the copyrightable status of game mechanics see: http://www.copyright.gov/fls/fl108.html . Also keep in mind that many commercial games are essential remakes of older games with better graphics, luckily game mechanics cannot be copyrighted (IANAL). From mattdm at mattdm.org Tue Aug 1 21:10:28 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Tue, 1 Aug 2006 17:10:28 -0400 Subject: crack attack trademark issues / ok for Fe? In-Reply-To: <44CFC2D1.4030509@hhs.nl> References: <44CFC2D1.4030509@hhs.nl> Message-ID: <20060801211028.GA17770@jadzia.bu.edu> On Tue, Aug 01, 2006 at 11:08:33PM +0200, Hans de Goede wrote: > Now the game play / mechanics may be copied from Tetris Attack, but that > is not a problem (IANAL). game play / mechanics cannot be trademarked or > copyrighted *. What could be a problem is if the game had copied more > then only game mechanics, for example have very similar graphics, > identical levels (not relevant here as the levels are not mazes or > something similar), etc. Right. This hasn't stopped the owners of the rights to the original Tetris game from suing people. They're probably wrong, but most people just cave to avoid the hassle. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From wart at kobold.org Tue Aug 1 21:14:22 2006 From: wart at kobold.org (Wart) Date: Tue, 01 Aug 2006 14:14:22 -0700 Subject: crack attack trademark issues / ok for Fe? In-Reply-To: <44CFC2D1.4030509@hhs.nl> References: <44CFC2D1.4030509@hhs.nl> Message-ID: <44CFC42E.80905@kobold.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hans de Goede wrote: > Hi, > > I was wondering why the game crack-attack was in that other repo instead > of in FE. So I asked the other repo, I got a reply pointing to this post: > > https://www.redhat.com/archives/fedora-extras-list/2005-April/msg00727.html This also has ramifications on ltris: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200665 as well as ksmiletris (part of kde-games) and tong (already in FE). - --Mike -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFEz8QtDeYlPfs40g8RAnTFAJ4ummP2ix7cHAAQSO+8HqS6nuorhwCggTOY FH7axGH0g//YUJuALfWoQLc= =2xTO -----END PGP SIGNATURE----- From michael at knox.net.nz Tue Aug 1 23:01:47 2006 From: michael at knox.net.nz (Michael J. Knox) Date: Wed, 02 Aug 2006 11:01:47 +1200 Subject: FE Package Status of Aug 2, 2006 Message-ID: <44CFDD5B.3080201@knox.net.nz> New Extras report for this week. Thanks! Michael FE Package Status of Aug 2, 2006 The full report can be found here: http://fedoraproject.org/wiki/Extras/PackageStatus Owners file stats: - 2057 packages - 37 orphans - 30 packages not available in extras devel or release Fedora at FamilleCollet dot com php-pecl-zip Fedora at FamilleCollet dot com php-pear-HTTP cgoorah at yahoo dot com dot au kadischi davidhart at tqmcube dot com leafnode dennis at ausil dot us oooqs2 fredrik at dolda2000 dot com icmpdn gauret at free dot fr agave ghenry at suretecsystems dot com gnome-applet-netmon ifoox at redhat dot com ht2html ivazquez at ivazquez dot net gpredict j dot w dot r dot degoede at hhs dot nl soundtouch jeff at ollie dot clive dot ia dot us iksemel jpo at di dot uminho dot pt perl-Test-Builder-Tester matthias at rpmforge dot net fillets-ng-data-cs matthias at rpmforge dot net php-mmcache nomis80 at nomis80 dot org juk notting at redhat dot com comps notting at redhat dot com aqhbci-qt-tools oliver at linux-kernel dot at squidGuard paul at city-fan dot org libpng10 rvinyard at cs dot nmsu dot edu bitgtkmm tcallawa at redhat dot com R-RScaLAPACK tcallawa at redhat dot com libgdamm tcallawa at redhat dot com R-hdf5 tcallawa at redhat dot com opendap toniw at iki dot fi silky toniw at iki dot fi libmatchbox toshio at tiki-lounge dot com hula wolters dot liste at gmx dot net ktorrent wtogami at redhat dot com iiimf-le-simplehangul - 9 packages not available in extras devel but present in release andreas at bawue dot net echoping andreas at bawue dot net mboxgrep dakingun at gmail dot com baobab ivazquez at ivazquez dot net gnome-applet-rhythmbox nando at ccrma dot stanford dot edu qjackctl nando at ccrma dot stanford dot edu qsynth noa at resare dot com vorbisgain ville dot skytta at iki dot fi em8300-kmod ville dot skytta at iki dot fi em8300 - 1 packages which have not yet been FE-APPROVE'd... https://bugzilla.redhat.com/bugzilla/buglist.cgi?bug_id=189375 Maelstrom notting at redhat.com - 3 packages present in the development repo which have no owners entry BackupPC ip6sic mercator - 3 orphaned packages, yet available in extras devel dxpc gtkglarea2 soundtracker - 43 packages that moved to core Packages appearing both in Core and Extras: - 6 packages duplicated for devel: jpo at di dot uminho dot pt perl-Net-SSLeay jpo at di dot uminho dot pt perl-IO-Socket-SSL jpo at di dot uminho dot pt perl-Socket6 michael at knox dot net dot nz freeglut petersen at redhat dot com scim-bridge tagoh at redhat dot com paps FE-ACCEPT packages stats: - 1110 accepted, closed package reviews - 7 accepted, closed package reviews not in repo - 7 accepted, open package reviews older than 4 weeks; - 9 accepted, open package reviews with a package already in the repo FE-REVIEW packages stats: - 111 open tickets - 26 tickets with no activity in eight weeks - 16 tickets with no activity in four weeks - 4 closed tickets FE-NEW packages stats: - 175 open tickets - 25 tickets with no activity in eight weeks - 26 tickets with no activity in four weeks FE-NEEDSPONSOR packages stats: - 46 open tickets - 4 tickets with no activity in eight weeks - 5 tickets with no activity in four weeks FE-LEGAL packages stats: - 1 open tickets OPEN-BUGS packages stats: - 248 open tickets - 147 tickets with no activity in eight weeks - 23 tickets with no activity in four weeks CVS stats: - 2068 packages with a devel directory - 29 packages with no owners entry BackupPC gpasman grandr_applet gsview initng ip6sic k3b-ape kernel-module-thinkpad libexif mercator muse nethack-falconseye perl-Convert-ASN1 perl-DateManip perl-GD-SVG perl-Graph perl-Heap perl-Maypole perl-RPM-Specfile perl-SVG perl-Text-Shellwords perl-XML-LibXML-Common perl-XML-NamespaceSupport perl-XML-SAX perl-XML-Writer perl-bioperl php-apc python-ldap zoo - 4 packages in CVS devel *and* Core freeglut libevent pam_pkcs11 paps - 88 packages were dropped from extras Maintainers stats: - 216 maintainers - 19 inactive maintainers with open bugs - 23 inactive maintainers Dropped FC packages: - 270 packages were dropped from core since FC 1 [michael at leroy qa]$ From liljencrantz at gmail.com Wed Aug 2 00:22:05 2006 From: liljencrantz at gmail.com (Axel Liljencrantz) Date: Wed, 2 Aug 2006 02:22:05 +0200 Subject: Update of the fish package In-Reply-To: <20060801214923.e1c28708.bugs.michael@gmx.net> References: <7dad0d770607310841y221983adoc26bde09b3088013@mail.gmail.com> <645d17210608010429s3468cc54s4e1e36fef9724e1f@mail.gmail.com> <200608011343.39141@rineau.schtroumpfette> <200608011139.53076.jkeating@redhat.com> <7dad0d770608010919j4e839126u45cca5d0bb99e5c7@mail.gmail.com> <44CF87BF.5070806@hhs.nl> <7dad0d770608011055i7ff73454xff495a8a17b0b450@mail.gmail.com> <20060801214923.e1c28708.bugs.michael@gmx.net> Message-ID: <7dad0d770608011722h7daf9831y89c7ebf587b0d412@mail.gmail.com> On 8/1/06, Michael Schwendt wrote: > On Tue, 1 Aug 2006 19:55:56 +0200, Axel Liljencrantz wrote: > > > On 8/1/06, Hans de Goede wrote: > > > > > > > > > > > Look at e.g. > > > > > > > > http://roo.no-ip.org/fish/darcs/fish.spec > > > > > > > > can you honestly say that 'nobody could understand the spec'? > > > > > > I understand it, but I concider myself not the average packagers and > > > even for me it hurts my eyes. I know the only conditional stuff in there > > > are the X-requires but thats a 3 times nested if. Now as a C-programmer > > > I generally try to avoid nested conditional statements more then 2 > > > levels deep, for a spec file 3 levels of nesting is just wrong. > > > > > > So I think your example actually makes a strong point for those > > > objecting to one spec for all. > > > > Then we must simply agree to disagree. Strongly. > > > > As a C programmer, I try to avoid tripple-nested if-statements, but > > duplicating 200 lines of code N times (where N is currently 4, but can > > potentially be a large number) simply because 1-2 lines differ between > > versions is an order of magnitude worse. > > Much nicer to the eyes: > > # Locate correct build time-dependencies for providing X headers > %if "%fedora" >= "5" > # Modern Fedora version, has modular X.org > BuildRequires: xorg-x11-proto-devel libX11-devel libXt-devel > %endif > > %if "%fedora" < "5" > %if "%fedora" >= "3" > # Semi-old Fedora version, has non-modular X.org > BuildRequires: xorg-x11-devel > %endif > %endif > > %if "%fedora" < "3" > # Ancient Fedora version, has XFree86 > BuildRequires: XFree86-devel > %endif > > %if 0%{!?fedora} > # This is not a Fedora system, try guessing BuildRequires by > # looking at the directory structure > %define xinclude /usr%(if [ -d /usr/X11R6/include ]; then echo /X11R6; fi)/inclu > de > BuildRequires: %{xinclude}/X11/StringDefs.h, %{xinclude}/X11/Xlib.h > BuildRequires: %{xinclude}/X11/Intrinsic.h, %{xinclude}/X11/Xatom.h > %endif True. Though a bit wordier, it is easier on the eyes and removes the tripple-nesting argument. I'll probably update the spec file. What one really wants, though, is conditional requires. I belive .deb files support something like: BuildRequires: xorg-x11-devel || XFree86-devel || (xorg-x11-proto-devel && libX11-devel && libXt-devel) That would solve the problem in a very neat way. > > -- > fedora-extras-list mailing list > fedora-extras-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-extras-list > -- Axel From christoph.wickert at nurfuerspam.de Wed Aug 2 01:10:52 2006 From: christoph.wickert at nurfuerspam.de (Christoph Wickert) Date: Wed, 02 Aug 2006 03:10:52 +0200 Subject: no feedback from Fedora Ticket System Message-ID: <1154481052.3920.12.camel@hal9000.local.lan> Recently a package of mine failed to build and the buildsys told me to "contact the build system administrator" which I did via Fedora Ticket System/OTRS. Later the issues were resolved and I was able to build my package again. Nevertheless I have not been emailed or contacted and there is absolutely no information in my ticket. It's "successfully closed", but that's all. To me a trouble ticket system, that doesn't inform users and that doesn't hold any information, is just useless. Christoph -- Please do not sent private messages to this address, it is not beeing monitored. Bitte keine pers?nlichen Nachrchten an diese Adresse senden, sie wird nicht ?berwacht. From skvidal at linux.duke.edu Wed Aug 2 04:17:43 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Wed, 02 Aug 2006 00:17:43 -0400 Subject: no feedback from Fedora Ticket System In-Reply-To: <1154481052.3920.12.camel@hal9000.local.lan> References: <1154481052.3920.12.camel@hal9000.local.lan> Message-ID: <1154492263.10944.3.camel@cutter> On Wed, 2006-08-02 at 03:10 +0200, Christoph Wickert wrote: > Recently a package of mine failed to build and the buildsys told me to > "contact the build system administrator" which I did via Fedora Ticket > System/OTRS. > > Later the issues were resolved and I was able to build my package again. > Nevertheless I have not been emailed or contacted and there is > absolutely no information in my ticket. It's "successfully closed", but > that's all. To me a trouble ticket system, that doesn't inform users > and that doesn't hold any information, is just useless. Could you tell us which ticket # it was so we can find out what the story was? Thanks, -sv From cweyl at alumni.drew.edu Wed Aug 2 04:29:22 2006 From: cweyl at alumni.drew.edu (Chris Weyl) Date: Tue, 1 Aug 2006 21:29:22 -0700 Subject: Odd results from make tag / plague Message-ID: <7dd7ab490608012129l41c92cacgbe96a31d0470cef4@mail.gmail.com> Hey all -- I just imported 915resolution, and kicked off a build in devel with "make tag && make plague". It doesn't appear that the makefiles like package names that begin with numbers very much.... --------- [cweyl at zeus devel]$ make tag && make plague cvs tag -c resolution-0_5_2-2_fc6 cvs tag: Tagging . T .cvsignore T 915resolution.spec T Makefile T README.fedora T sources Tagged with: resolution-0_5_2-2_fc6 /usr/bin/plague-client build 915resolution resolution-0_5_2-2_fc6 devel Package 915resolution enqueued. Job ID: 13586. -------- -Chris -- Chris Weyl Ex astris, scientia From j.w.r.degoede at hhs.nl Wed Aug 2 05:02:21 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Wed, 02 Aug 2006 07:02:21 +0200 Subject: crack attack trademark issues / ok for Fe? In-Reply-To: <44CFC42E.80905@kobold.org> References: <44CFC2D1.4030509@hhs.nl> <44CFC42E.80905@kobold.org> Message-ID: <44D031DD.5030705@hhs.nl> Wart wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hans de Goede wrote: >> Hi, >> >> I was wondering why the game crack-attack was in that other repo instead >> of in FE. So I asked the other repo, I got a reply pointing to this post: >> >> https://www.redhat.com/archives/fedora-extras-list/2005-April/msg00727.html > > This also has ramifications on ltris: > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200665 > > as well as ksmiletris (part of kde-games) and tong (already in FE). > Yes indeed, for each game which we package which is inspired by another game we must carefully way if that it was merely inspired (iow uses the same game mechanics / rules) or is just a complete copy. Assuming the graphics were all redrawn by hand (and not taken from screenshots which would be a plain copyright violation) if the graphics are a pretty exact copy its still legally a bit of a gray area (plagiarism). As said in my previous mail for platform games for example, copying the levels even with redrawn / other graphics would probably not be ok. Basicly any copying other then the game concept is most likely not ok :) Also using tris in the name is not helping these other cases. I believe these others should be patched so that they no longer use tris in the name nor reference tetris in the docs, just use "falling blocks game" in the docs instead. I think that a patch in the SRPM removing the use of *tris from the shipped RPMS should be good enough, this is how core does it with gnome-games which also contains a tetris like game. This game is removed from gnome-games in %install, so it it still in the SRPM. Regards, Hans And remember this is all IMHO, IANAL From Axel.Thimm at ATrpms.net Wed Aug 2 05:28:48 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Wed, 2 Aug 2006 07:28:48 +0200 Subject: VTK anyone? In-Reply-To: <20060718173850.GH5874@neu.nirvana> References: <20060710144436.GB5455@free.fr> <44B27321.4060809@cora.nwra.com> <44B3DAA5.4050506@jhu.edu> <20060712075318.GA1242@neu.nirvana> <20060718173850.GH5874@neu.nirvana> Message-ID: <20060802052848.GA30553@neu.nirvana> On Tue, Jul 18, 2006 at 07:38:50PM +0200, Axel Thimm wrote: > On Wed, Jul 12, 2006 at 10:23:19AM +0200, Gianluca Sforna wrote: > > On 7/12/06, Axel Thimm wrote: > > >On Tue, Jul 11, 2006 at 11:24:19PM +0200, Gianluca Sforna wrote: > > >Well, I've already put quite some time into vtk packaging with the > > >intend to push it to extras when it's done and I also need it for my > > >(current) day job, so I'm interested in continuing maintenance. FWIW the packages have been submitted for some time now and have been semi-reviewed. Anyone who wants to finish it off: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199405 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199406 -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From ville.skytta at iki.fi Wed Aug 2 06:54:01 2006 From: ville.skytta at iki.fi (Ville =?ISO-8859-1?Q?Skytt=E4?=) Date: Wed, 02 Aug 2006 09:54:01 +0300 Subject: Odd results from make tag / plague In-Reply-To: <7dd7ab490608012129l41c92cacgbe96a31d0470cef4@mail.gmail.com> References: <7dd7ab490608012129l41c92cacgbe96a31d0470cef4@mail.gmail.com> Message-ID: <1154501641.2743.6.camel@localhost.localdomain> On Tue, 2006-08-01 at 21:29 -0700, Chris Weyl wrote: > Hey all -- > > I just imported 915resolution, and kicked off a build in devel with > "make tag && make plague". It doesn't appear that the makefiles like > package names that begin with numbers very much.... CVS tags must start with a letter (CVS enforces this), so "915resolution-0_5_2-2_fc6" is not an option. Does it cause an actual failure somewhere? If not, I suppose it can be ignored until another "resolution" or "resolution" package enters the repository... From bugs.michael at gmx.net Wed Aug 2 08:31:34 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Wed, 2 Aug 2006 10:31:34 +0200 Subject: no feedback from Fedora Ticket System In-Reply-To: <1154481052.3920.12.camel@hal9000.local.lan> References: <1154481052.3920.12.camel@hal9000.local.lan> Message-ID: <20060802103134.1934c890.bugs.michael@gmx.net> On Wed, 02 Aug 2006 03:10:52 +0200, Christoph Wickert wrote: > Recently a package of mine failed to build and the buildsys told me to > "contact the build system administrator" which I did via Fedora Ticket > System/OTRS. > > Later the issues were resolved and I was able to build my package again. > Nevertheless I have not been emailed or contacted and there is > absolutely no information in my ticket. It's "successfully closed", but > that's all. To me a trouble ticket system, that doesn't inform users > and that doesn't hold any information, is just useless. Same here. I'd like to add that I did not even receive any notification when the ticket was closed. Ticket #2006073010000017 The only mail I got is when I submitted it: | A new ticket has been created in response to your request. | | A member of the team will be in touch with you as soon as possible. | | Thank you for contacting the Fedora Project. From andreas.bierfert at lowlatency.de Wed Aug 2 09:15:22 2006 From: andreas.bierfert at lowlatency.de (Andreas Bierfert) Date: Wed, 2 Aug 2006 11:15:22 +0200 Subject: Extras Buildsys Update In-Reply-To: <200608011016.07140.dennis@ausil.us> References: <200608010038.03674.dennis@ausil.us> <200608010802.12716.dennis@ausil.us> <20060801155126.4dc4fbc2@alkaid.a.lan> <200608011016.07140.dennis@ausil.us> Message-ID: <20060802111522.6bdb07d9@alkaid.a.lan> On Tue, 1 Aug 2006 10:16:06 -0500 Dennis Gilmore wrote: > On Tuesday 01 August 2006 08:51, Andreas Bierfert wrote: > > Hm, both my FC6 builds worked but on this FC5 build I get a strange error > > in root.log... make mockbuild worked fine here: > > http://buildsys.fedoraproject.org/logs/fedora-5-extras/13442-sylpheed-claws > >-2.4.0-1.fc5/i386/root.log > > > > - Andreas > Can you please try again, I made a change to the mock configs to exclude > *.x86_64 it looks like its trying to bring in 64 bit stuff to the i386 build > root. the only place it can get 64 bit packages is the repo of not yet > pushed packages. Just requeued and worked. Thanks for fixing this :) > Thanks for your patience No worries. I just thought letting you know will help you find problems with the upgrade :) - Andreas -- Andreas Bierfert | http://awbsworld.de | GPG: C58CF1CB andreas.bierfert at lowlatency.de | http://lowlatency.de | signed/encrypted phone: +49 2402 102373 | cell: +49 173 5803043 | mail preferred -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From christoph.wickert at nurfuerspam.de Wed Aug 2 09:21:10 2006 From: christoph.wickert at nurfuerspam.de (Christoph Wickert) Date: Wed, 02 Aug 2006 11:21:10 +0200 Subject: no feedback from Fedora Ticket System In-Reply-To: <1154492263.10944.3.camel@cutter> References: <1154481052.3920.12.camel@hal9000.local.lan> <1154492263.10944.3.camel@cutter> Message-ID: <1154510470.3244.3.camel@hal9000.local.lan> Am Mittwoch, den 02.08.2006, 00:17 -0400 schrieb seth vidal: > On Wed, 2006-08-02 at 03:10 +0200, Christoph Wickert wrote: > > Recently a package of mine failed to build and the buildsys told me to > > "contact the build system administrator" which I did via Fedora Ticket > > System/OTRS. > > > > Later the issues were resolved and I was able to build my package again. > > Nevertheless I have not been emailed or contacted and there is > > absolutely no information in my ticket. It's "successfully closed", but > > that's all. To me a trouble ticket system, that doesn't inform users > > and that doesn't hold any information, is just useless. > > Could you tell us which ticket # it was so we can find out what the > story was? 2006072910000038 There's not even a timestamp when the ticket was closed. > > Thanks, > -sv > Christoph -- Please do not sent private messages to this address, it is not beeing monitored. Bitte keine pers?nlichen Nachrchten an diese Adresse senden, sie wird nicht ?berwacht. From thias at spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net Wed Aug 2 11:56:31 2006 From: thias at spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net (Matthias Saou) Date: Wed, 2 Aug 2006 13:56:31 +0200 Subject: When should the mass FE6 rebuild begin? In-Reply-To: <1154452022.2748.138.camel@localhost.localdomain> References: <20060801111338.08c68175@python2> <1154452022.2748.138.camel@localhost.localdomain> Message-ID: <20060802135631.2878c062@python2> Ville Skytt? wrote : > On Tue, 2006-08-01 at 11:13 +0200, Matthias Saou wrote: > > > When should the mass FE6 rebuild begin? > > The current plan is at FC6 test3 time (Aug 30 according to the > preliminary schedule in Wiki). Oh, the schedule has already slipped more than enough for me, as I'll be back by that time :-) Thanks! Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Fedora Core release 5.91 (FC6 Test2) - Linux kernel 2.6.17-1.2462.fc6 Load : 0.48 0.38 0.29 From mr.ecik at gmail.com Wed Aug 2 12:03:32 2006 From: mr.ecik at gmail.com (=?ISO-8859-2?Q?Micha=B3_Bentkowski?=) Date: Wed, 2 Aug 2006 14:03:32 +0200 Subject: When should the mass FE6 rebuild begin? In-Reply-To: <1154452022.2748.138.camel@localhost.localdomain> References: <20060801111338.08c68175@python2> <1154452022.2748.138.camel@localhost.localdomain> Message-ID: <668bb39a0608020503t673701dfs355b358fa3592720@mail.gmail.com> > The current plan is at FC6 test3 time (Aug 30 according to the > preliminary schedule in Wiki). On Aug 30 I will be on holidays. Could somebody build my packages (kadu and python-mutagen)? From skvidal at linux.duke.edu Wed Aug 2 12:20:44 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Wed, 02 Aug 2006 08:20:44 -0400 Subject: no feedback from Fedora Ticket System In-Reply-To: <1154510470.3244.3.camel@hal9000.local.lan> References: <1154481052.3920.12.camel@hal9000.local.lan> <1154492263.10944.3.camel@cutter> <1154510470.3244.3.camel@hal9000.local.lan> Message-ID: <1154521244.10944.35.camel@cutter> On Wed, 2006-08-02 at 11:21 +0200, Christoph Wickert wrote: > Am Mittwoch, den 02.08.2006, 00:17 -0400 schrieb seth vidal: > > On Wed, 2006-08-02 at 03:10 +0200, Christoph Wickert wrote: > > > Recently a package of mine failed to build and the buildsys told me to > > > "contact the build system administrator" which I did via Fedora Ticket > > > System/OTRS. > > > > > > Later the issues were resolved and I was able to build my package again. > > > Nevertheless I have not been emailed or contacted and there is > > > absolutely no information in my ticket. It's "successfully closed", but > > > that's all. To me a trouble ticket system, that doesn't inform users > > > and that doesn't hold any information, is just useless. > > > > Could you tell us which ticket # it was so we can find out what the > > story was? > > 2006072910000038 > > There's not even a timestamp when the ticket was closed. Weird. I can't find or see anything in the interface either and I'm marked as one of the admins. Mike, do you know what's going on here? -sv From j.w.r.degoede at hhs.nl Wed Aug 2 13:18:05 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Wed, 02 Aug 2006 15:18:05 +0200 Subject: crack attack trademark issues / ok for Fe? In-Reply-To: <20060801211028.GA17770@jadzia.bu.edu> References: <44CFC2D1.4030509@hhs.nl> <20060801211028.GA17770@jadzia.bu.edu> Message-ID: <44D0A60D.20202@hhs.nl> Matthew Miller wrote: > On Tue, Aug 01, 2006 at 11:08:33PM +0200, Hans de Goede wrote: >> Now the game play / mechanics may be copied from Tetris Attack, but that >> is not a problem (IANAL). game play / mechanics cannot be trademarked or >> copyrighted *. What could be a problem is if the game had copied more >> then only game mechanics, for example have very similar graphics, >> identical levels (not relevant here as the levels are not mazes or >> something similar), etc. > > Right. This hasn't stopped the owners of the rights to the original Tetris > game from suing people. They're probably wrong, but most people just cave to > avoid the hassle. > I know that the owners of the rights to the original Tetris are sue happy. I'm wondering what point you're trying to make here: that it is a good thing that crack-attack is not in FE because of this sue happines, or are you trying to say that indeed crack-attack should be fine for FE, but that the sue happiness worries you? Regards, Hans From mattdm at mattdm.org Wed Aug 2 13:38:38 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Wed, 2 Aug 2006 09:38:38 -0400 Subject: crack attack trademark issues / ok for Fe? In-Reply-To: <44D0A60D.20202@hhs.nl> References: <44CFC2D1.4030509@hhs.nl> <20060801211028.GA17770@jadzia.bu.edu> <44D0A60D.20202@hhs.nl> Message-ID: <20060802133838.GA20490@jadzia.bu.edu> On Wed, Aug 02, 2006 at 03:18:05PM +0200, Hans de Goede wrote: > > Right. This hasn't stopped the owners of the rights to the original > > Tetris game from suing people. They're probably wrong, but most people > > just cave to avoid the hassle. > I know that the owners of the rights to the original Tetris are sue > happy. I'm wondering what point you're trying to make here: that it is a > good thing that crack-attack is not in FE because of this sue happines, > or are you trying to say that indeed crack-attack should be fine for FE, > but that the sue happiness worries you? I simply am supposing that it is in the other repo because of this concern, regardless of its merits. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From cweyl at alumni.drew.edu Wed Aug 2 14:29:50 2006 From: cweyl at alumni.drew.edu (Chris Weyl) Date: Wed, 2 Aug 2006 07:29:50 -0700 Subject: Odd results from make tag / plague In-Reply-To: <1154501641.2743.6.camel@localhost.localdomain> References: <7dd7ab490608012129l41c92cacgbe96a31d0470cef4@mail.gmail.com> <1154501641.2743.6.camel@localhost.localdomain> Message-ID: <7dd7ab490608020729q61286d4fuafc7c4966cb6884a@mail.gmail.com> On 8/1/06, Ville Skytt? wrote: > On Tue, 2006-08-01 at 21:29 -0700, Chris Weyl wrote: > > Hey all -- > > > > I just imported 915resolution, and kicked off a build in devel with > > "make tag && make plague". It doesn't appear that the makefiles like > > package names that begin with numbers very much.... > > CVS tags must start with a letter (CVS enforces this), so > "915resolution-0_5_2-2_fc6" is not an option. Does it cause an actual > failure somewhere? If not, I suppose it can be ignored until another > "resolution" or "resolution" package enters the repository... No -- everything went through cleanly, aside from dropping the leading 915. I could see a conflict if we had a package called "resolution" with the same versions, but otherwise it's just an oddity. -Chris -- Chris Weyl Ex astris, scientia From bugs.michael at gmx.net Wed Aug 2 15:12:50 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Wed, 2 Aug 2006 17:12:50 +0200 Subject: crack attack trademark issues / ok for Fe? In-Reply-To: <44CFC2D1.4030509@hhs.nl> References: <44CFC2D1.4030509@hhs.nl> Message-ID: <20060802171250.f7e8082d.bugs.michael@gmx.net> On Tue, 01 Aug 2006 23:08:33 +0200, Hans de Goede wrote: > Hi, > > I was wondering why the game crack-attack was in that other repo instead > of in FE. With more searching it might be possible to find more references to prior discussion. This has come up before and also before April 2005. So I asked the other repo, I got a reply pointing to this post: > > https://www.redhat.com/archives/fedora-extras-list/2005-April/msg00727.html This doesn't contain any details. > Which talks about the Tetris trademark. I however do not see how thats > an issue as the name crack attack does not seem to use the word Tetris. Maybe it does no longer. The game web page still does. Wikipedia gives a brief summary of all the legal rumblings around clones of Tetris, which didn't use the same name. Enough reason to be concerned unless you're a lawyer. From wart at kobold.org Wed Aug 2 16:35:36 2006 From: wart at kobold.org (Michael Thomas) Date: Wed, 02 Aug 2006 09:35:36 -0700 Subject: duplicate %files in mock Message-ID: <44D0D458.3080407@kobold.org> While working on cyphesis (BZ #200976) I discovered that rpmbuild's warnings about duplicates in %files don't appear when a package is built in mock. That is, if you have: %files %{_datadir}/foo %ghost %{_datadir}/foo/bar.txt ...them rpmbuild, when run from the command line in FC5/FC6, will issue the warning: warning: File listed twice: /usr/share/foo/bar.txt But when run through mock, this warning doesn't appear. Isn't this something that mock should be reporting? --Wart -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3820 bytes Desc: S/MIME Cryptographic Signature URL: From wart at kobold.org Wed Aug 2 16:53:20 2006 From: wart at kobold.org (Michael Thomas) Date: Wed, 02 Aug 2006 09:53:20 -0700 Subject: desktop icons In-Reply-To: <44CDA403.8010107@hhs.nl> References: <44CD9FED.1050903@kobold.org> <44CDA403.8010107@hhs.nl> Message-ID: <44D0D880.7080402@kobold.org> Hans de Goede wrote: > > Wart wrote: > >>What is the preferred directory for storing desktop icons? I've seen >>some packages use %{_datadir}/icons/hicolor/, while others put >>them in %{_datadir}/pixmaps. >> >>--Mike > > > According to the freedesktop.org icon standard it is > %{_datadir}/icons/hicolor/, this is where all my packages put them > and I've even blocked reviews on poluting /usr/share/pixmaps with icons > (which will work too to support legacy apps). Thanks for the pointer. This is what I had thought. --Mike -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3820 bytes Desc: S/MIME Cryptographic Signature URL: From florin at andrei.myip.org Wed Aug 2 17:03:57 2006 From: florin at andrei.myip.org (Florin Andrei) Date: Wed, 02 Aug 2006 10:03:57 -0700 Subject: Genius math tool Message-ID: <1154538237.15293.2.camel@stantz.corp.sgi.com> Anybody already working to maintain this in Extras? http://www.jirka.org/genius.html -- Florin Andrei http://florin.myip.org/ From jpmahowald at gmail.com Wed Aug 2 17:26:13 2006 From: jpmahowald at gmail.com (John Mahowald) Date: Wed, 2 Aug 2006 12:26:13 -0500 Subject: Genius math tool In-Reply-To: <1154538237.15293.2.camel@stantz.corp.sgi.com> References: <1154538237.15293.2.camel@stantz.corp.sgi.com> Message-ID: <3ea997540608021026u686ee772r3e7530881821a8aa@mail.gmail.com> On 8/2/06, Florin Andrei wrote: > Anybody already working to maintain this in Extras? > > http://www.jirka.org/genius.html > Proposed to the Sci Tech SIG. http://fedoraproject.org/wiki/Extras/SIGs/SciTech John From j.w.r.degoede at hhs.nl Wed Aug 2 18:14:37 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Wed, 02 Aug 2006 20:14:37 +0200 Subject: crack attack trademark issues / ok for Fe? In-Reply-To: <20060802171250.f7e8082d.bugs.michael@gmx.net> References: <44CFC2D1.4030509@hhs.nl> <20060802171250.f7e8082d.bugs.michael@gmx.net> Message-ID: <44D0EB8D.5010209@hhs.nl> Michael Schwendt wrote: > On Tue, 01 Aug 2006 23:08:33 +0200, Hans de Goede wrote: > >> Hi, >> >> I was wondering why the game crack-attack was in that other repo instead >> of in FE. > > With more searching it might be possible to find more references to prior > discussion. This has come up before and also before April 2005. > > So I asked the other repo, I got a reply pointing to this post: >> https://www.redhat.com/archives/fedora-extras-list/2005-April/msg00727.html > > This doesn't contain any details. > >> Which talks about the Tetris trademark. I however do not see how thats >> an issue as the name crack attack does not seem to use the word Tetris. > > Maybe it does no longer. The game web page still does. > > Wikipedia gives a brief summary of all the legal rumblings around clones > of Tetris, which didn't use the same name. Enough reason to be concerned > unless you're a lawyer. > I think (IANAL) that the owners of the Tetris Trademark have no legal standing against Crack Attack, because it only has similar game mechanics and the name and graphics are different. Mere mentioning of the name Tetris Attack, in the context of pointing out that Crack-attack has similar game play is not a legal problem. If that is a legal problem, then we wave a lot, really a lot of packages with this problem. Dia claims to be similar to visio, openoffice claims to be similar to and compatible with microsoft word / excell. gnumeric claims to have reached 100% of excel's functionality, etc. And even closer to this case we have freeciv, which even has part of the name the same and lincity, which both are in FE. The *mere* fact that in this case the owner of the product mentioned in comparison is a bit trigger happy with sueing shouldn't mean that we thus don't ship it. That is a *very* bad precedent to set, that is giving in to blackmail, which is asking for a lot more blackmail! Now I could live with stripping the mention of Tetris from the version we ship, but not shipping because the original homepage then still mentions it is ridiculous. The owners of Tetris already have very little legal standing in this case, especially against us since we are merely distributing and they have left upstream alone for years. Going after us, with as argument that we link to a homepage which mentions their trademark (in what is probably a fair use way) is a very long shot, and will most likely get thrown out of court pretty fast (IANAL). So, does submitting a version with any mention of Tetris removed sound ok? If not can someone please ask RH legals department for advice on this? Regards, Hans From gajownik at gmail.com Wed Aug 2 19:15:48 2006 From: gajownik at gmail.com (Dawid Gajownik) Date: Wed, 02 Aug 2006 21:15:48 +0200 Subject: %lang macro does not work with %doc? Message-ID: <44D0F9E4.4060108@gmail.com> Hi! I wanted to help reviewing libgadu (#200348). In this package documentation is written in Polish. It's not a problem for me and other folks from Poland but others will find it useless ;-) I put this into /root/.rpmmacros %_install_langs en:en_US:C and changed libgadu.spec to include this lines %doc lib/COPYING %lang(pl) %doc docs/{README,TODO} ChangeLog Unfortunately, it does not work - files README, TODO and ChangeLog should not be installed but they are. Have I missed something? Regards, Dawid -- ^_* From djsparymtz at yahoo.com Wed Aug 2 19:57:28 2006 From: djsparymtz at yahoo.com (djspary) Date: Wed, 2 Aug 2006 12:57:28 -0700 (PDT) Subject: %lang macro does not work with %doc? In-Reply-To: <44D0F9E4.4060108@gmail.com> Message-ID: <20060802195728.61300.qmail@web34102.mail.mud.yahoo.com> thanks for the addvice --- Dawid Gajownik wrote: > Hi! > > I wanted to help reviewing libgadu (#200348). In > this package > documentation is written in Polish. It's not a > problem for me and other > folks from Poland but others will find it useless > ;-) > > I put this into /root/.rpmmacros > > %_install_langs en:en_US:C > > and changed libgadu.spec to include this lines > > %doc lib/COPYING > %lang(pl) %doc docs/{README,TODO} ChangeLog > > Unfortunately, it does not work - files README, TODO > and ChangeLog > should not be installed but they are. Have I missed > something? > > Regards, > Dawid > > -- > > ^_* > > -- > fedora-extras-list mailing list > fedora-extras-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-extras-list > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From buildsys at fedoraproject.org Wed Aug 2 20:11:36 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Wed, 2 Aug 2006 16:11:36 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-02 Message-ID: <20060802201136.25FBA152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 20 amavisd-new-2.4.2-2.fc5 aplus-fsf-4.20.2-5.fc5 auriferous-1.0.1-2.fc5 bitgtkmm-0.2.2-4.fc5 cairomm-0.6.0-2.fc5 cmake-2.4.3-2.fc5 crystal-stacker-themes-1.0-2.fc5 digikam-0.8.2-1.fc5 dogtail-0.5.2-2.fc5 git-1.4.1-1.fc5 gtksourceview-sharp-2.0-15.fc5 inotify-tools-2.2-3.fc5 nautilus-open-terminal-0.7-1.fc5 perl-Gtk2-Sexy-0.02-4.fc5 puppet-0.18.4-2.fc5 pyspi-0.5.5-1.fc5 qstat-2.10-4.fc5 rrdtool-1.2.15-3.fc5 sylpheed-claws-2.4.0-1.fc5 torque-2.1.2-1.fc5 Packages built and released for Fedora Extras 4: 11 amavisd-new-2.4.2-2.fc4 bitgtkmm-0.2.2-4.fc4 cmake-2.4.3-2.fc4 digikam-0.8.2-1.fc4 git-1.4.1-1.fc4 glibmm24-2.6.6-1 perl-Gtk2-Sexy-0.02-4.fc4 puppet-0.18.4-2.fc4 qstat-2.10-4.fc4 rrdtool-1.2.15-3.fc4 torque-2.1.2-1.fc4 Packages built and released for Fedora Extras 3: 3 amavisd-new-2.4.2-2.fc3 digikam-0.8.2-2.fc3 torque-2.1.2-1.fc3 Packages built and released for Fedora Extras development: 25 915resolution-0.5.2-3.fc6 XaraLX-0.7-2.fc6.r1614 amavisd-new-2.4.2-2.fc6 bitgtkmm-0.2.2-4.fc6 camE-1.9-6.fc6 celestia-1.4.1-4.fc6 chess-1.0-2.fc6 cmake-2.4.3-2.fc6 cone-0.68-1.fc6 crystal-stacker-themes-1.0-2.fc6 digikam-0.8.2-1.fc6 galeon-2.0.1-5.fc6 gtk2hs-0.9.10-2.fc6 libpng10-1.0.20-3.fc6 nautilus-open-terminal-0.7-1.fc6 nip2-7.10.20-1.fc6 pdsh-2.11-2.fc6 puppet-0.18.4-2.fc6 qjackctl-0.2.20-5.fc6 qsynth-0.2.5-5.fc6 rrdtool-1.2.15-3.fc6 soundtouch-1.3.1-5.fc6 torque-2.1.2-1.fc6 uuid-1.5.0-1.fc6 yum-utils-0.6-5.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Wed Aug 2 20:12:03 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Wed, 2 Aug 2006 16:12:03 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-02 Message-ID: <20060802201203.A0C2B152169@buildsys.fedoraproject.org> azureus: green AT redhat.com 5: 0:2.4.0.3-0.20060529cvs_1.fc5 (FE5) 6: 0:2.4.0.3-0.20060328cvs_5.fc6 (FE6) banshee: caillon AT redhat.com 5: 0:0.10.9-1..fc5 (FE5) 6: 0:0.10.8-1 (FE6) cairomm: rvinyard AT cs.nmsu.edu 5: 0:0.6.0-2.fc5 (FE5) 6: 0:0.6.0-1.fc6 (FE6) camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) digikam: mgarski AT post.pl 3: 0:0.8.2-2.fc3 (FE3) 4: 0:0.8.2-1.fc4 (FE4) 5: 0:0.8.2-1.fc5 (FE5) 6: 0:0.8.2-1.fc6 (FE6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) dogtail: zcerza AT redhat.com 5: 0:0.5.2-2.fc5 (FE5) 6: 0:0.5.2-1.fc6 (FC6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: oliver AT linux-kernel.at 4: 0:1.14.0-1.fc4 (FE4) 5: 0:1.12.0-1.fc5 (FE5) 6: 0:1.12.0-1.fc5 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gaim-gaym: cweyl AT alumni.drew.edu 5: 0:0.96-3.fc5 (FE5) 6: 0:0.96-2.fc6 (FE6) gauche-gl: gemi AT bluewin.ch 5: 0:0.4.1-5.fc5 (FE5) 6: 0:0.4.1-4.fc6 (FE6) gcdmaster: denis AT poolshark.org 4: 0:1.2.1-5.fc4 (FE4) 5: 0:1.2.1-4.fc5 (FE5) 6: 0:1.2.1-4.fc5 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) gtksourceview-sharp: paul AT all-the-johnsons.co.uk 5: 0:2.0-15.fc5 (FE5) 6: 0:2.0-14.fc6 (FE6) icon-naming-utils: 5: 0:0.7.3-1.fc5 (FC5-updates) 6: 0:0.7.3-1 (FC6) inkscape: denis AT poolshark.org 4: 0:0.44-3.fc4 (FE4) 5: 0:0.44-2.fc5 (FE5) 6: 0:0.44-2.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) libnasl: andreas.bierfert AT lowlatency.de 5: 0:2.2.8-1.fc5 (FE5) 6: 0:2.2.7-1.fc6 (FE6) libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) lvm2: 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-16.fc6 (FC6) mozilla: 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) nfs-utils: 5: 1:1.0.8-2.fc5 (FC5-updates) 6: 0:1.0.9-2.fc6 (FC6) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-1.FC6.1 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.1-2.fc5 (FE5) 6: 0:1.0.1-1.fc5 (FE6) quagga: 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-anthy: tagoh AT redhat.com 5: 0:1.2.0-1.fc5.1 (FC5-updates) 6: 0:1.0.0-4.fc6 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5 (FE5) 6: 0:0.2.0-4.fc6 (FE6) scons: gemi AT bluewin.ch 5: 0:0.96.1-2.fc5 (FE5) 6: 0:0.96.1-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) smart: Axel.Thimm AT ATrpms.net 5: 0:0.42-34.fc5 (FE5) 6: 0:0.41-31.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.4-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) wine-docs: andreas.bierfert AT lowlatency.de 3: 0:0.9.17-1.fc3 (FE3) 4: 0:0.9.17-0.1.fc4 (FE4) 5: 0:0.9.17-1.fc5 (FE5) 6: 0:0.9.17-1.fc6 (FE6) xorg-x11-drv-nv: 5: 0:1.2.0-3.fc5 (FC5-updates) 6: 0:1.2.0-2.fc6 (FC6) From buildsys at fedoraproject.org Wed Aug 2 20:33:29 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Wed, 02 Aug 2006 20:33:29 -0000 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-02 Message-ID: <20060802203329.18048.29585@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (118 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (118 days) wine-core - 0.9.17-1.fc6.i386 (7 days) byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (14 days) gaim-guifications - 2.12-3.fc5.ppc (14 days) gaim-guifications - 2.12-3.fc5.x86_64 (14 days) caillon AT redhat.com banshee - 0.10.8-1.i386 (14 days) banshee - 0.10.8-1.ppc (14 days) banshee - 0.10.8-1.x86_64 (14 days) libipoddevice - 0.4.5-1.fc6.i386 (13 days) libipoddevice - 0.4.5-1.fc6.ppc (13 days) libipoddevice - 0.4.5-1.fc6.x86_64 (13 days) cweyl AT alumni.drew.edu gaim-gaym - 0.96-2.fc6.i386 (14 days) gaim-gaym - 0.96-2.fc6.ppc (14 days) gaim-gaym - 0.96-2.fc6.x86_64 (14 days) dennis AT ausil.us knetworkmanager - 0.1-0.3.svn20060625.fc6.i386 (13 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.ppc (13 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.x86_64 (13 days) fedora AT leemhuis.info gsynaptics - 0.9.8-1.fc6.ppc (14 days) frank-buettner AT gmx.net qt4-qsa - 1.2.1-13.fc6.i386 qt4-qsa - 1.2.1-13.fc6.ppc qt4-qsa - 1.2.1-13.fc6.x86_64 gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (6 days) amarok - 1.4.1-3.fc6.ppc (6 days) green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.i386 (7 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (7 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.x86_64 (7 days) jogl - 1.1.1-14.fc5.ppc (10 days) ivazquez AT ivazquez.net gnome-applet-music - 0.9.0-1.fc6.i386 (14 days) gnome-applet-music - 0.9.0-1.fc6.ppc (14 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (14 days) nautilus-search-tool - 0.2-1.fc5.i386 (14 days) nautilus-search-tool - 0.2-1.fc5.ppc (14 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (14 days) lmacken AT redhat.com python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.i386 (18 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.ppc (18 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.x86_64 (18 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.i386 (18 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.ppc (18 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.x86_64 (18 days) matthias AT rpmforge.net diradmin - 1.7.1-4.fc5.i386 (14 days) diradmin - 1.7.1-4.fc5.ppc (14 days) diradmin - 1.7.1-4.fc5.x86_64 (14 days) gtktalog - 1.0.4-7.fc5.i386 (14 days) gtktalog - 1.0.4-7.fc5.ppc (14 days) gtktalog - 1.0.4-7.fc5.x86_64 (14 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (14 days) gfontview - 0.5.0-5.fc5.ppc (14 days) gfontview - 0.5.0-5.fc5.x86_64 (14 days) gtkhtml36 - 3.6.2-5.fc6.i386 (14 days) gtkhtml36 - 3.6.2-5.fc6.ppc (14 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (14 days) libvisual-plugins - 0.2.0-3.fc5.i386 (14 days) libvisual-plugins - 0.2.0-3.fc5.i386 (14 days) libvisual-plugins - 0.2.0-3.fc5.ppc (14 days) libvisual-plugins - 0.2.0-3.fc5.ppc (14 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (14 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (14 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (77 days) syck-php - 0.55-7.fc5.i386 (77 days) syck-php - 0.55-7.fc5.ppc (77 days) syck-php - 0.55-7.fc5.ppc (77 days) syck-php - 0.55-7.fc5.x86_64 (77 days) syck-php - 0.55-7.fc5.x86_64 (77 days) pertusus AT free.fr cernlib - 2005-21.fc6.ppc (14 days) cernlib-packlib - 2005-21.fc6.ppc (14 days) dap-hdf4_handler - 3.6.0-3.fc5.i386 (10 days) dap-hdf4_handler - 3.6.0-3.fc5.ppc (10 days) dap-hdf4_handler - 3.6.0-3.fc5.x86_64 (10 days) patchy - 2005-21.fc6.ppc (14 days) paw - 2005-21.fc6.ppc (14 days) petersen AT redhat.com scim-bridge - 0.1.12-1.fc5.i386 scim-bridge - 0.1.12-1.fc5.ppc scim-bridge - 0.1.12-1.fc5.x86_64 qshen AT redhat.com scim-fcitx-tools - 3.1.1-4.1.fc5.i386 scim-fcitx-tools - 3.1.1-4.1.fc5.ppc scim-fcitx-tools - 3.1.1-4.1.fc5.x86_64 rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (14 days) libibverbs - 1.0.3-1.fc6.ppc (14 days) libibverbs - 1.0.3-1.fc6.x86_64 (14 days) libibverbs-utils - 1.0.3-1.fc6.i386 (14 days) libibverbs-utils - 1.0.3-1.fc6.ppc (14 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (14 days) thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (14 days) directfb - 0.9.24-5.fc5.ppc (14 days) directfb - 0.9.24-5.fc5.x86_64 (14 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.i386 requires python-protocols >= 0:1.0 scim-bridge-0.1.12-1.fc5.i386 requires libstdc++-20060428.so.7 scim-bridge-0.1.12-1.fc5.i386 requires libstdc++-20060428.so.7(CXXABI_1.4) scim-bridge-0.1.12-1.fc5.i386 requires libstdc++-20060428.so.7(GLIBCXX_4.2) scim-fcitx-tools-3.1.1-4.1.fc5.i386 requires libstdc++-20060428.so.7 scim-fcitx-tools-3.1.1-4.1.fc5.i386 requires libstdc++-20060428.so.7(GLIBCXX_4.2) scim-fcitx-tools-3.1.1-4.1.fc5.i386 requires libstdc++-20060428.so.7(CXXABI_1.4) syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) python-ruledispatch-0.5a0-0.1.svnr2115.fc5.x86_64 requires python-protocols >= 0:1.0 scim-bridge-0.1.12-1.fc5.x86_64 requires libstdc++-20060428.so.7(CXXABI_1.4)(64bit) scim-bridge-0.1.12-1.fc5.x86_64 requires libstdc++-20060428.so.7()(64bit) scim-bridge-0.1.12-1.fc5.x86_64 requires libstdc++-20060428.so.7(GLIBCXX_4.2)(64bit) scim-fcitx-tools-3.1.1-4.1.fc5.x86_64 requires libstdc++-20060428.so.7(CXXABI_1.4)(64bit) scim-fcitx-tools-3.1.1-4.1.fc5.x86_64 requires libstdc++-20060428.so.7()(64bit) scim-fcitx-tools-3.1.1-4.1.fc5.x86_64 requires libstdc++-20060428.so.7(GLIBCXX_4.2)(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.ppc requires python-protocols >= 0:1.0 scim-bridge-0.1.12-1.fc5.ppc requires libstdc++-20060428.so.7 scim-bridge-0.1.12-1.fc5.ppc requires libstdc++-20060428.so.7(CXXABI_1.4) scim-bridge-0.1.12-1.fc5.ppc requires libstdc++-20060428.so.7(GLIBCXX_4.2) scim-fcitx-tools-3.1.1-4.1.fc5.ppc requires libstdc++-20060428.so.7 scim-fcitx-tools-3.1.1-4.1.fc5.ppc requires libstdc++-20060428.so.7(GLIBCXX_4.2) scim-fcitx-tools-3.1.1-4.1.fc5.ppc requires libstdc++-20060428.so.7(CXXABI_1.4) syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.i386 requires python-protocols >= 0:1.0 Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.x86_64 requires python-protocols >= 0:1.0 Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.ppc requires python-protocols >= 0:1.0 Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.i386 requires libgcj.so.7 banshee-0.10.8-1.i386 requires libnautilus-burn.so.3 banshee-0.10.8-1.i386 requires libdbus-1.so.2 dap-hdf4_handler-3.6.0-3.fc5.i386 requires libdap.so.4 diradmin-1.7.1-4.fc5.i386 requires libgnomesupport.so.0 diradmin-1.7.1-4.fc5.i386 requires libart_lgpl.so.2 diradmin-1.7.1-4.fc5.i386 requires libgnome.so.32 diradmin-1.7.1-4.fc5.i386 requires libgnomeui.so.32 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.i386 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 gtktalog-1.0.4-7.fc5.i386 requires libart_lgpl.so.2 gtktalog-1.0.4-7.fc5.i386 requires gnome-libs >= 0:1.2 gtktalog-1.0.4-7.fc5.i386 requires libgnomesupport.so.0 gtktalog-1.0.4-7.fc5.i386 requires libgnome.so.32 gtktalog-1.0.4-7.fc5.i386 requires libgnomeui.so.32 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-qt-1.so.1 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libipoddevice-0.4.5-1.fc6.i386 requires libdbus-1.so.2 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 qt4-qsa-1.2.1-13.fc6.i386 requires qt4 < 0:4.2 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- azureus-2.4.0.3-0.20060328cvs_5.fc6.x86_64 requires libgcj.so.7()(64bit) banshee-0.10.8-1.x86_64 requires libnautilus-burn.so.3()(64bit) banshee-0.10.8-1.x86_64 requires libdbus-1.so.2()(64bit) dap-hdf4_handler-3.6.0-3.fc5.x86_64 requires libdap.so.4()(64bit) diradmin-1.7.1-4.fc5.x86_64 requires libgnomesupport.so.0()(64bit) diradmin-1.7.1-4.fc5.x86_64 requires libart_lgpl.so.2()(64bit) diradmin-1.7.1-4.fc5.x86_64 requires libgnome.so.32()(64bit) diradmin-1.7.1-4.fc5.x86_64 requires libgnomeui.so.32()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-gaym-0.96-2.fc6.x86_64 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) gtktalog-1.0.4-7.fc5.x86_64 requires libgnomesupport.so.0()(64bit) gtktalog-1.0.4-7.fc5.x86_64 requires gnome-libs >= 0:1.2 gtktalog-1.0.4-7.fc5.x86_64 requires libart_lgpl.so.2()(64bit) gtktalog-1.0.4-7.fc5.x86_64 requires libgnome.so.32()(64bit) gtktalog-1.0.4-7.fc5.x86_64 requires libgnomeui.so.32()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-qt-1.so.1()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-1.so.2()(64bit) libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libipoddevice-0.4.5-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) qt4-qsa-1.2.1-13.fc6.x86_64 requires qt4 < 0:4.2 syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.17-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 banshee-0.10.8-1.ppc requires libnautilus-burn.so.3 banshee-0.10.8-1.ppc requires libdbus-1.so.2 cernlib-2005-21.fc6.ppc requires libg2c.so.0 cernlib-packlib-2005-21.fc6.ppc requires libg2c.so.0 dap-hdf4_handler-3.6.0-3.fc5.ppc requires libdap.so.4 diradmin-1.7.1-4.fc5.ppc requires libgnomesupport.so.0 diradmin-1.7.1-4.fc5.ppc requires libart_lgpl.so.2 diradmin-1.7.1-4.fc5.ppc requires libgnome.so.32 diradmin-1.7.1-4.fc5.ppc requires libgnomeui.so.32 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.ppc requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gsynaptics-0.9.8-1.fc6.ppc requires synaptics gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 gtktalog-1.0.4-7.fc5.ppc requires libart_lgpl.so.2 gtktalog-1.0.4-7.fc5.ppc requires gnome-libs >= 0:1.2 gtktalog-1.0.4-7.fc5.ppc requires libgnomesupport.so.0 gtktalog-1.0.4-7.fc5.ppc requires libgnome.so.32 gtktalog-1.0.4-7.fc5.ppc requires libgnomeui.so.32 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-qt-1.so.1 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libipoddevice-0.4.5-1.fc6.ppc requires libdbus-1.so.2 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 patchy-2005-21.fc6.ppc requires libg2c.so.0 paw-2005-21.fc6.ppc requires libg2c.so.0 qt4-qsa-1.2.1-13.fc6.ppc requires qt4 < 0:4.2 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 ====================================================================== New report for: cweyl AT alumni.drew.edu package: gaim-gaym - 0.96-2.fc6.i386 from fedora-extras-development-i386 unresolved deps: gaim < 1:2.0.0 package: gaim-gaym - 0.96-2.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: gaim < 1:2.0.0 package: gaim-gaym - 0.96-2.fc6.ppc from fedora-extras-development-ppc unresolved deps: gaim < 1:2.0.0 ====================================================================== New report for: mpeters AT mac.com package: gfontview - 0.5.0-5.fc5.i386 from fedora-extras-development-i386 unresolved deps: libttf.so.2 package: gtkhtml36 - 3.6.2-5.fc6.i386 from fedora-extras-development-i386 unresolved deps: libgailutil.so.17 package: gtkhtml36 - 3.6.2-5.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libgailutil.so.17()(64bit) package: gfontview - 0.5.0-5.fc5.x86_64 from fedora-extras-development-x86_64 unresolved deps: libttf.so.2()(64bit) package: gfontview - 0.5.0-5.fc5.ppc from fedora-extras-development-ppc unresolved deps: libttf.so.2 package: gtkhtml36 - 3.6.2-5.fc6.ppc from fedora-extras-development-ppc unresolved deps: libgailutil.so.17 ====================================================================== New report for: byte AT fedoraproject.org package: gaim-guifications - 2.12-3.fc5.i386 from fedora-extras-development-i386 unresolved deps: gaim < 1:2 package: gaim-guifications - 2.12-3.fc5.x86_64 from fedora-extras-development-x86_64 unresolved deps: gaim < 1:2 package: gaim-guifications - 2.12-3.fc5.ppc from fedora-extras-development-ppc unresolved deps: gaim < 1:2 ====================================================================== New report for: fedora AT leemhuis.info package: gsynaptics - 0.9.8-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: synaptics ====================================================================== New report for: pertusus AT free.fr package: paw - 2005-21.fc6.ppc from fedora-extras-development-ppc unresolved deps: libg2c.so.0 package: cernlib-packlib - 2005-21.fc6.ppc from fedora-extras-development-ppc unresolved deps: libg2c.so.0 package: cernlib - 2005-21.fc6.ppc from fedora-extras-development-ppc unresolved deps: libg2c.so.0 package: patchy - 2005-21.fc6.ppc from fedora-extras-development-ppc unresolved deps: libg2c.so.0 ====================================================================== New report for: caillon AT redhat.com package: banshee - 0.10.8-1.i386 from fedora-extras-development-i386 unresolved deps: libnautilus-burn.so.3 libdbus-1.so.2 package: banshee - 0.10.8-1.x86_64 from fedora-extras-development-x86_64 unresolved deps: libnautilus-burn.so.3()(64bit) libdbus-1.so.2()(64bit) package: banshee - 0.10.8-1.ppc from fedora-extras-development-ppc unresolved deps: libnautilus-burn.so.3 libdbus-1.so.2 ====================================================================== New report for: thomas AT apestaart.org package: directfb - 0.9.24-5.fc5.i386 from fedora-extras-development-i386 unresolved deps: libsysfs.so.1 package: directfb - 0.9.24-5.fc5.x86_64 from fedora-extras-development-x86_64 unresolved deps: libsysfs.so.1()(64bit) package: directfb - 0.9.24-5.fc5.ppc from fedora-extras-development-ppc unresolved deps: libsysfs.so.1 ====================================================================== New report for: rolandd AT cisco.com package: libibverbs-utils - 1.0.3-1.fc6.i386 from fedora-extras-development-i386 unresolved deps: libsysfs.so.1 package: libibverbs - 1.0.3-1.fc6.i386 from fedora-extras-development-i386 unresolved deps: libsysfs.so.1 package: libibverbs-utils - 1.0.3-1.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libsysfs.so.1()(64bit) package: libibverbs - 1.0.3-1.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libsysfs.so.1()(64bit) package: libibverbs - 1.0.3-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: libsysfs.so.1 package: libibverbs-utils - 1.0.3-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: libsysfs.so.1 ====================================================================== New report for: ivazquez AT ivazquez.net package: gnome-applet-music - 0.9.0-1.fc6.i386 from fedora-extras-development-i386 unresolved deps: libgailutil.so.17 libdbus-1.so.2 package: nautilus-search-tool - 0.2-1.fc5.i386 from fedora-extras-development-i386 unresolved deps: libgailutil.so.17 package: gnome-applet-music - 0.9.0-1.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libgailutil.so.17()(64bit) libdbus-1.so.2()(64bit) package: nautilus-search-tool - 0.2-1.fc5.x86_64 from fedora-extras-development-x86_64 unresolved deps: libgailutil.so.17()(64bit) package: gnome-applet-music - 0.9.0-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: libgailutil.so.17 libdbus-1.so.2 package: nautilus-search-tool - 0.2-1.fc5.ppc from fedora-extras-development-ppc unresolved deps: libgailutil.so.17 ====================================================================== New report for: matthias AT rpmforge.net package: diradmin - 1.7.1-4.fc5.i386 from fedora-extras-development-i386 unresolved deps: libgnomesupport.so.0 libart_lgpl.so.2 libgnome.so.32 libgnomeui.so.32 package: gtktalog - 1.0.4-7.fc5.i386 from fedora-extras-development-i386 unresolved deps: libart_lgpl.so.2 gnome-libs >= 0:1.2 libgnomesupport.so.0 libgnome.so.32 libgnomeui.so.32 package: gtktalog - 1.0.4-7.fc5.x86_64 from fedora-extras-development-x86_64 unresolved deps: libgnomesupport.so.0()(64bit) gnome-libs >= 0:1.2 libart_lgpl.so.2()(64bit) libgnome.so.32()(64bit) libgnomeui.so.32()(64bit) package: diradmin - 1.7.1-4.fc5.x86_64 from fedora-extras-development-x86_64 unresolved deps: libgnomesupport.so.0()(64bit) libart_lgpl.so.2()(64bit) libgnome.so.32()(64bit) libgnomeui.so.32()(64bit) package: diradmin - 1.7.1-4.fc5.ppc from fedora-extras-development-ppc unresolved deps: libgnomesupport.so.0 libart_lgpl.so.2 libgnome.so.32 libgnomeui.so.32 package: gtktalog - 1.0.4-7.fc5.ppc from fedora-extras-development-ppc unresolved deps: libart_lgpl.so.2 gnome-libs >= 0:1.2 libgnomesupport.so.0 libgnome.so.32 libgnomeui.so.32 From mailinglists at erwinrol.com Wed Aug 2 21:19:26 2006 From: mailinglists at erwinrol.com (Erwin Rol) Date: Wed, 02 Aug 2006 23:19:26 +0200 Subject: Cross-compilers. In-Reply-To: <44D1093B.5090100@redhat.com> References: <1153656919.29989.74.camel@shinybook.infradead.org> <44D1093B.5090100@redhat.com> Message-ID: <1154553566.2760.22.camel@xpc.home.erwinrol.com> On Wed, 2006-08-02 at 15:21 -0500, Clark Williams wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > - From the responses you got, I'd say there's a fair amount of interest. > > What do you think about starting small (e.g. generating a mesh of FC x > FC compilers)? Starting with an FC target would mean that we could use > packages we know already work in the Fedora framework. It would just > be a matter of making a specfile (or series of specfiles) that are > cross-friendly to build and package gcc, binutils, glibc and gdb. > I've done that a few times and while it's not exactly pretty, it's > doable. We could generate x86, x86_64, and PPC hosted toolchains for > x86, x86_64 and PPC and then be able to build say PPC packages from an > x86_64 (the immediate benefactor would probably be the build system). > Of course after getting the toolchains packaged, it's a matter of > asking the maintainers to keep their specfiles cross friendly, but if > they'll take patches, we can clean that up. It is way more than just keeping their specfiles cross friendly. Most larger projects, like Xorg, are a bitch to crosscompile, and almost all need a lot of tuning before even './configure' works. The ones without configure will probably even more work to get obscure Makefiles to do cross compiling. The cross compiler part is less than 0.1% of the problem. - Erwin From buildsys at fedoraproject.org Wed Aug 2 21:57:39 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Wed, 2 Aug 2006 17:57:39 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-02 Message-ID: <20060802215739.A1717152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 3 gallery2-2.1-0.23.svn20060524.fc5 xboard-4.2.7-12.fc5.1 zope-2.9.3-4.fc5 Packages built and released for Fedora Extras 4: 2 gallery2-2.1-0.23.svn20060524.fc4 zope-2.8.3-5.fc4 Packages built and released for Fedora Extras 3: 1 zope-2.8.0-4.fc3 Packages built and released for Fedora Extras development: 3 gallery2-2.1-0.23.svn20060524.fc6 xboard-4.2.7-14.fc6 zope-2.9.3-4.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Wed Aug 2 21:58:11 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Wed, 2 Aug 2006 17:58:11 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-02 Message-ID: <20060802215811.474D6152169@buildsys.fedoraproject.org> azureus: green AT redhat.com 5: 0:2.4.0.3-0.20060529cvs_1.fc5 (FE5) 6: 0:2.4.0.3-0.20060328cvs_5.fc6 (FE6) banshee: caillon AT redhat.com 5: 0:0.10.9-1..fc5 (FE5) 6: 0:0.10.8-1 (FE6) cairomm: rvinyard AT cs.nmsu.edu 5: 0:0.6.0-2.fc5 (FE5) 6: 0:0.6.0-1.fc6 (FE6) camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) digikam: mgarski AT post.pl 3: 0:0.8.2-2.fc3 (FE3) 4: 0:0.8.2-1.fc4 (FE4) 5: 0:0.8.2-1.fc5 (FE5) 6: 0:0.8.2-1.fc6 (FE6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) dogtail: zcerza AT redhat.com 5: 0:0.5.2-2.fc5 (FE5) 6: 0:0.5.2-1.fc6 (FC6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: oliver AT linux-kernel.at 4: 0:1.14.0-1.fc4 (FE4) 5: 0:1.12.0-1.fc5 (FE5) 6: 0:1.12.0-1.fc5 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gaim-gaym: cweyl AT alumni.drew.edu 5: 0:0.96-3.fc5 (FE5) 6: 0:0.96-2.fc6 (FE6) gauche-gl: gemi AT bluewin.ch 5: 0:0.4.1-5.fc5 (FE5) 6: 0:0.4.1-4.fc6 (FE6) gcdmaster: denis AT poolshark.org 4: 0:1.2.1-5.fc4 (FE4) 5: 0:1.2.1-4.fc5 (FE5) 6: 0:1.2.1-4.fc5 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) gtksourceview-sharp: paul AT all-the-johnsons.co.uk 5: 0:2.0-15.fc5 (FE5) 6: 0:2.0-14.fc6 (FE6) icon-naming-utils: 5: 0:0.7.3-1.fc5 (FC5-updates) 6: 0:0.7.3-1 (FC6) inkscape: denis AT poolshark.org 4: 0:0.44-3.fc4 (FE4) 5: 0:0.44-2.fc5 (FE5) 6: 0:0.44-2.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) libnasl: andreas.bierfert AT lowlatency.de 5: 0:2.2.8-1.fc5 (FE5) 6: 0:2.2.7-1.fc6 (FE6) libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) lvm2: 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-16.fc6 (FC6) mozilla: 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) nfs-utils: 5: 1:1.0.8-2.fc5 (FC5-updates) 6: 0:1.0.9-2.fc6 (FC6) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-1.FC6.1 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.1-2.fc5 (FE5) 6: 0:1.0.1-1.fc5 (FE6) quagga: 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-anthy: tagoh AT redhat.com 5: 0:1.2.0-1.fc5.1 (FC5-updates) 6: 0:1.0.0-4.fc6 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5 (FE5) 6: 0:0.2.0-4.fc6 (FE6) scons: gemi AT bluewin.ch 5: 0:0.96.1-2.fc5 (FE5) 6: 0:0.96.1-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) smart: Axel.Thimm AT ATrpms.net 5: 0:0.42-34.fc5 (FE5) 6: 0:0.41-31.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.4-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) wine-docs: andreas.bierfert AT lowlatency.de 3: 0:0.9.17-1.fc3 (FE3) 4: 0:0.9.17-0.1.fc4 (FE4) 5: 0:0.9.17-1.fc5 (FE5) 6: 0:0.9.17-1.fc6 (FE6) xorg-x11-drv-nv: 5: 0:1.2.0-3.fc5 (FC5-updates) 6: 0:1.2.0-2.fc6 (FC6) From gajownik at gmail.com Wed Aug 2 22:11:00 2006 From: gajownik at gmail.com (Dawid Gajownik) Date: Thu, 03 Aug 2006 00:11:00 +0200 Subject: %lang macro does not work with %doc? In-Reply-To: <20060802195728.61300.qmail@web34102.mail.mud.yahoo.com> References: <20060802195728.61300.qmail@web34102.mail.mud.yahoo.com> Message-ID: <44D122F4.6060801@gmail.com> Dnia 08/02/2006 09:58 PM, U?ytkownik djspary napisa?: > thanks for the addvice Actually, it's not an advice but question about packaging issue ;-) If I use %lang(pl) without %doc everything works correct (files are not being installed). I don't know how to workaround this problem :/ Regards, Dawid -- ^_* From buildsys at fedoraproject.org Wed Aug 2 22:17:29 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Wed, 02 Aug 2006 22:17:29 -0000 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-02 Message-ID: <20060802221729.21777.88632@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (118 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (118 days) wine-core - 0.9.17-1.fc6.i386 (7 days) byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (14 days) gaim-guifications - 2.12-3.fc5.ppc (14 days) gaim-guifications - 2.12-3.fc5.x86_64 (14 days) caillon AT redhat.com banshee - 0.10.8-1.i386 (14 days) banshee - 0.10.8-1.ppc (14 days) banshee - 0.10.8-1.x86_64 (14 days) libipoddevice - 0.4.5-1.fc6.i386 (13 days) libipoddevice - 0.4.5-1.fc6.ppc (13 days) libipoddevice - 0.4.5-1.fc6.x86_64 (13 days) cweyl AT alumni.drew.edu gaim-gaym - 0.96-2.fc6.i386 (14 days) gaim-gaym - 0.96-2.fc6.ppc (14 days) gaim-gaym - 0.96-2.fc6.x86_64 (14 days) dennis AT ausil.us knetworkmanager - 0.1-0.3.svn20060625.fc6.i386 (13 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.ppc (13 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.x86_64 (13 days) fedora AT leemhuis.info gsynaptics - 0.9.8-1.fc6.ppc (14 days) frank-buettner AT gmx.net qt4-qsa - 1.2.1-13.fc6.i386 qt4-qsa - 1.2.1-13.fc6.ppc qt4-qsa - 1.2.1-13.fc6.x86_64 gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (6 days) amarok - 1.4.1-3.fc6.ppc (6 days) green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.i386 (7 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (7 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.x86_64 (7 days) jogl - 1.1.1-14.fc5.ppc (10 days) ivazquez AT ivazquez.net gnome-applet-music - 0.9.0-1.fc6.i386 (14 days) gnome-applet-music - 0.9.0-1.fc6.ppc (14 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (14 days) nautilus-search-tool - 0.2-1.fc5.i386 (14 days) nautilus-search-tool - 0.2-1.fc5.ppc (14 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (14 days) lmacken AT redhat.com python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.i386 (18 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.ppc (18 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.x86_64 (18 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.i386 (18 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.ppc (18 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.x86_64 (18 days) matthias AT rpmforge.net diradmin - 1.7.1-4.fc5.i386 (14 days) diradmin - 1.7.1-4.fc5.ppc (14 days) diradmin - 1.7.1-4.fc5.x86_64 (14 days) gtktalog - 1.0.4-7.fc5.i386 (14 days) gtktalog - 1.0.4-7.fc5.ppc (14 days) gtktalog - 1.0.4-7.fc5.x86_64 (14 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (14 days) gfontview - 0.5.0-5.fc5.ppc (14 days) gfontview - 0.5.0-5.fc5.x86_64 (14 days) gtkhtml36 - 3.6.2-5.fc6.i386 (14 days) gtkhtml36 - 3.6.2-5.fc6.ppc (14 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (14 days) libvisual-plugins - 0.2.0-3.fc5.i386 (14 days) libvisual-plugins - 0.2.0-3.fc5.i386 (14 days) libvisual-plugins - 0.2.0-3.fc5.ppc (14 days) libvisual-plugins - 0.2.0-3.fc5.ppc (14 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (14 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (14 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (77 days) syck-php - 0.55-7.fc5.i386 (77 days) syck-php - 0.55-7.fc5.ppc (77 days) syck-php - 0.55-7.fc5.ppc (77 days) syck-php - 0.55-7.fc5.x86_64 (77 days) syck-php - 0.55-7.fc5.x86_64 (77 days) pertusus AT free.fr cernlib - 2005-21.fc6.ppc (14 days) cernlib-packlib - 2005-21.fc6.ppc (14 days) dap-hdf4_handler - 3.6.0-3.fc5.i386 (10 days) dap-hdf4_handler - 3.6.0-3.fc5.ppc (10 days) dap-hdf4_handler - 3.6.0-3.fc5.x86_64 (10 days) patchy - 2005-21.fc6.ppc (14 days) paw - 2005-21.fc6.ppc (14 days) petersen AT redhat.com scim-bridge - 0.1.12-1.fc5.i386 scim-bridge - 0.1.12-1.fc5.ppc scim-bridge - 0.1.12-1.fc5.x86_64 qshen AT redhat.com scim-fcitx-tools - 3.1.1-4.1.fc5.i386 scim-fcitx-tools - 3.1.1-4.1.fc5.ppc scim-fcitx-tools - 3.1.1-4.1.fc5.x86_64 rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (14 days) libibverbs - 1.0.3-1.fc6.ppc (14 days) libibverbs - 1.0.3-1.fc6.x86_64 (14 days) libibverbs-utils - 1.0.3-1.fc6.i386 (14 days) libibverbs-utils - 1.0.3-1.fc6.ppc (14 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (14 days) thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (14 days) directfb - 0.9.24-5.fc5.ppc (14 days) directfb - 0.9.24-5.fc5.x86_64 (14 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.i386 requires python-protocols >= 0:1.0 scim-bridge-0.1.12-1.fc5.i386 requires libstdc++-20060428.so.7 scim-bridge-0.1.12-1.fc5.i386 requires libstdc++-20060428.so.7(CXXABI_1.4) scim-bridge-0.1.12-1.fc5.i386 requires libstdc++-20060428.so.7(GLIBCXX_4.2) scim-fcitx-tools-3.1.1-4.1.fc5.i386 requires libstdc++-20060428.so.7 scim-fcitx-tools-3.1.1-4.1.fc5.i386 requires libstdc++-20060428.so.7(GLIBCXX_4.2) scim-fcitx-tools-3.1.1-4.1.fc5.i386 requires libstdc++-20060428.so.7(CXXABI_1.4) syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) python-ruledispatch-0.5a0-0.1.svnr2115.fc5.x86_64 requires python-protocols >= 0:1.0 scim-bridge-0.1.12-1.fc5.x86_64 requires libstdc++-20060428.so.7(CXXABI_1.4)(64bit) scim-bridge-0.1.12-1.fc5.x86_64 requires libstdc++-20060428.so.7()(64bit) scim-bridge-0.1.12-1.fc5.x86_64 requires libstdc++-20060428.so.7(GLIBCXX_4.2)(64bit) scim-fcitx-tools-3.1.1-4.1.fc5.x86_64 requires libstdc++-20060428.so.7(CXXABI_1.4)(64bit) scim-fcitx-tools-3.1.1-4.1.fc5.x86_64 requires libstdc++-20060428.so.7()(64bit) scim-fcitx-tools-3.1.1-4.1.fc5.x86_64 requires libstdc++-20060428.so.7(GLIBCXX_4.2)(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.ppc requires python-protocols >= 0:1.0 scim-bridge-0.1.12-1.fc5.ppc requires libstdc++-20060428.so.7 scim-bridge-0.1.12-1.fc5.ppc requires libstdc++-20060428.so.7(CXXABI_1.4) scim-bridge-0.1.12-1.fc5.ppc requires libstdc++-20060428.so.7(GLIBCXX_4.2) scim-fcitx-tools-3.1.1-4.1.fc5.ppc requires libstdc++-20060428.so.7 scim-fcitx-tools-3.1.1-4.1.fc5.ppc requires libstdc++-20060428.so.7(GLIBCXX_4.2) scim-fcitx-tools-3.1.1-4.1.fc5.ppc requires libstdc++-20060428.so.7(CXXABI_1.4) syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.i386 requires python-protocols >= 0:1.0 Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.x86_64 requires python-protocols >= 0:1.0 Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.ppc requires python-protocols >= 0:1.0 Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.i386 requires libgcj.so.7 banshee-0.10.8-1.i386 requires libnautilus-burn.so.3 banshee-0.10.8-1.i386 requires libdbus-1.so.2 dap-hdf4_handler-3.6.0-3.fc5.i386 requires libdap.so.4 diradmin-1.7.1-4.fc5.i386 requires libgnomesupport.so.0 diradmin-1.7.1-4.fc5.i386 requires libart_lgpl.so.2 diradmin-1.7.1-4.fc5.i386 requires libgnome.so.32 diradmin-1.7.1-4.fc5.i386 requires libgnomeui.so.32 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.i386 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 gtktalog-1.0.4-7.fc5.i386 requires libart_lgpl.so.2 gtktalog-1.0.4-7.fc5.i386 requires gnome-libs >= 0:1.2 gtktalog-1.0.4-7.fc5.i386 requires libgnomesupport.so.0 gtktalog-1.0.4-7.fc5.i386 requires libgnome.so.32 gtktalog-1.0.4-7.fc5.i386 requires libgnomeui.so.32 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-qt-1.so.1 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libipoddevice-0.4.5-1.fc6.i386 requires libdbus-1.so.2 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 qt4-qsa-1.2.1-13.fc6.i386 requires qt4 < 0:4.2 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- azureus-2.4.0.3-0.20060328cvs_5.fc6.x86_64 requires libgcj.so.7()(64bit) banshee-0.10.8-1.x86_64 requires libnautilus-burn.so.3()(64bit) banshee-0.10.8-1.x86_64 requires libdbus-1.so.2()(64bit) dap-hdf4_handler-3.6.0-3.fc5.x86_64 requires libdap.so.4()(64bit) diradmin-1.7.1-4.fc5.x86_64 requires libgnomesupport.so.0()(64bit) diradmin-1.7.1-4.fc5.x86_64 requires libart_lgpl.so.2()(64bit) diradmin-1.7.1-4.fc5.x86_64 requires libgnome.so.32()(64bit) diradmin-1.7.1-4.fc5.x86_64 requires libgnomeui.so.32()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-gaym-0.96-2.fc6.x86_64 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) gtktalog-1.0.4-7.fc5.x86_64 requires libgnomesupport.so.0()(64bit) gtktalog-1.0.4-7.fc5.x86_64 requires gnome-libs >= 0:1.2 gtktalog-1.0.4-7.fc5.x86_64 requires libart_lgpl.so.2()(64bit) gtktalog-1.0.4-7.fc5.x86_64 requires libgnome.so.32()(64bit) gtktalog-1.0.4-7.fc5.x86_64 requires libgnomeui.so.32()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-qt-1.so.1()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-1.so.2()(64bit) libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libipoddevice-0.4.5-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) qt4-qsa-1.2.1-13.fc6.x86_64 requires qt4 < 0:4.2 syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.17-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 banshee-0.10.8-1.ppc requires libnautilus-burn.so.3 banshee-0.10.8-1.ppc requires libdbus-1.so.2 cernlib-2005-21.fc6.ppc requires libg2c.so.0 cernlib-packlib-2005-21.fc6.ppc requires libg2c.so.0 dap-hdf4_handler-3.6.0-3.fc5.ppc requires libdap.so.4 diradmin-1.7.1-4.fc5.ppc requires libgnomesupport.so.0 diradmin-1.7.1-4.fc5.ppc requires libart_lgpl.so.2 diradmin-1.7.1-4.fc5.ppc requires libgnome.so.32 diradmin-1.7.1-4.fc5.ppc requires libgnomeui.so.32 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.ppc requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gsynaptics-0.9.8-1.fc6.ppc requires synaptics gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 gtktalog-1.0.4-7.fc5.ppc requires libart_lgpl.so.2 gtktalog-1.0.4-7.fc5.ppc requires gnome-libs >= 0:1.2 gtktalog-1.0.4-7.fc5.ppc requires libgnomesupport.so.0 gtktalog-1.0.4-7.fc5.ppc requires libgnome.so.32 gtktalog-1.0.4-7.fc5.ppc requires libgnomeui.so.32 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-qt-1.so.1 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libipoddevice-0.4.5-1.fc6.ppc requires libdbus-1.so.2 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 patchy-2005-21.fc6.ppc requires libg2c.so.0 paw-2005-21.fc6.ppc requires libg2c.so.0 qt4-qsa-1.2.1-13.fc6.ppc requires qt4 < 0:4.2 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 From Axel.Thimm at ATrpms.net Wed Aug 2 22:27:08 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Thu, 3 Aug 2006 00:27:08 +0200 Subject: Cross-compilers. In-Reply-To: <1153656919.29989.74.camel@shinybook.infradead.org> References: <1153656919.29989.74.camel@shinybook.infradead.org> Message-ID: <20060802222708.GC14474@neu.nirvana> On Sun, Jul 23, 2006 at 08:15:18AM -0400, David Woodhouse wrote: > How much interest would there be in getting a bunch of cross-compilers > into Extras? A very good idea. > It'd be particularly nice if we could install native -devel packages > into each toolchain's sysroot I don't think installing packages of a foreign arch is easy w/o an emulator. You have scriptlets (%post and friends) that need to run on the target arch's platform. E.g. even installing glibc calls /usr/sbin/glibc_post_upgrade.* which would have to be emulated. -devel usually has no scriplets, but the pulled in main lib package will at the very least want to call ldconfig. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Axel.Thimm at ATrpms.net Wed Aug 2 22:45:41 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Thu, 3 Aug 2006 00:45:41 +0200 Subject: Cross-compilers. In-Reply-To: <44D12870.50608@redhat.com> References: <1153656919.29989.74.camel@shinybook.infradead.org> <20060802222708.GC14474@neu.nirvana> <44D12870.50608@redhat.com> Message-ID: <20060802224541.GD14474@neu.nirvana> On Wed, Aug 02, 2006 at 05:34:24PM -0500, Clark Williams wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Axel Thimm wrote: > > On Sun, Jul 23, 2006 at 08:15:18AM -0400, David Woodhouse wrote: > >> How much interest would there be in getting a bunch of cross-compilers > >> into Extras? > > > > A very good idea. > > > >> It'd be particularly nice if we could install native -devel packages > >> into each toolchain's sysroot > > > > I don't think installing packages of a foreign arch is easy w/o an > > emulator. You have scriptlets (%post and friends) that need to run on > > the target arch's platform. E.g. even installing glibc calls > > /usr/sbin/glibc_post_upgrade.* which would have to be emulated. > > > > -devel usually has no scriplets, but the pulled in main lib package > > will at the very least want to call ldconfig. > > Well, it really depends on what you're doing in the scriptlet. If it's > running chkconfig, adduser, etc. (i.e. updating configuration > information) then something we've done in the past would work (it's > ugly, but it works). Essentially you work in a chroot and at the point > where you want to run the scriptlets, you bind mount the host /bin, > /sbin, /lib, /usr/lib, /usr/bin, and /usr/sbin into the chroot (from > outside the chroot of course), then run the scriptlets inside the > chroot natively, then undo it (Hey! I *said* it was ugly). I've used > this method to build mipsel and sh root filesystems. Yes, I've done similar things to create an embedded ppc chroot, but the pain is big and each package to be imported needs to be examined and handled specially. Mostly because some packages install stuff of the target arch in /bin and friends and you need to replace them with cross-built tools during the package installation, e.g. intercept the package installation between cpio unpacking and scriplets. You can do that for a couple of packages (like for an embedded system), but it doesn't really scale well. :( -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From rvinyard at cs.nmsu.edu Wed Aug 2 23:18:30 2006 From: rvinyard at cs.nmsu.edu (Rick L Vinyard Jr) Date: Wed, 02 Aug 2006 17:18:30 -0600 Subject: Cross-compilers. In-Reply-To: <20060802222708.GC14474@neu.nirvana> References: <1153656919.29989.74.camel@shinybook.infradead.org> <20060802222708.GC14474@neu.nirvana> Message-ID: <44D132C6.6060200@cs.nmsu.edu> Axel Thimm wrote: > On Sun, Jul 23, 2006 at 08:15:18AM -0400, David Woodhouse wrote: > >> How much interest would there be in getting a bunch of cross-compilers >> into Extras? >> > > A very good idea. > It would be very cool to see something like these in FE: http://packages.debian.org/stable/devel/binutils-m68hc1x http://packages.debian.org/testing/devel/gcc-m68hc1x http://packages.debian.org/stable/devel/gdb-m68hc1x From dwmw2 at infradead.org Thu Aug 3 01:30:34 2006 From: dwmw2 at infradead.org (David Woodhouse) Date: Thu, 03 Aug 2006 09:30:34 +0800 Subject: Cross-compilers. In-Reply-To: <44D1093B.5090100@redhat.com> References: <1153656919.29989.74.camel@shinybook.infradead.org> <44D1093B.5090100@redhat.com> Message-ID: <1154568634.19590.41.camel@shinybook.infradead.org> On Wed, 2006-08-02 at 15:21 -0500, Clark Williams wrote: > We could generate x86, x86_64, and PPC hosted toolchains for > x86, x86_64 and PPC and then be able to build say PPC packages from an > x86_64 (the immediate benefactor would probably be the build system). Cross-compilation of packages is never going to work reliably. Too many people make the mistake of using autocrap, and don't handle cross-compilation at all well. -- dwmw2 From rc040203 at freenet.de Thu Aug 3 02:03:42 2006 From: rc040203 at freenet.de (Ralf Corsepius) Date: Thu, 03 Aug 2006 04:03:42 +0200 Subject: Cross-compilers. In-Reply-To: <1154568634.19590.41.camel@shinybook.infradead.org> References: <1153656919.29989.74.camel@shinybook.infradead.org> <44D1093B.5090100@redhat.com> <1154568634.19590.41.camel@shinybook.infradead.org> Message-ID: <1154570622.5253.192.camel@mccallum.corsepiu.local> On Thu, 2006-08-03 at 09:30 +0800, David Woodhouse wrote: > On Wed, 2006-08-02 at 15:21 -0500, Clark Williams wrote: > > We could generate x86, x86_64, and PPC hosted toolchains for > > x86, x86_64 and PPC and then be able to build say PPC packages from an > > x86_64 (the immediate benefactor would probably be the build system). > > Cross-compilation of packages is never going to work reliably. True. > Too many > people make the mistake of using autocrap, and don't handle > cross-compilation at all well. You are dead wrong. auto*tools do handle cross compilation very well. Many auto* based configuration work with cross-compilers OTB. Ralf From paul at city-fan.org Thu Aug 3 08:12:19 2006 From: paul at city-fan.org (Paul Howarth) Date: Thu, 03 Aug 2006 09:12:19 +0100 Subject: %lang macro does not work with %doc? In-Reply-To: <44D0F9E4.4060108@gmail.com> References: <44D0F9E4.4060108@gmail.com> Message-ID: <1154592739.2996.18.camel@laurel.intra.city-fan.org> On Wed, 2006-08-02 at 21:15 +0200, Dawid Gajownik wrote: > Hi! > > I wanted to help reviewing libgadu (#200348). In this package > documentation is written in Polish. It's not a problem for me and other > folks from Poland but others will find it useless ;-) > > I put this into /root/.rpmmacros > > %_install_langs en:en_US:C > > and changed libgadu.spec to include this lines > > %doc lib/COPYING > %lang(pl) %doc docs/{README,TODO} ChangeLog > > Unfortunately, it does not work - files README, TODO and ChangeLog > should not be installed but they are. Have I missed something? I don't know but did you try it with %doc and %lang the other way around? %doc %lang(pl) docs/{README,TODO} ChangeLog Paul. From giallu at gmail.com Thu Aug 3 08:26:28 2006 From: giallu at gmail.com (Gianluca Sforna) Date: Thu, 3 Aug 2006 10:26:28 +0200 Subject: Cross-compilers. In-Reply-To: <1154570622.5253.192.camel@mccallum.corsepiu.local> References: <1153656919.29989.74.camel@shinybook.infradead.org> <44D1093B.5090100@redhat.com> <1154568634.19590.41.camel@shinybook.infradead.org> <1154570622.5253.192.camel@mccallum.corsepiu.local> Message-ID: On 8/3/06, Ralf Corsepius wrote: > > Too many > > people make the mistake of using autocrap, and don't handle > > cross-compilation at all well. > You are dead wrong. auto*tools do handle cross compilation very well. > Many auto* based configuration work with cross-compilers OTB. If done properly, I am sure it does. SQLite does not fall into the category though... From Christian.Iseli at licr.org Thu Aug 3 09:30:42 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Thu, 3 Aug 2006 11:30:42 +0200 Subject: Stalled review policy proposal In-Reply-To: <7dd7ab490607312124s459a8dc2t8d12ada2020cccb5@mail.gmail.com> References: <7dd7ab490607312124s459a8dc2t8d12ada2020cccb5@mail.gmail.com> Message-ID: <20060803113042.5a4eec34@ludwig-alpha> On Sat, 29 Jul 2006 13:08:55 -0500, Jason L Tibbitts III (JLT) wrote: JLT> As discussed at the recent FESCo meeting, I've drawn up a quick policy JLT> for dealing with stalled reviews. It's not intended to be JLT> comprehensive; the idea is to address two main issues that have been JLT> causing problems in the review process: unresponsive reviewers and JLT> unresponsive package submitters. I like it. On Mon, 31 Jul 2006 21:24:58 -0700, Chris Weyl (CW) wrote: CW> Would it be possible to, say, close it with a keyword, or have it CW> blocking something like "FE-DEADREVIEW"? That way it'd be much easier CW> to find if someone wants to give the package another shot. (Or if CW> people want to generate statistics, etc, etc...) I like this too. Christian From Christian.Iseli at licr.org Thu Aug 3 09:36:07 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Thu, 3 Aug 2006 11:36:07 +0200 Subject: FESCo Meeting Minutes 2006-07-27 In-Reply-To: <1154210645.5101.5.camel@T7.Linux> References: <1154157077.4720.6.camel@localhost> <1154210645.5101.5.camel@T7.Linux> Message-ID: <20060803113607.50903290@ludwig-alpha> On Sat, 29 Jul 2006 23:04:05 +0100, Paul (P) wrote: P> The shape of said bridge is a called a nodoid. Hey, thanks for the info. Learned something new today :-) BTW, you sign most (all ?) your messages, but I don't know where to find your public key... Any hint there ? Cheers, Christian From mr.ecik at gmail.com Thu Aug 3 10:40:24 2006 From: mr.ecik at gmail.com (=?ISO-8859-2?Q?Micha=B3_Bentkowski?=) Date: Thu, 3 Aug 2006 12:40:24 +0200 Subject: %lang macro does not work with %doc? In-Reply-To: <44D122F4.6060801@gmail.com> References: <20060802195728.61300.qmail@web34102.mail.mud.yahoo.com> <44D122F4.6060801@gmail.com> Message-ID: <668bb39a0608030340r42216b9cwf178cb04b72bd568@mail.gmail.com> 2006/8/3, Dawid Gajownik : > Actually, it's not an advice but question about packaging issue ;-) If I > use %lang(pl) without %doc everything works correct (files are not being > installed). I don't know how to workaround this problem :/ > Well, I found something like that on PLD forums (http://lists.pld-linux.org/mailman/pipermail/pld-devel-pl/2001-January/002001.html - only for Polish speaking folks) and it looks like RPM doesn't provide such option. PLD developers simply copied doc files to %{_docdir}/%{name}-%{version} and then added %lang(pl) macro to that files; they didn't use %doc macro. For example: http://cvs.pld.org.pl/SPECS/konwert.spec?rev=1.14 Regards. Micha?. From enrico.scholz at informatik.tu-chemnitz.de Thu Aug 3 11:55:25 2006 From: enrico.scholz at informatik.tu-chemnitz.de (Enrico Scholz) Date: Thu, 03 Aug 2006 13:55:25 +0200 Subject: FC-4 buildsystem broken; does not strip binaries Message-ID: <87hd0ujaoi.fsf@kosh.bigo.ensc.de> Hello, the FC-4 buildsystem seems to broken. It fails to strip binaries due to | /usr/lib/rpm/find-debuginfo.sh: line 31: eu-strip: command not found Enrico -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 480 bytes Desc: not available URL: From bugzilla at redhat.com Thu Aug 3 12:39:10 2006 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 3 Aug 2006 08:39:10 -0400 Subject: [Bug 179852] FC4 buildsys fails - FC4 mock succeeds - wine-docs package In-Reply-To: Message-ID: <200608031239.k73CdAK4005189@bugzilla.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: FC4 buildsys fails - FC4 mock succeeds - wine-docs package https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179852 ------- Additional Comments From andreas.bierfert at lowlatency.de 2006-08-03 08:29 EST ------- Still the same with 0.9.18: http://buildsys.fedoraproject.org/build-status/job.psp?uid=13672 -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. From paul at city-fan.org Thu Aug 3 13:06:08 2006 From: paul at city-fan.org (Paul Howarth) Date: Thu, 03 Aug 2006 14:06:08 +0100 Subject: FC-4 buildsystem broken; does not strip binaries In-Reply-To: <87hd0ujaoi.fsf@kosh.bigo.ensc.de> References: <87hd0ujaoi.fsf@kosh.bigo.ensc.de> Message-ID: <1154610369.2996.40.camel@laurel.intra.city-fan.org> On Thu, 2006-08-03 at 13:55 +0200, Enrico Scholz wrote: > Hello, > > the FC-4 buildsystem seems to broken. It fails to strip binaries due to > > | /usr/lib/rpm/find-debuginfo.sh: line 31: eu-strip: command not found This is due to the switch to the new version of mock, with the reduced buildroot, for the Extras buildsystem. The problem has been known about for quite some time and I'm surprised that it was rolled out to the buildsystem before being fixed: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=196930 Paul. From tibbs at math.uh.edu Thu Aug 3 14:50:15 2006 From: tibbs at math.uh.edu (Jason L Tibbitts III) Date: Thu, 03 Aug 2006 09:50:15 -0500 Subject: Stalled review policy proposal In-Reply-To: <7dd7ab490607312124s459a8dc2t8d12ada2020cccb5@mail.gmail.com> (Chris Weyl's message of "Mon, 31 Jul 2006 21:24:58 -0700") References: <7dd7ab490607312124s459a8dc2t8d12ada2020cccb5@mail.gmail.com> Message-ID: >>>>> "CW" == Chris Weyl writes: CW> Would it be possible to, say, close it with a keyword, or have it CW> blocking something like "FE-DEADREVIEW"? That's a good idea; I've updated the draft. - J< From tibbs at math.uh.edu Thu Aug 3 14:56:52 2006 From: tibbs at math.uh.edu (Jason L Tibbitts III) Date: Thu, 03 Aug 2006 09:56:52 -0500 Subject: FC-4 buildsystem broken; does not strip binaries In-Reply-To: <1154610369.2996.40.camel@laurel.intra.city-fan.org> (Paul Howarth's message of "Thu, 03 Aug 2006 14:06:08 +0100") References: <87hd0ujaoi.fsf@kosh.bigo.ensc.de> <1154610369.2996.40.camel@laurel.intra.city-fan.org> Message-ID: >>>>> "PH" == Paul Howarth writes: PH> This is due to the switch to the new version of mock, with the PH> reduced buildroot, for the Extras buildsystem. Note that pretty much all Python packages are broken as well, because Python is no longer installed in the FC4 buildroot by default. It seems that the total dependency coverage of the minimal buildroot includes Python on FC5 and up while on FC4 it doesn't. This means that Python packages will need tweaks to the macros in the specfile template so that they return something meaningful if Python is not available. I wonder what package started depending on Python. - J< From bugs.michael at gmx.net Thu Aug 3 15:09:41 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Thu, 3 Aug 2006 17:09:41 +0200 Subject: rpms/tetex-IEEEtran/FC-4 tetex-IEEEtran.spec,1.2,1.3 In-Reply-To: <200607260331.k6Q3VCRs016831@cvs-int.fedora.redhat.com> References: <200607260331.k6Q3VCRs016831@cvs-int.fedora.redhat.com> Message-ID: <20060803170941.211ff44b.bugs.michael@gmx.net> On Tue, 25 Jul 2006 20:31:10 -0700, Rick L. Vinyard wrote: > Author: rvinyard > > Update of /cvs/extras/rpms/tetex-IEEEtran/FC-4 > In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16753 > > Modified Files: > tetex-IEEEtran.spec > Log Message: > Added lyx triggers and other cleanup > > > > Index: tetex-IEEEtran.spec > =================================================================== > RCS file: /cvs/extras/rpms/tetex-IEEEtran/FC-4/tetex-IEEEtran.spec,v > retrieving revision 1.2 > retrieving revision 1.3 > diff -u -r1.2 -r1.3 > --- tetex-IEEEtran.spec 21 Jul 2006 21:08:35 -0000 1.2 > +++ tetex-IEEEtran.spec 26 Jul 2006 03:31:10 -0000 1.3 > @@ -8,16 +8,14 @@ > %define bibpkgdoc %{_texmf}/doc/bibtex/%{texpkg} > > Name: tetex-%{texpkg} > -Version: 1.6c > -Release: 3%{?dist} > +Version: 1.6 > +Release: 4%{?dist} > Summary: Official LaTeX class for IEEE transactions journals and conferences > > Group: Applications/Publishing > License: Artistic > URL: http://www.ctan.org/tex-archive/help/Catalogue/entries/ieeetran.html > -# DANTE generates CTAN packages zipfiles on-the-fly > Source0: ftp://ftp.dante.de/tex-archive/macros/latex/contrib/IEEEtran.zip > -#Source0: IEEEtran.zip > BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) > BuildArch: noarch > > @@ -31,11 +29,6 @@ > Institute of Electrical and Electronics Engineers (IEEE) transactions > journals and conferences. > > -Lyx users: After installing this package you need to make Lyx aware of the > -IEEEtran document class. To do this start Lyx, select Tools from the main > -menu, then select Reconfigure. After the reconfiguration is complete restart > -Lyx. > - > %prep > %setup -q -n %{texpkg} > mv extras/tux.eps . > @@ -68,6 +61,17 @@ > %postun > texhash >/dev/null 2>&1 || : > > +%triggerin -- lyx > +if [ $2 -gt 1 ]; then > +cd %{_datadir}/lyx && \ > + ./configure --without-latex-config > /dev/null 2>&1 ||: > +fi > + > +%triggerun -- lyx > +if [ $2 -eq 0 ]; then > +cd %{_datadir}/lyx && \ > + ./configure --without-latex-config > /dev/null 2>&1 ||: > +fi > > %files > %defattr(-,root,root,-) > @@ -80,6 +84,12 @@ > > > %changelog > +* Tue Jul 25 2006 Rick L Vinyard Jr - 1.6-4 > +- Removed alpha character from version > +- Added lyx triggers provided by Rex Dieter > +- Removed notice for Lyx users > +- Did some minor cleanup of the sources > + > * Fri Jul 21 2006 Rick L Vinyard Jr - 1.6c-3 > - Added note to Lyx users in description > > This change does not match lyx's own configuration and creates an empty LaTex packages.lst. On the contrary, lyx %post runs "configure" including the LaTeX packages check. From gajownik at gmail.com Thu Aug 3 17:58:20 2006 From: gajownik at gmail.com (Dawid Gajownik) Date: Thu, 03 Aug 2006 19:58:20 +0200 Subject: %lang macro does not work with %doc? In-Reply-To: <1154592739.2996.18.camel@laurel.intra.city-fan.org> References: <44D0F9E4.4060108@gmail.com> <1154592739.2996.18.camel@laurel.intra.city-fan.org> Message-ID: <44D2393C.1040808@gmail.com> Dnia 08/03/2006 10:13 AM, U?ytkownik Paul Howarth napisa?: > I don't know but did you try it with %doc and %lang the other way > around? > > %doc %lang(pl) docs/{README,TODO} ChangeLog Yep, I tried that before posting. It does not work as expected :/ Regards, Dawid -- ^_* From gajownik at gmail.com Thu Aug 3 18:00:09 2006 From: gajownik at gmail.com (Dawid Gajownik) Date: Thu, 03 Aug 2006 20:00:09 +0200 Subject: %lang macro does not work with %doc? In-Reply-To: <668bb39a0608030340r42216b9cwf178cb04b72bd568@mail.gmail.com> References: <20060802195728.61300.qmail@web34102.mail.mud.yahoo.com> <44D122F4.6060801@gmail.com> <668bb39a0608030340r42216b9cwf178cb04b72bd568@mail.gmail.com> Message-ID: <44D239A9.7000301@gmail.com> Dnia 08/03/2006 12:41 PM, U?ytkownik Micha? Bentkowski napisa?: > it looks like RPM doesn't provide such option. PLD developers simply > copied doc files to %{_docdir}/%{name}-%{version} and then added > %lang(pl) macro to that files; they didn't use %doc macro. For > example: http://cvs.pld.org.pl/SPECS/konwert.spec?rev=1.14 Thanks, that works! What a pity that we have to use such a ugly hacks ;( Regards, Dawid -- ^_* From mr.ecik at gmail.com Thu Aug 3 18:10:41 2006 From: mr.ecik at gmail.com (=?ISO-8859-2?Q?Micha=B3_Bentkowski?=) Date: Thu, 3 Aug 2006 20:10:41 +0200 Subject: %lang macro does not work with %doc? In-Reply-To: <44D239A9.7000301@gmail.com> References: <20060802195728.61300.qmail@web34102.mail.mud.yahoo.com> <44D122F4.6060801@gmail.com> <668bb39a0608030340r42216b9cwf178cb04b72bd568@mail.gmail.com> <44D239A9.7000301@gmail.com> Message-ID: <668bb39a0608031110s32607b64ndc45195e8a5d0057@mail.gmail.com> 06-08-03, Dawid Gajownik napisa?(a): > Thanks, that works! What a pity that we have to use such a ugly hacks ;( Yes, right. Maybe we should submit it to a rpm related list? From gajownik at gmail.com Thu Aug 3 18:39:09 2006 From: gajownik at gmail.com (Dawid Gajownik) Date: Thu, 03 Aug 2006 20:39:09 +0200 Subject: %lang macro does not work with %doc? In-Reply-To: <668bb39a0608031110s32607b64ndc45195e8a5d0057@mail.gmail.com> References: <20060802195728.61300.qmail@web34102.mail.mud.yahoo.com> <44D122F4.6060801@gmail.com> <668bb39a0608030340r42216b9cwf178cb04b72bd568@mail.gmail.com> <44D239A9.7000301@gmail.com> <668bb39a0608031110s32607b64ndc45195e8a5d0057@mail.gmail.com> Message-ID: <44D242CD.2070501@gmail.com> Dnia 08/03/2006 08:12 PM, U?ytkownik Micha? Bentkowski napisa?: > Maybe we should submit it to a rpm related list? Uh-huh. This should be fixed upstream. Unfortunately, I'm not able to test it with the newest RPM (read: I don't have time to mess with my system). Fedora's RPM is a bit outdated and I don't want Jeff to shout at me if it's already corrected :P Regards, Dawid -- ^_* From mr.ecik at gmail.com Thu Aug 3 18:51:42 2006 From: mr.ecik at gmail.com (=?ISO-8859-2?Q?Micha=B3_Bentkowski?=) Date: Thu, 3 Aug 2006 20:51:42 +0200 Subject: %lang macro does not work with %doc? In-Reply-To: <44D242CD.2070501@gmail.com> References: <20060802195728.61300.qmail@web34102.mail.mud.yahoo.com> <44D122F4.6060801@gmail.com> <668bb39a0608030340r42216b9cwf178cb04b72bd568@mail.gmail.com> <44D239A9.7000301@gmail.com> <668bb39a0608031110s32607b64ndc45195e8a5d0057@mail.gmail.com> <44D242CD.2070501@gmail.com> Message-ID: <668bb39a0608031151p69614041nf33a7d6f09d96d4c@mail.gmail.com> 06-08-03, Dawid Gajownik napisa?(a): > Uh-huh. This should be fixed upstream. Unfortunately, I'm not able to > test it with the newest RPM (read: I don't have time to mess with my > system). Fedora's RPM is a bit outdated and I don't want Jeff to shout > at me if it's already corrected :P I don't think it is fixed upstream. PLD list posts are from 2001 and it is stll unfixed. From paul at cypherpunks.ca Thu Aug 3 19:24:24 2006 From: paul at cypherpunks.ca (Paul Wouters) Date: Thu, 3 Aug 2006 21:24:24 +0200 (CEST) Subject: mails with: Summary - Broken dependencies in Fedora Extras - 2006-08-02 In-Reply-To: <20060802203329.18048.29585@extras64.linux.duke.edu> References: <20060802203329.18048.29585@extras64.linux.duke.edu> Message-ID: On Wed, 2 Aug 2006, Fedora Extras repoclosure wrote: > Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-02 > > Summary of broken packages (by owner): With the frequency of these emails happening, I noticed I've started to ignore these myself (after all, *my* packages are never broken *cough*) Perhaps it is a better idea to have this script mail the individual package maintainers? (or generate bugzilla reports?) Paul From paul at cypherpunks.ca Thu Aug 3 19:30:06 2006 From: paul at cypherpunks.ca (Paul Wouters) Date: Thu, 3 Aug 2006 21:30:06 +0200 (CEST) Subject: devel not properly generating ./configure with autoconf? In-Reply-To: References: Message-ID: On Sat, 29 Jul 2006, Paul Wouters wrote: Following up on myself: > I am having troubles with gaim-otr on the devel branch. It seems the calls > to autoconf are not generating a configure file. As I do not have access > to an FC6test or rawhide server, it's hard for me to figure out what is > going on. > Did anyone else have similar problems with autoconf? Or does anyone have > a throwaway xenu of fc6test1 I can abuse for a day or two? No one responded with having access to an FC6, so I tried FC6test1. Whether I tried an update of FC4 or install from scratch an FC6test1 DVD, it was a bug ridden fest that caused anaconda to die in many many ways. I'm waiting for FC6 to become more stsble before trying again. Unfortunately, this means gaim-otr remains broken in devel :( Paul From wtogami at redhat.com Thu Aug 3 19:50:48 2006 From: wtogami at redhat.com (Warren Togami) Date: Thu, 03 Aug 2006 15:50:48 -0400 Subject: mails with: Summary - Broken dependencies in Fedora Extras - 2006-08-02 In-Reply-To: References: <20060802203329.18048.29585@extras64.linux.duke.edu> Message-ID: <44D25398.6090705@redhat.com> Paul Wouters wrote: > On Wed, 2 Aug 2006, Fedora Extras repoclosure wrote: > >> Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-02 >> >> Summary of broken packages (by owner): > > With the frequency of these emails happening, I noticed I've started to ignore > these myself (after all, *my* packages are never broken *cough*) > > Perhaps it is a better idea to have this script mail the individual package > maintainers? (or generate bugzilla reports?) > > Paul > Agreed, these would be more useful if it manages to annoy the people responsible... although having the list post is useful too. Unfortunately it seems that the script doesn't know who the owner is in many cases. Warren From bugs.michael at gmx.net Thu Aug 3 20:32:09 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Thu, 3 Aug 2006 22:32:09 +0200 Subject: mails with: Summary - Broken dependencies in Fedora Extras - 2006-08-02 In-Reply-To: <44D25398.6090705@redhat.com> References: <20060802203329.18048.29585@extras64.linux.duke.edu> <44D25398.6090705@redhat.com> Message-ID: <20060803223209.dcdb6d65.bugs.michael@gmx.net> On Thu, 03 Aug 2006 15:50:48 -0400, Warren Togami wrote: > Paul Wouters wrote: > > On Wed, 2 Aug 2006, Fedora Extras repoclosure wrote: > > > >> Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-02 > >> > >> Summary of broken packages (by owner): > > > > With the frequency of these emails happening, I noticed I've started to ignore > > these myself (after all, *my* packages are never broken *cough*) > > > > Perhaps it is a better idea to have this script mail the individual package > > maintainers? (or generate bugzilla reports?) > > > > Paul > > > > Agreed, these would be more useful if it manages to annoy the people > responsible... although having the list post is useful too. > > Unfortunately it seems that the script doesn't know who the owner is in > many cases. Are you kidding? :-O The script does mail the package owner. And it knows the owner of every Extras package if it is listed in CVS owners.list. And it repeats the personal mail every 14 days as long as the package remains broken. From tibbs at math.uh.edu Thu Aug 3 21:02:16 2006 From: tibbs at math.uh.edu (Jason L Tibbitts III) Date: Thu, 03 Aug 2006 16:02:16 -0500 Subject: Stalled review policy proposal In-Reply-To: (Jason L. Tibbitts, III's message of "Thu, 03 Aug 2006 09:50:15 -0500") References: <7dd7ab490607312124s459a8dc2t8d12ada2020cccb5@mail.gmail.com> Message-ID: Note that the draft was approved by FESCo today, and has moved to http://fedoraproject.org/wiki/Extras/Policy/StalledReviews - J< From ville.skytta at iki.fi Thu Aug 3 21:26:23 2006 From: ville.skytta at iki.fi (Ville =?ISO-8859-1?Q?Skytt=E4?=) Date: Fri, 04 Aug 2006 00:26:23 +0300 Subject: FC-4 buildsystem broken; does not strip binaries In-Reply-To: References: <87hd0ujaoi.fsf@kosh.bigo.ensc.de> <1154610369.2996.40.camel@laurel.intra.city-fan.org> Message-ID: <1154640383.2743.119.camel@localhost.localdomain> On Thu, 2006-08-03 at 09:56 -0500, Jason L Tibbitts III wrote: > >>>>> "PH" == Paul Howarth writes: > > PH> This is due to the switch to the new version of mock, with the > PH> reduced buildroot, for the Extras buildsystem. IMHO missing elfutils and python in the FC4 build root is a bug that should be fixed there. The exact set of packages in build roots will continue to slightly differ between releases because dependencies evolve, but my understanding is that people who approved the current baseline set of packages in Packaging/Guidelines#Exceptions for all distro versions looked at what it expands to in FC5, see Extras/FullExceptionList in Wiki. The expanded list (which contains both elfutils and python) is also referred to in the guidelines' exceptions section. > I wonder what package started depending on Python. Some SELinux things, IIRC. From rc040203 at freenet.de Fri Aug 4 04:37:02 2006 From: rc040203 at freenet.de (Ralf Corsepius) Date: Fri, 04 Aug 2006 06:37:02 +0200 Subject: devel not properly generating ./configure with autoconf? In-Reply-To: References: Message-ID: <1154666222.5253.268.camel@mccallum.corsepiu.local> On Thu, 2006-08-03 at 21:30 +0200, Paul Wouters wrote: > On Sat, 29 Jul 2006, Paul Wouters wrote: > > Following up on myself: > > > I am having troubles with gaim-otr on the devel branch. It seems the calls > > to autoconf are not generating a configure file. As I do not have access > > to an FC6test or rawhide server, it's hard for me to figure out what is > > going on. > > Did anyone else have similar problems with autoconf? Or does anyone have > > a throwaway xenu of fc6test1 I can abuse for a day or two? > > No one responded with having access to an FC6, so I tried FC6test1. It would have helped if you had posted a proper error description ;) Even on FC5, I can reproduce a series of bugs in building this package, circulating around you not correctly invoking the autotools and missing several "cd %{name} ... cd ..". However, the origin of all these bugs is you using a source tarball containing a raw cvs snapshot, instead of a properly built package tarball. To cut a proper tarball, you would have to go through the steps an upstream maintainer would have to go through: 1. Checkout a copy of gaim-otr from sourceforge 2. Inside of this checked-out copy: autoreconf -i 3. ./configure 4. make dist This will result into a tarball called gaim-otr-3.0.0.tar.gz, internally using a dirname of "gain-3.0.0", containing all the files you need (provided upstream packages their stuff correctly). 5. Then will want to rename this tarball to using a filename which doesn't conflict with a future final gaim-otr-3.0.0.tar.gz tarball in FE CVS's look-aside cache, e.g. mv gaim-otr-3.0.0 gaim-otr-3.0.0-20060804.tar.gz, 6. Reflect these changes into your spec. Having performed the steps about you should not need to run any autotools nor cd between dirs anymore. Contact me on PM, should you need further assistance or give me permission to perform the steps above directly in FE's CVS. Ralf From andy at smile.org.ua Fri Aug 4 08:19:25 2006 From: andy at smile.org.ua (Andy Shevchenko) Date: Fri, 04 Aug 2006 11:19:25 +0300 Subject: duplicate filenames in the different packages [qstat vs. torque] Message-ID: <44D3030D.1060107@smile.org.ua> Hi, folks! Tonight I've received the following bug http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201279 I'm packager of the qstat tool. But the torque (in torque-client) already consists the /usr/bin/qstat. And main question here: what should I do? -- With best regards, Andy Shevchenko. mailto: andy at smile.org.ua From paul at all-the-johnsons.co.uk Fri Aug 4 10:39:20 2006 From: paul at all-the-johnsons.co.uk (PFJ) Date: Fri, 04 Aug 2006 11:39:20 +0100 Subject: Someone poke the buildsys please Message-ID: <1154687961.5572.15.camel@localhost.localdomain> Hi, monodevelop is currently failing to build on the FE buildsys. It's giving the following error 8--> Executing /usr/sbin/mock-helper yum --installroot /var/lib/mock/fedora-development-i386-core-f653db06900991cff831a17766c2f27da84f5fc7/root install buildsys-build file:///pub/fedora/linux/core/development/i386/os/Fedora/RPMS/unzip-5.52-2.2.1.i386.rpm: [Errno -1] Header is not complete. Trying other mirror. Error: failure: Fedora/RPMS/unzip-5.52-2.2.1.i386.rpm from core: [Errno 256] No more mirrors to try. Cleaning up... Executing /usr/sbin/mock-helper umount /var/lib/mock/fedora-development-i386-core-f653db06900991cff831a17766c2f27da84f5fc7/root/proc Executing /usr/sbin/mock-helper umount /var/lib/mock/fedora-development-i386-core-f653db06900991cff831a17766c2f27da84f5fc7/root/dev/pts Done. <--8 looks like something has gone a bit wobbly! TTFN Paul -- "Logic, my dear Zoe, is merely the ability to be wrong with authority" - Dr Who From bugs.michael at gmx.net Fri Aug 4 10:48:04 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Fri, 4 Aug 2006 12:48:04 +0200 Subject: duplicate filenames in the different packages [qstat vs. torque] In-Reply-To: <44D3030D.1060107@smile.org.ua> References: <44D3030D.1060107@smile.org.ua> Message-ID: <20060804124804.b7f890ca.bugs.michael@gmx.net> On Fri, 04 Aug 2006 11:19:25 +0300, Andy Shevchenko wrote: > Hi, folks! > > Tonight I've received the following bug > http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201279 > > I'm packager of the qstat tool. But the torque (in torque-client) > already consists the /usr/bin/qstat. > > And main question here: what should I do? In general, it is always bad if packages pollute the namespace of a global search location like /usr/bin with a filename that is not related to the package name. Why isn't this program called "torque-qstat"? You could patch it and rename it like that. What is the sense in creating such a short and generic name like "qstat"? Is the program useful outside of "torque"? Could it be placed in /usr/libexec/torque/qstat instead if not renamed? Btw, I don't like the growing tendency among packagers to suggest explicit Conflicts in Fedora Extras in favour of working on making packages coexist nicely whether with the help of upstream or not. From andy at smile.org.ua Fri Aug 4 11:40:11 2006 From: andy at smile.org.ua (Andy Shevchenko) Date: Fri, 04 Aug 2006 14:40:11 +0300 Subject: duplicate filenames in the different packages [qstat vs. torque] In-Reply-To: <20060804124804.b7f890ca.bugs.michael@gmx.net> References: <44D3030D.1060107@smile.org.ua> <20060804124804.b7f890ca.bugs.michael@gmx.net> Message-ID: <44D3321B.9010502@smile.org.ua> Michael Schwendt wrote: >>Tonight I've received the following bug >>http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201279 >>I'm packager of the qstat tool. But the torque (in torque-client) >>already consists the /usr/bin/qstat. > Why isn't this program called "torque-qstat"? You could patch it and > rename it like that. What is the sense in creating such a short and > generic name like "qstat"? Is the program useful outside of "torque"? > Could it be placed in /usr/libexec/torque/qstat instead if not renamed? Thanks for opinoin, but I think some miscommunication is present here. I'm not a packager of torque. As I understand you correctly the issue inhere torque than qstat. Anyway I've filled bug to torque with references to this maillist discussion already. I'm wating for torque packager response. -- With best regards, Andy Shevchenko. mailto: andy at smile.org.ua From Axel.Thimm at ATrpms.net Fri Aug 4 13:18:30 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Fri, 4 Aug 2006 15:18:30 +0200 Subject: duplicate filenames in the different packages [qstat vs. torque] In-Reply-To: <44D3321B.9010502@smile.org.ua> References: <44D3030D.1060107@smile.org.ua> <20060804124804.b7f890ca.bugs.michael@gmx.net> <44D3321B.9010502@smile.org.ua> Message-ID: <20060804131830.GA11342@neu.nirvana> On Fri, Aug 04, 2006 at 02:40:11PM +0300, Andy Shevchenko wrote: > Michael Schwendt wrote: > >>Tonight I've received the following bug > >>http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201279 > >>I'm packager of the qstat tool. But the torque (in torque-client) > >>already consists the /usr/bin/qstat. > > >Why isn't this program called "torque-qstat"? You could patch it and > >rename it like that. What is the sense in creating such a short and > >generic name like "qstat"? Is the program useful outside of "torque"? > >Could it be placed in /usr/libexec/torque/qstat instead if not renamed? > Thanks for opinoin, but I think some miscommunication is present here. > I'm not a packager of torque. As I understand you correctly the issue > inhere torque than qstat. Anyway I've filled bug to torque with > references to this maillist discussion already. I'm wating for torque > packager response. The bugzilla URL would be nice. On the use of qstat: qstat/qsub and friends have been around in Unix/Linux queuing systems for some decades now, and it is expected by users of these systems to find the tools under qstat and not dqs-qstat, nqs-qstat or torque-qstat. I'm not sure how to fix this issue, but renaming qstat in torque is bad. Given that not many systems will run quake and a queuing managing system in parallel maybe Conflicts: is the lesser evil. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dcbw at redhat.com Fri Aug 4 14:15:01 2006 From: dcbw at redhat.com (Dan Williams) Date: Fri, 04 Aug 2006 10:15:01 -0400 Subject: Someone poke the buildsys please In-Reply-To: <1154687961.5572.15.camel@localhost.localdomain> References: <1154687961.5572.15.camel@localhost.localdomain> Message-ID: <1154700901.2678.7.camel@localhost.localdomain> On Fri, 2006-08-04 at 11:39 +0100, PFJ wrote: > Hi, > > monodevelop is currently failing to build on the FE buildsys. It's > giving the following error > > 8--> > Executing /usr/sbin/mock-helper yum > --installroot /var/lib/mock/fedora-development-i386-core-f653db06900991cff831a17766c2f27da84f5fc7/root install buildsys-build > file:///pub/fedora/linux/core/development/i386/os/Fedora/RPMS/unzip-5.52-2.2.1.i386.rpm: [Errno -1] Header is not complete. > Trying other mirror. Looks like the repo sync window got hit, or the repo is otherwise inconsistent... Can you requeue in about an hour or so and see if it goes through then? Dan From bugs.michael at gmx.net Fri Aug 4 14:45:20 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Fri, 4 Aug 2006 16:45:20 +0200 Subject: rpms/fish/devel .cvsignore, 1.4, 1.5 fish.spec, 1.7, 1.8 sources, 1.4, 1.5 In-Reply-To: <200608041420.k74EKmWq008743@cvs-int.fedora.redhat.com> References: <200608041420.k74EKmWq008743@cvs-int.fedora.redhat.com> Message-ID: <20060804164520.5f5e82a4.bugs.michael@gmx.net> On Fri, 4 Aug 2006 07:20:46 -0700, Axel Liljencrantz wrote: > Author: ascii > > Update of /cvs/extras/rpms/fish/devel > -%find_lang %{name}.\* > -%files -f %{name}.\*.lang > +# Translations > +%_datadir/locale/*/LC_MESSAGES/fish.mo http://fedoraproject.org/wiki/Packaging/ReviewGuidelines - MUST: The spec file MUST handle locales properly. This is done by using the %find_lang macro. Using %{_datadir}/locale/* is strictly forbidden. From liljencrantz at gmail.com Fri Aug 4 14:46:22 2006 From: liljencrantz at gmail.com (Axel Liljencrantz) Date: Fri, 4 Aug 2006 16:46:22 +0200 Subject: rpms/fish/devel .cvsignore, 1.4, 1.5 fish.spec, 1.7, 1.8 sources, 1.4, 1.5 In-Reply-To: <20060804164520.5f5e82a4.bugs.michael@gmx.net> References: <200608041420.k74EKmWq008743@cvs-int.fedora.redhat.com> <20060804164520.5f5e82a4.bugs.michael@gmx.net> Message-ID: <7dad0d770608040746i5af13b52oed7f1e5ea7dfbafd@mail.gmail.com> On 8/4/06, Michael Schwendt wrote: > On Fri, 4 Aug 2006 07:20:46 -0700, Axel Liljencrantz wrote: > > > Author: ascii > > > > Update of /cvs/extras/rpms/fish/devel > > > -%find_lang %{name}.\* > > > -%files -f %{name}.\*.lang > > > +# Translations > > +%_datadir/locale/*/LC_MESSAGES/fish.mo > > > http://fedoraproject.org/wiki/Packaging/ReviewGuidelines > > - MUST: The spec file MUST handle locales properly. This is done by using > the %find_lang macro. Using %{_datadir}/locale/* is strictly forbidden. My bad. Will fix. I'll also look into the build failiure under x86_64. > > -- > fedora-extras-list mailing list > fedora-extras-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-extras-list > -- Axel From garrick at usc.edu Fri Aug 4 16:32:39 2006 From: garrick at usc.edu (Garrick Staples) Date: Fri, 4 Aug 2006 09:32:39 -0700 Subject: duplicate filenames in the different packages [qstat vs. torque] In-Reply-To: <20060804131830.GA11342@neu.nirvana> References: <44D3030D.1060107@smile.org.ua> <20060804124804.b7f890ca.bugs.michael@gmx.net> <44D3321B.9010502@smile.org.ua> <20060804131830.GA11342@neu.nirvana> Message-ID: <20060804163239.GP4324@polop.usc.edu> On Fri, Aug 04, 2006 at 03:18:30PM +0200, Axel Thimm alleged: > On Fri, Aug 04, 2006 at 02:40:11PM +0300, Andy Shevchenko wrote: > > Michael Schwendt wrote: > > >>Tonight I've received the following bug > > >>http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201279 > > >>I'm packager of the qstat tool. But the torque (in torque-client) > > >>already consists the /usr/bin/qstat. > > > > >Why isn't this program called "torque-qstat"? You could patch it and > > >rename it like that. What is the sense in creating such a short and > > >generic name like "qstat"? Is the program useful outside of "torque"? > > >Could it be placed in /usr/libexec/torque/qstat instead if not renamed? > > Thanks for opinoin, but I think some miscommunication is present here. > > I'm not a packager of torque. As I understand you correctly the issue > > inhere torque than qstat. Anyway I've filled bug to torque with > > references to this maillist discussion already. I'm wating for torque > > packager response. > > The bugzilla URL would be nice. > > On the use of qstat: qstat/qsub and friends have been around in > Unix/Linux queuing systems for some decades now, and it is expected by > users of these systems to find the tools under qstat and not > dqs-qstat, nqs-qstat or torque-qstat. The name "qstat" is actually a requirement in POSIX 1003.2d, and as Axel stated, it has been implemented by many batch queueing systems over the decades. If we had more than 1 batch queueing system, than setting up an alternatives system would work. > I'm not sure how to fix this issue, but renaming qstat in torque is > bad. Given that not many systems will run quake and a queuing managing > system in parallel maybe Conflicts: is the lesser evil. Why bother with a Conflicts: tag? They already conflict, don't they? -- Garrick Staples, Linux/HPCC Administrator University of Southern California -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From wtogami at redhat.com Fri Aug 4 17:14:23 2006 From: wtogami at redhat.com (Warren Togami) Date: Fri, 04 Aug 2006 13:14:23 -0400 Subject: CVS Branch Request Change Message-ID: <44D3806F.5030700@redhat.com> http://fedoraproject.org/wiki/Extras/CVSSyncNeeded From now on please include bug numbers after package names when you make CVS Branch requests. This remains only a "temporary" process until we can better automate the workflow in the Package Database project. Warren Togami wtogami at redhat.com From j.w.r.degoede at hhs.nl Fri Aug 4 17:21:40 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Fri, 04 Aug 2006 19:21:40 +0200 Subject: Short vacation Message-ID: <44D38224.6090300@hhs.nl> Hi all, I'll be on a short vacation starting tomorrow, I'll be back coming wednesday. If in the mean time any earth shattering bugs or security issues in one of my packages turn up, you are free to fix them. If you do please drop me a private mail informing me of this. Regards, Hans From ad+lists at uni-x.org Fri Aug 4 17:17:50 2006 From: ad+lists at uni-x.org (Alexander Dalloz) Date: Fri, 04 Aug 2006 19:17:50 +0200 Subject: rpms/fish/devel fish.spec,1.10,1.11 In-Reply-To: <200608041523.k74FNru6012610@cvs-int.fedora.redhat.com> References: <200608041523.k74FNru6012610@cvs-int.fedora.redhat.com> Message-ID: <44D3813E.3020903@uni-x.org> Axel Liljencrantz (ascii) schrieb: >Author: ascii > >Update of /cvs/extras/rpms/fish/devel >In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12592 > >Modified Files: > fish.spec >Log Message: >Third try of update to 1.21.1. Revert accidental switch to wrong method for finding translation files, and add missing build dependency. > > Please don't forget to make a %changelog entry as well. Alexander From fedora at camperquake.de Fri Aug 4 17:17:47 2006 From: fedora at camperquake.de (Ralf Ertzinger) Date: Fri, 4 Aug 2006 19:17:47 +0200 Subject: duplicate filenames in the different packages [qstat vs. torque] In-Reply-To: <20060804163239.GP4324@polop.usc.edu> References: <44D3030D.1060107@smile.org.ua> <20060804124804.b7f890ca.bugs.michael@gmx.net> <44D3321B.9010502@smile.org.ua> <20060804131830.GA11342@neu.nirvana> <20060804163239.GP4324@polop.usc.edu> Message-ID: <20060804191747.71fdc751@nausicaa.camperquake.de> Hi. Garrick Staples wrote: > Why bother with a Conflicts: tag? They already conflict, don't they? It is usually considered to be polite to state this upfront instead of throwing obscure file conflict messages. -- "Bring 'em on. I prefer a straight fight to all this sneaking around." -- Han Solo From rvinyard at cs.nmsu.edu Fri Aug 4 18:01:58 2006 From: rvinyard at cs.nmsu.edu (Rick L Vinyard Jr) Date: Fri, 04 Aug 2006 12:01:58 -0600 Subject: rpms/tetex-IEEEtran/FC-4 tetex-IEEEtran.spec,1.2,1.3 In-Reply-To: <20060803170941.211ff44b.bugs.michael@gmx.net> References: <200607260331.k6Q3VCRs016831@cvs-int.fedora.redhat.com> <20060803170941.211ff44b.bugs.michael@gmx.net> Message-ID: <44D38B96.4080002@cs.nmsu.edu> Michael Schwendt wrote: > On Tue, 25 Jul 2006 20:31:10 -0700, Rick L. Vinyard wrote: > > >> +%triggerin -- lyx >> +if [ $2 -gt 1 ]; then >> +cd %{_datadir}/lyx && \ >> + ./configure --without-latex-config > /dev/null 2>&1 ||: >> +fi >> + >> +%triggerun -- lyx >> +if [ $2 -eq 0 ]; then >> +cd %{_datadir}/lyx && \ >> + ./configure --without-latex-config > /dev/null 2>&1 ||: >> +fi >> >> > > This change does not match lyx's own configuration and creates an empty > LaTex packages.lst. On the contrary, lyx %post runs "configure" including > the LaTeX packages check. > > Since Rex is the maintainer of lyx, I sent him a note yesterday to get his opinion on why he included the --without-latex-config in the triggers. I'm not sure how many other tetex packages potentially affect lyx, but it would be nice to have Rex's triggers in those as well (if there aren't any problems). From wart at kobold.org Fri Aug 4 18:02:59 2006 From: wart at kobold.org (Michael Thomas) Date: Fri, 04 Aug 2006 11:02:59 -0700 Subject: duplicate filenames in the different packages [qstat vs. torque] In-Reply-To: <20060804163239.GP4324@polop.usc.edu> References: <44D3030D.1060107@smile.org.ua> <20060804124804.b7f890ca.bugs.michael@gmx.net> <44D3321B.9010502@smile.org.ua> <20060804131830.GA11342@neu.nirvana> <20060804163239.GP4324@polop.usc.edu> Message-ID: <44D38BD3.3080900@kobold.org> Garrick Staples wrote: > On Fri, Aug 04, 2006 at 03:18:30PM +0200, Axel Thimm alleged: > >>On Fri, Aug 04, 2006 at 02:40:11PM +0300, Andy Shevchenko wrote: >> >>>Michael Schwendt wrote: >>> >>>>>Tonight I've received the following bug >>>>>http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201279 >>>>>I'm packager of the qstat tool. But the torque (in torque-client) >>>>>already consists the /usr/bin/qstat. >>> >>>>Why isn't this program called "torque-qstat"? You could patch it and >>>>rename it like that. What is the sense in creating such a short and >>>>generic name like "qstat"? Is the program useful outside of "torque"? >>>>Could it be placed in /usr/libexec/torque/qstat instead if not renamed? >>> >>>Thanks for opinoin, but I think some miscommunication is present here. >>>I'm not a packager of torque. As I understand you correctly the issue >>>inhere torque than qstat. Anyway I've filled bug to torque with >>>references to this maillist discussion already. I'm wating for torque >>>packager response. >> >>The bugzilla URL would be nice. >> >>On the use of qstat: qstat/qsub and friends have been around in >>Unix/Linux queuing systems for some decades now, and it is expected by >>users of these systems to find the tools under qstat and not >>dqs-qstat, nqs-qstat or torque-qstat. > > > The name "qstat" is actually a requirement in POSIX 1003.2d, and as Axel > stated, it has been implemented by many batch queueing systems over the > decades. > > If we had more than 1 batch queueing system, than setting up an > alternatives system would work. The 'qstat' package that Andy maintains is not part of a batch queuing system, however. It's a quake/halflife server query tool: http://www.qstat.org Perhaps the game-server qstat package should rename its binary to 'quakestat' to avoid the conflict? --Mike -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3820 bytes Desc: S/MIME Cryptographic Signature URL: From bugs.michael at gmx.net Fri Aug 4 18:33:14 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Fri, 4 Aug 2006 20:33:14 +0200 Subject: duplicate filenames in the different packages [qstat vs. torque] In-Reply-To: <20060804163239.GP4324@polop.usc.edu> References: <44D3030D.1060107@smile.org.ua> <20060804124804.b7f890ca.bugs.michael@gmx.net> <44D3321B.9010502@smile.org.ua> <20060804131830.GA11342@neu.nirvana> <20060804163239.GP4324@polop.usc.edu> Message-ID: <20060804203314.bd3152fc.bugs.michael@gmx.net> On Fri, 4 Aug 2006 09:32:39 -0700, Garrick Staples wrote: > Why bother with a Conflicts: tag? They already conflict, don't they? Explicit "Conflicts" make it clear that the conflict is intentional and known. Explicit "Conflicts" can be queried/examined/resolved more easily than finding out about it no later than with a first transaction check. > The name "qstat" is actually a requirement in POSIX 1003.2d, and as Axel > stated, it has been implemented by many batch queueing systems over the > decades. Valid point. The general part of my comment holds true, though, since for several other packages, pollution of /usr/bin or /usr/include is a reoccuring problem. It quickly gets nasty when example programs or small binary tools with very generic names are pulled in together with library packages. Generic file names are worth a second look during package review. From tibbs at math.uh.edu Fri Aug 4 18:37:06 2006 From: tibbs at math.uh.edu (Jason L Tibbitts III) Date: Fri, 04 Aug 2006 13:37:06 -0500 Subject: CVS Branch Request Change In-Reply-To: <44D3806F.5030700@redhat.com> (Warren Togami's message of "Fri, 04 Aug 2006 13:14:23 -0400") References: <44D3806F.5030700@redhat.com> Message-ID: >>>>> "WT" == Warren Togami writes: WT> From now on please include bug numbers after package names when WT> you make CVS Branch requests. Just to be sure, is the bug number supposed to refer to the package review ticket, or is a separate bug supposed to be opened that just requests the branch? What about packages that branched some time ago and are just now getting a branch to an older release for whatever reason? - J< From dan at danny.cz Fri Aug 4 18:40:44 2006 From: dan at danny.cz (Hor=?ISO-8859-2?Q?=E1?=k) Date: Fri, 4 Aug 2006 20:40:44 +0200 Subject: Code::Blocks IDE for Extras Message-ID: <200608042040.AA29294734@danny.cz> Hello, I have prepared packages of Code::Blocks IDE that could be included in Extras (see http://fedora.danny.cz). But there is one serious issue - due some bug in gcc 4.1 it is not possible to make it fully functional - C++ bindings of squirrel scripting language are broken, so almost all wizards don't work. The Patch0 makes the code at least to compile. If there is someone that is able to find the bug, please go into it. Dan From wtogami at redhat.com Fri Aug 4 18:51:06 2006 From: wtogami at redhat.com (Warren Togami) Date: Fri, 04 Aug 2006 14:51:06 -0400 Subject: CVS Branch Request Change In-Reply-To: References: <44D3806F.5030700@redhat.com> Message-ID: <44D3971A.6090606@redhat.com> Jason L Tibbitts III wrote: >>>>>> "WT" == Warren Togami writes: > > WT> From now on please include bug numbers after package names when > WT> you make CVS Branch requests. > > Just to be sure, is the bug number supposed to refer to the package > review ticket, or is a separate bug supposed to be opened that just > requests the branch? > > What about packages that branched some time ago and are just now > getting a branch to an older release for whatever reason? > > - J< > Good questions. Bug number should be of the review, and it is really optional. It only makes it faster for the branch approver to be sure the process was followed properly before branching. Warren Togami wtogami at redhat.com From fedora at camperquake.de Fri Aug 4 18:59:03 2006 From: fedora at camperquake.de (Ralf Ertzinger) Date: Fri, 4 Aug 2006 20:59:03 +0200 Subject: CVS Branch Request Change In-Reply-To: <44D3971A.6090606@redhat.com> References: <44D3806F.5030700@redhat.com> <44D3971A.6090606@redhat.com> Message-ID: <20060804205903.7fcd3300@nausicaa.camperquake.de> Hi. Warren Togami wrote: > Good questions. Bug number should be of the review, and it is really > optional. It only makes it faster for the branch approver to be sure > the process was followed properly before branching. What is this supposed to accomplish? Or the other way around: what does this protect against? -- "I love deadlines. I especially like the whooshing sound they make as they go flying by." -- Douglas Adams From wtogami at redhat.com Fri Aug 4 19:07:04 2006 From: wtogami at redhat.com (Warren Togami) Date: Fri, 04 Aug 2006 15:07:04 -0400 Subject: CVS Branch Request Change In-Reply-To: <20060804205903.7fcd3300@nausicaa.camperquake.de> References: <44D3806F.5030700@redhat.com> <44D3971A.6090606@redhat.com> <20060804205903.7fcd3300@nausicaa.camperquake.de> Message-ID: <44D39AD8.8030201@redhat.com> Ralf Ertzinger wrote: > Hi. > > Warren Togami wrote: > >> Good questions. Bug number should be of the review, and it is really >> optional. It only makes it faster for the branch approver to be sure >> the process was followed properly before branching. > > What is this supposed to accomplish? > Or the other way around: what does this protect against? > Enforce FC-3 branching restriction. As the approver, it helps me to have an idea of what new contributors are doing and if they need help in education of the process. Warren Togami wtogami at redhat.com From Axel.Thimm at ATrpms.net Fri Aug 4 19:07:58 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Fri, 4 Aug 2006 21:07:58 +0200 Subject: duplicate filenames in the different packages [qstat vs. torque] In-Reply-To: <20060804163239.GP4324@polop.usc.edu> References: <44D3030D.1060107@smile.org.ua> <20060804124804.b7f890ca.bugs.michael@gmx.net> <44D3321B.9010502@smile.org.ua> <20060804131830.GA11342@neu.nirvana> <20060804163239.GP4324@polop.usc.edu> Message-ID: <20060804190758.GA18815@neu.nirvana> On Fri, Aug 04, 2006 at 09:32:39AM -0700, Garrick Staples wrote: > Why bother with a Conflicts: tag? They already conflict, don't they? Adding to all valiud points made by other: Usually depsolvers only know about file conflicts when they unleash the rpm transaction which then fails. An explicit Conflicts: informs the depsolver early in its computation about whether to not include the conflicting package or sometimes even to remove a package. E.g. when packages A and B conflict, explicitly asking a depsolver to install B may remove A (I know it's the case for apt and smart, not 100% sure about yum). Whether this policy or intelligent depsolvers is desired or not is another topic, the explict Conflicts: just enables the processing of this information into depsolver mechanics. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From brkamikaze at gmail.com Fri Aug 4 19:12:29 2006 From: brkamikaze at gmail.com (Nikolai) Date: Fri, 4 Aug 2006 16:12:29 -0300 Subject: A -debuginfo package failing to "exist" Message-ID: I am packaging a game that is compiled without symbols, and when RPM is creating the binary package I get the error "N?o consegui abrir o ficheiro do %files /usr/src/redhat/BUILD/widelands-20060801/debugfiles.list: Arquivo ou diret?rio n?o encontrado", a.k.a File Not Found in english. What can I do to prevent the generation of the "-debuginfo" package? From mattdm at mattdm.org Fri Aug 4 19:14:00 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Fri, 4 Aug 2006 15:14:00 -0400 Subject: A -debuginfo package failing to "exist" In-Reply-To: References: Message-ID: <20060804191400.GA26388@jadzia.bu.edu> On Fri, Aug 04, 2006 at 04:12:29PM -0300, Nikolai wrote: > I am packaging a game that is compiled without symbols, and when RPM > is creating the binary package I get the error "N?o consegui abrir o > ficheiro do %files > /usr/src/redhat/BUILD/widelands-20060801/debugfiles.list: Arquivo ou > diret?rio n?o encontrado", a.k.a File Not Found in english. What can > I do to prevent the generation of the "-debuginfo" package? I think you're fixing the wrong problem -- instead, make the game be compiled with the debug information. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From peter at thecodergeek.com Fri Aug 4 20:24:38 2006 From: peter at thecodergeek.com (Peter Gordon) Date: Fri, 04 Aug 2006 13:24:38 -0700 Subject: Short vacation In-Reply-To: <44D38224.6090300@hhs.nl> References: <44D38224.6090300@hhs.nl> Message-ID: <44D3AD06.1030800@thecodergeek.com> Hans de Goede wrote: > I'll be on a short vacation starting tomorrow, I'll be back coming > wednesday. If in the mean time any earth shattering bugs or security > issues in one of my packages turn up, you are free to fix them. If you > do please drop me a private mail informing me of this. Have a great time; and stay safe! :) -- Peter Gordon (codergeek42) GnuPG Public Key ID: 0xFFC19479 / Fingerprint: DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479 My Blog: http://thecodergeek.com/blog/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From liljencrantz at gmail.com Fri Aug 4 20:58:37 2006 From: liljencrantz at gmail.com (Axel Liljencrantz) Date: Fri, 4 Aug 2006 22:58:37 +0200 Subject: rpms/fish/devel fish.spec,1.10,1.11 In-Reply-To: <44D3813E.3020903@uni-x.org> References: <200608041523.k74FNru6012610@cvs-int.fedora.redhat.com> <44D3813E.3020903@uni-x.org> Message-ID: <7dad0d770608041358o6c288063g62c16572700b1730@mail.gmail.com> On 8/4/06, Alexander Dalloz wrote: > Axel Liljencrantz (ascii) schrieb: > > >Author: ascii > > > >Update of /cvs/extras/rpms/fish/devel > >In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12592 > > > >Modified Files: > > fish.spec > >Log Message: > >Third try of update to 1.21.1. Revert accidental switch to wrong method for finding translation files, and add missing build dependency. > > > > > Please don't forget to make a %changelog entry as well. Done. Thanks. > > Alexander > > > -- > fedora-extras-list mailing list > fedora-extras-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-extras-list > -- Axel From brkamikaze at gmail.com Fri Aug 4 21:51:13 2006 From: brkamikaze at gmail.com (Nikolai) Date: Fri, 4 Aug 2006 18:51:13 -0300 Subject: A -debuginfo package failing to "exist" In-Reply-To: <20060804191400.GA26388@jadzia.bu.edu> References: <20060804191400.GA26388@jadzia.bu.edu> Message-ID: > I think you're fixing the wrong problem -- instead, make the game be > compiled with the debug information. That was the wrong problem indeed. The game uses SCONS, and due to the lack of experience I forgot to turn on debug (autotools always enable debug) :P From Christian.Iseli at licr.org Fri Aug 4 23:15:30 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Sat, 5 Aug 2006 01:15:30 +0200 Subject: Package database, SCM, ACLs, co-maintainership, and all that stuff Message-ID: <20060805011530.1aaf09b3@ludwig-alpha> Warning, brain dump ahead... We want lots of packages We want lots of maintainers We want to make it easy for maintainers to collaborate We also want secure packages One of the nagging questions is: how do we keep things as open as possible while ensuring that no malicious/bad edits are planted in packages. We can put controls at three points: 1. at the SCM level, with ACLs 2. at the build level, with a proper package database 3. at the package signing stage 1 is maybe a bit premature. SCM is nice in the way that it's easy to know who changed what, and bad things can be undone easily. It's also completely private: no external user is affected if a bad change temporarily enters the SCM. When collaborating, it's nice to just be able to say to your friend maintainer: "just commit your change to the SCM". 2 might be a good point to make checks. Effects of builds are semi-private: newly built packages are available to the buildsys to build further packages, and could have potential impact on packages released to our users. It'd need fine grained controls in the package database though, and must work in a completely automated way. 3 is the last chance before the package is released unto the world. The nice thing is that this step is performed by a real person, who can use her/his better judgement to decide whether or not to sign a package. The risk is that the task becomes complicated and burdensome... Ah well, time to go get some sleep. Cheers, Christian From garrick at usc.edu Sat Aug 5 02:50:16 2006 From: garrick at usc.edu (Garrick Staples) Date: Fri, 4 Aug 2006 19:50:16 -0700 Subject: duplicate filenames in the different packages [qstat vs. torque] In-Reply-To: <20060804203314.bd3152fc.bugs.michael@gmx.net> References: <44D3030D.1060107@smile.org.ua> <20060804124804.b7f890ca.bugs.michael@gmx.net> <44D3321B.9010502@smile.org.ua> <20060804131830.GA11342@neu.nirvana> <20060804163239.GP4324@polop.usc.edu> <20060804203314.bd3152fc.bugs.michael@gmx.net> Message-ID: <20060805025016.GT4324@polop.usc.edu> On Fri, Aug 04, 2006 at 08:33:14PM +0200, Michael Schwendt alleged: > On Fri, 4 Aug 2006 09:32:39 -0700, Garrick Staples wrote: > > The name "qstat" is actually a requirement in POSIX 1003.2d, and as Axel > > stated, it has been implemented by many batch queueing systems over the > > decades. > > Valid point. The general part of my comment holds true, though, since > for several other packages, pollution of /usr/bin or /usr/include is > a reoccuring problem. It quickly gets nasty when example programs or > small binary tools with very generic names are pulled in together > with library packages. Generic file names are worth a second look during > package review. Especially when these "other" packages violate POSIX, IEEE, and SUSv3 :) -- Garrick Staples, Linux/HPCC Administrator University of Southern California -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jeff at ocjtech.us Sat Aug 5 03:28:05 2006 From: jeff at ocjtech.us (Jeffrey C. Ollie) Date: Fri, 04 Aug 2006 22:28:05 -0500 Subject: Package database, SCM, ACLs, co-maintainership, and all that stuff In-Reply-To: <20060805011530.1aaf09b3@ludwig-alpha> References: <20060805011530.1aaf09b3@ludwig-alpha> Message-ID: <1154748486.2632.27.camel@lt16858.campus.dmacc.edu> On Sat, 2006-08-05 at 01:15 +0200, Christian Iseli wrote: > > One of the nagging questions is: how do we keep things as open as > possible while ensuring that no malicious/bad edits are planted in > packages. > > We can put controls at three points: > 1. at the SCM level, with ACLs > 2. at the build level, with a proper package database > 3. at the package signing stage * Minimal ACLs on SCM, so any authenticated user can commit changes to any package. I'd recommend however ACLs to keep the directory structure organized though. * However, emails are generated to directly to all maintainers of a particular area. That way unauthorized changes get noticed faster by the maintainers. * Builds can be initiated only by package maintainers and the security team (so that security fixes can be pushed out quickly). The security team would keep changes to the minimum necessary to resolve a security problem. * Before a build is initiated, the initiator would have to "approve" somehow all of the changes made by non-maintainers. Not quite sure how this would work, esp. given the need to track reversions of unapproved changes. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From jamatos at fc.up.pt Sat Aug 5 08:14:39 2006 From: jamatos at fc.up.pt (=?iso-8859-1?q?Jos=E9_Matos?=) Date: Sat, 5 Aug 2006 09:14:39 +0100 Subject: rpms/tetex-IEEEtran/FC-4 tetex-IEEEtran.spec,1.2,1.3 In-Reply-To: <44D38B96.4080002@cs.nmsu.edu> References: <200607260331.k6Q3VCRs016831@cvs-int.fedora.redhat.com> <20060803170941.211ff44b.bugs.michael@gmx.net> <44D38B96.4080002@cs.nmsu.edu> Message-ID: <200608050914.39567.jamatos@fc.up.pt> On Friday 04 August 2006 19:01, Rick L Vinyard Jr wrote: > > Since Rex is the maintainer of lyx, I sent him a note yesterday to get > his opinion on why he included the --without-latex-config in the > triggers. I'm not sure how many other tetex packages potentially affect > lyx, but it would be nice to have Rex's triggers in those as well (if > there aren't any problems). tetex-dvipost is one. OTOH as a lyx developer I seem to remember that something changed recently in the way as lyx checks its configuration. I think that now it does that at user level and not at system level, that is what the scheme intends to do... I need to search for some answers. :-) -- Jos? Ab?lio From paul at all-the-johnsons.co.uk Sat Aug 5 09:40:32 2006 From: paul at all-the-johnsons.co.uk (Paul) Date: Sat, 05 Aug 2006 10:40:32 +0100 Subject: Really strange permissions issue Message-ID: <1154770832.4220.16.camel@T7.Linux> Hi, Bit of background. As some know, I maintain quite a few packages and review even more. My old buildsys was a rescue job from a skip with a P2-600(ish) in. Last week, it finally died, but the drives were fine. I replaced the drives into a P4-700 box, fired up and all was well. The system booted up and I could log in locally to all three users on the system (paul, build and su). Normally, I don't log into the box, I ssh onto it. Tested that and it worked as well. Great. Now I had to do an updated (the old box would die when updating). ssh to the box, su, yum -y update. yum complained saying it couldn't find a valid repo for extras or development. Okay. Logged into the box directly (same user, build), yum -y update - same result. Logged out. Logged in as paul, started X, ran yumex and all was well. Next time I updated. I directly logged in as build, tried running yum, same result. Logged out, logged in as paul, yum worked perfectly. At this point, I disabled selinux just incase. Rebooted the buildsys. Next test, ssh to the buildsys as paul. yum works fine. Tried user build - same result - can't find repo. This leads me to suspect a problem with user build, but I'm at a loss as to how to fix the problem. Any suggestions? I need to get user build working again as it's holding up a number of package reviews (as well as me submitting some more) TTFN Paul -- Wenn sie denken, dass die bildung teuer ist, versuchen sie ignoranz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From paul at all-the-johnsons.co.uk Sat Aug 5 11:29:18 2006 From: paul at all-the-johnsons.co.uk (Paul) Date: Sat, 05 Aug 2006 12:29:18 +0100 Subject: Any sign of a push? Message-ID: <1154777358.4220.21.camel@T7.Linux> Hi, I can't seem to see any FE pushes for the past couple of days. Is there a problem with the email out or is me? TTFN Paul (looking for Monodevelop) -- Wenn sie denken, dass die bildung teuer ist, versuchen sie ignoranz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From skvidal at linux.duke.edu Sat Aug 5 11:33:12 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Sat, 05 Aug 2006 07:33:12 -0400 Subject: Any sign of a push? In-Reply-To: <1154777358.4220.21.camel@T7.Linux> References: <1154777358.4220.21.camel@T7.Linux> Message-ID: <1154777592.3092.0.camel@cutter> On Sat, 2006-08-05 at 12:29 +0100, Paul wrote: > Hi, > > I can't seem to see any FE pushes for the past couple of days. Is there > a problem with the email out or is me? we had a drive failure on the system to where the packages are pushed. I'm out of town on a little trip and I've not had a chance to check the push mechanism to make sure it will work. I'll see if I get to it tonight. -sv From brkamikaze at gmail.com Sat Aug 5 11:36:57 2006 From: brkamikaze at gmail.com (Nikolai) Date: Sat, 5 Aug 2006 08:36:57 -0300 Subject: Really strange permissions issue In-Reply-To: <1154770832.4220.16.camel@T7.Linux> References: <1154770832.4220.16.camel@T7.Linux> Message-ID: As I use the computer only at home (and I'm the only user), security is not a big concern, so I just chmod a+rw(x) on everything that fails. If this is ok for you, do it. Try setting the debug information to 10 on yum.conf and running yum again, it should spit out some useful information. From paul at all-the-johnsons.co.uk Sat Aug 5 12:25:32 2006 From: paul at all-the-johnsons.co.uk (Paul) Date: Sat, 05 Aug 2006 13:25:32 +0100 Subject: Really strange permissions issue In-Reply-To: References: <1154770832.4220.16.camel@T7.Linux> Message-ID: <1154780732.4220.23.camel@T7.Linux> Hi, > Try setting the debug information to 10 on yum.conf and running yum > again, it should spit out some useful information. Gives almost exactly the same info as before except the buildroot is \ and the COMMAND was yum -- Wenn sie denken, dass die bildung teuer ist, versuchen sie ignoranz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From paul at city-fan.org Sat Aug 5 14:40:10 2006 From: paul at city-fan.org (Paul Howarth) Date: Sat, 05 Aug 2006 15:40:10 +0100 Subject: Really strange permissions issue In-Reply-To: <1154770832.4220.16.camel@T7.Linux> References: <1154770832.4220.16.camel@T7.Linux> Message-ID: <1154788810.21385.33.camel@laurel.intra.city-fan.org> On Sat, 2006-08-05 at 10:40 +0100, Paul wrote: > Hi, > > Bit of background. > > As some know, I maintain quite a few packages and review even more. My > old buildsys was a rescue job from a skip with a P2-600(ish) in. Last > week, it finally died, but the drives were fine. > > I replaced the drives into a P4-700 box, fired up and all was well. The > system booted up and I could log in locally to all three users on the > system (paul, build and su). > > Normally, I don't log into the box, I ssh onto it. Tested that and it > worked as well. Great. > > Now I had to do an updated (the old box would die when updating). ssh to > the box, su, yum -y update. yum complained saying it couldn't find a > valid repo for extras or development. > > Okay. Logged into the box directly (same user, build), yum -y update - > same result. Logged out. Logged in as paul, started X, ran yumex and all > was well. > > Next time I updated. I directly logged in as build, tried running yum, > same result. Logged out, logged in as paul, yum worked perfectly. At > this point, I disabled selinux just incase. > > Rebooted the buildsys. > > Next test, ssh to the buildsys as paul. yum works fine. > > Tried user build - same result - can't find repo. > > This leads me to suspect a problem with user build, but I'm at a loss as > to how to fix the problem. Any suggestions? I need to get user build > working again as it's holding up a number of package reviews (as well as > me submitting some more) Look at the ownership and permissions of all of the yum config files and their parent directories: $ ls -ld / /etc /etc/yum* $ ls -la /etc/yum.repos.d Paul. From toshio at tiki-lounge.com Sat Aug 5 14:42:25 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Sat, 05 Aug 2006 07:42:25 -0700 Subject: Really strange permissions issue In-Reply-To: <1154770832.4220.16.camel@T7.Linux> References: <1154770832.4220.16.camel@T7.Linux> Message-ID: <1154788945.3765.5.camel@localhost> On Sat, 2006-08-05 at 10:40 +0100, Paul wrote: > Next time I updated. I directly logged in as build, tried running yum, > same result. Logged out, logged in as paul, yum worked perfectly. At > this point, I disabled selinux just incase. Can user build ping a repository host? Can user build wget files from the repositories directly? Does rpm -V yum and rpm -V mock show any problems? If you create a new user does the new user have issues? Are you becoming root via su or sudo? -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From paul at all-the-johnsons.co.uk Sat Aug 5 15:25:31 2006 From: paul at all-the-johnsons.co.uk (Paul) Date: Sat, 05 Aug 2006 16:25:31 +0100 Subject: Really strange permissions issue In-Reply-To: <1154788810.21385.33.camel@laurel.intra.city-fan.org> References: <1154770832.4220.16.camel@T7.Linux> <1154788810.21385.33.camel@laurel.intra.city-fan.org> Message-ID: <1154791531.4220.30.camel@T7.Linux> Hi, > Look at the ownership and permissions of all of the yum config files and > their parent directories: > > $ ls -ld / /etc /etc/yum* All owned by root:root > $ ls -la /etc/yum.repos.d All owned by root:root Can't see a problem there :-( TTFN Paul -- Wenn sie denken, dass die bildung teuer ist, versuchen sie ignoranz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From paul at all-the-johnsons.co.uk Sat Aug 5 15:33:40 2006 From: paul at all-the-johnsons.co.uk (Paul) Date: Sat, 05 Aug 2006 16:33:40 +0100 Subject: Really strange permissions issue In-Reply-To: <1154788945.3765.5.camel@localhost> References: <1154770832.4220.16.camel@T7.Linux> <1154788945.3765.5.camel@localhost> Message-ID: <1154792020.4220.37.camel@T7.Linux> Hi, > Can user build wget files from > the repositories directly? No. I get Resolving localhost 127.0.0.1 Connecting to localhost|127.0.0.1|:3128... failed: Connection refused Isn't 3128 squid? Let's switch it on. Bummer. That got it. I'll go back to sleep now... Thanks for that. I need more coffee! TTFN Paul -- Wenn sie denken, dass die bildung teuer ist, versuchen sie ignoranz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From davidswaty at gmail.com Sun Aug 6 01:05:43 2006 From: davidswaty at gmail.com (David Swaty) Date: Sat, 5 Aug 2006 20:05:43 -0500 Subject: please remove me from list Message-ID: <87c8c03f0608051805v71051495n4585e76104e44a63@mail.gmail.com> please remove me from list -------------- next part -------------- An HTML attachment was scrubbed... URL: From peter at thecodergeek.com Sun Aug 6 03:07:17 2006 From: peter at thecodergeek.com (Peter Gordon) Date: Sat, 05 Aug 2006 20:07:17 -0700 Subject: please remove me from list In-Reply-To: <87c8c03f0608051805v71051495n4585e76104e44a63@mail.gmail.com> References: <87c8c03f0608051805v71051495n4585e76104e44a63@mail.gmail.com> Message-ID: <44D55CE5.60507@thecodergeek.com> David Swaty wrote: > please remove me from list Hello, David. You need to manually unsubscribe yourself by visiting the list's info page[1], wherein there is a section at the bottom that you can use to unsubscribe yourself and/or edit your subscription options. Have a great day! -- Peter Gordon (codergeek42) GnuPG Public Key ID: 0xFFC19479 / Fingerprint: DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479 My Blog: http://thecodergeek.com/blog/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From peter at thecodergeek.com Sun Aug 6 03:10:09 2006 From: peter at thecodergeek.com (Peter Gordon) Date: Sat, 05 Aug 2006 20:10:09 -0700 Subject: please remove me from list In-Reply-To: <44D55CE5.60507@thecodergeek.com> References: <87c8c03f0608051805v71051495n4585e76104e44a63@mail.gmail.com> <44D55CE5.60507@thecodergeek.com> Message-ID: <44D55D91.9040500@thecodergeek.com> Peter Gordon wrote: > David Swaty wrote: >> please remove me from list > > Hello, David. You need to manually unsubscribe yourself by visiting the > list's info page[1], wherein there is a section at the bottom that you > can use to unsubscribe yourself and/or edit your subscription options. > > Have a great day! > It'd be great if I actually appended the footnotes which I reference in my message. [1] https://www.redhat.com/mailman/listinfo/fedora-extras-list Sorry about that. >_< -- Peter Gordon (codergeek42) GnuPG Public Key ID: 0xFFC19479 / Fingerprint: DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479 My Blog: http://thecodergeek.com/blog/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From fedora at leemhuis.info Sun Aug 6 11:07:46 2006 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Sun, 06 Aug 2006 13:07:46 +0200 Subject: Fix problems building Extras packages for FC3 and FC4 Message-ID: <44D5CD82.8040103@leemhuis.info> Hi! Now that mock on the Extras builders was updated to 0.6 (thx dgilmore for your work) we noticed that there are big problems building Extras packages for FC3 and FC4. For details see this thread: https://www.redhat.com/archives/fedora-extras-list/2006-August/msg00091.html The problem is well know and described in #196930 -- opened by Paul Howarth on 2006-06-27 We really should fix this as soon as possible. That means: - add elfutils to the default buildroot in all Fedora Dists < FC5 - add python to the default buildroot in FC3 and FC4 Everyone (especially fedora-packaging) fine with that? I'd like to see this fixed soon and would like to avoid waiting for the next meetings. If yes: can somebody (skvidal) please apply this patch: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=133705 and update http://buildsys.fedoraproject.org/buildgroups/ please? The patch does what's described above and also fixes the default buildroots for older dists (see patch for details). CU thl From ville.skytta at iki.fi Sun Aug 6 11:33:43 2006 From: ville.skytta at iki.fi (Ville =?ISO-8859-1?Q?Skytt=E4?=) Date: Sun, 06 Aug 2006 14:33:43 +0300 Subject: Fix problems building Extras packages for FC3 and FC4 In-Reply-To: <44D5CD82.8040103@leemhuis.info> References: <44D5CD82.8040103@leemhuis.info> Message-ID: <1154864023.2997.28.camel@localhost.localdomain> On Sun, 2006-08-06 at 13:07 +0200, Thorsten Leemhuis wrote: > - add elfutils to the default buildroot in all Fedora Dists < FC5 > - add python to the default buildroot in FC3 and FC4 > > Everyone (especially fedora-packaging) fine with that? +1 From fedora at leemhuis.info Sun Aug 6 12:41:46 2006 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Sun, 06 Aug 2006 14:41:46 +0200 Subject: I'll request removal of brightside and notemeister from devel branch soon and mark them as orphans Message-ID: <44D5E38A.6010108@leemhuis.info> Hi! Just FYI, I'll request removal of brightside and notemeister from extras/devel soon and will mark them as orphans in owners.list (I'll add myself to the initial CC-list in case new bugs show up for existing packages). Feel free to take them over if you are interested in them. I never really liked brightside (I liked the edge-flipping feature in the gnome 1.X days but now it confuses me) and so lost interest in it. Upstream seems to be vanished in the past months. notemeister is officially stopped upstream - see http://notemeister.sourceforge.net/ for details. Successor: http://newton.sourceforge.net/ Cu thl From wtogami at redhat.com Sun Aug 6 17:54:31 2006 From: wtogami at redhat.com (Warren Togami) Date: Sun, 06 Aug 2006 13:54:31 -0400 Subject: Any sign of a push? In-Reply-To: <1154777592.3092.0.camel@cutter> References: <1154777358.4220.21.camel@T7.Linux> <1154777592.3092.0.camel@cutter> Message-ID: <44D62CD7.8070103@redhat.com> seth vidal wrote: > On Sat, 2006-08-05 at 12:29 +0100, Paul wrote: >> Hi, >> >> I can't seem to see any FE pushes for the past couple of days. Is there >> a problem with the email out or is me? > > we had a drive failure on the system to where the packages are pushed. > I'm out of town on a little trip and I've not had a chance to check the > push mechanism to make sure it will work. > > I'll see if I get to it tonight. > Attempted a sign & push just now. Signing succeeded, but it failed somewhere during sync with "Input/output error". Don't know if this is more fallout from the disk failure, and I don't have access to the other side of rsync to investigate further. Warren Togami wtogami at redhat.com From fedora at leemhuis.info Sun Aug 6 18:25:03 2006 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Sun, 06 Aug 2006 20:25:03 +0200 Subject: RFC: Split Package with Obsolete Message-ID: <44D633FF.3010700@leemhuis.info> Hi, I want to split off the evolution plugin from mail-notification into a separate package to avoid the dep on evolution in the main mail-notification package. That's supported by mail-notification. But this leads to one problem: Users of the evolution plugin in mail-notification now need to manually install the new sub-package to gain all the features they had before in the non-split mail-notification. There are now two scenarios to proceed afaics: 1) Do the split only in devel/FC6 and get it documented in the release notes. 2) add a this two lines to the new sub-pacakge: Requires: %{name} = %{version}-%{release} Obsoletes: mail-notification < 3.0-4 (see attached patch for the full context). This way yum will install the new subpackage because it obsoletes the old main-package *and* yum will install the new main-package because it's a dep of the new subpackage. Worked as expected in a local test: ---- $ sudo yum --enablerepo=test update [...] Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Downloading header for mail-notification-evolution-plugin to pack into transaction set. mail-notification-evoluti 100% |=========================| 7.3 kB 00:00 ---> Package mail-notification-evolution-plugin.i386 0:3.0-4 set to be updated --> Running transaction check --> Processing Dependency: mail-notification = 3.0-4 for package: mail-notification-evolution-plugin --> Restarting Dependency Resolution with new changes. --> Populating transaction set with selected packages. Please wait. ---> Downloading header for mail-notification to pack into transaction set. mail-notification-3.0-4.i 100% |=========================| 15 kB 00:00 ---> Package mail-notification.i386 0:3.0-4 set to be updated --> Running transaction check Dependencies Resolved ============================================================================= Package Arch Version Repository Size ============================================================================= Installing: mail-notification-evolution-plugin i386 3.0-4 test 22 k replacing mail-notification.i386 3.0-2.fc5 Updating for dependencies: mail-notification i386 3.0-4 test 341 k Transaction Summary ============================================================================= Install 1 Package(s) Update 1 Package(s) Remove 0 Package(s) Total download size: 363 k Is this ok [y/N]: y Downloading Packages: Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating : mail-notification ######################### [1/3] Installing: mail-notification-evolution- ######################### [2/3] Cleanup : mail-notification ######################### [3/3] Installed: mail-notification-evolution-plugin.i386 0:3.0-4 Dependency Updated: mail-notification.i386 0:3.0-4 Replaced: mail-notification.i386 0:3.0-2.fc5 Complete! ---- This is somewhat hackish, but it's probably the most comfortable way for the user. Does anyone know why solution 2) should not work or if it leads to trouble somewhere? If not I'm going to try it (of course only in devel)... CU thl -------------- next part -------------- A non-text attachment was scrubbed... Name: ml.patch Type: text/x-patch Size: 2508 bytes Desc: not available URL: From toshio at tiki-lounge.com Sun Aug 6 18:30:59 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Sun, 06 Aug 2006 11:30:59 -0700 Subject: 2006 August 05 FESCo Meeting Minutes Message-ID: <1154889059.3765.63.camel@localhost> = 2006 August 05 FESCo Meeting = Meeting Summaries are posted on the wiki at: http://www.fedoraproject.org/wiki/Extras/SteeringCommittee/Meetings == Attending == * thl * c4chris * tibbs * bpepple * abadger1999 * warren * jwb (late) * dgilmore (late) == Summary == * Mass Rebuild * Builders are updated. Need to add python and elfutils so that FC < 5 works in the builders. * Mass rebuild for FC6 will start on Mon, 28th August since Core is not expecting any changes that would require a rebuild after that. * Email to fedora-extras will request comments on length of time for maintainers to rebuild their packages before someone else rebuilds for them and whether all packages need to be rebuilt or not. * Comaintainership * thl sent a message but got no replies so far. * Having SIGs be co-maintainers was well received. * Package database is needed to enable a lot of the functionality. * SCM needs (should?) have ACLs for separating write access by group. This is hopefully coming between FC6 and FC7. * Comps.xml * For now the report on comps will list everything except perl-*, python-*, lib*, and *-devel. * Better results but harder to implement would be to retrieve dependency information and only complain about packages which are not depended upon by anything else. * Stalled Review * Approved: http://fedoraproject.org/wiki/JasonTibbitts/StalledReviewPolicy * Warren will setup nobody at fedoraproject.org to handle unassigned bugs. * Activate Legacy in the buildroots: * Most FESCo members accepted that legacy should be added to the buildroots (has security fixes and is what we want end-users on Legacy to run.) * There was some discussion around mschwendt's post about this: https://www.redhat.com/archives/fedora-maintainers/2006-July/msg00005.html * Dissent centered around who is responsible for supporting FE when the equivalent FC goes Legacy. * Security Team, Fedora Legacy (Core), and at least some Fedora Extras maintainers don't want the responsiblity. * Co-maintainers (with the package database) could help track volunteers who are fixing the older releases but this still leaves open who is responsible. * At the moment, some FE maintainers are doing the work but dgilmore has personally done ~10 security rebuilds on FE3 for packages he does not own. * tibbs will bring this to extras-list as a draft document of maintainers responsibilities. * Kmod reviews * sysprof was accepted as it seems to be an interim measure until the userspace GUI can be migrated to oprofile. * However, there might not be any work being done on this currently. * zaptel: The upstream authors have stated they do not want to get the module into the kernel due to their preference for a dual license. * nirik will generate an email about zaptel in specific and kmod criteria in general on the fedora-devel list. * CVS Branch Requests * As an interim measure, packagers submitting a branch request should append the bug number to the request: {{{* FC-4 FC-5 cluestick 28437}}} * Package Database is the eventual solution. * Package Database * c4chris will open a discussion on fedora-extras this week. * Encourage Extras Reviews * We're doing better now. * Getting new people involved via co-maintainership should help as well. * This item is being closed for now. * mono packaging * mono-core may move to libdir in time for FC6 -- it depends on how serious this bug turns out to be: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199790 == Log == {{{ (10:00:23) thl: my clock says it's time to start (10:00:35) c4chris: mine too :) (10:00:37) thl has changed the topic to: FESCo Meeting in progress (10:00:48) thl: k, who's around? (10:00:57) tibbs: I'm here. (10:00:58) ***bpepple is here. (10:00:59) ***cweyl is here (rabble) (10:01:03) abadger1999: i'm back (10:01:24) ***nirik is in the rabble seats. (10:01:35) thl: dgilmore, are you around? (10:02:01) thl: well, let's start slowly (10:02:05) c4chris: hmm 5/13 th... (10:02:43) warren: here (10:02:43) thl: c4chris|w, well, I prefer a meeting with only 5 people over no meeting (10:03:08) c4chris: sure. should've added a half smiley (10:03:11) thl: c4chris, we did a lot of meeting with only five of 17 in the old FESCo (10:03:18) thl: c4chris, k (10:03:34) c4chris: 6 now :-) (10:03:40) thl: I got the impression that some people only want meetings when we are at least seven ;-) (10:03:43) thl has changed the topic to: FESCo Meeting in progress -- M{ae}ss-Rebuild (10:03:46) ***nirik would hope that the shiny new FESCo would have more folks interested in participating.... (10:04:01) tibbs: Several folks are on vacation this week. (10:04:09) tibbs: At leasr Rex and spot. (10:04:10) thl: k, dglimore upgraded the builders (10:04:21) thl: that's not working perfectly (10:04:24) warren: Is test3 enough time to rebuild everything before final? (10:04:24) thl: but mostly (10:04:46) thl: warren, I still prefer to start a bit earlier (10:04:46) c4chris: thl, anyone working on the strip problem? (10:04:57) thl: c4chris, I suppose we need dgilmore for that job (10:04:57) tibbs: Is there any downside to having folks start early if they want? (10:05:00) warren: c4chris, is that documented anywhere? (10:05:14) abadger1999: tibbs: Just that they might have to do it again later. (10:05:17) thl: warren, on the list only currently (10:05:20) c4chris: warren, no idea (10:05:30) abadger1999: (If there's a late gcc change, python upgrade, et al.) (10:05:38) thl: abadger1999, agreed (10:06:00) thl: warren, "late gcc change, python upgrade, et al." -> if we get a go from core we can start (10:06:13) warren: let me check (10:06:41) stickster [n=paul] entered the room. (10:07:07) thl: warren, but I prefer FC6T3 over a "ohh, sorry, we found a problem in foo; you need to rebuild everything in Extras once again" (10:07:10) c4chris: dgilmore sent a messaeg saying he'd be at ClueCon (whatever that is) (10:07:24) bpepple: thl: +1 (10:07:38) nirik: FYI, the stripping and python issues for fc4 are discussed in this thread: https://www.redhat.com/archives/fedora-extras-list/2006-August/msg00091.html (10:08:14) warren: No changes are expected, we should go ahead. How about late August? (10:08:28) thl: warren, sounds good to me (10:08:42) thl: 28 August? (10:08:49) thl: that's a monday (10:09:02) cweyl: is there a definition of what needs to be rebuilt, again? all packages !noarch? (10:09:23) thl: I don't have a definition yet (10:09:32) thl: scop probably should know (10:09:48) warren: how about we discuss that on list, and have a definition by August 24th's meeting (10:10:08) thl: warren, +1 (10:10:14) thl: but one thing here (10:10:30) thl: how much time should we give people to rebuild there pacakges? (10:10:33) thl: two weeks? (10:10:49) thl: three weeks? (10:10:51) bpepple: thl: How about 3? Some people have got a lot of packages. (10:10:55) c4chris: I think 3 (10:11:01) tibbs: It kind of depends on how the buildsys can handle the load. (10:11:13) tibbs: The new buildroots seem to have sped things up a bit, which is good. (10:11:29) tibbs: But if we experience the hanging problems again then it could take quite some time. (10:11:37) c4chris: Did we ever bring the buildsys down through overloading? (10:12:07) thl: c4chris, I don#t think so (10:12:22) abadger1999: I don't think so but there were deadlocks in the code previously. (10:12:27) cweyl: jobs should just queue up once the buildsys has reached it's limit, right? (10:12:30) stickster left the room ("Withdrawing to the lair..."). (10:12:31) abadger1999: with those gone, we can find new bugs :-) (10:12:40) ***cweyl thinks this is going to be an interesting stress test of plague :) (10:12:40) warren: deadlocks were signal based at first, then kernel bugs (10:12:53) c4chris: sure, the code had problems, but I think the system handles the load nicely (10:13:31) thl: okay (10:13:43) thl: let's think about it and discuss the other details in later meetins (10:13:50) thl: moving on (10:14:01) tibbs: I'm not disparaging the buildsys, just noting that if there are problems we should consider plan b. (10:14:02) c4chris: who open the thread on fel? (10:14:08) thl has changed the topic to: FESCo Meeting in progress -- Comaintainership (10:14:22) thl: c4chris, seems scop was interesed ;-) (10:14:36) c4chris: scop +1 :-) (10:14:41) tibbs: scop had to be away today.... (10:14:46) thl: well, I got no replys for my Comaintainership mail (10:14:53) c4chris: tibbs, I know... ;-) (10:15:02) ***bpepple meant to write something, but hasn't found time. (10:15:08) thl: so what do to now? ifnore it? (10:15:10) thl: ignore (10:15:14) cweyl: thl: I liked the idea of SIGs having comaintainership over their packages (10:15:23) c4chris: I mostly liked it. (10:15:25) tibbs: BTW, thl, the new schedule looks great. (10:15:42) c4chris: I think we need the package database to make things really work. (10:15:43) cweyl: it makes sense to me, they'd likely have both a vested interest in the packages and the knowledge of how to do it right (10:15:46) thl: tibbs, thx; I also hope it's a bit easier to keep it up2date and informative this way (10:15:59) cweyl: c4chris: +1 for package database (10:16:01) thl: cweyl, yes, that's one of the things we need (10:16:12) thl: s/cweyl/c4chris/ (10:16:16) warren: Technically this is no different from who was allowed to make changes in the past. Only difference is creating formalized groups. Similar vein to multiple owners. (10:16:41) warren: doesn't this count as another aspect where the package database would be handy? (10:17:10) c4chris: and apparently we'd need some support from the SCM (10:17:23) c4chris: warren, yes I think so (10:17:25) thl: warren, yes, it would be very handy (10:17:37) thl: but we need support from the SCM, too (10:17:49) warren: how so? (10:18:00) abadger1999: All you need is ACLs for groups, yes? (10:18:02) c4chris: to manage who can change the repo (10:18:20) warren: We generally plan on keeping checkin access almost wide open (10:18:26) thl: warren, read https://www.redhat.com/archives/fedora-extras-list/2006-July/msg00960.html (10:18:26) warren: ACL groups will happen though, yes. (10:18:53) thl: ACL will happen in CVS or the new SCM? (10:18:59) giallu left the room (quit: Read error: 110 (Connection timed out)). (10:19:10) warren: Ideally new SCM (10:19:14) thl: abadger1999, yes, I think all we need are ACLs for groups, yes (10:19:22) c4chris: ETA ? (10:19:35) thl: warren, yeah, ETA? (10:19:44) warren: The entire new SCM thing is post-FC6 (10:19:46) abadger1999: warren: Could I get someplace to put my bzr proof of concept? (10:20:05) warren: abadger1999, good question... we should discuss that during infrastructure meeting (10:20:11) c4chris: warren, and pre FC& ? (10:20:22) abadger1999: warren: I'll add it to the schedule there. (10:20:23) warren: c4chris, that is the hope. (10:20:26) c4chris: s/FC&/FC7/ (10:20:49) c4chris: k (10:20:55) thl: let's stop here (10:21:07) thl: maybe I get some more replys to the list for my mail ;-) (10:21:08) warren: I think people have the wrong idea here. (10:21:16) thl: warren, ? (10:21:23) thl: warren, did you actually read my mail? (10:21:32) warren: The important part of this is multiple owners, groups of owners, and subscription mapping between owners/groups and packages. (10:22:13) c4chris: warren, sure. But what is the wrong idea ? (10:22:50) warren: I guess it is the same idea, but different part is salient. (10:23:23) thl: warren, let's stop here and move on (10:23:26) warren: ok (10:23:33) thl: warren, maybe you can post your ideas to the list please? (10:23:46) thl has changed the topic to: FESCo Meeting in progress -- Use comps.xml properly (10:23:52) thl: c4chris ? (10:24:10) thl: "c4chris evaluating what packages need to be listed" (10:24:27) drfickle left the room (quit: "Please do not reply to this burrito"). (10:24:59) thl: c4chris lost :| (10:25:02) c4chris: My current thinking is to get most packages except perl- python- and -devel stuff (10:25:13) c4chris: (sorry, slow typing here) (10:25:29) c4chris: not sure about lib* stuff (10:25:38) c4chris: probably not (10:25:48) thl: c4chris, yeah, probably not (10:25:55) c4chris: Of course, people are free to add those they like (10:26:07) thl: c4chris, can you automate checks in you PackageStatus scripts? (10:26:09) c4chris: I'll just not complain if they are not listed (10:26:21) f13: if a package is a dep of something already in comps, don't list it (10:26:23) c4chris: thl, tes, that's the idea (10:26:37) tibbs: Well, not necessarily. (10:26:40) ***jwb is here now (10:26:41) c4chris: f13, yes, that's a good idea (10:27:07) c4chris: tibbs, sure, but don't have the script complain in this case (10:27:25) tibbs: OK, I see what you're saying. (10:27:55) thl: c4chris, can you work further on this? there is no real need to hurry (10:28:05) thl: c4chris, but we should have something in place before FC6 (10:28:13) c4chris: getting the dep tree from teh script might be a bit tricky though... (10:28:13) thl: e.g. mid-september? (10:28:38) c4chris: thl, yes, I plan to get things into shape over the next couple weeks. (10:28:45) thl: c4chris, k (10:29:00) thl: c4chris, is it ok for you if I move on? or do you want anything discussed? (10:29:28) c4chris: thl, fine with me. Please post ideas to the thread (10:29:36) thl has changed the topic to: FESCo Meeting in progress -- Stalled Package Reviews (10:29:39) thl: thx c4chris (10:29:39) osphy [n=randey] entered the room. (10:29:45) tibbs: Current draft is in: http://fedoraproject.org/wiki/JasonTibbitts/StalledReviewPolicy (10:30:12) thl: tibbs, okay for me (10:30:17) tibbs: I added the bit about FE-DEADREVIEW as suggested on extras-list but otherwise haven't revised it since my initial post. (10:30:18) thl: other opinions? (10:30:39) c4chris: I like it (10:30:39) bpepple: Looks alright to me. (10:30:57) tibbs: No complaints from me. (10:30:58) cweyl: I like it. especially the FE-DEADREVIEW part ;) (10:31:01) tibbs: (obviously) (10:31:25) tibbs: I can set up the FE-DEADREVIEW blocker. (10:31:29) thl: do we need to play the "+1" game or was that "I like it" enough for everyone? (10:31:49) tibbs: Did nobody at fedoraproject.org ever get set up? (10:31:50) bpepple: Should be fine. I didn't hear any complaints. (10:31:50) jwb: i like it (10:32:03) c4chris: no disagreements. All clear (10:32:03) thl: warren, nobody at fedoraproject.org ? (10:32:08) abadger1999: FE-DEADREVIEW was a nice addition. I don't see anything wrong with it. (10:32:21) thl: okay, "Stalled Package Reviews" accepted (10:32:23) warren: thl, oops, I forgot to follow through, I can do that today. (10:32:31) mharris_sun [n=mharris] entered the room. (10:32:34) thl: tibbs, can you integrate it into the wiki at the proper place? tia! (10:32:34) tibbs: I just need to know who to assign unassugned bugs back to. (10:32:38) warren: mharris_sun, sun? (10:32:49) tibbs: Since we can't put things back into NEW and there's no UNASSIGNED state. (10:32:51) mharris_sun is now known as mharris (10:32:56) thl: warren, no need to hurry (10:32:59) mharris: warren: better? ;) (10:33:14) thl: k, moving on (10:33:24) thl has changed the topic to: FESCo Meeting in progress -- Activate legacy in buildroots (10:33:25) tibbs: I'll just use the current phantom thl mailbox until nobody at fedoraproject.org gets set up. (10:33:37) thl: tibbs, I can create the bug, too (10:33:51) thl: tibbs, otherwise you'll get all the mails also because you are the reporter (10:34:17) tibbs: I have my own phantom mailbox, so it's no problem, but go ahead and create it if you like. (10:34:43) dgilmore: hey guys im here now (10:34:45) thl: tibbs, okay; remond me if I forget about it (10:34:59) thl: ohh, welcome dgilmore :) (10:35:06) xris [n=xris] entered the room. (10:35:34) thl: dgilmore, did you read https://www.redhat.com/archives/fedora-extras-list/2006-August/msg00091.html yet? (10:35:43) dgilmore: thl: no (10:35:49) dgilmore: let me read now (10:35:55) thl has changed the topic to: FESCo Meeting in progress -- problems with the new builders (10:36:17) dgilmore: thl: eithe elfutils is broken or not installed (10:36:30) thl: dgilmore, read the thread completely (10:36:31) dgilmore: so we need to install elfutils if it is not (10:36:40) thl: there is also a bug filed somewhere (10:36:47) thl: we should try to fix that soon (10:36:54) thl: dgilmore, are you still traveling? (10:37:12) dgilmore: thl: im eating lunch at the conference (10:37:27) dgilmore: network conectivity has been boorked (10:37:28) abadger1999: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=196930 (10:37:50) abadger1999: The bug. Details other problems with pre-FC5 buildroots as well. (10:38:06) thl: dgilmore, when do you get home again? (10:38:29) dgilmore: thl: tonight (10:38:51) thl: dgilmore, can you fix the debug-problem this weekend please? (10:39:09) tibbs: Does anyone know how the dependency coverage of the minimal buildroot was calculated? (10:39:34) warren: installing a chroot with yum (10:39:49) warren: If things are missing, just add them to the list and not worry about it. (10:39:50) tibbs: OK, that makes sense. (10:39:59) thl: tibbs, python probably should be added for FC3 and FC4 IMHO (10:40:34) tibbs: I kind of wish it were the other way, with python not being in FC5+ (10:40:55) thl: tibbs, I think there is a pyhton dep in rpm (or somewhere else) that pulls it in (10:40:57) tibbs: But with cached buildroots in mock now it's much less of an issue. (10:41:17) dgilmore: thl: i dont know if i can. it will need to be fixed in the buildsys-build package i dont know where it lives and where i need to put it so we access it (10:41:40) thl: dgilmore, skvidal should know (10:42:18) thl: I'm getting more and more annoyed of this "buildsys-build is somewhere in the web" scheme (10:42:32) thl: I'd prefer if it would be shipped together with mock :-/ (10:42:43) cweyl: thl: +1 (10:42:58) dgilmore: thl: python can easily be added if we add the macro for scop and require fedora-rpmdevtools (10:43:21) dgilmore: tibbs: we are not using cached buildroots (10:43:47) c4chris: dgilmore, I thought we would... (10:43:52) thl: hmmmm, so how to proceed (10:44:09) tibbs: I am at home, which is where it counts for me since I do so many builds. (10:44:11) thl: dgilmore, let's us two try to ping skvidal tomorrow to get this fixed (10:44:19) dgilmore: maybe we could and rebuild the cache with each core update (10:44:25) dgilmore: thl: sure (10:44:31) thl: everything okay if we add elf-utils and python to the minimal buildroots? (10:44:49) thl: everybody (10:44:57) dgilmore: im fine with it (10:44:58) warren: It doesn't hurt to add redundant things to the list. (10:45:01) c4chris: thl, +1 (10:45:01) tibbs: Can we just do it for the releases that need it? (10:45:02) warren: Just Do it (10:45:11) thl: tibbs, agreed (10:45:28) dgilmore: tibbs: yes we just need to maintain each distro seperatly (10:45:37) c4chris: tibbs, k (10:45:37) tibbs: Otherwise two years from now we'll argue about why it was put there. (10:45:46) tibbs: Just like most of the stuff we cut out last time. (10:45:49) thl: okay, then this seems to be settled for now ; let's move on (10:45:56) thl has changed the topic to: FESCo Meeting in progress -- Activate legacy in buildroots (10:46:00) thl: back to this one (10:46:17) thl: mschwendt didn't like this idea (10:46:22) thl: he posted to the list once (10:46:23) c4chris: what needs to happen? (10:46:42) tibbs: Legacy is dropping FC2- soon anyway; so don't we pretty much have this already? (10:46:43) thl: c4chris, well, we just need to say "We want to activate legacy in buildroots" (10:46:52) dgilmore: c4chris:make sure fc3 packages get built with legacy updates in the buildroot also (10:47:12) c4chris: thl, meaning we pull packages from legacy into the buildroot? (10:47:18) thl: c4chris, yes (10:47:39) dgilmore: mschwendt mostly didint like it because if a user does not have legacy installed then it might break something (10:47:39) c4chris: k (10:47:52) thl: here's the mail from mschwendt: https://www.redhat.com/archives/fedora-maintainers/2006-July/msg00005.html (10:47:59) thl: he has some points (10:48:06) dgilmore: I say if your still running FC3 like i am, then your are an idiot if you are not using legacy updates (10:48:23) thl: but I don#t think we have a choice (10:48:35) thl: we IMHOI must activate legacy in the builders for FE3 (10:48:40) thl: and FE4 soon (10:48:55) dgilmore: thl: I fully agree which is why i brought it up initially (10:48:56) thl: other opinions? (10:49:14) thl: or let's play the "+1" game again: (10:49:22) tibbs: I agree that this needs to be done. (Says someone with loads of FC3 still around.) (10:49:23) thl: +1 for activate legacy in buildroots (10:49:31) c4chris: sounds saner to me (10:49:33) dgilmore: +1 (10:49:35) c4chris: +1 (10:49:46) tibbs: +1 (10:50:32) warren: Just do it! (10:50:32) abadger1999: -1 (10:50:34) ***thl will wait another 15 seconds before he considers this accepted (10:50:37) thl: ohh (10:50:42) thl: abadger1999, --verbose please (10:50:44) abadger1999: Did anyone answer mschwendt's points? (10:51:01) abadger1999: Just to say -- here's why I think you're barking up the wrong tree? (10:51:05) thl: abadger1999, I started once, but got distracted (10:51:16) dgilmore: thl: as did i (10:51:40) c4chris: do we really want FE + FC versus FE + FL + FC ? (10:52:02) abadger1999: heh -- So itsounds like you have answers to his points but no one has put them in a public place where everyone can then understand the reasoning. (10:52:08) c4chris: there's supposed to be security fixes in FL (10:52:20) thl: c4chris, "do we really want to build FE for a FC4 that's unsupported without FL" (10:52:23) thl: ? (10:52:35) c4chris: thl, yes (10:52:50) tibbs: The breakage goes the other way, too. (10:52:50) cweyl: c4chris: is it really "FC + FC + FL"? I mean, e.g., FC-3 was "transferred" to FL... (10:53:14) tibbs: do we really want to build FE for an FC4 that's unsupported with FL? (10:53:17) c4chris: cweyl, F[CL] probably (10:53:25) thl: abadger1999, we probably should answer (10:53:32) thl: abadger1999, but there are so many mails on the list (10:53:47) thl: abadger1999, we can reply to each and everyone because we never get stuff done otherwise (10:54:04) cweyl: yah. I mean, if FL is responsible for updates to FC-3, then it seems like if we don't include them it's almost the same as just disabling the updates repo (10:54:37) dgilmore: cweyl: thats what i think (10:54:42) c4chris: cweyl, that's my impression too (10:55:10) thl: yeah, mine too (10:55:13) abadger1999: thl: I think the one point from his emails I want answered is who maintains FE-legacy? (10:55:24) bpepple: abadger1999: +1 (10:55:25) thl: abadger1999, there is no FE-legacy (10:55:29) abadger1999: Exactly. (10:55:42) thl: abadger1999, when we created the EOL policy (10:55:52) thl: most people wanted to avoid FE-legacy (10:56:05) dgilmore: abadger1999: we maintaine FE in legacy (10:56:06) thl: so the normal maintainers are responsible for their pacakges (10:56:09) abadger1999: So if FC-Legacy upgrades a library to fix a security hole and that breaks FE apps, who is going to fix it? (10:56:28) dgilmore: abadger1999: the maintainer (10:56:32) thl: abadger1999, the Extras maintainer should fix it (10:56:34) tibbs: This came up recently with some security fixes. One maintainer wasn't sure if he was responsible for fixing the FE3 version of his package. (10:56:37) dgilmore: if not them then the Fedora Security team (10:56:40) abadger1999: No. (10:57:06) tibbs: I told him that it's much preferred that he do it, but that if he insisted on not doing it then the security team would step in. (10:57:07) abadger1999: Maintainers have continuously said that they don't want indefinite responsibility for their packages. (10:57:12) dgilmore: abadger1999: yes the maintainer should. he should be strongly encouraged to do so (10:57:32) dgilmore: abadger1999: if he doesnt then i will do so (10:57:50) thl: abadger1999, this could be solved with a package database (10:57:55) dgilmore: I have already build 10 or so other peoples fe3 packages for security reasons (10:58:13) thl: abadger1999, then maintainer could hand over their packages for older dists to other people (10:58:14) cweyl: abadger1999: agreed. there needs to be a point at which a maintainer can legitimately say "that stuff is just too old. you now get to keep both parts" (10:58:28) thl: abadger1999, but I don#t cosider this a prople specific to FL (10:58:41) thl: abadger1999, I suppose there are already some maintainers that ignore FE4 also (10:58:54) thl: that's a general problem that needs to be solved (10:58:55) abadger1999: thl: Not really (package db). It doesn't assign responsibility, it only records who has volunteered. (10:59:22) abadger1999: thl: +1 to general problem. (10:59:30) tibbs: Do we have a document on maintainer responsibility? (10:59:31) dgilmore: abadger1999: there is no package DB but it needs to be one of the design goals of the package db (10:59:31) thl: well, we?re running late (10:59:34) cweyl: maybe something like "consider all extras branches for legacy distros orphaned unless explicitly owned? (e.g. via a 'maintained' file containing the email of the owner in the branch?)" (10:59:39) bpepple: tibbs: Not that I'm aware of. (10:59:43) ***cweyl is just brainstorming (10:59:47) thl: someone really need to bring this to the list again for further discussion (10:59:50) tibbs: If not, I'm happy to start one. (10:59:53) thl: any volunteers? (10:59:58) tibbs: Lots of argument potential there. (11:00:16) thl: tibbs, no, we have no defined "maintainer [19:59:29] < tibbs> | Do we have a document on maintainer responsibility? (11:00:26) thl: tibbs, no, we have no defined responsibilitys" (11:00:42) thl: sorry, cut'n'paste by touchpad error (11:00:58) tibbs: Is there agreement that we need to define some basic responsibilities? (11:01:00) thl: tibbs, but we need one soon (er or later) (11:01:04) thl: tibbs, yes (11:01:06) bpepple: tibbs: +1 (11:01:20) c4chris: tibbs, +1 (11:01:29) abadger1999: tibbs: +1 (11:01:46) tibbs: I'll start writing something up and will take it to the list for further discussion. (11:01:53) thl: tibbs, tia (11:01:58) tibbs: extras-list, right? Not fesco-list? (11:02:02) thl: tibbs, yes (11:02:11) thl: extras-list (11:02:18) tibbs: OK, I'll try to have something soon. (11:02:32) thl has changed the topic to: FESCo Meeting in progress -- CTRL-C problem (11:02:36) thl: no news yet afaik (11:02:39) thl: skipping (11:02:47) thl has changed the topic to: FESCo Meeting in progress -- IPv6 Support in Extras (11:02:52) thl: jwb, ? (11:03:00) thl: do we need to discuss this today? (11:03:00) jwb: i think it has mostly been covered (11:03:05) thl: It's late already (11:03:10) thl: jwb, mostly? (11:03:20) jwb: from a packaging standpoint, yes (11:03:27) jwb: we talked about it a few weeks ago (11:03:38) jwb: it's fine if we skip it today (11:03:46) thl: jwb, the packaging comittee looked into this, too (11:03:57) jwb: right, that's the discussion i'm referring to (11:04:02) thl: jwb, they created some guidelines for stuff like this iirc (11:04:20) jwb: yep (11:04:22) tibbs: Yes, we did, but there's still some question as to whether it's really our business to define something like that. (11:05:02) tibbs: Besides, the guidelines the packaging committee adopted is quite weak. (11:05:27) thl: well, let's skip it for today then (11:05:39) thl has changed the topic to: FESCo Meeting in progress -- Packaging Committee Report (11:05:41) thl: tibbs, ? (11:05:56) abadger1999: Nothing to report from the Packaging committee. (11:05:58) tibbs: Not a lot of folks around; nothing was able to be voted upon. (11:06:02) abadger1999: Not enough members present today. (11:06:06) thl: okay, moving on (11:06:15) thl has changed the topic to: FESCo Meeting in progress -- Weekly sponsorship nomination (11:06:19) thl: any new nominations? (11:06:40) ***thl will wait for about 30 seconds (11:06:40) ***noddy pipes up that he would like to be considered again for sponsor (11:06:40) warren: brb, bathroom (11:06:57) ixs: mhm (11:07:01) ixs: are new sponsors needed? (11:07:14) ***bpepple isn't sure. (11:07:27) cweyl: ixs: they're always needed :) (11:07:41) ixs: cweyl: ;D (11:08:00) ixs: ahh well, I'll go next week. ;D (11:08:14) tibbs: I wonder if c4chris couldn't be persuaded to generate some stats on FE-NEEDSPONSOR. (11:08:40) thl: noddy, we should probably wait some weeks before we discuss upgrading you to a sponsor again (11:08:43) thl: noddy, that okay? (11:08:46) c4chris: tibbs, there be some. What would you like to see? (11:08:58) tibbs: I did a lot of sponsorship work last week and it turned out rather well, I think. (11:09:22) tibbs: c4chris: Just a count over time, I guess. If we're trending upwards then we need more sponsors or more sponsorship activity. (11:09:31) noddy: thl : not a problem. I'll call back in the middle of Aug if you think that's long enough (11:09:47) warren: back (11:10:03) c4chris: tibbs, ok, I'll give this a shot (11:10:14) thl: k, so let's move on (11:10:18) tibbs: c4chris: I do see the NEEDSPONSOR section in PackageStatus now; thanks. (11:10:25) thl has changed the topic to: FESCo Meeting in progress -- review kmod's (11:10:32) thl: the easy one first (11:10:55) thl: sysprof (11:11:01) thl: +0,75 from me (11:11:12) c4chris: +1 (11:11:13) thl: it's not perfect (11:11:19) thl: but acceptable IMHO (11:11:47) thl: that all? (11:11:54) tibbs: +1 as well; I still wish someone would make the userspace part work with oprofile. (11:12:02) tibbs: but I don't think that should keep it out. (11:12:06) bpepple: +1 (11:12:09) abadger1999: +1 (11:12:18) tibbs: Note that scop voted +1 on the list. (11:12:26) thl: tibbs, seems that's at least considered by the authors (11:12:31) thl: okay, accepted (11:12:32) warren: Haven't been following kmod lately, will follow whatever thl and scop decides. (11:12:49) thl: warren, then you'll have a problem now (11:12:57) thl has changed the topic to: FESCo Meeting in progress -- review kmod's -- zaptel-kmod (11:13:01) thl: I stick to my -1 (11:13:07) thl: warren, scop voted +1 (11:13:20) thl: warren, https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177583#c41 for details (11:13:38) thl: jwb, jeremy, I'd be very interested in your opinions on this (11:14:18) tibbs: I'm +1; frankly I wish someone would just take it over and submit it upstream. (11:14:24) thl: the whole thing in short: upstream doesn't want to get the module included in the upstream kernel from kernel.org (11:14:42) thl: and we only agreed to have kmod in extras (11:14:52) jeremy: has anyone asked if they, similarly, don't want the module included in Fedora? (11:14:52) c4chris: Yea, the zero chance of it going upstream bugs me (11:14:54) ***nirik had hopes that openpbx would do somethng like that, but they seem stalled out these days. ;( (11:14:55) thl: if we make sure that the stuff we include get's upstream (11:15:22) nirik: jeremy: that statement in the bug is from a digium guy... (11:15:22) tibbs: sysprof will never get upstream either. (11:15:23) mjk_ is now known as mjk- (11:15:43) thl: tibbs, but the author at least works close with upstream (11:15:49) c4chris: tibbs, but sysprof is a temporary thing untill oprofile is used (11:16:01) thl: c4chris, agreed, too (11:16:02) tibbs: Who's to say the Digium folks don't work closely with upstream. (11:16:05) dgilmore: i use the module regullary (11:16:11) ixs: jeremy: the digium guy said something along: "we'd be glad to help in a reasonable way to get it into fedora" (11:16:20) nirik: "we'd like to see Asterisk and Zaptel in Fedora Extras as well, so we'll do anything that's within reason to help achieve that goal :-)" (11:16:22) dgilmore: but im not really sure if we want it in extras forever (11:16:38) tibbs: c4chris: My reading of the discussion is that the sysprof author has no interesting in making his code work with oprofile because it's too much work. (11:17:07) dgilmore: nirik: where ia am at cluecon has some openpbx guys here they nearly have zaptel s need removed (11:17:10) tibbs: He certainly hasn't made any progress towards that end in over a year. (11:17:19) ***jeremy really thinks that the answer for the zaptel stuff is some cluebat'ing about usptream (11:17:23) jeremy: maybe send dwmw2 to them ;-) (11:17:26) nirik: dgilmore: cool. ;) (11:17:42) c4chris: tibbs, hmmm (11:17:43) thl: jeremy, I had hoped dwmw2 would join the discussion on the bug ;-) (11:17:46) jwb: doesn't dwmw2 actually use this? (11:17:55) dgilmore: jwb: yeah he does (11:17:59) jwb: thought so (11:18:03) jwb: he's in .tw now though (11:18:08) nirik: dgilmore: then perhaps we should reject asterisk/zaptel and wait for openpbx. ;) (11:18:18) thl: jwb, dwmw2 opinions is also here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189400#c9 (11:18:34) dgilmore: i think im going to go +1 just beacuse i think it will be really useful. but i think longterm we need to presure for it to go upstream (11:18:39) jcollie[work]: don't hold your breath waiting for openpbx (11:18:44) jwb: thl, ok. i'll review those soon (11:18:59) dgilmore: nirik: they say an openpbx tarball will be a month or more away from a 0.2 release (11:19:10) thl: we probably really should shift this discussion to the list (11:19:43) thl: seems I'm the idiot that has to do this :-/ (11:19:46) c4chris: thl, yea I'm pretty undecided ATM (11:19:46) tibbs: dwmw2's opinion is interesting but unfortunately isn't selectively applicable to this module. (11:19:51) thl: I'll try to find time for it (11:19:53) abadger1999: This discussion could be generalized as "What are the criteria FESCo should be applying?" (11:20:10) nirik: thl: if you want I can post about it, since I was going to review the kmod... ? (11:20:16) c4chris: abadger1999, that would be useful too (11:20:18) tibbs: abadger1999: Exactly my opinion as voiced on the list. (11:20:21) thl: nirik, k, that would be helpfull (11:20:47) thl: abadger1999, c4chris, tibbs, we work on that after that discussion (11:20:51) nirik: sure, can do no problem... (11:20:55) thl: nirik, could you use fedora-devel please (11:21:05) thl: that seems the proper place for this discussion IMHO (11:21:05) nirik: not extras? ok... (11:21:09) c4chris: gotta run RSN... (11:21:36) thl has changed the topic to: FESCo Meeting in progress -- warren: CVS Branch Request Process (11:21:38) thl: warren ? (11:21:42) warren: A simple improvement to the CVS branching request process that requires no infrastructure changes is to append the bug number after package name. So it would like * FC-4 FC-5 cluestick 284327 This is only an improvement to this interim process until we can better automate the workflow in the package database. (11:21:57) warren: that is all (11:22:02) tibbs: +many (11:22:07) mmcgrath: +1 (11:22:11) c4chris: +1 (11:22:15) bpepple: +1 (11:22:23) abadger1999: +1 (11:22:24) thl: +1 (11:22:34) dgilmore: +1 (11:22:45) thl: k, that was easy ;-) (11:22:50) tibbs: Frankly I don't even think you needed to ask. (11:23:03) thl: tibbs, agreed (11:23:10) tibbs: warren: What about blocker bugs for branck requests? (11:23:14) thl: we don#t need to discuss each and every details (11:23:26) tibbs: NEEDBRANCH-FE4? (11:23:28) thl: just doing it until somebody yells often is okay for me often (11:23:29) warren: tibbs, doesn't handle re-requesting of new branches for things already previously branched (11:23:31) warren: oh (11:23:32) warren: hmm (11:23:50) warren: tibbs, I'd prefer this system, it is supposed to be temporary anyway (11:24:10) tibbs: It's your process to make as far as I'm concerned. (11:24:14) thl has changed the topic to: FESCo Meeting in progress -- abadger1999 , Future FESCo elections (11:24:17) thl: any news? (11:24:23) thl: or shall we just skip it? (11:24:27) abadger1999: Not enough time this week. (11:24:29) abadger1999: skip it. (11:24:31) maners [n=maners] entered the room. (11:24:35) warren: wah!/ (11:24:43) warren: spot made the CVS examples into an image (11:24:43) thl has changed the topic to: FESCo Meeting in progress -- c4chris , Package Database (11:24:45) warren: heh (11:24:57) thl: ohh, he left (11:25:04) thl: warren, seems c4chris is interesed in this (11:25:05) c4chris: not quite (11:25:11) thl: ohh :) (11:25:16) c4chris: but RSN (11:25:28) thl: c4chris, so how to get this thing rolling? (11:25:29) c4chris: can we discuss this next week ? (11:25:34) thl: c4chris, sure (11:25:38) tibbs: Lots of folks are interested in this, I think. (11:25:54) thl: yeah (11:25:55) c4chris: thl, thanks (11:26:07) thl has changed the topic to: FESCo Meeting in progress -- tibbs , Encourage Extras reviews (11:26:15) thl: tibbs, that's still on the schedule (11:26:19) ***c4chris goes afk now. Cheers and TTYL (11:26:20) thl: what do we do with it? (11:26:26) tibbs: Yes, low priority. (11:26:27) thl: c4chris, bye (11:26:46) tibbs: At this point not much is going to happen unless someone has new ideas. (11:26:58) tibbs: I think we're actually doing pretty good lately. (11:27:05) thl: tibbs, then I'll knock it of the schedule for now (11:27:06) ***bpepple agrees. (11:27:06) tibbs: Several new active reviewers and such. (11:27:14) thl: we can re-add it later at any time (11:27:22) tibbs: If we could get devimgrunduz sponsored I think we'd have another. (11:27:47) thl: also co-maintainership might help a bit in the longer term (at least if I get it workin as I'd like it) (11:28:10) abadger1999: tibbs: He's more interested in maintaining than reviewing. (11:28:10) tibbs: If co-maintainership opens up a second enterance to the process then I agree it would help. (11:28:14) bpepple: thl: Yeah, that would solve the problem with people only submitting one package. (11:28:25) thl has changed the topic to: FESCo Meeting in progress -- Free discussion around extras (11:28:26) abadger1999: But I'm close to sponsoring him. (11:28:34) tibbs: abadger1999: Lots of people are, but they still do the odd review. Every one helps. (11:28:43) thl: anything else that needs to be discussed? (11:29:22) abadger1999: Something of a side note -- mono may move to %{_libdir} for FC6. (11:29:34) tibbs: Wow. (11:29:46) tibbs: Who pushed that through? (11:30:03) abadger1999: We're trying not to do that (big change) but there may not be any other choice. (11:30:26) abadger1999: alexl is on vacation this week so no progress until next week. (11:30:38) tibbs: There shouldn't be any other choice. It's terrible the way it is. (11:30:49) ***thl still hopes we can get gutenprint into FC6 (11:30:55) abadger1999: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199790 (11:31:10) tibbs: thl: I think that's pushing it. (11:31:37) thl: tibbs, ? (11:31:54) tibbs: abadger1999: Heh. Yes, that bug kind of sums up the stupidity. (11:31:58) warren: thl, FC6 feature freeze was weeks ago (11:32:02) tibbs: thl: it's probably too late for gutenprint. (11:32:15) abadger1999: tibbs: Right-o *grin* (11:32:16) thl: warren, I know, I know (11:32:40) thl: we'll seems we can close the meeting (11:32:42) tibbs: But if it's packaged well enough couldn't it just slot right in? Or does it conflict with core in some way? (11:32:52) ***thl will close the meeting in 30 seconds (11:33:09) thl: warren, really, gutenprint will imnprove hardware support a lot (11:33:23) thl: the new version supports a lot of printers gimp-print doesn#tsupport (11:33:24) warren: thl, was this discussed on f-d-l? (11:33:28) ***thl will close the meeting in 15 seconds (11:33:32) thl: warren, nope (11:33:35) thl: once on testing (11:33:54) thl: warren, seems the biggest problems is: twaught lacks hardware to test (11:34:01) thl: (and of course time to work on it) (11:34:06) ***thl will close the meeting in 5 seconds (11:34:12) thl: -- MARK -- Meeting End }}} -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From toshio at tiki-lounge.com Sun Aug 6 20:31:37 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Sun, 06 Aug 2006 13:31:37 -0700 Subject: FESCo Election Policy **Draft** Message-ID: <1154896297.3765.78.camel@localhost> I've created a draft election policy for FESCo. The text is included below and on the wiki at: http://www.fedoraproject.org/wiki/ToshioKuratomi/ElectionDraft Please comment on this draft as FESCo will be discussing soon. We need time to improve the elections infrastructure before the next election so we need to start making decisions about this. There are several sections which may be controversial such as how long to wait between elections, who is eligible to be a candidate, and what voting model we will use in the future so be sure to read through the policy and give feedback about sections you think should be revised or are just downright wrong. I have not addressed the points raised by Michael Schwendt about what FESCo's purpose is in this document as that is a separate issue from elections. If someone would like to make that discussion into a policy draft so we can argue specifics it would greatly aid work in that area. -Toshio = FESCo Voting Proposal = FESCo elections help to keep the leadership of the project in touch with the packagers who make up the project. == Schedule == FESCo elections will be held approximately once a year, after an odd numbered Core release. Elections will start two weeks after the release is made public unless there is a lack of candidates (See Candidates below). If there are other elections scheduled at the same time the ballots will be offered at the same time. This is to help keep people involved with the project from having a constant stream of elections to remember to take part in. Elections will run for a period between one and two week. An attempt will be made to include two weekends in the open voting period so people can vote when they have free time. The elections will be announced in public lists. A reminder mail to those who are eligible to vote but haven't done so will be sent three days before the close of the election. == Seats on FESCo == There will be 13 seats on FESCo. == Candidates == Candidates may be any member of the cladone group in the Fedora Accounts System. This means anyone who has done the minimum to become a member of the Fedora Project can run for a seat on FESCo whether or not they are a contributer to the Fedora Extras portion of the project. Candidates must self nominate at least three days before the election opens by writing their information onto the wiki (Fedora account, email and irc nick, statement of past contributions and what they hope to accomplish while on the Fedora Project Board.) In order to hold an election a minimum number of candidates are necessary. This will be the number of open seats + 25%. If there are 13 seats available, there will need to be at least 16 candidates. If not enough candidates have signed up by the deadline, the election will be held back by one week for more candidates to appear. If there are still not enough candidates, the candidates who are present will be voted upon (or merely confirmed if there are less candidates than open seats.) If FESCo does not have the full number of seats filled at this point, please see Filling Vacant Seats below. Contributers who want to nominate themselves only if there are not enough people to fill the seats may put the same information on a separate section of the wiki page. If there are not enough candidates to complete the ballot, all the contributers listed in this section will be added to the ballot. No special considerations will be made for candidates elected through this process to resign their seats after the election. If you really do not want to be on FESCo, please withdraw your name from this list at least three days before the election so your name does not go on the ballot. == Voters == Voters may be any member of the cvsextras group in the Fedora Accounts System. This means everyone who has permission to maintain and approve packages for Extras will take part in voting. == Filling Vacant Seats == If FESCo does not have all its seats filled due to members leaving or other lack, the vacant seats will attempt to be filled by the following methods: 1. If there are runner-up candidates from the previous election that did not have the opportunity to be on FESCo, they will be offered a seat according to their rank in the voting. 2. If those candidates have been exhausted, FESCo will operate with less members until the next Core release. If this is an odd Core release, normal elections will ensue. If this is an even Core release, a special election will be held to fill the vacant seats. The candidates elected to those seats will serve a half-term (until the next normal election). Rules for declaring candidacy and voting will be the same for a special election as for a normal election. == Voting System == The voting model for the election aims to be simple, easy to audit, and fair in case someone resigns and their runner-up is selected. We have chosen a specific method of Range Voting to address these criteria. A voter receives a ballot listing all the candidates. For each candidate the voter assigns from ''{{{0}}}'' to ''{{{number of candidates}}}'' points. At the close of the election, the points for each candidate are tallied and the ones with the most points win a seat. For example, if we have 20 candidates running for 13 seats, the voter will be presented with a ballot where they can assign 0-20 points to each candidate. After voting, the 13 candidates with the most points will win the election. == Notes == There are no term limits imposed by this policy. If FESCo chooses to impose term limits for its internal positions (Chair, VP, etc) those should be specified in the FESCo by-laws rather than this document. The voting application needs to be enhanced in the following ways to support this policy: * Web based administration to create a new election. * Creation of a new election needs to trigger generation of a script that will interact with the accounts db and election db to send out a reminder to vote message three days before the close of the election. * The interface will show the voter ballots for all the elections that they can vote in. Other enhancements: * List upcoming elections. * List results for current and previous elections. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From skvidal at linux.duke.edu Sun Aug 6 23:16:32 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Sun, 06 Aug 2006 19:16:32 -0400 Subject: Any sign of a push? In-Reply-To: <44D62CD7.8070103@redhat.com> References: <1154777358.4220.21.camel@T7.Linux> <1154777592.3092.0.camel@cutter> <44D62CD7.8070103@redhat.com> Message-ID: <1154906192.1922.0.camel@cutter> On Sun, 2006-08-06 at 13:54 -0400, Warren Togami wrote: > seth vidal wrote: > > On Sat, 2006-08-05 at 12:29 +0100, Paul wrote: > >> Hi, > >> > >> I can't seem to see any FE pushes for the past couple of days. Is there > >> a problem with the email out or is me? > > > > we had a drive failure on the system to where the packages are pushed. > > I'm out of town on a little trip and I've not had a chance to check the > > push mechanism to make sure it will work. > > > > I'll see if I get to it tonight. > > > > Attempted a sign & push just now. Signing succeeded, but it failed > somewhere during sync with "Input/output error". Don't know if this is > more fallout from the disk failure, and I don't have access to the other > side of rsync to investigate further. > The perms aren't in place on the other side for the sync to work. I'll be fixing that this evening - I didn't get to it last night - had other things going on w/family. -sv From paul at all-the-johnsons.co.uk Mon Aug 7 00:20:45 2006 From: paul at all-the-johnsons.co.uk (Paul) Date: Mon, 07 Aug 2006 01:20:45 +0100 Subject: signing of packages built in mock Message-ID: <1154910045.4220.89.camel@T7.Linux> Hi, When I run mock over packages being reviewed and try to do a localinstall, I seem to be getting that the debuginfo packages and any additional packages (such as inchi which is generated from open-babel) created from a source are all not signed. Is this down to me or down to a problem with mock? TTFN Paul -- Wenn sie denken, dass die bildung teuer ist, versuchen sie ignoranz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From jkeating at redhat.com Mon Aug 7 00:43:14 2006 From: jkeating at redhat.com (Jesse Keating) Date: Sun, 6 Aug 2006 20:43:14 -0400 Subject: signing of packages built in mock In-Reply-To: <1154910045.4220.89.camel@T7.Linux> References: <1154910045.4220.89.camel@T7.Linux> Message-ID: <200608062043.17738.jkeating@redhat.com> On Sunday 06 August 2006 20:20, Paul wrote: > When I run mock over packages being reviewed and try to do a > localinstall, I seem to be getting that the debuginfo packages and any > additional packages (such as inchi which is generated from open-babel) > created from a source are all not signed. > > Is this down to me or down to a problem with mock? When you build, the binaries are not signed until you sign them. That's kind of the point of package signing... if you could rebuild a package and have it keep a signature, that's a bit worthless. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Axel.Thimm at ATrpms.net Mon Aug 7 10:58:08 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Mon, 7 Aug 2006 12:58:08 +0200 Subject: RFC: Split Package with Obsolete In-Reply-To: <44D633FF.3010700@leemhuis.info> References: <44D633FF.3010700@leemhuis.info> Message-ID: <20060807105808.GD27561@neu.nirvana> On Sun, Aug 06, 2006 at 08:25:03PM +0200, Thorsten Leemhuis wrote: > 2) add a this two lines to the new sub-pacakge: > Requires: %{name} = %{version}-%{release} > Obsoletes: mail-notification < 3.0-4 > (see attached patch for the full context). This way yum will install the > new subpackage because it obsoletes the old main-package *and* yum will > install the new main-package because it's a dep of the new subpackage. > This is somewhat hackish, but it's probably the most comfortable way for > the user. Sounds sane enough. I would add a comment above the "hack" to identify which upgrade paths are affected (e.g. all FC <= 5), so when FC5 get's dropped from FL one day (in 18 months with FC9?) one can remove it again. I think this is not really a hack, perhaps even the most elegant solution for such transparent splits. Maybe worth globally documenting somewhere in the wiki perhaps even the packaging guide? -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From buildsys at fedoraproject.org Mon Aug 7 11:56:23 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Mon, 7 Aug 2006 07:56:23 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-07 Message-ID: <20060807115623.6FF3D152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 48 915resolution-0.5.2-3.fc5 asymptote-1.12-1.fc5 cegui-0.4.1-10.fc5 emelfm2-0.1.8-1.fc5 fish-1.21.10-3.fc5 freeciv-2.0.8-5.fc5 ghex-2.8.2-1.fc5 gossip-0.14-2.fc5 htmldoc-1.8.27-1.fc5 ifm-5.1-4.fc5 iksemel-1.2-6.fc5 jthread-1.2.1-1.fc5 knemo-0.4.3-1.fc5 koffice-1.5.2-1.fc5 koffice-langpack-1.5.2-1.fc5 libpqxx-2.6.7-1.fc5 mod_nss-1.0.3-4.fc5 monotone-0.28-2.fc5 nagios-2.5-2.fc5 nip2-7.10.20-1.fc5 pengupop-2.1.0-1.fc5 perl-Apache-Session-Wrapper-0.31-1.fc5 perl-Class-Accessor-0.27-1.fc5 perl-Class-Factory-Util-1.6-2.fc5 perl-DateTime-Format-IBeat-0.161-3.fc5 perl-Devel-Cover-0.56-1.fc5 perl-GSSAPI-0.23-1.fc5 perl-Image-ExifTool-6.30-1.fc5 perl-Module-CoreList-2.06-1.fc5 perl-Object-InsideOut-1.48-1.fc5 perl-Smart-Comments-1.000002-2.fc5 perl-prefork-1.01-1.fc5 pure-ftpd-1.0.21-8.fc5 python-dns-1.4.0-1.fc5 scim-bridge-0.1.12-1.fc5.1 scim-fcitx-3.1.1-4.2.fc5 scim-input-pad-0.1.1-5.fc5 scim-skk-0.5.2-7.fc5.1 scim-tomoe-0.2.0-6.fc5.1 seamonkey-1.0.4-0.5.1.fc5 soundtouch-1.3.1-5.fc5 ss5-3.5.9-1 sylpheed-claws-plugins-2.4.0-1.fc5 torque-2.1.2-2.fc5 tre-0.7.4-4.fc5 uim-1.2.0-1.fc5 wine-docs-0.9.18-1.fc5 wormux-0.7.2-6.fc5 Packages built and released for Fedora Extras 4: 38 915resolution-0.5.2-3.fc4 aplus-fsf-4.20.2-9 asymptote-1.12-1.fc4 cegui-0.4.1-10.fc4 colorscheme-0.3-4.fc4 fish-1.21.10-3.fc4.1 freeciv-2.0.8-4.fc4 gobby-0.3.0-6.fc4 gtkmm24-2.6.14-1.fc4 htmldoc-1.8.27-1.fc4 ifm-5.1-3.fc4 iksemel-1.2-6.fc4 jthread-1.2.1-1.fc4 knemo-0.4.3-1.fc4 koffice-1.5.2-1.fc4 koffice-langpack-1.5.2-1.fc4 libpqxx-2.6.7-1.fc4 monotone-0.28-2.fc4 nagios-2.5-2.fc4 nip2-7.10.20-1.fc4 pengupop-2.1.0-1.fc4 perl-Apache-Session-Wrapper-0.31-1.fc4 perl-Class-Accessor-0.27-1.fc4 perl-Class-Factory-Util-1.6-2.fc4 perl-DateTime-Format-IBeat-0.161-3.fc4 perl-GSSAPI-0.23-1.fc4 perl-Image-ExifTool-6.30-1.fc4 perl-Module-CoreList-2.06-1.fc4 perl-Smart-Comments-1.000002-2.fc4.1 perl-prefork-1.01-1.fc4 python-dns-1.4.0-1.fc4 seamonkey-1.0.4-0.4.2.fc4 ss5-3.5.9-1 torque-2.1.2-2.fc4 tre-0.7.4-4.fc4 uim-1.2.0-1.fc4 wine-docs-0.9.18-1.fc4 wormux-0.7.2-6.fc4 Packages built and released for Fedora Extras 3: 7 fish-1.21.10-3.fc3.1 freeciv-2.0.8-3.fc3 ifm-5.1-3.fc3 nagios-2.5-2.fc3 perl-prefork-1.01-1.fc3 torque-2.1.2-2.fc3 wine-docs-0.9.18-1.fc3 Packages built and released for Fedora Extras development: 62 asymptote-1.12-1.fc6 cairomm-1.1.10-1.fc6 cegui-0.4.1-10.fc6 compface-1.5.2-3.fc6 cyrus-imapd-2.3.7-2.fc6 ddskk-12.2.0-8.fc6 emelfm2-0.1.8-1.fc6 fish-1.21.10-2.fc6 flim-1.14.8-1.fc6 freeciv-2.0.8-6.fc6 gauche-gl-0.4.1-5.fc6 ghdl-0.24-0.60svn.0.fc6 gossip-0.14-3.fc6 htmldoc-1.8.27-1.fc6 ifm-5.1-4.fc6 iksemel-1.2-6.fc6 jabberd-2.0-0.s11.10.fc6 javasvn-1.1.0-0.2.beta4.fc6 jthread-1.2.1-1.fc6 knemo-0.4.3-1.fc6 koffice-langpack-1.5.2-1.fc6 libapreq2-2.08-0.rc5.1.fc6 libnasl-2.2.8-1.fc6 mod_nss-1.0.3-4.fc6 monkey-bubble-0.4.0-1.fc6 monodevelop-0.11-16.fc6 monotone-0.28-2.fc6 nagios-2.5-2.fc6 pengupop-2.1.0-1.fc6 perl-Algorithm-Diff-1.1902-1.fc6 perl-Apache-Session-Wrapper-0.31-1.fc6 perl-Archive-Extract-0.11-1.fc6 perl-Class-Accessor-0.27-1.fc6 perl-Class-Factory-Util-1.6-2.fc6 perl-Config-Record-1.1.1-1 perl-DateTime-Format-HTTP-0.36-3.fc6 perl-DateTime-Format-IBeat-0.161-3.fc6 perl-DateTime-Format-Mail-0.30-3.fc6 perl-Devel-Cover-0.57-1.fc6 perl-File-Fetch-0.08-1.fc6 perl-GSSAPI-0.23-1.fc6 perl-Image-ExifTool-6.30-1.fc6 perl-Module-CoreList-2.06-1.fc6 perl-Module-Load-Conditional-0.10-1.fc6 perl-Object-InsideOut-1.48-1.fc6 perl-Smart-Comments-1.000002-2.fc6 perl-Time-Piece-1.09-1.fc6 perl-prefork-1.01-1.fc6 pitivi-0.10.1-1 pure-ftpd-1.0.21-8.fc6 pyicq-t-0.7-3.fc6 python-dns-1.4.0-1.fc6 qt4-qsa-1.2.1-16.fc6 rssowl-1.2.1-4.fc6 scim-input-pad-0.1.1-5.fc6 scons-0.96.1-2.fc6 sylpheed-claws-plugins-2.4.0-1.fc6 torque-2.1.2-2.fc6 tre-0.7.4-4.fc6 uim-1.2.0-1.fc6 wine-docs-0.9.18-1.fc6 wormux-0.7.2-6.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Mon Aug 7 11:56:52 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Mon, 7 Aug 2006 07:56:52 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-07 Message-ID: <20060807115652.9340E152169@buildsys.fedoraproject.org> aplus-fsf: Jochen AT herr-schmitt.de 4: 0:4.20.2-9 (FE4) 5: 0:4.20.2-5.fc5 (FE5) 6: 0:4.20.2-5.fc6 (FE6) azureus: green AT redhat.com 5: 0:2.4.0.3-0.20060529cvs_1.fc5 (FE5) 6: 0:2.4.0.3-0.20060328cvs_5.fc6 (FE6) banshee: caillon AT redhat.com 5: 0:0.10.9-1..fc5 (FE5) 6: 0:0.10.8-1 (FE6) camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) colorscheme: gauret AT free.fr 4: 0:0.3-4.fc4 (FE4) 5: 0:0.3-3.fc5 (FE5) 6: 0:0.3.91-2.fc6 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) digikam: mgarski AT post.pl 3: 0:0.8.2-2.fc3 (FE3) 4: 0:0.8.2-1.fc4 (FE4) 5: 0:0.8.2-1.fc5 (FE5) 6: 0:0.8.2-1.fc6 (FE6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) dogtail: zcerza AT redhat.com 5: 0:0.5.2-2.fc5 (FE5) 6: 0:0.5.2-1.fc6 (FC6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: liljencrantz AT gmail.com 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gaim-gaym: cweyl AT alumni.drew.edu 5: 0:0.96-3.fc5 (FE5) 6: 0:0.96-2.fc6 (FE6) gcdmaster: denis AT poolshark.org 4: 0:1.2.1-5.fc4 (FE4) 5: 0:1.2.1-4.fc5 (FE5) 6: 0:1.2.1-4.fc5 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) gtksourceview-sharp: paul AT all-the-johnsons.co.uk 5: 0:2.0-15.fc5 (FE5) 6: 0:2.0-14.fc6 (FE6) inkscape: denis AT poolshark.org 4: 0:0.44-3.fc4 (FE4) 5: 0:0.44-2.fc5 (FE5) 6: 0:0.44-2.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) koffice: andreas.bierfert AT lowlatency.de 5: 0:1.5.2-1.fc5 (FE5) 6: 0:1.5.1-2.fc6 (FE6) libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) libpqxx: andreas.bierfert AT lowlatency.de 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) lvm2: 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-16.fc6 (FC6) mozilla: 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.1-2.fc5 (FE5) 6: 0:1.0.1-1.fc5 (FE6) quagga: 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) seamonkey: kengert AT redhat.com 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) smart: Axel.Thimm AT ATrpms.net 5: 0:0.42-34.fc5 (FE5) 6: 0:0.41-31.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.4-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) From bugs.michael at gmx.net Mon Aug 7 12:01:12 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Mon, 7 Aug 2006 14:01:12 +0200 Subject: Rebuild policy needed Message-ID: <20060807140112.27619a4a.bugs.michael@gmx.net> The push-script has caught this: > New packages in PUSHED /srv/rpmbuild/repodir/fedora-development-extras/rssowl/1.2.1-4.fc6, clearing flag This means that an older build of the same package has been signed and published before (a file "PUSHED" in the build job results directory of a package in the needsign tree), and that the results of the new build job have been found in the old directory which has not expired yet. When the package was modified without bumping release (or if build dependencies have changed meanwhile), some users may already have updated to the previous binaries. They won't ever see changes in the new builds unless they reinstall the package(s). That is bad. Note that ever since, the various push scripts have never overwritten old packages in the master repository. The "copy" and "move" functions do not overwrite existing destination files, which is good. So, we have kind of a partially undefined situation here, since a version-bump-less rebuild may introduce new sub-packages or be made for more/less architectures. A rebuild may also be accidental, and remember, even if EVR has not changed, it is impossible to kill/withdraw succeeded build jobs with plague-client. We need to define what is done with a version-bump-less rebuild of a package that has been published before. * Overwriting existing rpms in the published tree is bad. * Rule of thumb: If you want changes to enter your packages, bump Release! * Detecting and ignoring rebuilds is not trivial [*] if the previous build job results directory is gone already. (it would need something like looking for existing destination files, then ignoring the entire results of a build job before any rpms would be copied/moved/linked) [*] doable, but worth the effort? * At the level of the push-script, we have no way to inform a packager about rejected/ignored build results. * The build report is misleading if it mentions a package, which has been ignored partially or completely, because an older build of it exists in the repository already. The package database could help with this and make the build server reject rebuilds of previously built package releases. Meanwhile I say: Avoid version-bump-less rebuilds like the plague! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From buildsys at fedoraproject.org Mon Aug 7 12:18:14 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Mon, 07 Aug 2006 12:18:14 -0000 Subject: (1/2) Summary - Broken dependencies in Fedora Extras - 2006-08-07 Message-ID: <20060807121814.11614.39303@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (123 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (123 days) koffice-langpack-af - 1.5.2-1.fc6.noarch koffice-langpack-af - 1.5.2-1.fc6.noarch koffice-langpack-af - 1.5.2-1.fc6.noarch koffice-langpack-ar - 1.5.2-1.fc6.noarch koffice-langpack-ar - 1.5.2-1.fc6.noarch koffice-langpack-ar - 1.5.2-1.fc6.noarch koffice-langpack-bg - 1.5.2-1.fc6.noarch koffice-langpack-bg - 1.5.2-1.fc6.noarch koffice-langpack-bg - 1.5.2-1.fc6.noarch koffice-langpack-br - 1.5.2-1.fc6.noarch koffice-langpack-br - 1.5.2-1.fc6.noarch koffice-langpack-br - 1.5.2-1.fc6.noarch koffice-langpack-bs - 1.5.2-1.fc6.noarch koffice-langpack-bs - 1.5.2-1.fc6.noarch koffice-langpack-bs - 1.5.2-1.fc6.noarch koffice-langpack-ca - 1.5.2-1.fc6.noarch koffice-langpack-ca - 1.5.2-1.fc6.noarch koffice-langpack-ca - 1.5.2-1.fc6.noarch koffice-langpack-cs - 1.5.2-1.fc6.noarch koffice-langpack-cs - 1.5.2-1.fc6.noarch koffice-langpack-cs - 1.5.2-1.fc6.noarch koffice-langpack-cy - 1.5.2-1.fc6.noarch koffice-langpack-cy - 1.5.2-1.fc6.noarch koffice-langpack-cy - 1.5.2-1.fc6.noarch koffice-langpack-da - 1.5.2-1.fc6.noarch koffice-langpack-da - 1.5.2-1.fc6.noarch koffice-langpack-da - 1.5.2-1.fc6.noarch koffice-langpack-de - 1.5.2-1.fc6.noarch koffice-langpack-de - 1.5.2-1.fc6.noarch koffice-langpack-de - 1.5.2-1.fc6.noarch koffice-langpack-el - 1.5.2-1.fc6.noarch koffice-langpack-el - 1.5.2-1.fc6.noarch koffice-langpack-el - 1.5.2-1.fc6.noarch koffice-langpack-en_GB - 1.5.2-1.fc6.noarch koffice-langpack-en_GB - 1.5.2-1.fc6.noarch koffice-langpack-en_GB - 1.5.2-1.fc6.noarch koffice-langpack-eo - 1.5.2-1.fc6.noarch koffice-langpack-eo - 1.5.2-1.fc6.noarch koffice-langpack-eo - 1.5.2-1.fc6.noarch koffice-langpack-es - 1.5.2-1.fc6.noarch koffice-langpack-es - 1.5.2-1.fc6.noarch koffice-langpack-es - 1.5.2-1.fc6.noarch koffice-langpack-et - 1.5.2-1.fc6.noarch koffice-langpack-et - 1.5.2-1.fc6.noarch koffice-langpack-et - 1.5.2-1.fc6.noarch koffice-langpack-eu - 1.5.2-1.fc6.noarch koffice-langpack-eu - 1.5.2-1.fc6.noarch koffice-langpack-eu - 1.5.2-1.fc6.noarch koffice-langpack-fi - 1.5.2-1.fc6.noarch koffice-langpack-fi - 1.5.2-1.fc6.noarch koffice-langpack-fi - 1.5.2-1.fc6.noarch koffice-langpack-fr - 1.5.2-1.fc6.noarch koffice-langpack-fr - 1.5.2-1.fc6.noarch koffice-langpack-fr - 1.5.2-1.fc6.noarch koffice-langpack-ga - 1.5.2-1.fc6.noarch koffice-langpack-ga - 1.5.2-1.fc6.noarch koffice-langpack-ga - 1.5.2-1.fc6.noarch koffice-langpack-he - 1.5.2-1.fc6.noarch koffice-langpack-he - 1.5.2-1.fc6.noarch koffice-langpack-he - 1.5.2-1.fc6.noarch koffice-langpack-hi - 1.5.2-1.fc6.noarch koffice-langpack-hi - 1.5.2-1.fc6.noarch koffice-langpack-hi - 1.5.2-1.fc6.noarch koffice-langpack-hu - 1.5.2-1.fc6.noarch koffice-langpack-hu - 1.5.2-1.fc6.noarch koffice-langpack-hu - 1.5.2-1.fc6.noarch koffice-langpack-is - 1.5.2-1.fc6.noarch koffice-langpack-is - 1.5.2-1.fc6.noarch koffice-langpack-is - 1.5.2-1.fc6.noarch koffice-langpack-it - 1.5.2-1.fc6.noarch koffice-langpack-it - 1.5.2-1.fc6.noarch koffice-langpack-it - 1.5.2-1.fc6.noarch koffice-langpack-ja - 1.5.2-1.fc6.noarch koffice-langpack-ja - 1.5.2-1.fc6.noarch koffice-langpack-ja - 1.5.2-1.fc6.noarch koffice-langpack-lt - 1.5.2-1.fc6.noarch koffice-langpack-lt - 1.5.2-1.fc6.noarch koffice-langpack-lt - 1.5.2-1.fc6.noarch koffice-langpack-mk - 1.5.2-1.fc6.noarch koffice-langpack-mk - 1.5.2-1.fc6.noarch koffice-langpack-mk - 1.5.2-1.fc6.noarch koffice-langpack-ms - 1.5.2-1.fc6.noarch koffice-langpack-ms - 1.5.2-1.fc6.noarch koffice-langpack-ms - 1.5.2-1.fc6.noarch koffice-langpack-nb - 1.5.2-1.fc6.noarch koffice-langpack-nb - 1.5.2-1.fc6.noarch koffice-langpack-nb - 1.5.2-1.fc6.noarch koffice-langpack-nl - 1.5.2-1.fc6.noarch koffice-langpack-nl - 1.5.2-1.fc6.noarch koffice-langpack-nl - 1.5.2-1.fc6.noarch koffice-langpack-nn - 1.5.2-1.fc6.noarch koffice-langpack-nn - 1.5.2-1.fc6.noarch koffice-langpack-nn - 1.5.2-1.fc6.noarch koffice-langpack-pl - 1.5.2-1.fc6.noarch koffice-langpack-pl - 1.5.2-1.fc6.noarch koffice-langpack-pl - 1.5.2-1.fc6.noarch koffice-langpack-pt - 1.5.2-1.fc6.noarch koffice-langpack-pt - 1.5.2-1.fc6.noarch koffice-langpack-pt - 1.5.2-1.fc6.noarch koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch koffice-langpack-ro - 1.5.2-1.fc6.noarch koffice-langpack-ro - 1.5.2-1.fc6.noarch koffice-langpack-ro - 1.5.2-1.fc6.noarch koffice-langpack-ru - 1.5.2-1.fc6.noarch koffice-langpack-ru - 1.5.2-1.fc6.noarch koffice-langpack-ru - 1.5.2-1.fc6.noarch koffice-langpack-se - 1.5.2-1.fc6.noarch koffice-langpack-se - 1.5.2-1.fc6.noarch koffice-langpack-se - 1.5.2-1.fc6.noarch koffice-langpack-sk - 1.5.2-1.fc6.noarch koffice-langpack-sk - 1.5.2-1.fc6.noarch koffice-langpack-sk - 1.5.2-1.fc6.noarch koffice-langpack-sl - 1.5.2-1.fc6.noarch koffice-langpack-sl - 1.5.2-1.fc6.noarch koffice-langpack-sl - 1.5.2-1.fc6.noarch koffice-langpack-sr - 1.5.2-1.fc6.noarch koffice-langpack-sr - 1.5.2-1.fc6.noarch koffice-langpack-sr - 1.5.2-1.fc6.noarch koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch koffice-langpack-sv - 1.5.2-1.fc6.noarch koffice-langpack-sv - 1.5.2-1.fc6.noarch koffice-langpack-sv - 1.5.2-1.fc6.noarch koffice-langpack-ta - 1.5.2-1.fc6.noarch koffice-langpack-ta - 1.5.2-1.fc6.noarch koffice-langpack-ta - 1.5.2-1.fc6.noarch koffice-langpack-tg - 1.5.2-1.fc6.noarch koffice-langpack-tg - 1.5.2-1.fc6.noarch koffice-langpack-tg - 1.5.2-1.fc6.noarch koffice-langpack-tr - 1.5.2-1.fc6.noarch koffice-langpack-tr - 1.5.2-1.fc6.noarch koffice-langpack-tr - 1.5.2-1.fc6.noarch koffice-langpack-uk - 1.5.2-1.fc6.noarch koffice-langpack-uk - 1.5.2-1.fc6.noarch koffice-langpack-uk - 1.5.2-1.fc6.noarch koffice-langpack-uz - 1.5.2-1.fc6.noarch koffice-langpack-uz - 1.5.2-1.fc6.noarch koffice-langpack-uz - 1.5.2-1.fc6.noarch koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch libopensync-plugin-evolution2 - 0.18-6.fc5.i386 libopensync-plugin-evolution2 - 0.18-6.fc5.ppc libopensync-plugin-evolution2 - 0.18-6.fc5.x86_64 wine-core - 0.9.17-1.fc6.i386 (12 days) bdpepple AT ameritech.net contact-lookup-applet - 0.14-3.fc6.i386 contact-lookup-applet - 0.14-3.fc6.ppc contact-lookup-applet - 0.14-3.fc6.x86_64 byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (19 days) gaim-guifications - 2.12-3.fc5.ppc (19 days) gaim-guifications - 2.12-3.fc5.x86_64 (19 days) caillon AT redhat.com banshee - 0.10.8-1.i386 (19 days) banshee - 0.10.8-1.ppc (19 days) banshee - 0.10.8-1.x86_64 (19 days) libipoddevice - 0.4.5-1.fc6.i386 (18 days) libipoddevice - 0.4.5-1.fc6.ppc (18 days) libipoddevice - 0.4.5-1.fc6.x86_64 (18 days) cweyl AT alumni.drew.edu gaim-gaym - 0.96-2.fc6.i386 (19 days) gaim-gaym - 0.96-2.fc6.ppc (19 days) gaim-gaym - 0.96-2.fc6.x86_64 (19 days) dennis AT ausil.us knetworkmanager - 0.1-0.3.svn20060625.fc6.i386 (18 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.ppc (18 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.x86_64 (18 days) fedora AT leemhuis.info gsynaptics - 0.9.8-1.fc6.ppc (19 days) gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (11 days) amarok - 1.4.1-3.fc6.ppc (11 days) showimg-pgsql - 0.9.5-7.fc4.i386 showimg-pgsql - 0.9.5-7.fc4.ppc showimg-pgsql - 0.9.5-7.fc4.x86_64 showimg-pgsql - 0.9.5-7.fc5.i386 showimg-pgsql - 0.9.5-7.fc5.ppc showimg-pgsql - 0.9.5-7.fc5.x86_64 green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.i386 (12 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (12 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.x86_64 (12 days) jogl - 1.1.1-14.fc5.ppc (15 days) ivazquez AT ivazquez.net deskbar-applet - 2.14.1.1-1.fc6.i386 deskbar-applet - 2.14.1.1-1.fc6.ppc deskbar-applet - 2.14.1.1-1.fc6.x86_64 gnome-applet-music - 0.9.0-1.fc6.i386 (19 days) gnome-applet-music - 0.9.0-1.fc6.ppc (19 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (19 days) nautilus-search-tool - 0.2-1.fc5.i386 (19 days) nautilus-search-tool - 0.2-1.fc5.ppc (19 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (19 days) jkeating AT redhat.com contacts - 0.1-1.i386 contacts - 0.1-1.ppc contacts - 0.1-1.x86_64 lmacken AT redhat.com python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.i386 (23 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.ppc (23 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.x86_64 (23 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.i386 (23 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.ppc (23 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.x86_64 (23 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (19 days) gfontview - 0.5.0-5.fc5.ppc (19 days) gfontview - 0.5.0-5.fc5.x86_64 (19 days) gtkhtml36 - 3.6.2-5.fc6.i386 (19 days) gtkhtml36 - 3.6.2-5.fc6.ppc (19 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (19 days) libvisual-plugins - 0.2.0-3.fc5.i386 (19 days) libvisual-plugins - 0.2.0-3.fc5.i386 (19 days) libvisual-plugins - 0.2.0-3.fc5.ppc (19 days) libvisual-plugins - 0.2.0-3.fc5.ppc (19 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (19 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (19 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (82 days) syck-php - 0.55-7.fc5.i386 (82 days) syck-php - 0.55-7.fc5.ppc (82 days) syck-php - 0.55-7.fc5.ppc (82 days) syck-php - 0.55-7.fc5.x86_64 (82 days) syck-php - 0.55-7.fc5.x86_64 (82 days) pertusus AT free.fr dap-hdf4_handler - 3.6.0-3.fc5.i386 (15 days) dap-hdf4_handler - 3.6.0-3.fc5.ppc (15 days) dap-hdf4_handler - 3.6.0-3.fc5.x86_64 (15 days) rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (19 days) libibverbs - 1.0.3-1.fc6.ppc (19 days) libibverbs - 1.0.3-1.fc6.x86_64 (19 days) libibverbs-utils - 1.0.3-1.fc6.i386 (19 days) libibverbs-utils - 1.0.3-1.fc6.ppc (19 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (19 days) thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (19 days) directfb - 0.9.24-5.fc5.ppc (19 days) directfb - 0.9.24-5.fc5.x86_64 (19 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.i386 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc5.i386 requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) python-ruledispatch-0.5a0-0.1.svnr2115.fc5.x86_64 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc5.x86_64 requires libpqxx-2.6.6.so()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.ppc requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc5.ppc requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.i386 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc4.i386 requires libpqxx-2.6.6.so Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.x86_64 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc4.x86_64 requires libpqxx-2.6.6.so()(64bit) Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.ppc requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc4.ppc requires libpqxx-2.6.6.so Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.i386 requires libgcj.so.7 banshee-0.10.8-1.i386 requires libnautilus-burn.so.3 banshee-0.10.8-1.i386 requires libdbus-1.so.2 contact-lookup-applet-0.14-3.fc6.i386 requires libebook-1.2.so.5 contacts-0.1-1.i386 requires libebook-1.2.so.5 dap-hdf4_handler-3.6.0-3.fc5.i386 requires libdap.so.4 deskbar-applet-2.14.1.1-1.fc6.i386 requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.i386 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-qt-1.so.1 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libipoddevice-0.4.5-1.fc6.i386 requires libdbus-1.so.2 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- azureus-2.4.0.3-0.20060328cvs_5.fc6.x86_64 requires libgcj.so.7()(64bit) banshee-0.10.8-1.x86_64 requires libnautilus-burn.so.3()(64bit) banshee-0.10.8-1.x86_64 requires libdbus-1.so.2()(64bit) contact-lookup-applet-0.14-3.fc6.x86_64 requires libebook-1.2.so.5()(64bit) contacts-0.1-1.x86_64 requires libebook-1.2.so.5()(64bit) dap-hdf4_handler-3.6.0-3.fc5.x86_64 requires libdap.so.4()(64bit) deskbar-applet-2.14.1.1-1.fc6.x86_64 requires libebook-1.2.so.5()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-gaym-0.96-2.fc6.x86_64 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-qt-1.so.1()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-1.so.2()(64bit) koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libipoddevice-0.4.5-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libedata-cal-1.2.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libebook-1.2.so.5()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.17-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 banshee-0.10.8-1.ppc requires libnautilus-burn.so.3 banshee-0.10.8-1.ppc requires libdbus-1.so.2 contact-lookup-applet-0.14-3.fc6.ppc requires libebook-1.2.so.5 contacts-0.1-1.ppc requires libebook-1.2.so.5 dap-hdf4_handler-3.6.0-3.fc5.ppc requires libdap.so.4 deskbar-applet-2.14.1.1-1.fc6.ppc requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.ppc requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gsynaptics-0.9.8-1.fc6.ppc requires synaptics gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-qt-1.so.1 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libipoddevice-0.4.5-1.fc6.ppc requires libdbus-1.so.2 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 ====================================================================== New report for: andreas.bierfert AT lowlatency.de package: koffice-langpack-it - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-bg - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-uz - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-fr - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-nn - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-se - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ta - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ru - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-tg - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ro - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-cs - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-is - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ar - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-en_GB - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ga - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ja - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-he - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-lt - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-el - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-es - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-da - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-br - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sl - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sr - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-af - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-hi - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-uk - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-eu - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ms - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-tr - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ca - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: libopensync-plugin-evolution2 - 0.18-6.fc5.i386 from fedora-extras-development-i386 unresolved deps: libedata-cal-1.2.so.1 libebook-1.2.so.5 package: koffice-langpack-nl - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-cy - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-mk - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-pl - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-hu - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-nb - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-fi - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-bs - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-de - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-et - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sv - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-pt - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sk - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-eo - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch from fedora-extras-development-i386 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ta - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-fi - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ar - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ru - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 From buildsys at fedoraproject.org Mon Aug 7 12:18:14 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Mon, 07 Aug 2006 12:18:14 -0000 Subject: (2/2) Summary - Broken dependencies in Fedora Extras - 2006-08-07 Message-ID: <20060807121814.11614.8930@extras64.linux.duke.edu> package: koffice-langpack-pt - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ms - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-it - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-he - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sr - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-br - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-tr - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-hi - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-af - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sv - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-nb - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-es - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-pl - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-nn - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-se - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-cy - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-bs - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: libopensync-plugin-evolution2 - 0.18-6.fc5.x86_64 from fedora-extras-development-x86_64 unresolved deps: libedata-cal-1.2.so.1()(64bit) libebook-1.2.so.5()(64bit) package: koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-is - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-eu - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-bg - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-hu - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-nl - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-et - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-lt - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ga - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-da - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-cs - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sl - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ro - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-uz - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-fr - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-de - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-tg - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-mk - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-uk - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-el - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-en_GB - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ja - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-eo - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sk - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ca - 1.5.2-1.fc6.noarch from fedora-extras-development-x86_64 unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-uz - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-fr - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ja - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ga - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-en_GB - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-es - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-nn - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-da - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-nl - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-bg - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-lt - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ar - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ta - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-bs - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-he - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ca - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-af - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-nb - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-hu - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-eu - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ro - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-el - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sl - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ru - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-is - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-fi - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-et - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-eo - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-it - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-pl - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-se - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sr - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-pt - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sk - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sv - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: libopensync-plugin-evolution2 - 0.18-6.fc5.ppc from fedora-extras-development-ppc unresolved deps: libedata-cal-1.2.so.1 libebook-1.2.so.5 package: koffice-langpack-tg - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-hi - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-de - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-cy - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-mk - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-uk - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-br - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-tr - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-ms - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-cs - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 package: koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch from fedora-extras-development-ppc unresolved deps: koffice-core >= 0:1.5.2 ====================================================================== New report for: dennis AT ausil.us package: knetworkmanager - 0.1-0.3.svn20060625.fc6.i386 from fedora-extras-development-i386 unresolved deps: libdbus-1.so.2 libdbus-qt-1.so.1 package: knetworkmanager - 0.1-0.3.svn20060625.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libdbus-qt-1.so.1()(64bit) libdbus-1.so.2()(64bit) package: knetworkmanager - 0.1-0.3.svn20060625.fc6.ppc from fedora-extras-development-ppc unresolved deps: libdbus-1.so.2 libdbus-qt-1.so.1 ====================================================================== New report for: jkeating AT redhat.com package: contacts - 0.1-1.i386 from fedora-extras-development-i386 unresolved deps: libebook-1.2.so.5 package: contacts - 0.1-1.x86_64 from fedora-extras-development-x86_64 unresolved deps: libebook-1.2.so.5()(64bit) package: contacts - 0.1-1.ppc from fedora-extras-development-ppc unresolved deps: libebook-1.2.so.5 ====================================================================== New report for: pertusus AT free.fr package: dap-hdf4_handler - 3.6.0-3.fc5.i386 from fedora-extras-development-i386 unresolved deps: libdap.so.4 package: dap-hdf4_handler - 3.6.0-3.fc5.x86_64 from fedora-extras-development-x86_64 unresolved deps: libdap.so.4()(64bit) package: dap-hdf4_handler - 3.6.0-3.fc5.ppc from fedora-extras-development-ppc unresolved deps: libdap.so.4 ====================================================================== New report for: caillon AT redhat.com package: libipoddevice - 0.4.5-1.fc6.i386 from fedora-extras-development-i386 unresolved deps: libdbus-1.so.2 package: libipoddevice - 0.4.5-1.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libdbus-1.so.2()(64bit) package: libipoddevice - 0.4.5-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: libdbus-1.so.2 ====================================================================== New report for: green AT redhat.com package: jogl - 1.1.1-14.fc5.ppc from fedora-extras-development-ppc unresolved deps: libgcj.so.7 ====================================================================== New report for: ivazquez AT ivazquez.net package: deskbar-applet - 2.14.1.1-1.fc6.i386 from fedora-extras-development-i386 unresolved deps: libebook-1.2.so.5 package: deskbar-applet - 2.14.1.1-1.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libebook-1.2.so.5()(64bit) package: deskbar-applet - 2.14.1.1-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: libebook-1.2.so.5 ====================================================================== New report for: bdpepple AT ameritech.net package: contact-lookup-applet - 0.14-3.fc6.i386 from fedora-extras-development-i386 unresolved deps: libebook-1.2.so.5 package: contact-lookup-applet - 0.14-3.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libebook-1.2.so.5()(64bit) package: contact-lookup-applet - 0.14-3.fc6.ppc from fedora-extras-development-ppc unresolved deps: libebook-1.2.so.5 From paul at all-the-johnsons.co.uk Mon Aug 7 22:14:52 2006 From: paul at all-the-johnsons.co.uk (Paul) Date: Mon, 07 Aug 2006 23:14:52 +0100 Subject: Warning to those using boo on rawhide Message-ID: <1154988892.20827.3.camel@T7.Linux> Hi, I've noticed that gtksourceview now includes a boo.lang file which conflicts with boo-0.7.6.2237-7 (does not affect FC5 users currently). I have just uploaded boo-0.7.6.2237-8 for the next extras push, which will probably mean that you'll need to exclude gtksourceview on your next update. TTFN Paul -- Wenn sie denken, dass die bildung teuer ist, versuchen sie ignoranz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Axel.Thimm at ATrpms.net Tue Aug 8 05:27:59 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Tue, 8 Aug 2006 07:27:59 +0200 Subject: RFC: Split Package with Obsolete In-Reply-To: <20060807105808.GD27561@neu.nirvana> References: <44D633FF.3010700@leemhuis.info> <20060807105808.GD27561@neu.nirvana> Message-ID: <20060808052759.GB1475@neu.nirvana> On Mon, Aug 07, 2006 at 12:58:08PM +0200, Axel Thimm wrote: > On Sun, Aug 06, 2006 at 08:25:03PM +0200, Thorsten Leemhuis wrote: > > 2) add a this two lines to the new sub-pacakge: > > Requires: %{name} = %{version}-%{release} > > Obsoletes: mail-notification < 3.0-4 I just stumbled on another occasion about an rpmlint "error" which would hit this idiom just the same: E: ... obsolete-not-provided I think this qualifies in general at the very most as a warning. Some Obsoletes: like in this case are not implying that this package provides the required functionality. > > (see attached patch for the full context). This way yum will install the > > new subpackage because it obsoletes the old main-package *and* yum will > > install the new main-package because it's a dep of the new subpackage. > > > This is somewhat hackish, but it's probably the most comfortable way for > > the user. > > Sounds sane enough. I would add a comment above the "hack" to identify > which upgrade paths are affected (e.g. all FC <= 5), so when FC5 get's > dropped from FL one day (in 18 months with FC9?) one can remove it > again. > > I think this is not really a hack, perhaps even the most elegant > solution for such transparent splits. Maybe worth globally documenting > somewhere in the wiki perhaps even the packaging guide? -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From peter at newton.cx Tue Aug 8 05:36:43 2006 From: peter at newton.cx (Peter Williams) Date: Tue, 8 Aug 2006 01:36:43 -0400 (EDT) Subject: 'straw' package appears to be orphaned Message-ID: <42578.140.247.244.211.1155015403.squirrel@www.newton.cx> As per https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186731, the Fedora Extras package of the Straw news reader is extremely old. The maintainer, Colin Charles has seemed nonresponsive for about five months, at least. I'm not sure what's going on since his blog is updated quite regularly. I'm not familiar with the organization of Fedora Extras, but can this package be added the orphaned list? And, well, it would be cool if someone stepped up to maintain the package :-) Thanks, Peter -- Peter Williams / peter at newton.cx From fedora at leemhuis.info Tue Aug 8 07:29:52 2006 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Tue, 08 Aug 2006 09:29:52 +0200 Subject: 'straw' package appears to be orphaned In-Reply-To: <42578.140.247.244.211.1155015403.squirrel@www.newton.cx> References: <42578.140.247.244.211.1155015403.squirrel@www.newton.cx> Message-ID: <44D83D70.8090109@leemhuis.info> Hi! Peter Williams schrieb: > As per https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186731, the > Fedora Extras package of the Straw news reader is extremely old. The > maintainer, Colin Charles has seemed nonresponsive for about five months, > at least. I'm not sure what's going on since his blog is updated quite > regularly. > > I'm not familiar with the organization of Fedora Extras, but can this > package be added the orphaned list? And, well, it would be cool if someone > stepped up to maintain the package :-) I pinged bytee in #fedora-extras on this, here's his response: [07:54:09] < thl> | bytee_, please read https://www.redhat.com/archives/fedora-extras-list/2006-August/msg00170.html [09:18:44] < bytee_> | thl: i will respond and fix that bug. sorry. [09:19:04] < bytee_> | thl: my main problem was that the package required an update. and the update breaks the old database. i havent figured out a nice way to deal with it [09:19:32] < bytee_> | thl: i'm thinking that breaking it in itself might be the best way. because the straw package itself doesn't offfer a conversion tool [09:23:19] < thl> | bytee_, thx [09:23:31] < thl> | bytee_, gaim-guifications needs a update, too [09:23:37] < thl> | bytee_, see https://www.redhat.com/archives/fedora-extras-list/2006-August/msg00166.html [09:24:10] < bytee_> | thl: i know that, i will do that next week. [09:24:14] < bytee_> | as does MagicPoint. [09:24:26] < bytee_> | thl: give me a week, i'm not home at the moment [09:24:50] < bytee_> | thl: do you mind responding to the post for me? its not convenient to do email atm [09:26:58] < thl> | bytee_, shall I simply cut'n'paste this conversation? [09:27:05] < bytee_> | thl: sure, if you want. [09:27:17] < bytee_> | thl: i'll update it all next week when back. CU thl From bugs.michael at gmx.net Tue Aug 8 09:42:13 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Tue, 8 Aug 2006 11:42:13 +0200 Subject: 'straw' package appears to be orphaned In-Reply-To: <42578.140.247.244.211.1155015403.squirrel@www.newton.cx> References: <42578.140.247.244.211.1155015403.squirrel@www.newton.cx> Message-ID: <20060808114213.37f717ef.bugs.michael@gmx.net> On Tue, 8 Aug 2006 01:36:43 -0400 (EDT), Peter Williams wrote: > As per https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186731, the > Fedora Extras package of the Straw news reader is extremely old. The > maintainer, Colin Charles has seemed nonresponsive for about five months, > at least. I'm not sure what's going on since his blog is updated quite > regularly. > > I'm not familiar with the organization of Fedora Extras, but can this > package be added the orphaned list? A single ticket in bugzilla without a list of subsequent contact attempts is not enough to mark someone's package as orphaned. http://fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers From pertusus at free.fr Tue Aug 8 15:07:50 2006 From: pertusus at free.fr (Patrice Dumas) Date: Tue, 8 Aug 2006 17:07:50 +0200 Subject: add FE-Legal to ReviewGuidelines Message-ID: <20060808150750.GA3131@free.fr> Hello, Could it be possible for somebody who can to add FE-Legal with the other blocker bugs at the bottom of http://fedoraproject.org/wiki/Packaging/ReviewGuidelines There is also something like FE-GUIDELINES if I recall well. Is there another place in bugzilla/wiki/web site where such bugs are referenced? I always look there but it may be wrong... -- Pat From pertusus at free.fr Tue Aug 8 16:33:10 2006 From: pertusus at free.fr (Patrice Dumas) Date: Tue, 8 Aug 2006 18:33:10 +0200 Subject: add FE-Legal to ReviewGuidelines In-Reply-To: <20060808150750.GA3131@free.fr> References: <20060808150750.GA3131@free.fr> Message-ID: <20060808163310.GB3131@free.fr> On Tue, Aug 08, 2006 at 05:07:50PM +0200, Patrice Dumas wrote: > Hello, > > Could it be possible for somebody who can to add > > FE-Legal with the other blocker bugs at the bottom of > http://fedoraproject.org/wiki/Packaging/ReviewGuidelines > > There is also something like FE-GUIDELINES if I recall well. And also FE-DEADREVIEW From buildsys at fedoraproject.org Tue Aug 8 18:09:15 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Tue, 8 Aug 2006 14:09:15 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-08 Message-ID: <20060808180915.33947152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 24 TeXmacs-1.0.6.5-1.fc5 XaraLX-0.7-2.fc5.r1614 akode-2.0.1-1.fc5 boo-0.7.6.2237-8.fc5 digikamimageplugins-0.8.2-3.fc5 geomview-1.8.2-0.17.rc8.fc5 ghdl-0.24-0.60svn.0.fc5 gtkwave-3.0.8-1.fc5 jabberd-2.0-0.s11.10.fc5 ks3switch-0.1-2.fc5 liferea-1.0.20-3.fc5 monodevelop-0.11-16.fc5 perl-DateTime-Format-HTTP-0.36-3.fc5 perl-DateTime-Format-Mail-0.30-3.fc5 perl-MIME-tools-5.420-2.fc5 perl-Module-Starter-1.42-3.fc5 pessulus-2.15.91-1.fc5 plplot-5.6.1-2.fc5 python-paramiko-1.6.1-1.fc5 python-sqlalchemy-0.2.6-1.fc5 python-tpg-3.1.0-1.fc5 rxvt-unicode-7.9-1.fc5 smart-0.42-35.fc5 xforms-1.0.90-7.fc5 Packages built and released for Fedora Extras 4: 16 TeXmacs-1.0.6.5-1.fc4.1 akode-2.0.1-1.fc4 digikamimageplugins-0.8.2-3.fc4 gtkwave-3.0.8-1.fc4 perl-DateTime-Format-HTTP-0.36-3.fc4 perl-DateTime-Format-Mail-0.30-3.fc4 perl-Exception-Class-1.23-1.fc4 perl-MIME-tools-5.420-2.fc4 perl-Module-Starter-1.42-3.fc4 perl-Object-InsideOut-1.48-1.fc4 plplot-5.6.1-2.fc4 python-paramiko-1.6.1-1.fc4 python-sqlalchemy-0.2.6-1.fc4 python-tpg-3.1.0-1.fc4 rxvt-unicode-7.9-1.fc4 smart-0.42-35.fc4 Packages built and released for Fedora Extras development: 24 abcde-2.3.99.6-1.fc6 akode-2.0.1-1.fc6 banshee-0.10.11-1.fc6 boo-0.7.6.2237-8.fc6 dap-hdf4_handler-3.7.1-2.fc6 digikamimageplugins-0.8.2-3.fc6 geomview-1.8.2-0.17.rc8.fc6 gtksourceview-sharp-2.0-15.fc6 gtkwave-3.0.8-1.fc6 libipoddevice-0.4.5-2.fc6 liferea-1.0.20-4.fc6 perl-MIME-tools-5.420-2.fc6 perl-Module-Starter-1.42-3.fc6 perl-Module-Starter-PBP-0.000003-4.fc6 pessulus-2.15.91-1.fc6 plplot-5.6.1-3.fc6 python-paramiko-1.6.1-1.fc6 python-sqlalchemy-0.2.6-1.fc6 python-tpg-3.1.0-1.fc6 qt4-4.2.0-0.5.tp1.fc6 rxvt-unicode-7.9-1.fc6 tuxpuck-0.8.2-1.fc6 vorbisgain-0.34-1.fc6 xforms-1.0.90-7.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Tue Aug 8 18:09:46 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Tue, 8 Aug 2006 14:09:46 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-08 Message-ID: <20060808180946.644C4152169@buildsys.fedoraproject.org> aplus-fsf: Jochen AT herr-schmitt.de 4: 0:4.20.2-9 (FE4) 5: 0:4.20.2-5.fc5 (FE5) 6: 0:4.20.2-5.fc6 (FE6) azureus: green AT redhat.com 5: 0:2.4.0.3-0.20060529cvs_1.fc5 (FE5) 6: 0:2.4.0.3-0.20060328cvs_5.fc6 (FE6) camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) colorscheme: gauret AT free.fr 4: 0:0.3-4.fc4 (FE4) 5: 0:0.3-3.fc5 (FE5) 6: 0:0.3.91-2.fc6 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) digikam: mgarski AT post.pl 3: 0:0.8.2-2.fc3 (FE3) 4: 0:0.8.2-1.fc4 (FE4) 5: 0:0.8.2-1.fc5 (FE5) 6: 0:0.8.2-1.fc6 (FE6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) dogtail: zcerza AT redhat.com 5: 0:0.5.2-2.fc5 (FE5) 6: 0:0.5.2-1.fc6 (FC6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: liljencrantz AT gmail.com 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gaim-gaym: cweyl AT alumni.drew.edu 5: 0:0.96-3.fc5 (FE5) 6: 0:0.96-2.fc6 (FE6) gcdmaster: denis AT poolshark.org 4: 0:1.2.1-5.fc4 (FE4) 5: 0:1.2.1-4.fc5 (FE5) 6: 0:1.2.1-4.fc5 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) inkscape: denis AT poolshark.org 4: 0:0.44-3.fc4 (FE4) 5: 0:0.44-2.fc5 (FE5) 6: 0:0.44-2.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) koffice: andreas.bierfert AT lowlatency.de 5: 0:1.5.2-1.fc5 (FE5) 6: 0:1.5.1-2.fc6 (FE6) libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) libpqxx: andreas.bierfert AT lowlatency.de 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) lvm2: 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-16.fc6 (FC6) mozilla: 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.1-2.fc5 (FE5) 6: 0:1.0.1-1.fc5 (FE6) quagga: 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) seamonkey: kengert AT redhat.com 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) smart: Axel.Thimm AT ATrpms.net 5: 0:0.42-35.fc5 (FE5) 6: 0:0.41-31.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.5-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) vorbisgain: noa AT resare.com 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) ypbind: 5: 3:1.19-1 (FC5-updates) 6: 3:1.19-0.3 (FC6) From buildsys at fedoraproject.org Tue Aug 8 18:30:31 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Tue, 08 Aug 2006 18:30:31 -0000 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-08 Message-ID: <20060808183031.30871.33184@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- Jochen AT herr-schmitt.de blender - 2.42-5.fc6.i386 blender - 2.42-5.fc6.ppc blender - 2.42-5.fc6.x86_64 andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (124 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (124 days) koffice-langpack-af - 1.5.2-1.fc6.noarch koffice-langpack-af - 1.5.2-1.fc6.noarch koffice-langpack-af - 1.5.2-1.fc6.noarch koffice-langpack-ar - 1.5.2-1.fc6.noarch koffice-langpack-ar - 1.5.2-1.fc6.noarch koffice-langpack-ar - 1.5.2-1.fc6.noarch koffice-langpack-bg - 1.5.2-1.fc6.noarch koffice-langpack-bg - 1.5.2-1.fc6.noarch koffice-langpack-bg - 1.5.2-1.fc6.noarch koffice-langpack-br - 1.5.2-1.fc6.noarch koffice-langpack-br - 1.5.2-1.fc6.noarch koffice-langpack-br - 1.5.2-1.fc6.noarch koffice-langpack-bs - 1.5.2-1.fc6.noarch koffice-langpack-bs - 1.5.2-1.fc6.noarch koffice-langpack-bs - 1.5.2-1.fc6.noarch koffice-langpack-ca - 1.5.2-1.fc6.noarch koffice-langpack-ca - 1.5.2-1.fc6.noarch koffice-langpack-ca - 1.5.2-1.fc6.noarch koffice-langpack-cs - 1.5.2-1.fc6.noarch koffice-langpack-cs - 1.5.2-1.fc6.noarch koffice-langpack-cs - 1.5.2-1.fc6.noarch koffice-langpack-cy - 1.5.2-1.fc6.noarch koffice-langpack-cy - 1.5.2-1.fc6.noarch koffice-langpack-cy - 1.5.2-1.fc6.noarch koffice-langpack-da - 1.5.2-1.fc6.noarch koffice-langpack-da - 1.5.2-1.fc6.noarch koffice-langpack-da - 1.5.2-1.fc6.noarch koffice-langpack-de - 1.5.2-1.fc6.noarch koffice-langpack-de - 1.5.2-1.fc6.noarch koffice-langpack-de - 1.5.2-1.fc6.noarch koffice-langpack-el - 1.5.2-1.fc6.noarch koffice-langpack-el - 1.5.2-1.fc6.noarch koffice-langpack-el - 1.5.2-1.fc6.noarch koffice-langpack-en_GB - 1.5.2-1.fc6.noarch koffice-langpack-en_GB - 1.5.2-1.fc6.noarch koffice-langpack-en_GB - 1.5.2-1.fc6.noarch koffice-langpack-eo - 1.5.2-1.fc6.noarch koffice-langpack-eo - 1.5.2-1.fc6.noarch koffice-langpack-eo - 1.5.2-1.fc6.noarch koffice-langpack-es - 1.5.2-1.fc6.noarch koffice-langpack-es - 1.5.2-1.fc6.noarch koffice-langpack-es - 1.5.2-1.fc6.noarch koffice-langpack-et - 1.5.2-1.fc6.noarch koffice-langpack-et - 1.5.2-1.fc6.noarch koffice-langpack-et - 1.5.2-1.fc6.noarch koffice-langpack-eu - 1.5.2-1.fc6.noarch koffice-langpack-eu - 1.5.2-1.fc6.noarch koffice-langpack-eu - 1.5.2-1.fc6.noarch koffice-langpack-fi - 1.5.2-1.fc6.noarch koffice-langpack-fi - 1.5.2-1.fc6.noarch koffice-langpack-fi - 1.5.2-1.fc6.noarch koffice-langpack-fr - 1.5.2-1.fc6.noarch koffice-langpack-fr - 1.5.2-1.fc6.noarch koffice-langpack-fr - 1.5.2-1.fc6.noarch koffice-langpack-ga - 1.5.2-1.fc6.noarch koffice-langpack-ga - 1.5.2-1.fc6.noarch koffice-langpack-ga - 1.5.2-1.fc6.noarch koffice-langpack-he - 1.5.2-1.fc6.noarch koffice-langpack-he - 1.5.2-1.fc6.noarch koffice-langpack-he - 1.5.2-1.fc6.noarch koffice-langpack-hi - 1.5.2-1.fc6.noarch koffice-langpack-hi - 1.5.2-1.fc6.noarch koffice-langpack-hi - 1.5.2-1.fc6.noarch koffice-langpack-hu - 1.5.2-1.fc6.noarch koffice-langpack-hu - 1.5.2-1.fc6.noarch koffice-langpack-hu - 1.5.2-1.fc6.noarch koffice-langpack-is - 1.5.2-1.fc6.noarch koffice-langpack-is - 1.5.2-1.fc6.noarch koffice-langpack-is - 1.5.2-1.fc6.noarch koffice-langpack-it - 1.5.2-1.fc6.noarch koffice-langpack-it - 1.5.2-1.fc6.noarch koffice-langpack-it - 1.5.2-1.fc6.noarch koffice-langpack-ja - 1.5.2-1.fc6.noarch koffice-langpack-ja - 1.5.2-1.fc6.noarch koffice-langpack-ja - 1.5.2-1.fc6.noarch koffice-langpack-lt - 1.5.2-1.fc6.noarch koffice-langpack-lt - 1.5.2-1.fc6.noarch koffice-langpack-lt - 1.5.2-1.fc6.noarch koffice-langpack-mk - 1.5.2-1.fc6.noarch koffice-langpack-mk - 1.5.2-1.fc6.noarch koffice-langpack-mk - 1.5.2-1.fc6.noarch koffice-langpack-ms - 1.5.2-1.fc6.noarch koffice-langpack-ms - 1.5.2-1.fc6.noarch koffice-langpack-ms - 1.5.2-1.fc6.noarch koffice-langpack-nb - 1.5.2-1.fc6.noarch koffice-langpack-nb - 1.5.2-1.fc6.noarch koffice-langpack-nb - 1.5.2-1.fc6.noarch koffice-langpack-nl - 1.5.2-1.fc6.noarch koffice-langpack-nl - 1.5.2-1.fc6.noarch koffice-langpack-nl - 1.5.2-1.fc6.noarch koffice-langpack-nn - 1.5.2-1.fc6.noarch koffice-langpack-nn - 1.5.2-1.fc6.noarch koffice-langpack-nn - 1.5.2-1.fc6.noarch koffice-langpack-pl - 1.5.2-1.fc6.noarch koffice-langpack-pl - 1.5.2-1.fc6.noarch koffice-langpack-pl - 1.5.2-1.fc6.noarch koffice-langpack-pt - 1.5.2-1.fc6.noarch koffice-langpack-pt - 1.5.2-1.fc6.noarch koffice-langpack-pt - 1.5.2-1.fc6.noarch koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch koffice-langpack-ro - 1.5.2-1.fc6.noarch koffice-langpack-ro - 1.5.2-1.fc6.noarch koffice-langpack-ro - 1.5.2-1.fc6.noarch koffice-langpack-ru - 1.5.2-1.fc6.noarch koffice-langpack-ru - 1.5.2-1.fc6.noarch koffice-langpack-ru - 1.5.2-1.fc6.noarch koffice-langpack-se - 1.5.2-1.fc6.noarch koffice-langpack-se - 1.5.2-1.fc6.noarch koffice-langpack-se - 1.5.2-1.fc6.noarch koffice-langpack-sk - 1.5.2-1.fc6.noarch koffice-langpack-sk - 1.5.2-1.fc6.noarch koffice-langpack-sk - 1.5.2-1.fc6.noarch koffice-langpack-sl - 1.5.2-1.fc6.noarch koffice-langpack-sl - 1.5.2-1.fc6.noarch koffice-langpack-sl - 1.5.2-1.fc6.noarch koffice-langpack-sr - 1.5.2-1.fc6.noarch koffice-langpack-sr - 1.5.2-1.fc6.noarch koffice-langpack-sr - 1.5.2-1.fc6.noarch koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch koffice-langpack-sv - 1.5.2-1.fc6.noarch koffice-langpack-sv - 1.5.2-1.fc6.noarch koffice-langpack-sv - 1.5.2-1.fc6.noarch koffice-langpack-ta - 1.5.2-1.fc6.noarch koffice-langpack-ta - 1.5.2-1.fc6.noarch koffice-langpack-ta - 1.5.2-1.fc6.noarch koffice-langpack-tg - 1.5.2-1.fc6.noarch koffice-langpack-tg - 1.5.2-1.fc6.noarch koffice-langpack-tg - 1.5.2-1.fc6.noarch koffice-langpack-tr - 1.5.2-1.fc6.noarch koffice-langpack-tr - 1.5.2-1.fc6.noarch koffice-langpack-tr - 1.5.2-1.fc6.noarch koffice-langpack-uk - 1.5.2-1.fc6.noarch koffice-langpack-uk - 1.5.2-1.fc6.noarch koffice-langpack-uk - 1.5.2-1.fc6.noarch koffice-langpack-uz - 1.5.2-1.fc6.noarch koffice-langpack-uz - 1.5.2-1.fc6.noarch koffice-langpack-uz - 1.5.2-1.fc6.noarch koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch libopensync-plugin-evolution2 - 0.18-6.fc5.i386 libopensync-plugin-evolution2 - 0.18-6.fc5.ppc libopensync-plugin-evolution2 - 0.18-6.fc5.x86_64 wine-core - 0.9.17-1.fc6.i386 (13 days) bdpepple AT ameritech.net contact-lookup-applet - 0.14-3.fc6.i386 contact-lookup-applet - 0.14-3.fc6.ppc contact-lookup-applet - 0.14-3.fc6.x86_64 byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (20 days) gaim-guifications - 2.12-3.fc5.ppc (20 days) gaim-guifications - 2.12-3.fc5.x86_64 (20 days) cweyl AT alumni.drew.edu gaim-gaym - 0.96-2.fc6.i386 (20 days) gaim-gaym - 0.96-2.fc6.ppc (20 days) gaim-gaym - 0.96-2.fc6.x86_64 (20 days) dennis AT ausil.us knetworkmanager - 0.1-0.3.svn20060625.fc6.i386 (19 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.ppc (19 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.x86_64 (19 days) fedora AT leemhuis.info gsynaptics - 0.9.8-1.fc6.ppc (20 days) gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (12 days) amarok - 1.4.1-3.fc6.ppc (12 days) showimg-pgsql - 0.9.5-7.fc4.i386 showimg-pgsql - 0.9.5-7.fc4.ppc showimg-pgsql - 0.9.5-7.fc4.x86_64 showimg-pgsql - 0.9.5-7.fc5.i386 showimg-pgsql - 0.9.5-7.fc5.ppc showimg-pgsql - 0.9.5-7.fc5.x86_64 green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.i386 (13 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (13 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.x86_64 (13 days) jogl - 1.1.1-14.fc5.ppc (16 days) ivazquez AT ivazquez.net deskbar-applet - 2.14.1.1-1.fc6.i386 deskbar-applet - 2.14.1.1-1.fc6.ppc deskbar-applet - 2.14.1.1-1.fc6.x86_64 gnome-applet-music - 0.9.0-1.fc6.i386 (20 days) gnome-applet-music - 0.9.0-1.fc6.ppc (20 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (20 days) nautilus-search-tool - 0.2-1.fc5.i386 (20 days) nautilus-search-tool - 0.2-1.fc5.ppc (20 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (20 days) jkeating AT redhat.com contacts - 0.1-1.i386 contacts - 0.1-1.ppc contacts - 0.1-1.x86_64 lmacken AT redhat.com python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.i386 (24 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.ppc (24 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.x86_64 (24 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.i386 (24 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.ppc (24 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.x86_64 (24 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (20 days) gfontview - 0.5.0-5.fc5.ppc (20 days) gfontview - 0.5.0-5.fc5.x86_64 (20 days) gtkhtml36 - 3.6.2-5.fc6.i386 (20 days) gtkhtml36 - 3.6.2-5.fc6.ppc (20 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (20 days) libvisual-plugins - 0.2.0-3.fc5.i386 (20 days) libvisual-plugins - 0.2.0-3.fc5.i386 (20 days) libvisual-plugins - 0.2.0-3.fc5.ppc (20 days) libvisual-plugins - 0.2.0-3.fc5.ppc (20 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (20 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (20 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (83 days) syck-php - 0.55-7.fc5.i386 (83 days) syck-php - 0.55-7.fc5.ppc (83 days) syck-php - 0.55-7.fc5.ppc (83 days) syck-php - 0.55-7.fc5.x86_64 (83 days) syck-php - 0.55-7.fc5.x86_64 (83 days) rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (20 days) libibverbs - 1.0.3-1.fc6.ppc (20 days) libibverbs - 1.0.3-1.fc6.x86_64 (20 days) libibverbs-utils - 1.0.3-1.fc6.i386 (20 days) libibverbs-utils - 1.0.3-1.fc6.ppc (20 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (20 days) tcallawa AT redhat.com gambas-runtime - 1.0.14-2.fc5.i386 thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (20 days) directfb - 0.9.24-5.fc5.ppc (20 days) directfb - 0.9.24-5.fc5.x86_64 (20 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.i386 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc5.i386 requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) python-ruledispatch-0.5a0-0.1.svnr2115.fc5.x86_64 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc5.x86_64 requires libpqxx-2.6.6.so()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.ppc requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc5.ppc requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.i386 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc4.i386 requires libpqxx-2.6.6.so Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.x86_64 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc4.x86_64 requires libpqxx-2.6.6.so()(64bit) Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.ppc requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc4.ppc requires libpqxx-2.6.6.so Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.i386 requires libgcj.so.7 blender-2.42-5.fc6.i386 requires libgettextlib-0.14.5.so contact-lookup-applet-0.14-3.fc6.i386 requires libebook-1.2.so.5 contacts-0.1-1.i386 requires libebook-1.2.so.5 deskbar-applet-2.14.1.1-1.fc6.i386 requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.i386 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 gambas-runtime-1.0.14-2.fc5.i386 requires libgettextlib-0.14.5.so gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-qt-1.so.1 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- azureus-2.4.0.3-0.20060328cvs_5.fc6.x86_64 requires libgcj.so.7()(64bit) blender-2.42-5.fc6.x86_64 requires libgettextlib-0.14.5.so()(64bit) contact-lookup-applet-0.14-3.fc6.x86_64 requires libebook-1.2.so.5()(64bit) contacts-0.1-1.x86_64 requires libebook-1.2.so.5()(64bit) deskbar-applet-2.14.1.1-1.fc6.x86_64 requires libebook-1.2.so.5()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-gaym-0.96-2.fc6.x86_64 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-qt-1.so.1()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-1.so.2()(64bit) koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libedata-cal-1.2.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libecal-1.2.so.3()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libebook-1.2.so.5()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.17-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 blender-2.42-5.fc6.ppc requires libgettextlib-0.14.5.so contact-lookup-applet-0.14-3.fc6.ppc requires libebook-1.2.so.5 contacts-0.1-1.ppc requires libebook-1.2.so.5 deskbar-applet-2.14.1.1-1.fc6.ppc requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.ppc requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gsynaptics-0.9.8-1.fc6.ppc requires synaptics gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-qt-1.so.1 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 ====================================================================== New report for: Jochen AT herr-schmitt.de package: blender - 2.42-5.fc6.i386 from fedora-extras-development-i386 unresolved deps: libgettextlib-0.14.5.so package: blender - 2.42-5.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libgettextlib-0.14.5.so()(64bit) package: blender - 2.42-5.fc6.ppc from fedora-extras-development-ppc unresolved deps: libgettextlib-0.14.5.so ====================================================================== New report for: tcallawa AT redhat.com package: gambas-runtime - 1.0.14-2.fc5.i386 from fedora-extras-development-i386 unresolved deps: libgettextlib-0.14.5.so From dominik at greysector.net Tue Aug 8 20:11:46 2006 From: dominik at greysector.net (Dominik 'Rathann' Mierzejewski) Date: Tue, 8 Aug 2006 22:11:46 +0200 Subject: add FE-Legal to ReviewGuidelines In-Reply-To: <20060808150750.GA3131@free.fr> References: <20060808150750.GA3131@free.fr> Message-ID: <20060808201146.GC15994@rathann.pekin.waw.pl> On Tuesday, 08 August 2006 at 17:07, Patrice Dumas wrote: > Hello, > > Could it be possible for somebody who can to add > > FE-Legal with the other blocker bugs at the bottom of > http://fedoraproject.org/wiki/Packaging/ReviewGuidelines > > There is also something like FE-GUIDELINES if I recall well. > > Is there another place in bugzilla/wiki/web site where such > bugs are referenced? I always look there but it may be wrong... Since we're on the subject of FE-Legal, how long does one have to wait for any response? mkvtoolnix has been waiting for a long time... https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177134 Regards, R. -- MPlayer developer and RPMs maintainer: http://rpm.greysector.net/mplayer/ There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan From xb_ml at kelkoo.net Tue Aug 8 20:40:30 2006 From: xb_ml at kelkoo.net (Xavier Bachelot) Date: Tue, 08 Aug 2006 22:40:30 +0200 Subject: Overriding kernel modules Message-ID: <44D8F6BE.80504@kelkoo.net> Hi, There is a feature in FC4/FC5 kernels that allow to override modules from them by placing files in /lib/modules/$kernel_version/updates. There is also a policy in FE that prohibit replacement of a Core package. In the case of this feature, this is not exactly a replacement. Would this be allowed in FE ? And if yes, how should that be packaged ? This is not covered in the packaging kernel modules guidelines. Just for a little background, I'm interested in this feature because I use a development version (openchrome) of the X driver for via chipsets (unichrome/unichrome pro) that requires more recent drm kernel modules than the ones in upstream kernel to work to their full extend. Regards, Xavier From jwboyer at jdub.homelinux.org Wed Aug 9 01:39:44 2006 From: jwboyer at jdub.homelinux.org (Josh Boyer) Date: Tue, 08 Aug 2006 20:39:44 -0500 Subject: Overriding kernel modules In-Reply-To: <44D8F6BE.80504@kelkoo.net> References: <44D8F6BE.80504@kelkoo.net> Message-ID: <1155087584.4288.5.camel@vader.jdub.homelinux.org> On Tue, 2006-08-08 at 22:40 +0200, Xavier Bachelot wrote: > Hi, > > There is a feature in FC4/FC5 kernels that allow to override modules > from them by placing files in /lib/modules/$kernel_version/updates. > There is also a policy in FE that prohibit replacement of a Core > package. In the case of this feature, this is not exactly a replacement. If it's a newer version of a module that already exists in the base kernel package, then yes it is a replacement. > Would this be allowed in FE ? IMHO, no. > And if yes, how should that be packaged ? This is not covered in the > packaging kernel modules guidelines. Probably because it was never intended to be allowed. > Just for a little background, I'm interested in this feature because I > use a development version (openchrome) of the X driver for via chipsets > (unichrome/unichrome pro) that requires more recent drm kernel modules > than the ones in upstream kernel to work to their full extend. That's replacing Core modules, and therefore not allowed. Please don't interpret the above to mean you can't personally do it yourself or even provide a third party repo for this. However, it does not belong in Extras. josh From sundaram at fedoraproject.org Wed Aug 9 06:55:41 2006 From: sundaram at fedoraproject.org (Rahul) Date: Wed, 09 Aug 2006 12:25:41 +0530 Subject: FESCo Election Policy **Draft** In-Reply-To: <1154896297.3765.78.camel@localhost> References: <1154896297.3765.78.camel@localhost> Message-ID: <44D986ED.1040905@fedoraproject.org> Toshio Kuratomi wrote: > > == Candidates == > > Candidates may be any member of the cladone group in the Fedora Accounts > System. This means anyone who has done the minimum to become a member > of the Fedora Project can run for a seat on FESCo whether or not they > are a contributer to the Fedora Extras portion of the project. > Candidates must self nominate at least three days before the election > opens by writing their information onto the wiki (Fedora account, email > and irc nick, statement of past contributions and what they hope to > accomplish while on the Fedora Project Board. Did you want to say FESCo instead of the Fedora Project Board here? Rahul From sundaram at fedoraproject.org Wed Aug 9 06:57:21 2006 From: sundaram at fedoraproject.org (Rahul) Date: Wed, 09 Aug 2006 12:27:21 +0530 Subject: add FE-Legal to ReviewGuidelines In-Reply-To: <20060808201146.GC15994@rathann.pekin.waw.pl> References: <20060808150750.GA3131@free.fr> <20060808201146.GC15994@rathann.pekin.waw.pl> Message-ID: <44D98751.3070805@fedoraproject.org> Dominik 'Rathann' Mierzejewski wrote: > Since we're on the subject of FE-Legal, how long does one have > to wait for any response? mkvtoolnix has been waiting for a long > time... https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177134 > Did someone actually ask legal this question? I dont see any comments that suggest that. Rahul From toshio at tiki-lounge.com Wed Aug 9 07:54:11 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Wed, 09 Aug 2006 00:54:11 -0700 Subject: Ideas for Co-maintainership in Extras In-Reply-To: <44CB681A.8030709@leemhuis.info> References: <44CB681A.8030709@leemhuis.info> Message-ID: <1155110051.2640.67.camel@localhost> On Sat, 2006-07-29 at 15:52 +0200, Thorsten Leemhuis wrote: > Hi all! > > Welcome everybody to my brain dump of ideas around co-maintainership for > Fedora Extras. > > == Why we need it == [snip] I agree with every one of those uses for co-maintainership. We might have to break out the rules for them into several different documents but they all seem to be things we really want to enable. > == What we need to make all that happen == > > * we need limited access in the VCS -- e.g. new contributors that start > as co-maintainers get only access to the packages they co-maintain, but > not to the buildsys or to other packages > I think this will need to be implemented partially in the VCS and partially in the buildsys. The VCS will keep packagers from committing changes to packages they aren't comaintainers of. The buildsys will have to be smart enough not to queue packages from maintainers that don't have the build permissions. * Note: permission to build has to be added to either the package database or the new account system depending on whether we want building to be a per contributor permission or a person/group-per-package permission. > * per repo maintainers should be possible -- we probably need a proper > the package database for this > Yes. For the previous point as well. The package database needs to hold all the information about what role a person plays for a package. The VCS will sync with the package database to control access to the files. > * primary- and other co-maintainers need to get mails directly into > their inbox for everything other maintainers do with a package (commit > changes, updates, upload of new files, build requests, pushes). > This needs a script to run on commit that queries the package database for people interested in seeing commits to a specific package. The package database would be recording more than just owners for this (Feel free to come up with better names): * tier one owners AKA primary owner. Do we want to allow more than one? This person can commit files, request builds, and approve other contributers as co-maintainers, etc. * Comaintainers Can commit files and request builds. Should they be able to approve other contributers as maintainers as well? * Tier-two maintainers: This is primarily for the "new maintainer" case. The person is not fully sponsored. They can commit files to designated branches of the package but nothing else. * Observers: People who want to watch commit emails and bugzilla reports for this package. > * rules need to be written, e.g. > * responsibilities between co-maitainer and primary maintainer > * Bug responsiveness > * do we need a primary maintainer at all? > * can N (N=4?) co-maintainers outvote the primary maintainer in case of > disputes? > * can there be takeovers ("I'm doing all the work and my primary > maintainer never does anything; I want to take the package over") > * probably a lot more... > * "new contributors have to actively co-maintain one package for at > least X months before they can take over this or other packages > completely (they of course can also take the traditional route with a > new package and sponsoring) > There are going to be lots of these details. Should we break this up into steps to create this policy? 1) Write down all the "Why we need it" ideas along with any more we come up with. 2) Create a sample structure (Two tiers of maintainers plus observers? Three tiers?) and make sure it will work with all our "Why we need it" cases. 3) Write up rules that describe how one transitions between tiers in the hierarchy and the responsibilities of each level of maintainership. 2 + 3 = the base policy for co-maintainership. 4) Write up separate documents or add to existing documents to enable the rest of the "Why we need it" cases (Example: Create policy on becoming a contributer by going through co-maintainership instead of package submission. Add this to the "How to get Sponsored" document.) > > == Action plan == > > === Short term === > > * Fix bugzilla auto-CC in owners.list -- see > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198109 > Hmm.. The last entry there is asking for input from Sopwith but he's on extended leave. Maybe someone should ping warren or mmcgrath about this. > * evaluate in detail the technical groundwork we need for proper > co-maintainership -- especially package database, VCS, the accounts > system and everywhere else > The VCS is currently targeted at FC-7. We need to be sure we have all our requirements put together otherwise that target will slip. > === Middle term === > > * Wait for the new package database to finish and make sure it offers > everything we need (maintainers per dist, ...) > is there someone assigned to this? I thought someone in Infrastructure was looking into this but I'm looking at the Infrastructure Schedule and it's not on there.... > * encourage co-maintainership in general -- I'd say that 95% of Extras > packages should have co-maintainers (the other 5% are packages for > special interest areas where only one of the current contributors might > bne interested in) > > * especially encourage co-maintainership or even a package hand-over to > those people that maintain a lot of or important packages > Would it be good to shift our ideas of package ownership? My impression of Core is that the package ownership paradigm is much looser there. Would it be helpful to revamp our view of packages from: Package is owned and maintained by Foo with help from comaintainer Bar and the Baz SIG. Into: Package is a part of the Baz SIG and maintained by the members Foo and Bar. Viewing things this way, packages are always a part of one or more SIGs/groups which have people who have volunteered to take on responsibility for the package in question. Packagers are similarly a part of the SIGs to which the package belongs and can ask the relevant SIGs for help (I am packaging a mono web server which belongs to the mono and internet server SIGs. If the question is whether mono apps are noarch I ask the mono SIG. If the question is whether web servers should each have their own document root, I ask the Internet Server SIG.) Potential difficulties are that there may not presently be a SIG for every package. We can create them (Educational SIG, Science SIG, File Server SIG, Version Control SIG....) but it may not work as well if the SIGs don't grow organically.... Organization of the SIGs might also be a problem but we could use something like Trove categories.... > * work out detailed rules for co-maintainership (see above) > > === Long term === > > * make sure co-maintainers get mails when one of their packages is > changed in CVS or build (people can set up local filters to get > something like that but it's often forgotten and likely to break; a > feature like this is also interesting for sponsors that want to watch > people they sponsored closely) > This should be tracked by the package database with a script that watches commits querying the db for the list of people to send to. (Alternately, changes to the package db could set up mail aliases for each package. The script would then only have to send mail to the alais for the package.) > * make co-maintainership possible in core, too. > The Great Merge is the goal for our generation of Fedora. What will be the goal for the Post-Merge generation? :-) -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From toshio at tiki-lounge.com Wed Aug 9 08:09:46 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Wed, 09 Aug 2006 01:09:46 -0700 Subject: FESCo Election Policy **Draft** In-Reply-To: <44D986ED.1040905@fedoraproject.org> References: <1154896297.3765.78.camel@localhost> <44D986ED.1040905@fedoraproject.org> Message-ID: <1155110986.2640.78.camel@localhost> On Wed, 2006-08-09 at 12:25 +0530, Rahul wrote: > Toshio Kuratomi wrote: > > > > > == Candidates == > > > > Candidates may be any member of the cladone group in the Fedora Accounts > > System. This means anyone who has done the minimum to become a member > > of the Fedora Project can run for a seat on FESCo whether or not they > > are a contributer to the Fedora Extras portion of the project. > > Candidates must self nominate at least three days before the election > > opens by writing their information onto the wiki (Fedora account, email > > and irc nick, statement of past contributions and what they hope to > > accomplish while on the Fedora Project Board. > > Did you want to say FESCo instead of the Fedora Project Board here? Yes. Good catch. I've now changed this to FESCo on the wiki:: http://www.fedoraproject.org/wiki/Extras/Schedule/ElectionDraft BTW, this was one of the sections I considered controversial when I drafted this policy. Is anyone opposed to letting anyone in cladone become a candidate for FESCo? It could bring in thoughtful people who largely watch the proceedings of Extras or contribute to the infrastructure of the project rather than contributing packages into directly into Extras. It could also bring people who are only involved because they have an opinion but don't want to do any work. Assuming intelligent voters, this could still be a problem if we don't have enough candidates to fill all the open seats; allowing the person in by default.... -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sundaram at fedoraproject.org Wed Aug 9 08:21:45 2006 From: sundaram at fedoraproject.org (Rahul) Date: Wed, 09 Aug 2006 13:51:45 +0530 Subject: FESCo Election Policy **Draft** In-Reply-To: <1155110986.2640.78.camel@localhost> References: <1154896297.3765.78.camel@localhost> <44D986ED.1040905@fedoraproject.org> <1155110986.2640.78.camel@localhost> Message-ID: <44D99B19.9030100@fedoraproject.org> Toshio Kuratomi wrote: > BTW, this was one of the sections I considered controversial when I > drafted this policy. Is anyone opposed to letting anyone in cladone > become a candidate for FESCo? It could bring in thoughtful people who > largely watch the proceedings of Extras or contribute to the > infrastructure of the project rather than contributing packages into > directly into Extras. It could also bring people who are only involved > because they have an opinion but don't want to do any work. Assuming > intelligent voters, this could still be a problem if we don't have > enough candidates to fill all the open seats; allowing the person in by > default.... > Yes. I support this view point. Now that the packaging committee is handling the core packaging details, FESCo is more of a management job that doesnt really require intimate knowledge about packaging or to be a Fedora Extras packager to get involved and sort out affairs. Anyone who keeps tracks of things and is obsessed with discussing and communicating what is being tracked and resolved should fit the bill. Rahul From Axel.Thimm at ATrpms.net Wed Aug 9 08:41:22 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Wed, 9 Aug 2006 10:41:22 +0200 Subject: add FE-Legal to ReviewGuidelines In-Reply-To: <44D98751.3070805@fedoraproject.org> References: <20060808150750.GA3131@free.fr> <20060808201146.GC15994@rathann.pekin.waw.pl> <44D98751.3070805@fedoraproject.org> Message-ID: <20060809084122.GD23919@neu.nirvana> On Wed, Aug 09, 2006 at 12:27:21PM +0530, Rahul wrote: > Dominik 'Rathann' Mierzejewski wrote: > > >Since we're on the subject of FE-Legal, how long does one have > >to wait for any response? mkvtoolnix has been waiting for a long > >time... https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177134 > > > > Did someone actually ask legal this question? I dont see any comments > that suggest that. How does one ask legal and what kind of questions are admitted (not related to the above directly)? Thanks. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From sundaram at fedoraproject.org Wed Aug 9 08:48:46 2006 From: sundaram at fedoraproject.org (Rahul) Date: Wed, 09 Aug 2006 14:18:46 +0530 Subject: add FE-Legal to ReviewGuidelines In-Reply-To: <20060809084122.GD23919@neu.nirvana> References: <20060808150750.GA3131@free.fr> <20060808201146.GC15994@rathann.pekin.waw.pl> <44D98751.3070805@fedoraproject.org> <20060809084122.GD23919@neu.nirvana> Message-ID: <44D9A16E.8070907@fedoraproject.org> Axel Thimm wrote: > How does one ask legal and what kind of questions are admitted (not > related to the above directly)? > > Thanks. > Legal inquiries have been handled by Greg Dek so far http://fedora.redhat.com/About/contact.html I have heard that the process has been problematic though I didnt notice any specific details mentioned. I have suggested writing a mail to Fedora Advisory Board list if it requires a wider discussion since the deputy general counsel - Mark Webbink is on the list. http://fedoraproject.org/wiki/Board Any queries related to Fedora which require input from a lawyer should be ok. Rahul From xb_ml at kelkoo.net Wed Aug 9 09:27:00 2006 From: xb_ml at kelkoo.net (Xavier Bachelot) Date: Wed, 09 Aug 2006 11:27:00 +0200 Subject: Overriding kernel modules In-Reply-To: <1155087584.4288.5.camel@vader.jdub.homelinux.org> References: <44D8F6BE.80504@kelkoo.net> <1155087584.4288.5.camel@vader.jdub.homelinux.org> Message-ID: <44D9AA64.2050006@kelkoo.net> Josh Boyer wrote: > On Tue, 2006-08-08 at 22:40 +0200, Xavier Bachelot wrote: > >>Hi, >> >>There is a feature in FC4/FC5 kernels that allow to override modules >>from them by placing files in /lib/modules/$kernel_version/updates. >>There is also a policy in FE that prohibit replacement of a Core >>package. In the case of this feature, this is not exactly a replacement. > > > If it's a newer version of a module that already exists in the base > kernel package, then yes it is a replacement. > What I meant was it doesn't replace any file already owned by the kernel package, nor does it replace the kernel package. This is more like an extra module and this is an included feature of the Fedora provided kernel. But yes, I agree, it "taints" the kernel, the same way any out of tree kernel module (kmod-em8300 from Extras) or even in tree but not provided by Fedora (kmod-ntfs from the unamed repo) or worst a binary kernel (nvidia, ati...). Its just not the same level of tainting. > >>Would this be allowed in FE ? > > > IMHO, no. > > >>And if yes, how should that be packaged ? This is not covered in the >>packaging kernel modules guidelines. > > > Probably because it was never intended to be allowed. > yes, I just wanted to show that I did read the guidelines. > >>Just for a little background, I'm interested in this feature because I >>use a development version (openchrome) of the X driver for via chipsets >>(unichrome/unichrome pro) that requires more recent drm kernel modules >>than the ones in upstream kernel to work to their full extend. > > > That's replacing Core modules, and therefore not allowed. > > Please don't interpret the above to mean you can't personally do it > yourself or even provide a third party repo for this. However, it does > not belong in Extras. > That's what I'm already doing. Actually, I was doing it by overwritting some files owned by the kernel rpm, which is plain dirty until I found out this feature. And I'm also maintaining a third party repo for this purpose, but I try to keep it as clean as possible wrt to Fedora packaging guidelines. btw, do anyone have a suggestion on how such a package should be named ? something along the line kmod-update-drm maybe ? And also, we haven't heard of Fedora Alternatives for sometime and it was a good idea imho, at least for some very specific niche projects. My own repo provides functionalities for unichrome based graphic chipset and replace at least xorg-x11-drv-via for FC5 and was replacing the whole xorg for FC2/3/4 as well as some other packages. Thanks for your answers. Regards, Xavier From fedora at leemhuis.info Wed Aug 9 09:32:07 2006 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Wed, 09 Aug 2006 11:32:07 +0200 Subject: FESCo Election Policy **Draft** In-Reply-To: <44D99B19.9030100@fedoraproject.org> References: <1154896297.3765.78.camel@localhost> <44D986ED.1040905@fedoraproject.org> <1155110986.2640.78.camel@localhost> <44D99B19.9030100@fedoraproject.org> Message-ID: <44D9AB97.8090800@leemhuis.info> Rahul schrieb: > Toshio Kuratomi wrote: > >> BTW, this was one of the sections I considered controversial when I >> drafted this policy. Is anyone opposed to letting anyone in cladone >> become a candidate for FESCo? It could bring in thoughtful people who >> largely watch the proceedings of Extras or contribute to the >> infrastructure of the project rather than contributing packages into >> directly into Extras. It could also bring people who are only involved >> because they have an opinion but don't want to do any work. Assuming >> intelligent voters, this could still be a problem if we don't have >> enough candidates to fill all the open seats; allowing the person in by >> default.... > Yes. I support this view point. Now that the packaging committee is > handling the core packaging details, FESCo is more of a management job > that doesnt really require intimate knowledge about packaging or to be a > Fedora Extras packager to get involved and sort out affairs. Anyone who > keeps tracks of things and is obsessed with discussing and communicating > what is being tracked and resolved should fit the bill. I'd prefer if the FESCo members at least maintain one package in Extras so they know how the whole process works. But that's just my 2 cent. CU thl From Axel.Thimm at ATrpms.net Wed Aug 9 10:06:14 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Wed, 9 Aug 2006 12:06:14 +0200 Subject: Fixing FC4 bugs Message-ID: <20060809100614.GA31959@neu.nirvana> Hi, what was the policy on legacy bugfixing? FC3 and earlier had been frozen and some special permission was/is needed. The same has happened or will happen with FC4. o Has it already happened with FC4 going legacy or will there be a different date for FE FC4 freezing? o If it is now frozen, whom do I ask for permission to fix an FC4 bug? I want to fix a (non-critical) bug (201760). Thanks! -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From triad at df.lth.se Wed Aug 9 10:15:59 2006 From: triad at df.lth.se (Linus Walleij) Date: Wed, 9 Aug 2006 12:15:59 +0200 (CEST) Subject: Overriding kernel modules In-Reply-To: <44D9AA64.2050006@kelkoo.net> References: <44D8F6BE.80504@kelkoo.net> <1155087584.4288.5.camel@vader.jdub.homelinux.org> <44D9AA64.2050006@kelkoo.net> Message-ID: On Wed, 9 Aug 2006, Xavier Bachelot wrote: > But yes, I agree, it "taints" the kernel, the same way any out of tree kernel > module (kmod-em8300 from Extras) I though the term "tainted" refered to a kernel linking kernel modules that aren't GPL, i.e. a legal issue, not just any new kernel modules. Correct me if I'm wrong.... Linus From dominik at greysector.net Wed Aug 9 10:18:56 2006 From: dominik at greysector.net (Dominik 'Rathann' Mierzejewski) Date: Wed, 9 Aug 2006 12:18:56 +0200 Subject: add FE-Legal to ReviewGuidelines In-Reply-To: <44D98751.3070805@fedoraproject.org> References: <20060808150750.GA3131@free.fr> <20060808201146.GC15994@rathann.pekin.waw.pl> <44D98751.3070805@fedoraproject.org> Message-ID: <20060809101856.GB29291@rathann.pekin.waw.pl> On Wednesday, 09 August 2006 at 08:57, Rahul wrote: > Dominik 'Rathann' Mierzejewski wrote: > > >Since we're on the subject of FE-Legal, how long does one have > >to wait for any response? mkvtoolnix has been waiting for a long > >time... https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177134 > > > > Did someone actually ask legal this question? I dont see any comments > that suggest that. I was under impression that Ville did, but maybe I was mistaken. Regards, R. -- MPlayer developer and RPMs maintainer: http://rpm.greysector.net/mplayer/ There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan From xb_ml at kelkoo.net Wed Aug 9 10:26:44 2006 From: xb_ml at kelkoo.net (Xavier Bachelot) Date: Wed, 09 Aug 2006 12:26:44 +0200 Subject: Overriding kernel modules In-Reply-To: References: <44D8F6BE.80504@kelkoo.net> <1155087584.4288.5.camel@vader.jdub.homelinux.org> <44D9AA64.2050006@kelkoo.net> Message-ID: <44D9B864.3070707@kelkoo.net> Linus Walleij wrote: > On Wed, 9 Aug 2006, Xavier Bachelot wrote: > >> But yes, I agree, it "taints" the kernel, the same way any out of tree >> kernel module (kmod-em8300 from Extras) > > > I though the term "tainted" refered to a kernel linking kernel modules > that aren't GPL, i.e. a legal issue, not just any new kernel modules. > > Correct me if I'm wrong.... > Yes, you're right, that the original meaning, but from a support pov, its also tainted, that's what I meant. Dave Jones recently said in one or the other fedora mailing lists that he will disregard any kernel bug report which involves modules not coming from the Core kernel packages, because he has enough to do with just them. Introducing unknown parameters, even if the modules are coming from a verified source (FE), even if the sources are available, etc... is an additional burden. Regards, Xavier From dhowells at redhat.com Wed Aug 9 10:42:12 2006 From: dhowells at redhat.com (David Howells) Date: Wed, 09 Aug 2006 11:42:12 +0100 Subject: Overriding kernel modules In-Reply-To: References: <44D8F6BE.80504@kelkoo.net> <1155087584.4288.5.camel@vader.jdub.homelinux.org> <44D9AA64.2050006@kelkoo.net> Message-ID: <17358.1155120132@warthog.cambridge.redhat.com> Linus Walleij wrote: > > But yes, I agree, it "taints" the kernel, the same way any out of tree > > kernel module (kmod-em8300 from Extras) > > I though the term "tainted" refered to a kernel linking kernel modules that > aren't GPL, i.e. a legal issue, not just any new kernel modules. > > Correct me if I'm wrong.... I believe loading an unsigned kernel module or a differently signed kernel module will also taint the kernel, though in a different way. David From dennis at ausil.us Wed Aug 9 13:12:17 2006 From: dennis at ausil.us (Dennis Gilmore) Date: Wed, 9 Aug 2006 08:12:17 -0500 Subject: Fixing FC4 bugs In-Reply-To: <20060809100614.GA31959@neu.nirvana> References: <20060809100614.GA31959@neu.nirvana> Message-ID: <200608090812.18326.dennis@ausil.us> On Wednesday 09 August 2006 05:06, Axel Thimm wrote: > Hi, > > what was the policy on legacy bugfixing? FC3 and earlier had been > frozen and some special permission was/is needed. The same has > happened or will happen with FC4. > > o Has it already happened with FC4 going legacy or will there be a > different date for FE FC4 freezing? > > o If it is now frozen, whom do I ask for permission to fix an FC4 bug? > > I want to fix a (non-critical) bug (201760). > > Thanks! You can always fix your own bugs, until FE goes EOL. Which is not as clearly defined as it should be. I personally feel that extras should be EOL when legacy stops supporting the release. What is frozen now is new Branches for FE-4 if you have a package and have some need for it to be in FE-3 or FE-4 then you need to ask FESCo for permission to have the branch created. All this means is there should be no new FE-4 Branches for anything. but otherwise you are free to maintain your packages. FE-4 has joined FE-3 in maintenance mode Dennis From fedora at leemhuis.info Wed Aug 9 13:18:27 2006 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Wed, 09 Aug 2006 15:18:27 +0200 Subject: Fixing FC4 bugs In-Reply-To: <200608090812.18326.dennis@ausil.us> References: <20060809100614.GA31959@neu.nirvana> <200608090812.18326.dennis@ausil.us> Message-ID: <44D9E0A3.8050101@leemhuis.info> Dennis Gilmore schrieb: > On Wednesday 09 August 2006 05:06, Axel Thimm wrote: >> what was the policy on legacy bugfixing? FC3 and earlier had been >> frozen and some special permission was/is needed. The same has >> happened or will happen with FC4. >>[...] > You can always fix your own bugs, until FE goes EOL. Yes > Which is not as clearly defined as it should be. http://www.fedoraproject.org/wiki/Extras/Security/EOLPolicy But yes, the wiki needs a major cleanup. > I personally feel that extras should be EOL > when legacy stops supporting the release. Yes, quoting "When the Fedora Project drops support for a Fedora Core release the corresponding Fedora Extras is also dropped [...]". Read "Fedora Project" as Fedora Legacy in this case. [...] CU thl From mattdm at mattdm.org Wed Aug 9 13:32:00 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Wed, 9 Aug 2006 09:32:00 -0400 Subject: Fixing FC4 bugs In-Reply-To: <200608090812.18326.dennis@ausil.us> References: <20060809100614.GA31959@neu.nirvana> <200608090812.18326.dennis@ausil.us> Message-ID: <20060809133200.GA25281@jadzia.bu.edu> On Wed, Aug 09, 2006 at 08:12:17AM -0500, Dennis Gilmore wrote: > permission to have the branch created. All this means is there should be > no new FE-4 Branches for anything. but otherwise you are free to maintain > your packages. FE-4 has joined FE-3 in maintenance mode I'm in favor of a policy that encourages only security updates and serious bugfixes for versions corresponding to Core releases handled by Legacy. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From paul at all-the-johnsons.co.uk Wed Aug 9 15:42:10 2006 From: paul at all-the-johnsons.co.uk (PFJ) Date: Wed, 09 Aug 2006 16:42:10 +0100 Subject: Query on the owners.list Message-ID: <1155138130.3106.12.camel@localhost.localdomain> Hi, There looks to be two identical packages in the owners list ddrescue and dd_rescue. They both contain the same description and are packaged by the same person. Can anyone say if they are the same package and if they are, why there are two copies in FE (or at least the owners list)? TTFN Paul -- "Logic, my dear Zoe, is merely the ability to be wrong with authority" - Dr Who From ville.skytta at iki.fi Wed Aug 9 16:00:46 2006 From: ville.skytta at iki.fi (Ville =?ISO-8859-1?Q?Skytt=E4?=) Date: Wed, 09 Aug 2006 19:00:46 +0300 Subject: add FE-Legal to ReviewGuidelines In-Reply-To: <20060809101856.GB29291@rathann.pekin.waw.pl> References: <20060808150750.GA3131@free.fr> <20060808201146.GC15994@rathann.pekin.waw.pl> <44D98751.3070805@fedoraproject.org> <20060809101856.GB29291@rathann.pekin.waw.pl> Message-ID: <1155139246.2997.224.camel@localhost.localdomain> On Wed, 2006-08-09 at 12:18 +0200, Dominik 'Rathann' Mierzejewski wrote: > On Wednesday, 09 August 2006 at 08:57, Rahul wrote: > > Dominik 'Rathann' Mierzejewski wrote: > > > > >Since we're on the subject of FE-Legal, how long does one have > > >to wait for any response? mkvtoolnix has been waiting for a long > > >time... https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177134 > > > > > > > Did someone actually ask legal this question? I dont see any comments > > that suggest that. > > I was under impression that Ville did, but maybe I was mistaken. You are not. In this particular case, I have asked other FESCO members in January, discussed with some of them on IRC about it later (getting comments like "legal doesn't deal with issues like that" without getting an answer to "well, who to contact, then?"), and a month or so ago pinged Max Spevack after his clarification [0] who to contact about legal issues. He quickly ack'd the ping, but I haven't heard back since. Max, any news about this one? I've also tried some other channels than the above over time in other cases, including the official ones whatever they were at the time, but pretty much consistently failed to get answers :( [0] https://www.redhat.com/archives/fedora-advisory-board/2006-July/msg00090.html From wolfy at nobugconsulting.ro Wed Aug 9 16:03:13 2006 From: wolfy at nobugconsulting.ro (Manuel Wolfshant) Date: Wed, 09 Aug 2006 19:03:13 +0300 Subject: Query on the owners.list In-Reply-To: <1155138130.3106.12.camel@localhost.localdomain> References: <1155138130.3106.12.camel@localhost.localdomain> Message-ID: <44DA0741.8080608@nobugconsulting.ro> PFJ wrote: > Hi, > > There looks to be two identical packages in the owners list > > ddrescue and dd_rescue. > > They both contain the same description and are packaged by the same > person. Can anyone say if they are the same package and if they are, why > there are two copies in FE (or at least the owners list)? > > TTFN > > Paul > AFAIR, the packages contain two different implementations of the same functions. they overlap, but not completely. There was a thread about them some [looong] time ago. From cweyl at alumni.drew.edu Wed Aug 9 16:24:37 2006 From: cweyl at alumni.drew.edu (Chris Weyl) Date: Wed, 9 Aug 2006 09:24:37 -0700 Subject: FE @ LinuxWorld SF 2006? Message-ID: <7dd7ab490608090924u93521c0lcb79c1c70ec80a5d@mail.gmail.com> Is anyone planning on going to LinuxWorld? I live locally, and it's always nice to put faces to names if anyone is going to be around... -Chris -- Chris Weyl Ex astris, scientia From laurent.rineau__fedora_extras at normalesup.org Wed Aug 9 16:38:34 2006 From: laurent.rineau__fedora_extras at normalesup.org (Laurent Rineau) Date: Wed, 9 Aug 2006 18:38:34 +0200 Subject: python package: pyo files Message-ID: <200608091838.34782@rineau.schtroumpfette> The guidelines for python packages, at http://fedoraproject.org/wiki/Packaging/Python, explain how to make the .pyo files be uninstalled, if the package is uninstalled. Actually, those guidelines are quite ambiguous: can a package ship .pyo files or not? Since rpm-build-4.4.1-0.1 (Dec 05 2004), the rpm macro __os_install_post contains /usr/lib/rpm/brp-python-bytecompile, which compiles .py files into .pyc and .pyo. From toshio at tiki-lounge.com Wed Aug 9 16:40:42 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Wed, 09 Aug 2006 09:40:42 -0700 Subject: FE @ LinuxWorld SF 2006? In-Reply-To: <7dd7ab490608090924u93521c0lcb79c1c70ec80a5d@mail.gmail.com> References: <7dd7ab490608090924u93521c0lcb79c1c70ec80a5d@mail.gmail.com> Message-ID: <1155141642.3027.5.camel@localhost> On Wed, 2006-08-09 at 09:24 -0700, Chris Weyl wrote: > Is anyone planning on going to LinuxWorld? I live locally, and it's > always nice to put faces to names if anyone is going to be around... I registered for a free pass for the floor. I wasn't sure which day(s) I'd go for, though. Is there going to be a Fedora BoF or any events at the Fedora Booth? (We do have a booth, right? Not just an add on to the Red Hat booth?) -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From cweyl at alumni.drew.edu Wed Aug 9 16:44:30 2006 From: cweyl at alumni.drew.edu (Chris Weyl) Date: Wed, 9 Aug 2006 09:44:30 -0700 Subject: FE @ LinuxWorld SF 2006? In-Reply-To: <1155141642.3027.5.camel@localhost> References: <7dd7ab490608090924u93521c0lcb79c1c70ec80a5d@mail.gmail.com> <1155141642.3027.5.camel@localhost> Message-ID: <7dd7ab490608090944u62b0af2bu8b6af7ed8a7d9e29@mail.gmail.com> On 8/9/06, Toshio Kuratomi wrote: > On Wed, 2006-08-09 at 09:24 -0700, Chris Weyl wrote: > > Is anyone planning on going to LinuxWorld? I live locally, and it's > > always nice to put faces to names if anyone is going to be around... > > I registered for a free pass for the floor. I wasn't sure which day(s) > I'd go for, though. Is there going to be a Fedora BoF or any events at > the Fedora Booth? (We do have a booth, right? Not just an add on to > the Red Hat booth?) >From the post to the -announce list, it does look like a booth. (Though there's no map I can see, so I don't know if it's an addon or not.) There's a BoF session on 8/15 from 6-7PM, and hopefully us exhibit-pass holders can get into that. -Chris -- Chris Weyl Ex astris, scientia From mr.ecik at gmail.com Wed Aug 9 16:46:58 2006 From: mr.ecik at gmail.com (=?ISO-8859-2?Q?Micha=B3_Bentkowski?=) Date: Wed, 9 Aug 2006 18:46:58 +0200 Subject: python package: pyo files In-Reply-To: <200608091838.34782@rineau.schtroumpfette> References: <200608091838.34782@rineau.schtroumpfette> Message-ID: <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> 2006/8/9, Laurent Rineau : > Actually, those guidelines are quite ambiguous: can a package ship .pyo files > or not? It is really ambigous... IMHO .pyo shouldn't be added to package and this is done by doing %ghost macro. From toshio at tiki-lounge.com Wed Aug 9 16:54:01 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Wed, 09 Aug 2006 09:54:01 -0700 Subject: python package: pyo files In-Reply-To: <200608091838.34782@rineau.schtroumpfette> References: <200608091838.34782@rineau.schtroumpfette> Message-ID: <1155142441.3027.17.camel@localhost> On Wed, 2006-08-09 at 18:38 +0200, Laurent Rineau wrote: > The guidelines for python packages, at > http://fedoraproject.org/wiki/Packaging/Python, explain how to make the .pyo > files be uninstalled, if the package is uninstalled. > > Actually, those guidelines are quite ambiguous: can a package ship .pyo files > or not? > For a reason. It's packager's discretion right now. The .pyo files have little practical benefit so that's a reason to %ghost them. OTOH the space savings from %ghost'ing the .pyo's is also small so that's a reason for just including them and not worrying about the space. I personally ghost because every little bit helps when you are a space limited device. The only thing what's disallowed is not listing the .pyo's in the %files section at all. > Since rpm-build-4.4.1-0.1 (Dec 05 2004), the rpm macro __os_install_post > contains /usr/lib/rpm/brp-python-bytecompile, which compiles .py files > into .pyc and .pyo. > If someone will remind me of which FC version this was added in I'll add this to the page: As of FCX, rpm automatically compiles to .pyc and .pyo files for you. As long as you are not going to build your package on versions older than that you do not need to manually byte compile the files. You still need to include the files in your %files section, though. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From laurent.rineau__fedora_extras at normalesup.org Wed Aug 9 16:57:01 2006 From: laurent.rineau__fedora_extras at normalesup.org (Laurent Rineau) Date: Wed, 9 Aug 2006 18:57:01 +0200 Subject: python package: pyo files In-Reply-To: <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> References: <200608091838.34782@rineau.schtroumpfette> <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> Message-ID: <200608091857.01885@rineau.schtroumpfette> On Wednesday 09 August 2006 18:46, Micha? Bentkowski wrote: > 2006/8/9, Laurent Rineau : > > Actually, those guidelines are quite ambiguous: can a package ship .pyo > > files or not? > > It is really ambigous... IMHO .pyo shouldn't be added to package and > this is done by doing %ghost macro. I do not know the reason, but since last December, .pyo files are created after %install stage by rpmbuild itself. I am not used to Python, actually. I have no personal thought about that. Debian policy states that packages must not even ship .pyc of .pyo files. Instead they must be generated in the postint stage, and removed in postun. See http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-bytecompilation I am sure to understand the rational of that choice. From katzj at redhat.com Wed Aug 9 17:03:09 2006 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 09 Aug 2006 13:03:09 -0400 Subject: python package: pyo files In-Reply-To: <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> References: <200608091838.34782@rineau.schtroumpfette> <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> Message-ID: <1155142989.14414.15.camel@aglarond.local> On Wed, 2006-08-09 at 18:46 +0200, Micha? Bentkowski wrote: > 2006/8/9, Laurent Rineau : > > Actually, those guidelines are quite ambiguous: can a package ship .pyo files > > or not? > It is really ambigous... IMHO .pyo shouldn't be added to package and > this is done by doing %ghost macro. They need to be present so that things can end up with the correct SELinux context -- otherwise, if you run a python app with -O2 as a user, you end up getting various avc denials Jeremy From laurent.rineau__fedora_extras at normalesup.org Wed Aug 9 17:03:08 2006 From: laurent.rineau__fedora_extras at normalesup.org (Laurent Rineau) Date: Wed, 9 Aug 2006 19:03:08 +0200 Subject: python package: pyo files In-Reply-To: <1155142441.3027.17.camel@localhost> References: <200608091838.34782@rineau.schtroumpfette> <1155142441.3027.17.camel@localhost> Message-ID: <200608091903.08500@rineau.schtroumpfette> On Wednesday 09 August 2006 18:54, Toshio Kuratomi wrote: > The only thing what's disallowed is not listing the .pyo's in the %files > section at all. > > > Since rpm-build-4.4.1-0.1 (Dec 05 2004), the rpm macro __os_install_post > > contains /usr/lib/rpm/brp-python-bytecompile, which compiles .py files > > into .pyc and .pyo. > > If someone will remind me of which FC version this was added in I'll add > this to the page: > > As of FCX, rpm automatically compiles to .pyc and .pyo files for you. > As long as you are not going to build your package on versions older > than that you do not need to manually byte compile the files. You still > need to include the files in your %files section, though. FC-4, if I understand CVS logs well. Can you add a paragraph that tells explicitly that shipping or ghosting the .pyo file is packager's discretion? You should even precise that .pyc must be shipped in the package. Do you see why Debian do not ship .pyc files? It seems that it allows to re-bytecompile all .pyc files, when at a python upgrade, without bumping packages version. From paul at all-the-johnsons.co.uk Sun Aug 6 09:54:28 2006 From: paul at all-the-johnsons.co.uk (Paul) Date: Sun, 06 Aug 2006 10:54:28 +0100 Subject: Not sure about this error on a package I'm about to submit for FE Message-ID: <1154858068.4220.60.camel@T7.Linux> Hi, I've packaged VisualOS for inclusion in extras and it builds fine outside of mock. However, in mock, I've getting an error that gnomeConf.sh cannot be found. In the %build section, I've added --with-gnome=%{_libdir} to the build configure line, but the build always fails that the script can't find gnomeConf.sh in the libdir, despite it being there. Any clues on how to fix this problem? TTFN Paul -- Wenn sie denken, dass die bildung teuer ist, versuchen sie ignoranz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From rdieter at math.unl.edu Wed Aug 9 17:29:49 2006 From: rdieter at math.unl.edu (Rex Dieter) Date: Wed, 09 Aug 2006 12:29:49 -0500 Subject: Not sure about this error on a package I'm about to submit for FE References: <1154858068.4220.60.camel@T7.Linux> Message-ID: Paul wrote: > I've packaged VisualOS for inclusion in extras and it builds fine > outside of mock. However, in mock, I've getting an error that > gnomeConf.sh cannot be found. > > In the %build section, I've added --with-gnome=%{_libdir} to the build > configure line, but the build always fails that the script can't find > gnomeConf.sh in the libdir, despite it being there. > > Any clues on how to fix this problem? I'd say go ahead and submit it for review. With the actual package handy, I'm sure it will get sorted out. -- Rex From icon at fedoraproject.org Wed Aug 9 17:32:21 2006 From: icon at fedoraproject.org (Konstantin Ryabitsev) Date: Wed, 9 Aug 2006 13:32:21 -0400 Subject: python package: pyo files In-Reply-To: <1155142989.14414.15.camel@aglarond.local> References: <200608091838.34782@rineau.schtroumpfette> <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> <1155142989.14414.15.camel@aglarond.local> Message-ID: On 8/9/06, Jeremy Katz wrote: > They need to be present so that things can end up with the correct > SELinux context -- otherwise, if you run a python app with -O2 as a > user, you end up getting various avc denials So, what does that mean in terms of %ghost? Cheers, -- Konstantin Ryabitsev Montr?al, Qu?bec From toshio at tiki-lounge.com Wed Aug 9 18:16:46 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Wed, 09 Aug 2006 11:16:46 -0700 Subject: python package: pyo files In-Reply-To: <1155142989.14414.15.camel@aglarond.local> References: <200608091838.34782@rineau.schtroumpfette> <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> <1155142989.14414.15.camel@aglarond.local> Message-ID: <1155147407.3027.22.camel@localhost> On Wed, 2006-08-09 at 13:03 -0400, Jeremy Katz wrote: > On Wed, 2006-08-09 at 18:46 +0200, Micha? Bentkowski wrote: > > 2006/8/9, Laurent Rineau : > > > Actually, those guidelines are quite ambiguous: can a package ship .pyo files > > > or not? > > It is really ambigous... IMHO .pyo shouldn't be added to package and > > this is done by doing %ghost macro. > > They need to be present so that things can end up with the correct > SELinux context -- otherwise, if you run a python app with -O2 as a > user, you end up getting various avc denials Unless I'm misremembering the issue, you get AVC denials in the logs due to python's just-in-time byte compilation trying to write out the .pyo file. The program should still run fine. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From triad at df.lth.se Wed Aug 9 20:43:19 2006 From: triad at df.lth.se (Linus Walleij) Date: Wed, 9 Aug 2006 22:43:19 +0200 (CEST) Subject: Overriding kernel modules In-Reply-To: <44D9B864.3070707@kelkoo.net> References: <44D8F6BE.80504@kelkoo.net> <1155087584.4288.5.camel@vader.jdub.homelinux.org> <44D9AA64.2050006@kelkoo.net> <44D9B864.3070707@kelkoo.net> Message-ID: On Wed, 9 Aug 2006, Xavier Bachelot wrote: >> I though the term "tainted" refered to a kernel linking kernel modules >> that aren't GPL, i.e. a legal issue, not just any new kernel modules. >> > Yes, you're right, that the original meaning, but from a support pov, its > also tainted, that's what I meant. (...) I would call that "tainting fedora core" not "tainting the kernel" but when its clear what you mean I guess it doesn't matter much... Linus From katzj at redhat.com Wed Aug 9 20:45:52 2006 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 09 Aug 2006 16:45:52 -0400 Subject: python package: pyo files In-Reply-To: References: <200608091838.34782@rineau.schtroumpfette> <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> <1155142989.14414.15.camel@aglarond.local> Message-ID: <1155156352.22203.20.camel@aglarond.local> On Wed, 2006-08-09 at 13:32 -0400, Konstantin Ryabitsev wrote: > On 8/9/06, Jeremy Katz wrote: > > They need to be present so that things can end up with the correct > > SELinux context -- otherwise, if you run a python app with -O2 as a > > user, you end up getting various avc denials > > So, what does that mean in terms of %ghost? That it's not a good idea and the .pyo files should just be included in the package Jeremy From katzj at redhat.com Wed Aug 9 20:47:37 2006 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 09 Aug 2006 16:47:37 -0400 Subject: python package: pyo files In-Reply-To: <1155147407.3027.22.camel@localhost> References: <200608091838.34782@rineau.schtroumpfette> <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> <1155142989.14414.15.camel@aglarond.local> <1155147407.3027.22.camel@localhost> Message-ID: <1155156457.22203.23.camel@aglarond.local> On Wed, 2006-08-09 at 11:16 -0700, Toshio Kuratomi wrote: > On Wed, 2006-08-09 at 13:03 -0400, Jeremy Katz wrote: > > On Wed, 2006-08-09 at 18:46 +0200, Micha? Bentkowski wrote: > > > 2006/8/9, Laurent Rineau : > > > > Actually, those guidelines are quite ambiguous: can a package ship .pyo files > > > > or not? > > > It is really ambigous... IMHO .pyo shouldn't be added to package and > > > this is done by doing %ghost macro. > > > > They need to be present so that things can end up with the correct > > SELinux context -- otherwise, if you run a python app with -O2 as a > > user, you end up getting various avc denials > > Unless I'm misremembering the issue, you get AVC denials in the logs due > to python's just-in-time byte compilation trying to write out the .pyo > file. The program should still run fine. Sure, but denials (even when things end up working properly) still lead people to believe that there's a problem. Jeremy From jkeating at redhat.com Wed Aug 9 20:54:31 2006 From: jkeating at redhat.com (Jesse Keating) Date: Wed, 9 Aug 2006 16:54:31 -0400 Subject: python package: pyo files In-Reply-To: <1155156352.22203.20.camel@aglarond.local> References: <200608091838.34782@rineau.schtroumpfette> <1155156352.22203.20.camel@aglarond.local> Message-ID: <200608091654.31541.jkeating@redhat.com> On Wednesday 09 August 2006 16:45, Jeremy Katz wrote: > On Wed, 2006-08-09 at 13:32 -0400, Konstantin Ryabitsev wrote: > > On 8/9/06, Jeremy Katz wrote: > > > They need to be present so that things can end up with the correct > > > SELinux context -- otherwise, if you run a python app with -O2 as a > > > user, you end up getting various avc denials > > > > So, what does that mean in terms of %ghost? > > That it's not a good idea and the .pyo files should just be included in > the package This is reason enough for me to amend the Python packaging rule for this. If you want .pyo, do it when building and package them up. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From toshio at tiki-lounge.com Wed Aug 9 21:14:37 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Wed, 09 Aug 2006 14:14:37 -0700 Subject: python package: pyo files In-Reply-To: <1155156457.22203.23.camel@aglarond.local> References: <200608091838.34782@rineau.schtroumpfette> <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> <1155142989.14414.15.camel@aglarond.local> <1155147407.3027.22.camel@localhost> <1155156457.22203.23.camel@aglarond.local> Message-ID: <1155158077.3027.119.camel@localhost> On Wed, 2006-08-09 at 16:47 -0400, Jeremy Katz wrote: > On Wed, 2006-08-09 at 11:16 -0700, Toshio Kuratomi wrote: > > > > Unless I'm misremembering the issue, you get AVC denials in the logs due > > to python's just-in-time byte compilation trying to write out the .pyo > > file. The program should still run fine. > > Sure, but denials (even when things end up working properly) still lead > people to believe that there's a problem. > So why isn't SELinux allowing python to write the file or using a dontaudit rule to not print an audit message for those denials? SELinux is supposed to prevent things that are unexpected from happening. python is expected to attempt to write the .pyo. (The write can still fail based on file permissions as normal without logging an AVC denial, right?) I could be missing something that you'll point out next, but it seems like we're solving the symptom rather than the issue. Perhaps I'll be using Fedora as a basis for a file server on a flash DOM. I remove all the .pyo's manually to save space and enable SELinux to help contain any security holes. Because I'm a silly goose, I've set PYTHONOPTIMIZE="yes". Now I've got tons of AVC messages.... I know just enough SELinux to be dangerous, so feel free to educate me. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From steve at silug.org Wed Aug 9 20:59:32 2006 From: steve at silug.org (Steven Pritchard) Date: Wed, 9 Aug 2006 15:59:32 -0500 Subject: Query on the owners.list In-Reply-To: <1155138130.3106.12.camel@localhost.localdomain> References: <1155138130.3106.12.camel@localhost.localdomain> Message-ID: <20060809205932.GA3452@osiris.silug.org> On Wed, Aug 09, 2006 at 04:42:10PM +0100, PFJ wrote: > There looks to be two identical packages in the owners list > > ddrescue and dd_rescue. They aren't identical. https://www.redhat.com/archives/fedora-extras-list/2005-June/msg00782.html There is no dd_rescue in Extras. The owners.list entry is bogus. The ddrescue package in Extras *should* be called dd_rescue, since it is the original dd_rescue renamed. We don't have GNU ddrescue (http://www.gnu.org/software/ddrescue/ddrescue.html) packaged for Extras. I volunteered to fix this mess last year, but it looked like Andreas Thienemann was going to take care of it. Unfortunately the pre-bugzilla review requests never went anywhere, so the fix never happened. Apparently everyone involved hasn't had time for it in the post-bugzilla-review-request era. FWIW, my main motivation for fixing all this was to get dd_rhelp (http://www.kalysto.org/utilities/dd_rhelp/index.en.html) in Extras, but I've since decided it is a hopeless mess. Oh, and GNU ddrescue is supposed to do what dd_rhelp + dd_rescue are supposed to do, but it has never worked right for me, so I've just been using dd_rescue, restarting it manually if necessary. Steve -- Steven Pritchard - K&S Pritchard Enterprises, Inc. Email: steve at kspei.com http://www.kspei.com/ Phone: (618)398-3000 Mobile: (618)567-7320 From katzj at redhat.com Wed Aug 9 21:23:52 2006 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 09 Aug 2006 17:23:52 -0400 Subject: python package: pyo files In-Reply-To: <1155158077.3027.119.camel@localhost> References: <200608091838.34782@rineau.schtroumpfette> <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> <1155142989.14414.15.camel@aglarond.local> <1155147407.3027.22.camel@localhost> <1155156457.22203.23.camel@aglarond.local> <1155158077.3027.119.camel@localhost> Message-ID: <1155158632.25038.2.camel@aglarond.local> On Wed, 2006-08-09 at 14:14 -0700, Toshio Kuratomi wrote: > On Wed, 2006-08-09 at 16:47 -0400, Jeremy Katz wrote: > > On Wed, 2006-08-09 at 11:16 -0700, Toshio Kuratomi wrote: > > > > > > Unless I'm misremembering the issue, you get AVC denials in the logs due > > > to python's just-in-time byte compilation trying to write out the .pyo > > > file. The program should still run fine. > > > > Sure, but denials (even when things end up working properly) still lead > > people to believe that there's a problem. > > > So why isn't SELinux allowing python to write the file or using a > dontaudit rule to not print an audit message for those denials? SELinux > is supposed to prevent things that are unexpected from happening. > python is expected to attempt to write the .pyo. (The write can still > fail based on file permissions as normal without logging an AVC denial, > right?) Well, allowing normal users to write to /usr seems like a bad idea would be first on my list of "why not allow it" ;-) As for having a dontaudit rule, it's difficult as you can be talking about *anything* written in python here. eg, think about having foo.py in your homedir and just running it -- it's not going to have any special context to be able to dontaudit writes to user. And in general, if an application is trying to do that, we _do_ want to know so that it can be fixed, so it's not practical to dontaudit all attempts to write to /usr. Jeremy From katzj at redhat.com Wed Aug 9 21:24:47 2006 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 09 Aug 2006 17:24:47 -0400 Subject: python package: pyo files In-Reply-To: <200608091654.31541.jkeating@redhat.com> References: <200608091838.34782@rineau.schtroumpfette> <1155156352.22203.20.camel@aglarond.local> <200608091654.31541.jkeating@redhat.com> Message-ID: <1155158687.25038.4.camel@aglarond.local> On Wed, 2006-08-09 at 16:54 -0400, Jesse Keating wrote: > On Wednesday 09 August 2006 16:45, Jeremy Katz wrote: > > On Wed, 2006-08-09 at 13:32 -0400, Konstantin Ryabitsev wrote: > > > On 8/9/06, Jeremy Katz wrote: > > > > They need to be present so that things can end up with the correct > > > > SELinux context -- otherwise, if you run a python app with -O2 as a > > > > user, you end up getting various avc denials > > > > > > So, what does that mean in terms of %ghost? > > > > That it's not a good idea and the .pyo files should just be included in > > the package > > This is reason enough for me to amend the Python packaging rule for this. > > If you want .pyo, do it when building and package them up. ... they automatically get generated with current redhat-rpm-config (and with what was shipped in FC5... possibly even FC4, but I'd have to go look and am too lazy to do that atm ;-). The key is just making sure you include them in your package's %files Jeremy From toshio at tiki-lounge.com Wed Aug 9 21:24:52 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Wed, 09 Aug 2006 14:24:52 -0700 Subject: python package: pyo files In-Reply-To: <200608091654.31541.jkeating@redhat.com> References: <200608091838.34782@rineau.schtroumpfette> <1155156352.22203.20.camel@aglarond.local> <200608091654.31541.jkeating@redhat.com> Message-ID: <1155158692.3027.130.camel@localhost> On Wed, 2006-08-09 at 16:54 -0400, Jesse Keating wrote: > On Wednesday 09 August 2006 16:45, Jeremy Katz wrote: > > On Wed, 2006-08-09 at 13:32 -0400, Konstantin Ryabitsev wrote: > > > On 8/9/06, Jeremy Katz wrote: > > > > They need to be present so that things can end up with the correct > > > > SELinux context -- otherwise, if you run a python app with -O2 as a > > > > user, you end up getting various avc denials > > > > > > So, what does that mean in terms of %ghost? > > > > That it's not a good idea and the .pyo files should just be included in > > the package > > This is reason enough for me to amend the Python packaging rule for this. > > If you want .pyo, do it when building and package them up. > Err. I think you're misunderstanding. End-users (well, the root user on the consumer's system) can generate .pyos by running python -O PROGRAM or PYTHONOPTIMIZE="yes" PROGRAM. This is because python will create the byte compiled files automatically when it is run. So the packager has to either include the .pyos or %ghost the pyos to solve that. The packager can't make the decision to not deal with .pyo's at all. Jeremy's position is that in the case where an end-user has PYTHONOPTIMIZE set and SELinux enabled, they are going to generate extraneous AVC denials in the logs. So packages should all include the .pyos, not ghost them. My position is that it's expected behaviour for python to attempt to create the .pyos so SELinux policy should be adapted to not log an error when that happens and %ghosting should be fine. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From shahms at shahms.com Wed Aug 9 22:01:52 2006 From: shahms at shahms.com (Shahms King) Date: Wed, 09 Aug 2006 15:01:52 -0700 Subject: python package: pyo files In-Reply-To: <1155156352.22203.20.camel@aglarond.local> References: <200608091838.34782@rineau.schtroumpfette> <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> <1155142989.14414.15.camel@aglarond.local> <1155156352.22203.20.camel@aglarond.local> Message-ID: <44DA5B50.4000103@shahms.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeremy Katz wrote: > On Wed, 2006-08-09 at 13:32 -0400, Konstantin Ryabitsev wrote: >> On 8/9/06, Jeremy Katz wrote: >>> They need to be present so that things can end up with the correct >>> SELinux context -- otherwise, if you run a python app with -O2 as a >>> user, you end up getting various avc denials >> So, what does that mean in terms of %ghost? > > That it's not a good idea and the .pyo files should just be included in > the package > > Jeremy If this is the case, then the packaging guidelines and python spec template need to be updated to indicate this as they currently require %ghost'ing the .pyo files. I'd be happy to update the Wiki, if that's the new "best practices," but someone else will need to fix the python spec template in fedora-rpmdevtools. - --Shahms -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFE2lkY/qs2NkWy11sRApeSAJ0bWUnOSp0SpshPFF+N4Rwa4yyaAACgl098 IObYtjV2Vuic9ZfTZ3Lxnro= =FxZO -----END PGP SIGNATURE----- From bugs.michael at gmx.net Wed Aug 9 22:52:22 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Thu, 10 Aug 2006 00:52:22 +0200 Subject: Package Signing/GPG Key Management Questions In-Reply-To: <44C4FA19.3030908@tycho.ncsc.mil> References: <44C4FA19.3030908@tycho.ncsc.mil> Message-ID: <20060810005222.5814b691.bugs.michael@gmx.net> On Mon, 24 Jul 2006 12:49:29 -0400, Chris wrote: > Could someone shed light on the process for GPG signing of packages in > the Extras repository? Limited knowledge only: A few people (from Red Hat and the community) have access to the key and its pass-phrase. Packages built on the build clients are collected by the build master [server] and stored in the "needsign" queue. The packages from that queue are not published into the master repository automatically. The people with access to the key need to start a manual process (aka the extras-push script) which prompts for the pass-phrase, signs the packages and installs them into the master repository as appropriate. > I briefly searched the archives, but found only > an inconclusive argument about its usefulness. What have you found? Obviously, signed packages (particularly when signed manually) have the benefit that they cannot be modified once they enter the network of repository mirrors. And it is not possible to infiltrate any repository with faked signed packages as long as you don't have access to the key (and passphrase in this case). > How does the Extras package signing process differ from Base/Updates? Only somebody who knows the Core signing-process can answer that. > I know RPM-GPG-KEY-fedora-extras sits alongside RPM-GPG-KEY-fedora, but > who has control of the Extras signing key? The group mentioned above. > Is checking for a CLA on > file the extent of vetting done to submitted packages (assuming they > meet all other packaging criteria outlined in the Wiki)? Currently, the CLA and sponsorship (by an Extras contributor who has got "sponsor" privileges) are the prerequisites to getting access to CVS and the build system for submission of build jobs. > It would be most helpful to have a sketch of what the ultimate signer (a > RH employee?) does before he/she decides it's OK to sign the package > with the official fedora-extras key. With the high number of packages which are built and upgraded every day, it is impossible for a human being to apply any security relevant post-build checks to individual packages. Verifying binary rpms without examining src.rpm tarball contents and build dependency chains is impossible. Monitoring of CVS commits, builds and releases must be done by the entire community of Users, Developers and Packagers. It is particularly important that packagers peruse the build logs they receive from the build system. Plus, the system administrators must keep all servers involved secure. From Christian.Iseli at licr.org Wed Aug 9 23:32:21 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Thu, 10 Aug 2006 01:32:21 +0200 Subject: FE Package Status of Aug 10, 2006 Message-ID: <20060810013221.1a8dab9a@ludwig-alpha> Hi folks, Here is this week's report. I tried to come up with some reasonable criteria to filter a bit the missing packages from the comps.xml file. That still leaves over 700 missing... so please have a look and add them where you think it's appropriate. A rough guesstimate of what should go in comps.xml is found here http://fedoraproject.org/wiki/Extras/CompsXml I know I still need to clean that page... that'll come. (or someone else can beat me to it... I won't hold grudges... :-) ) For the moment, I used those rules to filter the packages: ignore a package named P-xxx if a package named P is in Core or Extras ignore packages where the string "plugin" appears in their name ignore packages with names starting with: lib compat- font(s)- gtk- kmod- xfce4- ignore packages with names ending with: -devel lib(s0-9) -python -perl -server(s) -client(s) -tool(s) -contrib(s) -doc(s) -(x)emacs -util(s) -font(s) There are also some cases of non-existent packages listed in comps.xml. I think they should be removed when we prepare the branching of FC6... Cheers, Christian ---- FE Package Status of Aug 10, 2006 The full report can be found here: http://fedoraproject.org/wiki/Extras/PackageStatus Owners file stats: - 2081 packages - 37 orphans - 32 packages not available in extras devel or release Fedora at FamilleCollet dot com php-pecl-zip Fedora at FamilleCollet dot com php-pear-HTTP cgoorah at yahoo dot com dot au kadischi cweyl at alumni dot drew dot edu perl-DateTime-Format-Builder davidhart at tqmcube dot com leafnode dennis at ausil dot us oooqs2 enrico dot scholz at informatik dot tu-chemnitz dot de x11-ssh-askpass fredrik at dolda2000 dot com icmpdn gauret at free dot fr agave ghenry at suretecsystems dot com gnome-applet-netmon ifoox at redhat dot com ht2html ivazquez at ivazquez dot net gpredict jpo at di dot uminho dot pt perl-Test-Builder-Tester matthias at rpmforge dot net fillets-ng-data-cs notting at redhat dot com comps oliver at linux-kernel dot at squidGuard paul at all-the-johnsons dot co dot uk db4o paul at all-the-johnsons dot co dot uk genchemlab rpm at greysector dot net libtlen rpm at greysector dot net openbabel rvinyard at cs dot nmsu dot edu conexus splinux at fedoraproject dot org gstm tcallawa at redhat dot com perl-Maypole tcallawa at redhat dot com R-RScaLAPACK tcallawa at redhat dot com libgdamm tcallawa at redhat dot com R-hdf5 tcallawa at redhat dot com opendap toniw at iki dot fi silky toniw at iki dot fi libmatchbox toshio at tiki-lounge dot com hula wolters dot liste at gmx dot net ktorrent wtogami at redhat dot com iiimf-le-simplehangul - 6 packages not available in extras devel but present in release andreas at bawue dot net echoping andreas at bawue dot net mboxgrep ivazquez at ivazquez dot net gnome-applet-rhythmbox paul at xtdnet dot nl s3switch ville dot skytta at iki dot fi em8300-kmod ville dot skytta at iki dot fi em8300 - 1 packages which have not yet been FE-APPROVE'd... https://bugzilla.redhat.com/bugzilla/buglist.cgi?bug_id=189375 Maelstrom notting at redhat.com - 2 packages present in the development repo which have no owners entry BackupPC ip6sic - 3 orphaned packages, yet available in extras devel dxpc gtkglarea2 soundtracker - 45 packages that moved to core Packages appearing both in Core and Extras: - 5 packages duplicated for devel: jpo at di dot uminho dot pt perl-Net-SSLeay jpo at di dot uminho dot pt perl-IO-Socket-SSL jpo at di dot uminho dot pt perl-Socket6 petersen at redhat dot com scim-bridge tagoh at redhat dot com paps FE-ACCEPT packages stats: - 1130 accepted, closed package reviews - 6 accepted, closed package reviews not in repo - 1 accepted, closed package reviews not in owners - 7 accepted, open package reviews older than 4 weeks; - 8 accepted, open package reviews with a package already in the repo FE-REVIEW packages stats: - 114 open tickets - 20 tickets with no activity in eight weeks - 25 tickets with no activity in four weeks - 3 closed tickets FE-NEW packages stats: - 180 open tickets - 24 tickets with no activity in eight weeks - 45 tickets with no activity in four weeks FE-NEEDSPONSOR packages stats: - 45 open tickets - 4 tickets with no activity in eight weeks - 10 tickets with no activity in four weeks FE-LEGAL packages stats: - 2 open tickets FE-GUIDELINES packages stats: - 13 open tickets - 12 tickets with no activity in four weeks OPEN-BUGS packages stats: - 254 open tickets - 145 tickets with no activity in eight weeks - 37 tickets with no activity in four weeks CVS stats: - 2052 packages with a devel directory - 6 packages with no owners entry BackupPC initng ip6sic muse php-apc zoo - 4 packages in CVS devel *and* Core dogtail libevent pam_pkcs11 pyspi - 107 packages were dropped from extras Maintainers stats: - 217 maintainers - 19 inactive maintainers with open bugs - 22 inactive maintainers Dropped FC packages: - 270 packages were dropped from core since FC 1 Comps.xml files stats: - 442 packages in comps-fe6 file - 771 packages missing from comps-fe6 file - 20 packages in comps-fe6 but not in repo - 441 packages in comps-fe5 file - 757 packages missing from comps-fe5 file - 17 packages in comps-fe5 but not in repo From buildsys at fedoraproject.org Wed Aug 9 23:36:13 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Wed, 9 Aug 2006 19:36:13 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-09 Message-ID: <20060809233613.E506A152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 26 XaraLX-0.7-3.fc5.r1614 abcMIDI-20060805-1.fc5 agave-0.4.0-1.fc5 aplus-fsf-4.20.2-9.fc5 celestia-1.4.1-4.fc5 clamav-0.88.4-1.fc5 conexus-0.2.3-2.fc5 gcdmaster-1.2.1-5.fc5 geomview-1.8.2-0.18.rc8.fc5 ghex-2.8.2-2.fc5 inkscape-0.44-3.fc5 ksynaptics-0.3.1-2.fc5 libsynaptics-0.14.6b-2.fc5 libtlen-0-0.4.20060309.fc5 perl-DateTime-Format-Builder-0.7807-3.fc5 perl-Devel-Cover-0.58-1.fc5 perl-Error-0.17001-1.fc5 perl-Log-Dispatch-2.12-1.fc5 perl-Module-Build-0.2805-1.fc5 perl-Module-CoreList-2.07-1.fc5 perl-Module-Starter-PBP-0.000003-4.fc5 perl-Pod-Coverage-0.18-2.fc5 perl-SVK-1.08-4.fc5 perl-Test-Memory-Cycle-1.04-1.fc5 perl-YAML-0.62-1.fc5 python-irclib-0.4.6-1.fc5 Packages built and released for Fedora Extras 4: 11 abcMIDI-20060805-1.fc4 aplus-fsf-4.20.2-9.fc4.1 clamav-0.88.4-1.fc4 conexus-0.2.3-2.fc4 libtlen-0-0.4.20060309.fc4 perl-DateTime-Format-Builder-0.7807-3.fc4 perl-Log-Dispatch-2.12-1.fc4 perl-Module-CoreList-2.07-1.fc4 perl-Module-Starter-PBP-0.000003-4.fc4 perl-Pod-Coverage-0.18-2.fc4 perl-SVK-1.08-4.fc4 Packages built and released for Fedora Extras 3: 1 clamav-0.88.4-1.fc3 Packages built and released for Fedora Extras development: 35 Macaulay2-0.9.20-0.3.20060808svn.fc6 Terminal-0.2.5.4-0.1.beta2.fc6 abcMIDI-20060805-1.fc6 agave-0.4.0-1.fc6 aplus-fsf-4.20.2-9.fc6 clamav-0.88.4-1.fc6 conexus-0.2.3-2.fc6 db4o-5.5-8.fc6 exo-0.3.1.8-0.1.beta2.fc6 gcdmaster-1.2.1-5.fc6 genchemlab-1.0-4.fc6 geomview-1.8.2-0.18.rc8.fc6 ghex-2.8.2-2.fc6 glib-1.2.10-22.fc6 gtk+-1.2.10-54.fc6 inkscape-0.44-3.fc6 jasper-1.701.0-12.fc6 k3b-extras-0.12.16-1.fc6 kdemultimedia-extras-3.5.4-3.fc6 libmpcdec-1.2.2-3.fc6 libtlen-0-0.4.20060309.fc6 maxima-5.9.3.99-0.4.rc2.fc6 obby-0.4.0-6.rc3.fc6 openslp-1.2.1-5.fc6 perl-DateTime-Format-Builder-0.7807-3.fc6 perl-Devel-Cover-0.58-1.fc6 perl-Error-0.17001-1.fc6 perl-Log-Dispatch-2.12-1.fc6 perl-Module-Build-0.2805-1.fc6 perl-Module-CoreList-2.07-1.fc6 perl-Pod-Coverage-0.18-2.fc6 perl-SVK-1.08-4.fc6 perl-Test-Memory-Cycle-1.04-1.fc6 python-irclib-0.4.6-1.fc6 x11-ssh-askpass-1.2.4.1-1.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Wed Aug 9 23:36:47 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Wed, 9 Aug 2006 19:36:47 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-09 Message-ID: <20060809233647.2E37D152169@buildsys.fedoraproject.org> azureus: green AT redhat.com 5: 0:2.4.0.3-0.20060529cvs_1.fc5 (FE5) 6: 0:2.4.0.3-0.20060328cvs_5.fc6 (FE6) camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) digikam: mgarski AT post.pl 3: 0:0.8.2-2.fc3 (FE3) 4: 0:0.8.2-1.fc4 (FE4) 5: 0:0.8.2-1.fc5 (FE5) 6: 0:0.8.2-1.fc6 (FE6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) dogtail: zcerza AT redhat.com 5: 0:0.5.2-2.fc5 (FE5) 6: 0:0.5.2-1.fc6 (FC6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: liljencrantz AT gmail.com 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gaim-gaym: cweyl AT alumni.drew.edu 5: 0:0.96-3.fc5 (FE5) 6: 0:0.96-2.fc6 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) koffice: andreas.bierfert AT lowlatency.de 5: 0:1.5.2-1.fc5 (FE5) 6: 0:1.5.1-2.fc6 (FE6) libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) libpqxx: andreas.bierfert AT lowlatency.de 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) lvm2: 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) mozilla: 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) mtools: 5: 0:3.9.10-2.fc5 (FC5-updates) 6: 0:3.9.10-1.2.2 (FC6) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.1-2.fc5 (FE5) 6: 0:1.0.1-1.fc5 (FE6) quagga: 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) seamonkey: kengert AT redhat.com 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) smart: Axel.Thimm AT ATrpms.net 5: 0:0.42-35.fc5 (FE5) 6: 0:0.41-31.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.5-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) vorbisgain: noa AT resare.com 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) XaraLX: paul AT all-the-johnsons.co.uk 5: 0:0.7-3.fc5.r1614 (FE5) 6: 0:0.7-2.fc6.r1614 (FE6) ypbind: 5: 3:1.19-1 (FC5-updates) 6: 3:1.19-0.3 (FC6) From Christian.Iseli at licr.org Wed Aug 9 23:46:33 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Thu, 10 Aug 2006 01:46:33 +0200 Subject: Package database, SCM, ACLs, co-maintainership, and all that stuff In-Reply-To: <1154748486.2632.27.camel@lt16858.campus.dmacc.edu> References: <20060805011530.1aaf09b3@ludwig-alpha> <1154748486.2632.27.camel@lt16858.campus.dmacc.edu> Message-ID: <20060810014633.29a8d590@ludwig-alpha> On Fri, 04 Aug 2006 22:28:05 -0500, Jeffrey C. Ollie wrote: > * Before a build is initiated, the initiator would have to "approve" > somehow all of the changes made by non-maintainers. Not quite sure how > this would work, esp. given the need to track reversions of unapproved > changes. Thinking some more on the issue of "controlling" what gets built/published, I came up with this idea: basically, what needs to be "approved" at some point is a particular set of file revision numbers in a SCM repository. In CVS we have tags. The problem with tags is that they can be forcibly moved using -F, but if we admit for a second that we have a mean to forbid any tag movement, then I think we have a pretty easy solution to control things. The approved maintainers of a particular package for a particular release (and even a particular arch) are allowed to define which is the current valid tag for said package within the package database. Once we have that mechanism in place, anyone can hack the sources and request builds: it doesn't really matter as long as we only build/publish package SRPMs assembled from a valid tag. I'm not sure I'm explaining this very clearly (I need to get some sleep real quick) so please ask if things are not clear... Cheers, Christian From buildsys at fedoraproject.org Wed Aug 9 23:56:56 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Wed, 09 Aug 2006 23:56:56 -0000 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-09 Message-ID: <20060809235656.13898.72305@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- Jochen AT herr-schmitt.de blender - 2.42-5.fc6.i386 blender - 2.42-5.fc6.ppc blender - 2.42-5.fc6.x86_64 andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (125 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (125 days) koffice-langpack-af - 1.5.2-1.fc6.noarch koffice-langpack-af - 1.5.2-1.fc6.noarch koffice-langpack-af - 1.5.2-1.fc6.noarch koffice-langpack-ar - 1.5.2-1.fc6.noarch koffice-langpack-ar - 1.5.2-1.fc6.noarch koffice-langpack-ar - 1.5.2-1.fc6.noarch koffice-langpack-bg - 1.5.2-1.fc6.noarch koffice-langpack-bg - 1.5.2-1.fc6.noarch koffice-langpack-bg - 1.5.2-1.fc6.noarch koffice-langpack-br - 1.5.2-1.fc6.noarch koffice-langpack-br - 1.5.2-1.fc6.noarch koffice-langpack-br - 1.5.2-1.fc6.noarch koffice-langpack-bs - 1.5.2-1.fc6.noarch koffice-langpack-bs - 1.5.2-1.fc6.noarch koffice-langpack-bs - 1.5.2-1.fc6.noarch koffice-langpack-ca - 1.5.2-1.fc6.noarch koffice-langpack-ca - 1.5.2-1.fc6.noarch koffice-langpack-ca - 1.5.2-1.fc6.noarch koffice-langpack-cs - 1.5.2-1.fc6.noarch koffice-langpack-cs - 1.5.2-1.fc6.noarch koffice-langpack-cs - 1.5.2-1.fc6.noarch koffice-langpack-cy - 1.5.2-1.fc6.noarch koffice-langpack-cy - 1.5.2-1.fc6.noarch koffice-langpack-cy - 1.5.2-1.fc6.noarch koffice-langpack-da - 1.5.2-1.fc6.noarch koffice-langpack-da - 1.5.2-1.fc6.noarch koffice-langpack-da - 1.5.2-1.fc6.noarch koffice-langpack-de - 1.5.2-1.fc6.noarch koffice-langpack-de - 1.5.2-1.fc6.noarch koffice-langpack-de - 1.5.2-1.fc6.noarch koffice-langpack-el - 1.5.2-1.fc6.noarch koffice-langpack-el - 1.5.2-1.fc6.noarch koffice-langpack-el - 1.5.2-1.fc6.noarch koffice-langpack-en_GB - 1.5.2-1.fc6.noarch koffice-langpack-en_GB - 1.5.2-1.fc6.noarch koffice-langpack-en_GB - 1.5.2-1.fc6.noarch koffice-langpack-eo - 1.5.2-1.fc6.noarch koffice-langpack-eo - 1.5.2-1.fc6.noarch koffice-langpack-eo - 1.5.2-1.fc6.noarch koffice-langpack-es - 1.5.2-1.fc6.noarch koffice-langpack-es - 1.5.2-1.fc6.noarch koffice-langpack-es - 1.5.2-1.fc6.noarch koffice-langpack-et - 1.5.2-1.fc6.noarch koffice-langpack-et - 1.5.2-1.fc6.noarch koffice-langpack-et - 1.5.2-1.fc6.noarch koffice-langpack-eu - 1.5.2-1.fc6.noarch koffice-langpack-eu - 1.5.2-1.fc6.noarch koffice-langpack-eu - 1.5.2-1.fc6.noarch koffice-langpack-fi - 1.5.2-1.fc6.noarch koffice-langpack-fi - 1.5.2-1.fc6.noarch koffice-langpack-fi - 1.5.2-1.fc6.noarch koffice-langpack-fr - 1.5.2-1.fc6.noarch koffice-langpack-fr - 1.5.2-1.fc6.noarch koffice-langpack-fr - 1.5.2-1.fc6.noarch koffice-langpack-ga - 1.5.2-1.fc6.noarch koffice-langpack-ga - 1.5.2-1.fc6.noarch koffice-langpack-ga - 1.5.2-1.fc6.noarch koffice-langpack-he - 1.5.2-1.fc6.noarch koffice-langpack-he - 1.5.2-1.fc6.noarch koffice-langpack-he - 1.5.2-1.fc6.noarch koffice-langpack-hi - 1.5.2-1.fc6.noarch koffice-langpack-hi - 1.5.2-1.fc6.noarch koffice-langpack-hi - 1.5.2-1.fc6.noarch koffice-langpack-hu - 1.5.2-1.fc6.noarch koffice-langpack-hu - 1.5.2-1.fc6.noarch koffice-langpack-hu - 1.5.2-1.fc6.noarch koffice-langpack-is - 1.5.2-1.fc6.noarch koffice-langpack-is - 1.5.2-1.fc6.noarch koffice-langpack-is - 1.5.2-1.fc6.noarch koffice-langpack-it - 1.5.2-1.fc6.noarch koffice-langpack-it - 1.5.2-1.fc6.noarch koffice-langpack-it - 1.5.2-1.fc6.noarch koffice-langpack-ja - 1.5.2-1.fc6.noarch koffice-langpack-ja - 1.5.2-1.fc6.noarch koffice-langpack-ja - 1.5.2-1.fc6.noarch koffice-langpack-lt - 1.5.2-1.fc6.noarch koffice-langpack-lt - 1.5.2-1.fc6.noarch koffice-langpack-lt - 1.5.2-1.fc6.noarch koffice-langpack-mk - 1.5.2-1.fc6.noarch koffice-langpack-mk - 1.5.2-1.fc6.noarch koffice-langpack-mk - 1.5.2-1.fc6.noarch koffice-langpack-ms - 1.5.2-1.fc6.noarch koffice-langpack-ms - 1.5.2-1.fc6.noarch koffice-langpack-ms - 1.5.2-1.fc6.noarch koffice-langpack-nb - 1.5.2-1.fc6.noarch koffice-langpack-nb - 1.5.2-1.fc6.noarch koffice-langpack-nb - 1.5.2-1.fc6.noarch koffice-langpack-nl - 1.5.2-1.fc6.noarch koffice-langpack-nl - 1.5.2-1.fc6.noarch koffice-langpack-nl - 1.5.2-1.fc6.noarch koffice-langpack-nn - 1.5.2-1.fc6.noarch koffice-langpack-nn - 1.5.2-1.fc6.noarch koffice-langpack-nn - 1.5.2-1.fc6.noarch koffice-langpack-pl - 1.5.2-1.fc6.noarch koffice-langpack-pl - 1.5.2-1.fc6.noarch koffice-langpack-pl - 1.5.2-1.fc6.noarch koffice-langpack-pt - 1.5.2-1.fc6.noarch koffice-langpack-pt - 1.5.2-1.fc6.noarch koffice-langpack-pt - 1.5.2-1.fc6.noarch koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch koffice-langpack-ro - 1.5.2-1.fc6.noarch koffice-langpack-ro - 1.5.2-1.fc6.noarch koffice-langpack-ro - 1.5.2-1.fc6.noarch koffice-langpack-ru - 1.5.2-1.fc6.noarch koffice-langpack-ru - 1.5.2-1.fc6.noarch koffice-langpack-ru - 1.5.2-1.fc6.noarch koffice-langpack-se - 1.5.2-1.fc6.noarch koffice-langpack-se - 1.5.2-1.fc6.noarch koffice-langpack-se - 1.5.2-1.fc6.noarch koffice-langpack-sk - 1.5.2-1.fc6.noarch koffice-langpack-sk - 1.5.2-1.fc6.noarch koffice-langpack-sk - 1.5.2-1.fc6.noarch koffice-langpack-sl - 1.5.2-1.fc6.noarch koffice-langpack-sl - 1.5.2-1.fc6.noarch koffice-langpack-sl - 1.5.2-1.fc6.noarch koffice-langpack-sr - 1.5.2-1.fc6.noarch koffice-langpack-sr - 1.5.2-1.fc6.noarch koffice-langpack-sr - 1.5.2-1.fc6.noarch koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch koffice-langpack-sv - 1.5.2-1.fc6.noarch koffice-langpack-sv - 1.5.2-1.fc6.noarch koffice-langpack-sv - 1.5.2-1.fc6.noarch koffice-langpack-ta - 1.5.2-1.fc6.noarch koffice-langpack-ta - 1.5.2-1.fc6.noarch koffice-langpack-ta - 1.5.2-1.fc6.noarch koffice-langpack-tg - 1.5.2-1.fc6.noarch koffice-langpack-tg - 1.5.2-1.fc6.noarch koffice-langpack-tg - 1.5.2-1.fc6.noarch koffice-langpack-tr - 1.5.2-1.fc6.noarch koffice-langpack-tr - 1.5.2-1.fc6.noarch koffice-langpack-tr - 1.5.2-1.fc6.noarch koffice-langpack-uk - 1.5.2-1.fc6.noarch koffice-langpack-uk - 1.5.2-1.fc6.noarch koffice-langpack-uk - 1.5.2-1.fc6.noarch koffice-langpack-uz - 1.5.2-1.fc6.noarch koffice-langpack-uz - 1.5.2-1.fc6.noarch koffice-langpack-uz - 1.5.2-1.fc6.noarch koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch libopensync-plugin-evolution2 - 0.18-6.fc5.i386 libopensync-plugin-evolution2 - 0.18-6.fc5.ppc libopensync-plugin-evolution2 - 0.18-6.fc5.x86_64 wine-core - 0.9.17-1.fc6.i386 (14 days) bdpepple AT ameritech.net contact-lookup-applet - 0.14-3.fc6.i386 contact-lookup-applet - 0.14-3.fc6.ppc contact-lookup-applet - 0.14-3.fc6.x86_64 liferea - 1.0.20-4.fc6.i386 liferea - 1.0.20-4.fc6.ppc liferea - 1.0.20-4.fc6.x86_64 byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (21 days) gaim-guifications - 2.12-3.fc5.ppc (21 days) gaim-guifications - 2.12-3.fc5.x86_64 (21 days) cweyl AT alumni.drew.edu gaim-gaym - 0.96-2.fc6.i386 (21 days) gaim-gaym - 0.96-2.fc6.ppc (21 days) gaim-gaym - 0.96-2.fc6.x86_64 (21 days) dennis AT ausil.us knetworkmanager - 0.1-0.3.svn20060625.fc6.i386 (20 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.ppc (20 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.x86_64 (20 days) fedora AT leemhuis.info gsynaptics - 0.9.8-1.fc6.ppc (21 days) gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (13 days) amarok - 1.4.1-3.fc6.ppc (13 days) showimg-pgsql - 0.9.5-7.fc4.i386 showimg-pgsql - 0.9.5-7.fc4.ppc showimg-pgsql - 0.9.5-7.fc4.x86_64 showimg-pgsql - 0.9.5-7.fc5.i386 showimg-pgsql - 0.9.5-7.fc5.ppc showimg-pgsql - 0.9.5-7.fc5.x86_64 green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.i386 (14 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (14 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.x86_64 (14 days) jogl - 1.1.1-14.fc5.ppc (17 days) ivazquez AT ivazquez.net deskbar-applet - 2.14.1.1-1.fc6.i386 deskbar-applet - 2.14.1.1-1.fc6.ppc deskbar-applet - 2.14.1.1-1.fc6.x86_64 gnome-applet-music - 0.9.0-1.fc6.i386 (21 days) gnome-applet-music - 0.9.0-1.fc6.ppc (21 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (21 days) nautilus-search-tool - 0.2-1.fc5.i386 (21 days) nautilus-search-tool - 0.2-1.fc5.ppc (21 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (21 days) jkeating AT redhat.com contacts - 0.1-1.i386 contacts - 0.1-1.ppc contacts - 0.1-1.x86_64 lmacken AT redhat.com python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.i386 (25 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.ppc (25 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.x86_64 (25 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.i386 (25 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.ppc (25 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.x86_64 (25 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (21 days) gfontview - 0.5.0-5.fc5.ppc (21 days) gfontview - 0.5.0-5.fc5.x86_64 (21 days) gtkhtml36 - 3.6.2-5.fc6.i386 (21 days) gtkhtml36 - 3.6.2-5.fc6.ppc (21 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (21 days) libvisual-plugins - 0.2.0-3.fc5.i386 (21 days) libvisual-plugins - 0.2.0-3.fc5.i386 (21 days) libvisual-plugins - 0.2.0-3.fc5.ppc (21 days) libvisual-plugins - 0.2.0-3.fc5.ppc (21 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (21 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (21 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (84 days) syck-php - 0.55-7.fc5.i386 (84 days) syck-php - 0.55-7.fc5.ppc (84 days) syck-php - 0.55-7.fc5.ppc (84 days) syck-php - 0.55-7.fc5.x86_64 (84 days) syck-php - 0.55-7.fc5.x86_64 (84 days) petersen AT redhat.com ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.i386 ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.ppc ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.x86_64 rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (21 days) libibverbs - 1.0.3-1.fc6.ppc (21 days) libibverbs - 1.0.3-1.fc6.x86_64 (21 days) libibverbs-utils - 1.0.3-1.fc6.i386 (21 days) libibverbs-utils - 1.0.3-1.fc6.ppc (21 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (21 days) tcallawa AT redhat.com gambas-runtime - 1.0.14-2.fc5.i386 thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (21 days) directfb - 0.9.24-5.fc5.ppc (21 days) directfb - 0.9.24-5.fc5.x86_64 (21 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.i386 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc5.i386 requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) python-ruledispatch-0.5a0-0.1.svnr2115.fc5.x86_64 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc5.x86_64 requires libpqxx-2.6.6.so()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.ppc requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc5.ppc requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.i386 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc4.i386 requires libpqxx-2.6.6.so Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.x86_64 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc4.x86_64 requires libpqxx-2.6.6.so()(64bit) Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.ppc requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc4.ppc requires libpqxx-2.6.6.so Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.i386 requires libgcj.so.7 blender-2.42-5.fc6.i386 requires libgettextlib-0.14.5.so contact-lookup-applet-0.14-3.fc6.i386 requires libebook-1.2.so.5 contacts-0.1-1.i386 requires libebook-1.2.so.5 deskbar-applet-2.14.1.1-1.fc6.i386 requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.i386 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 gambas-runtime-1.0.14-2.fc5.i386 requires libgettextlib-0.14.5.so gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-2.fc6.i386 requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-qt-1.so.1 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 liferea-1.0.20-4.fc6.i386 requires firefox = 0:1.5.0.5 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- azureus-2.4.0.3-0.20060328cvs_5.fc6.x86_64 requires libgcj.so.7()(64bit) blender-2.42-5.fc6.x86_64 requires libgettextlib-0.14.5.so()(64bit) contact-lookup-applet-0.14-3.fc6.x86_64 requires libebook-1.2.so.5()(64bit) contacts-0.1-1.x86_64 requires libebook-1.2.so.5()(64bit) deskbar-applet-2.14.1.1-1.fc6.x86_64 requires libebook-1.2.so.5()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-gaym-0.96-2.fc6.x86_64 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) ghc642-gtk2hs-mozembed-0.9.10-2.fc6.x86_64 requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-qt-1.so.1()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-1.so.2()(64bit) koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libedata-cal-1.2.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libecal-1.2.so.3()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libebook-1.2.so.5()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) liferea-1.0.20-4.fc6.x86_64 requires firefox = 0:1.5.0.5 nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.17-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 blender-2.42-5.fc6.ppc requires libgettextlib-0.14.5.so contact-lookup-applet-0.14-3.fc6.ppc requires libebook-1.2.so.5 contacts-0.1-1.ppc requires libebook-1.2.so.5 deskbar-applet-2.14.1.1-1.fc6.ppc requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.ppc requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-2.fc6.ppc requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gsynaptics-0.9.8-1.fc6.ppc requires synaptics gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-qt-1.so.1 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 liferea-1.0.20-4.fc6.ppc requires firefox = 0:1.5.0.5 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 ====================================================================== New report for: andreas.bierfert AT lowlatency.de package: wine-core - 0.9.17-1.fc6.i386 from fedora-extras-development-x86_64 unresolved deps: libglut.so.3 ====================================================================== New report for: petersen AT redhat.com package: ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.i386 from fedora-extras-development-i386 unresolved deps: firefox-devel = 0:1.5.0.5 package: ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: firefox-devel = 0:1.5.0.5 package: ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.ppc from fedora-extras-development-ppc unresolved deps: firefox-devel = 0:1.5.0.5 ====================================================================== New report for: green AT redhat.com package: azureus - 2.4.0.3-0.20060328cvs_5.fc6.i386 from fedora-extras-development-i386 unresolved deps: libgcj.so.7 package: azureus - 2.4.0.3-0.20060328cvs_5.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libgcj.so.7()(64bit) package: azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc from fedora-extras-development-ppc unresolved deps: libgcj.so.7 ====================================================================== New report for: bdpepple AT ameritech.net package: liferea - 1.0.20-4.fc6.i386 from fedora-extras-development-i386 unresolved deps: firefox = 0:1.5.0.5 package: liferea - 1.0.20-4.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: firefox = 0:1.5.0.5 package: liferea - 1.0.20-4.fc6.ppc from fedora-extras-development-ppc unresolved deps: firefox = 0:1.5.0.5 From toshio at tiki-lounge.com Thu Aug 10 00:12:32 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Wed, 09 Aug 2006 17:12:32 -0700 Subject: python package: pyo files In-Reply-To: <1155158632.25038.2.camel@aglarond.local> References: <200608091838.34782@rineau.schtroumpfette> <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> <1155142989.14414.15.camel@aglarond.local> <1155147407.3027.22.camel@localhost> <1155156457.22203.23.camel@aglarond.local> <1155158077.3027.119.camel@localhost> <1155158632.25038.2.camel@aglarond.local> Message-ID: <1155168752.3027.160.camel@localhost> On Wed, 2006-08-09 at 17:23 -0400, Jeremy Katz wrote: > On Wed, 2006-08-09 at 14:14 -0700, Toshio Kuratomi wrote: > > So why isn't SELinux allowing python to write the file or using a > > dontaudit rule to not print an audit message for those denials? SELinux > > is supposed to prevent things that are unexpected from happening. > > python is expected to attempt to write the .pyo. (The write can still > > fail based on file permissions as normal without logging an AVC denial, > > right?) > > Well, allowing normal users to write to /usr seems like a bad idea would > be first on my list of "why not allow it" ;-) > That should be prevented by normal Unix file permissions ;-) > As for having a dontaudit rule, it's difficult as you can be talking > about *anything* written in python here. eg, think about having foo.py > in your homedir and just running it -- it's not going to have any > special context to be able to dontaudit writes to user. > > And in general, if an application is trying to do that, we _do_ want to > know so that it can be fixed, so it's not practical to dontaudit all > attempts to write to /usr. It sounds like SELinux isn't flexible enough to do what I wish it could in this circumstance. :-) In experimenting I've found what I think is a python bug which I think swings the argument in your favor for a different reason as well. python -O and python -OO both generate .pyos. However, python won't overwrite a pyo that is already generated. I'll have to do a bit of googling, but I think that's a bug. If we %ghost all the pyos and then a system administrator runs python -OO [All sorts of python programs] he'll end up with a large number of files without docstrings. If some of programs need those docstrings to operate, he'll start getting tracebacks. At this point, running python -O [PROGRAM] won't work because python will reuse the existing pyo instead of creating a new one at the reduced optimization level. The sys admin will have to rm all the .pyos on the system to get all his docstrings back. By the same token, because the .pyos are not overwritten, if we precreate the .pyos the system administrator will not be able to replace the .pyos without first rm'ing them. So it would make sense to include the pyos so the system administrator can't get into a broken state without first knowing how to fix it. If this bug is ever fixed, though, then we could see a case where we get AVC denials again. We install python -O optimized pyos for foo. The user runs python -OO foo and suddenly python will want to overwrite the .pyos with ones that are byte compiled at a different optimization level. So including the .pyos is fixing a symptom, not the cause. A complete solution has to come from SELinux, not from tweaks we put in the spec file. (BTW: In case it wasn't obvious, I think it does make sense to deprecate the usage of %ghost with .pyos, at least for now.) -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From jkeating at redhat.com Thu Aug 10 03:16:10 2006 From: jkeating at redhat.com (Jesse Keating) Date: Wed, 9 Aug 2006 23:16:10 -0400 Subject: Package Signing/GPG Key Management Questions In-Reply-To: <20060810005222.5814b691.bugs.michael@gmx.net> References: <44C4FA19.3030908@tycho.ncsc.mil> <20060810005222.5814b691.bugs.michael@gmx.net> Message-ID: <200608092316.10423.jkeating@redhat.com> On Wednesday 09 August 2006 18:52, Michael Schwendt wrote: > > How does the Extras package signing process differ from Base/Updates? > > Only somebody who knows the Core signing-process can answer that. Core works like this. We have a database that holds a collection of packages. It knows where these packages live on the file system. When it comes to release time, I run a script that checks for a specific gpg sig on every package in the collection. If the signature isn't there, rpm sign it (prompting me for the passphrase). Once every package is signed with the right key, then I spin a tree for release. Updates work somewhat like Extras. A developer builds a package for an update, uses a web tool to request the package be released as an update (filling in things like why the update exists, what bugs it might fix, whether its for -testing or final updates, etc.. I get alerted that there is a pending update and I use a tool to move the package to the correct package collection, sign the package, toss it in a staging area for updates, and syncs out to the outside world, and sends email the developer created. VERY few people know the passphrase for the fedora-testing and fedora-final key. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From panemade at gmail.com Thu Aug 10 07:34:40 2006 From: panemade at gmail.com (=?UTF-8?Q?Parag_N(=E0=A4=AA=E0=A4=B0=E0=A4=BE=E0=A5=9A)?=) Date: Thu, 10 Aug 2006 13:04:40 +0530 Subject: Local repository setup problem with fedora-mirror.py Message-ID: Hi, I was using local repositories setup for mock build successfully on FC5 previously. Now i formatted my system and installed FC6 Test 2 and tried to follow the same steps that i did from my page http://fedoraproject.org/wiki/ParagNemade/MockSetupUsingLocalMirror When i try to execute python script i am getting errors as [root at localhost parag]# python fedora-mirror.py syncing: Fedora development core i386 binary to /mirror_repo Traceback (most recent call last): File "/usr/bin/reposync", line 43, in ? from repomd.packageSack import ListPackageSack ImportError: No module named repomd.packageSack syncing: Fedora development extras i386 binary to /mirror_repo Traceback (most recent call last): File "/usr/bin/reposync", line 43, in ? from repomd.packageSack import ListPackageSack ImportError: No module named repomd.packageSack [root at localhost parag]# Do i need any changes to fedora-mirror.py script or anything else i am missing?? Regards, Parag. From j.w.r.degoede at hhs.nl Thu Aug 10 09:39:35 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Thu, 10 Aug 2006 11:39:35 +0200 Subject: FE Package Status of Aug 10, 2006 In-Reply-To: <20060810013221.1a8dab9a@ludwig-alpha> References: <20060810013221.1a8dab9a@ludwig-alpha> Message-ID: <44DAFED7.5000300@hhs.nl> Christian Iseli wrote: > Hi folks, > > Here is this week's report. I tried to come up with some reasonable > criteria to filter a bit the missing packages from the comps.xml file. > That still leaves over 700 missing... so please have a look and add > them where you think it's appropriate. > > A rough guesstimate of what should go in comps.xml is found here > http://fedoraproject.org/wiki/Extras/CompsXml > > I know I still need to clean that page... that'll come. (or someone > else can beat me to it... I won't hold grudges... :-) ) > > For the moment, I used those rules to filter the packages: > ignore a package named P-xxx if a package named P is in Core or Extras > ignore packages where the string "plugin" appears in their name > ignore packages with names starting with: > lib > compat- > font(s)- > gtk- > kmod- > xfce4- > ignore packages with names ending with: > -devel > lib(s0-9) > -python > -perl > -server(s) > -client(s) > -tool(s) > -contrib(s) > -doc(s) > -(x)emacs > -util(s) > -font(s) > > There are also some cases of non-existent packages listed in > comps.xml. I think they should be removed when we prepare the > branching of FC6... > I've been running through the list of packages I own which are listed in your status report as missing from comps. Many of them are valid (and have been added), but there are also quite a few false positives: * AllegroOGG (library) * Glide3 (library) * Hermes (library) * adime (library) * arc (cmdline tool) * bin2iso (cmdline tool) * coldet (library) * dumb (library) * glyph-keeper (library) * goffice (library) * lzo (library) * ode (library) * ogre (library) * soundtouch (library) How do we handle these, blacklist them? (Maybe hidden somewhere in the wiki so that you don't have to maintain the blacklist?) Regards, Hans From Axel.Thimm at ATrpms.net Thu Aug 10 10:29:27 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Thu, 10 Aug 2006 12:29:27 +0200 Subject: FE-NEW \ FE-NEEDSPONSOR Message-ID: <20060810102927.GB25950@neu.nirvana> Hi, is there a way to query in bugzilla all unassigned review requests that don't need a sponsor? For some strange reason whenever I see a package I'd like to review it requires a sponsor, so I'd like a filtering method for non-sponsors :) -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Axel.Thimm at ATrpms.net Thu Aug 10 10:39:00 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Thu, 10 Aug 2006 12:39:00 +0200 Subject: FE Package Status of Aug 10, 2006 In-Reply-To: <20060810013221.1a8dab9a@ludwig-alpha> References: <20060810013221.1a8dab9a@ludwig-alpha> Message-ID: <20060810103900.GC25950@neu.nirvana> On Thu, Aug 10, 2006 at 01:32:21AM +0200, Christian Iseli wrote: > For the moment, I used those rules to filter the packages: > ignore a package named P-xxx if a package named P is in Core or Extras > ignore packages where the string "plugin" appears in their name > ignore packages with names starting with: > lib > compat- > font(s)- > gtk- > kmod- > xfce4- > ignore packages with names ending with: > -devel > lib(s0-9) > -python > -perl > -server(s) > -client(s) > -tool(s) > -contrib(s) > -doc(s) > -(x)emacs > -util(s) > -font(s) Wouldn't it be better to have some kind of (fake) full installation of all comps.xml content + dependencies (something like the old rpmdb package using --justdb like semantics) and filter out the packages that were installed as dependencies - or even easier all packages that were installed that way? The remaining packages are exact those that are inaccessible from comps.xml and these are the ones we'd like to deal with. For example ignoring all -devel packages in comps.xml is bad, why shouldn't a user be able to develop on his system? The FC comps does include development groups for instance. If yum has --justdb support it would be very easy, if not, maybe it's trivial for Seth or someone else to add it to yum, if it makes sense. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From j.w.r.degoede at hhs.nl Thu Aug 10 10:54:25 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Thu, 10 Aug 2006 12:54:25 +0200 Subject: The bug squad is hiring! Message-ID: <44DB1061.7020508@hhs.nl> Hi all, Introducing the bug squad: Currently there is not much to introduce except for this idea in my head. Last friday I started a thread about collecting and fixing pet peeve bugs, the idea behind this thread was to build a collection of bugs which are high on the annoyance ladder and are fixable by mere mortals. Building such a collection is just the start however, the next step is to build a team of volunteers to tackle these bugs: the bug squad. I myself will be part of the team, and I'm looking for partners in crime to squash all those nasty bugs. So what is expected of a bug squad member? Well the nescesarry skills to hunt down and fix bugs of course and some time to spare and invest, thats about all. And the rewards, well beside enormous fame the biggest reward will be a better distro and a better Linux landscape in general with less bugs and thus more fun. So come on and sign up today! --- So what will the bug squad do once formed? *The* purpose is to fix bugs. That is a but of a wide scope however, so the main purpose is to fix those bugs which affect a large audience and which are fixable with the skills and capabilities available in the bug squad. Also this will be strictly about bugs, not about behavioral changes (like the gnome file selector discussions), we might do simple RFE's if and only if upstream agrees its an enhancement. We will also need to devise some way for people to bring bugs which match our MO to our attention and some coordination to avoid debugging the same bug with 3 people at the same time, but that will all come, once we have our most important asset: People. So come on and sign up today! Regards, Hans p.s. Here is a list of bugs collected from the pet peeve bug discussion to get us started, filtered somewhat to weed out any behavioral change requests: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188079 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=106552 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131428 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187268 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=168660 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177823 From dan at danny.cz Thu Aug 10 11:50:48 2006 From: dan at danny.cz (Dan Hor=?ISO-8859-2?Q?=E1?=k) Date: Thu, 10 Aug 2006 13:50:48 +0200 Subject: FE-NEW \ FE-NEEDSPONSOR Message-ID: <200608101350.AA174325938@danny.cz> Hi, could you look at Code::Blocks IDE (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201674) Dan From jkeating at redhat.com Thu Aug 10 12:08:40 2006 From: jkeating at redhat.com (Jesse Keating) Date: Thu, 10 Aug 2006 08:08:40 -0400 Subject: Local repository setup problem with fedora-mirror.py In-Reply-To: References: Message-ID: <200608100808.40694.jkeating@redhat.com> On Thursday 10 August 2006 03:34, Parag N(????) wrote: > ?File "/usr/bin/reposync", line 43, in ? > ? ?from repomd.packageSack import ListPackageSack > ImportError: No module named repomd.packageSack > [root at localhost parag]# > > Do i need any changes to fedora-mirror.py script or anything else i am > missing?? Regards, Yum api is in flux. Open up /usr/bin/reposync, and chnage 'repomd.packageSack' to 'yum.packageSack'. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mtasaka at ioa.s.u-tokyo.ac.jp Thu Aug 10 12:14:15 2006 From: mtasaka at ioa.s.u-tokyo.ac.jp (Mamoru Tasaka) Date: Thu, 10 Aug 2006 21:14:15 +0900 Subject: Please someone review jfbterm (bug 201170) Message-ID: <44DB2317.4020400@ioa.s.u-tokyo.ac.jp> Hello. I submitted the review request for jfbterm as https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201170 , however, by now I received no responce against this for one week. Currently, on FC(andFE)5 there is no way to see Japanese (or Korean and so on) characters correctly on CUI with frame buffer. So I hope I can release this package on FE5 ASAP. This package bears no rpmlint complaint and can be rebuilt in mock cleanly, so I think this package can be accepted soon. So, please someone review this bug? I already have another package in FE, so I don't need a sponsor. BTW, when must I think that my review request is currently ignored and I should ask for someone to review it? From panemade at gmail.com Thu Aug 10 12:31:58 2006 From: panemade at gmail.com (=?UTF-8?Q?Parag_N(=E0=A4=AA=E0=A4=B0=E0=A4=BE=E0=A5=9A)?=) Date: Thu, 10 Aug 2006 18:01:58 +0530 Subject: Local repository setup problem with fedora-mirror.py In-Reply-To: <200608100808.40694.jkeating@redhat.com> References: <200608100808.40694.jkeating@redhat.com> Message-ID: Hi, On 8/10/06, Jesse Keating wrote: > On Thursday 10 August 2006 03:34, Parag N(????) wrote: > > File "/usr/bin/reposync", line 43, in ? > > from repomd.packageSack import ListPackageSack > > ImportError: No module named repomd.packageSack > > [root at localhost parag]# > > > > Do i need any changes to fedora-mirror.py script or anything else i am > > missing?? Regards, > > Yum api is in flux. > > Open up /usr/bin/reposync, and chnage 'repomd.packageSack' > to 'yum.packageSack'. Now i got [root at localhost parag]# python fedora-mirror.py syncing: Fedora development core i386 binary to /mirror_repo /usr/lib/python2.4/site-packages/yum/plugins.py:381: DeprecationWarning: registerOpt() will go away in a future version of Yum. Please manipulate config.YumConf and config.RepoConf directly. DeprecationWarning) Traceback (most recent call last): File "/usr/bin/reposync", line 193, in ? main() File "/usr/bin/reposync", line 115, in main my.doConfigSetup(fn=opts.config) File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 121, in doConfigSetup startupconf.pluginconfpath) File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 220, in doPluginSetup plugin_types, confpath) File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 136, in __init__ self.run('config') File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 152, in run func(conduitcls(self, self.base, conf, **kwargs)) File "/usr/lib/yum-plugins/downloadonly.py", line 26, in config_hook parser.add_option('', '--downloadonly', dest='dlonly', action='store_true', AttributeError: 'NoneType' object has no attribute 'add_option' syncing: Fedora development extras i386 binary to /mirror_repo /usr/lib/python2.4/site-packages/yum/plugins.py:381: DeprecationWarning: registerOpt() will go away in a future version of Yum. Please manipulate config.YumConf and config.RepoConf directly. DeprecationWarning) Traceback (most recent call last): File "/usr/bin/reposync", line 193, in ? main() File "/usr/bin/reposync", line 115, in main my.doConfigSetup(fn=opts.config) File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 121, in doConfigSetup startupconf.pluginconfpath) File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 220, in doPluginSetup plugin_types, confpath) File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 136, in __init__ self.run('config') File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 152, in run func(conduitcls(self, self.base, conf, **kwargs)) File "/usr/lib/yum-plugins/downloadonly.py", line 26, in config_hook parser.add_option('', '--downloadonly', dest='dlonly', action='store_true', AttributeError: 'NoneType' object has no attribute 'add_option' [root at localhost parag]# Regards, Parag. From denis at poolshark.org Thu Aug 10 12:42:43 2006 From: denis at poolshark.org (Denis Leroy) Date: Thu, 10 Aug 2006 14:42:43 +0200 Subject: The bug squad is hiring! In-Reply-To: <44DB1061.7020508@hhs.nl> References: <44DB1061.7020508@hhs.nl> Message-ID: <44DB29C3.9020504@poolshark.org> Hans de Goede wrote: > Hi all, > > Introducing the bug squad: Currently there is not much to introduce > except for this idea in my head. Last friday I started a thread about > collecting and fixing pet peeve bugs, the idea behind this thread was to > build a collection of bugs which are high on the annoyance ladder and > are fixable by mere mortals. Building such a collection is just the > start however, the next step is to build a team of volunteers to tackle > these bugs: the bug squad. > > I myself will be part of the team, and I'm looking for partners in crime > to squash all those nasty bugs. So what is expected of a bug squad > member? Well the nescesarry skills to hunt down and fix bugs of course > and some time to spare and invest, thats about all. And the rewards, > well beside enormous fame the biggest reward will be a better distro and > a better Linux landscape in general with less bugs and thus more fun. > > So come on and sign up today! I'm game! The bug i wanted to fix is the "CD Burning only works as root for a buncha burners", though it requires significant effort... -denis From Christian.Iseli at licr.org Thu Aug 10 13:05:32 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Thu, 10 Aug 2006 15:05:32 +0200 Subject: FE Package Status of Aug 10, 2006 In-Reply-To: <44DAFED7.5000300@hhs.nl> References: <20060810013221.1a8dab9a@ludwig-alpha> <44DAFED7.5000300@hhs.nl> Message-ID: <20060810150532.2b7432c8@ludwig-alpha> On Thu, 10 Aug 2006 11:39:35 +0200, Hans de Goede wrote: > How do we handle these, blacklist them? Maybe. Taking a quick look, I see that most packages you described as (library) actually do have the keyword "library" in the owners.list description, so for those I could take that into account. The cmdline tools are more problematic... (As a side note: I tend to like cmdline tools, and would like to see them listed in comps.xml anyway... but maybe that's just me) Christian From dragoran at feuerpokemon.de Thu Aug 10 13:08:30 2006 From: dragoran at feuerpokemon.de (dragoran) Date: Thu, 10 Aug 2006 15:08:30 +0200 Subject: The bug squad is hiring! In-Reply-To: <44DB29C3.9020504@poolshark.org> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> Message-ID: <44DB2FCE.2080909@feuerpokemon.de> Denis Leroy wrote: > Hans de Goede wrote: >> Hi all, >> >> Introducing the bug squad: Currently there is not much to introduce >> except for this idea in my head. Last friday I started a thread about >> collecting and fixing pet peeve bugs, the idea behind this thread was to >> build a collection of bugs which are high on the annoyance ladder and >> are fixable by mere mortals. Building such a collection is just the >> start however, the next step is to build a team of volunteers to tackle >> these bugs: the bug squad. >> >> I myself will be part of the team, and I'm looking for partners in crime >> to squash all those nasty bugs. So what is expected of a bug squad >> member? Well the nescesarry skills to hunt down and fix bugs of course >> and some time to spare and invest, thats about all. And the rewards, >> well beside enormous fame the biggest reward will be a better distro and >> a better Linux landscape in general with less bugs and thus more fun. >> >> So come on and sign up today! > > I'm game! The bug i wanted to fix is the "CD Burning only works as > root for a buncha burners", though it requires significant effort... > I want this bug to be fixed too (see FC6 and cdbruning thread) but we should wait for 2.6.19 (which will allow scsi commands to be enabled for a device from userspace), we should try to backport this changes and get them in the FC kernel before FC6 is released. > -denis > From pertusus at free.fr Thu Aug 10 13:10:31 2006 From: pertusus at free.fr (Patrice Dumas) Date: Thu, 10 Aug 2006 15:10:31 +0200 Subject: Please someone review jfbterm (bug 201170) In-Reply-To: <44DB2317.4020400@ioa.s.u-tokyo.ac.jp> References: <44DB2317.4020400@ioa.s.u-tokyo.ac.jp> Message-ID: <20060810131031.GB2547@free.fr> On Thu, Aug 10, 2006 at 09:14:15PM +0900, Mamoru Tasaka wrote: > Hello. > > I submitted the review request for jfbterm as > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201170 , > however, by now I received no responce against this > for one week. One week is not unusual. Some review request are standing for more than 2 month. > BTW, when must I think that my review request is currently > ignored and I should ask for someone to review it? That's up to you. One traditional way of having people reviewing your package is to review their packages first. But doing some advertising like you just did isn't bad either. -- Pat From denis at poolshark.org Thu Aug 10 13:11:42 2006 From: denis at poolshark.org (Denis Leroy) Date: Thu, 10 Aug 2006 15:11:42 +0200 Subject: The bug squad is hiring! In-Reply-To: <44DB2FCE.2080909@feuerpokemon.de> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> <44DB2FCE.2080909@feuerpokemon.de> Message-ID: <44DB308E.40607@poolshark.org> dragoran wrote: >> The bug i wanted to fix is the "CD Burning only works as >> root for a buncha burners", though it requires significant effort... >> > I want this bug to be fixed too (see FC6 and cdbruning thread) but we > should wait for 2.6.19 > (which will allow scsi commands to be enabled for a device from > userspace), we should try to backport this changes and get them in the > FC kernel before FC6 is released. Are you referring to Peter Jones' patch ? If it's going into 2.6.19, that's great news. The job on our side is more the user-space aspect (hotplug module?)... -denis From dragoran at feuerpokemon.de Thu Aug 10 13:28:40 2006 From: dragoran at feuerpokemon.de (dragoran) Date: Thu, 10 Aug 2006 15:28:40 +0200 Subject: The bug squad is hiring! In-Reply-To: <44DB308E.40607@poolshark.org> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> <44DB2FCE.2080909@feuerpokemon.de> <44DB308E.40607@poolshark.org> Message-ID: <44DB3488.5090800@feuerpokemon.de> Denis Leroy wrote: > dragoran wrote: >>> The bug i wanted to fix is the "CD Burning only works as root for a >>> buncha burners", though it requires significant effort... >>> >> I want this bug to be fixed too (see FC6 and cdbruning thread) but we >> should wait for 2.6.19 >> (which will allow scsi commands to be enabled for a device from >> userspace), we should try to backport this changes and get them in >> the FC kernel before FC6 is released. > > Are you referring to Peter Jones' patch ? If it's going into 2.6.19, > that's great news. The job on our side is more the user-space aspect > (hotplug module?)... > yes I am talking about this patch: http://marc.theaimsgroup.com/?l=linux-scsi&m=115441532600684&w=2 as for the userspace I don't know where this should be done? I would say HAL should do it (or udev?) or let kudzu writte it to a config file and let a initscript uploads it to the kernel > -denis > From Christian.Iseli at licr.org Thu Aug 10 13:57:58 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Thu, 10 Aug 2006 15:57:58 +0200 Subject: FE-NEW \ FE-NEEDSPONSOR In-Reply-To: <20060810102927.GB25950@neu.nirvana> References: <20060810102927.GB25950@neu.nirvana> Message-ID: <20060810155758.191c9189@ludwig-alpha> On Thu, 10 Aug 2006 12:29:27 +0200, Axel Thimm wrote: > is there a way to query in bugzilla all unassigned review requests > that don't need a sponsor? > > For some strange reason whenever I see a package I'd like to review it > requires a sponsor, so I'd like a filtering method for non-sponsors :) This might do (part of) what you want... Remember people sometimes forget to block FE-NEEDSPONSOR... https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora+Extras&component=Package+Review&query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=MODIFIED&cmdtype=doit&field0-0-0=blocked&type0-0-0=equals&value0-0-0=163776&negate1=1&field1-0-0=blocked&type1-0-0=equals&value1-0-0=177841 Cheers, Christian From icon at fedoraproject.org Thu Aug 10 14:08:38 2006 From: icon at fedoraproject.org (Konstantin Ryabitsev) Date: Thu, 10 Aug 2006 10:08:38 -0400 Subject: python package: pyo files In-Reply-To: <1155156352.22203.20.camel@aglarond.local> References: <200608091838.34782@rineau.schtroumpfette> <668bb39a0608090946y40d0d618l882f1b105c64712e@mail.gmail.com> <1155142989.14414.15.camel@aglarond.local> <1155156352.22203.20.camel@aglarond.local> Message-ID: On 8/9/06, Jeremy Katz wrote: > > So, what does that mean in terms of %ghost? > > That it's not a good idea and the .pyo files should just be included in > the package Excellent. If anything, that makes the %files section SO much cleaner and easier. Let the guidelines be modified! :) Cheers, -- Konstantin Ryabitsev Montr?al, Qu?bec From mattdm at mattdm.org Thu Aug 10 14:42:23 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Thu, 10 Aug 2006 10:42:23 -0400 Subject: The bug squad is hiring! In-Reply-To: <44DB1061.7020508@hhs.nl> References: <44DB1061.7020508@hhs.nl> Message-ID: <20060810144223.GB12044@jadzia.bu.edu> On Thu, Aug 10, 2006 at 12:54:25PM +0200, Hans de Goede wrote: > Here is a list of bugs collected from the pet peeve bug discussion to > get us started, filtered somewhat to weed out any behavioral change > requests: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188079 > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=106552 > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131428 > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187268 > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=168660 > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177823 Oooh, here's another: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=81836 -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From j.w.r.degoede at hhs.nl Thu Aug 10 14:58:32 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Thu, 10 Aug 2006 16:58:32 +0200 Subject: FE Package Status of Aug 10, 2006 In-Reply-To: <20060810150532.2b7432c8@ludwig-alpha> References: <20060810013221.1a8dab9a@ludwig-alpha> <44DAFED7.5000300@hhs.nl> <20060810150532.2b7432c8@ludwig-alpha> Message-ID: <44DB4998.9090501@hhs.nl> Christian Iseli wrote: > On Thu, 10 Aug 2006 11:39:35 +0200, Hans de Goede wrote: >> How do we handle these, blacklist them? > > Maybe. > > Taking a quick look, I see that most packages you described as > (library) actually do have the keyword "library" in the owners.list > description, so for those I could take that into account. > You couldalso check the actual rpm contents, and if there is nothing under /[s]bin or /usr/[s]bin then not complain, I don't know hoe hard that would be though. The taking a look at owners.list descriptions definetly is a good start! > The cmdline tools are more problematic... > I agree, not even looking at the rpms helps there, which leads to the conclusion we really need a blacklist. Still the script could/should be made a bit smarter like using owners.list descriptions to keep the size of the blacklist down. > (As a side note: I tend to like cmdline tools, and would like > to see them listed in comps.xml anyway... but maybe that's just me) > I like them too, but they are for power users and comps is (AFAIK) for the "ordinary" end user, so I think the current policy of not putting them in comps.xml is correct. Regards, Hans From mtasaka at ioa.s.u-tokyo.ac.jp Thu Aug 10 15:13:36 2006 From: mtasaka at ioa.s.u-tokyo.ac.jp (Mamoru Tasaka) Date: Fri, 11 Aug 2006 00:13:36 +0900 Subject: Please someone review jfbterm (bug 201170) In-Reply-To: <20060810131031.GB2547@free.fr> References: <44DB2317.4020400@ioa.s.u-tokyo.ac.jp> <20060810131031.GB2547@free.fr> Message-ID: <44DB4D20.4080505@ioa.s.u-tokyo.ac.jp> Patrice Dumas wrote: > On Thu, Aug 10, 2006 at 09:14:15PM +0900, Mamoru Tasaka wrote: >> Hello. >> BTW, when must I think that my review request is currently >> ignored and I should ask for someone to review it? > > That's up to you. One traditional way of having people reviewing > your package is to review their packages first. But doing some > advertising like you just did isn't bad either. Thank you. My review request is now got a new reviewer and currently is under discussion. Mamoru Tasaka From skadz1 at gmail.com Thu Aug 10 15:41:34 2006 From: skadz1 at gmail.com (Ryan Skadberg) Date: Thu, 10 Aug 2006 11:41:34 -0400 Subject: 'straw' package appears to be orphaned In-Reply-To: <20060808114213.37f717ef.bugs.michael@gmx.net> References: <42578.140.247.244.211.1155015403.squirrel@www.newton.cx> <20060808114213.37f717ef.bugs.michael@gmx.net> Message-ID: <8719b8230608100841x400c32cew3bf5322f117c2d9d@mail.gmail.com> As one of the maintainers of Straw, I sent the maintainer new specs and srpms a while back after he said he wanted to keep maintaining the package and nothing ever got updated :( You can get a SRPM of the latest version of straw here: http://www.skadz.com/files/straw-0.26-1.src.rpm Skadz On 8/8/06, Michael Schwendt wrote: > On Tue, 8 Aug 2006 01:36:43 -0400 (EDT), Peter Williams wrote: > > > As per https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186731, the > > Fedora Extras package of the Straw news reader is extremely old. The > > maintainer, Colin Charles has seemed nonresponsive for about five months, > > at least. I'm not sure what's going on since his blog is updated quite > > regularly. > > > > I'm not familiar with the organization of Fedora Extras, but can this > > package be added the orphaned list? > > A single ticket in bugzilla without a list of subsequent contact attempts > is not enough to mark someone's package as orphaned. > > http://fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers > > -- > fedora-extras-list mailing list > fedora-extras-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-extras-list > From pertusus at free.fr Thu Aug 10 16:08:34 2006 From: pertusus at free.fr (Patrice Dumas) Date: Thu, 10 Aug 2006 18:08:34 +0200 Subject: FE Package Status of Aug 10, 2006 In-Reply-To: <44DB4998.9090501@hhs.nl> References: <20060810013221.1a8dab9a@ludwig-alpha> <44DAFED7.5000300@hhs.nl> <20060810150532.2b7432c8@ludwig-alpha> <44DB4998.9090501@hhs.nl> Message-ID: <20060810160834.GA2299@free.fr> > I like them too, but they are for power users and comps is (AFAIK) for > the "ordinary" end user, so I think the current policy of not putting > them in comps.xml is correct. There are command line apps in comps, but not in all sections. For example there are some in the "Hardware Support", "System Tools", "Development Tools", there could be in "Engineering and Scientific". There are mathematical libraries in "Engineering and Scientific". That's because what is an ordinary user depends on the comps section. And I think it is right to add more command line apps if they fit in a section intended for system administrators, developers or scientists. -- Pat From wtogami at redhat.com Thu Aug 10 17:08:25 2006 From: wtogami at redhat.com (Warren Togami) Date: Thu, 10 Aug 2006 13:08:25 -0400 Subject: Anyone want pyzor? Message-ID: <44DB6809.201@redhat.com> pyzor is a networked hash based spam detection system that automatically adds to the effectiveness of spamassassin. I would like to give ownership of pyzor to someone else who may be more interested in maintaining it. There are a number of patches in other Linux distributions that fix bugs in pyzor beyond the last upstream release, but I have not had time to verify their correctness and the upstream development project seems dead. Would anyone like to claim ownership of pyzor? Warren Togami wtogami at redhat.com From wtogami at redhat.com Thu Aug 10 17:47:10 2006 From: wtogami at redhat.com (Warren Togami) Date: Thu, 10 Aug 2006 13:47:10 -0400 Subject: FE6 Orphan Warning: dxpc gtkglarea2 soundtracker Message-ID: <44DB711E.4020407@redhat.com> dxpc gtkglarea2 soundtracker These packages are currently in FE6 but are missing owners. If they are not claimed by an active Extras contributor by August 28th, they will be removed from the repository. Any cvsextras member may claim any of the orphan packages by changing owners.list in CVS, and a short friendly note to fedora-extras-list informing others of your claim. If you have a strong personal interest in any of these packages but are not currently a cvsextras member, please talk to me directly. Warren Togami wtogami at redhat.com From bugs.michael at gmx.net Thu Aug 10 19:22:21 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Thu, 10 Aug 2006 21:22:21 +0200 Subject: rpms/liferea/devel .cvsignore, 1.32, 1.33 liferea.spec, 1.46, 1.47 sources, 1.33, 1.34 In-Reply-To: <200608101829.k7AITRf4007246@cvs-int.fedora.redhat.com> References: <200608101829.k7AITRf4007246@cvs-int.fedora.redhat.com> Message-ID: <20060810212221.7bdb227e.bugs.michael@gmx.net> On Thu, 10 Aug 2006 11:29:25 -0700, Brian Pepple wrote: > Author: bpepple > > Update of /cvs/extras/rpms/liferea/devel > -Version: 1.0.20 > -Release: 4%{?dist} > +Version: 1.0.21 > +Release: 3%{?dist} Normal would be to restart at 1%{?dist} when bumping %version. From buildsys at fedoraproject.org Thu Aug 10 19:39:21 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Thu, 10 Aug 2006 15:39:21 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-10 Message-ID: <20060810193921.79C14152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 5 em8300-kmod-0.15.3-7.2.6.17_1.2174_FC5 gnubiff-2.2.1-2.fc5 nagios-plugins-1.4.3-16.fc5 perl-DateTime-Format-HTTP-0.37-1.fc5 qstat-2.10-5.fc5 Packages built and released for Fedora Extras 4: 2 nagios-plugins-1.4.3-16.fc4 perl-DateTime-Format-HTTP-0.37-1.fc4 Packages built and released for Fedora Extras development: 9 blender-2.42-6.fc6 bochs-2.3-0.1.pre3.fc6 galeon-2.0.1-6.fc6 mail-notification-3.0-4.fc6 nagios-plugins-1.4.3-16.fc6 openbabel-2.0.2-2.fc6 perl-DateTime-Format-HTTP-0.37-1.fc6 qstat-2.10-5.fc6 xdrawchem-1.9.9-3.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Thu Aug 10 19:39:50 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Thu, 10 Aug 2006 15:39:50 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-10 Message-ID: <20060810193950.8FA8C152169@buildsys.fedoraproject.org> azureus: green AT redhat.com 5: 0:2.4.0.3-0.20060529cvs_1.fc5 (FE5) 6: 0:2.4.0.3-0.20060328cvs_5.fc6 (FE6) camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) digikam: mgarski AT post.pl 3: 0:0.8.2-2.fc3 (FE3) 4: 0:0.8.2-1.fc4 (FE4) 5: 0:0.8.2-1.fc5 (FE5) 6: 0:0.8.2-1.fc6 (FE6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) dogtail: zcerza AT redhat.com 5: 0:0.5.2-2.fc5 (FE5) 6: 0:0.5.2-1.fc6 (FC6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: liljencrantz AT gmail.com 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gaim-gaym: cweyl AT alumni.drew.edu 5: 0:0.96-3.fc5 (FE5) 6: 0:0.96-2.fc6 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) koffice: andreas.bierfert AT lowlatency.de 5: 0:1.5.2-1.fc5 (FE5) 6: 0:1.5.1-2.fc6 (FE6) libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) libpqxx: andreas.bierfert AT lowlatency.de 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) lvm2: 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) mozilla: 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.1-2.fc5 (FE5) 6: 0:1.0.1-1.fc5 (FE6) quagga: 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) seamonkey: kengert AT redhat.com 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) smart: Axel.Thimm AT ATrpms.net 5: 0:0.42-35.fc5 (FE5) 6: 0:0.41-31.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.5-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) vorbisgain: noa AT resare.com 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) XaraLX: paul AT all-the-johnsons.co.uk 5: 0:0.7-3.fc5.r1614 (FE5) 6: 0:0.7-2.fc6.r1614 (FE6) ypbind: 5: 3:1.19-1 (FC5-updates) 6: 3:1.19-0.3 (FC6) From buildsys at fedoraproject.org Thu Aug 10 19:59:40 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Thu, 10 Aug 2006 19:59:40 -0000 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-10 Message-ID: <20060810195940.9990.67354@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (126 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (126 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (3 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (3 days) libopensync-plugin-evolution2 - 0.18-6.fc5.i386 (3 days) libopensync-plugin-evolution2 - 0.18-6.fc5.ppc (3 days) libopensync-plugin-evolution2 - 0.18-6.fc5.x86_64 (3 days) wine-core - 0.9.17-1.fc6.i386 (15 days) bdpepple AT ameritech.net contact-lookup-applet - 0.14-3.fc6.i386 (3 days) contact-lookup-applet - 0.14-3.fc6.ppc (3 days) contact-lookup-applet - 0.14-3.fc6.x86_64 (3 days) liferea - 1.0.20-4.fc6.i386 liferea - 1.0.20-4.fc6.ppc liferea - 1.0.20-4.fc6.x86_64 byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (22 days) gaim-guifications - 2.12-3.fc5.ppc (22 days) gaim-guifications - 2.12-3.fc5.x86_64 (22 days) cweyl AT alumni.drew.edu gaim-gaym - 0.96-2.fc6.i386 (22 days) gaim-gaym - 0.96-2.fc6.ppc (22 days) gaim-gaym - 0.96-2.fc6.x86_64 (22 days) dennis AT ausil.us knetworkmanager - 0.1-0.3.svn20060625.fc6.i386 (21 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.ppc (21 days) knetworkmanager - 0.1-0.3.svn20060625.fc6.x86_64 (21 days) fedora AT leemhuis.info gsynaptics - 0.9.8-1.fc6.ppc (22 days) gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (14 days) amarok - 1.4.1-3.fc6.ppc (14 days) showimg-pgsql - 0.9.5-7.fc4.i386 (3 days) showimg-pgsql - 0.9.5-7.fc4.ppc (3 days) showimg-pgsql - 0.9.5-7.fc4.x86_64 (3 days) showimg-pgsql - 0.9.5-7.fc5.i386 (3 days) showimg-pgsql - 0.9.5-7.fc5.ppc (3 days) showimg-pgsql - 0.9.5-7.fc5.x86_64 (3 days) green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.i386 (15 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (15 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.x86_64 (15 days) jogl - 1.1.1-14.fc5.ppc (18 days) ivazquez AT ivazquez.net deskbar-applet - 2.14.1.1-1.fc6.i386 (3 days) deskbar-applet - 2.14.1.1-1.fc6.ppc (3 days) deskbar-applet - 2.14.1.1-1.fc6.x86_64 (3 days) gnome-applet-music - 0.9.0-1.fc6.i386 (22 days) gnome-applet-music - 0.9.0-1.fc6.ppc (22 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (22 days) nautilus-search-tool - 0.2-1.fc5.i386 (22 days) nautilus-search-tool - 0.2-1.fc5.ppc (22 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (22 days) jkeating AT redhat.com contacts - 0.1-1.i386 (3 days) contacts - 0.1-1.ppc (3 days) contacts - 0.1-1.x86_64 (3 days) lmacken AT redhat.com python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.i386 (26 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.ppc (26 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc4.x86_64 (26 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.i386 (26 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.ppc (26 days) python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.x86_64 (26 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (22 days) gfontview - 0.5.0-5.fc5.ppc (22 days) gfontview - 0.5.0-5.fc5.x86_64 (22 days) gtkhtml36 - 3.6.2-5.fc6.i386 (22 days) gtkhtml36 - 3.6.2-5.fc6.ppc (22 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (22 days) libvisual-plugins - 0.2.0-3.fc5.i386 (22 days) libvisual-plugins - 0.2.0-3.fc5.i386 (22 days) libvisual-plugins - 0.2.0-3.fc5.ppc (22 days) libvisual-plugins - 0.2.0-3.fc5.ppc (22 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (22 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (22 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (85 days) syck-php - 0.55-7.fc5.i386 (85 days) syck-php - 0.55-7.fc5.ppc (85 days) syck-php - 0.55-7.fc5.ppc (85 days) syck-php - 0.55-7.fc5.x86_64 (85 days) syck-php - 0.55-7.fc5.x86_64 (85 days) petersen AT redhat.com ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.i386 ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.ppc ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.x86_64 rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (22 days) libibverbs - 1.0.3-1.fc6.ppc (22 days) libibverbs - 1.0.3-1.fc6.x86_64 (22 days) libibverbs-utils - 1.0.3-1.fc6.i386 (22 days) libibverbs-utils - 1.0.3-1.fc6.ppc (22 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (22 days) tcallawa AT redhat.com gambas-runtime - 1.0.14-2.fc5.i386 thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (22 days) directfb - 0.9.24-5.fc5.ppc (22 days) directfb - 0.9.24-5.fc5.x86_64 (22 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.i386 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc5.i386 requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) python-ruledispatch-0.5a0-0.1.svnr2115.fc5.x86_64 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc5.x86_64 requires libpqxx-2.6.6.so()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 python-ruledispatch-0.5a0-0.1.svnr2115.fc5.ppc requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc5.ppc requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.i386 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc4.i386 requires libpqxx-2.6.6.so Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.x86_64 requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc4.x86_64 requires libpqxx-2.6.6.so()(64bit) Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- python-ruledispatch-0.5a0-0.1.svnr2115.fc4.ppc requires python-protocols >= 0:1.0 showimg-pgsql-0.9.5-7.fc4.ppc requires libpqxx-2.6.6.so Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.i386 requires libgcj.so.7 contact-lookup-applet-0.14-3.fc6.i386 requires libebook-1.2.so.5 contacts-0.1-1.i386 requires libebook-1.2.so.5 deskbar-applet-2.14.1.1-1.fc6.i386 requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.i386 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 gambas-runtime-1.0.14-2.fc5.i386 requires libgettextlib-0.14.5.so gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-2.fc6.i386 requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.i386 requires libdbus-qt-1.so.1 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 liferea-1.0.20-4.fc6.i386 requires firefox = 0:1.5.0.5 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- azureus-2.4.0.3-0.20060328cvs_5.fc6.x86_64 requires libgcj.so.7()(64bit) contact-lookup-applet-0.14-3.fc6.x86_64 requires libebook-1.2.so.5()(64bit) contacts-0.1-1.x86_64 requires libebook-1.2.so.5()(64bit) deskbar-applet-2.14.1.1-1.fc6.x86_64 requires libebook-1.2.so.5()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-gaym-0.96-2.fc6.x86_64 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) ghc642-gtk2hs-mozembed-0.9.10-2.fc6.x86_64 requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-qt-1.so.1()(64bit) knetworkmanager-0.1-0.3.svn20060625.fc6.x86_64 requires libdbus-1.so.2()(64bit) koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libedata-cal-1.2.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libecal-1.2.so.3()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libebook-1.2.so.5()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) liferea-1.0.20-4.fc6.x86_64 requires firefox = 0:1.5.0.5 nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.17-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 contact-lookup-applet-0.14-3.fc6.ppc requires libebook-1.2.so.5 contacts-0.1-1.ppc requires libebook-1.2.so.5 deskbar-applet-2.14.1.1-1.fc6.ppc requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.ppc requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-2.fc6.ppc requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gsynaptics-0.9.8-1.fc6.ppc requires synaptics gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-1.so.2 knetworkmanager-0.1-0.3.svn20060625.fc6.ppc requires libdbus-qt-1.so.1 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 liferea-1.0.20-4.fc6.ppc requires firefox = 0:1.5.0.5 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 ====================================================================== New report for: gauret AT free.fr package: amarok - 1.4.1-3.fc6.i386 from fedora-extras-development-i386 unresolved deps: HelixPlayer package: amarok - 1.4.1-3.fc6.ppc from fedora-extras-development-ppc unresolved deps: HelixPlayer From ville.skytta at iki.fi Thu Aug 10 20:05:51 2006 From: ville.skytta at iki.fi (Ville =?ISO-8859-1?Q?Skytt=E4?=) Date: Thu, 10 Aug 2006 23:05:51 +0300 Subject: Planning next version of rpmdevtools In-Reply-To: <1152911573.2696.49.camel@localhost.localdomain> References: <1152911573.2696.49.camel@localhost.localdomain> Message-ID: <1155240351.2997.317.camel@localhost.localdomain> On Sat, 2006-07-15 at 00:12 +0300, Ville Skytt? wrote: > Rename scripts (with appropriate backwards compat symlinks for a while): > * fedora-extract -> extractarchive After having used the new package locally from CVS for a while, my left hand already protests against this change, it says "extracta" is too hard to type repeatedly and shorter variants before the are not unique here :). So unless someone is aware of a conflict this would cause, I'm going to re-rename it as "xvf" - see top of the script for where that name comes from. In addition to the above, in the TODO list are *.pyo related changes to the Python spec template (as discussed in today's packaging committee meeting, see http://fedoraproject.org/wiki/Packaging/GuidelinesTodo), and the PHP spec template stuff. Unless something unexpected happens, I'm going to push 5.0 at end of next week to devel, and to FE5 a bit later. The PHP stuff will make it in this release if it's ready, otherwise an update will be pushed later when it is. From michael at knox.net.nz Thu Aug 10 20:09:31 2006 From: michael at knox.net.nz (Michael J. Knox) Date: Fri, 11 Aug 2006 08:09:31 +1200 (NZST) Subject: Anyone want pyzor? In-Reply-To: <44DB6809.201@redhat.com> References: <44DB6809.201@redhat.com> Message-ID: <29348.203.118.135.21.1155240571.squirrel@www.knox.net.nz> Warren Togami wrote: > pyzor is a networked hash based spam detection system that automatically > adds to the effectiveness of spamassassin. > > I would like to give ownership of pyzor to someone else who may be more > interested in maintaining it. There are a number of patches in other > Linux distributions that fix bugs in pyzor beyond the last upstream > release, but I have not had time to verify their correctness and the > upstream development project seems dead. > > Would anyone like to claim ownership of pyzor? If no one has staked a claim, I will. Still with out broadband at home :-( so I can't work on it for another week (hopefully). Michael From chris.stone at gmail.com Thu Aug 10 20:51:59 2006 From: chris.stone at gmail.com (Christopher Stone) Date: Thu, 10 Aug 2006 13:51:59 -0700 Subject: Planning next version of rpmdevtools In-Reply-To: <1155240351.2997.317.camel@localhost.localdomain> References: <1152911573.2696.49.camel@localhost.localdomain> <1155240351.2997.317.camel@localhost.localdomain> Message-ID: On 8/10/06, Ville Skytt? wrote: > On Sat, 2006-07-15 at 00:12 +0300, Ville Skytt? wrote: > and the PHP spec template stuff. I think the PHP spec template stuff is still waiting on the php-pear package that is in testing to move to updates so we can get the new macros. From chris.stone at gmail.com Thu Aug 10 20:54:12 2006 From: chris.stone at gmail.com (Christopher Stone) Date: Thu, 10 Aug 2006 13:54:12 -0700 Subject: Broken upgrade paths in FC+FE 2006-08-10 In-Reply-To: <20060810193950.8FA8C152169@buildsys.fedoraproject.org> References: <20060810193950.8FA8C152169@buildsys.fedoraproject.org> Message-ID: Hi, can these be sorted by e-mail address rather than package name for quicker perusal purposes? On 8/10/06, buildsys at fedoraproject.org wrote: > azureus: green AT redhat.com > 5: 0:2.4.0.3-0.20060529cvs_1.fc5 (FE5) > 6: 0:2.4.0.3-0.20060328cvs_5.fc6 (FE6) > > camstream: nomis80 AT nomis80.org > 5: 0:0.26.3-10.fc5 (FE5) > 6: 0:0.26.3-9.fc5 (FE6) > > dclib: lmacken AT redhat.com > 5: 0:0.3.7-8.fc5 (FE5) > 6: 0:0.3.7-7.fc6 (FE6) > > device-mapper: > 4: 0:1.02.07-2.0 (FC4-updates) > 5: 0:1.02.02-3.2 (FC5) > 6: 0:1.02.07-1.1 (FC6) > > digikam: mgarski AT post.pl > 3: 0:0.8.2-2.fc3 (FE3) > 4: 0:0.8.2-1.fc4 (FE4) > 5: 0:0.8.2-1.fc5 (FE5) > 6: 0:0.8.2-1.fc6 (FE6) > > dillo: andreas.bierfert AT lowlatency.de > 4: 0:0.8.6-2.fc4 (FE4) > 5: 0:0.8.6-1.fc5 (FE5) > 6: 0:0.8.6-2.fc6 (FE6) > > dogtail: zcerza AT redhat.com > 5: 0:0.5.2-2.fc5 (FE5) > 6: 0:0.5.2-1.fc6 (FC6) > > firestarter: mpeters AT mac.com > 5: 0:1.0.3-11.fc5 (FE5) > 6: 0:1.0.3-10.fc6 (FE6) > > fish: liljencrantz AT gmail.com > 5: 0:1.21.10-3.fc5 (FE5) > 6: 0:1.21.10-2.fc6 (FE6) > > flumotion: thomas AT apestaart.org > 5: 0:0.2.1-2.fc5 (FE5) > 6: 0:0.2.0-1.fc5 (FE6) > > fortune-firefly: meme AT daughtersoftiresias.org > 5: 0:2.1.1-2.fc5 (FE5) > 6: 0:2.1.1-1.fc6 (FE6) > > fuse-encfs: lemenkov AT newmail.ru > 5: 0:1.3.1-1.fc5 (FE5) > 6: 0:1.3.0-1.fc6 (FE6) > > fuse-sshfs: lemenkov AT newmail.ru > 5: 0:1.6-3.fc5 (FE5) > 6: 0:1.6-2.fc6 (FE6) > > gaim-gaym: cweyl AT alumni.drew.edu > 5: 0:0.96-3.fc5 (FE5) > 6: 0:0.96-2.fc6 (FE6) > > gdesklets: luya_tfz AT thefinalzone.com > 4: 0:0.35.3-8.1.fc4 (FE4) > 5: 0:0.35.3-8.fc5 (FE5) > 6: 0:0.35.3-8.fc6 (FE6) > > istanbul: jspaleta AT gmail.com > 5: 0:0.1.1-9.fc5 (FE5) > 6: 0:0.1.1-9 (FE6) > > koffice: andreas.bierfert AT lowlatency.de > 5: 0:1.5.2-1.fc5 (FE5) > 6: 0:1.5.1-2.fc6 (FE6) > > libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de > 5: 0:0.18-7.fc5 (FE5) > 6: 0:0.18-6.fc5 (FE6) > > libpqxx: andreas.bierfert AT lowlatency.de > 5: 0:2.6.7-1.fc5 (FE5) > 6: 0:2.6.6-1.fc6 (FE6) > > lvm2: > 4: 0:2.02.06-1.0.fc4 (FC4-updates) > 5: 0:2.02.01-1.2.1 (FC5) > 6: 0:2.02.06-3 (FC6) > > m17n-db: petersen AT redhat.com > 4: 0:1.3.3-1.fc4 (FE4) > 5: 0:1.3.3-1 (FC5) > 6: 0:1.3.3-17.fc6 (FC6) > > mozilla: > 3: 37:1.7.13-1.3.1.legacy (FL3-updates) > 4: 37:1.7.13-1.1.fc4 (FC4-updates) > 5: 37:1.7.13-1.1.fc5 (FC5-updates) > > opencv: nomis80 AT nomis80.org > 5: 0:0.9.7-16.fc5 (FE5) > 6: 0:0.9.7-15.fc5 (FE6) > > perl-String-CRC32: paul AT city-fan.org > 4: 0:1.4-1.fc4 (FE4) > 5: 0:1.4-1.FC5 (FC5-updates) > 6: 0:1.4-2.fc6 (FC6) > > pgadmin3: ghenry AT suretecsystems.com > 5: 0:1.4.3-2.fc5 (FE5) > 6: 0:1.4.1-2.fc5 (FE6) > > php-pear-DB: rpm AT timj.co.uk > 5: 0:1.7.6-6.fc5 (FE5) > 6: 0:1.7.6-6 (FE6) > > python-myghty: lmacken AT redhat.com > 5: 0:1.0.1-2.fc5 (FE5) > 6: 0:1.0.1-1.fc5 (FE6) > > quagga: > 4: 0:0.98.6-1.fc4 (FC4-updates) > 5: 0:0.98.6-1.FC5 (FC5-updates) > 6: 0:0.98.6-2.1 (FC6) > > scim-tomoe: ryo-dairiki AT users.sourceforge.net > 5: 0:0.2.0-6.fc5.1 (FE5) > 6: 0:0.2.0-4.fc6 (FE6) > > seamonkey: kengert AT redhat.com > 5: 0:1.0.4-0.5.1.fc5 (FE5) > 6: 0:1.0.2-1.fc6 (FE6) > > serpentine: foolish AT guezz.net > 5: 0:0.7-4.fc5 (FE5) > 6: 0:0.7-3.fc6 (FE6) > > smart: Axel.Thimm AT ATrpms.net > 5: 0:0.42-35.fc5 (FE5) > 6: 0:0.41-31.fc6 (FE6) > > stratagus: lemenkov AT newmail.ru > 5: 0:2.1-6.fc5 (FE5) > 6: 0:2.1-5.fc6 (FE6) > > TeXmacs: gemi AT bluewin.ch > 5: 0:1.0.6.5-1.fc5 (FE5) > 6: 0:1.0.6.3-1.fc6 (FE6) > > valknut: lmacken AT redhat.com > 5: 0:0.3.7-9.fc5 (FE5) > 6: 0:0.3.7-8.fc6 (FE6) > > vorbisgain: noa AT resare.com > 5: 0:0.34-2.fc5 (FE5) > 6: 0:0.34-1.fc6 (FE6) > > XaraLX: paul AT all-the-johnsons.co.uk > 5: 0:0.7-3.fc5.r1614 (FE5) > 6: 0:0.7-2.fc6.r1614 (FE6) > > ypbind: > 5: 3:1.19-1 (FC5-updates) > 6: 3:1.19-0.3 (FC6) > > -- > fedora-extras-list mailing list > fedora-extras-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-extras-list > From dcbw at redhat.com Thu Aug 10 21:09:40 2006 From: dcbw at redhat.com (Dan Williams) Date: Thu, 10 Aug 2006 17:09:40 -0400 Subject: Csound in extras? Message-ID: <1155244180.14998.4.camel@localhost.localdomain> Hi, I seem to recall seeing a mail recently asking whether Csound (http://www.csounds.com/ ) was suitable for proposal to Fedora Extras, but there were some legal questions. Am I eating too many magic shrooms? Thanks, Dan From wart at kobold.org Thu Aug 10 22:12:03 2006 From: wart at kobold.org (Michael Thomas) Date: Thu, 10 Aug 2006 15:12:03 -0700 Subject: FE Package Status of Aug 10, 2006 In-Reply-To: <20060810160834.GA2299@free.fr> References: <20060810013221.1a8dab9a@ludwig-alpha> <44DAFED7.5000300@hhs.nl> <20060810150532.2b7432c8@ludwig-alpha> <44DB4998.9090501@hhs.nl> <20060810160834.GA2299@free.fr> Message-ID: <44DBAF33.7090801@kobold.org> Patrice Dumas wrote: >>I like them too, but they are for power users and comps is (AFAIK) for >>the "ordinary" end user, so I think the current policy of not putting >>them in comps.xml is correct. > > > There are command line apps in comps, but not in all sections. For example > there are some in the "Hardware Support", "System Tools", "Development Tools", > there could be in "Engineering and Scientific". There are mathematical > libraries in "Engineering and Scientific". That's because what is an ordinary > user depends on the comps section. > > And I think it is right to add more command line apps if they fit in a > section intended for system administrators, developers or scientists. Another vitally important exception are applications such as rogue, nethack, and ularn. Though these would be more accurately described as terminal-based apps than command-line apps. --Mike -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3820 bytes Desc: S/MIME Cryptographic Signature URL: From paul at all-the-johnsons.co.uk Thu Aug 10 22:29:45 2006 From: paul at all-the-johnsons.co.uk (Paul) Date: Thu, 10 Aug 2006 23:29:45 +0100 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-10 In-Reply-To: <20060810195940.9990.67354@extras64.linux.duke.edu> References: <20060810195940.9990.67354@extras64.linux.duke.edu> Message-ID: <1155248985.20807.9.camel@T7.Linux> Hi, > gaim-guifications - 2.12-3.fc5.i386 (22 days) > gaim-gaym - 0.96-2.fc6.i386 (22 days) > knetworkmanager - 0.1-0.3.svn20060625.fc6.i386 (21 days) > gsynaptics - 0.9.8-1.fc6.ppc (22 days) > gnome-applet-music - 0.9.0-1.fc6.i386 (22 days) > nautilus-search-tool - 0.2-1.fc5.i386 (22 days) > python-ruledispatch - 0.5a0-0.1.svnr2115.fc5.i386 (26 days) > gfontview - 0.5.0-5.fc5.i386 (22 days) > gtkhtml36 - 3.6.2-5.fc6.i386 (22 days) > libvisual-plugins - 0.2.0-3.fc5.i386 (22 days) > syck-php - 0.55-7.fc5.i386 (85 days) > libibverbs - 1.0.3-1.fc6.i386 (22 days) > libibverbs-utils - 1.0.3-1.fc6.i386 (22 days) > directfb - 0.9.24-5.fc5.i386 (22 days) Are these all relying on upstream or other packages to be built and if they are, surely some of them should be pensioned off? TTFN Paul -- Wenn sie denken, dass die bildung teuer ist, versuchen sie ignoranz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Christian.Iseli at licr.org Thu Aug 10 22:50:47 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Fri, 11 Aug 2006 00:50:47 +0200 Subject: .pyo files Message-ID: <20060811005047.19ea1b7e@ludwig-alpha> Hi folks, The packaging rules for python modules were amended and .pyo files shall no longer be %ghosted but must be provided in the package. I expect the Packaging wiki pages will be updated shortly... Anyway, I was asked to file BZ tickets to get all python packages in devel fixed. So I have a couple questions: 1. I think a pyo blocker bug would be nice to track progress. Could thl or someone with a /dev/null mailbox please create a tracker ticket ? 2. Anyone has a working script to enter BZ tickets that I could borrow ? Cheers, Christian From dennis at ausil.us Thu Aug 10 23:15:22 2006 From: dennis at ausil.us (Dennis Gilmore) Date: Thu, 10 Aug 2006 18:15:22 -0500 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-10 In-Reply-To: <1155248985.20807.9.camel@T7.Linux> References: <20060810195940.9990.67354@extras64.linux.duke.edu> <1155248985.20807.9.camel@T7.Linux> Message-ID: <200608101815.22481.dennis@ausil.us> On Thursday 10 August 2006 5:29 pm, Paul wrote: > > ? ? ? ? knetworkmanager - 0.1-0.3.svn20060625.fc6.i386 ? ?(21 days) This i am working on now, dbusqt was pulled out of extras with no warning so I now need to patch knetworkmanager to talk directly to dbus. when it first happened i contacted upstream but have not heard from them -- Dennis Gilmore, RHCE Proud Australian From toshio at tiki-lounge.com Fri Aug 11 00:00:43 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Thu, 10 Aug 2006 17:00:43 -0700 Subject: .pyo files In-Reply-To: <20060811005047.19ea1b7e@ludwig-alpha> References: <20060811005047.19ea1b7e@ludwig-alpha> Message-ID: <1155254443.3034.40.camel@localhost> On Fri, 2006-08-11 at 00:50 +0200, Christian Iseli wrote: > Hi folks, > > The packaging rules for python modules were amended and .pyo files > shall no longer be %ghosted but must be provided in the package. > > I expect the Packaging wiki pages will be updated shortly... > > Anyway, I was asked to file BZ tickets to get all python packages in > devel fixed. Hey Christian, Go ahead and work on this, but hold off on actually implementing it for a bit. I'm going to post the details to fedora-maintainers as well so packagers in both Core and Extras get a chance to holler if they have an issue. With Jeremy's support for the change, I doubt there'll be a problem but just in case :-) -Toshio P.S. The packaging committee usually asks for comments from FESCo and Core and then the policy goes into effect the following week if there were no objections. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sundaram at fedoraproject.org Fri Aug 11 00:03:41 2006 From: sundaram at fedoraproject.org (Rahul) Date: Fri, 11 Aug 2006 05:33:41 +0530 Subject: .pyo files In-Reply-To: <1155254443.3034.40.camel@localhost> References: <20060811005047.19ea1b7e@ludwig-alpha> <1155254443.3034.40.camel@localhost> Message-ID: <44DBC95D.1070201@fedoraproject.org> Toshio Kuratomi wrote: > > P.S. The packaging committee usually asks for comments from FESCo and > Core and then the policy goes into effect the following week if there > were no objections. Which people from Core? Is it the release engineering team? Can you document your working methodology somewhere? Rahul From toshio at tiki-lounge.com Fri Aug 11 00:19:43 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Thu, 10 Aug 2006 17:19:43 -0700 Subject: .pyo files In-Reply-To: <44DBC95D.1070201@fedoraproject.org> References: <20060811005047.19ea1b7e@ludwig-alpha> <1155254443.3034.40.camel@localhost> <44DBC95D.1070201@fedoraproject.org> Message-ID: <1155255583.3034.59.camel@localhost> On Fri, 2006-08-11 at 05:33 +0530, Rahul wrote: > Toshio Kuratomi wrote: > > > > > P.S. The packaging committee usually asks for comments from FESCo and > > Core and then the policy goes into effect the following week if there > > were no objections. > > Which people from Core? Is it the release engineering team? > Can you document your working methodology somewhere? In the past it was up to Jesse Keating to make sure that the relevant people in Core were given the information and take the objections back to the Packaging Committee. For this week (and presumably if it works well, for the future) Jesse asked that the changes be emailed to the fedora-maintainers mailing list as a heads-up and in case anyone found the change objectionable. http://www.fedoraproject.org/wiki/Packaging/Committee Says that the current methodology is for representatives from Core and Extras (currently Jesse for Core and Packaging Committee Members that are also on FESCo for Extras) will present the information. Several weeks ago the Packaging Committee and FESCo agreed that this process would also handle objections to the policies. For FESCo, the Packaging Committee has been presenting its meeting summary at the FESCo meeting which occurs directly after. Today's FESCo discussed the possibility of doing some of this via email which would require the Packaging Committee or FESCo to change the weekday they meet so there's time for a summary to be emailed and viewed by the members. The email to maintainers-list also is happening for the first time today. If it continues to be the norm we'll document it on the Packaging/Committee page. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From rc040203 at freenet.de Fri Aug 11 04:33:37 2006 From: rc040203 at freenet.de (Ralf Corsepius) Date: Fri, 11 Aug 2006 06:33:37 +0200 Subject: Planning next version of rpmdevtools In-Reply-To: <1155240351.2997.317.camel@localhost.localdomain> References: <1152911573.2696.49.camel@localhost.localdomain> <1155240351.2997.317.camel@localhost.localdomain> Message-ID: <1155270817.2403.123.camel@mccallum.corsepiu.local> On Thu, 2006-08-10 at 23:05 +0300, Ville Skytt? wrote: > On Sat, 2006-07-15 at 00:12 +0300, Ville Skytt? wrote: > > > Rename scripts (with appropriate backwards compat symlinks for a while): > > * fedora-extract -> extractarchive > > After having used the new package locally from CVS for a while, my left > hand already protests against this change, My left hand already is stiff from protesting against this renamer in general ;) Please keep these scripts using a common prefix. Which doesn't really matter, be it fedora-, rpmdev- or whatever you prefer, but don't commit the same fault others (e.g. SELinux) have tripped into. Ralf From dan at danny.cz Fri Aug 11 05:59:47 2006 From: dan at danny.cz (Dan =?ISO-8859-1?Q?Hor=E1k?=) Date: Fri, 11 Aug 2006 07:59:47 +0200 Subject: FE-NEW \ FE-NEEDSPONSOR In-Reply-To: <200608101350.AA174325938@danny.cz> References: <200608101350.AA174325938@danny.cz> Message-ID: <1155275987.3496.6.camel@eagle.danny.cz> > could you look at Code::Blocks IDE I was in a hurry, so I have moved the meaning of the mail a bit ;-) Dan From pmatilai at laiskiainen.org Fri Aug 11 06:01:12 2006 From: pmatilai at laiskiainen.org (Panu Matilainen) Date: Fri, 11 Aug 2006 09:01:12 +0300 (EEST) Subject: Planning next version of rpmdevtools In-Reply-To: <1155240351.2997.317.camel@localhost.localdomain> References: <1152911573.2696.49.camel@localhost.localdomain> <1155240351.2997.317.camel@localhost.localdomain> Message-ID: On Thu, 10 Aug 2006, Ville Skytt? wrote: > On Sat, 2006-07-15 at 00:12 +0300, Ville Skytt? wrote: > >> Rename scripts (with appropriate backwards compat symlinks for a while): >> * fedora-extract -> extractarchive > > After having used the new package locally from CVS for a while, my left > hand already protests against this change, it says "extracta" is > too hard to type repeatedly and shorter variants before the are > not unique here :). So unless someone is aware of a conflict this would > cause, I'm going to re-rename it as "xvf" - see top of the script for > where that name comes from. Mm. "xvf" is totally obscure as a name (well .. like 'sed' isn't :) Since these tools deal with rpm's, how about renaming them with rpm- prefix? Would keep them in a separate namespace which is good IMHO (we have enough of too generic names in /usr/bin; "fixfiles" huh...) and point into right direction wrt their intended use (unlike the earlier fedora- prefix). - Panu - From ville.skytta at iki.fi Fri Aug 11 08:52:30 2006 From: ville.skytta at iki.fi (Ville =?ISO-8859-1?Q?Skytt=E4?=) Date: Fri, 11 Aug 2006 11:52:30 +0300 Subject: Planning next version of rpmdevtools In-Reply-To: References: <1152911573.2696.49.camel@localhost.localdomain> <1155240351.2997.317.camel@localhost.localdomain> Message-ID: <1155286350.2997.356.camel@localhost.localdomain> On Fri, 2006-08-11 at 09:01 +0300, Panu Matilainen wrote: > Since these tools deal with rpm's, how about renaming them with rpm- > prefix? The archive differ and extractor operate on many more things than just rpms, so prefixing them with just rpm- would be misleading. On Fri, 2006-08-11 at 06:33 +0200, Ralf Corsepius wrote: > Which doesn't really matter, be it fedora-, rpmdev- or whatever Hmm, while I don't think there are big problems with the names of things that do deal with rpms in the package, rpmdev-* could work, it's sufficiently easy to type, descriptive, and relatively TAB-clash-free. Here's the current list of utils and some comments about them; feel free to throw in more suggestions or +1/-1's, I'll look through them late next week and pick something based on the feedback. /usr/bin/buildrpmtree (somewhat misleading/generic? doesn't have to be typed often, so doesn't matter if a new name would be a bit hard to type) /usr/bin/diffarchive /usr/bin/extractarchive (--> xvf? extarchive? extrarchive? unarchive? dearchive? explode?) /usr/bin/newrpmspec /usr/bin/rmdevelrpms /usr/bin/rpmchecksig /usr/bin/rpminfo /usr/bin/rpmmd5 /usr/bin/rpmvercmp /usr/bin/spectool /usr/bin/wipebuildtree (somewhat misleading/generic?) With rpmdev prefix, maybe something like this. rpmdeX would work: /usr/bin/rpmdev-setuptree /usr/bin/rpmdev-diff /usr/bin/rpmdev-extract /usr/bin/rpmdev-newspec /usr/bin/rpmdev-rmdevel(rpm?)s /usr/bin/rpmdev-checksig /usr/bin/rpminfo (upstream name, unchanged) /usr/bin/rpmdev-md5 /usr/bin/rpmdev-vercmp /usr/bin/spectool (upstream name, unchanged) /usr/bin/rpmdev-wipetree From Christian.Iseli at licr.org Fri Aug 11 09:10:52 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Fri, 11 Aug 2006 11:10:52 +0200 Subject: .pyo files In-Reply-To: <1155254443.3034.40.camel@localhost> References: <20060811005047.19ea1b7e@ludwig-alpha> <1155254443.3034.40.camel@localhost> Message-ID: <20060811111052.1b4f35ff@ludwig-alpha> On Thu, 10 Aug 2006 17:00:43 -0700, Toshio Kuratomi wrote: > Go ahead and work on this, but hold off on actually implementing it for > a bit. I'm going to post the details to fedora-maintainers as well so > packagers in both Core and Extras get a chance to holler if they have an > issue. > > With Jeremy's support for the change, I doubt there'll be a problem but > just in case :-) ok. I'll wait for a GA from you. In any case, I've no mass BZ submit script yet... > P.S. The packaging committee usually asks for comments from FESCo and > Core and then the policy goes into effect the following week if there > were no objections. Yea, I jumped the gun a bit on this one. Sorry. 't's been a long day... Christian From Christian.Iseli at licr.org Fri Aug 11 09:14:25 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Fri, 11 Aug 2006 11:14:25 +0200 Subject: Planning next version of rpmdevtools In-Reply-To: <1155286350.2997.356.camel@localhost.localdomain> References: <1152911573.2696.49.camel@localhost.localdomain> <1155240351.2997.317.camel@localhost.localdomain> <1155286350.2997.356.camel@localhost.localdomain> Message-ID: <20060811111425.0149f97d@ludwig-alpha> On Fri, 11 Aug 2006 11:52:30 +0300, Ville Skytt? wrote: > With rpmdev prefix, maybe something like this. rpmdeX would > work: I like it. Christian From jonathan.underwood at gmail.com Fri Aug 11 09:44:02 2006 From: jonathan.underwood at gmail.com (Jonathan Underwood) Date: Fri, 11 Aug 2006 10:44:02 +0100 Subject: Local repository setup problem with fedora-mirror.py In-Reply-To: References: Message-ID: <645d17210608110244ha615e8eid74da19352e8e7a4@mail.gmail.com> On 10/08/06, Parag N(????) wrote: > Hi, > I was using local repositories setup for mock build successfully > on FC5 previously. Now i formatted my system and installed FC6 Test 2 > and tried to follow the same steps that i did from my page > http://fedoraproject.org/wiki/ParagNemade/MockSetupUsingLocalMirror Parag - this is a really useful page - I wonder if it could be moved somewhere more visible, i.e. made part of the main FE wiki pages. jonathan. From triad at df.lth.se Fri Aug 11 10:32:55 2006 From: triad at df.lth.se (Linus Walleij) Date: Fri, 11 Aug 2006 12:32:55 +0200 (CEST) Subject: Upload problem Message-ID: Having this problem with "make new-sources" (or make upload): Checking : gnokii-0.6.13.tar.bz2 on https://cvs.fedora.redhat.com/repo/extras/upload.cgi... ERROR: could not check remote file status make: *** [upload] Error 255 Hm, error 255... Now that's clear as mud... Is it a problem with the server or just my own fault as usual? Linus From j.w.r.degoede at hhs.nl Fri Aug 11 10:41:25 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Fri, 11 Aug 2006 12:41:25 +0200 Subject: Upload problem In-Reply-To: References: Message-ID: <44DC5ED5.9090509@hhs.nl> Linus Walleij wrote: > Having this problem with "make new-sources" (or make upload): > > Checking : gnokii-0.6.13.tar.bz2 on > https://cvs.fedora.redhat.com/repo/extras/upload.cgi... > ERROR: could not check remote file status > make: *** [upload] Error 255 > > Hm, error 255... Now that's clear as mud... > > Is it a problem with the server or just my own fault as usual? > I hit the same yesterday, your ~/.fedora.cert is expired, go get a new one from the account system. Regards, Hans From bugs.michael at gmx.net Fri Aug 11 10:47:14 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Fri, 11 Aug 2006 12:47:14 +0200 Subject: .pyo files In-Reply-To: <20060811005047.19ea1b7e@ludwig-alpha> References: <20060811005047.19ea1b7e@ludwig-alpha> Message-ID: <20060811124714.48a1fd78.bugs.michael@gmx.net> On Fri, 11 Aug 2006 00:50:47 +0200, Christian Iseli wrote: > 2. Anyone has a working script to enter BZ tickets that I could borrow ? Yes, via bugzilla xml-rpc. See attachment. I don't know how stable the API is yet, though. -------------- next part -------------- A non-text attachment was scrubbed... Name: fe-reportbug.py Type: application/octet-stream Size: 856 bytes Desc: not available URL: From bugs.michael at gmx.net Fri Aug 11 11:32:49 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Fri, 11 Aug 2006 13:32:49 +0200 Subject: rpms/gtkdatabox/devel gtkdatabox.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2 In-Reply-To: <200608100633.k7A6Xp3B003358@cvs-int.fedora.redhat.com> References: <200608100633.k7A6Xp3B003358@cvs-int.fedora.redhat.com> Message-ID: <20060811133249.889e8425.bugs.michael@gmx.net> On Wed, 9 Aug 2006 23:33:49 -0700, Eric Work wrote: > Author: ework > > Update of /cvs/extras/rpms/gtkdatabox/devel > %post -p /sbin/ldconfig > %postun -p /sbin/ldconfig > %post devel -p /sbin/ldconfig > %postun devel -p /sbin/ldconfig The scriptlets for the -devel package are not needed. When the package is installed, the *.so symlink points to the right *.so.N library file already. In case the *.so.N library has been replaced with a different N, you're in trouble anyway, and updating the link with ldconfig would lead to unexpected/wrong results (i.e. -lgtkdatabox would not link with the library from your main gtkdatabox file). > %files > %defattr(-,root,root,-) > %doc AUTHORS ChangeLog COPYING NEWS README TODO > %{_libdir}/libgtkdatabox-*.so.* > > %files devel > %defattr(-,root,root,-) > %doc examples/*.c > %{_includedir}/gtkdatabox*.h > %{_libdir}/libgtkdatabox.so > %{_libdir}/pkgconfig/gtkdatabox.pc From Christian.Iseli at licr.org Fri Aug 11 12:20:04 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Fri, 11 Aug 2006 14:20:04 +0200 Subject: .pyo files In-Reply-To: <20060811124714.48a1fd78.bugs.michael@gmx.net> References: <20060811005047.19ea1b7e@ludwig-alpha> <20060811124714.48a1fd78.bugs.michael@gmx.net> Message-ID: <20060811142004.6c762c07@ludwig-alpha> On Fri, 11 Aug 2006 12:47:14 +0200, Michael Schwendt wrote: > Yes, via bugzilla xml-rpc. See attachment. Thanks a bunch. I guess it's time I learn some python by example :-) > I don't know how stable the API is yet, though. Ok. I'll see how it goes. BTW, I noticed the normal BZ submit page has some javascript stuff to properly setup the initial owner of the bug, and your script doesn't appear to set it up. Should it be set from the script, or does BZ set it up itself at soem later point ? Cheers, Christian From nphilipp at redhat.com Fri Aug 11 13:43:33 2006 From: nphilipp at redhat.com (Nils Philippsen) Date: Fri, 11 Aug 2006 15:43:33 +0200 Subject: Csound in extras? In-Reply-To: <1155244180.14998.4.camel@localhost.localdomain> References: <1155244180.14998.4.camel@localhost.localdomain> Message-ID: <1155303813.5088.1.camel@gibraltar.stuttgart.redhat.com> On Thu, 2006-08-10 at 17:09 -0400, Dan Williams wrote: > I seem to recall seeing a mail recently asking whether Csound > (http://www.csounds.com/ ) was suitable for proposal to Fedora Extras, > but there were some legal questions. Can't find anything about it in the archives or the wiki. Nils -- Nils Philippsen / Red Hat / nphilipp at redhat.com "Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety." -- B. Franklin, 1759 PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011 From bugs.michael at gmx.net Fri Aug 11 13:56:13 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Fri, 11 Aug 2006 15:56:13 +0200 Subject: .pyo files In-Reply-To: <20060811142004.6c762c07@ludwig-alpha> References: <20060811005047.19ea1b7e@ludwig-alpha> <20060811124714.48a1fd78.bugs.michael@gmx.net> <20060811142004.6c762c07@ludwig-alpha> Message-ID: <20060811155613.3ea7b6be.bugs.michael@gmx.net> On Fri, 11 Aug 2006 14:20:04 +0200, Christian Iseli wrote: > On Fri, 11 Aug 2006 12:47:14 +0200, Michael Schwendt wrote: > > Yes, via bugzilla xml-rpc. See attachment. > > Thanks a bunch. I guess it's time I learn some python by example :-) > > > I don't know how stable the API is yet, though. > > Ok. I'll see how it goes. > > BTW, I noticed the normal BZ submit page has some javascript stuff to > properly setup the initial owner of the bug, and your script doesn't > appear to set it up. Should it be set from the script, or does BZ set > it up itself at soem later point ? Setting the assigned_to field is not mandatory when creating a new bug. It depends on the "component" name and is filled in automatically. From jwboyer at jdub.homelinux.org Fri Aug 11 14:10:55 2006 From: jwboyer at jdub.homelinux.org (Josh Boyer) Date: Fri, 11 Aug 2006 09:10:55 -0500 Subject: Csound in extras? In-Reply-To: <1155303813.5088.1.camel@gibraltar.stuttgart.redhat.com> References: <1155244180.14998.4.camel@localhost.localdomain> <1155303813.5088.1.camel@gibraltar.stuttgart.redhat.com> Message-ID: <1155305455.2697.6.camel@zod.rchland.ibm.com> On Fri, 2006-08-11 at 15:43 +0200, Nils Philippsen wrote: > On Thu, 2006-08-10 at 17:09 -0400, Dan Williams wrote: > > > I seem to recall seeing a mail recently asking whether Csound > > (http://www.csounds.com/ ) was suitable for proposal to Fedora Extras, > > but there were some legal questions. > > Can't find anything about it in the archives or the wiki. I looked at the website. The description of "How CSounds is free" doesn't lead me to believe it's all free. There's a statement about a single person's contributions being LGPL, but not the entire project. josh From cweyl at alumni.drew.edu Fri Aug 11 14:50:22 2006 From: cweyl at alumni.drew.edu (Chris Weyl) Date: Fri, 11 Aug 2006 07:50:22 -0700 Subject: rpms/gtkdatabox/devel gtkdatabox.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2 In-Reply-To: <20060811133249.889e8425.bugs.michael@gmx.net> References: <200608100633.k7A6Xp3B003358@cvs-int.fedora.redhat.com> <20060811133249.889e8425.bugs.michael@gmx.net> Message-ID: <7dd7ab490608110750h3ef3b7fbp346e6aceeb9ab2ed@mail.gmail.com> On 8/11/06, Michael Schwendt wrote: > > %post -p /sbin/ldconfig > > %postun -p /sbin/ldconfig > > %post devel -p /sbin/ldconfig > > %postun devel -p /sbin/ldconfig > > The scriptlets for the -devel package are not needed. When the package is > installed, the *.so symlink points to the right *.so.N library file > already. In case the *.so.N library has been replaced with a different N, > you're in trouble anyway, and updating the link with ldconfig would lead > to unexpected/wrong results (i.e. -lgtkdatabox would not link with the > library from your main gtkdatabox file). Wouldn't that conflict with: "MUST: If the package contains shared library files located in the dynamic linker's default paths, that package must call ldconfig in %post and %postun. If the package has multiple subpackages with libraries, each subpackage should also have a %post/%postun section that calls /sbin/ldconfig." In this case, there is a versioned .so[1] present in the main package, with an unversioned library in -devel, per guidelines. There isn't a symlink from the unversioned to the versioned being created. [1] It's versioned, but 0.0.0. > > %files > > %defattr(-,root,root,-) > > %doc AUTHORS ChangeLog COPYING NEWS README TODO > > %{_libdir}/libgtkdatabox-*.so.* > > > > %files devel > > %defattr(-,root,root,-) > > %doc examples/*.c > > %{_includedir}/gtkdatabox*.h > > %{_libdir}/libgtkdatabox.so > > %{_libdir}/pkgconfig/gtkdatabox.pc -- Chris Weyl Ex astris, scientia From bugs.michael at gmx.net Fri Aug 11 15:56:38 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Fri, 11 Aug 2006 17:56:38 +0200 Subject: rpms/gtkdatabox/devel gtkdatabox.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2 In-Reply-To: <7dd7ab490608110750h3ef3b7fbp346e6aceeb9ab2ed@mail.gmail.com> References: <200608100633.k7A6Xp3B003358@cvs-int.fedora.redhat.com> <20060811133249.889e8425.bugs.michael@gmx.net> <7dd7ab490608110750h3ef3b7fbp346e6aceeb9ab2ed@mail.gmail.com> Message-ID: <20060811175638.09cf0677.bugs.michael@gmx.net> On Fri, 11 Aug 2006 07:50:22 -0700, Chris Weyl wrote: > > > %post -p /sbin/ldconfig > > > %postun -p /sbin/ldconfig > > > %post devel -p /sbin/ldconfig > > > %postun devel -p /sbin/ldconfig > > > > The scriptlets for the -devel package are not needed. When the package is > > installed, the *.so symlink points to the right *.so.N library file > > already. In case the *.so.N library has been replaced with a different N, > > you're in trouble anyway, and updating the link with ldconfig would lead > > to unexpected/wrong results (i.e. -lgtkdatabox would not link with the > > library from your main gtkdatabox file). > > Wouldn't that conflict with: No. > "MUST: If the package contains shared library files located in the > dynamic linker's default paths, that package must call ldconfig in > %post and %postun. If the package has multiple subpackages with > libraries, each subpackage should also have a %post/%postun section > that calls /sbin/ldconfig." The -devel is a sub-package, *but* it doesn't contain any library. It contains only a symbolic link to a file contained within the main package. A symlink only to be used during compile-time. The paragraph you quoted refers to real library files which shall enter the dynamic linker's search cache. I recommend the paragraph is rewritten: "MUST: Every binary RPM package, which stores shared library files (and not just symbolic links) in any of the dynamic linker's default paths, must call ldconfig in %post and %postun. > In this case, there is a versioned .so[1] present in the main package, > with an unversioned library in -devel, per guidelines. There isn't a > symlink from the unversioned to the versioned being created. The symlink is included in the -devel package. From fedora at leemhuis.info Fri Aug 11 16:28:31 2006 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Fri, 11 Aug 2006 18:28:31 +0200 Subject: FYI: Fedora Extras 4 in Maintenance state, FC-4 branches need to be permitted by FESCo Message-ID: <44DCB02F.8070605@leemhuis.info> Replies to fedora-extras-list only please to avoid confusion. Hi all! just a heads up: Now that Fedora Core 4 was transfered to Fedora Legacy Fedora Extras 4 is in Maintenance state now, too. See http://www.fedoraproject.org/wiki/Extras/Security/EOLPolicy for details. That why http://www.fedoraproject.org/wiki/Extras/CVSSyncNeeded now contains: > FC-3 and FC-4 branches require FESCo approval and are generally > discouraged. There are still some branch requests for FC-4. I suggest we create those and stop from now on. Further please keep the following in mind now when building for FE3 or FE4 (quoted from the EOL Policy page): > In this [Maintenance] state maintainers will be allowed to issue updates to > existing packages, but Maintainers are strongly urged to only issue > severe bugfix or security fixes. New software versions should be > avoided except when necessary for resolving issues with the the > current version. Thanks for your attention and your work in Fedora Extras. CU thl From triad at df.lth.se Fri Aug 11 17:44:57 2006 From: triad at df.lth.se (Linus Walleij) Date: Fri, 11 Aug 2006 19:44:57 +0200 (CEST) Subject: Upload problem In-Reply-To: <44DC5ED5.9090509@hhs.nl> References: <44DC5ED5.9090509@hhs.nl> Message-ID: On Fri, 11 Aug 2006, Hans de Goede wrote: > I hit the same yesterday, your ~/.fedora.cert is expired, go get a new > one from the account system. Ah, error 255 :-) Linus From j.w.r.degoede at hhs.nl Fri Aug 11 19:07:21 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Fri, 11 Aug 2006 21:07:21 +0200 Subject: Upload problem In-Reply-To: References: <44DC5ED5.9090509@hhs.nl> Message-ID: <44DCD569.70900@hhs.nl> Linus Walleij wrote: > On Fri, 11 Aug 2006, Hans de Goede wrote: > >> I hit the same yesterday, your ~/.fedora.cert is expired, go get a new >> one from the account system. > > Ah, error 255 :-) > Yeah, it took me quite some debugging to find out, so I thought I would / could spare you the same. Regards, Hans From jima at beer.tclug.org Fri Aug 11 19:05:05 2006 From: jima at beer.tclug.org (Jima) Date: Fri, 11 Aug 2006 14:05:05 -0500 (CDT) Subject: Upload problem In-Reply-To: <44DCD569.70900@hhs.nl> References: <44DC5ED5.9090509@hhs.nl> <44DCD569.70900@hhs.nl> Message-ID: On Fri, 11 Aug 2006, Hans de Goede wrote: > Linus Walleij wrote: >> On Fri, 11 Aug 2006, Hans de Goede wrote: >> >>> I hit the same yesterday, your ~/.fedora.cert is expired, go get a new >>> one from the account system. >> >> Ah, error 255 :-) >> > > Yeah, it took me quite some debugging to find out, so I thought I would > / could spare you the same. Really? My first thought when I see "Error 255" is "hmm, looks like someone needs a new client cert!" It's been asked (and answered) many times on the mailing lists. Maybe it needs to be in a FAQ somewhere? Maybe we need a wiki page titled Error_255? :) I won't deny, though, that the message isn't exactly verbose or helpful. Jima From triad at df.lth.se Fri Aug 11 22:22:00 2006 From: triad at df.lth.se (Linus Walleij) Date: Sat, 12 Aug 2006 00:22:00 +0200 (CEST) Subject: Upload problem In-Reply-To: References: <44DC5ED5.9090509@hhs.nl> <44DCD569.70900@hhs.nl> Message-ID: On Fri, 11 Aug 2006, Jima wrote: > Really? My first thought when I see "Error 255" is "hmm, looks like someone > needs a new client cert!" It's been asked (and answered) many times on the > mailing lists. Maybe it needs to be in a FAQ somewhere? Maybe we need a wiki > page titled Error_255? :) Nah I put it in at the end of the CVS FAQ... Linus From j.w.r.degoede at hhs.nl Sat Aug 12 05:37:24 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Sat, 12 Aug 2006 07:37:24 +0200 Subject: The bug squad is hiring! In-Reply-To: <44DB29C3.9020504@poolshark.org> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> Message-ID: <44DD6914.4080401@hhs.nl> Denis Leroy wrote: > Hans de Goede wrote: >> Hi all, >> >> Introducing the bug squad: Currently there is not much to introduce >> except for this idea in my head. Last friday I started a thread about >> collecting and fixing pet peeve bugs, the idea behind this thread was to >> build a collection of bugs which are high on the annoyance ladder and >> are fixable by mere mortals. Building such a collection is just the >> start however, the next step is to build a team of volunteers to tackle >> these bugs: the bug squad. >> >> So come on and sign up today! > > I'm game! The bug i wanted to fix is the "CD Burning only works as root > for a buncha burners", though it requires significant effort... > Well it seems that its just you and me for now, I'm thinking about posting weekly status reports to the devel list with the bugs we've squashed as means of PR in the hope of getting more volunteers. I would like to setup a wiki page which a list of potential bugs for us to fix, with a short description per bug and an URL to the bug, we could then also add a text like "Hans is working on this" to the bugs there to claim bugs to avoid collisions, does this sound like a plan. Wiki maintainers, where should this page be (maybe under Extras/SIGs? But its not soley for Extras). Regards, Hans From sundaram at fedoraproject.org Sat Aug 12 10:25:55 2006 From: sundaram at fedoraproject.org (Rahul) Date: Sat, 12 Aug 2006 15:55:55 +0530 Subject: The bug squad is hiring! In-Reply-To: <44DD6914.4080401@hhs.nl> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> <44DD6914.4080401@hhs.nl> Message-ID: <44DDACB3.6000509@fedoraproject.org> Hans de Goede wrote: > > > Denis Leroy wrote: >> Hans de Goede wrote: >>> Hi all, >>> >>> Introducing the bug squad: Currently there is not much to introduce >>> except for this idea in my head. Last friday I started a thread about >>> collecting and fixing pet peeve bugs, the idea behind this thread was to >>> build a collection of bugs which are high on the annoyance ladder and >>> are fixable by mere mortals. Building such a collection is just the >>> start however, the next step is to build a team of volunteers to tackle >>> these bugs: the bug squad. >>> >>> So come on and sign up today! >> >> I'm game! The bug i wanted to fix is the "CD Burning only works as >> root for a buncha burners", though it requires significant effort... >> > > Well it seems that its just you and me for now, I'm thinking about > posting weekly status reports to the devel list with the bugs we've > squashed as means of PR in the hope of getting more volunteers. > > I would like to setup a wiki page which a list of potential bugs for us > to fix, with a short description per bug and an URL to the bug, we could > then also add a text like "Hans is working on this" to the bugs there to > claim bugs to avoid collisions, does this sound like a plan. > > Wiki maintainers, where should this page be (maybe under Extras/SIGs? > But its not soley for Extras). > http://fedoraproject.org/wiki/BugZappers Rahul From andreas at bawue.net Sat Aug 12 10:52:48 2006 From: andreas at bawue.net (Andreas Thienemann) Date: Sat, 12 Aug 2006 12:52:48 +0200 (CEST) Subject: Anyone want pyzor? In-Reply-To: <29348.203.118.135.21.1155240571.squirrel@www.knox.net.nz> References: <44DB6809.201@redhat.com> <29348.203.118.135.21.1155240571.squirrel@www.knox.net.nz> Message-ID: On Fri, 11 Aug 2006, Michael J. Knox wrote: > > Would anyone like to claim ownership of pyzor? > If no one has staked a claim, I will. Still with out broadband at home :-( > so I can't work on it for another week (hopefully). Mhm. We're using pyzor ourselves on our productive spam-filter. I could take it and maintain it. Additional plus: I do have broadband. :D regards, andreas From buildsys at fedoraproject.org Sat Aug 12 11:58:00 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Sat, 12 Aug 2006 07:58:00 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-12 Message-ID: <20060812115800.5F47C152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 32 bitbake-1.4.2-1.fc5 blender-2.42-6.fc5 bzr-0.9-1.fc5 bzrtools-0.9.0-1.fc5 emelfm2-0.1.8-2.fc5 gnubiff-2.2.1-2.fc5 gtkdatabox-0.7.0.0-1.fc5 gtkwave-3.0.9-1.fc5 ipython-0.7.2-2.fc5 kadu-0.5.0-0.7.20060808svn.fc5 libapreq2-2.08-1.fc5 liferea-1.0.21-2.fc5 lilypond-2.8.6-1.fc5 lilypond-doc-2.8.6-1.fc5 mbuffer-20060728-2.fc5 perl-DateTime-Format-MySQL-0.04-2.fc5 perl-Gtk2-TrayIcon-0.03-2.fc5 perl-Object-InsideOut-1.49-1.fc5 perl-POE-0.3600-1.fc5 perl-POE-Component-JobQueue-0.5500-1.fc5 perl-WWW-Myspace-0.52-2.fc5 python-durus-3.4.1-3.fc5 python-lxml-1.0.2-2.fc5 python-mutagen-1.6-1.fc5 python-paramiko-1.6.1-2.fc5 python-protocols-1.0-0.2.a0dev_r2082.fc5 python-psyco-1.5.1-3.fc5 python-quixote-2.4-3.fc5 python-simpletal-4.1-3.fc5 python-sqlalchemy-0.2.6-2.fc5 python-tpg-3.1.0-2.fc5 scribes-0.2.5-3.fc5 Packages built and released for Fedora Extras 4: 21 bzr-0.9-1.fc4 bzrtools-0.9.0-1.fc4 gtkdatabox-0.7.0.0-1.fc4 gtkwave-3.0.9-1.fc4 ipython-0.7.2-2.fc4 mbuffer-20060728-2.fc4 perl-DateTime-Format-MySQL-0.04-2.fc4 perl-Gtk2-TrayIcon-0.03-2.fc4 perl-Object-InsideOut-1.49-1.fc4 perl-POE-0.3600-1.fc4 perl-POE-Component-JobQueue-0.5500-1.fc4 perl-WWW-Myspace-0.52-2.fc4 python-durus-3.4.1-3.fc4 python-lxml-1.0.2-2.fc4 python-paramiko-1.6.1-2.fc4 python-protocols-1.0-0.2.a0dev_r2082.fc4 python-psyco-1.5.1-3.fc4 python-quixote-2.4-3.fc4 python-simpletal-4.1-3.fc4 python-sqlalchemy-0.2.6-2.fc4 python-tpg-3.1.0-2.fc4 Packages built and released for Fedora Extras development: 42 alleggl-0.4.0-0.4.rc4.fc6 bitbake-1.4.2-1.fc6 blender-2.42-7.fc6 bwidget-1.7.0-3.fc6 bzr-0.9-1.fc6 bzrtools-0.9.0-1.fc6 emelfm2-0.1.8-2.fc6 gnokii-0.6.13-2.fc6 gnubiff-2.2.2-1.fc6 gtkdatabox-0.7.0.0-1.fc6 gtkwave-3.0.9-1.fc6 inkscape-0.44-4.fc6 ipython-0.7.2-2.fc6 k3d-0.5.16.0-3.fc6 kadu-0.5.0-0.7.20060808svn.fc6 knetworkmanager-0.1-0.3.svn20060809.fc6 libapreq2-2.08-1.fc6 liferea-1.0.21-3.fc6 lilypond-2.8.6-1.fc6 lilypond-doc-2.8.6-1.fc6 mbuffer-20060728-2.fc6 perl-DateTime-Format-MySQL-0.04-2.fc6 perl-Gtk2-TrayIcon-0.03-2.fc6 perl-Object-InsideOut-1.49-1.fc6 perl-POE-0.3600-1.fc6 perl-POE-Component-JobQueue-0.5500-1.fc6 perl-POE-Component-SSLify-0.04-2.fc6 perl-WWW-Myspace-0.52-2.fc6 pinball-0.3.1-5.fc6 python-durus-3.4.1-3.fc6 python-lxml-1.0.2-2.fc6 python-mutagen-1.6-1.fc6 python-paramiko-1.6.1-2.fc6 python-protocols-1.0-0.2.a0dev_r2082.fc6 python-psyco-1.5.1-3.fc6 python-quixote-2.4-3.fc6 python-simpletal-4.1-3.fc6 python-sqlalchemy-0.2.6-2.fc6 python-tpg-3.1.0-2.fc6 ruby-postgres-0.7.1-4.fc6 scribes-0.2.5-3.fc6 xscreensaver-5.00-16.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Sat Aug 12 11:58:25 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Sat, 12 Aug 2006 07:58:25 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-12 Message-ID: <20060812115825.F2E56152169@buildsys.fedoraproject.org> azureus: green AT redhat.com 5: 0:2.4.0.3-0.20060529cvs_1.fc5 (FE5) 6: 0:2.4.0.3-0.20060328cvs_5.fc6 (FE6) camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) digikam: mgarski AT post.pl 3: 0:0.8.2-2.fc3 (FE3) 4: 0:0.8.2-1.fc4 (FE4) 5: 0:0.8.2-1.fc5 (FE5) 6: 0:0.8.2-1.fc6 (FE6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: liljencrantz AT gmail.com 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gaim-gaym: cweyl AT alumni.drew.edu 5: 0:0.96-3.fc5 (FE5) 6: 0:0.96-2.fc6 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) koffice: andreas.bierfert AT lowlatency.de 5: 0:1.5.2-1.fc5 (FE5) 6: 0:1.5.1-2.fc6 (FE6) libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) libpqxx: andreas.bierfert AT lowlatency.de 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) lvm2: 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) mozilla: 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.1-2.fc5 (FE5) 6: 0:1.0.1-1.fc5 (FE6) quagga: 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) seamonkey: kengert AT redhat.com 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) smart: Axel.Thimm AT ATrpms.net 5: 0:0.42-35.fc5 (FE5) 6: 0:0.41-31.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.5-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) vorbisgain: noa AT resare.com 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) XaraLX: paul AT all-the-johnsons.co.uk 5: 0:0.7-3.fc5.r1614 (FE5) 6: 0:0.7-2.fc6.r1614 (FE6) From sundaram at fedoraproject.org Sat Aug 12 12:00:38 2006 From: sundaram at fedoraproject.org (Rahul) Date: Sat, 12 Aug 2006 17:30:38 +0530 Subject: Splashy Message-ID: <44DDC2E6.5080600@fedoraproject.org> Hi Anyone interested in packaging http://splashy.alioth.debian.org/wiki/doku.php It's a splash program similar to RHGB Rahul From buildsys at fedoraproject.org Sat Aug 12 12:16:09 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Sat, 12 Aug 2006 12:16:09 -0000 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-12 Message-ID: <20060812121609.7931.24562@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (128 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (128 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (5 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (5 days) libopensync-plugin-evolution2 - 0.18-6.fc5.i386 (5 days) libopensync-plugin-evolution2 - 0.18-6.fc5.ppc (5 days) libopensync-plugin-evolution2 - 0.18-6.fc5.x86_64 (5 days) wine-core - 0.9.17-1.fc6.i386 (17 days) bdpepple AT ameritech.net contact-lookup-applet - 0.14-3.fc6.i386 (5 days) contact-lookup-applet - 0.14-3.fc6.ppc (5 days) contact-lookup-applet - 0.14-3.fc6.x86_64 (5 days) byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (24 days) gaim-guifications - 2.12-3.fc5.ppc (24 days) gaim-guifications - 2.12-3.fc5.x86_64 (24 days) cweyl AT alumni.drew.edu gaim-gaym - 0.96-2.fc6.i386 (24 days) gaim-gaym - 0.96-2.fc6.ppc (24 days) gaim-gaym - 0.96-2.fc6.x86_64 (24 days) fedora AT leemhuis.info gsynaptics - 0.9.8-1.fc6.ppc (24 days) gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (16 days) amarok - 1.4.1-3.fc6.ppc (16 days) showimg-pgsql - 0.9.5-7.fc4.i386 (5 days) showimg-pgsql - 0.9.5-7.fc4.ppc (5 days) showimg-pgsql - 0.9.5-7.fc4.x86_64 (5 days) showimg-pgsql - 0.9.5-7.fc5.i386 (5 days) showimg-pgsql - 0.9.5-7.fc5.ppc (5 days) showimg-pgsql - 0.9.5-7.fc5.x86_64 (5 days) green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.i386 (17 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (17 days) azureus - 2.4.0.3-0.20060328cvs_5.fc6.x86_64 (17 days) jogl - 1.1.1-14.fc5.ppc (20 days) ivazquez AT ivazquez.net deskbar-applet - 2.14.1.1-1.fc6.i386 (5 days) deskbar-applet - 2.14.1.1-1.fc6.ppc (5 days) deskbar-applet - 2.14.1.1-1.fc6.x86_64 (5 days) gnome-applet-music - 0.9.0-1.fc6.i386 (24 days) gnome-applet-music - 0.9.0-1.fc6.ppc (24 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (24 days) nautilus-search-tool - 0.2-1.fc5.i386 (24 days) nautilus-search-tool - 0.2-1.fc5.ppc (24 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (24 days) jkeating AT redhat.com contacts - 0.1-1.i386 (5 days) contacts - 0.1-1.ppc (5 days) contacts - 0.1-1.x86_64 (5 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (24 days) gfontview - 0.5.0-5.fc5.ppc (24 days) gfontview - 0.5.0-5.fc5.x86_64 (24 days) gtkhtml36 - 3.6.2-5.fc6.i386 (24 days) gtkhtml36 - 3.6.2-5.fc6.ppc (24 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (24 days) libvisual-plugins - 0.2.0-3.fc5.i386 (24 days) libvisual-plugins - 0.2.0-3.fc5.i386 (24 days) libvisual-plugins - 0.2.0-3.fc5.ppc (24 days) libvisual-plugins - 0.2.0-3.fc5.ppc (24 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (24 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (24 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (87 days) syck-php - 0.55-7.fc5.i386 (87 days) syck-php - 0.55-7.fc5.ppc (87 days) syck-php - 0.55-7.fc5.ppc (87 days) syck-php - 0.55-7.fc5.x86_64 (87 days) syck-php - 0.55-7.fc5.x86_64 (87 days) petersen AT redhat.com ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.i386 (3 days) ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.ppc (3 days) ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.x86_64 (3 days) rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (24 days) libibverbs - 1.0.3-1.fc6.ppc (24 days) libibverbs - 1.0.3-1.fc6.x86_64 (24 days) libibverbs-utils - 1.0.3-1.fc6.i386 (24 days) libibverbs-utils - 1.0.3-1.fc6.ppc (24 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (24 days) tcallawa AT redhat.com gambas-runtime - 1.0.14-2.fc5.i386 (4 days) thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (24 days) directfb - 0.9.24-5.fc5.ppc (24 days) directfb - 0.9.24-5.fc5.x86_64 (24 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.i386 requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) showimg-pgsql-0.9.5-7.fc5.x86_64 requires libpqxx-2.6.6.so()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.ppc requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.i386 requires libpqxx-2.6.6.so Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.x86_64 requires libpqxx-2.6.6.so()(64bit) Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.ppc requires libpqxx-2.6.6.so Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.i386 requires libgcj.so.7 contact-lookup-applet-0.14-3.fc6.i386 requires libebook-1.2.so.5 contacts-0.1-1.i386 requires libebook-1.2.so.5 deskbar-applet-2.14.1.1-1.fc6.i386 requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.i386 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 gambas-runtime-1.0.14-2.fc5.i386 requires libgettextlib-0.14.5.so gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-2.fc6.i386 requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- azureus-2.4.0.3-0.20060328cvs_5.fc6.x86_64 requires libgcj.so.7()(64bit) contact-lookup-applet-0.14-3.fc6.x86_64 requires libebook-1.2.so.5()(64bit) contacts-0.1-1.x86_64 requires libebook-1.2.so.5()(64bit) deskbar-applet-2.14.1.1-1.fc6.x86_64 requires libebook-1.2.so.5()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-gaym-0.96-2.fc6.x86_64 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) ghc642-gtk2hs-mozembed-0.9.10-2.fc6.x86_64 requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libedata-cal-1.2.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libecal-1.2.so.3()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libebook-1.2.so.5()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.17-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 contact-lookup-applet-0.14-3.fc6.ppc requires libebook-1.2.so.5 contacts-0.1-1.ppc requires libebook-1.2.so.5 deskbar-applet-2.14.1.1-1.fc6.ppc requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.ppc requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-2.fc6.ppc requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gsynaptics-0.9.8-1.fc6.ppc requires synaptics gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 From splinux at fedoraproject.org Sat Aug 12 13:25:38 2006 From: splinux at fedoraproject.org (Damien Durand) Date: Sat, 12 Aug 2006 15:25:38 +0200 Subject: Splashy In-Reply-To: <44DDC2E6.5080600@fedoraproject.org> References: <44DDC2E6.5080600@fedoraproject.org> Message-ID: I can take a look on this. 2006/8/12, Rahul : > > Hi > > > Anyone interested in packaging > > http://splashy.alioth.debian.org/wiki/doku.php > > It's a splash program similar to RHGB > > Rahul > > -- > fedora-extras-list mailing list > fedora-extras-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-extras-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nando at ccrma.Stanford.EDU Sat Aug 12 19:27:28 2006 From: nando at ccrma.Stanford.EDU (Fernando Lopez-Lezcano) Date: Sat, 12 Aug 2006 12:27:28 -0700 Subject: Csound in extras? In-Reply-To: <1155244180.14998.4.camel@localhost.localdomain> References: <1155244180.14998.4.camel@localhost.localdomain> Message-ID: <1155410848.20154.4.camel@cmn3.stanford.edu> On Thu, 2006-08-10 at 17:09 -0400, Dan Williams wrote: > Hi, > > I seem to recall seeing a mail recently asking whether Csound > (http://www.csounds.com/ ) was suitable for proposal to Fedora Extras, > but there were some legal questions. Am I eating too many magic > shrooms? Csound5 is now lgpl, see: http://csound.sourceforge.net/ (that was not the case with the previous major version) -- Fernando From chris.stone at gmail.com Sat Aug 12 23:52:22 2006 From: chris.stone at gmail.com (Christopher Stone) Date: Sat, 12 Aug 2006 16:52:22 -0700 Subject: Multi-Lib Question Message-ID: Hi this may be a little off-topic or a stupid question, but I recently tried to build a 32-bit application on Fedora's x86_64 arch. I thought that all I needed to do was add -m32 to the CFLAGS and LDFLAGS to the makefile, but as it turns out the linking was problematic. It turns out I did not have the 32-bit .so file needed for linking, so I attempted to install it with "yum install expat-devel.i386" but yum was unable to find the package. Basically I needed to hard code a softlink in order to get the application to link. So the bottom line I guess is, how do I install a 32bit devel package on a Fedora x86_64 system? And if 32bit libraries are provided as default for this system, why aren't their 32bit devel counterparts also provided? From chris.stone at gmail.com Sun Aug 13 00:27:26 2006 From: chris.stone at gmail.com (Christopher Stone) Date: Sat, 12 Aug 2006 17:27:26 -0700 Subject: Multi-Lib Question In-Reply-To: References: Message-ID: On 8/12/06, Christopher Stone wrote: > Hi this may be a little off-topic or a stupid question, but I recently > tried to build a 32-bit application on Fedora's x86_64 arch. I > thought that all I needed to do was add -m32 to the CFLAGS and LDFLAGS > to the makefile, but as it turns out the linking was problematic. It > turns out I did not have the 32-bit .so file needed for linking, so I > attempted to install it with "yum install expat-devel.i386" but yum > was unable to find the package. Basically I needed to hard code a > softlink in order to get the application to link. > > So the bottom line I guess is, how do I install a 32bit devel package > on a Fedora x86_64 system? And if 32bit libraries are provided as > default for this system, why aren't their 32bit devel counterparts > also provided? > After thinking about this a bit I realize the devel packages would conflict with the header files. It seems to me that the best solution to this problem is to create noarch and arch specific devel packages. So header files can go in the noarch part and the .a and .so files can go in the arch specific part. The noarch package would depend on the arch specific one. I guess this is probably too much to ask for however. :| From jkeating at redhat.com Sun Aug 13 00:38:45 2006 From: jkeating at redhat.com (Jesse Keating) Date: Sat, 12 Aug 2006 20:38:45 -0400 Subject: Multi-Lib Question In-Reply-To: References: Message-ID: <200608122038.45489.jkeating@redhat.com> On Saturday 12 August 2006 20:27, Christopher Stone wrote: > After thinking about this a bit I realize the devel packages would > conflict with the header files. > > It seems to me that the best solution to this problem is to create > noarch and arch specific devel packages. ?So header files can go in > the noarch part and the .a and .so files can go in the arch specific > part. ?The noarch package would depend on the arch specific one. Fedora Core 5's multi-lib environment was geared toward running 32bit apps, and only a small number of packages were setup to be multi-lib. In FC6, we're also targetting app development, and as such made some changes to rpm and to our tree building software so that any package that has a -devel subpackage will be considered multi-lib and brought into the tree. If you wish to test this out, please try Fedora Core 6 Test 2. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From chris.stone at gmail.com Sun Aug 13 01:15:30 2006 From: chris.stone at gmail.com (Christopher Stone) Date: Sat, 12 Aug 2006 18:15:30 -0700 Subject: Multi-Lib Question In-Reply-To: <200608122038.45489.jkeating@redhat.com> References: <200608122038.45489.jkeating@redhat.com> Message-ID: On 8/12/06, Jesse Keating wrote: > On Saturday 12 August 2006 20:27, Christopher Stone wrote: > > After thinking about this a bit I realize the devel packages would > > conflict with the header files. > > > > It seems to me that the best solution to this problem is to create > > noarch and arch specific devel packages. So header files can go in > > the noarch part and the .a and .so files can go in the arch specific > > part. The noarch package would depend on the arch specific one. > > Fedora Core 5's multi-lib environment was geared toward running 32bit apps, > and only a small number of packages were setup to be multi-lib. > > In FC6, we're also targetting app development, and as such made some changes > to rpm and to our tree building software so that any package that has > a -devel subpackage will be considered multi-lib and brought into the tree. > If you wish to test this out, please try Fedora Core 6 Test 2. > HI Jesse, this is great news! Thanks for the info. I will be looking forward to FC6 :) From dcbw at redhat.com Sun Aug 13 01:20:15 2006 From: dcbw at redhat.com (Dan Williams) Date: Sat, 12 Aug 2006 21:20:15 -0400 Subject: Csound in extras? In-Reply-To: <1155410848.20154.4.camel@cmn3.stanford.edu> References: <1155244180.14998.4.camel@localhost.localdomain> <1155410848.20154.4.camel@cmn3.stanford.edu> Message-ID: <1155432015.2841.1.camel@localhost.localdomain> On Sat, 2006-08-12 at 12:27 -0700, Fernando Lopez-Lezcano wrote: > On Thu, 2006-08-10 at 17:09 -0400, Dan Williams wrote: > > Hi, > > > > I seem to recall seeing a mail recently asking whether Csound > > (http://www.csounds.com/ ) was suitable for proposal to Fedora Extras, > > but there were some legal questions. Am I eating too many magic > > shrooms? > > Csound5 is now lgpl, see: > http://csound.sourceforge.net/ > (that was not the case with the previous major version) Yeah, I confirmed this with Barry personally on Friday. I also inspected a bunch of the code for 5.02.1 and found that LGPL license headers are present on source files as well. What's _not_ FLOSS are some of the samples that are traditionally bundled with Csound, for example in the RPM available from the download site. Those aren't included in the source tarball though, so I think I'll go ahead and put together a proposal for Extras. dan From bugs.michael at gmx.net Sun Aug 13 01:53:41 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Sun, 13 Aug 2006 03:53:41 +0200 Subject: Multi-Lib Question In-Reply-To: References: Message-ID: <20060813035341.201a3a67.bugs.michael@gmx.net> On Sat, 12 Aug 2006 17:27:26 -0700, Christopher Stone wrote: > > Hi this may be a little off-topic or a stupid question, but I recently > > tried to build a 32-bit application on Fedora's x86_64 arch. I > > thought that all I needed to do was add -m32 to the CFLAGS and LDFLAGS > > to the makefile, but as it turns out the linking was problematic. It > > turns out I did not have the 32-bit .so file needed for linking, so I > > attempted to install it with "yum install expat-devel.i386" but yum > > was unable to find the package. Basically I needed to hard code a > > softlink in order to get the application to link. > > > > So the bottom line I guess is, how do I install a 32bit devel package > > on a Fedora x86_64 system? And if 32bit libraries are provided as > > default for this system, why aren't their 32bit devel counterparts > > also provided? > > > > After thinking about this a bit I realize the devel packages would > conflict with the header files. > > It seems to me that the best solution to this problem is to create > noarch and arch specific devel packages. So header files can go in > the noarch part and the .a and .so files can go in the arch specific > part. The noarch package would depend on the arch specific one. That doesn't make much sense, since files with the same checksum don't conflict and can be in multiple packages. The conflicts would be in the arch-specific files (e.g. arch-specific header contents). From panemade at gmail.com Sun Aug 13 03:06:28 2006 From: panemade at gmail.com (=?UTF-8?Q?Parag_N(=E0=A4=AA=E0=A4=B0=E0=A4=BE=E0=A5=9A)?=) Date: Sun, 13 Aug 2006 08:36:28 +0530 Subject: Local repository setup problem with fedora-mirror.py In-Reply-To: <645d17210608110244ha615e8eid74da19352e8e7a4@mail.gmail.com> References: <645d17210608110244ha615e8eid74da19352e8e7a4@mail.gmail.com> Message-ID: Hi, On 8/11/06, Jonathan Underwood wrote: > On 10/08/06, Parag N(????) wrote: > > Hi, > > I was using local repositories setup for mock build successfully > > on FC5 previously. Now i formatted my system and installed FC6 Test 2 > > and tried to follow the same steps that i did from my page > > http://fedoraproject.org/wiki/ParagNemade/MockSetupUsingLocalMirror > > Parag - this is a really useful page - I wonder if it could be moved > somewhere more visible, i.e. made part of the main FE wiki pages. Thanks for appreciating my work. I will be very happy if this page is moved to main FE pages. But i don't know how can i do that? Do anyone have suggestions on this then kindly mail back to me. Thanks & Regards, Parag. > -- > fedora-extras-list mailing list > fedora-extras-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-extras-list > From sundaram at fedoraproject.org Sun Aug 13 03:11:06 2006 From: sundaram at fedoraproject.org (Rahul) Date: Sun, 13 Aug 2006 08:41:06 +0530 Subject: Local repository setup problem with fedora-mirror.py In-Reply-To: References: <645d17210608110244ha615e8eid74da19352e8e7a4@mail.gmail.com> Message-ID: <44DE984A.9040106@fedoraproject.org> Parag N(????) wrote: > Hi, > On 8/11/06, Jonathan Underwood wrote: >> On 10/08/06, Parag N(????) wrote: >> > Hi, >> > I was using local repositories setup for mock build successfully >> > on FC5 previously. Now i formatted my system and installed FC6 Test 2 >> > and tried to follow the same steps that i did from my page >> > http://fedoraproject.org/wiki/ParagNemade/MockSetupUsingLocalMirror >> >> Parag - this is a really useful page - I wonder if it could be moved >> somewhere more visible, i.e. made part of the main FE wiki pages. > Thanks for appreciating my work. I will be very happy if this page > is moved to main FE pages. But i don't know how can i do that? Do > anyone have suggestions on this then kindly mail back to me. > You have to a rename. Click on the menu in the side bar and select "Rename Page" Rahul. From rc040203 at freenet.de Sun Aug 13 03:19:38 2006 From: rc040203 at freenet.de (Ralf Corsepius) Date: Sun, 13 Aug 2006 05:19:38 +0200 Subject: Multi-Lib Question In-Reply-To: <20060813035341.201a3a67.bugs.michael@gmx.net> References: <20060813035341.201a3a67.bugs.michael@gmx.net> Message-ID: <1155439178.2403.175.camel@mccallum.corsepiu.local> On Sun, 2006-08-13 at 03:53 +0200, Michael Schwendt wrote: > On Sat, 12 Aug 2006 17:27:26 -0700, Christopher Stone wrote: > > > > Hi this may be a little off-topic or a stupid question, but I recently > > > tried to build a 32-bit application on Fedora's x86_64 arch. I > > > thought that all I needed to do was add -m32 to the CFLAGS and LDFLAGS > > > to the makefile, but as it turns out the linking was problematic. It > > > turns out I did not have the 32-bit .so file needed for linking, so I > > > attempted to install it with "yum install expat-devel.i386" but yum > > > was unable to find the package. Basically I needed to hard code a > > > softlink in order to get the application to link. > > > > > > So the bottom line I guess is, how do I install a 32bit devel package > > > on a Fedora x86_64 system? And if 32bit libraries are provided as > > > default for this system, why aren't their 32bit devel counterparts > > > also provided? > > > > > > > After thinking about this a bit I realize the devel packages would > > conflict with the header files. A multilib-ready package does not conflict in its header files. It implements an arch-independent API. > > It seems to me that the best solution to this problem is to create > > noarch and arch specific devel packages. So header files can go in > > the noarch part and the .a and .so files can go in the arch specific > > part. The noarch package would depend on the arch specific one. > > That doesn't make much sense, since files with the same checksum don't > conflict and can be in multiple packages. The conflicts would be in > the arch-specific files (e.g. arch-specific header contents). Ralf From panemade at gmail.com Sun Aug 13 03:34:02 2006 From: panemade at gmail.com (=?UTF-8?Q?Parag_N(=E0=A4=AA=E0=A4=B0=E0=A4=BE=E0=A5=9A)?=) Date: Sun, 13 Aug 2006 09:04:02 +0530 Subject: Local repository setup problem with fedora-mirror.py In-Reply-To: <44DE984A.9040106@fedoraproject.org> References: <645d17210608110244ha615e8eid74da19352e8e7a4@mail.gmail.com> <44DE984A.9040106@fedoraproject.org> Message-ID: Hi, On 8/13/06, Rahul wrote: > Parag N(????) wrote: > > Hi, > > On 8/11/06, Jonathan Underwood wrote: > >> On 10/08/06, Parag N(????) wrote: > >> > Hi, > >> > I was using local repositories setup for mock build successfully > >> > on FC5 previously. Now i formatted my system and installed FC6 Test 2 > >> > and tried to follow the same steps that i did from my page > >> > http://fedoraproject.org/wiki/ParagNemade/MockSetupUsingLocalMirror > >> > >> Parag - this is a really useful page - I wonder if it could be moved > >> somewhere more visible, i.e. made part of the main FE wiki pages. > > Thanks for appreciating my work. I will be very happy if this page > > is moved to main FE pages. But i don't know how can i do that? Do > > anyone have suggestions on this then kindly mail back to me. > > > > You have to a rename. Click on the menu in the side bar and select > "Rename Page" Thanks Rahul. I did that and now same page can be accessed at http://fedoraproject.org/wiki/MockSetupUsingLocalMirror Regards, Parag. From seg at haxxed.com Sun Aug 13 06:43:29 2006 From: seg at haxxed.com (Callum Lerwick) Date: Sun, 13 Aug 2006 01:43:29 -0500 Subject: FE6 Orphan Warning: dxpc gtkglarea2 soundtracker In-Reply-To: <44DB711E.4020407@redhat.com> References: <44DB711E.4020407@redhat.com> Message-ID: <1155451409.14640.12.camel@localhost> On Thu, 2006-08-10 at 13:47 -0400, Warren Togami wrote: > soundtracker I'm taking soundtracker. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From j.w.r.degoede at hhs.nl Sun Aug 13 08:19:19 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Sun, 13 Aug 2006 10:19:19 +0200 Subject: The bug squad is hiring! In-Reply-To: <44DDACB3.6000509@fedoraproject.org> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> <44DD6914.4080401@hhs.nl> <44DDACB3.6000509@fedoraproject.org> Message-ID: <44DEE087.4090708@hhs.nl> Rahul wrote: > Hans de Goede wrote: >> Wiki maintainers, where should this page be (maybe under Extras/SIGs? >> But its not soley for Extras). >> > > http://fedoraproject.org/wiki/BugZappers > Yes that might work, but that is a bit different that is about triaging bug, helping the bug owners to get better bug reports. Denis and mine effort is about helping bug owners by really fixing some (low hanging easy, great impact) bugs, thus do the debugging hunt it down to the line of code and create a patch. So similar but different. Should I just add a section to the above page for our effort / work? Regards, Hans From j.w.r.degoede at hhs.nl Sun Aug 13 10:44:43 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Sun, 13 Aug 2006 12:44:43 +0200 Subject: ClanLib abi breakage headsup Message-ID: <44DF029B.4050800@hhs.nl> Hi, I will be pushing an update from ClanLib 0.8.0-RC2 to 0.8.0 (final) judging from the changes in some header files this will break the ABI (without changing the soname!). The ABI changes are small and will probably not influence most programs as they wont be using this part of the ABI, still a recompile is advised! AFAIK the only ClanLib using package is pingus which I maintain myself and will recompile (even though it works fine with the new ClanLib). Because of this ABI-breakage I'm only pushing this for devel leaving FC-5 at RC2. Regards, Hans From sundaram at fedoraproject.org Sun Aug 13 14:19:49 2006 From: sundaram at fedoraproject.org (Rahul) Date: Sun, 13 Aug 2006 19:49:49 +0530 Subject: The bug squad is hiring! In-Reply-To: <44DEE087.4090708@hhs.nl> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> <44DD6914.4080401@hhs.nl> <44DDACB3.6000509@fedoraproject.org> <44DEE087.4090708@hhs.nl> Message-ID: <44DF3505.3090309@fedoraproject.org> Hans de Goede wrote: > > Rahul wrote: >> Hans de Goede wrote: >>> Wiki maintainers, where should this page be (maybe under Extras/SIGs? >>> But its not soley for Extras). >>> >> http://fedoraproject.org/wiki/BugZappers >> > > Yes that might work, but that is a bit different that is about triaging > bug, helping the bug owners to get better bug reports. Denis and mine > effort is about helping bug owners by really fixing some (low hanging > easy, great impact) bugs, thus do the debugging hunt it down to the line > of code and create a patch. So similar but different. > > > Should I just add a section to the above page for our effort / work? > > Yes. Fixing low hanging bugs is part of triaging IMO. Rahul From kushaldas at gmail.com Sun Aug 13 18:53:42 2006 From: kushaldas at gmail.com (Kushal Das) Date: Mon, 14 Aug 2006 00:23:42 +0530 Subject: Need a list of educational packages Message-ID: <200608140023.42193.kushaldas@gmail.com> Hi, I am making a offline tool to install stuffs from fedora extras & livna. I want to include different educational/development tools available in the extras repo, which can help the school/engg. students. For that I need a list of packages. Can anyone send me the names.. Regards, Kushal From andy at smile.org.ua Sun Aug 13 19:01:44 2006 From: andy at smile.org.ua (Andy Shevchenko) Date: Sun, 13 Aug 2006 22:01:44 +0300 Subject: Need a list of educational packages In-Reply-To: <200608140023.42193.kushaldas@gmail.com> References: <200608140023.42193.kushaldas@gmail.com> Message-ID: <44DF7718.8000700@smile.org.ua> Kushal Das wrote: > I am making a offline tool to install stuffs from fedora extras & livna. I > want to include different educational/development tools available in the > extras repo, which can help the school/engg. students. For that I need a list > of packages. > Can anyone send me the names.. At first step you can use the comps.xml file (CVS module comps) and CVS:owners/owners.list. May be good solution to grep specs by Group tag. -- With best regards, Andy Shevchenko. mailto: andy at smile.org.ua From bugs.michael at gmx.net Sun Aug 13 19:52:01 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Sun, 13 Aug 2006 21:52:01 +0200 Subject: [Fedora Project Wiki] Update of "Extras/FC6Status" by ChrisWeyl In-Reply-To: <20060812192214.4406.54772@fpserv.linux.duke.edu> References: <20060812192214.4406.54772@fpserv.linux.duke.edu> Message-ID: <20060813215201.5c627bef.bugs.michael@gmx.net> On Sat, 12 Aug 2006 19:22:14 -0000, fedorawiki-noreply at fedoraproject.org wrote: > The following page has been changed by ChrisWeyl: > http://www.fedoraproject.org/wiki/Extras/FC6Status > > ------------------------------------------------------------------------------ > - > + * gaim-gaym - upstream code is not yet ready for the level of gaim in fc6 Pardon? Builds have been released for fc5 and fc4 already long ago, so removing the packages from the devel repo would break the upgrade path. From wtogami at redhat.com Sun Aug 13 20:01:59 2006 From: wtogami at redhat.com (Warren Togami) Date: Sun, 13 Aug 2006 16:01:59 -0400 Subject: Anyone want pyzor? In-Reply-To: References: <44DB6809.201@redhat.com> <29348.203.118.135.21.1155240571.squirrel@www.knox.net.nz> Message-ID: <44DF8537.4050802@redhat.com> Andreas Thienemann wrote: > On Fri, 11 Aug 2006, Michael J. Knox wrote: > >>> Would anyone like to claim ownership of pyzor? >> If no one has staked a claim, I will. Still with out broadband at home :-( >> so I can't work on it for another week (hopefully). > Mhm. We're using pyzor ourselves on our productive spam-filter. > > I could take it and maintain it. Additional plus: I do have broadband. :D > > regards, > andreas > How about this, assign primary ownership to Andreas and you can coordinate on joint ownership. I trust that most of the cvsextras members would do the right thing. This good? Warren Togami wtogami at redhat.com From toshio at tiki-lounge.com Sun Aug 13 20:06:55 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Sun, 13 Aug 2006 13:06:55 -0700 Subject: FESCo Meeting Summary for 2006-08-10 Message-ID: <1155499615.3114.6.camel@localhost> = 2006 August 10 FESCo = Meeting Summaries are posted on the wiki at: http://www.fedoraproject.org/wiki/Extras/SteeringCommittee/Meetings == Attending == * warren * thl * scop * c4chris * rdieter * tibbs * abadger1999 * bpepple * dgilmore == Summary == === Mass Rebuild === * Plan and questions are on the wiki at http://www.fedoraproject.org/wiki/Extras/Schedule/FC6MassRebuild * Which packages need to be rebuilt * sha256sum wasn't implemented in rpm so that isn't a factor * Minimal buildroots have been implemented and will influence most packages * Decided to go with the original plan: If a maintainer thinks a rebuild isn't required, they write a commit message that tells why not. * Criteria that maintainers should apply is everything that isn't content should be rebuilt. === comps.xml === * The comps.xml script produced a big list: http://www.fedoraproject.org/wiki/Extras/PackageStatus * Commandline stuff should be included * Packages should not be listed twice (confuses end users) * nagmails will be sent so people know they have packages needing looking at === Legacy in buildroots === * Voted to activate legacy in buildroots and discuss maintainers responsibilities later * tibbs will send out an email regarding maintainer responsibilities * thl will document that FE branches in maintenance mode use Legacy packages === Ctrl-C Problem === * Async notification seems to be the only method to guarantee commit mail is sent * Warren to take that up at the infrastructure meeting === Packaging Committee Report === * Python .pyos are to be included directly in packages instead of % ghosted * c4chris is looking for a script to file bugzilla bugs for packages that need fixing * scop has related changes to the python spec template prepared: http://koti.welho.com/vskytta/pyspec.patch === Sponsorship Nominations === * rdieter was accepted === Misc === * FESCo members are now on both FAB and -maintainers === Future Elections === * Draft is at: http://www.fedoraproject.org/wiki/Extras/Schedule/ElectionDraft * No objections to it yet. Wait one more week and then vote on acceptance === Package Database === * http://www.fedoraproject.org/wiki/Extras/Schedule/PackageDatabase * http://www.fedoraproject.org/wiki/Infrastructure/PackageDatabase * c4chris posted some brain dumps about this to extras-list * c4chris joining infrastructure list so he can help coordinate between the extras community needs and infrastructure people doing the implementation === Free discussion === * zaptel-kmod and kmod policy in general * Main question: Should kmods which have no intention of ever moving into the mainstream kernel be allowed in? * If the package is well maintained and end-users accept the risk, why not? * Fedora kernel developers have stated they will not debug kernel problems where users have kernel mods not from upstream installed * thl to take the question to FAB * http://fedoraproject.org/wiki/Extras/PackageEndOfLife documents how to remove a package from Extras (in case it is renamed upstream, moved to Core, etc) === After Meeting Discussion === * Too many items on the agenda per meeting? Items to discuss moving onto email instead of in the weekly IRC meetings * Possibly move packaging committee report to email list * To be able to discuss before the next packaging meeting, the FESCo meeting can't be directly after the packaging meeting. One would have to change times/dates * Owners of a task update the status on the wiki before the meeting * New sponsor discussion could happen entirely on list: * Use two lists cvs-sponsors and fesco-list == Log == {{{ (09:55:13) ***warren here. (09:59:42) thl has changed the topic to: FESCo meeting in progress (09:59:46) thl: hi everyone (09:59:54) thl: who's around? (09:59:57) Rathann: o/ (10:00:01) Rathann: :> (10:00:07) ***c4chris__ is here (10:00:11) scop [n=scop] entered the room. (10:00:15) c4chris__ is now known as c4chris (10:00:18) drfickle left the room (quit: "Please do not reply to this burrito"). (10:00:24) rdieter: here. (10:00:36) tibbs: president. (10:00:41) warren: president? (10:00:56) tibbs: Used to say that in grade school. (10:00:59) c4chris: s/id// (10:01:07) c4chris: :) (10:01:24) thl: okay, then let's start slowly... (10:01:25) ***abadger1999 here (10:01:33) thl has changed the topic to: FESCo meeting in progress -- M{ae}ss-Rebuild (10:01:54) ***bpepple is here. (10:01:55) thl: scop, I assigned that job to you some days ago (10:02:06) scop: works4me (10:02:23) scop: but I've noticed a bunch of "fc6 respin" builds recently (10:02:29) thl: scop, there are some question still open; see http://www.fedoraproject.org/wiki/Extras/Schedule/FC6MassRebuild (10:03:02) thl: scop, can you work out the details that are still below "to be discussed" (10:03:17) thl: then we can discuss it in the next meeting (10:03:26) thl: (or now if someone prefers) (10:03:45) abadger1999: rpm signing w/ sha256sum seems to affect all packages (10:03:53) scop: I can do that, but I think those look pretty much like no-brainers (10:03:57) abadger1999: So the answer to which packages need rebuilding would be all. (10:04:04) scop: good point (10:04:13) thl: scop, probably, but someone need to work them out anyway ;-) (10:04:14) f13: abadger1999: that didn't make it in (10:04:22) f13: abadger1999: there is no sha256sum. (10:04:38) ***cweyl is here (rabble) (10:04:44) rdieter: is sha256sum signing in place now/yet (no?)? (10:04:48) f13: abadger1999: so the real answer is anything that is gcc compiled. (10:05:08) f13: rdieter: I don't think the patches even went into our rpm package yet. It was nacked to do such signing for FC6/RHEL5 (10:05:27) f13: the option may be patched into rpm, but it won't be enabled by default. (10:05:27) abadger1999: What about rebuilding with minimal buildroots? (10:05:45) ***dgilmore is kinda here (10:05:54) f13: abadger1999: certainly possible criteria (10:06:01) c4chris: And do we start on August 28 ? (10:06:17) f13: now that Extras has the minimal roots, you could add 'anything that hasn't built since ' where foo is the date that the minimal buildroots went into place. (10:06:29) thl: c4chris, that's the plan currently, but I suggest we discuss this next week again (or the week after that) (10:06:37) c4chris: k (10:07:01) dgilmore: abadger1999: minimal buildroots are in place and the buildsys-build packages have been fixed (10:07:20) thl: well, a lot of people don't like a mass-rebuild were everything is rebuild (10:07:28) f13: abadger1999: for Core, the criteria was: Any binary compiled package (for gnu-hash support), any package that hasn't yet been built in brew (our minimal buildroot stuff), and any package that was still being pulled in from FC5. (10:07:49) thl: because it creates lot's of downloads that are unnesessary for people (10:08:07) thl: but if we want to rebuild everything to make sure that it stil builds -> okay for me (10:08:24) c4chris: thl, we are talking devel here (10:08:43) thl: c4chris, yes, but devel will become FC6 (10:08:45) c4chris: I think we need the mass rebuild (10:08:47) rdieter: c4chris++ right, better to be safe than sorry later. (10:08:59) thl: and people updateing from FC5 have the downloads then, too (10:09:11) c4chris: thl, become is the key word... (10:09:15) f13: rebuilding for gnu-hash is a big bonus (10:09:28) f13: I think people would like the performance increase it can give. (10:09:30) warren: FC3 and FC6 will be Extras releases that continue to be used long after FC4 and FC5 are retired for obvious reasons. Rebuilding FC6 Extras now is a good idea. (10:09:47) thl: okay, so a real mass rebuild (10:09:56) warren: I guarantee it will also find more bugs. (10:09:57) thl: we should post this to the list for discussion (10:10:00) scop: it's just plain silly to rebuild eg. huge game content packages that aren't anything else but stuff copied from the tarball to the file system (10:10:05) thl: who will manage that? (10:10:25) warren: scop, what if we setup an explicit exclusion list? owners can request packages to exclude. (10:11:17) scop: sure, if there's someone to review/maintain that list (10:11:36) scop: personally, I think the original plan would work well enough (10:11:45) warren: Are we proposing that we automatically rebuild everything, or first ask maintainers to do it themselves to see who is AWOL? (10:11:58) thl: warren, ask maintainers (10:11:59) c4chris: warren, ask maintainers (10:12:04) rdieter: scop, warren: isn't that what "needs.rebuild" on FC6MassRebuild? (10:12:08) warren: If that's the case, then they can deal with their own exclusions. (10:12:21) c4chris: warren, I think so too (10:12:35) warren: OK, this plan is good. (10:13:03) warren: > are there still 3 orphans in devel repo according to the package report: dxpc gtkglarea2 soundtracker. What do do? Remove them? (10:13:09) thl: does anyone want to annouce this plan to the list for discussion? (10:13:14) f13: ask people, give it a week or two, then step in and buildthe ones that haven't piped up? (10:13:18) thl: or do we simply mention it in the summary? (10:13:19) warren: One more warning on the mailing list asking for owners, with Aug 28th deadline to remove if nobody claims it. (10:13:36) rdieter: warren++ (10:13:47) thl: warren, +1 (10:13:47) c4chris: warren, yup (10:13:55) bpepple: warren: +1 (10:14:03) warren: I'll do that warning now... (10:14:23) scop: does anything else depend on any of those three? (10:14:30) thl: warren, let me check if those three are still around first (or if there are others still around) (10:14:33) warren: good question, I'll check (10:14:36) tibbs: dxpc was rebuilt fairly recently. (10:15:04) thl: warren, no, seems those three are the only ones according to the PackageStatus page (10:15:18) rdieter: I updated/built dxpc recently... so that it would be in good shape for any potential new maintainer. (10:15:23) ***f13 steps out (10:15:37) thl: okay, so again: does anyone want to annouce this new plan to the list for discussion? or do we simply mention it in the summary? (10:15:48) scop: one more item: what happens if a maintainer does not take care of his rebuilds? (10:15:52) warren: rdieter, without anybody responsible though, do we really want to keep it? (10:16:02) scop: thl, I thought warren said he'd announce it (10:16:06) rdieter: warren: no maintainer -> remove it. (10:16:23) warren: scop, I said I'd announce the orphan removal warning (10:16:26) thl: scop, I though warren want's to warn that those three might get removed? (10:16:52) scop: yep... so what's the new plan thl was talking about? (10:17:00) tibbs: BTW, I count 37 pachages belonging to extras-orphan at fedoraproject.org in the current owners.list. (10:17:02) scop: Extras/Schedule/FC6MassRebuild? (10:17:26) thl: scop, I thought we rebuild everything now (besides big data-only packages)? (10:17:38) thl: that's the impression I got (10:18:15) warren: How about rebuild everything *EXCEPT* maintainers can choose to explicitly skip it if they have a good reason? (10:18:16) c4chris: thl, right, but that's pretty much what FC6MassRebuild says, no? (10:18:31) warren: ooh... (10:18:34) scop: c4chris, exactly (10:18:38) thl: warren, we need to define "good reason" in that case (10:18:45) warren: How about rebuild everything *EXCEPT* maintainers can choose to explicitly skip it if they have a good reason? Except they MUST rebuild if it is demonstrated that a rebuild would fail. (10:19:05) warren: Binaries without GNU_HASH always rebuild? (10:19:13) warren: perl modules built against earlier perl versions? (10:19:15) warren: python? (10:19:16) thl: warren, Binaries without GNU_HASH always rebuild +1 (10:19:44) cweyl: warren: so basically everything that isn't content? (10:20:25) c4chris: cweyl, yes that's a good way to put it (10:21:23) abadger1999: cweyl: Sounds good. So everything goes through the minimal buildroot. (10:21:38) thl: "so basically everything that isn't content" -- +1, 0 or -1 please! (10:21:45) scop: as a general rule, works4me (10:21:45) warren: Content must be rebuilt *IF* it would fail to rebuild. (10:21:51) thl: "everything that isn't content" +0.66 (10:22:02) scop: warren, if it fails to rebuild, it can't be rebuilt (10:22:11) warren: Then it must be fixed? (10:22:25) scop: yes (10:22:27) warren: How about a separate exclude.list that contains (10:22:31) warren: packagename reason (10:22:51) warren: uqm-bigasscontent 1GB of game data that doesn't change. (10:23:02) rdieter: warren: do we really care about the reason? (10:23:13) Nodoid [n=paul] entered the room. (10:23:27) scop: I still think that the commit message to needs.rebuild is enough (10:23:38) c4chris: scop, +1 (10:23:42) thl: scop, +1 (10:23:42) abadger1999: scop: +1 (10:24:01) warren: hmm.. I guess (10:24:02) warren: ok (10:24:04) tibbs: !2 (10:24:04) c4chris: "everything that isn't content" +1 (10:24:08) tibbs: crap. (10:24:12) tibbs: +1 (10:24:28) bpepple: +1 (10:24:45) rdieter: I agree with scop, why isn't needs.rebuild sufficient? (or is this orthogonal to that?) (10:25:25) thl: guys we run late (10:25:38) warren: Let's move on (10:25:42) rdieter: ok (10:25:44) thl: afaics the current plan looks like this: (10:25:47) scop: we use needs.rebuild, but append something like "as a general rule, everything that is not pure content should be rebuilt" to FC6MassRebuild (10:25:53) thl: "everything that isn't content need a rebuild" (10:26:06) thl: "a needs.rebuild file will be placed into cvs" (10:26:31) thl: and if people don#t rebuild stuff they have to mention the reasons in the cvs delete commits message of needs.rebuild (10:26:37) thl: that okay for everybody? (10:26:40) ***warren looks at the 37 orphans... (10:26:42) c4chris: thl, scop: +1 (10:26:46) rdieter: +1 (10:26:55) scop: +1 (10:27:02) abadger1999: +1 (10:27:04) tibbs: +1 (10:27:05) bpepple: +1 (10:27:11) thl: okay, then let's move on (10:27:24) thl has changed the topic to: FESCO meeting -- Use comps.xml properly (10:27:26) thl: c4chris ? (10:27:31) warren: I suggested the exclude.list with reasons because it is easier to search than commit messages (10:27:35) warren: but that's fine (10:27:38) c4chris: Well I produced a big list... (10:27:54) c4chris: There was another idea to trim down soem more libs (10:28:17) thl: c4chris, do you want to work further on that idea and the stuff in general? (10:28:22) c4chris: So far, only Hans has added stuff to comps... (10:28:49) scop: warren, searching for needs.rebuild in a folder containing commit mails should work (10:28:49) c4chris: thl, a few things are not really clear: (10:28:56) thl: c4chris, we should send out mails directly to the maintainers when we now what needs to be in comps (and what not) (10:29:07) c4chris: do we also want cmdline stuff? (10:29:09) thl: then at least some maintainers will add stuff (10:29:19) thl: c4chris, cmdline stuff -> IMHO yes (10:29:38) c4chris: and do we allow packages listed twice? (10:29:42) thl: c4chris, or how does core handle cmdline stuff? (10:30:00) thl: c4chris, twiece? good question. Maybe you should ask jeremy or f13 (10:30:16) c4chris: thl, I think there are cmdline tools in Core too (10:30:17) scop: I'd suggest a SIG or a special group for taking care of comps (10:30:20) rdieter: c4chris: twice, as in more than one section/group? (10:30:25) jeremy: c4chris: packages being listed twice should be avoided (10:30:28) c4chris: rdieter, yes (10:30:34) jeremy: it leads to lots of user confusion (10:30:41) c4chris: jeremy, k, I thought so (10:30:54) rdieter: agreed, pick one(primary) group (and stick with it). (10:30:56) thl: scop, well, do you want to run the SIG? (10:31:10) warren: c4chris, twice is fine (10:31:17) warren: jeremy, eh? (10:31:24) thl: scop, I think we need a QA sig that looks after stuff like this (10:31:45) c4chris: thl, we sorta have a QA SIG... :-) (10:31:49) scop: thl, no, I'm not personally terribly interested in it (10:31:50) warren: Hmm, I might be thinking of the common practice of listing packages multiple times in the hidden language groups. (10:32:25) thl: c4chris, well, then it would be good if that sig could handle that ;-) (10:32:32) scop: which is actually why I'd prefer someone who is interested and can keep things consistent and useful would maintain comps (10:32:48) c4chris: thl, k (10:32:58) thl: c4chris, thx (10:33:08) thl: well, was this all regarding this topic for today? (10:33:29) c4chris: thl, yup. I'll see about sending some nagmails... (10:33:43) thl: c4chris, tia (10:33:45) thl has changed the topic to: FESCO meeting in progress currently -- Activate legacy in buildroots (10:33:54) thl: well, we had the discussion on the list (10:34:21) thl: my vote: activate legacy in buildroots now, discuss the maintainer responsibilities later (10:34:22) mspevack is now known as mspevack_afk (10:34:38) dgilmore: +1 (10:34:43) thl: building FE3 and FE4 without legacy is ridiculous (10:34:51) warren: +1 (10:35:00) tibbs: +1 (10:35:01) c4chris: +1 (10:35:09) rdieter: +1 (10:35:09) thl: abadger1999 ? (10:35:18) abadger1999: Yeah, why not? +1 (10:35:35) bpepple: +1 (10:35:38) thl: k, settled (10:35:43) dgilmore: Ill get the mock config changes done, and make sure we sync up the legacy tree (10:35:51) thl: dgilmore, tia (10:36:01) thl has changed the topic to: FESCO meeting in progress currently -- CTRL-C problem (10:36:05) thl: any news? (10:36:08) scop: hold on a bit (10:36:10) abadger1999: tibbs, Are you still going to send out a maintainer resp. email? (10:36:17) thl has changed the topic to: FESCO meeting in progress currently -- Activate legacy in buildroots (10:36:19) thl: scop, ? (10:36:38) scop: it should be also documented somewhere that use of "EOL" FE branches assumess FL is in use too (10:36:40) tibbs: I lost some work in the wiki crash, unfortunately. (10:37:03) thl: scop, agreed (10:37:04) tibbs: I've been trying to feel out where the community is on FE3-4 maintenance. (10:37:13) thl: dgilmore, can you look after that, too? (10:37:42) thl: http://www.fedoraproject.org/wiki/Extras/UsingExtras is the proper place afaics (10:38:05) scop: indeed (10:38:06) warren: What ever happened with the security SIG? The top priority of a security team would be to track issues and file tickets if new issues appear. Has that began? (10:38:18) abadger1999: tibbs: :-( (10:38:18) scop: yes (10:38:20) bpepple: warren: Yeah. (10:38:22) abadger1999: warren: Yes. (10:38:24) thl: warren, that's working afaics (10:38:26) warren: good =) (10:38:28) tibbs: That's been ongoing for some time. (10:38:55) thl: scop, well, I'll put in on http://www.fedoraproject.org/wiki/Extras/UsingExtras if no one else wants (10:39:00) thl: so, let's move on (10:39:04) thl has changed the topic to: FESCO meeting in progress currently -- CTRL-C problem (10:39:19) thl: any news? sopwith still traveling afaik (10:39:22) thl: so probably no (10:39:31) ***thl will skip this one in 20 seconds (10:39:34) warren: Same thought as last week (10:39:46) warren: only way to really fix this is to make CVS commit mail async (10:39:50) warren: do we want to do this? (10:40:12) thl: warren, are there ans disadvantages (10:40:30) thl: s/ans/any/ (10:40:50) scop: yes, someone has to do the work :) (10:41:11) warren: I'll bring it up at the infrastructure meeting today (10:41:21) warren: I don't know how easy it would be (10:41:28) thl: scop, hehe, the usual problem ;-) (10:41:35) thl: warren, tia (10:41:40) scop: and actually, it can be somewhat difficult (10:41:40) thl: k, moving on (10:41:41) warren: tia means? (10:41:46) scop: warren, TIA (10:41:50) warren: ? (10:41:55) scop: Thanks In Advance (10:41:58) warren: oh (10:41:59) thl: thx in advance (10:41:59) warren: ok (10:42:12) thl has changed the topic to: FESCO meeting in progress currently -- Packaging Committee Report (10:42:14) thl: ? (10:42:42) abadger1999: I think the only thing that passed today was changing how .pyos are handled. (10:42:56) abadger1999: They are to be included instead of ghosted. (10:43:16) thl: abadger1999, we probably should run a script over a devel checkout of extras and file bugs (10:43:24) thl: otherwise stuff will never get fixed... (10:43:34) thl: maybe another job for the QA sig? (10:43:37) abadger1999: That's a good idea. (10:43:47) bpepple: Yeah, there should be a lot of python packages this affects. (10:43:54) c4chris: thl, gotcha (10:43:56) thl: or any other volunteers (10:43:59) thl: ? (10:44:08) thl: c4chris, sorry ;-) (10:44:16) c4chris: np (10:44:27) scop: related python spec template changes: http://koti.welho.com/vskytta/pyspec.patch (10:44:54) thl: abadger1999, c4chris, can you look after such a script please? (10:45:02) rdieter: it was/is-going to be mentioned on fedora-maintainers too... (10:45:12) scop: grep -lF '%ghost' */devel/*.spec (10:45:23) c4chris: thl, yup, we'll cook something up (10:45:32) thl: scop, + "| file _bugs.sh" (10:45:36) thl: c4chris, tia (10:45:49) abadger1999: thl: Will do. (10:45:49) thl: k, moving on (10:45:58) thl has changed the topic to: FESCO meeting in progress currently -- Sponsorship nominations (10:46:04) thl: any new nominations? (10:46:29) c4chris: not that I know of (10:46:32) dgilmore: thl: yeah ill look after it also (10:46:33) ***bpepple listens to the crickets. (10:46:35) rdieter: Well, it feels dirty, but I'd like to nominate me. (10:46:56) c4chris: rdieter, self nominations are fine (10:46:57) rdieter: (wanted to sponsor someone the other day, and realized I couldn't... yet) (10:47:21) ***thl wonders why rdieter isn't a sponsor yet (10:47:26) warren: +1 rdieter (10:47:27) thl: well, that's probably easy (10:47:32) bpepple: +1 (10:47:33) abadger1999: +1 (10:47:34) c4chris: +1 (10:47:35) thl: I think we don#t need to discus this (10:47:36) scop: huh? -1 (10:47:39) thl: rdieter sponsor +1 (10:47:39) dgilmore: +1 for rdieter (10:47:41) scop: OOPS +1 (10:47:51) thl: k, rdieter accepted (10:48:03) thl has changed the topic to: FESCO meeting in progress currently -- approve kmod's (10:48:03) rdieter: thanks, no I have no excuse for more work.. (: (10:48:04) tibbs: +1 (10:48:08) tibbs: (slow) (10:48:16) ***warren upgrades rdieter (10:48:21) thl: no new kmods up for discussion, moving on (10:48:35) thl has changed the topic to: FESCO meeting in progress currently -- MISC (10:48:53) thl: dgilmore, FE3 and FE4 builders are working fine now (python and elf-utils?) (10:48:57) thl: ? (10:49:01) dgilmore: thl: yep all donr (10:49:02) c4chris: crap, the package database item has been eaten by the wiki crash... (10:49:04) dgilmore: done (10:49:19) thl: dgilmore, thx (10:49:24) warren: BTW, are all FESCO members on fedora-maintainers and fedora-advisory-board? (10:49:29) thl: c4chris, uhhps, yes, sorry (10:49:55) rdieter: -maintainers, probably, fab maybe not (but probably should) 9: (10:49:57) dgilmore: warren: should be though i know us new FESCO guys were only just added to fab (10:50:04) tibbs: warren: My mailbox is certainly bulging from the latter list, yes. (10:50:10) bpepple: warren: I'm on both. (10:50:13) c4chris: warren, I am (10:50:13) thl: all FESCo members should be on FAB now (10:50:16) tibbs: Someone went through and added us. (10:50:22) thl: I checked the subscribers last week (10:50:26) rdieter: good. (10:50:35) dgilmore: fab is high volume :) (10:50:42) warren: As developement leaders in Fedora, your opinions would be valued in many matters of importance discussed on fab. (10:50:55) thl has changed the topic to: FESCO meeting in progress currently -- Future FESCo elections (10:51:29) thl: abadger1999, we wait a bit more for replys to your mail before we proceed? (10:51:29) abadger1999: I posted the draft. Anyone want to propose changes? (10:51:34) dgilmore: warren: i gave a longish reply last night about how i went about doing aurora extras (10:51:52) ***warren reads that mail... (10:51:54) dgilmore: abadger1999: looked pretty sane to me (10:51:58) c4chris: abadger1999, I like the draft (10:52:01) warren: rdieter, upgraded (10:52:21) ***thl votes for "wait another week before we accept the proposal" (10:52:38) c4chris: thl, k (10:52:44) bpepple: thl: +1 (10:52:49) rdieter: thl: +1 (10:52:54) thl: k, so let's move on (10:52:55) abadger1999: thl: +1 (10:53:05) thl has changed the topic to: FESCO meeting in progress currently -- package database (10:53:46) thl: c4chris, warren ,do we want to discuss stuff regarding that topic today? (10:53:46) c4chris: I posted a couple brain-dumps kinda mails (10:54:10) c4chris: any word of advice at this time ? (10:54:23) warren: Keep dumping, next step is to collect and organize everything we want. (10:54:29) thl: c4chris, well, "simply do something until somebody yells" (10:54:44) c4chris: thl, k (10:54:57) thl: c4chris, sorry, but that#s often the only way to really get something done afaics (10:54:57) dgilmore: c4chris: Just that there is alot of things that it needs to support. We need to design it in a modular fashion so it can grow as we grow (10:55:17) mspevack_afk is now known as mspevack (10:55:25) c4chris: warren, k. I'll try to start the collect phase soon... (10:55:26) [splinux] left the room (quit: "Ex-Chat"). (10:55:33) warren: due to the large scope of package database, mailing lists and wiki are most appropriate and a best use of time. Only after we have the mess better organized into plans should we discuss it? (10:55:34) abadger1999: c4chris: Are you on infrastructure list? (10:55:43) thl: warren, +1 (10:55:59) dgilmore: warren: +1 (10:56:08) c4chris: abadger1999, not sure (10:56:11) abadger1999: warren: +1 (10:56:18) bpepple: warren: +1 (10:56:24) c4chris: abadger1999, is it open? (10:56:31) warren: c4chris, yes, to anyone (10:56:40) c4chris: I'll check (10:56:52) thl: k, so let's move on (10:56:57) c4chris: I think I'm on the buildsys list (or soemthing) (10:57:00) warren: https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list (10:57:03) thl has changed the topic to: FESCO meeting in progress currently -- free discussion around extras (10:57:10) thl: anything that we need to discuss? (10:57:11) j-rod: dgilmore: how are you setting -j32? (10:57:18) thl: or was that all for today? (10:57:34) dgilmore: j-rod: thats how many cpus are in the box so its being auto done (10:57:45) nirik: thl: any thoughts further on zaptel-kmod? (10:57:59) scop: this info should find a home somewhere: http://fedoraproject.org/wiki/PackagingDrafts/PackageEndOfLife (10:58:10) dgilmore: thl: I think thats all. Ive seen no further feedback on buildysys issues (10:58:43) thl: nirik, good idea (10:58:44) tibbs: scop: Yes, this is in FESCo's jurisdiction, it seems. (10:58:52) thl has changed the topic to: FESCO meeting in progress currently -- zaptel-kmod (10:58:58) scop: it's in the packaging namespace but is Extras only (at least for now) so that's not quite the correct place for it (10:59:16) thl: well, nirik started a discussion on fedora-devel (10:59:18) j-rod: dgilmore: ah, gotcha -- I was thinking it would be better to use slightly less, with the intention of filling the cpus with multiple simultaneous builds (10:59:25) cweyl: scop: maybe just move to Extras/PackageEndOfLife? (10:59:28) thl: but there was much that came out of it afaics (10:59:47) scop: cweyl, yeah, maybe (10:59:48) nirik: I guess I would say: should the kmod guidelines say "If the upstream has no plans to merge with the upstream kernel, the module is not acceptable for extras" ? (11:00:08) thl: nirik, well, IMHO yes (11:00:13) dgilmore: zaptel as much as i want it in. We need to do something to make sure that it gets upstream. So we should ask the community of someone is willing to do that (11:00:58) thl: dgilmore, sounds like a good idea, but I doubt we'll find someone (11:01:22) cweyl: wait, I've never really understood this. why should it matter if (for whatever, presumably legitimate reason) an upstream decides to not pursue having it merged into the kernel proper? (11:02:12) thl: c4chris, well, drivers belong in the kernel -- kmods are a solution to bridge the gap until they get merged into the kenrel, but no long term solution (11:02:26) thl: s/c4chris/cweyl/ (11:02:31) thl: cweyl, simply example: (11:02:46) thl: kmod-foo breaks after rebase to 2.6.18 (11:02:56) dgilmore: though dave jones comment that he wont provide support for kernels with any kind of external module means that we could have confused users if they file a bug and get in return WONTFIX becaue of the extras kmods (11:02:59) thl: but a new kmod-bar doesn#t build anymore on 2.6.17 (11:03:06) devrimgunduz left the room (quit: Remote closed the connection). (11:03:13) thl: people that need both kmod-foo and kmod-bar will have problems now (11:03:25) tibbs: I personally believe that the length of the solution is up to the maintainer of the Extras package. (11:03:47) cweyl: tibbs: +1 (11:03:49) tibbs: Any external module solution will have problems keeping in step with kernels. At that point it's up to the maintainer. (11:03:56) cweyl: thl: I think we're setting the bar too high (11:04:05) scop: cweyl++ (11:04:17) tibbs: I don't believe that acceptance into extras should be used as any kind of political leverage as I have seen some state before. (11:04:45) tibbs: The issue of bugs and their interaction with the main kernel is quite compelling, though. (11:04:46) thl: tibbs, that was the agreement we settled on before we worked on the kmod stuff at all (11:04:54) cweyl: it sounds like zaptel-kmod is well maintained, isn't going anywhere anytime soon, and isn't going into the mainstream kernel ever due to business reasons... why shouldn't we let a maintainer package it for people who want it? (11:05:04) thl: well (11:05:15) thl: I'll bring it up to fab for discussion (11:05:19) thl: that okay for everybody? (11:05:26) cweyl: wait -- why fap? (11:05:30) thl: FAB (11:05:33) tibbs: thl: I was not a party to that discussion. (11:05:33) abadger1999: To me we have to keep our kernel people happy. (11:05:34) cweyl: err, fab? isn't this just an extras? (11:05:34) thl: sorry, typo (11:05:46) thl: abadger1999, +1 (11:05:47) bpepple: abadger1999: +1 (11:05:47) cweyl: err, a FESCo decision? (11:06:05) tibbs: If the "agreement" is unchangeable then that would be unfortunate. (11:06:08) thl: cweyl, no, this IMHO is something that matter for fedora at a whole project (11:06:13) cweyl: hrm. (11:06:21) thl: tibbs, everything can be changed (11:06:25) ***dgilmore steps back, I want it in but i understand the reasons for not having it in (11:06:35) warren: thl, except Bush's mind. (11:06:45) tibbs: WTF? (11:06:45) thl: warren, :) (11:06:57) cweyl: well, think of it this way too: as a user, I choose to buy a nvidia card, knowing that I'll need a kmod for it. (11:07:07) cweyl: I know there are risks that go along with that, and I'm willing to take them. (11:07:21) c4chris: but when your kernel crash, you usually file a kernel bug... (11:07:30) warren: BTW, vaguely on this topic, there was interesting news yesterday. (11:07:34) cweyl: Same thing with people who want to use zaptek-kmod, or the iscsi module that was discussed a while back... (11:07:40) warren: AMD is planning on open sourcing some of the ATI driver stuff. (11:07:49) tibbs: warren: Link? (11:07:54) thl: warren, are they really planing it? (11:07:59) c4chris: cweyl, that's why we need to keep the kernel maintainers happy (11:08:00) ***warren finds URL (11:08:00) bpepple: warren: Yeah, that looks like it could be promising. (11:08:01) dgilmore: cweyl: not always. my company provides me a system (probably laptop) it needs a kmod and i dont support binary drivers. but i get no say in the purchasing decision (11:08:04) thl: I only heard rumors (11:08:30) ***nirik also only heard rumors. (11:08:31) cweyl: c4chris: I'm not saying we shouldn't :) (11:08:41) tibbs: I've only heard wishful thinking. (11:08:47) warren: http://www.infoworld.com/article/06/08/02/32OPcurve_1.html (11:08:49) nirik: warren: you talking about: http://www.infoworld.com/article/06/08/02/32OPcurve_1.html ? (11:08:58) nirik: yeah, I read that as a rumor. (11:08:59) thl: I consider that as rumors (11:09:12) c4chris: cweyl, that means we probably need FAB buying the idea too... (11:09:24) thl: I ascutally asked AMD and ATI guys for clarification already earlier today (11:09:27) warren: I think consulting FAB i sa good idea. (11:09:30) thl: no reply until now (11:09:38) warren: thl, not surprised (11:09:40) cweyl: dgilmore: right. but the point is I want to use h/w that requires a kmod, and my decision to do that doesn't impact anyone else (11:09:54) warren: Anyway, if this becomes true, it will put pressure on NVidia. (11:10:05) ***bpepple thinks it needs to go to FAB also. (11:10:07) cweyl: c4chris: it's not like kmods change their package, or globally affect all fedora users (11:10:09) thl: so, anything else that needs to be discussed? (11:10:18) ***thl will close the meeting in 60 seconds (11:10:24) dgilmore: cweyl: yes and no. its not always my decsion but yes i want my hareware to work (11:10:45) warren: I think we're actually slowly winning the proprietary kernel module war (11:10:55) warren: Intel is leading the way, and hopefully AMD comes next (11:11:00) ***thl will close the meeting in 30 seconds (11:11:11) abadger1999: Approving this? http://fedoraproject.org/wiki/PackagingDrafts/PackageEndOfLife (11:11:21) warren: Our only way to promote further growth is to maintain our hard line stance. (11:11:46) warren: SuSe and Ubuntu both switched away from proprietary modules to a hard line stance. (11:11:50) warren: we're doing the right thing (11:11:58) thl: abadger1999, well, if that something FESCo should approve (11:11:58) warren: it will be painful meanwhile though... (11:12:08) thl: why is it in the Packaging namespace then? (11:12:28) thl: abadger1999, but well, get's a +1 from me (11:12:32) c4chris: abadger1999, looks fine to me (11:12:52) scop: I suggested to put it in the packaging namespace, but others corrected me (11:13:07) abadger1999: thl: scop proposed it in packaging this morning but it seems much more like a FESCo thing. (11:13:17) thl: abadger1999, well, never mind (11:13:26) thl: abadger1999, it actually describes what we do already (11:13:29) thl: so +1 (11:13:35) c4chris: +1 (11:13:36) abadger1999: +1 (11:13:37) rdieter: +1 (11:13:38) bpepple: +1 (11:13:57) tibbs: +1 (11:14:00) thl: k, settled (11:14:16) thl: abadger1999, can you moe it over to a proper place in the wiki please? (11:14:23) ***thl will close the meeting in 30 (11:14:32) abadger1999: will do. (11:14:33) thl: s/moe/move/ (11:14:40) ***thl will close the meeting in 10 (11:14:50) thl: -- MARK -- Meeting end (11:14:55) thl: thx everybody! (11:15:05) tibbs: thl: Thanks. (11:15:11) c4chris: thl, thx (11:15:31) thl has changed the topic to: This is the Fedora Extras channel, home of the FESCo meetings and general Extras discussion. | http://fedoraproject.org/wiki/Extras | Next FESCo Meeting: 2006-08-17 1700 UTC (11:15:43) ***c4chris goes afk: time fer dinner :-) (11:16:10) thl: are you guys still satisfied with the way I run the meetings? (11:16:19) thl: or is there anything we should change? (11:16:33) tibbs: I'm not sure it could be done much better. (11:16:45) scop: thl, absolutely no problem with that (11:16:49) thl: I know I'm a bit hectic now and then (11:16:55) scop: I think the agenda is a bit swollen, though (11:17:01) dgilmore: thl: i think your doinga great job (11:17:21) thl: scop, you mean the wiki (11:17:28) dgilmore: thl: something you may need to step up and say hey were done on this now move on (11:17:40) thl: well, I wanted a better overview for those that missed a meeting or two (11:18:05) scop: thl, no, but I think there are maybe a bit too many things to process per meeting (11:18:39) thl: scop, yes (11:18:52) thl: maybe we should do more via mail (11:19:09) thl: e.g. the reports from the packaging committee maybe (11:19:33) scop: that would work for me (11:19:34) thl: maybe the owners of task should update the wiki pages with a status update *before* the meeting (11:19:51) abadger1999: thl: Both of those would be good ideas. (11:19:52) thl: we could avoid the "status update" questions then (11:20:05) scop: and sponsor stuff could be taken entirely to the list (11:20:09) Rathann: Nodoid: wow, you really did it, #202004 (11:21:08) thl: I'll think about it a bit more (11:21:37) thl: abadger1999, scop, but we need to make sure that we discuss important things from the packaging committee meetings here (11:21:50) scop: good point (11:21:51) thl: the less important things could be done on the list (11:22:11) abadger1999: If it needs to be discussed here then the report needs to be done here. (11:22:22) abadger1999: Or the wekly packaging meeting could be changed. (11:22:27) bpepple: scop: +1 (11:22:58) thl: abadger1999, changeing thepackaging meetings could help (11:23:51) thl: btw, regading sponsor discussions (11:23:59) thl: do we want to do that on cvs-sponsors (11:24:02) thl: or fesco only (11:24:11) ***thl votes for cvs-sponsors (11:24:38) ***bpepple votes for fesco. Could give more frank discussions. (11:24:48) abadger1999: I'll add meeting time to the packaging agenda. (11:25:44) thl: bpepple, but we are getting quite big, so it might more and more often happen that FESCo members don#t know those that were nominated for the sponsor job (11:26:23) bpepple: thl: It's pretty easy to query bugzilla for the reviews. (11:26:48) thl: well, let's discuss this on the list or in the next meeting (11:26:56) bpepple: no problem. (11:27:21) tibbs: c4chris did add bugzilla links to the "top reviewers" table in PackageStatus. (11:27:36) thl: bpepple, the past discussions we had on cvs-sponsors were quite frank iirc (11:27:45) tibbs: That list currently covers twelve reviews and up. (11:28:58) bpepple: yeah, but I'm afraid some of the discussions might discourage the participants enthusiasm, if there not comfortable with criticisms. (11:29:37) scop left the room ("Leaving"). (11:31:29) thl: bpepple, maybe we should do it on both lists? (11:32:00) bpepple: That might be a good idea. (11:34:20) cweyl: if there are criticisms, and they're discussed privately, might I suggest that it's a good idea to offer those criticisms, packaged constructively, to the nominee? That way they know what prevented them from being approved, and what they need to fix (11:34:20) thl: c4chris, /Extras/Schedule/PackageDatabase in place again (11:34:42) thl: cweyl, yeah, that's what I thought already, too (11:35:12) cweyl: and doing that publicly would give others guidance, establish precedent, etc, etc (11:35:30) cweyl: thl: I suspect I'm just stating the obvious here, but someone had to do it :) (11:35:45) dgilmore: thl: whats cvs-sponsers (11:36:26) bpepple: cweyl: Agreed, that was what I was thinking. (11:37:21) thl: dgilmore, a mailing-list where all sponsors are subscribed (it#s actually an alias or something else and no proper mailinglist) (11:38:00) dgilmore: thl: ok well i think its bad to discusss there because some fesco members are not in on that. (11:38:04) nirik: yeah, it's an alias... which unfortunately causes SPF issues. ;( (11:38:28) dgilmore: thl: namely me and im sure others (11:38:40) cweyl: nirik: cvs-sponsors causes skin cancer? (11:38:41) thl: dgilmore, well, we probably really should discuss on both lists (11:39:02) dgilmore: and I know i really dont have the time to dedicate to being a sponsor (11:39:37) nirik: cweyl: Sender Policy Framework... skin cancer might be easier to treat sometimes. ;( (11:40:00) cweyl: nirik: gotcha :) (11:40:36) dgilmore: nirik: people using SPF should add redhat /fedora mailservers to their dns (11:40:39) thl: dgilmore, np, I also don't find enough time to review and sponsor (11:40:49) thl: dgilmore, that's sad and I don#t like it (11:41:15) thl: but that's how it is ATM... :-/ (11:42:10) dgilmore: thl: yeaqh it is. Between Security and Infrastructure and my sparc port of extras, FESCO and maintaining my own packages I review when i can but I dont want to do a half assed job of something (11:42:50) thl: I actually even tried to get rid of a lot of packages in Extras (11:43:05) thl: to have more time for other stuff (11:43:13) dgilmore: I dont have a huge amount of packages. (11:43:36) dgilmore: I try to commit myself to things where i feel ill have a positive effect on something }}} -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From andreas at bawue.net Sun Aug 13 20:26:22 2006 From: andreas at bawue.net (Andreas Thienemann) Date: Sun, 13 Aug 2006 22:26:22 +0200 (CEST) Subject: Anyone want pyzor? In-Reply-To: <44DF8537.4050802@redhat.com> References: <44DB6809.201@redhat.com> <29348.203.118.135.21.1155240571.squirrel@www.knox.net.nz> <44DF8537.4050802@redhat.com> Message-ID: On Sun, 13 Aug 2006, Warren Togami wrote: > How about this, assign primary ownership to Andreas and you can coordinate on > joint ownership. I trust that most of the cvsextras members would do the > right thing. sounds okay to me. I haven't fiddled yet with joint ownership, but no problem there. There's a first time for everything. Michael, you okay with that? regards, andreas From Jochen at herr-schmitt.de Sun Aug 13 20:58:30 2006 From: Jochen at herr-schmitt.de (Jochen Schmitt) Date: Sun, 13 Aug 2006 22:58:30 +0200 Subject: .Q: Best Practice for dir owneership Message-ID: <0MKwh2-1GCN2Y07lX-0004ZF@mrelayeu.kundenserver.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hello, I have a special problem with a package which I have submitted for review at BZ #174021. This package contains two subpackages with fonts. the first subpackage conatins trutype fonts which should installed at %{_datadir}/fonts/apl/TrueType. The second conains classic X11 bitmap fonts which shluld installed on %{_datadir}/fonts/apl/pcf. In comment #28 there was a suggestion to put the X11 fonts to %{_datadir}/X11/fonts/apl but I think only the core fonts on the X11 system should put into %{_datadir}/X11/fonts, so I want to keep the X11 fonts into %{_datadir}/fonts/apl/pcf. Now there is the direcotry %{_datadir]/fonts/apl which is not owned by any package. My question now, what is the best practice to solve this problem. Best Regards: Jochen Schmitt -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.0.2 (Build 2424) iQA/AwUBRN+Sfk9gByurcX4MEQIEkgCg/5C/I0WTGhucCKPCNkf/1niEaOMAn0Mp OVnm30D0peWaz6mj+0UhwitT =egsy -----END PGP SIGNATURE----- From j.w.r.degoede at hhs.nl Sun Aug 13 21:29:56 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Sun, 13 Aug 2006 23:29:56 +0200 Subject: Need a list of educational packages In-Reply-To: <200608140023.42193.kushaldas@gmail.com> References: <200608140023.42193.kushaldas@gmail.com> Message-ID: <44DF99D4.80008@hhs.nl> Kushal Das wrote: > Hi, > > I am making a offline tool to install stuffs from fedora extras & livna. I > want to include different educational/development tools available in the > extras repo, which can help the school/engg. students. For that I need a list > of packages. > Can anyone send me the names.. > I maintain 2 big educational packages: gcompris childsplay Notice that gcompris has many seperate installable langpacks and that childsplay can use the gcompris langpacks too. Also we have the venerable tuxpaint, and probably others. Regards, Hans From paul at all-the-johnsons.co.uk Sun Aug 13 21:41:12 2006 From: paul at all-the-johnsons.co.uk (Paul) Date: Sun, 13 Aug 2006 22:41:12 +0100 Subject: Need a list of educational packages In-Reply-To: <44DF99D4.80008@hhs.nl> References: <200608140023.42193.kushaldas@gmail.com> <44DF99D4.80008@hhs.nl> Message-ID: <1155505272.8903.35.camel@T7.Linux> Hi, > Also we have the venerable tuxpaint, and probably others. genchemlab is in extras and I'm hoping to get MOPAC and ORTEP in at some point soon (though for some reason, ORTEP is being a sod and it's a single f77 file!) TTFN Paul -- Wenn sie denken, dass die bildung teuer ist, versuchen sie ignoranz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From mpugazh at gmail.com Mon Aug 14 01:31:25 2006 From: mpugazh at gmail.com (pugazhendhi muthuraman) Date: Mon, 14 Aug 2006 07:01:25 +0530 Subject: Need a list of educational packages In-Reply-To: <1155505272.8903.35.camel@T7.Linux> References: <200608140023.42193.kushaldas@gmail.com> <44DF99D4.80008@hhs.nl> <1155505272.8903.35.camel@T7.Linux> Message-ID: <3a15d92b0608131831w1a2892d9uc98f43e7e7b1b40c@mail.gmail.com> Hi All, Can you kindly include Jiletters also. The other i feel must is abacus,Super tux.As of now let me compile the names of other software also.I am concentrating more on kids software more.I will reply with the list in a day. Thanks and regards Pugazhendhi Muthuraman On 8/14/06, Paul wrote: > > Hi, > > > Also we have the venerable tuxpaint, and probably others. > > genchemlab is in extras and I'm hoping to get MOPAC and ORTEP in at some > point soon (though for some reason, ORTEP is being a sod and it's a > single f77 file!) > > TTFN > > Paul > -- > Wenn sie denken, dass die bildung teuer ist, versuchen sie ignoranz > > > > -- > fedora-extras-list mailing list > fedora-extras-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-extras-list > > > > -- Thanks and regards, Pugazhendhi,M -------------- next part -------------- An HTML attachment was scrubbed... URL: From jkeating at redhat.com Mon Aug 14 02:23:17 2006 From: jkeating at redhat.com (Jesse Keating) Date: Sun, 13 Aug 2006 22:23:17 -0400 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-12 In-Reply-To: <20060812121609.7931.24562@extras64.linux.duke.edu> References: <20060812121609.7931.24562@extras64.linux.duke.edu> Message-ID: <200608132223.17919.jkeating@redhat.com> On Saturday 12 August 2006 08:16, Fedora Extras repoclosure wrote: > ? ? jkeating AT redhat.com > ? ? ? ? contacts - 0.1-1.i386 ? ?(5 days) > ? ? ? ? contacts - 0.1-1.ppc ? ?(5 days) > ? ? ? ? contacts - 0.1-1.x86_64 ? ?(5 days) This should be fixed with the next push. An SVN snapshot was needed to build against the new evo-data-server. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From wolters.liste at gmx.net Mon Aug 14 04:05:03 2006 From: wolters.liste at gmx.net (Roland Wolters) Date: Mon, 14 Aug 2006 06:05:03 +0200 Subject: Problems with tagging Message-ID: <200608140605.55884.wolters.liste@gmx.net> Hi, due to a missing build require I was forced to update the spec file - I did so, but run into errors when I tried to tag again (as mentioned in http://www.fedoraproject.org/wiki/Extras/UsingCvsFaq). I thought it was due to the fact that I did not changed the minor number in the package, but after I did so the re-tagging failed again: $ make tag build cvs tag -c ktorrent-2_0-2_fc6 For more information on using the Fedora source code repositories, please visit http://fedoraproject.org/wiki/UsingCvs ? i386 ? ktorrent-2.0 ? ktorrent-2.0-2.src.rpm ERROR: creating module-wide tags is prohibited cvs tag: Pre-tag check failed ERROR: The tag ktorrent-2_0-2_fc6 is already applied on a different branch ERROR: You can not forcibly move tags between branches ktorrent-1_2-4:devel:liquidat:1150854425 ktorrent-1_2-4_fc6:devel:liquidat:1150920337 ktorrent-1_2-4_fc5:FC-5:liquidat:1150920347 ktorrent-2_0-1:devel:liquidat:1155525600 ktorrent-2_0-1_fc6:devel:liquidat:1155525752 ktorrent-2_0-2_fc6:devel:liquidat:1155527830 cvs tag: Pre-tag check failed ERROR: Tag ktorrent-2_0-2_fc6 has been already created. The following tags have been created so far ktorrent-1_2-4:devel:liquidat:1150854425 ktorrent-1_2-4_fc6:devel:liquidat:1150920337 ktorrent-1_2-4_fc5:FC-5:liquidat:1150920347 ktorrent-2_0-1:devel:liquidat:1155525600 ktorrent-2_0-1_fc6:devel:liquidat:1155525752 ktorrent-2_0-2_fc6:devel:liquidat:1155527830 cvs tag: Pre-tag check failed I thought about deleting the newest tag, but that's not allowed. It already looks like a mess, so before I screw it up even more: What should I do now? Roland -- "Ein Pr?sident ist wie ein Friedhofsverwalter. Er hat eine Menge Leute unter sich, aber keiner h?rt zu." -- Bill Clinton -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From j.w.r.degoede at hhs.nl Mon Aug 14 07:58:59 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Mon, 14 Aug 2006 09:58:59 +0200 Subject: Need a list of educational packages In-Reply-To: <3a15d92b0608131831w1a2892d9uc98f43e7e7b1b40c@mail.gmail.com> References: <200608140023.42193.kushaldas@gmail.com> <44DF99D4.80008@hhs.nl> <1155505272.8903.35.camel@T7.Linux> <3a15d92b0608131831w1a2892d9uc98f43e7e7b1b40c@mail.gmail.com> Message-ID: <44E02D43.4060701@hhs.nl> pugazhendhi muthuraman wrote: > Hi All, > > Can you kindly include Jiletters also. > The other i feel must is abacus,Super tux.As of now let me compile the > names > of other software also.I am concentrating more on kids software more.I will > reply with the list in a day. > Thanks and regards > Pugazhendhi Muthuraman > We really should maintain a list of these somewhere, and as already mentioned in this thread, the proper place is in comps-feX.xml.in the "Educational Software" group. So all mentioned packages really should be added there (and removed elsewhere from comps if they are elsewhere, because packages should not be listed twice). Regards, Hans From sundaram at fedoraproject.org Mon Aug 14 07:56:44 2006 From: sundaram at fedoraproject.org (Rahul) Date: Mon, 14 Aug 2006 13:26:44 +0530 Subject: Need a list of educational packages In-Reply-To: <44E02D43.4060701@hhs.nl> References: <200608140023.42193.kushaldas@gmail.com> <44DF99D4.80008@hhs.nl> <1155505272.8903.35.camel@T7.Linux> <3a15d92b0608131831w1a2892d9uc98f43e7e7b1b40c@mail.gmail.com> <44E02D43.4060701@hhs.nl> Message-ID: <44E02CBC.5030008@fedoraproject.org> Hans de Goede wrote: > > We really should maintain a list of these somewhere, and as already > mentioned in this thread, the proper place is in comps-feX.xml.in > the "Educational Software" group. > > So all mentioned packages really should be added there (and removed > elsewhere from comps if they are elsewhere, because packages should not > be listed twice). > This work is best done by a SIG. I was quite surprised to see that we didnt have a Education SIG yet when Kushal asked me for a list of packages in IRC earlier. Rahul From bugs.michael at gmx.net Mon Aug 14 08:25:40 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Mon, 14 Aug 2006 10:25:40 +0200 Subject: Problems with tagging In-Reply-To: <200608140605.55884.wolters.liste@gmx.net> References: <200608140605.55884.wolters.liste@gmx.net> Message-ID: <20060814102540.57fe6afe.bugs.michael@gmx.net> On Mon, 14 Aug 2006 06:05:03 +0200, Roland Wolters wrote: > Hi, > > due to a missing build require I was forced to update the spec file - I did > so, but run into errors when I tried to tag again (as mentioned in > http://www.fedoraproject.org/wiki/Extras/UsingCvsFaq). I thought it was due > to the fact that I did not changed the minor number in the package, but after > I did so the re-tagging failed again: > > $ make tag build > cvs tag -c ktorrent-2_0-2_fc6 > I thought about deleting the newest tag, but that's not allowed. > > It already looks like a mess, so before I screw it up even more: What should I > do now? Simply bump "Release", commit, and run "make tag" again. From paul at all-the-johnsons.co.uk Mon Aug 14 08:38:19 2006 From: paul at all-the-johnsons.co.uk (PFJ) Date: Mon, 14 Aug 2006 09:38:19 +0100 Subject: Need a list of educational packages In-Reply-To: <44E02CBC.5030008@fedoraproject.org> References: <200608140023.42193.kushaldas@gmail.com> <44DF99D4.80008@hhs.nl> <1155505272.8903.35.camel@T7.Linux> <3a15d92b0608131831w1a2892d9uc98f43e7e7b1b40c@mail.gmail.com> <44E02D43.4060701@hhs.nl> <44E02CBC.5030008@fedoraproject.org> Message-ID: <1155544699.2911.0.camel@localhost.localdomain> Hi, > > So all mentioned packages really should be added there (and removed > > elsewhere from comps if they are elsewhere, because packages should not > > be listed twice). > > > > This work is best done by a SIG. I was quite surprised to see that we > didnt have a Education SIG yet when Kushal asked me for a list of > packages in IRC earlier. An education SIG would be a cracking idea, plus a new group in the RPM group of Applications/Education would help. TTFN Paul -- "Logic, my dear Zoe, is merely the ability to be wrong with authority" - Dr Who From Christian.Iseli at licr.org Mon Aug 14 09:08:01 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Mon, 14 Aug 2006 11:08:01 +0200 Subject: Need a list of educational packages In-Reply-To: <1155544699.2911.0.camel@localhost.localdomain> References: <200608140023.42193.kushaldas@gmail.com> <44DF99D4.80008@hhs.nl> <1155505272.8903.35.camel@T7.Linux> <3a15d92b0608131831w1a2892d9uc98f43e7e7b1b40c@mail.gmail.com> <44E02D43.4060701@hhs.nl> <44E02CBC.5030008@fedoraproject.org> <1155544699.2911.0.camel@localhost.localdomain> Message-ID: <20060814110801.0735961c@ludwig-alpha> On Mon, 14 Aug 2006 09:38:19 +0100, PFJ wrote: > plus a new group in the RPM > group of Applications/Education would help. Probably won't happen. Please only concentrate on getting a good comps-feX.xml.in Christian From j.w.r.degoede at hhs.nl Mon Aug 14 10:00:07 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Mon, 14 Aug 2006 12:00:07 +0200 Subject: Need a list of educational packages In-Reply-To: <1155544699.2911.0.camel@localhost.localdomain> References: <200608140023.42193.kushaldas@gmail.com> <44DF99D4.80008@hhs.nl> <1155505272.8903.35.camel@T7.Linux> <3a15d92b0608131831w1a2892d9uc98f43e7e7b1b40c@mail.gmail.com> <44E02D43.4060701@hhs.nl> <44E02CBC.5030008@fedoraproject.org> <1155544699.2911.0.camel@localhost.localdomain> Message-ID: <44E049A7.4080300@hhs.nl> PFJ wrote: > Hi, >>> So all mentioned packages really should be added there (and removed >>> elsewhere from comps if they are elsewhere, because packages should not >>> be listed twice). >>> >> This work is best done by a SIG. I was quite surprised to see that we >> didnt have a Education SIG yet when Kushal asked me for a list of >> packages in IRC earlier. > > An education SIG would be a cracking idea, plus a new group in the RPM > group of Applications/Education would help. > Well I'm interested in educational software, but I've been currently doing this under the gaming SIG umbrella, I know that is a bit of the mark but sofar it works. Regards, Hans From sundaram at fedoraproject.org Mon Aug 14 10:13:20 2006 From: sundaram at fedoraproject.org (Rahul) Date: Mon, 14 Aug 2006 15:43:20 +0530 Subject: Need a list of educational packages In-Reply-To: <44E049A7.4080300@hhs.nl> References: <200608140023.42193.kushaldas@gmail.com> <44DF99D4.80008@hhs.nl> <1155505272.8903.35.camel@T7.Linux> <3a15d92b0608131831w1a2892d9uc98f43e7e7b1b40c@mail.gmail.com> <44E02D43.4060701@hhs.nl> <44E02CBC.5030008@fedoraproject.org> <1155544699.2911.0.camel@localhost.localdomain> <44E049A7.4080300@hhs.nl> Message-ID: <44E04CC0.90702@fedoraproject.org> Hans de Goede wrote: > > PFJ wrote: >> Hi, >>>> So all mentioned packages really should be added there (and removed >>>> elsewhere from comps if they are elsewhere, because packages should not >>>> be listed twice). >>>> >>> This work is best done by a SIG. I was quite surprised to see that we >>> didnt have a Education SIG yet when Kushal asked me for a list of >>> packages in IRC earlier. >> An education SIG would be a cracking idea, plus a new group in the RPM >> group of Applications/Education would help. >> > > Well I'm interested in educational software, but I've been currently > doing this under the gaming SIG umbrella, I know that is a bit of the > mark but sofar it works. > There are some games which play a education role and there are tools which provide entertainment while learning broadly classified under "Edutainment" however there are several other additional ones like for example touch typing that would fit into a education SIG but not often into a games SIG. It would be much better to have separate SIG's since it makes the role of these groups easier to identify and participate in. Rahul From kushaldas at gmail.com Mon Aug 14 10:16:49 2006 From: kushaldas at gmail.com (Kushal Das) Date: Mon, 14 Aug 2006 15:46:49 +0530 Subject: Need a list of educational packages In-Reply-To: <44E02CBC.5030008@fedoraproject.org> References: <200608140023.42193.kushaldas@gmail.com> <44DF99D4.80008@hhs.nl> <1155505272.8903.35.camel@T7.Linux> <3a15d92b0608131831w1a2892d9uc98f43e7e7b1b40c@mail.gmail.com> <44E02D43.4060701@hhs.nl> <44E02CBC.5030008@fedoraproject.org> Message-ID: On 8/14/06, Rahul wrote: > > This work is best done by a SIG. I was quite surprised to see that we > didnt have a Education SIG yet when Kushal asked me for a list of > packages in IRC earlier. > > Rahul > Education SIG will be a very good idea. In the different engineering colleges I saw mostly(more than 95 %) are based on Fedora only :) If an Education SIG starts up, it will be pretty easier to maintain educational packages. Regards, Kushal From j.w.r.degoede at hhs.nl Mon Aug 14 10:31:23 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Mon, 14 Aug 2006 12:31:23 +0200 Subject: Need a list of educational packages In-Reply-To: References: <200608140023.42193.kushaldas@gmail.com> <44DF99D4.80008@hhs.nl> <1155505272.8903.35.camel@T7.Linux> <3a15d92b0608131831w1a2892d9uc98f43e7e7b1b40c@mail.gmail.com> <44E02D43.4060701@hhs.nl> <44E02CBC.5030008@fedoraproject.org> Message-ID: <44E050FB.2010505@hhs.nl> Kushal Das wrote: > On 8/14/06, Rahul wrote: >> >> This work is best done by a SIG. I was quite surprised to see that we >> didnt have a Education SIG yet when Kushal asked me for a list of >> packages in IRC earlier. >> >> Rahul >> > Education SIG will be a very good idea. In the different engineering > colleges I saw mostly(more than 95 %) are based on Fedora only :) > If an Education SIG starts up, it will be pretty easier to maintain > educational packages. > Well I'm game, but I won't be taking the lead. For starters someone should start writing a wiki page for the SIG with a clear definitions of the SIGs goals, see the Games SIGs wiki page as an example. Besides that we need a way (wiki page works well for the games sig) to maintain a list of: 1) interesting software to package 2) educational packages waiting for review And we might encounter some packaging issues which turn out to be a common theme for educational software in which case we should discuss them, come up with a solution and document the found solution on the wiki page. Regards, Hans From j.w.r.degoede at hhs.nl Mon Aug 14 10:34:50 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Mon, 14 Aug 2006 12:34:50 +0200 Subject: Proper Source0 URL for sf.net hosted projects? Message-ID: <44E051CA.3030804@hhs.nl> Hi all, I was wondering what the correct Source0 URL for sourceforge.net hosted projects is? I've seen both: http://dl.sf.net// and: http://dl.sf.net/sourceforge// And they both seem to work, however I believe that the first form working is a matter of luck (hitting the right mirror) and the second form always works, is this correct? Maybe we should document this somewhere? Regards, Hans From paul at all-the-johnsons.co.uk Mon Aug 14 10:38:32 2006 From: paul at all-the-johnsons.co.uk (PFJ) Date: Mon, 14 Aug 2006 11:38:32 +0100 Subject: Proper Source0 URL for sf.net hosted projects? In-Reply-To: <44E051CA.3030804@hhs.nl> References: <44E051CA.3030804@hhs.nl> Message-ID: <1155551912.2911.58.camel@localhost.localdomain> Hi, > I was wondering what the correct Source0 URL for sourceforge.net hosted > projects is? > > I've seen both: > http://dl.sf.net// > and: > http://dl.sf.net/sourceforge// > > And they both seem to work, however I believe that the first form > working is a matter of luck (hitting the right mirror) and the second > form always works, is this correct? Yes - one points to the other. Personally, I always list the URL of a mirror (in my case, kent) as SF has been known to fall dead when it comes to redirecting or getting files directly from their own server. > Maybe we should document this somewhere? I'd actually say that the packager lists the mirror as the URL rather than sf.net TTFN Paul -- "Logic, my dear Zoe, is merely the ability to be wrong with authority" - Dr Who From j.w.r.degoede at hhs.nl Mon Aug 14 11:03:48 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Mon, 14 Aug 2006 13:03:48 +0200 Subject: Proper Source0 URL for sf.net hosted projects? In-Reply-To: <1155551912.2911.58.camel@localhost.localdomain> References: <44E051CA.3030804@hhs.nl> <1155551912.2911.58.camel@localhost.localdomain> Message-ID: <44E05894.9050909@hhs.nl> PFJ wrote: > Hi, > >> I was wondering what the correct Source0 URL for sourceforge.net hosted >> projects is? >> >> I've seen both: >> http://dl.sf.net// >> and: >> http://dl.sf.net/sourceforge// >> >> And they both seem to work, however I believe that the first form >> working is a matter of luck (hitting the right mirror) and the second >> form always works, is this correct? > > Yes - one points to the other. Personally, I always list the URL of a > mirror (in my case, kent) as SF has been known to fall dead when it > comes to redirecting or getting files directly from their own server. > I've done that in the past too, but sometimes mirrors go away, and not all mirrors carry all files all of the time (strange but true). >> Maybe we should document this somewhere? > > I'd actually say that the packager lists the mirror as the URL rather > than sf.net > Because of the reasons given above I disagree :) Still I think a common rule, or atleast an advicable way of doing this for the whole of FE would be good. Regards, Hans From j.w.r.degoede at hhs.nl Mon Aug 14 13:14:31 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Mon, 14 Aug 2006 15:14:31 +0200 Subject: The bug squad is hiring! In-Reply-To: <44DF3505.3090309@fedoraproject.org> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> <44DD6914.4080401@hhs.nl> <44DDACB3.6000509@fedoraproject.org> <44DEE087.4090708@hhs.nl> <44DF3505.3090309@fedoraproject.org> Message-ID: <44E07737.2070009@hhs.nl> Rahul wrote: > Hans de Goede wrote: >> >> Rahul wrote: >>> Hans de Goede wrote: >>>> Wiki maintainers, where should this page be (maybe under Extras/SIGs? >>>> But its not soley for Extras). >>>> >>> http://fedoraproject.org/wiki/BugZappers >>> >> >> Yes that might work, but that is a bit different that is about triaging >> bug, helping the bug owners to get better bug reports. Denis and mine >> effort is about helping bug owners by really fixing some (low hanging >> easy, great impact) bugs, thus do the debugging hunt it down to the line >> of code and create a patch. So similar but different. >> >> >> Should I just add a section to the above page for our effort / work? >> >> > > Yes. Fixing low hanging bugs is part of triaging IMO. > OKay, I'll add a part to the bugzappers wiki about this then, I also would like to maintain a page with a list of easy fixable bugs, or rather with 3 lists: 1) easy fixable and annoying / high impact 2) annoying / highimpact 3) easy fixable The idea is to have a short description of each bug and an URL, so that people who want to help with this can easily find a bug to work on. Can you create a wiki page (and give me and dennis edit rights) for this? Thanks, Hans From triad at df.lth.se Mon Aug 14 13:09:33 2006 From: triad at df.lth.se (Linus Walleij) Date: Mon, 14 Aug 2006 15:09:33 +0200 (CEST) Subject: Proper Source0 URL for sf.net hosted projects? In-Reply-To: <44E05894.9050909@hhs.nl> References: <44E051CA.3030804@hhs.nl> <1155551912.2911.58.camel@localhost.localdomain> <44E05894.9050909@hhs.nl> Message-ID: On Mon, 14 Aug 2006, Hans de Goede wrote: > I've done that in the past too, but sometimes mirrors go away, and not > all mirrors carry all files all of the time (strange but true). Strange or not but I've noticed this to be true for the Fedora Extras mirrors as well .. Linus From sundaram at fedoraproject.org Mon Aug 14 13:19:33 2006 From: sundaram at fedoraproject.org (Rahul) Date: Mon, 14 Aug 2006 18:49:33 +0530 Subject: The bug squad is hiring! In-Reply-To: <44E07737.2070009@hhs.nl> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> <44DD6914.4080401@hhs.nl> <44DDACB3.6000509@fedoraproject.org> <44DEE087.4090708@hhs.nl> <44DF3505.3090309@fedoraproject.org> <44E07737.2070009@hhs.nl> Message-ID: <44E07865.1050302@fedoraproject.org> Hans de Goede wrote: > I'll add a part to the bugzappers wiki about this then, I also would > like to maintain a page with a list of easy fixable bugs, or rather with > 3 lists: > 1) easy fixable and annoying / high impact > 2) annoying / highimpact > 3) easy fixable > > The idea is to have a short description of each bug and an URL, so that > people who want to help with this can easily find a bug to work on. Wouldnt it be better to use the bugzilla whiteboard for this and just link to the queries from the wiki page? You can talk to Will Woods if you need more information on doing this. He has also demonstrated some queries to show recent bugzilla activity and other details in #fedora-triage which are useful to tackle. Maintaining a list manually in the wiki is harder and inefficient. Can > you create a wiki page (and give me and dennis edit rights) for this? > Bugzapper pages are open to everyone in the edit group. Feel free to create any new pages you want. I generally want to avoid adding more ACL's to them. Just set watches on the pages you create. Rahul From wolters.liste at gmx.net Mon Aug 14 13:29:32 2006 From: wolters.liste at gmx.net (Roland Wolters) Date: Mon, 14 Aug 2006 15:29:32 +0200 Subject: Problems with tagging In-Reply-To: <20060814102540.57fe6afe.bugs.michael@gmx.net> References: <200608140605.55884.wolters.liste@gmx.net> <20060814102540.57fe6afe.bugs.michael@gmx.net> Message-ID: <200608141529.38862.wolters.liste@gmx.net> Once upon a time Michael Schwendt wrote: > On Mon, 14 Aug 2006 06:05:03 +0200, Roland Wolters wrote: > > > > $ make tag build > > cvs tag -c ktorrent-2_0-2_fc6 > > > > It already looks like a mess, so before I screw it up even more: What > > should I do now? > > Simply bump "Release", commit, and run "make tag" again. Thanks for the naswer, but unfortunately I do not get it - what do you mean with "bump"? Should I delete the "Release" line in the spec file of the devel branch? Roland -- Man gab uns einen Funken Idiotie, und im Verlauf vieler hunderttausend Jahre entfachten wir ein gro?es Feuer daraus. -- Terry Pratchett -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bugs.michael at gmx.net Mon Aug 14 13:39:40 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Mon, 14 Aug 2006 15:39:40 +0200 Subject: Problems with tagging In-Reply-To: <200608141529.38862.wolters.liste@gmx.net> References: <200608140605.55884.wolters.liste@gmx.net> <20060814102540.57fe6afe.bugs.michael@gmx.net> <200608141529.38862.wolters.liste@gmx.net> Message-ID: <20060814153940.c1aa4284.bugs.michael@gmx.net> On Mon, 14 Aug 2006 15:29:32 +0200, Roland Wolters wrote: > Once upon a time Michael Schwendt wrote: > > On Mon, 14 Aug 2006 06:05:03 +0200, Roland Wolters wrote: > > > > > > $ make tag build > > > cvs tag -c ktorrent-2_0-2_fc6 > > > > > > It already looks like a mess, so before I screw it up even more: What > > > should I do now? > > > > Simply bump "Release", commit, and run "make tag" again. > > Thanks for the naswer, but unfortunately I do not get it - what do you mean > with "bump"? Should I delete the "Release" line in the spec file of the devel > branch? No, _increase_ its value, commit, then run "make tag". From wolters.liste at gmx.net Mon Aug 14 13:49:19 2006 From: wolters.liste at gmx.net (Roland Wolters) Date: Mon, 14 Aug 2006 15:49:19 +0200 Subject: Problems with tagging In-Reply-To: <20060814153940.c1aa4284.bugs.michael@gmx.net> References: <200608140605.55884.wolters.liste@gmx.net> <200608141529.38862.wolters.liste@gmx.net> <20060814153940.c1aa4284.bugs.michael@gmx.net> Message-ID: <200608141549.25227.wolters.liste@gmx.net> Once upon a time Michael Schwendt wrote: > On Mon, 14 Aug 2006 15:29:32 +0200, Roland Wolters wrote: > > Once upon a time Michael Schwendt wrote: > > > On Mon, 14 Aug 2006 06:05:03 +0200, Roland Wolters wrote: > > > > $ make tag build > > > > cvs tag -c ktorrent-2_0-2_fc6 > > > > > > > > It already looks like a mess, so before I screw it up even more: What > > > > should I do now? > > > > > > Simply bump "Release", commit, and run "make tag" again. > > > > Thanks for the naswer, but unfortunately I do not get it - what do you > > mean with "bump"? Should I delete the "Release" line in the spec file of > > the devel branch? > > No, _increase_ its value, commit, then run "make tag". I tried, and it didn't work. The output is attached, it is everythign what I did after editing the local spec file in the devel directory. I wonder why it says that there already is a .3 release although I just edited the spec file to get a .3 release... Roland -- If you're not with us, you're against us. - If you're not an apple, you're a banana. -- Terry Pratchett -------------- next part -------------- $ cvs commit -m "Increase release value to 3" cvs commit: Examining . cvs commit: Examining ktorrent cvs commit: Examining ktorrent/FC-5 cvs commit: Examining ktorrent/common cvs commit: Examining ktorrent/devel For more information on using the Fedora source code repositories, please visit http://fedoraproject.org/wiki/UsingCvs ? ktorrent-2.0-2.src.rpm ? ktorrent-2.0 ? i386 **** Access allowed: liquidat is in ACL for rpms/ktorrent/devel. Checking in ktorrent.spec; /cvs/extras/rpms/ktorrent/devel/ktorrent.spec,v <-- ktorrent.spec new revision: 1.5; previous revision: 1.4 done Running syncmail... Mailing cvsextras at fedora.redhat.com... ...syncmail done. Running syncmail... Mailing relnotes at fedoraproject.org... ...syncmail done. $ make tag cvs tag -c ktorrent-2_0-3_fc6 For more information on using the Fedora source code repositories, please visit http://fedoraproject.org/wiki/UsingCvs ? i386 ? ktorrent-2.0 ? ktorrent-2.0-2.src.rpm ERROR: creating module-wide tags is prohibited cvs tag: Pre-tag check failed ERROR: The tag ktorrent-2_0-3_fc6 is already applied on a different branch ERROR: You can not forcibly move tags between branches ktorrent-1_2-4:devel:liquidat:1150854425 ktorrent-1_2-4_fc6:devel:liquidat:1150920337 ktorrent-1_2-4_fc5:FC-5:liquidat:1150920347 ktorrent-2_0-1:devel:liquidat:1155525600 ktorrent-2_0-1_fc6:devel:liquidat:1155525752 ktorrent-2_0-2_fc6:devel:liquidat:1155527830 ktorrent-2_0-2_fc6:devel:liquidat:1155527895 ktorrent-2_0-2_fc6:devel:liquidat:1155527896 ktorrent-2_0-3_fc6:devel:liquidat:1155562961 cvs tag: Pre-tag check failed ERROR: Tag ktorrent-2_0-3_fc6 has been already created. The following tags have been created so far ktorrent-1_2-4:devel:liquidat:1150854425 ktorrent-1_2-4_fc6:devel:liquidat:1150920337 ktorrent-1_2-4_fc5:FC-5:liquidat:1150920347 ktorrent-2_0-1:devel:liquidat:1155525600 ktorrent-2_0-1_fc6:devel:liquidat:1155525752 ktorrent-2_0-2_fc6:devel:liquidat:1155527830 ktorrent-2_0-2_fc6:devel:liquidat:1155527895 ktorrent-2_0-2_fc6:devel:liquidat:1155527896 ktorrent-2_0-3_fc6:devel:liquidat:1155562961 cvs tag: Pre-tag check failed cvs [tag aborted]: correct the above errors first! make: *** [tag] Fehler 1 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bugs.michael at gmx.net Mon Aug 14 14:58:56 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Mon, 14 Aug 2006 16:58:56 +0200 Subject: Problems with tagging In-Reply-To: <200608141549.25227.wolters.liste@gmx.net> References: <200608140605.55884.wolters.liste@gmx.net> <200608141529.38862.wolters.liste@gmx.net> <20060814153940.c1aa4284.bugs.michael@gmx.net> <200608141549.25227.wolters.liste@gmx.net> Message-ID: <20060814165856.19b9b2cb.bugs.michael@gmx.net> On Mon, 14 Aug 2006 15:49:19 +0200, Roland Wolters wrote: > Once upon a time Michael Schwendt wrote: > > On Mon, 14 Aug 2006 15:29:32 +0200, Roland Wolters wrote: > > > Once upon a time Michael Schwendt wrote: > > > > On Mon, 14 Aug 2006 06:05:03 +0200, Roland Wolters wrote: > > > > > $ make tag build > > > > > cvs tag -c ktorrent-2_0-2_fc6 > > > > > > > > > > It already looks like a mess, so before I screw it up even more: What > > > > > should I do now? > > > > > > > > Simply bump "Release", commit, and run "make tag" again. > > > > > > Thanks for the naswer, but unfortunately I do not get it - what do you > > > mean with "bump"? Should I delete the "Release" line in the spec file of > > > the devel branch? > > > > No, _increase_ its value, commit, then run "make tag". > > I tried, and it didn't work. > The output is attached, it is everythign what I did after editing the local > spec file in the devel directory. I wonder why it says that there already is > a .3 release although I just edited the spec file to get a .3 release... The new tag was created 2006-08-14 by you: > torrent-2_0-3_fc6:devel:liquidat:1155562961 1155562961 is today. Maybe you just got the order wrong. Moving it (retagging the files) worked fine here: $ cvs co ktorrent ; cd ktorrent/devel $ TAG_OPTS=-F make tag cvs tag -F -c ktorrent-2_0-3_fc6 For more information on using the Fedora source code repositories, please visit http://fedoraproject.org/wiki/UsingCvs cvs tag: Tagging . T .cvsignore T Makefile T ktorrent.spec T sources Tagged with: ktorrent-2_0-3_fc6 From j.w.r.degoede at hhs.nl Mon Aug 14 15:09:52 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Mon, 14 Aug 2006 17:09:52 +0200 Subject: The bug squad is hiring! In-Reply-To: <44E07865.1050302@fedoraproject.org> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> <44DD6914.4080401@hhs.nl> <44DDACB3.6000509@fedoraproject.org> <44DEE087.4090708@hhs.nl> <44DF3505.3090309@fedoraproject.org> <44E07737.2070009@hhs.nl> <44E07865.1050302@fedoraproject.org> Message-ID: <44E09240.3040605@hhs.nl> Rahul wrote: > Hans de Goede wrote: > >> I'll add a part to the bugzappers wiki about this then, I also would >> like to maintain a page with a list of easy fixable bugs, or rather with >> 3 lists: >> 1) easy fixable and annoying / high impact >> 2) annoying / highimpact >> 3) easy fixable >> >> The idea is to have a short description of each bug and an URL, so that >> people who want to help with this can easily find a bug to work on. > > Wouldnt it be better to use the bugzilla whiteboard for this and just > link to the queries from the wiki page? Perhaps, call me a newbie, but what is the bugzilla whiteboard? I know about keywords and blocker bugs, but this one is new to me. Regards, Hans From sundaram at fedoraproject.org Mon Aug 14 15:18:05 2006 From: sundaram at fedoraproject.org (Rahul) Date: Mon, 14 Aug 2006 20:48:05 +0530 Subject: The bug squad is hiring! In-Reply-To: <44E09240.3040605@hhs.nl> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> <44DD6914.4080401@hhs.nl> <44DDACB3.6000509@fedoraproject.org> <44DEE087.4090708@hhs.nl> <44DF3505.3090309@fedoraproject.org> <44E07737.2070009@hhs.nl> <44E07865.1050302@fedoraproject.org> <44E09240.3040605@hhs.nl> Message-ID: <44E0942D.6070700@fedoraproject.org> Hans de Goede wrote: > > Rahul wrote: >> Hans de Goede wrote: >> >>> I'll add a part to the bugzappers wiki about this then, I also would >>> like to maintain a page with a list of easy fixable bugs, or rather with >>> 3 lists: >>> 1) easy fixable and annoying / high impact >>> 2) annoying / highimpact >>> 3) easy fixable >>> >>> The idea is to have a short description of each bug and an URL, so that >>> people who want to help with this can easily find a bug to work on. >> Wouldnt it be better to use the bugzilla whiteboard for this and just >> link to the queries from the wiki page? > > Perhaps, call me a newbie, but what is the bugzilla whiteboard? I know > about keywords and blocker bugs, but this one is new to me. > Think of it as a "notes" field where you add in comments about the bug which says that this is a easy fix or whatever and then query that. https://bugzilla.redhat.com/bugzilla/queryhelp.cgi#statuswhiteboard Rahul From j.w.r.degoede at hhs.nl Mon Aug 14 16:09:06 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Mon, 14 Aug 2006 18:09:06 +0200 Subject: Crack-attack submitted for review Message-ID: <44E0A022.9010606@hhs.nl> Hi all, Sine the discussion about the legal stuff has gone quiet without any real objections I've just submitted crack-attack for review: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202457 I'm posting this notice here so that people who object get a chance todo so now and so that I don't get accused of trying to sneak this into FE. Regards, Hans From wolters.liste at gmx.net Mon Aug 14 17:06:54 2006 From: wolters.liste at gmx.net (Roland Wolters) Date: Mon, 14 Aug 2006 19:06:54 +0200 Subject: Problems with tagging In-Reply-To: <20060814165856.19b9b2cb.bugs.michael@gmx.net> References: <200608140605.55884.wolters.liste@gmx.net> <200608141549.25227.wolters.liste@gmx.net> <20060814165856.19b9b2cb.bugs.michael@gmx.net> Message-ID: <200608141907.01211.wolters.liste@gmx.net> Once upon a time Michael Schwendt wrote: > [...] > > > No, _increase_ its value, commit, then run "make tag". > > > > I tried, and it didn't work. > > The output is attached, it is everythign what I did after editing the > > local spec file in the devel directory. I wonder why it says that there > > already is a .3 release although I just edited the spec file to get a .3 > > release... > > The new tag was created 2006-08-14 by you: > > torrent-2_0-3_fc6:devel:liquidat:1155562961 > > 1155562961 is today. Maybe you just got the order wrong. > Moving it (retagging the files) worked fine here: > > $ cvs co ktorrent ; cd ktorrent/devel > $ TAG_OPTS=-F make tag > cvs tag -F -c ktorrent-2_0-3_fc6 > For more information on using the Fedora source code repositories, > please visit http://fedoraproject.org/wiki/UsingCvs > cvs tag: Tagging . > T .cvsignore > T Makefile > T ktorrent.spec > T sources > Tagged with: ktorrent-2_0-3_fc6 So, what should I do now? I tried the same steps as you did, and the result is: $ TAG_OPTS=-F make tag cvs tag -F -c ktorrent-2_0-3_fc6 For more information on using the Fedora source code repositories, please visit http://fedoraproject.org/wiki/UsingCvs ? i386 ? ktorrent-2.0 ? ktorrent-2.0-2.src.rpm ERROR: creating module-wide tags is prohibited cvs tag: Pre-tag check failed ERROR: The tag ktorrent-2_0-3_fc6 is already applied on a different branch ERROR: You can not forcibly move tags between branches cvs tag: Pre-tag check failed cvs [tag aborted]: correct the above errors first! make: *** [tag] Fehler 1 -- "All terrorists should die". Nice... No. All terrorists should be brought to justice. What makes you better than them, otherwise? [...] Following the Geneva convention isn't a sign that we're wussies and girlie-men. It's a sign that we aren't afraid of the attacks, and that we can think. -- Adriano Varoli Piazza -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bugs.michael at gmx.net Mon Aug 14 17:25:38 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Mon, 14 Aug 2006 19:25:38 +0200 Subject: Problems with tagging In-Reply-To: <200608141907.01211.wolters.liste@gmx.net> References: <200608140605.55884.wolters.liste@gmx.net> <200608141549.25227.wolters.liste@gmx.net> <20060814165856.19b9b2cb.bugs.michael@gmx.net> <200608141907.01211.wolters.liste@gmx.net> Message-ID: <20060814192538.6961b243.bugs.michael@gmx.net> On Mon, 14 Aug 2006 19:06:54 +0200, Roland Wolters wrote: > So, what should I do now? I tried the same steps as you did, and the result > is: > > $ TAG_OPTS=-F make tag > cvs tag -F -c ktorrent-2_0-3_fc6 > For more information on using the Fedora source code repositories, > please visit http://fedoraproject.org/wiki/UsingCvs > ? i386 > ? ktorrent-2.0 > ? ktorrent-2.0-2.src.rpm > ERROR: creating module-wide tags is prohibited > cvs tag: Pre-tag check failed > ERROR: The tag ktorrent-2_0-3_fc6 is already applied on a different branch > ERROR: You can not forcibly move tags between branches > cvs tag: Pre-tag check failed > cvs [tag aborted]: correct the above errors first! > make: *** [tag] Fehler 1 Restart at a fresh checkout? From jkeating at redhat.com Mon Aug 14 17:29:34 2006 From: jkeating at redhat.com (Jesse Keating) Date: Mon, 14 Aug 2006 13:29:34 -0400 Subject: Problems with tagging In-Reply-To: <200608141907.01211.wolters.liste@gmx.net> References: <200608140605.55884.wolters.liste@gmx.net> <20060814165856.19b9b2cb.bugs.michael@gmx.net> <200608141907.01211.wolters.liste@gmx.net> Message-ID: <200608141329.34640.jkeating@redhat.com> On Monday 14 August 2006 13:06, Roland Wolters wrote: > ERROR: The tag ktorrent-2_0-3_fc6 is already applied on a different branch > ERROR: You can not forcibly move tags between branches Um, what branch are you trying to tag in? If you're getting '.fc6' versioning while not in the devel/ branch, you've got something going on that needs to be fixed perhaps by a fresh checkout of the module. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From wolters.liste at gmx.net Mon Aug 14 17:59:01 2006 From: wolters.liste at gmx.net (Roland Wolters) Date: Mon, 14 Aug 2006 19:59:01 +0200 Subject: Problems with tagging In-Reply-To: <200608141329.34640.jkeating@redhat.com> References: <200608140605.55884.wolters.liste@gmx.net> <200608141907.01211.wolters.liste@gmx.net> <200608141329.34640.jkeating@redhat.com> Message-ID: <200608141959.06238.wolters.liste@gmx.net> Once upon a time Jesse Keating wrote: > On Monday 14 August 2006 13:06, Roland Wolters wrote: > > ERROR: The tag ktorrent-2_0-3_fc6 is already applied on a different > > branch ERROR: You can not forcibly move tags between branches > > Um, what branch are you trying to tag in? If you're getting '.fc6' > versioning while not in the devel/ branch, you've got something going on > that needs to be fixed perhaps by a fresh checkout of the module. As I mentioned, I am in the devel directory. Roland -- "It seems to me that with or without religion good people will behave well and bad people will do evil things. But for good people to do evil things, that takes religion." -- Dr. Steven Weinberg, Physiknobelpreistr?ger -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From wolters.liste at gmx.net Mon Aug 14 18:00:57 2006 From: wolters.liste at gmx.net (Roland Wolters) Date: Mon, 14 Aug 2006 20:00:57 +0200 Subject: Problems with tagging In-Reply-To: <20060814192538.6961b243.bugs.michael@gmx.net> References: <200608140605.55884.wolters.liste@gmx.net> <200608141907.01211.wolters.liste@gmx.net> <20060814192538.6961b243.bugs.michael@gmx.net> Message-ID: <200608142000.57391.wolters.liste@gmx.net> Once upon a time Michael Schwendt wrote: > On Mon, 14 Aug 2006 19:06:54 +0200, Roland Wolters wrote: > > So, what should I do now? I tried the same steps as you did, and the > > result is: > > > > $ TAG_OPTS=-F make tag > > cvs tag -F -c ktorrent-2_0-3_fc6 > > For more information on using the Fedora source code repositories, > > please visit http://fedoraproject.org/wiki/UsingCvs > > ? i386 > > ? ktorrent-2.0 > > ? ktorrent-2.0-2.src.rpm > > ERROR: creating module-wide tags is prohibited > > cvs tag: Pre-tag check failed > > ERROR: The tag ktorrent-2_0-3_fc6 is already applied on a different > > branch ERROR: You can not forcibly move tags between branches > > cvs tag: Pre-tag check failed > > cvs [tag aborted]: correct the above errors first! > > make: *** [tag] Fehler 1 > > Restart at a fresh checkout? You mean with a previous "cvs co ktorrent" from my cvs root directory? I did it, like you did, with cvs co ktorrent ; cd ktorrent/devel Or should I completely remove the whole directory from my hard disk, and check it out new? I thought that such steps are not necessary with cvs... Roland -- "Was wir zu f?rchten haben, ist nicht die Unmenschlichkeit der gro?en M?nner, sondern dass Unmenschlichkeit oft zu Gr??e f?hrt." -- Alexis de Tocqueville -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bugs.michael at gmx.net Mon Aug 14 18:19:40 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Mon, 14 Aug 2006 20:19:40 +0200 Subject: Problems with tagging In-Reply-To: <200608142000.57391.wolters.liste@gmx.net> References: <200608140605.55884.wolters.liste@gmx.net> <200608141907.01211.wolters.liste@gmx.net> <20060814192538.6961b243.bugs.michael@gmx.net> <200608142000.57391.wolters.liste@gmx.net> Message-ID: <20060814201940.9a26535f.bugs.michael@gmx.net> On Mon, 14 Aug 2006 20:00:57 +0200, Roland Wolters wrote: > Once upon a time Michael Schwendt wrote: > > On Mon, 14 Aug 2006 19:06:54 +0200, Roland Wolters wrote: > > > So, what should I do now? I tried the same steps as you did, and the > > > result is: > > > > > > $ TAG_OPTS=-F make tag > > > cvs tag -F -c ktorrent-2_0-3_fc6 > > > For more information on using the Fedora source code repositories, > > > please visit http://fedoraproject.org/wiki/UsingCvs > > > ? i386 > > > ? ktorrent-2.0 > > > ? ktorrent-2.0-2.src.rpm > > > ERROR: creating module-wide tags is prohibited > > > cvs tag: Pre-tag check failed > > > ERROR: The tag ktorrent-2_0-3_fc6 is already applied on a different > > > branch ERROR: You can not forcibly move tags between branches > > > cvs tag: Pre-tag check failed > > > cvs [tag aborted]: correct the above errors first! > > > make: *** [tag] Fehler 1 > > > > Restart at a fresh checkout? > > You mean with a previous "cvs co ktorrent" from my cvs root directory? Yes. > I did > it, like you did, with cvs co ktorrent ; cd ktorrent/devel Well, your output contains working files. I don't want to guess what else might confuse cvs. Further, moving existing tags with option -F doesn't work reliably always, particularly if all files are tagged already correctly. It is really trivial to just increase the release version, commit the change, then run "make tag". Since you write you've tried that earlier and it failed, try again on a fresh check-out. If it still fails to tag your files, you do a systematic mistake somewhere. From wolters.liste at gmx.net Mon Aug 14 18:48:46 2006 From: wolters.liste at gmx.net (Roland Wolters) Date: Mon, 14 Aug 2006 20:48:46 +0200 Subject: Problems with tagging In-Reply-To: <20060814201940.9a26535f.bugs.michael@gmx.net> References: <200608140605.55884.wolters.liste@gmx.net> <200608142000.57391.wolters.liste@gmx.net> <20060814201940.9a26535f.bugs.michael@gmx.net> Message-ID: <200608142048.51787.wolters.liste@gmx.net> Once upon a time Michael Schwendt wrote: > On Mon, 14 Aug 2006 20:00:57 +0200, Roland Wolters wrote: > > Once upon a time Michael Schwendt wrote: > > > On Mon, 14 Aug 2006 19:06:54 +0200, Roland Wolters wrote: > > > > So, what should I do now? I tried the same steps as you did, and the > > > > result is: > > > > > > > > $ TAG_OPTS=-F make tag > > > > cvs tag -F -c ktorrent-2_0-3_fc6 > > > > For more information on using the Fedora source code repositories, > > > > please visit http://fedoraproject.org/wiki/UsingCvs > > > > ? i386 > > > > ? ktorrent-2.0 > > > > ? ktorrent-2.0-2.src.rpm > > > > ERROR: creating module-wide tags is prohibited > > > > cvs tag: Pre-tag check failed > > > > ERROR: The tag ktorrent-2_0-3_fc6 is already applied on a different > > > > branch ERROR: You can not forcibly move tags between branches > > > > cvs tag: Pre-tag check failed > > > > cvs [tag aborted]: correct the above errors first! > > > > make: *** [tag] Fehler 1 > > > > > > Restart at a fresh checkout? > > > > You mean with a previous "cvs co ktorrent" from my cvs root directory? > > Yes. > > > I did > > it, like you did, with cvs co ktorrent ; cd ktorrent/devel > > Well, your output contains working files. I don't want to guess what else > might confuse cvs. Further, moving existing tags with option -F doesn't > work reliably always, particularly if all files are tagged already > correctly. It is really trivial to just increase the release version, > commit the change, then run "make tag". Since you write you've tried that > earlier and it failed, try again on a fresh check-out. If it still fails > to tag your files, you do a systematic mistake somewhere. Ok, this worked: I deleted the whole ktorrent directory on my hard disk, made a fresh co, increased the release number, commited the change, and tagged. The build process was also successful. I wonder why this worked - I thought that the job of cvs is to keep the files synchronized?! Anyway, thanks for the help! Roland -- Blo? weil es mir egal ist, hei?t das nicht, dass ich es nicht vestehe. -- Homer Simpson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From katzj at redhat.com Mon Aug 14 18:55:50 2006 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 14 Aug 2006 14:55:50 -0400 Subject: Upload problem In-Reply-To: References: <44DC5ED5.9090509@hhs.nl> <44DCD569.70900@hhs.nl> Message-ID: <1155581750.22107.19.camel@aglarond.local> On Sat, 2006-08-12 at 00:22 +0200, Linus Walleij wrote: > On Fri, 11 Aug 2006, Jima wrote: > > Really? My first thought when I see "Error 255" is "hmm, looks like someone > > needs a new client cert!" It's been asked (and answered) many times on the > > mailing lists. Maybe it needs to be in a FAQ somewhere? Maybe we need a wiki > > page titled Error_255? :) > > Nah I put it in at the end of the CVS FAQ... Note: if anyone wants to work on a patch to Makefile.common that actually checks the validity of the cert before trying the upload, I would be *more* than happy to commit it :-) Jeremy From wtogami at redhat.com Mon Aug 14 19:21:00 2006 From: wtogami at redhat.com (Warren Togami) Date: Mon, 14 Aug 2006 15:21:00 -0400 Subject: nobody@fedoraproject.org Assignment and Querying Message-ID: <44E0CD1C.3060105@redhat.com> I have created nobody at fedoraproject.org Bugzilla account. This will be the new default assignee for Extras package reviews. It is a little more appropriate and informative than bugzilla-sink at leemhuis.info. Nobody's working on this, feel free to take it I got the idea from Mozilla's Bugzilla. It makes it more obvious from reading that nothing will happen with a bug unless somebody takes it. Bugs against orphan packages should be reassigned here too, as well as anything that cannot be fixed by the primary assignee. While it would be bad to overuse it, I think it is more honest than bugs sitting forever and the assignee having the inability to work on it. http://tinyurl.com/lc4s2 The idea is that a standard URL "canned query" can be used to pull up all issues that nobody is working on. Then other project participants can easily find issues that are otherwise stuck and explicitly claim them. This is just a temporary URL, we should make a permanent URL somewhere in the Fedora Infrastructure. If something truly bad remains assigned to nobody, and no one wishes to claim it, then these cases are to be identified and escalated to FPB, where priority assessment and assignment can happen. Warren Togami wtogami at redhat.com From wtogami at redhat.com Mon Aug 14 19:25:56 2006 From: wtogami at redhat.com (Warren Togami) Date: Mon, 14 Aug 2006 15:25:56 -0400 Subject: nobody@fedoraproject.org Assignment and Querying In-Reply-To: <44E0CD1C.3060105@redhat.com> References: <44E0CD1C.3060105@redhat.com> Message-ID: <44E0CE44.6090408@redhat.com> Warren Togami wrote: > > http://tinyurl.com/lc4s2 > The idea is that a standard URL "canned query" can be used to pull up > all issues that nobody is working on. Then other project participants > can easily find issues that are otherwise stuck and explicitly claim > them. This is just a temporary URL, we should make a permanent URL > somewhere in the Fedora Infrastructure. > > If something truly bad remains assigned to nobody, and no one wishes to > claim it, then these cases are to be identified and escalated to FPB, > where priority assessment and assignment can happen. > I misstated this. Escalation would happen up the chain of command. In the case of Extras, it would start with FESCO first, then FPB if FESCO fails. Warren Togami wtogami at redhat.com From rhbugs at n-dimensional.de Mon Aug 14 19:40:01 2006 From: rhbugs at n-dimensional.de (Hans Ulrich Niedermann) Date: Mon, 14 Aug 2006 21:40:01 +0200 Subject: Proposal for (FC and) FE Package Review Request template Message-ID: <1155584401.4586.14.camel@mir> Hi, I'd like to suggest to change the "Subject" line of the the bugzilla FE Package Review Request template at https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora% 20Extras&format=extras-review to "Review Request:
: " or "Review Request:
- " The summary part is currently missing, but the Review Guidelines suggest it and it seems to be common practise to include it: http://fedoraproject.org/wiki/Packaging/ReviewGuidelines Gru?, Uli P.S: The same applies to the FC Package Review Request template at https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora% 20Core&format=core-review From j.w.r.degoede at hhs.nl Mon Aug 14 19:52:49 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Mon, 14 Aug 2006 21:52:49 +0200 Subject: The bug squad is hiring! In-Reply-To: <44E0942D.6070700@fedoraproject.org> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> <44DD6914.4080401@hhs.nl> <44DDACB3.6000509@fedoraproject.org> <44DEE087.4090708@hhs.nl> <44DF3505.3090309@fedoraproject.org> <44E07737.2070009@hhs.nl> <44E07865.1050302@fedoraproject.org> <44E09240.3040605@hhs.nl> <44E0942D.6070700@fedoraproject.org> Message-ID: <44E0D491.5000003@hhs.nl> Hi All, I've been thinking about this some more and although I still firmly believe in the basic ideas behind this (taping into the community to help fix high impact / annoying bugs), I don't feel like pulling the kart / spearheading the effort. so I won't be adding something to the wiki, mainly because I have the feeling it won't be used much as the response to this thread sofar has been minimal. Maybe I also have been going the wrong way, because I believe that in order for the community to help fix bugs, the package maintainer who could use / wants / needs the communities help should get involved. Maybe he should not only be involved but he should be taking the initiative to ask the community for help, that way the volunteers have guarantees that their work will get integrated. Currently my experience with this has been a bit frustrating. In order to be able to help in many cases I will need some pointers (general direction) where to look. And sofar replies to requests for such general directions have been absent. In the one case where I did manage to locate and fix a bug after a couple of hours of debugging, the fix for this hasn't been integrated yet (its a very simple 1 line fix which is obviously correct). So to make a long story short I will still be trying to help out by cherry picking some bugs and trying to fix this, but I hereby cease any activities to try and create a coordinated community bug squashing effort. Still any Core developers overwelmed with bugs who need a hand feel free to ask me, and I think / guess you should feel free to ask the community in general, that might be the better way to get the community involved in helping with the enormous amount of bugs (of much varying severity). Regards, Hans From steve at silug.org Mon Aug 14 22:43:42 2006 From: steve at silug.org (Steven Pritchard) Date: Mon, 14 Aug 2006 17:43:42 -0500 Subject: Proper Source0 URL for sf.net hosted projects? In-Reply-To: <44E051CA.3030804@hhs.nl> References: <44E051CA.3030804@hhs.nl> Message-ID: <20060814224341.GA31541@osiris.silug.org> On Mon, Aug 14, 2006 at 12:34:50PM +0200, Hans de Goede wrote: > I was wondering what the correct Source0 URL for sourceforge.net hosted > projects is? [...] Any time I see a sourceforge URL, I take it as a suggestion. I don't expect it to work as-is necessarily. Steve -- Steven Pritchard - K&S Pritchard Enterprises, Inc. Email: steve at kspei.com http://www.kspei.com/ Phone: (618)398-3000 Mobile: (618)567-7320 From buildsys at fedoraproject.org Mon Aug 14 23:16:44 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Mon, 14 Aug 2006 19:16:44 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-14 Message-ID: <20060814231644.33935152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 25 alleggl-0.4.0-0.4.rc4.fc5 azureus-2.4.0.3-0.20060604cvs_1.fc5 bwidget-1.7.0-3.fc5 dia-0.95-6.fc5 gcompris-7.4-13.fc5 gnome-translate-0.99-8.fc5 gtkglext-1.2.0-3.fc5 k3d-0.5.16.0-3.fc5 ktorrent-2.0-5.fc5 libupnp-1.4.1-1.fc5 nip2-7.10.20-2.fc5 pengupop-2.1.4-1.fc5 perl-Email-Address-1.870-1.fc5 perl-POE-0.3601-1.fc5 perl-POE-Component-SSLify-0.04-2.fc5 perl-Params-Util-0.17-1.fc5 perl-Params-Validate-0.86-1.fc5 pinball-0.3.1-5.fc5 python-myghty-1.0.2-2.fc5 python-vobject-0.4.1-1.fc5 seahorse-0.8.1-1.fc5 sylpheed-2.2.7-1.fc5 wordpress-2.0.4-0.fc5 xsp-1.1.16.1-1.fc5 yum-utils-0.6-3.fc5 Packages built and released for Fedora Extras 4: 9 k3d-0.5.16.0-4.fc4 libupnp-1.4.1-1.fc4 nip2-7.10.20-2.fc4 pengupop-2.1.4-1.fc4 perl-Email-Address-1.870-1.fc4 perl-Params-Util-0.17-1.fc4 perl-Params-Validate-0.86-1.fc4 seahorse-0.8.1-1.fc4 wordpress-2.0.4-0.fc4 Packages built and released for Fedora Extras 3: 1 libupnp-1.4.1-1.fc3 Packages built and released for Fedora Extras development: 41 ClanLib-0.8.0-1.fc6 audacious-1.1.1-4.fc6 azureus-2.4.0.3-0.20060730cvs_1.fc6 buoh-0.8.1-10 contacts-0.1-4.20060813svn.fc6 dates-0.1-2.20060813svn.fc6 dia-0.95-6.fc6 echoping-5.2.0-1.fc6 gcompris-7.4-13.fc6 gnome-build-0.1.3-8.fc6 gnome-translate-0.99-9.fc6 gtkglext-1.2.0-3.fc6 ktorrent-2.0-4.fc6 libtorrent-0.10.0-1.fc6 libupnp-1.4.1-1.fc6 mboxgrep-0.7.9-2.fc6 nautilus-flac-converter-0.0.2-5.fc6 nautilus-image-converter-0.0.5-4.fc6 nip2-7.10.20-2.fc6 pengupop-2.1.4-1.fc6 perl-AppConfig-1.63-1.fc6 perl-Cairo-0.91-1.fc6 perl-Email-Address-1.870-1.fc6 perl-File-HomeDir-0.58-1.fc6 perl-POE-0.3601-1.fc6 perl-Params-Util-0.17-1.fc6 perl-Params-Validate-0.86-1.fc6 php-pecl-apc-3.0.10-4.fc6 pingus-0.7.0-0.3.20060721.fc6 python-clientform-0.2.2-5.fc6 python-configobj-4.3.2-3.fc6 python-myghty-1.0.2-1.fc6 python-ruledispatch-0.5a0-0.2.svnr2115.fc6 python-simplejson-1.3-3.fc6 python-vobject-0.4.1-1.fc6 rt3-3.6.1-1.fc6 rtorrent-0.6.0-1.fc6 seahorse-0.8.1-1.fc6 ufsparse-2.0.0-1.fc6 wordpress-2.0.4-0.fc6 xsp-1.1.16.1-1.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Mon Aug 14 23:17:15 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Mon, 14 Aug 2006 19:17:15 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-14 Message-ID: <20060814231715.66BAC152169@buildsys.fedoraproject.org> camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) digikam: mgarski AT post.pl 3: 0:0.8.2-2.fc3 (FE3) 4: 0:0.8.2-1.fc4 (FE4) 5: 0:0.8.2-1.fc5 (FE5) 6: 0:0.8.2-1.fc6 (FE6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: liljencrantz AT gmail.com 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gaim-gaym: cweyl AT alumni.drew.edu 5: 0:0.96-3.fc5 (FE5) 6: 0:0.96-2.fc6 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) k3d: denis AT poolshark.org 4: 0:0.5.16.0-4.fc4 (FE4) 5: 0:0.5.16.0-3.fc5 (FE5) 6: 0:0.5.16.0-3.fc6 (FE6) koffice: andreas.bierfert AT lowlatency.de 5: 0:1.5.2-1.fc5 (FE5) 6: 0:1.5.1-2.fc6 (FE6) ktorrent: wolters.liste AT gmx.net 5: 0:2.0-5.fc5 (FE5) 6: 0:2.0-4.fc6 (FE6) libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) libpqxx: andreas.bierfert AT lowlatency.de 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) libsoup: 5: 0:2.2.96-1.fc5.1 (FC5-updates) 6: 0:2.2.96-1 (FC6) lvm2: 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) mozilla: 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.2-2.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) quagga: 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) seamonkey: kengert AT redhat.com 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) smart: Axel.Thimm AT ATrpms.net 5: 0:0.42-35.fc5 (FE5) 6: 0:0.41-31.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.5-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) vorbisgain: noa AT resare.com 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) XaraLX: paul AT all-the-johnsons.co.uk 5: 0:0.7-3.fc5.r1614 (FE5) 6: 0:0.7-2.fc6.r1614 (FE6) From buildsys at fedoraproject.org Mon Aug 14 23:36:53 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Mon, 14 Aug 2006 23:36:53 -0000 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-14 Message-ID: <20060814233653.10020.22658@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (130 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (130 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (7 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (7 days) libopensync-plugin-evolution2 - 0.18-6.fc5.i386 (7 days) libopensync-plugin-evolution2 - 0.18-6.fc5.ppc (7 days) libopensync-plugin-evolution2 - 0.18-6.fc5.x86_64 (7 days) wine-core - 0.9.17-1.fc6.i386 (19 days) bdpepple AT ameritech.net contact-lookup-applet - 0.14-3.fc6.i386 (7 days) contact-lookup-applet - 0.14-3.fc6.ppc (7 days) contact-lookup-applet - 0.14-3.fc6.x86_64 (7 days) byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (26 days) gaim-guifications - 2.12-3.fc5.ppc (26 days) gaim-guifications - 2.12-3.fc5.x86_64 (26 days) cweyl AT alumni.drew.edu gaim-gaym - 0.96-2.fc6.i386 (26 days) gaim-gaym - 0.96-2.fc6.ppc (26 days) gaim-gaym - 0.96-2.fc6.x86_64 (26 days) fedora AT leemhuis.info gsynaptics - 0.9.8-1.fc6.ppc (26 days) gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (18 days) amarok - 1.4.1-3.fc6.ppc (18 days) showimg-pgsql - 0.9.5-7.fc4.i386 (7 days) showimg-pgsql - 0.9.5-7.fc4.ppc (7 days) showimg-pgsql - 0.9.5-7.fc4.x86_64 (7 days) showimg-pgsql - 0.9.5-7.fc5.i386 (7 days) showimg-pgsql - 0.9.5-7.fc5.ppc (7 days) showimg-pgsql - 0.9.5-7.fc5.x86_64 (7 days) green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (19 days) jogl - 1.1.1-14.fc5.ppc (22 days) ivazquez AT ivazquez.net deskbar-applet - 2.14.1.1-1.fc6.i386 (7 days) deskbar-applet - 2.14.1.1-1.fc6.ppc (7 days) deskbar-applet - 2.14.1.1-1.fc6.x86_64 (7 days) gnome-applet-music - 0.9.0-1.fc6.i386 (26 days) gnome-applet-music - 0.9.0-1.fc6.ppc (26 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (26 days) nautilus-search-tool - 0.2-1.fc5.i386 (26 days) nautilus-search-tool - 0.2-1.fc5.ppc (26 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (26 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (26 days) gfontview - 0.5.0-5.fc5.ppc (26 days) gfontview - 0.5.0-5.fc5.x86_64 (26 days) gtkhtml36 - 3.6.2-5.fc6.i386 (26 days) gtkhtml36 - 3.6.2-5.fc6.ppc (26 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (26 days) libvisual-plugins - 0.2.0-3.fc5.i386 (26 days) libvisual-plugins - 0.2.0-3.fc5.i386 (26 days) libvisual-plugins - 0.2.0-3.fc5.ppc (26 days) libvisual-plugins - 0.2.0-3.fc5.ppc (26 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (26 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (26 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (89 days) syck-php - 0.55-7.fc5.i386 (89 days) syck-php - 0.55-7.fc5.ppc (89 days) syck-php - 0.55-7.fc5.ppc (89 days) syck-php - 0.55-7.fc5.x86_64 (89 days) syck-php - 0.55-7.fc5.x86_64 (89 days) paul AT all-the-johnsons.co.uk gnome-build - 0.1.3-8.fc6.i386 gnome-build - 0.1.3-8.fc6.ppc gnome-build - 0.1.3-8.fc6.x86_64 petersen AT redhat.com ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.i386 (5 days) ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.ppc (5 days) ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.x86_64 (5 days) qspencer AT ieee.org octave - 6:2.9.7-1.fc6.i386 octave - 6:2.9.7-1.fc6.ppc octave - 6:2.9.7-1.fc6.x86_64 rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (26 days) libibverbs - 1.0.3-1.fc6.ppc (26 days) libibverbs - 1.0.3-1.fc6.x86_64 (26 days) libibverbs-utils - 1.0.3-1.fc6.i386 (26 days) libibverbs-utils - 1.0.3-1.fc6.ppc (26 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (26 days) tcallawa AT redhat.com gambas-runtime - 1.0.14-2.fc5.i386 (6 days) thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (26 days) directfb - 0.9.24-5.fc5.ppc (26 days) directfb - 0.9.24-5.fc5.x86_64 (26 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.i386 requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) showimg-pgsql-0.9.5-7.fc5.x86_64 requires libpqxx-2.6.6.so()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.ppc requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.i386 requires libpqxx-2.6.6.so Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.x86_64 requires libpqxx-2.6.6.so()(64bit) Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.ppc requires libpqxx-2.6.6.so Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer contact-lookup-applet-0.14-3.fc6.i386 requires libebook-1.2.so.5 deskbar-applet-2.14.1.1-1.fc6.i386 requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.i386 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 gambas-runtime-1.0.14-2.fc5.i386 requires libgettextlib-0.14.5.so gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-2.fc6.i386 requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gnome-build-0.1.3-8.fc6.i386 requires perl(GBF::Make) gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 octave-6:2.9.7-1.fc6.i386 requires libccolamd.so.1 octave-6:2.9.7-1.fc6.i386 requires libumfpack.so.4 octave-6:2.9.7-1.fc6.i386 requires libcxsparse.so.1 octave-6:2.9.7-1.fc6.i386 requires libamd.so.1 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- contact-lookup-applet-0.14-3.fc6.x86_64 requires libebook-1.2.so.5()(64bit) deskbar-applet-2.14.1.1-1.fc6.x86_64 requires libebook-1.2.so.5()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-gaym-0.96-2.fc6.x86_64 requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) ghc642-gtk2hs-mozembed-0.9.10-2.fc6.x86_64 requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gnome-build-0.1.3-8.fc6.x86_64 requires perl(GBF::Make) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libedata-cal-1.2.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libecal-1.2.so.3()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libebook-1.2.so.5()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) octave-6:2.9.7-1.fc6.x86_64 requires libcxsparse.so.1()(64bit) octave-6:2.9.7-1.fc6.x86_64 requires libumfpack.so.4()(64bit) octave-6:2.9.7-1.fc6.x86_64 requires libccolamd.so.1()(64bit) octave-6:2.9.7-1.fc6.x86_64 requires libamd.so.1()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.17-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 contact-lookup-applet-0.14-3.fc6.ppc requires libebook-1.2.so.5 deskbar-applet-2.14.1.1-1.fc6.ppc requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-gaym-0.96-2.fc6.ppc requires gaim < 1:2.0.0 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-2.fc6.ppc requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gnome-build-0.1.3-8.fc6.ppc requires perl(GBF::Make) gsynaptics-0.9.8-1.fc6.ppc requires synaptics gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 octave-6:2.9.7-1.fc6.ppc requires libccolamd.so.1 octave-6:2.9.7-1.fc6.ppc requires libumfpack.so.4 octave-6:2.9.7-1.fc6.ppc requires libcxsparse.so.1 octave-6:2.9.7-1.fc6.ppc requires libamd.so.1 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 ====================================================================== New report for: paul AT all-the-johnsons.co.uk package: gnome-build - 0.1.3-8.fc6.i386 from fedora-extras-development-i386 unresolved deps: perl(GBF::Make) package: gnome-build - 0.1.3-8.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: perl(GBF::Make) package: gnome-build - 0.1.3-8.fc6.ppc from fedora-extras-development-ppc unresolved deps: perl(GBF::Make) ====================================================================== New report for: qspencer AT ieee.org package: octave - 6:2.9.7-1.fc6.i386 from fedora-extras-development-i386 unresolved deps: libccolamd.so.1 libumfpack.so.4 libcxsparse.so.1 libamd.so.1 package: octave - 6:2.9.7-1.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libcxsparse.so.1()(64bit) libumfpack.so.4()(64bit) libccolamd.so.1()(64bit) libamd.so.1()(64bit) package: octave - 6:2.9.7-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: libccolamd.so.1 libumfpack.so.4 libcxsparse.so.1 libamd.so.1 From cweyl at alumni.drew.edu Tue Aug 15 00:35:55 2006 From: cweyl at alumni.drew.edu (Chris Weyl) Date: Mon, 14 Aug 2006 17:35:55 -0700 Subject: [Fedora Project Wiki] Update of "Extras/FC6Status" by ChrisWeyl In-Reply-To: <20060813215201.5c627bef.bugs.michael@gmx.net> References: <20060812192214.4406.54772@fpserv.linux.duke.edu> <20060813215201.5c627bef.bugs.michael@gmx.net> Message-ID: <7dd7ab490608141735x7dac30d3h5ad8d12c8001f322@mail.gmail.com> On 8/13/06, Michael Schwendt wrote: > On Sat, 12 Aug 2006 19:22:14 -0000, fedorawiki-noreply at fedoraproject.org wrote: > > > The following page has been changed by ChrisWeyl: > > http://www.fedoraproject.org/wiki/Extras/FC6Status > > > > ------------------------------------------------------------------------------ > > - > > + * gaim-gaym - upstream code is not yet ready for the level of gaim in fc6 > > Pardon? Builds have been released for fc5 and fc4 already long ago, so > removing the packages from the devel repo would break the upgrade path. Right, unfortunately this plugin works with gaim1, not gaim2+. I've been beating up on upstream since gaim2 made it into devel, but always with the response "when gaim2 goes GA, we'll update." And who knows when that'll be. Not even the CVS code supports gaim2 yet, unfortunately. Soo... Right now, short of my writing a patch to make the necessary changes (which I'm close to doing, non-trivial as I suspect it might be), at least removing this package from fc6 will keep people from trying to install it under fresh builds. -Chris -- Chris Weyl Ex astris, scientia From paul at city-fan.org Tue Aug 15 07:36:53 2006 From: paul at city-fan.org (Paul Howarth) Date: Tue, 15 Aug 2006 08:36:53 +0100 Subject: The bug squad is hiring! In-Reply-To: <44E0D491.5000003@hhs.nl> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> <44DD6914.4080401@hhs.nl> <44DDACB3.6000509@fedoraproject.org> <44DEE087.4090708@hhs.nl> <44DF3505.3090309@fedoraproject.org> <44E07737.2070009@hhs.nl> <44E07865.1050302@fedoraproject.org> <44E09240.3040605@hhs.nl> <44E0942D.6070700@fedoraproject.org> <44E0D491.5000003@hhs.nl> Message-ID: <1155627413.23378.5.camel@metropolis.intra.city-fan.org> On Mon, 2006-08-14 at 21:52 +0200, Hans de Goede wrote: > So to make a long story short I will still be trying to help out by > cherry picking some bugs and trying to fix this, but I hereby cease any > activities to try and create a coordinated community bug squashing effort. > > Still any Core developers overwelmed with bugs who need a hand feel free > to ask me, and I think / guess you should feel free to ask the community > in general, that might be the better way to get the community involved > in helping with the enormous amount of bugs (of much varying severity). Does this mean you're not interested in Extras bugs? I have a couple of bugs in bittorrent that I lack the python skills to fix: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189072 (bittorrent gui needs to die gracefully when user logs out, just like it does if you close it manually) https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189295 (curses client not displaying UTF-8 characters properly) I'm not getting any responses to bug reports from upstream these days. I don't think they'll work on the first one at all since the GUI has been rewritten in wx instead of pygtk since the report was made. The second one might be a curses issue; I don't know. Paul. From j.w.r.degoede at hhs.nl Tue Aug 15 09:09:46 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Tue, 15 Aug 2006 11:09:46 +0200 Subject: The bug squad is hiring! In-Reply-To: <1155627413.23378.5.camel@metropolis.intra.city-fan.org> References: <44DB1061.7020508@hhs.nl> <44DB29C3.9020504@poolshark.org> <44DD6914.4080401@hhs.nl> <44DDACB3.6000509@fedoraproject.org> <44DEE087.4090708@hhs.nl> <44DF3505.3090309@fedoraproject.org> <44E07737.2070009@hhs.nl> <44E07865.1050302@fedoraproject.org> <44E09240.3040605@hhs.nl> <44E0942D.6070700@fedoraproject.org> <44E0D491.5000003@hhs.nl> <1155627413.23378.5.camel@metropolis.intra.city-fan.org> Message-ID: <44E18F5A.2070406@hhs.nl> Paul Howarth wrote: > On Mon, 2006-08-14 at 21:52 +0200, Hans de Goede wrote: >> So to make a long story short I will still be trying to help out by >> cherry picking some bugs and trying to fix this, but I hereby cease any >> activities to try and create a coordinated community bug squashing effort. >> >> Still any Core developers overwelmed with bugs who need a hand feel free >> to ask me, and I think / guess you should feel free to ask the community >> in general, that might be the better way to get the community involved >> in helping with the enormous amount of bugs (of much varying severity). > > Does this mean you're not interested in Extras bugs? I have a couple of > bugs in bittorrent that I lack the python skills to fix: > Ofcourse I'm willing to help with Extras bugs too, but extras doesn't need to seem as much help as core does (try looking for open bugs with keywords EasiFix in Extras versus Core). However my python skills are very minimal, so I cannot help you there. But a mail with a subject of 'Help from python "experts" needed' to f-e-l might help :) Regards, Hans From j.w.r.degoede at hhs.nl Tue Aug 15 09:12:02 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Tue, 15 Aug 2006 11:12:02 +0200 Subject: Proper Source0 URL for sf.net hosted projects? In-Reply-To: <20060814224341.GA31541@osiris.silug.org> References: <44E051CA.3030804@hhs.nl> <20060814224341.GA31541@osiris.silug.org> Message-ID: <44E18FE2.6010105@hhs.nl> Steven Pritchard wrote: > On Mon, Aug 14, 2006 at 12:34:50PM +0200, Hans de Goede wrote: >> I was wondering what the correct Source0 URL for sourceforge.net hosted >> projects is? > [...] > > Any time I see a sourceforge URL, I take it as a suggestion. I don't > expect it to work as-is necessarily. > But thats bad isn't it, that breaks things like spectool -g, which can be handy at times. Can't we come up with an always working one? Sofar this has been very successfull for me: http://dl.sf.net/sourceforge// Does anyone have any examples where this fails? Regards, Hans From Axel.Thimm at ATrpms.net Tue Aug 15 12:34:06 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Tue, 15 Aug 2006 14:34:06 +0200 Subject: Attention kernel module project packagers! Message-ID: <20060815123406.GG13461@neu.nirvana> Hi all, there is currently a discussion about replacing the current kernel module scheme ("kmod") with a new one ("kmdls"). This is because the current scheme has some unfixable flaws. The proposed new scheme is the one used at ATrpms, so if you ever used a kernel module package from there you know how it is setup. The kmdl approach has several nice features other than being resistant to the design issues of the current setup. * It is an interface/implementation design that can actually even be used for the current (broken) setup. The specfile remains invariant. * It uses one specfile/src.rpm for both userland and kernel modules, e.g. one set of sources/patches/changelogs/bugzilla entries/owners. * It is kernel and kernel-flavour agnostic, the same specfile/src.rpm can be used for any kernel/flavour combination, even for such that are yet to come. * Has full yum-support with a 99-line python plugin, works even w/o the plugin with a couple more keystrokes. * Is field-proven for several years and managed to never have to change the interface! More details are on http://fedoraproject.org/wiki/AxelThimm/kmdls It is important for FC6 and RHEL5 to make a decision on adopting it. Currently GFS is being packaged in the old scheme which is known to exhibit several flaws. An argument against adopting kmdls presented by Thorsten Leemhuis is that * it's too late now to fix it, we should live on with kmod bugs for RHEL5's life-cycle (ending 2012 ...) * too many packages for kmod are written (but actually there is only one in Fedora Extras 5, the rest is pending or in other repos and if other repos count, then ATrpms has several dozens of kmdls :) I think the flaws are severe enough to immediate block the current kmod standard especially it's propagation into RHEL. The wiki above shows that the design flaws propagate throughout any attemt to "fix" yum (note: yum is not broken, there the quotes in "fix") and finally end with the requirement that only one kernel can be supported in any point of time. This is neither acceptable by Fedora, and even less be RHEL. The number of packages following the kmod standard are quite few and I hope that the authors will not mind using the kmdl standard, but that's for you to say. Especially if you are a kernel module package author or want to become one: Please check the wiki and if you care about it join the discussion at fedora-packaging - reply-to set to that list, please don't scatter the discussion on fedora-extras and fedora-devel, I'm only calling for participation in the discussion to get this nailed once and for all. Thanks! -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Axel.Thimm at ATrpms.net Tue Aug 15 12:36:47 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Tue, 15 Aug 2006 14:36:47 +0200 Subject: Attention kernel module project packagers! In-Reply-To: <20060815123406.GG13461@neu.nirvana> References: <20060815123406.GG13461@neu.nirvana> Message-ID: <20060815123647.GH13461@neu.nirvana> On Tue, Aug 15, 2006 at 02:34:06PM +0200, Axel Thimm wrote: > Especially if you are a kernel module package author or want to become > one: Please check the wiki and if you care about it join the > discussion at fedora-packaging - reply-to set to that list, please > don't scatter the discussion on fedora-extras and fedora-devel, I'm > only calling for participation in the discussion to get this nailed > once and for all. Thanks! I messed up with fedora-packaging's mail address, it's fedora-packaging at redhat.com, not fedora-packaging-list at redhat.com So please fix it before replying :) -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dwmw2 at infradead.org Tue Aug 15 12:48:05 2006 From: dwmw2 at infradead.org (David Woodhouse) Date: Tue, 15 Aug 2006 13:48:05 +0100 Subject: Attention kernel module project packagers! In-Reply-To: <20060815123406.GG13461@neu.nirvana> References: <20060815123406.GG13461@neu.nirvana> Message-ID: <1155646085.22871.43.camel@pmac.infradead.org> On Tue, 2006-08-15 at 14:34 +0200, Axel Thimm wrote: > An argument against adopting kmdls presented by Thorsten Leemhuis is > that > > * it's too late now to fix it, we should live on with kmod bugs for > RHEL5's life-cycle (ending 2012 ...) > > * too many packages for kmod are written (but actually there is only one > in Fedora Extras 5, the rest is pending or in other repos and if > other repos count, then ATrpms has several dozens of kmdls :) I think this argument is invalid. We should ban _all_ module packages from Core and Extras anyway. -- dwmw2 From jwboyer at jdub.homelinux.org Tue Aug 15 12:51:48 2006 From: jwboyer at jdub.homelinux.org (Josh Boyer) Date: Tue, 15 Aug 2006 07:51:48 -0500 Subject: Attention kernel module project packagers! In-Reply-To: <20060815123406.GG13461@neu.nirvana> References: <20060815123406.GG13461@neu.nirvana> Message-ID: <1155646309.3004.2.camel@zod.rchland.ibm.com> On Tue, 2006-08-15 at 14:34 +0200, Axel Thimm wrote: > Hi all, > > there is currently a discussion about replacing the current kernel > module scheme ("kmod") with a new one ("kmdls"). This is because the > current scheme has some unfixable flaws. The proposed new scheme is > the one used at ATrpms, so if you ever used a kernel module package > from there you know how it is setup. > > The kmdl approach has several nice features other than being resistant > to the design issues of the current setup. > > * It is an interface/implementation design that can actually even be > used for the current (broken) setup. The specfile remains invariant. > > * It uses one specfile/src.rpm for both userland and kernel modules, > e.g. one set of sources/patches/changelogs/bugzilla entries/owners. > > * It is kernel and kernel-flavour agnostic, the same specfile/src.rpm > can be used for any kernel/flavour combination, even for such that > are yet to come. > > * Has full yum-support with a 99-line python plugin, works even w/o > the plugin with a couple more keystrokes. > > * Is field-proven for several years and managed to never have to > change the interface! > > More details are on http://fedoraproject.org/wiki/AxelThimm/kmdls > > It is important for FC6 and RHEL5 to make a decision on adopting > it. Currently GFS is being packaged in the old scheme which is known > to exhibit several flaws. > > An argument against adopting kmdls presented by Thorsten Leemhuis is > that > > * it's too late now to fix it, we should live on with kmod bugs for > RHEL5's life-cycle (ending 2012 ...) Fedora is _not_ RHEL. Period. If they happen to use the same packaging scheme for modules, fine. That doesn't mean that Fedora cannot change it's standards during a particular RHEL's lifetime. Therefore, I see no urgency in getting this changed. If kmdls is truly a better way, then it can be adapted when it has been fully discussed. josh From Axel.Thimm at ATrpms.net Tue Aug 15 12:56:13 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Tue, 15 Aug 2006 14:56:13 +0200 Subject: Attention kernel module project packagers! In-Reply-To: <1155646085.22871.43.camel@pmac.infradead.org> References: <20060815123406.GG13461@neu.nirvana> <1155646085.22871.43.camel@pmac.infradead.org> Message-ID: <20060815125613.GM13461@neu.nirvana> On Tue, Aug 15, 2006 at 01:48:05PM +0100, David Woodhouse wrote: > On Tue, 2006-08-15 at 14:34 +0200, Axel Thimm wrote: > > An argument against adopting kmdls presented by Thorsten Leemhuis is > > that > > > > * it's too late now to fix it, we should live on with kmod bugs for > > RHEL5's life-cycle (ending 2012 ...) > > > > * too many packages for kmod are written (but actually there is only one > > in Fedora Extras 5, the rest is pending or in other repos and if > > other repos count, then ATrpms has several dozens of kmdls :) > > I think this argument is invalid. We should ban _all_ module packages > from Core and Extras anyway. That's a valid viewpoint. Assuming Fedora Core/Extras indeed bans all external kernel module packages, does it have the authority/interest to maintain a kernel module packaging guide? If not who should? -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Axel.Thimm at ATrpms.net Tue Aug 15 13:02:54 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Tue, 15 Aug 2006 15:02:54 +0200 Subject: Attention kernel module project packagers! In-Reply-To: <1155646309.3004.2.camel@zod.rchland.ibm.com> References: <20060815123406.GG13461@neu.nirvana> <1155646309.3004.2.camel@zod.rchland.ibm.com> Message-ID: <20060815130254.GN13461@neu.nirvana> On Tue, Aug 15, 2006 at 07:51:48AM -0500, Josh Boyer wrote: > > An argument against adopting kmdls presented by Thorsten Leemhuis is > > that > > > > * it's too late now to fix it, we should live on with kmod bugs for > > RHEL5's life-cycle (ending 2012 ...) > > Fedora is _not_ RHEL. Period. If they happen to use the same packaging > scheme for modules, fine. That doesn't mean that Fedora cannot change > it's standards during a particular RHEL's lifetime. I agree that Fedora is not RHEL and vice versa. But once any idiom is adopted into one of the two the other will have a very hard time to get by, the bar is raised quite a bit. Whether we like it or not (BTW I like it) the two distributions are closely related and influence each-other. > Therefore, I see no urgency in getting this changed. If kmdls is truly > a better way, then it can be adapted when it has been fully discussed. GFS is in FC6, too. Only the life-span of FC6 is shorter. Furthermore yum developers want to know what scheme will need to be supported. As argued in the wiki yum support for the current scheme is an endless story, while the new proposed scheme already has it's fully working plugin submitted. Do you really want to see developers burn more time in a lost cause? We could be using that developer time elsewhere. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mjc at avtechpulse.com Tue Aug 15 13:21:19 2006 From: mjc at avtechpulse.com (Dr. Michael J. Chudobiak) Date: Tue, 15 Aug 2006 09:21:19 -0400 Subject: Attention kernel module project packagers! In-Reply-To: <20060815130254.GN13461@neu.nirvana> References: <20060815123406.GG13461@neu.nirvana> <1155646309.3004.2.camel@zod.rchland.ibm.com> <20060815130254.GN13461@neu.nirvana> Message-ID: <44E1CA4F.5080201@avtechpulse.com> Axel Thimm wrote: > argued in the wiki yum support for the current scheme is an endless > story, while the new proposed scheme already has it's fully working > plugin submitted. > > Do you really want to see developers burn more time in a lost cause? > We could be using that developer time elsewhere. Does your scheme prevent a new kernel from being installed if a matching kernel module is not yet available? - Mike From jkeating at redhat.com Tue Aug 15 13:27:34 2006 From: jkeating at redhat.com (Jesse Keating) Date: Tue, 15 Aug 2006 09:27:34 -0400 Subject: Attention kernel module project packagers! In-Reply-To: <1155646085.22871.43.camel@pmac.infradead.org> References: <20060815123406.GG13461@neu.nirvana> <1155646085.22871.43.camel@pmac.infradead.org> Message-ID: <200608150927.34829.jkeating@redhat.com> On Tuesday 15 August 2006 08:48, David Woodhouse wrote: > I think this argument is invalid. We should ban _all_ module packages > from Core and Extras anyway. I'm with David on this one. Packaging of modules is the path to insanity. It requires all kinds of weird hacks to how they are built, how they are named, how they are handled by rpm and depsolvers, they always lag, they always hold users behind when critical kernel fixes come out, etc, etc, etc... I personally feel (as does David) that if the module isn't good enough for upstream, then it would HAVE to live in the kernel package itself. If it's not good enough for the kernel package itself, then it isn't good enough for Fedora. (Same could be applied to RHEL, but that's a battle for a different list). Arguing over which ugly ass hack to apply to be able to package kernel modules is a bikeshed argument. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dwmw2 at infradead.org Tue Aug 15 13:40:23 2006 From: dwmw2 at infradead.org (David Woodhouse) Date: Tue, 15 Aug 2006 14:40:23 +0100 Subject: Attention kernel module project packagers! In-Reply-To: <200608150927.34829.jkeating@redhat.com> References: <20060815123406.GG13461@neu.nirvana> <1155646085.22871.43.camel@pmac.infradead.org> <200608150927.34829.jkeating@redhat.com> Message-ID: <1155649223.22871.54.camel@pmac.infradead.org> On Tue, 2006-08-15 at 09:27 -0400, Jesse Keating wrote: > Arguing over which ugly ass hack to apply to be able to package kernel modules > is a bikeshed argument. I'm not necessarily suggesting that we shouldn't have an agreed method of building kernel module packages at all -- just that we shouldn't have any such packages in Core or Extras. There _are_ relatively sane (and legal, unlike nvidia/ati stuff) cases where one might want to build a separate module -- like the NTFS modules in Livna, for example. And other 'new drivers' which aren't yet upstream. Of course you're right when you agree with me that those new drivers shouldn't be in Core or Extras -- but that doesn't mean we shouldn't provide a way to package them at all. So I think it _is_ worthwhile having the debate about how kernel module packages can be done -- I just don't think it's worth getting _particularly_ worked up about. -- dwmw2 From dwmw2 at infradead.org Tue Aug 15 13:49:17 2006 From: dwmw2 at infradead.org (David Woodhouse) Date: Tue, 15 Aug 2006 14:49:17 +0100 Subject: Attention kernel module project packagers! In-Reply-To: <20060815125613.GM13461@neu.nirvana> References: <20060815123406.GG13461@neu.nirvana> <1155646085.22871.43.camel@pmac.infradead.org> <20060815125613.GM13461@neu.nirvana> Message-ID: <1155649757.22871.62.camel@pmac.infradead.org> On Tue, 2006-08-15 at 14:56 +0200, Axel Thimm wrote: > > I think this argument is invalid. We should ban _all_ module packages > > from Core and Extras anyway. > > That's a valid viewpoint. Assuming Fedora Core/Extras indeed bans all > external kernel module packages, does it have the authority/interest > to maintain a kernel module packaging guide? If not who should? I think it's probably sane enough for Fedora to maintain a kernel module packaging guide, despite not actually having any such packages for itself. We understand and expect that there is an ecosystem of other repositories built around Fedora, and it makes sense to have guidelines (and infrastructure in our kernel packages, where appropriate) which make that easier. Especially when that'll be useful for RHEL too. -- dwmw2 From jkeating at redhat.com Tue Aug 15 13:50:00 2006 From: jkeating at redhat.com (Jesse Keating) Date: Tue, 15 Aug 2006 09:50:00 -0400 Subject: Attention kernel module project packagers! In-Reply-To: <1155649223.22871.54.camel@pmac.infradead.org> References: <20060815123406.GG13461@neu.nirvana> <200608150927.34829.jkeating@redhat.com> <1155649223.22871.54.camel@pmac.infradead.org> Message-ID: <200608150950.00442.jkeating@redhat.com> On Tuesday 15 August 2006 09:40, David Woodhouse wrote: > I'm not necessarily suggesting that we shouldn't have an agreed method > of building kernel module packages at all -- just that we shouldn't have > any such packages in Core or Extras. > > There _are_ relatively sane (and legal, unlike nvidia/ati stuff) cases > where one might want to build a separate module -- like the NTFS modules > in Livna, for example. And other 'new drivers' which aren't yet > upstream. Of course you're right when you agree with me that those new > drivers shouldn't be in Core or Extras -- but that doesn't mean we > shouldn't provide a way to package them at all. Given that we don't want it on Core or Extras, I'm pretty happy to let random 3rd party packager do whatever they want for packaging modules. I'm not interested in dictating how they should handle this ugly hack. Your example about ntfs is not usable w/out the userland (ntfsprogs), which nobody wants to touch due to legal reasons, and would be obsoleted by FUSE anyway where the most recent ntfs support is done entirely in userspace. There are many more things the packaging committee can spend time worrying about. Packaging of kernel modules isn't one of them IMHO. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dwmw2 at infradead.org Tue Aug 15 13:58:06 2006 From: dwmw2 at infradead.org (David Woodhouse) Date: Tue, 15 Aug 2006 14:58:06 +0100 Subject: Attention kernel module project packagers! In-Reply-To: <200608150950.00442.jkeating@redhat.com> References: <20060815123406.GG13461@neu.nirvana> <200608150927.34829.jkeating@redhat.com> <1155649223.22871.54.camel@pmac.infradead.org> <200608150950.00442.jkeating@redhat.com> Message-ID: <1155650286.22871.72.camel@pmac.infradead.org> On Tue, 2006-08-15 at 09:50 -0400, Jesse Keating wrote: > Given that we don't want it on Core or Extras, I'm pretty happy to let random > 3rd party packager do whatever they want for packaging modules. I'm not > interested in dictating how they should handle this ugly hack. > > Your example about ntfs is not usable w/out the userland (ntfsprogs), which > nobody wants to touch due to legal reasons, and would be obsoleted by FUSE > anyway where the most recent ntfs support is done entirely in userspace. > > There are many more things the packaging committee can spend time worrying > about. Packaging of kernel modules isn't one of them IMHO. Yeah, that's a fair point. However, it would be useful if those who _do_ care about kernel module packages would come to an agreement about how it should be done, and that can be documented somewhere central to Fedora -- like on the Fedora wiki. We can modify our kernel RPM and yum if appropriate in order to support that agreed method. But you're right; the packaging committee don't need to waste time on it. -- dwmw2 From fedora at leemhuis.info Tue Aug 15 14:12:06 2006 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Tue, 15 Aug 2006 16:12:06 +0200 Subject: Attention kernel module project packagers! In-Reply-To: <1155650286.22871.72.camel@pmac.infradead.org> References: <20060815123406.GG13461@neu.nirvana> <200608150927.34829.jkeating@redhat.com> <1155649223.22871.54.camel@pmac.infradead.org> <200608150950.00442.jkeating@redhat.com> <1155650286.22871.72.camel@pmac.infradead.org> Message-ID: <44E1D636.1000502@leemhuis.info> David Woodhouse schrieb: > On Tue, 2006-08-15 at 09:50 -0400, Jesse Keating wrote: >> Given that we don't want it on Core or Extras, I'm pretty happy to >> let random 3rd party packager do whatever they want for packaging >> modules. I'm not interested in dictating how they should handle >> this ugly hack. >> >> Your example about ntfs is not usable w/out the userland >> (ntfsprogs), which nobody wants to touch due to legal reasons, and >> would be obsoleted by FUSE anyway where the most recent ntfs >> support is done entirely in userspace. >> >> There are many more things the packaging committee can spend time >> worrying about. Packaging of kernel modules isn't one of them >> IMHO. > > Yeah, that's a fair point. However, it would be useful if those who > _do_ care about kernel module packages would come to an agreement > about how it should be done, and that can be documented somewhere > central to Fedora -- like on the Fedora wiki. > > We can modify our kernel RPM and yum if appropriate in order to > support that agreed method. That already happend -- FESCo worked out and agreed on a propsoal last winter http://www.fedoraproject.org/wiki/Packaging/KernelModules It's working fine. CU thl From Axel.Thimm at ATrpms.net Tue Aug 15 15:17:05 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Tue, 15 Aug 2006 17:17:05 +0200 Subject: Attention kernel module project packagers! In-Reply-To: <44E1D636.1000502@leemhuis.info> References: <20060815123406.GG13461@neu.nirvana> <200608150927.34829.jkeating@redhat.com> <1155649223.22871.54.camel@pmac.infradead.org> <200608150950.00442.jkeating@redhat.com> <1155650286.22871.72.camel@pmac.infradead.org> <44E1D636.1000502@leemhuis.info> Message-ID: <20060815151705.GP13461@neu.nirvana> On Tue, Aug 15, 2006 at 04:12:06PM +0200, Thorsten Leemhuis wrote: > > > David Woodhouse schrieb: > >On Tue, 2006-08-15 at 09:50 -0400, Jesse Keating wrote: > >>Given that we don't want it on Core or Extras, I'm pretty happy to > >>let random 3rd party packager do whatever they want for packaging > >>modules. I'm not interested in dictating how they should handle > >>this ugly hack. > >> > >>Your example about ntfs is not usable w/out the userland > >>(ntfsprogs), which nobody wants to touch due to legal reasons, and > >>would be obsoleted by FUSE anyway where the most recent ntfs > >>support is done entirely in userspace. > >> > >>There are many more things the packaging committee can spend time > >>worrying about. Packaging of kernel modules isn't one of them > >>IMHO. > > > >Yeah, that's a fair point. However, it would be useful if those who > >_do_ care about kernel module packages would come to an agreement > >about how it should be done, and that can be documented somewhere > >central to Fedora -- like on the Fedora wiki. > > > >We can modify our kernel RPM and yum if appropriate in order to > >support that agreed method. > > That already happend -- FESCo worked out and agreed on a propsoal last > winter http://www.fedoraproject.org/wiki/Packaging/KernelModules > > It's working fine. No, it's not, proven in debates on fedora-packaging and here http://fedoraproject.org/wiki/AxelThimm/kmdls The proposal you worked out is leading to broken rpm and yum support. That's not working fine. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From rdieter at math.unl.edu Tue Aug 15 15:38:14 2006 From: rdieter at math.unl.edu (Rex Dieter) Date: Tue, 15 Aug 2006 10:38:14 -0500 Subject: [Fedora-packaging] Re: Attention kernel module project packagers! In-Reply-To: <20060815151705.GP13461@neu.nirvana> References: <20060815123406.GG13461@neu.nirvana> <200608150927.34829.jkeating@redhat.com> <1155649223.22871.54.camel@pmac.infradead.org> <200608150950.00442.jkeating@redhat.com> <1155650286.22871.72.camel@pmac.infradead.org> <44E1D636.1000502@leemhuis.info> <20060815151705.GP13461@neu.nirvana> Message-ID: <44E1EA66.6040602@math.unl.edu> Axel Thimm wrote: > On Tue, Aug 15, 2006 at 04:12:06PM +0200, Thorsten Leemhuis wrote: >>> We can modify our kernel RPM and yum if appropriate in order to >>> support that agreed method. >> That already happend -- FESCo worked out and agreed on a propsoal last >> winter http://www.fedoraproject.org/wiki/Packaging/KernelModules >> It's working fine. > No, it's not... Thorsten, Axel, In the hopes of furthering the discussion can we at least agree that the current kmod scheme works, at least to some people's perception of what that means. I hope, also, that we can agree that the current kmod scheme does have limitations/shortcomings. With that in mind, I think this (should) all boil down to the question: which weighs more heavily in your mind, the pain/suffering(*) of involved in 1. Adopting/changing-to a new (kmdl) standard 2. living with the limitations/shortcomings that come with using kmod. ? (*) Which brought to my mind one of my favorite movie quotes: "Life is pain, Highness. Anyone who says differently is selling something." -- Rex From rhbugs at n-dimensional.de Tue Aug 15 15:44:12 2006 From: rhbugs at n-dimensional.de (Hans Ulrich Niedermann) Date: Tue, 15 Aug 2006 17:44:12 +0200 Subject: .Q: Best Practice for dir owneership In-Reply-To: <0MKwh2-1GCN2Y07lX-0004ZF@mrelayeu.kundenserver.de> References: <0MKwh2-1GCN2Y07lX-0004ZF@mrelayeu.kundenserver.de> Message-ID: <1155656652.3102.41.camel@mir> On Sun, 2006-08-13 at 22:58 +0200, Jochen Schmitt wrote: > I have a special problem with a package which I have submitted > for review at BZ #174021. This package contains two subpackages > with fonts. the first subpackage conatins trutype fonts which > should installed at %{_datadir}/fonts/apl/TrueType. The second > conains classic X11 bitmap fonts which shluld installed on > %{_datadir}/fonts/apl/pcf. In comment #28 there was a suggestion > to put the X11 fonts to %{_datadir}/X11/fonts/apl but I think > only the core fonts on the X11 system should put into > %{_datadir}/X11/fonts, so I want to keep the X11 fonts into > %{_datadir}/fonts/apl/pcf. Having only X11 core packages messing around with %{_anydir}/X11 makes sense to me. > Now there is the directory %{_datadir]/fonts/apl which is not > owned by any package. You package is named "aplus-fsf". I suppose the "apl" in that directory name stands for "aplus"? IMHO abbreviating package name does not make much sense here. IMHO, the cleanest solution in the absence of any official policy is to have the package %{name} with the fonts depend on the fontconfig package which owns the %{_datadir}/fonts directory and then install a directory %{_datadir}/fonts/%{name} owned by the %{name} package. The scriptlets of the %{name} package will then call fc-cache for scalable fonts to register them with fontconfig. For non-fontconfig programs (such as xfontsel, xterm, etc.), AFAICT you need to call mkfontdir (from the xorg-x11-font-utils package) and chkfontpath (from the chkfontpath package) to register the bitmap fonts with the X11 fontserver. At least that is what I had to do to get my terminus package (#202356) to work with xterm. > My question now, what is the best practice to solve this problem. Non-representative examination of existing packages: The bitstream-vera-fonts package installs all its fonts in %{_datadir}/fonts/bitstream-vera and then calls fc-cache. The bitmap-fonts package installs all its fonts in %{_datadir}/fonts/bitmap-fonts and then calls fc-cache. The gnome-print package just drops a bunch of .afm files into %{_datadir}/fonts/afms/adobe/ without any package owning the "afms" or "adobe" directories and calls /usr/bin/redhat-update-gnome-font-install. So I'd say that owning and installing into %{_datadir}/fonts/%{name} is a safe bet. Gru?, Uli From jkeating at redhat.com Tue Aug 15 16:11:35 2006 From: jkeating at redhat.com (Jesse Keating) Date: Tue, 15 Aug 2006 12:11:35 -0400 Subject: [Fedora-packaging] Re: Attention kernel module project packagers! In-Reply-To: <44E1EA66.6040602@math.unl.edu> References: <20060815123406.GG13461@neu.nirvana> <20060815151705.GP13461@neu.nirvana> <44E1EA66.6040602@math.unl.edu> Message-ID: <200608151211.41301.jkeating@redhat.com> On Tuesday 15 August 2006 11:38, Rex Dieter wrote: > With that in mind, I think this (should) all boil down to the question: > which weighs more heavily in your mind, the pain/suffering(*) of involved > in 1. ?Adopting/changing-to a new (kmdl) standard > 2. ?living with the limitations/shortcomings that come with using kmod. > ? 3. Kicking kernel module packages out of Core / Extras and moving the debate away from us so that we can focus on the more important things. I vote for #3. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dwmw2 at infradead.org Tue Aug 15 16:13:59 2006 From: dwmw2 at infradead.org (David Woodhouse) Date: Tue, 15 Aug 2006 17:13:59 +0100 Subject: [Fedora-packaging] Re: Attention kernel module project packagers! In-Reply-To: <200608151211.41301.jkeating@redhat.com> References: <20060815123406.GG13461@neu.nirvana> <20060815151705.GP13461@neu.nirvana> <44E1EA66.6040602@math.unl.edu> <200608151211.41301.jkeating@redhat.com> Message-ID: <1155658439.22871.99.camel@pmac.infradead.org> On Tue, 2006-08-15 at 12:11 -0400, Jesse Keating wrote: > 3. Kicking kernel module packages out of Core / Extras and moving the debate > away from us so that we can focus on the more important things. I vote for > #3. As do I. -- dwmw2 From bugzilla at redhat.com Tue Aug 15 16:40:13 2006 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 15 Aug 2006 12:40:13 -0400 Subject: [Bug 177247] Review Request: jthread In-Reply-To: Message-ID: <200608151640.k7FGeDSE019464@bugzilla.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: jthread https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177247 bugzilla at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC|fedora-extras- | |list at redhat.com | CC| |fedora-package- | |review at redhat.com CC|fedora-package- | |review at redhat.com | CC| |fedora-extras- | |list at redhat.com -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. From jkeating at redhat.com Tue Aug 15 17:33:07 2006 From: jkeating at redhat.com (Jesse Keating) Date: Tue, 15 Aug 2006 13:33:07 -0400 Subject: Attention kernel module project packagers! In-Reply-To: References: <20060815123406.GG13461@neu.nirvana> <44E1EA66.6040602@math.unl.edu> Message-ID: <200608151333.07641.jkeating@redhat.com> On Tuesday 15 August 2006 13:28, Benny Amorsen wrote: > Would the same problems that we have with kernel modules appear with > e.g. apache modules, if having two different apache versions installed > was possible? Theoretically yes, however thankfully we don't really let two different apaches be installed. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From manuel at todo-linux.com Tue Aug 15 18:41:30 2006 From: manuel at todo-linux.com (Manuel Arostegui Ramirez) Date: Tue, 15 Aug 2006 20:41:30 +0200 Subject: [Bug 201149] Review Request: -Sponsor needed Message-ID: <200608152041.30216.manuel@todo-linux.com> Hi gurus. Last 3 August I submitted as a new package: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201149 Same day, Bill Nottigam move it from devel to Extras. Since that day no one have pick it up to review, just John Patrick (thank you very much, John) who reported some corrections to the spec file. >From cherokee proyect are really looking forward to include Cherokee on Fedora Core Extras, we are working very hard to bring near RPM packages to everyone. The reason I'm sending this mail is because of I need an Sponsor could who point me how to made Cherokee an official package of Fedora Core Extras Hope someone could sponsor this package, I'll be really grateful. I'm also testing some packages which are on the bug list, avaiable at:https://bugzilla.redhat.com/bugzilla/buglist.cgi?regetlastlist=1 marked as NEW in order to help as possible as I can on the reviews of that packages. Thanks in advance. -- Manuel Arostegui Ramirez. Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues. From Axel.Thimm at ATrpms.net Tue Aug 15 18:50:10 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Tue, 15 Aug 2006 20:50:10 +0200 Subject: Attention kernel module project packagers! In-Reply-To: <44E1CA4F.5080201@avtechpulse.com> References: <20060815123406.GG13461@neu.nirvana> <1155646309.3004.2.camel@zod.rchland.ibm.com> <20060815130254.GN13461@neu.nirvana> <44E1CA4F.5080201@avtechpulse.com> Message-ID: <20060815185010.GG31789@neu.nirvana> On Tue, Aug 15, 2006 at 09:21:19AM -0400, Dr. Michael J. Chudobiak wrote: > Axel Thimm wrote: > >argued in the wiki yum support for the current scheme is an endless > >story, while the new proposed scheme already has it's fully working > >plugin submitted. > > > >Do you really want to see developers burn more time in a lost cause? > >We could be using that developer time elsewhere. > > > Does your scheme prevent a new kernel from being installed if a matching > kernel module is not yet available? That's not a scheme's purpose, that's more a depsolver's mechanics. In this point both old and new schemes are the same. Concerning the plugins Jack Neely who writes the one for kmods has added some pinning support like you describe. The plugin I wrote for kmdls does not block kernel upgrades, but instead installs kmdls for that kernel as they become available. The reason is that perhaps a kmdl has been swallowed into the kernel (or superseeded by the kernel's version), in this case it would block th upgrade forever. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From tibbs at math.uh.edu Tue Aug 15 19:21:04 2006 From: tibbs at math.uh.edu (Jason L Tibbitts III) Date: Tue, 15 Aug 2006 14:21:04 -0500 Subject: [Bug 201149] Review Request: -Sponsor needed In-Reply-To: <200608152041.30216.manuel@todo-linux.com> (Manuel Arostegui Ramirez's message of "Tue, 15 Aug 2006 20:41:30 +0200") References: <200608152041.30216.manuel@todo-linux.com> Message-ID: >>>>> "MAR" == Manuel Arostegui Ramirez writes: MAR> The reason I'm sending this mail is because of I MAR> need an Sponsor could who point me how to made Cherokee an MAR> official package of Fedora Core Extras First off, you didn't block FE-NEEDSPONSOR so nobody would know that you need sponsorship. I've done that for you. Now, have you read http://fedoraproject.org/wiki/Extras/HowToGetSponsored ? If you want to speed the process, go ahead and help out with those other reviews you mentioned and then add a comment with the bug numbers to the Cherokee review ticket so that the sponsors will have an easier time finding the other work you're doing. Finally, it looks like you neglected to send new files when you made your fixes to the package. It's not a good idea to update the existing package and spec in place when you make changes; instead, bump the version and put out a new package. That way it's obvious for reviewers to know if they have the latest version. - J< From nando at ccrma.Stanford.EDU Tue Aug 15 19:57:13 2006 From: nando at ccrma.Stanford.EDU (Fernando Lopez-Lezcano) Date: Tue, 15 Aug 2006 12:57:13 -0700 Subject: Attention kernel module project packagers! In-Reply-To: <200608150927.34829.jkeating@redhat.com> References: <20060815123406.GG13461@neu.nirvana> <1155646085.22871.43.camel@pmac.infradead.org> <200608150927.34829.jkeating@redhat.com> Message-ID: <1155671833.19797.41.camel@cmn3.stanford.edu> On Tue, 2006-08-15 at 09:27 -0400, Jesse Keating wrote: > On Tuesday 15 August 2006 08:48, David Woodhouse wrote: > > I think this argument is invalid. We should ban _all_ module packages > > from Core and Extras anyway. > > I'm with David on this one. Packaging of modules is the path to insanity. It > requires all kinds of weird hacks to how they are built, how they are named, > how they are handled by rpm and depsolvers, they always lag, they always hold > users behind when critical kernel fixes come out, etc, etc, etc... Sorry. No. Not "always". Always is _always_ too strong a word, oh well, perhaps not? :-) ;-) :-) ALSA: I've been packaging ALSA kernel modules for years for the Planet CCRMA project (since 2001). Bumped my head against many walls in the process. Examined kernel packaging proposals that sounded fine till you used them and found they did _not_ work. I packaged kernel modules first out of necessity because the kernel did not include ALSA at all. Then also out of necessity to get newer versions of the ALSA kernel modules than the ones in the standard kernel tree - or modules for soundcards that have not made it to the kernel tree yet but are usable (and no, waiting for them to make it to the standard tree is not always an option). I'm not arguing for or against including kernel modules in extra or core or rhel or whatever - but there should be a solid guideline on how to package them that works. With proper support in resolvers, kernel infrastructure, etc[*]. If the current one has flaws (it does!) then let's fix them. The need exists, it is part of reality, denying reality will not make it dissappear (that's at least my experience over the years). I'm still using in Planet CCRMA a scheme similar to the one proposed. It works. -- Fernando [*] even support for the kernel itself has problems - if I have a kernel that is version-release older than the latest kernel I _can not_ install it using an unpatched yum. > I personally feel (as does David) that if the module isn't good enough for > upstream, then it would HAVE to live in the kernel package itself. If it's > not good enough for the kernel package itself, then it isn't good enough for > Fedora. (Same could be applied to RHEL, but that's a battle for a different > list). > > Arguing over which ugly ass hack to apply to be able to package kernel modules > is a bikeshed argument. From benny+usenet at amorsen.dk Tue Aug 15 17:28:31 2006 From: benny+usenet at amorsen.dk (Benny Amorsen) Date: 15 Aug 2006 19:28:31 +0200 Subject: Attention kernel module project packagers! References: <20060815123406.GG13461@neu.nirvana> <200608150927.34829.jkeating@redhat.com> <1155649223.22871.54.camel@pmac.infradead.org> <200608150950.00442.jkeating@redhat.com> <1155650286.22871.72.camel@pmac.infradead.org> <44E1D636.1000502@leemhuis.info> <20060815151705.GP13461@neu.nirvana> <44E1EA66.6040602@math.unl.edu> Message-ID: >>>>> "RD" == Rex Dieter writes: RD> In the hopes of furthering the discussion can we at least agree RD> that the current kmod scheme works, at least to some people's RD> perception of what that means. I hope, also, that we can agree RD> that the current kmod scheme does have limitations/shortcomings. RD> With that in mind, I think this (should) all boil down to the RD> question: which weighs more heavily in your mind, the RD> pain/suffering(*) of involved in 1. Adopting/changing-to a new RD> (kmdl) standard 2. living with the limitations/shortcomings that RD> come with using kmod. ? Would the same problems that we have with kernel modules appear with e.g. apache modules, if having two different apache versions installed was possible? /Benny From Christian.Iseli at licr.org Tue Aug 15 23:22:34 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Wed, 16 Aug 2006 01:22:34 +0200 Subject: FE Package Status of Aug 15, 2006 Message-ID: <20060816012234.50122944@ludwig-alpha> Hi folks, Here comes this week's report. I've tried to further trim the list of missing packages in comps.xml by looking at owners.list. Packages with this RE (binding|library|module|utilit) in their short description are excluded. I've updated the comps wiki page: http://fedoraproject.org/wiki/Extras/CompsXml I'll start sending nagmails RSN... Cheers, Christian P.S. I'll be on vacations next week. I hope Michael K. will update the status page. I sure won't :-) ---- FE Package Status of Aug 15, 2006 The full report can be found here: http://fedoraproject.org/wiki/Extras/PackageStatus Owners file stats: - 2097 packages - 38 orphans - 27 packages not available in extras devel or release Fedora at FamilleCollet dot com php-pecl-zip Fedora at FamilleCollet dot com php-pear-HTTP cgoorah at yahoo dot com dot au kadischi davidhart at tqmcube dot com leafnode dennis at ausil dot us oooqs2 fedora at theholbrooks dot org php-shout fredrik at dolda2000 dot com icmpdn ghenry at suretecsystems dot com gnome-applet-netmon ifoox at redhat dot com ht2html ivazquez at ivazquez dot net gpredict jpo at di dot uminho dot pt perl-Test-Builder-Tester matthias at rpmforge dot net fillets-ng-data-cs notting at redhat dot com comps oliver at linux-kernel dot at squidGuard pertusus at free dot fr tetex-elsevier splinux at fedoraproject dot org gstm tcallawa at redhat dot com perl-Maypole tcallawa at redhat dot com R-RScaLAPACK tcallawa at redhat dot com comical tcallawa at redhat dot com libgdamm tcallawa at redhat dot com R-hdf5 tcallawa at redhat dot com opendap toniw at iki dot fi silky toniw at iki dot fi libmatchbox toshio at tiki-lounge dot com hula triad at df dot lth dot se gnome-phone-manager wtogami at redhat dot com iiimf-le-simplehangul - 4 packages not available in extras devel but present in release ivazquez at ivazquez dot net gnome-applet-rhythmbox paul at xtdnet dot nl s3switch ville dot skytta at iki dot fi em8300-kmod ville dot skytta at iki dot fi em8300 - 1 packages which have not yet been FE-APPROVE'd... https://bugzilla.redhat.com/bugzilla/buglist.cgi?bug_id=189375 Maelstrom notting at redhat.com - 3 packages present in the development repo which have no owners entry BackupPC dates ip6sic - 2 orphaned packages, yet available in extras devel dxpc gtkglarea2 - 45 packages that moved to core Packages appearing both in Core and Extras: - 5 packages duplicated for devel: jpo at di dot uminho dot pt perl-Net-SSLeay jpo at di dot uminho dot pt perl-IO-Socket-SSL jpo at di dot uminho dot pt perl-Socket6 petersen at redhat dot com scim-bridge tagoh at redhat dot com paps FE-ACCEPT packages stats: - 1147 accepted, closed package reviews - 4 accepted, closed package reviews not in repo - 1 accepted, closed package reviews not in owners - 9 accepted, open package reviews older than 4 weeks; - 8 accepted, open package reviews with a package already in the repo FE-REVIEW packages stats: - 120 open tickets - 22 tickets with no activity in eight weeks - 21 tickets with no activity in four weeks - 3 closed tickets FE-NEW packages stats: - 178 open tickets - 24 tickets with no activity in eight weeks - 37 tickets with no activity in four weeks FE-NEEDSPONSOR packages stats: - 47 open tickets - 5 tickets with no activity in eight weeks - 9 tickets with no activity in four weeks FE-LEGAL packages stats: - 2 open tickets - 1 tickets with no activity in four weeks FE-GUIDELINES packages stats: - 12 open tickets - 11 tickets with no activity in four weeks OPEN-BUGS packages stats: - 248 open tickets - 140 tickets with no activity in eight weeks - 42 tickets with no activity in four weeks CVS stats: - 2071 packages with a devel directory - 7 packages with no owners entry BackupPC dates initng ip6sic muse php-apc zoo - 4 packages in CVS devel *and* Core dogtail libevent pam_pkcs11 pyspi - 110 packages were dropped from extras Maintainers stats: - 218 maintainers - 20 inactive maintainers with open bugs - 22 inactive maintainers Dropped FC packages: - 270 packages were dropped from core since FC 1 Comps.xml files stats: - 463 packages in comps-fe6 file - 590 packages missing from comps-fe6 file - 23 packages in comps-fe6 but not in repo - 461 packages in comps-fe5 file - 576 packages missing from comps-fe5 file - 19 packages in comps-fe5 but not in repo From michael at knox.net.nz Tue Aug 15 23:30:48 2006 From: michael at knox.net.nz (Michael J. Knox) Date: Wed, 16 Aug 2006 11:30:48 +1200 (NZST) Subject: FE Package Status of Aug 15, 2006 In-Reply-To: <20060816012234.50122944@ludwig-alpha> References: <20060816012234.50122944@ludwig-alpha> Message-ID: <3385.203.118.135.21.1155684648.squirrel@www.knox.net.nz> Christian Iseli wrote: > P.S. > I'll be on vacations next week. I hope Michael K. will update the > status page. I sure won't :-) I hope so too... lack of internet is killing me. Webmail is all I have from work atm :-( Michael From michael at knox.net.nz Tue Aug 15 23:31:55 2006 From: michael at knox.net.nz (Michael J. Knox) Date: Wed, 16 Aug 2006 11:31:55 +1200 (NZST) Subject: Anyone want pyzor? In-Reply-To: References: <44DB6809.201@redhat.com> <29348.203.118.135.21.1155240571.squirrel@www.knox.net.nz> <44DF8537.4050802@redhat.com> Message-ID: <4587.203.118.135.21.1155684715.squirrel@www.knox.net.nz> Andreas Thienemann wrote: > On Sun, 13 Aug 2006, Warren Togami wrote: > >> How about this, assign primary ownership to Andreas and you can >> coordinate on >> joint ownership. I trust that most of the cvsextras members would do >> the >> right thing. > sounds okay to me. I haven't fiddled yet with joint ownership, but no > problem there. > There's a first time for everything. > > Michael, you okay with that? Hey Andreas, Sure, I am cool with that. Michael From Christian.Iseli at licr.org Wed Aug 16 00:28:00 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Wed, 16 Aug 2006 02:28:00 +0200 Subject: FE Package Status of Aug 15, 2006 In-Reply-To: <3385.203.118.135.21.1155684648.squirrel@www.knox.net.nz> References: <20060816012234.50122944@ludwig-alpha> <3385.203.118.135.21.1155684648.squirrel@www.knox.net.nz> Message-ID: <20060816022800.01839466@ludwig-alpha> On Wed, 16 Aug 2006 11:30:48 +1200 (NZST), Michael J. Knox wrote: > I hope so too... lack of internet is killing me. Webmail is all I have > from work atm :-( I can feel your pain... the nagmails have been sent (all 162 of them) Let's see what happens. Cheers, Christian From wart at kobold.org Wed Aug 16 01:23:50 2006 From: wart at kobold.org (Wart) Date: Tue, 15 Aug 2006 18:23:50 -0700 Subject: Packages missing in comps-feX.xml.in In-Reply-To: <20060816021729.1834e0eb@ludwig-alpha> References: <20060816021729.1834e0eb@ludwig-alpha> Message-ID: <44E273A6.2040002@kobold.org> Christian Iseli wrote: > Hi, > > You own the following packages which are not listed in comps-fe6.xml.in > Please have a look at http://fedoraproject.org/wiki/Extras/CompsXml and > consider adding them > > Thanks, > Christian (c4chris) > > ---- > crossfire > prboom These are game servers, not client applications. I guess they could still go in the 'games' category, along with xpilot-ng-server and wesnoth-server. > deutex > yadex I'm not sure where these should go. They are DOOM game level editors. deutex is a command line tool, while yadex is a graphical editing app. They could fit in either the 'games' or 'graphics' group. Any suggestions on which would be better? --Wart From jkeating at redhat.com Wed Aug 16 02:20:21 2006 From: jkeating at redhat.com (Jesse Keating) Date: Tue, 15 Aug 2006 22:20:21 -0400 Subject: Packages missing in comps-feX.xml.in In-Reply-To: <44E273A6.2040002@kobold.org> References: <20060816021729.1834e0eb@ludwig-alpha> <44E273A6.2040002@kobold.org> Message-ID: <200608152220.22118.jkeating@redhat.com> On Tuesday 15 August 2006 21:23, Wart wrote: > I'm not sure where these should go. ?They are DOOM game level editors. > deutex is a command line tool, while yadex is a graphical editing app. > They could fit in either the 'games' or 'graphics' group. ?Any > suggestions on which would be better? Perhaps a Game Development group? -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jpmahowald at gmail.com Wed Aug 16 03:40:58 2006 From: jpmahowald at gmail.com (John Mahowald) Date: Tue, 15 Aug 2006 22:40:58 -0500 Subject: Python submodule naming In-Reply-To: <20060721185504.GA4410@crow.rdu.redhat.com> References: <20060721185504.GA4410@crow.rdu.redhat.com> Message-ID: <3ea997540608152040w62e0ab9cv8a34fc8520c76e32@mail.gmail.com> On 7/21/06, Luke Macken wrote: > I'm currently working on getting Paste{,Deploy,Script} though the review > process, and Patrice Dumas asks a good naming question in the bug[0]: > > I don't know if the name should be python-paste-deploy or > python-pastedeploy. The guidelines don't cover the case of python > submodules. If it is "This makes a package name format of python-$NAME" > it seems to be python-pastedeploy, but if one follow "use the name of the > module that you type to import it in a script" it should be > python-paste-deploy. The second naming convention is also consistent > with perl modules naming. > > Anyone have any insight into this ? > > luke > > [0]: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198288#c2 > > FYI, Debian seems to go the second route without the second dash. I'm inclined to go along. http://packages.debian.org/unstable/python/python-pastescript John From Matt_Domsch at dell.com Wed Aug 16 04:09:54 2006 From: Matt_Domsch at dell.com (Matt Domsch) Date: Tue, 15 Aug 2006 23:09:54 -0500 Subject: Extras x86_64 rawhide rebuild in mock status 2006-08-15 Message-ID: <20060815230954.A15575@humbolt.us.dell.com> Extras Rawhide-in-Mock Build Results for x86_64 Tue Aug 15 22:59:22 CDT 2006 Note: This is using a reduced set of packages in the build chroot as compared to the standard Fedora Extras build system before FC6test1. See http://fedoraproject.org/wiki/QA/FixBuildRequires for more information, including the list of packages removed from the default build chroot. Open Bugs which now build, and can be marked CLOSED RAWHIDE: argus-2.0.6.fixes.1-11.fc6 197215 NEW bidiv-1.5-3.fc5 197224 NEW flow-tools-0.68-10.fc6 197706 NEW gtktalog 198897 NEW libtomoe-gtk-0.1.0-6.fc6 200114 NEW Number failed to build: 90 Number expected to fail due to ExclusiveArch or ExcludeArch: 23 Leaving: 67 (there may be some duplicates if rawhide has 2 versions of a package) Of those expected to have worked... Without a bug filed: 49 ---------------------------------- atitvout-0.4-5 andreas.bierfert at lowlatency.de boo-0.7.6.2237-8.fc6 paul at all-the-johnsons.co.uk camstream-0.26.3-9.fc5 nomis80 at nomis80.org contact-lookup-applet-0.14-3.fc6 bdpepple at ameritech.net directfb-0.9.24-5.fc5 thomas at apestaart.org ebtables-2.0.8-0.5.rc1.fc6 tcallawa at redhat.com epiphany-extensions-2.14.1-1 caillon at redhat.com foobillard-3.0a-4 mitr at redhat.com gif2png-2.5.1-2.fc5 enrico.scholz at informatik.tu-chemnitz.de gobby-0.4.0-6.rc2.fc6 lmacken at redhat.com gstreamer08-python-0.8.4-1.fc5 thomas at apestaart.org gtk2hs-0.9.10-2.fc6 petersen at redhat.com GtkAda-2.4.0-11.fc5 gemi at bluewin.ch gtksourceview-sharp-2.0-15.fc6 paul at all-the-johnsons.co.uk ifplugd-0.24-6 aaron.bennett at olin.edu john-1.6-4 ghenry at suretecsystems.com kmymoney2-0.8.4-1.fc6 rdieter at math.unl.edu ladspa-1.12-5 thomas at apestaart.org libpolyxmass-0.9.0-6.fc5 andreas.bierfert at lowlatency.de MagicPoint-1.11b-2.fc5 byte at fedoraproject.org mlton-20051202-8.fc6 adam at spicenitz.org monodevelop-0.11-16.fc6 paul at all-the-johnsons.co.uk nautilus-open-terminal-0.7-1.fc6 stickster at gmail.com new-1.3.7-2 redhat at flyn.org pam_keyring-0.0.7-2 redhat at flyn.org php-pear-DB-1.7.6-6 rpm at timj.co.uk pl-5.6.16-1.fc6 gemi at bluewin.ch python-goopy-0.1-1 pjones at redhat.com python-reportlab-1.20-5.fc5 bdpepple at ameritech.net python-TestGears-0.2-1.fc5 ivazquez at ivazquez.net quarry-0.1.16-2.fc5 michel.salim at gmail.com rpmDirectoryCheck-0.8-2 enrico.scholz at informatik.tu-chemnitz.de scanssh-2.1-6.fc5 oliver at linux-kernel.at SDL_ttf-2.0.7-4.fc5 bdpepple at ameritech.net ser-0.9.6-7.fc6 andreas at bawue.net serpentine-0.7-3.fc6 foolish at guezz.net stratagus-2.1-5.fc6 lemenkov at newmail.ru synce-0.9.1-7.fc5 andreas.bierfert at lowlatency.de synce-software-manager-0.9.0-5.fc5 andreas.bierfert at lowlatency.de synce-trayicon-0.9.0-6.fc5 andreas.bierfert at lowlatency.de WindowMaker-0.92.0-8.fc5 andreas.bierfert at lowlatency.de wlassistant-0.5.5-1.fc5 tcallawa at redhat.com wv2-0.2.3-1.fc6 andreas.bierfert at lowlatency.de xaos-3.2.1-3.fc6 gemi at bluewin.ch xbsql-0.11-6.fc6 tcallawa at redhat.com xcin-2.5.3.pre3-27 llch at redhat.com xplanet-1.0.1-7 jylitalo at iki.fi xprobe2-0.3-5.fc5 lmacken at redhat.com xsupplicant-1.2.6-1.fc6 tcallawa at redhat.com With bugs filed: 18 ---------------------------------- alacarte-0.8-7.fc5 ['194250 NEW'] jpmahowald at gmail.com banshee-0.10.11-1.fc6 ['194505 NEW'] caillon at redhat.com cowbell-0.2.7.1-2.fc6 ['197366 CLOSED'] foolish at guezz.net dillo-0.8.6-2.fc6 ['197370 CLOSED'] andreas.bierfert at lowlatency.de gdesklets-0.35.3-8.fc6 ['197799 NEW'] luya_tfz at thefinalzone.com gnome-applet-music-0.9.0-1.fc6 ['197924 NEW'] ivazquez at ivazquez.net gnome-schedule-1.0.0-1 ['197927 NEW'] frank at scirocco-5v-turbo.de grhino-0.15.0-5.fc5 ['197950 NEW'] michel.salim at gmail.com jam-2.5-3.fc5 ['198924 NEW'] tcallawa at redhat.com leafpad-0.8.9-1.fc6 ['200088 NEW'] ivazquez at ivazquez.net libtabe-0.2.6-14 ['200104 NEW'] llch at redhat.com logjam-4.5.3-4.fc6 ['200387 NEW'] tcallawa at redhat.com multisync-0.90.18-5.fc5 ['200399 ASSIGNED'] andreas.bierfert at lowlatency.de nautilus-search-tool-0.2-1.fc5 ['200420 NEW'] ivazquez at ivazquez.net nco-3.1.2-1.fc6 ['193541 NEW'] ed at eh3.com NetworkManager-vpnc-0.7.0-0.cvs20060529.1.fc6 ['200424 NEW'] davidz at redhat.com ngrep-1.44-4.fc5 ['200429 NEW'] oliver at linux-kernel.at opencv-0.9.7-15.fc5 ['200788 NEW'] nomis80 at nomis80.org Full logs at http://linux.dell.com/files/fedora/FixBuildRequires/ -- Matt Domsch Software Architect Dell Linux Solutions linux.dell.com & www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com From Matt_Domsch at dell.com Wed Aug 16 04:10:07 2006 From: Matt_Domsch at dell.com (Matt Domsch) Date: Tue, 15 Aug 2006 23:10:07 -0500 Subject: Extras i386 rawhide rebuild in mock status 2006-08-15 Message-ID: <20060815231007.A15589@humbolt.us.dell.com> Extras Rawhide-in-Mock Build Results for i386 Tue Aug 15 23:03:35 CDT 2006 Note: This is using a reduced set of packages in the build chroot as compared to the standard Fedora Extras build system before FC6test1. See http://fedoraproject.org/wiki/QA/FixBuildRequires for more information, including the list of packages removed from the default build chroot. Open Bugs which now build, and can be marked CLOSED RAWHIDE: argus-2.0.6.fixes.1-11.fc6 197215 NEW bidiv-1.5-3.fc5 197224 NEW flow-tools-0.68-10.fc6 197706 NEW gtktalog 198897 NEW libtomoe-gtk-0.1.0-6.fc6 200114 NEW Number failed to build: 68 Number expected to fail due to ExclusiveArch or ExcludeArch: 1 Leaving: 67 (there may be some duplicates if rawhide has 2 versions of a package) Of those expected to have worked... Without a bug filed: 47 ---------------------------------- boo-0.7.6.2237-8.fc6 paul at all-the-johnsons.co.uk camstream-0.26.3-9.fc5 nomis80 at nomis80.org contact-lookup-applet-0.14-3.fc6 bdpepple at ameritech.net directfb-0.9.24-5.fc5 thomas at apestaart.org ebtables-2.0.8-0.5.rc1.fc6 tcallawa at redhat.com epiphany-extensions-2.14.1-1 caillon at redhat.com gif2png-2.5.1-2.fc5 enrico.scholz at informatik.tu-chemnitz.de gobby-0.4.0-6.rc2.fc6 lmacken at redhat.com gstreamer08-python-0.8.4-1.fc5 thomas at apestaart.org gtk2hs-0.9.10-2.fc6 petersen at redhat.com GtkAda-2.4.0-11.fc5 gemi at bluewin.ch gtksourceview-sharp-2.0-15.fc6 paul at all-the-johnsons.co.uk ifplugd-0.24-6 aaron.bennett at olin.edu john-1.6-4 ghenry at suretecsystems.com kmymoney2-0.8.4-1.fc6 rdieter at math.unl.edu ktorrent-2.0-4.fc6 wolters.liste at gmx.net ladspa-1.12-5 thomas at apestaart.org MagicPoint-1.11b-2.fc5 byte at fedoraproject.org mfstools-2.0-9.snapshot050221.fc5 tcallawa at redhat.com monodevelop-0.11-16.fc6 paul at all-the-johnsons.co.uk nautilus-open-terminal-0.7-1.fc6 stickster at gmail.com orange-0.3-1.cvs20051118.fc6 andreas.bierfert at lowlatency.de pam_keyring-0.0.7-2 redhat at flyn.org perl-POE-Component-Client-HTTP-0.77-2.fc6 cweyl at alumni.drew.edu pl-5.6.16-1.fc6 gemi at bluewin.ch python-goopy-0.1-1 pjones at redhat.com python-TestGears-0.2-1.fc5 ivazquez at ivazquez.net quarry-0.1.16-2.fc5 michel.salim at gmail.com rpmDirectoryCheck-0.8-2 enrico.scholz at informatik.tu-chemnitz.de scanssh-2.1-6.fc5 oliver at linux-kernel.at SDL_ttf-2.0.7-4.fc5 bdpepple at ameritech.net ser-0.9.6-7.fc6 andreas at bawue.net serpentine-0.7-3.fc6 foolish at guezz.net stratagus-2.1-5.fc6 lemenkov at newmail.ru syck-0.55-7.fc5 oliver at linux-kernel.at synce-0.9.1-7.fc5 andreas.bierfert at lowlatency.de synce-software-manager-0.9.0-5.fc5 andreas.bierfert at lowlatency.de synce-trayicon-0.9.0-6.fc5 andreas.bierfert at lowlatency.de WindowMaker-0.92.0-8.fc5 andreas.bierfert at lowlatency.de wlassistant-0.5.5-1.fc5 tcallawa at redhat.com wv2-0.2.3-1.fc6 andreas.bierfert at lowlatency.de xaos-3.2.1-3.fc6 gemi at bluewin.ch xbsql-0.11-6.fc6 tcallawa at redhat.com xcin-2.5.3.pre3-27 llch at redhat.com xplanet-1.0.1-7 jylitalo at iki.fi xprobe2-0.3-5.fc5 lmacken at redhat.com xsupplicant-1.2.6-1.fc6 tcallawa at redhat.com With bugs filed: 20 ---------------------------------- alacarte-0.8-7.fc5 ['194250 NEW'] jpmahowald at gmail.com amaya-9.5-1.fc6 ['195652 NEW'] paul at all-the-johnsons.co.uk banshee-0.10.11-1.fc6 ['194505 NEW'] caillon at redhat.com cowbell-0.2.7.1-2.fc6 ['197366 CLOSED'] foolish at guezz.net dillo-0.8.6-2.fc6 ['197370 CLOSED'] andreas.bierfert at lowlatency.de gdesklets-0.35.3-8.fc6 ['197799 NEW'] luya_tfz at thefinalzone.com gnome-applet-music-0.9.0-1.fc6 ['197924 NEW'] ivazquez at ivazquez.net gnome-schedule-1.0.0-1 ['197927 NEW'] frank at scirocco-5v-turbo.de grhino-0.15.0-5.fc5 ['197950 NEW'] michel.salim at gmail.com jam-2.5-3.fc5 ['198924 NEW'] tcallawa at redhat.com leafpad-0.8.9-1.fc6 ['200088 NEW'] ivazquez at ivazquez.net librx-1.5-6.fc5 ['200090 NEW'] tcallawa at redhat.com libtabe-0.2.6-14 ['200104 NEW'] llch at redhat.com logjam-4.5.3-4.fc6 ['200387 NEW'] tcallawa at redhat.com multisync-0.90.18-5.fc5 ['200399 ASSIGNED'] andreas.bierfert at lowlatency.de nautilus-search-tool-0.2-1.fc5 ['200420 NEW'] ivazquez at ivazquez.net nco-3.1.2-1.fc6 ['193541 NEW'] ed at eh3.com NetworkManager-vpnc-0.7.0-0.cvs20060529.1.fc6 ['200424 NEW'] davidz at redhat.com ngrep-1.44-4.fc5 ['200429 NEW'] oliver at linux-kernel.at opencv-0.9.7-15.fc5 ['200788 NEW'] nomis80 at nomis80.org Full logs at http://linux.dell.com/files/fedora/FixBuildRequires/ -- Matt Domsch Software Architect Dell Linux Solutions linux.dell.com & www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com From peter at thecodergeek.com Wed Aug 16 04:33:25 2006 From: peter at thecodergeek.com (Peter Gordon) Date: Tue, 15 Aug 2006 21:33:25 -0700 Subject: comps comps-fe6.xml,1.4,1.5 In-Reply-To: <200608160208.k7G28bKx002902@cvs-int.fedora.redhat.com> References: <200608160208.k7G28bKx002902@cvs-int.fedora.redhat.com> Message-ID: <44E2A015.7050703@thecodergeek.com> Jeff Layton (jlayton) wrote: > Author: jlayton > > Update of /cvs/extras/comps > In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2885 > > Modified Files: > comps-fe6.xml > Log Message: > Added ez-ipupdate and xwrits Bad Jeff! No cookie! :P You're supposed to update the .xml.in files instead. The .xml files are automagically regenerated from those. -- Peter Gordon (codergeek42) GnuPG Public Key ID: 0xFFC19479 / Fingerprint: DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479 My Blog: http://thecodergeek.com/blog/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From j.w.r.degoede at hhs.nl Wed Aug 16 04:34:19 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Wed, 16 Aug 2006 06:34:19 +0200 Subject: Ok to change description in owners.list Message-ID: <44E2A04B.5060404@hhs.nl> Hi all, 2 questions: 1) Must the description in owners.list exactly match the rpm summary? 2) May the descriotion be changed after the initial adding of a package to owners.list? I'm asking because I would like to change the description of a few libraries I maintain to include the word library (but only in onwers.list, not in the rpms) to stop Chris's comps nag mails from nagging me :) Regards, Hans From chris.stone at gmail.com Wed Aug 16 05:20:29 2006 From: chris.stone at gmail.com (Christopher Stone) Date: Tue, 15 Aug 2006 22:20:29 -0700 Subject: Ok to change description in owners.list In-Reply-To: <44E2A04B.5060404@hhs.nl> References: <44E2A04B.5060404@hhs.nl> Message-ID: On 8/15/06, Hans de Goede wrote: > Hi all, > > 2 questions: > > 1) Must the description in owners.list exactly match the rpm summary? > 2) May the descriotion be changed after the initial adding of a package > to owners.list? > > I'm asking because I would like to change the description of a few > libraries I maintain to include the word library (but only in > onwers.list, not in the rpms) to stop Chris's comps nag mails from > nagging me :) 1) No. If it changes, just what is going to break? Nothing. Therefore it can be different. I think the descriptions are only used in the bugzilla page (AFAIK). 2) Yes. If it changes, just what is going to break? Nothing... etc blah blah Anyway, this e-mail it seems is more to do with Chris' comps email nags than owner list changes. Parsing the owners list for the word library seems like an *extremely* unreliable way to filter out libraries. Perhaps he should look at an rpms group tag, or if there is a devel subpackage for the rpm instead. Anyway, I wouldn't bother changing owner descriptions just to work-around Chris' email nag software. Instead Chris needs to come up with a better filtering algorithm. From chris.stone at gmail.com Wed Aug 16 05:50:40 2006 From: chris.stone at gmail.com (Christopher Stone) Date: Tue, 15 Aug 2006 22:50:40 -0700 Subject: Packages missing in comps-feX.xml.in In-Reply-To: <200608152220.22118.jkeating@redhat.com> References: <20060816021729.1834e0eb@ludwig-alpha> <44E273A6.2040002@kobold.org> <200608152220.22118.jkeating@redhat.com> Message-ID: On 8/15/06, Jesse Keating wrote: > On Tuesday 15 August 2006 21:23, Wart wrote: > > I'm not sure where these should go. They are DOOM game level editors. > > deutex is a command line tool, while yadex is a graphical editing app. > > They could fit in either the 'games' or 'graphics' group. Any > > suggestions on which would be better? Since everyone is talking about groups, I have a few questions: 1) Why are rpm groups different than comps groups? 2) How come comps doesn't have Development/Libraries? 3) Where on the wiki page can I find definitions of all the comps/rpm groups? 4) What are you supposed to do if your software falls into multiple group categories? List it twice? Pick a category and list it once? 5) What if your software doesnt fall into any defined category? Do you create your own comps group or rpm group? For example, numpy is classified as "Development/Languages" in rpm, and "Applications/Engineering and Scientific" in comps. But isn't numpy used primarily as a library for other python applications such as pygame? Wouldn't it be better classified as "Development/Libraries"? It is a library just like a C library, only it's for python. So therefore the rpm group changes from "Development/Libraries" to "Development/Languages" simply because it's written in python and not C? And isn't comps' "Applications/Engineering and Scientific" meant for end-user applications and not libararies? Oh god I'm so confused. :-| For me, this whole grouping of software seems very complicated and confusing. Is there any hope of standardizing this stuff? Maybe a whole new paradigm of software grouping needs to be invented. For example a set of flags which define the software such as language, usage, category, etc. From chabotc at xs4all.nl Wed Aug 16 05:52:18 2006 From: chabotc at xs4all.nl (Chris Chabot) Date: Wed, 16 Aug 2006 07:52:18 +0200 Subject: [Fwd: Packages missing in comps-feX.xml.in] Message-ID: <44E2B292.9020205@xs4all.nl> Hmmm where to put php-pecl-apc .. its an addon (byte code cache) for php, so it doesn't really fit well under 'web servers', and i saw there's no php packages included in the comps at all yet Maybe a Web Server addons, or a php group would be in order? -- Chris -------------- next part -------------- An embedded message was scrubbed... From: Christian Iseli Subject: Packages missing in comps-feX.xml.in Date: Wed Aug 16 02:17:26 2006 +0200 Size: 1677 URL: From wart at kobold.org Wed Aug 16 06:36:16 2006 From: wart at kobold.org (Wart) Date: Tue, 15 Aug 2006 23:36:16 -0700 Subject: Ok to change description in owners.list In-Reply-To: <44E2A04B.5060404@hhs.nl> References: <44E2A04B.5060404@hhs.nl> Message-ID: <44E2BCE0.6040906@kobold.org> Hans de Goede wrote: > Hi all, > > 2 questions: > > 1) Must the description in owners.list exactly match the rpm summary? > 2) May the descriotion be changed after the initial adding of a package > to owners.list? AFAIK, there is no rule that says the description in owners.list must match the Summary: in the spec file. I know for a fact that a handful of my own packages don't match (because I was too lazy to open up the spec file when I was adding them to owners.list). > I'm asking because I would like to change the description of a few > libraries I maintain to include the word library (but only in > onwers.list, not in the rpms) to stop Chris's comps nag mails from > nagging me :) I wouldn't bother unless you are extremely bored, or really bothered by the nag mails. :) --Mike From frank-buettner at gmx.net Wed Aug 16 06:45:23 2006 From: frank-buettner at gmx.net (=?ISO-8859-1?Q?Frank_B=FCttner?=) Date: Wed, 16 Aug 2006 08:45:23 +0200 Subject: FE Package Status of Aug 15, 2006 In-Reply-To: <20060816012234.50122944@ludwig-alpha> References: <20060816012234.50122944@ludwig-alpha> Message-ID: <44E2BF03.2080703@gmx.net> Christian Iseli schrieb: > Hi folks, > > Here comes this week's report. I've tried to further trim the list of > missing packages in comps.xml by looking at owners.list. Packages > with this RE (binding|library|module|utilit) in their short description > are excluded. > > I've updated the comps wiki page: > http://fedoraproject.org/wiki/Extras/CompsXml > > I'll start sending nagmails RSN... > > Cheers, > Christian > > P.S. > I'll be on vacations next week. I hope Michael K. will update the > status page. I sure won't :-) > > ---- > > FE Package Status of Aug 15, 2006 > > The full report can be found here: > http://fedoraproject.org/wiki/Extras/PackageStatus Witch group is better for my nas (Network Audio System) network-server or ound-and-video? Frank -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 4285 bytes Desc: S/MIME Cryptographic Signature URL: From ryo-dairiki at users.sourceforge.net Wed Aug 16 08:02:27 2006 From: ryo-dairiki at users.sourceforge.net (Ryo Dairiki) Date: Wed, 16 Aug 2006 17:02:27 +0900 Subject: New category needed for compsXML: i18n Message-ID: <44E2D113.1060409@users.sourceforge.net> Hi, I'm thinking of writing compsXML for SCIM related packages, and I need a new category like "I18n" or "Internationalization" for them. Where can I request it? Or just posting here is enough? Regards, Ryo Dairiki From denis at poolshark.org Wed Aug 16 09:42:13 2006 From: denis at poolshark.org (Denis Leroy) Date: Wed, 16 Aug 2006 11:42:13 +0200 Subject: FE Package Status of Aug 15, 2006 In-Reply-To: <20060816012234.50122944@ludwig-alpha> References: <20060816012234.50122944@ludwig-alpha> Message-ID: <44E2E875.4050900@poolshark.org> erbatiChristian Iseli wrote: > Hi folks, > > Here comes this week's report. I've tried to further trim the list of > missing packages in comps.xml by looking at owners.list. Packages > with this RE (binding|library|module|utilit) in their short description > are excluded. I'm not a huge fan of this exclusion mechanism, it is approximate and yields lots of false positives (both ways). As a result, people are confused as to what should or should not go into the comps file, and the overall value of comps is reduced. Worse, people will start writing artifical package descriptions to make sure they include one of those words. Also, the wiki states that the comps file should only include packages that make sense for a user to include, i.e. a graphical application. Yet the comps file seems to include a lot more than that already, command-line-only utilities, devel packages. There needs to be at least a robust way to exclude packages from the comps categorization, whether that's an extra entry in the owner file, or preferrably an actual file checked into the module directory ? -denis From pertusus at free.fr Wed Aug 16 10:24:57 2006 From: pertusus at free.fr (Patrice Dumas) Date: Wed, 16 Aug 2006 12:24:57 +0200 Subject: Packages missing in comps-feX.xml.in In-Reply-To: References: <20060816021729.1834e0eb@ludwig-alpha> <44E273A6.2040002@kobold.org> <200608152220.22118.jkeating@redhat.com> Message-ID: <20060816102457.GB2768@free.fr> rpm groups and comps groups are unrelated. rpm groups are amost unusefull and not used, while comps groups are important. > 3) Where on the wiki page can I find definitions of all the comps/rpm > groups? The comps groups are defined within the comps file (it may be nice to have an automatically formatted page summarizing category/definition somewhere, though). > 4) What are you supposed to do if your software falls into multiple > group categories? List it twice? Pick a category and list it once? List it once. > 5) What if your software doesnt fall into any defined category? Do > you create your own comps group or rpm group? > > For example, numpy is classified as "Development/Languages" in rpm, > and "Applications/Engineering and Scientific" in comps. But isn't > numpy used primarily as a library for other python applications such > as pygame? Wouldn't it be better classified as numpy is in 'Engineering and Scientific' in comps because it is where it is used for himself. > "Applications/Engineering and Scientific" meant for end-user > applications and not libararies? Oh god I'm so confused. :-| The end user depends on the category being considered. For scientists and engineers libraries that bay be used for themselves (like lapack, numpy and so on) should be in comps. Similarly, 'Development Tools' and development sections are for developpers, so it makes sense to have command line apps in this category. Lastly 'System Tools' and 'Hardware Support', and the servers are primarily for system administrators so it make sense to have command-line apps in it (most servers are command-line apps, indeed...). -- Pat From pertusus at free.fr Wed Aug 16 10:27:03 2006 From: pertusus at free.fr (Patrice Dumas) Date: Wed, 16 Aug 2006 12:27:03 +0200 Subject: [Fwd: Packages missing in comps-feX.xml.in] In-Reply-To: <44E2B292.9020205@xs4all.nl> References: <44E2B292.9020205@xs4all.nl> Message-ID: <20060816102703.GC2768@free.fr> On Wed, Aug 16, 2006 at 07:52:18AM +0200, Chris Chabot wrote: > Hmmm where to put php-pecl-apc .. its an addon (byte code cache) for > php, so it doesn't really fit well under 'web servers', and i saw > there's no php packages included in the comps at all yet Is it really necessary to have php-pecl-apc in comps at all? -- Pat From pertusus at free.fr Wed Aug 16 10:29:41 2006 From: pertusus at free.fr (Patrice Dumas) Date: Wed, 16 Aug 2006 12:29:41 +0200 Subject: New category needed for compsXML: i18n In-Reply-To: <44E2D113.1060409@users.sourceforge.net> References: <44E2D113.1060409@users.sourceforge.net> Message-ID: <20060816102940.GD2768@free.fr> On Wed, Aug 16, 2006 at 05:02:27PM +0900, Ryo Dairiki wrote: > Hi, > I'm thinking of writing compsXML for SCIM related packages, > and I need a new category like "I18n" or "Internationalization" for them. > Where can I request it? Or just posting here is enough? I am fairly ignorant on that subject, but aren't I18n related packages like libraries, and pulled as dependencies by the apps that use them? Are they of use by themselves? -- Pat From andy at smile.org.ua Wed Aug 16 11:00:19 2006 From: andy at smile.org.ua (Andy Shevchenko) Date: Wed, 16 Aug 2006 14:00:19 +0300 Subject: FE Package Status of Aug 15, 2006 In-Reply-To: <44E2BF03.2080703@gmx.net> References: <20060816012234.50122944@ludwig-alpha> <44E2BF03.2080703@gmx.net> Message-ID: <44E2FAC3.6000106@smile.org.ua> Frank B?ttner wrote: > Witch group is better for my nas (Network Audio System) network-server > or ound-and-video? I've put jack-audio-connection-kit to sound-and-video group. I think nas wold be at the same group. In first it a sound server. -- With best regards, Andy Shevchenko. mailto: andy at smile.org.ua From mr.ecik at gmail.com Wed Aug 16 11:13:18 2006 From: mr.ecik at gmail.com (=?ISO-8859-2?Q?Micha=B3_Bentkowski?=) Date: Wed, 16 Aug 2006 13:13:18 +0200 Subject: CompsXml and python modules Message-ID: <668bb39a0608160413v16658d89v5f12a5fa5848ccee@mail.gmail.com> Hi! Recently, I receive mail about adding my packages to comps file. But I'm owner ot two packages: kadu and python-mutagen, that mail says only about the first one. When I've taken a look on comps-fe6.xml.in, I saw that there are no python packages. I'm not sure if python modules owners haven't been added by their owners yet, or we are simple not allowed to add them modules. Could somebody explain me it? Micha? From ryo-dairiki at users.sourceforge.net Wed Aug 16 14:44:57 2006 From: ryo-dairiki at users.sourceforge.net (Ryo Dairiki) Date: Wed, 16 Aug 2006 23:44:57 +0900 Subject: New category needed for compsXML: i18n In-Reply-To: <20060816102940.GD2768@free.fr> References: <44E2D113.1060409@users.sourceforge.net> <20060816102940.GD2768@free.fr> Message-ID: <44E32F69.3040400@users.sourceforge.net> Patrice Dumas wrote: > On Wed, Aug 16, 2006 at 05:02:27PM +0900, Ryo Dairiki wrote: > >> Hi, >> I'm thinking of writing compsXML for SCIM related packages, >> and I need a new category like "I18n" or "Internationalization" for them. >> Where can I request it? Or just posting here is enough? >> > > I am fairly ignorant on that subject, but aren't I18n related packages > like libraries, and pulled as dependencies by the apps that use them? > Are they of use by themselves? > > -- > Pat > Not, really. There are some extra packages in that category. For example, special input methods, and special composing dictionaries. I own "scim-skk", which is yet another input method for Japanese. As you know, the default input method for Japanese in Fedora is "scim-anthy", which is installed by dependencies on Japanese environments. But there are some people who prefer scim-skk to scim-anthy. For such people, scim-skk must shown in the list of apps to install. Just installed by dependencies is not a good idea. Ryo Dairiki From laurent.rineau__fedora_extras at normalesup.org Wed Aug 16 15:04:05 2006 From: laurent.rineau__fedora_extras at normalesup.org (Laurent Rineau) Date: Wed, 16 Aug 2006 17:04:05 +0200 Subject: Packages missing in comps-feX.xml.in In-Reply-To: <20060816021728.95dfae1b@ludwig-alpha> References: <20060816021728.95dfae1b@ludwig-alpha> Message-ID: <200608161704.05039@rineau.schtroumpfette> On Wednesday 16 August 2006 04:17, you wrote: > Hi, > > You own the following packages which are not listed in comps-fe6.xml.in > Please have a look at http://fedoraproject.org/wiki/Extras/CompsXml and > consider adding them > par2cmdline I do not know where to put par2cmdline. I do not see any group about backups, archiving tools, and so one. From j.w.r.degoede at hhs.nl Wed Aug 16 15:18:51 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Wed, 16 Aug 2006 17:18:51 +0200 Subject: New category needed for compsXML: i18n In-Reply-To: <44E32F69.3040400@users.sourceforge.net> References: <44E2D113.1060409@users.sourceforge.net> <20060816102940.GD2768@free.fr> <44E32F69.3040400@users.sourceforge.net> Message-ID: <44E3375B.5050507@hhs.nl> Ryo Dairiki wrote: > Patrice Dumas wrote: >> On Wed, Aug 16, 2006 at 05:02:27PM +0900, Ryo Dairiki wrote: >> >>> Hi, >>> I'm thinking of writing compsXML for SCIM related packages, >>> and I need a new category like "I18n" or "Internationalization" for >>> them. >>> Where can I request it? Or just posting here is enough? >>> >> >> I am fairly ignorant on that subject, but aren't I18n related packages >> like libraries, and pulled as dependencies by the apps that use them? >> Are they of use by themselves? >> >> -- >> Pat >> > > Not, really. > > There are some extra packages in that category. > For example, special input methods, and special composing dictionaries. > > I own "scim-skk", which is yet another input method for Japanese. > As you know, the default input method for Japanese in Fedora is > "scim-anthy", > which is installed by dependencies on Japanese environments. > But there are some people who prefer scim-skk to scim-anthy. > For such people, scim-skk must shown in the list of apps to install. > Just installed by dependencies is not a good idea. > > Ryo Dairiki > I could use such a catagory too (I think) gcompris comes with many subpackages which contain spoken sound in different languages. I've been reluctant to add all the gcompris-sounds-xx packages too comps because I don't want to polute the education comps group with those, but I do feel they should be in comps so users can install them without using the commandline, any other suggestions for this problem are welcome. Regards, Hans From ad+lists at uni-x.org Wed Aug 16 15:38:03 2006 From: ad+lists at uni-x.org (Alexander Dalloz) Date: Wed, 16 Aug 2006 17:38:03 +0200 Subject: comps-fe[56].xml id mail-server doubled Message-ID: <44E33BDB.2070406@uni-x.org> Hi, a few minutes ago I checked out comps from CVS and found in the xml(.in) files for both branches that mail-server is listed twice, though small difference in the description (feel "SMTP mail server" is the correct string rather than naming Postfix explicitly). "clamav" is listed in both sections. $ grep -n "mail-server" -A15 comps-fe6.xml.in 428: mail-server 429- <_name>Mail Server 430- <_description>These packages allow you to configure an IMAP or Postfix mail server. 431- false 432- true 433- 434- cyrus-imapd 435- enemies-of-carlotta 436- perl-Cyrus 437- clamav 438- clamav-data 439- clamav-milter 440- esmtp 441- exim 442- exim-doc 443- mlmmj -- 788: mail-server 789- <_name>Mail Server 790- <_description>These packages allow you to configure an IMAP or SMTP mail server. 791- false 792- true 793- 794- amavisd-new 795- clamav 796- 797- [ ... ] Guess that should be corrected. Alexander From dan at danny.cz Wed Aug 16 15:53:00 2006 From: dan at danny.cz (Dan =?ISO-8859-1?Q?Hor=E1k?=) Date: Wed, 16 Aug 2006 17:53:00 +0200 Subject: comps.xml and subpackages Message-ID: <1155743580.3495.5.camel@eagle.danny.cz> Hello, what should be written into comps.xml.in - only the main package or package + all subpackages? Dan From Christian.Iseli at licr.org Wed Aug 16 16:40:12 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Wed, 16 Aug 2006 18:40:12 +0200 Subject: comps comps-fe6.xml.in,1.72,1.73 In-Reply-To: <200608161616.k7GGGcZ5014226@cvs-int.fedora.redhat.com> References: <200608161616.k7GGGcZ5014226@cvs-int.fedora.redhat.com> Message-ID: <20060816184012.0c6906cc@ludwig-alpha> Hi Paul, On Wed, 16 Aug 2006 09:16:36 -0700, Paul Howarth wrote: > - ushare > - torque-server Was this intentional ? Christian From paul at city-fan.org Wed Aug 16 16:57:08 2006 From: paul at city-fan.org (Paul Howarth) Date: Wed, 16 Aug 2006 17:57:08 +0100 Subject: comps comps-fe6.xml.in,1.72,1.73 In-Reply-To: <20060816184012.0c6906cc@ludwig-alpha> References: <200608161616.k7GGGcZ5014226@cvs-int.fedora.redhat.com> <20060816184012.0c6906cc@ludwig-alpha> Message-ID: <44E34E64.2060808@city-fan.org> Christian Iseli wrote: > Hi Paul, > > On Wed, 16 Aug 2006 09:16:36 -0700, Paul Howarth wrote: >> - ushare >> - torque-server > > Was this intentional ? Yes. You missed this bit later on: > + torque-server > + ushare I was fixing the sort order. Paul. From katzj at redhat.com Wed Aug 16 17:42:01 2006 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 16 Aug 2006 13:42:01 -0400 Subject: New category needed for compsXML: i18n In-Reply-To: <44E32F69.3040400@users.sourceforge.net> References: <44E2D113.1060409@users.sourceforge.net> <20060816102940.GD2768@free.fr> <44E32F69.3040400@users.sourceforge.net> Message-ID: <1155750121.5006.14.camel@orodruin.boston.redhat.com> On Wed, 2006-08-16 at 23:44 +0900, Ryo Dairiki wrote: > Patrice Dumas wrote: > > On Wed, Aug 16, 2006 at 05:02:27PM +0900, Ryo Dairiki wrote: > >> I'm thinking of writing compsXML for SCIM related packages, > >> and I need a new category like "I18n" or "Internationalization" for them. > >> Where can I request it? Or just posting here is enough? > >> > > > > I am fairly ignorant on that subject, but aren't I18n related packages > > like libraries, and pulled as dependencies by the apps that use them? > > Are they of use by themselves? > > Not, really. > > There are some extra packages in that category. > For example, special input methods, and special composing dictionaries. > > I own "scim-skk", which is yet another input method for Japanese. > As you know, the default input method for Japanese in Fedora is > "scim-anthy", > which is installed by dependencies on Japanese environments. > But there are some people who prefer scim-skk to scim-anthy. > For such people, scim-skk must shown in the list of apps to install. > Just installed by dependencies is not a good idea. There are groups for language support groups that this would be fine for adding to Jeremy From jkeating at redhat.com Wed Aug 16 18:22:54 2006 From: jkeating at redhat.com (Jesse Keating) Date: Wed, 16 Aug 2006 14:22:54 -0400 Subject: comps.xml and subpackages In-Reply-To: <1155743580.3495.5.camel@eagle.danny.cz> References: <1155743580.3495.5.camel@eagle.danny.cz> Message-ID: <200608161422.54330.jkeating@redhat.com> On Wednesday 16 August 2006 11:53, Dan Hor?k wrote: > what should be written into comps.xml.in - only the main package or > package + all subpackages? Usually you list the top level package. Say you want widget. You list widget, but not all the deps that widget may have. Or if you have package widget, which has widget-devel widget-gui and widget-common, you might put widget-devel in a development group, widget-gui in a X Desktop group, and maybe widget in whatever group it belongs in depending on what it does. -common will probably be a dep of every other widget package (same with widget package itself) so no matter where the user selects, they would end up getting part or all of the subpackages of widget. Clear as mud? -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dan at danny.cz Wed Aug 16 18:36:22 2006 From: dan at danny.cz (Dan =?ISO-8859-1?Q?Hor=E1k?=) Date: Wed, 16 Aug 2006 20:36:22 +0200 Subject: comps.xml and subpackages In-Reply-To: <200608161422.54330.jkeating@redhat.com> References: <1155743580.3495.5.camel@eagle.danny.cz> <200608161422.54330.jkeating@redhat.com> Message-ID: <1155753382.3495.8.camel@eagle.danny.cz> Jesse Keating p??e v St 16. 08. 2006 v 14:22 -0400: > On Wednesday 16 August 2006 11:53, Dan Hor?k wrote: > > what should be written into comps.xml.in - only the main package or > > package + all subpackages? > > Usually you list the top level package. Say you want widget. You list > widget, but not all the deps that widget may have. > > Or if you have package widget, which has widget-devel widget-gui and > widget-common, you might put widget-devel in a development group, widget-gui > in a X Desktop group, and maybe widget in whatever group it belongs in > depending on what it does. -common will probably be a dep of every other > widget package (same with widget package itself) so no matter where the user > selects, they would end up getting part or all of the subpackages of widget. > > Clear as mud? > Sure, looks logical :-) Dan From toshio at tiki-lounge.com Wed Aug 16 19:12:57 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Wed, 16 Aug 2006 12:12:57 -0700 Subject: [Fwd: Packages missing in comps-feX.xml.in] In-Reply-To: <20060816102703.GC2768@free.fr> References: <44E2B292.9020205@xs4all.nl> <20060816102703.GC2768@free.fr> Message-ID: <1155755577.2662.69.camel@localhost> On Wed, 2006-08-16 at 12:27 +0200, Patrice Dumas wrote: > On Wed, Aug 16, 2006 at 07:52:18AM +0200, Chris Chabot wrote: > > Hmmm where to put php-pecl-apc .. its an addon (byte code cache) for > > php, so it doesn't really fit well under 'web servers', and i saw > > there's no php packages included in the comps at all yet > > Is it really necessary to have php-pecl-apc in comps at all? It's a toplevel package, isn't it? In other words, nothing depends on it so if it's not selected by the user from comps, it won't get installed? -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From toshio at tiki-lounge.com Wed Aug 16 19:25:52 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Wed, 16 Aug 2006 12:25:52 -0700 Subject: Packages missing in comps-feX.xml.in In-Reply-To: <200608161704.05039@rineau.schtroumpfette> References: <20060816021728.95dfae1b@ludwig-alpha> <200608161704.05039@rineau.schtroumpfette> Message-ID: <1155756352.2662.74.camel@localhost> On Wed, 2006-08-16 at 17:04 +0200, Laurent Rineau wrote: > > par2cmdline > > I do not know where to put par2cmdline. I do not see any group about backups, > archiving tools, and so one. > rdiff-backup is in system-tools. You could also check Core's comps file and see where amanda is. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Christian.Iseli at licr.org Wed Aug 16 20:18:34 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Wed, 16 Aug 2006 22:18:34 +0200 Subject: comps comps-fe6.xml.in,1.72,1.73 In-Reply-To: <44E34E64.2060808@city-fan.org> References: <200608161616.k7GGGcZ5014226@cvs-int.fedora.redhat.com> <20060816184012.0c6906cc@ludwig-alpha> <44E34E64.2060808@city-fan.org> Message-ID: <20060816221834.0625c46e@ludwig-alpha> On Wed, 16 Aug 2006 17:57:08 +0100, Paul Howarth wrote: > I was fixing the sort order. Ah, darn. I keep doing that :-( (second time in a week I think) Sorry, Christian From chabotc at xs4all.nl Wed Aug 16 21:00:02 2006 From: chabotc at xs4all.nl (Chris Chabot) Date: Wed, 16 Aug 2006 23:00:02 +0200 Subject: [Fwd: Packages missing in comps-feX.xml.in] In-Reply-To: <1155755577.2662.69.camel@localhost> References: <44E2B292.9020205@xs4all.nl> <20060816102703.GC2768@free.fr> <1155755577.2662.69.camel@localhost> Message-ID: <44E38752.6010006@xs4all.nl> Yep top level package (aka nothing depends on it), and for people running php it can have huge benifits. Many other such packages such as php-Smarty, php-json, php-pecl-mailparse etc that are very usefull to people who use php .. so why not include them in the comps? -- Chris Toshio Kuratomi wrote: > On Wed, 2006-08-16 at 12:27 +0200, Patrice Dumas wrote: > >> On Wed, Aug 16, 2006 at 07:52:18AM +0200, Chris Chabot wrote: >> >>> Hmmm where to put php-pecl-apc .. its an addon (byte code cache) for >>> php, so it doesn't really fit well under 'web servers', and i saw >>> there's no php packages included in the comps at all yet >>> >> Is it really necessary to have php-pecl-apc in comps at all? >> > > It's a toplevel package, isn't it? In other words, nothing depends on > it so if it's not selected by the user from comps, it won't get > installed? > > -Toshio > -------------- next part -------------- An HTML attachment was scrubbed... URL: From packages at amiga-hardware.com Wed Aug 16 22:30:27 2006 From: packages at amiga-hardware.com (Ian Chapman) Date: Wed, 16 Aug 2006 23:30:27 +0100 Subject: openmxs. cbios Message-ID: <44E39C83.5080909@amiga-hardware.com> Hi, Would the following be unsuitable for inclusion in FE because of patent issues or other legal complexities? http://openmsx.sourceforge.net/ An MSX Emulator released under GPL http://cbios.sourceforge.net/ A third party MSX BIOS released under BSD license. -- Ian Chapman. From Christian.Iseli at licr.org Wed Aug 16 23:06:01 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Thu, 17 Aug 2006 01:06:01 +0200 Subject: Packages missing in comps-feX.xml.in In-Reply-To: <200608161704.05039@rineau.schtroumpfette> References: <20060816021728.95dfae1b@ludwig-alpha> <200608161704.05039@rineau.schtroumpfette> Message-ID: <20060817010601.235b8e66@ludwig-alpha> On Wed, 16 Aug 2006 17:04:05 +0200, Laurent Rineau wrote: > I do not know where to put par2cmdline. I do not see any group about backups, > archiving tools, and so one. Looks like you found a spot... :-) Bonnes salutations, Christian From kevin.kofler at chello.at Wed Aug 16 23:12:27 2006 From: kevin.kofler at chello.at (Kevin Kofler) Date: Wed, 16 Aug 2006 23:12:27 +0000 (UTC) Subject: Packages missing in comps-feX.xml.in References: <20060816021729.1834e0eb@ludwig-alpha> <44E273A6.2040002@kobold.org> <200608152220.22118.jkeating@redhat.com> <20060816102457.GB2768@free.fr> Message-ID: Patrice Dumas writes: > rpm groups and comps groups are unrelated. rpm groups are amost unusefull > and not used, while comps groups are important. They are used by Synaptic: the group filters use RPM groups, not comps groups. You also notice typoed or otherwise weird (where my definition of "weird" is "used only by exactly one package" ;-), and inconsistent with other groups too (e.g. "System" instead of "System/Something" or "Something/System")) groups that way. Should I file bugs against the offending packages? Kevin Kofler From laurent.rineau__fedora_extras at normalesup.org Wed Aug 16 23:18:37 2006 From: laurent.rineau__fedora_extras at normalesup.org (Laurent Rineau) Date: Thu, 17 Aug 2006 01:18:37 +0200 Subject: Packages missing in comps-feX.xml.in In-Reply-To: <20060817010601.235b8e66@ludwig-alpha> References: <20060816021728.95dfae1b@ludwig-alpha> <200608161704.05039@rineau.schtroumpfette> <20060817010601.235b8e66@ludwig-alpha> Message-ID: <200608170118.37566@rineau.schtroumpfette> On Thursday 17 August 2006 01:06, Christian Iseli wrote: > On Wed, 16 Aug 2006 17:04:05 +0200, Laurent Rineau wrote: > > I do not know where to put par2cmdline. I do not see any group about > > backups, archiving tools, and so one. > > Looks like you found a spot... I am not real conviced that system-tools is the right group for par2cmdline. As a first approximation, it could lie there. From fedora at theholbrooks.org Wed Aug 16 23:50:43 2006 From: fedora at theholbrooks.org (Brandon Holbrook) Date: Wed, 16 Aug 2006 18:50:43 -0500 Subject: comps comps-fe6.xml.in,1.57,1.58 In-Reply-To: <200608160706.k7G76bh9017553@cvs-int.fedora.redhat.com> References: <200608160706.k7G76bh9017553@cvs-int.fedora.redhat.com> Message-ID: <44E3AF53.7040803@theholbrooks.org> Was this un-alphabetical entry for ipe intentional? My obsessive-compulsive nature is considering writing an alphabetize script to re-order every section. Good / bad / pointless idea? -Brandon Laurent Rineau (rineau) wrote: > --- comps-fe6.xml.in 16 Aug 2006 06:46:32 -0000 1.57 > +++ comps-fe6.xml.in 16 Aug 2006 07:06:35 -0000 1.58 > @@ -406,6 +406,7 @@ > sodipodi > tuxpaint > wings > + ipe > > > > > From buildsys at fedoraproject.org Thu Aug 17 01:53:30 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Wed, 16 Aug 2006 21:53:30 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-16 Message-ID: <20060817015330.D333B152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras development: 34 abook-0.5.6-2.fc6 cmucl-19c-5.fc6 convmv-1.10-1.fc6 digikam-0.8.2-2.fc6 dnsmasq-2.33-1.fc6 gnome-build-0.1.3-9.fc6 heartbeat-2.0.7-1.fc6 inotify-tools-2.3-1.fc6 libconfuse-2.5-2.fc6 libsexymm-0.1.7-3.fc6 mm-1.4.2-1.fc6 nagios-plugins-1.4.3-17.fc6 octave-2.9.7-3.fc6 perl-Cairo-0.92-1.fc6 perl-Class-InsideOut-1.02-2.fc6 perl-Data-Compare-0.13-1.fc6 perl-DateTime-0.34-1.fc6 perl-Locale-Maketext-Simple-0.17-1.fc6 perl-MIME-Types-1.17-1.fc6 perl-Object-Accessor-0.21-1.fc6 perl-PAR-Dist-0.16-1.fc6 perl-Scalar-Properties-0.12-1.fc6 php-shout-0.3.1-5.fc6 prboom-2.4.5-1.fc6 pyicq-t-0.7-4.fc6 python-dns-1.4.0-2.fc6 python-musicbrainz2-0.3.1-2.fc6 python-xmpp-0.3.1-2.fc6 tetex-elsevier-0.1.20060516-2.fc6 trackballs-1.1.2-2.fc6 trackballs-music-1.2-2.fc6 x3270-3.3.4p7-4.fc6 xprobe2-0.3-7.fc6 yaz-2.1.26-1.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Thu Aug 17 01:54:00 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Wed, 16 Aug 2006 21:54:00 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-16 Message-ID: <20060817015400.B0889152169@buildsys.fedoraproject.org> camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: liljencrantz AT gmail.com 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) k3d: denis AT poolshark.org 4: 0:0.5.16.0-4.fc4 (FE4) 5: 0:0.5.16.0-3.fc5 (FE5) 6: 0:0.5.16.0-3.fc6 (FE6) koffice: andreas.bierfert AT lowlatency.de 5: 0:1.5.2-1.fc5 (FE5) 6: 0:1.5.1-2.fc6 (FE6) ktorrent: wolters.liste AT gmx.net 5: 0:2.0-5.fc5 (FE5) 6: 0:2.0-4.fc6 (FE6) libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) libpqxx: andreas.bierfert AT lowlatency.de 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) lvm2: 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) mozilla: 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.2-2.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) quagga: 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) seamonkey: kengert AT redhat.com 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) smart: Axel.Thimm AT ATrpms.net 5: 0:0.42-35.fc5 (FE5) 6: 0:0.41-31.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.5-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) vorbisgain: noa AT resare.com 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) XaraLX: paul AT all-the-johnsons.co.uk 5: 0:0.7-3.fc5.r1614 (FE5) 6: 0:0.7-2.fc6.r1614 (FE6) From buildsys at fedoraproject.org Thu Aug 17 02:13:25 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Thu, 17 Aug 2006 02:13:25 -0000 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-16 Message-ID: <20060817021325.23299.33309@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (132 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (132 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (9 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (9 days) libopensync-plugin-evolution2 - 0.18-6.fc5.i386 (9 days) libopensync-plugin-evolution2 - 0.18-6.fc5.ppc (9 days) libopensync-plugin-evolution2 - 0.18-6.fc5.x86_64 (9 days) wine-core - 0.9.17-1.fc6.i386 (21 days) bdpepple AT ameritech.net contact-lookup-applet - 0.14-3.fc6.i386 (9 days) contact-lookup-applet - 0.14-3.fc6.ppc (9 days) contact-lookup-applet - 0.14-3.fc6.x86_64 (9 days) byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (28 days) gaim-guifications - 2.12-3.fc5.ppc (28 days) gaim-guifications - 2.12-3.fc5.x86_64 (28 days) fedora AT leemhuis.info gsynaptics - 0.9.8-1.fc6.ppc (28 days) gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (20 days) amarok - 1.4.1-3.fc6.ppc (20 days) showimg-pgsql - 0.9.5-7.fc4.i386 (9 days) showimg-pgsql - 0.9.5-7.fc4.ppc (9 days) showimg-pgsql - 0.9.5-7.fc4.x86_64 (9 days) showimg-pgsql - 0.9.5-7.fc5.i386 (9 days) showimg-pgsql - 0.9.5-7.fc5.ppc (9 days) showimg-pgsql - 0.9.5-7.fc5.x86_64 (9 days) green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (21 days) jogl - 1.1.1-14.fc5.ppc (24 days) ivazquez AT ivazquez.net deskbar-applet - 2.14.1.1-1.fc6.i386 (9 days) deskbar-applet - 2.14.1.1-1.fc6.ppc (9 days) deskbar-applet - 2.14.1.1-1.fc6.x86_64 (9 days) gnome-applet-music - 0.9.0-1.fc6.i386 (28 days) gnome-applet-music - 0.9.0-1.fc6.ppc (28 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (28 days) nautilus-search-tool - 0.2-1.fc5.i386 (28 days) nautilus-search-tool - 0.2-1.fc5.ppc (28 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (28 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (28 days) gfontview - 0.5.0-5.fc5.ppc (28 days) gfontview - 0.5.0-5.fc5.x86_64 (28 days) gtkhtml36 - 3.6.2-5.fc6.i386 (28 days) gtkhtml36 - 3.6.2-5.fc6.ppc (28 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (28 days) libvisual-plugins - 0.2.0-3.fc5.i386 (28 days) libvisual-plugins - 0.2.0-3.fc5.i386 (28 days) libvisual-plugins - 0.2.0-3.fc5.ppc (28 days) libvisual-plugins - 0.2.0-3.fc5.ppc (28 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (28 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (28 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (91 days) syck-php - 0.55-7.fc5.i386 (91 days) syck-php - 0.55-7.fc5.ppc (91 days) syck-php - 0.55-7.fc5.ppc (91 days) syck-php - 0.55-7.fc5.x86_64 (91 days) syck-php - 0.55-7.fc5.x86_64 (91 days) petersen AT redhat.com ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.i386 (7 days) ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.ppc (7 days) ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.x86_64 (7 days) rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (28 days) libibverbs - 1.0.3-1.fc6.ppc (28 days) libibverbs - 1.0.3-1.fc6.x86_64 (28 days) libibverbs-utils - 1.0.3-1.fc6.i386 (28 days) libibverbs-utils - 1.0.3-1.fc6.ppc (28 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (28 days) tcallawa AT redhat.com gambas-runtime - 1.0.14-2.fc5.i386 (8 days) thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (28 days) directfb - 0.9.24-5.fc5.ppc (28 days) directfb - 0.9.24-5.fc5.x86_64 (28 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.i386 requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) showimg-pgsql-0.9.5-7.fc5.x86_64 requires libpqxx-2.6.6.so()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.ppc requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.i386 requires libpqxx-2.6.6.so Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.x86_64 requires libpqxx-2.6.6.so()(64bit) Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.ppc requires libpqxx-2.6.6.so Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer contact-lookup-applet-0.14-3.fc6.i386 requires libebook-1.2.so.5 deskbar-applet-2.14.1.1-1.fc6.i386 requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 gambas-runtime-1.0.14-2.fc5.i386 requires libgettextlib-0.14.5.so gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-2.fc6.i386 requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- contact-lookup-applet-0.14-3.fc6.x86_64 requires libebook-1.2.so.5()(64bit) deskbar-applet-2.14.1.1-1.fc6.x86_64 requires libebook-1.2.so.5()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) ghc642-gtk2hs-mozembed-0.9.10-2.fc6.x86_64 requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libedata-cal-1.2.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libecal-1.2.so.3()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libebook-1.2.so.5()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.17-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 contact-lookup-applet-0.14-3.fc6.ppc requires libebook-1.2.so.5 deskbar-applet-2.14.1.1-1.fc6.ppc requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-2.fc6.ppc requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gsynaptics-0.9.8-1.fc6.ppc requires synaptics gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 ====================================================================== New report for: mpeters AT mac.com package: gfontview - 0.5.0-5.fc5.i386 from fedora-extras-development-i386 unresolved deps: libttf.so.2 package: gtkhtml36 - 3.6.2-5.fc6.i386 from fedora-extras-development-i386 unresolved deps: libgailutil.so.17 package: gtkhtml36 - 3.6.2-5.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libgailutil.so.17()(64bit) package: gfontview - 0.5.0-5.fc5.x86_64 from fedora-extras-development-x86_64 unresolved deps: libttf.so.2()(64bit) package: gtkhtml36 - 3.6.2-5.fc6.ppc from fedora-extras-development-ppc unresolved deps: libgailutil.so.17 package: gfontview - 0.5.0-5.fc5.ppc from fedora-extras-development-ppc unresolved deps: libttf.so.2 ====================================================================== New report for: byte AT fedoraproject.org package: gaim-guifications - 2.12-3.fc5.i386 from fedora-extras-development-i386 unresolved deps: gaim < 1:2 package: gaim-guifications - 2.12-3.fc5.x86_64 from fedora-extras-development-x86_64 unresolved deps: gaim < 1:2 package: gaim-guifications - 2.12-3.fc5.ppc from fedora-extras-development-ppc unresolved deps: gaim < 1:2 ====================================================================== New report for: thomas AT apestaart.org package: directfb - 0.9.24-5.fc5.i386 from fedora-extras-development-i386 unresolved deps: libsysfs.so.1 package: directfb - 0.9.24-5.fc5.x86_64 from fedora-extras-development-x86_64 unresolved deps: libsysfs.so.1()(64bit) package: directfb - 0.9.24-5.fc5.ppc from fedora-extras-development-ppc unresolved deps: libsysfs.so.1 ====================================================================== New report for: rolandd AT cisco.com package: libibverbs - 1.0.3-1.fc6.i386 from fedora-extras-development-i386 unresolved deps: libsysfs.so.1 package: libibverbs-utils - 1.0.3-1.fc6.i386 from fedora-extras-development-i386 unresolved deps: libsysfs.so.1 package: libibverbs - 1.0.3-1.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libsysfs.so.1()(64bit) package: libibverbs-utils - 1.0.3-1.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libsysfs.so.1()(64bit) package: libibverbs-utils - 1.0.3-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: libsysfs.so.1 package: libibverbs - 1.0.3-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: libsysfs.so.1 ====================================================================== New report for: ivazquez AT ivazquez.net package: nautilus-search-tool - 0.2-1.fc5.i386 from fedora-extras-development-i386 unresolved deps: libgailutil.so.17 package: gnome-applet-music - 0.9.0-1.fc6.i386 from fedora-extras-development-i386 unresolved deps: libgailutil.so.17 libdbus-1.so.2 package: gnome-applet-music - 0.9.0-1.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libgailutil.so.17()(64bit) libdbus-1.so.2()(64bit) package: nautilus-search-tool - 0.2-1.fc5.x86_64 from fedora-extras-development-x86_64 unresolved deps: libgailutil.so.17()(64bit) package: nautilus-search-tool - 0.2-1.fc5.ppc from fedora-extras-development-ppc unresolved deps: libgailutil.so.17 package: gnome-applet-music - 0.9.0-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: libgailutil.so.17 libdbus-1.so.2 ====================================================================== New report for: fedora AT leemhuis.info package: gsynaptics - 0.9.8-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: synaptics From paul at cypherpunks.ca Thu Aug 17 03:25:53 2006 From: paul at cypherpunks.ca (Paul Wouters) Date: Thu, 17 Aug 2006 05:25:53 +0200 (CEST) Subject: Request package removal hping2 from devel (obsoleted by hping3) Message-ID: Hi people, I am the maintainer of hping2 and hping3. I would like to remove hping2 from the development repository. hping3 provides "hping2", so no package should break. And as far as I know, only nagios-plugins depends on it, and it depends on "hping" not "hping2". Is this something I should do by emptying the devel/ CVS repository and removing the package from the owner's list? Or is this something someone else has to do? Paul From mattdm at mattdm.org Thu Aug 17 03:35:51 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Wed, 16 Aug 2006 23:35:51 -0400 Subject: Request package removal hping2 from devel (obsoleted by hping3) In-Reply-To: References: Message-ID: <20060817033551.GA1181@jadzia.bu.edu> On Thu, Aug 17, 2006 at 05:25:53AM +0200, Paul Wouters wrote: > Is this something I should do by emptying the devel/ CVS repository and > removing the package from the owner's list? Or is this something someone > else has to do? There's a Top Secret [*] wiki page for it: http://fedoraproject.org/wiki/Extras/FC6Status [*] not intentionally, I don't think. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From laurent.rineau__fedora_extras at normalesup.org Thu Aug 17 06:56:06 2006 From: laurent.rineau__fedora_extras at normalesup.org (Laurent Rineau) Date: Thu, 17 Aug 2006 08:56:06 +0200 Subject: comps comps-fe6.xml.in,1.57,1.58 In-Reply-To: <44E3AF53.7040803@theholbrooks.org> References: <200608160706.k7G76bh9017553@cvs-int.fedora.redhat.com> <44E3AF53.7040803@theholbrooks.org> Message-ID: <200608170856.06340@rineau.schtroumpfette> On Thursday 17 August 2006 01:50, Brandon Holbrook wrote: > Was this un-alphabetical entry for ipe intentional? Fixed. > My obsessive-compulsive nature is considering writing an alphabetize > script to re-order every section. Good / bad / pointless idea? I have added a note about the alphabetical order in the Wiki page. From j.w.r.degoede at hhs.nl Thu Aug 17 07:18:16 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Thu, 17 Aug 2006 09:18:16 +0200 Subject: Packages missing in comps-feX.xml.in In-Reply-To: <200608170118.37566@rineau.schtroumpfette> References: <20060816021728.95dfae1b@ludwig-alpha> <200608161704.05039@rineau.schtroumpfette> <20060817010601.235b8e66@ludwig-alpha> <200608170118.37566@rineau.schtroumpfette> Message-ID: <44E41838.6060807@hhs.nl> Laurent Rineau wrote: > On Thursday 17 August 2006 01:06, Christian Iseli wrote: >> On Wed, 16 Aug 2006 17:04:05 +0200, Laurent Rineau wrote: >>> I do not know where to put par2cmdline. I do not see any group about >>> backups, archiving tools, and so one. >> Looks like you found a spot... > > I am not real conviced that system-tools is the right group for par2cmdline. > As a first approximation, it could lie there. > Its where I put arc, maybe we need a archivers group, we have zip, tar, arc, par2, etc, etc. Regards, Hans From ville.skytta at iki.fi Thu Aug 17 08:49:38 2006 From: ville.skytta at iki.fi (Ville =?ISO-8859-1?Q?Skytt=E4?=) Date: Thu, 17 Aug 2006 11:49:38 +0300 Subject: Request package removal hping2 from devel (obsoleted by hping3) In-Reply-To: <20060817033551.GA1181@jadzia.bu.edu> References: <20060817033551.GA1181@jadzia.bu.edu> Message-ID: <1155804579.15307.287.camel@localhost.localdomain> On Wed, 2006-08-16 at 23:35 -0400, Matthew Miller wrote: > On Thu, Aug 17, 2006 at 05:25:53AM +0200, Paul Wouters wrote: > > Is this something I should do by emptying the devel/ CVS repository and > > removing the package from the owner's list? Or is this something someone > > else has to do? > > There's a Top Secret [*] wiki page for it: > > http://fedoraproject.org/wiki/Extras/FC6Status And more instructions at http://fedoraproject.org/wiki/Extras/PackageEndOfLife If the hping2 package continues to be shipped for any distro versions, it shouldn't be removed from owners.list. From tla-ml at rasmil.dk Thu Aug 17 13:52:32 2006 From: tla-ml at rasmil.dk (Tim Lauridsen) Date: Thu, 17 Aug 2006 15:52:32 +0200 Subject: cant upload new source Message-ID: <44E474A0.4000003@rasmil.dk> I try to upload some new sources, but i get this error message, anybody know what i wrong ?? [tim at localhost devel]$ make new-sources FILES="~/rpmbuild/SOURCES/yumex-1.1.1.tar.gz" Checking : yumex-1.1.1.tar.gz on https://cvs.fedora.redhat.com/repo/extras/upload.cgi... ERROR: could not check remote file status make: *** [new-sources] Error 255 Tim From j.w.r.degoede at hhs.nl Thu Aug 17 14:07:57 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Thu, 17 Aug 2006 16:07:57 +0200 Subject: cant upload new source In-Reply-To: <44E474A0.4000003@rasmil.dk> References: <44E474A0.4000003@rasmil.dk> Message-ID: <44E4783D.7070007@hhs.nl> Tim Lauridsen wrote: > I try to upload some new sources, but i get this error message, anybody > know what i wrong ?? > > [tim at localhost devel]$ make new-sources > FILES="~/rpmbuild/SOURCES/yumex-1.1.1.tar.gz" > > Checking : yumex-1.1.1.tar.gz on > https://cvs.fedora.redhat.com/repo/extras/upload.cgi... > ERROR: could not check remote file status > make: *** [new-sources] Error 255 > > > Tim > Well known problem, go fetch yourself a new ~/.fefora.cert from the account system. Regards, HANS From gajownik at gmail.com Thu Aug 17 14:03:01 2006 From: gajownik at gmail.com (Dawid Gajownik) Date: Thu, 17 Aug 2006 16:03:01 +0200 Subject: cant upload new source In-Reply-To: <44E474A0.4000003@rasmil.dk> References: <44E474A0.4000003@rasmil.dk> Message-ID: <44E47715.2060203@gmail.com> Dnia 08/17/2006 03:49 PM, U?ytkownik Tim Lauridsen napisa?: > make: *** [new-sources] Error 255 You should read it as: "Congratulations! You've been a Fedora Extras maintainter for a year." ;-) http://fedoraproject.org/wiki/Extras/UsingCvsFaq#head-805d2a90470d52ce968d1e4b4b2487e982ea1b66 -- ^_* From tla-ml at rasmil.dk Thu Aug 17 14:39:05 2006 From: tla-ml at rasmil.dk (Tim Lauridsen) Date: Thu, 17 Aug 2006 16:39:05 +0200 Subject: cant upload new source In-Reply-To: <44E47715.2060203@gmail.com> References: <44E474A0.4000003@rasmil.dk> <44E47715.2060203@gmail.com> Message-ID: <44E47F89.8060105@rasmil.dk> Dawid Gajownik wrote: > Dnia 08/17/2006 03:49 PM, U?ytkownik Tim Lauridsen napisa?: >> make: *** [new-sources] Error 255 > > You should read it as: "Congratulations! You've been a Fedora Extras > maintainter for a year." ;-) > > http://fedoraproject.org/wiki/Extras/UsingCvsFaq#head-805d2a90470d52ce968d1e4b4b2487e982ea1b66 > > Thanks, now it is working Tim From andy at smile.org.ua Thu Aug 17 15:46:44 2006 From: andy at smile.org.ua (Andy Shevchenko) Date: Thu, 17 Aug 2006 18:46:44 +0300 Subject: comps comps-fe6.xml,1.10,1.11 In-Reply-To: <200608171231.k7HCVPTS018735@cvs-int.fedora.redhat.com> References: <200608171231.k7HCVPTS018735@cvs-int.fedora.redhat.com> Message-ID: <44E48F64.4050904@smile.org.ua> Sindre Pedersen Bj?rdal (sindrepb) wrote: > Author: sindrepb > > Update of /cvs/extras/comps > In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18714 > > Index: comps-fe6.xml > diff -u -r1.10 -r1.11 > - deskbar-applet > + deskbar-applet > - seahorse > + seahorse > - blogtk > + blogtk > - easytag > + easytag > - soundconverter > + soundconverter Why do you change whitespacing? And may by prefer to change comps-feX.xml.*in* files. -- With best regards, Andy Shevchenko. mailto: andy at smile.org.ua From andy at smile.org.ua Thu Aug 17 15:52:00 2006 From: andy at smile.org.ua (Andy Shevchenko) Date: Thu, 17 Aug 2006 18:52:00 +0300 Subject: comps-feX.xml vs. my own packages Message-ID: <44E490A0.6010503@smile.org.ua> Hi, all! I'm maintaining the man-pages-uk and qstat packages that aren't included into comps. First off, I've can't find any documentation related gropu for man-pages. Second, qstat is not a game, just stat-server for game servers. I may include it to game category but I'm in some doubt. Could anybody solute me something? Thank you. -- With best regards, Andy Shevchenko. mailto: andy at smile.org.ua From fedora at camperquake.de Thu Aug 17 18:01:35 2006 From: fedora at camperquake.de (Ralf Ertzinger) Date: Thu, 17 Aug 2006 20:01:35 +0200 Subject: cant upload new source In-Reply-To: <44E474A0.4000003@rasmil.dk> References: <44E474A0.4000003@rasmil.dk> Message-ID: <20060817200135.262ee32d@nausicaa.camperquake.de> Hi. Tim Lauridsen wrote: > Checking : yumex-1.1.1.tar.gz on > https://cvs.fedora.redhat.com/repo/extras/upload.cgi... > ERROR: could not check remote file status > make: *** [new-sources] Error 255 As has been told this is due to an expired certificate. Since I feel like chasing bugs today: Is there a way to provide me with an expired certificate, in order to produce a patch that will lead to a more meaningful error message? My own certificate is quite non-expired, unfortunately :) -- I'm a sysadmin, not a doctor, and I've spent the last ten years ensuring that state of affairs. -- Patrick Gosling From jima at beer.tclug.org Thu Aug 17 18:28:54 2006 From: jima at beer.tclug.org (Jima) Date: Thu, 17 Aug 2006 13:28:54 -0500 (CDT) Subject: cant upload new source In-Reply-To: <20060817200135.262ee32d@nausicaa.camperquake.de> References: <44E474A0.4000003@rasmil.dk> <20060817200135.262ee32d@nausicaa.camperquake.de> Message-ID: On Thu, 17 Aug 2006, Ralf Ertzinger wrote: > As has been told this is due to an expired certificate. Since I feel > like chasing bugs today: > > Is there a way to provide me with an expired certificate, in order to > produce a patch that will lead to a more meaningful error message? > > My own certificate is quite non-expired, unfortunately :) Actually, I threw together a patch this morning and emailed it to Jeremy, as he solicited on Monday. My Makefile-fu is weak, though, so I can't be absolutely sure it's good. (Also, I don't know if I should be uploading junk files for testing.) However, AFAICT, the expiration date is in plaintext, so my method of testing was to just edit the date (as that's all my patch checks for). Anyone more knowledgable in Makefiles, or simply braver than me, can play with this: http://beer.tclug.org/fedora-extras/fedora-cert-expired.patch Feedback is readily encouraged. :) Jima From fedora at camperquake.de Thu Aug 17 18:52:26 2006 From: fedora at camperquake.de (Ralf Ertzinger) Date: Thu, 17 Aug 2006 20:52:26 +0200 Subject: cant upload new source In-Reply-To: References: <44E474A0.4000003@rasmil.dk> <20060817200135.262ee32d@nausicaa.camperquake.de> Message-ID: <20060817205226.294cbdc2@nausicaa.camperquake.de> Hi. Jima wrote: > Actually, I threw together a patch this morning and emailed it to > Jeremy, as he solicited on Monday. My Makefile-fu is weak, though, so > I can't be absolutely sure it's good. (Also, I don't know if I should > be uploading junk files for testing.) However, AFAICT, the expiration > date is in plaintext, so my method of testing was to just edit the date > (as that's all my patch checks for). > Anyone more knowledgable in Makefiles, or simply braver than me, can > play with this: > > http://beer.tclug.org/fedora-extras/fedora-cert-expired.patch > > Feedback is readily encouraged. :) Ah. That is a way to check it that did not occur to me. My take is below, just to provide some choice :) Thanks to Dawid Gajownik for providing me with an expired certificate. -- Eagles may soar, but weasels don't get sucked into jet engines. -------------- next part -------------- A non-text attachment was scrubbed... Name: fedora-Makefile.common-certexpire.patch Type: text/x-patch Size: 728 bytes Desc: not available URL: From paul at city-fan.org Thu Aug 17 20:24:00 2006 From: paul at city-fan.org (Paul Howarth) Date: Thu, 17 Aug 2006 21:24:00 +0100 Subject: mock/etc redhat-8-i386.cfg, 1.1, 1.2 fedora-1-i386-core.cfg, 1.4, 1.5 fedora-2-i386-core.cfg, 1.4, 1.5 In-Reply-To: <200608171823.k7HINvSR005288@cvs-int.fedora.redhat.com> References: <200608171823.k7HINvSR005288@cvs-int.fedora.redhat.com> Message-ID: <1155846240.12345.4.camel@metropolis.intra.city-fan.org> On Thu, 2006-08-17 at 11:23 -0700, John Clark Williams wrote: > Author: jcwillia > > Update of /cvs/fedora/mock/etc > In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5266/etc > > Modified Files: > fedora-1-i386-core.cfg fedora-2-i386-core.cfg > Added Files: > redhat-8-i386.cfg > Log Message: > updated config files to handle FC[12] lack of runuser; added template for RHL8 None of the RHLs had runuser either, so they (e.g. the new redhat-8-i386.cfg) will need "config_opts['runuser'] = '/bin/su'" as well. Paul. From ryo-dairiki at users.sourceforge.net Fri Aug 18 03:41:00 2006 From: ryo-dairiki at users.sourceforge.net (Ryo Dairiki) Date: Fri, 18 Aug 2006 12:41:00 +0900 Subject: New category needed for compsXML: i18n In-Reply-To: <1155750121.5006.14.camel@orodruin.boston.redhat.com> References: <44E2D113.1060409@users.sourceforge.net> <20060816102940.GD2768@free.fr> <44E32F69.3040400@users.sourceforge.net> <1155750121.5006.14.camel@orodruin.boston.redhat.com> Message-ID: <44E536CC.6000309@users.sourceforge.net> Jeremy Katz wrote: > On Wed, 2006-08-16 at 23:44 +0900, Ryo Dairiki wrote: > >> Patrice Dumas wrote: >> >>> On Wed, Aug 16, 2006 at 05:02:27PM +0900, Ryo Dairiki wrote: >>> >>>> I'm thinking of writing compsXML for SCIM related packages, >>>> and I need a new category like "I18n" or "Internationalization" for them. >>>> Where can I request it? Or just posting here is enough? >>>> >>>> >>> I am fairly ignorant on that subject, but aren't I18n related packages >>> like libraries, and pulled as dependencies by the apps that use them? >>> Are they of use by themselves? >>> >> Not, really. >> >> There are some extra packages in that category. >> For example, special input methods, and special composing dictionaries. >> >> I own "scim-skk", which is yet another input method for Japanese. >> As you know, the default input method for Japanese in Fedora is >> "scim-anthy", >> which is installed by dependencies on Japanese environments. >> But there are some people who prefer scim-skk to scim-anthy. >> For such people, scim-skk must shown in the list of apps to install. >> Just installed by dependencies is not a good idea. >> > > There are groups for language support groups that this would be fine for > adding to > > Jeremy > Thanks, But I don't see any "language*" groups in comps-fe5.xml.in or comps-fe6.xml.in. Can I add it by myself? Ryo From tla-ml at rasmil.dk Fri Aug 18 07:13:13 2006 From: tla-ml at rasmil.dk (Tim Lauridsen) Date: Fri, 18 Aug 2006 09:13:13 +0200 Subject: cant upload new source In-Reply-To: <20060817200135.262ee32d@nausicaa.camperquake.de> References: <44E474A0.4000003@rasmil.dk> <20060817200135.262ee32d@nausicaa.camperquake.de> Message-ID: <44E56889.9050808@rasmil.dk> Ralf Ertzinger wrote: > Hi. > > Tim Lauridsen wrote: > > >> Checking : yumex-1.1.1.tar.gz on >> https://cvs.fedora.redhat.com/repo/extras/upload.cgi... >> ERROR: could not check remote file status >> make: *** [new-sources] Error 255 >> > > As has been told this is due to an expired certificate. Since I feel > like chasing bugs today: > > Is there a way to provide me with an expired certificate, in order to > produce a patch that will lead to a more meaningful error message? > > My own certificate is quite non-expired, unfortunately :) > > > I think i have my old cert someplace, i will try to find, and mail it later to day. Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul at all-the-johnsons.co.uk Fri Aug 18 14:14:54 2006 From: paul at all-the-johnsons.co.uk (PFJ) Date: Fri, 18 Aug 2006 15:14:54 +0100 Subject: Appending a file in %{_sysconfdir} Message-ID: <1155910494.2548.9.camel@localhost.localdomain> Hi, I'm packaging sdldotnet for inclusion into extras and have hit a small snag. I need to amend %{_sysconfdir}/mono/config to include some bits required for sdldotnet. How do I append said file inside of a spec file? Should I just create a new version, add the bits, diff and apply or is there a better way? Obviously, this has to be done during the install step. TTFN Paul -- "Logic, my dear Zoe, is merely the ability to be wrong with authority" - Dr Who From rdieter at math.unl.edu Fri Aug 18 14:22:23 2006 From: rdieter at math.unl.edu (Rex Dieter) Date: Fri, 18 Aug 2006 09:22:23 -0500 Subject: Appending a file in %{_sysconfdir} References: <1155910494.2548.9.camel@localhost.localdomain> Message-ID: PFJ wrote: > I'm packaging sdldotnet for inclusion into extras and have hit a small > snag. I need to amend %{_sysconfdir}/mono/config to include some bits > required for sdldotnet. > > How do I append said file inside of a spec file? Should I just create a > new version, add the bits, diff and apply or is there a better way? This seems something to be done in a scriplet in %post (and to undo the mods in %postun) -- Rex From tla-ml at rasmil.dk Fri Aug 18 15:42:22 2006 From: tla-ml at rasmil.dk (Tim Lauridsen) Date: Fri, 18 Aug 2006 17:42:22 +0200 Subject: cant upload new source In-Reply-To: <44E56889.9050808@rasmil.dk> References: <44E474A0.4000003@rasmil.dk> <20060817200135.262ee32d@nausicaa.camperquake.de> <44E56889.9050808@rasmil.dk> Message-ID: <44E5DFDE.7060101@rasmil.dk> Tim Lauridsen wrote: > Ralf Ertzinger wrote: >> Hi. >> >> Tim Lauridsen wrote: >> >> >>> Checking : yumex-1.1.1.tar.gz on >>> https://cvs.fedora.redhat.com/repo/extras/upload.cgi... >>> ERROR: could not check remote file status >>> make: *** [new-sources] Error 255 >>> >> >> As has been told this is due to an expired certificate. Since I feel >> like chasing bugs today: >> >> Is there a way to provide me with an expired certificate, in order to >> produce a patch that will lead to a more meaningful error message? >> >> My own certificate is quite non-expired, unfortunately :) >> >> >> > I think i have my old cert someplace, i will try to find, and mail it > later to day. > > Tim Here is my expired cert. Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: .fedora.cert URL: From pnasrat at redhat.com Fri Aug 18 15:54:17 2006 From: pnasrat at redhat.com (Paul Nasrat) Date: Fri, 18 Aug 2006 11:54:17 -0400 Subject: Appending a file in %{_sysconfdir} In-Reply-To: References: <1155910494.2548.9.camel@localhost.localdomain> Message-ID: <1155916457.2935.3.camel@enki.eridu> On Fri, 2006-08-18 at 09:22 -0500, Rex Dieter wrote: > PFJ wrote: > > > I'm packaging sdldotnet for inclusion into extras and have hit a small > > snag. I need to amend %{_sysconfdir}/mono/config to include some bits > > required for sdldotnet. > > > > How do I append said file inside of a spec file? Should I just create a > > new version, add the bits, diff and apply or is there a better way? > > This seems something to be done in a scriplet in %post (and to undo the mods > in %postun) If you want to do it programatically - rhpl.simpleconfig.SimpleConfig is what we basically use in to set these up. Paul From paul at all-the-johnsons.co.uk Fri Aug 18 17:03:14 2006 From: paul at all-the-johnsons.co.uk (Paul) Date: Fri, 18 Aug 2006 18:03:14 +0100 Subject: Appending a file in %{_sysconfdir} In-Reply-To: <1155916457.2935.3.camel@enki.eridu> References: <1155910494.2548.9.camel@localhost.localdomain> <1155916457.2935.3.camel@enki.eridu> Message-ID: <1155920595.4248.0.camel@T7.Linux> Hi, > > This seems something to be done in a scriplet in %post (and to undo the mods > > in %postun) > > If you want to do it programatically - rhpl.simpleconfig.SimpleConfig is > what we basically use in to set these up. It must be because it's Friday, but what is rhpl.simpleconfig.SimpleConfig? TTFN Paul -- "Ist du meine Mutter?" - der leerkinde -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From pnasrat at redhat.com Fri Aug 18 21:03:29 2006 From: pnasrat at redhat.com (Paul Nasrat) Date: Fri, 18 Aug 2006 17:03:29 -0400 Subject: Appending a file in %{_sysconfdir} In-Reply-To: <1155920595.4248.0.camel@T7.Linux> References: <1155910494.2548.9.camel@localhost.localdomain> <1155916457.2935.3.camel@enki.eridu> <1155920595.4248.0.camel@T7.Linux> Message-ID: <1155935009.2935.13.camel@enki.eridu> On Fri, 2006-08-18 at 18:03 +0100, Paul wrote: > Hi, > > > > This seems something to be done in a scriplet in %post (and to undo the mods > > > in %postun) > > > > If you want to do it programatically - rhpl.simpleconfig.SimpleConfig is > > what we basically use in to set these up. > > It must be because it's Friday, but what is > rhpl.simpleconfig.SimpleConfig? A python module ipython import rhpl.simpleconfig myconf = rhpl.simpleconfig.SimpleConfig() myconf.read("/etc/sysconfig/i18n") Paul From jkeating at redhat.com Fri Aug 18 21:06:18 2006 From: jkeating at redhat.com (Jesse Keating) Date: Fri, 18 Aug 2006 17:06:18 -0400 Subject: Appending a file in %{_sysconfdir} In-Reply-To: <1155910494.2548.9.camel@localhost.localdomain> References: <1155910494.2548.9.camel@localhost.localdomain> Message-ID: <200608181706.18411.jkeating@redhat.com> On Friday 18 August 2006 10:14, PFJ wrote: > I'm packaging sdldotnet for inclusion into extras and have hit a small > snag. I need to amend %{_sysconfdir}/mono/config to include some bits > required for sdldotnet. Danger Will Robinson! Fiddling with file content, especially config files is bad juju. What you should really do is work with the mono packager to make a %{_sysconfdir}/mono/config.d/ directory that packages can drop config stubs into and remove from. We learned long ago trying to fiddle with file contents is just a bad idea. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dominik at greysector.net Fri Aug 18 22:03:09 2006 From: dominik at greysector.net (Dominik 'Rathann' Mierzejewski) Date: Sat, 19 Aug 2006 00:03:09 +0200 Subject: FC-4 branch request (was Re: FYI: Fedora Extras 4 in Maintenance state, FC-4 branches need to be permitted by FESCo) In-Reply-To: <44DCB02F.8070605@leemhuis.info> References: <44DCB02F.8070605@leemhuis.info> Message-ID: <20060818220308.GB5346@rathann.pekin.waw.pl> On Friday, 11 August 2006 at 18:28, Thorsten Leemhuis wrote: [...] > just a heads up: Now that Fedora Core 4 was transfered to Fedora Legacy > Fedora Extras 4 is in Maintenance state now, too. See > http://www.fedoraproject.org/wiki/Extras/Security/EOLPolicy > for details. > > That why > http://www.fedoraproject.org/wiki/Extras/CVSSyncNeeded > now contains: > > > FC-3 and FC-4 branches require FESCo approval and are generally > > discouraged. > > There are still some branch requests for FC-4. I suggest we create those > and stop from now on. I'd like to request FC-4 branch for crm114. tre, on which it depends, managed to slip in at the last minute, but crm114 didn't make it in time. Regards, R. -- Fedora Extras contributor http://fedoraproject.org/wiki/DominikMierzejewski MPlayer developer http://rpm.greysector.net/mplayer/ "Faith manages." -- Delenn to Lennier in Babylon 5:"Confessions and Lamentations" From rdieter at math.unl.edu Fri Aug 18 23:54:11 2006 From: rdieter at math.unl.edu (Rex Dieter) Date: Fri, 18 Aug 2006 18:54:11 -0500 Subject: Appending a file in %{_sysconfdir} In-Reply-To: <200608181706.18411.jkeating@redhat.com> References: <1155910494.2548.9.camel@localhost.localdomain> <200608181706.18411.jkeating@redhat.com> Message-ID: Jesse Keating wrote: > On Friday 18 August 2006 10:14, PFJ wrote: >> I'm packaging sdldotnet for inclusion into extras and have hit a small >> snag. I need to amend %{_sysconfdir}/mono/config to include some bits >> required for sdldotnet. > > Danger Will Robinson! Fiddling with file content, especially config files is > bad juju. What you should really do is work with the mono packager to make > a %{_sysconfdir}/mono/config.d/ directory that packages can drop config stubs > into and remove from. We learned long ago trying to fiddle with file > contents is just a bad idea. Jesse's absolutely right... his suggestion certainly is the best (long-term) solution to this general type of problem, e.g. /etc/ld.so.conf.d/ /etc/fonts/conf.d/ /etc/httpd/conf.d/ -- Rex From tibbs at math.uh.edu Fri Aug 18 23:48:17 2006 From: tibbs at math.uh.edu (Jason L Tibbitts III) Date: Fri, 18 Aug 2006 18:48:17 -0500 Subject: FC-4 branch request In-Reply-To: <20060818220308.GB5346@rathann.pekin.waw.pl> (Dominik Mierzejewski's message of "Sat, 19 Aug 2006 00:03:09 +0200") References: <44DCB02F.8070605@leemhuis.info> <20060818220308.GB5346@rathann.pekin.waw.pl> Message-ID: >>>>> "DM" == Dominik Mierzejewski writes: DM> I'd like to request FC-4 branch for crm114. Could you give a reason why this needs to be branched for FC4? - J< From toshio at tiki-lounge.com Fri Aug 18 23:48:26 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Fri, 18 Aug 2006 16:48:26 -0700 Subject: FESCo Meeting Minutes for 2006-08-17 Message-ID: <1155944907.2982.22.camel@localhost> = 2006 August 17 FESCo = Meeting Summaries are posted on the wiki at: http://www.fedoraproject.org/wiki/Extras/SteeringCommittee/Meetings == Attending == * warren * thl * bpepple * c4chris * rdieter * tibbs * abadger1999 * dgilmore == Summary == === Mass Rebuild === * http://www.fedoraproject.org/wiki/Extras/Schedule/FC6MassRebuild * Packagers get 3 weeks to rebuild just like AWOL policy. * Packages that haven't been rebuilt get orphaned and the packages won't ship in the FC6 repository. * AWOL package process started for ignacio as he has a bunch of packages that others might have to pick up as dependencies. === comps.xml === * c4chris sent out nagmails. Many people have updated their packaged in comps.xml.in. * There are preliminary plans by the Packaging Committee to remove the group tag in the spec file and only have the information in comps.xml. * c4chris thinks the only way to make 100% accurate nagmails is to record a group for all packages, which could be an invisible group for some packages. This information might be appropriate for the Package Database. * c4chris and bpepple will start a comps SIG. * Even command-line tools should be in comps. === Legacy in buildroots === * Waiting on legacy being able to access the buildsystem so they can build ppc updates. === Ctrl-C Problem === * Infrastructure says figuring out a solution before the new VCS is probably too much work. * New VCS prototyping is waiting on two new servers to be installed at the end of August. Hoping to have something ready for Extras people to test by FC7t1. === Packaging Committee Report === * Started discussing deprecating and removing Group tag. No timeline yet but definitely a post-FC6 change. * ldconfig wording change to clarify the meaning. * Talked about changing the meeting day/time so there's time to send the committee report to FESCo via email. === Sponsorship Nominations === * dgilmore and c4chris accepted as sponsors. * New rule, nominate new FESCo members for sponsorship if they are not already; debate about upgrading them will be per normal. * Qualifications to be a sponsor needs to be discussed. === Misc === * New Package Review template approved: https://www.redhat.com/archives/fedora-extras-list/2006-August/msg00361.html * wiki user setup to send changes to FESCo list when /Extras/Schedule* is changed. * kmod discussion * Packaging Committee will discuss the technical aspects, whether to allow them in Fedora Extras/Core at all is being passed up to FAB. === Free discussion === * Maintainer Responsibility:: http://fedoraproject.org/wiki/JasonTibbitts/MaintainerResponsibilityPolicy * tibbs solicits input on the draft policy. There are several open questions that need answering therein. == Log == {{{ (09:55:23) ***warren here. (09:55:32) warren: mdomsch, you there? (09:55:48) mdomsch: warren, yes (09:57:40) ***jima pops some popcorn for the show (09:59:05) ***cweyl settles in to lurk... silly people at work who presume to schedule their meetings during FESCo! (10:00:16) thl has changed the topic to: FESCo meeting in progress (10:00:22) thl: hy everyone (10:00:26) thl: who's around? (10:00:36) ***bpepple is here. (10:00:36) ***c4chris_ is here (10:00:55) c4chris_ is now known as c4chris (10:01:28) rdieter: here (10:01:35) tibbs: I'm here. (10:01:38) ***cweyl is lurking (rabble) (10:01:41) thl: okay, so let's start slowly (10:01:56) thl has changed the topic to: FESCo meeting in progress -- M{ae}ss-Rebuild (10:01:57) ***abadger1999 here (10:02:16) thl: scop not around (10:02:26) thl: do we want to discuss this further (10:02:37) thl: open issues: How much time need people to rebuild their stuff? What happens with packages that haven't been rebuilt or marked as not needing a rebuild by deadline X? (10:03:04) c4chris: what's the delay in the AWOL policy? (10:03:15) ***dgilmore is here (10:03:29) c4chris: I think we should use the same delay (10:03:35) dgilmore: thl: no need for discussion Lets just do it (10:03:59) tibbs: The delay is three weeks and three days, BTW. (10:04:00) thl: c4chris, I don#t know the exact delay from AWOL (10:04:27) c4chris: tibbs, sounds about right (10:04:32) thl: let's say: give people three weeks to rebuild their stuff? (10:04:39) c4chris: thl, +1 (10:04:40) bpepple: thl: +1 (10:04:46) thl: that leaves some time to fix the remaining stuff before FC6 ships (10:04:47) tibbs: +1 (10:04:50) warren: +1 (10:05:02) dgilmore: +1 (10:05:05) rdieter: +1 (10:05:11) thl: okay, three weeks (10:05:27) thl: What happens with packages that haven't been rebuilt or marked as not needing a rebuild by deadline X? (10:05:39) tibbs: Orphaned? (10:05:47) c4chris: Let's deal with the not rebuilt package when we have an idea how many there are (10:06:11) tibbs: We should know in advance so that people won't just expect the current package to rull into FC6. (10:06:23) tibbs: s/rull/roll/ (10:06:27) c4chris: mmh (10:06:31) c4chris: ok (10:06:37) dgilmore: im kindof scared if ignacio doesnt step up he has alot of packages (10:06:43) thl: dgilmore, +1 (10:06:43) c4chris: orphaned sounds about right (10:06:55) thl: jwb, you wanted to contact ignacio iirc (10:07:07) bpepple: dgilmore: Should other people be brought in to help him? (10:07:10) jwb: thl, i sent him an email. no repsonse (10:07:19) thl: jwb, thx (10:07:39) tibbs: Packages not rebuilt certainly shouldn't get autobranched to FC6, but I don't think they should be deleted. (10:07:50) dgilmore: i sent him one about 6-8 weeks ago asked how things were going got nothing (10:07:55) c4chris: we never delete packages (10:08:00) c4chris: just orphan them (10:08:10) thl: tibbs, well, that would mean that someone had to maintain them through the entry lifecicle of FC6 (10:08:15) thl: we need to delete them (10:08:46) dgilmore: delete binaries but not cvs (10:08:55) c4chris: dgilmore, oh right (10:09:35) tibbs: The binaries should not get out to FC6 unless they've been rebuilt. (10:09:57) thl: okay (10:10:02) c4chris: so the threat is: they won't ship in FC6 until rebuilt (or a short explanation why they are not rebuilt...) (10:10:16) jwb: that seems reasonable (10:10:19) rdieter: yup (10:10:26) thl: so just to be sure: +1 for "delete all packages that are not rebuild in time" please (10:10:27) tibbs: +1 (10:10:34) jwb: +1 (10:10:34) c4chris: +1 (10:10:36) abadger1999: +1 (10:10:38) rdieter: +1 (10:10:42) dgilmore: +1 (10:10:51) tibbs: +1 (10:10:58) abadger1999: For ignacio specifically, has the AWOL packagers process been started? (10:11:26) dgilmore: abadger1999: no but it really needs to (10:11:32) jwb: agreed (10:11:41) bpepple: dgilmore: +1 (10:11:48) warren: Want me to attempt to use non-email to contact him? (10:11:52) BobJensen: dgilmore: +1 (10:11:57) warren: Ask him what he wants us to do with his packages. (10:12:00) abadger1999: warren: +1 (10:12:05) thl: warren, maybe that would be a good idea (10:12:08) c4chris: warren, +1 (10:12:09) Daveman: :o (10:12:15) tibbs: If someone has his phone number, it would certainly be a good idea to try it. (10:12:21) BobJensen: I tried calling all I got was VM (10:12:36) Daveman: FC6? (10:12:36) dgilmore: warren: +1 (10:12:42) warren: I'll give it a try. (10:12:58) thl: k -- lets ignore the question "remove pacakges from cvs or only orphan them later" (10:13:09) thl: maybe we could use a scheme like this: (10:13:25) thl: remove all packages that were not rebuild three weeks before FC6 (10:13:53) thl: and remove all those from cvs when the branch for FC6 happens, that don#t have a new maintainer yet (10:14:37) thl: so let's move on (10:14:47) dgilmore: thl: they stay in cvs but get flagged so they wont build (10:15:08) thl: dgilmore, could work, too (10:15:24) thl: how hard it restoring of deleted things? (10:15:43) thl: (in cvs) (10:15:48) c4chris: easy (10:15:50) dgilmore: harder than fixing a spec file set to not build (10:16:04) thl: let's stop here (10:16:13) thl: we can discuss this later (10:16:16) thl has changed the topic to: FESCo meeting in progress -- Use comps.xml properly (10:16:22) thl: c4chris, the nag mails worked great (10:16:29) c4chris: thl, yup (10:16:33) jwb: yes, they do (10:16:45) thl: dgilmore: automate comps file during push or via cron (10:16:49) c4chris: Now I have a few questions... (10:16:51) thl: dgilmore, did you look into this? (10:16:53) abadger1999: c4chris: I don't think I received any though (and I should have) (10:17:07) thl: ohh, shoot (dgilmore, we'll discuss this later) (10:17:08) c4chris: abadger1999, I'll check (10:17:12) dgilmore: thl: i was going to help who was but i cant rember who that was. (10:17:36) thl: dgilmore, probably scop -- he knows a lot of the push-script details (10:17:39) c4chris: Is there a plan to remove the group tag in spec files? (10:17:56) dgilmore: c4chris: not that i know of (10:18:02) abadger1999: c4chris: Packaging Committee talked about it today. (10:18:03) tibbs: Yes. (10:18:05) bpepple: c4chris: I think it's only be discussed so far. (10:18:29) c4chris: So it's on the PC agenda? (10:18:46) abadger1999: Won't happen for FC6 but we're coming up with a timeline to make it optional and then dropped. (10:19:03) c4chris: abadger1999, ok. Great. (10:19:35) c4chris: Another one is: can we have a hidden group in comps? (10:20:01) c4chris: I think it'd be way easier to tell people: add all your packages in comps (10:20:19) thl: that was my stupid idea -- I think there were hidden groups possible in the past (10:20:22) c4chris: (until the day we have a shiny package database, that is... :-) ) (10:21:00) abadger1999: Would be even better to have a hidden attribute. (10:21:15) c4chris: I'm afraid there's no automated way to decide which packages should appear in comps, no matter how hard we try (10:21:54) abadger1999: So if Fedora policy is not to have commandline tools generally, you can still put your application in and properly categorized but flagged to be hidden. (10:21:56) jima: all my packages are non-gui; only one (dnsmasq) seemed common enough for me to bother putting it in comps. (10:22:41) thl: jima, maybe a "command line tools" group would be a good idea (10:22:44) c4chris: IMHO, comps is a way to make some publicity for your package (10:22:56) rdieter: just put 'em all in there then (at least for now until a better solution magically appears) (10:23:02) jima: c4chris: if there's a category your package fits in. (10:23:03) c4chris: you went to the trouble of packaging it: why not advertise it somehow (10:23:17) thl: c4chris, +1 (10:23:35) thl: c4chris, we IMHO really need a real comps SIG (10:23:37) jima: (admittedly i only have one package that didn't fit perfectly into a category) (10:23:46) thl: or at least some people that really take care of it (10:23:57) thl: there were so many questions on f-e-l in the past days (10:24:02) c4chris: thl, yea probably (10:24:02) abadger1999: c4chris: Is there a plan to have groups in the package database? (Or a desire?) (10:24:09) thl: or should the PC handle comps? (10:24:28) c4chris: thl, it affects core too... (10:24:50) thl: yes and no (10:24:53) c4chris: abadger1999, not completely sure (10:25:11) thl: we IMHO need agroup that handles the comps stuff for extras and watches it over (10:25:11) abadger1999: It's not listed on the pages yet -- os if it's a desire, it needs to get listed. (10:25:22) bpepple: thl: +1 (10:25:22) abadger1999: s/os/so/ (10:25:22) c4chris: but the package database would be a nice place to put such attributes I think (10:25:39) rdieter: SIG++, it needs/deserves extra tlc (10:25:51) rdieter: it = comps (10:25:58) c4chris: tlc? (10:26:07) rdieter: tender loving care. (10:26:14) c4chris: Oh :-) (10:26:22) c4chris: yes! (10:26:25) thl: c4chris, well, seems you have a new job (10:26:39) thl: c4chris, can you find one or two more poeple for the sig? (10:26:46) c4chris: thl, k (10:26:49) ***bpepple would be willing to help/ (10:26:53) c4chris: Yup, I'll need help (10:26:59) c4chris: bpepple, thanks (10:27:17) bpepple: no prob. (10:27:17) thl: c4chris, anything else regarding comps we should discuss? (10:27:31) c4chris: thl, no I'm fine (10:27:40) c4chris: I'll start a wiki page soon(ish) (10:28:11) thl: k, so let's move on (10:28:23) thl: c4chris, can you update the status page on the schedule please? (10:28:33) thl: to reflect the recent discusssions? (10:28:35) c4chris: thl, will do (10:29:00) thl has changed the topic to: FESCo meeting in progress -- Activate legacy in buildroots (10:29:12) thl: dgilmore told me that it's not activated yet (10:29:20) thl: so I think we can skip this today (10:29:22) dgilmore: not yet (10:30:01) dgilmore: hopefully this week we can get everything in place. i need to setup legacy to use the buildsys first or they wont have fc4 ppc updates (10:30:13) thl has changed the topic to: FESCo meeting in progress -- CTRL-C problem (10:30:17) thl: skipping as well (10:30:20) thl: ohh (10:30:25) thl: or, no (10:30:38) thl: warren, did you bring it up in the last infrasctructure meeting? (10:30:51) warren: bad news (10:31:13) warren: It is the judgement of the infrastructure team that this simply is not a priority. (10:31:26) warren: If someone has ideas they're willing to try it. (10:31:35) warren: that is all. (10:31:52) thl: warren, not nice, but life sucks sometimes (10:32:02) thl: warren, related to this (10:32:14) thl: how is the schedule for the new VCS? (10:32:25) thl: are there detailsed plans yet? (10:32:30) warren: Infrastructure rather focus efforts on making VCS happen sooner than to improve the existing one. (10:32:43) thl: otherwise it'll be FC( until it's in place... (10:32:50) warren: late August two new servers will be installed, and we will simultaneously test mercurial and bazaar-ng (10:33:35) tibbs: That's great news. (10:33:59) warren: we're ordering a pretty sweet beefy box today (10:34:03) thl: warren, yeah, great (10:34:09) dgilmore: thl: from memory we hopped to have something ready for testing when FC7 test1 hits the streets (10:34:11) abadger1999: I've got the backend for a bzr implementation but we also need work done on the packaging database to work on a finished front end. (10:34:27) warren: 2x2 xeon, 8GB RAM, big SCSI drives. It should host a few xen guests comfortably for greater infrastructure flexibility. (10:34:41) jima: nice! (10:34:53) thl: k, let's stop here now and move on (10:35:06) thl has changed the topic to: FESCo meeting in progress -- Packaging Committee Report (10:35:34) abadger1999: We started discussion of removing the Group tag today. (10:35:54) abadger1999: Approved trying to get a patch into rpm to make the tag optional for FC6. (10:36:20) abadger1999: We'll look at the timeline for changing the guidelines based on when that makes it into rpm. (10:36:47) jima: if it's in by the time we're supposed to do the final mass-rebuild, i wouldn't have any qualms with removing the tag from my specs while i'm incrementing. (10:37:03) abadger1999: ldconfig wording on the Guidelines page was clarified but with the same meaning (10:37:08) c4chris: sounds cool (10:37:11) tibbs: jima: We're not targeting FC6 for this. (10:37:46) abadger1999: That's all for changes. (10:37:54) thl: abadger1999, thx (10:38:01) abadger1999: Oh -- we're talking about changing meeting date/time (10:38:10) abadger1999: But we're continuing that on the mailing list. (10:38:22) thl: I saw it roughly (10:38:29) thl: there was the problem with DST (10:38:50) thl: weco meets at 18:00 UTC during winters IIRC (10:38:57) thl: and 17:00 during summers (10:39:10) thl: so the effective meeting time stays the same (10:39:28) thl: s/weco/FESCo/ (10:39:43) thl: is that scheme fine for all the new FESCo members, too? (10:39:49) bpepple: Yup. (10:39:56) abadger1999: Yes. (10:40:00) c4chris: it's ok (10:40:03) tibbs: Yes. (10:40:14) rdieter: ok (10:40:16) thl: k (10:40:36) thl has changed the topic to: FESCo meeting in progress -- Sponsorship nominations (10:40:41) thl: any new nominations? (10:41:02) jwb: are we supposed to send them to FESCo list first? (10:41:06) thl: btw, someone really should send Nodoid a summary why we didn#t apporve him last time (10:41:18) c4chris: I don't get mails from the sponsor list (10:41:21) thl: does anyone still have the mails that were send around when we discussed it? (10:41:39) tibbs: I probably do. (10:41:46) thl: I'd like to porpose that we send it to both lists (10:41:56) thl: e.g. FESCo and sponsors (10:42:05) bpepple: thl: +1 (10:42:07) c4chris: thl, yup, that's be useful (10:42:08) thl: or we need to create a special mailinglist (10:42:16) thl: but that's probaly overkill (10:42:24) warren: any self-nominations? (10:42:39) thl: I'm wonering if we should make c4chris a sponsor (10:42:48) thl: FESCo members IMHO should also be sponsors (10:42:51) tibbs: I have everything sent to cvsextras-sponsors at fedoraproject.org since the beginning of May, BTW. (10:43:25) thl: tibbs, can you send me the discussions around upgrading nodoid? then I'l send him a summary why we didn't approve him (10:43:35) tibbs: Going by the top reviewiers, Patrice Dumas would up for sponsorship. (10:44:36) dgilmore: thl: honestly you could make me a sponser. but i dont know if i would be a good one (10:44:41) thl: tibbs, can you send a mail to the list to start the discussions (10:44:51) dgilmore: tibbs: thats bad not all of fesco get that (10:45:11) thl: dgilmore, you don't have to use your powers if you don't feel compfortable with it (10:45:33) thl: who else from FESCo isn't a sponsor? Currently c4chris and dgilmore afaics (10:46:09) thl: a lot of silence here (10:46:18) c4chris: I guess we are the only 2... (10:46:24) thl: seems poeple don't like the iea to make all FESCo members sponsors... (10:46:28) dgilmore: thl: i guess its just me and c4chris (10:46:52) thl: s/iea/iea/ (10:46:53) c4chris: the thing is I don't do that many reviews (10:46:56) thl: s/iea/idea/ (10:46:57) abadger1999: It's overloading the sponsorship role... (10:47:13) jima: i don't see the justification, personally. (10:47:27) thl: abadger1999, okay, so let's just drop that idea of mine (10:47:33) jima: sponsors become sponsors based on merit, don't they? (10:47:55) c4chris: yup, that's the idea (10:48:03) thl: jima, yes, but that merit doesn't always mean "reviews" (10:48:06) rdieter: Hopefully, FESCo implies merit... (: (10:48:12) c4chris: and a deep knowledge of the packaging rules... (10:48:13) thl: I didn't do to much reviews (10:48:15) dgilmore: i guess being in Fesco means your trusted by the community (10:48:20) thl: but I'm here and a sponsor, too (10:48:23) BobJensen is now known as BobJensen-Away (10:48:25) warren: I'm for giving them sponsorship, I trust that they would do the right thing. (10:48:34) rdieter: +1 (10:48:38) thl: +1 (10:48:41) bpepple: warren: +1 (10:48:54) abadger1999: I would give them sponsorship too -- but that's separate from making all FESCo members sponsors. (10:49:21) abadger1999: So c4chris, dgilmore sponsorship +1 (10:49:23) thl: abadger1999, yeah, your right (10:49:25) thl: abadger1999, +1 (10:49:37) c4chris: So you need to simple rule to always nominate DESCo members to sponsorship, and then simply debate it like usual... (10:50:02) jima: c4chris: that sounds better to me than just automatically upgrading them. (10:50:03) c4chris: s/D/F/ doh (10:50:15) tibbs: But the debate wouldn't necessarily be based on the number and quality of reviews. (10:50:20) jima: if they have merit, that's fine, imo. (10:50:38) thl: I'm counting 5 votes to make c4chris and dgilmore sponsors currently (four indirect) (10:50:49) thl: so I think they are accepted (10:50:58) thl: please yell now if you disagree (10:51:02) jima: otherwise sponsorship can be attained by winning a popularity contest (the fesco election) :) (10:51:03) tibbs: I don't have any problem with having more sponsors, but I am curious that we seem to have changed the qualifications. (10:51:38) thl: tibbs, as I said -- I also didn't do to much reviews (10:52:11) tibbs: Perhaps we can consider the qualifications at a future meeting. Because honestly we do need more active sponsors. (10:52:27) thl: tibbs, yeah (10:52:35) c4chris: tibbs, wouldn't be a bad idea (10:52:47) tibbs: In any case, +1 for both folks. (10:52:57) c4chris: that reminds me we need to discuss responsibilities at some point... (10:52:58) thl: I consider them accepted them (10:53:11) thl: s/them/then/ (10:53:23) thl: there must be something wrong with my keyboard today ;-) (10:53:23) tibbs: Do remember that you have to review in order to actually sponsor someone. (10:53:28) thl: so let's move on now (10:53:50) thl has changed the topic to: FESCo meeting in progress -- approve kmod's (10:54:01) thl: I didn#t get new request for approvals (10:54:13) c4chris: no wonder... (10:54:14) thl: and I didn#t find time to forward the zaptel issue to FAB (10:54:31) tibbs: Wasn't new kmod approval put on hold? (10:54:41) thl: let's get the other stuff around kmods sorted out first before we bring that on hte table again (10:55:03) c4chris: yea, my inbox needs a break... (10:55:12) bpepple: no doubt. (10:55:14) thl: :) (10:55:17) thl: so let's move on (10:55:30) thl has changed the topic to: FESCo meeting in progress -- MISC from schedule (10:55:41) thl has changed the topic to: FESCo meeting in progress -- MISC from schedule -- Proposal for (FC and) FE Package Review Request template (10:55:47) thl: https://www.redhat.com/archives/fedora-extras-list/2006-August/msg00361.html (10:55:50) thl: do we like the idea? (10:56:04) c4chris: yes (10:56:15) tibbs: Yes, the summary would be nice to have. (10:56:22) abadger1999: Makes sense to me. (10:56:27) tibbs: It would also be nice if people knew to remove the angle brackets. (10:56:44) c4chris: tibbs, yes (10:56:45) ***bpepple doesn't have a problem with it. (10:56:47) tibbs: I've found that it's not nearly as obvious to some folks as you'd think. (10:57:07) c4chris: maybe remove them from the template? (10:57:27) thl: c4chris, +1 (10:57:47) thl: so we consider this accepted? (10:57:49) bpepple: c4chris: +1 (10:57:57) c4chris: thl, +1 (10:58:03) rdieter: +1 (10:58:03) tibbs: +1 (10:58:06) bpepple: thl: +1 (10:58:14) thl: k, moving on (10:58:21) thl has changed the topic to: FESCo meeting in progress -- MISC from schedule -- create a FESCO user in the wiki that sends mails to the FESCo list and subscribe it to /Extras/Schedul.* in the wiki (10:58:29) thl: I send this to the fesco list (10:58:30) c4chris: who can update the template? (10:58:41) bpepple: thl: +1, this sounds like a good idea. (10:58:56) tibbs: Yes, this is definitely good. +1 (10:59:06) thl: c4chris, djb (or what was his nick?); I'll take care of it (10:59:07) c4chris: why not. I'm subscribed, but that would give us a log of things (10:59:17) c4chris: thl, k thx (10:59:18) abadger1999: +1 (10:59:26) rdieter: sounds good to me, +1 (10:59:34) c4chris: (for the next time the wiki crashes... :-P) (10:59:40) warren: Just do it (10:59:47) thl: k (11:00:06) thl has changed the topic to: FESCo meeting in progress -- MISC from schedule -- jwb suggested in #fedora-extras that we discuss the current kmod discusions (11:00:06) warren: would that user's e-mail address be the fesco list ? (11:00:16) thl: warren, yes (11:00:32) thl: I'd like to stay mostly quiet on the kmod stuff (11:00:34) thl: jwb, ? (11:00:49) jwb: actually (11:00:55) warren: The kmod issue.... is big and complicated. For this reason we scheduled tomorrow's meeting. But even then I don't think we will be successful. (11:01:16) warren: I am uncertain what to do at this point. (11:01:20) dgilmore: warren: ? toomorrows meeting (11:01:32) jwb: warren, yeah... what dgilmore said (11:01:47) tibbs: There's some sort of telephone conference scheduled. (11:01:57) warren: thinking to do it on IRC instead (11:01:57) jwb: with who? (11:01:59) warren: haven't decided yet (11:02:06) warren: see fedora-packaging for details (11:02:18) jwb: kmod is bigger than just packaging (11:02:25) warren: yes it is (11:02:50) jwb: we've got davej and dwmw2 saying they should die in Extras and Core all together (11:03:00) jwb: among others (11:03:02) dgilmore: I think that kmods are important for testing and proving things. but that perhaps it should have its own repo fedora-kmods make the user have a clear decission to make knowing that core kernel developers wont support them (11:03:28) jwb: dgilmore, that's what 3rd party repos are for (11:03:49) jwb: dgilmore, IMHO, an "unsupported" repo by the kernel devs cannot be part of the fedora project officially (11:03:54) warren: Those kinds of decisions are FPB's to make. (11:04:13) jwb: warren, that doesn't mean we don't get to make suggestions (11:04:41) abadger1999: If the guidelines are just for other repos, then the whole landscape of what's a good guideline changes. (11:04:55) jwb: agreed (11:05:23) jwb: i think this is a case where we either care enough to allow it in fedora repos, or we get off the pot and let 3rd party repos decide what they want to do (11:05:28) warren: If you truly care about the kmod issues, then please seriously participate in the fedora-packaging list discussions. (11:05:32) dgilmore: i think we could have a repo within fedora thats disablled by default where they can live (11:05:39) warren: Right now it is a big mess. (11:06:06) jwb: warren, i care more about having/not having modules in fedora to begin with (11:06:20) jwb: warren, i think that needs to be settled before any kind of packaging standard comes about (11:06:50) warren: OK, then that is defnitely something you need to bring to FAB (11:06:52) warren: are you on FAB? (11:07:06) jwb: which i realize is confusing because kmods already exist... where were davej and dwmw2 when kmods originated? (11:07:10) jwb: warren, yes. i can email FAB (11:07:30) warren: jwb, package committee and fesco decides mainly on technical details, you are asking about quasi-political policy (11:07:36) thl: jwb, davej was asked by jeremy for permission of the kmod stuff iirc (11:07:44) jwb: thl, that's what i thought (11:07:49) rdieter: gotta run, another meeting (fun). (11:07:52) jwb: ok, i'd like to take a vote really quick (11:07:59) rdieter: (ok, I'll wait) (11:08:02) jwb: who in FESCo thinks we should have kmods? (11:08:12) rdieter: have, vs. not have? (11:08:17) dgilmore: jwb: my vote is for a kmod repository (11:08:18) jwb: rdieter, right (11:08:22) rdieter: have +1. (11:08:27) tibbs: I'm undecided, sorry. (11:08:50) thl: from the political standpoint: not have (11:08:57) c4chris: I think we can have modules in Extras (11:08:59) ***rdieter runs... (11:09:04) rdieter is now known as rdieter_away (11:09:10) skvidal: rdieter_away: come back here (11:09:13) thl: but we compete with ubuntu and suse: and they have all the stuff, so we should have it, too (11:09:25) bpepple: have +1 (11:09:36) rdieter_away: skvidal: huh? (11:09:41) warren: I think the current kmod standard with its strict restrictions is a generally good thing. (11:09:53) dgilmore: i think we can but if its in its own repository then users will be more aware of what support they can expect (11:09:56) jwb: so in general, FESCo feels kmods should remain (11:10:01) warren: It isn't a "free ride" into Fedora with any kmod. it must satisfy requirements, and pressure is put to push things upstream. (11:10:02) thl: warren, maybe we shopuld put the "time restiction" back on the table, too (11:10:16) thl: e.g. allow each kmod in extras only for a certain time (11:10:20) rdieter_away is now known as rdieter (11:10:21) ***cweyl scrolls back and reads (11:10:24) tibbs: I think that from a user's standpoint having access under the Fedora umbrella to every module which does not violate the law is a good thing. (11:10:24) thl: three releases (11:10:45) thl: tibbs, we should work towards modules that get merged upstream (11:10:59) dgilmore: warren: which can only be done in a fedora project controlled repo. 3rd party repos == "no input from us" (11:11:00) tibbs: But maintenance is paramount and the argument of the kernel devs atainst having to deal with bug reports arising from external modules is compelling. (11:11:11) thl: It's really important that they get merged into the vanilla kernel (11:11:16) tibbs: thl: I disagree; I don't think it's our business to push any code author towards anything they don't want to do. (11:11:56) thl: tibbs, http://www.fedoraproject.org/wiki/Objectives : To do as much of the development work as possible directly in the upstream packages. (11:12:12) bpepple: thl: +1 (11:12:16) tibbs: I don't see how that applies. (11:12:28) tibbs: A kernel module's upstream isn't necessarily the kernel. (11:12:32) dgilmore: thl: yes but a kmod upstream is different to kernel upstream (11:12:40) abadger1999: tibbs: +1 (11:12:48) tibbs: That objective just says we shouldn't carry around fedora-specific patches in fedora packages. (11:13:06) cweyl: tibbs: +1 on "...is a good thing" (11:13:08) dgilmore: thl: if we patch a kmod we should get it upstream whereever that is (11:13:16) warren: The way spot describes it, the restrictions set by packaging committee on what qualifies for kmod is strict. (11:13:34) jwb: thl, i'll email FAB asking for a political decision (11:13:42) thl: jwb, thx (11:13:49) ***jwb steps away for a second (11:13:51) thl: so let's stop here for today (11:14:02) warren: The time requirement is not exactly important to decide now, it is closer to a political decision. The bigger problem is the technical issues for the near-term. (11:14:03) thl has changed the topic to: FESCo meeting in progress -- free discussion (11:14:16) tibbs: I started on http://fedoraproject.org/wiki/JasonTibbitts/MaintainerResponsibilityPolicy (11:14:16) thl: anything else we should discuss? (11:14:40) tibbs: A nice rat's nest there which will require a good bit of spirited discussion. (11:14:56) tibbs: I'd like to see anyone interested contribute to that document. (11:15:34) thl: tibbs, can you move that over to the FESCo namespace please (11:15:36) tibbs: Unfortunately my wiki-fu is still crap and I can't get the list indentation right. (11:15:44) thl: then I'll create a entry on the schedule (11:15:50) rdieter is now known as rdieter_away (11:16:00) tibbs: Where would you like it to live? (11:16:08) tibbs: Under Schedule? (11:16:45) thl: tibbs, let me handle the moving (11:16:55) thl: I can also look at the list indentation (11:17:16) cweyl: tibbs: I assume rabble contributions are good as well? (11:17:24) tibbs: I was trying to get too fancy with boxed bits within a list. (11:17:36) tibbs: cweyl: I want to see as much input on this kind of thing as is possible. (11:17:42) cweyl: cool. (11:17:42) c4chris: cweyl, sure (11:18:13) cweyl: not that I've ever asked before.... ;) (11:18:29) c4chris: FYI I won't be here next week (vacations, yay! :-) ) (11:18:37) jima: err, can rabble edit things under FESCo namespace? (11:18:47) thl: jima, yes (11:19:02) jima: ok, wasn't sure if it was locked down like Packaging (11:19:09) cweyl: yah. same here (11:19:20) tibbs: Packaging is an anomaly, I think. (11:19:32) jima: ok (11:19:40) tibbs: You just need to be in EditGroup. (11:20:25) thl: k, anything else? (11:20:31) ***thl needs to leave soon (11:20:41) thl: abadger1999, btw, many thx for writing the summaries (11:20:48) tibbs: Nothing else from me. (11:20:53) ***thl will close the meeting in 60 (11:21:17) abadger1999: jima: BTW: PackagingDrafts shouldn't be locked down, just the actual Packaging hierarchy. (11:21:21) ***thl will close the meeting in 30 (11:21:28) abadger1999: thl: np. (11:21:41) ***thl will close the meeting in 10 (11:21:53) thl: -- MARK -- Meeting end (11:21:57) thl: thx everyone! (11:22:03) c4chris: thl, thx. }}} -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From dominik at greysector.net Sat Aug 19 00:30:53 2006 From: dominik at greysector.net (Dominik 'Rathann' Mierzejewski) Date: Sat, 19 Aug 2006 02:30:53 +0200 Subject: FC-4 branch request In-Reply-To: References: <44DCB02F.8070605@leemhuis.info> <20060818220308.GB5346@rathann.pekin.waw.pl> Message-ID: <20060819003053.GA6616@rathann.pekin.waw.pl> On Saturday, 19 August 2006 at 01:48, Jason L Tibbitts III wrote: > >>>>> "DM" == Dominik Mierzejewski writes: > > DM> I'd like to request FC-4 branch for crm114. > > Could you give a reason why this needs to be branched for FC4? Well, the whole point of getting tre into FE was to get crm114 in, too. Granted, tre (and agrep) are useful on their own, but without crm114 it feels like stopping half-way and leaving unfinished work to me. As I said, I managed to slip tre in around the time it became Legacy, but crm114 couldn't make it in time. I'm sure Jima would concur, as he was interested in both of these, too. Regards, R. -- Fedora Extras contributor http://fedoraproject.org/wiki/DominikMierzejewski MPlayer developer http://rpm.greysector.net/mplayer/ "Faith manages." -- Delenn to Lennier in Babylon 5:"Confessions and Lamentations" From jima at beer.tclug.org Sat Aug 19 02:03:07 2006 From: jima at beer.tclug.org (Jima) Date: Fri, 18 Aug 2006 21:03:07 -0500 (CDT) Subject: FC-4 branch request In-Reply-To: <20060819003053.GA6616@rathann.pekin.waw.pl> References: <44DCB02F.8070605@leemhuis.info> <20060818220308.GB5346@rathann.pekin.waw.pl> <20060819003053.GA6616@rathann.pekin.waw.pl> Message-ID: On Sat, 19 Aug 2006, Dominik 'Rathann' Mierzejewski wrote: > As I said, I managed to slip tre in around the time it became Legacy, > but crm114 couldn't make it in time. > > I'm sure Jima would concur, as he was interested in both of these, too. I don't think my opinion counts for all that much, but yes, I was trying to help get crm114 into Extras for a LUG colleague. Alas, things got delayed on my end, so I can't complain too loudly. Jima From j.w.r.degoede at hhs.nl Sat Aug 19 09:29:41 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Sat, 19 Aug 2006 11:29:41 +0200 Subject: FESCo Meeting Minutes for 2006-08-17 In-Reply-To: <1155944907.2982.22.camel@localhost> References: <1155944907.2982.22.camel@localhost> Message-ID: <44E6DA05.9080708@hhs.nl> Toshio Kuratomi wrote: > * AWOL package process started for ignacio as he has a bunch of > packages that others might have to pick up as dependencies. > Ouch, may I ask what the story is here? Judging from the list of packages he maintains (search for ivazquez at ivazquez.net in owners.list). He is (once was ?) a very active FE member, I don't think we want to loose him. I also feel that the AWOL process was not created for the likes of him, but more for Johnny 1-shot package. So what is the story? Is he completly not responding? Or? I would really like to know if there are personal circumstances (in which case there is nothing we can do) or if for some reason he and FE have grown apart, and if tis the latter why? Hopefully we can keep him aboard and at the very least we should learn from this. Regards, Hans From fedora at leemhuis.info Sat Aug 19 10:44:12 2006 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Sat, 19 Aug 2006 12:44:12 +0200 Subject: FESCo Meeting Minutes for 2006-08-17 In-Reply-To: <44E6DA05.9080708@hhs.nl> References: <1155944907.2982.22.camel@localhost> <44E6DA05.9080708@hhs.nl> Message-ID: <44E6EB7C.4080709@leemhuis.info> Hans de Goede schrieb: > > Toshio Kuratomi wrote: >> * AWOL package process started for ignacio as he has a bunch of >> packages that others might have to pick up as dependencies. > Ouch, may I ask what the story is here? Judging from the list of > packages he maintains (search for ivazquez at ivazquez.net in owners.list). > He is (once was ?) a very active FE member, I don't think we want to > loose him. Agreed, that why warren offered to call him via telephone; look at the full IRC log for details: (10:10:58) abadger1999: For ignacio specifically, has the AWOL packagers process been started? (10:11:26) dgilmore: abadger1999: no but it really needs to (10:11:32) jwb: agreed (10:11:41) bpepple: dgilmore: +1 (10:11:48) warren: Want me to attempt to use non-email to contact him? (10:11:52) BobJensen: dgilmore: +1 (10:11:57) warren: Ask him what he wants us to do with his packages. (10:12:00) abadger1999: warren: +1 (10:12:05) thl: warren, maybe that would be a good idea (10:12:08) c4chris: warren, +1 (10:12:09) Daveman: :o (10:12:15) tibbs: If someone has his phone number, it would certainly be a good idea to try it. (10:12:21) BobJensen: I tried calling all I got was VM (10:12:36) Daveman: FC6? (10:12:36) dgilmore: warren: +1 (10:12:42) warren: I'll give it a try. > I also feel that the AWOL process was not created for the > likes of him, but more for Johnny 1-shot package. > > So what is the story? Is he completly not responding? Or? I would really > like to know if there are personal circumstances (in which case there is > nothing we can do) or if for some reason he and FE have grown apart, and > if tis the latter why? Hopefully we can keep him aboard and at the very > least we should learn from this. I currently prefer a solution like this if he doesn't show up again in time: Interested contributors take over his packages for now; when he shows up again he gets them back (if he wants them back). CU thl From Christian.Iseli at licr.org Sat Aug 19 10:47:34 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Sat, 19 Aug 2006 12:47:34 +0200 Subject: FESCo Meeting Minutes for 2006-08-17 In-Reply-To: <44E6DA05.9080708@hhs.nl> References: <1155944907.2982.22.camel@localhost> <44E6DA05.9080708@hhs.nl> Message-ID: <20060819124734.30928c02@ludwig-alpha> On Sat, 19 Aug 2006 11:29:41 +0200, Hans de Goede wrote: > So what is the story? Is he completly not responding? Yes, that's the thing: no email replied, no phone answered, nothing... :-( warren promised he'd keep trying, so we'll see Cheers, Christian From Christian.Iseli at licr.org Sat Aug 19 16:12:34 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Sat, 19 Aug 2006 18:12:34 +0200 Subject: comps comps-fe6.xml,1.13,1.14 In-Reply-To: <200608191032.k7JAWHX3030206@cvs-int.fedora.redhat.com> References: <200608191032.k7JAWHX3030206@cvs-int.fedora.redhat.com> Message-ID: <20060819181234.0a9c31d9@ludwig-alpha> On Sat, 19 Aug 2006 03:32:15 -0700, Tim Jackson wrote: > Modified Files: > comps-fe6.xml Please update comps-fe6.xml.in (*not* comps-fe6.xml) otherwise your changes will be lost next time comps-fe6.xml is rebuilt from the .in file... Cheers, Christian From steve at silug.org Sat Aug 19 16:50:12 2006 From: steve at silug.org (Steven Pritchard) Date: Sat, 19 Aug 2006 11:50:12 -0500 Subject: FESCo Meeting Minutes for 2006-08-17 In-Reply-To: <44E6DA05.9080708@hhs.nl> References: <1155944907.2982.22.camel@localhost> <44E6DA05.9080708@hhs.nl> Message-ID: <20060819165012.GA23627@osiris.silug.org> On Sat, Aug 19, 2006 at 11:29:41AM +0200, Hans de Goede wrote: > Ouch, may I ask what the story is here? Judging from the list of > packages he maintains (search for ivazquez at ivazquez.net in owners.list). > He is (once was ?) a very active FE member, I don't think we want to > loose him. I also feel that the AWOL process was not created for the > likes of him, but more for Johnny 1-shot package. He doesn't have that many bugs open: https://bugzilla.redhat.com/bugzilla/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&emailassigned_to1=1&emailtype1=exact&email1=ivazquez%40ivazquez.net Maybe anyone interested should jump in and start trying to fix those? (I was hoping something would jump out at me, but I think I've only used a couple of his packages.) Steve -- Steven Pritchard - K&S Pritchard Enterprises, Inc. Email: steve at kspei.com http://www.kspei.com/ Phone: (618)398-3000 Mobile: (618)567-7320 From paul at all-the-johnsons.co.uk Sat Aug 19 17:31:55 2006 From: paul at all-the-johnsons.co.uk (Paul) Date: Sat, 19 Aug 2006 18:31:55 +0100 Subject: Appending a file in %{_sysconfdir} In-Reply-To: <200608181706.18411.jkeating@redhat.com> References: <1155910494.2548.9.camel@localhost.localdomain> <200608181706.18411.jkeating@redhat.com> Message-ID: <1156008716.1841.0.camel@T7.Linux> Hi, > Danger Will Robinson! Fiddling with file content, especially config files is > bad juju. What you should really do is work with the mono packager to make > a %{_sysconfdir}/mono/config.d/ directory that packages can drop config stubs > into and remove from. We learned long ago trying to fiddle with file > contents is just a bad idea. I take it that's alexl still - I thought he wanted to drop it. TTFN Paul -- "Ist du meine Mutter?" - der leerkinde -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Matt_Domsch at dell.com Sat Aug 19 19:02:11 2006 From: Matt_Domsch at dell.com (Matt Domsch) Date: Sat, 19 Aug 2006 14:02:11 -0500 Subject: Extras x86_64 rawhide rebuild in mock status 2006-08-19 Message-ID: <20060819140211.A1162@humbolt.us.dell.com> Extras Rawhide-in-Mock Build Results for x86_64 Sat Aug 19 13:45:32 CDT 2006 Note: This is using a reduced set of packages in the build chroot starting with FC6test2. See http://fedoraproject.org/wiki/QA/FixBuildRequires for more information, including the list of packages removed from the default build chroot. Open Bugs which now build, and can be marked CLOSED RAWHIDE: argus-2.0.6.fixes.1-11.fc6 197215 NEW bidiv-1.5-3.fc5 197224 NEW flow-tools-0.68-10.fc6 197706 NEW gtktalog 198897 NEW libtomoe-gtk-0.1.0-6.fc6 200114 NEW Number failed to build: 90 Number expected to fail due to ExclusiveArch or ExcludeArch: 23 Leaving: 67 (there may be some duplicates if rawhide has 2 versions of a package) Of those expected to have worked... Without a bug filed: 49 ---------------------------------- atitvout-0.4-5 andreas.bierfert at lowlatency.de boo-0.7.6.2237-8.fc6 paul at all-the-johnsons.co.uk camstream-0.26.3-9.fc5 nomis80 at nomis80.org contact-lookup-applet-0.14-3.fc6 bdpepple at ameritech.net digikam-0.8.2-2.fc6 mgarski at post.pl directfb-0.9.24-5.fc5 thomas at apestaart.org ebtables-2.0.8-0.5.rc1.fc6 tcallawa at redhat.com epiphany-extensions-2.14.1-1 caillon at redhat.com foobillard-3.0a-4 mitr at redhat.com gif2png-2.5.1-2.fc5 enrico.scholz at informatik.tu-chemnitz.de gobby-0.4.0-6.rc2.fc6 lmacken at redhat.com gstreamer08-python-0.8.4-1.fc5 thomas at apestaart.org gtk2hs-0.9.10-2.fc6 petersen at redhat.com GtkAda-2.4.0-11.fc5 gemi at bluewin.ch gtksourceview-sharp-2.0-15.fc6 paul at all-the-johnsons.co.uk ifplugd-0.24-6 aaron.bennett at olin.edu john-1.6-4 ghenry at suretecsystems.com kmymoney2-0.8.4-1.fc6 rdieter at math.unl.edu ladspa-1.12-5 thomas at apestaart.org libpolyxmass-0.9.0-6.fc5 andreas.bierfert at lowlatency.de MagicPoint-1.11b-2.fc5 byte at fedoraproject.org mlton-20051202-8.fc6 adam at spicenitz.org monodevelop-0.11-16.fc6 paul at all-the-johnsons.co.uk nautilus-open-terminal-0.7-1.fc6 stickster at gmail.com new-1.3.7-2 redhat at flyn.org pam_keyring-0.0.7-2 redhat at flyn.org php-pear-DB-1.7.6-6 rpm at timj.co.uk pl-5.6.16-1.fc6 gemi at bluewin.ch python-goopy-0.1-1 pjones at redhat.com python-reportlab-1.20-5.fc5 bdpepple at ameritech.net python-TestGears-0.2-1.fc5 ivazquez at ivazquez.net quarry-0.1.16-2.fc5 michel.salim at gmail.com rpmDirectoryCheck-0.8-2 enrico.scholz at informatik.tu-chemnitz.de scanssh-2.1-6.fc5 oliver at linux-kernel.at SDL_ttf-2.0.7-4.fc5 bdpepple at ameritech.net ser-0.9.6-7.fc6 andreas at bawue.net serpentine-0.7-3.fc6 foolish at guezz.net stratagus-2.1-5.fc6 lemenkov at newmail.ru synce-0.9.1-7.fc5 andreas.bierfert at lowlatency.de synce-software-manager-0.9.0-5.fc5 andreas.bierfert at lowlatency.de synce-trayicon-0.9.0-6.fc5 andreas.bierfert at lowlatency.de WindowMaker-0.92.0-8.fc5 andreas.bierfert at lowlatency.de wlassistant-0.5.5-1.fc5 tcallawa at redhat.com wv2-0.2.3-1.fc6 andreas.bierfert at lowlatency.de xaos-3.2.1-3.fc6 gemi at bluewin.ch xbsql-0.11-6.fc6 tcallawa at redhat.com xcin-2.5.3.pre3-27 llch at redhat.com xplanet-1.0.1-7 jylitalo at iki.fi xsupplicant-1.2.6-1.fc6 tcallawa at redhat.com With bugs filed: 18 ---------------------------------- alacarte-0.8-7.fc5 ['194250 NEW'] jpmahowald at gmail.com banshee-0.10.11-1.fc6 ['194505 NEW'] caillon at redhat.com cowbell-0.2.7.1-2.fc6 ['197366 CLOSED'] foolish at guezz.net dillo-0.8.6-2.fc6 ['197370 CLOSED'] andreas.bierfert at lowlatency.de gdesklets-0.35.3-8.fc6 ['197799 NEW'] luya_tfz at thefinalzone.com gnome-applet-music-0.9.0-1.fc6 ['197924 NEW'] ivazquez at ivazquez.net gnome-schedule-1.0.0-1 ['197927 NEW'] frank at scirocco-5v-turbo.de grhino-0.15.0-5.fc5 ['197950 NEW'] michel.salim at gmail.com jam-2.5-3.fc5 ['198924 NEW'] tcallawa at redhat.com leafpad-0.8.9-1.fc6 ['200088 NEW'] ivazquez at ivazquez.net libtabe-0.2.6-14 ['200104 NEW'] llch at redhat.com logjam-4.5.3-4.fc6 ['200387 NEW'] tcallawa at redhat.com multisync-0.90.18-5.fc5 ['200399 ASSIGNED'] andreas.bierfert at lowlatency.de nautilus-search-tool-0.2-1.fc5 ['200420 NEW'] ivazquez at ivazquez.net nco-3.1.2-1.fc6 ['193541 NEW'] ed at eh3.com NetworkManager-vpnc-0.7.0-0.cvs20060529.1.fc6 ['200424 NEW'] davidz at redhat.com ngrep-1.44-4.fc5 ['200429 NEW'] oliver at linux-kernel.at opencv-0.9.7-15.fc5 ['200788 NEW'] nomis80 at nomis80.org Full logs at http://linux.dell.com/files/fedora/FixBuildRequires/ -- Matt Domsch Software Architect Dell Linux Solutions linux.dell.com & www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com From Matt_Domsch at dell.com Sat Aug 19 19:02:54 2006 From: Matt_Domsch at dell.com (Matt Domsch) Date: Sat, 19 Aug 2006 14:02:54 -0500 Subject: Extras i386 rawhide rebuild in mock status 2006-08-19 Message-ID: <20060819140254.A1210@humbolt.us.dell.com> Extras Rawhide-in-Mock Build Results for i386 Sat Aug 19 13:49:40 CDT 2006 Note: This is using a reduced set of packages in the build chroot starting with FC6test2. See http://fedoraproject.org/wiki/QA/FixBuildRequires for more information, including the list of packages removed from the default build chroot. Open Bugs which now build, and can be marked CLOSED RAWHIDE: argus-2.0.6.fixes.1-11.fc6 197215 NEW bidiv-1.5-3.fc5 197224 NEW flow-tools-0.68-10.fc6 197706 NEW gtktalog 198897 NEW libtomoe-gtk-0.1.0-6.fc6 200114 NEW Number failed to build: 67 Number expected to fail due to ExclusiveArch or ExcludeArch: 1 Leaving: 66 (there may be some duplicates if rawhide has 2 versions of a package) Of those expected to have worked... Without a bug filed: 46 ---------------------------------- boo-0.7.6.2237-8.fc6 paul at all-the-johnsons.co.uk camstream-0.26.3-9.fc5 nomis80 at nomis80.org contact-lookup-applet-0.14-3.fc6 bdpepple at ameritech.net digikam-0.8.2-2.fc6 mgarski at post.pl directfb-0.9.24-5.fc5 thomas at apestaart.org ebtables-2.0.8-0.5.rc1.fc6 tcallawa at redhat.com epiphany-extensions-2.14.1-1 caillon at redhat.com gif2png-2.5.1-2.fc5 enrico.scholz at informatik.tu-chemnitz.de gobby-0.4.0-6.rc2.fc6 lmacken at redhat.com gstreamer08-python-0.8.4-1.fc5 thomas at apestaart.org gtk2hs-0.9.10-2.fc6 petersen at redhat.com GtkAda-2.4.0-11.fc5 gemi at bluewin.ch gtksourceview-sharp-2.0-15.fc6 paul at all-the-johnsons.co.uk ifplugd-0.24-6 aaron.bennett at olin.edu john-1.6-4 ghenry at suretecsystems.com kmymoney2-0.8.4-1.fc6 rdieter at math.unl.edu ladspa-1.12-5 thomas at apestaart.org MagicPoint-1.11b-2.fc5 byte at fedoraproject.org mfstools-2.0-9.snapshot050221.fc5 tcallawa at redhat.com monodevelop-0.11-16.fc6 paul at all-the-johnsons.co.uk nautilus-open-terminal-0.7-1.fc6 stickster at gmail.com orange-0.3-1.cvs20051118.fc6 andreas.bierfert at lowlatency.de pam_keyring-0.0.7-2 redhat at flyn.org perl-POE-Component-Client-HTTP-0.77-2.fc6 (fixed in CVS) pl-5.6.16-1.fc6 gemi at bluewin.ch python-goopy-0.1-1 pjones at redhat.com python-TestGears-0.2-1.fc5 ivazquez at ivazquez.net quarry-0.1.16-2.fc5 michel.salim at gmail.com rpmDirectoryCheck-0.8-2 enrico.scholz at informatik.tu-chemnitz.de scanssh-2.1-6.fc5 oliver at linux-kernel.at SDL_ttf-2.0.7-4.fc5 bdpepple at ameritech.net ser-0.9.6-7.fc6 andreas at bawue.net serpentine-0.7-3.fc6 foolish at guezz.net stratagus-2.1-5.fc6 lemenkov at newmail.ru syck-0.55-7.fc5 oliver at linux-kernel.at synce-0.9.1-7.fc5 andreas.bierfert at lowlatency.de synce-software-manager-0.9.0-5.fc5 andreas.bierfert at lowlatency.de synce-trayicon-0.9.0-6.fc5 andreas.bierfert at lowlatency.de WindowMaker-0.92.0-8.fc5 andreas.bierfert at lowlatency.de wlassistant-0.5.5-1.fc5 tcallawa at redhat.com wv2-0.2.3-1.fc6 andreas.bierfert at lowlatency.de xaos-3.2.1-3.fc6 gemi at bluewin.ch xbsql-0.11-6.fc6 tcallawa at redhat.com xcin-2.5.3.pre3-27 llch at redhat.com xplanet-1.0.1-7 jylitalo at iki.fi xsupplicant-1.2.6-1.fc6 tcallawa at redhat.com With bugs filed: 20 ---------------------------------- alacarte-0.8-7.fc5 ['194250 NEW'] jpmahowald at gmail.com amaya-9.5-1.fc6 ['195652 NEW'] paul at all-the-johnsons.co.uk banshee-0.10.11-1.fc6 ['194505 NEW'] caillon at redhat.com cowbell-0.2.7.1-2.fc6 ['197366 CLOSED'] foolish at guezz.net dillo-0.8.6-2.fc6 ['197370 CLOSED'] andreas.bierfert at lowlatency.de gdesklets-0.35.3-8.fc6 ['197799 NEW'] luya_tfz at thefinalzone.com gnome-applet-music-0.9.0-1.fc6 ['197924 NEW'] ivazquez at ivazquez.net gnome-schedule-1.0.0-1 ['197927 NEW'] frank at scirocco-5v-turbo.de grhino-0.15.0-5.fc5 ['197950 NEW'] michel.salim at gmail.com jam-2.5-3.fc5 ['198924 NEW'] tcallawa at redhat.com leafpad-0.8.9-1.fc6 ['200088 NEW'] ivazquez at ivazquez.net librx-1.5-6.fc5 ['200090 NEW'] tcallawa at redhat.com libtabe-0.2.6-14 ['200104 NEW'] llch at redhat.com logjam-4.5.3-4.fc6 ['200387 NEW'] tcallawa at redhat.com multisync-0.90.18-5.fc5 ['200399 ASSIGNED'] andreas.bierfert at lowlatency.de nautilus-search-tool-0.2-1.fc5 ['200420 NEW'] ivazquez at ivazquez.net nco-3.1.2-1.fc6 ['193541 NEW'] ed at eh3.com NetworkManager-vpnc-0.7.0-0.cvs20060529.1.fc6 ['200424 NEW'] davidz at redhat.com ngrep-1.44-4.fc5 ['200429 NEW'] oliver at linux-kernel.at opencv-0.9.7-15.fc5 ['200788 NEW'] nomis80 at nomis80.org Full logs at http://linux.dell.com/files/fedora/FixBuildRequires/ -- Matt Domsch Software Architect Dell Linux Solutions linux.dell.com & www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com From fedora at theholbrooks.org Sat Aug 19 19:28:42 2006 From: fedora at theholbrooks.org (Brandon Holbrook) Date: Sat, 19 Aug 2006 14:28:42 -0500 Subject: FESCo Meeting Minutes for 2006-08-17 In-Reply-To: <20060819165012.GA23627@osiris.silug.org> References: <1155944907.2982.22.camel@localhost> <44E6DA05.9080708@hhs.nl> <20060819165012.GA23627@osiris.silug.org> Message-ID: <44E7666A.9050907@theholbrooks.org> Steven Pritchard wrote: > On Sat, Aug 19, 2006 at 11:29:41AM +0200, Hans de Goede wrote: > >> Ouch, may I ask what the story is here? Judging from the list of >> packages he maintains (search for ivazquez at ivazquez.net in owners.list). >> He is (once was ?) a very active FE member, I don't think we want to >> loose him. I also feel that the AWOL process was not created for the >> likes of him, but more for Johnny 1-shot package. >> > > He doesn't have that many bugs open: > > https://bugzilla.redhat.com/bugzilla/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&emailassigned_to1=1&emailtype1=exact&email1=ivazquez%40ivazquez.net > > Maybe anyone interested should jump in and start trying to fix those? > > (I was hoping something would jump out at me, but I think I've only > used a couple of his packages.) > > Steve > I've gone ahead and answered https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198564 for Ignacio's php-json package. Bumped to latest upstream and successfully built. Are we ready to go ahead and start the 3-day FESco-approval-with-no-objections for his packages? Anybody else interested in php-json? Also, it seems since my sponsorship a little over a week ago I still don't have any rights in bugzilla. How long does it take for new packages (php-shout) to appear and new contributors (fedora at theholbrooks.org) to get rights? -Brandon From bpepple at fedoraproject.org Sat Aug 19 20:16:02 2006 From: bpepple at fedoraproject.org (Brian Pepple) Date: Sat, 19 Aug 2006 16:16:02 -0400 Subject: FESCo Meeting Minutes for 2006-08-17 In-Reply-To: <44E7666A.9050907@theholbrooks.org> References: <1155944907.2982.22.camel@localhost> <44E6DA05.9080708@hhs.nl> <20060819165012.GA23627@osiris.silug.org> <44E7666A.9050907@theholbrooks.org> Message-ID: <1156018562.13715.2.camel@shuttle.piedmont.com> On Sat, 2006-08-19 at 14:28 -0500, Brandon Holbrook wrote: > I've gone ahead and answered > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198564 for > Ignacio's php-json package. Bumped to latest upstream and successfully > built. Are we ready to go ahead and start the 3-day > FESco-approval-with-no-objections for his packages? Anybody else > interested in php-json? > > Also, it seems since my sponsorship a little over a week ago I still > don't have any rights in bugzilla. How long does it take for new > packages (php-shout) to appear and new contributors > (fedora at theholbrooks.org) to get rights? The process for AWOL contributors is here: http://fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers Since we just started the AWOL process for Ignacio, it seems you request is a bit premature. /B -- Brian Pepple gpg --keyserver pgp.mit.edu --recv-keys 810CC15E BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From bugs.michael at gmx.net Sat Aug 19 20:36:53 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Sat, 19 Aug 2006 22:36:53 +0200 Subject: Ignacio / php-json (was: Re: FESCo Meeting...) In-Reply-To: <44E7666A.9050907@theholbrooks.org> References: <1155944907.2982.22.camel@localhost> <44E6DA05.9080708@hhs.nl> <20060819165012.GA23627@osiris.silug.org> <44E7666A.9050907@theholbrooks.org> Message-ID: <20060819223653.ce67f8cb.bugs.michael@gmx.net> On Sat, 19 Aug 2006 14:28:42 -0500, Brandon Holbrook wrote: > >> Ouch, may I ask what the story is here? Judging from the list of > >> packages he maintains (search for ivazquez at ivazquez.net in owners.list). > I've gone ahead and answered > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198564 for > Ignacio's php-json package. Bumped to latest upstream and successfully > built. Important: I've excluded the results of this build job from the next push. If you read the bug report, the reporter mentions that Ignacio has published a working/newer version for FC5. Your changes to the devel branch in CVS differ from Ignacio's FC-5 version. Further, you mention a "New Maintainer" in the %changelog, which is not official yet for this package, is it? I'd like to see the following policy in action http://fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers rather than an immediate package take-over. Sorry for the pain. > Are we ready to go ahead and start the 3-day > FESco-approval-with-no-objections for his packages? Anybody else > interested in php-json? > > Also, it seems since my sponsorship a little over a week ago I still > don't have any rights in bugzilla. Have you joined fedora_bugs group? > How long does it take for new > packages (php-shout) to appear Build job 14359 won't appear, since I moved the results out of the needsign queue. I can restore the results, but would like to see an official "okay". Other jobs are published as soon as they are signed and pushed by somebody. Today's push is in progress, btw. From fedora at theholbrooks.org Sat Aug 19 20:57:10 2006 From: fedora at theholbrooks.org (Brandon Holbrook) Date: Sat, 19 Aug 2006 15:57:10 -0500 Subject: Ignacio / php-json In-Reply-To: <20060819223653.ce67f8cb.bugs.michael@gmx.net> References: <1155944907.2982.22.camel@localhost> <44E6DA05.9080708@hhs.nl> <20060819165012.GA23627@osiris.silug.org> <44E7666A.9050907@theholbrooks.org> <20060819223653.ce67f8cb.bugs.michael@gmx.net> Message-ID: <44E77B26.7000101@theholbrooks.org> Michael Schwendt wrote: > On Sat, 19 Aug 2006 14:28:42 -0500, Brandon Holbrook wrote: > > >>>> Ouch, may I ask what the story is here? Judging from the list of >>>> packages he maintains (search for ivazquez at ivazquez.net in owners.list). >>>> > > > >> I've gone ahead and answered >> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198564 for >> Ignacio's php-json package. Bumped to latest upstream and successfully >> built. >> > > Important: I've excluded the results of this build job from the next push. > > If you read the bug report, the reporter mentions that Ignacio has > published a working/newer version for FC5. Your changes to the devel > branch in CVS differ from Ignacio's FC-5 version. Further, you mention > a "New Maintainer" in the %changelog, which is not official yet for > this package, is it? I'd like to see the following policy in action > > ...I guess I'm a little confused here. The bug reports mentions nothing about a working version for FC5, only that a working version of 1.2.1 is in FEdevel and the requestor would like to see that update backported for FC5, which I did. Granted, I also did some general housekeeping while I was in there, like consistent macro usage and the new PHP Macros approved by the Packaging Committe. I wasn't trying to be misleading by putting "New Maintainer" in the changelog, I just wanted to highlight the fact that I was a different guy from the previous maintainer. Are these what you are referring to by "changes that differ"? I haven't made any changes to the devel branch, although I was considering applying the same PHP housekeeping. I'll put everything on hold until this gets explored a little further. > http://fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers > > rather than an immediate package take-over. Sorry for the pain. > > Which is why I asked if we were ready for the takeover process, rather than assuming so. When somebody suggested that we start taking bug reports, I though that might mean we had jumped to the package takeover, so I asked for clarification. >> Are we ready to go ahead and start the 3-day >> FESco-approval-with-no-objections for his packages? Anybody else >> interested in php-json? >> >> Also, it seems since my sponsorship a little over a week ago I still >> don't have any rights in bugzilla. >> > > Have you joined fedora_bugs group? > > That was my problem, I joined "fedorabugs" instead of "fedora_bugs". Now when I try to join fedora_bugs I get a Python AttributeError in get_allowed_group_actions(). >> How long does it take for new >> packages (php-shout) to appear >> > > Build job 14359 won't appear, since I moved the results out of the > needsign queue. I can restore the results, but would like to see an > official "okay". Other jobs are published as soon as they are signed and > pushed by somebody. Today's push is in progress, btw. > No sweat :) From buildsys at fedoraproject.org Sat Aug 19 21:26:01 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Sat, 19 Aug 2006 17:26:01 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-19 Message-ID: <20060819212601.86B6A152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 53 abook-0.5.6-2.fc5 abuse-0.7.0-1.fc5 bygfoot-2.0.0-2.fc5 bzrtools-0.9.1-1.fc5 conexus-0.3.0-1.fc5 conserver-8.1.14-3.fc5.1 convmv-1.10-1.fc5 crm114-0-0.1.20060704.fc5 digikam-0.8.2-2.fc5 dnsmasq-2.33-1.fc5 fRaBs-2.10-1.fc5 gallery2-2.1-0.24.svn20060817.fc5 gnome-phone-manager-0.7-4.fc5 gtkdatabox-0.7.0.0-2.fc5 heartbeat-2.0.7-1.fc5 inotify-tools-2.3-1.fc5 kooldock-0.3-3.20060720cvs.fc5 libconfuse-2.5-2.fc5 libsexymm-0.1.7-3.fc5 lyx-1.4.2-4.fc5 mock-0.6.1-1.fc5 nagios-plugins-1.4.3-17.fc5 nethack-vultures-2.1.0-4.fc5 octave-2.9.7-3.fc5 openbabel-2.0.2-2.fc5 perl-AppConfig-1.63-1.fc5 perl-Class-InsideOut-1.02-1.fc5 perl-Data-Alias-1.0-2.fc5 perl-Data-Compare-0.13-1.fc5 perl-File-HomeDir-0.58-1.fc5 perl-MIME-Types-1.17-1.fc5 perl-PAR-Dist-0.16-1.fc5 perl-POE-Component-Server-HTTP-0.09-2.fc5 perl-POE-Component-Server-SimpleHTTP-1.11-2.fc5 perl-POE-Component-Server-XMLRPC-0.05-2.fc5 perl-Scalar-Properties-0.12-1.fc5 perl-Sys-Virt-0.1.1-5.fc5 php-shout-0.3.1-5.fc5 plotutils-2.5-2.fc5 pstoedit-3.44-3.fc5 pyicq-t-0.7-4.fc5 python-dns-1.4.0-2.fc5 python-lxml-1.0.3-1.fc5 python-musicbrainz2-0.3.1-2.fc5 python-sqlalchemy-0.2.7-1.fc5 python-xmpp-0.3.1-2.fc5 renrot-0.23-1.fc5 smb4k-0.7.2-1.fc5 trackballs-1.1.2-2.fc5 trackballs-music-1.2-3.fc5 ufsparse-2.0.0-1.fc5 xdrawchem-1.9.9-3.fc5 yaz-2.1.26-1.fc5 Packages built and released for Fedora Extras 4: 17 bzrtools-0.9.1-1.fc4 digikam-0.8.2-2.fc4 gallery2-2.1-0.24.svn20060817.fc4 gtkdatabox-0.7.0.0-2.fc4 heartbeat-2.0.7-1.fc4 lyx-1.4.2-4.fc4 nagios-plugins-1.4.3-17.fc4 nethack-vultures-2.1.0-4.fc4 openbabel-2.0.2-2.fc4 pyicq-t-0.7-4.fc4 python-dns-1.4.0-2.fc4 python-lxml-1.0.3-1.fc4 python-sqlalchemy-0.2.7-1.fc4 python-xmpp-0.3.1-2.fc4 smb4k-0.7.2-1.fc4 xdrawchem-1.9.9-3.fc4 yaz-2.1.26-1.fc4 Packages built and released for Fedora Extras 3: 1 nethack-vultures-2.1.0-4.fc3 Packages built and released for Fedora Extras development: 43 NetworkManager-openvpn-0.3.2-5 abuse-0.7.0-1.fc6 audacious-1.1.1-6.fc6 brandy-1.0.19-3.fc6 bygfoot-2.0.0-2.fc6 bzrtools-0.9.1-1.fc6 cln-1.1.13-1.fc6 conexus-0.3.0-1.fc6 crm114-0-0.1.20060704.fc6 deltarpm-3.3-4.fc6 deskbar-applet-2.15.91-1.fc6 eris-1.3.11-7.fc6 fRaBs-2.10-1.fc6 gallery2-2.1-0.24.svn20060817.fc6 gtkdatabox-0.7.0.0-2.fc6 hfsplus-tools-332.14-2.fc6 hnb-1.9.18-2.fc6 kooldock-0.3-3.20060720cvs.fc6 libibverbs-1.0.3-1.fc6 lyx-1.4.2-4.fc6 mock-0.6.1-1.fc6 nautilus-open-terminal-0.7-2.fc6 nethack-vultures-2.1.0-4.fc6 perl-Archive-Extract-0.12-1.fc6 perl-Data-Alias-1.0-2.fc6 perl-Module-Load-Conditional-0.12-1.fc6 perl-POE-Component-Server-HTTP-0.09-2.fc6 perl-POE-Component-Server-SOAP-1.09-2.fc6 perl-POE-Component-Server-SimpleHTTP-1.11-2.fc6 perl-POE-Component-Server-XMLRPC-0.05-2.fc6 perl-Sys-Virt-0.1.1-5.fc6 php-manual-en-20060813-1.fc6 plotutils-2.5-2.fc6 pstoedit-3.44-3.fc6 python-lxml-1.0.3-1.fc6 python-sqlalchemy-0.2.7-1.fc6 renrot-0.23-1.fc6 smart-0.42-35.fc6 smb4k-0.7.2-1.fc6 trackballs-music-1.2-3.fc6 uw-imap-2004g-5.fc6 xscreensaver-5.00-17.fc6 yumex-1.1.1-1.0.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Sat Aug 19 21:26:34 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Sat, 19 Aug 2006 17:26:34 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-19 Message-ID: <20060819212634.D0875152169@buildsys.fedoraproject.org> camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: liljencrantz AT gmail.com 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) k3d: denis AT poolshark.org 4: 0:0.5.16.0-4.fc4 (FE4) 5: 0:0.5.16.0-3.fc5 (FE5) 6: 0:0.5.16.0-3.fc6 (FE6) koffice: andreas.bierfert AT lowlatency.de 5: 0:1.5.2-1.fc5 (FE5) 6: 0:1.5.1-2.fc6 (FE6) ktorrent: wolters.liste AT gmx.net 5: 0:2.0-5.fc5 (FE5) 6: 0:2.0-4.fc6 (FE6) libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) libpqxx: andreas.bierfert AT lowlatency.de 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) lvm2: 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) mozilla: 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.2-2.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) quagga: 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) seamonkey: kengert AT redhat.com 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.5-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) vorbisgain: noa AT resare.com 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) XaraLX: paul AT all-the-johnsons.co.uk 5: 0:0.7-3.fc5.r1614 (FE5) 6: 0:0.7-2.fc6.r1614 (FE6) From steve at silug.org Sat Aug 19 21:33:09 2006 From: steve at silug.org (Steven Pritchard) Date: Sat, 19 Aug 2006 16:33:09 -0500 Subject: Ignacio / php-json In-Reply-To: <44E77B26.7000101@theholbrooks.org> References: <1155944907.2982.22.camel@localhost> <44E6DA05.9080708@hhs.nl> <20060819165012.GA23627@osiris.silug.org> <44E7666A.9050907@theholbrooks.org> <20060819223653.ce67f8cb.bugs.michael@gmx.net> <44E77B26.7000101@theholbrooks.org> Message-ID: <20060819213309.GA6895@osiris.silug.org> On Sat, Aug 19, 2006 at 03:57:10PM -0500, Brandon Holbrook wrote: > When somebody suggested that we start taking bug reports, I though > that might mean we had jumped to the package takeover, so I asked for > clarification. I never meant to imply that people should start taking over package maintenance. I was just thinking that some bug fixes might be in order while we wait for Ignacio to reappear. My personal feeling is that the whole AWOL maintainer procedure should be held off as long as possible in this case. Assuming he is on vacation and acting appropriately seems reasonable though. Again, that's just my opinion. Steve -- Steven Pritchard - K&S Pritchard Enterprises, Inc. Email: steve at kspei.com http://www.kspei.com/ Phone: (618)398-3000 Mobile: (618)567-7320 From bugs.michael at gmx.net Sat Aug 19 21:54:17 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Sat, 19 Aug 2006 23:54:17 +0200 Subject: Ignacio / php-json In-Reply-To: <44E77B26.7000101@theholbrooks.org> References: <1155944907.2982.22.camel@localhost> <44E6DA05.9080708@hhs.nl> <20060819165012.GA23627@osiris.silug.org> <44E7666A.9050907@theholbrooks.org> <20060819223653.ce67f8cb.bugs.michael@gmx.net> <44E77B26.7000101@theholbrooks.org> Message-ID: <20060819235417.b6fb3138.bugs.michael@gmx.net> On Sat, 19 Aug 2006 15:57:10 -0500, Brandon Holbrook wrote: > >> I've gone ahead and answered > >> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198564 for > >> Ignacio's php-json package. Bumped to latest upstream and successfully > >> built. > >> > > > > Important: I've excluded the results of this build job from the next push. > > > > If you read the bug report, the reporter mentions that Ignacio has > > published a working/newer version for FC5. Your changes to the devel > > branch in CVS differ from Ignacio's FC-5 version. Further, you mention > > a "New Maintainer" in the %changelog, which is not official yet for > > this package, is it? I'd like to see the following policy in action > > > > > ...I guess I'm a little confused here. The bug reports mentions nothing > about a working version for FC5, only that a working version of 1.2.1 is > in FEdevel I mixed FC5 and devel in above paragraph. :) Ignacio has had the newer version in devel already, but the one you committed and built for FC5 is not his but the modified one. Even if it may be a trivial upgrade, the thing I'm interested in is whether we do have an active policy for "AWOL maintainers" or not? If the policy is considered a burden, too insufficient, we should change it. > > http://fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers > Which is why I asked if we were ready for the takeover process, rather > than assuming so. When somebody suggested that we start taking bug > reports, I though that might mean we had jumped to the package takeover, > so I asked for clarification. Well, asking for clarification and modifying CVS/submitting build jobs are two entirely different things. Whether "to jump" should remain FESCo's decision, IMO. Has anybody tracked in bugzilla the contact attempts that have been made in order to reach Ignacio? From buildsys at fedoraproject.org Sat Aug 19 21:47:12 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Sat, 19 Aug 2006 21:47:12 -0000 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-19 Message-ID: <20060819214712.19889.24920@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (135 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (135 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (12 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (12 days) libopensync-plugin-evolution2 - 0.18-6.fc5.i386 (12 days) libopensync-plugin-evolution2 - 0.18-6.fc5.ppc (12 days) libopensync-plugin-evolution2 - 0.18-6.fc5.x86_64 (12 days) wine-core - 0.9.17-1.fc6.i386 (24 days) bdpepple AT ameritech.net contact-lookup-applet - 0.14-3.fc6.i386 (12 days) contact-lookup-applet - 0.14-3.fc6.ppc (12 days) contact-lookup-applet - 0.14-3.fc6.x86_64 (12 days) byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (31 days) gaim-guifications - 2.12-3.fc5.ppc (31 days) gaim-guifications - 2.12-3.fc5.x86_64 (31 days) caillon AT redhat.com banshee - 0.10.11-1.fc6.i386 banshee - 0.10.11-1.fc6.ppc banshee - 0.10.11-1.fc6.x86_64 foolish AT guezz.net muine - 0.8.5-1.fc6.i386 muine - 0.8.5-1.fc6.ppc muine - 0.8.5-1.fc6.x86_64 gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (23 days) amarok - 1.4.1-3.fc6.ppc (23 days) showimg-pgsql - 0.9.5-7.fc4.i386 (12 days) showimg-pgsql - 0.9.5-7.fc4.ppc (12 days) showimg-pgsql - 0.9.5-7.fc4.x86_64 (12 days) showimg-pgsql - 0.9.5-7.fc5.i386 (12 days) showimg-pgsql - 0.9.5-7.fc5.ppc (12 days) showimg-pgsql - 0.9.5-7.fc5.x86_64 (12 days) green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (24 days) jogl - 1.1.1-14.fc5.ppc (27 days) ivazquez AT ivazquez.net gnome-applet-music - 0.9.0-1.fc6.i386 (31 days) gnome-applet-music - 0.9.0-1.fc6.ppc (31 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (31 days) nautilus-search-tool - 0.2-1.fc5.i386 (31 days) nautilus-search-tool - 0.2-1.fc5.ppc (31 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (31 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (31 days) gfontview - 0.5.0-5.fc5.ppc (31 days) gfontview - 0.5.0-5.fc5.x86_64 (31 days) gtkhtml36 - 3.6.2-5.fc6.i386 (31 days) gtkhtml36 - 3.6.2-5.fc6.ppc (31 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (31 days) libvisual-plugins - 0.2.0-3.fc5.i386 (31 days) libvisual-plugins - 0.2.0-3.fc5.i386 (31 days) libvisual-plugins - 0.2.0-3.fc5.ppc (31 days) libvisual-plugins - 0.2.0-3.fc5.ppc (31 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (31 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (31 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (94 days) syck-php - 0.55-7.fc5.i386 (94 days) syck-php - 0.55-7.fc5.ppc (94 days) syck-php - 0.55-7.fc5.ppc (94 days) syck-php - 0.55-7.fc5.x86_64 (94 days) syck-php - 0.55-7.fc5.x86_64 (94 days) paul AT all-the-johnsons.co.uk gtksourceview-sharp - 2.0-15.fc6.i386 gtksourceview-sharp - 2.0-15.fc6.ppc gtksourceview-sharp - 2.0-15.fc6.x86_64 petersen AT redhat.com ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.i386 (10 days) ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.ppc (10 days) ghc642-gtk2hs-mozembed - 0.9.10-2.fc6.x86_64 (10 days) rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (31 days) libibverbs - 1.0.3-1.fc6.ppc (31 days) libibverbs - 1.0.3-1.fc6.x86_64 (31 days) libibverbs-utils - 1.0.3-1.fc6.i386 (31 days) libibverbs-utils - 1.0.3-1.fc6.ppc (31 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (31 days) tcallawa AT redhat.com gambas-runtime - 1.0.14-2.fc5.i386 (11 days) thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (31 days) directfb - 0.9.24-5.fc5.ppc (31 days) directfb - 0.9.24-5.fc5.x86_64 (31 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.i386 requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) showimg-pgsql-0.9.5-7.fc5.x86_64 requires libpqxx-2.6.6.so()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.ppc requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.i386 requires libpqxx-2.6.6.so Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.x86_64 requires libpqxx-2.6.6.so()(64bit) Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.ppc requires libpqxx-2.6.6.so Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer banshee-0.10.11-1.fc6.i386 requires mono(gconf-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(glade-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(pango-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gnome-vfs-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(glib-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gtk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gnome-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gdk-sharp) = 0:2.8.0.0 contact-lookup-applet-0.14-3.fc6.i386 requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 gambas-runtime-1.0.14-2.fc5.i386 requires libgettextlib-0.14.5.so gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-2.fc6.i386 requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(gnome-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(gtk-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(glib-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(gdk-sharp) = 0:2.8.0.0 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 muine-0.8.5-1.fc6.i386 requires mono(glib-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.i386 requires mono(gtk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.i386 requires mono(gdk-sharp) = 0:2.8.0.0 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- banshee-0.10.11-1.fc6.x86_64 requires mono(gconf-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(glade-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gnome-vfs-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gtk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gdk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gnome-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(pango-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(glib-sharp) = 0:2.8.0.0 contact-lookup-applet-0.14-3.fc6.x86_64 requires libebook-1.2.so.5()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) ghc642-gtk2hs-mozembed-0.9.10-2.fc6.x86_64 requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(gnome-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(gtk-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(glib-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(gdk-sharp) = 0:2.8.0.0 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libedata-cal-1.2.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libecal-1.2.so.3()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libebook-1.2.so.5()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) muine-0.8.5-1.fc6.x86_64 requires mono(gdk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.x86_64 requires mono(gtk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.x86_64 requires mono(glib-sharp) = 0:2.8.0.0 nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.17-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 banshee-0.10.11-1.fc6.ppc requires mono(gconf-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(glade-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(pango-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gnome-vfs-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(glib-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gtk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gnome-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gdk-sharp) = 0:2.8.0.0 contact-lookup-applet-0.14-3.fc6.ppc requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 ghc642-gtk2hs-mozembed-0.9.10-2.fc6.ppc requires firefox-devel = 0:1.5.0.5 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(gnome-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(gtk-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(glib-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(gdk-sharp) = 0:2.8.0.0 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 muine-0.8.5-1.fc6.ppc requires mono(glib-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.ppc requires mono(gtk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.ppc requires mono(gdk-sharp) = 0:2.8.0.0 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 ====================================================================== New report for: paul AT all-the-johnsons.co.uk package: gtksourceview-sharp - 2.0-15.fc6.i386 from fedora-extras-development-i386 unresolved deps: mono(gnome-sharp) = 0:2.8.0.0 mono(gtk-sharp) = 0:2.8.0.0 mono(glib-sharp) = 0:2.8.0.0 mono(gdk-sharp) = 0:2.8.0.0 package: gtksourceview-sharp - 2.0-15.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: mono(gnome-sharp) = 0:2.8.0.0 mono(gtk-sharp) = 0:2.8.0.0 mono(glib-sharp) = 0:2.8.0.0 mono(gdk-sharp) = 0:2.8.0.0 package: gtksourceview-sharp - 2.0-15.fc6.ppc from fedora-extras-development-ppc unresolved deps: mono(gnome-sharp) = 0:2.8.0.0 mono(gtk-sharp) = 0:2.8.0.0 mono(glib-sharp) = 0:2.8.0.0 mono(gdk-sharp) = 0:2.8.0.0 ====================================================================== New report for: caillon AT redhat.com package: banshee - 0.10.11-1.fc6.i386 from fedora-extras-development-i386 unresolved deps: mono(gconf-sharp) = 0:2.8.0.0 mono(glade-sharp) = 0:2.8.0.0 mono(pango-sharp) = 0:2.8.0.0 mono(gnome-vfs-sharp) = 0:2.8.0.0 mono(glib-sharp) = 0:2.8.0.0 mono(gtk-sharp) = 0:2.8.0.0 mono(gnome-sharp) = 0:2.8.0.0 mono(gdk-sharp) = 0:2.8.0.0 package: banshee - 0.10.11-1.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: mono(gconf-sharp) = 0:2.8.0.0 mono(glade-sharp) = 0:2.8.0.0 mono(gnome-vfs-sharp) = 0:2.8.0.0 mono(gtk-sharp) = 0:2.8.0.0 mono(gdk-sharp) = 0:2.8.0.0 mono(gnome-sharp) = 0:2.8.0.0 mono(pango-sharp) = 0:2.8.0.0 mono(glib-sharp) = 0:2.8.0.0 package: banshee - 0.10.11-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: mono(gconf-sharp) = 0:2.8.0.0 mono(glade-sharp) = 0:2.8.0.0 mono(pango-sharp) = 0:2.8.0.0 mono(gnome-vfs-sharp) = 0:2.8.0.0 mono(glib-sharp) = 0:2.8.0.0 mono(gtk-sharp) = 0:2.8.0.0 mono(gnome-sharp) = 0:2.8.0.0 mono(gdk-sharp) = 0:2.8.0.0 ====================================================================== New report for: foolish AT guezz.net package: muine - 0.8.5-1.fc6.i386 from fedora-extras-development-i386 unresolved deps: mono(glib-sharp) = 0:2.8.0.0 mono(gtk-sharp) = 0:2.8.0.0 mono(gdk-sharp) = 0:2.8.0.0 package: muine - 0.8.5-1.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: mono(gdk-sharp) = 0:2.8.0.0 mono(gtk-sharp) = 0:2.8.0.0 mono(glib-sharp) = 0:2.8.0.0 package: muine - 0.8.5-1.fc6.ppc from fedora-extras-development-ppc unresolved deps: mono(glib-sharp) = 0:2.8.0.0 mono(gtk-sharp) = 0:2.8.0.0 mono(gdk-sharp) = 0:2.8.0.0 From rvinyard at cs.nmsu.edu Sat Aug 19 21:31:55 2006 From: rvinyard at cs.nmsu.edu (Rick L Vinyard Jr) Date: Sat, 19 Aug 2006 15:31:55 -0600 Subject: comps and gtk In-Reply-To: <1154355884.20753.5.camel@orodruin.boston.redhat.com> References: <20060729093041.GA2701@free.fr> <1154355884.20753.5.camel@orodruin.boston.redhat.com> Message-ID: <44E7834B.6040804@cs.nmsu.edu> Jeremy Katz wrote: >> * does it makes sense to have some packages in more than one group? For >> example I put grads is in 'Graphics', I think it also could be in >> 'Engineering and Scientific'. >> > > The problem with doing so is that it can lead to a confusing UI in some > cases. We've tried (hard) to get to where packages are only listed for > one component. I'd like to try to stay there. > I see a real disconnect between a policy like the above, the current names, and the current usage. Take a look at the following two categories: gnome-software-development GNOME Software Development Install these packages in order to develop GTK+ and GNOME graphical applications. xfce-software-development XFCE Software Development Install these packages in order to develop GTK+ and XFCE graphical applications. In the former, there are packages such as gazpacho, gtkmm24-devel and anjuta, et. al. In the latter there are gtk2-devel, glade2, glib2-devel, et. al. I think there will need to be one of two changes: 1) Allow gtk2-devel to be in both GNOME and XFCE development categories 2) Create a GTK+ and language bindings development category From rvinyard at cs.nmsu.edu Sat Aug 19 21:51:26 2006 From: rvinyard at cs.nmsu.edu (Rick L Vinyard Jr) Date: Sat, 19 Aug 2006 15:51:26 -0600 Subject: comps categories In-Reply-To: <200608161422.54330.jkeating@redhat.com> References: <1155743580.3495.5.camel@eagle.danny.cz> <200608161422.54330.jkeating@redhat.com> Message-ID: <44E787DE.9090402@cs.nmsu.edu> Personally, I would like to see a generalized development category where all -devel subpackages get placed that don't fit in any of the other development categories. Even more preferable is more categorization to the -devel packages. On that note, what about a 'Networking and Communications Software Development' category? Throw in things like pcap-devel, ORBit2-devel, avahi-devel, curl-devel, dbus-devel, gnet2-devel, conexus-devel, libwvstreams-devel, et. al. From buildsys at fedoraproject.org Sun Aug 20 00:30:45 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Sat, 19 Aug 2006 20:30:45 -0400 (EDT) Subject: [TEST] -- Broken upgrade paths in FC+FE 2006-08-19 Message-ID: <20060820003045.DC10B152169@buildsys.fedoraproject.org> : device-mapper 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) lvm2 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) mozilla 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) quagga 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) andreas.bierfert AT lowlatency.de: dillo 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) koffice 5: 0:1.5.2-1.fc5 (FE5) 6: 0:1.5.1-2.fc6 (FE6) libopensync-plugin-evolution2 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) libpqxx 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) denis AT poolshark.org: k3d 4: 0:0.5.16.0-4.fc4 (FE4) 5: 0:0.5.16.0-3.fc5 (FE5) 6: 0:0.5.16.0-3.fc6 (FE6) foolish AT guezz.net: serpentine 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) gemi AT bluewin.ch: TeXmacs 5: 0:1.0.6.5-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) ghenry AT suretecsystems.com: pgadmin3 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) jspaleta AT gmail.com: istanbul 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) kengert AT redhat.com: seamonkey 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) lemenkov AT newmail.ru: fuse-encfs 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) stratagus 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) liljencrantz AT gmail.com: fish 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) lmacken AT redhat.com: dclib 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) python-myghty 5: 0:1.0.2-2.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) valknut 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) luya_tfz AT thefinalzone.com: gdesklets 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) meme AT daughtersoftiresias.org: fortune-firefly 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) mpeters AT mac.com: firestarter 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) noa AT resare.com: vorbisgain 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) nomis80 AT nomis80.org: camstream 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) opencv 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) paul AT all-the-johnsons.co.uk: XaraLX 5: 0:0.7-3.fc5.r1614 (FE5) 6: 0:0.7-2.fc6.r1614 (FE6) paul AT city-fan.org: perl-String-CRC32 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) petersen AT redhat.com: m17n-db 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) rpm AT timj.co.uk: php-pear-DB 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) ryo-dairiki AT users.sourceforge.net: scim-tomoe 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) thomas AT apestaart.org: flumotion 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) wolters.liste AT gmx.net: ktorrent 5: 0:2.0-5.fc5 (FE5) 6: 0:2.0-4.fc6 (FE6) ---------------------------------------------------------------------- camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: liljencrantz AT gmail.com 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) k3d: denis AT poolshark.org 4: 0:0.5.16.0-4.fc4 (FE4) 5: 0:0.5.16.0-3.fc5 (FE5) 6: 0:0.5.16.0-3.fc6 (FE6) koffice: andreas.bierfert AT lowlatency.de 5: 0:1.5.2-1.fc5 (FE5) 6: 0:1.5.1-2.fc6 (FE6) ktorrent: wolters.liste AT gmx.net 5: 0:2.0-5.fc5 (FE5) 6: 0:2.0-4.fc6 (FE6) libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) libpqxx: andreas.bierfert AT lowlatency.de 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) lvm2: 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) mozilla: 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.2-2.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) quagga: 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) seamonkey: kengert AT redhat.com 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.5-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) vorbisgain: noa AT resare.com 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) XaraLX: paul AT all-the-johnsons.co.uk 5: 0:0.7-3.fc5.r1614 (FE5) 6: 0:0.7-2.fc6.r1614 (FE6) From chitlesh at fedoraproject.org Sun Aug 20 07:52:46 2006 From: chitlesh at fedoraproject.org (Chitlesh GOORAH) Date: Sun, 20 Aug 2006 09:52:46 +0200 Subject: cvs-import.sh 2nd time fails Message-ID: <13dbfe4f0608200052ub2115f8h63d3ba9efbe2b193@mail.gmail.com> Hello there, I run into a timeout while uploading my katapult package. So I retried to upload my package, impossible ! Below is what I'm getting. What should be done here ? chitlesh(~)[0]$./common/cvs-import.sh katapult-0.3.1.3-4.src.rpm Checking out the modules file... For more information on using the Fedora source code repositories, please visit http://fedoraproject.org/wiki/UsingCvs For more information on using the Fedora source code repositories, please visit http://fedoraproject.org/wiki/UsingCvs Module 'katapult' already exists... Checking out module: 'katapult' For more information on using the Fedora source code repositories, please visit http://fedoraproject.org/wiki/UsingCvs cvs [checkout aborted]: there is no repository /cvs/extras/rpms/katapult ./common/cvs-import.sh: line 247: cd: katapult: No such file or directory Unpacking source package: katapult-0.3.1.3-4.src.rpm... find: devel: No such file or directory ./common/cvs-import.sh: line 291: devel/sources.new: No such file or directory ./common/cvs-import.sh: line 292: devel/.cvsignore.new: No such file or directory mv: cannot move `tmpiz3367/katapult.spec' to `devel/katapult.spec': No such file or directory ./common/cvs-import.sh: line 318: pushd: devel: No such file or directory For more information on using the Fedora source code repositories, please visit http://fedoraproject.org/wiki/UsingCvs cvs add: cannot open CVS/Entries for reading: No such file or directory cvs [add aborted]: no repository A katapult.spec ./common/cvs-import.sh: line 338: popd: directory stack empty mv: cannot move `tmpiz3367/katapult_0.3.1.3.orig.tar.gz' to `devel/katapult_0.3.1.3.orig.tar.gz': No such file or directory ./common/cvs-import.sh: line 318: pushd: devel: No such file or directory L katapult_0.3.1.3.orig.tar.gz ./common/cvs-import.sh: line 338: popd: directory stack empty ./common/cvs-import.sh: line 341: pushd: devel: No such file or directory mv: cannot stat `sources.new': No such file or directory mv: cannot stat `.cvsignore.new': No such file or directory make: *** No rule to make target `upload'. Stop. ERROR: Uploading the source tarballs failed! -- http://clunixchit.blogspot.com From bugs.michael at gmx.net Sun Aug 20 09:48:57 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Sun, 20 Aug 2006 11:48:57 +0200 Subject: cvs-import.sh 2nd time fails In-Reply-To: <13dbfe4f0608200052ub2115f8h63d3ba9efbe2b193@mail.gmail.com> References: <13dbfe4f0608200052ub2115f8h63d3ba9efbe2b193@mail.gmail.com> Message-ID: <20060820114857.d34fdb0c.bugs.michael@gmx.net> On Sun, 20 Aug 2006 09:52:46 +0200, Chitlesh GOORAH wrote: > Hello there, > > I run into a timeout while uploading my katapult package. > So I retried to upload my package, impossible ! > > Below is what I'm getting. What should be done here ? > > chitlesh(~)[0]$./common/cvs-import.sh katapult-0.3.1.3-4.src.rpm > Checking out the modules file... > For more information on using the Fedora source code repositories, > please visit http://fedoraproject.org/wiki/UsingCvs > For more information on using the Fedora source code repositories, > please visit http://fedoraproject.org/wiki/UsingCvs > Module 'katapult' already exists... > Checking out module: 'katapult' > For more information on using the Fedora source code repositories, > please visit http://fedoraproject.org/wiki/UsingCvs > cvs [checkout aborted]: there is no repository /cvs/extras/rpms/katapult Try again now and never interrupt cvs-import.sh > ./common/cvs-import.sh: line 247: cd: katapult: No such file or directory > Unpacking source package: katapult-0.3.1.3-4.src.rpm... > find: devel: No such file or directory From chitlesh at fedoraproject.org Sun Aug 20 09:55:16 2006 From: chitlesh at fedoraproject.org (Chitlesh GOORAH) Date: Sun, 20 Aug 2006 11:55:16 +0200 Subject: cvs-import.sh 2nd time fails In-Reply-To: <20060820114857.d34fdb0c.bugs.michael@gmx.net> References: <13dbfe4f0608200052ub2115f8h63d3ba9efbe2b193@mail.gmail.com> <20060820114857.d34fdb0c.bugs.michael@gmx.net> Message-ID: <13dbfe4f0608200255h53f73f4ci9aaeb5966947a34b@mail.gmail.com> On 8/20/06, Michael Schwendt wrote: > Try again now and never interrupt cvs-import.sh Thanks, I've learnt the lesson :) -- http://clunixchit.blogspot.com From opensource at till.name Sun Aug 20 11:58:23 2006 From: opensource at till.name (Till Maas) Date: Sun, 20 Aug 2006 13:58:23 +0200 Subject: Contacting the Fedora Account System's management team Message-ID: <200608201358.40043.opensource@till.name> Hiyas, I would like to contanct someone from the Fedora Account Systems's management team, because I have some trouble getting my signed CLA accepted. http://www.fedoraproject.org/wiki/Infrastructure/AccountSystem/Contact states that I could contact the team with an email to accounts at fedoraproject.org but I got only an automated response back: With regards to "Problems signing CLA". Your message could not be processed. Reason Signature was not valid. Please see http://fedoraproject.org/wiki/DocsProject/UsingGpg/CreatingKeys My message I sent was signed the same way this message is signed. http://www.fedoraproject.org/wiki/Infrastructure mentions admin at fedoraproject.org in "E-mail the team with an introduction" - is this the correct e-mail address that should also be mentioned in http://www.fedoraproject.org/wiki/Infrastructure/AccountSystem/Contact ? Regards, Till -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Christian.Iseli at licr.org Sun Aug 20 13:45:24 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Sun, 20 Aug 2006 15:45:24 +0200 Subject: The comps SIG is born and hiring Message-ID: <20060820154524.419fcf28@ludwig-alpha> Hi folks, First, a big thank you to all of you who took some time to take a look at the comps files and add packages and drop me kind messages. I know things are not completely clear to many people wrt the purpose and usefulness of the comps files. It's also not too clear exactly what packages should appear in there. Which also goes to say that there is no way to write an automated tool that would determine which packages should appear in there and either add them automatically or send nagmails to their owners. For all these reasons, it was decided during the last FESCo meeting to create a new comps SIG, which purpose will be to: - clearly document why and what packages should go in comps - document and implement a way for maintainers to request new groups - periodically review the contents of the comps file to make sure all mentioned packages exist and are properly classified - periodically review all packages available in Extras and either ask their owners to add them in comps or simply add them in some cases If you would like to help with any of these tasks, please head to http://fedoraproject.org/wiki/Extras/SIGs/Comps sign yourself up and pitch in. comps is probably the first showcase a Fedora user will see: anaconda (the Fedora installer) uses comps to present available packages to the user. Other package management GUI also make use of comps to let users select package from software groups. The "group" tag in spec files is on its way to become optional, and might slowly fade into oblivion. If you went to the trouble of packaging some software that you think users will want to install on their machine, why not make it easy for them to just select it from a group list ? All you need to do is add it to the comps file in the appropriate group... Cheers, Christian From paul at all-the-johnsons.co.uk Sun Aug 20 14:16:52 2006 From: paul at all-the-johnsons.co.uk (Paul) Date: Sun, 20 Aug 2006 15:16:52 +0100 Subject: groupdel in a spec file Message-ID: <1156083412.3564.2.camel@T7.Linux> Hi, I have a package I'm reviewing which has a groupdel in the postun which rpmlint is quite rightly objecting to (though only at a warning level and doesn't mind groupadd being used). Is there any caveats for checking to ensure that other users won't have things broken should the rpm be removed? Or anything else that should be observed prior to the groupdel being executed? TTFN Paul -- "Ist du meine Mutter?" - der leerkinde -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From fedora at leemhuis.info Sun Aug 20 14:36:11 2006 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Sun, 20 Aug 2006 16:36:11 +0200 Subject: More feedback on co-maintainership please (Was : Re: Ideas for Co-maintainership in Extras) In-Reply-To: <1155110051.2640.67.camel@localhost> References: <44CB681A.8030709@leemhuis.info> <1155110051.2640.67.camel@localhost> Message-ID: <44E8735B.10600@leemhuis.info> Hi all! Toshio Kuratomi schrieb: > On Sat, 2006-07-29 at 15:52 +0200, Thorsten Leemhuis wrote: >> Welcome everybody to my brain dump of ideas around co-maintainership for >> Fedora Extras. >> == Why we need it == > [snip] > I agree with every one of those uses for co-maintainership. We might > have to break out the rules for them into several different documents > but they all seem to be things we really want to enable. [...] Toshio, many thx for your mail. I integrated nearly all of your comments to the FESCo schedule/planing page at http://www.fedoraproject.org/wiki/Extras/Schedule/Comaintainership (It also holds all the details from the first email on co-maintainership I send out some weeks ago in case somebody needs more context or wants to refresh his memory on the topic). But I'm wondering: There were no replies to my initial mail on this topic besides the one from Toshio. I can interpret this now as 1) comaintainership in this extend is stupid. That so obvious that people don't even replied to the mail. 2) comaintainership in this extend is exactly what people want. All details and ideas were laid down in that mail and nothing was wrong. So people didn't reply to it. >From my experience I know that "2)" is highly unlikely (read: impossible). "1)" is also unlikely, but at least more possible. So chances are high that it's something in between those two extremes. In other words: I'd like to get a bit more feedback on this topic before we actually start working further on co-maintainership in this extend. I especially would like to hear some comments from new and old FESCo members... I'd also appreciate small "I like the whole idea and the concept, please start working further on it, and I'll comment on individual details when they get discussed." mails. CU thl P.S.: >> === Long term === >> * make co-maintainership possible in core, too. > The Great Merge is the goal for our generation of Fedora. What will be > the goal for the Post-Merge generation? :-) My personal plan: Step down from FESCo. I'm sure there will be fresh people around with some new ideas how to make Fedora even better. From paul at cypherpunks.ca Sun Aug 20 14:42:55 2006 From: paul at cypherpunks.ca (Paul Wouters) Date: Sun, 20 Aug 2006 16:42:55 +0200 (CEST) Subject: SPF failures nuke fedora-extras* msgs from redhat.com Message-ID: [ sorry if slightly off-topic ] Hey people, I wondered why I was not receiving any fedora-extras messages for a week. So after tweaking my procmail rules, I found it all email was deleted as spam, because it scores "SPFFAIL". # host -t txt redhat.com redhat.com descriptive text "v=spf1 include:spf-2.redhat.com include:spf-1.redhat.com -all" # host -t any spf-1.redhat.com spf-1.redhat.com descriptive text "v=spf1 ip4:204.16.104.38 ip4:66.187.233.31 ip4:66.187.237.31 ip4:66.187.233.32" # host -t any spf-2.redhat.com spf-2.redhat.com descriptive text "v=spf1 mx ip4:204.14.234.13 ip4:204.14.232.13 ip4:204.14.234.14 ip4:204.14.232.14 ip4:209.132.177.0/24 ip4:65.125.54.185 ip4:65.125.54.186 ip4:65.125.54.187 ip4:65.125.54.188 ip4:65.125.54.189 ip4:65.125.54.190 ip4:219.120.63.242 ip4:66.187.224.200" Mail arrives from: Received: from hormel.redhat.com (hormel.redhat.com [209.132.177.30]) Now hormel is indeed listed for spf-2, so I am not sure what is going on. This comes from enabling loadplugin Mail::SpamAssassin::Plugin::SPF with spamassassin-3.1.3-5 A re-ordering of procmail rules worked around this issue for me. Paul From ville.skytta at iki.fi Sun Aug 20 14:58:04 2006 From: ville.skytta at iki.fi (Ville =?ISO-8859-1?Q?Skytt=E4?=) Date: Sun, 20 Aug 2006 17:58:04 +0300 Subject: groupdel in a spec file In-Reply-To: <1156083412.3564.2.camel@T7.Linux> References: <1156083412.3564.2.camel@T7.Linux> Message-ID: <1156085884.2508.13.camel@viper.local> On Sun, 2006-08-20 at 15:16 +0100, Paul wrote: > Is there any caveats for checking to ensure that other users won't have > things broken should the rpm be removed? Or anything else that should be > observed prior to the groupdel being executed? The problem is that such a check is AFAIK pretty much impossible to do sanely. Both leaving users/groups behind and removing them at final erase time have their disadvantages, but I think the smaller evil is to not remove any groups (or users) created by packages -- leave it for the sysadmin to take care of if they so desire, and ensure that package installation doesn't fail if the desired user/group already exists at install time. From Axel.Thimm at ATrpms.net Sun Aug 20 15:02:45 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Sun, 20 Aug 2006 17:02:45 +0200 Subject: groupdel in a spec file In-Reply-To: <1156083412.3564.2.camel@T7.Linux> References: <1156083412.3564.2.camel@T7.Linux> Message-ID: <20060820150245.GG22844@neu.nirvana> On Sun, Aug 20, 2006 at 03:16:52PM +0100, Paul wrote: > Hi, > > I have a package I'm reviewing which has a groupdel in the postun which > rpmlint is quite rightly objecting to (though only at a warning level > and doesn't mind groupadd being used). > > Is there any caveats for checking to ensure that other users won't have > things broken should the rpm be removed? Or anything else that should be > observed prior to the groupdel being executed? Removing a user/group is only 100% safe to not casue issues, if it is certain that no files remain which carry these ids. This includes files generated outside the package's known file space, for example a local (backup) copy. Whether this is enough to have a general policy against removing users/groups is a different strory. Maybe there is a global guideline or even rule somewhere in the wiki. If not you would have to check the package's functionality to judge on a case-by-case basis, there is no general answer possible. For example say removing an MTA's user/group and recycling it for a games group means that all games will be able to read any old mails in the MTA's queues. The other way around (the MTA reading the gamers' savefiles) is probably not as severe :) -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mattdm at mattdm.org Sun Aug 20 15:14:44 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Sun, 20 Aug 2006 11:14:44 -0400 Subject: SPF failures nuke fedora-extras* msgs from redhat.com In-Reply-To: References: Message-ID: <20060820151444.GA8534@jadzia.bu.edu> On Sun, Aug 20, 2006 at 04:42:55PM +0200, Paul Wouters wrote: > I wondered why I was not receiving any fedora-extras messages for a week. > So after tweaking my procmail rules, I found it all email was deleted > as spam, because it scores "SPFFAIL". Ow! Never treat SPFFAIL that way -- that's not what SPF is for. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From ville.skytta at iki.fi Sun Aug 20 15:31:45 2006 From: ville.skytta at iki.fi (Ville =?ISO-8859-1?Q?Skytt=E4?=) Date: Sun, 20 Aug 2006 18:31:45 +0300 Subject: Planning next version of rpmdevtools In-Reply-To: <20060811111425.0149f97d@ludwig-alpha> References: <1152911573.2696.49.camel@localhost.localdomain> <1155240351.2997.317.camel@localhost.localdomain> <1155286350.2997.356.camel@localhost.localdomain> <20060811111425.0149f97d@ludwig-alpha> Message-ID: <1156087905.2508.15.camel@viper.local> On Fri, 2006-08-11 at 11:14 +0200, Christian Iseli wrote: > On Fri, 11 Aug 2006 11:52:30 +0300, Ville Skytt? wrote: > > With rpmdev prefix, maybe something like this. rpmdeX would > > work: > > I like it. Will proceed according to this plan. From bugzilla at redhat.com Sun Aug 20 19:25:06 2006 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 20 Aug 2006 15:25:06 -0400 Subject: [Bug 189342] Python egg spec template In-Reply-To: Message-ID: <200608201925.k7KJP65g028658@bugzilla.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Python egg spec template https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189342 ville.skytta at iki.fi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED Resolution| |INSUFFICIENT_DATA ------- Additional Comments From ville.skytta at iki.fi 2006-08-20 15:15 EST ------- No feedback to comment 4, assuming this is not needed. Feel free to reopen for more discussion if you disagree. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. From rvinyard at cs.nmsu.edu Sun Aug 20 20:10:59 2006 From: rvinyard at cs.nmsu.edu (Rick L Vinyard Jr) Date: Sun, 20 Aug 2006 14:10:59 -0600 Subject: The comps SIG is born and hiring In-Reply-To: <20060820154524.419fcf28@ludwig-alpha> References: <20060820154524.419fcf28@ludwig-alpha> Message-ID: <44E8C1D3.7020107@cs.nmsu.edu> Christian Iseli wrote: > If you would like to help with any of these tasks, please head to > http://fedoraproject.org/wiki/Extras/SIGs/Comps > sign yourself up and pitch in. > > The page isn't editable... From rvinyard at cs.nmsu.edu Sun Aug 20 20:21:18 2006 From: rvinyard at cs.nmsu.edu (Rick L Vinyard Jr) Date: Sun, 20 Aug 2006 14:21:18 -0600 Subject: The comps SIG is born and hiring In-Reply-To: <20060820154524.419fcf28@ludwig-alpha> References: <20060820154524.419fcf28@ludwig-alpha> Message-ID: <44E8C43E.5050001@cs.nmsu.edu> Christian Iseli wrote: > - periodically review the contents of the comps file to make sure all > mentioned packages exist and are properly classified > I noticed that gnome-software-development is missing from the Development category. From jwboyer at jdub.homelinux.org Sun Aug 20 21:06:27 2006 From: jwboyer at jdub.homelinux.org (Josh Boyer) Date: Sun, 20 Aug 2006 16:06:27 -0500 Subject: More feedback on co-maintainership please (Was : Re: Ideas for Co-maintainership in Extras) In-Reply-To: <44E8735B.10600@leemhuis.info> References: <44CB681A.8030709@leemhuis.info> <1155110051.2640.67.camel@localhost> <44E8735B.10600@leemhuis.info> Message-ID: <1156107987.2683.61.camel@vader.jdub.homelinux.org> On Sun, 2006-08-20 at 16:36 +0200, Thorsten Leemhuis wrote: > > But I'm wondering: There were no replies to my initial mail on this > topic besides the one from Toshio. I can interpret this now as > > 1) comaintainership in this extend is stupid. That so obvious that > people don't even replied to the mail. > > 2) comaintainership in this extend is exactly what people want. All > details and ideas were laid down in that mail and nothing was wrong. So > people didn't reply to it. Or 3) people just haven't read it yet. I'm guilty of 3. That email hit the lists while I was on vacation, so I must have missed it when I was playing catch-up. But I've read it now :) > In other words: I'd like to get a bit more feedback on this topic before > we actually start working further on co-maintainership in this extend. I > especially would like to hear some comments from new and old FESCo > members... > > I'd also appreciate small "I like the whole idea and the concept, please > start working further on it, and I'll comment on individual details when > they get discussed." mails. I personally do like the concept. I think co-maintainership is both beneficial and important. And yes, I plan on comment more as individual details come out. Overall, I think what is documented in that page is a pretty good start. Some of the questions definitely need answering (like tiers, and whether co-maintainers can approve other things, etc) but I think they're a bit too far out to discuss them right now. We need to get bugzilla auto-CC fixed and the new VCS and package database in place first, and those aren't small things. josh From Christian.Iseli at licr.org Sun Aug 20 21:23:06 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Sun, 20 Aug 2006 23:23:06 +0200 Subject: More feedback on co-maintainership please (Was : Re: Ideas for Co-maintainership in Extras) In-Reply-To: <44E8735B.10600@leemhuis.info> References: <44CB681A.8030709@leemhuis.info> <1155110051.2640.67.camel@localhost> <44E8735B.10600@leemhuis.info> Message-ID: <20060820232306.250cf22f@ludwig-alpha> On Sun, 20 Aug 2006 16:36:11 +0200, Thorsten Leemhuis wrote: > "I like the whole idea and the concept, please > start working further on it, and I'll comment on individual details when > they get discussed." Couldn't have said it better myself :-) More when I get back from vacations... Christian From Christian.Iseli at licr.org Sun Aug 20 21:35:39 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Sun, 20 Aug 2006 23:35:39 +0200 Subject: The comps SIG is born and hiring In-Reply-To: <44E8C1D3.7020107@cs.nmsu.edu> References: <20060820154524.419fcf28@ludwig-alpha> <44E8C1D3.7020107@cs.nmsu.edu> Message-ID: <20060820233539.7150ea42@ludwig-alpha> On Sun, 20 Aug 2006 14:10:59 -0600, Rick L Vinyard Jr wrote: > The page isn't editable... That's strange... Could someone commanding the proper magic please have a look and see why Rick can't edit the page ? (or explain me what I can/should do...) Thanks, Christian From buildsys at fedoraproject.org Mon Aug 21 00:06:04 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Sun, 20 Aug 2006 20:06:04 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-20 Message-ID: <20060821000604.5DB40152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 4 ktorrent-2.0-6.fc5 pcb-0.20060422-6 perl-Sys-Virt-0.1.1-6.fc5 shorewall-3.2.2-1.fc5 Packages built and released for Fedora Extras 4: 1 shorewall-3.2.2-1.fc4 Packages built and released for Fedora Extras development: 11 cairomm-1.2.0-2.fc6 deskbar-applet-2.15.91-3.fc6 efont-unicode-bdf-0.4.2-6.fc6 gtk2hs-0.9.10-3.fc6 ktorrent-2.0-6.fc6 net6-1.3.0-5.rc3.fc6 obby-0.4.0-7.rc4.fc6 pcb-0.20060422-8.fc6 perl-Sys-Virt-0.1.1-6.fc6 rpmdevtools-5.0-1.fc6 shorewall-3.2.2-1.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Mon Aug 21 00:06:26 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Sun, 20 Aug 2006 20:06:26 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-20 Message-ID: <20060821000626.BB741152169@buildsys.fedoraproject.org> UNKNOWN OWNER (possibly Core package): device-mapper 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) lvm2 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) mozilla 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) quagga 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) andreas.bierfert AT lowlatency.de: dillo 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) koffice 5: 0:1.5.2-1.fc5 (FE5) 6: 0:1.5.1-2.fc6 (FE6) libopensync-plugin-evolution2 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) libpqxx 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) denis AT poolshark.org: k3d 4: 0:0.5.16.0-4.fc4 (FE4) 5: 0:0.5.16.0-3.fc5 (FE5) 6: 0:0.5.16.0-3.fc6 (FE6) foolish AT guezz.net: serpentine 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) gemi AT bluewin.ch: TeXmacs 5: 0:1.0.6.5-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) ghenry AT suretecsystems.com: pgadmin3 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) jspaleta AT gmail.com: istanbul 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) kengert AT redhat.com: seamonkey 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) lemenkov AT newmail.ru: fuse-encfs 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) stratagus 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) liljencrantz AT gmail.com: fish 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) lmacken AT redhat.com: dclib 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) python-myghty 5: 0:1.0.2-2.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) valknut 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) luya_tfz AT thefinalzone.com: gdesklets 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) meme AT daughtersoftiresias.org: fortune-firefly 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) mpeters AT mac.com: firestarter 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) noa AT resare.com: vorbisgain 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) nomis80 AT nomis80.org: camstream 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) opencv 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) paul AT all-the-johnsons.co.uk: XaraLX 5: 0:0.7-3.fc5.r1614 (FE5) 6: 0:0.7-2.fc6.r1614 (FE6) paul AT city-fan.org: perl-String-CRC32 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) petersen AT redhat.com: m17n-db 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) rpm AT timj.co.uk: php-pear-DB 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) ryo-dairiki AT users.sourceforge.net: scim-tomoe 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) thomas AT apestaart.org: flumotion 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) ---------------------------------------------------------------------- camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: UNKNOWN OWNER (possibly Core package) 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: liljencrantz AT gmail.com 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) k3d: denis AT poolshark.org 4: 0:0.5.16.0-4.fc4 (FE4) 5: 0:0.5.16.0-3.fc5 (FE5) 6: 0:0.5.16.0-3.fc6 (FE6) koffice: andreas.bierfert AT lowlatency.de 5: 0:1.5.2-1.fc5 (FE5) 6: 0:1.5.1-2.fc6 (FE6) libopensync-plugin-evolution2: andreas.bierfert AT lowlatency.de 5: 0:0.18-7.fc5 (FE5) 6: 0:0.18-6.fc5 (FE6) libpqxx: andreas.bierfert AT lowlatency.de 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) lvm2: UNKNOWN OWNER (possibly Core package) 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) mozilla: UNKNOWN OWNER (possibly Core package) 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.2-2.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) quagga: UNKNOWN OWNER (possibly Core package) 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) seamonkey: kengert AT redhat.com 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.5-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) vorbisgain: noa AT resare.com 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) XaraLX: paul AT all-the-johnsons.co.uk 5: 0:0.7-3.fc5.r1614 (FE5) 6: 0:0.7-2.fc6.r1614 (FE6) From buildsys at fedoraproject.org Mon Aug 21 00:22:18 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Mon, 21 Aug 2006 00:22:18 -0000 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-20 Message-ID: <20060821002218.6723.83486@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (136 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (136 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-af - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ar - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-bg - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-br - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-bs - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ca - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-cs - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-cy - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-da - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-de - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-el - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-en_GB - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-eo - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-es - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-et - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-eu - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-fi - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-fr - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ga - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-he - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-hi - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-hu - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-is - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-it - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ja - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-lt - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-mk - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ms - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-nb - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-nl - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-nn - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-pl - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-pt - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-pt_BR - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ro - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ru - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-se - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sk - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sl - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sr - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sr-Latn - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-sv - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-ta - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-tg - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-tr - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-uk - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-uz - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-zh_CN - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (13 days) koffice-langpack-zh_TW - 1.5.2-1.fc6.noarch (13 days) libopensync-plugin-evolution2 - 0.18-6.fc5.i386 (13 days) libopensync-plugin-evolution2 - 0.18-6.fc5.ppc (13 days) libopensync-plugin-evolution2 - 0.18-6.fc5.x86_64 (13 days) wine-core - 0.9.17-1.fc6.i386 (25 days) bdpepple AT ameritech.net contact-lookup-applet - 0.14-3.fc6.i386 (13 days) contact-lookup-applet - 0.14-3.fc6.ppc (13 days) contact-lookup-applet - 0.14-3.fc6.x86_64 (13 days) byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (32 days) gaim-guifications - 2.12-3.fc5.ppc (32 days) gaim-guifications - 2.12-3.fc5.x86_64 (32 days) caillon AT redhat.com banshee - 0.10.11-1.fc6.i386 banshee - 0.10.11-1.fc6.ppc banshee - 0.10.11-1.fc6.x86_64 foolish AT guezz.net muine - 0.8.5-1.fc6.i386 muine - 0.8.5-1.fc6.ppc muine - 0.8.5-1.fc6.x86_64 gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (24 days) amarok - 1.4.1-3.fc6.ppc (24 days) showimg-pgsql - 0.9.5-7.fc4.i386 (13 days) showimg-pgsql - 0.9.5-7.fc4.ppc (13 days) showimg-pgsql - 0.9.5-7.fc4.x86_64 (13 days) showimg-pgsql - 0.9.5-7.fc5.i386 (13 days) showimg-pgsql - 0.9.5-7.fc5.ppc (13 days) showimg-pgsql - 0.9.5-7.fc5.x86_64 (13 days) green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (25 days) jogl - 1.1.1-14.fc5.ppc (28 days) ivazquez AT ivazquez.net gnome-applet-music - 0.9.0-1.fc6.i386 (32 days) gnome-applet-music - 0.9.0-1.fc6.ppc (32 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (32 days) nautilus-search-tool - 0.2-1.fc5.i386 (32 days) nautilus-search-tool - 0.2-1.fc5.ppc (32 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (32 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (32 days) gfontview - 0.5.0-5.fc5.ppc (32 days) gfontview - 0.5.0-5.fc5.x86_64 (32 days) gtkhtml36 - 3.6.2-5.fc6.i386 (32 days) gtkhtml36 - 3.6.2-5.fc6.ppc (32 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (32 days) libvisual-plugins - 0.2.0-3.fc5.i386 (32 days) libvisual-plugins - 0.2.0-3.fc5.i386 (32 days) libvisual-plugins - 0.2.0-3.fc5.ppc (32 days) libvisual-plugins - 0.2.0-3.fc5.ppc (32 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (32 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (32 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (95 days) syck-php - 0.55-7.fc5.i386 (95 days) syck-php - 0.55-7.fc5.ppc (95 days) syck-php - 0.55-7.fc5.ppc (95 days) syck-php - 0.55-7.fc5.x86_64 (95 days) syck-php - 0.55-7.fc5.x86_64 (95 days) paul AT all-the-johnsons.co.uk gtksourceview-sharp - 2.0-15.fc6.i386 gtksourceview-sharp - 2.0-15.fc6.ppc gtksourceview-sharp - 2.0-15.fc6.x86_64 rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (32 days) libibverbs - 1.0.3-1.fc6.ppc (32 days) libibverbs - 1.0.3-1.fc6.x86_64 (32 days) libibverbs-utils - 1.0.3-1.fc6.i386 (32 days) libibverbs-utils - 1.0.3-1.fc6.ppc (32 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (32 days) tcallawa AT redhat.com gambas-runtime - 1.0.14-2.fc5.i386 (12 days) thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (32 days) directfb - 0.9.24-5.fc5.ppc (32 days) directfb - 0.9.24-5.fc5.x86_64 (32 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.i386 requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) showimg-pgsql-0.9.5-7.fc5.x86_64 requires libpqxx-2.6.6.so()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.ppc requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.i386 requires libpqxx-2.6.6.so Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.x86_64 requires libpqxx-2.6.6.so()(64bit) Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.ppc requires libpqxx-2.6.6.so Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer banshee-0.10.11-1.fc6.i386 requires mono(gconf-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(glade-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(pango-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gnome-vfs-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(glib-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gtk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gnome-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gdk-sharp) = 0:2.8.0.0 contact-lookup-applet-0.14-3.fc6.i386 requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 gambas-runtime-1.0.14-2.fc5.i386 requires libgettextlib-0.14.5.so gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(gnome-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(gtk-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(glib-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(gdk-sharp) = 0:2.8.0.0 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.i386 requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 muine-0.8.5-1.fc6.i386 requires mono(glib-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.i386 requires mono(gtk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.i386 requires mono(gdk-sharp) = 0:2.8.0.0 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- banshee-0.10.11-1.fc6.x86_64 requires mono(gconf-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(glade-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gnome-vfs-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gtk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gdk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gnome-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(pango-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(glib-sharp) = 0:2.8.0.0 contact-lookup-applet-0.14-3.fc6.x86_64 requires libebook-1.2.so.5()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(gnome-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(gtk-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(glib-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(gdk-sharp) = 0:2.8.0.0 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libedata-cal-1.2.so.1()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libecal-1.2.so.3()(64bit) libopensync-plugin-evolution2-0.18-6.fc5.x86_64 requires libebook-1.2.so.5()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) muine-0.8.5-1.fc6.x86_64 requires mono(gdk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.x86_64 requires mono(gtk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.x86_64 requires mono(glib-sharp) = 0:2.8.0.0 nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.17-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 banshee-0.10.11-1.fc6.ppc requires mono(gconf-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(glade-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(pango-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gnome-vfs-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(glib-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gtk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gnome-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gdk-sharp) = 0:2.8.0.0 contact-lookup-applet-0.14-3.fc6.ppc requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(gnome-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(gtk-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(glib-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(gdk-sharp) = 0:2.8.0.0 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 koffice-langpack-af-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ar-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-br-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-bs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ca-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cs-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-cy-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-da-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-de-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-el-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-en_GB-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eo-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-es-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-et-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-eu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-fr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ga-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-he-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hi-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-hu-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-is-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-it-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ja-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-lt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-mk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ms-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nb-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-nn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-pt_BR-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ro-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ru-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-se-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sl-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sr-Latn-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-sv-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-ta-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tg-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-tr-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uk-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-uz-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_CN-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 koffice-langpack-zh_TW-1.5.2-1.fc6.noarch requires koffice-core >= 0:1.5.2 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libedata-cal-1.2.so.1 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libecal-1.2.so.3 libopensync-plugin-evolution2-0.18-6.fc5.ppc requires libebook-1.2.so.5 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 muine-0.8.5-1.fc6.ppc requires mono(glib-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.ppc requires mono(gtk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.ppc requires mono(gdk-sharp) = 0:2.8.0.0 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 From nman64 at n-man.com Mon Aug 21 03:59:55 2006 From: nman64 at n-man.com (Patrick W. Barnes) Date: Sun, 20 Aug 2006 22:59:55 -0500 Subject: Contacting the Fedora Account System's management team In-Reply-To: <200608201358.40043.opensource@till.name> References: <200608201358.40043.opensource@till.name> Message-ID: <200608202259.58934.nman64@n-man.com> On Sunday 20 August 2006 06:58, Till Maas wrote: > > I would like to contanct someone from the Fedora Account Systems's > management team, because I have some trouble getting my signed CLA > accepted. > > http://www.fedoraproject.org/wiki/Infrastructure/AccountSystem/Contact > states that I could contact the team with an email to > accounts at fedoraproject.org but I got only an automated response back: > > With regards to "Problems signing CLA". > Your message could not be processed. > Reason Signature was not valid. Please see > http://fedoraproject.org/wiki/DocsProject/UsingGpg/CreatingKeys > > My message I sent was signed the same way this message is signed. > > http://www.fedoraproject.org/wiki/Infrastructure > mentions admin at fedoraproject.org in "E-mail the team with an introduction" > - is this the correct e-mail address that should also be mentioned in > http://www.fedoraproject.org/wiki/Infrastructure/AccountSystem/Contact ? > The same address handles both automated messages and normal correspondence. The subject of the message is used to pick up the CLA messages. If you need to get a message through and the automated system is picking it up, try changing the subject. Your particular issue is arising because the email address you have registered in the Account System is not a UID on your signing key. You need to either add opensource at still.name as a UID on your signing key or change the address you are using in the Account System to till.maas at still.name. -- Patrick "The N-Man" Barnes nman64 at n-man.com http://www.n-man.com/ LinkedIn: http://www.linkedin.com/in/nman64 Have I been helpful? Rate my assistance! http://rate.affero.net/nman64/ -- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From tibbs at math.uh.edu Mon Aug 21 04:14:23 2006 From: tibbs at math.uh.edu (Jason L Tibbitts III) Date: Sun, 20 Aug 2006 23:14:23 -0500 Subject: Ignacio / php-json In-Reply-To: <44E77B26.7000101@theholbrooks.org> (Brandon Holbrook's message of "Sat, 19 Aug 2006 15:57:10 -0500") References: <1155944907.2982.22.camel@localhost> <44E6DA05.9080708@hhs.nl> <20060819165012.GA23627@osiris.silug.org> <44E7666A.9050907@theholbrooks.org> <20060819223653.ce67f8cb.bugs.michael@gmx.net> <44E77B26.7000101@theholbrooks.org> Message-ID: >>>>> "BH" == Brandon Holbrook writes: BH> That was my problem, I joined "fedorabugs" instead of BH> "fedora_bugs". No, it's fedorabugs, but I've been waiting for you to apply there and haven't seen the request yet. I checked again and see that you do have your cvsextras membership but aren't currently a member of fedorabugs. I double checked the list of pending approvals there and you are not on that list. (I'm checking the user ID "static"; please correct me if that's wrong.) - J< From opensource at till.name Mon Aug 21 10:37:30 2006 From: opensource at till.name (Till Maas) Date: Mon, 21 Aug 2006 12:37:30 +0200 Subject: Contacting the Fedora Account System's management team Message-ID: <200608211237.45256.opensource@till.name> Hiyas, this is the second time I send this e-mail, it seems tom me that the previous one never reached the mailing list. Is there any spam filtering done for this list? Here is my original text: I would like to contanct someone from the Fedora Account Systems's management team, because I have some trouble getting my signed CLA accepted. http://www.fedoraproject.org/wiki/Infrastructure/AccountSystem/Contact states that I could contact the team with an email to accounts at fedoraproject.org but I got only an automated response back: With regards to "Problems signing CLA". Your message could not be processed. Reason Signature was not valid. Please see http://fedoraproject.org/wiki/DocsProject/UsingGpg/CreatingKeys My message I sent was signed the same way this message is signed. http://www.fedoraproject.org/wiki/Infrastructure mentions admin at fedoraproject.org in "E-mail the team with an introduction" - is this the correct e-mail address that should also be mentioned in http://www.fedoraproject.org/wiki/Infrastructure/AccountSystem/Contact ? Regards, Till -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jamatos at fc.up.pt Mon Aug 21 10:47:01 2006 From: jamatos at fc.up.pt (=?iso-8859-15?q?Jos=E9_Matos?=) Date: Mon, 21 Aug 2006 11:47:01 +0100 Subject: More feedback on co-maintainership please (Was : Re: Ideas for Co-maintainership in Extras) In-Reply-To: <44E8735B.10600@leemhuis.info> References: <44CB681A.8030709@leemhuis.info> <1155110051.2640.67.camel@localhost> <44E8735B.10600@leemhuis.info> Message-ID: <200608211147.02073.jamatos@fc.up.pt> On Sunday 20 August 2006 15:36, Thorsten Leemhuis wrote: > I'd also appreciate small "I like the whole idea and the concept, please > start working further on it, and I'll comment on individual details when > they get discussed." mails. +1 :-) -- Jos? Ab?lio From fedora at leemhuis.info Mon Aug 21 10:58:10 2006 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Mon, 21 Aug 2006 12:58:10 +0200 Subject: Contacting the Fedora Account System's management team In-Reply-To: <200608211237.45256.opensource@till.name> References: <200608211237.45256.opensource@till.name> Message-ID: <44E991C2.4010201@leemhuis.info> CCing Till directly, just to make sure. Till Maas schrieb: > this is the second time I send this e-mail, it seems tom me that the previous > one never reached the mailing list. [...] It did arrive :) You'll find you mail in the archives at https://www.redhat.com/archives/fedora-extras-list/2006-August/thread.html e.g. https://www.redhat.com/archives/fedora-extras-list/2006-August/msg00494.html There is also an answer already: https://www.redhat.com/archives/fedora-extras-list/2006-August/msg00512.html HTH CU thl From bugs.michael at gmx.net Mon Aug 21 12:09:43 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Mon, 21 Aug 2006 14:09:43 +0200 Subject: Multilib in Extras repo? Message-ID: <20060821140943.1d820124.bugs.michael@gmx.net> I've looked a bit into preparing the Extras push script for multilib support. In particular: - Copy all noarch packages (considering ExcludeArch) to all repositories. This is done already. - Find all multicompat -devel binary rpms (considering virtual packages and ExcludeArch) and copy them to their multilib capable arch repository, e.g. (i386/i586/i686/athlon -> x86_64). - Examine the unresolved dependencies of the multicompat packages and copy all missing Extras packages into the target repository, too. For the dep resolving, I've used the Yum back-end's returnPackagesByDep() method. Although the results look reasonable -- i.e. I see the -devel packages pull it their mother packages and all their deps in Extras -- I'm not an expert in Yum API programming and have yet to find out what corner-cases one may need to deal with (Obsoletes? arch/multiarch package picking extra-burden?) and what other pitfalls may be lurking. Has anyone else spent thoughts on this? Too late for FE6? What is the estimated multilib readiness of FE6? Do we expect many file conflicts (due to arch-specific stuff in generated headers) or package installer/updater problems (on multilib installations)? From paul at cypherpunks.ca Mon Aug 21 14:04:54 2006 From: paul at cypherpunks.ca (Paul Wouters) Date: Mon, 21 Aug 2006 16:04:54 +0200 (CEST) Subject: [Possible Spam] Re: SPF failures nuke fedora-extras* msgs from redhat.com In-Reply-To: <20060820151444.GA8534@jadzia.bu.edu> References: <20060820151444.GA8534@jadzia.bu.edu> Message-ID: On Sun, 20 Aug 2006, Matthew Miller wrote: > On Sun, Aug 20, 2006 at 04:42:55PM +0200, Paul Wouters wrote: > > I wondered why I was not receiving any fedora-extras messages for a week. > > So after tweaking my procmail rules, I found it all email was deleted > > as spam, because it scores "SPFFAIL". > > Ow! Never treat SPFFAIL that way -- that's not what SPF is for. First, I believe this is stock spamassassin rpm packaging, so that would then be a fedora bug. But second, AFAIK, it *is* what SPF is for. If a machine claiming to send on behalf of a domain is not listed in a TXT record for that domain, then it is a roque sender and therefor fake, and therefor should be dropped. Paul From tibbs at math.uh.edu Mon Aug 21 15:01:21 2006 From: tibbs at math.uh.edu (Jason L Tibbitts III) Date: Mon, 21 Aug 2006 10:01:21 -0500 Subject: The comps SIG is born and hiring In-Reply-To: <20060820233539.7150ea42@ludwig-alpha> (Christian Iseli's message of "Sun, 20 Aug 2006 23:35:39 +0200") References: <20060820154524.419fcf28@ludwig-alpha> <44E8C1D3.7020107@cs.nmsu.edu> <20060820233539.7150ea42@ludwig-alpha> Message-ID: >>>>> "CI" == Christian Iseli writes: CI> Could someone commanding the proper magic please have a look and CI> see why Rick can't edit the page ? (or explain me what I CI> can/should do...) What's his name in the wiki and in the Fedora account system? Someone needs to check that he has completed the CLA and then add him to the EditGroup. - J< From katzj at redhat.com Mon Aug 21 15:13:45 2006 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 21 Aug 2006 11:13:45 -0400 Subject: Multilib in Extras repo? In-Reply-To: <20060821140943.1d820124.bugs.michael@gmx.net> References: <20060821140943.1d820124.bugs.michael@gmx.net> Message-ID: <1156173225.29467.47.camel@aglarond.local> On Mon, 2006-08-21 at 14:09 +0200, Michael Schwendt wrote: > I've looked a bit into preparing the Extras push script for multilib > support. In particular: Thanks a lot for looking into this -- it's something I've been meaning to do, but just haven't gotten enough round 'tuits. :-/ > - Find all multicompat -devel binary rpms (considering virtual packages > and ExcludeArch) and copy them to their multilib capable arch repository, > e.g. (i386/i586/i686/athlon -> x86_64). > > - Examine the unresolved dependencies of the multicompat packages and > copy all missing Extras packages into the target repository, too. > > For the dep resolving, I've used the Yum back-end's returnPackagesByDep() > method. Although the results look reasonable -- i.e. I see the -devel > packages pull it their mother packages and all their deps in Extras -- > I'm not an expert in Yum API programming and have yet to find out what > corner-cases one may need to deal with (Obsoletes? arch/multiarch > package picking extra-burden?) and what other pitfalls may be lurking. This is what we do for Core with the addition of also having a whitelist/blacklist (so that relevant non -devel packages, eg, things with gtk+ or pam modules can be included). > Has anyone else spent thoughts on this? Too late for FE6? > > What is the estimated multilib readiness of FE6? Do we expect > many file conflicts (due to arch-specific stuff in generated > headers) or package installer/updater problems (on multilib > installations)? I expect a fair bit of conflicts both on the runtime and the -devel side... unfortunately, the only way to really be able to say for sure is to actually check the packages. My initial thought was to enable something along these lines for Extras devel right after FC6 came out to give time for things to shake out. I could be convinced that doing it now for FE6 and getting things into shape is the right answer, though Jeremy From mattdm at mattdm.org Mon Aug 21 15:40:09 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Mon, 21 Aug 2006 11:40:09 -0400 Subject: [Possible Spam] Re: SPF failures nuke fedora-extras* msgs from redhat.com In-Reply-To: References: <20060820151444.GA8534@jadzia.bu.edu> Message-ID: <20060821154009.GA20151@jadzia.bu.edu> On Mon, Aug 21, 2006 at 04:04:54PM +0200, Paul Wouters wrote: > First, I believe this is stock spamassassin rpm packaging, so that would > then be a fedora bug. But second, AFAIK, it *is* what SPF is for. If a It does seem odd that it's getting flagged for you when it shouldn't be.) > machine claiming to send on behalf of a domain is not listed in a TXT > record for that domain, then it is a roque sender and therefor fake, > and therefor should be dropped. It should *not* be dropped -- it should be flagged for further inspection. This is the only way to make SPF compatible with the existing internet. (Otherwise, SRS would have to be implemented everywhere, and SRS is kinda nasty.) -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From notting at redhat.com Mon Aug 21 16:05:42 2006 From: notting at redhat.com (Bill Nottingham) Date: Mon, 21 Aug 2006 12:05:42 -0400 Subject: comps and gtk In-Reply-To: <44E7834B.6040804@cs.nmsu.edu> References: <20060729093041.GA2701@free.fr> <1154355884.20753.5.camel@orodruin.boston.redhat.com> <44E7834B.6040804@cs.nmsu.edu> Message-ID: <20060821160542.GA27975@nostromo.devel.redhat.com> Rick L Vinyard Jr (rvinyard at cs.nmsu.edu) said: > Take a look at the following two categories: > gnome-software-development > GNOME Software Development > Install these packages in order to develop GTK+ and > GNOME graphical applications. > > xfce-software-development > XFCE Software Development > Install these packages in order to develop GTK+ and > XFCE graphical applications. > > In the former, there are packages such as gazpacho, gtkmm24-devel and > anjuta, et. al. In the latter there are gtk2-devel, glade2, glib2-devel, > et. al. > > I think there will need to be one of two changes: > 1) Allow gtk2-devel to be in both GNOME and XFCE development categories > 2) Create a GTK+ and language bindings development category Take it out of both and let it get pulled in by dependencies. :) Bill From wtogami at redhat.com Mon Aug 21 16:13:18 2006 From: wtogami at redhat.com (Warren Togami) Date: Mon, 21 Aug 2006 12:13:18 -0400 Subject: [Possible Spam] Re: SPF failures nuke fedora-extras* msgs from redhat.com In-Reply-To: References: <20060820151444.GA8534@jadzia.bu.edu> Message-ID: <44E9DB9E.6080701@redhat.com> Paul Wouters wrote: > On Sun, 20 Aug 2006, Matthew Miller wrote: > >> On Sun, Aug 20, 2006 at 04:42:55PM +0200, Paul Wouters wrote: >>> I wondered why I was not receiving any fedora-extras messages for a week. >>> So after tweaking my procmail rules, I found it all email was deleted >>> as spam, because it scores "SPFFAIL". >> Ow! Never treat SPFFAIL that way -- that's not what SPF is for. > > First, I believe this is stock spamassassin rpm packaging, so that would > then be a fedora bug. But second, AFAIK, it *is* what SPF is for. If a > machine claiming to send on behalf of a domain is not listed in a TXT > record for that domain, then it is a roque sender and therefor fake, > and therefor should be dropped. > > Paul > stock spamassassin does SPF only if you install the optional perl-Mail-SPF-Query from Fedora Extras. http://david.woodhou.se/why-not-spf.html There is a good reason why we don't enable SPF by default in Fedora. It is not particularly useful at protecting you against spam. Warren Togami wtogami at redhat.com From paul at cypherpunks.ca Mon Aug 21 17:54:09 2006 From: paul at cypherpunks.ca (Paul Wouters) Date: Mon, 21 Aug 2006 19:54:09 +0200 (CEST) Subject: [Possible Spam] Re: [Possible Spam] Re: SPF failures nuke fedora-extras* msgs from redhat.com Message-ID: On Mon, 21 Aug 2006, Warren Togami wrote: > stock spamassassin does SPF only if you install the optional > perl-Mail-SPF-Query from Fedora Extras. Correct. Which I have done. > http://david.woodhou.se/why-not-spf.html Let's not discuss the usefulness of SPF here.... > There is a good reason why we don't enable SPF by default in Fedora. It is > not particularly useful at protecting you against spam. If that is redhat's opinion, they should stop publishing spf records. If it is not, then someone needs to forward this complaind that enabling SPF with an extras pacakge is currently failing for the redhat setup, and needs to be fixed. So, either this should go to the sysadmins responsoble for redhat, or it should go as a bug report to perl-Mail-SPF-Query. I'm happy to do either if I know which one is correct. What is not a good way to proceed is not doing anything. It will cause people deploying redhat/fedora boxes with SPF enabled to miss various if not all redhat mailinglist messages. Paul From steve at silug.org Mon Aug 21 18:37:39 2006 From: steve at silug.org (Steven Pritchard) Date: Mon, 21 Aug 2006 13:37:39 -0500 Subject: [Possible Spam] Re: [Possible Spam] Re: SPF failures nuke fedora-extras* msgs from redhat.com In-Reply-To: References: Message-ID: <20060821183739.GA29602@osiris.silug.org> On Mon, Aug 21, 2006 at 07:54:09PM +0200, Paul Wouters wrote: > So, either this should go to the sysadmins responsoble for redhat, It's definitely their problem. > or it should go as a bug report to perl-Mail-SPF-Query. Please don't do that. :-) Steve -- Steven Pritchard - K&S Pritchard Enterprises, Inc. Email: steve at kspei.com http://www.kspei.com/ Phone: (618)398-3000 Mobile: (618)567-7320 From gemi at bluewin.ch Mon Aug 21 18:45:20 2006 From: gemi at bluewin.ch (=?ISO-8859-1?Q?G=E9rard?= Milmeister) Date: Mon, 21 Aug 2006 20:45:20 +0200 Subject: Removal of package from a repository Message-ID: <1156185921.19379.1.camel@scriabin.tannenrauch.ch> The package TeXmacs currently does not build correctly on Fedora devel. There are, however, versions in the development repository. What must I do to request their removal. Shoud I open an ticket? Regards -- G?rard Milmeister Langackerstrasse 49 CH-8057 Z?rich From buildsys at fedoraproject.org Mon Aug 21 18:49:35 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Mon, 21 Aug 2006 14:49:35 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-21 Message-ID: <20060821184935.2DAA9152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 12 efont-unicode-bdf-0.4.2-6.fc5 gtkwave-3.0.10-1.fc5 hfsplus-tools-332.14-2.fc5 jfbterm-0.4.7-7.fc5 katapult-0.3.1.3-4.fc5 libopensync-plugin-evolution2-0.18-8.fc5 nqc-3.1.4-2.fc5 openal-0.0.9-0.6.20060204cvs.fc5 perl-POE-Component-Server-SOAP-1.09-2.fc5 sjasm-0.39-0.3.g1.fc5 wine-docs-0.9.19-1.fc5 xdg-utils-1.0-0.6.beta3.fc5 Packages built and released for Fedora Extras 4: 4 gtkwave-3.0.10-1.fc4 openal-0.0.9-0.5.20060204cvs.fc4 wine-docs-0.9.19-1.fc4 xdg-utils-1.0-0.6.beta3.fc4 Packages built and released for Fedora Extras 3: 3 openal-0.0.9-0.5.20060204cvs.fc3 wine-0.9.19-1.fc3 wine-docs-0.9.19-1.fc3 Packages built and released for Fedora Extras development: 10 gtkwave-3.0.10-1.fc6 jfbterm-0.4.7-7.fc6 katapult-0.3.1.3-4.fc6 koffice-1.5.2-1.fc6 libopensync-plugin-evolution2-0.18-8.fc6 nqc-3.1.4-3.fc6 openal-0.0.9-0.7.20060204cvs.fc6 sjasm-0.39-0.3.g1.fc6 wine-docs-0.9.19-1.fc6 xdg-utils-1.0-0.6.beta3.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Mon Aug 21 18:50:05 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Mon, 21 Aug 2006 14:50:05 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-21 Message-ID: <20060821185005.B48FD152169@buildsys.fedoraproject.org> UNKNOWN OWNER (possibly Core package): device-mapper 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) ftp 5: 0:0.17-33.fc5 (FC5-updates) 6: 0:0.17-32.1.2.4 (FC6) lvm2 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) mozilla 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) quagga 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) andreas.bierfert AT lowlatency.de: dillo 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) libpqxx 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) wine 3: 0:0.9.19-1.fc3 (FE3) 4: 0:0.9.16-2.fc4 (FE4) 5: 0:0.9.17-1.fc5 (FE5) 6: 0:0.9.17-1.fc6 (FE6) denis AT poolshark.org: k3d 4: 0:0.5.16.0-4.fc4 (FE4) 5: 0:0.5.16.0-3.fc5 (FE5) 6: 0:0.5.16.0-3.fc6 (FE6) foolish AT guezz.net: serpentine 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) gemi AT bluewin.ch: TeXmacs 5: 0:1.0.6.5-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) ghenry AT suretecsystems.com: pgadmin3 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) jspaleta AT gmail.com: istanbul 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) kengert AT redhat.com: seamonkey 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) lemenkov AT newmail.ru: fuse-encfs 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) stratagus 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) liljencrantz AT gmail.com: fish 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) lmacken AT redhat.com: dclib 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) python-myghty 5: 0:1.0.2-2.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) valknut 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) luya_tfz AT thefinalzone.com: gdesklets 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) meme AT daughtersoftiresias.org: fortune-firefly 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) mpeters AT mac.com: firestarter 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) noa AT resare.com: vorbisgain 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) nomis80 AT nomis80.org: camstream 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) opencv 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) paul AT all-the-johnsons.co.uk: XaraLX 5: 0:0.7-3.fc5.r1614 (FE5) 6: 0:0.7-2.fc6.r1614 (FE6) paul AT city-fan.org: perl-String-CRC32 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) petersen AT redhat.com: m17n-db 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) rpm AT timj.co.uk: php-pear-DB 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) ryo-dairiki AT users.sourceforge.net: scim-tomoe 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) thomas AT apestaart.org: flumotion 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) ---------------------------------------------------------------------- camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: UNKNOWN OWNER (possibly Core package) 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: liljencrantz AT gmail.com 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) ftp: UNKNOWN OWNER (possibly Core package) 5: 0:0.17-33.fc5 (FC5-updates) 6: 0:0.17-32.1.2.4 (FC6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) k3d: denis AT poolshark.org 4: 0:0.5.16.0-4.fc4 (FE4) 5: 0:0.5.16.0-3.fc5 (FE5) 6: 0:0.5.16.0-3.fc6 (FE6) libpqxx: andreas.bierfert AT lowlatency.de 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) lvm2: UNKNOWN OWNER (possibly Core package) 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) mozilla: UNKNOWN OWNER (possibly Core package) 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.2-2.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) quagga: UNKNOWN OWNER (possibly Core package) 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) seamonkey: kengert AT redhat.com 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) TeXmacs: gemi AT bluewin.ch 5: 0:1.0.6.5-1.fc5 (FE5) 6: 0:1.0.6.3-1.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) vorbisgain: noa AT resare.com 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) wine: andreas.bierfert AT lowlatency.de 3: 0:0.9.19-1.fc3 (FE3) 4: 0:0.9.16-2.fc4 (FE4) 5: 0:0.9.17-1.fc5 (FE5) 6: 0:0.9.17-1.fc6 (FE6) XaraLX: paul AT all-the-johnsons.co.uk 5: 0:0.7-3.fc5.r1614 (FE5) 6: 0:0.7-2.fc6.r1614 (FE6) From buildsys at fedoraproject.org Mon Aug 21 19:10:53 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Mon, 21 Aug 2006 19:10:53 -0000 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-21 Message-ID: <20060821191053.5339.64110@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (137 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (137 days) wine-core - 0.9.17-1.fc6.i386 (26 days) bdpepple AT ameritech.net contact-lookup-applet - 0.14-3.fc6.i386 (14 days) contact-lookup-applet - 0.14-3.fc6.ppc (14 days) contact-lookup-applet - 0.14-3.fc6.x86_64 (14 days) byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (33 days) gaim-guifications - 2.12-3.fc5.ppc (33 days) gaim-guifications - 2.12-3.fc5.x86_64 (33 days) caillon AT redhat.com banshee - 0.10.11-1.fc6.i386 banshee - 0.10.11-1.fc6.ppc banshee - 0.10.11-1.fc6.x86_64 foolish AT guezz.net muine - 0.8.5-1.fc6.i386 muine - 0.8.5-1.fc6.ppc muine - 0.8.5-1.fc6.x86_64 gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (25 days) amarok - 1.4.1-3.fc6.ppc (25 days) showimg-pgsql - 0.9.5-7.fc4.i386 (14 days) showimg-pgsql - 0.9.5-7.fc4.ppc (14 days) showimg-pgsql - 0.9.5-7.fc4.x86_64 (14 days) showimg-pgsql - 0.9.5-7.fc5.i386 (14 days) showimg-pgsql - 0.9.5-7.fc5.ppc (14 days) showimg-pgsql - 0.9.5-7.fc5.x86_64 (14 days) green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (26 days) jogl - 1.1.1-14.fc5.ppc (29 days) ivazquez AT ivazquez.net gnome-applet-music - 0.9.0-1.fc6.i386 (33 days) gnome-applet-music - 0.9.0-1.fc6.ppc (33 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (33 days) nautilus-search-tool - 0.2-1.fc5.i386 (33 days) nautilus-search-tool - 0.2-1.fc5.ppc (33 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (33 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (33 days) gfontview - 0.5.0-5.fc5.ppc (33 days) gfontview - 0.5.0-5.fc5.x86_64 (33 days) gtkhtml36 - 3.6.2-5.fc6.i386 (33 days) gtkhtml36 - 3.6.2-5.fc6.ppc (33 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (33 days) libvisual-plugins - 0.2.0-3.fc5.i386 (33 days) libvisual-plugins - 0.2.0-3.fc5.i386 (33 days) libvisual-plugins - 0.2.0-3.fc5.ppc (33 days) libvisual-plugins - 0.2.0-3.fc5.ppc (33 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (33 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (33 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (96 days) syck-php - 0.55-7.fc5.i386 (96 days) syck-php - 0.55-7.fc5.ppc (96 days) syck-php - 0.55-7.fc5.ppc (96 days) syck-php - 0.55-7.fc5.x86_64 (96 days) syck-php - 0.55-7.fc5.x86_64 (96 days) paul AT all-the-johnsons.co.uk gtksourceview-sharp - 2.0-15.fc6.i386 gtksourceview-sharp - 2.0-15.fc6.ppc gtksourceview-sharp - 2.0-15.fc6.x86_64 rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (33 days) libibverbs - 1.0.3-1.fc6.ppc (33 days) libibverbs - 1.0.3-1.fc6.x86_64 (33 days) libibverbs-utils - 1.0.3-1.fc6.i386 (33 days) libibverbs-utils - 1.0.3-1.fc6.ppc (33 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (33 days) tcallawa AT redhat.com gambas-runtime - 1.0.14-2.fc5.i386 (13 days) thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (33 days) directfb - 0.9.24-5.fc5.ppc (33 days) directfb - 0.9.24-5.fc5.x86_64 (33 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.i386 requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) showimg-pgsql-0.9.5-7.fc5.x86_64 requires libpqxx-2.6.6.so()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.ppc requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.i386 requires libpqxx-2.6.6.so Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.x86_64 requires libpqxx-2.6.6.so()(64bit) Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.ppc requires libpqxx-2.6.6.so Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer banshee-0.10.11-1.fc6.i386 requires mono(gconf-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(glade-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(pango-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gnome-vfs-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(glib-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gtk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gnome-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gdk-sharp) = 0:2.8.0.0 contact-lookup-applet-0.14-3.fc6.i386 requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 gambas-runtime-1.0.14-2.fc5.i386 requires libgettextlib-0.14.5.so gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(gnome-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(gtk-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(glib-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(gdk-sharp) = 0:2.8.0.0 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 muine-0.8.5-1.fc6.i386 requires mono(glib-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.i386 requires mono(gtk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.i386 requires mono(gdk-sharp) = 0:2.8.0.0 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- banshee-0.10.11-1.fc6.x86_64 requires mono(gconf-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(glade-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gnome-vfs-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gtk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gdk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gnome-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(pango-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(glib-sharp) = 0:2.8.0.0 contact-lookup-applet-0.14-3.fc6.x86_64 requires libebook-1.2.so.5()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(gnome-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(gtk-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(glib-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(gdk-sharp) = 0:2.8.0.0 libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) muine-0.8.5-1.fc6.x86_64 requires mono(gdk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.x86_64 requires mono(gtk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.x86_64 requires mono(glib-sharp) = 0:2.8.0.0 nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.17-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 banshee-0.10.11-1.fc6.ppc requires mono(gconf-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(glade-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(pango-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gnome-vfs-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(glib-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gtk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gnome-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gdk-sharp) = 0:2.8.0.0 contact-lookup-applet-0.14-3.fc6.ppc requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(gnome-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(gtk-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(glib-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(gdk-sharp) = 0:2.8.0.0 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 muine-0.8.5-1.fc6.ppc requires mono(glib-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.ppc requires mono(gtk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.ppc requires mono(gdk-sharp) = 0:2.8.0.0 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 ====================================================================== New report for: green AT redhat.com package: jogl - 1.1.1-14.fc5.ppc from fedora-extras-development-ppc unresolved deps: libgcj.so.7 ====================================================================== New report for: bdpepple AT ameritech.net package: contact-lookup-applet - 0.14-3.fc6.i386 from fedora-extras-development-i386 unresolved deps: libebook-1.2.so.5 package: contact-lookup-applet - 0.14-3.fc6.x86_64 from fedora-extras-development-x86_64 unresolved deps: libebook-1.2.so.5()(64bit) package: contact-lookup-applet - 0.14-3.fc6.ppc from fedora-extras-development-ppc unresolved deps: libebook-1.2.so.5 From rdieter at math.unl.edu Mon Aug 21 19:11:57 2006 From: rdieter at math.unl.edu (Rex Dieter) Date: Mon, 21 Aug 2006 14:11:57 -0500 Subject: Removal of package from a repository References: <1156185921.19379.1.camel@scriabin.tannenrauch.ch> Message-ID: G?rard Milmeister wrote: > The package TeXmacs currently does not build correctly on Fedora devel. > There are, however, versions in the development repository. What must > I do to request their removal. Shoud I open an ticket? http://fedoraproject.org/wiki/Extras/FC6Status -- Rex From tdiehl at rogueind.com Mon Aug 21 20:42:20 2006 From: tdiehl at rogueind.com (Tom Diehl) Date: Mon, 21 Aug 2006 16:42:20 -0400 (EDT) Subject: SPF failures nuke fedora-extras* msgs from redhat.com In-Reply-To: References: Message-ID: On Mon, 21 Aug 2006, Paul Wouters wrote: > On Mon, 21 Aug 2006, Warren Togami wrote: > >> stock spamassassin does SPF only if you install the optional >> perl-Mail-SPF-Query from Fedora Extras. > > Correct. Which I have done. > >> http://david.woodhou.se/why-not-spf.html > > Let's not discuss the usefulness of SPF here.... Yes I know, do not confuse the issue with facts!! >> There is a good reason why we don't enable SPF by default in Fedora. It is >> not particularly useful at protecting you against spam. > > If that is redhat's opinion, they should stop publishing spf records. If it is There are some good reasons to publish SPF records even if you do not believe in it. I publish SPF records for some of my domains because certain large email providers require it of you wanr/need to pass large amounts of mail through their systems. They do not even reject mail based soley on SPF records. It is used as a method for scoring. Regards, -- Tom Diehl tdiehl at rogueind.com Spamtrap address mtd123 at rogueind.com From Axel.Thimm at ATrpms.net Mon Aug 21 21:32:49 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Mon, 21 Aug 2006 23:32:49 +0200 Subject: SPF failures nuke fedora-extras* msgs from redhat.com In-Reply-To: <20060821183739.GA29602@osiris.silug.org> References: <20060821183739.GA29602@osiris.silug.org> Message-ID: <20060821213249.GA1927@neu.nirvana> On Mon, Aug 21, 2006 at 01:37:39PM -0500, Steven Pritchard wrote: > On Mon, Aug 21, 2006 at 07:54:09PM +0200, Paul Wouters wrote: > > So, either this should go to the sysadmins responsoble for redhat, > > It's definitely their problem. > > > or it should go as a bug report to perl-Mail-SPF-Query. > > Please don't do that. :-) I agree, whether a mail domain hosting some resources of Fedora has some policy on SPF and whether SPF is available to other users thorugh Fedora is a different story. We don't want to endorse either side through the repo's contents. Paul, could you contact postmaster@ which is the `person' the RFCs scapegoat for such a case? -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bugs.michael at gmx.net Mon Aug 21 22:25:19 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Tue, 22 Aug 2006 00:25:19 +0200 Subject: clamav-exim Message-ID: <20060822002519.d5949917.bugs.michael@gmx.net> I've stumbled upon mysterious "clamav-exim" packages in FE in all repos except FE3: 4/i386/clamav-exim-0.86.2-5.fc4.i386.rpm 4/ppc/clamav-exim-0.86.2-5.fc4.ppc.rpm 4/x86_64/clamav-exim-0.86.2-5.fc4.x86_64.rpm 5/i386/clamav-exim-0.86.2-5.fc5.i386.rpm 5/ppc/clamav-exim-0.86.2-5.fc5.ppc.rpm 5/x86_64/clamav-exim-0.86.2-5.fc5.x86_64.rpm development/i386/clamav-exim-0.86.2-5.fc5.i386.rpm development/ppc/clamav-exim-0.86.2-5.fc5.ppc.rpm development/x86_64/clamav-exim-0.86.2-5.fc5.x86_64.rpm They are from Sep 10 2005 and point to an old and meanwhile non-existant clamav src.rpm. Since the clamav %changelog mentions that this package has been dropped, I've deleted the binary rpms in all repos. They will be gone with the next push. From bugs.michael at gmx.net Mon Aug 21 22:25:45 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Tue, 22 Aug 2006 00:25:45 +0200 Subject: crossfire-maps-devel Message-ID: <20060822002545.239eeada.bugs.michael@gmx.net> I've stumbled upon orphaned/obsolete "crossfire-maps-devel" packages in FE Development: i386/crossfire-maps-devel-1.9.0-1.fc6.noarch.rpm ppc/crossfire-maps-devel-1.9.0-1.fc6.noarch.rpm x86_64/crossfire-maps-devel-1.9.0-1.fc6.noarch.rpm They point to an old and meanwhile non-existant src.rpm. Since the crossfire-maps package marks them as Obsoletes, I've deleted the binary rpms from "development". They will be gone with the next push. From wart at kobold.org Mon Aug 21 22:35:50 2006 From: wart at kobold.org (Michael Thomas) Date: Mon, 21 Aug 2006 15:35:50 -0700 Subject: crossfire-maps-devel In-Reply-To: <20060822002545.239eeada.bugs.michael@gmx.net> References: <20060822002545.239eeada.bugs.michael@gmx.net> Message-ID: <44EA3546.40809@kobold.org> Michael Schwendt wrote: > I've stumbled upon orphaned/obsolete "crossfire-maps-devel" packages > in FE Development: > > i386/crossfire-maps-devel-1.9.0-1.fc6.noarch.rpm > ppc/crossfire-maps-devel-1.9.0-1.fc6.noarch.rpm > x86_64/crossfire-maps-devel-1.9.0-1.fc6.noarch.rpm > > They point to an old and meanwhile non-existant src.rpm. Since the > crossfire-maps package marks them as Obsoletes, I've deleted the binary > rpms from "development". This is true. As of version 1.9.1 there is no reason to separate out the contents of the crossfire-maps and crossfire-maps-devel packages. > They will be gone with the next push. Thanks. --Mike From fedora at theholbrooks.org Mon Aug 21 23:34:22 2006 From: fedora at theholbrooks.org (Brandon Holbrook) Date: Mon, 21 Aug 2006 18:34:22 -0500 Subject: Ignacio / php-json In-Reply-To: References: <1155944907.2982.22.camel@localhost> <44E6DA05.9080708@hhs.nl> <20060819165012.GA23627@osiris.silug.org> <44E7666A.9050907@theholbrooks.org> <20060819223653.ce67f8cb.bugs.michael@gmx.net> <44E77B26.7000101@theholbrooks.org> Message-ID: <44EA42FE.6070805@theholbrooks.org> Jason L Tibbitts III wrote: > No, it's fedorabugs, but I've been waiting for you to apply there and > haven't seen the request yet. I checked again and see that you do > have your cvsextras membership but aren't currently a member of > fedorabugs. I double checked the list of pending approvals there and > you are not on that list. > > (I'm checking the user ID "static"; please correct me if that's > wrong.) > I don't know what could have been happening... I've removed the entry that was in my grouplist and re-submitted a request for membership... Yes static is the correct username. Thanks Jason! From jspaleta at gmail.com Tue Aug 22 00:23:47 2006 From: jspaleta at gmail.com (Jeff Spaleta) Date: Mon, 21 Aug 2006 16:23:47 -0800 Subject: Call for devel tree testing with an aim at resurrecting istanbul. Message-ID: <604aa7910608211723q50e7b2fan65710251673be89f@mail.gmail.com> Good Morning campers, I need some help from people running rawhide or a test release to help me prep a new istanbul package for the devel tree aimed at fc6. Since I couldn't find a sucker..err uhm volunteer...to take this package over before I left for the great white north.. this thing is still sort of sitting in limbo. The good news is I have a package building for istanbul 0.2.1 using the gstreamer bits from core development. The bad news is I really can't follow this up with the appropriate amount of devel tree testing myself, I simply don't have the bandwidth at home right now to run a development box. So what I need is for someone to act as my proxy and help me test to make sure the basic minimum of functionality works.... even if the video is still rough. More excitingly the new istanbul claims it can do audio recording and claims it can record the mouse pointer... so if the new features work then we have a pretty useful tool to create theora tour videos. Regardless of how well it actually functions, the first step is making sure it does build and does the basic operation on a devel box. I can email my latest srpm to people who want to test this on a devel box. Sadly I don't have a good place to park the srpm for people to upload right now. Any takers? Backstory: Since the magic behind instanbul is just a fancy presentation of several gst modules working together, the underlying gst modules need to be present for istanbul to work. As of the time of my move to the great white north, the move to gst .10 had left the necessary modules to do X display capture out of the "good" category and it was instead lingering in the low quality category (not the legally grey category). As a result istanbul 0.2.1 will not work on fc5.. but it does appear that the needed gst module is in fc6's gstreamer-plugins-good package. -jef From gemi at bluewin.ch Tue Aug 22 00:49:51 2006 From: gemi at bluewin.ch (=?ISO-8859-1?Q?G=E9rard?= Milmeister) Date: Tue, 22 Aug 2006 02:49:51 +0200 Subject: Removal of package from a repository In-Reply-To: References: <1156185921.19379.1.camel@scriabin.tannenrauch.ch> Message-ID: <1156207791.8590.0.camel@scriabin.tannenrauch.ch> On Mon, 2006-08-21 at 14:11 -0500, Rex Dieter wrote: > G?rard Milmeister wrote: > > > The package TeXmacs currently does not build correctly on Fedora devel. > > There are, however, versions in the development repository. What must > > I do to request their removal. Shoud I open an ticket? > > http://fedoraproject.org/wiki/Extras/FC6Status Ok. Thanks. -- G?rard Milmeister Langackerstrasse 49 CH-8057 Z?rich From jwboyer at jdub.homelinux.org Tue Aug 22 02:07:33 2006 From: jwboyer at jdub.homelinux.org (Josh Boyer) Date: Mon, 21 Aug 2006 21:07:33 -0500 Subject: Call for devel tree testing with an aim at resurrecting istanbul. In-Reply-To: <604aa7910608211723q50e7b2fan65710251673be89f@mail.gmail.com> References: <604aa7910608211723q50e7b2fan65710251673be89f@mail.gmail.com> Message-ID: <1156212453.2683.63.camel@vader.jdub.homelinux.org> On Mon, 2006-08-21 at 16:23 -0800, Jeff Spaleta wrote: > > Regardless of how well it actually functions, the first step is making > sure it does build and does the basic operation on a devel box. I can > email my latest srpm to people who want to test this on a devel box. > Sadly I don't have a good place to park the srpm for people to upload > right now. Any takers? I can host it. Send it to me and I'll put it up. I even have a rawhide box I can try building it on. josh From s.mako at gmx.net Tue Aug 22 05:46:52 2006 From: s.mako at gmx.net (Zoltan Kota) Date: Tue, 22 Aug 2006 07:46:52 +0200 (CEST) Subject: recode in comps? Message-ID: Hi, Should I add 'recode' to comps-fe6 (and fe5)? I can't really find any suitable category. Zoltan From paul at all-the-johnsons.co.uk Tue Aug 22 09:01:56 2006 From: paul at all-the-johnsons.co.uk (PFJ) Date: Tue, 22 Aug 2006 10:01:56 +0100 Subject: Was there a push last night? Message-ID: <1156237316.2672.14.camel@localhost.localdomain> Hi, It could have been me, but was there an FE push last night for rawhide? I don't recall seeing any notification of it only the broken upgrade path notices. BTW : I've uploaded a newer version of both XaraLX and gtksourceview-sharp for both FC5 and Rawhide. TTFN Paul -- "Logic, my dear Zoe, is merely the ability to be wrong with authority" - Dr Who From lists at timj.co.uk Tue Aug 22 09:31:02 2006 From: lists at timj.co.uk (Tim Jackson) Date: Tue, 22 Aug 2006 10:31:02 +0100 Subject: clamav-exim In-Reply-To: <20060822002519.d5949917.bugs.michael@gmx.net> References: <20060822002519.d5949917.bugs.michael@gmx.net> Message-ID: <44EACED6.6020203@timj.co.uk> Michael Schwendt wrote: > I've stumbled upon mysterious "clamav-exim" packages in FE in all repos > except FE3: [...] > I've deleted the binary rpms in all repos. You did the right thing. See also bug #181450. Tim From bugs.michael at gmx.net Tue Aug 22 10:09:46 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Tue, 22 Aug 2006 12:09:46 +0200 Subject: Was there a push last night? In-Reply-To: <1156237316.2672.14.camel@localhost.localdomain> References: <1156237316.2672.14.camel@localhost.localdomain> Message-ID: <20060822120946.9dab07e4.bugs.michael@gmx.net> On Tue, 22 Aug 2006 10:01:56 +0100, PFJ wrote: > Hi, > > It could have been me, but was there an FE push last night for rawhide? Yes. > I don't recall seeing any notification of it only the broken upgrade > path notices. https://www.redhat.com/archives/fedora-extras-list/2006-August/msg00527.html From dwmw2 at infradead.org Tue Aug 22 18:30:48 2006 From: dwmw2 at infradead.org (David Woodhouse) Date: Tue, 22 Aug 2006 19:30:48 +0100 Subject: [Possible Spam] Re: [Possible Spam] Re: SPF failures nuke fedora-extras* msgs from redhat.com In-Reply-To: References: Message-ID: <1156271448.29825.29.camel@pmac.infradead.org> On Mon, 2006-08-21 at 19:54 +0200, Paul Wouters wrote: > If that is redhat's opinion, they should stop publishing spf records. Do not mistake the publication of records by Red Hat sysadmins for a company policy which approves of such a stupid scheme. This _has_ been raised internally but I wouldn't really expect it to change any time soon. In the meantime, the company just continues to advertise its technical cluelessness in this particular respect. > So, either this should go to the sysadmins responsoble for redhat, or it should > go as a bug report to perl-Mail-SPF-Query. I'm happy to do either if I know > which one is correct. Personally, I think we should drop perl-Mail-SPF-Query, or at _least_ modify our SpamAssassin package so that it needs to be _explicitly_ asked to do SPF rather than doing so by default if the package is installed. -- dwmw2 From steve at silug.org Tue Aug 22 18:56:24 2006 From: steve at silug.org (Steven Pritchard) Date: Tue, 22 Aug 2006 13:56:24 -0500 Subject: [Possible Spam] Re: [Possible Spam] Re: SPF failures nuke fedora-extras* msgs from redhat.com In-Reply-To: <1156271448.29825.29.camel@pmac.infradead.org> References: <1156271448.29825.29.camel@pmac.infradead.org> Message-ID: <20060822185624.GA31391@osiris.silug.org> On Tue, Aug 22, 2006 at 07:30:48PM +0100, David Woodhouse wrote: > Personally, I think we should drop perl-Mail-SPF-Query It's there for some (optional) functionality in amavisd-new. SpamAssassin being able to use it was a side-effect. > or at _least_ modify our SpamAssassin package so that it needs to be > _explicitly_ asked to do SPF rather than doing so by default if the > package is installed. It looks like that would just be a matter of commenting out the "loadplugin Mail::SpamAssassin::Plugin::SPF" in /etc/mail/spamassassin/init.pre. Steve -- Steven Pritchard - K&S Pritchard Enterprises, Inc. Email: steve at kspei.com http://www.kspei.com/ Phone: (618)398-3000 Mobile: (618)567-7320 From mattdm at mattdm.org Tue Aug 22 19:38:53 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Tue, 22 Aug 2006 15:38:53 -0400 Subject: [Possible Spam] Re: [Possible Spam] Re: SPF failures nuke fedora-extras* msgs from redhat.com In-Reply-To: <1156271448.29825.29.camel@pmac.infradead.org> References: <1156271448.29825.29.camel@pmac.infradead.org> Message-ID: <20060822193853.GA18107@jadzia.bu.edu> On Tue, Aug 22, 2006 at 07:30:48PM +0100, David Woodhouse wrote: > Personally, I think we should drop perl-Mail-SPF-Query, or at _least_ > modify our SpamAssassin package so that it needs to be _explicitly_ > asked to do SPF rather than doing so by default if the package is > installed. I disagree with you on SPF in many regards, but this part I totally agree with. Having a package behave totally differently depending simply on the *presence* of a perl module is bad behavior. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From bugzilla at redhat.com Tue Aug 22 20:16:48 2006 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 22 Aug 2006 16:16:48 -0400 Subject: [Bug 180066] Request: Inclusion of a ruby template file In-Reply-To: Message-ID: <200608222016.k7MKGm4H009454@bugzilla.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Request: Inclusion of a ruby template file https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180066 ville.skytta at iki.fi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |CURRENTRELEASE Fixed In Version|1.5-1 |5.0-2 ------- Additional Comments From ville.skytta at iki.fi 2006-08-22 16:06 EST ------- The updated version is shipped in rpmdevtools 5.0-2 -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. From orion at cora.nwra.com Tue Aug 22 20:16:57 2006 From: orion at cora.nwra.com (Orion Poplawski) Date: Tue, 22 Aug 2006 14:16:57 -0600 Subject: comps comps-fe6.xml,1.13,1.14 In-Reply-To: <20060819181234.0a9c31d9@ludwig-alpha> References: <200608191032.k7JAWHX3030206@cvs-int.fedora.redhat.com> <20060819181234.0a9c31d9@ludwig-alpha> Message-ID: <44EB6639.20700@cora.nwra.com> Christian Iseli wrote: > On Sat, 19 Aug 2006 03:32:15 -0700, Tim Jackson wrote: >> Modified Files: >> comps-fe6.xml > > Please update comps-fe6.xml.in (*not* comps-fe6.xml) otherwise your > changes will be lost next time comps-fe6.xml is rebuilt from the .in > file... > > Cheers, > Christian > Why is comps-fe6.xml even in CVS if it is auto generated? -- Orion Poplawski System Administrator 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion at cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com From opensource at till.name Tue Aug 22 22:11:52 2006 From: opensource at till.name (Till Maas) Date: Wed, 23 Aug 2006 00:11:52 +0200 Subject: Contacting the Fedora Account System's management team In-Reply-To: <200608202259.58934.nman64@n-man.com> References: <200608201358.40043.opensource@till.name> <200608202259.58934.nman64@n-man.com> Message-ID: <200608230012.01288.opensource@till.name> Hello, I just realized that I replied to you only in private, not via the list. So here is my answer, again. On Monday 21 August 2006 05:59, Patrick W. Barnes wrote: > Your particular issue is arising because the email address you have > registered in the Account System is not a UID on your signing key. You > need to either add opensource at still.name as a UID on your signing key or > change the address you are using in the Account System to > till.maas at still.name. Actually I added the needed UID (opensource at till.name) last friday and made it even primary. Nevertheless, the same error still occurs, see here: http://pgpkeys.pca.dfn.de/pks/lookup?op=index&fingerprint=on&search=opensource%40till.name Regards, Till PS: Thank you Thorsten for the pointer to the archives :-) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Axel.Thimm at ATrpms.net Tue Aug 22 23:33:46 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Wed, 23 Aug 2006 01:33:46 +0200 Subject: SPF failures nuke fedora-extras* msgs from redhat.com In-Reply-To: <20060822193853.GA18107@jadzia.bu.edu> References: <1156271448.29825.29.camel@pmac.infradead.org> <20060822193853.GA18107@jadzia.bu.edu> Message-ID: <20060822233346.GH5028@neu.nirvana> On Tue, Aug 22, 2006 at 03:38:53PM -0400, Matthew Miller wrote: > On Tue, Aug 22, 2006 at 07:30:48PM +0100, David Woodhouse wrote: > > Personally, I think we should drop perl-Mail-SPF-Query, or at _least_ > > modify our SpamAssassin package so that it needs to be _explicitly_ > > asked to do SPF rather than doing so by default if the package is > > installed. > > I disagree with you on SPF in many regards, but this part I totally agree > with. Having a package behave totally differently depending simply on the > *presence* of a perl module is bad behavior. That's true of a lot of other (optional) perl modules in spamassassin. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From buildsys at fedoraproject.org Wed Aug 23 00:21:37 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Tue, 22 Aug 2006 20:21:37 -0400 (EDT) Subject: Fedora Extras Package Build Report 2006-08-22 Message-ID: <20060823002137.6724B152169@buildsys.fedoraproject.org> Packages built and released for Fedora Extras 5: 18 TeXmacs-1.0.6.6-1.fc5 XaraLX-0.7-4.fc5.r1709 apcupsd-3.12.4-1.fc5 celestia-1.4.1-5.fc5 cln-1.1.13-1.fc5 compat-wxGTK-2.4.2-20.fc5 hnb-1.9.18-2.fc5 inkscape-0.44-4.fc5 js-1.5-5.fc5 k3d-0.6.0.0-1.fc5.1 kdmtheme-1.1.2-2.fc5 kmenu-gnome-0.6-3.fc5 ktorrent-2.0.1-2.fc5 nautilus-actions-1.4-2.fc5 rpmdevtools-5.0-2.fc5 ucarp-1.2-3.fc5 wine-0.9.19-1.fc5 xmms-speex-0.9.1-7.fc5 Packages built and released for Fedora Extras 4: 8 TeXmacs-1.0.6.6-1.fc4 apcupsd-3.12.4-1.fc4 compat-wxGTK-2.4.2-20.fc4 inkscape-0.44-4.fc4 php-eaccelerator-5.0.1_0.9.4-2.fc4 php-mmcache-4.3.11_2.4.6-8.fc4 ucarp-1.2-3.fc4 wine-0.9.19-1.fc4 Packages built and released for Fedora Extras development: 28 XaraLX-0.7-4.fc6.r1709 apcupsd-3.12.4-1.fc6 celestia-1.4.1-5.fc6 clement-2.1-202.fc6 compat-wxGTK-2.4.2-20.fc6 gconfmm26-2.16.0-1.fc6 glibmm24-2.12.0-1 gnome-vfsmm26-2.16.0-1 gobby-0.4.0-10.rc4.fc6 gtkmm24-2.10.0-2.fc6 inkscape-0.44-5.fc6 kdmtheme-1.1.2-2.fc6 keyutils-1.2-1.fc6 kmenu-gnome-0.6-3.fc6 ktorrent-2.0.1-2.fc6 libgnomecanvasmm26-2.16.0-1 libgnomemm26-2.16.0-2 libgnomeuimm26-2.16.0-1 nautilus-actions-1.4-2.fc6 ncftp-3.2.0-1.fc6 php-eaccelerator-5.1.4_0.9.5-0.3.rc1.fc6 python-paste-deploy-0.5-3.fc6 python-paste-script-0.9-4.fc6 rpmdevtools-5.0-2.fc6 tetex-elsevier-0.1.20060516-3.fc6 ucarp-1.2-3.fc6 wine-0.9.19-1.fc6 xmms-speex-0.9.1-7.fc6 For more information about the built packages please see the repository or the Fedora Info Feed: http://fedoraproject.org/infofeed/ From buildsys at fedoraproject.org Wed Aug 23 00:22:07 2006 From: buildsys at fedoraproject.org (buildsys at fedoraproject.org) Date: Tue, 22 Aug 2006 20:22:07 -0400 (EDT) Subject: Broken upgrade paths in FC+FE 2006-08-22 Message-ID: <20060823002207.06E1C152169@buildsys.fedoraproject.org> UNKNOWN OWNER (possibly Core package): device-mapper 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) ftp 5: 0:0.17-33.fc5 (FC5-updates) 6: 0:0.17-32.1.2.4 (FC6) lvm2 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) mozilla 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) quagga 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) andreas.bierfert AT lowlatency.de: dillo 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) libpqxx 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) denis AT poolshark.org: k3d 5: 0:0.6.0.0-1.fc5.1 (FE5) 6: 0:0.5.16.0-3.fc6 (FE6) foolish AT guezz.net: serpentine 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) ghenry AT suretecsystems.com: pgadmin3 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) jspaleta AT gmail.com: istanbul 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) kengert AT redhat.com: seamonkey 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) lemenkov AT newmail.ru: fuse-encfs 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) stratagus 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) liljencrantz AT gmail.com: fish 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) lmacken AT redhat.com: dclib 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) python-myghty 5: 0:1.0.2-2.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) valknut 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) luya_tfz AT thefinalzone.com: gdesklets 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) meme AT daughtersoftiresias.org: fortune-firefly 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) mpeters AT mac.com: firestarter 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) noa AT resare.com: vorbisgain 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) nomis80 AT nomis80.org: camstream 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) opencv 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) paul AT city-fan.org: perl-String-CRC32 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) petersen AT redhat.com: m17n-db 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) rpm AT timj.co.uk: php-pear-DB 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) ryo-dairiki AT users.sourceforge.net: scim-tomoe 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) thomas AT apestaart.org: flumotion 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) ---------------------------------------------------------------------- camstream: nomis80 AT nomis80.org 5: 0:0.26.3-10.fc5 (FE5) 6: 0:0.26.3-9.fc5 (FE6) dclib: lmacken AT redhat.com 5: 0:0.3.7-8.fc5 (FE5) 6: 0:0.3.7-7.fc6 (FE6) device-mapper: UNKNOWN OWNER (possibly Core package) 4: 0:1.02.07-2.0 (FC4-updates) 5: 0:1.02.02-3.2 (FC5) 6: 0:1.02.07-1.1 (FC6) dillo: andreas.bierfert AT lowlatency.de 4: 0:0.8.6-2.fc4 (FE4) 5: 0:0.8.6-1.fc5 (FE5) 6: 0:0.8.6-2.fc6 (FE6) firestarter: mpeters AT mac.com 5: 0:1.0.3-11.fc5 (FE5) 6: 0:1.0.3-10.fc6 (FE6) fish: liljencrantz AT gmail.com 5: 0:1.21.10-3.fc5 (FE5) 6: 0:1.21.10-2.fc6 (FE6) flumotion: thomas AT apestaart.org 5: 0:0.2.1-2.fc5 (FE5) 6: 0:0.2.0-1.fc5 (FE6) fortune-firefly: meme AT daughtersoftiresias.org 5: 0:2.1.1-2.fc5 (FE5) 6: 0:2.1.1-1.fc6 (FE6) ftp: UNKNOWN OWNER (possibly Core package) 5: 0:0.17-33.fc5 (FC5-updates) 6: 0:0.17-32.1.2.4 (FC6) fuse-encfs: lemenkov AT newmail.ru 5: 0:1.3.1-1.fc5 (FE5) 6: 0:1.3.0-1.fc6 (FE6) fuse-sshfs: lemenkov AT newmail.ru 5: 0:1.6-3.fc5 (FE5) 6: 0:1.6-2.fc6 (FE6) gdesklets: luya_tfz AT thefinalzone.com 4: 0:0.35.3-8.1.fc4 (FE4) 5: 0:0.35.3-8.fc5 (FE5) 6: 0:0.35.3-8.fc6 (FE6) istanbul: jspaleta AT gmail.com 5: 0:0.1.1-9.fc5 (FE5) 6: 0:0.1.1-9 (FE6) k3d: denis AT poolshark.org 5: 0:0.6.0.0-1.fc5.1 (FE5) 6: 0:0.5.16.0-3.fc6 (FE6) libpqxx: andreas.bierfert AT lowlatency.de 5: 0:2.6.7-1.fc5 (FE5) 6: 0:2.6.6-1.fc6 (FE6) lvm2: UNKNOWN OWNER (possibly Core package) 4: 0:2.02.06-1.0.fc4 (FC4-updates) 5: 0:2.02.01-1.2.1 (FC5) 6: 0:2.02.06-3 (FC6) m17n-db: petersen AT redhat.com 4: 0:1.3.3-1.fc4 (FE4) 5: 0:1.3.3-1 (FC5) 6: 0:1.3.3-17.fc6 (FC6) mozilla: UNKNOWN OWNER (possibly Core package) 3: 37:1.7.13-1.3.1.legacy (FL3-updates) 4: 37:1.7.13-1.1.fc4 (FC4-updates) 5: 37:1.7.13-1.1.fc5 (FC5-updates) opencv: nomis80 AT nomis80.org 5: 0:0.9.7-16.fc5 (FE5) 6: 0:0.9.7-15.fc5 (FE6) perl-String-CRC32: paul AT city-fan.org 4: 0:1.4-1.fc4 (FE4) 5: 0:1.4-1.FC5 (FC5-updates) 6: 0:1.4-2.fc6 (FC6) pgadmin3: ghenry AT suretecsystems.com 5: 0:1.4.3-2.fc5 (FE5) 6: 0:1.4.1-2.fc5 (FE6) php-pear-DB: rpm AT timj.co.uk 5: 0:1.7.6-6.fc5 (FE5) 6: 0:1.7.6-6 (FE6) python-myghty: lmacken AT redhat.com 5: 0:1.0.2-2.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) quagga: UNKNOWN OWNER (possibly Core package) 4: 0:0.98.6-1.fc4 (FC4-updates) 5: 0:0.98.6-1.FC5 (FC5-updates) 6: 0:0.98.6-2.1 (FC6) scim-tomoe: ryo-dairiki AT users.sourceforge.net 5: 0:0.2.0-6.fc5.1 (FE5) 6: 0:0.2.0-4.fc6 (FE6) seamonkey: kengert AT redhat.com 5: 0:1.0.4-0.5.1.fc5 (FE5) 6: 0:1.0.2-1.fc6 (FE6) serpentine: foolish AT guezz.net 5: 0:0.7-4.fc5 (FE5) 6: 0:0.7-3.fc6 (FE6) stratagus: lemenkov AT newmail.ru 5: 0:2.1-6.fc5 (FE5) 6: 0:2.1-5.fc6 (FE6) valknut: lmacken AT redhat.com 5: 0:0.3.7-9.fc5 (FE5) 6: 0:0.3.7-8.fc6 (FE6) vorbisgain: noa AT resare.com 5: 0:0.34-2.fc5 (FE5) 6: 0:0.34-1.fc6 (FE6) From buildsys at fedoraproject.org Wed Aug 23 00:40:50 2006 From: buildsys at fedoraproject.org (Fedora Extras repoclosure) Date: Wed, 23 Aug 2006 00:40:50 -0000 Subject: Summary - Broken dependencies in Fedora Extras - 2006-08-22 Message-ID: <20060823004050.17947.68897@extras64.linux.duke.edu> Summary of broken packages (by owner): ---------------------------------------------------------------------- andreas.bierfert AT lowlatency.de fluxbox - 0.9.15.1-1.fc3.i386 (138 days) fluxbox - 0.9.15.1-1.fc3.x86_64 (138 days) wine-core - 0.9.19-1.fc6.i386 bdpepple AT ameritech.net contact-lookup-applet - 0.14-3.fc6.i386 (15 days) contact-lookup-applet - 0.14-3.fc6.ppc (15 days) contact-lookup-applet - 0.14-3.fc6.x86_64 (15 days) byte AT fedoraproject.org gaim-guifications - 2.12-3.fc5.i386 (34 days) gaim-guifications - 2.12-3.fc5.ppc (34 days) gaim-guifications - 2.12-3.fc5.x86_64 (34 days) caillon AT redhat.com banshee - 0.10.11-1.fc6.i386 (3 days) banshee - 0.10.11-1.fc6.ppc (3 days) banshee - 0.10.11-1.fc6.x86_64 (3 days) foolish AT guezz.net muine - 0.8.5-1.fc6.i386 (3 days) muine - 0.8.5-1.fc6.ppc (3 days) muine - 0.8.5-1.fc6.x86_64 (3 days) gauret AT free.fr amarok - 1.4.1-3.fc6.i386 (26 days) amarok - 1.4.1-3.fc6.ppc (26 days) showimg-pgsql - 0.9.5-7.fc4.i386 (15 days) showimg-pgsql - 0.9.5-7.fc4.ppc (15 days) showimg-pgsql - 0.9.5-7.fc4.x86_64 (15 days) showimg-pgsql - 0.9.5-7.fc5.i386 (15 days) showimg-pgsql - 0.9.5-7.fc5.ppc (15 days) showimg-pgsql - 0.9.5-7.fc5.x86_64 (15 days) green AT redhat.com azureus - 2.4.0.3-0.20060328cvs_5.fc6.ppc (27 days) jogl - 1.1.1-14.fc5.ppc (30 days) ivazquez AT ivazquez.net gnome-applet-music - 0.9.0-1.fc6.i386 (34 days) gnome-applet-music - 0.9.0-1.fc6.ppc (34 days) gnome-applet-music - 0.9.0-1.fc6.x86_64 (34 days) nautilus-search-tool - 0.2-1.fc5.i386 (34 days) nautilus-search-tool - 0.2-1.fc5.ppc (34 days) nautilus-search-tool - 0.2-1.fc5.x86_64 (34 days) mpeters AT mac.com gfontview - 0.5.0-5.fc5.i386 (34 days) gfontview - 0.5.0-5.fc5.ppc (34 days) gfontview - 0.5.0-5.fc5.x86_64 (34 days) gtkhtml36 - 3.6.2-5.fc6.i386 (34 days) gtkhtml36 - 3.6.2-5.fc6.ppc (34 days) gtkhtml36 - 3.6.2-5.fc6.x86_64 (34 days) libvisual-plugins - 0.2.0-3.fc5.i386 (34 days) libvisual-plugins - 0.2.0-3.fc5.i386 (34 days) libvisual-plugins - 0.2.0-3.fc5.ppc (34 days) libvisual-plugins - 0.2.0-3.fc5.ppc (34 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (34 days) libvisual-plugins - 0.2.0-3.fc5.x86_64 (34 days) oliver AT linux-kernel.at syck-php - 0.55-7.fc5.i386 (97 days) syck-php - 0.55-7.fc5.i386 (97 days) syck-php - 0.55-7.fc5.ppc (97 days) syck-php - 0.55-7.fc5.ppc (97 days) syck-php - 0.55-7.fc5.x86_64 (97 days) syck-php - 0.55-7.fc5.x86_64 (97 days) paul AT all-the-johnsons.co.uk gtksourceview-sharp - 2.0-15.fc6.i386 (3 days) gtksourceview-sharp - 2.0-15.fc6.ppc (3 days) gtksourceview-sharp - 2.0-15.fc6.x86_64 (3 days) rolandd AT cisco.com libibverbs - 1.0.3-1.fc6.i386 (34 days) libibverbs - 1.0.3-1.fc6.ppc (34 days) libibverbs - 1.0.3-1.fc6.x86_64 (34 days) libibverbs-utils - 1.0.3-1.fc6.i386 (34 days) libibverbs-utils - 1.0.3-1.fc6.ppc (34 days) libibverbs-utils - 1.0.3-1.fc6.x86_64 (34 days) tcallawa AT redhat.com gambas-runtime - 1.0.14-2.fc5.i386 (14 days) thomas AT apestaart.org directfb - 0.9.24-5.fc5.i386 (34 days) directfb - 0.9.24-5.fc5.ppc (34 days) directfb - 0.9.24-5.fc5.x86_64 (34 days) Broken packages in fedora-extras-5-i386: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.i386 requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-5-x86_64: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) showimg-pgsql-0.9.5-7.fc5.x86_64 requires libpqxx-2.6.6.so()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 Broken packages in fedora-extras-5-ppc: ---------------------------------------------------------------------- libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 showimg-pgsql-0.9.5-7.fc5.ppc requires libpqxx-2.6.6.so syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 Broken packages in fedora-extras-4-i386: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.i386 requires libpqxx-2.6.6.so Broken packages in fedora-extras-4-x86_64: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.x86_64 requires libpqxx-2.6.6.so()(64bit) Broken packages in fedora-extras-4-ppc: ---------------------------------------------------------------------- showimg-pgsql-0.9.5-7.fc4.ppc requires libpqxx-2.6.6.so Broken packages in fedora-extras-3-i386: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.i386 requires pyxdg Broken packages in fedora-extras-3-x86_64: ---------------------------------------------------------------------- fluxbox-0.9.15.1-1.fc3.x86_64 requires pyxdg Broken packages in fedora-extras-development-i386: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.i386 requires HelixPlayer banshee-0.10.11-1.fc6.i386 requires mono(gconf-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(glade-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(pango-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gnome-vfs-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(glib-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gtk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gnome-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.i386 requires mono(gdk-sharp) = 0:2.8.0.0 contact-lookup-applet-0.14-3.fc6.i386 requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.i386 requires libsysfs.so.1 gaim-guifications-2.12-3.fc5.i386 requires gaim < 1:2 gambas-runtime-1.0.14-2.fc5.i386 requires libgettextlib-0.14.5.so gfontview-0.5.0-5.fc5.i386 requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.i386 requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.i386 requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.i386 requires libgailutil.so.17 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(gnome-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(gtk-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(glib-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.i386 requires mono(gdk-sharp) = 0:2.8.0.0 libibverbs-1.0.3-1.fc6.i386 requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.i386 requires libsysfs.so.1 libvisual-plugins-0.2.0-3.fc5.i386 requires libvisual.so.0 muine-0.8.5-1.fc6.i386 requires mono(glib-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.i386 requires mono(gtk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.i386 requires mono(gdk-sharp) = 0:2.8.0.0 nautilus-search-tool-0.2-1.fc5.i386 requires libgailutil.so.17 syck-php-0.55-7.fc5.i386 requires php = 0:5.1.2 Broken packages in fedora-extras-development-x86_64: ---------------------------------------------------------------------- banshee-0.10.11-1.fc6.x86_64 requires mono(gconf-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(glade-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gnome-vfs-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gtk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gdk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(gnome-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(pango-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.x86_64 requires mono(glib-sharp) = 0:2.8.0.0 contact-lookup-applet-0.14-3.fc6.x86_64 requires libebook-1.2.so.5()(64bit) directfb-0.9.24-5.fc5.x86_64 requires libsysfs.so.1()(64bit) gaim-guifications-2.12-3.fc5.x86_64 requires gaim < 1:2 gfontview-0.5.0-5.fc5.x86_64 requires libttf.so.2()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libgailutil.so.17()(64bit) gnome-applet-music-0.9.0-1.fc6.x86_64 requires libdbus-1.so.2()(64bit) gtkhtml36-3.6.2-5.fc6.x86_64 requires libgailutil.so.17()(64bit) gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(gnome-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(gtk-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(glib-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.x86_64 requires mono(gdk-sharp) = 0:2.8.0.0 libibverbs-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libibverbs-utils-1.0.3-1.fc6.x86_64 requires libsysfs.so.1()(64bit) libvisual-plugins-0.2.0-3.fc5.x86_64 requires libvisual.so.0()(64bit) muine-0.8.5-1.fc6.x86_64 requires mono(gdk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.x86_64 requires mono(gtk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.x86_64 requires mono(glib-sharp) = 0:2.8.0.0 nautilus-search-tool-0.2-1.fc5.x86_64 requires libgailutil.so.17()(64bit) syck-php-0.55-7.fc5.x86_64 requires php = 0:5.1.2 wine-core-0.9.19-1.fc6.i386 requires libglut.so.3 Broken packages in fedora-extras-development-ppc: ---------------------------------------------------------------------- amarok-1.4.1-3.fc6.ppc requires HelixPlayer azureus-2.4.0.3-0.20060328cvs_5.fc6.ppc requires libgcj.so.7 banshee-0.10.11-1.fc6.ppc requires mono(gconf-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(glade-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(pango-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gnome-vfs-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(glib-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gtk-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gnome-sharp) = 0:2.8.0.0 banshee-0.10.11-1.fc6.ppc requires mono(gdk-sharp) = 0:2.8.0.0 contact-lookup-applet-0.14-3.fc6.ppc requires libebook-1.2.so.5 directfb-0.9.24-5.fc5.ppc requires libsysfs.so.1 gaim-guifications-2.12-3.fc5.ppc requires gaim < 1:2 gfontview-0.5.0-5.fc5.ppc requires libttf.so.2 gnome-applet-music-0.9.0-1.fc6.ppc requires libgailutil.so.17 gnome-applet-music-0.9.0-1.fc6.ppc requires libdbus-1.so.2 gtkhtml36-3.6.2-5.fc6.ppc requires libgailutil.so.17 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(gnome-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(gtk-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(glib-sharp) = 0:2.8.0.0 gtksourceview-sharp-2.0-15.fc6.ppc requires mono(gdk-sharp) = 0:2.8.0.0 jogl-1.1.1-14.fc5.ppc requires libgcj.so.7 libibverbs-1.0.3-1.fc6.ppc requires libsysfs.so.1 libibverbs-utils-1.0.3-1.fc6.ppc requires libsysfs.so.1 libvisual-plugins-0.2.0-3.fc5.ppc requires libvisual.so.0 muine-0.8.5-1.fc6.ppc requires mono(glib-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.ppc requires mono(gtk-sharp) = 0:2.8.0.0 muine-0.8.5-1.fc6.ppc requires mono(gdk-sharp) = 0:2.8.0.0 nautilus-search-tool-0.2-1.fc5.ppc requires libgailutil.so.17 syck-php-0.55-7.fc5.ppc requires php = 0:5.1.2 ====================================================================== New report for: andreas.bierfert AT lowlatency.de package: wine-core - 0.9.19-1.fc6.i386 from fedora-extras-development-x86_64 unresolved deps: libglut.so.3 ====================================================================== New report for: tcallawa AT redhat.com package: gambas-runtime - 1.0.14-2.fc5.i386 from fedora-extras-development-i386 unresolved deps: libgettextlib-0.14.5.so From mattdm at mattdm.org Wed Aug 23 01:08:31 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Tue, 22 Aug 2006 21:08:31 -0400 Subject: SPF failures nuke fedora-extras* msgs from redhat.com In-Reply-To: <20060822233346.GH5028@neu.nirvana> References: <1156271448.29825.29.camel@pmac.infradead.org> <20060822193853.GA18107@jadzia.bu.edu> <20060822233346.GH5028@neu.nirvana> Message-ID: <20060823010831.GA32032@jadzia.bu.edu> On Wed, Aug 23, 2006 at 01:33:46AM +0200, Axel Thimm wrote: > > I disagree with you on SPF in many regards, but this part I totally agree > > with. Having a package behave totally differently depending simply on the > > *presence* of a perl module is bad behavior. > That's true of a lot of other (optional) perl modules in spamassassin. Oh, I know. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From opensource at till.name Wed Aug 23 08:42:06 2006 From: opensource at till.name (Till Maas) Date: Wed, 23 Aug 2006 10:42:06 +0200 Subject: Contacting the Fedora Account System's management team In-Reply-To: <200608230012.01288.opensource@till.name> References: <200608201358.40043.opensource@till.name> <200608202259.58934.nman64@n-man.com> <200608230012.01288.opensource@till.name> Message-ID: <200608231042.06670.opensource@till.name> On Wednesday 23 August 2006 00:11, Till Maas wrote: > Actually I added the needed UID (opensource at till.name) last friday and made > it even primary. Nevertheless, the same error still occurs, see here: > http://pgpkeys.pca.dfn.de/pks/lookup?op=index&fingerprint=on&search=opensou >rce%40till.name Just in case someone wants to know how to fix this problem: I needed to update the key on hkp://pgp.mit.edu to solve my problem. Greetings, Till -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bugzilla at redhat.com Wed Aug 23 10:56:08 2006 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 23 Aug 2006 06:56:08 -0400 Subject: [Bug 198558] libvisual-plugins does not update do to a bad rpm resulting in missing deps when doing yum update/install In-Reply-To: Message-ID: <200608231056.k7NAu85n023678@bugzilla.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: libvisual-plugins does not update do to a bad rpm resulting in missing deps when doing yum update/install https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198558 bugs.michael at gmx.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fedora-extras- | |list at redhat.com ------- Additional Comments From bugs.michael at gmx.net 2006-08-23 06:46 EST ------- Why is this thing in FE5 broken for 34 days? I really believe we need a working policy, so that others can step in and fix such crap. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. From bugzilla at redhat.com Wed Aug 23 11:07:00 2006 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 23 Aug 2006 07:07:00 -0400 Subject: [Bug 198558] libvisual-plugins does not update do to a bad rpm resulting in missing deps when doing yum update/install In-Reply-To: Message-ID: <200608231107.k7NB70xD024244@bugzilla.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: libvisual-plugins does not update do to a bad rpm resulting in missing deps when doing yum update/install https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198558 bugs.michael at gmx.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC|fedora-extras- | |list at redhat.com | -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. From j.w.r.degoede at hhs.nl Wed Aug 23 11:38:10 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Wed, 23 Aug 2006 13:38:10 +0200 Subject: Autodownloader for free(gratis) legal but not redistributable game content Message-ID: <44EC3E22.5020403@hhs.nl> Hi all, I would like to package some games which consists of a free (as in freedom /OSS) game-engine (either set free by the original creators or a free engine reimplementation) which require content which has only be set free to a certain degree. Example: xu4 - Ultima IV Recreated, which requires the datafiles from the original Ultima IV. These datafiles have once been distributed on a cover CD of a magazine and after this the copyright holders have given permission to members of the ultima fan-network known as the dragons to make these files freely available for download from their websites. Its clear that since the permission was only given to the dragon fan network, that we (Fedora) don't have permission to distribute these files. Thus I would like to create an (nice userfriendly GUI) autodownloader which can be used by games like this to download the nescesarry files, this should work something like this: -user tries to start the game for the first time -a dialog is shown to the user explaining that this game needs some additional files and that if the user agrees a connection to the internet will be made to download these files so that the game can be run. -If the user agrees a dialog is shown with the license of these files, -If the user accepts the license, the files get downloaded and dropped into the proper place. -the game gets started normally On subsequent runs the game will be started immediatly. So my question basicly is what do others think about this? Does this for example break the 100% FOSS goal of Fedora, IMHO it doesn't but its a bit murky. Thanks & Regards, Hans From notting at redhat.com Wed Aug 23 12:34:37 2006 From: notting at redhat.com (Bill Nottingham) Date: Wed, 23 Aug 2006 08:34:37 -0400 Subject: Autodownloader for free(gratis) legal but not redistributable game content In-Reply-To: <44EC3E22.5020403@hhs.nl> References: <44EC3E22.5020403@hhs.nl> Message-ID: <20060823123437.GB15578@nostromo.devel.redhat.com> Hans de Goede (j.w.r.degoede at hhs.nl) said: > So my question basicly is what do others think about this? Does this for > example break the 100% FOSS goal of Fedora, IMHO it doesn't but its a > bit murky. Well, we don't patch the plugin autofinder out of firefox. However, firefox is generally useful outside of any plugins - I'm not sure that these game engines are. Bill From j.w.r.degoede at hhs.nl Wed Aug 23 14:39:23 2006 From: j.w.r.degoede at hhs.nl (Hans de Goede) Date: Wed, 23 Aug 2006 16:39:23 +0200 Subject: Autodownloader for free(gratis) legal but not redistributable game content In-Reply-To: <20060823123437.GB15578@nostromo.devel.redhat.com> References: <44EC3E22.5020403@hhs.nl> <20060823123437.GB15578@nostromo.devel.redhat.com> Message-ID: <44EC689B.8060204@hhs.nl> Bill Nottingham wrote: > Hans de Goede (j.w.r.degoede at hhs.nl) said: >> So my question basicly is what do others think about this? Does this for >> example break the 100% FOSS goal of Fedora, IMHO it doesn't but its a >> bit murky. > > Well, we don't patch the plugin autofinder out of firefox. True, good point. > However, > firefox is generally useful outside of any plugins - I'm not sure that > these game engines are. > Also true, but so is for example prboom / vavoom (with freedoom), still it would be nice to add a desktop shortcut called Heretic Shareware which would download and install the heretic shareware datafiles (if the user agrees) and then run vavoom with those to give the user heretic. Regards, Hans From paul at all-the-johnsons.co.uk Wed Aug 23 21:24:31 2006 From: paul at all-the-johnsons.co.uk (Paul F. Johnson) Date: Wed, 23 Aug 2006 21:24:31 +0000 Subject: Amaya Message-ID: <20060823212431.M29432@all-the-johnsons.co.uk> Hi, For those who are getting slightly frustrated over the lack of movement on a working version of Amaya 9.51 for FE (both in FC5 and FC6), I've been informed from upstream that there will be a point release next week and a full update in September. With luck, the point release with have the majority of fixes in which will mean that both an x86 and x86_64 version can be released. My intention is to release the point version for FC-devel (6 test 2) and the full version for both FC5 and FC6. Amaya 8.5 is no longer being developed (from what I can gather) and I have no intention in keeping the package up to date, similarly, I don't have the ability to test code on an FC4 box, so will not maintain Amaya for anything under FC5. Hope that sheds some light on things. BTW : The next amaya is wx based and not gtk based. Upstream are depricating the gtk version (from what I can gather only the wx version is being developed now). -- Get your free @ukpost.com account now http://www.ukpost.com/ From chris.stone at gmail.com Wed Aug 23 21:44:23 2006 From: chris.stone at gmail.com (Christopher Stone) Date: Wed, 23 Aug 2006 14:44:23 -0700 Subject: Building i386 RPMs with mock on x86_64 Message-ID: I am trying to build an i386 rpm under mock with Fedora 5 x86_64 and it is not working because when mock pulls in the denedencies, it is getting x86_64 versions of the packages. My fedora-5-i386-core.cfg file is the default and is unmodified. Does anyone have any ideas on why this is happening, and how to fix it? From skvidal at linux.duke.edu Wed Aug 23 21:48:18 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Wed, 23 Aug 2006 17:48:18 -0400 Subject: Building i386 RPMs with mock on x86_64 In-Reply-To: References: Message-ID: <1156369699.19660.5.camel@cutter> On Wed, 2006-08-23 at 14:44 -0700, Christopher Stone wrote: > I am trying to build an i386 rpm under mock with Fedora 5 x86_64 and > it is not working because when mock pulls in the denedencies, it is > getting x86_64 versions of the packages. My fedora-5-i386-core.cfg > file is the default and is unmodified. > > Does anyone have any ideas on why this is happening, and how to fix it? 1. mv /etc/rpm/platform /etc/rpm/not-platform 2. setarch i386 mock ...... -sv From opensource at till.name Wed Aug 23 23:16:55 2006 From: opensource at till.name (Till Maas) Date: Thu, 24 Aug 2006 01:16:55 +0200 Subject: Contacting Ignacio Vazquez-Abrams - Maintainer of linphone Message-ID: <200608240117.02089.opensource@till.name> Hiyas, I just want to ask if someone knows how to contact Ignacio Vazquez-Abrams, the maintainer of linphone. I noticed that fedora extras includes only an old version of linphone and openend a bug report on August 2nd: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201017 I received no response yet. I looked into some of his other packages (he owns 53) and noticed that at least 19 of them are also outdated, with at least one missing security fixes: notecase numpy alltray OpenEXR ortp ecore edje eet embryo evas ghasher gpredict hamlib moodle (misses security fixes) pyparsing python-nose python-sqlobject (not sure) soundconverter sqlite2 One package has been updated by someone else: deskbar-applet He is not listed on http://fedoraproject.org/wiki/Vacation Last entry on http://www.ivazquez.net/ is from May, 21st. So if someone knows how to contact him, please do. Otherwise I will proceed as described in http://fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers and ask officially for other ways to contact him in five days. Regards, Till -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From opensource at till.name Wed Aug 23 23:31:29 2006 From: opensource at till.name (Till Maas) Date: Thu, 24 Aug 2006 01:31:29 +0200 Subject: Contacting Ignacio Vazquez-Abrams - Maintainer of linphone In-Reply-To: <200608240117.02089.opensource@till.name> References: <200608240117.02089.opensource@till.name> Message-ID: <200608240131.29674.opensource@till.name> On Thursday 24 August 2006 01:16, Till Maas wrote: > moodle (misses security fixes) I filled a bug report for this: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203844 Regards, Till -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From michael at knox.net.nz Wed Aug 23 23:39:49 2006 From: michael at knox.net.nz (Michael J. Knox) Date: Thu, 24 Aug 2006 11:39:49 +1200 (NZST) Subject: Contacting Ignacio Vazquez-Abrams - Maintainer of linphone In-Reply-To: <200608240131.29674.opensource@till.name> References: <200608240117.02089.opensource@till.name> <200608240131.29674.opensource@till.name> Message-ID: <60327.203.118.135.21.1156376389.squirrel@www.knox.net.nz> Till Maas wrote: > On Thursday 24 August 2006 01:16, Till Maas wrote: >> moodle (misses security fixes) > > I filled a bug report for this: > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203844 Ignacio has been missing for sometime. The AWOL guide lines is a good place to start. I think some people have picked up on some of his packages already, but the AWOL process should be used here. Thanks! Michael From opensource at till.name Thu Aug 24 00:07:42 2006 From: opensource at till.name (Till Maas) Date: Thu, 24 Aug 2006 02:07:42 +0200 Subject: extend AWOL/MIA Maintainer Policy to all packages from an maintainer Message-ID: <200608240207.55409.opensource@till.name> Hiyas, I just realized that the actual AWOL/MIA Maintainer Policy is in my opionion missing a major detail. It is only about one package that is neglected but I guess in reality an AWOL/MIA maintainer will neglect all of his packages. For this reason the policy should target how to proceed with all packages of the maintainer, e.g. checking how many issues are open and whether or not they are up-to-date. Also the Policy does not tell what to do if noone wants to adopt a package from an missing maintainer. Regards, Till -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From opensource at till.name Thu Aug 24 00:17:10 2006 From: opensource at till.name (Till Maas) Date: Thu, 24 Aug 2006 02:17:10 +0200 Subject: What is /cvs/extras/devel for? Message-ID: <200608240217.10851.opensource@till.name> Hiyas, I am wondering why this is not a FAQ (at least I cannot find it in the wiki... ) - What is /cvs/extras/devel for? Is the structure of the fedora cvs repository explained anywhere? Regards, Till -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From fedora at theholbrooks.org Thu Aug 24 03:37:53 2006 From: fedora at theholbrooks.org (Brandon Holbrook) Date: Wed, 23 Aug 2006 22:37:53 -0500 Subject: Ignacio / AWOL Policy (Was: Contacting Ignacio ...) In-Reply-To: <60327.203.118.135.21.1156376389.squirrel@www.knox.net.nz> References: <200608240117.02089.opensource@till.name> <200608240131.29674.opensource@till.name> <60327.203.118.135.21.1156376389.squirrel@www.knox.net.nz> Message-ID: <44ED1F11.9010202@theholbrooks.org> Has anybody had any contact with Igzacio since this was first brought up in the FESCo meeting on the 19th? Last we heard Warren was still trying to reach him by phone. If so, what's the news? If not, will somebody (preferably from FESCo) lay down a timeline for when the AWOL process began and when the next set of deadlines will fall. Do we start counting from when FESCo approved to start the AWOL process? Does this particular instance warrant an expedited process since his absence started in May? Are we as current maintainers allowed (as suggested and I mistakenly acted upon for php-json) to respond to his open bugzilla reports, or does all our red tape impede progress? I agree with Till that the AWOL policy should be amended to include the case when a Maintainer is AWOL from several (or all) of his packages, that all those packages are considered orphans up for adoption, and possibly removal further down the road if nobody is interested in taking them. The current AWOL policy assumes there is always somebody ready and waiting to adopt the neglected package. I also think (as hinted above) that an explicit provision should be made when other contributors can intercede and fix open bug reports (halfway through step 2?), especially for security-related bugs (maybe even a separate, sooner time for this). 3 weeks + 3 days +