[DPKG] emacsen-common package not configured before a2ps despite Depends

[Debian Bug Importer]

Automatically imported from Debian bug report #294895 http://bugs.debian.org/294895

[Rodrigo Tadeu Claro (rlinux)]

Hi,

I am sending patch for its package. I wait that this decides the BUG and
that this package is in sarge. The archive control was modified by
understanding that in this case pre-depends cannot be applied. I made
the installation and removal of the package and got success.

Regards,

--
Rodrigo Tadeu Claro <email address hidden>
RLINUX Solutions

[Frank Küster (frank-kuesterei)]

Richard Lewis <email address hidden> wrote:

> When doing a "apt-get dist-upgrade" (from version 1:4.13b-4)
> I got the following error
>
> dpkg: dependency problems prevent configuration of a2ps:
> a2ps depends on emacsen-common; however:
> Package emacsen-common is not configured yet.
> dpkg: error processing a2ps (--configure):
> dependency problems - leaving unconfigured
>
> re-running "apt-get dist-upgrade" fixed things.
> emacsen-common was upgraded from 1.4.15 -> 1.4.16

Richard, do you remember any error messages prior to this? The most
likely cause for this error is that dpkg tried to configure
emacsen-common first (as dictated by the declared dependencies), but
failed for some reason.

Rodrigo Tadeu Claro <email address hidden> wrote:

> I am sending patch for its package. I wait that this decides the BUG and
> that this package is in sarge. The archive control was modified by
> understanding that in this case pre-depends cannot be applied. I made
> the installation and removal of the package and got success.

Success only because you accidently had emacsen-common installed. It is
used in a2ps' postinst script, and therefore it must be installed and set
up before this postinst script is run.

Therefore a2ps needs a "Depends: emacsen-common". But in fact there is
no need for a Pre-depends - it doesn't even have a preinst file, and I
have no idea how it could "hamper the ability of the system to continue
with any upgrade", as Policy says.

Regards, Frank

--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer

[Lars Wirzenius (liw-iki)]

I tried to reproduce the bug with upgrading a2ps, but failed. What I
did: Before each test, on a sarge machine, with only the base system
installed, I installed the old versions of a2ps (1:4.13b-4) and
emacsen-common (1.4.15). Also depdendencies of these, from current
sarge.

The tests:

* dist-upgrading both to the current sarge versions (1:4:13b-4.3 and
1.4.16). No problems.

* Installing only the current sarge version of a2ps with the old version
of emacsen-common. Again, no problems.

* Unpacking the current sarge version of emacsen-common, editing its
postinst to fail (exit 1 at the end), then dist-upgrading. As expected,
the configure phase of emacsen-common failed. apt-get didn't even try to
upgrade a2ps, so the problem was not repeated. Fixing the postinst back
to working and doing a dist-upgrade again upgraded both packages
properly.

I played around with the system in other ways as well, but couldn't get
the problem to appear. I also don't know of a situation where apt-get
will run dpkg on a package before its (pre-)dependencies have been
fixed, but admittedly my knowledge of the inner workings of apt-get are
somewhat vague.

I propose, therefore, that what happened may have been a fluke or caused
by something else having slighly broken apt-get during the dist-upgrade
run. This would then make the problem unreproducible and probably
unfixable.

(I'm not the maintainer of the package, I'm merely having a look at the
release critical bugs for Debian and seeing if I can reproduce or
otherwise help fix them.)

[Steve Langasek (vorlon)]

tags 294895 unreproducible
reassign 294895 emacsen-common
severity 294895 important
thanks

[Richard Lewis (debian-rtf)]

Frank Küster writes:

>> When doing a "apt-get dist-upgrade" (from version 1:4.13b-4)
>> I got the following error
>>
>> dpkg: dependency problems prevent configuration of a2ps:
>> a2ps depends on emacsen-common; however:
>> Package emacsen-common is not configured yet.
>> dpkg: error processing a2ps (--configure):
>> dependency problems - leaving unconfigured
>>
>> re-running "apt-get dist-upgrade" fixed things.
>> emacsen-common was upgraded from 1.4.15 -> 1.4.16
>
> Richard, do you remember any error messages prior to this? The most
> likely cause for this error is that dpkg tried to configure
> emacsen-common first (as dictated by the declared dependencies), but
> failed for some reason.
>

no errors were displayed. I've got a transcript of the whole upgrade
(both the first run that gave the error, and the second that
succeeded) which I could provide if needed.

[Frank Küster (frank-kuesterei)]

