Tim Daneliuk writes:
> > Are you sure you are using perl-after-upgrade correctly? You do
> > understand that just running:
> >
> > # perl-after-upgrade
> >
> > doesn't actually modify anything on disk: instead it shows you what
> > needs to be done. To actually effect the change you
On 12/21/2011 09:28 AM, Matthew Seaman wrote:
On 21/12/2011 14:59, Tim Daneliuk wrote:
Almost every time there is a perl upgrade, it manages to break
Mailscanner even after running perl-after-upgrade. The solution
ends up being a reinstall of Mailscanner, but this is a real pain,
because you ha
On 21/12/2011 14:59, Tim Daneliuk wrote:
> Almost every time there is a perl upgrade, it manages to break
> Mailscanner even after running perl-after-upgrade. The solution
> ends up being a reinstall of Mailscanner, but this is a real pain,
> because you have to delete and reinstall every dependen
On 12/21/2011 03:59 PM, Tim Daneliuk wrote:
> Almost every time there is a perl upgrade, it manages to break
> Mailscanner even after running perl-after-upgrade. The solution
> ends up being a reinstall of Mailscanner, but this is a real pain,
> because you have to delete and reinstall every depen
Almost every time there is a perl upgrade, it manages to break
Mailscanner even after running perl-after-upgrade. The solution
ends up being a reinstall of Mailscanner, but this is a real pain,
because you have to delete and reinstall every dependent perl
package used by Mailscanner.
Does anyone
