Re: packages: util-vserver/util-vserver.spec, util-vserver/TODO (NEW) - move TO...

2009-05-13 Thread Elan Ruusamäe
On Wednesday 13 May 2009 13:44:38 blues wrote:
  $Log$
 +Revision 1.225  2009/05/13 10:44:33  blues
 +- move TODO to separate file

why? i liked the otherwise

it's
1. in spec file, always around when you edit the file
3. nobody really goes to see what is in TODO, maybe i'm bored and i fix 
something.
2. PLD-doc/make-todo.sh scanned SPECS for TODO sections
4. if there are lots of SOURCES in package (like php for example), catching 
eye on TODO in `ls` is unlikely.

-- 
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: packages: util-vserver/util-vserver.spec, util-vserver/TODO (NEW) - move TO...

2009-05-13 Thread Pawel Golaszewski
On Wed, 13 May 2009, Elan Ruusamäe wrote:
 On Wednesday 13 May 2009 13:44:38 blues wrote:
   $Log$
  +Revision 1.225  2009/05/13 10:44:33  blues
  +- move TODO to separate file
 why? i liked the otherwise
 
 it's
 1. in spec file, always around when you edit the file
 3. nobody really goes to see what is in TODO, maybe i'm bored and i fix 
 something.
 2. PLD-doc/make-todo.sh scanned SPECS for TODO sections
 4. if there are lots of SOURCES in package (like php for example), catching 
 eye on TODO in `ls` is unlikely.

Because:
- it makes only noise in spec
- nobody goes to see TODO in spec too :)
- it's clean and nice
- TODO can be not only for SPEC
- TODO can be vry long...
- you don't have to catch anything - you know it's there, like spec :D

I think it's better way, easier to parse.

-- 
pozdr.  Paweł Gołaszewski  jid:bluesatjabberdotgdadotpl
--
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.___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Fwd: packages (rpm-4_5): rpm/rpm-shescape-memfault.patch (NEW) - doing xrealloc ...

2009-05-13 Thread Elan Ruusamäe
 ___
 pld-cvs-commit mailing list
 pld-cvs-com...@lists.pld-linux.org
 http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit

why there are no more cvsweb links at the end of commit mails?

-- 
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


verify rpm package contents

2009-05-13 Thread Tomasz Pala
How to verify digest of files in rpm package (like when repackaged
modified files)? For example I've got:

~: rpm -qplv xorg-proto-xproto-devel-7.0.14-1.i586.rpm
-rw-r--r--1 rootroot   167477 Oct 28  2008 
/usr/include/X11/keysymdef.h
but after un-cpio there is:167401 May 22  2008

rpm --verify -p file.rpm

verifies against filesystem contents not files within.

-- 
Tomasz Pala go...@pld-linux.org
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: verify rpm package contents

2009-05-13 Thread Jeff Johnson

On May 13, 2009, at 1:41 PM, Tomasz Pala wrote:

 How to verify digest of files in rpm package (like when repackaged
 modified files)? For example I've got:

 ~: rpm -qplv xorg-proto-xproto-devel-7.0.14-1.i586.rpm
 -rw-r--r--1 rootroot   167477 Oct 28  2008 /usr/ 
 include/X11/keysymdef.h
 but after un-cpio there is:167401 May 22  2008

 rpm --verify -p file.rpm

 verifies against filesystem contents not files within.


Repackaged files have no digest verification. The digest
carried in repackaged packages is the original digest;
but the file in the payload may have been modified or
even deleted and not present in te repackaged package payload.

You can work around by using a transaction probe dependency.

E.g.

 mkdir -p /etc/rpm/sysinfo
 md5sum /etc/passwd | sed -e 's/\([^ ]*\) *\(.*\)/digest(\2) =  
\1/'  /etc/rpm/sysinfo/Requirename

verifies the md5 of /etc/passwd every time rpm -Uvh is run.

hth

73 de Jeff
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: packages: util-vserver/util-vserver.spec, util-vserver/TODO (NEW) - move TO...

2009-05-13 Thread wrobell
On Wed, May 13, 2009 at 01:53:38PM +0200, Pawel Golaszewski wrote:
 On Wed, 13 May 2009, Elan Ruusamäe wrote:
  On Wednesday 13 May 2009 13:44:38 blues wrote:
$Log$
   +Revision 1.225  2009/05/13 10:44:33  blues
   +- move TODO to separate file
  why? i liked the otherwise
  
  it's
  1. in spec file, always around when you edit the file
  3. nobody really goes to see what is in TODO, maybe i'm bored and i fix 
  something.
  2. PLD-doc/make-todo.sh scanned SPECS for TODO sections
  4. if there are lots of SOURCES in package (like php for example), catching 
  eye on TODO in `ls` is unlikely.
 
 Because:
 - it makes only noise in spec

not true, because they are usually short

 - nobody goes to see TODO in spec too :)

it is easy to spot todo in spec, imho

 - it's clean and nice
 - TODO can be not only for SPEC

so what? it is about the package not spec

 - TODO can be vry long...

any examples... even if there is one or two, then usually they are short if
i reckon well

wrobell wrob...@pld-linux.org
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en