Bug#846325: RFS: netperfmeter/1.6.1-1

Control: noowner -1 Timeout...  Therefore removing the owner tag and no longer indicating that I will sponsor the upload. On Fri, 30 Dec 2016 12:18:56 +0100 Tobias Frost wrote: > ping? >  > 

Bug#851756: RFS: telegram-desktop/1.0.0-2

19.01.2017 00:23, Gianfranco Costamagna пишет: I see tag for 1.0.1 pushed on github [1] This is alpha version. It is not in upstream changelog on [1]. To be noted upstream author does not always publish the tags in time. P.S.: I don't know how to put this remote changelog into the package.

Re: mpgrafic - mpirun test program as root in automatic build

On Thu, Jan 19, 2017 at 7:44 AM, Sean Whitton wrote: > This is temporarily false: #852071 Is there a typo in that bug? I get a 404 -- bye, pabs https://wiki.debian.org/PaulWise

Re: question on binary-or-shlib-defines-rpath

Dear Nico, On Wed, Jan 18, 2017 at 10:39:47PM +, Nico Schlömer wrote: > That's not true later on when the libraries are _installed_, of course. For > this, CMake has the switch CMAKE_SKIP_INSTALL_RPATH [3], which serves exactly > that purpose. For some reason, lintian doesn't seem to be happy

Re: mpgrafic - mpirun test program as root in automatic build

Hello, On Wed, Jan 18, 2017 at 02:25:41PM +0800, Paul Wise wrote: > On Wed, Jan 18, 2017 at 5:13 AM, Boud Roukema wrote: > > > I've looked a bit at buildd.debian.org, but it's not completely > > trivial to decide which is correct - do the buildd builds on the > > debian build machines run

question on binary-or-shlib-defines-rpath

Hi everyone, I'm co-maintaining the Trilinos package [1] in Debian and recently found a bunch of new lintian warnings of the kind binary-or-shlib-defines-rpath [2]. It say in the description of the warning: ``` To fix this problem, look for link lines like: gcc test.o -o test

Bug#851799: RFS: hamlib/3.1.0-1

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "hamlib" * Package name : hamlib Version : 3.1.0-1 Upstream Author : Kamal Mostafa , Colin Tuckley * URL :

Bug#851756: RFS: telegram-desktop/1.0.0-2

Hello >Version : 1.0.0-2~rc2 >https://mentors.debian.net/debian/pool/contrib/t/telegram-desktop/telegram-desktop_1.0.0-2~rc2.dsc I see tag for 1.0.1 pushed on github [1] Isn't it a good release? I didn't look at the code, but instead of an rc, I would prefer a stable 1.0.1 (even

Bug#851756: RFS: telegram-desktop/1.0.0-2

On Wed, Jan 18, 2017 at 10:07:34PM +0300, Коля Гурьев wrote: > > Why is it in contrib? > From what I understand, there are packages with dependencies on non-free > software in contrib section. This program does not work if Telegram server > is stopped for any reason. But this server is

Re: Backporting shibboleth-sp2 2.6.0+dfsg1-4 to jessie: dh-systemd, piuparts and lintian errors

Etienne Dysli-Metref: > On 17/01/17 18:30, Niels Thykier wrote: E: libshibsp7: postinst-must-call-ldconfig usr/lib/x86_64-linux-gnu/libshibsp.so.7.0.0 >> >> This lintian error: >> >> * is aimed at stretch or later, and >> * should be ignored for stable and stable-backports

Bug#851756: RFS: telegram-desktop/1.0.0-2

I already fixed a few things: debian/changelog, the list of build dependencies. My fork on Github is specified temporally in debian/control. I just don't know a more appropriate value for this field at the moment. I've putted the current changes back to [1]. I would appreciate your advice

Bug#851789: RFS: python-h5netcdf/0.3.1-1 [ITP]

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "python-h5netcdf" * Package name: python-h5netcdf   Version : 0.3.1-1   Upstream Author : Stephan Hoyer * URL : https://github.com/shoyer/h5netcdf

Fattura TIM linea Fissa - Gennaio 2017 - scadenza 12/01/2017

<<< text/html: Unrecognized >>>

Bug#851762: RFS: hamlib/3.1.0-1+nmu1 [NMU]

Hi Adrey, On Wed, Jan 18, 2017 at 11:16:16PM +0500, Andrey Rahmatullin wrote: > On Wed, Jan 18, 2017 at 04:57:44PM +0100, Ervin Hegedüs wrote: > > I'm member of the team (as guest: > > https://alioth.debian.org/users/airween-guest/). As I wrote, I > > noticed the team through the list - no

Bug#851762: RFS: hamlib/3.1.0-1+nmu1 [NMU]

On Wed, Jan 18, 2017 at 04:57:44PM +0100, Ervin Hegedüs wrote: > I'm member of the team (as guest: > https://alioth.debian.org/users/airween-guest/). As I wrote, I > noticed the team through the list - no response. In that case this upload should be a team upload and not a NMU. See

Bug#851756: RFS: telegram-desktop/1.0.0-2

Why is it in contrib? -- WBR, wRAR signature.asc Description: PGP signature

Bug#851756: RFS: telegram-desktop/1.0.0-2

Control: owner -1 ! Control: tag -1 moreinfo On Wed, Jan 18, 2017 at 04:46:46PM +0300, Коля Гурьев wrote: > I am looking for a sponsor for my package "telegram-desktop" Hi! I am an heavy user of telegram, and I was looking forward for this package, despite the privacy concerns, etc. >

Bug#851762: RFS: hamlib/3.1.0-1+nmu1 [NMU]

Hi Adrey, On Wed, Jan 18, 2017 at 08:35:50PM +0500, Andrey Rahmatullin wrote: > On Wed, Jan 18, 2017 at 04:29:43PM +0100, Ervin Hegedüs wrote: > > > Why are doing this NMU? > > because lintian indicated that I must give NMU as version to that > > package > I've meant why are you doing this upload

Bug#851762: RFS: hamlib/3.1.0-1+nmu1 [NMU]

On Wed, Jan 18, 2017 at 04:29:43PM +0100, Ervin Hegedüs wrote: > > Why are doing this NMU? > because lintian indicated that I must give NMU as version to that > package I've meant why are you doing this upload of someone else's package. > Okay, thanks for your feedback - what should I do now? As

Bug#851762: RFS: hamlib/3.1.0-1+nmu1 [NMU]

Hi, On Wed, Jan 18, 2017 at 08:15:53PM +0500, Andrey Rahmatullin wrote: > Control: tags -1 + moreinfo > > Why are doing this NMU? because lintian indicated that I must give NMU as version to that package > Does it fix any bugs? yes, till I worked on the package, I've found a bug (a binary

Bug#851762: RFS: hamlib/3.1.0-1+nmu1 [NMU]

Control: tags -1 + moreinfo Why are doing this NMU? Does it fix any bugs? Have you read about the NMU procedure at https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#nmu and followed it? Besides, it even has a wrong version suffix. -- WBR, wRAR signature.asc Description: PGP

Bug#851762: RFS: hamlib/3.1.0-1+nmu1 [NMU]

Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package "hamlib" * Package name : hamlib Version : 3.1.0-1+nmu1 Upstream Author : Kamal Mostafa , Colin Tuckley

Re: mpgrafic - mpirun test program as root in automatic build

Paul Wise writes: > On Wed, Jan 18, 2017 at 3:58 PM, Ole Streicher wrote: > >> Also when using cowbuilder? At least I see the whole build done by root >> when running in my cowbuilder chroot. That was the point that lead to >> the trouble here... > > Yep. I tested this with id

Re: Backporting shibboleth-sp2 2.6.0+dfsg1-4 to jessie: dh-systemd, piuparts and lintian errors

On 17/01/17 18:30, Niels Thykier wrote: >>> E: libshibsp7: postinst-must-call-ldconfig >>> usr/lib/x86_64-linux-gnu/libshibsp.so.7.0.0 > > This lintian error: > > * is aimed at stretch or later, and > * should be ignored for stable and stable-backports After having overridden this lintian

Bug#851756: RFS: telegram-desktop/1.0.0-2

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "telegram-desktop" * Package name: telegram-desktop Version : 1.0.0-2~rc2 Upstream Author : John Preston * URL :

Re: mpgrafic - mpirun test program as root in automatic build

On Wed, Jan 18, 2017 at 3:58 PM, Ole Streicher wrote: > Also when using cowbuilder? At least I see the whole build done by root > when running in my cowbuilder chroot. That was the point that lead to > the trouble here... Yep. I tested this with id and override_dh_auto_* in cowbuilder:

Bug#851696: marked as done (RFS: python-qtpy/1.2.0-1)

Your message dated Wed, 18 Jan 2017 10:18:08 + with message-id <1484734688.18572.27.ca...@gmail.com> and subject line Re: Bug#851696: RFS: python-qtpy/1.2.0-1 has caused the Debian Bug report #851696, regarding RFS: python-qtpy/1.2.0-1 to be marked as done. This means that you claim that the

Bug#851606: RFS: rmlint/2.4.6-1 [ITP]

Hi Carlos, Carlos Maddela wrote: >rmlint (2.4.6-1) unstable; urgency=medium > > * Initial upload to Debian. Thanks to Axel Beckert for getting >it all started. (Closes: #845155) > > -- Carlos Maddela Tue, 17 Jan 2017 04:45:28 +1100 Thanks a lot for

Re: Backporting shibboleth-sp2 2.6.0+dfsg1-4 to jessie: dh-systemd, piuparts and lintian errors

On 17/01/17 18:30, Niels Thykier wrote: >>> E: libshibsp7: postinst-must-call-ldconfig >>> usr/lib/x86_64-linux-gnu/libshibsp.so.7.0.0 > > This lintian error: > > * is aimed at stretch or later, and > * should be ignored for stable and stable-backports Thanks Niels! :) That's a bit strange

Re: mpgrafic - mpirun test program as root in automatic build

Paul Wise writes: > On Wed, Jan 18, 2017 at 3:37 PM, Boud Roukema wrote: > >> I guess by "both of these" you mean "most of the build steps (apart from >> the 'debian/rules install' step)"? > > What I wrote wasn't clear and wasn't strictly true, sorry! > > When manually building

Re: mpgrafic - mpirun test program as root in automatic build

On Wed, 18 Jan 2017, Paul Wise wrote: When manually building from source: You always build/test as a normal user. You install as either root or normal user, depending on the install prefix. When doing Debian package builds: You always build/test as a normal user. You always install using