Your message dated Sat, 08 Dec 2018 04:27:43 +
with message-id
and subject line closing RFS: mint-y-icons/1.3.0-1 [ITP]
has caused the Debian Bug report #904745,
regarding RFS: mint-y-icons/1.3.0-1 [ITP]
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On 2018-12-07 17:06 -0800, John Horigan wrote:
> On Fri, Dec 7, 2018 at 8:36 AM Wookey wrote:
> On 2018-12-07 08:27 -0800, John Horigan wrote:
> Normally the library package
> libfoo is shared, and the libfoo-dev package contains the static
> version. You already have the static
On Fri, Dec 7, 2018 at 8:50 AM Andrey Rahmatullin wrote:
> On Fri, Dec 07, 2018 at 08:27:24AM -0800, John Horigan wrote:
> > I maintain a static library package, libagg-dev. There is an outstanding
> > request for a shared library of libagg.
> Is building the shared lib supported by the
On Fri, Dec 7, 2018 at 8:36 AM Wookey wrote:
> On 2018-12-07 08:27 -0800, John Horigan wrote:
> > I maintain a static library package, libagg-dev. There is an outstanding
> > request for a shared library of libagg. I'm leaving the original
> libagg-dev
> > binary package as it is, with just the
Hi nicoo,
Thank you for looking at my package! I appreciate any feedback.
On Freitag, 07 Dezember 2018, 13:08 +0100, Nicolas Braud-Santoni wrote:
> I created salsa.d.o/Debian/pyxs and granted access to @benjamin-guest.
> Can you confirm this is you? :)
Thank you! It is I and I have pushed
Hi Herbert,
many thanks for your advice.
I followed the instructions in uscan - imported the upstream
maintainers public key and then exported the minimal signing key.
I've rebuilt the package, confirmed that uscan downloads with the
minimal signing key and then built on buster.
Running
On Fri, Dec 07, 2018 at 08:27:24AM -0800, John Horigan wrote:
> I maintain a static library package, libagg-dev. There is an outstanding
> request for a shared library of libagg.
Is building the shared lib supported by the upstream?
> libagg2-dev has the .so file with the name libagg.so and
On 2018-12-07 08:27 -0800, John Horigan wrote:
> I maintain a static library package, libagg-dev. There is an outstanding
> request for a shared library of libagg. I'm leaving the original libagg-dev
> binary package as it is, with just the static libraries. I'm adding binary
> packages
I maintain a static library package, libagg-dev. There is an outstanding
request for a shared library of libagg. I'm leaving the original libagg-dev
binary package as it is, with just the static libraries. I'm adding binary
packages libagg2-dev and libagg2. libagg2-dev has everything that
Hi,
Switched to quilt, but I don't understand why mentor lintian says "No
compatibility level set!"
Thanks
Hi Adam and Marcos,
thank you for your input. I will upload a package with re-integrated
sysvinit support soon.
@Marcos: I wonder why Lintian on mentors.debian.net complains about
several issues while the lintian check included in debuild stays calm.
Any clue about this?
Cheers,
Sven
Yes. You'll need to do that.
Scott K
On Friday, December 07, 2018 10:25:40 AM Brent Clark wrote:
> Good day Scott and Paul
>
> Thanks so much for looking at my RFS.
>
> Sorry for not communicating that in the changelog.
> Do you guys want that in the changelog?
>
> Regards
> Brent
>
> On
On Fri, Dec 07, 2018 at 11:35:52AM +0100, Jose G. López wrote:
> Dear mentors,
>
> Is it permitted by the Debian Policy to have a personalized makefile inside
> debian
> directory and call it from rules file? Or I should patch the upstream's
> makefile completly?
There's also a third way: as
Control: tag -1 + pending
Control: owner -1 !
Hi Benjamin,
On Tue, Nov 27, 2018 at 08:49:53PM +0100, Benjamin Hof wrote:
> I am looking for a sponsor for my package "python-pyxs"
I will review your package later today.
> The Vcs-Browser and Vcs-Git fields point to salsa.debian.org/debian,
>
On Fri, Dec 07, 2018 at 11:59:16AM +0100, Jose G. López wrote:
> Well my problem is that upstream's software is intended to build just
> an executable and I'm building a shared library.
This is even more important problem. Are you sure you can do it properly?
--
WBR, wRAR
signature.asc
On 07/12/2018 08:10, foss.freedom wrote:
It has been about a month since the initial package was uploaded to
mentors. Still hoping for some feedback please.
Yesterday I've tweaked the package to remove an unnecessary
build-dependency after discussing with upstream.
I note one new
On Fri, 7 Dec 2018 10:43:26 +
Mo Zhou wrote:
> Hi Jose,
>
> If you think writting a new makefile is better than patching the
> upstream build system, please go ahead. However, having to write a
> makefiles by oneself often signifies problematic upstream.
>
> On Fri, 7 Dec 2018 15:40:17
Hi Jose,
If you think writting a new makefile is better than patching the
upstream build system, please go ahead. However, having to write a
makefiles by oneself often signifies problematic upstream.
On Fri, Dec 07, 2018 at 11:35:52AM +0100, Jose G. López wrote:
> Dear mentors,
>
> Is it
On Fri, Dec 07, 2018 at 11:35:52AM +0100, Jose G. López wrote:
> Dear mentors,
>
> Is it permitted by the Debian Policy to have a personalized makefile inside
> debian
> directory and call it from rules file? Or I should patch the upstream's
> makefile completly?
>
> I'm packaging fathom[0][1]
Dear mentors,
Is it permitted by the Debian Policy to have a personalized makefile inside
debian
directory and call it from rules file? Or I should patch the upstream's
makefile completly?
I'm packaging fathom[0][1] and can't find an answer.
Thanks and sorry if the answer is obvious.
Regards,
Control: forcemerge 907212 911726
On Tue, Oct 23, 2018 at 05:01:31PM -0700, Felix Lechner wrote:
> Package: sponsorship-requests
> Severity: normal
> X-Debbugs-CC: debian...@lists.debian.org
>
> Dear mentors,
>
> I am looking for a sponsor for my package "golang-github-xanzy-go-gitlab".
It has been about a month since the initial package was uploaded to
mentors. Still hoping for some feedback please.
Yesterday I've tweaked the package to remove an unnecessary
build-dependency after discussing with upstream.
I note one new "Information" lintian issue now occurs since the
Good day Scott and Paul
Thanks so much for looking at my RFS.
Sorry for not communicating that in the changelog.
Do you guys want that in the changelog?
Regards
Brent
On 2018/12/07 09:18, Paul Wise wrote:
On Fri, Dec 7, 2018 at 3:12 PM Scott Kitterman wrote:
This package currently has Paul
23 matches
Mail list logo
