I can confirm this is an issue.
I had to hack through the systemd start file (and remove -p ...) for
opendkim, otherwise I couldn't get postfix milter to connect to the DKIM
filter daemon (which require a inet connection. Local/Unix socket won't
work because my postfix is chroot'd)..
--Ivan
Giuseppe Iuculano wrote:
Hi Ivan,
Why an installation shouldn't have the default wordpress admin user?
Well, the 'default' administrator may no longer exist for several
reasons, but the main reason is because it was removed after
installation since it didn't seem necessary to keep it based
Package: wordpress
Version: 2.8.3-2
Severity: important
When an installation doesn't use or no longer has the default wordpress
administrative user, the database upgrade cannot be initiated because
the upgrade.php script checks if the current logged in user id is '1'
instead of checking whethe
Package: hercules
Version: 3.04.1-3
Severity: wishlist
Just a quick heads up from upstream !
The current version of hercules upstream is 3.05 (since June 24th 2007).
It would be nice if the debian package could be updated accordingly.
Furthermore, I think most (if not all) debian reported bugs
Fixed upstream too !
thank you,
--Ivan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Andreas, p2,
This is a known issue that has been fixed upstream on 10/19/2006 in CVS :
*** cvs diff -ub starts here ***
diff -u -b -r1.24 -r1.25
--- hercifc.c 23 Apr 2006 04:59:57 - 1.24
+++ hercifc.c 19 Oct 2006 21:15:45 - 1.25
@@ -36,8 +36,10 @@
void* pArg
Package: linux-2.6
Severity: normal
This is about the kernel image installation process (all linux-image-*)
There is a critical time window during install that occurs if
- multiple packages are being installed at once (for exemple during
"apt-get upgrade")
- *AND* the same kernel is being upd
>
> Only problem was that the network interface did not come up. Trying to
> manually start it resulted in:
> # ifup eth0
> Ignoring unknown interface eth0=eth0.
>
> This looks like an issue related to udev persistent device naming.
>
> Further info:
> - The ctc module was loaded:
> # lsmod
> Modu
Some additional info.
This is with a self compiled klibc-2.1-3
If this is is irrelevant to #349857, I will eventually open a new incident.
I am trying this with 2.6.15-4-s390 kernel.. The 2.6.15-3 headers were just
not capable of compiling klibc 1.2-3 for s390 anyway.
Upon IPL (boot), I am gett
>
> On Thu, Dec 01, 2005 at 02:49:03AM +0100, Ivan Warren wrote:
>
> > The build went ok.. however, here is what I get :
> >
> > deb390-1:/tmp# /home/ivan/local/sbin/yaird -v -o junk.img
> > yaird: goal: template, prologue
> (/home/ivan/local/etc/yai
>
> The code is untested and will probably break. If this
> happens and the cause is
> not immediately obvious, could you add a load of Base::debug
> statements
> to Ccw*.pm and post the diffs and output?
>
Erik,
Well..
The build went ok.. however, here is what I get :
deb390-1:/tmp# /home
> >
> > I therefore removed the "INPUT" goal from /etc/yaird/Default.cfg
> > (since input devices on S/390 z/Arch is irrelevant) as well
> > as anything relating to mouse, etc..
>
> OK, manageable so far ...
>
Agreed.. although something needs to be done about it - eventually
(otherwise depende
12 matches
Mail list logo
