Control: tags -1 - pending

Ciao Lazarus

On Wed, Nov 14, 2012 at 02:23:06AM +0000, Lazarus Long wrote:
> On Tue, Nov 13, 2012 at 9:15 PM, Salvatore Bonaccorso <car...@debian.org> 
> wrote:
> > Hi Lazarus
> >
> > On Tue, Nov 13, 2012 at 07:37:11PM +0000, Lazarus Long wrote:
> >> On Mon, Nov 12, 2012 at 5:09 PM, Salvatore Bonaccorso <car...@debian.org> 
> >> wrote:
> >> >
> >> > Hi Steven
> >> >
> >> > On Wed, Nov 07, 2012 at 10:48:15AM +0100, Steven Post wrote:
> >> > > Package: sqldeveloper-package
> >> > > Version: 0.2.3+nmu1
> >> > > Severity: grave
> >> > >
> >> > >
> >> > > Dear maintainer,
> >> > >
> >> > > The command make-sql-developer fails to build the sqldeveloper package
> >> > > with a rather unhelpful message.
> >> > >
> >> > > Terminal output:
> >> > > $ make-sqldeveloper-package -b sqldeveloper
> >> > > sqldeveloper-3.2.20.09.87-no-jre.zip
> >> > >
> >> > > chmod: missing operand after `755'
> >> > > Try `chmod --help' for more information.
> >> > >
> >> > > Omitting the -b parameter has no effect on the output.
> >> >
> >> > As you migth have seen, I uploaded a NMU to a delayed queue. You can
> >> > test the package in [1] if you like.
> >> >
> >> >  [1]: http://ftp-master.debian.org/deferred/
> >>
> >> Hi:
> >>
> >> I've uploaded to mentors.debian.net
> >> <https://mentors.debian.net/package/sqldeveloper-package> version
> >> 0.3.0, that addresses this issue (along all other bugs reported both
> >> on Debian and on Ubuntu).
> >>
> >> I'm not quite sure how will the package be moved to ftp-master (last
> >> time one of the Developers offered to move it).
> >>
> >> Thank you for all the feedback and regards,
> >
> > Thanks for your reply! Should I cancel my NMU from the delayed queue?
> >
> > But please note, the debdiff between 0.2.3+nmu1 and 0.3.0 looks quite
> > big. If you plan an upload (and need sponsoring) could you have a look
> > at [1] for the wheezy freeze_policy?
> >
> > At this stage of the freeze only some important issues, and clearly RC
> > bugs should be addressed to have the package in wheezy; so it might be
> > to late for some of the addressed issues.
> >
> >  [1]: http://release.debian.org/wheezy/freeze_policy.html
> >
> > Please let me know if you have some questions.
> 
> Ciao, Salvatore:
> 
> I wasn't aware of the Wheezy freeze in progress.

Okay!

> 
> The 0.3.0 version I've uploaded to Mentors is my current running
> script, that I've been testing and modifying since my last upload in
> 2009,
> 
> Beside the obvious need to address the RCs, the changes it contains
> are required since otherwise:
> - unaware users wouldn't be able to:find the package to download due
> to dead links;
> - an old deprecated license agreement would be accompanying the
> package instead of a current valid one;
> - old and unavailable methods to get a compatible JDK would be tried and 
> failed;
> 
> These seem not so important for users that are already using the
> package, and know what the changes Oracle introduced in the last two
> years, but for new users it would be stressing and an incentive to not
> using it, supposing it is flawed (and in it's current state it is).
> 
> Beside the above changes all others are related to addressing lintian
> and QA warnings or errors and compliance to standards, not in the
> script itself.
> 
> The large difference between this version and the previous is due to
> the peculiar fact that the script is also a generator of a
> "debianized" package, so in order to the generated package to be
> standard compliant and error free the script has to be edited and the
> above mentioned changes (mainly the license, which is about a third of
> the size of the script), placed inside it.
> 
> I hope I explained my idea, if you feel it's not applicable, please
> let me know so we can try to find a way to do it right.

Yes I understand. Honestly I'm not using sqldeveloper-package but only
helping out on current RC bugs for wheezy.

I have now cancelled my NMU upload. I would now suggest to try the
following: Have a look at the freeze policy and try to adapt the
required changes you think are necessary for the package to have it in
wheezy. As next step, create a debdiff against current version in
testing and then via an unblock request first ask for a (pre-)approval
of the package.

You can keep me in CC, so that if the Release-Team gives their ACK to
it, I can sponsor your upload to the archive.

Does this helps?

Regards,
Salvatore

Attachment: signature.asc
Description: Digital signature

Reply via email to