| 2006-07-27 09:39:05 |
Ian Jackson |
bug |
|
|
added bug |
| 2006-08-18 14:46:47 |
Michael Vogt |
update-manager: assignee |
|
mvo |
|
| 2006-08-18 14:46:47 |
Michael Vogt |
update-manager: statusexplanation |
|
|
|
| 2006-08-29 10:52:27 |
Michael Vogt |
update-manager: status |
Unconfirmed |
Confirmed |
|
| 2006-08-29 10:52:27 |
Michael Vogt |
update-manager: statusexplanation |
|
Thanks for this reminder.
I was looking into this today and while this is certainly possible. But I'm concerned that the addition of breaks may break the dist-upgrader in much the same way as what happend to firefox and the firefox-theme package.
The problem is essentially the same, i.e. the libapt implementation that calculates the upgrade from dapper->edgy will not know about breaks (yet). Downloading/install dpkg early does not help here because libapt needs some understanding about the field as well. Upgrading dpkg/apt and then re-runing the dist-upgrader to calculate a new upgrade would work but it makes the operation irreversible (well, we could DOWNGRADE again *shudder*) - something that we don't really want.
I see the following possible strategies:
1. put a updated apt into dapper-updates that supports breaks (and if we do this anyway add dpkg as well to avoid the extra step of the dist-upgrader). This shouldn't be too bad because presumably this changes does not change anything for packages without breaks-fields. OTOH it is going to be a invasive change in dapper (something we may not want to do after the X fiasco)
2. put a updated apt into dapper-updates that maps "breaks" to "conflicts". This means we don't win anything but we don't lose anything either. The only advantage here is that the change in apt is likely to be minimal (~5 lines of code hopefully)
3. bite the bullet and start using breaks in edgy :(
None of those is very applealing. I'm open for suggestions and better ideas of course :)
Cheers,
Michael |
|
| 2006-09-13 08:06:45 |
Michael Vogt |
title |
update-manager for edgy needs to upgrade dpkg early on |
update-manager for edgy needs to upgrade dpkg/apt before calculating the upgrade to support the new "breaks" |
|
| 2006-09-21 15:20:05 |
Michael Vogt |
update-manager: statusexplanation |
Thanks for this reminder.
I was looking into this today and while this is certainly possible. But I'm concerned that the addition of breaks may break the dist-upgrader in much the same way as what happend to firefox and the firefox-theme package.
The problem is essentially the same, i.e. the libapt implementation that calculates the upgrade from dapper->edgy will not know about breaks (yet). Downloading/install dpkg early does not help here because libapt needs some understanding about the field as well. Upgrading dpkg/apt and then re-runing the dist-upgrader to calculate a new upgrade would work but it makes the operation irreversible (well, we could DOWNGRADE again *shudder*) - something that we don't really want.
I see the following possible strategies:
1. put a updated apt into dapper-updates that supports breaks (and if we do this anyway add dpkg as well to avoid the extra step of the dist-upgrader). This shouldn't be too bad because presumably this changes does not change anything for packages without breaks-fields. OTOH it is going to be a invasive change in dapper (something we may not want to do after the X fiasco)
2. put a updated apt into dapper-updates that maps "breaks" to "conflicts". This means we don't win anything but we don't lose anything either. The only advantage here is that the change in apt is likely to be minimal (~5 lines of code hopefully)
3. bite the bullet and start using breaks in edgy :(
None of those is very applealing. I'm open for suggestions and better ideas of course :)
Cheers,
Michael |
|
|
| 2006-09-21 15:20:51 |
Michael Vogt |
title |
update-manager for edgy needs to upgrade dpkg/apt before calculating the upgrade to support the new "breaks" |
update-manager for edgy needs to upgrade dpkg/apt before calculating the upgrade to support the new "breaks" - otherwise the upgrade may fail |
|
| 2006-09-22 23:12:04 |
Michael Vogt |
update-manager: status |
Confirmed |
In Progress |
|
| 2006-09-22 23:12:04 |
Michael Vogt |
update-manager: statusexplanation |
|
Here is the current status for this bug:
- a new version of the dist-upgrader is uploaded. it supports fetching of selected backports from arbitrary sources.list fragments (e.g. dapper-backports)
- it will get and unpack those packages into a tempdir and modify PATH,LD_LIBRARY_PATH and PYTHONPATH to make sure that the updated versions are used
- it will re-exec itself once the update is fetched to support the new libraries
- it will still work with --cdrom, even if no updates are found on the cdrom if a network is used
Still todo:
1. get the backports into the official dapper-backports
2. add the backports to the CD
3. make dist-upgrader look for the backports on CD first (to support upgrades without network) |
|
| 2006-09-27 07:44:09 |
Michael Vogt |
update-manager: statusexplanation |
Here is the current status for this bug:
- a new version of the dist-upgrader is uploaded. it supports fetching of selected backports from arbitrary sources.list fragments (e.g. dapper-backports)
- it will get and unpack those packages into a tempdir and modify PATH,LD_LIBRARY_PATH and PYTHONPATH to make sure that the updated versions are used
- it will re-exec itself once the update is fetched to support the new libraries
- it will still work with --cdrom, even if no updates are found on the cdrom if a network is used
Still todo:
1. get the backports into the official dapper-backports
2. add the backports to the CD
3. make dist-upgrader look for the backports on CD first (to support upgrades without network) |
Removed the beta-blocker tag. We do not ship any package that uses Breaks so this is not required for the dapper->edgy upgrade. |
|
| 2006-09-29 10:02:52 |
Andreas Constantinides |
bug |
|
|
added attachment 'apt.log' (apt.log) |
| 2007-09-07 15:10:36 |
Michael Vogt |
title |
update-manager for edgy needs to upgrade dpkg/apt before calculating the upgrade to support the new "breaks" - otherwise the upgrade may fail |
[dapper->hardy] update-manager for edgy needs to upgrade dpkg/apt before calculating the upgrade to support the new "breaks" - otherwise the upgrade may fail |
|
| 2007-11-19 19:31:43 |
gerard |
bug |
|
|
assigned to update-manager (Baltix) |
| 2008-02-01 11:13:29 |
Michael Vogt |
update-manager: status |
In Progress |
Fix Released |
|
| 2008-02-01 11:14:08 |
Michael Vogt |
update-manager: status |
New |
Fix Released |
|
