pakfire --verbose

pakfire --verbose

[Larsen]

[-- Attachment #1: Type: text/plain, Size: 376 bytes --]

Hi,

I wanted to see if I could add a command line parameter to tell pakfire to  
be more verbose, instead of silently putting its output into  
"/var/log/pakfire/update-core-upgrade-##.log".
I have cloned the repository https://github.com/ipfire/pakfire.git but  
cannot find one of the other params (non-interactive, no-colors) in the  
code.

What am I doing wrong?


Lars

Re: pakfire --verbose

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 738 bytes --]

Hey,

what you are looking at there is the source code of Pakfire 3. The code
of the version that is running in IPFire 2 is here:

http://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=src/pakfire;h=48946826ad9888dd39760783268566fe904de70d;hb=HEAD

-Michael

On Fri, 2016-01-22 at 16:13 +0100, Larsen wrote:
> Hi,
> 
> I wanted to see if I could add a command line parameter to tell
> pakfire to  
> be more verbose, instead of silently putting its output into  
> "/var/log/pakfire/update-core-upgrade-##.log".
> I have cloned the repository https://github.com/ipfire/pakfire.git bu
> t  
> cannot find one of the other params (non-interactive, no-colors) in
> the  
> code.
> 
> What am I doing wrong?
> 
> 
> Lars

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: pakfire --verbose

[Larsen]

[-- Attachment #1: Type: text/plain, Size: 981 bytes --]

Ah ok, found it. Thanks!

Will the code from pakfire2 (if I change anything) be used for pakfire3 as  
well?


Lars



On Fri, 22 Jan 2016 16:52:31 +0100, Michael Tremer  
<michael.tremer(a)ipfire.org> wrote:

> Hey,
>
> what you are looking at there is the source code of Pakfire 3. The code
> of the version that is running in IPFire 2 is here:
>
> http://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=src/pakfire;h=48946826ad9888dd39760783268566fe904de70d;hb=HEAD
>
> -Michael
>
> On Fri, 2016-01-22 at 16:13 +0100, Larsen wrote:
>> Hi,
>>
>> I wanted to see if I could add a command line parameter to tell
>> pakfire to
>> be more verbose, instead of silently putting its output into
>> "/var/log/pakfire/update-core-upgrade-##.log".
>> I have cloned the repository https://github.com/ipfire/pakfire.git bu
>> t
>> cannot find one of the other params (non-interactive, no-colors) in
>> the
>> code.
>>
>> What am I doing wrong?
>>
>>
>> Lars

Re: pakfire --verbose

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]

No, that code has been dropped and pakfire was rewritten in C and
Python. So there is no code shared.

-Michael

On Fri, 2016-01-22 at 17:22 +0100, Larsen wrote:
> Ah ok, found it. Thanks!
> 
> Will the code from pakfire2 (if I change anything) be used for
> pakfire3 as  
> well?
> 
> 
> Lars
> 
> 
> 
> On Fri, 22 Jan 2016 16:52:31 +0100, Michael Tremer  
> <michael.tremer(a)ipfire.org> wrote:
> 
> > Hey,
> > 
> > what you are looking at there is the source code of Pakfire 3. The
> > code
> > of the version that is running in IPFire 2 is here:
> > 
> > http://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=src/pakfire;h=4894
> > 6826ad9888dd39760783268566fe904de70d;hb=HEAD
> > 
> > -Michael
> > 
> > On Fri, 2016-01-22 at 16:13 +0100, Larsen wrote:
> > > Hi,
> > > 
> > > I wanted to see if I could add a command line parameter to tell
> > > pakfire to
> > > be more verbose, instead of silently putting its output into
> > > "/var/log/pakfire/update-core-upgrade-##.log".
> > > I have cloned the repository 
> > > https://github.com/ipfire/pakfire.git bu
> > > t
> > > cannot find one of the other params (non-interactive, no-colors)
> > > in
> > > the
> > > code.
> > > 
> > > What am I doing wrong?
> > > 
> > > 
> > > Lars

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: pakfire --verbose

[Larsen]

[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]

Ok, what would be the best way then? I don't want my efforts to be wasted,  
but am certainly not a C coder.


On Fri, 22 Jan 2016 17:23:51 +0100, Michael Tremer  
<michael.tremer(a)ipfire.org> wrote:

> No, that code has been dropped and pakfire was rewritten in C and
> Python. So there is no code shared.
>
> -Michael
>
> On Fri, 2016-01-22 at 17:22 +0100, Larsen wrote:
>> Ah ok, found it. Thanks!
>>
>> Will the code from pakfire2 (if I change anything) be used for
>> pakfire3 as
>> well?
>>
>>
>> Lars
>>
>>
>>
>> On Fri, 22 Jan 2016 16:52:31 +0100, Michael Tremer
>> <michael.tremer(a)ipfire.org> wrote:
>>
>> > Hey,
>> >
>> > what you are looking at there is the source code of Pakfire 3. The
>> > code
>> > of the version that is running in IPFire 2 is here:
>> >
>> > http://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=src/pakfire;h=4894
>> > 6826ad9888dd39760783268566fe904de70d;hb=HEAD
>> >
>> > -Michael
>> >
>> > On Fri, 2016-01-22 at 16:13 +0100, Larsen wrote:
>> > > Hi,
>> > >
>> > > I wanted to see if I could add a command line parameter to tell
>> > > pakfire to
>> > > be more verbose, instead of silently putting its output into
>> > > "/var/log/pakfire/update-core-upgrade-##.log".
>> > > I have cloned the repository
>> > > https://github.com/ipfire/pakfire.git bu
>> > > t
>> > > cannot find one of the other params (non-interactive, no-colors)
>> > > in
>> > > the
>> > > code.
>> > >
>> > > What am I doing wrong?
>> > >
>> > >
>> > > Lars

Re: pakfire --verbose

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]

The best way for doing what?

On Fri, 2016-01-22 at 18:08 +0100, Larsen wrote:
> Ok, what would be the best way then? I don't want my efforts to be
> wasted,  
> but am certainly not a C coder.
> 
> 
> On Fri, 22 Jan 2016 17:23:51 +0100, Michael Tremer  
> <michael.tremer(a)ipfire.org> wrote:
> 
> > No, that code has been dropped and pakfire was rewritten in C and
> > Python. So there is no code shared.
> > 
> > -Michael
> > 
> > On Fri, 2016-01-22 at 17:22 +0100, Larsen wrote:
> > > Ah ok, found it. Thanks!
> > > 
> > > Will the code from pakfire2 (if I change anything) be used for
> > > pakfire3 as
> > > well?
> > > 
> > > 
> > > Lars
> > > 
> > > 
> > > 
> > > On Fri, 22 Jan 2016 16:52:31 +0100, Michael Tremer
> > > <michael.tremer(a)ipfire.org> wrote:
> > > 
> > > > Hey,
> > > > 
> > > > what you are looking at there is the source code of Pakfire 3.
> > > > The
> > > > code
> > > > of the version that is running in IPFire 2 is here:
> > > > 
> > > > http://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=src/pakfire;h=
> > > > 4894
> > > > 6826ad9888dd39760783268566fe904de70d;hb=HEAD
> > > > 
> > > > -Michael
> > > > 
> > > > On Fri, 2016-01-22 at 16:13 +0100, Larsen wrote:
> > > > > Hi,
> > > > > 
> > > > > I wanted to see if I could add a command line parameter to
> > > > > tell
> > > > > pakfire to
> > > > > be more verbose, instead of silently putting its output into
> > > > > "/var/log/pakfire/update-core-upgrade-##.log".
> > > > > I have cloned the repository
> > > > > https://github.com/ipfire/pakfire.git bu
> > > > > t
> > > > > cannot find one of the other params (non-interactive, no
> > > > > -colors)
> > > > > in
> > > > > the
> > > > > code.
> > > > > 
> > > > > What am I doing wrong?
> > > > > 
> > > > > 
> > > > > Lars

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: pakfire --verbose

[Larsen]

[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]

The best way to get this improvement into both versions? Or will pakfire3  
already have such a verbose param?


On Fri, 22 Jan 2016 18:10:58 +0100, Michael Tremer  
<michael.tremer(a)ipfire.org> wrote:

