Please upload emacs22 22.1-0ubuntu10

Bug #172389 reported by Jamie Raymond
6
Affects Status Importance Assigned to Milestone
emacs22 (Ubuntu)
Fix Released
Undecided
Michael Olson
Hardy
Fix Released
Undecided
Michael Olson

Bug Description

You can see that there is a conflict between emacs22-common_22.1-0ubuntu5.1 and emacs22-common-non-dfsg. I had to uninstall emacs22-common-non-dfsg to get the dist-upgrade to complete.

Preparing to replace emacs22-common 22.1-0ubuntu5 (using .../emacs22-common_22.1-0ubuntu5.1_all.deb) ...
Unpacking replacement emacs22-common ...
dpkg: error processing /var/cache/apt/archives/emacs22-common_22.1-0ubuntu5.1_all.deb (--unpack):
 trying to overwrite `/usr/share/emacs/22.1/etc/CENSORSHIP', which is also in package emacs22-common-non-dfsg
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/emacs22-common_22.1-0ubuntu5.1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:

dpkg: dependency problems prevent configuration of emacs22-el:
 emacs22-el depends on emacs22-common (= 22.1-0ubuntu5.1); however:
  Version of emacs22-common on system is 22.1-0ubuntu5.
dpkg: error processing emacs22-el (--configure):
 dependency problems - leaving unconfigured

Related branches

CVE References

Revision history for this message
Michael Olson (mwolson) wrote : Re: Please remove emacs22-common-non-dfsg from the archive

The emacs22-common-non-dfsg package is not needed at all. It is an artifact from Debian's emacs22 package.

Archive admins, please remove emacs22-common-non-dfsg.

Revision history for this message
Martin Pitt (pitti) wrote :

To reduce deviation from Debian, shouldn't we rather promote the emacs22-non-dfsg source and binaries to main, add a dependency from our emacs22 package and drop the files from our emacs22? If I just remove the package, then upgrades will still break (since it's not automatically removed on upgrades), so you need a Conflicts:/Replaces: on emacs22 anyway. However, using the Debian packages seems much more sensible to me.

Changed in emacs22:
assignee: nobody → mwolson
status: New → Incomplete
Revision history for this message
Martin Pitt (pitti) wrote :

If you prefer keeping the current structure, please add the Conflicts/Replaces, then I can remove the package.

Revision history for this message
Michael Olson (mwolson) wrote :

No, we should absolutely not use Debian's packaging :^) .

I'll add the necessary Conflicts/Replaces lines to our own packaging in the near future, and will reply to this bug again when I have done so.

Revision history for this message
Jonathan Riddell (jr) wrote :

It would be helpful if you said why we should not use Debian's packaging.

Revision history for this message
Michael Olson (mwolson) wrote :

I've explained my reasons for creating this separate package in the #ubuntu-devel channel earlier in the year. It would seem that people need a hard-copy version of these reasons, so I'm going to add something to the wiki to cover this. I'm going to shoot for tomorrow night to both write this up and check in a fixed package.

Revision history for this message
Michael Olson (mwolson) wrote :

Here's my write-up on why I want to keep the packages separate: <https://wiki.ubuntu.com/MichaelOlson/WhyDifferentEmacs>. I ran out of time on the Conflicts/Replaces line, so that will have to wait until a week or two, due to holiday traveling.

Revision history for this message
Martin Pitt (pitti) wrote :

Thanks for the write-up. I added that link and the package to the sync-blacklist, so that it won't turn up again and removed emacs22-non-dfsg.

Will remove the following packages from hardy:

emacs22-common-non-dfsg | 22.1+1-1 | amd64, hppa, i386, ia64, lpia, powerpc, sparc
emacs22-non-dfsg | 22.1+1-1 | source

------------------- Reason -------------------
(pitti) Ubuntu emacs22 has all the docs, maintained independently
----------------------------------------------

Going to remove the packages now.

Remaining task is now to add the Conflicts/Replaces:

Changed in emacs22:
status: Incomplete → Triaged
Revision history for this message
Michael Olson (mwolson) wrote : Re: Missing Conflicts:/Replaces: to emacs22-common-non-dfsg

Here's the change which fixes this, along with several other bugs. Debdiff attached.

emacs22 (22.1-0ubuntu10) hardy; urgency=low

  * debian/control: Conflict and Replace emacs22-common-non-dfsg
    (LP: #172389). Thanks to Jamie Raymond for the report.
  * debian/emacs.prerm: Remove alternatives in reverse creation order
    (LP: #162932). Thanks to James Troup for the report.
  * debian/emacs.menu.in:
    - Use Applications/Editors instead of Apps/Editors as per menu policy.
    - Move menu definition for "emacs -nw" here, and delete
      emacs-common.menu.in. This way, if the user installs emacs22-nox,
      they will not have an unwanted menu item added (LP: #157984).
      Thanks to Ryan for the report.
  * debian/patches:
    - feature-spell-warning.diff: New patch that displays a warning when
      spell is used and the spell binary is not installed (LP: #154989).
    - fix-comint-sudo.diff: New patch that causes comint to recognize the
      sudo prompt used by Ubuntu (LP: #162890).
    - Rename CVE-2007-6109.diff to fix-format-overflow.diff so that it
      shows up in README.Debian. Add patch header as well.
    - fix-local-vars-security.diff: Add CVE ID.
  * debian/README.in:
    - Place Ubuntu rather than Debian in the header line.
    - Add link to further explanation for why we use a separate package.
    - Clarify what "this package" means.
    - Together this fixes LP: #180164. Thanks to era for the report and
      patch.
  * debian/rules: Don't build debian/emacs-common.menu and don't call
    dh_installmenu -i.

 -- Michael W. Olson (GNU address) <email address hidden> Tue, 08 Jan 2008 18:00:57 -0500

Changed in emacs22:
status: Triaged → Fix Committed
Revision history for this message
Daniel Holbach (dholbach) wrote :

Michael (mvo): can you take a look at it?

Revision history for this message
Michael Olson (mwolson) wrote :

I'm pinging the sponsors for main again, because it has been a week since there was last activity on this upload request, and nearly two weeks since the upload was requested.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package emacs22 - 22.1-0ubuntu10

---------------
emacs22 (22.1-0ubuntu10) hardy; urgency=low

  * debian/control: Conflict and Replace emacs22-common-non-dfsg
    (LP: #172389). Thanks to Jamie Raymond for the report.
  * debian/emacs.prerm: Remove alternatives in reverse creation order
    (LP: #162932). Thanks to James Troup for the report.
  * debian/emacs.menu.in:
    - Use Applications/Editors instead of Apps/Editors as per menu policy.
    - Move menu definition for "emacs -nw" here, and delete
      emacs-common.menu.in. This way, if the user installs emacs22-nox,
      they will not have an unwanted menu item added (LP: #157984).
      Thanks to Ryan for the report.
  * debian/patches:
    - feature-spell-warning.diff: New patch that displays a warning when
      spell is used and the spell binary is not installed (LP: #154989).
    - fix-comint-sudo.diff: New patch that causes comint to recognize the
      sudo prompt used by Ubuntu (LP: #162890).
    - Rename CVE-2007-6109.diff to fix-format-overflow.diff so that it
      shows up in README.Debian. Add patch header as well.
    - fix-local-vars-security.diff: Add CVE ID.
  * debian/README.in:
    - Place Ubuntu rather than Debian in the header line.
    - Add link to further explanation for why we use a separate package.
    - Clarify what "this package" means.
    - Together this fixes LP: #180164. Thanks to era for the report and
      patch.
  * debian/rules: Don't build debian/emacs-common.menu and don't call
    dh_installmenu -i.

 -- <email address hidden> (Michael W. Olson (GNU address)) Tue, 08 Jan 2008 18:00:57 -0500

Changed in emacs22:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.