Skip to content
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.

Bad name of application on deb package #46

Closed
1 task done
rsantellan opened this issue Oct 11, 2023 · 3 comments
Closed
1 task done

Bad name of application on deb package #46

rsantellan opened this issue Oct 11, 2023 · 3 comments
Labels

Comments

@rsantellan
Copy link

Expected Behavior

I should be able to install insomnia and insomnium side by side, just to check if everything is imported correctly.

Actual Behavior

image

Only can install one.

Reproduction Steps

  1. Download deb package
  2. Try to installed.

Is there an existing issue for this?

Additional Information

No response

Insomnium Version

0.2.1-b

What operating system are you using?

Ubuntu

Operating System Version

20.04.1-Ubuntu

Installation method

deb

Last Known Working Insomnium version

No response

@archywillhe
Copy link
Member

archywillhe commented Oct 12, 2023

oh no; aww thanks for spotting this; looks like deb uses a diff place for identifier than other os; the fix will be out in the next release

@hasan-4
Copy link

hasan-4 commented Oct 25, 2023

Sorry to say it's not solved yet.
I tried to install Insomnium 0.2.2

(Reading database ... xxxxx files and directories currently installed.)
Preparing to unpack Insomnium.Core-0.2.2.deb ...
Unpacking insomnium (0.2.2) ...
dpkg: error processing archive Insomnium.Core-0.2.2.deb (--install):
trying to overwrite '/usr/share/applications/insomnia.desktop', which is also in package insomnia 2023.5.8
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Errors were encountered while processing:
Insomnium.Core-0.2.2.deb

lazystone pushed a commit to lazystone/insomnium that referenced this issue Oct 26, 2023
archywillhe added a commit that referenced this issue Oct 26, 2023
@archywillhe
Copy link
Member

ooh i see..

I think lazystone just found a fix and did a PR
so this should be resolved in the next build

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants