Bug#283005: ispCP debian package
On Mon, Jun 18, 2007 at 03:41:20PM -0500, Raphael wrote: > > I'm not sure about this, but I think DD's won't like upgrade stuff > from a package that never existed in the Debian rep to a new coming > one. That sounds perfectly reasonable to me. Specially if there has been a debian package around, even if not part of Debian. -- Robert Millan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#283005: ispCP debian package
On 18/06/07, Hendrik Frenzel <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Raphael schrieb: > Hello, > > On 18/06/07, Hendrik Frenzel <[EMAIL PROTECTED]> wrote: > > Well, the plans are to provide the debian/ scripts from upstream; and > > of course making any required change to ispCP so there's no need of > > applying any patch for the Debian package. > > And as you may see in http://www.isp-control.net/ispcp/ticket/394 > > there are still some thing to do. > > > If you wish to help the packaging I guess we can work together, so > > maybe you can get svn access (I'll talk to the others about all > > this.). > I think an idependend debian/ might be the better solution, as it is not recommended in upstream source[1], but it is a good thing working together on packaging. Well, not really, because it would be what is know as a Debian-native package; and that's ok, mainly because the default Makefile's and configs are meant to work with Debian. I already have clean vhcs packages (sarge only) and already work on ispcp (sid), so you don't have to reinvent the wheel and start from scratch. I can inject my files into SVN if I got access to it, but at the actual state I prefer to send you my debian/ as tar.gz. I don't have plans on starting packaging until the ticket I mentioned on my last message is closed. And like I said, I want to make all the changes directly into the source so there's no need to patch anything. > I think in about 2-4 Weeks the 1st packages can be tested. > > Only the update-path from vhcs to ispcp might be a not so trivial > problem, because the database names and many paths > have changed. > > > I'm not sure about this, but I think DD's won't like upgrade stuff > > from a package that never existed in the Debian rep to a new coming > > one. You would have to provide that feature on your own packages. > > But I think you'll want to wait until our vhcs to ispCP script is > ready. Ok, vhcs never existed in official debian repositories, but i got many users who installed vhcs off my old apt.scunc.it and they should also be able to use apt / dpkg for easy upgrading their installations. I think a clean upgrade between vhcs and ispcp is a must. I know. I can tell you I'm one of them ;-) but I don't have to forget the fact that it never existed in the Debian rep, so an upgrade system will be considered pointless in the main repository. Bye Hendrik [1] http://people.debian.org/~daniel/documents/packaging.html#debian-directory - -- I am chaos. I am the substance from which your artists and scientists build rhythms and rhimes. I am the spirit with which your children and clowns laugh in happy anarchy. I am chaos. I am alive, and I tell you that you are free. - Eris, Goddess Of Chaos, Discord & Confusion. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGdvr7jWcQfAgCZA8RCN9oAKDNu4VioyA9CECSfjKIZF8ZMsoStACg2r/v YiUYnJO3h5cWiVzXNo1IsLI= =v4Xz -END PGP SIGNATURE- -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#283005: ispCP debian package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Raphael schrieb: > Hello, > > On 18/06/07, Hendrik Frenzel <[EMAIL PROTECTED]> wrote: > > Well, the plans are to provide the debian/ scripts from upstream; and > > of course making any required change to ispCP so there's no need of > > applying any patch for the Debian package. > > And as you may see in http://www.isp-control.net/ispcp/ticket/394 > > there are still some thing to do. > > > If you wish to help the packaging I guess we can work together, so > > maybe you can get svn access (I'll talk to the others about all > > this.). > I think an idependend debian/ might be the better solution, as it is not recommended in upstream source[1], but it is a good thing working together on packaging. I already have clean vhcs packages (sarge only) and already work on ispcp (sid), so you don't have to reinvent the wheel and start from scratch. I can inject my files into SVN if I got access to it, but at the actual state I prefer to send you my debian/ as tar.gz. > I think in about 2-4 Weeks the 1st packages can be tested. > > Only the update-path from vhcs to ispcp might be a not so trivial > problem, because the database names and many paths > have changed. > > > I'm not sure about this, but I think DD's won't like upgrade stuff > > from a package that never existed in the Debian rep to a new coming > > one. You would have to provide that feature on your own packages. > > But I think you'll want to wait until our vhcs to ispCP script is > ready. Ok, vhcs never existed in official debian repositories, but i got many users who installed vhcs off my old apt.scunc.it and they should also be able to use apt / dpkg for easy upgrading their installations. I think a clean upgrade between vhcs and ispcp is a must. Bye Hendrik [1] http://people.debian.org/~daniel/documents/packaging.html#debian-directory - -- I am chaos. I am the substance from which your artists and scientists build rhythms and rhimes. I am the spirit with which your children and clowns laugh in happy anarchy. I am chaos. I am alive, and I tell you that you are free. - Eris, Goddess Of Chaos, Discord & Confusion. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGdvr7jWcQfAgCZA8RCN9oAKDNu4VioyA9CECSfjKIZF8ZMsoStACg2r/v YiUYnJO3h5cWiVzXNo1IsLI= =v4Xz -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#283005: ispCP debian package
Hello,
On 18/06/07, Hendrik Frenzel <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
i'm currently working at the ispcp packages, so there is no need to restart the
packaging.
The packages builds lintian clean at the moment and installs the files a bit
FHS conform.
Now i'm starting convert the config and {pre,post}{ins,rm} of my VHCS Packages
to ispcp.
Well, the plans are to provide the debian/ scripts from upstream; and
of course making any required change to ispCP so there's no need of
applying any patch for the Debian package.
And as you may see in http://www.isp-control.net/ispcp/ticket/394
there are still some thing to do.
If you wish to help the packaging I guess we can work together, so
maybe you can get svn access (I'll talk to the others about all
this.).
I think in about 2-4 Weeks the 1st packages can be tested.
Only the update-path from vhcs to ispcp might be a not so trivial problem,
because the database names and many paths
have changed.
I'm not sure about this, but I think DD's won't like upgrade stuff
from a package that never existed in the Debian rep to a new coming
one. You would have to provide that feature on your own packages.
But I think you'll want to wait until our vhcs to ispCP script is ready.
Bye
Hendrik
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGdtwzjWcQfAgCZA8RCPxKAKCUz2sDvZVEe65Omp/M6JWdaTbPRgCcDArV
dOGH4YG2EM7rcw9vMpZ3hbk=
=njqH
-END PGP SIGNATURE-
Sincerely,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#283005: ispCP debian package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
i'm currently working at the ispcp packages, so there is no need to restart the
packaging.
The packages builds lintian clean at the moment and installs the files a bit
FHS conform.
Now i'm starting convert the config and {pre,post}{ins,rm} of my VHCS Packages
to ispcp.
I think in about 2-4 Weeks the 1st packages can be tested.
Only the update-path from vhcs to ispcp might be a not so trivial problem,
because the database names and many paths
have changed.
Bye
Hendrik
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGdtwzjWcQfAgCZA8RCPxKAKCUz2sDvZVEe65Omp/M6JWdaTbPRgCcDArV
dOGH4YG2EM7rcw9vMpZ3hbk=
=njqH
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#283005: ispCP debian package
Hello, I would like to notify that upstream (including me) has plans to create it's Debian package. I've already identified some changes that need to be made so it can be packaged without patching anything. Please see: http://www.isp-control.net/ispcp/ticket/394 -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