Richard Lewis <email address hidden> wrote:

> no errors were displayed. I've got a transcript of the whole upgrade
> (both the first run that gave the error, and the second that
> succeeded) which I could provide if needed.

Yes, it would be very good if you could send the transcript (Cc to me,
please).

Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer

[Richard Lewis (debian-rtf)]

<email address hidden> (Frank Küster) writes:

> Richard Lewis <email address hidden> wrote:
>
>> no errors were displayed. I've got a transcript of the whole upgrade
>> (both the first run that gave the error, and the second that
>> succeeded) which I could provide if needed.
>
> Yes, it would be very good if you could send the transcript (Cc to me,
> please).

(I hope this mail has the right people in To/CC)

I've put the files at

www.rtf.org.uk/tmp/a2ps-bug/typescript.a2ps-prob-first-attempt--2005-02-12.bz2

and

www.rtf.org.uk/tmp/a2ps-bug/typescript.a2ps-prob-second-attempt--2005-02-12.bz2

The first-attempt was what was shown on "apt-get
dist-upgrade", which gave the error, the second-attempt succeeded
without further intervention from me.

[Frank Küster (frank-debian)]

reassign 294895 dpkg
retitle 294895 dpkg: Tries to configure in the wrong order
thanks

Richard Lewis <email address hidden> wrote:

> I've put the files at
>
> www.rtf.org.uk/tmp/a2ps-bug/typescript.a2ps-prob-first-attempt--2005-02-12.bz2
>
> and
>
> www.rtf.org.uk/tmp/a2ps-bug/typescript.a2ps-prob-second-attempt--2005-02-12.bz2
>
> The first-attempt was what was shown on "apt-get
> dist-upgrade", which gave the error, the second-attempt succeeded
> without further intervention from me.

Thank you. This clearly shows that there was no attempt to configure
emacsen-common before giving the error message about a2ps:

$ egrep 'emacsen-common|a2ps' typescript.a2ps-prob-first-attempt--2005-02-12
  a2ps ace-of-penguins acpid alsa-base alsa-utils anjuta anjuta-common apache-common apache-utils apt
  dselect dvidvi dvipng emacs-goodies-el emacsen-common esound esound-clients esound-common evolution
grave bugs of emacsen-common (1.4.15 -> 1.4.16) <done>
 xpdf-reader(1 bug), strace(1 bug), libgtk2.0-0(1 bug), mysql-server(2 bugs), vorbis-tools(1 bug), login(1 bug), openoffice.org(1 bug), xine-ui(1 bug), apt(1 bug), mozilla-browser(1 bug), xfs(1 bug), gnupg(1 bug), alsa-base(1 bug), libgtk2.0-bin(1 bug), kernel-package(1 bug), emacsen-common(1 bug), initrd-tools(2 bugs), dillo(1 bug), libxslt1-dev(1 bug), udev(1 bug), gdm(1 bug), reportbug(1 bug), gcompris(1 bug), synaptic(1 bug), debconf(1 bug), perl(2 bugs)
Preparing to replace a2ps 1:4.13b-4 (using .../a2ps_1%3a4.13b-4.3_i386.deb) ...
remove/a2ps: purging byte-compiled files for emacs21
Unpacking replacement a2ps ...
Preparing to replace emacsen-common 1.4.15 (using .../emacsen-common_1.4.16_all.deb) ...
emacsen-common: Handling removal of emacsen flavor emacs
emacsen-common: Handling removal of emacsen flavor emacs21
emacsen-common: purging byte-compiled files for emacs21
Unpacking replacement emacsen-common ...
emacsen-common: purging byte-compiled files for emacs21
dpkg: dependency problems prevent configuration of a2ps:
 a2ps depends on emacsen-common; however:
  Package emacsen-common is not configured yet.
dpkg: error processing a2ps (--configure):
 a2ps
frank@alhambra:~/src/packages_for_mydebwork$

Richard, will the files be available constantly at this place? Sometimes
dpkg bugs take long until they are investigated. If not, I suggest that
you post the files to the bug address as attachments.

Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer

[Scott James Remnant (Canonical) (canonical-scott)]

# Automatically generated email from bts, devscripts version 2.8.6
retitle 294895 [DPKG] emacsen-common package not configured before a2ps despite Depends
tags 294895 - unreproducible
severity 294895 serious

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #294895 http://bugs.debian.org/294895

[Debian Bug Importer (debzilla)]

