Re: kdelibs4 docs move
+1. Doing a bulk rebuild this close to release seems like a bad idea. Scott K On Wednesday, April 01, 2015 09:40:06 PM Rohan Garg wrote: > Wouldn't installing a symlink to the older docs be a simpler / faster > / easier solution? > > Regards > Rohan Garg > > On Wed, Apr 1, 2015 at 9:02 PM, Jonathan Riddell wrote: > > On Wed, Apr 01, 2015 at 03:00:31PM -0400, Scott Kitterman wrote: > >> On Wednesday, April 01, 2015 08:40:23 PM Jonathan Riddell wrote: > >> > kdelibs4 docs were in /usr/share/doc/kde/HTML/ > >> > > >> > but frameworks uses /usr/share/doc/HTML/ > >> > > >> > so we need to change kde4libs to set the docs path to > >> > /usr/share/doc/HTML/ > >> > > >> > I've uploaded kde4libs with this change. Where is kde4libs kept in > >> > revision control these days? I can't find an up to date repository > >> > and debian/control doesn't tell me > >> > > >> > This then needs a bulk upload of all 372 source packages that have > >> > kdelibs4 docs along with changes to the .install files to them, fairly > >> > easy to script but making sure all the VCS repos are updated may be > >> > hassle > >> > > >> > This makes us incompatible with Debian syncs too which I guess will be > >> > a hassle on occasion in the next cycle. > >> > > >> > Jonathan > >> > >> Why does kde4libs need to change because Kf5 uses a different location? > > > > because khelpcenter follows the kf5 path and can't be asked to look in two > > paths. > > > > Jonathan > > > > -- > > kubuntu-devel mailing list > > kubuntu-devel@lists.ubuntu.com > > Modify settings or unsubscribe at: > > https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: kdelibs4 docs move
Wouldn't installing a symlink to the older docs be a simpler / faster / easier solution? Regards Rohan Garg On Wed, Apr 1, 2015 at 9:02 PM, Jonathan Riddell wrote: > On Wed, Apr 01, 2015 at 03:00:31PM -0400, Scott Kitterman wrote: >> On Wednesday, April 01, 2015 08:40:23 PM Jonathan Riddell wrote: >> > kdelibs4 docs were in /usr/share/doc/kde/HTML/ >> > >> > but frameworks uses /usr/share/doc/HTML/ >> > >> > so we need to change kde4libs to set the docs path to /usr/share/doc/HTML/ >> > >> > I've uploaded kde4libs with this change. Where is kde4libs kept in >> > revision control these days? I can't find an up to date repository >> > and debian/control doesn't tell me >> > >> > This then needs a bulk upload of all 372 source packages that have >> > kdelibs4 docs along with changes to the .install files to them, fairly >> > easy to script but making sure all the VCS repos are updated may be >> > hassle >> > >> > This makes us incompatible with Debian syncs too which I guess will be >> > a hassle on occasion in the next cycle. >> > >> > Jonathan >> >> Why does kde4libs need to change because Kf5 uses a different location? > > because khelpcenter follows the kf5 path and can't be asked to look in two > paths. > > Jonathan > > -- > kubuntu-devel mailing list > kubuntu-devel@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: kdelibs4 docs move
On Wed, Apr 01, 2015 at 03:00:31PM -0400, Scott Kitterman wrote: > On Wednesday, April 01, 2015 08:40:23 PM Jonathan Riddell wrote: > > kdelibs4 docs were in /usr/share/doc/kde/HTML/ > > > > but frameworks uses /usr/share/doc/HTML/ > > > > so we need to change kde4libs to set the docs path to /usr/share/doc/HTML/ > > > > I've uploaded kde4libs with this change. Where is kde4libs kept in > > revision control these days? I can't find an up to date repository > > and debian/control doesn't tell me > > > > This then needs a bulk upload of all 372 source packages that have > > kdelibs4 docs along with changes to the .install files to them, fairly > > easy to script but making sure all the VCS repos are updated may be > > hassle > > > > This makes us incompatible with Debian syncs too which I guess will be > > a hassle on occasion in the next cycle. > > > > Jonathan > > Why does kde4libs need to change because Kf5 uses a different location? because khelpcenter follows the kf5 path and can't be asked to look in two paths. Jonathan -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: kdelibs4 docs move
On Wednesday, April 01, 2015 08:40:23 PM Jonathan Riddell wrote: > kdelibs4 docs were in /usr/share/doc/kde/HTML/ > > but frameworks uses /usr/share/doc/HTML/ > > so we need to change kde4libs to set the docs path to /usr/share/doc/HTML/ > > I've uploaded kde4libs with this change. Where is kde4libs kept in > revision control these days? I can't find an up to date repository > and debian/control doesn't tell me > > This then needs a bulk upload of all 372 source packages that have > kdelibs4 docs along with changes to the .install files to them, fairly > easy to script but making sure all the VCS repos are updated may be > hassle > > This makes us incompatible with Debian syncs too which I guess will be > a hassle on occasion in the next cycle. > > Jonathan Why does kde4libs need to change because Kf5 uses a different location? Scott K -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
kdelibs4 docs move
kdelibs4 docs were in /usr/share/doc/kde/HTML/ but frameworks uses /usr/share/doc/HTML/ so we need to change kde4libs to set the docs path to /usr/share/doc/HTML/ I've uploaded kde4libs with this change. Where is kde4libs kept in revision control these days? I can't find an up to date repository and debian/control doesn't tell me This then needs a bulk upload of all 372 source packages that have kdelibs4 docs along with changes to the .install files to them, fairly easy to script but making sure all the VCS repos are updated may be hassle This makes us incompatible with Debian syncs too which I guess will be a hassle on occasion in the next cycle. Jonathan -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Kubuntu docs
Hello you're on ubuntu-core-docs which is the maintainer and driver of kubuntu-docs project on launchpad. We're updating the docs now and want to commit to the branches but none of us have access. Could you change the maintainer and driver of kubuntu-docs to kubuntu-council ? Jonathan -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
CI + QML deps
quick heads up. I plan to roll out QML dependency verification later this week across all builds. Missing qml deps will cause the builds to get marked unstable (possibly going to be failing at a later point). Output will look something like this: http://kci.pangea.pub/job/vivid_unstable_kdeplasma-addons/107/parsed_console/job/vivid_unstable_kdeplasma-addons/107/parsed_console/log_content.html#WARNING1 In the next build cycle the verifier will be run on kwin, plasma-framework, plasma-desktop and kdeplasma-addons, once those look good it will get used for all builds. Before this gets rolled out across all builds I probably still have to wire up some override tech, which is written but not used at this time. I am not sure where one would place the override, possibly debian/$package.qml-override. The format is final though [1], straight forward one-import-per-line-ignore with an optional version attribute to only ignore a specific version. It also supports posix patterns. Sine JR asked how this works: [11:13] anyway, what happens is: it installs each of the debs generated by the source, lists their content, parses all *.qml files to extract their imports, then tries to lookup the actual module according to the lookup rules, it purges the package and autoremoves the deps again and moves on to the next package [11:14] i.e. basic principle: if installing the package does not also install the module, the module must be missing [1] http://anonscm.debian.org/cgit/pkg-kde/ci-tooling.git/diff/test/data/test_qml_ignore_rule/test_read?id=569b3ca0d1ab57271dae2d0f08fabbc2e43b700a -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: nvidia-prime and sddm
On 31-03-15 19:29:54, Jonathan Riddell wrote: > We've switched to SDDM in Kubuntu but alas I know nothing about > nvidia. Alberto I think you're the dude who does know? > > nvidia-prime is the proprietary driver we need to care about for NVidia users? > > Last cycle I put in an alternate so it depended on lightdm | sddm but > that seems to have been removed. Is there more sddm integration > needed? > > Jonathan Hi Jonathan, I maintain both the nvidia packages and nvidia-prime. What nvidia-prime does is provide a way to use hybrid graphics (Intel+NVIDIA) in Ubuntu. While I don't recall dropping he alternate dependency on sddm (which is entirely possible that I did), maybe sddm doesn't really work with nvidia-prime. If you want hybrid graphics to work (as it does in Ubuntu), you'll need support for something like the following stanzas from lightdm: display-setup-script=/sbin/prime-offload display-stopped-script=/sbin/prime-switch The first line is executed after X starts, whereas the second line is executed after stopping X (and before starting a new one). Does sddm support that? I should also modify the relevant upstart job in ubuntu-drivers-common (the systemd unit already works). Regards, -- Alberto Milone Software Engineer Hardware Enablement Team Professional and Engineering Services -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: CI LXC -> Docker
On Tue, Mar 31, 2015 at 4:21 PM, Harald Sitter wrote: > ...or at least I am deploying that right now under the assumption that > it will actually work. Also for the next day or two integration will > be disabled while I make sure that jobs turn red over night. It seems to work better than expected, so I am switching integration back to normal later today. > Ideally this change doesn't affect anyone but me, I do however expect > odd build failures as the docker roll out was not very well tested and > is hard to test cover in general. ^ I have since noticed that a fancy tool we use for mocking http traffic in tests also supports the lib we use to interact with the docker socket. That means that eventually we can do mocked tests to verify code consistency WRT docker API usage \o/ HS -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
