Some preliminary comments as I have not yet had time to look at the
package proper:
- the diff.gz is pretty much empty, it just patches the
debian/changelog. I have not been able to verify if the upstream
tarballs contain debian/* as the files do not seem to be on the sf.net
mirrors yet. From the
Some preliminary comments as I have not yet had time to look at the
package proper:
- the diff.gz is pretty much empty, it just patches the
debian/changelog. I have not been able to verify if the upstream
tarballs contain debian/* as the files do not seem to be on the sf.net
mirrors yet. From the
> * Does it really have no command-line flags at all? The manpage
> seems to say so.
So far there are no command-line flags, you can just specify the name
of a file to open. I still gave the manpage a bit of a polish as it
was really dry!
> * Have a look at
> http://lists.debian.org/debian-leg
> * Does it really have no command-line flags at all? The manpage
> seems to say so.
So far there are no command-line flags, you can just specify the name
of a file to open. I still gave the manpage a bit of a polish as it
was really dry!
> * Have a look at
> http://lists.debian.org/debian-leg
age name: sailcut
Version : 0.7.0
Upstream Authors: Robert Lainé <[EMAIL PROTECTED]>,
Jeremy Lainé <[EMAIL PROTECTED]>
* URL : http://sailcut.sourceforge.net/
* License : GPL
Description : A sail design and plotting software
S
age name: sailcut
Version : 0.7.0
Upstream Authors: Robert Lainé <[EMAIL PROTECTED]>,
Jeremy Lainé <[EMAIL PROTECTED]>
* URL : http://sailcut.sourceforge.net/
* License : GPL
Description : A sail design and plotting software
S
> Currently, the stable version of drbd is the 0.6.x series. A new
> version is on the way, the 0.7.x series. I'd like to package the
> new 0.7.x version in debian, but keep the 0.6.x series in Debian as
> well. How should I go about this?
If the 0.7.x series is going to be the development versi
> Currently, the stable version of drbd is the 0.6.x series. A new
> version is on the way, the 0.7.x series. I'd like to package the
> new 0.7.x version in debian, but keep the 0.6.x series in Debian as
> well. How should I go about this?
If the 0.7.x series is going to be the development versi
Hi again Thomas,
I just had a look at your control file.. it's HUGE as you define all the
kernel-lis-modules-2.4.26-1-(386|586tsc|etc..) packages! I suggest you
take a look at how alsa or pcmcia-cs are packaged and create an
"lis-source" package in your control file.
You should not be building a
> Uploaded to http://mentors.debian.org/
Failed to fetch
http://mentors.debian.net/debian/pool/main/l/lis/lis_2.16.16.orig.tar.gz
404 Not Found
Looks like you didn't include the original source with your upload. This
is because your package version is neither -0 nor -1, so dpkg-genchanges
did no
Hi again Thomas,
I just had a look at your control file.. it's HUGE as you define all the
kernel-lis-modules-2.4.26-1-(386|586tsc|etc..) packages! I suggest you
take a look at how alsa or pcmcia-cs are packaged and create an
"lis-source" package in your control file.
You should not be building a
> Uploaded to http://mentors.debian.org/
Failed to fetch
http://mentors.debian.net/debian/pool/main/l/lis/lis_2.16.16.orig.tar.gz
404 Not Found
Looks like you didn't include the original source with your upload. This
is because your package version is neither -0 nor -1, so dpkg-genchanges
did no
> A better solution would be detecting whether a password is needed
> (i.e. the debian-sys-maint or whatever the account is called is not
> available) and if so, prompt the user via debconf at purge.
Trying to be guess whether a password is needed seems rather risky as
the database could very well
Upon purging a package, it is expected that all installed data should be
removed. The package "diogenes" installs a MySQL database and a MySQL
user by prompting the user via debconf for the admin user/password.
I want to give users the possibility to remove that database and user
when the package
> A better solution would be detecting whether a password is needed
> (i.e. the debian-sys-maint or whatever the account is called is not
> available) and if so, prompt the user via debconf at purge.
Trying to be guess whether a password is needed seems rather risky as
the database could very well
Upon purging a package, it is expected that all installed data should be
removed. The package "diogenes" installs a MySQL database and a MySQL
user by prompting the user via debconf for the admin user/password.
I want to give users the possibility to remove that database and user
when the package
Hi Matthijs,
When you have a multibinary package, debian/tmp is the default place
where files get put. It's then up to you to move those files out of
there to put them into the various binary packages' directories, for
instance using dh_movefiles (see manpage) if you use debhelper.
In your case,
Hi Matthijs,
When you have a multibinary package, debian/tmp is the default place
where files get put. It's then up to you to move those files out of
there to put them into the various binary packages' directories, for
instance using dh_movefiles (see manpage) if you use debhelper.
In your case,
Hi Matthew,
> I have gone ahead and made the changes so that you can see them in
> action. This is done in 0.9.9.3-5 which I have uploaded to your
> queue. As far as I can tell, that deals with the last item on your
> initial review of the package, let me know if you find anything
> else!
Have yo
Hi Matthew,
> I have gone ahead and made the changes so that you can see them in
> action. This is done in 0.9.9.3-5 which I have uploaded to your
> queue. As far as I can tell, that deals with the last item on your
> initial review of the package, let me know if you find anything
> else!
Have yo
> Would this be ok?
I have gone ahead and made the changes so that you can see them in
action. This is done in 0.9.9.3-5 which I have uploaded to your queue.
As far as I can tell, that deals with the last item on your initial
review of the package, let me know if you find anything else!
Jeremy
-
> Upload it to my queue (as described at
done
> I'd say that if the problem can be detected at the time the config
> script runs
I've thought about it, and yes, it *can* be done though it requires
sucking a wwwconfig-common script into the config script, as we cannot
depend on wwwconfig-common b
> Would this be ok?
I have gone ahead and made the changes so that you can see them in
action. This is done in 0.9.9.3-5 which I have uploaded to your queue.
As far as I can tell, that deals with the last item on your initial
review of the package, let me know if you find anything else!
Jeremy
-
> Upload it to my queue (as described at
done
> I'd say that if the problem can be detected at the time the config
> script runs
I've thought about it, and yes, it *can* be done though it requires
sucking a wwwconfig-common script into the config script, as we cannot
depend on wwwconfig-common b
> > * I never got asked the DB admin questions, so installation
> > failed.
I think I've got it : diogenes.config tried to figure out the database
admin and password by using wwwconfig-common's mysql-localadmpass.get
(which reads /etc/mysql/my.cnf /var/lib/mysql/my.cnf ~/.my.cnf) and if
it got an
> > * I never got asked the DB admin questions, so installation
> > failed.
I think I've got it : diogenes.config tried to figure out the database
admin and password by using wwwconfig-common's mysql-localadmpass.get
(which reads /etc/mysql/my.cnf /var/lib/mysql/my.cnf ~/.my.cnf) and if
it got an
> > * Automatic installation failed to properly install the apache
> > config.
Ok, got it, /etc/diogenes/apache.conf needed to be created before
calling the wwwconfig-common scripts that get it included in httpd.conf!
The fixes in my previous email as well as this one are included in the
0.9.9.3-
> > * Automatic installation failed to properly install the apache
> > config.
Ok, got it, /etc/diogenes/apache.conf needed to be created before
calling the wwwconfig-common scripts that get it included in httpd.conf!
The fixes in my previous email as well as this one are included in the
0.9.9.3-
Hi Matthew,
Thanks for taking the time to look at the package! I have a few
questions, especially regarding the database configuration.
> * No WNPP bug filed.
fixed, I have filed an ITP
> * Communicates with the user via the console. Consider using debconf
> notes instead if it's vitally impor
Hi Matthew,
Thanks for taking the time to look at the package! I have a few
questions, especially regarding the database configuration.
> * No WNPP bug filed.
fixed, I have filed an ITP
> * Communicates with the user via the console. Consider using debconf
> notes instead if it's vitally impor
Hi!
> After this upload only two wishlist bugs and one important
> (segfault, unreproducible on my system, being investigated) will be
> left.
I get a segmentation fault on my system, it's pretty strange.. If I
just run xcruise, the velocity starts to go negative, and increasingly
so (it goes to
Hi!
> After this upload only two wishlist bugs and one important
> (segfault, unreproducible on my system, being investigated) will be
> left.
I get a segmentation fault on my system, it's pretty strange.. If I
just run xcruise, the velocity starts to go negative, and increasingly
so (it goes to
> Aarrrgh! If you'd happened to package this a couple of months
> ago, I would have been so incredibly happy.
Ah well.. Diogenes *has* been packaged since 2 Dec 2003 but I wanted to
make sure the packages were rock solid before looking for a sponsor :)
> If you can hold off for a couple of d
> Aarrrgh! If you'd happened to package this a couple of months
> ago, I would have been so incredibly happy.
Ah well.. Diogenes *has* been packaged since 2 Dec 2003 but I wanted to
make sure the packages were rock solid before looking for a sponsor :)
> If you can hold off for a couple of d
> Experience, probably. Time is the pressing issue. Out of interest,
> what does diogenes do (apart from WebDAV, which isn't of pressing
> interest to me personally) that other content management systems, such
> as MySource, don't do?
I have looked through the MySource documentation and I won't
Hi!
I am still looking for a sponsor for Diogenes! I am sure there is
someone with some PHP/MySQL/debconf experience out there to look at the
packages?
Cheers,
Jeremy
On Mon, 29 Mar 2004 15:02:27 +0200
Jeremy Lainé <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am looking fo
> Experience, probably. Time is the pressing issue. Out of interest,
> what does diogenes do (apart from WebDAV, which isn't of pressing
> interest to me personally) that other content management systems, such
> as MySource, don't do?
I have looked through the MySource documentation and I won't
Hi!
I am still looking for a sponsor for Diogenes! I am sure there is
someone with some PHP/MySQL/debconf experience out there to look at the
packages?
Cheers,
Jeremy
On Mon, 29 Mar 2004 15:02:27 +0200
Jeremy Lainé <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am looking fo
Hello,
I am looking for a sponsor for "Diogenes", a web content management system.
Here is the relevant information:
Package : diogenes
License : GPL v2
Upstream : Jeremy Lainé <[EMAIL PROTECTED]>
URL : http://opensource.polytechni
Hello,
I am looking for a sponsor for "Diogenes", a web content management system.
Here is the relevant information:
Package : diogenes
License : GPL v2
Upstream : Jeremy Lainé <[EMAIL PROTECTED]>
URL : http://opensource.polytechni
Cancel my last, I hadn't seen the messages on debian-devel :)
Jeremy
--
http://www.jerryweb.org/ : JerryWeb.org
http://sailcut.sourceforge.net/ : Sailcut CAD
http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
If someone is interested in working on packages for sylpheed-claws
(please, pretty please as Gustavo Noronha Silva is currently
unavailable!), you can use the diffs I put online to save a little time.
I took Gustavo's patches for 0.9.6 and made the necessary changes to
make them work for sylpheed-
Cancel my last, I hadn't seen the messages on debian-devel :)
Jeremy
--
http://www.jerryweb.org/ : JerryWeb.org
http://sailcut.sourceforge.net/ : Sailcut CAD
http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
If someone is interested in working on packages for sylpheed-claws
(please, pretty please as Gustavo Noronha Silva is currently
unavailable!), you can use the diffs I put online to save a little time.
I took Gustavo's patches for 0.9.6 and made the necessary changes to
make them work for sylpheed-
Thanks for all the input! From this discussion I conclude that in my
package's case there is no call for db_input in postinst, so I just
commented out those calls and lintian/linda are happy :)
Maybe it would be useful to summarise the cases where you are pretty
forced to use db_input calls in pos
Thanks for all the input! From this discussion I conclude that in my
package's case there is no call for db_input in postinst, so I just
commented out those calls and lintian/linda are happy :)
Maybe it would be useful to summarise the cases where you are pretty
forced to use db_input calls in pos
Hi!
I am trying to put the finishing touches on a package of Diogenes, a
web content management system. The package relies on a MySQL database,
and this database is created based on some information provided by the
user through debconf. I am down to one lintian warning :
W: diogenes: postinst-use
Hi!
I am trying to put the finishing touches on a package of Diogenes, a
web content management system. The package relies on a MySQL database,
and this database is created based on some information provided by the
user through debconf. I am down to one lintian warning :
W: diogenes: postinst-use
> >To achieve this I use the "deb-makepkg" script below.
> >
> Thanks a lot, I will look at this. Shouldn't this advertised
> publicly, and a package made for it?
I have rewritten my script in Perl, cleaned it up, removed hard coded
values and now both package name and version are extracted from
> AFAIK, this is not OK. Though I used to do it myself too. The
> correct way, I believe is to make a tar.gz file, like the one which
> is online, and build the Debian package from that.
To achieve this I use the "deb-makepkg" script below. You need to
adjust the BUILDIR to wherever you build your
Sweet package, I got it to run on Apache2 in 3 minutes flat. I am
unfortunately not a DD so lets hope someone steps up!
Thanks for the good work and good luck..
Jeremy
--
http://www.jerryweb.org/ : JerryWeb.org
http://sailcut.sourceforge.net/ : Sailcut CAD
http://mpf70.sourceforge.net
Sweet package, I got it to run on Apache2 in 3 minutes flat. I am
unfortunately not a DD so lets hope someone steps up!
Thanks for the good work and good luck..
Jeremy
--
http://www.jerryweb.org/ : JerryWeb.org
http://sailcut.sourceforge.net/ : Sailcut CAD
http://mpf70.sourceforge.net
> You should probably subscribe to buildd-discuss at nocrew.org.
done, but no reply so far.
In the meantime, I have started work using your package as a base, and
have got the buildd package to generate an /etc/default/buildd via
debconf. It is structured exactly like the current
/etc/buildd/buil
> You should probably subscribe to buildd-discuss at nocrew.org.
done, but no reply so far.
In the meantime, I have started work using your package as a base, and
have got the buildd package to generate an /etc/default/buildd via
debconf. It is structured exactly like the current
/etc/buildd/buil
> You might be interested in
> http://www.whinlatter.uklinux.net/buildd/
Definitely, I'm looking through it right now.
> You should probably subscribe to buildd-discuss at nocrew.org.
Done, and browsing through the archives I see I'm going pretty much
the same way as you as I also rely on autoco
> You might be interested in
> http://www.whinlatter.uklinux.net/buildd/
Definitely, I'm looking through it right now.
> You should probably subscribe to buildd-discuss at nocrew.org.
Done, and browsing through the archives I see I'm going pretty much
the same way as you as I also rely on autoco
Hi!
I am interested in becoming a Debian developer and have already
produced a number of Debian packages, but they fall in the "pet
packages" category referred to in another thread on this list. The
most recent ones are mpf70-source and mpf70-utils, respectively the
source for a kernel module (bui
Hi!
I am interested in becoming a Debian developer and have already
produced a number of Debian packages, but they fall in the "pet
packages" category referred to in another thread on this list. The
most recent ones are mpf70-source and mpf70-utils, respectively the
source for a kernel module (bui
58 matches
Mail list logo
