[13:21] <Nafallo> hiya. is the git+ssh interface down, or is it just me?
[13:22] <cjwatson> Load spike
[13:22] <Nafallo> so not just me. thanks :-)
[13:23]  * cjwatson cancels some recipe builds
[13:25] <cjwatson> May be recovering slightly now
[13:29] <Nafallo> seem to manage to push slowly now :-)
[13:34] <Nafallo> not it broke again :-)
[13:35] <cjwatson> No need to keep telling me
[13:35] <cjwatson> I have graphs
[13:35] <GyrosGeier> hi
[13:35] <Nafallo> alright :-)
[13:36] <GyrosGeier> does the git server have problems, or is that just me getting rate limited because there is a Jenkins instance on my box?
[13:36] <cjwatson> GyrosGeier: Already working on it
[13:36] <GyrosGeier> cool, thanks
[13:37] <cjwatson> Nafallo,GyrosGeier: Should be back now
[13:38] <cjwatson> (existing connections will have been interrupted; quickest way to restore service)
[13:40] <Nafallo> yepp :-)
[13:55] <kami> Hello
[13:56] <kami> I would like to see the current code in the packaging repo of this package: https://launchpad.net/ubuntu/disco/+source/js2-mode
[13:56] <kami> But the code tab is empty
[13:58] <kami> I thought something like 'bzr branch lp:ubuntu/cosmic/js2-mode' would get me there
[13:58] <cjwatson> pull-lp-source js2-mode disco
[13:58] <cjwatson> The bzr imports are obsolete and no longer maintained
[13:58] <cjwatson> They will eventually be replaced with git imports, but that's still in progress
[13:58] <kami> cjwatson: thank you
[13:58] <cjwatson> So for now, just grab the source package
[14:00] <kami> will do
[14:31] <kami> cjwatson: I hope I may ask a packaging question here. The build of my package fails because a build dependency is not being installed.
[14:31] <kami> https://launchpadlibrarian.net/425866708/buildlog_ubuntu-bionic-amd64.js2-mode_0~20190526-1mc1~bionic+1_BUILDING.txt.gz
[14:32] <kami> The version specified in Build-Depends is dh-elpa (>= 0.0.11~)
[14:33] <kami> and the version in bionic 1.11
[14:33] <kami> What does the tilde at the end of 0.0.11~ mean?
[14:41] <GyrosGeier> kami, ~ means "less than empty string"
[14:41] <GyrosGeier> it is usually used for backports
[14:41] <GyrosGeier> e.g. a backport version would use 0.0.11~bpo
[14:41] <GyrosGeier> and it would sort before 0.0.11
[14:42] <GyrosGeier> so a system that has backports installed would replace them with the release version on dist-upgrade
[14:42] <GyrosGeier> the single ~ sorts before ~bpo (because the empty string after the tilde sorts before "bpo")
[14:43] <kami> GyrosGeier: I see. Thank you, but that doesn't explain why the builder doesn't install the build dependency.
[14:43] <GyrosGeier> so this means "any version that is at least 0.0.11, including backports and prereleases"
[14:45] <acheronuk> your build depends say:
[14:45] <acheronuk> Build-Depends: debhelper (>= 9),
[14:45] <acheronuk>                dh-elpa (>= 1.11)
[14:47] <kami> acheronuk: I tried the original >= 0.0.11~ and another build with >= 1.11. Did I make any mistake? Do you spot an error?
[14:47] <GyrosGeier> bionic has 1.11
[14:47] <GyrosGeier> that should also work
[14:47] <GyrosGeier> it's in universe, but universe should be available
[14:48] <kami> "Depends: dh-elpa (>= xxxxx) but it is not going to be installed"
[14:50] <kami> "Get:9 http://ftpmaster.internal/ubuntu bionic/universe amd64 Packages"
[14:51] <acheronuk> The following packages have unmet dependencies:
[14:51] <acheronuk>  dh-elpa : Depends: emacs25-nox but it is not going to be installed or
[14:51] <acheronuk>                     emacs2
[14:52] <acheronuk> your emacs build in the ppa is braking its install dependencies
[14:52] <acheronuk> *breaking
[14:52] <kami> acheronuk: did you find that in the build log?
[14:52] <acheronuk> no
[14:52] <acheronuk> in a pbuilder chroot
[14:52] <kami> acheronuk: ah, thanks.
[14:53] <kami> acheronuk: so this means that transitive dependencies of the Build-Depends have to be specified explicitly?
[14:55] <cjwatson> No, you don't have to specify transitive dependencies explicitly
[14:55] <cjwatson> But they do have to actually be installable, which apparently yours aren't
[14:55] <cjwatson> "but it is not going to be installed" is apt's not-hugely-helpful way of saying that something further down the dependency stack isn't resolvable
[14:56] <cjwatson> To figure out what's going on, make a matching apt environment for yourself (chroot or whatever, or chdist from ubuntu-dev-tools can be helpful) and try installing the build-deps explicitly with more and more detail until it gives you an error message that's actually useful
[14:56] <acheronuk> kami: if I remove your ppa from the sources.list of by bionic pbuilder chroot, then dh-elpa installs fine
[14:57] <acheronuk> so certainly something in your ppa
[14:59] <seb128> hey there. Does anyone here would have a pointer to how the width of the tag-edit-entry is defined? I tried to look at lib/lp/bugs/javascript/bug_tags_entry.js but I don't see any obvious place/value in there?
[15:00] <seb128> the current entry is quite small, it's annoying to edit tags list like "bionic verification-needed verification-needed-bionic" to e.g change those to -done, need to sroll, find the right one, etc
[15:05] <acheronuk> emacs25-common : Depends: emacsen-common (>= 2.0.8) but it is not going to be installed
[15:05] <acheronuk> emacsen-common : Conflicts: emacs25-common but 25.2+1-6 is to be installed
[15:05] <acheronuk> kami: that is were I get to following the dep chain
[15:06] <acheronuk> impossible requirements, as a result of what you have in that ppa
[15:06] <cjwatson> seb128: Not actually sure.  It might be computed from some kind of default value for the size or something
[15:06] <cjwatson> I mean the <input> size
[15:06]  * acheronuk leaves it there
[15:06] <kami> acheronuk: many thanks! I'm still struggling with pbuilder ...
[15:06] <cjwatson> But I could be wrong - don't see anything obvious in the CSS
[15:07] <cjwatson> seb128: I'd probably suggest experimenting with styles in Firefox's handy style editor thing
[15:07] <seb128> cjwatson, k, I guess not a 3 min hack I could do/propose on the side then I guess :/
[15:07] <seb128> good hints
[15:08] <seb128> thx cjwatson, I put a note on my side-todolist to try playing with that whenever I get some free cycles... unsure if/when I get to it, but that would make SRU verification editing less frustrating :)
[15:10] <cjwatson> seb128: Setting "width: 20em" or similar (number was arbitrary) on the CSS for that element seems to resize it in appropriate ways
[15:10] <cjwatson> FWIW
[15:10] <seb128> thx
[15:10] <cjwatson> seb128: But it might be more appropriate to set the size attribute on the <input> element's HTML
[15:11] <cjwatson> size="30" or whatever
[15:11] <seb128> what's the easiest way to test such changes made to the launchpad source if I want to go this way?
[15:11] <cjwatson> grep around to see if there's anything similar elsewhere in the codebase, which might also serve to supply appropriate choices of number
[15:11] <seb128> I haven't hacked on launchpad so far
[15:11] <cjwatson> https://dev.launchpad.net/Running
[15:12] <seb128> thx
[15:13] <cjwatson> May or may not want a unit test in this case too (not sure how valuable it would be), but for something visual you'd mainly want to try it out in a browser
[15:17] <kami> pbuilder gives me 'Unknown distribution: bionic'
[15:19] <seb128> back, my laptop reconnect to another wifi and IRC didn't like that :/
[15:19] <seb128> cjwatson, did you write something after
 May or may not want a unit test in this case too (not sure how valuable it would be), but for something visual you'd mainly want to try it out in a browser
[15:19] <seb128> ?
[15:20] <cjwatson> I did not
[15:20] <seb128> k, good
[15:20] <seb128> cjwatson, thanks for the hint, I might try to have a go to this one, would be nice to have a launchpad contribution :)
[15:24] <cjwatson> :)