Summary: | x11-misc/{gdeskcal,gdeskcal-skins} removal request | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jakub Moc (RETIRED) <jakub> |
Component: | New packages | Assignee: | Nguyen Thai Ngoc Duy (RETIRED) <pclouds> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | desktop-misc, parasietje, skotlex |
Priority: | High | Keywords: | PMASKED |
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 60246, 128030, 128031, 128032 | ||
Bug Blocks: |
Description
Jakub Moc (RETIRED)
2006-07-26 09:06:24 UTC
p.masked them. I leave this bug open until they are removed. The "other serious malfunctions" are in fact only ONE malfunction, with the others being a duplicate for them. The malfunction is that "monthly" reminders are missed. Hardly a reason to remove a package from the portage tree? I've been unable to reproduce the crashes in bug 60246 and 128030. Bug 128030 states it is known by the developer. I have mailed the gdeskcal developer with a plead to try and fix that bug. So, in summary, these are the issues with gdeskcal: - Monthly reminders are missed - Two crashes I've been unable to reproduce - No upstream release for 2 years I would hate to see this package be removed solely because of these few issues... Is it really that unethical to mark this package ~x86 and let it reside in the portage tree? Enlightenment also has multiple issues, and will have them for a very long time. Besides, people who aren't running KDE or Gnome really have no other lightweight calendar alternative... I have to concur with Ruben. I've not experienced the reported crashes at all, and under Fluxbox, I haven't found a suitable replacement for gdeskcal. I personally hate to see bugs left open in b.g.o for ages because I can't fix them. You could move it into your overlays if you want to use. Leaving it in the tree means that we have to support it (but I can't in this case). It may be re-added when upstream releases a new version. They're gone *** Bug 203258 has been marked as a duplicate of this bug. *** |