ke, 2022-06-15 kello 09:55 +0200, julien.pu...@gmail.com kirjoitti:
>
> Let your new package migrate to testing, since it's that one which
> doesn't have the autoremoval issue?
>
I'm not sure I understand what you mean. The Guile 2.2 dependency issue
is solved in
#x27;m not sure I understand what you mean. The Guile 2.2 dependency
> issue is solved in the new package guile-cairo 1.11.2-5, which should
> not be autoremoved. The new package should migrate to testing in a
> few days.
>
The autoremoval from testing concerns the old package, whic
Le mercredi 15 juin 2022 à 10:29 +0300, Tommi Höynälänmaa a écrit :
>
> I recently received e-mail that package guile-cairo is to be
> autoremoved 2022-07-09. The reason is that it depended on guile 2.2.
> However, I made new version guile-cairo-1.11.2-5 that depends only on
>
Hello
I recently received e-mail that package guile-cairo is to be
autoremoved 2022-07-09. The reason is that it depended on guile 2.2.
However, I made new version guile-cairo-1.11.2-5 that depends only on
guile 3.0. What shall I do in order to cancel the autoremoval?
- Tommi Höynälänmaa
Package: wnpp
Severity: wishlist
Owner: Andreas Rottmann <[EMAIL PROTECTED]>
* Package name: guile-cairo
Version : 1.4.0
Upstream Author : Andy Wingo
* URL : http://home.gna.org/guile-cairo/
* License : LGPL
Programming Lang: C, Scheme
Descr
5 matches
Mail list logo