Your message dated Sat, 8 Apr 2017 22:34:52 +0200
with message-id <20170408203451.srpftycl3k2t6...@mapreri.org>
and subject line Re: Bug#859238: RFS: microsoft-gsl/0.1~2017.03.20~git16a6a41-1
has caused the Debian Bug report #859238,
regarding RFS: microsoft-gsl/0.1~2017.03.20~git16a6a41-1 [ITP]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
859238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "microsoft-gsl"
Package name : microsoft-gsl
Version : 0.1~2017.03.20~git16a6a41-1
URL : https://github.com/Microsoft/GSL
License : MIT (Expat)
Section : libdevel
It builds those binary packages:
libmicrosoft-gsl-dev - Microsoft Guidelines Support Library
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/microsoft-gsl
Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/m/microsoft-gsl/microsoft-gsl_0.1~2017.03.20~git16a6a41-1.dsc
More information about hello can be obtained from https://www.example.com.
This package is required for build new version of telegram-desktop
Regards,
Nicholas Guriev
--- End Message ---
--- Begin Message ---
On Sat, Apr 08, 2017 at 11:15:43PM +0300, Коля Гурьев wrote:
> 08.04.2017 18:07, Mattia Rizzolo пишет:
> > Nice, would you also please push upstream and prisitine-tar branches?
> > (you may name upstream and debian branches as you see fit, just be sure
> > HEAD points to the packaging branch and debian/gbp.conf reflects the
> > reality if it's not the default)
>
> Done.
Thank you, uploaded!
I'll have a look at telegram-desktop soon too (I'd prefer to wait until
this one is accepted though).
Could you please add a debian/ tag?
> > Look better, debhelper >= 10 is available in xenial, yakkety and zesty.
> > Besides, in theory you are supposed to test your packages in Debian too
> > :P
> >
> > Also, it shouldn't matter much, as you should be building your packages
> > in the current development version, using a chroot (see tools like
> > pbuilder or sbuild).
>
> Oh, I was a fool, I didn't note that this version is available in
> xenial-updates repository.
it's in xenial-backports, not -updates, and -backports is not enabled by
default in chroots installation (it is in the regular desktop install
though).
Same for -updates.
> I used xenial in chroot jail for ensure that all
> dependencies are specified correctly. But pbuilder or sbuild seem so
> complicated for me.
Well, you should probably use a unstable chroot instead.
Anyhow, trust me that once you get the hold on pbuilder (which in my not
so humble opionion (well, I maintain it :P) is a lot easier than sbuild)
you'll find your work is quite easier than going manually through
chroot; both pbuilder and sbuild as just an overlay to chroot(2) (sbuild
also going through schroot).
:D
> > > It seems the upstream doesn't need this patch because they use a last
> > > version of UnitTeset++ framework where the header has capital letters.
> >
> > | + In libunittest++ debian package others paths are.
> >
> > The grammar of this sentence is off :)
> > I suggest "In the libunittest++ debian package the paths are different".
> > But is it really just a debian thing? :O Or upstream changed something?
>
> Sorry, English isn't my native language (you already know it) :-(
> As for libunittest++,
Don't worry, it's fine :)
(Besides, I am no native speaker either, and doing free software work
helped considerably in improving it)
> I think it relates to old version of this package in
> Debian archive, v1.4. A new version v2.0 is available, but it looks that
> everything works okay.
This would be https://bugs.debian.org/784665 I have no idea why
Gianfranco didn't go ahead and hijacked^Wadopted it, I've asked him
(privately) if he is still interested.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
--- End Message ---
