September 2009 - CRUX - lists.crux.nu

Testing wanted: pkgmk with --ignore-new option
by Johannes Winkelmann 09 Nov '09

09 Nov '09

Hi there, I've done an update to pkgmk to add symbolic error codes (fairly coarse for now), and to optionally ignore footprint missmatches if no files are missing (also see bug #221 for more information on this). I've prepared an updated pkgutils port; you can get it via httpup sync http://jw.smts.ch/files/crux/ports#pkgutils pkgutils To make prt-get use that new feature, edit /etc/prt-get.conf and add the following line: makecommand pkgmk -in Note that it is recommended to avoid using --ignore-new/-in during packaging, since footprint missmatches should always be looked at in this phase. Please let me know if you have comments or feedback! Cheers, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch

5 8

ports/opt (2.6): [notify] mpeg2dec: dropped in favour of libmpeg2
by crux＠crux.nu 23 Sep '09

23 Sep '09

commit f01679849c50277147ba4d9daca664992474f359 Author: Thomas Penteker <tek(a)serverop.de> Date: Wed Sep 23 22:28:16 2009 +0200 [notify] mpeg2dec: dropped in favour of libmpeg2 please change your local installation to use libmpeg2 instead of mpeg2dec diff --git a/mpeg2dec/.footprint b/mpeg2dec/.footprint deleted file mode 100644 index 0da852d..0000000 --- a/mpeg2dec/.footprint +++ /dev/null @@ -1,21 +0,0 @@ -drwxr-xr-x root/root usr/ -drwxr-xr-x root/root usr/bin/ --rwxr-xr-x root/root usr/bin/corrupt_mpeg2 --rwxr-xr-x root/root usr/bin/extract_mpeg2 --rwxr-xr-x root/root usr/bin/mpeg2dec -drwxr-xr-x root/root usr/include/ -drwxr-xr-x root/root usr/include/mpeg2dec/ --rw-r--r-- root/root usr/include/mpeg2dec/mpeg2.h --rw-r--r-- root/root usr/include/mpeg2dec/mpeg2convert.h -drwxr-xr-x root/root usr/lib/ --rw-r--r-- root/root usr/lib/libmpeg2.a --rwxr-xr-x root/root usr/lib/libmpeg2.la --rw-r--r-- root/root usr/lib/libmpeg2convert.a --rwxr-xr-x root/root usr/lib/libmpeg2convert.la -drwxr-xr-x root/root usr/lib/pkgconfig/ --rw-r--r-- root/root usr/lib/pkgconfig/libmpeg2.pc --rw-r--r-- root/root usr/lib/pkgconfig/libmpeg2convert.pc -drwxr-xr-x root/root usr/man/ -drwxr-xr-x root/root usr/man/man1/ --rw-r--r-- root/root usr/man/man1/extract_mpeg2.1.gz --rw-r--r-- root/root usr/man/man1/mpeg2dec.1.gz diff --git a/mpeg2dec/.md5sum b/mpeg2dec/.md5sum deleted file mode 100644 index e4af5d3..0000000 --- a/mpeg2dec/.md5sum +++ /dev/null @@ -1 +0,0 @@ -7631b0a4bcfdd0d78c0bb0083080b0dc mpeg2dec-0.4.1.tar.gz diff --git a/mpeg2dec/Pkgfile b/mpeg2dec/Pkgfile deleted file mode 100644 index d740142..0000000 --- a/mpeg2dec/Pkgfile +++ /dev/null @@ -1,16 +0,0 @@ -# Description: MPEG1/MPEG2 decoder (includes libmpeg2) -# URL: http://libmpeg2.sourceforge.net/ -# Maintainer: Thomas Penteker, tek at serverop dot de -# Packager: Tilman Sauerbeck, tilman at code-monkey dot de - -name=mpeg2dec -version=0.4.1 -release=1 -source=(http://libmpeg2.sourceforge.net/files/$name-$version.tar.gz) - -build () { - cd $name-$version - ./configure --prefix=/usr - make - make DESTDIR=$PKG install -}

1 0

Re: hardware clock and utc, etc...
by Vasylchyshyn Nikolay 21 Sep '09

21 Sep '09

> On Sun, Sep 20, 2009 at 06:42:23PM +1000, Danny Rawlins wrote: > > Juergen Daubert wrote: > > > On Fri, Sep 18, 2009 at 02:04:59PM +0300, Vasylchyshyn Nikolay wrote: > > > > > >> Hello guys. > > >> > > >> > > > > > > > > Hi, > > > Hello, > > > > > > > > >> I have some problem. > > >> How can i set my RTC to UTC? > > >> > > >> in rc.conf: > > >> TIMEZONE=Europe/Kiev > > >> > > >> The problem is actually in the fact, that when i do > > >> # hwclock --utc --systohc, then RTC is setups in localtime minus 3 hours. > > >> But when i do hwclock --utc --hctosys, then my sys time is the > > >> same as in RTC. > > >> > > > > > > That's wrong, if you have your TIMEZONE set in rc.conf and, more important, > > > your /etc/localtime is a valid symlink to /usr/share/zoneinfo/Europe/Kiev > > > than your systime should be RTC time + 3 hours. > > > > > > > > >> How can i configure my RTC to UTC and have correct localtime? > > >> (I know about /etc/adjtime and > > >> rc:79 hwclock --hctosys and > > >> rc.shutdown:37 hwclock --systohc) > > >> > > >> If i setup my RTC to 10:00:00 (say, from BIOS). And the last line of /etc/adjtime is > > >> UTC, then when i boot up CRUX, i have localtime set to 10:00:00, but > > >> when i do shutdown, then my RTC sets to 7:00:00. > > >> (... then bootup - 7:00:00, shutdown - 4:00:00) > > >> So, i get 3 hours time shift... > > >> How can I avoid this? > > >> > > >> And how cat I properly set my RTC to UTC? > > >> > > > > > > - verify the /etc/localtime symlink > > > - set your systime to the correct localtime, best with rdate > > > - run 'hwclock --utc --systohc' > > > > > Also if you dual boot be sure the other systems are correct to. > > > > > > HTH and best regards > > > Juergen > > > > > > > > Danny > > _______________________________________________ > > CRUX mailing list > > CRUX(a)lists.crux.nu > > http://lists.crux.nu/mailman/listinfo/crux > > Thank you, Hazel, Juergen, Denny, for your responses. I used Hazel recipe, then Juergen recipe. Neither is working for me :(. Maybe the problem is in the fact, that when i do $ hwclock --show and $ hwclock --debug --show i see the same result? So, i set my RTC to localtime. Localtime is OK too :). In any way, thank you for your letters, time and responses. With best regards, Nikolay.

1 0

hardware clock and utc, etc...
by Vasylchyshyn Nikolay 20 Sep '09

20 Sep '09

Hello guys. I have some problem. How can i set my RTC to UTC? in rc.conf: TIMEZONE=Europe/Kiev The problem is actually in the fact, that when i do # hwclock --utc --systohc, then RTC is setups in localtime minus 3 hours. But when i do hwclock --utc --hctosys, then my sys time is the same as in RTC. How can i configure my RTC to UTC and have correct localtime? (I know about /etc/adjtime and rc:79 hwclock --hctosys and rc.shutdown:37 hwclock --systohc) If i setup my RTC to 10:00:00 (say, from BIOS). And the last line of /etc/adjtime is UTC, then when i boot up CRUX, i have localtime set to 10:00:00, but when i do shutdown, then my RTC sets to 7:00:00. (... then bootup - 7:00:00, shutdown - 4:00:00) So, i get 3 hours time shift... How can I avoid this? And how cat I properly set my RTC to UTC? PS: I have CRUX-2.5 and util-linux-ng-2.16.1 Thanks for your attension, time and ansvers. And sorry me for my horrible english.

3 2

Re: hardware clock and utc
by Hazel Russman 19 Sep '09

19 Sep '09

> Message: 1 > Date: Fri, 18 Sep 2009 14:04:59 +0300 > From: Vasylchyshyn Nikolay <younghead(a)ukr.net> > Subject: hardware clock and utc, etc... > To: crux(a)lists.crux.nu > Message-ID: <20090918110459.GA24356(a)VasylchyshynNI.192.168.2.1> > Content-Type: text/plain; charset=us-ascii > > Hello guys. > > I have some problem. > How can i set my RTC to UTC? > > in rc.conf: > TIMEZONE=Europe/Kiev > > The problem is actually in the fact, that when i do > # hwclock --utc --systohc, then RTC is setups in localtime minus 3 hours. > But when i do hwclock --utc --hctosys, then my sys time is the > same as in RTC. > > How can i configure my RTC to UTC and have correct localtime? > (I know about /etc/adjtime and > rc:79 hwclock --hctosys and > rc.shutdown:37 hwclock --systohc) > > If i setup my RTC to 10:00:00 (say, from BIOS). And the last line of /etc/adjtime is > UTC, then when i boot up CRUX, i have localtime set to 10:00:00, but > when i do shutdown, then my RTC sets to 7:00:00. > (... then bootup - 7:00:00, shutdown - 4:00:00) > So, i get 3 hours time shift... > How can I avoid this? > > And how cat I properly set my RTC to UTC? > > PS: I have CRUX-2.5 and util-linux-ng-2.16.1 > > Thanks for your attension, time and ansvers. > And sorry me for my horrible english. > > > First you need to realise that if your hardware clock is set to UTC, then when you show the time with "hwclock --show", you aren't actually seeing the real time on the clock. hwclock adjusts the displayed time to local using your timezone information. That's why the hardware clock seems to show the same time as the system clock; it's actually three hours earlier than that. To see the real time on the hardware clock, use the --debug option with --show. You will probably find that it isn't set to the time you thought it was! Use the BIOS to reset it to three hours before your local time and, with the adjtime file you have, it should work out right. That worked for me when I had the identical problem. ------------------------------ Hazel Russman <hazel_russman(a)yahoo.co.uk>

