Bug#337358: Bug#337346: slib upgrade broken
Hello Rob and Thomas, This bug is assigned to libglade9 which has been removed from unstable. As a consequence, this bug should either be closed or reassigned. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337358: Bug#337346: slib upgrade broken
Bill Allombert [EMAIL PROTECTED] writes: On Tue, Jun 06, 2006 at 08:52:26AM -0700, Thomas Bushnell BSG wrote: [EMAIL PROTECTED] writes: Hello Rob and Thomas, This bug is assigned to libglade9 which has been removed from unstable. As a consequence, this bug should either be closed or reassigned. Bug 337346 (in your subject line) has nothing to do with glade, and is closed as of guile-1.6/1.6.7-2. Bug 337358 (to which you sent the email) doesn't mention libglade9 at all, and is not assigned to libglade9. Sorry, I meant libguile9 libguile9 has not actually been removed from unstable; see http://packages.debian.org/cgi-bin/search_packages.pl?searchon=namesversion=allexact=1keywords=libguile9. Perhaps the maintainer should file a request with the FTP masters to have it removed, at which point the bug will be automatically closed. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337358: Bug#337346: slib upgrade broken
On Tue, Jun 06, 2006 at 08:52:26AM -0700, Thomas Bushnell BSG wrote: [EMAIL PROTECTED] writes: Hello Rob and Thomas, This bug is assigned to libglade9 which has been removed from unstable. As a consequence, this bug should either be closed or reassigned. Bug 337346 (in your subject line) has nothing to do with glade, and is closed as of guile-1.6/1.6.7-2. Bug 337358 (to which you sent the email) doesn't mention libglade9 at all, and is not assigned to libglade9. Sorry, I meant libguile9 Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337358: Bug#337346: slib upgrade broken
[EMAIL PROTECTED] writes: Hello Rob and Thomas, This bug is assigned to libglade9 which has been removed from unstable. As a consequence, this bug should either be closed or reassigned. Bug 337346 (in your subject line) has nothing to do with glade, and is closed as of guile-1.6/1.6.7-2. Bug 337358 (to which you sent the email) doesn't mention libglade9 at all, and is not assigned to libglade9. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337358: Bug#337346: slib upgrade broken
On Tue, Jun 06, 2006 at 10:08:37AM -0700, Thomas Bushnell BSG wrote: libguile9 has not actually been removed from unstable; see http://packages.debian.org/cgi-bin/search_packages.pl?searchon=namesversion=allexact=1keywords=libguile9. The link you post only lists libguile9 in _stable_. No, it doesn't. I can only wonder if you actually follewd it. Actually I made a copy-paste error: I did lynx 'http://packages.debian.org/cgi-bin/search_packages.pl?searchon=namesversion=all+exact=1keywords=libguile9' so I did not get the html data you provide, sorry about that. I see the following when I follow that link. What do you see? With your data I get Package libguile9 * oldstable (libs): libraries for Guile1.4 (guile, guilereadline, and qthreads). 1:1.4-24: alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc * stable (libs): libraries for Guile1.4 (guile, guilereadline, and qthreads) 1:1.4-26: alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc * unstable (libs): libraries for Guile1.4 (guile, guilereadline, and qthreads) 1:1.4-26: kfreebsd-i386 But kfreebsd-i386 does not count since it use an external archive and the ftp-masters cannot remove packages there, so as far as the official archive is concerned, libguile9 was removed from unstable. Now, that we are back on track, do you know whether this bug should be reassigned or closed ? Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337358: Bug#337346: slib upgrade broken
Bill Allombert [EMAIL PROTECTED] writes: On Tue, Jun 06, 2006 at 09:25:06AM -0700, Thomas Bushnell BSG wrote: Bill Allombert [EMAIL PROTECTED] writes: On Tue, Jun 06, 2006 at 08:52:26AM -0700, Thomas Bushnell BSG wrote: [EMAIL PROTECTED] writes: Hello Rob and Thomas, This bug is assigned to libglade9 which has been removed from unstable. As a consequence, this bug should either be closed or reassigned. Bug 337346 (in your subject line) has nothing to do with glade, and is closed as of guile-1.6/1.6.7-2. Bug 337358 (to which you sent the email) doesn't mention libglade9 at all, and is not assigned to libglade9. Sorry, I meant libguile9 libguile9 has not actually been removed from unstable; see http://packages.debian.org/cgi-bin/search_packages.pl?searchon=namesversion=allexact=1keywords=libguile9. The link you post only lists libguile9 in _stable_. No, it doesn't. I can only wonder if you actually follewd it. I see the following when I follow that link. What do you see? bin7ymnG2So9D.bin Description: html Thomas
Bug#337358: Bug#337346: slib upgrade broken
On Tue, Jun 06, 2006 at 09:25:06AM -0700, Thomas Bushnell BSG wrote: Bill Allombert [EMAIL PROTECTED] writes: On Tue, Jun 06, 2006 at 08:52:26AM -0700, Thomas Bushnell BSG wrote: [EMAIL PROTECTED] writes: Hello Rob and Thomas, This bug is assigned to libglade9 which has been removed from unstable. As a consequence, this bug should either be closed or reassigned. Bug 337346 (in your subject line) has nothing to do with glade, and is closed as of guile-1.6/1.6.7-2. Bug 337358 (to which you sent the email) doesn't mention libglade9 at all, and is not assigned to libglade9. Sorry, I meant libguile9 libguile9 has not actually been removed from unstable; see http://packages.debian.org/cgi-bin/search_packages.pl?searchon=namesversion=allexact=1keywords=libguile9. The link you post only lists libguile9 in _stable_. Furthermore on merkel: % madison libguile9 libguile9 | 1:1.4-24 | oldstable | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libguile9 | 1:1.4-26 |stable | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc So it seems pretty clear libguile9 was removed. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337358: Bug#337346: slib upgrade broken
Steve Langasek [EMAIL PROTECTED] writes: Perhaps the maintainer should file a request with the FTP masters to have it removed, at which point the bug will be automatically closed. Bugs aren't automatically closed on package removal. Curious; I get such messages all the time when packages are removed, which seem to be sent automatically by the FTP masters when they remove packages. How can this be? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337358: Bug#337346: slib upgrade broken
On Tue, Jun 06, 2006 at 09:25:06AM -0700, Thomas Bushnell BSG wrote: Bill Allombert [EMAIL PROTECTED] writes: Sorry, I meant libguile9 libguile9 has not actually been removed from unstable; yes, it has. see http://packages.debian.org/cgi-bin/search_packages.pl?searchon=namesversion=allexact=1keywords=libguile9. Er, note that it only lists it as being present on kfreebsd-i386, which is not an architecture in the main archive. Perhaps the maintainer should file a request with the FTP masters to have it removed, at which point the bug will be automatically closed. Bugs aren't automatically closed on package removal. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337358: Bug#337346: slib upgrade broken
Bill Allombert [EMAIL PROTECTED] writes: Now, that we are back on track, do you know whether this bug should be reassigned or closed ? The similar bug in guile-1.6 has been fixed. It's up to the maintainer, but I think it can be closed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337358: Bug#337346: slib upgrade broken
This one time, at band camp, Thomas Bushnell BSG said: Bill Allombert [EMAIL PROTECTED] writes: The link you post only lists libguile9 in _stable_. No, it doesn't. I can only wonder if you actually follewd it. Yes, it does. The fact that kfreebsd-i386, an unofficial arch, is still listed does not mean it's in unstable. No need to get hostile - just reread the page, please. -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#337358: Bug#337346: slib upgrade broken
On Tue, Jun 06, 2006 at 10:09:15AM -0700, Thomas Bushnell BSG wrote: Steve Langasek [EMAIL PROTECTED] writes: Perhaps the maintainer should file a request with the FTP masters to have it removed, at which point the bug will be automatically closed. Bugs aren't automatically closed on package removal. Curious; I get such messages all the time when packages are removed, which seem to be sent automatically by the FTP masters when they remove packages. How can this be? Normally, you will see such closures only for the removal requests themselves, the bugs filed on ftp.debian.org. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337346: slib upgrade broken
Thomas Bushnell BSG [EMAIL PROTECTED] writes: So the slib upgrade to version 3a2 doesn't work because the ice-9 has a slib.scm file which should be a copy (or near copy) of the slib file guile.init. Well, it should contain all the important parts, but should be modified to work appropriately for guile, whatever that means. It looks to me like in the past, guile may have been modifying guile.init to produce ice-9/slib.scm. However, without knowing more of the history, I can't say for sure. My guess is that some of the modifications have had to do with making sure slib functions as a proper guile module. Version 3a2 has added the function with-load-pathname and it isn't in the slib.scm file that the guile packages provide. It seems to me that: 1) slib.scm should not be in guile-1.6-libs and libguile9. 2) slib.scm should be in guile1.4-slib and guile-1.6-slib. How would this help? 3) the guile*-slib packages should contain a *versioned* dependency on slib so that new slib versions which change the initialization interface can DTRT. Can you elaborate on what you have in mind here? Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337346: slib upgrade broken
Rob Browning [EMAIL PROTECTED] writes: Well, it should contain all the important parts, but should be modified to work appropriately for guile, whatever that means. It looks to me like in the past, guile may have been modifying guile.init to produce ice-9/slib.scm. However, without knowing more of the history, I can't say for sure. My guess is that some of the modifications have had to do with making sure slib functions as a proper guile module. Yes, this is exactly right. Version 3a2 has added the function with-load-pathname and it isn't in the slib.scm file that the guile packages provide. It seems to me that: 1) slib.scm should not be in guile-1.6-libs and libguile9. 2) slib.scm should be in guile1.4-slib and guile-1.6-slib. How would this help? It doesn't solve the instant problem. It makes it (together with 3) easier the next time. 3) the guile*-slib packages should contain a *versioned* dependency on slib so that new slib versions which change the initialization interface can DTRT. Can you elaborate on what you have in mind here? Right now guile-1.6-slib depends on slib. It should contain slib.scm itself (rather than putting it in guile-1.6-slib) and then depend on, for example, slib (=3e2). Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337346: slib upgrade broken
So the slib upgrade to version 3a2 doesn't work because the ice-9 has a slib.scm file which should be a copy (or near copy) of the slib file guile.init. Version 3a2 has added the function with-load-pathname and it isn't in the slib.scm file that the guile packages provide. It seems to me that: 1) slib.scm should not be in guile-1.6-libs and libguile9. 2) slib.scm should be in guile1.4-slib and guile-1.6-slib. 3) the guile*-slib packages should contain a *versioned* dependency on slib so that new slib versions which change the initialization interface can DTRT. Whether this re-factoring happens, however, can you please fix the current ice-9 in each guile version to be able to load scm 3a2? Thanks. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
