First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 149827
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Antivirus Team <antivirus@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Janne Pikkarainen <jaba@mikrobitti.fi>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 149827 depends on: Show dependency tree
Show dependency graph
Bug 149827 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-10-02 03:08 0000 
A new version of amavisd-new was released couple of days ago. It should be
mostly backwards compatible, although couple of new configuration parameters
and changes are present. This also seems to be a normal maintenance release
with no urgent security or bug fixes, so take your time.

My test server (with Postfix + OpenLDAP + amavisd-new + SpamAssassin) continued
to work when I just renamed the ebuild, renamed the
amavisd-new-2.4.2-amavisd.conf-gentoo.patch to
amavisd-new-2.4.3-amavisd.conf-gentoo.patch and emerged it away. My stunt is
not probably the way to go, and especially the new configuration variables
should be examined before letting this release to join Portage.

Cheers,

Jaba

------- Comment #1 From Andrej Kacian (RETIRED) 2006-10-04 07:18:42 0000 ------- 
Bumped in portage, thanks!

Lot of conf file changes this time, but all of it is pretty minor stuff,
explained in release notes. Nothing major to deal with.

------- Comment #2 From Janne Pikkarainen 2006-10-04 08:18:20 0000 ------- 
Thank you very much!
First Last Prev Next    No search results available      Search page      Enter new bug