Le 09/01/2017 à 20:18, Eli Schwartz via arch-general a écrit : > On 01/09/2017 02:07 PM, Bruno Pagani via arch-general wrote: >>> Does this mean we will see 4.8.16 being built and pushed out to users? >> This could indeed be done (it’s even 4.8.17 as of today) if 4.9.2 still >> doesn’t fix those issues (it has been discussed before that Arch should >> continue to package updates to the kernel if the new one isn’t ready for >> consumption), but that’s up to @tpowa. ;) > Well, the kernel still needs to go through [testing] (which is where we > are currently testing 4.9). So maybe that would happen if tpowa gives up > on 4.9 for now altogether. Yes, that’s why I’ve said it was up to @tpowa. ;) > I'm a bit confused as to why the svntogit logs claim 4.9.2 was pushed to > testing, but the repos still show 4.9.1 Well, I’ve often seen a bit of discrepancy between svntogit logs and the repos. Like a package to be updated on my system, but when I go to see what was changed, nothing… I admit not being and expert in archweb internals, so whether that is kind of expected or not, but I seem to remember there was a discussion about this one day on a ML even if can’t find that again right now. Bruno
Attachment:
signature.asc
Description: OpenPGP digital signature
