** Summary changed:
- package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20
was unconfigured during 15.10 to 16.04 upgrade
+ package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20
was unconfigured during 15.10 to 16.04 upgrade (apt does not configure
Pre
Sorry, missed the the google earth dependencies
** Attachment added: "google earth dependencies"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1560797/+attachment/4637413/+files/all-google-earth-dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
To
comment to #42: Paul, the installation of the skype package pulls in
libgcrypt20:i386 amongst others. And google-earth-stable does the same.
See attachments for details.
** Attachment added: "skype dependencies"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1560797/+attachment/4637396/+fi
```
dpkg --purge libcgmanager0:i386 libdbus-1-3:i386 libgcrypt20:i386
libnih-dbus1:i386 libsystemd0:i386
```
Wouldn't using `apt-get purge` more proper than using `dpkg --purge`?
One week before 14.04 release, it would be great if the patch lands 14.04 and
15.10 soon.
--
You received this bug
Quick fix solution if you hit this on an amd64 system before the patch
propagates:
dpkg --purge libcgmanager0:i386 libdbus-1-3:i386 libgcrypt20:i386
libnih-dbus1:i386 libsystemd0:i386
(Don't know why my system had i386 versions of these packages installed,
maybe they were automatically installed
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu Wily)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.ne
For me, the bug fixing and the way of working is very impressive!
Thank You all for Your help!
That's the reason, why i like using linux ubuntu!
I hadn't any other problem after upgrading from 15.10 to 16.04!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
This bug was fixed in the package apt - 1.2.10ubuntu1
---
apt (1.2.10ubuntu1) xenial; urgency=medium
* Recheck Pre-Depends satisfaction in SmartConfigure, to avoid unconfigured
Pre-Depends (which dpkg later fails on). Fixes upgrade failures of
systemd, util-linux, and other
I think we need to backport this to trusty and wily too, as it's not
guaranteed that we get the new apt before the affected packages on
upgrade.
** Also affects: apt (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Wily)
Importance: Undecided
St
** Changed in: apt (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1560797
Title:
package systemd-sysv 225-1ubuntu9.1 faile
Wow David, you rock! Thanks muchly!
Also thanks to Winfried for his exemplary testing.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
** Changed in: apt (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubunt
I downloaded the apt source for ubuntu-mate-1510-amd64, modified the two
lines in apt_pkg/packagemanager.cc, rebuild the lot according to
http://askubuntu.com/questions/81870/how-to-download-modify-build-and-
install-a-debian-source-package, and installed it locally on my ubuntu-
mate-1510-amd64 sy
The attachment "0001-recheck-Pre-Depends-satisfaction-in-
SmartConfigure.patch" seems to be a patch. If it isn't, please remove
the "patch" flag from the attachment, remove the "patch" tag, and if you
are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message perfo
Attached is a trivial patch [in retrospective] I just committed upstream
which should fix this issue – I have only verified it by logchecking
with the two status files from the buglog (again: thanks!) through, I
haven't actually run it on a real system so testers welcome!
That should be easily bac
I have been playing a bit and did a fully manual update to 1604:
1.0) disable any third party packages in /etc/apt/source.list.d/
1.1) in /etc/apt/source.list change "wily" to "xenial" throughout
2.) apt-get update
3.) apt-get install base-file dpkg systemd
4.) apt-get dist-upgrade
5.) and it works
I compared an update of a 1510-amd64 only system - the one from above
(ubuntu-mate-15.10-desktop-amd64.iso) with a the same system, added the
libgcrypt20:i386 packages.
1.) There is hardly any de-configuring going in the "pure" amd64 system, only
(plymouth and ifupdown).
2.) in the amd64 + libgcr
What did not happen in amd64 + libgcrypt20:i386 system: the de-
configured packages were not set up again "Setting up ...". What
triggers the setup to happen?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
http
I just marked bug 1569099 as a duplicate, although it happens for a
different package (libudev1:i386 and util-linux) the root cause in apt
looks fairly identical.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
I've confirmed Winfried's reproduce steps on a Ubuntu 15.10 clean
install VM.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1560797
Title:
package systemd-sysv 225-1ubuntu9.1
Why would amd64 arch. systemd depends on i386 arch. libgcrypt20?
Anyway thanks for testing, I'll try to reproduce it as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1560
5.) bang, see attached /var/log/dist-upgrade/apt-term.log
...
dpkg: dependency problems prevent configuration of systemd:^M
systemd depends on libgcrypt20 (>= 1.6.1); however:^M
Package libgcrypt20:amd64 is not configured yet.^M
^M
dpkg: error processing package systemd (--configure):^M
depend
1.) fresh install of ubuntu-mate 1510 in a VirtualBox environment
2.) sudo apt-get update && sudo apt-get dist-upgrade # --to get latest kernel
etc ...
3.) sudo apt-get install libgcrypt20:i386 # -- force installation of
libgcrypt20:i386
4.) sudo do-relase-upgrade -d
--
You received this bug no
Oops, I made wrong new title, fixed.
Now we finally have a way to reproduce the bug!
** Summary changed:
- package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20
was unconfigured during 15.04 to 16.04 upgrade
+ package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: l
I just confirmed: clean am64 system + installation of libgcrypt20:i386
(plus dependencies) breaks the upgrade.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1560797
Title:
pa
I will attach /var/log/dist-upgrade/screenlog.0. It shows that only
libgcrypt20:i386 is deconfigured (line 1448), but apt breaks later.
** Attachment added: "screenlog shows "De-configuring libgcrypt20:i386""
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1560797/+attachment/4633874/+f
Copy from a duplicate bug report...
```
Winfried PLappert (winfried-plappert) wrote 3 hours ago:#4
I have done some more testing:
1.) I removed all the i386 packages, used for skype and google-earth and did a
'do-release-upgrade -d' -- and it worked.
2.) I rerun the 'do-release-upgrade -
I noticed that there's a /var/log/dist-upgrade/apt-
clone_system_state.tar.gz which seems to have most (if not all) APT
state before upgrading, maybe someone can reconstruct an similar system
to test on?
** Attachment added: "/var/log/dist-upgrade/apt-clone_system_state.tar.gz"
https://bugs.la
Thank you both for the files! A quick test suggests that both expose the
problem by unpacking but not configuring libgcrypt before touching
systemd. The actual produced order is quiet different through (and both
systems are obviously far away from a minbase chroot – which happily
does the right th
Sorry, please entirely ignore #17 as I wrongly recognize my system as
upgraded from trusty, but in fact it is a wily clean install instead.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.
The system that I've used is based on my os distro project "Taiwan
Community Customized Unofficial Ubuntu Operating System" which is based
on Ubuntu trusty and is downloadable from https://github.com/Ubuntu-
Taiwan-Community/Ubuntu-TW-
Ubuntu/releases/tag/v0.3.0-release201510120351 , I've used this
Hi,
I've disabled and also downgraded most 3rd-party repo packages by using APT
Pinning before upgrading Ubuntu and have recorded an 4.5 hour long screencast
while I doing this and the entire upgrade, please refer to the video:
https://www.youtube.com/watch?v=yzK7uEybliQ
The dpkg.status backup
OK, here ist my "dpkg.status.X.gz", which is the last one befor update
(Update was at 2016.04.08; last day, where Ubuntu was started before,
was the date of the log-file 2016.04.05).
** Attachment added: "dpkg.status.1.gz from 2016-04-05"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/
As pitti can't reproduce it with a clean system there is a good chance
an "unrelated" package from a PPA or cruft from an earlier upgrade
confuses apt (as far as I remember PPAs are disabled on upgrade in
Ubuntu, so it can't be new "unrelated" packages at least). These bugs
are everyone’s favorite
It seem's, i have the problem on 2 Notebooks with Update from 15.10 => 16.04:
1st HP Elitebook with xubuntu, 2nd Dell Latitude with Ubuntu.
Maybe other logs are useful? F.e. my apt-term.log from the Dell-Nb.:
/var/log/dist-upgrade/apt-term.log. See attachm.
** Attachment added: "/var/log/dist-
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: apt (Ubuntu)
Importance: Undecided => High
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
This report and all duplicates use :amd64 and :i386 packages at the same
time. I tried to reproduce this again with
dpkg --add-architecture i386
apt update
apt install libgcrypt20:i386 libcap2:i386
# switch apt sources to xenial
apt-get dist-upgrade
but this still works fine for me, so
Thanks, it's good to finally have a complete log here. I don't
understand why apt fails on that error instead of simply configuring the
new libgcrypt20 first -- libgcrypt20 has no circular dependencies with
systemd, it only depends on libgpg-error0 and libc6, and both are
configured before. And the
```
(Reading database ... 100%^M(Reading database ... 692766 f
iles and directories currently installed.)
Preparing to unpack .../libgcrypt20_1.6.5-2_amd64.deb ...
De-configuring libgcrypt20:i386 (1.6.3-2ubuntu1.1) ...
Unpacking libgcrypt20:amd64 (1.6.5-2) over (1.6.3-2ubuntu1.1) ...
Preparing to u
@Martin
> Can you please look in /var/log/dist-upgrade/ whether there is a more
> complete term log there?
Here's your log.
** Attachment added: "/var/log/dist-upgrade/apt-term.log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1560797/+attachment/4628024/+files/apt-term.log
** Chan
> Seems to be resolved by today's update to systemd-sysv 229-3ubuntu1
No, I still encounter this issue on 4/6 and I'm sure all updates are installed.
So the bug still exist.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sys
See my report #1565363 for details of this still happening with
systemd-sysv 229-3ubuntu2. (Sorry for the comment spam.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/15607
I just experienced this same issue. I upgraded from 15.10 to 16.04 last
night, so that update apparently didn't resolve it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/15
Seems to be resolved by today's update to systemd-sysv 229-3ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1560797
Title:
package systemd-sysv 225-1ubuntu9.1 faile
44 matches
Mail list logo