[00:44] well I got 2/4 'major' commits done. [05:46] so would https://bugs.launchpad.net/ubuntu/+source/ecere-sdk/+filebug be the proper place where to file each of these bugs that this SRU will target? [05:46] yes [05:48] So I got the 4 crucial bugs cherry-picked. [05:48] I just need to see how many of the 40 others I want to get done :S [05:49] I got 13 marked in red already :| [06:05] now I'm going to be fixing the debian packaging as well in a separate branch... Should I add a new changelog entry? [06:06] I see this https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging for versioning scheme [06:08] yes [07:27] why's mysql-workbench 'main' and not 'universe' or otherwise? if you know... [07:39] good morning [07:39] hi there :P [07:44] TheLordOfTime: mysql-workbench: 500 http://ru.archive.ubuntu.com/ubuntu/ raring/**universe** i386 Packages [07:44] guten morgen dholbach! [07:45] привет mitya57 :) [07:47] dholbach: we've been doing some u-p-g fixes yesterday (but for some reason the website is stuck on r255) [07:49] mitya57, why does apt-cache show otherwise? [07:49] o.O [07:49] * TheLordOfTime checks apt-cache [07:49] * TheLordOfTime facedesks [07:50] mitya57, let me check [07:53] note to self: don't try and ask questions at 3AM :/ [08:00] mitya57, the file on disk on the server has r265 which is in line with what's in the ppa [08:00] mitya57, some of the content on dev.u.c is going through a cache, so maybe it's a caching issue? *shrug* [08:01] $ wget http://developer.ubuntu.com/packaging/html/index.html -qO- | grep '~bzr' [08:01] VERSION: '0.3.1~bzr255~quantal1', [08:01] Version: 0.3.1~bzr255~quantal1. [08:01] yes [08:01] 255 != 265 [08:01] I realise that [08:02] ah, do you mean server-side cache? [08:02] yes [08:02] o [08:02] *ok [08:02] I'll ask the IS folks [08:02] thanks a lot for your work on this [08:03] mitya57, ru.po is at 64% so getting very close :-) [08:04] dholbach: I've sent a call for translations to ubuntu-l10n-ru@lists.u.c, but *only one* new string got translated after that :( [08:04] and as usual I have not time to do that myself :( [08:04] sure, I understand [08:04] we'll see how it goes :) [08:06] maybe more translators will get an e-mail if I file a bug and assign ~launchpad-l10n-ru there, but this sounds a bit agressive to me [08:07] I'm sure we'll get there :) === almaisan-away is now known as al-maisan === yofel_ is now known as yofel [10:37] I got this done: https://github.com/ecere/sdk/commits/quantal_sru =) [10:37] 'morning dholbach :) [10:38] Hello there I am trying to make a daily build recipe on launchpad and It keeps on failing but does not fail at all when I run local [10:39] it is saying that bzr is not loged in [10:39] https://launchpadlibrarian.net/129732948/buildlog.txt.gz [10:41] recipe is http://paste.ubuntu.com/1580322/ [10:41] thanks for taking some time to look at this for me [10:47] bobweaver: looks like not your fault, try to ask on #launchpad [10:47] thanks mitya57 === ziviani is now known as Guest13377 === Guest13377 is now known as ziviani [10:57] Which format should I use for bug patches on LP? [10:57] And my multiple-bug SRU should still be split up in multiple patches, right? (one for each bug, but I can point to all the bug in the same SRU? Should one of the bugs 'be' the SRU?) [11:00] ESphynx: For the multiple-bug SRU. Yes, we can remove those patches in case of a new upstream release is bought into the Ubuntu repositories [11:01] ESphynx: We will know which patch to remove and which (distribution-specific) patch to kepp :) [11:05] well all of these patches are Quantal specific [11:06] ESphynx: hmm, it will still be safe to keep them different [11:07] ESphynx: Because a new version can also be backported [11:14] hmm would a bazar branch work? [11:14] i.e. a specific revision? === al-maisan is now known as almaisan-away [13:30] there :| 14 bug reports filed .... https://bugs.launchpad.net/ubuntu/+source/ecere-sdk [13:30] I will try to improve on these tomorrow... Could they all please be targeted to Quantal? [13:35] what should I put the status of these SRU bugs to? Fix Committed? [13:36] ESphynx: For SRUs, In Progress = uploaded waiting review, Fix Committed = in -proposed, Fix Released = in -updates [13:37] So In Progress then? :) (that's what I've been setting them to) [13:37] thanks [13:37] if someone has uploaded them [13:37] I'm linking to the bzr revision [13:37] https://launchpad.net/ubuntu/quantal/+queue?queue_state=1&queue_text= [13:37] I don't think they hve been uploaded [13:38] you probably want Confirmed [13:38] on the Ubuntu task at least [13:38] ah [13:38] they have to be uploaded there? [13:38] yes, once uploaded they enter that queue to be reviewed by the SRU team [13:39] there should be something to say the bug has been fixed and the patch is available :| [13:42] if you want it to be uploaded then subscribe the sponsor team [13:43] ESphynx: there is something to say a patch is available. Attach a patch / link a branch [13:43] or even better, close the bug, with a new upload into the development release [13:43] in the status, I meant tumbleweed :P [13:44] close the bug? I just went through all this trouble opening these 14 bugs :P [13:44] in that case, link the bugs to the upstream project. You can use your project's statuses however you like [13:44] tumbleweed yeah but this is specific to an SRU :P [13:44] SRUs can't be accepted into stable releases until they've been fixed in the development release [13:44] I have my own tracker on ecere.com/mantis/ :P [13:44] tumbleweed: these bugs are all fixed in the development release [13:45] LP can deal with external bug trackers for upstreams [13:45] ESphynx: then they should be marked as being fixed in the development release, that' seasy [13:45] tumbleweed: is it? [13:45] these bugs I filed I strictly for the SRU [13:45] are* [13:45] once the nomination for Quantal is accepted you'll have two entries [13:47] why 2 entries? [13:48] one for the development release and one for quantal [13:48] set the development release one to Fix Released because it is fixed there [13:48] but they're not issues in the developemtn release [13:48] they're only isues in Quantal [13:49] in otehr words they've been fixed in the development release [13:50] they've been in a totally non-Ubuntu related way. [13:50] that's totally normal [13:50] right. [13:55] micahg: Please take a look @ https://bugs.launchpad.net/ubuntu/+source/ecere-sdk/+bugs when you have a chance [14:02] well, good night gus [14:02] guys* [14:22] ESphynx: it can be raring=invalid quantal=confirmed if that makes it easier to understand that bug affects quantal only. [16:41] http://packages.ubuntu.com/search?suite=default§ion=all&arch=any&keywords=freeze.py&searchon=contents [16:41] No contents information available for this suite [16:45] xnox: I see a few of them with apt-file [16:48] yeah, if one goes to http://packages.ubuntu.com/freeze.py and then first clicks raring, and then switches to contents - they appear. === funkyHat_ is now known as funkyHat === almaisan-away is now known as al-maisan [20:22] if i want to package some source files (in, /usr/share/doc/mypackage/examples/source.gz), how does one do that? [20:29] kdub: http://man.cx/dh_installexamples [20:30] thank you kindly siretart === jackyalcine_ is now known as jalcine === al-maisan is now known as almaisan-away === jalcine is now known as JackyAlcine === matttbe_ is now known as matttbe