From shadzik at gmail.com Fri Jun 1 00:13:03 2012 From: shadzik at gmail.com (=?UTF-8?B?QmFydG9zeiDFmndpxIV0ZWs=?=) Date: Fri, 1 Jun 2012 00:13:03 +0200 Subject: [PATCH] kernel-vanilla In-Reply-To: <1338497241.30170.2.camel@pldmachine> References: <1338410970.2054.1.camel@pldmachine> <1338497241.30170.2.camel@pldmachine> Message-ID: 2012/5/31 Przemo Firszt : > On Wed, 2012-05-30 at 22:54 +0200, Bartosz ?wi?tek wrote: >> 2012/5/30 Przemo Firszt : >> > The patch not finished (new config options), but it allows to build the >> > vanilla kernel. >> >> So? What should be done with it now? >> Oh wait! I know! You should finish the patch, start your mails with a >> 'Hallo' and say nicely what you expect from the developers. Easy, >> right? >> Good luck! > > Let's make a nice flame out of this. > I don't expect _anything_ from the developers. If my patch is useful > apply it, if it's not ignore/comment back. I personally don't like people not saying anything and expecting everything, or geeks not being able to say 'Hello' just because their "matter is so much more important" than their form. Anyway, even if you manage to get your patch commited I wish you all the luck in the world, to get you hired by anyone who doesn't care about your lack of culture. Maybe there is a dark basement in a big company, where you won't need to communicate with other people directly ;) I hope for you there is. -- "I'm living proof if you do one thing right in your career, you can coast for a long time. A LOOOOONG time." -Guy Kawasaki From przemo at firszt.eu Fri Jun 1 10:32:37 2012 From: przemo at firszt.eu (Przemo Firszt) Date: Fri, 01 Jun 2012 09:32:37 +0100 Subject: [PATCH] kernel-vanilla In-Reply-To: References: <1338410970.2054.1.camel@pldmachine> <1338497241.30170.2.camel@pldmachine> Message-ID: <1338539557.30203.16.camel@pldmachine> On Fri, 2012-06-01 at 00:13 +0200, Bartosz ?wi?tek wrote: [..] > I personally don't like people not saying anything and expecting > everything, or geeks not being able to say 'Hello' just because their > "matter is so much more important" than their form. Anyway, even if > you manage to get your patch commited I wish you all the luck in the > world, to get you hired by anyone who doesn't care about your lack of > culture. > > Maybe there is a dark basement in a big company, where you won't need > to communicate with other people directly ;) I hope for you there is. Hi, I'm not treating this list as a social ground. It's purely technical and that's why I can't see anything wrong in sending a patch alone without any comments or "Please take a look at my patch." - this is obvious. BTW Email communication is awful: you're jumping to conclusions about me (lack of culture, a good workplace for me, me being antisocial geek) based on _one_ (broken) patch :-) I have to go back to my dark basement now to finish a patch ;-) -- Kind regards, Przemo Firszt From baggins at pld-linux.org Fri Jun 1 12:25:45 2012 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Fri, 1 Jun 2012 12:25:45 +0200 Subject: udev/systemd 183 in th-test Message-ID: <20120601102545.GC2459@sith.mimuw.edu.pl> *** lang=en Hi, As you may know udev, as of version 183, has been merged into systemd and is now built from systemd source tree. This new version of systemd and udev is now available in th-test. Due to libudev soname change, udev-libs must be installed with 'just-install' for now (dependant packages hasn't been rebuilt on purpose, to ease reverting in case of breakage). Please test and report if anything is broken. *** lang=pl Hej, Jak pewnie wiecie udev od wersji 183 zosta? po??czony z systemd i jest budowany ze ?r?de? systemd. Ta nowa wersja jest dost?pna w th-test. Poniewa? zmieni? si? soname libudev, pakiet udev-libs musi, p?ki co, by? instalowany przez 'just-install' (zale?ne pakiety celowo nie zosta?y przebudowane, ?eby by?o pro?ciej cofn?? si? do starszej wersji jakby co? by?o zepsute) Uprasza si? o przetestowanie i informacj? je?li co? jest zepsute. -- Jan R?korajski | PLD/Linux SysAdm | http://www.pld-linux.org/ bagginsmimuw.edu.pl bagginspld-linux.org From wrobell at pld-linux.org Fri Jun 1 20:44:56 2012 From: wrobell at pld-linux.org (Artur Wroblewski) Date: Fri, 1 Jun 2012 19:44:56 +0100 Subject: [PATCH] kernel-vanilla In-Reply-To: References: <1338410970.2054.1.camel@pldmachine> <1338497241.30170.2.camel@pldmachine> Message-ID: On Thu, May 31, 2012 at 11:13 PM, Bartosz ?wi?tek wrote: > 2012/5/31 Przemo Firszt : >> On Wed, 2012-05-30 at 22:54 +0200, Bartosz ?wi?tek wrote: >>> 2012/5/30 Przemo Firszt : >>> > The patch not finished (new config options), but it allows to build the >>> > vanilla kernel. >>> >>> So? What should be done with it now? >>> Oh wait! I know! You should finish the patch, start your mails with a >>> 'Hallo' and say nicely what you expect from the developers. Easy, >>> right? >>> Good luck! >> >> Let's make a nice flame out of this. >> I don't expect _anything_ from the developers. If my patch is useful >> apply it, if it's not ignore/comment back. > > I personally don't like people not saying anything and expecting > everything [...] Szadzik, could you please stop trolling and shut up if you have nothing constructive to say (as it is for last couple of weeks)? Please? Regards, w From shadzik at gmail.com Fri Jun 1 23:48:31 2012 From: shadzik at gmail.com (=?UTF-8?B?QmFydG9zeiDFmndpxIV0ZWs=?=) Date: Fri, 1 Jun 2012 23:48:31 +0200 Subject: [PATCH] kernel-vanilla In-Reply-To: References: <1338410970.2054.1.camel@pldmachine> <1338497241.30170.2.camel@pldmachine>

Message-ID: 2012/6/1 Artur Wroblewski : > On Thu, May 31, 2012 at 11:13 PM, Bartosz ?wi?tek wrote: >> 2012/5/31 Przemo Firszt : >>> On Wed, 2012-05-30 at 22:54 +0200, Bartosz ?wi?tek wrote: >>>> 2012/5/30 Przemo Firszt : >>>> > The patch not finished (new config options), but it allows to build the >>>> > vanilla kernel. >>>> >>>> So? What should be done with it now? >>>> Oh wait! I know! You should finish the patch, start your mails with a >>>> 'Hallo' and say nicely what you expect from the developers. Easy, >>>> right? >>>> Good luck! >>> >>> Let's make a nice flame out of this. >>> I don't expect _anything_ from the developers. If my patch is useful >>> apply it, if it's not ignore/comment back. >> >> I personally don't like people not saying anything and expecting >> everything > [...] > > Szadzik, could you please stop trolling If I could then I would, but I can't so I shan't. > and shut up if you have > nothing constructive to say (as it is for last couple of weeks)? And vice versa. BTW. The nick is shadzik, not szadzik, my dear fr?bel. -- "I'm living proof if you do one thing right in your career, you can coast for a long time. A LOOOOONG time." -Guy Kawasaki From glen at pld-linux.org Mon Jun 4 17:02:44 2012 From: glen at pld-linux.org (=?ISO-8859-1?Q?Elan_Ruusam=E4e?=) Date: Mon, 04 Jun 2012 18:02:44 +0300 Subject: packages: xen/xen-watchdog.init, xen/xen.spec, xen/xenconsoled.init, xen/xe... In-Reply-To: References:

Message-ID: <4FCCCE14.90100@pld-linux.org> On 04.06.2012 17:48, mmazur wrote: > Author: mmazur Date: Mon Jun 4 14:48:55 2012 GMT > Module: packages Tag: HEAD > ---- Log message: > - rel 4 > - remove the lsb-style init stanzas from init scripts; our chkconfig is too > old to support it and if we ever upgraded, then magically xen would stop > booting correctly this is not true. we "support" them, via systemd sysv emulation -- glen From jajcus at jajcus.net Mon Jun 4 18:15:16 2012 From: jajcus at jajcus.net (Jacek Konieczny) Date: Mon, 4 Jun 2012 18:15:16 +0200 Subject: packages: xen/xen-watchdog.init, xen/xen.spec, xen/xenconsoled.init, xen/xe... In-Reply-To: <4FCCCE14.90100@pld-linux.org> References:

<4FCCCE14.90100@pld-linux.org> Message-ID: <20120604161516.GA5733@lolek.nigdzie> On Mon, Jun 04, 2012 at 06:02:44PM +0300, Elan Ruusam?e wrote: > On 04.06.2012 17:48, mmazur wrote: > > Author: mmazur Date: Mon Jun 4 14:48:55 2012 GMT > > Module: packages Tag: HEAD > > ---- Log message: > > - rel 4 > > - remove the lsb-style init stanzas from init scripts; our chkconfig is too > > old to support it and if we ever upgraded, then magically xen would stop > > booting correctly > this is not true. we "support" them, via systemd sysv emulation And removing some functionality, because 'we don't support it right now' does not sound like a good idea. If an upgrade can cause problems then this should be handled by a trigger in the upgraded package. Even if now most Th and other PLD-based system ignore that information it does not mean it is not useful for anyone. I say no for removing information from packages. Greets, Jacek From qboosh at pld-linux.org Mon Jun 4 20:00:56 2012 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Mon, 4 Jun 2012 20:00:56 +0200 Subject: packages: seamonkey/seamonkey.spec - fixed install - updated files - mailne... In-Reply-To: References:

Message-ID: <20120604180056.GA31027@mail> On Mon, Jun 04, 2012 at 02:46:09PM +0200, baggins wrote: > Author: baggins Date: Mon Jun 4 12:46:09 2012 GMT > Module: packages Tag: HEAD > ---- Log message: > - fixed install > - updated files > - mailnews in separate package makes no sense Why not? No longer splittable? -- Jakub Bogusz http://qboosh.pl/ From baggins at pld-linux.org Mon Jun 4 20:38:09 2012 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Mon, 4 Jun 2012 20:38:09 +0200 Subject: packages: seamonkey/seamonkey.spec - fixed install - updated files - mailne... In-Reply-To: <20120604180056.GA31027@mail> References:

<20120604180056.GA31027@mail> Message-ID: <20120604183809.GA12210@sith.mimuw.edu.pl> On Mon, 04 Jun 2012, Jakub Bogusz wrote: > On Mon, Jun 04, 2012 at 02:46:09PM +0200, baggins wrote: > > Author: baggins Date: Mon Jun 4 12:46:09 2012 GMT > > Module: packages Tag: HEAD > > ---- Log message: > > - fixed install > > - updated files > > - mailnews in separate package makes no sense > > Why not? > No longer splittable? Looks like that. If I package the same files as in iceweasel/firefox (ie just browser functionality + common files) in main package, then it will still advertise and allow to open mail app, but with random non-functionality. So, there is no point in splitting. Oh, and separate mailnews package would be approximately 70KB, comparing to megabytes of main package gives one more argument against split. -- Jan R?korajski | PLD/Linux SysAdm | http://www.pld-linux.org/ bagginsmimuw.edu.pl bagginspld-linux.org From mmazur at kernel.pl Tue Jun 5 11:30:50 2012 From: mmazur at kernel.pl (Mariusz Mazur) Date: Tue, 5 Jun 2012 11:30:50 +0200 Subject: packages: xen/xen-watchdog.init, xen/xen.spec, xen/xenconsoled.init, xen/xe... In-Reply-To: <20120604161516.GA5733@lolek.nigdzie> References: <4FCCCE14.90100@pld-linux.org> <20120604161516.GA5733@lolek.nigdzie> Message-ID: <201206051130.50724.mmazur@kernel.pl> On Mon of June 4 2012, Jacek Konieczny wrote: > And removing some functionality, because 'we don't support it right now' > does not sound like a good idea. If an upgrade can cause problems then > this should be handled by a trigger in the upgraded package. > > Even if now most Th and other PLD-based system ignore that information > it does not mean it is not useful for anyone. I say no for removing > information from packages. I've removed it to save other people the trouble once someone upgrades chkconfig. I'm not willing to try to figure out how this works and how to fix it, since it's not functionality that I have any use for. What I can do is can revert the change, but that would be with the assumption that I'm leaving it buggy as-is and it's going to be someone else's problem (when it stops working) some time in the future. Are you two both sure it's a preferable alternative? In something as important as xen? --mmazur From shadzik at gmail.com Wed Jun 6 13:36:15 2012 From: shadzik at gmail.com (=?UTF-8?B?QmFydG9zeiDFmndpxIV0ZWs=?=) Date: Wed, 6 Jun 2012 13:36:15 +0200 Subject: Postfix 2.9.3 Message-ID: Witam, w za??czniku patch na Postfiksa 2.9.3. Prosz? o komit. Pozdrawiam, b -- "I'm living proof if you do one thing right in your career, you can coast for a long time. A LOOOOONG time." -Guy Kawasaki -------------- next part -------------- A non-text attachment was scrubbed... Name: postfix.spec.patch Type: application/octet-stream Size: 829 bytes Desc: not available URL: From kiesiu at pld-linux.org Wed Jun 6 13:58:39 2012 From: kiesiu at pld-linux.org (Lukasz Kies) Date: Wed, 6 Jun 2012 13:58:39 +0200 Subject: Postfix 2.9.3 In-Reply-To: References: Message-ID: W dniu 6 czerwca 2012 13:36 u?ytkownik Bartosz ?wi?tek napisa?: > Witam, > > w za??czniku patch na Postfiksa 2.9.3. > Prosz? o komit. > > Pozdrawiam, > b Dodane, dzi?ki. -- Pozdrawiam, ?ukasz From lordblick at gmail.com Wed Jun 13 15:32:36 2012 From: lordblick at gmail.com (Lord Blick) Date: Wed, 13 Jun 2012 15:32:36 +0200 Subject: armst.spec Message-ID: <4FD89674.4060307@gmail.com> Include an attachment spec and small patch (cosmetic anti-warnings & fix install) so grateful for a tool that can be helpful in the construction of the programmer Versaloon(http://www.versaloon.com/) and other ST ARM grounded projects. I'd appreciate testings and comments. -- Best Regards, Lord Blick -------------- next part -------------- # $Revision: $, $Date: $ # Summary: ST ARM-CortexM3 Linux RS-232 Loader Summary(pl.UTF-8): ST ARM-CortexM3 Linux RS-232 Loader Name: armst Version: 1.20 Release: 1 License: GPL v3 Group: Development/Tools Source0: http://isotel.eu/ARMst/%{name}-%{version}-src.tgz # Source0-md5: aeaf4fa71c5b2cf7a4678409f82ec13e Patch0: stmbl.patch URL: http://isotel.eu/ARMst/ BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) %description The ARMst utility is a command line tool for flashing the ST ARM-CortexM3 family via the standard RS-232 port. %description -l pl.UTF-8 Narz?dzie ARMst jest uruchamialnym z konsoli narz?dziem do zapisywania w pami?ci mikrokontroler?w ST ARM Cortex-M3 przez standartowy port szeregowy RS-232. %prep %setup -n ARMst -q %patch0 -p0 %build %{__make} %install rm -rf $RPM_BUILD_ROOT install -d $RPM_BUILD_ROOT%{_bindir} %{__make} install \ DESTDIR=$RPM_BUILD_ROOT%{_bindir} %clean rm -rf $RPM_BUILD_ROOT %files %defattr(644,root,root,755) %{_bindir}/armst %define date %(echo `LC_ALL="C" date +"%a %b %d %Y"`) %changelog * %{date} PLD Team All persons listed below can be reached at @pld-linux.org $Log: armst.spec,v $ -------------- next part -------------- --- stmbl.c.oryg 2012-06-13 15:01:49.000000000 +0200 +++ stmbl.c 2012-06-13 15:12:51.000000000 +0200 @@ -127,7 +127,7 @@ int stmblRecv(uint8_t* buf, unsigned int size) { int rsize = 0; - int rval, i; + int rval; while( rsize < size ) { // Look whether there are still pending bytes in the buffer @@ -210,6 +210,7 @@ int stmblGetVersionNprotection() { + return 0; } @@ -236,7 +237,6 @@ address & 0xFF }; int rval; - int i; if (size > 256) return STMBL_ERR_SIZE; if (!stmblCmdAvail(0x11)) return STMBL_ERR_INVALIDCMD; @@ -308,19 +308,23 @@ int stmblWriteProtect() { + return 0; } int stmblWriteUnprotect() { + return 0; } int stmblReadoutProtect() { + return 0; } int stmblReadoutUnprotect() { + return 0; } --- Makefile~ 2012-06-13 15:17:22.000000000 +0200 +++ Makefile 2012-06-13 15:17:22.000000000 +0200 @@ -10,7 +10,7 @@ LIBS = CFLAGS = -Wall -g - +DESTDIR=/usr/local/bin # Do the stuff as specified above. all: armst @@ -19,7 +19,7 @@ $(CC) -o $@ $(CFLAGS) $(OBJ) $(LIBS) install: armst - install armst /usr/local/bin + install armst $(DESTDIR) clean: rm *~ *.o From glen at pld-linux.org Wed Jun 13 18:09:10 2012 From: glen at pld-linux.org (=?ISO-8859-1?Q?Elan_Ruusam=E4e?=) Date: Wed, 13 Jun 2012 19:09:10 +0300 Subject: armst.spec In-Reply-To: <4FD89674.4060307@gmail.com> References: <4FD89674.4060307@gmail.com> Message-ID: <4FD8BB26.3050105@pld-linux.org> On 13.06.2012 16:32, Lord Blick wrote: > Include an attachment spec and small patch (cosmetic anti-warnings & > fix install) so grateful for a tool that can be helpful in the > construction of the programmer Versaloon(http://www.versaloon.com/) > and other ST ARM grounded projects. > I'd appreciate testings and comments. don't have hardware to test, so just cleaned up and added to cvs also cleared summary appearing as polish, but really it was c-p from english -- glen From lordblick at gmail.com Thu Jun 14 12:30:19 2012 From: lordblick at gmail.com (Daniel Dawid Majewski) Date: Thu, 14 Jun 2012 12:30:19 +0200 Subject: eclipse-cpp-bin.spec Message-ID: <4FD9BD3B.7080603@gmail.com> Include an attachment spec and std desktop file. Spec is copy of eclipse-bin.spec, but it makes happiest all developers, which don't need JavaEE development stuff, so is for half size downloading, less residing in memory and a little faster version of archive.Actually I'm using package from this spec and until now haven't found any problems. I'd appreciate testings and comments. B.T.W. Should eclipse-bin.spec be renamed to eclipse-jee-bin.spec, as actually it uses binaries or change binaries to eclipse-SDK ? -- Best Regards, Lord Blick -------------- next part -------------- %bcond_without ix86 # don't download ix86 source %bcond_without x86_64 # don't download x86_64 source Summary: Eclipse - an open extensible IDE Summary(pl.UTF-8): Eclipse - otwarte, rozszerzalne ?rodowisko programistyczne Name: eclipse-cpp-bin Version: 3.7.2 Release: 1 License: EPL v1.0 Group: Development/Tools %if %{with ix86} Source0: ftp://ftp.uninett.no/pub/eclipse/technology/epp/downloads/release/indigo/SR2/eclipse-cpp-indigo-SR2-incubation-linux-gtk.tar.gz # Source0-md5: 98ba2db4c23957553ef332c6cbc1cc71 %endif %if %{with x86_64} Source1: ftp://ftp.uninett.no/pub/eclipse/technology/epp/downloads/release/indigo/SR2/eclipse-cpp-indigo-SR2-incubation-linux-gtk-x86_64.tar.gz # Source1-md5: 0c4d3065478c0e4751b13a8bc6120082 %endif Source2: eclipse.desktop URL: http://www.eclipse.org/ BuildRequires: rpm-pythonprov BuildRequires: unzip Requires: ant Requires: jdk >= 1.4 Conflicts: eclipse-SDK Conflicts: eclipse-bin Obsoletes: eclipse Provides: eclipse = %{version}-%{release} Provides: eclipse-cpp BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) %define eclipse_arch %(echo %{_target_cpu} | sed 's/i.86\\|athlon\\|pentium/x86/;s/amd64/x86_64/') %define no_install_post_chrpath 1 # list of script capabilities (regexps) not to be used in Provides %define _noautoprov libcairo.so.2 %description Eclipse is a kind of universal tool platform - an open extensible IDE for anything and nothing in particular. Current package includes C/C++ developmnet plugins %description -l pl.UTF-8 Eclipse to rodzaj uniwersalnej platformy narz?dziowej - otwarte, rozszerzalne IDE (zintegrowane ?rodowisko programistyczne) do wszystkiego i niczego w szczeg?lno?ci. Ten zestaw binar?w zawiera wtyczki do programowania w C/C++ %prep %ifarch %{ix86} %setup -q -T -c -a0 %endif %ifarch %{x8664} %setup -q -T -c -a1 %endif %install rm -rf $RPM_BUILD_ROOT install -d $RPM_BUILD_ROOT{{%{_libdir},%{_datadir}}/eclipse/dropins,%{_bindir}} \ $RPM_BUILD_ROOT{%{_desktopdir},%{_pixmapsdir},%{_sysconfdir}/eclipse} cd eclipse cp -a features p2 configuration plugins \ libcairo-swt.so eclipse artifacts.xml \ $RPM_BUILD_ROOT%{_libdir}/eclipse install -p icon.xpm $RPM_BUILD_ROOT%{_pixmapsdir}/eclipse-icon.xpm cp -p %{SOURCE2} $RPM_BUILD_ROOT%{_desktopdir} cp -p eclipse.ini $RPM_BUILD_ROOT%{_sysconfdir}/eclipse/eclipse.ini ln -s %{_libdir}/eclipse/eclipse $RPM_BUILD_ROOT%{_bindir} ln -s %{_sysconfdir}/eclipse/eclipse.ini $RPM_BUILD_ROOT%{_libdir}/eclipse/eclipse.ini # place for arch independent plugins install -d $RPM_BUILD_ROOT%{_datadir}/eclipse/{features,plugins} cat <<-'EOF'> $RPM_BUILD_ROOT%{_datadir}/eclipse/.eclipseextension name=Eclipse Platform id=org.eclipse.platform version=%{version} EOF %clean rm -rf $RPM_BUILD_ROOT %files %defattr(644,root,root,755) %doc eclipse/{about_files,readme,*html} %dir %{_libdir}/eclipse %dir %{_libdir}/eclipse/dropins %{_libdir}/eclipse/features %{_libdir}/eclipse/p2 %{_libdir}/eclipse/configuration %{_libdir}/eclipse/plugins %{_libdir}/eclipse/eclipse.ini %{_libdir}/eclipse/artifacts.xml %{_desktopdir}/eclipse.desktop %{_pixmapsdir}/eclipse-icon.xpm %dir %{_sysconfdir}/eclipse %config(noreplace) %verify(not md5 mtime size) %attr(644,root,root) %{_sysconfdir}/eclipse/eclipse.ini %attr(755,root,root) %{_libdir}/eclipse/libcairo-swt.so %attr(755,root,root) %{_libdir}/eclipse/eclipse %attr(755,root,root) %{_bindir}/eclipse %dir %{_datadir}/eclipse %dir %{_datadir}/eclipse/dropins %{_datadir}/eclipse/.eclipseextension %define date %(echo `LC_ALL="C" date +"%a %b %d %Y"`) %changelog * %{date} PLD Team All persons listed below can be reached at @pld-linux.org -------------- next part -------------- [Desktop Entry] Name=Eclipse Comment=Eclipse Comment[pl]=Eclipse Exec=eclipse Icon=eclipse-icon Terminal=false MultipleArgs=false Type=Application Categories=Development;IDE; # vi: encoding=utf-8 From glen at delfi.ee Thu Jun 14 13:20:09 2012 From: glen at delfi.ee (=?ISO-8859-1?Q?Elan_Ruusam=E4e?=) Date: Thu, 14 Jun 2012 14:20:09 +0300 Subject: eclipse-cpp-bin.spec In-Reply-To: <4FD9BD3B.7080603@gmail.com> References: <4FD9BD3B.7080603@gmail.com> Message-ID: <4FD9C8E9.4070903@delfi.ee> On 14.06.2012 13:30, Daniel Dawid Majewski wrote: > Include an attachment spec and std desktop file. Spec is copy of > eclipse-bin.spec, but it makes happiest all developers, which don't need > JavaEE development stuff, so is for half size downloading, less > residing in memory and a little faster version of archive.Actually I'm > using package from this spec and until now haven't found any problems. > I'd appreciate testings and comments. > B.T.W. Should eclipse-bin.spec be renamed to eclipse-jee-bin.spec, as > actually it uses binaries or change binaries to eclipse-SDK ? added for now with minor fixes but perhaps it should be made non-conflicting with eclipse installation, by using %{_libdir}/%{name} and %{_datadir}/%{name} as installation paths this would then of course lose the oppurtunity to use plugins installed to eclipse dir, or it's somehow solvable to setup it to use alternative (more than one) dropins dir? -- glen From lordblick at gmail.com Thu Jun 14 22:40:37 2012 From: lordblick at gmail.com (Lord Blick) Date: Thu, 14 Jun 2012 22:40:37 +0200 Subject: eclipse-cpp-bin.spec In-Reply-To: <4FD9C8E9.4070903@delfi.ee> References: <4FD9BD3B.7080603@gmail.com> <4FD9C8E9.4070903@delfi.ee> Message-ID: <4FDA4C45.10903@gmail.com> In reply on 14.06.2012 13:20, from Elan Ruusam?e: > added for now with minor fixes Thanks. > but perhaps it should be made non-conflicting with eclipse installation, > by using %{_libdir}/%{name} and %{_datadir}/%{name} as installation paths In my mean, it's alternative instalation of eclipse without JavaEE, nor some extension. Same packagings as on : http://www.eclipse.org/downloads/ -- Best Regards, Lord Blick From mmazur at kernel.pl Fri Jun 15 17:46:45 2012 From: mmazur at kernel.pl (Mariusz Mazur) Date: Fri, 15 Jun 2012 17:46:45 +0200 Subject: RM candidates Message-ID: <201206151746.45853.mmazur@kernel.pl> PLD Th is lacking a Release Manager (arekm stepped down recently) and due to recent regulation changes, a new one must get approved by a CDG vote. If you're interested in the position, please speak up (in this thread). --mmazur From pluto at agmk.net Fri Jun 15 21:38:13 2012 From: pluto at agmk.net (=?utf-8?B?UGF3ZcWC?= Sikora) Date: Fri, 15 Jun 2012 21:38:13 +0200 Subject: RM candidates In-Reply-To: <201206151746.45853.mmazur@kernel.pl> References: <201206151746.45853.mmazur@kernel.pl> Message-ID: <1506903.gufuH9JhKa@localhost> On Friday 15 of June 2012 17:46:45 Mariusz Mazur wrote: > PLD Th is lacking a Release Manager (arekm stepped down recently) and due to > recent regulation changes, a new one must get approved by a CDG vote. > > If you're interested in the position, please speak up (in this thread). do we need another so called release manager for pld-th neverending story? all major distro's bullets can be discussed on mailinglists and currently we only need a few people for maintaining ftp/rpm/pkgs deps consistency. From shadzik at gmail.com Fri Jun 15 21:41:50 2012 From: shadzik at gmail.com (=?UTF-8?B?QmFydG9zeiDFmndpxIV0ZWs=?=) Date: Fri, 15 Jun 2012 21:41:50 +0200 Subject: RM candidates In-Reply-To: <1506903.gufuH9JhKa@localhost> References: <201206151746.45853.mmazur@kernel.pl> <1506903.gufuH9JhKa@localhost> Message-ID: <-7350390451664752890@unknownmsgid> On 15 cze 2012, at 21:38, "Pawe? Sikora" wrote: > On Friday 15 of June 2012 17:46:45 Mariusz Mazur wrote: >> PLD Th is lacking a Release Manager (arekm stepped down recently) and due to >> recent regulation changes, a new one must get approved by a CDG vote. >> >> If you're interested in the position, please speak up (in this thread). > > do we need another so called release manager for pld-th neverending story? Yes, not everyone is happy with the existing politics... A more snapshot centric politic is advised. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6350 bytes Desc: not available URL: From glen at pld-linux.org Wed Jun 20 01:48:53 2012 From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=) Date: Wed, 20 Jun 2012 02:48:53 +0300 Subject: packages: icu/icu.spec - Maitnance release 4.8.1.1. Helps with my problems ... In-Reply-To: References:

Message-ID: <4FE10FE5.70506@pld-linux.org> On 06/19/2012 11:31 PM, lmasko wrote: > Author: lmasko Date: Tue Jun 19 20:31:21 2012 GMT > Module: packages Tag: HEAD > ---- Log message: > - Maitnance release 4.8.1.1. Helps with my problems with libreoffice. > > ---- Files affected: > packages/icu: > icu.spec (1.49 -> 1.50) > > ---- Diffs: > > ================================================================ > Index: packages/icu/icu.spec > diff -u packages/icu/icu.spec:1.49 packages/icu/icu.spec:1.50 > --- packages/icu/icu.spec:1.49 Wed Apr 11 18:38:47 2012 > +++ packages/icu/icu.spec Tue Jun 19 22:31:15 2012 > @@ -3,12 +3,12 @@ > Summary: International Components for Unicode > Summary(pl.UTF-8): Mi?dzynarodowe komponenty dla unikodu > Name: icu > -Version: 49.1.1 > +Version: 4.8.1.1 um, this is downgrade in sense of how rpm calculates versions $ rpmvercmp 49.1.1 4.8.1.1 49.1.1 > 4.8.1.1 did you see the previous commit? http://cvs.pld-linux.org/cgi-bin/viewvc.cgi/cvs/packages/icu/icu.spec?r1=1.48&r2=1.49 if you want to update 4.8 series, you should branch last 4.8 (as ICU_4_8 i guess) and take that, as HEAD already on new code version, which is stable so perfectly valid to have it on HEAD -- glen From draenog at pld-linux.org Wed Jun 20 16:20:11 2012 From: draenog at pld-linux.org (Kacper Kornet) Date: Wed, 20 Jun 2012 16:20:11 +0200 Subject: Git migration: authorship of cvs commits Message-ID: <20120620142011.GG21431@camk.edu.pl> Domy?lnie stare commity z CVS b?d? przeniesione do repozytori?w git z nast?puj?cymi danymi: Author: nick Committer: cvs2git Je?eli wolisz, ?eby w polu Author: widnia?o Twoje pe?ne imi? i nazwisko, powiniene? zmieni? odpowiedni? lini? w pliku git-migration/cvs.users w PLD CVS z: nick=nick na: nick=Full Name The encoding for the file is utf8. Dokonuj?c ten czyno?ci wyra?asz zgod? na u?ycie przez projekt PLD Twojego imienia i nazwiska w repozytoriach git jako autora zmian dokonanych przez Ciebie oraz do innych cel?w, kt?re wykorzystuj? dane z tych repozytori?w: np. listy zmian pokazywane przez 'rpm -q --changelog' By default old commits from CVS will be translated to git repositories with the following metadata: Author: nick Committer: cvs2git However if you prefer your full name to appear in Author: field for commits made by you, please change a proper line in file git-migration/cvs.users from: nick=nick to nick=Full Name Kodowanie pliku to utf8. By doing this you allow PLD project to show your full name as an author of your changes in git repositories and to other purposes that use data from these repositories. -- Kacper Kornet -- Kacper Kornet From draenog at pld-linux.org Fri Jun 22 21:47:08 2012 From: draenog at pld-linux.org (Kacper Kornet) Date: Fri, 22 Jun 2012 21:47:08 +0200 Subject: Git migration: ssh keys Message-ID: <20120622194708.GA1236@camk.edu.pl> (Polska wersja w drugiej cz??cie wiadomo?ci:) In git repositories authentication will be based on ssh keys. Therefore I would like to ask developers with RW access to CVS to upload their public ssh keys to SSH-keys directory in CVS. If you upload a new key, I would prefer if you put it in a file named according to one of the following patterns: cvs_login.pub cvs_login at string.pub where string should contains only characters from class a-zA-Z0-9_ Developers whose keys are already present there, please remove any of your keys to which private counterpart you have no longer access or you have any doubts about their security. In case of any doubts please remove your key. You don't have to rename your existing keys. Please refrain from modifying names of keys, that don't belong to you. Final notes: 1. One developer can have more then one keys 2. Only keys generated by openssh implementation are supported. Polish version: Uwierzytelnienie w repozytoriach git b?dzie oparte o klucze ssh. Dlatego prosi?bym wszystkie osoby z RW do CVS o wgranie swoich publicznych kluczy ssh do katalogu SSH-keys w CVS. Przy wgrywaniu nowych kluczy wola?bym ?e robiono to do plik?w o nazwach z jednej z dw?ch kategorii: cvs_login.pub cvs_login at string.pub gdzie string powinien zawiera? znaki tylko z zakres?w a-zA-Z0-9_ Osoby, kt?rych klucze s? ju? obecne w wy?ej wymienionym miejscu prosi?bym o sprawdzenie czy nadal maj? dost?p do odpowiednich prywatnych kluczy i czy s? one nadal bezpieczne w u?yciu. W przypadku wszelkich w?tpliwo?ci klucz nale?y usun??. Zmiana nazw plik?w z ju? istniej?cymi kluczami nie jest wymagana. W ?adnym wypadku nie nale?y zmienia? nazw plik?w z kluczami nie nale??cymi do siebie. Ko?cowe uwagi: 1. Jeden deweloper mo?e posiada? wi?cej ni? jeden klucz 2. Klucze wyprodukowane przez inne implementacje ni? openssh nie b?d? wspierane -- Kacper From draenog at pld-linux.org Sat Jun 23 00:28:36 2012 From: draenog at pld-linux.org (Kacper Kornet) Date: Sat, 23 Jun 2012 00:28:36 +0200 Subject: Git migration: ssh keys In-Reply-To: <20120622194708.GA1236@camk.edu.pl> References: <20120622194708.GA1236@camk.edu.pl> Message-ID: <20120622222836.GF3166@camk.edu.pl> I have forgotten about one think. Please make sure that one file with contains only one key. If you want to use few keys, you should keep them in separate files. Polish translation: Jeszcze jedna uwaga. Ka?dy plik powinien zawiera? dok?adnie jeden klucz. Je?eli kto? si? chce pos?ugiwa? kilkoma kluczami, to powinien je umie?ci? w kilku plikach. -- Kacper From baggins at pld-linux.org Mon Jun 25 18:52:32 2012 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Mon, 25 Jun 2012 18:52:32 +0200 Subject: Git migration: subdirs under packages/ In-Reply-To: <20120622194708.GA1236@camk.edu.pl> References: <20120622194708.GA1236@camk.edu.pl> Message-ID: <20120625165232.GA1651@home.lan> Small suggestion - add ability to slug.py to work with package(s) in a one level hash directories based on the first letter of package name, like this: packages/[0-9A-Za-z]/ Rationale: having entire packages checked out is RPITA, entering/listing packages/ directory is painfully slow - much slower than with CVS. One level hash will greatly speedup things. -- Jan R?korajski | PLD/Linux SysAdm | http://www.pld-linux.org/ bagginsmimuw.edu.pl bagginspld-linux.org From pluto at agmk.net Mon Jun 25 19:43:42 2012 From: pluto at agmk.net (=?utf-8?B?UGF3ZcWC?= Sikora) Date: Mon, 25 Jun 2012 19:43:42 +0200 Subject: Git migration: subdirs under packages/ In-Reply-To: <20120625165232.GA1651@home.lan> References: <20120622194708.GA1236@camk.edu.pl> <20120625165232.GA1651@home.lan> Message-ID: <2716744.rHOymkQChh@localhost> On Monday 25 of June 2012 18:52:32 Jan R?korajski wrote: > Small suggestion - add ability to slug.py to work with package(s) > in a one level hash directories based on the first letter > of package name, like this: > > packages/[0-9A-Za-z]/ > > Rationale: having entire packages checked out is RPITA, entering/listing > packages/ directory is painfully slow - much slower than with CVS. > One level hash will greatly speedup things. this is a bad workaround. the core problem is in glibc's readdir() which calls getdents syscall multiple times with small 32k buffer. e.g, for rpm/packages, `ls -1` produces: (...) getdents(3, /* 913 entries */, 32768) = 32760 getdents(3, /* 911 entries */, 32768) = 32744 getdents(3, /* 914 entries */, 32768) = 32736 getdents(3, /* 906 entries */, 32768) = 32760 getdents(3, /* 919 entries */, 32768) = 32752 getdents(3, /* 919 entries */, 32768) = 32768 getdents(3, /* 917 entries */, 32768) = 32744 getdents(3, /* 919 entries */, 32768) = 32744 getdents(3, /* 917 entries */, 32768) = 32744 getdents(3, /* 907 entries */, 32768) = 32728 getdents(3, /* 915 entries */, 32768) = 32736 getdents(3, /* 918 entries */, 32768) = 32752 getdents(3, /* 918 entries */, 32768) = 32744 getdents(3, /* 921 entries */, 32768) = 32752 getdents(3, /* 907 entries */, 32768) = 32752 getdents(3, /* 465 entries */, 32768) = 16784 getdents(3, /* 0 entries */, 32768) = 0 (...) From pluto at agmk.net Mon Jun 25 20:49:22 2012 From: pluto at agmk.net (=?utf-8?B?UGF3ZcWC?= Sikora) Date: Mon, 25 Jun 2012 20:49:22 +0200 Subject: Git migration: subdirs under packages/ In-Reply-To: <2716744.rHOymkQChh@localhost> References: <20120622194708.GA1236@camk.edu.pl> <20120625165232.GA1651@home.lan> <2716744.rHOymkQChh@localhost> Message-ID: <1387855.Ck7I9XRyG8@localhost> On Monday 25 of June 2012 19:43:42 Pawe? Sikora wrote: > On Monday 25 of June 2012 18:52:32 Jan R?korajski wrote: > > Small suggestion - add ability to slug.py to work with package(s) > > in a one level hash directories based on the first letter > > of package name, like this: > > > > packages/[0-9A-Za-z]/ > > > > Rationale: having entire packages checked out is RPITA, entering/listing > > packages/ directory is painfully slow - much slower than with CVS. > > One level hash will greatly speedup things. > > this is a bad workaround. the core problem is in glibc's readdir() > which calls getdents syscall multiple times with small 32k buffer. > e.g, for rpm/packages, `ls -1` produces: > > (...) > getdents(3, /* 913 entries */, 32768) = 32760 > getdents(3, /* 911 entries */, 32768) = 32744 > getdents(3, /* 914 entries */, 32768) = 32736 > getdents(3, /* 906 entries */, 32768) = 32760 > getdents(3, /* 919 entries */, 32768) = 32752 > getdents(3, /* 919 entries */, 32768) = 32768 > getdents(3, /* 917 entries */, 32768) = 32744 > getdents(3, /* 919 entries */, 32768) = 32744 > getdents(3, /* 917 entries */, 32768) = 32744 > getdents(3, /* 907 entries */, 32768) = 32728 > getdents(3, /* 915 entries */, 32768) = 32736 > getdents(3, /* 918 entries */, 32768) = 32752 > getdents(3, /* 918 entries */, 32768) = 32744 > getdents(3, /* 921 entries */, 32768) = 32752 > getdents(3, /* 907 entries */, 32768) = 32752 > getdents(3, /* 465 entries */, 32768) = 16784 > getdents(3, /* 0 entries */, 32768) = 0 > (...) ...and the major performance issue is the `mc` listing algorithm for custom view with the 'size' column. it finally calls the lstat() for each entry (~15k times). From draenog at pld-linux.org Tue Jun 26 11:00:02 2012 From: draenog at pld-linux.org (Kacper Kornet) Date: Tue, 26 Jun 2012 11:00:02 +0200 Subject: Git migration: Change in auto-* tags Message-ID: <20120626090002.GA10073@camk.edu.pl> There are two suggestions about auto-tags- 1. Move auto- tags to dir like substructure. So the tag auto-th-gcc-4_3_2-4 would be renamed auto/th/gcc-4_3_2-4 2. Drop the replacement '.@ -> '_#' during generation of auto tags. This one would go for only new tags. Any objections, comments? Polish version: Dwie propozycje tag?w auto-* 1. Zmieni? ich struktur? na podobn? do katalog?w. Tzn. tag auto-th-gcc-4_3_2-4 sta?by si? auto/th/gcc-4_3_2-4. Troszeczk? by to u?atwi?o skryptologi? w przysz?o?ci 2. Porzuci? zast?powanie znak?w '.@' -> '_#' w auto tagach generowanych po konwersji do git. Stare by zosta?y bez zmian pod tym wzgl?dem. Sprzeciwy, komentarze? -- Kacper From adamg at pld-linux.org Tue Jun 26 14:15:11 2012 From: adamg at pld-linux.org (Adam Golebiowski) Date: Tue, 26 Jun 2012 14:15:11 +0200 Subject: [administrativia] shadzik's unsubscription Message-ID: <20120626121511.GA13671@adamg.eu> Dear all, Respecting cdg's decission I have removed Bartosz from the following lists: - pld-devel-en - pld-devel-pl - pld-discuss adamg PS: IIRC for almost 15 years we survived without having to ban anyone. It's a shame we had to break this rule. From jajcus at jajcus.net Thu Jun 28 09:43:17 2012 From: jajcus at jajcus.net (Jacek Konieczny) Date: Thu, 28 Jun 2012 09:43:17 +0200 Subject: packages: git-core-slug/git-core-slug.spec - don't pack Attic; its location... In-Reply-To: References:

Message-ID: <20120628074317.GA26969@jajo.eggsoft> On Thu, Jun 28, 2012 at 03:36:56AM +0200, draenog wrote: > ---- Files affected: > packages/git-core-slug: > git-core-slug.spec (1.18 -> 1.19) Why is this package called 'git-core-slug'? It is not in any way part of the GIT core, is it? Wouldn't 'git-slug' or just 'slug' or 'pld-slug' be better? Greets, Jacek From kornet at camk.edu.pl Thu Jun 28 09:55:31 2012 From: kornet at camk.edu.pl (Kacper Kornet) Date: Thu, 28 Jun 2012 09:55:31 +0200 Subject: packages: git-core-slug/git-core-slug.spec - don't pack Attic; its location... In-Reply-To: <20120628074317.GA26969@jajo.eggsoft> References:

<20120628074317.GA26969@jajo.eggsoft> Message-ID: <20120628075531.GA16077@camk.edu.pl> On Thu, Jun 28, 2012 at 09:43:17AM +0200, Jacek Konieczny wrote: > On Thu, Jun 28, 2012 at 03:36:56AM +0200, draenog wrote: > > ---- Files affected: > > packages/git-core-slug: > > git-core-slug.spec (1.18 -> 1.19) > Why is this package called 'git-core-slug'? It is not in any way part of > the GIT core, is it? Wouldn't 'git-slug' or just 'slug' or 'pld-slug' be > better? Someone on IRC suggested that name. I think it was a compromise between slug, and git-core-pld. The connection with git is that instead of calling command slug.py , you can use 'git pld '. -- Kacper From jajcus at jajcus.net Thu Jun 28 10:04:39 2012 From: jajcus at jajcus.net (Jacek Konieczny) Date: Thu, 28 Jun 2012 10:04:39 +0200 Subject: packages: git-core-slug/git-core-slug.spec - don't pack Attic; its location... In-Reply-To: <20120628075531.GA16077@camk.edu.pl> References:

<20120628074317.GA26969@jajo.eggsoft> <20120628075531.GA16077@camk.edu.pl> Message-ID: <20120628080439.GB26969@jajo.eggsoft> On Thu, Jun 28, 2012 at 09:55:31AM +0200, Kacper Kornet wrote: > Someone on IRC suggested that name. I think it was a compromise between > slug, and git-core-pld. The connection with git is that instead of > calling command slug.py , you can use 'git pld > '. But still, a plugin to git is not a part of the git core IMHO. Greets, Jacek From kornet at camk.edu.pl Thu Jun 28 10:16:39 2012 From: kornet at camk.edu.pl (Kacper Kornet) Date: Thu, 28 Jun 2012 10:16:39 +0200 Subject: packages: git-core-slug/git-core-slug.spec - don't pack Attic; its location... In-Reply-To: <20120628080439.GB26969@jajo.eggsoft> References:

<20120628074317.GA26969@jajo.eggsoft> <20120628075531.GA16077@camk.edu.pl> <20120628080439.GB26969@jajo.eggsoft> Message-ID: <20120628081639.GB16077@camk.edu.pl> On Thu, Jun 28, 2012 at 10:04:39AM +0200, Jacek Konieczny wrote: > On Thu, Jun 28, 2012 at 09:55:31AM +0200, Kacper Kornet wrote: > > Someone on IRC suggested that name. I think it was a compromise between > > slug, and git-core-pld. The connection with git is that instead of > > calling command slug.py , you can use 'git pld > > '. > But still, a plugin to git is not a part of the git core IMHO. On the other hand git-slug would suggest that it is a plugin to "A set of GNU Interactive Tools" ;-). But I wouldn't resit strongly if you want to change the name of the package. -- Kacper From pluto at agmk.net Fri Jun 29 20:54:20 2012 From: pluto at agmk.net (=?utf-8?B?UGF3ZcWC?= Sikora) Date: Fri, 29 Jun 2012 20:54:20 +0200 Subject: Git migration: ssh keys In-Reply-To: <20120622194708.GA1236@camk.edu.pl> References: <20120622194708.GA1236@camk.edu.pl> Message-ID: <2338308.Av8pGPc0lC@localhost> On Friday 22 of June 2012 21:47:08 Kacper Kornet wrote: > (Polska wersja w drugiej cz??cie wiadomo?ci:) > > In git repositories authentication will be based on ssh keys. Therefore I > would like to ask developers with RW access to CVS to upload their public ssh > keys to SSH-keys directory in CVS. how long do you plan to keep this ssh-keys-upload window open? From draenog at pld-linux.org Fri Jun 29 21:53:10 2012 From: draenog at pld-linux.org (Kacper Kornet) Date: Fri, 29 Jun 2012 21:53:10 +0200 Subject: Git migration: ssh keys In-Reply-To: <2338308.Av8pGPc0lC@localhost> References: <20120622194708.GA1236@camk.edu.pl> <2338308.Av8pGPc0lC@localhost> Message-ID: <20120629195310.GA9403@camk.edu.pl> On Fri, Jun 29, 2012 at 08:54:20PM +0200, Pawe? Sikora wrote: > On Friday 22 of June 2012 21:47:08 Kacper Kornet wrote: > > (Polska wersja w drugiej cz??cie wiadomo?ci:) > > In git repositories authentication will be based on ssh keys. Therefore I > > would like to ask developers with RW access to CVS to upload their public ssh > > keys to SSH-keys directory in CVS. > how long do you plan to keep this ssh-keys-upload window open? I don't know. Probably till official date of migration. By the way, keys which were upload before yesterday are already in git.pld-linux.org so most active developers should have an access. Beware that it is still a beta version. What I mean that whatever changes you will made there, can be destroyed without any warning. -- Kacper