Package: wnpp
Severity: wishlist
Owner: Carles Pina i Estany
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-asyncclick
Version : 8.1.7.0+async
Upstream Contact: python-trio team (to be confirmed)
* URL : https://github.com/python-trio/asyncclick
Package: wnpp
Severity: wishlist
Owner: Carles Pina i Estany
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-ring-doorbell
Version : 0.8.3
Upstream Contact: Marcelo Moreira de Mello
* URL : https://github.com/tchellomello/python-ring-doorbell
Package: wnpp
Severity: wishlist
Owner: Carles Pina i Estany
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-ping3
Version : 4.0.4
Upstream Contact: kyan001
* URL : https://github.com/kyan001/ping3
* License : MIT
Programming Lang: Python
Package: wnpp
Severity: wishlist
Owner: Carles Pina i Estany
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: qnetload
Version : 1.3.2
Upstream Contact: Carles Pina i Estany
* URL : https://github.com/cpina/qnetload
* License : GPL-3.0
Package: wnpp
Severity: wishlist
Owner: Carles Pina i Estany
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-cloudscraper
Version : 1.2.68
Upstream Contact: VeNoMouS
* URL : https://github.com/VeNoMouS/cloudscraper
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Carles Pina i Estany
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-pyaarlo
Version : 0.8.0.beta.8
Upstream Contact: Ntwrecked
* URL : https://github.com/twrecked/pyaarlo
* License : LGPL-3.0
Package: wnpp
X-Debbugs-Cc: debian-devel@lists.debian.org
Owner: "Gudjon I. Gudjonsson"
Severity: wishlist
* Package name: python3-trove-classifiers
Version : 2022.12.1
Upstream Contact:
* URL : https://pypi.org/project/trove-classifiers/
* License
Package: wnpp
Severity: wishlist
Owner: Jirawat Iamsamang
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-protobufjs
Version : 6.10.2
Upstream Author : Daniel Wirtz
* URL : https://protobufjs.github.io/protobuf.js/
* License : BSD-3-Clause
P
Package: wnpp
Severity: wishlist
Owner: Sao I Kuan
* Package name: dukpy
Version : 0.2.3
Upstream Author : Alessandro Molina
* URL : https://github.com/amol-/dukpy
* License : Expat
Programming Lang: Python
Description : Simple JavaScript interpreter
Package: wnpp
Severity: wishlist
Owner: Sao I Kuan
* Package name: benten
Version : 2020.06.03
Upstream Author : Kaushik Ghose
* URL : http://github.com/rabix/benten
* License : Apache-2.0
Programming Lang: Python
Description : Language server for
Package: wnpp
Severity: wishlist
Owner: Sao I Kuan
* Package name: duckpy
Version : 2.1.1
Upstream Author : Alisson Lauffe
* URL : https://github.com/AmanoTeam/duckpy
* License : Expat
Programming Lang: Python
Description : A simple Python library for
Package: wnpp
Severity: wishlist
Owner: Sao I Kuan
* Package name: cwlformat
Version : 2020.05.19
Upstream Author : Kaushik Ghose
* URL : https://github.com/rabix/cwl-format
* License : Apache-2.0
Programming Lang: Python
Description : opinionated
Package: wnpp
Severity: wishlist
Owner: Sao I Kuan
* Package name: seirsplus
Version : 0.0~git20200528.5c04080
Upstream Author : Ryan Seamus McGee
* URL : https://github.com/ryansmcgee/seirsplus
* License : Expat
Programming Lang: Python
Description
Package: wnpp
Severity: wishlist
Owner: Sao I Kuan
* Package name: insilicoseq
Version : 1.4.6
Upstream Author : Hadrien Gourle
* URL : http://github.com/HadrienG/InSilicoSeq
* License : Expat
Programming Lang: Python
Description : A sequencing
Package: wnpp
Severity: wishlist
Owner: Sao I Kuan
* Package name: ncbi-acc-download
Version : 0.2.6
Upstream Author : Kai Blin
* URL : https://github.com/kblin/ncbi-acc-download
* License : Apache-2.0
Programming Lang: Python
Description : Download
Package: wnpp
Severity: wishlist
Owner: Sao I Kuan
* Package name: smart-open
Version : 1.11.1
Upstream Author : Radim Rehurek
* URL : https://github.com/piskvorky/smart_open
* License : Expat
Programming Lang: Python
Description : utils for streaming
Package: wnpp
Severity: wishlist
Owner: Sao I Kuan
* Package name: recan
Version : 0.1.2
Upstream Author : Yuriy Babin
* URL : https://github.com/babinyurii/recan
* License : Expat
Programming Lang: Python
Description : genetic distance plotting for
Package: wnpp
Severity: wishlist
Owner: Sao I Kuan
* Package name: idseq-bench
Version : 0.0~git20191121.9623264
Upstream Author : Chan Zuckerberg Initiative
* URL : https://github.com/chanzuckerberg/idseq-bench
* License : Expat
Programming Lang: Python
Dzień dobry,
Zastanawiasz się ile powinna kosztować nowoczesna *Strona WWW*?
Odpisz na tego maila w treści wpisując *TAK*,
a my błyskawicznie zaproponujemy Ci atrakcyjne warunki dla Twojego biznesu!
/--/
/Agencja Interaktywna z charakterem/
Dzień dobry,
Zastanawiasz się ile powinna kosztować nowoczesna *Strona WWW*?
Odpowiedz na tego maila w treści wpisując *Tak*,
a my błyskawicznie zaproponujemy Ci atrakcyjne warunki dla Twojego biznesu!
/--/
/Agencja Interaktywna z charakterem/
Dzień dobry,
reprezentuję firmę zajmującą się tworzeniem nowoczesnych *_Stron i Sklepów_*
WWW.
Z przyjemnością podeślę naszą aktualną propozycję w tym zakresie.
Jeżeli mogę, proszę o e-mail zwrotny o treści *TAK.*
_ _ _
Z poważaniem,
Andrzej Mysiński
Strony i Sklepy WWW
Sorry if this is off-topic, but I can't help asking if that "15381 March 1977"
was on purpose or just from some wonky email client: 15380 days after March 1st
1977 happens to be April 10th 2019, so...
--
Pengcheng Xu
https://jsteward.moe/
> -Original Message-
>
Dzień dobry,
zajmujemy się tworzeniem nowoczesnych, responsywnych*_ Stron i Sklepów
internetowych. _*
Jeśli chcieliby Państwo otrzymać bezpłatną propozycję w tym zakresie dla
Państwa firmy prosimy o odpowiedź *TAK.*
- - - -
Pozdrawiamy Serdecznie,
Twórcy Stron i Sklepów WWW
Dzień dobry,
zajmujemy się tworzeniem nowoczesnych *Stron i Sklepów WWW*.
Jeśli chcieliby Państwo otrzymać propozycję w tym zakresie dla Państwa firmy
prosimy o odpowiedź "*_TAK_*".
Serdecznie Pozdrawiamy
Dzień dobry,zajmujemy się budową stron i sklepów internetowych dla firm. Jeżeli
chcieliby Państwo otrzymać bezpłatną, niezobowiązującą propozycję na ten
tematprosimy o odpowiedź TAK na ten e-mail. Jeśli mają Państwo skonkretyzowane
wymagania dotyczące oferty, prosimy o wskazówki.--Serdecznie
Dzień dobry,reprezentuję nowoczesnej Agencję Interaktywną.Zajmujemy się budową
nowoczesnych oraz profesjonalnych Stron i Sklepów internetowych. Jeżeli mogę
przedstawić Państwu nieodpłatnie naszą aktualną propozycję dla Państwa firmy to
bardzo proszę o odpowiedź o treści "tak" na t
Package: wnpp
Severity: wishlist
Owner: Sagar Ippalpalli
X-Debbugs-CC: debian-devel@lists.debian.org,
pkg-go-maintain...@lists.alioth.debian.org
* Package name : golang-github-zyedidia-glob
Version : 0.0~git20170209.dd4023a-1
Upstream Author : Zachary Yedidia
* URL : ht
Package: wnpp
Severity: wishlist
Owner: Sagar Ippalpalli
X-Debbugs-CC: debian-devel@lists.debian.org,
pkg-go-maintain...@lists.alioth.debian.org
* Package name : golang-gopkg-data-dog-go-sqlmock.v1
Version : 1.3.0-1
Upstream Author : DATA-DOG
* URL : https://github.com/
On रविवार 04 फेब्रु 2018 10:49 म.नं., Adam Borowski wrote:
> On Sun, Feb 04, 2018 at 09:59:56PM +0530, I Sagar wrote:
>> I prepared the packaging of materia-gtk-theme. It is lintian clean
>> and tested with pbuilder.Further information about this package can
>> be
Hi,
I prepared the packaging of materia-gtk-theme. It is lintian clean
and tested with pbuilder.Further information about this package can
be accessed from the URL :
https://salsa.debian.org/isaagar-guest/materia-gtk-theme
It would be nice if it is maintained under Debian desktop group
On Wed, Nov 16, 2016 at 1:58 PM, Pau Garcia i Quiles
wrote:
[...]
> OpenSSL 1.0 only
> =
[...]
> * Some obscure feature (e. g. BlaBla20) may be missing or be difficult
> to support on a limited number of packages (e. g. apache2)
[...]
Sorry, it's ChaCha20, not
On Wed, Nov 16, 2016 at 1:26 PM, Ian Jackson
wrote:
> A maintainer should be ready to explain, and if necessary change,
> decisions they have taken. (Ideally wider consultation before taking
> such a decision would be better.)
>
> In the absence of input from the openssl maint
s - particularly,
> failures where the package compiles and seems to work, but has some
> kind of problem in its use of openssl APIs which constitutes a
> security problem.
>
[...]
I fully agree and I have been stating that for months.
In fact, yesterday I checked that my package witty now
, regardless of -DOPENSSL_API_COMPAT.
>
>
This whole "let's shove OpenSSL 1.1 down your throat" is a very bad idea,
IMHO.
My upstreams (witty and ace) have no plans to support OpenSSL 1.1 in the
next months.
I do not have enough knowledge with OpenSSL to feel comforta
Package: wnpp
Severity: wishlist
Owner: Sagar Ippalpalli
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-deprecated
Version: 0.0.1
Upstream Author: Fractal
(http://wearefractal.com/)
* URL : http://github.com/wearefract
Package: wnpp
Severity: wishlist
Owner: Sagar Ippalpalli
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-beeper
Version : 1.1.0
Upstream Author : Sindre Sorhus (sindresorhus.com)
* URL : https://github.com/sindresorhus/beeper
* License : Expat
y
> > later ?
>
> Certainly. 1.1 brings a lot of internal changes which will be beneficial in
> the long run. And of course's there a wide range of 1.1 features which
> will b
> e important during the lifetime of stretch (e.g. chacha20/poly1305
> support).
>
>
I
On Sun, Apr 10, 2016 at 10:24 PM, Henrique de Moraes Holschuh <
h...@debian.org> wrote:
> 1) make it clearn that static linking is to be used only when strongly
> justified (e.g. system rescue tools like sash).
>
>
As I see it, static libraries are mostly meant for the
On Tue, Sep 15, 2015 at 1:24 AM, Colin Watson wrote:
> > This is what I generally do: last release + "git" + ISO 8601 date and
> time
> > + 10-char substring of the commit id. I. e:
> >
> > 0.5+git20150531T211420-cdd9d98f2c-1
>
> IME it is in fact
r release coincided with your birthday.
>
> I will use this scheme from now on:
>
> 0.4+20150911
>
>
What if you take a second snapshot on that day?
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
On Mon, Sep 14, 2015 at 11:04 AM, Jakub Wilk wrote:
* Pau Garcia i Quiles , 2015-09-14, 10:46:
>
>> 0.5+git20150531T211420-cdd9d98f2c-1~vivid~pgquiles1
>>
>
> Still shorter than 1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-1.
> You're not trying hard enough.
On Mon, Sep 14, 2015 at 8:51 AM, Colin Watson wrote:
On Mon, Sep 14, 2015 at 07:51:09AM +0200, Thomas Koch wrote:
> > How would you format the upstream part of the packages version number?
> How
> > about 0.4+24+git+a5e5f9e?
>
> I wouldn't put the commit identifier in
e
> links to normal media in various places on our web sites, we should
> include links to the non-free media too, *with* some explanatory text
> describing the problems with non-free firmware and why it's not
> included by default. Also, similar better links to the firmware
>
d version. It's possible, but without the
> > appropriate tools, it's painful.
>
> I've been using yui-compressor to get the minified javascript.
>
> I never add any issue this it.
>
> Now if you are talking about generating one big javascript file
> cont
d version. It's possible, but without the
> > appropriate tools, it's painful.
>
> I've been using yui-compressor to get the minified javascript.
>
> I never add any issue this it.
>
> Now if you are talking about generating one big javascript file
> cont
Hello,
I am the maintainer of witty, a C++ library for web development.
In addition to the latest version of Debian, I provide backports of the
package for all the supported versions of Ubuntu in a PPA, and for Debian
oldstable in an OBS repository. I have been doing this for years.
So far
features.
Since before the fork, the libav developers have been sabotaging ffmpeg as
much as possible, in every "combat field": library names, library versions,
taking distributions hostage (ffmpeg package that installs libav!?), etc.
This is not the way to fork anything. This is a
On Fri, Aug 1, 2014 at 1:29 AM, Russ Allbery wrote:
> I personally don't have enough information to know why libav was chosen
> instead of FFmpeg, and the discussion on debian-devel so far has mostly
> come from FFmpeg advocates. So there's probably another side to the story
s. Looks
good to me. Maybe Andreas should have made a not-so-polite proposal?
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
k than 100 *really*
> minor security updates.
>
How is it better to have libav, which does a lot less security bugfixing,
in?
I'd rather have a library that fixes bugs than one that passes in order to
look "more secure". When in fact it's less.
--
Pau Garcia i Quiles
http://www
On Tue, Jul 29, 2014 at 6:10 PM, Andreas Cadhalpun <
andreas.cadhal...@googlemail.com> wrote:
> I don't have an opinion about ffmpeg vs libav, apart from how hard the
>> soname transitions are, especially in ubuntu where we somehow ended up
>> with ex-multimedia package
On Fri, Feb 7, 2014 at 5:52 PM, Andreas Beckmann wrote:
> If your upstream is git, you don't have monotonically increasing
> revision numbers, but (unordered) commit hashes. I usually use something
> based on 'git describe' as that gives you a number of commits si
rsion. It
> should also allow you to upgrade via new svn version (0.0-1~svnr1235), as
> well as new packaging of same svn version (0.0-2~svnr1234). Please,
> correct me, if there is a better method, here!
>
>
That's exactly what I had thought: 0.0-somenumber~svn123, where
Hello,
I am interested in packaging Skia ( https://code.google.com/p/skia/ ), the
2D library used in Chromium, Firefox and others. I need it because a
package I maintain (witty) is replacing GraphicsMagick with Skia.
I went to Skia's download page and... found there is none: Skia does not
celona on 15-16 March 2014, where Debian enthusiasts from
> far and wide will gather to talk about the latest Debian changes
> and the Debian community, as well as to meet new and old friends.
>
[...]
Is this conference limited to women only? (it's not clear from the CfP or
the webs
On Sat, Dec 14, 2013 at 11:53 PM, John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Well, to be honest, I think the problem is actually libav, not mplayer.
> Most users prefer the original ffmpeg over libav from my own experience.
>
Agreed
Furthermore,
XFCE could be an
interesting talk, BTW.
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
On Fri, Oct 25, 2013 at 12:50 PM, Andrey Rahmatullin wrote:
> > Why are we still talking about CDs? Didn't everybody move to DVDs a
> century
> > ago?
> And then they moved away from DVDs too.
> I guess we are talking about install images to download (where you usuall
nes which only have a CD
reader can use USB or an external DVD unit and let the project move to
DVDs.
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
On Wed, Aug 28, 2013 at 4:55 PM, Neil McGovern wrote:
> I think you have a very valid point here. I kind of doubt many people
> would
> > like to run on a five year old desktop.
> >
>
> Stats seem to disagree:
>
> http://marketshare.hitslink.com/operating-sys
7;t respond?
>
>
Then, and only then, as a last resort, the Security Team / LTS Team takes
care of the problem
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
On Tue, Aug 27, 2013 at 12:03 PM, Lars Wirzenius wrote:
On Tue, Aug 27, 2013 at 11:53:47AM +0200, Pau Garcia i Quiles wrote:
> > But I'd like to stress we need *all* developers to be involved fix bugs
> > (esp. security) in their packages in all the supported releases, not on
;s how I'd like the Security Team to work. It would
alleviate the burden on them and move the bugfixing/security fixing to the
people who know the package better and are probably in touch with upstream.
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
e, especially if we
want 5 years support for the *whole* archive (IMHO Ubuntu did a smart move
in regards to support when it split the archive in main/universe/multiverse
and decided to support only main).
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
On Wed, Aug 21, 2013 at 5:45 PM, Kevin Chadwick wrote:
Does anyone even know for sure what the decision to switch was actually
> based upon?
>
Not really, but I have seen Debian rejected at several companies
(customers) due to too-short support of old releases and too-far away
releases. Bo
On Wed, Aug 21, 2013 at 1:48 AM, Ben Hutchings wrote:
Ubuntu uses a combination of driver backports and newer kernel versions
> in LTS releases.
>
>
As Clint, Philipp and you say, I was wrong.
However, I don't see that as an insurmountable argument against Debian
LTSs. It &q
ity team. Of course some package maintainers do help.
>
> I consider it part of my responsibility as a package maintainer to provide
> security support for my packages for as long as Debian does. If I felt
> like I couldn't do that, I would orphan the package or look at having it
> rem
duty as Debian
> > developers. Sure, packaging new upstream versions is always more exciting
> > than fixing a broken version/package but it needs to be done.
>
> You seem to be saying "this is an important thing to do - will you
> all please go and do it".
>
>
upgrade the kernel to LTS+1's ?
>
AFAIK Ubuntu does not add drivers for new hardware to any version save for,
maybe, some exceptional cases (that I cannot remember, frankly).
Quite the opposite: it's the hardware manufacturers themselves who are
compelled to provide drivers f
On Tue, Aug 20, 2013 at 12:46 PM, Steve Langasek wrote:
> On Mon, Aug 19, 2013 at 11:48:13PM -0400, Michael Gilbert wrote:
> > > Russ already replied and I agree with its reply. Just to say that
> Debian
> > > usually has a 3 year support. This is the kind of misguiding t
of
> 5-year security support. This support only applies for packages in
> main. A common example is nginx which is in universe. Packages in
> universe are just unsupported. They may or may not get any security
> support. If you need to advocate for Debian vs Ubuntu, I think this is a
&g
Hello,
I am the maintainer of Wt [1], a C++ web development library (think of Qt
or Gtk+ for the web) and web server.
My upstream [2] sent me a mail asking about mixing C++03 and C++11. My
understanding is it is not possible for a variety of reasons, unless all
players take great care (see [3
b for a
> couple of years. We recently ran Mayhem on almost all ELF binaries of
> Debian Wheezy (~23K binaries) [2], and it reported thousands of
> crashes.
>
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
On Sun, Jun 23, 2013 at 6:56 PM, Thomas Koch wrote:
I'm currently switching my laptop (again) and I have the following vision:
> The Debian system should provide tools to make it possible to switch over
> from
> one machine to another in a matter of minutes without le
Hello,
What is the right way to contact the Security Team? I have tried the
tracker, and a variety of e-mail addresses but nothing yet (maybe I'm doing
something wrong?). An update to Debian 7 was released today without a
security fix for my package jquery-jplayer, even though the fix has
On Fri, May 17, 2013 at 4:31 AM, Chow Loong Jin wrote:
> On 17/05/2013 01:01, Pau Garcia i Quiles wrote:
> >
> > Patch releases are NOT available as zip files and the list of
> wrongdoings is long:
> > - Patch releases are only available
Hello,
I am having trouble with my package jquery-jplayer (a JavaScript library
with Flash fallback) and I would like to ask for advice on how to proceed
Major and minor releases are available as zip files from the official
website ( http://jplayer.org/download/ ) and they are tagged in the git
On Thu, May 2, 2013 at 6:02 PM, Thibaut Paumard wrote:
> Questions:
> - How will this affect the speed at which Ubuntu users can get updates?
> - Should we keep macfanctld in launchpad/mactel repo? Or is there a
> smarter way if Debian package it?
What I do for Wt ( http://package
On Fri, Apr 26, 2013 at 11:50 PM, Bill Allombert <
bill.allomb...@math.u-bordeaux1.fr> wrote:
> So I do not think it is fair to restrict JPEG support in Debian to 1998
> image
> processing technology.
>
>
According to this mail by the Fedora KDE maintainer, ISO reject
;
mike.gabr...@das-netzwerkteam.de> wrote:
> Hi Ondřej,
>
> I have just uploaded libjpeg-turbo to Debian and it still hovers in NEW
> [1].
>
> On Mi 24 Apr 2013 11:23:04 CEST Ondřej Surý wrote:
>
> Debian has already open ITP[3] #602034 for libjpeg-turbo, which
>> suppor
lity is a complete opposite), or
> that configuration files are less human-readable than shell scripts.
>
I guess his point is session bus vs system bus.
I have suffered myself services which offer some DBus calls only over the
session bus, not the system bus, while my use case was exactly I ne
Hello,
This blogpost is months old but it makes some interesting reflections:
http://www.pappp.net/?p=969
I wonder what's Debian position in regards to FLOS* vs Unix philosophy. Is
there one, at all? (I can't remember reading one, my apologies if this was
discussed and I have n
On Wed, Nov 14, 2012 at 11:43 PM, Ben Hutchings wrote:
> I believe the regression (removal of support for firmware loading
> during module loading) has been fixed. However, the udev developers
> *knew in advance* that this would be a problem, reported such uses
> of firmware load
nrelated
> packages, possibly many of them, will become RC-instabuggy.
I'd say it's not a problem.
If one day the package containing the corresponding source vanishes
from the archive, the other package (witty, in my case) would not be
buildable, as witty build-depends on libjs-jquer
On Wed, Aug 22, 2012 at 8:30 PM, Russ Allbery wrote:
> I think the debate in this thread is about whether it makes sense to
> require removing the minimized version from the upstream source when we
> don't install that file or otherwise use it in the binary package (because
> t
a minifier may use generate
shortened variable names randomly.
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
On Sat, Aug 18, 2012 at 8:06 PM, Jakub Wilk wrote:
> * Pau Garcia i Quiles , 2012-08-17, 13:39:
>
>>> 3) Make a new source package containing every jQuery version existing in
>>> the wild, then build depend on that.
>>
>> FTP Masters do not like that soluti
s of this?
>> http://lintian.debian.org/tags/source-contains-prebuilt-windows-
> binary.html
>
> This includes:
>
> tcltrf (source)
> * win/msvcrt.dll
>
> This is part of Windows. I don't expect Debian has been granted
> permission to distribute it. :)
Are you sur
haël proposes is indeed not good
but I'd say this one would clear the issues:
"The program ust include source code for all the files that are used
in building the Debian binary packages"
Which means:
- If upstream is including jquery.min.js but I'm not using it because
I'm u
ancement to uupdate if it could deal with a list
>> > > > of files (wildcard strings that could be feed to `rm -rf`) which should
>> > > > be removed from the upstream tarball? This could simplify repackaging
>> > > > to a certain amount.
>> > >
On Fri, Aug 17, 2012 at 1:14 PM, Jakub Wilk wrote:
> 3) Make a new source package containing every jQuery version existing in the
> wild, then build depend on that.
FTP Masters do not like that solution.
Vincent's question was due to FTP masters complaining about the
package '
Package: wnpp
Followup-For: Bug #662736
Owner: "Pedro I. Sanchez"
Package: wnpp
Followup-For: Bug #662736
Owner: "Pedro I. Sanchez"
Package: wnpp
Followup-For: Bug #662736
Owner: "Pedro I. Sanchez"
Package: wnpp
Severity: wishlist
* Package na
On Fri, May 4, 2012 at 6:53 PM, Steve Langasek wrote:
> Hi Pau,
>
> On Fri, May 04, 2012 at 04:24:21PM +0200, Pau Garcia i Quiles wrote:
>> Regarding the often-mentioned "many users run 'node script' from the
>> command-line"... so what? If we can get enou
been an log struggle between the nodejs package and the node
> package, which is still unresolved (bug #611698 for example) And I
> wonder now what the future should look like.
>
> To summarize the problem:
> * the nodejs upstream binary is called "node", and the upstream
&g
re a bit ugly but still look sensible
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm
On Thu, Nov 10, 2011 at 9:28 AM, Fabian Greffrath wrote:
> Am 09.11.2011 17:04, schrieb Pau Garcia i Quiles:
>>
>> Yes, that would be my advice. Unfortunately mingw32 is now too far
>> behind mingw-w64. The fork has become better than the original
>> project.
>
On Wed, Nov 9, 2011 at 5:04 PM, Fabian Greffrath wrote:
> So if I understand it correctly, it would be best to entirely drop mingw32,
> gcc-mingw32, mingw32-runtime and the other members of that family from
> Debian and concentrate on mingw-w64 (which then, as a bonus, could be spl
On Wed, Nov 9, 2011 at 2:16 PM, Simon McVittie wrote:
> Does mingw[32] have any particular advantages over mingw-w64, I wonder?
Not that I know. mingw-w64's CRT is more complete (it includes LFS,
which mingw32 does not, for instance), includes more up-to-date
compilers and handles t
ls-mingw-w64.
>
> Is there a principle behind all this or where can I help to clean this up?
> ;)
>
> Cheers,
> Fabian
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@l
e what's worse: a malfunctioning application or an insecure one.
Zygmunt's proposal of adding unit testing, etc to upstream is a noble
one but highly unrealistic, IMHO.
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
--
To UNSUBSCRI
1 - 100 of 140 matches
Mail list logo
