Re: guile-cairo
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 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. - Tommi -- Kotisivu / Homepage: http://www.iki.fi/tohoyn/ Sähköposti / E-Mail: tommi.hoynalan...@iki.fi GPG-sormenjälki / GPG fingerprint: 55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046 0F83 FM, Debian-ylläpitäjä / M.Sc., Debian Maintainer
Re: guile-cairo
Le mercredi 15 juin 2022 à 11:11 +0300, Tommi Höynälänmaa a écrit : > 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 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, which does depend on guile 2.2. Normally your new package should migrate to testing before the old one gets kicked out. Don't worry! J.Puydt
Re: guile-cairo
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 > guile 3.0. What shall I do in order to cancel the autoremoval? Let your new package migrate to testing, since it's that one which doesn't have the autoremoval issue? Cheers, J.Puydt
guile-cairo
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 -- Kotisivu / Homepage: http://www.iki.fi/tohoyn/ Sähköposti / E-Mail: tommi.hoynalan...@iki.fi GPG-sormenjälki / GPG fingerprint: 55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046 0F83 FM, Debian-ylläpitäjä / M.Sc., Debian Maintainer
Bug#439103: ITP: guile-cairo -- Guile bindings for Cairo
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
Description : Guile bindings for Cairo
This is the proposed control file:
Source: guile-cairo
Section: interpreters
Priority: extra
Maintainer: Andreas Rottmann <[EMAIL PROTECTED]>
Standards-Version: 3.7.2
Build-Depends: cdbs (>= 0.4.49), autotools-dev, debhelper (>> 5),
patchutils (>= 0.2.25), guile-1.8-dev, libcairo2-dev (>= 1.4.10),
guile-library (>= 0.1.2)
Package: guile-cairo
Architecture: any
Depends: ${shlibs:Depends}
Description: Guile bindings for Cairo
This package contains Guile modules that provide access to the Cairo
library.
Package: guile-cairo-dev
Architecture: any
Depends: guile-cairo (= ${binary:Version}), guile-1.8-dev, libcairo2-dev (>=
1.4.10)
Description: Guile bindings for Cairo, development files
This package contains the info manual for guile-cairo and the header
files to allow compilation of wrappers depending on guile-cairo.
The reason that there is no lib* package is that the shared library
shipped in guile-cairo is dlopen'ed by the Guile code, so the symlinks
and .la file ship in guile-cairo.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-1-k7 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
