Hi Andreas, On Sun, Dec 31, 2017 at 07:53:59PM +0100, Andreas Henriksson wrote: > Control: severity -1 serious > > Hello Tomasz Buchert, > > Thanks for your followup. > > On Sun, Jul 16, 2017 at 09:31:57AM +0200, Tomasz Buchert wrote: > > Hi Laurent, > > verbiste depends on libgnomeui-2.0 which then depends on gnome-vfs. > > Right, and both of these are deprecated and set for removal. > > > The package does not build anymore if I remove the libgnomeui > > As Laurent already pointed out you'll need to do (trivial) > code changes as well. > > > dependency, but if in the process of your transition you are going to > > fix deps of libgnomeui, then this package will profit too. > > Maybe I'm misinterpretting you here, but sounds like you don't > actually want to maintain this package? If so please replace > your name with Debian QA in the Maintainer field so others can > work on this package. > > Anyway, since you atleast replied it was some kind of indication that > the package isn't completely abandoned and I've thus looked into helping > you out fixing the issue. I see multiple ways to accomplish that so > please help me out answering the following questions.
I use this package regularly (so much faster than flipping through the Bescherelle!) and just noticed that it was removed from testing—when I checked to see if verbiste-el had yet been converted to use dh-elpa. I'm a DM primarily active on the Emacsen Team. With six months without a reply to this bug, how do we procede? > What is the point of building both a gtk and a gnome version? > Porting the gnome version would mean replacing libgnome* usage with pure > gtk+ usage, basically providing 2 gtk versions which seems kind of > pointless to me. Maybe we should instead just drop the verbiste-gnome > package and provide a transitional package that pulls in the > verbiste(-gtk) package (and have that provide /usr/bin/verbiste). Then > you can (optionally) work with your upstream to improve the gtk > version.... For example the function to provide a default icon > is available as gtk_window_set_default_icon_from_file(...) and > you could chose to migrate ~/.gnome2/verbiste to either dconf/gsettings > or just continue using it as is eg. by opening it via libinih(-dev) or > similar. I haven't looked at the src:package yet, but is the gtk+ version packaged? Bin:verbiste provides /usr/bin/french-conjugator /usr/bin/french-deconjugator and a gui seems to be provided exclusively by bin:verbiste-gnome. Or is this just a case of ./configure --enable-gnome vs --disable-gnome? > Btw, while looking at this I noticed there are missing > build-dependencies (which is a policy violation of its own). > You don't declare libgtk2.0-dev and/or libxml2-dev as build- > dependencies but configure explicitly/unconditionally checks for these > and bails out if missing. (I figured we'll fix this while at it > so didn't bother filing a separate bug report for this.) > > The removal of the deprecated libraries are upon us now, so looking > to hear from you ASAP if we're going to work this out before > verbiste is removed together with the rest of the unmaintained/abandoned > packages. Worst-case scenario, if the maintainer is MIA and/or this package is abandoned, I'd like to retain bin:verbiste, bin:verbiste-el (converted to use dh-elpa), and introduce bin:verbiste-gtk (replaces verbiste-gnome). Best-case scenario I'd like to work on a QT or Plasma frontend, but I doubt I'll have time for the best case before buster's freeze. Regards, Nicholas
signature.asc
Description: PGP signature