On Thu, Apr 2, 2015 at 3:51 AM, Antti Järvinen wrote:
> I'll write about this to debian-devel-announce.
That is only for announcements :)
> But here I need advice as https://wiki.debian.org/DebianMaintainer
> says I'll need a PGP-key with at least 2k key length.
>
> The key I used at https://men
On Mon, 1 Dec 2014 10:27:52 Paul Wise wrote:
> Personally I prefer to separate packaging from upstream development
> because they are two different things. When I use a VCS for packaging
> it contains only the debian/ directory.
This is how I like to handle Debian packaging in git as well.
--
Ch
On Wed, 1 Apr 2015 09:20:34 Etienne Millon wrote:
> I refreshed this, forwarded two patches and picked the upstream
> version of one.
Nice. But I meant to use all those headers (except for Applied-Upstream which
I use ocassionally).
> I'm not too familiar with how icons work, so I've installed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tobias Frost writes:
> Control: owner -1 !
> Control: tags -1 pending
Aye, best aprils fool's prank for some time :)
> Debian sees the (high-res image) as part of the source code, the
> preferred form of the source actually. So you should include
Package: sponsorship-requests
Severity: normal
I am looking for a sponsor for the source package "h5py".
It builds the following binary packages:
python-h5py -- Python 2 version
python3-h5py -- Python 3 version
This upload brings the package up to date with the most recent
stable upstream
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "node-convert-source-map"
* Package name: node-convert-source-map
Version : 1.0.0-1
Upstream Author : Thorsten Lorenz (http://thlorenz.com)
* URL : https://github
* Alexandre Detiste [150401 20:22]:
> Le mercredi 1 avril 2015, 20:38:30 Dmitry Smirnov a écrit :
> > Hmm, how about doing it gnu-make-style?
>
> I tried that too, but this doesn't work as I expected ("Only the first ‘%’ in
> the pattern and replacement is treated this way; any subsequent ‘%’ i
Your message dated Wed, 1 Apr 2015 17:47:53 +0100
with message-id
and subject line
has caused the Debian Bug report #781381,
regarding RFS: h5py/2.2.1-2~exp1 -- general-purpose Python interface to hdf5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Le mercredi 1 avril 2015, 20:38:30 Dmitry Smirnov a écrit :
> Hmm, how about doing it gnu-make-style?
I tried that too, but this doesn't work as I expected ("Only the first ‘%’ in
the pattern and replacement is treated this way; any subsequent ‘%’ is
unchanged." from the manual)
--
icons := $
Your message dated Wed, 1 Apr 2015 14:49:16 +0100
with message-id <20150401134916.ga27...@shiftout.net>
and subject line xastir/2.0.6-1 uploaded to unstable
has caused the Debian Bug report #771433,
regarding RFS: xastir/2.0.6-1
to be marked as done.
This means that you claim that the problem has
On Wed, 1 Apr 2015 20:38:30 Dmitry Smirnov wrote:
> Hmm, how about doing it gnu-make-style?
Just kidding, your way is OK, just please pass
"--mode=644 --preserve-timestamps" to install (taking care of reproducible
build etc.). Also you can replace `mkdir` with `-D` option to `install`.
--
Chee
On Wed, 1 Apr 2015 10:19:15 Alexandre Detiste wrote:
> I fixed the icon location.
>
> for size in 22 24 32 48 128 ; do \
> - mkdir -p usr/share/icons/hicolor/$${size}x$${size}/apps ;\
> - install linux/icons/tyrian-$${size}.png
> usr/share/icons/hicolor/$${size}x$${size}/apps/opentyrian.png ;\
> +
> Thanks for taking the time to look at this.
Thanks too.
I fixed the icon location.
for size in 22 24 32 48 128 ; do \
- mkdir -p usr/share/icons/hicolor/$${size}x$${size}/apps ;\
- install linux/icons/tyrian-$${size}.png
usr/share/icons/hicolor/$${size}x$${size}/apps/opentyrian.png ;\
+ mkdir
* Dmitry Smirnov [150401 07:34]:
> On Tue, 31 Mar 2015 19:35:12 Etienne Millon wrote:
> > I am looking for a sponsor for my package "opentyrian"
>
> That is very nice. I was looking forward to see opentyrian in Debian for a
> while. Thanks for packaging.
Thanks for taking the time to look at th
Hi Niels,
thanks for your quick reply.
> Note that uploading it to proposed-updates is not sufficient to mark it
> as fixed in stable. If you have uploaded the fix for the coming point
> release, the bug will remain open until the release actually happens.
Okay, I see. This means that everythin
15 matches
Mail list logo
