Custom Query (894 matches)


Show under each result:

Results (34 - 36 of 894)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Ticket Owner Reporter Resolution Summary
#1129 desai m4z <[email protected]…> fixed 1.3.0pre1 doesn't build from misc/bcfg2.spec

I wondered if the Version (1.3.0) and Release (0.0pre1) tags for 1.3.0pre1 were broken, since Release is usually just the RPM build count (the "version of the RPM package"), but stpierre on IRC explained that they were chosen to keep the package upgradeable (from 1.3.0-x.xpre1 to 1.3.0-x.x with greater x in the latter, whereas 1.3.0pre1-* to 1.3.0-* would not work with most or all rpm tools).

However, this choice leads to problems with the RPM macros because the tarball is still named 1.3.0pre1, as is the directory within it. The following isn't beautiful, but fixes the build:

> osc diff -r1
Index: bcfg2.spec
--- bcfg2.spec	(revision 1)
+++ bcfg2.spec	(working copy)
@@ -18,10 +18,10 @@
 License:          BSD
 %if 0%{?suse_version}
 # SUSEs OBS does not understand the id macro below.
-BuildRoot:        %{_tmppath}/%{name}-%{version}-%{release}
+BuildRoot:        %{_tmppath}/%{name}-%{version}pre1-%{release}
-BuildRoot:        %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
+BuildRoot:        %{_tmppath}/%{name}-%{version}pre1-%{release}-root-%(%{__id_u} -n)
@@ -229,7 +229,7 @@
 This package includes the Bcfg2 reports web frontend.
-%setup -q -n %{name}-%{version}
+%setup -q -n %{name}-%{version}pre1
 %{__python}%{pythonversion} build

I assume this will probably not be merged because it is just temporary and will need to be changed back when 1.3.0 is released, but now at least this ticket documents it. (;

#576 desai [email protected] fixed 2 group of same category should give an alert, only the last is taken

If you build up a profile with some groups that are catogarized, if the same category show up more than one time, only the last category/Group is considered and the other is lost. An alert should show up about this issue because the sysadmin would not realize his error much too late.

An alert should show up in the log and an alert should be in the statistics.

#739 desai strauss fixed 403 Forbidden error for repodata/repomd.xml causes traceback in

Summary says it all :-)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Note: See TracQuery for help on using queries.