Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "budgie-desktop"
* Package name: budgie-desktop
Version : 10.2.9-3
Upstream Author : i...@solus-project.com
* URL : https://github.com/budgie-desktop/budgie-
Andreas Moog writes:
> Your sbuild-environment has outdated mirror information. For example
> the current libreadline version in unstable is 7.0-3. Does the build
> work after running sbuild-update?
The ‘sbuild’ process updates from the mirrors when it begins:
+
Andreas Moog writes:
> Your sbuild-environment has outdated mirror information. For example
> the current libreadline version in unstable is 7.0-3. Does the build
> work after running sbuild-update?
The build dependency chain also leads to ‘libreadline’, which *is*
fetched at version “7.0-3”. Bu
Hi Ben,
sbuild maintainer here. In these cases you can always file a bug but lets see
if we can solve this here.
Quoting Ben Finney (2017-07-01 13:08:17)
> Andreas Moog writes:
>
> > Your sbuild-environment has outdated mirror information. For example
> > the current libreadline version in unst
control: owner -1 !
control: tags -1 moreinfo
> I am looking for a sponsor for my package "budgie-desktop"
here we are
>the target is for stretch to fix the bug #866730 marked as Important
>Tested that this builds via pbuilder-dist
this is nonsense.
You need to target unstable, and let the fix
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "i8kutils":
* Package name: i8kutils
Version : 1.43
Upstream Author : Vitor Augusto
* URL : https://launchpad.net/i8kutils
* License : GNU GPL
tags 866736 - moreinfo
Hi Gianfranco,
okey dokey,
first time trying to fix something in stable :) sounds like a bit
different from launchpads SRU process.
I've uploaded a new version with a target of unstable.
Sorry - I didnt really understand about filing a bug against
release.debian.org t
Your message dated Sat, 1 Jul 2017 16:13:28 + (UTC)
with message-id <1101826259.4461560.1498925608...@mail.yahoo.com>
and subject line Re: Bug#866736: RFS: budgie-desktop/10.2.9-3
has caused the Debian Bug report #866736,
regarding RFS: budgie-desktop/10.2.9-3
to be marked as done.
This means
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "weresync"
* Package name: weresync
Version : 1.0-1
Upstream Author : Daniel Manila
* URL : https://github.com/DonyorM/weresync
* License : Apache
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-devel-ga...@lists.debian.org
Dear mentors,
I am looking for a sponsor for my package "gigalomania":
* Package name: gigalomania
Version : 0.28+git.20170219.g08f4811-1
Upstream Author : Mark Harman
* URL
On 07/01/2017 05:27 PM, foss.freedom wrote:
> Sorry - I didnt really understand about filing a bug against
> release.debian.org targeting "p-u" - I had a look here but didnt see
> an example https://www.debian.org/Bugs/Reporting
There is a bit more background information in the Developers Referenc
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "node-jsonfile"
* Package name: node-jsonfile
Version : 3.0.0-1
Upstream Author : JP Richardson
* URL : https://github.com/jprichardson/node-jsonfile
* Lice
Your message dated Sat, 1 Jul 2017 22:03:12 +0200
with message-id <20170701200312.bv34zd57gs355...@angband.pl>
and subject line Re: Bug#866801: RFS: node-jsonfile/3.0.0-1
has caused the Debian Bug report #866801,
regarding RFS: node-jsonfile/3.0.0-1
to be marked as done.
This means that you claim
On Sat, Jul 01, 2017 at 12:21:06PM -0300, Vitor Augusto wrote:
> I am looking for a sponsor for my package "i8kutils":
>
> * Package name: i8kutils
>Version : 1.43
> i8kutils (1.43) unstable; urgency=low
>
> * Remove ui from i8kmon.
> * Removed smm tool as smm.c code is ob
I understood, by your questioning about RC, that I should remove it. If
so, I agree! I am new at packaging. I put RC there as I thought I should
have chosen between ITA,ITP,QA,NMU,RC. It is not clear in the rfs-howto
that this field is optional. Then, RC removed from subject.
Lintian error "bad sy
On Sat, Jul 01, 2017 at 07:15:24PM -0300, Vitor Augusto wrote:
> I understood, by your questioning about RC, that I should remove it. If
> so, I agree! I am new at packaging. I put RC there as I thought I should
> have chosen between ITA,ITP,QA,NMU,RC. It is not clear in the rfs-howto
> that this f
Johannes Schauer writes:
> sbuild maintainer here. In these cases you can always file a bug but
> lets see if we can solve this here.
Thank you for weighing in to this thread.
> Secondly, just using --upgrade will do nothing unless you also --update the
> chroot.
That seems like a bug; why wou
Your message dated Sun, 2 Jul 2017 03:41:58 +0200
with message-id <20170702014158.qvcvodscuxvbq...@angband.pl>
and subject line Re: Bug#866783: RFS: gigalomania/0.28+git.20170219.g08f4811-1
[ITP]
has caused the Debian Bug report #866783,
regarding RFS: gigalomania/0.28+git.20170219.g08f4811-1 [ITP
Hola,
Quoting Ben Finney (2017-07-02 02:57:25)
> > Secondly, just using --upgrade will do nothing unless you also --update the
> > chroot.
> That seems like a bug; why would ‘--upgrade’ silently do nothing? I
> would think it should either complain that it's useless, or implicitly
> turn on ‘--upd
19 matches
Mail list logo
