Hello, you are right I seem to have ended up with a mixed stable/unstable
system.
In fact if I:
$ apt-show-versions | grep unstable | wc -l
I get 303 packages. I must have installed something from unstable and it
pulled a lot of dependencies in.
I will revert to stable with a high priority for stable packages in
/etc/apt/preferences/.
Thanks for pointing this out.
It is still worth it to push this bug report upstream to poedit. I will do
so.
Thanks for your time,
Borislav.
On Tue, Apr 28, 2015 at 12:12 AM, Andreas Ronnquist <mailingli...@gusnan.se>
wrote:
> On Mon, 27 Apr 2015 23:25:18 +0300,
> Борислав Събев<borislavsa...@gmail.com> wrote:
>
> >Hello all.
> >
> >I just saw the bug's resolution.
> >OK if it is fixed it is fine with me.
> >
> >Any idea when will the updated code be available for download?
> >Will it come in 8.1 or is it doing to be a regular source update.
> >
>
> Hi
>
> You reported the bug against the poedit version 1.7.6-1, which isn't
> available in Debian stable - Theres only 1.6.10-2 in current stable
> (with codename Jessie), and in that version your segfault bug isn't
> present.
>
> In unstable (Sid) though, 1.7.6-1 was available when you reported the
> bug, which is the one you reported against (and it is there the fix has
> been uploaded too).
>
> So, you cannot have installed poedit 1.7.6-1 if you are running a pure
> stable (Jessie) system.
>
> This makes me have no idea on what version of Debian you are running,
> maybe a mix of stable and unstable (which _never_ should be done).
>
> Since Jessie is stable, hardly any new updates will not get into that
> release (other than security fixes). I do have plans to make a backport
> of the 1.7.5 when it comes to testing, but I haven't tested if it
> builds on stable, so I am not sure if that works. (It's one of the rules
> of backports to wait for the unstable version to get to testing before
> backporting it to stable).
>
> /Andreas Rönnquist
> gus...@debian.org
> mailingli...@gusnan.se
>
--
* Best Regards,Borislav Sabev.*
