devel May 2009

devel@lists.stg.fedoraproject.org

310 participants
223 discussions

Finding file conflicts
by Axel Thimm 11 Jun '09

11 Jun '09

Hi, I ran into a situation where two packages in F10 (pwlib-devel and ptlib-devel) contained file conflicts, and yum tried to install both (in this case there seems to be a bug that made yum ignore the Obsoletes: line of on of the packages). If I as a packager craft a package for Fedora, how can I check that this package's contents aren't accidentially conflicting with another package in Fedora? Is there some magic python script that would check a package against a whole repo? Thanks! -- Axel.Thimm at ATrpms.net

8 12

mono-2.4 and ppc64 status
by Toshio Kuratomi 10 Jun '09

10 Jun '09

Mono-2.4 has been built for ppc64 in F11 and devel. So people should be able to start rebuilding packages to include ppc64 as well as the other arches. There's a few wrinkles to watch out for: 1) Packages with dependencies will have to be built in dependency order. For instance, a lot of packages depend on the gtk-sharp2 bindings and those haven't been built yet. 2) Because of the imminent release of F11 we're in a freeze state. This means getting dependencies into the Fedora11 buildroot will require people to request tagging explicitly. This also means that if you rebuild your package for F11 with ppc64 support and later you have to get this package tagged into the release, all of the packages it depends on will need to be tagged in as well (otherwise your ppc64 build will have broken deps). With these in mind, I'd recommend people start rebuilding their mono packages on ppc64 in the devel branch. Keep track of the dependency chain you encounter. Then perform your builds in the Fedora 11 branch as updates after the release. I'm not a mono-sig member, though, so if you guys decide something else makes sense, just be sure to come up with a plan so we don't release with a bunch of broken dependencies. -Toshio

5 9

PolicyKit changes in F12
by Matthias Clasen 10 Jun '09

10 Jun '09

Just a heads-up: We hope to land a new PolicyKit version (which will turn into 1.0, eventually) in F12 soon. The new version simplifies the API and will require PolicyKit-using application to be ported. For more information, have a look at the feature page: http://fedoraproject.org/wiki/Features/PolicyKitOne It also has pointers to api docs and a (terse) porting guide. We already have a collection of patches for quite a few PolicyKit-using apps, so the transitions should be relatively painless. Matthias

9 20

ctrlproxy-3.0.6
by Bernie Innocenti 09 Jun '09

09 Jun '09

Ciao, I updated ctrlproxy to 3.0.6, and the resulting packages are here: http://www.codewiz.org/pub/fedora/pkgs/ Patch follows. Can I commit it to CVS? diff -u -p -r1.15 ctrlproxy.spec --- ctrlproxy.spec 19 Feb 2008 07:31:45 -0000 1.15 +++ ctrlproxy.spec 25 May 2008 14:25:14 -0000 @@ -1,12 +1,18 @@ +%define ctrlproxy_homedir %{_var}/lib/ctrlproxy +%define ctrlproxy_logdir %{_var}/log/irc +%define ctrlproxy_service ctrlproxy +%define ctrlproxy_user ctrlproxy + Summary: ctrlproxy Name: ctrlproxy -Version: 3.0.5 -Release: 2%{?dist} +Version: 3.0.6 +Release: 1%{?dist} License: GPLv2+ Group: Applications/Internet Source: http://jelmer.vernstok.nl/releases/ctrlproxy-%{version}.tar.gz Url: http://jelmer.vernstok.nl/ctrlproxy/ -Patch0: ctrlproxy-fix-ansi-build.patch +Source100: ctrlproxy.init +Source101: ctrlproxy.config BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) BuildRequires: glib2-devel, popt, gnutls-devel @@ -31,7 +37,6 @@ ctrlproxy development headers %prep %setup -q -%patch0 -p1 %build %configure @@ -45,6 +50,23 @@ mkdir $RPM_BUILD_ROOT make DESTDIR=$RPM_BUILD_ROOT install make DESTDIR=$RPM_BUILD_ROOT -C doc install chmod 0644 ${RPM_BUILD_ROOT}%{_datadir}/ctrlproxy/motd +install -D -m 0755 %{SOURCE100} $RPM_BUILD_ROOT/%{_sysconfdir}/init.d/ctrlproxy +install -D -m 0640 %{SOURCE101} $RPM_BUILD_ROOT/%{ctrlproxy_homedir}/config +install -D -d -m 0750 $RPM_BUILD_ROOT/%{ctrlproxy_logdir} + + +%pre +/usr/sbin/useradd -s /sbin/nologin -M -r -d %{ctrlproxy_homedir} \ + -c "ctrlproxy IRC daemon" %{ctrlproxy_user} &>/dev/null || : + +%post +/sbin/chkconfig --add %{ctrlproxy_service} + +%preun +if [ $1 = 0 ]; then + /sbin/service %{ctrlproxy_service} stop > /dev/null 2>&1 || : + /sbin/chkconfig --del %{ctrlproxy_service} +fi %clean [ -d "$RPM_BUILD_ROOT" -a "$RPM_BUILD_ROOT" != "/" ] && rm -rf $RPM_BUILD_ROOT @@ -59,12 +81,24 @@ chmod 0644 ${RPM_BUILD_ROOT}%{_datadir}/ %dir %{_docdir}/ctrlproxy %{_docdir}/ctrlproxy/* +%{_sysconfdir}/init.d/ctrlproxy +%attr(0750, ctrlproxy, ctrlproxy) %dir %{ctrlproxy_logdir} +%attr(0750, ctrlproxy, ctrlproxy) %dir %{ctrlproxy_homedir} +%attr(0750, ctrlproxy, ctrlproxy) %config(noreplace) %{ctrlproxy_homedir}/config + + %files devel %defattr(-,root,root) %{_includedir}/ctrlproxy-3.0/* %{_libdir}/pkgconfig/ctrlproxy.pc %changelog +* Sun May 25 2008 Bernardo Innocenti <bernie(a)codewiz.org> 3.0.6-1 +- Update to latest upstream +- Drop ctrlproxy-fix-irssi-log.patch +- Add initscript +- Create a ctrlproxy user to run ctrlproxy as a daemon + * Tue Feb 19 2008 Fedora Release Engineering <rel-eng(a)fedoraproject.org> - 3.0.5-2 - Autorebuild for GCC 4.3 -- \___/ _| X | Bernie Innocenti - http://www.codewiz.org/ \|_O_| "It's an education project, not a laptop project!"

