[09:15] Hi ! [09:15] After how much time a package is deleted from a PPA? I keep seeing my package listed despite requesting the deletion almost a month ago... :/ [09:26] Kendos-Kenlen: Can you give us a link? [09:27] Yes, here is the PPA : https://launchpad.net/~baro.app/+archive/ubuntu/ppa [09:27] I forget the exact timings but it shouldn't take more than six hours. [09:27] Kendos-Kenlen: OK, which package and version are you referring to? [09:27] I still can see the old package by going in "View package details" and selecting "Any Status" in the list. [09:27] Kendos-Kenlen: That's expected. [09:28] Packages are deleted, not obliterated from history. [09:28] Oh okay. Then, there is no way to delete it? The reason I want to do so is that these packages were "testing packages" or from my experimentations with debian package system/launchpad itself. [09:29] What problem are they causing being in the history of the archive? [09:30] You can delete the entire PPA (which of course would delete everything else in it), but otherwise they'll stay in its history [09:31] I'd prefer to keep the history clean, especially regarding stuff that have no purpose today. [09:32] And won't benefit anyone [09:32] You could copy the things that remain valuable to a new PPA and delete the current PPA, I suppose. There is no other way [09:32] I would encourage you to not worry too much about clean history though [09:33] Okay ah ah, then I'll follow the second recommendation. [09:33] (In general we have to keep the history there because otherwise it's too easy to accidentally do things that will thoroughly confuse apt clients) [09:35] Also I have another question. Let say I have a package that bundle testing stuff. These testing binaries relies on packages available in an external repository, previously added by another package available in the PPA. Because the binary relies on a library installed by one of these packages, the building task fail (unable to find the corresponding library). [09:36] PPA builds can't refer to anything outside of Launchpad; you'd have to get those external packages into a PPA somehow [09:36] What is the best way to package my binary and still push it in launchpad in this case? For information, the library I need is CUDA (NVidia' lib) and I reference their repository to avoid distributing their stuff by myself. [09:36] Isn't CUDA in Ubuntu? [09:37] CUDA is in Ubuntu, but the latest version is only available in 19.04. However, I am bundling for 18.04 (only). [09:37] Right, but you could backport the newest version [09:37] Or perhaps somebody else has already done so in another PPA [09:39] You can keep the backport in a different PPA that's clearly marked in its description as being just for use in build-dependencies, but there's no way around having it in some Launchpad-published archive [09:40] (See "Edit PPA dependencies" on your PPA for how to make it use other PPAs in its builds) [09:41] Okay, thank you! I checked but could not find any PPA. I'll check how to backport then. I guess it is just copying the binaries from one PPA to another (CUDA is delivered pre-compiled) [09:42] "backportpackage" in the ubuntu-dev-tools package may be helpful. (I haven't checked whether nvidia-cuda-toolkit might have inconvenient build-dependencies that might need to be adjusted.) [09:45] Thank you very much cjwatson, you gave me very good tips! I'll investigate on this and see what I can do to only rely on launchpad! [09:45] Hope it goes well [09:45] Thank, you saved me few hours ;) [10:23] hmm, e.g. https://launchpad.net/~jonathonf/+archive/ubuntu/cuda/+packages [10:32] ricotz: the user in question has already /parted [10:33] cjwatson, I know :( === cpaelzer__ is now known as cpaelzer === lan3y is now known as Laney