From lunar-bugs at lunar-linux.org Tue Oct 7 13:52:51 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Tue, 7 Oct 2008 13:52:51 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000362]: Cannot boot after update Message-ID: <14fb09baa41dc5fcd45f2f992bf4c4ee@bugs.lunar-linux.org> A NOTE has been added to this issue. ====================================================================== http://bugs.lunar-linux.org/view.php?id=362 ====================================================================== Reported By: piggy Assigned To: sofar ====================================================================== Project: Lunar Linux Issue ID: 362 Category: lunar Reproducibility: always Severity: crash Priority: normal Status: feedback Moonbase Version: 20080821.1 Core Tools: Lunar Core Tools Version: 2007MMDD (I'm an idiot and didn't edit this field.) ====================================================================== Date Submitted: 08-21-2008 08:34 CEST Last Modified: 10-07-2008 13:52 CEST ====================================================================== Summary: Cannot boot after update Description: Dear sir: I had installed lunar 1.6.1 from CD. and I update with #lunar -v update after that I had reboot my system. Then it fail after reboot and the error show on the picture. I used a brand NEW haddisk and reinstalled it many times and changed file system to Ext3, Ext2, ReiserFS. But it still the same problem. Could you please help me to fix this. Best Regards ====================================================================== ---------------------------------------------------------------------- piggy - 08-21-08 08:39 ---------------------------------------------------------------------- More info... If I pressed Ctrl-D the system will reboot. If I input root password. The system will return prompt. I had tried #reiserfsck /dev/hda3 but it cannot solve the problem. Please help me. ---------------------------------------------------------------------- El_Angelo - 08-21-08 08:39 ---------------------------------------------------------------------- Please read the update guide on the front-page of lunar-linux.org and follow update instructions there http://www.lunar-linux.org/index.php?option=com_content&task=view&id=58&Itemid=1 ---------------------------------------------------------------------- piggy - 08-21-08 12:43 ---------------------------------------------------------------------- Dear Sir: I had followed the instruction that web page. http://www.lunar-linux.org/index.php?option=com_content&task=view&id=58&Itemid=1 But I still have the same problem. After boot, If I press ctrl-d the system will reboot. If I give a root's password. It return prompt. I try to use reiserfs /dev/hda3 It return "Failed to open the device '/dev/hda3' : No such file or directory. Please advice me. Best Regards. ---------------------------------------------------------------------- hittis - 10-07-08 13:52 ---------------------------------------------------------------------- I have the same issue on a system (main firewall at home) after the latest 'lunar renew' last friday. The system has been updated regularly, last time before this - approx a week before. I started a 'screen' and ran 'lunar renew' which I left running. After a while (two or more hours) I get back to check on the progress and the session just closes (using putty on windows). Can not log back in. It was pingable but traffic through it wasn't working correctly so I just asked my fianc?e to restart the box "the hard way". When I got home I connected a screen to the box and saw the same error as in the pictures - though my root device is /dev/sda1. Due to timeconstraints I haven't had time to dig deeper. Issue History Date Modified Username Field Change ====================================================================== 08-21-08 08:34 piggy New Issue 08-21-08 08:34 piggy Status new => assigned 08-21-08 08:34 piggy Assigned To => sofar 08-21-08 08:34 piggy File Added: IMG_2416.jpg 08-21-08 08:34 piggy Moonbase Version => 20080821.1 08-21-08 08:34 piggy Core Tools => Lunar 08-21-08 08:34 piggy Core Tools Version => 2007MMDD (I'm an idiot and didn't edit this field.) 08-21-08 08:36 piggy File Added: IMG_2417.jpg 08-21-08 08:39 piggy Note Added: 0000812 08-21-08 08:39 El_Angelo Status assigned => closed 08-21-08 08:39 El_Angelo Note Added: 0000813 08-21-08 08:39 El_Angelo Resolution open => fixed 08-21-08 12:43 piggy Status closed => feedback 08-21-08 12:43 piggy Resolution fixed => reopened 08-21-08 12:43 piggy Note Added: 0000814 10-07-08 13:52 hittis Note Added: 0000828 ====================================================================== From lunar-bugs at lunar-linux.org Tue Oct 7 13:54:06 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Tue, 7 Oct 2008 13:54:06 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000362]: Cannot boot after update Message-ID: <1e08763e64fdf2293fbaa1270168cc76@bugs.lunar-linux.org> A NOTE has been added to this issue. ====================================================================== http://bugs.lunar-linux.org/view.php?id=362 ====================================================================== Reported By: piggy Assigned To: sofar ====================================================================== Project: Lunar Linux Issue ID: 362 Category: lunar Reproducibility: always Severity: crash Priority: normal Status: feedback Moonbase Version: 20080821.1 Core Tools: Lunar Core Tools Version: 2007MMDD (I'm an idiot and didn't edit this field.) ====================================================================== Date Submitted: 08-21-2008 08:34 CEST Last Modified: 10-07-2008 13:54 CEST ====================================================================== Summary: Cannot boot after update Description: Dear sir: I had installed lunar 1.6.1 from CD. and I update with #lunar -v update after that I had reboot my system. Then it fail after reboot and the error show on the picture. I used a brand NEW haddisk and reinstalled it many times and changed file system to Ext3, Ext2, ReiserFS. But it still the same problem. Could you please help me to fix this. Best Regards ====================================================================== ---------------------------------------------------------------------- piggy - 08-21-08 08:39 ---------------------------------------------------------------------- More info... If I pressed Ctrl-D the system will reboot. If I input root password. The system will return prompt. I had tried #reiserfsck /dev/hda3 but it cannot solve the problem. Please help me. ---------------------------------------------------------------------- El_Angelo - 08-21-08 08:39 ---------------------------------------------------------------------- Please read the update guide on the front-page of lunar-linux.org and follow update instructions there http://www.lunar-linux.org/index.php?option=com_content&task=view&id=58&Itemid=1 ---------------------------------------------------------------------- piggy - 08-21-08 12:43 ---------------------------------------------------------------------- Dear Sir: I had followed the instruction that web page. http://www.lunar-linux.org/index.php?option=com_content&task=view&id=58&Itemid=1 But I still have the same problem. After boot, If I press ctrl-d the system will reboot. If I give a root's password. It return prompt. I try to use reiserfs /dev/hda3 It return "Failed to open the device '/dev/hda3' : No such file or directory. Please advice me. Best Regards. ---------------------------------------------------------------------- hittis - 10-07-08 13:52 ---------------------------------------------------------------------- I have the same issue on a system (main firewall at home) after the latest 'lunar renew' last friday. The system has been updated regularly, last time before this - approx a week before. I started a 'screen' and ran 'lunar renew' which I left running. After a while (two or more hours) I get back to check on the progress and the session just closes (using putty on windows). Can not log back in. It was pingable but traffic through it wasn't working correctly so I just asked my fianc?e to restart the box "the hard way". When I got home I connected a screen to the box and saw the same error as in the pictures - though my root device is /dev/sda1. Due to timeconstraints I haven't had time to dig deeper. ---------------------------------------------------------------------- hittis - 10-07-08 13:54 ---------------------------------------------------------------------- Oh, using the boot-cd I ran an fsck on the system (ext3) and it completed without errors. Issue History Date Modified Username Field Change ====================================================================== 08-21-08 08:34 piggy New Issue 08-21-08 08:34 piggy Status new => assigned 08-21-08 08:34 piggy Assigned To => sofar 08-21-08 08:34 piggy File Added: IMG_2416.jpg 08-21-08 08:34 piggy Moonbase Version => 20080821.1 08-21-08 08:34 piggy Core Tools => Lunar 08-21-08 08:34 piggy Core Tools Version => 2007MMDD (I'm an idiot and didn't edit this field.) 08-21-08 08:36 piggy File Added: IMG_2417.jpg 08-21-08 08:39 piggy Note Added: 0000812 08-21-08 08:39 El_Angelo Status assigned => closed 08-21-08 08:39 El_Angelo Note Added: 0000813 08-21-08 08:39 El_Angelo Resolution open => fixed 08-21-08 12:43 piggy Status closed => feedback 08-21-08 12:43 piggy Resolution fixed => reopened 08-21-08 12:43 piggy Note Added: 0000814 10-07-08 13:52 hittis Note Added: 0000828 10-07-08 13:54 hittis Note Added: 0000829 ====================================================================== From lunar-bugs at lunar-linux.org Sat Oct 11 19:40:05 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sat, 11 Oct 2008 19:40:05 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000322]: "lunar submit " does not work anymore Message-ID: <4fe1acb08936ac63773ce85e719e206e@bugs.lunar-linux.org> The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=322 ====================================================================== Reported By: gb Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 322 Category: lunar Reproducibility: always Severity: major Priority: normal Status: closed Moonbase Version: 20071231.17 Core Tools: Lunar Core Tools Version: 20071211 Resolution: fixed Fixed in Version: ====================================================================== Date Submitted: 01-02-2008 21:09 CET Last Modified: 10-11-2008 19:40 CEST ====================================================================== Summary: "lunar submit " does not work anymore Description: When I am trying to submit a module change, I now get this error: "fvwm: Submit this module now? [y] y Error: not authorized" It used to work quite well. I noticed that in my /etc/lunar/local/config file there are many double entries. ADMIN was a double entry too, so I left only my email address as "ADMIN", but it still does not work. Any advice? ====================================================================== ---------------------------------------------------------------------- ratler - 09-20-08 08:21 ---------------------------------------------------------------------- Is this still an issue? AFAIK other people can submit without any problems. ---------------------------------------------------------------------- gb - 09-20-08 13:30 ---------------------------------------------------------------------- Hi, Thanks for the feedback. Currently I have no modules to submit, can I issue a dummy submit just to check if it still broken? (I will state that it is a dummy in the submit message). (Or, I could simply update something you know must get updated as a chore, testing my "submissive" capabilities altogether ;) ) As for the double entries in /etc/lunar/local/config, they are still there. I have attached "config" here below for reference. Gb ---------------------------------------------------------------------- ratler - 09-20-08 14:29 ---------------------------------------------------------------------- Just re-submit the bug if it still exist when you do have a module to submit, I'm pretty sure it works anyway. Regarding the double entries in local/config that bug was fixed in "theedge" back in Mars (I don't know if it was merged into lunar yet). If you use theedge that problem shouldn't be there anymore, try changing some settings and it should be nice and clean up after it self (otherwise manually edit the file and remove the duplicates). They won't show up again though :) ---------------------------------------------------------------------- gb - 09-20-08 21:22 ---------------------------------------------------------------------- I have just successfully submitted a version bump of "mldonkey": > mldonkey: Submit this module now? [y] y > OK: submission queued So the "lvu submit" problem seems solved. About the double entries in /etc/lunar/local/config, I am using "lunar", not "theedge". I have just run the "config" file through "sort -u" and then fiddled a bit inside "lunar". No double entries have been created this time, so this seems sorted too. Thanks, Gb ---------------------------------------------------------------------- ratler - 09-21-08 08:18 ---------------------------------------------------------------------- Both issues fixed. Issue History Date Modified Username Field Change ====================================================================== 01-02-08 21:09 gb New Issue 01-02-08 21:09 gb Status new => assigned 01-02-08 21:09 gb Assigned To => sofar 01-02-08 21:09 gb Moonbase Version => 20071231.17 01-02-08 21:09 gb Core Tools => Lunar 01-02-08 21:09 gb Core Tools Version => 20071211 01-02-08 21:10 gb Issue Monitored: gb 09-20-08 08:21 ratler Note Added: 0000823 09-20-08 08:21 ratler Status assigned => feedback 09-20-08 13:21 gb File Added: config 09-20-08 13:30 gb Note Added: 0000824 09-20-08 14:26 ratler Status feedback => assigned 09-20-08 14:26 ratler Assigned To sofar => ratler 09-20-08 14:29 ratler Note Added: 0000825 09-20-08 21:22 gb Note Added: 0000826 09-21-08 08:18 ratler Status assigned => resolved 09-21-08 08:18 ratler Resolution open => fixed 09-21-08 08:18 ratler Note Added: 0000827 10-11-08 19:40 ratler Status resolved => closed ====================================================================== From lunar-bugs at lunar-linux.org Sat Oct 11 19:40:06 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sat, 11 Oct 2008 19:40:06 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000183]: Adding 1st normal user returns error in groupadd 100 command Message-ID: The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=183 ====================================================================== Reported By: zbiggy Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 183 Category: ISO Reproducibility: always Severity: minor Priority: normal Status: closed Moonbase Version: 2006MMDD.NN Core Tools: Lunar Core Tools Version: 2006MMDD Resolution: fixed Fixed in Version: ====================================================================== Date Submitted: 02-24-2007 14:48 CET Last Modified: 10-11-2008 19:40 CEST ====================================================================== Summary: Adding 1st normal user returns error in groupadd 100 command Description: This bug exist in all isos I remember. During setup in one of steps there is option to setup root password and user accounts. When you add first normal user the groupadd 100 command is executed. This command returns error: "groupadd 100: is not correct group name" I think -g parameter is missing and groupadd thinks guid is group name. ====================================================================== ---------------------------------------------------------------------- sofar - 03-31-07 23:32 ---------------------------------------------------------------------- that would probably be a bug in `luser` .... need to verify. ---------------------------------------------------------------------- ratler - 09-17-08 12:29 ---------------------------------------------------------------------- Fixed in lunar-tools version 2008.1. This fix will be available on the next beta ISO of 1.6.4. Issue History Date Modified Username Field Change ====================================================================== 02-24-07 14:48 zbiggy New Issue 02-24-07 14:48 zbiggy Status new => assigned 02-24-07 14:48 zbiggy Assigned To => sofar 02-24-07 14:48 zbiggy Moonbase Version => 2006MMDD.NN 02-24-07 14:48 zbiggy Core Tools => Lunar 02-24-07 14:48 zbiggy Core Tools Version => 2006MMDD 03-31-07 23:32 sofar Note Added: 0000474 09-17-08 12:28 ratler Assigned To sofar => ratler 09-17-08 12:29 ratler Status assigned => resolved 09-17-08 12:29 ratler Resolution open => fixed 09-17-08 12:29 ratler Note Added: 0000821 10-11-08 19:40 ratler Status resolved => closed ====================================================================== From lunar-bugs at lunar-linux.org Sat Oct 11 19:40:06 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sat, 11 Oct 2008 19:40:06 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000205]: htfig build fails on x86_64 Message-ID: <8b57cd2ac050256ff3a195c180bfe5b6@bugs.lunar-linux.org> The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=205 ====================================================================== Reported By: neognomic Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 205 Category: module Reproducibility: always Severity: minor Priority: normal Status: closed Moonbase Version: 2006MMDD.NN Core Tools: Lunar Core Tools Version: 2006MMDD Resolution: won't fix Fixed in Version: ====================================================================== Date Submitted: 03-16-2007 05:29 CET Last Modified: 10-11-2008 19:40 CEST ====================================================================== Summary: htfig build fails on x86_64 Description: It looks like a code &/R gcc 4.1.* problem but reporting it here since there is a patch applied. [--x--] #> lin htdig htdig: Install & use optional (not installed) module apache2 Purpose: to use web interface ? [n] htdig: Install & use optional (not installed) module apache Purpose: to use web interface ? [n] htdig: Install & use optional (not installed) module apache-mod_ssl Purpose: to use web interface ? [n] Checking dependencies for htdig Downloading source file htdig-3.1.6.tar.gz for module htdig --23:09:10-- http://www.htdig.org/files/htdig-3.1.6.tar.gz [snip] Building htdig version 3.1.6 patching file ./configure OPTS= CFLAGS= -O2 -march=opteron -pipe -Wno-deprecated creating cache ./config.cache [snip] SGMLEntities.cc: In static member function 'static unsigned char SGMLEntities::translate(char*)': SGMLEntities.cc:157: error: cast from 'Object*' to 'int' loses precision make[1]: *** [SGMLEntities.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make[1]: Leaving directory `/usr/src/htdig-3.1.6/htdig' make: *** [all] Error 1 Creating /var/log/lunar/compile/htdig-3.1.6.bz2 ! Problem detected during BUILD [--x--] ====================================================================== ---------------------------------------------------------------------- sofar - 03-16-07 06:15 ---------------------------------------------------------------------- please stop filing module bugs in the lunar-iso category, thanks. ---------------------------------------------------------------------- ratler - 09-16-08 10:32 ---------------------------------------------------------------------- htdig is no longer maintained by it's developers so this module have been removed from moonbase. Issue History Date Modified Username Field Change ====================================================================== 03-16-07 05:29 neognomic New Issue 03-16-07 05:29 neognomic Status new => assigned 03-16-07 05:29 neognomic Assigned To => sofar 03-16-07 05:29 neognomic Moonbase Version => 2006MMDD.NN 03-16-07 05:29 neognomic Core Tools => Lunar 03-16-07 05:29 neognomic Core Tools Version => 2006MMDD 03-16-07 06:15 sofar Note Added: 0000422 03-16-07 06:15 sofar Assigned To sofar => 03-16-07 06:15 sofar Status assigned => new 03-16-07 06:15 sofar Category ISO => module 04-15-07 12:49 ratler Status new => assigned 04-15-07 12:49 ratler Assigned To => ratler 09-16-08 10:32 ratler Status assigned => resolved 09-16-08 10:32 ratler Resolution open => won't fix 09-16-08 10:32 ratler Note Added: 0000820 10-11-08 19:40 ratler Status resolved => closed ====================================================================== From lunar-bugs at lunar-linux.org Sat Oct 11 19:40:06 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sat, 11 Oct 2008 19:40:06 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000281]: vfat is lacking in initrd Message-ID: <35ddbb1099574217992321f44044ba5e@bugs.lunar-linux.org> The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=281 ====================================================================== Reported By: El_Angelo Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 281 Category: ISO Reproducibility: N/A Severity: feature Priority: normal Status: closed Moonbase Version: 20070913.123 Core Tools: Theedge Core Tools Version: 20070623 Resolution: fixed Fixed in Version: 1.6.4 Alpha releases(s) ====================================================================== Date Submitted: 09-14-2007 09:07 CEST Last Modified: 10-11-2008 19:40 CEST ====================================================================== Summary: vfat is lacking in initrd Description: 08:57 | sofar | I should add the fs modules to the initrd so we can have vfat-formatted usbstick booting lunar ====================================================================== ---------------------------------------------------------------------- Striker - 09-14-07 09:29 ---------------------------------------------------------------------- Lame. ---------------------------------------------------------------------- ratler - 09-16-08 10:26 ---------------------------------------------------------------------- vfat is present on 1.6.4-alpha3 (including usb install support) Issue History Date Modified Username Field Change ====================================================================== 09-14-07 09:07 El_Angelo New Issue 09-14-07 09:07 El_Angelo Status new => assigned 09-14-07 09:07 El_Angelo Assigned To => sofar 09-14-07 09:07 El_Angelo Moonbase Version => 20070913.123 09-14-07 09:07 El_Angelo Core Tools => Theedge 09-14-07 09:07 El_Angelo Core Tools Version => 20070623 09-14-07 09:29 Striker Note Added: 0000621 09-14-07 09:29 Striker Priority immediate => normal 09-14-07 09:29 Striker Severity block => feature 09-14-07 09:29 Striker Reproducibility always => N/A 09-16-08 10:17 ratler Assigned To sofar => ratler 09-16-08 10:26 ratler Status assigned => resolved 09-16-08 10:26 ratler Fixed in Version => 1.6.4 Alpha releases(s) 09-16-08 10:26 ratler Resolution open => fixed 09-16-08 10:26 ratler Note Added: 0000819 10-11-08 19:40 ratler Status resolved => closed ====================================================================== From lunar-bugs at lunar-linux.org Sat Oct 11 19:40:07 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sat, 11 Oct 2008 19:40:07 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000275]: db 4.6.18 conflict with openldap Message-ID: The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=275 ====================================================================== Reported By: piggy Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 275 Category: module Reproducibility: always Severity: minor Priority: normal Status: closed Moonbase Version: 20070807.02 Core Tools: Lunar Core Tools Version: 2007MMDD (I'm an idiot and didn't edit this field.) Resolution: reopened Fixed in Version: ====================================================================== Date Submitted: 08-27-2007 04:47 CEST Last Modified: 10-11-2008 19:40 CEST ====================================================================== Summary: db 4.6.18 conflict with openldap Description: Dear sir: I had tried update my server with lunar -v update then it update my OpenLDAP and its database. After server restart. I had tried to connect my ldap. But it always faild. I had roll back to db 4.5.20 then my system work find. Best Regards ====================================================================== ---------------------------------------------------------------------- ratler - 08-27-07 06:56 ---------------------------------------------------------------------- Could you please try again and send us the compile log of openldap. Also logs from openldap when you try to connect to openldap would be of great value. ---------------------------------------------------------------------- ratler - 08-27-07 07:14 ---------------------------------------------------------------------- One more thing, you might have to run db_upgrade in /var/openldap-data followed by a db_recover. Please make backups before doing so. If neither of the approaches work, make a LDIF dump of your entire ldap database with db 4.5.20. Then upgrade db and rebuild openldap. After that start with a fresh /var/openldap-data and then import that LDIF again. But as I said make sure you have proper backups before doing this. ---------------------------------------------------------------------- ratler - 09-09-07 12:00 ---------------------------------------------------------------------- So is this still an issue? If not I'm going to close this bug report. ---------------------------------------------------------------------- ratler - 09-14-07 08:32 ---------------------------------------------------------------------- No response. Assuming that it was not a module problem. ---------------------------------------------------------------------- piggy - 09-17-07 09:44 ---------------------------------------------------------------------- Dear Sir: Sorry for reply very late. I just came back from upcountry. Thank you for your advice. Today I follow your instruction on 08-27-07 07:14. My server still have the same problem. These are compile log of Berkerly DB and Openldap. Could you please check them and give me the advices. Best Regards Tosapol ================================================================================ root at master ~ # lin -r db + Reconfiguring "db" db: Install & use optional (not installed) module tcl Purpose: to build the tcl api ? [n] + adding "optional" depends for "db" on "tcl" (off) db: Install & use optional (not installed) module sun-jdk Purpose: for java support ? [n] + adding "optional" depends for "db" on "sun-jdk" (off) + Spawning download manager + download queue: db + starting lin "db" Checking dependencies for db + downloading module "db" + Skipping download of "db-4.6.18.tar.gz" (in cache) Building db version 4.6.18 + running "default_pre_build" + validating "/usr/src/db-4.6.18" + creating building dir "/usr/src/db-4.6.18" + Unpacking "/var/spool/lunar/db-4.6.18.tar.gz" in "/usr/src" + building "db" version "4.6.18" in /usr/src/db-4.6.18 + CC_EXT="ccache " + CXX_EXT="ccache " + CC="gcc" + CXX="g++" + CPP="cpp" + CFLAGS="" + CXXFLAGS="" + CPPFLAGS="" + LDFLAGS=" -s -Wl,-O1" + Enabled wrapper script usage checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking if building in the top-level or dist directories... no checking if --disable-cryptography option specified... no checking if --disable-hash option specified... no checking if --disable-mutexsupport option specified... no checking if --disable-queue option specified... no checking if --disable-replication option specified... no checking if --disable-statistics option specified... no checking if --disable-verify option specified... no checking if --enable-compat185 option specified... yes checking if --enable-cxx option specified... yes checking if --enable-debug option specified... no checking if --enable-debug_rop option specified... no checking if --enable-debug_wop option specified... no checking if --enable-diagnostic option specified... no checking if --enable-dump185 option specified... no checking if --enable-java option specified... no checking if --enable-mingw option specified... no checking if --enable-fine_grained_lock_manager option specified... no checking if --enable-o_direct option specified... no checking if --enable-posixmutexes option specified... no checking if --enable-pthread_api option specified... no checking if --enable-rpc option specified... no checking if --enable-smallbuild option specified... no checking if --enable-tcl option specified... no checking if --enable-test option specified... no checking if --enable-uimutexes option specified... no checking if --enable-umrw option specified... no checking if --with-mutex=MUTEX option specified... no checking if --with-tcl=DIR option specified... no checking if --with-uniquename=NAME option specified... no checking for chmod... chmod checking for cp... cp checking for ln... ln checking for mkdir... mkdir checking for rm... rm checking for sh... /bin/sh checking for a BSD-compatible install... /usr/bin/install -c checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for an ANSI C-conforming const... yes checking for inline... inline checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking how to run the C++ preprocessor... g++ -E checking whether C++ supports the ISO C++ standard includes... yes checking whether we are using gcc version 2.96... no checking whether g++ requires -fhandle-exceptions... no checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ld used by gcc... /var/lib/lunar/compilers/ld checking if the linker (/var/lib/lunar/compilers/ld) is GNU ld... yes checking for /var/lib/lunar/compilers/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... cpp checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking how to run the C++ preprocessor... g++ -E checking for g77... no checking for xlf... no checking for f77... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for xlf90... no checking for f90... no checking for pgf90... no checking for pghpf... no checking for epcf90... no checking for gfortran... no checking for g95... no checking for xlf95... no checking for f95... no checking for fort... no checking for ifort... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for ftn... no checking whether we are using the GNU Fortran 77 compiler... no checking whether accepts -g... no checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/var/lib/lunar/compilers/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /var/lib/lunar/compilers/ld checking if the linker (/var/lib/lunar/compilers/ld) is GNU ld... yes checking whether the g++ linker (/var/lib/lunar/compilers/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/var/lib/lunar/compilers/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking SOSUFFIX from libtool... .so checking MODSUFFIX from libtool... .so checking JMODSUFFIX from libtool... .so checking whether stat file-mode macros are broken... no checking whether time.h and sys/time.h may both be included... yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking for struct stat.st_blksize... yes checking for inttypes.h... (cached) yes checking for stdint.h... yes checking if stdint.h can be used by C++... yes checking stddef.h usability... yes checking stddef.h presence... yes checking for stddef.h... yes checking for unistd.h... (cached) yes checking for char... yes checking size of char... 1 checking for unsigned char... yes checking size of unsigned char... 1 checking for short... yes checking size of short... 2 checking for unsigned short... yes checking size of unsigned short... 2 checking for int... yes checking size of int... 4 checking for unsigned int... yes checking size of unsigned int... 4 checking for long... yes checking size of long... 4 checking for unsigned long... yes checking size of unsigned long... 4 checking for long long... yes checking size of long long... 8 checking for unsigned long long... yes checking size of unsigned long long... 8 checking for char *... yes checking size of char *... 4 checking for u_char... yes checking for u_short... yes checking for u_int... yes checking for u_long... yes checking for u_int8_t... yes checking for u_int16_t... yes checking for int16_t... yes checking for u_int32_t... yes checking for int32_t... yes checking for u_int64_t... yes checking for int64_t... yes checking for FILE... yes checking for off_t... yes checking for pid_t... yes checking for size_t... yes checking for time_t... yes checking for size_t... (cached) yes checking size of size_t... 4 checking for ssize_t... yes checking for uintmax_t... yes checking for uintptr_t... yes checking for socklen_t... yes checking for ANSI C exit success/failure values... yes checking for mutexes... POSIX/pthreads/library/x86/gcc-assembly checking for main in -lpthread... yes checking for library containing sched_yield... none required checking for library containing fdatasync... none required checking for library containing getaddrinfo... none required checking for library containing hstrerror... none required checking for main in -lm... yes checking for main in -lnsl... yes checking for main in -lpthread... (cached) yes checking for main in -lsocket... no checking for abort... yes checking for atoi... yes checking for atol... yes checking for getcwd... yes checking for getenv... yes checking for getopt... yes checking for isalpha... yes checking for isdigit... yes checking for isprint... yes checking for isspace... yes checking for memcmp... yes checking for memcpy... yes checking for memmove... yes checking for printf... yes checking for qsort... yes checking for raise... yes checking for rand... yes checking for strcasecmp... yes checking for strcat... yes checking for strchr... yes checking for strdup... yes checking for strerror... yes checking for strncat... yes checking for strncmp... yes checking for strrchr... yes checking for strsep... yes checking for strtol... yes checking for strtoul... yes checking for _fstati64... no checking for directio... no checking for fchmod... yes checking for fclose... yes checking for fcntl... yes checking for fdatasync... yes checking for fgetc... yes checking for fgets... yes checking for fopen... yes checking for fwrite... yes checking for getaddrinfo... yes checking for getrusage... yes checking for gettimeofday... yes checking for getuid... yes checking for hstrerror... yes checking for localtime... yes checking for mprotect... yes checking for pstat_getdynamic... no checking for pthread_yield... yes checking for sched_yield... yes checking for select... yes checking for sigaction... yes checking for snprintf... yes checking for stat... yes checking for strftime... yes checking for sysconf... yes checking for time... yes checking for vsnprintf... yes checking for yield... no checking for ftruncate... yes checking for clock_gettime... no checking for ctime_r... yes checking for 2 or 3 argument version of ctime_r... 2-argument checking for pread... yes checking for pwrite... yes checking for fcntl/F_SETFD... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... 64 checking for mlock... yes checking for munlock... yes checking for mmap... yes checking for munmap... yes checking for shmget... yes checking for 64-bit integral type support for sequences... yes configure: creating ./config.status config.status: creating Makefile config.status: creating db_cxx.h config.status: creating db_int.h config.status: creating clib_port.h config.status: creating include.tcl config.status: creating db.h config.status: creating db_185.h config.status: creating db185_int.h config.status: creating db_config.h + Editing "Makefile" + Editing "Makefile" + running "default_make" ... =============================================================================== root at master ~ # lin -r openldap + Reconfiguring "openldap" + removing all depends for and optional on "openldap" openldap: Use NTLM patch for Windows AD support? [y] + adding "required" depends for "openldap" on "db" (on) + Auto-adding optional dependency "openssl" + adding "optional" depends for "openldap" on "openssl" (on) openldap: Use optional (installed) module cyrus-sasl Purpose: for secure authentication ? [y] n + adding "optional" depends for "openldap" on "cyrus-sasl" (off) openldap: Install & use optional (not installed) module krb5 Purpose: for Kerberos V.5 authentication ? [n] + adding "optional" depends for "openldap" on "krb5" (off) openldap: Use optional (installed) module tcp_wrappers Purpose: for TCP wrapper support ? [y] + adding "optional" depends for "openldap" on "tcp_wrappers" (on) + Spawning download manager + download queue: openldap + starting lin "openldap" Checking dependencies for openldap + downloading module "openldap" + Skipping download of "openldap-2.3.38.tgz" (in cache) + Skipping download of "openldap-2.3.x-ntlm.diff" (in cache) Building openldap version 2.3.38 + running "default_pre_build" + validating "/usr/src/openldap-2.3.38" + creating building dir "/usr/src/openldap-2.3.38" + Removing old source directory first! + Unpacking "/var/spool/lunar/openldap-2.3.38.tgz" in "/usr/src" + building "openldap" version "2.3.38" in /usr/src/openldap-2.3.38 + CC_EXT="ccache " + CXX_EXT="ccache " + CC="gcc" + CXX="g++" + CPP="cpp" + CFLAGS="" + CXXFLAGS="" + CPPFLAGS="" + LDFLAGS=" -s -Wl,-O1" + Enabled wrapper script usage + patch_it "openldap-2.3.x-ntlm.diff" "0" patching file include/ldap.h Hunk http://bugs.lunar-linux.org/view.php?id=1 succeeded at 2118 with fuzz 2 (offset 365 lines). patching file libraries/libldap/Makefile.in Hunk http://bugs.lunar-linux.org/view.php?id=2 From lunar-bugs at lunar-linux.org Sat Oct 11 19:40:08 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sat, 11 Oct 2008 19:40:08 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000320]: qemu cannot build because of gcc version env variable Message-ID: <0368bd074a82ecb49314935e1ab34a5a@bugs.lunar-linux.org> The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=320 ====================================================================== Reported By: gb Assigned To: ====================================================================== Project: Lunar Linux Issue ID: 320 Category: module Reproducibility: always Severity: minor Priority: normal Status: closed Moonbase Version: 20071230.17 Core Tools: Lunar Core Tools Version: 20071211 Resolution: open Fixed in Version: ====================================================================== Date Submitted: 12-31-2007 13:40 CET Last Modified: 10-11-2008 19:40 CEST ====================================================================== Summary: qemu cannot build because of gcc version env variable Description: qemu needs a 3.x.x gcc compiler. I have both the "gcc" and "gcc3" compilers installed, and the default one is 3.4.6 ("which" is the file in /usr/bin/gcc). I am not completely sure if everything is fine in my system, since I cannot use "lunar optimize" to select the compiler & options (see http://bugs.lunar-linux.org/view.php?id=319). I have manually downloaded the qemu_0.9.0 source file and built it successfully on my system. But when I use "lin qemu", I get the error you can see in the attached file. ("ERROR: "/opt/lunar/gcc3/bin/gcc" either does not exist or does not work") Apparently, this code in the BUILD of the qemu module: ${GCC3_PREFIX:-/opt/lunar/gcc3}/bin/gcc expands to something meaningless: "/opt/lunar/gcc3/bin/gcc" What could be done? Is my system broken or that env variable is not correct or is it outdated? ====================================================================== ---------------------------------------------------------------------- gb - 01-12-08 17:30 ---------------------------------------------------------------------- I noticed that qemu has been recently updated from version 0.9.0 to version 0.9.1 . I guess that means that somebody is using it and it works, because the BUILD script is unchanged from version 0.9.0. Could you please let me know if the module can be built correctly on your system? ---------------------------------------------------------------------- florin - 08-22-08 11:04 ---------------------------------------------------------------------- The issue was solved. The module version was bumped recently. Issue History Date Modified Username Field Change ====================================================================== 12-31-07 13:40 gb New Issue 12-31-07 13:40 gb File Added: qemu-0.9.0.bz2 12-31-07 13:40 gb Moonbase Version => 20071230.17 12-31-07 13:40 gb Core Tools => Lunar 12-31-07 13:40 gb Core Tools Version => 20071211 12-31-07 13:40 gb Issue Monitored: gb 01-12-08 17:30 gb Note Added: 0000736 08-22-08 11:04 florin Note Added: 0000816 08-22-08 11:04 florin Status new => resolved 10-11-08 19:40 ratler Status resolved => closed ====================================================================== From lunar-bugs at lunar-linux.org Sat Oct 11 19:40:09 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sat, 11 Oct 2008 19:40:09 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000350]: Cannot Lin Pulseaudio Message-ID: The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=350 ====================================================================== Reported By: Wuss912 Assigned To: ====================================================================== Project: Lunar Linux Issue ID: 350 Category: module Reproducibility: always Severity: minor Priority: normal Status: closed Moonbase Version: 20070704 Core Tools: Lunar Core Tools Version: 20070704 Resolution: open Fixed in Version: ====================================================================== Date Submitted: 07-07-2008 22:01 CEST Last Modified: 10-11-2008 19:40 CEST ====================================================================== Summary: Cannot Lin Pulseaudio Description: getting the same error as http://bugs.gentoo.org/show_bug.cgi?format=multiple&id=215656 ====================================================================== ---------------------------------------------------------------------- dveatch - 07-07-08 22:52 ---------------------------------------------------------------------- pulseaudio-0.9.10 compiled fine here. ---------------------------------------------------------------------- florin - 08-22-08 11:03 ---------------------------------------------------------------------- The module compile and install just fine. Please do a lunar update first. Issue History Date Modified Username Field Change ====================================================================== 07-07-08 22:01 Wuss912 New Issue 07-07-08 22:01 Wuss912 Moonbase Version => 20070704 07-07-08 22:01 Wuss912 Core Tools => Lunar 07-07-08 22:01 Wuss912 Core Tools Version => 20070704 07-07-08 22:52 dveatch Note Added: 0000799 08-18-08 19:14 sofar Severity block => minor 08-22-08 11:03 florin Note Added: 0000815 08-22-08 11:03 florin Status new => resolved 10-11-08 19:40 ratler Status resolved => closed ====================================================================== From lunar-bugs at lunar-linux.org Sat Oct 11 19:40:09 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sat, 11 Oct 2008 19:40:09 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000343]: glib-2 "downgraded" from 16.1 to 14.6 prevents seamonkey to run Message-ID: The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=343 ====================================================================== Reported By: gb Assigned To: florin ====================================================================== Project: Lunar Linux Issue ID: 343 Category: module Reproducibility: always Severity: minor Priority: normal Status: closed Moonbase Version: 20080330.09 Core Tools: Lunar Core Tools Version: 20080303 Resolution: open Fixed in Version: ====================================================================== Date Submitted: 03-30-2008 13:57 CEST Last Modified: 10-11-2008 19:40 CEST ====================================================================== Summary: glib-2 "downgraded" from 16.1 to 14.6 prevents seamonkey to run Description: Seamonkey (both ver 1.1.8 and 1.1.9) requires glib-2 ver 16.1 . Otherwise, it reports: /usr/lib64/libgtk-x11-2.0.so: undefined reference to `g_dpgettext' That happens only when glib-2 gets downgraded from 16.1 to 14.6 . Relining gtk+-2 afterwards does not solve the problem. ====================================================================== ---------------------------------------------------------------------- dveatch - 03-30-08 14:11 ---------------------------------------------------------------------- Yes you need to down grade glib-2 as it suggests. You will most likely need to relin a number of other packages such as, atk, gtk+-2 and a few others of which I forget. How many need a relin depends on how many glib-2 apps/libs you have compiled. Just follow the dependency chain for seamonkey and that might take care of it. ---------------------------------------------------------------------- gb - 04-05-08 19:03 ---------------------------------------------------------------------- Thanks. I resolved this issue by relining these modules (probably more than necessary): glib-2 atk gtk+-2 dbus-glib gamin glibmm libcroco libgsf librsvg ORBit2 libIDL pango pygobject shared-mime-info This bug report can be closed. Gb ---------------------------------------------------------------------- dveatch - 04-05-08 19:33 ---------------------------------------------------------------------- Closed by request of the user as noted by his rebuilding of various modules. ---------------------------------------------------------------------- gb - 05-23-08 20:48 ---------------------------------------------------------------------- Please change status of this bug report to "resolved". Thanks, Gb ---------------------------------------------------------------------- florin - 08-18-08 19:16 ---------------------------------------------------------------------- The current version is 16.5 in the moonbase. The issue is solved now. Issue History Date Modified Username Field Change ====================================================================== 03-30-08 13:57 gb New Issue 03-30-08 13:57 gb Moonbase Version => 20080330.09 03-30-08 13:57 gb Core Tools => Lunar 03-30-08 13:57 gb Core Tools Version => 20080303 03-30-08 13:58 gb Issue Monitored: gb 03-30-08 14:11 dveatch Note Added: 0000783 04-05-08 19:03 gb Note Added: 0000784 04-05-08 19:33 dveatch Note Added: 0000785 05-23-08 20:48 gb Note Added: 0000790 08-18-08 19:16 florin Note Added: 0000811 08-18-08 19:16 florin Assigned To => florin 08-18-08 19:16 florin Status new => assigned 08-22-08 11:01 florin Status assigned => resolved 10-11-08 19:40 ratler Status resolved => closed ====================================================================== From lunar-bugs at lunar-linux.org Sun Oct 12 10:20:52 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sun, 12 Oct 2008 10:20:52 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000252]: swap twice in fstab when using the installer Message-ID: <5639b3267799b72632979d5677d3a760@bugs.lunar-linux.org> The following issue has been RESOLVED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=252 ====================================================================== Reported By: wdp Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 252 Category: ISO Reproducibility: always Severity: minor Priority: normal Status: resolved Moonbase Version: 2006MMDD.NN Core Tools: Lunar Core Tools Version: 2006MMDD Resolution: fixed Fixed in Version: ====================================================================== Date Submitted: 06-03-2007 14:27 CEST Last Modified: 10-12-2008 10:20 CEST ====================================================================== Summary: swap twice in fstab when using the installer Description: If you're using more than one swap device within the installer it's writing them twice to the /etc/fstab file: /dev/hda7 / ext3 defaults 0 1 /dev/hda1 /boot ext3 defaults 0 2 /dev/hda3 none swap sw 0 0 /dev/hdc1 none swap sw 0 0 /dev/hda3 none swap sw 0 0 /dev/hdc1 none swap sw 0 0 /dev/hdc6 /svn ext3 defaults 0 2 /dev/hda5 /usr ext3 defaults 0 2 /dev/hdc3 /var ext3 defaults 0 2 ====================================================================== ---------------------------------------------------------------------- ratler - 09-20-08 08:18 ---------------------------------------------------------------------- Bug confirmed, will have a fix available for 1.6.4-beta1 ---------------------------------------------------------------------- ratler - 10-12-08 10:20 ---------------------------------------------------------------------- Fixed for 1.6.4-beta1 that should be available in a couple of days. Issue History Date Modified Username Field Change ====================================================================== 06-03-07 14:27 wdp New Issue 06-03-07 14:27 wdp Status new => assigned 06-03-07 14:27 wdp Assigned To => sofar 06-03-07 14:27 wdp Moonbase Version => 2006MMDD.NN 06-03-07 14:27 wdp Core Tools => Lunar 06-03-07 14:27 wdp Core Tools Version => 2006MMDD 09-20-08 08:17 ratler Assigned To sofar => ratler 09-20-08 08:18 ratler Note Added: 0000822 09-20-08 08:18 ratler Status assigned => confirmed 10-12-08 10:20 ratler Status confirmed => resolved 10-12-08 10:20 ratler Resolution open => fixed 10-12-08 10:20 ratler Note Added: 0000830 ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 13 18:38:11 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 13 Oct 2008 18:38:11 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000219]: JFS seems not working Message-ID: The following issue has been ASSIGNED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=219 ====================================================================== Reported By: wdp Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 219 Category: ISO Reproducibility: have not tried Severity: minor Priority: normal Status: assigned Moonbase Version: 2006MMDD.NN Core Tools: Lunar Core Tools Version: 2006MMDD ====================================================================== Date Submitted: 04-02-2007 15:23 CEST Last Modified: 10-13-2008 18:38 CEST ====================================================================== Summary: JFS seems not working Description: I tried to use JFS instead of ext3/xfs for a testpartition. When it was at the formatting process it gave an error. It seems that there some problems with the jfsutils or maybe (but i don't think so) missing jfs in kernel. Allthough i think that not many or nearly no one is using jfs, this should be fixed. ====================================================================== ---------------------------------------------------------------------- sofar - 04-02-07 17:08 ---------------------------------------------------------------------- was this when you were booting off of the lunar iso? which version of the iso then? ---------------------------------------------------------------------- wdp - 04-02-07 17:12 ---------------------------------------------------------------------- Yes. I crashed my whole system so i installed it new with the new 1.6.1 moose thingy iso. As a test i wanted to have /dev/hdb3 as /testsys with JFS. I were booting from that ISO. In that Installer i got no error from jfsutils the installer simply said that it had a problem with JFS.. ---------------------------------------------------------------------- sofar - 04-02-07 17:20 ---------------------------------------------------------------------- boot the lunar iso, start a shell and do `grep jfs /proc/filesystems` ---------------------------------------------------------------------- sofar - 04-13-07 08:32 ---------------------------------------------------------------------- test lunar-1.6.2-alpha please for me. Issue History Date Modified Username Field Change ====================================================================== 04-02-07 15:23 wdp New Issue 04-02-07 15:23 wdp Status new => assigned 04-02-07 15:23 wdp Assigned To => sofar 04-02-07 15:23 wdp Moonbase Version => 2006MMDD.NN 04-02-07 15:23 wdp Core Tools => Lunar 04-02-07 15:23 wdp Core Tools Version => 2006MMDD 04-02-07 17:08 sofar Note Added: 0000477 04-02-07 17:08 sofar Status assigned => feedback 04-02-07 17:12 wdp Note Added: 0000478 04-02-07 17:20 sofar Note Added: 0000479 04-13-07 08:32 sofar Note Added: 0000509 10-13-08 18:38 ratler Status feedback => assigned 10-13-08 18:38 ratler Assigned To sofar => ratler ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 13 18:39:13 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 13 Oct 2008 18:39:13 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000219]: JFS seems not working Message-ID: The following issue has been RESOLVED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=219 ====================================================================== Reported By: wdp Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 219 Category: ISO Reproducibility: have not tried Severity: minor Priority: normal Status: resolved Moonbase Version: 2006MMDD.NN Core Tools: Lunar Core Tools Version: 2006MMDD Resolution: fixed Fixed in Version: ====================================================================== Date Submitted: 04-02-2007 15:23 CEST Last Modified: 10-13-2008 18:39 CEST ====================================================================== Summary: JFS seems not working Description: I tried to use JFS instead of ext3/xfs for a testpartition. When it was at the formatting process it gave an error. It seems that there some problems with the jfsutils or maybe (but i don't think so) missing jfs in kernel. Allthough i think that not many or nearly no one is using jfs, this should be fixed. ====================================================================== ---------------------------------------------------------------------- sofar - 04-02-07 17:08 ---------------------------------------------------------------------- was this when you were booting off of the lunar iso? which version of the iso then? ---------------------------------------------------------------------- wdp - 04-02-07 17:12 ---------------------------------------------------------------------- Yes. I crashed my whole system so i installed it new with the new 1.6.1 moose thingy iso. As a test i wanted to have /dev/hdb3 as /testsys with JFS. I were booting from that ISO. In that Installer i got no error from jfsutils the installer simply said that it had a problem with JFS.. ---------------------------------------------------------------------- sofar - 04-02-07 17:20 ---------------------------------------------------------------------- boot the lunar iso, start a shell and do `grep jfs /proc/filesystems` ---------------------------------------------------------------------- sofar - 04-13-07 08:32 ---------------------------------------------------------------------- test lunar-1.6.2-alpha please for me. ---------------------------------------------------------------------- ratler - 10-13-08 18:39 ---------------------------------------------------------------------- This is working just fine with the new 1.6.4-beta1 iso. Closing this old bug. Issue History Date Modified Username Field Change ====================================================================== 04-02-07 15:23 wdp New Issue 04-02-07 15:23 wdp Status new => assigned 04-02-07 15:23 wdp Assigned To => sofar 04-02-07 15:23 wdp Moonbase Version => 2006MMDD.NN 04-02-07 15:23 wdp Core Tools => Lunar 04-02-07 15:23 wdp Core Tools Version => 2006MMDD 04-02-07 17:08 sofar Note Added: 0000477 04-02-07 17:08 sofar Status assigned => feedback 04-02-07 17:12 wdp Note Added: 0000478 04-02-07 17:20 sofar Note Added: 0000479 04-13-07 08:32 sofar Note Added: 0000509 10-13-08 18:38 ratler Status feedback => assigned 10-13-08 18:38 ratler Assigned To sofar => ratler 10-13-08 18:39 ratler Status assigned => resolved 10-13-08 18:39 ratler Resolution open => fixed 10-13-08 18:39 ratler Note Added: 0000831 ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 13 18:40:06 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 13 Oct 2008 18:40:06 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000218]: Cannot use any command Message-ID: <39a9c622c6af657f169eaf57c296aefc@bugs.lunar-linux.org> The following issue has been ASSIGNED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=218 ====================================================================== Reported By: piggy Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 218 Category: kernel Reproducibility: always Severity: major Priority: normal Status: assigned Moonbase Version: 20070331.05 Core Tools: Lunar Core Tools Version: 20070318 ====================================================================== Date Submitted: 04-02-2007 05:14 CEST Last Modified: 10-13-2008 18:40 CEST ====================================================================== Summary: Cannot use any command Description: Dear Sir: I have been updated my server with #lunar -v update (You can see my updated with the attach file) Then I cannot boot my system with new kernel (2.6-stable), the server reported Kernel panic -not syncing: VFS: Unable to mount root fs on unknown-block(8,3) I'm sure I build the new kernel with reiserfs option. I try to boot with old kernel(2.6.20) that provide & recommend by lunar CD. After I login with root account. I cannot use any command with my server. The server will return login promt after I use that command even though reboot command. What should I do about this? Plz advice me for fix it. Best Regards Piggy. ====================================================================== ---------------------------------------------------------------------- sofar - 04-02-07 06:05 ---------------------------------------------------------------------- You mention 2 different problems. Please file a separate bugreport for the -stable kernel issue if you think this is a bug. ---------------------------------------------------------------------- sofar - 04-02-07 06:06 ---------------------------------------------------------------------- Can you mount the filesystems after booting from the lunar install ISO? chroot into your system? ---------------------------------------------------------------------- piggy - 04-03-07 11:56 ---------------------------------------------------------------------- Yep.. I can mount that file system when I boot my server with the recommend kernel-2.6.20 that provided with Lunar CD. But I cannot use any command with my server. The server will return login prompt after I use any command. You can check what program that had been updated from attached file. Best Regards PIggy ---------------------------------------------------------------------- sofar - 04-03-07 16:47 ---------------------------------------------------------------------- This is really hard to debug without seeing any cut'n'paste output. Can you execute any binary after mounting your filesystem from the ISO (but not chrooting?) Do you get any error messages? is /var/log/* showing anything? can you run static binaries (ldconfig?!?!) ---------------------------------------------------------------------- piggy - 04-04-07 04:29 ---------------------------------------------------------------------- Dear Sir: I have to go to another city. I will back after April,13th. Best Regards Piggy. Issue History Date Modified Username Field Change ====================================================================== 04-02-07 05:14 piggy New Issue 04-02-07 05:14 piggy File Added: activity 04-02-07 05:14 piggy Moonbase Version => 20070331.05 04-02-07 05:14 piggy Core Tools => Lunar 04-02-07 05:14 piggy Core Tools Version => 20070318 04-02-07 06:05 sofar Note Added: 0000475 04-02-07 06:06 sofar Note Added: 0000476 04-02-07 23:36 sofar Status new => feedback 04-03-07 11:56 piggy Note Added: 0000480 04-03-07 16:47 sofar Note Added: 0000483 04-04-07 04:29 piggy Note Added: 0000484 10-13-08 18:40 ratler Status feedback => assigned 10-13-08 18:40 ratler Assigned To => ratler ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 13 18:42:23 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 13 Oct 2008 18:42:23 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000218]: Cannot use any command Message-ID: The following issue has been RESOLVED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=218 ====================================================================== Reported By: piggy Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 218 Category: kernel Reproducibility: always Severity: major Priority: normal Status: resolved Moonbase Version: 20070331.05 Core Tools: Lunar Core Tools Version: 20070318 Resolution: won't fix Fixed in Version: ====================================================================== Date Submitted: 04-02-2007 05:14 CEST Last Modified: 10-13-2008 18:42 CEST ====================================================================== Summary: Cannot use any command Description: Dear Sir: I have been updated my server with #lunar -v update (You can see my updated with the attach file) Then I cannot boot my system with new kernel (2.6-stable), the server reported Kernel panic -not syncing: VFS: Unable to mount root fs on unknown-block(8,3) I'm sure I build the new kernel with reiserfs option. I try to boot with old kernel(2.6.20) that provide & recommend by lunar CD. After I login with root account. I cannot use any command with my server. The server will return login promt after I use that command even though reboot command. What should I do about this? Plz advice me for fix it. Best Regards Piggy. ====================================================================== ---------------------------------------------------------------------- sofar - 04-02-07 06:05 ---------------------------------------------------------------------- You mention 2 different problems. Please file a separate bugreport for the -stable kernel issue if you think this is a bug. ---------------------------------------------------------------------- sofar - 04-02-07 06:06 ---------------------------------------------------------------------- Can you mount the filesystems after booting from the lunar install ISO? chroot into your system? ---------------------------------------------------------------------- piggy - 04-03-07 11:56 ---------------------------------------------------------------------- Yep.. I can mount that file system when I boot my server with the recommend kernel-2.6.20 that provided with Lunar CD. But I cannot use any command with my server. The server will return login prompt after I use any command. You can check what program that had been updated from attached file. Best Regards PIggy ---------------------------------------------------------------------- sofar - 04-03-07 16:47 ---------------------------------------------------------------------- This is really hard to debug without seeing any cut'n'paste output. Can you execute any binary after mounting your filesystem from the ISO (but not chrooting?) Do you get any error messages? is /var/log/* showing anything? can you run static binaries (ldconfig?!?!) ---------------------------------------------------------------------- piggy - 04-04-07 04:29 ---------------------------------------------------------------------- Dear Sir: I have to go to another city. I will back after April,13th. Best Regards Piggy. ---------------------------------------------------------------------- ratler - 10-13-08 18:42 ---------------------------------------------------------------------- Closing this bug. Can hardly be relevant anymore since no further feedback have been reported. Issue History Date Modified Username Field Change ====================================================================== 04-02-07 05:14 piggy New Issue 04-02-07 05:14 piggy File Added: activity 04-02-07 05:14 piggy Moonbase Version => 20070331.05 04-02-07 05:14 piggy Core Tools => Lunar 04-02-07 05:14 piggy Core Tools Version => 20070318 04-02-07 06:05 sofar Note Added: 0000475 04-02-07 06:06 sofar Note Added: 0000476 04-02-07 23:36 sofar Status new => feedback 04-03-07 11:56 piggy Note Added: 0000480 04-03-07 16:47 sofar Note Added: 0000483 04-04-07 04:29 piggy Note Added: 0000484 10-13-08 18:40 ratler Status feedback => assigned 10-13-08 18:40 ratler Assigned To => ratler 10-13-08 18:42 ratler Status assigned => resolved 10-13-08 18:42 ratler Resolution open => won't fix 10-13-08 18:42 ratler Note Added: 0000832 ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 13 18:43:27 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 13 Oct 2008 18:43:27 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000251]: some problems with lunar-install when using chroot Message-ID: <66febcab91cc1032cf0a7382177945bb@bugs.lunar-linux.org> The following issue has been ASSIGNED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=251 ====================================================================== Reported By: wdp Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 251 Category: ISO Reproducibility: always Severity: minor Priority: normal Status: assigned Moonbase Version: 2006MMDD.NN Core Tools: Lunar Core Tools Version: 2006MMDD ====================================================================== Date Submitted: 06-03-2007 14:25 CEST Last Modified: 10-13-2008 18:43 CEST ====================================================================== Summary: some problems with lunar-install when using chroot Description: I don't know if it's cause of the chroot, i did it the following way: 1.) downloaded iso 2.) mount -t iso9660 -o loop bla.iso iso 3.) mount --bind /dev/ iso/dev 4.) mount --bind /proc/ iso/proc 5.) chroot iso 6.) mount /dev/pts 7.) mount /tmp 8.) lunar-install Not working is: 1.) Software Raid it's bailing out with a "ARRAY" error 2.) Hostname and Domainname aren't settable (it's jumping to the next menu step, if i go back, it's doing it again) 3.) Networking isn't settable (same like above) 4.) Users aren't settable (same like above) rest is working. ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 06-03-07 14:25 wdp New Issue 06-03-07 14:25 wdp Status new => assigned 06-03-07 14:25 wdp Assigned To => sofar 06-03-07 14:25 wdp Moonbase Version => 2006MMDD.NN 06-03-07 14:25 wdp Core Tools => Lunar 06-03-07 14:25 wdp Core Tools Version => 2006MMDD 10-13-08 18:43 ratler Assigned To sofar => ratler ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 13 18:45:31 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 13 Oct 2008 18:45:31 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000251]: some problems with lunar-install when using chroot Message-ID: <6f70f07e5f10904d32cf80acb005a54a@bugs.lunar-linux.org> The following issue has been RESOLVED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=251 ====================================================================== Reported By: wdp Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 251 Category: ISO Reproducibility: always Severity: minor Priority: normal Status: resolved Moonbase Version: 2006MMDD.NN Core Tools: Lunar Core Tools Version: 2006MMDD Resolution: fixed Fixed in Version: ====================================================================== Date Submitted: 06-03-2007 14:25 CEST Last Modified: 10-13-2008 18:45 CEST ====================================================================== Summary: some problems with lunar-install when using chroot Description: I don't know if it's cause of the chroot, i did it the following way: 1.) downloaded iso 2.) mount -t iso9660 -o loop bla.iso iso 3.) mount --bind /dev/ iso/dev 4.) mount --bind /proc/ iso/proc 5.) chroot iso 6.) mount /dev/pts 7.) mount /tmp 8.) lunar-install Not working is: 1.) Software Raid it's bailing out with a "ARRAY" error 2.) Hostname and Domainname aren't settable (it's jumping to the next menu step, if i go back, it's doing it again) 3.) Networking isn't settable (same like above) 4.) Users aren't settable (same like above) rest is working. ====================================================================== ---------------------------------------------------------------------- ratler - 10-13-08 18:45 ---------------------------------------------------------------------- 1.6.4-beta1 allow you to boot from a usb-stick or other media where the iso recides. If you boot the initrd from the ISO using a usb-stick it will scan the usb-stick and all other partitions that might have a lunar iso and launch the install from it, it basicly does exactly what you demonstrated below :) Issue History Date Modified Username Field Change ====================================================================== 06-03-07 14:25 wdp New Issue 06-03-07 14:25 wdp Status new => assigned 06-03-07 14:25 wdp Assigned To => sofar 06-03-07 14:25 wdp Moonbase Version => 2006MMDD.NN 06-03-07 14:25 wdp Core Tools => Lunar 06-03-07 14:25 wdp Core Tools Version => 2006MMDD 10-13-08 18:43 ratler Assigned To sofar => ratler 10-13-08 18:45 ratler Status assigned => resolved 10-13-08 18:45 ratler Resolution open => fixed 10-13-08 18:45 ratler Note Added: 0000833 ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 13 18:50:56 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 13 Oct 2008 18:50:56 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000353]: view_file doesn't support ISO-8859 text Message-ID: <8461b642b5ee378226c0dc25733fdf91@bugs.lunar-linux.org> The following issue has been ASSIGNED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=353 ====================================================================== Reported By: V4hn Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 353 Category: theedge Reproducibility: always Severity: minor Priority: normal Status: assigned Moonbase Version: 20080720.13 Core Tools: Theedge Core Tools Version: 20080303 ====================================================================== Date Submitted: 07-20-2008 15:36 CEST Last Modified: 10-13-2008 18:50 CEST ====================================================================== Summary: view_file doesn't support ISO-8859 text Description: well, the summary gives it all away.. in /var/lib/lunar/functions/view.lunar there is no case for ISO-8859. Currently there isn't but if there would be a module which does install filenames with ISO-8859 encoding(like 'glest', which i'm currently preparing) `lvu install ` would/does exit without showing an install-log. btw: the defaults for Moonbase Version/Core Tools Version in this bugtracker should be updated(there're still 200_7_) ;) ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 07-20-08 15:36 V4hn New Issue 07-20-08 15:36 V4hn Status new => assigned 07-20-08 15:36 V4hn Assigned To => sofar 07-20-08 15:36 V4hn Moonbase Version => 20080720.13 07-20-08 15:36 V4hn Core Tools => Theedge 07-20-08 15:36 V4hn Core Tools Version => 20080303 08-18-08 19:12 sofar Assigned To sofar => 10-13-08 18:50 ratler Assigned To => ratler ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 13 18:53:08 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 13 Oct 2008 18:53:08 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000262]: Plugin that does exit 1 cause lin to be left hanging Message-ID: The following issue has been ASSIGNED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=262 ====================================================================== Reported By: ratler Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 262 Category: theedge Reproducibility: always Severity: minor Priority: normal Status: assigned Moonbase Version: 20060607.07 Core Tools: Theedge Core Tools Version: 20070408 ====================================================================== Date Submitted: 06-18-2007 07:56 CEST Last Modified: 10-13-2008 18:53 CEST ====================================================================== Summary: Plugin that does exit 1 cause lin to be left hanging Description: If a plugin does an exit 1 instead of just returning an error code the lin process will be left hanging until manually killed. ====================================================================== ---------------------------------------------------------------------- ratler - 08-17-07 07:06 ---------------------------------------------------------------------- Since I think these are related I wont bother opening a new bug. The problem above also happen during a lunar update|renew or when using lin and a module either 1) Fail checksum 2) Fail to download the source. So it's very easy to test it, but it will probably be a bit troublesome locating the error. The problem is confirmed by Moe. Issue History Date Modified Username Field Change ====================================================================== 06-18-07 07:56 ratler New Issue 06-18-07 07:56 ratler Status new => assigned 06-18-07 07:56 ratler Assigned To => sofar 06-18-07 07:56 ratler Moonbase Version => 20060607.07 06-18-07 07:56 ratler Core Tools => Theedge 06-18-07 07:56 ratler Core Tools Version => 20070408 08-17-07 07:06 ratler Note Added: 0000586 08-17-07 07:06 ratler Note Edited: 0000586 10-13-08 18:53 ratler Assigned To sofar => ratler ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 13 19:24:35 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 13 Oct 2008 19:24:35 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000299]: gcc is not installed Message-ID: <4adda093878e6320cb6916855e3dfb81@bugs.lunar-linux.org> The following issue has been ASSIGNED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=299 ====================================================================== Reported By: El_Angelo Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 299 Category: ISO Reproducibility: always Severity: minor Priority: normal Status: assigned Moonbase Version: 20071009.11 so now i'm not an idiot? Core Tools: Lunar Core Tools Version: 20070623 ====================================================================== Date Submitted: 10-10-2007 13:15 CEST Last Modified: 10-13-2008 19:24 CEST ====================================================================== Summary: gcc is not installed Description: lvu info gcc reports that gcc is not installed but still i have installed it a zillion times already. (s/zillion/3/g) samuel at gisoil07 ~ $ lvu info gcc General Module Info Name: gcc Description: GNU compiler collection. Website: http://gcc.gnu.org Lunar Version: 4.1.2 Last Updated: 20070306 Section: compilers Restrictions: sustained solo Installation Info Module not installed. Module Activity History (last 10) 20070223-17:35:47 lrm gcc 4.1.2 success 20070223-17:37:26 lin gcc 4.1.2 success 20070228-16:38:05 lrm gcc 4.1.2 success 20070228-16:39:37 lin gcc 4.1.2 success 20070309-10:11:40 lrm gcc 4.1.2 success 20070309-10:13:22 lin gcc 4.1.2 success 20070418-08:52:03 lrm gcc 4.1.2 success 20070418-08:53:40 lin gcc 4.1.2 success 20070605-07:28:17 lin gcc 4.1.2 success 20070810-14:03:11 lin gcc 4.1.2 success ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 10-10-07 13:15 El_Angelo New Issue 10-10-07 13:15 El_Angelo Status new => assigned 10-10-07 13:15 El_Angelo Assigned To => sofar 10-10-07 13:15 El_Angelo Moonbase Version => 20071009.11 so now i'm not an idiot? 10-10-07 13:15 El_Angelo Core Tools => Lunar 10-10-07 13:15 El_Angelo Core Tools Version => 20070623 10-10-07 13:18 El_Angelo Description Updated 10-13-08 19:24 ratler Assigned To sofar => ratler ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 13 19:25:09 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 13 Oct 2008 19:25:09 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000299]: gcc is not installed Message-ID: <53e6a9c3b24506a919b3cae641c1eb03@bugs.lunar-linux.org> The following issue has been RESOLVED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=299 ====================================================================== Reported By: El_Angelo Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 299 Category: ISO Reproducibility: always Severity: minor Priority: normal Status: resolved Moonbase Version: 20071009.11 so now i'm not an idiot? Core Tools: Lunar Core Tools Version: 20070623 Resolution: unable to reproduce Fixed in Version: ====================================================================== Date Submitted: 10-10-2007 13:15 CEST Last Modified: 10-13-2008 19:25 CEST ====================================================================== Summary: gcc is not installed Description: lvu info gcc reports that gcc is not installed but still i have installed it a zillion times already. (s/zillion/3/g) samuel at gisoil07 ~ $ lvu info gcc General Module Info Name: gcc Description: GNU compiler collection. Website: http://gcc.gnu.org Lunar Version: 4.1.2 Last Updated: 20070306 Section: compilers Restrictions: sustained solo Installation Info Module not installed. Module Activity History (last 10) 20070223-17:35:47 lrm gcc 4.1.2 success 20070223-17:37:26 lin gcc 4.1.2 success 20070228-16:38:05 lrm gcc 4.1.2 success 20070228-16:39:37 lin gcc 4.1.2 success 20070309-10:11:40 lrm gcc 4.1.2 success 20070309-10:13:22 lin gcc 4.1.2 success 20070418-08:52:03 lrm gcc 4.1.2 success 20070418-08:53:40 lin gcc 4.1.2 success 20070605-07:28:17 lin gcc 4.1.2 success 20070810-14:03:11 lin gcc 4.1.2 success ====================================================================== ---------------------------------------------------------------------- ratler - 10-13-08 19:25 ---------------------------------------------------------------------- Elangelo havn't seen this issue anymore, so closing it. Issue History Date Modified Username Field Change ====================================================================== 10-10-07 13:15 El_Angelo New Issue 10-10-07 13:15 El_Angelo Status new => assigned 10-10-07 13:15 El_Angelo Assigned To => sofar 10-10-07 13:15 El_Angelo Moonbase Version => 20071009.11 so now i'm not an idiot? 10-10-07 13:15 El_Angelo Core Tools => Lunar 10-10-07 13:15 El_Angelo Core Tools Version => 20070623 10-10-07 13:18 El_Angelo Description Updated 10-13-08 19:24 ratler Assigned To sofar => ratler 10-13-08 19:25 ratler Status assigned => resolved 10-13-08 19:25 ratler Resolution open => unable to reproduce 10-13-08 19:25 ratler Note Added: 0000834 ====================================================================== From lunar-bugs at lunar-linux.org Tue Oct 14 10:44:00 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Tue, 14 Oct 2008 10:44:00 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000251]: some problems with lunar-install when using chroot In-Reply-To: <6f70f07e5f10904d32cf80acb005a54a@bugs.lunar-linux.org> References: <6f70f07e5f10904d32cf80acb005a54a@bugs.lunar-linux.org> Message-ID: <20081014084400.GA30695@lunar-linux.org> Hello, Yes, I know this is closed, but just on side note, you are missing to mount --bind /sys (only if you haven't only missed saying so and you did mount it). Bye, nestu On Mon, Oct 13, 2008 at 06:45:31PM +0200, Lunar bug reports list wrote: > [ .. ] > 1.) downloaded iso > 2.) mount -t iso9660 -o loop bla.iso iso > 3.) mount --bind /dev/ iso/dev > 4.) mount --bind /proc/ iso/proc > 5.) chroot iso > 6.) mount /dev/pts > 7.) mount /tmp > 8.) lunar-install From lunar-bugs at lunar-linux.org Sat Oct 18 14:00:30 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sat, 18 Oct 2008 14:00:30 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000365]: mirage 0.9 doesn't work anymore after updating python to ver 2.6 Message-ID: <47d83d2363197fe6365d83a134dbaf45@bugs.lunar-linux.org> The following issue has been SUBMITTED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=365 ====================================================================== Reported By: gb Assigned To: ====================================================================== Project: Lunar Linux Issue ID: 365 Category: module Reproducibility: always Severity: minor Priority: normal Status: new Moonbase Version: 20081018.08 Core Tools: Lunar Core Tools Version: 20080303 ====================================================================== Date Submitted: 10-18-2008 14:00 CEST Last Modified: 10-18-2008 14:00 CEST ====================================================================== Summary: mirage 0.9 doesn't work anymore after updating python to ver 2.6 Description: Does mirage like the latest python? I tried re-lining mirage, but is didn't do the trick. Maybe I forgot something important? ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 10-18-08 14:00 gb New Issue 10-18-08 14:00 gb Moonbase Version => 20081018.08 10-18-08 14:00 gb Core Tools => Lunar 10-18-08 14:00 gb Core Tools Version => 20080303 ====================================================================== From lunar-bugs at lunar-linux.org Sun Oct 19 14:47:28 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sun, 19 Oct 2008 14:47:28 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000299]: gcc is not installed Message-ID: <88f645777b95aaf5938998f421218129@bugs.lunar-linux.org> The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=299 ====================================================================== Reported By: El_Angelo Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 299 Category: ISO Reproducibility: always Severity: minor Priority: normal Status: closed Moonbase Version: 20071009.11 so now i'm not an idiot? Core Tools: Lunar Core Tools Version: 20070623 Resolution: unable to reproduce Fixed in Version: ====================================================================== Date Submitted: 10-10-2007 13:15 CEST Last Modified: 10-19-2008 14:47 CEST ====================================================================== Summary: gcc is not installed Description: lvu info gcc reports that gcc is not installed but still i have installed it a zillion times already. (s/zillion/3/g) samuel at gisoil07 ~ $ lvu info gcc General Module Info Name: gcc Description: GNU compiler collection. Website: http://gcc.gnu.org Lunar Version: 4.1.2 Last Updated: 20070306 Section: compilers Restrictions: sustained solo Installation Info Module not installed. Module Activity History (last 10) 20070223-17:35:47 lrm gcc 4.1.2 success 20070223-17:37:26 lin gcc 4.1.2 success 20070228-16:38:05 lrm gcc 4.1.2 success 20070228-16:39:37 lin gcc 4.1.2 success 20070309-10:11:40 lrm gcc 4.1.2 success 20070309-10:13:22 lin gcc 4.1.2 success 20070418-08:52:03 lrm gcc 4.1.2 success 20070418-08:53:40 lin gcc 4.1.2 success 20070605-07:28:17 lin gcc 4.1.2 success 20070810-14:03:11 lin gcc 4.1.2 success ====================================================================== ---------------------------------------------------------------------- ratler - 10-13-08 19:25 ---------------------------------------------------------------------- Elangelo havn't seen this issue anymore, so closing it. Issue History Date Modified Username Field Change ====================================================================== 10-10-07 13:15 El_Angelo New Issue 10-10-07 13:15 El_Angelo Status new => assigned 10-10-07 13:15 El_Angelo Assigned To => sofar 10-10-07 13:15 El_Angelo Moonbase Version => 20071009.11 so now i'm not an idiot? 10-10-07 13:15 El_Angelo Core Tools => Lunar 10-10-07 13:15 El_Angelo Core Tools Version => 20070623 10-10-07 13:18 El_Angelo Description Updated 10-13-08 19:24 ratler Assigned To sofar => ratler 10-13-08 19:25 ratler Status assigned => resolved 10-13-08 19:25 ratler Resolution open => unable to reproduce 10-13-08 19:25 ratler Note Added: 0000834 10-19-08 14:47 ratler Status resolved => closed ====================================================================== From lunar-bugs at lunar-linux.org Sun Oct 19 14:47:28 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sun, 19 Oct 2008 14:47:28 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000251]: some problems with lunar-install when using chroot Message-ID: <6bbc389dc1500bf4f5cbec323be1008b@bugs.lunar-linux.org> The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=251 ====================================================================== Reported By: wdp Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 251 Category: ISO Reproducibility: always Severity: minor Priority: normal Status: closed Moonbase Version: 2006MMDD.NN Core Tools: Lunar Core Tools Version: 2006MMDD Resolution: fixed Fixed in Version: ====================================================================== Date Submitted: 06-03-2007 14:25 CEST Last Modified: 10-19-2008 14:47 CEST ====================================================================== Summary: some problems with lunar-install when using chroot Description: I don't know if it's cause of the chroot, i did it the following way: 1.) downloaded iso 2.) mount -t iso9660 -o loop bla.iso iso 3.) mount --bind /dev/ iso/dev 4.) mount --bind /proc/ iso/proc 5.) chroot iso 6.) mount /dev/pts 7.) mount /tmp 8.) lunar-install Not working is: 1.) Software Raid it's bailing out with a "ARRAY" error 2.) Hostname and Domainname aren't settable (it's jumping to the next menu step, if i go back, it's doing it again) 3.) Networking isn't settable (same like above) 4.) Users aren't settable (same like above) rest is working. ====================================================================== ---------------------------------------------------------------------- ratler - 10-13-08 18:45 ---------------------------------------------------------------------- 1.6.4-beta1 allow you to boot from a usb-stick or other media where the iso recides. If you boot the initrd from the ISO using a usb-stick it will scan the usb-stick and all other partitions that might have a lunar iso and launch the install from it, it basicly does exactly what you demonstrated below :) Issue History Date Modified Username Field Change ====================================================================== 06-03-07 14:25 wdp New Issue 06-03-07 14:25 wdp Status new => assigned 06-03-07 14:25 wdp Assigned To => sofar 06-03-07 14:25 wdp Moonbase Version => 2006MMDD.NN 06-03-07 14:25 wdp Core Tools => Lunar 06-03-07 14:25 wdp Core Tools Version => 2006MMDD 10-13-08 18:43 ratler Assigned To sofar => ratler 10-13-08 18:45 ratler Status assigned => resolved 10-13-08 18:45 ratler Resolution open => fixed 10-13-08 18:45 ratler Note Added: 0000833 10-19-08 14:47 ratler Status resolved => closed ====================================================================== From lunar-bugs at lunar-linux.org Sun Oct 19 14:47:28 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sun, 19 Oct 2008 14:47:28 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000218]: Cannot use any command Message-ID: <4ad8e7a3222a6ae1e5fb0524555d94f4@bugs.lunar-linux.org> The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=218 ====================================================================== Reported By: piggy Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 218 Category: kernel Reproducibility: always Severity: major Priority: normal Status: closed Moonbase Version: 20070331.05 Core Tools: Lunar Core Tools Version: 20070318 Resolution: won't fix Fixed in Version: ====================================================================== Date Submitted: 04-02-2007 05:14 CEST Last Modified: 10-19-2008 14:47 CEST ====================================================================== Summary: Cannot use any command Description: Dear Sir: I have been updated my server with #lunar -v update (You can see my updated with the attach file) Then I cannot boot my system with new kernel (2.6-stable), the server reported Kernel panic -not syncing: VFS: Unable to mount root fs on unknown-block(8,3) I'm sure I build the new kernel with reiserfs option. I try to boot with old kernel(2.6.20) that provide & recommend by lunar CD. After I login with root account. I cannot use any command with my server. The server will return login promt after I use that command even though reboot command. What should I do about this? Plz advice me for fix it. Best Regards Piggy. ====================================================================== ---------------------------------------------------------------------- sofar - 04-02-07 06:05 ---------------------------------------------------------------------- You mention 2 different problems. Please file a separate bugreport for the -stable kernel issue if you think this is a bug. ---------------------------------------------------------------------- sofar - 04-02-07 06:06 ---------------------------------------------------------------------- Can you mount the filesystems after booting from the lunar install ISO? chroot into your system? ---------------------------------------------------------------------- piggy - 04-03-07 11:56 ---------------------------------------------------------------------- Yep.. I can mount that file system when I boot my server with the recommend kernel-2.6.20 that provided with Lunar CD. But I cannot use any command with my server. The server will return login prompt after I use any command. You can check what program that had been updated from attached file. Best Regards PIggy ---------------------------------------------------------------------- sofar - 04-03-07 16:47 ---------------------------------------------------------------------- This is really hard to debug without seeing any cut'n'paste output. Can you execute any binary after mounting your filesystem from the ISO (but not chrooting?) Do you get any error messages? is /var/log/* showing anything? can you run static binaries (ldconfig?!?!) ---------------------------------------------------------------------- piggy - 04-04-07 04:29 ---------------------------------------------------------------------- Dear Sir: I have to go to another city. I will back after April,13th. Best Regards Piggy. ---------------------------------------------------------------------- ratler - 10-13-08 18:42 ---------------------------------------------------------------------- Closing this bug. Can hardly be relevant anymore since no further feedback have been reported. Issue History Date Modified Username Field Change ====================================================================== 04-02-07 05:14 piggy New Issue 04-02-07 05:14 piggy File Added: activity 04-02-07 05:14 piggy Moonbase Version => 20070331.05 04-02-07 05:14 piggy Core Tools => Lunar 04-02-07 05:14 piggy Core Tools Version => 20070318 04-02-07 06:05 sofar Note Added: 0000475 04-02-07 06:06 sofar Note Added: 0000476 04-02-07 23:36 sofar Status new => feedback 04-03-07 11:56 piggy Note Added: 0000480 04-03-07 16:47 sofar Note Added: 0000483 04-04-07 04:29 piggy Note Added: 0000484 10-13-08 18:40 ratler Status feedback => assigned 10-13-08 18:40 ratler Assigned To => ratler 10-13-08 18:42 ratler Status assigned => resolved 10-13-08 18:42 ratler Resolution open => won't fix 10-13-08 18:42 ratler Note Added: 0000832 10-19-08 14:47 ratler Status resolved => closed ====================================================================== From lunar-bugs at lunar-linux.org Sun Oct 19 14:47:29 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sun, 19 Oct 2008 14:47:29 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000219]: JFS seems not working Message-ID: The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=219 ====================================================================== Reported By: wdp Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 219 Category: ISO Reproducibility: have not tried Severity: minor Priority: normal Status: closed Moonbase Version: 2006MMDD.NN Core Tools: Lunar Core Tools Version: 2006MMDD Resolution: fixed Fixed in Version: ====================================================================== Date Submitted: 04-02-2007 15:23 CEST Last Modified: 10-19-2008 14:47 CEST ====================================================================== Summary: JFS seems not working Description: I tried to use JFS instead of ext3/xfs for a testpartition. When it was at the formatting process it gave an error. It seems that there some problems with the jfsutils or maybe (but i don't think so) missing jfs in kernel. Allthough i think that not many or nearly no one is using jfs, this should be fixed. ====================================================================== ---------------------------------------------------------------------- sofar - 04-02-07 17:08 ---------------------------------------------------------------------- was this when you were booting off of the lunar iso? which version of the iso then? ---------------------------------------------------------------------- wdp - 04-02-07 17:12 ---------------------------------------------------------------------- Yes. I crashed my whole system so i installed it new with the new 1.6.1 moose thingy iso. As a test i wanted to have /dev/hdb3 as /testsys with JFS. I were booting from that ISO. In that Installer i got no error from jfsutils the installer simply said that it had a problem with JFS.. ---------------------------------------------------------------------- sofar - 04-02-07 17:20 ---------------------------------------------------------------------- boot the lunar iso, start a shell and do `grep jfs /proc/filesystems` ---------------------------------------------------------------------- sofar - 04-13-07 08:32 ---------------------------------------------------------------------- test lunar-1.6.2-alpha please for me. ---------------------------------------------------------------------- ratler - 10-13-08 18:39 ---------------------------------------------------------------------- This is working just fine with the new 1.6.4-beta1 iso. Closing this old bug. Issue History Date Modified Username Field Change ====================================================================== 04-02-07 15:23 wdp New Issue 04-02-07 15:23 wdp Status new => assigned 04-02-07 15:23 wdp Assigned To => sofar 04-02-07 15:23 wdp Moonbase Version => 2006MMDD.NN 04-02-07 15:23 wdp Core Tools => Lunar 04-02-07 15:23 wdp Core Tools Version => 2006MMDD 04-02-07 17:08 sofar Note Added: 0000477 04-02-07 17:08 sofar Status assigned => feedback 04-02-07 17:12 wdp Note Added: 0000478 04-02-07 17:20 sofar Note Added: 0000479 04-13-07 08:32 sofar Note Added: 0000509 10-13-08 18:38 ratler Status feedback => assigned 10-13-08 18:38 ratler Assigned To sofar => ratler 10-13-08 18:39 ratler Status assigned => resolved 10-13-08 18:39 ratler Resolution open => fixed 10-13-08 18:39 ratler Note Added: 0000831 10-19-08 14:47 ratler Status resolved => closed ====================================================================== From lunar-bugs at lunar-linux.org Sun Oct 19 14:47:29 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sun, 19 Oct 2008 14:47:29 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000252]: swap twice in fstab when using the installer Message-ID: The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=252 ====================================================================== Reported By: wdp Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 252 Category: ISO Reproducibility: always Severity: minor Priority: normal Status: closed Moonbase Version: 2006MMDD.NN Core Tools: Lunar Core Tools Version: 2006MMDD Resolution: fixed Fixed in Version: ====================================================================== Date Submitted: 06-03-2007 14:27 CEST Last Modified: 10-19-2008 14:47 CEST ====================================================================== Summary: swap twice in fstab when using the installer Description: If you're using more than one swap device within the installer it's writing them twice to the /etc/fstab file: /dev/hda7 / ext3 defaults 0 1 /dev/hda1 /boot ext3 defaults 0 2 /dev/hda3 none swap sw 0 0 /dev/hdc1 none swap sw 0 0 /dev/hda3 none swap sw 0 0 /dev/hdc1 none swap sw 0 0 /dev/hdc6 /svn ext3 defaults 0 2 /dev/hda5 /usr ext3 defaults 0 2 /dev/hdc3 /var ext3 defaults 0 2 ====================================================================== ---------------------------------------------------------------------- ratler - 09-20-08 08:18 ---------------------------------------------------------------------- Bug confirmed, will have a fix available for 1.6.4-beta1 ---------------------------------------------------------------------- ratler - 10-12-08 10:20 ---------------------------------------------------------------------- Fixed for 1.6.4-beta1 that should be available in a couple of days. Issue History Date Modified Username Field Change ====================================================================== 06-03-07 14:27 wdp New Issue 06-03-07 14:27 wdp Status new => assigned 06-03-07 14:27 wdp Assigned To => sofar 06-03-07 14:27 wdp Moonbase Version => 2006MMDD.NN 06-03-07 14:27 wdp Core Tools => Lunar 06-03-07 14:27 wdp Core Tools Version => 2006MMDD 09-20-08 08:17 ratler Assigned To sofar => ratler 09-20-08 08:18 ratler Note Added: 0000822 09-20-08 08:18 ratler Status assigned => confirmed 10-12-08 10:20 ratler Status confirmed => resolved 10-12-08 10:20 ratler Resolution open => fixed 10-12-08 10:20 ratler Note Added: 0000830 10-19-08 14:47 ratler Status resolved => closed ====================================================================== From lunar-bugs at lunar-linux.org Sun Oct 19 22:37:39 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sun, 19 Oct 2008 22:37:39 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000366]: lvu install shows nothing if install log not common file type Message-ID: <6d0c13ee4433a3af77d509a3a4422500@bugs.lunar-linux.org> The following issue has been SUBMITTED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=366 ====================================================================== Reported By: engelsman Assigned To: sofar ====================================================================== Project: Lunar Linux Issue ID: 366 Category: theedge Reproducibility: always Severity: minor Priority: normal Status: assigned Moonbase Version: 20081019.12 Core Tools: Theedge Core Tools Version: 20080303 ====================================================================== Date Submitted: 10-19-2008 22:37 CEST Last Modified: 10-19-2008 22:37 CEST ====================================================================== Summary: lvu install shows nothing if install log not common file type Description: Just discovered this with new glest submission. lvu install glest shows nothing, but install log exists. install log file type is not handled by view_file function ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 10-19-08 22:37 engelsman New Issue 10-19-08 22:37 engelsman Status new => assigned 10-19-08 22:37 engelsman Assigned To => sofar 10-19-08 22:37 engelsman Moonbase Version => 20081019.12 10-19-08 22:37 engelsman Core Tools => Theedge 10-19-08 22:37 engelsman Core Tools Version => 20080303 ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 20 06:37:36 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 20 Oct 2008 06:37:36 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000366]: lvu install shows nothing if install log not common file type Message-ID: <5058ccc0518a8c86e7eae5ccbc0a23a9@bugs.lunar-linux.org> The following issue has been set as DUPLICATE OF issue 0000353. ====================================================================== http://bugs.lunar-linux.org/view.php?id=366 ====================================================================== Reported By: engelsman Assigned To: sofar ====================================================================== Project: Lunar Linux Issue ID: 366 Category: theedge Reproducibility: always Severity: minor Priority: normal Status: assigned Moonbase Version: 20081019.12 Core Tools: Theedge Core Tools Version: 20080303 ====================================================================== Date Submitted: 10-19-2008 22:37 CEST Last Modified: 10-20-2008 06:37 CEST ====================================================================== Summary: lvu install shows nothing if install log not common file type Description: Just discovered this with new glest submission. lvu install glest shows nothing, but install log exists. install log file type is not handled by view_file function ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- duplicate of 0000353 view_file doesn't support ISO-8859 text ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 10-19-08 22:37 engelsman New Issue 10-19-08 22:37 engelsman Status new => assigned 10-19-08 22:37 engelsman Assigned To => sofar 10-19-08 22:37 engelsman Moonbase Version => 20081019.12 10-19-08 22:37 engelsman Core Tools => Theedge 10-19-08 22:37 engelsman Core Tools Version => 20080303 10-20-08 06:37 ratler Relationship added duplicate of 0000353 ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 20 06:37:37 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 20 Oct 2008 06:37:37 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000353]: view_file doesn't support ISO-8859 text Message-ID: The issue 0000366 has been set as DUPLICATE OF the following issue. ====================================================================== http://bugs.lunar-linux.org/view.php?id=353 ====================================================================== Reported By: V4hn Assigned To: ratler ====================================================================== Project: Lunar Linux Issue ID: 353 Category: theedge Reproducibility: always Severity: minor Priority: normal Status: assigned Moonbase Version: 20080720.13 Core Tools: Theedge Core Tools Version: 20080303 ====================================================================== Date Submitted: 07-20-2008 15:36 CEST Last Modified: 10-13-2008 18:50 CEST ====================================================================== Summary: view_file doesn't support ISO-8859 text Description: well, the summary gives it all away.. in /var/lib/lunar/functions/view.lunar there is no case for ISO-8859. Currently there isn't but if there would be a module which does install filenames with ISO-8859 encoding(like 'glest', which i'm currently preparing) `lvu install ` would/does exit without showing an install-log. btw: the defaults for Moonbase Version/Core Tools Version in this bugtracker should be updated(there're still 200_7_) ;) ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- has duplicate 0000366 lvu install shows nothing if install lo... ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 07-20-08 15:36 V4hn New Issue 07-20-08 15:36 V4hn Status new => assigned 07-20-08 15:36 V4hn Assigned To => sofar 07-20-08 15:36 V4hn Moonbase Version => 20080720.13 07-20-08 15:36 V4hn Core Tools => Theedge 07-20-08 15:36 V4hn Core Tools Version => 20080303 08-18-08 19:12 sofar Assigned To sofar => 10-13-08 18:50 ratler Assigned To => ratler 10-20-08 06:37 ratler Relationship added has duplicate 0000366 ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 20 07:25:05 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 20 Oct 2008 07:25:05 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000366]: lvu install shows nothing if install log not common file type Message-ID: <18d76d1a73eb2428e13a6b643788f8d6@bugs.lunar-linux.org> The following issue has been UPDATED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=366 ====================================================================== Reported By: engelsman Assigned To: sofar ====================================================================== Project: Lunar Linux Issue ID: 366 Category: theedge Reproducibility: always Severity: minor Priority: normal Status: assigned Moonbase Version: 20081019.12 Core Tools: Theedge Core Tools Version: 20080303 ====================================================================== Date Submitted: 10-19-2008 22:37 CEST Last Modified: 10-20-2008 07:25 CEST ====================================================================== Summary: lvu install shows nothing if install log not common file type Description: Just discovered this with new glest submission. lvu install glest shows nothing, but install log exists. install log file type is not handled by view_file function ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- duplicate of 0000353 view_file doesn't support ISO-8859 text ====================================================================== ---------------------------------------------------------------------- engelsman - 10-20-08 07:25 ---------------------------------------------------------------------- closing duplicate Issue History Date Modified Username Field Change ====================================================================== 10-19-08 22:37 engelsman New Issue 10-19-08 22:37 engelsman Status new => assigned 10-19-08 22:37 engelsman Assigned To => sofar 10-19-08 22:37 engelsman Moonbase Version => 20081019.12 10-19-08 22:37 engelsman Core Tools => Theedge 10-19-08 22:37 engelsman Core Tools Version => 20080303 10-20-08 06:37 ratler Relationship added duplicate of 0000353 10-20-08 07:25 engelsman Note Added: 0000835 ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 20 07:26:49 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 20 Oct 2008 07:26:49 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000366]: lvu install shows nothing if install log not common file type Message-ID: <3482509fa6d20af6b18fc2ac3d241a1f@bugs.lunar-linux.org> The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=366 ====================================================================== Reported By: engelsman Assigned To: sofar ====================================================================== Project: Lunar Linux Issue ID: 366 Category: theedge Reproducibility: always Severity: minor Priority: normal Status: closed Moonbase Version: 20081019.12 Core Tools: Theedge Core Tools Version: 20080303 Resolution: duplicate Duplicate: 0 Fixed in Version: ====================================================================== Date Submitted: 10-19-2008 22:37 CEST Last Modified: 10-20-2008 07:26 CEST ====================================================================== Summary: lvu install shows nothing if install log not common file type Description: Just discovered this with new glest submission. lvu install glest shows nothing, but install log exists. install log file type is not handled by view_file function ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- duplicate of 0000353 view_file doesn't support ISO-8859 text ====================================================================== ---------------------------------------------------------------------- engelsman - 10-20-08 07:25 ---------------------------------------------------------------------- closing duplicate ---------------------------------------------------------------------- engelsman - 10-20-08 07:26 ---------------------------------------------------------------------- closing duplicate II Issue History Date Modified Username Field Change ====================================================================== 10-19-08 22:37 engelsman New Issue 10-19-08 22:37 engelsman Status new => assigned 10-19-08 22:37 engelsman Assigned To => sofar 10-19-08 22:37 engelsman Moonbase Version => 20081019.12 10-19-08 22:37 engelsman Core Tools => Theedge 10-19-08 22:37 engelsman Core Tools Version => 20080303 10-20-08 06:37 ratler Relationship added duplicate of 0000353 10-20-08 07:25 engelsman Note Added: 0000835 10-20-08 07:26 engelsman Note Added: 0000836 10-20-08 07:26 engelsman Status assigned => closed 10-20-08 07:26 engelsman Resolution open => duplicate ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 20 09:57:27 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 20 Oct 2008 09:57:27 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000365]: mirage 0.9 doesn't work anymore after updating python to ver 2.6 Message-ID: The following issue has been UPDATED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=365 ====================================================================== Reported By: gb Assigned To: ====================================================================== Project: Lunar Linux Issue ID: 365 Category: module Reproducibility: always Severity: minor Priority: normal Status: new Moonbase Version: 20081018.08 Core Tools: Lunar Core Tools Version: 20080303 ====================================================================== Date Submitted: 10-18-2008 14:00 CEST Last Modified: 10-20-2008 09:57 CEST ====================================================================== Summary: mirage 0.9 doesn't work anymore after updating python to ver 2.6 Description: Does mirage like the latest python? I tried re-lining mirage, but is didn't do the trick. Maybe I forgot something important? ====================================================================== ---------------------------------------------------------------------- engelsman - 10-20-08 09:57 ---------------------------------------------------------------------- Javier Adrian Ortiz de la Tabla submitted an update to 0.9.3 This builds for me, although there are warnings at run-time. Can you please confirm that it builds for you? Issue History Date Modified Username Field Change ====================================================================== 10-18-08 14:00 gb New Issue 10-18-08 14:00 gb Moonbase Version => 20081018.08 10-18-08 14:00 gb Core Tools => Lunar 10-18-08 14:00 gb Core Tools Version => 20080303 10-18-08 14:01 gb Issue Monitored: gb 10-20-08 09:57 engelsman Note Added: 0000837 ====================================================================== From lunar-bugs at lunar-linux.org Mon Oct 20 10:00:13 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Mon, 20 Oct 2008 10:00:13 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000365]: mirage 0.9 doesn't work anymore after updating python to ver 2.6 Message-ID: <292dbe4b66406bc5a4370a69eaba7db3@bugs.lunar-linux.org> The following issue has been RESOLVED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=365 ====================================================================== Reported By: gb Assigned To: ====================================================================== Project: Lunar Linux Issue ID: 365 Category: module Reproducibility: always Severity: minor Priority: normal Status: resolved Moonbase Version: 20081018.08 Core Tools: Lunar Core Tools Version: 20080303 Resolution: open Fixed in Version: ====================================================================== Date Submitted: 10-18-2008 14:00 CEST Last Modified: 10-20-2008 10:00 CEST ====================================================================== Summary: mirage 0.9 doesn't work anymore after updating python to ver 2.6 Description: Does mirage like the latest python? I tried re-lining mirage, but is didn't do the trick. Maybe I forgot something important? ====================================================================== ---------------------------------------------------------------------- engelsman - 10-20-08 09:57 ---------------------------------------------------------------------- Javier Adrian Ortiz de la Tabla submitted an update to 0.9.3 This builds for me, although there are warnings at run-time. Can you please confirm that it builds for you? ---------------------------------------------------------------------- engelsman - 10-20-08 10:00 ---------------------------------------------------------------------- should be fixed Issue History Date Modified Username Field Change ====================================================================== 10-18-08 14:00 gb New Issue 10-18-08 14:00 gb Moonbase Version => 20081018.08 10-18-08 14:00 gb Core Tools => Lunar 10-18-08 14:00 gb Core Tools Version => 20080303 10-18-08 14:01 gb Issue Monitored: gb 10-20-08 09:57 engelsman Note Added: 0000837 10-20-08 10:00 engelsman Note Added: 0000838 10-20-08 10:00 engelsman Status new => resolved ====================================================================== From lunar-bugs at lunar-linux.org Thu Oct 23 18:47:21 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Thu, 23 Oct 2008 18:47:21 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000367]: MythTV Message-ID: <3c6ade8b3587da0917b33861ff51ae9e@bugs.lunar-linux.org> The following issue has been SUBMITTED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=367 ====================================================================== Reported By: El_Angelo Assigned To: ====================================================================== Project: Lunar Linux Issue ID: 367 Category: module Reproducibility: always Severity: minor Priority: normal Status: new Moonbase Version: 2008GIT MASTER Core Tools: Theedge Core Tools Version: 20080303 ====================================================================== Date Submitted: 10-23-2008 18:47 CEST Last Modified: 10-23-2008 18:47 CEST ====================================================================== Summary: MythTV Description: the mythtv module has optional_depends on mythtv_plugins and mythtv_themes modules... both of them should have actual hard dependencies on mythtv (both of them fail compilation if mythtv is not installed) ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 10-23-08 18:47 El_Angelo New Issue 10-23-08 18:47 El_Angelo Moonbase Version => 2008GIT MASTER 10-23-08 18:47 El_Angelo Core Tools => Theedge 10-23-08 18:47 El_Angelo Core Tools Version => 20080303 ====================================================================== From lunar-bugs at lunar-linux.org Thu Oct 23 18:47:31 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Thu, 23 Oct 2008 18:47:31 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000367]: MythTV Message-ID: The following issue has been ASSIGNED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=367 ====================================================================== Reported By: El_Angelo Assigned To: Striker ====================================================================== Project: Lunar Linux Issue ID: 367 Category: module Reproducibility: always Severity: minor Priority: normal Status: assigned Moonbase Version: 2008GIT MASTER Core Tools: Theedge Core Tools Version: 20080303 ====================================================================== Date Submitted: 10-23-2008 18:47 CEST Last Modified: 10-23-2008 18:47 CEST ====================================================================== Summary: MythTV Description: the mythtv module has optional_depends on mythtv_plugins and mythtv_themes modules... both of them should have actual hard dependencies on mythtv (both of them fail compilation if mythtv is not installed) ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 10-23-08 18:47 El_Angelo New Issue 10-23-08 18:47 El_Angelo Moonbase Version => 2008GIT MASTER 10-23-08 18:47 El_Angelo Core Tools => Theedge 10-23-08 18:47 El_Angelo Core Tools Version => 20080303 10-23-08 18:47 El_Angelo Status new => assigned 10-23-08 18:47 El_Angelo Assigned To => Striker ====================================================================== From lunar-bugs at lunar-linux.org Sat Oct 25 17:06:24 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sat, 25 Oct 2008 17:06:24 +0200 Subject: [Lunar-bugs] [Lunar Linux 0000368]: Cannot build blender 2.48 Message-ID: <24406e40344afac0c7036104742169b5@bugs.lunar-linux.org> The following issue has been SUBMITTED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=368 ====================================================================== Reported By: gb Assigned To: ====================================================================== Project: Lunar Linux Issue ID: 368 Category: module Reproducibility: always Severity: minor Priority: normal Status: new Moonbase Version: 20081025.14 Core Tools: Lunar Core Tools Version: 20080303 ====================================================================== Date Submitted: 10-25-2008 17:06 CEST Last Modified: 10-25-2008 17:06 CEST ====================================================================== Summary: Cannot build blender 2.48 Description: > lin blender ... Compiling ==> 'modifier.c' Compiling ==> 'icons.c' Compiling ==> 'constraint.c' Compiling ==> 'nla.c' Compiling ==> 'sca.c' Compiling ==> 'colortools.c' Compiling ==> 'node.c' source/blender/blenkernel/intern/node.c:30:20: error: Python.h: No such file or directory scons: *** [build/source/blender/blenkernel/intern/node.o] Error 1 scons: building terminated because of errors. Creating /var/log/lunar/compile/blender-2.48.bz2 ! Problem detected during BUILD I also attach the full compile log. ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 10-25-08 17:06 gb New Issue 10-25-08 17:06 gb File Added: blender-2.48.bz2 10-25-08 17:06 gb Moonbase Version => 20081025.14 10-25-08 17:06 gb Core Tools => Lunar 10-25-08 17:06 gb Core Tools Version => 20080303 ====================================================================== From lunar-bugs at lunar-linux.org Sun Oct 26 18:13:05 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sun, 26 Oct 2008 18:13:05 +0100 Subject: [Lunar-bugs] [Lunar Linux 0000368]: Cannot build blender 2.48 Message-ID: A NOTE has been added to this issue. ====================================================================== http://bugs.lunar-linux.org/view.php?id=368 ====================================================================== Reported By: gb Assigned To: ====================================================================== Project: Lunar Linux Issue ID: 368 Category: module Reproducibility: always Severity: minor Priority: normal Status: new Moonbase Version: 20081025.14 Core Tools: Lunar Core Tools Version: 20080303 ====================================================================== Date Submitted: 10-25-2008 17:06 CEST Last Modified: 10-26-2008 18:13 CET ====================================================================== Summary: Cannot build blender 2.48 Description: > lin blender ... Compiling ==> 'modifier.c' Compiling ==> 'icons.c' Compiling ==> 'constraint.c' Compiling ==> 'nla.c' Compiling ==> 'sca.c' Compiling ==> 'colortools.c' Compiling ==> 'node.c' source/blender/blenkernel/intern/node.c:30:20: error: Python.h: No such file or directory scons: *** [build/source/blender/blenkernel/intern/node.o] Error 1 scons: building terminated because of errors. Creating /var/log/lunar/compile/blender-2.48.bz2 ! Problem detected during BUILD I also attach the full compile log. ====================================================================== ---------------------------------------------------------------------- engelsman - 10-26-08 18:13 ---------------------------------------------------------------------- What happens if you 'lvu edit blender' [*] cd /var/lib/lunar/moonbase/zlocal/blender edit BUILD, and change the sedit line from 2.5 to 2.5 lin blender ? [*] You might first need to set ZLOCAL_OVERRIDES to ON see lunar / Options / Feature Menu / ZLOCAL_OVERRIDES Issue History Date Modified Username Field Change ====================================================================== 10-25-08 17:06 gb New Issue 10-25-08 17:06 gb File Added: blender-2.48.bz2 10-25-08 17:06 gb Moonbase Version => 20081025.14 10-25-08 17:06 gb Core Tools => Lunar 10-25-08 17:06 gb Core Tools Version => 20080303 10-25-08 17:07 gb Issue Monitored: gb 10-26-08 18:13 engelsman Note Added: 0000839 ====================================================================== From lunar-bugs at lunar-linux.org Sun Oct 26 22:19:04 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Sun, 26 Oct 2008 22:19:04 +0100 Subject: [Lunar-bugs] [Lunar Linux 0000368]: Cannot build blender 2.48 Message-ID: <12fa7681457c71571cf609d9888fa200@bugs.lunar-linux.org> A NOTE has been added to this issue. ====================================================================== http://bugs.lunar-linux.org/view.php?id=368 ====================================================================== Reported By: gb Assigned To: ====================================================================== Project: Lunar Linux Issue ID: 368 Category: module Reproducibility: always Severity: minor Priority: normal Status: new Moonbase Version: 20081025.14 Core Tools: Lunar Core Tools Version: 20080303 ====================================================================== Date Submitted: 10-25-2008 17:06 CEST Last Modified: 10-26-2008 22:19 CET ====================================================================== Summary: Cannot build blender 2.48 Description: > lin blender ... Compiling ==> 'modifier.c' Compiling ==> 'icons.c' Compiling ==> 'constraint.c' Compiling ==> 'nla.c' Compiling ==> 'sca.c' Compiling ==> 'colortools.c' Compiling ==> 'node.c' source/blender/blenkernel/intern/node.c:30:20: error: Python.h: No such file or directory scons: *** [build/source/blender/blenkernel/intern/node.o] Error 1 scons: building terminated because of errors. Creating /var/log/lunar/compile/blender-2.48.bz2 ! Problem detected during BUILD I also attach the full compile log. ====================================================================== ---------------------------------------------------------------------- engelsman - 10-26-08 19:45 ---------------------------------------------------------------------- What happens if you 'lvu edit blender' [*] cd /var/lib/lunar/moonbase/zlocal/blender edit BUILD, and change the sedit line from 2.5 to 2.6 lin blender ? [*] You might first need to set ZLOCAL_OVERRIDES to ON see lunar / Options / Feature Menu / ZLOCAL_OVERRIDES ---------------------------------------------------------------------- gb - 10-26-08 22:19 ---------------------------------------------------------------------- Thanks, it did the trick! In blender's "BUILD", I changed: - sedit "s:2.4:2.5:" config/linux2-config.py && + sedit "s:2.5:2.6:" config/linux2-config.py && I have submitted the patched module with "lvu submit blender". Gb Issue History Date Modified Username Field Change ====================================================================== 10-25-08 17:06 gb New Issue 10-25-08 17:06 gb File Added: blender-2.48.bz2 10-25-08 17:06 gb Moonbase Version => 20081025.14 10-25-08 17:06 gb Core Tools => Lunar 10-25-08 17:06 gb Core Tools Version => 20080303 10-25-08 17:07 gb Issue Monitored: gb 10-26-08 18:13 engelsman Note Added: 0000839 10-26-08 19:45 engelsman Note Edited: 0000839 10-26-08 22:19 gb Note Added: 0000840 ====================================================================== From lunar-bugs at lunar-linux.org Tue Oct 28 05:10:43 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Tue, 28 Oct 2008 05:10:43 +0100 Subject: [Lunar-bugs] [Lunar Linux 0000369]: xf86-video-intel-git install Message-ID: <426c870492b08cb5a48902f0b6c36926@bugs.lunar-linux.org> The following issue has been SUBMITTED. ====================================================================== http://bugs.lunar-linux.org/view.php?id=369 ====================================================================== Reported By: kaexsar Assigned To: ====================================================================== Project: Lunar Linux Issue ID: 369 Category: module Reproducibility: always Severity: minor Priority: normal Status: new Moonbase Version: 20081028.01 Core Tools: Lunar Core Tools Version: 20080303 ====================================================================== Date Submitted: 10-28-2008 05:10 CET Last Modified: 10-28-2008 05:10 CET ====================================================================== Summary: xf86-video-intel-git install Description: Error while installing module xf86-video-intel-git. error: pathspec 'modesetting' did not match any file(s) known to git. ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 10-28-08 05:10 kaexsar New Issue 10-28-08 05:10 kaexsar Moonbase Version => 20081028.01 10-28-08 05:10 kaexsar Core Tools => Lunar 10-28-08 05:10 kaexsar Core Tools Version => 20080303 ====================================================================== From lunar-bugs at lunar-linux.org Tue Oct 28 08:38:55 2008 From: lunar-bugs at lunar-linux.org (Lunar bug reports list) Date: Tue, 28 Oct 2008 08:38:55 +0100 Subject: [Lunar-bugs] [Lunar Linux 0000369]: xf86-video-intel-git install Message-ID: <86fb44ed2e6f636c3905c2efb3c49867@bugs.lunar-linux.org> The following issue has been CLOSED ====================================================================== http://bugs.lunar-linux.org/view.php?id=369 ====================================================================== Reported By: kaexsar Assigned To: ====================================================================== Project: Lunar Linux Issue ID: 369 Category: module Reproducibility: always Severity: minor Priority: normal Status: closed Moonbase Version: 20081028.01 Core Tools: Lunar Core Tools Version: 20080303 Resolution: open Fixed in Version: ====================================================================== Date Submitted: 10-28-2008 05:10 CET Last Modified: 10-28-2008 08:38 CET ====================================================================== Summary: xf86-video-intel-git install Description: Error while installing module xf86-video-intel-git. error: pathspec 'modesetting' did not match any file(s) known to git. ====================================================================== ---------------------------------------------------------------------- El_Angelo - 10-28-08 08:38 ---------------------------------------------------------------------- we can't provide support for git-modules... afaik you have to install a newer kernel. anything higher than 2.6.28-rc1 should do. Issue History Date Modified Username Field Change ====================================================================== 10-28-08 05:10 kaexsar New Issue 10-28-08 05:10 kaexsar Moonbase Version => 20081028.01 10-28-08 05:10 kaexsar Core Tools => Lunar 10-28-08 05:10 kaexsar Core Tools Version => 20080303 10-28-08 08:38 El_Angelo Status new => closed 10-28-08 08:38 El_Angelo Note Added: 0000841 ======================================================================