Re: [Slackbuilds-users] office/when has [moved]

2023-04-12 Thread Jan Sucan
On Sun, 29 Jan 2023 16:41:06 -0500 (EST)
"B. Watson"  wrote:

> On Sun, 29 Jan 2023, j+sbo-us...@maschinengott.de wrote:
> 
> > https://bitbucket.org/ben-crowell/when
> >
> > found via: https://github.com/bcrowell/  
> >> Because of Microsoft's harmful activities in AI, I am moving my
> >> software   
> > from github to https://bitbucket.org/ben-crowell/ .  
> 
> Good deal.
> 
> However, it doesn't help with the SlackBuild: I don't see any release
> tarballs at bitbucket either, so the script and .info file still will
> have to be changed. Rather the maintainer do that, but I will do it
> eventually if we don't hear back from him...

Hi, 

Sorry for the delay. I will modify the SlackBuild to use the source
from Debian.

I discussed releasing tarballs at GitHub with the author of 'when' some
years ago. He was very open to it. I will try to contact him again.
Maybe we will be able to switch back to the original source.

Thanks,
Jan
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] office/when has [moved]

2023-01-30 Thread Qun-Ying
If you look at:
https://bitbucket.org/ben-crowell/when/downloads/?tab=tags, you have
all the tar ball could be download from the tags.

On 1/30/23, Daniel Prosser  wrote:
> If we can't find the source tarball, maybe the name should be changed to
> "where" instead of "when".
>
> Apologies for the bad joke.
>
> On 1/29/23 16:41, B. Watson wrote:
>>
>>
>> On Sun, 29 Jan 2023, j+sbo-us...@maschinengott.de wrote:
>>
>>> https://bitbucket.org/ben-crowell/when
>>>
>>> found via: https://github.com/bcrowell/
 Because of Microsoft's harmful activities in AI, I am moving my
 software
>>> from github to https://bitbucket.org/ben-crowell/ .
>>
>> Good deal.
>>
>> However, it doesn't help with the SlackBuild: I don't see any release
>> tarballs at bitbucket either, so the script and .info file still will
>> have to be changed. Rather the maintainer do that, but I will do it
>> eventually if we don't hear back from him...
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


-- 
Qun-Ying
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] office/when has [moved]

2023-01-30 Thread Daniel Prosser
If we can't find the source tarball, maybe the name should be changed to 
"where" instead of "when".


Apologies for the bad joke.

On 1/29/23 16:41, B. Watson wrote:



On Sun, 29 Jan 2023, j+sbo-us...@maschinengott.de wrote:


https://bitbucket.org/ben-crowell/when

found via: https://github.com/bcrowell/
Because of Microsoft's harmful activities in AI, I am moving my 
software 

from github to https://bitbucket.org/ben-crowell/ .


Good deal.

However, it doesn't help with the SlackBuild: I don't see any release
tarballs at bitbucket either, so the script and .info file still will
have to be changed. Rather the maintainer do that, but I will do it
eventually if we don't hear back from him...
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] office/when has [moved]

2023-01-29 Thread B. Watson




On Sun, 29 Jan 2023, j+sbo-us...@maschinengott.de wrote:


https://bitbucket.org/ben-crowell/when

found via: https://github.com/bcrowell/
Because of Microsoft's harmful activities in AI, I am moving my software 

from github to https://bitbucket.org/ben-crowell/ .


Good deal.

However, it doesn't help with the SlackBuild: I don't see any release
tarballs at bitbucket either, so the script and .info file still will
have to be changed. Rather the maintainer do that, but I will do it
eventually if we don't hear back from him...
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] office/when has [moved]

2023-01-29 Thread j+sbo-users

https://bitbucket.org/ben-crowell/when

found via: https://github.com/bcrowell/
> Because of Microsoft's harmful activities in AI, I am moving my 
software from github to https://bitbucket.org/ben-crowell/ .


On 28.01.23 06:03, B. Watson wrote:


It looks like upstream's removed the github repo for this...

The homepage has a source tarball, but the SlackBuild is going
to need changes to build it from that. Plus, the filename has no
version number in it, meaning it's going to get replaced when upstream
releases the next version (breaking our build). They don't seem to
keep old versions on that site.

I couldn't find a copy of the github-generated source tarball
anywhere. Apparently it was only available for a few days.
web.archive.org has 1.1.44, but not 1.1.45.

I did find a copy of the 1.1.45 source here:

http://deb.debian.org/debian/pool/main/w/when/when_1.1.45.orig.tar.xz

The md5sum doesn't match, possibly just because it's a .xz file
instead of .gz. Also, the SlackBuild would need changes to use this
filename.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/