[Bug 1442857] Re: Install updates shows a percentage over 100
I don't think we've changed the download side of the server in a long time. The size reported by click-package-index is 867687 which matches the UI. Downloading the file gives a file of that size, and wget reported that many bytes transferred. This suggests to me a client issue, but we can look again if you have more evidence that it is the server. The hash error in the logs suggests that it may be counting bytes for a redownload, or possibly that the client downloaded too much somehow, and that led to the hash error. Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442857 Title: Install updates shows a percentage over 100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-download-manager/+bug/1442857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 445303]
(In reply to Simon McVittie from comment #8) In the absence of a recent polkit release, I'm looking into updating Debian experimental's polkit (which currently includes this patch) to current git master. This looks suspiciously like Bug #60847. James, does the patch that was merged for that bug look OK? It stops using the child watch at all, and only reads stdout, which seems a more correct solution to this. Hi, That does sound rather similar, yes, though the symptoms in the arch bug sound a bit different. If it's not using the child watch then the problem may well be gone. Unfortunately I can't remember the specifics of a race condition from over 4 years ago to say for sure whether it will be handled by the other patch. Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/445303 Title: policykit-1 password dialog sometimes hangs To manage notifications about this bug go to: https://bugs.launchpad.net/policykit/+bug/445303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1408644] Re: App namespace move to appname.devname
Hi, The store now accepts the new style. The old style is still accepted, but developers signing up to the site today will find it hard to use it because they can't set their old-style namespace. You can go ahead and make any changes that expect the new style to work live. Thanks, James ** Changed in: developer-portal Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1408644 Title: App namespace move to appname.devname To manage notifications about this bug go to: https://bugs.launchpad.net/click-reviewers-tools/+bug/1408644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403468] [NEW] dnsmasq profile incomplete for lxc usage
Public bug reported: Hi, I am using the dnsmasq profile with lxc, and I am getting DENIED messages like: Dec 16 22:26:58 superstar kernel: [226445.568383] type=1400 audit(1418768818.310:865): apparmor=DENIED operation=truncate profile=/usr/sbin/dnsmasq name=/var/lib/misc/dnsmasq.lxcbr0.leases pid=1472 comm=dnsmasq requested_mask=w denied_mask=w fsuid=118 ouid=0 Adding rw for that path obviously makes it go away, and seems like a reasonable change. Thanks, James ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apparmor-profiles 2.8.95~2430-0ubuntu5.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 17 11:27:18 2014 PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-43-generic root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: [modified] mtime.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: 2014-12-16T20:38:31.370339 mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2014-12-17T11:21:47.159017 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403468 Title: dnsmasq profile incomplete for lxc usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1403468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403050] [NEW] Firefox profile denied messages with google hangouts
Public bug reported:
Hi,
I am using apparmor on trusty, with the firefox profile in enforce mode.
I have just tried hangouts for the first time under the profile, and
there are two DENIED:
Dec 16 12:36:31 superstar kernel: [191033.672376] type=1400
audit(1418733391.061:436): apparmor=DENIED operation=open
profile=/usr/lib/firefox/firefox{,*[^s][^h]} name=/dev/video0
pid=19492 comm=GoogleTalkPlugi requested_mask=r denied_mask=r
fsuid=1000 ouid=0
Which means that it thinks I have no webcam. I don't know if this should be
allowed or not. I'd prefer to enable
my webcam in a hangout, but I can see an argument for denying this to firefox.
Dec 16 12:36:37 superstar kernel: [191039.824064] type=1400
audit(1418733397.217:440): apparmor=DENIED operation=mknod
profile=/usr/lib/firefox/firefox{,*[^s][^h]} name=/run/shm/google-
nacl-shm--19492.3 pid=19492 comm=GoogleTalkPlugi requested_mask=c
denied_mask=c fsuid=1000 ouid=1000
I assume this is something to do with NaCl. I haven't noticed anything
that is broken by this.
Thanks,
James
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apparmor 2.8.95~2430-0ubuntu5.1
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Dec 16 12:58:32 2014
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-43-generic
root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog:
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403050
Title:
Firefox profile denied messages with google hangouts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1403050/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1328281] Re: bzr-buildpackage fails GPG signing
Hi, Does signing succeed if you run bzr-buildpackage -- -k$KEYID ? Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1328281 Title: bzr-buildpackage fails GPG signing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzr-builddeb/+bug/1328281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Blueprint servercloud-r-charmworld] Juju Charm Store Web UI improvements
Blueprint changed by James Westby: Whiteboard changed: User Stories: Risks: Test Plans: Release Note: (Spec details and work item documentation needed) - [12-dec-2012: a.rosales] --- Discussion at UDS --- Things to fix for 13.04 in lp:charmworld, including addition of charm ratings to the UI. -Discuss adding any possible usage statistics -Discuss adding provider testing status Current charm browser: http://jujucharms.com/ - https://launchpad.net/charmworld Example : https://crate.io/packages/requests/ Ideas to add to the charm browser: -Charm Quality: https://juju.ubuntu.com/docs/charm-quality.html -Provider testing status (currently in Jenkins) -Be able to easily drill down to specific release charms -If you have an LTS version of the charm is there a mechanism to tell the user if they have the latst and greatest charm. -Group the charms into categories -tag charms to be part of a group Ordering: Quality, Assesment, Test results incorporation, usage statistics WI: [] add charm Charm Quality qualatative assesment rating to the charms in the Charm Browser - [marcoceppi] include provider testing status in the charm browser - -https://jenkins.qa.ubuntu.com/view/Charms/ + [marcoceppi] include provider testing status in the charm browser (https://jenkins.qa.ubuntu.com/view/Charms/): TODO [] list charms that are curently failing in a given provider [] include download stats from the charm store [] have a link to ask ubuntu which passes appropriate tags onto Ask Ubuntu [] add login via ubuntu SSO [] SEO Optimization for current release charms (google search for juju wordpress charm) [] series linking from charm details [] qualitative assement on charm display, + on listing, (stretch) sorting [] user ratings [] define rubric/catalog of tags [] update charm proof to be tag aware [] upstream discussion of tags [] charmworld to have tag based display [] pull testing artifacts [] download stats recorded [] most popular downloads by series [] twitter feed on homepage [] handover to twitter account to jorge [] login via ubuntu sso [enablement for quality assessment forms] [] tracking average review time on charmers review queue, avg time in the queue. for trending direction analysis [] charm revisions from store displayed more prominently. [] check if we can make '.' a valid character in charms and also 'juju' and 'ubuntu' [] charm proof rewrite [] beautiful error pages [] breadcrumb links on tools 404 [] hooks in breadcrumbs 404 [] symlinks more relevant [] tab the user interface for a charm [] jorge fixes readme for markdown display [] time travel on revisions, ie what store revision existing at a given point in time -- Juju Charm Store Web UI improvements https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-charmworld -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1054460] Re: Error 500 while purchasing
** Changed in: ubuntu-website Status: New = Invalid ** Also affects: software-center Importance: Undecided Status: New ** No longer affects: software-center ** Also affects: software-center-agent Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054460 Title: Error 500 while purchasing To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/1054460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054460] Re: Error 500 while purchasing
Hi, The support address is actually isd-supp...@canonical.com. I'm not sure why it suggests webmaster@, I've filed a bug to change that. If you email isd-support@ then someone will be sure to help you through this problem, and escalate it for fixing if there is a problem in the code or with the service. Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054460 Title: Error 500 while purchasing To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/1054460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007327] Re: [needs-packaging] pkgme should be packaged
** Changed in: ubuntu Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007327 Title: [needs-packaging] pkgme should be packaged To manage notifications about this bug go to: https://bugs.launchpad.net/pkgme/+bug/1007327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007327] Re: [needs-packaging] pkgme should be packaged
We think the packaging should live outside the lp:pkgme branch. We suggest lp:ubuntu/pkgme. Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007327 Title: [needs-packaging] pkgme should be packaged To manage notifications about this bug go to: https://bugs.launchpad.net/pkgme/+bug/1007327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1052721] Re: Some packages say not available for your current Ubuntu version when viewed from purchase list
On Wed, 19 Sep 2012 08:31:45 -, Michael Nelson 1052...@bugs.launchpad.net wrote: The attached sca branch only fixes the HIB thank-you page on software- center-agent (so that when buying an app that is multi-arch using Chromium, you won't be told that it's not available yet). We also discussed on irc [1] whether sca could potentially provide a work-around for USC's Reinstall previous purchases by appending :i386 to all multi-arch apps, but in the end it seems this isn't possible, because at that point (the /subscriptions/ api handler), sca does not currently know the client distroseries (and whether it will understand :i386 suffixes) [2]. Will an old distroseries that doesn't understand that syntax be able to install that package if it can find it? Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1052721 Title: Some packages say not available for your current Ubuntu version when viewed from purchase list To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/1052721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1042396] Re: bzr-builddeb fails to import-dsc with native package on Ubuntu 12.04
** Also affects: bzr-builddeb Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1042396 Title: bzr-builddeb fails to import-dsc with native package on Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/bzr-builddeb/+bug/1042396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Moving udd away from sqlite
On Tue, 03 Jul 2012 18:12:06 +0100, James Westby james.wes...@canonical.com wrote: I think I've addressed all the comments so far, and I'm keen to move ahead with the deployment before we get too close to the weekend. Therefore if there are no objections I'd like to merge these and deploy Wed morning UK time. Hi, The importer is now running on storm again. There were a couple of bugs that I fixed, but I don't believe bad data should have come from either of them. There have been some database locked errors, but so far everything has kept running without deadlocking. I'll continue to keep an eye on it while we work on the postgres stuff. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Moving udd away from sqlite
On Thu, 21 Jun 2012 11:29:08 -0400, James Westby james.wes...@canonical.com wrote: I need to do that, as well as some unicode fixes. I'll get those done and up for review by the end of this week. Belatedly here they are: https://code.launchpad.net/~james-w/udd/storm/+merge/112983 https://code.launchpad.net/~james-w/udd/storm-unicode-fixes/+merge/112984 https://code.launchpad.net/~james-w/udd/storm-sqlite-db-provider/+merge/112985 I'll then spin up an ec2 instance to run in parallel and do everything except push the branches back, and leave this running over the weekend. I spun up three udd instances on ec2, each rigged to not hit codehosting, but to have something like the db access pattern of doing imports. There was one running tip of trunk, one running the code we tried to deploy last time, and one running my current code. After leaving them for a weekend grep database is locked debug_log* gives: trunk: 0 old code: 7199 new code: 0 (with me logging in a couple of times to kill the old code because it was in a deadlocked state.) which is hopefully good evidence that we should have fewer issues this time. The new code also imported roughly the same number of packages as trunk in that time, so there doesn't seem to be any large performance impact from the changes. Then on Tuesday morning my time (starting 1300 UTC) I'll do a deployment of the code to production if (reviews, ec2) don't show any problems. We can then carefully monitor the service for the next few days. I'm ready to do this once the code is reviewed. I'll send another email before I do it. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
[Bug 1019700] [NEW] Declares that it depends on testresources at the python level, but the package doesn't depend on it
Public bug reported: launchpadlib has testresources listed in its requires.txt, though it is only a test dependency. The package in Ubuntu doesn't depend on python-testresources. If you try and use pkg_resources in any project that depends on launchpadlib you get errors if python-testresources isn't installed. The packaging could add the dependency, but it's only needed to run launchpadlib's test suite. launchpadlib could move testresources to be a test dependency (either test_requires or whatever the spelling it, or an extra_requires for [test] or however that is done.) In the meantime the workaround is to install python-testresources if you need to use pkg_resources in a project that depends on launchpadlib. Thanks, James ** Affects: launchpadlib Importance: Undecided Status: New ** Affects: python-launchpadlib (Ubuntu) Importance: Undecided Status: New ** Affects: python-launchpadlib (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: python-launchpadlib (Ubuntu) Importance: Undecided Status: New ** Also affects: python-launchpadlib (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019700 Title: Declares that it depends on testresources at the python level, but the package doesn't depend on it To manage notifications about this bug go to: https://bugs.launchpad.net/launchpadlib/+bug/1019700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Moving udd away from sqlite
On Thu, 21 Jun 2012 18:22:22 +0200, Vincent Ladeuil vila+...@canonical.com wrote: Rollback is to revert the storm code again Restore the dbs. I don't think we should do that if we have no evidence of data corruption. We'd be repeating work for no benefit. Rollback is to stop the importer, revert the config changes, restore the dbs. No need, as changes would be written to postgres, so just switching back to sqlite is an effective restore. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
[Bug 1014802] Re: merge-upstream changes po files behind your back
** Package changed: bzr-builddeb (Ubuntu) = bzr -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014802 Title: merge-upstream changes po files behind your back To manage notifications about this bug go to: https://bugs.launchpad.net/bzr/+bug/1014802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014802] Re: merge-upstream changes po files behind your back
Hi, The merge is done by the po_merge plugin. http://doc.bazaar.canonical.com/beta/en/whats-new/whats-new-in-2.5.html #po-merge-plugin bzr-builddeb might be causing this to activate when using in bzr branches, but I don't think so. Do you have the config described in that link set on your machine? Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014802 Title: merge-upstream changes po files behind your back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzr-builddeb/+bug/1014802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Moving udd away from sqlite
On Mon, 18 Jun 2012 10:45:26 +0200, Vincent Ladeuil vila+...@canonical.com wrote: James Westby james.wes...@canonical.com writes: On Fri, 15 Jun 2012 12:34:12 +0200, Vincent Ladeuil vila+...@canonical.com wrote: It's not magic. It's moving from a database that's not designed for concurrent use to one that is designed for concurrent use. Despite not being designed for concurrent use, it *is* used this way and lock contentions have been encountered leading me to believe that the actual *design* needs to be fixed. The fact that changing the db is triggering more contentions is a symptom of a deeper issue. Changing the db access layer is triggering that, we were still running on the same (non-multi-user db). I agree that the design needs to be fixed, and that's exactly what we're taking about, fixing it by moving a db that is designed for multi-user use. It looks like your understanding of the issue is better than mine here, would you mind sharing that knowledge in an automated test (with the added benefit that we won't regress in this area) ? Just this week-end we had an add-import-jobs failure: Traceback (most recent call last): File /srv/package-import.canonical.com/new/scripts/bin/add-import-jobs, line 5, in module sys.exit(main()) File /srv/package-import.canonical.com/new/scripts/udd/scripts/add_import_jobs.py, line 17, in main icommon.create_import_jobs(lp, status_db) File /srv/package-import.canonical.com/new/scripts/udd/icommon.py, line 304, in create_import_jobs status_db.add_import_jobs(checked, newest_published) File /srv/package-import.canonical.com/new/scripts/udd/icommon.py, line 633, in add_import_jobs self._add_job(c, package, self.JOB_TYPE_NEW) File /srv/package-import.canonical.com/new/scripts/udd/icommon.py, line 615, in _add_job datetime.utcnow(), None, None)) sqlite3.OperationalError: database is locked So we already know that add_import_jobs is involved in the bug (with the current sqlite-based implementation), who is the other user in this case and how can this be reproduced ? Each connection to sqlite is another user, so each of the cron scripts, as well as the imports themselves, and several connections within mass-import are all the users. When a write operation is started a global lock is acquired that locks out any other writers until the operation is complete. If the lock is held then the library will wait up to a timeout (configured to be 30s for udd) for the lock to be released before giving up. The errors like the above occur when the timeout is reached, so either another transaction took more than 30s to release the lock, or there were lots of connections trying to take the lock, and this one didn't win before the 30s was up. When we change to storm it forces pysqlite in to a higher isolation level, so that transactions are started when any statement is executed. My guess is that this means locks are taken more frequently and are held for longer, giving more contention errors. Postgres doesn't have a global lock, it has table or row locks, so that clients will only hit lock contention if they are changing the same data, which will be much less frequent. How can I show that in an automated test? I can write an XFAIL test that if two connections are opened, one starts a transaction and then the other hits an locking exception if it tries to do anything, but that doesn't seem to prove much about the operation of the system. I.e. reproducing the add_import_jobs failure in a test that will fail with sqlite and succeed with your changes will demonstrate we've captured (and fixed) at least one lock contention. We are dealing with probabilistic failure though. I can demonstrate that in a deterministic situation changing two separate tables under sqlite will take global locks, but I can't prove that we will never get contention under postgres. If the test suite cannot be trusted to catch most of the issues that happen in production, the test suite should be fixed. You're not implying that testing in production being needed, the test suite is useless right ? No, I'm saying that the only measure of whether something runs correctly in production is whether it runs in production. From that, can we imagine a test that will import a few packages and compare the corresponding dbs ? We can do that as part of testing the migration script. It can be restarted with the dbs from whenever the transition starts and it will catch up in roughly the between starting the transition and rolling back. There may be a few bugs due to replaying things, but we do it all the time (e.g. removing revids and re-importing when someone does push --overwrite) As in requeue --full ? requeue --zap-revids ? None of them is used on a daily basis but my limited experience there never triggered issues
Re: Upgrading pristine-xz on jubany
On Fri, 15 Jun 2012 10:32:59 +0200, Vincent Ladeuil vila+...@canonical.com wrote: Barry Warsaw ba...@ubuntu.com writes: On Jun 14, 2012, at 05:21 PM, Vincent Ladeuil wrote: - I'm already running successful tests inside a quantal lxc container :) It has become for many of us not just a nice-to-have but a must-have for Ubuntu development. That's my understanding as well. Here are my last achievements for the week: - I got in touch with pristine-tar maintainers resulting in a trivial bugfix included in 1.25. This is a small step in getting *known* as a primary consumer but it also demonstrates that we can get fixes upstream quickly (1.25 has already been uploaded to sid and quantal). - I got in touch with xz maintainers and a fix is on its way there (many thanks to Lasse Collin for its invaluable help here). This will require an additional fix to pristine-xz which I will submit as soon as I can test the xz fix). With these fixes in place, on quantal, it should remain only 10 pristine-tar import failures out of the current 338 on jubany. That's great work Vincent, I look forward to it being deployed, however that happens :-) Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Moving udd away from sqlite
On Fri, 15 Jun 2012 12:34:12 +0200, Vincent Ladeuil vila+...@canonical.com wrote: It's not magic. It's moving from a database that's not designed for concurrent use to one that is designed for concurrent use. Despite not being designed for concurrent use, it *is* used this way and lock contentions have been encountered leading me to believe that the actual *design* needs to be fixed. The fact that changing the db is triggering more contentions is a symptom of a deeper issue. Changing the db access layer is triggering that, we were still running on the same (non-multi-user db). I agree that the design needs to be fixed, and that's exactly what we're taking about, fixing it by moving a db that is designed for multi-user use. Well, when the correctness and safety is demonstrated, the context (and hence my own answer) will probably be different but until then I just can't say. And I'm very reluctant to fork without an actual plan for merging back: how to know when it's safe how to actually achieve it. And I have no idea (nor time right now) to debug the fallouts of such a change that the actual package importer doesn't need. Hence my tendency to consider that demonstrating the validity of this change should be achieved first. But you just said above that you *do* think it needs to be fixed? How can we demonstrate the validity of the change? We can only demonstrate that it doesn't break production by running the changes in production. What would satisfy you that it was unlikely to break production? Would there be a script to migrate from sqlite to PG ? Yes. Can the package importer be re-started with empty dbs and catch up (how long will it take ? Days ? Weeks ?). Can this trigger bugs because the importer don't remember what it pushed to lp ? It can be restarted with the dbs from whenever the transition starts and it will catch up in roughly the between starting the transition and rolling back. There may be a few bugs due to replaying things, but we do it all the time (e.g. removing revids and re-importing when someone does push --overwrite) Or do you expect us to see another peek like http://webnumbr.com/ubuntu-package-import-failures.from%282012-01-24%29 ? Hopefully not. Yes, that's why we're not in a position to safely accept such a change ! And all the time spent on integrating these changes is not spent on allowing them to be accepted in good conditions. Sorry, I don't understand this, could you explain? but it demonstrated the locking problem and is how he came up with those options. Then the test improvements are certainly valuable to backport to lp:udd or is there nothing to reuse from the EC2 experiment ? It wasn't a set of unit tests, it was a set of tests of a live system, so nothing to backport. We have had a lot of experience recently working with Canonical IS to get new servers and new staging servers deployed. If you want a staging server, we'd be happy to help you and would gladly advocate for you in their priority queue. Great to hear :) I should come back soon on this topic, just a quick question though: are the new servers running lucid or precise ? New servers are being installed with precise. If an existing server is used it may be lucid, but there is a concerted effort to upgrade all machines to precise currently underway. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: [Bug 1006299] Re: Please merge kerneloops 0.12+git20090217-3
On Mon, 11 Jun 2012 13:21:00 -, Martin Pitt martin.p...@ubuntu.com wrote: Is that package still actually recommended upstream? The submit site has been down for quite a while, and that package uses really old technology (GTK 2, applets, etc.) It seems rather costly to keep large patches like submit-pipe and kerneloops-submit downstream. I believe we are still interested in getting the oops info in to errors.ubuntu.com, but much of the code is unrelated to that. The daemon part and submit-pipe is all that is really needed for that I think, though there may be a better way to structure it if we don't care about submitting to kerneloops as well. Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1006299 Title: Please merge kerneloops 0.12+git20090217-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1006299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1007327] Re: [needs-packaging] pkgme should be packaged
On Wed, 06 Jun 2012 09:22:27 -, Daniel Holbach daniel.holb...@ubuntu.com wrote: Somebody still needs to decide if we merge the packaging or if it should maybe live in a separate, maybe debian/-only(?), branch? I think it should live in an lp:ubuntu/pkgme branch :-) Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007327 Title: [needs-packaging] pkgme should be packaged To manage notifications about this bug go to: https://bugs.launchpad.net/pkgme/+bug/1007327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 912509] Re: Lots of requests to the checkout complete URL
On Wed, 16 May 2012 21:11:48 -, Gary Lasker gary.las...@canonical.com wrote: So, the _block_wk_handlers() method of softwarecenter/ui/gtk3/views/purchaseview.py is meant to block the title_change events after a successful purchase. This was added as part of the fix for bug 696861. This code has been there since Natty (April of 2011). That looks like it is just blocking the response to the events, but won't necessarily stop making requests. I'm not sure which bit of code is making the requests to be sure though. Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/912509 Title: Lots of requests to the checkout complete URL To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/912509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645404] Re: Support Private PPAs
Calling lp.people[lp.me.name].getArchiveSubscriptionURL(archive) once the archive has been found will get the url to be used for private PPAs. getArchiveSubscriptionURL Get a text line that is suitable to be used for a sources.list entry. It will create a new IArchiveAuthToken if one doesn't already exist. Parameters Parameter Value Description ws.op (required) Fixed: getArchiveSubscriptionURL archive (required) Link to a archive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/645404 Title: Support Private PPAs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: DEB_VENDOR package imports
On Thu, 03 May 2012 14:49:19 +0100, Dmitrijs Ledkovs dmitrij.led...@ubuntu.com wrote: I think, the lp:debian/* imports should be run with export DEB_VENDOR=Debian This should make the lp:debian/package to match the source package as it is unpacked/built on Debian. I'm agreed on this, and Colin pointed it out too and I filed a bug: https://bugs.launchpad.net/udd/+bug/911496 . Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Importer add-import-jobs cronjob temporarily disabled
On Sat, 28 Apr 2012 10:52:44 +0100, Max Bowsher _...@maxb.eu wrote: See https://bugs.launchpad.net/udd/+bug/990394 Thanks for catching this. Fwiw it's not normally an issue as it normally takes longer to run branch-distro.py and re-enable things, and once there has been another package published to the new release it only acts on all the packages once. For whatever reason that didn't happen this time. I'll reply to the bug with some comments about how it could be better handled in future. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: UDD importer making a nuisance of itself with v3 source format branches
On Fri, 13 Apr 2012 01:13:22 +0100, Max Bowsher _...@maxb.eu wrote: I've just had a conversation with cjwatson and slangasek on #ubuntu-release about the importer making a nuisance of itself by declaring a perfectly reasonable commit to be a collision / difference, and replacing it with one of its own. The key pain point here is the .pc/ directory. It's practically impossible to maintain a .pc/ directory checked into VCS without unnatural jumping through hoops. As a result, packages being seriously developed in bzr by humans, rather than being primarily imported, tend NOT to have a .pc/ : cjwatson patches applied doesn't have to imply .pc in vcs; it's unfortunate that the importer took that particular decision cjwatson (I've been using patches-applied-in-bzr since well before the importer did, *without* .pc) I think, as a short term fix, we should modify the collision-is-clean check to ignore the absence of a .pc directory in packager-committed revisions. That sounds reasonable. It does mean that there starts to be some differences in how the branches should be handled, but they exist already depending on whether the importer or a human was last to push. I think there's more to a transition that just ignoring .pc, but it should be considered if that's how humans prefer to deal with the branches. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Importer stopped since Sunday?
On Tue, 10 Apr 2012 01:08:25 +0100, Max Bowsher _...@maxb.eu wrote: It looks like someone stopped the UDD importer on Sunday? James W. has a 'crontab -e' editor open from around that time. Anyone know what's going on, and if it's safe to restart? We're failing rather dismally at providing prompt imports at the moment. Hi, Firstly my apologies for not sending a mail about this at the time. Some time on Saturday night the importer started failing hard with sqlite contention errors. The mass-import process was stuck, so nothing was being imported, and the cronjobs were failing causing two emails to be sent every 5 minutes. Given that nothing was being imported anyway, I stopped the process until I would have more time to investigate after the long weekend. I suspect the changes are somehow related to my storm changes, but I don't know what the relationship is yet. It ran fine for a couple of days, so we should be fine to restart and process the queue. It may well fail again though. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: What to do when a packaging branch is out of date
On Wed, 04 Apr 2012 15:51:21 -0300, Andreas Hasenack andr...@canonical.com
wrote:
Hi, can you take another look? It seems there is a delay again:
$ bzr branch ubuntu:landscape-client precise-already-done
Most recent Ubuntu version: 12.04.3-0ubuntu1
Packaging branch version: 12.04.2-0ubuntu1
Packaging branch status: OUT-OF-DATE
Branched 44 revisions.
There is an error for it in the package importer:
http://package-import.ubuntu.com/status/landscape-client.html#2012-03-30
06:12:01.518169
bzrlib.errors.UnknownErrorFromSmartServer: Server sent an unexpected
error: ('error', 'xmlrpclib.Fault', Fault -1: 'Unexpected Zope
exception: RequestExpired: request expired.')
Hi,
It is now up to date again.
Thanks,
James
--
ubuntu-distributed-devel mailing list
ubuntu-distributed-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: bzr merge-upstream: why delete and add the same unchanged file?
On Thu, 29 Mar 2012 12:21:41 +0200, Jelmer Vernooij jel...@canonical.com wrote: Am 29/03/12 05:14, schrieb James Westby: On Tue, 20 Mar 2012 18:06:52 -0300, Andreas Hasenack andr...@canonical.com wrote: I understand they are isolated and separated branches. I thought supporting a bzr branch for the upstream branch was more of a convenience and that merge-upstream would actually just export it to a temporary tarball and then move on like if I had given it a tarball to work with, but I see now that's not the case. Yeah, there is some old code in bzr-builddeb to do that, but I've forgotten how to activate it now :-) I think I'm missing some context - are you talking about running bzr merge-upstream branch ? That should still work. That will merge in the branch as well as export the tarball right? I think Andreas was asking about a way to just export the tarball and use it in merge-upstream without also merging the branch. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: bzr merge-upstream: why delete and add the same unchanged file?
On Tue, 20 Mar 2012 18:06:52 -0300, Andreas Hasenack andr...@canonical.com wrote: Yes, and I don't have commit or upload rights to ubuntu:landscape-client, so it will always be the first time :) If your sponsor pushes to the branch then it will be there for the next time that you make a change. I understand they are isolated and separated branches. I thought supporting a bzr branch for the upstream branch was more of a convenience and that merge-upstream would actually just export it to a temporary tarball and then move on like if I had given it a tarball to work with, but I see now that's not the case. Yeah, there is some old code in bzr-builddeb to do that, but I've forgotten how to activate it now :-) It also makes it very hard to review the changes this first time, right? The diff isn't helpful. Yeah, the best thing to do I think is to fall back to diff -Nru of two trees so that you diff based on paths rather than file ids. I'm not aware of anyway to get bzr to do this. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: bzr merge-upstream: why delete and add the same unchanged file?
On Tue, 20 Mar 2012 16:20:29 -0300, Andreas Hasenack andr...@canonical.com wrote: Why is it removing and adding the same file? This file (and several others) didn't change between ubuntu:landscape-client and lp:landscape-client, it's exactly the same. I'm assuming that this is the first time you've done any sort of merge between the two? Because they are unrelated branches from bzr's point of view, it has to reconcile the history and file-ids. For the history it joins the two revisions history together, which is fine. The file ids isn't so easy though, as they can't be joined. Therefore it replaces the ubuntu file ids with the upstream ones, which is why you see everything as removed and added. This is annoying, but it allows you to move forward, and only needs to happen once. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
[Bug 938736] Re: For-purchase apps not showing up on Oneiric
I had the caching bug, and opening s-c twice with the fixed version allows me to see the apps again. My understanding is that having to open twice is expected. Thanks, James ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/938736 Title: For-purchase apps not showing up on Oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/938736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924240] Re: datetime interpretation changed
** Changed in: python-wadllib (Ubuntu) Milestone: ubuntu-12.04-beta-1 = None ** Also affects: python-wadllib (Ubuntu Precise) Importance: Critical Status: Triaged ** Changed in: python-wadllib (Ubuntu Precise) Importance: Critical = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924240 Title: datetime interpretation changed To manage notifications about this bug go to: https://bugs.launchpad.net/wadllib/+bug/924240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: UDD breakdown when building orig.tar.gz from upstream VCS
On Wed, 15 Feb 2012 08:21:37 -0500, Barry Warsaw ba...@ubuntu.com wrote: I just want to put this out there for the historical record. I think this is a rare enough use case that UDD doesn't need to address, certainly not any time soon, if ever. OTOH, maybe there's an easy workaround. I was working on an NBS for the fgfs-atlas package (LP: #903225). The solution was straightforward enough: upstream had all the necessary fixes in their CVS repository, but hadn't done a release in a long time. I twiddled the packaging to build an orig.tar.gz from CVS, and the googlez helped find some good general packaging information on how to do this. Unfortunately, UDD is essentially useless here. The problem is that after creating the tarball from CVS, `bzr bd -S` can't be used because dpkg-source will complain too much about deltas between the tarball and the source tree. It'll warn about a lot of stuff, but then fail with some unrepresentable changes to source. I worked around this by unpacking the new orig.tar.gz and `cp -a` the debian/ directory from the precise version of the package (with my changes) over into the unpacked tarball. After a few rounds of tweaking, and using `debuild -S -sa`, I had a debian/ that built locally, so I uploaded it and will let the importer (hopefully) sort out the mess. I still did all my changes to debian/ in a source branch though, because that made it easier to get a diff for the linked Debian bug. Is there's a magical udd switch or config setting that would have helped me keep all the changes in the source branch? It seems like this is somewhat similar to the merge-upstream issue when upstream has a rather large released tarball delta. What's the merge-upstream issue? I think that using merge-upstream is what should be done here, passing it the tarball you created. That will merge in the new code, keep the debian directory and any changes, with conflicts if necessary. Once all that is resolved `bzr bd -S` should just work. Of course there may be a large gulf between theory and reality :-) Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
[Bug 929068] Re: [Precise] bug_task.date_created is returning 'unicode' objects instead of 'datetime' objects
*** This bug is a duplicate of bug 924240 *** https://bugs.launchpad.net/bugs/924240 ** This bug has been marked a duplicate of bug 924240 datetime interpretation changed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/929068 Title: [Precise] bug_task.date_created is returning 'unicode' objects instead of 'datetime' objects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-wadllib/+bug/929068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924240] Re: datetime interpretation changed
** Also affects: python-wadllib (Ubuntu) Importance: Undecided Status: New ** Changed in: python-wadllib (Ubuntu) Status: New = Triaged ** Changed in: python-wadllib (Ubuntu) Importance: Undecided = Critical ** Changed in: python-wadllib (Ubuntu) Milestone: None = ubuntu-12.04-beta-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924240 Title: datetime interpretation changed To manage notifications about this bug go to: https://bugs.launchpad.net/wadllib/+bug/924240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820415] Re: bzr crashed with AttributeError in __init__(): 'NoneType' object has no attribute 'makefile'
It's actually an httplib2 bug I think: http://code.google.com/p/httplib2/issues/detail?id=96 ** Bug watch added: code.google.com/p/httplib2/issues #96 http://code.google.com/p/httplib2/issues/detail?id=96 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/820415 Title: bzr crashed with AttributeError in __init__(): 'NoneType' object has no attribute 'makefile' To manage notifications about this bug go to: https://bugs.launchpad.net/lazr.restfulclient/+bug/820415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 681394] Re: existing dependency on elementree at python level
rick_h did a release with this in it last week. Barry is going to upload to Precise. Thanks, James ** Changed in: wadllib Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/681394 Title: existing dependency on elementree at python level To manage notifications about this bug go to: https://bugs.launchpad.net/wadllib/+bug/681394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 681394] Re: existing dependency on elementree at python level
** Also affects: python-wadllib (Ubuntu Lucid) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/681394 Title: existing dependency on elementree at python level To manage notifications about this bug go to: https://bugs.launchpad.net/wadllib/+bug/681394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 681394] Re: existing dependency on elementree at python level
** Description changed: + Impact: Python code using pkg_resources where the code uses wadllib (or + launchpadlib) will spuriosly fail, causing problems in other packages. + Development fix: cjwatson is fixing as part of his Python 3 port. + Stable fix: drop the requirement from the requires.txt, as it is not doing anything +and only breaking code. elementtree is merged in to Python as of 2.6, and having +then entry won't change what is installed on Ubuntu. + Test case: + 1. Install python-wadllib from lucid. + 2. Check that elementtree is listed in /usr/share/pyshared/wadllib-1.1.4.egg-info/requires.txt + 3. Install python-wadllib from lucid-proposed + 4. Check that elementtree is no-longer listed in /usr/share/pyshared/wadllib-1.1.4.egg-info/requires.txt + Regression potential: very low, as the line was redundant. + Binary package hint: python-wadllib With the python-wadllib in maverick installed, the following code fails: - - Python 2.6.6 (r266:84292, Sep 15 2010, 16:22:56) + Python 2.6.6 (r266:84292, Sep 15 2010, 16:22:56) [GCC 4.4.5] on linux2 Type help, copyright, credits or license for more information. from pkg_resources import require require(wadllib) Traceback (most recent call last): - File stdin, line 1, in module - File /usr/lib/python2.6/dist-packages/pkg_resources.py, line 654, in require - needed = self.resolve(parse_requirements(requirements)) - File /usr/lib/python2.6/dist-packages/pkg_resources.py, line 552, in resolve - raise DistributionNotFound(req) + File stdin, line 1, in module + File /usr/lib/python2.6/dist-packages/pkg_resources.py, line 654, in require + needed = self.resolve(parse_requirements(requirements)) + File /usr/lib/python2.6/dist-packages/pkg_resources.py, line 552, in resolve + raise DistributionNotFound(req) pkg_resources.DistributionNotFound: elementtree - + It is because `/usr/share/pyshared/wadllib-1.1.4.egg-info/requires.txt` contains `elementtree`, but in fact `elementree` is not used when the user is using python = 2.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/681394 Title: existing dependency on elementree at python level To manage notifications about this bug go to: https://bugs.launchpad.net/wadllib/+bug/681394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 803475] Re: Missing dependency on python-simplejson
Checked that the new package works fine. Thanks, James ** Description changed: - The python-lazr.restfulclient package on Lucid is missing a dependency - on python-simplejson. As a result, anything which uses python- - lazr.restfulclient and requires it working at build time via Build- - Depends, will fail, due to the missing dependency. A workaround is to - explicitly Build-Depends on python-simplejson as well, but this is the - incorrect solution. + Impact: The python-lazr.restfulclient package on Lucid is missing a + dependency on python-simplejson. As a result, anything which uses + python-lazr.restfulclient and requires it working at build time via + Build-Depends, will fail, due to the missing dependency. A workaround is + to explicitly Build-Depends on python-simplejson as well, but this is + the incorrect solution. + + Development Fix: Already fixed by adding the dependency + Stable Fix: Add the dependency on python-simplejson + Test Case: + 1. Install python-lazr.restfulclient from lucid-updates + 2. Check that it doesn't depend on python-simplejson + 3. Install python-lazr.restfulclient from lucid-proposed + 4. Check that it does depend on python-simplejson + Regression Potential: low, just adding a dependency ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/803475 Title: Missing dependency on python-simplejson To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lazr.restfulclient/+bug/803475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 918307] [NEW] Declares that it requires the test dependencies, but doesn't depend on them, breaking other python code
Public bug reported: Impact: code that uses lazr.restfulclient (or launchpadlib) and pkg_resources can't work. The python package declares that the test dependencies are required, but they aren't listed in the .deb dependencies, and so aren't installed. They aren't needed for the code so they should be dropped. Development fix: Drop the requires on the test dependencies Stable fix: the same thing Test Case: 1. Install the lazr.restfulclient package from -updates 2. Check that van.testing, wsgi_intercept, lazr.restful and lazr.authentication are listed in the first section of /usr/share/pyshared/lazr.restfulclient-0.9.11.egg-info/requires.txt 3. Install the lazr.restfulclient package from -proposed 4. Check that those lines are now listed in a [tests] section. Regression potential: low, as the packages haven't been installed as dependencies, and some aren't even packaged, so nothing should be relying on them being declared as dependencies. ** Affects: lazr.restfulclient (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/918307 Title: Declares that it requires the test dependencies, but doesn't depend on them, breaking other python code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lazr.restfulclient/+bug/918307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 597041] Re: No way to get from binary package to source package
On Sat, 07 Jan 2012 01:50:43 -, Colin Watson cjwat...@canonical.com wrote: It would probably be simplest to have a way to return all source packages that want to build a given binary, and then I can look through those to see which ones I care about. I think this feels natural enough in the LP API because lookups for source and binary publications also return collections. How about Archive.getPublishedSources(binary_name=...), which you could then limit by series, binary version, etc. as required? Would that work for everyone? The use case that we had for this the other day was just to get the source package name for the given binary publication, as there no information in https://launchpad.net/+apidoc/devel.html#binary_package_publishing_history that can provide it. I don't see a problem with what you want to provide in addition to that, assuming that dsc_binaries is pretty reliable. Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/597041 Title: No way to get from binary package to source package To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/597041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 905413] Re: SRU for vmware-view
Hi, I've just verified this too, I get vmware-view-client:i386 1.3.0-0ubuntu1+oneiric2 showing up in software-center on amd64 after installing the proposed package. Thanks, James ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/905413 Title: SRU for vmware-view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/app-install-data-partner/+bug/905413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Moving udd to django
On Wed, 14 Dec 2011 09:32:28 +0100, Vincent Ladeuil vila+...@canonical.com wrote: True, but I'm not saying your plan is *bad* for udd, quite the contrary. And yes, sharing some service to query launchpad sounds also like a good idea (I think I mention adding pkgme to mass_import and that's one of the points I had in mind). But this can achieved only by either running both pkgme and udd on the same host or add yet another layer to access the db remotely. In both cases, what I'm saying is that udd has already higher priorities. My plan is delete add-import-jobs, and an a POST handler that gets told when there are new packages to scan. add-import-jobs would then move somewhere else (could be the same machine) That's perhaps what you mean by another layer. It's not a priority for udd, but even while drafting this mail there's a conversation going on about another service that would want the same information. We can take what we have from udd and turn it in to an enabler for lots of other useful things. I would be worried about the risks involved with changing production udd in such a large way at once. The steps I outlined here would involve targeted production changes that should be much easier to debug. But if you follow these steps during your rewrite, nothing forbids following them when deploying once we know you've fully debugged them right ? Except that any feedback from earlier steps has to be incorporated after completing later steps, so you may have to undo lots of work. Both projects will benefit from this separation: - pkgme can go ahead without caring for udd needs, as long as the actual code base evolve by separating old features from the new ones with a reasonable effort to make the new ones easier to integrate. I don't think that's true. It's not like we don't care about udd, and if we make changes without regard for it Why would you do that ? pkgme can go ahead without caring for udd needs The easiest way for us to make changes caring for udd is to have prompt feedback about the way it is affecting udd. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Moving udd to django
On Wed, 14 Dec 2011 09:38:53 +0100, Vincent Ladeuil vila+...@canonical.com wrote: it will be less risky to deploy changes gradually, Only if we have tested these changes before deployment which we can't do for now (don't take my word for it, just look at the lp:udd history). Even my recent changes in this regard gave us the ability to *manually* test locally (and there, look at revno 555 history for cases I had to fix on top of our actual test suite). Why not set up a staging instance of udd to test changes before they are deployed to production? and we are better off not forking if we can avoid it. Eventually we can split it into separate services/components. I'm all in favor of splitting, I'm advocating the less risky (and as such the cheapest) way to get there. The way I see it the same code is going to be changing either way, and it can either do so incrementally, or in one big jump. If everything goes well then one big jump is less work, but if things break, and you are saying that they are very likely to, then it's easier to deal with that incrementally, where you have fewer things to reason about. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Moving udd to django
On Thu, 15 Dec 2011 08:09:00 +1300, Robert Collins robe...@robertcollins.net wrote: On Thu, Dec 15, 2011 at 7:08 AM, James Westby jw+deb...@jameswestby.net wrote: My plan is delete add-import-jobs, and an a POST handler that gets told when there are new packages to scan. 'there is work to do now' is a classic pub-sub situation. Rather than a post handler, I suggest you want one of: - a webhook http://wiki.webhooks.org/w/page/13385124/FrontPage The concept of a WebHook is simple. A WebHook is an HTTP callback: an HTTP POST that occurs when something happens; a simple event-notification via HTTP POST. Are you referring to a different webhook? Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Moving udd to django
On Tue, 13 Dec 2011 09:11:36 +0100, Vincent Ladeuil vila+...@canonical.com wrote: 3. It would also allow for starting to move udd to an SOA, or at least make it easier. Not a concern for udd so far. Actually I'd like to turn add_import_jobs in to a separate service, as it could be shared between udd and pkgme, and other services that people want to build, reducing load on Launchpad. That would be much easier if udd was in django (or twisted, or go, or ...) 4. It would be nice to have a query builder, rather than all the hand-written sql. Not a big problem for udd so far. Indeed, but I consider it technical debt, and it makes the code harder to read and change. 1) Install python-django in production - So that it is there when it is needed. This should be cheap. On the other hand, if newer versions are needed (which would be known during the dev/test phase) this will also be useless. Coding to django 1.1 (lucid) is not too restrictive. IS can also run django 1.3 if absolutely required. What do you think? Is this worth doing? Frankly ? This certainly sounds like a very good plan. I also think udd doesn't need any of that in the short term. Now, if you do it for pkgme, we will certainly be interested in cannibalizing part or all of it. In the mean time, the less disruptive changes we do to udd, the more we can focus on the import failures which is where the paint points are. I do think dealing with import failures is good, but I'm not sure the approach you advocate is the right one. What I mean is that forcing the use of the same code base for two projects with different goals sounds like a sure way to trigger failures for the other project without benefits for the project needing the new features. We've already encountered such issues at a small scale and until the test suite become rock-solid, I fail to see while we won't encounter new issues. I.e.: It sounds easier to separate common parts from specific parts in the actual udd code base while starting a *new* project than doing so in the udd code base that is already in production. Once those parts are clearly separated, the package importer can look at integrating the new and well-separated udd. I would be worried about the risks involved with changing production udd in such a large way at once. The steps I outlined here would involve targeted production changes that should be much easier to debug. Both projects will benefit from this separation: - pkgme can go ahead without caring for udd needs, as long as the actual code base evolve by separating old features from the new ones with a reasonable effort to make the new ones easier to integrate. I don't think that's true. It's not like we don't care about udd, and if we make changes without regard for it then it's likely that either lots of changes will be required to support udd again, or udd will never used the new codebase. - udd won't have to integrate incremental steps that bring no added value but still cost deployment/debugging time or do so *only* when a tangible benefit emerge *and* addresses issues. If you believe this then we can go away and ignore udd, but I fear it will be more work and more risk in the end. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Moving udd to django
On Sat, 10 Dec 2011 17:52:40 +1300, Robert Collins robe...@robertcollins.net wrote: On Sat, Dec 10, 2011 at 3:10 PM, James Westby jw+deb...@jameswestby.net wrote: Hi, I think there are a few reasons that we should consider moving udd to django (more on what this actually means later.) I'm curious what data udd stores. There are two sets. There's the bookkeeping data for running import-package each time a package is uploaded to Debian or Ubuntu, keeping track of failures, etc. Then there's the bookkeeping data for import-package itself, about what it thinks the state of bzr is etc. These should be treated differently, with the former the one that is more important for the goals laid out here. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Moving udd to django
On Sun, 11 Dec 2011 06:38:25 +1300, Robert Collins robe...@robertcollins.net wrote: It might be interesting - as a thought experiment if nothing else - to consider failures a form of crash and upload them to a crash database rather than processing them inside udd - e.g. toss them out over amqp. The current design is that it also uses them to avoid acting on that package until there is manual intervention. So it may be interesting to use oopses to communicate the problems and do analysis of them, but it won't avoid storing the data as well unless that model is changed. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
[Bug 893620] [NEW] Doesn't include egg-info dir
Public bug reported: The python package doesn't include the egg-info dir, so it is invisible to setuptools etc. making it harder to work with the package in other projects. Thanks, James ** Affects: subunit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893620 Title: Doesn't include egg-info dir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subunit/+bug/893620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Ubuntu versions
Hi, You can report a bug about this at https://bugs.launchpad.net/ubuntu-webcatalog/+filebug There is some upcoming design work, so this can be considered as part of those changes. Thanks, James On Sun, 06 Nov 2011 18:32:31 -0500, Jonathan Carter (highvoltage) jonat...@ubuntu.com wrote: Howdy! I was just taking a peek on the Ubuntu Apps Directory [1] and noticed that it only lists Ubuntu codenames for the release. Many users, and especially newcomers to Ubuntu often have problems remembering which release maps to which version. Wouldn't it be appropriate to always include the Ubuntu version number when presenting a list of Ubuntu releases to a user? * Ubuntu 10.04 LTS (Lucid Lynx) * Ubuntu 10.10 (Maverick Meerkat) * Ubuntu 11.04 (Natty Narhwal) * Ubuntu 11.10 (Oneiric Ocelot) * Ubuntu 12.04 LTS (Precise Pangolin) I think that having consistent and clear versioning will be beneficial to Ubuntu users. Any thoughts? -Jonathan [1] https://apps.ubuntu.com/cat/department/oneiric/6/ -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: bzr bd -S --package-merge
Hi, I think this is likely to be https://bugs.launchpad.net/ubuntu/+source/bzr-builddeb/+bug/876888 Thanks, James On Thu, 27 Oct 2011 07:39:09 -0400, Barry Warsaw ba...@ubuntu.com wrote: How exactly does --package-merge calculate the version it passes to dpkg-genchanges -v? I'm wondering because it doesn't seem to be doing what I'd expect it to do, and I'm reluctant to use it. Latest case in point: I'm merging boost1.46 from testing into precise, so I do the following: $ bzr branch ubuntu:boost1.46 precise $ cd precise $ bzr merge-package debianlp:boost1.46 Most recent Debian version: MISSING Text conflict in debian/control 1 conflicts encountered. The merge resulted in 1 conflicts. Please resolve these and commit the changes with bzr commit. resolve conflict $ bzr diff debian/changelog === modified file 'debian/changelog' --- debian/changelog 2011-06-03 20:28:58 + +++ debian/changelog 2011-10-27 01:57:00 + @@ -1,3 +1,35 @@ +boost1.46 (1.46.1-7ubuntu1) precise; urgency=low + + * Merge with Debian testing. Remaining Ubuntu changes: +- Detect gcc atomic intrinsics, needed for arm spinlock (LP: #513721) +- Drop libboost-mpi, libboost-mpi-python, and libboost-graph-parallel (and + related -dev packages): we don't want to pull all of the mpi packages + into main. These are provided in a separate boost-mpi-source1.46 + package +- Drop libboost1.46-all-dev and provide from boost-mpi-source1.46 +- Adjust debian/rules and debian/control + + -- Barry Warsaw ba...@ubuntu.com Wed, 26 Oct 2011 21:56:45 -0400 + +boost1.46 (1.46.1-7) unstable; urgency=low + + * control: Fix ungrammatical description for iostreams packages. +Closes: #633865. + + * rules: Dump boostrap log file if bootstrapping fails. + + * libboost-doc.README.Debian: Remove reference to packages bjam and +boost-build; now only need boostX.YZ-dev. Closes: #630529. + + -- Steve M. Robbins s...@debian.org Wed, 17 Aug 2011 23:18:52 -0500 + +boost1.46 (1.46.1-6) unstable; urgency=low + + * control(libboost-mpi-python1.46.1, libboost-python1.46.1): Suggests a +python interpreter. Closes: #620775. + + -- Steve M. Robbins s...@debian.org Sun, 12 Jun 2011 00:37:42 -0500 + boost1.46 (1.46.1-5ubuntu2) oneiric; urgency=low * No change rebuild to drop Python 3.1 support. looks good $ bzr bd -S --package-merge If I now look at boost1.46_1.46.1-7ubuntu1_source.changes I see *all* the version entries from 1.46.1-7ubuntu1 all the way back to 1.21.1-1, the first in the changelog. If I drop the --package-merge option, I get a much trimmer changes file, with just the last changelog entry in it. That's not right either though. I'd expect to see entries for -6, -7 and -7ubuntu1. I've pushed the branch to lp:~barry/ubuntu/precise/boost1.46/debian-merge in case you'd like to take a look at see what's going on. I'll hold off on uploading for a bit in case there's something obvious going on. Cheers, -Barry Attachment: signature.asc (application/pgp-signature) -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
[Bug 876888] Re: bzr bd -S --package-merge on e2fsprogs 1.42~WIP-2011-10-09-1ubuntu1 generates a .changes file recording the birth of the universe
** Description changed: The --package-merge option should detect the last time the package was merged into Ubuntu, and pass an appropriate -v option to dpkg- buildpackage. Instead, when run against lp:ubuntu/e2fsprogs for package version 1.42~WIP-2011-10-09-1ubuntu1, it spits out these errors: parsechangelog/debian: warning: 'since' option specifies non-existing version parsechangelog/debian: warning: use newest entry that is earlier than the one specified parsechangelog/debian: warning: none found, starting from the oldest entry and the resulting .changes includes all the changelog entries back to - 1995. + THE DAWN OF TIME. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: bzr-builddeb 2.7.8 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 17 14:41:31 2011 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) PackageArchitecture: all ProcEnviron: - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: bzr-builddeb UpgradeStatus: Upgraded to oneiric on 2011-09-23 (23 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876888 Title: bzr bd -S --package-merge on e2fsprogs 1.42~WIP-2011-10-09-1ubuntu1 generates a .changes file recording the birth of the universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzr-builddeb/+bug/876888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876888] Re: bzr bd -S --package-merge on e2fsprogs 1.42~WIP-2011-10-09-1ubuntu1 generates a .changes file recording the birth of the universe
Oops:
UBUNTU_RELEASES = ('warty', 'hoary', 'breezy', 'dapper', 'edgy',
'feisty', 'gutsy', 'hardy', 'intrepid', 'jaunty', 'karmic',
'lucid', 'maverick', 'natty', oneiric)
Would be really nice to get rid of that.
Thanks,
James
** Changed in: bzr-builddeb (Ubuntu)
Importance: Medium = High
** Changed in: bzr-builddeb (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876888
Title:
bzr bd -S --package-merge on e2fsprogs 1.42~WIP-2011-10-09-1ubuntu1
generates a .changes file recording the birth of the universe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bzr-builddeb/+bug/876888/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876888] Re: bzr bd -S --package-merge on e2fsprogs 1.42~WIP-2011-10-09-1ubuntu1 generates a .changes file recording the birth of the universe
Making use of distro-info would at least stop having to modify the code here, if we can't avoid needing the information. Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876888 Title: bzr bd -S --package-merge on e2fsprogs 1.42~WIP-2011-10-09-1ubuntu1 generates a .changes file recording the birth of the universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzr-builddeb/+bug/876888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Collision branches
On Thu, 8 Sep 2011 14:51:44 +1000, Martin Pool m...@canonical.com wrote:
I looked into a few of them and they weren't all clearly due to quilt
problems, but perhaps most of them are (or I didn't understand the
cause from a glance.)
In order to get some data on this I just looked back at 45 of these from
the last month, and found:
9 that looked real, or at least feasible
2 that were caused by updates to .po files
4 that were caused by automatically generated debian/control files
1 caused by updates to config.{guess,sub}
29 caused by quilt interaction
So 64% of these were caused by quilt interactions, and all the other
spurious ones were less than 50% of what's left, indicating that quilt
is the place to focus our efforts to make these merge proposals have
much more signal than noise.
Thanks,
James
--
ubuntu-distributed-devel mailing list
ubuntu-distributed-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: [Bug 854245] Re: Multiple packages are titled Bazaar in the Ubuntu Software Center
On Mon, 19 Sep 2011 23:05:06 -, Andrew Starr-Bochicchio a.star...@gmail.com wrote: That's coming from the bzr-handle-patch.desktop file. As none of the desktopfiles in the package really do a good job of describing the package as a whole, it might be best to over-ride it in app-install- data-ubuntu. I would have thought that desktop file would have an option for it to not show up in menus (as it's a handler rather than an application you would run from a menu I think,) and that app-install-data would similarly ignore it. Am I wrong on any of those points? If not, is the file missing such an option? Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/854245 Title: Multiple packages are titled Bazaar in the Ubuntu Software Center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/app-install-data-ubuntu/+bug/854245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 660196] Re: linaro-media-create fails umount: dir/binary/proc: not found
On Tue, 13 Sep 2011 13:43:59 -, Adrien Ferré 660...@bugs.launchpad.net wrote: Still having this bug with: sudo linaro-media-create --rootfs ext3 --mmc /dev/sdb --binary linaro-n -ubuntu-desktop-tar-20110824-1.tar.gz --hwpack hwpack_linaro- igep_20110823-0_armel.tar.gz --dev beagle Bug: cp: cannot stat `/tmp/tmpizVz9G/binary/usr/lib/u-boot/omap3_beagle/u-boot.bin': No such file or directory Traceback (most recent call last): File /usr/bin/linaro-media-create, line 161, in module args.is_live, args.is_lowmem, args.consoles) File /usr/lib/pymodules/python2.7/linaro_image_tools/media_create/boards.py, line 480, in populate_boot proc.wait() File /usr/lib/pymodules/python2.7/linaro_image_tools/cmd_runner.py, line 100, in wait raise SubcommandNonZeroReturnValue(self._my_args, returncode) linaro_image_tools.cmd_runner.SubcommandNonZeroReturnValue: Sub process ['cp', '-v', '/tmp/tmpizVz9G/binary/usr/lib/u-boot/omap3_beagle/u-boot.bin', '/tmp/tmpizVz9G/boot-disc'] returned a non-zero value: 1 Hi, What version of linaro-media-create is this? I think this might have been fixed recently. Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/660196 Title: linaro-media-create fails umount: dir/binary/proc: not found To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-image-tools/+bug/660196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 845696] Re: linaro-fetch-image-ui: Ignores image size
** Changed in: linaro-image-tools Importance: Undecided = Medium ** Changed in: linaro-image-tools Assignee: (unassigned) = James Tunnicliffe (dooferlad) ** Changed in: linaro-image-tools Milestone: None = 2011.08 ** Also affects: linaro-image-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: linaro-image-tools (Ubuntu) Status: New = Triaged ** Changed in: linaro-image-tools (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/845696 Title: linaro-fetch-image-ui: Ignores image size To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-image-tools/+bug/845696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Collision branches
On Thu, 8 Sep 2011 14:51:44 +1000, Martin Pool m...@canonical.com wrote: I looked into a few of them and they weren't all clearly due to quilt problems, but perhaps most of them are (or I didn't understand the cause from a glance.) Unfortunately it's necessary to look at the importer log for the package to see why the importer felt it necessary to file the merge proposal. This is because the diff you are seeing is the result of merging the branch in to the new tip, but the importer decides based on the diff of the two revisions. These frequently differ and mean that looking at the merge diff doesn't tell you why the importer chose to do that (particularly if the merge diff is empty.) Perhaps that's the wrong check, but that's the way it is currently. I think we can handle this without blocking on looms by doing a smarter merge that unapplies and reapplies the patches. There is some work towards this in eg https://bugs.launchpad.net/bugs/608675 which Jelmer is working on - we may need extra work to hook it up into the udd importer. Would it also need to be used by LP when generating the merge diffs? What we should probably do next is look at the merge proposals that were filed and work out whether each one - is a real conflict in a sensible form - is not a real conflict and shouldn't be generated at all (some have zero diff) - could be either avoided or better presented by smarter quilt handling or something else That would be good. Is someone able to look at this analysis? Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Collision branches
Hi, Thanks for fixing the bugs that were preventing merge proposals for getting filed for collisions. This had led to a surge in the number of such merge proposals. This is mainly due to a backlog, but there have been 10 or so in the two days since. You can see the extent of this by searching for ubuntu-branches at http://reports.qa.ubuntu.com/reports/sponsoring/index.html Colin has valiantly reviewed some of them (maybe half, thanks Colin,) and has found that in none of the cases so far were the collisions real in the sense that someone pushed and someone else uploaded something different. There was one case at https://code.launchpad.net/~ubuntu-branches/ubuntu/oneiric/ibus/oneiric-201108121834/+merge/73916 which seems to indicate a bug though. From my previous experience going through these merge proposals the majority of issues will be caused by the representation of quilt in the branch. Can the Bazaar team do something to stop this influx of merge proposals that must be sorted, leaving just real ones? Does this have to involve work on looms? Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Terminating the append_revisions_only experiment, for now
On Tue, 23 Aug 2011 09:41:24 +0200, vila v.ladeuil...@free.fr wrote: This is also very close to my feelings and I like to add that we should *really* write tests to capture them and make sure we don't regress again in the future. Overall, I feel we have far too much failures when landing *good* stuff *because* we lack a proper way to test. It's a long known issue that we miss a launchpad test server but *not* having tests to guard against regressions is clearly a path we don't want to pursue as demonstrated here (IMNSHO). Whether we address that by using staging or any sort of local launchpad test server is open to discussion but the sooner we start this discussion the better. I think there are tests that could be written that would have caught some of these issues that don't require a Launchpad instance to run. There are problems when the append-revisions-only is set on the local branches for instance. Whether the code is structured such that you can test those code paths without a Launchpad instance is a different matter though :-) I'm not saying that we shouldn't work out a way to test against Launchpad, just that there may be useful things that can be done without solving that problem. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
[Blueprint server-o-ensemble-conference-talks] Ensemble Conference Talks
Blueprint changed by James Westby:
Whiteboard changed:
Work Items:
[bcsaller] Cloud Camp - May 26, 2011 in San Francisco, CA, USA {1}: DONE
DevOps Day Australia (Taking talk submissions now) - July 22-23rd in
Melbourne, Australia{2}: POSTPONED
HotCloud (Poster submissions are due by Monday, May 30, 2011, at 3:00 p.m.
PDT) - June 14–15 in Portland, OR, USA{3}: POSTPONED
[bcsaller] DevOps Day Mountain View (Proposal Deadline is 1st of June 2011) -
June 17-18th in Mountain View{4}: TODO
Cloud Camp - June 2, 2011 in Boston (Waltham, MA), USA{5}: POSTPONED
[kirkland] Cloud Camp - June 7, 2011 in New York, USA{6}: DONE
Velocity BoF Session (Call closes 11:59pm 06/09/2011 PDT) - June 14th-16th
in Santa Clara, CA{7}: POSTPONED
Large Installation System Administration Conference - (Call closes June 9,
2011, 11:59 p.m. PDT) - December 4–9, 2011, Boston, MA{8}: POSTPONED
Ops Camp - June 13, 2011 in Portland, OR, USA{10}: POSTPONED
[clint-fewbar] Cloud Camp - June 14, 2011 in San Diego, CA, USA{11}: DONE
Cloud Camp - June 16, 2011 in Seattle, USA{12}: POSTPONED
CloudCamp - June 20, 2011 in Cincinnati, OH, USA{13}: POSTPONED
Cloud Computing Expo (Call closes June 30, 2011) - Nov 7-10 in Santa Clara,
CA {15}: POSTPONED
- [robbie.w] CloudCamp - July 20, 2011 in Austin, TX, USA{18}: POSTPONED
+ [robbiew] CloudCamp - July 20, 2011 in Austin, TX, USA{18}: POSTPONED
[clint-fewbar] OSCON Talk: DONE
[clint-fewbar] OSCON BoF Session (Call closes 11:59pm 07/22/2011 PDT) - July
25-29th in Portland, OR{14}: DONE
LinuxConf AU (Call close Friday 29th July 2011) - January 16-20th Ballarat,
Australia{18}: POSTPONED
Cloud Connect 2012 - (Call closes August 18th, 2011) - February 13-16, 2012,
Silicon Valley, CA{9}: TODO
CloudCamp - September 10, 2011 in Munich, Germany{16}: POSTPONED
CloudCamp - October 9, 2011 in Cloud Track @ Silicon Valley Code Camp,
USA{17}: TODO
Links:
{1} http://www.cloudcamp.org/sf/2011-05-26
{2} http://devopsdownunder.org/
{3} http://www.usenix.org/events/hotcloud11/
{4} http://www.devopsdays.org/events/2011-mountainview/proposals/
{5} http://www.cloudcamp.org/boston/2011-06-02
{6} http://www.cloudcamp.org/ny/2011-06-07
{7} http://velocityconf.com/velocity2011/public/cfp/157
{8} http://www.usenix.org/events/lisa11/
{9} http://www.cloudconnectevent.com/santaclara/call-for-papers/
{10} http://www.opscamp.org/
{11} http://www.cloudcamp.org/sandiego/2011-06-14
{12} http://www.cloudcamp.org/seattle/2011-06-16
{13} http://www.cloudcamp.org/cincinnati/2011-06-20
{14} http://www.oscon.com/oscon2011/public/cfp/164
{15} http://cloudcomputingexpo2011west.sys-con.com/general/papers2011w.htm
{16} http://www.cloudcamp.org/munich/2011-09-10
{17} http://www.cloudcamp.org/siliconvalley/2011-10-09
{18} http://cloudcamp-austin-2011-estw.eventbrite.com/
{19} http://linux.conf.au/programme/papers
--
Ensemble Conference Talks
https://blueprints.launchpad.net/ubuntu/+spec/server-o-ensemble-conference-talks
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-documentation] Improving Ubuntu Server Documentation
Blueprint changed by James Westby: Whiteboard changed: - Work Items: [jwcampbell] look at build toolchain transition needs to produce something similar to docs.openstack.org: TODO Look at what we currently have, what needs to change, and plan how we do it: TODO - [robbie.w] look at getting funding for dedicated document resource: DONE + [robbiew] look at getting funding for dedicated document resource: DONE Jim or Adam to look at an Ubuntu Open Week-type session regarding additional contributions to server docs: TODO Server team to identify server resources that could be used to test out server documentation configurations for the purpose of documenting them.: TODO -- Improving Ubuntu Server Documentation https://blueprints.launchpad.net/ubuntu/+spec/server-o-documentation -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: Patch pilot report - 2011/07/27
On Thu, 28 Jul 2011 00:00:13 +0200, Benjamin Drung bdr...@ubuntu.com wrote: Am Mittwoch, den 27.07.2011, 17:39 -0400 schrieb Stéphane Graber: NOTE: Is the report still updating? I seem to remember it updating every 30 minutes or so, but last update was more than 10 hours ago... It should be updated even 15 or 30 minutes. So no, there seems to be a problem. I pulled the latest sponsoring code and ran it. It works without any crash. No idea, why the sponsoring overview isn't updated any more. The machine it is running on is having problems. It is being worked on I believe, but I don't know an ETA for a solution. I also don't know if there as an RT ticket for tracking it. Consider this an almost content-free message then :-) Thanks, James -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 804397] Re: xdg-open depends on gnome-open, but it's not on the CD
** Also affects: xdg-utils (Ubuntu Oneiric) Importance: High Status: Confirmed ** Changed in: xdg-utils (Ubuntu Oneiric) Milestone: None = ubuntu-11.10-beta-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804397 Title: xdg-open depends on gnome-open, but it's not on the CD To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox/+bug/804397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 813755] [NEW] gnome-keyring-daemon fails to start as it can't get capabilities
Public bug reported: Hi, With a fresh oneiric install gnome-keyring-daemon won't start for me, complaining about not being able to get capabilities. If I set the excecutable to be suid root then it starts fine. Thanks, James ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/813755 Title: gnome-keyring-daemon fails to start as it can't get capabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/813755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596313] Re: [needs-packaging] gm-notify - Highly Ubuntu integrated GMail Notifier
** Branch unlinked: lp:~ubuntu-branches/ubuntu/maverick/gm- notify/maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/596313 Title: [needs-packaging] gm-notify - Highly Ubuntu integrated GMail Notifier To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/596313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Patch pilot report 2011-07-07
On Thu, 07 Jul 2011 17:12:29 +0200, Didier Roche didro...@ubuntu.com wrote: https://code.launchpad.net/~ubuntu-branches/ubuntu/oneiric/opendrim-lmp-powermanagement/oneiric-201107070710/+merge/67122 - the patch and content is in the source package. The thing is, as it was the first patch, the debian/patches directory was created in both branches, and so the ids don't match, hence the conflict. Any idea how to detect (making a traditional diff first?) and not make the autoimporter conflicting? To avoid further conflicts, as I couldn't set the status to rejected but still waiting to get the MR off the list, I set the status to WIP. I didn't simply deleted it as maybe James wants to do some autogenerated branch cleanup. I filed https://bugs.launchpad.net/udd/+bug/806940 Thanks. That's not quite what happened. The issue is that the branch didn't contain the same .pc info as the unpacked source package. This is what caused the collision, and the conflicts are just an artefact of a bug in the way that it handles that. I'll update the bug with more info. Thanks, James -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 804622] Re: Fails to guess package for python-cheetah
distribute seems to have a safe_name function in pkg_resources.py https://bitbucket.org/tarek/distribute/src/edd2f2c24b20/pkg_resources.py#cl-1130 but it doesn't call lower() and is different to debpython's anyway. Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804622 Title: Fails to guess package for python-cheetah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/804622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 804622] [NEW] Fails to guess package for python-cheetah
Public bug reported: Hi, python-cheetah installs Cheetah-*-.egg-info, so I put install_requires=[Cheetah] in setup.py. When dh_python2 tries to guess the package name it uses safe_name before it puts it in the regex, which calls lower() on the string. This means that it doesn't find the Cheetah egg-info dir and so complains that the package can't be found. If it didn't call lower() it wouldn't be found. I don't know what the purpose of the lower call is in a function called safe_name, and it says that it is taken from distribute, so there may be a reason for it there. Thanks, James ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804622 Title: Fails to guess package for python-cheetah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/804622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Wondering how to fix up a category of import failure
On Thu, 23 Jun 2011 10:48:05 +0200, John Arbash Meinel j...@arbash-meinel.com wrote: I personally like C when reasonable. However reasonable means that nobody else has started working on the project (since creating new revisions will break their existing changes). Otherwise, I would go for B. branch-nick doesn't mean all that much. I agree that B is likely the best option here. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: python-oauth
On Thu, 23 Jun 2011 15:32:18 -0400, Barry Warsaw ba...@ubuntu.com wrote: * The package importer is barfing on python-oauth, so there's no Debian source branch available. Try again now. Thanks, James -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: shrinking the desktop DVD image to 1.5GB
On Wed, 08 Jun 2011 15:50:30 -0700, Allison Randal alli...@canonical.com wrote: - What should we cut from the current DVD image (currently a superset of desktop, alternate, and server)? Or, perhaps more simply, what would be worth adding beyond the current 700MB CD image? Does the DVD install extra stuff than the CD if you install a desktop? I think we should be careful of diluting the experience is by providing alternatives to packages on the CD (e.g. providing Thunderbird if evolution is still the default.) I also think that it would be good to have a metapackage to install the extra packages if you install from the CD first, like the kubuntu-full package that Scott mentions. Looking at what I have installed that isn't default, I would suggest * inkscape * gimp * frozen-bubble The other things probably aren't appropriate (wireshark?) Thanks, James -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Blueprint server-o-load-testing] Server Load Testing Suite
Blueprint changed by James Westby: Whiteboard changed: Work Items: [bladernr] Jeff to list the testing team info so interested parties can sign up and participate in making this happen: DONE - [hardware-cert team] Create a list of the tests to be run (a small number of useful tests to start, we can expand afterwards).: TODO - [hardware-cert team] Documentation of test cases and configs and other useful information (wiki?, testcases.qa.ubuntu.com?): TODO - [hardware-cert team] Package a consistently runnable test suite: TODO + [canonical-hw-cert] Create a list of the tests to be run (a small number of useful tests to start, we can expand afterwards).: TODO + [canonical-hw-cert] Documentation of test cases and configs and other useful information (wiki?, testcases.qa.ubuntu.com?): TODO + [canonical-hw-cert] Package a consistently runnable test suite: TODO Previous discussions: https://blueprints.launchpad.net/ubuntu/+spec/packageselection-arm-server-optimized-lamp-stack https://wiki.ubuntu.com/UDSProceedings/N/PackageSelectionAndSystemDefaults#Arm%20Server%20Optimized%20Lamp%20Stack Notes from this session: http://summit.ubuntu.com/uds-o/meeting/server-o-load-testing/ Q: Can you please try to address IPMI (Server management) as well A: To what extent? There is already an IPMI test that performs basic function testing (e.g. connect to the BMC, pull SEL events and system info to ensure that the IPMI bits are working). Definition of Done: 1: Defined list of specific hardware subsystems on servers that are to be tested 2: Defined list of specific common server applications that are to be tested 3: Scope infrastructure changes as may be needed (new hardware, etc) 4: Defined list of tests that will verify server stability and functionality 5: Defined limits on what is acceptable load minimums and maximums for testing 6: Defined list of which tests will be hardware certification tests and which will be QA style tests 7: Responsibilities for each set of tests assigned to the appropriate teams 8: Tests written if they do not currently exist, tested for usability and implemented in Checkbox 9: Separate whitelists defined in checkbox for server certification and server QA 10: New infrastructure in place and operational if necessary 11: Servers tested using full server certification and server QA whitelists 12: 11.10 is thoroughly hammered using our new combined Super Monkey Powers 13: 12.04 is the best Server LTS EVER! -- Server Load Testing Suite https://blueprints.launchpad.net/ubuntu/+spec/server-o-load-testing -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-puppet-integration] Ubuntu Server Puppet Integration
Blueprint changed by James Westby: Whiteboard changed: Work Items for oneiric-alpha-2: [gandelman-a] Nova, single server Common modules: TODO [gandelman-a] Nova, multi-server Common modules: TODO [gandelman-a] Swift, single server Common modules: TODO [gandelman-a] Swift, multi-server Common modules: TODO [gandelman-a] Glance Common modules: TODO Work Items: Package Puppet 2.7: TODO Package Puppet dashboard (on mysql/apache): TODO Package modules: TODO - [negronj] Make/package current orchestra modules to function without orchestra provisioning: TODO + [negronjl] Make/package current orchestra modules to function without orchestra provisioning: TODO [negronjl] apache Puppet Module: DONE [negronjl] puppet-apt helper Puppet Module: DONE [negronjl] debconf helper Puppet Module: DONE [negronjl] distcc Puppet Module: DONE [negronjl] gearman Puppet Module: DONE [negronjl] glusterfs Puppet Module: DONE [negronjl] hadoop Puppet Module: DONE [negronjl] haproxy ( with apache and tomcat integration ) Puppet Module: DONE [negronjl] mongodb Puppet Module: DONE [negronjl] mpi ( mpich2 ) Puppet Module: DONE [negronjl] mysql Puppet Module: DONE [negronjl] tomcat ( tomcat6) Puppet Module: DONE rsyslog Orchestra modules: TODO nagios Orchestra modules: TODO cobbler Orchestra modules: TODO bzr/git Orchestra modules: TODO fs creation/management Orchestra modules: TODO jenkins (master and slave) Orchestra modules: TODO ha cluster (drbd, pacemaker, corosync, cman) Orchestra modules: TODO kvm (host and guest?) Orchestra modules: TODO LXC Orchestra modules: TODO Xen Orchestra modules: TODO [gandelman-a] OpenStack: TODO Mail server Common modules: TODO LAMP stack Common modules: TODO SSH Common modules: TODO samba Common modules: TODO DNS Common modules: TODO PostgreSQL Common modules: TODO Print server ( cups ) Common modules: TODO rsyslog Common modules: TODO Hadoop Common modules: TODO Eucalyptus Common modules: TODO Test modules within vanilla Ubuntu/Puppet infrastructure: TODO Test modules within Ubuntu/Orchestra infrastructure: TODO -- Ubuntu Server Puppet Integration https://blueprints.launchpad.net/ubuntu/+spec/server-o-puppet-integration -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 790760] Re: linaro-hwpack-create fails with GPG errors from APT
On Thu, 02 Jun 2011 13:21:32 -, Guilherme Salgado guilherme.salg...@linaro.org wrote: http://paste.ubuntu.com/616721/ seems to confirm my hypothesis. something that used to work on Maverick no longer works on Oneiric. Now we need to figure out whether it's a regression in python-apt or just a new requirement that trusted.gpg.d is in place before you run cache.update() I don't know if http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596189 is fixed in oneiric yet, it may be related. Thanks, James ** Bug watch added: Debian Bug tracker #596189 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596189 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790760 Title: linaro-hwpack-create fails with GPG errors from APT -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366047] Re: /etc/init.d/bootlogs.sh has gdm in Required-Start
** Branch unlinked: lp:~ubuntu-branches/ubuntu/karmic/sysvinit/karmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/366047 Title: /etc/init.d/bootlogs.sh has gdm in Required-Start -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 283200] Re: NetworkManager starts up twice
** Branch unlinked: lp:~ubuntu-branches/ubuntu/karmic/sysvinit/karmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/283200 Title: NetworkManager starts up twice -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 203323] Re: fsck/usplash: device names not fully reported
** Branch unlinked: lp:~ubuntu-branches/ubuntu/karmic/sysvinit/karmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/203323 Title: fsck/usplash: device names not fully reported -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95368] Re: Cannot remove directory on unmount due to stale .hal-mtab entries
** Branch unlinked: lp:~ubuntu-branches/ubuntu/karmic/sysvinit/karmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/95368 Title: Cannot remove directory on unmount due to stale .hal-mtab entries -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Launchpad-dev] Removing ubuntu-branches and ubuntu-techboard celebrities
On Mon, 30 May 2011 17:28:14 -0400, Francis J. Lacoste francis.laco...@canonical.com wrote: For official package branch, this change would affect James Westby as he's the only member of ubuntu branches that is not part of the technical board. Maybe what's needed is to fix https://bugs.launchpad.net/launchpad/+bug/365098 and allow anyone who can upload the package to set the official link. The question then becomes, do we need to fix that bug before proceeding (in other word, would there be unwanted fall-outs from restricting this to the current distribution owners.) Yes, that bug needs to be fixed before removing the celebrity, or some other way of keeping the importer working needs to be found. The importer currently runs with my credentials in order to be able to do all of the things that it needs to do (handily I am a core-dev and a member of ~ubuntu-branches, which equates to full permission to do everything that it needs to do.) We want to change this anyway, but haven't ever got to doing it. The importer frequently sets official branches (e.g. when a new package is uploaded to Ubuntu,) and so this needs to continue to work, but I don't feel strongly about the exact mechanics. To put it another way the importer needs to have * ability to push to every official branch for Debian and Ubuntu (to keep them up to date) * ability to set the official branches for Debian and Ubuntu (to add them when something new appears, e.g. new package, first security update for a package to a particular release) and it uses all of those permissions regularly, so any temporary removal would disrupt its operation. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: [Bug 789135] [NEW] Add image/hwpack information into image
On Fri, 27 May 2011 13:28:30 -, Marcin Juszkiewicz 789...@bugs.launchpad.net wrote: Public bug reported: Binary package hint: linaro-image-tools Would be nice to have /etc/linaro-image file with informations about which LEB and hwpack were used to create it. I think this is dupe, but I agree that is is desirable. You can kind of get this info now: Something like: Linaro evaluation build image: linaro-natty-alip 20110527 cat /var/lib/ubuntu_dist_channel (or something like that) hwpack: panda-x11-base 20110527 dpkg -l hwpack* Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/789135 Title: Add image/hwpack information into image -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 789135] Re: Add image/hwpack information into image
On Fri, 27 May 2011 15:25:49 -, Marcin Juszkiewicz
789...@bugs.launchpad.net wrote:
root@linaro:/var/lib# cat ubuntu_dist_channel
# This is a distribution channel descriptor
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-linaro-natty-alip-20110527-0
Ah,
/etc/buildstamp is better for that info.
(canonical-oem can be changed next cycle via
config/offspring-builder.config:IBS_DISTRIBUTION_CHANNEL_DESCRIPTOR_PREFIX=offspring-${HOSTNAME})
Thanks,
James
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789135
Title:
Add image/hwpack information into image
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Blueprint server-o-seed-review] Server Seed Review
Blueprint changed by James Westby: Whiteboard changed: - Work Items: - [] Check that the current seed is still relevant: TODO - [] Add additional packages to a seed if suitable: TODO - [] Reconcile ~ubuntu-server subscribed packages to seed(s): TODO + Work + Check that the current seed is still relevant: TODO + Add additional packages to a seed if suitable: TODO + Reconcile ~ubuntu-server subscribed packages to seed(s): TODO == Comments == * Come up with a sensible package list for ubuntu-dev-team so members of the ubuntu server team can upload packages to the archive. -- zul * The ubuntu-server-dev team should mirror the seeds, but this might be somewhat extensive. -- Daviey -- Server Seed Review https://blueprints.launchpad.net/ubuntu/+spec/server-o-seed-review -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-jonas] JOnAS Packaging Certification
Blueprint changed by James Westby: Whiteboard changed: Recap on work on Natty: Current Challenges: * Binary packaging produced for Natty release does not currently pass JEE Certification Tests on OpenJDK (only passes on sun-jdk); this needs to be resolved if we are going to try to get this into the main archive. Packaging Approach: * Key Dependencies: - ow2 EasyBeans - ow2 JOTM - ow2 CAROL - ow2 monolog - ow2 perseus - ow2 cmi - ow2 medor - tomcat7 - Adobe Cairngorm - axis2 - ops4j - Google Guice * Potential Issues: - Maven version 2.1.x (not 2.0.x) in archive - osgi wraps around existing libraries - Flash in admin GUI. - Large amount of dependency packaging JOnAS - 5.3 - JEE 6 profile - 5.3 - JEE 5 profile OSGi 4.2- stan - Apache Felix (or Eclipse) Micro-container architecutre - very low dependency requirement. Services delivered as bundles. Certified against full bundle of componets. Diff between dev and production modes - quick startup. Open source flex compilier - maven plugin. Jonas admn console - separatre component. OSGi enterprise standard. Work Items (oneiric-alpha-2): [james-page] Review current OSGi packaging:TODO - [fbenoit] Identify priority list of ow2 components for packaging during Oneiric: TODO - [fbenoit] Idnetify list of ow2 and other maven plugins required to support JOnAS: TODO + [florent-benoit] Identify priority list of ow2 components for packaging during Oneiric: TODO + [florent-benoit] Idnetify list of ow2 and other maven plugins required to support JOnAS: TODO Work Items: [james-page] work upstream in Debian to help with Maven 3 packaging: TODO [james-page] Work with florent on understanding JOnAS clustering and how this might feed into Ensemble and Orchestra: TODO -- JOnAS Packaging Certification https://blueprints.launchpad.net/ubuntu/+spec/server-o-jonas -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-infra-power] Infrastructure power management
Blueprint changed by James Westby: Whiteboard changed: Work items: [aquette] Implement device discovery tools / libs / binding in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Create Augeas lenses for configuration for NUT: DONE [aquette] Distribute NUT Augeas lenses: TODO [aquette] Distribute the new NUT documentation: TODO [aquette] Create a NUT client only (upsmon) package: TODO [?] Convert initscripts to upstart: TODO - [aquette] Create Avahi publication script for : IN PROGRESS + [aquette] Create Avahi publication script for : INPROGRESS [aquette] Implement a native NUT PSU (power supply unit) driver, using libsmbios: TODO [aquette] Implement a native NUT IPMI driver (remove the need for PowerMan) using OpenIPMI: TODO [aquette] Implement the PowerPath (or PowerChain) notion in NUT, to be able to link for example PSU1 - PDU outlet2 - UPS1: TODO [zulcss] Investigate and implement NUT Puppet integration: TODO [zulcss] Investigate and implement NUT cobbler integration: TODO [zulcss] Investigate and implement NUT Orchestra integration: TODO [zulcss] Investigate and implement NUT Ensemble integration: TODO [kim0] Investigate and implement NUT Ensemble integration: TODO [aquette] Implement improved PDU and power devices support in fence-agents: TODO [?] provide fence-agents package (separated from cman): TODO [andreserl] Investigate PowerNap using NUT as a data broker: INPROGRESS [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [bencer] Implement NUT support in Zentyal: TODO [aquette] Implement NUT support in Zentyal: TODO [?] Implement power support in Cloud schedulers using NUT: TODO [cr3] Implement support for UPS testing in Checkbox using NUT: TODO [aquette] Implement support for UPS testing in Checkbox using NUT: TODO Remaining questions: - is Augeas support sufficient for configuration, or does it need a more advanced wrapper? - related to the above, is a configuration library / tool needed? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? == Items to consider == 1. Create power consumption reports (not ready for billing, only informative) 2. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... -- Infrastructure power management https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-drop-vmbuilder] Drop VMBuilder?
Blueprint changed by James Westby: Whiteboard changed: Work Items: [mvo] move do-release-upgrade build/testing to live-build: TODO [smoser] move oneiric cloud images build to live-build: TODO [jdstrand] vm-tools to live-build: TODO [davewalker] Investigate CCA requirement for vmbuilder: TODO discuss with cody what is appropriate release to target for 11.10: TODO update web/wiki documentation to indicate deprecation of vmbuilder: TODO mailng list or blog request for upstream vmbuilder maintainer: TODO - [nijiba] talk to canonical legal regarding droping CCA: TODO + [nijaba] talk to canonical legal regarding droping CCA: TODO add deprecated warning on vm-builder: TODO Notes: etherpad: http://pad.ubuntu.com/uds-o-server-o-drop-vmbuilder etherpad-history: http://pad.ubuntu.com/ep/pad/view/uds-o-server-o-drop-vmbuilder/latest -- Drop VMBuilder? https://blueprints.launchpad.net/ubuntu/+spec/server-o-drop-vmbuilder -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 766242] Re: lp:ubuntu/cloud-init is not buildable by bzr-builder
Hi Jelmer, Perhaps the applying of quilt patches in bzr-builder can be more graceful in its handling of this state. That is: * patches in debian/patches * Those patches already applied * No .pc directory Thanks, James -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/766242 Title: lp:ubuntu/cloud-init is not buildable by bzr-builder -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 766242] Re: lp:ubuntu/cloud-init is not buildable by bzr-builder
On Mon, 16 May 2011 22:18:37 -, Clint Byrum cl...@fewbar.com wrote: There's not much we can do if the source package patches conflicts directly with upstream. The build log is quite clear which patches won't apply, so they can be selectively removed if some need to stay. Ultimately you have 4 different versions of the code: 1 upstream .orig 2 upstream .orig + packaging patches 3 upstream NEW + packaging patches 4 upstream NEW Picking which one to build could be simpler, thats true. But the problem is that there's some conflicting, duplicated delta between 2 and 3 that must be hand merged because the patches are not applied, so the common version is unknown. I stand by my original assessment, that while its not easy, its necessary to be able to be clear about which patches you want to apply. Is there some confusion here? This case isn't about updating the package to a new upstream release. This is just about rebuilding the current Ubuntu package, so what's in debian/patches should apply, otherwise the packaging is broken. What is causing the issue is that debuild and bzr-builder apply the quilt patches in slightly different ways, with bzr-builder failing if the patches are already applied and there is no .pc directory, and debuild no failing in that case. It's my opinion that when using bzr + dpkg v3 (quilt), the bzr tree should have patches applied and a .pc directory, as that allows you to directly work with quilt when getting the branch. However, given that debuild accepts the current branch as input, bzr-builder probably should too, as it isn't really doing anything different. This is yet another case where the mismatch between quilt patches and bzr bites us, so I'd like for it to go away by natively supporting changes against a base in bzr. Thanks, James -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/766242 Title: lp:ubuntu/cloud-init is not buildable by bzr-builder -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 766242] Re: lp:ubuntu/cloud-init is not buildable by bzr-builder
Hi Jelmer, Perhaps the applying of quilt patches in bzr-builder can be more graceful in its handling of this state. That is: * patches in debian/patches * Those patches already applied * No .pc directory Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/766242 Title: lp:ubuntu/cloud-init is not buildable by bzr-builder -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 766242] Re: lp:ubuntu/cloud-init is not buildable by bzr-builder
On Mon, 16 May 2011 22:18:37 -, Clint Byrum cl...@fewbar.com wrote: There's not much we can do if the source package patches conflicts directly with upstream. The build log is quite clear which patches won't apply, so they can be selectively removed if some need to stay. Ultimately you have 4 different versions of the code: 1 upstream .orig 2 upstream .orig + packaging patches 3 upstream NEW + packaging patches 4 upstream NEW Picking which one to build could be simpler, thats true. But the problem is that there's some conflicting, duplicated delta between 2 and 3 that must be hand merged because the patches are not applied, so the common version is unknown. I stand by my original assessment, that while its not easy, its necessary to be able to be clear about which patches you want to apply. Is there some confusion here? This case isn't about updating the package to a new upstream release. This is just about rebuilding the current Ubuntu package, so what's in debian/patches should apply, otherwise the packaging is broken. What is causing the issue is that debuild and bzr-builder apply the quilt patches in slightly different ways, with bzr-builder failing if the patches are already applied and there is no .pc directory, and debuild no failing in that case. It's my opinion that when using bzr + dpkg v3 (quilt), the bzr tree should have patches applied and a .pc directory, as that allows you to directly work with quilt when getting the branch. However, given that debuild accepts the current branch as input, bzr-builder probably should too, as it isn't really doing anything different. This is yet another case where the mismatch between quilt patches and bzr bites us, so I'd like for it to go away by natively supporting changes against a base in bzr. Thanks, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/766242 Title: lp:ubuntu/cloud-init is not buildable by bzr-builder -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Patch pilot report 2011-05-04
On Wed, 4 May 2011 14:27:18 +0100, Colin Watson cjwat...@ubuntu.com wrote: == Auto-importer changes (bzr history only) == These happen when the source package as uploaded doesn't quite match the branch (often things like differences in an autogenerated debian/control), or when the branch wasn't properly tagged before upload. I generally follow the rule of thumb that I merge just the history (with 'bzr merge BRANCH; bzr revert .') if the extra history has things like extra contributor credit not reflected in the auto-imported branch, and reject it if it doesn't really add anything substantial. In some cases the branch really does have extra commits not reflected in the auto-import branch (this happens if somebody had committed to lp:ubuntu/foo but not uploaded, and somebody else uploaded something else independently), but I didn't see any cases of that today. Hi Colin, Thanks for explaining this. It seems that the reason for these merge proposals was insufficiently clear. In order to help with that I have a change to the importer to add some (hopefully) clear instructions to the description when it creates them in future. I'll commit this when I get off the plane. If anyone sees any issues with the importer (and that includes things like poor documentation or unclear actions that it takes) then please file a bug at https://bugs.launchpad.net/udd. We would appreciate everyone's help in improving the service so that it only creates merge proposals when needed by filing bugs when it creates extra ones. Thanks, James -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: [Oneiric-Foundations-Topic] networked client app updates
On Thu, 21 Apr 2011 18:23:52 +0100, John Rowland Lenton john.len...@canonical.com wrote: * if our projects switch to, say, python 4, then we'd be looking at shipping python 4 to all supported ubuntus, including LTS'es. I can see why you would want to do this for ease of support, but it's common for projects to support several versions to avoid this requirement. In addition, making a change like this would likely have effects far beyond u1, in order to allow u1-on-lts to use a Python version that may not have been available when it was released. * it's easy to imagine scenarios where we'd want to ship updated versions of rhythmbox, banshee or nautilus (and/or any newer application that integrated with our apis). Much more commonly we'd want to update plugins to those apps. Why would you want to upgrade the apps themselves? This seems to be getting away from what I thought was the original question in the discussion, and in to the more general territory of wanting to push new stuff in to released versions, and perhaps it is worthwhile to separate those discussions if possible? the thing we need is to have as much feature parity as is possible across all the platforms we support, This seems to be a core point of contention. Perhaps you could explain why feature parity across versions of Ubuntu is important to your team. As I understood the original question it was how to update client code to keep it in sync with changes that the server makes. It would be possible to do that in order to keep old features working and not enable new features on the old releases. A desire to push new features in to old releases is valid, but seems to be a different question to me, and not one that has a lot to do with the code in question being a networked service client. Thanks, James -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: [Oneiric-Topic] LightDM for display management
On Fri, 08 Apr 2011 19:02:35 +1000, Robert Ancell robert.anc...@canonical.com wrote: Last cycle I proposed using LightDM to replace GDM [1]. It was deferred due to the Unity work, so time to repropose! The main reasons for switching are: - Simpler code to maintain (GDM is a huge ~50,000 line C program and we carry 36 patches. LightDM is nearer 10,000 lines of C). - More flexible greeter development - greeters are as easy as X applications to write, which means we can have an Ubuntu specific greeter that without branching the rest of the code I assume that the greeters can be written to be accessible via screenreaders etc, and that they can be localised etc as well? Thanks, James -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 745801] Re: system-based authorization doesn't store useful credentials in gnome-keyring
Here's the serialize code for what is stored parser.add_section(CREDENTIALS_FILE_VERSION) parser.set(CREDENTIALS_FILE_VERSION, 'consumer_key', self.consumer.key) parser.set(CREDENTIALS_FILE_VERSION, 'consumer_secret', self.consumer.secret) parser.set(CREDENTIALS_FILE_VERSION, 'access_token', self.access_token.key) parser.set(CREDENTIALS_FILE_VERSION, 'access_secret', self.access_token.secret) parser.write(writable_file) so it executes the first line fine, but the rest don't have the desired effect. I'm not sure what would cause the other statements to have no effect. The write() must have an effect, otherwise you would get nothing, so either there is something odd going on with the ConfigParserClass or we are getting the equivalent of short read/write (the writeable_file isn't a real file here, just an in memory one, so it's not that exactly) There is some oddness with a credential_save_failed that could be involved. Adding an upstream task for their input. Thanks, James ** Also affects: launchpadlib Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/745801 Title: system-based authorization doesn't store useful credentials in gnome- keyring -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
