gmane.linux.ubuntu.devel.distributed

Re: DEB_VENDOR & package imports

James Westby — 2012-05-08T01:50:19

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

DEB_VENDOR & package imports

Dmitrijs Ledkovs — 2012-05-03T13:49:19

Hello,

I am having fun times with package lp:debian/accountsservice

$ bzr cat lp:debian/accountsservice/.pc/applied-patches
Most recent Debian version: MISSING
0001-formats-locale-property.patch

0002-create-and-manage-groups-like-on-a-ubuntu-system.patch
0005-gdm_config_file_path_ubuntu.patch
0006-adduser_instead_of_useradd.patch
0007-add-lightdm-support.patch
0008-nopasswdlogin-group.patch
0009-language-tools.patch
0010-set-language.patch
0011-add-background-file-support.patch
0012-add-keyboard-layout-support.patch
0013-add-has-message-support.patch
1001-buildsystem.patch
2001-icon_reset.patch
3001-show_more_than_one_user_powerpc.patch

$ bzr cat lp:debian/accountsservice/debian/patches/series
Most recent Debian version: MISSING
0002-create-and-manage-groups-like-on-a-debian-system.patch

0005-gdm_config_file_path.patch
0006-adduser_instead_of_useradd.patch
0007-add-lightdm-support.patch
1001-buildsystem.patch
2001-icon_reset.patch
3001-show_more_than_one_user_powerpc.patch

It has both ./debian/patches/

Re: Switching over to Quantal

Vincent Ladeuil — 2012-05-02T07:26:30

    > On 01/05/12 14:01, John Arbash Meinel wrote:
    >> Using the config item:
    >> launchpad.packaging_verbosity=False
    >> 
    >> In bzr-2.5 and above, you can actually set that on the command line with:
    >> 
    >> bzr -Olaunchpad.packaging_verbosity=False ...

    > This particular config item wants off rather than False.

    > Also, -O doesn't work (though setting it in bazaar.conf does).

This is already fixed in trunk by using the new config framework (revno
6466 7 Feb 2012 14:46:16).

Could be backported if needed.

     Vincent

Re: Switching over to Quantal

Max Bowsher — 2012-05-01T19:47:29

This particular config item wants off rather than False.

Also, -O doesn't work (though setting it in bazaar.conf does).


Max.

Re: Switching over to Quantal

John Arbash Meinel — 2012-05-01T13:01:42

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 4/30/2012 5:33 PM, Barry Warsaw wrote:

This looks to be bug #888615. It is only triggered because of the
freshness checking. It is trying to walk the ancestry, and is failing
because of a stacking boundary.

I don't have a specific answer on how to fix it, but the short-term
workaround is to just disable the OUT-OF-DATE check.

Using the config item:
  launchpad.packaging_verbosity=False

In bzr-2.5 and above, you can actually set that on the command line with:

bzr -Olaunchpad.packaging_verbosity=False ...

John
=:->


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+f3rYACgkQJdeBCYSNAAPz/QCeOKypFnT/3oexVT0dT7365uUH
jgkAn3kn94DJgEWbOTWusJhxhXeHS/rm
=7frQ
-----END PGP SIGNATURE-----

Re: Switching over to Quantal

Micah Gersten — 2012-04-30T22:08:15

Sorry, I was under the impression that the bzr branch failure was due to
the backports repo trying to stack on a non-existent branch.  My
imagination might have been running astray.

Micah

Re: Switching over to Quantal

Max Bowsher — 2012-04-30T21:45:38

I've filed https://bugs.launchpad.net/bzr/+bug/992245 for this.


Er, backports? Where?

Barry's second command is misleading because he's written
"bzr branch ubuntu:debootstrap precise" when ubuntu:<packagename> now
denotes the quantal branch.

Max.

Re: Switching over to Quantal

Barry Warsaw — 2012-04-30T18:34:36


This could just be an importer bug with debootstrap, since the source branch
is out-of-date.

You're right that ubuntu:codename/srcpkg should never point to the backports
version, but instead to the stable release, so it would reflect SRUs.  OTOH, I
believe ubuntu:codename-{proposed,backports}/srcpkg are also generally
available.

Cheers,
-Barry

Re: Switching over to Quantal

Micah Gersten — 2012-04-30T17:44:18

This looks like an inherent bug.  I don't believe bzr branch
ubuntu:$RELEASE/foo should ever look at backports.  This might adversely
affect someone using this workflow to prepare SRUs.

Thanks,
Micah

Switching over to Quantal

Barry Warsaw — 2012-04-30T15:33:16

Now that Quantal is open for development, what do we need to do to get things
switched over, and UDD all happy-like?

