fails to configure because gs-common is not configured

Bug #11928 reported by Debian Bug Importer
4
Affects Status Importance Assigned to Milestone
gs-gpl (Debian)
Fix Released
Unknown
gs-gpl (Ubuntu)
Invalid
High
Unassigned

Bug Description

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

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Fri, 14 Jan 2005 14:16:45 -0800
From: Matt Kraai <email address hidden>
To: <email address hidden>
Subject: fails to configure because gs-common is not configured

Package: gs-gpl
Version: 8.01-5
Severity: serious

The Desktop task failed to install while installing Debian because
gs-gpl failed to configure because gs-common was not configured:

 dpkg: dependency problems prevent configuration of gs-gpl:
  gs-gpl depends on gs-common (>= 0.2); however:
   Package gs-common is not configured yet.
 dpkg: error processing gs-gpl (--configure):
  dependency problems - leaving unconfigured

--
Matt

Revision history for this message
In , Frank Lichtenheld (djpig) wrote : tagging 290597

# Automatically generated email from bts, devscripts version 2.8.5
tags 290597 moreinfo

Revision history for this message
In , Frank Lichtenheld (djpig) wrote : Re: Bug#290597: fails to configure because gs-common is not configured

On Fri, Jan 14, 2005 at 02:16:45PM -0800, Matt Kraai wrote:
> The Desktop task failed to install while installing Debian because
> gs-gpl failed to configure because gs-common was not configured:
>
> dpkg: dependency problems prevent configuration of gs-gpl:
> gs-gpl depends on gs-common (>= 0.2); however:
> Package gs-common is not configured yet.
> dpkg: error processing gs-gpl (--configure):
> dependency problems - leaving unconfigured

I don't quite understand how this would be gs-gpl's fault, it's either
gs-common (because of an error during the configuration) or apt/dpkg,
isn't it? Do you have a complete log of the install, I suspect there
was an error during configuring gs-common.

Gruesse,
--
Frank Lichtenheld <email address hidden>
www: http://www.djpig.de/

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Fri, 21 Jan 2005 16:31:55 +0100
From: Frank Lichtenheld <email address hidden>
To: Matt Kraai <email address hidden>, <email address hidden>
Subject: Re: Bug#290597: fails to configure because gs-common is not configured

On Fri, Jan 14, 2005 at 02:16:45PM -0800, Matt Kraai wrote:
> The Desktop task failed to install while installing Debian because
> gs-gpl failed to configure because gs-common was not configured:
>
> dpkg: dependency problems prevent configuration of gs-gpl:
> gs-gpl depends on gs-common (>= 0.2); however:
> Package gs-common is not configured yet.
> dpkg: error processing gs-gpl (--configure):
> dependency problems - leaving unconfigured

I don't quite understand how this would be gs-gpl's fault, it's either
gs-common (because of an error during the configuration) or apt/dpkg,
isn't it? Do you have a complete log of the install, I suspect there
was an error during configuring gs-common.

Gruesse,
--
Frank Lichtenheld <email address hidden>
www: http://www.djpig.de/

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Fri, 21 Jan 2005 16:34:26 +0100
From: Frank Lichtenheld <email address hidden>
To: <email address hidden>
Subject: tagging 290597

# Automatically generated email from bts, devscripts version 2.8.5
tags 290597 moreinfo

Revision history for this message
In , Matt Kraai (kraai-ftbfs) wrote :

On Fri, Jan 21, 2005 at 04:31:55PM +0100, Frank Lichtenheld wrote:
> On Fri, Jan 14, 2005 at 02:16:45PM -0800, Matt Kraai wrote:
> > The Desktop task failed to install while installing Debian because
> > gs-gpl failed to configure because gs-common was not configured:
> >
> > dpkg: dependency problems prevent configuration of gs-gpl:
> > gs-gpl depends on gs-common (>= 0.2); however:
> > Package gs-common is not configured yet.
> > dpkg: error processing gs-gpl (--configure):
> > dependency problems - leaving unconfigured
>
> I don't quite understand how this would be gs-gpl's fault, it's either
> gs-common (because of an error during the configuration) or apt/dpkg,
> isn't it? Do you have a complete log of the install, I suspect there
> was an error during configuring gs-common.

I reported it against gs-gpl because that was what failed to compile.
There appears to be a dependency loop between gs-gpl, gs-common, and
gs.

--
Matt

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Fri, 21 Jan 2005 17:48:28 -0800
From: Matt Kraai <email address hidden>
To: Frank Lichtenheld <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#290597: fails to configure because gs-common is not configured

On Fri, Jan 21, 2005 at 04:31:55PM +0100, Frank Lichtenheld wrote:
> On Fri, Jan 14, 2005 at 02:16:45PM -0800, Matt Kraai wrote:
> > The Desktop task failed to install while installing Debian because
> > gs-gpl failed to configure because gs-common was not configured:
> >
> > dpkg: dependency problems prevent configuration of gs-gpl:
> > gs-gpl depends on gs-common (>= 0.2); however:
> > Package gs-common is not configured yet.
> > dpkg: error processing gs-gpl (--configure):
> > dependency problems - leaving unconfigured
>
> I don't quite understand how this would be gs-gpl's fault, it's either
> gs-common (because of an error during the configuration) or apt/dpkg,
> isn't it? Do you have a complete log of the install, I suspect there
> was an error during configuring gs-common.

I reported it against gs-gpl because that was what failed to compile.
There appears to be a dependency loop between gs-gpl, gs-common, and
gs.

--
Matt

Revision history for this message
In , Frank Lichtenheld (djpig) wrote :

On Fri, Jan 21, 2005 at 05:48:28PM -0800, Matt Kraai wrote:
> On Fri, Jan 21, 2005 at 04:31:55PM +0100, Frank Lichtenheld wrote:
> > I don't quite understand how this would be gs-gpl's fault, it's either
> > gs-common (because of an error during the configuration) or apt/dpkg,
> > isn't it? Do you have a complete log of the install, I suspect there
> > was an error during configuring gs-common.
>
> I reported it against gs-gpl because that was what failed to compile.
> There appears to be a dependency loop between gs-gpl, gs-common, and
> gs.

Ok, now I understand. Although I find it rather normal that gs-gpl
depends on gs-common but rather weird that gs-common in turn depends
on gs. I would therefor propose to reassign the bug to gs-common.

Gruesse,
--
Frank Lichtenheld <email address hidden>
www: http://www.djpig.de/

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sat, 22 Jan 2005 15:02:54 +0100
From: Frank Lichtenheld <email address hidden>
To: Matt Kraai <email address hidden>, <email address hidden>
Subject: Re: Bug#290597: fails to configure because gs-common is not configured

On Fri, Jan 21, 2005 at 05:48:28PM -0800, Matt Kraai wrote:
> On Fri, Jan 21, 2005 at 04:31:55PM +0100, Frank Lichtenheld wrote:
> > I don't quite understand how this would be gs-gpl's fault, it's either
> > gs-common (because of an error during the configuration) or apt/dpkg,
> > isn't it? Do you have a complete log of the install, I suspect there
> > was an error during configuring gs-common.
>
> I reported it against gs-gpl because that was what failed to compile.
> There appears to be a dependency loop between gs-gpl, gs-common, and
> gs.

Ok, now I understand. Although I find it rather normal that gs-gpl
depends on gs-common but rather weird that gs-common in turn depends
on gs. I would therefor propose to reassign the bug to gs-common.

Gruesse,
--
Frank Lichtenheld <email address hidden>
www: http://www.djpig.de/

Revision history for this message
In , Matt Kraai (kraai-ftbfs) wrote :

On Sat, Jan 22, 2005 at 03:02:54PM +0100, Frank Lichtenheld wrote:
> On Fri, Jan 21, 2005 at 05:48:28PM -0800, Matt Kraai wrote:
> > On Fri, Jan 21, 2005 at 04:31:55PM +0100, Frank Lichtenheld wrote:
> > > I don't quite understand how this would be gs-gpl's fault, it's either
> > > gs-common (because of an error during the configuration) or apt/dpkg,
> > > isn't it? Do you have a complete log of the install, I suspect there
> > > was an error during configuring gs-common.
> >
> > I reported it against gs-gpl because that was what failed to compile.

Oops. I meant configure, not compile.

> > There appears to be a dependency loop between gs-gpl, gs-common, and
> > gs.
>
> Ok, now I understand. Although I find it rather normal that gs-gpl
> depends on gs-common but rather weird that gs-common in turn depends
> on gs. I would therefor propose to reassign the bug to gs-common.

That sounds good to me.

--
Matt

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sat, 22 Jan 2005 11:09:30 -0800
From: Matt Kraai <email address hidden>
To: Frank Lichtenheld <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#290597: fails to configure because gs-common is not configured

