Re: Will installation on BIOS systems with no ESP be supported in 21.04?

2021-04-16 Thread Sai Vinoba
On Sat, 10 Apr 2021 17:07:37 +0200, Liam Proven  wrote:

> I reported a bug that occurs in both Ubuntu Unity 20.10 and Xubuntu
> 20.10 and which prevents me from installing either OS on my computers:
> 
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1915152
> 
> It seems that the Ubiquity installer *requires* an EFI System
> Partition (ESP) even if being installed on a BIOS-based system with an
> MBR hard disk.
> 
> None of my PC computers use UEFI. I do own 2 with UEFI but I run them
> in legacy BIOS mode with MBR-partitioned disks.
> 
> So they do not have UEFI system partitions.
> 
> Multiple retries of reinstallation of 20.10 always fail because of this.
> 
> My bug report has attracted no attention so I wanted to ask if anyone
> had tried this in 21.04 yet?
> 
> I do not want to repartition and reformat the HDDs of several
> computers just to install a new release of Ubuntu. :-(
> 
> -- 
> Liam Proven 

Hi Liam,
I just want to know if it is not possible for you to allocate around 200-500M 
and mark it as 'EFI System Partition' as the installer is requesting? It 
doesn't require major re-partitioning, doesn't have to be the first partition, 
it can also be extended partition. I checked putting EFI partition as an 
extended partition and it installs and boots properly. Tools like Gparted would 
help you do this without affecting your already existing partitions. 

That said, if you really don't want to create an EFI parition, you can consider 
using Lubuntu. It uses Calamares, not ubiquity and as such is not affected by 
this bug. I did few BIOS mode (MBR parition) installs today, without an EFI 
partition and it installs and boots without any issue.


Regards,
Sai

-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel


Ubuntu Focal update of broken Calibre package

2020-10-15 Thread Sai Vinoba
Hi all,

I checked Calibre in Groovy (version 4.99.12+dfsg+really4.23.0-1) and it works 
fine. As per bug report #1898904 
(https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1898904/comments/7), 
Calibre >=4.15 has the required patch. So, instead of waiting for 5.2, can we 
backport current Groovy version of Calibre to Focal?

Regards,

Sai


Unfortunately, Calibre 5.x requires SIP 5 and PyQt5 that is built against
SIP 5. Moving PyQt5 to the new SIP is a major transition, that happened
in Debian recently (two weeks ago) and did not happen in Ubuntu yet because
of freeze.

This requires changes in many packages simultaneously: at least pyqt5,
pyqt5charts, pyqt5webengine, qscintilla2, calibre, python-poppler-qt5,
veusz, krita and qgis.

I am planning to land this change early in Groovy+1 cycle.

> Is the above (update to 5.2.0) possible in Ubuntu Focal, and if yes,
> what kind if steps are necessary?

So for Focal and Groovy we need a version of Calibre that still uses SIP 4.
Last such version in Debian was 4.99.12+dfsg+really4.23.0-1, Groovy already
has that. If you know some specific fixes, maybe they can be applied on top
of what Focal or Groovy has.

--
Dmitry Shachnev
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss