On 03/26/2014 01:54 PM, Paul Gevers wrote: > On 26-03-14 18:10, David Smith wrote: >> On 03/26/2014 04:47 AM, Emilio Pozuelo Monfort wrote: >>> On 26/03/14 08:08, David Smith wrote: >>>> On 03/25/2014 03:40 PM, Emilio Pozuelo Monfort wrote: >>>>> On 25/03/14 21:31, Paul Gevers wrote: >>>>>>> So you want me to upload? This means that you consider the bug we have >>>>>>> been discussing so far as not the regression you thought it to be? >>>>>>> >>>> To be honest, I think it does have a regression starting in 1.10.7 >>>> related to etags (new feature). I made a bug report upstream about it >>>> and then I was going to contact Lars (upstream) about it but then I >>>> realized that all the etags stuff wasn't even written by Lars at all. >>>> >>>> I'm not really in a position to guess how big or little the etags crash >>>> is.. For me, it happens enough to be very annoying. >>>> >>>> The only thing 1.10.7 adds is the etags stuff so I think I should be >>>> able to just dig through that and figure out what's happening. >>>> >>>> I'm going to be contacting the etags dev for liferea and hoping that I >>>> can get a quick response. >>>> >>>> If 1.10.7 seems to be working ok for you guys then I'd say just go ahead >>>> and do the upload and I'll do an update as soon as upstream makes a >>>> patch for it. >>> I think you've been right in your concerns. If liferea crashes for you 100% >>> of >>> the time on startup, it'll probably crash the same way for a few users. >>> Since >>> this new feature is not critically needed, we could upload 1.10.6 instead >>> until >>> this crash is analyzed and fixed. >>> >>> Emilio >> 1.10.6 is packaged in git and ready for upload to unstable. > Hi David, > > First, (don't get me wrong, I only try to teach here) please read > http://www.git-scm.com/book/en/Git-Branching-Rebasing and especially the > line: > """Do not rebase commits that you have pushed to a public repository.""" > No big harm, but the current history looks slightly messy. Yeah, it didn't end up at all like I expected. On my side it looked like I was moving commits in my local branch but when it finally got to the point of pushing it into the server, it wouldn't let me push the rebase.. It said I had to do a pull first, and that ended up recalculating all the work I did and putting it after the last commit in the master branch. Needless to say the end result in the git history didn't look at all like what I had in my git log but it accomplished the same thing.
I google searched it and saw a lot of people saying to just do a rebase in my situation, but I guess I probably should have just created a branch at 1.10.5, brought in 1.10.6 and then merged in the changes from 1.10.7 I needed applied to 1.10.6 too... And left the master branch alone at 1.10.7. If I knew the git summary would look the way it does, I wouldn't have done it. > Furthermore, I saw Lars released 1.10.8 today to fix/work around you > issue. Wouldn't you rather have that version? If not, I will probably > upload tomorrow. It's not a fix for my crash, it's a fix for another crash related to hitting a scroll button before the GUI loads. Lars told me to try it anyway, and it's the next thing I'm going to do. Lars said he's looking for some help on rewriting some of the GUI so that it checks dependencies better to reduce crashes on startup. I guess if there's anybody that's really good at programming, maybe they can give upstream some help. I deal mostly with higher level languages so I'm not too experienced with C. -David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
