> A few to look at and verify.
>
> AGPL-3+ | BSL-1.0 openvpn3-core/deps/vcpkg-
> ports/asio/vcpkg.json
> AGPL-3+ | GPL-3openvpn3-
> core/openvpn/asio/asioresolverres.hpp
> AGPL-3+ | Unicode-DFS-2015 openvpn3-core/openvpn/common/unicode-
> impl.hpp
> AGPL
>> * Package name : openvpn3-client
> BTW, why it is named this way?
> Is it client-only now, without the server part?
> Previous package is named just "openvpn", it acts
> as both client or server (actually the two roles are
> symmetric, it can be both). If new openvpn is like
> this, I sug
> The issue and ITP talks about there being two packages, a library part
> and the client part. Has this changed (I cannot find the library part.)
I did start out to have different packages (client, library, dev); but
after discussing with upstream, I decided to mirror the upstream
(tarball) relea
code-impl.hpp
* d/README: update dfsg motivation
* remove sum files (see d/README.source)
Regards,
Additional discussion on the packaging with upstream can be found here:
https://github.com/OpenVPN/openvpn3-linux/issues/193
--
Marc Leeman
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "dvdauthor":
* Package name : dvdauthor
Version : 0.7.2-2
Upstream contact : Lawrence D'Oliveiro
* URL : https://dvdauthor.sourceforge.net
* License
> I have just followed the link to
> http://www.auto.tuwien.ac.at/~mkoegler/index.php/pth
> and found Debian packages there, right from pthsem's author. The package
> should be taken from there - do you agree?
I haven't done anything on pthsem (yet); I will need to do some work on
it since eibd-se
> George Danchev wrote:
>> * Generally, your sponsor(s) would want to test the packages, however
>> that would need certain home automation infrastructure to be in place
>> which is not available everywhere, so you might need to suggest a way
>> to simulate their operation if that is easily poss
Dear mentors,
I'm looking for someone that would be interested in sponsoring a number
of packages related to home automation:
see:
http://plugcomputer.org/plugforum/index.php?topic=824.0
Though it is described to run on armel; I've ran it on arm, mips,
powerpc, i386 and amd64 too (etch, lenny, s
> > As long as my sponsors don't mind uploading the packages and I can use
> > aloith to cooperate with others, I don't feel the need anymore to
> > continue and try again for full DD; though I'm sure I would have
> > contributed more (a number of packages never found a sponsor, so I
> > dropped th
> just trying to contribute to Debian, I am not looking for a
> second job. But currently I feel kept out by a bureaucratic
> and slow procedure.
Same here, I gave up a couple of years ago. Currently I maintain a
number of packages and contribute to others in Debian.
As long as my sponsors don't
> [cut]
> I forgot the ITP number: 320045
I have been testing k9copy on a number of my DVDs; but it rarely manages
to shrink a DVD properly (1-1).
I might be missing something, but what seems to be a problem is:
1. you cannot adjust the shrink ratio: on analysing a DVD, it does
some guess
Added most comments and improved the packages, the lintian comments are
(for the package quake3):
W: quake3: binary-without-manpage q3a
W: quake3: binary-without-manpage q3ded
I'll add those next, but it might take some weeks.
The packages can be found here:
http://scorpius.homelinux.org/~marc/de
> > Do you know of any efforts to create DFSG q3a content, which would allow
> > migration into main? (just curious)
>
> There is, but it's in very early stage:
> http://www.planetgargoyle.com/openarena/
emphasis on *very* :)
If it matures, I'll add it as an alternative, next to installation of
> > /var/cache/install/$PACKAGE?
> Why not /var/cache/$package/
> maybe /v/c/$package/install/
OK, I took the last one:
[EMAIL PROTECTED] sources]$ ls -al /var/cache/quake3-data/install/
total 78336
drwxr-xr-x 2 root root 16 2005-11-10 23:33 .
drwxr-xr-x 3 root root 16 2005-11-10 23
> > Indeed /root/ feels like a bad place. I would suggest /tmp/ or something
> > in /var/. Maybe /var/cache/, because "information" isn't "lost" if it gets
> > deleted?
>
> /var/cache/install/$PACKAGE?
Looking at the already present directories in /var/cache/ it would be
more something along th
> Right; You can also do whatever you want to a file whose name is
> outputted by a successful invocation of mktemp, but note that this
> probably wont play nice with wget. If fn=`mktemp`, and you wget -O
> $fn, then wget will probably call its outupt $fn.1, since $fn exists
> (as a requirement fo
> That is a tag + security race condition between rm and mkdir. You'll
> want to use mktemp -d instead.
fixed, tnx.
> I didn't look at your script closely; there may be other problems.
> Nothing should ever get written to /tmp/ except if the output filename
> is the result of a successful ($?==0
I addressed most of the issues, except:
[EMAIL PROTECTED] sources]$ lintian quake3-data_2_all.deb
W: quake3-data: possibly-insecure-handling-of-tmp-files-in-maintainer-script
postinst:211
[EMAIL PROTECTED] sources]$ lintian quake3_0.1-4_i386.deb
W: quake3: binary-without-manpage q3a
the new pack
> (most of these problems are probably inherited from the quake2
> packaging you used). You will have to fix most of these before
> someone should sponsor the package.
They were all quickly fixed. My intention was to see if anyone was
interested in the first place, then do more fundamental functio
> > > > Anyone intersted in answering the call?
> > > A link to actual packages files would be good...
> >
> > http://scorpius.homelinux.org/~marc/debian/
>
> Any reason why you didn't send this to the list but only to me?
> You will certainly get more useful feed back by actually posting
> the l
Hi,
I've been maintaining a number of packages for about 5 years. For these
packages, I've been working with a number of DDs and since the
cooperation was so satisfactory, I never had the need (and for a couple
of years, the time) to apply for DD myself.
Last week, I made packages for Quake III.
With some delay; but a version of the package can be found on
http://scorpius.homelinux.org/~marc/debian/
(I saw that there was some activity in this 'lost' directory; so here
goes again)...
Still looking for someone to upload if interested. Shoot, I really
should look into becoming a deb. dev.
With some delay; but a version of the package can be found on
http://scorpius.homelinux.org/~marc/debian/
(I saw that there was some activity in this 'lost' directory; so here
goes again)...
Still looking for someone to upload if interested. Shoot, I really
should look into becoming a deb. dev.
Hello, anyone interested in sponsering these packages (after evaluation
and approvement of course):
[EMAIL PROTECTED] result]$ lintian libtk-codetext-perl_0.3.1_all.deb
E: libtk-codetext-perl: changelog-file-missing-in-native-package
[EMAIL PROTECTED] result]$ lintian libsyntax-highlight-perl_1.0
> what can I do?
I do not recognise the error, I would suggest you try a crash test in
the GNU/autotools, which is never a bad idea for a develper anyway.
This is an overview:
http://lesbos.esat.kuleuven.ac.be/~mleeman/downloads/athens-opensource-0.4.pdf
--
greetz, marc
because of net
Feedback please? If there are no objections, sponsor for this package?
* Package name: fortunes-farscape
Version : 0.1
Upstream Author : Marc Leeman <[EMAIL PROTECTED]>
* URL : http://members.chello.be/cr50624/debian/farscape
* License : GPL
Descr
Feedback please? If there are no objections, sponsor for this package?
* Package name: fortunes-farscape
Version : 0.1
Upstream Author : Marc Leeman <[EMAIL PROTECTED]>
* URL : http://members.chello.be/cr50624/debian/farscape
* License : GPL
Descr
> Ok, i don't configured http-access very well. So you're not able to browse
> there at the moment. But direct access on the *.deb file or using apt-get
> should work...
>
> > Could you provide source packages? See dpkg-source(1) or debuild(1)
> > for more info.
I seem to have already 2 up-to-d
> Ok, i don't configured http-access very well. So you're not able to browse
> there at the moment. But direct access on the *.deb file or using apt-get
> should work...
>
> > Could you provide source packages? See dpkg-source(1) or debuild(1)
> > for more info.
I seem to have already 2 up-to-d
A second call for a sponsor for the package ogmtools.
The package enables e.g. encoding media files (xvid, ...) with an ogg
audio stream instead of mp3 encoded audio.
The tools are used in transcode (excellent video transcoding tool
(maintained by Christian Marillat).
Upstream: http://www.bunk
A second call for a sponsor for the package ogmtools.
The package enables e.g. encoding media files (xvid, ...) with an ogg
audio stream instead of mp3 encoded audio.
The tools are used in transcode (excellent video transcoding tool
(maintained by Christian Marillat).
Upstream: http://www.bunk
The package is already in a "working" state, but I need to write
manpages etc for them.
deb http://lesbos.esat.kuleuven.ac.be/~mleeman/debian unstable/
deb-src http://lesbos.esat.kuleuven.ac.be/~mleeman/debian unstable/
If anyone agrees to sponsor this, you should know that I will be gone
for ab
The package is already in a "working" state, but I need to write
manpages etc for them.
deb http://lesbos.esat.kuleuven.ac.be/~mleeman/debian unstable/
deb-src http://lesbos.esat.kuleuven.ac.be/~mleeman/debian unstable/
If anyone agrees to sponsor this, you should know that I will be gone
for a
Well, I am going to ask advice _again_ in a naming collision problem (I
seem to get in problems with this quite often).
The situation:
I am packaging the nvrec tools from Justin Schuman since a couple of
months (sponsor is in the process of agreeing the package ;), but he's
on holidays now).
It ha
Well, I am going to ask advice _again_ in a naming collision problem (I
seem to get in problems with this quite often).
The situation:
I am packaging the nvrec tools from Justin Schuman since a couple of
months (sponsor is in the process of agreeing the package ;), but he's
on holidays now).
It h
Well, my previous package (problems and all) seems to get approval of my
mentor, so I thought it was time to start thinking about me second
package.
My reasoning is that I never package anything that I do not use or am
not interested in (just a matter of still spending enough times when
work is ge
Well, my previous package (problems and all) seems to get approval of my
mentor, so I thought it was time to start thinking about me second
package.
My reasoning is that I never package anything that I do not use or am
not interested in (just a matter of still spending enough times when
work is g
> > > The package is locate at pumuki.hispalinux.es/debian/mcplay/
> Is it packed? cannot find it from packages.debian.org in any of the
> debs.
Yes, but not in debian (yet)
deb http://lesbos.esat.kuleuven.ac.be/~mleeman/debian unstable/
deb-src http://lesbos.esat.kuleuven.ac.be/~mleeman/debian un
> The package is locate at pumuki.hispalinux.es/debian/mcplay/
>
> mcplay is a c-clone of the popular python frontend for mpg123/ogg123
> which seems to be as powerfull as the parent package.
The nvrec software also has a binary called mcplay
together with mcthrow and mccatch (multicast), it enbl
> > > The package is locate at pumuki.hispalinux.es/debian/mcplay/
> Is it packed? cannot find it from packages.debian.org in any of the
> debs.
Yes, but not in debian (yet)
deb http://lesbos.esat.kuleuven.ac.be/~mleeman/debian unstable/
deb-src http://lesbos.esat.kuleuven.ac.be/~mleeman/debian u
> The package is locate at pumuki.hispalinux.es/debian/mcplay/
>
> mcplay is a c-clone of the popular python frontend for mpg123/ogg123
> which seems to be as powerfull as the parent package.
The nvrec software also has a binary called mcplay
together with mcthrow and mccatch (multicast), it enb
I must be missing something here, I want the package to show a not when
installing to indicate that custom builds _are_ very useful for the time
being, but guess what, it's not asking :(
Any help?
[EMAIL PROTECTED] nvrec-20020624]$ sudo ./debian/nvrec.config
debconf (developer): frontend started
I must be missing something here, I want the package to show a not when
installing to indicate that custom builds _are_ very useful for the time
being, but guess what, it's not asking :(
Any help?
[marc@scorpius nvrec-20020624]$ sudo ./debian/nvrec.config
debconf (developer): frontend started
d
> could keep on top of these. I have tried to get the ball rolling by
> answering a couple of sponsorship requests today, but there are several
> others with subjects containing "sponsor", "RFS", or in one case "spronsor".
Sure, take your time :)
I already had some _very_ good comments and sugge
> could keep on top of these. I have tried to get the ball rolling by
> answering a couple of sponsorship requests today, but there are several
> others with subjects containing "sponsor", "RFS", or in one case "spronsor".
Sure, take your time :)
I already had some _very_ good comments and sugg
> I waited 6 weeks before AM assigned. (I had advocate when applied.)
> My AM does not yet contact me few days while I see his posting on ML.
> But right after I moved to cue with AM, many people got AM. Somewhat
> random.
> You can see this nm.debin.org/nmlist.php.
> People are busy now due to m
> I waited 6 weeks before AM assigned. (I had advocate when applied.)
> My AM does not yet contact me few days while I see his posting on ML.
> But right after I moved to cue with AM, many people got AM. Somewhat
> random.
> You can see this nm.debin.org/nmlist.php.
> People are busy now due to
The situation is as follows:
I intend (am) packaging nvrec (for a small audience at this time ;) ),
and Nicolas is looking through the package to check compliance.
Next to making some obviously good remarks about the format, the
following pops up:
nvrec is dependent on liblame or liblame-dev, wh
> What about autobuilders, or anyone who might have to do a non-maintainer
> upload of the package at some point in the future?
Autobuilders will have a package that is tailored to their system
(optimised, hence running faster).
Somebody that does a non-maintainer build (not me), will have to che
Hello again,
I have a general question, that I did find a answer for in the debian
policy guide (don't falme me if I missed it :(( )
Nicolas gave me the advice to exclude all processor optimisations in the
nvrec package, so I added the configure flags
--enable-mmxcheck
--enable-cpucheck
that are
> Why don't you suggest upstream to use libogg instead/too?
I do not think that ogg is supported in common video compressed formats.
I guess it's just a matter of comply with "standards".
I am not aware of video (trans)coders that use ogg for audio compression
(yet).
--
greetz, marc
> Why don't you suggest upstream to use libogg instead/too?
I do not think that ogg is supported in common video compressed formats.
I guess it's just a matter of comply with "standards".
I am not aware of video (trans)coders that use ogg for audio compression
(yet).
--
greetz, marc
> As far as I know, lame is not in Debian, and can't be because of a
> patent... :-(
> So I guess nvrec will at best belong to contrib. Were you aware of this
> issue?
I know that lame and all related mp3 encoders were not in debian because
of this problem, but it completely slipped my mind when
> As far as I know, lame is not in Debian, and can't be because of a
> patent... :-(
> So I guess nvrec will at best belong to contrib. Were you aware of this
> issue?
I know that lame and all related mp3 encoders were not in debian because
of this problem, but it completely slipped my mind when
Version: 20020530-3
Priority: extra
Section: x11
Maintainer: Marc Leeman <[EMAIL PROTECTED]>
Depends: libc6 (>= 2.2.4-4), liblame0 (>= 3.91-0.1)
Architecture: i386
Filename: unstable/nvrec_20020530-3_i386.deb
Size: 220132
MD5sum: 8c24d10f5c7f11c9da237e4e18177d6b
Description: a high quality,
Version: 20020530-3
Priority: extra
Section: x11
Maintainer: Marc Leeman <[EMAIL PROTECTED]>
Depends: libc6 (>= 2.2.4-4), liblame0 (>= 3.91-0.1)
Architecture: i386
Filename: unstable/nvrec_20020530-3_i386.deb
Size: 220132
MD5sum: 8c24d10f5c7f11c9da237e4e18177d6b
Description: a high quality,
56 matches
Mail list logo