Message-Id: <E1CzrYY-0007sd-2j@stack>
Date: Sat, 12 Feb 2005 07:19:05 +0000
From: Richard Lewis <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: dependency problems prevent configuration of a2ps

Package: a2ps
Version: 1:4.13b-4.3
Severity: grave
Justification: renders package unupgradeable

(I hope the severity is appropriate; it's not exactly hard to fix the
problem but clearly something needs to be fixed)

When doing a "apt-get dist-upgrade" (from version 1:4.13b-4)
I got the following error

dpkg: dependency problems prevent configuration of a2ps:
 a2ps depends on emacsen-common; however:
   Package emacsen-common is not configured yet.
   dpkg: error processing a2ps (--configure):
    dependency problems - leaving unconfigured

re-running "apt-get dist-upgrade" fixed things.
emacsen-common was upgraded from 1.4.15 -> 1.4.16

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-2005-01-22
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages a2ps depends on:
ii emacsen-common 1.4.16 Common facilities for all emacsen
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libpaper1 1.1.14-3 Library for handling paper charact

-- no debconf information

[Debian Bug Importer (debzilla)]

Message-Id: <1108683856.4531.7.camel@rlinux-note>
Date: Thu, 17 Feb 2005 21:44:15 -0200
From: Rodrigo Tadeu Claro <email address hidden>
To: <email address hidden>
Subject: Patch for a2ps

--=-dAwL0pvBdkvPdAm86obG
Content-Type: multipart/mixed; boundary="=-OktPjQcZe3mc59VU3g/X"

--=-OktPjQcZe3mc59VU3g/X
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi,

I am sending patch for its package. I wait that this decides the BUG and
that this package is in sarge. The archive control was modified by
understanding that in this case pre-depends cannot be applied. I made
the installation and removal of the package and got success.

Regards,

--=20
Rodrigo Tadeu Claro <email address hidden>
RLINUX Solutions

--=-OktPjQcZe3mc59VU3g/X
Content-Disposition: attachment; filename=control
Content-Type: text/plain; name=control; charset=ISO-8859-1
Content-Transfer-Encoding: base64

U291cmNlOiBhMnBzDQpTZWN0aW9uOiB0ZXh0DQpQcmlvcml0eTogb3B0aW9uYWwNCk1haW50YWlu
ZXI6IE1hc2F5dWtpIEhhdHRhIChtaGF0dGEpIDxtaGF0dGFAZGViaWFuLm9yZz4NCkJ1aWxkLURl
cGVuZHM6IGF1dG90b29scy1kZXYsIGJpc29uLCBiemlwMiwgZGViaGVscGVyICg+PiA0LjAuMCks
IGRwYXRjaCwgZW1hY3MyMS1ub3ggfCBlbWFjc2VuLCBlbWFjc2VuLWNvbW1vbiwgZmlsZSwgZmxl
eCwgZ3MtY29tbW9uLCBncm9mZi1iYXNlLCBndiwgaHRtbDJwcywgaW1hZ2VtYWdpY2ssIGxpYnBh
cGVyLWRldiwgbHByLCBwc3V0aWxzLCB0ZXRleC1iaW4sIHRleGluZm8NClN0YW5kYXJkcy1WZXJz
aW9uOiAzLjYuMQ0KDQpQYWNrYWdlOiBhMnBzDQpBcmNoaXRlY3R1cmU6IGFueQ0KRGVwZW5kczog
JHtzaGxpYnM6RGVwZW5kc30NClJlY29tbWVuZHM6IGJ6aXAyLCBscHIgfCBjdXBzeXMtY2xpZW50
LCBwc3V0aWxzLCB3ZGlmZg0KU3VnZ2VzdHM6IGVtYWNzMjEtbm94IHwgZW1hY3NlbiwgZ3JvZmYs
IGdzLWNvbW1vbiwgZ3YsIGh0bWwycHMsIGltYWdlbWFnaWNrLCB0ZXRleC1iaW4sIHQxLWN5cmls
bGljDQpEZXNjcmlwdGlvbjogR05VIGEycHMgLSAnQW55dGhpbmcgdG8gUG9zdFNjcmlwdCcgY29u
dmVydGVyIGFuZCBwcmV0dHktcHJpbnRlcg0KIEdOVSBhMnBzIGNvbnZlcnRzIGZpbGVzIGludG8g
UG9zdFNjcmlwdCBmb3IgcHJpbnRpbmcgb3Igdmlld2luZy4gSXQgdXNlcyBhDQogbmljZSBkZWZh
dWx0IGZvcm1hdCwgdXN1YWxseSB0d28gcGFnZXMgb24gZWFjaCBwaHlzaWNhbCBwYWdlLCBib3Jk
ZXJzDQogc3Vycm91bmRpbmcgcGFnZXMsIGhlYWRlcnMgd2l0aCB1c2VmdWwgaW5mb3JtYXRpb24g
KHBhZ2UgbnVtYmVyLCBwcmludGluZw0KIGRhdGUsIGZpbGUgbmFtZSBvciBzdXBwbGllZCBoZWFk
ZXIpLCBsaW5lIG51bWJlcmluZywgc3ltYm9sIHN1YnN0aXR1dGlvbg0KIGFzIHdlbGwgYXMgcHJl
dHR5IHByaW50aW5nIGZvciBhIHdpZGUgcmFuZ2Ugb2YgcHJvZ3JhbW1pbmcgbGFuZ3VhZ2VzLg0K
IC4NCiBIaXN0b3JpY2FsbHksIGEycHMgc3RhcnRlZCBhcyBhIHRleHQgdG8gUG9zdFNjcmlwdCBj
b252ZXJ0ZXIsIGJ1dCB0aGFua3MNCiB0byBwb3dlcmZ1bCBkZWxlZ2F0aW9ucyBpdCBpcyBhYmxl
IHRvIGxldCB5b3UgdXNlIGl0IGZvciBhbnkga2luZCBvZiBmaWxlcywNCiBpZSBpdCBjYW4gYWxz
byBkaWdlc3QgbWFudWFsIHBhZ2VzLCBkdmkgZmlsZXMsIHRleGluZm8sIC4uLi4NCiAuDQogQW1v
bmcgdGhlIG90aGVyIG1vc3Qgbm90aWNlYWJsZSBmZWF0dXJlcyBvZiBhMnBzIGFyZToNCiAgLSB2
YXJpb3VzIGVuY29kaW5ncyAoYWxsIHRoZSBMYXRpbnMgYW5kIG90aGVycyksDQogIC0gdmFyaW91
cyBmb250cyAoYXV0b21hdGljIGZvbnQgZG93biBsb2FkaW5nKSwNCiAgLSB2YXJpb3VzIG1lZGlh
cywNCiAgLSB2YXJpb3VzIHByaW50ZXIgaW50ZXJmYWNlcywNCiAgLSB2YXJpb3VzIG91dHB1dCBz
dHlsZXMsDQogIC0gdmFyaW91cyBwcm9ncmFtbWluZyBsYW5ndWFnZXMsDQogIC0gdmFyaW91cyBo
ZWxwaW5nIGFwcGxpY2F0aW9ucywNCiAgLSBhbmQgdmFyaW91cyBzcG9rZW4gbGFuZ3VhZ2VzLg0K
DQoNCg0KDQoNCg0K

--=-OktPjQcZe3mc59VU3g/X--

--=-dAwL0pvBdkvPdAm86obG
Content-Type: application/pgp-signature; name=signature.asc
Content-Descrip...

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 18 Feb 2005 16:59:12 +0100
From: <email address hidden> (=?iso-8859-1?q?Frank_K=FCster?=)
To: Rodrigo Tadeu Claro <email address hidden>
Cc: <email address hidden>, Richard Lewis <email address hidden>, <email address hidden>
Subject: Re: Patch for a2ps

Richard Lewis <email address hidden> wrote:

> When doing a "apt-get dist-upgrade" (from version 1:4.13b-4)
> I got the following error
>
> dpkg: dependency problems prevent configuration of a2ps:
> a2ps depends on emacsen-common; however:
> Package emacsen-common is not configured yet.
> dpkg: error processing a2ps (--configure):
> dependency problems - leaving unconfigured
>=20=20=20=20=20
> re-running "apt-get dist-upgrade" fixed things.
> emacsen-common was upgraded from 1.4.15 -> 1.4.16

Richard, do you remember any error messages prior to this? The most
likely cause for this error is that dpkg tried to configure
emacsen-common first (as dictated by the declared dependencies), but
failed for some reason.=20

Rodrigo Tadeu Claro <email address hidden> wrote:

> I am sending patch for its package. I wait that this decides the BUG and
> that this package is in sarge. The archive control was modified by
> understanding that in this case pre-depends cannot be applied. I made
> the installation and removal of the package and got success.

Success only because you accidently had emacsen-common installed. It is
used in a2ps' postinst script, and therefore it must be installed and set
up before this postinst script is run.

