dropline-gnome-devel — Discuss the development of Dropline GNOME

Re: [DLG-dev] Geary 3.38.1

[Sasa O. <ca...@gm...>]

I need to fix up DBS to be able to build evolution-data-server and
evolution. This is on my TODO list.
Rgds
Saxa

On Fri, Jan 1, 2021 at 1:13 AM Nathaniel Russell
<nat...@gm...> wrote:
>
> Looking at the root cause:
> installed       slackware64     icu4c-68.2-x86_64-1
> installed     gnome          evolution-data-server-3.38.0-x86_64-1dl
> The libedataserver-1.2.so.25 was installed with evolution-data-server-3.38.0-x86_64-1d.
> I tried to recompile folk and geary but I was unable to.
>
> On Thu, Dec 31, 2020 at 6:05 PM Sasa Ostrouska <ca...@gm...> wrote:
>>
>> Thanks for the headsup, I am travelling and will be back after Jan.10
>> to be able to fix anything.
>> Enjoy guys.
>> Rgds
>> Saxa
>>
>> On Wed, Dec 30, 2020 at 3:09 AM Nathaniel Russell
>> <nat...@gm...> wrote:
>> >
>> > nate@Dad:/usr/bin$ geary
>> > *[wrn] 20:06:23.0597 folks:backend-store.vala:768: Failed to load module from path '/usr/lib64/folks/46/backends/eds/eds.so': libedataserver-1.2.so.24: cannot open shared object file: No such file or directory
>> > *[wrn] 20:06:23.0602 folks:backend-store.vala:768: Failed to load module from path '/usr/lib64/folks/46/backends/ofono/ofono.so': libicui18n.so.67: cannot open shared object file: No such file or directory
>> > *[wrn] 20:06:23.0606 folks:backend-store.vala:768: Failed to load module from path '/usr/lib64/folks/46/backends/bluez/bluez.so': libicui18n.so.67: cannot open shared object file: No such file or directory
>> > *[wrn] 20:06:23.0633 geary:application-certificate-manager.vala:74: No GCR slot URIs found, GCR certificate pinning unavailable
>> > *[wrn] 20:06:23.0696 folks:backend-store.vala:435: Error preparing Backend 'telepathy': The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files
>> > *[wrn] 20:06:23.0696 folks:Failed to find primary PersonaStore with type ID 'eds' and ID 'system-address-book'.
>> > Individuals will not be linked properly and creating new links between Personas will not work.
>> > The configured primary PersonaStore's backend may not be installed. If you are unsure, check with your distribution.
>> > *[wrn] 20:06:23.0706 geary:application-client.vala:945: Error creating controller: The name org.freedesktop.secrets was not provided by any .service files
>> > nate@Dad:/usr/bin$
>> > _______________________________________________
>> > Dropline-gnome-devel mailing list
>> > Dro...@li...
>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>
>>
>> _______________________________________________
>> Dropline-gnome-devel mailing list
>> Dro...@li...
>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

Re: [DLG-dev] Tracker-Miner Segfault

[Sasa O. <ca...@gm...>]

Thanks for the headsup, I will check that on mine machine next week
and confirm it. Most probably some of the latest updates
from slackware or gnome breaks this. But you can also open a bug on
the tracker gnome gitlab.
https://gitlab.gnome.org/GNOME/tracker/-/issues

On Wed, Jan 6, 2021 at 4:31 AM Nathaniel Russell
<nat...@gm...> wrote:
>
> [ 3085.156447] tracker-miner-f[4845]: segfault at 0 ip 00007f34d0b8a7cf sp 00007ffc33ef5000 error 4 in libtracker-miner-3.0.so[7f34d0b6f000+23000]
> [ 3085.156467] Code: 48 89 c7 e8 d3 53 fe ff c9 c3 55 48 89 e5 48 83 ec 20 48 89 7d e8 48 8b 45 e8 48 89 c7 e8 a9 5d fe ff 48 89 45 f8 48 8b 45 f8 <48> 8b 00 c9 c3 55 48 89 e5 48 83 ec 50 48 89 7d c8 48 89 75 c0 48
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[DLG-dev] Tracker-Miner Segfault

[Nathaniel R. <nat...@gm...>]

[ 3085.156447] tracker-miner-f[4845]: segfault at 0 ip 00007f34d0b8a7cf sp
00007ffc33ef5000 error 4 in libtracker-miner-3.0.so[7f34d0b6f000+23000]
[ 3085.156467] Code: 48 89 c7 e8 d3 53 fe ff c9 c3 55 48 89 e5 48 83 ec 20
48 89 7d e8 48 8b 45 e8 48 89 c7 e8 a9 5d fe ff 48 89 45 f8 48 8b 45 f8
<48> 8b 00 c9 c3 55 48 89 e5 48 83 ec 50 48 89 7d c8 48 89 75 c0 48

Re: [DLG-dev] Geary 3.38.1

[Nathaniel R. <nat...@gm...>]

Looking at the root cause:
installed       slackware64     icu4c-68.2-x86_64-1
installed     gnome          evolution-data-server-3.38.0-x86_64-1dl
The libedataserver-1.2.so.25 was installed with
evolution-data-server-3.38.0-x86_64-1d.
I tried to recompile folk and geary but I was unable to.

On Thu, Dec 31, 2020 at 6:05 PM Sasa Ostrouska <ca...@gm...> wrote:

> Thanks for the headsup, I am travelling and will be back after Jan.10
> to be able to fix anything.
> Enjoy guys.
> Rgds
> Saxa
>
> On Wed, Dec 30, 2020 at 3:09 AM Nathaniel Russell
> <nat...@gm...> wrote:
> >
> > nate@Dad:/usr/bin$ geary
> > *[wrn] 20:06:23.0597 folks:backend-store.vala:768: Failed to load module
> from path '/usr/lib64/folks/46/backends/eds/eds.so':
> libedataserver-1.2.so.24: cannot open shared object file: No such file or
> directory
> > *[wrn] 20:06:23.0602 folks:backend-store.vala:768: Failed to load module
> from path '/usr/lib64/folks/46/backends/ofono/ofono.so': libicui18n.so.67:
> cannot open shared object file: No such file or directory
> > *[wrn] 20:06:23.0606 folks:backend-store.vala:768: Failed to load module
> from path '/usr/lib64/folks/46/backends/bluez/bluez.so': libicui18n.so.67:
> cannot open shared object file: No such file or directory
> > *[wrn] 20:06:23.0633 geary:application-certificate-manager.vala:74: No
> GCR slot URIs found, GCR certificate pinning unavailable
> > *[wrn] 20:06:23.0696 folks:backend-store.vala:435: Error preparing
> Backend 'telepathy': The name org.freedesktop.Telepathy.AccountManager was
> not provided by any .service files
> > *[wrn] 20:06:23.0696 folks:Failed to find primary PersonaStore with type
> ID 'eds' and ID 'system-address-book'.
> > Individuals will not be linked properly and creating new links between
> Personas will not work.
> > The configured primary PersonaStore's backend may not be installed. If
> you are unsure, check with your distribution.
> > *[wrn] 20:06:23.0706 geary:application-client.vala:945: Error creating
> controller: The name org.freedesktop.secrets was not provided by any
> .service files
> > nate@Dad:/usr/bin$
> > _______________________________________________
> > Dropline-gnome-devel mailing list
> > Dro...@li...
> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
>
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>

Re: [DLG-dev] Geary 3.38.1

[Sasa O. <ca...@gm...>]

Thanks for the headsup, I am travelling and will be back after Jan.10
to be able to fix anything.
Enjoy guys.
Rgds
Saxa

On Wed, Dec 30, 2020 at 3:09 AM Nathaniel Russell
<nat...@gm...> wrote:
>
> nate@Dad:/usr/bin$ geary
> *[wrn] 20:06:23.0597 folks:backend-store.vala:768: Failed to load module from path '/usr/lib64/folks/46/backends/eds/eds.so': libedataserver-1.2.so.24: cannot open shared object file: No such file or directory
> *[wrn] 20:06:23.0602 folks:backend-store.vala:768: Failed to load module from path '/usr/lib64/folks/46/backends/ofono/ofono.so': libicui18n.so.67: cannot open shared object file: No such file or directory
> *[wrn] 20:06:23.0606 folks:backend-store.vala:768: Failed to load module from path '/usr/lib64/folks/46/backends/bluez/bluez.so': libicui18n.so.67: cannot open shared object file: No such file or directory
> *[wrn] 20:06:23.0633 geary:application-certificate-manager.vala:74: No GCR slot URIs found, GCR certificate pinning unavailable
> *[wrn] 20:06:23.0696 folks:backend-store.vala:435: Error preparing Backend 'telepathy': The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files
> *[wrn] 20:06:23.0696 folks:Failed to find primary PersonaStore with type ID 'eds' and ID 'system-address-book'.
> Individuals will not be linked properly and creating new links between Personas will not work.
> The configured primary PersonaStore's backend may not be installed. If you are unsure, check with your distribution.
> *[wrn] 20:06:23.0706 geary:application-client.vala:945: Error creating controller: The name org.freedesktop.secrets was not provided by any .service files
> nate@Dad:/usr/bin$
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[DLG-dev] Geary 3.38.1

[Nathaniel R. <nat...@gm...>]

nate@Dad:/usr/bin$ geary
*[wrn] 20:06:23.0597 folks:backend-store.vala:768: Failed to load module
from path '/usr/lib64/folks/46/backends/eds/eds.so':
libedataserver-1.2.so.24: cannot open shared object file: No such file or
directory
*[wrn] 20:06:23.0602 folks:backend-store.vala:768: Failed to load module
from path '/usr/lib64/folks/46/backends/ofono/ofono.so': libicui18n.so.67:
cannot open shared object file: No such file or directory
*[wrn] 20:06:23.0606 folks:backend-store.vala:768: Failed to load module
from path '/usr/lib64/folks/46/backends/bluez/bluez.so': libicui18n.so.67:
cannot open shared object file: No such file or directory
*[wrn] 20:06:23.0633 geary:application-certificate-manager.vala:74: No GCR
slot URIs found, GCR certificate pinning unavailable
*[wrn] 20:06:23.0696 folks:backend-store.vala:435: Error preparing Backend
'telepathy': The name org.freedesktop.Telepathy.AccountManager was not
provided by any .service files
*[wrn] 20:06:23.0696 folks:Failed to find primary PersonaStore with type ID
'eds' and ID 'system-address-book'.
Individuals will not be linked properly and creating new links between
Personas will not work.
The configured primary PersonaStore's backend may not be installed. If you
are unsure, check with your distribution.
*[wrn] 20:06:23.0706 geary:application-client.vala:945: Error creating
controller: The name org.freedesktop.secrets was not provided by any
.service files
nate@Dad:/usr/bin$

Re: [DLG-dev] Slackpkg+ Complaince

[Sasa O. <ca...@gm...>]

