Bug#322348: /etc/init.d/apache script wasn't removed by postrm

2005-11-01 Thread A. Costa
On Fri, 28 Oct 2005 18:59:12 +1000
Adam Conrad [EMAIL PROTECTED] wrote:

  Seconded.  It's not installed on my system:
  
  % dlocate -s apache | grep Status
  Status: deinstall ok config-files
 
 Uhh, sure it's installed.  Note the config-files state.  You removed
 the package, but didn't purge it.  (dpkg --purge apache, or purge it
 in whatever package frontend you use)

According to this definition you're right:

not-installed

No files are installed from the package, it has no config 
files left, it uninstalled cleanly if it ever was installed.

-- dpkg technical manual 
   1.2 The dpkg status area
   /usr/share/doc/libapt-pkg-doc/dpkg-tech.html/ch1.html#s1.2

It logically follows that the opposite of not-installed, where NO
files from the package are present, would be all or some files, even
just one.

Yet given the next definition (from the same source)
I'd be correct:

installed

All files for the package are installed, and the 
configuration was also successful.

It logically follows from the quantifier 'ALL' that just one file
missing would mean the package was not installed, just as 51 cards make
an incomplete deck.  

Seems like the above definitions of 'installed' and 'not-installed'
are merely _contrary_, and fail to conform to the common usage of the
prefix not- as a _contradictory_.

Note that my apache 'Status' field quoted above uses the term
'deinstall', which the 'dpkg technical manual' alludes to once,
but does not define.  Here's a definition:

% man dpkg | grep -A 2 -n deinstall | head -n 3
75:   deinstall
76:  The  package  is  selected  for  deinstallation (i.e. 
we want to
77-  remove all files, except configuration files).

By that usage we were both being vague -- the package wasn't
'installed', (since all files weren't there), and it wasn't
'not-installed', (since some were), it was 'deinstalled'.

Unfortunately the prefix de- in this context has the common usage
of reversing or undoing, which in this context is virtually what
the common usage of not- means.  Oy vey.

Aside from that...

Perhaps you were implying that I ought to have purged 'apache'
-- I usually don't use 'purge', as old config files sometimes have
system specific information that comes in handy.

Lastly, for anyone reading this who knows, a question:

Does the Debian distro's definition of a config file include 
executables?

(My definition would be restricted to inert data, and never code; so
'/etc/fstab' would be a 'config file', but any setup or maintenance
program, such as '/etc/init.d/apache', would not be.)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#322348: /etc/init.d/apache script wasn't removed by postrm

2005-11-01 Thread Pawel Wiecek
On Nov 1,  3:08am, A. Costa wrote:
 Lastly, for anyone reading this who knows, a question:
 
   Does the Debian distro's definition of a config file include 
 executables?

Debian definition of config file expressly includes everything in /etc. And
yes, startup script is definitely a config file, since system-specific
configuration can be set there.

Pawel

-- 
 (___)  | Pawel Wiecek -- Coven / Svart -- http://www.coven.vmh.net/ |
 o o  |  [EMAIL PROTECTED]GPG/PGP info in headers GSM: +48603240006 
 |
 \ ^ /  | *  *  As the people here grow colder I turn to my computer*  * |
  ()   | *  *  And spend my evenings with it Like a friend -- Kate Bush |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#322348: /etc/init.d/apache script wasn't removed by postrm

2005-11-01 Thread Adam Conrad
A. Costa wrote:
 
Seconded.  It's not installed on my system:

% dlocate -s apache | grep Status
Status: deinstall ok config-files
 [ much confusion about status lines ]

I think you're confusing the first and last columns.  That installed |
not-installed stuff goes in the third column, which is the state
column.  In your case, the state is config-files, which is basically
halfway in between installed and not-installed.

The first column is the selection state (what would get set by dselect,
for instance), which is more a statement of what you've TOLD the package
system to do, not necessarily what it has done.  That one can be
install, deinstall, or purge, IIRC.

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#336651: libapr0: Need to compile --with-devrandom=/dev/urandom

2005-11-01 Thread Mark A. Hershberger

Steve Langasek wrote:

 It is quite likely that it is not a bug at all -- /dev/urandom is *not* a

proper replacement for /dev/random when real entropy is needed, and the

 Debian packages should not sacrifice security casually.

svnadmin create repos and other svn commands that need UUIDs don't 
work entropy isn't available.  They hang.


Thus, you've created a security problem (denial of service) by making 
policy decisions that should be left for the site to make (e.g. what 
quality of randomness do we need from apr?)


--
http://mah.everybody.org/weblog/
GPG Fingerprint: 7E15 362D A32C DFAB E4D2  B37A 735E F10A 2DFC BFF5

Someone will always sell you for 30 pieces of silver.
 -- Andrei Rublev


signature.asc
Description: OpenPGP digital signature