Re: Orphaning packages
Hi, On 21.8.2009 22:41, Aurelien Bompard wrote: - python-dialog -- Python interface to the Unix dialog utility I've taken this one, if you want I can also grab the F10/F11 branches. Regards, Milos -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
Aurelien Bompard wrote: > - gwenview -- Simple image viewer for KDE This one is obsolete, gwenview is part of kdegraphics these days. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Broken dependencies in Fedora 11 - 2009-08-20
Michael Schwendt wrote: > Pitfalls remain nevertheless. F10 ktorrent got marked stable with the > KDE4 buildroot override packages still sitting in updates-testing. Yeah, indeed, the maintainer screwed up big time there. :-/ He didn't talk to us at all before pushing that ktorrent update. :-( He used to be on #fedora-kde from time to time, but not anymore. He apparently didn't read our announcement about the KDE 4.3.0 buildroot override on the mailing list either. BTW, the update notes for that update are also completely worthless, when upstream even summarized the changes nicely in their newsitem (so there's really no excuse for not pasting them in). Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
Hi Aurelien, Aurelien Bompard wrote: > I'm orphaning a few packages I'm not using anymore, feel free to take over: > - xbindkeys -- Binds keys or mouse buttons to shell commands under X. I took this one. If you like I can also take care of F11 and F10. So if you orphan them, I'll take ownership of these, too. Best regards, Christian -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Upcoming scheduled tasks
Name Start End Stage & Sync Alpha to Mirrors Thu 2009-08-20 Tue 2009-08-25 Alpha Export Control Reporting Fri 2009-08-21 Fri 2009-08-21 Allow Pre-branch Fedora 13 Tue 2009-08-25 Tue 2009-08-25 Alpha Public Availability Tue 2009-08-25 Tue 2009-08-25 Alpha Testing Tue 2009-08-25 Tue 2009-09-29 Compose Snap #1Wed 2009-09-02 Wed 2009-09-02 Snapshot 1 Wed 2009-09-02 Fri 2009-09-04 Stage & Sync Snap #1 Thu 2009-09-03 Fri 2009-09-04 -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
* Aurelien Bompard [21/08/2009 22:59] : > > - perl-Unicode-Map -- Perl module for mapping charsets from and to utf16 > unicode > - perl-Unicode-Map8 -- Mapping table between 8-bit chars and Unicode for > Perl > - perl-Unicode-MapUTF8 -- Conversions to and from arbitrary character sets > and UTF8 > - perl-Unicode-String -- Perl modules to handle various Unicode issues I've taken ownership of these four. Emmanuel -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
On Friday 21 August 2009 01:41:09 pm Aurelien Bompard wrote: > Whoops, I forgot a few more : > > - libifp -- A general-purpose library-driver for iRiver's iFP portable > audio players I have a package or two that uses this, I'll take it. Regards, -- Conrad Meyer -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Add Moblin Desktop group to comps
> Hi All, > > I would like to add a group for the Moblin Desktop. My proposed patch > is below and feedback is welcome. This is updated with the current components that are in rawhide. All the other packages should be pulled in by deps. Cheers, Peter --- comps-f12.xml.in.orig 2009-08-20 17:10:23.0 +0100 +++ comps-f12.xml.in2009-08-21 23:11:19.0 +0100 @@ -4235,6 +4235,24 @@ +moblin-desktop +<_name>Moblin Desktop Environment +<_description>Moblin is a desktop environment for NetBook/NetTop/MID devices. +false +true + + bisho + bognor-regis + moblin-cursor-theme + moblin-gtk-engine + moblin-icon-theme + moblin-panel-applications + moblin-session + moblin-sound-theme + anjal + + + mongolian-support <_name>Mongolian Support <_description/> @@ -6237,6 +6255,7 @@ gnome-desktop kde-desktop lxde-desktop + moblin-desktop sugar-desktop window-managers xfce-desktop -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > - qca2 -- Qt Cryptographic Architecture I'll take this one - --Ben -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqPE+IACgkQiPi+MRHG3qR5BACdF9QP6V0LSJPnDtLklv3FSUIG roUAoL8FVAQGEyZtbMQtPrjLLRsXpgM4 =Smit -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
On Friday 21 August 2009 04:34:24 pm Aurelien Bompard wrote: > - ulogd -- The userspace logging daemon for netfilter I'm taking this one. Thanks, -Steve -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
Grabbed tiger and agave as well. Vivek -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
Hi Aurélien, Picked up stow. If you want I can manage the Fedora-10 and 11 branches as well. In case you orphan them, I will pick them up as well. Thanks and Regards, Vivek -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
Hi, I would like to take up pdftohtml. I could only see the devel branch in pkgdb without the Fedora 10 and 11 branch. I will be taking up ownership of the devel branch. Thanks and Regards, Vivek -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
> You might not have gotten around to it, but it appears you only > orphaned the devel branch of apachetop, wasn't sure if you want to > continue to maintain the stable branches but no longer beyond that or > completely orphan? I'm not sure what the right way is. If you want to maintain it, I'll be happy to orphan F10 and F11 too, I just thought that if no-one showed up I could handle maintenance til F12. I'll orphan them right now. Aurélien -- http://aurelien.bompard.org Jabber : abomp...@jabber.fr "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
On Fri, 21 Aug 2009 22:34:24 +0200, Aurelien wrote: > I'm orphaning a few packages I'm not using anymore, feel free to take over: > > - taglib -- Audio Meta-Data Library I'll sign up for that one... -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
You might not have gotten around to it, but it appears you only orphaned the devel branch of apachetop, wasn't sure if you want to continue to maintain the stable branches but no longer beyond that or completely orphan? -Adam -- http://maxamillion.googlepages.com - () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
On Fri, Aug 21, 2009 at 3:34 PM, Aurelien Bompard wrote: > I'm orphaning a few packages I'm not using anymore, feel free to take over: > > - apachetop -- A top-like display of Apache log I'd like to take this one, I use it quite often. I'll be taking ownership in Fedora pkgdb here in a moment. -Adam -- http://maxamillion.googlepages.com - () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
Whoops, I forgot a few more : - libifp -- A general-purpose library-driver for iRiver's iFP portable audio players - libkexif -- Allow Kipi plugins to extract EXIF information - libkipi -- Common plugin infrastructure for KDE image applications - libvisual & libvisual-plugins -- Abstraction library for audio visualisation plugins - python-dialog -- Python interface to the Unix dialog utility Thanks Aurélien -- http://aurelien.bompard.org Jabber : abomp...@jabber.fr "Everyone thinks of changing the world, but no one thinks of changing himself." -- Tolstoï -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: popcorn sound with kernel 2.6.29.6
On Fri, 2009-08-21 at 21:41 +0200, Chitlesh GOORAH wrote: > I am experiencing some random popcorn sound while playing mp3 and > while assisting flash based webinars with the kernel-2.6.29.6. Can you reproduce if for example running "pasuspender totem " ? Jon. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Orphaning packages
I'm orphaning a few packages I'm not using anymore, feel free to take over: - agave -- Generate a variety of colorschemes from a single starting color - apachetop -- A top-like display of Apache logs - basket -- Taking care of your ideas - blobby -- Volley-ball game - cryptopp -- Public domain C++ class library of cryptographic schemes - glest & glest-data -- 3D real time strategy game - gwenview -- Simple image viewer for KDE - mhonarc -- Perl mail-to-HTML converter - moodbar -- Identifies the "mood" of your music files - pdftohtml -- PDF to HTML converter - perl-Jcode -- Perl extension interface for converting Japanese text - perl-Unicode-Map -- Perl module for mapping charsets from and to utf16 unicode - perl-Unicode-Map8 -- Mapping table between 8-bit chars and Unicode for Perl - perl-Unicode-MapUTF8 -- Conversions to and from arbitrary character sets and UTF8 - perl-Unicode-String -- Perl modules to handle various Unicode issues - php-adodb -- Active Data Objects Data Base - qca -- Qt Cryptographic Architecture - qca-gnupg -- GnuPG plugin for the Qt Cryptographic Architecture v2 - qca-ossl -- OpenSSL plugin for the Qt Cryptographic Architecture v2 - qca-tls -- TLS plugin for the Qt Cryptographic Architecture - qca2 -- Qt Cryptographic Architecture - showimg -- Feature-rich image viewer for KDE - stow -- Manage the installation of software packages from source - taglib -- Audio Meta-Data Library - tetex-unicode -- Unicode support for LaTeX - tiger -- Security auditing on UNIX systems - ulogd -- The userspace logging daemon for netfilter - unrtf -- RTF to other formats converter - wv -- MSWord 6/7/8/9 binary file format to HTML converter - xbindkeys -- Binds keys or mouse buttons to shell commands under X. - xine-lib -- A multimedia engine - xlhtml -- Excel 95/97 and PowerPoint to HTML converter Thanks Aurélien -- http://aurelien.bompard.org Jabber : abomp...@jabber.fr "We act as though comfort and luxury were the chief requirements of life, when all that we need to make us happy is something to be enthusiastic about." -- Albert Einstein -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Emacs packaging guidelines fix for XEmacs
On Fri, Aug 21, 2009 at 2:25 PM, Jason L Tibbitts III wrote: > Certainly the text not agreeing with the templates is something we need > to fix. I've changed four references of xemacs/site-packages to > xemacs/site-packages/lisp in two specfile templates. Please > double-check that everything is correct. Yes, it looks correct now. Thanks, Jason! -- Jerry James http://www.jamezone.org/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Emacs packaging guidelines fix for XEmacs
Certainly the text not agreeing with the templates is something we need to fix. I've changed four references of xemacs/site-packages to xemacs/site-packages/lisp in two specfile templates. Please double-check that everything is correct. - J< -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Emacs packaging guidelines fix for XEmacs
On Fri, Aug 21, 2009 at 1:58 PM, Jerry James wrote: > that it would be taken care of. Ah, perhaps it was. Item #7 in the > Executive Guidelines on the wiki page gets it right. Now that I look closer, the text gets it right everywhere. It's just the spec file samples that get it wrong. So forget the global search and replace. Could someone just do the search and replace on the spec file samples? Thanks, -- Jerry James http://www.jamezone.org/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Emacs packaging guidelines fix for XEmacs
On Fri, Aug 21, 2009 at 1:46 PM, Jason L Tibbitts III wrote: > Could we have some explanation of why these changes are needed? Have > these directories changed location recently? Are there versions of > Fedora where these changes will not apply? What about RHEL/EPEL? No, the XEmacs locations have needed the "lisp" part for a long time. See the very bottom of this page, and notice the copyright dates: http://www.xemacs.org/Documentation/packageGuide.html My suspicion is that whoever wrote the wiki page did a copy&paste from the Emacs version and overlooked the "lisp" portion of the path. I actually noted this once before and thought from the response I got that it would be taken care of. Ah, perhaps it was. Item #7 in the Executive Guidelines on the wiki page gets it right. This change is appropriate for every distribution with a post 2000 release of XEmacs. Prior to that, it used site-lisp like Emacs anyway Thanks, -- Jerry James http://www.jamezone.org/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Emacs packaging guidelines fix for XEmacs
> "JJ" == Jerry James writes: JJ> Would someone who has editing rights to JJ> https://fedoraproject.org/wiki/Packaging:Emacs please do a global JJ> search and replace: Could we have some explanation of why these changes are needed? Have these directories changed location recently? Are there versions of Fedora where these changes will not apply? What about RHEL/EPEL? - J< -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
popcorn sound with kernel 2.6.29.6
Hello there, I am experiencing some random popcorn sound while playing mp3 and while assisting flash based webinars with the kernel-2.6.29.6. However I am not experiencing this with kernel-2.6.29.5. By random I mean, I don't get this popcorn sound everytime I play the same mp3 and at the same timeframe. This popcorn sound seems to attenuate the gain of the music and at the same time it speeds the play. Has anyone encountered this issue with kernel-2.6.29.6 or any means to troubleshoot it ? I was hoping to see this fix in the latest fedora release but the problem is still there. regards, Chitlesh -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Emacs packaging guidelines fix for XEmacs
Would someone who has editing rights to
https://fedoraproject.org/wiki/Packaging:Emacs please do a global
search and replace:
%{_datadir}/xemacs/site-packages to %{_datadir}/xemacs/site-packages/lisp
In particular, be sure that
%{_datadir}/xemacs/site-packages/site-start.d gets changed to
%{_datadir}/xemacs/site-packages/lisp/site-start.d.
Thanks!
--
Jerry "My other hobby is XEmacs" James
http://www.jamezone.org/
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Broken dependencies in Fedora 11 - 2009-08-20
On Fri, 21 Aug 2009 20:13:34 +0200, Kevin wrote: > drago01 wrote: > > Sorry but the fail here is 100% on bodhi's side , why does a single > > package obsolete a complete group update? > > That is just broken, and this example clearly showed it. > > It's broken (we've had some fun with that with the KDE grouped updates too, > we learned to be careful about what we push when), Pitfalls remain nevertheless. F10 ktorrent got marked stable with the KDE4 buildroot override packages still sitting in updates-testing. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Broken dependencies in Fedora 11 - 2009-08-20
>>> Sorry but the fail here is 100% on bodhi's side , why does a single >>> package obsolete a complete group update? >>> That is just broken, and this example clearly showed it. >> >> It's broken (we've had some fun with that with the KDE grouped updates too, >> we learned to be careful about what we push when), but a maintainer should >> know how to use our tools, which includes being aware of their limitations. >> Double-checking things both before and after filing an update (e.g. checking >> https://admin.fedoraproject.org/updates/thepackageyoureabouttopushanupdatefor >> before filing the new update request) definitely can't hurt (I always do >> that), and it will help avoiding issues you don't even know about, or at >> least catching them earlier than 2 months after the fact (as happened here). > > Sure if you know about a bug/limitation you can try to avoid it, but > as Josh said you can't expect that every maintainer knows about all > (undocumented) bugs/limitations. Agreed, I ran into the issue a while ago. Not such a major issues as it would be for something like a KDE or mono update but annoying none the less. Peter -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Broken dependencies in Fedora 11 - 2009-08-20
On Fri, Aug 21, 2009 at 8:13 PM, Kevin Kofler wrote: > drago01 wrote: >> Sorry but the fail here is 100% on bodhi's side , why does a single >> package obsolete a complete group update? >> That is just broken, and this example clearly showed it. > > It's broken (we've had some fun with that with the KDE grouped updates too, > we learned to be careful about what we push when), but a maintainer should > know how to use our tools, which includes being aware of their limitations. > Double-checking things both before and after filing an update (e.g. checking > https://admin.fedoraproject.org/updates/thepackageyoureabouttopushanupdatefor > before filing the new update request) definitely can't hurt (I always do > that), and it will help avoiding issues you don't even know about, or at > least catching them earlier than 2 months after the fact (as happened here). Sure if you know about a bug/limitation you can try to avoid it, but as Josh said you can't expect that every maintainer knows about all (undocumented) bugs/limitations. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Broken dependencies in Fedora 11 - 2009-08-20
On Fri, Aug 21, 2009 at 08:13:34PM +0200, Kevin Kofler wrote: >drago01 wrote: >> Sorry but the fail here is 100% on bodhi's side , why does a single >> package obsolete a complete group update? >> That is just broken, and this example clearly showed it. > >It's broken (we've had some fun with that with the KDE grouped updates too, >we learned to be careful about what we push when), but a maintainer should >know how to use our tools, which includes being aware of their limitations. I use bodhi every day. I have yet to find all it's limitations. There are known limitations that aren't even documented. I think it's a bit far reaching to say that maintainers should just know, when there is no good way for them to know without either reading the code or excessive use. >Double-checking things both before and after filing an update (e.g. checking >https://admin.fedoraproject.org/updates/thepackageyoureabouttopushanupdatefor >before filing the new update request) definitely can't hurt (I always do >that), and it will help avoiding issues you don't even know about, or at >least catching them earlier than 2 months after the fact (as happened here). That's decent advice, but it will not catch quite a number of the problems that we see come up. josh -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Broken dependencies in Fedora 11 - 2009-08-20
drago01 wrote: > Sorry but the fail here is 100% on bodhi's side , why does a single > package obsolete a complete group update? > That is just broken, and this example clearly showed it. It's broken (we've had some fun with that with the KDE grouped updates too, we learned to be careful about what we push when), but a maintainer should know how to use our tools, which includes being aware of their limitations. Double-checking things both before and after filing an update (e.g. checking https://admin.fedoraproject.org/updates/thepackageyoureabouttopushanupdatefor before filing the new update request) definitely can't hurt (I always do that), and it will help avoiding issues you don't even know about, or at least catching them earlier than 2 months after the fact (as happened here). Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
FESCo meeting summary for 20090821
Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2009-08-21/fedora-meeting.2009-08-21-17.00.html Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2009-08-21/fedora-meeting.2009-08-21-17.00.txt Log: http://meetbot.fedoraproject.org/fedora-meeting/2009-08-21/fedora-meeting.2009-08-21-17.00.log.html --- 17:00:03 #startmeeting FESCo meeting 2009-08-21 17:00:06 #chair dgilmore jwb notting nirik sharkcz jds2001 j-rod skvidal Kevin_Kofler 17:00:11 * nirik is here. 17:00:12 Present. 17:00:16 * sharkcz here 17:00:16 * jwb is here 17:00:58 seems as though we have some minimal quorum 17:01:12 * notting is here 17:01:22 #topic Moblin feature 17:01:29 .fesco 244 17:01:46 * nirik goes to doublecheck the page now 17:01:58 IMHO the rescoped feature is OK. 17:02:18 i agree 17:02:20 Not quite as exciting as the original (complete Moblin, spin), but still worth mentioning. 17:02:21 yeah, I think so too. 17:02:26 * jds2001 too 17:02:30 +1 17:02:34 hopefully if things go well the spin for f13 would be nice. ;) 17:02:37 works for me 17:02:48 +1 to accepting the rescoped feature 17:02:48 +1 17:02:53 * j-rod here 17:02:56 * mchua lurking 17:03:03 +1, fine with that too 17:03:08 +1 (making it official) 17:03:11 +1 17:03:23 #agreed Re-scoped Moblin feature is accepted for F12 17:03:32 yay. we aren't unreasonable 17:03:43 #topic jjames sponsor nomination 17:03:48 .fesco 242 17:04:03 I didn't see any objections to this. 17:04:25 +1, no objections from me nor anyone else AFAIK 17:04:35 +1 17:04:41 +1 17:04:47 +1 from me. 17:04:50 +1 from me 17:05:05 #agreed jjames sponsor nomination is approved 17:05:08 +1, though i think we need to address the NEEDSPONSOR thing a bit separately 17:05:30 Uhm, how? What do you mean? 17:05:46 his reasoning for wanting to be a sponsor (which is fine) is: 17:05:50 (What's the problem and what's your proposed solution?) 17:06:03 "This request is prompted by the large number of times that I have seen a package submission that I was personally interested in, only to find that the submitter needed a sponsor." 17:06:17 oh, we need more sponsors :) 17:06:19 there is no reason he couldn't have reviewed it without being a sponsor 17:06:22 we just got one more :) 17:06:26 no, we need more active sponsors. ;( 17:06:55 anyway, this is a tangent 17:07:03 we can come back to it during open discussion 17:07:06 anyhow, next 17:07:13 #topic libvdpau inclusion 17:07:19 .fesco 238 17:07:22 any updates? 17:07:26 no, I suck 17:07:39 * drago01 too 17:07:47 but ajax mail is worth reading 17:07:54 was on my TODO list last night 17:08:00 alrighty then, deferred again 17:08:07 drago01, yeah i found that to be a good email 17:08:13 #topic Open floor 17:08:21 that's all i had :) 17:08:31 Are there any FPC guidelines pending ratification? A mail on the fedora-devel-list claimed there are. 17:08:35 jds2001, was tomas' provenpackager not included? 17:08:37 there are? 17:08:46 jwb: no, because it came in yesterday 17:08:48 ah 17:10:35 therew as a number of FPC guidelines that i didnt close the ticket for that we considered last week 17:10:40 https://fedorahosted.org/fesco/ticket/245 17:10:52 .fesco 245 17:10:58 This one is new and wasn't put on the meeting agenda (with the keyword) for some reason. 17:11:05 I don't remember voting over this, at least. 17:11:08 wait... does ajax's argument sway anyone one way or another wrt libvdpau? 17:11:11 oh, oops 17:11:19 Kevin_Kofler: right, we didn't 17:11:25 sorry abuot that :( 17:12:49 The mail talked about multiple ones, but that's the only open report I'm aware of. 17:13:04 right, I think the other ones were what we did last week 17:13:11 spot: ping 17:13:25 jds2001: yes? 17:13:28 * jds2001 occasionally sucks at closing old tickets 17:13:41 spot: the only outstanding FPC guideline I'm aware of is Fortran 17:13:55 * jds2001 forgot to throw that on the agenda today, sorry 17:14:01 Yeah, 2 more FPC members confirmed that too to me. :-) 17:14:03 but you mentioned "several" in your mail. 17:14:06 So Fortran it is. 17:14:16 s/2 more/2/ 17:14:21 jds2001: 241 wasn't closed when i looked before 17:14:38 spot: oh, sorry about that, I sucked at closing tickets from last weeks meeting\ 17:15:02 Can we vote over the Fortran guidelines now? 17:15:06 sure thing 17:15:08 seem reasonable as much as fortran is. +1 17:15:13 #topic Fortran FPC guideline 17:15:18 yeah, same here... +1 from me. 17:15:52 also here ... +1 17:15:56 +1, guidelines look sane. 17:16:00 fortan is not cutting-edge and not in line with Fedora's goals. -1 17:16:08 oh wait... no. 17:16:09 +1 i think they look fine 17:16:10 +1 17:16:11 :) 17:16:24 +1 17:16:59 #agreed Fortran guidelines are accepted. 17:17:09 +1 17:17:44 #topic Open Floor again... 17:17:56 ! 17:18:06 kwizart: ? 17:18:07 About VDPAU, i've contacted Aaron Plattner from nvidia and more accurately the "freedesktop.org vdpau maintainer" to ask either or no
Re: TeX Live 2009 for Fedora
Norbert Preining wrote: > So you are packaging each an every tlp into one rpm. Wowww. > > Well, that makes many things easier, and at the same time also > complicated. Many packages. In Debian we couldn't do that, adding sooo > many packages in one go. That was how rel-eng and FPC explicitly asked for things to be done. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Broken dependencies in Fedora 11 - 2009-08-20
On Fri, Aug 21, 2009 at 3:07 PM, Kevin Kofler wrote: > Michael Schwendt wrote: >> Indeed. A single tomboy build obsoleted more than a dozen Mono packages >> and actually got marked stable sometimes later without anyone adding >> a comment. > > I'd blame the tomboy maintainer for the chaos there. Before you push an > update to a package, you MUST check for previous updates for the package > (possibly filed by somebody else, Bodhi will NOT mail you about them, even > if you are the maintainer!), and if it's a grouped update, you CANNOT push a > new update for your package, you MUST get it updated in the group instead. Sorry but the fail here is 100% on bodhi's side , why does a single package obsolete a complete group update? That is just broken, and this example clearly showed it. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Broken dependencies in Fedora 11 - 2009-08-20
Till Maas wrote: > I'd blame the bad workflow and the unexpected beheaviour of bodhi. Btw. > all your steps are not documented in the Package Update Howto[0] and are > probably not valid anymore, since the auto obsoletion is disabled now. > But I do not really know how Bodhi would behave now. The new behavior is probably that Bodhi will just make a big mess if you push that update (like thinking that the older version in the group is "newer" if it gets pushed later for whatever reason). Or at best you'll get an error. So I think my advice to get the group edited to include your new build instead is still sound. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Plan for tomorrow's (20090821) FESCo meeting
On Fri, 2009-08-21 at 18:22 +0200, drago01 wrote: > On Fri, Aug 21, 2009 at 5:54 PM, Adam Williamson wrote: > > On Fri, 2009-08-21 at 16:51 +0200, drago01 wrote: > > > >> Well S3 does, but there driver isn't open either. > >> But it proves that non nvidia implementations are possible. > > > > S3's driver implements VAAPI, not VDPAU. I already have a package review > > for libva submitted (mentioned it yesterday). > > http://drivers.s3graphics.com/en/download/drivers/chrome5x-Linux/RN_Linux_EN.txt > > hmm? > > I have not tested it due to lack of hardware but it says: > > 06/26/2009: Version 14.02.17 > - Bug Fixes > - XRandR support > - VDPAU support > - KMS Support > > SUPPORTED FEATURES > > - H/W accelerated 2D (XAA/EXA) > - H/W accelerated direct-rendering OpenG3.0 > - H/W accelerated H.264/MPEG2/WMV-9/VC-1 video playback. > - SAMM / Rotation / Xinerama / Compiz > - XRandR support > - VDPAU support > - KMS Support > > > And there are a lot of VDPAU references in the bug fixed list. Oh, that's interesting. I guess you're right, then. Sorry - I was going off references from the VAAPI site, I didn't check with the actual driver package. http://www.freedesktop.org/wiki/Software/vaapi lists VIA / S3 Graphics Accelerated Linux Driver under 'Drivers (back-ends) that implement VA API'. Maybe it does both... -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning some packages
Hi, sali...@fedoraproject.org wrote: > On these other packages, I'm reducing my involvement to being > co-maintainer, and new package owners are already selected when > ownership was released: > banshee [spot] If there is help needed, I'd like to volunteer co-maintaining banshee. I'm using banshee from time to time and I'm also maintaining some other mono-based packages. Best regards, Christian -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Plan for tomorrow's (20090821) FESCo meeting
On Fri, Aug 21, 2009 at 5:54 PM, Adam Williamson wrote: > On Fri, 2009-08-21 at 16:51 +0200, drago01 wrote: > >> Well S3 does, but there driver isn't open either. >> But it proves that non nvidia implementations are possible. > > S3's driver implements VAAPI, not VDPAU. I already have a package review > for libva submitted (mentioned it yesterday). http://drivers.s3graphics.com/en/download/drivers/chrome5x-Linux/RN_Linux_EN.txt hmm? I have not tested it due to lack of hardware but it says: 06/26/2009: Version 14.02.17 - Bug Fixes - XRandR support - VDPAU support - KMS Support SUPPORTED FEATURES - H/W accelerated 2D (XAA/EXA) - H/W accelerated direct-rendering OpenG3.0 - H/W accelerated H.264/MPEG2/WMV-9/VC-1 video playback. - SAMM / Rotation / Xinerama / Compiz - XRandR support - VDPAU support - KMS Support And there are a lot of VDPAU references in the bug fixed list. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Plan for tomorrow's (20090821) FESCo meeting
On Fri, 2009-08-21 at 16:51 +0200, drago01 wrote: > Well S3 does, but there driver isn't open either. > But it proves that non nvidia implementations are possible. S3's driver implements VAAPI, not VDPAU. I already have a package review for libva submitted (mentioned it yesterday). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Plan for tomorrow's (20090821) FESCo meeting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 21.08.2009 17:10, schrieb Adam Jackson: > On Fri, 2009-08-21 at 16:26 +0200, Jochen Schmitt wrote: > >> - From my point of view. This cases demostrate, that we need a >> clarification about the requirements which a package has to >> fullfill for inclusssion into Fedora. > > I don't disagree, but... > >> Package which are only useable if you have installed a package >> which is not part of Fedora may not allow for Fedora. This is the >> argument why we not contributes eumulators. In common emulators >> requires special ROM images which contains copyright content. > > I think this is a faulty generalization. > > X is a network protocol. vdpau and xnvctrl applications can be > perfectly functional running on a Fedora machine with no nvidia > driver installed, if they happen to be talking to some _other_ > machine somewhere in the world that does support those extensions. > One might argue that this is a trivial distinction, and that it > still requires some non-free blob to be made to work, but to make > that assertion you're basically saying that interoperability is > only acceptable if there's some free implementation of what you're > interoperating with. If you follow that idea through, you end up > removing pilot-link, libgpod... > > The emulator rule-of-thumb makes sense to the extent that the > emulator itself is the end goal. If the only reason you could want > it installed is to play some arcade game ROM then there's pretty > clearly no interoperability argument to be made. But libvdpau > isn't the end goal; the VDPAU app is the end goal. libvdpau is > just how you get there. > > The emulator RoT also assumes that the copyright holder of the > magic bits doesn't _want_ you to use them. NVIDIA clearly wants > people to use VDPAU. > > - ajax Thank you for your explaination. I think we should make a distinct betwenn a regquirement which must install on the same machine and another requirement which is provides by a remote system. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAkqOumsACgkQZLAIBz9lVu9MoQP/ZNjwRUZSEUFxRj19pmjKocky 4OfA8yE8k15ZSEGr46wy7aMTshSnN0Ccw3hxwM1Qj+Z/g21XVJlXOK4EyFIz28Mt voBhqg2nYOBbArbBfLs+Jp3BnVZ1WIUdhTtWyDfdo6l5si61QYc5QGL2ZATBaHRT 7BYhDbiZFWxevACyRPE= =QIRs -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Plan for tomorrow's (20090821) FESCo meeting
On Fri, 2009-08-21 at 16:26 +0200, Jochen Schmitt wrote: > - From my point of view. This cases demostrate, that we need a > clarification about the requirements which a package has to fullfill > for inclusssion into Fedora. I don't disagree, but... > Package which are only useable if you have installed a package which > is not part of Fedora may not allow for Fedora. This is the argument > why we not contributes eumulators. In common emulators requires > special ROM images which contains copyright content. I think this is a faulty generalization. X is a network protocol. vdpau and xnvctrl applications can be perfectly functional running on a Fedora machine with no nvidia driver installed, if they happen to be talking to some _other_ machine somewhere in the world that does support those extensions. One might argue that this is a trivial distinction, and that it still requires some non-free blob to be made to work, but to make that assertion you're basically saying that interoperability is only acceptable if there's some free implementation of what you're interoperating with. If you follow that idea through, you end up removing pilot-link, libgpod... The emulator rule-of-thumb makes sense to the extent that the emulator itself is the end goal. If the only reason you could want it installed is to play some arcade game ROM then there's pretty clearly no interoperability argument to be made. But libvdpau isn't the end goal; the VDPAU app is the end goal. libvdpau is just how you get there. The emulator RoT also assumes that the copyright holder of the magic bits doesn't _want_ you to use them. NVIDIA clearly wants people to use VDPAU. - ajax signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Broken dependencies in Fedora 11 - 2009-08-20
On Fri, Aug 21, 2009 at 03:07:47PM +0200, Kevin Kofler wrote: > Michael Schwendt wrote: > > Indeed. A single tomboy build obsoleted more than a dozen Mono packages > > and actually got marked stable sometimes later without anyone adding > > a comment. > > I'd blame the tomboy maintainer for the chaos there. Before you push an > update to a package, you MUST check for previous updates for the package > (possibly filed by somebody else, Bodhi will NOT mail you about them, even > if you are the maintainer!), and if it's a grouped update, you CANNOT push a > new update for your package, you MUST get it updated in the group instead. I'd blame the bad workflow and the unexpected beheaviour of bodhi. Btw. all your steps are not documented in the Package Update Howto[0] and are probably not valid anymore, since the auto obsoletion is disabled now. But I do not really know how Bodhi would behave now. Regards Till [0] https://fedoraproject.org/wiki/Package_update_HOWTO pgpe0kVTrakjl.pgp Description: PGP signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Plan for tomorrow's (20090821) FESCo meeting
On Fri, Aug 21, 2009 at 3:57 PM, Adam Jackson wrote: > On Fri, 2009-08-21 at 15:39 +0200, Jochen Schmitt wrote: >> On Thu, 20 Aug 2009 22:10:59 -0400, you wrote: >> >> >238 Can libvdpau go in Fedora? >> >> As far I understand this package itself is open source but has a >> dependency to the properitary nVidia video driver which is >> provides by rpmfusion.org. >> >> For this reason I vote agains the inclusion of this package into >> Fedora because I introduce a requirement reference to a >> third-party repository. > > I think there's precedents for accepting it for Fedora: > > - libXNVCtrl, another X extension library that happens to only do > anything when the user is running the nvidia binary driver, but which is > itself MIT-licensed. > > - gstreamer-plugins-flumpegdemux, which allows you to separate the audio > and video streams from MPEG files, even though the decoding itself is > off-limits for Fedora > > It happens that only nvidia implements VDPAU at the moment, but so what? > Any other vendor could too. Well S3 does, but there driver isn't open either. But it proves that non nvidia implementations are possible. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Audacious 2.1 coming - SONAME change
On 07/16/2009 02:30 PM, Michael Schwendt wrote: Audacious 2.1 is going to land in Rawhide soon. src.rpm updates have been comitted to Fedora package cvs/devel already. Compared with 1.5.1 this new final release changes the SONAME version of essential libraries within the audacious-libs package. Dependencies will need to be rebuilt. Plugins may need a minor update to sync with modified plugin API structures. Hi Michael, I've finally gotten around to upgrading the freeworld plugins in rpmfusion development repo, they are at 2.1 now too. Regards, Hans -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Plan for tomorrow's (20090821) FESCo meeting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 21.08.2009 15:57, schrieb Adam Jackson: > On Fri, 2009-08-21 at 15:39 +0200, Jochen Schmitt wrote: >> On Thu, 20 Aug 2009 22:10:59 -0400, you wrote: >> >>> 238Can libvdpau go in Fedora? >> >> As far I understand this package itself is open source but has a >> dependency to the properitary nVidia video driver which is >> provides by rpmfusion.org. >> >> For this reason I vote agains the inclusion of this package into >> Fedora because I introduce a requirement reference to a >> third-party repository. > > I think there's precedents for accepting it for Fedora: > > - libXNVCtrl, another X extension library that happens to only do > anything when the user is running the nvidia binary driver, but which is > itself MIT-licensed. > > - gstreamer-plugins-flumpegdemux, which allows you to separate the audio > and video streams from MPEG files, even though the decoding itself is > off-limits for Fedora - From my point of view. This cases demostrate, that we need a clarification about the requirements which a package has to fullfill for inclusssion into Fedora. Package which are only useable if you have installed a package which is not part of Fedora may not allow for Fedora. This is the argument why we not contributes eumulators. In common emulators requires special ROM images which contains copyright content. > > It happens that only nvidia implements VDPAU at the moment, but so what? > Any other vendor could too. > > - A made dicision may not be valid forever. If we will have got a opensource package which allow the usage of vdpau with the close source driver from nvidia we can change this dicision. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAkqOrqYACgkQZLAIBz9lVu8IPQP/URKbZwLWz86b6y+8mRJtNv61 sUhgpY8pXQ1ztvf1HKVL2gdj6QnVuzFS6wb4x3UN3UTpErDZaF5x6galuS1zJOOo 5+iSjtkVdxDr12CQTEUT7+weKYTGxw3Vg2cFNzH4j3GkQzo8vxm2DJCDEwXvyZ3Q K8WjxvoHRS/LUXQn5pM= =8/2F -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Plan for tomorrow's (20090821) FESCo meeting
On 08/20/2009 10:10 PM, Jon Stanley wrote: > Apologies for the late agenda, I completely blanked out today :(. The > following are the topics for tomorrow's meeting at 17:00UTC on > #fedora-meeting on freenode: > > 244 Reconsider Moblin Feature for Fedora 12 > 238 Can libvdpau go in Fedora? > > For more complete details, please visit each individual ticket. The > report of the agenda items can be found at > https://fedorahosted.org/fesco/report/9 > > If you would like to add something to this agenda, you can reply to > this e-mail, file a new ticket at https://fedorahosted.org/fesco, > e-mail me directly, or bring it up at the end of the meeting, during > the open floor. I'm pretty sure there are several Fedora Packaging Committee items waiting to be ratified. I think there are at least two tickets still open in Traac. ~spot -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Plan for tomorrow's (20090821) FESCo meeting
On Fri, 2009-08-21 at 15:39 +0200, Jochen Schmitt wrote: > On Thu, 20 Aug 2009 22:10:59 -0400, you wrote: > > >238 Can libvdpau go in Fedora? > > As far I understand this package itself is open source but has a > dependency to the properitary nVidia video driver which is > provides by rpmfusion.org. > > For this reason I vote agains the inclusion of this package into > Fedora because I introduce a requirement reference to a > third-party repository. I think there's precedents for accepting it for Fedora: - libXNVCtrl, another X extension library that happens to only do anything when the user is running the nvidia binary driver, but which is itself MIT-licensed. - gstreamer-plugins-flumpegdemux, which allows you to separate the audio and video streams from MPEG files, even though the decoding itself is off-limits for Fedora It happens that only nvidia implements VDPAU at the moment, but so what? Any other vendor could too. - ajax signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning packages
Picked up: 1. gquilt 2. quilt Co-maintainers are welcome. Thanks and Regards, Vivek -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Multiline values in bodhi.template
I'm believe before this works fine, but now I try put multiline comment into notes field like: # Description of your update notes=- New version. - Name directory in tarball sim instead of trunk. - Step to lzma source packaging. - For BUG#478341 fixing add R kdebase3-libs and got error: [pa...@x-www F-10]$ make update Traceback (most recent call last): File "/usr/bin/bodhi", line 322, in main() File "/usr/bin/bodhi", line 129, in main updates = bodhi.parse_file(input_file=opts.input_file) File "/usr/lib/python2.6/site-packages/fedora/client/bodhi.py", line 276, in parse_file config.readfp(template_file) File "/usr/lib/python2.6/site-packages/iniparse/compat.py", line 115, in readfp self.data._readfp(fp) File "/usr/lib/python2.6/site-packages/iniparse/ini.py", line 629, in _readfp raise exc ConfigParser.ParsingError: File contains parsing errors: bodhi.template [line 14]: - New version. [line 15]: - Name directory in tarball sim instead of trunk. [line 16]: - Step to lzma source packaging. [line 17]: - For BUG#478341 fixing add R kdebase3-libs Why? Can I provide multiline notes at all? How? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Plan for tomorrow's (20090821) FESCo meeting
On Thu, 20 Aug 2009 22:10:59 -0400, you wrote: >238Can libvdpau go in Fedora? As far I understand this package itself is open source but has a dependency to the properitary nVidia video driver which is provides by rpmfusion.org. For this reason I vote agains the inclusion of this package into Fedora because I introduce a requirement reference to a third-party repository. Best Regards: Jochen Schmitt -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: TeX Live 2009 for Fedora
On Thu, 2009-08-20 at 17:10 +0200, Jindrich Novy wrote:
> On Thu, Aug 20, 2009 at 04:48:49PM +0300, Jussi Lehtola wrote:
> > It seems your spec making program has some bugs, as some packages have
> > names such as texlive-csplain.ARCH, this probably shouldn't be..?
>
> Nope, it is intentional. It is needed to somehow distinguish the
> noarch and arch-dependent part. So package texlive-csplain contains
> the noarch bits and texlive-csplain.ARCH ships the binaries.
Wouldn't it be better to have texlive-csplain%{_isa} shipping the arch
dependent bits and a texlive-csplain-common.noarch shipping the arch
independent stuff? That would be more in line with other packages.
--
Jussi Lehtola
Fedora Project Contributor
jussileht...@fedoraproject.org
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Broken dependencies in Fedora 11 - 2009-08-20
Michael Schwendt wrote: > Indeed. A single tomboy build obsoleted more than a dozen Mono packages > and actually got marked stable sometimes later without anyone adding > a comment. I'd blame the tomboy maintainer for the chaos there. Before you push an update to a package, you MUST check for previous updates for the package (possibly filed by somebody else, Bodhi will NOT mail you about them, even if you are the maintainer!), and if it's a grouped update, you CANNOT push a new update for your package, you MUST get it updated in the group instead. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: TeX Live 2009 for Fedora
Jindrich Novy wrote: > Nope, it is intentional. It is needed to somehow distinguish the > noarch and arch-dependent part. So package texlive-csplain contains > the noarch bits and texlive-csplain.ARCH ships the binaries. Wouldn't texlive-csplain-libs or texlive-csplain-bin be more compliant to our guidelines? Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Confusion with openal-soft
Jochen Schmitt wrote: > Pushing openal-soft info F-11/F-10 is a violation of the Fedora > updating policy. It's not. It's entirely acceptable to bump a soname if there's a good reason to and dependent packages WILL have to get rebuilt. It would be impossible to update something like xulrunner for security fixes otherwise. That said, in this case, IMHO there are too many dependent packages to force such a global rebuild. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Confusion with openal-soft
Adam Williamson wrote: > It's usually possible to have the devel packages co-exist by renaming > the new library (make it libopenal-soft.so). This may require a small > patch to any app you want to build against the new version (make it look > for libopenal-soft instead of just libopenal), but I think this is > preferable to conflicting -devel packages. Right, see also the hackery we do to allow kdelibs-devel and kdelibs3-devel to coexist. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Add Moblin Desktop group to comps
On Fri, 2009-08-21 at 09:57 +0100, Peter Robinson wrote: > >> I would like to add a group for the Moblin Desktop. My proposed patch > >> is below and feedback is welcome. > >> > >> Cheers, > >> Peter > >> > >> + > >> + mutter > >> + mutter-moblin > >> + > > > > Speaking of these two, any reason mutter-moblin does not currently > > require moblin? (And when it's fixed, is it better to list both mutter > > and mutter-moblin, or let depsolving pull in mutter?) > > There is no "moblin" package as such. In fact mutter-moblin is the > main desktop env package. Ah, I meant listing both mutter and mutter-moblin, rather than just mutter-moblin. Slip of the fingers, when both parts of the name starts with the same letter and have the same length! -- Michel signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Add Moblin Desktop group to comps
>> I would like to add a group for the Moblin Desktop. My proposed patch >> is below and feedback is welcome. >> >> Cheers, >> Peter >> >> + >> + mutter >> + mutter-moblin >> + > > Speaking of these two, any reason mutter-moblin does not currently > require moblin? (And when it's fixed, is it better to list both mutter > and mutter-moblin, or let depsolving pull in mutter?) There is no "moblin" package as such. In fact mutter-moblin is the main desktop env package. I need to sit down and got through the package list and work out the exact dependency tree. I know it mostly from packaging everything up but there's no doubt something I'll miss. Peter -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Add Moblin Desktop group to comps
>> > Depends on which bits you look at. Most of the packages are based on >> > Fedora packages, the whole lot is built using the suse build system. >> > The NM/connman is an interesting split. It seems suse is assisting the >> > process from the build side of things but has written a NetworkManger >> > moblin GUI that looks the same as the connman one sot they are >> > interchangable. Obviously we'll use the NM one because NM is cool :-) >> > Other than the 30 odd new packages needed for Moblin there doesn't >> > seem to be massive convergence from the other core Fedora packages. >> >> Doesn't seem to be convergence? > > I think he meant divergence. No thinking needed. he definitely meant that yesterday was a busy day :) Peter -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
