On 8/13/24 04:34, Daniel Gröber wrote:
On Mon, Aug 12, 2024 at 11:37:24PM +1000, Dmitry Smirnov wrote:
IMHO GBP approach is counter-productive, with needlessly complicated
workflow, redundant upstream branch(es) and incredibly inconvenient merge
of debian packaging and upstream files in "mas
progress_indicator = 2
allowed_distributions = .*
On Friday, June 14, 2024 4:27:27 PM MST Matthew Fernandez wrote:
On 6/15/24 09:26, Matthew Fernandez wrote:
Hello mentors,
I am getting the following behaviour when trying to upload to mentors:
$ dput mentors ../rumur_2024.05.07-1_source.changes
On 6/15/24 09:26, Matthew Fernandez wrote:
Hello mentors,
I am getting the following behaviour when trying to upload to mentors:
$ dput mentors ../rumur_2024.05.07-1_source.changes
Checking signature on .changes
gpg: ../rumur_2024.05.07-1_source.changes: Valid signature from
Hello mentors,
I am getting the following behaviour when trying to upload to mentors:
$ dput mentors ../rumur_2024.05.07-1_source.changes
Checking signature on .changes
gpg: ../rumur_2024.05.07-1_source.changes: Valid signature from
A44D25C91888A6A4
Checking signature on .dsc
gpg: ..
A gentle bump to see if anyone might have time to sponsor this one?
On 5/19/24 14:58, Matthew Fernandez wrote:
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur":
* Package name : rumur
Version : 20
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur":
* Package name : rumur
Version : 2024.05.07-1
Upstream contact : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
Just a gentle bump to see if anyone has time to take a look at this RFS?
On 12/10/23 12:17, Matthew Fernandez wrote:
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur":
* Package name : rumur
Version : 2023.11.27-1
Upstre
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur":
* Package name : rumur
Version : 2023.11.27-1
Upstream contact : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License : Unlicense
* Vcs : https://github.
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "rumur":
* Package name : rumur
Version : 2023.05.21-1
Upstream contact : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License : Unlicense
* Vcs : https://github.
On 9/14/22 07:32, Bo YU wrote:
Hi,
On Wed, Sep 14, 2022 at 09:45:45AM -0400, Aaron Boxer wrote:
Hello,
I currently have failed builds on mipsel and armel archs.
For these systems, it appears that I need to link explicitly
to libatomic. I've added the link flag, but the failures persist.
Any s
On 8/21/22 00:32, Tobias Frost wrote:
Package: sponsorship-requests
Followup-For: Bug #1017815
Hi Matthew,
thanks for the updated package fixing an RC bug!
Thanks for sponsoring!
I have is some feedback regarding it:
- The format of d/changelog is a bit unusual, usually there are no
blank
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "rumur":
* Package name : rumur
Version : 2022.08.20-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License : Unlicense
* Vcs : https://github.
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "rumur":
* Package name: rumur
Version : 2022.03.05-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "rumur":
* Package name: rumur
Version : 2021.12.27-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
> On Nov 3, 2021, at 19:30, Seunghun Han wrote:
>
>> I am also not sure if you are allowed to write in /tmp on package building.
>> I will check that.
> Everyone has write access right to /tmp directory, so I guess the
> package also has it.
I don’t think this is the cause of the failures, bu
Hello mentors,
I was reviewing one of my own packages on the QA page¹ and was surprised to
notice it gets full marks for CI/Rep. “Surprised? Isn’t that a good thing?” you
say. It’s surprising because I’ve been tracking an upstream bug that I *know*
makes this package’s build not-reproducible. C
> On Oct 5, 2021, at 03:27, Tobias Frost wrote:
>
> On Tue, Oct 05, 2021 at 06:35:34PM +0900, notebook wrote:
>>
[Me]
It looks like becoming a maintainer requires 40+ hours to go through all
the "must read" articles and becoming accustomed to every procedure and
guideline.
> On Oct 2, 2021, at 16:37, Adam Borowski wrote:
>
> On Sat, Oct 02, 2021 at 11:26:19AM -0700, Matthew Fernandez wrote:
>> * Package name: rumur
>> Version : 2021.09.29-1
>
>> rumur (2021.09.29-1) unstable; urgency=medium
>
>
> E: rumur
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur":
* Package name: rumur
Version : 2021.09.29-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur":
* Package name: rumur
Version : 2021.08.28-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
> On Mar 25, 2021, at 22:12, Adam Borowski wrote:
>
> On Wed, Mar 24, 2021 at 01:36:10PM +0100, Gürkan Myczko wrote:
>>> The menu icon for .desktop doesn't show up for me (in XFCE).
>>
>> probably because it's .gif and fd.o doesn't support it
>
> And, according to the spec:
> https://specific
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur":
* Package name: rumur
Version : 2020.12.20-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
> On Dec 2, 2020, at 10:41, Andrey Rahmatullin wrote:
>
> As I've already told you yesterday on IRC, the test succeeds with -O2,
> which is set when building the package.
Furthermore you can actually see a variant of the problem with this test code
even on non-MIPS:
$ uname -m
x86_64
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "rumur":
* Package name: rumur
Version : 2020.09.06-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur":
* Package name: rumur
Version : 2020.07.28-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
> On Jul 8, 2020, at 19:34, Paul Wise wrote:
>
> On Wed, 2020-07-08 at 20:09 +0300, Boian Bonev wrote:
>
>> That is perfectly safe - all recent (last 20 years) glibc versions
>> allow passing NULL for %s and print (null)... Anyways it is better to
>> check it explicitly and spare some time for
Re-sending to check if anyone is willing to sponsor this one? It’s a pretty
straightforward update to the package, so hopefully should not be
controversial. Any help would be greatly appreciated.
> On Jun 21, 2020, at 12:02, Matthew Fernandez
> wrote:
>
> Package: sponsors
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur"
* Package name: rumur
Version : 2020.06.20-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
> On May 31, 2020, at 07:54, Vasyl Gello wrote:
>
> Dear Mattia and Matthew!
>
> First of all I would like to thank you for all the efforts you did to teach
> me how to do proper Debian packaging.
> Your reviews made me rethink some practices I followed and it already helps
> me in my activit
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur"
* Package name: rumur
Version : 2020.05.27-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
> 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 *
> 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 May 26, 2020, at 15:10, Mattia Rizzolo wrote:
>
> * building the package shows this "scary" GCC warning:
> |In file included from /usr/include/string.h:495,
> | from cryptopass.c:19:
> |In function 'strncpy',
> |inlined from 'main' at cryptopass.c:200:9:
> |/usr/includ
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur"
* Package name: rumur
Version : 2020.05.18-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
> One small issue... Valgrind recommends -O0 or -O1
TIL :) Thanks, Jeff!
> You can sometimes locate a bus error at build time with -Wcast-align.
> At runtime you can usually locate them with -fsanitize=undefined.
I had previously tried UBSan and, while it turned up a number of shifting and
stri
> On Apr 30, 2020, at 00:31, Andreas Tille wrote:
>
> On Wed, Apr 29, 2020 at 05:51:26PM -0700, Matthew Fernandez wrote:
>
>> The other option I suggested was Valgrind, but if you can’t run apt-file you
>> probably can’t install Valgrind either.
>
> Well, I
> On Apr 29, 2020, at 09:04, Andreas Tille wrote:
>
> On Wed, Apr 29, 2020 at 07:14:30AM -0700, Matthew Fernandez wrote:
>
>> For those on this thread who have access to mipsel hardware or can shell in
>> to one of the mipsel build machines, I would suggest running
> On Apr 29, 2020, at 02:12, Andreas Tille wrote:
>
> Hi,
>
> On Wed, Apr 29, 2020 at 10:30:35AM +0800, 黄佳文 wrote:
>> I am a developer from Loongson company (R & D CPU/mip64el), I've been
>> looking at this recently.
>
> Very nice to see mips developers to care for biological software. :-)
>
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur"
* Package name: rumur
Version : 2020.04.26-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
> On Apr 25, 2020, at 00:10, Rebecca N. Palmer wrote:
>
> Matthew Fernandez wrote (ordering changed):
>> I don’t get the same warning for mipsel and armel because the binary built
>> fine there. It’s just that the test suite didn’t complete.
>
> No: by default, f
Hi Andrey,
Thanks for your reply.
> On Apr 24, 2020, at 08:32, Andrey Rahmatullin wrote:
>
> On Fri, Apr 24, 2020 at 07:29:40AM -0700, Matthew Fernandez wrote:
>> The arm64 failure [2] looks legitimate (though I
>> don’t understand why excuses also says “arch:arm64 not b
Hello mentors,
I recently uploaded a new version of my package that is waiting in unstable
[0], too young to yet migrate into testing. However, IIUC the excuses [1] the
migration block is probably permanent due to regressions on arm64 and mipsel.
The arm64 failure [2] looks legitimate (though I
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur"
* Package name: rumur
Version : 2020.04.05-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
> On Apr 17, 2020, at 22:39, Andreas Tille wrote:
>
> Hi Matthew,
>
> thanks a lot for your detailed investigation.
>
> On Fri, Apr 17, 2020 at 04:28:23PM -0700, Matthew Fernandez wrote:
>>> Program received signal SIGBUS, Bus error.
>>> 0x5556a1b8 in
> On Apr 17, 2020, at 13:18, Andreas Tille wrote:
>
> Hi Matthew,
>
> On Fri, Apr 17, 2020 at 08:18:29AM -0700, Matthew Fernandez wrote:
>>> Thanks for the patch which I applied to packaging Git. I assume you
>>> want to express that while these fixes are de
On Fri, 17 Apr 2020 at 08:09, Andreas Tille wrote:
> Hi Matthew,
>
> On Fri, Apr 17, 2020 at 07:40:54AM -0700, Matthew Fernandez wrote:
> >
> > As a jumping off point, the attached patch fixes some issues with
> logging calls in the upstream 1.2.4 source release.
>
>
> On Apr 17, 2020, at 04:20, Andreas Tille wrote:
>
> Control: tags -1 help
>
> Hi,
>
> as it can be seen on the recent build log of clustalo on mips[1] the
> build fails with
>
>
> # Run additional test from python-biopython package to verify that
> # this will work as well
> src/clustalo -
Hi Andreas,
I can’t reproduce this either, but in case your subject was hinting at a
suspected cause, I don’t think this is it. The output shows CMake successfully
finding Pthreads. The line numbers don’t make much sense to me; there is no
else statement on line 69, and CMakeLists.txt is only 1
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur"
* Package name: rumur
Version : 2020.03.12-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
On Mon, 2 Mar 2020 at 07:38, Adam Borowski wrote:
> On Mon, Mar 02, 2020 at 07:29:54AM -0800, Matthew Fernandez wrote:
> > Adam, did my last comment on #951497 make sense? Just wanted to check
> > you’re not waiting on more information from me.
> >
> > > On F
Adam, did my last comment on #951497 make sense? Just wanted to check you’re
not waiting on more information from me.
> On Feb 18, 2020, at 20:49, Matthew Fernandez
> wrote:
>
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking f
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur"
* Package name: rumur
Version : 2020.01.27-2
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur"
* Package name: rumur
Version : 2020.02.17-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur"
* Package name: rumur
Version : 2020.01.27-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
> On Jan 22, 2020, at 11:56, Andreas Tille wrote:
>
> Control: tags -1 help
>
> I have fixed Python2->Python3 migration as well as the FTBFS with
> pbseqlib 5.3.3+dfsg-1 issue in Git[1]. Unfortunately there is another
> build issue in the C++ code which I have no idea how to fix:
>
>
> ...
>
> On Jan 15, 2020, at 10:33, Adam Borowski wrote:
>
> On Tue, Jan 14, 2020 at 08:07:05PM -0800, Matthew Fernandez wrote:
>> OK, uploaded a new version with this fix. Please let me know if you have a
>> chance to take another look.
>
> Alas, still fails:
>
On Thu, 16 Jan 2020 at 10:53, Hilmar Preuße wrote:
> Am 16.01.2020 um 17:24 teilte Matthew Fernandez mit:
>
> Hi,
>
> > This error appears to be from the BDW garbage collector [0]. Are you
> > sure it works on Linux on Alpha? The docs refer to a missing file,
> > RE
This error appears to be from the BDW garbage collector [0]. Are you sure it
works on Linux on Alpha? The docs refer to a missing file, README.alpha, and
the source has exciting comments like “untested but hopefully should work on
Linux/Alpha.” What’s going on here might be an mmap or sbrk failu
> On Jan 14, 2020, at 08:00, Matthew Fernandez
> wrote:
>
>>
>> On Jan 13, 2020, at 19:44, Adam Borowski wrote:
>>
>> On Mon, Jan 13, 2020 at 06:24:32PM -0800, Matthew Fernandez wrote:
>>>>> * Package name: rumur
>>>>> V
> On Jan 13, 2020, at 19:44, Adam Borowski wrote:
>
> On Mon, Jan 13, 2020 at 06:24:32PM -0800, Matthew Fernandez wrote:
>>>> * Package name: rumur
>>>> Version : 2020.01.11-1
>
>> OK I think I’ve corrected this now. Adam (or any oth
Thanks for being clear, Andrei. And thanks for your work building and
maintaining this package.
I jumped into this thread knowing nothing about this package but merely
recognizing a compiler error. Now that I look up what it does, I don’t have the
necessary background to fully understand its fu
> On Jan 12, 2020, at 17:14, Matthew Fernandez
> wrote:
>
>
>
> On Sun, 12 Jan 2020 at 16:56, Adam Borowski <mailto:kilob...@angband.pl>> wrote:
> On Sun, Jan 12, 2020 at 02:13:18PM -0800, Matthew Fernandez wrote:
> > * Package name: rumur
&
Sorry, I didn’t have much context for the original issue and was probably too
terse in my responses. Some more elaboration inline below.
> On Jan 13, 2020, at 01:14, Andreas Tille wrote:
>
> On Sun, Jan 12, 2020 at 02:08:56PM -0800, Matthew Fernandez wrote:
>>
>>> O
On Sun, 12 Jan 2020 at 16:56, Adam Borowski wrote:
> On Sun, Jan 12, 2020 at 02:13:18PM -0800, Matthew Fernandez wrote:
> > * Package name: rumur
> >Version : 2020.01.11-1
>
> > Changes since the last upload:
> >
> >* New upstream releas
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur"
* Package name: rumur
Version : 2020.01.11-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License :
> On Jan 12, 2020, at 12:49, Andreas Tille wrote:
>
> Hi,
>
> I'm wondering how this bug
>
>
> rk1968/rk1968.cc: In lambda function:
> rk1968/rk1968.cc:237:103: error: expected '{' before '->' token
> 237 | auto make_error_return = [&L] ( const char* fmt, ...)
> __attribute__ ((for
Hello mentors,
While slowly improving my first Debian package [0] I’m trying to understand the
debian/control Vcs-Git field. IIUC the docs [1] tell me to point it at the
branch used for packaging, in my case ‘packaging/debian’. I realised vcswatch
uses this to decide when to prompt you for a ne
> On Dec 10, 2019, at 17:44, Adam Borowski wrote:
>
> On Tue, Dec 10, 2019 at 08:30:44PM -0500, Dan Davison wrote:
>> On Sun, 8 Dec 2019 at 22:31, Paul Wise wrote:
>>> On Sat, Dec 7, 2019 at 9:36 PM Dan Davison wrote:
>>>
Currently (FreeBSD, Rust Cargo, Arch Linux, Homebrew) the package
> On Oct 31, 2019, at 00:36, Sven Joachim wrote:
>
> On 2019-10-30 22:27 -0700, Matthew Fernandez wrote:
>
>> I should remove debian/rumur.manpages, right?
>
> I don't think that is a particularly good idea. At least you want to
> keep ast-dump/doc/rumur-ast
On Wed, 30 Oct 2019 at 19:40, Matthew Fernandez
wrote:
> Hello mentors,
>
> Thanks to the hard work of Debian volunteers, I recently had a package
> sponsored and uploaded [0]. Not being confident in my ability to remember
> the packaging steps, I scripted my understanding of be
Hello mentors,
Thanks to the hard work of Debian volunteers, I recently had a package
sponsored and uploaded [0]. Not being confident in my ability to remember the
packaging steps, I scripted my understanding of best practice for next time
[1]. I later successfully ran this to generate a source
> On Oct 7, 2019, at 01:25, Thomas Dettbarn wrote:
>
> Hello!
>
> Currently, I am trying to get my package dMagnetic into
> Debian's repository. You can find it at
>
> https://mentors.debian.net/package/dmagnetic
>
> Despite my best effords, there are still a handful of lintian warnings le
> On Sep 14, 2019, at 14:35, Abou Al Montacir wrote:
>
> On Sat, 2019-09-14 at 12:58 +0200, Geert Stappers wrote:
>> On Sat, Sep 14, 2019 at 10:55:11AM +0200, Abou Al Montacir wrote:
>>> Actually I'm very surprised that a user space program (compiler) running on
>>> an
>>> unprevileged account
> On Aug 27, 2019, at 08:48, Fabian Wolff wrote:
>
> On 8/27/19 4:00 PM, Matthew Fernandez wrote:
>>> z3 (4.8.4-0.1) unstable; urgency=medium
>>
>> I am not a z3 dev, but the latest z3 release is 4.8.5. Is there a
>> particular motivation for uploading a
> On Aug 27, 2019, at 06:27, Fabian Wolff wrote:
>
> Package: sponsorship-requests
> Severity: normal
> X-Debbugs-CC: m...@debian.org
> X-Debbugs-CC: locutusofb...@debian.org
>
> Dear mentors,
>
> I am looking for a sponsor for a non-maintainer upload of the z3 package.
>
> The z3 package is
Hello mentors,
I received several notifications like the following recently, which seem to be
a rejection of an RFS I filed. The package it’s referring to was uploaded by
Jonathan Carter and I see it currently in the New Queue [0] with Jonathan as
the sponsor. My understanding was that I needed
> On Apr 5, 2019, at 19:08, Mo Zhou wrote:
>
> Hi mentors,
>
> This question tightly associates with my ongoing work for Debian's
> BLAS/LAPACK packages, specifically the 32-bit and 64-bit variants.
> I encountered a problem that I don't fully understand so I think I
> need some help at this p
faster and uses less memory on large input problems.
Any and all feedback welcome. Thank you for your time.
Matthew
> On Jan 18, 2019, at 18:43, Matthew Fernandez
> wrote:
>
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sp
> On Jan 19, 2019, at 17:29, Adam Borowski wrote:
>
> On Fri, Jan 18, 2019 at 06:43:13PM -0800, Matthew Fernandez wrote:
>> * Package name: rumur
>> Version : 2019.01.12-1
>
>> dget -x
>> https://mentors.debian.net/debian/pool/main/r/rumur/
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rumur"
* Package name: rumur
Version : 2019.01.12-1
Upstream Author : Matthew Fernandez
* URL : https://github.com/Smattr/rumur
* License : The
> On Dec 25, 2018, at 02:41, Geert Stappers wrote:
>
> On Mon, Dec 24, 2018 at 06:09:04PM -0800, Matthew Fernandez wrote:
>> Hello Debian Mentors,
>>
>> I???m preparing to request a piece of software I maintain be made
>> available on Debian and have been do
Hello Debian Mentors,
I’m preparing to request a piece of software I maintain be made available on
Debian and have been doing my homework trying to package it correctly. It’s a
C++ binary, but comes with a Python wrapper for invoking it [0]. This script
should run with either Python 2 or Python
82 matches
Mail list logo
