** Changed in: spice (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450043
Title:
spice package for trusty contains a malformed patch
To manage notif
** Branch linked: lp:ubuntu/trusty-proposed/spice
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450043
Title:
spice package for trusty contains a malformed patch
To manage notifications about this
I verified this using the test case of 'apt-get source spice'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450043
Title:
spice package for trusty contains a malformed patch
To manage notificatio
This bug was fixed in the package spice - 0.12.4-0nocelt2ubuntu1
---
spice (0.12.4-0nocelt2ubuntu1) trusty-proposed; urgency=medium
[Gregory Boyce]
* Fix newline-damaged patch (LP: #1450043)
-- Serge Hallyn Mon, 04 May 2015 10:47:58
-0500
** Changed in: spice (Ubuntu Trusty)
The patches can be applied and removed now
ubuntu@trusty-affinity:~/spice-0.12.4$ quilt push -a
File series fully applied, ends at patch
fix-buffer-overflow-when-decrypting-client-spice-ticket.patch
ubuntu@trusty-affinity:~/spice-0.12.4$ quilt pop -a
Removing patch fix-buffer-overflow-when-decryp
Thanks Brian. It's not in proposed yet, but the package itself extracts
fine.
On Fri, May 8, 2015 at 5:20 PM Brian Murray wrote:
> Hello Gregory, or anyone else affected,
>
> Accepted spice into trusty-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+so
Hello Gregory, or anyone else affected,
Accepted spice into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/spice/0.12.4-0nocelt2ubuntu1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
** Also affects: spice (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450043
Title:
spice package for trusty contains a malformed patch
T
** Tags added: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450043
Title:
spice package for trusty contains a malformed patch
To manage notifications about this bug go to:
https://bugs.laun
** Description changed:
Impact: the package cannot be unpacked (patches do not apply)
Devel fix: the patch is dropped (applied upstream)
stable fix: fix the newline damage in the patch
test case: apt-get source spice (on a trusty machine)
- regression
** Description changed:
+
+ Impact: the package cannot be unpacked (patches do not apply)
+ Devel fix: the patch is dropped (applied upstream)
+ stable fix: fix the newline damage in the patch
+ test case: apt-get source spice (on a trusty machine)
+ regression
** Changed in: spice (Ubuntu)
Status: Incomplete => Triaged
** Changed in: spice (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450043
Title:
spice
The attachment "spice-newlinefix.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian
The impact on Trusty users is that if they need to extract the sources
in order to view them or rebuild them, they would not be able to. In my
case I needed to rebuild the source. The binary packages themselves are
fine.
The chance of regression in this case is very minimal if the missing
newlin
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
> This is fixed in later releases by removing the specific patch, but it
would be useful for the Trusty package to be fixed.
Why? What is the impact to Trusty users?
To update a package in Trusty the procedure is
15 matches
Mail list logo