Hello,

* Jayen Ashar <[email protected]> [2012-09-29 20:18-0400]:
> Package: puppet
> Version: 0.24.7-1
> Severity: normal
> 
> from my pp file:
>     file {
>         "/etc/cups":
>             source => "puppet:///files/staff/etc/cups",
>             recurse => inf;
>     }
> 
> from puppet:///files/staff/etc/cups/ppd:
> -rw-r--r-- 1 lp   lp   146989 2009-02-19 10:05 km-c451.clr.ppd
> -rw-r--r-- 1 lp   lp   146989 2009-02-19 10:12 km-c451.bw.ppd
> lrwxrwxrwx 1 root root     15 2009-02-19 10:13 prtom.clr.ppd -> 
> km-c451.clr.ppd
> lrwxrwxrwx 1 root root     14 2009-02-19 10:13 prtom.ppd -> km-c451.bw.ppd
> 
> on the puppet client, in /etc/cups/ppd:
> lrwxrwxrwx 1 root root     15 2008-12-05 22:06 prtom.ppd -> lex-c762.bw.ppd
> lrwxrwxrwx 1 root root     15 2009-02-19 09:52 prtom.clr.ppd -> 
> km-c451.clr.ppd
> -rw-r--r-- 1 lp   lp   146989 2009-02-19 10:05 km-c451.clr.ppd
> -rw-r--r-- 1 lp   lp   146989 2009-02-19 10:14 km-c451.bw.ppd
> 
> it appears to ignore the update to prtom.ppd.

I'm sorry that there has been no resolution for this bug. It was tagged
upstream some time ago, but that upstream tag didn't include a specific URL to
the upstream bug.

However, you reported this issue when you were running 0.24 and I know that
there were many symlink related bugs that were fixed since then.

Is it possible for you to test this to see if it occurs in a newer version of
puppet and report back to the bug your results (and let me know what version
you tried)?

Thanks,
micah

Attachment: signature.asc
Description: Digital signature

Reply via email to