Upload of jed and jed-extra to unstable
Rafael Laboissiere
rafael at debian.org
Sat Jul 8 11:26:55 UTC 2006
* Jörg Sommer <joerg at alea.gnuu.de> [2006-07-08 11:31]:
> Rafael Laboissiere schrieb am Sat 08. Jul, 10:27 (+0200):
> > On the sad side, my personal configuration is now broken with these
> > uploads, so that I had to put the packages in my system on hold:
>
> Can you give us more details?
Jed does not initialize correctly for me with the new package. I did not
investigated the problem further, since I do not have much time for this
now. I simply reverted the packages to the previous versions in unstable
and put them on hold. I will probably get to this during the next month
or so.
> > Another thing that has to be done is cleaning up the huge list of bugs
> > against the packages, in particular the jed package:
> >
> > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=jed
> > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=jed-extra
> >
> > Many of them are already tagged fixed-in-experimental and should be close
> > by hand.
>
> No. Don't do this! This must happen automaticly with the upload.
> Otherwise we did something wrong in the changelog.
This has nothing to do with debian/changelog but with the .changes file,
which must contain the appropriate "Closes:" field. (See
http://lists.debian.org/debian-devel-changes/2006/07/msg00682.html)
This is obtained by using the option -v0.99.16-6 to dpkg-buildpackage,
which I have not done for the upload of 0.99.18-2. I did it for version
0.99.18-3, which was just uploaded.
Thanks, Jörg, for the heads up. I learned two things today about Debian
packaging.
--
Rafael
More information about the Pkg-jed-devel
mailing list