bug-reports
I succeded in generating a bug report about the akonadi-crashes. But the automatic installation of the missing debuginfos did not work in the report generator. I had to do it manually. Wolfgang -- Wolfgang Romey Anhänge bitte nur in offenen Formaten wie z.B. die OpenDocument-Formate Diese E-mail ist signiert signature.asc Description: This is a digitally signed message part. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
tagging behaves strange with books
I tried to generate channels with books, but the tags I entered were allways removed or altered. So I never succeded in creating the channels i wanted. I wanted to rebuild the books channel in Vivaldi-1, but i did not work. Wth Wallpapers I did succeed. Until now, one has to guess, what tags to use. What happens, if I use the tag dark, are there all assets shown, which have these tag? Wolfgang -- Wolfgang Romey Anhänge bitte nur in offenen Formaten wie z.B. die OpenDocument-Formate Diese E-mail ist signiert signature.asc Description: This is a digitally signed message part. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
INFO: Continuous Integration Status on build.merproject.org
Mon Nov 11 15:30:18 CET 2013 Continuous Integration Status: disabled Build Service Package: kde:devel:ux/bangarang Tarball Prefix: bangarang-2.2+ Repository URL: git://anongit.kde.org/bangarang Branch: master Continuous Integration Status: enabled Build Service Package: kde:devel:ux/blinken Tarball Prefix: blinken-4.10.2+ Repository URL: git://anongit.kde.org/blinken Branch: KDE/4.10 Continuous Integration Status: disabled Build Service Package: kde:devel:ux/calligra Tarball Prefix: calligra-2.6.0+ Repository URL: git://anongit.kde.org/calligra Branch: calligra/2.6 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/declarative-plasmoids Tarball Prefix: declarative-plasmoids-4.10.2+ Repository URL: git://anongit.kde.org/declarative-plasmoids Branch: master Continuous Integration Status: enabled Build Service Package: kde:devel:ux/gwenview Tarball Prefix: gwenview-4.10.2+ Repository URL: git://anongit.kde.org/gwenview Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/kalgebra Tarball Prefix: kalgebra-4.10.2+ Repository URL: git://anongit.kde.org/kalgebra Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/kate Tarball Prefix: kate-4.10.2+ Repository URL: git://anongit.kde.org/kate Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/kde-baseapps Tarball Prefix: kde-baseapps-4.10.2+ Repository URL: git://anongit.kde.org/kde-baseapps Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/kdelibs Tarball Prefix: kdelibs-4.10.2+ Repository URL: git://anongit.kde.org/kdelibs Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/kdepim Tarball Prefix: kdepim-4.10.2+ Repository URL: git://anongit.kde.org/kdepim Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/kdepimlibs Tarball Prefix: kdepimlibs-4.10.2+ Repository URL: git://anongit.kde.org/kdepimlibs Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/kdepim-runtime Tarball Prefix: kdepim-runtime-4.10.2+ Repository URL: git://anongit.kde.org/kdepim-runtime Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/kde-runtime Tarball Prefix: kde-runtime-4.10.2+ Repository URL: git://anongit.kde.org/kde-runtime Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/kde-workspace Tarball Prefix: kde-workspace-4.10.2+ Repository URL: git://anongit.kde.org/kde-workspace Branch: KDE/4.10 Continuous Integration Status: disabled Build Service Package: home:notmart:Mer_Extras:Adaptation:Archos-gen9/kernel-adaptation-archos-gen9 Tarball Prefix: archos-gpl-gen9-kernel-3.0.8+ Repository URL: git://gitorious.org/archos-gen9-mer-adaptation-kernel/archos-gen9-mer-adaptation-kernel-ics.git Branch: master Continuous Integration Status: disabled Build Service Package: home:notmart:Mer_Extras:Adaptation:Archos-gen9:pvr/kernel-adaptation-archos-gen9-pvr Tarball Prefix: archos-gpl-gen9-kernel-3.0.8+ Repository URL: git://gitorious.org/archos-gen9-mer-adaptation-kernel/archos-gen9-mer-adaptation-kernel-ics.git Branch: pvr Continuous Integration Status: enabled Build Service Package: kde:devel:ux/kmix Tarball Prefix: kmix-4.10.2+ Repository URL: git://anongit.kde.org/kmix Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/konsole Tarball Prefix: konsole-4.10.2+ Repository URL: git://anongit.kde.org/konsole Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/ksnapshot Tarball Prefix: ksnapshot-4.10.2+ Repository URL: git://anongit.kde.org/ksnapshot Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/libkactivities Tarball Prefix: libkactivities-6.3+ Repository URL: git://anongit.kde.org/kactivities Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/maliit-active Tarball Prefix: maliit-active-0.1+ Repository URL: git://anongit.kde.org/plasma-active-maliit Branch: master Continuous Integration Status: enabled Build Service Package: kde:devel:ux/marble Tarball Prefix: marble-4.10.2+ Repository URL: git://anongit.kde.org/marble Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/nepomuk-core Tarball Prefix: nepomuk-core-4.10.2+ Repository URL: git://anongit.kde.org/nepomuk-core Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/nepomuk-widgets Tarball Prefix: nepomuk-widgets-4.10.2+ Repository URL: git://anongit.kde.org/nepomuk-widgets Branch: KDE/4.10 Continuous Integration Status: enabled Build Service Package: kde:devel:ux/NetworkManager-kde Tarball Prefix: networkmanagement-0.9.0+ Repository URL: git://anongit.kde.org/networ
Re: random idea about OBS packages
On Monday 11 November 2013, Bogdan Cristea wrote: > On 11/11/2013 11:17 AM, Marco Martin wrote: > > I was thinking about how to make the osc integration a bit better, since > > now is a bit clunky (starting from the fact the input fields in the > > upload form seems to be a bit confusing) > > > > another problem that surfaced is that when there is an update in plasma > > active that touches things like kdelibs, it triggers a rebuild of the > > other packages as well, changing the build number, making the packageid > > invalid (i corrected by hand the two assets interested) > > > > an idea may be: > > * the user only inputs the project (or not even that if we force all to > > be in a single repo) > > * the ackage name (again the obs package name and rpm name are the same > > in 99% of the cases) > > * the architecturei586,armv7hl (if we still want to be two different > > assets for the two architectures) > > > > then the descriptor file on the server is just a template, the actual > > packageid should be generated by a command (possibly when the asset is > > downloaded, to be really really sure is the newest one) > > > > something like > > > > osc list -b kde:stable:apps TabletReader|grep TabletReader > > > > seems a good base for the job > > > > opinions? comments? > > I would go for using the package name and its version number, as defined > by the author, e.g. > name: TabletReader > version: 3.0.2 > then the number generated by the build system is added automatically. > > However, I don't see how you update the package from that single repo > when the author makes available a new version. Should the author upload > all the files needed to build the package on OBS ? I think the final thing will be the author updates in his home repo, which is put in the upload form then the publish phase automatically copies over the package as approval process -- Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: random idea about OBS packages
On 11/11/2013 11:17 AM, Marco Martin wrote: I was thinking about how to make the osc integration a bit better, since now is a bit clunky (starting from the fact the input fields in the upload form seems to be a bit confusing) another problem that surfaced is that when there is an update in plasma active that touches things like kdelibs, it triggers a rebuild of the other packages as well, changing the build number, making the packageid invalid (i corrected by hand the two assets interested) an idea may be: * the user only inputs the project (or not even that if we force all to be in a single repo) * the ackage name (again the obs package name and rpm name are the same in 99% of the cases) * the architecturei586,armv7hl (if we still want to be two different assets for the two architectures) then the descriptor file on the server is just a template, the actual packageid should be generated by a command (possibly when the asset is downloaded, to be really really sure is the newest one) something like osc list -b kde:stable:apps TabletReader|grep TabletReader seems a good base for the job opinions? comments? I would go for using the package name and its version number, as defined by the author, e.g. name: TabletReader version: 3.0.2 then the number generated by the build system is added automatically. However, I don't see how you update the package from that single repo when the author makes available a new version. Should the author upload all the files needed to build the package on OBS ? ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: bug reports
Am Montag, 11. November 2013, 11:25:39 schrieb Marco Martin: > On Monday 11 November 2013, Wolfgang Romey wrote: > > On my weTab with PA4 i have crashes, when I set up the syncing of contacts > > and calendar with owncloud. Obviously akonadi(?) crashes. > > > > I wanted to send a bug report, was offerd to install the debugging > > symbols, > > which was not succesful, because repros are missing. I ask again, what > > repros have to be activated for bug reports. > > hmm, all the packages in the standard repos seems to have an accompaining > debuginfo one So I have to look, if only the error message ist wrong or it is something different. Thanx Wolfgang -- Wolfgang Romey Anhänge bitte nur in offenen Formaten wie z.B. die OpenDocument-Formate Diese E-mail ist signiert signature.asc Description: This is a digitally signed message part. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: bug reports
On Monday 11 November 2013, Wolfgang Romey wrote: > On my weTab with PA4 i have crashes, when I set up the syncing of contacts > and calendar with owncloud. Obviously akonadi(?) crashes. > > I wanted to send a bug report, was offerd to install the debugging symbols, > which was not succesful, because repros are missing. I ask again, what > repros have to be activated for bug reports. hmm, all the packages in the standard repos seems to have an accompaining debuginfo one -- Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
bug reports
On my weTab with PA4 i have crashes, when I set up the syncing of contacts and calendar with owncloud. Obviously akonadi(?) crashes. I wanted to send a bug report, was offerd to install the debugging symbols, which was not succesful, because repros are missing. I ask again, what repros have to be activated for bug reports. Wolfgang -- Wolfgang Romey Anhänge bitte nur in offenen Formaten wie z.B. die OpenDocument-Formate Diese E-mail ist signiert signature.asc Description: This is a digitally signed message part. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
random idea about OBS packages
Hi all, I was thinking about how to make the osc integration a bit better, since now is a bit clunky (starting from the fact the input fields in the upload form seems to be a bit confusing) another problem that surfaced is that when there is an update in plasma active that touches things like kdelibs, it triggers a rebuild of the other packages as well, changing the build number, making the packageid invalid (i corrected by hand the two assets interested) an idea may be: * the user only inputs the project (or not even that if we force all to be in a single repo) * the ackage name (again the obs package name and rpm name are the same in 99% of the cases) * the architecturei586,armv7hl (if we still want to be two different assets for the two architectures) then the descriptor file on the server is just a template, the actual packageid should be generated by a command (possibly when the asset is downloaded, to be really really sure is the newest one) something like osc list -b kde:stable:apps TabletReader|grep TabletReader seems a good base for the job opinions? comments? Cheers, Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Errors when editing an already published asset
On 11/11/2013 10:44 AM, Marco Martin wrote: what do you mean as in platform tag? you can assign any of the two in the tag drag and drop thinghie (second action icon in the assets view) I don't understand your question "what do you mean as in platform tag?". The platform tag I see when editing contains Vivaldi string and if I publish my assert exactly like this it gets rejected. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Errors when editing an already published asset
On Sunday 10 November 2013, Bogdan Cristea wrote: > Hi > > When I try to edit an already published asset (created from OBS) I have > noticed that the selected platform is Vivaldi, even if previously I have > published the asset for PA. This is an issue as assets for Vivaldi > platform are rejected. Also, the fields for screenshots and application > icons are empty even if previously I have filled this fields. what do you mean as in platform tag? you can assign any of the two in the tag drag and drop thinghie (second action icon in the assets view) -- Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
