Bug#756816: apt: apt-get upgrade packagename should not set packagename to manually installed

2014-08-15 Thread David Kalnischkies
On Sat, Aug 02, 2014 at 06:43:00PM +0200, Axel Beckert wrote: David Kalnischkies wrote: When doing dist-upgrades from oldstable to stable, I do them in very small bits, so that no service has a downtime longer than necessary. One of these steps usually includes bigger bunches of

Bug#756816: apt: apt-get upgrade packagename should not set packagename to manually installed

2014-08-07 Thread Adam D. Barratt
On 2014-08-02 17:43, Axel Beckert wrote: Hi David, David Kalnischkies wrote: [...] It is also a remark on how people think they have installed a security fix by installing pkgA, while the fix is actually in libobscureA… O.o While I can imagine that people don't exactly know in which

Bug#756816: apt: apt-get upgrade packagename should not set packagename to manually installed

2014-08-02 Thread David Kalnischkies
Control: retitle -1 document apt(-get) (dist-)upgrade pkga pkgb- On Sat, Aug 02, 2014 at 02:02:50AM +0200, Axel Beckert wrote: it seems that -- despite the documentation suggests otherwise -- you now can pass package names as parameter to apt-get upgrade and it does what you expect: Try to

Bug#756816: apt: apt-get upgrade packagename should not set packagename to manually installed

2014-08-02 Thread Julian Andres Klode
On Sat, Aug 2, 2014 at 12:20 PM, David Kalnischkies da...@kalnischkies.de wrote: Well, there is apts usual reason: If you care enough to mention the package explicitly on the commandline, you properly don't want apt to suggest its removal later on. I can't say I am a huge fan of that, but it

Bug#756816: apt: apt-get upgrade packagename should not set packagename to manually installed

2014-08-02 Thread Axel Beckert
Hi David, thanks for the explanations. David Kalnischkies wrote: Control: retitle -1 document apt(-get) (dist-)upgrade pkga pkgb- Yeah, I would have done that after your mails if you wouldn't have done that. JFTR: I looked IIRC in the man-page for apt-get, maybe also in the one for apt. On

Bug#756816: apt: apt-get upgrade packagename should not set packagename to manually installed

2014-08-02 Thread David Kalnischkies
On Sat, Aug 02, 2014 at 02:02:50AM +0200, Axel Beckert wrote: But it also seems to set the given package to manually installed for which there is no reason at all: Well, there is apts usual reason: If you care enough to mention the package explicitly on the commandline, you properly

Bug#756816: apt: apt-get upgrade packagename should not set packagename to manually installed

2014-08-02 Thread Axel Beckert
Hi David, David Kalnischkies wrote: When doing dist-upgrades from oldstable to stable, I do them in very small bits, so that no service has a downtime longer than necessary. One of these steps usually includes bigger bunches of libsomething packages which I surely never want to have the

Bug#756816: apt: apt-get upgrade packagename should not set packagename to manually installed

2014-08-01 Thread Axel Beckert
Package: apt Version: 1.1~exp2 Severity: normal Dear APT Developers, it seems that -- despite the documentation suggests otherwise -- you now can pass package names as parameter to apt-get upgrade and it does what you expect: Try to upgrade only that package. But it also seems to set the given