On 03/29/2015 08:01 PM, Niko Tyni wrote:
> Glad to see progress on this!
>
> On Sun, Mar 29, 2015 at 05:46:44PM +0200, Kasper Loopstra wrote:
>
>> However, I am quite sure that I removed /usr/local/share before starting
>> off with the upgrade, so perhaps there is something wrong with the
>> upgrad
Glad to see progress on this!
On Sun, Mar 29, 2015 at 05:46:44PM +0200, Kasper Loopstra wrote:
> However, I am quite sure that I removed /usr/local/share before starting
> off with the upgrade, so perhaps there is something wrong with the
> upgrade path between wheezy and jessie. So below is what
On 03/29/2015 05:02 PM, gregor herrmann wrote:
> On Sun, 29 Mar 2015 16:44:07 +0200, Kasper Loopstra wrote:
>
>> I'm not sure where to go from here? Should I wait until #781120 is
>> resolved in jessie, or continue trying to figure out what's wrong?
> The fix will only print a better error message
On Sun, 29 Mar 2015 16:44:07 +0200, Kasper Loopstra wrote:
> Setting up spamassassin (3.4.0-6) ...
> Can't locate strict.pm: Permission denied at /usr/bin/sa-update line 23.
> BEGIN failed--compilation aborted at /usr/bin/sa-update line 23.
> dpkg: error processing package spamassassin (--config
Dear Niko,
I recently did a new upgrade on a copy of the same system, but before
the upgrade I moved everything in /usr/local to a backup location, and
only replaced some scripts in /usr/local/sbin we use to restart our LDAP
server and such.
On 03/24/2015 08:35 PM, Niko Tyni wrote:
> Also, just
On Tue, Mar 24, 2015 at 09:35:40PM +0200, Niko Tyni wrote:
> On Mon, Mar 23, 2015 at 10:24:50AM +0100, Kasper Loopstra wrote:
> > Or should we postpone further testing of the jessie upgrade path until a
> > new version of Perl becomes available in testing? Will that happen
> > before release?
>
>
On Mon, Mar 23, 2015 at 10:24:50AM +0100, Kasper Loopstra wrote:
> >> Setting up spamassassin (3.4.0-6) ...
> >> Can't locate strict.pm: Permission denied at /usr/bin/sa-update line 23.
> > I assume you have a restricted directory on the default Perl search path
> > (@INC) that the debian-spamd u
> As far as I know, the system we're using never had any special Perl
> stuff happening to it, but it has been upgraded from squeeze (or maybe
> etch) over the last years. Should I raise a bug with the perl package?
Looks like you have ancient modules sitting in /usr/local/
I'd suggest to mode as
Dear Niko,
Thank you for the quick response,
>> Setting up spamassassin (3.4.0-6) ...
>> Can't locate strict.pm: Permission denied at /usr/bin/sa-update line 23.
> I assume you have a restricted directory on the default Perl search path
> (@INC) that the debian-spamd user can't read, probably u
On Fri, Mar 20, 2015 at 08:54:21AM +0100, Kasper Loopstra wrote:
> Package: spamassassin
> Version: 3.4.0-6
> Severity: important
> Setting up spamassassin (3.4.0-6) ...
> Can't locate strict.pm: Permission denied at /usr/bin/sa-update line 23.
I assume you have a restricted directory on the de
Package: spamassassin
Version: 3.4.0-6
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Doing a wheezy/jessie upgrade on a virtualbox clone of our server, we
encountered some errors with spamas
11 matches
Mail list logo
