Bug#726174: apt: APT::Get::Upgrade-Allow-New installs new packages when depending package isn't upgraded

2016-10-09 Thread Timo Haas
Hi

I've got the same problem. Situation after apt autoremove:

apt upgrade
Reading package lists... Done
Building dependency tree  
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer
required:
  kactivities-bin kactivitymanagerd kio-extras kio-extras-data
kpackagelauncherqml kpackagetool5 ktexteditor-data ktexteditor-katepart
libboost-program-options1.61.0 libboost-regex1.61.0
  libboost-serialization1.61.0 libclang1-3.8 libdbusmenu-qt5-2
libgrantlee-templates5 libkasten3controllers3 libkasten3core3
libkasten3gui3 libkasten3okteta1controllers1 libkasten3okteta1core1
  libkasten3okteta1gui1 libkf5activities5 libkf5attica5
libkf5bookmarks-data libkf5bookmarks5 libkf5declarative-data
libkf5declarative5 libkf5dnssd-data libkf5dnssd5 libkf5globalaccel-bin
  libkf5globalaccel-data libkf5globalaccel5 libkf5globalaccelprivate5
libkf5gpgmepp5 libkf5itemmodels5 libkf5js5 libkf5kcmutils-data
libkf5kcmutils5 libkf5kdelibs4support-data libkf5kdelibs4support5
  libkf5kdelibs4support5-bin libkf5khtml-bin libkf5khtml-data
libkf5khtml5 libkf5kiofilewidgets5 libkf5newstuff-data libkf5newstuff5
libkf5notifications-data libkf5notifications5 libkf5notifyconfig-data
  libkf5notifyconfig5 libkf5package-data libkf5package5 libkf5parts-data
libkf5parts-plugins libkf5parts5 libkf5pty-data libkf5pty5
libkf5quickaddons5 libkf5solid5 libkf5solid5-data libkf5sonnet5-data
  libkf5sonnetcore5 libkf5sonnetui5 libkf5sysguard-data
libkf5texteditor5 libkf5textwidgets-data libkf5textwidgets5
libkf5threadweaver5 libkf5wallet-bin libkf5wallet-data libkf5wallet5
libkf5xmlgui-bin
  libkf5xmlgui-data libkf5xmlgui5 libkomparediff2-5 libkwalletbackend5-5
libobjc-6-dev libokteta2core2 libokteta2gui2 libphonon4qt5-4
libprocesscore7 libprocessui7 libqca-qt5-2 libqca-qt5-2-plugins libssh-4
  phonon4qt5 phonon4qt5-backend-vlc sonnet-plugins
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  kactivities-bin kactivitymanagerd kio-extras kio-extras-data
kpackagelauncherqml kpackagetool5 ktexteditor-data ktexteditor-katepart
libclang1-3.8 libdbusmenu-qt5-2 libkasten3controllers3 libkasten3core3
  libkasten3gui3 libkasten3okteta1controllers1 libkasten3okteta1core1
libkasten3okteta1gui1 libkf5activities5 libkf5attica5
libkf5bookmarks-data libkf5bookmarks5 libkf5declarative-data
libkf5declarative5
  libkf5dnssd-data libkf5dnssd5 libkf5globalaccel-bin
libkf5globalaccel-data libkf5globalaccel5 libkf5globalaccelprivate5
libkf5gpgmepp5 libkf5js5 libkf5kcmutils-data libkf5kcmutils5
libkf5kdelibs4support-data
  libkf5kdelibs4support5 libkf5kdelibs4support5-bin libkf5khtml-bin
libkf5khtml-data libkf5khtml5 libkf5kiofilewidgets5 libkf5newstuff-data
libkf5newstuff5 libkf5notifications-data libkf5notifications5
  libkf5package-data libkf5package5 libkf5parts-data libkf5parts-plugins
libkf5parts5 libkf5pty-data libkf5pty5 libkf5quickaddons5 libkf5solid5
libkf5solid5-data libkf5sonnet5-data libkf5sonnetcore5
  libkf5sonnetui5 libkf5sysguard-data libkf5texteditor5
libkf5textwidgets-data libkf5textwidgets5 libkf5threadweaver5
libkf5wallet-bin libkf5wallet-data libkf5wallet5 libkf5xmlgui-bin
libkf5xmlgui-data
  libkf5xmlgui5 libkwalletbackend5-5 libobjc-6-dev libokteta2core2
libokteta2gui2 libphonon4qt5-4 libprocesscore7 libprocessui7
libqca-qt5-2 libqca-qt5-2-plugins libssh-4 phonon4qt5 phonon4qt5-backend-vlc
  sonnet-plugins
The following packages have been kept back:
  kdevelop libboost-date-time-dev libboost-filesystem-dev
libboost-program-options-dev libboost-regex-dev libboost-system-dev
0 upgraded, 80 newly installed, 0 to remove and 6 not upgraded.
Need to get 20.9 MB of archives.
After this operation, 104 MB of additional disk space will be used.
Do you want to continue? [Y/n]



Bug#726174: apt: APT::Get::Upgrade-Allow-New installs new packages when depending package isn't upgraded

2016-04-08 Thread Felipe Sateler
On Wed, 4 Jun 2014 16:22:04 -0400 Felipe Sateler wrote:
> James McCoy wrote:
>
> > If a package is pinned to prevent an upgrade, but the candidate version
> > has new dependencies, apt will install those even though the depending
> > package isn't being upgraded.
>
> This also happens when a package cannot be upgraded due to dependency
> conflicts. If package 'ugrademe' has a conflict and cannot be installed, it
> will still pull in the new dependencies.
>
> Attached is a test case of this behavior.
>
> Adding the --auto-remove option makes the test pass, FWIW.

