On Fri, Oct 21, 2011 at 7:10 AM, Steve Snodgrass <phe...@gmail.com> wrote: > My apologies, I didn't completely investigate the problem before > complaining. My reposync cron job is not pulling down dashboard 1.2.2 > to my local mirror from the EL6 x86_64 directory. After looking, I > found that while the file is present on your web server, reposync is > ignoring it because your repo metadata is out of date. I verified > that 1.2.2 is missing from the primary.xml file, but you can tell just > from the timestamps - the RPM is from 10/10 10:53, whereas the > metadata is from 10/10 10:19. It would be helpful if you would > automate a createrepo job to either run periodically or as part of > your release process. Thanks.
I think we updated the repodata today. Agreed, though, repodata should be updated when new packages arrive ;) > > On Oct 20, 5:06 pm, Michael Stahnke <stah...@puppetlabs.com> wrote: >> On Thu, Oct 20, 2011 at 9:46 AM, Steve Snodgrass <phe...@gmail.com> wrote: >> > Is this going to make it into the yum repo? Thanks. >> >> What is "this" in this context? Dashboard 1.2.2 is available in the >> yum repo for EL6. >> >> >> >> >> >> >> >> >> >> > On Oct 10, 2:33 pm, Michael Stahnke <stah...@puppetlabs.com> wrote: >> >> This is a maintenance release of Puppet Dashboard 1.2.2. >> >> >> This release is available for download >> >> at:http://downloads.puppetlabs.com/dashboard/ >> >> >> We have included Debian and RPM packages as well as a tarball. >> >> >> RPMs are also available on yum.puppetlabs.com. >> >> >> See the Verifying Puppet Download section >> >> at:http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet >> >> >> Please report feedback via the Puppet Labs Redmine site, using an >> >> affected version of 1.2.2http://projects.puppetlabs.com/projects/dashboard >> >> >> Documentation is available >> >> at:http://docs.puppetlabs.com/dashboard/index.html >> >> >> # Highlights for this release >> >> >> ## (#9940) dashboard-workers can be managed as service >> >> >> The stop command in the puppet-dashboard-workers init script would >> >> fail when >> >> run using a puppet service resource. This had something to do with >> >> the way sudo >> >> works on EL. Removing the sudo from the stop function allows the >> >> service to be >> >> managed by puppet reliably. And because it is stopping the process, >> >> and not >> >> creating the process, it doesn't matter whether it runs as root or >> >> puppet-dashboard. >> >> >> ## (#9429) Prevent editing node name >> >> >> The uneditable node name was displayed in a text input control, >> >> which was less >> >> than ideal for a number of reasons. Now it's plain text. >> >> >> ## (#9429) makes node name field readonly during edit action >> >> >> The readonly attribute of the node name text field is set via the >> >> @readonly_name >> >> instance variable. When nil, the node name can be edited. This >> >> commit prevents >> >> the node name from being edited, though it can be set normally >> >> during node creation. >> >> >> ## (#9429) adds attr_readonly to name in the node model >> >> >> Changes to the name attribute of nodes are ignored, via the >> >> attr_readonly >> >> attribute in the model. In the view, readonly input controls are >> >> assigned >> >> a #EEE background. spec tests updated with readonly changes. >> >> >> ## (#9282) Change user in database.yml.example to "dashboard" >> >> >> Previously, our database.yml.example file suggested handing the keys >> >> to the >> >> root MySQL user to Dashboard, which is a poor security practice. This >> >> commit >> >> changes the default user suggestion to "dashboard", which is the >> >> default MySQL >> >> user used in Puppet Enterprise. >> >> >> ## (#9262) causes the contents of .section divs to scroll when >> >> overflowing >> >> >> This is a short-term solution to a larger problem. Dashboard is >> >> split into two columns, >> >> the sidebar (20% of window width), and the main content pane (80% >> >> of window width). The >> >> problem is when dealing with large strings of non-breaking text >> >> (e.g. file paths), the >> >> containing element runs off the screen unless accomodations are >> >> made (e.g. overflow: auto;). >> >> The better--long term--fix is to replace the 20%/80% column layout >> >> with one that allows >> >> the main content pane variable width. Thus, the entire window >> >> scrolls horizonally when >> >> elements overflow instead of requiring short-term fixes for each >> >> offending element. >> >> >> ## (#9215) Add a Rake task that removes nodes >> >> >> v1.2.2 >> >> === >> >> 484b323 Change node:delete to node:del for consistency >> >> 56b141c (#9215) Rename node:del to node:delete >> >> 20cf5fe (#9954) Add a rake task to add classes to a nodegroup >> >> d9eca18 (#9954) Add a rake task to list nodeclasses >> >> e75b51d (#9953) Add a rake task for listing nodegroups >> >> 14b93a2 Maint: adding VERSION_LINK to .gitignore >> >> 8725921 (#9940) dashboard-workers can be managed as service >> >> ce3868f (#9429) Prevent editing node name >> >> edbb48e (#9429) makes node name field readonly during edit action >> >> 14bc1e5 (#9429) adds attr_readonly to name in the node model >> >> a344e82 (#9366) removes conditional on .git for APP_VERSION_LINK >> >> 9ed1c19 (#9366) allows a custom version link to be specified >> >> 39a07de (#9773) Report content hidden >> >> 233fbf0 (#9756/Maint) Fix plugin loading. >> >> 54146c6 (#9756/Maint) Better guards around installed_plugins. >> >> 7b36bb3 (#9756) Autoload plugin initializers. >> >> 5311e6b (#9731) Refactor the Dashboard logo rendering. >> >> 1e4996c Maint: telling git to ignore MCollective logs >> >> 6c2e454 (#9306) tweaks base header styling to match markup changes >> >> c897d00 (#9571) tweaks header markup, method of importing CSS styles >> >> 5f381a0 (#9306) adds divs to header markup >> >> a63c1df (#9306) sanitizes header markup for assimilation by Riddler >> >> 22001cc (9571) exports global nav bar via /header.html >> >> ca7d7a5 (#9282) Rewrite explanatory text in database.yml.example >> >> 1f42a27 (#8825) allows configuration of logo dimensions and alt text >> >> 992af88 (#9262) causes the contents of .section divs to scroll when >> >> overflowing >> >> ad4641f (#9282) Change user in database.yml.example to "dashboard" >> >> 090538f (#9215) Add a Rake task that removes nodes >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Puppet Users" group. >> > To post to this group, send email to puppet-users@googlegroups.com. >> > To unsubscribe from this group, send email to >> > puppet-users+unsubscr...@googlegroups.com. >> > For more options, visit this group >> > athttp://groups.google.com/group/puppet-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
