[03:31] <pieq> Morning!
[03:31] <pieq> Is there a feature in Launchpad to prevent people from pushing things directly into a project Git repository and instead having to use Merge Proposals?
[03:31] <pieq> (I know this exists on Gitlab and Github, but I'm wondering about Launchpad)
[03:59] <wgrant> pieq: Most projects do that today by having their main repository owned by their merge bot user. But we're currently working on a feature that will let branches in an existing team repository be locked down to particular users.
[03:59] <pieq> wgrant, thanks, that's very good news!
[04:00] <karstensrage> how do you change the changed-by email for the package
[04:00] <karstensrage> is not using the right email
[04:01] <pieq> wgrant, I ask because last week, I was demoing Git to my team, explained them how to setup their own repo (by the way, is there a "Fork this repo" feature in Launchpad?) and push changes (`git push myrepo`), but someone typed `git push` by mistake and it pushed his modifications over to the central repo directly...
[04:01] <pieq> we did a git revert and pushed that to fix the issue, but it got me thinking :)
[04:02] <wgrant> karstensrage: That's the email address in the most recent entry in debian/changelog
[04:03] <wgrant> pieq: There's no fork button, since you can just push and the repo will be automatically created.
[04:03] <wgrant> pieq: In that situation we'd currently recommend that the merge robot own the repository.
[04:03] <karstensrage> wgrant, i changed it when i updated the changelog
[04:03] <wgrant> karstensrage: Where are you seeing the old address?
[04:03] <pieq> wgrant, but how to define the personal repo?
[04:03] <karstensrage> in the .changes file
[04:04] <wgrant> pieq: git remote add lp git.launchpad.net:~USER/PROJECT
[04:04] <wgrant> git push lp master
[04:04] <pieq> wgrant, ok thanks
[04:04] <wgrant> The repository will be automatically created on the server if it doesn't already exist, sharing data with lp:PROJECT so the first push should be very quick.
[04:04] <pieq> (I never remember the simple ~user/project and always end up copy-pasting and adjusting the URL from the main repo)
[04:05] <wgrant> karstensrage: That's from debian/changelog unless you're doing something unusual.
[04:06] <karstensrage> well if i do dch -i it adds a new entry with the bad email
[04:06] <karstensrage> but the changelog has the right email in it if i cat it
[04:07] <wgrant> You can override dch's default email address with the DEBEMAIL environment variable.
[04:07] <wgrant> But are you sure you rebuilt the .changes after you fixed the address in debian/changelog?
[04:08] <karstensrage> pretty sure, i did dpkg-buildpackage after dch
[04:08] <wgrant> Rerun it and confirm the mtime
[04:14] <karstensrage> hmmm
[04:19] <karstensrage> i did rebuild and it seemed to be ok, did dupload -f and it says source/binary (i.e. mixed) uploads are not allowed
[04:20] <wgrant> karstensrage: You always need to build with -S
[04:20] <wgrant> To create a source-only upload; Launchpad doesn't accept binary uploads.
[04:22] <karstensrage> -S on what dpkg-buildpackage?
[04:22] <wgrant> karstensrage: Yes
[05:35] <karstensrage> thank you wgrant
[13:20] <wsnipex> hey, since 2 days my uploads to 2 different PPAs never get built. I don't get a mail notification, nor do I see them in the web interface. Is there a general problem?
[14:26] <karstensrage> maybe  the mail is wrong?
[14:26] <karstensrage> i get email notifications of rejected and accepted
[14:28] <karstensrage> if your version is 1.0-ppa2~trusty
[14:28] <karstensrage> what is the ppa, the 2 and the trusty, parsed as?
[15:15] <wsnipex> karstensrage, my upload have been working for years. ppas are: https://launchpad.net/~team-xbmc/+archive/ubuntu/xbmc-nightly and https://launchpad.net/~team-xbmc/+archive/ubuntu/unstable
[15:17] <teward> is Launchpad having issues?  Getting timeouts visiting source pacakge pages :|
[15:20] <wsnipex> well, my uploads are just being ignored
[15:34] <acheronuk> are they being signed, and with the right key?
[15:34] <wgrant> teward: You need to include the OOPS ID when reporting a timeout.
[15:35] <teward> wgrant: it resolved itself
[15:35] <teward> my guess is "random blip" as the cause
[15:35] <teward> (next time it shows, I'll giv eyou an OOPSID, but it resolved itself on the next attempt to load so)
[15:35] <teward> (sorry for not followign up with "Nevermind")
[15:37] <wgrant> wsnipex: There's a weird crash that's only affecting your packages, so I think there's something changed in your build process
[15:37] <wgrant> TagFileParseError: None: E:Unable to parse package file  (1)
[15:37] <wgrant> Let's see what makes python-apt say that...
[15:39] <wgrant> wsnipex: It's definitely some kind of error in parsing the .changes file
[15:39] <wgrant> Is there anything weird in its formatting?
[15:52] <wgrant> wsnipex: Ah, the changelog entry is more than 39 thousand lines.
[16:13] <acheronuk> wow!
[22:27] <wxl> trying to use the email interface but i'm getting an error about not signing with a key registered, but i certainly have this one registered and a signature is indeed attached
[22:39] <wxl> nevermind