=== jrib is now known as Guest10239 [06:59] good morning === Nigel_ is now known as G === Guest10239 is now known as jrib [14:38] Is there a wiki or help page on the difference between regular suite and -update suite? [14:38] And the timeline for when -update flows back into regular one? I.e. the point releases? [14:39] Ah, I guess I found it, https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule [14:40] Are all packages in -update flowing into the next point, or are there sometimes packages getting rejected? [15:15] Rhonda: all packages in -updates go to the next point release - in fact the point release is basically a snapshot of -updates [15:17] A snapshot of -updates? So -updates is a full suite, not just the revised packages? [15:19] Sorry, a snapshot of (release + release-updates) [15:19] -updates is a partial suite [15:31] Thanks :) [17:09] hi [17:09] bzr builddeb fails and says "secret key not available" [17:09] but I have the key [17:10] may be it is because I have multiple keys in it [17:11] is there a way to specify the key? [17:11] like there was in dh_builddeb [18:14] what is a "multi byte string"? Does that mean UTF-8 or does it depend on your locale? [18:19] any unicode string can be multibyte [18:19] e.g there are unicode codecs with fixed size, 2, 3 or 4 byte, or variable size codecs like utf-8 [18:20] utf-8 is multibyte as soon as you go beyong ascii (or latin1?) [18:23] I mean the C functions like wctomb... what does it mean when it says multi byte? what is the actual char set used? [18:24] parted seems to be taking the UTF-16 string in the partition table and just decimating it to 8 bit chars by discarding the upper 8 bits [18:24] so I'm trying to figure out how to fix it to translate it to the proper form, but I'm not sure what that is and how to do it... [18:25] I'm guessing it is UTF-8 [18:26] or does the native code set depend on the current locale? and some don't use utf-8? [18:28] there is utf-16 in the partition table oO [18:28] fun [18:28] I think what the C w* functions do is locale dependent [18:29] but luckyly I never had to actually use them [18:29] so can't really help you [18:32] looks like I need to convert from utf-16 to wchar_t, then convert that into whatever encoding the current locale is using... wait... what is wchar_t? isnt't that always utf-16? [18:32] I think so [18:32] no not utf-16, but always 2 byte [18:33] could be UCS-16 or whatever weird 2 byte encodings there are [18:34] hm no its not even defined what size it is in the standard [18:36] (4 byte on my system btw) [18:37] jesus christ... how can all of these conversion functions talk about what they are converting from/to without knowing what the actual format of either end is! [18:38] they get it from the locale [18:38] any help up above? [18:38] so the locale defines BOTH the format of wchar_t, and the multibyte char set? [18:39] yes [18:39] this is fubar [18:39] Legendario: pass -k to the build [18:39] or DEBSIGN_KEYID= in ~/.devscripts [18:39] yes unicode in C is no fun [18:40] man problems would be solved if everything would just be utf8 :( [19:06] jtaylor, I've tried but got an error "bzr: ERROR: no such option: -k" [19:06] add it after -- [19:06] it goes to dpkg-buildpackage [19:06] bzr-buildpackage -- -k [19:11] jtaylor, cool! Worked out! :-) [19:12] jtaylor, what does the -- stand for? [19:12] its convention to indicate stop parsing for own parameters and pass the rest on to sub-processes [19:12] or treat as literal strings rather than options [19:23] jtaylor, cjwatson , awsome! :-) Is it still possible to add a package to saucy or is it already frozen? [19:24] We're pretty hard-frozen for non-essentials [19:24] But T is only six months away [19:45] Tiny Trilobyte? ;) [20:09] I could have sworn that redhat had a nice page that made it simple to see what patches they have applied to their packages, but google is being unhelpful. Anyone know what I'm talking about? === jalcine is now known as jalcine_ === funkyHat_ is now known as funkyHat === jalcine is now known as jalcine_