[FFe] Sync alarm-clock 1.2.3-2 (universe) from Debian unstable (main)

Bug #400605 reported by Artur Rona
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alarm-clock (Debian)
Fix Released
Undecided
Unassigned
alarm-clock (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: alarm-clock

Please upgrade package to 1.2.3 version. 0.9.19 is out-of-date and version 1.2.3 fixes other bugs reported on launchpad.

 alarm-clock (1.2.3-1) unstable; urgency=low

   * New Upstream Version (LP: #400605, #419167)
     - has correct homepage link (LP: #375958)
   * add README.source
   * remove libglade2-dev from build deps, no longer needed
   * Debian Policy 3.8.3
   * fix some old ubuntu bugs in older versions (not yet synced) in the
     changelog

 -- Ryan Niebur <email address hidden> Wed, 02 Sep 2009 16:39:01 -0700
alarm-clock (1.2.1-1) unstable; urgency=low

   * New Upstream Version
     - fixes simple counters (Closes: #537791)
   * patch to fix the autostart exec path (Closes: #537793)

 -- Ryan Niebur <email address hidden> Sun, 02 Aug 2009 01:40:45 -0700
alarm-clock (1.1-2) unstable; urgency=low

   * upload to unstable

 -- Ryan Niebur <email address hidden> Thu, 09 Jul 2009 04:22:20 -0700
alarm-clock (1.1-1) experimental; urgency=low

   * New Upstream Version
     - no longer uses glade (LP: #375952)
   * Debian Policy 3.8.2
   * remove patching
   * remove config.{log,status} in d/clean, and add lintain overrides for
     configure-generated-file-in-source

 -- Ryan Niebur <email address hidden> Thu, 09 Jul 2009 04:03:12 -0700
alarm-clock (1.0~beta1-1) experimental; urgency=low

   * replace using the constantly changing ip address in debian/watch
     with using a script on my VPS
   * adopt packages (Closes: #521226)
   * New upstream release
   * remove all of the python and cdbs
     - this version is no longer in python
       (LP: #321795, #365079, #271489, #274121, #275090)
   * convert to dh7
   * convert to arch:any
   * add build deps and shlibs:depends
   * add a quilt patch to fix build
   * make changes to the menu and man page for the rename from alarm-
     clock to alarmclock
   * update man page, there is no longer any options
   * add DMUA header

 -- Ryan Niebur <email address hidden> Sat, 30 May 2009 10:17:38 -0700

Tags: patch upgrade

Related branches

Artur Rona (ari-tczew)
description: updated
tags: added: upgrade
summary: - Please sync alarm-clock 1.1-2 (universe) from Debian unstable (main)
+ Please upgrade alarm-clock to 1.2.2 version
Changed in alarm-clock (Ubuntu):
assignee: nobody → Chris Coulson (chrisccoulson)
importance: Undecided → Wishlist
status: New → In Progress
Revision history for this message
Artur Rona (ari-tczew) wrote : Re: Please upgrade alarm-clock to 1.2.2 version

@Chris, are you working on alarm-clock? If not, I'll make package. I want to got alarm-clock 1.2.2 in karmic before FFe.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Feel free to take this one. I've got other stuff that I need to work on at the moment.

Artur Rona (ari-tczew)
Changed in alarm-clock (Ubuntu):
assignee: Chris Coulson (chrisccoulson) → Artur Rona (ari-tczew)
Revision history for this message
Artur Rona (ari-tczew) wrote :

I made package, it builds fine on my-ppa.
https://edge.launchpad.net/~ari-tczew/+archive/ppa/+build/1170417/+files/buildlog_ubuntu-karmic-i386.alarm-clock_1.2.2-0ubuntu1~ppa0_FULLYBUILT.txt.gz

alarm-clock (1.2.2-0ubuntu1) karmic; urgency=low

  * New upstream release (LP: #400605):
    - Use GtkBuilder instead libglade (LP: #375952)
    - No longer code in python (LP: #321795)
  * Merge debian-dir from 1.2.1-1 (unstable), remaining changes:
    - Drop libglade2-dev from Build-Depends, no longer needed.
    - Add README.source to fix lintian warning.

 -- Artur Rona <email address hidden> Wed, 19 Aug 2009 01:16:45 +0200

Changed in alarm-clock (Ubuntu):
assignee: Artur Rona (ari-tczew) → nobody
status: In Progress → New
Revision history for this message
Julien Lavergne (gilir) wrote :

Thanks for your work. Some comments :
* Please forward the changes you made on debian/ to Debian to let the package in sync with Debian.
* bug 375952 is not relative to the use of GtkBuilder. It shouldn't be close like this.
* bug 321795 should not be close like this. you should try to reproduce the bug with the new version and with the reporter of the bug. Changing the language doesn't mean the bug is gone.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Also, did you have to repack the tar.bz2 from the alarm-clock website? (I didn't find a tar.gz available there) If so, it would be good to share the tar.gz with Debian to make the packages sync-able.

Thanks

Revision history for this message
Artur Rona (ari-tczew) wrote :

Julien says: "bug 321795 should not be close like this. you should try to reproduce the bug with the new version and with the reporter of the bug."
I guess that it's no need reproduce, because alarm-clock 1.2.2 isn't wroted in python.

Artur Rona (ari-tczew)
tags: added: patch
Revision history for this message
Ryan Niebur (ryan52) wrote :

hi guys. thanks much for your work on this! I will integrate it into Debian, and then during the next Ubuntu release cycle I will request a sync. Sorry that this didn't get into Karmic in time.

Changed in alarm-clock (Ubuntu):
assignee: nobody → Ryan Niebur (ryan52)
status: New → In Progress
Ryan Niebur (ryan52)
Changed in alarm-clock (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Artur Rona (ari-tczew) wrote : Re: [FFe] Sync alarm-clock 1.2.3-1 (universe) from Debian unstable (main)

 alarm-clock (1.2.3-1) unstable; urgency=low

   * New Upstream Version (LP: #400605, #419167)
     - has correct homepage link (LP: #375958)
   * add README.source
   * remove libglade2-dev from build deps, no longer needed
   * Debian Policy 3.8.3
   * fix some old ubuntu bugs in older versions (not yet synced) in the
     changelog

 -- Ryan Niebur <email address hidden> Wed, 02 Sep 2009 16:39:01 -0700

summary: - Please upgrade alarm-clock to 1.2.2 version
+ [FFe] Sync alarm-clock 1.2.3-1 (universe) from Debian unstable (main)
Changed in alarm-clock (Debian):
status: New → Fix Released
Changed in alarm-clock (Ubuntu):
assignee: Ryan Niebur (ryan52) → nobody
status: Fix Committed → New
Revision history for this message
Artur Rona (ari-tczew) wrote :

Removed my package from attachments, subscribing motu-release to waiting for ACK FFe.

description: updated
Revision history for this message
Andrea Veri (av) wrote :

Which kind of tests have you done with this package? was it completely working on karmic?
unsubscribing u-u-s, motu-release will process your request.

Revision history for this message
Ryan Niebur (ryan52) wrote :

note that this is a complete rewrite...

Revision history for this message
Nathan Handler (nhandler) wrote :

I am setting this bug to 'Incomplete' until details about the tests performed are provided. As Ryan said, this was a complete rewrite, so we want to make sure that there are no regressions or other serious issues.

Changed in alarm-clock (Ubuntu):
status: New → Incomplete
Revision history for this message
Artur Rona (ari-tczew) wrote :

Test start work on bug #425163

Revision history for this message
Ryan Niebur (ryan52) wrote :

new version (1.2.3-2) fixing #425163 uploaded to Debian.

summary: - [FFe] Sync alarm-clock 1.2.3-1 (universe) from Debian unstable (main)
+ [FFe] Sync alarm-clock 1.2.3-2 (universe) from Debian unstable (main)
Revision history for this message
Artur Rona (ari-tczew) wrote :

Now 1.2.3-2 can be sync from Debian unstable. Bug #425163 has been fixed.

Changed in alarm-clock (Ubuntu):
status: Incomplete → Confirmed
Artur Rona (ari-tczew)
Changed in alarm-clock (Ubuntu):
status: Confirmed → New
Revision history for this message
Martin Pitt (pitti) wrote :

This seems to be a complete rewrite (Python -> C), which is usually the "bad" direction in terms of program stability and crashes. What's the convincing benefit of getting this into karmic at this time?

Changed in alarm-clock (Ubuntu):
status: New → Incomplete
Revision history for this message
Martin Pitt (pitti) wrote :

Package is in universe, just leaving motu-release subscribed.

Revision history for this message
StefanPotyra (sistpoty) wrote :

While you can write bad code in any language, I've taken a glimpse at the new code. This makes me sceptical:
src/counters.c, function counters_accept:
 char buffer[30];
        [..]
 strftime(buffer, 40, "%Y", localtime(&curtime));

so -1 from me for karmic, as I believe that pitti's assumption might be correct.

Revision history for this message
Iulian Udrea (iulian) wrote :

Nack from me too. This will be automatically synced.

Marking as Won't Fix.

Changed in alarm-clock (Ubuntu):
status: Incomplete → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package alarm-clock - 1.2.4-1

---------------
alarm-clock (1.2.4-1) unstable; urgency=low

  * New Upstream Version
    - only change was already fixed in package,
      uploading anyway for updated email address
  * remove fix-duplicate-id patch, fixed upstream
  * update my email address and remove DMUA field

alarm-clock (1.2.3-2) unstable; urgency=low

  * don't do 'make check', it doesn't work right with quilt patches
  * add gtk-builder-proper-error-handling patch, used to debug LP 425163
  * add fix-duplicate-id, which fixes loading on Ubuntu (LP: #425163)

alarm-clock (1.2.3-1) unstable; urgency=low

  * New Upstream Version (LP: #400605, #419167)
    - has correct homepage link (LP: #375958)
  * add README.source
  * remove libglade2-dev from build deps, no longer needed
  * Debian Policy 3.8.3
  * fix some old ubuntu bugs in older versions (not yet synced) in the
    changelog

alarm-clock (1.2.1-1) unstable; urgency=low

  * New Upstream Version
    - fixes simple counters (Closes: #537791)
  * patch to fix the autostart exec path (Closes: #537793)

alarm-clock (1.1-2) unstable; urgency=low

  * upload to unstable

alarm-clock (1.1-1) experimental; urgency=low

  * New Upstream Version
    - no longer uses glade (LP: #375952)
  * Debian Policy 3.8.2
  * remove patching
  * remove config.{log,status} in d/clean, and add lintain overrides for
    configure-generated-file-in-source

alarm-clock (1.0~beta1-1) experimental; urgency=low

  * replace using the constantly changing ip address in debian/watch
    with using a script on my VPS
  * adopt packages (Closes: #521226)
  * New upstream release
  * remove all of the python and cdbs
    - this version is no longer in python
      (LP: #321795, #365079, #271489, #274121, #275090)
  * convert to dh7
  * convert to arch:any
  * add build deps and shlibs:depends
  * add a quilt patch to fix build
  * make changes to the menu and man page for the rename from alarm-
    clock to alarmclock
  * update man page, there is no longer any options
  * add DMUA header

 -- Ubuntu Archive Auto-Sync <email address hidden> Wed, 04 Nov 2009 01:45:04 +0000

Changed in alarm-clock (Ubuntu):
status: Won't Fix → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.