Therefore a2ps needs a "Depends: emacsen-common". But in fact there is
no need for a Pre-depends - it doesn't even have a preinst file, and I
have no idea how it could "hamper the ability of the system to continue
with any upgrade", as Policy says.

Regards, Frank

--=20
Frank K=FCster
Inst. f. Biochemie der Univ. Z=FCrich
Debian Developer

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Tue, 22 Feb 2005 09:18:27 +0200
From: Lars Wirzenius <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: a2ps: couldn't reproduce upgrade problem

I tried to reproduce the bug with upgrading a2ps, but failed. What I
did: Before each test, on a sarge machine, with only the base system
installed, I installed the old versions of a2ps (1:4.13b-4) and
emacsen-common (1.4.15). Also depdendencies of these, from current
sarge.

The tests:

* dist-upgrading both to the current sarge versions (1:4:13b-4.3 and
1.4.16). No problems.

* Installing only the current sarge version of a2ps with the old version
of emacsen-common. Again, no problems.

* Unpacking the current sarge version of emacsen-common, editing its
postinst to fail (exit 1 at the end), then dist-upgrading. As expected,
the configure phase of emacsen-common failed. apt-get didn't even try to
upgrade a2ps, so the problem was not repeated. Fixing the postinst back
to working and doing a dist-upgrade again upgraded both packages
properly.

I played around with the system in other ways as well, but couldn't get
the problem to appear. I also don't know of a situation where apt-get
will run dpkg on a package before its (pre-)dependencies have been
fixed, but admittedly my knowledge of the inner workings of apt-get are
somewhat vague.

I propose, therefore, that what happened may have been a fluke or caused
by something else having slighly broken apt-get during the dist-upgrade
run. This would then make the problem unreproducible and probably
unfixable.

(I'm not the maintainer of the package, I'm merely having a look at the
release critical bugs for Debian and seeing if I can reproduce or
otherwise help fix them.)

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 26 Feb 2005 01:11:02 -0800
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: unexplained install failure, downgrading/reassigning

tags 294895 unreproducible
reassign 294895 emacsen-common
severity 294895 important
thanks

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 23 Feb 2005 01:54:32 +0000
From: Richard Lewis <email address hidden>
To: <email address hidden> (=?iso-8859-1?q?Frank_K=FCster?=)
Cc: <email address hidden>, <email address hidden>,
   <email address hidden>
Subject: Re: Patch for a2ps

Frank K=FCster writes:

>> When doing a "apt-get dist-upgrade" (from version 1:4.13b-4)
>> I got the following error
>>
>> dpkg: dependency problems prevent configuration of a2ps:
>> a2ps depends on emacsen-common; however:
>> Package emacsen-common is not configured yet.
>> dpkg: error processing a2ps (--configure):
>> dependency problems - leaving unconfigured
>>=20=20=20=20=20
>> re-running "apt-get dist-upgrade" fixed things.
>> emacsen-common was upgraded from 1.4.15 -> 1.4.16
>
> Richard, do you remember any error messages prior to this? The most
> likely cause for this error is that dpkg tried to configure
> emacsen-common first (as dictated by the declared dependencies), but
> failed for some reason.=20
>

no errors were displayed. I've got a transcript of the whole upgrade
(both the first run that gave the error, and the second that
succeeded) which I could provide if needed.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 28 Feb 2005 11:07:04 +0100
From: <email address hidden> (=?iso-8859-1?q?Frank_K=FCster?=)
To: Richard Lewis <email address hidden>
Cc: <email address hidden>, <email address hidden>,
        <email address hidden>
Subject: Re: Patch for a2ps

Richard Lewis <email address hidden> wrote:

> no errors were displayed. I've got a transcript of the whole upgrade
> (both the first run that gave the error, and the second that
> succeeded) which I could provide if needed.

Yes, it would be very good if you could send the transcript (Cc to me,
please).=20

Regards, Frank
--=20
Frank K=FCster
Inst. f. Biochemie der Univ. Z=FCrich
Debian Developer

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 07 Mar 2005 02:53:49 +0000
From: Richard Lewis <email address hidden>
To: <email address hidden> (=?iso-8859-1?q?Frank_K=FCster?=)
Cc: <email address hidden>, <email address hidden>,
   <email address hidden>
Subject: Re: Patch for a2ps

<email address hidden> (Frank K=FCster) writes:

