Re: [Libreoffice-qa] What should I do with a bug, where I got a file to test and can confirm it, but are not allowed to attach the file to the bug?
Hi Thomas, *, On Thursday, May 1, 2014, Thomas Hackert thack...@nexgo.de wrote Oh, to be clear: Just randomly mailing documents to people is not the way to go. Instead up show up on the #libreoffice-dev channel sigh ... Maybe I will find the time this weekend, and than I will try to join IRC. No need to sigh - just meant as it is just not nice to just randomly mail documents to people without asking first. That basically means I expect you to fix it, no matter how many other things you need to do and that's just not nice. IRC just is easiest medium for quick feedback regarding this - you're not forced to used IRC. [discus, disk or something else?] Ring, CD, but not discus or disk - that is misleading. And write that it is one with big radius, otherwise the screenshot in the bug doesn't make it clear what is being talked about. And no need to rewrite the comment again. It depends, how you do define easily done ... ;) They are named something like U1.E1.001.odt up to U8.E1.001.odt (not to forget a copyright and a copyright file for something else) ... :( I would not know an easy way to do this ... :( for file in *.odt; do cp -f my-one-sample.odt $i; done i.e. for each file U1 whatever, it copies (and overwrites, that's what the -f switch does) a single document, in this case my-one-sample.odt. over the file. I get an quote cp: cannot stat 'my-one-sample.odt': No such file or directory /quote here ... :( Well - that is the placeholder for the one filename you want to use. Obviously I have no idea how you name your documents / how the documents in the example are all called :-) but it might just be a drawing shape. for file in *.odt; do zipgrep 'draw:type=ring' $file /dev/null echo Ringshape in file $file; done Again, only an error message: quote bash: syntax error near unexpected token `' /quote PS: - Just use a blank line - that makes it easier to parse quickly (at least for me :-)) the lenghty quote isn't necessary. And yes, it is a copy'n'paste error. the whole commans is meant to be put on a single line. And it is meant to be run from the directory where all the odts are - otherwise the *.odt won't match anything. for file in *.odt; means get a list of all files with odt extension and run a loop with it. For each file you encounter, assign the filename to the variable file do zipgrep 'draw:type=ring' $file /dev/null echo Ringshape in file $file means: for each file, run the command zipgrep. Search for the string 'draw:type=ring' in the file named $file (that is where we reuse the variable define in the previous part), and discard the output if it matches (redirect stdout to /dev/null , that is the /dev/null part. content.xml has no linebreaks, and when the zipgrep matches, it would pint a hge line to the terminal that we're not interested in anyway. If zipgrep did find something, then output the name of the file with the echo statement. means. If the previous command returned without error, then run the second one. || would be the opposite: if the previous command returned with error (in the case of zipgrep: string wasn't found), then run the second one. ; is the third way: No matter whether previous command was successful or not, just run the second one anyway. done marks the end of the statement that should be repeated. so everything between the do and done is executed for each file. ... :( First I thought, some kind of cp errors with your commands, changed any quotation mark and inverted comma, but this does not solve the problem ... :( /me thinks, I should learn a little bit more of these Bash internals ... ;) Wouldn't hurt to know some basic shell-scripting :-)) ciao Christain ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] What should I do with a bug, where I got a file to test and can confirm it, but are not allowed to attach the file to the bug?
Hi Thomas, *, On Thursday, May 1, 2014, Thomas Hackert thack...@nexgo.dejavascript:_e(%7B%7D,'cvml','thack...@nexgo.de'); wrote Oh, to be clear: Just randomly mailing documents to people is not the way to go. Instead up show up on the #libreoffice-dev channel sigh ... Maybe I will find the time this weekend, and than I will try to join IRC. No need to sigh - just meant as it is just not nice to just randomly mail documents to people without asking first. That basically means I expect you to fix it, no matter how many other things you need to do and that's just not nice. IRC just is easiest medium for quick feedback regarding this - you're not forced to used IRC. [discus, disk or something else?] Ring, CD, but not discus or disk - that is misleading. And write that it is one with big radius, otherwise the screenshot in the bug doesn't make it clear what is being talked about. And no need to rewrite the comment again. It depends, how you do define easily done ... ;) They are named something like U1.E1.001.odt up to U8.E1.001.odt (not to forget a copyright and a copyright file for something else) ... :( I would not know an easy way to do this ... :( for file in *.odt; do cp -f my-one-sample.odt $i; done i.e. for each file U1 whatever, it copies (and overwrites, that's what the -f switch does) a single document, in this case my-one-sample.odt. over the file. I get an quote cp: cannot stat 'my-one-sample.odt': No such file or directory /quote here ... :( Well - that is the placeholder for the one filename you want to use. Obviously I have no idea how you name your documents / how the documents in the example are all called :-) but it might just be a drawing shape. for file in *.odt; do zipgrep 'draw:type=ring' $file /dev/null echo Ringshape in file $file; done Again, only an error message: quote bash: syntax error near unexpected token `' /quote PS: - Just use a blank line - that makes it easier to parse quickly (at least for me :-)) the lenghty quote isn't necessary. And yes, it is a copy'n'paste error. the whole commans is meant to be put on a single line. And it is meant to be run from the directory where all the odts are - otherwise the *.odt won't match anything. for file in *.odt; means get a list of all files with odt extension and run a loop with it. For each file you encounter, assign the filename to the variable file do zipgrep 'draw:type=ring' $file /dev/null echo Ringshape in file $file means: for each file, run the command zipgrep. Search for the string 'draw:type=ring' in the file named $file (that is where we reuse the variable define in the previous part), and discard the output if it matches (redirect stdout to /dev/null , that is the /dev/null part. content.xml has no linebreaks, and when the zipgrep matches, it would pint a hge line to the terminal that we're not interested in anyway. If zipgrep did find something, then output the name of the file with the echo statement. means. If the previous command returned without error, then run the second one. || would be the opposite: if the previous command returned with error (in the case of zipgrep: string wasn't found), then run the second one. ; is the third way: No matter whether previous command was successful or not, just run the second one anyway. done marks the end of the statement that should be repeated. so everything between the do and done is executed for each file. ... :( First I thought, some kind of cp errors with your commands, changed any quotation mark and inverted comma, but this does not solve the problem ... :( /me thinks, I should learn a little bit more of these Bash internals ... ;) Wouldn't hurt to know some basic shell-scripting :-)) ciao Christian ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] What should I do with a bug, where I got a file to test and can confirm it, but are not allowed to attach the file to the bug?
Hello Christian, *, On Fr, 2. Mai 2014 12:46 Christian Lohmaier wrote: On Thursday, May 1, 2014, Thomas Hackert thack...@nexgo.dejavascript:_e(%7B%7D,'cvml','thack...@nexgo.de'); wrote [randomly sending documents to devs] sigh ... Maybe I will find the time this weekend, and than I will try to join IRC. No need to sigh - just meant as it is just not nice to just randomly mail documents to people without asking first. That I would not mail documents randomly to our devs ;) I just wanted to find out, who of the devs is responsible for the master document code to ask him, if it is OK to send it after I have explained the problem to him ... ;) basically means I expect you to fix it, no matter how many other things you need to do and that's just not nice. He, do you really think, I am that evil ;? IRC just is easiest medium for quick feedback regarding this - you're not forced to used IRC. It depends: I remember times during bug hunting parties, where you have to wait, until someone ansered there ... :( Then again ... This is the same with mail ... ;) [discus, disk or something else?] Ring, CD, but not discus or disk - that is misleading. And write that it is one with big radius, otherwise the screenshot in the bug doesn't make it clear what is being talked about. And no need to rewrite the comment again. O.K. [How to find a string in one ODT] for file in *.odt; do cp -f my-one-sample.odt $i; done i.e. for each file U1 whatever, it copies (and overwrites, that's what the -f switch does) a single document, in this case my-one-sample.odt. over the file. I get an quote cp: cannot stat 'my-one-sample.odt': No such file or directory /quote here ... :( Well - that is the placeholder for the one filename you want to use. Obviously I have no idea how you name your documents / how the documents in the example are all called :-) But ... I understood this command that way, that it will create my- one-sample.odt, if it does not exist. And this was my intention :) I just copied your example as is to prevent any typos ... ;) Does it mean, that I have to create this file beforehand? but it might just be a drawing shape. for file in *.odt; do zipgrep 'draw:type=ring' $file /dev/null echo Ringshape in file $file; done Again, only an error message: quote bash: syntax error near unexpected token `' /quote PS: - Just use a blank line - that makes it easier to parse quickly (at least for me :-)) the lenghty quote isn't necessary. O.K. And yes, it is a copy'n'paste error. the whole commans is meant to be put on a single line. And it is meant to be run from the directory where all the odts are - otherwise the *.odt won't match anything. I had run it in the directory with all the odt files ... ;) for file in *.odt; means get a list of all files with odt extension and run a loop with it. For each file you encounter, assign the filename to the variable file O.K. do zipgrep 'draw:type=ring' $file /dev/null echo Ringshape in file $file means: for each file, run the command zipgrep. Search for the string 'draw:type=ring' in the file named $file (that is where we reuse the variable define in the previous part), and discard the output if it matches (redirect stdout to /dev/null , that is the /dev/null part. content.xml has no linebreaks, and when the zipgrep matches, it would pint a hge line to the terminal that we're not interested in anyway. If zipgrep did find something, then output the name of the file with the echo statement. Ah, O.K. means. If the previous command returned without error, then run the second one. || would be the opposite: if the previous command returned with || error (in the case of zipgrep: string wasn't found), then run the second one. ; is the third way: No matter whether previous command was successful or not, just run the second one anyway. O.K. done marks the end of the statement that should be repeated. so everything between the do and done is executed for each file. O.K. Thank you for your crash course with Bash oneliners :) ... :( First I thought, some kind of cp errors with your commands, changed any quotation mark and inverted comma, but this does not solve the problem ... :( /me thinks, I should learn a little bit more of these Bash internals ... ;) Wouldn't hurt to know some basic shell-scripting :-)) Sure :) Just need an easy to understand and fast too read guide ... ;) And one, which is not a shell scripting guide, but only an advanced luser guide ... ;) But still, if I use your example as a oneliner, I get zipinfo: cannot find or open , .zip or .ZIP. /usr/bin/zipgrep: 97: test: -eq: unexpected operator /usr/bin/zipgrep: 100: test: Illegal number: as an message ... :( Does this mean, zipgrep does not recognize ODTs as zip files? Do I have to either change all file extensions to zip instead of odt, or find some kind of file to tell zip(grep), that
Re: [Libreoffice-qa] What should I do with a bug, where I got a file to test and can confirm it, but are not allowed to attach the file to the bug?
Good morning Christian, * On Mi, 30. Apr 2014 20:28 Christian Lohmaier wrote: On Wed, Apr 30, 2014 at 6:51 PM, Thomas Hackert thack...@nexgo.de wrote: On Mi, 30. Apr 2014 13:38 Christian Lohmaier wrote: but then, who is working in the area of master documents? I found only Writer (and therefore Michael S.) ... :( Oh, to be clear: Just randomly mailing documents to people is not the way to go. Instead up show up on the #libreoffice-dev channel sigh ... Maybe I will find the time this weekend, and than I will try to join IRC. and ping the candidates and ask whether it is OK to mail them the documents/whether they know a better contact. O.K. [...] I confirm, I should have written this in a more understandable manner, sorry ... :( Yes, that were the versions, with which I could reproduce the bug. Yeah, those could have also benefitted from some linebreaks for easier quick parsing :-P O.K. Should I add an additional comment with something like quote Just to clarify 1. confirmed with a. $version b. $version $(additional info) /quote ? [discus, disk or something else?] While you speculate earlier that it is the white bar with the black outline, you write ... does not show the discus (or maybe better disc?) - I neither see something that looks like a floppy disk or harddrive, nor anything round. So what is the bug about? I assume the white bar. Well, there are also Compact Disk ... ;) That would be included in round - I didn't expect it to have such a large radius that it appears as a bar on first look in that screenshot. But from your description now it is clear that it is a donut shape, or in technical terms an annulus (Kreisring), or as it is called in LO's drawing shapes: Ring :-) http://en.wikipedia.org/wiki/Annulus_(mathematics) Ah, O.K. Thanks for your info and the link :) i.e. first replace all documents with a single one (i.e. copy one document and name it like the others) - this is easily done, but of course doesn't guarantee that the problem still shows. It depends, how you do define easily done ... ;) They are named something like U1.E1.001.odt up to U8.E1.001.odt (not to forget a copyright and a copyright file for something else) ... :( I would not know an easy way to do this ... :( for file in *.odt; do cp -f my-one-sample.odt $i; done i.e. for each file U1 whatever, it copies (and overwrites, that's what the -f switch does) a single document, in this case my-one-sample.odt. over the file. I get an quote cp: cannot stat 'my-one-sample.odt': No such file or directory /quote here ... :( → all files will be like my-one-sample.odt O.K. but it might just be a drawing shape. for file in *.odt; do zipgrep 'draw:type=ring' $file /dev/null echo Ringshape in file $file; done Again, only an error message: quote bash: syntax error near unexpected token `' /quote ... :( First I thought, some kind of cp errors with your commands, changed any quotation mark and inverted comma, but this does not solve the problem ... :( /me thinks, I should learn a little bit more of these Bash internals ... ;) Then examine the file in LibreOffice. If that doesn't match anything, try to search for more draw shapes (draw:custom-shape) When I find a solution to get these commands ... ;) Thank you for your answer and have a nice day Thomas. -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] What should I do with a bug, where I got a file to test and can confirm it, but are not allowed to attach the file to the bug?
Hi, Did you ask him to create a test document himself? You were unable to reproduce it without the test doc? Does it work with plain (or close to) documents and with a reduced number? If you could not reproduce it without and he does not provide a testcase, it might be a bit sharp, but invalid might still be the right. Leaving that aside, if it works with the limited set, please attach it and set out to new. .. Just my thoughts, but you asked for those. Sorry for TOFU -- Liebe Grüße, / Yours, Florian Reisinger On 30. April 2014 08:41:09 MESZ, Jochen Schiffers oo...@jochenschiffers.de wrote: Hi Thomas, what do you mean: share the documents on our cloud and set a link to the folder? Or do I misunterstand yor question? reg Jochen Am 29.04.2014 18:59, schrieb Thomas Hackert: Hello @ll, I stumbled upon bug #77330 (https://bugs.freedesktop.org/show_bug.cgi?id=77330), when doing a little bit QA last weekend. After I added comment #1 (https://bugs.freedesktop.org/show_bug.cgi?id=77330#c1) and set the status to NEEDINFO, the reporter sent me a private mail with an attached zipped file, containing the master document and its subdocuments. He asked me not to attach it to the bug. Now I am not sure, what I should do with this bug ... :( I had searched at https://wiki.documentfoundation.org/FindTheExpert to find out, if I could find a dev, to whom I could send this zipped files, but I am not sure, if this is right way. As I can partly confirm this bug, I have added my comment to the bug (https://bugs.freedesktop.org/show_bug.cgi?id=77330#c2). And now? As I am not a dev, I will not be able to fix it ... :( The master document in question depends on 100 ODT files with pictures and the like, so it would be hard to create one master document with that amount of ODTs (or better say: I would not have the time for it the next months) ... :( Thanks for any insights Thomas. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/ ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] What should I do with a bug, where I got a file to test and can confirm it, but are not allowed to attach the file to the bug?
Hello Christian, *, On Mi, 30. Apr 2014 13:38 Christian Lohmaier wrote: On Tue, Apr 29, 2014 at 6:59 PM, Thomas Hackert thack...@nexgo.de wrote: I stumbled upon bug #77330 (https://bugs.freedesktop.org/show_bug.cgi?id=77330), I had searched at https://wiki.documentfoundation.org/FindTheExpert to find out, if I could find a dev, to whom I could send this zipped files, This is more or less the only way in such a case, when the sample should not be made public for whatever reason. but then, who is working in the area of master documents? I found only Writer (and therefore Michael S.) ... :( but I am not sure, if this is right way. As I can partly confirm this bug, I have added my comment to the bug (https://bugs.freedesktop.org/show_bug.cgi?id=77330#c2). That comment is written in a rather unclear fashion. It misses what a) actually refers to. From context one can guess that those are the versions that you can reproduce with. I confirm, I should have written this in a more understandable manner, sorry ... :( Yes, that were the versions, with which I could reproduce the bug. And also still unclear what discus is, as in the crippled screenshot I cannot see anything that resembles a disc/round object/discus. I am still not sure, how I should name it, as this discus (as Ton has named it) stretches over several sides, so if I look at it, it seems to form a disc (like the outer part of an CD). And circle does not seem to fit here as well ... :( While you speculate earlier that it is the white bar with the black outline, you write ... does not show the discus (or maybe better disc?) - I neither see something that looks like a floppy disk or harddrive, nor anything round. So what is the bug about? I assume the white bar. Well, there are also Compact Disk ... ;) I have looked for a better word, but alas was not able to find one ... :( As written above, this white (pitch or graduated?) circle on the screenshot spans over the following sides, so it seems to form a whole circle. But if you use either a larger display and a smaller zoom factor than 50 or 100%, this effect does not show (that is, what Ton told me). I cannot confirm it, as I have only my 10 netbook here ... :( And now? As I am not a dev, I will not be able to fix it ... :( The master document in question depends on 100 ODT files with pictures and the like, so it would be hard to create one master document with that amount of ODTs (or better say: I would not have the time for it the next months) ... :( The crux is not to create a new set of documents, but to trim down the existing ones to show the problem. O.K. i.e. first replace all documents with a single one (i.e. copy one document and name it like the others) - this is easily done, but of course doesn't guarantee that the problem still shows. It depends, how you do define easily done ... ;) They are named something like U1.E1.001.odt up to U8.E1.001.odt (not to forget a copyright and a copyright file for something else) ... :( I would not know an easy way to do this ... :( But if it does still show, then that does already help a lot. Hm. Maybe I will have the time the next days, but I cannot give such undertaking, sorry ... :( Thanks for your answer Thomas. -- To every Ph.D. there is an equal and opposite Ph.D. -- B. Duggan ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] What should I do with a bug, where I got a file to test and can confirm it, but are not allowed to attach the file to the bug?
Hello Jochen, *, On Mi, 30. Apr 2014 08:41 Jochen Schiffers wrote: what do you mean: share the documents on our cloud and set a link to the folder? Or do I misunterstand yor question? yes. I am not allowed to give it to the public (= attach to a bug). So I think, to put it in the cloud is not a good idea ... :( Have a nice evening Thomas Fullquote removed -- Yow! Is my fallout shelter termite proof? ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] What should I do with a bug, where I got a file to test and can confirm it, but are not allowed to attach the file to the bug?
Hi Thomas, *, On Wed, Apr 30, 2014 at 6:51 PM, Thomas Hackert thack...@nexgo.de wrote: Hello Christian, *, On Mi, 30. Apr 2014 13:38 Christian Lohmaier wrote: but then, who is working in the area of master documents? I found only Writer (and therefore Michael S.) ... :( Oh, to be clear: Just randomly mailing documents to people is not the way to go. Instead up show up on the #libreoffice-dev channel and ping the candidates and ask whether it is OK to mail them the documents/whether they know a better contact. [...] I confirm, I should have written this in a more understandable manner, sorry ... :( Yes, that were the versions, with which I could reproduce the bug. Yeah, those could have also benefitted from some linebreaks for easier quick parsing :-P And also still unclear what discus is, as in the crippled screenshot I cannot see anything that resembles a disc/round object/discus. I am still not sure, how I should name it, as this discus (as Ton has named it) stretches over several sides, so if I look at it, it seems to form a disc (like the outer part of an CD). And circle does not seem to fit here as well ... :( While you speculate earlier that it is the white bar with the black outline, you write ... does not show the discus (or maybe better disc?) - I neither see something that looks like a floppy disk or harddrive, nor anything round. So what is the bug about? I assume the white bar. Well, there are also Compact Disk ... ;) That would be included in round - I didn't expect it to have such a large radius that it appears as a bar on first look in that screenshot. But from your description now it is clear that it is a donut shape, or in technical terms an annulus (Kreisring), or as it is called in LO's drawing shapes: Ring :-) http://en.wikipedia.org/wiki/Annulus_(mathematics) i.e. first replace all documents with a single one (i.e. copy one document and name it like the others) - this is easily done, but of course doesn't guarantee that the problem still shows. It depends, how you do define easily done ... ;) They are named something like U1.E1.001.odt up to U8.E1.001.odt (not to forget a copyright and a copyright file for something else) ... :( I would not know an easy way to do this ... :( for file in *.odt; do cp -f my-one-sample.odt $i; done i.e. for each file U1 whatever, it copies (and overwrites, that's what the -f switch does) a single document, in this case my-one-sample.odt. over the file. → all files will be like my-one-sample.odt but it might just be a drawing shape. for file in *.odt; do zipgrep 'draw:type=ring' $file /dev/null echo Ringshape in file $file; done Then examine the file in LibreOffice. If that doesn't match anything, try to search for more draw shapes (draw:custom-shape) ciao Christian ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
