Sven Joachim wrote:
> On 2011-01-24 23:38 +0100, Jonathan Nieder wrote:
>> Rather than forcing the removal or upgrade of various info browsers
>> before dpkg, let dpkg provide the install-info functionality for
>> another release. Other packages will still depend on install-info
>> directly so th
On Mon, Jan 24, 2011 at 16:38:23 -0600, Jonathan Nieder wrote:
> Rather than forcing the removal or upgrade of various info browsers
> before dpkg, let dpkg provide the install-info functionality for
> another release. Other packages will still depend on install-info
> directly so the dependency
On 2011-01-24 23:38 +0100, Jonathan Nieder wrote:
> Rather than forcing the removal or upgrade of various info browsers
> before dpkg, let dpkg provide the install-info functionality for
> another release. Other packages will still depend on install-info
> directly so the dependency can be droppe
Rather than forcing the removal or upgrade of various info browsers
before dpkg, let dpkg provide the install-info functionality for
another release. Other packages will still depend on install-info
directly so the dependency can be dropped in wheezy.
The cost is around 256 KiB.
Signed-off-by: J
Julien Cristau wrote:
> On Mon, Jan 24, 2011 at 21:37:01 +0100, Sven Joachim wrote:
>> I wonder whether the Breaks against the emacs2[12] packages need to be
>> taken out as well. In a chroot the upgrade process removes emacs and
>> its dependencies:
>
> Possibly the breaks is a bad idea for anyt
On Mon, Jan 24, 2011 at 21:37:01 +0100, Sven Joachim wrote:
> Hi,
>
> I wonder whether the Breaks against the emacs2[12] packages need to be
> taken out as well. In a chroot the upgrade process removes emacs and
> its dependencies:
>
Possibly the breaks is a bad idea for anything that's more th
Hi,
I wonder whether the Breaks against the emacs2[12] packages need to be
taken out as well. In a chroot the upgrade process removes emacs and
its dependencies:
,
| # LANG=C apt-get install udev
| Reading package lists... Done
| Building dependency tree
| Reading state information...
> You installed a version of menu without triggers support, is that what you
> said?
No - I deinstalled menu and noticed the triggers remained.
> Or are you referring to installation of another random package that
> activated those triggers?
No - there is another package, unrelated to menu, unre
Hi,
On Mon, 24 Jan 2011, Peter van Dijk wrote:
> in short: removing a package that has requested File triggers, does not
> remove those triggers from /var/lib/dpkg/triggers/File. Is this intended
> behaviour?
I also noticed this recently (with some test-suite work), and it's true
for named trigge
Hello,
in short: removing a package that has requested File triggers, does not remove
those triggers from /var/lib/dpkg/triggers/File. Is this intended behaviour?
In long: installing the 'menu' package (tested on Debian 5 and Ubuntu 10.04)
causes three triggers to end up in /var/lib/dpkg/trigge
tag 610991 pending
thanks
Hello,
Bug #610991 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:
http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=f589a03
---
commit f589a03c6fcd9360d00cb4b084d55704c3c8746f
Aut
Processing commands for cont...@bugs.debian.org:
> tag 610991 pending
Bug #610991 [dpkg] lenny->squeeze: kde metapackages get removed by "apt-get
install udev"
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
610991: http://bugs.debian.org/cg
Processing commands for cont...@bugs.debian.org:
> severity 610991 serious
Bug #610991 [dpkg] lenny->squeeze: kde metapackages get removed by "apt-get
install udev"
Severity set to 'serious' from 'normal'
> found 610991 1.15.8.8
Bug #610991 [dpkg] lenny->squeeze: kde metapackages get removed by
Processing commands for cont...@bugs.debian.org:
> found 525160 dpkg/1.15.8.8
Bug #525160 [dpkg] Can't remove old triggers
Bug Marked as found in versions dpkg/1.15.8.8.
> quit
Stopping processing here.
Please contact me if you need assistance.
--
525160: http://bugs.debian.org/cgi-bin/bugreport
found 525160 dpkg/1.15.8.8
quit
Raphael Hertzog wrote:
> On Mon, 24 Jan 2011, Peter van Dijk wrote:
>> However, removing+purging menu does not remove those triggers. Is this
>> intended behaviour? I'm asking because in a situation with a non-Debian
>> package, I installed a version without trigge
Processing commands for cont...@bugs.debian.org:
> clone 610968 -1
Bug#610968: lenny->squeeze: kde metapackages get removed by "apt-get install
udev"
Bug 610968 cloned as bug 610991.
> reassign -1 dpkg
Bug #610991 [upgrade-reports] lenny->squeeze: kde metapackages get removed by
"apt-get instal
Raphael Hertzog wrote:
> --path-include/exclude apply for "installation" of packages
> (i.e. dpkg's operations) and not for the other operations delegated
> to dpkg-deb.
>
> The opposite can be also very misleading... suppose you have a few
> --path-* options in /etc/dpkg.cfg and you want to extrac
Package: dpkg
Version: 1.15.8.7
Severity: minor
File: /usr/bin/dpkg
I wanted to run logcheck on my centralized logging server, to which
syslog messages are sent. Further, I wanted to see this with the
logcheck exclusions provided by individual packages. To this end, I
fetched the relevant packag
Hi,
On Mon, 24 Jan 2011, Trent W. Buck wrote:
> I wanted to run logcheck on my centralized logging server, to which
> syslog messages are sent. Further, I wanted to see this with the
> logcheck exclusions provided by individual packages. To this end, I
> fetched the relevant packages and from th
19 matches
Mail list logo
