Re: Bug#109833: postinst could offer to run lilo

[Colin Walters]

Manoj Srivastava <[EMAIL PROTECTED]> writes:

>>>"Yann" == Yann Dirson <[EMAIL PROTECTED]> writes:
>
>  Yann> Right.  Probably other booloaders could be handled as well.
>  Yann> Such a mechanism is already implemented by kernel-package, I
>  Yann> don't know how easy it could be reused.  Maybe this could be
>  Yann> turned into a somewhat generic API to bootloaders.

Yeah, I'm working on what I'm tentatively calling kernel-package2.
The status is still experimental, but you can make kernel packages
with it and install them.  I've tested the basics (no bootfloppy
creation or anything) on powerpc-linux and i386-linux.  Lots more work
still needs to be done.

Currently I'm doing all the work on my computer (I'm still in
new-maintainer), so the CVS repository is there.  It's browsable
online at:

http://cvs.verbum.org/cgi-bin/viewcvs.cgi/debian>

Most importantly, see the file CONCEPT in the distribution for the
main ideas.  I've added stuff to the TODO file.

They're directly accessible at:

http://cvs.verbum.org/cgi-bin/viewcvs.cgi/debian/kernel-package2/CONCEPT>
and
http://cvs.verbum.org/cgi-bin/viewcvs.cgi/debian/kernel-package2/TODO>

I can give verbum.org CVS accounts to anyone who wants to work on it,
or we could move the CVS repository to debian.org or somewhere else;
whichever is fine by me.

Note that I'm not targeting this for woody; it would take too much
testing to be sure everything works.

And finally, I'm going to be on vacation until September 4th, but I'll
be able to check my email during that time.

Re: microwindows build status

[Colin Walters]

On Fri, 2002-01-04 at 18:47, Thomas Bushnell, BSG wrote:
> This is not such a good idea.  Maintainers are generally not
> responsible for checking build status and logs [...]

Which is kind of silly, given how easy it is to go to
http://buildd.debian.org and look up build logs for a package.

Re: xscreensaver/login/passwd developer MIA

[Colin Walters]

On Wed, 2002-07-17 at 11:39, Ari Pollak wrote:
> Hi everybody.. It seems that Karl Ramm <[EMAIL PROTECTED]> is missing in 
> action - he has not updated any bugs or packages in a few months, and 
> his xscreensaver package is woefully outdated. I've attempted to e-mail 
> him over the course of the last few months, with no response. I propose 
> that his important packages, such as login and passwd, be reassigned to 
> the QA team

Generally, the first step is just to start NMUing the package.  If the
maintainer still doesn't respond, then you can either switch the
maintainer to yourself, or to the QA team.

>, and I'd like to volunteer to take over his xscreensaver 
> packages if need be, if someone would agree to sponsor them. 

I will sponsor your uploads.

> I'm not an 
> official maintainer yet, but I do have 2 packages in Debian already via 
> sponsors (one of my sponsors, [EMAIL PROTECTED], seems to be MIA as 
> well), xmms-cdread and libgtkspell0/libgtkspell-dev. I've been 
> maintaining updated xscreensaver packages since upstream 4.0, and mine 
> can be found at .

I'm looking at your xscreensaver packages now.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: xscreensaver/login/passwd developer MIA

[Colin Walters]

I took a look at your xscreensaver packages.  Some comments: 

I don't see why you patch hacks/speedmine.c; the optimization you make
(turning a division by two into a right bitshift by 1) is generally
going to be made by GCC anyways.

Your diff includes po/.intltool-merge-cache, which probably isn't
intentional.

Now, you should change the version number to 4.05-1.1, since this is a
NMU.  I suggest just merging all your changelog entries since Colin
Watson's upload together, since they weren't actually part of Debian.

Finally, there are a lot of open bugs against xscreensaver.  Could you
go through some of the list and see which ones are closed by this new
upstream version?  I imagine a lot of them will be.

Thanks for working on this package!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]