desktop-packages team mailing list archive

[Bruno Nova <1165104@xxxxxxxxxxxxxxxxxx>]

I've updated the oneconf, oneconf-common, python-oneconf and
python3-oneconf packages to the version in -proposed both in my Trusty
machine and in a Vivid virtual machine.

Then, in each one, I opened the Software Center and clicked "File > Sync
Between Computers", logging in to Ubuntu One if necessary.

After that, I could see my Trusty machine in Vivid's Software Center,
plus another one (probably a previous installation).

In Trusty, however, the list of computers wasn't being displayed, for some reason. I had to remove the Ubuntu One credential from the Gnome Keyring and then re-login in the Software Center for it to work (some temporary problem in USC?).
The package sync was working though, as I tested by listing the contents of "~/.cache/oneconf/*/", and using "oneconf-query".

So, the update fixes the problem in oneconf, for both Trusty and Vivid.

** Tags removed: verification-needed
** Tags added: verification-done verification-done-trusty verification-done-vivid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to oneconf in Ubuntu.
https://bugs.launchpad.net/bugs/1165104

Title:
  oneconf is only showing the pc you are on in raring and isn't sharing
  to other machines

Status in One Hundred Papercuts:
  Fix Released
Status in oneconf package in Ubuntu:
  Fix Released
Status in oneconf source package in Trusty:
  Fix Committed
Status in oneconf source package in Vivid:
  Fix Committed

Bug description:
  [Impact]

  The package synchronization in the Ubuntu Software Center doesn't
  work, and only the current machine is displayed.

  [Test Case]

  At least two computers (or virtual machines) are needed.

  First, enable software sync in both computers, by opening the Ubuntu
  Software Center, then clicking "File > Sync Between Computers" in the
  menu in each computer. Enter your Ubuntu One credentials if asked.

  Then either use both computers normally for some time (one or two days?) so the package sync occurs naturally, or force the sync to happen in both of them (faster) by running:
  $ oneconf-query --stop
  $ oneconf-service --debug
  (The --debug flag is not necessary, but useful for debugging)
  Do this for both computers, one at a time.

  Then open the Software Center and click on the Installed Software tab, or "File > Sync Between Computers".
  If all computer are listed, and if clicking on one of them (except the current one) bring up a package comparison, the bug is fixed.
  If not, you may try to force a sync on both computers one last time and check again, just to be sure.

  [Regression Potential]

  Oneconf wasn't working as intended, so there's probably no regression
  potential. But it suppose it could impact the stability of Oneconf or
  the Software Center.

  [Original Report]

  In Raring I see only the machince I'm on.  In the precise box beside
  it I see a couple of boxes but not this one.  Please see the
  screenshots attached.

  I have a feeling that some how the sync has broken but I'm not sure
  what technology it is use on the backend.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: oneconf 0.3.3
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Fri Apr  5 18:18:24 2013
  InstallationDate: Installed on 2013-04-02 (3 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: oneconf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1165104/+subscriptions