On Fri, Jan 24, 2014 at 11:14 PM, Jacek Konieczny wrote:
> Before merging on master I would like to see opinion of anybody using
> the asterisk package.
>
I am using the 1.8 packages in production but the boxes are EOLed and I'm
in the process of migrating the services, so I don't plan on upgrad
On Tue, Dec 31, 2013 at 10:46 PM, Aria Stewart wrote:
> On Tue, Dec 31, 2013 at 09:36:40PM +0100, Jan Rękorajski wrote:
> > As promised I made a new snapshot of the PLD Th line.
> > See the announcment on http://www.pld-linux.org/ for details.
>
> And there was much rejoicing!
>
Excellent, keep
I tried to do an install via Rescue CD and poldek --root the other day
only to discover that apparently a lot of packages (including the
kernel) are missing from the current main TH ftp repository.
What's the deal with this? How is anybody supposed to get a system up
and running without a way to b
Are there sanely recent CRI images for TH to be had anywhere?
Caleb
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Can we rename the terminator package to gnome-terminator? There are
actually two projects by this name and I'd like to introduce the one
we don't have to a couple of my systems. I looked at the upstream
projects and it looks like the one currently in our specs repo is
already partially renamed upst
2012/9/29 Aria Stewart :
>> seems github packages are case insensitive, perhaps we should limit
>> similarily in pld to disallow creating packages that differ just
>> character case?
>
> +1. And lowercase be the norm.
+1, the current mix-n-match case is kind of a mess and is more of a
pain than it
> I'm afraid ohloh might be overwhelmed by *all* the things you do
> (just as it was when facing *all* the ALT Linux gear repos when
Their recent takeover by BlackDuck has given them a few more resources
and they've got a lot of stuff cleaned up. I don't think they would
give us the boot do to DoS
Is there any place where the entire PLD git repository can be cloned
as single repository? I realize this would be a read-only thing, but
the multiple repository layout is problematic for some things such as
the code and commiter analysis done by sites like Ohloh
(https://www.ohloh.net/p/pld-linux)
2012/8/10 Bartosz Świątek :
> should be punished
This isn't about punishment. It's about civility and cooperation.
If you're interested in those things, start practicing them instead
of trying to stir things up. People would be fine with your
participation if you did.
Caleb
_
> 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.
Quite honestly, that has nothing to do with the present case. Even if a
si
2012/8/7 Bartosz Taudul :
> Ponieważ Bartek cały czas jest żywotnie zainteresowany rozwojem
> dystrybucji i aktywnie przyczynia się do wprowadzania zmian, proponuję
> aby dać mu dostęp RW do repozytorium.
Aren't you rather skipping over a number or relevant issues?
First of all, the user you are
I've been playing around with a script that generates a live-cd based
off of Th for a special purpose machine. I'm generating the target
file system using `poldek --install-dist`.
My current package set installs, but later in the script when I try to
run some commands having chrooted into the targ
2012/8/7 Jan Rękorajski :
> You missed the real change, I did not remove P/O for cryptsetup-luks.
> I removed P/O for cryptsetup i.e itself
A... sure enough. Looks like I missed that one too. Sorry to
bother you, but having broken upgrade paths myself in the past over
that mistake...
Caleb
__
2012/8/7 baggins :
> Providing and obsoleting itself makes no sense
> Release 2
> -Provides: cryptsetup-luks = %{version}-%{release}
> -Obsoletes: cryptsetup-luks < 1.4.1-2
Actually it does make sense in the case where a different package used
to provide something of the same nam
2012/7/10 Kacper Kornet :
> The solution that I know is to define a wrapper around git, that calls
> call "git -c user.email=whatever", where whatever depends on the current
> path. It's cumbersome, but maybe better then nothing.
Here's my current hack as function for my zsh shell:
function git (
2012/7/10 Mariusz Mazur :
> Or one can alias the 'git' command to a simple script that checks for
> .git/config, check if remote origin is git.pld-linux.org and if so, uses a
> different user.email.
>
> Hm, I could use that. Wonder if anyone already wrote it.
I thought of that too and could code i
2012/7/10 Jakub Bogusz :
> On Tue, Jul 10, 2012 at 03:40:58PM +0200, Kacper Kornet wrote:
>> On Tue, Jul 10, 2012 at 04:26:00PM +0300, Caleb Maclennan wrote:
>> > 2) Is there a way to set git's user.email config variable without
>> > doing it globally? I use git fo
2012/7/9 Kacper Kornet :
> * Some documentation
>
>
> For some basic introduction to git and how to use it to work with PLD
> repositories please see:
>
> http://www.pld-linux.org/dokuwiki/howto-git
Two simple questions:
1) I haven't seen any notes in the docs about comment f
2012/7/6 Bartosz Taudul :
> I told you it's just a stupid kindergarten power play. Some people
> never learn...
Look. If all you guys want is to make me part of a power play, please
just count me out. Don't vote for me. I'm not interested in joining a
pre-school. I skipped that the first time arou
> - temporarily withdraw my second; let's wait a week or two and see how caleb's
> current projects with regards to the cdg go; if he succeeds, that means he
> might be of use at conflict resolution; if he fails, he fails, and there's
> no point in granting him cdg membership at the present t
2012/7/1 Jacek Konieczny :
> On Sun, Jul 01, 2012 at 10:47:19PM +0300, Elan Ruusamäe wrote:
>> On 07/01/2012 11:51 AM, Jacek Konieczny wrote:
>> > Do we need clvmd in the main lvm2 package? It pulls some dependencies
>> > irrelevant for non-clustered setups.
>> i'm in for moving clustered deps to s
2012/5/7 Elan Ruusamäe :
> 1. rename gedit dir to gedit0 in cvs server side and optionally drop it
> client side
> 2. rename gedit2 dir to gedit in cvs server side, and adjust names in files
> on cvs client side
This sounds good. If somebody takes care of the server side bit I'll
help cleanup the
2012/5/6 Elan Ruusamäe :
> feel free to merge gedit2.spec to gedit.spec (and drop the former), just
> remember to handle obsoletes properly
As a latecomer to CVS (backporting my knowledge of VCS from
subversion, git, etc) I am not sure which button to push here. Since
these two specs aren't a bran
> Package copied/renamed server-side.
Thank you!
Can I ask why our gedit module is called gedit2 on cvs? The upstream
project seems to be at 3.4.1, which is what we have in that spec file.
Is there any point in keeping that legacy name in our cvs module?
Caleb
___
The upstream project NautilusSVN has been renamed to RabbitVCS. Can we
get our CVS module renamed or should I work on a new spec?
Thanks,
Caleb
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld
2012/4/20 Artur Wroblewski :
> it is very simple. "th-stable", "ac-stable" or whatever... provide
> meaningful, self documenting names to things.
Hey guys, how does this compute? My version control experience is
mostly subversion with a bit of git lately. CVS is still black magic
to me. Would a ch
> Caleb, "stop trolling"*! You're asking very inconvenient questions :)
Wink wink.
I'm not actually trying to troll or be inconvenient. I'm also not
interested in pointing fingers.
I am a system administrator having a hard time keeping up with all the
broken systems. I think a contributing facto
> well... if you need more stable line, then why not to create one with
> appropriate
> branch in CVS? of course, the problem is that somebody needs to maintain that,
> which I believe is full time job and lack of resources causes the stable
> branch
> to freeze. therefore, imho, it is not good id
> Ac is stable release for which we have appropriate branch and Th
> is in constant development mode, isn't it?
This is one area where PLD's release system is actually pretty wonky.
Other than a few emebeded or very static applications, AC is simply
too old to use for most stable systems. This put
2012/4/19 Artur Wroblewski :
> hi,
>
> i would like to move gimp 2.8.0 rc1 from DEVEL to HEAD.
>
> any argument against?
>
> btw. we have some quite old gimp plugins on ftp, i.e. build in 2010, 2009.
> shall
> they be removed, rebuilt?
>
> regards,
>
> w
Yes. That is an RC for a major release ver
2012/3/27 Caleb Maclennan :
>> http://www.nvnews.net/vbulletin/showthread.php?p=2538961
>>
>> Fixed a bug that caused OpenGL applications to crash with some libc
>> versions, such as eglibc 2.15.
And ... that did the trick. 295.33 with the 3.3.3 kernel from th-test
ru
> http://www.nvnews.net/vbulletin/showthread.php?p=2538961
>
> Fixed a bug that caused OpenGL applications to crash with some libc
> versions, such as eglibc 2.15.
Eh? Now that looks promising. I'm trying to build PLD's packages now.
Silly me I would have thought nvidia would fix major bugs like
> I have reported this problem long time ago on a polish devel list. There was
> no solution given (only "we must wait for the next nvidia release") and I've
> switched to nv. Then pluto suggested to try:
I started seeing this with a 290.x nvidia driver version and never
figured it out, but I've w
-- Forwarded message --
From: "Caleb Maclennan"
Date: Mar 26, 2012 1:51 PM
Subject: Segfaults on across the board in TH
To: "PLD Devel"
Recently I've upgraded several desktop oriented machines against the
latest TH repositories. The two I'm loo
On Tue, Aug 23, 2011 at 19:14, Patryk Zawadzki wrote:
> Yes, other rpm wrappers support triggers. I think the proper way would
> be to add these to rpm itself rather than trying to hack them into
> poldek.
Add add system wide %pre-transaction %post-transaction macros to rpm
itself? That sounds fa
On Tue, Aug 23, 2011 at 17:54, Patryk Zawadzki wrote:
> If you're only interested in a particular
> group of packages, consider faking install-time expansion by calling a
> common shell script in %post or %posttrans.
I am interested in ALL packages, however I don't understand what you
mean by "fa
Does poldek offer any hooks or way to trigger actions at any point?
For example are there pre/post transaction hooks that I could modify
to run something before and/or after any rpm action is taken? How
about an "on exit if any package installed / upgraded / uninstalled"
during the lifetime of the
2011/7/25 Elan Ruusamäe :
> or just use our distfiles upload...
Would you believe I don't know how to do that?
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
On Sat, Jul 23, 2011 at 11:35, caleb wrote:
> wget -nv --no-check-certificate --user-agent=PLD/distfiles -O
> ./tmp/9c4646a0-f84d-45c6-9e96-8c9a251e6297/fdf09c8cdea9c9e58c6fc2acc79a0528/keenerd-pacgraph-e495c03.tar.gz
> "https://download.github.com/keenerd-pacgraph-e495c03.tar.gz":
> https://dow
> "ready" is a place where packages are moved over longer period of time to get
> kind of package set ready to be moved to "main".
So is there a reason Gnome3 skipped the "ready" tree?
> Because there is no checking in python scripts for that.
Shouldn't there be some kind of test using rpm to ch
The current zsh package on the main mirror site for TH x86_64 is zsh-4.3.12-1.
When I try to upgrade to it from 4.3.11-1 I get something like this:
> error: zsh-4.3.12-1.x86_64: req libc.so.6(GLIBC_2.14)(64bit) not found
The version of glibc in the same TH tree is 2.13-6. Only the th-test
tree h
>> >> - ta_LK (Sri Lanka Tamil) unsupported, rel 2
>> >>
>> > caleb, why only this one? :)
>>
>> Valid question. The workings of find_lang and some other rpm ninja
>> tricks are still slightly magic to me.
>>
>> In this case, because it worked. That one language was causing RPM to
>> fail to insta
> caleb, why only this one? :)
Valid question. The workings of find_lang and some other rpm ninja
tricks are still slightly magic to me.
In this case, because it worked. That one language was causing RPM to
fail to install, and removing it allowed it to be installed without
errors.
Right now I'
> http://cvs.pld-linux.org/cgi-bin/cvsweb/packages/obsoleted/obsoleted.spec?rev=HEAD
>
> It works by building an empty package that marks the upgrade target
> and immediately gets obsoleted by said target. There is nothing to
> clean up then.
Where have you been all my life?
__
>> or how do you foresee the upgrade path in pld if both package names just
>> dissapear?
>
> Some Provides and Obsoletes should be sufficient. Correct meif i'm wrong.
Yes, the Provides and Obsoletes will take care of being able to
upgrade and replace the previous package names. The problem is tha
2011/3/22 Bartosz Taudul :
>> cvs up -jDEVEL
Thanks widget.
> http://images.mylot.com/userImages/images/postphotos/2130671.jpg
Wolf, I feel like I'm on the outside of an insider joke.
Caleb
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.or
2011/3/22 wiget :
> - merge DEVEL branch
Is there a magic CVS command for doing that merge or did you do it by
hand? I've wanted to do it to a few other specs and not known what was
the best practice.
___
pld-devel-en mailing list
pld-devel-en@lists.pld-
2011/3/22 wiget :
> - %files fix
> ...
> +%{_npkgconfigdir}/mm-common-util.pc
Widget ... sorry I guess I broke that, but that file did not show up
when I built the first time. It does now. Any idea what I was doing
wrong?
Caleb
___
pld-devel-en mailing
2011/1/27 Elan Ruusamäe :
> thanks, verified you didn't add your secret clause :)
I won't say I didn't think about it. I figured since I was sending it to the
list and not just slipping in a commit that it might not be subltle enough
to get away with ;-) Then again there is always `cvs annotate`.
I had a look at the cdg regulations file, and the English version is
very rough. I took the liberty of re-writing it in clearer English.
Since I do not speak Polish I am unable to compare this to the
original. I am attatching my update for review before attempting to
commit to to CVS. Since I am no
2011/1/10 Michał Lisowski
>
> > - Removed patch8, applied upstream
> >
> ^^^ if you remove patch, make sure you also remove it from cvs.
I did, the whole action was in one commit.
This is noted in the subject of the notification email sent to the
list: mono/mono.spec, mono/mono-encryption.patch
2010/12/14 Paweł Zuzelski :
> It does not build on th-i686 builder:
> http://buildlogs.pld-linux.org/index.php?dist=th&arch=i686&ok=0&name=kernel-xenU&id=39eeab1b-c086-4036-b8df-31473ed7822c&action=tail
Roger that ... I think I know what that's about. I'll try to fix it
when I get back to a comput
On Tue, Dec 14, 2010 at 03:35, pawelz wrote:
> - up to 2.6.36.2
> - please, test i686
This builds fine on i686 for me. I don't know why you had a problem
with it. What kind of error did you get? Are you cross-compiling?
Caleb
___
pld-devel-en mailing l
>>> ...pff, make temp var "key" there
>> you have write access.
> no, fix yourself,
Hey guys don't forget we're on the same team here.
I tried making this change myself, but either my smattering of awk
knowledge is not enough or something else is going on here. I made up
a variable and striped t
Bug in the tracker: https://bugs.launchpad.net/pld-linux/+bug/689563
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
> Does anybody maintain AC? Is there any chance that exim will be patched or
> upgraded to 4.7x in case of this bug:
> http://seclists.org/bugtraq/2010/Dec/77 ?
I imagine for a security issue like that someone will step in and update AC.
However it might be pertinent to ask whether that should be
2010/12/13 Zsolt Udvari :
> Bug report:
> http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2010-November/021902.html
That link isn't a bug report so much as a request for one. Also it was
suggested what information would be helpful to include in the bug
report. I just looked in the bug tr
On Thu, Dec 9, 2010 at 19:40, qboosh wrote:
> BuildRequires: libffi-devel
> -BuildRequires: libffi-devel
Huh what? These were not back to back when I edited, adapter did that :-)
Trying to build was failing during configure with something about
missing ffi.h or some such. I ran `poldek -i libff
2010/12/8 Paweł Zuzelski :
>> + /bin/sed -i -e s,\r$,, -f php,inc,js,css
>> /bin/sed: couldn't open file php,inc,js,css: No such file or directory
> Looks like %undos macro. It BRs rpmbuild(macros) >= 1.566.
Thank you Paweł. I could have cyphered that out if I hadn't had a
blind eye to that line i
2010/12/8 Elan Ruusamäe :
> On 08/12/10 21:12, Caleb Maclennan wrote:
>> I noticed while doing some testing of the roundcube beta package that
>> it will not build using older rpm-build-macros. Specifically I had a
>> machine with 561 that died trying to run the fi
I noticed while doing some testing of the roundcube beta package that
it will not build using older rpm-build-macros. Specifically I had a
machine with 561 that died trying to run the first %sed macro, after
upgrading to 596 it builds fine.
Is this something that should be noted as a BR? If so doe
On Thu, Dec 2, 2010 at 15:02, Marcin Rybak wrote:
> I have no idea if it's important to PLD, but if we take sources from oficial
> ftp.proftpd.org this should be taken into account:
>
> http://sourceforge.net/mailarchive/message.php?msg_name=alpine.DEB.2.00.1012011542220.12930%40familiar.castaglia
On Sat, Nov 20, 2010 at 17:54, Marcin Rybak wrote:
> I don't know if I have a law to say something :) - but, I'm not sure if
> dokuwiki with revisions and recent changes is what should appear on PLD
> site. IMO it is better for guides (like docs.pld-users.org was)
I hear your concern about the na
2010/11/11 Elan Ruusamäe :
> there actually exists dokuwiki install:
> http://www.pld-linux.org/dokuwiki/
>
> currently it uses pldusers.org theme, so if somebody would
> create theme similar to current www in dokuwiki format,
> i'd finish the data migration and replace the moinmoun install
>
> moi
On Tue, Nov 9, 2010 at 13:20, arekm wrote:
> -busybox(42) [OLD] 1.16.2 [NEW] 1.17.3
I've been thinking a little about the notify script that generates
these messages. I'm working on a special purpose live-cd project and
upgrading the software that will go into it, so it's been a useful
little scr
On Tue, Nov 9, 2010 at 08:37, Jakub Bogusz wrote:
> Also cairomm 1.9.x and AFAIR fribidi 0.19.x are development versions...
> (stable cairomm is 1.8.x)
The specs for poppler and cairomm have been reset to their proper
stable branches.
For fribidi, I would argue that it might be just as well to k
On Mon, Nov 8, 2010 at 21:55, Artur Frysiak wrote:
> On Mon, Nov 8, 2010 at 20:25, caleb wrote:
>> Author: caleb Date: Mon Nov 8 19:25:19 2010 GMT
>> Module: packages Tag: HEAD
>> Log message:
>> - Up to 0.15.1
>>
>> Files affected:
>> packag
Three questions about the main pld-linux.org site:
1) How does one get a working wiki user? I've tried signing up with my
cvs editor name and with a WikiName and every other suggestion but
no-way-no-how am I able to edit the wiki pages.
2) How are changes from the PLDWWW cvs module pushed to the
On Wed, Oct 13, 2010 at 13:50, caleb wrote:
> - Up to 3.2.10
Sorry guys neglected to mark this commit NFY without a release number.
There are some path changes and such that need to be fixed in this
upgrade, and I had only just started. The commit was just to switch to
a different devel box.
Alright guys I'm lost. I've been poking around in specs trying to
figure this out and can't make out what I'm supposed to use or what I
need to work on if there isn't the right thing available.
I am trying to maintain several TH machines on i386 instances over on
EC2. They have recently opened up
On Mon, Sep 27, 2010 at 12:04, Tomasz Pala wrote:
> Who? This voting is too stripped to know who about it is.
If you follow the whole email thread this came up after Przemo Firszt
sent in a bunch of stuff to be committed for
NetworkManager.
2010/9/27 Elan Ruusamäe :
> do you know, that if you s
On Sat, Sep 25, 2010 at 19:21, Mariusz Mazur wrote:
> On Friday 13 of August 2010, Pawel Golaszewski wrote:
>> I think we should give you chance to work on your own account.
>>
>> me: +1
>
> +1
>
> Anyone else? :)
+1
___
pld-devel-en mailing list
pld-de
2010/8/18 Elan Ruusamäe :
> On 18/08/10 02:57, Caleb Maclennan wrote:
>> 2010/8/16 glen :
>>> %define buildid 3533.1731
>>
>> Where can the correct source package version be downloaded from or how
>> should this be built? Building with the packag
2010/8/18 Marcin Rybak :
> Updated to 2.6.28 (changelog: http://www.openswan.org/download/CHANGES ),
I committed for you at rev 1.50, and thanks for contributing.
You might look at the following messages and consider if either of
these should get packaged, particularly the index.html file under
d
2010/8/16 glen :
> %define buildid 3533.1731
Where can the correct source package version be downloaded from or how
should this be built? Building with the package from the URL listed in
the spec leads to:
+ [ 5.2.1.1547-1 != 5.1.3533.1731-1 ]
+ exit 1
2010/6/15 Elan Ruusamäe :
> yet it was missing python-genshi dep
Thanks for sorting that and the rest of the lang file mess out.
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
2010/6/15 Elan Ruusamäe :
> i don't see any lang files with disabled bulldarch: noarch either.
Try building on i686. I don't get them on x86_64.
Also it's possible that python-Babel >= 0.9.5 is a BR.
Caleb
___
pld-devel-en mailing list
pld-devel-en@lis
I'm having some trouble packaging trac-0.12.
The current spec compiles, but the languages files are not generated
properly. If I remove BuildArch: noarch, everything builds and runs
fine but it doesn't seem that trac should be architecture specific
just because of some locale files. What is the co
2010/6/7 pawelz :
> + Fractional release (0.1, 0.5, 3.14 etc) means package is not yet ready to
> + be sent to builders. If you think that package is ready to be build,
> + increase release to the next integer.
How does this information apply to packages such as open-iscsi which
has a releas
2010/6/6 arekm
>
> Author: arekm Date: Sun Jun 6 15:36:42 2010 GMT
> Module: packages Tag: HEAD
> Log message:
> - release 5
>
> Files affected:
> packages/perl-Clutter-GStreamer:
> perl-Clutter-GStreamer.spec (1.3 -> 1.4)
Why did the rel g
2010/6/5 Arkadiusz Miskiewicz :
> New PLD RescueCD is hopefuly to be produced at the end of this month but areq
> needs help with fixing packages.
Great timing. I was just now beating my head against a problem using
the old rescue cd wondering if it would ever be updated.
I would be happy to help
2010/6/2 Elan Ruusamäe :
> it's not 1st of april to do those jokes, is it?
> hint: the source:
> http://translate.google.com/#pl|et|Pawel%20Golaszewski
Epic fail.
For icing on the cake note that this translation is used in ANY target
language. Apparently Elan Ruusamäe is the new Pawel Golaszewski
2010/5/4 Jacek Konieczny :
> I think Upstart support should be implemented as an option, coexisting
> with current solution, so the administrator may choose what he prefers
> and even use init.d for some services and upstart for other.
+1
> - chkconfig would link/unlink the files when requested
Does anybody have any input on keeping a TH system up to date while
being forced to run an old kernel (2.6.16) not compatible with current
udev packages?
Is it possible these days to not have udev packages installed at all?
Or should I work on setting up a custom udev package with an an older
ver
2010/5/1 caleb :
> - patched setup script to run on ruby-1.9
> +Patch0: %{name}-ruby19.patch
> +%patch0 -p1
Some [widely bemoaned] changes to the way ruby handles string encoding
from 1.8 to 1.9 require changes in some scripts to run reliably. I
took a cue from several other patched
2010/4/24 Patryk Zawadzki :
> If %{__make} fails, your first target is -j1 :)
Good to know, thanks. Is the proper way to do this just to run
%{__make} -j1? I noticed this gets executed as make -j6 -j1 which
seems kinda clumsy.
In this case that did not fix my problem, but with some help from
deej
In an attempt to get emerillon packaged for PLD I've been working on
specs for the two missing deps, librest and libethos. Librest went ok
but I'm having fits with libethos.
Most PLD packages use the macro %{__make} for the build, but for some
reason that breaks the build whereas just make runs a
2010/4/14 Elan Ruusamäe :
> even now the version: tag matches
Yes, the version tag matches, but the base package is different and
they are in fact different versions! I looked at the upstream project
files the other day and they apparently have different branches of the
project that share parallel
I have the same problem with the builder script on my local machine
after upgrading rpm-build-tools.
cvs up builder did not fix it although there was a newer version.
Caleb
2010/4/9 Jan WIdeł :
> On Thu, 8 Apr 2010 20:51:38 +0200, Zsolt Udvari
> wrote:
>> Hi all!
>>
>> I've a problem on carme-s
ating around in dozens
of locations) is making me dizzy.
I have subscribed to the cvs commit list and will try to keep up with
what's current that way.
Caleb
2010/3/29 Elan Ruusamäe :
> On Monday 29 March 2010 14:48:05 Caleb Maclennan wrote:
>> Question about log messages. I noticed
Should I give a holler here or directly to somebody when I have a
commit or will things been seen and reviewed?
Question about log messages. I noticed after I committed a bump to the
version of hugin last night that most log messages for spec file
commits start with a leading dash. Does this have
Can somebody tell me who to get in touch with regarding commit access
to PLD spec files?
I requested access back in Nov of 2007 after submitting some patches
and specs. I was +1'd by Aria and Krystian as well as feedback from
Andrzej and Elan. I was then contacted and asked to turn in my desired
c
I have been working on setting up some servers using Amazons Elastic
Cloud Computing offering. If anyone is interested, I have created
a base image that can be used as a starting point for anyone else
wishing to run PLD as an Amazon Machine Image. The process of getting
a new image up and running i
On Fri, Nov 09, 2007 at 07:40:18PM -0700, Caleb Maclennan wrote:
> It throws a warning
> about unpackaged (doc) files on build
Would it be appropriate to throw something like the following at
the end of %install to suppress the error?
rm -rf $RPM_BUILD_ROOT%{_datadir}/docs/%{name}
On Sat, Nov 10, 2007 at 04:16:36AM +0200, Elan Ruusamäe wrote:
> but rather using rpmbuildroot paths use relative %doc from builddir, then
> documents get compressed too:
>
> %doc docs/*
Ok, this didn't quite make sense to me but I think I figured out
what you were after. See if this fits the bi
On Sat, Nov 10, 2007 at 04:14:38AM +0200, Elan Ruusamäe wrote:
> > %{_desktopdir}/*
>
> this is dangerous -- you might package %{_desktopdir}/kde if you don't look
> each time what you package.
Ok, I have specified these individually. I tried globing them with {,_server}
but that kind of globing
Thanks for the pointers Andrzej. I am attaching an updated
spec file with your changes.
Caleb
# $Revision:$, $Date:$
Summary:The GNU Lyric Display System
Name: lyricue
Version:1.9.6
Release:0.6
License:GPL
Group: X11/Applications/Graphics
URL:
On Fri, Nov 09, 2007 at 06:11:19PM -0700, Aria Stewart wrote:
> On Nov 9, 2007, at 5:49 PM, Andrzej Krzysztofowicz wrote:
> > We try to keep the BuildRoot entry as the last in this section.
> > Patch# just
> > after Sources.
>
> Indeed. The ./adapter script in the SPECS repo does a lot of this.
Hello all,
My thanks to everyone who has contributed to make PLD the great
distro that it is. I have been a user since a little before RA
was finalized and haven't missed a beat since. At last count
I have 5 TH and 14 AC systems and am the systems guru for 27 more
AC systems at a local ISP.
Up un
Building the DEVEL branch of librsvg seems to require rpm-pythonprov.
Index: librsvg.spec
===
RCS file: /cvsroot/SPECS/librsvg.spec,v
retrieving revision 1.99.2.7
diff -u -r1.99.2.7 librsvg.spec
--- librsvg.spec28 Feb 2006 15:0
100 matches
Mail list logo