** Changed in: silky (Debian)
Status: Unknown => Fix Released
--
[FTBFS] silky (0.5.4-0.1) fails to build in gutsy
https://bugs.launchpad.net/bugs/135782
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: silky (Debian)
Bugwatch: Debian Bug tracker #433820 => Debian Bug tracker #474073
Status: New => Unknown
--
[FTBFS] silky (0.5.4-0.1) fails to build in gutsy
https://bugs.launchpad.net/bugs/135782
You received this bug notification because you are a member of Ubuntu
Bug
2008-04-08 03:48:38 INFOcreating lockfile
2008-04-08 03:48:41 INFORemoving candidates:
2008-04-08 03:48:41 INFOsilky 0.5.4-0.1 in hardy
2008-04-08 03:48:41 INFOsilky 0.5.4-0.1 in hardy amd64
2008-04-08 03:48:41 INFOsilky 0.5.4-0.1 in hardy i386
2008-04-08 03:48:41 IN
Archive admins, please remove silky from the archive.
It doesn't build with the newer libsilc and upstream is no more.
The package has been removed from Debian unstable:
http://packages.qa.debian.org/s/silky/news/20080403T225716Z.html
--
[FTBFS] silky (0.5.4-0.1) fails to build in gutsy
https://
I can confirm that this is still not fixed in Hardy beta. I believe
there are 2 solutions:
1. Remove the silky package from the repositories.
2. Add the libsilc-1.0-2 package to the repositories.
Either will work and I don't have a preference for which, but one fix or
the other should be imple
The chances to remove it if this is still not removed in Debian are very slim.
If anybody picks up the work done by Jeremy and finishes it (effectively taking
over upstream) will obviously revive it.
The process for requesting a removal is described here:
https://wiki.ubuntu.com/UbuntuDevelopmen
No opinion if this should be removed or not, but confirming that it does
still not install on Hardy. Obviously something needs to happen to the
depends if nothing else.
silky:
Depends: libsilc-1.0-2 but it is not installable
--
[FTBFS] silky (0.5.4-0.1) fails to build in gutsy
https
As a workaround, I used the libsilc-1.0-2-dev package from the Feisty
repositories.
https://bugs.launchpad.net/ubuntu/+source/silky/+bug/155442
--
[FTBFS] silky (0.5.4-0.1) fails to build in gutsy
https://bugs.launchpad.net/bugs/135782
You received this bug notification because you are a member
I can confirm that the library versions don't match. But should the
application be removed if it's no longer maintained? It can be a
security treat for it's potential users, since there will be no fixes
released. It also won't be adapted to new libraries what will cause the
very problem we have her
** Changed in: silky (Ubuntu)
Assignee: Cesare Tirabassi (norsetto) => (unassigned)
Status: In Progress => Confirmed
--
[FTBFS] silky (0.5.4-0.1) fails to build in gutsy
https://bugs.launchpad.net/bugs/135782
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: silky (Ubuntu)
Importance: Undecided => Medium
--
[FTBFS] silky (0.5.4-0.1) fails to build in gutsy
https://bugs.launchpad.net/bugs/135782
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
** Changed in: silky (Debian)
Status: Unknown => New
--
[FTBFS] silky (0.5.4-0.1) fails to build in gutsy
https://bugs.launchpad.net/bugs/135782
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
silky FTBFS with new library due to the number of changes in the API.
See debian bug #433820.
Note that upstream is no more:
http://sourceforge.net/forum/forum.php?forum_id=717434
** Attachment added: "build log with new library"
http://launchpadlibrarian.net/9054818/silky
--
[FTBFS] silky
** Bug watch added: Debian Bug tracker #433820
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433820
** Also affects: silky (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433820
Importance: Unknown
Status: Unknown
--
[FTBFS] silky (0.5.4-0.1) fails to build in gu
14 matches
Mail list logo