Ok, sorry for my silence, but still quite busy with my work. Meanwhile
I keep struggling in my head on how things should work.
One thing would be to have an automated upload script, or a script
which could generate the repo, and automagically updated the
ChangeLog in the repository.

This would mean something like this:

./upload_new_packages.sh
Password: ******

And that would do all the needed work, which is:
1. Upload the newly built packages from $DLG_REPO (/tmp/DLG/packages)
2. Create the changelog file
3. Create the signature or other files needed for slackpkg to work.

Rgds
Saxa

On Tue, Dec 8, 2020 at 12:23 AM Nathaniel Russell
<nat...@gm...> wrote:
>
> I can deal with that i like it.
>
> On Mon, Dec 7, 2020 at 5:21 PM Sasa Ostrouska <ca...@gm...> wrote:
>>
>> Sorry for my silence but busy with my work. Basically what I mean is
>> something like this:
>>
>> Changelog for repository
>> For detailed changes see each individual package ChangeLog in
>> /usr/src/dropline-build-system/scripts/$package_name
>>
>> 07-12-2020 x86-64 repo updated with following packages:
>> package 1
>> package 2
>> etc....
>>
>> Thats it.
>> Rgds
>> Saxa
>>
>> On Fri, Dec 4, 2020 at 10:11 PM Nathaniel Russell
>> <nat...@gm...> wrote:
>> >
>> > Could u attach a changelog with what u are saying please so i have a better understanding as to how u r thinking it should be??
>> >
>> > On Fri, Dec 4, 2020 at 9:24 AM Sasa Ostrouska <ca...@gm...> wrote:
>> >>
>> >> Sure, we can mention to see the individual changelogs in
>> >> /usr/src/dropline-build-system/scripts/$PACKAGENAME
>> >>
>> >> Also we can use the Changelog to reflect the repository tree update
>> >> date and package name.
>> >>
>> >> On Fri, Dec 4, 2020 at 12:55 AM Nathaniel Russell
>> >> <nat...@gm...> wrote:
>> >> >
>> >> > So then would we out something in the changelog that would refer them to the individual changelog???
>> >> >
>> >> > On Thu, Dec 3, 2020 at 5:53 PM Sasa Ostrouska <ca...@gm...> wrote:
>> >> >>
>> >> >> On Fri, Dec 4, 2020 at 12:49 AM Nathaniel Russell
>> >> >> <nat...@gm...> wrote:
>> >> >> >
>> >> >> > So then how would u like to do the changelog ????
>> >> >> I do think that the empty one can work for the repo, and leave the
>> >> >> ones we have where they are.
>> >> >>
>> >> >> >
>> >> >> > On Thu, Dec 3, 2020 at 5:42 PM Sasa Ostrouska <ca...@gm...> wrote:
>> >> >> >>
>> >> >> >> On Thu, Dec 3, 2020 at 11:50 PM Nathaniel Russell
>> >> >> >> <nat...@gm...> wrote:
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > That would be fine if u want I can do the changelog and u could keep doing your version of a changlog within the packages.
>> >> >> >> The thing is that all that stuff should go into DBS so it can be
>> >> >> >> automated. But again, I think is no sense to have twice the same
>> >> >> >> information
>> >> >> >> listed in 2 places, and then be more mistake prone.
>> >> >> >>
>> >> >> >> Rgds
>> >> >> >> Saxa
>> >> >> >> >
>> >> >> >> > On Thu, Dec 3, 2020 at 4:36 PM Sasa Ostrouska <ca...@gm...> wrote:
>> >> >> >> >>
>> >> >> >> >> On Thu, Dec 3, 2020 at 9:23 PM Tomáš Bažant <tom...@gm...> wrote:
>> >> >> >> >> >
>> >> >> >> >> > hi
>> >> >> >> >> > you're correct, it should be the repo-owner's key, definitely. but signing them requires the private part of the gpg key imho, so.......you cant sign it with someone else's key, but maybe i'm wrong here.
>> >> >> >> >> > t.
>> >> >> >> >> >
>> >> >> >> >> > čt 3. 12. 2020 v 20:25 odesílatel Nathaniel Russell <nat...@gm...> napsal:
>> >> >> >> >> >>
>> >> >> >> >> >> But you dont want gen_repos to use ur gpf key these are majntained by Sasa not us that is y im asking him for his gpg key to sign all packages.
>> >> >> >> >>
>> >> >> >> >> Ok, I can do a public key and a private one for droplinegnome project
>> >> >> >> >> and we could share that then.
>> >> >> >> >>
>> >> >> >> >> Rgds
>> >> >> >> >> Saxa
>> >> >> >> >> >>
>> >> >> >> >> >> On Thu, Dec 3, 2020 at 12:11 PM Tomáš Bažant <tom...@gm...> wrote:
>> >> >> >> >> >>>
>> >> >> >> >> >>> It is always best to have a valid changelog, no donut about it. The gpg thing - the `gen_repos_files.sh` script signs the packages with your GPG key (see notes at project's sf.net wiki).
>> >> >> >> >> >>> If you want to run `slackpkg update` on a repo whose packages are not signed, then you need to update the `/etc/slackpkg/slackpkgplus.conf` file and set `STRICTGPG=on`
>> >> >> >> >> >>>
>> >> >> >> >> >>> čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <nat...@gm...> napsal:
>> >> >> >> >> >>>>
>> >> >> >> >> >>>> Acutally if you run the gen_repo script of Eric’s it ends up making a Blank Changelog.txt file so I would say it is.
>> >> >> >> >> >>>>
>> >> >> >> >> >>>> When you have all the files you need running slackpkg update barfs on GPG-KEY for Gnome i will send u a picture 2nite.
>> >> >> >> >> >>>>
>> >> >> >> >> >>>> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <ca...@gm...> wrote:
>> >> >> >> >> >>>>>
>> >> >> >> >> >>>>> Out of curiosity, is the Changelog.txt obligatory ?
>> >> >> >> >> >>>>>
>> >> >> >> >> >>>>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
>> >> >> >> >> >>>>> <nat...@gm...> wrote:
>> >> >> >> >> >>>>> >
>> >> >> >> >> >>>>> > This is a start for the slackpkg+ repo files I still have to work on the Changelog and get everything in order. When I run my slackpkg update it is barfing on a GPG-KEY for the dropline gnome repo.
>> >> >> >> >> >>>>> > Is there any way you have this Key on hand so that I can continue to update and the files and help with making this slackpkg+ complaint?
>> >> >> >> >> >>>>> > _______________________________________________
>> >> >> >> >> >>>>> > Dropline-gnome-devel mailing list
>> >> >> >> >> >>>>> > Dro...@li...
>> >> >> >> >> >>>>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >> >> >>>>>
>> >> >> >> >> >>>>>
>> >> >> >> >> >>>>> _______________________________________________
>> >> >> >> >> >>>>> Dropline-gnome-devel mailing list
>> >> >> >> >> >>>>> Dro...@li...
>> >> >> >> >> >>>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >> >> >>>>
>> >> >> >> >> >>>> --
>> >> >> >> >> >>>> Nathaniel & LeAnna Russell
>> >> >> >> >> >>>> _______________________________________________
>> >> >> >> >> >>>> Dropline-gnome-devel mailing list
>> >> >> >> >> >>>> Dro...@li...
>> >> >> >> >> >>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >> >> >>>
>> >> >> >> >> >>> _______________________________________________
>> >> >> >> >> >>> Dropline-gnome-devel mailing list
>> >> >> >> >> >>> Dro...@li...
>> >> >> >> >> >>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >> >> >>
>> >> >> >> >> >> --
>> >> >> >> >> >> Nathaniel & LeAnna Russell
>> >> >> >> >> >> _______________________________________________
>> >> >> >> >> >> Dropline-gnome-devel mailing list
>> >> >> >> >> >> Dro...@li...
>> >> >> >> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >> >> >
>> >> >> >> >> > _______________________________________________
>> >> >> >> >> > Dropline-gnome-devel mailing list
>> >> >> >> >> > Dro...@li...
>> >> >> >> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> _______________________________________________
>> >> >> >> >> Dropline-gnome-devel mailing list
>> >> >> >> >> Dro...@li...
>> >> >> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Nathaniel & LeAnna Russell
>> >> >> >> > _______________________________________________
>> >> >> >> > Dropline-gnome-devel mailing list
>> >> >> >> > Dro...@li...
>> >> >> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >>
>> >> >> >>
>> >> >> >> _______________________________________________
>> >> >> >> Dropline-gnome-devel mailing list
>> >> >> >> Dro...@li...
>> >> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >
>> >> >> > --
>> >> >> > Nathaniel & LeAnna Russell
>> >> >> > _______________________________________________
>> >> >> > Dropline-gnome-devel mailing list
>> >> >> > Dro...@li...
>> >> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> Dropline-gnome-devel mailing list
>> >> >> Dro...@li...
>> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >
>> >> > --
>> >> > Nathaniel & LeAnna Russell
>> >> > _______________________________________________
>> >> > Dropline-gnome-devel mailing list
>> >> > Dro...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >>
>> >>
>> >> _______________________________________________
>> >> Dropline-gnome-devel mailing list
>> >> Dro...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >
>> > --
>> > Nathaniel & LeAnna Russell
>> > _______________________________________________
>> > Dropline-gnome-devel mailing list
>> > Dro...@li...
>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>
>>
>> _______________________________________________
>> Dropline-gnome-devel mailing list
>> Dro...@li...
>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
> --
> Nathaniel & LeAnna Russell
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

Re: [DLG-dev] Slackpkg+ Complaince

[Nathaniel R. <nat...@gm...>]

I can deal with that i like it.

On Mon, Dec 7, 2020 at 5:21 PM Sasa Ostrouska <ca...@gm...> wrote:

> Sorry for my silence but busy with my work. Basically what I mean is
> something like this:
>
> Changelog for repository
> For detailed changes see each individual package ChangeLog in
> /usr/src/dropline-build-system/scripts/$package_name
>
> 07-12-2020 x86-64 repo updated with following packages:
> package 1
> package 2
> etc....
>
> Thats it.
> Rgds
> Saxa
>
> On Fri, Dec 4, 2020 at 10:11 PM Nathaniel Russell
> <nat...@gm...> wrote:
> >
> > Could u attach a changelog with what u are saying please so i have a
> better understanding as to how u r thinking it should be??
> >
> > On Fri, Dec 4, 2020 at 9:24 AM Sasa Ostrouska <ca...@gm...> wrote:
> >>
> >> Sure, we can mention to see the individual changelogs in
> >> /usr/src/dropline-build-system/scripts/$PACKAGENAME
> >>
> >> Also we can use the Changelog to reflect the repository tree update
> >> date and package name.
> >>
> >> On Fri, Dec 4, 2020 at 12:55 AM Nathaniel Russell
> >> <nat...@gm...> wrote:
> >> >
> >> > So then would we out something in the changelog that would refer them
> to the individual changelog???
> >> >
> >> > On Thu, Dec 3, 2020 at 5:53 PM Sasa Ostrouska <ca...@gm...>
> wrote:
> >> >>
> >> >> On Fri, Dec 4, 2020 at 12:49 AM Nathaniel Russell
> >> >> <nat...@gm...> wrote:
> >> >> >
> >> >> > So then how would u like to do the changelog ????
> >> >> I do think that the empty one can work for the repo, and leave the
> >> >> ones we have where they are.
> >> >>
> >> >> >
> >> >> > On Thu, Dec 3, 2020 at 5:42 PM Sasa Ostrouska <ca...@gm...>
> wrote:
> >> >> >>
> >> >> >> On Thu, Dec 3, 2020 at 11:50 PM Nathaniel Russell
> >> >> >> <nat...@gm...> wrote:
> >> >> >> >
> >> >> >> >
> >> >> >> > That would be fine if u want I can do the changelog and u could
> keep doing your version of a changlog within the packages.
> >> >> >> The thing is that all that stuff should go into DBS so it can be
> >> >> >> automated. But again, I think is no sense to have twice the same
> >> >> >> information
> >> >> >> listed in 2 places, and then be more mistake prone.
> >> >> >>
> >> >> >> Rgds
> >> >> >> Saxa
> >> >> >> >
> >> >> >> > On Thu, Dec 3, 2020 at 4:36 PM Sasa Ostrouska <ca...@gm...>
> wrote:
> >> >> >> >>
> >> >> >> >> On Thu, Dec 3, 2020 at 9:23 PM Tomáš Bažant <
> tom...@gm...> wrote:
> >> >> >> >> >
> >> >> >> >> > hi
> >> >> >> >> > you're correct, it should be the repo-owner's key,
> definitely. but signing them requires the private part of the gpg key imho,
> so.......you cant sign it with someone else's key, but maybe i'm wrong here.
> >> >> >> >> > t.
> >> >> >> >> >
> >> >> >> >> > čt 3. 12. 2020 v 20:25 odesílatel Nathaniel Russell <
> nat...@gm...> napsal:
> >> >> >> >> >>
> >> >> >> >> >> But you dont want gen_repos to use ur gpf key these are
> majntained by Sasa not us that is y im asking him for his gpg key to sign
> all packages.
> >> >> >> >>
> >> >> >> >> Ok, I can do a public key and a private one for droplinegnome
> project
> >> >> >> >> and we could share that then.
> >> >> >> >>
> >> >> >> >> Rgds
> >> >> >> >> Saxa
> >> >> >> >> >>
> >> >> >> >> >> On Thu, Dec 3, 2020 at 12:11 PM Tomáš Bažant <
> tom...@gm...> wrote:
> >> >> >> >> >>>
> >> >> >> >> >>> It is always best to have a valid changelog, no donut
> about it. The gpg thing - the `gen_repos_files.sh` script signs the
> packages with your GPG key (see notes at project's sf.net wiki).
> >> >> >> >> >>> If you want to run `slackpkg update` on a repo whose
> packages are not signed, then you need to update the
> `/etc/slackpkg/slackpkgplus.conf` file and set `STRICTGPG=on`
> >> >> >> >> >>>
> >> >> >> >> >>> čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <
> nat...@gm...> napsal:
> >> >> >> >> >>>>
> >> >> >> >> >>>> Acutally if you run the gen_repo script of Eric’s it ends
> up making a Blank Changelog.txt file so I would say it is.
> >> >> >> >> >>>>
> >> >> >> >> >>>> When you have all the files you need running slackpkg
> update barfs on GPG-KEY for Gnome i will send u a picture 2nite.
> >> >> >> >> >>>>
> >> >> >> >> >>>> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <
> ca...@gm...> wrote:
> >> >> >> >> >>>>>
> >> >> >> >> >>>>> Out of curiosity, is the Changelog.txt obligatory ?
> >> >> >> >> >>>>>
> >> >> >> >> >>>>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
> >> >> >> >> >>>>> <nat...@gm...> wrote:
> >> >> >> >> >>>>> >
> >> >> >> >> >>>>> > This is a start for the slackpkg+ repo files I still
> have to work on the Changelog and get everything in order. When I run my
> slackpkg update it is barfing on a GPG-KEY for the dropline gnome repo.
> >> >> >> >> >>>>> > Is there any way you have this Key on hand so that I
> can continue to update and the files and help with making this slackpkg+
> complaint?
> >> >> >> >> >>>>> > _______________________________________________
> >> >> >> >> >>>>> > Dropline-gnome-devel mailing list
> >> >> >> >> >>>>> > Dro...@li...
> >> >> >> >> >>>>> >
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >> >> >>>>>
> >> >> >> >> >>>>>
> >> >> >> >> >>>>> _______________________________________________
> >> >> >> >> >>>>> Dropline-gnome-devel mailing list
> >> >> >> >> >>>>> Dro...@li...
> >> >> >> >> >>>>>
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >> >> >>>>
> >> >> >> >> >>>> --
> >> >> >> >> >>>> Nathaniel & LeAnna Russell
> >> >> >> >> >>>> _______________________________________________
> >> >> >> >> >>>> Dropline-gnome-devel mailing list
> >> >> >> >> >>>> Dro...@li...
> >> >> >> >> >>>>
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >> >> >>>
> >> >> >> >> >>> _______________________________________________
> >> >> >> >> >>> Dropline-gnome-devel mailing list
> >> >> >> >> >>> Dro...@li...
> >> >> >> >> >>>
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Nathaniel & LeAnna Russell
> >> >> >> >> >> _______________________________________________
> >> >> >> >> >> Dropline-gnome-devel mailing list
> >> >> >> >> >> Dro...@li...
> >> >> >> >> >>
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >> >> >
> >> >> >> >> > _______________________________________________
> >> >> >> >> > Dropline-gnome-devel mailing list
> >> >> >> >> > Dro...@li...
> >> >> >> >> >
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> _______________________________________________
> >> >> >> >> Dropline-gnome-devel mailing list
> >> >> >> >> Dro...@li...
> >> >> >> >>
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >> >
> >> >> >> > --
> >> >> >> > Nathaniel & LeAnna Russell
> >> >> >> > _______________________________________________
> >> >> >> > Dropline-gnome-devel mailing list
> >> >> >> > Dro...@li...
> >> >> >> >
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >>
> >> >> >>
> >> >> >> _______________________________________________
> >> >> >> Dropline-gnome-devel mailing list
> >> >> >> Dro...@li...
> >> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >
> >> >> > --
> >> >> > Nathaniel & LeAnna Russell
> >> >> > _______________________________________________
> >> >> > Dropline-gnome-devel mailing list
> >> >> > Dro...@li...
> >> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Dropline-gnome-devel mailing list
> >> >> Dro...@li...
> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >
> >> > --
> >> > Nathaniel & LeAnna Russell
> >> > _______________________________________________
> >> > Dropline-gnome-devel mailing list
> >> > Dro...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >>
> >>
> >> _______________________________________________
> >> Dropline-gnome-devel mailing list
> >> Dro...@li...
> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >
> > --
> > Nathaniel & LeAnna Russell
> > _______________________________________________
> > Dropline-gnome-devel mailing list
> > Dro...@li...
> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
>
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
-- 
Nathaniel & LeAnna Russell

Re: [DLG-dev] Slackpkg+ Complaince

[Sasa O. <ca...@gm...>]

Sorry for my silence but busy with my work. Basically what I mean is
something like this:

Changelog for repository
For detailed changes see each individual package ChangeLog in
/usr/src/dropline-build-system/scripts/$package_name

07-12-2020 x86-64 repo updated with following packages:
package 1
package 2
etc....

Thats it.
Rgds
Saxa

On Fri, Dec 4, 2020 at 10:11 PM Nathaniel Russell
<nat...@gm...> wrote:
>
> Could u attach a changelog with what u are saying please so i have a better understanding as to how u r thinking it should be??
>
> On Fri, Dec 4, 2020 at 9:24 AM Sasa Ostrouska <ca...@gm...> wrote:
>>
>> Sure, we can mention to see the individual changelogs in
>> /usr/src/dropline-build-system/scripts/$PACKAGENAME
>>
>> Also we can use the Changelog to reflect the repository tree update
>> date and package name.
>>
>> On Fri, Dec 4, 2020 at 12:55 AM Nathaniel Russell
>> <nat...@gm...> wrote:
>> >
>> > So then would we out something in the changelog that would refer them to the individual changelog???
>> >
>> > On Thu, Dec 3, 2020 at 5:53 PM Sasa Ostrouska <ca...@gm...> wrote:
>> >>
>> >> On Fri, Dec 4, 2020 at 12:49 AM Nathaniel Russell
>> >> <nat...@gm...> wrote:
>> >> >
>> >> > So then how would u like to do the changelog ????
>> >> I do think that the empty one can work for the repo, and leave the
>> >> ones we have where they are.
>> >>
>> >> >
>> >> > On Thu, Dec 3, 2020 at 5:42 PM Sasa Ostrouska <ca...@gm...> wrote:
>> >> >>
>> >> >> On Thu, Dec 3, 2020 at 11:50 PM Nathaniel Russell
>> >> >> <nat...@gm...> wrote:
>> >> >> >
>> >> >> >
>> >> >> > That would be fine if u want I can do the changelog and u could keep doing your version of a changlog within the packages.
>> >> >> The thing is that all that stuff should go into DBS so it can be
>> >> >> automated. But again, I think is no sense to have twice the same
>> >> >> information
>> >> >> listed in 2 places, and then be more mistake prone.
>> >> >>
>> >> >> Rgds
>> >> >> Saxa
>> >> >> >
>> >> >> > On Thu, Dec 3, 2020 at 4:36 PM Sasa Ostrouska <ca...@gm...> wrote:
>> >> >> >>
>> >> >> >> On Thu, Dec 3, 2020 at 9:23 PM Tomáš Bažant <tom...@gm...> wrote:
>> >> >> >> >
>> >> >> >> > hi
>> >> >> >> > you're correct, it should be the repo-owner's key, definitely. but signing them requires the private part of the gpg key imho, so.......you cant sign it with someone else's key, but maybe i'm wrong here.
>> >> >> >> > t.
>> >> >> >> >
>> >> >> >> > čt 3. 12. 2020 v 20:25 odesílatel Nathaniel Russell <nat...@gm...> napsal:
>> >> >> >> >>
>> >> >> >> >> But you dont want gen_repos to use ur gpf key these are majntained by Sasa not us that is y im asking him for his gpg key to sign all packages.
>> >> >> >>
>> >> >> >> Ok, I can do a public key and a private one for droplinegnome project
>> >> >> >> and we could share that then.
>> >> >> >>
>> >> >> >> Rgds
>> >> >> >> Saxa
>> >> >> >> >>
>> >> >> >> >> On Thu, Dec 3, 2020 at 12:11 PM Tomáš Bažant <tom...@gm...> wrote:
>> >> >> >> >>>
>> >> >> >> >>> It is always best to have a valid changelog, no donut about it. The gpg thing - the `gen_repos_files.sh` script signs the packages with your GPG key (see notes at project's sf.net wiki).
>> >> >> >> >>> If you want to run `slackpkg update` on a repo whose packages are not signed, then you need to update the `/etc/slackpkg/slackpkgplus.conf` file and set `STRICTGPG=on`
>> >> >> >> >>>
>> >> >> >> >>> čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <nat...@gm...> napsal:
>> >> >> >> >>>>
>> >> >> >> >>>> Acutally if you run the gen_repo script of Eric’s it ends up making a Blank Changelog.txt file so I would say it is.
>> >> >> >> >>>>
>> >> >> >> >>>> When you have all the files you need running slackpkg update barfs on GPG-KEY for Gnome i will send u a picture 2nite.
>> >> >> >> >>>>
>> >> >> >> >>>> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <ca...@gm...> wrote:
>> >> >> >> >>>>>
>> >> >> >> >>>>> Out of curiosity, is the Changelog.txt obligatory ?
>> >> >> >> >>>>>
>> >> >> >> >>>>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
>> >> >> >> >>>>> <nat...@gm...> wrote:
>> >> >> >> >>>>> >
>> >> >> >> >>>>> > This is a start for the slackpkg+ repo files I still have to work on the Changelog and get everything in order. When I run my slackpkg update it is barfing on a GPG-KEY for the dropline gnome repo.
>> >> >> >> >>>>> > Is there any way you have this Key on hand so that I can continue to update and the files and help with making this slackpkg+ complaint?
>> >> >> >> >>>>> > _______________________________________________
>> >> >> >> >>>>> > Dropline-gnome-devel mailing list
>> >> >> >> >>>>> > Dro...@li...
>> >> >> >> >>>>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >> >>>>>
>> >> >> >> >>>>>
>> >> >> >> >>>>> _______________________________________________
>> >> >> >> >>>>> Dropline-gnome-devel mailing list
>> >> >> >> >>>>> Dro...@li...
>> >> >> >> >>>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >> >>>>
>> >> >> >> >>>> --
>> >> >> >> >>>> Nathaniel & LeAnna Russell
>> >> >> >> >>>> _______________________________________________
>> >> >> >> >>>> Dropline-gnome-devel mailing list
>> >> >> >> >>>> Dro...@li...
>> >> >> >> >>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >> >>>
>> >> >> >> >>> _______________________________________________
>> >> >> >> >>> Dropline-gnome-devel mailing list
>> >> >> >> >>> Dro...@li...
>> >> >> >> >>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Nathaniel & LeAnna Russell
>> >> >> >> >> _______________________________________________
>> >> >> >> >> Dropline-gnome-devel mailing list
>> >> >> >> >> Dro...@li...
>> >> >> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >> >
>> >> >> >> > _______________________________________________
>> >> >> >> > Dropline-gnome-devel mailing list
>> >> >> >> > Dro...@li...
>> >> >> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >>
>> >> >> >>
>> >> >> >> _______________________________________________
>> >> >> >> Dropline-gnome-devel mailing list
>> >> >> >> Dro...@li...
>> >> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >
>> >> >> > --
>> >> >> > Nathaniel & LeAnna Russell
>> >> >> > _______________________________________________
>> >> >> > Dropline-gnome-devel mailing list
>> >> >> > Dro...@li...
>> >> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> Dropline-gnome-devel mailing list
>> >> >> Dro...@li...
>> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >
>> >> > --
>> >> > Nathaniel & LeAnna Russell
>> >> > _______________________________________________
>> >> > Dropline-gnome-devel mailing list
>> >> > Dro...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >>
>> >>
>> >> _______________________________________________
>> >> Dropline-gnome-devel mailing list
>> >> Dro...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >
>> > --
>> > Nathaniel & LeAnna Russell
>> > _______________________________________________
>> > Dropline-gnome-devel mailing list
>> > Dro...@li...
>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>
>>
>> _______________________________________________
>> Dropline-gnome-devel mailing list
>> Dro...@li...
>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
> --
> Nathaniel & LeAnna Russell
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

Re: [DLG-dev] Slackpkg+ Complaince

[Nathaniel R. <nat...@gm...>]

Could u attach a changelog with what u are saying please so i have a better
understanding as to how u r thinking it should be??

On Fri, Dec 4, 2020 at 9:24 AM Sasa Ostrouska <ca...@gm...> wrote:

> Sure, we can mention to see the individual changelogs in
> /usr/src/dropline-build-system/scripts/$PACKAGENAME
>
> Also we can use the Changelog to reflect the repository tree update
> date and package name.
>
> On Fri, Dec 4, 2020 at 12:55 AM Nathaniel Russell
> <nat...@gm...> wrote:
> >
> > So then would we out something in the changelog that would refer them to
> the individual changelog???
> >
> > On Thu, Dec 3, 2020 at 5:53 PM Sasa Ostrouska <ca...@gm...> wrote:
> >>
> >> On Fri, Dec 4, 2020 at 12:49 AM Nathaniel Russell
> >> <nat...@gm...> wrote:
> >> >
> >> > So then how would u like to do the changelog ????
> >> I do think that the empty one can work for the repo, and leave the
> >> ones we have where they are.
> >>
> >> >
> >> > On Thu, Dec 3, 2020 at 5:42 PM Sasa Ostrouska <ca...@gm...>
> wrote:
> >> >>
> >> >> On Thu, Dec 3, 2020 at 11:50 PM Nathaniel Russell
> >> >> <nat...@gm...> wrote:
> >> >> >
> >> >> >
> >> >> > That would be fine if u want I can do the changelog and u could
> keep doing your version of a changlog within the packages.
> >> >> The thing is that all that stuff should go into DBS so it can be
> >> >> automated. But again, I think is no sense to have twice the same
> >> >> information
> >> >> listed in 2 places, and then be more mistake prone.
> >> >>
> >> >> Rgds
> >> >> Saxa
> >> >> >
> >> >> > On Thu, Dec 3, 2020 at 4:36 PM Sasa Ostrouska <ca...@gm...>
> wrote:
> >> >> >>
> >> >> >> On Thu, Dec 3, 2020 at 9:23 PM Tomáš Bažant <
> tom...@gm...> wrote:
> >> >> >> >
> >> >> >> > hi
> >> >> >> > you're correct, it should be the repo-owner's key, definitely.
> but signing them requires the private part of the gpg key imho,
> so.......you cant sign it with someone else's key, but maybe i'm wrong here.
> >> >> >> > t.
> >> >> >> >
> >> >> >> > čt 3. 12. 2020 v 20:25 odesílatel Nathaniel Russell <
> nat...@gm...> napsal:
> >> >> >> >>
> >> >> >> >> But you dont want gen_repos to use ur gpf key these are
> majntained by Sasa not us that is y im asking him for his gpg key to sign
> all packages.
> >> >> >>
> >> >> >> Ok, I can do a public key and a private one for droplinegnome
> project
> >> >> >> and we could share that then.
> >> >> >>
> >> >> >> Rgds
> >> >> >> Saxa
> >> >> >> >>
> >> >> >> >> On Thu, Dec 3, 2020 at 12:11 PM Tomáš Bažant <
> tom...@gm...> wrote:
> >> >> >> >>>
> >> >> >> >>> It is always best to have a valid changelog, no donut about
> it. The gpg thing - the `gen_repos_files.sh` script signs the packages with
> your GPG key (see notes at project's sf.net wiki).
> >> >> >> >>> If you want to run `slackpkg update` on a repo whose packages
> are not signed, then you need to update the
> `/etc/slackpkg/slackpkgplus.conf` file and set `STRICTGPG=on`
> >> >> >> >>>
> >> >> >> >>> čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <
> nat...@gm...> napsal:
> >> >> >> >>>>
> >> >> >> >>>> Acutally if you run the gen_repo script of Eric’s it ends up
> making a Blank Changelog.txt file so I would say it is.
> >> >> >> >>>>
> >> >> >> >>>> When you have all the files you need running slackpkg update
> barfs on GPG-KEY for Gnome i will send u a picture 2nite.
> >> >> >> >>>>
> >> >> >> >>>> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <
> ca...@gm...> wrote:
> >> >> >> >>>>>
> >> >> >> >>>>> Out of curiosity, is the Changelog.txt obligatory ?
> >> >> >> >>>>>
> >> >> >> >>>>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
> >> >> >> >>>>> <nat...@gm...> wrote:
> >> >> >> >>>>> >
> >> >> >> >>>>> > This is a start for the slackpkg+ repo files I still have
> to work on the Changelog and get everything in order. When I run my
> slackpkg update it is barfing on a GPG-KEY for the dropline gnome repo.
> >> >> >> >>>>> > Is there any way you have this Key on hand so that I can
> continue to update and the files and help with making this slackpkg+
> complaint?
> >> >> >> >>>>> > _______________________________________________
> >> >> >> >>>>> > Dropline-gnome-devel mailing list
> >> >> >> >>>>> > Dro...@li...
> >> >> >> >>>>> >
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >> >>>>>
> >> >> >> >>>>>
> >> >> >> >>>>> _______________________________________________
> >> >> >> >>>>> Dropline-gnome-devel mailing list
> >> >> >> >>>>> Dro...@li...
> >> >> >> >>>>>
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >> >>>>
> >> >> >> >>>> --
> >> >> >> >>>> Nathaniel & LeAnna Russell
> >> >> >> >>>> _______________________________________________
> >> >> >> >>>> Dropline-gnome-devel mailing list
> >> >> >> >>>> Dro...@li...
> >> >> >> >>>>
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >> >>>
> >> >> >> >>> _______________________________________________
> >> >> >> >>> Dropline-gnome-devel mailing list
> >> >> >> >>> Dro...@li...
> >> >> >> >>>
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Nathaniel & LeAnna Russell
> >> >> >> >> _______________________________________________
> >> >> >> >> Dropline-gnome-devel mailing list
> >> >> >> >> Dro...@li...
> >> >> >> >>
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >> >
> >> >> >> > _______________________________________________
> >> >> >> > Dropline-gnome-devel mailing list
> >> >> >> > Dro...@li...
> >> >> >> >
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >>
> >> >> >>
> >> >> >> _______________________________________________
> >> >> >> Dropline-gnome-devel mailing list
> >> >> >> Dro...@li...
> >> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >
> >> >> > --
> >> >> > Nathaniel & LeAnna Russell
> >> >> > _______________________________________________
> >> >> > Dropline-gnome-devel mailing list
> >> >> > Dro...@li...
> >> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Dropline-gnome-devel mailing list
> >> >> Dro...@li...
> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >
> >> > --
> >> > Nathaniel & LeAnna Russell
> >> > _______________________________________________
> >> > Dropline-gnome-devel mailing list
> >> > Dro...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >>
> >>
> >> _______________________________________________
> >> Dropline-gnome-devel mailing list
> >> Dro...@li...
> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >
> > --
> > Nathaniel & LeAnna Russell
> > _______________________________________________
> > Dropline-gnome-devel mailing list
> > Dro...@li...
> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
>
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
-- 
Nathaniel & LeAnna Russell

Re: [DLG-dev] Slackpkg+ Complaince

[Sasa O. <ca...@gm...>]

Sure, we can mention to see the individual changelogs in
/usr/src/dropline-build-system/scripts/$PACKAGENAME

Also we can use the Changelog to reflect the repository tree update
date and package name.

On Fri, Dec 4, 2020 at 12:55 AM Nathaniel Russell
<nat...@gm...> wrote:
>
> So then would we out something in the changelog that would refer them to the individual changelog???
>
> On Thu, Dec 3, 2020 at 5:53 PM Sasa Ostrouska <ca...@gm...> wrote:
>>
>> On Fri, Dec 4, 2020 at 12:49 AM Nathaniel Russell
>> <nat...@gm...> wrote:
>> >
>> > So then how would u like to do the changelog ????
>> I do think that the empty one can work for the repo, and leave the
>> ones we have where they are.
>>
>> >
>> > On Thu, Dec 3, 2020 at 5:42 PM Sasa Ostrouska <ca...@gm...> wrote:
>> >>
>> >> On Thu, Dec 3, 2020 at 11:50 PM Nathaniel Russell
>> >> <nat...@gm...> wrote:
>> >> >
>> >> >
>> >> > That would be fine if u want I can do the changelog and u could keep doing your version of a changlog within the packages.
>> >> The thing is that all that stuff should go into DBS so it can be
>> >> automated. But again, I think is no sense to have twice the same
>> >> information
>> >> listed in 2 places, and then be more mistake prone.
>> >>
>> >> Rgds
>> >> Saxa
>> >> >
>> >> > On Thu, Dec 3, 2020 at 4:36 PM Sasa Ostrouska <ca...@gm...> wrote:
>> >> >>
>> >> >> On Thu, Dec 3, 2020 at 9:23 PM Tomáš Bažant <tom...@gm...> wrote:
>> >> >> >
>> >> >> > hi
>> >> >> > you're correct, it should be the repo-owner's key, definitely. but signing them requires the private part of the gpg key imho, so.......you cant sign it with someone else's key, but maybe i'm wrong here.
>> >> >> > t.
>> >> >> >
>> >> >> > čt 3. 12. 2020 v 20:25 odesílatel Nathaniel Russell <nat...@gm...> napsal:
>> >> >> >>
>> >> >> >> But you dont want gen_repos to use ur gpf key these are majntained by Sasa not us that is y im asking him for his gpg key to sign all packages.
>> >> >>
>> >> >> Ok, I can do a public key and a private one for droplinegnome project
>> >> >> and we could share that then.
>> >> >>
>> >> >> Rgds
>> >> >> Saxa
>> >> >> >>
>> >> >> >> On Thu, Dec 3, 2020 at 12:11 PM Tomáš Bažant <tom...@gm...> wrote:
>> >> >> >>>
>> >> >> >>> It is always best to have a valid changelog, no donut about it. The gpg thing - the `gen_repos_files.sh` script signs the packages with your GPG key (see notes at project's sf.net wiki).
>> >> >> >>> If you want to run `slackpkg update` on a repo whose packages are not signed, then you need to update the `/etc/slackpkg/slackpkgplus.conf` file and set `STRICTGPG=on`
>> >> >> >>>
>> >> >> >>> čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <nat...@gm...> napsal:
>> >> >> >>>>
>> >> >> >>>> Acutally if you run the gen_repo script of Eric’s it ends up making a Blank Changelog.txt file so I would say it is.
>> >> >> >>>>
>> >> >> >>>> When you have all the files you need running slackpkg update barfs on GPG-KEY for Gnome i will send u a picture 2nite.
>> >> >> >>>>
>> >> >> >>>> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <ca...@gm...> wrote:
>> >> >> >>>>>
>> >> >> >>>>> Out of curiosity, is the Changelog.txt obligatory ?
>> >> >> >>>>>
>> >> >> >>>>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
>> >> >> >>>>> <nat...@gm...> wrote:
>> >> >> >>>>> >
>> >> >> >>>>> > This is a start for the slackpkg+ repo files I still have to work on the Changelog and get everything in order. When I run my slackpkg update it is barfing on a GPG-KEY for the dropline gnome repo.
>> >> >> >>>>> > Is there any way you have this Key on hand so that I can continue to update and the files and help with making this slackpkg+ complaint?
>> >> >> >>>>> > _______________________________________________
>> >> >> >>>>> > Dropline-gnome-devel mailing list
>> >> >> >>>>> > Dro...@li...
>> >> >> >>>>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >>>>> _______________________________________________
>> >> >> >>>>> Dropline-gnome-devel mailing list
>> >> >> >>>>> Dro...@li...
>> >> >> >>>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >>>>
>> >> >> >>>> --
>> >> >> >>>> Nathaniel & LeAnna Russell
>> >> >> >>>> _______________________________________________
>> >> >> >>>> Dropline-gnome-devel mailing list
>> >> >> >>>> Dro...@li...
>> >> >> >>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >>>
>> >> >> >>> _______________________________________________
>> >> >> >>> Dropline-gnome-devel mailing list
>> >> >> >>> Dro...@li...
>> >> >> >>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >>
>> >> >> >> --
>> >> >> >> Nathaniel & LeAnna Russell
>> >> >> >> _______________________________________________
>> >> >> >> Dropline-gnome-devel mailing list
>> >> >> >> Dro...@li...
>> >> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >> >
>> >> >> > _______________________________________________
>> >> >> > Dropline-gnome-devel mailing list
>> >> >> > Dro...@li...
>> >> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> Dropline-gnome-devel mailing list
>> >> >> Dro...@li...
>> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >
>> >> > --
>> >> > Nathaniel & LeAnna Russell
>> >> > _______________________________________________
>> >> > Dropline-gnome-devel mailing list
>> >> > Dro...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >>
>> >>
>> >> _______________________________________________
>> >> Dropline-gnome-devel mailing list
>> >> Dro...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >
>> > --
>> > Nathaniel & LeAnna Russell
>> > _______________________________________________
>> > Dropline-gnome-devel mailing list
>> > Dro...@li...
>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>
>>
>> _______________________________________________
>> Dropline-gnome-devel mailing list
>> Dro...@li...
>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
> --
> Nathaniel & LeAnna Russell
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

Re: [DLG-dev] Slackpkg+ Complaince

[Nathaniel R. <nat...@gm...>]

So then would we out something in the changelog that would refer them to
the individual changelog???

On Thu, Dec 3, 2020 at 5:53 PM Sasa Ostrouska <ca...@gm...> wrote:

> On Fri, Dec 4, 2020 at 12:49 AM Nathaniel Russell
> <nat...@gm...> wrote:
> >
> > So then how would u like to do the changelog ????
> I do think that the empty one can work for the repo, and leave the
> ones we have where they are.
>
> >
> > On Thu, Dec 3, 2020 at 5:42 PM Sasa Ostrouska <ca...@gm...> wrote:
> >>
> >> On Thu, Dec 3, 2020 at 11:50 PM Nathaniel Russell
> >> <nat...@gm...> wrote:
> >> >
> >> >
> >> > That would be fine if u want I can do the changelog and u could keep
> doing your version of a changlog within the packages.
> >> The thing is that all that stuff should go into DBS so it can be
> >> automated. But again, I think is no sense to have twice the same
> >> information
> >> listed in 2 places, and then be more mistake prone.
> >>
> >> Rgds
> >> Saxa
> >> >
> >> > On Thu, Dec 3, 2020 at 4:36 PM Sasa Ostrouska <ca...@gm...>
> wrote:
> >> >>
> >> >> On Thu, Dec 3, 2020 at 9:23 PM Tomáš Bažant <tom...@gm...>
> wrote:
> >> >> >
> >> >> > hi
> >> >> > you're correct, it should be the repo-owner's key, definitely. but
> signing them requires the private part of the gpg key imho, so.......you
> cant sign it with someone else's key, but maybe i'm wrong here.
> >> >> > t.
> >> >> >
> >> >> > čt 3. 12. 2020 v 20:25 odesílatel Nathaniel Russell <
> nat...@gm...> napsal:
> >> >> >>
> >> >> >> But you dont want gen_repos to use ur gpf key these are
> majntained by Sasa not us that is y im asking him for his gpg key to sign
> all packages.
> >> >>
> >> >> Ok, I can do a public key and a private one for droplinegnome project
> >> >> and we could share that then.
> >> >>
> >> >> Rgds
> >> >> Saxa
> >> >> >>
> >> >> >> On Thu, Dec 3, 2020 at 12:11 PM Tomáš Bažant <
> tom...@gm...> wrote:
> >> >> >>>
> >> >> >>> It is always best to have a valid changelog, no donut about it.
> The gpg thing - the `gen_repos_files.sh` script signs the packages with
> your GPG key (see notes at project's sf.net wiki).
> >> >> >>> If you want to run `slackpkg update` on a repo whose packages
> are not signed, then you need to update the
> `/etc/slackpkg/slackpkgplus.conf` file and set `STRICTGPG=on`
> >> >> >>>
> >> >> >>> čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <
> nat...@gm...> napsal:
> >> >> >>>>
> >> >> >>>> Acutally if you run the gen_repo script of Eric’s it ends up
> making a Blank Changelog.txt file so I would say it is.
> >> >> >>>>
> >> >> >>>> When you have all the files you need running slackpkg update
> barfs on GPG-KEY for Gnome i will send u a picture 2nite.
> >> >> >>>>
> >> >> >>>> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <ca...@gm...>
> wrote:
> >> >> >>>>>
> >> >> >>>>> Out of curiosity, is the Changelog.txt obligatory ?
> >> >> >>>>>
> >> >> >>>>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
> >> >> >>>>> <nat...@gm...> wrote:
> >> >> >>>>> >
> >> >> >>>>> > This is a start for the slackpkg+ repo files I still have to
> work on the Changelog and get everything in order. When I run my slackpkg
> update it is barfing on a GPG-KEY for the dropline gnome repo.
> >> >> >>>>> > Is there any way you have this Key on hand so that I can
> continue to update and the files and help with making this slackpkg+
> complaint?
> >> >> >>>>> > _______________________________________________
> >> >> >>>>> > Dropline-gnome-devel mailing list
> >> >> >>>>> > Dro...@li...
> >> >> >>>>> >
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >>>>>
> >> >> >>>>>
> >> >> >>>>> _______________________________________________
> >> >> >>>>> Dropline-gnome-devel mailing list
> >> >> >>>>> Dro...@li...
> >> >> >>>>>
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >>>>
> >> >> >>>> --
> >> >> >>>> Nathaniel & LeAnna Russell
> >> >> >>>> _______________________________________________
> >> >> >>>> Dropline-gnome-devel mailing list
> >> >> >>>> Dro...@li...
> >> >> >>>>
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >>>
> >> >> >>> _______________________________________________
> >> >> >>> Dropline-gnome-devel mailing list
> >> >> >>> Dro...@li...
> >> >> >>>
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >>
> >> >> >> --
> >> >> >> Nathaniel & LeAnna Russell
> >> >> >> _______________________________________________
> >> >> >> Dropline-gnome-devel mailing list
> >> >> >> Dro...@li...
> >> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >> >
> >> >> > _______________________________________________
> >> >> > Dropline-gnome-devel mailing list
> >> >> > Dro...@li...
> >> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Dropline-gnome-devel mailing list
> >> >> Dro...@li...
> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >
> >> > --
> >> > Nathaniel & LeAnna Russell
> >> > _______________________________________________
> >> > Dropline-gnome-devel mailing list
> >> > Dro...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >>
> >>
> >> _______________________________________________
> >> Dropline-gnome-devel mailing list
> >> Dro...@li...
> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >
> > --
> > Nathaniel & LeAnna Russell
> > _______________________________________________
> > Dropline-gnome-devel mailing list
> > Dro...@li...
> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
>
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
-- 
Nathaniel & LeAnna Russell

Re: [DLG-dev] Slackpkg+ Complaince

[Sasa O. <ca...@gm...>]

On Fri, Dec 4, 2020 at 12:49 AM Nathaniel Russell
<nat...@gm...> wrote:
>
> So then how would u like to do the changelog ????
I do think that the empty one can work for the repo, and leave the
ones we have where they are.

>
> On Thu, Dec 3, 2020 at 5:42 PM Sasa Ostrouska <ca...@gm...> wrote:
>>
>> On Thu, Dec 3, 2020 at 11:50 PM Nathaniel Russell
>> <nat...@gm...> wrote:
>> >
>> >
>> > That would be fine if u want I can do the changelog and u could keep doing your version of a changlog within the packages.
>> The thing is that all that stuff should go into DBS so it can be
>> automated. But again, I think is no sense to have twice the same
>> information
>> listed in 2 places, and then be more mistake prone.
>>
>> Rgds
>> Saxa
>> >
>> > On Thu, Dec 3, 2020 at 4:36 PM Sasa Ostrouska <ca...@gm...> wrote:
>> >>
>> >> On Thu, Dec 3, 2020 at 9:23 PM Tomáš Bažant <tom...@gm...> wrote:
>> >> >
>> >> > hi
>> >> > you're correct, it should be the repo-owner's key, definitely. but signing them requires the private part of the gpg key imho, so.......you cant sign it with someone else's key, but maybe i'm wrong here.
>> >> > t.
>> >> >
>> >> > čt 3. 12. 2020 v 20:25 odesílatel Nathaniel Russell <nat...@gm...> napsal:
>> >> >>
>> >> >> But you dont want gen_repos to use ur gpf key these are majntained by Sasa not us that is y im asking him for his gpg key to sign all packages.
>> >>
>> >> Ok, I can do a public key and a private one for droplinegnome project
>> >> and we could share that then.
>> >>
>> >> Rgds
>> >> Saxa
>> >> >>
>> >> >> On Thu, Dec 3, 2020 at 12:11 PM Tomáš Bažant <tom...@gm...> wrote:
>> >> >>>
>> >> >>> It is always best to have a valid changelog, no donut about it. The gpg thing - the `gen_repos_files.sh` script signs the packages with your GPG key (see notes at project's sf.net wiki).
>> >> >>> If you want to run `slackpkg update` on a repo whose packages are not signed, then you need to update the `/etc/slackpkg/slackpkgplus.conf` file and set `STRICTGPG=on`
>> >> >>>
>> >> >>> čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <nat...@gm...> napsal:
>> >> >>>>
>> >> >>>> Acutally if you run the gen_repo script of Eric’s it ends up making a Blank Changelog.txt file so I would say it is.
>> >> >>>>
>> >> >>>> When you have all the files you need running slackpkg update barfs on GPG-KEY for Gnome i will send u a picture 2nite.
>> >> >>>>
>> >> >>>> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <ca...@gm...> wrote:
>> >> >>>>>
>> >> >>>>> Out of curiosity, is the Changelog.txt obligatory ?
>> >> >>>>>
>> >> >>>>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
>> >> >>>>> <nat...@gm...> wrote:
>> >> >>>>> >
>> >> >>>>> > This is a start for the slackpkg+ repo files I still have to work on the Changelog and get everything in order. When I run my slackpkg update it is barfing on a GPG-KEY for the dropline gnome repo.
>> >> >>>>> > Is there any way you have this Key on hand so that I can continue to update and the files and help with making this slackpkg+ complaint?
>> >> >>>>> > _______________________________________________
>> >> >>>>> > Dropline-gnome-devel mailing list
>> >> >>>>> > Dro...@li...
>> >> >>>>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> _______________________________________________
>> >> >>>>> Dropline-gnome-devel mailing list
>> >> >>>>> Dro...@li...
>> >> >>>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >>>>
>> >> >>>> --
>> >> >>>> Nathaniel & LeAnna Russell
>> >> >>>> _______________________________________________
>> >> >>>> Dropline-gnome-devel mailing list
>> >> >>>> Dro...@li...
>> >> >>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >>>
>> >> >>> _______________________________________________
>> >> >>> Dropline-gnome-devel mailing list
>> >> >>> Dro...@li...
>> >> >>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >>
>> >> >> --
>> >> >> Nathaniel & LeAnna Russell
>> >> >> _______________________________________________
>> >> >> Dropline-gnome-devel mailing list
>> >> >> Dro...@li...
>> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >> >
>> >> > _______________________________________________
>> >> > Dropline-gnome-devel mailing list
>> >> > Dro...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >>
>> >>
>> >> _______________________________________________
>> >> Dropline-gnome-devel mailing list
>> >> Dro...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >
>> > --
>> > Nathaniel & LeAnna Russell
>> > _______________________________________________
>> > Dropline-gnome-devel mailing list
>> > Dro...@li...
>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>
>>
>> _______________________________________________
>> Dropline-gnome-devel mailing list
>> Dro...@li...
>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
> --
> Nathaniel & LeAnna Russell
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

Re: [DLG-dev] Slackpkg+ Complaince

[Nathaniel R. <nat...@gm...>]

So then how would u like to do the changelog ????

On Thu, Dec 3, 2020 at 5:42 PM Sasa Ostrouska <ca...@gm...> wrote:

> On Thu, Dec 3, 2020 at 11:50 PM Nathaniel Russell
> <nat...@gm...> wrote:
> >
> >
> > That would be fine if u want I can do the changelog and u could keep
> doing your version of a changlog within the packages.
> The thing is that all that stuff should go into DBS so it can be
> automated. But again, I think is no sense to have twice the same
> information
> listed in 2 places, and then be more mistake prone.
>
> Rgds
> Saxa
> >
> > On Thu, Dec 3, 2020 at 4:36 PM Sasa Ostrouska <ca...@gm...> wrote:
> >>
> >> On Thu, Dec 3, 2020 at 9:23 PM Tomáš Bažant <tom...@gm...>
> wrote:
> >> >
> >> > hi
> >> > you're correct, it should be the repo-owner's key, definitely. but
> signing them requires the private part of the gpg key imho, so.......you
> cant sign it with someone else's key, but maybe i'm wrong here.
> >> > t.
> >> >
> >> > čt 3. 12. 2020 v 20:25 odesílatel Nathaniel Russell <
> nat...@gm...> napsal:
> >> >>
> >> >> But you dont want gen_repos to use ur gpf key these are majntained
> by Sasa not us that is y im asking him for his gpg key to sign all packages.
> >>
> >> Ok, I can do a public key and a private one for droplinegnome project
> >> and we could share that then.
> >>
> >> Rgds
> >> Saxa
> >> >>
> >> >> On Thu, Dec 3, 2020 at 12:11 PM Tomáš Bažant <tom...@gm...>
> wrote:
> >> >>>
> >> >>> It is always best to have a valid changelog, no donut about it. The
> gpg thing - the `gen_repos_files.sh` script signs the packages with your
> GPG key (see notes at project's sf.net wiki).
> >> >>> If you want to run `slackpkg update` on a repo whose packages are
> not signed, then you need to update the `/etc/slackpkg/slackpkgplus.conf`
> file and set `STRICTGPG=on`
> >> >>>
> >> >>> čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <
> nat...@gm...> napsal:
> >> >>>>
> >> >>>> Acutally if you run the gen_repo script of Eric’s it ends up
> making a Blank Changelog.txt file so I would say it is.
> >> >>>>
> >> >>>> When you have all the files you need running slackpkg update barfs
> on GPG-KEY for Gnome i will send u a picture 2nite.
> >> >>>>
> >> >>>> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <ca...@gm...>
> wrote:
> >> >>>>>
> >> >>>>> Out of curiosity, is the Changelog.txt obligatory ?
> >> >>>>>
> >> >>>>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
> >> >>>>> <nat...@gm...> wrote:
> >> >>>>> >
> >> >>>>> > This is a start for the slackpkg+ repo files I still have to
> work on the Changelog and get everything in order. When I run my slackpkg
> update it is barfing on a GPG-KEY for the dropline gnome repo.
> >> >>>>> > Is there any way you have this Key on hand so that I can
> continue to update and the files and help with making this slackpkg+
> complaint?
> >> >>>>> > _______________________________________________
> >> >>>>> > Dropline-gnome-devel mailing list
> >> >>>>> > Dro...@li...
> >> >>>>> >
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >>>>>
> >> >>>>>
> >> >>>>> _______________________________________________
> >> >>>>> Dropline-gnome-devel mailing list
> >> >>>>> Dro...@li...
> >> >>>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >>>>
> >> >>>> --
> >> >>>> Nathaniel & LeAnna Russell
> >> >>>> _______________________________________________
> >> >>>> Dropline-gnome-devel mailing list
> >> >>>> Dro...@li...
> >> >>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >>>
> >> >>> _______________________________________________
> >> >>> Dropline-gnome-devel mailing list
> >> >>> Dro...@li...
> >> >>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >>
> >> >> --
> >> >> Nathaniel & LeAnna Russell
> >> >> _______________________________________________
> >> >> Dropline-gnome-devel mailing list
> >> >> Dro...@li...
> >> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >> >
> >> > _______________________________________________
> >> > Dropline-gnome-devel mailing list
> >> > Dro...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >>
> >>
> >> _______________________________________________
> >> Dropline-gnome-devel mailing list
> >> Dro...@li...
> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >
> > --
> > Nathaniel & LeAnna Russell
> > _______________________________________________
> > Dropline-gnome-devel mailing list
> > Dro...@li...
> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
>
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
-- 
Nathaniel & LeAnna Russell

Re: [DLG-dev] Slackpkg+ Complaince

[Sasa O. <ca...@gm...>]

On Thu, Dec 3, 2020 at 11:50 PM Nathaniel Russell
<nat...@gm...> wrote:
>
>
> That would be fine if u want I can do the changelog and u could keep doing your version of a changlog within the packages.
The thing is that all that stuff should go into DBS so it can be
automated. But again, I think is no sense to have twice the same
information
listed in 2 places, and then be more mistake prone.

Rgds
Saxa
>
> On Thu, Dec 3, 2020 at 4:36 PM Sasa Ostrouska <ca...@gm...> wrote:
>>
>> On Thu, Dec 3, 2020 at 9:23 PM Tomáš Bažant <tom...@gm...> wrote:
>> >
>> > hi
>> > you're correct, it should be the repo-owner's key, definitely. but signing them requires the private part of the gpg key imho, so.......you cant sign it with someone else's key, but maybe i'm wrong here.
>> > t.
>> >
>> > čt 3. 12. 2020 v 20:25 odesílatel Nathaniel Russell <nat...@gm...> napsal:
>> >>
>> >> But you dont want gen_repos to use ur gpf key these are majntained by Sasa not us that is y im asking him for his gpg key to sign all packages.
>>
>> Ok, I can do a public key and a private one for droplinegnome project
>> and we could share that then.
>>
>> Rgds
>> Saxa
>> >>
>> >> On Thu, Dec 3, 2020 at 12:11 PM Tomáš Bažant <tom...@gm...> wrote:
>> >>>
>> >>> It is always best to have a valid changelog, no donut about it. The gpg thing - the `gen_repos_files.sh` script signs the packages with your GPG key (see notes at project's sf.net wiki).
>> >>> If you want to run `slackpkg update` on a repo whose packages are not signed, then you need to update the `/etc/slackpkg/slackpkgplus.conf` file and set `STRICTGPG=on`
>> >>>
>> >>> čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <nat...@gm...> napsal:
>> >>>>
>> >>>> Acutally if you run the gen_repo script of Eric’s it ends up making a Blank Changelog.txt file so I would say it is.
>> >>>>
>> >>>> When you have all the files you need running slackpkg update barfs on GPG-KEY for Gnome i will send u a picture 2nite.
>> >>>>
>> >>>> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <ca...@gm...> wrote:
>> >>>>>
>> >>>>> Out of curiosity, is the Changelog.txt obligatory ?
>> >>>>>
>> >>>>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
>> >>>>> <nat...@gm...> wrote:
>> >>>>> >
>> >>>>> > This is a start for the slackpkg+ repo files I still have to work on the Changelog and get everything in order. When I run my slackpkg update it is barfing on a GPG-KEY for the dropline gnome repo.
>> >>>>> > Is there any way you have this Key on hand so that I can continue to update and the files and help with making this slackpkg+ complaint?
>> >>>>> > _______________________________________________
>> >>>>> > Dropline-gnome-devel mailing list
>> >>>>> > Dro...@li...
>> >>>>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >>>>>
>> >>>>>
>> >>>>> _______________________________________________
>> >>>>> Dropline-gnome-devel mailing list
>> >>>>> Dro...@li...
>> >>>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >>>>
>> >>>> --
>> >>>> Nathaniel & LeAnna Russell
>> >>>> _______________________________________________
>> >>>> Dropline-gnome-devel mailing list
>> >>>> Dro...@li...
>> >>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >>>
>> >>> _______________________________________________
>> >>> Dropline-gnome-devel mailing list
>> >>> Dro...@li...
>> >>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >>
>> >> --
>> >> Nathaniel & LeAnna Russell
>> >> _______________________________________________
>> >> Dropline-gnome-devel mailing list
>> >> Dro...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >
>> > _______________________________________________
>> > Dropline-gnome-devel mailing list
>> > Dro...@li...
>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>
>>
>> _______________________________________________
>> Dropline-gnome-devel mailing list
>> Dro...@li...
>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
> --
> Nathaniel & LeAnna Russell
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

Re: [DLG-dev] Slackpkg+ Complaince

[Nathaniel R. <nat...@gm...>]

That would be fine if u want I can do the changelog and u could keep doing
your version of a changlog within the packages.

On Thu, Dec 3, 2020 at 4:36 PM Sasa Ostrouska <ca...@gm...> wrote:

> On Thu, Dec 3, 2020 at 9:23 PM Tomáš Bažant <tom...@gm...> wrote:
> >
> > hi
> > you're correct, it should be the repo-owner's key, definitely. but
> signing them requires the private part of the gpg key imho, so.......you
> cant sign it with someone else's key, but maybe i'm wrong here.
> > t.
> >
> > čt 3. 12. 2020 v 20:25 odesílatel Nathaniel Russell <
> nat...@gm...> napsal:
> >>
> >> But you dont want gen_repos to use ur gpf key these are majntained by
> Sasa not us that is y im asking him for his gpg key to sign all packages.
>
> Ok, I can do a public key and a private one for droplinegnome project
> and we could share that then.
>
> Rgds
> Saxa
> >>
> >> On Thu, Dec 3, 2020 at 12:11 PM Tomáš Bažant <tom...@gm...>
> wrote:
> >>>
> >>> It is always best to have a valid changelog, no donut about it. The
> gpg thing - the `gen_repos_files.sh` script signs the packages with your
> GPG key (see notes at project's sf.net wiki).
> >>> If you want to run `slackpkg update` on a repo whose packages are not
> signed, then you need to update the `/etc/slackpkg/slackpkgplus.conf` file
> and set `STRICTGPG=on`
> >>>
> >>> čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <
> nat...@gm...> napsal:
> >>>>
> >>>> Acutally if you run the gen_repo script of Eric’s it ends up making a
> Blank Changelog.txt file so I would say it is.
> >>>>
> >>>> When you have all the files you need running slackpkg update barfs on
> GPG-KEY for Gnome i will send u a picture 2nite.
> >>>>
> >>>> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <ca...@gm...>
> wrote:
> >>>>>
> >>>>> Out of curiosity, is the Changelog.txt obligatory ?
> >>>>>
> >>>>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
> >>>>> <nat...@gm...> wrote:
> >>>>> >
> >>>>> > This is a start for the slackpkg+ repo files I still have to work
> on the Changelog and get everything in order. When I run my slackpkg update
> it is barfing on a GPG-KEY for the dropline gnome repo.
> >>>>> > Is there any way you have this Key on hand so that I can continue
> to update and the files and help with making this slackpkg+ complaint?
> >>>>> > _______________________________________________
> >>>>> > Dropline-gnome-devel mailing list
> >>>>> > Dro...@li...
> >>>>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> Dropline-gnome-devel mailing list
> >>>>> Dro...@li...
> >>>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >>>>
> >>>> --
> >>>> Nathaniel & LeAnna Russell
> >>>> _______________________________________________
> >>>> Dropline-gnome-devel mailing list
> >>>> Dro...@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >>>
> >>> _______________________________________________
> >>> Dropline-gnome-devel mailing list
> >>> Dro...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >>
> >> --
> >> Nathaniel & LeAnna Russell
> >> _______________________________________________
> >> Dropline-gnome-devel mailing list
> >> Dro...@li...
> >> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >
> > _______________________________________________
> > Dropline-gnome-devel mailing list
> > Dro...@li...
> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
>
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
-- 
Nathaniel & LeAnna Russell

Re: [DLG-dev] Slackpkg+ Complaince

[Sasa O. <ca...@gm...>]

On Thu, Dec 3, 2020 at 9:23 PM Tomáš Bažant <tom...@gm...> wrote:
>
> hi
> you're correct, it should be the repo-owner's key, definitely. but signing them requires the private part of the gpg key imho, so.......you cant sign it with someone else's key, but maybe i'm wrong here.
> t.
>
> čt 3. 12. 2020 v 20:25 odesílatel Nathaniel Russell <nat...@gm...> napsal:
>>
>> But you dont want gen_repos to use ur gpf key these are majntained by Sasa not us that is y im asking him for his gpg key to sign all packages.

Ok, I can do a public key and a private one for droplinegnome project
and we could share that then.

Rgds
Saxa
>>
>> On Thu, Dec 3, 2020 at 12:11 PM Tomáš Bažant <tom...@gm...> wrote:
>>>
>>> It is always best to have a valid changelog, no donut about it. The gpg thing - the `gen_repos_files.sh` script signs the packages with your GPG key (see notes at project's sf.net wiki).
>>> If you want to run `slackpkg update` on a repo whose packages are not signed, then you need to update the `/etc/slackpkg/slackpkgplus.conf` file and set `STRICTGPG=on`
>>>
>>> čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <nat...@gm...> napsal:
>>>>
>>>> Acutally if you run the gen_repo script of Eric’s it ends up making a Blank Changelog.txt file so I would say it is.
>>>>
>>>> When you have all the files you need running slackpkg update barfs on GPG-KEY for Gnome i will send u a picture 2nite.
>>>>
>>>> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <ca...@gm...> wrote:
>>>>>
>>>>> Out of curiosity, is the Changelog.txt obligatory ?
>>>>>
>>>>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
>>>>> <nat...@gm...> wrote:
>>>>> >
>>>>> > This is a start for the slackpkg+ repo files I still have to work on the Changelog and get everything in order. When I run my slackpkg update it is barfing on a GPG-KEY for the dropline gnome repo.
>>>>> > Is there any way you have this Key on hand so that I can continue to update and the files and help with making this slackpkg+ complaint?
>>>>> > _______________________________________________
>>>>> > Dropline-gnome-devel mailing list
>>>>> > Dro...@li...
>>>>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Dropline-gnome-devel mailing list
>>>>> Dro...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>>>
>>>> --
>>>> Nathaniel & LeAnna Russell
>>>> _______________________________________________
>>>> Dropline-gnome-devel mailing list
>>>> Dro...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>>
>>> _______________________________________________
>>> Dropline-gnome-devel mailing list
>>> Dro...@li...
>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>
>> --
>> Nathaniel & LeAnna Russell
>> _______________________________________________
>> Dropline-gnome-devel mailing list
>> Dro...@li...
>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

Re: [DLG-dev] Srry here is the Changelog

[Sasa O. <ca...@gm...>]

On Thu, Dec 3, 2020 at 1:05 PM Nathaniel Russell
<nat...@gm...> wrote:
>
> Yes ur local repo works with a empty changelog but if you look at how things are done in multilib, slackware, sbrepos having a full changelog is the way to go.
A good thing is that works with an empty Changelog. Surely I wont
struggle on how to unify the changelogs of all scripts and make one
big. If an empty
changelog file works this will then be the one.

It gives the user one place to find out everything that has been done
to the project in the past and present instead of looking threw files
and directorys to find out what is going on.

Exactly, but every time you need to find out what happened with a
certain script in the past you have to scroll over and over to find
out. So it has its benefit
but on the same time downsides too. Today with allthat git stuff and
flexibility a changelog even wont be needed anymore, but try to tell
that to the
slackware team :)

Anyway in the past we had a unique changelog, but due to difficulties
we decided to put one in each script folder.

Rgds
Saxa

>
> On Thu, Dec 3, 2020 at 5:58 AM <tom...@gm...> wrote:
>>
>> HI
>>
>> my local repo works with no or empty CHANGELOG.txt so i assume that it
>> is not compulsory
>>
>> Tomas
>>
>>
>> Sasa Ostrouska píše v Čt 03. 12. 2020 v 12:34 +0100:
>> > This can be a bit troublesome, we ship changelog file in each package
>> > and decided to make it per package rather than global one due to a
>> > need of detailed description on what has been done in the package
>> > build script. Also because in the past we had to modify sources and
>> > add patches etc... So one big changelog is a bit difficult to work
>> > with and cames out a mess when looking for what was done.
>> >
>> > On Thu, Dec 3, 2020 at 2:10 AM Nathaniel Russell
>> > <nat...@gm...> wrote:
>> > > Sorry here is the changelog as of what I have completed.
>> > > _______________________________________________
>> > > Dropline-gnome-devel mailing list
>> > > Dro...@li...
>> > > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>> >
>> > _______________________________________________
>> > Dropline-gnome-devel mailing list
>> > Dro...@li...
>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>
>>
>>
>> _______________________________________________
>> Dropline-gnome-devel mailing list
>> Dro...@li...
>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
> --
> Nathaniel & LeAnna Russell
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

Re: [DLG-dev] Slackpkg+ Complaince

[Tomáš B. <tom...@gm...>]

hi
you're correct, it should be the repo-owner's key, definitely. but signing
them requires the private part of the gpg key imho, so.......you cant sign
it with someone else's key, but maybe i'm wrong here.
t.

čt 3. 12. 2020 v 20:25 odesílatel Nathaniel Russell <nat...@gm...>
napsal:

> But you dont want gen_repos to use ur gpf key these are majntained by Sasa
> not us that is y im asking him for his gpg key to sign all packages.
>
> On Thu, Dec 3, 2020 at 12:11 PM Tomáš Bažant <tom...@gm...>
> wrote:
>
>> It is always best to have a valid changelog, no donut about it. The gpg
>> thing - the `gen_repos_files.sh` script signs the packages with your GPG
>> key (see notes at project's sf.net wiki).
>> If you want to run `slackpkg update` on a repo whose packages are not
>> signed, then you need to update the `/etc/slackpkg/slackpkgplus.conf` file
>> and set `STRICTGPG=on`
>>
>> čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <
>> nat...@gm...> napsal:
>>
>>> Acutally if you run the gen_repo script of Eric’s it ends up making a
>>> Blank Changelog.txt file so I would say it is.
>>>
>>> When you have all the files you need running slackpkg update barfs on
>>> GPG-KEY for Gnome i will send u a picture 2nite.
>>>
>>> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <ca...@gm...> wrote:
>>>
>>>> Out of curiosity, is the Changelog.txt obligatory ?
>>>>
>>>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
>>>> <nat...@gm...> wrote:
>>>> >
>>>> > This is a start for the slackpkg+ repo files I still have to work on
>>>> the Changelog and get everything in order. When I run my slackpkg update it
>>>> is barfing on a GPG-KEY for the dropline gnome repo.
>>>> > Is there any way you have this Key on hand so that I can continue to
>>>> update and the files and help with making this slackpkg+ complaint?
>>>> > _______________________________________________
>>>> > Dropline-gnome-devel mailing list
>>>> > Dro...@li...
>>>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>>>
>>>>
>>>> _______________________________________________
>>>> Dropline-gnome-devel mailing list
>>>> Dro...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>>>
>>> --
>>> Nathaniel & LeAnna Russell
>>> _______________________________________________
>>> Dropline-gnome-devel mailing list
>>> Dro...@li...
>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>>
>> _______________________________________________
>> Dropline-gnome-devel mailing list
>> Dro...@li...
>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>
> --
> Nathaniel & LeAnna Russell
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>

Re: [DLG-dev] Slackpkg+ Complaince

[Nathaniel R. <nat...@gm...>]

But you dont want gen_repos to use ur gpf key these are majntained by Sasa
not us that is y im asking him for his gpg key to sign all packages.

On Thu, Dec 3, 2020 at 12:11 PM Tomáš Bažant <tom...@gm...> wrote:

> It is always best to have a valid changelog, no donut about it. The gpg
> thing - the `gen_repos_files.sh` script signs the packages with your GPG
> key (see notes at project's sf.net wiki).
> If you want to run `slackpkg update` on a repo whose packages are not
> signed, then you need to update the `/etc/slackpkg/slackpkgplus.conf` file
> and set `STRICTGPG=on`
>
> čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <
> nat...@gm...> napsal:
>
>> Acutally if you run the gen_repo script of Eric’s it ends up making a
>> Blank Changelog.txt file so I would say it is.
>>
>> When you have all the files you need running slackpkg update barfs on
>> GPG-KEY for Gnome i will send u a picture 2nite.
>>
>> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <ca...@gm...> wrote:
>>
>>> Out of curiosity, is the Changelog.txt obligatory ?
>>>
>>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
>>> <nat...@gm...> wrote:
>>> >
>>> > This is a start for the slackpkg+ repo files I still have to work on
>>> the Changelog and get everything in order. When I run my slackpkg update it
>>> is barfing on a GPG-KEY for the dropline gnome repo.
>>> > Is there any way you have this Key on hand so that I can continue to
>>> update and the files and help with making this slackpkg+ complaint?
>>> > _______________________________________________
>>> > Dropline-gnome-devel mailing list
>>> > Dro...@li...
>>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>>
>>>
>>> _______________________________________________
>>> Dropline-gnome-devel mailing list
>>> Dro...@li...
>>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>>
>> --
>> Nathaniel & LeAnna Russell
>> _______________________________________________
>> Dropline-gnome-devel mailing list
>> Dro...@li...
>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
-- 
Nathaniel & LeAnna Russell

Re: [DLG-dev] Slackpkg+ Complaince

[Tomáš B. <tom...@gm...>]

It is always best to have a valid changelog, no donut about it. The gpg
thing - the `gen_repos_files.sh` script signs the packages with your GPG
key (see notes at project's sf.net wiki).
If you want to run `slackpkg update` on a repo whose packages are not
signed, then you need to update the `/etc/slackpkg/slackpkgplus.conf` file
and set `STRICTGPG=on`

čt 3. 12. 2020 v 18:13 odesílatel Nathaniel Russell <nat...@gm...>
napsal:

> Acutally if you run the gen_repo script of Eric’s it ends up making a
> Blank Changelog.txt file so I would say it is.
>
> When you have all the files you need running slackpkg update barfs on
> GPG-KEY for Gnome i will send u a picture 2nite.
>
> On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <ca...@gm...> wrote:
>
>> Out of curiosity, is the Changelog.txt obligatory ?
>>
>> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
>> <nat...@gm...> wrote:
>> >
>> > This is a start for the slackpkg+ repo files I still have to work on
>> the Changelog and get everything in order. When I run my slackpkg update it
>> is barfing on a GPG-KEY for the dropline gnome repo.
>> > Is there any way you have this Key on hand so that I can continue to
>> update and the files and help with making this slackpkg+ complaint?
>> > _______________________________________________
>> > Dropline-gnome-devel mailing list
>> > Dro...@li...
>> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>
>>
>> _______________________________________________
>> Dropline-gnome-devel mailing list
>> Dro...@li...
>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>>
> --
> Nathaniel & LeAnna Russell
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>

Re: [DLG-dev] Slackpkg+ Complaince

[Nathaniel R. <nat...@gm...>]

Acutally if you run the gen_repo script of Eric’s it ends up making a Blank
Changelog.txt file so I would say it is.

When you have all the files you need running slackpkg update barfs on
GPG-KEY for Gnome i will send u a picture 2nite.

On Thu, Dec 3, 2020 at 5:33 AM Sasa Ostrouska <ca...@gm...> wrote:

> Out of curiosity, is the Changelog.txt obligatory ?
>
> On Thu, Dec 3, 2020 at 1:58 AM Nathaniel Russell
> <nat...@gm...> wrote:
> >
> > This is a start for the slackpkg+ repo files I still have to work on the
> Changelog and get everything in order. When I run my slackpkg update it is
> barfing on a GPG-KEY for the dropline gnome repo.
> > Is there any way you have this Key on hand so that I can continue to
> update and the files and help with making this slackpkg+ complaint?
> > _______________________________________________
> > Dropline-gnome-devel mailing list
> > Dro...@li...
> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
>
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
-- 
Nathaniel & LeAnna Russell

Re: [DLG-dev] Srry here is the Changelog

[Nathaniel R. <nat...@gm...>]

Yes ur local repo works with a empty changelog but if you look at how
things are done in multilib, slackware, sbrepos having a full changelog is
the way to go. It gives the user one place to find out everything that has
been done to the project in the past and present instead of looking threw
files and directorys to find out what is going on.

On Thu, Dec 3, 2020 at 5:58 AM <tom...@gm...> wrote:

> HI
>
> my local repo works with no or empty CHANGELOG.txt so i assume that it
> is not compulsory
>
> Tomas
>
>
> Sasa Ostrouska píše v Čt 03. 12. 2020 v 12:34 +0100:
> > This can be a bit troublesome, we ship changelog file in each package
> > and decided to make it per package rather than global one due to a
> > need of detailed description on what has been done in the package
> > build script. Also because in the past we had to modify sources and
> > add patches etc... So one big changelog is a bit difficult to work
> > with and cames out a mess when looking for what was done.
> >
> > On Thu, Dec 3, 2020 at 2:10 AM Nathaniel Russell
> > <nat...@gm...> wrote:
> > > Sorry here is the changelog as of what I have completed.
> > > _______________________________________________
> > > Dropline-gnome-devel mailing list
> > > Dro...@li...
> > > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> >
> > _______________________________________________
> > Dropline-gnome-devel mailing list
> > Dro...@li...
> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
>
>
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
-- 
Nathaniel & LeAnna Russell

Re: [DLG-dev] Srry here is the Changelog

[<tom...@gm...>]

HI

my local repo works with no or empty CHANGELOG.txt so i assume that it
is not compulsory

Tomas


Sasa Ostrouska píše v Čt 03. 12. 2020 v 12:34 +0100:
> This can be a bit troublesome, we ship changelog file in each package
> and decided to make it per package rather than global one due to a
> need of detailed description on what has been done in the package
> build script. Also because in the past we had to modify sources and
> add patches etc... So one big changelog is a bit difficult to work
> with and cames out a mess when looking for what was done.
> 
> On Thu, Dec 3, 2020 at 2:10 AM Nathaniel Russell
> <nat...@gm...> wrote:
> > Sorry here is the changelog as of what I have completed.
> > _______________________________________________
> > Dropline-gnome-devel mailing list
> > Dro...@li...
> > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
> 
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

Re: [DLG-dev] Srry here is the Changelog

[Sasa O. <ca...@gm...>]

This can be a bit troublesome, we ship changelog file in each package
and decided to make it per package rather than global one due to a
need of detailed description on what has been done in the package
build script. Also because in the past we had to modify sources and
add patches etc... So one big changelog is a bit difficult to work
with and cames out a mess when looking for what was done.

On Thu, Dec 3, 2020 at 2:10 AM Nathaniel Russell
<nat...@gm...> wrote:
>
> Sorry here is the changelog as of what I have completed.
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel