Tag Info

Hot answers tagged

67

This list contains the reasons why it did not use back then and why it should not move now Lauchpad used bazaar which was developed long back. Github did not exist that time (as Robin said) Launchpad was launched in 2004 and Github in 2008 Github is not open source. Gitorious would be a better choice in this case. I know Launchpad was not FOSS initially, ...


26

I guess the simple answer is that Launchpad does a lot of stuff that other systems don't (and this was even more true back when Ubuntu started using Launchpad). Some examples: A bug tracker that lets you track bugs in multiple contexts (e.g. a bug that affects multiple packages, or affects both a package and its upstream, or the same package in multiple ...


25

Use Launchpad's +junk branch feature to publish your code to a temporary location. In fact, it is not temporary, as it will remain there until you explicitly delete it, but it is a nice place to put unfinished code you're experimenting with on a public location. This way it will stay out of the way from your regular branches, but you'll still be able to ...


22

This is not about the particular bugs you've filed, but general good practice for getting bugs dealt with in a timely manner: Make sure you've filed the bug report in the correct source package. Bug triagers and developers tend to be subscribed to the bug mail of packages they're interested in or responsible from, so for the relevant people to look into ...


21

Gradle requires a Java JDK to be installed. Gradle requires a JDK 1.5 or higher. Gradle ships with its own Groovy library, therefore no Groovy needs to be installed. Any existing Groovy installation is ignored by Gradle. Gradle uses whichever JDK it finds in your path (to check, use java -version). Alternatively, you can set the JAVA_HOME ...


20

That's a very wide question. I'll try to answer as much as I can, but it definitely WON'T be a step-by-step instruction. This is because there is no step-by-step algorithm for creating a package. The way you'll do it depends on many factors, mostly on the type of package (application, library), the structure of source, and many details. Luckily, there is a ...


19

From the papercut website: The One Hundred Paper Cuts project exists to work on the little annoyances in Ubuntu. These bugs are normally considered too low priority for the developers of the apps in question, who already have more than enough to work on, and so the One Hundred Paper Cuts project comes along and picks them up. In each release ...


19

Launchpad uses notification emails and Atom feeds to help you stay on top of the bugs that interest you. There are three ways to get bug notifications by email: subscribe to a bug subscribe to a milestone, project, package or distribution take a role that results in bug mail: bug reporter assignee commenter project or package ...


17

The definition of a paper cut Put briefly, a paper cut is a trivially fixable usability bug that the average user would encounter in a default application included on the Ubuntu desktop. If you prefer a more detailed, itemized definition, a paper cut is: A bug, or an unintended problem occurring within an existing piece of software, the presence of which ...


16

The repository is stored as a bazaar repository on Launchpad. Multiple git branches are not currently imported - this is being looked at & can be followed at https://bugs.launchpad.net/launchpad-code/+bug/380871 Writing to the branches on launchpad is not supported, according to http://blog.launchpad.net/code/git-branch-imports-now-in-public-beta From ...


16

No, Launchpad karma has no bearing on what you can access. The "Triaged" and "Won't Fix" bug statuses are reserved to the role called the "bug supervisor" for each project or distribution. For Ubuntu, this is the Ubuntu Bugs team (actually, effectively, the Ubuntu Bug Control team), which you have to be part of in order to set the statuses in question. ...


16

This can easily be done on Launchpad. What you are looking for is called a source package recipe. The way to set this up and get it building the source every day is to first register the project on Launchpad if it isn't already. Once that is complete, go to the project page and click "configure project branch": Now you need to tell Launchpad where the ...


14

The process for getting a package into Debian is outlined in this FAQ. Once your package is in Debian, it will be automatically imported into Ubuntu. Debian and Ubuntu use the same packaging system. Binary packages (.deb files) for Debian and Ubuntu are not necessarily compatible but when you package for Ubuntu and Debian you upload source code so that it ...


14

You're pretty close with your example steps, but here's what I'd suggest: Grab the sources with apt-get source wine and cd into the new directory Find what sort of patch system the wine package is based on: what-patch; in this case, it tells us we that the wine package uses quilt for patch management Since we're using quilt, add your custom patch(es) to ...


14

