Prev: delay shutdown while backup (rsnapshot) is running
Next: martian sources iptables
From: Andrei Popescu on 1 Jul 2010 16:50
On Jo, 01 iul 10, 20:51:05, Didster wrote:

[...]

> Then "apt-get install package-system" installs package-system 2.0.2
> along with V2.1.99 of the three packages. But "apt-get install
> package-system=2.0.1" fails as follows:
>
> The following packages have unmet dependencies.
> package-system: Depends: package1 (= 2.1.88) but 2.1.99 is to be installed
> Depends: package2 (= 2.1.88) but 2.1.99 is to be installed
> Depends: package3 (= 2.1.88) but 2.1.99 is to be installed
> E: Broken packages

Does aptitude behave the same way?

Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
From: Jordan Metzmeier on 1 Jul 2010 17:00
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/01/2010 03:51 PM, Didster wrote:
> Hi there,
>
> We use a local apt repository as a means to distribute our own
> software. The software is not and will not ever be part of the
> official Debian archives. Our software consists of 4 packages, 3 real
> ones, lets call then package1, package2 and package3 and a overall
> package that exists to bring in the three packages at a specific
> version to make a overall version of our system - gets call that
> package-system.
>
> The local repository consists of many versions of each of the four
> packages. When asking apt to install the very latest version of
> package-system, everything works just as it should. But when asking
> apt to install a specific older version of package-system (which we
> sometimes need to do), apt complains and says the dependencies cannot
> be met.
>
> Assume we have
>


What about a system similar to say, debian kernels. You can add the
versions to the package names so they become distinct packages eg.
package1-2.1.88. Of course, this could end up being a nightmare in the
Conflicts: field to prevent multiple version from being installed.

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

iQIcBAEBCAAGBQJMLQCHAAoJEKj/C3qNthmT+FcQAIHubtpYkt7X1fLjhffJvBxA
hbk/3cb94g2C8pBnOm2OygUsmAY09eTcWhcUgbucweg0BSzknpLyH3EJ9yaRcEv/
acu/dqJCtMt3ApgA2tdbMkwKdMrqq7OBOs+uQxNYOvtwXsRE6dGhAlCFN/lTwltW
lFGFIc3Q4Eh6KzZR82/GhJb0QSjyYNxPRTU4mHeSfoIsOyqqK15ojvrfTi75w2Ls
k3+3YZHWNz8hLav/8/mYy2VCqtIJcqG0gs41Lt9HYyway4/hyR+J+sUO8gIUbPpg
gAzGjJcaie21MMFu9U44n2iCSkg4BGpI03P0hoKwNvUoRKW1lVq7kyIjg6QCwT7C
Z0nJzbDiUelwNuXsBtiklFTLlZfYRGpe/eTxbBJhGHdmuW6cn1/M+Ri4GRM9XNf5
DvY1d1nj/PlHCS4uIg+uB7LRPZWps6vCA3Q3TnVc6WJfXJJ/ODFD0hoj6D1gMqId
4O9TD7IBzMFISuWpd+HS78zRtr9mPqhYPT4diIg9z5UKx6dG8NaIysdf2qDLqly0
NaT5tf4EfXkIwtE7DCK9jg0Sh0PQHg2LvQpulsUChpAhIWn+R202WNNaeg5G6ooS
fQi6WVfIlktMvx8ASyqHNTDfmyjERv2+mMcuYtEUHCzhNoodGpiIHASgKDo1oOfT
DXBoIjrBgM6MoXFYxFv7
=DfPE
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C2D0087.6060006(a)gmail.com
From: Didster on 1 Jul 2010 17:10
Sort of - but it can actually do the install:

The following packages are BROKEN:
package-system
The following packages have unmet dependencies:
package-system: Depends: package1 (= 2.1.88) but it is not installable
Depends: package2 (= 2.1.88) but it is not installable
Depends: package3 (= 2.1.88) but it is not installable
The following actions will resolve these dependencies:

Install the following packages:
package1 [2.1.88 (unstable)]
packge2 [2.1.88 (unstable)]
packge3 [2.1.88 (unstable)]

Selecting yes goes ahead and installs package1 2 and 3 followed by
package-system

How can a package that is "not installable" then be installed??!

Thanks