3 3

Announcing Fedora Activity Day - Fedora Development Cycle 2009
by Jesse Keating 08 Jun '09

08 Jun '09

We're announcing a Fedora Activity day coming up very very soon (apologies for the short notice). This activity day is for maintainers, QA, and release engineering folks to meet and discuss ongoing issues with the Fedora Development Cycle and to create a proposal on how to fix many of the issues. Note, this is not an event to decide on a solution, it is an event to decide on a proposal, which will then be shared with the whole community for more input and work. The timing of this is very short, so that we may have a chance at changing something within the Fedora 12 development cycle. Funding for the event was only confirmed a day or two ago, hence the late notice. If unable to attend (which most will be) but highly interested in helping with the process, we will be attempting to setup a Fedora Talk conference room to use throughout the event, as well as an IRC channel. We'll try to blog the process as well and gather feedback to be used during the event. If you will be able to attend in person, please add your name to the wiki page [1] so that we can properly plan the space needed within RHT. While the wiki page says that the page is still under construction, the dates are solid, the hours during the day are mostly solid, and the location (one of the RHT buildings) is solid. Please feel free to use the discussion page on the wiki to express your thoughts about the event and what problems you're having with the development cycle. Even thoughts on the initial proposal I drew up at the bottom of the wiki page would be welcome, although I do believe that this event will result in a proposal different from what is currently listed. Again we apologize for the short notice! [1]: https://fedoraproject.org/wiki/Fedora_Activity_Day_Fedora_Development_Cycle… -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating _______________________________________________ Fedora-devel-announce mailing list Fedora-devel-announce(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-announce

22 58

Static system level uid/gid's reservations in Fedora/RHEL - how to handle situation?
by Ondřej Vašík 08 Jun '09

08 Jun '09

