[MIR] libvisio
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| libvisio (Ubuntu) |
Undecided
|
Unassigned |
Bug Description
rationale: needed by LibreOffice, a core app. In Quantal we used the internal version of libvisio and shipped it inside the LibreOffice package, so the code is in main already anyway.
Benjamin Drung (bdrung) wrote : | #2 |
Identical comments as for libcdr MIR bug: The hardening-
Judging from the Email exchange with Rene hardening-
@bdrung: Can we unblock this as your other changes are helpful, but no blockers?
Benjamin Drung (bdrung) wrote : | #4 |
@Björn: It's not my decision. It's the decision of the MIR team.
@MIR team: Is it okay to wait for the next Debian upload to get hardening-
Benjamin Drung (bdrung) wrote : | #5 |
I have uploaded libvisio 0.0.24-1ubuntu1 which fixes the hardening-
Matthias Klose (doko) wrote : | #6 |
Override component to main
libvisio 0.0.24-1ubuntu2 in raring: universe/libs -> main
libvisio-0.0-0 0.0.24-1ubuntu2 in raring amd64: universe/
libvisio-0.0-0 0.0.24-1ubuntu2 in raring armhf: universe/
libvisio-0.0-0 0.0.24-1ubuntu2 in raring i386: universe/
libvisio-0.0-0 0.0.24-1ubuntu2 in raring powerpc: universe/
libvisio-dev 0.0.24-1ubuntu2 in raring amd64: universe/
libvisio-dev 0.0.24-1ubuntu2 in raring armhf: universe/
libvisio-dev 0.0.24-1ubuntu2 in raring i386: universe/
libvisio-dev 0.0.24-1ubuntu2 in raring powerpc: universe/
libvisio-doc 0.0.24-1ubuntu2 in raring amd64: universe/
libvisio-doc 0.0.24-1ubuntu2 in raring armhf: universe/
libvisio-doc 0.0.24-1ubuntu2 in raring i386: universe/
libvisio-doc 0.0.24-1ubuntu2 in raring powerpc: universe/
libvisio-tools 0.0.24-1ubuntu2 in raring amd64: universe/
libvisio-tools 0.0.24-1ubuntu2 in raring armhf: universe/
libvisio-tools 0.0.24-1ubuntu2 in raring i386: universe/
libvisio-tools 0.0.24-1ubuntu2 in raring powerpc: universe/
Changed in libvisio (Ubuntu): | |
status: | Incomplete → Fix Released |
Identical comments as from libcdr MIR bug 1124074 (same Debian packager and upstream authors, so makes sense I guess):
-Simple, modern packaging
-No delta
-No test suite
-No symbols file, but it's C++, so that's understandable
-debian/copyright file is a little malformed (missing license stanza), but that's an issue for NEW, not for MIR. Plus, this is from Debian so not worth a delta.
-Would be nice to see a bug subscriber
-This would normally need a security review, since it's a file parser, but since it's been in main, I'll skip that step. Splitting it out actually makes it easier to handle security issues.
*However*, it does have the lintian warning hardening- no-fortify- functions. Can you just check if that warning is a false or true positive? Otherwise, approved.