FedoraProject - Changes related to "Policy for nonresponsive package maintainers" [en]

Vacation

2013-05-20T02:01:57Z

Add myself for a couple of weeks.

Join the package collection maintainers

2013-05-17T22:52:52Z

‎Install the client tools (Koji) and set up your certificate:

Packaging:Guidelines

2013-05-16T17:06:32Z

Additional information for file permission section

@@ Line 5: / Line 5: @@
 |-
 | Nicolas CHAUVET || [[fas:kwizart|kwizart]] || 2013-05-01 || 2013-05-13 || Vacation, limited access
 |-
 | Jamie Nguyen || [[fas:jamielinux|jamielinux]] || 2013-03-23 || 2013-06-15 || Will respond to email

@@ Line 94: / Line 94: @@
 * Note that you need to supply the ''path'' to the source RPM (which ends in .src.rpm), and '''not''' a URL.  (If you only have the spec file, use <code>rpmbuild --nodeps -bs SPECFILE</code> to create the new source RPM).
-Your koji builds can only depend on packages that are actually in the TARGET distribution repository.  Thus, you can't use koji to build for released distributions if your package depends on other new packages that Bodhi hasn't released yet.  You ''can'' use koji to build for rawhide (the next unreleased version), even if it depends on other new packages, as long as the other packages were built for the "rawhide" as described below.  If you need to build against a package that is not yet a stable released
+Your koji builds can only depend on packages that are actually in the TARGET distribution repository.  Thus, you can't use koji to build for released distributions if your package depends on other new packages that  [[Bodhi | Bodhi]] hasn't released yet.  You ''can'' use koji to build for rawhide (the next unreleased version), even if it depends on other new packages, as long as the other packages were built for the "rawhide" as described below.  If you need to build against a package that is not yet a stable released
 update, you can file a ticket with rel-eng at: https://fedorahosted.org/rel-eng/newticket and request that that package be
 added as a buildroot override. For packages in EPEL, you have to use the component ''epel'' to get the request to the right persons.

@@ Line 1,267: / Line 1,267: @@
 === File Permissions ===
-Permissions on files must be set properly. Executables should be set with executable permissions, for example.
+Permissions on files must be set properly.  In the majority of situations, non-config and non-state files should be owned by root:root, writable only by the owner and universally readable (and executable only if appropriate), that is mode 0644 or 0755.  Directories should be mode 0755.  Most well behaved build scripts and rpm will use these defaults.
 In the past (pre rpm 4.4), it was necessary to have a <code>%defattr</code> section at the beginning of each <code>%files</code> section, but this is now the default and no longer necessary to explicitly include.