Bug#755044: boinc: unstable / experimental override?

Gianfranco Costamagna costamagnagianfranco at yahoo.it
Sun Oct 12 21:32:20 UTC 2014

Ciao Luca,

>At the moment, it's not possible to prevent cruft-report from
>displaying an experimental package when a newer version is available
>in unstable, and I realize it will be quite hard to "ignore" it
>everytime cruft-report is processed.

So closing this one, it useless to keep this bug open, and I don't
want to ask such a feature just for me :)

>What I could suggest is to use a prefix in the debian revision which
>makes the version in experimental always greater of the version in
>unstable (e.g. 7.4.22+dfsg-exp3, instead of 7.4.22+dfsg-3exp1). This
>works as long as you keep the same upstream versions in both unstable
>and experimental, though (but you can use the same trick for the
>upstream version as well).

yes, but the problem is:
1) Upstream releases many times, once every 15 days, and I don't want to be too
much behind in debian
2) I would like to *don't* maintain an experimental fork, and rules file is tweaked
to automagically add the required bits based on the target release
3) I would like to see one day the server packages into unstable (Steffen?)
4) I also thought about doing something like they did for ghc (it wasn't intentional,
but it works) or bumping epoch (bad, I consider this almost never acceptable, but I think 

it would work) just for experimental.

So, hoping that one day we will merge experimental into unstable, I don't think we need to
spare any more ftpmaster time.

thanks for answering,


More information about the pkg-boinc-devel mailing list