please update gjots2 to 2.3.8 (complete patch included)

[Rolf Leggewie]

The gjots2 Debian maintainer is MIA. I have taken the liberty to update to the latest upstream source and fix a couple of bugs in the process.

[Adil Arif (adisari06)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Judging from your description, I am going to assign this bug to the gjots2 package in hopes that it will have a faster response. If you believe that I have chosen the wrong package, please change your bug to the correct one. Good luck on getting it fixed!

[Rolf Leggewie (r0lf)]

ping

[Fabrice Coutadeur (fabricesp)]

Hi,

No need to ping: your bug report won't have higher priority than others :-)

As we are past Feature Freeze for Karmic, you have to request a Feature Freeze exception, in order to get your bug considered for Karmic.
You'll find the full process there: https://wiki.ubuntu.com/FreezeExceptionProcess

Unsubscribing u-u-s in the meantime.

Cheers,
Fabrice

[Rolf Leggewie (r0lf)]

No need to ping? I disagree. I may have needed to ping earlier.

It's sad to see the work I did go to waste now because nobody bothered to take a look early enough. Why should I be punished now and have to expend even more effort? No way!

I'm angry, the handling of this bug is a real shame. The sponsors had more than enough time. If they missed the boat, IMNSHO it's their responsibility to fix the mess, it's certainly not mine.

[Rolf Leggewie (r0lf)]

Fabrice, I see you are new as MOTU. Your comment is IMO highly cynical and blames and demotivates the wrong person (smiley present or not). It would be nice if you were more careful in the future when representing your newly acquired status and power.

[Fabrice Coutadeur (fabricesp)]

Hi Rolf,

I'm sorry if you interpreted my answer as cynical, as it wasn't the case: I only intended to explain you the process that has to be followed until Karmic is out. Once it's out, this will be possible for any MOTU to upload that package update. Before that, no MOTU can do anything without getting the acks from motu-release. This is how the Ubuntu release cycle works.

I came to your bug report because I was checking the sponsoring queue, and not because of the ping, and I was just explaining you that it's of no use to add a 'ping' comment in the bug report: most of the MOTUs just go through the list of bugs, sorted by bug number.

FYI, this kind of situation (too late: please fulfill a FFe) also happened to me 3 times, including in Karmic, and I followed the process...

One more time, I did'nt intended to be cynic.

Apologies,

Fabrice

[Rolf Leggewie (r0lf)]

I will adopt the package as Debian maintainer. So, despite the unfavorable performance of the MOTU team in this case, the work I did will not go to waste. It should be hitting Ubuntu Lucid. I will not make any special effort with regards to Ubuntu, though, after this experience.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gjots2 - 2.3.8-1

---------------
gjots2 (2.3.8-1) unstable; urgency=low

  * Take over maintenance of gjots2 from Khalid El Fathi (Closes: #547057)
    and acknowledge previous NMU uploads. Thank you, Khalid and Sandro for
    your work on this package.
  * New Upstream Version (LP: #406574)
    - display sidebar icons properly (Closes: #446696, LP: #115132)
  * move changes currently made directly to the source into proper patches,
    but don't actually use 20_seascape.patch
  * debian/control
    - recommend instead of depending on mpage and gv (Closes: #475404)
    - fix description, gjots is not a mindmap tool (Closes: #424724)
    - update to standard 3.8.3 and debhelper 5
    - set Vcs information
 -- Ubuntu Archive Auto-Sync <email address hidden> Mon, 30 Nov 2009 23:45:26 +0000