Looks like we're not going to be able to drop -dbg packages, but I think
fabo from Debian said that they were picking up some of our -dbg work
for Qt 4.6. This can be closed, anyways.
** Changed in: qt4-x11 (Ubuntu)
Status: Triaged => Fix Released
--
Packages have invalid .gnu_debuglink
h
I saw that the patch was integrated in the last package 4.5.3 uploaded
for karmic, note however that the source don't compile because the patch
still as the old path in it, i.e.
+--- qt4-x11-4.4.3.orig/mkspecs/common/linux.conf 2008-12-31
11:20:45.0 +0100
qt4-x11-4.4.3/mkspecs/
I've uploaded this debdiff following review by Bo Thorsten. Thanks
Martin von Gagern. We'll revisit this in Karmic.
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
OK, yet another debdiff. Revertet to -dbg packages (including a few
extra ones), dropped the lintian overrides, and also completed the
mapping from non-debug to debug packages, as the implicit cdbs build
logic didn't work as I originally expected. Currently queued in my ppa,
let's see...
** Attach
Jonathan Thomas [2009-03-18 12:23 -]:
> If we dropped the dbg packages now, that would mean we would have to
> drop the dbg packages from every KDE module since kdelibs5-dbg depends
> on the qt4 -dbg packages, and every kde dbg package depends on
> kdelibs5-dbg. That would be a somewhat large c
If we dropped the dbg packages now, that would mean we would have to
drop the dbg packages from every KDE module since kdelibs5-dbg depends
on the qt4 -dbg packages, and every kde dbg package depends on
kdelibs5-dbg. That would be a somewhat large change this late in the
cycle, and it would create
It took me a while to find the relevant documentation about pkg-create-dbgsym:
https://launchpad.net/pkg-create-dbgsym
https://wiki.ubuntu.com/AptElfDebugSymbols
https://launchpad.net/ubuntu/+spec/apt-get-debug-symbols
If this is really the way to go, some reference in
https://wiki.ubuntu.com/Pack
Martin, thanks for your work on this. Some questions/notes:
- Do we really need to explicitly build -dbg packages, given that pkg-
create-dbgsym already builds them for every package in the archive
anyway? The long-term goal is actually to remove -dbg packages entirely
(and we are pondering doing
I created an updated patch for Jaunty. It failed to build on my PPA,
though, due to some PostgreSQL-related issue that seems unrelated to my
patch, but makes testing a bit difficult. I'll try a local build
tomorrow, I think. The attached patch introduces three new debug
packages, for qt4-dev-tools
> The resulting list of debug symbol files looks somewhat longer, needs
to be invedtigated still.
I've investigated this now. The original debug packages only contained
debug symbols for libraries. With my patch in place, it contains debug
symbols for binaries as well. Debug files for the followin
Ah, indeed, I overlooked that. I apologize.
Debdiff:
http://launchpadlibrarian.net/20834194/qt4-x11_4.4.3-0ubuntu1_4.4.3-0ubuntu1.2%7Eppa0i.diff.gz
I subscribed the sponsoring team.
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
You received this bug notification
Do I understand you correctly that the diff in my PPA is enough for now,
rendering Marco's request for a patch obsolete?
So now I wait for some sponsor to have a look at this, and work out the next
steps based on his opinion?
The version against which my patch was created is no longer current. Sh
The fixing is described in comments 12 through 15. Martin's PPA has it
in patch form (debdiff I think):
http://launchpadlibrarian.net/20834194/qt4-x11_4.4.3-0ubuntu1_4.4.3-0ubuntu1.2~ppa0i.diff.gz
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
You received this bug
Marco, there is no patch for this problem yet, so your comment about
sponsoring is irrelevant here.
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
Please attach to this report a patch following the instructions reported here:
https://wiki.ubuntu.com/Bugs/HowToFix.
Then subscribe to this report ubuntu-main-sponsors.
Thanks for your work.
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
You received this bug not
** Changed in: qt4-x11 (Ubuntu)
Importance: Undecided => Medium
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
--
kubuntu-bugs mailing list
k
Can some Ubuntu qt packager please have a look at this?
I've put quite a lot of personal time, and even more computer runtime,
into trying to get this fixed. I've posted the relevant modifications as
well as instructions how to integrate them. I'm clobbering my PPA with
almost 1 GiB of packages fo
Complete list of my modifications:
* Modified debian/rules according to attached script.
* Added nostrip patch to debian patch series
* rm debian/*-dbg.install
* sed -i 's: \./\(.*\)\.debug: ./usr/lib/debug/\1:' debian/*-dbg.lintian
* Updated changelog :-)
I could have wrapped all this in a single
This patch can be added to the debian patch series in order to prevent
the qt build system from stripping objects.
** Attachment added: "nostrip.diff"
http://launchpadlibrarian.net/20842185/bug261380-nostrip.diff
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
Y
** Attachment added: "rules.diff"
http://launchpadlibrarian.net/20842168/bug261380-rules.diff
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
I've got a proposed version in my PPA, with debug packages managed by dh_strip,
not the qt build process.
See https://launchpad.net/~gagern/+archive
Adding CONFIG+=nostrip to QMAKE_VARS in the configure script didn't
work, so I added it to some other spec file. I also found that cdbs
provides ela
Still not fixed in 4.4.3-1ubuntu4_i386 for Jaunty.
I had a typo in comment 9; s/"dbg -x"/"dpkg -x"/
To get some traction here, I think the following should work:
1. (debian/patches/) patch configure to include "CONFIG+=nostrip" in QMAKE_VARS
2. (debian/rules) pass "-no-separate-debug-info" to the
Is there no fix for this in hardy?
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.u
It isn't necessary to update to Jaunty just to check this. It would be
enough to get a library package unpacked so you can objdump it, and to
compare the file name mentioned there with those from the dbg package
file list. "dbg -x" would do the former, while the latter might be
possible without eve
Oops: forgot the link:
https://launchpad.net/ubuntu/+source/qt4-x11/4.4.3-1ubuntu1
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
--
kubuntu-bug
Riddell just merged Qt4 for Jaunty. I wonder if the merge fixed this,
although nobody should recommend anybody upgrading to Jaunty this early
on to test.
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
You received this bug notification because you are a member of K
Another observation: Debian (tested with sid packages) also uses Fedora layout
for qt4-x11, but doesn't seem to suffer from broken debug links. So what do
they differently?
1. mention *.debug in debian/not-installed
2. some differences in debian/rules that I don't completely understand
3. several
The crc32 sum seems to be wrong as well. Therefore simply
moving/renaming the files won't solve the issue.
To use the libQtGui.so.4.4.3 from 4.4.3-0ubuntu1 on i386 as an example:
here /usr/lib/libQtGui.so.4.4.3.debug has a crc32 value of 0x61598269,
computed using the algorithm given in the gdb ma
Confirming for 4.4.3-0ubuntu1 on Intrepid.
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
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://l
cf. for example http://packages.debian.org/sid/amd64/libc6-dbg/filelist
and http://packages.debian.org/sid/amd64/libglib2.0-0-dbg/filelist. I
deal with -dbg packages quite a lot, and in fact qt4-x11 is the only
package I encountered so far which breaks this schema.
--
Packages have invalid .gnu_d
In general the links are not invalid, but they look just fine as far as
I can see. Fedora's debug symbol packages are structured differently,
which is why their debug link needs to point to "libQtGui.so.4.3.debug".
However, in Debian/Ubuntu, both the explicit -dbg packages, as well as
the automati
Martin could you provide some insight here?
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
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://
32 matches
Mail list logo