It seems the bug has been fixed in the meantime, or at least the
version this testcase tests. It now passes (as of 08407b8).


Saludos



Bug#726174: apt: APT::Get::Upgrade-Allow-New installs new packages when depending package isn't upgraded

2014-06-04 Thread Felipe Sateler
James McCoy wrote:

> If a package is pinned to prevent an upgrade, but the candidate version
> has new dependencies, apt will install those even though the depending
> package isn't being upgraded.

This also happens when a package cannot be upgraded due to dependency
conflicts. If package 'ugrademe' has a conflict and cannot be installed, it
will still pull in the new dependencies.

Attached is a test case of this behavior.

Adding the --auto-remove option makes the test pass, FWIW.

-- 

Saludos,
Felipe Sateler


test-bug-726174-allow-upgrade-installs-new-without-upgrade
Description: Binary data


Bug#726174: apt: APT::Get::Upgrade-Allow-New installs new packages when depending package isn't upgraded

2014-05-30 Thread Felipe Sateler
On Fri, May 30, 2014 at 5:22 PM, Felipe Sateler  wrote:
> Package: apt
> Version: 1.0.3
> Followup-For: Bug #726174
>
>> If a package is pinned to prevent an upgrade, but the candidate version
>> has new dependencies, apt will install those even though the depending
>> package isn't being upgraded.
>
> The same thing happens when a package cannot be upgraded due to
> dependency issues. For example:
>
> Attached is a test case I managed to come up with. Note that liba2 is
> installed even though a ends up not being upgraded.
>
> Note also that the problem is not exhibited if the conflicts is moved
> from package a to liba2, or only added to liba2.

I'll add that the bug is gone if APT::Get::AutomaticRemove=true is set.

-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#726174: apt: APT::Get::Upgrade-Allow-New installs new packages when depending package isn't upgraded

2014-05-30 Thread Felipe Sateler
Package: apt
Version: 1.0.3
Followup-For: Bug #726174

> If a package is pinned to prevent an upgrade, but the candidate version
> has new dependencies, apt will install those even though the depending
> package isn't being upgraded.

The same thing happens when a package cannot be upgraded due to
dependency issues. For example:

Attached is a test case I managed to come up with. Note that liba2 is
installed even though a ends up not being upgraded.

Note also that the problem is not exhibited if the conflicts is moved
from package a to liba2, or only added to liba2.



-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-3\.14-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-3\.14-rc7-amd64$";
APT::NeverAutoRemove:: "^linux-headers-3\.14-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-3\.14-rc7-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-3\.14-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-3\.14-rc7-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-3\.14-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-3\.14-rc7-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-3\.14-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-3\.14-rc7-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-3\.14-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-3\.14-rc7-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-3\.14-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-3\.14-rc7-amd64$";
APT::NeverAutoRemove:: "^.*-modules-3\.14-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-3\.14-rc7-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-3\.14-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-3\.14-rc7-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.14-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.14-rc7-amd64$";
APT::NeverAutoRemove:: "^linux-tools-3\.14-1-amd64$";
APT::NeverAutoRemove:: "^linux-tools-3\.14-rc7-amd64$";
APT::NeverAutoRemove:: "^postgresql-";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Never-MarkAuto-Sections:: "oldlibs";
APT::Never-MarkAuto-Sections:: "restricted/oldlibs";
APT::Never-MarkAuto-Sections:: "universe/oldlibs";
APT::Never-MarkAuto-Sections:: "multiverse/oldlibs";
APT::Periodic "";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "0";
APT::Periodic::AutocleanInterval "0";
APT::Update "";
APT::Update::Post-Invoke "";
APT::Update::Post-Invoke:: "touch /var/lib/apt/periodic/update-success-stamp 
2>/dev/null || true";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "[ ! -f /var/run/dbus/system_bus_socket ] || 
/usr/bin/dbus-send --system --dest=org.debian.apt --type=signal /org/debian/apt 
org.debian.apt.CacheChanged || true";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Archives "";
APT::Archives::MaxAge "30";
APT::Archives::MinAge "2";
APT::Archives::MaxSize "500";
APT::Get "";
APT::Get::Upgrade-Allow-New "true";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "1";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "2";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-9n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compress

Bug#726174: apt: APT::Get::Upgrade-Allow-New installs new packages when depending package isn't upgraded

2013-10-12 Thread James McCoy
Package: apt
Version: 0.9.12
Severity: normal

If a package is pinned to prevent an upgrade, but the candidate version
has new dependencies, apt will install those even though the depending
package isn't being upgraded.  For example,

Package: foo
Version: 1
Depends: bar
Pin-Priority: 1000

Package: foo
Version: 2
Depends: bar, baz

“apt-get upgrade --with-new-pkgs” will hold back foo but will both
install baz and list it as a package that can be autoremoved.

There may be other situations where this also occurs, since the
MarkInstall of the new depended packages happens before the resolver
determines how to handle the depending package.  This is just the first
situation I encountered.

-- Package-specific info:

-- (/etc/apt/preferences present, but not submitted) --


-- (/etc/apt/sources.list present, but not submitted) --


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apt depends on:
ii  debian-archive-keyring  2012.4
ii  gnupg   1.4.15-1
ii  libapt-pkg4.12  0.9.12
ii  libc6   2.17-93
ii  libgcc1 1:4.8.1-10
ii  libstdc++6  4.8.1-10

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc 
ii  aptitude0.6.8.2-1.2
ii  dpkg-dev1.17.1
ii  python-apt  0.8.9.1+b1
ii  xz-utils5.1.1alpha+20120614-2

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org