[10:21] <cpaelzer> versioning question - current version in Debian is 1.1.99.51-1~unstable  and I need a no change rebuild - dch -R will make 1.1.99.51-1~unstablebuild1 out of that - is that a pattern that will work in all tools?
[10:21] <cpaelzer> the fused "unstablebuild1" suffix makes me suspicious that might e.g. no more be auto-synced
[10:22] <cpaelzer> does anyone know for sure what the proper no change rebuild version for this would be?
[10:22] <cjwatson> Only an "ubuntu" substring inhibits auto-sync
[10:22] <cpaelzer> thanks cjwatson I was afraid it might have more complex rules
[10:23] <cjwatson> 1.1.99.51-1~unstablebuild1 seems fine.  I might possibly make it be 1.1.99.51-1~unstable+build1 for clarity for humans, but it's also OK to stick with the autogenerated version IMO
[10:25] <cjwatson> There are a few other non-version-related things that can cause auto-sync to refuse to touch a package, but the "ubuntu" substring has always been the only version-related rule
[11:32] <ahasenack> hi, any idea what this autopkgtest failure means? https://pastebin.ubuntu.com/p/mZyyPzZxSF/ "badpkg: rules extract failed with exit code 1"
[11:32] <ahasenack> on apt-source
[13:39] <ejat> hi .. how to troubleshoot if i cant login ubuntu using xorg but if i using wayland can login ?
[13:39] <ejat> its happened when im using kernel 4.19.x
[13:40] <ejat> but its working fine if im using kernel 4.18.x
[13:40] <ejat> can someone advise ? thanks
[13:50] <ejat> sorry ... my bad .. suddenly its working :(
[15:56] <teward> anyone know if there's a way I can tell the system what key to use to sign a package when I do debuild -S ?
[15:57] <teward> asking because I recently set my "old" keys to expire because I am doing key rotations every so often, and am providing a new key this time.
[15:57] <xnox> teward, ~/.devscripts ?
[15:57] <teward> xnox: right, but i meant the specific argument to provide in it
[15:58] <teward> i know ~/.devscripts but I made a fubar and lost my .devscripts oops.
[15:58] <teward> so I need to rebuild that.  Don't remember the key/value pair to enter in there
[15:58] <xnox> teward, man debsign -> configuration variable -> DEBSIGN_MAINT DEBSIGN_KEYID etc
[15:58] <teward> ah, thanks xnox :)
[16:01] <teward> xnox: always forget where in the manpages this stuff sits.  heh.  :P
[16:04] <cjwatson> This also suggests that you don't have backups, and you should fix that.
[16:12] <teward> cjwatson: well, actually the problem was drive death
[16:12] <teward> and then LVM2 corruption
[16:13] <teward> so that's the core problem there
[16:13] <teward> everything's backed up now
[16:13] <teward> and copied in at least 5 places :P
[22:44] <bdmurray> coreycb: Does bug 1811098 need to be private? that's frowned upon for SRU bugs
[22:46] <coreycb> bdmurray: i dont think it does based on the feedback in the bug but being a security issue inwas hesitant to switch back to public
[22:46] <coreycb> I was
[22:47] <bdmurray> I think its fine but maybe we should ask a security guru like sarnold
[22:54] <sarnold> bdmurray,coreycb, yes, I believe this bug ought to be public -- the fix is public, and it's not something that is itself exploitable
[22:55] <bdmurray> sarnold: evenly for an "immensely powerful advesary"?
[22:56] <bdmurray> The other day I saw you use those words and I busted up
[22:56] <sarnold> I'm always happy to entertain :)
[22:56]  * jbicha busts up thinking of bdmurray busting up
[22:57] <bdmurray> coreycb: So do you want to make it public?
[23:12] <coreycb> bdmurray: sure and thanks
[23:12] <coreycb> sarnold: thanks for the input
[23:12] <sarnold> you're welcome :)