Bug 1672 - Postfix post script create-ssl-certificate miss required openssl deps
Summary: Postfix post script create-ssl-certificate miss required openssl deps
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Daniel Lucio
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-06-07 17:25 CEST by Raphael Gertz
Modified: 2012-08-18 12:32 CEST (History)
3 users (show)

See Also:
Source RPM: postfix-2.7.4-1.mga1.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Raphael Gertz 2011-06-07 17:25:57 CEST 
Description of problem:
Postfix /usr/share/rpm-helper/create-ssl-certificate script line 62 need openssl.

14/71: postfix ##################################################################
/usr/share/rpm-helper/create-ssl-certificate: line 62: openssl: command not found
chmod: cannot access `/etc/pki/tls/private/postfix.pem': No such file or directory

Version-Release number of selected component (if applicable):
postfix-2.7.4-1.mga1

How reproducible:
When installing through chroot

Steps to Reproduce:
1. export ARCH=x86_64
2. LC_ALL=C urpmi --downloader=wget --no-verify-rpm --no-suggests --noclean --auto --allow-force --root=$PWD/$ARCH bash-completion acpi acpid bind bind-utils nail postfix lftp info man man-pages shorewall lsof mlocate lynx nano openssh-server patch procmail traceroute whois xauth reiserfsprogs sudo tree screen unzip unrar p7zip rsync openntpd mdadm
Comment 1 Samuel Verschelde 2011-10-01 03:34:53 CEST 
Assigning to maintainer now that our maintainers database has an entry for
this package. Please assign back to bugsquad@mageia.org in case of a mistake
from me.

CC: (none) => remco, stormi
Assignee: bugsquad => dlucio

Comment 2 Samuel Verschelde 2011-10-01 03:35:29 CEST 
If valid in Mageia, an update will be necessary I guess.
Comment 3 Marja Van Waes 2012-01-06 19:49:34 CET 
pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED


@ Daniel

Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.

@ Raphael

Is this bug still valid?

CC: (none) => marja11

Comment 4 Marja Van Waes 2012-04-21 20:40:45 CEST 
3 monthly ping
Comment 5 Marja Van Waes 2012-05-26 13:04:42 CEST 
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 6 Marja Van Waes 2012-07-06 15:05:42 CEST 
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 7 Marja Van Waes 2012-08-18 12:32:33 CEST 
4 pings, no reply

closing as old.

Please reopen when needed and tell for which version(s) of Mageia and postfix this bug is still valid.

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.