=== dviererbe1 is now known as dviererbe | ||
=== pushkarnk1 is now known as pushkarnk | ||
ahasenack | LocutusOfBorg: hi, is virtualbox (sync) 7.0.16-dfsg-3 meant to be deleted from noble unapproved, in favor of 7.0.16-dfsg-2ubuntu1.24.04.2? | 16:56 |
---|---|---|
ahasenack | https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=virtualbox | 16:56 |
ahasenack | ops, that was -hwe | 16:58 |
ahasenack | I meant 7.0.16-dfsg-3 vs 7.0.16-dfsg-2ubuntu1 for src:virtualbox in noble-unapproved | 16:59 |
Eickmeyer | waveform: Saw the Rpi testcases, and gave a cursory glance. This is purely for if one were to write to an NVMe and not a standard SD card testcase, right? | 17:05 |
waveform | Eickmeyer, basically duplicates the test cases so on Pi 4 we're testing SD and USB boot, and on Pi 5, SD, USB, and NVMe | 17:06 |
Eickmeyer | waveform: Oh! Well then, that makes perfects sense. I'll give it an ack and merge and let the other guys handle moving it to the ISO tracker. :) | 17:07 |
waveform | thanks! | 17:07 |
waveform | (hopefully I've picked reasonable IDs for the new cases) | 17:08 |
Eickmeyer | waveform: I mean, it looks like it. The merge was clean. | 17:10 |
Eickmeyer | The IDs are usually just in sequential order in the order they were added. | 17:11 |
Eickmeyer | Nothing *too* scientific there. | 17:11 |
Eickmeyer | waveform: I also like that you cleaned the model numbers to the specs since model numbers mean nothing to some people. :) | 17:14 |
ahasenack | LocutusOfBorg: around? | 17:16 |
waveform | heh, there's not many that can look at 902120 and say "that's a Pi Zero 2!" | 17:16 |
waveform | on the IDs though, I suspect the numeric part at least is a key in some database somewhere, in which case it'd depend on someone adding new entries in the right order to match the new files I've defined | 17:17 |
Eickmeyer | waveform: It's not hard as long as the filename doesn't change. ;) | 17:18 |
Eickmeyer | I've done it, but I only have access to Ubuntu Studio and Edubuntu. For Edubuntu Rpi I just re-use the Pi ones you made. :) | 17:20 |
waveform | heh, no worries -- incidentally, did you use the XML generator or just copy the outputs? (the XML generator may make it easier to customize things en masse) | 17:20 |
Eickmeyer | Nah, just point it to the ID. The ISO tracker automatically fills in the rest. | 17:21 |
Eickmeyer | In other words, it's the exact same test case, because there's no reason to change it. | 17:22 |
waveform | ah, that's a side of the tracker I've not seen yet (I just write test cases, and perform tests so far) | 17:23 |
Eickmeyer | Yep. Where there's a capitalized variable (FAMILY, for instance), the tracker will swap that out with the flavor. | 17:24 |
waveform | ah, I wrote a little XML tool (tools/test_case_gen) that I use to handle the mass of duplication in the tests (e.g. I define the bluetooth test case once, then "include" it in the models of Pi that have a bluetooth module, likewise for wifi, ethernet, etc.) | 17:29 |
LocutusOfBorg | ahasenack, as you wish | 17:35 |
LocutusOfBorg | they are both equivalent | 17:35 |
ahasenack | LocutusOfBorg: I'm just adding a comment to the bug, | 17:36 |
ahasenack | LocutusOfBorg: done | 17:36 |
LocutusOfBorg | ahasenack, the patch is coming from #vbox-dev irc channel | 17:37 |
ahasenack | is it committed? | 17:37 |
ahasenack | was anything else needed? I saw the same code further down | 17:37 |
ahasenack | why isn't there a 7.0.16.1 out yet, given the criticality? | 17:38 |
ahasenack | (not doubting you, and thanks for jumping on it, I'm just being careful with the details) | 17:38 |
ahasenack | and since I don't see further movement upstream (or I just didn't find the bug), my worry is if this patch is enough/correct at this moment, or if further analysis is happening | 17:40 |
LocutusOfBorg | it is correct | 17:40 |
LocutusOfBorg | but they don't release .1 updates, they jump to 7.0.18 and this takes time | 17:40 |
LocutusOfBorg | so they advice to not update for now, and in some days they will release it | 17:40 |
ahasenack | is there an upstream bug? | 17:41 |
LocutusOfBorg | not sure sorr | 17:41 |
ahasenack | I found some, but the host is windows | 17:41 |
ahasenack | like https://www.virtualbox.org/ticket/22045 | 17:41 |
-ubottu:#ubuntu-devel- www.virtualbox.org ticket 22045 in host support "VirtualBox 7.0.16 crashing host OS immediately with a BSOD by VBoxNetLwf.sys" [New] | 17:41 | |
ahasenack | found a commit: https://www.virtualbox.org/changeset/104355/vbox | 17:42 |
ahasenack | bugref:10585 | 17:43 |
ahasenack | let's see | 17:43 |
LocutusOfBorg | https://www.virtualbox.org/ticket/22052 | 17:43 |
-ubottu:#ubuntu-devel- www.virtualbox.org ticket 22052 in other "'VM guest crashed (Host: Windows 10, Guest: Debian GNU/Linux) due to '' rtR3WinUnhandledXcptFilter caught an exception'''" [New] | 17:43 | |
ahasenack | https://www.virtualbox.org/ticket/10585 doesn't seem to be it | 17:43 |
-ubottu:#ubuntu-devel- www.virtualbox.org ticket 10585 in other "The SIGALRM never fires" [Closed] | 17:43 | |
ahasenack | that's on 7.0.14, not .16 | 17:44 |
LocutusOfBorg | sorry I already found the commit, but the paste failed | 17:44 |
ahasenack | is there a git mirror by any chance? | 17:44 |
ahasenack | svn, ugh | 17:44 |
LocutusOfBorg | ahasenack, it is a tricky issue, it is due to USB ASAN being enabled inside kernel | 17:44 |
LocutusOfBorg | UBSAN whatever | 17:45 |
ahasenack | "Author: | 17:45 |
ahasenack | vboxsync" <-- I suppose they have an internal repository, closed up, and the external one just syncs from it | 17:45 |
LocutusOfBorg | so, the bug was there since long time, but recent kernels made serious | 17:45 |
LocutusOfBorg | yes they have | 17:45 |
ahasenack | the bugref in https://www.virtualbox.org/changeset/104355/vbox might also be pointing at an internal bug db? | 17:46 |
ahasenack | "SrvIntNetR0: Fixed regression from r162583 that caused allocation of one segment instead of two ​bugref:10585" | 17:46 |
LocutusOfBorg | yes correct | 17:47 |
ahasenack | even the mentioned changeset (r162583) is not available | 17:47 |
ahasenack | classic oracle, I think they do the same with mysql | 17:47 |
LocutusOfBorg | also correct, they map internal issues to external public ones | 17:47 |
LocutusOfBorg | :/ | 17:47 |
LocutusOfBorg | and they sync from time to time | 17:47 |
ahasenack | and no chatter about this in vbox-dev | 17:47 |
LocutusOfBorg | this way we can be "open source" without leveraging the internal customer defects | 17:48 |
ahasenack | https://www.virtualbox.org/pipermail/vbox-dev/2024-April/thread.html april all messages | 17:48 |
ahasenack | would it be worth it sending an email there asking about details for this crash? Bug, if the patch from that commit is the only fix needed, etc? | 17:48 |
ahasenack | also ask why they have that big fat warning in the front page, but not in the 7.0.16 changelog, and haven't even pulled 7.0.16 from what we can tell | 17:49 |
ahasenack | is that a crash in the kernel module loaded on the host? It actually crashes the host kernel and you have to reboot? | 17:49 |
ewlu | Hi I'm looking to package a version of binutils with a different tuple name (i.e. riscv64-something_here-linux-gnu-ar) which also wouldn't override the existing binutils installation. I'm new to creating packages and I've been struggling to change the installation tuple name for a while. Can I get some help? | 18:25 |
ewlu | I've modified the debian/rules to target the new tuple name, messed with the CROSS_GNU_TYPE (since I see that's what is used in the install step), tried messing with the package name in debian/control. Is there somewhere else I should be modifying? | 18:27 |
Eickmeyer | waveform: Quick question: Is there a way we can get Edubuntu 24.04 added to `rpi-imager`? | 18:31 |
waveform | Eickmeyer, yes -- there's a few questions to answer though. Specifically: do you want a separate Edubuntu section? (we need to request that from rpi upstream, but it's probably preferable to having yet-another-image under the already packaged Ubuntu section), where should be icon be hosted? (ideally this should be a unique URL specifically for the imager, and the icon needs to be a 48x48px PNG or SVG), and finally how do you want to control | 18:34 |
waveform | the JSON? (I've got a script for that too, if you want :) | 18:34 |
waveform | *the icon even | 18:34 |
Eickmeyer | waveform: Heh, the icon is easy; I can make that happen pretty quick. A separate Edubuntu section can be done, and JSONs are easy. :) | 18:36 |
waveform | for reference, https://git.launchpad.net/meta-release/tree/refresh_os_list?h=main is the script we use to maintain the JSON for the Ubuntu images (basic usage "point the url: field at the image and let it generate the rest") | 18:37 |
waveform | and https://git.launchpad.net/meta-release/tree/raspi/os_list_imagingutility_ubuntu.json?h=main is what the JSON looks like | 18:38 |
Eickmeyer | waveform: Well, since we only have one, this should be easy. | 18:42 |
Eickmeyer | waveform: Think this is suitable? https://git.launchpad.net/~edubuntu-dev/+git/edubuntu-assets/plain/LogoAssets/edubuntu-rpi-imgr.png | 18:43 |
Eickmeyer | Hmmm.. Actually, I have a better idea. | 18:44 |
waveform | Eickmeyer, best way to find out is to test it for yourself; generate the JSON with the icon URL as you'd like then serve your JSON with a local web-server (python3 -m http.server is fine), and run "rpi-imager --repo http://localhost:8000/os_list_imagingutility_edubuntu.json" for example -- you won't see the root menu this way but you should see how your entries will appear otherwise | 18:45 |
Eickmeyer | https://www.edubuntu.org/assets/edubuntu-rpi-imgr.png | 18:46 |
waveform | yeah, that icon certainly looks fine to me -- but I'd definitely try it out in the imager to check it looks okay there | 18:47 |
Eickmeyer | Yep. I'm 100% confident in that one, it's a github host. | 18:47 |
jbicha | https://merges.ubuntu.com/main.html looks down, wish I could cheer it up | 19:14 |
vorlon | jbicha: needs one of bdmurray, sil2100, or doko to fix it; all of them are currently off | 19:40 |
tarzeau | when does debian archive sync start again? | 20:16 |
hallyn | hm, having a case, in a rather convoluted noble based build script, where dracut module install is failing on btrfs when it wants to do 'printf "%s\n" "$(cmdline)" > "${initdir}/etc/cmdline.d/00-btrfs.conf' , saying no such file. | 20:35 |
hallyn | if i edit /usr/lib/dracut/modules.d/90btrfs/module-setup.sh to create that dir on the line before,it passes. | 20:35 |
hallyn | seems very odd, didn't see anything in debian/changelog to explain that | 20:35 |
ahasenack | dbungert: hi, around? | 21:41 |
dbungert | ahasenack: hey there | 21:41 |
ahasenack | dbungert: I'm looking at the pam sru | 21:42 |
ahasenack | dbungert: userdb is fine | 21:42 |
ahasenack | dbungert: the other one about docs, I did a rebuild in noble, but I'm not getting the extra docs | 21:42 |
ahasenack | dbungert: did you try a build in a ppa or something, and it worked? | 21:42 |
ahasenack | dbungert: I'm also failing to debug why my local build doesn't have the docs | 21:42 |
ahasenack | I do get "checking for DocBook XSL Stylesheets in XML catalog... found", which I can see in the noble archive build was "not found" | 21:43 |
dbungert | ahasenack: hmm, I thought I had, but I think I'm confusing with the oracular upload | 21:44 |
dbungert | ahasenack: yea, the 7ubuntu1 upload is happy and 5ubuntu5.1 is not, I'll investigate why. Sorry about that. | 21:49 |
ahasenack | ok, I'll leave a comment in the bug | 21:49 |
dbungert | ahasenack: please reject pam 1.5.3-5ubuntu5.1 | 22:25 |
dbungert | vorlon: would you reject pam 1.5.3-5ubuntu5.1 from noble? I need to reupload. | 22:48 |
vorlon | dbungert: ack | 23:06 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!