| === viv`d is now known as vivid | ||
| alkisg | Hi, I have two source packages with the same name "ltsp", its old (5) and its new (19) version. They produce completely different binaries with no overlaps or conflicts; old and new binaries can coexist in a system. | 06:08 |
|---|---|---|
| alkisg | But the sources cannot coexist in a PPA because of the same name, so I'd need different PPAs to host them, correct? | 06:08 |
| mitya57 | alkisg: Yes, you need either different PPAs or just the different source names. | 07:19 |
| alkisg | Thank you very much mitya57 | 07:19 |
| alkisg | So I think I can use a single PPA like this: (1) delete old packages so that their binaries won't conflict with "2", (2) upload a renamed version of the old source that will produce old-named binaries, and (3) upload the new source | 07:21 |
| mitya57 | That should work, yes | 07:26 |
| alkisg | Great | 07:28 |
| === mIk3_09 is now known as mIk3_08 | ||
| wgrant | alkisg: Why do you have two sources with the same name that need to coexist? You almost certainly want to rename one of them. | 08:35 |
| alkisg | wgrant: it's ok I'm also the debian co-maintainer of ltsp, and I've talked with the more experienced other co-maintainer too, | 08:36 |
| alkisg | The new ltsp is a complete rewrite, and we want to make it easier for our users to have both of them in parallel in case one fits them better for a migration period, | 08:36 |
| alkisg | so we'll offer the new ltsp in backports/ppas, and in 20.04 or so we'll remove the old ltsp from the archives completely | 08:36 |
| wgrant | Ah. So you wouldn't actually want them to coexist on one system. A separate legacy PPA probably makes sense | 08:37 |
| alkisg | For the migration period, I would encourage old users to have both of them coinstalled | 08:37 |
| alkisg | But that's an unofficial migration period; backports and ppas, not formal archives | 08:38 |
| alkisg | The new package will land in testing in Autumn, so that it'll be included in 20.04 and in bullseye | 08:38 |
| lennyb | Hi, what is a procedure to import pkg to Ubuntu bionic. This pkg exists in debian (https://packages.debian.org/search?searchon=sourcenames&keywords=networking-mlnx ) | 08:38 |
| wgrant | lennyb: That sounds like an Ubuntu question, so you probably want #ubuntu-devel | 08:40 |
| lennyb | wgrant. thanks. | 08:41 |
| pipedream | lennyb: https://packages.ubuntu.com/search?keywords=networking-mlnx&searchon=names&suite=all§ion=all | 11:59 |
| lennyb | pipedream: thanks. looks like there were some debian/ubuntu version issues that I am trying to figure out and solve | 12:27 |
| === cpaelzer__ is now known as cpaelzer | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!