1.0.1ubuntu2.13.. it does let me 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:
apt does not configure Pre-Depends: before depending package
Status
** Changed in: apt (Ubuntu Wily)
Assignee: Martin Pitt (pitti) => Nathanael (mnathanael26)
--
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:
apt does not
This bug was fixed in the package ubuntu-release-upgrader - 1:16.10.1
---
ubuntu-release-upgrader (1:16.10.1) yakkety; urgency=medium
* DistUpgrade/{EOL,}ReleaseAnnouncement,
DistUpgrade/DistUpgrade/window_main.ui,
data/gtkbuilder/DistUpgrade.ui,
data/DistUpgrade.cfg,
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Confirmed => Invalid
--
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:
apt does not configure
@Brian Visel - The way the release upgrader works is that it downloads a
tarball of ubuntu-release-upgrader for the release to which you are
upgrading. Subsequently, the fix doesn't need to be in the release from
which you are upgrading. Additionally, using "apt-get dist-upgrade"
bypasses the
..as a sanity check, it'd probably be a good idea for the upgrader to
check and ensure it's running the latest version.
--
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
I am having this issue right now. Before updating, I did:
sudo apt-get-update
sudo apt-get dist-upgrade
..and then launched Software Updater.
However, it seems that the newest version of the software updater didn't
install for whatever reason. As the install is running, if I do:
This bug was fixed in the package ubuntu-release-upgrader - 1:16.04.14
---
ubuntu-release-upgrader (1:16.04.14) xenial; urgency=medium
[ Steve Langasek ]
* No-change rebuild to pick up translations from Launchpad (including the
Greek translations, which had been accidentally
@Matthias - I have commented on your bug report, it looks like you did
not in fact have the fixed version of apt installed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
I've tested an upgrade from Wily to Xenial using the version of the
ubuntu-release-upgrader from -proposed and with apt version
1.0.10.2ubuntu1 installed, with that version of apt the release upgrade
process would not start. Once I installed the newer version of apt, I
was able to start the
Le 26/04/2016 10:51, Martin Pitt a écrit :
> Hello Dawid, or anyone else affected,
>
> Accepted ubuntu-release-upgrader into xenial-proposed. The package will
> build now and be available at https://launchpad.net/ubuntu/+source
> /ubuntu-release-upgrader/1:16.04.14 in a few hours, and then in the
I'm not sure this bug is fixed. I experienced and reported (#1573513)
this on April 22nd when this was supposedly already fixed. I'd like to
add that I definately upgraded wily before doing the dist-upgrade.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (Ubuntu)
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.
Hello Dawid, or anyone else affected,
Accepted ubuntu-release-upgrader into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:16.04.14 in a few hours, and then in the
-proposed repository.
Please help us by testing
If /usr/lib/ubuntu-release-upgrader/check-new-release-gtk is used, which
is called by the update-notifier release upgrade notification, the
upgrade can start without first upgrading the system (because update-
manager is by passed). It is possible to make ubuntu-release-upgrader
require certain
I better correct my statement at #62. I tested it just now and it is
incorrect. Upgrade inside wily (1510) comes first, and then distribution
upgrade.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
I don't know, but the update-manager did an update before I got the
option to upgrade the distribution. I didn't look into the details.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
The question is: was the apt package patch applied BEFORE the
distribution upgrade? I doubt it, if you use the graphical interface.
update-manager does not give you a chance to update first and then do a
distribution upgarde.
--
You received this bug notification because you are a member of
I wonder why this still happens even after the fix is released on
14.04/15.10...
--
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:
apt does not configure
Richard and Winfried,
I thank you both for your input and knowledge. I did basically
:
apt-get autoremove
apt-get update
apt-get install -f
then everything seem to work, for now??? I will wait for the next updates
and see if anything happens.
On Fri, Apr 22, 2016 at 2:16 PM, Winfried
Richard, you should be okay. I have had very similar problems when I
upgraded my virtual systems from wily (1510) to xenial (1604) when they
there still were in development mode. I recovered the upgrade by apt-get
-f install, apt-get update, apt-get dist-upgrade (issued a few times).
--
You
Richard, you should be okay. I have had very similar problems when I
upgraded my virtual systems from wily (1510) to xenial (1604) when there
still were in development mode.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt
I think I got this bug. I upgraded to 16.04 because my update manager proposed
that I do so.
I first had a message that I should choose between lightdm and gdm3. I chose
the default: lightdm.
Then systemd failed to install, then (I don't know in what order)
systemd-sysv
lidpam-systemd
This bug was fixed in the package apt - 1.0.10.2ubuntu2
---
apt (1.0.10.2ubuntu2) wily-proposed; urgency=medium
* Recheck Pre-Depends satisfaction in SmartConfigure, to avoid unconfigured
Pre-Depends (which dpkg later fails on). Fixes upgrade failures of
systemd,
I tested the proposed apt with some package installs (not upgrades) that
involve lots of dependencies (network-manager), conflicts (upstart-sysv
vs. systemd-sysv), and cross-architecture dependencies (ubuntu-
emulator:amd64 depends on ubuntu-emulator-runtime:i386). These all work
fine.
Given that
This bug was fixed in the package apt - 1.0.1ubuntu2.13
---
apt (1.0.1ubuntu2.13) trusty; 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
Did an upgrade to 1604:
1.) modfied /etc/apt/sources.list to include wily-proposed
2.) apt-get update
3.) apt-get install apt which installed apt and libapt-pkg4.16 at version
1.0.10.2ubuntu2
4.) do-release-upgrade -d
5.) success!!
6.) Get apt / libapt-pkg4.16 out in the world tonight or
I installed the version of apt from trusty-proposed and then completed
an upgrade from Trusty to Xenial using that version of apt with the
libgcrypt packages installed.
>From /var/log/dist-upgrade/apt-term.log we can see the following:
Processing triggers for libc-bin (2.19-0ubuntu6.7) ...^M
I installed the version of apt from wily-proposed and then completed an
upgrade from Wily to Xenial using that version of apt with the libgcrypt
packages installed.
>From /var/log/dist-upgrade/apt-term.log we can see the following:
Processing triggers for man-db (2.7.4-1) ...^M
Setting up
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1560797
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hello Dawid, or anyone else affected,
Accepted apt into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.0.10.2ubuntu2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
Happened during upgrade to 16.04, don't know any more details.
+
+ --
+ SRU INFORMATION
+ ===
+ Fix: https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=c75e60eb (applied
in Xenial last week)
+
+ Test case:
+ - Install clean wily amd64 desktop +
This still affects upgrades (see last two duplicates) as these use
trusty's/wily's apt, so we need to SRU this urgently.
** Summary changed:
- package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20
was unconfigured during 15.10 to 16.04 upgrade (apt does not configure
33 matches
Mail list logo
