** Changed in: debian
Status: New => 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/242043
Title:
[needs-packaging] read-edid-2.0.0 for amd64
To manage notifications about this b
** Bug watch added: Debian Bug tracker #502125
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502125
--
[needs-packaging] read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Branch linked: lp:ubuntu/read-edid
--
[needs-packaging] read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
** Branch linked: lp:ubuntu/karmic/read-edid
--
[needs-packaging] read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This bug was fixed in the package read-edid - 2.0.0-1ubuntu1
---
read-edid (2.0.0-1ubuntu1) karmic; urgency=low
* debian/{control,rules}, Makefile.am:: build amd64 and lpia with
libx86-dev (LP: #242043, debian bug 534742).
-- Kees CookFri, 26 Jun 2009 11:31:52 -0700
** Ch
** Summary changed:
- [needs-packaging} read-edid-2.0.0 for amd64
+ [needs-packaging] read-edid-2.0.0 for amd64
--
[needs-packaging] read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
> What I'm quite failing to understand is the original bug description. I might
> be wrong, but I doubt that
> dpkg-reconfigure xserver-xorg has anything to do with read-edid (as read-edid
> is universe... so it can't
> be automatically available for xserver).
I am sure that "dpkg-reconfigure xs
TJ, did you decide not to go ahead with this?
--
[needs-packaging} read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
setting to confirmed based on my recent ACK #2 (and no opposition).
Please go ahead.
** Changed in: read-edid (Ubuntu)
Status: New => Confirmed
--
[needs-packaging} read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification because you are a membe
** Tags added: edid
--
[needs-packaging} read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/
Thanks for testing.
No, the difference (address of vga Bios) is not a problem, that's quite
expected actually (don't ask, and just don't dare to look at libx86
*how* it handles graphic bios calls, you might be frightened *g*...).
What I'm quite failing to understand is the original bug descriptio
I also tested on another computer, a Dell Optiplex SX280 USFF. Basically
the same results. Identical STDOUT from get-edid and parse-edid, but a
similar difference in STDERR:
$ diff get-edid-1.4.err get-edid-2.0.err
1c1
< get-edid: get-edid version 1.4.1
---
> get-edid: get-edid version 2.0.0
9c9
<
I've tested the read-edid from the PPA (read-
edid_2.0.0-0ubuntu1~tj~ppa1j_i386.deb) and it seems to work fine. I
noticed a difference on STDERR from get-edid though:
$ diff get-edid-1.4.err get-edid-2.0.err1c1
< get-edid: get-edid version 1.4.1
---
> get-edid: get-edid version 2.0.0
9c9
< V
I'd like to see testing from more than one person.
--
[needs-packaging} read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
I'm fine with it.
ACK #1
** Changed in: read-edid (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
Status: In Progress => New
--
[needs-packaging} read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification because you are a member of U
On Wed, 2009-03-18 at 06:40 +, Iulian Udrea wrote:
> Are these rdepends affected by this upgrade?
>
> Reverse Depends:
> xdebconfigurator
> lm-sensors
>
> It looks like xdebconfigurator is not using read-edid by default. It
> just suggests read-edid now.
That's correct, and it detects t
Are these rdepends affected by this upgrade?
Reverse Depends:
xdebconfigurator
lm-sensors
It looks like xdebconfigurator is not using read-edid by default. It
just suggests read-edid now.
--
[needs-packaging} read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received thi
= Install log =
sudo apt-get install read-edid
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed
read-edid
0 upgraded, 1 newly installed, 0 to remove and 94 not upgraded.
Need to get 0B/12.8kB of archives.
** Attachment added: "pbuilder jaunty amd64 build log"
http://launchpadlibrarian.net/24017675/read-edid-2.0.0-0ubuntu1%7Etj%7Eppa1j-jaunty-amd64-2009-03-13_21-00-50.log
--
[needs-packaging} read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification be
Feature Freeze Exception request
* Upstream added support for amd64 architecture (using libx86) and has
a new maintainer
** Attachment added: "FFE ChangeLog"
http://launchpadlibrarian.net/24017626/ffe-ChangeLog.patch
--
[needs-packaging} read-edid-2.0.0 for amd64
https://bugs.launchpad.ne
Please test the package in my PPA and report back.
https://launchpad.net/~intuitivenipple/+archive/ppa/
--
[needs-packaging} read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm working on the package. I'll have a test package in my PPA shortly.
** Changed in: read-edid (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
Status: Triaged => In Progress
--
[needs-packaging} read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received t
Successfully build-tested for Hardy, Intrepid, Jaunty (i386 and amd64).
Runs on Jaunty amd64 (no results since Nvidia GeForce 7600 + Sony FE41Z don't
provide EDID output).
Runs on Jaunty i386 (no results since Intel i815M + Sony SRX51 TFT don't
provide EDID output).
--
[needs-packaging} read-e
** Changed in: debian
Status: Unknown => New
--
[needs-packaging} read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
24 matches
Mail list logo
