Your message dated Tue, 29 Dec 2015 15:28:48 +1100
with message-id <1633580.8D2ADzIoZA@deblab>
and subject line Re: Bug#801549: gitg: new upstream release available (3.18.0)
has caused the Debian Bug report #801549,
regarding gitg: new upstream release available (3.18.0)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
801549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801549
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gitg
Version: 3.17.1-1
Severity: wishlist
Dear Maintainer,
A new upstream version is available (3.18.0) which brings some more
improvement and bugfixes [1]. Please consider submitting an update
to the current package in experimental at least, or even unstable,
if your opinion regarding feature parity between v0.2.x and v3.18.x
has changed.
I personally prefer the more modern interface of the latest versions.
[1] http://ftp.gnome.org/pub/gnome/sources/gitg/3.18/gitg-3.18.0.news
Best regards,
Ghislain
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (2, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gitg depends on:
ii dbus-x11 1.10.0-3
ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2
ii gir1.2-peas-1.0 1.16.0-1
ii git 1:2.6.1-1
ii gsettings-desktop-schemas 3.18.0-1
ii libc6 2.19-22
ii libcairo2 1.14.2-2
ii libgdk-pixbuf2.0-0 2.32.1-1
ii libgee-0.8-2 0.18.0-1
ii libgirepository-1.0-1 1.44.0-1+b2
ii libgit2-glib-1.0-0 0.23.6-1
ii libglib2.0-0 2.46.0-2
ii libgtk-3-0 3.16.6-1
ii libgtksourceview-3.0-1 3.18.0-1
ii libgtkspell3-3-0 3.0.7-2
ii libjavascriptcoregtk-4.0-18 2.10.0+dfsg1-1
ii libjson-glib-1.0-0 1.0.4-2
ii libpango-1.0-0 1.38.0-3
ii libpeas-1.0-0 1.16.0-1
ii libsecret-1-0 0.18.3-1
ii libsoup2.4-1 2.52.0-1
ii libwebkit2gtk-4.0-37 2.10.0+dfsg1-1
gitg recommends no packages.
gitg suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
> with version 3.19.3 it builds fine using sbuild, and it also seems to be
> smoother at dealing with large diffing / branches merges.
> I just gave a try - it doesn't require big (if any) packaging change.
Thanks for reminding me about new release, Jérémy.
I've uploaded 3.19.3 to experimental so I'm closing this bug.
Unfortunately Gitg still have unfixed ill-designed diff view which I consider
detrimental for Gitg usefulness. Frankly I'm still not happy with performance
of Gitg (even on its own packaging repository) but that's hopeless...
Also 3.19.3 show rather annoying warning on every start:
~~~~
(gitg:69813): Gtk-WARNING **: Theme parsing error: <broken file>:1:0: Failed
to import: The resource at '/org/gnome/libgd/tagged-entry/default.css' does
not exist
~~~~
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
--
Best wishes,
Dmitry Smirnov.
---
There is no such thing as public opinion. There is only published opinion.
-- Winston Churchill
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
