[Qgis-user] Is there smth wrong with OSGEO4W installer?

[Etienne Tourigny]

On Tue, Nov 6, 2012 at 3:35 PM, Bernd Vogelgesang
<bernd.vogelgesang at gmx.de> wrote:
> ahh, life is not easy ;)
>
> so, there were already tickets to that stuff it seems, and also mailing list
> entries.
> But there seems to be a problem with me or the hole system, that i was not
> able to find them AND draw conclusions.
>
> 1. You have to know what to search for when qgis simply crashes silently ...
> plop!
> 2. The amount of entries in both the tracker and the mailing list
>
> "Ordinary" users have really no chance digging through all this tech-talk,
> but have a corrupted system anyway.
> But i have no real idea how to solve this myself.
> Maybe having by a system, where messages can easily be flagged by users for
> "importance", so when a thread starts "Hey hello, this update will kill qgis
> if you do not set this animal to this version and that beast to that" its
> likely that this message will be washed up, even if only few people have sth
> to contribute as reply .. i mean, simply that "modern" stuff that is
> available out there ...
> will spend some time thinking on this ... :)

There can be no such system, when bugs are yet unknown.

>
> @Ramon:
>
>> Out of curiousity, does the slightly out of sync mrsid gdal plugin stop
>> you using/viewing mrsid files?
>> I'm still able to open the ecw files that I have to deal with.
>>
> well, no, there was nothing to view, cause qgis crashed when i loaded that
> project with the mrsid, same as  when i tried to just load a single mrsid to
> an empty project.
>
> Am 06.11.2012, 15:47 Uhr, schrieb Ramon Andiñach <custard at westnet.com.au>:
>
>
>>
>> On 06/11/2012, at 19:25 , Bernd Vogelgesang wrote:
>>
>>>> Are the bug trackers stoneage to you, too?  You could have found a clue
>>>> there.
>>>> Or even filed a ticket, if you happen to hit that problem first.  We
>>>> first need
>>>> to know that there is a problem, before we can do something about it.
>>>
>>>
>>> "Normally", there are signs of a bug indicated by a thread on the mailing
>>> list, but i couldn't find a trace of that. I indeed had a look at the bug
>>> tracker, but obviously missed that one about the grass plugin.
>>>
>>> I think it would be counter productive to open a bug on each problem
>>> users encounter. I for myself see this as the last step when no other
>>> solution can be found. thats why i first started the thread here.
>>
>>
>>
>> Well, as another user not yet up to the postgis stage, the gdal bug was
>> here:
>>  http://lists.osgeo.org/pipermail/qgis-user/2012-October/019792.html
>> and this problem with GRASS was (to me) clearly similar:
>> http://lists.osgeo.org/pipermail/qgis-user/2012-October/019943.html
>>
>> Still, mostly sorted now.
>>
>> I'm not sure if this is standard practice, but usually I'll ask here if I
>> think I have a bug. 9 times out of 10 I've done something stupid to provoke
>> it. When someone does confirm it, then I'll log the bug.
>>
>> Out of curiousity, does the slightly out of sync mrsid gdal plugin stop
>> you using/viewing mrsid files?
>> I'm still able to open the ecw files that I have to deal with.
>>
>> -ramon.
>
>
>
> --
> Bernd Vogelgesang * Siedlerstrasse 2 * 91083 Baiersdorf * +49-9133-825374
> _______________________________________________
> Qgis-user mailing list
> Qgis-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-user