[Sisuite-devel] systemimager builds only under debian?

Discussion:

Erich Focht

2011-01-27 15:02:45 UTC

Hi guys,

after a long break we're looking at the latest systemimager trunk (r4506)
and I'm wondering:

install -m 755 /home/depple/Devel/systemimager.trunk/initrd_source/src/rsync-3.0.0/rsync
/home/depple/Devel/systemimager.trunk/initrd_source/build_dir/bin
cd /home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf && chmod +x ./debian/rules
cd /home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf && ./debian/rules clean
make[1]: dpkg-architecture: Command not found
make[1]: Entering directory `/home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf'
make[1]: dpkg-architecture: Command not found
dh_testdir
make[1]: dh_testdir: Command not found
make[1]: *** [clean] Error 127
make[1]: Leaving directory `/home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf'
make: *** [/home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf.build] Error 2

Is systemimager supposed to build only under debian? If yes, since when?
And ... is this on purpose?

Cheers,
Erich

Brian Elliott Finley

2011-01-27 15:22:18 UTC

Permalink

Erich,

Trunk is in flux right now. Debian (Ubuntu) is just what I happen to be doing the initial development in. When it stabilizes, it should be buildable on all the major distros.

Please use a branch for now, such as 4.1.6.

Lemme know if you have other questions.

Cheers,

Brian
--
Brian Elliott Finley
Mobile: +1.630.447.9108

-----Original Message-----
From: Erich Focht <***@gmail.com>
Date: Thu, 27 Jan 2011 16:02:45
To: sisuite-dev<sisuite-***@lists.sourceforge.net>
Subject: [Sisuite-devel] systemimager builds only under debian?

Hi guys,

after a long break we're looking at the latest systemimager trunk (r4506)
and I'm wondering:

install -m 755 /home/depple/Devel/systemimager.trunk/initrd_source/src/rsync-3.0.0/rsync
/home/depple/Devel/systemimager.trunk/initrd_source/build_dir/bin
cd /home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf && chmod +x ./debian/rules
cd /home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf && ./debian/rules clean
make[1]: dpkg-architecture: Command not found
make[1]: Entering directory `/home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf'
make[1]: dpkg-architecture: Command not found
dh_testdir
make[1]: dh_testdir: Command not found
make[1]: *** [clean] Error 127
make[1]: Leaving directory `/home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf'
make: *** [/home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf.build] Error 2

Is systemimager supposed to build only under debian? If yes, since when?
And ... is this on purpose?

Cheers,
Erich

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
sisuite-devel mailing list
sisuite-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuit

Erich Focht

2011-01-27 18:36:30 UTC

Permalink

Hi Brian,

thanks, will try and report back if something goes wrong ;-)

Regards,
Erich

Post by Brian Elliott Finley
Erich,
Trunk is in flux right now. Debian (Ubuntu) is just what I happen to be doing the initial development in. When it stabilizes, it should be buildable on all the major distros.
Please use a branch for now, such as 4.1.6.
Lemme know if you have other questions.
Cheers,
Brian
--
Brian Elliott Finley
Mobile: +1.630.447.9108
-----Original Message-----
Date: Thu, 27 Jan 2011 16:02:45
Subject: [Sisuite-devel] systemimager builds only under debian?
Hi guys,
after a long break we're looking at the latest systemimager trunk (r4506)
install -m 755 /home/depple/Devel/systemimager.trunk/initrd_source/src/rsync-3.0.0/rsync
/home/depple/Devel/systemimager.trunk/initrd_source/build_dir/bin
cd /home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf&& chmod +x ./debian/rules
cd /home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf&& ./debian/rules clean
make[1]: dpkg-architecture: Command not found
make[1]: Entering directory `/home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf'
make[1]: dpkg-architecture: Command not found
dh_testdir
make[1]: dh_testdir: Command not found
make[1]: *** [clean] Error 127
make[1]: Leaving directory `/home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf'
make: *** [/home/depple/Devel/systemimager.trunk/initrd_source/src/sysvinit-2.87dsf.build] Error 2
Is systemimager supposed to build only under debian? If yes, since when?
And ... is this on purpose?
Cheers,
Erich
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
sisuite-devel mailing list
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Bernard Li

2011-01-28 07:08:03 UTC

Permalink

Hi Erich:

Trunk @4474 should be stable, you should try that:

http://trac.systemimager.org/browser/trunk?rev=4474

What we should do is release r4474 as 4.1.7 (unstable), then rebrand
4.1.6 as 4.2.0 (stable).

I'll get to it when I get a chance, or you can do it since you seem to
be doing some development work with SystemImager :-)

I am also supposed to migrate the tree to GitHub... :P

Let me know what you think.

Cheers,

Bernard

Post by Erich Focht
Hi Brian,
thanks, will try and report back if something goes wrong ;-)
Regards,
Erich

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
sisuite-devel mailing list
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Bernard Li

2011-02-03 23:40:43 UTC

Permalink

Post by Bernard Li
What we should do is release r4474 as 4.1.7 (unstable), then rebrand
4.1.6 as 4.2.0 (stable).

After thinking about this some more, I think we should create 4.2.x
stable branch with r4474 as starting point, make sure doc/release
notes are up to date, then release that as 4.2.0. I only committed
minor fixes to trunk to fix some LVM issues so it should be stable
enough.

Then code coming out from trunk will be 4.3.x, which will be labelled
"unstable".

If we all agree, I can start working on this.

Cheers,

Bernard

Brian Elliott Finley

2011-02-04 01:56:04 UTC

Permalink

Sounds good. Do it.

Cheers,

Brian

------Original Message------
From: Bernard Li
To: Erich Focht
Cc: Brian Finley (H)
Cc: Sisuite-devel
Subject: Re: [Sisuite-devel] systemimager builds only under debian?
Sent: Feb 3, 2011 5:40 PM

Post by Bernard Li
What we should do is release r4474 as 4.1.7 (unstable), then rebrand
4.1.6 as 4.2.0 (stable).

Bernard Li

2011-02-04 20:05:37 UTC

Permalink

I tried to do it, but ran into an issue:

$ svn -r4474 cp
svn://svn.systemimager.org/var/lib/svn/systemimager/trunk
svn://svn.systemimager.org/var/lib/svn/systemimager/branches/4.2.x -m
'Create branch for 4.2.x (stable) development from trunk r4474'
svn: Cannot negotiate authentication mechanism

Anybody knows what is causing the problem?

BTW, any chance we could switch over to the https scheme and/or update
subversion version on our server?

I guess I could also just do the GitHub migration and start fresh from there.

Cheers,

Bernard

On Thu, Feb 3, 2011 at 5:56 PM, Brian Elliott Finley

Post by Brian Elliott Finley
Sounds good. Do it.
Cheers,
Brian
------Original Message------
From: Bernard Li
To: Erich Focht
Cc: Brian Finley (H)
Cc: Sisuite-devel
Subject: Re: [Sisuite-devel] systemimager builds only under debian?
Sent: Feb 3, 2011 5:40 PM

Post by Bernard Li
What we should do is release r4474 as 4.1.7 (unstable), then rebrand
4.1.6 as 4.2.0 (stable).

After thinking about this some more, I think we should create 4.2.x
stable branch with r4474 as starting point, make sure doc/release
notes are up to date, then release that as 4.2.0. I only committed
minor fixes to trunk to fix some LVM issues so it should be stable
enough.
Then code coming out from trunk will be 4.3.x, which will be labelled
"unstable".
If we all agree, I can start working on this.
Cheers,
Bernard
--
Brian Elliott Finley
Mobile: +1.630.447.9108

Brian Elliott Finley

2011-02-04 20:38:21 UTC

Permalink

s/svn/svn+ssh/

See if that does it.

As for your other questions, I think the answer is github.

Cheers,

Brian

------Original Message------
From: Bernard Li
To: Brian Finley (H)
Cc: Erich Focht
Cc: Sisuite-devel
Subject: Re: [Sisuite-devel] systemimager builds only under debian?
Sent: Feb 4, 2011 2:05 PM

I tried to do it, but ran into an issue:

$ svn -r4474 cp
svn://svn.systemimager.org/var/lib/svn/systemimager/trunk
svn://svn.systemimager.org/var/lib/svn/systemimager/branches/4.2.x -m
'Create branch for 4.2.x (stable) development from trunk r4474'
svn: Cannot negotiate authentication mechanism

Anybody knows what is causing the problem?

BTW, any chance we could switch over to the https scheme and/or update
subversion version on our server?

I guess I could also just do the GitHub migration and start fresh from there.

Cheers,

Bernard

On Thu, Feb 3, 2011 at 5:56 PM, Brian Elliott Finley

Post by Bernard Li
What we should do is release r4474 as 4.1.7 (unstable), then rebrand
4.1.6 as 4.2.0 (stable).

After thinking about this some more, I think we should create 4.2.x
stable branch with r4474 as starting point, make sure doc/release
notes are up to date, then release that as 4.2.0. I only committed
minor fixes to trunk to fix some LVM issues so it should be stable
enough.
Then code coming out from trunk will be 4.3.x, which will be labelled
"unstable".
If we all agree, I can start working on this.
Cheers,
Bernard
--
Brian Elliott Finley
Mobile: +1.630.447.9108

Bernard Li

2011-02-04 20:52:18 UTC

Permalink

Hey Brian:

On Fri, Feb 4, 2011 at 12:38 PM, Brian Elliott Finley

Post by Brian Elliott Finley
s/svn/svn+ssh/
See if that does it.

Thanks, that did it.

Goes to show how long it's been since I've checked code into
SystemImager SVN. :)

Anyways, the branch is there, I'll work on updating the release notes
and potentially committing a few patches into it.

Cheers,

Bernard

Brian Elliott Finley

2011-02-04 20:38:21 UTC

Permalink

Post by Bernard Li
What we should do is release r4474 as 4.1.7 (unstable), then rebrand
4.1.6 as 4.2.0 (stable).

After thinking about this some more, I think we should create 4.2.x
stable branch with r4474 as starting point, make sure doc/release
notes are up to date, then release that as 4.2.0. I only committed
minor fixes to trunk to fix some LVM issues so it should be stable
enough.
Then code coming out from trunk will be 4.3.x, which will be labelled
"unstable".
If we all agree, I can start working on this.
Cheers,
Bernard
--
Brian Elliott Finley
Mobile: +1.630.447.9108