Hello, I am preparing the new silx package and I got these error messages from
adequate
This package produce the silx python module but install also a bunch of files
for qtdesigner
in the rules file with this command.
# install the qtdesigner files only for the python3 package
d
[PICCA Frederic-Emmanuel, 2018-08-02]
> Hello, I am preparing the new silx package and I got these error messages
> from adequate
>
> This package produce the silx python module but install also a bunch of files
> for qtdesigner
> in the rules file with this command.
>
> # install the qtd
thanks a lot
Hey folks,
Today, we've had a productive BoF session at DebConf18, with around 12 people
in attendance (unfortunately, this was not held in a recorded room).
Here are the raw notes: https://gobby.debian.org/export/debconf18/bof/python
There are two team-wide items that would be of general intere
On Thu, Aug 02, 2018 at 06:50:59AM +, PICCA Frederic-Emmanuel wrote:
> Hello, I am preparing the new silx package and I got these error messages
> from adequate
>
> This package produce the silx python module but install also a bunch of files
> for qtdesigner
> in the rules file with this com
> A bit off-topic, but you should not use Qt 4 in new packages.
> See https://lists.debian.org/debian-devel-announce/2017/08/msg6.html.
I did the migration to qtcreator :))
do not worry
Fred
Hi guys,
čt 2. 8. 2018 v 23:25 odesílatel Nicolas Dandrimont
napsal:
> 2/ Ondrej Novy will do a mass-change from git-dpm to gbp on team packages.
> Related to this, Piotr will review and amend the team policy if necessary,
> as
> well as work on the pipeline to make sure the policy gets publishe
On 2018-08-03 11:06, Ondrej Novy wrote:
> 2. change default branch to debian/master
How about changing "upstream" to "upstream/latest" (for upstream
releases, typically for unstable) and "upstream/master" (for
following upstream master, typically for experimental)?
On August 3, 2018 3:51:00 AM UTC, "W. Martin Borgert"
wrote:
>On 2018-08-03 11:06, Ondrej Novy wrote:
>> 2. change default branch to debian/master
>
>How about changing "upstream" to "upstream/latest" (for upstream
>releases, typically for unstable) and "upstream/master" (for
>following upstre
On 2018-08-03 04:33, Scott Kitterman wrote:
> On August 3, 2018 3:51:00 AM UTC, "W. Martin Borgert"
> wrote:
> >How about changing "upstream" to "upstream/latest" (for upstream
> >releases, typically for unstable) and "upstream/master" (for
> >following upstream master, typically for experimental
10 matches
Mail list logo
