Bug#735488: Qt4 in arm64: wrap up of the current situation
On Monday 27 January 2014 22:32:01 Wookey wrote: [snip] > > Wookey: are there any arm64 porterboxes available? I can't promise > > anything, but maybe at some point I could help... > > Not yet. No. And I don't yet know when there might be. 'In time for > Jessie, hopefully' is the only clue I've had so far from people who will > be in a position to supply one. If you need builds done there are a > couple of DDs who can get access (Riku and Fathi). I can do it > indirectly. Probably best to pester me. I realise this is not at all > convenient but access is very strictly controlled at the moment (because > lawyers don't understand how work actually gets done). He, lawyers :) Don't worry, I get the idea :) To fully push the patches upstream we will need the -fpermisive stuff properly addressed though :-/ -- Why should I care about my chatter from yesterday? Nothing prevents me from becoming wiser. Konrad Adenauer, former German chancellor. http://lwn.net/SubscriberLink/397422/60a270d48f933c67/ Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#735488: Qt4 in arm64: wrap up of the current situation
On Monday 27 January 2014 18:20:21 Wookey wrote: [snip] > > Qt4 patches are not accepted upstream. All new code has to go to Qt5 and > > since 5.2.0 QAtomics stuff is using std::atomic so compiler takes care > > of it and there is no code for separate architectures. > > Are QT4 patches going to be accepted at some point or will distros have > to carry an arm64 patch for QT4 as long as it remains supported? Thiago just replied that while technically is a new feature and thus should not be applied to Qt4, distros and most probably other users will use them, so better to accept them. Wookey: are there any arm64 porterboxes available? I can't promise anything, but maybe at some point I could help... Kinds regards, Lisandro. -- http://xkcd.com/162/ Siempre quise una novia así :-) Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#735488: Qt4 in arm64: wrap up of the current situation
On Monday 27 January 2014 19:29:04 Marcin Juszkiewicz wrote: [snip] > > Are QT4 patches going to be accepted at some point or will distros have > > to carry an arm64 patch for QT4 as long as it remains supported? > > Ask in https://bugreports.qt-project.org/browse/QTBUG-35442 please I'll take care of asking. Thanks! -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#735488: Qt4 in arm64: wrap up of the current situation
On Monday 27 January 2014 19:32:43 Marcin Juszkiewicz wrote: > W dniu 27.01.2014 19:14, Lisandro Damián Nicanor Pérez Meyer pisze: > > So what we are currently missing should be: > > > > - The copyright and license of the qatomic stuff. > > Author: Mark Salter > License: same as upstream one \o/ Thanks a lot! -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#735488: Qt4 in arm64: wrap up of the current situation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 W dniu 27.01.2014 19:14, Lisandro Damián Nicanor Pérez Meyer pisze: > So what we are currently missing should be: > > - The copyright and license of the qatomic stuff. Author: Mark Salter License: same as upstream one -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJS5qZHAAoJECbKqQEReiUeZPQQALLzIGAeCJtUDdk/yBoNv1dh T01VrWX8/aCW1n/DlgAdBGtZm8lTbL/29glib3qhoqLTHDvh4VmQ9kBRRt537vCt 7Qj/v3mDDmZYv5pAyReX7i0N8RRExKWk4alXnBJy62lP3TAGZar4VYjyU5STCIkK NVqs4oE1It38uQObdUaVoDynB0HP1rPsr9UHqZlT716QpORE2qh2PUFDZ4ACZHZh 7bAStNL/JOYqTEGolIm+q8kti3Ozkjx/EdnSjW3yHYy0Ih5PhTtVtqBeWEyv9CXw i5L1TKzV6XFlmm0qHvUHkTKQtidnnpO3/ew5E6tdz8oXVpo9prBVFpO6CE+FPvmn +N6tX+h44fjZ189b1+XB57Z7mV+PrRL6Wk60pKxrJrk5zp9scI0Bb/TEo1FkwPcA CioHrDxCFvywEN15LlUjNQgr2eeO6sPgfaXmrPQ9RAiSX1ojUb8h3BVbqVE8sQHr x1CugZvAGo4v7rSi7paZEGfJdHUWV8+FX/XmeddJq2kqA0icMYLPMPCVc+s7hy3m wLTyACVCFVdaoc6rau8V4pbMgEItvKXkiQueKe4KE5BLBXmVdkT5y+1ltubimrhY 44sQIR1py/gHwQSRrNZ85fio4DpVbzhqwFvAADlJZCbuKr9VNTt9tk9Fz55Gd3+3 LHb+qyxBhHE0vf3R5WN6 =w740 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52e6a64b.7060...@redhat.com
Bug#735488: Qt4 in arm64: wrap up of the current situation
W dniu 27.01.2014 19:20, Wookey pisze: > +++ Marcin Juszkiewicz [2014-01-27 17:41 +0100]: >>> - It uses linux-g++ instead of linux-g++-64. While that could be the best >>> fit, >>> it would be good to know why. >> >> Maybe it is because linux-g++ may use '-m64' argument for GCC which >> AArch64 does not support so build fails. > > I think this is correct. I recall hitting that issue. There was also > stuff to do with selecting /lib64 vs /lib IIRC. (/lib is correct for > arm64/aarch64). /lib or /lib64 is also distro choice. > Are QT4 patches going to be accepted at some point or will distros have > to carry an arm64 patch for QT4 as long as it remains supported? Ask in https://bugreports.qt-project.org/browse/QTBUG-35442 please -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52e6a570.3000...@redhat.com
Bug#735488: Qt4 in arm64: wrap up of the current situation
On Monday 27 January 2014 17:41:26 Marcin Juszkiewicz wrote: [snip] > > - It uses linux-g++ instead of linux-g++-64. While that could be the best > > fit, it would be good to know why. > > Maybe it is because linux-g++ may use '-m64' argument for GCC which > AArch64 does not support so build fails. Cool, thanks :) [snip] > If you need that for something: > > Author: Marcin Juszkiewicz based on > gtkwebkit changes by Riku Voipio > > License: same as upstream one Excellent! > > aarch64_fix_atomic_set.patch: > > - Copyright present. > > - Possibly needs the above patch applied. > > It requires aarch64.patch as it just change two lines. Yes, sadly we don't have the copyright for that yet :-( > > = Some extra remarks > > > > We need at least the proper copyright and license for the patches. In that > > way I'm able to apply them in the package and ping upstream wrt them. > > > > Of course, if the original author can push it to upstream's gerrit the > > better, because in case some objection arises I don't need to be in the > > middle as a (possibly noisy) proxy. > > Qt4 patches are not accepted upstream. All new code has to go to Qt5 and > since 5.2.0 QAtomics stuff is using std::atomic so compiler takes care > of it and there is no code for separate architectures. > > And all required patches were submitted - just one change to qtwebkit is > stuck in review. > > https://bugreports.qt-project.org/browse/QTBUG-35442 is upstream bug. Correct. So what we are currently missing should be: - The copyright and license of the qatomic stuff. - Fix the code that FTBFS without -fpermissive. Thanks for your input! Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#735488: Qt4 in arm64: wrap up of the current situation
+++ Marcin Juszkiewicz [2014-01-27 17:41 +0100]: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > W dniu 23.01.2014 18:57, Lisandro Damián Nicanor Pérez Meyer pisze: > > I've tried to summarize the current arm64 situation. The following are my > > conclusions, feel free to point if something is wrong, give more > > info/feedback, etc. > > As you know from my blog post [0] Qt/AArch64 patch has long history. > > 0. > http://marcin.juszkiewicz.com.pl/2014/01/20/the-story-of-qtaarch64-patching/ > > > = Stuff under debian/ > > > > - As explained in a mail before, we don't like the idea of passing > > -fpermissive as it can lead to very strange crashes. The code will need > > proper > > fixing. > > > > - We are building webkit with a separate source, -no-javascript-jit and the > > relevant webkit patches should be applied in src:qtwebkit. The relevant > > patches contained in the patch submitted by Wookey come from Riku Voipio > > and > > seems too similar to other patches we already have there, so it should not > > be > > a problem to apply them once we have Qt4 ready form arm64. > > > - It uses linux-g++ instead of linux-g++-64. While that could be the best > > fit, > > it would be good to know why. > > Maybe it is because linux-g++ may use '-m64' argument for GCC which > AArch64 does not support so build fails. I think this is correct. I recall hitting that issue. There was also stuff to do with selecting /lib64 vs /lib IIRC. (/lib is correct for arm64/aarch64). > > = Code patches > > > > aarch64.patch: > > - *No copyright* nor license. We need this at least to be able to apply it > > and > > ask upstream if they see it fit. There's the chance that some code comes > > from > > Ubuntu people. > > > > - Webkit stuff: as described above. > > If you need that for something: > > Author: Marcin Juszkiewicz based on > gtkwebkit changes by Riku Voipio > > License: same as upstream one > > > aarch64_fix_atomic_set.patch: > > - Copyright present. > > - Possibly needs the above patch applied. > > It requires aarch64.patch as it just change two lines. > > > = Some extra remarks > > > > We need at least the proper copyright and license for the patches. In that > > way > > I'm able to apply them in the package and ping upstream wrt them. > > > > Of course, if the original author can push it to upstream's gerrit the > > better, > > because in case some objection arises I don't need to be in the middle as a > > (possibly noisy) proxy. > > Qt4 patches are not accepted upstream. All new code has to go to Qt5 and > since 5.2.0 QAtomics stuff is using std::atomic so compiler takes care > of it and there is no code for separate architectures. Are QT4 patches going to be accepted at some point or will distros have to carry an arm64 patch for QT4 as long as it remains supported? Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140127182021.gr21...@stoneboat.aleph1.co.uk
Bug#735488: Qt4 in arm64: wrap up of the current situation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 W dniu 23.01.2014 18:57, Lisandro Damián Nicanor Pérez Meyer pisze: > I've tried to summarize the current arm64 situation. The following are my > conclusions, feel free to point if something is wrong, give more > info/feedback, etc. As you know from my blog post [0] Qt/AArch64 patch has long history. 0. http://marcin.juszkiewicz.com.pl/2014/01/20/the-story-of-qtaarch64-patching/ > = Stuff under debian/ > > - As explained in a mail before, we don't like the idea of passing > -fpermissive as it can lead to very strange crashes. The code will need > proper > fixing. > > - We are building webkit with a separate source, -no-javascript-jit and the > relevant webkit patches should be applied in src:qtwebkit. The relevant > patches contained in the patch submitted by Wookey come from Riku Voipio and > seems too similar to other patches we already have there, so it should not be > a problem to apply them once we have Qt4 ready form arm64. > - It uses linux-g++ instead of linux-g++-64. While that could be the best > fit, > it would be good to know why. Maybe it is because linux-g++ may use '-m64' argument for GCC which AArch64 does not support so build fails. > = Code patches > > aarch64.patch: > - *No copyright* nor license. We need this at least to be able to apply it > and > ask upstream if they see it fit. There's the chance that some code comes from > Ubuntu people. > - Webkit stuff: as described above. If you need that for something: Author: Marcin Juszkiewicz based on gtkwebkit changes by Riku Voipio License: same as upstream one > aarch64_fix_atomic_set.patch: > - Copyright present. > - Possibly needs the above patch applied. It requires aarch64.patch as it just change two lines. > = Some extra remarks > > We need at least the proper copyright and license for the patches. In that > way > I'm able to apply them in the package and ping upstream wrt them. > > Of course, if the original author can push it to upstream's gerrit the > better, > because in case some objection arises I don't need to be in the middle as a > (possibly noisy) proxy. Qt4 patches are not accepted upstream. All new code has to go to Qt5 and since 5.2.0 QAtomics stuff is using std::atomic so compiler takes care of it and there is no code for separate architectures. And all required patches were submitted - just one change to qtwebkit is stuck in review. https://bugreports.qt-project.org/browse/QTBUG-35442 is upstream bug. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJS5owyAAoJECbKqQEReiUedDgQAIoJP8WhTIA+w08/LfuHsGMa gVI5vEtIsMb+IkMDPqFNmWok1//ocmdXPCJJPFRsHT7Nuy2z8I4pmmZFTzG6llgr zrbKb5mP3MCb6/tzv17YtOi3e8Inrz9+Z6YqdMEmhEtnKEO9llLQ55Af1n9ot7NP xB5OSGgWZSmwVpABEuO6+Ehg4wwyjciclC2JJFHUkTgEYjN4fzBDFGg007qS7fNe Q5jArjHnwXyfNFKsdtKWLbh/52IpwXm9t0Sa5OxqWjdmwmAnLo2YHDLrJWlLI1Of 4M7N36ph57huNuuN8pEuLgwM7BHhicK4EoDhjPD4dKisGUwTOaEGGhZMB+d1EjiQ pOCO8NUehWm96JvMmihv1Zb+j2R3q4q8zwwXK1nUQThTTBEE5Mdg63D5TAcHPV5P sL2GjaaKqHgePnQLrxekmZiSHNmfrjcJw12naTGUPsrf+tK4hZ3qGlHwznAKOKwn ZgJEH8mFiTRBNZ83gHSjP8j9NXiHCaxiRNFUL38e6dnYyNyEdz6zB+U4CyaHuEPR h7GQCyVapvHDe5PrA0aXIjVAAQQTw6TI57Ct4lYBdHqDNvBQZIvLr4lP8EYLWVhA gCdia6C7sbjGb96Gio8W8RtEuxhywh+g0wgndgWkF7RjMTXJxw4CFzOi/5WiTdQf topl5mzNXk+tvnb4jn6R =oz85 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52e68c36.1080...@redhat.com
kde-workspace_4.11.5-1_amd64.changes is NEW
binary:libkwinglesutils1 is NEW. Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1w7osr-0005ga...@franck.debian.org
Processing of kde-workspace_4.11.5-1_amd64.changes
kde-workspace_4.11.5-1_amd64.changes uploaded successfully to localhost along with the files: kde-workspace_4.11.5-1.dsc kde-workspace_4.11.5.orig.tar.xz kde-workspace_4.11.5-1.debian.tar.xz kde-workspace_4.11.5-1_all.deb kdebase-workspace_4.11.5-1_all.deb plasma-desktop_4.11.5-1_amd64.deb plasma-netbook_4.11.5-1_amd64.deb kde-workspace-bin_4.11.5-1_amd64.deb kdebase-workspace-bin_4.11.5-1_all.deb kde-workspace-data_4.11.5-1_all.deb kde-workspace-dev_4.11.5-1_amd64.deb kdebase-workspace-dev_4.11.5-1_all.deb plasma-dataengines-workspace_4.11.5-1_amd64.deb plasma-widgets-workspace_4.11.5-1_amd64.deb plasma-scriptengines_4.11.5-1_all.deb plasma-scriptengine-ruby_4.11.5-1_all.deb plasma-scriptengine-python_4.11.5-1_all.deb plasma-scriptengine-webkit_4.11.5-1_amd64.deb freespacenotifier_4.11.5-1_amd64.deb kdm_4.11.5-1_amd64.deb kinfocenter_4.11.5-1_amd64.deb klipper_4.11.5-1_amd64.deb ksysguardd_4.11.5-1_amd64.deb ksysguard_4.11.5-1_amd64.deb kde-window-manager_4.11.5-1_amd64.deb libkdecorations4abi2_4.11.5-1_amd64.deb libkwineffects1abi5_4.11.5-1_amd64.deb systemsettings_4.11.5-1_amd64.deb kde-workspace-kgreet-plugins_4.11.5-1_amd64.deb kde-style-oxygen_4.11.5-1_amd64.deb kmenuedit_4.11.5-1_amd64.deb libkephal4abi1_4.11.5-1_amd64.deb libkscreensaver5_4.11.5-1_amd64.deb libksgrd4_4.11.5-1_amd64.deb libksignalplotter4_4.11.5-1_amd64.deb libkworkspace4abi2_4.11.5-1_amd64.deb liblsofui4_4.11.5-1_amd64.deb libplasmaclock4abi4_4.11.5-1_amd64.deb libplasma-geolocation-interface4_4.11.5-1_amd64.deb libkwinglutils1abi2_4.11.5-1_amd64.deb libkwinglesutils1_4.11.5-1_amd64.deb libplasmagenericshell4_4.11.5-1_amd64.deb libprocesscore4abi1_4.11.5-1_amd64.deb libprocessui4a_4.11.5-1_amd64.deb libtaskmanager4abi4_4.11.5-1_amd64.deb libweather-ion6_4.11.5-1_amd64.deb kde-workspace-dbg_4.11.5-1_amd64.deb kdebase-workspace-dbg_4.11.5-1_amd64.deb ktouchpadenabler_4.11.5-1_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1w7nyi-00055n...@franck.debian.org
