Ubuntu
cvs package

upgrading cvs to 1:1.12.13-12 causes FTBFS on kbuild

Bug #296453 reported by Mario Limonciello
4
Affects Status Importance Assigned to Milestone
cvs (Ubuntu)
Fix Released
High
Kees Cook
kbuild (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: cvs

If kbuild is built against cvs 1:1.12.13-11, it builds properly. Trying to build it with cvs 1:1.12.13-12 causes it to FTBFS with the attached build log:

Revision history for this message
Mario Limonciello (superm1) wrote :
Revision history for this message
Mario Limonciello (superm1) wrote :

Additionally, it looks like CVS is entirely broken on it's own.

Try running "cvs status":

Revision history for this message
Kees Cook (kees) wrote :

I can't reproduce this failure (kbuild built fine for me). Is there a minimal test-case for cvs that shows this problem?

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

This bug was fixed in the package cvs - 1:1.12.13-12ubuntu1

---------------
cvs (1:1.12.13-12ubuntu1) jaunty; urgency=low

  * debian/patches/99ubuntu001-no-snprintf.diff: Don't build vasnprintf
    strings with snprintf to avoid %n in writable memory (LP: #296453).

 -- Kees Cook <email address hidden> Mon, 10 Nov 2008 15:01:40 -0800

Changed in cvs:
status: New → Fix Released
Kees Cook (kees)
Changed in cvs:
assignee: nobody → kees
importance: Undecided → High
status: Fix Released → New
Mario Limonciello (superm1)
Changed in cvs:
status: New → Fix Released
Felix Geyer (debfx)
Changed in kbuild (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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