Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Vorbis tools
Vorbis tools
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 62
    • Issues 62
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Xiph.Org
  • Vorbis toolsVorbis tools
  • Issues
  • #2323

Closed
Open
Created Jul 20, 2018 by Kai Burghardt@kb😙

vorbistagedit(1) doesn't properly handle hardlinks

I've been using vorbistagedit(1) to tag my music, since it does exactly what I tell it to do. It doesn't presume to be “smarter” than the user, e.g. doesn't modify any KEY=value pair like most other “regular user” applications do. Last but not least, I can use it on the console. (yeah!)

Recently I've noticed, that some hardlinks broke. My media directory structure looks like this:

  • media/
  • media/xartist/
  • media/xartist/badLoop/
  • media/xartist/badLoop/lumme.ogg
  • media/xlabel/
  • media/xlabel/kahvi/
  • media/xlabel/kahvi/029/
  • media/xlabel/kahvi/029/00-badLoop-lumme.ogg

Where – you've guessed it – both *.ogg files are hardlinked.

After editing either *.ogg file utilizing vorbistagedit(1), I realized that at the command-line specified file path a new file with the same name is created, thus decreasing the refcount of the file as it was initially loaded.

Obviously I don't want that.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None