[06:59] <dholbach> good morning
[14:38] <Rhonda> Is there a wiki or help page on the difference between regular suite and -update suite?
[14:38] <Rhonda> And the timeline for when -update flows back into regular one?  I.e. the point releases?
[14:39] <Rhonda> Ah, I guess I found it, https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule
[14:40] <Rhonda> Are all packages in -update flowing into the next point, or are there sometimes packages getting rejected?
[15:15] <cjwatson> Rhonda: all packages in -updates go to the next point release - in fact the point release is basically a snapshot of -updates
[15:17] <Rhonda> A snapshot of -updates?  So -updates is a full suite, not just the revised packages?
[15:19] <cjwatson> Sorry, a snapshot of (release + release-updates)
[15:19] <cjwatson> -updates is a partial suite
[15:31] <Rhonda> Thanks :)
[17:09] <Legendario> hi
[17:09] <Legendario> bzr builddeb fails and says "secret key not available"
[17:09] <Legendario> but I have the key
[17:10] <Legendario> may be it is because I have multiple keys in it
[17:11] <Legendario> is there a way to specify the key?
[17:11] <Legendario> like there was in dh_builddeb
[18:14] <psusi> what is a "multi byte string"?  Does that mean UTF-8 or does it depend on your locale?
[18:19] <jtaylor> any unicode string can be multibyte
[18:19] <jtaylor> e.g there are unicode codecs with fixed size, 2, 3 or 4 byte, or variable size codecs like utf-8
[18:20] <jtaylor> utf-8 is multibyte as soon as you go beyong ascii (or latin1?)
[18:23] <psusi> 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] <psusi> 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] <psusi> 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] <psusi> I'm guessing it is UTF-8
[18:26] <psusi> or does the native code set depend on the current locale?  and some don't use utf-8?
[18:28] <jtaylor> there is utf-16 in the partition table oO
[18:28] <jtaylor> fun
[18:28] <jtaylor> I think what the C w* functions do is locale dependent
[18:29] <jtaylor> but luckyly I never had to actually use them
[18:29] <jtaylor> so can't really help you
[18:32] <psusi> 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] <jtaylor> I think so
[18:32] <jtaylor> no not utf-16, but always 2 byte
[18:33] <jtaylor> could be UCS-16 or whatever weird 2 byte encodings there are
[18:34] <jtaylor> hm no its not even defined what size it is in the standard
[18:36] <jtaylor> (4 byte on my system btw)
[18:37] <psusi> 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] <jtaylor> they get it from the locale
[18:38] <Legendario> any help up above?
[18:38] <psusi> so the locale defines BOTH the format of wchar_t, and the multibyte char set?
[18:39] <jtaylor> yes
[18:39] <psusi> this is fubar
[18:39] <jtaylor> Legendario: pass -k<keyid> to the build
[18:39] <jtaylor> or DEBSIGN_KEYID= in ~/.devscripts
[18:39] <jtaylor> yes unicode in C is no fun
[18:40] <jtaylor> man problems would be solved if everything would just be utf8 :(
[19:06] <Legendario> jtaylor, I've tried but got an error "bzr: ERROR: no such option: -k"
[19:06] <jtaylor> add it after --
[19:06] <jtaylor> it goes to dpkg-buildpackage
[19:06] <jtaylor> bzr-buildpackage -- -k
[19:11] <Legendario> jtaylor, cool! Worked out! :-)
[19:12] <Legendario> jtaylor, what does the -- stand for?
[19:12] <jtaylor> its convention to indicate stop parsing for own parameters and pass the rest on to sub-processes
[19:12] <cjwatson> or treat as literal strings rather than options
[19:23] <Legendario> jtaylor, cjwatson , awsome! :-) Is it still possible to add a package to saucy or is it already frozen?
[19:24] <cjwatson> We're pretty hard-frozen for non-essentials
[19:24] <cjwatson> But T is only six months away
[19:45] <psusi> Tiny Trilobyte? ;)
[20:09] <psusi> 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?