this is master version... It has rough edges and there is no emergency to
fix the bug since this is an unreleased version.
If the fix is a simple one-line fix it's simpler to just wait for it than
to do the "revert, correct, resubmit" dance.
the point is : we know about this bug, it is indeed a serious bug and it
will be fixed before 1.6. If you use
master you are supposed to be aware of the risk, which might include such
things as
* darktable being unusable for a couple of days because of systematic
crash... just when you have an important job with your client
* darktable refusing to open your processed RAW image because some iop has
changed its format multiple time during developement and we only guarentee
backward compatibility with stable releases (for example, we have reverted
deflicker, which might break some XMP that were developed with 1.5)
* having to regularly destroy and recreate your library, loosing all your
presets in the process
* loosing your images because there is a but in whatever code moves images
around (local copy, moving images, getting images via gphoto when we used
to do that... I'm not saying that this is the case but since we DO move
files around it's always possible that we screw up stuff)
Let me be clear it's not that we don't care about our git-users, we care
about them a lot, they are the ones in the frontlines finding the bugs
before they bite our normal users, but we assume that :
* they have SOLID backups
* they have procedures to work with another version of DT if git is
completely unusable
* they know how to ask for help/revert to an older version of git if things
break
* they can cope with the occasional usability breakage until we fix them...
On Tue, Oct 21, 2014 at 2:12 AM, Patrick Shanahan <p...@opensuse.org> wrote:
> * Roman Lebedev <lebedev...@gmail.com> [10-20-14 16:26]:
> > Hello.
> >
> > I did a git bisect, and apparently it is a regression introduced by
> > https://github.com/darktable-org/darktable/pull/699
> >
> > So we are aware of this issue[s], and if it will not be fixed in next 7
> > days, that PR will be reverted.
> >
> > On Tue, Oct 21, 2014 at 12:15 AM, KOVÁCS István <k...@kovacs-telekes.org
> >
> > wrote:
> >
> > > Now exposure started losing its settings. They remain effective until
> > > you open exposure again, when everything is shown as 0 adjustment, and
> > > the effect is removed.
> > >
> > > On 20 October 2014 02:27, Patrick Shanahan <p...@opensuse.org> wrote:
> > > > * Patrick Shanahan <p...@opensuse.org> [10-19-14 20:09]:
> > > >> * Patrick Shanahan <p...@opensuse.org> [10-19-14 17:23]:
> > > >> > * Colin Adams <colinpaulad...@gmail.com> [10-19-14 16:59]:
> > > >> [...]
> > > >> > > > If I crop a landscape image into portrait mode and leave that
> > > photo, when
> > > >> > > > I return to make more adjustments and enable the crop mode,
> the
> > > entire
> > > >> > > > image (before previous crop) is presented in "landscape" mode
> > > rather than
> > > >> > > > returning to the previous selection/edit. Very unsettling.
> > > >> > > >
> > > >> > > > Any image I crop, if I return to that image and select the
> crop
> > > mode, the
> > > >> > > > crop returns to full original image selection as if I had not
> > > made a
> > > >> > > > previous selection. Appears all other modes are maintained at
> > > the last
> > > >> > > > setting chosen, only the crop/rotation is reset.
> > > >> > > >
> > > >> > > > Is this related to my darktablerc or do I have something else
> > > amiss in my
> > > >> > > > system?
> > > >> > > >
> > > >> > > > openSUSE-Factory (up-to-date)
> > > >> > > > darktable-1.5.1413735191.818dedb
> > > >> > > > Nvidia 340.32
> > > >> > > >
> > > >> > > > More tests, bug report, ????
> > > >>
> > > >> You not only loose crop, rotation disappears. wtf?
> > > >>
> > > >> darktable-1.5.1413735191.818dedb
> > > >
> > > > If I rotate the image either direction using the shortcut settings,
> > > > preferences ->
> > > > shortcuts ->
> > > > image operations ->
> > > > crop and rotate ->
> > > > edit -> set the edit
> > > >
> > > > rotate either direction resets the crop area to entire image
> > > > reactivating the crop-rotate module resets the crop area to entire
> > > image
> > > >
> > > > if I first rotate the image using the shortcuts, then activate the
> > > > crop-rotate module, the rotation is reset to 0.
> > > >
> > > > --
> > > > (paka)Patrick Shanahan Plainfield, Indiana, USA
> > > @ptilopteri
> > > > http://en.opensuse.org openSUSE Community Member
> > > facebook/ptilopteri
> > > > http://wahoo.no-ip.org Photo Album:
> > > http://wahoo.no-ip.org/gallery2
> > > > Registered Linux User #207535 @
> > > http://linuxcounter.net
> > > >
> > > >
> > >
> ------------------------------------------------------------------------------
> > > > Comprehensive Server Monitoring with Site24x7.
> > > > Monitor 10 servers for $9/Month.
> > > > Get alerted through email, SMS, voice calls or mobile push
> notifications.
> > > > Take corrective actions from your mobile device.
> > > > http://p.sf.net/sfu/Zoho
> > > > _______________________________________________
> > > > darktable-devel mailing list
> > > > darktable-devel@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/darktable-devel
> > >
> > >
> > >
> ------------------------------------------------------------------------------
> > > Comprehensive Server Monitoring with Site24x7.
> > > Monitor 10 servers for $9/Month.
> > > Get alerted through email, SMS, voice calls or mobile push
> notifications.
> > > Take corrective actions from your mobile device.
> > > http://p.sf.net/sfu/Zoho
> > > _______________________________________________
> > > darktable-devel mailing list
> > > darktable-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/darktable-devel
> > >
>
> >
> ------------------------------------------------------------------------------
> > Comprehensive Server Monitoring with Site24x7.
> > Monitor 10 servers for $9/Month.
> > Get alerted through email, SMS, voice calls or mobile push notifications.
> > Take corrective actions from your mobile device.
> > http://p.sf.net/sfu/Zoho
>
> > _______________________________________________
> > darktable-devel mailing list
> > darktable-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/darktable-devel
>
>
> Well, it is causing me a considerable amount of concern/difficulty right
> now. Why not revert the PR and resubmit *it* in a correct[ed] version?
>
> tks,
> --
> (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri
> http://en.opensuse.org openSUSE Community Member facebook/ptilopteri
> http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2
> Registered Linux User #207535 @ http://linuxcounter.net
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> darktable-devel mailing list
> darktable-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/darktable-devel
>
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel
