![]() Second, asking for review means that the requestee gets notified about your patch and can't forget it. First of all, unless you are a very experienced Eigen developer, we ask that you get your patches reviewed before you can push them. When you attach a patch to a bug, make sure to tick the 'patch' checkbox.Īsking for review serves two main purposes. By default, bugs are assigned to the dummy 'Nobody' user, which means that they need someone to take care of them. If you're taking care of a bug, mark it as 'assigned' to you. Tracking bugs have the corresponding version number as alias, so you don't need to remember their ids.įeatures wanted in a given release are the bugs blocking the tracking bug. Tracking the development of future Eigen versionsĮach planned future Eigen version should be represented by its own 'tracking bug', for example Eigen 3.0 is bug 25. the tracking bug for the 3.0 release has 3.0 as alias You don't need to know the tracking bug id, as tracking bugs have the version number as alias, e.g. If your feature should make it into a specific Eigen release, add to the 'Blocks' field the tracking bug for that release. You can split big features into smaller bugs, but then it's a good idea to file a meta-bug about the feature and mark it as 'depending' on the smaller bugs. Henceforth it's important to note that in bugzilla terminology, a 'bug' is not necessarily a bug in the usual sense, it is just any issue under tracking. You should file a new 'bug' for each feature that you're developing. This has been added recently (), so many old bugs still have 'Unknown' severity. If you are unsure use 'Unknown', or ask in IRC or the mailing list for other values. Use the 'severity' field to indicate the kind of problem. Try to select the right component, or set it to 'General' if you don't know. Check these to avoid entering duplicates - you can add yourself to the corresponding cc-list, add a new comment or edit the fields. While entering the summary, a list of possible duplicates appears. 3 Tracking the development of future Eigen versions.I expect this is because the package should be a noarch package.ġ packages and 0 specfiles checked 2 errors, 1 warnings. Note: There are rpmlint messages (see attachment).Ĭhecking: diffuse-0.6.86_64.rpmĭiffuse.x86_64: W: incoherent-version-in-changelog 0.6.0 ĭiffuse.x86_64: E: incorrect-fsf-address /usr/share/doc/diffuse/COPYINGĭiffuse.src:22: W: unversioned-explicit-provides mergetoolĭiffuse.src:23: W: unversioned-explicit-provides difftoolĭiffuse.src:8: W: mixed-use-of-spaces-and-tabs (spaces: line 1, tab: line 8)ĭiffuse.src: E: specfile-error warning: line 90: multiple %files for package 'diffuse'Ģ packages and 0 specfiles checked 4 errors, 4 warnings. : Rpmlint is run on all installed packages. It is possible to split the package into sub-packages here, but let's look at that after the first round of tweaks. Note: Arch-ed rpms have a total of 1003520 bytes in /usr/share : Large data in /usr/share should live in a noarch subpackage if package Reviews/1923830-diffuse3-meson/srpm-unpacked/diffuse3-meson.spec ![]() Note: Bad spec filename: /home/asinha/dump/fedora. : Spec file according to URL is the same as in SRPM. : Spec use %global instead of %define unless justified. : Sources can be downloaded from URI in Source: tag : Packager, Vendor, PreReq, Copyright tags should not be in spec file ![]() : No file requires outside of /etc, /bin, /sbin, /usr/bin, /usr/sbin. = Pass, = Fail, = Not applicable, = Not evaluated
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |