Bug#322235: most and the libslang2
severity 315639 grave tags 315639 sid merge 315639 322235 tags 322235 pending tags 315639 pending thanks These two bugs are the same problem. In any case, a fixed version of most that includes the latest upstream version (4.10.2) has been prepared, uploaded and accepted and both of these bugs should be closed as soon as that hits the archive. Regards, Mako -- Benjamin Mako Hill [EMAIL PROTECTED] http://mako.cc/ signature.asc Description: Digital signature
Bug#403994: marked as done (file conflict with webmagick)
> Your message dated Wed, 27 Dec 2006 17:47:02 + > with message-id <[EMAIL PROTECTED]> > and subject line Bug#403994: fixed in aub 2.2.1 > has caused the attached Bug report to be marked as done. > > This means that you claim that the problem has been dealt with. > If this is not the case it is now your responsibility to reopen the > Bug report if necessary, and/or fix the problem forthwith. Thanks Andreas for clearing this up! As you know, it's the Holiday sand I've been traveling and largely unresponsive over the last week or so. I saw the bug but had not had an opportunity to address it yet. Regards, Mako -- Benjamin Mako Hill [EMAIL PROTECTED] http://mako.cc/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#413469: bug 413469
> On 2007-03-14 19:58 -0400, Michael Gilbert wrote: > > with that said, i agree that in-development snapshots should be kept > > out of unstable, and only done in experimental. maybe this should be > > a change to debian-policy? > > Nah, dev. snapshots can be in testing/unstable.. but should never get > into stable... unless, of course, through an additional package > collection for it (backports), that does keep upgraded. Right. I don't see any reason to categorically keep all development snapshots out of unstable/testing. "Development snapshot" can mean different things in the context of different projects. Our actions should be shaped more by the nature of individual projects and by the expressed desire of upstream developers than by whether or not the version number contains a date. In this case, I see absolutely no reason to keep ion3 out of unstable and testing -- especially since Tuomo says he doesn't either. Regards, Mako -- Benjamin Mako Hill [EMAIL PROTECTED] http://mako.cc/ signature.asc Description: Digital signature
Bug#418348: libtemplate-perl 2.15-0.0 (unstable/alpha): FTBFS under sudo
Thanks Steve, I'll take a look into this today. Regards, Mako -- Benjamin Mako Hill [EMAIL PROTECTED] http://mako.cc/ signature.asc Description: Digital signature
Bug#418348: libtemplate-perl 2.15-0.0 (unstable/alpha): FTBFS under sudo
> I am a victim of abuse.. a person put my email in much mailing list... > > PLEASE UNSUBSCRIBE ME I'm not sure which email list you are subscribed to but you should be able to follow instructions at the bottom of mails or in email headers and unsubscribe yourself. :) Later, Mako -- Benjamin Mako Hill [EMAIL PROTECTED] http://mako.cc/ signature.asc Description: Digital signature
Bug#418348: libtemplate-perl 2.15-0.0 (unstable/alpha): FTBFS under sudo
> A likely cause for this error is use of $(PWD) in debian/rules: recent
> versions of sudo do not propagate the caller's PWD env variable by default,
> and sudo ./debian/rules only invokes make, so this variable will be unset.
> Please use the make built-in variable $(CURDIR) instead.
In fact, the problem here lines in Makefile.PL which is looking for
$ENV{PWD}. I'll work around this, try to fix #411044, and upload right
away.
Regards,
Mako
--
Benjamin Mako Hill
[EMAIL PROTECTED]
http://mako.cc/
signature.asc
Description: Digital signature