> Richard Lewis <email address hidden> wrote:
>
>> no errors were displayed. I've got a transcript of the whole upgrade
>> (both the first run that gave the error, and the second that
>> succeeded) which I could provide if needed.
>
> Yes, it would be very good if you could send the transcript (Cc to me,
> please).=20

(I hope this mail has the right people in To/CC)

I've put the files at

www.rtf.org.uk/tmp/a2ps-bug/typescript.a2ps-prob-first-attempt--2005-02-12.=
bz2

and

www.rtf.org.uk/tmp/a2ps-bug/typescript.a2ps-prob-second-attempt--2005-02-12=
.bz2

The first-attempt was what was shown on "apt-get
dist-upgrade", which gave the error, the second-attempt succeeded
without further intervention from me.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 11 Mar 2005 12:20:50 +0100
From: =?iso-8859-1?q?Frank_K=FCster?= <email address hidden>
To: Richard Lewis <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Patch for a2ps

reassign 294895 dpkg
retitle 294895 dpkg: Tries to configure in the wrong order
thanks

Richard Lewis <email address hidden> wrote:

> I've put the files at
>
> www.rtf.org.uk/tmp/a2ps-bug/typescript.a2ps-prob-first-attempt--2005-02-1=
2.bz2
>
> and
>
> www.rtf.org.uk/tmp/a2ps-bug/typescript.a2ps-prob-second-attempt--2005-02-=
12.bz2
>
> The first-attempt was what was shown on "apt-get
> dist-upgrade", which gave the error, the second-attempt succeeded
> without further intervention from me.

Thank you. This clearly shows that there was no attempt to configure
emacsen-common before giving the error message about a2ps:

$ egrep 'emacsen-common|a2ps' typescript.a2ps-prob-first-attempt--2005-02-1=
2=20
  a2ps ace-of-penguins acpid alsa-base alsa-utils anjuta anjuta-common apac=
he-common apache-utils apt
  dselect dvidvi dvipng emacs-goodies-el emacsen-common esound esound-clien=
ts esound-common evolution
grave bugs of emacsen-common (1.4.15 -> 1.4.16) <done>
 xpdf-reader(1 bug), strace(1 bug), libgtk2.0-0(1 bug), mysql-server(2 bugs=
), vorbis-tools(1 bug), login(1 bug), openoffice.org(1 bug), xine-ui(1 bug)=
, apt(1 bug), mozilla-browser(1 bug), xfs(1 bug), gnupg(1 bug), alsa-base(1=
 bug), libgtk2.0-bin(1 bug), kernel-package(1 bug), emacsen-common(1 bug), =
initrd-tools(2 bugs), dillo(1 bug), libxslt1-dev(1 bug), udev(1 bug), gdm(1=
 bug), reportbug(1 bug), gcompris(1 bug), synaptic(1 bug), debconf(1 bug), =
perl(2 bugs)
Preparing to replace a2ps 1:4.13b-4 (using .../a2ps_1%3a4.13b-4.3_i386.deb)=
 ...
remove/a2ps: purging byte-compiled files for emacs21
Unpacking replacement a2ps ...
Preparing to replace emacsen-common 1.4.15 (using .../emacsen-common_1.4.16=
_all.deb) ...
emacsen-common: Handling removal of emacsen flavor emacs
emacsen-common: Handling removal of emacsen flavor emacs21
emacsen-common: purging byte-compiled files for emacs21
Unpacking replacement emacsen-common ...
emacsen-common: purging byte-compiled files for emacs21
dpkg: dependency problems prevent configuration of a2ps:
 a2ps depends on emacsen-common; however:
  Package emacsen-common is not configured yet.
dpkg: error processing a2ps (--configure):
 a2ps
frank@alhambra:~/src/packages_for_mydebwork$=20

Richard, will the files be available constantly at this place? Sometimes
dpkg bugs take long until they are investigated. If not, I suggest that
you post the files to the bug address as attachments.

Regards, Frank
--=20
Frank K=FCster
Inst. f. Biochemie der Univ. Z=FCrich
Debian Developer

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Fri, 11 Mar 2005 12:11:06 +0000
From: Scott James Remnant <email address hidden>
To: <email address hidden>
Subject: retitle 294895 to [DPKG] emacsen-common package not configured before a2ps despite Depends
 ... ...

# Automatically generated email from bts, devscripts version 2.8.6
retitle 294895 [DPKG] emacsen-common package not configured before a2ps despite Depends
tags 294895 - unreproducible
severity 294895 serious

[Steve Langasek (vorlon)]

Scott,

