/srv/irclogs.ubuntu.com/2020/04/16/#launchpad.txt

kyrofaFor my peace of mind, can someone please confirm that if a private PPA password leaks, all that leaks is _read_ access to that _specific_ PPA?00:19
wgrantkyrofa: That's correct. PPA access tokens are read-only and tied to a specific PPA and user.00:22
kyrofawgrant, thank you sir00:22
kyrofaAnother unrelated question: is there a way to get the signing key for a PPA before it has packages?00:29
wgrantkyrofa: To save resources and not pollute keyservers, LP only generates the key for a PPA once packages exist in it. But do note that this only applies to the first PPA for a given person or team; subsequent PPAs with the same owner should reuse the existing key on creation.00:40
kyrofaOh that's interesting, I never noticed that00:49
=== lifeless_ is now known as liffeless
=== liffeless is now known as lifeless
=== cjwatson changed the topic of #launchpad to: Switching database master, brief outage imminent | Help contact: tomwardill (08:00 - 17:00Z) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad
cjwatson(or rather, in read-only mode)09:18
=== cjwatson changed the topic of #launchpad to: Help contact: tomwardill (08:00 - 17:00Z) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad
cjwatsonMaster switch finished a while ago, sorry for forgetting to update here09:34
cjwatsonWrites are now going to pure SSD so hopefully that'll help performance09:35
rbasakCould someone explain what's happening in https://api.launchpad.net/devel/debian/+archive/primary/+sourcepub/1934411 please? This object has no date_published entry. What does it mean for a publication history entry to have been created but never published?13:45
cjwatsonrbasak: An old bug.  Prior to https://git.launchpad.net/launchpad/commit/?id=93b487ee1332840f036603b1567183963d6a9fab, the Debian importer created source package publishing history entries as Pending and never set them to Published (unless the publisher was run on them, which never happened in this case).13:50
cjwatsonrbasak: But it could probably happen in other cases if the SPPH was quickly superseded by a newer version before being published.13:52
rbasakcjwatson: thanks.13:52
rbasakcjwatson: in other cases> in Ubuntu only presumably, or Debian too?13:53
rbasakBecause I assume you only create Debian publishing history entries when you see Debian publications?13:53
cjwatsonIn Ubuntu.  (I think.)13:53
cjwatsonRight.13:53
rbasakGot it. Thanks!13:53
cjwatsonSince the change above, Debian publications are immediately created as Published.13:53
wgrantI don't think something can be immediately superseded, but it can be immediately deleted13:54
wgrant(pretty sure the dominator only considers status == published)13:54
cjwatsonHm yes13:55
cjwatsonSo still possible but rarer13:55
rbasakIs there a guarantee that every source_package_publishing_history has a package_upload?13:56
cjwatsonThat seems unlikely; a Debian-imported one doesn't13:58
rbasakOh13:58
* rbasak wonders where git-ubuntu gets the source from then13:58
cjwatsonPackageUpload would seem a slightly odd thing to go through to get the source13:59
rbasakAh. It defers that to ubuntutools.archive14:00
cjwatsonYou could do sourceFileUrls on the SPPH14:00
cjwatsonOr yeah, look them up from the archive by source name and version14:00
rbasakSorry, I forgot the details of the model here.14:01
cjwatsonpackage_upload corresponds to something that has been in a queue at some point (/ubuntu/focal/+queue etc.)14:01
rbasakMy question is really: if I include spphs with no date_published entries, then will I have a problem importing them?14:01
rbasakOr will something importable always exist?14:02
rbasak(importable == I can grab a source tree, dsc file, etc)14:02
cjwatsonThey should still have files on the sourcepackagerelease even before being published14:02
rbasakSounds good, thanks14:02
cjwatsondate_published is more about being put on disk by the publisher14:02
rbasakI'll rely on the date_created of spphs then14:03
rbasakAnd mostly (completely?) ignore date_published14:03
cjwatsondate_published is interesting if you want to line things up with when the publisher ran, but I can't think of why it would be interesting to git-ubuntu14:04
rbasakAnd I'll use the earliest spph (keyed by date_created) for a (source_package_name, source_package_version) pair to keep consistency in ordering14:04
rbasakcjwatson: yeah - sounds like I took a wrong turn in using date_published instead of date_created14:05
cjwatsonI'm not sure I can authoritatively guarantee that every SPPH will have some associated files - it's possible there are anomalies - but I don't expect that to have anything to do with whether date_published is set14:06
cjwatsonAnd I don't know of a situation today where that would happen14:07
rbasakFair enough. If we find anomalies, the import will probably fail until I add code to detect the anomaly and treat the spph as if it doesn't exist. I think that's OK.14:07
wgrantIt is uncommon, but e.g. maitreya14:08
wgrantPossibly only maitreya14:08
wgrantI think we treated that like an early source expiry, rather than excising it from the DB entirely.14:08
cjwatsonNot importing that is in fact desired14:08
wgrantIndeed.14:08
cjwatsonOh maybe also really old obsolete things?14:09
cjwatsonI don't remember whether we've ever expired source files14:09
cjwatsonI didn't think so14:09
cjwatson(aside from maitreya)14:09
rbasakMore detail on maitreya please?14:09
cjwatsonLegal14:09
rbasakSounds like a good edge case to make sure git-ubuntu works with.14:09
rbasakWe can also put it in an import blacklist14:09
cjwatson(also, astrologers)14:10
rbasakBut I'd like to make sure git-ubuntu does work against things Launchpad has.14:10
cjwatsonThe gory details are best discussed over beer :)14:10
wgrantI don't think we've expired sources from the Ubuntu primary archive14:10
wgrantFor obsolescence reasons, I mean14:10
rbasakVirtual beer? :)14:10
cjwatsonhttps://wiki.canonical.com/InformationInfrastructure/OSA/RequestLogging/LP/SQL has some history, ish14:11
rbasakThanks!14:18
Odd_BlokeWe just saw a build failure in Launchpad that we didn't reproduce in either of the local builds we did (one using sbuild, one just building in their host).  Is there any (not entirely painful :p) way to build packages the way that Launchpad does?  (Or at least more closely?)14:47
Odd_Bloke(I know this is Complicated, but figured I'd double check that I'm not missing something I could be using.)14:48
tomwardillOdd_Bloke: is it a consistent failure?14:58
Odd_BlokeYeah, it's just a difference in environment.15:10
Odd_BlokeWhich I would like to be able to catch locally/in the build we do in our CI/..., if possible.15:10
cjwatsonOdd_Bloke: Tom wrote https://dev.launchpad.net/Soyuz/HowToDevelopWithBuildd a little while back, but it uses the LXD VM stuff and is generally a tad new16:23
cjwatsonAnd also doesn't do the restricted network stuff I think16:23
tomwardillsorry, dropped this conversation and got distracted16:23
tomwardillno, it doesn't do the restricted network (it could, but that's a bunch of ufw stuff that I'm not sure I can repeat atm)16:23
Odd_BlokeOK, cool, I'll give that a go at some point.  Thanks!17:03

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!