On Mon, 2013-07-01 at 12:44 +0530, Ritesh Raj Sarraf wrote:
> On Sunday 30 June 2013 11:36 PM, Adam D. Barratt wrote:
> > +multipath-tools (0.4.9+git0.4dfdaf2b-7+stable1) stable-proposed-updates;
> > urgency=low
> >
> > That version number won't work, for a couple of reasons - not least
> > becaus
On 2013-07-01 09:14, Ritesh Raj Sarraf wrote:
> On Sunday 30 June 2013 11:36 PM, Adam D. Barratt wrote:
>> +multipath-tools (0.4.9+git0.4dfdaf2b-7+stable1) stable-proposed-updates;
>> urgency=low
>>
>> That version number won't work, for a couple of reasons - not least
>> because it's _higher_ tha
On Sunday 30 June 2013 11:36 PM, Adam D. Barratt wrote:
> +multipath-tools (0.4.9+git0.4dfdaf2b-7+stable1) stable-proposed-updates;
> urgency=low
>
> That version number won't work, for a couple of reasons - not least
> because it's _higher_ than the version you uploaded to unstable.
>
> Please us
On Tue, 2013-06-11 at 13:13 +0530, Ritesh Raj Sarraf wrote:
> On Monday 10 June 2013 08:52 PM, Ritesh Raj Sarraf wrote:
> > On Monday 10 June 2013 08:12 PM, Adam D. Barratt wrote:
> >> Getting the fixes in to sid would be appreciated in any case, so that
> >> we can look at a p-u update for 7.2.
>
On Thu, Jun 13, 2013 at 10:31:02PM +0530, Ritesh Raj Sarraf wrote:
> On Tuesday 11 June 2013 01:13 PM, Ritesh Raj Sarraf wrote:
> > On Monday 10 June 2013 08:52 PM, Ritesh Raj Sarraf wrote:
> >> > On Monday 10 June 2013 08:12 PM, Adam D. Barratt wrote:
> >>> >> For the record, the window for gettin
On 2013-06-13 18:01, Ritesh Raj Sarraf wrote:
On Tuesday 11 June 2013 01:13 PM, Ritesh Raj Sarraf wrote:
On Monday 10 June 2013 08:52 PM, Ritesh Raj Sarraf wrote:
> On Monday 10 June 2013 08:12 PM, Adam D. Barratt wrote:
>> For the record, the window for getting fixes in to the upcoming
point
On Tuesday 11 June 2013 01:13 PM, Ritesh Raj Sarraf wrote:
> On Monday 10 June 2013 08:52 PM, Ritesh Raj Sarraf wrote:
>> > On Monday 10 June 2013 08:12 PM, Adam D. Barratt wrote:
>>> >> For the record, the window for getting fixes in to the upcoming point
>>> >> release closed yesterday.
>>> >>
>>
On Monday 10 June 2013 08:52 PM, Ritesh Raj Sarraf wrote:
> On Monday 10 June 2013 08:12 PM, Adam D. Barratt wrote:
>> For the record, the window for getting fixes in to the upcoming point
>> release closed yesterday.
>>
>> Getting the fixes in to sid would be appreciated in any case, so that
>> we
On Monday 10 June 2013 08:12 PM, Adam D. Barratt wrote:
>
> For the record, the window for getting fixes in to the upcoming point
> release closed yesterday.
>
> Getting the fixes in to sid would be appreciated in any case, so that
> we can look at a p-u update for 7.2.
I will get it done for sid
On 2013-06-10 15:21, Ritesh Raj Sarraf wrote:
On Sunday 09 June 2013 11:28 PM, Jonathan McDowell wrote:
I can't see anything on
> > > http://packages.qa.debian.org/m/multipath-tools.html so I'm
assuming
> > > this isn't going to make the first point release next
weekend?
[...]
Ritesh, if the
On Sunday 09 June 2013 11:28 PM, Jonathan McDowell wrote:
I can't see anything on
> > > http://packages.qa.debian.org/m/multipath-tools.html so I'm assuming
> > > this isn't going to make the first point release next weekend?
>>> > >
>>> > > Attached are the 2 patches that need to b
On Sun, Jun 09, 2013 at 12:54:56PM +0100, Adam D. Barratt wrote:
> On Sun, 2013-06-09 at 17:18 +0530, Ritesh Raj Sarraf wrote:
> > On Sunday 09 June 2013 05:28 AM, Jonathan McDowell wrote:
> > > I can't see anything on
> > > http://packages.qa.debian.org/m/multipath-tools.html so I'm assuming
> > >
On Sun, 2013-06-09 at 17:18 +0530, Ritesh Raj Sarraf wrote:
> On Sunday 09 June 2013 05:28 AM, Jonathan McDowell wrote:
> > I can't see anything on
> > http://packages.qa.debian.org/m/multipath-tools.html so I'm assuming
> > this isn't going to make the first point release next weekend?
>
> Attach
On Sunday 09 June 2013 05:28 AM, Jonathan McDowell wrote:
> I can't see anything on
> http://packages.qa.debian.org/m/multipath-tools.html so I'm assuming
> this isn't going to make the first point release next weekend?
Attached are the 2 patches that need to be added.
My build is failing for som
On Sat, May 25, 2013 at 12:55:33PM +0530, Ritesh Raj Sarraf wrote:
> On Saturday 25 May 2013 05:13 AM, Jonathan McDowell wrote:
> > I've just hit this myself upgrading a server to wheezy and can't see any
> > sign of more recent packages in the archive yet. Is it likely this will
> > happen in time
On Saturday 25 May 2013 05:13 AM, Jonathan McDowell wrote:
> I've just hit this myself upgrading a server to wheezy and can't see any
> sign of more recent packages in the archive yet. Is it likely this will
> happen in time for the first point release next month?
Yes. THis should go into s-p-u. I
On Monday 8th April 2013 22:04 PM, Ritesh Raj Sarraf wrote:
> On Monday 08 April 2013 02:43 PM, Guy Roussin wrote:
> >> Just to re-confirm, is the actual bug, that was initially reported by
> >> Guy, is that also resolved?
> > Yes the bug is resolved. No more errors when "update-initramfs -u"
> >
>
On Monday 08 April 2013 02:43 PM, Guy Roussin wrote:
>> Just to re-confirm, is the actual bug, that was initially reported by
>> Guy, is that also resolved?
> Yes the bug is resolved. No more errors when "update-initramfs -u"
>
> Thank you,
>
Thank you for confirming.
Given that we are in deep fre
> Just to re-confirm, is the actual bug, that was initially reported by
> Guy, is that also resolved?
Yes the bug is resolved. No more errors when "update-initramfs -u"
Thank you,
--
Guy
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Tr
On Wednesday 03 April 2013 06:56 PM, matthew pideil wrote:
> Thanks, it works now.
>
> LM05q:~# dpkg -l |grep multipath
> ii multipath-tools0.4.9+git0.4dfdaf2b-7 ...
> ii multipath-tools-boot 0.4.9+git0.4dfdaf2b-7 ...
Thank you Matthew.
Just to re-confirm, is
Le 02/04/2013 20:19, Ritesh Raj Sarraf a écrit :
To work around it, you will have to brute force part of the
installation. Attached with this email is the new initscirpt which has
the fix. You need to take this initscript and overwrite it to the one in
/etc/init.d/
Once you do that, you should no
On Tue, Apr 02, 2013 at 11:49:54PM +0530, Ritesh Raj Sarraf wrote:
> On Tuesday 02 April 2013 08:27 PM, matthew pideil wrote:
>
> Okay!! It is a tricky situation now. The old, buggy version, has the bug
> that you cannot stop the daemon. When the dpkg installer calls it with
> the stop target, it
On Tuesday 02 April 2013 08:27 PM, matthew pideil wrote:
> Hello,
>
> I tried your packages without results :
>
> LM05q:~/tmp# LANG=C dpkg -i *deb
> (Reading database ... 31699 files and directories currently installed.)
> Preparing to replace kpartx 0.4.9+git0.4dfdaf2b-7 (using
> kpartx_0.4.9+git0
Hello,
I tried your packages without results :
LM05q:~/tmp# LANG=C dpkg -i *deb
(Reading database ... 31699 files and directories currently installed.)
Preparing to replace kpartx 0.4.9+git0.4dfdaf2b-7 (using
kpartx_0.4.9+git0.4dfdaf2b-7_amd64.deb) ...
Unpacking replacement kpartx ...
Preparin
On Saturday 30 March 2013 01:13 AM, Ritesh Raj Sarraf wrote:
> On Friday 29 March 2013 01:46 PM, Guy Roussin wrote:
>> > multipath-tools_0.4.9+git0.4dfdaf2b-7_amd64.deb) ...
>> > [] Root is on a multipathed device, multipathd can not be
>> > stopped:invoke-rc.d: initscript multipath-tools, acti
On Friday 29 March 2013 01:46 PM, Guy Roussin wrote:
> multipath-tools_0.4.9+git0.4dfdaf2b-7_amd64.deb) ...
> [] Root is on a multipathed device, multipathd can not be
> stopped:invoke-rc.d: initscript multipath-tools, action "stop" failed.
> dpkg: warning: subprocess old pre-removal script ret
Le 29/03/2013 08:20, Ritesh Raj Sarraf a écrit :
> On Friday 29 March 2013 01:04 AM, Ritesh Raj Sarraf wrote:
>
>> Can you paste the logs when you hit the command?
>> The init script denies stopping the daemon since root in on multipath.
>>
>> But I guess, your installation would have completed.
On Friday 29 March 2013 01:04 AM, Ritesh Raj Sarraf wrote:
> Can you paste the logs when you hit the command?
> The init script denies stopping the daemon since root in on multipath.
>
> But I guess, your installation would have completed. Can you also paste
> the output of dpkg -l | grep -i multip
On Thursday 28 March 2013 11:10 PM, Guy Roussin wrote:
> Hi,
>
> Thank you Ritesh,
> I don't know how to test those packages. I try dpkg -i *deb
> but multipath-tools refuse to upgrade because "/" is
> multipathed ...
>
> I can make some tests, my server is not a production server ...
Can you past
On 28/03/2013 16:55, Ritesh Raj Sarraf wrote:
On Thursday 28 March 2013 04:08 PM, Michael Prokop wrote:
I can't see a reason why this would fail. I suspect it to be an
>initramfs problem.
Looks like /usr/share/initramfs-tools/scripts/init-top/multipath is
missing the PREREQ/prereqs header (see
On Thursday 28 March 2013 04:08 PM, Michael Prokop wrote:
>> I can't see a reason why this would fail. I suspect it to be an
>> > initramfs problem.
> Looks like /usr/share/initramfs-tools/scripts/init-top/multipath is
> missing the PREREQ/prereqs header (see e.g. initramfs-tools(8)), so
> set this
reassign 704073 multipath-tools-boot
thanks
* Ritesh Raj Sarraf [Thu Mar 28, 2013 at 10:58:20AM +0530]:
> On Wednesday 27 March 2013 10:03 PM, Guy Roussin wrote:
> > I get this error when upgrading from squeeze to wheezy
> > on a boot on san (ibm ds4700)
> > update-initramfs: Generating /boot/in
reassign 704073 initramfs-tools
thanks
On Wednesday 27 March 2013 10:03 PM, Guy Roussin wrote:
> I get this error when upgrading from squeeze to wheezy
> on a boot on san (ibm ds4700)
>
> update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
> /var/tmp/mkinitramfs_aO0QW9/scripts/init-top/mul
Package: multipath-tools-boot
Version: 0.4.9+git0.4dfdaf2b-6
Severity: normal
--- Please enter the report below this line. ---
Hi,
I get this error when upgrading from squeeze to wheezy
on a boot on san (ibm ds4700)
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
/var/tmp/mkinitramf
34 matches
Mail list logo
