I was am, dunno * cb400f wonders if the zenworks-yast team knows.. mrpudding: ok, so one question to start. How many ppl is the zen team working in this stuff? no zenwork ... need a managed station plugin in yast then make the package manager really use zmd , add a filter for box you wanna use and your in affair what Id like to see is those ppl flying to nurenberg, working in the same office as ppl doing the yast module <_Marcus_> aka_druid_: they did for 2 weeks ;) to fix up for release as nothing was working ... * countryroad (n=countryr@125.92.18.244) has joined #opensuse _Marcus_: no, I mean for 8 months yup, AJ mentioned that in the status meeting.. seems a lot of progress was made <_Marcus_> aka_druid_: well, that might be too hard _Marcus_: all handcuffed one to another til they get sick of seeing each other :) * countryroad has quit (Remote closed the connection) maybe it would be better flying some of the Nürnberg devs to US.. talk some sence into the Novell suits .. _Marcus_: cmon, theres cheap erdinger in there. Id go without thinking twice cb400f: novell suits have that reputation... !ned <_Marcus_> nuernberg has better beer than erdinger ;) ned is Novell Entropy Dept * JernejL has quit (Connection timed out) * _jdanield has quit (Remote closed the connection) ok, guys stay tuned for a pictorial explanation http://www.natbudin.com/package-management-in-code10.png mrpudding: very nice, and very helpful * mrpudding bows I see :) * bill-barriere looking * }-Tux-{ has quit ("kampf-chameleon") mrpudding: are the data files in /var/lib/zmd serialized .net objects or something? benJIman: yeah, some of them are snorp: unfortunately means every time they're corrupted one can't fix them with a text editor benJIman: the most significant one is the sqlite database (the diamond over on the right) which wouldn't be a problem if they wern't frequently corrupted benJIman: sure, but I've never seen one get corrupted... benJIman: this stores 99.9% of the data you care about benJIman: you can edit it using sqlite3 mrpudding: the sources list appears to just be serialized to file though unless i'm wrong yeah, it is benJIman: you've seen that become corrupted? yes several times a week benJIman: not a very high risk for corruption in that one, IMO seriously?! I have to re-add them all whoa benJIman: is it reproducable? are you sure that's not corruption of the zmd.db causing those sources not to show up? I have honestly *never* seen that file get corrupted yeah, me neither snorp: well it happens at random times, probably one of the repositories triggering something odd I suppose presumably it's something in zmd itself that writes that? benJIman: what are the symptoms of this corruption snorp: clients don't see any of the sources any more, they are clearly there visible catting the file and it won't add any new until deleted the file benJIman`: hmm, crazy never seen that while you knowledgable people are here how can one regenerate the product id in /var/lib/zypp/db/products? benJIman`: what does it do when you try to add a new one then? benJIman: next time that happens, could you file a bug and attach your sources file to it? snorp: gives an "informative" error like unable to add repository * ced117 has quit (Remote closed the connection) oh damn, I leave for 5 secs and you are all talking agian humpf I will make a note next time and see if I can add a trace or something * ced117 (n=ced117@2001:5c0:8fff:fffe:0:0:0:49e3) has joined #opensuse benJIman`: yeah, please file a bug next time benJIman: incidentally, do you know about the debug settings in zmd? benJIman`: running with with --debug might give more info too s/with/rug/ mrpudding: they what generate the 10gb logfiles? :) benJIman`: rug set log-level debug ; rug set log-exception-traces true benJIman`: no, that's libzypp generating the 10gb logfile no matter what :) re my above question about product id, this isn't generated upon upgrading from previous version or using custom made cds, or even with the addon cd it appears * hanni (n=Olaf@p548CF07E.dip.t-dialin.net) has joined #opensuse and I can't find a way to re-generate it so online update configuration won't work, people would have to know the exact url for update server benJIman`: yeah, no idea about that one, you'd have to ask one of the libzypp developers .. ho yeah 9gig log file seen some of those ... evil mrpudding: mind if I set a wiki page with taht pic, where we could track the situation, suggestions? Or you ppl already have something. That would be quite informative for lots of ppl bill-barriere: actually, the excessive logging should also be somewhat reduced by aj's new patch * save_ has quit ("Konversation terminated!") aka_druid_: ok, just make sure to copy it onto the wiki server, because I probably won't be keeping it on my personal web space ok well that zen-updater thingy ??? remove it just leave an applet to track patch then yast need connect directly to zmd zen-installer zen-remover zen... wtf do a diff on the source files for zen-updater zen-installer and whatever the other one is, most amusing mrpudding: that yast package managemnt goin straight to libzypp doesnt feel right aka_druid_: yeah, personally, I'd like to be able to remove the big curvy arrow on the left and replace it with an arrow right down to zmd * symtab (n=symtab@193.230.207.150) has joined #opensuse hello mrpudding: why does yast start zmd, for syncing sources? does it actually add every source twice? benJIman`: yeah, when you tell yast to add a source, it runs "rug service-add ..." itself any ideas why php doesnt link with -lxcrypt when compilling on a system that has libxcrypt instead of libcrypt? in suse can you install closed source programs by accident? there's no equivalent command for yast, so it's harder for zmd to sync back symtab: hmm.. ask in #suse aka_druid: ok thanks jhenn: you asked earlier and were answered, do you have a point ? jhenn: ask in #suse too heh it shouldnt need to sync back indeed adding things twice is insane as it takes so long anyway yeah, I agree, if yast was just frontending straight to zmd we wouldn't need to deal with this syncing nonsense * snowglu (n=christia@p549416C1.dip0.t-ipconnect.de) has joined #opensuse the syncing is 90% of the problems imo theres a very small page for zmd where we could put that http://en.opensuse.org/Zmd using one or the other is much more reliable nod mrpudding: is there any configuration option to turn off syncing or is it hardcoded? ok, ppl stay tuned in http://en.opensuse.org/Zmd benJIman`: I've looked and haven't found one, I think it's probably hardcoded in yast except for the resolver problems and they mainly seem to effect rug/zen-updater, havn't had problems with yast yeah, I think a lot of those problems will be worked out with aj's patch and other upcoming patches like snorp said, the zmd+zypp integration isn't really mature yet just as a sidenote, zmd is also the management daemon in ZENworks Linux Management 7, where it uses a different backend - libredcarpet - and in general is much faster and reliable with that mrpudding: I hope that making it mature means abandoning the way its done now and putting the proper front end to ayst and not the dual stuff me too also the helper thingy ? thats an additional useless stage cant that alredy be done by zypp lib itself * TL_CLD has quit (Remote closed the connection) bill-barriere: actually, there is a good technical reason for that one mono ? bill-barriere: libzypp is written in C++ urg not C linking non-C++ code against C++ code is very difficult due to ABI instability and name mangling and all that good stuff writing zmd in mon wasnt right :( that should be in good old c++ too well, some of us wanted to use ycp but it didn't work out bill-barriere: maybe. writing libzypp in C++ was definitely not right, it should have been C * _Iznogood_ (n=Iznogood@80.239.63.140) has left #opensuse * apokryphos installs patches ... no its mono the problem dont put it on c++ bill-barriere: well have to get mono to talk to it mrpudding: meh, may I ask your name, for the credits? need a c++ compiler for mono bill-barriere: actually, if you look at the output of top while running rug, you'll see very high cpu usage from the C++ components and none from zmd (the mono component) bill-barriere: so I don't think that's correct aka_druid_: sure, my name is Nat Budin ok thx mrpudding: it's parse-metadata and update-status and query-system which are the killers benJIman`: right, those are written in C++ and linking to C++ code mmmm * save_ (n=mseiwert@c152177.adsl.hansenet.de) has joined #opensuse those are indeed annoying there's a lot of optimization that could be done on libzypp that hasn't been yet dunno how to add the pic heh aka_druid, there is a image page somewhere to upload thingy it's a brand-new library, so I'd expect to see some serious optimization done on it for 10.2 * ced117 has quit ("leaving") bill-barriere: link me! * benJIman` needs to sleep right now, the general idea has been that it's best to get the functionality working right first, and then we can optimize thanks mrpudding and snorp for clarifying things mrpudding: keep talking. Ill add the info you and _Marcus_ gave us in there, I hope benJIman`: no problem! benJIman`: np <_Marcus_> i actually saw update-status wasting quite some time on the dvd9 packages file !sleep sleep is for the tired http://en.opensuse.org/Special:Upload and snorp * KevManU has quit (Remote closed the connection) yup, very enlightening :)