| Summary: | Missing perl dependencies for postgrey | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marc Krämer <mageia> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | herman.viaene, lewyssmith, lists.jjorge, mageia, marja11, sysadmin-bugs, tmb |
| Version: | 6 | Keywords: | advisory, validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA6-32-OK MGA6-64-OK | ||
| Source RPM: | postgrey-1.37-1.mga6.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: | New Spec file for missing deps | ||
|
Description
Marc Krämer
2017-07-28 13:59:59 CEST
Rémi Verschelde
2017-07-28 14:28:05 CEST
Summary:
dependency mismatch =>
Missing perl dependencies for postgrey still valid. Created attachment 9764 [details]
New Spec file for missing deps
This should be bakcported to mga6!
new version in testing for mga6 Status:
NEW =>
RESOLVED Yuor mentor should have told you how to handle updates to stable releases... this is not done yet... CC:
(none) =>
tmb (In reply to Thomas Backlund from comment #4) > Yuor mentor should have told you how to handle updates to stable releases... > this is not done yet... Indeed, it still needs to be tested and validated by QA team Instead, please add an advisory, see the example here: https://wiki.mageia.org/en/Update_Advisory_Announcement_Example (don't forget the list of packages that are generated from postgrey-1.37-1.1.mga6.srpm) CC'ing M K and zézinho CC:
(none) =>
lists.jjorge, mageia, marja11 I have uploaded an updated package for postgrey It fixes missing dependencies for postgrey. Suggested advisory: ======================== Postgrey before this update could only be used after manually installing perl-Net* and perl-BerkeleyDB this update fixes the package dependencies. Updated packages in core/updates_testing: ======================== postgrey-1.37-3.mga7.noarch.rpm Source RPMs: postgrey-1.37-3.mga7.src.rpm (In reply to M K from comment #6) > I have uploaded an updated package for postgrey > It fixes missing dependencies for postgrey. > > Suggested advisory: > ======================== > Postgrey before this update could only be used after manually installing > perl-Net* and perl-BerkeleyDB this update fixes the package dependencies. > > Updated packages in core/updates_testing: > ======================== > postgrey-1.37-3.mga7.noarch.rpm > > Source RPMs: > postgrey-1.37-3.mga7.src.rpm Please don't get discouraged, Marc, but that's the cauldron version ;-) I have uploaded an updated package for postgrey It fixes missing dependencies for postgrey. Suggested advisory: ======================== Postgrey before this update could only be used after manually installing perl-Net* and perl-BerkeleyDB this update fixes the package dependencies. Updated packages in core/updates_testing: ======================== postgrey-1.37-1.1.mga6.noarch.rpm Source RPMs: postgrey-1.37-1.1.mga6.src.rpm MGA6-32 on Asus A6000VM MATE No installation issues. Found some guidance in https://www.howtoforge.com/greylisting_postfix_postgrey, but this is obsolete or the Mageia implementation is slightly different: postgrey configuration file is to be found in /etc/sysconfig, not /etc/default At CLI: # systemctl start postgrey [root@mach6 ~]# systemctl -l status postgrey ● postgrey.service - Postfix Greylisting Service Loaded: loaded (/usr/lib/systemd/system/postgrey.service; enabled; vendor preset: enabled) Active: active (running) since wo 2017-11-15 10:00:16 CET; 3s ago Process: 24332 ExecStart=/usr/sbin/postgrey --pidfile=/run/postgrey.pid --daemonize $SOCKET $OPTIONS (code Process: 24330 ExecStartPre=/bin/rm -f /run/postgrey.pid (code=exited, status=0/SUCCESS) Main PID: 24336 (postgrey --pidf) CGroup: /system.slice/postgrey.service └─24336 postgrey --pidfile=/run/postgrey.pid --daemonize --unix=/var/spool/postfix/extern/postgre nov 15 10:00:14 mach6.hviaene.thuis systemd[1]: Starting Postfix Greylisting Service... nov 15 10:00:16 mach6.hviaene.thuis postgrey[24336]: Process Backgrounded nov 15 10:00:16 mach6.hviaene.thuis postgrey[24336]: 2017/11/15-10:00:16 postgrey (type Net::Server::Multipl nov 15 10:00:16 mach6.hviaene.thuis systemd[1]: Started Postfix Greylisting Service. nov 15 10:00:16 mach6.hviaene.thuis postgrey[24336]: Binding to UNIX socket file "/var/spool/postfix/extern/ nov 15 10:00:16 mach6.hviaene.thuis postgrey[24336]: Setting gid to "954 954" nov 15 10:00:16 mach6.hviaene.thuis postgrey[24336]: Setting uid to "957" As I do not operate postfix, to me it seems OK. Whiteboard:
(none) =>
MGA6-32-OK Probing M6/64 theoretically BEFORE upodate: $ urpmq -i postgrey Version : 1.37 Release : 1.mga6 Source RPM : postgrey-1.37-1.mga6.src.rpm $ urpmq -d postgrey | grep ^perl perl-DB_File|perl perl-File-Sync perl-MDK-Common perl-Sys-Syslog|perl perl-base But switching to 'updates testing' then showed the same result ? So I installed the package from issued repos, then... AFTER update: specifically choosing just 'postgrey' pulled in the missing Perl things: - perl-BerkeleyDB-0.550.0-5.mga6.x86_64 - perl-IO-Multiplex-1.160.0-3.mga6.noarch - perl-Net-Server-2.8.0-5.mga6.noarch - postgrey-1.37-1.1.mga6.noarch $ rpm -q postgrey postgrey-1.37-1.1.mga6 $ urpmq -d postgrey | grep ^perl perl perl-BerkeleyDB perl-File-Sync perl-IO-Multiplex perl-MDK-Common perl-Net-DNS perl-Net-Server perl-NetAddr-IP perl-base So the update does what it says. OK. Validating, advisoried. Whiteboard:
MGA6-32-OK =>
MGA6-32-OK MGA6-64-OK An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2017-0110.html Status:
REOPENED =>
RESOLVED |