[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: vrweb, newbie maintainer/developer



On Fri, Sep 24, 1999 at 02:16:54PM +0800, Paul Harris wrote:
> > apply the diff on the source manually than update the control and the
> > changelog files and make a 'dpkg-buildpackage -rfakeroot'. It should
> > work (my rules file used some debhelper scripts which is useful to stay
> > policy compliant).
> 
> done it all! that dpkg-bui... thing is pretty cool :) 

And you not even try cvs-buildpackage and dbuild. Those ones are even
cooler!

> 
> i have a fresh question tho: do i have the right to rewrite/correct
> spelling mistakes in README.Debian even tho i didn't originally debianise
> vrweb? just some minor corrections... 

Sure, go for it! English is only my second language. I'm French. Either,
it'll be your package now, so, do whatever you like.

> 
> oh and also, when vrweb is installed, is netscape supposed to
> automatically know to use vrweb to open .wrl files? mine doesn't :( tho
> lynx does :)

netscape has their own mime-type association. You have to install
plugger to have it use the system default.

>  
> > Be sure also to send the patches to upstream!
> 
> ok, i'll do that after you have checked them :)

Right. Be aware that they considered VRweb mostly orphaned. They push
all their development effort on VRwave currently. No new version for
almost two years so...

> 
> > The diff dpkg-source wait for is one produce by the build process (is
> > not a custom one except that the paths are fixed). Just apply them manually
> > and update the debian/changelog file appropriately using dch or the
> > debbian-changelog mode of emacs.
> 
> i had problems there, but i can't recall what now as i worked around them.

If you can now build a valid debian source package, it's ok.

>  
> > You should install debian-policy & packaging-manual and read the Developper
> > Corner of the web pages.
> 
> i would have liked an idiot-proof howto / stepbystep guide to making /
> changing a package (would make debian more accessible to new developers).
> the docs were clear on the 5th time around, but a tutorial doc would be
> nice.

They're no really straight way to do a package. They're too much exceptions.
Personnaly, I find the uses of the debhelper scripts quite useful to stay
update with the Policy. The Debian New-Maintainer Guide and the Howto Create
a Debian Package are quite good at this. Do you read them? If yes, which
difficulty do you encounter regarding vrweb? 

Note: vrweb was my first package and pre-date the debhelper scripts.
That can be confusing at first since everything is done by hand.

> 
> but as usual, RTFM 5 or 6 times and you are clear on everything.
> 
> > > - How do I accept vrweb as mine? Do I need to get a sponser or something?
> > 
> > I can be your sponsor seens you're not a maintainer. It'll be your when
> > you upload it under your name. Please, contact me. I can give more
> > details.
> 
> excellent :) how do i get it to you? email the .diff.gz, .changes and
> .dsc? they are only about 97kb (love how small programs are in linux,
> but thats a large patch).

Please, do so. I have trouble contacting the web site you put in
another mail.

> 
> > > - How do I wack it on the debian mirror and all that?
> > 
> > dupload do the work when you're a maintainer.
> 
> cool. i'll leave that to you

OK. I'll have to put my name under it however because it's my PGP
signature who'll be checked. When you'll get your account as a maintainer,
you can upload a new version with the right maintainer on it. [It'll be
not too big cause only the patch, dsc and changes need to be upload, the
original source files doesn't because it doesn't change.]

