Re: kismet-c++.patch (NONE - 1.1) (NEW)
Author: arekmDate: Sun Jun 24 11:47:23 2007 GMT
Module: SOURCES Tag: HEAD
Log message:
- new
Files affected:
SOURCES:
kismet-c++.patch (NONE - 1.1) (NEW)
+ for (int t = 0; t numthreads; t++) {
+ void *tmp;
+ pthread_join(mapthread[t], tmp);
+-thread_status = reinterpret_castint(tmp);
++thread_status = reinterpret_castlong(tmp);
+ }
czy aby nie przypadkiem status watku, to wartosc zwrocona przez join() ?
0 == ok, albo -Ecostam
--
MIT is like the Paris Hilton of technology universities.
Every guy knows about it and want's to get inside.
___
pld-devel-pl mailing list
pld-devel-pl@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-pl
geninitrd a raid5
Hello. Nasz geninitrd wymieka gdy root jest na programowym raid5. Stwierdza, ze nie ma modulu raid5. I slusznie, bo nie ma takiego, to jest tylko alias do modulu raid456. Majac taki system mozna latwo wyedytowac geninitrd zeby sobie poradzil, ale przydalo by sie jakies koszerne rozwiazanie, ktore bedzie dzialalo zarowno ze starszymi kernelami (modul raid5) jak i nowszymi (modul raid456 i alias raid5). Ma ktos pomysl na taka poprawke? M. ___ pld-devel-pl mailing list pld-devel-pl@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-pl
Re: SPECS: mldonkey.spec - BR: gd-devel libmagic-devel libpng-devel
On Tue, Jun 19, 2007 at 10:04:25PM +0200, qboosh wrote:
Author: qboosh Date: Tue Jun 19 20:04:25 2007 GMT
Module: SPECS Tag: HEAD
Log message:
- BR: gd-devel libmagic-devel libpng-devel
Files affected:
SPECS:
mldonkey.spec (1.169 - 1.170)
Diffs:
Index: SPECS/mldonkey.spec
diff -u SPECS/mldonkey.spec:1.169 SPECS/mldonkey.spec:1.170
--- SPECS/mldonkey.spec:1.169 Sun Jun 17 01:43:18 2007
+++ SPECS/mldonkey.spec Tue Jun 19 22:04:20 2007
@@ -38,14 +38,16 @@
BuildRequires: autoconf
BuildRequires: automake
BuildRequires: bzip2-devel
-%{?with_gui:BuildRequires: gd-devel}
+BuildRequires: gd-devel = 2.0.14
%{?with_gui:BuildRequires: gtk+2-devel = 2:2.4.0}
+BuildRequires: libmagic-devel
+BuildRequires: libpng-devel
+%{?with_gui:BuildRequires: librsvg-devel = 2.0}
BuildRequires: libstdc++-devel
BuildRequires: ncurses-devel
BuildRequires: ocaml-camlp4 = 1:%{ocaml_ver}
%{?with_gui:BuildRequires: ocaml-lablgtk2-devel = 2.6.0}
%{?with_gui:BuildRequires: ocaml-lablgtk2-rsvg-devel = 2.6.0}
-%{?with_gui:BuildRequires: librsvg-devel = 2.0}
BuildRequires: cpp
BuildRequires: perl-base
%{?with_gui:BuildRequires: pkgconfig}
Nasuwa mi się takie pytanie: czy ocaml-lablgtk2-rsvg-devel nie powinien mieć
Req: librsvg-devel?
--
Szymon Siwek
Los nikomu nie szczędzi rozczarowań
___
pld-devel-pl mailing list
pld-devel-pl@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-pl
Re: SPECS: cryptsetup-luks.spec - up to 1.0.5
On Fri, Jun 22, 2007 at 07:55:59PM +0200, prism wrote:
Author: prismDate: Fri Jun 22 17:55:59 2007 GMT
Module: SPECS Tag: HEAD
Log message:
- up to 1.0.5
Files affected:
SPECS:
cryptsetup-luks.spec (1.18 - 1.19)
Diffs:
Index: SPECS/cryptsetup-luks.spec
diff -u SPECS/cryptsetup-luks.spec:1.18 SPECS/cryptsetup-luks.spec:1.19
--- SPECS/cryptsetup-luks.spec:1.18 Thu May 24 23:00:19 2007
+++ SPECS/cryptsetup-luks.specFri Jun 22 19:55:54 2007
@@ -3,15 +3,16 @@
# Conditonal build:
%bcond_with static # link cryptsetup statically
#
+%define _realname cryptsetup
Summary: LUKS for dm-crypt implemented in cryptsetup
Summary(pl.UTF-8): LUKS dla dm-crypta zaimplementowany w cryptsetup
Name:cryptsetup-luks
-Version: 1.0.4
+Version: 1.0.5
Release: 1
License: GPL
Group: Base
-Source0: http://luks.endorphin.org/source/%{name}-%{version}.tar.bz2
-# Source0-md5: 156ae6b618438ee9feeddc6c2bdc4e94
+Source0: http://luks.endorphin.org/source/%{_realname}-%{version}.tar.bz2
+# Source0-md5: 0aa2f94c39123f1a0352983e5366179c
Patch1: %{name}-nostatic.patch
URL: http://luks.endorphin.org/about
BuildRequires: autoconf
@@ -91,7 +92,7 @@
Statyczna wersja biblioteki cryptsetup.
%prep
-%setup -q
+%setup -q -n %{_realname}-%{version}
%patch1 -p1
%build
@@ -116,7 +117,7 @@
ln -sf /%{_lib}/$(cd $RPM_BUILD_ROOT/%{_lib}; echo libcryptsetup.so.*.*.*) \
$RPM_BUILD_ROOT%{_libdir}/libcryptsetup.so
-%find_lang %{name}
+%find_lang %{_realname}
%clean
rm -rf $RPM_BUILD_ROOT
@@ -124,7 +125,7 @@
%post-p /sbin/ldconfig
%postun -p /sbin/ldconfig
-%files -f %{name}.lang
+%files -f %{_realname}.lang
%defattr(644,root,root,755)
%doc ChangeLog
%attr(755,root,root) %{_sbindir}/cryptsetup
Odnoszę wrażenie, że w tej chwili istnieje tylko jeden cryptsetup, tzn.
należałoby przerzucić zawartość cryptsetup-luks.spec do cryptsetup.spec,
plus odpowiednie poprawki w pakietach zależnych (? util-linux{,-ng}).
Kto za? kto przeciw? kto się wstrzymuje?
--
Szymon Siwek
Los nikomu nie szczędzi rozczarowań
___
pld-devel-pl mailing list
pld-devel-pl@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-pl
