Thank you for kindly support.
* change
Debian helper compact and Standard.
Change URL to salsa Debian.
Debian/Rules update
Debian/watch update
https://mentors.debian.net/package/ibus-keymagic
On Wed, May 27, 2020, 11:37 PM Kyle Robbertze
wrote:
> Hi,
>
> This is no longer on mentors, can yo
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "xtrkcad"
Package name: xtrkcad
Version : 1:5.1.2a-1
Upstream Author : XTrkCAD Developers
URL : http://xtrkcad.org/
License : GPL-2+
Vcs
Hi,
This is no longer on mentors, can you please re-upload?
Cheers
Kyle
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Kyle Robbertze
⢿⡄⠘⠷⠚⠋⠀ Debian Developer
⠈⠳⣄ https://wiki.debian.org/KyleRobbertze
> On May 27, 2020, at 08:15, Vasyl Gello wrote:
>
> Hi Matthew!
>
> Thanks for the continued review! You read my mind now?)
>
> >
> >Now that I read the remainder of the main source file, I spotted a
> >completely separate issue, src/cryptopass.c:375-384 [1]:
> >
> > /* Clean up everything *
Hi Matthew!
Thanks for the continued review! You read my mind now?)
>
>Now that I read the remainder of the main source file, I spotted a completely
>separate issue, src/cryptopass.c:375-384 [1]:
>
>/* Clean up everything */
>
>for (counter = 0; counter < 10; counter++) {
> memset(d
> On May 26, 2020, at 23:46, Vasyl Gello wrote:
>
> Hi Matthew!
>
>> I would suggest adding one as well as fuzzing this code before exposing the
>> downstream public to it.
>
> Will fix the issues and add testsuite && fuzzcorp ASAP.
>
> BTW I fixed all the stuff GCC 8.3.0 reported me with FO
On Wed, 27 May 2020, 1:12 pm Vasyl Gello, wrote:
> Hi Wookey!
>
> >OK, but you have to build new packages in a sid chroot too to check
> >they work, as that's the suite they get uploaded to. It's fine to
> >package in such a way that the package also builds in buster, but the
> >primary target of
Hi Wookey!
>OK, but you have to build new packages in a sid chroot too to check
>they work, as that's the suite they get uploaded to. It's fine to
>package in such a way that the package also builds in buster, but the
>primary target of a new package in debian is always sid (unstable).
So I can t
On 2020-05-27 09:26 +, Vasyl Gello wrote:
> >You should be building your packages in a chroot (possibly using wrapper
> >tools such as pbuilder or sbuild) to, as from what you said you aren't
> >building them in sid.
>
> I am building in chroot but targeting buster as primary target of this c
Hi Mattia!
>I just used the current default in Debian sid, which is GCC 9.
>
>You should be building your packages in a chroot (possibly using wrapper
>tools such as pbuilder or sbuild) to, as from what you said you aren't
>building them in sid.
I am building in chroot but targeting buster as pri
On Wed, May 27, 2020 at 06:46:42AM +, Vasyl Gello wrote:
> BTW I fixed all the stuff GCC 8.3.0 reported me with FORTIFY_SOURCE=2 before
> pushing code to GitHub.
> Did you use GCC 10?
I just used the current default in Debian sid, which is GCC 9.
You should be building your packages in a chr
11 matches
Mail list logo
