Hi,
On Tue, 13 Oct 2020, at 06:53, Noah Meyerhans wrote:
> On Fri, Oct 09, 2020 at 12:14:23PM +0200, Stephan Seitz wrote:
> > That’s why I need to know the different programs anyway. Why would I go for
> > something like open which can only use one program for the file type?
> You wouldn't, but
Hi,
it's nice that you want to make the software available for others, but
this task is simply way to simple to have a special package for it.
The whole thing can be done with a few shell commands, so there is no
need for a tool in my opinion.
For example a perl oneliner doing the line substit
Hi pe pi and others,
Quoting Alex Mestiashvili (2020-10-13 09:54:15)
> it's nice that you want to make the software available for others, but
> this task is simply way to simple to have a special package for it.
> The whole thing can be done with a few shell commands, so there is no
> need for
Hi,
it doesnt matter if it is written in c language or perl script or in
something else
main goal is to make it that simple, how can it be
and as a part of linux main install, not as an optional package
available in every variants of shell
pe pi
On 13. 10. 2020 9:54, Alex Mestiashvili wrote:
Hi,
FYI:
I'm able to run archive rebuilds on a quite regular basis. I do that to
find (and file) FTBFS bugs, but it's also possible to test candidate
changes in Debian (for example, new versions of compilers, interpreters,
or other packages that are common build-depends).
If that's useful for you
Hi All,
libtracevent is currently being packaged from the linux kernel source
and as such it has the version of '5.8.14-1' same as the kernel. As
reported in #971976, the upstream libtraceevent now lives in its own
repo and has a version of '1.1.0'
So, I will need to add an epoch to the version to
On Fri, Oct 09, 2020 at 09:00:44PM -0500, Brett Gilio wrote:
> I am a long term user of Debian GNU/Linux (and a regular contributor to
> GNU Guix). I have been using Debian or some other variant of GNU/Linux
> for 10+ years, in both professional and personal capacities. I notice
> that some package
On Tue, Oct 13, 2020 at 09:52:24AM -0700, Dmitry Borodaenko wrote:
> Sounds like your interests are relevant for the Debian Science team [2]
> (which is marked dead) and Debian Science Maintainers team [3], getting
> in touch with them would be a good place to start.
Oops, messed up my references,
* Noah Meyerhans [201013 00:54]:
> "open" is a verb commonly used to describe the action of accessing a
> file in Linux. You used it yourself above, and it's one of the most
> prominent functions in the file API. It seems sensible to provide a
> tool that matches the verb most commonly used to d
On Tue, Oct 13, 2020 at 1:52 PM Marvin Renich wrote:
>
> * Noah Meyerhans [201013 00:54]:
> > "open" is a verb commonly used to describe the action of accessing a
> > file in Linux. You used it yourself above, and it's one of the most
> > prominent functions in the file API. It seems sensible t
Hi all
(please Cc)
is there a way to update hopelessly broken packages in Ubuntu Focal LTS?
(packages in question are onedrive and in particular calibre - I refrain
from commenting on the reasons behind calibre)
Ubuntu seems to pull at arbitrary intervals rather incomplete packages
that end up
On Wed, 14 Oct 2020, Norbert Preining wrote:
Hi all
(please Cc)
is there a way to update hopelessly broken packages in Ubuntu Focal LTS?
(packages in question are onedrive and in particular calibre - I refrain
from commenting on the reasons behind calibre)
Ubuntu seems to pull at arbitrary i
On Wed, 14 Oct 2020 07:23:58 +0900,
Norbert Preining wrote:
>Hi all
>
>(please Cc)
>
>is there a way to update hopelessly broken packages in Ubuntu Focal
>LTS?
>
>(packages in question are onedrive and in particular calibre - I
>refrain from commenting on the reasons behind calibre)
>
>Ubuntu seem
Dmitry Borodaenko writes:
>
> Generally speaking, the best way to set up collaborative maintenance for
> such packages is to put them up on Salsa [0], for that you'll need to
> convert them to Git packaging [1] if they aren't already on it (e.g.
> blank VCS field for MLton tells me that it's not)
Hi Scott, hi Andreas,
thanks for your answers.
On Tue, 13 Oct 2020, Scott Talbert wrote:
> better discussed on an Ubuntu mailing list, rather than Debian.
I have sent an email to ubuntu-devel with detailed explanations.
I hoped for some contact here of a Debian *and* Ubuntu developer with
exper
Brett Gilio writes:
>
> Could you explain what "marked dead" means in this context? Is the
> Debian Science team different from the Debian Science Maintainers team?
> Thank you for clarifying the issue.
Update, I see what you mean. The blend mailing list is marked dead.
--
Brett M. Gilio
http
Dmitry Borodaenko writes:
>
> Oops, messed up my references, above should read: "Debian Science
> mailing list (which is marked dead)[2] and Debian Science Maintainers
> team [3]"
>
> [2] https://lists.debian.org/debian-science/
> [3] https://wiki.debian.org/DebianScience
It sounds like the Debi
Brett Gilio writes:
> It sounds like the Debian Science Maintainers team uses
> https://alioth.debian.org/, but that URL is not resolving.
Update: Ignore this, just a case of an outdated Wiki. :)
--
Brett M. Gilio
https://brettgilio.com
Thank you, Norbert, for trying to get this fixed. calibre upstream
already had 6 bug reports and counting in just the last week, for an issue:
- that was fixed in May
- only applicable to people field-testing the python3 transition which
was marked as beta and is currently superseded by stable r
19 matches
Mail list logo
