=== grumble is now known as blockchain === blockchain is now known as grumble [14:31] How is X-Launchpad-Message-Rationale resolved into a single entry if multiple reasons exist (such as membership of multiple teams)? [14:31] Specifically I want to filter out "X-Launchpad-Message-Rationale: Reviewer @usd-import-team" but don't want it to catch MPs in which I am in some other more selective teams. [14:38] I think in general we try to give the most specific reason [14:38] Which is a slightly vague idea [14:39] The trouble is I'm not sure you know my priority order for my team memberships [14:40] In the case of e.g. subscriber vs. registrant it's clearer [14:41] (Bear with me, refreshing my memory) [14:43] Right, so personal reasons always beat team ones, but otherwise I'm afraid it's currently whichever one LP adds to its recipient set first [14:43] OK, thanks [14:44] https://git.launchpad.net/launchpad/tree/lib/lp/services/mail/notificationrecipientset.py more or less === zbr is now known as zbr|ruck === kyrofa_ is now known as kyrofa [17:01] Hi. I get error when I try to copy package. [17:01] Launchpad encountered an error during the following operation: copying package bitwise. bitwise 0.21-1ubuntu1 in precise (binaries conflicting with the existing ones) [17:02] As far as I remember I'm using the same method I used before. I initially upload my package to Trusty, and then copy to all other serieses [17:02] Copy from Trusty to Precise worked, and all other failed. [17:13] what operation exactly did you undertake? [17:37] sarnold: using the web site I'm trying to copy package. [17:38] https://launchpad.net/~ramon-fried/+archive/ubuntu/bitwise/+copy-packages [17:38] Choosing the package, destination series and "Copy existing binaries" as copy options. [17:40] hrm, dang, I've got nothing, you'll need an expert for that one then, sorry [17:41] It's already in precise for that archive, you can't copy it again [17:41] Oh, not sure about xenial, will have to look when not also making dinner [17:42] You may just need to upload to xenial with a slightly higher version number (e.g. append +ubuntu16.04.1) [17:43] Uploading to trusty first and copying to precise is weird anyway. Normally you either upload to the oldest and then copy forward to everything else once it's built and published, or upload separately to each [18:19] sarnold, cjwatson: it appears that it works only if I copy to a later release, and doesn't work if I copy to a earlier release. [18:19] Thanks for you suggestion [18:21] interesting; I knew that copying to previous releases would probably be a problem for *users* but didn't expect launchpad to dislike it :) [18:39] The problem is usually something related to "new" architectures appearing (i.e. architectures that were in the older release but gone in the newer one) [18:42] ahhh :) thanks