Hi, it looks as a very good idea, indeed .
On 10/08/17 08:13, Alexandre Hannud Abdo wrote:
> Ni!
>
> Hello Debian science maintainers,
>
> I am quite new to Debian packaging, but I'd like to help see the graph-
> tool[1] scientific library packaged for Debian.
>
> [1] http://graph-tool.skewed.d
FYI: The status of the lua-torch-sys source package
in Debian's testing distribution has changed.
Previous version: 0~20161027-gf073f05-1
Current version: 0~20161027-gf073f05-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens mul
Ni!
Hello Debian science maintainers,
I am quite new to Debian packaging, but I'd like to help see the graph-
tool[1] scientific library packaged for Debian.
[1] http://graph-tool.skewed.de/
The main developper of the package already provides his own repo[2],
which I checked and as far as I und
Processing commands for cont...@bugs.debian.org:
> tag 853513 pending
Bug #853513 [src:libvigraimpex] libvigraimpex: BlockwiseWatershedTest not fit
for gcc7
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
853513: https://bugs.debian.org/cgi-
Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-dynamic-reconfigure: FTBFS: ImportError: No module named yaml
to be marked as done.
This means that you claim that the
Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-ros-comm: FTBFS: ImportError: No module named yaml
to be marked as done.
This means that you claim that the problem ha
Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-bond-core: FTBFS: ImportError: No module named yaml
to be marked as done.
This means that you claim that the problem h
Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-std-msgs: FTBFS: ImportError: No module named yaml
to be marked as done.
This means that you claim that the problem ha
Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-common-msgs: FTBFS: ImportError: No module named yaml
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-geometry: FTBFS: ImportError: No module named yaml
to be marked as done.
This means that you claim that the problem ha
Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding python-genpy: missing dependency on python-yaml
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-geometry-experimental: FTBFS: ImportError: No module named yaml
to be marked as done.
This means that you claim that t
Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-navigation-msgs: FTBFS: ImportError: No module named yaml
to be marked as done.
This means that you claim that the pro
Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-ros-comm-msgs: FTBFS: ImportError: No module named yaml
to be marked as done.
This means that you claim that the probl
Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-image-common: FTBFS: ImportError: No module named yaml
to be marked as done.
This means that you claim that the proble
Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-pcl-msgs: FTBFS: ImportError: No module named yaml
to be marked as done.
This means that you claim that the problem ha
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 09 Aug 2017 22:43:19 +0200
Source: ros-genpy
Binary: python-genpy
Architecture: source
Version: 0.6.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Jochen Sprickerhof
ros-genpy_0.6.6-2_source.changes uploaded successfully to localhost
along with the files:
ros-genpy_0.6.6-2.dsc
ros-genpy_0.6.6-2.debian.tar.xz
ros-genpy_0.6.6-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
debian-science-maintainers m
ros-genpy_0.6.6-2.dsc: Invalid size hash for ros-genpy_0.6.6.orig.tar.gz:
According to the control file the size hash should be 51945,
but ros-genpy_0.6.6.orig.tar.gz has 51949.
If you did not include ros-genpy_0.6.6.orig.tar.gz in your upload, a different
version
might already be known to the
binary:apertium-bel is NEW.
binary:apertium-bel is NEW.
source:apertium-bel is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patie
ros-genpy_0.6.6-2_source.changes uploaded successfully to localhost
along with the files:
ros-genpy_0.6.6-2.dsc
ros-genpy_0.6.6-2.debian.tar.xz
ros-genpy_0.6.6-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
debian-science-maintainers m
apertium-bel_0.1.0~r81357-1_amd64.changes uploaded successfully to localhost
along with the files:
apertium-bel_0.1.0~r81357-1.dsc
apertium-bel_0.1.0~r81357.orig.tar.bz2
apertium-bel_0.1.0~r81357-1.debian.tar.xz
apertium-bel_0.1.0~r81357-1_all.deb
apertium-bel_0.1.0~r81357-1_amd64.buildin
Package: bibus
Version: 1.5.2-4
Severity: wishlist
Please remove me from the Uploaders list.
For further details, see
https://lists.alioth.debian.org/pipermail/debian-science-maintainers/2017-August/052195.html.
Thanks and best regards,
Jan
--
Jan Beyer
mailj...@beathovn.de
binary:apertium-rus is NEW.
binary:apertium-rus is NEW.
source:apertium-rus is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patie
Hello Anton,
thanks a lot for the heads-up. I will go ahead and submit the bug report, as
you proposed. That's a good idea.
Best regards,
Jan
Am 08.08.2017 um 21:46 schrieb Anton Gladky:
> Hi Jan,
>
> thanks for your work on this package. It seems bibus is in a
> good shape, at least there are
apertium-rus_0.1.0~r81184-1_amd64.changes uploaded successfully to localhost
along with the files:
apertium-rus_0.1.0~r81184-1.dsc
apertium-rus_0.1.0~r81184.orig.tar.bz2
apertium-rus_0.1.0~r81184-1.debian.tar.xz
apertium-rus_0.1.0~r81184-1_all.deb
apertium-rus_0.1.0~r81184-1_amd64.buildin
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 31 Jul 2017 19:38:57 -0700
Source: scram
Binary: scram scram-gui
Architecture: source amd64
Version: 0.14.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Olzhas Rakhi
Mapping stretch to stable.
Mapping stable to proposed-updates.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 30 Jul 2017 18:01:10 -0300
Source: librsb
Binary: librsb0 librsb-dev librsb-doc
Architecture: source amd64 all
Version: 1.2.0-rc5-3+deb9u1
Distribution:
librsb_1.2.0-rc5-3+deb9u1_amd64.changes uploaded successfully to localhost
along with the files:
librsb_1.2.0-rc5-3+deb9u1.dsc
librsb_1.2.0-rc5-3+deb9u1.debian.tar.xz
librsb-dev-dbgsym_1.2.0-rc5-3+deb9u1_amd64.deb
librsb-dev_1.2.0-rc5-3+deb9u1_amd64.deb
librsb-doc_1.2.0-rc5-3+deb9u1_all.d
Hello Drew,
Thanks for the bug report.
Στις Σάββατο, 29 Ιουλίου 2017 6:13:09 Μ.Μ. EEST γράψατε:
> Source: freefem++
> Version: 3.47+dfsg1-1
> Severity: normal
>
> blacs is about to be removed from the Debian archives, replaced by
> scalapack2.0 (now in experimental). So the configuration for th
Your message dated Wed, 9 Aug 2017 09:45:26 +0200
with message-id
and subject line enblend-enfuse: ftbfs with GCC-7
has caused the Debian Bug report #853389,
regarding enblend-enfuse: ftbfs with GCC-7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 9 Aug 2017 09:45:33 +0200
with message-id <74b08770-6032-f98c-6989-bde7ba07d...@danielstender.com>
and subject line hugin: ftbfs with GCC-7
has caused the Debian Bug report #853447,
regarding hugin: ftbfs with GCC-7
to be marked as done.
This means that you claim that the p
Processing commands for cont...@bugs.debian.org:
> reassign 853389 src:libvigraimpex
Bug #853389 [src:enblend-enfuse] enblend-enfuse: ftbfs with GCC-7
Bug reassigned from package 'src:enblend-enfuse' to 'src:libvigraimpex'.
No longer marked as found in versions enblend-enfuse/4.2-2.
Ignoring reque
Processing commands for cont...@bugs.debian.org:
> unblock 853389 by 853513
Bug #853389 [src:enblend-enfuse] enblend-enfuse: ftbfs with GCC-7
853389 was blocked by: 853513
853389 was not blocking any bugs.
Removed blocking bug(s) of 853389: 853513
> unblock 853447 by 853513
Bug #853447 [src:hugin]
Source: libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)
With the latest upload there are FTBFS problems on some archs.
Running test_gridgraph
cd
/<>/libvigraimpex-1.10.0+git20160211.167be93
Your message dated Wed, 9 Aug 2017 09:05:06 +0200
with message-id
and subject line gamera: ftbfs with GCC-7
has caused the Debian Bug report #853412,
regarding gamera: ftbfs with GCC-7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Processing commands for cont...@bugs.debian.org:
> reassign 853412 src:libvigraimpex
Bug #853412 [src:gamera] gamera: ftbfs with GCC-7
Bug reassigned from package 'src:gamera' to 'src:libvigraimpex'.
No longer marked as found in versions gamera/1:3.4.2+git20160808.1725654-1.
Ignoring request to al
37 matches
Mail list logo
