It strange, that brp tools worked until that moment (and still works for 12.3, 12.2, etc.). This file has always been there. It is generated by the following fun bash-construction in makefile: for file in *.ctx; \ do (cd $(CTXDIR); $(LN) ../applic/$$PCK/etc/$$file $$file;) \ done And when there are no any *.ctx files in directory, the $file equals '*.ctx'. Ok, I have to fix that... 03.05.2013 11:54, Stephan Kulow пишет:

On 03.05.2013 09:42, Matwey V. Kornilov wrote:

...

Hi,

I am experiencing strange issue at science eso-midas Factory. brp-25-symlink want to relink my links in a quite strange manner. here is log:

[ 446s] INFO: relinking /opt/eso-midas/12FEBpl1.3/context/*.ctx ->

You seriusly have packaged a *.ctx file? Perhaps you should fix that first

Greetings, Stephan

-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On 05/03/2013 03:31 PM, Stephan Kulow wrote:

On 03.05.2013 15:26, Matwey V. Kornilov wrote:

...

It strange, that brp tools worked until that moment (and still works for 12.3, 12.2, etc.). This file has always been there. It is generated by

I assume there was some subtle change in coreutils and/or bash that triggered finding that bug.

I don't see a change in ln in the new coreutils package. What's the command line ln sees? ... I mean it's not a problem for ln to create such a link: $ ln -sv 'a/b/c/*.ctx' '*.ctx' '*.ctx' -> 'a/b/c/*.ctx' $ ls -ldog \*.ctx lrwxrwxrwx 1 11 May 3 16:35 *.ctx -> a/b/c/*.ctx ln (or better the kernel) even permits such a symlink to itself: $ ln -sv '*.ctx' '*.ctx' '*.ctx' -> '*.ctx' $ ls -ldog \*.ctx lrwxrwxrwx 1 5 May 3 16:38 *.ctx -> *.ctx Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On 05/03/2013 05:16 PM, Michal Kubeček wrote:

IMHO the problem rather is that now there isn't any matching file while before there was at least one.

That's strange because the original error message ln: target './/opt/eso-midas/12FEBpl1.3/context/*.ctx' is not a directory can only occur when ln is fed with multiple operands: $ ln -sv x y z ln: target `z' is not a directory Given Matwey's Makefile rule ... for file in *.ctx; \ do (cd $(CTXDIR); $(LN) ../applic/$$PCK/etc/$$file $$file;) \ done this means that there are files matching the glob *.ctx in the directory "$CTXDIR/../applic/$$PCK/etc/". But I still don't see how the *.ctx glob would result in './/opt/eso-midas/12FEBpl1.3/context/*.ctx'. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Actually, there is no problem in *.ctx link. But there are other real files.ctx in the same target directory, so the issue was that in brp, filename *.ctx was treated as blob and expanded. 03.05.2013 18:42, Bernhard Voelker пишет:

On 05/03/2013 03:31 PM, Stephan Kulow wrote:

...

On 03.05.2013 15:26, Matwey V. Kornilov wrote:

...

It strange, that brp tools worked until that moment (and still works for 12.3, 12.2, etc.). This file has always been there. It is generated by

I assume there was some subtle change in coreutils and/or bash that triggered finding that bug.

I don't see a change in ln in the new coreutils package. What's the command line ln sees? ... I mean it's not a problem for ln to create such a link:

$ ln -sv 'a/b/c/*.ctx' '*.ctx' '*.ctx' -> 'a/b/c/*.ctx'

$ ls -ldog \*.ctx lrwxrwxrwx 1 11 May 3 16:35 *.ctx -> a/b/c/*.ctx

ln (or better the kernel) even permits such a symlink to itself:

$ ln -sv '*.ctx' '*.ctx' '*.ctx' -> '*.ctx'

$ ls -ldog \*.ctx lrwxrwxrwx 1 5 May 3 16:38 *.ctx -> *.ctx

Have a nice day, Berny

-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org