Is it certain that this is a dpkg bug? I notice that the submitter's
typescript shows he was using apt 0.5.27 when upgrading, which was before
the Dpkg::MaxArgs setting was bumped to 1024 -- the first typescript shows a
total of 640 packages being upgraded, and the second typescript shows 281
packages not fully installed or removed, so perhaps this is a bad dpkg
invocation, not a bug in dpkg itself?

--
Steve Langasek
postmodern programmer

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 12 Mar 2005 02:03:48 -0800
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: Re: [DPKG] emacsen-common package not configured before a2ps despite Depends

--Izn7cH1Com+I3R9J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Scott,

Is it certain that this is a dpkg bug? I notice that the submitter's
typescript shows he was using apt 0.5.27 when upgrading, which was before
the Dpkg::MaxArgs setting was bumped to 1024 -- the first typescript shows a
total of 640 packages being upgraded, and the second typescript shows 281
packages not fully installed or removed, so perhaps this is a bad dpkg
invocation, not a bug in dpkg itself?

--=20
Steve Langasek
postmodern programmer

--Izn7cH1Com+I3R9J
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCMr6BKN6ufymYLloRAiRyAJ0ft6x46/tIRNhoGq4HYkgQuyTqIQCeMpFS
5cXdnNpQUOtxZQUJybDJ5uE=
=Iawq
-----END PGP SIGNATURE-----

--Izn7cH1Com+I3R9J--

[Scott James Remnant (Canonical) (canonical-scott)]

On Sat, 2005-03-12 at 02:03 -0800, Steve Langasek wrote:

> Is it certain that this is a dpkg bug? I notice that the submitter's
> typescript shows he was using apt 0.5.27 when upgrading, which was before
> the Dpkg::MaxArgs setting was bumped to 1024 -- the first typescript shows a
> total of 640 packages being upgraded, and the second typescript shows 281
> packages not fully installed or removed, so perhaps this is a bad dpkg
> invocation, not a bug in dpkg itself?
>
I don't think it's an apt issue, both emacsen-common and a2ps were
passed to dpkg in the same run (they were unpacked within the same
block) -- I need to digest the typescripts a little more, but I'm
tending towards that it is a dpkg bug.

Not in the least because I have a hunch I've seen something similar
myself since a change was made to the depcycle breaker last year.

Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Sat, 12 Mar 2005 18:21:43 +0000
From: Scott James Remnant <email address hidden>
To: <email address hidden>, Steve Langasek <email address hidden>
Subject: Re: Bug#294895: [DPKG] emacsen-common package not configured
 before a2ps despite Depends

--=-UMaxr5XS9L512NGAz6nV
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2005-03-12 at 02:03 -0800, Steve Langasek wrote:

> Is it certain that this is a dpkg bug? I notice that the submitter's
> typescript shows he was using apt 0.5.27 when upgrading, which was before
> the Dpkg::MaxArgs setting was bumped to 1024 -- the first typescript show=
s a
> total of 640 packages being upgraded, and the second typescript shows 281
> packages not fully installed or removed, so perhaps this is a bad dpkg
> invocation, not a bug in dpkg itself?
>=20
I don't think it's an apt issue, both emacsen-common and a2ps were
passed to dpkg in the same run (they were unpacked within the same
block) -- I need to digest the typescripts a little more, but I'm
tending towards that it is a dpkg bug.

Not in the least because I have a hunch I've seen something similar
myself since a change was made to the depcycle breaker last year.

Scott
--=20
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?

--=-UMaxr5XS9L512NGAz6nV
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBCMzM2IexP3IStZ2wRArmKAJ0V3lhYdhkjbyQ9246YIy0tOZQVCACfZipk
SDw+AemEDpp3rHUigJ7pv0I=
=GbnR
-----END PGP SIGNATURE-----

--=-UMaxr5XS9L512NGAz6nV--

[Matt Zimmerman (mdz)]

This does indeed look like the dpkg arg-limit bug in apt, which is was fixed
before Warty released

[Matt Zimmerman (mdz)]

ok, perhaps not :-)

[Scott James Remnant (Canonical) (canonical-scott)]

severity 294895 normal
reassign 294895 apt
thanks

On Fri, 2005-03-11 at 12:20 +0100, Frank Küster wrote:

> Thank you. This clearly shows that there was no attempt to configure
> emacsen-common before giving the error message about a2ps:
>
On closer examination, a2ps and emacsen-common are being installed in
different dpkg invocations. This is an APT problem.

Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?

