mvoRAOF: hey, do you think you could check the snapd SRU (2.46.1) ? woudl be great to get it into *-proposed to help e.g. the cpc tema that needs it for their work06:56
RAOFmvo: I presume 2.46.1 supercedes the 2.46 already in the unapproved queue?06:59
mvoRAOF: correct07:00
mvoRAOF: thanks a lot for looking into this07:00
RAOFUrgh. Could you do a new upload, with the combined 2.46 & 2.46.1 changelog in the .changes?07:02
RAOFOr maybe not.07:03
RAOFThose changelogs are not user-friendly ;)07:04
mvoRAOF: *cough* that is unfortunately true07:05
RAOFHeh. https://wiki.ubuntu.com/SnapdUpdates could do with an update!07:06
RAOF16.04 is not the latest stable release, and it turns out we have not one, but two LTS releases that need upgrade testing for :)07:07
mvoRAOF: indeed, let me look at this wiki page07:51
mvoRAOF: thanks for letting it into -proposed07:52
seb128hum, I don't understand why the proposed report lists gstreamer1.0 blocked on the spice/ppc64el autopkgtest failing today but wasn't yesterday08:58
seb128the test failed a week ago and gstreamer didn't change since yesterday08:58
seb128why did it start picking it up now?08:58
ginggsseb128: because spice passed once against zlib/1:1.2.11.dfsg-2ubuntu2, resetting the force-reset-test09:03
seb128ginggs, oh, ok, that would explain, thanks!09:04
ginggsseb128: yw!09:04
seb128could someone from ubuntu-release bump that reset?09:05
ginggsseb128: that's one way, but is it fixed now? i'm retrying the test you triggered, adding zlib09:16
seb128ginggs, I already had done that (retrying with zlib added)09:18
seb128but yeah, let's wait for that09:18
seb128ginggs, https://autopkgtest.ubuntu.com/packages/s/spice/groovy/ppc64el had one success at the bottom and I don't really see why the zlib update would fix the issue, I think it's more likely that it's just get lucky sometimes and avoid the timeout and it happened to be one of those tries09:19
ginggsseb128: yeah, that success at the bottom is just inherited from the previous series, my test has already finished - results should appear soon09:22
ginggsif it failed you can ask in #ubuntu-release for someone to bump the force-reset-test hint09:24
ginggsseb128: oh and there you result appeared.  sigh, the lag here is really annoying09:25
LocutusOfBorgseb128, better wait for gst* 1.18 that is now in sid=09:30
LocutusOfBorggst-plugins* merges are a nightmare09:30
LocutusOfBorgwill do 1.18 once mergeomatic catches it09:31
LaneyLocutusOfBorg: you're aware of feature freeze yes?09:37
seb128_bah, disconnected again09:47
seb128_Laney, unsure if that got replied, but I did sync the new gstreamer 1.17 serie before ff, just failed to merge some components to get it migrated out of proposed and I asked LocutusOfBorg for help with the merges09:48
Laneyseb128_: ok09:48
seb128_Laney, you think ff is needed in that case?09:48
Laneybtw Ken took the task of looking at all of that in the last team meeting09:48
seb128_it's a bit of a weird situation09:48
seb128_Ken fixed his part09:48
Laneyso you might want to check ...09:48
seb128_which was the failed tests09:49
Laneywhat part?09:49
Laneythe part was "gstreamer is stuck in proposed"09:49
seb128_the failing tests09:49
Laneynot any random section of it :p09:49
seb128_well I talked to him friday09:49
seb128_I don't he realized there was more than the tests09:49
seb128_since the by team report doesn't mention the broken binaries09:49
Laneyff> probably not, but depends what is in the new releases09:49
seb128_(I've a mp up for review improving that btw)09:49
=== seb128_ is now known as seb128
seb128Laney, well, technically the non merged plugins would need a ffe since that's an update to a new serie09:50
seb128but at the same time it's the same as the new GNOME, we can't release one an half finished transition...09:51
LaneyI guess the main thing we'd want is reassurance that it's been well tested and that someone is going to take care of any issues09:54
seb128LocutusOfBorg, hey, since 1.18 has been uploaded then the merges are doable now10:09
Laneynot sure why you'd want/need to wait for merge-o-matic when those are maintained in git in both Debian and Ubuntu10:11
Laneyhopefully the latter is true, but I refuse to check and find out it's not since I stopped looking after it :p10:12
LocutusOfBorgLaney, they are maintained in git, and I update git10:39
LocutusOfBorgbut the packaging has been redone from scratch10:39
LocutusOfBorgso merge is painful10:39
LocutusOfBorgand by looking at the ~10 closed bugs in 1.18, mentioning crash fixes in Debian, meh, I think its worth a look...10:40
Laneyhow can merge-o-matic do it better?10:40
LocutusOfBorgspecially because the diff between 1.17.90 in proposed and 1.18 might be so little10:40
LocutusOfBorgLaney, probably it won't but meh, I'm used to it10:40
LocutusOfBorgI usually use MoM and then commit on git and upload :p10:41
* xnox too10:51
xnoxi remember using mercurial-queues really well to do merges.10:51
xnoxbzr merge didn't quite work for me.10:51
xnoxand i never managed a git-based package merge yet.10:52
=== didrocks999 is now known as didrocks
kanashiroFYI my +1 maint shift started and I am trying to make rails 6 migrate14:54
xnoxLaney:  are you AA on a +1 by any chance?15:15
xnoxi want to demote two packages, and remove two =)15:15
xnoxcause that's the way my +1 maintainance rolls.15:16
xnoxi guess i can highlight that in the status report.15:16
LocutusOfBorgseb128, sync the gst* from sid?15:27
LocutusOfBorgI'm doing based and good merges now15:27
LocutusOfBorg*good and ugly*15:27
seb128LocutusOfBorg, I will sync when syncpackage picks the update up, which isn't the case yet15:28
LocutusOfBorginteresting, mergeomatic picked them up15:28
GunnarHjHi tsimonq2, would appreciate your input wrt Lubuntu on this topic:15:30
Laneyxnox: I'm not, but I could maybe help depending on if it's simple15:32
Laneyif it requires some thought, punt to the status report :-)15:32
seb128LocutusOfBorg, I don't really understand how often and when things get available for syncing...15:35
cjwatsonmerge-o-matic goes off its own Debian mirror, so it can be a bit in advance of LP's view on occasion15:40
cjwatsonJust depends on exact timing of Debian archive cycles etc.15:40
cjwatsonLP's view is synced every six hours a little behind when the Debian archive is predicted to publishe15:41
cjwatsonBut it's not a particularly exact science15:41
seb128thanks for the details, I will retry in a bit15:44
tyhickshello - I'm missing some historical context on the purpose of the Xorg enablement stack (xserver-xorg-hwe-18.04 in Bionic) and thought someone here might be able to help16:44
tyhicksis the Xorg enablement stack required for compatibility with the kernel enablement stack or is it purely for supporting new hardware?16:44
tyhicksin other words, has the kernel enablement stack broken something in Xorg?16:45
tjaaltontyhicks: the latter, traditionally. but these days there's less hwe specific bits in the xorg stack, maybe for amdgpu but that's it. mesa is backported as-is, so that the GA stack uses the same mesa without issues17:07
LocutusOfBorgseb128, finally looks syncable now17:14
tyhicksthanks tjaalton :)17:16
tjaaltonyw :)18:01

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!