: grep rough audit - source code auditing tool
This is a simple script and signature sets that allows you to find
potential
security flaws in source code using the GNU utility grep. It's
comparable to
other static analysis applications like RATS, SWAAT and flaw-finder
while
keeping
Quoting Otto Kekäläinen (2024-03-30 22:09:46)
> Is it so that the debian/copyright file is reviewed by ftp-masters
> only for packages in NEW queue, and there is probably no automation in
> place to flag subsequent copyright changes for re-review?
It is my understanding that it is, and always has
credited, in the event of some sort of criminal or civil liability
attaching to the work. The xz backdoor and the mysterious identity of
its perpetrator(s) should underscore this concern.
> Having source code in the public domain means that there is no
> copyright, so no attribution required ei
Hi!
While reviewing xz-utils commits I noticed that a bunch of old
copyright holder names were removed in
https://salsa.debian.org/debian/xz-utils/-/commit/d1b67558cbc06c449a0ae7b7c1694e277aef4a78.
Is this OK to do so? Having source code in the public domain means
that there is no copyright, so
: Apache-2
Programming Lang: Python
Description : Source-to-source code translator for Fortran
Loki is an experimental tool to explore the possible use of
source-to-source translation for ECMWF's Integrated Forecasting System (IFS) and
associated Fortran software packages.
Loki is based
t should not contain any actual source code, only
> pointing to the real package(via "Depends" field).
Transitional packages are binary packages, talking about source code is
not relevant here. And all binary packages are built from source packages
even if they are mostly empty.
>
Hello Debian Community,
I need to define a transitional package like debian Renaming Packages Method
<https://wiki.debian.org/RenamingPackages#Transition_package_method>.
Since it is transitional it should not contain any actual source code, only
pointing to the real package(via "Dep
: MIT
Programming Lang: javascript
Description : Low footprint JavaScript source code parser
Tool that allows you to analyze ECMAScript (JavaScript) code efficiently
and with low resource usage. The main objective is to examine the JavaScript
source code for various information
Package: wnpp
Severity: wishlist
Owner: Matthias Geiger
X-Debbugs-Cc: debian-devel@lists.debian.org,
pkg-rust-maintain...@alioth-lists.debian.net, werdah...@riseup.net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: rust-bindgen-cli
Version : 0.66.1
Upstream
* License : Apache-2.0 or Expat
Programming Lang: Rust
Description : pure-rust Noise Protocol Framework implementation - Rust
source code
The snow crate is a straightforward,
Hard To Fuck Up™ Noise Protocol implementation.
.
The Noise Protocol Framework is a set of crypto protocols
: CRC C source code generator
pycrc is a Cyclic Redundancy Check (CRC) C source code generator.
.
It supports different implementations, with various speed-space
compromises. The CRC parameters can be freely chosen, and pycrc
includes a number of well-known CRC models (CRC-16, CRC-32 etc
: BSD-2-clause
Programming Lang: Python
Description : include source code from any Sphinx project using only its
import path
Sphinx-code-include is an extension for Sphinx that lets you render
source-code of any class or function directly into your Sphinx documentation
using only
: https://metacpan.org/pod/String::License
* License : AGPL-3+
Programming Lang: Perl
Description : detect source code license statements in a text string
String::License identifies license statements in a string
and serializes them in a normalized format.
This package is a fork
Package: wnpp
Severity: normal
X-Debbugs-Cc: debian-devel@lists.debian.org
Control: affects -1 src:highlight
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I request assistance with maintaining the highlight package.
I have not really been keeping up with new upstream releases and could
use a
Your message dated Thu, 30 Jun 2022 10:22:58 +0200
with message-id <20220630082257.dfe35x2cghs7a...@gpm.stappers.nl>
and subject line Too broad
has caused the Debian Bug report #1014029,
regarding invisible malicious unicode in source code - detection and prevention
to be marked a
Your text is quite chaotic, it is hard to distinguish the quotes from
your ideas what to do in Debian.
I think the main problem here are the programs which are presenting
source code to humans (text editors, terminals, HTML pages in Gitlab
etc.).
Quotes should always terminate everything
-submodules
* License : LGPL-2+
Programming Lang: C
Description : MATE source code required by several components
Since MATE 1.26 some code has been moved into a separate code
repository that gets pulled in as submodules. In Debian, we
will handle this by providing the source code
On 10/11/21 11:20 AM, Yadd wrote:
> For now:
>
> $ cat tags/s/source-contains-prebuilt-javascript-object.tag
> Tag: source-contains-prebuilt-javascript-object
> Severity: pedantic
> Check: cruft
> Explanation: The source tarball contains a prebuilt (minified)
>JavaScript object.
>
ussion, it should be a "Severity: error",
> shouldn't it?
I expect it would only be an error if the original source code for
it is not also included somewhere in main (either in the same source
package or another one), though how to be certain of that is a topic
for debate. If the ups
they had eiffel sources, and the
>> C code was preprocessed and didn't allow/permit bootstrapping. It took some
>
> This is a good example, because it shows how "source code" is defined by
> what upstream development uses, not merely by users being able to compile
>
didn't allow/permit bootstrapping. It took some
This is a good example, because it shows how "source code" is defined by
what upstream development uses, not merely by users being able to compile
the released code.
But the situation here seems to be the opposite: The minified javascript
*is*
00), Yadd wrote: [...]
> > > > > If you really consider minified files as binary, there's a
> > > > > room for creating a lot of RC bugs
> > > >
> > > > The more appropriate question is whether Debian considers
> > > > minified fil
Quoting Stephan Verbücheln (2021-10-10 14:03:51)
> On Sat, 2021-10-09 at 18:52 +0200, Jonas Smedegaard wrote:
> > It is not source code.
> >
> > It is not binary code.
> >
> > It is not...
> >
> > The appropriate question is how it fits Debia
.]
> > > > If you really consider minified files as binary, there's a room
> > > > for creating a lot of RC bugs
> > >
> > > The more appropriate question is whether Debian considers minified
> > > files to be source code, or a compiled form. To needl
On Sat, 2021-10-09 at 18:52 +0200, Jonas Smedegaard wrote:
> It is not source code.
>
> It is not binary code.
>
> It is not...
>
> The appropriate question is how it fits Debian Free Software
> Guidelines.
Programs with a license on the one hand which demands the r
creating a lot of RC bugs
> >
> > The more appropriate question is whether Debian considers minified
> > files to be source code, or a compiled form. To needlessly quote
> > DFSG §2: "The program must include source code, and must allow
> > distribution in sourc
ebian considers minified
> files to be source code, or a compiled form. To needlessly quote
> DFSG §2: "The program must include source code, and must allow
> distribution in source code as well as compiled form."
>
Minified code isn't code in a form meant/supposed to be modified by hand,
so it's not source code.
J. Puydt
>
On 2021-10-09 08:53:57 +0200 (+0200), Yadd wrote:
[...]
> If you really consider minified files as binary, there's a room for
> creating a lot of RC bugs
The more appropriate question is whether Debian considers minified
files to be source code, or a compiled form. To needlessly quote
D
Le 08/10/2021 à 22:54, Thomas Goirand a écrit :
> On 10/8/21 10:20 AM, Yadd wrote:
>> Take a look, most of them embed a minified version (jquery* for example)
> Yeah ... Everyone upstream thinks it's ok to have 15907152438 copies of
> jquery floating around... There's room for improvement for
On 10/8/21 10:20 AM, Yadd wrote:
> Take a look, most of them embed a minified version (jquery* for example)
Yeah ... Everyone upstream thinks it's ok to have 15907152438 copies of
jquery floating around... There's room for improvement for sure! :)
Thomas Goirand (zigo)
different ways of testing a code.
>
> Option 1: Agree, we should allow these files in main
> Option 2: Disagree, we should not allow these files in main
> Option 3: Further discussion
>
>
A few problems with what you wrote above...
* Please don't use the word "minified" w
onsidering the tradeoffs involved.
Hang on, let me consider ... done ! :)
I do not think you'll go as far as saying that running unit (or
functional) tests using blobs is superior to do that using source only
tests (or built from source libraries to run tests). We shall have, as a
goal, to shi
dition to the
limitations described about them being used only for tests) limited to
only JavaScript code which compared to its source code only has had
unnecessary characters removed without changing its functionality (based
on Wikipedia article on Minification).
I think composing the ballo
Draft text for the GR (this is my first time proposing a GR text, so
help is welcome to make the text clearer).
We should not worry about minified files in main that are (a) only in
the source package and not in any binary package, and (b) only used to
run tests, not to build the binary
en
Hi,
this files are used for test only, maybe severity could be
decreased.
I find the severity accurate: Relying on non-source code is a
severe
violation of Debian Policy, not matter the purpose of relying on
it.
I think we should change the policy here. Running tests helps
improve
th
On വ്യാ, ഒക്ടോ 7 2021 at 11:43:52 രാവിലെ
-0700 -0700, Russ Allbery wrote:
Jonas Smedegaard writes:
Right: It is ok to use upstream-provided pre-minified code, as long
as
that code is DFSG-free, which requires the source of that code must
exist in Debian.
...and because that is
The debug version is compiled without source (lintian warn) and
>>>>> moreover the
>>>>> > rest of file are already packaged
>>>>> >
>>>>> > grep -R vendor * gives only a few hit that could be cured by
>>>>> symlinking
>>
ry should be emptied
>>>>>> >
>>>>>> > The debug version is compiled without source (lintian warn) and
>>>>>> moreover the
>>>>>> > rest of file are already packaged
>>>>>> >
>>>>>&
ource (lintian warn) and
>>>>> moreover the
>>>>> > rest of file are already packaged
>>>>> >
>>>>> > grep -R vendor * gives only a few hit that could be cured by
>>>>> symlinking
>>>>> >
>
Jonas Smedegaard writes:
> Right: It is ok to use upstream-provided pre-minified code, as long as
> that code is DFSG-free, which requires the source of that code must
> exist in Debian.
> ...and because that is often complicated to ensure (not because it
> violates DFSG in itself), it is
case, I personally don't see a big problem with them being
> vendored as opposed to using system copies.
>
> But AFAIK, they do still need to be DFSG-free to be in main if they
> are in the source tarball. And I personally would not consider
> minified JS (if that is indeed at issue he
would not consider minified JS
(if that is indeed at issue here) to be "source code".
--
Richard
OpenPGP_signature
Description: OpenPGP digital signature
Richard Laager writes:
> I haven't looked into the specifics of this situation, but in general,
> tests should be run against the same versions of dependencies that the
> actual code will use, for what should be obvious reasons. If Debian has
> the dependencies with different API versions, then
On 10/7/21 4:40 AM, Pirate Praveen wrote:
What you are proposing would require the package maintainer to adapt these
tests to versions available (many times with different API versions) in Debian
and the easier choice is disabling tests.
I haven't looked into the specifics of this situation,
an warn)
> >>>> > and moreover the rest of file are already packaged
> >>>> >
> >>>> > grep -R vendor * gives only a few hit that could be cured by
> >>>> > symlinking
> >>>> >
> >>>> &
rest of file are already packaged
>>>>>>
>>>>>> grep -R vendor * gives only a few hit that could be cured by
>>>>>> symlinking
>>>>> this files are used for test only, maybe severity could be
>>>>> decreased.
>
e already packaged
>>>> >
>>>> > grep -R vendor * gives only a few hit that could be cured by
>>>> symlinking
>>>> >
>>>> > Bastien
>>>> Hi,
>>>>
>>>> this files are used for test onl
ed
>>>> >
>>>> > grep -R vendor * gives only a few hit that could be cured by
>>>> symlinking
>>>> >
>>>> > Bastien
>>>> Hi,
>>>>
>>>> this files are used for test only, maybe severity co
;>> >
>>> > The debug version is compiled without source (lintian warn) and
>>> moreover the
>>> > rest of file are already packaged
>>> >
>>> > grep -R vendor * gives only a few hit that could be cured by
>>> symlink
hit that could be cured by
symlinking
>
> Bastien
Hi,
this files are used for test only, maybe severity could be
decreased.
I find the severity accurate: Relying on non-source code is a severe
violation of Debian Policy, not matter the purpose of relying on it.
I think we should change
-docgen
* License : Apache-2.0 OR GPL-3.0-or-later
Programming Lang: Python
Description : source code documentation tool using GObject-Introspection
GI-DocGen is a document generator for GObject-based libraries. GObject
is the base type system of the GNOME project. GI-Docgen reuses
Package: wnpp
Severity: wishlist
Owner: Adam Cecile
* Package name: python-prestring
Version : 0.9.0
Upstream Author : Podhmo
* URL : https://github.com/podhmo/prestring
* License : Expat
Programming Lang: Python
Description : Source code generation
Hi,
On Thu, Mar 11, 2021 at 12:59:25PM +0530, Manikant Singh wrote:
> Hi Team,
>
> I am IIT Kanpur student. I am trying to build debian package from source
> code after making some changes to it.
> Though I am able to make changes and build debian package successfully,
> s
Hi Team,
I am IIT Kanpur student. I am trying to build debian package from source
code after making some changes to it.
Though I am able to make changes and build debian package successfully,
some of the changes are not reflected.
I made changes to corefile.c which are correctly reflected
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 07 Feb 2021 15:35:32 +0100
Source: gedit-source-code-browser-plugin
Architecture: source
Version: 3.0.3-6
Distribution: unstable
Urgency: medium
Maintainer: Pietro Battiston
Changed-By: Pietro Battiston
Changes:
gedit
transforms tokens into source code
Untokenize transforms tokens into source code.
.
Unlike the standard library's tokenize.untokenize(), it preserves the original
whitespace between tokens.
This package is a dependency of python-docformatter which is a dependency of
python-xsdata.
I intend to maintain
)
* URL : https://github.com/eProsima/Fast-DDS-Gen
* License : Apache-2
Programming Lang: Java
Description : IDL source code generator for eProsima FastDDS
eProsima Fast DDS-Gen is a Java application that generates source code
for eProsima Fast DDS using the data types
the build tools that allow
compiling ONLYOFFICE
Desktop Editors
from source code
. Here
https://helpcenter.onlyoffice.com/desktop/documents/linux/compile-desktop.aspx
you will find an example of compiling the source code for
Ubuntu
14.04
. You can adapt this instruction and compile the source
Le 19/05/2020 à 17:24, olivier sallou a écrit :
>
>
> Le mar. 19 mai 2020 à 16:48, Kseniya Fedoruk
> mailto:kseniya.fedo...@onlyoffice.com>>
> a écrit :
>
> Hi team,
>
> I'm Kseniyafrom ONLYOFFICE. We are developingopen-source office
> applications, including the absolutely free
: Universal grep: ultra fast searcher of file systems, text
and binary files, source code, archives, compressed files, documents, and more.
NEW ultra fast grep with interactive query UI: search file systems,
text, source code, binary files, archives (cpio/tar/pax/zip), compressed
files (zip/gz/Z/bz2
> With the latest version we also released the build tools that allow compiling
> ONLYOFFICE Desktop Editors from source code. Here
> *https://helpcenter.onlyoffice.com/desktop/documents/linux/compile-desktop.aspx*
> <https://helpcenter.onlyoffice.com/desktop/documents/linux/compile-de
On Tue, 2020-05-19 at 14:25 +, Kseniya Fedoruk wrote:
> Hi team,
>
> I'm Kseniya from ONLYOFFICE. We are developing open-source office
> applications, including the absolutely free ONLYOFFICE Desktop
> Editors that provide alternatives to MS Office Word, Excel, and
> PowerPoint distributed
Package: wnpp
Severity: wishlist
Owner: Ian Campbell
* Package name: cmake-format
Version : 0.6.10
Upstream Author : Josh Bialkowski
* URL : https://github.com/cheshirekow/cmake_format
* License : GPL-3
Programming Lang: Python
Description : source
Package: wnpp
Severity: wishlist
Owner: Joenio Costa
* Package name: analizo
Version : 1.23.0
Upstream Author : Joenio Costa
* URL : http://www.analizo.org
* License : GPL-3+
Programming Lang: Perl
Description : multi-language source code analysis
: Python
Description : highlights source code blocks in chat window
It uses markdown-style syntax, i.e. text in-between `single backticks` is
rendered as inline code,
```language
selection is possible in multi-line code snippets in between triple-backticks
Note the newlines in this case…
```
++ source code transformation tool
automates the otherwise time consuming, error prone process of generating type
descriptors for HDF5 Compound datatypes by building the AST of a given TU
translation unit, and identifying all POD datatypes referenced from H5CPP
operators/functions. The result
Srinivas Rao writes:
> Hi Debian devel team,
>
> I am planning to work on small IoT kind of project using Debian OS. I would
> like to customize Debian OS. could you please tell me, where can I get or
> download Debian source code and how can I create build system.
>
&g
Boyuan Yang writes ("Re: Reg: Debian Source code"):
> Here are some resources that I am aware of:
>
> * By running "apt source ", you will be able to retrieve the
> source code for that certain source package that corresponds to the
> you indicated.
`dgi
Hi Srinivas,
The whole Debian system is made up of all packages in Debian. If you are able
to (re)build all the packages, it is equivalent to (re)building the whole
system.
Similarly, if you retrieve the package source code for all Debian packages, it
is equivalent to having retrieved the source
Quoting Srinivas Rao (2019-03-13 08:03:12)
> As you said, it is only for specific package customization process. I
> would like to know the entire Debian source code build procedure .
> please let me know, how can I get entire Debian 9.8 stretch source
> code and how can I create
Dear Simon Ritcher,
Thanks for your reply.
As you said, it is only for specific package customization process. I would
like to know the entire Debian source code build procedure . please let me
know, how can I get entire Debian 9.8 stretch source code and how can I create
build system
Hi,
On 12.03.19 13:33, Srinivas Rao wrote:
> I am planning to work on small IoT kind of project using Debian OS. I
> would like to customize Debian OS. could you please tell me, where can I
> get or download Debian source code and how can I create build system.
Debian is sel
Hi Debian devel team,
I am planning to work on small IoT kind of project using Debian OS. I would
like to customize Debian OS. could you please tell me, where can I get or
download Debian source code and how can I create build system.
please let me know if any need anymore details.
Thanks
for source code navigation for a cargo project
rusty-tags is a command-line tool that creates tags for source code
navigation using ctags for a cargo project, all of its direct and
indirect dependencies and the Rust standard library.
I intend to package rusty-tags as part of the Rust packaging team
: Apache-2.0
Description: Strip rustdoc comments from source code
rustdoc-stripper is a tool used to remove rustdoc comments from your code and
save them in a comments.cmts file if you want to regenerate them.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 10 Jun 2018 16:42:35 +0300
Source: gedit-source-code-browser-plugin
Binary: gedit-source-code-browser-plugin
Architecture: source
Version: 3.0.3-5.1
Distribution: unstable
Urgency: medium
Maintainer: Pietro Battiston
Changed
Ansgar Burchardt writes ("Re: Want to make salsa advertise contact and source
code details [and 1 more messages]"):
> That seems like an horrible maintenance nightmare just to avoid even
> talking to upstream...
OK, so does someone in Debian, maybe from the Salsa team, have any
On Fri, 2018-05-25 at 18:57 +0100, Ian Jackson wrote:
> Another way to achieve the effect I want would be to do it post-hoc in
> a reverse proxy. I see that salsa is using Apache as a reverse proxy.
> So perhaps the right answer is to do this in Apache. It seems quite
> hacky, but if it's
Ian Jackson writes ("Re: Want to make salsa advertise contact and source code
details [and 1 more messages]"):
> Oh, quite possibly. I don't know anything about gitlab's plugin
> system.
... I don't think so, in fact. I found this documentation:
https://docs.gitlab.com/c
Jonathan Carter writes ("Re: Want to make salsa advertise contact and source
code details [and 1 more messages]"):
> On 25/05/2018 19:16, Ian Jackson wrote:
> > Can you please tell me what you think the appropriate path or venue is
> > for me to pursue this diagreement ?
On Fri, 25 May 2018, Ian Jackson wrote:
> Alexander Wirt writes ("Re: Want to make salsa advertise contact and source
> code details [and 1 more messages]"):
> > It was a decision by the team to disallow any patch that is not
> > really really needed for functi
*rings chimes*
On 25/05/2018 19:16, Ian Jackson wrote:
> Can you please tell me what you think the appropriate path or venue is
> for me to pursue this diagreement ?
I notice GitLab has a plugin system, would it be possible to affect that
change in a plugin? That way it's at least not a patch to
Alexander Wirt writes ("Re: Want to make salsa advertise contact and source
code details [and 1 more messages]"):
> It was a decision by the team to disallow any patch that is not
> really really needed for function. Please submit your patch
> upstream.
I see. I'm afraid
On Fri, 25 May 2018, Geert Stappers wrote:
> On Fri, May 25, 2018 at 02:54:17PM +0200, Alexander Wirt wrote:
> > On Fri, 25 May 2018, Ian Jackson wrote:
> > >
> > >
> > > But, I find this response worrying. It makes me wonder whether Salsa
> > > is in fact really Free Software, for Debian. I
On Fri, 25 May 2018, Ian Jackson wrote:
> Alexander Wirt writes ("Re: Want to make salsa advertise contact and source
> code details [and 1 more messages]"):
> > > Can you point me to the source code for Salsa's gitlab instance,
> > > please ?
> > https:/
Alexander Wirt writes ("Re: Want to make salsa advertise contact and source
code details [and 1 more messages]"):
> > Can you point me to the source code for Salsa's gitlab instance,
> > please ?
> https://salsa.debian.org/salsa/gitlab-ce
I think I see where to make
On Fri, 2018-05-25 at 17:16 +0200, Geert Stappers wrote:
> Not knowing who is "we", but the thing I want to says is
>
> Do not ask for a lighter load,
> but ask for more shoulders to carry the load.
Asking for a lighter load has given us the wheel, washing machines,
dishwashers, computers,
On Fri, May 25, 2018 at 02:54:17PM +0200, Alexander Wirt wrote:
> On Fri, 25 May 2018, Ian Jackson wrote:
> >
> >
> > But, I find this response worrying. It makes me wonder whether Salsa
> > is in fact really Free Software, for Debian. I don't want to suck
> > energy out of the Salsa team,
On Fri, 25 May 2018, Ian Jackson wrote:
> Quoting my own other mail for more context:
>
> Ian Jackson writes ("Re: Want to make salsa advertise contact and source code
> details"):
> > Alexander Wirt tells me that that feature is "EE only", ie AIUI
Programming Lang: ATS
Description : Polyglot is a command-line tool for counting lines of
source code and detecting languages.
Polyglot is a command-line tool for detecting languages within projects. It
allows users to quickly assess an unfamiliar project, and it allows projects to
track com
Quoting my own other mail for more context:
Ian Jackson writes ("Re: Want to make salsa advertise contact and source code
details"):
> Alexander Wirt tells me that that feature is "EE only", ie AIUI
> that the Gitlab company have kept that feature proprietary.
&
On Fri, 25 May 2018, Ian Jackson wrote:
> Sean Whitton writes ("Re: Bug#864354: Bug #864354 in marked as
> pending"):
> > Thank you for advocating on behalf of users who are not in a position to
> > use the web form, Ian.
>
> Thanks for your support, Sean. I have submitted:
>
>
Ian Jackson writes ("Want to make salsa advertise contact and source code
details"):
> https://salsa.debian.org/salsa/support/issues/77
>Please provide web page footer on every page with service information
>
> In response to the latter, Alexander Wirt writes:
>
&g
Sean Whitton writes ("Re: Bug#864354: Bug #864354 in marked as
pending"):
> Thank you for advocating on behalf of users who are not in a position to
> use the web form, Ian.
Thanks for your support, Sean. I have submitted:
https://salsa.debian.org/salsa/webhook/merge_requests/7
Improve
hi Aaron,
On Tue, May 01, 2018 at 11:10:15AM +0100, Aaron Gray wrote:
> Where do I find the .deb source packaging source code for packlages ? I
> does not seem to be in your sources. I need to update some packages to
> latest releease. Is this done by bhand on packages b
Aaron Gray writes ("source packing source code"):
> Where do I find the .deb source packaging source code for packlages ? I does
> not seem to be in your sources.
I think you probably want my tool `dgit', which will provide the
ready-to-build source code for every package in gi
On Tue, May 01, 2018 at 12:26:30PM +0200, Geert Stappers wrote:
> On Tue, May 01, 2018 at 03:17:27PM +0500, Andrey Rahmatullin wrote:
> > On Tue, May 01, 2018 at 11:10:15AM +0100, Aaron Gray wrote:
> > > Where do I find the .deb source packaging source code for packlages ?
&
On Tue, May 01, 2018 at 03:17:27PM +0500, Andrey Rahmatullin wrote:
> On Tue, May 01, 2018 at 11:10:15AM +0100, Aaron Gray wrote:
> > Where do I find the .deb source packaging source code for packlages ?
> Source packages don't have a .deb extension nor are they one file per
> packa
On Tue, May 01, 2018 at 11:10:15AM +0100, Aaron Gray wrote:
> Where do I find the .deb source packaging source code for packlages ?
Source packages don't have a .deb extension nor are they one file per
package, but you can find them in the apt repo, if you add a deb-src line
mirroring your
Where do I find the .deb source packaging source code for packlages ? I
does not seem to be in your sources. I need to update some packages to
latest releease. Is this done by bhand on packages by bespoke or is there a
build systemn that will deal with separate GNU autoconf/make packages
1 - 100 of 332 matches
Mail list logo
