| RAOF | Hey all! (take 2) | 02:34 |
|---|---|---|
| RAOF | Who particularly wanted https://wiki.ubuntu.com/NVidiaUpdates to be considered? I'm SRU-team-looking at it at the moment. | 02:34 |
| RAOF | And I Have Questions. | 02:34 |
| RAOF | jibel: Aha! Now that matrix has caught up I see you! | 02:37 |
| duflu | That's a large glitch in the matrix | 04:05 |
| RAOF | That's LXD updating, and for some reason losing network connectivity out of the containers I have my homeserver in… | 04:08 |
| jibel | RAOF, hi, thanks for reviewing. What questions? | 05:51 |
| * jibel waits for the matrix to update and an answer on Monday | 05:51 | |
| jibel | hi all | 05:52 |
| RAOF | jibel: 😛 | 05:52 |
| RAOF | So, my main question is: why backport the short-lived branches? | 05:52 |
| RAOF | Because, as I understand it, you get all the hardware-enablement goodness out of SRUing the long-lived branch? | 05:53 |
| jibel | RAOF, because short lived adds new features and latest gpu support | 05:54 |
| jibel | in long lived there are also new gpu but only bug fixes | 05:54 |
| RAOF | I thought the long-lived branches also added GPU support? | 05:54 |
| jibel | yes, but only bug fixes | 05:55 |
| RAOF | Ok. So SRUing the short-lived branch is not really about hardware enablement, then? | 05:56 |
| jibel | someone who's on long lived won't be switch to short lived unless he does it intentionally | 05:56 |
| jibel | no, it's more to bring the latest stuff from upstream to the users of this hardware. | 05:57 |
| jibel | they also have support for newer gpu earlier with short lived | 05:57 |
| RAOF | Ok. | 05:58 |
| RAOF | So, the rest is entirely uncontrovertial, as far as I can see; long-lived and legacy are clearly HWE, and we made our peace with that long ago 😸 | 05:59 |
| jibel | Great :) | 06:03 |
| jibel | RAOF, so what's next, we'll get a formal approval or have to amend the exception? | 06:07 |
| RAOF | And since you need to opt-in to using the short-lived branches, they're probably fine to SRU, too. | 06:07 |
| jibel | excellent | 06:07 |
| RAOF | That's a good question! | 06:07 |
| RAOF | My memory of the feeling of the SRU team in the meeting was that this was basically a special case of the HWE exception we already have. | 06:08 |
| RAOF | I'll check the notes for that, but I believe the next step is me signing off on that. | 06:08 |
| duflu | Morning jibel | 06:09 |
| jibel | Evening duflu | 06:09 |
| duflu | Not quite. But it is for RAOF | 06:10 |
| duflu | Evening/afternoon RAOF | 06:10 |
| RAOF | And a fine afternoon to you, too, duflu | 06:10 |
| duflu | Is there an Nvidia definition of long/short lived? | 06:11 |
| duflu | Or is that of our making? | 06:12 |
| jibel | duflu, there is no official definition, but it's what I gathered from their website and replies from their support team on the forums | 06:13 |
| jibel | it's a recurring question | 06:13 |
| duflu | Yeah I was trying to tell from the version numbers but could not | 06:13 |
| duflu | You can only tell a series is long lived when it's long lived | 06:13 |
| jibel | there is no logic between the version number and the branch | 06:13 |
| RAOF | They explicitly call out long lived/short lived on the driver page: https://www.nvidia.com/object/unix.html | 06:14 |
| duflu | Oh. How did I miss that? Thanks! | 06:14 |
| duflu | I guess I always go in via the drivers menu which is on the black geforce web site and it doesn't tell you there | 06:15 |
| RAOF | Although, amusingly, there isn't currently a short-lived branch that's useful. | 06:15 |
| RAOF | (The current short-lived branch is 415; the long-lived branch is 430) | 06:16 |
| jibel | from my discussion with tseliot odd numbers are short lived and even are long lived | 06:16 |
| jibel | to be confirmed | 06:16 |
| duflu | That makes sense. So how long is "long" according to Nvidia? | 06:17 |
| jibel | "A short-lived branch typically has only one or two (non-beta) releases, while long-lived branches will have several." | 06:19 |
| jibel | so "long" = "several releases" that's helpful | 06:20 |
| jibel | from the archive there's been 6 releases of 415 (short lived) between Nov 2018 and Jan 2019 | 06:27 |
| jibel | and 6 of 410 from Sept. 2018 and Feb 2019 | 06:28 |
| jibel | long is a bit longer that short but not much | 06:28 |
| === pstolowski|afk is now known as pstolowski | ||
| marcustomlinson | good morning! | 07:46 |
| willcooke | morning all | 07:51 |
| seb128 | good morning desktopers | 07:52 |
| willcooke | hi seb128 | 07:52 |
| seb128 | hey marcustomlinson willcooke, happy friday! | 07:52 |
| willcooke | \o/ | 07:52 |
| marcustomlinson | :D | 07:52 |
| Laney | yo | 08:02 |
| Laney | guten fridayen | 08:03 |
| seb128 | hoi Laney, bon vendredi ! | 08:03 |
| duflu | Good morning marcustomlinson, willcooke, seb128, Laney | 08:07 |
| seb128 | hey duflu, how are you? having a nice friday? ready for the weekend? ;) | 08:07 |
| duflu | seb128, mostly nice yeah. I don't know about "ready" for the weekend but I will appreciate it. You? | 08:08 |
| seb128 | one full day to go, I hope to get some work done, we are approaching end of june and I have half my trello card not started yet for this iteration :/ | 08:09 |
| seb128 | otherwise I'm looking forward the w.e, we are in the North of France for 3 days, weather should be nice and there are music festival for the summer start | 08:09 |
| Laney | hey seb128 duflu | 08:09 |
| Laney | happy summer/winter solstice! | 08:11 |
| * Laney should get to start a new Trello card on Monday hopefully ... | 08:12 | |
| Wimpress | o/ | 08:15 |
| duflu | \o | 08:21 |
| Laney | _o> | 08:23 |
| seb128 | tkamppeter, hey, what's the status of fixing the network manager autopkgtests? | 08:37 |
| kenvandine | seb128: last i heard he had found the cause of the callback hanging but there were other failures he was working on too | 12:59 |
| seb128 | kenvandine, hey, k, thx for the update! (is Till off today? also do you know if he works in a vcs or such?) | 13:00 |
| kenvandine | not off and not sure if he's pushing his work anywhere | 13:00 |
| seb128 | k, enough work for this week | 16:35 |
| seb128 | today was Debian merges day and bug triage, I feel tired now, going to enjoy the nice weather and a beer :) | 16:35 |
| seb128 | see you on monday! | 16:36 |
| Laney | bye seb128 | 16:36 |
| teward | seb128: have one on me :) | 16:39 |
| seb128 | :-) | 16:40 |
| willcooke | happy weekend all, see you next week | 17:10 |
| === pstolowski is now known as pstolowski|afk | ||
| kenvandine | jdstrand: i have a snap awaiting review because of a minor change to the dbus name | 18:21 |
| kenvandine | - name: org.gnome.sudoku | 18:22 |
| kenvandine | + name: org.gnome.Sudoku | 18:22 |
| tkamppeter | Hi, Is there a function to turn the string "192.168.5.23" into an integer? | 18:51 |
| sarnold | tkamppeter: yes. *however*, using it will mean you're not going to work with ipv6 addresses. | 18:56 |
| sarnold | tkamppeter: if you're okay with ipv4 only for whatever reasons, inet_aton(3). that'll emit the address in network byte order, not host endianness. | 18:56 |
| tkamppeter | sarnold, first, the code part where I will use it, is IPv4-only, and second, I got the suggestion to use the netaddr Python module which has a function which convers both IPv4 and IPv6 addresses. | 20:01 |
| sarnold | tkamppeter: oh cool | 20:01 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!