FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 08-21-2010, 06:54 PM
Ray Rashif
 
Default TU application

On 22/08/2010, Ray Rashif <schivmeister@gmail.com> wrote:
> If Chris didn't sponsor you, I would. Good luck!

s/Chris/Thorsten/

I think I should leave computers and any machine with a keyboard alone
for today; making too many typos.


--
GPG/PGP ID: B42DDCAD
 
Old 08-22-2010, 10:46 AM
 
Default TU application

On Sat, 21 Aug 2010 20:42:50 +0200
Florian Pritz <bluewind@server-speed.net> wrote:
> Hi,
>
> I've been asked a few times to apply as a TU and finally decided to do
> so .
>
...*snip*...
>
> Thorsten Töpper asked me to become a TU and also wants to sponsor me.
> Thanks.
>
> If you want to know more, please ask. I'm not a good story writer
>
>
> [1] http://aur.archlinux.org/packages.php?SeB=m&K=bluewind
> [2] http://paste.xinu.at
> [3] http://git.server-speed.net/users/flo/filebin
>

I happily confirm to sponsor him so:

Let the discussion period begin!
--
Jabber: atsutane@freethoughts.de Blog: http://atsutane.freethoughts.de/
Key: 295AFBF4 FP: 39F8 80E5 0E49 A4D1 1341 E8F9 39E4 F17F 295A FBF4
 
Old 08-22-2010, 04:28 PM
Jaroslav Lichtblau
 
Default TU application

On Tue, Aug 17, 2010 at 10:43:23AM +0200, Lukáš Jirkovský wrote:
> Hello,
> the discussion about pulling ufoai into [community] made me thing
> about applying for a TU. Since I've got quite a lot of time recently I
> finally decided to apply for a TU position which I've been encouraged
> into several times in the past.
>
> My name is Lukas Jirkovsky. I'm from Pilsen, Czech Republic. Currently
> I'm pursuing my bachelors degree in computer science at the Faculty of
> Applied Sciences at the University of West Bohemia. I'm using Linux
> for about six years (I still have the old Mandrake 10.1 CD here). I
> used Slackware for several years but approximately 3 years ago I moved
> to Arch Linux which I immediately fell in love with ;-)
>
> Currently I maintain 94 packages in AUR. Several packages of mine got
> it's way into [community] and [extra] too. I can remember
> ttf-linux-libertine, geeqie, luminance and autopano-sift-c being ones.
> I'd like to move the klavaro package into community and maybe some
> other popular packages. I'm also very interested in bringing more
> graphics software to Arch Linux. Moving ufoai if wanted should be
> without problems too, I've got a decent connection at home. The last
> words about my packaging work is that I'm aware that some of my
> PKGBUILDS still uses contributor instead of maintainer. I'm slowly
> replacing these packages when a new version comes out or any other
> update is needed.
>
> Now something about my skills. I've a decent knowledge of C and C++
> and in my spare time I'm participating in the development of Hugin
> [1]. I know Java too, but I prefer C++ (templates are just so
> beautiful). I used to maintain the Arch-graphics repo [2] but since I
> switched to x86_64 I don't do regular builds (I'd have to rewrite some
> of the scripts first).
>
> I can build for both x86_64 and i686.
>
> best regards,
> Lukas Jirkovsky
>
> [1] http://hugin.sourceforge.net/
> [2] http://arch-graphics.kx.cz/
>

Hi Lukáš,
nice to see someone from the Czech Republic aplying for a TU!
Since so many people asking for discussion and none has been done yet,
here a short output from namcap for your AUR packages. All simple fixes,
I always liked your PKGBUILDs, so I didn't expect any bigger problems.

PKGBUILD (aacplus) W: Description should not contain the package name.
PKGBUILD (cdrtools) W: Description should not contain the package name.
PKGBUILD (gimp-plugin-texturize) E: Use $srcdir instead of $startdir/src
PKGBUILD (gimp-plugin-texturize) E: Use $pkgdir instead of $startdir/pkg
PKGBUILD (metisse-cvs) E: Use $srcdir instead of $startdir/src
PKGBUILD (metisse-cvs) E: Use $pkgdir instead of $startdir/pkg
PKGBUILD (nucleo-cvs) E: Use $srcdir instead of $startdir/src
PKGBUILD (nucleo-cvs) E: Use $pkgdir instead of $startdir/pkg
PKGBUILD (ocropus) E: Not enough md5sums: 2 needed
PKGBUILD (ossec-agent) E: File referenced in $startdir
PKGBUILD (ossec-local) E: File referenced in $startdir
PKGBUILD (ossec-server) E: File referenced in $startdir
PKGBUILD (targetware) E: Use $srcdir instead of $startdir/src
PKGBUILD (targetware) E: Use $pkgdir instead of $startdir/pkg

In your application, you didn't mention your age. So may I ask how old are you?
Good luck!

Cheers,
Jaroslav
 
Old 08-22-2010, 05:12 PM
Jaroslav Lichtblau
 
Default TU application

On Sat, Aug 21, 2010 at 08:42:50PM +0200, Florian Pritz wrote:
> Hi,

<snip>

> If you want to know more, please ask. I'm not a good story writer
>
>
> [1] http://aur.archlinux.org/packages.php?SeB=m&K=bluewind
> [2] http://paste.xinu.at
> [3] http://git.server-speed.net/users/flo/filebin
>
> --
> Florian Pritz -- {flo,bluewind}@server-speed.net
>

Hi Florian!
running namcap on your AUR packages gives this output:

PKGBUILD (blazeblogger-git) E: Use $pkgdir instead of $startdir/pkg
PKGBUILD (extract) W: Description should not contain the package name.
PKGBUILD (glark) W: Description should not contain the package name.
PKGBUILD (mbuffer) E: Use $srcdir instead of $startdir/src
PKGBUILD (mbuffer) E: Use $pkgdir instead of $startdir/pkg
PKGBUILD (perl-mail-checkuser) W: Missing Maintainer tag
PKGBUILD (portbunny) E: Use $pkgdir instead of $startdir/pkg
PKGBUILD (spampd) E: File referenced in $startdir

Besides that, I feel informed enough about you.
Good luck!
Jaroslav
 
Old 08-22-2010, 05:26 PM
Florian Pritz
 
Default TU application

On 22.08.2010 19:12, Jaroslav Lichtblau wrote:
> PKGBUILD (blazeblogger-git) E: Use $pkgdir instead of $startdir/pkg

Fixed for next release

> PKGBUILD (extract) W: Description should not contain the package name.

"extract" is used in a different context

> PKGBUILD (glark) W: Description should not contain the package name.

Fixed

> PKGBUILD (mbuffer) E: Use $srcdir instead of $startdir/src
> PKGBUILD (mbuffer) E: Use $pkgdir instead of $startdir/pkg

Fixed for next release

> PKGBUILD (perl-mail-checkuser) W: Missing Maintainer tag

Fixed for next release

> PKGBUILD (portbunny) E: Use $pkgdir instead of $startdir/pkg

This package doesn't build anymore with recent kernels (and breaks with
nearly every update), but I'll fix that if upstream decides to work on
it again.

> PKGBUILD (spampd) E: File referenced in $startdir

I use startdir here to generate a ChangeLog. If there is a better way
I'd like to know.

Or should I just forget that as nearly nobody else uses them?

>
> Besides that, I feel informed enough about you.
> Good luck!

Thanks for your feedback.


--
Florian Pritz -- {flo,bluewind}@server-speed.net
 
Old 08-22-2010, 05:49 PM
Jaroslav Lichtblau
 
Default TU application

On Sun, Aug 22, 2010 at 07:26:31PM +0200, Florian Pritz wrote:
> On 22.08.2010 19:12, Jaroslav Lichtblau wrote:
> > PKGBUILD (blazeblogger-git) E: Use $pkgdir instead of $startdir/pkg
>
> Fixed for next release
>
> > PKGBUILD (extract) W: Description should not contain the package name.
>
> "extract" is used in a different context
>
> > PKGBUILD (glark) W: Description should not contain the package name.
>
> Fixed
>
> > PKGBUILD (mbuffer) E: Use $srcdir instead of $startdir/src
> > PKGBUILD (mbuffer) E: Use $pkgdir instead of $startdir/pkg
>
> Fixed for next release
>
> > PKGBUILD (perl-mail-checkuser) W: Missing Maintainer tag
>
> Fixed for next release
>
> > PKGBUILD (portbunny) E: Use $pkgdir instead of $startdir/pkg
>
> This package doesn't build anymore with recent kernels (and breaks with
> nearly every update), but I'll fix that if upstream decides to work on
> it again.
>
> > PKGBUILD (spampd) E: File referenced in $startdir
>
> I use startdir here to generate a ChangeLog. If there is a better way
> I'd like to know.
>
> Or should I just forget that as nearly nobody else uses them?

Oh, fast response!
The generated ChangeLog is not included in the package, so why bothering with generating
it to the startdir anyway? Either put it in a directory like /usr/share/doc/spampd/ or
delete the whole line.

>
> >
> > Besides that, I feel informed enough about you.
> > Good luck!
>
> Thanks for your feedback.
>
>
> --
> Florian Pritz -- {flo,bluewind}@server-speed.net
>

Regards,
Jaroslav
 
Old 08-22-2010, 06:01 PM
Lukáš Jirkovský
 
Default TU application

Hi Jaroslav

On 22 August 2010 18:28, Jaroslav Lichtblau <tu@dragonlord.cz> wrote:
> On Tue, Aug 17, 2010 at 10:43:23AM +0200, Lukáš Jirkovský wrote:
>
> Hi Lukáš,
> nice to see someone from the Czech Republic aplying for a TU!
> Since so many people asking for discussion and none has been done yet,
> here a short output from namcap for your AUR packages. All simple fixes,
> I always liked your PKGBUILDs, so I didn't expect any bigger problems.
>
> PKGBUILD (aacplus) W: Description should not contain the package name.
> PKGBUILD (cdrtools) W: Description should not contain the package name.
> PKGBUILD (gimp-plugin-texturize) E: Use $srcdir instead of $startdir/src
> PKGBUILD (gimp-plugin-texturize) E: Use $pkgdir instead of $startdir/pkg
> PKGBUILD (metisse-cvs) E: Use $srcdir instead of $startdir/src
> PKGBUILD (metisse-cvs) E: Use $pkgdir instead of $startdir/pkg
> PKGBUILD (nucleo-cvs) E: Use $srcdir instead of $startdir/src
> PKGBUILD (nucleo-cvs) E: Use $pkgdir instead of $startdir/pkg
> PKGBUILD (ocropus) E: Not enough md5sums: 2 needed
> PKGBUILD (ossec-agent) E: File referenced in $startdir
> PKGBUILD (ossec-local) E: File referenced in $startdir
> PKGBUILD (ossec-server) E: File referenced in $startdir
> PKGBUILD (targetware) E: Use $srcdir instead of $startdir/src
> PKGBUILD (targetware) E: Use $pkgdir instead of $startdir/pkg

Thanks for posting the error list here. I didn't know about the
$startdir issues, because I did some sed magic when $pkgdir and
$srcdir were introduced locally to replace them and it seems I didn't
have to update these packages since that time. I'll fix that ASAP.

As for the ossec-* packages it's intentional. I expect the user
changes the configuration file which is a part of the package. I don't
want to bother users with need to change the checksums array every
time they change some of the settings and I didn't find any other
option how to exclude the file from checksums check.

> In your application, you didn't mention your age. So may I ask how old are you?
> Good luck!
>
> Cheers,
> Jaroslav
>
>

Sure you can ask. I'm 21.

Have a nice day,
Lukas
 
Old 08-22-2010, 06:33 PM
Florian Pritz
 
Default TU application

On 22.08.2010 19:49, Jaroslav Lichtblau wrote:
> On Sun, Aug 22, 2010 at 07:26:31PM +0200, Florian Pritz wrote:
>> On 22.08.2010 19:12, Jaroslav Lichtblau wrote:
>> > PKGBUILD (spampd) E: File referenced in $startdir
>>
>> I use startdir here to generate a ChangeLog. If there is a better way
>> I'd like to know.
>>
>> Or should I just forget that as nearly nobody else uses them?
>
> Oh, fast response!
> The generated ChangeLog is not included in the package, so why bothering with generating
> it to the startdir anyway? Either put it in a directory like /usr/share/doc/spampd/ or
> delete the whole line.

Okay reread the manpage and noticed I forgot to set the changelog
variable. Removed it for now.


--
Florian Pritz -- {flo,bluewind}@server-speed.net
 
Old 08-22-2010, 07:03 PM
Lukáš Jirkovský
 
Default TU application

> PKGBUILD (aacplus) W: Description should not contain the package name.
> PKGBUILD (cdrtools) W: Description should not contain the package name.
Intentional

> PKGBUILD (gimp-plugin-texturize) E: Use $srcdir instead of $startdir/src
> PKGBUILD (gimp-plugin-texturize) E: Use $pkgdir instead of $startdir/pkg
Fixed

> PKGBUILD (metisse-cvs) E: Use $srcdir instead of $startdir/src
> PKGBUILD (metisse-cvs) E: Use $pkgdir instead of $startdir/pkg
> PKGBUILD (nucleo-cvs) E: Use $srcdir instead of $startdir/src
> PKGBUILD (nucleo-cvs) E: Use $pkgdir instead of $startdir/pkg
I guess these can be safely removed. They must have shut down the
repository earlier this year (IIRC I built nucleo-cvs and metisse-cvs
in January or so). I can't contact the server anymore. It's a pity,
because it was really interesting project.

> PKGBUILD (ocropus) E: Not enough md5sums: 2 needed
I know about this one and I admit that it's my fault. The package
didn't work correctly neither with tesseract from [community] nor with
tesseract-svn from AUR (it's mentioned in comments). Currently I'm
waiting for a new version with which I'll fix all the mentioned
problems. There is version 4.3 tagged in repository but it wasn't
released as a source tarball. I'm thinking of trying this version
instead

> PKGBUILD (ossec-agent) E: File referenced in $startdir
> PKGBUILD (ossec-local) E: File referenced in $startdir
> PKGBUILD (ossec-server) E: File referenced in $startdir
Intentional

> PKGBUILD (targetware) E: Use $srcdir instead of $startdir/src
> PKGBUILD (targetware) E: Use $pkgdir instead of $startdir/pkg
I have problems running it because there is no package arts anymore. I
guess it can be safely removed too. Moreover nobody use it (only 3
votes and nobody complained about missing arts).
 
Old 08-22-2010, 09:46 PM
Eric Bélanger
 
Default TU application

On Sun, Aug 22, 2010 at 2:33 PM, Florian Pritz
<bluewind@server-speed.net> wrote:
> On 22.08.2010 19:49, Jaroslav Lichtblau wrote:
>> On Sun, Aug 22, 2010 at 07:26:31PM +0200, Florian Pritz wrote:
>>> On 22.08.2010 19:12, Jaroslav Lichtblau wrote:
>>> > PKGBUILD (spampd) E: File referenced in $startdir
>>>
>>> I use startdir here to generate a ChangeLog. If there is a better way
>>> I'd like to know.
>>>
>>> Or should I just forget that as nearly nobody else uses them?
>>
>> Oh, fast response!
>> The generated ChangeLog is not included in the package, so why bothering with generating
>> it to the startdir anyway? Either put it in a directory like /usr/share/doc/spampd/ or
>> delete the whole line.
>
> Okay reread the manpage and noticed I forgot to set the changelog
> variable. Removed it for now.
>

The changelog variable is meant to be used for a ChangeLog listing
changes made to the PKGBUILD and other build files, not the upstream
ChangeLog. If you want the upstream ChangeLog to be installed, IMO it
would be better to put it in /usr/share/doc/spampd/

>
> --
> Florian Pritz -- {flo,bluewind}@server-speed.net
>
>
 

Thread Tools




All times are GMT. The time now is 12:43 AM.

VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org