1 0

Re: libc-2.10.1 causes previously well-behaved program to abort
by Hazel Russman 19 Sep '09

19 Sep '09

Tilman Sauerbeck wrote Thu, 17 Sep 2009 16:49:51 +0200 > I'm guessing that the program does something wrong, and that the error > was tolerated by earlier glibc versions. > > Try running the program in valgrind; that should give you more clues on > where the heap corruption happens resp what causes it. > > Regards, > Tilman > > -- You're right. I'm the one at fault here. According to valgrind, there's an illegal write operation which presumably corrupts my memory and (sometimes) causes the next g_malloc call to crash. The malloc thing was just a symptom of the real problem. The statement that does the illegal write is a call to strcpy, which copies data originally read from the configuration file; that meshes exactly with what I noticed about the effects of changing this file. I think I can see what's illegal about it; it looks like I forgot to convert a void pointer to char. Anyway I'll have a go at fixing it now. Thanks for introducing me to valgrind. It's an awsome program. Hazel -- Hazel Russman <hazel_russman(a)yahoo.co.uk>

1 0

ports/opt (2.6): [notify] php: update to 5.2.11
by crux＠crux.nu 18 Sep '09

18 Sep '09

commit 2f0964961e9b1ff4503fc203f945134fed91f50f Author: Juergen Daubert <jue(a)jue.li> Date: Fri Sep 18 17:08:55 2009 +0200 [notify] php: update to 5.2.11 See http://www.php.net/releases/5_2_11.php diff --git a/php/.footprint b/php/.footprint index 89f0679..c388127 100644 --- a/php/.footprint +++ b/php/.footprint @@ -145,7 +145,6 @@ drwxr-xr-x root/root usr/include/php/ext/standard/ -rw-r--r-- root/root usr/include/php/ext/standard/cyr_convert.h -rw-r--r-- root/root usr/include/php/ext/standard/datetime.h -rw-r--r-- root/root usr/include/php/ext/standard/dl.h --rw-r--r-- root/root usr/include/php/ext/standard/dns.h -rw-r--r-- root/root usr/include/php/ext/standard/exec.h -rw-r--r-- root/root usr/include/php/ext/standard/file.h -rw-r--r-- root/root usr/include/php/ext/standard/flock_compat.h @@ -162,6 +161,7 @@ drwxr-xr-x root/root usr/include/php/ext/standard/ -rw-r--r-- root/root usr/include/php/ext/standard/php_browscap.h -rw-r--r-- root/root usr/include/php/ext/standard/php_crypt.h -rw-r--r-- root/root usr/include/php/ext/standard/php_dir.h +-rw-r--r-- root/root usr/include/php/ext/standard/php_dns.h -rw-r--r-- root/root usr/include/php/ext/standard/php_ext_syslog.h -rw-r--r-- root/root usr/include/php/ext/standard/php_filestat.h -rw-r--r-- root/root usr/include/php/ext/standard/php_fopen_wrappers.h @@ -192,7 +192,6 @@ drwxr-xr-x root/root usr/include/php/ext/standard/ -rw-r--r-- root/root usr/include/php/ext/standard/streamsfuncs.h -rw-r--r-- root/root usr/include/php/ext/standard/uniqid.h -rw-r--r-- root/root usr/include/php/ext/standard/url.h --rw-r--r-- root/root usr/include/php/ext/standard/url_scanner.h -rw-r--r-- root/root usr/include/php/ext/standard/url_scanner_ex.h drwxr-xr-x root/root usr/include/php/ext/xml/ -rw-r--r-- root/root usr/include/php/ext/xml/expat_compat.h diff --git a/php/.md5sum b/php/.md5sum index 517a9f6..3573a92 100644 --- a/php/.md5sum +++ b/php/.md5sum @@ -1,2 +1,2 @@ 683de3db60200bc38aa6e154aa925fa6 extensions.ini -15c7b5a87f57332d6fc683528e28247b php-5.2.10.tar.bz2 +286bf34630f5643c25ebcedfec5e0a09 php-5.2.11.tar.bz2 diff --git a/php/Pkgfile b/php/Pkgfile index 8281c69..f239054 100644 --- a/php/Pkgfile +++ b/php/Pkgfile @@ -4,7 +4,7 @@ # Depends on: ncurses readline zlib libpcre libxml2 bzip2 curl db gdbm zip name=php -version=5.2.10 +version=5.2.11 release=1 source=(http://www.php.net/distributions/php-$version.tar.bz2 extensions.ini)

