[09:22] Hi, I'm upstream and Debian maintainer for the "ltsp" package. A rewritten version of it has just landed in Debian testing, and it'd be best if focal got it too. [09:22] Question, will this be done automatically or do I need to do some action? https://launchpad.net/ubuntu/+source/ltsp lists it in "proposed". [09:35] alkisg: hi! Thank you for looking out for your package in Ubuntu! [09:35] The reason something gets "stuck on proposed" is much the same as migration to testing in Debian [09:35] https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ltsp has the details [09:36] Is there some kind of rearrangement in the binary packages produced? [09:36] Thanks, reading.. :) [09:37] Yes, many binary packages were removed [09:37] There's only one "ltsp" binary package now [09:37] And it's "arch: all", interpreted [09:38] I'm somewhat puzzled why this hasn't happened automatically. [09:38] The migration to debian testing only happened yesterday [09:39] Maybe it just needs some time? [09:39] No Ubuntu doesn't have a mandatory delay like testing [09:40] And the excuses file is clear that it's blocked [09:40] I think deletion of the binaries in the release pocket would work, but I'm not sure that's definitely the right thing to do. [09:40] We need to ask an archive admin (equivalent of an ftpmaster) to take a look. [09:40] Unless there's something I'm missing here [09:40] We did have to ping ftp master for the debian migration to testing [09:41] Maybe something similar is needed here [09:41] What happens if a user has the old binary packages installed? [09:41] I don't see an upgrade path? [09:42] It should remain installed, and it should be possible to get autoremoved with apt [09:42] It was possible to have the old and the new ltsp coexist for some time, that's why this was preferred [09:42] Also the other debian developer said that way it would avoid the New queue for debian ;) [09:43] (vagrantc is DD, I'm just DM, so I defer to him for such issues :)) [09:43] Could you file a bug against ltsp in Ubuntu please, and subscribe ~ubuntu-archive to it? [09:43] Sure, thank you [09:43] I don't want to go into the technical detail myself because I'm not confident I understand the nuances here and I don't want to take you down a path that's wrong. [09:44] And I don't have the authority to resolve it in the archive anyway. [09:48] Hopefully I got the correct list subscribed: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1855422 [09:48] Launchpad bug 1855422 in ltsp (Ubuntu) "New ltsp package stuck in focal proposed" [Undecided,New] [09:52] akelling: thanks! Yes, that subscription is correct. [09:52] Ty. alkisg :) [09:52] The archive admins tend to process things in batches though so the bug may not get attention quickly. [09:52] Ah, sorry! [09:53] There's no hurry, just making sure it requires no other action from my part [09:53] You were right to ask in here. [09:53] And feel free to ask again if it doesn't get attention in a while. [09:53] Great, thank you [09:53] I don't see any European archive admins in here right now [09:54] Ah, seb128 maybe? ^ [10:03] rbasak, hey, sorry had to change wifi, I'm around now ... what's up? [10:03] seb128: are you an active archive admin? [10:03] yes [10:04] alkisg has an issue with ltsp migrating. I think it needs some binary deletions but am not sure. On my advice he just filed bug 1855422 but then I saw you were online :) [10:04] bug 1855422 in ltsp (Ubuntu) "New ltsp package stuck in focal proposed" [Undecided,New] https://launchpad.net/bugs/1855422 [10:05] looking [10:06] Ty, I'm here if feedback's needed [10:20] alkisg, rbasak, seems like the old binaries have no rdepends and just need to be deleted [10:21] Nice [10:27] coreycb: those two pushes of yours should work now [10:28] teward: wasn't around then. what do you need? [11:15] seb128: thank you! [11:21] rbasak, np! [11:52] rbasak, did you see my message yesterday about the sphinxsearch issue? ruby-riddle regression is the only thing avoiding ruby-defaults migration atm [12:20] kanashiro: yes. That research looks good. Did you have a question for me? [12:31] rbasak, there was no question, I thought I was handing it over to someone else :p but that's fine, I can try to find the fix by myself [12:32] if I have any question I'll ping you [12:34] kanashiro: oh, sorry for the confusion! [12:36] np :) === ricab is now known as ricab|bbl [13:05] cjwatson: thanks [13:08] cpaelzer: how does one build manual test-retrigger urls again? I'm trying to do it for one package specifically before going the all-proposed=1 route (learning experience) [13:08] https://autopkgtest.ubuntu.com/request.cgi?release=focal&arch=amd64&package=samba&trigger=ldb%2F2.0.7-4 <-- failed with [13:08] You submitted an invalid request: ldb/2.0.7-4 is not published in focal [13:08] which is correct, as ldb 2.0.7-4 is in focal-proposed [13:09] I want to run the samba test under https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ldb [13:09] but with the samba package from focal-proposed [13:09] test is green as is [13:11] or, to use a real case that is read [13:11] samba under https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#talloc [13:11] I need it to run with samba from focal-proposed [13:11] and didn't want to pass all-proposed=1 [13:12] * ahasenack reads https://wiki.ubuntu.com/ProposedMigration in the mean time [13:14] * ahasenack adds samba itself as a trigger [13:15] * ahasenack feels smart [13:15] * ahasenack waits for the outcome [13:19] Unpacking samba-libs:amd64 (2:4.11.1+dfsg-3ubuntu1) ... [13:20] yay, seems to have picked up the correct version [13:20] nice [13:32] ddstreet, hey, please commit your network-manager changes to the packaging vcs [15:03] alkisg, rbasak, the ltsp update is in focal now [15:15] Thank you! [15:19] Great seb128, thank you, thanks to rbasak too === ricab|bbl is now known as ricab [15:19] yw! [16:14] rbasak: Thanks! [16:18] yw! [17:50] seb128 done, sorry [17:50] ddstreet, np, thanks! [17:52] vorlon will i386 autopkgtests on focal get properly tweaked somehow so they pull the right arch deps (I see you did some work for build-essential already), or will they all just get marked ignore? [17:52] i'm assuming for now, at least, i386 tests on focal can be ignored [19:01] seb128: python-pceclib: please don't depend on python, use python2 instead [19:01] doko, ack === rkta_ is now known as rkta [20:15] ddstreet: many autopkgtests will need adjusted individually to have correct cross-capable definitions; I've started working on uploading a number of these and will be posting to ubuntu-devel with some guidance on how to do this. In the meantime, it's correct to mark any that are failing "ignore" since they have regressed in the release pocket [20:31] so ... i386 packages started to "dissapear", correct? [20:31] from focal I mean [20:34] ah, indeed [20:34] * santa_ reads ubuntu-devel ML [20:35] yep, time to ditch my kde test rebuilds for i386 I guess [20:35] for focal, very much so ;) [21:38] fossfreedom, is it ok to sync nautilus-dropbox? [21:39] the new release is fine with budgie or not? [21:39] speaking wrt https://bugs.launchpad.net/ubuntu/+source/nautilus-dropbox/+bug/1683051 [21:39] Launchpad bug 1683051 in nautilus-dropbox (Ubuntu) "Ubuntu Budgie: Bad integration with Dropbox" [Medium,Fix released] [21:56] merged it [22:27] kanashiro, hello, any idea for this failure? I tried to sync ruby-riddle but failed https://launchpad.net/ubuntu/+source/ruby-riddle/2.3.1-2ubuntu1 [22:27] looks like the current version in focal is not even working with a no-change rebuild