> The best way for doing what?
>
> On Fri, 2016-01-22 at 18:08 +0100, Larsen wrote:
>> Ok, what would be the best way then? I don't want my efforts to be
>> wasted,
>> but am certainly not a C coder.
>>
>>
>> On Fri, 22 Jan 2016 17:23:51 +0100, Michael Tremer
>> <michael.tremer(a)ipfire.org> wrote:
>>
>> > No, that code has been dropped and pakfire was rewritten in C and
>> > Python. So there is no code shared.
>> >
>> > -Michael
>> >
>> > On Fri, 2016-01-22 at 17:22 +0100, Larsen wrote:
>> > > Ah ok, found it. Thanks!
>> > >
>> > > Will the code from pakfire2 (if I change anything) be used for
>> > > pakfire3 as
>> > > well?
>> > >
>> > >
>> > > Lars
>> > >
>> > >
>> > >
>> > > On Fri, 22 Jan 2016 16:52:31 +0100, Michael Tremer
>> > > <michael.tremer(a)ipfire.org> wrote:
>> > >
>> > > > Hey,
>> > > >
>> > > > what you are looking at there is the source code of Pakfire 3.
>> > > > The
>> > > > code
>> > > > of the version that is running in IPFire 2 is here:
>> > > >
>> > > > http://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=src/pakfire;h=
>> > > > 4894
>> > > > 6826ad9888dd39760783268566fe904de70d;hb=HEAD
>> > > >
>> > > > -Michael
>> > > >
>> > > > On Fri, 2016-01-22 at 16:13 +0100, Larsen wrote:
>> > > > > Hi,
>> > > > >
>> > > > > I wanted to see if I could add a command line parameter to
>> > > > > tell
>> > > > > pakfire to
>> > > > > be more verbose, instead of silently putting its output into
>> > > > > "/var/log/pakfire/update-core-upgrade-##.log".
>> > > > > I have cloned the repository
>> > > > > https://github.com/ipfire/pakfire.git bu
>> > > > > t
>> > > > > cannot find one of the other params (non-interactive, no
>> > > > > -colors)
>> > > > > in
>> > > > > the
>> > > > > code.
>> > > > >
>> > > > > What am I doing wrong?
>> > > > >
>> > > > >
>> > > > > Lars

Re: pakfire --verbose

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 2575 bytes --]

Pakfire 3 works very different. So there is verbose output.

You can download the latest image to from over here to have a look:
  http://people.ipfire.org/~stevee/IPFire_3.x/VM-Images/20151101/x86_64/

-Michael

On Fri, 2016-01-22 at 18:48 +0100, Larsen wrote:
> The best way to get this improvement into both versions? Or will
> pakfire3  
> already have such a verbose param?
> 
> 
> On Fri, 22 Jan 2016 18:10:58 +0100, Michael Tremer  
> <michael.tremer(a)ipfire.org> wrote:
> 
> > The best way for doing what?
> > 
> > On Fri, 2016-01-22 at 18:08 +0100, Larsen wrote:
> > > Ok, what would be the best way then? I don't want my efforts to
> > > be
> > > wasted,
> > > but am certainly not a C coder.
> > > 
> > > 
> > > On Fri, 22 Jan 2016 17:23:51 +0100, Michael Tremer
> > > <michael.tremer(a)ipfire.org> wrote:
> > > 
> > > > No, that code has been dropped and pakfire was rewritten in C
> > > > and
> > > > Python. So there is no code shared.
> > > > 
> > > > -Michael
> > > > 
> > > > On Fri, 2016-01-22 at 17:22 +0100, Larsen wrote:
> > > > > Ah ok, found it. Thanks!
> > > > > 
> > > > > Will the code from pakfire2 (if I change anything) be used
> > > > > for
> > > > > pakfire3 as
> > > > > well?
> > > > > 
> > > > > 
> > > > > Lars
> > > > > 
> > > > > 
> > > > > 
> > > > > On Fri, 22 Jan 2016 16:52:31 +0100, Michael Tremer
> > > > > <michael.tremer(a)ipfire.org> wrote:
> > > > > 
> > > > > > Hey,
> > > > > > 
> > > > > > what you are looking at there is the source code of Pakfire
> > > > > > 3.
> > > > > > The
> > > > > > code
> > > > > > of the version that is running in IPFire 2 is here:
> > > > > > 
> > > > > > http://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=src/pakfir
> > > > > > e;h=
> > > > > > 4894
> > > > > > 6826ad9888dd39760783268566fe904de70d;hb=HEAD
> > > > > > 
> > > > > > -Michael
> > > > > > 
> > > > > > On Fri, 2016-01-22 at 16:13 +0100, Larsen wrote:
> > > > > > > Hi,
> > > > > > > 
> > > > > > > I wanted to see if I could add a command line parameter
> > > > > > > to
> > > > > > > tell
> > > > > > > pakfire to
> > > > > > > be more verbose, instead of silently putting its output
> > > > > > > into
> > > > > > > "/var/log/pakfire/update-core-upgrade-##.log".
> > > > > > > I have cloned the repository
> > > > > > > https://github.com/ipfire/pakfire.git bu
> > > > > > > t
> > > > > > > cannot find one of the other params (non-interactive, no
> > > > > > > -colors)
> > > > > > > in
> > > > > > > the
> > > > > > > code.
> > > > > > > 
> > > > > > > What am I doing wrong?
> > > > > > > 
> > > > > > > 
> > > > > > > Lars

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: pakfire --verbose

