* Flameeyes QA Warning! /usr/doc present in image! /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/index.html /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/fdl-license.html /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/gpl-license.html /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/care.html /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/help.html /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/whatis.html /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/importexport1.png /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/importexport2.png /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/importexport3.png /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/mainwindow.png /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/pref1.png /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/pref2.png /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/pref3.png /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/selectdate.png /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/statistics.png /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/mainwindow_preg.png /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/README /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/COPYING /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/AUTHORS /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/ChangeLog /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/INSTALL /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/NEWS /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/TODO /var/tmp/portage/x11-misc/periodic-calendar-2.2/image//usr/doc/PeriodicCalendar/ABOUT-NLS
I have tried to edit Makefile.am without success, automake needs: cp /usr/share/gettext/config.rpath . intltoolize --force --copy --automake || die "intltoolize failed" eautoreconf to run but, later, it starts this loop without end: cd .. \ && CONFIG_FILES=po/Makefile.in CONFIG_HEADERS= CONFIG_LINKS= \ /bin/sh ./config.status config.status: creating po/Makefile.in config.status: executing depfiles commands config.status: executing libtool commands config.status: executing po-directories commands config.status: creating po/POTFILES config.status: creating po/Makefile make[2]: Leaving directory `/var/tmp/portage/x11-misc/periodic-calendar-2.3/work/PeriodicCalendar-2.3/po' make[2]: Entering directory `/var/tmp/portage/x11-misc/periodic-calendar-2.3/work/PeriodicCalendar-2.3/po' cd .. \ && CONFIG_FILES=po/Makefile.in CONFIG_HEADERS= CONFIG_LINKS= \ /bin/sh ./config.status config.status: creating po/Makefile.in config.status: executing depfiles commands config.status: executing libtool commands config.status: executing po-directories commands config.status: creating po/POTFILES config.status: creating po/Makefile make[2]: Leaving directory `/var/tmp/portage/x11-misc/periodic-calendar-2.3/work/PeriodicCalendar-2.3/po' make[2]: Entering directory `/var/tmp/portage/x11-misc/periodic-calendar-2.3/work/PeriodicCalendar-2.3/po' cd .. \ After reading this from upstream: http://linuxorg.sourceforge.net/download.php I would vote for treecleaning this and point people to use upstream jars directly
looks like this bug was misassigned, anyway, this is still a candidate for removal I think... :-/
I found it on bugwranglers without realizing upstream was dead for quite some time. Pacho feel free to start the removal procedure if you want.
Will use this bug for that then
dropped