Package: wnpp
Severity: wishlist
Owner: Marc Dequènes (Duck)
X-Debbugs-Cc: debian-devel@lists.debian.org
Control: block -1 with 1010247
* Package name: wlgreet
Version : 0.3
Upstream Author : Kenny Levinsen
* URL : https://git.sr.ht/~kennylevinsen/wlgreet
* License
Package: wnpp
Severity: wishlist
Owner: Marc Dequènes (Duck)
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: greetd
Version : 0.8.0
Upstream Author : Kenny Levinsen
* URL : https://git.sr.ht/~kennylevinsen/greetd
* License : GPL-3
Programming
Quack,
On 2019-05-14 11:24, Sean Whitton wrote:
Switching the entire Haskell ecosystem over to use dh would be a
massive
amount of work, as the new dh_haskell would need a lot of testing etc.
So Haskell libraries and apps would probably have to be one of the
exceptions.
It took months to get
Quack,
On 2018-07-25 22:35, Jonathan Dowland wrote:
I think it would be worthwhile to file a BTS bug so it can be easily
tracked which versions of the package we distribute still carry this
bug, so I will do that.
Agreed, we should ensure all fixes are in all versions and I'd be glad
to have
Quack,
On 2018-07-22 19:16, Rens Houben wrote:
In other news for Sun, Jul 22, 2018 at 09:39:51AM +0900, Marc Dequènes
{ A whole lot of refuge in technicalities snipped }
There was no "technicalities". I decided to explain my decision and not
base it on vague feelings or emotional outburst
Quack,
On 2018-07-22 09:52, Mike Hommey wrote:
but... https://git.weboob.org/weboob/devel/merge_requests/232
Thanks for pointing this out. It's not in yet and I've just asked
upstream to clean this mess.
\_o<
--
Marc Dequènes
Quack,
It seems the project is leaving the decision about Weboob onto me, so
I'll try to address it.
The diversity statement tells me we should welcome others even if they
are very different and with conflicting opinions but nothing beyond
that. There is no policy part that I found helpful.
Quack,
(This is a followup of the thread started on debian-private. This is not
a private matter at all, and we should have discussed this openly from
the start.)
It has been brought to my attention that this package, its name and the
name of the binaries and further content was deemed offen
ng
snapshots of configurations would help ensure quality, and could be
commented inside the documentation, so managed by the documentation
maintainers for example.
> PS: Duck isn't subscribed to these lists anymore? Just checking to avoid
> harassing him with tons of mails
I'm still
may still ask for help.
> 2. It won't decompile python2.4 bytecode. This will be somewhat harder
>to fix (and I haven't done it yet).
If it is not able to decompile recent python version, then it is a kind
of useless one. Python 2.4 is out since a while, what are upstream plans
f
al persons of a team so as to avoid this situation, and you're
talking about planned major feature changes. You're out of topic.
--
Marc Dequènes (Duck)
pgp1nwqwLKqBL.pgp
Description: PGP signature
al persons of a team so as to avoid this situation, and you're
talking about planned major feature changes. You're out of topic.
--
Marc Dequènes (Duck)
pgpPDJSYpppnV.pgp
Description: PGP signature
important reasons like the control auto
generation one, a warning is displayed (so you know you cannot count on
it). Undocumented parts are either documentation lack or internal stuff
you should not care about and count on. Nevertheless, i do agree this
needs improvements (please reply to the part of the thread with bubule
if you want to continue on this specific topic).
--
Marc Dequènes (Duck)
pgpGN7Uu1aDZd.pgp
Description: PGP signature
Joey Hess <[EMAIL PROTECTED]> writes:
> To be fair, debhelper is not co-maintained either.
I never noticed it wasn't, but i do think it should. Fact is you're
taking far much care when integrating changes, that's a major
difference.
--
Marc Dequènes (Duck)
pgpmw2zfDo
people use it than the one in the package, but this is not an ideal
situation.
--
Marc Dequènes (Duck)
pgppLqfQbzMvs.pgp
Description: PGP signature
nyone
with knowledge on CDBS and translations.
The original documentation can be found here:
http://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml
(sources are in the 'cdbs-doc/' directory)
--
Marc Dequènes (Duck)
pgpXyuODfIshx.pgp
Description: PGP signature
this procedure. Such a lightweight proposal
should never have passed the DAM filter in step 1. Moreover, having only
1*Q persons needed to open such a GRAVE process is so incredible !!!
--
Marc Dequènes (Duck)
pgpr9sGDR1jmC.pgp
Description: PGP signature
problem a
needs,
bugs, build issues, ... it is, from my point of view, also a question of
respect and
courtesy.
Sorry for being so idealist...
Duck
P.S. :
Notice i am still signing as "Duck" and not "Marc DequÃnes", because it the
way most
people know me and call me in re
lly important to give a word on the situation.
When you find several ITPs filled more than 6 years ago and an official DD
"seems" not to mind about using the BTS properly, you may wonder about the
future of your prefered distribution.
Thx for your explanation and proposal.
Duck
-BE
I really wonder why the NMP exist, once DD you can do things without being
serious any more, and many agree.
Filip is probably a good packager, but i still disagree on that way to do.
I told my opinion and this conversation is over.
Duck
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hamish Moffatt <[EMAIL PROTECTED]> writes:
>> I was writing an ITP when you posted that and suddendly, saw all my
>> work preparation turned into ashes.
>
> "Duck", why did you do any preparation before writing the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chad Walstrom <[EMAIL PROTECTED]> writes:
> Duck, perhaps you should have written the ITP earlier. Instead of
> complaining, why don't you thank your fellow developer and offer to
> co-maintain the package. Perhaps the packag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Coin,
Somenone already did the job and forgot the BTS usage.
(see #163252 for more details)
So, i'm closing those ITPs.
Duck
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8
ecause i'm sure
u do not have a second for such social activities.
Thx for remebering you're not alone in the world...
Duck
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQE/tq7ssczZc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Winston <[EMAIL PROTECTED]> writes:
> On Sat, 2003-11-08 at 15:18, Joe Drew wrote:
>> On Sat, 2003-11-08 at 07:41, Duck wrote:
>> > Songwrite is a guitar tablature (fingering notation) editor and player,
>&g
forgot the dummy packages depending on the right python
version, thx for telling me.
A new release correcting this on editobj, py2play, pyopenal, soya, and genetic
will be uploaded soon.
Duck
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8
g the project,
so did he.
to be continued...
Duck
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQE/ramGsczZcpAmcIYRArwxAKCIQGQE2bMWNNtnIQXF7xV8oFzjEACeKNoG
q0nn+jdBuUFtM7AZVU3FoPw=
=gvZf
-
bad writtent ITP, please ? (Bug #219200)
Thx for help.
Duck
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQE/rOsPsczZcpAmcIYRAtXkAJ41qHFoE86nOvrKGj1nSsS+6kSFaACeMnon
akpp++saSWor3ja2jC6JTsI=
description was crap.
Duck
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQE/rOkbsczZcpAmcIYRAty2AKCnHL+Jakkr2cKFOWzgyX2nlxPcfgCeJH4r
pCOU9jucUnhl8QbuNY6SfRw=
=HnpW
-END PGP SIGNATURE-
external programs.
Songwrite was formely know as GTablature.
Duck and Jiba
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQE/rOR4sczZcpAmcIYRAlNzAJ4gpU9hMyqRwM8iqJwAdCPpxQbklACcCjoP
MOSl+i4ZiiDIySq8d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Coin,
This ITP was badly written as it was my first attempt, sorry.
Here is a better one with an improved Description :
* Package name: ircd-ptlink
Version : 6.16.1
Upstream Author : PTlink Coders team <[EMAIL PROTECTED]>
* URL or We
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This ITP was badly written as it was my first attempt, sorry.
Here is a better one with an improved Description :
* Package name: ircd-ptlink
Version : 2.23.6
Upstream Author : PTlink Coders team <[EMAIL PROTECTED]>
* URL or Web page
ffects,
filters, and converters through the LADSPA plugin architecture (band pass
filter, frequency shifter, reverb, flanger, pitch scaler, pink noise,
stereo to mono converter, and many others).
Duck
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Coin,
Gnusound is using OSS only.
Yet, afaik there's no plan to add Alsa/Esd/Arts/... support.
The included TODO file reads that the upstream author is likely to fix
many technical and cosmetic bug before adding big features.
Duck
-BEGI
also sprach David Whedon (on Mon, 07 May 2001 01:10:02PM -0700):
> Lame cannot be included in Debian, please see:
> http://www.debian.org/devel/wnpp/unable-to-package
thanks for the reply(ies). i hope i didn't inconvenience anyone with
my ignorant post. i'll be better in the future, promise!
mart
hi developers,
this is my first message, i hope it's appropriate. there's talk going
on on the users mailing list about lame and its absence from the
package tree. i would like to adopt the lame mp3 encoder as a debian
package and was wondering if there are any objections? is there
already a mainta
hi developers,
this is my first message, i hope it's appropriate. there's talk going
on on the users mailing list about lame and its absence from the
package tree. i would like to adopt the lame mp3 encoder as a debian
package and was wondering if there are any objections? is there
already a mainta
38 matches
Mail list logo
