Custom Query (894 matches)

When redirecting 'bcfg2-info groups' output to a file or whatever, not all information is redirected.

I tried on virtual servers

1. Fedora 16 3.1.0-7.fc16.x86_64 bcfg2-server 1.2.1-2
2. Fedora 15 2.6.40.3-0.fc15.i686.PAE bcfg2-server 1.2.0-1

So i have redirected command output to a bcfg2-groups file Then copy/paste command output to a file bcfg2-groups-pasted

Here is a result:

1. Fedora 16, bcfg2-server 1.2.1-2

   [root]# bcfg2-info groups > bcfg2-groups 2>&1
   [root]# ll bcfg2-groups
   -rw-r--r-- 1 root root 14462 Oct  2 12:38 bcfg2-groups
   [root]# wc -l bcfg2-groups
   60 bcfg2-groups
   [root]# ll bcfg2-groups-pasted
   -rw-r--r-- 1 root root 18153 Oct  2 12:43 bcfg2-groups-pasted
   [root]# wc -l bcfg2-groups-pasted 
   95 bcfg2-groups-pasted
   

2. Fedora 15, bcfg2-server 1.2.0-1

   [root]# bcfg2-info groups > bcfg2-groups 2>&1
   [root]# ll bcfg2-groups
   -rw-rw-r-- 1 root root 35038 Oct  2 05:50 bcfg2-groups
   [root]# wc -l bcfg2-groups
   174 bcfg2-groups
   [root]# ll bcfg2-groups-pasted 
   -rw-rw-r-- 1 root root 36623 Oct  2 05:50 bcfg2-groups-pasted
   [root]# wc -l bcfg2-groups-pasted 
   184 bcfg2-groups-pasted
   

After upgrading from 1.2.1 to 1.2.3 the following template code ceased to function:

{% for s in metadata.Packages.sources %}\
deb ${s.url}${s.version} {% for comp in s.components %}$comp {% end %}
{% end %}\

The "components" list attribute now appears to be a "component" string.

Not sure if the docs just need updating: ​http://docs.bcfg2.org/server/plugins/generators/packages.html#generating-client-apt-yum-configurations or if there is also a code change required.

Also not sure if the use of the "groups" attribute in the example is accurate. I don't see it in my environment.

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 @@
 %endif
 License:          BSD
 URL:              http://bcfg2.org
-Source0:          ftp://ftp.mcs.anl.gov/pub/bcfg/%{name}-%{version}.tar.gz
+Source0:          ftp://ftp.mcs.anl.gov/pub/bcfg/%{name}-%{version}pre1.tar.gz
 %if 0%{?suse_version}
 # SUSEs OBS does not understand the id macro below.
-BuildRoot:        %{_tmppath}/%{name}-%{version}-%{release}
+BuildRoot:        %{_tmppath}/%{name}-%{version}pre1-%{release}
 %else
-BuildRoot:        %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
+BuildRoot:        %{_tmppath}/%{name}-%{version}pre1-%{release}-root-%(%{__id_u} -n)
 %endif
@@ -229,7 +229,7 @@
 This package includes the Bcfg2 reports web frontend.
 
 %prep
-%setup -q -n %{name}-%{version}
+%setup -q -n %{name}-%{version}pre1
 
 %build
 %{__python}%{pythonversion} setup.py 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. (;