Hello, at the moment static system level uid/gid's are handled by setup package and /usr/share/doc/setup-*/uidgid file. There is threshold of system uid/gid's - it's uid/gid 100. Another way to reserve "static" uid/gid reservation is http://fedoraproject.org/wiki/PackageUserRegistry ... usable only for Fedora and only semi-static (as base id could be easily changed). As we are running out of the free uid/gid's in uidgid reservation file (no free gid's in fact at the moment), it has to be solved somehow... there are quite often requests for uidgid reservations as it increases security in many cases... What's the best way to handle that situation? One possibility is to increase the threshold of system level id's (to 200? 300?), another is to check current reservation and clean long-term unused reservations (I doubt there are many such cases, so it's only temporary solution). Other could be sharing groups (as static uid's are still available), but that's not always good solution. Any other idea or some prefered solution? Greetings, Ondřej Vašík

7 8

Mono (& Moonlight) Licensing? Revisited
by Frank Murphy 06 Jun '09

06 Jun '09

http://www.itwire.com/content/view/25215/1090/1/1 Not intending to burn the house down. But, going by this article: http://www.itwire.com/content/view/25215/1090/1/1 Dated 25th May. Unease sets in. Frank -- msn: frankly3d skype: frankly3d Mailing-List Reply to: Mailing-List Still Learning, Unicode where possible

5 12

welcome to fedora
by Valent Turkovic 03 Jun '09

03 Jun '09

http://images.howtoforge.com/images/the_perfect_desktop_linux_mint_7_gloria… I saw this and thought that it would also be a nice idea to have in fedora, like a welcome screen "Wellcome to Fedora" or something similar... What are your thoughts on this? -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic

8 10

Maintainer Responsibility Policy
by Brian Pepple 03 Jun '09

03 Jun '09

Hi all, I'm looking for some feedback on what I've got so far for the Maintainer Responsibility Policy. http://fedoraproject.org/wiki/Extras/Schedule/MaintainerResponsibilityPolicy -- == Maintainer Responsibility Policy == === How long to maintain? === 13 months from initial release. === Belong to the appropriate low-traffic mailing list === * Package maintainers will receive important announcements through the moderated fedora-devel-announce mailing list. Maintainers will be automatically subscribed to this list. Everyone that is a primary maintainer of a package in Fedora is also strongly encouraged to subscribe to the fedora-devel list, though this is not mandatory. * http://www.redhat.com/mailman/listinfo/fedora-devel-announce * http://www.redhat.com/mailman/listinfo/fedora-devel-list === Manage security issues === * Package maintainer should handle security issues quickly, and if they need help they should contact the Security Response Team. * http://fedoraproject.org/wiki/Security/ResponseTeam === Deal with reported bugs in a timely manner ==== * 'Nuff said. === Maintain stability for users === * Package maintainers should limit updates within a single Fedora release to those which do not require special user action. Many users update automatically, and if their applications stop working from no action of their own then they will be upset. This goes doubly for services which may break overnight. === Track dependency issues in a timely manner === * In the development tree, and to a small degree in the release trees as well, updates to packages may cause other packages to have broken dependencies. Maintainers will be alerted when this happens, and should work to rebuild their packages with all due haste. Broken dependencies may leave end user systems in a state where no updates will be applied. In order to keep the distribution in a reasonable state, someone will step in and rebuild packages that have had dependency issues for some time, but package maintainers should not rely on these rebuilds. === Notify others of changes that may affect their packages === * Some packages are depended upon by others; in this case, changes to one package may cause issues for others. Maintainers should be aware of the effects that changes to their packages may have, and should alert to the fedora-devel-announce mailing list of updates which contain ABI or API changes which may cause dependency problems for other packages. The announcement should occur a week before the packages update, so all maintainers affected are notified. The announcement should include the following information: * Nature of the change. * Branches (devel, F9, etc.) which will be affected by the change. * Expected date of the change. * List of packages which are affected by the change. Generally, this is merely the list of packages which depend directly on the package which is being updated, and can be found with "repoquery --whatrequires package" where "package" is the package being updated. * If your package upgrade breaks other packages in Rawhide, you should try to help fix the packages affected. For example, when Python-2.5 was integrated into Rawhide, Jeremy Katz at least fixed the important packages and queued a rebuild for all the other packages affected. === Miscellaneous Items === * Maintainers need to maintain an upgrade path for their packages. * F(current-1) -> F(current) -> Rawhide * Packages should be pushed to the Rawhide branch first. If it builds and works fine for a few days, then it can be pushed to F(current). If there is a good reason to push it to F(current-1), it should be done after a few days of being in F(current). --- Thanks, /B -- Brian Pepple <bpepple(a)fedoraproject.org> http://fedoraproject.org/wiki/BrianPepple gpg --keyserver pgp.mit.edu --recv-keys 810CC15E BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E

13 21

Swapping reviews
by Patrick Monnerat 02 Jun '09

02 Jun '09

Hello list, Package WebCalendar (https://bugzilla.redhat.com/show_bug.cgi?id=471231) is awaiting review for 5 month already. I will be glad to review another package in counterpart of this one's review. Thanks in advance. Patrick

3 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel May 2009