With these "fixes", users are unable to boot a live USB with persistent
partition:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489855
http://askubuntu.com/questions/664577/unable-to-boot-ubuntu-live-usb-flash-drive-with-casper-rw-persistent-partition
Is there any likelihood that the "f
This bug was fixed in the package casper - 1.363
---
casper (1.363) wily; urgency=low
* scripts/casper: migrate existing persistent disk images to the
updated upper/work form. Record the actual format used and
ensure we use the existing format and abort if not possible.
** Branch linked: lp:ubuntu/casper
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481117
Title:
casper 1.340.1 breaks previous persistency
To manage notifications about this bug go to:
https://bugs
** Changed in: casper (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: casper (Ubuntu Vivid)
Status: New => Triaged
** Changed in: casper (Ubuntu Vivid)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This bug was fixed in the package casper - 1.340.2
---
casper (1.340.2) trusty; urgency=low
* scripts/casper: migrate existing persistent disk images to the
updated upper/work form. Record the actual format used and
ensure we use the existing format and abort if not possibl
Ok tested with the bits in the package in -proposed. Tested create
persistence from .2 and then boot against .2, invalid format specifier,
and a clean create from the -proposed bits. Seems to work as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You receive
Worth noting that, with this SRU, downgrading will still break, and
there's pretty much nothing we can do about that. If you setup
persistence on 14.04.3 or 15.10 or something and try to later boot it
with <= 14.04.2, it's not going to work. I don't think that's a use-
case we can even attempt t
** Changed in: casper (Ubuntu Trusty)
Milestone: None => ubuntu-14.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481117
Title:
casper 1.340.1 breaks previous persistency
To manage notific
Hello Adrien, or anyone else affected,
Accepted casper into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/casper/1.340.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubunt
** Changed in: casper (Ubuntu)
Milestone: None => ubuntu-15.08
** Changed in: casper (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481117
Title:
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481117
Title:
casper 1.340.1 breaks previous persistency
To manage notifications about this bug go to:
https://bugs.launchpad.ne
** Changed in: casper (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481117
Title:
casper 1.340.1 breaks previous persistency
To manage
Indeed we probably should try to support this. Marking Triaged / Medium,
as I'm not sure whether this is a common use case. Handling the
migration should be fairly straightforward, I'd think.
** Changed in: casper (Ubuntu)
Status: New => Triaged
** Changed in: casper (Ubuntu)
Importance
Adding tag "regression-update" as per comment #7 of bug #1401620
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481117
Title:
casper 1.340.1 breaks previous persist
14 matches
Mail list logo