> 
> > The bug seems to be fixes. In the changelog entry, add a 'Closes: #29078'
> > anywhere. The bug will be automatically closed when the package will be
> > uploaded.
> 
> vrweb (1.5-3) unstable; urgency=low
> 
>   * Fixed Imakefiles and source code. (Closes: #23539, #29078, #39580)
>   * Change maintainer
>   * Changed it to use update-mime. (Closes: #28866)
> 
>  -- Paul Harris <harri-pc@ee.uwa.edu.au>  Thu, 23 Sep 1999 04:32:51 +0800
> 
> how does that look? will all three be automatically closed? does it matter
> if a change runs over one line? can i put 3 bug closures together like
> that?

Right! That's exactly how it works. I'll have to change the maintainer
name but be sure I give you all the credits!

> 
> > First, please, read the FM and web pages. A new, non-official procedure
> > to help reducing the load of new-maintainer is to be sponsored by a current
> > maintainer. I'm willing and will be happy to do this for you :) Please,
> > read a little more and the contact me for any question. I'll contact you
> > again if you have any other questions.
> 
> great :) i'm happy to be your sponsee :) i think i got everything right...
> i'm trying for policy-3.0.1.1 but am unsure if i got everything ok... i
> think so.

I'll check that as soon as I have your patches. Maybe I'll make few
changes to use the debhelper scripts. My other packages used them and
I only have to recompile them with the new scripts and reupload everything.
A real economy of my spare time ;)

>  
> > Also, the sponsor help to speed up things by verifying the new package
> > and uploading it himself in the name of the new maintainer (you have
> > to be a maintainer to upload a package). So, can you send me your patches
> > that I can check them? I can even upload it before you get your account
> > if it's your desire.
> 
> i'll send them once i figure out this gpg thing, i'd like to get at least
> one person to sign my key. also, do you know what keyserver i'm supposed
> to upload my public key to?

You have to send it to the new maintainer when it'll be sign by Dave.

> 
> i'm just going to wait and see if i can meet with Dave Cook for him to
> sign my fresh gpg key (he's in perth somewhere nearby).

Send it to me right after you make it sign by Dave. I will send it
to new-maintainer@debian.org with my recommendations. However, here
also some questions about your application. It's easy questions and
don't need strong answer. (I mean, Debian doesn't need you to be a
full activist of the OpenSource/FreeSoftware movement. Just that you
understand that's it's one of our goal and that you'll be part of it.
Debian is not a political movement, just an organization build under
the OpenSource philosophy.) I hope to don't seem too much
"authorative" but it's real hard when it's not even your first
language.

So, first, have you read the Debian Social Contract (if not, do it ;)?
Do you understand it? What do you think about it? I'll be please to
answer any questions about it.

What's your future goals with Debian? Do you want to participate
more actively to Debian, push up more packages or simply maintain
your current package? What I really want here is to present you
the opportunities of Debian. Working for Debian isn't just packaging
some cool software. It can be really more than that, and most of the
stuff is even more exciting than package maintenance. I also want you
to know that your job as a package maintainer isn't finish when you
upload your package. You have to support it after that (that's where
I failed with vrweb :( ). That's mean following at least the
debian-devel-announce mailing list (really low volume), update your
package when new version on the dependencies appears, answer to
bugs reports, give some (limited) support to users who ask you,
and ensure that your package still follow the current Policy.

Finally, one little warning: As a Debian Maintainer, you'll be
given a new e-mail address @debian.org and some accounts on
different machines around the world. Does machine and bandwidth
are given by donators to Debian absolutely free of charge. Don't
abuse those gifts and try to use it solely for Debian-related
purposes. It's not mandatory but some maintainers have seen there
rights as maintainer remove already in the past for such things
and we don't want to be seen as a bunch of donators' abusers
(sorry, can explain it more clearly).

Voila!

> 
> > Give me some news!
> > Fabien
> > { happy to see this embarrassing bugs finally closed! ;) }
> 
> almost there! so close!
> Paul 
> (happy to fix these bugs!)
> 
> "If you can't make it good, make it look good."
> 				Bill Gates, 1995 

Regards,

-- 
------------------------------------------------------------------------
Fabien Ninoles        Chevalier servant de la Dame Catherine des Rosiers
aka Corbeau aka le Veneur Gris               Debian GNU/Linux maintainer
E-mail:                                                    fab@tzone.org
WebPage:                                    http://www.tzone.org/~fabien
RSA PGP KEY [E3723845]: 1C C1 4F A6 EE E5 4D 99  4F 80 2D 2D 1F 85 C1 70
------------------------------------------------------------------------


Reply to: