Don't edit packaging
See original GitHub issueThis is bad practice, it’s creating non reproducible builds, and general badness.
This error shouldn’t be possible:
dpkg-source: error: source package has two conflicting values - maya-calendar and io.elementary.calendar
Houston stuck the string io.elementary.calendar
in there somewhere at some point.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
50 Creative Packaging Design Ideas - Canva
Inside, we look at 50 unique packaging design ideas along with tips on how to make your product stand out.
Read more >The ultimate guide to product packaging design - 99Designs
You don't have to make any decisions right now, but you'll want to start noticing the different options. Budget. Packaging design budgets break...
Read more >How to use Canva and Packhelp to design custom packaging
Using Canva and the Packhelp Editor you can create personalised mailer boxes and a ... If you don't, head over to DesignEvo and...
Read more >The Ultimate Guide to Product Packaging - Shopify
Learn how to design beautiful packaging for your products that builds customer loyalty and drives retention in your online store.
Read more >Canva Tutorial: How to Make an Illustrated Packaging Design
Canva Tutorial: How to Make an Illustrated Packaging Design---Website: ... How Good is the Canva Video Editor | Editing a Facebook Video Ad....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@btkostner
Source:
is a unique line indebian/control
and it’s ALWAYS the 1st line, it should be easy and reliable to read.The reason not to rename all the packages affected by this right now is because it’s not part of the beta period fixes and I don’t want to create new problems because CI is telling me it’s a good time. I plan on gradually transitioning the package names and it’s gonna take a little time and testing to make sure it goes well. I’m still traumatized by renaming all the binaries before the beta started…
This doesn’t seem relevant anymore since we’re moving to flatpak