Bug#1011483: closed by Chris Hofstaedtler (Re: #1011483 duplicate/related to #1003366)

2022-08-05 Thread Chris Hofstaedtler
Hi,

* Eugene Losowski-Gallagher  [220804 
18:48]:
> Hi Chris,
> 
> Thank you for the prompt to test against sid.
> I just tested and can confirm that it works.

Thanks for checking!

Chris



Bug#1011483: closed by Chris Hofstaedtler (Re: #1011483 duplicate/related to #1003366)

2022-08-04 Thread Eugene Losowski-Gallagher
Hi Chris,

Thank you for the prompt to test against sid.
I just tested and can confirm that it works.

Thank you so much for the help.

Eugene

On Thu, 4 Aug 2022 at 13:00, Chris Hofstaedtler  wrote:

> Hi Eugene,
>
> * Eugene Losowski-Gallagher 
> [220804 08:25]:
> > Ref: Bug#1011483
> (please keep the bug in To:)
>
> > Thank you for the comment on closing, and apologies for the delay in
> > writing.
> > I'll admit the description is poor (I submitted too early while trying to
> > report it- so didn't properly write the description to match the title).
> >
> > Questions on this closing:
> > 1) What is happening to the patch attached?
> > 2) I also wrote a patch for 1003366 - and both should resolve the issues
> on
> > OpenISCSI (just needs to be applied in order 1003366 first, then
> 1011483).
>
> > I have tested these and am using the "dev" build as installation media
> > until these get applied.
> >
> > Please advice how to proceed: New ticket for all components + patch,
> > patches applied (and both closed), etc?
>
> As far as I know, iscsi now works in the installer. I tried a sid
> installer from a few days ago and successfully installed a new VM.
>
> Is there anything left to do / something that does not work for you?
>
> Chris
>
>

-- 

*Eugene Losowski-Gallagher*
*Mob: *07825160923


Bug#1011483: closed by Chris Hofstaedtler (Re: #1011483 duplicate/related to #1003366)

2022-08-04 Thread Eugene Losowski-Gallagher
Hi Chris,

Ref: Bug#1011483

Thank you for the comment on closing, and apologies for the delay in
writing.
I'll admit the description is poor (I submitted too early while trying to
report it- so didn't properly write the description to match the title).

Questions on this closing:
1) What is happening to the patch attached?
2) I also wrote a patch for 1003366 - and both should resolve the issues on
OpenISCSI (just needs to be applied in order 1003366 first, then 1011483).

I have tested these and am using the "dev" build as installation media
until these get applied.

Please advice how to proceed: New ticket for all components + patch,
patches applied (and both closed), etc?

Many thanks

Eugene


On Fri, 29 Jul 2022 at 21:27, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the open-iscsi package:
>
> #1011483: reportbug: open-iscsi-udeb - iscsiadm InitiatorName not set:
> /etc/iscsi/initiatorname.iscsi does not exist
>
> It has been closed by Chris Hofstaedtler .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Chris Hofstaedtler <
> z...@debian.org> by
> replying to this email.
>
>
> --
> 1011483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011483
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Chris Hofstaedtler 
> To: 1011483-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Fri, 29 Jul 2022 22:22:17 +0200
> Subject: Re: #1011483 duplicate/related to #1003366
> I'll close this bug (doesnt have much info) in favor of #1003366.
>
>
> -- Forwarded message --
> From: Eugene 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Mon, 23 May 2022 22:02:09 +0100
> Subject: reportbug: open-iscsi-udeb - iscsiadm InitiatorName not set:
> /etc/iscsi/initiatorname.iscsi does not exist
> Package: open-iscsi
> Version: 2.1.3-5
> Severity: normal
> Tags: d-i
> X-Debbugs-Cc: eugene.losowskigallag...@googlemail.com
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate
> ***
>
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
>
> *** End of the template - remove these template lines ***
>
>
> -- System Information:
> Debian Release: 11.3
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
> 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_GB:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages open-iscsi depends on:
> ii  debconf [debconf-2.0]  1.5.77
> ii  libc6  2.31-13+deb11u3
> ii  libisns0   0.100-3
> ii  libkmod2   28-1
> ii  libmount1  2.36.1-8+deb11u1
> ii  libopeniscsiusr2.1.3-5
> ii  libssl1.1  1.1.1n-0+deb11u2
> ii  libsystemd0247.3-7
> ii  udev   247.3-7
>
> open-iscsi recommends no packages.
>
> open-iscsi suggests no packages.
>
> -- debconf information excluded
>


-- 

*Eugene Losowski-Gallagher*
*Mob: *07825160923


Bug#1011483: closed by Chris Hofstaedtler (Re: #1011483 duplicate/related to #1003366)

2022-08-04 Thread Chris Hofstaedtler
Hi Eugene,

* Eugene Losowski-Gallagher  [220804 
08:25]:
> Ref: Bug#1011483
(please keep the bug in To:)

> Thank you for the comment on closing, and apologies for the delay in
> writing.
> I'll admit the description is poor (I submitted too early while trying to
> report it- so didn't properly write the description to match the title).
> 
> Questions on this closing:
> 1) What is happening to the patch attached?
> 2) I also wrote a patch for 1003366 - and both should resolve the issues on
> OpenISCSI (just needs to be applied in order 1003366 first, then 1011483).

> I have tested these and am using the "dev" build as installation media
> until these get applied.
> 
> Please advice how to proceed: New ticket for all components + patch,
> patches applied (and both closed), etc?

As far as I know, iscsi now works in the installer. I tried a sid
installer from a few days ago and successfully installed a new VM.

Is there anything left to do / something that does not work for you?

Chris