From noreply at ubuntu.com Tue Jul 9 03:29:41 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 09 Jul 2013 03:29:41 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_fitoschido?= Message-ID: <20130709032941.3106.97184@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Tags" page has been changed by fitoschido: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=191&rev2=192 Comment: these are obsolete || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-error|`gstreamer-error`]] || Bug is related to bad drivers and not Cheese; ''Switch bug to related package(`linux` for missing/bad drivers)''|| || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-ok|`gstreamer-ok`]] || Video gstreamer input works fine (drivers seem fine), most likely a Cheese bug || - === Firefox/Xulrunner Stable Upgrade Regressions === - || '''Tag''' || '''Use case''' || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-hardy|`ffox36-hardy`]] || Regressions on Hardy due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-jaunty|`ffox36-jaunty`]] || Regressions on Jaunty due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-karmic|`ffox36-karmic`]] || Regressions on Karmic due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 || - === Network Manager === <> From webmaster at ubuntu.com Sun Jul 14 15:29:56 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sun, 14 Jul 2013 15:29:56 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_uusijani?= Message-ID: <20130714152956.21636.65065@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by uusijani: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=235&rev2=236 Comment: s/997283/994921, off-line (slight tweaks) enabled=1 }}} - /!\ Even when enabled, apport will not upload crash reports to Launchpad for a stable release. For more on this please see [[https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921|bug #994921]]. Instead, crash reports are uploaded to [[http://errors.ubuntu.com]]. To have a bug report filed on Launchpad anyways, one may open the following file via a command line: {{{ + /!\ Even when enabled, apport will not upload crash reports to Launchpad for a stable release (see [[https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921|bug #994921]]). Instead, crash reports are uploaded to [[http://errors.ubuntu.com]]. To file a report on Launchpad anyway, one may open the following file via a command line: {{{ gksudo gedit /etc/apport/crashdb.conf }}} and change: {{{ 'problem_types': ['Bug', 'Package'], @@ -236, +236 @@ In the event that you have an issue with your Internet connection or want to file a bug for another system you can still do this using apport. - First, gather the information about the target system in a file: + First, on the target system, gather the information in a file: * For a bug report about a system crash:<
>`apport-cli -p` ''``'' `--save bug.crash` * For a bug report about any other issue:<
>`apport-cli -f -p` ''``'' `--save bug.apport` You will need to answer a few questions, which will vary depending on which package the bug report is about. Relevant system information, including the package name, is then saved on the target system, in the current directory. The extension indicates if it is a crash report or another kind of report. If you decide to rename the report file, please keep the `.apport` or `.crash` extension. - After copying it to a different system you can file that report using the following command:<
>`ubuntu-bug -c` ''``'' + When the file is ready, copy it to the system you intend to use for filing the report. There you can then file the report:<
> + `ubuntu-bug -c` ''``'' - /!\ 'ubuntu-bug -c x.crash' does not work for crash reports from stable Ubuntu releases, see [[https://bugs.launchpad.net/apport/+bug/997283|bug #997283]] crash reports "do not get filed to Launchpad any more... we don't want crash reports for the non-development version on Launchpad." A possible workaround is detailed above in the section "Reporting an application crash > Stable release": UPDATE: 'apport-cli -c x.crash' seems to work + /!\ 'ubuntu-bug -c x.crash' does not work for crash reports from stable Ubuntu releases (see [[#Stable_release|note about stable releases above]]). If this is to be added to an existing bug report, also use the -u option:<
>`ubuntu-bug -c` ''``'' `-u` ''``'' From webmaster at ubuntu.com Sun Jul 14 15:32:19 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sun, 14 Jul 2013 15:32:19 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_uusijani?= Message-ID: <20130714153219.27252.8174@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by uusijani: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=236&rev2=237 Comment: indent, backticks /!\ 'ubuntu-bug -c x.crash' does not work for crash reports from stable Ubuntu releases (see [[#Stable_release|note about stable releases above]]). - If this is to be added to an existing bug report, also use the -u option:<
>`ubuntu-bug -c` ''``'' `-u` ''``'' + If this is to be added to an existing bug report, also use the -u option:<
> + `ubuntu-bug -c` ''``'' `-u` ''``'' - You will need to answer a few questions, and a web browser will be launched to complete the bug report. Please do not attach the .apport or .crash file to the report, as this is not the same as performing the above mentioned steps. + You will need to answer a few questions, and a web browser will be launched to complete the bug report. Please do not attach the `.apport` or `.crash` file to the report, as this is not the same as performing the above mentioned steps. == Filing bugs at Launchpad.net == From noreply at ubuntu.com Tue Jul 16 06:01:12 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 16 Jul 2013 06:01:12 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_alan-pater?= Message-ID: <20130716060112.27119.97808@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Status" page has been changed by alan-pater: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=60&rev2=61 Comment: faulty hw? * Make a judgment call: as long as ''more than one person'' experiences the bug, the proper status is "Confirmed". * What should a triager do if a bug needs more information, including steps to reproduce, but the original reporter is not available to provide it? * Mark the bug as Invalid with a comment that the reporter should provide the information and reopen the bug by resetting its status to 'New'. + * What is the appropiate bug status for issues caused by faulty hardware? ||{{attachment:IconHelp2.png}}Not yet an [[https://wiki.ubuntu.com/UbuntuBugControl|Ubuntu Bug Control]] member? If you notice a bug having sufficient information and has not yet been set to Triaged, you'll have to ask someone who is to set the bug to ''Triaged'' for you. Paste the bug number in {{{#ubuntu-bugs}}} channel at [[https://wiki.ubuntu.com/FreeNode|FreeNode]] and say you think the bug should be set to 'Triaged' with importance 'Wishlist / Low / Medium / High / Critical' according to [[Bugs/Importance]]. Someone will notice your comment and set it for you, although not necessarily immediately.|| From brian at ubuntu.com Tue Jul 16 15:54:34 2013 From: brian at ubuntu.com (Brian Murray) Date: Tue, 16 Jul 2013 08:54:34 -0700 Subject: [Ubuntu Wiki] Update of "Bugs/Status" by alan-pater In-Reply-To: <20130716060112.27119.97808@mangaba.canonical.com> References: <20130716060112.27119.97808@mangaba.canonical.com> Message-ID: <20130716155434.GY2977@murraytwins.com> On Tue, Jul 16, 2013 at 06:01:12AM -0000, Ubuntu Wiki wrote: > Dear Wiki user, > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. > > The "Bugs/Status" page has been changed by alan-pater: > http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=60&rev2=61 > > Comment: > faulty hw? > > * Make a judgment call: as long as ''more than one person'' experiences the bug, the proper status is "Confirmed". > * What should a triager do if a bug needs more information, including steps to reproduce, but the original reporter is not available to provide it? > * Mark the bug as Invalid with a comment that the reporter should provide the information and reopen the bug by resetting its status to 'New'. > + * What is the appropiate bug status for issues caused by faulty hardware? The answer here is Invalid. I'd be great if someone could remove the information indicating that this wiki page is a good place to ask questions, I'd rather discussions happened on the mailing list. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From teward at ubuntu.com Tue Jul 16 16:16:05 2013 From: teward at ubuntu.com (Thomas Ward) Date: Tue, 16 Jul 2013 12:16:05 -0400 Subject: [Ubuntu Wiki] Update of "Bugs/Status" by alan-pater In-Reply-To: <20130716155434.GY2977@murraytwins.com> References: <20130716060112.27119.97808@mangaba.canonical.com> <20130716155434.GY2977@murraytwins.com> Message-ID: Everyone: On Tue, Jul 16, 2013 at 11:54 AM, Brian Murray wrote: > On Tue, Jul 16, 2013 at 06:01:12AM -0000, Ubuntu Wiki wrote: > > Dear Wiki user, > > > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for > change notification. > > > > The "Bugs/Status" page has been changed by alan-pater: > > http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=60&rev2=61 > > > > Comment: > > faulty hw? > > > > * Make a judgment call: as long as ''more than one person'' > experiences the bug, the proper status is "Confirmed". > > * What should a triager do if a bug needs more information, > including steps to reproduce, but the original reporter is not available to > provide it? > > * Mark the bug as Invalid with a comment that the reporter should > provide the information and reopen the bug by resetting its status to 'New'. > > + * What is the appropiate bug status for issues caused by faulty > hardware? > > The answer here is Invalid. I'd be great if someone could remove the > information indicating that this wiki page is a good place to ask > questions, I'd rather discussions happened on the mailing list. > > -- > Brian Murray > Ubuntu Bug Master > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > I wholeheartedly agree with Brian on removing the segment on where people can ask questions via that page. I forgot to add that they should email the mailing list, though, and I will add that in shortly. I also added the answer to the question that was asked. ------ Thomas Ward -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Tue Jul 16 16:14:25 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 16 Jul 2013 16:14:25 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_teward?= Message-ID: <20130716161425.19471.73658@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Status" page has been changed by teward: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=61&rev2=62 Comment: Removed segment about "Feel free to add your question here" per request and statements of Brian Murray on the mailing list. Answered the latest question. === Frequently Asked Questions === - ''If you have a question, please feel free to add it here without an answer. A [[BugSquad]] member will add the answer later.'' - * What is the appropriate status if the bug's reporter later says the bug no longer exists but the related changelog does not note a fix? * See the first point under "Invalid", the bug does not have sufficient information. * What should a triager do if there is consensus ''among users and developers'' that an issue is valid but there is no good solution? @@ -81, +79 @@ * What should a triager do if a bug needs more information, including steps to reproduce, but the original reporter is not available to provide it? * Mark the bug as Invalid with a comment that the reporter should provide the information and reopen the bug by resetting its status to 'New'. * What is the appropiate bug status for issues caused by faulty hardware? + * The appropriate bug status for such issues is "Invalid". ||{{attachment:IconHelp2.png}}Not yet an [[https://wiki.ubuntu.com/UbuntuBugControl|Ubuntu Bug Control]] member? If you notice a bug having sufficient information and has not yet been set to Triaged, you'll have to ask someone who is to set the bug to ''Triaged'' for you. Paste the bug number in {{{#ubuntu-bugs}}} channel at [[https://wiki.ubuntu.com/FreeNode|FreeNode]] and say you think the bug should be set to 'Triaged' with importance 'Wishlist / Low / Medium / High / Critical' according to [[Bugs/Importance]]. Someone will notice your comment and set it for you, although not necessarily immediately.|| From noreply at ubuntu.com Tue Jul 16 16:26:24 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 16 Jul 2013 16:26:24 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_teward?= Message-ID: <20130716162624.19597.45005@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Status" page has been changed by teward: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=62&rev2=63 Comment: Modified FAQ section to include a statement saying that if you have a question you should email the Bug Squad mailing list, and provided the email address for the mailing list. === Frequently Asked Questions === + ''If you have a question, please feel free to ask it by emailing the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad|BugSquad mailing list]] with your question.'' + * What is the appropriate status if the bug's reporter later says the bug no longer exists but the related changelog does not note a fix? * See the first point under "Invalid", the bug does not have sufficient information. * What should a triager do if there is consensus ''among users and developers'' that an issue is valid but there is no good solution? From noreply at ubuntu.com Tue Jul 23 20:24:32 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 23 Jul 2013 20:24:32 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/HowToFix=22_by_tagatac?= Message-ID: <20130723202432.11137.85400@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/HowToFix" page has been changed by tagatac: http://wiki.ubuntu.com/Bugs/HowToFix?action=diff&rev1=10&rev2=11 Comment: page duplicated at developer.ubuntu.com + #REFRESH 0 http://developer.ubuntu.com/packaging/html/fixing-a-bug.html - ## page was renamed from DanielHolbach/Bugs/HowToFix - <> - ||<>|| - - - = Fixing a bug in Ubuntu = - == Introduction and Prerequisites == - - If you followed the instructions to [[UbuntuDevelopment/GettingSetUp|get set up with Ubuntu Development]], you should be all set and ready to go. - - {{http://daniel.holba.ch/temp/guide/_images/fixing-a-bug.png}} - - ## XXX: add as attachment - - As you can see in the image above, there are no surprises in the process of fixing bugs in Ubuntu: you find a problem, you get the code, work on the fix, test it, push your changes to Launchpad and ask for it to be reviewed and merged. In this guide we will go through all the necessary steps one by one. - - == Finding the problem == - - There are a lot of different ways to find things to work on. It might be a bug report you are encountering yourself (which gives you a good opportunity to test the fix), or a problem you noted elsewhere, maybe in a bug report. - - [[http://harvest.ubuntu.com|Harvest]] is where we keep track of various TODO lists regarding Ubuntu development. It lists bugs that were fixed upstream or in Debian already, lists small bugs (we call them 'bitesize'), and so on. Check it out and find your first bug to work on. - - == Get the code == - - If you know which source package contains the code that shows the problem, it’s trivial. Just type in: - {{{ - bzr branch lp:ubuntu/}}} - - where `` is the name of the source package. This will check out the code of the latest Ubuntu development release. If you need the code of a [[StableReleaseUpdate|stable release]], let's say `hardy`, you would type in: - - {{{ - bzr branch lp:ubuntu/hardy/}}} - - ## XXX: What if they don't know the source package name? - - == Work on a fix == - - There are entire books written about finding bugs, fixing them, testing them, etc. If you are completely new to programming, try to fix easy bugs such as obvious typos first. Try to keep changes as minimal as possible and document your change and assumptions clearly. - - Before working on a fix yourself, make sure to investigate if nobody else has fixed it already or is currently working on a fix. Good sources to check are: - * Upstream (and Debian) bug tracker (open and closed bugs), - * Upstream revision history (or newer release) might have fixed the problem, - * bugs or package uploads of Debian or other distributions. - - If you find a patch to fix the problem, running this command in the source directory should apply the patch: - {{{ - patch -p1 < ../bugfix.patch}}} - - Refer to the `patch(1)` manpage for options and arguments such as `--dry-run`, `-p`, etc. - - == Testing the fix == - - To build a test package with your changes, run these commands: - {{{ - bzr bd -- -S -us -uc - pbuilder-dist build ../_.dsc}}} - - This will create a source package from the branch contents (`-us -uc` will just omit the step to sign the source package) and `pbuilder-dist` will build the package from source for whatever release you choose. - - Once the build succeeded, install the package from `~/pbuilder/_result/` (using `sudo dpkg -i _.deb`). Then test to see if the bug is fixed. - - == Documenting the fix == - - It is very important to document your change sufficiently so developers who look at the code in the future won't have to guess what your reasoning was and what your assumptions were. Every Debian and Ubuntu package source includes `debian/changelog`, where changes of each uploaded package are tracked. - - The easiest way to do this is to run: - {{{ - dch -i}}} - - This will add a boilerplate changelog entry for you and launch an editor where you can fill out the blanks. An example of this could be: - {{{ - specialpackage (1.2-3ubuntu4) natty; urgency=low - - * debian/control: updated description to include frobnicator (LP: #123456) - - -- Emma Adams Sat, 17 Jul 2010 02:53:39 +0200}}} - - `dch` should fill out the first and last line of such a changelog entry for you already. Line 1 consists of the source package name, the version number, which Ubuntu release it is uploaded to, the urgency (which almost always is ‘low’). The last line always contains the name, email address and timestamp (in RFC 2822 format) of the change. - - With that out of the way, let’s focus on the actual changelog entry itself: it’s very important to document: - 1. where the change was done - 1. what was changed - 1. where the discussion of the change happened - - In our (very sparse) example the last point is covered by "(LP: #123456)" which refers to Launchpad bug 123456. Bug reports or mailing list threads or specifications are usually good information to provide as a rationale for a change. As a bonus, if you use the `LP: #` notation for Launchpad bugs, the bug will be automatically closed when the package is uploaded to Ubuntu. - - - == Committing the fix == - - With the changelog entry written and saved, you can just run: - {{{ - debcommit}}} - - and the change will be committed (locally) with your changelog entry as a commit message. - - To push it to Launchpad, as the remote branch name, you need to stick to the following nomenclature: - {{{ - lp:~/ubuntu///}}} - - This could for example be: - {{{ - lp:~emmaadams/ubuntu/natty/specialpackage/fix-for-123456}}} - - So if you just run: - {{{ - bzr push lp:~emmaadams/ubuntu/natty/specialpackage/fix-for-123456 - bzr lp-open}}} - - you should be all set. The push command should push it to Launchpad and the second command will open the Launchpad page of the remote branch in your browser. There find the "(+) Propose for merging" link, click it to get the change reviewed by somebody and included in Ubuntu. If you can't find anyone to review your work, you can also click the "Subscribe someone else" link and add ubuntu-sponsors. - - ---- - [[CategoryBugSquad]] - From magus_penwolf at hotmail.com Wed Jul 24 10:43:53 2013 From: magus_penwolf at hotmail.com (Merlin the Magician) Date: Wed, 24 Jul 2013 03:43:53 -0700 Subject: security update issues Message-ID: I have Important security updates in the update manager that will not update, I am confused how to proceed. .......... Important security updates libxml2 GNOME XML library (Size 810 KB) libxml2-utls XML utilities (Size 88 KB) python-libxml2 Python bindings for the GNOME XML library (Size 221 KB) W: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/libx/libxml2/libxml2_2.7.6.dfsg-1ubuntu1.9_i386.deb 404 Not Found [IP: 91.189.92.201 80] ..... I do not know what to do? -------------- next part -------------- An HTML attachment was scrubbed... URL: From alessandro.menti at hotmail.it Thu Jul 25 12:34:24 2013 From: alessandro.menti at hotmail.it (Alessandro Menti) Date: Thu, 25 Jul 2013 14:34:24 +0200 Subject: security update issues In-Reply-To: References: Message-ID: Il 24/07/2013 12:43, Merlin the Magician ha scritto: > I have Important security updates in the update manager that will not > update, I am confused how to proceed. > .......... > Important security updates > > libxml2 > GNOME XML library (Size 810 KB) > > libxml2-utls > XML utilities (Size 88 KB) > > python-libxml2 > Python bindings for the GNOME XML library (Size 221 KB) > > W: Failed to fetch > http://security.ubuntu.com/ubuntu/pool/main/libx/libxml2/libxml2_2.7.6.dfsg-1ubuntu1.9_i386.deb > 404 Not Found [IP: 91.189.92.201 80] > ..... > I do not know what to do? > Hi Merlin, it seems like a new version of libxml2 has been published in the meantime, as the "old" update introduced a new bug [1]. Try searching for new updates again and then installing libxml2. Hope this helps, Alessandro Menti [1] http://changelogs.ubuntu.com/changelogs/pool/main/libx/libxml2/libxml2_2.7.6.dfsg-1ubuntu1.10/changelog -- A neutron walks into a bar and asks how much for a drink. The bartender replies "for you, no charge". -- Sheldon Cooper, The Big Bang Theory From alegomaster at yahoo.ca Fri Jul 26 12:29:48 2013 From: alegomaster at yahoo.ca (Alex) Date: Fri, 26 Jul 2013 14:29:48 +0200 Subject: Ubuntu-bugsquad Digest, Vol 85, Issue 5 Message-ID: <2eafe5yxvqrohfe7lld83ieh.1374841788708@email.android.com> ubuntu-bugsquad-request at lists.ubuntu.com wrote: >Send Ubuntu-bugsquad mailing list submissions to > ubuntu-bugsquad at lists.ubuntu.com > >To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >or, via email, send a message with subject or body 'help' to > ubuntu-bugsquad-request at lists.ubuntu.com > >You can reach the person managing the list at > ubuntu-bugsquad-owner at lists.ubuntu.com > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Ubuntu-bugsquad digest..." > > >Today's Topics: > > 1. Re: security update issues (Alessandro Menti) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Thu, 25 Jul 2013 14:34:24 +0200 >From: Alessandro Menti >To: Merlin the Magician >Cc: "ubuntu-bugsquad at lists.ubuntu.com" > >Subject: Re: security update issues >Message-ID: >Content-Type: text/plain; charset="ISO-8859-1" > >Il 24/07/2013 12:43, Merlin the Magician ha scritto: >> I have Important security updates in the update manager that will not >> update, I am confused how to proceed. >> .......... >> Important security updates >> >> libxml2 >> GNOME XML library (Size 810 KB) >> >> libxml2-utls >> XML utilities (Size 88 KB) >> >> python-libxml2 >> Python bindings for the GNOME XML library (Size 221 KB) >> >> W: Failed to fetch >> http://security.ubuntu.com/ubuntu/pool/main/libx/libxml2/libxml2_2.7.6.dfsg-1ubuntu1.9_i386.deb >> 404 Not Found [IP: 91.189.92.201 80] >> ..... >> I do not know what to do? >> >Hi Merlin, >it seems like a new version of libxml2 has been published in the >meantime, as the "old" update introduced a new bug [1]. Try searching >for new updates again and then installing libxml2. > >Hope this helps, >Alessandro Menti > >[1] >http://changelogs.ubuntu.com/changelogs/pool/main/libx/libxml2/libxml2_2.7.6.dfsg-1ubuntu1.10/changelog >-- >A neutron walks into a bar and asks how much for a drink. >The bartender replies "for you, no charge". > -- Sheldon Cooper, The Big Bang Theory > > > >------------------------------ > >-- >Ubuntu-bugsquad mailing list >Ubuntu-bugsquad at lists.ubuntu.com >https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > >End of Ubuntu-bugsquad Digest, Vol 85, Issue 5 >********************************************** From retail at the-gammons.net Wed Jul 31 20:01:42 2013 From: retail at the-gammons.net (Ross Gammon) Date: Wed, 31 Jul 2013 22:01:42 +0200 Subject: Bug assigned to Ubuntu but there is no package Message-ID: <51F96D26.60503@the-gammons.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am new to the bugsquad, so apologies if this has been asked before. I was just looking at some unassigned bugs and found one that was listed as affecting a project, and also Ubuntu. The project is on a PPA, and there is no package in Ubuntu. The bug is "in progress" under the project, but the Ubuntu entry is showing "new" and "undecided". Is there a way to remove the entry against Ubuntu? There is no Ubuntu package you can assign it to. Regards, Ross -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJR+W0WAAoJEFP+e72miRD8fjAP/AwQ8SJ+867WGp5mrGYmqIZI f/L3l07z2iR0Initem1QnYyqch3BUssqepTeRloWclSCm409nqL+UciyR+1SgBJc +1RgTd5eCXIqq028VNb23wWwTscVzVlYlecvcKeTSUH7gZXafT2eKX0cFHk+7gLs WHQZcVLZsHm6muoQ1XFiqIJoAEHuCXKpjpHlai5RmoGZ03lKnYQrLxgVanbIBpjJ SpeDOS1SDkWxuRMecbgBdLLDo4lmC7TFKwUrmhUa3eyAu8uaLA06Tgmd1830+Tpv uc2kbyqwavyhQD06SxJm1TVmFsEXrIfILUxzo9pHvWR8gv3BBL8OkYubxpD7k2ob OOTnmv4b6O78c3rGUHJEK6fs2n/NPw7UeGSMrhBqde+0lRghxJQZ6Pu+ao4DtXsO qlwRnHoIyrS2SZXVR6tL4+3Q9FIXgBE6KmyEQDwqcA7ACUIsFlinGK9EgxprPIYo G7e+UY4+ad6eciOsnVDFrYdyispShkogH4jwxU7PKUKHdnh1745AN6b0+yWFa4qi qhMIEktLZjpX+6CVolpESoLpgmgX4Ig6PbeMhRNi8iTm6vNLXmAxYUp9lbR1eVfn FQH6ABXd4OFV8kFzFaQABdLkrBRbn9NwYg9vAQTjcHcp9vhHbOBjYC6lSLWpMts9 6WBtn4L98Hh+ZRLWWPTR =2Qz4 -----END PGP SIGNATURE----- From teward at ubuntu.com Wed Jul 31 21:13:58 2013 From: teward at ubuntu.com (Thomas Ward) Date: Wed, 31 Jul 2013 17:13:58 -0400 Subject: Bug assigned to Ubuntu but there is no package In-Reply-To: <51F96D26.60503@the-gammons.net> References: <51F96D26.60503@the-gammons.net> Message-ID: Hi, Ross. Can you provide a link for the bug so I can take a peek? On Wednesday, July 31, 2013, Ross Gammon wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I am new to the bugsquad, so apologies if this has been asked before. > I was just looking at some unassigned bugs and found one that was > listed as affecting a project, and also Ubuntu. > > The project is on a PPA, and there is no package in Ubuntu. The bug is > "in progress" under the project, but the Ubuntu entry is showing "new" > and "undecided". > > Is there a way to remove the entry against Ubuntu? There is no Ubuntu > package you can assign it to. > > Regards, > > Ross > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with undefined - http://www.enigmail.net/ > > iQIcBAEBAgAGBQJR+W0WAAoJEFP+e72miRD8fjAP/AwQ8SJ+867WGp5mrGYmqIZI > f/L3l07z2iR0Initem1QnYyqch3BUssqepTeRloWclSCm409nqL+UciyR+1SgBJc > +1RgTd5eCXIqq028VNb23wWwTscVzVlYlecvcKeTSUH7gZXafT2eKX0cFHk+7gLs > WHQZcVLZsHm6muoQ1XFiqIJoAEHuCXKpjpHlai5RmoGZ03lKnYQrLxgVanbIBpjJ > SpeDOS1SDkWxuRMecbgBdLLDo4lmC7TFKwUrmhUa3eyAu8uaLA06Tgmd1830+Tpv > uc2kbyqwavyhQD06SxJm1TVmFsEXrIfILUxzo9pHvWR8gv3BBL8OkYubxpD7k2ob > OOTnmv4b6O78c3rGUHJEK6fs2n/NPw7UeGSMrhBqde+0lRghxJQZ6Pu+ao4DtXsO > qlwRnHoIyrS2SZXVR6tL4+3Q9FIXgBE6KmyEQDwqcA7ACUIsFlinGK9EgxprPIYo > G7e+UY4+ad6eciOsnVDFrYdyispShkogH4jwxU7PKUKHdnh1745AN6b0+yWFa4qi > qhMIEktLZjpX+6CVolpESoLpgmgX4Ig6PbeMhRNi8iTm6vNLXmAxYUp9lbR1eVfn > FQH6ABXd4OFV8kFzFaQABdLkrBRbn9NwYg9vAQTjcHcp9vhHbOBjYC6lSLWpMts9 > 6WBtn4L98Hh+ZRLWWPTR > =2Qz4 > -----END PGP SIGNATURE----- > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > ------ Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From retail at the-gammons.net Wed Jul 31 21:29:20 2013 From: retail at the-gammons.net (Ross Gammon) Date: Wed, 31 Jul 2013 23:29:20 +0200 Subject: Bug assigned to Ubuntu but there is no package In-Reply-To: References: <51F96D26.60503@the-gammons.net> Message-ID: <51F981B0.9000601@the-gammons.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 https://bugs.launchpad.net/ubuntu/+bug/1002598 On 07/31/2013 11:13 PM, Thomas Ward wrote: > Hi, Ross. Can you provide a link for the bug so I can take a > peek? > > On Wednesday, July 31, 2013, Ross Gammon wrote: > > Hi, > > I am new to the bugsquad, so apologies if this has been asked > before. I was just looking at some unassigned bugs and found one > that was listed as affecting a project, and also Ubuntu. > > The project is on a PPA, and there is no package in Ubuntu. The bug > is "in progress" under the project, but the Ubuntu entry is showing > "new" and "undecided". > > Is there a way to remove the entry against Ubuntu? There is no > Ubuntu package you can assign it to. > > Regards, > > Ross >> >> -- Ubuntu-bugsquad mailing list Ubuntu-bugsquad at lists.ubuntu.com >> >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> > > ------ Thomas > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJR+YGwAAoJEFP+e72miRD8c5wP/ReMVTWFGuV8wItyzjDVGYqS IOgWR5zbMo9GohJx0Kd6Yk6DBBW3bC2NHscOSAivl1Ogmt8YUGIebZVVyfHI+3We qRsW4kKKwFMbinWkChnjw0drKyJ17NHLae1Vw3meLQkI0YeiCNYq/5CV8+pUlICN KR5+3kO/GdihN6IJGzgt9kOmDmFqaW7l8hmMk6G6uVMlGOq9n7Bia+883sJn4Xa5 z74d8j3j11ArYY5owAycQdXLzKUH1Xy5Yw+YTCWAnefgiBJV8zPQvqc+dm5k9Fa2 eEOcsEDRFMap59HvTPr1CSt/G0o/jOoO9hWqvzt97WkLYL4d5XsE/7bRvhd9eOIo Fp8RjknrcpeP6s8GoPAUxyrP4u/9xr5daDiTd/E6CreOOh3pnU/HZloQtVPzKbLQ leBQTFXe1AANz6vTpzSMLtVD7DNdDmfE8cSNrkNC+f2qfyeO1qtYdSzh8lalI/tk rjNI9Tgekj4P4lR897mjGdn8ObfotsHyQ2Rlavrm4Y0bEtSYL30TpRf1W2990NxY mYyF/qSRMYBJjLiByCRQXKA3Vrlwt2Sn72b4Sm6wFUlk2IoU8Bg9ZZxSIVgjJErC 97/ZHWXIroARCrsPdJ8XXrYeG2W/giYcSRbRMxAW5f4kU0VO20I3S+Cp8luG2mOW PVeEZeGFH4E98o8eQkjc =6p/I -----END PGP SIGNATURE----- From fitoschido at gmail.com Wed Jul 31 23:57:16 2013 From: fitoschido at gmail.com (Adolfo Jayme Barrientos) Date: Wed, 31 Jul 2013 18:57:16 -0500 Subject: Bug assigned to Ubuntu but there is no package In-Reply-To: <51F981B0.9000601@the-gammons.net> References: <51F96D26.60503@the-gammons.net> <51F981B0.9000601@the-gammons.net> Message-ID: I removed the Ubuntu task from the bug report, thank you.