Register on Launchpad like txwikinger said, then you need to generate a GPG key gpg --gen-key and upload it to Ubuntu's keyserver gpg --keyserver keyserver.ubuntu.com --publish-keys $KEYID Replacing $KEYID with the number after the slash on the "sec" line of: gpg -K --fingerprint Click the green + next to the GPG key part of your profile, and give ...


14

You can add a PPA location with the command sudo add-apt-repository ppa:<ppa_name> For example sudo add-apt-repository ppa:gnome-desktop You can find some help on Ubuntu Documentation


13

Murat's answer is correct for good processes. For your specific bug it seems to be assigned to the wrong component. gnome-vfs is the old unmaintained thing, the current GNOME piece that handles this sort of thing is actually called gvfs. Your problem is likely that no one is looking at bugs for something we haven't shipped in a while. Fixing the component ...


13

As Marco Ceppi has pointed me towards launchpadlib, I wrote a little script that will do this for you.  download it here Run the script by calling python name_of_the_script.py in a Terminal after you've downloaded and saved it. It will ask you for a programming language, case insensitive, and a search query (where wildcards, *, are allowed). If you ...


12

For testing Maverick, testdrive is easiest. It'll automatically download the latest Maverick daily and run it in a Virtual Machine. sudo apt-get install testdrive virtualbox-ose testdrive


12

Check out this script: #!/usr/bin/python # Usage python ppastats.py PPATEAM (ex: webupd8team) PPA (ex: gthumb) DIST (Ubuntu version eg maverick) ARCH (ubuntu arch eg i386 or amd64) # Example - highest downloaded file: python ppastats.py webupd8team y-ppa-manager maverick amd64 | tr '\t' ',' | cut -d ',' -f3 | sort -gr import sys from ...


12

On your old machine, you generated a SSH key and then added that to your Launchpad account. Bzr uses that key to acces launchpad. So if the key on your new machine doesn't match the one you uploaded to Launchpad, you will be unable to branch code from certain repositories on Launchpad. Two solutions are possible. The first is of course to transfer your SSH ...


11

The name of the installation wizard is ubiquity. Linked Question: What is ubiquity?


11

Use a GitHub gist - You don't even need to register.


11

sudo add-apt-repository ppa:cwchien/gradle sudo apt-get update This is correct answer, but before make sudo apt-get install gradle, do: sudo apt-cache search gradle and next install latest version from new repo. In my case it: sudo apt-get install gradle-1.9 it work's! (if you don't tell, what version you need, it install gradle(1.4) from main repo, ...


11

To expand on fluteflute's answer, which is mostly right, the automated retracer does not set the bug public. It merely adds a stack trace to the bug so that it is more clear where the problem lies. The sensitive information is kept in the bug report, as it can be invaluable to a developer working on a fix. The bug is reviwed by members of the ...


11

Go to the project page that you want to create a branch for and click 'Submit Code'. Then set up the branch. Make sure it is hosted in Launchpad. You can then push to the branch: bzr push lp:branch The first time you push, you will need to use: bzr push lp:branch --use-existing-dir Once you are ready to merge, click 'Propose for merging' on the ...


11

To assign a bug to yourself in Launchpad, first navigate to the bug page (e.g. https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/397393 ) This shows that the bug is not assigned to anyone at the moment. Click on the Unassigned link Finally, click on the Assign Me link (the little yellow exclamation point) The bug is now assigned for you to work ...


11

I actually think it's more like "why do they use bzr, and hence launchpad"? Canonical invested money and people into developing bzr and its precursor baz, long before GitHub existed, and they probably don't want to throw away all of that accumulated expertise and investment now. Indeed, baz was started before git existed. Also, with Launchpad being ...


10

Answered on Launchpad: Launchpad does not support markup in user entered content at this time. URL and bug numbers are linked by the formatter that preserves blank lines. Please support this bug for a Launchpad wiki.


10

Packages take a while to process. You just need to wait. You will receive an email soon saying that your package was accepted (or rejected) then the packages will build, which will take some time. You should see the build progress on the right of your PPA page. Once the packages have built (or failed to build), you will be emailed again.



Only top voted, non community-wiki answers of a minimum length are eligible