Oh, thanks for the obvious answer, Christopher. See ACCUMULO-1560<https://issues.apache.org/jira/browse/ACCUMULO-1560> .
On Mon, Jul 8, 2013 at 8:21 AM, Christopher <[email protected]> wrote: > It doesn't. Debs are packaged with a separate configuration. > > -- > Christopher L Tubbs II > http://gravatar.com/ctubbsii > > > On Sun, Jul 7, 2013 at 9:03 PM, Mike Drob <[email protected]> wrote: > > I've made this change independently, and I recall it working. I don't > know > > how this affects debian and other apt-based systems, however. > > > > > > On Sun, Jul 7, 2013 at 8:53 PM, Christopher <[email protected]> wrote: > > > >> As a workaround, it would only take a slight modification to the POM > >> to re-generate the RPM with the correct arch (change > >> '<needarch>true</needarch>' to '<needarch>x86_64</needarch>' in the > >> parent pom.xml). > >> > >> This change could be made for 1.4.4, I suppose, if it's not too late > >> to sneak in that fix (Mike Drob had mentioned trying to tag 1.4.4 > >> soon). If you can confirm this change fixes things for you, and you > >> create a ticket with a fixVersion of 1.4.4, we can make the change. > >> > >> -- > >> Christopher L Tubbs II > >> http://gravatar.com/ctubbsii > >> > >> > >> On Sun, Jul 7, 2013 at 8:10 PM, Andres Danter <[email protected]> > wrote: > >> > Hi Christopher, > >> > > >> > That's an excellent observation, and something that is easy to verify > and > >> > fix. > >> > > >> > Is there anyone opposed to changing the Arch of the 1.4.3 RPM from > amd64 > >> to > >> > x86_64, if that is the problem here? > >> > > >> > Thanks, > >> > > >> > Andres > >> > On Jul 7, 2013 6:11 PM, "Christopher" <[email protected]> wrote: > >> > > >> >> The ARCH for the 1.4.3 RPM is amd64 instead of x86_64. I'm guessing > >> >> that's why you're seeing this problem. RPM will still install the > >> >> 1.4.3 RPM, but YUM doesn't like it. > >> >> > >> >> -- > >> >> Christopher L Tubbs II > >> >> http://gravatar.com/ctubbsii > >> >> > >> >> > >> >> On Sat, Jul 6, 2013 at 9:21 PM, Andres Danter <[email protected]> > >> wrote: > >> >> > Hi all, > >> >> > > >> >> > I ran into an odd problem and was wondering if anyone could verify > a > >> >> > possible issue. > >> >> > > >> >> > I tried setting up a local yum repository that contains only the > RPM > >> for > >> >> > Accumulo 1.4.3. I created a file in /etc/yum.repos.d called > >> local.repo. > >> >> > It contains the following: > >> >> > > >> >> > [localrepo] > >> >> > name=localrepo > >> >> > baseurl=file:///var/www/html/localrepo > >> >> > enabled=1 > >> >> > gpgcheck=0 > >> >> > > >> >> > I placed the RPM in /var/www/html/localrepo/accumulo/ > >> >> > > >> >> > Then I ran the following command: > >> >> > > >> >> > createrepo /var/www/html/localrepo > >> >> > > >> >> > Then I ran the following: > >> >> > > >> >> > repoquery -q --repoid=localrepo -a > >> >> > > >> >> > Which returned nothing. It should have listed the Accumulo RPM. > >> >> > > >> >> > I then replaced the 1.4.3 RPM with the 1.5.0 RPM and ran the > following > >> >> > command: > >> >> > > >> >> > createrepo --update /var/www/html/localrepo > >> >> > > >> >> > Then I ran: > >> >> > > >> >> > yum clean all > >> >> > > >> >> > Then I re-ran: > >> >> > > >> >> > repoquery -q --repoid=localrepo -a > >> >> > > >> >> > This time the command returned: > >> >> > > >> >> > accumulo-0:1.5.0-1.noarch > >> >> > > >> >> > I was even able to install the Accumulo 1.5.0 RPM using Yum. I was > >> >> unable > >> >> > to do that with the 1.4.3 RPM. > >> >> > > >> >> > So has anyone ever successfully set up a repository with the 1.4.3 > >> RPM? > >> >> > Does anyone have any clue as to why one RPM is seen by Yum and the > >> other > >> >> is > >> >> > not? I figured it has to do with the metadata that is created when > >> the > >> >> RPM > >> >> > is built, but I don't have any insight beyond that. > >> >> > > >> >> > Thanks, > >> >> > > >> >> > Andres > >> >> > >> >
