Bigtop
  1. Bigtop
  2. BIGTOP-969

a few files belong to more than one package

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.6.0
    • Fix Version/s: 0.6.0
    • Component/s: rpm
    • Labels:
      None

      Description

      Here's the list:

      /usr/bin/sqoop
      /usr/lib/sqoop  
      /usr/lib/sqoop/bin
      /usr/lib/hadoop/bin/fuse_dfs 
      /etc/default/hadoop-fuse
      

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Patch Available Patch Available
        2d 15m 1 Roman Shaposhnik 07/May/13 04:27
        Patch Available Patch Available Resolved Resolved
        12h 54m 1 Roman Shaposhnik 07/May/13 17:21
        Resolved Resolved Closed Closed
        45d 7h 28m 1 Roman Shaposhnik 22/Jun/13 00:49
        Roman Shaposhnik made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Roman Shaposhnik made changes -
        Status Patch Available [ 10002 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Peter Linnell added a comment -

        +1 LGTM

        Show
        Peter Linnell added a comment - +1 LGTM
        Hide
        Konstantin Boudnik added a comment -

        +1 - looks good

        Show
        Konstantin Boudnik added a comment - +1 - looks good
        Roman Shaposhnik made changes -
        Status Open [ 1 ] Patch Available [ 10002 ]
        Roman Shaposhnik made changes -
        Field Original Value New Value
        Attachment 0001-BIGTOP-969.-a-few-files-belong-to-more-than-one-pack.patch [ 12582031 ]
        Hide
        Roman Shaposhnik added a comment -

        Ok, so sqoop ended up being test being staled – false alarm there, but hadoop-hdfs-fuse is the real deal.

        Patch attached.

        Show
        Roman Shaposhnik added a comment - Ok, so sqoop ended up being test being staled – false alarm there, but hadoop-hdfs-fuse is the real deal. Patch attached.
        Hide
        Roman Shaposhnik added a comment -

        Well, it does show up in our Package tests and I'd rather fix the underlying issue than kludge the test logic (even though I agree it is NOT a catastrophic problem).

        I think I've got a fix for fuse stuff, as for sqoop – lets look into it some more.

        Show
        Roman Shaposhnik added a comment - Well, it does show up in our Package tests and I'd rather fix the underlying issue than kludge the test logic (even though I agree it is NOT a catastrophic problem). I think I've got a fix for fuse stuff, as for sqoop – lets look into it some more.
        Hide
        Sean Mackrory added a comment -

        I have been looking at this with regards to Sqoop (specifically, the contents of /usr/lib/sqoop and its subdirectories). I'm not sure I have a good solution for this that still allows us to keep the -client package as minimal as possible, but if you have any ideas I'd be happy to spend the time to patch this. I'm surprised about /usr/bin/sqoop, though - I only see it in the sqoop-client package. Where else is it showing up?

        Other than just being bad style and the potential for confusion and related bugs, are there any consequences of this? I know that the /usr/lib/sqoop issue causes that directory to remain (empty) after removing the packages, but I see that as a minor annoyance that would be nice to fix if / when we come up with a good way to split those packages better. Just wandering if this is connected to any more serious issues as well.

        Show
        Sean Mackrory added a comment - I have been looking at this with regards to Sqoop (specifically, the contents of /usr/lib/sqoop and its subdirectories). I'm not sure I have a good solution for this that still allows us to keep the -client package as minimal as possible, but if you have any ideas I'd be happy to spend the time to patch this. I'm surprised about /usr/bin/sqoop, though - I only see it in the sqoop-client package. Where else is it showing up? Other than just being bad style and the potential for confusion and related bugs, are there any consequences of this? I know that the /usr/lib/sqoop issue causes that directory to remain (empty) after removing the packages, but I see that as a minor annoyance that would be nice to fix if / when we come up with a good way to split those packages better. Just wandering if this is connected to any more serious issues as well.
        Roman Shaposhnik created issue -

          People

          • Assignee:
            Roman Shaposhnik
            Reporter:
            Roman Shaposhnik
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development