Custom Query (159 matches)
Results (49 - 51 of 159)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #65 | fixed | Make Enduser usage of created packages more easy | ||
| Description |
To make the usage of the created packages more easy to the end user, some more actions should be done. This should be related to all Distribution, even if I only add OpenSuSe right now, because they have a solution. It would be nice to create a ymp-file on OpenSuSe too, which can be used to enable one-click-installation. I've translated the example from http://de.opensuse.org/1-Klick-Installation/ISV (only available in german) into english, to make it more useable. This file can be linked from a website and if the user activates the link, the defined repository are added and the software is installed. Ubuntu has a quite similar feature too (called apt-protocol). To use this nothing must be done, because a link like apt://urltorepo?package=PKGNAME?dist=VERSION?section=contrib should allow a user to install the package. But actually this kind of links are disabled, because of security concerns at ubuntu. |
|||
| #67 | fixed | Incorrectly commented define in the template rpm spec | ||
| Description |
I use pb version 0.9.10-1042. It generates incorrect template for rpm spec located at pbconf/PROJECT/rpm/PROJECT.spec. This template contains the following line: #%define srcname PBPKG That causes following error during build2pkg: #%define is forbidden, use #define to comment a %define So, that line should look like this #define srcname PBPKG |
|||
| #68 | fixed | Process without interaction (handy: cron mode) | ||
| Description |
pb should be able to run the whole process cms2vm and test2vm without any gui and user interaction (if ssh is configured correctly by the user). For example: We use Project-Builder to run tests during the night on different distributions (results: softqa.engsas.de/meganizer). This test are run by cron without gui and any interaction.
We discussed some points concerning making pb guiless on the mailing list, if there are no changes right now, i've appended the patch, which I suggested there. The patch assumes, that the user wants to access the VM only if he launches launchvm. All other launches are done by pb and therefore I assume, that the user does not interact with VM manually. We started to discuss some other possible solutions, which may be better. This ticket should be ment as a remind, to go on with that discussion.
Sometimes, the VM hangs (randomly, don't know why), but pb does not detect it, so I suggest to let the user define a default max time per vm, after that time, the vm is halted or killed if halt is not working. This does not solve the problem with the vm, but the process isn't stopped completly and the following vm's are at least processed. |
|||
