> Well, my point was to have a common predefined way of doing it: once you
> install kdm (or someone else), or move to xdm or whatever, you still can
> disable the start of X by putting nox in the command line, instead of having
> to erase the links in rc2.d.
Acutally there should be no link in ru
> Thats not true. Read the Debian Policy. Its just that some other
> distributions use runlevel 2 for console mode. In Debian thats all up to
> the user/administrator of the system. Of course we can change this but
> its not true currently.
Sorry, consider me spoiled by SuSE which I am forced to
> see
> http://www.linuxbase.org/modules.php?name=specrev&url=http://www.linuxbase.org/spec//booksets/LSB-Core-generic/LSB-Core-generic/set1.html
> for what the LSB has to say about the subject
So its seems SuSE was following LSB recommendations.
Just wondering if Debian should switch to LSB reco
Hello,
as a non-DD I am not so tuned into the Debian project as many of you
are. However I would like to make a proposal about the "hot topic".
As I have noticed, most people ojecting against dropping architecures
feared for the coherence of the systems. They wanted to be able to have
the *same*
I really like this suggestion and in fact I had the same idea too, but I
found your post only when I was ready with writing. You can find my
proposal at http://lists.debian.org/debian-devel/2005/03/msg01647.html.
It goes a little more into detail, but is based on basically the same
idea.
Greetings
> I really hope [...] you can find a sponsor!
I don't really think he needs one. Look at the email address..
--
Please do not sent any email to the [EMAIL PROTECTED] - all email not
originating from the mailing list will be deleted automatically. Use the
reply to address instead.
--
To UNSUBS
Only a thought that occured to me when reading this: Did you think about
how your approach will work once the proposed parallel boot script
execution is implemented?
Best regards Ben
--
Please do not sent any email to the [EMAIL PROTECTED] - all email not
originating from the mailing list will be
> Description : ESense (ErlangSense) is a minor emacs mode which provides
> features similar to IntelliSense or CodeSense in other editors.
This line seems to be too long to me. Also it refers to IntelliSense and
CodeSense where you cannot assume that they are known. Also do not start
your s
Another thought:
> * Package name: esense
A lot of emacs modes are named -mode (haskell-mode,
asn1-mode,...) . In this fashion you might also consider naming it
erlang-mode.
> ESense will help developers write Erlang programs more quickly by
> helping them refer to the function exported by a
Hello,
today I've tried to address the issue raised by Steve Langasek regarding
"inherited" dependencies [1].
As I am unexperienced with the whole linking and dependency process I
was not able to deduce the consequences of this announcement for my
packaging.
As far as I have understood the email
Hello,
thanks for you comments.
> A bug report is probably in order.
Done.
Best regards
Ben
--
Please do not send any email to the [EMAIL PROTECTED] - all email not
originating from the mailing list will be deleted automatically. Use the
reply to address instead.
--
To UNSUBSCRIBE, email
> "Please (re)check, if the package can be built by g++ > 3.4
> on [hppa/arm/m68k]"?
>
> Do I simply remove the explicit build dependency on g++,
> upload the package and wait if it succeeds (and probably
> create another package version with the build dependencies
> re-added again if it still fa
Hello
> Secondly, you do not seem to understand how Debian works. "Unstable" is
> called "Unstable" for a reason. It is the first stage of public testing.
> Renaming it to "Latest" would not only falsely describe what it is, but
> would simply be not true. If you want the latest, you download a
Hello
> How on Earth would that be allowed into testing? I can imagine Serious
> bugs slipping trough (because most are reported as Normal, after all),
> but broken dependencies?
I admit I was imprecise, often it are conflicts (usually through library
stuff) that prevent packages from being inst
Hello,
> > > However due to the QT library transition my package
> > > which I fixed in unstable at once has not entered testing yet...
>
> packagesearch | 2.0.4 | testing | source, alpha, ...
> packagesearch | 2.0.4 | unstable | source, alpha, ...
You are right, the QT libra
Hello,
> > So please disregard my statement against "testing"
>
[..]
> (In this case, xterm could have had a conflict with your package to
> avoid screwing users over unnoticed; and we could (in future) have added
> a note to the testing scripts to not allow upgrades of xterm until a
> fixed vers
Note that there was a discussion using debtags for license information
on debtags-devel/debian-legal.
http://lists.debian.org/debian-legal/2005/06/msg00016.html
is a good starting point.
Personally I believe, that if such an information should be available,
debtags is more suitable to express thi
Hello,
I would say line 15 says it pretty clearly:
If you didn't upload those files, please just ignore this
message.
>From that message I would deduce that things like this might happen from
time to time...
Best regards
Ben
--
Please do not send any email to [EMAIL PROTECTED]
Hello,
> The Vancouver proposals satisfy all of these, potentially at the cost of
> removing some architectures from the set released by Debian. If we want
> to avoid that cost, can we come up with another proposal that solves the
> same problems in a way that satisfies the release team?
There w
Hello,
I have a package which I develop on my own and which is debian native.
However due to historical reasons, I have a CHANGELOG file which is not
the debian/changelog file.
How should I handle this case? I am in favour of handling it like an
upstream package, meaning
1. debian/changelog
Hello
> * Package name: soundconverter
> Version : 0.7.1
> Upstream Author : Gautier Portet
> * URL : http://soundconverter.berlios.de/
> * License : GPL v2
> Description : convert sound files to other formats
What about "converts between different sound
> Manual edit of /etc/apt/sources.list and apt-get update ; apt-get
> dist-upgrade. [NOTE: I'm fairly sure the archive layout changed for
> non-US/main between Woody -> Sarge and I had problems here. Could be a
> show stopper as not immediately obvious what to change]
As far as I've read the list r
> You would rather have silence than know why you are being ignored?
> Then silence you shall have.
Well, its the tone that makes the music we use to say here in Germany.
Certainly there would have been ways to tell Bluefuture that his mail
was hard to read/understand without becoming offensive.
Hello
> > > the right thing to do would be to switch from sections, to keywords, so
> > > that kmplayer could live in sound + video + kde, instead of multimedia
> > > that is not very informative.
> >
> > Now this, I'd second :)
> >
> > (OTOH, I'm not volunteering to implement support for this, I
Hello,
> Is it already used in any package management tools? Or is the debedit
> GUI currently the only program using the preliminary database?
As far as I know it is hidden deep into synaptic, but I don't know if
the support is currently broken or not. Also there is a cool search
application cal
On Tue, 2005-06-07 at 19:30 +0300, Meelis Roos wrote:
> JFSP> - Separate runlevels: 2 for multi, no net, 3 for multi no X, 4 for X,
> 4=5
>
> Why? Display manager as a normal service that can be started and stopped
> like other services is very natural. No need to confuse the users with
> more ru
> If your X configuration is broken and your X won't start then that is
> effectively the same thing as the proposed run level 3 anyway. So
> what is the point?
Well, I used to have problems with my graphiccard that hard locked the
system on startup. Being able to do boot into runlevel (RL) 3 wit
> I use both of these and would like to adopt them. I will upload next
> week (via Anibal).
I think they are no longer maintained upstream.
Take a look at http://www.icewm.org/FAQ/IceWM-FAQ-11.html#tools4icewm
for more modern and supported alternatives.
Greetings Ben
--
Please do not sent any
[It's been a while since this message hit the debtags-devel list, thus I
include an almost full quote as well as CCing the participants of the
discussion, please follow up on debtags-devel@ or CC it in responses]
[Response below]
On Mon, 2006-07-31 at 17:14 +, Thaddeus H. Black wrote:
> The f
Package: wnpp
Severity: wishlist
Owner: Benjamin Mesing <[EMAIL PROTECTED]>
* Package name: umlet
Version : 7.0
Upstream Author : <[EMAIL PROTECTED]>
* URL : http://www.umlet.com
* License : GPL
Programming Lang: Java
Description : simple,
Hello,
I want to close #355625 which says that packagesearch crashes on startup
if debtags is not installed.
I have implemented a solution that should fix this, but since Justin
said it is somewhat unreproducable once debtags was installed (pbuilder,
and tested with dancer's xnest recipe) and I
Hello
> Usually people want the source package here. I see it is available on
> your web page, but as the directory is not browsable, it's a bit
> annoying to find.
Sorry about that.
The source package is available at:
http://www.mesing.de/packagesearch/packagesearch_2.1.tar.gz
And .dsc and .ch
Hello,
my comments as someone planning to enter NM during the next couple of
month follow.
Overall I find your analysis enlightening. I agree with those points I
do not discuss here.
> 1.2.1 Add more people
[Marc argues that this is not a long solution]
I disagree here up to a certain point. I
Sorry, the message was intended for d-p, please do not follow up here.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: wnpp
Severity: wishlist
Owner: Benjamin Mesing <[EMAIL PROTECTED]>
* Package name: vos
Version : 0.23.0
Upstream Author : Peter Amstutz <[EMAIL PROTECTED]>
* URL : http://interreality.org/
* License : mostly LGPL, some GPL
Program
Hello,
my congratulation to the team too. However I was not as fortunate as the
Sean.
What about the xlibmesa-glu packages? Can we expect them to enter the
archive again? Else I have to remove some of my shiny GL applications
(crystalspace, freewrl, libdevil,...)
Greetings Ben
--
Please do no
Hello,
> > You claim that if someone spends just as much time translating Debian as
> > someone else does on packaging software, the first one shouldn't become a
> > DD and the second one does? I disagree firmly.
>
> Packaging is the essential work and everyone involved into Debian must
> be able
Hello,
> > To get some indication on the order the bugs should be solved in? As
> > we have limited time and people, it is smart to start with the bugs
> > affecting most people.
> >
>
> I can only see usefulness for QA team (orphaned) packages. A properly
> maintained package should have a
Hello,
> Several people probably faced the problem that after initial system bootup,
> and startup of *dm, keyboard does not work.
> Suggested workaround was to add implicit 'vtX' parameter to X server
> command line in Xservers file.
I don't use a diplay manager, but I face the same problem wh
Hello,
I agree with you, that the documentation review team should have the
debtags approach in mind. Also debtags-edit being able to edit
descriptions would be desirable - however someone would need to
implement this, and Enrico is very busy ;-). Being able to edit the
package information in one
Hello,
> If the debtags also get searched when she does a simple search, then
> great. This will depend on how seamlessly debtags get integrated into
> package managers (like Synaptic's) search facilities (for example, a
> simple search by default, then an "Advanced" button to expand the searc
> HAYAYYY!!!
>
> $ svn st|grep ^C
> C debian/control
> C README
> C configure.ac
>
> Small things easy to resolve. Wow! It's done!
This should have gone to debtags-devel I suppose :-)
--
Please do not sent any email to the [EMAIL PROTECTED] - all email not
originating from the
Hello
> Confirmed: libqt is still gcc3.
>
> Given that libqt is gcc3 and libapt and libdebtags1 are gcc4, this means
> that you are stuck until libqt migrates to gcc4. :(
Thanks for taking a look. Now I know at least some of your hassles...
> It looks like a good time to do some work on the in-
Hello,
[Uh, my first message was not supposed to go to debian-devel, but was
intended as a rant on debtags-devel ;-) But now that it has reached
debian-devel I can as well provide some useful information]
I had the problem for some time now - I hope it will vanish with the
time...
OK, here is the
> http://wiki.debian.net/?spamInWikiPages
> http://wiki.debian.net/?DealingWithSpam
After having read this - wouldn't it be easier to report the user doing
the spamming, and simply reverting all changes done by this user
(probably the users spamming will not have add valuable content)?
Who is in
> What documentation is available on the subject of creating debian
> packages ? What documents should I read before starting ?
http://www.google.com/search?hs=V9&hl=en&lr=&client=opera&rls=en&q=debian+packaging+maintainer&btnG=Search
> And before
> applying for NM ? I'm especially interested,
Hello
> assume that an update to a package brings in a changed conffile, and
> because the local admin had changed the conffile, he is asked, and he
> refuses to accept the changed version.
This brings up an issue that is bothering me as a user since a long
time. Whenever I change a config file,
Package: wnpp
Severity: wishlist
Owner: Benjamin Mesing
This package is required by umlet 12.0beta1.
It seems to be no longer actively maintained.
* Package name: libjapa-javaparser-java
Version : 1.0.8
Upstream Author : Júlio Vilmar Gesser jges...@gmail.com
* URL
48 matches
Mail list logo
