[01:03] <miki4242> hi all, i'm trying to fix a bug (LP: #354522) "espeak sound doesn't play correctly", which kills ubuntu speech accessibility. help is very welcome because this can be a show-stopper for people with vision problems installing Ubuntu.
[01:05] <stgraber> pochu: yes, I'll be at UDS. What about you ?
[01:05] <miki4242> i believe the problem is with portaudio v19, but i'm having problems with building a package from newer svn snapshot.
[01:20] <pochu> stgraber: me too!
[01:21] <stgraber> pochu: oh, finally :)
[01:22] <pochu> indeed :)
[01:25]  * pochu waves good night
[02:32] <Zarel> Hey, guys.
[02:32] <Zarel> How locked down is Jaunty right now?
[02:35] <JontheEchidna> No UI changes, string changes or new features
[02:35] <Zarel> Can we update minor (bugfix) versions of packages?
[02:36] <s0nix> hi
[02:36] <Zarel> Warzone 2100 has version 2.1.1 in the Ubuntu repos. -> http://packages.ubuntu.com/jaunty/warzone2100
[02:36] <Zarel> But the latest stable release is 2.1.3.
[02:36] <Zarel> Is it too late to update?
[02:37] <s0nix> Anyone could explain to me the "advantage/goal" of using this king of version number in a ubuntu package: 4:4.1.2-0ubuntu1~hardy1~ppa1 ...... especially the "hardy1" if ubuntu1 is already in it
[02:38] <JontheEchidna> Zarel: nah, not too late
[02:38] <Zarel> JontheEchidna: Oh, good. How would I go about doing that?
[02:38] <Zarel> It's fortunately already in the Debian repos.
[02:39] <s0nix> then, it should be synched, no?
[02:39] <JontheEchidna> Come the 9th it will be too late, though
[02:40] <Zarel> Yeah. How do I request for it to be synced?
[02:42] <JontheEchidna> File a bug requesting the sync from the appropriate debian repo (unstable, etc)
[02:43] <JontheEchidna> then an MOTU will look over it and subscribe the archive admins, who will sync it
[02:48] <Zarel> JontheEchidna: I don't deal with Ubuntu's bugtacker very much. Is there a guide for doing this kind of request somewhere?
[02:48] <JontheEchidna> nope, that's how it's done
[02:48] <JontheEchidna> oh
[02:48]  * JontheEchidna misread
[02:49] <JontheEchidna> just search for "please sync" in the bugs
[03:01] <Zarel> JontheEchidna: It still confuses me. "main", "universe", "multiverse"... How do I ask for it to be in Jaunty?
[03:02] <JontheEchidna> warzone2100 is in universe
[03:04] <Zarel> So if I ask "Please sync warzone2100_2.1.3-1 (universe) from Debian unstable (main)", it will go into Jaunty?
[03:09] <JontheEchidna> yeah
[03:15] <StevenK> 2.1.3 is a new upstream release, it will require an FFe.
[03:24] <Zarel> StevenK: FFe?
[03:25] <Snova> Zarel: Feature Freeze Exception
[03:25] <Zarel> Snova: But it doesn't add any new features; it's just a bugfix release.
[03:26] <Zarel> Maybe that explains all my problems. In Ubuntu, bugfixes count as features!
[03:26] <Snova> I wouldn't know...
[03:29] <StevenK> Zarel: No, you just need to explain in the sync request that 2.1.3 only fixes bugs, and doesn't introduce new features.
[03:44] <Zarel> Okay, I've submitted the report.
[03:44] <Zarel> https://bugs.launchpad.net/ubuntu/+source/warzone2100/+bug/356753
[06:48] <StevenK> ScottK: Any plans to fix havp and dansguardian with the new clamav?
[08:21] <Juli_> Hi MOTUs. Could you please explain how things go after Final Freeze? I've fixed a bug: https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/345562 and attached debdiff several days ago but still don't have sponsor. Will it be possible to upload the changes after April, 10 or FException is required? Thanks!
[08:30] <siretart_> sladen: should make no problems
[08:49] <ttx> Juli_: I'll have a look.
[08:49] <Juli_> ttx: Thanks!
[09:29] <toabctl> hi all
[09:30] <toabctl> i create a debian package (python script with setup.py) with cdbs and have a MANIFEST.in file, but in the debian package, the files from MANIFEST.in are not included. why?
[09:51] <Toadstool> hi all
[10:23] <giskard> hi *
[10:23] <giskard> i'm a OLD ubuntu-motu
[10:24] <giskard> but it's a lot of time that i don't do an upload
[10:24] <giskard> or something usefull for ubuntu
[10:24] <giskard> i don't know if there is a policy for retirment
[10:24] <giskard> do we have something similar
[10:24] <giskard> where i have to look?
[10:26] <giskard> retirement*
[10:27] <gaspa> bdmurray, there has been a pending change in harvest-data for sime time. please, could you take a look? ( I don't see dholbach ATM..)
[10:33] <wintellect> As everything is gpg signed - is there any suggestions as to how long a current key should be used? Eg. should you have keys that expire every 3 years? 5 years? never? or does it not matter?
[10:36] <slytherin> giskard: I believe there is but I don't have any link. You better mail to MOTU Council
[10:41] <slytherin> wintellect: it is personal preference.
[10:41] <wintellect> slytherin: k, thanks for clarifying :)
[10:43] <giskard> slytherin,  thank you.
[11:21] <sladen> siretart: in the, I had jpds copy the tarball back into incoming/
[11:22] <sladen> siretart: I might investigate the exact squence when the .orig is less than 10MB :)
[11:22] <sladen> siretart: and see if I can replicate it again
[11:46] <wintellect> lintian gives me errors about hyphens in the manpage needing backslashing - is it customary to fix this with a patch file in debian/patches/ ?
[11:47] <hyperair> wintellect: i should think so
[11:47] <hyperair> wintellect: but you should also submit the patch upstream.
[11:50] <wintellect> I thought that anything in debian/ was included in the diff.gz?
[11:54] <savvas> wintellect: it is, also any direct changes in the root folder of the source packages are also included :)
[11:54] <savvas> hyperair meant checking if the package is in Debian, and submitting your changes there as well
[11:57] <hyperair> savvas: no, i meant to the upstream authors of the said package. or basically whoever wrote the manpage
[11:58] <hyperair> wintellect: if it's in debian/ then fix it in debian/ directly. if it's not, then use a patch.
[11:58] <hyperair> wintellect: that's the general rule.
[11:59] <wintellect> hyperair: gotcha
[12:00] <savvas> oh
[12:00] <savvas> my mistake :P
[12:00] <hyperair> savvas: ;)
[12:02] <savvas> and excusable, I
[12:02] <savvas> I'm recovering from a 5-day cold-a-thon :)
[12:02] <hyperair> hahaha get well soon
[12:02] <savvas> thank you :)
[12:04] <slytherin> wintellect: if the man page is in debian/ directory then it is created by the packager/maintainer in Debian. In that case you need to modify it directly. The patches in debian/patches directory are for the source provided by upstream not for the files in debian/ directory.
[12:05] <wintellect> slytherin: yeah. It's in the main source so I'll need to use debian/patches
[12:06] <wintellect> any suggestions for a good patchfile name - it's backslashing hyphens in the manpage
[12:06] <wintellect> ?
[12:06] <wintellect> manpage_backslash_hyphens.patch
[12:06] <wintellect> ?
[12:06] <wintellect> that too long?
[12:07] <slytherin> wintellect: fix_man_page.patch and with appropriate number prefix.
[12:07] <savvas> wintellect: which package is it?
[12:08] <slytherin> wintellect: then explain it in changelog what you actually fixed. Also if the patch system is dpatch then the patch header should contain some description.
[12:10] <wintellect> just using plain old "patch"
[12:11] <wintellect> slytherin: if it's the first patch, should it be: 0_fix_man_page.patch or 1_fix_man_page.patch ?
[12:11] <savvas> I like to use 10-fix_man_page.patch :)
[12:12] <wintellect> savvas: tmux. It's not a complicated pkg but saw a needs-packaging bug and wanted to give it a go
[12:12] <wintellect> the pkg itself already builds and works - just tidying up for lintian, etc
[12:12] <slytherin> wintellect: which patch system does it use? dpatch reserves prefix 00 for the file that contains patches to be applied. apart from that starting with 01 is better (note 2 digits).
[12:13] <savvas> wintellect: even if it's the first patch, using a higher number gives other people more options if say it needs to be patched later on
[12:13] <wintellect> savvas: gotcha
[12:14] <wintellect> slytherin: none as far as I can tell. It's never had a patch applied. Is it ok to use plain old "patch -u" ?
[12:14] <slytherin> savvas: I don't understand your comment.
[12:16] <slytherin> wintellect: I am not sure how that would work. You canread about patch systems here - https://wiki.ubuntu.com/PackagingGuide/PatchSystems
[12:16] <wintellect> slytherin: I took savvas to mean if you start at "10" then people can apply earlier patches later by giving them a number lower, eg "05"
[12:16] <savvas> slytherin: maybe a patch in the future needs to be done before another patch, so if it's 10-fix_manpage the current, and they add 05-some_patch, 05 would be taken before 10, isn't that right?
[12:17] <savvas> woops, I just realised we use series for patching systems :)
[12:17] <hyperair> you mean quilt.
[12:17] <slytherin> savvas: but why would be a patch in future need to be done before this patch. And even if it did, you can always use alphabetical order.
[12:18] <slytherin> savvas: and if you are using dpatch or quilt you can define any order you want.
[12:19] <savvas> I think that's my queue to stop giving advice to people until I get better :P
[12:20] <technologiclee> #ubuntu+1 suggested this channel - and that i file a request at launchpad: https://answers.launchpad.net/ubuntu/+question/66717    any further suggestions?
[12:24] <wintellect> slytherin: If I were to use dpatch, how do I generate the patch file with the differences in it? Do I need to use dpatch for this? Or just generate a standard "diff -u"?
[12:24] <hyperair> daptch-edit-patch
[12:24] <slytherin> wintellect: have you read the page I pointed you? It has decent explaination about all three patch systems.
[12:25] <slytherin> technologiclee: if there is no source available how do you expect anyone to add it to repositories?
[12:25] <wintellect> slytherin: I did, and the entry about dpatches only shows how to apply patches
[12:26] <andol> cjwatson: Ok if I ask a question regarding you comment on bug #355800:
[12:26] <andol> This report is public
[12:26] <technologiclee> the source is available from Nanorex - with an account request - does listing in Sourceforge mean that anyone can develop it further? - it is supposed to be 'open source'
[12:26] <slytherin> technologiclee: if it is open source why does it require an account to download?
[12:27] <technologiclee> i don't know that is the way they do it but it claims GPL liscence - i believe
[12:28] <wintellect> hyperair: thanks. The man page told me all I needed to know :D
[12:28] <hyperair> wintellect: =)
[12:28] <wintellect> I didn't know dpatch created a copy of the directory too :D
[12:28] <hyperair> i prefer quilt
[12:28] <slytherin> wintellect: Ok. Here is a short note. When you do dpatch-edit-patch name.patch it will create a temporary copy of the source where you can edit file you want. when you type 'exit' and enter you have the patch created. Then add the patch name to debian/patches/00list. You will also need to do some changes to your debian/rules file for patching/unpatching.
[12:29] <slytherin> hyperair: quilt is confusing for new developers.
[12:29] <wintellect> Do you have to be in the root of the src directory when you call dpatch-edit-patch?
[12:29] <slytherin> wintellect: yes
[12:29] <hyperair> slytherin: what's so confusing?
[12:29] <wintellect> slytherin: Thanks! Makes perfect sense now :D
[12:30] <slytherin> hyperair: did you try it when you were new to packaging? :-)
[12:30] <hyperair> slytherin: no, i used cdbs-edit-patch.
[12:30] <hyperair> slytherin: after that i switched to quilt.
[12:30] <hyperair> slytherin: i think dpatch is redundant.
[12:31] <slytherin> hyperair: I tried all three and the packages that used quilt were last on my list. :-)
[12:31] <hyperair> slytherin: i use quilt on all of the packages i maintain =)
[12:31] <slytherin> now it doesn't matter to me what system the package is already uses. But if I am adding a new system then cdbs, dpatch, quilt is my order of preference.
[12:32] <hyperair> slytherin: i liked being able to quilt refresh
[12:32] <slytherin> technologiclee: tell them to make it available without account and then file a bug with tag 'needs-packaging'.
[12:32] <technologiclee> awesome - thanks
[12:36] <cjwatson> andol: yes, what about it?
[12:47] <andol> cjwatson: Regarding marking version depency. From what I can see the --debconf-ok option depends on >= 0.28, while even dapper hade ucf 2.0. Is it really neccesary to mark such a trivial/old dependency.
[12:47] <andol> cjwatson: Not that I mind, since there is already the patch. I'm more curious on a general level.
[12:48] <directhex> the GPL doesn't prevent you from putting your code behind a passworded page - it also doesn't prevent other people redistributing it without said impediment
[12:52] <cjwatson> andol: it's probably not all that important but since I feel you ought to remove the incorrect --debconf-ok from the postrm anyway, and edit the changelog, syncing up with the rest of the Debian change does no harm
[12:53] <cjwatson> andol: I wouldn't have asked you to go back round just for that
[12:53] <ttx> Juli_: libnb-platform-java sponsored/uploaded, i'll do netbeans when libnb-platform-java will be published.
[12:55] <andol> cjwatson: I agree. Just wanted to know for future cases. Thanks for explaing. I'll try to do my homework better next time.
[13:09] <slytherin> directhex: right, how many packagers will be willing to download a source which requires registering?
[14:26] <alexander_> hy, I'm needing help to packing a software
[14:26] <alexander_> someone could help me?
[14:27] <alexander_> someone could help me?
[14:28] <alexander_> I have a problem to create a package .deb
[14:30] <alexander_> could someone help me with pbuild ?
[14:30] <mok0> DktrKranz: ping
 pong
[14:32] <mok0> huh?
[14:32] <alexander_> could you help me with a pbuild ?
[14:32] <mok0> !ask | alexander_
 Sorry
[14:33] <hyperair> lol ubottu's a bot.
[14:34] <mok0> hehe
[14:34] <hyperair> =p
[14:34] <mok0> hi hyperair
[14:34] <hyperair> hi mok0
[14:34] <hyperair> long time no see =p
[14:34] <mok0> hyperair: yeah, I've been busy doing other stuff
[14:34] <hyperair> mok0: hahah same here =p
[14:34] <hyperair> mok0: also i'm waiting out feature freeze =p
[14:34] <mok0> hyperair: yep
[14:35] <mok0> hyperair: how are your apps doing in jaunty?
[14:36] <hyperair> mok0: fine fine
[14:36] <mok0> great
[14:36] <hyperair> mok0: just that there's a new version of codelite, geanyvc, and geanyproj, all of which appeared after FF
[14:36] <hyperair> i mean after FF started.
[14:36] <mok0> ah. They can go in karmic
[14:36] <hyperair> yep
[14:37] <hyperair> i'm trying to get codelite into debian, but after a looong while, a sponsor appeared, and i think he's busy, so he'll take some time to look at it
[14:37] <slytherin> alexander_: no one can help you unless you state the question
[14:37] <directhex> Subject: 	Your Oxford Bus the Airline Booking Confirmation
[14:37] <mok0> hyperair: it does take extremely long to get something into Debian
[14:38] <mok0> hyperair: best bet is to become part of a team
[14:38] <alexander_> I'm packing a software. And I'm having problem to create system user
[14:38] <hyperair> mok0: yeah, but there isn't really any team for c++ apps/libs right?
[14:38] <mok0> hyperair: hmm, I don't know...
[14:39] <hyperair> mok0: also, regarding sigx's FTBFS, it magically fixed itself after i got the upstream author to fix his code, but without me attempting to get another upload in
[14:39] <directhex> alexander_, you want your package to create a new user on installation?
[14:39] <slytherin> My best experience is when one Debian developer asked my what was stopping me from porting a package updated in Ubuntu to Debian. He helped me all the way through clearing the NEW queue. :-)
[14:39] <alexander_> Yeah
[14:39] <hyperair> mok0: sigx ftbfs'd on everything non i386,amd64,lpia that time
[14:39] <slytherin> alexander_: how are you doing it?
[14:39] <alexander_> I need my package create a system user
[14:39] <mok0> hyperair: heh. Perhaps it was due to a missing dep?
[14:39] <hyperair> mok0: no, there was some weird compilation error.
[14:40] <hyperair> mok0: i think the dep was there, but something changed in one of the deps
[14:40] <alexander_> I'm adding in the debian/rules the commands to create user
[14:40] <directhex> alexander_, wrong.
[14:40] <directhex> alexander_, debian/rules is a makefile, executed at package compile time
[14:40] <alexander_> hmm
[14:40] <mok0> alexander_: take a look at some other package that creates a a user
[14:40] <directhex> alexander_, debian/rules is never installed or executed on an end-user's system
[14:41] <hyperair> mok0: something regarding g_atomic_pointer_set.
 hmm
