2/debian/changelog 2023-02-21 14:13:26.0 +0100
+++ binoculars-0.0.13/debian/changelog 2023-04-14 19:23:27.0 +0200
@@ -1,3 +1,11 @@
+binoculars (0.0.13-1) unstable; urgency=medium
+
+ * New upstream version 0.0.13
+ * d/control: B-D removed python3-vtk9
+ * d/patches: remo
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package binoculars
It solves 3 important bugs, the later one is very important since it let the
package completly unusable without the proposed fixes.
923859, 924024 , 9867
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pi...@debian.org
Please unblock package debian-pan
it is a Debian blends, the objectif od this blends is to package
softwares for synchrotron and neutron facilities.
https://
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: pi...@debian.org
(please explain about the transition: impacted packages, reason, ...
for more info see: https://wiki.debian.org/Teams/ReleaseTeam/Transitions)
Hello,
I
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package sardana
Hello, first this unblock depends of this other unblock bug #767074.
with the same reasons than taurus. but sardana depends of the latests taurus
package.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package taurus
Hello, me and the upstream of taurus worked last week to prepare
a release of taurus specifically for debian8.
this is mostly a bug fix. (the usual relase cycl
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Hello
It seems that with the latest python the extensions are expected to be under
/usr/lib/python2.x/site-package//gnukfreebsd9 instead of gnukfreebsd8
(when the package was uploaded)
the
> > If you think that it it better to take only the first and the last chunk,
> > just tell me.
> I would prefer that, yes. Otherwise no objections, please ping the bug when
> it's uploaded.
ok,
I remove the undesired part. The last chunck was changed a little bit since it
contains also the r
> Perhaps I'm wrong, but from what I can see only the first and last hunks
> patching setup.py are actually relevant, the rest just renames the
> argument? Did I miss something significant?
Yes in fact I took the patch from the upstream and adapt the rules file to use
the
renamed option.
If you
>The diff you sent doesn't contain these patches...
Sorry about that, I did the debdiff with the .dsc but.
So here the 2 patches
Cheers
FredFrom: =?UTF-8?q?Picca=20Fr=C3=A9d=C3=A9ric-Emmanuel?=
Date: Fri, 18 Jan 2013 21:20:39 +0100
Subject: upstream fix for the FTBFS due to image conversion
-
-upstream-fix-for-the-FTBFS-due-to-image-conversion.patch
+ * All icons are now available (Closes: #698464)
+- 0003-upstream-fix-tango-icon-resources.patch
+
+ -- Picca Frédéric-Emmanuel Fri, 18 Jan 2013 21:50:25
+0100
+
taurus (3.0.0-1) unstable; urgency=low
* Initial release (Closes
> Unfortunately, this does not say what the problem was. (Please let me
> refer you to devref 6.3, that reads: "When referring to bugs, don't
> assume anything. Say what the problem was, how it was fixed, and
> append the closes: #n string.".)
> But well, this was uploaded already, so whatever.
2.1.10/debian/changelog 2012-07-31 22:44:05.0 +0200
@@ -1,3 +1,10 @@
+spyder (2.1.10-2) unstable; urgency=low
+
+ * debian/pacthes
+- 0003-from-upstream-fix-1098.patch (new) (Closes: #678339)
+
+ -- Picca Frédéric-Emmanuel Tue, 31 Jul 2012 22:42:04 +0200
+
spyder (2.1.10-1) unstab
w
+
+ * debian/patch
+- 0002-debian-my.cnf.in.patch (updated) (Closes: #684332)
+ put the right user in my.cnf using dbconfig-common template engine
+
+ -- Picca Frédéric-Emmanuel Sat, 15 Sep 2012 08:31:51 +0200
+
tango (7.2.6+dfsg-13) unstable; urgency=low
* Bump Standards-Version to 3.9.3
d
14 matches
Mail list logo
