From sparky at pld-linux.org Tue Dec 2 00:39:47 2008 From: sparky at pld-linux.org (Przemyslaw Iskra) Date: Tue, 2 Dec 2008 00:39:47 +0100 Subject: SOURCES: mysqltuner.patch - todo (quite obvious one) In-Reply-To: References:

Message-ID: <20081201233947.GB306@pld-linux.org> On Mon, Dec 01, 2008 at 11:46:04PM +0100, glen wrote: > +TODO: cook perlish which(), or hardcode should be enough: sub which($) { my $file = shift || return undef; foreach my $dir ( split /:/, ( $ENV{PATH} || return undef ) ) { my $path = $dir . '/' . $file; return $path if -x $path; } } you may change "return undef" to "die" to make it paranoid if needed -- ____ Sparky{PI] -- Przemyslaw _ ___ _ _ ........... LANG...Pl..Ca..Es..En /____) ___ ___ _ _ || Iskra | | _ \| | | : WWW........ppcrcd.pld-linux.org \____\| -_)'___| ||^'||//\\// < | _/| | | : JID......sparkyjabberes.org (____/|| (_-_|_|| ||\\ || |_ |_| |_| _| : Mail....sparkypld-linux.org From radek at pld-linux.org Tue Dec 2 11:32:20 2008 From: radek at pld-linux.org (Radoslaw Zielinski) Date: Tue, 2 Dec 2008 11:32:20 +0100 Subject: SOURCES: mysqltuner.patch - todo (quite obvious one) In-Reply-To: <20081201233947.GB306@pld-linux.org> References:

<20081201233947.GB306@pld-linux.org> Message-ID: <20081202103220.GA1077@bzium> Przemyslaw Iskra [02-12-2008 00:39]: > On Mon, Dec 01, 2008 at 11:46:04PM +0100, glen wrote: >> +TODO: cook perlish which(), or hardcode > should be enough: > sub which($) > { > my $file = shift || return undef; > foreach my $dir ( split /:/, ( $ENV{PATH} || return undef ) ) { use File::Spec (); foreach my $dir ( File::Spec->path ) { > my $path = $dir . '/' . $file; my $path = File::Spec->catfile( $dir, $file ); -- Rados?aw Zieli?ski -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From glen at pld-linux.org Tue Dec 2 20:20:58 2008 From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=) Date: Tue, 2 Dec 2008 21:20:58 +0200 Subject: SPECS: tmpwatch.spec - missingok flag for cron.daily entries for not to ree... In-Reply-To: References:

Message-ID: <200812022120.58577.glen@pld-linux.org> On Tuesday 02 December 2008 20:01:41 gotar wrote: > Author: gotar Date: Tue Dec 2 18:01:41 2008 GMT > Module: SPECS Tag: HEAD > ---- Log message: > - missingok flag for cron.daily entries for not to reenable file removal > > ---- Files affected: > SPECS: > tmpwatch.spec (1.80 -> 1.81) ... > $Log$ > +Revision 1.81 2008/12/02 18:01:36 gotar > +- missingok flag for cron.daily entries for not to reenable file removal this is bad idea. don't remove the file, truncate it (comment out, etc) it is quite hard to recover the file otherwise as rpm won't even place you .rpmnew file if it hasn't changed in package! also you wouldn't have even idea the there should be any file to start recovering it (even rpm -V shouldn't complain) -- glen From gotar at polanet.pl Wed Dec 3 02:09:11 2008 From: gotar at polanet.pl (Tomasz Pala) Date: Wed, 3 Dec 2008 02:09:11 +0100 Subject: SPECS: tmpwatch.spec - missingok flag for cron.daily entries for not to ree... In-Reply-To: <200812022120.58577.glen@pld-linux.org> References:

<200812022120.58577.glen@pld-linux.org> Message-ID: <20081203010911.GB5971@pepin.polanet.pl> On Tue, Dec 02, 2008 at 21:20:58 +0200, Elan Ruusam?e wrote: >> +- missingok flag for cron.daily entries for not to reenable file removal > > this is bad idea. I don't want tmpwatch at all. It tries to install themselve whenever I install any other package containing tmpwatch/*.conf files (did I mention how I love directory dependencies?). This is the way I'm gonna get rid of tmpwatch forever. > don't remove the file, truncate it (comment out, etc) tmpwatch is entire script, not one-liner - it doesn't fit to be commented out (truncating and exiting is way to ugly). tmpwatch.directories is symlink to tmpwatch.cron that resides in %_sbindir - I'd prefer not to have any %verify in this directory. > it is quite hard to recover the file otherwise If I remove the file it means I want to have it removed, regarding contents. Restoring tmpwatch.directories is easy anyway (just symlink). > as rpm won't even place > you .rpmnew file if it hasn't changed in package! I'd like not to have .rpmnew file in place of removed one (and don't risk accidental running). > also you wouldn't have even idea the there should be any file to start > recovering it (even rpm -V shouldn't complain) This file won't be useful unless I do need this functionality. If I needed it I would know that there's missing cron entry. -- Tomasz Pala From glen at pld-linux.org Wed Dec 3 03:54:09 2008 From: glen at pld-linux.org (Elan =?iso-8859-2?q?Ruusam=E4e?=) Date: Wed, 3 Dec 2008 04:54:09 +0200 Subject: SPECS: tmpwatch.spec - missingok flag for cron.daily entries for not to ree... In-Reply-To: <20081203010911.GB5971@pepin.polanet.pl> References: <200812022120.58577.glen@pld-linux.org> <20081203010911.GB5971@pepin.polanet.pl> Message-ID: <200812030454.09982.glen@pld-linux.org> On Wednesday 03 December 2008 03:09, Tomasz Pala wrote: > (did I mention how I love directory dependencies?) so there's the glitch, lets move /etc/tmpwatch directory to filesystem package and both problems solved. same goes for /etc/logrotate.d imho. -- glen From wrobell at pld-linux.org Sat Dec 6 22:41:21 2008 From: wrobell at pld-linux.org (wrobell) Date: Sat, 6 Dec 2008 21:41:21 +0000 Subject: TeXLive In-Reply-To: <760ece280811280935j3c0bb1d6pc6dff597d1377e03@mail.gmail.com> References: <760ece280811280935j3c0bb1d6pc6dff597d1377e03@mail.gmail.com> Message-ID: <20081206214121.GC10778@borg> On Fri, Nov 28, 2008 at 06:35:29PM +0100, Zsolt Udvari wrote: > Hi folks! > > I want to create texlive.spec, and it's under developing. I use the > tetex.spec as the beginning, but I've a question: should I split more > subpackages the texlive package? What I think: the style-files, > documentclass-files, e.g. exam.cls put into texlive-latex-exam, etc. > When you think it, I make it. Imho it would be better (nearer to > "pld-philosphy": http://www.pld-linux.org/Features -> Micropackages). well, tetex.spec went bit nuts :) i do remember that tetex package split gave us real HDD space[1] and network usage[2] savings, so it is worth the effort. for example, tetex-*context* packages, which i don't use, are over 38MB in size (to download). if you know that adding some subpackage will save several MB in size, then why not. otherwise i would not bother. regards, wrobell [1] my asus eee pc has 4GB of storage, so don't event try to tell me that sdd space is cheap [2] i am accessing internet via 3G, so please don't tell me that bandwith is cheap, as well From n3npq at mac.com Sat Dec 6 23:19:41 2008 From: n3npq at mac.com (Jeff Johnson) Date: Sat, 06 Dec 2008 17:19:41 -0500 Subject: TeXLive In-Reply-To: <20081206214121.GC10778@borg> References: <760ece280811280935j3c0bb1d6pc6dff597d1377e03@mail.gmail.com> <20081206214121.GC10778@borg> Message-ID: On Dec 6, 2008, at 4:41 PM, wrobell wrote: > > [1] my asus eee pc has 4GB of storage, so don't event try to tell me > that > sdd space is cheap > > [2] i am accessing internet via 3G, so please don't tell me that > bandwith > is cheap, as well Well asus eee is not exactly representative hqrdware, and 3G doesn't exactly supply bandwidth yet, are the flaws in your reasoning abt packaging. But points noted fer sure, TeX is not easy packaging, never has been. 73 de Jeff -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4664 bytes Desc: not available URL: From wrobell at pld-linux.org Sat Dec 6 23:35:52 2008 From: wrobell at pld-linux.org (wrobell) Date: Sat, 6 Dec 2008 22:35:52 +0000 Subject: TeXLive In-Reply-To: References: <760ece280811280935j3c0bb1d6pc6dff597d1377e03@mail.gmail.com> <20081206214121.GC10778@borg> Message-ID: <20081206223552.GD10778@borg> On Sat, Dec 06, 2008 at 05:19:41PM -0500, Jeff Johnson wrote: > > On Dec 6, 2008, at 4:41 PM, wrobell wrote: > >> >> [1] my asus eee pc has 4GB of storage, so don't event try to tell me >> that >> sdd space is cheap >> >> [2] i am accessing internet via 3G, so please don't tell me that >> bandwith >> is cheap, as well > > Well asus eee is not exactly representative hqrdware, and 3G doesn't > exactly supply bandwidth yet, are the flaws in your reasoning abt > packaging. you are right for asus eee pc, but still... it is nice to have tetex on it and not waste over 60MB in unneeded stuff. hence, pld on my machine instead of other distro. in case of 3G... well... let's allow the flame to start. i don't mind 10KB/s download speeds (as _not_ advertised) but 1GB for 9.99eu or 0.49eu for 1MB if you are over your limit is not cheap. for me, at least. > But points noted fer sure, TeX is not easy packaging, never has been. indeed :) best regards, wrobell From n3npq at mac.com Sun Dec 7 00:05:57 2008 From: n3npq at mac.com (Jeff Johnson) Date: Sat, 06 Dec 2008 18:05:57 -0500 Subject: TeXLive In-Reply-To: <20081206223552.GD10778@borg> References: <760ece280811280935j3c0bb1d6pc6dff597d1377e03@mail.gmail.com> <20081206214121.GC10778@borg> <20081206223552.GD10778@borg> Message-ID: On Dec 6, 2008, at 5:35 PM, wrobell wrote: > > >> But points noted fer sure, TeX is not easy packaging, never has been. > > indeed :) > Note I dinna say either of (Diskspace|bandwidth) is cheap. Being stoopid is way more costly than commodity items. Ugly and evil have the same flaws. Heck even gasoline is now US$1.60/per gallon now ... 73 de Jeff -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4664 bytes Desc: not available URL: From wrobell at pld-linux.org Sun Dec 7 00:37:25 2008 From: wrobell at pld-linux.org (wrobell) Date: Sat, 6 Dec 2008 23:37:25 +0000 Subject: TeXLive In-Reply-To: References: <760ece280811280935j3c0bb1d6pc6dff597d1377e03@mail.gmail.com> <20081206214121.GC10778@borg> <20081206223552.GD10778@borg> Message-ID: <20081206233725.GE10778@borg> On Sat, Dec 06, 2008 at 06:05:57PM -0500, Jeff Johnson wrote: > > On Dec 6, 2008, at 5:35 PM, wrobell wrote: > >> >> >>> But points noted fer sure, TeX is not easy packaging, never has been. >> >> indeed :) >> > > Note I dinna say either of > (Diskspace|bandwidth) is cheap. > Being stoopid is way more costly than commodity items. Ugly and evil > have the same flaws. well, every time, we started to talk about splitting packages on this list, somebody claimed that something (cpu, bandwidth, disk space) is cheap, hence my off-topic remarks. but it seems, that if one tries to prevent stupid discussion about somebody's dick length[1], then we are ending up with an off-topic, philosophical thread. my fault, lesson learnt. [...] regards, wrobell [1] my desktop machine is sooooo huuuuuuugeeee, baby From n3npq at mac.com Sun Dec 7 01:35:14 2008 From: n3npq at mac.com (Jeff Johnson) Date: Sat, 06 Dec 2008 19:35:14 -0500 Subject: TeXLive In-Reply-To: <20081206233725.GE10778@borg> References: <760ece280811280935j3c0bb1d6pc6dff597d1377e03@mail.gmail.com> <20081206214121.GC10778@borg> <20081206223552.GD10778@borg> <20081206233725.GE10778@borg> Message-ID: On Dec 6, 2008, at 6:37 PM, wrobell wrote: > > [1] my desktop machine is sooooo huuuuuuugeeee, baby Well I dunno nothin' about your desktop. But my desktop has accumulated 1,337,924.20 cobblestones patiently grinding away, mostly Einstein at HOME, through BOINC. I hope to contribute 0.005% to the USA cobblestone total sometime in the next 12 months. I am currently at the 99.529% percintile ... It's __ALL__ about what you do with your desktop, not otherwise ;-) 73 de Jeff -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4664 bytes Desc: not available URL: From deejay1 at srem.org Sun Dec 7 10:29:19 2008 From: deejay1 at srem.org (=?UTF-8?Q?=C5=81ukasz_Jerna=C5=9B?=) Date: Sun, 7 Dec 2008 10:29:19 +0100 Subject: TeXLive In-Reply-To: References: <760ece280811280935j3c0bb1d6pc6dff597d1377e03@mail.gmail.com> <20081206214121.GC10778@borg> <20081206223552.GD10778@borg> Message-ID: <77fcfd0a0812070129n5d3f9301ice51ae462f01bb7c@mail.gmail.com> 2008/12/7 Jeff Johnson : > Heck even gasoline is now US$1.60/per gallon now ... Well, where most PLD devs/users live it's about 4.61498478 USD per gallon of super... Regards, -- ?ukasz [DeeJay1] Jerna From n3npq at mac.com Sun Dec 7 18:54:29 2008 From: n3npq at mac.com (Jeff Johnson) Date: Sun, 07 Dec 2008 12:54:29 -0500 Subject: TeXLive In-Reply-To: <77fcfd0a0812070129n5d3f9301ice51ae462f01bb7c@mail.gmail.com> References: <760ece280811280935j3c0bb1d6pc6dff597d1377e03@mail.gmail.com> <20081206214121.GC10778@borg> <20081206223552.GD10778@borg> <77fcfd0a0812070129n5d3f9301ice51ae462f01bb7c@mail.gmail.com> Message-ID: <671E7A73-201A-4903-8B54-D7459B963E8B@mac.com> On Dec 7, 2008, at 4:29 AM, ?ukasz Jerna? wrote: > 2008/12/7 Jeff Johnson : > >> Heck even gasoline is now US$1.60/per gallon now ... > > Well, where most PLD devs/users live it's about 4.61498478 USD per > gallon of super... > The more interesting questions are What's the $/Gb and $/Mbps costs? Computers don't (yet) run on super or beer. I'm sure a Polish vodka powered opteron would scream ... ;-) 73 de Jeff -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4664 bytes Desc: not available URL: From sparky at pld-linux.org Mon Dec 8 23:53:49 2008 From: sparky at pld-linux.org (Przemyslaw Iskra) Date: Mon, 8 Dec 2008 23:53:49 +0100 Subject: SPECS: kvm.spec - removed unreasoned userspace bcond disabling (accidental?) In-Reply-To: References:

Message-ID: <20081208225349.GA5657@pld-linux.org> On Mon, Dec 08, 2008 at 11:46:57PM +0100, glen wrote: > Author: glen Date: Mon Dec 8 22:46:57 2008 GMT > Module: SPECS Tag: HEAD > ---- Log message: > - removed unreasoned userspace bcond disabling (accidental?) > +%if "%{_alt_kernel}" != "%{nil}" > +%undefine with_userspace > +%endif reason: userspace requires kernel headers so I whould have to compile additional kernel version, to be able to compile the userspace -- ____ Sparky{PI] -- Przemyslaw _ ___ _ _ ........... LANG...Pl..Ca..Es..En /____) ___ ___ _ _ || Iskra | | _ \| | | : WWW........ppcrcd.pld-linux.org \____\| -_)'___| ||^'||//\\// < | _/| | | : JID......sparkyjabberes.org (____/|| (_-_|_|| ||\\ || |_ |_| |_| _| : Mail....sparkypld-linux.org From glen at pld-linux.org Wed Dec 10 09:36:08 2008 From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=) Date: Wed, 10 Dec 2008 10:36:08 +0200 Subject: java-sun dep loops Message-ID: <200812101036.09350.glen@pld-linux.org> hmm. what to do here? libmawt.so()(64bit) is provided by both packages, so they don't actually depend on each other in loop proves that i can uninstall java-sun-jre-X11 without java-sun-jre being pulled down too. moving headless to x11 package isn't proper either, as it doesn't link with x11 libs dropping provides likely not good either, as programs may link with it (i have no samples to provide) and such deep library path makes it more suspicious anybody able to link with it at all is there anything to change in rpm side? like if self package provides dependency don't go looking it elsewhere? or just add to dependency_whitehout this loop and be done with it? error: LOOP: error: removing java-sun-jre-X11-1.6.0.11-1.x86_64 "Requires: java-sun-jre = 1.6.0.11-1" from tsort relations. error: java-sun-jre-X11-1.6.0.11-1.x86_64 Requires: java-sun-jre = 1.6.0.11-1 error: removing java-sun-jre-1.6.0.11-1.x86_64 "Requires(auto): libmawt.so()(64bit)" from tsort relations. error: java-sun-jre-1.6.0.11-1.x86_64 Requires(auto): libmawt.so()(64bit) error: LOOP: error: removing java-sun-jre-X11-1.6.0.10-5.x86_64 "Requires(auto): libmawt.so()(64bit)" from tsort relations. error: java-sun-jre-X11-1.6.0.10-5.x86_64 Requires(auto): libmawt.so()(64bit) error: removing java-sun-jre-1.6.0.10-5.x86_64 "Requires: java-sun-jre = 1.6.0.10-5" from tsort relations. error: java-sun-jre-1.6.0.10-5.x86_64 Requires: java-sun-jre = 1.6.0.10-5 Preparing... ########################################### [100%] Repackaging... $ ql java-sun-jre-X11 |grep libmawt.so /usr/lib64/jvm/java-sun-1.6.0.11/jre/lib/amd64/motif21/libmawt.so /usr/lib64/jvm/java-sun-1.6.0.11/jre/lib/amd64/xawt/libmawt.so $ ql java-sun-jre |grep libmawt.so /usr/lib64/jvm/java-sun-1.6.0.11/jre/lib/amd64/headless/libmawt.so $ rpm -q java-sun-jre --provides|grep libmawt.so libmawt.so()(64bit) libmawt.so(SUNWprivate_1.1)(64bit) $ rpm -q java-sun-jre-X11 --provides|grep libmawt.so libmawt.so()(64bit) libmawt.so(SUNWprivate_1.1)(64bit) $ q java-sun-jre --requires|grep libmawt.so libmawt.so()(64bit) libmawt.so(SUNWprivate_1.1)(64bit) $ q java-sun-jre-X11 --requires|grep libmawt.so $ ldd /usr/lib64/jvm/java-sun-1.6.0.11/jre/lib/amd64/headless/libmawt.so linux-vdso.so.1 => (0x00007fff651ff000) libjvm.so => not found libawt.so => /usr/lib64/jvm/java-sun-1.6.0.11/jre/lib/amd64/headless/../libawt.so (0x00007f555cee6000) libm.so.6 => /lib64/libm.so.6 (0x00007f555cc63000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f555ca5f000) libjava.so => /usr/lib64/jvm/java-sun-1.6.0.11/jre/lib/amd64/headless/../libjava.so (0x00007f555c92f000) libc.so.6 => /lib64/libc.so.6 (0x00007f555c5d8000) /lib64/ld-linux-x86-64.so.2 (0x00007f555d1d2000) libjvm.so => not found libjvm.so => not found libverify.so => /usr/lib64/jvm/java-sun-1.6.0.11/jre/lib/amd64/headless/../libverify.so (0x00007f555c4c8000) libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f555c2b0000) libjvm.so => not found -- glen From sparky at pld-linux.org Wed Dec 10 14:19:27 2008 From: sparky at pld-linux.org (Przemyslaw Iskra) Date: Wed, 10 Dec 2008 14:19:27 +0100 Subject: java-sun dep loops In-Reply-To: <200812101036.09350.glen@pld-linux.org> References: <200812101036.09350.glen@pld-linux.org> Message-ID: <20081210131927.GA27106@pld-linux.org> On Wed, Dec 10, 2008 at 10:36:08AM +0200, Elan Ruusam?e wrote: > hmm. what to do here? > > libmawt.so()(64bit) is provided by both packages, > so they don't actually depend on each other in loop > proves that i can uninstall java-sun-jre-X11 without java-sun-jre being pulled down too. > > moving headless to x11 package isn't proper either, as it doesn't link with x11 libs > > dropping provides likely not good either, as programs may link with it > (i have no samples to provide) and such deep library path makes it more suspicious anybody able to link with it at all > > is there anything to change in rpm side? > like if self package provides dependency don't go looking it elsewhere? > error: LOOP: > error: removing java-sun-jre-X11-1.6.0.11-1.x86_64 "Requires: java-sun-jre = 1.6.0.11-1" from tsort relations. > error: java-sun-jre-X11-1.6.0.11-1.x86_64 Requires: java-sun-jre = 1.6.0.11-1 > error: removing java-sun-jre-1.6.0.11-1.x86_64 "Requires(auto): libmawt.so()(64bit)" from tsort relations. > error: java-sun-jre-1.6.0.11-1.x86_64 Requires(auto): libmawt.so()(64bit) > error: LOOP: > error: removing java-sun-jre-X11-1.6.0.10-5.x86_64 "Requires(auto): libmawt.so()(64bit)" from tsort relations. > error: java-sun-jre-X11-1.6.0.10-5.x86_64 Requires(auto): libmawt.so()(64bit) > error: removing java-sun-jre-1.6.0.10-5.x86_64 "Requires: java-sun-jre = 1.6.0.10-5" from tsort relations. > error: java-sun-jre-1.6.0.10-5.x86_64 Requires: java-sun-jre = 1.6.0.10-5 > Preparing... ########################################### [100%] > Repackaging... Removing libmawt.so* from java-sun-jre requires list should to the trick, and it won't brake anything as -jre provides the library anyways. But I think the proper way to solve this would be to teach rpm/poldek to remove all the Requires which are provided by the same package before starting sort procedure. Alternatively, do it at the sort time - start looking for the provided dependancy in the package that requires it. Or would it brake something ? -- ____ Sparky{PI] -- Przemyslaw _ ___ _ _ ........... LANG...Pl..Ca..Es..En /____) ___ ___ _ _ || Iskra | | _ \| | | : WWW........ppcrcd.pld-linux.org \____\| -_)'___| ||^'||//\\// < | _/| | | : JID......sparkyjabberes.org (____/|| (_-_|_|| ||\\ || |_ |_| |_| _| : Mail....sparkypld-linux.org From glen at pld-linux.org Thu Dec 11 18:07:01 2008 From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=) Date: Thu, 11 Dec 2008 19:07:01 +0200 Subject: SOURCES: clive-delfi.patch (REMOVED), clive-reporter.patch (REMOVED), clive... In-Reply-To: References:

Message-ID: <200812111907.01184.glen@pld-linux.org> On Thursday 11 December 2008 15:09:39 lisu wrote: > Author: lisu Date: Thu Dec 11 13:09:39 2008 GMT > Module: SOURCES Tag: HEAD > ---- Log message: > - outdated > > ---- Files affected: > SOURCES: > clive-delfi.patch (1.8 -> NONE) (REMOVED), clive-reporter.patch (1.2 -> > NONE) (REMOVED), clive-spz.patch (1.4 -> NONE) (REMOVED), clive-setup.py > (1.3 -> NONE) (REMOVED) ??? that patches totally don't apply don't mean they'e applied upstream! glen at wintersunset pld/SPECS $ grep -r delfi ../BUILD/clive-2.1.0/ glen at wintersunset pld/SPECS $ grep -r south ../BUILD/clive-2.1.0/ glen at wintersunset pld/SPECS $ -- glen From glen at pld-linux.org Fri Dec 12 12:11:40 2008 From: glen at pld-linux.org (Elan =?utf-8?q?Ruusam=C3=A4e?=) Date: Fri, 12 Dec 2008 13:11:40 +0200 Subject: SPECS: openssl.spec - keep /var/lib/openssl as default dir in Titanium, mov... In-Reply-To: References:

Message-ID: <200812121311.40793.glen@pld-linux.org> On Friday 12 December 2008 00:34:39 hawk wrote: > Author: hawk Date: Thu Dec 11 22:34:39 2008 GMT > Module: SPECS Tag: HEAD > ---- Log message: > - keep /var/lib/openssl as default dir in Titanium, moving to /etc/openssl > breaks too many apps and messess up stuff created manually in > /var/lib/openssl, however add symlinks in /etc/openssl to keep > compatibility with official PLD ... > +%if "%{pld_release}" == "ti" > +ln -sf %{_var}/lib/%{name}/%{name}.cnf \ > + $RPM_BUILD_ROOT%{_sysconfdir}/%{name}/openssl.cnf wtf, don't you want to do it opposite way, so that /etc/ migration doesn't have to be done again in the future? -- glen From hawk at limanowa.net Fri Dec 12 12:47:26 2008 From: hawk at limanowa.net (Marcin Krol) Date: Fri, 12 Dec 2008 12:47:26 +0100 Subject: SPECS: openssl.spec - keep /var/lib/openssl as default dir in Titanium, mov... In-Reply-To: <200812121311.40793.glen@pld-linux.org> References:

<200812121311.40793.glen@pld-linux.org> Message-ID: <49424F4E.2000503@limanowa.net> > wtf, don't you want to do it opposite way, so that /etc/ migration doesn't > have to be done again in the future? There will be no migration of /var/lib/openssl to /etc in Titanium. Th was not affected by my changes. M. From wrobell at pld-linux.org Fri Dec 19 19:19:19 2008 From: wrobell at pld-linux.org (wrobell) Date: Fri, 19 Dec 2008 18:19:19 +0000 Subject: SPECS: python-psycopg2.spec - Release 3. Killed nonworking mx bcond. Prepar... In-Reply-To: References:

Message-ID: <20081219181919.GZ6135@borg> On Fri, Dec 19, 2008 at 09:49:35AM +0100, matkor wrote: > Author: matkor Date: Fri Dec 19 08:49:34 2008 GMT > Module: SPECS Tag: HEAD > ---- Log message: > - Release 3. Killed nonworking mx bcond. Prepared for Ac. now, if somebody wants to to compile psycopg, then he has to build it with mx.DateTime, which - is non-standard - i don't know any modern application, which uses it what's the point? is it for python 2.4 and Ac? then just do that on ac branch, please. at least, you could leave mx bcond and explain why it is not working for you. best regards, wrobell From wrobell at pld-linux.org Fri Dec 19 19:20:48 2008 From: wrobell at pld-linux.org (wrobell) Date: Fri, 19 Dec 2008 18:20:48 +0000 Subject: xulrunner.spec and ac bcond Message-ID: <20081219182048.GA6135@borg> as i know we have ac branch for ac distro line. what's the point of ac bcond in xulrunner.spec? best regards, wrobell From blues at pld-linux.org Fri Dec 19 19:35:54 2008 From: blues at pld-linux.org (Pawel Golaszewski) Date: Fri, 19 Dec 2008 19:35:54 +0100 (CET) Subject: xulrunner.spec and ac bcond In-Reply-To: <20081219182048.GA6135@borg> References: <20081219182048.GA6135@borg> Message-ID: On Fri, 19 Dec 2008, wrobell wrote: > as i know we have ac branch for ac distro line. what's the point of ac > bcond in xulrunner.spec? I think it's good direction when the difference is only in BR's or some simple configure options. There is no point in branching for so simple things. -- pozdr. Pawe? Go?aszewski jid:bluesjabbergdapl -------------------------------------------------------------------------- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Pro-Logic Surround Sound with Bass Boost and all the music is free. From wrobell at pld-linux.org Fri Dec 19 19:43:18 2008 From: wrobell at pld-linux.org (wrobell) Date: Fri, 19 Dec 2008 18:43:18 +0000 Subject: xulrunner.spec and ac bcond In-Reply-To: References: <20081219182048.GA6135@borg> Message-ID: <20081219184318.GB6135@borg> On Fri, Dec 19, 2008 at 07:35:54PM +0100, Pawel Golaszewski wrote: > On Fri, 19 Dec 2008, wrobell wrote: > > as i know we have ac branch for ac distro line. what's the point of ac > > bcond in xulrunner.spec? > > I think it's good direction when the difference is only in BR's or some > simple configure options. There is no point in branching for so simple > things. it is messy as you need to look at distro line i 3 ways - trunk (no changes) - ac branch - and now ac bcond and i bet it will kick our asses sooner or later. people will abuse the bcond thing. moreover, it already happens with python-psycopg2.spec to build psycopg with python 2.4. we will end up with mess. best regards, wrobell From blues at pld-linux.org Sat Dec 20 14:04:39 2008 From: blues at pld-linux.org (Pawel Golaszewski) Date: Sat, 20 Dec 2008 14:04:39 +0100 (CET) Subject: xulrunner.spec and ac bcond In-Reply-To: <20081219184318.GB6135@borg> References: <20081219182048.GA6135@borg> <20081219184318.GB6135@borg> Message-ID: On Fri, 19 Dec 2008, wrobell wrote: > > > as i know we have ac branch for ac distro line. what's the point of > > > ac bcond in xulrunner.spec? > > I think it's good direction when the difference is only in BR's or > > some simple configure options. There is no point in branching for so > > simple things. > it is messy as you need to look at distro line i 3 ways > - trunk (no changes) > - ac branch > - and now ac bcond No, there should be always AC branch/tag for last version that s prepared for AC. It's easier to move tag/branch than merge changes. > and i bet it will kick our asses sooner or later. people will abuse the > bcond thing. moreover, it already happens with python-psycopg2.spec to > build psycopg with python 2.4. we will end up with mess. -- pozdr. Pawe? Go?aszewski jid:bluesjabbergdapl -------------------------------------------------------------------------- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Pro-Logic Surround Sound with Bass Boost and all the music is free. From wrobell at pld-linux.org Sat Dec 20 15:47:15 2008 From: wrobell at pld-linux.org (wrobell) Date: Sat, 20 Dec 2008 14:47:15 +0000 Subject: xulrunner.spec and ac bcond In-Reply-To: References: <20081219182048.GA6135@borg> <20081219184318.GB6135@borg> Message-ID: <20081220144714.GA3739@borg> On Sat, Dec 20, 2008 at 02:04:39PM +0100, Pawel Golaszewski wrote: > On Fri, 19 Dec 2008, wrobell wrote: > > > > as i know we have ac branch for ac distro line. what's the point of > > > > ac bcond in xulrunner.spec? > > > I think it's good direction when the difference is only in BR's or > > > some simple configure options. There is no point in branching for so > > > simple things. > > it is messy as you need to look at distro line i 3 ways > > - trunk (no changes) > > - ac branch > > - and now ac bcond > > No, there should be always AC branch/tag for last version that s prepared > for AC. > It's easier to move tag/branch than merge changes. i really don't mind until specs get messy. your choice guys. so just to state it loud. we do allow distro line bconds like "ra", "ac", and "ti". there shall be no "th" bconds as it is trunk forever. is that ok for everyone? [...] wrobell From blues at pld-linux.org Sat Dec 20 18:04:09 2008 From: blues at pld-linux.org (Pawel Golaszewski) Date: Sat, 20 Dec 2008 18:04:09 +0100 (CET) Subject: xulrunner.spec and ac bcond In-Reply-To: <20081220144714.GA3739@borg> References: <20081219182048.GA6135@borg> <20081219184318.GB6135@borg> <20081220144714.GA3739@borg> Message-ID: On Sat, 20 Dec 2008, wrobell wrote: > so just to state it loud. we do allow distro line bconds like "ra", > "ac", and "ti". yep. Just not bconds - conditions. > there shall be no "th" bconds as it is trunk forever. Byt default HEAD is for Th. OTher lines can use conditions for simplicity. -- pozdr. Pawe? Go?aszewski jid:bluesjabbergdapl -------------------------------------------------------------------------- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Pro-Logic Surround Sound with Bass Boost and all the music is free. From arekm at maven.pl Sun Dec 21 09:26:02 2008 From: arekm at maven.pl (Arkadiusz Miskiewicz) Date: Sun, 21 Dec 2008 09:26:02 +0100 Subject: xulrunner.spec and ac bcond In-Reply-To: <20081220144714.GA3739@borg> References: <20081219182048.GA6135@borg> <20081220144714.GA3739@borg> Message-ID: <200812210926.02688.arekm@maven.pl> On Saturday 20 of December 2008, wrobell wrote: > On Sat, Dec 20, 2008 at 02:04:39PM +0100, Pawel Golaszewski wrote: > > On Fri, 19 Dec 2008, wrobell wrote: > > > > > as i know we have ac branch for ac distro line. what's the point of > > > > > ac bcond in xulrunner.spec? > > > > > > > > I think it's good direction when the difference is only in BR's or > > > > some simple configure options. There is no point in branching for so > > > > simple things. > > > > > > it is messy as you need to look at distro line i 3 ways > > > - trunk (no changes) > > > - ac branch > > > - and now ac bcond > > > > No, there should be always AC branch/tag for last version that s prepared > > for AC. > > It's easier to move tag/branch than merge changes. > > i really don't mind until specs get messy. your choice guys. > > so just to state it loud. we do allow distro line bconds like "ra", "ac", > and "ti". there shall be no "th" bconds as it is trunk forever. Prepare for "arekm" and "companyiworkfor" conditions, too! (joke... for now) -- Arkadiusz Mi?kiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/ From glen at delfi.ee Sun Dec 21 21:17:55 2008 From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=) Date: Sun, 21 Dec 2008 22:17:55 +0200 Subject: xulrunner.spec and ac bcond In-Reply-To: <20081220144714.GA3739@borg> References: <20081219182048.GA6135@borg> <20081220144714.GA3739@borg> Message-ID: <200812212217.56067.glen@delfi.ee> On Saturday 20 December 2008 16:47, wrobell wrote: > so just to state it loud. we do allow distro line bconds like "ra", "ac", > and "ti". there shall be no "th" bconds as it is trunk forever. there's no bcond. it's %{pld_release} macro rather... -- glen From glen at delfi.ee Sun Dec 21 21:21:04 2008 From: glen at delfi.ee (Elan =?utf-8?q?Ruusam=C3=A4e?=) Date: Sun, 21 Dec 2008 22:21:04 +0200 Subject: SPECS: texlive.spec - %files fixes In-Reply-To: References:

Message-ID: <200812212221.04380.glen@delfi.ee> On Sunday 21 December 2008, uzsolt wrote: > +# %postun fonts-bh > +# %texhash for the zillionth time: to disable macro expansion use %% -- glen From glen at delfi.ee Sun Dec 21 21:21:48 2008 From: glen at delfi.ee (Elan =?utf-8?q?Ruusam=C3=A4e?=) Date: Sun, 21 Dec 2008 22:21:48 +0200 Subject: SPECS: texlive.spec - %files fixes In-Reply-To: References:

Message-ID: <200812212221.48415.glen@delfi.ee> On Sunday 21 December 2008, uzsolt wrote: > +# %package fonts-bh > +# Summary:?????Bold & Heavy Fonts > +# Summary(pl.UTF-8):???Fonty Bold i Heavy > +# Group:???????????????Fonts > +# Requires:????%{name}-dirs-fonts > ? > -%description fonts-bh > -Bold & Heavy Fonts. > +# %description fonts-bh > +# Bold & Heavy Fonts. to disable subpackage building, it is sufficent to disable ONLY %files section! -- glen From wrobell at pld-linux.org Mon Dec 22 10:22:42 2008 From: wrobell at pld-linux.org (wrobell) Date: Mon, 22 Dec 2008 09:22:42 +0000 Subject: xulrunner.spec and ac bcond In-Reply-To: References: <20081219182048.GA6135@borg> Message-ID: <20081222092242.GA1006@borg> On Fri, Dec 19, 2008 at 07:35:54PM +0100, Pawel Golaszewski wrote: > On Fri, 19 Dec 2008, wrobell wrote: > > as i know we have ac branch for ac distro line. what's the point of ac > > bcond in xulrunner.spec? > > I think it's good direction when the difference is only in BR's or some > simple configure options. There is no point in branching for so simple > things. one question, though. if one of the distro lines dies, then who is going to clean up the conditionals introduced by such distro line? wrobell From glen at pld-linux.org Mon Dec 22 12:17:11 2008 From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=) Date: Mon, 22 Dec 2008 13:17:11 +0200 Subject: xulrunner.spec and ac bcond In-Reply-To: <20081222092242.GA1006@borg> References: <20081219182048.GA6135@borg> <20081222092242.GA1006@borg> Message-ID: <200812221317.12005.glen@pld-linux.org> On Monday 22 December 2008 11:22:42 wrobell wrote: > On Fri, Dec 19, 2008 at 07:35:54PM +0100, Pawel Golaszewski wrote: > > On Fri, 19 Dec 2008, wrobell wrote: > > > as i know we have ac branch for ac distro line. what's the point of ac > > > bcond in xulrunner.spec? > > > > I think it's good direction when the difference is only in BR's or some > > simple configure options. There is no point in branching for so simple > > things. > > one question, though. if one of the distro lines dies, then who is going to > clean up the conditionals introduced by such distro line? you can always do cvs annotate and ask whoever added it... -- glen From udvzsolt at gmail.com Mon Dec 22 16:35:25 2008 From: udvzsolt at gmail.com (Zsolt Udvari) Date: Mon, 22 Dec 2008 16:35:25 +0100 Subject: SPECS: texlive.spec - %files fixes In-Reply-To: <200812212221.04380.glen@delfi.ee> References:

<200812212221.04380.glen@delfi.ee> Message-ID: <760ece280812220735le720479nd63bb72ed479993c@mail.gmail.com> 2008/12/21 Elan Ruusam?e : > On Sunday 21 December 2008, uzsolt wrote: >> +# %postun fonts-bh >> +# %texhash > > for the zillionth time: to disable macro expansion use %% So should I use %%postun fonts-bh From glen at delfi.ee Mon Dec 22 16:43:21 2008 From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=) Date: Mon, 22 Dec 2008 17:43:21 +0200 Subject: SPECS: texlive.spec - %files fixes In-Reply-To: <760ece280812220735le720479nd63bb72ed479993c@mail.gmail.com> References: <200812212221.04380.glen@delfi.ee> <760ece280812220735le720479nd63bb72ed479993c@mail.gmail.com> Message-ID: <200812221743.21206.glen@delfi.ee> On Monday 22 December 2008 17:35, Zsolt Udvari wrote: > 2008/12/21 Elan Ruusam?e : > > On Sunday 21 December 2008, uzsolt wrote: > >> +# %postun fonts-bh > >> +# %texhash > > > > for the zillionth time: to disable macro expansion use %% > > So should I use > %%postun fonts-bh no, # %%postun but if you disable %files, it's irrelevant anyway as package is not written -- glen From wrobell at pld-linux.org Mon Dec 22 19:43:48 2008 From: wrobell at pld-linux.org (wrobell) Date: Mon, 22 Dec 2008 18:43:48 +0000 Subject: xulrunner.spec and ac bcond In-Reply-To: <200812221317.12005.glen@pld-linux.org> References: <20081219182048.GA6135@borg> <20081222092242.GA1006@borg> <200812221317.12005.glen@pld-linux.org> Message-ID: <20081222184348.GB1006@borg> On Mon, Dec 22, 2008 at 01:17:11PM +0200, Elan Ruusam?e wrote: > On Monday 22 December 2008 11:22:42 wrobell wrote: > > On Fri, Dec 19, 2008 at 07:35:54PM +0100, Pawel Golaszewski wrote: > > > On Fri, 19 Dec 2008, wrobell wrote: > > > > as i know we have ac branch for ac distro line. what's the point of ac > > > > bcond in xulrunner.spec? > > > > > > I think it's good direction when the difference is only in BR's or some > > > simple configure options. There is no point in branching for so simple > > > things. > > > > one question, though. if one of the distro lines dies, then who is going to > > clean up the conditionals introduced by such distro line? > > you can always do cvs annotate and ask whoever added it... to be honest, that's too optymistic statement. but... will you? best regards, wrobell From wolf.pld at gmail.com Tue Dec 23 01:27:34 2008 From: wolf.pld at gmail.com (Bartosz Taudul) Date: Tue, 23 Dec 2008 01:27:34 +0100 Subject: xulrunner.spec and ac bcond In-Reply-To: <200812221317.12005.glen@pld-linux.org> References: <20081219182048.GA6135@borg> <20081222092242.GA1006@borg> <200812221317.12005.glen@pld-linux.org> Message-ID: <20081223002734.GA4067@bajzel> On Mon, Dec 22, 2008 at 01:17:11PM +0200, Elan Ruusam?e wrote: > you can always do cvs annotate and ask whoever added it... Jokes go to fortunes CVS module, not here. wolf -- Bartek . Taudul : .:.................................................................... w o l f @ p l d - l i n u x . o r g .:. http://wolf.valkyrie.one.pl/ From wrobell at pld-linux.org Tue Dec 23 11:48:41 2008 From: wrobell at pld-linux.org (wrobell) Date: Tue, 23 Dec 2008 10:48:41 +0000 Subject: SPECS: python-psycopg2.spec - Release 3. Killed nonworking mx bcond. Prepar... In-Reply-To: <20081219181919.GZ6135@borg> References:

<20081219181919.GZ6135@borg> Message-ID: <20081223104841.GC1006@borg> On Fri, Dec 19, 2008 at 06:19:19PM +0000, wrobell wrote: > On Fri, Dec 19, 2008 at 09:49:35AM +0100, matkor wrote: > > Author: matkor Date: Fri Dec 19 08:49:34 2008 GMT > > Module: SPECS Tag: HEAD > > ---- Log message: > > - Release 3. Killed nonworking mx bcond. Prepared for Ac. > > now, if somebody wants to to compile psycopg, then he has to build it with > mx.DateTime, which > - is non-standard > - i don't know any modern application, which uses it > > what's the point? is it for python 2.4 and Ac? then just do that on ac > branch, please. > > at least, you could leave mx bcond and explain why it is not working for > you. no answer so far and my understanding is that matkor's change was due to python 2.4 in ac. therefore my proposal to solve this conflict is as follows - i will move python-psycopg2.spec to AC-branch - i will revert HEAD of the spec to previous version and upgrade it to 2.0.8 - if distro line bconds (whatever you call it) are allowed on HEAD, then matkor, please use the distro line bcond instead of py_ver hack (to not introduce more mess), but please leave mx bcond for those who would like to use it[1] anyone wishes to comment? regards, wrobell [1] i made it in my spare time for others but imho mx bcond can die From glen at pld-linux.org Tue Dec 23 15:34:52 2008 From: glen at pld-linux.org (Elan =?utf-8?q?Ruusam=C3=A4e?=) Date: Tue, 23 Dec 2008 16:34:52 +0200 Subject: xulrunner.spec and ac bcond In-Reply-To: <20081222184348.GB1006@borg> References: <20081219182048.GA6135@borg> <200812221317.12005.glen@pld-linux.org> <20081222184348.GB1006@borg> Message-ID: <200812231634.52684.glen@pld-linux.org> On Monday 22 December 2008 20:43:48 wrobell wrote: > On Mon, Dec 22, 2008 at 01:17:11PM +0200, Elan Ruusam?e wrote: > > On Monday 22 December 2008 11:22:42 wrobell wrote: > > > On Fri, Dec 19, 2008 at 07:35:54PM +0100, Pawel Golaszewski wrote: > > > > On Fri, 19 Dec 2008, wrobell wrote: > > > > > as i know we have ac branch for ac distro line. what's the point of > > > > > ac bcond in xulrunner.spec? > > > > > > > > I think it's good direction when the difference is only in BR's or > > > > some simple configure options. There is no point in branching for so > > > > simple things. > > > > > > one question, though. if one of the distro lines dies, then who is > > > going to clean up the conditionals introduced by such distro line? > > > > you can always do cvs annotate and ask whoever added it... > > to be honest, that's too optymistic statement. but... will you? i'l complete the sentence: "and ask whoever added it, whether you can remove it". i don't say how things should be, i just say how they are... -- glen From glen at pld-linux.org Tue Dec 23 15:36:55 2008 From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=) Date: Tue, 23 Dec 2008 16:36:55 +0200 Subject: SPECS: python-psycopg2.spec - Release 3. Killed nonworking mx bcond. Prepar... In-Reply-To: <20081223104841.GC1006@borg> References: <20081219181919.GZ6135@borg> <20081223104841.GC1006@borg> Message-ID: <200812231636.56223.glen@pld-linux.org> On Tuesday 23 December 2008 12:48:41 wrobell wrote: > - if distro line bconds (whatever you call it) are allowed on HEAD, forbidding it, is like forbidding commits to SPECS module, i'll continue add them if i find it better than making AC-branch, and likely same applies to Titanium branch and hawk's family. -- glen From blues at pld-linux.org Tue Dec 23 16:08:06 2008 From: blues at pld-linux.org (Pawel Golaszewski) Date: Tue, 23 Dec 2008 16:08:06 +0100 (CET) Subject: SPECS: python-psycopg2.spec - Release 3. Killed nonworking mx bcond. Prepar... In-Reply-To: <200812231636.56223.glen@pld-linux.org> References: <20081219181919.GZ6135@borg> <20081223104841.GC1006@borg> <200812231636.56223.glen@pld-linux.org> Message-ID: On Tue, 23 Dec 2008, Elan Ruusam?e wrote: > > - if distro line bconds (whatever you call it) are allowed on HEAD, > forbidding it, is like forbidding commits to SPECS module, i'll continue add > them if i find it better than making AC-branch, Ok, but AC-branch must exist in this place. -- pozdr. Pawe? Go?aszewski jid:bluesjabbergdapl -------------------------------------------------------------------------- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Pro-Logic Surround Sound with Bass Boost and all the music is free. From wrobell at pld-linux.org Tue Dec 23 16:16:39 2008 From: wrobell at pld-linux.org (wrobell) Date: Tue, 23 Dec 2008 15:16:39 +0000 Subject: SPECS: python-psycopg2.spec - Release 3. Killed nonworking mx bcond. Prepar... In-Reply-To: <200812231636.56223.glen@pld-linux.org> References: <20081219181919.GZ6135@borg> <20081223104841.GC1006@borg> <200812231636.56223.glen@pld-linux.org> Message-ID: <20081223151639.GB11110@borg.culture.mapflow.com> On Tue, Dec 23, 2008 at 04:36:55PM +0200, Elan Ruusam?e wrote: > On Tuesday 23 December 2008 12:48:41 wrobell wrote: > > - if distro line bconds (whatever you call it) are allowed on HEAD, > > forbidding it, is like forbidding commits to SPECS module, i'll continue add > them if i find it better than making AC-branch, and likely same applies to > Titanium branch and hawk's family. please, use the other thread. wrobell From wrobell at pld-linux.org Tue Dec 23 16:19:36 2008 From: wrobell at pld-linux.org (wrobell) Date: Tue, 23 Dec 2008 15:19:36 +0000 Subject: xulrunner.spec and ac bcond In-Reply-To: <200812231634.52684.glen@pld-linux.org> References: <20081219182048.GA6135@borg> <200812221317.12005.glen@pld-linux.org> <20081222184348.GB1006@borg> <200812231634.52684.glen@pld-linux.org> Message-ID: <20081223151936.GC11110@borg.culture.mapflow.com> On Tue, Dec 23, 2008 at 04:34:52PM +0200, Elan Ruusam?e wrote: > On Monday 22 December 2008 20:43:48 wrobell wrote: > > On Mon, Dec 22, 2008 at 01:17:11PM +0200, Elan Ruusam?e wrote: > > > On Monday 22 December 2008 11:22:42 wrobell wrote: > > > > On Fri, Dec 19, 2008 at 07:35:54PM +0100, Pawel Golaszewski wrote: > > > > > On Fri, 19 Dec 2008, wrobell wrote: > > > > > > as i know we have ac branch for ac distro line. what's the point of > > > > > > ac bcond in xulrunner.spec? > > > > > > > > > > I think it's good direction when the difference is only in BR's or > > > > > some simple configure options. There is no point in branching for so > > > > > simple things. > > > > > > > > one question, though. if one of the distro lines dies, then who is > > > > going to clean up the conditionals introduced by such distro line? > > > > > > you can always do cvs annotate and ask whoever added it... > > > > to be honest, that's too optymistic statement. but... will you? > > i'l complete the sentence: "and ask whoever added it, whether you can remove > it". > > i don't say how things should be, i just say how they are... well... me too :) my point is that it is really easy to remove a branch or a tag from CVS, but it is a lot of work to remove the bconds from multiple specs. regards, wrobell From radek at pld-linux.org Wed Dec 24 12:55:56 2008 From: radek at pld-linux.org (Radoslaw Zielinski) Date: Wed, 24 Dec 2008 12:55:56 +0100 Subject: libdrm 2.4.3 => X segfault Message-ID: <20081224115556.GA7198@bzium> After upgrading libdrm to 2.4.3, my X have segfaulted like this: Backtrace: 0: /usr/bin/Xorg(xorg_backtrace+0x3b) [0x8120717] 1: /usr/bin/Xorg(xf86SigHandler+0x4d) [0x80b7980] 2: [0xb80c5400] 3: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b97400] 4: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b98c36] 5: /usr/bin/Xorg(AddScreen+0x184) [0x806ac36] 6: /usr/bin/Xorg(InitOutput+0x1f7) [0x809fff8] 7: /usr/bin/Xorg(main+0x276) [0x806b3e9] 8: /lib/libc.so.6(__libc_start_main+0xee) [0xb7cf46ee] Fatal server error: Caught signal 11. Server aborting Full log: http://radek.cc/Xorg.0.log Does something need to be rebuilt...? Or is it just a screwed up release? -- Rados?aw Zieli?ski -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From arekm at maven.pl Wed Dec 24 13:00:34 2008 From: arekm at maven.pl (Arkadiusz Miskiewicz) Date: Wed, 24 Dec 2008 13:00:34 +0100 Subject: libdrm 2.4.3 => X segfault In-Reply-To: <20081224115556.GA7198@bzium> References: <20081224115556.GA7198@bzium> Message-ID: <200812241300.34654.arekm@maven.pl> On Wednesday 24 of December 2008, Radoslaw Zielinski wrote: > After upgrading libdrm to 2.4.3, my X have segfaulted like this: > > Backtrace: > 0: /usr/bin/Xorg(xorg_backtrace+0x3b) [0x8120717] > 1: /usr/bin/Xorg(xf86SigHandler+0x4d) [0x80b7980] > 2: [0xb80c5400] > 3: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b97400] > 4: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b98c36] > 5: /usr/bin/Xorg(AddScreen+0x184) [0x806ac36] > 6: /usr/bin/Xorg(InitOutput+0x1f7) [0x809fff8] > 7: /usr/bin/Xorg(main+0x276) [0x806b3e9] > 8: /lib/libc.so.6(__libc_start_main+0xee) [0xb7cf46ee] > > Fatal server error: > Caught signal 11. Server aborting > > > Full log: http://radek.cc/Xorg.0.log > > Does something need to be rebuilt...? > Or is it just a screwed up release? We don't know, yet - http://lists.pld-linux.org/mailman/pipermail/pld-devel-pl/2008-December/147897.html -- Arkadiusz Mi?kiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/ From wrobell at pld-linux.org Wed Dec 24 16:42:59 2008 From: wrobell at pld-linux.org (wrobell) Date: Wed, 24 Dec 2008 15:42:59 +0000 Subject: libdrm 2.4.3 => X segfault In-Reply-To: <20081224115556.GA7198@bzium> References: <20081224115556.GA7198@bzium> Message-ID: <20081224154258.GA4728@borg.culture.mapflow.com> On Wed, Dec 24, 2008 at 12:55:56PM +0100, Radoslaw Zielinski wrote: > After upgrading libdrm to 2.4.3, my X have segfaulted like this: > > Backtrace: > 0: /usr/bin/Xorg(xorg_backtrace+0x3b) [0x8120717] > 1: /usr/bin/Xorg(xf86SigHandler+0x4d) [0x80b7980] > 2: [0xb80c5400] > 3: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b97400] > 4: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b98c36] > 5: /usr/bin/Xorg(AddScreen+0x184) [0x806ac36] > 6: /usr/bin/Xorg(InitOutput+0x1f7) [0x809fff8] > 7: /usr/bin/Xorg(main+0x276) [0x806b3e9] > 8: /lib/libc.so.6(__libc_start_main+0xee) [0xb7cf46ee] > > Fatal server error: > Caught signal 11. Server aborting > > > Full log: http://radek.cc/Xorg.0.log which version of kernel? regards, wrobell From radek at pld-linux.org Wed Dec 24 16:34:59 2008 From: radek at pld-linux.org (Radoslaw Zielinski) Date: Wed, 24 Dec 2008 16:34:59 +0100 Subject: libdrm 2.4.3 => X segfault In-Reply-To: <20081224154258.GA4728@borg.culture.mapflow.com> References: <20081224115556.GA7198@bzium> <20081224154258.GA4728@borg.culture.mapflow.com> Message-ID: <20081224153459.GA5052@bzium> wrobell [24-12-2008 16:42]: > On Wed, Dec 24, 2008 at 12:55:56PM +0100, Radoslaw Zielinski wrote: > > After upgrading libdrm to 2.4.3, my X have segfaulted like this: [...] > which version of kernel? kernel-2.6.27.10-1.i686 (latest in Th repository). -- Rados?aw Zieli?ski -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From udvzsolt at gmail.com Thu Dec 25 17:52:29 2008 From: udvzsolt at gmail.com (Zsolt Udvari) Date: Thu, 25 Dec 2008 17:52:29 +0100 Subject: TeXLive again Message-ID: <760ece280812250852r5d3a72ebx3398c0054718bbd@mail.gmail.com> Hi all! First: happy and merry christmas! Second: as you know, I'm working on texlive.spec. From it you can create the packages (all platforms, except ppc), but it don't works. Maybe it missed some %dir, and maybe(?) there are mixed (need cleaning) but the main error: can't create a simple dvi file. E.g. from simple 'hello.tex' ------ code ------ Hello, World! \bye -- end code -- can't build dvi output ("tex hello.tex"). First: you must set TEXMFMAIN environment variable (this maybe isn't error, but would be nice when shouldn't set). Second: it missed *.fmt and I don't know how can I create. This the biggest problem. So, if anyone use(d) (La)TeX and knows (a little) how it works, and has free time, please check and try it! And correct the texlive.spec or send me his/her suggestions. Thanks! Zsolt From qboosh at pld-linux.org Fri Dec 26 13:04:25 2008 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Fri, 26 Dec 2008 13:04:25 +0100 Subject: SPECS: iceweasel-lang-ca.spec - fixed License information, translated pl in... In-Reply-To: References:

Message-ID: <20081226120425.GA5957@stranger.qboosh.pl> On Fri, Dec 26, 2008 at 01:03:04PM +0100, qboosh wrote: > Author: qboosh Date: Fri Dec 26 12:03:04 2008 GMT > Module: SPECS Tag: HEAD > ---- Log message: > - fixed License information, translated pl into Polish Please fix remaining iceweasel-lang-* in the same way > ================================================================ > Index: SPECS/iceweasel-lang-ca.spec > diff -u SPECS/iceweasel-lang-ca.spec:1.10 SPECS/iceweasel-lang-ca.spec:1.11 > --- SPECS/iceweasel-lang-ca.spec:1.10 Wed Dec 17 12:28:20 2008 > +++ SPECS/iceweasel-lang-ca.spec Fri Dec 26 13:02:58 2008 > @@ -3,11 +3,11 @@ > Summary: Catalan resources for Iceweasel > Summary(ca.UTF-8): Recursos catalans per Iceweasel > Summary(es.UTF-8): Recursos catalanes para Iceweasel > -Summary(pl.UTF-8): Katalo?skie pliki j?zykowe dla Iceweasel > +Summary(pl.UTF-8): Katalo?skie pliki j?zykowe dla Iceweasela > Name: iceweasel-lang-%{_lang} > Version: 3.0.5 > Release: 1 > -License: GPL > +License: MPL 1.1 or GPL v2+ or LGPL v2.1+ > Group: I18n > Source0: http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/%{version}/linux-i686/xpi/%{_lang}.xpi > # Source0-md5: 2f07344aa1c82ef333b4c2e8f85e4bb5 > @@ -34,7 +34,7 @@ > Recursos catalanes para Iceweasel. > > %description -l pl.UTF-8 > -Katalo?skie pliki j?zykowe dla Iceweasel. > +Katalo?skie pliki j?zykowe dla Iceweasela. > > %prep > -- Jakub Bogusz http://qboosh.pl/ From udvzsolt at gmail.com Sat Dec 27 16:36:52 2008 From: udvzsolt at gmail.com (Zsolt Udvari) Date: Sat, 27 Dec 2008 16:36:52 +0100 Subject: TeXLive again In-Reply-To: <760ece280812250852r5d3a72ebx3398c0054718bbd@mail.gmail.com> References: <760ece280812250852r5d3a72ebx3398c0054718bbd@mail.gmail.com> Message-ID: <760ece280812270736x1bb8d15fj9e17b5cabe51a5e7@mail.gmail.com> > First: you must set TEXMFMAIN environment variable (this maybe isn't > error, but would be nice when shouldn't set). > Second: it missed *.fmt and I don't know how can I create. This the > biggest problem. It's done. Next problem: sometimes needs to create fonts, and there are few possibilities: - create the fonts to $HOME/.texlive-2008 directory - imho this is not too good solution - create the fonts to /var/lib/texmf (or any other directory) - it's the better, but there are problems with this. It must be writeable by all users. The idea, that its owner/group is 'texmf', and some files of texlive has sgid, doesn't work, because it calls 'mkdir', 'cp'. What should I do? Zsolt From sparky at pld-linux.org Sat Dec 27 19:16:33 2008 From: sparky at pld-linux.org (Przemyslaw Iskra) Date: Sat, 27 Dec 2008 19:16:33 +0100 Subject: TeXLive again In-Reply-To: <760ece280812270736x1bb8d15fj9e17b5cabe51a5e7@mail.gmail.com> References: <760ece280812250852r5d3a72ebx3398c0054718bbd@mail.gmail.com> <760ece280812270736x1bb8d15fj9e17b5cabe51a5e7@mail.gmail.com> Message-ID: <20081227181633.GA4235@pld-linux.org> On Sat, Dec 27, 2008 at 04:36:52PM +0100, Zsolt Udvari wrote: > > First: you must set TEXMFMAIN environment variable (this maybe isn't > > error, but would be nice when shouldn't set). > > Second: it missed *.fmt and I don't know how can I create. This the > > biggest problem. > It's done. > > Next problem: sometimes needs to create fonts, and there are few possibilities: > - create the fonts to $HOME/.texlive-2008 directory - imho this is not > too good solution > - create the fonts to /var/lib/texmf (or any other directory) - it's > the better, but there are problems with this. > It must be writeable by all users. The idea, that its owner/group is > 'texmf', and some files of texlive has sgid, doesn't work, because it > calls 'mkdir', 'cp'. > > What should I do? Could you tell us more about those fonts ? As far as I understand this is just some font cache. - Is it generated for every shape and size ? - How big are those files, compared to source ? - How much time does it take to generate them ? - How often same cache is used ? How probable is that different users will be interested in same font cache ? Maybe we could generate this cache for fonts we distribute and place it somewere under /usr/share ? And if a user needs some additional fonts she could just use that $HOME/.tex... directory. -- ____ Sparky{PI] -- Przemyslaw _ ___ _ _ ........... LANG...Pl..Ca..Es..En /____) ___ ___ _ _ || Iskra | | _ \| | | : WWW........ppcrcd.pld-linux.org \____\| -_)'___| ||^'||//\\// < | _/| | | : JID......sparkyjabberes.org (____/|| (_-_|_|| ||\\ || |_ |_| |_| _| : Mail....sparkypld-linux.org From wrobell at pld-linux.org Sun Dec 28 02:31:25 2008 From: wrobell at pld-linux.org (wrobell) Date: Sun, 28 Dec 2008 01:31:25 +0000 Subject: TeXLive again In-Reply-To: <760ece280812270736x1bb8d15fj9e17b5cabe51a5e7@mail.gmail.com> References: <760ece280812250852r5d3a72ebx3398c0054718bbd@mail.gmail.com> <760ece280812270736x1bb8d15fj9e17b5cabe51a5e7@mail.gmail.com> Message-ID: <20081228013125.GB27587@borg> On Sat, Dec 27, 2008 at 04:36:52PM +0100, Zsolt Udvari wrote: > > First: you must set TEXMFMAIN environment variable (this maybe isn't > > error, but would be nice when shouldn't set). > > Second: it missed *.fmt and I don't know how can I create. This the > > biggest problem. > It's done. > > Next problem: sometimes needs to create fonts, and there are few possibilities: > - create the fonts to $HOME/.texlive-2008 directory - imho this is not > too good solution > - create the fonts to /var/lib/texmf (or any other directory) - it's > the better, but there are problems with this. > It must be writeable by all users. The idea, that its owner/group is > 'texmf', and some files of texlive has sgid, doesn't work, because it > calls 'mkdir', 'cp'. > > What should I do? that was solved in tetex.spec, isn't it? /var/cache/fonts has sticky bit if i reckon well. wrobell From wrobell at pld-linux.org Sun Dec 28 02:29:31 2008 From: wrobell at pld-linux.org (wrobell) Date: Sun, 28 Dec 2008 01:29:31 +0000 Subject: TeXLive again In-Reply-To: <20081227181633.GA4235@pld-linux.org> References: <760ece280812250852r5d3a72ebx3398c0054718bbd@mail.gmail.com> <760ece280812270736x1bb8d15fj9e17b5cabe51a5e7@mail.gmail.com> <20081227181633.GA4235@pld-linux.org> Message-ID: <20081228012931.GA27587@borg> On Sat, Dec 27, 2008 at 07:16:33PM +0100, Przemyslaw Iskra wrote: > On Sat, Dec 27, 2008 at 04:36:52PM +0100, Zsolt Udvari wrote: > > > First: you must set TEXMFMAIN environment variable (this maybe isn't > > > error, but would be nice when shouldn't set). > > > Second: it missed *.fmt and I don't know how can I create. This the > > > biggest problem. > > It's done. > > > > Next problem: sometimes needs to create fonts, and there are few possibilities: > > - create the fonts to $HOME/.texlive-2008 directory - imho this is not > > too good solution > > - create the fonts to /var/lib/texmf (or any other directory) - it's > > the better, but there are problems with this. > > It must be writeable by all users. The idea, that its owner/group is > > 'texmf', and some files of texlive has sgid, doesn't work, because it > > calls 'mkdir', 'cp'. > > > > What should I do? > > Could you tell us more about those fonts ? As far as I understand this > is just some font cache. > - Is it generated for every shape and size ? > - How big are those files, compared to source ? > - How much time does it take to generate them ? > - How often same cache is used ? How probable is that different users > will be interested in same font cache ? > > Maybe we could generate this cache for fonts we distribute and place it > somewere under /usr/share ? And if a user needs some additional fonts > she could just use that $HOME/.tex... directory. that's bit complicated. if you use different dpi for you dvi documents, then fonts should be regenerated for you. for sure people are using 300dpi, 600dpi, but... you never know :) wrobell From z at xatka.net Mon Dec 29 02:22:48 2008 From: z at xatka.net (=?utf-8?q?Pawe=C5=82_Zuzelski?=) Date: Mon, 29 Dec 2008 02:22:48 +0100 Subject: /usr/{share,lib}/java Message-ID: <200812290222.48828.z@xatka.net> What is the difference between /usr/share/java and /usr/lib/java directories? Most specs installs jar files into /usr/share/java, but there are few specs that uses /usr/lib/java? (for example gnu.regexp.spec and batik.spec) Regards, Pawe? Zuzelski -- ..... Pozdrawiam, ..... ..... Pawel Zuzelski ..... ..... jid:pzz at touk.pl ..... From glen at delfi.ee Mon Dec 29 09:45:59 2008 From: glen at delfi.ee (Elan =?utf-8?q?Ruusam=C3=A4e?=) Date: Mon, 29 Dec 2008 10:45:59 +0200 Subject: /usr/{share,lib}/java In-Reply-To: <200812290222.48828.z@xatka.net> References: <200812290222.48828.z@xatka.net> Message-ID: <200812291045.59952.glen@delfi.ee> On Monday 29 December 2008 03:22, Pawe? Zuzelski wrote: > What is the difference between /usr/share/java and /usr/lib/java > directories? dunno. > Most specs installs jar files into /usr/share/java, but there are few specs > that uses /usr/lib/java? (for example gnu.regexp.spec and batik.spec) outdated and both should be updated to use %{_javadir}. > Regards, > Pawe? Zuzelski -- glen From udvzsolt at gmail.com Mon Dec 29 15:42:33 2008 From: udvzsolt at gmail.com (Zsolt Udvari) Date: Mon, 29 Dec 2008 15:42:33 +0100 Subject: TeXLive rel 0.8 testing Message-ID: <760ece280812290642t75f1046cv43ca539a1364bcd9@mail.gmail.com> Hi all! I hope there are many-many pld users, who wants TeXLive. So, here is the uniqe chance! There is a(n almost) ready version of TeXLive (2008), but needed some testing. You can download the 0.8 release from carme-i686:/var/tmp/uzsolt-texlive. In this directory there is a file BASE_RPMS, which contains the name of the rpms, with them you can use/compile/view/... not too complicated TeX/LaTeX files. The TeXLive is more faster than "old" tetex, so please try and test it! You can bugreport or send me an email or can modify texlive.spec, when you found a bug. When there are not "critical" bugs, can change the release to 1, send STBR, and after rebuild texlive.spec (bootstrap). Zsolt From witek.firlej at gmail.com Mon Dec 29 16:45:55 2008 From: witek.firlej at gmail.com (Witek Firlej) Date: Mon, 29 Dec 2008 16:45:55 +0100 Subject: TeXLive rel 0.8 testing In-Reply-To: <760ece280812290642t75f1046cv43ca539a1364bcd9@mail.gmail.com> References: <760ece280812290642t75f1046cv43ca539a1364bcd9@mail.gmail.com> Message-ID: On Mon, Dec 29, 2008 at 3:42 PM, Zsolt Udvari wrote: > Hi all! > > I hope there are many-many pld users, who wants TeXLive. So, here is > the uniqe chance! > There is a(n almost) ready version of TeXLive (2008), but needed some testing. > You can download the 0.8 release from > carme-i686:/var/tmp/uzsolt-texlive. In this directory there is a file Give a full link and forward this msg to pld-user-list. -- :: Witek Firlej :: Voiceless it cries, Wingless flutters, Toothless bites, Mouthless mutters. :: http://grizz.pl :: http://grizz.firlej.org :: jid: grizz//jabster.pl :: From deejay1 at srem.org Mon Dec 29 19:42:59 2008 From: deejay1 at srem.org (=?UTF-8?Q?=C5=81ukasz_Jerna=C5=9B?=) Date: Mon, 29 Dec 2008 19:42:59 +0100 Subject: TeXLive rel 0.8 testing In-Reply-To: <760ece280812290642t75f1046cv43ca539a1364bcd9@mail.gmail.com> References: <760ece280812290642t75f1046cv43ca539a1364bcd9@mail.gmail.com> Message-ID: <77fcfd0a0812291042x45a84915xad185e57cf9f023c@mail.gmail.com> On Mon, Dec 29, 2008 at 3:42 PM, Zsolt Udvari wrote: > Hi all! > > I hope there are many-many pld users, who wants TeXLive. So, here is > the uniqe chance! > There is a(n almost) ready version of TeXLive (2008), but needed some testing. > You can download the 0.8 release from > carme-i686:/var/tmp/uzsolt-texlive. In this directory there is a file > BASE_RPMS, which contains the name of the rpms, with them you can > use/compile/view/... not too complicated TeX/LaTeX files. > The TeXLive is more faster than "old" tetex, so please try and test it! > You can bugreport or send me an email or can modify texlive.spec, when > you found a bug. Wouldn't it be better to post them in your ~/public_html together with poldek indexes? Regards, -- ?ukasz [DeeJay1] Jerna? From udvzsolt at gmail.com Mon Dec 29 19:49:40 2008 From: udvzsolt at gmail.com (Zsolt Udvari) Date: Mon, 29 Dec 2008 19:49:40 +0100 Subject: TeXLive rel 0.8 testing In-Reply-To: <77fcfd0a0812291042x45a84915xad185e57cf9f023c@mail.gmail.com> References: <760ece280812290642t75f1046cv43ca539a1364bcd9@mail.gmail.com> <77fcfd0a0812291042x45a84915xad185e57cf9f023c@mail.gmail.com> Message-ID: <760ece280812291049i6ed4cdd2ue0a6b61648da9861@mail.gmail.com> > Wouldn't it be better to post them in your ~/public_html together with > poldek indexes? OK. But how? Should I create RPMS directory? And create all architecture? I've built only i686 (my machine is i686 ;) ). And should I create RPMS/{i686,x86_64,...}? Zsolt From deejay1 at srem.org Mon Dec 29 19:53:46 2008 From: deejay1 at srem.org (=?UTF-8?Q?=C5=81ukasz_Jerna=C5=9B?=) Date: Mon, 29 Dec 2008 19:53:46 +0100 Subject: TeXLive rel 0.8 testing In-Reply-To: <760ece280812291049i6ed4cdd2ue0a6b61648da9861@mail.gmail.com> References: <760ece280812290642t75f1046cv43ca539a1364bcd9@mail.gmail.com> <77fcfd0a0812291042x45a84915xad185e57cf9f023c@mail.gmail.com> <760ece280812291049i6ed4cdd2ue0a6b61648da9861@mail.gmail.com> Message-ID: <77fcfd0a0812291053v228d0f8fm58ee9950647b38b7@mail.gmail.com> On Mon, Dec 29, 2008 at 7:49 PM, Zsolt Udvari wrote: >> Wouldn't it be better to post them in your ~/public_html together with >> poldek indexes? > OK. But how? Should I create RPMS directory? And create all > architecture? I've built only i686 (my machine is i686 ;) ). And > should I create RPMS/{i686,x86_64,...}? Well it's entirely up to you, but I would propose somethinglike that: ~/public_html/texlive/RPMS/{i686,whatever_arch_is_built} and then in the rpm directory run "poldek -s . --mkidxz" (sans quotes) of course don't forget to make the files readable. Regards, -- ?ukasz From udvzsolt at gmail.com Mon Dec 29 20:21:32 2008 From: udvzsolt at gmail.com (Zsolt Udvari) Date: Mon, 29 Dec 2008 20:21:32 +0100 Subject: TeXLive rel 0.8 testing In-Reply-To: <77fcfd0a0812291053v228d0f8fm58ee9950647b38b7@mail.gmail.com> References: <760ece280812290642t75f1046cv43ca539a1364bcd9@mail.gmail.com> <77fcfd0a0812291042x45a84915xad185e57cf9f023c@mail.gmail.com> <760ece280812291049i6ed4cdd2ue0a6b61648da9861@mail.gmail.com> <77fcfd0a0812291053v228d0f8fm58ee9950647b38b7@mail.gmail.com> Message-ID: <760ece280812291121n2679aa4by341f6db6d3c5bca4@mail.gmail.com> > Well it's entirely up to you, but I would propose somethinglike that: > ~/public_html/texlive/RPMS/{i686,whatever_arch_is_built} > and then in the rpm directory run "poldek -s . --mkidxz" (sans quotes) > of course don't forget to make the files readable. IMHO it's done. http://carme.pld-linux.org/~uzsolt/texlive/RPMS/i686/ From adamg at pld-linux.org Mon Dec 29 23:06:39 2008 From: adamg at pld-linux.org (Adam Golebiowski) Date: Mon, 29 Dec 2008 23:06:39 +0100 Subject: TeXLive rel 0.8 testing In-Reply-To: <760ece280812291121n2679aa4by341f6db6d3c5bca4@mail.gmail.com> References: <760ece280812290642t75f1046cv43ca539a1364bcd9@mail.gmail.com> <77fcfd0a0812291053v228d0f8fm58ee9950647b38b7@mail.gmail.com> <760ece280812291121n2679aa4by341f6db6d3c5bca4@mail.gmail.com> Message-ID: <200812292306.39299.adamg@pld-linux.org> On Monday 29 December 2008, Zsolt Udvari wrote: > > Well it's entirely up to you, but I would propose somethinglike that: > > ~/public_html/texlive/RPMS/{i686,whatever_arch_is_built} > > and then in the rpm directory run "poldek -s . --mkidxz" (sans quotes) > > of course don't forget to make the files readable. > > IMHO it's done. > http://carme.pld-linux.org/~uzsolt/texlive/RPMS/i686/ Great, thanks. I tried installing it inside chroot and failed with: [root at ankh-th ~]# LANG=C poldek -s http://carme.pld-linux.org/~uzsolt/texlive/RPMS/i686/ -n th --root /chr (...) poldek:/all-avail> install texlive- Processing dependencies... texlive-20080816-0.8.i686 marks texlive-dirs-fonts-20080816-0.8.i686 (cap /usr/share/texmf-dist/fonts/enc/dvips/vntex) texlive-dirs-fonts-20080816-0.8.i686 marks texlive-fonts-marvosym-20080816-0.8.i686 (cap /usr/share/texmf-dist/doc/latex/marvosym/mac/oztex) error: texlive-fonts-marvosym-20080816-0.8.i686: req /usr/share/texmf-dist/source/fonts/eurofont not found texlive-fonts-marvosym-20080816-0.8.i686 marks texlive-latex-20080816-0.8.i686 (cap /usr/share/texmf-dist/tex/latex) texlive-latex-20080816-0.8.i686 marks tetex-latex-3.0-12.i686 (cap /usr/share/texmf/tex/latex) tetex-latex-3.0-12.i686 marks tetex-3.0-12.i686 (cap tetex = 1:3.0-12) tetex-3.0-12.i686: required "libkpathsea.so.4" is provided by following packages: a) kpathsea-3.0-12.i686 b) kpathsea-20080816-0.8.i686 Which one do you want to install ('Q' to abort)? [a] tetex-3.0-12.i686 marks kpathsea-20080816-0.8.i686 (cap libkpathsea.so.4) tetex-3.0-12.i686 marks tetex-dirs-fonts-3.0-12.i686 (cap tetex-dirs-fonts) tetex-3.0-12.i686 marks tetex-fonts-cm-3.0-12.i686 (cap tetex-fonts-cm = 1:3.0-12) tetex-3.0-12.i686 marks tetex-fonts-misc-3.0-12.i686 (cap tetex-fonts-misc = 1:3.0-12) tetex-3.0-12.i686 marks tetex-metafont-3.0-12.i686 (cap tetex-metafont = 1:3.0-12) tetex-latex-3.0-12.i686 marks tetex-fonts-eurosym-3.0-12.i686 (cap tetex-fonts-eurosym = 1:3.0-12) tetex-latex-3.0-12.i686 marks tetex-fonts-latex-3.0-12.i686 (cap tetex-fonts-latex = 1:3.0-12) texlive-latex-20080816-0.8.i686 marks texlive-fonts-eurosym-20080816-0.8.i686 (cap texlive-fonts-eurosym = 20080816-0.8) texlive-fonts-eurosym-20080816-0.8.i686 marks texlive-fonts-cm-20080816-0.8.i686 (cap /usr/share/texmf-dist/doc/fonts) texlive-latex-20080816-0.8.i686 marks texlive-fonts-latex-20080816-0.8.i686 (cap texlive-fonts-latex = 20080816-0.8) texlive-fonts-latex-20080816-0.8.i686 marks texlive-fonts-type1-bluesky-20080816-0.8.i686 (cap /usr/share/texmf-dist/fonts/type1/bluesky) texlive-latex-20080816-0.8.i686 marks texlive-tex-ruhyphen-20080816-0.8.i686 (cap texlive-tex-ruhyphen) error: texlive-tex-ruhyphen-20080816-0.8.i686: req /usr/share/texmf-dist/source/generic not found texlive-latex-20080816-0.8.i686 marks texlive-tex-ukrhyph-20080816-0.8.i686 (cap texlive-tex-ukrhyph) error: texlive-dirs-fonts-20080816-0.8.i686: req /usr/share/texmf-dist/tex4ht not found texlive-20080816-0.8.i686 marks texlive-cslatex-20080816-0.8.i686 (cap /usr/share/texmf-dist/tex/cslatex/base) texlive-cslatex-20080816-0.8.i686 marks texlive-fonts-cs-20080816-0.8.i686 (cap texlive-fonts-cs = 20080816-0.8) texlive-cslatex-20080816-0.8.i686 marks texlive-plain-20080816-0.8.i686 (cap texlive-plain = 20080816-0.8) texlive-20080816-0.8.i686: required "texconfig" is provided by following packages: a) texconfig-3.0-12.i686 b) texconfig-20080816-0.8.i686 Which one do you want to install ('Q' to abort)? [a] texlive-20080816-0.8.i686 marks texconfig-20080816-0.8.i686 (cap texconfig) texconfig-20080816-0.8.i686 marks texlive-dvips-20080816-0.8.i686 (cap texlive-dvips = 20080816-0.8) texconfig-20080816-0.8.i686 marks texlive-metafont-20080816-0.8.i686 (cap texlive-metafont = 20080816-0.8) texconfig-20080816-0.8.i686 marks xdvi-20080816-0.8.i686 (cap xdvi = 20080816-0.8) texlive-20080816-0.8.i686 marks texlive-fonts-misc-20080816-0.8.i686 (cap texlive-fonts-misc = 20080816-0.8) error: texlive-20080816-0.8.i686 conflicts with tetex-3.0-12.i686 And it gets more scary if I try to install texlive*. adamg -- http://www.mysza.eu.org/ | Everybody needs someone sure, someone true, PLD Linux developer | Everybody needs some solid rock, I know I do. From udvzsolt at gmail.com Mon Dec 29 23:31:39 2008 From: udvzsolt at gmail.com (Zsolt Udvari) Date: Mon, 29 Dec 2008 23:31:39 +0100 Subject: TeXLive rel 0.8 testing In-Reply-To: <200812292306.39299.adamg@pld-linux.org> References: <760ece280812290642t75f1046cv43ca539a1364bcd9@mail.gmail.com> <77fcfd0a0812291053v228d0f8fm58ee9950647b38b7@mail.gmail.com> <760ece280812291121n2679aa4by341f6db6d3c5bca4@mail.gmail.com> <200812292306.39299.adamg@pld-linux.org> Message-ID: <760ece280812291431p480aa3blc3ae67565fde8e75@mail.gmail.com> > I tried installing it inside chroot and failed with: Imho it needs some %dir. With simple "rpm -i" can you install them? I don't have more free time (I must learn and work - with using of texlive ;) ), so if anyone has free time, feel free and modify the spec file ;) Zsolt