On Tue, Jul 10, 2012 at 12:56:31AM +0200, jose antonio wrote:
> Hello all,
>
> I have installed Debian Wheezy on my computer and I have followed the
> maint-guide (http://www.debian.org/doc/manuals/maint-guide/) using the
> sources gentoo-0.19.13 I previously have downloaded.
>
> I have practiced
Processing commands for cont...@bugs.debian.org:
> block 680892 by 681020
Bug #680892 [wnpp] ITP: radeontop -- radeontop: Utility to show Radeon GPU
utilization
680892 was not blocked by any bugs.
680892 was not blocking any bugs.
Added blocking bug(s) of 680892: 681020
> stop
Stopping processing
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "radeontop"
* Package name: radeontop
Version : 0.5.4+1-gf2c42f4-1
Upstream Author : Lauri Kasanen
* URL : https://github.com/clbr/radeontop
* License
Processing commands for cont...@bugs.debian.org:
> retitle 678992 RFS: grive/0.2.0-1 [ITP #675310]
Bug #678992 [sponsorship-requests] grive/0.2.0-1 [ITP #675310]
Changed Bug title to 'RFS: grive/0.2.0-1 [ITP #675310]' from 'grive/0.2.0-1
[ITP #675310]'
> stop
Stopping processing here.
Please con
On Mon, Jul 09, 2012 at 05:28:03PM +0200, Andreas Tille wrote:
> [...]
> uscan warning: In directory ., downloading
> https://forge.imag.fr/frs/download.php/238/camitk-3.0.0-Source.tar.gz
> failed: 500 Can't connect to forge.imag.fr:443 (certificate verify failed)
> -- Scan finished
>
> Any ide
On Mon, Jul 9, 2012 at 9:28 AM, Andreas Tille wrote:
> Any idea how to successfully get the upstream source using uscan?
If you are unable to get upstream to have their SSL cert signed by a
CA trusted by your system, you can ignore the certificate validity by
setting the PERL_LWP_SSL_VERIFY_HOSTN
Hi,
at
svn://svn.debian.org/svn/debian-med/trunk/packages/camitk/trunk
I did some preparation for a package including a watch file.
Unfortunately I get:
$ uscan --verbose --force-download
-- Scanning for watchfiles in .
-- Found watchfile in ./debian
-- In debian/watch, processing watchfile
José Luis Segura Lucas wrote:
> Forget about all the patches mess. Upstream has released 0.2.0 version,
> which makes unnecessary to apply all those patches.
>
> I just uploaded it to mentors.debian.net [1]. Please, feel free to
> comment here or in the grive's page on mentors.debian.net any issue
Andreas Rönnquist writes:
> I believe you have greater chances getting an answer to this on
> debian-mentors@lists.debian.org - list CC'd.
Actually, no, not really. The debian-mentors@ list is for Debian
packaging, mostly, not for questions unrelated to that. I'd think -user
or http://ask.debian
For debian packaging I'm using this manual:
https://honk.sigxcpu.org/piki/development/debian_packages_in_git/
2012/7/9 Andreas Rönnquist
> On Mon, 09 Jul 2012 15:26:50 +0200
> Jimmy Thrasibule wrote:
>
> > Hello,
> >
> > I have a core project on which I maintain a set of patches using
> > Quilt
On Mon, 09 Jul 2012 15:26:50 +0200
Jimmy Thrasibule wrote:
> Hello,
>
> I have a core project on which I maintain a set of patches using
> Quilt. This allows me to make changes to the project without touching
> the files so I can upgrade to new versions easily.
>
> I keep my patches and the cor
Processing commands for cont...@bugs.debian.org:
> retitle 678992 grive/0.2.0-1 [ITP #675310]
Bug #678992 [sponsorship-requests] RFS: grive/0.1.1-1 [ITP #675310]
Changed Bug title to 'grive/0.2.0-1 [ITP #675310]' from 'RFS: grive/0.1.1-1
[ITP #675310]'
> thanks
Stopping processing here.
Please c
retitle 678992 grive/0.2.0-1 [ITP #675310]
thanks
Forget about all the patches mess. Upstream has released 0.2.0 version,
which makes unnecessary to apply all those patches.
I just uploaded it to mentors.debian.net [1]. Please, feel free to
comment here or in the grive's page on mentors.debian.ne
13 matches
Mail list logo
