Steve Langasek:
> Do you ever intend to release this software as a tarball for use outside
> of Debian?
Yes, the tarball that I create for Debian is also distributed from my
homepage (together with Debian packages compiled for potato, for those that
do not use unstable), along with a RAR package
Peter,
On Fri, 20 Jul 2001, peter karlsson wrote:
> > Since this is the Debian changelog rather than an upstream changelog, the
> > majority of changes noted are specific to the shared debian directory, of
> > which there is precisely one for any set of binary packages that are built
> > from a s
Steve Langasek:
> Do you ever intend to release this software as a tarball for use outside
> of Debian?
Yes, the tarball that I create for Debian is also distributed from my
homepage (together with Debian packages compiled for potato, for those that
do not use unstable), along with a RAR package
Peter,
On Fri, 20 Jul 2001, peter karlsson wrote:
> > Since this is the Debian changelog rather than an upstream changelog, the
> > majority of changes noted are specific to the shared debian directory, of
> > which there is precisely one for any set of binary packages that are built
> > from a
Steve Langasek:
> Since this is the Debian changelog rather than an upstream changelog, the
> majority of changes noted are specific to the shared debian directory, of
> which there is precisely one for any set of binary packages that are built
> from a single source package.
Well, first of all,
Steve Langasek:
> Since this is the Debian changelog rather than an upstream changelog, the
> majority of changes noted are specific to the shared debian directory, of
> which there is precisely one for any set of binary packages that are built
> from a single source package.
Well, first of all,
On Thu, 19 Jul 2001, peter karlsson wrote:
> > You can't do that, changelogs have to be shared.
> Why? The changelog lists what was changed between the versions, and that
> differens between the two binary packages I created (there was a feature
> only added to the command line version, not the G
On Jul 19, 1:27pm, peter karlsson wrote:
> Why? The changelog lists what was changed between the versions, and that
> differens between the two binary packages I created (there was a feature
> only added to the command line version, not the GUI version), and I want
> that reflected in the changelo
On Thu, 19 Jul 2001, peter karlsson wrote:
> > You can't do that, changelogs have to be shared.
> Why? The changelog lists what was changed between the versions, and that
> differens between the two binary packages I created (there was a feature
> only added to the command line version, not the
Wichert Akkerman:
> You can't do that, changelogs have to be shared.
Why? The changelog lists what was changed between the versions, and that
differens between the two binary packages I created (there was a feature
only added to the command line version, not the GUI version), and I want
that refl
Previously peter karlsson wrote:
> dpkg-gencontrol: error: source package has two conflicting values - turqstat
> and xturqstat
debian/changelog and debian/control have different for the package name.
> My source package "turqstat" generates two binary packages, "turqstat"
> and "xturqstat". They
On Jul 19, 1:27pm, peter karlsson wrote:
> Why? The changelog lists what was changed between the versions, and that
> differens between the two binary packages I created (there was a feature
> only added to the command line version, not the GUI version), and I want
> that reflected in the changel
Wichert Akkerman:
> You can't do that, changelogs have to be shared.
Why? The changelog lists what was changed between the versions, and that
differens between the two binary packages I created (there was a feature
only added to the command line version, not the GUI version), and I want
that ref
Previously peter karlsson wrote:
> dpkg-gencontrol: error: source package has two conflicting values - turqstat
> and xturqstat
debian/changelog and debian/control have different for the package name.
> My source package "turqstat" generates two binary packages, "turqstat"
> and "xturqstat". The
Hi!
What does this mean?
dpkg-gencontrol: error: source package has two conflicting values - turqstat
and xturqstat
My source package "turqstat" generates two binary packages, "turqstat"
and "xturqstat". They each have their own changelogs (debian/changelog
and debian/xturqstat.changelog), and
On Wed, 18 Jul 2001, peter karlsson wrote:
> Hi!
>
> What does this mean?
>
> dpkg-gencontrol: error: source package has two conflicting values - turqstat
> and xturqstat
>
> My source package "turqstat" generates two binary packages, "turqstat"
> and "xturqstat". They each have their own chan
On Wed, 18 Jul 2001, peter karlsson wrote:
> Hi!
>
> What does this mean?
>
> dpkg-gencontrol: error: source package has two conflicting values - turqstat and
>xturqstat
>
> My source package "turqstat" generates two binary packages, "turqstat"
> and "xturqstat". They each have their own chan
Hi!
What does this mean?
dpkg-gencontrol: error: source package has two conflicting values - turqstat and
xturqstat
My source package "turqstat" generates two binary packages, "turqstat"
and "xturqstat". They each have their own changelogs (debian/changelog
and debian/xturqstat.changelog), and
18 matches
Mail list logo
