Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lxqt 0.10 version bump #393

Closed
wants to merge 26 commits into from
Closed

lxqt 0.10 version bump #393

wants to merge 26 commits into from

Conversation

PPed72
Copy link
Contributor

@PPed72 PPed72 commented Nov 24, 2015

Just pushing Alpha Bravo's changes in https://bugs.gentoo.org/show_bug.cgi?id=564718 and https://bugs.gentoo.org/show_bug.cgi?id=565952 since they've been there for a week and nothing happened yet.

@gentoo-repo-qa-bot
Copy link
Collaborator

😞 The QA check for this pull request has found the following issues:

https://qa-reports.gentoo.org/output/gentoo-ci/7754095/9.html#l1631
https://qa-reports.gentoo.org/output/gentoo-ci/7754095/10.html#l1826
https://qa-reports.gentoo.org/output/gentoo-ci/7754095/10.html#l1856

Please note that the issues may come from the underlying Gentoo repository state rather than the pull request itself.

@monsieurp
Copy link
Member

Hi and thank you for you PR. LGTM except the messages format. Could you reformat your commit messages and instead write "package/category: message" ? That'd helpful. Thanks!

@monsieurp
Copy link
Member

@jauhien

@PPed72
Copy link
Contributor Author

PPed72 commented Nov 25, 2015

In data Wednesday 25 November 2015 00:45:28, monsieurp ha scritto:

Hi and thank you for you PR. LGTM except the messages format. Could you
reformat your commit messages and instead write "package/category: message"

Shouldn't it be "category/package", like "lxqt-base/lxqt-meta"?

? That'd helpful. Thanks!

I'll do that, probably tomorrow.

Thanks.

Paolo Pedroni
paolo.pedroniiol.it

PPed72 and others added 20 commits November 26, 2015 09:18
Also fixes https://bugs.gentoo.org/show_bug.cgi?id=561420
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> and Denis I. Polukarov
<dipolukarov@gmail.com> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
Thanks to Alpha Bravo <aos@ungwana.de> in bug #565952
Fixes bug #565952
Thanks to Alpha Bravo <aos@ungwana.de> in bug #564718
@PPed72
Copy link
Contributor Author

PPed72 commented Nov 26, 2015

Changed all the commit messages. Are they OK, now? Thanks for the attention

@gentoo-repo-qa-bot
Copy link
Collaborator

😞 The QA check for this pull request has found the following issues:

https://qa-reports.gentoo.org/output/gentoo-ci/2c1b8e5/9.html#l1631
https://qa-reports.gentoo.org/output/gentoo-ci/2c1b8e5/10.html#l1826
https://qa-reports.gentoo.org/output/gentoo-ci/2c1b8e5/10.html#l1856

Please note that the issues may come from the underlying Gentoo repository state rather than the pull request itself.

@gentoo-repo-qa-bot
Copy link
Collaborator

😞 The QA check for this pull request has found the following issues:

https://qa-reports.gentoo.org/output/gentoo-ci/7c7f0d1/9.html#l1631
https://qa-reports.gentoo.org/output/gentoo-ci/7c7f0d1/10.html#l1826
https://qa-reports.gentoo.org/output/gentoo-ci/7c7f0d1/10.html#l1855

Please note that the issues may come from the underlying Gentoo repository state rather than the pull request itself.

@jauhien
Copy link
Contributor

jauhien commented Nov 26, 2015

Hi,

I'm busy at the moment and also have problems with my computer. Could you, please, ping somebody else from the lxqt herd?

@monsieurp
Copy link
Member

Thank for the PR @PPed72. Unfortunately, there are still errors that are to be looked after.

https://qa-reports.gentoo.org/output/gentoo-ci/7c7f0d1/10.html#l1826

Something's up with the ~arm keyword, lxqt-base/lxqt-config and lxqt-base/lxqt-panel. Could you please make sure all ebuilds are keyworded correctly and your PR is not generating errors? Thanks!

@PPed72
Copy link
Contributor Author

PPed72 commented Nov 27, 2015

kde-frameworks/solid and kde-plasma/libkscreen have no keywords for arm. I'm going to drop arm and arm64 for the moment

lxqt-base/liblxqt-0.10.0: drop ~arm and ~arm64
x11-misc/pcmanfm-qt-0.10.0: drop ~arm and ~arm64

kde-frameworks/solid and kde-plasma/libkscreen are not keyworded for arm
and arm64
@gentoo-repo-qa-bot
Copy link
Collaborator

😞 The QA check for this pull request has found the following issues:

https://qa-reports.gentoo.org/output/gentoo-ci/886233f/9.html#l1631

Please note that the issues may come from the underlying Gentoo repository state rather than the pull request itself.

@monsieurp
Copy link
Member

Thanks a lot. PR merged. 👍

@monsieurp monsieurp closed this Nov 28, 2015
@PPed72 PPed72 deleted the PPed72-lxqt-0.10-version-bump branch November 30, 2015 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants