This bug was fixed in the package apt - 1.0.1ubuntu2.11
---
apt (1.0.1ubuntu2.11) trusty; urgency=medium
* apt-pkg/packagemanager.cc:
- fix incorrect configure ordering in the SmartConfigure step by skipping
packages that do not need immediate action. (LP: #1347721,
Hello Erick, or anyone else affected,
Accepted apt into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.11 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Verification done via the other bug report.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347721
Title:
Saucy -> Trusty
This was never fixed in Trusty and has manifested itself as bug 1497688
when upgrading to Vivid. The test case for fixing this exists in the
other bug.
** Changed in: apt (Ubuntu Trusty)
Status: Triaged => In Progress
** Changed in: apt (Ubuntu Trusty)
Assignee: Michael Vogt (mvo) =>
** Changed in: apt (Ubuntu Trusty)
Milestone: ubuntu-14.04.2 = ubuntu-14.04.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347721
Title:
Saucy - Trusty upgrade failed: procps fails to
Installed and updated Saucy, enabled proposed, and ran apt-get install
apt:
Start-Date: 2014-08-11 23:15:49
Commandline: apt-get install apt
Upgrade: apt:i386 (0.9.9.1~ubuntu3.2, 0.9.9.1~ubuntu3.3), libapt-pkg4.12:i386
(0.9.9.1~ubuntu3.2, 0.9.9.1~ubuntu3.3)
End-Date: 2014-08-11 23:16:02
Then
This bug was fixed in the package apt - 0.9.9.1~ubuntu3.3
---
apt (0.9.9.1~ubuntu3.3) saucy-proposed; urgency=low
* apt-pkg/packagemanager.cc:
- fix incorrect configure ordering in the SmartConfigure step
by skiping packages that do not need immediate action
(LP:
For those of us who have been affected by the bug, it would be good to
have guidance on whether we need to do a clean install of 14.04 or if
there's some other action that should be taken. As some others have
reported, my system seems to be working properly, but would like to know
if there's some
@Jim - its hard to know with our more information from you. Did you
upgrade from 12.04 or from 13.10? How did you go about working around
the upgrade failure?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Erick, or anyone else affected,
Accepted apt into saucy-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/apt/0.9.9.1~ubuntu3.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
@Brian - I updated from 13.10. All I did to recover was wait for the
aborted upgrade to complete or recover, and rebooted my system, and it
claims to be running 14.04 now. The only thing that seemed potentially
funny was a message, error: diskfilter writes are not supported when I
booted it.
** Branch linked: lp:ubuntu/saucy-proposed/apt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347721
Title:
Saucy - Trusty upgrade failed: procps fails to configure
To manage notifications about
@Adam, I'm installing Saucy now - will follow up ASAP.
@Jim, be sure to check and see what kernel you're now running via uname
-r as I did in comment #4. As best I recall I seemed to be able to
recover simply by running update-grub and apt-get -f install (and
following suggestions provided by -f
A improved version of the patch, I tested it with:
- precise build chroot - trusty
- saucy build chroot - trusty
- trusty build chroot - utopic (2014-07-29)
and it worked for those cases correctly.
The bug was that apt tried to SmartUnPack packages that were
dependencies but did not need
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Utopic)
Importance: Critical
Assignee: Michael Vogt (mvo)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I also did a precise-trusty-utopic upgrade cycle with the patch (the
precise base that triggered #1347964 before) and again all good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347721
Title:
** Changed in: apt (Ubuntu Trusty)
Assignee: (unassigned) = Michael Vogt (mvo)
** Changed in: apt (Ubuntu Trusty)
Milestone: None = ubuntu-14.04.2
** Changed in: apt (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: apt (Ubuntu Trusty)
Status: New = In Progress
**
** Branch linked: lp:ubuntu/utopic-proposed/apt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347721
Title:
Saucy - Trusty upgrade failed: procps fails to configure
To manage notifications about
This bug was fixed in the package apt - 1.0.4ubuntu6
---
apt (1.0.4ubuntu6) utopic; urgency=low
* apt-pkg/packagemanager.cc:
- fix incorrect configure ordering in the SmartConfigure step
by skiping packages that do not need immediate action
(LP: #1347721)
--
** Patch removed: diff with the fix
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1347721/+attachment/4164541/+files/lp1347721.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347721
And I just verified that the commit before the offending one (66706285)
fully works and upgrades the system correctly. The immediate-configure
property is also better honored.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This diff works for me:
diff --git a/apt-pkg/packagemanager.cc b/apt-pkg/packagemanager.cc
index 393f836..57d4b5a 100644
--- a/apt-pkg/packagemanager.cc
+++ b/apt-pkg/packagemanager.cc
@@ -406,6 +406,12 @@ bool pkgPackageManager::SmartConfigure(PkgIterator Pkg, int
if
** Patch added: diff with the fix
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1347721/+attachment/4164541/+files/lp1347721.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347721
Title:
Hm, now that saucy is closed, how can I upload a updated apt into saucy-
updates that contains the fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347721
Title:
Saucy - Trusty upgrade failed:
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347721
Title:
Saucy - Trusty upgrade failed: procps fails to configure
To manage notifications about this bug go to:
Some more work is needed fo the patch, its eliminating too many case.
But the direction is there, the SmartConfigure() is currently trying to
configure too much too early when its not really needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Chroot that triggers the bug with a small set of
dependencies
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1347721/+attachment/4162808/+files/upgrade-bug-smaller4.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It seems like the issue is the following:
There is a dependency loop
mountall-udev-procps-initscripts-mountall. When apt tries to deal
with it, it configures them all initially together, then it finds the
libplymouth4 dependency of mountall that is not unpacked yet and
inserts the unpack at this
I bisected this now (as the precise apt did not trigger the bug in the
chroot) and it it appears to be caused by:
42d51f333e8ef522fed02cdfc48663488d56c3a3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also reproduced in the lab:
https://jenkins.qa.ubuntu.com/view/Upgrade/job/upgrade-ubuntu-saucy-trusty-desktop-amd64/140/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347721
Title:
Saucy - Trusty
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: High = Critical
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) = Canonical Foundations Team
(canonical-foundations)
** Description changed:
- I'm just performing 14.04.1 pre-release testing and decided
The jenkins log shows packages being configured out of order:
Preparing to unpack .../initscripts_2.88dsf-41ubuntu6_amd64.deb ...
Unpacking initscripts (2.88dsf-41ubuntu6) over (2.88dsf-41ubuntu3) ...
[...]
dpkg: dependency problems prevent configuration of procps:
procps depends on initscripts;
I just tried to reproduce it locally without much success, I try again
tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347721
Title:
Saucy - Trusty upgrade failed: procps fails to
33 matches
Mail list logo
