[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

How to get rid of a poised version



Hello,

Mea culpa. I did a stupid thing with sbcl: in version 1:0.9.6.0-1  I used the 
following construction:

Package: sbcl
Depends: sbcl-common (= ${Source-Version}), ${shlibs:Depends}
...
Package: sbcl-common

Now it turns out that the buildd network cannot build new packages[1]:

|The following packages have unmet dependencies:
|  sbcl: Depends: sbcl-common (= 1:0.9.6.0-1) but 1:0.9.6.0-6 is to be 
|  installed 

Now, after thinking a bit I dropped the Depends, but I cannot force the 
buildd's to build a new version. I tried:

- to force to use a known good version: (1:0.9.6.0-4)
Build-Depends: debhelper (>> 4.1.16), sbcl (= 1:0.9.5.50-1) ...

This also failed [2]:

|The following packages have unmet dependencies:
|  sbcl: Depends: sbcl-common (= 1:0.9.6.0-1) but it is not going to be
||  installed 

-include sbcl-common into the build-depends (1:0.9.6.0-6)
Build-Depends: debhelper (>> 4.1.16), sbcl-common, sbcl (>= 1:0.8.16-1)
Also [3]:

|The following packages have unmet dependencies:
|  sbcl: Depends: sbcl-common (= 1:0.9.6.0-1) but 1:0.9.6.0-6 is to be
|  installed 

So is there anything else I can do? 

Groetjes, Peter

1:  
http://buildd.debian.org/fetch.php?&pkg=sbcl&ver=1%3A0.9.6.0-6&arch=alpha&stamp=1130914277&file=log&as=raw
2:
http://buildd.debian.org/fetch.php?&pkg=sbcl&ver=1%3A0.9.6.0-4&arch=alpha&stamp=1130888045&file=log&as=raw
3:
http://buildd.debian.org/fetch.php?&pkg=sbcl&ver=1%3A0.9.6.0-6&arch=alpha&stamp=1130914277&file=log&as=raw
-- 
signature -at- pvaneynd.mailworks.org 
http://www.livejournal.com/users/pvaneynd/
"God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson| 



Reply to: