Re: SPECS (DEVEL): kde4-kdebase.spec - added BR: libraw1394-devel
Dnia czwartek 09 październik 2008, paszczus napisał: Author: paszczus Date: Thu Oct 9 19:17:39 2008 GMT Module: SPECS Tag: DEVEL Log message: - added BR: libraw1394-devel Files affected: SPECS: kde4-kdebase.spec (1.73.2.11 - 1.73.2.12) Diffs: Index: SPECS/kde4-kdebase.spec diff -u SPECS/kde4-kdebase.spec:1.73.2.11 SPECS/kde4-kdebase.spec:1.73.2.12 --- SPECS/kde4-kdebase.spec:1.73.2.11 Thu Oct 2 16:58:10 2008 +++ SPECS/kde4-kdebase.spec Thu Oct 9 21:17:34 2008 @@ -49,6 +49,7 @@ BuildRequires: lame-libs-devel BuildRequires: libjpeg-devel BuildRequires: libpng-devel = 1.0.8 +BuildRequires: libraw1394-devel BuildRequires: libraw1394-devel = 1.2.0 BuildRequires: libsmbclient-devel = 3.0.0 BuildRequires: libstdc++-devel It's so late that I just don't understand your change? As long as I stair at this I still see this libraw on BR list... Regards, -- Rafał Cygnarowski rafilists [at] gmail [dot] com signature.asc Description: This is a digitally signed message part. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: qt4 tools
Dnia piątek, 4 stycznia 2008, Jakub Bogusz napisał:
AICS some packages expect Qt4 tools to have -qt4 suffix rather than
qt4- prefix - so I'd rename them to be compatible with the rest of the
world. Also, I'm going to add suffixed version of lrelease, so it could
be called without specifying full %{_libdir}/qt4/bin path.
Any comments?
What about providing old symlinks for backward compatibility to avoid problems
with tools witch use prefixed version?
Regards,
--
Rafał Cygnarowski
[EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part.
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: qt4 tools
Dnia piątek, 4 stycznia 2008, Patryk Zawadzki napisał: Are there any? All apps I touched first check for qmake-qt4, then some of them check for qt4-qmake then all fall back to qmake. At least my private scripts ;) Regards, -- Rafał Cygnarowski [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Unclear Firefox situation
Dnia czwartek, 20 września 2007, Cezary Krzyzanowski napisał: Dnia 19-09-2007, Śr o godzinie 22:22 +0200, Rafał Cygnarowski napisał(a): quotation If an individual or organization is creating a Community Edition of Mozilla Firefox or Thunderbird, it must use the names Firefox Community Edition or Thunderbird Community Edition to identify this software. These names may be further qualified to identify the software (e.g. Firefox Community Edition, French, Thunderbird Community Edition, Joe's optimized AMD Opteron build, etc.). Localizers may also translate the words Community Edition. /quotation So... Mozilla Firefox should be called just Firefox... isn't it true? Ehm -- and not 'Fierefox Community Edition' ?? Yes, I just shorted MFCE and FCE to MF and F... But it seems like Bon Echo name is illegal(?) int this case and we should use Firefox. Regards, -- Rafał Cygnarowski [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Unclear Firefox situation
Dnia środa, 19 września 2007, Jakub Bogusz napisał: Mozilla Community Edition Policy doesn't say anything about files or filenames, just: You may not prefix the name product with Mozilla (e.g. Mozilla Firefox Community Edition is not allowed.) nor use the official Firefox or Thunderbird logos to identify the software. You can, of course, still use the unofficial ones. And earlier: quotation If an individual or organization is creating a Community Edition of Mozilla Firefox or Thunderbird, it must use the names Firefox Community Edition or Thunderbird Community Edition to identify this software. These names may be further qualified to identify the software (e.g. Firefox Community Edition, French, Thunderbird Community Edition, Joe's optimized AMD Opteron build, etc.). Localizers may also translate the words Community Edition. /quotation So... Mozilla Firefox should be called just Firefox... isn't it true? Regards, -- Rafał Cygnarowski [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: qt4.spec - adapter
Dnia środa, 20 czerwca 2007, glen napisał:
Author: glen Date: Wed Jun 20 21:51:01 2007 GMT
Module: SPECS Tag: HEAD
Log message:
- adapter
Files affected:
SPECS:
qt4.spec (1.134 - 1.135)
Diffs:
Index: SPECS/qt4.spec
diff -u SPECS/qt4.spec:1.134 SPECS/qt4.spec:1.135
--- SPECS/qt4.spec:1.134 Fri Jun 15 07:42:03 2007
+++ SPECS/qt4.specWed Jun 20 23:50:56 2007
@@ -1537,19 +1537,33 @@
%{_qtdir}/doc
%files -n QtCore-devel -f QtCore-devel.files
+%defattr(644,root,root,755)
^^
This change is wrong. Qt*-devel.files already contains this and it's
respected. If this is done by adapter, then adapter needs to be fixed.
Remove these lines, please.
Regards,
--
Rafał Cygnarowski
[EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part.
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: qt4.spec - adapter
Dnia czwartek, 21 czerwca 2007, Radoslaw Zielinski napisał: Rafał Cygnarowski [EMAIL PROTECTED] [21-06-2007 10:14]: Dnia środa, 20 czerwca 2007, glen napisał: [...] %files -n QtCore-devel -f QtCore-devel.files +%defattr(644,root,root,755) ^^ This change is wrong. Why do you think so? Because 1. it's already there 2. it's less readable now (so bugs prone). Qt*-devel.files already contains this and it's respected. If this is done by adapter, then adapter needs to be fixed. Remove these lines, please. All %files sections should begin with %defattr; no exceptions. And there is no exception in this situation. This cuts down the time needed to wonder if it's needed here and just missing or defined somewhere else... Consider it a policy. If someone(tm) took care of it to be right, then it's not policy but too smart adapter... In the same way I could check every thing 100 times to be sure that one variable is set correctly but one place is enough if done right in right place. Regards, -- Rafał Cygnarowski [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: qt4.spec - adapter
Dnia czwartek, 21 czerwca 2007, Elan Ruusamäe napisał: agree (that's why i commited it too), and it made branch diffing easier of both branches in comparision are adaptered. On AC-branch it's also included in *-files so it's not an argument. the same topic can be argued around any *-i18n* *-i10l* packages. And it is... if there is this definition already then why makes it double? Besides it makes spec-s more readable and a little bit smaller. I understand including this in %files when file list is only addition, but when it's only one source of file list - it's not necessary. Regards, -- Rafał Cygnarowski [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: qt4.spec - adapter
Dnia czwartek, 21 czerwca 2007, Andrzej Krzysztofowicz napisał: It was told some times ago that the rule is to have the %defattr line just after %files. Even if file used via -f (generally language file) already contains it - just for case the -f option is temporary disabled for any reason. This may be a little overloading but should not hurt. Adapter starts remind me MS Word autocorrection (not every dot followed by space is new sentence!). -- Rafał Cygnarowski [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [th] qt4 problems
Dnia sobota, 16 czerwca 2007, Tomasz Pala napisał: Hi, 1. closing any qt4 application (e.g. kpoldek) crashes entire X server, 2. qt4 doesn't honour fontocnfig setup (doesn't draw through freetype/cairo/Xft and I've got badly subpixeled fonts) - is it fourth rendering engine? I didn't seen such behaviour. What Qt4 version you use? What is your xorg*drivers*? What about your freetype/cairo/Xft? Regards, -- Rafał Cygnarowski [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: PLD 2.0 (Ac) marked as stable
Dnia poniedziałek, 2 kwietnia 2007, Marcin Król napisał: PLD 2.0 (Ac) main package tree has been permanently locked and marked as stable. In next few days SPECS SOURCES in CVS will be tagged with AC-STABLE tag. Packages will be probably signed too. Then I'll start working on iso images which should be available in two or three weeks. It would be nice if someone could write a press note about this release and plans about next release. Regards, -- Rafał Cygnarowski [EMAIL PROTECTED] pgpBjHQUDhOaH.pgp Description: PGP signature ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SoC alternative
Dnia wtorek, 20 marca 2007, Patryk Zawadzki napisał: [cut] There are two models possible: - Contract some of the developers full-time It's my the deepest dream ;) - Set a bounty list along with rewards and let the community organize itself Not to worry anyone, they are not trying to change any part of our philosophy. The first targets would most probably be a working Anaconda installation CD/DVD and a PyGTK poldek shell (using python-poldek, not wrapping the binary). The ultimate goal is to be able to offer PLD to some hardware suppliers in UK. I'd love to hear your opinions and I need to know if anyone would be interested in participating. Generally... I'm interesed in but more details whould be appreciate. It's nice to hear that some company would like to help with PLD development. Any kind of help (work, money, machines, promotion) is needed especially if PLD would like to reach the name of DESKTOP system. Regards, -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
amanda on th
Hi! I was just trying to build amanda on Th. It seems there is some linker problem. On AC same spec builds fine. Can anyone confirm my suspicion? Here is end of build log: /bin/sh ../libtool --tag=CC --mode=link i686-pld-linux-gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -O2 -fno-strict-aliasing -fwrapv -march=i686 -mtune=pentium4 -gdwarf-2 -g2 -Wl,--as-needed -o ammt ammt.o ../common-src/libamanda.la libamtape.la ../common-src/libamanda.la -lm i686-pld-linux-gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -O2 -fno-strict-aliasing -fwrapv -march=i686 -mtune=pentium4 -gdwarf-2 -g2 -Wl,--as-needed -o .libs/ammt ammt.o ./.libs/libamtape.so ../common-src/.libs/libamanda.so -lm creating ammt i686-pld-linux-gcc -DHAVE_CONFIG_H -I. -I../config -I../common-src -I../common-src-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -O2 -fno-strict-aliasing -fwrapv -march=i686 -mtune=pentium4 -gdwarf-2 -g2 -MT amdd.o -MD -MP -MF .deps/amdd.Tpo -c -o amdd.o amdd.c mv -f .deps/amdd.Tpo .deps/amdd.Po /bin/sh ../libtool --tag=CC --mode=link i686-pld-linux-gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -O2 -fno-strict-aliasing -fwrapv -march=i686 -mtune=pentium4 -gdwarf-2 -g2 -Wl,--as-needed -o amdd amdd.o ../common-src/libamanda.la libamtape.la ../common-src/libamanda.la -lm i686-pld-linux-gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -O2 -fno-strict-aliasing -fwrapv -march=i686 -mtune=pentium4 -gdwarf-2 -g2 -Wl,--as-needed -o .libs/amdd amdd.o ./.libs/libamtape.so ../common-src/.libs/libamanda.so -lm ./.libs/libamtape.so: undefined reference to `debug_vstralloc' ./.libs/libamtape.so: undefined reference to `debug_areads' ./.libs/libamtape.so: undefined reference to `debug_alloc' ./.libs/libamtape.so: undefined reference to `build_header' ./.libs/libamtape.so: undefined reference to `fh_init' ./.libs/libamtape.so: undefined reference to `debug_amtable_alloc' ./.libs/libamtape.so: undefined reference to `debug_newvstralloc' ./.libs/libamtape.so: undefined reference to `quote_string' ./.libs/libamtape.so: undefined reference to `debug_alloc_push' ./.libs/libamtape.so: undefined reference to `fullwrite' ./.libs/libamtape.so: undefined reference to `vstrextend' ./.libs/libamtape.so: undefined reference to `debug_newstralloc' ./.libs/libamtape.so: undefined reference to `split' ./.libs/libamtape.so: undefined reference to `debug_printf' ./.libs/libamtape.so: undefined reference to `parse_file_header' ./.libs/libamtape.so: undefined reference to `areads_relbuf' ./.libs/libamtape.so: undefined reference to `sanitise_filename' ./.libs/libamtape.so: undefined reference to `debug_stralloc' ./.libs/libamtape.so: undefined reference to `amtable_free' collect2: ld returned 1 exit status make[1]: *** [amdd] Error 1 make[1]: Leaving directory `/home/users/pldcvs/rpm/BUILD/amanda-2.5.1p2/tape-src' make: *** [all-recursive] Error 1 błąd: Błędny status wyjścia z /home/users/pldcvs/tmp/rpm-tmp.53778 (%build) Unresolved symbols are in ../common-src/.libs/libamanda.so but are not seen by linker. -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: amanda on th
Dnia czwartek, 8 marca 2007, Elan Ruusamäe napisał: altho it also may look due -Wl,--as-needed and -llibs at wrong side of it for ass-needed you might find useful this doc: http://www.pld-linux.org/DevelopingPLD/AdvancedDeveloping/FixingAsNeeded yup... it's --as-needed problem, thanks. -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
geninitrd and udhcpc
Hi!
geninitrd has a bug in /dev/urandom creation which causes udhcpc wating for
some random data for a very long time (or some kbd input which will generate
some random irqs)
initrd_gen_nfs() {
# use root=/dev/ram0 init=/linuxrc when starting kernel or you will
# have problems like init(XX) being child process of swapper(1).
debug Adding rootfs on NFS support to initrd (dhcp)
mknod $MNTIMAGE/dev/urandom c 1 8
should be:
mknod $MNTIMAGE/dev/urandom c 1 9
--
Rafał Cygnarowski
[EMAIL PROTECTED]
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: geninitrd 8142
Dnia sobota, 27 stycznia 2007, Arkadiusz Miskiewicz napisał: On sobota, 27 stycznia 2007, Rafał Cygnarowski wrote: BTW: th kernel-2.6.17.13 on ftp doesn't detect my disk on SATA controller - 2.6.16.35 from th-test does. ATI SB600? It's backported in 2.6.16. Nope. Intel P965+ICH8R (http://www.foxconnchannel.com/Product/motherboard_detail.aspx?ID=en-us170). -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: geninitrd 8142
Dnia sobota, 27 stycznia 2007, Cezary Krzyzanowski napisał: root=0302 init=/sbin/initng acpi_sleep=s3_bios video=vesafb:1024x768-32 splash=verbose,theme:ppcrcd,tty:12 console=tty1 #cat /proc/cmdline BOOT_IMAGE=PLD ro root=806 I use lilo now - maybe this will help you find out what happend. BTW: th kernel-2.6.17.13 on ftp doesn't detect my disk on SATA controller - 2.6.16.35 from th-test does. Not udev/initrd matter IMHO No, it isn't. It's kernel problem I met yesterday while setting up PLD box (just before this initrd problem...). -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: geninitrd 8142
Dnia sobota, 27 stycznia 2007, Cezary Krzyzanowski napisał: Dnia 27-01-2007, sob o godzinie 12:50 +0100, Rafał Cygnarowski napisał(a): Geninitrd from HEAD doesn't detect root partition properly. After boot I've got sth like Metallica rocks! and kernel panic consequently. My bad - could You pass me [cut] Could you change this Metallica... to sth less confusing? Maybe sth like: Initrd could not find your root device. Bootloader passed following options: [options here] (or anything else but useful ...) -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [Th] SMP for all!
Dnia wtorek, 23 stycznia 2007, Bartosz Taudul napisał: On Mon, Jan 22, 2007 at 06:32:54PM +0100, Rafał Cygnarowski wrote: Besides... if there is problem with thouse devices on smp kernel than it should be fixed and I think it's the correct way to solve problem (not running away to up kernel...). So fix them and then we'll talk. There are many things that should be, but unfortunately, they aren't. There is nothing to fix so far, couse no one said concretes informatinon - only rumors: 1. [EMAIL PROTECTED] I.E. Amarok and probably some other apps do some magic on their own to ensure smooth ridding on SMP machines and wouldn't this post problems?? _magic_ is not my domain 2. Paweł Sikora iirc not all stuff works fine in smp enviroment. e.g. some lirc drivers, video tuners, tape/floppy drivers. _some_ - which one? what are the symptoms of not working? oops? where they are? 3. Marcin Król There is one. I've encountered some UP hardware where running any SMP kernel simply locks whole machine. no concret information - even kernel version is a secret 4. qboosh What about modules marked as BROKEN_ON_SMP since the beginning (of BROKEN_ON_SMP flag)? I found no driver which uses this flag. I suppose most of these rumors concern some old 2.6 (or even 2.5) kernels. -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [Th] SMP for all!
2. Paweł Sikora iirc not all stuff works fine in smp enviroment. e.g. some lirc drivers, video tuners, tape/floppy drivers. _some_ - which one? what are the symptoms of not working? oops? where they are? 2.6.17 doesn't have one tape driver ( 2.6.20 not checked ), lirc_parallel.c isn't smp safe, v4l looks fixed in recent 2.6.x 2.6.20: [cut] Now it doesn't look so bright... :/ -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [Th] SMP for all!
Dnia wtorek, 23 stycznia 2007, Andrzej Krzysztofowicz napisał: Yes. I even know a person who is using one of them. They are dumb and very useful for copying CDs protected by malformed CD info. How do you think: persons with such hardwer need special kernel with extra patches? What about vanila-up kernels for those machines? -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [Th] SMP for all!
Dnia poniedziałek, 22 stycznia 2007, Jakub Bogusz napisał: What about modules marked as BROKEN_ON_SMP since the beginning (of BROKEN_ON_SMP flag)? I see no source files with BROKEN_ON_SMP string. grep -r BROKEN_ON_SMP linux-2.6.19/ shows only CONFIG_BROKEN_ON_SMP=y in config files (or am I wrong?). -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: lm_sensors-config.spec - more pl, removed invalid use of _s...
Dnia środa, 15 listopada 2006 23:53, qboosh napisał:
Author: qboosh Date: Wed Nov 15 22:53:18 2006 GMT
Module: SPECS Tag: HEAD
Log message:
- more pl, removed invalid use of _sysconfdir
What is _sysconfdir for? I've seen that in rpm-4.4.6 _sysconfdir was defined
as /etc and now (4.4.7) as %{_prefix}/etc. What about some std /etc
directories like init.d, sysconfig? - maybe they should have their own
defines?
--
Rafał Cygnarowski
[EMAIL PROTECTED]
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
lm_sensors - config files for motherboards
Hi! I would like to create lm_sensors-config packages for apropriate motherboards and lm_sensors-config-default to contain our current configuration files. Also I want to move sensorsd init script to sensors package so it could load kernel modules without sensorsd installed (sensorsd could be started if two conditions are met: sensorsd binary exists and /etc/sysconfig/sensors want it (by default)). Has anyoune got sth against such change? Regards, -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: qt4.spec - Updated to 4.2.0 - Patches updated - debug-and-r...
Dnia czwartek, 5 października 2006 23:52, Jakub Bogusz napisał: No problem: http://www.pers.pl/qdbus.debug.stripped and original from build tree: http://www.pers.pl/qdbus.debug It seems to be just debuginfo extracted from executable, not actual executable. These *.debug files shouldn't be installed. We have our own mechanisms to extract debuginfo. I'll try to build it with -no-separate-debug-info - new configure option in Qt 4.2... -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: qt4.spec - Updated to 4.2.0 - Patches updated - debug-and-r...
Dnia czwartek, 5 października 2006 12:05, Elan Ruusamäe napisał: probably copy of /home/users/pldcvs/tmp/qt4-4.2.0-root-pldcvs/usr/bin/qdbus.debug would help to analyze the problem No problem: http://www.pers.pl/qdbus.debug.stripped and original from build tree: http://www.pers.pl/qdbus.debug -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: qt4.spec - Updated to 4.2.0 - Patches updated - debug-and-r...
Dnia środa, 4 października 2006 23:15, pascalek napisał:
Author: pascalek Date: Wed Oct 4 21:15:08 2006 GMT
Module: SPECS Tag: HEAD
Log message:
- Updated to 4.2.0
[...]
- Packaging failed in rpm script after RPATH removing with:
xargs: file: terminated by signal 13
After building qt4 packaging failed. Below is end of build log.
Full log is available here: http://www.pers.pl/qt4.bi.log.tgz (ca. 400KB) and
rpm-tmp.95512 here: http://www.pers.pl/rpm-tmp.95512
Can anyone have idea how to handle this?
--- build log ---
[...]
remove-rpath: /usr/lib
in /home/users/pldcvs/tmp/qt4-4.2.0-root-pldcvs/usr/bin/qdbus
+ '[' '' = '' ']'
+ chrpath -d /home/users/pldcvs/tmp/qt4-4.2.0-root-pldcvs/usr/bin/qdbus
+ read file
+ rpath=
+ chmod u+w /home/users/pldcvs/tmp/qt4-4.2.0-root-pldcvs/usr/bin/qdbus.debug
++ chrpath -l /home/users/pldcvs/tmp/qt4-4.2.0-root-pldcvs/usr/bin/qdbus.debug
Length of dynamic section is zero.
found no dynamic section: Success
++ awk '/RPATH=/ { gsub(/.*RPATH=/,); gsub(/:/, ); print $0 }'
+ '[' '' = '' ']'
+ chrpath -d /home/users/pldcvs/tmp/qt4-4.2.0-root-pldcvs/usr/bin/qdbus.debug
Length of dynamic section is zero.
found no dynamic section: Success
xargs: file: terminated by signal 13
błąd: Błędny status wyjścia z /home/users/pldcvs/tmp/rpm-tmp.95512 (%install)
--- end ---
--
Rafał Cygnarowski
[EMAIL PROTECTED]
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: qt4.spec - Updated to 4.2.0 - Patches updated - debug-and-r...
Dnia środa, 4 października 2006 23:56, Rafał Cygnarowski napisał: After building qt4 packaging failed. Below is end of build log. Full log is available here: http://www.pers.pl/qt4.bi.log.tgz (ca. 400KB) and rpm-tmp.95512 here: http://www.pers.pl/rpm-tmp.95512 Can anyone have idea how to handle this? ^^ (Too much wants in one sentence...) Should be: Has anyone got idea how to handle this? (or sth like that). Sorry pals for that. Have a nice day, -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
What's AC status now?
Hi! What's the AC status now? What's left to do for full release? -- Rafał Cygnarowski [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
