Georg Faerber:
> Hi all,
>
> I've just uploaded 0.8.0-1 to unstable, which ships .epub support as
> requested by some people and the patch to make the Nautilus extension
> work. It should migrate on March 10 or the day after.
>
> On 19-02-26 11:31:21, Jonas Meurer wrote:
>> After I slept a night
Hi all,
I've just uploaded 0.8.0-1 to unstable, which ships .epub support as
requested by some people and the patch to make the Nautilus extension
work. It should migrate on March 10 or the day after.
On 19-02-26 11:31:21, Jonas Meurer wrote:
> After I slept a night over it, I realized that this
Hi all,
Georg Faerber:
> On 19-02-22 23:26:45, Jonas Meurer wrote:
>> I skimmed through the patch and it looks good to me. I also did some
>> rough testing and at least with my test files it worked as expected.
>>
>> I merged jvoisin's changes into the d/0.7.0-2 branch.
>
> Thanks a lot for your
Hi all,
On 19-02-22 23:26:45, Jonas Meurer wrote:
> I skimmed through the patch and it looks good to me. I also did some
> rough testing and at least with my test files it worked as expected.
>
> I merged jvoisin's changes into the d/0.7.0-2 branch.
Thanks a lot for your inputs, reviews and chan
jvoisin:
>> On 19-02-12 14:39:32, Georg Faerber wrote:
>>> That is: option one of the second proposal ("quickly patch together a
>>> Python 2 Nautilus extension that wraps mat2's CLI").
>>
>> Unfortunately, and sorry again for my delay working on this, there was
>> no feedback. I've poked Jonas tod
> On 19-02-12 14:39:32, Georg Faerber wrote:
>> That is: option one of the second proposal ("quickly patch together a
>> Python 2 Nautilus extension that wraps mat2's CLI").
>
> Unfortunately, and sorry again for my delay working on this, there was
> no feedback. I've poked Jonas today on IRC priv
Hi all,
(Cc:ing all the people who took part in this issue, and also Julien as
the upstream author.)
On 19-02-12 14:39:32, Georg Faerber wrote:
> That is: option one of the second proposal ("quickly patch together a
> Python 2 Nautilus extension that wraps mat2's CLI").
Unfortunately, and sorry
Hi,
On 19-02-12 14:33:31, Georg Faerber wrote:
> On 19-01-27 22:44:24, intrigeri wrote:
> > Other data points & ideas:
> >
> > - Given the python-nautilus issue essentially requires a transition,
> >I doubt we'll find some way to provide desktop integration for mat2
> >via buster-backpor
Hi,
On 19-01-27 22:44:24, intrigeri wrote:
> To me this boils down to this question: do we feel more comfortable
> with:
>
> a) including mat v1 in Buster (so less technical can use its GUI,
> even though its Nautilus extension was broken last time I tried),
> in addition to v2
>
> o
Hi,
On 19-01-31 14:46:55, Georg Faerber wrote:
> I'll tacke this, although I might need support and of course, at least
> one review.
Unfortunately, this didn't worked out, as my whole time got consumed by
Schleuder. :( Sorry for this.
Cheers,
Georg
signature.asc
Description: Digital signature
Hi,
On 19-01-31 18:28:02, Jonas Meurer wrote:
> Georg Faerber:
> > I'll tacke this, although I might need support and of course, at least
> > one review.
>
> Wow, that would be awesome. I think I would be up for a review.
Great! :)
> Jeremy said this to me when we privately discussed the topic
Hey Georg!
Georg Faerber:
>> There's still a chance to get it in: if we craft a patch for
>> nautilus-python that introduces a new package python3-nautilus which
>> is co-installable (and doesn't conflict) with python-nautilus, then
>> the nautilus-python maintainer already said that he would cons
Hi all,
Sorry for my late reply, I just returned from traveling six weeks
without my PC.
On 19-01-29 00:16:55, Jonas Meurer wrote:
> thanks for picking up the discussion about mat/mat2 in Buster!
Seconded, thanks a lot.
> There's still a chance to get it in: if we craft a patch for
> nautilus-p
Hi intrigeri,
thanks for picking up the discussion about mat/mat2 in Buster!
intrigeri:
> Daniel Kahn Gillmor:
>> On Sun 2018-10-07 10:31:13 +0200, intrigeri wrote:
>>> intrigeri:
What matters to me is the users' perspective. I think we should
provide a clear, unambiguous transition pat
Hi,
Daniel Kahn Gillmor:
> On Sun 2018-10-07 10:31:13 +0200, intrigeri wrote:
>> intrigeri:
>>> What matters to me is the users' perspective. I think we should
>>> provide a clear, unambiguous transition path and avoid leaking
>>> technical details to users. So once MAT2 reaches feature parity wit
On Sun 2018-10-07 10:31:13 +0200, intrigeri wrote:
> intrigeri:
>> What matters to me is the users' perspective. I think we should
>> provide a clear, unambiguous transition path and avoid leaking
>> technical details to users. So once MAT2 reaches feature parity with
>> MAT (I think the only real
Hi intrigeri,
Am 07.10.2018 um 10:31 schrieb intrigeri:
> let's discuss how we'll be handling the transition from MAT to MAT2
> in Buster. My goal here is to avoid users keeping using the
> deprecated, unmaintained MAT v1, and to nicely transition them to the
> new MAT2 implementation.
Full ack.
Package: mat2
Version: 0.4.0-1
Severity: normal
Hi,
let's discuss how we'll be handling the transition from MAT to MAT2
in Buster. My goal here is to avoid users keeping using the
deprecated, unmaintained MAT v1, and to nicely transition them to the
new MAT2 implementation.
As I wrote on the ITP
18 matches
Mail list logo
