Bug#585145: gtimelog in Debian
On Thu, 06 Oct 2011 at 14:26:41 -0400, Barry Warsaw wrote:
> I just wanted to follow up since I released a new gtimelog (0.7.0) both
> upstream and for Ubuntu 11.10.
(FYI, neither I nor Lars will be notified if you just mail the bug: for bugs
in normal Debian packages, the maintainer is automatically contacted, but
the maintainer of the wnpp pseudo-package is a mailing list or something, and
has little to do with individual wnpp bugs.)
> * The Vcs-Bzr branch is in an older bzr format. I'd like to get that
> upgraded to 2a if that's feasible. Any objections?
Whatever you think is best, as far as I'm concerned.
> * Can I change Maintainer: to point to myself?
Yes, if you're taking responsibility for the package, please do. Lars (or
anyone else interested) might well want to be in Uploaders as a co-maintainer.
You could also move it to Python applications team maintenance if you like:
the Python teams might be a good source of sponsors (although they might
also insist that you use svn).
> * I don't think the Oneiric version will port straight over to Sid because
> Ubuntu seems to be ahead of Debian with some of the dependencies.
Ah, if 0.7.0 needs GNOME 3 then that complicates things - the GNOME 3
transition in unstable is still in progress.
> Maybe we need to get the new version into experimental, where I think the
> dependencies can be satisfied. From the d/control file:
>
> Package: gtimelog
> Architecture: all
> Depends: gir1.2-appindicator3-0.1,
> gir1.2-gtk-3.0,
> gir1.2-pango-1.0 (>= 1.29.3+git20110916),
> python-gobject (>= 2.90),
> ${misc:Depends},
> ${python:Depends}
>
> * experimental has python-gobject 2.90.3-2 (unstable has 2.28.6-5).
> * gir1.2-pango-1.0 and gir1.2-gtk-3.0 both seem okay in unstable.
> * afaict, gir1.2-appindicator3-0.1 isn't available in Debian at all.
>
> I'll try to build a version w/o appindicator and see if I can get that
> installed and running in experimental.
Uploading to experimental sounds like the best plan for now. I suspect
appindicator isn't vital functionality - if I understand Ubuntu correctly,
it's a replacement for the tray icon, so one easy fallback if appindicator was
missing would be to have a traditional tray icon, and another would be to
not have a tray-icon-like-thing at all.
I'm getting very tempted to ask for gtimelog to be removed from unstable
(and hence testing) until a better version like 0.7.0 can go in - anyone
who's desperate enough can get 0.0+svn88 from stable, and having the
package available in unstable in the meantime gives a false indication
of its quality. As long as it's in the archive *somewhere* (e.g. stable and/or
experimental), you shouldn't have to go through the NEW queue to reinstate it
when it's ready.
S
Reply to: