[00:43] <pieq> !
[00:44] <sarnold> ~
[07:43] <ricotz> RAOF, thanks!
[12:29] <kanashiro> I am checking lm-sensors package before do the merge of the latest version we have in Debian and I am not sure if I agree with the delta we carry in this package. It basically replaces a "Breaks" with a "Conflicts" in debian/control with the justification that "Breaks" shouldn't be used without version
[12:29] <kanashiro> however, this is not mandatory and "Breaks" is preferable most of the times
[12:30] <kanashiro> could someone take a look and give me a second opinion on this?
[12:32] <cjwatson> What is the semantic purpose of the Breaks or Conflicts relationship here?
[12:33] <rbasak> I found https://git.launchpad.net/ubuntu/+source/lm-sensors/commit/?id=a7a21eead36e463e665bea74cd98ab400014c229
[12:33] <rbasak> libsensors4 last existed in Bionic
[12:34] <cjwatson> https://bugs.debian.org/915873
[12:34] <kanashiro> cjwatson, you were faster than me :)
[12:36] <cjwatson> It does seem to me that this should probably be spelled Breaks, but Conflicts+Replaces is special and so are configuration files.  I'd suggest specifically asking infinity (who made this change) for the background
[12:41] <kanashiro> cjwatson, thanks for taking a look, let's see infinity's feedback
[13:57]  * rafaeldtinoco created a ubuntu-server-ha project and ~ubuntu-server-ha team -> subscribed all HA related packages. feel free to subscribe ubuntu-server-ha to any HA related bugs
[13:59] <rafaeldtinoco> and sorry for the noise on ubuntu-server as many of those bugs were also ubuntu-server subscribed
[16:16] <rbasak> dannf: o/
[16:16] <dannf> rbasak: hey
[16:17] <rbasak> dannf: in your Bionic upload of gdb, shouldn't the changelog message say "Fix breakpoints in 32-bit programs" or something?
[16:17] <rbasak> That's what's really being fixed, right?
[16:18] <dannf> rbasak: i suspect it goes beyond breakpoints, but i'd be fine w/ mentioning that explicitly
[16:18] <rbasak> dannf: if it's quick for you to fix up please.
[16:19] <rbasak> Just that users reporting affected are holding on the package and it seems appropriate to tell them their bug is being fixed :)
[16:19] <rbasak> (and the bug description referenced doesn't match the current description)
[16:19] <dannf> rbasak: ack
[16:26] <dannf> rbasak: done - thx for the feedback!
[16:28] <rbasak> Perfect - thank you!
[16:39] <RikMills> mwhudson: hi. will there be eoan docker images any time in next week?
[17:19] <doko> jbicha: https://lists.debian.org/debian-gtk-gnome/2019/10/msg00001.html  is this agreed upon in Debian?
[19:06] <Skuggen> mdeslaur: One comment about the php issue with mysql: One reason to have used skip-grant-tables would have been if php has|had any tests that actually tried to connect remotely, since by default mysql will only create a root@localhose user.
[19:06] <Skuggen> (5.7+)
[19:08] <mdeslaur> Skuggen: yeah, I'm not sure since the php mysql tests don't seem to actually run
[19:08] <mdeslaur> I'll have to investigate...I did remove skip-grant-tables, and that made it build
[19:08] <mdeslaur> thanks for the hint
[20:11] <kanashiro> infinity, did you see our discussion earlier here about lm-sensors? If it's possible I'd like to know why do we need Conflicts instead of Breaks here https://git.launchpad.net/ubuntu/+source/lm-sensors/commit/?id=a7a21eead36e463e665bea74cd98ab400014c229
[20:16] <infinity> kanashiro: Conflicts/Replaces means "remove A to install B", Breaks/Replaces means "files in B overwrite files in A".  The latter should be versioned, the former not.  What you wanted was the former.
[20:19] <infinity> kanashiro: If what was actually intended was to overwrite files, then it should have been versioned with the version when the file moved.  I didn't look at history deeply to decide that when I made the fix, I was just fixing the case where our frontends (like update-manager) refused to perform the upgrade because an unversioned Breaks pretty much *is* a Conflict, but it won't do the swap without Conflicts/Replaces being in play.
[20:22] <kanashiro> infinity, okay, so this delta fixes an upgrade issue you faced, that's enough for me
[20:22] <kanashiro> thanks for the reply
[20:23] <infinity> kanashiro: Okay, looking at the original Debian report that caused this, yes, it should have been a Conflict.  It would have been a (versioned) Breaks if a newer version of libsensors4 existed that didn't ship the file, but that's not a thing.
[20:24] <infinity> kanashiro: Anyhow, we only need this delta through the release of 20.04 (to keep things smooth from 18.04), then it can go bye-bye.  So adding a comment like that in debian/control above the Conflicts line might be a helpful hint to future mergers.
[20:25] <kanashiro> infinity, good point, will add this comment for future merges
[20:33] <mwhudson> RikMills: do you mean focal? there have been eoan images for a while
[20:34] <RikMills> mwhudson: yeah, I do. still easy to make that mistake!
[20:35] <mwhudson> hm no images at https://partner-images.canonical.com/core/ yet
[22:38] <jbicha> doko: please be more specific with your question
[22:40] <jbicha> pygtk may be dropped from Debian Testing by the end of this year
[23:03] <jbicha> mitya57: would you like to rebuild gnome-panel and gnome-applets for https://people.canonical.com/~ubuntu-archive/transitions/html/libgweather.html ?
[23:40] <mwhudson> RikMills: https://github.com/docker-library/official-images/pull/6888