scubuntu-dev team mailing list archive
-
scubuntu-dev team
-
Mailing list archive
-
Message #00006
Re: [Fwd: ubiquity options]
Looking at this page:
http://lintian.debian.org/tags/python-script-but-no-python-dep.html
and my control file for the .deb build:
Package: ubiquity-frontend-scubuntu
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends},
ubiquity, ubiquity-frontend-gtk
Provides: ubiquity-frontend-${mangled-version}
XB-Python-Version: ${python:Versions}
Description: Scubuntu frontend for the Ubiquity live installer
This package provides a GTK+-based user interface frontend for the use
when performing a Scubuntu installation. The interface is derived
from the GTK frontend already available.
I see that I do have the dependency on python.
Not sure what is wrong here
On Wed, 2009-03-04 at 12:58 +0200, Pieter van Zyl wrote:
> Good day.
>
> I have been busy with "# Step4: Test installing with manifest and
> blacklist and remove_extras etc" for the last week and a half."
>
> This means I am actually trying to install and copy the live cd
> filesystem to the target (Phase 2 of the installation for those who have
> read our CSIR paper)
>
> I have a few issues.
>
> They are:
> * Current: Sometimes the live cd would start up by there would be
> a problem. The background is black and there are thousands of
> file managers that are trying to open. No idea why. I can start
> ubiquity scubuntu from the command line. Then it would get to
> the stage at 5% where it will try and copy the file system and
> just stay there busy forever. I thought at first that that there
> was something wrong with the alpha4 cd. But I have tried with
> the new aplha 5. Same issue. Screen captures of the issue are
> attached
> * Previous issues was that it would get to 5% of the file copy and
> then end and say the install finished, please reboot. But this
> meant a broken system as nothing was copied. I fixed this by
> mainly copying the main install script methods to the scubuntu
> install script
> * Also strange: Before you change the live cd iso and run it there
> are no defects if you run the live cd tests. If I create a new
> one with "no changes" there are already 3 defects. There were
> some defects on the release cd's as well (If I remember
> correctly)
>
>
> Somehow ubiquity is broken, specifically the scubuntu deb.
> There are some error messages when I do a debuild.
>
> debuild output is attached.
>
> "E: ubiquity-frontend-scubuntu:
> python-script-but-no-python-dep ./usr/share/ubiquity/scubuntu_install.py"
> this could be the cause? will look into it
>
> But it builds, it installs fine and I can test the first phase (package
> selection) which is fine on my pc.
>
> Any ideas?
>
>
> On Mon, 2009-02-23 at 13:23 +0200, Pieter van Zyl wrote:
> > Update: I have followed option 2 and currently the select screen is
> > displaying. The page numbers is not working correctly.
> >
> > So far Step 1 and Step 2 seems to be working fine. I can see packages
> > are selected.
> >
> > Going to try/implement step 3.
> >
> > On Fri, 2009-02-20 at 14:23 +0200, Pieter van Zyl wrote: y.
> > > working on option 2
> > >
> > > -------- Forwarded Message --------
> > > From: Thomas Fogwill <thomas.fogwill@xxxxxxxxxxxxx>
> > > To: Pieter van Zyl <pvzyl@xxxxxxxxxx>
> > > Subject: ubiquity options
> > > Date: Fri, 20 Feb 2009 13:51:07 +0200
> > >
> > > # Option1: Generate .glade file
> > > # Option2: Copy parent __init__ and changing nested method
> > > # Option3: subclass GtkViewport (something like ScubuntuPkgSelectionGtkViewport) in gui/glade/setupScientific_package_select_tree.glade so that it loads the xml in its __init__
> > >
> > >
> > > # Step1: copy all __init__ from ParentWizard
> > > # Step2: test events
> > > # Step3: create new manifest
> > > # Step4: Test installing with manifest and blacklist and remove_extras etc
> > > # Step5: Cleanup as per option3 above
> > >
> > >
> > >
> > >
> >
> >
--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.
This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean. MailScanner thanks Transtec Computers for their support.
References