I guess the best way is to open a new bug, summarize these points and
start from scratch in 2016.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008876
Title:
plugin package broken
To manage
fqj1994 (fqj1994) wrote on 2012-06-28:
> The way to enable it is not like what is mentioned in hg-git.github.com
THIS is clearly the bug. How can you possibly not see this? The Debian
package for a python module should install that module under the same
name that it is DESIGNED to have and
As a novice Mercurial user I was also surprised that the `hggit =` line
mentioned at http://hg-git.github.com/ wouldn't enable the plugin, and I
needed either `git =` or `hgext.git =` instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is a problem for me. I share my .hgrc across different systems.
This is impossible if I have to use hgext.git= for Ubuntu and hggit= for
every other platform. Is my problem a different bug or should this one
be reopened? Is it something I should raise with the upstream
maintainer?
--
You
I have to redeclare that it is NOT a bug.
1. Why don't we enable it by default ?
I said : we cannot enable plugins by default.
and upstream also said we SHOULD NOT enable plugins by default.
I'm sorry for the improper use of the word cannot as I'm not an English
native speaker. The cannot
Hello,
I think the plugin should not be enabled by default.
Enabling it by default is a system-wide, because it may make users without
permission difficult to disable it.
Users who need it should enabled it itself.
How do you think of adding a text notification telling users the way to enable
There are two points:
1. No need in one more redirect - message should provide instructions itself
2. Where this message is be shown?
If users see the package is installed, but can not receive the message -
it won't help. To propose anything it is critical to know why official
way described
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: hg-git (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008876
Title:
1. we cannot enable plugins by default
please see the NEWS of mercurial 1.1.2-1
mercurial (1.1.2-1) unstable; urgency=low
Since the 1.1.2-1 version, mercurial does not enable any extension by
default anymore. Upstream asks us to do so because:
- users can easily enable any extension if
blod - bold
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008876
Title:
plugin package broken
To manage notifications about this bug go to:
SEE an old bug:
https://bugs.launchpad.net/ubuntu/+source/hg-git/+bug/666292
** Changed in: hg-git (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008876
** Changed in: hg-git (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008876
Title:
plugin package broken
To manage notifications about this bug go to:
If you didn't noticed it is me who marked bug #666292 as a duplicate, so
I obviously have SEEN it. ;)
If you feel that it contains some essential stuff that I've missed, then
a quote that you find relevant and a link to original comment will be
more useful. Now back on track. I add quotes,
Please refer to:
/usr/share/doc/mercurial-git/README.Debian
to enable it
The way to enable it is not like what is mentioned in hg-git.github.com
Please refer to
The readme document in:
/usr/share/doc/mercurial-git/README.Debian
thanks
** Changed in: hg-git (Ubuntu)
Status: New =
** Changed in: hg-git (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008876
Title:
plugin package broken
To manage notifications about this bug go to:
Let me raise a point. Plugins are things that work automatically or with
a minimal manual intervention. Every plugin-enabled product has rules
reflected in official documentation how to work with plugins. If the
platform that distributes the product breaks this user level API - it
shoud provide
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008876
Title:
plugin package broken
To manage notifications about this bug go to:
17 matches
Mail list logo
