[SRU] wordnet 1:3.0-2 in Gutsy was not built with debian/patches applied as intended.

Bug #275122 reported by Stefan Lesicnik
8
Affects Status Importance Assigned to Milestone
wordnet (Ubuntu)
Fix Released
Undecided
Unassigned
Gutsy
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: wordnet

I was testing security patches to Wordnet in Gutsy when I noticed that the wordnet Gutsy package was built with none of the debian/patches applied to the source.

The problem lies in the fact that it uses cdbs and cdbs looks for debian/patches and the package in this case only contains debian/patch.

I noticed this because none of my new security patches were being applied.

After renaming debian/patch to debian/patches the patches were applied. I had to remove the debian/patches/src_wn_c.diff as it was already applied upstream in the source.

I believe this is something that should get fixed as it was always intended to be included.

Patches that adjust the resource directory for the dictionary file and license file.
Allow grind to enable building database from plain ASCII sources.
Enable usage of wordnet with dict.
Fixed string constant in src/stubs.c - Debian #389415

I would like this SRU backported so I can apply the security fixes. https://bugs.edge.launchpad.net/ubuntu/hardy/+source/wordnet/+bug/267067

Revision history for this message
Stefan Lesicnik (stefanlsd) wrote :

Please find attached debdiff to correct above behaviour.

This debdiff was built and tested with pbuilder and a Gutsy chroot.

Arnaud Soyez (weboide)
Changed in wordnet:
status: New → Confirmed
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
Gutsy task.

Changed in wordnet (Ubuntu Gutsy):
status: New → Won't Fix
Revision history for this message
Phillip Susi (psusi) wrote :

It looks like this was fixed.

Changed in wordnet (Ubuntu):
status: Confirmed → 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.