On Thu, Jul 1, 2010 at 9:43 PM, Andrei Popescu <andreimpopescu(a)gmail.com> wrote:
> On Jo, 01 iul 10, 20:51:05, Didster wrote:
>
> [...]
>
>> Then "apt-get install package-system" installs package-system 2.0.2
>> along with V2.1.99 of the three packages.  But "apt-get install
>> package-system=2.0.1" fails as follows:
>>
>> The following packages have unmet dependencies.
>>   package-system: Depends: package1 (= 2.1.88) but 2.1.99 is to be installed
>>                 Depends: package2 (= 2.1.88) but 2.1.99 is to be installed
>>                 Depends: package3 (= 2.1.88) but 2.1.99 is to be installed
>> E: Broken packages
>
> Does aptitude behave the same way?
>
> Regards,
> Andrei
> --
> Offtopic discussions among Debian users and developers:
> http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQEcBAEBCAAGBQJMLP31AAoJEHNWs3jeoi3pjyMH/2hgebZN/XviZNwxJowTqr5A
> xIJObvCcJ8Ndr1vvQpPzXaQHzSHMvJSpPBojL1lcspJBnzVN6kcryAdeTXlguo6+
> 4ZFjtRDfd0J0LOLMHulNtB4oKIuSX1KT7+wiIkclcJRdHt02Os2qSkPzhMmiwTl8
> L6qsjVGbtkKbczFVl2SMr065aZtzs5ehpg6pqRLGESf8z8bBsjTgNw9+RLSx7u1m
> HXPFYRExKt09lmt9jfeO4MYHzAtBGdMtUsCQtRHV8MgZy//wgX68iz8Tlew0IyWz
> 0ToJJSWTx3pEsd0F+e/4zmv6RRkSVrhoFoHxOURyEA6PRH+oJaGk5HPKs19InGQ=
> =RB/Y
> -----END PGP SIGNATURE-----
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/AANLkTikxxfMcbdT-b1B4Rs6jYjFwd3SfWNxusF3OZ_4W(a)mail.gmail.com
From: Didster on 1 Jul 2010 17:20
I tried this, but it didn't help.

I gave package-system a unique name based on the version, but it did
the same thing. I didn't try giving all 3 packages their own name
based on version (nor would I want to!)

Thanks


On Thu, Jul 1, 2010 at 9:54 PM, Jordan Metzmeier <titan8990(a)gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 07/01/2010 03:51 PM, Didster wrote:
>> Hi there,
>>
>> We use a local apt repository as a means to distribute our own
>> software.  The software is not and will not ever be part of the
>> official Debian archives.  Our software consists of 4 packages, 3 real
>> ones, lets call then package1, package2 and package3 and a overall
>> package that exists to bring in the three packages at a specific
>> version to make a overall version of our system - gets call that
>> package-system.
>>
>> The local repository consists of many versions of each of the four
>> packages.  When asking apt to install the very latest version of
>> package-system, everything works just as it should.  But when asking
>> apt to install a specific older version of package-system (which we
>> sometimes need to do), apt complains and says the dependencies cannot
>> be met.
>>
>> Assume we have
>>
>
>
> What about a system similar to say, debian kernels. You can add the
> versions to the package names so they become distinct packages eg.
> package1-2.1.88. Of course, this could end up being a nightmare in the
> Conflicts: field to prevent multiple version from being installed.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iQIcBAEBCAAGBQJMLQCHAAoJEKj/C3qNthmT+FcQAIHubtpYkt7X1fLjhffJvBxA
> hbk/3cb94g2C8pBnOm2OygUsmAY09eTcWhcUgbucweg0BSzknpLyH3EJ9yaRcEv/
> acu/dqJCtMt3ApgA2tdbMkwKdMrqq7OBOs+uQxNYOvtwXsRE6dGhAlCFN/lTwltW
> lFGFIc3Q4Eh6KzZR82/GhJb0QSjyYNxPRTU4mHeSfoIsOyqqK15ojvrfTi75w2Ls
> k3+3YZHWNz8hLav/8/mYy2VCqtIJcqG0gs41Lt9HYyway4/hyR+J+sUO8gIUbPpg
> gAzGjJcaie21MMFu9U44n2iCSkg4BGpI03P0hoKwNvUoRKW1lVq7kyIjg6QCwT7C
> Z0nJzbDiUelwNuXsBtiklFTLlZfYRGpe/eTxbBJhGHdmuW6cn1/M+Ri4GRM9XNf5
> DvY1d1nj/PlHCS4uIg+uB7LRPZWps6vCA3Q3TnVc6WJfXJJ/ODFD0hoj6D1gMqId
> 4O9TD7IBzMFISuWpd+HS78zRtr9mPqhYPT4diIg9z5UKx6dG8NaIysdf2qDLqly0
> NaT5tf4EfXkIwtE7DCK9jg0Sh0PQHg2LvQpulsUChpAhIWn+R202WNNaeg5G6ooS
> fQi6WVfIlktMvx8ASyqHNTDfmyjERv2+mMcuYtEUHCzhNoodGpiIHASgKDo1oOfT
> DXBoIjrBgM6MoXFYxFv7
> =DfPE
> -----END PGP SIGNATURE-----
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian..org
> Archive: http://lists.debian.org/4C2D0087.6060006(a)gmail.com
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/AANLkTin0Gkdkh6Gmv1IMM46GApsw8QTn4SSnPPox-Y3n(a)mail.gmail.com
From: Andrei Popescu on 1 Jul 2010 18:20
On Jo, 01 iul 10, 22:06:49, Didster wrote:
>
> How can a package that is "not installable" then be installed??!

As you've shown in you 'apt-cache policy' those versions are not
'candidate' versions, but aptitude offers alternative solutions (one of
the benefits over apt-get), one of them being to actually install
non-candidate versions. This is AFAIU, someone will correct me if I'm
wrong.

Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
 |  Next  |  Last
Pages: 1 2
Prev: delay shutdown while backup (rsnapshot) is running
Next: martian sources iptables