[14:41] <mok0> hyperair: perhaps the compiler chain was updated?
 So How can I do it ?
[14:41] <hyperair> mok0: perhaps.
[14:41] <directhex> alexander_, postinst.
[14:41] <slytherin> alexander_: I believe you will need to do it in postinst file. You can take a look at how apache package does it.
[14:41] <directhex> alexander_, download the ntp source package, look in debian/ntp.postinst
[14:42] <directhex> alexander_, ntp is a very simple example package for you
 oh thanks
 hmm , thanks
 I'll download the source ntp code
[14:43] <mok0> alexander_: alternatively, go into /var/lib/dpkg/info and do a grep grep adduser *postinst
[14:43] <directhex> that works
 thanks
[14:44] <mok0> alexander_: np. Good luck
[14:45] <alexander_> thanks to all
[14:53] <wintellect> what goes in the "XSBC-Original-Maintainer" field in the control file - the maintainer of the source? Ie. who wrote the app?
[14:55] <hyperair> wintellect: no, the original maintainer of the debian package
[14:55] <hyperair> wintellect: i.e. the maintainer in debian, or you.'
[14:55] <hyperair> wintellect: for stuff entering ubuntu through revu, Maintainer says MOTU, and XSBC blah blah says you
[14:55] <maxb> wintellect: The Debian maintainer, for a source synced from Debian. You can, and probably should, omit the field entirely if its not a packaging synced from elsewhere.
[14:56] <hyperair> maxb: don't you mean merged?
[14:56] <maxb> uh, yes, yes I do :-)
[14:57] <wintellect> hyperair: maxb: it's not from Debian, it's my own work. So, do I omit the field or put my name?!?
[14:57] <hyperair> =)
[14:57] <maxb> wintellect: You're allowed to do either
[14:57] <hyperair> wintellect: generally for stuff entering through revu i put my own name.
[14:57] <wintellect> ok
[14:57] <wintellect> thanks
[15:05] <DktrKranz> mok0: timeout error :)
[15:07] <hyperair> heheh
[15:07] <hyperair> maybe he set his TTL really high you know? =p
[15:09] <DktrKranz> hyperair: yeah. my T1 is still experimental :)
[15:09] <hyperair> DktrKranz: hahah =p
[15:10] <DktrKranz> I've a videoconference call next thursday to fix it
[15:10] <DktrKranz> so I can go 2Mbyte/sec :)
[15:10] <DktrKranz> my bad I can only dowload intercompany files, no P2P or packages ;)
[15:11] <hyperair> meh lucky you
[15:12] <hyperair> i can go... at around 1Mbye/sec for some streaming sites, but i think that's some transparent proxy cache thing going on
[15:13] <hyperair> on the other hand, the ubuntu mirror here goes at 10MB/s
[15:13] <hyperair> =D
[15:13] <hyperair> the one maintained by me on the campus of course
[15:19] <DktrKranz> hyperair: heh, my DSL at home goes at 30Kb/sec :/
[15:21] <directhex> my bus to heathrow is booked
[15:22] <hyperair> DktrKranz: mine goes at 50kB/s at home.
[15:29] <bddebian> Heya gang
[15:29]  * hyperair yawns
[15:30]  * mok0 yawns
[15:30] <Pici> boo
[15:30] <hyperair> hehehe
[15:30] <mok0> It's contageous :-)
[15:30] <Pici> I keep mistaking this channel for -bugs.
[15:30]  * hyperair whois's bddebian
[15:30] <hyperair> ooh bdefreese!
[15:31] <hyperair> remember me? =p
[15:31] <bddebian> heh
[15:31] <bddebian> hyperair: Sure :)
[15:31] <hyperair> =D
[15:43] <tzn> hi there
[15:44] <tzn> what is the best way to patch a package, that doean't ahve any patches yest
[15:46] <slytherin> tzn: is the package from Debian? if yes then don't introduce the patch system. If the package is from ubuntu (i.e 0ubuntuX version) then you are free to introduce patch system.
[15:49] <incorrect> I am packaging zabbix 1.6.4 and got dpkg-buildpackage: failure: dpkg-source -b zabbix-1.6.4 gave error exit status 1
[15:50] <RainCT> incorrect: look some lines above that for the real error message
[15:50] <incorrect> dpkg-buildpackage: failure: dpkg-source -b zabbix-1.6.4 gave error exit status 1
[15:50] <incorrect> that i guess
[15:51] <incorrect> dpkg-source: unrepresentable changes to source
[15:51] <RainCT> incorrect: OK, so you've added/modified some binary file
[15:54] <incorrect> possibly
[15:54] <incorrect> basically i took the source code from zabbix.org and the diff file from the package of 1.6.1
[15:54] <incorrect> i should remove the patches that have been applied too
[15:55] <GuyFromHell> By something being assigned to me, does it suggest that I should have the ability to merge it as well? or just fix the bug?
[15:56] <hyperair> fix the bug.
[15:56] <hyperair> basically it means you're working on it
[15:56] <hyperair> if you're not, unassign yourself
[16:00] <GuyFromHell> hyperair, alright, thanks.
[16:01] <hyperair> GuyFromHell: you're welcome
[16:03] <incorrect> thanks! sorted!
[16:03] <james_w> RainCT: I gave you wrong information earlier, sorry
[16:11] <tzn> thanx slytherin
[16:25] <ttx> Juli_: netbeans sponsored/uploaded
[16:25] <Juli_> ttx: Thanks a lot!
 hy, thanks for help. I made my package
 Thanks for help, my package is donne :)
