Re: [request-tracker-maintainers] Bug#857748: Please package current version - 1.02

[Satoru KURASHIKI]

hi,

Release team,

In the later stage of freeze, are there any chance to upload newer
upstream version (into testing) to fix RC bugs?
If it can, I will finish staged git chages as soon as I can.

(This package is leaf plugin for request-tracker, so any other
r/depeds will not affect.)

regards,

On Fri, Mar 17, 2017 at 7:12 AM, Dominic Hargreaves  wrote:
> Control: severity -1 serious
>
> On Tue, Mar 14, 2017 at 07:25:32PM +0300, Max Kosmach wrote:
>> X-Debbugs-CC: pkg-request-tracker-maintain...@lists.alioth.debian.org
>> Package: rt4-extension-customfieldsonupdate
>> Version: 0.01-1.1
>>
>> Please package current version (1.02) which is compatible with RT 4.2 and RT 
>> 4.4
>
> Hi Max,
>
> Thanks for raising this issue. From the changelog I take it that 0.0.1
> doesn't support 4.2 or 4.4 at all. Is that your understanding too?
>
> As such this is RC for both jessie and stretch, so raising the
> severity appropriately.
>
> Dominic.



-- 
KURASHIKI Satoru

Bug#771029: unblock: emacs-calfw/1.3+git20141031-2

[Satoru KURASHIKI]

hi,

On Thu, Nov 27, 2014 at 3:38 AM, Niels Thykier ni...@thykier.net wrote:
 To be honest, the 4307ea34 commit smells more like a feature than a bug
 fix at first glance.  Anyhow, please go ahead and let us know once it
 has been uploaded to unstable.

Excuse me, (a bit) incorrect expression. I had seen them as a set of improvement
for displaying diary...

Anyway, thanks, I've uploaded the package into unstable.

regards,
-- 
KURASHIKI Satoru


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAM0xXk_B56PNr942HUBhKF7NtczfhafvTF9+COBmHuH_Xy5=d...@mail.gmail.com

Bug#701098: pre-approval unblock: ruby-rack/1.4.1-2.1

[Satoru KURASHIKI]

hi,

On Fri, Feb 22, 2013 at 12:45 AM, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
 On 21.02.2013 14:31, KURASHIKI Satoru wrote:
 We can't unblock packages which aren't in the archive...

 #698440
 #700173
 #700226


 ... and you don't need pre-approval to fix RC bugs.

OK, I will seek for spnsor to upload into unstable.

 +ruby-rack (1.4.1-2.1) testing-security; urgency=high

 Why does this say testing-security? The upload would go via unstable.

I intended to do the instruction which developers reference 5.8.5.4 says.
I would have better to set it unstable, and after upload I will revisit
this unblock request, right?

regards,
-- 
KURASHIKI Satoru


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAM0xXk-OVeuyh4huWUEFaMvKKBhtOYB5Xa3HkCt=cT58gFP=4...@mail.gmail.com

Bug#698434: unblock: mha4mysql-manager/0.53-2

[Satoru KURASHIKI]

hi,

On Wed, Jan 23, 2013 at 12:17 AM, Niels Thykier ni...@thykier.net wrote:
 So, future version will have unless(defined($msg)). I will prepare
 0.53-3 which apply this in advance.

 Okay, let me know when 0.53-3 is in unstable.

I've uploaded 0.53-3 into unstable. debdiff below:

diff -Nru mha4mysql-manager-0.53/debian/changelog
mha4mysql-manager-0.53/debian/changelog
--- mha4mysql-manager-0.53/debian/changelog 2013-01-18 22:38:59.0 
+0900
+++ mha4mysql-manager-0.53/debian/changelog 2013-01-21 20:35:06.0 
+0900
@@ -1,3 +1,9 @@
+mha4mysql-manager (0.53-3) unstable; urgency=medium
+
+  * replace 0.53-2 patch for more strict conditioning.
+
+ -- KURASHIKI Satoru lur...@gmail.com  Mon, 21 Jan 2013 20:25:46 +0900
+
 mha4mysql-manager (0.53-2) unstable; urgency=medium

   * backports upstream patch to fix UUV issue. (Closes: #697197)
diff -Nru mha4mysql-manager-0.53/debian/patches/chomp-fix
mha4mysql-manager-0.53/debian/patches/chomp-fix
--- mha4mysql-manager-0.53/debian/patches/chomp-fix 2013-01-18
22:34:16.0 +0900
+++ mha4mysql-manager-0.53/debian/patches/chomp-fix 2013-01-21
20:24:49.0 +0900
@@ -6,7 +6,7 @@
  our $log_fmt = sub {
my %args = @_;
my $msg  = $args{message};
-+  $msg =  unless($msg);
++  $msg =  unless(defined($msg));
chomp $msg;
if ( $args{level} eq error ) {
  my ( $ln, $script ) = ( caller(4) )[ 2, 1 ];

regards,
-- 
KURASHIKI Satoru


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAM0xXk8QTaZKmAr97OOYQi83hHQjTCs0xh=auuggragw8ln...@mail.gmail.com

Bug#698434: unblock: mha4mysql-manager/0.53-2

[Satoru KURASHIKI]

hi,

On Fri, Jan 18, 2013 at 11:02 PM, Niels Thykier ni...@thykier.net wrote:
 Technically, this can map a 0 to a  - not sure how likely that is in
 a log_this function, but you(r upstream) might have wanted
 unless(defined($msg)); instead.

I've contacted upstream author about this. he thinks that:

It can be replaced with defined(), though there is no problem
with present code (unless($msg)) by their design.

So, future version will have unless(defined($msg)). I will prepare
0.53-3 which apply this in advance.

regards,
--
KURASHIKI Satoru


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cam0xxk9whxn8fyfs9vxo9j6nwc_fbjma0dv6rrctweb4dtj...@mail.gmail.com

Bug#692740: unblock: hyperestraier/1.4.13-8

[Satoru KURASHIKI]

hi,

On Fri, Nov 23, 2012 at 2:21 AM, Niels Thykier ni...@thykier.net wrote:

 For this to work, you must (after the upload) file a bug against
 ftp.debian.org, requesting for the removal of the s390x binaries.



 The debdiff itself looks reasonable.  That said, I am not sure we will
 re-allow the package into Wheezy due to the delay between the removal
 and this request.

 Freeze Policy: http://release.debian.org/wheezy/freeze_policy.html


Thank you for your checking.

Anyhow, I uploaded the changed source package (it's in NEW queue)
and filed a removal request (which is already dealt with by ftp masters)
as needed steps.

regards,
-- 
KURASHIKI Satoru

Re: Bug#692740: unblock: hyperestraier/1.4.13-8

[Satoru KURASHIKI]

hi,

At Thu, 08 Nov 2012 21:31:18 +0900,
KURASHIKI Satoru wrote:

 Subject: Bug#692740: unblock: hyperestraier/1.4.13-8

I'm sorry forgetting to add the keyword, this bug is intended as
pre approval request (so package itself still don't be uploaded).
# I fixed BTS title.

regards,
--
KURASHIKI Satoru

Bug#668461: RM: request-tracker3.8/3.8.11-1

[Satoru KURASHIKI]

hi,

On Thu, Apr 12, 2012 at 8:54 AM, Konstantin Khomoutov
flatw...@users.sourceforge.net wrote:
 So my question is: is there some upgrade path the users of
 request-tracker3.8 may follow to convert their current installs to the
 new package?  I'm mostly concerned with the database, the settings and
 custom scrips.

I've tried to migrate from 3.8 to 4 with packaged documentation,
and suceeded to do so.

# RT4 itself distributes database migration script from older version.
# It runs pretty fine (with some custom scrips). Though here are some
# pitfalls, you will be able to avoid them by reading those documents.

regards,
-- 
KURASHIKI Satoru



--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAM0xXk_8pnMFQL=bhvnxf1vuh-bpyjseeggascevycuym-b...@mail.gmail.com

Bug#597788: unblock: hyperestraier/1.4.13-2

[Satoru KURASHIKI]

hi,

On Thu, Sep 23, 2010 at 2:57 PM, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
 On Thu, 2010-09-23 at 08:34 +0900, KURASHIKI Satoru wrote:
 Please unblock package hyperestraier. 1.4.13-2 basically
 fixes FTBFS bugs introduced in 1.4.13-1.

 That's a fairly broad definition of basically, given this:

 hyperestraier (1.4.13-2) unstable; urgency=low
 [...]
   * libestraier-ruby-doc:
     new package. split ruby api documentation.

 Introducing new packages during freeze is not particularly helpful;
 tying an RC-bug fix up with it less so still.

I've recognized this, as it should be introduced in 1.4.13-1, when I
added separate package for supporting ruby 1.9 series.
(to avoid including duplicate documents for them)

 As 1.4.13-1 never managed to migrate to testing due to the FTBFS bugs,
 afaics none of the bugs fixed in -2 are regressions from the version
 currently in Squeeze; I'm debating whether we should therefore just
 leave 1.4.9-1.4 in Squeeze.

Please consider to update 1.4.13, though I  know that I couldn't push it
to testing before freeze because of my inmature packaging;
1.4.9 (released 2006/11) is pretty old, even though for lenny. No users
want to use it.

regards,
-- 
KURASHIKI Satoru



--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikczsgp49bppqc_3gtouppvcs-tgcuxab_...@mail.gmail.com