On Sat, Jan 22, 2005 at 03:02:54PM +0100, Frank Lichtenheld wrote:
> On Fri, Jan 21, 2005 at 05:48:28PM -0800, Matt Kraai wrote:
> > On Fri, Jan 21, 2005 at 04:31:55PM +0100, Frank Lichtenheld wrote:
> > > I don't quite understand how this would be gs-gpl's fault, it's either
> > > gs-common (because of an error during the configuration) or apt/dpkg,
> > > isn't it? Do you have a complete log of the install, I suspect there
> > > was an error during configuring gs-common.
> >
> > I reported it against gs-gpl because that was what failed to compile.

Oops. I meant configure, not compile.

> > There appears to be a dependency loop between gs-gpl, gs-common, and
> > gs.
>
> Ok, now I understand. Although I find it rather normal that gs-gpl
> depends on gs-common but rather weird that gs-common in turn depends
> on gs. I would therefor propose to reassign the bug to gs-common.

That sounds good to me.

--
Matt

Revision history for this message
In , Steve Langasek (vorlon) wrote :

reassign 290597 gs-common
thanks

Matt,

All of the high-level apt tools should be capable of breaking this kind of
dependency loop between gs-gpl and gs-common, so the most apparent reason
for this kind of failure would be that gs-common could not be configured for
reasons other than this dependency loop. I think we really need to see the
output of trying to install gs-common on this system in order to debug this.

Thanks,
--
Steve Langasek
postmodern programmer

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sun, 23 Jan 2005 01:37:03 -0800
From: Steve Langasek <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: fails to configure because gs-common is not configured

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

reassign 290597 gs-common
thanks

Matt,

All of the high-level apt tools should be capable of breaking this kind of
dependency loop between gs-gpl and gs-common, so the most apparent reason
for this kind of failure would be that gs-common could not be configured for
reasons other than this dependency loop. I think we really need to see the
output of trying to install gs-common on this system in order to debug this.

Thanks,
--=20
Steve Langasek
postmodern programmer

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

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

iD8DBQFB83A8KN6ufymYLloRAq9DAJ9zHDi20e4wHfTdr62t9QRLGvFJOACcCxjq
opdlziPmHt8A/C54O3hXkEk=
=KQjO
-----END PGP SIGNATURE-----

--f2QGlHpHGjS2mn6Y--

Revision history for this message
In , Matt Kraai (kraai-ftbfs) wrote :

On Sun, Jan 23, 2005 at 01:37:03AM -0800, Steve Langasek wrote:
> reassign 290597 gs-common
> thanks
>
> Matt,
>
> All of the high-level apt tools should be capable of breaking this kind of
> dependency loop between gs-gpl and gs-common, so the most apparent reason
> for this kind of failure would be that gs-common could not be configured for
> reasons other than this dependency loop. I think we really need to see the
> output of trying to install gs-common on this system in order to debug this.

OK. I'll reproduce the problem Monday and send more information.

--
Matt

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sun, 23 Jan 2005 08:46:07 -0800
From: Matt Kraai <email address hidden>
To: Steve Langasek <email address hidden>, <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Bug#290597: fails to configure because gs-common is not configured

On Sun, Jan 23, 2005 at 01:37:03AM -0800, Steve Langasek wrote:
> reassign 290597 gs-common
> thanks
>
> Matt,
>
> All of the high-level apt tools should be capable of breaking this kind of
> dependency loop between gs-gpl and gs-common, so the most apparent reason
> for this kind of failure would be that gs-common could not be configured for
> reasons other than this dependency loop. I think we really need to see the
> output of trying to install gs-common on this system in order to debug this.

OK. I'll reproduce the problem Monday and send more information.

--
Matt

Revision history for this message
In , Matt Kraai (kraai-ftbfs) wrote : unreproducible -> done

Howdy,

I can't reproduce this bug any more, so I'm closing it.

--
Matt

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Mon, 24 Jan 2005 14:25:40 -0800
From: Matt Kraai <email address hidden>
To: <email address hidden>
Subject: unreproducible -> done

Howdy,

I can't reproduce this bug any more, so I'm closing it.

--
Matt

Revision history for this message
Martin Pitt (pitti) wrote :

Was closed as unreproducible in Debian and does not seem to happen on Hoary
either; closing.

Changed in gs-gpl:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.