Bug#885677: liblablgtksourceview2-ocaml: Depends on unmaintained gtksourceview2

2020-04-04 Thread Thomas Leonard
On Sat, 4 Apr 2020 at 13:01, Ralf Treinen  wrote:
>
> Hello,
>
> On Fri, Apr 03, 2020 at 07:22:41AM +0200, Stéphane Glondu wrote:
> > Le 02/04/2020 à 22:23, Thomas Leonard a écrit :
> > > My package (https://tracker.debian.org/pkg/zeroinstall-injector)
> > > depends on lablgtk2 and the tracker says it will be removed on 4th Apr
> > > due to this issue.
>
> that is, removed from testing.
>
> > > I can't upgrade to lablgtk3 because Debian/unstable only has an old
> > > beta release of that (3.0~beta6-2), which is missing some functions.
> >
> > There is 3.1.0 in experimental. Does it suit your needs?

Yes, 3.1.0 works fine with 0install.

> > Ralf, what are your plans concerning lablgtk3?
>
> The only blocker for an upload of 3.1 is that the current version
> of why3 was not compiling with lablgtk3.1. Now, there is a new
> version of why3, which does, but there are a few issues with it
> that I wanted to resolve before uploading the new why3 and lablgtk 3.1
> to sid. Some more urgent issues with other packages took the
> priority in the meantime. Now it is a bit late, as April 4 is tomorrow.
>
> Would it really be a big problem when zeroinstall-injector temporarilly
> drops out of testing?
>
> > Just wait. Either lablgtk2 leaves testing and I will fix it quickly and
> > it (and its reverse dependencies such as your package) will migrate back
> > to testing. Or lablgtk3 will be updated.

OK, I'll wait a few days and see what happens then.

Thanks,


-- 
talex5 (GitHub/Twitter)http://roscidus.com/blog/
GPG: 5DD5 8D70 899C 454A 966D  6A51 7513 3C8F 94F6 E0CC



Bug#885677: liblablgtksourceview2-ocaml: Depends on unmaintained gtksourceview2

2020-04-03 Thread Ralf Treinen
Hello,

On Fri, Apr 03, 2020 at 07:22:41AM +0200, Stéphane Glondu wrote:
> Le 02/04/2020 à 22:23, Thomas Leonard a écrit :
> > My package (https://tracker.debian.org/pkg/zeroinstall-injector)
> > depends on lablgtk2 and the tracker says it will be removed on 4th Apr
> > due to this issue.

that is, removed from testing.

> > I can't upgrade to lablgtk3 because Debian/unstable only has an old
> > beta release of that (3.0~beta6-2), which is missing some functions.
> 
> There is 3.1.0 in experimental. Does it suit your needs?
> 
> Ralf, what are your plans concerning lablgtk3?

The only blocker for an upload of 3.1 is that the current version
of why3 was not compiling with lablgtk3.1. Now, there is a new
version of why3, which does, but there are a few issues with it
that I wanted to resolve before uploading the new why3 and lablgtk 3.1
to sid. Some more urgent issues with other packages took the
priority in the meantime. Now it is a bit late, as April 4 is tomorrow.

Would it really be a big problem when zeroinstall-injector temporarilly
drops out of testing? 

> Just wait. Either lablgtk2 leaves testing and I will fix it quickly and
> it (and its reverse dependencies such as your package) will migrate back
> to testing. Or lablgtk3 will be updated.

I hope to be able to work on the why3/lablgtk3 issue next week.

-Ralf.



Bug#885677: liblablgtksourceview2-ocaml: Depends on unmaintained gtksourceview2

2020-04-02 Thread Stéphane Glondu
Le 02/04/2020 à 22:23, Thomas Leonard a écrit :
> My package (https://tracker.debian.org/pkg/zeroinstall-injector)
> depends on lablgtk2 and the tracker says it will be removed on 4th Apr
> due to this issue.
> 
> I can't upgrade to lablgtk3 because Debian/unstable only has an old
> beta release of that (3.0~beta6-2), which is missing some functions.

There is 3.1.0 in experimental. Does it suit your needs?

Ralf, what are your plans concerning lablgtk3?

> I'm not using the gtksourceview2 part, so dropping that would be OK for me.

I am planning to disable the gtksourceview2 part of lablgtk2 when
lablgtk2 effectively leaves testing. I am waiting, because I already
disabled it once, and gtksourceview2 maintainers changed their mind, and
I had to re-enable it. I don't want to disable/enable it again so I want
to be sure that gtksourceview2 has effectively left testing before doing it.

> What do you recommend?

Just wait. Either lablgtk2 leaves testing and I will fix it quickly and
it (and its reverse dependencies such as your package) will migrate back
to testing. Or lablgtk3 will be updated.


Cheers,

-- 
Stéphane



Bug#885677: liblablgtksourceview2-ocaml: Depends on unmaintained gtksourceview2

2020-04-02 Thread Thomas Leonard
Hi,

My package (https://tracker.debian.org/pkg/zeroinstall-injector)
depends on lablgtk2 and the tracker says it will be removed on 4th Apr
due to this issue.

I can't upgrade to lablgtk3 because Debian/unstable only has an old
beta release of that (3.0~beta6-2), which is missing some functions.

I'm not using the gtksourceview2 part, so dropping that would be OK for me.

What do you recommend?

Thanks,


-- 
talex5 (GitHub/Twitter)http://roscidus.com/blog/
GPG: 5DD5 8D70 899C 454A 966D  6A51 7513 3C8F 94F6 E0CC



Bug#885677: liblablgtksourceview2-ocaml: Depends on unmaintained gtksourceview2

2019-02-13 Thread Stéphane Glondu
Control: tag -1 - pending
Control: severity -1 important

Le 14/12/2018 à 23:52, Jeremy Bicha a écrit :
> gtksourceview2 will be included in Debian 10 "Buster" but we will try
> to remove it early in the Bullseye series. [1]
> 
> Therefore, I suggest bringing that package back, then you can lower
> the severity of this bug to Important. We'll have to figure something
> out for Bullseye.

I've just uploaded lablgtk2 with its gtksourceview2 component back in.


Cheers,

-- 
Stéphane



Bug#885677: liblablgtksourceview2-ocaml: Depends on unmaintained gtksourceview2

2018-12-14 Thread Jeremy Bicha
Control: reopen -1

You can't drop liblablgtksourceview2-ocaml-dev as long as stuff still
depends and build-depends on it.

coq
lablgtk-extra
laby
marionnet

gtksourceview2 will be included in Debian 10 "Buster" but we will try
to remove it early in the Bullseye series. [1]

Therefore, I suggest bringing that package back, then you can lower
the severity of this bug to Important. We'll have to figure something
out for Bullseye.

[1] https://lists.debian.org/debian-devel/2018/11/msg00570.html

Thanks,
Jeremy Bicha