Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Hi Adam,
On 2/4/23 13:11, Adam D. Barratt wrote:
Control: tags -1 + confirmed
On Sun, 2023-01-29 at 20:28 -0500, Olek Wojnar wrote:
The phyx package incorrectly declares a Build Dependency on the
libatlas-cpp-0.6-dev package. The src:atlas-cpp package is obsolete
since the
only packages
upload
+ * Remove erroneous Build Dependency on libatlas-cpp
+- libatlas-cpp is completely unrelated to phyx and phyx does not use it
+- The BD was added accidentally and needs to be removed for proper
+ dependency resolution
+
+ -- Olek Wojnar Sun, 29 Jan 2023 18:27:53 -0500
+
phyx
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear Release Team,
Please unblock package google-oauth-client-java
[ Reason ]
Backport of fix for RC security issue (CVE-2020-7692)
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Stable Release Team,
I would like to add the ember package [1] to proposed-updates. This package
did not make it into buster before release due to problems with one of its
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Release team,
Please provide a transition slot for atlas-cpp. This should be fairly
straightforward: there are only 3 reverse-depends and I maintain all three of
them. They all build
to Frans Spiesschaert (Closes: #771370)
+
+ -- Olek Wojnar olek-...@wojnar.org Thu, 04 Dec 2014 22:32:18 -0500
+
+cyphesis-cpp (0.6.0-2) unstable; urgency=medium
+
+ * Fix d/postinst error (Closes: #767057)
+ * Fix libreadline dependency (Closes: #767009)
+
+ -- Olek Wojnar olek-...@wojnar.org Tue
14 matches
Mail list logo