$ bzr branch ubuntu:precise/debootstrap precise
bzr: ERROR: Revision {package-import-GeWIH/nMZzJKr9sWaVLiSSMbcUnWK/KXJQVSFeiJYKfRRQAXIyLz2A< at >public.gmane.orgd7p4} not present in "Graph(StackedParentsProvider(bzrlib.repository._LazyListJoin(([CachingParentsProvider(None)], []))))".
$ bzr branch ubuntu:debootstrap precise
Most recent Ubuntu version: 1.0.40
Packaging branch version: 1.0.38
Packaging branch status: OUT-OF-DATE

-Barry

Re: Importer add-import-jobs cronjob temporarily disabled

James Westby — 2012-04-30T14:20:11

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

Importer add-import-jobs cronjob temporarily disabled

Max Bowsher — 2012-04-28T09:52:44

See https://bugs.launchpad.net/udd/+bug/990394

Re: jubany: Importer stopped

Max Bowsher — 2012-04-26T23:19:37

And now I've updated the series lists and started it up again.

Max.

Re: jubany: Importer stopped

Max Bowsher — 2012-04-26T23:03:43

Someone appears to have restarted it without fixing the problem.

I've stopped it again.

Max.

jubany: Importer stopped

Max Bowsher — 2012-04-26T21:38:23

I've stopped the importer. It needs to be taught about quantal before it can proceed:

Traceback (most recent call last):
  File "/srv/package-import.canonical.com/new/scripts/bin/import-package", line 7, in <module>
    main()
  File "/srv/package-import.canonical.com/new/scripts/udd/scripts/import_package.py", line 1177, in main
    only_before=options.only_before))
  File "/srv/package-import.canonical.com/new/scripts/udd/scripts/import_package.py", line 1045, in _import_package
    versions = get_versions(lp, package, extra_debian=extra_debian)
  File "/srv/package-import.canonical.com/new/scripts/udd/scripts/import_package.py", line 257, in get_versions
    vlist.sort()
  File "/srv/package-import.canonical.com/new/scripts/udd/icommon.py", line 265, in sort
    self.plist.sort(cmp=PackageToImport.import_order_comparator)
  File "/srv/package-import.canonical.com/new/scripts/udd/icommon.py", line 240, in import_order_comparator
    b_release = import_sequence_distro_releases[b.distro].index(b.release)
Va

Re: Stormified importer has introduced unintended change in databeing written to sqlite

James Westby — 2012-04-25T22:00:15

Thanks for going through that to reconstruct the data.


I'm fine with that, but we should aim to push it back in, as it is a
step to moving away from sqlite, which is one of the causes of these
issues.


How do we go about doing that. We have only the production environment
available to give us good feedback on the reliability of the code it
seems.

The revert should have happened sooner, and I would have done it
immediately if the issues hadn't takes more than 24 hours to show up in
the first place.

I am genuinely interested in ideas for handling this better though.


Thanks for ensuring good service.


James

Re: ubuntu-distributed-devel Digest, Vol 29, Issue 10

Mr. Sutthipong Chaisongkram — 2012-04-24T15:50:21

How to start build UBUNTU from source code from this link 
(http://cdimage.ubuntu.com/releases/11.10/release/source/), Help me please.

Importer status: back up to date, running at 8 threads

Max Bowsher — 2012-04-22T19:53:20

The importer has now caught up from the massive backlog caused by
spurious fails of just about everything.

I've reduced the concurrency to 8, to reduce the level of API requests
being directed at Launchpad by the importer's fallback re-processing of
packages that it performs whilst idle.

Max.

Re: Stormified importer has introduced unintended change in databeing written to sqlite

Max Bowsher — 2012-04-22T00:52:16

I've repaired the database, mainly by making lots of use of:

UPDATE foo SET bar = CAST(bar AS text) WHERE typeof(bar) = 'blob';

However, in two tables (revids and should_retry), it wasn't that simple,
since the above technique would give a key uniqueness violation.

For those, I manually consulted the data and merged it appropriately. In
the revids table, this only affected 4 packages (6tunnel aalib acct ace).


Because of the above woes and because of the deadlocking issue, and some
discussion with Jelmer on #bzr, I've reverted Storm out of lp:udd.

I guess we can put it back in, in time, but this time let's be really
really sure we don't create operational issues.

With the above accomplished, the importer is now happily alive, and
chugging through the extreme backlog from the previous malfunction at a
concurrency level of 12 threads.

Max.

Re: Stormified importer has introduced unintended change in databeing written to sqlite

Max Bowsher — 2012-04-21T22:58:53

This turns out to be fairly bad, since it has allowed what were supposed
to be primary keys to be duplicated (once as a blob, once as text). I'm
working on manually understanding the consequences and repairing the DB
consistency.

Max.

Stormified importer has introduced unintended change in data beingwritten to sqlite

Max Bowsher — 2012-04-21T17:44:35

The stormification has introduced an unintended change in how the data
for testaments and revision ids are stored in the sqlite DBs.

They are now being stored as binary blobs rather than strings.

The importer is currently stopped whilst I investigate further.

Max.