RE: FW: FW: [qmailtoaster] qmailtoaster-plus-0.2.14-1.3.17 is out!
I will gladly give it a go. I will need to wait until the beginning of next
week as we are having a nice big snow storm here in New England. I guess
Punxsutawney Phil was right! I will also send an email (off list) to Erik
Espinoza to get any info on necessary changes to the packages (or if they
should work directly).
I'll keep you posted.
Thanks;
Thomas M. Jaeger
Computer Technician, A.A.S.
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-Original Message-
From: Eric Shubes [mailto:[EMAIL PROTECTED]
Sent: Friday, February 29, 2008 11:48 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: FW: FW: [qmailtoaster] qmailtoaster-plus-0.2.14-1.3.17 is out!
Thomas M. Jaeger wrote:
# cat /etc/fedora-release shows:
Fedora release 7 (Moonshine)
The /usr/sbin/qtp-whatami file shows fdr70 (and fdr7064) in the lsiting.
I
also made sure to use /usr/sbin/qtp-whatami to be sure that there are no
redundant older copies somewhere that are being accessed. I still get the
same sorry message. Could it be that the Check Fedora section of the
script is looking for Core instead of just Fedora (as Core was dropped
from the distro since the release of 7)?
That's precisely the problem. They dropped Core from the name and the
script doesn't find the release number as a result.
This was the issue that Natalio was addressing with the alteration of the
qtp-whatami script. The changes made in that script where the addition of
fdr70 to the distro list at the beginning, the removal of word 2 in the
check fedora section and OSVER=$word3 relnum=${word3%.*}:
That's the extent of the fix for FC7/8, but it breaks the script for earlier
versions. Here's a fixed version of that routine:
###
## check fedora
#
b23_fedora(){
BUILD_DIR=/usr/src/redhat
if [ $word1 == Fedora ]; then
if [ $word2 == release ]; then
DISTRO=$word1
OSVER=$word3
relnum=${word3%.*}
case $relnum in
8 | 7 )
BUILD_DIST=fdr${relnum}0
q1_distro_64
esac
elif [ $word2 == Core ]; then
DISTRO=$word1 $word2
OSVER=$word4
relnum=${word4%.*}
case $relnum in
6 | 5 | 4 )
BUILD_DIST=fdr${relnum}0
q1_distro_64
if [ $relnum == 5 ]; then
case $QTARCH in
i386 | $ARCH64 )
tested=y
;;
esac
fi
;;
3 | 2 | 1 )
BUILD_DIST=fdr${relnum}0
;;
esac
fi
fi
}
Will you edit your script with this version and give it a try? If it works
then I'll check it in for the next QTP release.
I have not tested this alteration yet as I fear that upgrading with the
qtp-newmodel might run into issues.
You need to be sure that the packages on the web site have been upgraded for
versions 7,8 before it'll work for sure. I don't know their status, but Erik
Espinoza would know for sure (since he's the one who does all that magic).
If the packages haven't been configured for the version you're running,
they'll be built with the default settings, which probably won't work for
you. If you want to fake it out, the easiest way is to (temporarily) change
the /etc/fedora-release file to correspond to the most recent toaster
version. (don't forget to change it back later!)
Sory for the rambling, the answer to your question is at the top...
NP
Thank you, again,
Thomas M. Jaeger
Computer Technician, A.A.S.
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-Original Message-
From: Eric Shubes [mailto:[EMAIL PROTECTED]
Sent: Friday, February 29, 2008 1:45 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: FW: FW: [qmailtoaster] qmailtoaster-plus-0.2.14-1.3.17 is
out!
That version of qtp-whatami should recognize FC7 (keyword: should).
What does
# cat /etc/fedora-release
tell you?
Thomas M. Jaeger wrote:
I was on vacation and away for a while. I did the qmailtoaster-plus
update via yum (.noarch.0.3.0-1.4.0) and still get Fedora release 7
(Moonshine) is not supported. Sorry when using the qtp-newmodel
command. The qtp-menu also does not run and gives the message, Your
distro is not supported, exiting. Should I uninstall the
qmailtoaster-plus, remove the repository from yum and do a manual
install of QTP? Some of the qtp- commands work but (obviously) not
all. Regardless, I understand that Fedora is not the supported OS (or
OS of choice) and I could go about this all manually. Also, I have not
yet had the chance to try Natalio's qtp-whatami changes. I will give
that a try once the storms have passed through New England over the next
two days. (I could try it remotely but fear the possible errors.)
Thanks, again,
Thomas M. Jaeger
Computer Technician, A.A.S.
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--
-Eric 'shubes'
-
QmailToaster hosted by: VR Hosted http://www.vr.org
[qmailtoaster] unionfs and fc4 trouble
Well, I tried the unioned sandbox method and it didn't seem to work for me. I appears I have an unsupported kernel (fc4 vintage). The logs mention that I can add some extra flags to the command but I am unsure of the impact or repercussions. Comments are welcome. I have pasted some text from my session, any assistance would be greatly appreciated. Would you like a unioned sandbox (quicker, smaller, maybe less stable) [y]/n: y Using union filesystem ... qtp-mount-sandbox v0.2.6 --No existing unionfs12 found. Continuing with build process --Testing for valid rpm install tool: yum -y install found! --Searching for valid kernel source/devel to build unionfs12: kernel-devel-2.6.17-1.2142_FC4 --Looking at current kernel --You have the kernel source for the running kernel! --Building mv: cannot stat `unionfs.ko': No such file or directory --Something went wrong with the unionfs12 build --Please check /var/log/unionfs-build.log to see what happened qtp-build-unionfs failed,ure. Exiting! qtp-newmodel - qtp-mount-sandbox failed, exiting --- Hit ENTER to return to menu --- ** my logs are as follows: ** make -C /lib/modules/2.6.17-1.2142_FC4/build SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2 FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk clean make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686' CLEAN /opt/qmailtoaster-plus/src/unionfs-1.2/.tmp_versions make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686' rm -f subr.o dentry.o file.o inode.o main.o super.o stale_inode.o branchman.o xattr.o rdstate.o copyup.o dirhelper.o rename.o unlink.o lookup.o persistent_inode.o commonfops.o dirfops.o print.o malloc_debug.o mmap.o unionfs.o unionfs.ko *.d .*.flags \#* *~ rm -f TAGS tags rm -f unionfs-1.2.tar.gz make -C utils clean make[1]: Entering directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils' rm -f unionctl uniondbg unionimap TAGS tags make[1]: Leaving directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils' ** If you have questions about or problems building Unionfs, please read INSTALL. ** make -C /lib/modules/2.6.17-1.2142_FC4/build SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2 FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk modules make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686' CC [M] /opt/qmailtoaster-plus/src/unionfs-1.2/subr.o In file included from /opt/qmailtoaster-plus/src/unionfs-1.2/subr.c:22: /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:50:2: error: #warning You are compiling Unionfs on an unsupported kernel version. /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:51:2: error: #warning To compile Unionfs, you will need to define UNIONFS_UNSUPPORTED. /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:52:2: error: #warning Try adding: EXTRACFLAGS=-DUNIONFS_UNSUPPORTED to fistdev.mk make[2]: *** [/opt/qmailtoaster-plus/src/unionfs-1.2/subr.o] Error 1 make[1]: *** [_module_/opt/qmailtoaster-plus/src/unionfs-1.2] Error 2 make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686' make: *** [unionfs.ko] Error 2 *** Francisco Paco Peralta
Re: FW: FW: FW: [qmailtoaster] qmailtoaster-plus-0.2.14-1.3.17 is out!
As I've mentioned before in the list, Fedora fixes are not coming. I'm
spending my time working on the QT 1.4 branch right now. The current
branch will be maintained as is + upstream fixes for now.
The Fedora + QT users is such a low amount of users, it's really not
worth it especially since FC6 compiles FC7/8 properly in most cases.
If someone wants to step up and rewrite the current spec files (and
send me diffs) then I will go ahead and release them.
I can't do it all myself.
EE
On Sat, Mar 1, 2008 at 6:18 AM, Thomas M. Jaeger [EMAIL PROTECTED] wrote:
Erik;
Below is the correspondence from the qmailtoaster list for a Fedora fix that
I will test early next week (you probably already have this info but...).
Erik Shubes has said that you would know the status of the packages online
and if they are upgraded for use on Fedora 7,8 distros. Are they or is
there a way to prepare them for use with Fedora 7,8? (I am running Fedora 7
x86.)
Thanks;
Thomas M. Jaeger
Computer Technician, A.A.S.
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-Original Message-
From: Eric Shubes [mailto:[EMAIL PROTECTED]
Sent: Friday, February 29, 2008 11:48 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: FW: FW: [qmailtoaster] qmailtoaster-plus-0.2.14-1.3.17 is out!
Thomas M. Jaeger wrote:
# cat /etc/fedora-release shows:
Fedora release 7 (Moonshine)
The /usr/sbin/qtp-whatami file shows fdr70 (and fdr7064) in the lsiting.
I
also made sure to use /usr/sbin/qtp-whatami to be sure that there are no
redundant older copies somewhere that are being accessed. I still get the
same sorry message. Could it be that the Check Fedora section of the
script is looking for Core instead of just Fedora (as Core was dropped
from the distro since the release of 7)?
That's precisely the problem. They dropped Core from the name and the
script doesn't find the release number as a result.
This was the issue that Natalio was addressing with the alteration of the
qtp-whatami script. The changes made in that script where the addition of
fdr70 to the distro list at the beginning, the removal of word 2 in the
check fedora section and OSVER=$word3 relnum=${word3%.*}:
That's the extent of the fix for FC7/8, but it breaks the script for earlier
versions. Here's a fixed version of that routine:
###
## check fedora
#
b23_fedora(){
BUILD_DIR=/usr/src/redhat
if [ $word1 == Fedora ]; then
if [ $word2 == release ]; then
DISTRO=$word1
OSVER=$word3
relnum=${word3%.*}
case $relnum in
8 | 7 )
BUILD_DIST=fdr${relnum}0
q1_distro_64
esac
elif [ $word2 == Core ]; then
DISTRO=$word1 $word2
OSVER=$word4
relnum=${word4%.*}
case $relnum in
6 | 5 | 4 )
BUILD_DIST=fdr${relnum}0
q1_distro_64
if [ $relnum == 5 ]; then
case $QTARCH in
i386 | $ARCH64 )
tested=y
;;
esac
fi
;;
3 | 2 | 1 )
BUILD_DIST=fdr${relnum}0
;;
esac
fi
fi
}
Will you edit your script with this version and give it a try? If it works
then I'll check it in for the next QTP release.
I have not tested this alteration yet as I fear that upgrading with the
qtp-newmodel might run into issues.
You need to be sure that the packages on the web site have been upgraded for
versions 7,8 before it'll work for sure. I don't know their status, but Erik
Espinoza would know for sure (since he's the one who does all that magic).
If the packages haven't been configured for the version you're running,
they'll be built with the default settings, which probably won't work for
you. If you want to fake it out, the easiest way is to (temporarily) change
the /etc/fedora-release file to correspond to the most recent toaster
version. (don't forget to change it back later!)
Sory for the rambling, the answer to your question is at the top...
NP
Thank you, again,
Thomas M. Jaeger
Computer Technician, A.A.S.
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-Original Message-
From: Eric Shubes [mailto:[EMAIL PROTECTED]
Sent: Friday, February 29, 2008 1:45 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: FW: FW: [qmailtoaster] qmailtoaster-plus-0.2.14-1.3.17 is
out!
That version of qtp-whatami should recognize FC7 (keyword: should).
What does
# cat /etc/fedora-release
tell you?
Thomas M. Jaeger wrote:
I was on vacation and away for a while. I did the qmailtoaster-plus
update via yum (.noarch.0.3.0-1.4.0) and still get Fedora release 7
(Moonshine) is not supported. Sorry when using the qtp-newmodel
command. The qtp-menu also does not run and gives the message, Your
distro is not supported, exiting. Should I uninstall the
