[pacman-dev] Package pacman.

7 Sep 2010

      Good Morning.

The package 'pacman-3.4.1-1', is bug. For update any package, is needed do
pacman -Sf.

Thank you, sorry my english,

-- 
-   °v°  Albino Biasutti Neto | Bino aka bino28
-  /(_)\  GNU-Linux - Livre, Poderoso e Seguro
-  ^ ^  Linux User #511213
- Archlinux-br user - http://www.archlinux-br.org
- Debian Brasil Member
- KDE Brasil Member
- GUBrO-ES - Grupo de Usuários de BrOffice.org do ES
- Tux-ES member - www.tux-es.org
- http://www.binoinformatica.com /blog

On Mon, Sep 6, 2010 at 12:46 PM,  wrote:
...
Send pacman-dev mailing list submissions to
       pacman-dev@archlinux.org
To subscribe or unsubscribe via the World Wide Web, visit
       http://mailman.archlinux.org/mailman/listinfo/pacman-dev
or, via email, send a message with subject or body 'help' to
       pacman-dev-request@archlinux.org
You can reach the person managing the list at
       pacman-dev-owner@archlinux.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of pacman-dev digest..."
Today's Topics:
1. Re: [PATCH 2/3] Use OpenSSL MD5 crypto functions  if available
     (Allan McRae)
  2. Re: [PATCH 2/3] Use OpenSSL MD5 crypto functions if       available
     (Dan McGee)
  3. Re: [PATCH 2/3] Use OpenSSL MD5 crypto functions if available
     (Allan McRae)
----------------------------------------------------------------------
Message: 1
Date: Tue, 07 Sep 2010 01:04:48 +1000
From: Allan McRae 
Subject: Re: [pacman-dev] [PATCH 2/3] Use OpenSSL MD5 crypto functions
       if available
To: Bryce Gibson ,      Discussion list
       for pacman development 
Message-ID: <4C850310.3080304@archlinux.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 07/09/10 00:25, Bryce Gibson wrote:
...
----- Original message -----
...
On 04/09/10 19:16, J?rgen H?tzel wrote:
...
Hi Dan,
2010/9/2 Dan McGee:
...
This does not remove the MD5 code from our codebase, but it does
enable linking against OpenSSL to get their much faster
implementation if it is available on whatever platform you are
using. At configure-time, we will default to using it if it is
available, but this can be easily changed by using the
`--with-openssl` or `--without-openssl` arguments to configure.
What about just replacing the current MD5 implementation with the
OpenSSL implementation?
This would prevent conditional compilation and a direct OpenSSL
dependency in libalpm.
Can we do that?   Openssl is BSD code.
Anyway, I have concerns...     Think of an openssl upgrade.   pacman is
in
...
...
SyncFirst and it pulls in all its deps.   If that pulls in openssl with
a
soname bump, things may get interesting.   I have not check, but I do
not
think --as-needed saves us there.
Allan
The licenses that openssl is released under aren't compatible with the
gpl (according to the fsf) because of the advertising clause... So openssl
code can't really be used like that... (Unfortunately)
How does the coreutils md5sum speed compare?  That is GPL code so could
be included directly.  Though I guess it is now GPL3 being a GNU project...
Allan
------------------------------
Message: 2
Date: Mon, 6 Sep 2010 10:15:46 -0500
From: Dan McGee 
Subject: Re: [pacman-dev] [PATCH 2/3] Use OpenSSL MD5 crypto functions
       if      available
To: Discussion list for pacman development 
Message-ID:

...
Content-Type: text/plain; charset="utf-8"
On Mon, Sep 6, 2010 at 10:04 AM, Allan McRae  wrote:
...
On 07/09/10 00:25, Bryce Gibson wrote:
...
----- Original message -----
...
On 04/09/10 19:16, J?rgen H?tzel wrote:
...
Hi Dan,
2010/9/2 Dan McGee:
...
This does not remove the MD5 code from our codebase, but it does
enable linking against OpenSSL to get their much faster
implementation if it is available on whatever platform you are
using. At configure-time, we will default to using it if it is
available, but this can be easily changed by using the
`--with-openssl` or `--without-openssl` arguments to configure.
What about just replacing the current MD5 implementation with the
OpenSSL implementation?
This would prevent conditional compilation and a direct OpenSSL
dependency in libalpm.
Can we do that? ? Openssl is BSD code.
Anyway, I have concerns... ? ? Think of an openssl upgrade. ? pacman is
in
SyncFirst and it pulls in all its deps. ? If that pulls in openssl with
a
...
...
soname bump, things may get interesting. ? I have not check, but I do
not
think --as-needed saves us there.
Allan
The licenses that openssl is released under aren't compatible with the
gpl
(according to the fsf) because of the advertising clause... So openssl
code
can't really be used like that... (Unfortunately)
How does the coreutils md5sum speed compare? ?That is GPL code so could
be
included directly. ?Though I guess it is now GPL3 being a GNU project...
Quite a bit slower. Test results (for one platform, please test on
whatever you are running on, it is very machine-dependent) and the
test harness included below, run using ./md5-speed.sh <bigfile>
Keep in mind that "including directly" more than likely is a drawback.
I wouldn't be surprised if there are assembly routines involved in
both of these codebases which just makes the build process that much
more involved and we have to work it into our code. Not that I think
these routines change much upstream, but it is one more thing to keep
up to date.
-Dan
dmcgee@dublin /tmp
$ ./md5-speed.sh ~/downloads/Fireworks.amb
path: /home/dmcgee/downloads/Fireworks.amb
md5(/home/dmcgee/downloads/Fireworks.amb) =
987fef0281e0924977fc8d14f78f4cd4
Version: i686
real    0m9.019s
user    0m7.623s
sys     0m1.143s
path: /home/dmcgee/downloads/Fireworks.amb
md5(/home/dmcgee/downloads/Fireworks.amb) =
987fef0281e0924977fc8d14f78f4cd4
Version: atom
real    0m9.082s
user    0m7.736s
sys     0m1.120s
path: /home/dmcgee/downloads/Fireworks.amb
md5(/home/dmcgee/downloads/Fireworks.amb) =
987fef0281e0924977fc8d14f78f4cd4
Version: native
real    0m9.078s
user    0m7.739s
sys     0m1.103s
987fef0281e0924977fc8d14f78f4cd4  /home/dmcgee/downloads/Fireworks.amb
Program: md5sum
real    0m8.034s
user    0m6.963s
sys     0m0.870s
MD5(/home/dmcgee/downloads/Fireworks.amb)= 987fef0281e0924977fc8d14f78f4cd4
Program: openssl dgst -md5
real    0m6.511s
user    0m5.356s
sys     0m0.980s