[Larsen]

[-- Attachment #1: Type: text/plain, Size: 2945 bytes --]

I checked the code, but as update.sh is called there is no easy way or no  
way I know of to get this done with pakfire2.
And as pakfire3 already has verbose output, there also is no real need for  
this.


Lars


On Fri, 22 Jan 2016 19:01:15 +0100, Michael Tremer  
<michael.tremer(a)ipfire.org> wrote:

> Pakfire 3 works very different. So there is verbose output.
>
> You can download the latest image to from over here to have a look:
>   http://people.ipfire.org/~stevee/IPFire_3.x/VM-Images/20151101/x86_64/
>
> -Michael
>
> On Fri, 2016-01-22 at 18:48 +0100, Larsen wrote:
>> The best way to get this improvement into both versions? Or will
>> pakfire3
>> already have such a verbose param?
>>
>>
>> On Fri, 22 Jan 2016 18:10:58 +0100, Michael Tremer
>> <michael.tremer(a)ipfire.org> wrote:
>>
>> > The best way for doing what?
>> >
>> > On Fri, 2016-01-22 at 18:08 +0100, Larsen wrote:
>> > > Ok, what would be the best way then? I don't want my efforts to
>> > > be
>> > > wasted,
>> > > but am certainly not a C coder.
>> > >
>> > >
>> > > On Fri, 22 Jan 2016 17:23:51 +0100, Michael Tremer
>> > > <michael.tremer(a)ipfire.org> wrote:
>> > >
>> > > > No, that code has been dropped and pakfire was rewritten in C
>> > > > and
>> > > > Python. So there is no code shared.
>> > > >
>> > > > -Michael
>> > > >
>> > > > On Fri, 2016-01-22 at 17:22 +0100, Larsen wrote:
>> > > > > Ah ok, found it. Thanks!
>> > > > >
>> > > > > Will the code from pakfire2 (if I change anything) be used
>> > > > > for
>> > > > > pakfire3 as
>> > > > > well?
>> > > > >
>> > > > >
>> > > > > Lars
>> > > > >
>> > > > >
>> > > > >
>> > > > > On Fri, 22 Jan 2016 16:52:31 +0100, Michael Tremer
>> > > > > <michael.tremer(a)ipfire.org> wrote:
>> > > > >
>> > > > > > Hey,
>> > > > > >
>> > > > > > what you are looking at there is the source code of Pakfire
>> > > > > > 3.
>> > > > > > The
>> > > > > > code
>> > > > > > of the version that is running in IPFire 2 is here:
>> > > > > >
>> > > > > > http://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=src/pakfir
>> > > > > > e;h=
>> > > > > > 4894
>> > > > > > 6826ad9888dd39760783268566fe904de70d;hb=HEAD
>> > > > > >
>> > > > > > -Michael
>> > > > > >
>> > > > > > On Fri, 2016-01-22 at 16:13 +0100, Larsen wrote:
>> > > > > > > Hi,
>> > > > > > >
>> > > > > > > I wanted to see if I could add a command line parameter
>> > > > > > > to
>> > > > > > > tell
>> > > > > > > pakfire to
>> > > > > > > be more verbose, instead of silently putting its output
>> > > > > > > into
>> > > > > > > "/var/log/pakfire/update-core-upgrade-##.log".
>> > > > > > > I have cloned the repository
>> > > > > > > https://github.com/ipfire/pakfire.git bu
>> > > > > > > t
>> > > > > > > cannot find one of the other params (non-interactive, no
>> > > > > > > -colors)
>> > > > > > > in
>> > > > > > > the
>> > > > > > > code.
>> > > > > > >
>> > > > > > > What am I doing wrong?
>> > > > > > >
>> > > > > > >
>> > > > > > > Lars