[17:15] <Laney> gah
[17:15] <Laney> I keep thinking you're pasting peoples lines, alexander_
[17:16] <lfaraone> Laney: he isn't? :)
[17:16] <Laney> nope, those are replies
[17:16] <alexander_> lanay, I think too
[17:17] <alexander_> sorry , I'm new in roons like this
[17:17] <alexander_> bye
[17:17] <Laney> whoops
[18:12] <goshawk> i'm packaging a compiler for a programming language, this compiler (call it project A) needs a runtime library (static library) which is a separate project (call it project B). To create project A i need the sources of B too and compile them all together. Project B is a static library and it's unuseful without project A. How should i package it? just packaging the project A alone?
[18:12] <goshawk> or should i package project B too, from the same sources of project A?
[18:57] <quadrispro> hi guys
[19:03] <pochu> hi quadrispro
[19:03] <quadrispro> hi pochu
[19:35] <marrow> Hi
[20:45] <defcon> n8
[21:40] <habtool> How does one go about finding someone to package a program into a deb for inclusion in ubuntu? I am a user of the program, not the developer.  Its one of the only tools that can backup and restore a ext4 partition (similar to partimage, but cli only) Partimage does not support ext4. http://www.fsarchiver.org/Main_Page
[21:41] <jpds> habtool: File a [needs-packaging] bug for it at bugs.launchpad.net/ubuntu/+filebug
[21:41] <lfaraone> habtool: you either A) find someone who knows packaging to do it for you, B) learn packaging and do it yourself, or C) hire a consultant. :)
 I can run it from the /home/bin folder, it is more for other that may want to use it, not for me as such ;)
[21:43] <lfaraone> habtool: packaging isn't terribly difficult, if you want you could do it in a few hours.
[21:43] <habtool> partimage is great but no longer developed :(
[21:43] <jpds> habtool: See: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
 Ok, will have a look
[21:52] <maxb> habtool: <someone'snick> usually means you are quoting them, not replying to them
[21:55] <habtool> maxb: Sorry was just coping the names in xchat. Now know for future reference.
[21:56] <maxb> Instead, try typing the first few letters, then tab complete
[21:58] <habtool> maxb, thanks, that works great :)
[23:02] <goshawk> i'm packaging a compiler for a programming language, this compiler (call it project A) needs a runtime library (static library) which is a separate project (call it project B). To create project A i need the sources of B too and compile them all together. Project B is a static library and it's unuseful without project A. How should i package it? just packaging the project A alone?
[23:02] <goshawk> or should i package project B too, from the same sources of project A?