Activity log for bug #252026

Date Who What changed Old value New value Message
2008-07-26 02:02:52 Christopher Tozzi bug added bug
2008-07-26 04:50:15 Andy bug added attachment 'makemenu.log' (error log of the makemenu command)
2008-08-17 06:42:13 Andy bug added attachment 'tovid_GUI_1.png' (tovid_GUI_1.png)
2008-08-17 06:42:13 Andy bug added attachment 'tovid_GUI_2.png' (tovid_GUI_2.png)
2008-08-17 06:42:13 Andy bug added attachment 'tovid_GUI_3.png' (tovid_GUI_3.png)
2008-08-17 06:42:13 Andy bug added attachment 'tovid_log' (tovid_log)
2008-08-17 06:42:13 Andy bug added attachment 'tovid_log_a' (tovid_log_a)
2008-08-30 18:16:12 Christopher Tozzi description Binary package hint: tovid As described at http://ubuntuforums.org/showthread.php?t=830499, the Debian package for tovid available in the repositories on Hardy installs makemenu, makexml, makedvd and makevcd (and possibly other scripts) into /usr/share/tovid, but these utilities are not placed into the user's path. The only way to call them is to give the full path; i.e., simplying typing "makemenu" returns a "command not found" error, but "/usr/share/tovid/makemenu" works. This was not the case on Gutsy, so I think it's a bug. To make things worse, tovidgui (installed from the same repository) fails because it complains about not being able to find makemenu, etc., because it expects them to be in the user's path and they're not. Symlinking the programs in /usr/share/tovid to /usr/bin works around the problem, but that solution is not obvious to non-technical users. Unless there's an obscure logic behind not placing makemenu, etc. in the user's path, why don't we fix this? I'm using amd64; I'm not sure if this problems exists with the i386 package as well. Binary package hint: tovid As described at http://ubuntuforums.org/showthread.php?t=830499, the Debian package for tovid available in the repositories on Hardy installs makemenu, makexml, makedvd and makevcd (and possibly other scripts) into /usr/share/tovid, but these utilities are not placed into the user's path. The only way to call them is to give the full path; i.e., simply typing "makemenu" returns a "command not found" error, but "/usr/share/tovid/makemenu" works. This was not the case on Gutsy, so I think it's a bug. To make things worse, tovidgui (installed from the same repository) fails because it complains about not being able to find makemenu, etc., because it expects them to be in the user's path and they're not. Symlinking the programs in /usr/share/tovid to /usr/bin works around the problem, but that solution is not obvious to non-technical users. Unless there's an obscure logic behind not placing makemenu, etc. in the user's path, why don't we fix this? I'm using amd64; I'm not sure if this problems exists with the i386 package as well.
2008-08-30 18:16:12 Christopher Tozzi title Hardy package for tovid doesn't makemenu, makexml etc. into user's path Hardy package for tovid doesn't place makemenu, makexml etc. into user's path
2009-03-21 09:20:10 Alessio Treglia tovid (Ubuntu): status New Incomplete
2010-12-06 16:02:37 Leo Arias tags maverick
2011-01-17 15:12:45 Leo Arias tovid (Ubuntu): status Incomplete New
2011-04-30 14:00:12 Launchpad Janitor tovid (Ubuntu): status New Fix Released
2011-04-30 15:07:42 Andy removed subscriber Andy
2011-05-01 00:29:14 Launchpad Janitor branch linked lp:ubuntu/tovid