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

Bug#699344: marked as done (unblock: sendmail/8.14.4-4)

Your message dated Sat, 13 Apr 2013 12:26:42 +0100
with message-id <1365852402.4627.23.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#699344: unblock: sendmail/8.14.4-4
has caused the Debian Bug report #699344,
regarding unblock: sendmail/8.14.4-4
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.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
699344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699344
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Maybe unblock package sendmail

sendmail in squeeze and testing creates a big mess with symlinks in
/usr/share/doc (and the same in /usr/share/bug, although less noticable)
with the following problems:
* non-strict dependencies on the only package with a copyright file, so
  many packages may end up without a copyright file installed at all
* installing files over the symlinks, silently overwriting other
  packages (from src:sendmail)

In my changes Thomas and I concentrated on cleaning up this symlink mess
by having /usr/share/doc/$PACKAGE a real directory again everywhere (and
clean up on package upgrades as good as possible) and putting the
documentation in th eappropriate packages.

The raw diffstat from 8.14.4-2.1 is huge:

 137 files changed, 1589 insertions(+), 19859 deletions(-)

but after excluding the following:
* autotools stuff
* deletion of generated files (most of debian/ gets generated in some
  not obvious way, and deleting all files from the package that are
  regenerated anyway gives me a chance to find the files that should be
  modified to actually generate some effect.
* deletion of obsolete files (for a previous SOVERSION)
* renaming README.Debian.$PACKAGE => $PACKAGE.README.Debian
we get down to

 debian/Debian-specific                       |    5 +-
 debian/README.Debian.libmilter-dev           |    2 +-
 debian/build/debian/control.m4.in            |   11 ++--
 debian/build/debian/libmilter-dbg.dirs.in    |    2 -
 debian/build/debian/libmilter-dev.dirs.in    |    2 -
 debian/build/debian/libmilter-dev.links.in   |    1 -
 debian/build/debian/libmilter-dev.postrm.in  |   53 -------------------
 debian/build/debian/libmilter-dev.preinst.in |   59 ++++-----------------
 debian/build/debian/libmilter.dirs.in        |    2 -
 debian/build/debian/libmilter.links.in       |    1 -
 debian/build/debian/libmilter.postrm.in      |   53 -------------------
 debian/build/debian/libmilter.preinst.in     |   59 ++++-----------------
 debian/build/debian/rmail.dirs.in            |    2 -
 debian/build/debian/rmail.postrm.in          |   53 -------------------
 debian/build/debian/rmail.preinst.in         |   59 ++++-----------------
 debian/build/debian/sendmail-base.dirs.in    |    3 --
 debian/build/debian/sendmail-base.postrm.in  |    1 -
 debian/build/debian/sendmail-base.preinst.in |   41 ++++++---------
 debian/build/debian/sendmail-bin.dirs.in     |    4 +-
 debian/build/debian/sendmail-bin.postrm.in   |    3 ++
 debian/build/debian/sendmail-cf.dirs.in      |    2 -
 debian/build/debian/sendmail-cf.postrm.in    |    4 --
 debian/build/debian/sendmail-cf.preinst.in   |   59 ++++-----------------
 debian/build/debian/sendmail-doc.dirs.in     |    2 -
 debian/build/debian/sendmail-doc.postrm.in   |   53 -------------------
 debian/build/debian/sendmail-doc.preinst.in  |   71 ++++++++------------------
 debian/build/debian/sendmail.dirs.in         |    2 -
 debian/build/debian/sensible-mda.dirs.in     |    2 -
 debian/build/debian/sensible-mda.postrm.in   |   53 -------------------
 debian/build/debian/sensible-mda.preinst.in  |   59 ++++-----------------
 debian/changelog                             |   42 +++++++++++++++
 debian/configure.ac                          |   11 ----
 debian/control                               |    9 ++--
 debian/local/Makefile.in                     |    2 +-
 debian/rmail.links                           |    1 -
 debian/rules                                 |   36 +++++++++----
 debian/sendmail-base.links                   |    1 -
 debian/sendmail-base.maintscript             |    1 +
 debian/sendmail-bin.links                    |    1 -
 debian/sendmail-cf.links                     |    1 -
 debian/sendmail-doc.docs                     |    1 -
 debian/sensible-mda.links                    |    1 -
 42 files changed, 174 insertions(+), 656 deletions(-)

Note: this *includes* the removal of a lot of ancient maintainer
script code that set up the symlink mess I'm now cleaning up.

For an inspection of the individual changes performed I'd recommend to
look at the new GIT repository. If anyone is interested, I can push the
"cleaned up" branch I used for the filtered diff.
  git://git.debian.org/git/collab-maint/sendmail.git

There is another RC bug open against sendmail that I cannot fix as it
will require some knowledge of sendmail ... I have only been looking at
the packaging.

Anyway, I'd like to see this getting updated in wheezy for cleaning up
the symlink and copyright mess we currently have there.

Andreas

unblock sendmail/8.14.4-3

Attachment: 8.14.4-3.filtered.diff.gz
Description: GNU Zip compressed data


--- End Message ---
--- Begin Message --- 
On Wed, 2013-04-10 at 20:21 +0200, Andreas Beckmann wrote:
> In case an upload to wheezy is needed later on (t-p-u or security) that
> changes something that requires regenerating debian/configure, this
> upload will need to add several fixes to the build system because that
> does currently not work correctly. Regenerating debian/configure
> succeeds in wheezy (but it is completely undocumented how to do this
> correctly, I used the recipe I added to debian/rules in my -3 upload) ,
> but the freshly generated configure script will fail to run properly.

"Yay". Even so, it's still going to require manual work on the part of
whoever's performing the upload.

I'm not hugely happy about the size of the fixes, but have unblocked it
on the basis that it seems not to have exploded in sid and on the
assumption that you've done extensive upgrade testing...

Regards,

Adam

--- End Message ---
Reply to: