Official Debian packages for amora?
Axel Beckert
although there is a package for Debian Etch i386, there are neither
packages for other architectures like e.g. amd64 nor other (upcoming)
releases. And unfortunately there are also no appropriate Debian
source packages available to build those package yourself. (And in the
source tar.gz there is only a RPM spec file, but no debian directory.)
Additionally the available Debian package does not conform to the
Debian policy in many points (no copyright file, no changelog, no
documentation directory, no amorad man page, no source package, etc.).
So my question is: Are there plans to once offer proper Debian
packages and to officially include amora in Debian? Would really
appreciate it. :-)
Regards, Axel
--
Axel Beckert - a...@deuxchevaux.org, a...@noone.org - http://noone.org/abe/
Savago
How are you doing?
:-)
Lets answer the questions:
>
> although there is a package for Debian Etch i386, there are neither
> packages for other architectures like e.g. amd64 nor other (upcoming)
> releases.
site:
http://code.google.com/p/amora/downloads/list
>And unfortunately there are also no appropriate Debian
> source packages available to build those package yourself. (And in the
> source tar.gz there is only a RPM spec file, but no debian directory.)
>
that Debian users would download the tarball and compile it and create
a package for its architecture (since amora uses autotools that would
be quite easy).
But I was not aware that the tarball was not including the 'debian'
directory.
:-/
As a matter of fact, the trunk has the debian packaging directory. You
can check it out in the trunk:
svn checkout http://amora.googlecode.com/svn/trunk/ amora-read-only
> Additionally the available Debian package does not conform to the
> Debian policy in many points (no copyright file, no changelog, no
> documentation directory, no amorad man page, no source package, etc.).
>
known that it was not included in the tarball, what a shame...).
I suggest you to see the debian packaging of the trunk version and if
you see any area for improvements, please feel free to contacts us
(and send patches!).
:-)
> So my question is: Are there plans to once offer proper Debian
> packages and to officially include amora in Debian? Would really
> appreciate it. :-)
>
but I'm not sure how is the procedure for that and with who I should
contact with. Do you have any clues for that? Any help would be
greatly appreciated.
Amora was officially included in both Fedora and Mandriva because
people that were package maintainers for those distributions were
willing to make that happen.
Up until now, I was not contacted by Debian packagers (but I didn't
contacted then either...).
:-P
Best regards
Adenilson
Axel Beckert
On Sun, Jun 29, 2008 at 09:29:42AM -0700, Savago wrote:
> How are you doing? :-)
Warm. Sweating. Melting. It's too hot here. :-)
> > although there is a package for Debian Etch i386, there are neither
> > packages for other architectures like e.g. amd64 nor other (upcoming)
> > releases.
>
> There is a package for amd64, see in the downloads session of amora
> site:
> http://code.google.com/p/amora/downloads/list
Yeah, but this is not for Debian Stable (Etch):
3/0/0 root@c-crosser:pts/20 18:42:53 [~] # dpkg -i amora-server_1.0-0_amd64.deb
Selecting previously deselected package amora-server.
(Reading database ... 721230 files and directories currently installed.)
Unpacking amora-server (from amora-server_1.0-0_amd64.deb) ...
dpkg: dependency problems prevent configuration of amora-server:
amora-server depends on libbluetooth2 (>= 3.12); however:
Version of libbluetooth2 on system is 3.7-1.
amora-server depends on libc6 (>= 2.6-1); however:
Version of libc6 on system is 2.3.6.ds1-13etch5.
dpkg: error processing amora-server (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
amora-server
4/1/0 root@c-crosser:pts/20 18:43:42 [~] #
Looks to me as if is for current Ubuntus or Debian Unstable according
to the required libc6 version.
> > And unfortunately there are also no appropriate Debian
> > source packages available to build those package yourself. (And in the
> > source tar.gz there is only a RPM spec file, but no debian directory.)
>
> Yeah, you are right there is not a source package, because I think
> that Debian users would download the tarball and compile it and create
> a package for its architecture (since amora uses autotools that would
> be quite easy).
That would be fine if the debian directory is in there. :-)
> But I was not aware that the tarball was not including the 'debian'
> directory. :-/
Ah, ok.
> As a matter of fact, the trunk has the debian packaging directory. You
> can check it out in the trunk:
> svn checkout http://amora.googlecode.com/svn/trunk/ amora-read-only
Ah, cool. I tried to view into the repository online, but only got
server errors for a while.
> > Additionally the available Debian package does not conform to the
> > Debian policy in many points (no copyright file, no changelog, no
> > documentation directory, no amorad man page, no source package, etc.).
>
> The man page is available in the repository version (again, I didn'
> known that it was not included in the tarball, what a shame...).
'kay. Thanks for the hint, will have a look at it.
> I suggest you to see the debian packaging of the trunk version and if
> you see any area for improvements, please feel free to contacts us
> (and send patches!). :-)
I will.
> > So my question is: Are there plans to once offer proper Debian
> > packages and to officially include amora in Debian? Would really
> > appreciate it. :-)
>
> I would love to see Amora officially included in Debian repositories,
> but I'm not sure how is the procedure for that
Find someone who would package and maintain it according to Debian
standards. This can be a Debian Developer or someone who plans to
become one and does uploads of his packages via a so called sponsors.
> and with who I should contact with.
If you don't know anyone you can file a "Request for Package" bug
against the virtual package "wnpp" (work needing and prospective
packages).
> Amora was officially included in both Fedora and Mandriva because
> people that were package maintainers for those distributions were
> willing to make that happen.
>
> Up until now, I was not contacted by Debian packagers (but I didn't
> contacted then either...).
Well, you can see my mail as such contacting. :-)
I'm quite assimilated by^W^Winvolved in the Debian scene since years
and currently maintain about half a dozen packages in Debian. I'm
though not yet a Debian Developer (DD), but plan to become DD once in
the future.
And I would also package and maintain amora-server for Debian as long
as the maintainers of the package don't object. :-)
Savago
>
> Warm. Sweating. Melting. It's too hot here. :-)
>
summer there was one day with 42Celsius degrees (in the shadows casted
by a palm tree!).
:-D
>
> Yeah, but this is not for Debian Stable (Etch):
>
>
> Looks to me as if is for current Ubuntus or Debian Unstable according
> to the required libc6 version.
>
stable? I remember that there was an issue with amora D-Bus module
compiling fine in Debian unstable.
Amora 1.0 didn't uses D-Bus to detect dongle disconnection, it should
compile fine.
>
> > I suggest you to see the debian packaging of the trunk version and if
> > you see any area for improvements, please feel free to contacts us
> > (and send patches!). :-)
>
> I will.
>
> Well, you can see my mail as such contacting. :-)
>
> I'm quite assimilated by^W^Winvolved in the Debian scene since years
> and currently maintain about half a dozen packages in Debian. I'm
> though not yet a Debian Developer (DD), but plan to become DD once in
> the future.
>
> And I would also package and maintain amora-server for Debian as long
> as the maintainers of the package don't object. :-)
>
(I'm already forwarding this message to him) but I think he would not
make any objections to your offer to maintain a amora package.
As a matter of fact, I'm working to make a release of Amora 1.1 in the
next weeks (already tagged the amora-server code and I'm solving some
issues of the cellphone client). Its advisable, to prevent re-working,
that you base you changes on the trunk version of amora.
We can discuss this ideas further on the devels group:
http://groups.google.com/group/amora-devel
Also, feel free to contact me in both gtalk (cavalcantii-at-gmail.com)
or freenode (my nickname is Savago).
Best regards
Adenilson
Axel Beckert
On Sun, Jun 29, 2008 at 12:47:48PM -0700, Savago wrote:
> > Warm. Sweating. Melting. It's too hot here. :-)
>
> It can't be possible warmer than Manaus - Amazonas - Brazil. Last
> summer there was one day with 42Celsius degrees (in the shadows casted
> by a palm tree!). :-D
Not really, it's about 29 or 30 degree Celsius here in Switzerland.
But that's enough for my taste. ;-)
> > Looks to me as if is for current Ubuntus or Debian Unstable according
> > to the required libc6 version.
> >
>
> Yep. By the way, does the *trunk* source compiles fine in Debian
> stable?
Haven't tried it yet. Just compiled the 1.0 release a few weeks ago
from the tar.gz.
> I remember that there was an issue with amora D-Bus module
> compiling fine in Debian unstable.
I'll check it.
> Amora 1.0 didn't uses D-Bus to detect dongle disconnection, it should
> compile fine.
Yeah, it does (at least on Debian stable).
> > And I would also package and maintain amora-server for Debian as long
> > as the maintainers of the package don't object. :-)
>
> That would be great! Tomaz Noleto kindly wrote the debian packaging
Yeah, read that in the commit logs in the meanwhile. :-)
> (I'm already forwarding this message to him) but I think he would not
> make any objections to your offer to maintain a amora package.
I'm also open to collaborative package maintaining. My goal is to get
it into Debian and have it in the next release.
> As a matter of fact, I'm working to make a release of Amora 1.1 in
> the next weeks
Ah, such thing is good to know.
> (already tagged the amora-server code and I'm solving some
> issues of the cellphone client).
Ok, so I'll try to make (and test) a preliminary package out of trunk
the next few days.
> Its advisable, to prevent re-working, that you base you changes on
> the trunk version of amora.
Of course.
> We can discuss this ideas further on the devels group:
> http://groups.google.com/group/amora-devel
I just sent a subscription request and will confirm that after this
mail.
> Also, feel free to contact me in both gtalk (cavalcantii-at-gmail.com)
> or freenode (my nickname is Savago).
Added you to my Jabber roster (a...@noone.org) and to my notify
list on IRC. I'm as XTaran in Freenode.
Axel Beckert
On Sun, Jun 29, 2008 at 11:02:43PM +0200, Axel Beckert wrote:
> > Yep. By the way, does the *trunk* source compiles fine in Debian
> > stable?
Just tried to build a Debian package with the source and packaging
data from trunk (svn revision 520). It built without problems and
works fine. (Threw a few "Invalid event!" messages with my 1.0 client
though.)
> > I remember that there was an issue with amora D-Bus module
> > compiling fine in Debian unstable.
>
> I'll check it.
Built it on Debian Testing (which is about two weeks behind Unstable
for packages without release critical bugs). Did not build immediately
since there seem to be build dependencies on at least autoconf,
automake and pkg-config missing. They probably miss for Stable, too, I
just had them installed on my Debian Stable machine already. Nothing
critical though.
Starts up, too, but can't test it currently, because I'm currently
missing the USB bluetooth adapter for my Debian Testing machine.
(Those things are so tiny nowadays, you loose them so easily... ;-)
> > (I'm already forwarding this message to him) but I think he would
> > not make any objections to your offer to maintain a amora package.
>
> I'm also open to collaborative package maintaining. My goal is to
> get it into Debian and have it in the next release.
I allowed myself to file an "Intent to package" bug:
http://bugs.debian.org/488587
Savago
> Just tried to build a Debian package with the source and packaging
> data from trunk (svn revision 520). It built without problems and
> works fine. (Threw a few "Invalid event!" messages with my 1.0 client
> though.)
>
Those 'invalid events' are spewed to console when there is any missed
string command between the client and server (and its normal if only
happens from time to time).
> Built it on Debian Testing (which is about two weeks behind Unstable
> for packages without release critical bugs). Did not build immediately
> since there seem to be build dependencies on at least autoconf,
> automake and pkg-config missing. They probably miss for Stable, too, I
> just had them installed on my Debian Stable machine already. Nothing
> critical though.
Great, lets keeping it rolling (and some day Debian users will be able
to do: $apt-get install amora)
:-D
Best regards
Adenilson
Tomaz Noleto
Don't bother about me :) I haven't done more than user Debian tools
for that. So, there are no reasons to make objections about it.
And it would be really great to have Amora as an official Debian package.
BR
- Tomaz
> As a matter of fact, I'm working to make a release of Amora 1.1 in the
> next weeks (already tagged the amora-server code and I'm solving some
> issues of the cellphone client). Its advisable, to prevent re-working,
> that you base you changes on the trunk version of amora.
>
> We can discuss this ideas further on the devels group:
> http://groups.google.com/group/amora-devel
>
> Also, feel free to contact me in both gtalk (cavalcantii-at-gmail.com)
> or freenode (my nickname is Savago).
>
> Best regards
>
>
> Adenilson
>
--
Tomaz Noleto
tno...@gmail.com
--
Tomaz Noleto
tno...@gmail.com