1 0

libc-2.10.1 causes previously well-behaved program to abort
by Hazel Russman 17 Sep '09

17 Sep '09

I have a small gtk-based program which puts up buttonbars on my desktop. I have used it in both Crux and Debian and have never had any problems with it. But since upgrading to Crux-2.6, I have had intermittent aborts. The traceback (attached) suggests that the problem is inside libc, specifically in malloc. Once the program has aborted, it aborts each time it is restarted. But weirdly I was able to break this cycle simply by altering the order in which buttons were created, via the program's config file. For example, this version - (Files) </home/data/icons/file-manager.png> {gksu-not|sudo -S emelfm2} (Terminal) </home/data/icons/root-term.png> {gksu-not|sudo -S xterm -font 10x20} (Editor) </usr/share/pixmaps/vim32x32.png> {gksu-not|sudo -S gvim} (Other apps) </home/hazel/icons/applications-other.png> {bbrun -w} (Reboot) </home/data/icons/reboot.png> {gksu-not|sudo -S /sbin/shutdown -r now} (Shutdown) </home/data/icons/gnome-logout.png> {gksu-not|sudo -S /sbin/shutdown -h now} caused the program to abort yesterday (though not on previous days), but this one - (Files) </home/data/icons/file-manager.png> {gksu-not|sudo -S emelfm2} (Editor) </usr/share/pixmaps/vim32x32.png> {gksu-not|sudo -S gvim} (Terminal) </home/data/icons/root-term.png> {gksu-not|sudo -S xterm -font 10x20} (Other apps) </home/hazel/icons/applications-other.png> {bbrun -w} (Reboot) </home/data/icons/reboot.png> {gksu-not|sudo -S /sbin/shutdown -r now} (Shutdown) </home/data/icons/gnome-logout.png> {gksu-not|sudo -S /sbin/shutdown -h now} allowed it to run again. Is this a bug or am I doing something wrong? -- Hazel Russman <hazel_russman(a)yahoo.co.uk>

5 5

Re: libc-2.10.1 causes previously well-behaved program to abort
by Hazel Russman 17 Sep '09

17 Sep '09

> Date: Thu, 17 Sep 2009 02:31:41 +0200 On Thu, 17 Sep 2009 02:31:41 Fredrik Rinnestam wrote: > Sorry, no. I've run 2.10.1 for a couple of months now without issues. > i've even built a few iso's without trouble. are you guys sure the > toolchain is ok and that there are no broken library deps? are there > any specific apps (gtk, qt or whatever) that segfaults? > > -- > > /Fredrik Rinnestam > In my case, it isn't a segfault, it's an abort. The automatic traceback that comes with it suggests that the problem lies in the interface between glib2 and libc: g_malloc calls malloc and then it aborts with a "memory corruption" error. > ------------------------------ > On Thu, 17 Sep 2009 10:44:33 +1000 Lucas Hazel wrote: > Neither have I. How did you upgrade? I upgraded from the 2.6 ISO and just said yes to everything on the list, as suggested by the handbook. Then I did rejmerge, ports-u and prt-get sysup. Should I perhaps have rebuilt gtk2 against the new libc? > > -- Hazel Russman <hazel_russman(a)yahoo.co.uk>

1 0

Some gotchas after upgrading to CRUX 2.6
by Mikhail Kolesnik 17 Sep '09

17 Sep '09

Hi. After upgrading to 2.6 some of your desktop apps just would not work. A new X.Org release no longer ships with 'libxcb-xlib.so'. And some of your already installed apps mention xcb-xlib in their .la files, so just rebuilding would not work. The solution is to remove that references found in any .la on the system and rebuild all affected apps. This should at least fix apps that use libtool. The quick and dirty way is: for la in `find /usr -name "*.la"`; do sed -i -e \ "s:[^[:space:]]*xcb-xlib[^[:space:]]*::g" ${la}; done Then it's time to rebuild all broken binaries (there are probably a few more apps trying to load nonexistent shared libraries): prt-get update -fr `revdep` I also have mysql and qt3 installed and (as some other affected apps) qt3 tries to load an old 'libmysqlclient.so.15' library. Rebuilding qt3 fails at some point: at least 'uic' from_the_qt3_source_tree tries to load that old library. Just remove old qt3 package before rebuilding it. And don't forget to run 'mysql_upgrade' or better just dump and reload all databases! I have not finished rebuilding all affected (mostly qt3/kde) apps, but looks like these steps would fix majority of the problems after an upgrade. -- Mikhail Kolesnik JID: mike_k at jabber.org ICQ: 260259143 IRC: mike_k at freenode/#crux, rusnet/#yalta

1 0