[Scott James Remnant (Canonical) (canonical-scott)]

# Automatically generated email from bts, devscripts version 2.8.6
retitle 294895 a2ps passed to dpkg before its dependency, emacsen-common

[Scott James Remnant (Canonical) (canonical-scott)]

No, it is; I was a bit tired last night and didn't read the logs close enough --
a2ps and emacsen-common were being done in the same run.

The bug I thought of (in X) turned out to be a bug in that package's postinst as
well; so notwarty.

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Sat, 12 Mar 2005 21:50:36 +0000
From: Scott James Remnant <email address hidden>
To: Frank =?ISO-8859-1?Q?K=FCster?= <email address hidden>
Cc: Richard Lewis <email address hidden>, <email address hidden>
Subject: Re: Patch for a2ps

--=-ZeSnDJqwR9VX5J4mQANA
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

severity 294895 normal
reassign 294895 apt
thanks

On Fri, 2005-03-11 at 12:20 +0100, Frank K=C3=BCster wrote:

> Thank you. This clearly shows that there was no attempt to configure
> emacsen-common before giving the error message about a2ps:
>=20
On closer examination, a2ps and emacsen-common are being installed in
different dpkg invocations. This is an APT problem.

Scott
--=20
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?

--=-ZeSnDJqwR9VX5J4mQANA
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBCM2QrIexP3IStZ2wRAv8aAKCWcRbjqvMTDAGRFlhmoDQNsPPBGQCfWeOI
6PzoW+E//XksksZ4pK6IRzU=
=/+Td
-----END PGP SIGNATURE-----

--=-ZeSnDJqwR9VX5J4mQANA--

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Sat, 12 Mar 2005 22:11:55 +0000
From: Scott James Remnant <email address hidden>
To: <email address hidden>
Subject: retitle 294895 to a2ps passed to dpkg before its dependency, emacsen-common

# Automatically generated email from bts, devscripts version 2.8.6
retitle 294895 a2ps passed to dpkg before its dependency, emacsen-common

[Steve Langasek (vorlon)]

On Sat, Mar 12, 2005 at 09:50:36PM +0000, Scott James Remnant wrote:
> severity 294895 normal
> reassign 294895 apt
> thanks

> On Fri, 2005-03-11 at 12:20 +0100, Frank Küster wrote:

> > Thank you. This clearly shows that there was no attempt to configure
> > emacsen-common before giving the error message about a2ps:

> On closer examination, a2ps and emacsen-common are being installed in
> different dpkg invocations. This is an APT problem.

If this does turn out to be a symptom of the low Dpkg::MaxArgs setting in
woody, this bug should probably be reassigned to upgrade-reports as a
reminder to say something in the sarge release notes about wanting to
upgrade apt first.

--
Steve Langasek
postmodern programmer

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 12 Mar 2005 17:11:50 -0800
From: Steve Langasek <email address hidden>
To: <email address hidden>
Cc: Frank =?iso-8859-1?Q?K=FCster?= <email address hidden>,
 Richard Lewis <email address hidden>
Subject: Re: Bug#294895: Patch for a2ps

--Z8yxTSU1mh2gsre7
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Mar 12, 2005 at 09:50:36PM +0000, Scott James Remnant wrote:
> severity 294895 normal
> reassign 294895 apt
> thanks

> On Fri, 2005-03-11 at 12:20 +0100, Frank K=FCster wrote:

> > Thank you. This clearly shows that there was no attempt to configure
> > emacsen-common before giving the error message about a2ps:

> On closer examination, a2ps and emacsen-common are being installed in
> different dpkg invocations. This is an APT problem.

If this does turn out to be a symptom of the low Dpkg::MaxArgs setting in
woody, this bug should probably be reassigned to upgrade-reports as a
reminder to say something in the sarge release notes about wanting to
upgrade apt first.

--=20
Steve Langasek
postmodern programmer

--Z8yxTSU1mh2gsre7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCM5NSKN6ufymYLloRAr+UAJ9SDvwq492bhHhr5qpXsyCHbfvoEgCgvIYe
fHgxbk19Jn8rhJDVj3/j+zM=
=3M/t
-----END PGP SIGNATURE-----

--Z8yxTSU1mh2gsre7--

[Richard Lewis (richard-lewis-debian)]

# cron-apt (sources.list.d still read)
submitter 449386 !

## really old bugs
# a2ps/apt
submitter 294895 !

# screen
submitter 409398 !
changing submitter

#dtemacs
submitter 280368 !

thanks