DEB_VENDOR & package imports

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

Switching over to Quantal

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@...d7p4}
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

Importer add-import-jobs cronjob temporarily disabled

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

jubany: Importer stopped

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)
ValueError: list.index(x): x not in list

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

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

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.

Stormified importer has introduced unintended change in data being written to sqlite

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.

How to start build UBUNTU

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

---------------------------------------------------------------------------------------------------------
On 20/04/2555 19:00, ubuntu-distributed-devel-request@... 
wrote:
> Send ubuntu-distributed-devel mailing list submissions to
> 	ubuntu-distributed-devel@...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
> or, via email, send a message with subject or body 'help' to
> 	ubuntu-distributed-devel-request@...
>
> You can reach the person managing the list at
> 	ubuntu-distributed-devel-owner@...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ubuntu-distributed-devel digest..."
>
>
> Today's Topics:
>
>     1. How to ?? (=?windows-874?B?yti3uNS+p8nsIKrRwsqnpMPSwQ==?=)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 20 Apr 2012 05:25:35 +0000

Importer broken again

I just checked up on the importer status, and found it both locked up on
DB access again, and apparently it had been running with an improper
environment setup causing it to fail to import bzr-builddeb, so it had
put ~22k packages into failure state.

I've restarted it, properly, and requeued the failures, but that means
there is now a HUGE queue.

Ideally we'd increase the concurrency to churn through the queue
quickly... but we can't because of the db bug.

I REALLY think we should be reverting the introduction of storm.

Frankly, it's not fair that another effort wanting to re-use the UDD
code should impact the operational reliability of the UDD importer to
the degree the storm introduction already has.

By all means let's land infrastructural improvements - so long as they
are reasonably safe. Now that this one has been demonstrated not so,
let's push it out of trunk until it can be made safe.

Max.

How to ??

jubany package importer stopped?

Hi folks,

Our monitoring system is currently showing an alert for jubany's package
importer process, saying that no python processes were found. Restarting
mass-import doesn't seem to resolve the alert. Additionally
/srv/package-import.canonical.com/new/logs/debug_log has lots of
messages about the database being locked.

Is this the current expected state? If not, what action should I take,
if any?

Thanks,
Stephane (Canonical IS)