Am Freitag, den 01.11.2019, 00:48 +0100 schrieb gregor herrmann:
> On Thu, 31 Oct 2019 13:54:11 -0700, Sean Whitton wrote:
>
> > On Thu 31 Oct 2019 at 12:00PM +01, Gert Wollny wrote:
> > > "Then, you either prepare the NMU in a fork of the original
> > > pack
Dear all,
with salsa and most of the packaging going on in git I wonder whether
we could add using MRs as an alternative way to communicate the diff
that is related to an NMU instead of adding a patch to the related bug.
When preparing an NMU people might already be using git anyway, and if
one
Am Sonntag, den 13.05.2018, 15:18 -0400 schrieb Jeremy Bicha:
> Respectfully, you are the only one complaining about gconf's
> removal.
I might not have been complaining here, but I'm also not that happy
about some removals, and I don't understand the resistance to let
someone adopt the package. A
Am Mittwoch, den 18.04.2018, 14:55 +0500 schrieb Andrey Rahmatullin:
> On Wed, Apr 18, 2018 at 11:23:23AM +0200, Martin Steigerwald wrote:
> > As just someone who mostly maintains one package (fio - flexible
> > I/O tester) I can certainly understand how you feel about that
> > Lucas removed you as
Am Montag, den 16.04.2018, 09:58 +0200 schrieb Tobias Frost:
>
> Was mentioned on the salvaging packages BoF at Montreal:
> https://lists.debian.org/debian-devel/2012/09/msg00654.html
>
Indeed, and I think one of the key points in that proposalo is that the
last upload was an NMU - and as far a
Sorry, hit the wrong button and the email went out incomplete, if yo
read the other mail you can skip to (--).
Am Mittwoch, den 11.04.2018, 13:51 +0200 schrieb Gert Wollny:
> Am Mittwoch, den 11.04.2018, 07:08 + schrieb Lumin:
> > Hi folks,
> >
> > I'm sorry f
Am Mittwoch, den 11.04.2018, 07:08 + schrieb Lumin:
> Hi folks,
>
> I'm sorry for repeating this topic in -devel without reading all the
> followups in this thread [1] which seems to be dying. Is there
> any conclusion in the thread[1] ?
As the initator of this thread I'd like to chime in. My
Am Donnerstag, den 29.03.2018, 21:43 +0300 schrieb Adrian Bunk:
> On Wed, Mar 28, 2018 at 08:08:07PM -0700, Russ Allbery wrote:
> > Boyuan Yang <073p...@gmail.com> writes:
> >
> > > * Upstream released new version and bumped SONAME to 2
> > > * -dev package didn't change its name
> > > * My mentor
Am Mittwoch, den 07.03.2018, 20:35 +1100 schrieb Ben Finney:
> Gert Wollny writes:
>
> > […] simply asking the peers doesn't make the process very public.
>
> That is, IIUC, by design and for good reason.
>
> Before a review of the copyright status of the
Am Mittwoch, den 07.03.2018, 08:09 +0100 schrieb Joerg Jaspert:
>
> If someone comes up with a patch to process-new which does this in a
> halfway reliable way, it doesn't need a long time wasting thread on
> devel to get it.
Sure thing, I'll give it a try. Since I'm not familiar with the dak
cod
Am Montag, den 05.03.2018, 14:27 + schrieb Chris Lamb:
> Hi Gert,
>
> > (1) Given that all new source package come with an ITP bug, when a
> > package must be rejected, the FTP team could CC this bug in the
> > rejection message.
>
> Do you have any concrete suggestions for packages that are
Dear all,
thanks for all the feedback, based on this I'd like to modify the
proposal like follows:
(1) Given that all new source package come with an ITP bug, when a
package must be rejected, the FTP team could CC this bug in the
rejection message. This would have the advantage that for everyon
Am Freitag, den 02.03.2018, 17:49 +0100 schrieb Philip Hands:
> Gert Wollny writes:
>
> > Am Freitag, den 02.03.2018, 14:01 +0100 schrieb Iustin Pop:
> > >
> > > How do you (we) know the package indeed is DFSG-compliant, if
> > > there
> > > is n
Am Freitag, den 02.03.2018, 07:39 -0500 schrieb Scott Kitterman:
> On Friday, March 02, 2018 01:00:57 PM Gert Wollny wrote:
> > Dear all,
> >
> > as the one who is the uploader of the package that is currently
> > longest
> > in the NEW pipeline (vtk7)
Am Freitag, den 02.03.2018, 14:01 +0100 schrieb Iustin Pop:
>
> How do you (we) know the package indeed is DFSG-compliant, if there
> is no license information? If upstream cannot bother to provide
> headers, how do we know the code is indeed licenced under the claimed
> licence?
> Etc.
> Note:
Am Freitag, den 02.03.2018, 13:38 +0100 schrieb Philip Hands:
> Gert Wollny writes:
> ...
> > Short version: Use the salsa per-package issue tracker for problems
> > that come up with the review in NEW.
>
> Is there any significant benefit that this brings over having t
Am Freitag, den 02.03.2018, 14:15 +0200 schrieb Lars Wirzenius:
>
>
> Counter proposal: let's work on ways in which uploaders can make it
> easy and quick for ftp masters to review packages in NEW. The idea
> should be, in my opinion, that any package that requires more than a
> day of work to re
Am Freitag, den 02.03.2018, 13:10 +0100 schrieb Samuel Thibault:
> Hello,
>
> This reminds me a discussion at debconf: it could be useful that
> anybody be able to submit issues with the NEW package, so that for
> obvious things ftpmaster doesn't even have to spend time, and ideally
> ftpmaster wo
Dear all,
as the one who is the uploader of the package that is currently longest
in the NEW pipeline (vtk7), I'd like to make a proposal how
transparency and also the interaction from non ftp-master members to
review packages could be improved.
Short version: Use the salsa per-package issue tra
Am Freitag, den 02.02.2018, 09:32 +0100 schrieb Thomas Goirand:
[...]
> O: Package is unmaintained, hurry or the package is in danger to be
> removed.
I risk to differ, if this were so, we wouldn't have +700 packages that
have the QA team as maintainer, and quite a few have a five or even
six-fig
Am Samstag, den 16.12.2017, 13:20 +0100 schrieb Jonas Smedegaard:
>
> If it is "not worth [your] time" to cover _all_ sources for the
> project you are maintaining then perhaps you should team up with
> someone who does find it worthwhile to do that part of the packaging
> maintenance - because th
Hello Mathieu,
Am Dienstag, den 10.10.2017, 11:45 +0200 schrieb Mathieu Malaterre:
[...]
I don't think there is much to gain from it. Whenever there is a
change
> > in the major version of gcc/g++ many bugs show up and all involved
> > really do a great job fixing these. IMHO switching from an ol
Am Dienstag, den 10.10.2017, 08:45 +0200 schrieb Mathieu Malaterre:
[...]
With this mind I'd like to make mandatory the -std=c++XY flags when
> compiling either a c++ library or a stand-alone c++ program:
>
> 1. Either upstream define the explicit -std=c++XY flags by mean of
> its build system,
>
Am Dienstag, den 15.11.2016, 18:06 +0200 schrieb Adrian Bunk:
>
> > Unfortunately, in current unstable with thread sanitizer one might
> > get #796246 (at least I had this).
>
> Does "-fsanitize=thread -no-pie" work for you?
Indeed, that fixed the problem with g++-6.2 (g++-5.4 doesn't has this
p
Am Sonntag, den 06.11.2016, 01:12 -0200 schrieb Henrique de Moraes
Holschuh:
>
>
>
> Unfortunately, when hardware lock elision support was added to glibc
> upstream, libpthreads was *not* changed to properly assert() this
> forbidden condition on the non-hardware-elision codepaths. Such an
> as
You could enforce that no Qt-using package uses the wrong OpenSSL by
> adding libssl1.0-dev dependencies to libqt4-dev and qtbase5-dev.
>
> After that, trying to compile any Qt-using package with the wrong
> OpenSSL should fail due to unsatisfiable build dependencies.
>
>
Well, if a library A uses
Am Freitag, den 28.10.2016, 22:55 +0900 schrieb Osamu Aoki:
>
> Please consider building HTML only when you face such a problem and
> wish to get the package released. Your case seems to be LaTeX
> related.
I might add that the 'dot' related problems can not be worked around
like this, but you c
Am Mittwoch, den 29.06.2016, 22:38 +0200 schrieb Pau Garcia i Quiles:
> If possible, I would rather have both 1.0.2 and 1.1.0 in the archive,
> and move to 1.1.0 as upstream moves. I do not feel comfortable at all
> touching security-related stuff, it's not my specialty. Even less if
> we are talki
Am Montag, den 27.06.2016, 19:51 + schrieb Sune Vuorela:
> On 2016-06-27, Gert Wollny wrote:
> >
> > Hello,
> >
> >
> > >
> > > = Qt 4
> > >
> > > Qt 4 is dead upstream, so we have two choices:
> > >
> > >
Hello,
> = Qt 4
>
> Qt 4 is dead upstream, so we have two choices:
>
> - Someone to come up with a patch.
I volunteer to look into this. From what I've seen in DCMTK, the
changes are not too intrusive, most of the time it is just replacing
direct access to member variables with access functio
Hi all,
considering that BOOST 1.60 changes the ABI when compiled with -std >=
c++11 versus -std <= c++03 (cf. [1]) , and that g++-6 defaults to
-std=c++14 it would probably be a good idea if a boost >= 1.60 version
compiled with g++6 would be available from experimental when the bug
squashing s
Hello,
Am Mittwoch, den 04.05.2016, 20:34 + schrieb PICCA Frederic-
Emmanuel:
> I am using fglrx-driver for OpenCL on my W5100 and W7100 amd GPUs.
> Do you know if there will be a plan in order to support OpenCL on amd
> for strech ?
That was actually also my thirst thought.
However, regar
Hi,
> * The user assumes all responsibility for insuring that intellectual
> property claims associated with any data set deposited in the PDB
> archive are honored. It should be understood that the PDB data files
> do not contain any information on intellectual property claims with
> the excep
Hi all,
[...]
9. We expect to ship next Debian release (stretch) only with PHP
> 7.0, that means that all packages needs to be made compatible
> with PHP 7.0.
[...]
Mathieu [gdcm upstream] just pointed out to me that Swig does not yet
support PHP 7.0 [1], which means that for the t
Hi all,
I work on a package (gdcm) that contains files from a variety of
sources and as a result the d/copyright file is quite large [1].
Specifically, there are various source files that are all licensed with
a BSD-3-clause license which are worded slightly differently. i.e. in
some cases the
Hello,
On Sat, 2015-09-26 at 10:28 +0200, Ole Streicher wrote:
> Hi all,
>
> I need to package some large (~80MB) data files with a machine
> dependent byte order.
>
> How should I do this?
>
How about creating one package -bigendian and one -lowendian and a
virtual package that depends on one
On Wed, 2015-08-12 at 21:09 +0200, Gert Wollny wrote:
> However, if there is a package that works with face recognition example,
> and in this case this replacement is not usable.
>
After digging a bit through OpenCV, i can now confirm that the Lenna
image is used for face feature re
On Wed, 2015-08-12 at 20:31 +0200, Fabian Greffrath wrote:
> > Any productive suggestion?
>
> siretart has already provided a suitable replacement in the libav
> package:
>
> http://anonscm.debian.org/cgit/pkg
> -multimedia/libav.git/commit/tests/reference.pnm?id=b31a3c6f2670d4def5a
> a8bd3479da9
On Wed, 2015-08-12 at 16:10 +0200, Tobias Frost wrote:
> Depends on the requirement on those test pictures, but the first thing
> that came into my mind is our Debian swirl. Would that do it?
> Or maybe we can just create something based on that?
>
One of the reasons that the Lenna pictures got
Hello Steve,
at least geomview is still in the upload queue [1]. It seems that the
*.changelog file is missing. Maybe your upload didn't finish properly?
Best,
Gert
[1] ftp://ftp.upload.debian.org/pub/UploadQueue/
On Tue, 2015-06-09 at 16:57 -0500, Steve M. Robbins wrote:
> Hi,
>
> It used
On Wed, 2014-10-29 at 17:02 +0100, Jonas Smedegaard wrote:
> doxygen (and a very few others) links against libclang1-3.5
> "where available" according to the changelog, ...
> libllvm3.5 is also used for another few, including mesa.
It's not so much a question whether these packages are compiled
> Last time I asked:
>
> https://lists.debian.org/debian-devel/2013/09/msg00335.html
>
> It was prefered to provide a C++98 ABI compatible library for the time
> being. If you start providing a C++11 ABI library people will not be
> able to mix symbols from your lib and other part of debian syste
42 matches
Mail list logo
