Nack from me too. This will be automatically synced.
Marking as Won't Fix.
** Changed in: alarm-clock (Ubuntu)
Status: Incomplete => Won't Fix
--
[FFe] Sync alarm-clock 1.2.3-2 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/400605
You received this bug notificati
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
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
--
[FFe] Sync alarm-cloc
Package is in universe, just leaving motu-release subscribed.
--
[FFe] Sync alarm-clock 1.2.3-2 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/400605
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: alarm-clock (Ubuntu)
Status: Confirmed => New
--
[FFe] Sync alarm-clock 1.2.3-2 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/400605
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
Now 1.2.3-2 can be sync from Debian unstable. Bug #425163 has been
fixed.
** Changed in: alarm-clock (Ubuntu)
Status: Incomplete => Confirmed
--
[FFe] Sync alarm-clock 1.2.3-2 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/400605
You received this bug notification
new version (1.2.3-2) fixing #425163 uploaded to Debian.
** Summary changed:
- [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)
--
[FFe] Sync alarm-clock 1.2.3-2 (universe) from Debian unstable (main)
