Re: w32codec updated
2012/8/14 Artur Frysiak wi...@pld-linux.org: Zanim Bartek dostanie ponownie RW to myślę, że osoby które dają mu +1 powinny robić review jego kodu. Czyli mamy rozumieć, że sięgająca ponad rok historia podsyłanych patchy jest niewystarczającym probierzem? Chyba te kilka osób dających +1 już taki review zrobiło, bo niby że co, na złość wam te głosy poparcia były? Po pewnym czasie, gdy patche Bartka nie będą powodować problemów Bartek mógłby dostać RW. A jakieś problemy powodują, że mają je przestać powodować? Jak już pisałem, patche były podsyłane przez ponad rok. Niezbyt mi się chciało grzebać w archiwum żeby sprawdzić ile dokładnie wynosił ten okres czasu. Jak ci to jest mało, to weź jasno napisz ile wg ciebie to jest dobry czas, zamiast robić podchody jak panna na wydaniu. 20 lat starczy? A może 30? Taką samą procedurę można wprowadzić dla wszystkich zainteresowanych aby ich poprawki znalazły się w dystrybucji. Zgoda, pod warunkiem że zasady będą działały wstecz. Kilku takich co ma RW powinno być objętych rygorystycznym code review, bo same bomby sadzą. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: w32codec updated
2012/8/15 Artur Wroblewski wrob...@pld-linux.org: Czyli mamy rozumieć, że sięgająca ponad rok historia podsyłanych patchy jest niewystarczającym probierzem? Nie. To się określ czy 20 czy 30 lat wystarczy. Masz po prostu przestac rznac glupa. Chyba ty. Jedna osoba wczesniej zasugerowala, ze Bartek powinien wykazac sie konkretna inicjatywa. Druga wlasnie zaproponowala jak ta inicjatywa moglaby wygladac. A trzecia te sugestie olała. YPB? Jak grochem o sciane. Jak śliwka w kompot. Jak widzisz ludzie ciagle sa dosyc otwarci. Moje obserwacje są zupełnie rozbieżne z suponowanymi przez ciebie. Zaproponuj z Bartkiem jakas formule wspolpracy i skonczmy z ta brazyliana. http://sjp.pwn.pl/szukaj/brazyliana Propozycja jest następująca: rupcia dupcia salcesonik heloł beloł w dupę słonik. (Jak nie rozumiesz użytej gwary to mi bardzo przykro, ale trzeba było samemu najpierw nie zaczynać z lokalnym słownictwem.) wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: w32codec updated
On Wed, Aug 8, 2012 at 1:43 PM, Caleb Maclennan ca...@pld-linux.org wrote: Which brings us to the next problem. This user has been banned from the development lists for bad behavior, in particular a consistent series of posts that people felt were trolling and non-constructive. Since being on the devel lists is a requirement for all developers, this seems like a show stopper for repo access until such a time as it is resolved. I just thought about one funny thing. http://lists.pld-linux.org/mailman/pipermail/pld-discuss/2012-June/019503.html If shadzik is unable to regain CVS RW access due to his inability to be on the development list, I think it's only fair that arekm also should lose his RW access due to reasons in the linked mail. CVS admins, do your duty. One way or another. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: w32codec updated
2012/8/8 Piotr Budny piotr.bu...@gmail.com: Ponieważ Bartek cały czas jest żywotnie zainteresowany rozwojem dystrybucji i aktywnie przyczynia się do wprowadzania zmian, proponuję Z mojej strony +1. +1 +1 Bartek, wyślij nazwę użytkownika oraz skrót hasła do cvsadmina (oczywiście, jeśli chcesz otrzymać RW). Procedura z grubsza opisana tu: http://pl.docs.pld-linux.org/devel_cvs_wstep.html Dodatkowo polecam przeczytać: cvs::PLD-doc/devel-hints-en.txt Pamiętaj, że obowiązkiem każdego developera jest bycie zapisanym na listy dyskusyjne (http://www.pld-linux.org/DevelopingPLD#head-4f6f98c0b6d69bfe453200f538c2374c39f83c08). W razie problemów pytaj. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: w32codec updated
2012/8/8 Paweł Gołaszewski bl...@pld-linux.org: Żartujesz, tak? Bo się ciebie nie zapytał najpierw o pozwolenie? Przecież on sam zrezygnował Podobnie jak mkochano, co ci zupełnie nie przeszkadzało w słaniu mu zaproszeń: http://www.mail-archive.com/pld-devel-pl@pld-linux.org/msg16583.html wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: w32codec updated
On Wed, Aug 8, 2012 at 1:43 PM, Caleb Maclennan ca...@pld-linux.org wrote: First of all, the user you are suggesting for RW access previously had such access and voluntarily dropped it, publicly resigning from the project. Search the mailing list archives for mkochano who also dropped his RW access, also sent a number of patches to the list afterwards and was asked many times to send the password hash, so he would regain his access. sense. For a user who has previously resigned, I think we need something else. Very nice. Creating new rules when the old ones do not fit you. Like a notice of intent from the user perhaps? He asked me personally to give him a vote of confidence. He also gained such votes from pawelz and vip. Since being on the devel lists is a requirement for all developers, this seems like a show stopper for repo access until such a time as it is resolved. Maybe I also shouldn't be a developer because some people filter me in their mail clients? You are going too far. The ban is on the mailing list access, not on being developer. By the current rules, shadzik should be a developer, since he got the customary 3 votes for him. If you or another user with RW access would like to handle the interaction with this user and be responsible for the commits, there is nothing to stop them. Yes, we get that, you don't want shadzik to have RW access. But these patches are not something that has happened overnight. They were sent to the mailing lists regularly for more than a year, and I think he should be able to apply them himself. I thought it was clear. Apparently not. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [PATCH] xorg-driver-input-wacom 0.13.0-0.15.0
On Wed, May 30, 2012 at 10:54 PM, Bartosz Świątek shad...@gmail.com wrote: 2012/5/30 Przemo Firszt prz...@firszt.eu: -- Przemo Firszt prz...@firszt.eu -- I'm living proof if you do one thing right in your career, you can coast for a long time. A LONG time. -Guy Kawasaki ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: packages: python/python-lib64.patch, python/python-noarch_to_datadir.patch, ...
On Fri, May 11, 2012 at 10:37 AM, Elan Ruusamäe g...@pld-linux.org wrote: why such sudden change on existing 2.x branch? You don't have to understand. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: packages: python/python-lib64.patch, python/python-noarch_to_datadir.patch, ...
On Fri, May 11, 2012 at 10:45 AM, Arkadiusz Miśkiewicz ar...@maven.pl wrote: I am for including py files. That's the only argument you need. Suck it up, glen. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: packages: python/python-lib64.patch, python/python-noarch_to_datadir.patch, ...
On Fri, May 11, 2012 at 11:06 AM, Mateusz Korniak mate...@ant.gliwice.pl wrote: Including .py in python and python modules helps a lot with debugging on cost of little extra disk space. Are we having this idiotic argument again? Do we package debuginfo with compiled programs, or does it land in separate package, so only the people that need it will have it? Maybe we should start including source code of the compiled binaries inside all RPMs? Because, you know, it would make debugging easier. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: th stable (Re: gimp 2.8.0 rc1, gimp plugins)
On Sat, Apr 21, 2012 at 11:39 AM, Artur Wroblewski wrob...@pld-linux.org wrote: 1. DEVEL is for unstable versions - we are talking about RC. If this Release Candidate is stable, then why is it a Release Candidate and not the final version? Please tell us. 2. the release announcement contains the following statement The changes in GIMP 2.8rc1 since 2.7.5 are mostly not user-visible. We merely updated the code to work with newer versions of GEGL and babl, fixed GFig rendering issues and used all the translation updates we got to the point. Oh, so we might as well have 2.7.5 on HEAD? Why not 2.7.1? 3. it does not look like there are major issues with 2.8rc1. http://lkml.indiana.edu/hypermail/linux/kernel/0110.1/0932.html I am sure 2.4.11 also didn't look like it would have any major issues. 4. on top of that, i have tested it with my workflows Oh wow. Please go away and be back when you test MY workflow and ensure it works flawlessly. therefore, imho, it is worth _starting_ upgrading Then do it on DEVEL and merge to HEAD when the stable version is released and stop trolling already. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: th stable (Re: gimp 2.8.0 rc1, gimp plugins)
2012/4/21 Bartosz Świątek shad...@gmail.com: It may seem unbelievable to you, but there are people who use *uncritical* *programs* for living. How absurd is that! Right? I am thinking about doing some changes to apache. Or maybe mysql. No, python would be the best one to modify. Think breaks everything changes. I'm sure it's OK with you guys, as *I* don't need these *programs*. These are not even libraries, just programs. So no problem there, right baggins? wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: pld -cvs/svn - git / gitolite
On Tue, Mar 6, 2012 at 3:52 PM, Przemo Firszt prz...@firszt.eu wrote: Anyone tried to experiment with gitolite + git submodules? http://git.tld-linux.org/ wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: packages: nagios/nagios.spec - bcond embeded perl chsanged. [OOC] Glen nauc...
2012/2/7 Arkadiusz Miśkiewicz ar...@maven.pl: Please stop this personal crap. Better share with us about what is the actuall problem with this bcond? I cannot tell that from reading your commit logs. Jakbyś nie odpierdalał personal crapu z abw, to by sobie glen mógł przeczytać o co chodzi. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: packages: gocr/gocr.spec - upgraded to 0.49
2011/5/23 Elan Ruusamäe g...@pld-linux.org: and what's the problem there? No problem at all... none of the legacy drivers are in th because 1.10 xorg in th, so any commit is better than before By using that logic I may break any package and say that the broken version is not on the ftp, so where's the problem? wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: ssh: send/accept GIT_* env vars
2011/5/4 Pawel Golaszewski bl...@pld-linux.org: it's private glen's config in global stuff... Shadzik, stop pretending you are blues! wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: ntfs-3g and ntfsprogs merge
On Thu, Apr 21, 2011 at 10:50 AM, Caleb Maclennan ca...@pld-linux.org wrote: Yes, the Provides and Obsoletes will take care of being able to upgrade and replace the previous package names. The problem is that there is no notification feature for the OLD packages, they just get stuck at an old version and eventual disappear from the stable package set. However this is not a unique problem to this issue, it happens regularly and even I have been known to ask on this list where to find the new package name for something project that morphed into something else. Maybe we should provide empty rpms for the obsoleted packages with the appropriate R: and some special name in release field? For example: ntfs-3g-1.2.3-69.packageexpired, R: ntfs3g-newshit Then we may have a simple cron job that would do rpm -e `rpm -qa|grep packageexpired` on a regular basis to remove the obsolete stuff. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: packages: telepathy-glib/telepathy-glib.spec - merge DEVEL branch
On Tue, Mar 22, 2011 at 11:26 AM, Caleb Maclennan ca...@pld-linux.org wrote: Wolf, I feel like I'm on the outside of an insider joke. You will need a prayer book if you want to do merges in CVS. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cdg: shadzik-rw (NEW)
On Thu, Jan 27, 2011 at 2:57 PM, Piotr Budny piotr.bu...@gmail.com wrote: Due to that proposition, it should be also discussed list of active CDG members. According to sklad.txt and e.g. PLD Linux CVS Statistics - 2010 that list is obsolete. The admision/removal of a CDG member is accomplished by a 2/3 majority vote with a minimum of 50% turnout. Only CDG members vote. A proposal for removing a member is to be voted on after 3 months of that members inactivity as a CDG (lack of comments, no voting, etc.). A CDG member may resign. This does not require a vote. For this example, members that does not exists on that statistics are: So what? wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cdg: shadzik-rw (NEW)
On Thu, Jan 27, 2011 at 3:23 PM, Mariusz Mazur mma...@kernel.pl wrote: The admision/removal of a CDG member is accomplished by a 2/3 majority vote with a minimum of 50% turnout. Only CDG members vote. With the current cdg member's list, any vote will result in at least 50% of members getting automatically booted from cdg. Yes, rules are not perfect. A proposal for removing a member is to be voted on after 3 months of that members inactivity as a CDG (lack of comments, no voting, etc.). Can multible removals/additions be made in a single vote? Why not? For this example, members that does not exists on that statistics are: So what? For a CDG decission to have any legitimacy, the CDG members should reflect the currently active developers. So it makes sense to base the updated CDG members list on the top commiters list + infrastructure admins. cdg is cdg. Changing rules and/or member list in a way that breaks the aforementioned rules is in no way legal. Staging a coup d'état breaks the continouity of our government, for the lack of better word. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: packages: dotnet-evolution-sharp/dotnet-evolution-sharp.spec, dotnet-evolut...
On Sat, Nov 20, 2010 at 1:03 PM, Patryk Zawadzki pat...@pld-linux.org wrote:
On Fri, Nov 19, 2010 at 8:49 AM, lisu l...@pld-linux.org wrote:
Author: lisu Date: Fri Nov 19 07:49:44 2010 GMT
Module: packages Tag: HEAD
Log message:
- reverse, 0.21.x goes to DEVEL
- rel 3, epoch 1
When you bump Epoch, fix the Requires: %{name} = %{version}-%{release}
lines. Current packages are broken.
--
Patryk Zawadzki
Zapomniało ci się wpisać Stallmana i Torvaldsa do CC.
wolf
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [PATCH] NetworkManager ModemManager
On Mon, Sep 27, 2010 at 11:23 AM, Arkadiusz Miskiewicz ar...@maven.pl wrote: 2010/9/27 Elan Ruusamäe g...@pld-linux.org: do you know, that if you say +1, you must mentor his commits, i.e correct him and explain things, not just say yes AFAIK the above rule applies only to the first person proposing +1 (blues in this case). I believe glen is correct here. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: packages: cairo/cairo-link.patch, cairo/cairo.spec - 1.10.0 - merged from d...
On Sat, Sep 18, 2010 at 12:40 PM, Patryk Zawadzki pat...@pld-linux.org wrote: I don't think anyone would use PLD to write commercial games). Aj tam nie pierdol. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: rpm.groups - Libraries/Ruby
2010/6/24 Paweł Zuzelski z...@xatka.net: Any comments? Why do we care about RPM groups? wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: rpm.groups - Libraries/Ruby
2010/6/24 Jeff Johnson n3...@mac.com: Why do we care about RPM groups? What else would we discuss if RPMTAG_GROUP did not exist? I was referring to the general shit state of the group hierarchy in PLD. Basically 90% of the stuff is in Applications or X11/Applications, which makes the groups completly useless. There was some movement to make them more useful, but that was in 2004 and hadn't been talked about since then. New group hierarchy proposition can be found at http://cvs.pld-linux.org/cgi-bin/cvsweb/PLD-doc/nowe-grupy?rev=HEAD. Jeff, it would be interesting to hear what do you think about replacement of groups with tags, as that might make more sense. Prototype graphical package manager which sorts packages by groups can be downloaded from http://team.pld-linux.org/~wolf/pacman/, but it's not all that useful. Prototype tool for managing package groups can be downloaded from http://team.pld-linux.org/~wolf/rgmt.7z, but it works only with the old SPECS/SOURCES structure and will break on some spec files. But, since it displays the groups from all the spec files, it can show how much chaos and typos is there, since nobody really cares. tl;dr: RPM groups in PLD suck. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: rpm.groups - Libraries/Ruby
New group hierarchy proposition can be found at http://cvs.pld-linux.org/cgi-bin/cvsweb/PLD-doc/nowe-grupy?rev=HEAD. This tree is as good as any other I've seen, certainly far far better than synaptic/aptitude choices. It was based on sourceforge trove software map. Have you considered: Setting up a process to map specific packages into your taxonomy Something like a de.licio.us tagging framework to do the mapping subjectively with community (whatever that means) involvement would be one relatively painless process. Translation: noone would do it. Not worth the effort. wolf ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
WTF?
[17:35 w...@bajzel:~/rpm/packages]% cvs up -r 1.603 builder P builder [17:35 w...@bajzel:~/rpm/packages]% ./builder -g oneko # $Revision: 1.18 $, $Date: 2008/07/27 22:18:56 $ oneko-1.2.tar.gz having proper md5sum already exists [17:35 w...@bajzel:~/rpm/packages]% cvs up -r 1.604 builder P builder [17:35 w...@bajzel:~/rpm/packages]% ./builder -g oneko Warning: No CVS access defined - using local .spec file cvs checkout: No CVSROOT specified! Please use the `-d' option cvs [checkout aborted]: or set the CVSROOT environment variable. Error: spec file not stored in CVS repo. revision 1.604 date: 2010/02/11 19:25:12; author: glen; state: Exp; lines: +3 -3; kopt: kv; commitid: 2ecc4b7459985abf; filename: builder; - packages_dir = top dir, requires rpm build macros = 1.534 [17:36 w...@bajzel:~/rpm/packages]% rpm -q rpm-build-macros rpm-build-macros-1.555-1.noarch wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: xulrunner.spec and ac bcond
On Mon, Dec 22, 2008 at 01:17:11PM +0200, Elan Ruusamäe wrote: you can always do cvs annotate and ask whoever added it... Jokes go to fortunes CVS module, not here. wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: kernel + xorg + nvidia
On Tue, Aug 05, 2008 at 12:59:27PM +0300, Elan Ruusamäe wrote: how many out there use custom kernel anyway (i mean by that kernel installed without rpm package)? What kind of bullshit argument is it supposed to be? How many out there be developers who don't understand polish? Why am I even writing this in english? wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Packaging .py files
2008/7/17 Mariusz Mazur [EMAIL PROTECTED]: Yes, condoning bad code practices is the way to go. Go install your ubuntu. It's bad in theory. In practice, for the past mny years nobody gives a shit about theory in case of /bin/sh. Bad for them. So that's top score for theory and a FAIL on the reality check. Flushing quality down the toilet is not an option. Half the time the original developers don't have a clue, so your argument fails. Then fix upstream. The number of sane developers without inferiority complex is very low and I don't like to talk with idiots if I don't have to. I'd rather default to assuming that the guys who wrote the stuff know better than Joe Random Developer does. I'm actually *using* their code, so I kind of assume they have some kind of clue. I actually have enough *experience* to *know* that most of the time they don't. (python -- I'm quite sure it's authors never meant for it to be distributed the way we do) The more I know about python the more I am assured it's a joke language. That's not an argument. Running debug code by default and requiring special knobs for having release code ran is kind of funny if I don't have to use it. The only part where we actually prefer not to have bash is where our own (made in-house) scripts are concerned. You and who else? And concerning the point of that sentence? Anything you'd like to say? Maybe that it's false or sth? With some specific reasons as to why? Of course it's false. You are speaking strictly for yourself, yet you are manipulating everyone to think that's a widely applauded opinion (by using we instead of I). Bullshit. The scripts that expect bash have #!/bin/bash in header, not #!/bin/sh. That's true only for the scripts whose authors (a) know there are distros that don't use bash as sh You were saying something about developers having a clue recently? (b) give a shit. We know that you don't. Doing it 'our way' is simply pointless Our way? https://wiki.ubuntu.com/DashAsBinSh (what exactly do we gain?). Speed, correctness, etc. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Packaging .py files
On Thu, Jul 17, 2008 at 07:47:31PM +0200, Patryk Zawadzki wrote: I'm against being forced to do something counter-productive in order to get some I'm against being forced to have some shit installed on my computer that only some lazy developer needs. In other words - we are one of the most limited distros when it comes to resources. We will surely have more people power if we start lowering quality and blending with other distros. Pursuing a dream is one thing but we should not be forced to do it. I'm not sure I want to lose my job for the sake of saving the world. Since when does PLD care about your job (or mine)? Saying that your personal needs should come before general distros needs is extremely arrogant IMO. I want to be able to easily install a package and get the goddamn python sources. So install your python debuginfo equivalent and stop bitching. Why should everyone be forced to have your crap, when they're just fine with already compiled bytecode? Sure pydoc is useful but it's only useful to the extent man is - you have to know the name of the function in which case you probably don't need pydoc anymore (API changes or implementation details that change but some coder decided to rely on). Yes, yes, very interesting. I will start packaging all the sources of C libraries into main packages then, just so I can check if the code really, *really*, *REALLY* does what the documentation and/or man pages say. That's my favourite pastime activity, you know. I do it for the kicks. wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Packaging .py files
On Thu, Jul 17, 2008 at 12:30:40AM +0200, Mariusz Mazur wrote: It's not a reliable system when any application can fail because it either expects something that all of the other distros, except us, have (sh - bash) Yes, condoning bad code practices is the way to go. Go install your ubuntu. or we've done something to it without having much clue about original developers' reasons for a particular choice (ripping out internal versions of various libs). Half the time the original developers don't have a clue, so your argument fails. (python -- I'm quite sure it's authors never meant for it to be distributed the way we do) The more I know about python the more I am assured it's a joke language. The only part where we actually prefer not to have bash is where our own (made You and who else? in-house) scripts are concerned. All other scripts should be run with what their authors expected, and that's bash (the Have It Just Work rule). The Bullshit. The scripts that expect bash have #!/bin/bash in header, not #!/bin/sh. wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: ndoc-no-warnaserror.patch (NEW) - niech sobie ankry przenosi do SOURCES
On Thu, Jun 12, 2008 at 12:00:23AM +0200, Adam Gołębiowski wrote: Author: wolf Date: Wed Jun 11 21:56:45 2008 GMT Module: SPECS Tag: HEAD Log message: - niech sobie ankry przenosi do SOURCES Files affected: SPECS: ndoc-no-warnaserror.patch (NONE - 1.1) (NEW) WTF? cvs: hash.c:353: findnode: Assertion `key != ((void *)0)' failed. wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: PLD-specs-TODO
On Sat, May 24, 2008 at 02:49:25PM +0100, wrobell wrote: +1 +1 -1 -57 *2 dx (c=-1) wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: PLD-specs-TODO
On Sat, May 24, 2008 at 11:46:49AM +0200, Tomasz Pala wrote: +1 +1 -1 -57 wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: fortunes-pl.spec - add todo
On Sun, Jan 06, 2008 at 03:41:16PM +0100, Patryk Zawadzki wrote: I often use a simple script to convert Fedora specs to proper PLD format (for obvious reasons: most of the Fedora specs make adapter cry even after 3+ runs and these guys tend to override lots of macros in each spec file). Had I shared this script, I wouldn't ask for each of these files to carry a big fat warning: once upon a time someone decided to generate the file. How does that relate to fortunes-pl.spec? wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: fortunes-pl.spec - add todo
On Sun, Jan 06, 2008 at 03:59:06PM +0100, Patryk Zawadzki wrote: I mean generators are only useful when they make your work easier. If it's easier to fix and maintain the result than to fix the generator then it shouldn't be a real problem. fortunes-pl.spec generator is really simple. It's just concatenating spec parts, with one loop for the subpackages. I don't understand why it is easier to change something in fortunes-pl.spec than in one of the spec parts used by generator. Take a look, this file is part of generator: http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/fortunes-pl/SPEC/spec-template-header?rev=1.5;content-type=text%2Fplain wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS (AC-branch): pidgin.spec - AC-branched
On Sat, Oct 20, 2007 at 11:24:40PM +0200, Tomasz Pala wrote: http://opensubscriber.com/message/[EMAIL PROTECTED]/3312217.html Does it mean that glitz do nothing in cairo or what? git://people.freedesktop.org/~macslow/glitz-test Try to run that without glitz support in cairo. wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mono, gtk
On Fri, Aug 10, 2007 at 09:24:54PM +0100, wrobell wrote: when i switch back to mono 1.3.x, then it works perfectly. f-spot fails in the same way. works whith mono 1.3.x, though. What mono 1.3.x? wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: rpm and mono
On Sun, Jul 15, 2007 at 10:44:59AM +0200, Łukasz Jernaś wrote: I just want to drop a note here that current mono-find-requires doesn't find libraries p-invoked from mono assemblies. They can be partially get from monodis --moduleref assembly but some sort of mechanism for pulling the complete soname would be needed, because just the name of the lib is included in the output from the previous command. Any hints? In proper cross platform apps p-invokes should use windows dlls and unix libraries should be specified in dllmap. What about that? wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: NEW poldek 0.20070617.23 - please test
On Sun, Jun 17, 2007 at 11:42:22PM +0200, Arkadiusz Miskiewicz wrote: New poldek snap (0.20070617.23) was sent to Th builders. It has improvements in handling package colors and *tadam* multilib capabilities. Please test :) błąd: libxslt-1.1.21-1.athlon package color (0) is not equal to libxslt-1.1.21-1.athlon.rpm's one (1) błąd: libxslt-progs-1.1.21-1.athlon package color (0) is not equal to libxslt-progs-1.1.21-1.athlon.rpm's one (1) There were package coloring mismatches. Proceed? [y/N] wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [Th] SMP for all!
On Mon, Jan 22, 2007 at 06:32:54PM +0100, Rafał Cygnarowski wrote: Besides... if there is problem with thouse devices on smp kernel than it should be fixed and I think it's the correct way to solve problem (not running away to up kernel...). So fix them and then we'll talk. There are many things that should be, but unfortunately, they aren't. wolf -- Bartek . Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: beryl-core.spec, beryl-plugins.spec, beryl-settings.spec, e...
On Thu, Oct 05, 2006 at 01:40:32PM +0300, Elan Ruusamäe wrote: why snapshot in Version field? should use snapshot date in Release to avoid epoch bumps. It was late and I was too lazy to do that, but eager to see the new eyecandy. BTW, everybody fears bumping epoch, but I don't recall anyone saying why it is bad. wolf -- Bartek . - Będzie was obowiązywało (...) Nie na jutro broń boże, tylko Taudul :na pojutrze. .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: mono.spec - 1.1.16.1 - changes in dependency generators cau...
On Wed, Jul 12, 2006 at 10:19:55PM +0200, Adam Gołębiowski wrote: That's not a matter of bootstrap - I did it with 1.1.16 and had those mscorlib deps unresolved. So the generators were broken instead of being fixed by the mono team. I guess we'll stick to manual provides, unless someone wants to write and maintain a patch that will fix the generators. wolf -- Bartek . - Prąd jest jak większość stworzeń... będzie płynął tam, gdzie Taudul :mniejszy opór. .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: rpm.spec - R: rc-scripts (/etc/sysconfig) - rel 1.4
On Wed, May 24, 2006 at 02:32:45AM +0300, Elan Ruusamäe wrote: that's a bad dep. /etc/sysconfig is processed anyway as root from %post scripts as well we don't require pkgconfig in packages providing .pc files. Yes, it's a bad dependency, but without it there are problems with upgrading rpm on builders: error: Failed dependencies: /etc/sysconfig is needed by rpm-base-4.4.6-1.2.i686 wolf -- Bartek . - Jak doskonale udało wam się zapomnieć... Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: rpm.spec - R: rc-scripts (/etc/sysconfig) - rel 1.4
On Wed, May 24, 2006 at 03:07:51AM +0300, Elan Ruusamäe wrote: /etc/sysconfig is needed by rpm-base-4.4.6-1.2.i686 that's something new in rpm? Yes, it appeared in 4.4.6. wolf -- Bartek . - Stare porzekadła, przysłowia są takie dobre, bo zawsze można Taudul :wybrać to które pasuje. .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Java SUN
On Wed, May 17, 2006 at 01:06:19PM +0200, Jan Rekorajski wrote: Don't you tempt me ; [1] [1] to upgrade gcc to 3.4.x in AC... That would be just great. Do something currently, when AC is freezed, what hasn't been done for 2 or 3 years just because we were going to freeze AC in the next month and it would delay release. wolf -- Bartek . - No gdzie ten palec, możesz se między nogi wsadzić. Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: RPM changelog
On Thu, Apr 27, 2006 at 10:20:36PM +0200, Marcin Król wrote: in binary rpm's. why pointless? Few KB more or less per rpm makes no difference for me. [14:51 [EMAIL PROTECTED]:~]% rpm -qa|wc -l 1423 Assuming every package has 10 KB worth of changelog, then we're talking about 14 MB of almost never used, slowing rpm down, taking disk space crap. That's a lot of difference to me. changelog isn't compressed, and some small packages have more in changelog in Small packages usually doesn't have big changelogs. That assumption is just plain wrong. wolf -- Bartek . - W każdym porządnym domu powinien być fortepian. A wiecie po Taudul :co? Żeby na nim postawić palmę. .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: RPM changelog
On Fri, Apr 28, 2006 at 03:42:30PM +0200, Marcin Król wrote: [14:51 [EMAIL PROTECTED]:~]% rpm -qa|wc -l 1423 So? As I said, that makes no difference _for me_ So? I said it makes difference _for me_. wolf -- Bartek . - O! Jest ten co wypisuje o mnie bzdury. Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: openoffice.org for i686 rebuilt on current ac-main (neon, openldap deps)
On Sun, Jan 22, 2006 at 01:19:15PM +0100, Arkadiusz Miskiewicz wrote: If anyone is interested: http://ep09.pld-linux.org/~arekm/openoffice.org/ What about sending it to builders? wolf -- Bartek . - Pan długopisem stawia? Taudul : - A co się będę chrzanił. .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: openoffice.org for i686 rebuilt on current ac-main (neon,
On Sun, Jan 22, 2006 at 07:49:51PM +0100, Andrzej Krzysztofowicz wrote: http://ep09.pld-linux.org/~arekm/openoffice.org/ What about sending it to builders? It is easy to guess why it is wrong time: arekm is building new kde. And locking builders for many hours while it may be neccessary in a few days again (because of bugs found) is definitely not a good idea. I'm not saying 'now', but in general. arekm's openoffice rpms are sitting there for some time now and they work quite well. wolf -- Bartek . - Pamiętacie.. marzyciel, co? Z początku tego roku ruch Taudul :harmoniczny? .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [EMAIL PROTECTED]: ERRORS: pnetlib.spec pnetC.spec ml-pnet.spec OK: pnet.spec]
On Fri, Dec 23, 2005 at 06:03:50PM +0100, Andrzej 'The Undefined' Dopierała wrote: summary: - pnetlib doesn't build with resgen from mono - nant doesn't build with resgen from pnet how resolve it? have you any ideas? (other than remove pnet) Maybe rename pnet's resgen to, for example, pnet-resgen and make proper patch for pnetlib to use it? wolf -- Bartek . - Wzorek, jak doskonale zapomnieliście, 2 pi przez t. Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: X11 monolitic 6.9.0 for AC
On Fri, Dec 23, 2005 at 02:55:52PM +0100, Fryderyk Dziarmagowski wrote: works pretty well on two radeons (r200 and r300). On r200 with EXA and DRI, on r300 only 2D. since yesterday no problems here. Works, r300 with 3D acceleration. wolf -- Bartek . - Wiecie po co człowiek ma uszy? Żeby się śmiał od ucha do Taudul :ucha, a nie dookoła głowy. .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [EMAIL PROTECTED]: ERRORS: pnetlib.spec pnetC.spec ml-pnet.spec OK: pnet.spec]
On Wed, Dec 21, 2005 at 02:57:46AM +0100, Andrzej 'The Undefined' Dopierała wrote: why not use resgen from pnet, which is available on all platforms? It's only asking for trouble IMHO. I don't want to debug some weird errors introduced by using not-from-mono-unlike-rest-of-toolchain utility. wolf -- Bartek . - Później do krwioobiegu wypompowywane jest serce. Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: tao.spec - auto mono prov/req
On Fri, Aug 12, 2005 at 10:29:55PM +0300, Elan Ruusamäe wrote: what about just creating new package rpm-monoprov and requiring that package on BR? What should be in that package? macros.* are provided by rpm-build and mono-find-* are from mono. wolf -- Bartek . - Kto tam śpi? Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: mono.spec - handle rpm mono provides/requires - rel 2
On Thu, Aug 11, 2005 at 09:38:21PM +0300, Elan Ruusamäe wrote: why thse are in /usr/bin, while other similiar scripts are in /usr/lib/rpm? Mono places them there. If it's good or not is open to discussion. wolf -- Bartek . - Przy drobnych przeliczeniach, które zajmą ci stronę... Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: tao.spec - auto mono prov/req
On Thu, Aug 11, 2005 at 10:42:24PM +0300, Elan Ruusamäe wrote: i believe proper way of doing it is require some rpmbuild(macros) version (don't forget to document it in PLD-doc/BuildRequires.txt), in case someone backports it to ac-branch 4.4.1 version of rpm Almost all changes are in rpm's code, not in macros, so I don't see how it could work. Maybe some BR: rpm(monodep) would be better? wolf -- Bartek . - Wiecie o czym są Chłopi Reymonta? Taudul : - O chłopach. .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: rpm.spec - rpm-build P: rpmbuild(monoautodeps)
On Fri, Aug 12, 2005 at 01:51:28AM +0200, Paweł Sakowski wrote: -# because of -fvisibility... related fixes -Requires: gcc = 5:4.0.1-0.20050514.2 Was that on purpose? I can't see anything related to -fvisibility in rpm on HEAD. Furthermore: % cvs log rpm.macros revision 1.227 date: 2005/07/07 19:23:35; author: pluto; state: Exp; lines: +1 -1 - -fvisibility-inlines-hidden disabled. wolf -- Bartek . - Zwróćmy uwagę na wielorakość i różnorodność tego ruchu. Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: vte.spec - broken, rel. down to 0.1
On Wed, Aug 03, 2005 at 06:03:15PM +0200, Fryderyk Dziarmagowski wrote: +Revision 1.77 2005/08/03 14:19:04 freetz +- broken, rel. down to 0.1 If you elaborate what it is that you find broken, there's a chance that someone will fix it. sending a problem description to authors it's not sufficient? should I In case you didn't noticed, you commited into PLD cvs, not vte author's one. wolf -- Bartek . - Pamiętajmy, że ściany mają uszy, a czasami uszy są koło drzwi. Taudul : .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: vte.spec - broken, rel. down to 0.1
On Wed, Aug 03, 2005 at 06:45:59PM +0200, Fryderyk Dziarmagowski wrote: don't like my commits? feel free to report a abuse to PLD CDG. Not yet. wolf -- Bartek . - Będzie was obowiązywało (...) Nie na jutro broń boże, tylko Taudul :na pojutrze. .: w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
