| === _salem is now known as salem_ | ||
| === salem_ is now known as _salem | ||
| === tumbleweed_ is now known as tumbleweed | ||
| === ahoneybu- is now known as ahoneybun | ||
| === FlannelKing is now known as Flannel | ||
| === Adri2000_ is now known as Adri2000 | ||
| === Adri2000 is now known as Guest9808 | ||
| Laibsch | Would some kind soul please accept nomination for trusty for bug 1287424 and if possible even move along the SRU? | 12:03 |
|---|---|---|
| rbanffy | Hi folks. How is the usual process of packages trickling down from source to stable distribution? Every time I make changes to https://github.com/rbanffy/3270font I tell the Debian font team, who, in turn, say they'll reflect them. The package then goes from Debian repo (https://packages.debian.org/sid/fonts/fonts-3270) to all Debian-like distros (Ubuntu, which I use, included) | 12:31 |
| hjd | rbanffy: Hi. Ubuntu usually sync new packages from Debian unstable to the current Ubuntu development release. Exceptions are if the package has some ubuntu-specific patches (you can tell if the version number contains "ubuntu") in which case someone need to manually merge it, or when it is late in the development cycle when the automatic import has stopped in order to not have too many changes before release. | 12:39 |
| hjd | For instance, for Wily Werewolf, packages were automatically synced up until August 20th (https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule). It is of course possibly to request syncs at a later point though. | 12:40 |
| rbanffy | Thanks, hjd. | 12:45 |
| rbanffy | hjd, I guess the next sync will be for wily+1 then. | 12:47 |
| rbanffy | In any case, byobu users who use mu font (all three of them, me included) will be happy to know I added a ⟫ in late May. | 12:48 |
| infinity | rbanffy: If you ask nicely (and assure me it won't break), I can sync it to wily. There's still time. | 12:50 |
| rbanffy | infinity, I am pretty sure it won't. All 1.2.4 fixes (1.2.3 is on Sid) is Windows compatibility. | 12:52 |
| infinity | rbanffy: If you're sure the sid/testing version is cool, we can sync it. | 12:53 |
| rbanffy | I'm cool with it. My main machine uses it built from "source". | 12:54 |
| infinity | rbanffy: Done. | 12:54 |
| rbanffy | Maybe it's time to release again. I added a couple glyphs and fixed some hinting issues. | 12:54 |
| rbanffy | I'll take it for a spin on Wily. Thanks, infinity. | 12:55 |
| nadrimajstor | I'm trying to triage a bug for 14.04 and I found an SRU proposed change that targets Vivid that contain upstream bug fix. | 13:25 |
| nadrimajstor | Should I add a comment to the Vivid's SRU bug asking for additional release target to be added? | 13:27 |
| hjd | infinity: Hm... I actually didn't know it was still possible to sync packages this close to release. | 13:42 |
| tsimonq2 | hm, if a package is submitted to Debian, will it make it's way to Ubuntu no matter what? | 13:59 |
| cyphermox | No, it needs to be synced or merged manually, from now until release. | 14:02 |
| tsimonq2 | cyphermox: but if I upload it now, after the release will it filter down? | 14:05 |
| cyphermox | Yes | 14:05 |
| tsimonq2 | cyphermox: so every Debian package is in Ubuntu? | 14:05 |
| tsimonq2 | or the Ubuntu servers, rather | 14:06 |
| cyphermox | You can still have it in Ubuntu for the release if it lands in Debian and you ask for it to be synced | 14:06 |
| cyphermox | Pretty much every debian package is in Ubuntu yes | 14:06 |
| tsimonq2 | pretty much? | 14:06 |
| tsimonq2 | obsoleted packages maybe? | 14:06 |
| tsimonq2 | cyphermox: ok, thank you | 14:08 |
| cyphermox | There are some few exceptions for things that would be replaced by a package with a different name or things that are just for architectures we don't support, IIRC. You don't need to worry about it for your package, I'd think :-) | 14:10 |
| tsimonq2 | ok :) | 14:10 |
| tsimonq2 | cyphermox: and on average, how long does it take to filter downstream? right away if it is not near a release? | 14:11 |
| cyphermox | Depends on the schedule, right away if it's during the time we do automatic imports, except if there are changes in Ubuntu's version of the package at the time, otherwise there are some manual steps (merging, or requesting a sync) | 14:13 |
| tsimonq2 | ok :) | 14:17 |
| tsimonq2 | thank you | 14:17 |
| JanC | there are also Debian packages that have different packaging in Ubuntu, I think, in which case the original Debian package wouldn't be there? (at least there used to be) | 14:40 |
| tsimonq2 | JanC: Explain please | 14:43 |
| JanC | tsimonq2: there used to be applications that were packaged independently by both (so two developers making a different packaging); but AFAIK Ubuntu policy is not to do that unless it's *really* *really* necessary for some *very* *good* reason :) | 14:48 |
| tsimonq2 | ok :) | 14:50 |
| cyphermox | Yep | 14:50 |
| JanC | and some years ago there was some work done to remove those, but I'm not sure how many are left | 14:55 |
| JanC | I guess the kernel is one of them | 14:55 |
| === _salem is now known as salem_ | ||
| === salem_ is now known as _salem | ||
| hjd | I don't see any patch pilots, but if someone wants to do a small code review for Wily, there's bug 1507295 :) | 15:48 |
| tsimonq2 | what Debian version is Ubuntu based off of? | 16:29 |
| mitya57 | It's unstable. | 16:32 |
| tsimonq2 | ok, thanks | 16:33 |
| === _salem is now known as salem_ | ||
| === salem_ is now known as _salem | ||
| jtaylor | 16.04 is going to be testing right? | 20:10 |
| mitya57 | jtaylor, IIRC we are nowadays using unstable for LTSes too | 20:15 |
| mitya57 | (as we have smart proposed migration which will catch issues) | 20:15 |
| cjwatson | jtaylor: As mitya57 says, no, unstable. I explained this at more length the other day. | 20:35 |
| cjwatson | jtaylor: The last LTS to sync from testing was 12.04. | 20:35 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!