On 16 Aug 2014 16:19, "Lars Wirzenius" wrote:
> If you upload things to unstable that depend on things in NEW, nobody
> will be able to install or upgrade that package (until the dependency
> gets through NEW).
In this case however the 2nd package will also get blocked in New (Python3
support req
On Sat, Aug 16, 2014 at 11:07:01AM +1000, Brian May wrote:
> On that note, is it ok for me to upload packages that depend on packages
> stuck in NEW, or do I have to wait for the packages to clear NEW first? I
> have at least one pending Python3 package in this situation.
If you upload things to u
Le Fri, Aug 15, 2014 at 04:16:01PM +0200, Raphael Hertzog a écrit :
>
> while git is the most popular VCS for packaging, there's no clear rules
> on what you can expect in a random git packaging repository listed
> in Vcs-Git. I would like to fix this so that:
> - we can extract more useful data f
Henrique de Moraes Holschuh writes:
> On Fri, 15 Aug 2014, Steve Langasek wrote:
>> The alternative is handwaving and ignoring the fact that your package
>> repository is not a complete representation of your package as it
>> exists in the archive.
> What's wrong with storing the upstream tarbal
m...@linux.it (Marco d'Itri) writes:
> On Aug 15, Andrew Kelley wrote:
>> Can you explain what you mean by this, for someone who is relatively
>> new to packaging? What is the alternative to pristine-tar?
> The first step is to determine which problem you are trying to solve.
I want to be able
On Fri, 15 Aug 2014, Steve Langasek wrote:
> The alternative is handwaving and ignoring the fact that your package
> repository is not a complete representation of your package as it exists in
> the archive.
What's wrong with storing the upstream tarballs themselves on a separate
branch, if you're
On Friday, August 15, 2014 23:04:54 brian m. carlson wrote:
> On Fri, Aug 15, 2014 at 08:17:16PM +0200, Marco d'Itri wrote:
> > On Aug 15, Raphael Hertzog wrote:
> > > - are there other important things to standardize?
> >
> > Do not try to make other people change their workflows without evident
On 16 August 2014 03:42, Paul Tagliamonte wrote:
> There's currently a big push to ensure we're all Python 3 compatable,
>
Note that there is a huge number of Python packages in Debian. It is very
possible that your favourite packages aren't available as Python3 Debian
packages, either because u
On 2014-08-16 01:15:45 +0800 (+0800), Thomas Goirand wrote:
[...]
> Yes. Producing orig.tar.xz out of upstream tag should be industrialized,
> and written in "some" tools, which we would all be using. I currently
> do: ./debian/rules gen-orig-xz, but that shouldn't be specific to my own
> packages.
Processing commands for cont...@bugs.debian.org:
> tag 758178 + moreinfo
Bug #758178 [general] general: screen resolution reverts to minimum when not
selected by KVM
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
758178: http://bugs.debian
tag 758178 + moreinfo
thanks
Hey,
Can you please provide us with some more details about your problem?
1. Are there any suspicious messages in dmesg or gnome log after the
screen resolution drops to 600x480? Can you please attach them both?
2. Can you ssh to an affected machine after it black
On Fri, 15 Aug 2014, Marco d'Itri wrote:
> On Aug 15, Steve Langasek wrote:
> > The alternative is handwaving and ignoring the fact that your package
> > repository is not a complete representation of your package as it exists in
> > the archive.
>
> It is not obvious why this would be a problem.
On Fri, Aug 15, 2014 at 08:17:16PM +0200, Marco d'Itri wrote:
> On Aug 15, Raphael Hertzog wrote:
> > - are there other important things to standardize?
> Do not try to make other people change their workflows without evident
> benefits (pro tip: "standardization" in itself is not one) or they wil
On August 15, 2014 4:57:19 PM EDT, Diogene Laerce wrote:
>
>
>On 08/15/2014 10:20 PM, Scott Kitterman wrote:
>> On August 15, 2014 1:42:04 PM EDT, Paul Tagliamonte
> wrote:
>>> On Fri, Aug 15, 2014 at 07:28:06PM +0200, Diogene Laerce wrote:
>
>[...]
>
>>>
>>> the /usr/bin/python command is unlikel
On Fri, Aug 15, 2014 at 04:16:01PM +0200, Raphael Hertzog wrote:
> Hello,
>
> while git is the most popular VCS for packaging, there's no clear rules
> on what you can expect in a random git packaging repository listed
> in Vcs-Git. I would like to fix this so that:
> - we can extract more useful
On 08/15/2014 10:20 PM, Scott Kitterman wrote:
> On August 15, 2014 1:42:04 PM EDT, Paul Tagliamonte
> wrote:
>> On Fri, Aug 15, 2014 at 07:28:06PM +0200, Diogene Laerce wrote:
[...]
>>
>> the /usr/bin/python command is unlikely to change soon; more
>> information
>> on how this should be tre
On Aug 15, Steve Langasek wrote:
> The alternative is handwaving and ignoring the fact that your package
> repository is not a complete representation of your package as it exists in
> the archive.
It is not obvious why this would be a problem.
--
ciao,
Marco
signature.asc
Description: Digita
On 08/15/2014 07:42 PM, Paul Tagliamonte wrote:
> On Fri, Aug 15, 2014 at 07:28:06PM +0200, Diogene Laerce wrote:
>> Does someone have any clue or hint on the upgrade of Debian to Python3
>> natively ?
>
> Python 3.4 is in Jessie, ready for action. I can confirm it works great,
> It's all I use
On Fri, Aug 15, 2014 at 01:36:24PM -0700, Andrew Kelley wrote:
> On Fri, Aug 15, 2014 at 11:17 AM, Marco d'Itri wrote:
> > > - shall we standardize the "pristine-tar" branch?
> > Shall we kill pristine-tar instead, since it is mostly a waste of space
> > for everybody without an md5 fetish?
> Ca
Hi,
Le 15/08/2014 13:59, Stephen Allen a écrit :
> On Wed, Aug 13, 2014 at 06:15:05PM +0200, Cyril Brulebois wrote:
>> The Debian Installer team[1] is pleased to announce the first beta
>> release of the installer for Debian 8 "Jessie".
>
> Thanks.
+1
> Any changes between alpha errata to beta?
On Aug 15, Andrew Kelley wrote:
> > > - shall we standardize the "pristine-tar" branch?
> > Shall we kill pristine-tar instead, since it is mostly a waste of space
> > for everybody without an md5 fetish?
> Can you explain what you mean by this, for someone who is relatively new to
> packaging? W
On Fri, Aug 15, 2014 at 11:17 AM, Marco d'Itri wrote:
> > - shall we standardize the "pristine-tar" branch?
> Shall we kill pristine-tar instead, since it is mostly a waste of space
> for everybody without an md5 fetish?
Can you explain what you mean by this, for someone who is relatively new t
On August 15, 2014 1:42:04 PM EDT, Paul Tagliamonte wrote:
>On Fri, Aug 15, 2014 at 07:28:06PM +0200, Diogene Laerce wrote:
>> Hi,
>>
>> Does someone have any clue or hint on the upgrade of Debian to
>Python3
>> natively ?
>>
>> Thank you,
>
>Hey Diogene,
>
>Python 3.4 is in Jessie, ready for ac
On August 15, 2014 10:16:01 AM EDT, Raphael Hertzog wrote:
>Hello,
>
>while git is the most popular VCS for packaging, there's no clear rules
>on what you can expect in a random git packaging repository listed
>in Vcs-Git. I would like to fix this so that:
>- we can extract more useful data from t
Hi,
2014-08-15 14:20 GMT+02:00 Michael Niedermayer :
> On Fri, Aug 15, 2014 at 02:53:09PM +0800, Thomas Goirand wrote:
>> On 08/14/2014 11:59 PM, The Wanderer wrote:
>> > On 08/14/2014 11:27 AM, Thomas Goirand wrote:
>> >
>> >> On 08/13/2014 07:53 AM, Kieran Kunhya wrote:
>> >
>> >> On 08/13/2014
On Aug 15, Raphael Hertzog wrote:
> - we can more easily share our git repositories with upstreams
> and downstreams
Did they ask for this?
> - how do we tag the upstream releases?
> - upstream/
Some of my packages just use the real upstream git tree as their
upstream branch, so the upstrea
Package: wnpp
Owner: Balint Reczey
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org
* Package name: libcli-framework-perl
Version : 0.05
Upstream Author : Karl Erisman
* URL : https://metacpan.org/release/CLI-Framework
* Lice
On 15/08/14 15:16, Raphael Hertzog wrote:
> Some initial questions and possible answers:
I've been hesitating on whether to ask this because it gets into
questions of workflow and repo structure that are very much a matter of
taste and don't have a single widely-declared-to-be-good answer, but I
t
On Wed, Aug 13, 2014 at 06:15:05PM +0200, Cyril Brulebois wrote:
> The Debian Installer team[1] is pleased to announce the first beta
> release of the installer for Debian 8 "Jessie".
Thanks.
[ ...]
>
> Known bugs in this release
> ==
>
> * Firmware handling: udev no
On Fri, Aug 15, 2014 at 07:28:06PM +0200, Diogene Laerce wrote:
> Hi,
>
> Does someone have any clue or hint on the upgrade of Debian to Python3
> natively ?
>
> Thank you,
Hey Diogene,
Python 3.4 is in Jessie, ready for action. I can confirm it works great,
It's all I use for my personal proje
Hi,
Does someone have any clue or hint on the upgrade of Debian to Python3
natively ?
Thank you,
--
“One original thought is worth a thousand mindless quotings.”
“Le vrai n'est pas plus sûr que le probable.”
Diogene Laerce
signature.as
On Fri, Aug 15, 2014 at 06:51:44PM +0200, Bill Allombert wrote:
> Please do not report RC bug for this. Priorities are adjusted by the FTP
> master
> team by batch using the overrides file. There is no need to report bugs
> against
> the packages.
Hi, I filed three bugs for the extreme, where pr
On Fri, 15 Aug 2014, Michael Biebl wrote:
> Am 15.08.2014 17:47, schrieb Gerrit Pape:
> > Package: rsyslog
> > Version: 8.2.2-3
> > Severity: serious
> > Justification: Policy 2.5
> >
> > Hi, the current rsyslog package version in testing is priority important
> > and depends on packages with prio
On 08/15/2014 10:16 PM, Raphael Hertzog wrote:
> Some initial questions and possible answers:
>
> - how do we name the various branches?
>
> - /master for the main development trunk (aka unstable in Debian)
> - / for alternate versions
>
> The goal here is to be able to host in the same re
Package: wnpp
Severity: wishlist
* Package name: cool-old-term
Version : no released version yet as it seems
Upstream Author : Filippo Scognamiglio
* URL or Web page : https://github.com/Swordifish90/cool-old-term
* License : GPLv3+ (some parts seem also GPLv2)
Descripti
On Fri, 15 Aug 2014, Christian Kastner wrote:
> On 2014-08-15 16:16, Raphael Hertzog wrote:
> > - pkg/
> > (note: git-buildpackage uses debian/ but I find this confusing
> > as we then also have the "debian/" prefix for ubuntu or kali uploads, we
> > don't need the vendor prefix as the usua
On Fri, Aug 15, 2014 at 06:31:39PM +0200, Michael Biebl wrote:
> Am 15.08.2014 18:10, schrieb Michael Biebl:
> > Am 15.08.2014 17:47, schrieb Gerrit Pape:
> >> Severity: serious
> >> Justification: Policy 2.5
>
> [..]
>
> > That this rule is violated in hundreds of cases [1] clearly shows that
>
Am 15.08.2014 18:10, schrieb Michael Biebl:
> Am 15.08.2014 17:47, schrieb Gerrit Pape:
>> Severity: serious
>> Justification: Policy 2.5
[..]
> That this rule is violated in hundreds of cases [1] clearly shows that
> there is something wrong which needs to be addressed in a more idiomatic
> way.
On Fri, 15 Aug 2014, Raphael Hertzog wrote:
> - how do we tag the package releases?
>
> - pkg/
> (note: git-buildpackage uses debian/ but I find this confusing
> - shall we standardize the "pristine-tar" branch?
IMHO it should be reserved for pristine-tar usage (as in "don't use it for
somet
On Fri, Aug 15, 2014 at 04:16:01PM +0200, Raphael Hertzog wrote:
> - how do we tag the package releases?
>
> - pkg/
> (note: git-buildpackage uses debian/ but I find this confusing
> as we then also have the "debian/" prefix for ubuntu or kali uploads, we
> don't need the vendor prefix as
On 2014-08-15 16:16, Raphael Hertzog wrote:
> - pkg/
> (note: git-buildpackage uses debian/ but I find this confusing
> as we then also have the "debian/" prefix for ubuntu or kali uploads, we
> don't need the vendor prefix as the usual versioning rules embed the
> downstream distribution
Am 15.08.2014 17:47, schrieb Gerrit Pape:
> Package: rsyslog
> Version: 8.2.2-3
> Severity: serious
> Justification: Policy 2.5
>
> Hi, the current rsyslog package version in testing is priority important
> and depends on packages with priority extra. Policy 2.5 states:
>
> "Packages must not de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/15/2014 11:23 AM, Thomas Goirand wrote:
> On 08/15/2014 08:20 PM, Michael Niedermayer wrote:
>>> Absolutely everyone should *always* be able to leave comments, be
>>> it positive or negative.
>>
>> yes, i fully agree and this also was always
On 08/15/2014 08:20 PM, Michael Niedermayer wrote:
> Yes, the tricky part in FFmpeg and Libav in relation to this is that
> theres quite a bit of code that is only well understood by a single
> person even if you would combine both projects together.
Hum... Hang on here then! Does this mean that,
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: libjs-jsencrypt
Version : 2.0.0+dfsg1
Upstream Author : Travis Tidwell
* URL : http://travistidwell.com/jsencrypt/
* License : Expat
Programming Lang: JavaScript
Description : RSA E
Hi!
On 2014-08-15 at 16:16 (CEST), Raphael Hertzog wrote:
> [...]
> - are there other important things to standardize?
Well, I don't know but I love this idea.
+1 for me.
Cheers.
--
Matteo F. Vescovi | Debian Maintainer
GnuPG KeyID: 4096R/0x8062398983B2CF7A
signature.asc
Description: Dig
Hello,
while git is the most popular VCS for packaging, there's no clear rules
on what you can expect in a random git packaging repository listed
in Vcs-Git. I would like to fix this so that:
- we can extract more useful data from the git repositories
- we can more easily share our git repositorie
On Fri, 15 Aug 2014, Ondřej Surý wrote:
> On Fri, Aug 15, 2014, at 15:37, Henrique de Moraes Holschuh wrote:
> > And any package that cannot build arch:all on a released arch for which
> > it produces binary packages potentially has a FTBFS bug, anyway, which
> > can be reported by any interested p
On Fri, Aug 15, 2014, at 15:37, Henrique de Moraes Holschuh wrote:
> And any package that cannot build arch:all on a released arch for which
> it produces binary packages potentially has a FTBFS bug, anyway, which
> can be reported by any interested parties. Exceptions would be arches
> that are t
On Fri, 15 Aug 2014, Raphael Hertzog wrote:
> On Fri, 15 Aug 2014, Hector Oron wrote:
> > Even building arch:all packages in one architecture might solve the
> > issue, I do not like that approach, as it holds other arches from
> > building until that "primary" arch has built arch:all packages.
>
On Fri, 15 Aug 2014, Hector Oron wrote:
> Even building arch:all packages in one architecture might solve the
> issue, I do not like that approach, as it holds other arches from
> building until that "primary" arch has built arch:all packages.
I understand the concern at the philosophical level bu
On Fri, Aug 15, 2014 at 02:53:09PM +0800, Thomas Goirand wrote:
> On 08/14/2014 11:59 PM, The Wanderer wrote:
> > On 08/14/2014 11:27 AM, Thomas Goirand wrote:
> >
> >> On 08/13/2014 07:53 AM, Kieran Kunhya wrote:
> >
> >> On 08/13/2014 06:30 AM, Michael Niedermayer wrote:
> >
> >>> Also ive off
Hello,
2014-08-13 22:59 GMT+02:00 Philipp Kern :
> On 2014-08-13 14:34, Raphael Hertzog wrote:
>> On Wed, 13 Aug 2014, Colin Watson wrote:
>>> I don't think there's a good reason to build them separately, and some
>>> good reasons not to (for example, it would waste a good deal of buildd
>>> time
Hi Svante, hi all,
On Fr 15 Aug 2014 11:02:28 CEST, Svante Signell wrote:
Please don't top post!
On Thu, 2014-08-14 at 15:12 +0100, envite wrote:
Why not MATE for all and put a11y into it?
Makes more sense for e.g. small computers like those in 3rd World
talked before.
Enviado de Samsun
Package: wnpp
Severity: wishlist
Owner: Pierre Rudloff
* Package name: solarus
Version : 1.2.1
Upstream Author : Nathan Moore
* URL : http://www.solarus-games.org/
* License : GPL
Programming Lang: C++
Description : Open-source Zelda-like game engine
Hi,
Quoting Guillem Jover (2014-08-13 13:48:11)
> On Tue, 2014-08-12 at 13:27:38 +0200, Ansgar Burchardt wrote:
> > There are also other problems that need to be eventually addressed: as far
> > as I know there are some source packages producing arch:all binaries that
> > cannot be built on all ar
On Thu, 14 Aug 2014, Thomas Goirand wrote:
> What would probably work better would be to add the python library
> inside upstream code.
That would work as well.
> But then we have another issue: the Python module is supposed to be
> packaged as python-, and the JS libs are supposed to be
> packa
Please don't top post!
On Thu, 2014-08-14 at 15:12 +0100, envite wrote:
> Why not MATE for all and put a11y into it?
>
> Makes more sense for e.g. small computers like those in 3rd World talked
> before.
>
> Enviado de Samsung Mobile
I'm all for it, and am willing to help making it happen. Wi
Quoting Thomas Goirand (2014-08-15 09:26:20)
> On 08/15/2014 12:28 AM, Jonas Smedegaard wrote:
>> Quoting Thomas Goirand (2014-08-14 09:26:05)
>>> Note that the XStatic python modules aren't just meta packages, they
>>> also offer a mechanism for a Python script to discover where to find
>>> a gi
On Fri, Aug 15, 2014 at 2:53 PM, Thomas Goirand wrote:
> Hum... Well, to me, what's important is that the code gets
> peer-reviewed.
... by both humans and by automatically by computers; compiler
warnings, static analysis tools, fuzz testers etc.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On 08/15/2014 12:28 AM, Jonas Smedegaard wrote:
> Quoting Thomas Goirand (2014-08-14 09:26:05)
>> Note that the XStatic python modules aren't just meta packages, they
>> also offer a mechanism for a Python script to discover where to find a
>> given static file in the system (which really, isn't
61 matches
Mail list logo
